3GPP TS 36.523-1: Technical Specification

3GPP TS 36.523-1 V9.3.
0 (2010-12)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA)
and Evolved Packet Core (EPC);
User Equipment (UE) conformance specification;
Part 1: Protocol conformance specification
(Release 9)

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

Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP

only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP
TM
systemshould be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 2

Keywords
LTE, testing
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.

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

UMTS is a Trade Mark of ETSI registered for the benefit of its members
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners
GSMand the GSM logo are registered and owned by the GSM Association
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
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 3
Contents
Foreword .......................................................................................................................................................... 15
Introduction ...................................................................................................................................................... 15
1 Scope ...................................................................................................................................................... 16
2 References .............................................................................................................................................. 16
3 Definitions, symbols and abbreviations ................................................................................................. 18
3.1 Definitions ....................................................................................................................................................... 18
3.2 Abbreviations ................................................................................................................................................... 18
4 Overview ................................................................................................................................................ 18
4.1 Test methodology ............................................................................................................................................ 18
4.1.1 Testing of optional functions and procedures ............................................................................................ 18
4.1.2 Test interfaces and facilities ....................................................................................................................... 18
4.2 Implicit testing ................................................................................................................................................. 19
4.3 Repetition of tests ............................................................................................................................................ 19
5 Reference conditions .............................................................................................................................. 19
5.1 Generic setup procedures ................................................................................................................................. 19
6 Idle mode operations .............................................................................................................................. 19
6.0 Introduction ...................................................................................................................................................... 19
6.0.1 PLMN and TAC ......................................................................................................................................... 19
6.0.2 Other........................................................................................................................................................... 20
6.1 In a pure E-UTRAN environment .................................................................................................................... 20
6.1.1 PLMN selection ......................................................................................................................................... 20
6.1.1.1 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode ............ 20
6.1.1.2 PLMN selection of "Other PLMN/access technology combinations" / Automatic mode .................... 26
6.1.1.3 Void ...................................................................................................................................................... 30
6.1.1.4 PLMN selection in shared network environment / Automatic mode .................................................... 30
6.1.1.5 Void ...................................................................................................................................................... 33
6.1.1.6 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
User reselection .................................................................................................................................... 33
6.1.2 Cell selection and reselection ..................................................................................................................... 37
6.1.2.1 Void ...................................................................................................................................................... 37
6.1.2.2 Cell selection / Qrxlevmin .................................................................................................................... 37
6.1.2.3 Cell selection / Intra E-UTRAN / Serving cell becomes non-suitable (S<0 or barred) ........................ 40
6.1.2.4 Cell reselection ..................................................................................................................................... 44
6.1.2.5 Cell reselection for interband operation ................................................................................................ 46
6.1.2.6 Cell reselection using Q
hyst
, Q
offset
and T
reselection
................................................................................... 49
6.1.2.7 Cell reselection / Equivalent PLMN ..................................................................................................... 55
6.1.2.8 Cell reselection using cell status and cell reservations / Access control class 0 to 9 ............................ 60
6.1.2.9 Cell reselection using cell status and cell reservations / Access control class 11 to 15 ........................ 64
6.1.2.10 Cell reselection in shared network environment ................................................................................... 69
6.1.2.11 Inter-frequency cell reselection ............................................................................................................ 72
6.1.2.12 Cell reselection / Cell-specific reselection parameters provided by the network in a neighbouring
cell list .................................................................................................................................................. 73
6.1.2.13 Cell reselection, S
intrasearch
, S
nonintrasearch
................................................................................................. 76
6.1.2.14 Speed-dependent cell reselection .......................................................................................................... 80
6.1.2.15 Inter-frequency cell reselection according to cell reselection priority provided by SIBs ..................... 84
6.2 Multi-mode environment (E-UTRAN, UTRAN, GERAN, CDMA2000) ....................................................... 89
6.2.1 Inter-RAT PLMN selection ........................................................................................................................ 89
6.2.1.1 Inter-RAT PLMN Selection / Selection of correct RAT for OPLMN / Automatic mode .................... 89
6.2.1.2 Inter-RAT PLMN Selection / Selection of correct RAT for UPLMN / Automatic mode .................... 92
6.2.1.3 Inter-RAT PLMN Selection / Selection of correct PLMN and RAT in shared network
environment / Automatic mode ............................................................................................................ 94
6.2.1.4 Inter-RAT PLMN Selection / Selection of correct RAT from the OPLMN list / Manual mode .......... 97
6.2.2 Inter-RAT cell selection ............................................................................................................................. 99
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 4
6.2.2.1 Inter-RAT cell selection / From E-UTRA RRC_IDLE to UTRA_Idle / Serving cell becomes
non-suitable .......................................................................................................................................... 99
6.2.2.2 Inter-RAT cell selection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_idle / Serving
cell becomes non-suitable ................................................................................................................... 104
6.2.2.3 Inter-RAT Cell selection / From E-UTRA RRC_IDLE to HRPD Idle / Serving cell becomes
non-suitable ........................................................................................................................................ 110
6.2.2.4 Inter-RAT Cell selection / From E-UTRAN RRC_IDLE to 1xRTT idle / Serving cell becomes
non-suitable ........................................................................................................................................ 113
6.2.2.5 Cell selection / No USIM ................................................................................................................... 118
6.2.2.6 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-UTRA_RRC_IDLE /
Serving cell becomes non-suitable ..................................................................................................... 119
6.2.2.7 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-UTRA_RRC_IDLE ,when
the serving cell is barred. .................................................................................................................... 121
6.2.3 Inter-RAT cell reselection ........................................................................................................................ 124
6.2.3.1 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_Idle .............. 124
6.2.3.2 Inter-RAT Cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA .................................. 129
6.2.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE ........................................... 131
6.2.3.4 Inter-RAT cell reselection / From UTRA_CELL_PCH state to E-UTRA RRC_IDLE ..................... 136
6.2.3.5 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle ........................................... 141
6.2.3.6 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle according to RAT
priority provided by dedicated signalling ........................................................................................... 143
6.2.3.7 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is higher
reselection priority than E-UTRA ...................................................................................................... 152
6.2.3.8 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD is lower
reselection priority than E-UTRA ...................................................................................................... 157
6.2.3.9 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT Dormant When
CDMA2000 1xRTT cell is higher reselection priority than E-UTRA ................................................ 162
6.2.3.10 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT Idle When
CDMA2000 1xRTT is lower reselection priority than E-UTRA ....................................................... 167
6.2.3.11 Void .................................................................................................................................................... 171
6.2.3.12 Void .................................................................................................................................................... 171
6.2.3.13 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE according to RAT
priority provided by dedicated signalling ........................................................................................... 171
6.2.3.14 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA (priority of E-
UTRA cells are higher than the serving cell) ..................................................................................... 178
6.2.3.15 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA (priority of E-
UTRA cells are lower than the serving cell) ....................................................................................... 181
6.2.3.16 Void .................................................................................................................................................... 183
6.2.3.17 Void .................................................................................................................................................... 183
6.2.3.18 Void .................................................................................................................................................... 183
6.2.3.19 Redirection to E-UTRA upon the release of the CS connection ......................................................... 183
6.2.3.20 Redirection to E-UTRA upon the release of the CS connection and no suitable cell available .......... 186
6.2.3.21 Inter-RAT cell reselection / From GPRS Packet_Transfer (NC0 mode) to E-UTRA ........................ 188
6.2.3.22 Inter-RAT Cell Reselection Failure / from GPRS Packet_Transfer (NC0 mode) to E-UTRA ........... 191
6.2.3.23 Inter-RAT Cell Reselection from GPRS Packet transfer to E-UTRA in CCN Mode(PACKET
CELL CHANGE CONTINUE) .......................................................................................................... 195
6.2.3.24 Void .................................................................................................................................................... 198
6.2.3.25 Void .................................................................................................................................................... 198
6.2.3.26 Void .................................................................................................................................................... 198
6.2.3.27 Inter-RAT Cell selection from GPRS Packet_transfer to E-UTRA (NC2 Mode) .............................. 198
6.2.3.28 Inter-RAT Cell Reselection from GPRS Packet_transfer to E-UTRA (Network Assisted Cell
Change) .............................................................................................................................................. 202
6.2.3.29 Void .................................................................................................................................................... 206
6.2.3.30 Inter-RAT Cell Reselection failure from GPRS Packet transfer to E-UTRA (Network Assisted
Cell Change) ....................................................................................................................................... 206
6.2.3.31 Inter-RAT cell reselection / From UTRA_Idle (low priority) to E-UTRA RRC_IDLE (high
priority) according to RAT priority provided by dedicated signalling ............................................... 210
6.3 Closed Subscriber Group cells ....................................................................................................................... 216
6.3.1 Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-CSG cell to E-UTRA RRC_IDLE
CSG cell ................................................................................................................................................... 216
6.3.2 Void .......................................................................................................................................................... 220
6.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE CSG cell ................................. 220
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 5
6.3.4 Inter-RAT cell reselection / From UTRA CELL_PCH state to E-UTRA RRC_IDLE CSG cell............. 226
6.3.5 Void .......................................................................................................................................................... 232
6.3.6 Ignoring CSG cells in cell selection/reselection when allowed CSG list is empty or not supported ....... 232
6.3.7 Inter-RAT Cell reselection from E-UTRA idle non-CSG cell to a UTRA CSG cell ............................... 236
6.3.8 Inter-RAT CSG Cell Reselection from E-UTRA CSG cell to UTRA CSG cell ...................................... 241
7 Layer 2 ................................................................................................................................................. 249
7.1 MAC .............................................................................................................................................................. 249
7.1.1 Mapping between logical channels and transport channels ...................................................................... 249
7.1.1.1 CCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID .............................................. 249
7.1.1.2 DTCH or DCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID ............................. 252
7.1.2 RACH....................................................................................................................................................... 255
7.1.2.1 Correct selection of RACH parameters / Random access preamble and PRACH resource
explicitly signalled to the UE by RRC / Non-contention based random access procedure ................ 255
7.1.2.2 Correct selection of RACH parameters / Random access preamble and PRACH resource
explicitly signalled to the UE in PDCCH Order / Non-contention based random access procedure .. 258
7.1.2.3 Correct selection of RACH parameters / Preamble selected by MAC itself / Contention based
random access procedure .................................................................................................................... 260
7.1.2.4 Random access procedure / Successful .............................................................................................. 265
7.1.2.5 Random access procedure / MAC PDU containing multiple RARs ................................................... 271
7.1.2.6 Maintenance of uplink time alignment ............................................................................................... 274
7.1.2.7 MAC contention resolution / Temporary C-RNTI ............................................................................. 278
7.1.2.8 MAC contention resolution / C-RNTI ................................................................................................ 281
7.1.2.9 MAC backoff indicator ....................................................................................................................... 284
7.1.3 DL-SCH data transfer .............................................................................................................................. 288
7.1.3.1 Correct handling of DL assignment / Dynamic case .......................................................................... 288
7.1.3.2 Correct handling of DL assignment / Semi-persistent case ................................................................ 289
7.1.3.3 MAC PDU header handling ............................................................................................................... 297
7.1.3.4 Correct HARQ process handling / DCCH and DTCH ....................................................................... 302
7.1.3.5 Correct HARQ process handling / CCCH .......................................................................................... 305
7.1.3.6 Correct HARQ process handling / BCCH .......................................................................................... 309
7.1.3.7 MAC padding ..................................................................................................................................... 314
7.1.3.8 Void .................................................................................................................................................... 316
7.1.3.9 MAC reset / DL .................................................................................................................................. 316
7.1.4 UL-SCH data transfer .............................................................................................................................. 318
7.1.4.1 Correct handling of UL assignment / Dynamic case .......................................................................... 318
7.1.4.2 Correct handling of UL assignment / Semi-persistent case ................................................................ 320
7.1.4.3 Logical channel prioritization handling .............................................................................................. 329
7.1.4.4 Correct handling of MAC control information / Scheduling requests and PUCCH ........................... 332
7.1.4.5 Correct handling of MAC control information / Scheduling requests and random access
procedure ............................................................................................................................................ 334
7.1.4.6 Correct handling of MAC control information / Buffer status / UL data arrive in the UE Tx
buffer and retransmission of BSR / Regular BSR .............................................................................. 338
7.1.4.7 Correct handling of MAC control information / Buffer Status / UL resources are allocated /
Padding BSR ...................................................................................................................................... 345
7.1.4.8 Correct handling of MAC control information / Buffer status / Periodic BSR timer expires ............. 350
7.1.4.9 Void .................................................................................................................................................... 354
7.1.4.10 MAC padding ..................................................................................................................................... 354
7.1.4.11 Correct HARQ process handling ........................................................................................................ 357
7.1.4.12 MAC reset / UL .................................................................................................................................. 363
7.1.4.13 MAC PDU header handling ............................................................................................................... 367
7.1.4.14 Correct HARQ process handling / TTI bundling ................................................................................ 372
7.1.4.15 UE power headroom reporting / Periodic reporting ........................................................................... 379
7.1.4.16 UE power headroom reporting / DL pathloss change reporting ......................................................... 382
7.1.5 PUSCH Hopping ...................................................................................................................................... 386
7.1.5.1 Inter-TTI PUSCH hopping by uplink grant ........................................................................................ 386
7.1.5.2 Predefined intra-TTI PUSCH hopping (N_sb=1) ............................................................................... 389
7.1.5.3 Predefined intra-TTI PUSCH hopping (N_sb=2/3/4) ......................................................................... 393
7.1.5.4 Predefined inter-TTI PUSCH hopping (N_sb=1) ............................................................................... 395
7.1.5.5 Predefined inter-TTI PUSCH hopping (N_sb=2/3/4) ......................................................................... 396
7.1.6 DRX operation ......................................................................................................................................... 397
7.1.6.1 DRX operation / Short cycle not configured / Parameters configured by RRC ................................. 397
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 6
7.1.6.2 DRX Operation / Short cycle not configured / DRX command MAC control element reception ...... 404
7.1.7 Transport block size selection .................................................................................................................. 409
7.1.7.0 Specific configurations ....................................................................................................................... 409
7.1.7.1 DL-SCH transport block size selection .............................................................................................. 409
7.1.7.1.1 DL-SCH transport block size selection / DCI format 1 / RA type 0 ............................................. 409
7.1.7.1.2 DL-SCH transport block size selection / DCI format 1 / RA type 1 ............................................. 422
7.1.7.1.3 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Localised VRB .............. 435
7.1.7.1.4 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Distributed VRB ............ 449
7.1.7.1.5 DL-SCH transport block size selection / DCI format 2A / RA type 0 / Two transport blocks
enabled / Transport block to codeword swap flag value set to 0 ................................................ 463
7.1.7.1.6 DL-SCH Transport Block Size selection / DCI format 2A / RA type 1 / Two transport blocks
enabled / Transport block to codeword swap flag value set to 1 ................................................ 478
7.1.7.2 UL-SCH transport block size support ................................................................................................. 492
7.1.7.2.1 UL-SCH transport block size selection / DCI format 0 ................................................................ 492
7.1.8 Reporting of Rank Indicator (RI) ............................................................................................................. 505
7.1.8.1 Periodic RI reporting using PUCCH / Category 1 UE / Transmission mode 3/4 ............................... 505
7.2 RLC ............................................................................................................................................................... 510
7.2.1 General ..................................................................................................................................................... 510
7.2.2 Unacknowledged mode ............................................................................................................................ 510
7.2.2.1 UM RLC / Segmentation and reassembly / 5-bit SN / Framing info field.......................................... 510
7.2.2.2 UM RLC / Segmentation and reassembly / 10-bit SN / Framing info field........................................ 512
7.2.2.3 UM RLC / Reassembly / 5-bit SN / LI value >PDU size .................................................................. 514
7.2.2.4 UM RLC / Reassembly / 10-bit SN / LI value >PDU size ................................................................ 515
7.2.2.5 UM RLC / Correct use of sequence numbering ................................................................................. 516
7.2.2.5.1 UM RLC / 5-bit SN / Correct use of sequence numbering ........................................................... 516
7.2.2.5.2 UM RLC / 10-bit SN / Correct use of Sequence numbering ......................................................... 520
7.2.2.6 UM RLC / Concatenation, segmentation and reassembly .................................................................. 523
7.2.2.7 UM RLC / In sequence delivery of upper layer PDUs without residual loss of RLC PDUs /
Maximum re-ordering delay below t-Reordering ............................................................................... 528
7.2.2.8 UM RLC / In sequence delivery of upper layer PDUs without residual loss of RLC PDUs /
Maximum re-ordering delay exceeds t-Reordering ............................................................................ 531
7.2.2.9 UM RLC / In sequence delivery of upper layer PDUs with residual loss of RLC PDUs /
Maximum re-ordering delay exceeds t-Reordering ............................................................................ 533
7.2.2.10 UM RLC / Duplicate detection of RLC PDUs ................................................................................... 535
7.2.2.11 UM RLC / RLC re-establishment procedure ...................................................................................... 537
7.2.3 Acknowledged mode ................................................................................................................................ 540
7.2.3.1 AM RLC / Concatenation and reassembly ......................................................................................... 540
7.2.3.2 AM RLC / Segmentation and reassembly / No PDU segmentation ................................................... 543
7.2.3.3 AM RLC / Segmentation and reassembly / Framing info field .......................................................... 545
7.2.3.4 AM RLC / Segmentation and reassembly / Different numbers of length indicators .......................... 547
7.2.3.5 AM RLC / Reassembly / LI value >PDU size ................................................................................... 550
7.2.3.6 AM RLC / Correct use of sequence numbering ................................................................................. 551
7.2.3.7 AM RLC / Control of transmit window.............................................................................................. 554
7.2.3.8 AM RLC / Control of receive window ............................................................................................... 556
7.2.3.9 AM RLC / Polling for status ............................................................................................................... 558
7.2.3.10 AM RLC / Receiver status triggers .................................................................................................... 562
7.2.3.11 Void .................................................................................................................................................... 567
7.2.3.12 Void .................................................................................................................................................... 567
7.2.3.13 AM RLC / Reconfiguration of RLC parameters by upper layers ....................................................... 567
7.2.3.14 AM RLC / In sequence delivery of upper layers PDUs ...................................................................... 572
7.2.3.15 AM RLC / Re-ordering of RLC PDU segments ................................................................................. 575
7.2.3.16 AM RLC / Re-transmission of RLC PDU without re-segmentation .................................................. 580
7.2.3.17 AM RLC / Re-segmentation RLC PDU / SO, FI, LSF ....................................................................... 583
7.2.3.18 AM RLC / Reassembly / AMD PDU reassembly from AMD PDU segments, Segmentation
Offset and Last Segment Flag fields ................................................................................................... 586
7.2.3.19 Void .................................................................................................................................................... 591
7.2.3.20 AM RLC / Duplicate detection of RLC PDUs ................................................................................... 591
7.2.3.21 AM RLC / RLC re-establishment at RRC connection reconfiguration including
mobilityControlInfo IE ....................................................................................................................... 593
7.3 PDCP ............................................................................................................................................................. 595
7.3.1 Maintenance of PDCP sequence numbers for radio bearers .................................................................... 595
7.3.1.1 Maintenance of PDCP sequence numbers / User plane / RLC AM .................................................... 595
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 7
7.3.1.2 Maintenance of PDCP sequence numbers / User plane / RLC UM / Short PDCP SN (7 bits) ........... 598
7.3.1.3 Maintenance of PDCP sequence numbers / User plane / RLC UM / Long PDCP SN (12 bits) ......... 600
7.3.2 Void .......................................................................................................................................................... 602
7.3.3 PDCP ciphering and deciphering ............................................................................................................. 602
7.3.3.1 Ciphering and deciphering / Correct functionality of EPS AS encryption algorithms / SNOW 3G ... 602
7.3.3.2 Ciphering and deciphering / Correct functionality of EPS UP encryption algorithms / SNOW 3G ... 605
7.3.3.3 Ciphering and deciphering / Correct functionality of EPS AS encryption algorithms / AES ............. 606
7.3.3.4 Ciphering and deciphering / Correct functionality of EPS UP encription algorithms / AES.............. 607
7.3.4 PDCP integrity protection ........................................................................................................................ 608
7.3.4.1 Integrity protection / Correct functionality of EPS AS integrity algorithms / SNOW3G ................... 608
7.3.4.2 Integrity protection / Correct functionality of EPS AS integrity algorithms / AES ............................ 612
7.3.5 PDCP handover ........................................................................................................................................ 613
7.3.5.1 Void .................................................................................................................................................... 613
7.3.5.2 PDCP handover / Lossless handover / PDCP sequence number maintenance ................................... 613
7.3.5.3 PDCP handover / Non-lossless handover PDCP sequence number maintenance............................... 616
7.3.5.4 PDCP handover / Lossless handover / PDCP status report to convey the information on missing
or acknowledged PDCP SDUs at handover ........................................................................................ 619
7.3.5.5 PDCP handover / In-order delivery and duplicate elimination in the downlink ................................. 622
7.3.6 PDCP Others ............................................................................................................................................ 627
7.3.6.1 PDCP Discard ..................................................................................................................................... 627
8 RRC ...................................................................................................................................................... 629
8.1 RRC connection management procedures ..................................................................................................... 629
8.1.1 Paging....................................................................................................................................................... 629
8.1.1.1 RRC / Paging for connection in idle mode ......................................................................................... 629
8.1.1.2 RRC / Paging for notification of BCCH modification in idle mode ................................................... 632
8.1.1.3 RRC / Paging for connection in idle mode / Multiple paging records ................................................ 636
8.1.1.4 RRC / Paging for connection in idle mode / Shared network environment ........................................ 640
8.1.1.5 Void .................................................................................................................................................... 644
8.1.1.6 RRC / BCCH modification in connected mode .................................................................................. 644
8.1.2 RRC connection establishment ................................................................................................................ 646
8.1.2.1 RRC connection establishment / Ks=1.25/ Success ........................................................................... 646
8.1.2.2 RRC connection establishment / Reject with wait time ...................................................................... 650
8.1.2.3 RRC connection establishment / Return to idle state after T300 timeout ........................................... 653
8.1.2.4 Void .................................................................................................................................................... 654
8.1.2.5 RRC connection establishment / 0% access probability for MO calls, no restriction for MO
signalling ............................................................................................................................................ 654
8.1.2.6 RRC connection establishment / Non-zero percent access probability for MO calls, no restriction
for MO signalling ............................................................................................................................... 658
8.1.2.7 RRC connection establishment / 0% access probability for AC 0 to 9, AC 10 is barred, AC 11 to
15 are not barred, access for UE with access class in the range 11 to 15 is allowed .......................... 662
8.1.2.8 RRC connection establishment / Range of access baring time ........................................................... 666
8.1.2.9 RRC Connection Establishment / 0% access probability for MO calls, non-zero percent access
probability for MO signalling ............................................................................................................. 671
8.1.2.10 RRC connection establishment / 0% access probability for MO calls, 0% access probability for
MO signalling ..................................................................................................................................... 676
8.1.2.11 RRC connection establishment of emergency call ............................................................................. 680
8.1.2.12 RRC connection establishment of emergency call / Limited Service ................................................. 682
8.1.3 RRC connection release ........................................................................................................................... 686
8.1.3.1 RRC connection release / Success ...................................................................................................... 686
8.1.3.2 Void .................................................................................................................................................... 687
8.1.3.3 Void .................................................................................................................................................... 687
8.1.3.4 RRC connection release / Redirection to another E-UTRAN frequency ............................................ 687
8.1.3.5 RRC connection release / Success / With priority information .......................................................... 690
8.1.3.6 RRC connection release / Redirection from E-UTRAN to UTRAN .................................................. 694
8.1.3.7 RRC connection release / Redirection from UTRAN to E-UTRAN .................................................. 697
8.1.3.8 RRC connection release / Redirection from E-UTRAN to GERAN .................................................. 703
8.1.3.9 RRC connection release / Redirection from E-UTRAN to CDMA2000-HRPD ................................ 705
8.1.3.10 RRC connection release / Redirection from E-UTRAN to CDMA2000-1xRTT ............................... 707
8.2 RRC connection reconfiguration ................................................................................................................... 710
8.2.1 Radio bearer establishment ...................................................................................................................... 710
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 8
8.2.1.1 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE to
RRC_CONNECTED / Success / Default bearer / Early bearer establishment ................................... 710
8.2.1.2 Void .................................................................................................................................................... 712
8.2.1.3 RRC connection reconfiguration / Radio bearer establishment / Success / Dedicated bearer ............ 712
8.2.1.4 Void .................................................................................................................................................... 714
8.2.1.5 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_Idle to
RRC CONNECTED / Success / Latency check ................................................................................. 714
8.2.1.6 RRC connection reconfiguration / Radio bearer establishment for transition from RRC_Idle to
RRC CONNECTED / Success / Latency check / SecurityModeCommand and
RRCConnectionReconfiguration transmitted in the same TTI ........................................................... 719
8.2.1.7 RRC connection reconfiguration / Radio bearer establishment / Success / SRB2 .............................. 722
8.2.2 Radio resource reconfiguration ................................................................................................................ 724
8.2.2.1 RRC connection reconfiguration / Radio resource reconfiguration / Success .................................... 724
8.2.2.2 RRC connection reconfiguration / SRB/DRB reconfiguration / Success ........................................... 728
8.2.3 Radio bearer release ................................................................................................................................. 731
8.2.3.1 RRC connection reconfiguration / Radio bearer release / Success ..................................................... 731
8.2.4 Handover .................................................................................................................................................. 733
8.2.4.1 RRC connection reconfiguration / Handover / Success / Dedicated preamble ................................... 733
8.2.4.2 RRC connection reconfiguration / Handover / Success / Common preamble .................................... 742
8.2.4.3 RRC connection reconfiguration / Handover / Success / Intra-cell / Security reconfiguration .......... 746
8.2.4.4 RRC connection reconfiguration / Handover / Failure / Intra-cell / Security reconfiguration ........... 750
8.2.4.5 RRC connection reconfiguration / Handover / All parameters included ............................................ 755
8.2.4.6 RRC connection reconfiguration / Handover / Success / Inter-frequency .......................................... 761
8.2.4.7 RRC connection reconfiguration / Handover / Failure / Re-establishment successful ....................... 765
8.2.4.8 RRC connection reconfiguration / Handover / Failure / Re-establishment failure ............................. 779
8.2.4.9 RRC connection reconfiguration / Handover / Inter-band blind handover / Success ......................... 786
8.2.4.10 RRC connection reconfiguration / Handover (between FDD and TDD) ............................................ 789
8.2.4.11 Void .................................................................................................................................................... 793
8.2.4.12 RRC connection reconfiguration / Handover / Setup and release of MIMO ...................................... 793
8.3 Measurement configuration control and reporting ......................................................................................... 797
8.3.1 Intra E-UTRAN measurements ................................................................................................................ 797
8.3.1.1 Measurement configuration control and reporting / Intra E-UTRAN measurements / Event A1 ....... 797
8.3.1.2 Measurement configuration control and reporting / Intra E-UTRAN measurements / Event A2 ....... 802
8.3.1.3 Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A3 (intra and inter-frequency measurements) ................................................... 807
8.3.1.4 Measurement configuration control and reporting / Intra E-UTRAN measurements / Periodic
reporting (intra and inter-frequency measurements) ........................................................................... 815
simultaneous event A3 (intra-frequency measurements) .................................................................... 824
simultaneous events A2 and A3 (inter-frequency measurements) ...................................................... 832
8.3.1.7 Measurement configuration control and reporting / Intra E-UTRAN measurements / Blacklisting .. 840
8.3.1.8 Measurement configuration control and reporting / Intra E-UTRAN measurements / Handover /
IE measurement configuration present ............................................................................................... 846
8.3.1.9 Measurement configuration control and reporting / Intra E-UTRAN measurements / Intra-
frequency handover / IE measurement configuration not present ...................................................... 852
8.3.1.10 Measurement configuration control and reporting / Intra E-UTRAN measurements / Inter-
frequency handover / IE measurement configuration not present ...................................................... 860
8.3.1.11 Measurement configuration control and reporting / Intra E-UTRAN measurements /
Continuation of the measurements after RRC connection re-establishment ....................................... 866
8.3.2 Inter-RAT measurements ......................................................................................................................... 876
8.3.2.1 Measurement configuration control and reporting / Inter-RAT measurements / Event B2 /
Measurement of GERAN cells ........................................................................................................... 876
8.3.2.2 Measurement configuration control and reporting / Inter-RAT measurements / Periodic reporting
/ Measurement of GERAN cells ......................................................................................................... 883
Measurement of UTRAN cells ........................................................................................................... 890
/ Measurement of UTRAN cells ......................................................................................................... 898
/ Measurements of E-UTRAN, UTRAN and GERAN cells ............................................................... 907
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 9
8.3.2.6 Measurement configuration control and reporting / Inter-RAT measurements / Simultaneous A2
and two B2 / Measurements of E-UTRAN, UTRAN and GERAN cells ........................................... 917
8.3.2.7 Measurement configuration control and reporting / Inter-RAT measurements / Event B2
(measurement HRPD cells) ................................................................................................................ 925
/ Measurement of HRPD cells) ........................................................................................................... 932
Measurement of 1xRTT cells) ............................................................................................................ 941
/ Measurement of 1xRTT cells ........................................................................................................... 949
8.3.3 Measurements for self optimized networks .............................................................................................. 959
8.3.3.1 Measurement configuration control and reporting / SON / ANR / CGI reporting of E-UTRAN
cell ...................................................................................................................................................... 959
8.3.3.2 Measurement configuration control and reporting / SON / ANR / CGI reporting of UTRAN cell .... 971
8.3.3.3 Measurement configuration control and reporting / SON / ANR / CGI reporting of GERAN cell .... 983
8.3.3.4 Measurement configuration control and reporting / SON / ANR / CGI reporting of HRPD cell ....... 993
8.3.3.5 Measurement configuration control and reporting / SON / ANR / CGI reporting of 1xRTT cell .... 1005
8.4 Inter-RAT handover ..................................................................................................................................... 1017
8.4.1 1017
8.4.1.1 Void .................................................................................................................................................. 1017
8.4.1.2 Inter-RAT handover / From E-UTRA to UTRA PS / Data .............................................................. 1017
8.4.1.3 Void .................................................................................................................................................. 1019
8.4.1.4 Inter-RAT handover / From E-UTRA to UTRA HSDPA / Data ...................................................... 1019
8.4.2 1021
8.4.2.1 Void .................................................................................................................................................. 1021
8.4.2.2 Inter-RAT handover / From UTRA PS to E-UTRA / Data .............................................................. 1021
8.4.2.3 Void .................................................................................................................................................. 1026
8.4.2.4 Inter-RAT handover / From UTRA HSPA to E-UTRA / Data ......................................................... 1026
8.4.2.5 Void .................................................................................................................................................. 1031
8.4.2.6 Void .................................................................................................................................................. 1031
8.4.3 1031
8.4.3.1 Void .................................................................................................................................................. 1031
8.4.3.2 Inter-RAT cell change order / From E-UTRA data RRC_CONNECTED to GPRS / Without
NACC ............................................................................................................................................... 1031
8.4.3.3 Inter-RAT cell change order / From E-UTRA data to GPRS / With NACC .................................... 1035
8.4.4 Void ........................................................................................................................................................ 1039
8.4.5 Inter-RAT handover E-UTRA to HRPD ................................................................................................ 1039
8.4.5.1 Void .................................................................................................................................................. 1039
8.4.5.2 Void .................................................................................................................................................. 1039
8.4.5.3 Void .................................................................................................................................................. 1039
8.4.5.4 Pre-registration at HRPD and inter-RAT handover / From E-UTRA to HRPD Active / Data ......... 1039
8.4.6 Void ........................................................................................................................................................ 1050
8.4.7 Inter-RAT handover E-UTRA to 1xRTT ............................................................................................... 1050
8.4.7.1 Inter-RAT handover / SRVCC from E-UTRA to 1xRTT(CS) / Speech .......................................... 1050
8.4.7.2 Void .................................................................................................................................................. 1064
8.4.7.3 Pre-registration at 1xRTT and inter-RAT Handover / CS fallback from E-UTRA RRC_IDLE to
1xRTT .............................................................................................................................................. 1064
8.4.7.4 Pre-registration at 1xRTT and inter-RAT handover / CS fallback caused by addition of CS
service / From E-UTRA (Data) to 1xRTT ........................................................................................ 1072
8.5 RRC others ................................................................................................................................................... 1078
8.5.1 Radio link failure .................................................................................................................................... 1078
8.5.1.1 Radio link failure / RRC connection re-establishment success ........................................................ 1078
8.5.1.2 Radio link failure / T301 expiry ....................................................................................................... 1081
8.5.1.3 Radio link failure / T311 expiry ....................................................................................................... 1084
8.5.1.4 Radio link failure / RRC connection re-establisment reject ............................................................. 1086
8.5.1.5 Radio link failure / Radio link recovery while T310 is running ....................................................... 1087
8.5.2 1089
8.5.2.1 Redirection to E-UTRAN / From UTRAN upon reception of RRC CONNECTION REJ ECT ....... 1089
8.5.3 Void ........................................................................................................................................................ 1092
8.5.4 UE capability transfer ............................................................................................................................ 1092
8.5.4.1 UE capability transfer / Success ....................................................................................................... 1092
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 10
9 EPS mobility management ................................................................................................................. 1102
9.1 EMM common procedures .......................................................................................................................... 1102
9.1.1 Void ........................................................................................................................................................ 1102
9.1.1.1 Void .................................................................................................................................................. 1102
9.1.1.2 Void .................................................................................................................................................. 1102
9.1.2 Authentication procedure ....................................................................................................................... 1102
9.1.2.1 Authentication accepted ................................................................................................................... 1102
9.1.2.2 Void .................................................................................................................................................. 1105
9.1.2.3 Authentication not accepted by the network / GUTI used / Authentication reject and re-
authentication ................................................................................................................................... 1105
9.1.2.4 Authentication not accepted by the UE / MAC code failure ............................................................ 1107
9.1.2.5 Authentication not accepted by the UE / SQN failure ...................................................................... 1110
9.1.2.6 Abnormal cases / Network failing the authentication check ............................................................. 1113
9.1.3 Security mode control procedure ........................................................................................................... 1115
9.1.3.1 NAS security mode command accepted by the UE .......................................................................... 1115
9.1.3.2 NAS security mode command not accepted by the UE .................................................................... 1119
9.1.4 Identification procedure ......................................................................................................................... 1122
9.1.4.1 Void .................................................................................................................................................. 1122
9.1.4.2 Identification procedure / IMEI requested ........................................................................................ 1122
9.1.5 EMM information procedure ................................................................................................................. 1123
9.1.5.1 EMM information procedure ............................................................................................................ 1123
9.1.5.2 EMM information procedure not supported by the UE .................................................................... 1125
9.2 EMM specific procedures ............................................................................................................................ 1126
9.2.1 Attach procedure .................................................................................................................................... 1126
9.2.1.1 Attach procedure for EPS services ................................................................................................... 1126
9.2.1.1.1 Attach / Success / Valid GUTI .................................................................................................... 1126
9.2.1.1.1a Attach Procedure / Success / Last visited TAI, TAI list and equivalent PLMN list handling .... 1134
9.2.1.1.2 Attach Procedure / Success / With IMSI / GUTI reallocation .................................................... 1142
9.2.1.1.3 Attach Procedure / Success / Request for obtaining the IPv6 address of the home agent ........... 1145
9.2.1.1.4 Attach Procedure / Success / Request for obtaining the IPv4 address of the home agent ........... 1150
9.2.1.1.5 Void ............................................................................................................................................ 1155
9.2.1.1.6 Void ............................................................................................................................................ 1155
9.2.1.1.7 Attach Procedure / Success / List of equivalent PLMNs in the ATTACH ACCEPT message ... 1155
9.2.1.1.8 Void ............................................................................................................................................ 1159
9.2.1.1.9 Attach / Rejected / IMSI invalid ................................................................................................. 1159
9.2.1.1.10 Attach / Rejected / Illegal ME ..................................................................................................... 1162
9.2.1.1.11 Attach / Rejected / EPS services and non-EPS services not allowed .......................................... 1163
9.2.1.1.12 Attach / Rejected / EPS services not allowed ............................................................................. 1167
9.2.1.1.13 Attach / Rejected / PLMN not allowed ....................................................................................... 1171
9.2.1.1.14 Attach / Rejected / Tracking area not allowed ............................................................................ 1175
9.2.1.1.15 Attach / Rejected / Roaming not allowed in this tracking area ................................................... 1180
9.2.1.1.16 Attach / Rejected / EPS services not allowed in this PLMN ....................................................... 1185
9.2.1.1.17 Attach / Rejected / No suitable cells in tracking area.................................................................. 1188
9.2.1.1.18 Attach / Rejected / Not authorized for this CSG ......................................................................... 1193
9.2.1.1.19 Attach / Abnormal case / Failure due to non integrity protection ............................................... 1197
9.2.1.1.20 Attach / Abnormal case / Access barred because of access class barring or NAS signalling
connection establishment rejected by the network ...................................................................... 1202
9.2.1.1.21 Attach / Abnormal case / Success after several attempts due to no network response ............... 1207
9.2.1.1.22 Attach / Abnormal case / Unsuccessful attach after 5 attempts .................................................. 1209
9.2.1.1.23 Attach / Abnormal case / Repeated rejects for network failures ................................................. 1212
9.2.1.1.24 Attach / Abnormal case / Change of cell into a new tracking area ............................................. 1216
9.2.1.1.25 Attach / Abnormal case / Mobile originated detach required...................................................... 1219
9.2.1.1.26 Attach / Abnormal case / Detach procedure collision ................................................................. 1220
9.2.1.2 Combined attach procedure for EPS services and non-EPS services ............................................... 1223
9.2.1.2.1 Combined attach procedure / Success / EPS and non-EPS services ........................................... 1223
9.2.1.2.1b Combined attach procedure / Success / SMS only ...................................................................... 1229
9.2.1.2.1c Combined attach procedure / Success / EPS and CS Fallback not preferred .............................. 1233
9.2.1.2.2 Combined attach procedure / Success / EPS services only / IMSI unknown in HSS ................. 1236
9.2.1.2.3 Successful combined attach procedure / EPS service only / MSC temporarily not reachable .... 1243
9.2.1.2.4 Successful combined attach procedure / EPS service only / CS domain not available ............... 1251
9.2.1.2.5 Combined attach / Rejected / IMSI invalid ................................................................................. 1258
9.2.1.2.6 Combined attach / Rejected / Illegal ME .................................................................................... 1262
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 11
9.2.1.2.7 Combined attach / Rejected / EPS services and non-EPS services not allowed ......................... 1267
9.2.1.2.8 Combined attach / Rejected / EPS services not allowed ............................................................. 1271
9.2.1.2.9 Combined attach / Rejected / PLMN not allowed ....................................................................... 1273
9.2.1.2.10 Combined attach / Rejected / Tracking area not allowed ............................................................ 1277
9.2.1.2.11 Combined attach / Rejected / Roaming not allowed in this tracking area ................................... 1280
9.2.1.2.12 Combined attach / Rejected / EPS services not allowed in this PLMN ...................................... 1287
9.2.1.2.13 Combined attach / Rejected / No suitable cells in tracking area ................................................. 1291
9.2.1.2.14 Combined attach / Rejected / Not authorized for this CSG ........................................................ 1297
9.2.1.2.15 Combined attach / Abnormal case / Handling of the EPS attach attempt counter ...................... 1300
9.2.2 Detach procedure ................................................................................................................................... 1307
9.2.2.1 UE initiated detach procedure .......................................................................................................... 1307
9.2.2.1.1 UE initiated detach / UE switched off ......................................................................................... 1307
9.2.2.1.2 UE initiated detach / USIM removed from the UE ..................................................................... 1309
9.2.2.1.3 UE initiated detach / EPS capability of the UE is disabled ......................................................... 1311
9.2.2.1.4 Void ............................................................................................................................................ 1313
9.2.2.1.5 Void ............................................................................................................................................ 1313
9.2.2.1.6 UE initiated detach / Abnormal case / Local detach after 5 attempts due to no network
response ...................................................................................................................................... 1313
9.2.2.1.7 UE initiated detach / Abnormal case / Detach procedure collision ............................................. 1316
9.2.2.1.8 UE initiated detach / Abnormal case / Detach and EMM common procedure collision ............. 1317
9.2.2.1.9 UE initiated detach / Abnormal case / Change of cell into a new tracking area ......................... 1320
9.2.2.2 Network initiated detach procedure .................................................................................................. 1323
9.2.2.2.1 NW initiated detach / Re-attach required .................................................................................... 1323
9.2.2.2.2 NW initiated detach / IMSI detach.............................................................................................. 1325
9.2.2.2.3 to 9.2.2.2.13 Void ................................................................................................................................. 1327
9.2.2.2.14 NW initiated detach / Abnormal case / EMM cause not included .............................................. 1327
9.2.3 Tracking area updating procedure (S1 mode only) ................................................................................ 1329
9.2.3.1 Normal and periodic tracking area updating ..................................................................................... 1329
9.2.3.1.1 Normal tracking area update / Accepted ..................................................................................... 1329
9.2.3.1.2 Normal tracking area update / Accepted / "Active" flag set ....................................................... 1332
9.2.3.1.3 Void ............................................................................................................................................ 1336
9.2.3.1.4 Normal tracking area update / List of equivalent PLMNs in the TRACKING AREA
UPDATE ACCEPT message ...................................................................................................... 1336
9.2.3.1.5 Periodic tracking area update / Accepted .................................................................................... 1339
9.2.3.1.6 Normal tracking area update / UE with ISR active moves to E-UTRAN ................................... 1344
9.2.3.1.7 Void ............................................................................................................................................ 1351
9.2.3.1.8 UE receives an indication that the RRC connection was released with cause "load balancing
TAU required" ............................................................................................................................ 1351
9.2.3.1.9a Normal tracking area update / NAS signalling connection recovery .......................................... 1353
9.2.3.1.10 Normal tracking area update / Rejected / IMSI invalid ............................................................... 1355
9.2.3.1.11 Normal tracking area update / Rejected / Illegal ME .................................................................. 1358
9.2.3.1.12 Normal tracking area update / Rejected / EPS service not allowed ............................................ 1359
9.2.3.1.13 Normal tracking area update / Rejected / UE identity cannot be derived by the network ........... 1362
9.2.3.1.14 Normal tracking area update / Rejected / UE implicitly detached .............................................. 1365
9.2.3.1.15 Normal tracking area update / Rejected / PLMN not allowed .................................................... 1366
9.2.3.1.16 Normal tracking area update / Rejected / Tracking area not allowed ......................................... 1371
9.2.3.1.17 Normal tracking area update / Rejected / Roaming not allowed in this tracking area ................ 1376
9.2.3.1.18 Normal tracking area update / Rejected / EPS services not allowed in this PLMN .................... 1380
9.2.3.1.19 Normal tracking area update / Rejected / No suitable cells in tracking Area .............................. 1384
9.2.3.1.20 Void ............................................................................................................................................ 1386
9.2.3.1.21 Void ............................................................................................................................................ 1386
9.2.3.1.22 Void ............................................................................................................................................ 1386
9.2.3.1.23 Normal tracking area update / Abnormal case / Success after several attempts due to no
network response / TA belongs to TAI list and status is UPDATED / TA does not belong to
TAI list or status is not UPDATED ............................................................................................ 1386
9.2.3.1.24 Void ............................................................................................................................................ 1392
9.2.3.1.25 Normal tracking area update / Abnormal case / Failure after 5 attempts due to no network
response ...................................................................................................................................... 1392
9.2.3.1.26 Normal tracking area update / Abnormal case / TRACKING AREA UPDATE REJ ECT ......... 1397
9.2.3.1.27 Normal tracking area update / Abnormal case / Change of cell into a new tracking area ........... 1401
9.2.3.1.28 Normal tracking area update / Abnormal case / Tracking area updating and detach procedure
collision ....................................................................................................................................... 1403
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 12
9.2.3.2 Combined tracking area updating ..................................................................................................... 1404
9.2.3.2.1 Combined tracking area update / Successful............................................................................... 1404
9.2.3.2.1a Combined tracking area update / Successful / Check of last visited TAI and handling of TAI
list, LAI and TMSI ...................................................................................................................... 1410
9.2.3.2.1b Combined tracking area update / Success / SMS only ................................................................ 1419
9.2.3.2.1c Combined tracking area update / Success / CS Fallback not preferred ....................................... 1423
9.2.3.2.2 Combined tracking area update / Successful for EPS services only / IMSI unknown in HSS .... 1426
9.2.3.2.3 Combined tracking area update / Successful for EPS services only / MSC temporarily not
reachable ..................................................................................................................................... 1429
9.2.3.2.4 Combined tracking area update / Successful for EPS services only / CS domain not available . 1433
9.2.3.2.5 Combined tracking area update / Rejected / IMSI invalid .......................................................... 1435
9.2.3.2.6 Combined tracking area update / Rejected / Illegal ME ............................................................. 1437
9.2.3.2.7 Combined tracking area update / Rejected / EPS services and non-EPS services not allowed ... 1439
9.2.3.2.8 Combined tracking area update / Rejected / EPS services not allowed ...................................... 1440
9.2.3.2.9 Combined tracking area update / Rejected / UE identity cannot be derived by the network ...... 1443
9.2.3.2.10 Combined tracking area update / Rejected / UE implicitly detached .......................................... 1447
9.2.3.2.11 Combined tracking area update / Rejected / PLMN not allowed ................................................ 1448
9.2.3.2.12 Combined tracking area update / Rejected / Tracking area not allowed ..................................... 1453
9.2.3.2.13 Combined tracking area update / Rejected / Roaming not allowed in this tracking area ............ 1456
9.2.3.2.14 Combined tracking area update / Rejected / EPS services not allowed in the PLMN ................ 1459
9.2.3.2.15 Combined tracking area update / Rejected / No suitable cells in tracking area .......................... 1463
9.2.3.2.16 Combined tracking area update / Rejected / Not authorized for this CSG .................................. 1465
9.2.3.2.17 Combined tracking area update / Abnormal case / handling of the EPS tracking area updating
attempt counter ........................................................................................................................... 1468
9.2.3.3 Iu mode to S1 mode inter-system change in idle mode .................................................................... 1472
9.2.3.3.1 First Iu mode to S1 mode inter-system change after attach ........................................................ 1472
9.2.3.3.2 Iu mode to S1 mode intersystem change / ISR is active / Expiry of T3312 in E-UTRAN or
T3412 in UTRAN and further intersystem change ..................................................................... 1483
9.2.3.3.3 Void ............................................................................................................................................ 1491
9.2.3.3.4 First S1 mode to Iu mode inter-system change after attach ........................................................ 1491
9.2.3.3.5 Periodic routing area update ....................................................................................................... 1506
9.2.3.3.5a Periodic Location Update ........................................................................................................... 1511
9.2.3.3.6 E-UTRAN RRC connection failure / Reselection of UTRAN cell / NAS signaling to release
old S1 interface connection ......................................................................................................... 1516
9.2.3.4 1518
9.2.3.4.1 TAU/RAU procedure for inter-system cell reselection between A/Gb and S1 modes ............... 1518
9.3 EMM connection management procedures (S1 mode only) ........................................................................ 1530
9.3.1 Service request procedure ...................................................................................................................... 1530
9.3.1.1 Service request initiated by UE for user data ................................................................................... 1530
9.3.1.2 Void .................................................................................................................................................. 1532
9.3.1.3 Service request / Mobile originating CS fallback ............................................................................. 1532
9.3.1.4 Service request / Rejected / IMSI invalid ......................................................................................... 1535
9.3.1.5 Service request / Rejected / Illegal ME ............................................................................................ 1540
9.3.1.6 Service request / Rejected / EPS services not allowed ..................................................................... 1542
9.3.1.7 Service request / Rejected / UE identity cannot be derived by the network ..................................... 1547
9.3.1.7a Service request / Rejected / UE implicitly detached ......................................................................... 1548
9.3.1.8 to 9.3.1.12 Void ............................................................................................................................................ 1550
9.3.1.12a Extended service request / Rejected / CS domain temporarily not available .................................... 1550
9.3.1.13 Void .................................................................................................................................................. 1551
9.3.1.14 Void .................................................................................................................................................. 1551
9.3.1.15 Service request / Abnormal case / Tracking area update procedure is triggered .............................. 1551
9.3.1.16 Service request / Abnormal case / Switch off ................................................................................... 1555
9.3.1.17 Service request / Abnormal case / Procedure collision ..................................................................... 1557
9.3.1.18 Service Request / Rejected / Not authorized for this CSG ............................................................... 1559
9.3.2 Paging procedure .................................................................................................................................... 1562
9.3.2.1 Paging procedure .............................................................................................................................. 1562
9.3.2.2 Paging for CS fallback / Idle mode ................................................................................................... 1563
9.3.2.2a Paging for CS fallback / Connected mode ........................................................................................ 1566
9.4 NAS Security ............................................................................................................................................... 1568
9.4.1 Integrity protection / Correct functionality of EPS NAS integrity algorithm / SNOW3G ..................... 1568
9.4.2 Integrity protection / Correct functionality of EPS NAS integrity algorithm / AES .............................. 1571
9.4.3 Ciphering and deciphering / Correct functionality of EPS NAS encryption algorithm / SNOW3G ...... 1571
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 13
9.4.4 Ciphering and deciphering / Correct functionality of EPS NAS encryption algorithm / AES ............... 1575
10 EPS session management ................................................................................................................... 1576
10.1 Void ............................................................................................................................................................. 1576
10.2 Dedicated EPS bearer context activation ..................................................................................................... 1576
10.2.1 Dedicated EPS bearer context activation / Success ................................................................................ 1576
10.3 EPS bearer context modification ................................................................................................................. 1578
10.3.1 EPS bearer context modification / Success ............................................................................................ 1578
10.4 EPS bearer context deactivation .................................................................................................................. 1581
10.4.1 EPS bearer context deactivation / Success ............................................................................................. 1581
10.5 UE requested PDN connectivity .................................................................................................................. 1594
10.5.1 UE requested PDN connectivity accepted by the network ..................................................................... 1594
10.5.2 Void ........................................................................................................................................................ 1601
10.5.3 UE requested PDN connectivity not accepted ........................................................................................ 1601
10.6 UE requested PDN disconnect ..................................................................................................................... 1606
10.6.1 UE requested PDN disconnect procedure accepted by the network ....................................................... 1606
10.6.2 UE requested PDN disconnect procedure not accepted by the network ................................................. 1609
10.7 UE requested bearer resource allocation ...................................................................................................... 1612
10.7.1 UE requested bearer resource allocation accepted by the network / New EPS bearer context .............. 1612
10.7.2 UE requested bearer resource allocation accepted by the network / Existing EPS bearer context ......... 1614
10.7.3 UE requested bearer resource allocation not accepted by the network .................................................. 1616
10.7.4 UE requested bearer resource allocation / Expiry of timer T3480 ......................................................... 1619
10.7.5 UE requested bearer resource allocation / BEARER RESOURCE ALLOCATION REJECT message
including cause #43 "invalid EPS bearer identity" ................................................................................. 1621
10.8 UE requested bearer resource modification ................................................................................................. 1624
10.8.1 UE requested bearer resource modification accepted by the network / New EPS bearer context .......... 1624
10.8.2 UE requested bearer resource modification accepted by the network / Existing EPS bearer context .... 1626
10.8.3 UE requested bearer resource modification not accepted by the network .............................................. 1628
10.8.4 UE requested bearer resource modification / Cause #36 "regular deactivation" .................................... 1631
10.8.5 UE requested bearer resource modification / BEARER RESOURCE MODIFICATION REJ ECT
message including cause #43 "invalid EPS bearer identity" .................................................................. 1634
10.8.6 UE requested bearer resource modification / Collision of a UE requested bearer resource
modification procedure and EPS bearer context deactivation procedure ............................................... 1637
10.8.7 UE requested bearer resource modification / Expiry of timer T3481 ..................................................... 1639
10.9 UE routing of uplink packets ....................................................................................................................... 1642
10.9.1 UE routing of uplinks packets ................................................................................................................ 1642
11 General tests ......................................................................................................................................... 970
11.1 SMS over SGs ................................................................................................................................................ 970
11.1.1 MT-SMS over SGs / Idle mode ................................................................................................................ 970
11.1.2 MT-SMS over SGs / Active mode ........................................................................................................... 973
11.1.3 MO-SMS over SGs / Idle mode ............................................................................................................... 976
11.1.4 MO-SMS over SGs / Active mode ........................................................................................................... 981
12 E-UTRA radio bearer tests ................................................................................................................... 985
12.1 General ........................................................................................................................................................... 985
12.1.0 Definition of radio bearer combinations .................................................................................................. 985
12.1.1 Generic E-UTRA radio bearer test procedure / MIMO not configured ................................................... 985
12.1.2 Generic E-UTRA radio bearer test procedure / MIMO configured ......................................................... 987
12.2 MIMO not configured .................................................................................................................................... 988
12.2.1 Data transfer of E-UTRA radio bearer combinations 1,3,6 and 9 ............................................................ 988
12.2.2 Data transfer of E-UTRA radio bearer combinations 2,4,7 and 10 .......................................................... 989
12.2.3 Data transfer of E-UTRA radio bearer combinations 5,8,11 and 12 ........................................................ 990
12.2.4 Data transfer of E-UTRA radio bearer combination 13 ........................................................................... 991
12.3 MIMO configured .......................................................................................................................................... 992
12.3.1 Data transfer of E-UTRA radio bearer combinations 1,3,6 and 9 / MIMO .............................................. 992
12.3.2 Data transfer of E-UTRA radio bearer combinations 2,4,7 and 10 / MIMO ............................................ 993
12.3.3 Data transfer of E-UTRA radio bearer combinations 5,8,11 and 12 / MIMO .......................................... 994
12.3.4 Data transfer of E-UTRA radio bearer combination 13 / MIMO ............................................................. 995
13 Multi layer Procedures ......................................................................................................................... 996
13.1 Call setup ....................................................................................................................................................... 996
13.1.1 Activation and deactivation of additional data radio bearer in E-UTRA ................................................. 996
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 14
13.1.2 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection / MO call .............. 1000
13.1.3 Call setup from E-UTRAN RRC_CONNECTED / CS fallback to UTRAN with Redirection / MT
call .......................................................................................................................................................... 1004
13.1.4 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with Handover / MT call ................ 1013
13.1.5 Call setup from E-UTRAN RRC_CONNECTED / CS fallback to UTRAN with handover / MO call . 1021
13.1.6 Void ........................................................................................................................................................ 1024
13.1.7 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with redirection / MT call ...................... 1024
13.1.8 Call setup from E-UTRA RRC_CONNECTED/ CS fallback to GSM with Redirection / MO call ...... 1030
13.1.9 to 13.1.14 Void ............................................................................................................................................ 1037
13.1.15 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection / MT call /
UTRAN cell is barred ............................................................................................................................ 1037
13.2 RRC connection reconfiguration ................................................................................................................. 1041
13.2.1 RRC connection reconfiguration / E-UTRA to E-UTRA ...................................................................... 1041
13.3 ..................................................................................................................................................................... 1045
13.3.1 Intra-system connection re-establishment .............................................................................................. 1045
13.3.1.1 Intra-system connection re-establishment / Radio link recovery while T310 is running .................. 1045
13.3.1.2 Intra-system connection re-establishment / Re-establishment of a new connection when further
data is to be transferred ..................................................................................................................... 1046
13.4 Mobility ....................................................................................................................................................... 1048
13.4.1 Intra-system mobility ............................................................................................................................. 1048
13.4.1.2 Inter-frequency mobility / E-UTRA to E-UTRA packet .................................................................. 1048
13.4.2 Inter-system mobility packet .................................................................................................................. 1052
13.4.2.1 Inter-system mobility / E-UTRA to UTRA packet ........................................................................... 1052
14 ETWS ................................................................................................................................................. 1060
14.1 ETWS reception in RRC_IDLE state / Duplicate detection ........................................................................ 1060
14.2 ETWS reception in RRC_CONNECTED state / Duplicate detection ......................................................... 1068
14.3 ETWS reception in RRC_IDLE state / NITZ timestamp security check ..................................................... 1076
15 Mobility management based on DSMIPv6 (Dual-Stack Mobile IPv6) .............................................. 1083
15.1 Discovery of the home agent via DNS ......................................................................................................... 1083
15.2 Discovery of the Home Agent via DHCP .................................................................................................... 1085
15.3 Void ............................................................................................................................................................. 1088
15.4 Security association establishment with Home Agent reallocation procedure ............................................ 1088
15.5 Security association establishment without home agent reallocation procedure ......................................... 1099
15.6 Registration of a new IPv6 CoA (Binding Update/Acknowledgment procedure in IPv6 network) ............. 1113
15.7 Registration of a new IPv4 CoA (Binding Update/Acknowledgment procedure in IPv4 network) ............. 1116
15.8 Re-registration of IPv6 CoA ........................................................................................................................ 1119
15.9 Re-registration of IPv4 CoA ........................................................................................................................ 1120
15.10 Return to home link ..................................................................................................................................... 1121
15.11 Dual-Stack Mobile IPv6 detach in IPv6 network ........................................................................................ 1123
15.12 Dual-Stack Mobile IPv6 detach in IPv4 network ........................................................................................ 1125
16 Home (e)NB related ........................................................................................................................... 1128
16.1 UE Idle Mode Operations ............................................................................................................................ 1128
16.1.1 Cell Selection and Reselection ............................................................................................................... 1128
16.1.1.1 Inter-RAT Cell reselection from E-UTRA idle non-CSG cell to a UTRA CSG cell ....................... 1128
16.1.1.2 Inter-RAT CSG Cell Reselection from E-UTRA CSG cell to UTRA CSG cell .............................. 1133
Annex A (informative): Change history ....................................................................................................... 1140

Release 9
3GPP
15
3GPP TS 36.523-1 V9.3.0 (2010-12)
Foreword
This Technical Specification 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 8. 3GPP TS
36.523-2 [18] contains a pro-forma for the Implementation Conformance Statement (ICS) and an applicability table,
indicating the release from which each test case is applicable. 3GPP TS 36.523-3 [19] 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 [19].
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 9
3GPP
16
3GPP TS 36.523-1 V9.3.0 (2010-12)
1 Scope
The present document specifies the protocol conformance testing for the 3
rd
Generation E-UTRAN 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 could be found in accompanying specifications:
- the default setting of the test parameters [18];
- the applicability of each test case [19].
A detailed description of the expected sequence of messages could be found in the 3
rd
part of this test specification.
The Implementation Conformance Statement (ICS) pro-forma could be found in the 2
nd
part of the present document.
The present document is valid for UE implemented according to 3GPP Release 8.
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 8 UE, references to 3GPP documents are to version 8.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 34.108: "Common Test Environments for User Equipment (UE) Conformance Testing".
[6] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions".
[7] 3GPP TS 34.123-1: "User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification".
[8] 3GPP TS 34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
Release 9
3GPP
17
3GPP TS 36.523-1 V9.3.0 (2010-12)
[9] 3GPP TS 34.123-3: "User Equipment (UE) conformance specification; Part 3: Abstract Test Suites
(ATS)".
[10] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[11] 3GPP TS 36.302: "Services provided by the physical layer for E-UTRA".
[12] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE)
Procedures in idle mode ".
[13] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE)
Radio Access capabilities ".
[14] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access
Control (MAC) protocol specification".
[15] 3GPP TS 36.322: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link Control
(RLC) protocol specification".
[16] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA) Packet Data
Convergence Protocol (PDCP) specification".
[17] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource
Control (RRC) Protocol Specification".
Terrestrial Radio Access (E-UTRAN); Common Test Environments for User Equipment (UE)
Conformance Testing".
[19] 3GPP TS 36.523-2: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance
specification; Part 2: Implementation Conformance Statement (ICS) proforma specification".
[20] 3GPP TS 36.523-3: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
Universal Terrestrial Radio Access (E-UTRAN); User Equipment (UE) conformance
specification; Part 3: Abstract Test Suites (ATS)".
[21] 3GPP TR 24.801: "3GPP System Architecture Evolution; CT WG1 Aspects".
[22] 3GPP TS 23.401: "3GPP System Architecture Evolution; GPRS enhancements for E-UTRAN
access".
[23] 3GPP TS 51.010-1: "Mobile Station (MS) conformance specification; Part 1: Conformance
specification".
[24] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework".
Terrestrial Radio Access Network (E-UTRAN); Special conformance testing functions for User
Equipment (UE)".
[26] 3GPP TS 33.102: "3G Security; Security architecture"
[27] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[28] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".
[29] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
channel coding".
[30] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures"
Release 9
3GPP
18
3GPP TS 36.523-1 V9.3.0 (2010-12)
[31] 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception
[32] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".
[33] 3GPP2 A.S0008-C: "Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
Radio Access Network Interfaces with Session Control in the Access Network"
[34] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management"
[35] 3GPP TS 34.229-1: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE)
conformance specification; Part 1: Protocol conformance specification ".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
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 given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
ENB Evolved Node B
FDD Frequency Division Duplex
FFS For Further Study
ICS Implementation Conformance Statement
ROHC RObust Header Compression
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 will be provided in [6 or FFS].
Release 9
3GPP
19
3GPP TS 36.523-1 V9.3.0 (2010-12)
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.
4.3 Repetition of tests
As a general rule, the test cases specified in the present document are highly reproducible and don't need to be repeated
unless otherwise stated. However, the rate of correct UE behaviour such as cell re-selection, measurement and handover
is specified statistically, e.g. "at least 90%" [34]. It is the case that for those tests expecting such UE behaviour (stated
above) are not 100% reproducible, therefore if a UE does fail the test after its first trial and the tester suspects the reason
is due to the statistical nature of the test, then the UE should be re-tested one or more times.
5 Reference conditions
The reference environments used by all signalling and protocol tests will be specified in TS 36.508 [18]. 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
will be described in TS 36.508 [18]. These procedures will be used in numerous test cases throughout the present
document.
6 Idle mode operations
6.0 Introduction
6.0.1 PLMN and TAC
The PLMN numbers indicated in Table 6.0.1-1 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.0.1-1: Tracking Area Identity (TAI) in System Information Block Type 1
broadcast on the BCCH (E-UTRAN)
PLMN MCC1 MCC2 MCC3 MNC1 MNC2 MNC3 TAC
1 0 0 1 0 1 Not present See
Table
6.0.1-2
2 0 0 2 1 1 Not present

NOTE: The Location Area Information (LAI) for UTRA and GSM could be re-used from TS 34.123-1 clause 6.
If no TAC for E-UTRAN cell is explicitly specified in the test case description, the TACs for E-UTRAN cells indicated
in Table 6.0.1-2 are used in the test case.
Release 9
3GPP
20
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.0.1-2: Tracking Area Code (TAC) for E-UTRAN cells
cell ID TAC
Cell 1 1
Cell 2 2
Cell 3 3
Cell 4 4
Cell 6 6
Cell 10 10
Cell 11 11
Cell 12 12
Cell 13 13
Cell 14 14

If no RAI for UTRAN cell is explicitly specified in the test case description, the RAI for UTRAN cells indicated in
Table 4.4.4-2 in [18] are used in the test case.
6.0.2 Other
Editors note: Other generic [FFS] information for idle mode testing to be added in this clause is as follows:
- Default values of the system information fields for different methods and IEs specific to idle mode;
- Requirements for FDD and TDD cells (check TS 36.331) in order for the UE to be able to identify a new
detectable cell and camp on it (minimum channel power levels);
- Generic test behaviour in case of combined E-UTRA/UTRA/GSM/HRPD/1xRTT tests: indication of
access technology;
- Test channel numbers used in test cases to associate a cell with a frequency for that cell. If no channel is
explicitly specified, the default value is Test Channel 1. The frequencies and RF signal levels for UTRA
and GSM could be re-used from TS 34.123-1 clause 6. The frequencies and RF signal levels for E-UTRA
test channels shall be based on TS 36.508 clauses 4.3.1.1, 4.3.1.2 and 4.3.4.
6.1 In a pure E-UTRAN environment
6.1.1 PLMN selection
6.1.1.1 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /
Automatic mode
6.1.1.1.1 Test Purpose (TP)
(1)
with { UE i n Aut omat i c net wor k sel ect i on mode and RPLMN, HPLMN, UPLMN and OPLMN E- UTRAN cel l s
avai l abl e and UE i s f i t t ed wi t h a USI M i ndi cat i ng RPLMN shoul d be sel ect ed }
ensure that {
when { UE i s swi t ched on or r et ur n t o cover age }
then { UE sel ect s a cel l of t he RPLMN and UE at t empt s a l ocat i on r egi st r at i on on t he sel ect ed
cel l and when successf ul l y r egi st er ed i ndi cat es t he sel ect ed PLMN t o t he user . }
}

(2)
with { UE camped on an E- UTRAN VPLMN cel l and cel l s of a hi gher pr i or i t y E- UTRAN PLMN avai l abl e }
ensure that {
when { hi gher pr i or i t y PLMN sear ch t i mer T expi r es }
then { UE sel ect s and camps on a cel l of t he hi ghest pr i or i t y PLMN and UE at t empt s a l ocat i on
r egi st r at i on on t he sel ect ed cel l and when successf ul l y r egi st er ed i ndi cat es t he sel ect ed PLMN t o
t he user . }
}

Release 9
3GPP
21
3GPP TS 36.523-1 V9.3.0 (2010-12)
(3)
with { UE i n Aut omat i c net wor k sel ect i on mode and HPLMN, UPLMN and OPLMN E- UTRAN cel l s avai l abl e and
UE i s f i t t ed wi t h a USI M wi t h Access Technol ogy dat a f i l es f or each PLMN and t her e ar e no equi val ent
HPLMNs def i ned}
ensure that {
then { UE sel ect s a cel l of t he hi ghest pr i or i t y PLMN and UE at t empt s a l ocat i on r egi st r at i on on
t he sel ect ed cel l and when successf ul l y r egi st er ed i ndi cat es t he sel ect ed PLMN t o t he user . }
}

6.1.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1,
4.4.3.1.1 and 4.4.3.3.
[TS 23.122, clause 4.4.3.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 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 one of the following two procedures depending on its PLMN selection operating mode. At
switch on, if the MS provides the optional feature of user preferred PLMN selection operating mode at switch on then
this operating mode shall be used.
...
NOTE 1: If successful registration is achieved, then the current serving PLMN becomes the registered PLMN and
the MS does not store the previous registered PLMN for later use.
[TS 23.122, clause 4.4.3.1.1]
The MS selects and attempts registration on other PLMN/access technology combinations, if available and allowable, in
the following order:
i) either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is
available (if the EHPLMN list is present) ;
ii) each PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology"
data file in the SIM (in priority order);
iii) each PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access
Technology" data file in the SIM (in priority order);
iv)
v) ...
When following the above procedure the following requirements apply:
a)
b) ...
Release 9
3GPP
22
3GPP TS 36.523-1 V9.3.0 (2010-12)
c) In ii and iii, the MS should limit its search for the PLMN to the access technology or access technologies
associated with the PLMN in the appropriate PLMN Selector with Access Technology list (User Controlled or
Operator Controlled selector list). An MS using a SIM without access technology information storage (i.e. the
"User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with
Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN
in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of and shall
assume GSM access technology as the highest priority radio access technology.
d) ...
e) ...
f) In i, the MS shall search for all access technologies it is capable of. No priority is defined for the preferred access
technology and the priority is an implementation issue, but "HPLMN Selector with Access Technology" data file
on the SIM may be used to optimise the procedure.
g) ...
h) ...
NOTE 1: ...
NOTE 2: ...
NOTE 3: High quality signal is defined in the appropriate AS specification.
[TS 23.122, clause 4.4.3.3]
If the MS is in a VPLMN, the MS shall periodically attempt to obtain service on its HPLMN (if the EHPLMN list is not
present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a higher priority PLMN/access
technology combinations listed in "user controlled PLMN selector" or "operator controlled PLMN selector" by scanning
in accordance with the requirements that are applicable to i), ii) and iii) as defined in the Automatic Network Selection
Mode in clause 4.4.3.1.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. For this purpose, a value T minutes may be stored in the SIM, T is either in the range 6
minutes to 8 hours in 6 minute steps or it indicates that no periodic attempts shall be made. If no value is stored in the
SIM, a default value of 60 minutes is used.
The attempts to access the HPLMN or an EHPLMN or higher priority PLMN shall be as specified below:
a) The periodic attempts shall only be performed in automatic mode when the MS is roaming;
b) After switch on a period of at least 2 minutes and at most T minutes shall elapse before the first attempt is made;
c) The MS shall make the following attempts if the MS is on the VPLMN at time T after the last attempt;
d) Periodic attempts shall only be performed by the MS while in idle mode;
e) If the HPLMN (if the EHPLMN list is not present or is empty) or a EHPLMN (if the list is present) or a higher
priority PLMN is not found, the MS shall remain on the VPLMN.
f) In steps i), ii) and iii) of subclause 4.4.3.1.1 the MS shall limit its attempts to access higher priority
PLMN/access technology combinations to PLMN/access technology combinations of the same country as the
current serving VPLMN, as defined in Annex B.
g) ...
h) If the PLMN of the highest priority PLMN/access technology combination available is the current VPLMN, or
one of the PLMNs in the "Equivalent PLMNs" list, the MS shall remain on the current PLMN/access technology
combination.
Release 9
3GPP
23
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.1.1.1.3 Test description
6.1.1.1.3.1 Pre-test conditions
System Simulator:
- Four inter-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
default PLMNs as indicated in TS 36.508 Table 4.4.2-2 except that all MCC values are the same as for Cell 1.
- The PLMNs are identified in the test by the identifiers in Table 6.1.1.1.3.1-1.
Table 6.1.1.1.3.11: PLMN identifiers
Cell PLMN name
1 PLMN4
12 PLMN1
13 PLMN2
14 PLMN3

UE:
- The UE is in Automatic PLMN selection mode.
- The UE is registered to PLMN1 before it is switched off.
- The UE is equipped with a USIM containing default values (as per TS 36.508) except for those listed in Table
6.1.1.1.3.1-2.
Table 6.1.1.1.3.12: USIM configuration
USIM field Priority Value Access Technology Identifier
EF
LOCI
PLMN1 (See preamble)
EF
IMSI
The HPLMN (MCC+MNC) of the
IMSI is set to PLMN4.

EF
PLMNwAcT
1
2
3
Default
PLMN3
PLMN2
Remaining mandatory entries use
default values
Default
All specified
E-UTRAN

EF
OPLMNwACT
1 PLMN1
Remaining defined entries use
default values
All specified
EF
HPLMNwAcT
1 PLMN4 E-UTRAN
EF
UST
Services 20, 42, 43 and 74 are
supported. Service 71 is not
supported (there is no EHPLMN
list).

EF
HPPLMN
1 (6 minutes)

Preamble:
- The UE is in state Switched OFF (State 1).
6.1.1.1.3.2 Test procedure sequence
Table 6.1.1.1.3.2 1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configurations marked T1, T2 etc are applied at the points indicated in the Main behaviour
description in Table 6.1.1.1.3.2-2. Cell powers are chosen for a serving cell and a non-suitable Off cell as defined in
TS36.508 Table 6.2.2.1-1.
Release 9
3GPP
24
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.1.1.3.2-1: Cell configuration changes over time
Parameter Unit Cell 1 Cell 12 Cell 13 Cell 14 Remarks
T0 RS EPRE dBm/15kHz Off -85 Off Off Power level Off is
defined in TS36.508
Table 6.2.2.1-1
T1 RS EPRE dBm/15kHz -85 -85 -85 Off Power level Off is
defined in TS36.508
Table 6.2.2.1-1
T2 RS EPRE dBm/15kHz Off -85 -85 Off Power level Off is
defined in TS36.508
Table 6.2.2.1-1
T3 RS EPRE dBm/15kHz Off -85 -85 -85 Power level Off is
defined in TS36.508
Table 6.2.2.1-1

Release 9
3GPP
25
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.1.1.3.2-2: Main behaviour
St Procedure Message Sequence TP Verdict
U - S Message
1 SS adjusts cell levels according to row T1 of
table 6.1.1.1.3.2-1
- - - -
2 Power on the UE. - - - -
3 Check: Does the UE send an
RRCConnectionRequest on Cell 12?
--> RRCConnectionRequest 1 P
4-
18
Steps 3 to 17 of the registration procedure
described in TS 36.508 subclause 4.5.2.3 are
performed on Cell 12.
NOTE: The UE performs registration and the
RRC connection is released.
- - - -
19 Check: Is PLMN1 indicated by the UE? - - 1 P
RRCConnectionRequest on Cell 1 after 120
seconds, but before 360 seconds from power
on?
21-
25
Steps 2 to 6 of the generic test procedure in
TS 36.508 subclause 6.4.2.7 are performed on
Cell 1.
NOTE: The UE performs a TAU procedure and
the RRC connection is released.
- - - -
RRCConnectionRequest within [720
seconds]?
--> RRCConnectionRequest 2 F
table 6.1.1.1.3.2-1
- - - -
29 Check: Does the test result of generic test
procedure in TS 36.508 subclause 6.4.2.7
indicate that the UE is camped on E-UTRAN
Cell 13?
- - 3 -
table 6.1.1.1.3.2-1
- - - -
RRCConnectionRequest on Cell 14 after 360
seconds after step 28?
33-
37
TS 36.508 subclause 6.4.2.7 are performed.
- - - -
RRCConnectionRequest within [720
seconds]?
Note 1: Timers in Steps 20, 27, 32 and 39 are derived from the high priority PLMN search timer T defined by
EF
HPPLMN

6.1.1.1.3.3 Specific message contents
None
Release 9
3GPP
26
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.1.1.2 PLMN selection of "Other PLMN/access technology combinations" /
Automatic mode
(1)
with { UE i n Aut omat i c net wor k sel ect i on mode and EHPLMN, UPLMN, OPLMN and ot her PLMN/ access
t echnol ogy combi nat i ons cel l s avai l abl e and UE i s f i t t ed wi t h a USI M wi t h Access Technol ogy dat a
f i l es f or each PLMN }
ensure that {
then { UE sel ect s a cel l of t he EPLMN and UE at t empt s a l ocat i on r egi st r at i on on t he sel ect ed
}

(2)
with { UE i n Aut omat i c net wor k sel ect i on mode and UPLMN, OPLMN and ot her PLMN/ access t echnol ogy
combi nat i ons cel l s avai l abl e and UE i s f i t t ed wi t h a USI M wi t h Access Technol ogy dat a f i l es f or each
PLMN }
ensure that {
then { UE sel ect s a cel l of t he UPLMN and UE at t empt s a l ocat i on r egi st r at i on on t he sel ect ed
}

(3)
with { UE i n Aut omat i c net wor k sel ect i on mode and OPLMN and ot her PLMN/ access t echnol ogy
combi nat i ons cel l s avai l abl e and UE i s f i t t ed wi t h a USI M wi t h Access Technol ogy dat a f i l es f or each
PLMN }
ensure that {
then { UE sel ect s a cel l of t he OPLMN and UE at t empt s a l ocat i on r egi st r at i on on t he sel ect ed
}

(4)
with { UE i n Aut omat i c net wor k sel ect i on mode and ot her PLMN/ access t echnol ogy combi nat i ons cel l s
not bel ongi ng t o any of EHPLMN, UHPLMN or OPLMN avai l abl e }
ensure that {
then { UE sel ect s a cel l of ot her PLMN/ access t echnol ogy combi nat i ons and UE at t empt s a l ocat i on
r egi st r at i on on t he sel ect ed cel l and when successf ul l y r egi st er ed i ndi cat es t he sel ect ed PLMN t o
t he user . }
}

References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1.1.
[TS 23.122, clause 4.4.3.1.1]
4.4.3.1.1 Automatic Network Selection Mode Procedure
available (if the EHPLMN list is present);
iv) other PLMN/access technology combinations with received high quality signal in random order;
Release 9
3GPP
27
3GPP TS 36.523-1 V9.3.0 (2010-12)
v) other PLMN/access technology combinations in order of decreasing signal quality.
When following the above procedure the following requirements apply:
a) An MS with voice capability shall ignore PLMNs for which the MS has identified at least one GSM COMPACT.
b) In A/Gb mode or GSM COMPACT, an MS with voice capability, or an MS not supporting packet services shall
not search for CPBCCH carriers.
c) In ii and iii, the MS should limit its search for the PLMN to the access technology or access technologies
associated with the PLMN in the appropriate PLMN Selector with Access Technology list (User Controlled or
Operator Controlled selector list).
An MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector
with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are
not present) shall instead use the "PLMN Selector" data file, for each PLMN in the "PLMN Selector" data file,
the MS shall search for all access technologies it is capable of. The priority ordering amongst the access
technologies is implementation dependent.
d) In iv and v, the MS shall search for all access technologies it is capable of, before deciding which PLMN to
select.
e) In ii, and iii, a packet only MS which supports GSM COMPACT, but using a SIM without access technology
information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator
Controlled PLMN Selector with Access Technology" data files are not present) shall instead use the "PLMN
Selector" data file, for each PLMN in the "PLMN Selector" data file, the MS shall search for all access
technologies it is capable of and shall assume GSM COMPACT access technology as the lowest priority radio
access technology.
f) In i, the MS shall search for all access technologies it is capable of. No priority is defined for the preferred access
technology and the priority is an implementation issue, but "HPLMN Selector with Access Technology" data file
on the SIM may be used to optimise the procedure.
g) In i, an MS using a SIM without access technology information storage (i.e. the "HPLMN Selector with Access
Technology" data file is not present) shall search for all access technologies it is capable of. The priority ordering
amongst the access technologies is implementation dependent. A packet only MS which supports GSM
COMPACT using a SIM without access technology information storage shall also assume GSM COMPACT
access technology as the lowest priority radio access technology.
h) In v, 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.
NOTE 1: Requirements a) and b) apply also to requirement d), so a GSM voice capable MS should not search for
GSM COMPACT PLMNs, even if capable of GSM COMPACT.
NOTE 2: Requirements a) and b) apply also to requirement f), so a GSM voice capable MS should not search for
GSM COMPACT PLMNs, even if this is the only access technology on the "HPLMN Selector with
Access Technology" data file on the SIM.
NOTE 3: High quality signal is defined in the appropriate AS specification.
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 any of the lists "forbidden LAs for roaming", "forbidden TAs for roaming",
"forbidden LAs for regional provision of service" or "forbidden TAs for regional provision of service" prevented a
registration attempt, the MS selects the first such PLMN again and enters a limited service state.
Release 9
3GPP
28
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
- Four inter-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
default PLMNs as indicated in TS 36.508 Table 4.4.2-2.
Table 6.1.1.2.3.11: PLMN identifiers
Cell PLMN name
1 PLMN1
12 PLMN2
13 PLMN3
14 PLMN4

UE:
6.1.1.2.3.1-2.
EF
EHPLMN
1 PLMN1
default values
E-UTRAN
EF
PLMNwAcT
1 PLMN2
default values
E-UTRAN

EF
OPLMNwACT
1 PLMN3
default values
E-UTRAN

EF
UST
Services 20, 42 and 71 are
supported.

Preamble:
- The UE is in state Switched OFF (State 1).
Table 6.1.1.2.3.2 1 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configurations marked T1, T2 T3 T4etc are applied at the points indicated in the Main
behaviour description in Table 6.1.1.2.3.2-2. Cell powers are chosen for a serving cell and a non-suitable Off cell as
defined in TS36.508 Table 6.2.2.1-1.
Release 9
3GPP
29
3GPP TS 36.523-1 V9.3.0 (2010-12)
Parameter Unit Cell 1 Cell 12 Cell 13 Cell 14 Remarks
T1 RS EPRE dBm/15kHz -85 -85 -85 Off
T2 RS EPRE dBm/15kHz Off -85 -85 -85 Power level Off is
defined in TS36.508
Table 6.2.2.1-1
T3 RS EPRE dBm/15kHz Off Off -85 -85 Power level Off is
defined in TS36.508
Table 6.2.2.1-1
T4 RS EPRE dBm/15kHz Off Off Off -85 Power level Off is
defined in TS36.508
Table 6.2.2.1-1

U - S Message
1 SS adjusts cell levels according to row T1of
table 6.1.1.2.3.2-1
- - - -
4-
18
- - - -
19 Check: Is PLMN1 indicated by the UE?(FFS) - - 1 P
table 6.1.1.2.3.2-1
- - - -
22-
26
Cell 12.
- - - -
27 Check: Is PLMN2 indicated by the UE? (FFS) - - 2 P
table 6.1.1.2.3.2-1
- - - -
30-
34
Cell 13.
- - - -
table 6.1.1.2.3.2-1
- - - -
38-
41
Cell 14.
NOTE: The UE performs a TAU procedure.
- - - -

None
Release 9
3GPP
30
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.1.1.3 Void
6.1.1.4 PLMN selection in shared network environment / Automatic mode
(1)
with { t he UE i s i n aut omat i c net wor k sel ect i on mode and t her e i s a sui t abl e cel l wi t h mul t i pl e PLMN
i dent i t i es among whi ch t he HPLMN but not t he r egi st er ed PLMN }
ensure that {
when { t he UE i s swi t ched on }
then { t he UE at t aches t o t he HPLMN on t he shar ed cel l }
}

(2)
with { t he UE i n aut omat i c net wor k sel ect i on mode and t her e i s a sui t abl e cel l wi t h mul t i pl e PLMN
i dent i t i es among whi ch t he r egi st er ed PLMN }
ensure that {
when { t he UE r et ur ns t o cover age }
then { t he UE per f or ms a l ocat i on r egi st r at i on t o t he r egi st er ed PLMN on t he shar ed cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 5.1.2.2, TS
23.122 clauses 4.4.3 and 4.4.3.1.1, TS 24.301 clauses 5.5.1.1 and 5.5.3.1, and TS 36.331 clause 5.3.3.4.
[TS 36.304 clause 5.1.2.2]
The UE shall scan all RF channels in the E-UTRA bands according to its capabilities to find available PLMNs. On each
carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN(s)
the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN (see the
PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value),

Once the UE has selected a PLMN, the cell selection procedure shall be performed in order to select a suitable cell of
that PLMN to camp on.
[TS 23.122 clause 4.4.3]
When the MS reselects to a cell in a shared network, the AS may indicate multiple PLMN identities to the NAS
according to 3GPP TS 25.304 [32]. The MS shall choose one of these PLMNs. If the registered PLMN is available
among these PLMNs, the MS shall not choose a different PLMN.
[TS 23.122 clause 4.4.3.1.1]
[TS 24.301 clause 5.5.1.1]
...
Release 9
3GPP
31
3GPP TS 36.523-1 V9.3.0 (2010-12)
In a shared network, the UE shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [6]. The UE shall
construct the TAI of the cell from this chosen PLMN identity and the TAC received as part of the broadcast system
information. The chosen PLMN identity shall be indicated to the E-UTRAN (see 3GPP TS 36.331 [22]).
...
[TS 24.301 clause 5.5.3.1]
...
In a shared network, the UE shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [6]. The UE shall
construct the TAI of the cell from this chosen PLMN identity and the TAC received on the broadcast system
information. The chosen PLMN identity shall be indicated to the E-UTRAN (see 3GPP TS 36.331 [22]).
...
[TS 36.331 clause 5.3.3.4]
The UE shall:
...
1>set the content of RRCConnectionSetupComplete message as follows:
2>set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35])
from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;
...
2>submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the
procedure ends;
System Simulator:
- Cells 12 and 13, as specified in TS36.508 clause 4.4.1.2 are configured according to Table 4.4.2-2 in [18] except
for multiple broadcasted PLMN identities as shown in Table 6.1.1.4.3.1. Table 6.1.1.4.3.11: PLMN identifiers
broadcasted by cells in shared network
Cell PLMN names
12 PLMN15, PLMN1
13 PLMN15, PLMN1, PLMN16

UE:
6.1.1.4.3.1-2.
EF
LOCI
PLMN4 (MCC1/MNC4)
EF
PLMNwAcT
Empty
EF
IMSI

EF
UST
Service 74 is supported.
EF
LRPLMNSI
00

Release 9
3GPP
32
3GPP TS 36.523-1 V9.3.0 (2010-12)
Preamble:
- The UE is in state Switched OFF (state 1) according to [18].
Table 6.1.2.10.3.21 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configuration marked T1is applied at the points indicated in the Main behaviour description in
Table 6.1.2.10.3.2-2. Cell powers are chosen for a serving cell and a non-suitable cell as defined in TS36.508 Table
6.2.2.1-1.
Parameter Unit Cell 12 Cell 13 Remarks
T0 RS EPRE dBm/15kHz -85 Off The power level values are assigned to such that
camping on Cell 12 is guaranteed. Cell 13 is off.
T1 RS EPRE dBm/15kHz Off -85 Cell 12 becomes off. UE shall select Cell 13.

U - S Message
1 The SS adjusts cell levels according to row T0
of table 6.1.1.4.3.2-1
- - - -
3 Check: Does the UE transmits an
4 The SS transmits an RRCConnectionSetup <-- RRCConnectionSetup - -
5 Check; Does the UE transmit an
RRCConnectionSetupComplete message
indicating the HPLMN (second PLMN in the
list)?
Note: this message contains an ATTACH
REQUEST and a PDN CONNECTIVITY
REQUEST message according to default
message contents.
--> RRCConnectionSetupComplete 1 P
6 -
18
- - - -
20 The SS adjusts cell levels according to row T1
of table 6.1.1.4.3.2-1
- - - -
21 Check: Does the UE transmit an
22 -
26
- - - -
27 Check: Is the same PLMN as indicated by UE
in step 4 again indicated by the UE?
- - 2 P

Release 9
3GPP
33
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.1.4.3.3-1: RRCConnectionSetupComplete (step 5, Table 6.1.1.4.3.2-2)
Derivation Path: 36.508, Table 4.6.1-18
Information Element Value/remark Comment Condition
RRCConnectionSetupComplete ::=SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionSetupComplete-r8 SEQUENCE {
selectedPLMN-Identity 2 PLMN1
}
}
}
}

6.1.1.5 Void
6.1.1.6 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /
Automatic mode / User reselection
(1)
with { UE i n Aut omat i c net wor k sel ect i on mode r egi st er ed t o UPLMN and RPLMN, UPLMN and OPLMN E- UTRAN
cel l s avai l abl e }
ensure that {
when { UE i s r equest ed t o i ni t i at e r esel ect i on and r egi st r at i on ont o an avai l abl e PLMN }
then { UE r esel ect s t o t he cel l whi ch bel ongs t o hi gher pr i or i t y OPLMN }
}

(2)
with { UE i n Aut omat i c net wor k sel ect i on mode r egi st er ed t o OPLMN and onl y RPLMN E- UTRAN cel l
avai l abl e }
ensure that {
then { UE r emai ns on t he cur r ent cel l whi ch bel ongs t o RPLMN. }
}

(3)
with { UE i n Aut omat i c net wor k sel ect i on mode r egi st er ed t o OPLMN and RPLMN, UPLMN and OPLMN E- UTRAN
cel l s avai l abl e }
ensure that {
then { UE r esel ect s t o t he cel l whi ch bel ongs t o UPLMN }
}

(4)
with { UE i n Aut omat i c net wor k sel ect i on mode r egi st er ed t o UPLMN and RPLMN, UPLMN, OPLMN and HPLMN
E- UTRAN cel l s avai l abl e }
ensure that {
then { UE r esel ect s t o t he cel l whi ch bel ongs t o HPLMN }
}

References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause 4.4.3.2 and
4.4.3.2.1.
[TS 23.122, clause 4.4.3.2]
Release 9
3GPP
34
3GPP TS 36.523-1 V9.3.0 (2010-12)
At any time the user may request the MS to initiate reselection and registration onto an available PLMN, according to
the following procedures, dependent upon the operating mode.
[TS 23.122, clause 4.4.3.2.1]
The MS selects and attempts registration on PLMNs, if available and allowable, in all of its bands of operation in
accordance with the following order:
i) the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if
the EHPLMN list is present);
ii) PLMN/access technology combinations contained in the "User Controlled PLMN Selector with Access
Technology" data file in the SIM (in priority order) excluding the previously selected PLMN/access technology
combination;
iii) PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access
Technology" data file in the SIM (in priority order) excluding the previously selected PLMN/access technology
combination;
iv) other PLMN/access technology combinations with the received high quality signal in random order excluding
the previously selected PLMN/access technology combination;
v) other PLMN/access technology combinations, excluding the previously selected PLMN/access technology
combination in order of decreasing signal quality or, alternatively, the previously selected PLMN/access
technology combination may be chosen ignoring its signal quality;
vi) The previously selected PLMN/access technology combination.
The previously selected PLMN/access technology combination is the PLMN/access technology combination which the
MS has selected prior to the start of the user reselection procedure.
NOTE 1: If the previously selected PLMN is chosen, and registration has not been attempted on any other PLMNs,
then the MS is already registered on the PLMN, and so registration is not necessary.
The equivalent PLMNs list shall not be applied to the user reselection in Automatic Network Selection Mode.
System Simulator:
- Three inter-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
default NAS parameters as indicated in TS 36.508 Table 4.4.2-2.
Table 6.1.1.6.3.1-1: PLMN identifiers
Cell PLMN name
1 PLMN1
12 PLMN2
13 PLMN3
14 PLMN4

UE:
6.1.1.6.3.1-2.
Release 9
3GPP
35
3GPP TS 36.523-1 V9.3.0 (2010-12)
EF
LOCI
PLMN1
EF
IMSI

EF
PLMNwAcT
1 PLMN1
default values
E-UTRAN
EF
OPLMNwACT
1
2
PLMN2
PLMN4
default values
E-UTRAN
E-UTRAN
EF
HPLMNwAcT
1 PLMN3 E-UTRAN
EF
UST
Service 71 is not supported

Preamble:
- The UE is in state Registered, Idle Mode (State 2) on Cell 1 according to [18].
Table 6.1.1.6.3.2-1: Time instances of cell power level and parameter changes
Parameter Unit Cell 1 Cell 12 Cell 13 Cell 14 Remark
T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 -85 "Off" -85
The power level values are
assigned to satisfy R
Cell 1
=R
Cell 12
=
R
Cell 14
.
(NOTE 1).
T2
Cell-specific RS
EPRE
dBm/15
kHz
"Off" -85 "Off" "Off"
Only Cell 12 is available.
(NOTE 1).
T3
Cell-specific RS
EPRE
dBm/15
kHz
-85 "Off" -85 -85
Cell 1
=R
Cell 13
=
R
Cell 14
.
(NOTE 1).
NOTE 1: Power level Off is defined in TS36.508 Table 6.2.2.1-1.

Release 9
3GPP
36
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 The SS changes the power level setting
according to the row T1 in table 6.1.1.6.3.2-1
- - - -
2 Cause the UE in Automatic network selection
mode to initiate reselection and registration
onto an available PLMN. (see Note)
- - - -
4-8 Steps 2 to 6 of the generic test procedure in
Cell 12.
- - - -
9 Check: Is PLMN 2 indicated by the UE? - - 1 P
according to the row T2 in table 6.1.1.6.3.2-1.
- - - -
- - - -
RRCConnectionRequest on Cell 12 within 30
s?
- - - -
- - - -
17-
21
Cell 1.
- - - -
- - - -
- - - -
26-
30
Cell 13.
- - - -
Note: The request is assumed to be triggered by AT command +COPS.

None
Release 9
3GPP
37
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.1.2 Cell selection and reselection
6.1.2.1 Void
6.1.2.2 Cell selection / Qrxlevmin
(1)
with { UE i n E- UTRA RRC_I DLE st at e }
ensure that {
when { a cel l f ul f i l s al l r equi r ement s f or a sui t abl e cel l except t he cel l sel ect i on cr i t er i a
whi ch ar e not f ul f i l l ed ( S<0) }
then { t he UE does not consi der t he cel l sui t abl e and no campi ng on t hi s cel l can t ake pl ace }
}

(2)
ensure that {
when { a cel l f ul f i l s al l r equi r ement s f or a sui t abl e cel l i ncl udi ng t he cel l sel ect i on cr i t er i a
f or a cel l whi ch ar e al so f ul f i l l ed ( S>0) }
then { t he UE consi der s t he cel l sui t abl e and camps on i t }
}

References: The conformance requirements covered in the current TC are specified in: TS36.300, clause 10.1.1.1 and
TS 36.304, clause 4.1, 5.1.2.2, 5.2.3.1, 5.2.3.2 and 5.2.8.
[TS 36.300, clause 10.1.1.1]
Cell selection:
- The UE NAS identifies a selected PLMN and equivalent PLMNs;
- The UE searches the E-UTRA frequency bands and for each carrier frequency identifies the strongest cell. It
reads cell system information broadcast to identify its PLMN(s):
- The UE may search each carrier in turn ("initial cell selection") or make use of stored information to shorten
the search ("stored information cell selection").
- The UE seeks to identify a suitable cell; if it is not able to identify a suitable cell it seeks to identify an
acceptable cell. When a suitable cell is found or if only an acceptable cell is found it camps on that cell and
commence the cell reselection procedure:
- A suitable cell is one for which the measured cell attributes satisfy the cell selection criteria; the cell PLMN
is the selected PLMN, registered or an equivalent PLMN; the cell is not barred or reserved and the cell is not
part of a tracking area which is in the list of "forbidden tracking areas for roaming";
- An acceptable cell is one for which the measured cell attributes satisfy the cell selection criteria and the cell
is not barred;
[TS 36.304, clause 4.1]
When a UE is switched on, a public land mobile network (PLMN) is selected by NAS. For the selected PLMN,
associated RAT(s) may be set [5]. The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use
for cell selection and cell reselection.
With the cell selection, the UE searches for a suitable cell of the selected PLMN and chooses that cell to provide
available services, further the UE shall tune to its control channel. This choosing is known as "camping on the cell".
The UE will, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of
the chosen cell and as outcome of a successful Location Registration the selected PLMN becomes the registered PLMN
[5].
Release 9
3GPP
38
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 36.304, clause 5.1.2.2]
The UE shall scan all RF channels in the E-UTRA bands according to its capabilities to find available PLMNs. On each
carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN(s)
the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN (see the
PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value), provided
that the following high quality criterion is fulfilled:
1. For an E-UTRAN cell, the measured RSRP value shall be greater than or equal to -110 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 RSRP value. The quality measure reported by the UE to NAS shall
be the same for each PLMN found in one cell.
...
Once the UE has selected a PLMN, the cell selection procedure shall be performed in order to select a suitable cell of
that PLMN to camp on.
[TS 36.304, clause 5.2.3.1]
The UE shall use one of the following two cell selection procedures:
a) Initial Cell Selection
This procedure requires no prior knowledge of which RF channels are E-UTRA carriers. The UE shall scan all
RF channels in the E-UTRA bands according to its capabilities to find a suitable cell. On each carrier frequency,
the UE need only search for the strongest cell. Once a suitable cell is found this cell shall be selected.
[TS 36.304, clause 5.2.3.2]
The cell selection criterion S is fulfilled when:

Srxlev >0

Where:

Srxlev =Q
rxlevmeas
(Q
rxlevmin
+Q
rxlevminoffset
) - Pcompensation

Where:
the signalled value QrxlevminOffset is only applied when a cell is evaluated for cell selection as a result of a periodic
search for a higher priority PLMN while camped normally in a VPLMN [5]. During this periodic search for higher
priority PLMN the UE may check the S criteria of a cell using parameter values stored from a different cell of this
higher priority PLMN.
Srxlev Cell Selection RX level value (dB)
Q
rxlevmeas
Measured cell RX level value (RSRP).
Q
rxlevmin
Minimum required RX level in the cell (dBm)
Q
rxlevminoffset
Offset to the signalled Q
rxlevmin
taken into account in the Srxlev evaluation as a
result of a periodic search for a higher priority PLMN while camped normally in
a VPLMN [5]
Pcompensation max(P
EMAX
P
UMAX
, 0) (dB)
P
EMAX
Maximum TX power level an UE may use when transmitting on the uplink in
the cell (dBm) defined as P
EMAX
in [TS 36.101]
P
UMAX
Maximum RF output power of the UE (dBm) according to the UE power class
as defined in [TS 36.101]

[TS 36.304, clause 5.2.8]
Release 9
3GPP
39
3GPP TS 36.523-1 V9.3.0 (2010-12)
In this state, the UE shall attempt to find an acceptable cell of any PLMN to camp on, trying all RATs that are
supported by the UE and searching first for a high quality cell, as defined in subclause 5.1.2.2.
The UE, which is not camped on any cell, shall stay in this state until an acceptable cell is found.
System Simulator:
- Cell 1
UE:
- None.
Preamble:
Table 6.1.2.2.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cell at
various time instants of the test execution.The exact instants on which these values shall be applied are described in the
texts in this clause. Configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour
description in Table 6.1.2.2.3.2-2
Parameter Unit Cell 1 Remark
T1 Cell-specific RS
EPRE
dBm/
15kH
z
-95 The power level value is such to satisfy SrxlevCell 1 <0 but the UE is
able to read the PLMN identity
Qrxlevmin dBm -84
Qrxlevminoffset dB 0
Pcompensation dB 0
T2 Cell-specific RS
EPRE
dBm/
15kH
z
-75 The power level is such that SrxlevCell 1 >0
Note: The downlink signal level uncertainty is specified in TS 36.508 section 4.3.4.1

U - S Message
0A SS re-adjusts the cell-specific reference signal
level of Cell 1 according to row "T1" in table
6.1.2.2.3.2-1.
- - - -
0B Wait for 1.1* modification period to allow the
new system information to take effect.
- - - -
1 The UE is switched on. - - - -
RRCConnectionRequest on Cell 1 within the
next 60 s?
3 SS re-adjusts the cell-specific reference signal
level of Cell 1 level according to row "T2" in
table 6.1.2.2.3.2-1.
- - - -
5-
19
- - - -

Release 9
3GPP
40
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.2.3.3-1: SystemInformationBlockType1 for cell 1 (all steps)
Derivation Path: 36.508 clause 4.4.3.2
Information Element Value/Remark Comment Condition
SystemInformationBlockType1 ::=SEQUENCE {
cellSelectionInfo SEQUENCE {
q-RxLevMin -42 (-84 dBm)
}
}

6.1.2.3 Cell selection / Intra E-UTRAN / Serving cell becomes non-suitable (S<0 or
barred)
(1)
ensure that {
when { t he ser vi ng cel l becomes non- sui t abl e ( S<0) and t her e i s a sui t abl e nei ghbour cel l ( S>0) }
then { UE sel ect s t he sui t abl e nei ghbour gh cel l }
}

(2)
ensure that {
when { t he ser vi ng cel l becomes bar r ed and t her e i s a sui t abl e nei ghbour cel l }
then { UE sel ect s t he sui t abl e nei ghbour gh cel l }
}

TS 36.304, clause 4.1, 5.2.1, 5.2.3.2, 5.2.4.6 and 5.3.1.
[TS 36.300, clause 10.1.1.1]
Cell selection:
is not barred;
[TS 36.304, clause 4.1]
Release 9
3GPP
41
3GPP TS 36.523-1 V9.3.0 (2010-12)
[5].
If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it.
If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is
performed.
[TS 36.304, clause 5.2.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.
[TS 36.304, clause 5.2.3.2]

Srxlev >0

Where:

Srxlev =Q
rxlevmeas
(Qrxlevmin Qrxlevminoffset) - Pcompensation

Where:
Q
rxlevmeas
Q
rxlevmin
Q
rxlevminoffset
rxlevmin
taken into account in the Srxlev
evaluation as a result of a periodic search for a higher priority PLMN
while camped normally in a VPLMN [5]
Pcompensation max(P
EMAX
P
UMAX
, 0) (dB)
P
EMAX
Maximum TX power level an UE may use when transmitting on the
uplink in the cell (dBm) defined as P
EMAX
in [TS 36.101]
P
UMAX
Maximum RF output power of the UE (dBm) according to the UE
power class as defined in [TS 36.101]

[TS 36.304, clause 5.2.4.6]
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
- the new cell is better ranked than the serving cell during a time interval Treselection
RAT
;
- more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 36.304, clause 5.3.1]
Cell status and cell reservations are indicated in the SystemInformationBlockType1 [3] by means of two Information
Elements:
- cellBarred (IE type: "barred" or "not barred")
In case of multiple PLMNs indicated in SIB1 sharing, this IE is common for all PLMNs
...
When cell status is indicated as "not barred" and "not reserved" for operator use,
Release 9
3GPP
42
3GPP TS 36.523-1 V9.3.0 (2010-12)
- All UEs shall treat this cell as candidate during the cell selection and cell re-selection procedures.
...
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
- 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 cell is a CSG cell:
- the UE may select another cell on the same frequency if the selection/reselection criteria are fulfilled.
- else
- If the IE intraFreqReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to
"allowed", the UE may select another cell on the same frequency if re-selection criteria are fulfilled.
- The UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.
- If the IE intraFreqReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to "not
allowed" the UE shall not re-select a cell on the same frequency as the barred cell.
- The UE shall exclude the barred cell and the cells on the same frequency as a candidate for cell
selection/reselection for 300 seconds.
System Simulator:
- Cell 1 and Cell 2 have different tracking areas according to table 6.0.1-2.
UE:
None.
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell 1(serving cell) according to [18].
Table 6.1.2.3.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
various time instants of the test execution. The exact instants on which these values shall be applied are described in the
texts in this clause. Configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour
description in Table 6.1.2.3.3.2-2.
Parameter Unit Cell 1 Cell 2 Remark
T1
Cell-specific RS EPRE
dBm/
15kH
z
"Off" -85
Srxlev
Cell 1
<0 (NOTE 1)
Srxlev* dB - 25 Cell 2 becomes the strongest cell
T2
Cell-specific RS EPRE dBm/
15kH
z
-91 -85 Srxlev
Cell 2
>0, Srxlev
Cell 1
>0 , R
Cell 1
<R
Cell 2

Srxlev* dB 19 25 Cell 1 becomes suitable
cellBarred - notBarred barred Serving cell becomes barred

Release 9
3GPP
43
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
level of Cell 1 and Cell 2 according to row "T1"
in table 6.1.2.3.3.2-1.
- - - -
Cell 2?
- - 1 -
3 SS changes Cell 1 signal level and SIB1 IE
cellBarred according to row "T2" in table
6.1.2.3.3.2-1 and transmits a Paging message
including systemInfoModification. The
systemInfoValueTag in the
SystemInformationBlockType1 is increased.
<-- Paging - -
Cell 1?
- - 2 -

Table 6.1.2.3.3.3-1: Void
Table 6.1.2.3.3.3-2: SystemInformationBlockType1 for cells 1 and 2 (preamble and all steps, Table
6.1.2.3.3.2-2)
}
systemInfoValueTag The value is increased in
step 3

}

Table 6.1.2.3.3.3-3: SystemInformationBlockType3 for cells 1 and 2 (Preamble and all steps, table
6.1.2.3.3.2-2)
Derivation Path: 36.508 clause 4.4.3.3, Table 4.4.3.3-2
cellReselectionInfoCommon SEQUENCE {
q-Hyst dB0
}
intraFreqCellReselectionInfo SEQUENCE {
t-ReselectionEUTRA 7
}
}

Release 9
3GPP
44
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.3.3.3-4: SystemInformationBlockType1 for cell 2 (step 3, Table 6.1.2.3.3.2-2)
cellAccessRelatedInfo SEQUENCE {
cellBarred barred
intraFreqReselection allowed
}
systemInfoValueTag 1 Previous value is
0

}

Table 6.1.2.3.3.3-5: Paging (step 3, Table 6.1.2.3.3.2-2)
Derivation path: 36.508 Table 4.6.1-7
Paging ::=SEQUENCE {
pagingRecordList Not present
systemInfoModification True
etws-PrimaryNotificationIndication Not present
nonCriticalExtension SEQUENCE {} Not present
}

6.1.2.4 Cell reselection
(1)
ensure that {
when { UE det ect s t he cel l r anked as t he best cel l }
then { UE r esel ect s t he new cel l }
}

5.2.4.6.
[TS 36.304, clause 5.2.4.2]
When evaluating for reselection purposes cell selection criterion or SnonServingCell,x, the UE shall use parameters
provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
- If S
intrasearch
is sent in the serving cell and S
ServingCell
>S
intrasearch
, UE may choose to not perform intra-frequency
measurements.
- If S
ServingCell
<=S
intrasearch
, or S
intrasearch
is not sent in the serving cell UE shall perform intra-frequency
measurements.
- The UE shall apply the following rules for E-UTRAN inter-frequencies and inter-RAT frequencies which are
indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:
- For an E-UTRAN inter-frequency or inter-RAT frequency with a reselection priority higher than the
reselection priority of the current E-UTRA frequency the UE shall perform measurements of higher priority
E-UTRAN inter-frequency inter-RAT frequencies according to [10].
- For an E-UTRAN inter-frequency with an equal or lower reselection priority than the reselection priority of
the current E-UTRA frequency and for inter-RAT frequency with lower reselection priority than the
reselection priority of the current E-UTRAN frequency:
Release 9
3GPP
45
3GPP TS 36.523-1 V9.3.0 (2010-12)
- If S
nonintrasearch
ServingCell
>S
nonintrasearch
UE may choose not to perform
measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority.
- If S
ServingCell
<=S
nonintrasearch
or S
nonintrasearch
is not sent in the serving cell the UE shall perform
measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower priority
according to [10].
Where S
ServingCell
is the Srxlev-value of the serving cell.
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:

R
s
=Q
meas
,
s
+Qhyst
s

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
RSRP measurement quantity used in cell reselections.
Qoffset For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid,
otherwise this equals to zero.
For inter-frequency: Equals to Qoffset
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
is valid, otherwise this equals to Qoffset
frequency
.

The UE shall perform ranking of all cells that fulfill the cell selection criterion S, which is defined in 5.2.3.2, but may
exclude all CSG cells that are known by the UE to be not allowed.
The cells shall be ranked according to the R criteria specified above, deriving Q
meas,n
and Q
meas,s
and calculating the R
values using averaged RSRP results.
If a cell is ranked as the best cell the UE shall perform cell re-selection to that cell. If this cell is found to be not-
suitable, the UE shall behave according to subclause 5.2.4.4.
RAT

System Simulator:
- Cell 1 and Cell 2.
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) on Cell 1(serving cell) according to [18].
various time instants of the test execution. The configuration marked "T1" is applied at the point indicated in the Main
behaviour description in Table 6.1.2.4.3.2-2.
Release 9
3GPP
46
3GPP TS 36.523-1 V9.3.0 (2010-12)
T1 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 -79 The power level values are assigned to
satisfy R
Cell 1
<R
Cell 2.

U - S Message
1 The SS changes Cell 2 level according to the
row "T1" in table 6.1.2.4.3.2-1.
- - - -
Cell 2?
- - 1 -

Table 6.1.2.4.3.3-1: Void
6.1.2.5 Cell reselection for interband operation
(1)
ensure that {
when { UE det ect s t he cel l r e- sel ect i on cr i t er i a ar e met f or t he cel l on t he di f f er ent f r equency
band }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.1,
5.2.4.2 and 5.2.4.5.
[TS 36.304, clause 5.2.4.1]
Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the
system information, in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell
(re)selection. In the case of system information, an E-UTRAN frequency or inter-RAT frequency may be listed without
providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in
dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any
cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves
priorities provided by dedicated signalling unless specified otherwise. When the UE in camped normally state, has only
dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest
priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG
cell, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight
network configured values), irrespective of any other priority value allocated to this frequency. The UE shall delete
priorities provided by dedicated signalling when:
- the UE enters RRC_CONNECTED state; or
- the optional validity time of dedicated priorities (T320) expires; or
- a PLMN selection is performed on request by NAS [5].
NOTE: Equal priorities between RATs are not supported.
The UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are
given in system information and for which the UE has a priority provided.
Release 9
3GPP
47
3GPP TS 36.523-1 V9.3.0 (2010-12)
The UE shall not consider any black listed cells as candidate for cell reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e., T320 in E-
UTRA, T322 in UTRA and T3230 in GERAN), if configured, at inter-RAT cell (re)selection.
NOTE: The network may assign dedicated cell reselection priorities for frequencies not configured by system
information.
[TS 36.304, clause 5.2.4.2]
- If S
intrasearch
ServingCell
>S
intrasearch
measurements.
- If S
ServingCell
<=S
intrasearch
, or S
intrasearch
measurements.
E-UTRAN inter-frequency or inter-RAT frequencies according to [10].
- If S
nonintrasearch
ServingCell
>S
nonintrasearch
- If S
ServingCell
<=S
nonintrasearch
or S
nonintrasearch
according to [10].
Where S
ServingCell
[TS 36.304, clause 5.2.4.5]
Criteria 1: the S
nonServingCell,x
of a cell on evaluated frequency is greater than Thresh
x, high
during a time interval
Treselection
RAT
;
Cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than serving frequency shall
be performed if:
- A cell of a higher priority E-UTRAN frequency or inter-RAT frequency fulfils criteria 1; and
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based on ranking for Intra-frequency cell
reselection as defined in sub-clause 5.2.4.6.
Cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than serving frequency shall
be performed if:
- No cell on a higher priority E-UTRAN frequency or inter-RAT frequency than serving frequency fulfills the
criteria 1; and
- No cell on serving frequency or on an equal priority E-UTRAN frequency fulfills the criteria in 5.2.4.6; and
- S
ServingCell
<Threshs
erving, low
and the S
nonServingCell,x
of a cell of a lower priority E-UTRAN frequency or inter-RAT
frequency is greater than Thresh
x, low
during a time interval Treselection
RAT
; and
Release 9
3GPP
48
3GPP TS 36.523-1 V9.3.0 (2010-12)
For GERAN, UTRAN, and E-UTRAN, S
nonServingCell,x
is the Srxlev-value of an evaluated cell. For UTRAN FDD, Squal
is higher than 0, as defined in [8]. For cdma2000 RATs, S
nonServingCell,x
is equal to FLOOR(-2 x 10 x log10 Ec/Io) in units
of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, Threshx, high and Threshx, low are equal to -1 times the values signalled for the corresponding
parameters in the system information.
In all the above criteria the value of Treselection
RAT
is scaled when the UE is in the medium or high mobility state as
defined in subclause 5.2.4.3.1. If more than one cell meets the above criteria, the UE shall reselect a cell ranked as the
best cell among the cells meeting the criteria on the highest priority frequencies or the highest priority RAT if the
highest priority RAT is E-UTRA according to criteria defined in 5.2.4.6.
System Simulator:
- Cell 1, Cell 3 and Cell 10.
- System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) on Cell 1 (serving cell) according to [18].
various time instants of the test execution.The configuration marked "T1" is applied at the point indicated in the Main
Parameter Unit Cell 1 Cell 3 Cell 10 Remark
T1 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 -73 -73 Cell 3 and Cell 10 become stronger than
Thresh
x, high.

U - S Message
1 The SS changes Cell 3 and Cell 10 power
level according to the row "T1" in table
6.1.2.5.3.2-1.
- - - -
Cell 10?
- - 1 -

Release 9
3GPP
49
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.5.3.3-0: Conditions for specific message contents
in Tables 6.1.2.5.3.3-1 and 6.1.2.5.3.3-2
Condition Explanation
Cell 1 This condition applies to system information transmitted on Cell 1.

Table 6.1.2.5.3.3-1: SystemInformationBlockType3 for Cell 1, Cell 3 and Cell 10 (preamble and all
steps, Table 6.1.2.5.3.2-2)
Derivation path: 36.508 table 4.4.3.3-2
cellReselectionServingFreqInfo SEQUENCE {
cellReselectionPriority 1 Cell 1
3 Cell 3
5 Cell 10
}
}

Table 6.1.2.5.3.3-2: SystemInformationBlockType5 for Cell 1, Cell 3 and Cell 10 (preamble and all
steps, Table 6.1.2.5.3.2-2)
interFreqCarrierFreqList SEQUENCE (SIZE
(1..maxFreq)) OF SEQUENCE {

dl-CarrierFreq[n] Same downlink EARFCN
as used for Cell 3
Cell 1
Same downlink EARFCN
as used for Cell 1
Cell 3,
Cell 10
threshX-High[n] 10 20dB
cellReselectionPriority[n] 3 Cell 1
1 Cell 3,
Cell 10
dl-CarrierFreq[m] Same downlink EARFCN
as used for Cell 10
Cell 1,
Cell 3
as used for Cell 3
Cell 10
threshX-High[m] 10 20dB
cellReselectionPriority[m] 5 Cell 1,
Cell 3
3 Cell 10
}
}

6.1.2.6 Cell reselection using Q
hyst
, Q
offset
and T
reselection

(1)
with { UE i n E- UTRA RRC_I DLE st at e, and t he UE i s not i n hi gh mobi l i t y st at e }
ensure that {
when { Qhyst i s non- zer o or i t s val ue changes i n syst emi nf or mat i on }
then { UE r esel ect s t he hi ghest r anked cel l t aki ng t he act ual Qhyst val ue i nt o account }

}

Release 9
3GPP
50
3GPP TS 36.523-1 V9.3.0 (2010-12)
(2)
ensure that {
when { cel l r esel ect i on cr i t er i a ar e f ul f i l l ed dur i ng a t i me i nt er val Tr esel ect i on }
then { UE r esel ect s t he hi ghest r anked cel l }

}

(3)
ensure that {
when { Qof f set i s non- zer o or i t s val ue changes i n syst emi nf or mat i on }
then { UE r esel ect s t he hi ghest r anked cel l t aki ng t he act ual Qof f set val ue i nt o account }

}

TS 36.304, clauses 5.2.1 and 5.2.4.6 and TS 36.331 clause 6.3.1.
[TS 36.300, clause 10.1.1.2]
UE in RRC_IDLE performs cell reselection. The principles of the procedure are the following:
- The UE makes measurements of attributes of the serving and neighbour cells to enable the reselection process:
- There is no need to indicate neighbouring cell in the serving cell system information to enable the UE to
search and measure a cell i.e. E-UTRAN relies on the UE to detect the neighbouring cells;
- For the search and measurement of inter-frequency neighbouring cells, only the carrier frequencies need to be
indicated;
- Measurements may be omitted if the serving cell attribute fulfils particular search or measurement criteria.
- Cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria which
involves measurements of the serving and neighbour cells:
- Intra-frequency reselection is based on ranking of cells;
...
- Cell reselection parameters are applicable for all UEs in a cell, ...
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion R
s
for serving cell and R
n
for neighbouring cells is defined by:

R
s
=Q
meas
,
s
+Q
Hyst

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
Qoffset For intra-frequency: Equals to Qoffset
s,n
, if Qoffset
s,n
is valid,
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

Release 9
3GPP
51
3GPP TS 36.523-1 V9.3.0 (2010-12)
meas,n
and Q
meas,s
If a cell is ranked as the best cell the UE shall perform cell re-selection to that cell.
...
RAT,

[TS 36.331, clause 6.3.1]
The IE SystemInformationBlockType4 contains neighbouring cell related information relevant only for intra-frequency
cell re-selection. The IE includes cells with specific re-selection parameters as well as blacklisted cells.
System Simulator:
- Cell 1 and Cell 2 have different tracking areas according to table 6.0.1-2.
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) on Cell 1 according to [18].
texts in this clause. Configurations marked "T1", "T2", "T3", "T4", "T5", "T6" and "T7" are applied at the points
indicated in the Main behaviour description in Table 6.1.2.6.3.2-2.
Release 9
3GPP
52
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.6.3.2-1: Time instances of cell power level and parameter change
Ti Parameter Unit Cell 1 Cell 2 Remark
T1
Cell-specific RS
EPRE
dBm/
15kH
z
-91 -85
Cell 2 becomes stronger than Cell 1
but Cell 1 remains the highest ranked
one due to Qhyst
sCell1

T2
Qhyst
s

dB 0 0
Qhyst
sCell1
change causes Cell 2 to
become highest ranked cell
T3
Cell-specific RS
EPRE
dBm/
15kH
z
-85 -91
Cell 1 becomes the strongest and
highest ranked one due to
Qoffset
s,n
dB 24 0 Qoffset
s,nCell2
remains zero
T4
Cell-specific RS
EPRE
dBm/
15kH
z
-91 -85
Cell 1 becomes weaker but it remains
the highest ranked one due to
Qoffset
s,nCell 1

T5
Qoffset
s,n

dB 0 0
Cell 2 becomes the highest ranked
one due to Qoffset
s,nCell1
change
T6
Cell-specific RS
EPRE
dBm/
15kH
z
-85 -91
one
TreselectionEUTRAN s 7 0
T7
Cell-specific RS
EPRE
dBm/
15kH
z
-91 -85
cell
Note: The total test tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1) and
relative UE measurement accuracy of RSRP (TS 36.133 clause 9.1.2.2).

Release 9
3GPP
53
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
levels according to row "T1" in table
6.1.2.6.3.2-1.
- - - -
next 10s?
3 SS resets Qhyst
sCell1
according to row "T2" in
table 6.1.2.6.3.2-1 and notifies UE of the
system information change. The
<-- Paging - -
Cell 2? (Note 1)
- - 1 -
5 Void - - - -
5A SS changes Qoffset
s,nCell1
according to rows
"T3" in table 6.1.2.6.3.2-1 and notifies UE of
the system information change. The
<-- Paging - -
5B Wait for 1.1* modification period (Note 2) to
allow the new system information to take
effect.
- - - -
5C SS re-adjusts cell-specific reference signal
levels according to rows "T3" in table
6.1.2.6.3.2-1.
- - - -
6 Wait until there is any RRCConnectionRequest
send from the UE on Cell 1.
--> RRCConnectionRequest - -
7-
11
Cell 1.
- - - -
12 SS re-adjusts cell-specific reference signal
6.1.2.6.3.2-1.
- - - -
next 10s?
14 SS resets Qoffset
s,nCell1
according to row "T5"
in table 6.1.2.6.3.2-1 and notifies UE of the
system information change. The
<-- Paging - -
Cell 2? (Note 1)
- - 3 -
16 Void - - - -
16
A
SS changes TreselectionEUTRAN
Cell 1

according to rows "T6" in table 6.1.2.6.3.2-1
and notifies UE of the system information
change. The systemInfoValueTag in the
<-- Paging - -
16
B
Wait for 1.1* modification period (Note 2) to
allow the new system information to take
effect.
- - - -
16
C
SS re-adjusts cell-specific reference signal
- - - -
Release 9
3GPP
54
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.1.2.6.3.2-1.
17 Wait until there is any RRCConnectionRequest
send from the UE on Cell 1
18-
22
Cell 1.
- - - -
23 SS re-adjusts cell-specific reference signal
6.1.2.6.3.2-1.
- - - -
next 6s?
next 12s?
26-
29
Cell 2.
- - - -

NOTE 1: The time interval in step 4 and 15 is set to cover TevaluateFDD,intra (TS 36.133 clause 4.2.2.3) +1280
ms for DRX cycle +1280 ms for system information block type scheduling. The timer tolerances are
taken into account according to [18].
NOTE 2: The wait time of 1.1* modification period in step 5B and 16B is to allow for the network to paging the
system information change during the next modification period, and update the system information at the
subsequent modification period. UE should acquire the updated system information within 100ms of the
start of modification period.
Table 6.1.2.6.3.3-1: Void
Table 6.1.2.6.3.3-2: SystemInformationBlockType1 for cells 1 (preamble and all steps, Table
6.1.2.6.3.2-2)
Derivation Path: 36.508 table 4.4.3.2-3
Information Element Value/remark Comment
schedulingInformation ::=SEQUENCE (SIZE
(1..maxSI-Message)) OF SEQUENCE {}

systemInfoValueTag The value is increased by
1 in step 3, step 5A, step
14 and step 16A

}

Table 6.1.2.6.3.3-3: SystemInformationBlockType3 for cell 1 (preamble, table 6.1.2.6.3.2-2)
q-Hyst dB24 Qhyst
sCell1

}
}

Release 9
3GPP
55
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.6.3.3-4: SystemInformationBlockType3 for cell 1 (step 3, table 6.1.2.6.3.2-2)
q-Hyst dB0 Qhyst
sCell1

}
}

Table 6.1.2.6.3.3-5: SystemInformationBlockType3 for cell 1 (step 16A, table 6.1.2.6.3.2-2)
q-Hyst dB0 Qhyst
sCell1

}
t-ReselectionEUTRA 7 seconds
}
}

Table 6.1.2.6.3.3-6: SystemInformationBlockType4 for cell 1 (step 5A, table 6.1.2.6.3.2-2)
intraFreqNeighCellList SEQUENCE (SIZE
(1..maxCellIntra)) OF SEQUENCE {

physCellId [1] Physical cell identity of
Cell 2

q-OffsetCell [1] dB24 Qoffset
s,nCell 1

}
}

Table 6.1.2.6.3.3-7: SystemInformationBlockType4 for cell 1 (step 14, table 6.1.2.6.3.2-2)
intraFreqNeighCellList SEQUENCE (SIZE
(1..maxCellIntra)) OF SEQUENCE {

physCellId [1] Physical cell identity of
Cell 2

q-OffsetCell [1] dB0 Qoffset
s,nCell 1

}
}

6.1.2.7 Cell reselection / Equivalent PLMN
(1)
with { UE camped nor mal l y on a cel l and net wor k has downl oaded a l i st of equi val ent PLMNs dur i ng t he
Locat i on Regi st r at i on pr ocedur e }
ensure that {
when { a sui t abl e nei ghbour cel l on an equi val ent PLMN becomes bet t er r anked t han t he sui t abl e
Ser vi ng cel l }
then { UE r esel ect s t o t hi s equi val ent PLMN cel l . }
}

Release 9
3GPP
56
3GPP TS 36.523-1 V9.3.0 (2010-12)
(2)
ensure that {
when { t he Ser vi ng cel l becomes unsui t abl e due t o S<0 and a sui t abl e cel l exi st s on an equi val ent
PLMN }
}

(3)
ensure that {
when { t he Ser vi ng cel l becomes unsui t abl e due t o cel l bar r i ng and a sui t abl e cel l exi st s on an
equi val ent PLMN }
}

(4)
ensure that {
when { t he UE eval uat es cel l s f or r esel ect i on }
then { UE i gnor es sui t abl e cel l s f or whi ch t he UE has no r esel ect i on pr i or i t y pr ovi ded. }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 5.2.4.1, TS
23.122 clause 4.4.3.
[TS 36.304, clause 5.2.4.1]
UE shall only perform reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in
system information and for which the UE has a priority provided.
[TS 23.122, clause 4.4.3]
The Mobile Equipment stores 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 registered PLMN that downloaded the
list. All PLMNs in the stored list, in all access technologies supported by the PLMN, are regarded as equivalent to each
other for PLMN selection, cell selection/re-selection and handover.
System Simulator:
- Three inter-frequency multi-PLMN cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting
default NAS parameters as indicated in TS 36.508 Table 4.4.2-2.
Table 6.1.2.7.3.1-1: PLMN identifiers
Cell PLMN name
1 PLMN1
12 PLMN2
13 PLMN3

- All cells are high quality.
- All cells are suitable cells.
Release 9
3GPP
57
3GPP TS 36.523-1 V9.3.0 (2010-12)
UE:
6.1.2.7.3.1-2.
Table 6.1.2.7.3.1-2: USIM configuration
EF
LOCI
PLMN1 (See pre-amble)

Preamble:
- The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508 clause 4.5.2.3 except that
the ATTACH ACCEPT message indicates PLMN3 in the Equivalent PLMN list as described in Table
6.1.2.7.3.3-1.
Table 6.1.2.7.3.21 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configurations marked T1 and T2 are applied at the points indicated in the Main behaviour
description in Table 6.1.2.7.3.2-2. `
Parameter Unit Cell 1 Cell 12 Cell 13 Remarks
T0 RS EPRE dBm/15kHz -67 -82 -97 All cells S>0
Cell status N/A cellBarred=
notBarred
cellBarred=
notBarred
cellBarred=
notBarred
No cells are barred
T1 RS EPRE dBm/15kHz -115 -82 -97 Cell 1 S <0 as described in TS
36.508 clause 6.2.2.1
notBarred
cellBarred=
notBarred
cellBarred=
notBarred
No cells are barred
T2 RS EPRE dBm/15kHz -67 -82 -97 All cells S>0
notBarred
cellBarred=
barred
cellBarred=
notBarred
The Serving cell, Cell 12,
becomes barred
Note 1: The default values (including not present) for all other parameters influencing cell reselection are suitable
for this test. The values are defined in TS 36.508 clauses 4.4.3.2 and 4.4.3.3.

Release 9
3GPP
58
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
RRCConnectionRequest within the next [100
seconds]?
2 SS adjusts cell levels and cell status according to
row T1 of table 6.1.2.7.3.2-1.
- - - -
indicate that the UE is camped on E-UTRAN Cell
13?
NOTE: The UE performs a TAU procedure with
PLMN1 and PLMN2 listed as an Equivalent PLMN
in the TRACKING AREA UPDATE ACCEPT
message, and the RRC connection is released.
- - 2 P
4 Void - - - -
12?
- - 1 P
6 Void - - - -
row T0 of table 6.1.2.7.3.2-1.
- - - -
RRCConnectionRequest within the next [100
seconds]?
--> RRCConnectionRequest 1,4 F
row T2 of table 6.1.2.7.3.2-1.
Cell 12 becomes barred.
The SS notifies the UE of change of System
Information.
<-- Paging - -
10 Void - - - -
13?
- - 3,4 P
Note 1: In Steps 1 and 8, a wait time long enough to ensure that the UE has detected, measured and evaluated the
neighbour inter-frequency cells is provided, see 36.133 clause 4.2.2.4.
Note 2: In Step 11, the UE moves to Cell 13 because no reselection priority is defined for Cell 1, see Table
6.1.2.7.3.3-6.

Table 6.1.2.7.3.3-1: ATTACH ACCEPT for Cell 1 (preamble)
Equivalent PLMNs PLMN3

Table 6.1.2.7.3.3-2: TRACKING AREA UPDATE ACCEPT for Cell 13 (steps 3 & 11 , Table 6.1.2.7.3.2-2)
Equivalent PLMNs PLMN1, 2

Release 9
3GPP
59
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.7.3.3-3: TRACKING AREA UPDATE ACCEPT for Cell 12 (step 5, Table 6.1.2.7.3.2-2)
Equivalent PLMNs PLMN1, 3

Table 6.1.2.7.3.3-4: SystemInformationBlockType1 for Cell 12 (step 9, Table 6.1.2.7.3.2-2)
Derivation path: 36.508 Table 4.4.3.2-3
cellBarred barred
}
systemInfoValueTag 1 Previous value is 0
}

Table 6.1.2.7.3.3-5: Paging for Cell 12 (step 9, Table 6.1.2.7.3.2-2)
systemInfoModification true
etws-Indication Not present
}

Table 6.1.2.7.3.3-6: SystemInformationBlockType5 for Cell 12 (preamble and all steps, Table
6.1.2.7.3.2-2)

as used for Cell 1

cellReselectionPriority[n] Not present UE does not have
a priority for
frequency of Cell 1

}
}

6.1.2.7.3.2-2)

as used for Cell 1

cellReselectionPriority[n] Not present UE does not have
a priority for
frequency of Cell 1

}
}

Release 9
3GPP
60
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.1.2.8 Cell reselection using cell status and cell reservations / Access control class
0 to 9
(1)
with { UE camped nor mal l y i n st at e E- UTRA RRC_I DLE and UE f i t t ed wi t h a USI M wi t h access cl ass 0. . 9}
ensure that {
when { a hi gher r anked cel l i s f ound wi t h cel l st at us " bar r ed" }
then { UE does not at t empt t o r esel ect t o t he hi gher r anked cel l }
}

(2)
with { UE camped nor mal l y i n st at e E- UTRA RRC_I DLE and UE f i t t ed wi t h a USI M wi t h access cl ass 0. . 9}
ensure that {
when { a hi gher r anked cel l i s f ound " r eser ved" f or Oper at or use }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clauses 5.2.4.4 and
5.3.1.
[TS 36.304, clause 5.2.4.4]
For the highest ranked cell (including serving cell) according to cell reselection criteria specified in subclause 5.2.4.6,
the UE shall check if the access is restricted according to the rules in subclause 5.3.1.
If that cell and other cells have to be excluded from the candidate list, as stated in subclause 5.3.1, the UE shall not
consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes.
[TS 36.304, clause 5.3.1]
Elements:

- cellReservedForOperatorUse (IE type: "reserved" or "not reserved")

When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
- ...
- UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 and UEs with AC 11 or 15 not operating in
theirHLPMN/EHPLMN shall behave as if the cell status is barred in case the cell is reserved for operator
use for the PLMN the UE is currently registered with.
NOTE 1: ...
- ...
Release 9
3GPP
61
3GPP TS 36.523-1 V9.3.0 (2010-12)
- else
- If the IE intraFrequencyReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to
System Simulator:
- Three inter-frequency cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting default NAS
parameters as indicated in TS 36.508 Table 4.4.2-2, except that TAC values use the codes in Table 6.0.1-2.
- SIB 1 of Cell 3 and Cell 6 indicate cellBarred=barred.
- Each cell has only a single PLMN identity.
- The cell power levels are configured as shown in Table 6.1.2.8.3.1-1.
Table 6.1.2.8.3.1-1: Cell power configuration
Parameter Unit Cell 1 Cell 3 Cell 6
(min UL)
Remarks
RS EPRE dBm/15kHz -97 -82 -67 S>0 for all cells
Note 1: The default values (including not present) for all other parameters influencing cell reselection are
suitable for this test. The values are defined in TS36.508 clauses 4.4.3.2 and 4.4.3.3

UE:
- The UE is equipped with a USIM containing default values (as per TS 36.508) except for those shown in Table
6.1.2.8.3.1-2.
Table 6.1.2.8.3.12: USIM Configuration
USIM field Value
EF
ACC
Type A as defined in TS34.108 clause
8.3.2.15

Preamble:
Release 9
3GPP
62
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 SS adjusts SIB1 of Cell 3 to indicate
cellBarred=notBarred
- - - -
Cell 3?
- - 1 -
3 The SS notifies the UE of change of System
Information. SS adjusts SIB1 of Cell 3 to
indicate cellBarred=barred. (Cell 3 and Cell 6
are now both barred).
<-- Paging - -
4 Void - - - -
Cell 1?
- - 1 -
6 SS adjusts SIB1 of both Cell 3 and Cell 6: Cell
3 indicates cellBarred=notBarred; Cell 6
indicates cellBarred=notBarred and
cellReservedForOperatorUse =reserved.
- - - -
Cell 3?
- - 2 -
indicate cellReservedForOperatorUse =
reserved.
<-- Paging - -
9 Void. - - - -
Cell 1?
- - 2 -

in Tables 6.1.2.8.3.3-1, 6.1.2.8.3.3-2, 6.1.2.8.3.3-4 and 6.1.2.8.3.3-5

Release 9
3GPP
63
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.8.3.3-1: SystemInformationBlockType1 for Cell 3 and Cell 6 (pre-test conditions, Table
6.1.2.8.3.2-1)
SystemInformationBlockType1 ::=
SEQUENCE {

plmn-IdentityList SEQUENCE (SIZE (1..6))
OF SEQUENCE {
1 entry
cellReservedForOperatorUse notReserved Cell 3
Cell 6
}
cellBarred barred Cell 3
Cell 6
}
}

Table 6.1.2.8.3.3-2: SystemInformationBlockType1 for Cell 3 and Cell 6 (step 1, Table 6.1.2.8.3.2-1)
plmn-IdentityList SEQUENCE (SIZE (1..6)) OF
SEQUENCE {
1 entry
Cell 6
}
cellBarred notBarred Cell 3
barred Cell 6
}
systemInfoValueTag 1 Cell 3
0 Cell 6
}

Table 6.1.2.8.3.3-2A: SystemInformationBlockType1 for Cell 3 and Cell 6 (step 3, Table 6.1.2.8.3.2-1)
SEQUENCE {
1 entry
Cell 6
}
Cell 6
}
0 Cell 6
}

Release 9
3GPP
64
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.8.3.3-3: Paging (steps 3 & 8, Table 6.1.2.8.3.2-1)
Derivation Path: 36.508 Table 4.6.1-7
}

SEQUENCE {
1 entry
reserved Cell 6
}
Cell 6
}
1 Cell 6
}

SEQUENCE {
1 entry
cellReservedForOperatorUse reserved Cell 3
Cell 6
}
Cell 6
}
1 Cell 6
}

6.1.2.9 Cell reselection using cell status and cell reservations / Access control class
11 to 15
(1)
with { UE camped nor mal l y i n st at e E- UTRA RRC_I DLE and UE f i t t ed wi t h a USI M wi t h access cl ass 0. . 9
and access cl asses 11. . 15 i ncl usi ve }
ensure that {
when { a hi gher r anked cel l i s f ound wi t h cel l st at us " bar r ed" }
}

Release 9
3GPP
65
3GPP TS 36.523-1 V9.3.0 (2010-12)
(2)
with { UE camped nor mal l y i n st at e E- UTRA RRC_I DLE and UE f i t t ed wi t h a USI M wi t h access cl ass 0. . 9
and access cl asses 11. . 15 i ncl usi ve }
ensure that {
when { a hi gher r anked cel l i s f ound " r eser ved" f or Oper at or use }
then { UE r e- sel ect s t o t he hi gher r anked cel l }
}

5.3.1.
[TS 36.304, clause 5.2.4.4]
For the highest ranked cell (including serving cell) according to cell reselection criteria specified in subclause 5.2.4.6,
the UE shall check if the access is restricted according to the rules in subclause 5.3.1.
If that cell and other cells have to be excluded from the candidate list, as stated in subclause 5.3.1, the UE shall not
consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes.
[TS 36.304, clause 5.3.1]
Elements:

- cellReservedForOperatorUse (IE type: "reserved" or "not reserved")

When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
- UEs assigned to Access Class 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate
during the cell selection and reselection procedures if the IE cellReservedForOperatorUse for that PLMN set to
reserved.
- UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 and UEs with AC 11 or 15 not operating in
theirHLPMN/EHPLMN shall behave as if the cell status is barred in case the cell is reserved for operator
use for the PLMN the UE is currently registered with.
NOTE 1: ...
- ...
- else
- If the IE intraFrequencyReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to
"allowed", the UE may select another cell on the same frequency if selection/re-selection criteria are fulfilled.
- The UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.- If the IE
intraFreqReselection in IE cellAccessRelatedInfo in SystemInformationBlockType1 is set to "not allowed" the
UE shall not re-select a cell on the same frequency as the barred cell.
Release 9
3GPP
66
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
- Three inter-frequency cells as specified in TS36.508 clause 4.4.1.2 are configured broadcasting default NAS
parameters as indicated in TS 36.508 Table 4.4.2-2, except that TAC values use the codes in Table 6.0.1-2.
- SIB 1 of Cell 3 and Cell 6 indicate cellBarred=barred
- Each cell has only a single PLMN identity.
- The cell power levels are configured as shown in Table 6.1.2.9.3.1-1.
Table 6.1.2.9.3.11: Cell power configuration
Parameter Unit Cell 1 Cell 3 Cell 6 Remarks
RS EPRE dBm/15kHz -97 -82 -67 S>0 for all cells
Note 1: The default values (including not present) for all other parameters influencing cell reselection are
suitable for this test. The values are defined in TS36.508 clauses 4.4.3.2 and 4.4.3.3

UE:
- The UE is equipped with a USIM containing default values (as per TS 36.508) except for those shown in Table
6.1.2.9.3.1-2.
Table 6.1.2.9.3.12: USIM Configuration
USIM field Value
EF
ACC
Type B as defined in TS34.108 clause
8.3.2.15

Preamble:
Release 9
3GPP
67
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 SS adjusts SIB1 of Cell 3 to indicate
cellBarred=notBarred
- - - -
Cell 3?
- - 1 -
indicate cellBarred=barred. (Cell 3 and Cell 6
are now both barred) .
<-- Paging - -
4 Void. - - - -
Cell 1?
- - 1 -
6 SS adjusts SIB1 of both Cell 3 and Cell 6: Cell
3 indicates cellBarred=notBarred; Cell 6
indicates cellBarred=notBarred and
cellReservedForOperatorUse =reserved
- - - -
Cell 6?
- - 2 -

in Tables 6.1.2.9.3.3-1, 6.1.2.9.3.3-2 and 6.1.2.8.3.3-4

Table 6.1.2.9.3.3-1: SystemInformationBlockType1 for Cell 3 and Cell 6 (pre-test conditions, Table
6.1.2.9.3.2-1)
SEQUENCE {

plmn-IdentityList SEQUENCE (SIZE (1..6))
OF SEQUENCE {
1 entry
Cell 6
}
Cell 6
}
}

Release 9
3GPP
68
3GPP TS 36.523-1 V9.3.0 (2010-12)
SEQUENCE {
1 entry
Cell 6
}
barred Cell 6
}
0 Cell 6
}

Table 6.1.2.9.3.3-2A: SystemInformationBlockType1 for Cell 3 and Cell 6 (step 3, Table 6.1.2.8.3.2-1)
SEQUENCE {
1 entry
Cell 6
}
Cell 6
}
0 Cell 6
}

}

Release 9
3GPP
69
3GPP TS 36.523-1 V9.3.0 (2010-12)
SEQUENCE {
1 entry
reserved Cell 6
}
Cell 6
}
1 Cell 6
}

6.1.2.10 Cell reselection in shared network environment
wi t h { t he UE i s i n E- UTRA RRC_I dl e and r egi st er ed on t he HPLMN }
ensur e t hat {
when { a cel l of a di f f er ent PLMN but shar ed wi t h t he HPLMN becomes hi ghest r anked cel l }
t hen { t he UE r esel ect s t he cel l shar ed wi t h t he HPLMN }

References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 5.2.4.2 and TS
23.122 clause 4.4.3.
[TS 36.304, clause 5.2.4.6]
s
n

R
s
=Q
meas
,
s
+Q
Hyst

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
s,n
, if Qoffset
s,n
is valid,
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2, but may
meas,n
and Q
meas,s
If a cell is ranked as the best cell the UE shall perform cell reselection to that cell. If this cell is found to be not-suitable,
the UE shall behave according to subclause 5.2.4.4.
RAT
;
Release 9
3GPP
70
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 23.122, clause 4.4.3]
...
...
System Simulator:
- Cell 1 (HPLMN)
- Cell 12 (primary PLMN: same MCC like HPLMN but different MNC, secondary PLMN: HPLMN)
UE:
None.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while columns
marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in
the texts in this clause.
T0 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 Off
T1 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 -73 The power level values are assigned to satisfy Srxlev
Cell 12

>Srxlev
Cell 1

Release 9
3GPP
71
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 The SS changes Cell 1 and Cell 12 level
according to the row "T1" in table 6.1.2.10.3.2-
1.
- - - -
3 The SS transmits an RRCConnectionSetup <-- RRCConnectionSetup - -
4 Check; Does the UE transmit an
indicating the HPLMN (second PLMN in the
list)?
Note: this message contains an TRACKING
AREA UPDATE REQUEST message
according to default message contents.
5 -
7
- - - -

Table 6.1.2.10.3.3-1: SystemInformationBlockType1 (Cell 1, all steps, Table 6.1.2.10.3.2-2)
SEQUENCE {

plmn-Identity[1] Set to the same Mobile
Country Code and Mobile
Network Code stored in
EFIMSI on the test USIM
card

}
}
}

SEQUENCE {

Country Code stored in
EFIMSI on the test USIM,
MNC=02

Country Code and Mobile
Network Code stored in
EFIMSI on the test USIM
card
This is the same
PLMN as Cell 1

}
}
}

Release 9
3GPP
72
3GPP TS 36.523-1 V9.3.0 (2010-12)
c1 CHOICE{
selectedPLMN-Identity 2 HPLMN
}
}
}
}

6.1.2.11 Inter-frequency cell reselection
(1)
ensure that {
when { UE det ect s bot h i nt r a- f r equency and equal pr i or i t y i nt er - f r equency nei gbour cel l s and t he
i nt er - f r equency cel l i s t he hi ghest r anked cel l }
then { UE r esel ect s t he i nt er - f r equency cel l }
}

5.2.4.6.
[TS 36.304, clause 5.2.4.5]
[TS 36.304, clause 5.2.4.6]
s
n

R
s
=Q
meas
,
s
+Q
Hyst

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
s,n
, if Qoffset
s,n
is valid,
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

meas,n
and Q
meas,s
Release 9
3GPP
73
3GPP TS 36.523-1 V9.3.0 (2010-12)
RAT
;
System Simulator:
- Cell 1,Cell 2 and Cell 3 have different tracking areas according to table 6.0.1-2.
UE:
None.
Preamble:
T1 Cell-specific
RS EPRE
dBm/15kHz -85 -91 -73 The power level values are set so that R
Cell 2
<R
Cell 1
<R
Cell 3
.

U - S Message
1 The SS changes the cells power level setting
1.
- - - -
Cell 3?
- - 1 -

Table 6.1.2.11.3.3-1: Void
Table 6.1.2.11.3.3-2: Void
Table 6.1.2.11.3.3-3: Void
6.1.2.12 Cell reselection / Cell-specific reselection parameters provided by the
network in a neighbouring cell list
6.1.2.12.1 Test Purpose
(1)
wi t h { t he UE i s i n RRC_I DLE and Syst emI nf or mat i onBl ockType4 cont ai n a cel l - speci f i c Qof f set f or a
nei ghbour i nt r a f r equency cel l }
ensur e t hat {
when { t he nei ghbour cel l has l ower power t han t he ser vi ng cel l but i t i s hi gher r anked due t o t he
cel l - speci f i c Qof f set }
t hen { t he UE r esel ect s t he nei ghbour cel l wi t h cel l - speci f i c Qof f set }
Release 9
3GPP
74
3GPP TS 36.523-1 V9.3.0 (2010-12)
}

(2)
wi t h { t he UE i s i n RRC_I DLE and Syst emI nf or mat i onBl ockType4 cont ai n a bl ack l i st ed cel l }
ensur e t hat {
when { a bl ack l i st ed cel l becomes hi gher r anked t han t he ser vi ng cel l }
t hen { t he UE r emai ns camped on t he ser vi ng cel l }
}

6.1.2.12.2 Conformance Requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.304, clauses 5.2.4.1 and
5.2.4.6.
[TS 36.304 clause 5.2.4.1]
[TS 36.304 clause 5.2.4.6]
s
n

R
s
=Q
meas
,
s
+Q
Hyst

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
s,n
, if Qoffset
s,n
is valid,
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

meas,n
and Q
meas,s
RAT
;
System Simulator:
- cells 1, 2, and 4 on the same E-UTRA frequency and in different tracking areas
- only 2 cells are simultaneously active, Cell 4 can be implemented as minimum uplink cell
- cell 1 is transmitting SystemInformationBlockType4 according to specific message contents (Qoffset
1,2
is -24dB)
Release 9
3GPP
75
3GPP TS 36.523-1 V9.3.0 (2010-12)
- cell 2 is transmitting SystemInformationBlockType4 according to specific message contents (Qoffset
2,1
is 24dB,
cell 4 is on black list)
NOTE: Qoffset
2,1
does not serve any test purpose, but symmetrical Qoffset values may be more realistic and also
avoid the risk that the UE reselects cell 1 after step 2 is complete in case the SS takes some time before
switching cell 1 off.
UE:
None.
Preamble:
- the UE is in state Registered, Idle mode (state 2) on Cell 1 according to [18].
various time instants of the test execution. Rows marked "T0" denote the conditions after the preamble, while rows
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.
Ti Parameter Unit Cell 1 Cell 2 Cell 4 Remark
T0 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 Off Off Only Cell 1 is on
T1 -85 -91 Off Cell 2 has lower power but is higher ranked
due to cell-specific Qoffset
1,2

T2 Off -91 -85 Cell 4 has higher power than Cell 2 but is
black listed

U - S Message
1 The SS re-adjusts the cell-specific reference
signal levels according to row "T1" in table
6.1.2.12.3.2-1.
- - - -
2 Check: Does the test result of generic
procedure 6.4.2.7 indicate that the UE camps
on Cell 2?
- - 1 -
6.1.2.12.3.2-1.
- - - -
4 Check: Does the UE initiate a random access
procedure on Cell 4 within the next 120s?
- - 2 F

Table 6.1.2.12.3.3-1: SystemInformationBlockType4 for cell 1 (all steps, Table 6.1.2.12.3.2-2)
intraFreqNeighCellList SEQUENCE { 1 entry
physCellId[1] PhysicalCellID of Cell 2
q-OffsetCell[1] dB-24
}
}

Release 9
3GPP
76
3GPP TS 36.523-1 V9.3.0 (2010-12)
intraFreqNeighCellList { 1 entry
physCellId[1] PhysicalCellID of Cell 1
q-OffsetCell[1] dB24
}
intraFreqBlackCellList SEQUENCE { 1 entry
start[1] PhysicalCellID of Cell 4
range[1] Not present
}
}

6.1.2.13 Cell reselection, S
intrasearch
, S
nonintrasearch

(1)
ensure that {
when { S
i nt r asear ch
i s non- zer o i n syst emi nf or mat i on }
then { UE per f or mmeasur ement and r esel ect s t he hi ghest r anked cel l upon Sr xl ev < S
i nt r asear ch
}

}

(2)
ensure that {
when { S
noni nt r asear ch
then { UE per f or mmeasur ement and r esel ect s t he cel l whi ch bel ong t o t he equal pr i or i t y
f r equency cel l upon Sr xl ev < S
noni nt r asear ch
}

}

(3)
ensure that {
when { S
noni nt r asear ch
then { UE per f or mmeasur ement and r esel ect s t he cel l whi ch bel ong t o t he hi gh pr i or i t y
f r equency cel l upon Sr xl ev > S
noni nt r asear ch
}

}

References: The conformance requirements covered in the current TC are specified in: TS36.304, clauses 5.2.4.2,
5.2.4.5 and 5.2.4.6; TS36.331, clause 6.3.1.
[TS 36.304, clause 5.2.4.2]
- If S
intrasearch
ServingCell
>S
intrasearch
measurements.
- If S
ServingCell
<=S
intrasearch,
or S
intrasearch
measurements.
Release 9
3GPP
77
3GPP TS 36.523-1 V9.3.0 (2010-12)
- If S
nonintrasearch
ServingCell
>S
nonintrasearch
- If S
ServingCell
<=S
nonintrasearch
or S
nonintrasearch
according to [10].
Where S
ServingCell
[TS 36.304, clause 5.2.4.5]
Criteria 1: the S
nonServingCell,x
x, high
Treselection
RAT
;
.....
.....
RAT
best cell among the cells meeting the criteria on the highest priority frequencies or the highest priority RATif the
[TS 36.304, clause 5.2.4.6]
s
n

R
s
=Q
meas
,
s
+Q
Hyst

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
s,n
, if Qoffset
s,n
is valid,
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

meas,n
and Q
meas,s
If a cell is ranked as the best cell the UE shall perform cell re-selection to that cell.
...
RAT,

Release 9
3GPP
78
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 36.331, clause 6.3.1]
The IE SystemInformationBlockType3 contains cell re-selection information common for intra-frequency, inter-
frequency and/ or inter-RAT cell re-selection (i.e. applicable for more than one type of cell re-selection but not
necessarily all) as well as intra-frequency cell re-selection information other than neighbouring cell related.
System Simulator:
- Cell 1, Cell 2 and Cell 3 have different tracking areas.
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) on Cell 1(serving cell) according to [18].
texts in this clause. Configurations marked "T1", "T2" and "T3" are applied at the points indicated in the Main
T1
Cell-specific RS
EPRE
dBm/15kHz -91 -79 "Off"
Srxlev of Cell 1 is less than S
intrasearch.

Q
rxlevmin
dBm -106 -106 -106
S
intrasearch
dB [22] [22] [22]
T2
Cell-specific RS
EPRE
dBm/15kHz "Off" -97 -79
Srxlev of Cell 2 is less than S
nonintrasearch.

S
nonintrasearch
dB [16] [16] [16]
T3
Cell-specific RS
EPRE
dBm/15kHz -85 "Off" -79
Srxlev of Cell 3 is greater than
S
nonintrasearch
but Cell 1 is high priority cell.
Note: Power level Off is defined in TS36.508 Table 6.2.2.1-1.

Release 9
3GPP
79
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
6.1.2.13.3.2-1.
- - - -
2 Check: Does UE transmits an
RRCConnectionRequest message on Cell 2
within [6 minutes]?
3 - 7 Steps 2 to 6 of the generic test procedure in
TS 36.508 subclause 6.4.2.7 are performed
on Cell 2.
NOTE: The UE performs a TAU procedure
and the RRC connection is released.
- - - -
6.1.2.13.3.2-1.
- - - -
9 Check: Does UE transmits an
within [6 minutes]?
10 -
14
TS 36.508 subclause 6.4.2.7 are performed
on Cell 3.
NOTE: The UE performs a TAU procedure
- - - -
Information and changes the system
information for Cell 3. The
<-- Paging - -
16 Wait for 15 s for the UE to receive system
information.
- - - -
6.1.2.13.3.2-1.
- - - -
18 Check: Does the test result of steps 1 to 5 of
the generic test procedure in TS 36.508
subclause 6.4.2.7 indicate that the UE is
camped on E-UTRAN Cell 1? (Note1)
- - 3 -
Note1: UE shall search higher priority layer (i.e. E-UTRA carrier frequency of Cell 1) at least every (60 * N
layers
)
seconds, where N
layers
=1 as specified in [4.2.2, 34].

Table 6.1.2.13.3.3-1: SystemInformationBlockType1 for Cells 1, 2 and 3 (preamble, Table 6.1.2.13.3.2-
2)
schedulingInfoList ::=SEQUENCE (SIZE (1..maxSI-
Message)) OF SEQUENCE {}
Combination 3 in TS
36.508 section 4.4.3.1
SIB2, SIB3 and
SIB5 are
transmitted

}

Release 9
3GPP
80
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.13.3.3-2: SystemInformationBlockType3 for Cells 1, 2 and 3 (preamble and all steps, table
6.1.2.13.3.2-2)
s-NonIntraSearch 8 (16 dB)
}
s-IntraSearch 11 (22 dB)
}
}

Combination 3 in TS
36.508 section 4.4.3.1
SIB2, SIB3 and
SIB5 are
transmitted

systemInfoValueTag 1 Previous value is 0
}

1 entry
dl-CarrierFreq[1] EARFCN of Cell 1
threshX-High[1] 7 14 dB
cellReselectionPriority[1] 5
}
}

}

6.1.2.14 Speed-dependent cell reselection
(1)
with { UE i n E- UTRA RRC_I DLE st at e and i n hi gh mobi l i t y st at e }
ensure that {
when { UE det ect s t he cel l r anked as t he best cel l t aki ng i nt o account scal i ng f act or }
}

Release 9
3GPP
81
3GPP TS 36.523-1 V9.3.0 (2010-12)
5.2.4.3.1.
[TS 36.304, clause 5.2.4.3]
Besides Normal-mobility state a High-mobility and a Medium-mobility state are applicable if the parameters (T
CRmax
,
N
CR_H
, N
CR_M
and T
CRmaxHyst
) are sent in the system information broadcast of the serving cell.
State detection criteria:
...
High-mobility state criteria:
- If number of cell reselections during time period T
CRmax
exceeds N
CR_H

The UE shall not count consecutive reselections between same two cells into mobility state detection criteria if same
cell is reselected just after one other reselection.
State transitions:
The UE shall:
- if the criteria for High-mobility state is detected:
- enter High-mobility state.
...
If the UE is in High- or Medium-mobility state, the UE shall apply the speed dependent scaling rules as defined in
subclause 5.2.4.3.1.
[TS 36.304, clause 5.2.4.3.1]
UE shall apply the following scaling rules:
- If neither Medium- nor Highmobility state is detected:
- no scaling is applied.
- If High-mobility state is detected:
- Add the sf-High of "Speed dependent ScalingFactor for Q
hyst
to Q
hyst
if sent on system information
- For E-UTRAN cells multiply Treselection
EUTRA
by the sf-High of "Speed dependent ScalingFactor for
Treselection
EUTRA
- For UTRAN cells multiply Treselection
UTRA
Treselection
UTRA
- For GERAN cells multiply Treselection
GERA
Treselection
GERA
state if sent on system information
- For CDMA2000 HRPD cells Multiply Treselection
CDMA_HRPD
by the sf-High of "Speed dependent
ScalingFactor for Treselection
CDMA_HRPD
- For CDMA2000 1xRTT cells Multiply Treselection
CDMA_1xRTT
by the sf-High of "Speed dependent
ScalingFactor for Treselection
CDMA_1xRTT
...
In case scaling is applied to any Treselection
RAT
parameter the UE shall round up the result after all scalings to the
nearest second.
Release 9
3GPP
82
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
- Cell 1, Cell 2, and Cell 4.
UE:
None.
Preamble:
T1 Cell-specific
RS EPRE
dBm/
15kH
z
-91 -85 -91 Cell 2 becomes the highest ranked cell.
T2 Cell-specific
RS EPRE
dBm/
15kH
z
T3 Cell-specific
RS EPRE
dBm/
15kH
z

Release 9
3GPP
83
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1.
- - - -
2 Wait for 20s for the UE to perform cell
reselection procedure.(Note 1, Note 5)
- - - -
according to the row T2 in table 6.1.2.14.3.2-
1.
- - - -
reselection procedure.(Note 2, Note 5)
- - - -
1.
- - - -
reselection procedure. (Note 3, Note 5)
- - - -
1.
- - - -
reselection procedure. (Note 4, Note 5)
- - - -
9 The SS changes the TAC for Cell 4 to 2. - - - -
1.
- - - -
RRCConnectionRequest on Cell 4 within 5s?
(Note 5)
RRCConnectionRequest on Cell 4 within 7s
after step 11? (Note 5)
13-
17
Cell 4.
- - 1 -
Note 1: N
CR
(number of cell reselection) is 1.
Note 2: N
CR
is 2.
Note 3: N
CR
is 3.
Note 4: N
CR
is 4 and the UE enters high mobility state because number of cell reselections during time period T
CRmax

exceeds N
CR_H
.
Note 5: The wait time for cell reselection procedure is selected to cover time interval
Tmeasure,EUTRAN_Intra2+Tevaluate,E-UTRAN_intra+TreselectionEUTRAN+1280ms system information
block type scheduling.

Table 6.1.2.14.3.3-1: SystemInformationBlockType1 for Cell 2, and Cell 4 (preamble, Table
6.1.2.14.3.2-2)
Derivation Path: 36.508 Table 4.4.3.2-3
cellAccessRelatedInformation SEQUENCE {
trackingAreaCode 1
}
}

Release 9
3GPP
84
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.1.2.14.3.3-2: SystemInformationBlockType3 for Cell 1, Cell 2, and Cell 4 (preamble and all
steps, Table 6.1.2.14.3.2-2)
Derivation Path: 36.508, Table 4.4.3.3-2
speedStateReselectionPars SEQUENCE {
mobilityStateParameters SEQUENCE {
t-Evalulation s240
t-HystNormal s240
n-CellChangeMedium 3
n-CellChangeHigh 3
}
q-HystSF SEQUENCE {
sf-Medium dB0
sf-High dB0
}
}
}
t-ReselectionEUTRAN 7
t-ReselectionEUTRA-SF SEQUENCE {
sf-Medium oDot25
sf-High oDot25
}
}
}

trackingAreaCode 2
}
systemInfoValueTag 1
}

6.1.2.15 Inter-frequency cell reselection according to cell reselection priority provided
by SIBs
(1)
ensure that {
when { UE det ect s t he cel l r e- sel ect i on cr i t er i a ar e met f or t he cel l whi ch bel ongs t o t he equal
pr i or i t y f r equency }
then { UE r esel ect s t he cel l whi ch bel ongs t o t he equal pr i or i t y f r equency }
}

(2)
ensure that {
when { UE det ect s t he cel l r e- sel ect i on cr i t er i a ar e met f or t he cel l whi ch bel ongs t o t he hi gher
then { UE r esel ect s t he cel l whi ch bel ongs t o t he hi gher pr i or i t y f r equency }
}

Release 9
3GPP
85
3GPP TS 36.523-1 V9.3.0 (2010-12)
(3)
ensure that {
when { UE det ect s t he cel l r e- sel ect i on cr i t er i a ar e met f or t he cel l whi ch bel ongs t o t he l ower
then { UE r esel ect s t he cel l whi ch bel ongs t o t he l ower pr i or i t y f r equency }
}

5.2.4.2, 5.2.4.5 and 5.2.4.6.
[TS 36.304, clause 5.2.4.1]
priority frequency (i.e. lower than the eight network configured values). The UE shall delete priorities provided by
dedicated signalling when:
UTRA, T322 in UTRA and [T3230, FFS] in GERAN), if configured, at inter-RAT cell (re)selection.
information.
[TS 36.304, clause 5.2.4.2]
- If S
intrasearch
ServingCell
>S
intrasearch
measurements.
- If S
ServingCell
<=S
intrasearch
, or S
intrasearch
measurements.
Release 9
3GPP
86
3GPP TS 36.523-1 V9.3.0 (2010-12)
- If S
nonintrasearch
ServingCell
>S
nonintrasearch
- If S
ServingCell
<=S
nonintrasearch
or S
nonintrasearch
according to [10].
Where S
ServingCell
[TS 36.304, clause 5.2.4.5]
Criteria 1: the S
nonServingCell,x
x, high
Treselection
RAT
;
be performed if:
be performed if:
criteria 1; and
- S
ServingCell
<Threshs
erving, low
and the S
nonServingCell,x
x, low
RAT
; and
or if:
- there are no candidate cells for reselection on serving frequency according to 5.2.4.4 or 5.3.1.
nonServingCell,x
is higher than 0, as defined in [8].For cdma2000 RATs, S
nonServingCell,x
of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
RAT
best cell among the cells meeting the criteria on the highest priority frequencies or the highest priority RATif the
[TS 36.304, clause 5.2.4.6]

R
s
=Q
meas
,
s
+Qhyst
s

R
n
=Q
meas
,
n
- Qoffset

where:
Release 9
3GPP
87
3GPP TS 36.523-1 V9.3.0 (2010-12)
Q
meas
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

meas,n
and Q
meas,s
RAT
;
System Simulator:
- Cell 1, Cell 3 and Cell 6 have different tracking areas according to table 6.0.1-2.
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configurations marked "T1", "T2" and "T3" are applied at the
points indicated in the Main behaviour description in Table 6.1.2.15.3.2-2.
T1 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 -73 Off The power level values are assigned to
satisfy R
Cell 1
<R
Cell 3
.
(NOTE 1).
T2 Cell-
specific RS
EPRE
dBm/
15kH
z
Off -73 -73 The power level values are assigned to
satisfy Srxlev
Cell 1
<0 and Srxlev
Cell 6
>
Thresh
Cell 3, high
.
(NOTE 1).
T3 Cell-
specific RS
EPRE
dBm/
15kH
z
Off -73 -95 The power level values are assigned to
satisfy Srxlev
Cell 6
<Thresh
serving, low
and
Srxlev
Cell 3
>Thresh
Cell 6, low
, Srxlev
Cell 1
<0.

(NOTE 1).

Release 9
3GPP
88
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 The SS changes Cell 3 power level according
to the row "T1" in table 6.1.2.15.3.2-1.
- - - -
Cell 3?
- - 1 -
3 The SS changes Cell 1 and Cell 6 power level
1.
- - - -
Cell 6?
- - 2 -
- - - -
Cell 3?
- - 3 -

Table 6.1.2.15.3.3-1: Void
Table 6.1.2.15.3.3-2: Void
6.1.2.15.3.2-2)
threshServingLow 10 20 dB
cellReselectionPriority 5
}
}

Table 6.1.2.15.3.3-4: SystemInformationBlockType5 for Cell 1 and Cell 3 (preamble and all steps,
Table 6.1.2.15.3.2-2)

dl-CarrierFreq[n] EARFCN of Cell 6
threshX-High[n] 10 20 dB
cellReselectionPriority[n] 5
}
}

Release 9
3GPP
89
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2 Multi-mode environment (E-UTRAN, UTRAN, GERAN,
CDMA2000)
6.2.1 Inter-RAT PLMN selection
6.2.1.1 Inter-RAT PLMN Selection / Selection of correct RAT for OPLMN / Automatic
mode
(1)
with { UE i n Aut omat i c net wor k sel ect i on mode wi t h no RPLMN cel l s avai l abl e and OPLMN cel l s
avai l abl e on E- UTRAN and UTRAN }
ensure that {
when { UE i s swi t ched on}
then { UE sel ect s a t he hi ghest pr i or i t y OPLMN and RAT combi nat i on and UE at t empt s t o at t ach on
t he sel ect ed cel l and when successf ul l y r egi st er ed i ndi cat es t he PLMN t o t he user . }
}

(2)
with { UE i n Aut omat i c net wor k sel ect i on mode and OPLMN cel l s and non pr i or i t i sed RAT cel l s
avai l abl e on GERAN and E- UTRAN }
ensure that {
when { UE r et ur ns t o cover age}
}

(3)
with { UE i n Aut omat i c net wor k sel ect i on mode and bot h OPLMN cel l s and cel l s not on t he OPLMN l i st
ar e avai l abl e on E- UTRAN and UTRAN }
ensure that {
when { UE r et ur ns t o cover age }
}

References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1 and
4.4.3.1.1.
[TS 23.122, clause 4.4.3.1]
...
[TS 23.122, clause 4.4.3.1.1]
Release 9
3GPP
90
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator
- 4 cells are used: 2 cells belong to E-UTRAN, 1 cell belongs to GERAN and 1 cell belongs to UTRAN. The
cells are configured as specified in TS 36.508 clause 4.4.1.4 and Table 4.4.2-2.
UE
- The HPLMN is PLMN1
- There is no RPLMN.
USIM field Priority Value Access
technology
Comment
EF
PLMNwAcT
3GPP TS 31.102,
Annex E
The EF is empty.
EF
OPLMNwAcT
1 PLMN2 E-UTRAN
2 PLMN13 GERAN
3 PLMN2 UTRAN
4 PLMN13 E-UTRAN

Preamble
- The UE is in state Switched OFF (State 1)
- Cell levels are set according to row T0 of table 6.2.1.1.3.2-2.
Tables 6.2.1.1.3.2 1 and 2 show the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configurations marked T1, T2 and T3 are applied at the point indicated in the Main
behaviour description in Table 6.2.1.1.3.2-3. Cell powers for the E-UTRAN cell are defined in TS 36.508 Table 6.2.2.1-
1 and cell powers for the UTRAN and GERAN cells are defined in TS 36.508 Table 6.2.2.1-1.
A cell marked as OFF in table 6.2.1.1.3.2-2 is a cell that is not configured in the SS.
Table 6.2.1.1.3.2-1: Cell PLMN identities
Cell PLMN name
1 PLMN2
5 PLMN2
13 PLMN14
24 PLMN13

Release 9
3GPP
91
3GPP TS 36.523-1 V9.3.0 (2010-12)
Parameter
name
Unit Cell 1 Cell 5 Cell 13* Cell 24
T0 RS EPRE dBm/15kHz Serving cell OFF
CPICH_Ec dBm/3.84 MHz Serving cell
P-CCPCH dBm/1.28 MHz Serving cell
RF Signal
Level
dBm Serving cell
T1 RS EPRE dBm/15kHz Serving cell OFF
CPICH_Ec dBm/3.84 MHz Non-suitable
Off

P-CCPCH dBm/3.84 MHz Non-suitable
Off

RF Signal
Level
dBm Serving cell
T2 RS EPRE dBm/15kHz OFF OFF
CPICH_Ec dBm/3.84 MHz Non-suitable
Off

P-CCPCH dBm/3.84 MHz Non-suitable
Off

RF Signal
Level
dBm Serving cell Serving cell
T3 RS EPRE dBm/15kHz OFF Serving cell
RF Signal
Level
dBm OFF
*Only minimum uplink cell configuration required (See 6.3.3.2 in 36.508)

U S Message
2 Check: Does the UE send
3-
17
The UE performs Steps 3-17 of the registration
procedure described in TS 36.508 table
4.5.2.3-1.
- - - -
table 6.2.1.1.3.2-2.
- - - -
table 6.2.1.1.3.2-2.
- - - -
21 Check: Does the UE send a CHANNEL
REQUEST on Cell 24?
--> CHANNEL REQUEST 2 P
22-
31
The UE performs Steps 2-11 of the routing
area update procedure described in 36.508
table 6.4.2.9-1.
- - - -
table 6.2.1.1.3.2-2.
- - - -
36 Check: Does the UE send RRC
CONNECTION REQUEST on Cell 5?
--> RRC CONNECTION REQUEST 3 P
37-
47
area update procedure described in TS 36.508
Table 6.4.2.8-1.
- - - -

None
Release 9
3GPP
92
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.1.2 Inter-RAT PLMN Selection / Selection of correct RAT for UPLMN / Automatic
mode
(1)
with { UE i n Aut omat i c net wor k sel ect i on mode and UPLMN and OPLMN cel l s avai l abl e on E- UTRAN and
UTRAN}
ensure that {
then { UE sel ect s a t he hi ghest pr i or i t y UPLMN and RAT combi nat i on and UE at t empt s t o at t ach on
}

(2)
with { UE i n Aut omat i c net wor k sel ect i on mode and UPLMN and OPLMN cel l s avai l abl e on E- UTRAN and
UTRAN}
ensure that {
when { UE r et ur ns t o cover age}
then { UE sel ect s a t he hi ghest pr i or i t y VPLMN and RAT combi nat i on and UE at t empt s t o at t ach on
}

References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1 and
4.4.3.1.1.
[TS 23.122, clause 4.4.3.1]
...
[TS 23.122, clause 4.4.3.1.1]
System Simulator
- 3 cells are used: 2 cells belong to E-UTRAN and 1 cell belongs to UTRAN. The cells are configured as
specified in TS 36.508 clause 4.4.1.4 and Table 4.4.2-2.
Release 9
3GPP
93
3GPP TS 36.523-1 V9.3.0 (2010-12)
UE
technology
Comment
EF
PLMNwAcT
1 PLMN13 E-UTRAN
2 PLMN14 UTRAN
EF
OPLMNwAcT
1 PLMN2 All
2 PLMN14 UTRAN
3 PLMN13 E-UTRAN

Preamble
conditions. Subsequent configuration marked T1 is applied at the point indicated in the Main behaviour description in
Table 6.2.1.2.3.2-3. Cell powers for the E-UTRAN cell are defined in TS36.508 Table 6.2.2.1-1 and cell powers for the
UTRAN cells are defined in TS 36.508 Table 6.2.2.1-1.
Cell PLMN name
1 PLMN2
5 PLMN14
12 PLMN13

Parameter
name
Unit Cell 1* Cell 5 Cell 12
T0 RS EPRE dBm/15kHz Serving cell Serving cell
T1 RS EPRE dBm/15kHz Serving cell Non-suitable
Off

Release 9
3GPP
94
3GPP TS 36.523-1 V9.3.0 (2010-12)
U S Message
3-
17
4.5.2.3-1.
- - - -
table 6.2.1.2.3.2-2.
- - - -
20 Check: Does the UE send a RRC
21-
31
Table 6.4.2.8-1.
- - - -

None
6.2.1.3 Inter-RAT PLMN Selection / Selection of correct PLMN and RAT in shared
network environment / Automatic mode
(1)
with { UE i n Aut omat i c net wor k sel ect i on mode and shar ed OPLMN cel l s avai l abl e on E- UTRAN and
UTRAN }
ensure that {
t he sel ect ed cel l and PLMN and when successf ul l y r egi st er ed i ndi cat es t he cor r ect PLMN t o t he
user . }
}

(2)
with { UE i n Aut omat i c net wor k sel ect i on mode and shar ed OPLMN cel l s avai l abl e on E- UTRAN and
UTRAN }
ensure that {
t he sel ect ed cel l and PLMN and when successf ul l y r egi st er ed i ndi cat es t he cor r ect PLMN t o t he
user . }

References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3, 4.4.3.1
and 4.4.3.1.1.
[TS 23.122, clause 4.4.3]
[TS 23.122, clause 4.4.3.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 subclause 4.5.2) attempts to perform a Location Registration.

Release 9
3GPP
95
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 23.122, clause 4.4.3.1.1]
System Simulator
- 3 cells are used: 2 cells belong to E-UTRAN and 1 cell belongs to UTRAN. The cells are configured as
UE
- The HPLMN is PLMN1.
technology
Comment
EF
OPLMNwAcT
1 PLMN2 E-UTRAN
2 PLMN2 UTRAN
3 PLMN14 UTRAN
4 PLMN13 E-UTRAN

Preamble
conditions. Subsequent configuration marked T1 is applied at the point indicated in the Main behaviour description in
Table 6.2.1.3.3.2-3. Cell powers for the E-UTRAN cell are defined in TS 36.508 Table 6.2.2.1-1 and cell powers for the
UTRAN cells are defined in TS 36.508 Table 6.2.2.1-1.
Cell PLMN name
1 PLMN13,PLMN2
5 PLMN14, PLMN13
12 PLMN13, PLMN14

Release 9
3GPP
96
3GPP TS 36.523-1 V9.3.0 (2010-12)
Parameter
name
Unit Cell 1 Cell 5 Cell 12*
T1 RS EPRE dBm/15kHz Non-suitable
Off
Serving cell

U S Message
3-
17
4.5.2.3-1.
- - - -
table 6.2.1.3.3.2-2.
- - - -
20 Check: Does the UE send a RRC
21-
31
Table 6.4.2.8-1.
- - - -

SEQUENCE {

plmn-Identity[1] PLMN13.
plmn-Identity[2] PLMN2
}
}
}

Table 6.1.2.10.3.3-2: Master Information Block (Cell 5, all steps, Table 6.2.1.3.3.2-3)
Derivation path: 34.108 Section 6.1.0a
- Supported PLMN types
- PLMN type GSM-MAP
- PLMN identity PLMN14
- Multiple PLMN List
- PLMN identity with Optional MCC[1] PLMN13

Release 9
3GPP
97
3GPP TS 36.523-1 V9.3.0 (2010-12)
SEQUENCE {

}
}
}

Table 6.2.1.3.3-4: RRCConnectionSetupComplete (Step 5, Table 6.2.1.3.3.2-3)
Derivation Path: 36.331 clause 6.2.2
c1 CHOICE {
selectedPLMN-Identity 2 PLMN2

Table 6.2.1.3.3-5: INITIAL DITRECT TRANSFER (Step 23, Table 6.2.1.3.3.2-3)
PLMN identity PLMN14

6.2.1.4 Inter-RAT PLMN Selection / Selection of correct RAT from the OPLMN list /
Manual mode
(1)
with { UE i n Manual net wor k sel ect i on mode and OPLMN cel l s avai l abl e on E- UTRAN and GERAN}
ensure that {
when { t he USER sel ect s an OPLMN}
then { UE sel ect s a t he hi ghest pr i or i t y RAT f or t he OPLMN and UE at t empt s t o at t ach on t he
sel ect ed cel l and when successf ul l y r egi st er ed i ndi cat es t he PLMN t o t he user . }
}

(2)
with { UE i n Manual net wor k sel ect i on mode and OPLMN cel l s avai l abl e on E- UTRAN and GERAN}
ensure that {
when { t he USER sel ect s an OPLMN and RAT combi nat i on}
then {UE at t empt s t o at t ach on t he sel ect ed OPLMN and RAT combi nat i on and when successf ul l y
r egi st er ed i ndi cat es t he PLMN t o t he user . }
}

References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1.2.
[TS 23.122, clause 4.4.3.1.2]
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. An MS
which supports GSM COMPACT shall also indicate GSM COMPACT PLMNs (which use PBCCH).
If displayed, PLMNs meeting the criteria above are presented in the following order:
Release 9
3GPP
98
3GPP TS 36.523-1 V9.3.0 (2010-12)
i)- either the HPLMN (if the EHPLMN list is not present or is empty) or, if one or more of the EHPLMNs are
available then based on an optional data field on the SIM either only the highest priority available EHPLMN is
to be presented to the user or all available EHPLMNs are presented to the user in priority order. If the data field
is not present on the SIM, then only the highest priority available EHPLMN is presented;
ii)- PLMN/access technology combinations contained in the " User Controlled PLMN Selector with Access
Technology " data file in the SIM (in priority order);
iii)- PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access
iv)- other PLMN/access technology combinations with received high quality signal in random order;
v)- 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 TAs
for roaming", "forbidden LAs for regional provision of service", "forbidden TAs for regional provision of service",
"forbidden PLMNs for GPRS service" and "forbidden PLMNs" lists.
NOTE 1: 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 selected by the user is only used for initial
registration on the selected 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, and is only used for initial
registration.
System Simulator
- 3 cells are used: 2 cells belong to E-UTRAN and 1 cell belongs to GERAN. The cells are configured as
UE
technology
Comment
EF
OPLMNwAcT
1 PLMN2 E-UTRAN
2 PLMN2 GERAN
3 PLMN2 UTRAN
4 PLMN13 E-UTRAN
Preamble
- The UE is equipped with a USIM with default settings except for the ones specified in table 6.2.1.4.3.11 then
the UE is attached to PLMN1 and the UE is set to Manual PLMN selection mode before it is switched off.
conditions. Cell powers for the E-UTRAN cell are defined in TS36.508 Table 6.2.2.1-1 and cell powers for the
GERAN cell are defined in TS 36.508 Table 6.2.2.1-1.
Release 9
3GPP
99
3GPP TS 36.523-1 V9.3.0 (2010-12)
Cell PLMN name
1 PLMN2
12 PLMN13
24 PLMN2

Parameter
name
Unit Cell 1 Cell 12* Cell 24
RF Signal
Level
dBm Serving cell

U S Message
2 Make the UE display the list of available
PLMNs.
- - - -
3 PLMN2 (E-UTRAN) is selected. - - - -
RRCConnectionRequest on cell 1?
--> RRCConnectionRequest 1,2 P
5-
19
4.5.2.3-1.
- - - -
20 Check: Is PLMN2 indicated by the UE? - - 1,2 P

None
6.2.2 Inter-RAT cell selection
6.2.2.1 Inter-RAT cell selection / From E-UTRA RRC_IDLE to UTRA_Idle / Serving
cell becomes non-suitable
(1)
ensure that {
when { t he ser vi ng cel l becomes non- sui t abl e and t her e i s a sui t abl e UTRA nei ghbour cel l }
then { UE sel ect s t he sui t abl e UTRA nei ghbour cel l }

(2)
ensure that {
when { t he ser vi ng cel l becomes bar r ed and t her e i s a sui t abl e UTRA nei ghbour cel l }
then { UE sel ect s t he sui t abl e UTRA nei ghbour cel l }
}

Not e: ( SSer vi ngCel l <0 or bar r ed) coni dt i on i s f or r el 8; ( Sr xl ev<0 or Squal <0 or bar r ed) condi t i on
i s f or r el 9.
References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3,5.2.1,
5.2.3.2 and 5.3.1. TS 25.304, clause 5.2.3.2.
Release 9
3GPP
100
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 36.304, clause 4.1]
The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of
[5].
performed.
[TS 36.304, clause 4.3]
suitable cell:
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.
- The cell is part of either:
- the selected PLMN, or:
- the registered PLMN, or:
- a PLMN of the Equivalent PLMN list
according to the latest information provided by NAS:
- The cell is not barred, see subclause 5.3.1;
- The cell is part of at least one TA that is not part of the list of "forbidden tracking areas for roaming" [4], which
belongs to a PLMN that fulfils the first bullet above;
- The cell selection criteria are fulfilled, see subclause 5.2.3.2;
- For a CSG cell, the CSG ID is part of the allowed CSG list of the UE.
If more than one PLMN identity is broadcast in the cell, the cell is considered to be part of all TAs with TAIs
constructed from the PLMN identities and the TAC broadcast in the cell.
barred cell:
A cell is barred if it is so indicated in the system information [3].
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]

Srxlev >0

Where:

Srxlev =Q
rxlevmeas
(Q
rxlevmin
+Q
rxlevminoffset
) - Pcompensation

Where:
Release 9
3GPP
101
3GPP TS 36.523-1 V9.3.0 (2010-12)
Q
rxlevmeas
Q
rxlevmin
Q
rxlevminoffset
rxlevmin
Pcompensation max(P
EMAX
P
UMAX
, 0) (dB)
P
EMAX
EMAX
in [TS 36.101]
P
UMAX

[TS 36.304, clause 5.3.1]
Elements:
In case of multiple PLMNs indicated in SIB1, this IE is common for all PLMNs


- else
The cell selection of another cell may also include a change of RAT.
[TS 25.304, clause 5.2.3.2]
Release 9
3GPP
102
3GPP TS 36.523-1 V9.3.0 (2010-12)
for FDD cells: Srxlev >0 AND Squal >0
for TDD cells: Srxlev >0

Where:
Squal =Q
qualmeas
Qqualmin
Srxlev =Q
rxlevmeas
- Qrxlevmin - Pcompensation

Squal Cell Selection quality value (dB)
Applicable only for FDD cells.
Q
qualmeas
Measured cell quality value. The quality of the received signal expressed in CPICH E
c
/N
0

(dB) for FDD cells. CPICH Ec/N0 shall be averaged as specified in [10]. Applicable only
for FDD cells.
Q
rxlevmeas
Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm)
and P-CCPCH RSCP for TDD cells (dBm).
Qqualmin Minimum required quality level in the cell (dB). Applicable only for FDD cells.
Qrxlevmin Minimum required RX level in the cell (dBm)
Pcompensation max(UE_TXPWR_MAX_RACH P_MAX, 0) (dB)
UE_TXPWR_MAX_RACH Maximum TX power level an UE may use when accessing the cell on RACH (read in
system information) (dBm)
P_MAX Maximum RF output power of the UE (dBm)

System Simulator:
- Cell 1 and Cell 5
UE:
None.
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell 1 (serving cell) according to [18].
Tables 6.2.2.1.3.2-1 & 6.2.2.1.3.2-2 illustrates the downlink power levels and other changing parameters to be applied
for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and " T3" are
applied at the points indicated in the Main behaviour description in Table 6.2.2.1.3.2-3.
Release 9
3GPP
103
3GPP TS 36.523-1 V9.3.0 (2010-12)
T1
Cell-specific RS EPRE dBm -120 Srxlev
Cell 1
<0
Srxlev* dB -10 Cell 5 becomes the strongest cell
T2 Cell-specific RS EPRE dBm -60
T3
Cell 1
>Srxlev
Cell 5
>0
Srxlev* dB 50
cellBarred - Barred Serving cell becomes barred
Note: Srxlev is calculated in the UE

T1 CPICH_Ec dBm/3.84 MHz -70 Srxlev
Cell 5
>0,for FDD
P-CCPCH dBm/1.28 MHz -72 Srxlev
Cell 5
>0,for TDD
Srxlev* dB 9 Cell 5 becomes the strongest cell or
the suitable cell
T2 CPICH_Ec dBm/3.84 MHz OFF
P-CCPCH dBm/1.28 MHz OFF
Cell 5
>0,for FDD
P-CCPCH dBm/1.28 MHz -72 Srxlev
Cell 5
>0,for TDD
Srxlev* dB 9

U - S Message
6.2.2.1.3.2-1 & Cell 5 power level is set
according to row "T1" in table 6.2.2.1.3.2-2.
- - - -
indicate that the UE is camped on UTRAN Cell
5?
NOTE: The UE performs a RAU procedure
- - 1 -
- - - -
4 Generic test procedure in TS 36.508
subclause 6.4.2.7A is performed and the UE
will camped on E-UTRAN Cell 1.
- - - -
5 Void - - - -
6 SS changes Cell 5 power level according to
row "T3" in table 6.2.2.1.3.2-2 and modifies
System Information so that Cell 1 becomes
barred according to row "T3" in table
6.2.2.1.3.2-1. The SS transmits a Paging
message including systemInfoModification.
<-- Paging - -
6A Void - - - -
5?
NOTE: The UE performs a RAU procedure.
- - 2 -

Release 9
3GPP
104
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.2.1.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble and steps 1 to 5, Table
6.2.2.1.3.2-3)
q-Rxlevmin -55 (-110 dBm)
q-Rxlevminoffset Not present
}
}

}

cellBarred barred
}
}
0

}

6.2.2.2 Inter-RAT cell selection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS
Packet_idle / Serving cell becomes non-suitable
(1)
ensure that {
when { t he ser vi ng cel l becomes non- sui t abl e and t her e i s a sui t abl e GSM nei ghbour cel l }
then { UE sel ect s t he sui t abl e GSM nei ghbour cel l }

(2)
ensure that {
when { t he ser vi ng cel l becomes bar r ed and t her e i s a sui t abl e GSM nei ghbour cel l }
then { UE sel ect s t he sui t abl e GSM nei ghbour cel l }
}

i s f or r el 9.

Release 9
3GPP
105
3GPP TS 36.523-1 V9.3.0 (2010-12)
References: The conformance requirements covered in the current TC are specified in: TS 36.304, clause 4.1, 4.3,5.2.1,
5.2.3.2, 5.3.1, 43.022, clause 3.6 and TS 45.008, clause 6.4.
[TS 36.304, clause 4.1]
The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of
[5].
performed.
[TS 36.304, clause 4.3]
suitable cell:
barred cell:
A cell is barred if it is so indicated in the system information [3].
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]

Srxlev >0

Where:
Release 9
3GPP
106
3GPP TS 36.523-1 V9.3.0 (2010-12)

Srxlev =Q
rxlevmeas
(Q
rxlevmin
+Q
rxlevminoffset
) - Pcompensation

Where:
Q
rxlevmeas
Q
rxlevmin
Q
rxlevminoffset
rxlevmin
Pcompensation max(P
EMAX
P
UMAX
, 0) (dB)
P
EMAX
EMAX
in [TS 36.101]
P
UMAX

[TS 36.304, clause 5.3.1]
Elements:
In case of multiple PLMNs indicated in SIB1, this IE is common for all PLMNs


- else
The cell selection of another cell may also include a change of RAT.
[TS 43.022, clause 3.6]
Release 9
3GPP
107
3GPP TS 36.523-1 V9.3.0 (2010-12)
The MS uses a "path loss criterion" parameter C1 to determine whether a cell is suitable to camp on. C1 depends on 4
parameters:
i) The received signal level (suitably averaged);
ii) The parameter RXLEV_ACCESS_MIN, which is broadcast as system information, and is related to the
minimum signal that the operator wants the network to receive when being initially accessed by an MS;
iii) The parameter MS_TXPWR_MAX_CCH, which is also broadcast as system information, and is the maximum
power that an MS may use when initially accessing the network;
iv) The maximum power of the MS.
The formula for determining C1 is given in 3GPP TS 45.008.
Use of the parameter C1 enables the MS to determine whether communication is possible with the network in the
absence of interference. However because of the possibility of interference degrading the communications, an additional
safeguard is used. This is to monitor the success rate of the MS in decoding signalling blocks of the paging subchannel.
If there is a downlink signalling failure, i.e. the success rate drops too low, this indicates probable interference on the
downlink, and the MS attempts to find another suitable cell. Downlink signalling failure monitoring is specified in
3GPP TS 45.008.
In order to optimize cell reselection, additional cell reselection parameters can be broadcast as system information of
each cell. The cell reselection process employs a parameter C2 which depends on these parameters.
The parameters used to calculate C2 are as follows:
i) CELL_RESELECT_OFFSET (see subclause 3.5.2.2);
ii) PENALTY_TIME;
When the MS places the cell on the list of the strongest carriers as specified in 3GPP TS 45.008, it starts a timer
which expires after the PENALTY_TIME. This timer will be reset when the cell is taken off the list. For the
duration of this timer, C2 is given a negative offset. This will tend to prevent fast moving MSs from selecting the
cell.
iii) TEMPORARY_OFFSET;
This is the amount of the negative offset described in (ii) above. An infinite value can be applied, but a number
of finite values are also possible.
The permitted values of these parameters and the way in which they are combined to calculate C2 are defined in 3GPP
TS 45.008.
Instead of the parameter C2, a GPRS MS applies the corresponding GPRS parameter if provided.
[TS 45.008, clause 6.4]
The path loss criterion parameter C1 used for cell selection and reselection is defined by:
C1 =(A - Max(B,0))
where
A = RLA_C - RXLEV_ACCESS_MIN
B = MS_TXPWR_MAX_CCH - P
Release 9
3GPP
108
3GPP TS 36.523-1 V9.3.0 (2010-12)
except for the class 3 DCS 1 800 MS where:
B = MS_TXPWR_MAX_CCH +POWER OFFSET - P
RXLEV_ACCESS_MIN = Minimum received signal level at the MS required for access to the
system.
MS_TXPWR_MAX_CCH = Maximum TX power level an MS may use when accessing the system
until otherwise commanded.
POWER OFFSET = The power offset to be used in conjunction with the MS TXPWR
MAX CCH parameter by the class 3 DCS 1 800 MS.
P = Maximum RF output power of the MS.
All values are expressed in dBm.
The path loss criterion (3GPP TS 43.022) is satisfied if C1 >0.
System Simulator:
- Cell 1 and Cell 24
UE:
None.
Preamble:
for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and "T3" are
T1
Cell 1
<0
Srxlev* dB -10 Cell 24 becomes the strongest cell
T2 Cell-specific RS EPRE dBm -60
T3
Cell 1
>Srxlev
Cell 24
>0
Srxlev* dB 50
cellBarred - Barred Serving cell becomes barred

T1 RF Signal Level dBm -80 Srxlev
Cell 24
>0
C1* dB 20 Cell 24 becomes the strongest cell
T2 RF Signal Level dBm OFF
T3 RF Signal Level dBm -80 Srxlev
Cell 24
>0
C1* dB 20
Note: C1 is calculated in the UE

Release 9
3GPP
109
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
6.2.2.2.3.2-1 & cell 24 power level is set
- - - -
indicate that the UE is camped on GERAN Cell
24?
- - 1 -
- - - -
subclause 6.4.2.7A is performed and the UE
will camped on E-UTRAN Cell 1.
- - - -
5 Void - - - -
6 SS changes Cell 24 power level according to
row "T3" in table 6.2.2.2.3.2-2 and modifies
System Information so that Cell 1 becomes
barred according to row "T3" in table
6.2.2.2.3.2-1. The SS transmits a Paging
message including systemInfoModification.
<-- Paging - -
24?
- - 2 -

Table 6.2.2.2.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble and steps 1 to 5, Table
6.2.2.2.3.2-3)
}
}

cellBarred barred
}
}
0

}

Release 9
3GPP
110
3GPP TS 36.523-1 V9.3.0 (2010-12)
}

6.2.2.3 Inter-RAT Cell selection / From E-UTRA RRC_IDLE to HRPD Idle / Serving
(1)
ensure that {
when { t he ser vi ng cel l becomes non- sui t abl e and t her e i s a sui t abl e nei ghbour HRPD cel l ( S>0) }
then { UE sel ect s t he sui t abl e nei ghbour HRPD cel l }
}

i s f or r el 9.

TS 36.304, clause 4.1, 5.2.1, and 5.2.3.2.
[TS 36.300, clause 10.1.1.1]
Cell selection:
is not barred;
[TS 36.304, clause 4.1]
[5].
Release 9
3GPP
111
3GPP TS 36.523-1 V9.3.0 (2010-12)
performed.
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]

Srxlev >0

Where:

Srxlev =Q
rxlevmeas

Where:
Q
rxlevmeas
Qrxlevminoffset Offset to the signalled Qrxlevmin taken into account in the Srxlev
Pcompensation [FFS]

System Simulator:
- Cell 1 is a cell on E-UTRA
- Cell 15 is a cell on HRPD
UE:
None
Preamble:
various time instants of the test execution. Subsequent configurations marked "T1" and T2 are applied at the points
Release 9
3GPP
112
3GPP TS 36.523-1 V9.3.0 (2010-12)

T1
or/Ioc dB - -5 Cell 15 is on
Ioc dBm/1.23 MHz - -55
Pilot Ec/Io (Note 1) dB - -6
Cell-specific RS EPRE dBm/15 KHz -60
T2
Cell-specific RS EPRE dBm/15 kHz -120 - Srxlev
Cell 1
<0 and Cell 15 becomes the
strongest cell Srxlev* dB -10
or/Ioc dB - -5

Note 1: This parameter is not directly settable, but is derived by calculation from the other parameters set by the
SS.

U - S Message
level of Cell 15 according to "T1" in 6.2.2.3.3.2-
1.
- - - -
1a SS waits [10s] to allow the UE to read the
system information
- - - -
level of Cell 1 according to "T2" in 6.2.2.3.3.2-
1.
- - - -
3 Check: Does the UE transmit an Access Probe
on Cell 15?
--> Access Probe 1 P

Table 6.2.2.3.3.3-1 SystemInformationBlockType1 to Cell 1 (Preamble and all steps, table 6.2.2.3.3.2-1)
Derivation path: 36.508 table clause 4.4.3.2
}
}

Release 9
3GPP
113
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.2.3.3.3-2: SystemInformationBlockType8 to Cell 1 (Preamble and all steps, table 6.2.2.3.3.2-
1)
Derivation path: 36.508 table 4.4.3.3
cdma2000-SystemTimeInfo SEQUENCE {
cdma-EUTRA-Synchronisation TRUE
cdma-SystemTime CHOICE {
cdma-SynchronousSystemTime A valid value as per TS
36.331 and calculated by
the SS

}
}
searchWindowSize 5
hrpd-Parameters SEQUENCE {
hrpd-CellReselectionParameters SEQUENCE {
hrpd-BandClassList SEQUENCE (SIZE
(1..maxCDMA -BandClass)) OF SEQUENCE {
The same number of
entries as the configured
HRPD carriers

hrpd-BandClass Band Class of frequency
under test
[Set according to
specific test case]

hrpd-CellReselectionPriority 5 [3 is applicable
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]

threshX-High 30(-30) INTEGER (0..63)
threshX-Low 32(-32) INTEGER (0..63)
}
t-ReselectionCDMA-HRPD 0 INTEGER (0..7)
}
}
}

6.2.2.4 Inter-RAT Cell selection / From E-UTRAN RRC_IDLE to 1xRTT idle / Serving
(1)
ensure that {
when { t he ser vi ng cel l becomes non- sui t abl e and
t her e i s a sui t abl e nei ghbour 1xRTT cel l ( S>0) }
then { UE sel ect s t he sui t abl e nei ghbour 1xRTT cel l }
}

i s f or r el 9.

TS 36.304, clause 4.1, 5.2.1, and 5.2.3.2.
[TS 36.300, clause 10.1.1.1]
Cell selection:
Release 9
3GPP
114
3GPP TS 36.523-1 V9.3.0 (2010-12)
is not barred;
[TS 36.304, clause 4.1]
the chosen cell and as outcome of a successful Location Registration the selected PLMN becomes the registered PLMN.
performed.
[TS 36.304, clause 5.2.1]
[TS 36.304, clause 5.2.3.2]

Srxlev >0

Where:

Srxlev =Q
rxlevmeas

Where:
search for a higher priority PLMN while camped normally in a VPLMN. During this periodic search for higher priority
PLMN the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher
priority PLMN.
Q
rxlevmeas
Qrxlevminoffset Offset to the signalled Qrxlevmin taken into account in the Srxlev
Pcompensation [FFS]

Release 9
3GPP
115
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
- Cell 1 is a cell on E-UTRA
- Cell 19 is a cell on 1xRTT
UE:
None.
Preamble:
various time instants of the test execution. The configurations marked "T1" and T2 are applied at the point indicated
in the Main behaviour description in Table 6.2.2.4.3.2-2

T1 or/Ioc dB - -15 Cell 19 is on
Pilot Ec/ Ior -7
Ioc dBm - -75
CPICH_Ec/Io (Note 1) dB - -22
Cell-specific RS EPRE dBm/15 KHz -75 -
T2 or/Ioc dB - 0 Increase pilot power of 1xRTT cell such
that S
nonServingCell,
of Cell 19 >Thresh
1xRTT,
high

Pilot Ec/ Ior dB - -7
Cell-specific RS EPRE dBm/15 KHz -75 -
SS.

U - S Message
levels according to row T1 in Table
6.2.2.3.3.2-1.
- - - -
1a SS waits [10s] to allow the UE to read the
system information.
- - - -
levels according to row "T2" in Table
6.2.2.3.3.2-1.
- - - -
on Cell 19?

Release 9
3GPP
116
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.2.4.3.3-1 SystemInformationBlockType1 to Cell 1 (Preamble and all steps, table 6.2.2.4.3.2-1)
}
}

Release 9
3GPP
117
3GPP TS 36.523-1 V9.3.0 (2010-12)
1)
the SS

}
}

oneXRTT-Parameters SEQUENCE {} Not present HRPD
oneXRTT-Parameters SEQUENCE { 1XRTT
oneXRTT-CSFB-RegistrationInfo SEQUENCE {
oneXRTT-CSFB-RegistrationAllowed FFS BOOLEAN
oneXRTT-RegistrationParameters SEQUENCE FFS
{}

}
oneXRTT-LongCodeState FFS BIT STRING
(SIZE (42))
OPTIONAL

oneXRTT-CellReselectionParameters
SEQUENCE {
oneXRTT-BandClassList SEQUENCE (SIZE
(1..maxCDMA -BandClass)) OF SEQUENCE { The same number of
1xRTT carriers

oneXRTT BandClass FFS ENUMERATED {
bc0, bc1, bc2,
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2, spare1,
...}

oneXRTT-CellReselectionPriority FFS [3 is applicable
threshX-High FFS INTEGER (0..63)
threshX-Low FFS INTEGER (0..63)
oneXRTT-NeighborCellList SEQUENCE (SIZE
(1..16)) OF SEQUENCE {

bandClass FFS ENUMERATED {
bc0, bc1, bc2,
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2, spare1,
...}

Release 9
3GPP
118
3GPP TS 36.523-1 V9.3.0 (2010-12)
frequencyList SEQUENCE (SIZE (1..16)) OF
SEQUENCE {
FFS INTEGER
(0..2047)

frequency FFS
cellIdList SEQUENCE (SIZE (1..16)) OF
{INTEGER (0..maxPNOffset) }
FFS INTEGER
(0..maxPNOffset)

}
}
t-ReselectionCDMA-OneXRTT FFS INTEGER (0..7),
}

6.2.2.5 Cell selection / No USIM
(1)
with { UE f i t t ed wi t h no SI M/ USI M }
ensure that {
when { UE i s swi t ched on }
then { UE camps on a non- LTE cel l }
}

(2)
with { UE f i t t ed wi t h no SI M/ USI M and camped on a non- LTE cel l }
ensure that {
when { UE i s r equest ed t o make an emer gency cal l }
then { UE t r ansmi t s an RRC CONNECTI ON REQUEST message }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 4.1.
[TS 36.304, clause 4.1]
A UE which is not equipped with a valid USIM (i.e. no UICC or SIM only), or which shall consider the USIM as
invalid for EPS services as defined in [15] and [16] (e.g. due to a LR reject #3, #6, #7, #8) shall disable all its E-
UTRAN capabilities until switching off or the UICC containing the USIM is removed.
System Simulator:
UE:
- The UE is not equipped with a USIM.
Preamble:
Release 9
3GPP
119
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
2 Wait for 60s for the UE to complete cell
selection. E-UTRA cell is more powerful than
UTRA cell
- - - -
3 Cause the UE to originate Emergency call.
(see Note 1)
- - - -
4 Check: Does the UE transmit an RRC
CONNECTION REQUEST message on Cell
5?
--> RRC CONNECTION REQUEST 1, 2 P
5 The SS transmits an RRC CONNECTION
SETUP message on Cell 5.
<-- RRC CONNECTION SETUP - -
6 The UE transmits an RRC CONNECTION
SETUP COMPLETE message on Cell 5.
--> RRC CONNECTION SETUP
COMPLETE
- -
7 The UE transmits an INITIAL DIRECT
TRANSFER message on Cell 5.
This message includes a CM SERVICE
REQUEST message.
--> INITIAL DIRECT TRANSFER - -
8 The SS transmits a DOWNLINK DIRECT
This message includes a CM SERVICE
ACCEPT message.
<-- DOWNLINK DIRECT TRANSFER - -
9 The UE transmits an UPLINK DIRECT
This message includes an EMERGENCY
SETUP message.
--> UPLINK DIRECT TRANSFER - -
This message includes a CALL PROCEEDING
message.
11 The SS transmits a RADIO BEARER SETUP
message on Cell 5.
<-- RADIO BEARER SETUP - -
12 The UE transmits a RADIO BEARER SETUP
COMPLETE message on Cell 5.
--> RADIO BEARER SETUP
COMPLETE
- -
This message includes an ALERTING
message.
This message includes a CONNECT message.
This message includes a CONNECT
ACKNOWLEDGE message.
Note 1: The request is assumed to be triggered by AT command D.

None.
6.2.2.6 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-
UTRA_RRC_IDLE / Serving cell becomes non-suitable
(1)
with { UE i n GSM/ GPRS Regi st er ed st at e and no RR connect i on }
ensure that {
when { t he ser vi ng cel l becomes non- sui t abl e and t her e i s a sui t abl e E- UTRA nei ghbour cel l }
then { UE sel ect s t he sui t abl e E- UTRA nei ghbour cel l }
Release 9
3GPP
120
3GPP TS 36.523-1 V9.3.0 (2010-12)

(2)
ensure that {
when { t he ser vi ng cel l becomes bar r ed and t her e i s a sui t abl e E- UTRA nei ghbour cel l }
}

i s f or r el 9.

References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.4 .
...
[TS 45.008, clause 6.4]
C1 =(A - Max(B,0))
where
system.
System Simulator:
UE:
None.
Preamble:
for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after the
preamble, while rows 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.
Release 9
3GPP
121
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.2.6.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell

T0
Cell-specific RS EPRE dBm/15kHz -120 Srxlev
Cell 1
<0
Qrxlevmin dBm -110
Srxlev* dB N/A
T1
Cell-specific RS EPRE dBm/15kHz -70
Srxlev* dB 30 Srxlev
Cell 1
>THRESH_E-
UTRAN_high

Table 6.2.2.6.3.2-2: Time instances of cell power level and parameter changes for GERAN cell

T0
RF Signal Level dBm -80
RXLEV_ACCESS_MIN dBm -101
C1* dB 21
T1
RF Signal Level dBm OFF
RXLEV_ACCESS_MIN dBm N/A
C1* dB N/A

U - S Message
level of Cell 1 according to row T1 in Table
6.2.2.6.3.2-1 & cell 24 power level is set
according to row T1 in table 6.2.2.6.3.2-2
- - - -
Cell 1?
- - 1 -
Note: GERAN cell priority is not allocated, hence it will be considered as the less than all allowed values of 1 to 8.

None.
6.2.2.7 Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-
UTRA_RRC_IDLE ,when the serving cell is barred.
(1)
ensure that {
when { t he ser vi ng cel l becomes bar r ed and t her e i s a sui t abl e E- UTRA nei ghbour cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.4 and 6.6.1,
&TS 43.022 clause 3.2.1.
...
[TS 45.008, clause 6.4]
Release 9
3GPP
122
3GPP TS 36.523-1 V9.3.0 (2010-12)
C1 =(A - Max(B,0))
where
system.
[TS 45.008, clause 6.6.1]
The MS shall attempt to decode the full BCCH data of the serving cell at least every 30 seconds or at least as often as
possible in the case that system information scheduling period exceeds 30 seconds.
If SI13 is broadcast, the MS supporting change mark in SI13 (See 3GPP TS 44.018) is only required to confirm system
information on the BCCH of the serving cell if indicated by change mark in SI13.
[TS 43.022, clause 3.2.1]
The choice of such a suitable cell for the purpose of receiving normal service is referred to as "normal camping". There
are various requirements that a cell must satisfy before an MS can perform normal camping on it:
i) It should be a cell of the selected PLMN or, if the selected PLMN is equal to the last registered PLMN, an
equivalent PLMN;
ii) It should not be "barred" (see subclause 3.5.1);
System Simulator:
UE:
None.
Preamble:
for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after the
preamble, while rows marked "T1" are to be applied subsequently. The exact instants on which these values shall be
Release 9
3GPP
123
3GPP TS 36.523-1 V9.3.0 (2010-12)

T0
Cell 1
<0
Qrxlevmin dBm -110
Srxlev* dB N/A
T1
Cell 1
>THRESH_E-
UTRAN_high


T0
C1* dB 21
T1
C1* dB 21
cellBarred Barred

U - S Message
1 SS changes cell 1 power level according to
row "T1" in table 6.1.2.2.7.3.2-1 & changes cell
24 signal level and SI2 IE cellBarred according
to row "T1" in table 6.2.2.7.3.2-2.
- - - -
procedure in TS 36.508 subclause 6.4.2.7A
Cell 1?
- - 1 -

Table 6.2.2.7.3.3-1: RACH Control Parameters of SI2, SI3 and SI4 for Cell 24(step 1, Table 6.2.2.7.3.2-3)
Derivation Path: 51.010-1 clause 40.2.1.1
RACH Control Parameters{
Cell Barred for Access Barred
}

Table 6.2.2.7.3.3-2: SI 13 Rest Octets of , SI13 for Cell 24(step 1, Table 6.2.2.7.3.2-3)
Derivation Path: 51.010-1 clause 40.2.1.1
BCCH_CHANGE_MARK { 001
SI_CHANGE_FIELD 0011
}

Release 9
3GPP
124
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3 Inter-RAT cell reselection
6.2.3.1 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS
Packet_Idle
(1)
ensure that {
pr i or i t y i nt er - RAT( GERAN) f r equency f or Tr esel ect i on
RAT
}
then { UE r esel ect s t he cel l whi ch bel ongs t o t he hi gher pr i or i t y i nt er - RAT( GERAN) f r equency }
}

(2)
ensure that {
pr i or i t y i nt er - RAT( GERAN) f r equency f or Tr esel ect i on
RAT
}
then { UE r esel ect s t he cel l whi ch bel ongs t o t he l ower pr i or i t y i nt er - RAT( GERAN) f r equency }
}

5.2.4.2 and 5.2.4.5.
[TS 36.304, clause 5.2.4.1]
priority frequency (i.e. lower than the eight network configured values). The UE shall delete priorities provided by
dedicated signalling when:
information.
[TS 36.304, clause 5.2.4.2]
Release 9
3GPP
125
3GPP TS 36.523-1 V9.3.0 (2010-12)
- If S
intrasearch
ServingCell
>S
intrasearch
measurements.
- If S
ServingCell
<=S
intrasearch,
or S
intrasearch
measurements.
- If S
nonintrasearch
ServingCell
>S
nonintrasearch
- If S
ServingCell
<=S
nonintrasearch
or S
nonintrasearch
according to [10].
Where S
ServingCell
[TS 36.304, clause 5.2.4.5]
Criteria 1: the S
nonServingCell,x
x, high
Treselection
RAT
;
be performed if:
be performed if:
- No cell on serving frequency or on an equal priority E-UTRAN frequency or on a higher priority E-UTRAN
frequency or inter-RAT frequency than serving frequency fulfills the criteria 1; and
- S
ServingCell
<Thresh
serving, low
and the S
nonServingCell,x
x, low
RAT
; and
or if:
- there are no candidate cells for reselection on serving frequency according to 5.2.4.4 or 5.3.1.
nonServingCell,x
nonServingCell,x
of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured From the evaluated cell.
Release 9
3GPP
126
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
UE:
None.
Preamble:
for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and "T3" are
Table 6.2.3.1.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cells
T1
Cell 1
>0
Cell 1
>Srxlev
Cell 24
>0
T2
Cell 1
>20
Srxlev* dB 46
T3 Cell-specific RS EPRE dBm/15kHz -100 Srxlev
Cell 1
<20 [threshServingLow]

Table 6.2.3.1.3.2-2: Time instances of cell power level and parameter changes for GERAN cells
T1 RF Signal Level dBm -80 OFF Srxlev
Cell 24
>4[threshX-High]
C1* dB 21 N/A
T2 RF Signal Level dBm OFF OFF
C1* dB N/A 21
T3 RF Signal Level dBm OFF -80 Srxlev
Cell 25
>4[threshX-Low]

Release 9
3GPP
127
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 The SS changes Cell 1 according to the row
"T1" in table 6.2.3.1.3.2-1and Cell 24 level
according to the row "T1" in table 6.2.3.1.3.2-2.
- - - -
24?
- - 1 -
3 Void - - - -
4 Wait for [5 s]. - - - -
according to the row "T2" in table 6.2.3.1.3.2-2
- - - -
6 UE reselects Cell 1 and completes tracking
area update procedure.
- - - -
7 Wait for [5 s]. - - - -
- - - -
9 Void - - - -
25?
- - 2 -

Table 6.2.3.1.3.3-1: SystemInformationBlockType3 cell 1 (preamble and all steps, Table 6.2.3.1.3.2-3)
s-NonIntraSearch Not present
threshServingLow 10 Actual value =20
dB

cellReselectionPriority 4 A middle value in
the range has
been selected.

}
}

Release 9
3GPP
128
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.1.3.3-2: SystemInformationBlockType7 cell 1 (preamble and all steps, Table 6.2.3.1.3.2-3)
t-ReselectionGERAN 7 INTEGER (0..7)
speedDependentScalingParameters SEQUENCE
{}
Not present
carrierFreqsInfoList SEQUENCE (SIZE
(1..maxGNFG)) OF SEQUENCE {

carrierFreqsGERAN SEQUENCE [n] {
startingARFCN Same as cell 24
bandIndicator Same as cell 24
followingARFCNs CHOICE {
equallySpacedARFCNs SEQUENCE {
arfcn-Spacing Same as cell 24
numberOfFollowingARFCNs Same as cell 24
}
}
}
commonInfo SEQUENCE {
cellReselectionPriority 5 Greater than
EUTRA Freq

ncc-Permitted 11111111B
q-RxLevMin 2 The actual value
of Q
rxlevmin
in dBm
=(IE value * 2)
115.

threshX-High 2 Actual value =4
dB

threshX-Low 2 Actual value =4
dB

}
carrierFreqsGERAN SEQUENCE [m] {
}
}
}
cellReselectionPriority 3 Less than EUTRA
Freq

ncc-Permitted 11111111B
q-RxLevMin 2 The actual value
of Q
rxlevmin
in dBm
=(IE value * 2)
115.

threshX-High 2 Actual value =4
dB

threshX-Low 2 Actual value =4
dB

}
}
}

Release 9
3GPP
129
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3.2 Inter-RAT Cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA
(1)
ensure that {
pr i or i t y i nt er - RAT E- UTRA cel l }
then { UE r esel ect s t he cel l whi ch bel ongs t o t he hi gher pr i or i t y i nt er - RAT E- UTRA cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 10.1.3.3 & TS
44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 10.1.3.3]
The algorithm in this subclause shall be used for inter-RAT cell reselection if priority information is available to the MS
and threshold information is provided by the network. The network shall provide priority information if E-UTRAN
frequencies are included in the neighbour cell list. The mobile station may apply either priorities broadcast in system
information or individual priorities received through dedicated signalling. The rules regarding which set of priorities
shall apply are defined in 3GPP TS 44.018 and 3GPP TS 44.060.
NOTE: Throughout the specification, the phrase neighbour cell list will include also the E-UTRAN Neighbour
Cell list and/or the GPRS E-UTRANNeighbour Cell list where appropriate.
If the GPRS 3G Cell Reselection list or the GPRS E-UTRAN Neighbour Cell list include frequencies of other radio
access technologies, the MS shall, at least every 5 seconds update the value RLA_P for the serving cell and each of the
at least 6 strongest non serving GSM cells.
The MS shall then reselect a suitable (see 3GPP TS 25.304 for UTRAN and 3GPP TS 36.304 for E-UTRAN) cell of
another radio access technology if the criteria below are satisfied. S_non-serving_XXX is the measurement quantity of
a non-serving inter-RAT cell and XXX indicates the other radio access technology/mode. S_non-serving_XXX is
defined in subclause 6.6.6.
Cell reselection to a cell of another inter-RAT frequency shall be performed if any of the conditions below (to be
evaluated in the order shown) is satisfied:
- The S_non-serving_XXX of one or more cells of a higher priority inter-RAT frequency is greater than
THRESH_XXX_high during a time interval T_reselection; in that case, the mobile station shall consider the
cells for reselection in decreasing order of priority and, for cells of the same inter-RAT frequency, in decreasing
order of S_non-serving_XXX, and reselect the first cell that satisfies the conditions above;
- The value of S_serving is lower than THRESH_serving_low for the serving cell and all measured GSM cells; in
this case, the mobile station shall consider for reselection the inter-RAT cells in the following order, and reselect
the first one that satisfies the following criteria:
- cells of a lower priority inter-RAT frequency whose S_non-serving_XXX is greater than
THRESH_XXX_low during a time interval T_reselection; these cells shall be considered in decreasing order
of priority and, for cells of the same RAT, in decreasing order of S_non-serving_XXX;
- if no cells satisfy the criterion above, inter-RAT cells for which, during a time interval T_reselection, S_non-
serving_XXX is higher than S_serving by at least a specific hysteresis H_PRIO; these cells shall be
considered in decreasing order of S_non-serving_XXX.
A UTRAN FDD cell shall only be reselected if, in addition to the criteria above, its measured Ec/No value is equal to or
greater than FDD_Qmin - FDD_Qmin_Offset..
Cell reselection to a cell of another radio access technology (e.g. UTRAN or E-UTRAN) shall not occur within [5]
seconds after the MS has reselected a GSM cell from an inter-RAT cell if a suitable GSM cell can be found.
If the mobile station applies individual priorities received through dedicated signalling and priority information is
available only for some inter-RAT frequencies, cells belonging to frequencies for which no individual priority is
Release 9
3GPP
130
3GPP TS 36.523-1 V9.3.0 (2010-12)
available or no threshold is broadcast in system information shall not be considered for measurement and for cell re-
selection.
If a mobile station in camped normally state (see 3GPP TS 43.022) applies individual priorities received through
dedicated signalling and no priority is available for the serving cell, the mobile station shall consider any GSM cell
(including the serving cell) to have lowest priority (i.e. lower than the eight network configured values).
A mobile station in camped on any cell state (see 3GPP TS 43.022) shall ignore individual priorities received through
dedicated signalling and shall apply priorities received from the system information of the serving cell while attempting
to find a suitable cell. If the mobile station supports CS voice services, the MS shall avoid reselecting acceptable (but
not suitable) E-UTRA cells regardless of the priorities provided in system information.
NOTE: If the MS is camping on an acceptable cell, individual priorities are not discarded until an event leading to
their deletion occurs.
In case of a reselection attempt towards a barred UTRAN cell, the MS shall abandon further reselection attempts
towards this UTRAN cell as defined by the T
barred
value on the barred UTRAN cell (see 3GPP TS 25.331).
NOTE: It is FFS whether a similar requirement should be added in case of a reselection attempt towards a barred
E-UTRAN cell.
NOTE: Requirements for cells belonging to forbidden LAs for roaming should be included here.
[TS 44.018, clause 3.4.1.2.1.1a]
This applies only to a multi-RAT MS supporting E-UTRAN. One or more instances of the Measurement Information
message or SI2quater message may provide E-UTRAN Neighbour Cell Description information in one or more
instances of the Repeated E-UTRAN Neighbour Cells IE. This is used to build the E-UTRAN Neighbour Cell list. The
E-UTRAN Neighbour Cell list may contain up to 8 E-UTRAN frequencies. For each E-UTRAN frequency, zero or
more E-UTRAN neighbour cells may be specified that are not allowed for cell reselection. The list of not allowed cells
is defined in the Not Allowed Cells IEs.
Each EARFCN in each instance of the Repeated E-UTRAN Neighbour Cells IE is added to the E-UTRAN Neighbour
Cell list in the order in which it is received.
System Simulator:
UE:
None.
Preamble:
- The UE is in U0 null state (Registered, Idle mode) on Cell 24 (serving cell) as per TS 24.008 clause 5.1.2.1.1.
Table 6.2.3.2.3.2-illustrates the downlink power levels and other changing parameters to be applied for the cells at

Release 9
3GPP
131
3GPP TS 36.523-1 V9.3.0 (2010-12)
T1
Cell 1
>THRESH_E-
UTRAN_high

U - S Message
1 The SS sets power level of Cell 1 according to
the row "T1" in table 6.2.3.2.3.2-1.
- - - -
Cell 1?
- - 1 -

Table 6.2.3.2.3.3-1 Repeated E-UTRAN Neighbour Cells struct of SI2Quarter for Cell 24[Preamble]
Derivation Path: 36.508 table FFS
Repeated E-UTRAN Neighbour Cells ::=
SEQUENCE {

EARFCN Same as cell 1 This field specifies
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

Measurement Bandwidth Same as cell 1
E-UTRAN_PRIORITY 100B Same as cell 1
THRESH_E-UTRAN_high 00010B Actual value =4 dB
THRESH_E-UTRAN_low 00010B Actual value =4 dB
E-UTRAN_QRXLEVMIN FFS
}

6.2.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE
(1)
with { UE i n UTRA_I dl e st at e }
ensure that {
then { UE r esel ect s t he cel l whi ch bel ongs t o t he l ower pr i or i t y i nt er - RAT E- UTRA cel l }
}

(2)
ensure that {
}

Release 9
3GPP
132
3GPP TS 36.523-1 V9.3.0 (2010-12)
References: The conformance requirements covered in the present TC are specified in: TS 25.304, clause 5.2.6.1.2a and
5.2.6.1.4a.
[TS 25.304, clause 5.2.6.1.2a]
If the UE has received absolute priority information for inter-RAT layers, the UE shall follow these rules:
- The UE shall perform measurements of inter-RAT layers with a priority higher than the priority of the current
serving cell.
NOTE: The rate of these measurements may vary depending on whether Srxlev and Squal of the serving cell are
above or below S
prioritysearch1
and S
prioritysearch2
. This is specified in [10].
- For inter-RAT layers with a priority lower than the priority of the current serving cell:
- If Srxlev
ServingCell
>S
prioritysearch1
and Squal
ServingCell
>S
prioritysearch2
the UE may choose not to perform
measurements of inter-RAT layers of lower priority.
- If Srxlev
ServingCell
<=S
prioritysearch1
or Squal
ServingCell
<=S
prioritysearch2
the UE shall perform measurements of
inter-RAT layers of lower priority.
[TS 25.304, clause 5.2.6.1.4a]
Absolute priorities of different absolute priority layers may be provided to the UE. The following cell reselection
criteria are used for inter-frequency cells if absolute priority information for inter-frequency is available to the UE, and
inter-RAT cells if absolute priority information for inter-RAT is available to the UE.
...
The following definitions apply:
- Criterion 1: the Srxlev
nonServingCell,x
of a cell on an evaluated higher absolute priority layer is greater than
Thresh
x,high
during a time interval Treselection;

- Criterion 3: Srxlev
ServingCell
<Thresh
serving,low
or Squal
ServingCell
<0 and the Srxlev
nonServingCell,x
of a cell on an
evaluated lower absolute priority layer is greater than Thresh
x,low
Cell reselection to a cell on a higher absolute priority layer than the camped frequency shall be performed if criterion 1
is fulfilled.
...
Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall be performed if criterion 3 is
fulfilled.
If more than one cell meets the above criteria, the UE shall reselect the cell with the highest Srxlev
nonServingCell,x
among
the cells meeting the criteria on the highest absolute priority layer.
The UE shall not perform cell reselection to cells for which the cell selection criterion S is not fulfilled.
The UE shall not perform cell reselection until more than 1 second has elapsed since the UE camped on the current
serving cell.
System Simulator:
- Cell 1 and Cell 5
UE:
None.
Release 9
3GPP
133
3GPP TS 36.523-1 V9.3.0 (2010-12)
Preamble:
Tables 6.2.3.3.3.2-1 & Table 6.2.3.3.3.2-2 illustrate the downlink power levels and other changing parameters to be
applied for the cells at various time instants of the test execution. Subsequent configurations marked "T1", "T2" and
"T3" are applied at the points indicated in the Main behaviour description in Table 6.2.3.3.3.2-3.
T1
Srxlev* dB 21 Srxlev =Cell-specific RS EPRE -
qRxLevMinEUTRA
S
nonServingCell, Cell1
>Thresh
Cell1,low

T2 Cell-specific RS EPRE dBm/15kHz Off
Power level Off is defined in
TS36.508 Table 6.2.2.1-1.
T3
qRxLevMinEUTRA
S
>Thresh
Cell1,high


Table 6.2.3.3.3.2-2: Time instances of cell power level and parameter changes for UTRA cell
T1
CPICH_Ec dBm/3.84 MHz -90
P-CCPCH dBm/1.28 MHz -92
Srxlev* dB -11 Srxlev
ServingCell
<Thresh
Serving,low

T2
Srxlev* dB 19
T3
Srxlev* dB 9
Note : Srxlev is calculated in the UE

Release 9
3GPP
134
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 The SS changes Cell 1 and Cell 5 levels
and table 6.2.3.3.3.2-2.
- - - -
Cell 1?
the RRC Connection is released.
- - 1 -
and table 6.2.3.3.3.2-2.
- - - -
4 The UE reselects Cell5 and camp on Cell5. - - - -
5 The SS changes the E-UTRA cell priority
broadcast in system information.
- - - -
6 Notify UE change of System Information. <-- PAGING TYPE 1 - -
and table 6.2.3.3.3.2-2.
- - - -
Cell 1?
- - 2 -

Table 6.2.3.3.3.3-1: System Information Block type 19 for Cell 5 (preamble, Table 6.2.3.3.3.2-3)
SysInfoType19 ::=SEQUENCE {
utra-PriorityInfoList ::=SEQUENCE {
utra-ServingCell ::=SEQUENCE {
priority [4]
s-PrioritySearch1 [8 (16 dB)]
s-PrioritySearch2 Not present
threshServingLow [4 (8 dB)]
}
utran-FDD-FrequencyList Not present UTRA-
FDD
utran-TDD-FrequencyList Not present UTRA-
TDD
}
gsm-PriorityInfoList Not present
eutra-FrequencyAndPriorityInfoList ::=SEQUENCE
(SIZE (1..maxNumEUTRAFreqs) OF SEQUENCE {

earfcn [n] Same downlink EARFCN
as used for Cell 1

measurementBandwidth [n] Not present
priority [n] [3]
qRxLevMinEUTRA [n] [-60 (-120 dBm)]
threshXhigh [n] [16 (32 dB)]
threshXlow [n] [10 (20 dB)]
eutra-blackListedCellList [n] Not present
eutraDetection [n] [TRUE]
}
}
Note: GERAN cell priority is not allocated, hence it will be considered as the less than all allowed values of 0 to
7.

Release 9
3GPP
135
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.3.3.3-2: System Information Block type 19 for Cell 5 (step 5, Table 6.2.3.3.3.2-3)
priority [4]
s-PrioritySearch1 [8 (16 dB)]
s-PrioritySearch2 Not present
threshServingLow [4 (8 dB)]
}
utran-FDD-FrequencyList Not present UTRA-
FDD
utran-TDD-FrequencyList Not present UTRA-
TDD
}
gsm-PriorityInfoList Not present

as used for Cell 1

priority [n] [5]
qRxLevMinEUTRA [n] [-60 (-120 dBm)]
threshXhigh [n] [16 (32 dB)]
threshXlow [n] [10 (20 dB)]
eutra-blackListedCellList [n] Not present
eutraDetection [n] [TRUE]
}
}
Note: GERAN cell priority is not allocated, hence it will be considered as the less than all allowed values of 0 to
7.

UTRA-FDD UTRA FDD cell environment
UTRA-TDD UTRA TDD cell environment

Table 6.2.3.3.3.3-3: PAGING TYPE 1 (step 6, Table 6.2.3.3.3.2-3)
Derivation path: 34.108 clause 9.1.1
PagingType1 ::=SEQUENCE {
bcch-ModificationInfo ::=SEQUENCE {
mib-ValueTag Set to (Current MIB
value tag +1)

bcch-ModificationTime Not present
}
laterNonCriticalExtensions SEQUENCE {} Not present
}

Table 6.2.3.3.3.3-4:SystemInformationBlockType3 for Cell 1(preamble, Table 6.2.3.3.3.2-3)
}
}

Release 9
3GPP
136
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.3.3.3-5:SystemInformationBlockType3 for Cell 1(step 5, Table 6.2.3.3.3.2-3)
}
}

Table 6.2.3.3.3.3-6:SystemInformationBlockType6 for Cell 1(preamble, Table 6.2.3.3.3.2-3)
CarrierFreqListUTRA-FDD SEQUENCE (SIZE
(1..maxUTRA-FDD-Carrier)) OF SEQUENCE {
UTRA-FDD
carrierFreq[n] Same downlink
UARFCN as used
for cell 5

}
CarrierFreqListUTRA-TDD SEQUENCE (SIZE
(1..maxUTRA-TDD-Carrier)) OF SEQUENCE {
UTRA-TDD
carrierFreq[n] Same downlink
UARFCN as used
for cell 5

}
}


6.2.3.4 Inter-RAT cell reselection / From UTRA_CELL_PCH state to E-UTRA
RRC_IDLE
(1)
with { UE i n UTRA_CELL_PCH st at e }
ensure that {
}

5.2.6.1.4a; TS 25.331, clause 8.3.9.2, 8.3.9.3, Annex E.
[TS 25.304, clause 5.2.6.1.2a]
The measurement rules below apply in Idle, URA_PCH, CELL_PCH states.
...
serving cell.
Release 9
3GPP
137
3GPP TS 36.523-1 V9.3.0 (2010-12)
above or below S
prioritysearch1
and S
prioritysearch2
- If Srxlev
ServingCell
>S
prioritysearch1
and Squal
ServingCell
>S
prioritysearch2
- If Srxlev
ServingCell
<=S
prioritysearch1
or Squal
ServingCell
<=S
prioritysearch2
[TS 25.304, clause 5.2.6.1.4a]
...
nonServingCell,x
Thresh
x,high

is fulfilled.
...
nonServingCell,x
among
serving cell.
For UE in RRC connected mode states CELL_PCH or URA_PCH the interval Treselection
s,PCH
applies, if provided in
SIB4 (see [4]), while for UE in RRC connected mode state CELL_FACH the interval Treselection
s,FACH
applies, if
provided in SIB4 (see [4]).
In all the above criteria the values of Treselection
s
, Treselection
s,PCH
or Treselection
s,FACH
apply for Treselection and are
scaled according to the UE mobility state and target RAT, as specified in 5.2.6.1.1a.
[TS 25.331, 8.3.9.2]
This procedure is applicable in states CELL_FACH, CELL_PCH or URA_PCH. Inter-RAT cell reselection to E-
UTRAN in CELL_FACH state is not supported in this version of the specification.
When the UE based on received system information makes a cell reselection to a radio access technology other than
UTRAN, e.g. GSM/GPRS or E-UTRA, according to the criteria specified in [4], the UE shall:
...
[TS 25.331, 8.3.9.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.
UTRAN should:
1>release all UE dedicated resources upon indication that the UE has completed a connection establishment to the
other radio access technology.
Release 9
3GPP
138
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 25.331, Annex E]
This annex contains the definitions of the bits in EUTRA Feature Group Indicators.
In this release of the specification the UE shall include the optional EUTRA Feature Group Indicators IE in the UE
multi-mode/multi RAT capability IE of the RRC message. For a specific indicator, if all functionalities for a feature
group listed in Table E.1 have been implemented and tested, the UE shall set the indicator as as "true" (as one), else (i.e.
if any one of the functionalities in a feature group listed in Table E.1 have not been implemented or tested), the UE shall
set the indicator as zero.
The UE shall set all indicators, which do not have a definition in the table E.1, as "false" (as zero).
If the optional EUTRA Feature Group Indicators IE is not included by a UE supporting a future release of the
specification, the network may assume the UE supports all features in the feature groups listed in table E.1 and
deployed in the network.
Table E.1: Defintions of feature group indicators
Index of
indicator
(bit
number)
Definition
(description of the supported functionality, if indicator set to true)
Notes
1 (leftmost
bit)
- UTRA CELL_PCH to EUTRA RRC_IDLE cell reselection
- UTRA URA_PCH to EUTRA RRC_IDLE cell reselection

2 EUTRAN measurements and reporting in connected mode
3 Undefined
4 Undefined

Clarification for mobility to EUTRAN
For mobility to E-UTRAN, it is assumed that we have 6 main "functions":
A. Support of measurements and cell reselection procedure in idle mode
B. Support of measurements and cell reselection procedure in CELL/URA_PCH
C. Support of RRC release with redirection procedure
D. Support of RRC reject with redirection procedure
E. Support of EUTRAN measurements and reporting in connected mode
F. Support of handover procedure in connected mode
Of the above, all UEs that indicate support of E-UTRA in UE capability signalling "Support of E-UTRA FDD" or
"Support of E-UTRA TDD" support A), C) and D)ll EUTRA bands they support.
For B) above, UEs indicate support by the Group 1 indicator bit (if Group 1 is set to "true", it is supported for all
EUTRA bands the UE supports).
For E) above, UEs indicate support by the Group 2 indicator bit (if Group 2 is set to "true", it is supported for all
EUTRA bands the UE supports). The compressed mode capability for supported E-UTRA frequency bands ("Need for
compressed mode") in "Measurement capability extension" is ignored by the network when Group 2 is set to "false".
For F) above, UEs indicate support by the separate UE capability signaling "Support of Inter-RAT PS Handover to E-
UTRA FDD/TDD" defined in TS 25.306 (if this bit is set to "true", PS handover is supported for all EUTRA bands the
UE supports). This bit can only be set to "true" if the UE has set the Group 2 indicator bit to "true".
System Simulator:
Release 9
3GPP
139
3GPP TS 36.523-1 V9.3.0 (2010-12)
- Cell 1 suitable neighbour E-UTRA cell
- Cell 5 UTRA serving cell
UE:
None.
Preamble:
- The UE is in state CELL_PCH (state 6-12) on Cell 5 according to [5].
- The cell power level and parameter for Cell 5 is as follow:
Qrxlevmin (FDD) dBm -79 Default value
Qrxlevmin(TDD) dBm -81 Default value

Table 6.2.3.4.3.2-1: Time instance of cell power level and parameter changes for E-UTRA cell and
UTRA cell
T1
qRxLevMinEUTRA
S
>Thresh
Cell1,high

Srxlev* dB 9

U - S Message
(Note 1)
- - - -
Cell 1? (Note 2)
- - 1 -
Note 1: SS should not send any RRC message after UE has successfully proceed to CELL_PCH state in preamble.
Note 2: UE shall search higher priority layer (i.e. E-UTRA carrier frequency of Cell 1) at least every (60 * N
layers
)
seconds, where N
layers
=1 as specified in [4.2.2, 34].

Release 9
3GPP
140
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.4.3.3-1: System Information Block type 19 for Cell 5 (preamble and all steps, Table
6.2.3.4.3.2-2)
priority 4
}
1 entry
earfcn [1] Same downlink EARFCN
as used for Cell 1

priority [1] 5
qRxLevMinEUTRA [1] -53 (-106 dBm)
threshXhigh [1] 10 (20 dB)
threshXlow [1] 5 (10 dB)
}
}

Table 6.2.3.4.3.3-2: RRC CONNECTION SETUP COMPLETE for Cell 5 (preamble, step 4 of TS 34.108
Table 7.4.2.2.1.3)
Derivation Path: 34.108 default RRC CONNECTION SETUP COMPLETE in section clause 9.1.1 for UTRA FDD or
9.1.2 for UTRA TDD
UE radio access capability
UE multi-mode/multi-RAT capability
EUTRA Feature Group Indicators '1000'B Support of
- UTRA CELL_PCH to
EUTRA RRC_IDLE
cell reselection;
- UTRA URA_PCH to
EUTRA RRC_IDLE
cell reselection

Table 6.2.3.4.3.3-3:SystemInformationBlockType3 for Cell 1 (preamble and all steps, Table 6.2.3.4.3.2-
2)
CellReselectionPriority 5
}
}

Release 9
3GPP
141
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.4.3.3-4:SystemInformationBlockType6 for Cell 1 (preamble and all steps, Table 6.2.3.4.3.2-
2)
CarrierFreqListUTRA-FDD SEQUENCE (SIZE
UTRA-FDD
carrierFreq[n] Same as Cell 5
}
CarrierFreqListUTRA-TDD SEQUENCE (SIZE
UTRA-TDD
carrierFreq[n] Same as Cell 5
}
}


6.2.3.5 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle
(1)
ensure that {
when { UE det ect s t he cel l r e- sel ect i on cr i t er i a ar e met f or t he nei ghbour cel l whi ch bel ongs t o
t he hi gher pr i or i t y UTRAN f r equency }
then { UE r esel ect s t he UTRA cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.5.
[TS 36.304, clause 5.2.4.5]
Criteria 1: the S
nonServingCell,x
x, high
Treselection
RAT
;
be performed if:

nonServingCell,x
is the Srxlev-value of an evaluated cell. ...
System Simulator:
- 2 cells, one E-UTRA and one UTRA cell :
- Cell 1 is a E-UTRA cell
- Cell 5 is a UTRA cell
Release 9
3GPP
142
3GPP TS 36.523-1 V9.3.0 (2010-12)
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configuration marked "T1" is applied at the points indicated in
the Main behaviour description in Table 6.2.3.5.3.2-2.
T1
Cell-specific RS EPRE dBm/15kHz -85 -
CPICH_Ec dBm/3.84 MHz - -65 S
>Thresh
Cell 5,high

U - S Message
- - - -
5?
NOTE: The UE performs an RAU procedure
- - 1 -

Table 6.2.3.5.3.3-1: Void
Table 6.2.3.5.3.3-2: Void
6.2.3.5.3.2-2)
carrierFreqListUTRA-FDD SEQUENCE (SIZE
UTRA-
FDD
carrierFreq[n] Same downlink UARFCN
as used for cell 5

cellReselectionPriority[n] 5 Higher priority
than E-UTRA

}
carrierFreqListUTRA-TDD SEQUENCE (SIZE
UTRA-
TDD
as used for cell 5

cellReselectionPriority[n] 5 Higher priority
than E-UTRA

}
}

Release 9
3GPP
143
3GPP TS 36.523-1 V9.3.0 (2010-12)

6.2.3.6 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle
according to RAT priority provided by dedicated signalling
(1)
with { UE i n E- UTRA RRC_I DLE st at e havi ng r ecei ved an RRCConnectionRelease message i ncl udi ng a
cellReselectionPriority }
ensure that {
pr i or i t y RAT }
then { UE r esel ect s t he cel l whi ch bel ongs t o t he hi gher pr i or i t y RAT }
}

(2)
ensure that {
pr i or i t y RAT }
then { UE r esel ect s t he cel l whi ch bel ongs t o t he l ower pr i or i t y RAT }
}

(3)
ensure that {
when { T320 expi r es }
then { UE r esel ect s a cel l by appl yi ng t he cellReselectionPriority br oadcast i n t he syst em
i nf or mat i on }
}

(4)
with { UE i n E- UTRA RRC_I DLE st at e, and r esel ect i on pr i or i t i es have been pr ovi ded i n dedi cat ed
si gnal l i ng }
ensure that {
when { T320 has not expi r ed }
then { The UE shal l i gnor e al l t he pr i or i t i es pr ovi ded i n syst emi nf or mat i on, and not per f or m
cel l r esel ect i on eval uat i on f or E- UTRAN f r equenci es and i nt er - RAT f r equenci es f or whi ch t he UE
doesn t have a pr i or i t y pr ovi ded }
}

5.2.4.5 and TS 36.331, clause 5.3.8.3 and 5.3.8.4.
[TS 36.304, clause 5.2.4.1]
priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG cell,
the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight
Release 9
3GPP
144
3GPP TS 36.523-1 V9.3.0 (2010-12)
information.
[TS 36.304, clause 5.2.4.5]
Criteria 1: the S
nonServingCell,x
x, high
Treselection
RAT
;
be performed if:
be performed if:
criteria 1; and
- S
ServingCell
<Thresh
serving, low
and the S
nonServingCell,x
x, low
RAT
; and
...
nonServingCell,x
nonServingCell,x
is equal to -FLOOR(-2 x 10 x log10 Ec/Io) in
units of 0.5 dB, as defined in [18], with Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, Threshx, high and Threshx, low are equal to -1 times the values signalled for the corresponding
RAT
best cell among the cells meeting the criteria on the highest priority frequencies or the highest priority RAT if the
[TS 36.331, clause 5.3.8.3]
The UE shall:
Release 9
3GPP
145
3GPP TS 36.523-1 V9.3.0 (2010-12)
1>delay the following actions defined in this sub-clause 60 ms from the moment the RRCConnectionRelease
message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease
message has been successfully acknowledged, whichever is earlier;
1>if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:
2>store the cell reselection priority information provided by the idleModeMobilityControlInfo;
2>if the t320 is included:
3>start timer T320, with the timer value set according to the value of t320;
1>else:
2>apply the cell reselection priority information broadcast in the system information;
1>if the releaseCause received in the RRCConnectionRelease message indicates 'loadBalancingTAURequired':
2>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'load
balancing TAU required';
1>else:
2>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other';
[TS 36.331, clause 5.3.8.4]
The UE shall:
1>if T320 expires:
2>if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or
inherited from another RAT;
System Simulator:
- Cell 1(E-UTRA) and Cell 5(UTRA).
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].
various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while
columns marked "T1", "T2", "T3", "T4" and "T5" are to be applied subsequently. The exact instants on which these
values are applied are described in the texts in this clause.
Release 9
3GPP
146
3GPP TS 36.523-1 V9.3.0 (2010-12)
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-70 -
assigned to satisfy Srxlev
Cell 1
>0
and Srxlev
Cell 5
<0.
CPICH Ec
dBm/3.8
4 MHz
- -100
PCCPCH
RSCP
dBm/1.2
8MHz
-115
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-90 -
assigned to satisfy Thresh
x,high
<
Srxlev
cell 5
.
CPICH Ec
dBm/3.8
4 MHz
- -65
PCCPCH
RSCP
dBm/1.2
8MHz
-65
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-70 -
The power level values are such
that camping on Cell 1 is
guaranteed.
CPICH Ec
dBm/3.8
4 MHz
-
-100

PCCPCH
RSCP
dBm/1.2
8MHz
-115
T3
Cell-specific RS
EPRE
dBm/15k
Hz
-115 -
cell 1
<
Thresh
serving, low
and Thresh
x,low
<
Srxlev
cell 5
.
CPICH Ec
dBm/3.8
4 MHz
- -65
PCCPCH
RSCP
dBm/1.2
8MHz
-65
T4
Cell-specific RS
EPRE
dBm/15k
Hz
-70 -
guaranteed.
CPICH Ec
dBm/3.8
4 MHz
- -100
PCCPCH
RSCP
dBm/1.2
8MHz
-115
T5
Cell-specific RS
EPRE
dBm/15k
Hz
-70 -
cell 1
>
Thresh
serving, low
and Thresh
x,high
<
Srxlev
cell 5
.
CPICH Ec
dBm/3.8
4 MHz
- -65
PCCPCH
RSCP
dBm/1.2
8MHz
-65

Release 9
3GPP
147
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 The SS transmits an RRCConnectionRelease
message with an idleModeMobilityControlInfo
including a cellReselectionPriority on Cell 1.
<-- RRCConnectionRelease - -
2 The SS changes Cell 5 level according to row
"T1" in table 6.2.3.6.3.2-1.
- - - -
CONNECTION REQUEST message within the
next 30s on Cell 5?
--> RRC CONNECTION REQUEST 4 F
4 The SS transmits a Paging message including
matched identity on Cell 1.
<-- Paging - -
5 UE transmit an RRCConnectionRequest
message on Cell 1.
6 The SS transmits an RRCConnectionSetup
message on Cell 1.
<-- RRCConnectionSetup - -
7 The UE transmits an
RRCConnectionSetupComplete on Cell 1.
--> RRCConnectionSetupComplete - -
message with an idleModeMobilityControlInfo
including a cellReselectionPriority on Cell 1.
5?
- - 1 -
10 The SS changes Cell 1 and Cell 5 parameters
- - - -
subclause 6.4.2.7 is performed on Cell 1.
- - - -
- - - -
5?
- - 2 -
- - - -
- - - -
- - - -
17 Wait for 5 minutes from step 15 to ensure that
T320 expires.
- - - -
5?
- - 3 -

Release 9
3GPP
148
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.6.3.3-1: Void
6.2.3.6.3.2-2)
threshServingLow 1
}
}

6.2.3.6.3.2-2)
UTRA-FDD
as used for Cell 5

p-MaxUTRA[n] 0
}
UTRA-TDD
as used for Cell 5

p-MaxUTRA[n] 0
}
}


Release 9
3GPP
149
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.6.3.3-4: RRCConnectionRelease (Step 1, Table 6.2.3.6.3.2-2)
Derivation path: 36.508 table 4.6.1-15
RRCConnectionRelease ::=SEQUENCE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
IdleModeMobilityControlInfo ::=SEQUENCE {
freqPriorityListEUTRA SEQUENCE (SIZE (1..
maxFreq)) OF SEQUENCE {
1 entry
carrierFreq[1]

Same downlink
EARFCN as used for
Cell1

cellReselectionPriority[1]

4
}
freqPriorityListGERAN Not present
freqPriorityListUTRA-FDD Not present UTRA-TDD
freqPriorityListUTRA-TDD Not present UTRA-FDD
bandClassPriorityListHRPD Not present
bandClassPriorityList1XRTT Not present
t320 Not present
}
}
}
}
}


Release 9
3GPP
150
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.6.3.3-5: RRCConnectionRelease (step 8, Table 6.2.3.6.3.2-2)
c1 CHOICE {
idleModeMobilityControlInfo SEQUENCE {
1 entry
carrierFreq[1] Same downlink EARFCN
as used for Cell 1

}
freqPriorityListUTRA-FDD SEQUENCE (SIZE
1 entry UTRA-FDD
carrierFreq[1] Same downlink ARFCN
as used for Cell 5

}
freqPriorityListUTRA-TDD SEQUENCE (SIZE
1 entry UTRA-TDD
as used for Cell 5

}
t320 Not present
}
}
}
}
}


Release 9
3GPP
151
3GPP TS 36.523-1 V9.3.0 (2010-12)
c1 CHOICE {
1 entry
as used for Cell 1

}
1 entry UTRA-FDD
as used for Cell 5

}
1 entry UTRA-TDD
as used for Cell 5

}
t320 Not present
}
}
}
}
}


Release 9
3GPP
152
3GPP TS 36.523-1 V9.3.0 (2010-12)
c1 CHOICE {
1 entry
as used for Cell 1

}
1 entry UTRA-FDD
as used for Cell 5

}
1 entry UTRA-TDD
as used for Cell 5

}
t320 min5
}
}
}
}
}


6.2.3.7 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD
cell is higher reselection priority than E-UTRA
(1)
with { UE i n E- UTRA RRC_I DLE st at e and UE det ect s t he cel l r e- sel ect i on cr i t er i a t hat HRPD cel l i s
hi gher r esel ect i on pr i or i t y t han E- UTRAN ser vi ng cel l }
ensure that { when { UE sear ches f or and measur es HRPD cel l at l east ever y T
hi gher _pr i or i t y_sear ch

and Sr xl ev, HRPD > Thr esh
X, Hi ghP
}
then { UE r esel ect s t he HRPD cel l }
}

5.2.4.2 and 5.2.4.5 and TS 36.133, clause 4.2.2.5 and 4.2.2.5.4.
[TS 36.304, clause 5.2.4.1]
system information , in the RRCConnectionRelease message,or by inheriting from another RAT at inter-RAT cell
Release 9
3GPP
153
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 36.304, clause 5.2.4.2]
- If S
intrasearch
ServingCell
>S
intrasearch
measurements.
- If SServingCell <=Sintrasearch, or S
intrasearch
measurements.
- If S
nonintrasearch
is sent in the serving cell and SServingCell >Snonintrasearch UE may choose not to
perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower
priority.
- If SServingCell <=Snonintrasearch or S
nonintrasearch
according to [10].
Where S
ServingCell
[TS 36.304, clause 5.2.4.5]
If ThreshX-Q is provided, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency
than the serving frequency shall be performed if:
- A cell of a higher priority RAT/ frequency fulfils Squal >Thresh
X, HighQ
RAT
;
and
- More than 1 second has elapsed since the UE camped on the current serving cell.
Otherwise, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving
frequency shall be performed if:
Release 9
3GPP
154
3GPP TS 36.523-1 V9.3.0 (2010-12)
- A cell of a higher priority RAT/ frequency fulfils Srxlev >Thresh
X, HighP
RAT
;
and
If ThreshX-Q is provided, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency
- The serving cell fulfils Squal <Thresh
Serving, LowQ
and a cell of a lower priority RAT/ frequency fulfils Squal >
Thresh
X, LowQ
RAT
; and
Otherwise, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving
- The serving cell fulfils Srxlev <Thresh
Serving, LowP
and a cell of a lower priority RAT/ frequency fulfils Srxlev >
Thresh
X, LowP
RAT
; and
Cell reselection to a higher priority RAT/ frequency shall take precedence over a lower priority RAT/ frequency, if
multiple cells of different priorities fulfil the cell reselection criteria.
For cdma2000 RATs, Srxlev is equal to -FLOOR(-2 x 10 x log10 Ec/Io) in units of 0.5 dB, as defined in [18], with
Ec/Io referring to the value measured from the evaluated cell.
For cdma2000 RATs, Thresh
X, HighP
and Thresh
X, LowP
are equal to -1 times the values signalled for the corresponding
[TS 36.133, clause 4.2.2.5]
If the SServingCellof the E-UTRA serving cell is greater than S
nonintrasearch
, then the UE shall search for inter-RAT layers
of higher priority at least every T
higher_priority_search
where T
is described in section 4.2.2.
If the S
ServingCellof theE-UTRA
serving cell is less than or equal to S
nonintrasearch
then the UE shall search for and measure inter-
RAT layers of higher, lower priority in preparation for possible reselection. In this scenario, the minimum rate at which
the UE is required to search for and measure higher priority inter-RAT layers shall be the same as that defined below
for lower priority RATs.
[TS 36.133, clause 4.2.2.5.4]
In order to perform measurement and cell reselection to HRPD cell, the UE shall acquire the timing of HRPD cells.
When the measurement rules indicate that HRPD cells are to be measured, the UE shall measure CDMA2000 HRPD
Pilot Strength of HRPD cells in the neighbour cell list at the minimum measurement rate specified in this section.
The parameter Number of HRPD Neighbor Frequency, which is transmitted on E-UTRAN BCCH, is the number of
carriers used for all HRPD cells in the neighbour cell list.
When the RSRP of the E-UTRA serving cell (or other cells on the same frequency layer) is lower than HRPD Start
Measuring E-UTRAN Rx Power Strength Threshold and HRPD is of lower priority than the currently selected E-
UTRAN frequency layer, the UE shall measure CDMA2000 HRPD Pilot Strength of the HRPD cells at least every
(Number of HRPD Neighbor Frequency)*T
measureHRPD
.
The UE shall be capable of evaluating that the HRPD cell has met cell reselection criterion defined in [1] within
T
evaluateHRPD
.
Table 4.2.2.5.4-1 gives values of T
measureHRPD
and T
evaluateHRPD.

Release 9
3GPP
155
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 4.2.2.5.4-1: T
measureHRPD and
T
evaluateHRPD
DRX
cycle
length
[s]
T
measureHRPD
[s] (number
of DRX
cycles)
T
evaluateHRPD
[s]
(number of
DRX cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)

System Simulator:
- Cell 1 for E-UTRAN
- Cell 15 for HRPD with higher reselection priority than Cell 1
UE:
None.
Preamble:
in the Main behaviour description in Table 6.2.3.7.3.2-2.

Srxlev
,HRPD
of Cell 15 <Thresh
X, HighP

Ioc
dBm/1.
23
MHz
- -75
dBm/1
5 KHz
-60
T2 or/Ioc dB - 0 Increase pilot power of HRPD cell such
that Srxlev
,HRPD
of Cell 15 >Thresh
X, HighP

Ioc
dBm/1.
23
MHz
- -75
dBm/1
5 KHz
-60
SS.

Release 9
3GPP
156
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 Void - - - -
2 The SS changes Cell 15 level according to row
"T1" in table 6.2.3.7.3.2-1. Cell 15 is on and it
has higher reselection priority than Cell1.
- - - -
3 UE performs measurement for Cell 15 at every
T

- - - -
on Cell 15 within the next [60s]?
--> Access Probe 1 F
5 SS adjust HRPD cell signal level to make sure
S
nonServingCell,HRPD
of Cell 15 >Thresh
HRPD, high
,
according to T2 in table 6.2.3.7.3.2-2
- - - -
on Cell 15?

1)
}

Release 9
3GPP
157
3GPP TS 36.523-1 V9.3.0 (2010-12)
1)
SystemTimeInfo SEQUENCE {
SynchronousSystemTime A valid value as per TS
the SS

}
}
searchWindowSize 5
ParametersHRPD SEQUENCE { HRPD
CellReselectionParametersHRPD SEQUENCE {
BandClassList SEQUENCE (SIZE (1..maxCDMA -
BandClass)) OF SEQUENCE {
The same number of
HRPD carriers

BandClass Band Class of frequency
under test
[Set according to
specific test case]

CellReselectionPriority 5 [3 is applicable
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]

threshX-High 30(-30) INTEGER (0..63)
threshX-Low 32(-32) INTEGER (0..63)
}
t-ReselectionCDMA 7 INTEGER (0..7)
}
}
}

6.2.3.8 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD
is lower reselection priority than E-UTRA
(1)
with { UE i n E- UTRA RRC_I DLE st at e and UE det ect s t he cel l r e- sel ect i on cr i t er i a t hat HRPD cel l i s
equi al t o or l ower r esel ect i on pr i or i t y t han E- UTRAN ser vi ng cel l }
ensure that {
When{ S
Ser vi ngCel l
<= Thr esh
Ser vi ng, LowP
and Sr xl ev > Thr esh
HRPD, l ow
}
then { UE sear ches f or and measur es HRPD cel l at l east ever y T
and r esel ect s t he
HRPD cel l }
}

[TS 36.304, clause 5.2.4.1]
system information or in the RRC message releasing the RRC connection. If priorities are assigned via dedicated
signalling, the UE shall ignore all the priorities provided in system information. The UE shall delete priorities provided
by dedicated signalling when:
Release 9
3GPP
158
3GPP TS 36.523-1 V9.3.0 (2010-12)
UE shall only perform reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given in
system information and for which the UE has a priority provided.
[TS 36.304, clause 5.2.4.2]
- If SServingCell >Sintrasearch, UE may choose to not perform intra-frequency measurements.
- If SServingCell <=Sintrasearch, UE shall perform intra-frequency measurements.
o For an E-UTRAN inter-frequency or inter-RAT frequency with a reselection priority higher than the
o For an E-UTRAN inter-frequency with a equal or lower reselection priority than the reselection priority of
If SServingCell >Snonintrasearch UE may choose not to perform measurements of E-UTRAN inter-
frequencies or inter-RAT frequencies of equal or lower priority.
If SServingCell <=Snonintrasearch the UE shall perform measurements of E-UTRAN inter-frequencies
or inter-RAT frequencies cells of equal or lower priority according to [10].
Where S
ServingCell
[TS 36.304, clause 5.2.4.5]
X, HighQ
RAT
;
and
X, HighP
RAT
;
and
Serving, LowQ
Thresh
X, LowQ
RAT
; and
Release 9
3GPP
159
3GPP TS 36.523-1 V9.3.0 (2010-12)
Serving, LowP
Thresh
X, LowP
RAT
; and
X, HighP
and Thresh
X, LowP
[TS 36.133, clause 4.2.2.5]
If the SServingCellof the E-UTRA serving cell (or other cells on the same frequency layer) is greater than S
nonintrasearch
,
then
- the UE may not search for, or measure inter-RAT layers of equal or lower priority.
- the UE shall search for inter-RAT layers of higher priority at least every T
where T

If the S
nonintrasearch
, then the UE shall search for and measure inter-
RAT layers of higher, equal or lower priority in preparation for possible reselection. In this scenario, the minimum rate
at which the UE is required to search for and measure such layers is not reduced and shall be the same as that defined
below for lower priority RATs.
[TS 36.133, clause 4.2.2.5.4]
In order to perform measurement and cell reselection to HRPD cell, the UE shall acquire the timing of HRPD cells.
When the measurement rules indicate that HRPD cells are to be measured, the UE shall measure CDMA2000 HRPD
Pilot Strength of HRPD cells in the neighbour cell list at the minimum measurement rate specified in this section.
The parameter Number of HRPD Neighbor Frequency, which is transmitted on E-UTRAN BCCH, is the number of
carriers used for all HRPD cells in the neighbour cell list.
When the RSRP of the E-UTRA serving cell (or other cells on the same frequency layer) is lower than HRPD Start
Measuring E-UTRAN Rx Power Strength Threshold and HRPD is of lower priority than the currently selected E-
UTRAN frequency layer, the UE shall measure CDMA2000 HRPD Pilot Strength of the HRPD cells at least every
(Number of HRPD Neighbor Frequency)*T
measureHRPD
. In case HRPD is of higher priority than the currently selected E-
UTRAN frequency layer the UE shall measure HRPD cells at least every (Number of HRPD Neighbor Frequency)*
T
higher_proirty_search
. The parameter T
higher_proirty_search
is defined in section 4.2.2.
The UE shall be capable of evaluating that the HRPD cell has met cell reselection criterion defined in [1] within
T
evaluateHRPD
.
measureHRPD
and T
evaluateHRPD.

Table 4.2.2.5.4-1: T
measureHRPD and
T
evaluateHRPD
DRX
cycle
length
[s]
T
measureHRPD
[s] (number
of DRX
cycles)
T
evaluateHRPD
[s]
(number of
DRX cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)

Release 9
3GPP
160
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
- Cell 15 for HRPD with lower reselection priority than Cell 1
UE:
None.
Preamble:
in the Main behaviour description in Table 6.2.3.8.3.2-2.

Ioc
dBm/
1.23
MHz
- -55
Cell-specific RS EPRE dBm -70 -40 S
ServingCellof the E-UTRA
>Thresh
Serving, LowP
and Srxlev
,HRPD
of Cell 15 <Thresh
x,
low

Srxlev* dB 40
dBm/1
5 KHz
-60

T2 or/Ioc dB - -5 Increase pilot power of HRPD cell
such that S
nonServingCell,HRPD
of Cell 15 >
Thresh
x, low
Ioc
dBm/1.
23
MHz
- -55
Cell-specific RS EPRE dBm -120
Srxlev* dB -10 -12
dBm/1
5 KHz
-60
SS.
Note 2: Default value of Thresh
Serving, LowP
is 0.

Release 9
3GPP
161
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 Cell 15 is on and it has lower reselection
priority than Cell 1, according to T1 in
6.2.3.8.3-1.
SS adjusts the serving cell signal level so that
S
<=S
nonintrasearch
.2
- - - -
T

- - - -
5 SS adjust HRPD cell signal level to make sure
S
nonServingCell,HRPD
of Cell 15 >Thresh
HRPD, low

according to T2 in 6.2.3.8.3.2-1.
- - - -
on Cell 15?

1)
}
}

Release 9
3GPP
162
3GPP TS 36.523-1 V9.3.0 (2010-12)
1)
SystemTimeInfo SEQUENCE {
SynchronousSystemTime A valid value as per TS
the SS

}
}
searchWindowSize 5
ParametersHRPD SEQUENCE { HRPD
CellReselectionParametersHRPD SEQUENCE {
BandClassList SEQUENCE (SIZE (1..maxCDMA -
BandClass)) OF SEQUENCE {
The same number of
HRPD carriers

BandClass Band Class of frequency
under test
[Set according to
specific test case]

CellReselectionPriority 3 [3 is applicable
when HRPD is
lower priority than
E-UTRA. 5 is
applicable when
HRPD is higher
priority than E-
UTRA]

threshX-High 30[-30] INTEGER (0..63)
threshX-Low 32[-32] INTEGER (0..63)
}
t-ReselectionCDMA 0 INTEGER (0..7)
}
}
}

6.2.3.9 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT
Dormant When CDMA2000 1xRTT cell is higher reselection priority than E-
UTRA
(1)
with { UE i n E- UTRA RRC_I DLE st at e and UE det ect s t he cel l r e- sel ect i on cr i t er i a t hat CDMA2000 1xRTT
cel l i s hi gher r esel ect i on pr i or i t y t han E- UTRAN ser vi ng cel l }
ensure that { UE sear ches f or and measur es CDMA2000 1xRTT cel l at l east ever y T

when { SnonSer vi ngCel l , CDMA2000_1x > Thr esh
1xRTT, hi gh
}
then { UE r esel ect s t he CDMA2000 1xRTT cel l }
}

[TS 36.304, clause 5.2.4.1]
Release 9
3GPP
163
3GPP TS 36.523-1 V9.3.0 (2010-12)
information.
[TS 36.304, clause 5.2.4.5]
X, HighQ
RAT
;
and
X, HighP
RAT
;
and
Serving, LowQ
Thresh
X, LowQ
RAT
; and
Serving, LowP
Thresh
X, LowP
RAT
; and
Release 9
3GPP
164
3GPP TS 36.523-1 V9.3.0 (2010-12)
X, HighP
and Thresh
X, LowP
RAT
defined in subclause 5.2.4.3.1. If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
- If the highest-priority frequency is an E-UTRAN frequency, a cell ranked as the best cell among the cells on the
highest priority frequency(ies) meeting the criteria according to section 5.2.4.6;
- If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest
priority frequency(ies) meeting the criteria of that RAT.
[TS 36.133, clause 4.2.2.5]
If Srxlev >S
nonIntraSearchP
and Squal >S
nonIntraSearchQ
then the UE shall search for inter-RAT layers of higher priority at
least every T
where T
is described in section 4.2.2
If Srxlev S
nonIntraSearchP
or Squal S
nonIntraSearchQ
then the UE shall search for and measure inter-RAT layers of higher,
lower priority in preparation for possible reselection. In this scenario, the minimum rate at which the UE is required to
search for and measure higher priority inter-RAT layers shall be the same as that defined below for lower priority
RATs.
[TS 36.133, clause 4.2.2.5.5]
In order to perform measurement and cell reselection to cdma2000 1X cell, the UE shall acquire the timing of
cdma2000 1X cells.
When the measurement rules indicate that cdma2000 1X cells are to be measured, the UE shall measure cdma2000 1x
RTT Pilot Strength of cdma2000 1X cells in the neighbour cell list at the minimum measurement rate specified in this
section.
The parameter Number of CDMA2000 1X Neighbor Frequency, which is transmitted on E-UTRAN BCCH, is the
number of carriers used for all cdma2000 1X cells in the neighbour cell list.
If S
ServingCell
of the E-UTRA serving cell is greater than S
nonintrasearch
, the UE shall search for cdma2000 1X layers of
higher priority at least every T
where T
For CDMA2000 1X cells which have been detected, the UE shall measure CDMA2000 1xRTT Pilot Strength at least
every (Number of CDMA2000 1X Neighbor Frequency)*T
measureCDMA2000_1X
, when the S
ServingCell
of the E-UTRA serving
cell is less than or equal to S
nonintrasearch
.
The UE shall be capable of evaluating that the cdma2000 1X cell has met cell reselection criterion defined in [1] within
T
evaluateCDMA2000_1X
.
measureCDMA2000_1X
and T
evaluateCDMA2000_1X.

Table 4.2.2.5.5-1: T
measureCDMA2000 1X and
T
evaluateCDMA2000 1X
DRX
cycle
length
[s]
T
measureCDMA2000_1X

[s] (number of
DRX cycles)
T
evaluateCDMA2000_1X
[s] (number of
DRX cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)

If T
reselection
timer has a non zero value and the CDMA2000 1X cell is better ranked than the serving cell, the UE shall
evaluate this CDMA2000 1X cell for the T
reselection
time. If this cell remains better ranked within this duration, then the
UE shall reselect that cell.
Release 9
3GPP
165
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
- Cell 19 for CDMA2000 1xRTT with higher reselection priority than Cell 1
UE:
None.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows 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.
T0
- The power levels are such that camping
on Cell 1 is guaranteed.
T1 Cell-specific RS EPRE dBm/15 KHz -75 Cell 19 is on
or/Ioc dB -15
Pilot Ec/ Ior -7
Ioc dBm - -75
Pilot Ec/ Io (Note 1) dB - -22
T2 Cell-specific RS EPRE dBm/15 KHz -75 Increase pilot power of 1xRTT cell such
that S
nonServingCell,
of Cell 19 >Thresh
1xRTT,
high

or/Ioc dB 0
SS.

U - S Message
1 Cell 19 is on and it has higher reselection
priority than Cell1, according to T1 in
6.2.3.9.3.2
- - - -
T

- - - -
4 SS adjust CDMA2000 1xRTT cell signal level
to make sure S
nonServingCell, 1xRTT
of Cell 19 >
Thresh
1xRTT, high
, according to T2 in
6.2.3.9.3.2
- - - -
on Cell 19?

Release 9
3GPP
166
3GPP TS 36.523-1 V9.3.0 (2010-12)
1)
}
}

1)
the SS

}
}
searchWindowSize 5
oneXRTT-CellReselectionParameters SEQUENCE {
The same number of
1xRTT carriers

oneXRTT-BandClass FFS ENUMERATED
{bc0, bc1, bc2,
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2,
spare1, ...}

oneXRTT-CellReselectionPriority 5 [3 is applicable
when 1xRTT is
lower priority than
E-UTRA. 5 is
applicable when
1xRTTis higher
priority than E-
UTRA]

}
t-ReselectionCDMA-OneXRTT [7] INTEGER (0..7)
}
}
}

Release 9
3GPP
167
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3.10 Inter-RAT Cell Reselection: from E-UTRA RRC_IDLE to CDMA2000 1xRTT
Idle When CDMA2000 1xRTT is lower reselection priority than E-UTRA
(1)
with { UE i n E- UTRA RRC_I DLE st at e and UE det ect s t he cel l r e- sel ect i on cr i t er i a t hat CDMA2000 1xRTT
cel l i s equi al t o or l ower r esel ect i on pr i or i t y t han E- UTRAN ser vi ng cel l }
ensure that {
When{ S
Ser vi ngCel l
<= S
noni nt r asear ch
}
then { UE sear ches f or and measur es CDMA2000 1xRTT cel l at l east ever y T
measur eCDMA2000_1X
}
when { S
nonSer vi ngCel l ,
1xRTT > Thr esh
1xRTT, l ow
}
then { UE r esel ect s t he CDMA2000 1xRTT cel l }
}

[TS 36.304, clause 5.2.4.1]
information.
[TS 36.304, clause 5.2.4.5]
X, HighQ
RAT
;
and
Release 9
3GPP
168
3GPP TS 36.523-1 V9.3.0 (2010-12)
X, HighP
RAT
;
and
Serving, LowQ
Thresh
X, LowQ
RAT
; and
Serving, LowP
Thresh
X, LowP
RAT
; and
X, HighP
and Thresh
X, LowP
RAT
- If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest
priority frequency(ies) meeting the criteria of that RAT.
[TS 36.133, clause 4.2.2.5]
If the SServingCellof the E-UTRA serving cell (or other cells on the same frequency layer) is greater than S
nonintrasearch
,
then
- the UE may not search for, or measure inter-RAT layers of equal or lower priority.
- the UE shall search for inter-RAT layers of higher priority at least every T
where T

If the S
nonintrasearch
, then the UE shall search for and measure inter-
RAT layers of higher, equal or lower priority in preparation for possible reselection. In this scenario, the minimum rate
at which the UE is required to search for and measure such layers is not reduced and shall be the same as that defined
below for lower priority RATs.
[TS 36.133, clause 4.2.2.5]
If Srxlev >S
nonIntraSearchP
and Squal >S
nonIntraSearchQ
then the UE shall search for inter-RAT layers of higher priority at
least every T
where T
is described in section 4.2.2
If Srxlev S
nonIntraSearchP
or Squal S
nonIntraSearchQ
then the UE shall search for and measure inter-RAT layers of higher,
lower priority in preparation for possible reselection. In this scenario, the minimum rate at which the UE is required to
search for and measure higher priority inter-RAT layers shall be the same as that defined below for lower priority
RATs.
Release 9
3GPP
169
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 36.133, clause 4.2.2.5.5]
In order to perform measurement and cell reselection to cdma2000 1X cell, the UE shall acquire the timing of
cdma2000 1X cells.
When the measurement rules indicate that cdma2000 1X cells are to be measured, the UE shall measure cdma2000 1x
RTT Pilot Strength of cdma2000 1X cells in the neighbour cell list at the minimum measurement rate specified in this
section.
The parameter Number of CDMA2000 1X Neighbor Frequency, which is transmitted on E-UTRAN BCCH, is the
number of carriers used for all cdma2000 1X cells in the neighbour cell list.
If S
ServingCell
of the E-UTRA serving cell is greater than S
nonintrasearch
, the UE shall search for cdma2000 1X layers of
higher priority at least every T
where T
For CDMA2000 1X cells which have been detected, the UE shall measure CDMA2000 1xRTT Pilot Strength at least
every (Number of CDMA2000 1X Neighbor Frequency)*T
measureCDMA2000_1X
, when the S
ServingCell
of the E-UTRA serving
cell is less than or equal to S
nonintrasearch
.
The UE shall be capable of evaluating that the cdma2000 1X cell has met cell reselection criterion defined in [1] within
T
evaluateCDMA2000_1X
.
measureCDMA2000_1X
and T
evaluateCDMA2000_1X.

Table 4.2.2.5.5-1: T
measureCDMA2000 1X and
T
evaluateCDMA2000 1X
DRX
cycle
length
[s]
T
measureCDMA2000_1X

[s] (number of
DRX cycles)
T
evaluateCDMA2000_1X
[s] (number of
DRX cycles)
0.32 5.12 (16) 15.36 (48)
0.64 5.12 (8) 15.36 (24)
1.28 6.4 (5) 19.2 (15)
2.56 7.68 (3) 23.04 (9)

If T
reselection
timer has a non zero value and the CDMA2000 1X cell is better ranked than the serving cell, the UE shall
evaluate this CDMA2000 1X cell for the T
reselection
time. If this cell remains better ranked within this duration, then the
UE shall reselect that cell.
System Simulator:
- Cell 19 for CDMA2000 1xRTT with lower reselection priority than Cell 1
UE:
None.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows marked "T1"
Release 9
3GPP
170
3GPP TS 36.523-1 V9.3.0 (2010-12)
T0
- The power levels are such that camping
on Cell 1 is guaranteed.
T1 Cell-specific RS EPRE dBm/15 KHz -100 - Cell 19 is on
or/Ioc dB - -15
Pilot Ec/ Ior -7
Ioc dBm - -75
T2 Cell-specific RS EPRE dBm/15 KHz -120 - Increase pilot power of 1xRTT cell such
that S
nonServingCell,
of Cell 19 >Thresh
1xRTT,
high
and S
<Thresh
Serving,
LowP

or/Ioc dB - 0
Note 1: This parameter is not directly settable, but is derived by calculation from the other parameters set by the SS.
Note 2: Default value of Thresh
Serving, LowP
is 0.

U - S Message
1 Cell 19 is on and it has lowerer reselection
priority than Cell 1, according to T1 in
6.2.3.10.3.2-1
SS adjust the serving cell signal level so that
S
<=S
nonintrasearch

- - - -
T
measureCDMA2000_1X

- -
4 SS adjust CDMA2000 1xRTT Cell 19 signal
level to make sure S
nonServingCell,1xRTT
of Cell 19
>Thresh
1xRTT, low
, according to T2 in
6.2.3.10.3.2-1

on Cell 19?

Table 6.2.3.10.3.3-1: SystemInformationBlockType1 to Cell 1 (Preamble and all steps, table
6.2.3.10.3.2-1)
}
}

Release 9
3GPP
171
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.10.3.3-2: SystemInformationBlockType8 to Cell 1 (Preamble and all steps, table
6.2.3.10.3.2-1)
the SS

}
}
searchWindowSize 5
oneXRTT-CellReselectionParameters SEQUENCE {
The same number of
1xRTT carriers

oneXRTT-BandClass FFS ENUMERATED
{bc0, bc1, bc2,
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2,
spare1, ...}

oneXRTT-CellReselectionPriority 5 [3 is applicable
when 1xRTT is
lower priority than
E-UTRA. 5 is
applicable when
1xRTTis higher
priority than E-
UTRA]

}
t-ReselectionCDMA-OneXRTT [7] INTEGER (0..7)
}
}
}

6.2.3.11 Void
6.2.3.12 Void
6.2.3.13 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE
according to RAT priority provided by dedicated signalling
(1)
ensure that {
Release 9
3GPP
172
3GPP TS 36.523-1 V9.3.0 (2010-12)
pr i or i t y i nt er - RAT E- UTRA cel l based on t he conf i gur ed RAT pr i or i t y pr ovi ded by dedi cat ed
si gnal i ng }
then { UE r esel ect s t he cel l whi ch bel ongs t o t he l ower pr i or i t y i nt er - RAT E- UTRA cel l }
}

(2)
with { UE i n E- UTRA RRC_I DLE st at e havi ng i nher i t RAT pr i or i t y pr ovi ded by dedi cat ed si gnal i ng wi t h
t he r emai ni ng val i di t y t i me }
ensure that {
when { UE di scar d t he i nher i t RAT pr i or i t y upon connect i on est abl i shment }
then { UE r esel ect s a cel l by appl yi ng t he cellReselectionPriority br oadcast i n t he syst em
i nf or mat i on }
}

5.2.6.1.4a; TS 25.331, clause 8.3.3.3 and 8.6.7.23; TS 36.331, clause 5.3.3.4.
[TS 25.304, clause 5.2.6.1.2a]
serving cell.
above or below S
prioritysearch1
and S
prioritysearch2
- If Srxlev
ServingCell
>S
prioritysearch1
and Squal
ServingCell
>S
prioritysearch2
- If Srxlev
ServingCell
<=S
prioritysearch1
or Squal
ServingCell
<=S
prioritysearch2
[TS 25.304, clause 5.2.6.1.4a]

nonServingCell,x
Thresh
x,high

ServingCell
<Thresh
serving,low
or Squal
ServingCell
<0 and the Srxlev
nonServingCell,x
of a cell on an
x,low
is fulfilled.

fulfilled.
Release 9
3GPP
173
3GPP TS 36.523-1 V9.3.0 (2010-12)
nonServingCell,x
among
serving cell.
[TS 25.331, clause 8.3.3.3]
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:
1>act on received information elements as specified in subclause 8.6;
1>if the IE "Dedicated Priority Information" is present:
2>act upon the received IE as described in subclause 8.6.7.23.
[TS 25.331, clause 8.6.7.23]
If the CHOICE "Action" has the value "Configure dedicated priorities", the UE shall:
1>clear the variable PRIORITY_INFO_LIST;
1>stop timer T322, if it is running;
1>set the value of IE "Priority status" in the variable PRIORITY_INFO_LIST to "dedicated_priority";
1>for each occurrence of the IE "Priority Level List":
2>create a new entry in the IE "Priority Info List" in the variable PRIORITY_INFO_LIST, and in that new
entry:
3>set the CHOICE "Radio Access Technology" to the value received in the IE "Priority Level List";
3>set the IE "priority" to the value received in the IE "Priority Level List";
3>set the values in IE "Frequency List" or "BCCH ARFCN List" to the values received in the IE "Priority
Level List".
1>set the IE "E-UTRA detection" to the value received in the IE "Priority Level List".
1>if the IE "T322" is present:
2>start timer T322 using the value signalled in this IE.
1>if the UE is not in CELL_DCH state:
2>take the actions as described in subclause 8.1.1.6.19 using stored System information Block type 19.
[TS 36.331, clause 5.3.3.4]
The UE shall:
1>perform the radio resource configuration procedure in accordance with the received
radioResourceConfigDedicated and as specified in 5.3.10;
1>stop timer T300;
1>stop timer T302, if running;
Release 9
3GPP
174
3GPP TS 36.523-1 V9.3.0 (2010-12)
1>perform the actions as specified in 5.3.3.7;
1>enter RRC_CONNECTED;
1>stop the cell re-selection procedure;
...
procedure ends;
System Simulator:
NOTE: Common Priority information for Cell 1 & Cell 5: UTRA priority =3; E-UTRA priority =4.
UE:
None.
Preamble:
- The UE is in state PS-DCCH+DTCH_DCH (state 6-10) on Cell 5 according to [5].
Tables 6.2.3.13.3.2-1 and 6.2.3.13.3.2-2 illustrates the downlink power levels and other changing parameters to be
applied for the cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the
preamble, while row 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 6.2.3.13. 3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell
T0
Qrxlevmin dBm -106 Default value
Srxlev* dB 9
T1
qRxLevMinEUTRA
S
>Thresh
Cell1,low

T2
Srxlev* dB 9

Release 9
3GPP
175
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.13. 3.2-2: Time instances of cell power level and parameter changes for UTRA cell
T0
The power levels are such that
camping on Cell 5 is guaranteed.
Srxlev* dB 19
T1
Srxlev* dB 4 Srxlev
ServingCell
<Thresh
Serving,low

T2
Srxlev* dB 19

U - S Message
1 The SS provides dedicated priority information
(UTRA priority =5; E-UTRA priority =4) and
validity timer to the UE.
<-- UTRAN MOBILITY
INFORMATION
- -
2 The SS receives the UTRAN MOBILITY
INFOMRATION CONFIRM message.
--> UTRAN MOBILITY
INFORMATION CONFIRM
- -
3 The SS releases the UE connection. <-- RRC CONNECTION RELEASE - -
4 The SS receives UE release complete
message.
--> RRC CONNECTION RELEASE
COMPLETE
- -
message.
COMPLETE
- -
message.
COMPLETE
- -
1 and table 6.2.3.13.3.2-2.
- - - -
8 Check: does the test result of generic test
Cell 1?
the RRC Connection is released.
- - 1 -
9 Void - - - -
10 Void - - - -
1 and table 6.2.3.13.3.2-2.
- - - -
5?
- - 2 -

Release 9
3GPP
176
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.13.3.3-1: UTRAN MOBILITY INFORMATION for Cell 5 (step 1, Table 6.2.3.13.3.2-3)
Derivation Path: 34.108, clause 9
UTRANMobilityInformation ::=CHOICE {
later-than-r3 SEQUENCE {
r7 SEQUENCE {
v860NonCriticalExtensions SEQUENCE {
utranMobilityInformation-v860ext SEQUENCE
{

dedicatedPriorityInformation SEQUENCE {
action CHOICE {
configureDedicatedPriorities SEQUENCE
{

t-322 5 Time in minutes
priorityLevelList SEQUENCE (SIZE
(1..maxPrio)) OF SEQUENCE {
2 entry
priority[1] 5
radioAccessTechnology[1] CHOICE {
utraFDD SEQUENCE (SIZE
(1..maxNumFDDFreqs)) OF SEQUENCE {
1 entry UTRA-
FDD
uarfcn Same downlink UARFCN
as used for Cell 5

}
utraTDD SEQUENCE (SIZE
(1..maxNumTDDFreqs)) OF SEQUENCE {
1 entry UTRA-
TDD
as used for Cell 5

}
}
priority[2] 4
eutra SEQUENCE (SIZE
(1..maxNumEUTRAFreqs)) OF SEQUENCE {
1 entry
earfcn Same downlink EARFCN
as used for Cell 1

}
}
}
E-UTRA detection TRUE
}
}
}
}
}
}
}
}
}
}


Release 9
3GPP
177
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.13.3.3-2: RRC CONNECTION RELEASE for Cell 5 (step 3, Table 6.2.3.13.3.2-3)
RRCConnectionRelease ::=CHOICE {
r4 SEQUENCE {
n-308 2 2 (for CELL_DCH
state). Not
Present (for UE in
other connected
mode states).

releaseCause normalEvent
rplmn-information Not Present
}
v4d0NonCriticalExtensions SEQUENCE {} Not Present
}
}
}
}

6.2.3.13.3.2-3)
s-PrioritySearch1 8 (16 dB)
threshServingLow 4 (8 dB)
}
}

as used for Cell 1

qRxLevMinEUTRA [n] -53 (-106 dBm)
threshXhigh [n] 16 (32 dB)
threshXlow [n] 10 (20 dB)
}
}

6.2.3.13.3.2-3)
threshServingLow 5 (10dB)
}
}

Release 9
3GPP
178
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.13.3.3-5: SystemInformationBlockType6 for Cell 1 (preamble and all steps, Table 6.2.3.
13.3.2-3)
UTRA-FDD
carrierFreq[n] Downlink UARFCN of
Cell 5

threshX-High[n] 5 (10dB)
threshX-Low[n] 5 (10dB)
}
UTRA-TDD
carrierFreq[n] Downlink UARFCN of
Cell 5

threshX-High[n] 5 (10dB)
threshX-Low[n] 5 (10dB)
}
}


6.2.3.14 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA
(priority of E-UTRA cells are higher than the serving cell)
(1)
ensure that {
when { Pr i or i t y of E- UTRA nei ghbour cel l i s set l ower t han GERAN cel l }
then { UE does not r esel ect s t he l ower pr i or i t y E- UTRA nei ghbour cel l }
}
(2)
ensure that {
when { Pr i or i t y of E- UTRA nei ghbour cel l i s set hi gher t han GERAN cel l }
then { UE r esel ect s t he hi gher pr i or i t y i nt er - RAT E- UTRA nei ghbour cel l }
}

44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 10.1.3.3]
THRESH_XXX_high (or, in case of an E-UTRAN target, THRESH_E-UTRAN_high_Q, if provided) during a time
interval T_reselection; in that case, the mobile station shall consider the cells for reselection in decreasing order of
priority and, for cells of the same inter-RAT frequency or of inter-RAT frequencies of equal priority, in decreasing
...
Release 9
3GPP
179
3GPP TS 36.523-1 V9.3.0 (2010-12)
If the mobile station applies either common priorities or individual priorities received through dedicated signalling and
priorities are available only for some inter-RAT frequencies, cells belonging to frequencies for which no priority is
available or no threshold is provided by the serving cell shall not be considered for measurement and for cell re-
selection.
[TS 44.018, clause 3.4.1.2.1.1a]
System Simulator:
- Two cells:
- One GERAN cell, Cell 24 is serving cell.
- One E-UTRAN cell, Cell 1 is Suitable neighbour inter-frequency cell.
UE:
None.
Preamble:
- The UE is in state Registered, IDLE (GPRS) on Cell 24 (3GPP TS 51.010-1 clause 41.2.8.1.1)
U - S Message
next 70 s (70 s +T_reselect)?
2 The SS changes SI2Quater in Cell 24
according to table 6.2.3.14.3.3-2.
- - - -
3 The SS changes SI13 in Cell 24 according to
table 6.2.3.14.3.3-3.
- - - -
4 Wait for 70 s (70 s +T_reselect). - - - -
Cell 1?
- - 2 -

Release 9
3GPP
180
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.14.3.3-1: Repeated E-UTRAN Neighbour Cells struct of SI2Quarter for Cell 24 in Preample
Derivation Path: 36.508 FFS
Serving Cell Priority Parameters Description::={
GERAN_PRIORITY 5
THRESH_Priority_Search 0
THRESH_GSM_low 0
}
Repeated E-UTRAN Neighbour Cells ::={
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

E-UTRAN_PRIORITY 100B 4
}

Table 6.2.3.14.3.3-2: Repeated E-UTRAN Neighbour Cells struct of SI2Quarter for Cell 24 in table
6.2.3.14.3.2-1 step 2
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

E-UTRAN_PRIORITY 110B 6
}

Table 6.2.3.14.3.3-3: SI13 for Cell 24 in table 6.2.3.14.3.2-1 step 3
Derivation Path: 51.010-1 clause 40.2.1.1.1
SI 13 Rest Octets ::={
BCCH_CHANGE_MARK 001B
SI_CHANGE_FIELD 0010B Update of SI2, SI2
bis or SI2 ter
message or any
instance of SI2quater
messages.

}

Release 9
3GPP
181
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3.15 Inter-RAT Cell Reselection / from GSM_Idle/GPRS Packet_Idle to E-UTRA
(priority of E-UTRA cells are lower than the serving cell)
(1)
ensure that {
when { Sr xl ev
eut r an
< THRESH_E- UTRAN_l ow f or t he l ower pr i or i t y i nt er - RAT E- UTRA cel l }
then { UE does not r esel ect s t he l ower pr i or i t y i nt er - RAT E- UTRA cel l }
}
(2)
ensure that {
when { Sr xl ev
eut r an
> THRESH_E- UTRAN_l ow f or t he l ower pr i or i t y i nt er - RAT E- UTRA cel l }
then { UE r esel ect s t he l ower pr i or i t y i nt er - RAT E- UTRA cel l }
}

44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 10.1.3.3]
...
[TS 44.018, clause 3.4.1.2.1.1a]
System Simulator:
- Two cells:
- One GERAN cell, Cell 24 is serving cell.
- One E-UTRAN cell, Cell 1 is Suitable neighbour inter-frequency cell.
None.
Release 9
3GPP
182
3GPP TS 36.523-1 V9.3.0 (2010-12)
Preamble:
- The UE is in state Registered, IDLE (GPRS) on Cell 24 (3GPP TS 51.010-1 clause 41.2.8.1.1).
U S Message
next 25 s (25 s+T_reselect)?
2 The SS changes SI2Quater in Cell 24
according to table 6.2.3.15.3.3-2. Srxlev
Cell 1
>
THRESH_E-UTRAN_low.
- - - -
3 The SS changes SI13 in Cell 24 according to
table 6.2.3.15.3.3-3.
- - - -
4 Wait for 25 s (25 s+T_reselect). - - - -
Cell 1?
- - 2 -

Table 6.2.3.15.3.3-1: Repeated E-UTRAN Neighbour Cells struct of SI2Quarter for Cell 24 in Preamble
Serving Cell Priority Parameters Description::={
GERAN_PRIORITY 7
THRESH_GSM_low 15 MS is always allowed
to reselect to lower
priority cells

}
SEQUENCE {

EARFCN Same as Cell 1 This field specifies
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

Measurement Bandwidth Same as Cell 1
E-UTRAN_PRIORITY 001B
}

Release 9
3GPP
183
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.15.3.3-2: Repeated E-UTRAN Neighbour Cells struct of SI2Quarter for Cell 24 in table
6.2.3.15.3.2-1 step 2
EARFCN Same as Cell 1 This field specifies
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

Measurement Bandwidth Same as Cell 1
E-UTRAN_PRIORITY 001B
}

Table 6.2.3.15.3.3-3: SI13 for Cell 24 in table 6.2.3.15.3.2-1 step 3
SI 13 Rest Octets ::={
BCCH_CHANGE_MARK 001B
SI_CHANGE_FIELD 0010B Update of SI2, SI2
bis or SI2 ter
message or any
instance of SI2quater
messages.

}

6.2.3.16 Void
6.2.3.17 Void
6.2.3.18 Void
6.2.3.19 Redirection to E-UTRA upon the release of the CS connection
(1)
with { UE i n CS Act i ve st at e }
ensure that {
when { UE r ecei ves CHANNEL RELEASE message i ncl udi ng an I E Cell selection indicator after release
of all TCH and SDCCH,i ncl udi ng E- UTRAN car r i er f r equency of Cel l 1}
then { UE ent er s RRC_I DLE st at e on E- UTRAN Car r i er i ncl uded i n I E Cell selection indicator info }
}

References: The conformance requirements covered in the current TC are specified in: TS 44.018, clause 3.4.13.1.1,
and TS 45.008, clause 6.7.1.
[TS 44.018, clause 3.4.13.1.1]
The CHANNEL RELEASE message may include the information element "Cell selection indicator after release of all
TCH and SDCCH" which shall be used by the mobile station in its cell selection algorithm after release of all TCH and
SDCCH (see 3GPP TS 45.008).
The CHANNEL RELEASE message may include Individual priorities IE to convey individual priorities information to
the MS (see subclause 3.2.4). When the MS receives an Individual priorities IE it shall start an instance of timer T3230
with the value supplied in the Individual priorities IE.
Release 9
3GPP
184
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 45.008, clause 6.7.1]
In A/Gb mode, when the MS releases all TCHs or SDCCH and returns to idle mode, packet idle mode or MAC-Idle
state, it shall, as quickly as possible, camp on the cell whose channel has just been released. Similarly in Iu mode, when
the MS releases all DBPSCHs and returns to MAC-Idle state, it shall, as quickly as possible, camp on the cell whose
channel has just been released. However, in both modes (A/Gb mode or Iu mode), if the CHANNEL RELEASE
message contains a cell selection indicator after release of all TCH and SDCCH (see TS 44.018), the MS shall as
quickly as possible camp on an indicated GSM, UTRAN or E-UTRAN cell that has been identified by the CHANNEL
RELEASE message. If UTRAN or E-UTRAN frequency only is indicated the MS shall as quickly as possible camp on
a suitable cell of this frequency.
In case the cell selection indicator after release of all TCHs and SDCCH is not present, then if the full (P)BCCH data
for that cell was not decoded in the preceding 30s, the MS shall attempt to decode the full (P)BCCH data. Until the MS
has decoded the (P)BCCH data required for determining the paging group, it shall also monitor all paging blocks on
timeslot 0 of the BCCH carrier or, for GPRS if PCCCH exists and for Iu mode, on the PDCH indicated on BCCH for
possible paging messages that might address it. If the MS receives a page before having decoded the full (P)BCCH data
for the cell, the MS shall store the page and respond once the relevant (P)BCCH data has been decoded, provided that
the cell is not barred and the MS's access class is allowed. Reception of full BCCH(BA) information is not required
before responding to the page.
If the CHANNEL RELEASE does not contain a cell selection indicator after release of all TCH and SDCCH, and the
MS has the knowledge that the cell whose channel is being released is not suitable (see 3GPP TS 43.022), the MS is
allowed to camp on any suitable cell.
If the CHANNEL RELEASE contains a cell selection indicator after release of all TCH and SDCCH and
- the MS cannot find a suitable cell from the indicated ones within 10 s, or
- none of the indicated cells are suitable,
the MS is allowed to camp on any suitable cell.
NOTE: The received signal level measurements on surrounding cells made during the last 5 seconds on the TCH
or SDCCH in A/Gb mode, or on the DBPSCH in Iu mode, may be averaged and used, where possible, to
speed up the process. However, it should be noted that the received signal level monitoring while on the
TCH or SDCCH in A/Gb mode, or on the DBPSCH in Iu mode, is on carriers in BA (SACCH), while the
carriers to be monitored for cell reselection are in BA (BCCH) or BA (GPRS).
After decoding the relevant (P)BCCH data the MS shall perform cell reselection as specified in 3GPP TS 43.022.
System Simulator:
- 2 cells, one GSM and one E-UTRA cell:
- Cell 24 GSM serving cell
UE:
None
Preamble:
U10 Active state on cell 24.as per TS 51.010 clause 40.4.3.22
Release 9
3GPP
185
3GPP TS 36.523-1 V9.3.0 (2010-12)
U S Message
1 The SS transmits an CHANNEL RELEASE
message with IE, Cell selection indicator after
release of all TCH and SDCCH including E-
UTRAN carrier frequency of Cell 1.
<-- CHANNEL RELEASE - -
Cell 1?

NOTE: The UE shall perform TAU procedure
within 30 seconds.
- - 1 -

6.2.3.19.3.3 Specific message or IE contents
Table 6.2.3.19.3.3-1: Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24[Preamble]
the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

Measurement Bandwidth 6 Default
E-UTRAN_QRXLEVMIN 17 (-106 dBm)

Table 6.2.3.19.3.3-2: Channel Release message [Table 6.2.3.19.3.2-1, Step 1]
Protocol Discriminator 0110 RR Management
Skip Indicator 0000
Message Type 00001101
RR Cause
- RR Cause Value Normal event.
<Cell Selection Indicator after release of all TCH and
SDCCH IE >::=

E-UTRAN Description 011 {1 <E-UTRAN
Description : <E-
UTRAN Description
struct >>}

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

TARGET_PCID 1

Release 9
3GPP
186
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3.20 Redirection to E-UTRA upon the release of the CS connection and no
suitable cell available
(1)
with { UE i n CS Act i ve st at e }
ensure that {
when { UE r ecei ves CHANNEL RELEASE message i ncl udi ng an I E Cell selection indicator after release
of all TCH and SDCCH, i ncl udi ng E- UTRAN car r i er f r equency of Cel l 1 ( cel l does not exi st ) }
then { UE f ai l s t o f i nd t he EUTRAN cel l ment i oned i n channel r el ease or any sui t abl e cel l and
hence r emai ns on t he GERAN Cel l . Page t he MS t o ver i f y }
}

and TS 45.008, clause 6.7.1.
[TS 44.018, clause 3.4.13.1.1]
The CHANNEL RELEASE message may include the information element "Cell selection indicator after release of all
TCH and SDCCH" which shall be used by the mobile station in its cell selection algorithm after release of all TCH and
SDCCH (see 3GPP TS 45.008).
The CHANNEL RELEASE message may include Individual priorities IE to convey individual priorities information to
the MS (see subclause 3.2.4). When the MS receives an Individual priorities IE it shall start an instance of timer T3230
with the value supplied in the Individual priorities IE.
[TS 45.008, clause 6.7.1]
In A/Gb mode, when the MS releases all TCHs or SDCCH and returns to idle mode, packet idle mode or MAC-Idle
state, it shall, as quickly as possible, camp on the cell whose channel has just been released. Similarly in Iu mode, when
the MS releases all DBPSCHs and returns to MAC-Idle state, it shall, as quickly as possible, camp on the cell whose
channel has just been released. However, in both modes (A/Gb mode or Iu mode), if the CHANNEL RELEASE
message contains a cell selection indicator after release of all TCH and SDCCH (see TS 44.018), the MS shall as
quickly as possible camp on an indicated GSM, UTRAN or E-UTRAN cell that has been identified by the CHANNEL
RELEASE message. If UTRAN or E-UTRAN frequency only is indicated the MS shall as quickly as possible camp on
a suitable cell of this frequency.
In case the cell selection indicator after release of all TCHs and SDCCH is not present, then if the full (P)BCCH data
for that cell was not decoded in the preceding 30s, the MS shall attempt to decode the full (P)BCCH data. Until the MS
has decoded the (P)BCCH data required for determining the paging group, it shall also monitor all paging blocks on
timeslot 0 of the BCCH carrier or, for GPRS if PCCCH exists and for Iu mode, on the PDCH indicated on BCCH for
possible paging messages that might address it. If the MS receives a page before having decoded the full (P)BCCH data
for the cell, the MS shall store the page and respond once the relevant (P)BCCH data has been decoded, provided that
the cell is not barred and the MS's access class is allowed. Reception of full BCCH(BA) information is not required
before responding to the page.
If the CHANNEL RELEASE does not contain a cell selection indicator after release of all TCH and SDCCH, and the
MS has the knowledge that the cell whose channel is being released is not suitable (see 3GPP TS 43.022), the MS is
allowed to camp on any suitable cell.
If the CHANNEL RELEASE contains a cell selection indicator after release of all TCH and SDCCH and
- the MS cannot find a suitable cell from the indicated ones within 10 s, or
- none of the indicated cells are suitable,
the MS is allowed to camp on any suitable cell.
NOTE: The received signal level measurements on surrounding cells made during the last 5 seconds on the TCH or
SDCCH in A/Gb mode, or on the DBPSCH in Iu mode, may be averaged and used, where possible, to speed up the
process. However, it should be noted that the received signal level monitoring while on the TCH or SDCCH in A/Gb
Release 9
3GPP
187
3GPP TS 36.523-1 V9.3.0 (2010-12)
mode, or on the DBPSCH in Iu mode, is on carriers in BA (SACCH), while the carriers to be monitored for cell
reselection are in BA (BCCH) or BA (GPRS).
After decoding the relevant (P)BCCH data the MS shall perform cell reselection as specified in 3GPP TS 43.022.
System Simulator:
- Cell 1 and Cell 24 (GSM serving cell)
UE:
None
Preamble:
U10 Active state on cell 24, as per TS 51.010 clause 40.4.3.22.
U S Message
1 The SS transmits an CHANNEL RELEASE
message with IE, Cell selection indicator after
release of all TCH and SDCCH including E-
UTRAN carrier frequency of Cell 1.

<-- CHANNEL RELEASE -

-
2 Check: Does the UE send an RRC
CONNECTION REQUEST within the next
[30s]?

--> RRC CONNECTION REQUEST 1 F
3 Page the UE in the next paging block and
atleast 50 seconds after step 1.

<--

PAGING REQUEST TYPE 1

-

-

4 Check: Does the UE send Channel Request
message with ACCESS TYPE =Page
Response ". Received on RACH?

-->

CHANNEL REQUEST

1

P

Release 9
3GPP
188
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.20.3.3-1: Channel Release message [Table 6.2.3.20.3.2-1, Step 1]
Protocol Discriminator 0110 RR Management
Skip Indicator 0000
Message Type 00001101
RR Cause
- RR Cause Value Normal event.
<Cell Selection Indicator after release of all TCH and
SDCCH IE >::=

E-UTRAN Description 011 {1 <E-UTRAN
Description : <E-
UTRAN Description
struct >>}

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

TARGET_PCID 1

Table 6.2.3.20.3.3-2: PAGING REQUEST TYPE 1 [Table 6.2.3.20.3.2-1, Step 3]
Derivation Path: 51.010 clause 40.2.4.18.

6.2.3.21 Inter-RAT cell reselection / From GPRS Packet_Transfer (NC0 mode) to E-
UTRA
(1)
with { UE i n GPRS Regi st er ed st at e wi t h act i ve packet dat a t r ansf er i n NC0 mode }
ensure that {
}

44.018, clause 3.4.1.2.1.1a.
[TS 45.008, clause 10.1.3.3]
NOTE: Throughout the specification, the phrase neighbour cell list will include also the E-UTRAN Neighbour
Release 9
3GPP
189
3GPP TS 36.523-1 V9.3.0 (2010-12)
greater than FDD_Qmin - FDD_Qmin_Offset..
selection.
NOTE: If the MS is camping on an acceptable cell, individual priorities are not discarded until an event leading to
towards this UTRAN cell as defined by the Tbarred value on the barred UTRAN cell (see 3GPP TS 25.331).
NOTE: It is FFS whether a similar requirement should be added in case of a reselection attempt towards a barred
E-UTRAN cell.
NOTE: Requirements for cells belonging to forbidden LAs for roaming should be included here.
[TS 44.018, clause 3.4.1.2.1.1a]
Release 9
3GPP
190
3GPP TS 36.523-1 V9.3.0 (2010-12)
System Simulator:
UE:
None.
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to [23].
Tables 6.2.3.21.3.2-1 & 6.2.3.21.3.2-2 illustrates the downlink power levels and other changing parameters to be
applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after
the preamble, while rows marked "T1" are to be applied subsequently. The exact instants on which these values shall be

T0
Cell-specific RS EPRE dBm/15kHz OFF
Qrxlevmin dBm -106
Srxlev* dB N/A
T1
Cell 1
>THRESH_E-
UTRAN_high


T0
RF Signal Level dBm -80 Camping on Cell 24 is guaranteed
C1* dB 21

U - S Message
1 Downlink TBF is established according to TS
51.010 clause 40.4.3.14
- - - -
2 EXCEPTION: Step 3 and 4 are repeated 5
times.
- - - -
3 The SS transmits DOWNLINK RLC DATA
BLOCK
<-- DOWNLINK RLC DATA BLOCK - -
4 The UE transmits PACKET DOWNLINK
ACK/NACK
--> PACKET DOWNLINK ACK/NACK - -
5 SS adjusts cell levels for Cell 1 according to
row T1 of table 6.2.3.21.3.2-1
- - - -
- EXCEPTION: Steps 6 and 7 are repeated until
the parallel behaviour in table 6.2.3.21.3.2-4
takes place.
- - - -
BLOCK
ACK/NACK

Release 9
3GPP
191
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.21.3.2-4: Parallel behaviour
U - S Message
Cell 1?
- - 1 -

Table 6.2.3.21.3.3-1 Repeated E-UTRAN Neighbour Cells struct of SI2Quater for Cell 24[Preamble]
SEQUENCE {

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

}

6.2.3.22 Inter-RAT Cell Reselection Failure / from GPRS Packet_Transfer (NC0
mode) to E-UTRA
(1)
wi t h { UE i n GPRS Regi st er ed st at e wi t h act i ve packet dat a t r ansf er i n NC0 mode }
ensur e t hat {
t hen { UE f ai l s t o r esel ect as t he E- UTRA cel l i s Bar r ed and r esel ct s back t o GERAN cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 10.1.3.3 , TS
44.018, clause 3.4.1.2.1.1a & TS 36.304, clause 5.3.1.
[TS 45.008, clause 10.1.3.3]
NOTE 1: Throughout the specification, the phrase neighbour cell list will include also the E-UTRAN Neighbour
Release 9
3GPP
192
3GPP TS 36.523-1 V9.3.0 (2010-12)
greater than FDD_Qmin - FDD_Qmin_Offset.
selection.
NOTE 2: If the MS is camping on an acceptable cell, individual priorities are not discarded until an event leading to
towards this UTRAN cell as defined by the Tbarred value on the barred UTRAN cell (see 3GPP TS 25.331).
NOTE 3: It is FFS whether a similar requirement should be added in case of a reselection attempt towards a barred
E-UTRAN cell.
NOTE 4: Requirements for cells belonging to forbidden LAs for roaming should be included here.
[TS 44.018, clause 3.4.1.2.1.1a]
Release 9
3GPP
193
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 36.304, clause 5.3.1]
Elements:
In case of multiple PLMNs indicated in SIB1 sharing, this IE is common for all PLMNs
...
...
- else
- The UE shall exclude the barred cell and the cells on the same frequency as a candidate for cell
selection/reselection for 300 seconds.
System Simulator:
UE:
None.
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to [23].
Release 9
3GPP
194
3GPP TS 36.523-1 V9.3.0 (2010-12)

T0
Qrxlevmin dBm -106
Srxlev* dB N/A
cellBarred - barred E-UTRAN cell is Barred, as
indicated in
SystemInformationBlockType1
(Table 6.2.3.22.3.3-2)
T1
Cell 1
>THRESH_E-
UTRAN_high
cellBarred - barred E-UTRAN cell is Barred, as
indicated in
SystemInformationBlockType1
(Table 6.2.3.22.3.3-2)


T0
C1* dB 21

U - S Message
51.010 clause 40.4.3.14
- - - -
EXCEPTION: Step 3 and 4 are repeated 5
times.
- - - -
BLOCK
ACK/NACK
row T1 of table 6.2.3.22.3.2-1
- - - -
- EXCEPTION: Steps 6 and 7 are repeated until
the TBF is released in Cell 24.
- - - -
BLOCK
ACK/NACK
- NOTE: UE tries to Synchornise with Cell 1 and
acquire System Information Blocks. On
acquiring SystemInformationBlockType1 for
Cell1, UE fails to reselct to E-UTRAN as Cell 1
is Barred.
- - - -
8 Check: Does UE send Channel Request on
Cell 24?
9 SS sends Immediate assignment <-- IMMEDIATE ASSIGNMENT
10 Check: Does UE send Cell Update? --> CELL UPDATE 1 P
51.010 clause 40.4.3.14 and data transfer is
completed.
- - - -

Release 9
3GPP
195
3GPP TS 36.523-1 V9.3.0 (2010-12)
SEQUENCE {

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

}

Table 6.2.3.22.3.3-2: SystemInformationBlockType1 for Cell1[Preamble]
cellBarred barred
intraFreqReselection notallowed
}
}

6.2.3.23 Inter-RAT Cell Reselection from GPRS Packet transfer to E-UTRA in CCN
Mode(PACKET CELL CHANGE CONTINUE)
(1)
ensur e t hat {
when { UE det ect s t he cel l r e- sel ect i on cr i t er i a ar e met f or t he cel l and i n CCN mode }
t hen { UE l eaves CCN mode, r esel ect s t he E- UTRA cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 45.008 section 6.6.6,
10.1.3.3,10.1.4 and TS44.060 section 5.5.1.1a.2 and 5.5.2.3
[TS 45.008, section 6.6.6 and 10.1.3.3]
The algorithm in this subclause shall be used for inter-RAT cell reselection if priorities are available to the MS and
thresholds are provided by the network, and if the mobile station supports priority based inter-RAT cell re-selection and
priority information for the serving cell is provided by the network. A mobile station supporting E-UTRAN shall
support priority based inter-RAT cell re-selection towards all the supported RATs. A mobile station not supporting E-
UTRAN and supporting UTRAN and supporting priority based reselection from UTRAN to GERAN shall support
priority based inter-RAT cell re-selection towards UTRAN
The network shall provide priority information if E-UTRAN frequencies are included in the neighbour cell list. If
priority information is available to the mobile station and the mobile station supports priority based inter-RAT cell re-
selection, the algorithm in this subclause shall be used for inter-RAT reselection towards all RATs.
Release 9
3GPP
196
3GPP TS 36.523-1 V9.3.0 (2010-12)
If the 3G Cell Reselection list or the E-UTRAN Neighbour Cell list include frequencies of other radio access
technologies, 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.
a non-serving inter-RAT cell and XXX indicates the other radio access technology/mode and is defined as follows:
- for a E-UTRAN cell, is the measured RSRP value for the cell minus E-UTRAN_QRXLEVMIN for the cells
frequency if THRESH_E-UTRAN_high_Q is not provided; otherwise, if THRESH_E-UTRAN_high_Q is provided, is
the measured RSRQ value for the cell minus E-UTRAN_QQUALMIN for the cells frequency.
[TS 45.008, clause 10.1.4]
The network may request measurement reports from the MS and control its cell re-selection. This is indicated by the
parameter NETWORK_CONTROL_ORDER. The meaning of the different parameter values is specified as follows:
NC0 Normal MS control
The MS shall perform autonomous cell re-selection.
NC1 MS control with measurement reports
The MS shall send measurement reports to the network as defined in subclause 10.1.4.1.
NC2 Network control
The MS shall only perform autonomous cell re-selection when the reselection is triggered by a
downlink signalling failure as defined in subclause 6.5 or a random access failure as defined in
3GPP TS 44.018 and 3GPP TS 44.060 or if the cell is barred or the C1 criterion falls below zero.
The MS shall only determine whether the cell is barred once camped on the cell.
RESET The MS shall return to the broadcast parameters. Only sent on PCCCH or PACCH.
All signalling for support of network controlled cell re-selection and measurement reports are defined in 3GPP TS
44.060 section 5.5.1.1a.2 and 5.5.2.3.
System Simulator:
- Cell 24 is serving GERAN Cell
- Cell 1 is suitable E-UTRAN Cell
UE:
None.
Preamble:
- The UE is GPRS attached and the PDP context 2 activated according to section 41.2.8.1.1 and 40.4.3.15 of
TS51010-1
Release 9
3GPP
197
3GPP TS 36.523-1 V9.3.0 (2010-12)

Parameter Unit Cell 1 Cell24 Remark
T1 Cell-specific RS EPRE dBm/15kHz -60
No change The power level is
such that
SrxlevCell 1 >0

U - S Message
1 Uplink dynamic allocation two phase access
according to TS 51.010 clause 40.4.3.9 using
n=5000 octets of data
- - - -
2 EXCEPTION: MS continues to transfer data
and send measurement reports for cell 1 in
PACKET MEASUREMENT REPORT in
parallel to steps 3 to 4
- - - -
row T1 of table 6.2.3.23.3.2-1
- - - -
4 The UE transmists PACKET CELL CHANGE
NOTIFICATION to E_UTRA cell on 24
--> PACKET CELL CHANGE
NOTIFICATION

5 The SS sends PACKET CELL CHANGE
CONTINUE for cell 1 as the target cell on cell
24
<-- PACKET CELL CHANGE
CONTINUE
- -
6 Check: Does UE send RRC CONNECTION
REQUEST on cell1?
7 SS sends RRCConnectionSetup to the UE <-- RRCConnectionSetup - -
RRCConnectionSetupComplete message on
cell 1?

Serving Cell Priority Parameters ::=
{

GERAN_PRIORITY 001B This filed specifies
GERAN cell priority

}
{

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

}
E-UTRAN Parameters Description struct ::=
{

E-UTRAN_CCN_ACTIVE 1 CCN is enabled in
the cell

}

Release 9
3GPP
198
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.23.3.3-2: PACKET CELL CHANGE CONTINUE (step 5, Table 6.2.3.23.3.3-2)
Packet Cell Change Continue message content ::=
PAGE_MODE 00B Normal Paging
Global TFI TFI of the uplink TBF
ARFCN ARFCN of the cell 1

BSIC Range 0 to 63
CONTAINTER_ID Range 0 to 2

6.2.3.24 Void
6.2.3.25 Void
6.2.3.26 Void
6.2.3.27 Inter-RAT Cell selection from GPRS Packet_transfer to E-UTRA (NC2 Mode)
( 1) wi t h { UE i n GPRS Regi st er ed st at e wi t h act i ve packet dat a t r ansf er i n NC2 mode }
ensur e t hat {
when { UE det ect s net wor k r e- sel ect i on cr i t er i a ar e met on t he E- UTRA cel l }
t hen { UE per f or ms cel l change t o E- UTRA cel l and t he dat a t r ansf er i s cont i nued and compl et ed
i n E- UTRA cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 6.4, 10.1.4,
and 10.1.4.2:
[TS 45.008, clause 6.4]
C1 =(A - Max(B,0))
where
system.
[TS 45.008, clause 10.1.4]
Release 9
3GPP
199
3GPP TS 36.523-1 V9.3.0 (2010-12)
NC2 Network control
A list given by Packet Cell Change Order applies in the new cell. This list may also include cells with other radio access
technologies.
44.060.
If the MS operates in NC2 mode, the following rules shall be applied:
- The network controls the measurements of UTRAN cells by the parameter Qsearch_P. The network controls the
measurements of E-UTRAN cells by the parameter Qsearch_P_E-UTRAN.
- The network may control UTRAN measurements per individual UTRAN frequency by the parameters
Measurement_Control_UTRAN and E-UTRAN measurements per individual E-UTRAN frequency by the
parameters Measurement_Control_E-UTRAN.
[TS 45.008, clause 10.1.4.1]
When ordered to send measurement reports, the MS shall continuously monitor all carriers in BA(GPRS) or as
indicated by the parameter NC_FREQUENCY_LIST and the BCCH carrier of the serving cell. The measurement
requirements are defined in subclause 10.1.1 for the actual packet mode
[TS 44.018, clause 3.4.1.2.1.1a]
fast acquisition of system information procedure, as defined in subclause 3.4.1.2.1.11, shall be used to acquire E-
UTRAN measurement parameters and neighbour cell information from SI2quater and MEASUREMENT
INFORMATION.
System Simulator:
- 2 Cells, one GSM and one E-UTRA:
-Cell 24 GSM serving cell
-Cell 1 non-suitable Off cell
UE:
- None
Preamble:
- The UE is GPRS attached to the home PLMN and the PDP context 2 activated according to TS 51.010-1 clause
40.4.3.15.
Release 9
3GPP
200
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.27.3.2-1: Time instances of cell power level and parameter changes (E-UTRA and GERAN
cell)

T1
Cell-specific RS EPRE dBm/15kHz -70 - S
rxlevCell1
>0
Qrxlevmin dBm -106 - -
Qrxlevminoffset dB 0 - -
Pcompensation dB 0 - -
C1* dB - <0 Cell 24 become
weakest cell
Note: S
rxlev
is calculated in the UE
C1 is calculated in the UE

U - S Message
1 Uplink dynamic allocation two phase access
according to TS 51.010 clause 40.4.3.9 using
n=1500 octets of data.
--> - - -
2 The UE transmits PACKET MEASUREMENT
REPORT
--> PACKET MEASUREMENT
REPORT
- -
table 6.2.3.27.3.2-1.
- - - -
- EXCEPTION: Step 2 is repeated until
measurement results for cell 1 are included in
the PACKET MEASUREMENT REPORT
message in step 4. SS continues to transfer
data in parallel of step 4.
- - - -
REPORT for cell 1 are included in the
PACKET MEASUREMENT REPORT message
REPORT
- -
REQUEST on cell 1?
6 SS sends RRCCconnectionSetup to the UE <-- RRCCconnectionSetup - -
RRCCconnectionSetupComplete message on
cell 1?
--> RRCCconnectionSetupComplete
NAS: TRACKING AREA UPDATE
REQUEST
1 P
8-
11
Steps 4 to 7 from generic prodedure 36.508
Table 6.4.2.7A-1 are executed
- - - -
{How to handle data from GERAN to E-
UTRAN is under FFS}
- - - -

Release 9
3GPP
201
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.27.3.3-1: SI2Quater for Cell 24 (Preamble)
Derivation Path: 44.018 Table 10.5.2.33b.1
Serving Cell Priority Parameters Description::=
SEQUENCE {

GERAN_PRIORITY 7
THRESH_GSM_low 0(-98 dBm)
H_PRIO Hysteresis used in
the priority
reselection algorithm

T_Reselection 3(=20 seconds) Time hysteresis in
the reselection
algorithm

}
SEQUENCE {

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

}

Table 6.2.3.27.3.3-2: Message ATTACH REQUEST (Preamble)
Derivation Path: Table 9.4.1/3GPP TS 24.008
MS Radio Access capability
GERAN to E-UTRA support in GERAN packet
transfer mode
10B or 11B UTRAN Neighbour
Cell measurements
and MS autonomous
cell reselection to E-
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN

Mobile station classmark 3
E-UTRA FDD support 0B or 1B C1
E-UTRA TDD support 0B or 1B C1

C1 At least one of these fields shall be set to 1B

Release 9
3GPP
202
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.27.3.3-3: Message PACKET MEASUREMENT ORDER (step 4, Table 6.2.3.27.3.2-2)
NC Measurement parameters ::={
NETWORK_CONTROL_ORDER 10B NC2
NC_REPORTING_PERIOD_I 111B 61.44 sec
NC_REPORTING_PERIOD_T 010B 1.92 sec
}
NC_FREQUENCY_LIST 0 Not present

Table 6.2.3.27.3.3-4: RRCConnectionRequest (step 5, Table 6.2.3.27.3.2-2)
Derivation Path: 36.508 table 4.6.1-16
ue-Identity Any allowed value

6.2.3.28 Inter-RAT Cell Reselection from GPRS Packet_transfer to E-UTRA (Network
Assisted Cell Change)
( 1) wi t h { UE i n GPRS Regi st er ed st at e wi t h act i ve packet dat a t r ansf er i n NC2 mode }
ensur e t hat {
when { UE det ect s net wor k assi st ed cel l change and t he t ar get E- UTRA cel l }
t hen { UE r esel ect s f or t he t ar get E- UTRA cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 10.1.4, and
10.1.4.2:
[TS 45.008, clause 10.1.4]
NC2 Network control
technologies.
44.060.
Release 9
3GPP
203
3GPP TS 36.523-1 V9.3.0 (2010-12)
[TS 45.008, clause 10.1.4.1]
When ordered to send measurement reports, the MS shall continuously monitor all carriers in BA(GPRS) or as
indicated by the parameter NC_FREQUENCY_LIST and the BCCH carrier of the serving cell. The measurement
requirements are defined in subclause 10.1.1 for the actual packet mode
[TS 45.008, clause 10.1.4.2]
A cell re-selection command may be sent from the network to an MS. When the MS receives the command, it shall re-
select the cell according to the included cell description and change the network control mode according to the
command (see 3GPP TS 44.060). The command may include re-selection of another radio access technology/mode.
[TS 44.018, clause 3.4.1.2.1.1a]
fast acquisition of system information procedure, as defined in subclause 3.4.1.2.1.11, shall be used to acquire E-
UTRAN measurement parameters and neighbour cell information from SI2quater and MEASUREMENT
INFORMATION.
System Simulator:
UE:
Preamble:
- The UE is GPRS attached to the home PLMN and the PDP context 2 activated according to [23].
Table 6.2.3.28.3.2-1: Time instances of cell power level and parameter changes for the E-UTRA cell

T0
Qrxlevmin dBm -106
Pcompensation dB 0
T1
Cell-specific RS EPRE dBm/15kHz -70 S
rxlevCell1
>0
Qrxlevmin dBm -106
Pcompensation dB 0
Note: S
rxlev
is calculated in the UE

Release 9
3GPP
204
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.28.3.2-2: Time instances of cell power level and parameter changes for the GERAN cell

T0
C1* dB 21
T1
C1* dB 21

U - S Message
1 UE is brought into downlink packet transfer
mode . SS sends PACKET DOWNLINK
ASSIGNMENT
<-- PACKET DOWNLINK
ASSIGNMENT
- -
2 SS sends PACKET MEASUREMENT ORDER <-- PACKET MEASUREMENT
ORDER
- -
3 SS sends downlink data <-- - - -
REPORT
REPORT

tables 6.2.3.28.3.2-1 and 6.2.3.28.3.2-2.
- - - -
6 EXCEPTION: Step 3 to 4 are repeated until
message
- - - -
7 SS sends PACKET CELL CHANGE ORDER
for cell 1 as the target cell
<-- PACKET CELL CHANGE ORDER - -
REQUEST on cell 1?
9 SS sends RRCCconnectionSetup to the UE <-- RRCCconnectionSetup - -
RRCCconnectionSetupComplete message on
cell 1?
--> RRCCconnectionSetupComplete 1 P

Table 6.2.3.28.3.3-1: SI2Quater for Cell 24 (Preamble)
SEQUENCE {

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

}

Release 9
3GPP
205
3GPP TS 36.523-1 V9.3.0 (2010-12)
transfer mode
Cell measurements
and MS autonomous
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN

..E-UTRA TDD support 0B or 1B C1


}

Table 6.2.3.28.3.3-4: Message PACKET CELL CHANGE ORDER (step 7, Table 6.2.3.28.3.2-3)
IMMEDIATE_REL 1
ARFCN, BSIC specified for cell 1
}


Release 9
3GPP
206
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3.29 Void
6.2.3.30 Inter-RAT Cell Reselection failure from GPRS Packet transfer to E-UTRA
(Network Assisted Cell Change)
(1)
ensur e t hat {
when { UE det ect s net wor k assi st ed cel l change and cel l r e- sel ect i on f ai l ur e f or t he t ar get E- UTRA
cel l }
t hen { UE r esel ect s back t he GERAN cel l and downl i nk dat a t r ansf er i s cont i nued and compl et ed i n
GERAN cel l }
}

References: The conformance requirements covered in the present TC are specified in: TS 45.008, clause 10.1.4, and
10.1.4.2:
[TS 45.008, clause 10.1.4]
NC2 Network control
technologies.
44.060.
[TS 45.008, clause 10.1.4.2]
A cell re-selection command may be sent from the network to an MS. When the MS receives the command, it shall re-
select the cell according to the included cell description and change the network control mode according to the
command (see 3GPP TS 44.060). The command may include re-selection of another radio access technology/mode.
If a UTRAN capable MS receives a cell re-selection command towards a not known UTRAN cell (see 3GPP TS 25.133
and 3GPP TS 25.123), or if a E-UTRAN capable MS receives a cell re-selection command towards a not known E-
Release 9
3GPP
207
3GPP TS 36.523-1 V9.3.0 (2010-12)
UTRAN cell (see 3GPP TS 36.133), then the MS shall search for synchronisation information up to 800 ms. In case of
failure, the MS shall return to the old cell and indicate a packet cell change failure (see 3GPP TS 44.060).
System Simulator:
UE:
The HPLMN is PLMN1.
Preamble:
- The UE is GPRS attached to the home PLMN and the PDP context 2 activated according to [23].

T0
Qrxlevmin dBm -106
Pcompensation dB 0
T1 Cell-specific RS EPRE dBm/15kHz -70
The power level is such that
SrxlevCell 1 >0


T0
C1* dB 21
T1
C1* dB 21

Release 9
3GPP
208
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 UE is brought into downlink packet transfer
mode . SS sends PACKET DOWNLINK
ASSIGNMENT
<-- PACKET DOWNLINK
ASSIGNMENT
- -
2 SS sends PACKET MEASUREMENT ORDER <-- PACKET MEASUREMENT
ORDER
- -
3 SS sends downlink data <-- - - -
REPORT
REPORT

row T1 of table 6.2.3.30.3.2-1
- - - -
6 EXCEPTION: Step 3 to 4 are repeated until
message
- - - -
7 SS sends PACKET CELL CHANGE ORDER
for cell 1 as the target cell
<-- PACKET CELL CHANGE ORDER - -
8 UE sends RRCConnectionRequest to cell 1 --> RRCConnectionRequest - -
9 SS sends RRCConnectionReject to the UE <-- RRCConnectionReject - -
10 All the UL/DL messages sent in steps 11-20
shall be sent on cell 24.
- - -
11 Check: Does the UE send CHANNEL
REQUEST ?
12 SS sends IMMEDIATE ASSIGNMENT <-- IMMEDIATE ASSIGNMENT - -
13 Check: Does the UE send PACKET CELL
CHANGE FAILURE?
--> PACKET CELL CHANGE
FAILURE
1 P
14 UE may perform ROUTING AREA UPDATE
procedure
SS sends PACKET DOWNLINK
ASSIGNMENT
<-- PACKET DOWNLINK
ASSIGNMENT
- -
15 SS sends downlink data until downlink
data transfer is complete
<-- - - -
Note 1: GERAN cell priority is not allocated, hence it will be considered as the less than all allowed values of 1 to 8.

Table 6.2.3.30.3.3-1: Message SI2Quater for Cell 24 (Preamble)
SEQUENCE {

the E-UTRA Absolute
Radio Frequency
Channel Number as
defined in
3GPP TS 36.104.

}

Release 9
3GPP
209
3GPP TS 36.523-1 V9.3.0 (2010-12)
transfer mode
Cell measurements
and MS autonomous
UTRAN and CCN
towards E-UTRAN,
E-UTRAN Neighbour
Cell measurement
reporting and
Network controlled
UTRAN

..E-UTRA TDD support 0B or 1B C1


}

Table 6.2.3.30.3.3-4: Message PACKET CELL CHANGE ORDER (step 7, Table 6.2.3.30.3.2-3)
IMMEDIATE_REL 1
ARFCN, BSIC specified for cell 1
}


Table 6.2.3.30.3.3-6: Message PACKET CELL CHANGE FAILURE (step 13, Table 6.2.3.30.3.2-3)
CAUSE 0010B

Release 9
3GPP
210
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3.31 Inter-RAT cell reselection / From UTRA_Idle (low priority) to E-UTRA
RRC_IDLE (high priority) according to RAT priority provided by dedicated
signalling
(1)
ensure that {
when { UE det ect s t he cel l r e- sel ect i on cr i t er i a ar e met f or t he cel l whi ch bel ongs t o t he hi gh
pr i or i t y i nt er - RAT E- UTRA cel l based on t he conf i gur ed RAT pr i or i t y pr ovi ded by dedi cat ed
si gnal i ng }
}

5.2.6.1.4a; TS 25.331, clause 8.3.3.3 and 8.6.7.23; TS 36.331, clause 5.3.3.4.
[TS 25.304, clause 5.2.6.1.2a]
serving cell.
above or below S
prioritysearch1
and S
prioritysearch2
- If Srxlev
ServingCell
>S
prioritysearch1
and Squal
ServingCell
>S
prioritysearch2
- If Srxlev
ServingCell
<=S
prioritysearch1
or Squal
ServingCell
<=S
prioritysearch2
[TS 25.304, clause 5.2.6.1.4a]

nonServingCell,x
Thresh
x,high

ServingCell
<Thresh
serving,low
or Squal
ServingCell
<0 and the Srxlev
nonServingCell,x
of a cell on an
x,low
is fulfilled.

fulfilled.
Release 9
3GPP
211
3GPP TS 36.523-1 V9.3.0 (2010-12)
nonServingCell,x
among
serving cell.
[TS 25.331, clause 8.3.3.3]
When the UE receives a UTRAN MOBILITY INFORMATION message, it shall:
1>act on received information elements as specified in subclause 8.6;
1>if the IE "Dedicated Priority Information" is present:
2>act upon the received IE as described in subclause 8.6.7.23.
[TS 25.331, clause 8.6.7.23]
If the CHOICE "Action" has the value "Configure dedicated priorities", the UE shall:
1>clear the variable PRIORITY_INFO_LIST;
1>stop timer T322, if it is running;
1>set the value of IE "Priority status" in the variable PRIORITY_INFO_LIST to "dedicated_priority";
1>for each occurrence of the IE "Priority Level List":
2>create a new entry in the IE "Priority Info List" in the variable PRIORITY_INFO_LIST, and in that new
entry:
3>set the CHOICE "Radio Access Technology" to the value received in the IE "Priority Level List";
3>set the IE "priority" to the value received in the IE "Priority Level List";
3>set the values in IE "Frequency List" or "BCCH ARFCN List" to the values received in the IE "Priority
Level List".
1>set the IE "E-UTRA detection" to the value received in the IE "Priority Level List".
1>if the IE "T322" is present:
2>start timer T322 using the value signalled in this IE.
1>if the UE is not in CELL_DCH state:
2>take the actions as described in subclause 8.1.1.6.19 using stored System information Block type 19.
[TS 36.331, clause 5.3.3.4]
The UE shall:
1>stop timer T300;
Release 9
3GPP
212
3GPP TS 36.523-1 V9.3.0 (2010-12)
...
procedure ends;
System Simulator:
NOTE: Common Priority information for Cell 1 & Cell 5: UTRA priority =3; E-UTRA priority =4.
UE:
None.
Preamble:
- The UE is in state PS-DCCH+DTCH_DCH (state 6-10) on Cell 5 according to [5].
Tables 6.2.3.31.3.2-1 and 6.2.3.31.3.2-2 illustrates the downlink power levels and other changing parameters to be
applied for the cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the
preamble, while row marked "T1" is to be applied subsequently. The exact instants on which these values shall be
T0
Srxlev* dB 9
T1
Cell-specific RS EPRE dBm/15kHz
-79
qRxLevMinEUTRA
S
>Thresh
Cell1,high


Release 9
3GPP
213
3GPP TS 36.523-1 V9.3.0 (2010-12)
T0
Srxlev* dB 19
T1
Srxlev* dB 4

U - S Message
1 The SS provides dedicated priority information
(UTRA priority =3; E-UTRA priority =4) and
validity timer to the UE.
<-- UTRAN MOBILITY
INFORMATION
- -
2 The UE transmits UTRAN MOBILITY
INFOMRATION CONFIRM message on Cell 5.
--> UTRAN MOBILITY
INFORMATION CONFIRM
- -
RELEASE message to release UE connection.
<-- RRC CONNECTION RELEASE - -
RELEASE COMPLETE message on Cell 5.
COMPLETE
- -
COMPLETE
- -
COMPLETE
- -
1 and table 6.2.3.31.3.2-2.
- - - -
subclause 6.4.2.7A indicate that the UE is
camped on E-UTRAN Cell 1?
- - 1 -

Release 9
3GPP
214
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.31.3.3-1: UTRAN MOBILITY INFORMATION for Cell 5 (step 1, Table 6.2.3.31.3.2-3)
UTRANMobilityInformation ::=CHOICE {
r7 SEQUENCE {
utranMobilityInformation-v860ext SEQUENCE
{

dedicatedPriorityInformation SEQUENCE {
action CHOICE {
configureDedicatedPriorities SEQUENCE
{

t-322 5 Time in minutes
priorityLevelList SEQUENCE (SIZE
(1..maxPrio)) OF SEQUENCE {
2 entry
priority[1] 3
utraFDD SEQUENCE (SIZE
(1..maxNumFDDFreqs)) OF SEQUENCE {
1 entry UTRA-
FDD
as used for Cell 5

}
utraTDD SEQUENCE (SIZE
(1..maxNumTDDFreqs)) OF SEQUENCE {
1 entry UTRA-
TDD
as used for Cell 5

}
}
priority[2] 4
eutra SEQUENCE (SIZE
(1..maxNumEUTRAFreqs)) OF SEQUENCE {
1 entry
earfcn Same downlink EARFCN
as used for Cell 1

}
}
}
e-UTRA detection TRUE
}
}
}
}
}
}
}
}
}
}


Release 9
3GPP
215
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.2.3.31.3.3-2: RRC CONNECTION RELEASE for Cell 5 (step 3, Table 6.2.3.31.3.2-3)
RRCConnectionRelease ::=CHOICE {
r4 SEQUENCE {
n-308 2 2 (for CELL_DCH
state). Not
Present (for UE in
other connected
mode states).

releaseCause normalEvent
rplmn-information Not Present
}
v4d0NonCriticalExtensions SEQUENCE {} Not Present
}
}
}
}

6.2.3.31.3.2-3)
s-PrioritySearch1 8 (16 dB)
threshServingLow 4 (8 dB)
}
}
1 entry
earfcn [1] Same downlink EARFCN
as used for Cell 1

measurementBandwidth [1] Not present
qRxLevMinEUTRA [1] -53 (-106 dBm)
threshXhigh [1] 12 (24 dB)
threshXlow [1] 8 (16 dB)
}
}

6.2.3.31.3.2-3)
threshServingLow 5 (10dB)
}
}

Release 9
3GPP
216
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.2.3.31.3.2-3)
1 entry UTRA-FDD
carrierFreq[1] Downlink UARFCN of
Cell 5

threshX-High[1] 5 (10dB)
threshX-Low[1] 5 (10dB)
}
1 entry UTRA-TDD
carrierFreq[1] Downlink UARFCN of
Cell 5

threshX-High[1] 5 (10dB)
threshX-Low[1] 5 (10dB)
}
}


6.3 Closed Subscriber Group cells
6.3.1 Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-
CSG cell to E-UTRA RRC_IDLE CSG cell
6.3.1.1 Test Purpose (TP)
(1)
ensure that {
when { Manual CSG I D sel ect i on i s r equest ed }
then { UE sel ect s t he r equest ed CSG cel l }
}

(2)
with { UE i n E- UTRA RRC_I DLE st at e on a non- CSG cel l and UE s Al l owed CSG l i st i s not empt y }
ensure that {
when { a pr evi ousl y vi si t ed al l owed E- UTRA CSG cel l becomes t he st r ongest cel l on i t s f r equency }
then { UE r esel ect s t he E- UTRA CSG cel l }
}

6.3.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.8.1, and
36.133, clauses 4.2.2.10 and 4.2.2.10.1.
[TS 36.304, clause 5.2.4.8.1]
In addition to normal cell reselection, the UE shall use an autonomous search function to detect at least previously
visited allowed CSG cells on non-serving frequencies, including inter-RAT frequencies, according to the performance
requirements specified in [10], when at least one CSG ID is included in the UEs CSG whitelist. The UE may also use
autonomous search on the serving frequency. The UE shall disable the autonomous search function for CSG cells if the
UEs CSG whitelist is empty.
Release 9
3GPP
217
3GPP TS 36.523-1 V9.3.0 (2010-12)
NOTE: The UE autonomous search function, per UE implementation, determines when and/or where to search
for allowed CSG cells.
If the UE detects one or more suitable CSG cells on different frequencies, then the UE shall reselect to one of the
detected cells irrespective of the frequency priority of the cell the UE is currently camped on, if the concerned CSG cell
is the highest ranked cell on that frequency.
[TS 36.133, clause 4.2.2.10]
Reselection from non CSG to CSG cells may be performed using UE autonomous search as defined in [1] when at least
one CSG ID is included in the UEs CSG whitelist. The requirements in this section are valid for reselection to CSG
cells previously visited by the UE when the radio configuration parameters, including the carrier frequency and physical
cell identity of the CSG cell, non CSG cell and other neighbour cells are unchanged from the most recent previous visit.
[TS 36.133, clause 4.2.2.10.1]
The UE shall perform search and reselection to an allowed inter-frequency CSG cell that has met reselection criterion
defined in [1] and that is in its whitelist, within [6] minutes in the conditions shown in table 4.2.2.10.1-1. There is no
need for statistical testing of this requirement.
Table 4.2.2.10.1-1: Parameters for CSG inter-frequency reselection
Parameter Unit Cell 1 Cell 2
E-UARFCN
Note1
Channel 1 Channel 2
CSG indicator False True
Physical cell identity
Note1
1 2
CSG identity Not sent Already stored
in UE whitelist
from previous
visit
Propagation conditions Static, non multipath
CSG cell previously
visited by UE
Yes
PBCH_RA dB

0

0
PBCH_RB dB
PSS_RA dB
SSS_RA dB
PCFICH_RB dB
PHICH_RA dB
PHICH_RB dB
PDCCH_RA dB
PDCCH_RB dB
PDSCH_RA dB
PDSCH_RB dB
OCNG_RA
Note 1
dB
OCNG_RB
Note 1
dB
Qrxlevmin dBm -140 -140
oc
N

dBm/15 kHz Off
RSRP
Note2
dBm/15 KHz [TBD] [TBD]
Note 1: For this requirement to be applicable, the E-UARFCN and physical cell
identity for cell 1 and cell 2 shall be unchanged from when the CSG cell
was visited previously

Note 2: Chosen to ensure that CSG autonomous search has a high probability of
success on every attempt made by UE

6.3.1.3 Test description
6.3.1.3.1 Pre-test conditions
System Simulator:
- Cell 1, Cell 3, Cell 11 and Cell 23.
- Cell 1, Cell 11 and Cell 23 are not CSG cells.
Release 9
3GPP
218
3GPP TS 36.523-1 V9.3.0 (2010-12)
- Cell 3 is a CSG cell.
UE:
- If pc_Allowed_CSG_list, the UEs Allowed CSG list is empty.
Preamble:
6.3.1.3.2 Test procedure sequence
Table 6.3.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
various time instants of the test execution. Configurations marked "T0", "T1", "T2", "T3" and "T4" are applied at the
points indicated in the Main behaviour description in Table 6.3.1.3.2-2.
Table 6.3.1.3.2-1: Time instances of cell power level and parameter changes
Parameter Unit Cell 1 Cell 3 Cell 11 Cell 23 Remark
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-65 Off Off Off The power levels are such
guaranteed.
Qrxlevmin dBm -140 -140 -140 -140
Srxlev* dB 75 - - -
T1 Cell-specific RS
EPRE
dBm/15k
Hz
-65 -85 Off -91
Srxlev* dB 75 55 - 49
T2 Cell-specific RS
EPRE
dBm/15k
Hz
Off Off -65 Off The power levels are such
guaranteed.
Srxlev* dB - - 75 -
T3 Cell-specific RS
EPRE
dBm/15k
Hz
-65 Off -91 -85
Srxlev* dB 75 - 49 55
T4 Cell-specific RS
EPRE
dBm/15k
Hz
-65 -85 Off -91
Srxlev* dB 75 55 - 49

Release 9
3GPP
219
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.1.3.2-2: Main behaviour
U - S Message
2-
17
NOTE: the UE performs registration and the
- - - -
according to row "T1" in table 6.3.1.3.2-1.
- - - -
19 The UE is made to perform manual CSG ID
selection and select Cell 3.
- - - -
indicate that the UE is camped on Cell 3?
- - 1 -
21 The SS changes Cell1, Cell 3, Cell 11 and Cell
23 levels according to row "T2" in table
6.3.1.3.2-1.
- - - -
22-
27
Steps 1 to 6 of the TAU procedure described
in TS 36.508 subclause 6.4.2.7 are performed
on Cell 11.
NOTE: the UE performs a TAU and the RRC
connection is released.
- - - -
28 The SS changes Cell 1, Cell 11 and Cell 23
levels according to row "T3" in table 6.3.1.3.2-
1.
- - - -
29-
34
Steps 1 to 6 of the TAU procedure described
in TS 36.508 subclause 6.4.2.7 are performed
on Cell 1.
NOTE: the UE performs a TAU and the RRC
- - - -
1.
- - - -
36 Check: Does the test result of Steps 1 to 5 of
subclause 6.4.2.7 indicate that the UE is
camped on Cell 3 within [6] min?
- - 2 -

6.3.1.3.3 Specific message contents
Table 6.3.1.3.3-1: Conditions for table 6.3.1.3.3-2

Release 9
3GPP
220
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.1.3.3-2: SystemInformationBlockType1 for Cell 1, 3, 11 and 23 (preamble and all steps,
Table 6.3.1.3.2-2)
csg-Indication FALSE Cell 1
Cell 11
Cell 23
TRUE Cell 3
csg-Identity Not present Cell 1
Cell 11
Cell 23
'000 0000 0000 0000
0000 0000 0011'B
Cell 3
}
}

Table 6.3.1.3.3-3: SystemInformationBlockType4 for Cell 3 (Pre-test conditions and all steps, table
6.3.1.3.2-2)
csg-PhysCellIdRange ::=SEQUENCE {
start 3
range Not present The UE shall
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.

}
}

6.3.2 Void
6.3.3 Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE
CSG cell
(1)
with { UE i n UTRA I DLE st at e }
ensure that {
when { Manual CSG I D sel ect i on i s r equest ed }
then { UE sel ect t he sui t abl e E- UTRAN CSG cel l }
}

(2)
with { UE i n UTRA I DLE st at e and UE s Al l owed CSG l i st i s not empt y }
ensure that {
when { UE det ect s a sui t abl e E- UTRAN CSG cel l pr evi ousl y vi si t ed }
then { UE r esel ect s t he sui t abl e pr evi ousl y vi si t ed E- UTRAN CSG cel l i r r espect i ve of t he EUTRAN
cel l r esel ect i on pr i or i t y }
}

Release 9
3GPP
221
3GPP TS 36.523-1 V9.3.0 (2010-12)
References: The conformance requirements covered in the present TC are specified in: TS 25.304, clause 5.6.1,
5.2.6.4.1 and TS 36.304 clause 5.2.4.8.1, 5.2.4.6, 5.2.4.8.2, 5.2.4.1.
[TS 24.301, clause 5.5.3.2.4]
If the UE has initiated the tracking area updating procedure due to manual CSG selection and receives a TRACKING
AREA UPDATE ACCEPT message, the UE shall check if the CSG ID of the cell where the UE has sent the
TRACKING AREA UPDATE REQUEST message is contained in the Allowed CSG list. If not, the UE shall add that
CSD ID to the Allowed CSG list.
[TS 25.304, clause 5.6.1]
In the UE on request of NAS, the AS shall scan all RF channels in the UTRA bands according to its capabilities to find
available CSG IDs. On each carrier, the UE shall at least search for the strongest cell, read its system information and
report available CSG ID(s) together with their HNB name (if broadcast) and PLMN(s) to the NAS. The search for
available CSG IDs may be stopped on request of the NAS.
If NAS has selected a CSG ID and provided this selection to AS, the UE shall search for an acceptable or suitable cell
belonging to the selected CSG ID to camp on.
[TS 25.304, clause 5.2.6.4.1]
requirements specified in [10], when at least one CSG ID is included in the UEs CSG whitelist. The UE is required to
perform autonomous search function in Idle, Cell_PCH and URA_PCH states. The UE shall disable the autonomous
search function for CSG cells if the UEs CSG whitelist is empty. If "Dedicated CSG frequency(ies) " IE is present, the
UE may use the autonomous search function only on these dedicated frequencies and on the other frequencies listed in
the system information.
When the UE has no or an empty CSG whitelist, the UE may ignore cells with PSC in the stored range"CSG PSC Split
Information" [4] reserved for CSG cells for intra-frequency and inter-frequency measurements and cell re-selections.

If the UE detects a suitable CSG cell on a different frequency it shall reselect this cell irrespective of the cell reselection
rules applicable for the cell the UE is currently camped on, if the detected suitable CSG cell is the strongest cell on that
frequency. If suitable CSG cells are detected on different frequencies and these are the strongest cells on their
frequencies, then the UE shall reselect to any one of them.
If the UE detects one or more suitable CSG cell on another RAT, the UE shall reselect to one of them according to [18].
[TS 25.133, clause TBD]
TBD
[TS 36.304, clause 5.2.4.8.1]
Release 9
3GPP
222
3GPP TS 36.523-1 V9.3.0 (2010-12)
If the UE detects a suitable CSG cell on the same frequency, it shall reselect to this cell as per normal reselection rules
(5.2.4.6.).
[TS 36.304, clause 5.2.4.6]
s
n

R
s
=Q
meas
,
s
+Q
Hyst

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
s,n
, if Qoffset
s,n
is valid,
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

meas,n
and Q
meas,s
RAT
;
[TS 36.304, clause 5.2.4.8.2]
While camped on a suitable CSG cell, the UE shall apply the normal cell reselection rules as defined in subclause 5.2.4.
[TS 36.304, clause 5.2.4.1]
(re)selection.

While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest
priority frequency (i.e. higher than the eight network configured values), irrespective of any other priority value
allocated to this frequency.
[TS 36.133, clause TDB]
TBD
System Simulator:
Release 9
3GPP
223
3GPP TS 36.523-1 V9.3.0 (2010-12)
- Cell 1, Cell 5 and Cell 7 are not CSG cells.
- Cell 2 is CSG cell.
- Cell 5 and Cell 7 have different Routing Area.
UE:
Preamble:
Tables 6.3.3.3.2-1 and 6.3.3.3.2-2 illustrates the downlink power levels and other changing parameters to be applied for
the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows
marked "T1", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values shall be
Table 6.3.3.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell
T0
Cell-specific RS
EPRE
dBm/15kHz Off Off
TS36.508 Table 6.2.2.1-1.
T1
Cell-specific RS
EPRE
dBm/15kHz -91 -85

Srxlev* dB 15 21 Srxlev =Cell-specific RS EPRE -
qRxLevMinEUTRA

T2
Cell-specific RS
EPRE
dBm/15kHz Off Off
TS 36.508 Table 6.2.2.1-1.

Srxlev* dB Off Off S
>Thresh
Cell7,high

T3
Cell-specific RS
EPRE
dBm/15kHz -85 Off

T4
Cell-specific RS
EPRE
dBm/15kHz -91 -85

qRxLevMinEUTRA


Release 9
3GPP
224
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.3.3.2-2: Time instances of cell power level and parameter changes for UTRA cell
T0
CPICH_Ec dBm/3.84 MHz -60 Off
P-CCPCH dBm/1.28 MHz -62 Off
Qrxlevmin (FDD) dBm -79 -79 Default value
Qrxlevmin(TDD) dBm -81 -81 Default value
Srxlev* dB 19 Off
T1
Srxlev* dB 19 Off
T2
CPICH_Ec dBm/3.84 MHz Off -60
P-CCPCH dBm/1.28 MHz Off -62
Srxlev* dB Off 19
T3
CPICH_Ec dBm/3.84 MHz -60 -70
P-CCPCH dBm/1.28 MHz -62 -72
Srxlev* dB 19 9
T4
Srxlev* dB 19 Off
Note : Srxlev is calculated in the UE

Release 9
3GPP
225
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
2-
13
described in TS 34.108 subclause 7.2.2.3.3
are performed on Cell 5.
- - - -
according to the row "T1" in table 6.3.3.3.2-1.
- - - -
15 The UE is made to perform manual CSG ID
selection and select Cell 2.
- - - -
Cell 2?
- - 1 -
17 The SS changes Cell 1, Cell 2, Cell 5 and Cell
7 levels according to row "T2" in table
6.3.3.3.2-1 and table 6.3.3.3.2-2.
- - - -
18-
29
Steps 1 to 12 of the Routing Area Update
procedure described in TS 36.508 subclause
6.4.2.8 are performed on Cell 7.
NOTE: The UE performs RAU and the RRC
- - - -
1 and table 6.3.3.3.2-2.
- - - -
31-
43
NOTE: The UE performs RAU and the RRC
- - - -
according to row "T4" in table 6.3.3.3.2-1.
- - - -
Cell 2 within [FFS] mins?
- - 2 -

Table 6.3.3.3.3-1: Conditions for specific message contents
in Table 6.3.3.3.3-2 and Table 6.3.3.3.3-5

Table 6.3.3.3.3-2: SystemInformationBlockType1 for Cell 1 and Cell 2 (preamble and all steps, Table
6.3.3.3.2-3)
csg-Indication TRUE Cell 2
csg-Identity 1 Cell 2
}

Release 9
3GPP
226
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.3.3.3-3: SystemInformationBlockType4 for Cell 2 (preamble and all steps, Table 6.3.3.3.2-3)
csg-PhysCellIdRange
start 2
range n4
}

Table 6.3.3.3.3-4: System Information Block type 19 for Cell 5 and Cell 7 (Pre-test conditions and all
steps, Table 6.3.3.3.2-3
utra-PriorityInfoList SEQUENCE {
utra-ServingCell SEQUENCE {
Priority 5 Higher priority
than E-UTRA

}
eutra-FrequencyAndPriorityInfoList SEQUENCE
(SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE

earfcn[n] Same downlink EARFCN
as used for cell 1

priority[n] 4
}
}

Table 6.3.3.3.3-5: SystemInformationBlockType6 for Cell 1 and Cell 2 (Pre-test conditions and all
UTRA-FDD
as used for cell 5

}
UTRA-TDD
as used for cell 5

}
}


6.3.4 Inter-RAT cell reselection / From UTRA CELL_PCH state to E-
UTRA RRC_IDLE CSG cell
(1)
with { UE i n UTRA Cel l PCH st at e and UE s Al l owed CSG l i st i s not empt y }
ensure that {
when { UE det ect s a sui t abl e CSG cel l t hat i s not t he st r ongest cel l on t hat f r equency }
Release 9
3GPP
227
3GPP TS 36.523-1 V9.3.0 (2010-12)
then { UE does not r esel ect t o t he CSG cel l }
}

(2)
with { UE i n UTRA Cel l PCH st at e and UE s Al l owed CSG l i st i s not empt y }
ensure that {
when { UE det ect s a sui t abl e E- UTRAN CSG cel l pr evi ousl y vi si t ed }
then { UE r esel ect s t he sui t abl e pr evi ousl y vi si t ed E- UTRAN CSG cel l i r r espect i ve of t he EUTRAN
cel l r esel ect i on pr i or i t y }
}

References: The conformance requirements covered in the present TC are specified in: TS 25.304, 5.2.6.4.1, TS 36.304
clause 5.2.4.8.1, 5.2.4.6, 5.2.4.8.2, 5.2.4.1, TS 36.133 clause TDB and TS 25.331, Annex E.
[TS 25.304, clause 5.2.6.4.1]
requirements specified in [10], when at least one CSG ID is included in the UEs CSG whitelist. The UE is required to
perform autonomous search function in Idle, Cell_PCH and URA_PCH states. The UE shall disable the autonomous
search function for CSG cells if the UEs CSG whitelist is empty. If "Dedicated CSG frequency(ies) " IE is present, the
UE may use the autonomous search function only on these dedicated frequencies and on the other frequencies listed in
the system information.
NOTE: The UE autonomous search function, per UE implementation, determines when and/or where to search for
allowed CSG cells.
When the UE has no or an empty CSG whitelist, the UE may ignore cells with PSC in the stored range"CSG PSC Split
Information" [4] reserved for CSG cells for intra-frequency and inter-frequency measurements and cell re-selections.

If the UE detects a suitable CSG cell on a different frequency it shall reselect this cell irrespective of the cell reselection
rules applicable for the cell the UE is currently camped on, if the detected suitable CSG cell is the strongest cell on that
frequency. If suitable CSG cells are detected on different frequencies and these are the strongest cells on their
frequencies, then the UE shall reselect to any one of them.
If the UE detects one or more suitable CSG cell on another RAT, the UE shall reselect to one of them according to [18].
[TS 25.133, clause TBD]
TBD
[TS 36.304, clause 5.2.4.8.1]
If the UE detects a suitable CSG cell on the same frequency, it shall reselect to this cell as per normal reselection rules
(5.2.4.6.).
[TS 36.304, clause 5.2.4.6]
s
n
Release 9
3GPP
228
3GPP TS 36.523-1 V9.3.0 (2010-12)

R
s
=Q
meas
,
s
+Q
Hyst

R
n
=Q
meas
,
n
- Qoffset

where:
Q
meas
s,n
, if Qoffset
s,n
is valid,
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

meas,n
and Q
meas,s
RAT
;
[TS 36.304, clause 5.2.4.8.2]
[TS 36.304, clause 5.2.4.1]
(re)selection.

While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest
priority frequency (i.e. higher than the eight network configured values), irrespective of any other priority value
allocated to this frequency.
[TS 36.133, clause TDB]
TBD
[TS 25.331, Annex E]
This annex contains the definitions of the bits in EUTRA Feature Group Indicators.
In this release of the specification the UE shall include the optional EUTRA Feature Group Indicators IE in the UE
multi-mode/multi RAT capability IE of the RRC message. For a specific indicator, if all functionalities for a feature
group listed in Table E.1 have been implemented and tested, the UE shall set the indicator as as "true" (as one), else (i.e.
if any one of the functionalities in a feature group listed in Table E.1 have not been implemented or tested), the UE shall
set the indicator as zero.
The UE shall set all indicators, which do not have a definition in the table E.1, as "false" (as zero).
If the optional EUTRA Feature Group Indicators IE is not included by a UE supporting a future release of the
specification, the network may assume the UE supports all features in the feature groups listed in table E.1 and
deployed in the network.
Release 9
3GPP
229
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table E.1: Defintions of feature group indicators
Index of
indicator
(bit
number)
Definition
(description of the supported functionality, if indicator set to true)
Notes
1 (leftmost
bit)
- UTRA CELL_PCH to EUTRA RRC_IDLE cell reselection
- UTRA URA_PCH to EUTRA RRC_IDLE cell reselection

2 EUTRAN measurements and reporting in connected mode
3 Undefined
4 Undefined

Clarification for mobility to EUTRAN
For mobility to E-UTRAN, it is assumed that we have 6 main "functions":
A. Support of measurements and cell reselection procedure in idle mode
B. Support of measurements and cell reselection procedure in CELL/URA_PCH
C. Support of RRC release with redirection procedure
D. Support of RRC reject with redirection procedure
E. Support of EUTRAN measurements and reporting in connected mode
F. Support of handover procedure in connected mode
Of the above, all UEs that indicate support of E-UTRA in UE capability signalling "Support of E-UTRA FDD" or
"Support of E-UTRA TDD" support A), C) and D)ll EUTRA bands they support.
For B) above, UEs indicate support by the Group 1 indicator bit (if Group 1 is set to "true", it is supported for all
EUTRA bands the UE supports).
For E) above, UEs indicate support by the Group 2 indicator bit (if Group 2 is set to "true", it is supported for all
EUTRA bands the UE supports). The compressed mode capability for supported E-UTRA frequency bands ("Need for
compressed mode") in "Measurement capability extension" is ignored by the network when Group 2 is set to "false".
For F) above, UEs indicate support by the separate UE capability signaling "Support of Inter-RAT PS Handover to E-
UTRA FDD/TDD" defined in TS 25.306 (if this bit is set to "true", PS handover is supported for all EUTRA bands the
UE supports). This bit can only be set to "true" if the UE has set the Group 2 indicator bit to "true".
System Simulator:
- Cell 5.
- Cell 1, Cell 5 are not CSG cells.
- Cell 2 is CSG cell.
UE:
- If pc_Allowed_CSG_list, the UEs Allowed CSG list is not empty and it includes the CSG Identity of Cell 2.
Preamble:
- Cell 2 is a previously visited cell.
- The UE is in state CELL_PCH (state 6-12) on Cell 5 according to [5].
Release 9
3GPP
230
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.4.3.2-1 and Table 6.3.4.3.2-2 illustrate the downlink power levels and other changing parameters to be
applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions, while
rows 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 6.3.4.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell
T0
Cell-specific RS
EPRE
dBm/15kHz Off Off
TS36.508 Table 6.2.2.1-1.
T1
Cell-specific RS
EPRE
dBm/15kHz -85 -91

qRxLevMinEUTRA

T2
Cell-specific RS
EPRE
dBm/15kHz -91 -85
qRxLevMinEUTRA

T0
Qrxlevmin (FDD) dBm -79 Default value
Qrxlevmin(TDD) dBm -81 Default value
Srxlev* dB 19
T1
Srxlev* dB 19
T2
Srxlev* dB 19

U - S Message
(Note 1)
- - - -
- - 1 F
- - - -
subclause 6.4.2.7A indicate that the UE is
camped on E-UTRAN Cell 2 within [FFS]
mins?
- - 2 -
Note 1: SS should not send any RRC message after UE has successfully proceed to CELL_PCH state in preamble.

Release 9
3GPP
231
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.4.3.3-1: Conditions for specific message contents

6.3.4.3.2-3)
Combination 4 in TS
36.508 section 4.4.3.1
SIB2, SIB3 and
SIB6 are
transmitted
Cell 1
Combination 11 in TS
36.508 section 4.4.3.1
SIB2, SIB3, SIB 4
and SIB6 are
transmitted
Cell 2
csg-Identity 1 Cell 2
}

csg-PhysCellIdRange
start 2
range n4
}

Table 6.3.4.3.3-4: System Information Block type 19 for Cell 5 (Pre-test conditions and all steps, Table
6.3.4.3.2-3
Priority 5 Higher priority
than E-UTRA

}
1 entry the first entry only
priority[1] 4
}
}

Release 9
3GPP
232
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.4.3.3-5: RRC CONNECTION SETUP COMPLETE for Cell 5 (preamble, step 4 of TS 34.108
Table 7.4.2.2.1.3)
Derivation Path: 34.108 default RRC CONNECTION SETUP COMPLETE in section clause 9.1.1 for UTRA FDD or
9.1.2 for UTRA TDDincluding IE "eutraFeatureGroupIndicators".
UE radio access capability
UE multi-mode/multi-RAT capability
EUTRA Feature Group Indicators '1000'B Support of
- UTRA CELL_PCH to
EUTRA RRC_IDLE
cell reselection;
- UTRA URA_PCH to
EUTRA RRC_IDLE
cell reselection

Table 6.3.4.3.3-6: SystemInformationBlockType6 for Cell 1 and Cell 2 (Pre-test conditions and all
1 entry the first entry only UTRA-FDD
}
1 entry the first entry only UTRA-TDD
}
}


6.3.5 Void
6.3.6 Ignoring CSG cells in cell selection/reselection when allowed CSG
list is empty or not supported
(1)
with { UE i n E- UTRA RRC_I DLE st at e and UE does not suppor t Al l owed CSG l i st or UE s Al l owed CSG l i st
i s empt y }
ensure that {
when { Sr vl ev < 0 f or non- CSG cel l and Sr xl ev > 0 f or i nt r a- f r equency CSG cel l and Sr xl ev > 0 f or
i nt er - f r equency CSG cel l }
then { UE does not sel ect t he i nt r a- f r eq CSG cel l nor t he i nt er - f r equency CSG cel l }
}

(2)
i s empt y }
ensure that {
when { Sr vl ev > 0 f or non- CSG cel l and Sr xl ev of non- CSG cel l < Sr xl ev of i nt r a- f r equency CSG cel l
and Sr xl ev of non- CSG cel l < Sr xl ev of i nt er - f r equency CSG cel l }
then { UE sel ect s t he non- CSG cel l }
}

Release 9
3GPP
233
3GPP TS 36.523-1 V9.3.0 (2010-12)
(3)
i s empt y }
ensure that {
when { UE det ect s an i nt r a- f r equency CSG cel l wi t h R
n
hi gher t han R
s
}
then { UE does not r esel ect t o t he i nt r a- f r equency CSG cel l }
}

(4)
i s empt y }
ensure that {
when { UE det ect s an i nt er - f r equency CSG cel l wi t h R
n
hi gher t han R
s
}
then { UE does not r esel ect t o t he i nt er - f r equency CSG cel l }
}

5.2.4.6 and TS 36.331, clause B.2.
[TS 36.304, clause 5.2.3.2]

Srxlev >0

Where:

Srxlev =Q
rxlevmeas
(Q
rxlevmin
+Q
rxlevminoffset
) - Pcompensation

Where:
Q
rxlevmeas
Q
rxlevmin
Q
rxlevminoffset
rxlevmin
Pcompensation max(P
EMAX
P
UMAX
, 0) (dB)
P
EMAX
EMAX
in [TS 36.101]
P
UMAX

[TS 36.304, clause 5.2.4.6]

R
s
=Q
meas
,
s
+Qhyst
s

R
n
=Q
meas
,
n
- Qoffset

Release 9
3GPP
234
3GPP TS 36.523-1 V9.3.0 (2010-12)
where:
Q
meas
s,n
plus Qoffset
frequency
, if
Qoffset
s,n
frequency
.

The UE shall perform ranking of all cells that fulfill the cell selection criterion S, which is defined in 5.2.3.2
meas,n
and Q
meas,s
RAT
;
[TS 36.331, clause B.2]
In this release of the protocol, it is mandatory for the UE to support a minimum set of CSG functionality consisting of:
- Identifying whether a cell is CSG or not;
- Ignoring CSG cells in cell selection/reselection.
System Simulator:
- Cell 1 is not a CSG cell.
- Cell 2 and Cell 3 are CSG cells.
UE:
Preamble:
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows marked "T1",
"T2" and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in
the texts in this clause.
Release 9
3GPP
235
3GPP TS 36.523-1 V9.3.0 (2010-12)
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-115 -97 -85 Srxlev
Cell 1
<0 and Srxlev
Cell 3
>
Srxlev
Cell 2
>0.
Qrxlevmin dBm -106 -106 -106
Qhyst dB 0 0 0
Srxlev* dB -9 9 21 Cell 3 is the strongest cell
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-97 -73 -85 Srxlev
Cell 2
>Srxlev
Cell 3
>Srxlev
Cell 1

>0.
Srxlev* dB 9 33 21 Cell 2 is the strongest cell
T2 Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79 -115 The power level values are assigned
to satisfy R
Cell 1
<R
Cell 2
.
T3 Cell-specific RS
EPRE
dBm/15k
Hz
-85 -115 -73 The power level values are assigned
to satisfy R
Cell 1
<R
Cell 3
.

U - S Message
RRCConnectionRequest on Cell 2 or Cell 3
within 60 seconds?
1.
- - - -
5-
19
- - - -
1.
- - - -
RRCConnectionRequest on Cell 2 within 60
seconds?
1.
- - - -
RRCConnectionReques on Cell 3 within 60
seconds?

Table 6.3.6.3.3-1: Conditions for tables 6.3.6.3.3-2 and 6.3.6.3.3-3

Release 9
3GPP
236
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.6.3.3-2: SystemInformationBlockType1 for Cell 1, 2 and 3 (Pre-test conditions and all steps,
Table 6.3.6.3.2-2)
csg-Indication FALSE Cell 1
TRUE Cell 2
Cell 3
csg-Identity Not present Cell 1
'000 0000 0000 0000
0000 0000 0010'B
Cell 2
'000 0000 0000 0000
0000 0000 0011'B
Cell 3
}
}
}

Table 6.3.6.3.3-3: SystemInformationBlockType3 for Cell 1, 2 and 3 (Pre-test conditions and all steps,
table 6.3.6.3.2-2
q-Hyst dB0
}
}

Table 6.3.6.3.3-4: SystemInformationBlockType4 for Cell 2 and 3 (Pre-test conditions and all steps,
table 6.3.6.3.2-2
Start 2 Cell 2
3 Cell 3
Range Not present The UE shall
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.

}
}

6.3.7 Inter-RAT Cell reselection from E-UTRA idle non-CSG cell to a
UTRA CSG cell
(1)
with { UE i n E- UTRA RRC_I DLE st at e and UE s Al l owed CSG l i st i s not empt y }
ensure that {
when { UE det ect s a sui t abl e UTRA CSG cel l pr evi ousl y vi si t ed }
Release 9
3GPP
237
3GPP TS 36.523-1 V9.3.0 (2010-12)
then { UE sel ect s t he sui t abl e UTRA CSG cel l i r r espect i ve of i t s l ower pr i or i t y t han EUTRA
cel l s}
}

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.8, 4.3,
TS 25.304, clause 5.6.1, 5.2.3.1.2 and TS 25.367, clause 6.1, 7.2.3.
[TS 36.304, clause 5.2.4.8]
In addition to normal cell reselection, the UE shall use an autonomous search function to detect allowed CSG cells on
non-serving frequencies, including inter-RAT frequencies, when at least one CSG ID is included in the UEs CSG
whitelist. The UE may also use autonomous search on the serving frequency. The UE shall disable the autonomous
search function for CSG cells if the UEs CSG whitelist is empty.
If the UE detects one or more suitable CSG cells on another RAT, the UE shall reselect to one of them, if allowed
according to [19].
[TS 36.304, clause 4.3]
suitable cell:
[TS 25.304, clause 5.6.1]
report available CSG ID(s) belonging to the registered PLMN together with their HNB name (if broadcast) to the
NAS. The search for available CSG IDs may be stopped on request of the NAS.
[TS 25.304, clause 5.2.3.1.2]
Release 9
3GPP
238
3GPP TS 36.523-1 V9.3.0 (2010-12)

Where:

Squal =Q
qualmeas
(Qqualmin +QqualminOffset)
Srxlev =Q
rxlevmeas
(Qrxlevmin +QrxlevminOffset) Pcompensation

Where:
the signalled values QqualminOffset and QrxlevminOffset are only applied when a cell is evaluated for cell selection as
a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]. During this periodic
search for higher priority PLMN the UE may check the S criteria of a cell using parameter values stored from a
different cell of this higher priority PLMN.
Q
qualmeas
c
/N
0

for FDD cells.
Q
rxlevmeas
QqualminOffset Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of
a periodic search for a higher priority PLMN while camped normally in a VPLMN [5]
QrxlevminOffset Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of

[TS 25.367, clause 6.1]
During manual CSG ID selection a UE is allowed to perform Location Registration procedure on a CSG cell whose
CSD ID is not in the CSG whitelist.
Based on the outcome of a Location Registration procedure initiated on a CSG cell, the UEs CSG whitelist is updated.
[TS 25.367, clause 7.2.3]
Inter-RAT reselection to an allowed CSG cell is supported when the UE is camped on another RAT. The UE
requirements are defined in the specifications of the concerned RAT.
System Simulator:
- Cell 1 and Cell 2 are E-UTRAN cells
- Cell 5 and Cell 7 are UTRAN cells
- Cell 5 is a UTRA CSG cell
Release 9
3GPP
239
3GPP TS 36.523-1 V9.3.0 (2010-12)
UE:
Preamble:
- UE is in state Registered, Idle Mode (state 2) according to [18] in Cell 1.
Tables 6.3.7.3.2-1 & 6.3.7.3.2-2 illustrate the downlink power levels and other changing parameters to be applied for
marked "T1","T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values shall be
Table 6.3.7.3.2-1: Time instances of cell power level and parameter changes for E-UTRA Cell 1 and
Cell 2
T0
Cell-specific RS
EPRE
dBm/15kHz -85 OFF

Qrxlevmin dBm -106 -106 Default value
Qrxlevminoffset dB 0 0 Default value
Qhyst dB 0 0 Default value
Srxlev* dB 21 N/A Cell 1 is the strongest cell
T1
Cell-specific RS
EPRE
dBm/15kHz -85 OFF

Srxlev* dB 21 N/A
T2
Cell-specific RS
EPRE
dBm/15kHz OFF -85

Srxlev* dB N/A 21
T3
Cell-specific RS
EPRE
dBm/15kHz -85 -91

Srxlev* dB 21 15
T4
Cell-specific RS
EPRE
dBm/15kHz -85 OFF

Srxlev* dB 21 N/A

Table 6.3.7.3.2-2: Time instances of cell power level and parameter changes for UTRA Cell 5 and Cell
7
T0
CPICH_Ec dBm/3.84 MHz OFF OFF Camping on Cell 1 is guaranteed
PCCPCH RSCP dBm/1.28 MHz OFF OFF Camping on Cell 1 is guaranteed
Qrxlevmin (TDD) dBm -81 -81 Default value
Srxlev* dB N/A N/A
T1 CPICH_Ec dBm/3.84 MHz -60 -64 Srxlev
Cell 5
>0, for FDD
PCCPCH RSCP dBm/1.28 MHz -62 -66 Srxlev
Cell 5
>0, for TDD
Srxlev* dB 19 15 Cell 5 becomes the suitable cell
T2 CPICH_Ec dBm/3.84 MHz OFF OFF
PCCPCH RSCP dBm/1.28 MHz OFF OFF
Srxlev* dB N/A N/A
T3 CPICH_Ec dBm/3.84 MHz OFF -64
PCCPCH RSCP dBm/1.28 MHz OFF -66
Srxlev* dB N/A 15
Cell 5
>0,for FDD
Cell 5
>0, for TDD

Release 9
3GPP
240
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
1 The SS changes Cell 5 and Cell7 levels
- - - -
2 UE performs manual CSG ID selection. CSG
Identity ('000 0000 0000 0000 0000 0000
0010'B) is selected manually and added in
UEs Allowed CSG list.
- - - -
3-
10
Step 1 to 10 of the generic test procedure
performed on UTRA CSG Cell 5.
- - - -
11 The SS changes Cell 1, Cell 2, Cell 5 and Cell
7 levels according to the row "T2" in table
6.3.7.3.2-1 and table 6.3.7.3.2-2.
- - - -
12-
19
Step 1 to 8 of the procedure described in TS
36.508 subclause 6.4.2.7A is performed on
Cell 2.
- - - -
levels according to the row "T3" in table
6.3.7.3.2-1 and table 6.3.7.3.2-2.
- - - -
21-
26
Step 1 to 6 of the procedure described in TS
36.508 subclause 6.4.2.7 is performed on Cell
1.
- - - -
according to the row "T4" in table 6.3.7.3.2-1
and table 6.3.7.3.2-2.
- - - -
indicate that the UE is camped on UTRAN
CSG Cell 5 in [FFS] mins?
- - 1 -

Table 6.3.7.3.3-1: Conditions for Tables 6.3.7.3.3-2, 6.3.7.3.3-3, 6.3.7.3.3-4, 6.3.7.3.3-5 and 6.3.7.3.3-6

6.3.7.3.2-3)
schedulingInfo ::=SEQUENCE (SIZE (1..maxSI-
Combination 4 in TS
36.508 section 4.4.3.1.1
Only SIB2, SIB3
and SIB6 are
transmitted

}

Release 9
3GPP
241
3GPP TS 36.523-1 V9.3.0 (2010-12)
6.3.7.3.2-3)
cellReselectionPriority[1] 3 Lower priority than
E-UTRA

}
E-UTRA

}
}

Table 6.3.7.3.3-4: Master Information Block for Cell 5 (preamble and all steps, Table 6.3.7.3.2-3)
Derivation Path: 34.108 clause 6.1.0a.3
- CSG Indicator TRUE

Table 6.3.7.3.3-5: System Information Block type 1 for Cell 5 (preamble and all steps, Table 6.3.7.3.2-
3)
Derivation Path: 34.108 clause 6.1.0b
- CSG Identity '000 0000 0000 0000
0000 0000 0010'B

- CSG PSC Split Information
- Start PSC 104
- Number of PSCs 5
- PSC Range 2 Offset Not present

Table 6.3.7.3.3-6: System Information Block type 19 for Cell 5 and Cell 7 (preamble and all steps,
Table 6.3.7.3.2-3)
Priority 3 Lower priority than
E-UTRA
Cell 5
Cell 7
}
priority[1] 4 Cell 5
Cell 7
}
}

6.3.8 Inter-RAT CSG Cell Reselection from E-UTRA CSG cell to UTRA
CSG cell
(1)
with { UE i n E- UTRA RRC_I DLE st at e and UE s Al l owed CSG l i st i s not empt y }
Release 9
3GPP
242
3GPP TS 36.523-1 V9.3.0 (2010-12)
ensure that {
when { UE det ect s a sui t abl e UTRA CSG cel l pr evi ousl y vi si t ed }
then { UE sel ect s t he sui t abl e UTRA CSG cel l i r r espect i ve of i t s l ower pr i or i t y t han EUTRA
cel l s }
}

TS 25.304, clause 4.3, 5.6.1, 5.2.3.1.2 and TS 25.367, clause 6.1, 7.4.
[TS 36.304, clause 5.2.4.8]
To search for suitable CSG cells on non-serving frequencies, the UE may use an autonomous search function. If the UE
detects a CSG cell on a non-serving frequency, the UE may reselect to the detected CSG cell if it is the highest ranked
cell on its frequency.
If the UE detects one or more suitable CSG cells on another RAT, the UE may reselect to one of them if allowed
according to [19].
[TS 36.304, clause 4.3]
suitable cell:
[TS 25.304, clause 4.3]
suitable cell:
- The cell shall be part of either:
according to the latest information provided by the NAS.
Release 9
3GPP
243
3GPP TS 36.523-1 V9.3.0 (2010-12)
- The cell is not barred, see subclause 5.3.1.1;
- The cell is part of at least one LA that is not part of the list of "forbidden LAs for roaming" [9], which belongs to
a PLMN that fulfills the first bullet above;
- The cell selection criteria are fulfilled, see subclause 5.2.3.1.2.
- For a CSG cell the CSG ID is part of the Allowed CSG list of the UE.
If the IE Multiple PLMN List [4] is broadcast in the cell, the cell is considered to be part of all LAs with LAIs
constructed from the PLMN identities in the Multiple PLMN List and the LAC broadcast in the cell.
[TS 25.304, clause 5.6.1]
[TS 25.304, clause 5.2.3.1.2]

Where:

Squal =Q
qualmeas
Srxlev =Q
rxlevmeas

Where:
Release 9
3GPP
244
3GPP TS 36.523-1 V9.3.0 (2010-12)
Q
qualmeas
c
/N
0

for FDD cells.
Q
rxlevmeas

[TS 25.367, clause 6.1]
[TS 25.367, clause 7.4]
For reselection between allowed CSG cells, the UE follows the same cell ranking rules as those defined for the UTRA
case in [2].
System Simulator:
- Cell 1, Cell 2 and Cell 5
- Cell 1 is an E-UTRA CSG cell
UE:
- If pc_Allowed_CSG_list, the UEs Allowed CSG list is not empty and it includes a CSG Identity ('000 0000
0000 0000 0000 0000 0010'B).
Preamble:
Tables 6.3.8.3.2-1 & 6.3.8.3.2-2 illustrate the downlink power levels and other changing parameters to be applied for
marked "T1", "T2" and "T3" are to be applied subsequently. The exact instants on which these values shall be applied
are described in the text in this clause.
Release 9
3GPP
245
3GPP TS 36.523-1 V9.3.0 (2010-12)
Table 6.3.8.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cells
T0
Cell-specific RS EPRE dBm/15kHz -85 -91
Srxlev* dB 21 15 Cell 1 is the strongest cell and
camping on Cell 1 is guaranteed
T1
Srxlev* dB 21 15
T2
Srxlev* dB 21 15
T3
Srxlev* dB 15 21

T0
CPICH_Ec dBm/3.84 MHz OFF Camping on Cell 1 is guaranteed
PCCPCH RSCP dBm/1.28 MHz OFF Camping on Cell 1 is guaranteed
Qrxlevmin (FDD) dBm -79
Qrxlevmin (TDD) dBm -81 Default value
Srxlev* dB N/A
Cell 5
>0, for FDD
PCCPCH RSCP dBm/1.28 MHz -62 Srxlev
Cell 5
>0, for TDD
Srxlev* dB 19
T2
CPICH_Ec dBm/3.84 MHz OFF
PCCPCH RSCP dBm/1.28 MHz OFF
Srxlev* dB N/A
Cell 5
>0, for FDD
Cell 5
>0, for TDD
Srxlev* dB 19

Release 9
3GPP
246
3GPP TS 36.523-1 V9.3.0 (2010-12)
U - S Message
6.3.8.3.2-1 and table 6.3.8.3.2-2.
- - - -
2 UE performs manual CSG ID selection and
CSG Identity ('000 0000 0000 0000 0000 0000
- - - -
3-
12
Step 1 to 10 of the generic test procedure
described in TS 36.508 subclause 6.4.2.8 is
performed on UTRA CSG Cell 5.
- - - -
and table 6.3.8.3.2-2.
- - - -
14-
21
Step 1 to 8 of the generic procedure described
in TS 36.508 subclause 6.4.2.7A are
- - - -
and table 6.3.8.3.2-2.
- - - -
5 in [FFS] mins?
- - 1 -

Table 6.3.8.3.3-1: Conditions for Tables 6.3.8.3.3-2, 6.3.8.3.3-3, 6.3.8.3.3-4, 6.3.8.3.3-5, 6.3.8.3.3-6 and
6.3.8.3.3-7

6.3.8.3.2-3)
csg-Identity '000 0000 0000 0000
0000 0000 0010'B
Cell 1
}
q-RxLevMin -53 (-106 dBm) Cell 1
Cell 2
}
36.508 section 4.4.3.1
SIB2, SIB3, SIB4
and SIB6 are
transmitted
Cell 1
Combination 4 in TS
36.508 section 4.4.3.1
Only SIB2, SIB3
and SIB6 are
transmitted
Cell 2
}

Release 9
3GPP
247
3GPP TS 36.523-1 V9.3.0 (2010-12)
Start 2
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.

}
}

6.3.8.3.2-3)
E-UTRA

}
E-UTRA

}
}


Table 6.3.8.3.3-5: Master Information Block for Cell 5 (preamble and all steps, Table 6.3.8.3.2-3)

3)
- CSG Identity '000 0000 0000 0000
0000 0000 0100'B

- Start PSC 104
- Number of PSCs 5

Release 9
3GPP
248
3GPP TS 36.523-1 V9.3.0 (2010-12)
3)
E-UTRA

}
priority[1] 4
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 249
249
7 Layer 2
For all layer 2 test cases, default values for periodicBSR-Timer, retxBSR-Timer and phr-Config shall be taken
according to the condition no_periodic_BSR_or_PHR as specified in TS 36.508 subclause 4.8.2.1.5 unless test case
specific values are given in the test case.
In all MAC and RLC handover test cases during the execution of generic test procedure defined in [18] section 4.5.3A
following specific message content should be used for RRC Connection Reconfiguration message transmitted at step 8
of the table 4.5.3.3-1 [18]
Table 7-1: PDCP-Config-DRB-AM
PDCP-Config-DRB-AM ::=SEQUENCE {

rlc-AM SEQUENCE {
statusReportRequired FALSE
}
}

7.1 MAC
7.1.1 Mapping between logical channels and transport channels
7.1.1.1 CCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID
(1)
with { UE in E-UTRA RRC_IDLE state and after transmitting a RRCConnectionRequest message }
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its T-CRNTI but including a reserved value
for LCID }
then { UE discards the MAC PDU }
}

(2)
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its T-CRNTI with value 00000B as LCID }
then { UE forwards to upper layers the disassembled and demultiplexed SDU on logical channel
CCCH }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.11, 6.2.1 ,
5.3.3 and 6.1.2.
[TS 36.321, clause 5.11]
When a MAC entity receives a MAC PDU for the UEs C-RNTI or Semi-Persistent Scheduling C-RNTI, containing
reserved or invalid values, the MAC entity shall:
- discard the received PDU.
[TS 36.321, clause 6.2.1]
The MAC header is of variable size and consists of the following fields:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 250
250
- LCID: The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or
the type of the corresponding MAC control element or padding as described in tables 6.2.1-1 and 6.2.1-2 for the
DL and UL-SCH respectively. There is one LCID field for each MAC SDU, MAC control element or padding
included in the MAC PDU. The LCID field size is 5 bits;
...
Table 6.2.1-1: Values of LCID for DL-SCH
Index LCID values
00000 CCCH
00001-01010 Identity of the logical channel
01011-11011 Reserved
11100 UE Contention Resolution Identity
11101 Timing Advance
11110 DRX Command
11111 Padding

[TS 36.321, clause 5.3.3]
The UE shall disassemble and demultiplex a MAC PDU as defined in subclause 6.1.2.
[TS 36.321, clause 6.1.2]
A MAC PDU consists of a MAC header, zero or more MAC Service Data Units (MAC SDU), zero, or more MAC
control elements, and optionally padding; as described in Figure 6.1.2-3.
Both the MAC header and the MAC SDUs are of variable sizes.
A MAC PDU header consists of one or more MAC PDU sub-headers; each subheader corresponds to either a MAC
SDU, a MAC control element or padding.
A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last subheader in the MAC PDU
and for fixed sized MAC control elements. The last subheader in the MAC PDU and sub-headers for fixed sized MAC
control elements consist solely of the four header fields R/R/E/LCID. A MAC PDU subheader corresponding to
padding consists of the four header fields R/R/E/LCID.
LCID R
F L
R/R/E/LCID/F/Lsub-headerwith
7-bitsLfield
15-bitsLfield
R E LCID R
F L
R E
L
Oct1
Oct2
Oct1
Oct2
Oct3

Figure 6.1.2-1: R/R/E/LCID/F/L MAC subheader

LCID R
R/R/E/LCIDsub-header
R E Oct1

Figure 6.1.2-2: R/R/E/LCID MAC subheader

MAC PDU sub-headers have the same order as the corresponding MAC SDUs, MAC control elements and padding.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 251
251
MAC control elements, are always placed before any MAC SDU.
Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may
have any value and the UE shall ignore it.
When single-byte or two-byte padding is required, one or two MAC PDU sub-headers corresponding to padding are
placed at the beginning of the MAC PDU before any other MAC PDU subheader.
A maximum of one MAC PDU can be transmitted per TB per UE.
MACControl
element1
...
R/R/E/LCID
sub-header
MACheader
MACpayload
R/R/E/LCID
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
...
R/R/E/LCID/F/L
sub-header
R/R/E/LCIDpadding
sub-header
MACControl
element2
MACSDU MACSDU
Padding
(opt)

Figure 6.1.2-3: Example of MAC PDU consisting of MAC header, MAC control elements, MAC SDUs
and padding

System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 252
252
U - S Message
EXCEPTION: Steps 1 to 4 shall be repeated
for decreasing reserved LCID values from
01011 to 11011.
- - - -
a matched identity.
<-- - - -
2 The UE transmits an RRCConnectionRequest
message.
--> - - -
3 The SS Transmits a valid MAC PDU
containing RRCConnectionSetup, and
Contention Resolution Identity MAC Control
Element except for LCID in MAC Header set to
reserved value 11011 or lower (depending on
iteration number).
<-- MAC PDU - -
EXCEPTION: In parallel with step 4, UE may
execute parallel behaviour defined in table
7.1.1.1.3.2-2
- - - -
4 Check: For 5 seconds after Step3, does the
UE transmit RRCConnectionSetupComplete
message?
--> RRCConnectionSetupComplete 1 F
a matched identity.
<-- - - -
message.
--> - - -
7 The SS transmits a valid MAC PDU containing
RRCConnectionSetup, and Contention
Resolution Identity MAC Control Element and
LCID in MAC Header set correctly to CCCH
00000
<-- MAC PDU - -
8 Check: does the UE transmit an
including SERVICE REQUEST message?
9-
12
Steps 6 to 9 of the generic radio bearer
establishment procedure (TS 36.508 4.5.3.3-1)
are executed to successfully complete the
service request procedure.
- - - -

U - S Message
message.
--> - - -

None.
7.1.1.2 DTCH or DCCH mapped to UL SCH/ DL-SCH / Reserved Logical Channel ID
(1)
with { UE in E-UTRA RRC_Connected state with DRB [Logical channel ID 3] established }
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its CRNTI but including a reserved value
for LCID }
then { UE shall not forward the disassembled and demultiplexed SDU on the configured logical
channels }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 253
253
(2)
ensure that {
when { UE receives a MAC PDU on DL SCH and addressed to its CRNTI with value 00011B as LCID }
then { UE shall forward the disassembled and demultiplexed SDU on the corresponding logical
channel }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 6.2.1, 5.3.3
and 6.1.2.
[TS 36.321, clause 6.2.1]
included in the MAC PDU. The LCID field size is 5 bits;
...
Index LCID values
00000 CCCH
11101 Timing Advance
11110 DRX Command
11111 Padding

[TS 36.321, clause 5.3.3]
The UE shall disassemble and demultiplex a MAC PDU as defined in subclause 6.1.2.
[TS 36.321, clause 6.1.2]
A MAC PDU header consists of one or more MAC PDU sub-headers; each subheader corresponds to either a MAC
A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last subheader in the MAC PDU
and for fixed sized MAC control elements. The last subheader in the MAC PDU and sub-headers for fixed sized MAC
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 254
254
LCID R
F L
7-bitsLfield
15-bitsLfield
R E LCID R
F L
R E
L
Oct1
Oct2
Oct1
Oct2
Oct3

Figure 6.1.2-1: R/R/E/LCID/F/L MAC subheader

LCID R
R E Oct1

Figure 6.1.2-2: R/R/E/LCID MAC subheader

have any value and the UE shall ignore it.
MACControl
element1
...
R/R/E/LCID
sub-header
MACheader
MACpayload
R/R/E/LCID
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
...
R/R/E/LCID/F/L
sub-header
R/R/E/LCIDpadding
sub-header
MACControl
element2
MACSDU MACSDU
Padding
(opt)

and padding

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 255
255
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18].
NOTE: In the following, the established DRB is assumed to have Logical channel ID 3
U - S Message
EXCEPTION: the steps 1 and 2 are repeated
for decreasing reserved LCID values from
01011 to 11011
- - - -
a RLC PDU except for LCID in MAC Header
set to reserved value 11011.
<-- MAC PDU - -
2 Check: does the UE transmit a Scheduling
Request on PUCCH within 5 seconds after
step 1?
--> (SR) 1 F
containing RLC PDU with LCID in MAC
Header set correctly to DRB 00011.
<-- MAC PDU - -
4 Check: does the UE transmits a Scheduling
Request on PUCCH?
--> (SR) 2 P
5 The SS sends an UL grant suitable for the loop
back PDU to transmitted
<-- (UL Grant) - -
6 Check: does the UE transmit a MAC PDU with
LCID set to DRB 00011?
--> MAC PDU 2 P

None.
7.1.2 RACH
7.1.2.1 Correct selection of RACH parameters / Random access preamble and
PRACH resource explicitly signalled to the UE by RRC / Non-contention
based random access procedure
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { SS sends an RRCConnectionReconfiguration message including RACH-ConfigDedicated information
element }
then { UE sends a prach preamble given in the RACH-ConfigDedicated on the target cell }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 256
256
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.2 and
5.1.4.
[TS 36.321, clause 5.1.2]
The Random Access Resource selection procedure shall be performed as follows:
- If ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been
explicitly signalled and ra-PreambleIndex is not 000000:
- the Random Access Preamble and the PRACH Mask Index are those explicitly signalled.
[TS 36.321, clause 5.1.4]
Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the
UE shall monitor the PDCCH for Random Access Response(s) identified by the RA-RNTI defined below, in the RA
Response window which starts at the subframe that contains the end of the preamble transmission [7] plus three
subframes and has length ra-ResponseWindowSize subframes. The RA-RNTI associated with the PRACH in which the
Random Access Preamble is transmitted, is computed as:
RA-RNTI=1 +t_id+10*f_id
Where t_id is the index of the first subframe of the specified PRACH (0 t_id <10), and f_id is the index of the
specified PRACH within that subframe, in ascending order of frequency domain (0 f_id<6). The UE may stop
monitoring for Random Access Response(s) after successful reception of a Random Access Response containing
Random Access Preamble identifiers that matches the transmitted Random Access Preamble.
- If a downlink assignment for this TTI has been received on the PDCCH for the RA-RNTI and the received TB is
successfully decoded, the UE shall regardless of the possible occurrence of a measurement gap:
...
- if the Random Access Response contains a Random Access Preamble identifier corresponding to the
transmitted Random Access Preamble (see subclause 5.1.3), the UE shall:
- consider this Random Access Response reception successful;
- process the received Timing Advance Command (see subclause 5.2);
- indicate the preambleInitialReceivedTargetPower and the amount of power ramping applied to the latest
preamble transmission to lower layers (i.e., (PREAMBLE_TRANSMISSION_COUNTER 1) *
powerRampingStep);
- process the received UL grant value and indicate it to the lower layers;
- if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC):
- consider the Random Access procedure successfully completed.
System Simulator:
UE:
None.
Preamble:
- UE is in state Generic RB Established (state 3) according to [18] in cell 1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 257
257
columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -91
The power level values are such that
measurement results for Cell 1 (M1) and
Cell 2 (M2) satisfy exit condition for event
A3 (M2 <M1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79
Cell 2 (M2) satisfy entry condition for event
A3 (M2 >M1).

U - S Message
0A The SS transmits an
RRCConnectionReconfiguration message on
Cell 1 to setup intra frequency measurement.
- - - -
0B The UE transmits an
RRCConnectionReconfigurationComplete
message on Cell 1.
- - - -
0C The SS changes Cell 1 and Cell 2 parameters
- - - -
0D The UE transmits a MeasurementReport
message on Cell 1 to report event A3 with the
measured RSRP, RSRQ value for Cell 2.
- - - -
1 The SS transmits an
RRCConnectionReconfiguration message to
order the UE to perform intra frequency
handover to Cell 2, including explicit Random
Access Preamble.
- - - -
2 Check: Does the UE transmit Preamble on
PRACH corresponding to ra-PreambleIndex in
step 1?
--> (PRACH Preamble) 1 P
3 The SS transmits Random Access Response
on cell 2, with RAPID corresponding to ra-
PreambleIndex in step 1
<-- Random Access Response - -
4 Check: Does the UE sends on cell 2, a MAC
PDU containing
RRCConnectionReconfigurationComplete?
--> MAC PDU
(RRCConnectionReconfigurationC
omplete)
1 P
indicates that UE is in E-UTRA
RRC_CONNECTED state in cell 2?
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 258
258
Table 7.1.2.1.3.3-1: RRCConnectionReconfiguration (step 1, table 7.1.2.1.3.2-1)
Derivation Path: 36.508, Table 4.6.1-8, condition RBC-HO
RRCConnectionReconfiguration ::=SEQUENCE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInfo SEQUENCE { MobilityControlInfo-HO
targetPhysCellId PhysicalCellIdentity of
Cell 2 (see 36.508 clause
4.4.4.2)

carrierFreq Not present
rach-ConfigDedicated SEQUENCE {
ra-PreambleIndex 52 (see TS 36.211 Table
5.7.1-2)
FDD
ra-PreambleIndex 52 (see TS 36.211 Table
5.7.1-3)
TDD
ra-PRACH-MaskIndex 0 All
}
}
}
}
}
}

7.1.2.2 Correct selection of RACH parameters / Random access preamble and
PRACH resource explicitly signalled to the UE in PDCCH Order / Non-
contention based random access procedure
(1)
ensure that {
when { PDCCH control command is received providing Random Access Preamble }
then { UE sends a prach preamble given in the PDCCH Order }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state and transmitted PRACH Preamble, after reception of PDCCH
order }
ensure that {
when { UE does not receive a matching Random Accees response in ra-ResponseWindowSize (hence
considers RACH attempt as failed) and PREAMBLE_TRANSMISSION_COUNTER is less than
PREAMBLE_TRANS_MAX }
then { UE retransmists the Preamble given in the PDCCH Order }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.2 and
5.1.24.
[TS 36.321, clause 5.1.2]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 259
259
[TS 36.321, clause 5.1.4]
monitoring for Random Access Response(s) after successful reception of a Random Access Response containing the
...
powerRampingStep);
...
If no Random Access Response is received within the RA Response window, or if none of all received Random Access
Responses contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble,
the Random Access Response reception is considered not successful and the UE shall:
- increment PREAMBLE_TRANSMISSION_COUNTER by 1;
- If PREAMBLE_TRANSMISSION_COUNTER =preambleTransMax +1:
- indicate a Random Access problem to upper layers
- if in this Random Access procedure, the Random Access Preamble was selected by MAC:
- based on the backoff parameter in the UE, select a random backoff time according to a uniform
distribution between 0 and the Backoff Parameter Value;
- delay the subsequent Random Access transmission by the backoff time;
- proceed to the selection of a Random Access Resource (see subclause 5.1.2).
System Simulator:
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 260
260
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18] in cell 1
U - S Message
1 The SS transmits a PDCCH order providing
Random Access Preamble.
<-- (PDCCH Order) - -
2 Check: does the UE transmit a preamble on
PRACH using the same preamble index as
given in step 1?
PRACH after ra-ResponseWindowSize using
the same preamble index as given in step 1?
with RAPID corresponding to Preamble in step
1.
7 Check: does the test result of CALL generic
procedure indicate that UE is in E-UTRA
RRC_CONNECTED state?
- - 2 -

Table 7.1.2.2.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.2.3.2-1)
Derivation Path: 36.508 clause 4.4.3.3, Table Nr. 4.4.3.3.-1
radioResourceConfigCommon SEQUENCE {
rach-Configuration SEQUENCE {
ra-SupervisionInformation SEQUENCE {
preambleTransMax N4 PREAMBLE_TRA
NS_MAX

}
}
}
}
}

7.1.2.3 Correct selection of RACH parameters / Preamble selected by MAC itself /
Contention based random access procedure
(1)
with { UE in E-UTRA RRC_IDLE state }
ensure that {
when { SS sends a Paging message to the UE and MAC PDU Size carrying CCCH PDU is less than
messageSizeGroupA }
then { UE transmits a random access preamble using a preamble in group A of random access
preambles indicated in SIB2 }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 261
261
}

(2)
with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 }
ensure that {
when { SS does not respond before contention resolution timer expiry }
then { UE transmits a random access preamble using a preamble in the same group of random access
preambles as used for the first transmission of Msg3 }
}

(3)
with { UE in E-UTRA RRC_IDLE state and has transmitted Msg3 }
ensure that {
when { SS does not respond before contention resolution timer expiry after more than
preambleTransMax transmissions from UE }
then { UE transmits a random access preamble using a preamble in the same group of random access
preambles as used for the first transmission of Msg3 }
}

(4)
ensure that {
when { UE has data available for transmission and the MAC PDU Size carrying this data is greater
than messageSizeGroupA }
then { UE transmits a random access preamble using a preamble in group B of random access
preambles indicated in SIB2 }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.2 and
5.1.5.
[TS 36.321, clause 5.1.2]
explicitly signalled andra-PreambleIndex is not 000000:
...
- else the Random Access Preamble shall be selected by the UE as follows:
- If Msg3 has not yet been transmitted, the UE shall:
- if Random Access Preambles group B exists and if the potential message size (data available for
transmission plus MAC header and, where required, MAC control elements) is greater than
messageSizeGroupA and if the pathloss is less than P
CMAX
preambleInitialReceivedTargetPower
deltaPreambleMsg3 messagePowerOffsetGroupB, then:
- select the Random Access Preambles group B;
- else:
- select the Random Access Preambles group A.
- else, if Msg3 is being retransmitted, the UE shall, the UE shall:
- select the same group of Random Access Preambles as was used for the preamble transmission attempt
corresponding to the first transmission of Msg3.
- randomly select a Random Access Preamble within the selected group. The random function shall be such
that each of the allowed selections can be chosen with equal probability;
- set PRACH Mask Index to 0.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 262
262
- determine the next available subframe containing PRACH permitted by the restrictions given by the prach-
ConfigIndex and PRACH Mask Index (see subclause 7.3) and physical layer timing requirements [2] (a UE may
take into account the possible occurrence of measurement gaps when determining the next available PRACH
subframe);
- if the transmission mode is TDD and the PRACH Mask Index is equal to zero:
- if ra-PreambleIndex was explicitly signalled and the signalled random access preamble ID was not 000000
(i.e., not selected by MAC):
- randomly select, with equal probability, one PRACH from the PRACHs available in the determined
subframe.
- else:
subframe and the next two consecutive subframes.
- else:
- determine a PRACH within the determined subframe in accordance with the requirements of the PRACH
Mask Index.
- proceed to the transmission of the Random Access Preamble (see subclause 5.1.3).
[TS 36.321, clause 5.1.5]
Contention Resolution is based on either C-RNTI on PDCCH or UE Contention Resolution Identity on DL-SCH..
Once Msg3 is transmitted, the UE shall:
- start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ
retransmission;
- regardless of the possible occurrence of a measurement gap, monitor the PDCCH until mac-
ContentionResolutionTimer expires or is stopped;
- ...
- if mac-ContentionResolutionTimer expires:
- discard the Temporary C-RNTI;
- consider the Contention Resolution not successful.
- if the Contention Resolution is considered not successful the UE shall:
- flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer;
- indicate a Random Access problem to upper layers.
...
System Simulator:
- Cell 1.
- System information set using parameters as specified in Table 7.1.2.3.3.3-1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 263
263
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode, Test Mode Activated (State 2A) according to [18].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 264
264
U - S Message
a matched identity.
- - - -
2 Check: Does the UE transmit preamble on
PRACH using a preamble in group A defined
in SIB2 (numberOfRA-Preambles and
sizeOfRA-PreamblesGroupA)?
--> PRACH Preamble 1 P
with RAPID corresponding to the transmitted
Preamble in step 4, including T-CRNTI and not
including Backoff Indicator sub header.
message.
--> MAC PDU - -
PRACH using a preamble belonging to group
A?
8 Check: Does the UE continue to repeatedly
transmit for 2s after step 2 a preamble
belonging to group A?
Note: 2s is the value of T300.
--> PRACH Preamble 2, 3 P
9 The UE is in state Loopback Activated (state 4)
according to [18] using parameters as
specified in Table 7.1.2.3.3.3-2
- - - -
10 The SS transmits a MAC PDU containing a
PDCP SDU of size 320 bits[>208].
<-- MAC PDU - -
- Exception: steps 11 and 12 are repeated
dsr-TransMax times.
- - - -
11 UE transmits a Scheduling Request. --> Scheduling Request - -
12 The SS does not allocate UL grant for the
scheduling request in step 11.
- - - -
PRACH using a preamble in group B defined
Preamble in step 15, including T-CRNTI and
not including Backoff Indicator sub header.
17 The UE transmits a MAC PDU with C-RNTI
containing loop backed PDCP SDU
-> MAC PDU - -
18 The SS ignores the UL MAC PDU and does
not allocate UL grant for the C-RNTI in step
17.
- - - -
PRACH using a preamble belonging to group
B?
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 265
265
Preamble in step 19
21 The UE transmits a MAC PDU containing loop
backed PDCP SDU
--> MAC PDU - -
22 SS sends PDCCH transmission for UE C-RNTI - - - -
Note: Size of RRCConnectionRequest message is 45 bits, octet aligned =48 bits. With 8 bits of MAC Header the
minimum size of MAC PDU carrying RRCConnectionRequest is 56 bits.

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1
preambleInformation SEQUENCE {
numberOfRA-Preambles n64
preamblesGroupAConfig :={SEQUENCE {
sizeOfRA-PreamblesGroupA n28
messageSizeGroupA b208
messagePowerOffsetGroupB minusinfinity
}
}
}
}
ue-TimersAndConstants SEQUENCE{
t300 ms2000 T300
}
}
}
}

Table 7.1.2.3.3.3-2: RLC-Config-DRB-AM
Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
RLC-Config-DRB-AM ::=CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit ms200
}
}
}

7.1.2.4 Random access procedure / Successful
(1)
ensure that {
when { The SS pages the UE with a matching identity }
then { UE tranmits a random access preamble in the next available Random Access occasion }
}

(2)
with { UE in E-UTRA RRC_IDLE state after transmission of a PRACH preamble }
ensure that {
when { SS does not answer with a matching Random Accees Response within ra-ResponseWindowSize }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 266
266
then { UE retransmits a PRACH preamble }
}

(3)
with { SS transmits Random Access Response and UE send msg3 }
ensure that {
when { SS ignores the RRCConnectionRequest and does not send any Response }
then { UE select available PRACH resource to retransmits a PRACH preamble according to the
timing requirement }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.2, 5.1.3 &
5.1.4.
[TS 36.321, clause 5.1.2]
- else the Random Access Preamble shall be selected by the UE as follows:
- If Msg3 has not yet been transmitted, the UE shall:
- if Random Access Preambles group B exists and if the potential message size (data available for
transmission plus MAC header and, where required, MAC control elements) is greater than
messageSizeGroupA and if the pathloss is less than P
CMAX
preambleInitialReceivedTargetPower
deltaPreambleMsg3 messagePowerOffsetGroupB, then:
- select the Random Access Preambles group B;
- else:
- select the Random Access Preambles group A.
- else, if Msg3 is being retransmitted, the UE shall:
- select the same group of Random Access Preambles as was used for the preamble transmission attempt
corresponding to the first transmission of Msg3.
- randomly select a Random Access Preamble within the selected group. The random function shall be such
that each of the allowed selections can be chosen with equal probability;
- set PRACH Mask Index to 0.
- determine the next available subframe containing PRACH permitted by the restrictions given by the prach-
ConfigurationIndex and the PRACH Mask Index (see subclause 7.3) (a UE may take into account the possible
occurrence of measurement gaps when determining the next available PRACH subframe);
- if the transmission mode is TDD and the PRACH Mask Index is equal to zero:
subframe.
- else:
subframe and the next two consecutive subframes.
- else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 267
267
- determine a PRACH within the determined subframe in accordance with the requirements of the PRACH
Mask Index.
- proceed to the transmission of the Random Access Preamble (see subclause 5.1.3).
[TS 36.321, clause 5.1.3]
The random-access procedure shall be performed as follows:
- set PREAMBLE_RECEIVED_TARGET_POWER to preambleInitialReceivedTargetPower +
DELTA_PREAMBLE +(PREAMBLE_TRANSMISSION_COUNTER 1) * powerRampingStep;]
- instruct the physical layer to transmit a preamble using the selected PRACH, corresponding RA-RNTI, preamble
index and PREAMBLE_RECEIVED_TARGET_POWER.
[TS 36.321, clause 5.1.4]
subframes and has length ra-ResponseWindowSize subframes The RA-RNTI associated with the PRACH in which the
RA-RNTI=t1 +_id+10*f_id
monitoring for Random Access Response(s) after successful reception of a Random Access Response containing
- if the Random Access Response contains a Backoff Indicator sub header:
- set the backoff parameter value in the UE as indicated by the BI field of the Backoff Indicator sub header
and Table 7.2-1.
- else, set the backoff parameter value in the UE to 0 ms.
- indicate thepreambleInitialReceivedTargetPower and the amount of power ramping applied to the latest
powerRampingStep);
- else, if the Random Access Preamble was selected by UE MAC:
- set the Temporary C-RNTI to the value received in the Random Access Response message no later
than at the time of the first transmission corresponding to the UL grant provided in the Random
Access Response message;
- if this is the first successfully received Random Access Response within this Random Access
procedure:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 268
268
- if the transmission is not being made for the CCCH logical channel, indicate to the Multiplexing
and assembly entity to include a C-RNTI MAC control element in the subsequent uplink
transmission;
- obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity and store it in the
Msg3 buffer.
NOTE: When an uplink transmission is required, e.g., for contention resolution, the eNB should not provide a
grant smaller than 56 bits in the Random Access Response.
NOTE: If within a Random Access procedure, an uplink grant provided in the Random Access Response for the
same group of Random Access Preambles has a different size than the first uplink grant allocated during
that Random Access procedure, the UE behaviour is not defined.
...
TS 36.321, clause 6.1.5
A MAC PDU consists of a MAC header and one or more MAC Random Access Responses (MAC RAR) and optionally
padding as described in figure 6.1.5-4.
The MAC header is of variable size.
A MAC PDU header consists of one or more MAC PDU sub-headers; each subheader corresponding to a MAC RAR
except for the Backoff Indicator sub-header. If included, the Backoff Indicator sub-header is only included once and is
the first sub-header included within the MAC PDU header.
A MAC RAR consists of the four fields R/Timing Advance Command/UL Grant/Temporary C-RNTI (as described in
figure 6.1.5-3).
Padding may occur after the last MAC RAR. Presence and length of padding is implicit based on TB size, size of MAC
header and number of RARs.
Timing Advance Command Oct 1
Timing Advance
Command
UL Grant
UL Grant
Temporary C-RNTI
Temporary C-RNTI
UL Grant Oct 2
Oct 3
Oct 4
Oct 5
Oct 6
R

Figure 6.1.5-3: MAC RAR

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 269
269

MAC RAR 1
...
E/T/R/R/BI
subheader
MAC header
MAC payload
...
MAC RAR 2 MAC RAR n
E/T/RAPID
subheader 2
E/T/RAPID
subheader n
E/T/RAPID
subheader 1
Padding
(opt)

Figure 6.1.5-4: Example of MAC PDU consisting of a MAC header and MAC RARs

[TS 36.213, clause 6.1]
For the L1 random access procedure, UEs uplink transmission timing after a random access preamble transmission is
as follows.
a. If a PDCCH with associated RA-RNTI is detected in subframe n, and the corresponding DL-SCH
transport block contains a response to the transmitted preamble sequence, the UE shall, according to
the information in the response, transmit an UL-SCH transport block in the first subframe
1
k n + ,
6
1
k , if the UL delay field in section 6.2 is set to zero. The UE shall postpone the PUSCH
transmission to the next available UL subframe if the field is set to 1.
[TS 36.213, clause 6.2]
The higher layers indicate the 20-bit UL Grant to the physical layer, as defined in [8]. This is referred to the Random
Access Response Grant in the physical layer. The content of these 20 bits starting with the MSB and ending with the
LSB are as follows:
- Hopping flag 1 bit
- Fixed size resource block assignment 10 bits
- Truncated modulation and coding scheme 4 bits
- TPC command for scheduled PUSCH 3 bits
- UL delay 1 bit
- CQI request 1 bit

The UL delay applies for both TDD and FDD and this field can be set to 0 or 1 to indicate whether the delay of PUSCH
is introduced as shown in section 6.1.1.
System Simulator:
- Cell 1
- System information are set according to table 7.1.2.4.3.3-1
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 270
270
Preamble:
U - S Message
a matched identity.
- - - -
PRACH, in frame number X, subframe number
2, 5, 8 (FDD)/2,3,8(TDD)?
PRACH, in frame number X+1 or X+2,
subframe number 2, 5, 8 (FDD)/ 2,3,8 (TDD)?
--> PRACH Preamble 1,2 P
PRACH, in frame number X+2, X+3 or X+4,
5 The SS transmits a Random Access
Response with not-matching RA-Id, including
T-CRNTI and not including Backoff Indicator
sub header.
PRACH in frame number X+4, X+5 or X+6,
Preamble in step 6, including T-CRNTI and UL
grant and not including Backoff Indicator sub
header. The UL delay bit in the UL grant field
is set to 0
message.
--> - - -
9 The SS ignores the RRCConnectionRequest
message and does not send any response.
- - - -
10 UE waits for mac-ContentResolutionTimer
expire.
- - - -
11 Check: does the UE transmit preamble on
PRACH using a preamble in subframe number
2,5,8 for FDD and subframe number 2,3 or 8
for TDD?
not including Backoff Indicator sub header.
message.
--> - - -
including UE Contention Resolution Identity
MAC control element with matching
Contention Resolution Identity
<-- MAC PDU - -
RRCConnectionSetupComplete message.
--> - - -
16-
19
- - - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 271
271
Derivation path: 36.508 table 4.4.3.3.-1
mac-ContentionResolutionTimer Sf48 Timer for
contention
resolution is 48
subframes

ra-ResponseWindowSize sf10
}
}
prach-Configuration SEQUENCE {
prach-ConfigInfo SEQUENCE {
prach-ConfigurationIndex 10 As per table 5.7.1-
2 of 36.211, this
results in PRACH
preamble
transmission start
in any frame
numbers and sub-
frame number 2,
5, 8
FDD
4 of 36.211, this
results in PRACH
preamble
transmission with
frequency
resource index=0;
occurring in any
radio frames;
resource is
located in sub
frame number
2,3 ,8 Note 1
TDD
}
}
}
}
Note 1: 36.508, Table 4.4.3.2-3 specifies tdd-Configuration->subframeAssignment as sa1.

7.1.2.5 Random access procedure / MAC PDU containing multiple RARs
(1)
with { UE in E-UTRA RRC_IDLE state and transmitted PRACH preamble }
ensure that {

when { UE receives during TTI window [RA_WINDOW_BEGINRA_WINDOW_END] MAC PDU containing multiple
RARs but none of the subheaders contains a RAPID correseponding to the UE }
then { UE tranmits a random access preamble in the next available Random Access occasion }
}

(2)
with { UE in E-UTRA RRC_IDLE state and transmitted PRACH preamble }
ensure that {

when { UE receives during TTI window [RA_WINDOW_BEGINRA_WINDOW_END] MAC PDU containing multiple
RARs and one of the subheaders contains a RAPID correseponding to the UE }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 272
272
then { UE transmits MAC PDU containing RRCConnectionRequest }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.3 and
5.1.4.
[TS 36.321, clause 5.1.3]
The random-access procedure shall be performed as follows:
- set PREAMBLE_RECEIVED_TARGET_POWER to preambleInitialReceivedTargetPower +
DELTA_PREAMBLE +(PREAMBLE_TRANSMISSION_COUNTER 1) * powerRampingStep;]
- instruct the physical layer to transmit a preamble using the selected PRACH resource, corresponding RA-RNTI,
preamble index and PREAMBLE_RECEIVED_TARGET_POWER.
[TS 36.321, clause 5.1.4]
monitoring for Random Access Response(s) after successful reception of a Random Access Response containing the
and Table 7.2-1.
powerRampingStep);
- else, if the Random Access Preamble was selected by UE MAC:
- set the Temporary C-RNTI to the value received in the Random Access Response message no later
than at the time of the first transmission corresponding to the UL grant provided in the Random
Access Response message;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 273
273
- if this is the first successfully received Random Access Response within this Random Access
procedure:
- if the transmission is not being made for the CCCH logical channel, indicate to the Multiplexing
and assembly entity to include a C-RNTI MAC control element in the subsequent uplink
transmission;
- obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity and store it in the
Msg3 buffer.
NOTE: When an uplink transmission is required, e.g., for contention resolution, the eNB should not provide a
grant smaller than 56 bits in the Random Access Response.
NOTE: If within a Random Access procedure, an uplink grant provided in the Random Access Response for the
same group of Random Access Preambles has a different size than the first uplink grant allocated during
that Random Access procedure, the UE behaviour is not defined.
...
System Simulator:
- Cell 1
- System information are set according to table 7.1.2.4.3.3-1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 274
274
U - S Message
a matched identity.
<-- - - -
2 Check: Does the UE transmit a preamble on
PRACH?
3 The SS transmits a MAC PDU addressed to
UE RA-RNTI, containing multiple RARs but
none of the MAC sub headers contains a
matching RAPID
- EXCEPTION: In parallel with step 4, parallel
behaviour defined in table 7.1.2.5.3.2-2 is
executed
- - - -
4 Check: Does the UE re-transmit a preamble on
PRACH?
5 The SS transmits a MAC PDU addressed to
UE RA-RNTI, containing multiple RARs one
of the MAC sub headers contains a matching
RAPID
6 Check: does tCheck: Does the UE transmit a
MAC PDU containing RRCConnectionRequest
message?
--> MAC PDU
(RRCConnectionRequest)
2 P
7 The SS sends a MAC PDU containing
matching Contention Resolution Identity MAC
control element
<-- MAC Control PDU - -
7A SS transmit RRCConnectionSetup message <-- - - -
8 The UE transmit
including SERVICE REQUEST message.
--> - - -
9-
12
- - - -

U - S Message
RRCConnectionRequest message.
--> MAC PDU
1 F

None.
7.1.2.6 Maintenance of uplink time alignment
(1)
with { UE in E-UTRA RRC_IDLE state and having initiated a random access procedure }

ensure that {
when { The SS transmits a Timing Advance Command in a Random Access Response message }

then { the UE applies the received Timing Advance value in the next transmitted MAC PDU}
}

(2)
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 275
275
ensure that {
when { Timing Advanced Command MAC control element is received and UE has pending data during the
period the timeAlignmentTimer is running }
then { UE does not send any Random Access Preamble, but Scheduling Requests to request
transmission of data while timeAlignmentTimer is running }
}

(3)
ensure that {
when{ timeAlignmentTimer has expired or is not running and UL transmission is required}
then { UE triggers a RA Procedure }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.2.
[TS 36.321 clause 5.2]
The UE has a configurable timer timeAlignmentTimer which is used to control how long the UE is considered uplink
time aligned.
The UE shall:
- when a Timing Advance Command MAC control element is received:
- apply the Timing Advance Command;
- start or restart timeAlignmentTimer.
- when a Timing Advance Command is received in a Random Access Response message:
- if the Random Access Preamble was not selected by UE MAC:
- start or restart timeAlignmentTimer.
- else, if the timeAlignmentTimer is not running:
- start timeAlignmentTimer;
- when the contention resolution is considered not successful as described in subclause 5.1.5, stop
timeAlignmentTimer.
- else:
- ignore the received Timing Advance Command.
- when timeAlignmentTimer expires:
- flush all HARQ buffers;
- notify RRC to release PUCCH/SRS;
- clear any configured downlink assignments and uplink grants.
7.1.2.6.3.1 Pre-test condition
System Simulator:
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 276
276
UE:
None.
Preamble:
- The generic procedure to get UE in state Registered, Idle mode, UE Test Mode Activated (State 2a) according to
TS 36.508 clause 4.5 is executed.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 277
277
U S Message
1 SS pages the UE <-- - - -
2 SS respond to UE Random Access request
by a Random Access Response with TA field
within message set to 600 (Note 2).
<-- MAC PDU(Random Access
Response (TA=600))
- -
3 Check: Does UE send an
RRCConnectionRequest message in the first
scheduled UL transmission using the Timing
Advance value sent by the SS in step 2?
--> MAC PDU
1 P
4 The SS transmits a valid MAC PDU
containing UE Contention Resolution
Identity MAC control element with matching
Contention Resolution Identity and RA
Procedure considered a success.
<-- MAC PDU (UE Contention
Resolution Identity)
- -
5 The SS sends an RRCConnectionSetup
message.
<-- MAC PDU - -
RRCConnectionSetupComplete?
--> MAC PDU
(RRCConnectionSetupComplete)
1 P
7 The generic procedure to get UE in test state
Loopback Activated (State 4) according to
TS 36.508 clause 4.5 is executed with UL
SDU size set to 0 (no data returned in
uplink) using parameters as specified in
Table 7.1.2.6.3.3-1
- - - -
8 SS transmits Timing Advance command. SS
does not send any subsequent alignments.
<-- MAC PDU (Timing Advance
Command MAC Control Element)
- -
9 After 600ms (0.8 * timeAlignmentTimer) SS
sends a MAC PDU containing a RLC PDU
with SN=0 and poll bit set to trigger UE to
transmit a status report in uplink. SS does
not respond to any scheduling requests or
Random Access Preambles from the UE.
<-- MAC PDU - -
10 Check: For 0.2* timeAlignmentTimer does
UE transmit Scheduling Requests, but no
Random Access Preamble message?
(Note 1)
--> SR 2 P
11 Void - - - -
12 Check: Does the UE transmit a Random
Access Preamble?
--> Random Access Preamble 3 P
13 SS responds with a valid Random Access
Response
<-- MAC PDU (Random Access
Response (Temporary C-RNTI))
- -
14 Check: Does the UE transmit a MAC PDU
with C-RNTI containing RLC STATUS PDU
for the acknowledgement of the DL Data with
the Temporary C-RNTI set to the value
received in the Random Access Response
message??
--> MAC PDU(RLC STATUS PDU
(ACK_SN =1))
3 P
15 The SS Transmits a PDCCH transmission
addressed to the C-RNTI stored in the UE
and contains an UL grant for a new
transmission
<-- - - -
Note 1 A conformant UE correctly applies Timing Advance Command MAC Control and restarts
timeAlignmentTimer, causing the uplink to stay in sync for a period equal to the received Time Alignment
Value.
Note 2 T
A
value of 600 has been chosen arbitrarily in the middle of the range 0 to 1282 and corresponds to 0.3125
ms (timing advance in ms =1000 x N
TA
x
s
T where N
TA
=T
A
16 and ( ) 2048 15000 1
s
= T seconds
according to TS 36.213 and TS 36.211).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 278
278
7.1.2.6.3.3 Specific Message Contents
Table 7.1.2.6.3.3-1: SchedulingRequest-Configuration (RRCConnectionReconfiguration, step 7 table
7.1.2.6.3.2-1)
Derivation Path: 36.508 clause 4.6.3-20
SchedulingRequest-Configuration ::=CHOICE {
setup SEQUENCE {
dsr-TransMax n64 Max value allowed
}
}

7.1.2.7 MAC contention resolution / Temporary C-RNTI
(1)
ensure that {
when { SS does not send any MAC PDU including 'UE Contention Resolution Identity' MAC control
element before contention resolution timer expires }
then { UE re-transmits RRCConnectionRequest }
}

(2)
ensure that {
when { SS transmits a valid MAC PDU containing RRCConnectionSetup, but not including 'UE
Contention Resolution Identity' MAC control element }
}

(3)
ensure that {
when { SS transmits a valid MAC PDU containing RRCConnectionSetup, including 'UE Contention
Resolution Identity' MAC control element but with un-matched 'Contention Resolution Identity' }
}

(4)
ensure that {
when { SS transmits a valid MAC PDU containing a RRCConnectionSetup, including 'UE Contention
Resolution Identity' MAC control element and matching 'Contention Resolution Identity' }
then { UE transmits a RRCConnectionSetupComplete message }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.1.5.
[TS 36.321, clause 5.1.5]
retransmission;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 279
279
- if notification of a reception of a PDCCH transmission is received from lower layers, the UE shall:
...
- else if the CCCH SDU was included in Msg3 and the PDCCH transmission is addressed to its Temporary C-
RNTI:
- if the MAC PDU is successfully decoded:
- stop mac-ContentionResolutionTimer;
- if the MAC PDU contains a UE Contention Resolution Identity MAC control element; and
- if the UE Contention Resolution Identity included in the MAC control element matches the CCCH
SDU transmitted in Msg3:
- consider this Contention Resolution successful and finish the disassembly and demultiplexing of
the MAC PDU;
- set the C-RNTI to the value of the Temporary C-RNTI;
- consider this Random Access procedure successfully completed.
- else
- consider this Contention Resolution not successful and discard the successfully decoded MAC
PDU.
System Simulator:
- Cell 1
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 280
280
Preamble:
U - S Message
a matched identity.
<-- - 1 -
2 The UE transmits a MAC PDU containing an
--> MAC PDU 1 -
3 Check: For time equal to Contention
Resolution Timer, does UE send a PRACH
preamble?
--> PRACH preamble 1 F
4 Check: does the UE transmit a MAC PDU
containing an RRCConnectionRequest
message?
--> MAC PDU
1 P
- EXCEPTION: In parallel with steps 5 to 8, the
parallel behaviour in table 7.1.2.7.3.2-2 is
running.
- - - -
containing RRCConnectionSetup, but not
MAC control element
<-- MAC PDU
(RRCConnectionSetup)
2 -
message?
--> MAC PDU
2 P
MAC control element but with un matched
<-- MAC PDU 3 -
message?
--> MAC PDU 3 P
<-- MAC PDU 4 -
containing an RRCConnectionSetupComplete
message including SERVICE REQUEST
message?
--> MAC PDU
4 P
11-
14
- - - -

U - S Message
1 Check: UE transmits a MAC PDU containing
an RRCConnectionSetupComplete message
indicating acceptance of
RRCConnectionSetup message?
--> MAC PDU
2,3 F

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 281
281
7.1.2.7.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.2.7.3.2-1)
preambleTransMax N10 Max value
mac-ContentionResolutionTimer sf64 Max value
}
}
}
}

7.1.2.8 MAC contention resolution / C-RNTI
(1)
with { UE in E-UTRA RRC_CONNECTED state and after transmitting a
RRCConnectionReconfigurationComplete message for a handover without dedicated preamble }
ensure that {
when { The SS does not schedule any PDCCH transmission addressed to UE C-RNTI before Contention
resolution timer expiry }
then { The UE retransmits the RRCConnectionReconfigrationComplete message }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state and after transmitting a
RRCConnectionReconfigurationComplete message for a handover without dedicated preamble }
ensure that {
when { UE receive PDCCH transmission addressed to its C-RNTI before Contention resolution timer
expiry }
then { The UE does not retransmit the RRCConnectionReconfigrationComplete message }
}

[TS 36.321, clause 5.1.5]
retransmission;
- if notification of a reception of a PDCCH transmission is received from lower layers, the UE shall:
- if the C-RNTI MAC control element was included in Msg3:
- if the Random Access procedure was initiated by the MAC sublayer itself and the PDCCH transmission is
addressed to the C-RNTI and contains an UL grant for a new transmission; or
- if the Random Access procedure was initiated by a PDCCH order and the PDCCH transmission is
addressed to the C-RNTI:
- consider this Contention Resolution successful;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 282
282
- stop mac-ContentionResolutionTimer;
- consider this Random Access procedure successfully completed.
...
- else
- consider this Contention Resolution not successful and discard the successfully decoded MAC
PDU.
System Simulator:
- Cell 1 and Cell 2
- System information as in table 7.1.2.8.3.3-1.
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18] on cell 1.
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 283
283
U - S Message
- - - -
1 The SS transmits a MAC PDU containing an
handover to Cell 2, not including explicit
Random Access Preamble.
<-- MAC PDU - -
2 The UE transmits on cell 2 a MAC PDU
containing
RRCConnectionReconfigurationComplete,
including C-RNTI MAC control element. SS is
configured to not transmit RLC ACK for this
transmission.
--> MAC PDU - -
3 SS Does not schedule any PDCCH
transmission for UE C-RNTI
- - - -
4 Check: does the UE transmit a PRACH
preamble within time equal to Contention
Resolution Timer?
--> (PRACH preamble) 1 F
5 Check: does the UE transmit on cell 2 a MAC
PDU containing
RRCConnectionReconfigurationComplete with
RLC SN 0, including C-RNTI MAC control
element?
--> MAC PDU (RLC SN = 0 ) 1 P
6 SS sends PDCCH transmission for UE C-RNTI <-- - - -
7 Check: does the UE transmit MAC PDU
containing
RRCConnectionReconfigurationComplete with
RLC SN 0 within the next 2s?
--> MAC PDU (RLC SN =0 ) 2 F
8 Check: does the test result of CALL generic
procedure indicate that the UE is in E-UTRA
RRC_CONNECTED state on Cell 2?
- - 2 -

Table 7.1.2.8.3.3-1: SystemInformationBlockType2 (all steps, Table 7.1.2.8.3.2-1)
preambleTransMax N10 Max value
mac-ContentionResolutionTimer sf64 Max value
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 284
284
Table 7.1.2.8.3.3-2: RRCConnectionReconfiguration (step 1, Table 7.1.2.8.3.2-1)
Derivation path: 36.508 table 4.6.1-6, condition RBC-HO
c1 CHOICE{
mobilityControlInformation SEQUENCE { MobilityControlInformatio
n-HO

targetCellIdentity PhysicalCellIdentity of
4.4.4.2)

eutra-CarrierFreq Not present
}
}
}
}
}

7.1.2.9 MAC backoff indicator
(1)
ensure that {
when { SS sends a Random Access Response including a Backoff Indicator and the Random Access
Preamble identifier is different from the value received from the UE }
then { UE triggers RA preamble after a random time between 0 and the indicated Backoff
parameter }
}

(2)
ensure that {
when { SS sends a Random Access Response containing Backoff Indicator and a Random Access Preamble
identifier with the same value as received from the UE }
then { UE stores Backoff Indicator and sends a RRC connection request in the first scheduled UL
transmission }
}

(3)
ensure that {
when { UE receives a Contention Resolution failure }
then { UE triggers RA preamble after random time between 0 and the UE stored Backoff parameter }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.1.4, 5.1.5
and 7.2.
[TS 36.321 clause 5.1.4]
and Table 7.2-1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 285
285
...
...
- if in this Random Access procedure, the Random Access Preamble was selected by MAC:
- based on the backoff parameter in the UE, select a random backoff time according to a uniform distribution
between 0 and the Backoff Parameter Value;
[TS 36.321 clause 5.1.5]
- based on the backoff parameter in the UE, select a random backoff time according to a uniform distribution
between 0 and the Backoff Parameter Value;
[TS 36.321 clause 7.2]
Backoff Parameter values are presented in Table 7.2-1.
Table 7.2-1: Backoff Parameter values
Index Backoff Parameter value (ms)
0 0
1 10
2 20
3 30
4 40
5 60
6 80
7 120
8 160
9 240
10 320
11 480
12 960
13 Reserved
14 Reserved
15 Reserved

The reserved values of the backoff parameter if received by the current release version UEs shall be taken as 960 ms.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 286
286
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Registered, Idle Mode (state 2) according to [18].
Table 7.1.2.9.3.1-1: (Void)
Table 7.1.2.9.3.2-1: Backoff Parameter values.
x: Index y: Backoff Parameter value (ms)
1 10
2 20
3 30
4 40
5 60
6 80
7 120
8 160
9 240
10 320
11 480
12 960
13 960
14 960
15 960

U - S Message
- EXCEPTION: Steps 1 to 5e are repeated for
values of x and y according to table
7.1.2.9.3.2-1
- - - -
2 UE sends a Random Access Preamble --> Random Access Preamble - -
3 SS sends a Random Access Response with
the backoff parameter set to value Index field
x and with the Random Access Preamble
identifier different from the value received from
the UE in the Random Access Preamble.
The SS sets Timer_T1 to the Backoff value y
associated with the Index value x and starts
Timer_T1.
<-- Random Access Response(BI,
RAPID)
- -
4 Check: Does UE send a Random Access
Preamble while Timer_T1 is running?
Preamble in step 4, including T-CRNTI and not
including Backoff Indicator sub header
5A The UE transmits an RRCConnectionRequest
message.
--> - - -
5B The SS Transmits a valid MAC PDU
<-- MAC PDU
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 287
287

None
5C The UE transmits an
--> - - -
5D SS transmits SERVICE REJ ECT message
with EMM cause "Congestion" to complete the
procedure
Note: The EMM cause chosen is just for
convenience, to ensure that UE will abort the
procedure without side effects.
<-- - - -
5E The SS transmits an RRCConnectionRelease
message to release RRC connection and
move to RRC_IDLE.
<-- - - -
EXCEPTION: Steps 6 to 20 are repeated for
values of x and y according to table
7.1.2.9.3.2-1
- - - -
7 UE sends a Random Access Preamble --> Random Access Preamble - -
8 SS sends Random Access Response with a
backoff parameter set to value Index field x
and the Random Access Preamble identifier
value set to the same value as received from
the UE in the Random Access Preamble.
<-- Random Access Response(BI,
RAPID)
- -
9 Check: Does UE sends an
RRCConnectionRequest in the grant
associated to the Random Access Response
received in step 8?
--> MAC PDU
2 P
10 The SS sends a Contention Resolution Failure.
The SS sets Timer_T1 to the Backoff value y
associated with the Index value x and starts
Timer_T1.
<-- MAC Control PDU (Un
matching UE Contention
Resolution Identity)
- -
11 Check: Does UE send a Random Access
Preamble while Timer_T1 is running?
not including Backoff Indicator sub header
message.
--> - - -
<-- MAC PDU
- -
--> - - -
16-
19
- - - -
message to release RRC connection and
move to RRC_IDLE.
<-- - - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 288
288
7.1.3 DL-SCH data transfer
7.1.3.1 Correct handling of DL assignment / Dynamic case
(1)
ensure that {
when { UE receives downlink assignment on the PDCCH for the UEs C-RNTI and receives data in the
associated subframe and UE performs HARQ operation }
then { UE sends a HARQ feedback on the HARQ process }
}

(2)
ensure that {
when { UE receives downlink assignment on the PDCCH with a C-RNTI unknown by the UE and data is
available in the associated subframe }
then { UE does not send any HARQ feedback on the HARQ process }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 5.3.1
[TS 36.321, clause 5.3.1]
Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a particular UE
and provide the relevant HARQ information.
When the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI
during which it monitors PDCCH:
- if a downlink assignment for this TTI has been received on the PDCCH for the UEs C-RNTI, or Temporary
C-RNTI:
- if this is the first downlink assignment for this Temporary C-RNTI:
- consider the NDI to have been toggled.
- if the downlink assignment is for UEs C-RNTI and if the previous downlink assignment indicated to the
HARQ entity of the same HARQ process was either a downlink assignment received for the UEs Semi-
Persistent Scheduling C-RNTI or a configured downlink assignment:
- consider the NDI to have been toggled regardless of the value of the NDI.
- indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ
entity for this TTI.
System Simulator:
- Cell 1
- RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table
7.1.3.1.3.3-1
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 289
289
Preamble:
- The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is
executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no
data in uplink.
U - S Message
1 SS transmits a downlink assignment including
the C-RNTI assigned to the UE
<-- (PDCCH (C-RNTI)) - -
2 SS transmits in the indicated downlink
assignment a RLC PDU in a MAC PDU.
<-- MAC PDU - -
3 Check: Does the UE transmit an HARQ ACK
on PUCCH?
--> HARQ ACK 1 P
4 SS transmits a downlink assignment to
including a C-RNTI different from the assigned
to the UE
<-- (PDCCH (unknown C-RNTI)) - -
5 SS transmits in the indicated downlink
assignment a RLC PDU in a MAC PDU.
<-- MAC PDU - -
6 Check: Does the UE send any HARQ ACK on
PUCCH?
--> HARQ ACK 2 F

NOTE 1: For TDD, the timing of ACK/NACK is not constant as FDD, see Table 10.1-1 of TS 36.213.
Table 7.1.3.1.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)
Derivation path: 36.508 table 4.8.2.1.5-1
c1 CHOICE{
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated Infinity
}
}
}
}
}
}

Table 7.1.3.1.3.3-2: Void
Table 7.1.3.1.3.3-3: Void
7.1.3.2 Correct handling of DL assignment / Semi-persistent case
(1)
with { UE in E-UTRA RRC_Connected state with DRB established and sps-Configuration in DL is
enabled }
ensure that {
when { UE receives a DL assignment addressed to its stored SPS-CRNTI in SF-Num y and with NDI set
as 0 }
then { UE starts receiving DL MAC PDU in SF-Nums y+n*[semiPersistSchedIntervalDL] where n is
positive integer starting at zero }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 290
290

(2)
with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive
MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] }
ensure that {

when { UE receives a DL assignment addressed to its SPS-CRNTI in SF-Num p and with NDI set as 0,
where p!= y+n*[semiPersistSchedIntervalDL] }
then { UE starts receiving DL MAC PDU in SF-Nums p+n*[semiPersistSchedIntervalDL] and stops
receiving DL MAC PDU at SF-Nums y+n*[semiPersistSchedIntervalDL]where n is positive integer
starting at zero }
}

(3)
MAC PDU at SF-Num p+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a DL assignment [for retransmission] addressed to its SPS-CRNTI in SF-Num z and
with NDI set as 1, where z!= p+n*[semiPersistSchedIntervalDL] }
then { UE receives MAC PDU in SF-Num z as per the new grant for SPS-CRNTI }
}

(4)
MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a DL assignment addressed to its CRNTI in SF-Num p, such that p=
z+n*[semiPersistSchedIntervalDL] }
then { UE receives MAC PDU in SF-Num p as per assignment addresed to its C-RNTI }
}

(5)
with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS grant to receive MAC
PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a RRCConnectionReconfiguration including sps-Configuration with sps-
ConfigurationDL set as disable and hence resulting in DL SPS grant deactivation }
then { UE deletes the stored sps-Configuration DL parameters and stops receiving DL MAC PDUs as
per stored SPS assignment in SF-Num z+n*[semiPersistSchedIntervalDL] }
}

(6)
MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a PDCCH [for DL SPS explicit release according to Table 9.2-1A in TS 36.213]
addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p!=
z+n*[semiPersistSchedIntervalDL] }
then { UE sends an ACK to SS and releases the configured SPS assignment and stops receiving MAC
PDU in SF-Num z+n*[semiPersistSchedIntervalDL] as per assignment addresed to its SPS C-RNTI }
}

NOTE: SF-Num =[10*SFN +subframe] modulo 10240.
References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.3.1, 5.10 &
5.10.1, 36.331 clause 5.3.10.5, 36.300 clause 11.1.1 and 36.213 clause 9.2.
[TS 36.321, clause 5.3.1]
Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a particular UE
and provide the relevant HARQ information.
When the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI
during which it monitors PDCCH:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 291
291
- if a downlink assignment for this TTI has been received on the PDCCH for the UEs C-RNTI, or Temporary
C-RNTI:
- if this is the first downlink assignment for this Temporary C-RNTI:
- consider the NDI to have been toggled.
- if the downlink assignment is for UEs C-RNTI and if the previous downlink assignment indicated to the
HARQ entity of the same HARQ process was either a downlink assignment received for the UEs Semi-
Persistent Scheduling C-RNTI or a configured downlink assignment:
- indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ
entity for this TTI.
- else, if a downlink assignment for this TTI has been received on the PDCCH for the UEs Semi-Persistent
Scheduling C-RNTI:
- if the NDI in the received HARQ information is 1:
- consider the NDI not to have been toggled;
- indicate the presence of a downlink assignment and deliver the associated HARQ information to the
HARQ entity for this TTI.
- else, if the NDI in the received HARQ information is 0:
- if PDCCH contents indicate SPS release:
- clear the configured downlink assignment (if any);
- if timeAlignmentTimer is running:
- instruct the physical layer to transmit a positive acknowledgement.
- else:
- store the downlink assignment and the associated HARQ information as configured downlink
assignment;
- initialise (if not active) or re-initialise (if already active) the configured downlink assignment to start
in this TTI and to recur according to rules in subclause 5.10.1;
- set the HARQ Process ID to the HARQ Process ID associated with this TTI;
- consider the NDI bit to have been toggled;
- indicate the presence of a configured downlink assignment and deliver the stored HARQ information
to the HARQ entity for this TTI.
- else, if a downlink assignment for this TTI has been configured and there is no measurement gap in this TTI:
- instruct the physical layer to receive, in this TTI, transport block on the DL-SCH according to the configured
downlink assignment and to deliver it to the HARQ entity;
- set the HARQ Process ID to the HARQ Process ID associated with this TTI;
- indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the
HARQ entity for this TTI.
For downlink assignments received on the PDCCH for the UEs Semi-Persistent Scheduling C-RNTI and for
configured downlink assignments, the HARQ Process ID associated with this TTI is derived from the following
equation:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 292
292
HARQ Process ID =[floor(CURRENT_TTI/(Downlink Semi-Persistent Scheduling Interval))] modulo Number of
Configured SPS Processes,
where CURRENT_TTI=[(SFN * 10) +subframe number], Downlink Semi-Persistent Scheduling Interval is the
periodicity of semi-persistent scheduling signalled via RRC and Number of Configured SPS Processes is the number of
HARQ processes allocated for semi-persistent scheduling signalled via RRC.
[TS 36.321, clause 5.10]
When Semi-Persistent Scheduling is enabled by upper layer, the following information is provided:
- Semi-Persistent Scheduling C-RNTI;
- Uplink Semi-Persistent Scheduling Interval semiPersistSchedIntervalUL and number of empty transmissions
before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the uplink;
- Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;
- Downlink Semi-Persistent Scheduling Interval semiPersistSchedIntervalDL and number of configured HARQ
processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is
enabled for the downlink;
When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or
configured assignment shall be discarded.
[TS 36.321, clause 5.10.1]
After a Semi-Persistent downlink assignment is configured, the UE shall consider that the assignment recurs in each
subframe for which:
- (10 * SFN +subframe) =[(10 * SFN
start time
+subframe
start time
) +N * (Downlink Semi-Persistent Scheduling
Interval)] modulo 10240, for all N>0.
Where SFN
start time
and subframe
start time
are the SFN and subframe, respectively, at the time the configured downlink
assignment were (re-)initialised.
[TS 36.331, clause 5.3.10.5]
The UE shall:
1>reconfigure the semi-persistent scheduling in accordance with the received sps-Config:
[TS 36.300, clause 11.1.1]
In addition, E-UTRAN can allocate semi-persistent downlink resources for the first HARQ transmissions to UEs:
- RRC defines the periodicity of the semi-persistent downlink grant;
- PDCCH indicates whether the downlink grant is a semi-persistent one i.e. whether it can be implicitly reused in
the following TTIs according to the periodicity defined by RRC.
When required, retransmissions are explicitly signalled via the PDCCH(s). In the sub-frames where the UE has semi-
persistent downlink resource, if the UE cannot find its C-RNTI on the PDCCH(s), a downlink transmission according to
the semi-persistent allocation that the UE has been assigned in the TTI is assumed. Otherwise, in the sub-frames where
the UE has semi-persistent downlink resource, if the UE finds its C-RNTI on the PDCCH(s), the PDCCH allocation
overrides the semi-persistent allocation for that TTI and the UE does not decode the semi-persistent resources.
[TS 36.213, clause 9.2]
A UE shall validate a Semi-Persistent Scheduling assignment PDCCH only if all the following conditions are met:
- the CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-
RNTI
- the new data indicator field is set to 0. In case of DCI formats 2 and 2A, the new data indicator field refers to
the one for the enabled transport block.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 293
293
Validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-
1A.
If validation is achieved, the UE shall consider the received DCI information accordingly as a valid semi-persistent
activation or release.
If validation is not achieved, the received DCI format shall be considered by the UE as having been received with a
non-matching CRC.
Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation
DCI format 0 DCI format 1/1A DCI format 2/2A
TPC command for
scheduled PUSCH
set to 00 N/A N/A
Cyclic shift DM RS set to 000 N/A N/A
Modulation and coding
scheme and
redundancy version
MSB is set to 0 N/A N/A
HARQ process number N/A FDD: set to 000
TDD: set to 0000
FDD: set to 000
TDD: set to 0000
scheme
N/A MSB is set to 0 For the enabled
transport block:
MSB is set to 0
Redundancy version N/A set to 00 For the enabled
transport block:
set to 00

Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH Validation
DCI format 0 DCI format 1A
TPC command for scheduled
PUSCH
set to 00

N/A
Cyclic shift DM RS set to 000

N/A
Modulation and coding scheme and
redundancy version
set to 11111 N/A
Resource block assignment and
hopping resource allocation
Set to all 1s N/A
TDD: set to 0000
Modulation and coding scheme N/A set to 11111
Redundancy version N/A set to 00
Resource block assignment N/A Set to all 1s

7.1. 3.2.3 Test description
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].
- The UL RLC SDU size is set to not return any data.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 294
294
U - S Message
1 The SS Transmits a DL assignment using UEs
SPS C-RNTI in SF-Num Y, NDI=0
<-- (DL SPS Grant) - -
2 The SS transmits in SF-Num Y, a DL MAC
PDU containing a RLC PDU (DL-SQN=0)on
UM DRB
<-- MAC PDU - -
3 Check: Does the UE transmit a HARQ ACK? --> HARQ ACK 1 P
4 The SS transmits in SF-Num
Y+X(semiPersistSchedIntervalDL), a DL MAC
DRB
<-- MAC PDU - -
SPS C-RNTI in SF-Num P, NDI=0;
(Where Y+X<P<Y+2X)
7 The SS transmits in SF-Num P, a DL MAC
UM DRB
<-- MAC PDU - -
9 The SS transmits in SF-Num Y+2X, a DL
MAC PDU containing a RLC PDU (DL-
SQN=3)on UM DRB
<-- MAC PDU - -
10 Check: Does the UE transmit a HARQ
Feedback?
--> HARQ ACK/NACK 2 F
P+X(semiPersistSchedIntervalDL), a DL MAC
UM DRB; CRC is calculated in such a way will
result in CRC error in UE.
<-- MAC PDU - -
12 Check: Does the UE transmit a HARQ NACK? --> HARQ NACK 2 P
SPS C-RNTI in SF-Num Z, NDI=1;
Where (P+X <Z <P+2X); The DL HARQ
process is same as in step 11
14 The SS re-transmits in SF-Num Z, a DL MAC
UM DRB;
<-- MAC PDU - -
P+2X(semiPersistSchedIntervalDL), a DL
SQN=4)on UM DRB
<-- MAC PDU - -
C-RNTI in SF-Num
P+3X(semiPersistSchedIntervalDL)
<-- (DL Grant) - -
MAC PDU containing 1 RLC PDUs (DL-
SQN=4)on UM DRB;Note 1
<-- MAC PDU - -
20 Check: Does the UE transmit a HARQ ACK ? --> HARQ ACK 4 P
21 The SS Transmits a PDCCH [for DL SPS
explicit release] using UEs SPS C-RNTI in SF-
Num Q, NDI=0; Where (P+3X<Q <P+4X).
<-- PDCCH [for DL SPS explicit
release]
- -
SQN=5)on UM DRB;
<-- MAC PDU - -
24 Check: Does the UE transmit a HARQ --> HARQ ACK/NACK 6 F
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 295
295
Feedback?
SPS C-RNTI in SF-Num P+5X, NDI=0
26 The SS transmits in SF-Num P+5X, a DL
SQN=5)on UM DRB
<-- MAC PDU - -
28 Void - - - -
29 Void - - - -
30 SS Transmits RRCConnectionReconfiguration
to disable SPS-ConfigurationDL
- - - -
31 The UE transmits
--> - - -
P+nX(semiPersistSchedIntervalDL), a DL
SQN=5) on UM DRB; (n>5)
<-- MAC PDU - -
33 Check: Dose the UE transmit a HARQ
Feedback?
Note 1: The DL assignment for C-RNTI and hence the size of MAC PDU is different in size than stored SPS C-RNTI
DL assignment in step 6. This assures UE is reciving DSCH data as per DL assignment for C-RNTI and not
as per stored grant for SPS C-RNTI.
Note 2: For TDD, the subframe number for Y, P, Z and Q should be 0, 4, 5 and 9 respectively based on TDD
configuration 1.

Table 7.1.3.2.3.3-1: RRCConnectionReconfiguration. RadioResourceConfigDedicated (Preamble)
RadioResourceConfigDedicated::=SEQUENCE {
sps-Configuration ::=SEQUENCE {
semiPersistSchedC-RNTI FFF0H
sps-ConfigurationDL::=CHOICE{
enable SEQUENCE {
semiPersistSchedIntervalDL sf160 160 Subframe
numberOfConfSPS-Processes 8 FDD
numberOfConfSPS-Processes 7 Max DL HARQ
processes is 7
considering TDD
configuration 1.
TDD
n1Pucch-AN-Persistent 0
}
}
sps-ConfigurationUL Not Present
}
}

Table 7.1.3.2.3.3-2: RRCConnectionReconfiguration. RadioResourceConfigDedicated (step 30 of table
7.1.3.2.3.2-1)
semiPersistSchedC-RNTI Not Present
sps-ConfigurationDL::=CHOICE{
disable NULL
}
sps-ConfigurationUL Not Present
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 296
296
7.1.3.3 MAC PDU header handling
(1)
ensure that {
when { UE receives a MAC PDU containing an AMD PDU that is larger than 128 bytes with padding at
the end }
then { UE successfully decodes the MAC PDU and forward to higher layer }
}

(2)
ensure that {
when { UE receives a MAC PDU containing an AMD PDU that is smaller than 128 bytes with padding at
the end }
}

(3)
ensure that {
when { UE receives a MAC PDU containing an single AMD PDU with no padding }
}

(4)
ensure that {
when { UE receives a MAC PDU containing multiple MAC SDUs each containg an AMD PDU and no
padding }
then { UE successfully decodes the MAC PDU and forward the AMD PDUs to higher layer }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 6.1.2
and 6.2.1.
[TS 36.321, clause 6.1.2]
A MAC PDU header consists of one or more MAC PDU sub-headers; each sub header corresponding to either a MAC
A MAC PDU sub header consists of the six header fields R/R/E/LCID/F/L but for the last sub header in the MAC PDU
and for fixed sized MAC control elements. The last sub header in the MAC PDU and sub-headers for fixed sized MAC
control elements consist solely of the four header fields R/R/E/LCID. It follows that a MAC PDU sub header
corresponding to padding consists of the four header fields R/R/E/LCID.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 297
297
LCID R
F L
7-bitsLfield
15-bitsLfield
R E LCID R
F L
R E
L
Oct1
Oct2
Oct1
Oct2
Oct3

Figure 6.1.2-1: R/R/E/LCID/F/L MAC sub header

LCID R
R E Oct1

Figure 6.1.2-2: R/R/E/LCID MAC sub header

have any value and the UE shall ignore it. When padding is performed at the end of the MAC PDU, zero or more
padding bytes are allowed.
placed at the beginning of the MAC PDU before any other MAC PDU subheader.A maximum of one MAC PDU can be
transmitted per TB per UE.
MACControl
element1
...
R/R/E/LCID
sub-header
MACheader
MACpayload
R/R/E/LCID[/F/L]
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
...
R/R/E/LCID/F/L
sub-header
R/R/E/LCIDpadding
sub-header
MACControl
element2
MACSDU MACSDU
Padding
(opt)

and padding
[TS 36.321, clause 6.2.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 298
298
included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU,
when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC PDU.
The LCID field size is 5 bits;
- L: The Length field indicates the length of the corresponding MAC SDU or MAC control element in bytes.
There is one L field per MAC PDU sub header except for the last sub header and sub-headers corresponding to
fixed-sized MAC control elements. The size of the L field is indicated by the F field;
- F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per
MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control
elements. The size of the F field is 1 bit. If the size of the MAC SDU or MAC control element is less than 128
bytes, the UE shall set the value of the F field to 0, otherwise the UE shall set it to 1;
- E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set
to "1" to indicate another set of at least R/R/E/LCID fields. The E field is set to "0" to indicate that either a MAC
SDU, a MAC control element or padding starts at the next byte;
- R: Reserved bits, set to "0".
The MAC header and sub-headers are octet aligned.
Index LCID values
00000 CCCH
11101 Timing Advance Command
11110 DRX Command
11111 Padding

Table 6.2.1-2: Values of LCID for UL-SCH
Index LCID values
00000 CCCH
11010 Power Headroom Report
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding

Table 6.2.1-3: Values of F field:
Index Size of Length field (in bits)
0 7
1 15

System Simulator:
- Cell 1
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 299
299
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 300
300
U - S Message
RLC SDU of 130 bytes in an AMD PDU
(SN=0) with polling field P set to 1 and 5
bytes of padding. The MAC header contains
two MAC sub-headers where the first MAC
sub-header is a 3-byte R/R/E/LCID/F/L MAC
sub-header with E field set to 1, the F set to
1, the LCID field set to 00011 and the L
field set to 132 bytes. The second MAC sub-
header is a padding control 1byte R/R/E/LCID
MAC sub-header with E field set to 0 and
LCID field set to 11111.
<-- MAC PDU (R/R/E/LCID/F/L MAC
sub-header (E=1, LCID=00011,
F=1, L=132), MAC R/R/E/LCID
MAC sub-header (E=0,
LCID=11111), 132 bytes MAC
SDU and 5 bytes padding)
- -
containing an RLC STATUS PDU
achnowleding the reception of the AMD PDU
in step 1?

--> MAC PDU (RLC STATUS PDU
(ACK_SN 1))
1 P
RLC SDU of 40 bytes in an AMD PDU(SN=1)
with polling field P set to 1and 5 bytes of
padding. The MAC header contains two MAC
sub-headers where the first MAC sub-header
is a 2-byte R/R/E/LCID/F/L MAC sub-header
with E field set to 1, the F set to 0, the
LCID field set to 00011 and the L field set to
42 bytes. The second MAC sub-header is a
padding control 1byte R/R/E/LCID MAC sub-
header with E field set to 0 and LCID field
set to 11111.
<-- MAC PDU (R/R/E/LCID/F/L MAC
F=0, L=42), R/R/E/LCID MAC
sub-header (E=0, LCID=11111),
42 bytes MAC SDU and 5 bytes
padding)
- -
in step 3?
(ACK_SN 2))
2 P
MAC SDU with a RLC SDU of 130 bytes in an
AMD PDU(SN=2) with polling field P set to 1.
The MAC header contains one R/R/E/LCID
MAC sub-header with E field set to 0 and the
LCID field set to 00011.
<-- MAC PDU (R/R/E/LCID MAC sub-
header (E=0, LCID=00011), 132
bytes MAC SDU)
- -
in step 5?
(ACK_SN 3))
3 P
7 The SS transmits a MAC PDU containing one
MAC SDU containing a RLC SDU of size 127
bytes in an AMD PDU (SN=3) and five MAC
SDUs each containing a RLC SDU of 41 bytes
in an AMD PDU (SN=4 to 8) in an AMD PDU
with the polling field P set to 1 in the last
AMD PDU. The MAC header contains six MAC
sub-headers where the first The MAC sub-
header contains a 3 byte R/R/E/LCID/F/L MAC
sub-header with E field set to 1 , LCID field
set to 00011, F field set to 1 and the L field
set to 129. The second to fifth MAC sub-
header are two byte R/R/E/LCID/F/L MAC sub-
headers with E field set to 1 , LCID field set
to 00011, F field set to 0 and the L field set
to 43 bytes. The sixth MAC sub-header is a
one byte R/R/E/LCID MAC sub-header with E
field set to 0 and the LCID field set to
00011.
<-- MAC PDU (R/R/E/LCID/L MAC
F=1, L=129), 4 x R/R/E/LCID/L
MAC sub-header (E=1,
LCID=00011, F=0, L=43),
R/R/E/LCID MAC sub-header
(E=0, LCID=00011), 129 bytes
MAC SDU, 5 x 43 bytes MAC
SDUs)
4 -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 301
301
achnowleding the reception of the AMD PDUs
in step 7?
(ACK_SN 9))
4 P

None
7.1.3.4 Correct HARQ process handling / DCCH and DTCH
(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established }
ensure that {
when { the UE receives a MAC PDU for DRB and decode fails }
then { the UE transmits a NACK for the corresponding HARQ process }
}

(2)
ensure that {
when { the UE receives a MAC PDU retransmission for DRB, and results in successful decode}
then { the UE transmits an ACK for the corresponding HARQ process and delivers data to upper
layers }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 &
5.3.2.2.
[TS 36.321, clause 5.3.2.1]
There is one HARQ entity at the UE which maintains a number of parallel HARQ processes. Each HARQ process is
associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received
on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).
The number of DL HARQ processes is specified in [2], clause 7.
When the physical layer is configured for spatial multiplexing [2], one or two TBs are expected per subframe and they
are associated with the same HARQ process. Otherwise, one TB is expected per subframe.
The UE shall:
- If a downlink assignment has been indicated for this TTI:
- allocate the TBs received from the physical layer and the associated HARQ information to the HARQ
process indicated by the associated HARQ information.
- If a downlink assignment has been indicated for the broadcast HARQ process:
- allocate the received TB to the broadcast HARQ process.
NOTE: In case of BCCH a dedicated broadcast HARQ process is used.
[TS 36.321, clause 5.3.2.2]
For each subframe where a transmission takes place for the HARQ process, one or two (in case of spatial multiplexing)
TBs and the associated HARQ information are received from the HARQ entity.
For each received TB and associated HARQ information, the HARQ process shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 302
302
- if the NDI, when provided, has been toggled compared to the value of the previous received transmission
corresponding to this TB; or
- if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB
according to the system information schedule indicated by RRC; or
- if this is the very first received transmission for this TB(i.e. there is no previous NDI for this TB):
- consider this transmission to be a new transmission.
- else:
- consider this transmission to be a retransmission.
The UE then shall:
- if this is a new transmission
- replace the data currently in the soft buffer for this TB with the received data.
- else if this is a retransmission:
- if the data has not yet been successfully decoded:
- combine the received data with the data currently in the soft buffer for this TB.
- if the TB size is different from the last valid TB size signalled for this TB:
- the UE may replace the data currently in the soft buffer for this TB with the received data.
- attempt to decode the data in the soft buffer for this TB;
- if the data in the soft buffer was successfully decoded for this TB:
- if the HARQ process is equal to the broadcast process, deliver the decoded MAC PDU to upper layers.
- else if this is the first successful decoding of the data in the soft buffer for this TB:
-deliver the decoded MAC PDU to the disassembly and demultiplexing entity.
- generate a positive acknowledgement (ACK) of the data in this TB.
- else:
- generate a negative acknowledgement (NACK) of the data in this TB.
- if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention
Resolution is not successful (see subclause 5.1.5); or
- if the HARQ process is equal to the broadcast process; or
- - if timeAlignmentTimer is stopped or expired:
- do not indicate the generated positive or negative acknowledgement to the physical layer.
- else:
- indicate the generated positive or negative acknowledgement for this TB to the physical layer.
The UE shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when
determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.
System Simulator:
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 303
303
7.1.3.4.3.3-1
UE:
None.
Preamble:
U - S Message
- EXCEPTION: Steps 1 to 7 are run
8[FDD]/7[TDD] times using test parameter
values as given for each iteration in table
7.1.3.4.3.2.-2.
- - - -
1 The SS indicates a new transmission on
PDCCH and transmits a MAC PDU (containing
an RLC PDU), with content set so that UE
could not successfully decode the data from its
soft buffer. The AMD PDU contains a full RLC
SDU. (Note 1)
<-- MAC PDU 1 -
2 Check: Does the UE transmit a HARQ NACK? --> HARQ NACK P
EXCEPTION: Step 3 shall be repeated till
HARQ ACK is received at step 4 or until HARQ
retransmission count =4 is reached for MAC
PDU at step 3 (Note 2).

3 The SS indicates a retransmission on PDCCH
and transmits the same MAC PDU like step 1
(Note 1).
<-- MAC PDU - -
EXCEPTION: Up to 3 HARQ NACK from the
UE should be allowed at step 4 (Note 2).

4 Check: Does the UE send a HARQ ACK? --> HARQ ACK 2 P
5 UE transmit a Scheduling Request on PUCCH --> (SR) - -
6 The SS sends an UL grant suitable for the loop
back PDU to transmitted
<-- (UL Grant) - -
7 The UE transmit a MAC PDU containing the
loop back PDU corresponding to step 1 and 3
--> MAC PDU - -
Note 1: SS should transmit this PDU using I
TBS
=6, N
PRB
=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in
TBSize of 328 and having coding rate more than 1.
Note 2: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption
that, given the radio conditions used in this test case, a UE soft combiner implementation should have
sufficient retransmissions to be able to successfully decode the data in its soft buffer.

Table 7.1.3.4.3.2-2: Test Parameters
Iteration DL HARQ process
(X)
1 0
2 1
3 2
4 3
5 4
6 5
7 6
8 7[only for FDD]
Note: The maximum DL HARQ process is 7 for
TDD configuration 1.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 304
304
c1 CHOICE{
}
}
}
}
}
}

7.1.3.5 Correct HARQ process handling / CCCH
(1)
with { UE in E-UTRA RRC_ IDLE state with RRC connection establishment procedure initiated }
ensure that {
when { UE receives a MAC PDU addressed to RA-RNTI }
then { UE does not transmit ACK/NACK for the corresponding HARQ process }
}

(2)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI without UE Contention Resolution Identity
matching the one included in the RRCConnectionRequest message }
then { UE does not transmit a ACK/NACK for the corresponding HARQ process }
}

(3)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI and cannot decode properly }
then { UE does not transmits a NACK for the corresponding HARQ }
}

(4)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI with UE Contention Resolution Identity matching
the one included in the RRCConnectionRequest message }
then { UE transmits an ACK for the corresponding HARQ process and delivers data to upper
layers }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 and
5.3.2.2.
[TS 36.321, clause 5.3.2.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 305
305
The UE shall:
[TS 36.321, clause 5.3.2.2]
corresponding to this TB; or
- if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB
according to the system information schedule indicated by RRC; or
- else:
The UE then shall:
- if this is a new transmission
- if a retransmission is indicated for this TB:
- if the HARQ process is equal to the broadcast process:
- deliver the decoded MAC PDU to upper layers.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 306
306
- deliver the decoded MAC PDU to the disassembly and demultiplexing entity.
- else:
- if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and a UE the
Contention Resolution Identity match is not indicated successful (see subclause 5.1.5); or
- - if timeAlignmentTimer is stopped or expired:
- else:
determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.
System Simulator:
- Cell 1
- System information taking into account parameters in table 7.1.3.5.3.3-1
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode state (state 2) according to [18].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 307
307
U - S Message
a matched identity.
<-- - - -
2 The UE transmits Preamble on PRACH --> PRACH Preamble - -
with matching RA-Id and including T-CRNTI.
The CRC is calculated in such a way, it will
result in CRC error on UE side
4 Check: does the UE transmit a HARQ
ACK/NACK?
with matching RA-Id and including T-CRNTI .
The CRC is calculated in such a way, it will
result in CRC pass on UE side.
ACK/NACK?
--> MAC PDU - -
RRCConnectionSetup, and including UE
Contention Resolution Identity MAC control
element with not matching Contention
Resolution Identity.
<-- MAC PDU - -
ACK/NACK?
--> MAC PDU - -
element with matching Contention Resolution
Identity. The CRC is calculated in such a way
that it will result in CRC error on UE side
<-- MAC PDU - -
15 Check: Does UE transmit a HARQ NACK? --> HARQ NACK 3 F
--> MAC PDU - -
19 The SS transmits the same MAC PDU like in
step 14, but the CRC is calculated in such a
way that it will result in CRC pass on UE side
<-- MAC PDU - -
20 Check: does the UE transmit a HARQ ACK? --> HARQ ACK 4 P
including SERVICE REQUEST message
indicating acceptance of
RRCConnectionSetup message
--> MAC PDU - -
22-
25
- - - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 308
308
preambleTransMax n8
mac-ContentionResolutionTimer sf64 Max Value
}
}
prach-Configuration SEQUENCE {
2 of 36.211, this
results in PRACH
preamble
transmission start
in even frame
numbers and sub-
frame number 4
FDD
4 of 36.211, this
results in PRACH
preamble
transmission with
frequency
resource index=0;
occurring in even
radio frames;
resource is
located in first half
frame and sub
frame number 3
Note 1
TDD
}
}
}
ue-TimersAndConstants SEQUENCE{
t300 ms2000 T300
}
}

7.1.3.6 Correct HARQ process handling / BCCH
(1)
ensure that {
when { UE receives a MAC PDU addressed to SI-RNTI }
then { UE does not send any ACK/NACK for the corresponding dedicated HARQ process }
}

5.3.2.2.
[TS 36.321, clause 5.3.2.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 309
309
The UE shall:
[TS 36.321, clause 5.3.2.2]
corresponding tothis TB; or
- if the HARQ process is equal to the broadcast process and if the physical layer indicates a new transmission for
the TB according to the system information schedule indicated by RRC; or
- else:
The UE then shall:
- if this is a new transmission:
- else if this is a retransmission:
- if the HARQ process is equal to the broadcast process:
- deliver the decoded MAC PDU to upper layers.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 310
310
- deliver the decoded MAC PDU to the disassembly and demultiplexing entity.
- else:
- if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention
Resolution is not yet successful (see subclause 5.1.5); or
- if timeAlignmentTimer is stopped or expired:
- else:
determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous
transmission.
System Simulator:
- Cell 1
UE:
- None.
Preamble:
- RRC Connection Reconfiguration (Preamble: Table 4.5.3.3-1) using parameters as specified in Table 7.1.3.6.3.3-
4
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 311
311
U - S Message
A The SS transmits a Paging message including
the systemInfoModification. (Note 1)
- - - -
1 The SS transmits an updated system
information with SI-RNTI addressed in L1/L2
header at the start of the modification period.
CRC is calculated in such a way, it will result in
CRC fail on UE side. Dedicated HARQ
process for broadcast is used.
<-- - - -
2 Check: Does the UE transmit a HARQ
ACK/NACK? (Note 2 and 3)
3 Void - - - -
4 Void - -
5 Void - - - -
6 After 100ms of step 2, the SS transmits an
updated system information [contents same as
in step 1] with SI-RNTI addressed in L1/L2
header. CRC is calculated in such a way, it will
result in CRC pass on UE side. Dedicated
HARQ process for broadcast is used.
- - - -
7 Check: Does the UE transmit an ACK/NACK?
(Note 2 and 4)
-> HARQ ACK/NACK 1 F
8 SS is configured to not allocate UL Grants on
Scheduling Request
- - - -
9 The SS Transmits MAC PDU containing a RLC
PDU
<-- MAC PDU - -
10 The UE transmits a HARQ ACK --> HARQ ACK - -
11 Check: Does the UE transmit PRACH
Preamble, using PRACH resources as in new
SI?
12 The SS transmits Random Access Response <-- Random Access Response - -
13 The UE transmits a MAC PDU with C-RNTI
containing loop backed RLC PDU
--> MAC PDU - -
14 SS sends PDCCH transmission for UE C-RNTI
to complete contention resolution.
- - - -
Note 1: To guarantee that the UE will receive at least one Paging in the Modification Period preceding the SysInfo
change, SS should send the Paging message in every eligible PO in this Modification Period.
Note 2: When requested to check HARQ feedback for the dedicated broadcast HARQ process, the SS
shall assume the same PUCCH reception requirement as specified in TS 36.213 section 10 for a normal
HARQ process.
Note 3: For duration of 100ms, the SS should check HARQ NACK for all broadcast SIBs. This duration is sufficient
to ensure that SS transmits few times SIBs with CRC corruption.
Note 4: For duration of 5020ms (5120 - 100), the SS should check HARQ ACK for all broadcast SIBs. 5120ms is
the system information modification period calculated based on the default values of parameters specified
in TS 36.508.( modification period =modificationPeriodCoeff * defaultPagingCycle,and in TS 36.508,
modificationPeriodCoeff=4 and defaultPagingCycle=128radio frames).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 312
312
Table 7.1.3.6.3.3-1: SystemInformationBlockType2 (steps 1 and 6 of table 7.1.3.6.3.2-1)
prach-Config SEQUENCE {
rootSequenceIndex 20 (u =2, Value different
than default in TS
36.508)
FDD
rootSequenceIndex 2 (u =2, Value different
than default in TS
36.508)
rootSequenceInde
x should take
value from table of
5.7.2-5 in TS
36.211 since, the
PRACH format 4
is used as default
for testing for
TDD.
TDD
}
}
}

Table 7.1.3.6.3.3-2: Paging (step A, 5 of table 7.1.3.6.3.2-1)
}

Table 7.1.3.6.3.3-3: SystemInformationBlockType1 (step 1 of table 7.1.3.6.3.2-1)
}

Table 7.1.3.6.3.3-4: RRCConnectionReconfiguration (Preamble)
c1 CHOICE{
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 313
313
7.1.3.7 MAC padding
(1)
ensurethat {
when{ UE is receiving RLC PDUs in MAC PDUs with padding greater than 2 bytes }
then { UE acknowledges reception of the RLC PDUs }
}

(2)
ensure that {
when { UE is receiving RLC PDUs in MAC PDUs with padding equal to or less than 2 bytes }
then { UE acknowledges reception of the RLC PDUs }
}

(3)
ensure that {
when { SS is tranmitting a MAC control Timing Advance PDU with padding equal to or less than 2
bytes and no Data MAC PDU sub-headers followed by tranmitting a RLC PDU }
then { UE acknowledges reception of the RLC PDU using the new Timing Advance }
}

[TS 36.321 clause 6.1.2]
When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding are
MACControl
element1
...
R/R/E/LCID
sub-header
MACheader
MACpayload
R/R/E/LCID
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
...
R/R/E/LCID/F/L
sub-header
R/R/E/LCIDpadding
sub-header
MACControl
element2
MACSDU MACSDU
Padding
(opt)

and padding
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 314
314
System Simulator:
- Cell 1
UE:
None.
Preamble:
U - S Message
RLC SDU in an AMD PDU with polling field P
set to 1. The MAC SDU payload is set 8 bytes
smaller than the TB size allocated in the DL
Assignment minus AMD PDU and MAC
headers. SS adds a 7-byte padding at the end
of the MAC PDU and inserts a MAC padding
sub-header after the MAC SDU sub-header.
<-- MAC PDU(AMD PDU, 7-byte
padding)
- -
2 Check: Does the UE transmit an RLC STATUS
PDU with ACK_SN field equal to 1?
--> RLC STATUS PDU (ACK_SN 1) 1 P
RLC SDU in an AMD PDU with polling field P
set to 1. The MAC SDU payload is set to 1-
byte smaller than the TB size allocated in the
DL Assignment minus AMD PDU and MAC
headers. SS adds a 1 byte padding by
inserting a MAC PDU sub-header before first
Data MAC PDU sub-header.
<-- MACPDU(AMD PDU, one byte
padding)
- -
PDU with ACK_SN field equal to 2?
(ACK_SN =2) )
2 P
5 The SS sets the downlink assignment for TBS
of 16-bits
- - - -
6 The SS transmits a Timing Advance without
any additional padding. Start Timer_1 =Time
Alignment timer value.
<-- MAC Control PDU(Timing
Advance)
- -
7 The SS sets the downlink assignment for TBS
of 24-bits
- - - -
8 The SS waits a time period equal to 0.5 of
Timer_1 value and configures a MAC PDU that
consists of only a Control MAC PDU sub
header (8-bits). Transmit another Timing
Advance MAC PDU (8-bits) which leaves 1-
byte padding. The SS does not transmit any
subsequent timing alignment. Restart Timer_1
=Time Alignment timer value
<-- MAC Control Element (Timing
Advance) +1-byte padding
- -
9 The SS waits a time period equal to 0.7 of
Timer_1.
- - - -
9A SS transmits MAC PDU containing one RLC
SDU in an AMD PDU with polling field P set
to 1.
<-- MAC PDU(AMD PDU (SN=2,
P=1))
- -
PDU acknowledging the reception of the RLC
PDU in step 9 with new Timing Advance?
(ACK_SN =3))
3 P

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 315
315
None.
7.1.3.8 Void
7.1.3.9 MAC reset / DL
(1)
ensure that {
when { UE MAC is reset, due to handover to a new cell }
then { UE flushes DL HARQ buffer }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state )
ensure that {
when{ UE MAC is reset, due to handover to a new cell }
then { UE considers the next transmission for each DL HARQ process as very first }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.9.
[TS 36.321 clause 5.9]
If a reset of the MAC entity is requested by upper layers, the UE shall:
- initialize Bj for each logical channel to zero;
- stop (if running) all timers;
- consider the timeAlignmentTimer as expired and perform the corresponding actions in subclause 5.2;
- set the NDIs for all uplink HARQ processes to the value 0;
- stop, if any, ongoing RACH procedure;
- discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any;
- flush Msg3 buffer;
- cancel, if any, triggered Scheduling Request procedure;
- cancel, if any, triggered Buffer Status Reporting procedure;
- cancel, if any, triggered Power Headroom Reporting procedure;
- flush the soft buffers for all DL HARQ processes;
- for each DL HARQ process, consider the next received transmission for a TB as the very first;
- release, if any, Temporary C-RNTI.
System Simulator:
- Cell 1 and Cell 2
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 316
316
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) in Cell 1 according to [18]
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while columns marked "T1"
is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this
clause.
T0 Cell-specific RS EPRE dBm/15Khz -90 Off
T1 Cell-specific RS EPRE dBm/15Khz -90 -80

Table 7.1.3.9.3.3-2 illustrates the specific message content of RRC Connection Reconfiguration message during
preamble.
U - S Message
1 The SS ignores scheduling requests and does
not allocate any uplink grant.
- - - -
RLC SDU on DRB, but the CRC is calculated
in such a way that it will result in CRC error on
UE side.
<-- MAC PDU (1 RLC SDU of 40
bytes on DRB)
- -
3 The UE transmit a HARQ NACK --> HARQ NACK - -
row "T1" in table 7.1.4.12.3.2-1
- - - -
handover to Cell 2, including explicit Random
Access Preamble.
<-- - - -
6 The UE transmits on Cell 2,
--> - - -
7 Check: For 100 ms, does the UE transmit any
HARQ NACK?
--> HARQ NACK 1 F
8 The SS transmits a MAC PDU containing RLC
SDU on DRB. The HARQ Process and NDI on
PDCCH is same as in step 2. The SS shall
ensure that the HARQ process used at step 2
will not be used in between steps 4 and 7.
bytes on DRB)
- -
9 Check: Does the UE transmit a scheduling
request?
--> (SR) 2 P
10 The SS allocates UL Grant sufficient for one
RLC SDU to be loop backed in a TTI, and NDI
indicates new transmission
<-- Uplink Grant - -
11 The UE transmits a MAC PDU including one
RLC SDU
--> MAC PDU - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 317
317
c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityControlInfo-HO
4.6.5)

}
}
}
}
}

c1 CHOICE{
}
}
}
}
}
}

7.1.4 UL-SCH data transfer
7.1.4.1 Correct handling of UL assignment / Dynamic case
(1)
ensure that {
when { UE receives for a TTI an uplink grant with valid C-RNTI }
then { UE transmits data and associated HARQ information to the HARQ entity for this TTI }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 5.4.1.
[TS 36.321, clause 5.4.1]
In order to transmit on the UL-SCH the UE must have a valid uplink grant (except for non-adaptive HARQ
retransmissions) which it may receive dynamically on the PDCCH or in a Random Access Response or which may be
configured semi-persistently. To perform requested transmissions, the MAC layer receives HARQ information from
lower layers.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 318
318
When timeAlignmentTimer is running and the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-
RNTI, the UE shall for each TTI :
- if an uplink grant for this TTI has been received in a Random Access Response:
- set NDI to the value 0 and consider the NDI to have been toggled.
- if an uplink grant for this TTI has been received on the PDCCH for the UEs C-RNTI or Temporary C-
RNTI; or
- if the uplink grant is for UEs C-RNTI and if the previous uplink grant delivered to the HARQ entity for the
same HARQ process was either an uplink grant received for the UEs Semi-Persistent Scheduling C-RNTI or
a configured uplink grant:
- deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.
- else, if an uplink grant for this TTI has been received on the PDCCH for the UEs Semi-Persistent C-RNTI:
- indicate a valid uplink grant and the associated HARQ information to the HARQ entity for this TTI.
...
NOTE 1: The period of configured uplink grants is expressed in TTIs.
NOTE 2: If the UE receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi
persistent scheduling C-RNTI requiring transmissions in the same UL subframe, the UE may choose to
continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling
C-RNTI.
NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH
transmission during a measurement gap, the UE processes the grant but does not transmit on UL-SCH.
System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 319
319
U - S Message
- - - -
2 SS transmits a MAC PDU including a RLC
SDU
<-- MAC PDU 1 -
3 Void --> - - -
- EXCEPTION: Step 4 runs in parallel with
behaviour in table 7.1.4.1.3.2-2
- - - -
4 The SS is configured for Uplink Grant
Allocation Type 2. For 400 ms SS transmits
an UL Grant every 10 ms, allowing the UE to
return the RLC SDU as received in step 2, on
PDCCH, but with the C-RNTI different from the
C-RNTI assigned to the UE.Note 1:
<-- (UL Grant (unknown C-RNTI)) - -
corresponding to grant in step 4?
--> MAC PDU 1 F
Allocation Type 2. SS transmits an UL Grant,
allowing the UE to return the RLC SDU as
received in step 2, on PDCCH with the C-RNTI
assigned to the UE.
<-- (UL Grant (C-RNTI)) - -
--> MAC PDU 1 P
Note 1: Note 400 ms corresponding to 40 frames is selected to be sufficiently large than loop back delay and small
than the time needed for Scheduling Request to be repeated dsr-TransMax times( {64-1}* 20 milli
seconds ).

U - S Message
1 UE transmits a Scheduling Request. --> (SR) - -

7.1.4.1.3.3 Specific message contents.
Table 7.1.4.1.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration
in preamble
SchedulingRequest-Configuration ::=CHOICE {
setup SEQUENCE {
}
}

7.1.4.2 Correct handling of UL assignment / Semi-persistent case
(1)
with { UE in E-UTRA RRC_Connected state with DRB established and sps-Configuration in UL is
enabled }
ensure that {
when { UE receives a UL grant addressed to its stored SPS-CRNTI in SF-Num y and with NDI set as
0 }
then { UE starts transmitting UL MAC PDU in SF-Num F1 }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 320
320
(2)
with { UE in E-UTRA RRC_Connected state with DRB established and stored UL SPS grant to transmit MAC
PDU at SF-Num F1 }
ensure that {
when { UE receives a UL grant addressed to its SPS-CRNTI in SF-Num-frame p and with NDI set as 0,
where p+4!=F1(FDD) or p+k(p)!=F1(TDD) }
then { UE starts transmiting UL MAC PDU in SF-Num F2 and stops transmiting UL MAC PDU at SF-
NF1um }
}

(3)
PDU at SF-Num F1 }
ensure that {
when { UE receives a UL grant [for retransmission] addressed to its SPS-CRNTI in SF-Num z and with
NDI set as 1, for the corresponding HARQ Process, where z+4!=F1(FDD) or z+k(z)!=F1(TDD) }
then { UE re-tranmis MAC PDU in SF-Num z+4(FDD) or z+k(z)(TDD) as per the new grant for SPS-
CRNTI }
}

(4)
PDU at SF-Num F3 }
ensure that {
when { UE receives a UL grant addressed to its CRNTI in SF-Num p, such that in SF-Num p+4=F3(FDD)
or p+k(p)=F3(TDD) }
then { UE transmits MAC PDU in SF-Num p+4(FDD) or p+k(p)(TDD) as per grant addresed to its C-
RNTI }
}

(5)
PDU at SF-Num F3 }
ensure that {
when { UE receives a RRCConnectionReconfiguration including sps-Configuration with sps-
ConfigurationUL set as disable and hence resulting in UL SPS grant deactivation }
then { UE deletes the stored sps-Configuration UL parameters and stops transmitting UL MAC PDUs
as per stored SPS grant in SF-Num F3 }
}

(6)
with { UE in E-UTRA RRC_Connected state with DRB established and configured UL SPS grant }
ensure that {
when { UE transmits implicitReleaseAfter MAC PDUs on SPS-Grant containing zero MAC SDU }
then { UE clears configured SPS grant }
}

(7)
PDU at SF-Num F3 }
ensure that {
when { UE receives a PDCCH [for UL SPS explicit release according to Table 9.2-1A in TS 36.213]
addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p+4!=F3(FDD) or
p+k(p)!=F3(TDD) }
then { UE releases the configured SPS grant and stops transmitting UL MAC PDU in SF-Num F3 as
per grant addresed to its SPS C-RNTI }
}

NOTE: SF-Num =[10*SFN +subframe] modulo 10240.
NOTE 2: The value of the k(y), k(p), k(z) is k value determined according to the table 8-2 in the TS 36.213, given
that UL grant is in subframe y, p, z.
NOTE 3: The Subframe_Offset(y+k(y)), Subframe_Offset(p+k(p)), Subframe_Offset(z+k(z)) is subframe_offset
value determined according to the clause 5.10.2 in the TS36.321, given the position of initial Semi-
Persistent grant on subframe y+k(y), p+k(p), z+k(z).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 321
321
NOTE 4: To simply the TP description, following abbreviations are defined:
For FDD:
F1 =y+4+n*[semiPersistSchedIntervalUL]
F2 =p+4+n*[semiPersistSchedIntervalUL]
F3 =z+4+n*[semiPersistSchedIntervalUL]
For TDD:
F1 =y+k(y)+n*[semiPersistSchedIntervalUL]+Subframe_Offset(y+k(y))*(n modulo 2)
F2 =p+k(p)+n*[semiPersistSchedIntervalUL]+Subframe_Offset(p+k(p))*(n modulo 2)
F3 =z+k(z)+n*[semiPersistSchedIntervalUL]+Subframe_Offset(z+k(z))*(n modulo 2)
n >=0
References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.1, 5.10,
5.10.2, 7.4, 36.331 clause 5.3.10.5, 36.213 clause 8, 9.2 and 36.300 clause 11.1.2.
[TS 36.321, clause 5.4.1]
In order to transmit on the UL-SCH the UE must have a valid uplink grant (except for non-adaptive HARQ
retransmissions) which it may receive dynamically on the PDCCH or in a Random Access Response or which may be
configured semi-persistently. To perform requested transmissions, the MAC layer receives HARQ information from
lower layers.
When timeAlignmentTimer is running and the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-
RNTI, the UE shall for each TTI:
- set NDI to the value 0 and consider the NDI to have been toggled.
- if an uplink grant for this TTI has been received on the PDCCH for the UEs C-RNTI or Temporary C-RNTI; or
- if the uplink grant is for UEs C-RNTI and if the previous uplink grant delivered to the HARQ entity for the
same HARQ process was the uplink grant is for UEs C-RNTI and if the previous uplink grant delivered to
the HARQ entity for the same HARQ process was either an uplink grant received for the UEs Semi-
Persistent Scheduling C-RNTI or a configured uplink grant:
- else, if an uplink grant for this TTI has been received on the PDCCH for the UEs Semi-Persistent Scheduling C-
RNTI:
- else if the NDI in the received HARQ information is 0:
- if PDCCH contents indicate SPS release:
- clear the configured uplink grant (if any).
- else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 322
322
- store the uplink grant and the associated HARQ information as configured uplink grant;
- initialise (if not active) or re-initialise (if already active) the configured uplink grant to start in this TTI
and to recur according to rules in subclause 5.10.2;
- deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this
TTI.
- else, if an uplink grant for this TTI has been configured:
- deliver the configured uplink grant, and the associated HARQ information to the HARQ entity for this TTI.
NOTE 1: The period of configured uplink grants is expressed in TTIs.
NOTE 2: If the UE receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi
persistent scheduling C-RNTI requiring transmissions in the same UL subframe, the UE may choose to
continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling
C-RNTI.
NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH
transmission during a measurement gap, the UE processes the grant but does not transmit on UL-SCH.
[TS 36.321, clause 5.10]
When Semi-Persistent Scheduling is enabled by RRC, the following information is provided:
- Semi-Persistent Scheduling C-RNTI;
- Uplink Semi-Persistent Scheduling Interval semiPersistSchedIntervalUL and number of empty transmissions
before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the uplink;
- Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;
- Downlink Semi-Persistent Scheduling Interval semiPersistSchedIntervalDL and number of configured HARQ
processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is
enabled for the downlink;
When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or
configured assignment shall be discarded.
[TS 36.321, clause 5.10.2]
After a Semi-Persistent Scheduling uplink grant is configured, the UE shall:
- if twoIntervalsConfig is enabled by upper layer;
- set the Subframe_Offset according to Table 7.4-1.
- else:
- set Subframe_Offset to 0.
- consider that the grant recurs in each subframe for which:
- (10 * SFN +subframe) =[(10 * SFN
start time
+subframe
start time
) +N * semiPersistSchedIntervalUL +
Subframe_Offset * (N modulo 2)] modulo 10240, for all N>0.
Where SFN
start time
and subframe
start time
are the SFN and subframe, respectively, at the time the configured uplink grant
were (re-)initialised.
The UE shall clear the configured uplink grant immediately after implicitReleaseAfter number of consecutive new MAC
PDUs each containing zero MAC SDUs have been provided by the Multiplexing and Assembly entity, on the Semi-
Persistent Scheduling resource.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 323
323
NOTE 4: Retransmissions for Semi-Persistent Scheduling can continue after clearing the configured uplink grant.
[TS 36.321, clause 7.4]
Subframe_Offset values are presented in Table 7.4-1.
Table 7.4-1: Subframe_Offset values
TDD UL/DL configuration Position of initial Semi-Persistent grant Subframe_Offset value (ms)
0 N/A 0
1
Subframes 2 and 7 1
Subframes 3 and 8 -1
2
Subframe 2 5
Subframe 7 -5
3
Subframes 2 and 3 1
Subframe 4 -2
4
Subframe 2 1
Subframe 3 -1
5 N/A 0
6 N/A 0

[TS 36.331, clause 5.3.10.5]
The UE shall:
1>reconfigure the semi-persistent scheduling in accordance with the received sps-Config:
[TS 36.213, clause 8]

For TDD UL/DL configurations 1 and 6 and subframe bundling operation, the UE shall upon detection of a PDCCH
with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in subframe n-l
with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe n+k, with k
given in Table 8-2, according to the PDCCH and PHICH information.

Table 8-2 k for TDD configurations 0-6
TDD UL/DL
Configuration
DL subframe number n
0 1 2 3 4 5 6 7 8 9
0 4 6 4 6
1 6 4 6 4
2 4 4
3 4 4 4
4 4 4
5 4
6 7 7 7 7 5

[TS 36.213, clause 9.2]
A UE shall validate a Semi-Persistent Scheduling assignment PDCCH only if all the following conditions are met:
- the CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-
RNTI
- the new data indicator field is set to 0. In case of DCI formats 2 and 2A, the new data indicator field refers to
the one for the enabled transport block.
Validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-
1A.
If validation is achieved, the UE shall consider the received DCI information accordingly as a valid semi-persistent
activation or release.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 324
324
If validation is not achieved, the received DCI format shall be considered by the UE as having been received with a
non-matching CRC.
Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation
DCI format 0 DCI format 1/1A DCI format 2/2A
TPC command for
scheduled PUSCH
set to 00 N/A N/A
Cyclic shift DM RS set to 000 N/A N/A
scheme and
redundancy version
MSB is set to 0 N/A N/A
TDD: set to 0000
FDD: set to 000
TDD: set to 0000
scheme
N/A MSB is set to 0 For the enabled
transport block:
MSB is set to 0
Redundancy version N/A set to 00 For the enabled
transport block:
set to 00

Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH Validation
DCI format 0 DCI format 1A
TPC command for scheduled
PUSCH
set to 00

N/A
Cyclic shift DM RS set to 000

N/A
Modulation and coding scheme and
redundancy version
set to 11111 N/A
Resource block assignment and
hopping resource allocation
Set to all 1s N/A
TDD: set to 0000
Modulation and coding scheme N/A set to 11111
Redundancy version N/A set to 00
Resource block assignment N/A Set to all 1s

[TS 36.300, clause 11.1.2]
In addition, E-UTRAN can allocate a semi-persistent uplink resource for the first HARQ transmissions and potentially
retransmissions to UEs:
- RRC defines the periodicity of the semi-persistent uplink grant;
- PDCCH indicates whether the uplink grant is a semi-persistent one i.e. whether it can be implicitly reused in the
following TTIs according to the periodicity defined by RRC.
In the sub-frames where the UE has semi-persistent uplink resource, if the UE cannot find its C-RNTI on the
PDCCH(s), an uplink transmission according to the semi-persistent allocation that the UE has been assigned in the TTI
can be made. The network performs decoding of the pre-defined PRBs according to the pre-defined MCS. Otherwise, in
the sub-frames where the UE has semi-persistent uplink resource, if the UE finds its C-RNTI on the PDCCH(s), the
PDCCH allocation overrides the persistent allocation for that TTI and the UEs transmission follows the PDCCH
allocation, not the semi-persistent allocation. Retransmissions are either implicitly allocated in which case the UE uses
the semi-persistent uplink allocation, or explicitly allocated via PDCCH(s) in which case the UE does not follow the
semi-persistent allocation.
System Simulator:
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 325
325
UE:
None.
Preamble:
- The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDUs in UL of same
size.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 326
326
U - S Message
1 The SS transmits a DL MAC PDU containing
10 RLC SDUs on UM DRB.
<-- MAC PDU - -
2 The UE transmits a Scheduling Request,
indicating that loop back PDUs are ready for
transmission in UL RLC
--> (SR) - -
3 The SS transmits an UL Grant using UEs SPS
C-RNTI in SF-Num 4, NDI=0, allowing the UE
to transmit one loop back PDU per MAC PDU.
<-- (UL SPS Grant) - -
4 Check: Does the UE transmit a MAC PDU in
SF-Num 8 as per grant in step 3?
--> MAC PDU 1 P
5 The SS transmits a HARQ ACK <-- HARQ ACK - -
SF-Num 168(FDD)/167(TDD) as per grant in
step 3?
--> MAC PDU 1 P
8 The SS Transmits an UL Grant using UEs
SPS C-RNTI in SF-Num 244, NDI=0 and
allowing the UE to transmit two loop back
PDUs per MAC PDU.
--> MAC PDU 2 P
--> MAC PDU 2 F
step 8?
--> MAC PDU 2 P
SPS C-RNTI in SF-Num 484(FDD)/481(TDD),
NDI=1; the UL HARQ process is the same as
in step 12
15 Check: Does the UE transmit in SF-Num
488(FDD)/487(TDD) a MAC PDU as in step
12?
--> MAC PDU 3 P
--> MAC PDU 1 P
19 The SS Transmits an UL Grant using UEs C-
RNTI in SF-Num 724(FDD)/721(TDD);
allowing UE to transmit a MAC PDU containing
two RLC SDUs
<-- (UL Grant) - -
step 19?
--> MAC PDU 4 P
22 The SS transmits a PDCCH [for UL SPS
explicit release] using UEs SPS C-RNTI in SF-
Num 806 with NDI=0.
<-- PDCCH [for UL SPS explicit
release]
- -
SF-Num 888 as per grant in step 8 containing
zero MAC SDU?
--> MAC PDU 7 F
24 The SS transmits an UL Grant using UEs SPS
C-RNTI in SF-Num 969, NDI=0, transmit one
loop back PDU per MAC PDU
SF-Num 973 as per grant in step 24
containing zero MAC SDU?
--> MAC PDU 1 P
27 Check: Does the UE transmit a MAC PDU in --> MAC PDU 1 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 327
327
SF-Num 1133(FDD)/1132(TDD) as per grant
in step 24 containing zero MAC SDU?
--> MAC PDU 6 F
SPS C-RNTI in SF-Num 1374, NDI=0,
transmit one loop back PDU per MAC PDU.
SF-Num 1378 as per grant in step 30
containing zero MAC SDU?
--> MAC PDU 1 P
33 SS Transmits RRCConnectionReconfiguration
to disable SPS-ConfigurationUL.
<-- - - -
34 The UE transmits
--> - - -
35 The SS transmits a DL MAC PDU containing 1
RLC SDU
<-- MAC PDU - -
36 The UE transmits Scheduling request,
indicating loop back PDUs ready for
transmission in UL RLC
--> (SR) - -
SF-Num 1538(FDD)/1537(TDD) as per grant
in step 30?
--> MAC PDU 5 F
38 SS transmits an UL Grant <-- (UL Grant) - -
39 The UE transmits a MAC PDU as per grant in
step 38.
--> MAC PDU - -

Table 7.1.4.2.3.3-1: RRCConnectionReconfiguration. RadioResourceConfigDedicated (Preamble)
semiPersistSchedC-RNTI FFF0H
sps-ConfigurationDL Not Present
sps-ConfigurationUL::=CHOICE{
enable SEQUENCE {
semiPersistSchedIntervalUL sf160 160 Subframe
implicitReleaseAfter e2
p0-Persistent Not Present
twoIntervalConfig Not Present FDD
twoIntervalConfig true TDD
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 328
328
Table 7.1.4.2.3.3-2: RRCConnectionReconfiguration. RadioResourceConfigDedicated (step 33 of table
7.1.4.2.3.2-1)
semiPersistSchedC-RNTI Not Present
sps-ConfigurationDL Not Present
sps-ConfigurationUL::=CHOICE{
disable NULL
}
}
}

7.1.4.3 Logical channel prioritization handling
(1)
ensure that {
when { sending data on the uplink }
then { UE serves the logical channels according to their priority and configured PBR }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 5.4.3.1.
[TS 36.321, clause 5.4.3.1]
The Logical Channel Prioritization procedure is applied when a new transmission is performed.
RRC controls the scheduling of uplink data by signalling for each logical channel: priority where an increasing priority
value indicates a lower priority level, prioritisedBitRate which sets the Prioritized Bit Rate (PBR), bucketSizeDuration
which sets the Bucket Size Duration (BSD).
The UE shall maintain a variable Bj for each logical channel j. Bj shall be initialized to zero when the related logical
channel is established, and incremented by the product PBR TTI duration for each TTI, where PBR is Prioritized Bit
Rate of logical channel j. However, the value of Bj can never exceed the bucket size and if the value of Bj is larger than
the bucket size of logical channel j, it shall be set to the bucket size. The bucket size of a logical channel is equal to
PBR BSD, where PBR and BSD are configured by upper layers.
The UE shall perform the following Logical Channel Prioritization procedure when a new transmission is performed:
- The UE shall allocate resources to the logical channels in the following steps:
- Step 1: All the logical channels with Bj >0 are allocated resources in a decreasing priority order. If the PBR
of a radio bearer is set to infinity, the UE shall allocate resources for all the data that is available for
transmission on the radio bearer before meeting the PBR of the lower priority radio bearer(s);
- Step 2: the UE shall decrement Bj by the total size of MAC SDUs served to logical channel j in Step 1
NOTE: The value of Bj can be negative.
- Step 3: if any resources remain, all the logical channels are served in a strict decreasing priority order
(regardless of the value of Bj) until either the data for that logical channel or the UL grant is exhausted,
whichever comes first. Logical channels configured with equal priority should be served equally.
- The UE shall also follow the rules below during the scheduling procedures above:
- the UE should not segment an RLC SDU (or partially transmitted SDU or retransmitted RLC PDU) if the
whole SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 329
329
- if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill
the grant as much as possible;
- UE should maximise the transmission of data.
The UE shall not transmit data for a logical channel corresponding to a radio bearer that is suspended (the conditions for
when a radio bearer is considered suspended are defined in [8]).
For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in
decreasing order:
- MAC control element for C-RNTI or data from UL-CCCH;
- MAC control element for BSR, with exception of BSR included for padding;
- MAC control element for PHR;
- data from any Logical Channel, except data from UL-CCCH;
- MAC control element for BSR included for padding.
System Simulator:
- Cell 1
UE:
None
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.1.4.3.3.1-2
applicable for the configured UM DRBs and table 7.1.4.3.3.1-3 for SR configuration.
- The 3 UM DRBs are configured according to table 7.1.4.3.3.1-1.
Table 7.1.4.3.3.1-1: Priority, PBR and Bucket Delay settings
DRB priority prioritizedBitRate
(kbytes/s)
bucketSizeDuration
(ms)
DRB1 6 8 100
DRB2 7 16 100
DRB3 8 32 100

Table 7.1.4.3.3.1-2: PDCP Settings
Parameter Value
Discard_Timer ms1500

Table 7.1.4.3.3.1-3: SchedulingRequest-Config
dsr-TransMax n16

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 330
330
U - S Message
- EXCEPTION: Steps 0 to 4 are run 4 times
using the parameters specified for each run in
table 7.1.4.3.3.2-3.
- - - -
0 Void - - - -
1 The SS transmits N1 320-octet RLC SDUs on
DRB1, N2 320-octet RLC SDUs on DRB2, and
N3 320-octet RLC SDUs on DRB3.
<-- (RLC SDUs) - -
- EXCEPTION: In parallel to the event described
in step 2 the events specified in Table
7.1.4.3.3.2-2 shall take place.
- - - -
Allocation Type 2. 150 ms after Step 1 (Note1),
for a duration of T2, the SS transmits an UL
grant of D octets every T1.
<-- (UL grants) - -
3 Check: are the total number of octets of the UL
RLC SDUs received at the SS for each DRB
as follows?

- the total number of octets received for DRB1
is D1 octets +/- 10%

- - 1 P
4 The SS re-establishes the RLC for each RB at
the UE by sending an
RRCConnectionReconfiguration for intra-cell
handover with SR configuration set as per
Table 7.1.4.3.3.1-3.
- - - -
Note 1: This wait time will ensure that a) all octets have been completely received by the UE on all 3 DRBs before
the first UL grant is received and b) the Bjs for each logical channel have reached their maximum value ie
the bucket size of the corresponding logical channel before the first UL grant is received.

U - S Message
1 Check: Does the UE transmit the RLC SDUs
back to the SS?
--> - 1 P

Table 7.1.4.3.3.2-3: Test parameter values
Parameter First run Second run Third run Fourth run
N1 (SDUs) 13 13 7 104
N2 (SDUs) 25 25 50 25
N3 (SDUs) 50 50 50 50
D (octets) 1143 573 1143 1143
T1 (ms) 20 20 20 10
T2 (ms) 500 700 500 500
D1 (octets) 4160 4160 2240 33000 (Note 1)
D2 (octets) 8000 8000 10260 (Note 1) 8000
D3 (octets) 16000 7790 (Note 1) 16000 16000
Note 1: It is calculated from the following equation for the case of the least header size.
(D1 +D2 +D3) =(D - 3) * T2 / T1

NOTE: the numbers above and the test procedure assume that the UE has a loopback buffer of at least 57280
octets.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 331
331
None.
7.1.4.4 Correct handling of MAC control information / Scheduling requests and
PUCCH
(1)

ensure that {
when { PUCCH is configured and UE has UL data available for transmission and UE has no UL-SCH
resources available and SR_COUNTER is less than dsr-TransMax }
then { the UE transmits a SR on every available PUCCH until resources are granted }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state and has pending SR(s) }
ensure that {
when { UE receives an UL grant for a new transmission }
then { UE cancels all pending SR(s) }
}

[TS 36.321, clause 5.4.4]
The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.
When an SR is triggered, it shall be considered as pending until it is cancelled.
If an SR is triggered and there is no other SR pending, the UE shall set the SR_COUNTER to 0.
As long as one SR is pending, the UE shall for each TTI:
- if no UL-SCH resources are available for a transmission in this TTI:
- if the UE has no valid PUCCH resource for SR configured in any TTI: initiate a Random Access procedure
(see subclause 5.1) and cancel all pending SRs;
- else if the UE has a valid PUCCH resource for SR configured for this TTI and if this TTI is not part of a
measurement gap:
- if SR_COUNTER <dsr-TransMax:
- increment SR_COUNTER by 1;
- instruct the physical layer to signal the SR on PUCCH;
- else:
- clear any configured downlink assignments and uplink grants;
- initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs.
- else if UL-SCH resources for new transmission are granted in this TTI, cancel all pending SR(s).7.1.4.4.3 Test
description
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 332
332
System Simulator:
- - Cell 1
7.1.4.4.3.3-1
UE:
None.
Preamble:
U - S Message
1 The SS transmits a MAC PDU containing 10
MAC SDUs each containing a RLC SDU
<-- MAC PDU (containing 10 MAC
SDUs)
- -
- EXCEPTION: Step 2 runs in parallel with
behaviour in table 7.1.4.4.3.2-2.
- - - -
2 Check: Does the UE transmit 6 Scheduling
Requests separately on 6 consecutively
available PUCCHs? (Note 1)
--> (SR) 1 P
Allocation Type 3. The SS transmits an UL
grant to allocate UL-SCH resources that are
enough to transmit MAC PDU containing 10
MAC SDUs
<-- (UL Grant ) - -
containing 10 RLC PDUs?
--> MAC PDU (containing 10 MAC
SDUs)
1 P
5 Check: 1 second does the UE transmit a
Scheduling Request in the next 100ms?
--> (SR) 1,2 F
Note 1: The UE repeats the scheduling requests on every available PUCCH as long as SR_COUNTER <dsr-
TransMax and there is UL data available for transmission and there are no resources available to transmit
it. At the reception of first Scheduling Request from the UE, SS will be scheduled to transmit a grant after
100ms. Hence SS will receive 6 Scheduling Requests as sr-ConfigIndex =30.

U - S Message
1 Check: Does the UE transmit a MAC PDU? --> MAC PDU 1 F

Table 7.1.4.4.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration
in preamble
SchedulingRequest-Configuration::=CHOICE {
enable SEQUENCE {
dsr-TransMax n64
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 333
333
None.
7.1.4.5 Correct handling of MAC control information / Scheduling requests and
random access procedure
(1)
with { The UE is in E-UTRA RRC_CONNECTED state and no PUCCH resource for SR is configured }
ensure that {
when { UE has UL data available for transmission, UE has no UL-SCH resources available and time
alignment timer expires }
then { the UE initiates the random access procedure }
}

(2)
with { The UE in E-UTRA RRC_CONNECTED state )
ensure that {
when { PUCCH Configured and UE has UL data available for transmission and UE has no UL-SCH
resources available and SR_COUNTER becomes equal to dsr-TransMax }
then { the UE transmits a PRACH Preamble to initiate a Random Access procedure }

:}
References: The conformance requirements covered in the current TC are specified in: TS 36.321 , clause 5.4.4.
[TS 36.321 clause 5.4.4]
When an SR is triggered, it shall be considered as pending until it is cancelled.
If an SR is triggered and there is no other SR pending, the UE shall set the SR_COUNTER to 0.
As long as one SR is pending, the UE shall for each TTI:
- if no UL-SCH resources are available for a transmission in this TTI:
- if the UE has no valid PUCCH resource for SR configured in any TTI: initiate a Random Access procedure
(see subclause 5.1) and cancel all pending SRs;
- else if the UE has a valid PUCCH resource for SR configured for this TTI and if this TTI is not part of a
measurement gap:
- if SR_COUNTER <dsr-TransMax:
- increment SR_COUNTER by 1;
- instruct the physical layer to signal the SR on PUCCH;
- else:
- clear any configured downlink assignments and uplink grants;
- initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs.- else if UL-SCH resources
for new transmission are granted in this TTI, cancel all pending SR(s).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 334
334
System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 335
335
U - S Message
Timing Advance Command MAC Control
Element, but esdo not send any subsequent
alignments.
<-- MAC PDU (Timing Advance
Command)
- -
1A The SS transmits a MAC PDU containing a
MAC SDU
<-- MAC PDU (MAC SDU) - -
- EXCEPTION: Step 2B is repeated less than 64
times (dsr-TransMax)
- - - -
2B The UE may transmit Scheduling Requests
before time alignment timer expires. The SS
shall not respond to the Scheduling Requests
in this step. (Note 5)
--> (SR) - -
PRACH? (Note 1)
3 The SS transmits a Random Access Response
including an UL grant to enable UE to transmit
C-RNTI MAC Control Element and the MAC
SDU as received in step 1A.
4 The UE transmit a MAC PDU including a C-
RNTI MAC Control Element and a MAC SDU.
(Note 2)
--> MAC PDU (C-RNTI control
element, MAC SDU)
- -
5 The SS sends PDCCH transmission for UE C-
RNTI
<-- - - -
5A The SS transmits
RRCConnectionReconfiguration containing a
radioResourceConfiguration with a physical
channel reconfiguration
<-- - -
- EXCEPTION: Steps 5A1 to 5A4 are optionally
executed. (Note 6)
- - -
5A
1
The UE transmits a preamble on PRACH.
(Note 6)
--> (PRACH Preamble) - -
5A
2
The SS transmits a Random Access Response
including an UL grant of 7 bytes. (Note 7)
5A
3
The UE transmit a MAC PDU including a C-
RNTI MAC Control Element
--> - - -
5A
4
The SS sends PDCCH transmission for UE C-
RNTI
<-- - - -
5B The UE transmits a Scheduling Request on
PUCCH. (Note 8)
--> (SR) - -
5C The SS transmits an UL grant to enable UE to
transmit the
message. (Note 9)
<-- (UL Grant) - -
5D The UE transmits
message. (Note 6)
-->--> - -
5E Void - - - -
6 The SS ignores any Scheduling Requests from
the UE.
- - - -
MAC SDU containing a RLC SDU
<-- MAC PDU MAC SDU) - -
- EXCEPTION: Step 8 shall be repeated 8
times.
- - - -
8 The UE transmits a Scheduling Request on
PUCCH (Note 3)
--> (SR) - -
PRACH? (Note 4)
10 The SS transmits a Random Access Response
including an UL grant to enable UE to transmit
C-RNTI MAC Control Element and the MAC
SDU as received in step 7.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 336
336
11 The UE transmit a MAC PDU including a C-
RNTI MAC Control Element and a MAC SDU.
(Note 2)
--> MAC PDU (C-RNTI control
element, MAC SDU)
- -
12 The SS sends PDCCH transmission for UE C-
RNTI
<-- - - -
Note 1: When UL time alignment timer expires in the UE then "UL synchronization" is lost and the UE initiates a
Random Access Procedure.
Note 2: The UE transmission of the MAC PDU ensures that the random access procedure was successful.
Note 3: The UE repeats the scheduling requests as long as SR_COUNTER <dsr-TransMax and there is data in
the transmission buffer and there are no resources available to transmit it.
Note 4: Reception of PRACH Preamble by the SS verifies that UE has initiated a Random Access procedure
triggered by SR_COUNTER having reached dsr-TransMax.
Note 5: In step 2B, SR repetition of 63 times (dsr-TransMax (64)) will take atleast 63*20 =1260 ms which is much
larger than TA timer 750ms.
Note 6: RLC status PDU may trigger the UE to transmit PRACH Preamble.
Note 7: UL grant of 56 bits (ITBS=4, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to
transmit C-RNTI MAC Control Element but not allowing the UE to transmit RRCConnectionReconfiguration
Complete.
Note 8: If RRCConnectionReconfigurationComplete was not ready for transmission in step 5A3 then SR is
triggered when RRC message arrives in the transmission buffer. Otherwise
(RRCConnectionReconfigurationComplete was ready for the transmission in step 5A3) the SR is triggered
because expiry of the retxBSR-Timer.
Note 9: STATUS PDU is included if it was not transmitted by the UE in step 5A3.

Table 7.1.4.5.3.3-1: SchedulingRequest-Config to be used in RRCConnectionReconfiguration
( preamble, Table 7.1.4.5.3.2-1)
SchedulingRequest-Config-DEFAULT::=CHOICE {
setup SEQUENCE {
dsr-TransMax n64
}
}

Table 7.1.4.5.3.3-2: RRCConnectionReconfiguration (step 5A, Table 7.1.4.5.3.2-1)
rrc-TransactionIdentifier RRC-
TransactionIdentifier-DL

c1 CHOICE{
measConfig Not present
mobilityControlInfo Not present
dedicatedInfoNASList Not present
radioResourceConfigDedicated RadioResourceConfigDe
dicated-Step5a

securityConfigHO Not present
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 337
337
Table 7.1.4.5.3.3-3: RadioResourceConfigDedicated-Step5A (Table 7.1.4.5.3.3-2)
RadioResourceConfigDedicated-HO ::=SEQUENCE
{

srb-ToAddModList Not present
drb-ToAddModList Not present
drb-ToReleaseList Not present
mac-MainConfig Not present
sps-Config Not present
physicalConfigDedicated PhysicalConfigDedicated-
Step5a

}

Table 7.1.4.5.3.3-4: PhysicalConfigDedicated-Step5A (Table 7.1.4.5.3.3-3)
PhysicalConfigDedicated-DEFAULT ::=SEQUENCE {
pdsch-ConfigDedicated Not present
pucch-ConfigDedicated Not present
pusch-ConfigDedicated Not present
uplinkPowerControlDedicated Not present
tpc-PDCCH-ConfigPUCCH Not present
tpc-PDCCH-ConfigPUSCH Not present
cqi-ReportConfig CQI-ReportConfig-
DEFAULT using
condition
CQI_PERIODIC
See subclause
4.6.3 of 36.508

soundingRS-LU-ConfigDedicated SoundingRS-ULl-
ConfigDedicated-
DEFAULT
See subclause
4.6.3 of 36.508

antennaInfo Not present
schedulingRequestConfig SchedulingRequest-
Config- Config-Step5a

}

Table 7.1.4.5.3.3-5: SchedulingRequest-Config-Step5A (Table 7.1.4.5.3.3-4)
SchedulingRequest-Config::=CHOICE {
enable SEQUENCE {
dsr-TransMax n8
}
}

7.1.4.6 Correct handling of MAC control information / Buffer status / UL data arrive in
the UE Tx buffer and retransmission of BSR / Regular BSR
(1)
with ( UE in E-UTRA RRC_CONNECTED state )
ensure that {
when { UL data arrives in the UE transmission buffer and the data belongs to a logical channel
with higher priority than those for which data is already avialble for transmission and the new
logical channel and the existing logical channels belongs to the different LCG }
then { UE Reports a Long Buffer Status Reporting (BSR) }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 338
338
(2)
ensure that {
when { UL data arrives in the UE transmission buffer and there is no data available for
transmission for any of the logical channels which belong to a LCG }
then { UE Reports a Short Buffer Status Reporting (BSR) }
}

(3)
ensure that {
when { UL data arrives in the UE transmission buffer and the data belongs to a logical channel
with higher priority than those for which data is already avialalble for transmission and the new
logical channel and existing logical channels belong to the same LCG }
then { UE Reports a Short Buffer Status Reporting (BSR) }
}

(4)
ensure t hat {
when{RETX_BSR_TIMER expires and only one LCG has data available for transmission }
then { UE triggers a regular BSR and Reports a Short Buffer Status Reporting ( BSR)}
}
(5)
wi th (UE in E-UTRA RRC_CONNECTED stat e)
ensure that {
when { a Regular BSR has been triggered and UE has pending data for tranmission and UE has only
resources to send either BSR report or data }
then { UE transmits the BSR report }
}

(6)
ensure that {
when { UE determines that a BSR has been triggered since the last transmission of a BSR and UE has
no UL resources allocated for new transmission for this TTI }
then { UE transmits a scheduling request }
}
(7)
with (UE in E-UTRA RRC_CONNECTED state)
ensure that {
when { a Regular BSR has been triggered and UE has pending data on several logical channels for
tranmission and UE has only UL resources to send all pending data available for transmission, but UL
grant is not sufficient to additionally accommodate the BSR MAC control element}
then { UE cancels the triggered BSR report and transmits the UL data}
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1, 5.4.5,
6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323 clause 4.5.
[TS 36.321 clause 5.4.3.1]
decreasing order:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 339
339
[TS 36.321 clause 5.4.4]
[TS 36.321 clause 5.4.5]
The Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data
available for transmission in the UL buffers of the UE. RRC controls BSR reporting by configuring the two timers
periodicBSR-Timer and retxBSR-Timer and by, for each logical channel, optionally signalling logicalChannelGroup
which allocates the logical channel to an LCG [8].
For the Buffer Status reporting procedure, the UE shall consider all radio bearers which are not suspended and may
consider radio bearers which are suspended.
A Buffer Status Report (BSR) shall be triggered if any of the following events occur:
- UL data, for a logical channel which belongs to a LCG, becomes available for transmission in the RLC entity or
in the PDCP entity (the definition of what data shall be considered as available for transmission is specified in
[3] and [4] respectively) and either the data belongs to a logical channel with higher priority than the priorities of
the logical channels which belong to any LCG and for which data is already available for transmission, or there
is no data available for transmission for any of the logical channels which belong to a LCG, in which case the
BSR is referred below to as "Regular BSR";
- UL resources are allocated and number of padding bits is equal to or larger than the size of the Buffer Status
Report MAC control element plus its subheader, in which case the BSR is referred below to as "Padding BSR";
- retxBSR-Timer expires and the UE has data available for transmission for any of the logical channels which
belong to a LCG, in which case the BSR is referred below to as "Regular BSR";
- periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".
For Regular and Periodic BSR:
- if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long
BSR;
- else report Short BSR.
For Padding BSR:
- if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller
than the size of the Long BSR plus its subheader:
- if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report
Truncated BSR of the LCG with the highest priority logical channel with data available for transmission;
- else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader, report
Long BSR.
If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:
- if the UE has UL resources allocated for new transmission for this TTI:
- instruct the Multiplexing and Assembly procedure to generate a BSR MAC control element;
- start or restart periodicBSR-Timer except when the BSR is a Truncated BSR;
- start or restart retxBSR-Timer.
- else if a Regular BSR has been triggered:
- a Scheduling Request shall be triggered.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 340
340
A MAC PDU shall contain at most one MAC BSR control element, even when multiple events trigger a BSR by the
time a BSR can be transmitted in which case the Regular BSR and the Periodic BSR shall have precedence over the
padding BSR.
The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on UL-SCH.
All triggered BSRs shall be cancelled in case the UL grant can accommodate all pending data available for transmission
but is not sufficient to additionally accommodate the BSR MAC control element plus its subheader. All triggered BSRs
shall be cancelled when a BSR is included in a MAC PDU for transmission.
[TS 36.321 clause 6.1.2]
MAC control elements are always placed before any MAC SDU.
[TS 36.321 clause 6.1.3.1]
Buffer Status Report (BSR) MAC control elements consist of either:
- Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure
6.1.3.1-1); or
- Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2).
The BSR formats are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1.-1.
The fields LCG ID and Buffer Size are defined as follow:
- LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is
being reported. The length of the field is 2 bits;
- Buffer Size: The Buffer Size field identifies the total amount of data available across all logical channels of a
logical channel group after the MAC PDU has been built. The amount of data is indicated in number of bytes. It
shall include all data that is available for transmission in the RLC layer and in the PDCP layer; the definition of
what data shall be considered as available for transmission is specified in [3] and [4] respectively. The size of
the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 6 bits.
The values taken by the Buffer Size field are shown in Table 6.1.3.1-1.
Buffer Size LCG ID Oct 1

Figure 6.1.3.1-1: Short BSR and Truncated BSR MAC control element

Buffer Size #0
Buffer
Size #1
Buffer Size #1 Buffer Size #2
Buffer
Size #2
Buffer Size #3
Oct 1
Oct 2
Oct 3

Figure 6.1.3.1-2: Long BSR MAC control element

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 341
341
Table 6.1.3.1-1: Buffer size levels for BSR
Index Buffer Size (BS) value [bytes] Index Buffer Size (BS) value [bytes]
0 BS =0 32 1132 <BS <=1326
1 0 <BS <=10 33 1326 <BS <=1552
2 10 <BS <=12 34 1552 <BS <=1817
3 12 <BS <=14 35 1817 <BS <=2127
4 14 <BS <=17 36 2127 <BS <=2490
5 17 <BS <=19 37 2490 <BS <=2915
6 19 <BS <=22 38 2915 <BS <=3413
7 22 <BS <=26 39 3413 <BS <=3995
8 26 <BS <=31 40 3995 <BS <=4677
9 31 <BS <=36 41 4677 <BS <=5476
10 36 <BS <=42 42 5476 <BS <=6411
11 42 <BS <=49 43 6411 <BS <=7505
12 49 <BS <=57 44 7505 <BS <=8787
13 57 <BS <=67 45 8787 <BS <=10287
14 67 <BS <=78 46 10287 <BS <=12043
15 78 <BS <=91 47 12043 <BS <=14099
16 91 <BS <=107 48 14099 <BS <=16507
17 107 <BS <=125 49 16507 <BS <=19325
18 125 <BS <=146 50 19325 <BS <=22624
19 146 <BS <=171 51 22624 <BS <=26487
20 171 <BS <=200 52 26487 <BS <=31009
21 200 <BS <=234 53 31009 <BS <=36304
22 234 <BS <=274 54 36304 <BS <=42502
23 274 <BS <=321 55 42502 <BS <=49759
24 321 <BS <=376 56 49759 <BS <=58255
25 376 <BS <=440 57 58255 <BS <=68201
26 440 <BS <=515 58 68201 <BS <=79846
27 515 <BS <=603 59 79846 <BS <=93479
28 603 <BS <=706 60 93479 <BS <=109439
29 706 <BS <=826 61 109439 <BS <=128125
30 826 <BS <=967 62 128125 <BS <=150000
31 967 <BS <=1132 63 BS >150000

[TS 36.321 clause 6.2.1]
Index LCID values
00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding

[TS 36.323 clause 4.5]
For the purpose of MAC buffer status reporting, the UE shall consider the following as data available for transmission
in the PDCP layer:
For SDUs for which no PDU has been submitted to lower layers:
- the SDU itself, if the SDU has not yet been processed by PDCP, or
- the PDU (control or data) if the SDU has been processed by PDCP.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 342
342
System Simulator :
- Cell 1
7.1.4.6.3.3-1
UE:
None.
Preamble:
- 3 AM DRBS are configured with the following parameters:
Table 7.1.4.6.3.1-1: Logical Channel Configuration Settings
Parameter Value DRB1 Value DRB2 Value DRB3
LogicalChannel-Identity 3 4 5
Priority 8 7 6
prioritizedBitRate 0 kB/s 0 kB/s 0 kB/s
logicalChannelGroup 2 (LCG ID#2) 2 (LCG ID#2) 1 (LCG ID#1)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 343
343
U - S Message
- - - -
2 The SS transmits a MAC PDU containing two
RLC SDUs of size 10 bytes on LC 3
<-- MAC PDU (2 RLC SDUs on LC 3) - -
3 SS allocates an UL Grant of 32 bits. (Note 1) <-- (UL Grant, 32 bits) - -
4 Check: Does the UE transmit a Short BSR with
LCG ID field set to 2 and Buffer size field
set to value 6 or bigger? (Note 2)
--> MAC PDU (MAC Short BSR (LCG
ID=2, Buffer Size=6 or bigger))
2,5 P
5 Wait for retxBSR-Timer expiry on UE side. - - - -
request?
--> (SR) 6 P
7 The SS respond to the scheduling request in
step 6 by an UL Grant of 32 bits. (Note 1)
<-- (UL Grant, 32 bits) - -
LCG ID field set to 2 and Buffer size field
4,5 P
request?
--> (SR) 6 P
step 10 by an UL Grant of 32 bits. (Note 1)
LCG ID field set to 2 and Buffer size#1 field
3,5 P
request?
--> (SR) 6 P
step 14 by one UL Grant of 32 bits. (Note 1)
16 Check: Does the UE transmit a Long BSR with
Buffer size#1 field set to value 1, Buffer
size#2 field set to value 8 or bigger? (Note 3)
--> MAC PDU (MAC Long BSR
(Buffer size#1=1 or bigger, Buffer
size#2=8 or bigger)
1,5 P
17 Wait for retxBSR-Timer expiry on the UE side. - - -
request?
--> (SR) 6 P
19 SS allocates an UL Grant of 424 bits. (Note 4) <-- (UL Grant, 424 bits) - -
including five RLC SDUs and not including any
BSR? (Note 5)
--> MAC PDU (SDU subheader, AMD
PDU header and 2 RLC SDUs on
LC 3, SDU subheader, AMD PDU
header and 1 RLC SDUs on LC 4,
SDU subheader, AMD PDU
header and 2 RLC SDUs on LC
5)
7 P
Note 1: 32 bits enables UE to transmit a MAC PDU with a MAC BSR header and a Short BSR (1 bytes) or a Long
BSR (3 byte).
Note 2: UE triggers a Short BSR of type "Regular BSR" to report buffer status for one LCG for that TTI. The UE
should not send any of the received RLC SDUs (segmented) due to Regular BSR has higher priority than
U-plane logical channels.
Note 3: UE triggers and transmit a Long BSR of type "Regular BSR". The UL grant would be enough for UE to
transmit one RLC SDU as received in step 8, but Regular BSR has higher priority than U-plane logical
channels.
Note 4: The UE has 38 bytes of user data (received in steps 2, 9 and 13) in the transmission buffer. 424 bits
enables UE to transmit user data in MAC PDU with 2 bytes SDU subheader for LC 3, 2 bytes SDU
subheader for LC 4 and 1 byte SDU subheader for LC 5, 24 bytes MAC SDU for LC 3 (2 RLC SDUs, 10
bytes each and 4 bytes AMD PDU header), 12 bytes MAC SDU for LC 4 (1 RLC SDU, 10 bytes and 2
bytes AMD PDU header, 12 bytes MAC SDU for LC 5 (2 RLC SDUs, 4 bytes each and 4 bytes AMD PDU
header)) equals to 424 bits (53 bytes).
Note 5 The MAC SDUs for the different logical channels may be in any order in the MAC PDU.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 344
344
c1 CHOICE{
Explicit SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx n5
periodicBSR-Timer Infinity
retxBSR-Timer sf320
ttiBundling FALSE
}
}
}
}
}
}
}
}

7.1.4.7 Correct handling of MAC control information / Buffer Status / UL resources
are allocated / Padding BSR
(1)
ensure that {
when { UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size
of a Short BSR plus its subheader but smaller than the size of a Long BSR plus its subheader and the
UE has available data for transmission from more than one LCG in the TTI where the BSR is
transmitted }
then { UE reports a Truncated BSR of the LCG with the highest priority logical channel with data
available for transmission }
}

(2)
ensure that {
when { UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size
of a Short BSR plus its subheader but smaller than the size of a Long BSR plus its subheader and the
UE has available data for transmission form only one LCG in the TTI where the BSR is transmitted }
then { UE reports a Short BSR }
}

(3)
ensure that {
when{ UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size of
a Long BSR plus its subheader }
then { UE reports a long BSR }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1, 5.4.5,
6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323, clause 4.5.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 345
345
[TS 36.321 clause 5.4.3.1]
decreasing order:
[TS 36.321 clause 5.4.5]
...
- UL resources are allocated and number of padding bits is equal to or larger than the size of the Buffer Status
Report MAC control element plus its subheader, in which case the BSR is referred below to as "Padding BSR";
...
For padding BSR:
- if the number of padding bits is equal to or larger than the size of the Short BSR plus its sub header but smaller
than the size of the Long BSR plus its subheader:
- if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report
Truncated BSR of the LCG with the highest priority logical channel with data available for transmission;
- else if the number of padding bits is equal to or larger than the size of the Long BSR plus its sub header, report
Long BSR.
- start or restart the periodicBSR-Timer except when the BSR is a Truncated BSR;
- else if a Regular BSR has been triggered:
- a Scheduling Request shall be triggered.
padding BSR.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 346
346
[TS 36.321 clause 6.1.2]
[TS 36.321 clause 6.1.3.1]
6.1.3.1-1); or
The BSR formats are identified by MAC PDU sub headers with LCIDs as specified in table 6.2.1.-2.


Buffer Size #0
Buffer
Size #1
Buffer
Size #2
Buffer Size #3
Oct 1
Oct 2
Oct 3

[TS 36.321 clause 6.2.1]
Index LCID values
00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding

[TS 36.323 clause 4.5]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 347
347
For the purpose of MAC buffer status reporting, the UE shall consider PDCP Control PDUs, as well as the following as
data available for transmission in the PDCP layer:
- the PDU (control or data) if the SDU has been processed by PDCP.
System Simulator:
- Cell 1
7.1.4.7.3.3-1
UE:
None.
Preamble:
- 2 AM DRBS are configured with the parameters specified in table 7.1.4.7.1-1.
Table 7.1.4.7.1-1: Logical Channel Configuration Settings
Parameter DRB1 DRB2
LogicalChannel-Identity 3 4
Priority 7 6
prioritizedBitRate 0kbs 0kbs
logicalChannelGroup 2 (LCG ID#2) 1 (LCG ID#1)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 348
348
U - S Message
- - - -
- EXCEPTION: Step 2 shall be repeated for 2
times
- - - -
2 The SS transmits a MAC PDU including an
RLC SDU of size 12 bytes on logical channel
4.
<-- MAC PDU (RLC SDU on LC 4) -
3 The SS transmits a MAC PDU including an
RLC SDU of size 12 bytes on logical channel
3.
<-- MAC PDU (RLC SDU on LC 3) - -
4 UE transmits a Scheduling Request on
PUCCH.
--> (SR) - -
5 The SS sends an uplink grant of size 32 bits.
(Note 1)
<-- (UL grant) - -
6 The UE transmit a Long BSR report --> MAC PDU (Long BSR header
(LCID=11110), Long BSR)
- -
Allocation Type 3. The SS sends an uplink
grant of size 136 bits. (Note 2)
<-- (UL grant) - -
8 Check: Does UE transmit a MAC PDU
containing an RLC SDU and a Truncated BSR
indicating pending data (Buffer size field >0)
for logicalChannelGroup 1 (LCG ID field set to
01)?
--> MAC PDU (Truncated BSR
header (LCID=11100), Truncated
BSR(LCG ID =01, Buffer
size>0), RLC SDU)
1 P
9 Void - - - -
grant of size 136 bits
(Note 2)
<-- (UL grant) - -
containing an RLC SDU and with a Short BSR
indicating pending data (Buffer size field >0)
for logicalChannelGroup 2 (LCG ID field
=10)?
--> MAC PDU (Short BSR
header(LCID=11101), Short
BSR(LCG ID =10,Buffer size>0),
RLC SDU)
2 P
12 Void - - - -
13 Void - - - -
<-- (UL grant) - -
containing a RLC SDU and a Long BSR?
--> MAC PDU (Long BSR header
(LCID=11110), Long BSR), RLC
SDU)
3 P
Note 1: SS transmit an UL grant of 32 bits (I
TBS
=0, N
PRB
=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a
Regular BSR triggered by the new data received logicalChannelGroup 1 and 2 in steps 2 and 3. This to
enable testing of Padding BSR which has lower priority than Regular BSR.
Note 2: UL grant of 136 bits (I
TBS
=9, N
PRB
=1, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU
padding bits will be equal to or larger than the size of Short/Truncated BSR and smaller than Long BSR.
RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for
MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of
Short BSR/Truncated BSR is one byte, i.e. setting UL grant to 17 bytes (136 bits) enable UE to include
Short/Truncated BSR.
TBS
=0, N
PRB
=6, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU
padding bits will be equal to or larger than the size of Long BSR. RLC SDU size is 12 bytes, size of AMD
PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID
for last sub header and 1 byte for BSR sub-header) and size of Long BSR is 3 bytes, i.e. setting UL grant
to 19 bytes (152 bits) enable UE to include padding Long BSR.

None
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 349
349
7.1.4.8 Correct handling of MAC control information / Buffer status / Periodic BSR
timer expires
(1)
ensure that {
when { periodicBSR-Timer expires and more than one LCG has buffered data in a TTI }
then { UE triggers a Periodic BSR and reports Long BSR }
}

(2)
ensure that {
when { periodicBSR-Timer expires and one LCG has buffered data in a TTI }
then { UE triggers a Periodic BSR and reports Short BSR and restarts the periodicBSR-Timer}
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.5, 6.1.2,
6.1.3.1 and 6.2.1; TS 36.323 clause 4.5.
[TS 36.321 clause 5.4.5]
...
- periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".
For Regular and Periodic BSR:
- if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long
BSR;
...
- start or restart the periodicBSR-Timer except when the BSR is a Truncated BSR;
padding BSR.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 350
350
[TS 36.321 clause 6.1.2]
[TS 36.321 clause 6.1.3.1]
6.1.3.1-1); or
The BSR formats are identified by MAC PDU sub headers with LCIDs as specified in table 6.2.1.-2.


Buffer Size #0
Buffer
Size #1
Buffer
Size #2
Buffer Size #3
Oct 1
Oct 2
Oct 3


[TS 36.321 clause 6.2.1]
Table: 6.2.1-2 Values of LCID for UL-SCH
Index LCID values
00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 351
351
[TS 36.323 clause 4.5]
For the purpose of MAC buffer status reporting, the UE shall consider PDCP Control PDUs, as well as the following as
data available for transmission :
- the PDU if the SDU has been processed by PDCP.
System Simulator:
- Cell 1
7.1.4.8.3.3-1
UE:
None.
Preamble;
- 2 AM DRBS are configured with the parameters specified in table 7.1.4.8.1-1.
Table 7.1.4.8.1-1: Logical Channel Configuration Settings
Parameter DRB1 DRB2
priority 7 6
logicalChannelGroup 2 1

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 352
352
U S Message
- - - -
RLC PDU on logical channel 4 (LCG ID 1),
which contains 1 RLC SDU of size 14 bytes.
<-- MAC PDU (RLC PDU)
<-- (UL grant) - -
4 The UE transmits a short BSR report. (Note 6) --> MAC PDU ((LCID=11101, LCG
ID='01', Buffer size index >0)
- -
- EXCEPTION: Steps 5 to 6 shall be repeated
two times (Note 4)
- - - -
5 Wait for periodicBSR-Timer expiry. - - - -
5A The SS sends an uplink grant of size 32 bits - - - -
containing a Short BSR with LCG ID field set
to 01 (logicalChannelGroup 1) and Buffer
Size Index >0?
--> MAC PDU (LCID=11101, LCG
ID=01, Buffer Size index >0)
2 P
7 Void
RLC PDU on logical channel 3 (LCG ID 2),
which contains 1 RLC SDU of size 14 bytes.
<-- MAC PDU (RLC PDU) - -
8A The SS sends an uplink grant of size 32 bits
(Note 3)
<-- (UL grant) - -
8B The UE transmits a long BSR report with
Buffer size#1 (LCG ID=1) and Buffer size#2
(LCG ID=2) fields set to value >0
--> MAC PDU (( Buffer size#1 index
>0, Buffer size#2 index= >0)
- -
9 Void
- EXCEPTION: Step 9A to 10 shall be repeated
twice. (Note 5)
- - - -
containing a Long BSR with Buffer size#1
(LCG ID=1) and Buffer size#2 (LCG ID=2)
fields set to value >0?
--> MAC PDU 1 P
10
A
The SS is configured for Uplink Grant
Allocation Type 3. The SS transmits 1 UL grant
of size 328 bits to enable the UE to loopback
RLC SDU on LCG ID =1 and LCG =2. (Note
7)
- -
11 The UE transmits MAC PDU containing the
remaining RLC SDUs as sent by the SS in
steps 2 and 8.
--> MAC PDU - -
Note 1: Void.
Note 2: SS transmits an UL grant of 32 bits (I
TBS
=0, N
PRB
Regular BSR triggered by the new data received logicalChannelGroup 1 in step 2.
TBS
=0, N
PRB
Regular BSR triggered by the new data received logicalChannelGroup 2 in step 8.
Note 4: One short BSR due to first expiry of periodicBSR-Timer and one short BSR due to second expire of
periodicBSR-Timer.
Note 5: One long BSR due to expire of periodicBSR-Timer and one long BSR due to second expiry of
periodicBSR-Timer.
Note 6: The UE starts periodicBSR-Timer.
TBS
=7, N
PRB
=3, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit
RLC SDU on LCG =1 (14 bytes) and LCG =2 (14 bytes) and a minimum MAC header of 3 bytes.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 353
353
c1 CHOICE{
explicit SEQUENCE {
maxHARQ-Tx n5
periodicBSR-Timer sf10
retxBSR-Timer sf10240
ttiBundling FALSE
}
}
}
}
}
}
}
}

7.1.4.9 Void
7.1.4.10 MAC padding
(1)
ensure that {
when { UE is to transmit a MAC PDU with padding exceeding 2 bytes }
then { Padding goes to the end of the MAC PDU }
}

(2)
ensure that {
when { UE is to transmit a MAC PDU with single-byte padding and there is a data MAC PDU sub-header
present }
then { UE is inserting padding MAC PDU subheader before any other MAC PDU sub-header }
}

(3)
ensure that {
when { UE is to transmit a MAC PDU with two-byte padding and there is a data MAC PDU sub-header }
then { UE is inserting two padding MAC PDU subheaders before any other MAC PDU sub-header }
}

(4)
ensure that {
when { UE is to transmit a MAC PDU with single-byte padding and there is no data MAC PDU sub-
header but a MAC Control element is present }
then { UE is inserting a padding MAC PDU subheader before any other MAC PDU sub-header }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 354
354
References: The conformance requirements covered in the current TC are specified in TS 36.321, clause 6.1.2.
[TS 36.321 clause 6.1.2]
MACControl
element1
...
R/R/E/LCID
sub-header
MACheader
MACpayload
R/R/E/LCID[/F/L]
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
...
R/R/E/LCID/F/L
sub-header
R/R/E/LCIDpadding
sub-header
MACControl
element2
MACSDU MACSDU
Padding
(opt)

and padding
System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 355
355
Table 7.1.4.10.3.3.2-1: Main behaviour
U - S Message
- - - -
2 The SS transmits a MAC PDU with 10 bytes
MAC SDU.
<-- MAC PDU(AMD PDU) - -
PUCCH.
- (SR) - -
4 The SS transmits an uplink grant of size 176
bits. (Note 1)
<-- (UL grant) - -
5 Check: Does the UE transmit a MAC PDU with
a MAC SDU of length 10 bytes and where the
last MAC sub-header has the Extension field
E set to 0 and the Logical Channel ID field
LCID set to 11111?
--> MAC PDU (BSR sub-header, MAC
SDU sub-header, Padding MAC
sub-header (E=0,
LCID=11111),Short BSR, MAC
SDU, padding)
1 P
MAC SDU.
<-- MAC PDU(AMD PDU) - -
PUCCH.
- (SR) - -
bits. (Note 2)
<-- (UL grant) - -
a MAC SDU of length 10 bytes and with a
padding MAC sub-header, with Extension field
E is set to 1 and the Logical Channel ID field
LCID is set to 11111, inserted before the
MAC SDU sub-header?
--> MAC PDU (Padding MAC-sub-
header (E=1, LCID=11111),
MAC SDU sub-header, MAC
SDU)
2 P
MAC SDU.
<-- MAC PDU (AMD PDU) - -
PUCCH.
- (SR) - -
bits. (Note 3)
<-- (UL grant) - -
two padding MAC sub-headers, with Extension
field E is set to 1 and the Logical Channel ID
field LCID is set to 11111, inserted before
the BSR sub-header and the MAC SDU sub-
header?
header#1 (E=1, LCID=11111),
Padding MAC-sub-header#2
(E=1, LCID=11111), BSR sub-
header, MAC SDU sub-header,
BSR, MAC-SDU)
3 P
14 The SS transmits a Timing Advance command
and does not send any subsequent timing
alignments. Start Timer_T1 =Time Alignment
timer value on SS.
<-- MAC PDU
(Timing Advance Command)
- -
15 40 to 50 TTI before Timer_T1 expires the SS
transmits a MAC PDU containing an RLC AMD
PDU.
<-- MAC PDU (AMD PDU) - -
16 The SS ignores scheduling requests and waits
until the UE transmits a preamble on PRACH.
--> (PRACH preamble) - -
17 The SS transmits a Random Access
Response, with an UL Grant of 56-bits. (Note
4)
18 The UE transmits a Control sub-header (8-bits)
and a C-RNTI MAC Control Element (16-bits).
--> MAC PDU (MAC Control sub-
header, Padding MAC sub-header
(E=0, LCID=11111), C-RNTI
control element, padding)
- -
19 The SS transmits an UL grant of 24 bits.
(Note 5)
<-- (UL grant) - -
19
A
Check: Does the UE transmit a MAC PDU with
a padding MAC sub header with Extension
field E is set to 1 and LCID field set to
11111 (8-bits) inserted before a BSR sub-
header (8bits) and a short BSR (8 bits)
header (E=1, LCID=11111),
BSR sub-header, short BSR)
4 P
20 The SS transmits an uplink grant enabling UE <-- (UL grant) - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 356
356
to transmit loop back PDU.
21 The UE transmits Loop back PDU. --> MAC PDU(AMD PDU) - -
TBS
=3, N
PRB
=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU
padding will be larger than 2 bytes. RLC SDU size is 8 bytes, size of AMD PDU header is 2 bytes, size of
MAC header is 4 bytes (2 bytes for MAC SDU sub-header using 7-bit LI, 1 byte for BSR sub-header and 1
byte for padding MAC sub-header) and size of Short BSR is 1 byte, equals to 120 bits (15 bytes) and
resulting into 56 bits padding.
TBS
=0, N
PRB
padding will be a single byte. RLC SDU size is 11 bytes, size of AMD PDU header is 2 bytes and size of
MAC header is 1 byte for MAC SDU sub-header, equals to 112 bits (14 bytes) and resulting into 1 single
byte padding.
TBS
=0, N
PRB
padding will be equal to 2 bytes. RLC SDU size is 8 bytes, size of AMD PDU header is 2 bytes, size of
MAC header is 4 bytes (1 bytes for MAC SDU sub-header, 1 byte for Short BSR sub-header and 2 bytes
for padding MAC sub-header) and size of Short BSR is 1 byte, equals to 120 bits (15 bytes) and resulting
no padding at the end of the MAC PDU.
TBS
=0, N
PRB
=3, see TS 36.213 Table 7.1.7.2.1-1) is as 36.321 clause 5.1.4 states that
the eNB should not provide a grant smaller than 56 bits in the Random Access Response.
Note 5: UL grant of 24 bits (ITBS=1, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU
padding will be equal to a single byte.

None.
7.1.4.11 Correct HARQ process handling
(1)
ensure that {
when { UE receives an UL Grant with toggled NDI and has data available for transmission }
then { UE transmits a new MAC PDU using redundancy version 0 }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less
than maxHARQ-Tx times }
ensure that {
when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the
HARQ process }
then { UE performs non-adaptive retransmission of the MAC PDU with redundancy version toggled by
one of the last (re)transmission [0,2,3,1 order] }
}

(3)
ensure that {
when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process
with old NDI [not toggled], irrespective of ACK/NACK is received for previous (re)transmission }
then { UE performs an adaptive retransmission of the MAC PDU with redundancy version as received
on PDCCH }
}

(4)
ensure that {
when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the
HARQ process }
then { UE does not retransmit the MAC PDU }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 357
357
(5)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU
maxHARQ-Tx times }
ensure that {
with not toggled NDI }
then { UE does not retransmit the MAC PDU but transmit a MAC Padding PDU}
}

(6)
ensure that {
with toggled NDI, and data are not available for transmission }
then { UE transmits any MAC Padding PDU }
}

(7)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU
maxHARQ-Tx times }
ensure that {
HARQ process }
then { UE does not transmit any MAC PDU }
}

5.4.2.2.
[TS 36.321, clause 5.4.2.1]
There is one HARQ entity at the UE, which maintains a number of parallel HARQ processes allowing transmissions to
take place continuously while waiting for the feedback on the successful or unsuccessful reception of previous
transmissions.
The number of parallel HARQ processes is specified in [2], clause 8.
At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process for which a
transmission should take place. It also routes the received feedback (ACK/NACK information), MCS and resource,
relayed by the physical layer, to the appropriate HARQ process.
If TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle. TTI
bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of
the same bundle. Within a bundle HARQ retransmissions are non-adaptive andtrigged without waiting for feedback
from previous transmissions according to TTI_BUNDLE_SIZE. The feedback for a bundle is only received for the last
TTI of the bundle (i.e the TTI corresponding to TTI_BUNDLE_SIZE ), regardless of whether a transmission in that TTI
takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is also a TTI bundle.
For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply.For each TTI, the
HARQ entity shall:
- identify the HARQ process associated with this TTI;
- if an uplink grant has been indicated for this TTI:
- if the received grant was not addressed to a Temporary C-RNTI on PDCCH and if the NDI provided in the
associated HARQ information has been toggled compared to the value in the previous transmission of this
HARQ process; or
- if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is
empty; or- if the uplink grant was received in a Random Access Response:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 358
358
- if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access
Response:
- obtain the MAC PDU to transmit from the Msg3 buffer.
- else:
- obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;
- deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;
- instruct the identified HARQ process to trigger a new transmission.
- else:
- deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;
- instruct the identified HARQ process to generate an adaptive retransmission.
- else, if the HARQ buffer of the HARQ process corresponding to this TTI is not empty:
- instruct the identified HARQ process to generate a non-adaptive retransmission.
When determining if NDI has been toggled compared to the value in the previous transmission UE shall ignore NDI
received in all uplink grants on PDCCH for its Temporary C-RNTI.
[TS 36.321, clause 5.4.2.2]
Each HARQ process is associated with a HARQ buffer.
Each HARQ process shall maintain a state variable CURRENT_TX_NB, which indicates the number of transmissions
that have taken place for the MAC PDU currently in the buffer, and a state variable HARQ_FEEDBACK, which
indicates the HARQ feedback for the MAC PDU currently in the buffer. When the HARQ process is established,
CURRENT_TX_NB shall be initialized to 0.
The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of
redundancy versions. This variable is up-dated modulo 4.
New transmissions are performed on the resource and with the MCS indicated on PDCCH or Random Access Response.
Adaptive retransmissions are performed on the resource and, if provided, with the MCS indicated on PDCCH.Non-
adaptive retransmission is performed on the same resource and with the same MCS as was used for the last made
transmission attempt,
The UE is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ
transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes
and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of
transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, maximum
number of transmissions shall be set to maxHARQ-Msg3Tx.
When the HARQ feedback is received for this TB, the HARQ process shall:
- set HARQ_FEEDBACK to the received value.
If the HARQ entity requests a new transmission, the HARQ process shall:
- set CURRENT_TX_NB to 0;
- set CURRENT_IRV to 0;
- store the MAC PDU in the associated HARQ buffer;
- store the uplink grant received from the HARQ entity;
- set HARQ_FEEDBACK to NACK;
- generate a transmission as described below.
If the HARQ entity requests a retransmission, the HARQ process shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 359
359
- increment CURRENT_TX_NB by 1;
- if the HARQ entity requests an adaptive retransmission:
- set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ
information;
- else if the HARQ entity requests a non-adaptive retransmission:
- if HARQ_FEEDBACK =NACK:
NOTE: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.
NOTE: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ
feedback can be received and a non-adaptive retransmission follows.
To generate a transmission, the HARQ process shall:
- if there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission
does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer:
- instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy
version corresponding to the CURRENT_IRV value;
- increment CURRENT_IRV by 1;
- if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the
MAC PDU was not obtained from the Msg3 buffer:
- set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.
After performing above actions, the HARQ process then shall:
- if CURRENT_TX_NB =maximum number of transmissions - 1:
- flush the HARQ buffer.
System Simulator:
- Cell 1
- System information takes into account the parameters in table 7.1.2.11.3.1-1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] using parameters as specified in Table
7.1.4.11.3.3-1 and 7.1.4.11.3.3-2.
- The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDUs in UL.
- No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 360
360
U - S Message
containing RLC PDU
<-- MAC PDU - -
2 Void - - - -
Allocation Type 3. The SS allocates an UL
Grant for one HARQ process X, sufficient for
one RLC SDU to be loop backed in a TTI, and
NDI indicates new transmission
including one RLC SDU, in HARQ process X,
redundancy version 0?
(Note 1)
--> MAC PDU 1 P
5 The SS transmits a NACK <-- HARQ NACK - -
6 Check: Does the UE retransmit the MAC PDU
for HARQ process X, redundancy version 2?
(Note 1)
--> MAC PDU 2 P
(Note 1)
--> MAC PDU 2 P
(Note 1)
--> MAC PDU 2 P
(Note 1)
--> MAC PDU 2 P
13 Void - - - -
14 Void - - - -
15 The SS transmits an ACK <-- HARQ ACK - -
for HARQ process X?
--> MAC PDU 4 F
17 The SS transmits an UL grant corresponding
to TTI for HARQ process X, with NDI not
toggled and redundancy version to be used as
1
in for HARQ process X, using redundancy
version 1?
(Note 1)
--> MAC PDU 3 P
to next TTI for HARQ process X, with NDI not
toggled and redundancy version to be used as
3
21 Check: Does the UE retransmit theMAC PDU
for HARQ process X, using next redundancy
version 3?
(Note 1)
--> MAC PDU 3 P
in the next TTIs corresponding to HARQ
process X?
--> MAC PDU 7 F
to TTI for HARQ process X, with NDI not
toggled
EXCEPTION: In parallel with step 25, UE
executes parallel behaviour defined in table
7.1.4.11.3.2-2
- - - -
25 Check: Does the UE retransmit the MAC PDU --> MAC PDU 5 F
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 361
361
process X?
25
A
The SS transmits an RLC STATUS PDU to the
UE
<-- RLC STATUS PDU (ACK_SN=1) - -
RLC PDU
<-- MAC PDU - -
27 Void - - - -
Allocation Type 3. The SS allocates UL Grant
for one HARQ process Y, sufficient for one
including one RLC SDU, in HARQ process Y,
redundancy version 0?
(Note 1)
--> MAC PDU 1 P
Allocation Type 3. The SS allocates UL Grant
for one HARQ process Y, sufficient for one
EXCEPTION: In parallel with step 31, UE
executes parallel behaviour defined in table
7.1.4.11.3.2-2.
- - - -
process Y?
--> MAC PDU 6 F
32 The SS transmits an RLC STATUS PDU to the
UE
Note 1: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by
receiving the UL MAC PDU correctly at SS.

U - S Message
1 The UE transmits a MAC Padding PDU --> MAC PDU - -

Table 7.1.4.11.3.3-1: MAC-MainConfig {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1,
step 8)}
MAC-MainConfig-RBC ::=SEQUENCE {
maxHARQ-Tx n8
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 362
362
Table 7.1.4.11.3.3-2: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1,
step 8)}
Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
RLC-Config-DRB-AM ::=CHOICE {
am SEQUENCE {
}
}
}

7.1.4.12 MAC reset / UL
(1)
with(UE in E-UTRA RRC_CONNECTED state, with Scheduling Request procedure trig gered)
ensure that {
then { UE cancels Scheduling Request procedure }
}

(2)
ensure that {
then { UE flushes UL HARQ buffer }
}

(3)
with (UE in E-UTRA RRC_CONNECTED state )
ensure that {
then { UE Considers the next transmission for each UL HARQ process as very first }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.9.
[TS 36.321 clause 5.9]
If a reset of the MAC entity is requested by upper layers, the UE shall:
- initialize Bj for each logical channel to zero;
- stop (if running) all timers;
- consider timeAlignmentTimer as expired and perform the corresponding actions in subclause 5.2;
- stop, if any, ongoing RACH procedure;
- discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any;
- flush Msg3 buffer;
- cancel, if any, triggered Scheduling Request procedure;
- cancel, if any, triggered Buffer Status Reporting procedure;
- cancel, if any, triggered Power Headroom Reporting procedure;
- flush the soft buffers for all DL HARQ processes;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 363
363
- for each DL HARQ process, consider the next received transmission for a TB as the very first transmission;
- release, if any, Temporary C-RNTI.
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) in Cell 1 according to [18].
clause.
T0 Cell-specific RS EPRE dBm/15Khz -85 Off

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 364
364
U - S Message
- - - -
RLC SDU on LC 4
bytes on DRB)
- -
3 The UE transmit a scheduling request --> (SR) - -
4 Wait for 50ms [Discard timer] to expire at UE. - - - -
5 The SS changes power level according to the
row "T1" in table 7.1.4.12.3.2-1
- - - -
handover to Cell 2.
<-- - - -
7 The UE transmits on cell 2,
--> - - -
8 Check: For 2 seconds, if UE transmits a
scheduling request?
--> (SR) 1 F
SDU on LC 4
bytes on DRB)
- -
11 The SS allocate UL Grant sufficient for one
12 The UE transmit a MAC PDU including one
RLC SDU
--> MAC PDU - -
13
A
The SS changes power level according to the
row "T2" in table 7.1.4.12.3.2-1
- - - -
handover to Cell 1
<-- - - -
15 The UE transmits on cell 1,
--> - - -
16 Check: For 2 seconds, does UE transmit MAC
PDU containing Loop Back PDU?
--> MAC PDU (1 RLC SDU of 40
bytes on DRB)
2 F
SDU on LC 4
bytes on DRB)
- -
19 The SS allocate UL Grant sufficient for one
including one RLC SDU?
--> MAC PDU 3 P

Table 7.1. 4.12.3.3-1: MAC-MainConfiguration {RRCConnectionReconfiguration (preamble)}
MAC-MainConfiguration-RBC ::=SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx n28
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 365
365
Table 7.1. 4.12.3.3-2: PDCP-Configuration-DRB-UM {RRCConnectionReconfiguration (preamble)}
Derivation Path: 36.508 clause 4.8.2.1.2.1-1
PDCP-Configuration-DRB-UM ::=SEQUENCE {
discardTimer ms50 Lowest value
}

Table 7.1.4.12.3.3-3: SchedulingRequest-Configuration {RRCConnectionReconfiguration (preamble)}
SchedulingRequest-Configuration::=CHOICE {
enable SEQUENCE {
}
}

c1 CHOICE{
n-HO

4.4.4.2)

}
}
}
}
}

c1 CHOICE{
n-HO

4.4.4.2)

}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 366
366
7.1.4.13 MAC PDU header handling
(1)
ensure that {
when { UE has a MAC SDU to be transmitted that is less smaller 128 bytes }
then { UE sets F field to 0 }
}

(2)
ensure that {
when { UE has a MAC SDU to be transmitted that is larger than 128 bytes }
then { UE sets F field to 1 }
}

(3)
ensure that {
when { UE inserts a R/R/E/LCID field in the MAC header and there is a subsequent R/R/E/LCID field
to be inserted }
then { UE sets E field to 1 }
}

(4)
ensure that {
when { UE inserts a R/R/E/LCID field in the MAC header and a MAC SDU or a MAC control element
starts at the next byte }
then { UE sets E field to 0 }
}

(5)
ensure that {
when { UE inserts the last MAC sub-header in the MAC PDU }
then { UE inserts a MAC sub-header consist solely of the four header fields R/R/E/LCID }
}

(6)
ensure that {
when { UE inserts padding at the end of a MAC PDU }
then { UE inserts the last MAC sub-header as a padding MAC subheader consisting solely of the
four header fields R/R/E/LCID with LCID set to Padding }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 6.1.2
and 6.2.1.
[TS 36.321, clause 6.1.2]
A MAC PDU header consists of one or more MAC PDU sub-headers; each sub header corresponding to either a MAC
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 367
367
A MAC PDU sub header consists of the six header fields R/R/E/LCID/F/L but for the last sub header in the MAC PDU
and for fixed sized MAC control elements. The last sub header in the MAC PDU and sub-headers for fixed sized MAC
LCID R
F L
7-bitsLfield
15-bitsLfield
R E LCID R
F L
R E
L
Oct1
Oct2
Oct1
Oct2
Oct3

Figure 6.1.2-1: R/R/E/LCID/F/L MAC sub header

LCID R
R E Oct1

Figure 6.1.2-2: R/R/E/LCID MAC sub header

MACControl
element1
...
R/R/E/LCID
sub-header
MACheader
MACpayload
R/R/E/LCID[/F/L]
sub-header
R/R/E/LCID/F/L
sub-header
R/R/E/LCID/F/L
sub-header
...
R/R/E/LCID/F/L
sub-header
R/R/E/LCIDpadding
sub-header
MACControl
element2
MACSDU MACSDU
Padding
(opt)

and padding
[TS 36.321, clause 6.2.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 368
368
included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU,
when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC PDU.
The LCID field size is 5 bits;
- L: The Length field indicates the length of the corresponding MAC SDU or MAC control element in bytes.
There is one L field per MAC PDU sub header except for the last sub header and sub-headers corresponding to
fixed-sized MAC control elements. The size of the L field is indicated by the F field;
- F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per
MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control
elements. The size of the F field is 1 bit. If the size of the MAC SDU or MAC control element is less than 128
bytes, the UE shall set the value of the F field to 0, otherwise the UE shall set it to 1;
- E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set
to "1" to indicate another set of at least R/R/E/LCID fields. The E field is set to "0" to indicate that either a MAC
SDU, a MAC control element or padding starts at the next byte;
- R: Reserved bits, set to "0".
The MAC header and sub-headers are octet aligned.
...
Index LCID values
00000 CCCH
11011 C-RNTI
11100 Truncated BSR
11101 Short BSR
11110 Long BSR
11111 Padding

Table 6.2.1-3: Values of F field:
Index Size of Length field (in bits)
0 7
1 15

System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 369
369
- 2 AM DRBs are configured with the parameters specified in table 7.1.4.13.3.1-1.
Table 7.1.4.13.3.1-1: Logical Channel Configuration Settings
Parameter DRB1 DRB2
Priority 7 6
logicalChannelGroup 2 1

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 370
370
U - S Message
- - - -
MAC SDU of size 127 bytes (RLC SDU of size
125 bytes +AMD PDU header 2 bytes
) with the Logical Channel ID field LCID set to
00011, and 1 Byte Padding in the associated
MAC SDU sub-header.
<-- MAC PDU (MAC sub-header
( LCID=00011), AMD PDU)
- -
3 The UE sends Scheduling Request --> (SR) - -
bits. (Note 1)
<-- (UL grant) - -
5 Check: does the UE transmit a MAC PDU with
a MAC SDU sub-header with Logical Channel
ID field LCID set to 00011, Format field F
set to 0 and Length field L set to 127? (Note
6)
--> MAC PDU (MAC sub-header
( LCID=00011, F=0, L=127
bytes), AMD PDU)
1 P
5a The SS transmits an RLC STATUS PDU to
acknowledge correctly received data
MAC SDU of size 128 bytes (RLC SDU of 126
bytes +AMD PDU header 2 bytes) with the
Logical Channel ID field LCID set to 00011.
(LCID=00011), AMD PDU)
- -
7 The UE send Scheduling Request --> (SR) - -
bits. (Note 2)
<-- (UL grant) - -
with a MAC SDU sub-header with Format field
F set to 1 and Logical Channel ID field LCID
set to 00011? (Note 6)
(LCID=00011, F=1, L=128),
AMD PDU)
2 P
10 The SS transmits an RLC STATUS PDU to
acknowledge correctly received data
MAC SDUs, the first containing a 9 byte RLC
SDU with LCID set to 00011 and the second
containing s 6 byte RLC SDU with LCID set to
00100.
(E=1, LCID=00011, F=0,
L=11), MAC sub-header (E=0,
LCID=00100), AMD PDU, AMD
PDU)
- -
bits. (Note 3)
<-- (UL grant) - -
14 Check: Does the UE return a MAC PDU of
length 176 bits containing two MAC sub-
headers where the first MAC sub-header have
the Expansion bit E set to 1 and the second
MAC sub-header has the Expansion bit E set
to 0 and no length field? (Note 5)
(E=1, (LCID=00011, L=1) or
(LCID=00100,L=8), MAC sub-
header (E=0, no Length field
present), AMD PDU, AMD PDU)
3,4,
5
P
15 SS transmits an RLC STATUS PDU to
acknowledge correctly received
data(LCID=00011)
data(LCID=00100)
<-- RLC STATUS PDU (ACK_SN=1)
MAC SDUs, the first containing a 8 byte RLC
SDU with LCID set to 00011 and the second
containing a 7 byte RLC SDU with LCID set to
00100.
(E=1, LCID=00011, F=0,
L=10), MAC sub-header (E=0,
LCID=00100,), AMD PDU, AMD
PDU)
- -
bits. (Note 4)
<-- (UL grant) - -
20 Check: Does the UE return a MAC PDU of
length 256 bits containing four MAC sub-
--> MAC PDU (Long BSR MAC sub-
header (E=1, LCID=11110,
3,4,
6
P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 371
371
headers where the first three MAC sub-header
have the Expansion bit E set to 1 and the
last MAC sub-header has the Expansion bit E
set to 0 and the LCID field set to 11111?
(Note 5)
MAC sub-header (E=1, F=0),
F=0), padding MAC sub-header
(E=0, LCID=11111), Long BSR,
AMD PDU, AMD PDU, padding)
Or
MAC PDU (Short BSR MAC sub-
header (E=1, LCID=11101,
F=0), padding MAC sub-header
(E=0, LCID=11111), Short BSR,
AMD PDU, AMD PDU, padding)
data(LCID=00011)
data(LCID=00100)
TBS
=8, N
PRB
=8, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit a
MAC SDU of size 127 bytes in a MAC PDU (125 bytes RLC SDU size +2 bytes AMD PDU header + 2
bytes MAC header (7 bit LI) =129 bytes =1032 bits <1096 bits.
TBS
=8, N
PRB
=8, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit a
MAC SDU of size 128 bytes in a MAC PDU (126 bytes RLC SDU size +2 bytes AMD PDU header + 3
bytes MAC header (15 bit LI) =131 bytes =1048 bits <1096 bits.
TBS
=1, N
PRB
=5, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit two
MAC SDUs, one of size 11 and one of size 8 bytes, in a MAC PDU (9 bytes RLC SDU +2 bytes AMD PDU
header + 6 bytes RLC SDU +2 bytes AMD PDU header +2 bytes MAC sub-header (7 bit LI) +one byte
MAC sub-header (R/R/E/LCID) =22 bytes =176 bits)
TBS
=6, N
PRB
=3, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit two
MAC SDUs of size 10 and 9 bytes in a MAC PDU ( (8 bytes RLC SDU +2 bytes AMD PDU header +7
bytes RLC SDU+2 bytes AMD PDU header) +3 byte Long BSR+4 byte padding +one byte BSR header+
2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) =32bytes =256
bits) or (8 bytes RLC SDU +2 bytes AMD PDU header +7 bytes RLC SDU+2 bytes AMD PDU header) +
1 byte Short BSR+6 byte padding +one byte BSR header+2 x 2 bytes MAC sub-header (7 bit LI) + one
byte padding MAC sub-header (R/R/E/LCID) =32bytes =256 bits))
Note 5: MAC SDU for LCID 3 and 4 can come in any order
Note 6: At this step UE shall include a BSR and report it on any of the configured Logical Channel Groups: 0
(SRB2), 1 (DRB2) and 2 (DRB1),

None.
7.1.4.14 Correct HARQ process handling / TTI bundling
(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and TTI bundling configured }
ensure that {
when { UE receives an UL Grant with toggled NDI and has data available for transmission }
then { UE transmits a new MAC PDU and non-adaptive retransmissions for 3 additional consecutive
UL subframes }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having
transmitted a MAC PDU less than maxHARQ-Tx times }
ensure that {
bundled HARQ process }
then { UE performs non-adaptive retransmissions of the MAC PDU for 4 consecutive UL subframes }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 372
372
(3)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having
transmitted a MAC PDU less than maxHARQ-Tx times }
ensure that {
with old NDI, irrespective of ACK/NACK is received for previous (re)transmission }
then { UE performs an adaptive retransmission of the MAC PDU with redundancy version as received
on PDCCH in first UL subframe and non-adaptive retransmissions in 3 additional consecutive UL
subframes }
}

(4)
ensure that {
when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the
HARQ process }
then { UE does not retransmit the TTI Bundle }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1,
5.4.2.2 & 7.5, TS 36.213 clause 8, 8.3, 8.6.1 & 9.1.2.
[TS 36.321, clause 5.4.2.1]
There is one HARQ entity at the UE, which maintains a number of parallel HARQ processes allowing transmissions to
take place continuously while waiting for HARQ the feedback on the successful or unsuccessful reception of previous
transmissions.
The number of parallel HARQ processes is specified in [2], clause 8.
At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process for which a
transmission should take place. It also routes the received HARQ feedback (ACK/NACK information), MCS and
resource, relayed by the physical layer, to the appropriate HARQ process.
When TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle.
TTI bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is
part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and triggered without waiting for
feedback from previous transmissions according to TTI_BUNDLE_SIZE. The HARQ feedback of a bundle is only
received for the last TTI of the bundle (i.e the TTI corresponding to TTI_BUNDLE_SIZE), regardless of whether a
transmission in that TTI takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is
also a TTI bundle.
For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply.
For each TTI, the HARQ entity shall:
- identify the HARQ process associated with this TTI;
- if an uplink grant has been indicated for this TTI:
- if the received grant was not addressed to a Temporary C-RNTI on PDCCH and if the NDI provided in the
associated HARQ information has been toggled compared to the value in the previous transmission of this
HARQ process; or
- if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is
empty; or
- if the uplink grant was received in a Random Access Response:
- if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access
Response:
- obtain the MAC PDU to transmit from the Msg3 buffer.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 373
373
- else:
- obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;
- deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;
- instruct the identified HARQ process to trigger a new transmission.
- else:
- deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ
process;
- instruct the identified HARQ process to generate an adaptive retransmission.
- else, if the HARQ buffer of the HARQ process corresponding to this TTI is not empty:
- instruct the identified HARQ process to generate a non-adaptive retransmission.
When determining if NDI has been toggled compared to the value in the previous transmission UE shall ignore NDI
received in all uplink grants on PDCCH for its Temporary C-RNTI.
[TS 36.321, clause 5.4.2.2]
Each HARQ process is associated with a HARQ buffer.
Each HARQ process shall maintain a state variable CURRENT_TX_NB, which indicates the number of transmissions
that have taken place for the MAC PDU currently in the buffer, and a state variable HARQ_FEEDBACK, which
indicates the HARQ feedback for the MAC PDU currently in the buffer. When the HARQ process is established,
CURRENT_TX_NB shall be initialized to 0.
The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of
redundancy versions. This variable is up-dated modulo 4.
New transmissions are performed on the resource and with the MCS indicated on PDCCH or Random Access Response.
Adaptive retransmissions are performed on the resource and, if provided, with the MCS indicated on PDCCH. Non-
adaptive retransmission is performed on the same resource and with the same MCS as was used for the last made
transmission attempt.
The UE is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ
transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes
and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of
transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum
number of transmissions shall be set to maxHARQ-Msg3Tx.
When the HARQ feedback is received for this TB, the HARQ process shall:
- set HARQ_FEEDBACK to the received value.
If the HARQ entity requests a new transmission, the HARQ process shall:
- set CURRENT_TX_NB to 0;
- set CURRENT_IRV to 0;
- store the MAC PDU in the associated HARQ buffer;
If the HARQ entity requests a retransmission, the HARQ process shall:
- increment CURRENT_TX_NB by 1;
- if the HARQ entity requests an adaptive retransmission:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 374
374
- set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ
information;
- else if the HARQ entity requests a non-adaptive retransmission:
- if HARQ_FEEDBACK =NACK:
NOTE 1: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.
NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ
feedback can be received and a non-adaptive retransmission follows.
To generate a transmission, the HARQ process shall:
- if the MAC PDU was obtained from the Msg3 buffer; or
- if there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission
does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer in this TTI:
- instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy
version corresponding to the CURRENT_IRV value;
- increment CURRENT_IRV by 1;
- if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the
MAC PDU was not obtained from the Msg3 buffer:
- set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.
After performing above actions, the HARQ process then shall:
- if CURRENT_TX_NB =maximum number of transmissions 1:
- flush the HARQ buffer;
[TS 36.321, clause 7.5]
The parameter TTI_BUNDLE_SIZE is 4.
[TS 36.213, clause 8]
For FDD, there shall be 8 HARQ processes in the uplink for non-subframe bundling operation, i.e. normal HARQ
operation, and 4 HARQ processes in the uplink for subframe bundling operation. The subframe bundling operation is
configured by the parameter ttiBundling provided by higher layers.
In case higher layers configure the use of subframe bundling for FDD and TDD, the subframe bundling operation is
only applied to UL-SCH, such that four consecutive uplink subframes are used.

For FDD and subframe bundling operation, the UE shall upon detection of a PDCCH with DCI format 0 in subframe n
intended for the UE, and/or a PHICH transmission in subframe n-5 intended for the UE, adjust the corresponding first
PUSCH transmission in the bundle in subframe n+4 according to the PDCCH and PHICH information.

For TDD UL/DL configurations 1 and 6 and subframe bundling operation, the UE shall upon detection of a PDCCH
with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in subframe n-l
with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe n+k, with k
given in Table 8-2, according to the PDCCH and PHICH information.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 375
375

Table 8-2: k for TDD configurations 0-6
TDD UL/DL
Configuration
0 1 2 3 4 5 6 7 8 9
0 4 6 4 6
1 6 4 6 4
2 4 4
3 4 4 4
4 4 4
5 4
6 7 7 7 7 5

Table 8-2a: l for TDD configurations 0, 1 and 6
TDD UL/DL
Configuration
0 1 2 3 4 5 6 7 8 9
0 9 6 9 6
1 2 3 2 3
6 5 5 6 6 8

[TS 36.213, clause 8.3]
For Frame Structure type 1, an ACK/NACK received on the PHICH assigned to a UE in subframe i is associated with
the PUSCH transmission in subframe i-4.
For Frame Structure type 2 UL/DL configuration 1-6, an ACK/NACK received on the PHICH assigned to a UE in
subframe i is associated with the PUSCH transmission in the subframei-k as indicated by the following table 8.3-1.

Table 8.3-1 k for TDD configurations 0-6
TDD UL/DL
Configuration
DL subframe number i
0 1 2 3 4 5 6 7 8 9
0 7 4 7 4
1 4 6 4 6
2 6 6
3 6 6 6
4 6 6
5 6
6 6 4 7 4 6

[TS 36.213, clause 8.6.1]
For 28 0
MCS
I , the modulation order (
m
Q ) is determined as follows:

If the parameter ttiBundling provided by higher layers is set to TRUE, then the resource allocation size is
restricted to 3
PRB
N and the modulation order is set to 2 =
m
Q .
[TS 36.213, clause 9.1.2]
For scheduled PUSCH transmissions in subframe n, a UE shall determine the corresponding PHICH resource in
subframe n+ k
PHICH
, where k
PHICH
is always 4 for FDD and is given in table 9.1.2-1 for TDD. For subframe bundling
operation, the corresponding PHICH resource is associated with the last subframe in the bundle.
Table 9.1.2-1: k
PHICH
for TDD
TDD UL/DL UL subframe index n
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 376
376
Configuration 0 1 2 3 4 5 6 7 8 9
0 4 7 6 4 7 6
1 4 6 4 6
2 6 6
3 6 6 6
4 6 6
5 6
6 4 6 6 4 7

System Simulator:
- Cell 1
UE:
None.
Preamble:
- No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 377
377
U - S Message
containing RLC PDU of size 312 bits on UM
Bearer.
<-- MAC PDU - -
2 The UE transmits a Scheduling Request --> Scheduling Request - -
3 The SS allocates an UL Grant of 328 bits with
NDI indicating new transmission (i.e. Nprb=3
and Imcs=7)(Note 1)
including one RLC SDU, with redundancy
version 0, k subframes after step 3?
(Note 3)
--> MAC PDU 1 P
5 Check: Does UE repeat non-adaptive
retransmission of MAC PDU in step 4, for 3
consecutive UL subframes with redundancy
version 2, 3 and 1 respectively?
(Note 3)
--> MAC PDU 1 P
6 The SS transmits a NACK, kk subframes after
last transmission in step 5.
<-- HARQ NACK - -
7 Check: Does the UE make non-adaptive
retransmissions of the MAC PDU m
subframes after NACK in step 6, for 4
consecutive UL subframes with redundancy
version 0, 2, 3 and 1 respectively?
(Note 3)
--> MAC PDU 2 P
8 The SS transmits an ACK, kk subframes after
<-- HARQ ACK - -
9 The SS allocates an UL Grant with NDI
indicating retransmission, start redundancy
version =2[i.e. Nprb=3 and Imcs=30], l
subframes after ACK in step 8.
10 Check: Does the UE perform an adaptive
retransmission of the MAC PDU k subframes
after grant in step 9, using redundancy version
2?
(Note 3)
--> MAC PDU 3 P
11 Check: Does UE repeat non-adaptive
retransmission of MAC PDU in step 10, for 3
consecutive UL sub-frames with redundancy
version 3, 1 and 0 respectively?
(Note 3)
--> MAC PDU 3 P
12 The SS transmits an ACK, kk subframes after
<-- HARQ ACK - -
13 Check: Does the UE make any
retransmissions of the MAC PDU m
subframes after ACK in step 12, for 4
consecutive UL subframes?
--> MAC PDU 4 F
Note 1: In step3, for TDD, the subframe number of allocating UL grant should be selected from {1, 4, 6, 9}
based on TDD default UL/DL configuration 1.
Note 2: For FDD value of k, kk is 4, l is 5 and m is 9.
For TDD UL/DL configuration 1, values of k, l, m and kk are given in table 7.1.4.14.3.2-2.
Note 3: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by
receiving the UL MAC PDU correctly at SS.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 378
378
Table 7.1.4.14.3.2-2: Values for parameter k, l, m and kk in Main behavior.
Parameter DL sub-frame number n
0 1 2 3 4 5 6 7 8 9
k 6 4 6 4
l 3 2 3 2
m 7 8 7 8
kk 4 6 4 6

Table 7.1.4.14.3.3-1: MAC-MainConfig-RBC in RRCConnectionReconfiguration(preamble)
Derivation Path: 36.508 table 4.8.2.1.5-1
MAC-MainConfigRBC- ::=SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx n28 Max value allowed
periodicBSR-Timer sf20 Default value
retxBSR-Timer sf1280 Default value
ttiBundling TRUE
}
}

7.1.4.15 UE power headroom reporting / Periodic reporting
(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic power headroom reporting
configured }
ensure that {
when { periodicPHR-Timer is configured in RRCConnectionReconfiguration procedre }
then { UE transmits a MAC PDU contianing Power Headroom MAC Control Element }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic power headroom reporting
configured }
ensure that {
when { periodicPHR-Timer expires and UL resources allocated for new transmission }
then { UE transmits a MAC PDU contianing Power Headroom MAC Control Element }
}

(3)
ensure that {
when { power headroom reporting is disabled }
then { UE stops transmiting Power Headroom MAC Control Element }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and
6.1.3.6, 36.331.
[TS 36.321, clause 5.4.6]
The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference
between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. The reporting
period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of 3GPP TS 36.133 [9]. RRC controls
Power Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by
signalling dl-PathlossChange which sets the change in measured downlink pathloss to trigger a PHR [8].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 379
379
A Power Headroom Report (PHR) shall be triggered if any of the following events occur:
- the prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB
since the transmission of a PHR when UE has UL resources for new transmission;
- periodicPHR-Timer expires;
- upon configuration and reconfiguration of the power headroom reporting functionality by upper layers [8], which
is not used to disable the function.
If the UE has UL resources allocated for new transmission for this TTI:
- if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer.
- if the Power Headroom reporting procedure determines that at least one PHR has been triggered since the last
transmission of a PHR r this is the first time that a PHR is triggered, and;
- if the allocated UL resources can accommodate a PHR MAC control element plus its subheader as a result of
logical channel prioritization:
- obtain the value of the power headroom from the physical layer;
- instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element
based on the value reported by the physical layer;
- start or restart periodicPHR-Timer;
- start or restart prohibitPHR-Timer;
- cancel all triggered PHR(s).
[TS 36.321, clause 6.1.3.6]
The Power Headroom MAC control element is identified by a MAC PDU sub header with LCID as specified in table
6.2.1-2. It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.6-1):
- R: reserved bit, set to "0";
- Power Headroom(PH): this field indicates the power headroom level. The length of the field is 6 bits. The
reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 below (the
corresponding measured values in dB can be found in subclause 9.1.8.4 of [19])
Power Headroom Oct 1 R R

Figure 6.1.3.6-1: Power Headroom MAC control element

Table 6.1.3.6-1: Power Headroom levels for PHR
PH Power Headroom Level
0
POWER_HEADROOM_0
1
POWER_HEADROOM_1
2 POWER_HEADROOM_2
3 POWER_HEADROOM_3

60 POWER_HEADROOM_60

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 380
380
System Simulator:
- Cell 1
UE:
None.
Preamble:
U - S Message
Allocation Type 2. The SS transmits UL grant
for the UE at every TTI for FDD and only at DL
subframes for TDD.
--> - - -
provide Power Headroom parameters
<-- - - -
containing Power Headroom MAC Control
Element?
--> MAC PDU 1 P
message to confirm the setup of Power
Headroom parameters.
--> - - -
Element 200ms after step 3?
--> MAC PDU 2 P
disable Power Headroom reporting
<-- - - -
message to confirm the disabling of Power
Headroom parameters
--> - - -
8 Check: for 2 seconds, does the UE transmit a
MAC PDU containing Power Headroom MAC
Control Element?
--> MAC PDU 3 F
Note: Steps 3 and 4 can happen in 2 MAC PDUs, or may be combined in one MAC PDU.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 381
381
c1 CHOICE{
explicitValue SEQUENCE {
phr-Confign CHOICE {
setup SEQUENCE {
periodicPHR-Timer sf200
prohibitPHR-Timer sf1000
dl-PathlossChange infinity
}
}
}
}
}
}
}
}
}

c1 CHOICE{
phr-Config CHOICE {
release NULL
}
}
}
}
}
}
}
}

7.1.4.16 UE power headroom reporting / DL pathloss change reporting
(1)
with { UE in E-UTRA RRC_Connected state with DRB established, Power headroom reporting for
DL_PAthloss change configured }
ensure that {
when { the DL Pathloss changes and prohibitPHR-Timer is running }
then { UE does not transmits a MAC PDU containing Power Headroom MAC Control Element }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 382
382
(2)
with { UE in E-UTRA RRC_Connected state with DRB established, Power headroom reporting for
DL_PAthloss change configured }
ensure that {
when { prohibitPHR-Timer expires and power headroom report is triggered due to DL Pathloss
change }
then { UE transmits a MAC PDU containing Power Headroom MAC Control Element }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and
6.1.3.6
[TS 36.321, clause 5.4.6]
The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference
between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. The reporting
period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of [9]. RRC controls Power Headroom
reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-
PathlossChange which sets the change in measured downlink pathloss to trigger a PHR [8].
A Power Headroom Report (PHR) shall be triggered if any of the following events occur:
- prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB since
the transmission of a PHR when UE has UL resources for new transmission;
- periodicPHR-Timer expires;
- upon configuration or reconfiguration of the power headroom reporting functionality by upper layers [8], which
is not used to disable the function.

If the UE has UL resources allocated for new transmission for this TTI:
- if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer;
- if the Power Headroom reporting procedure determines that at least one PHR has been triggered since the last
transmission of a PHR or this is the first time that a PHR is triggered, and;
- if the allocated UL resources can accommodate a PHR MAC control element plus its subheader as a result of
logical channel prioritization:
- obtain the value of the power headroom from the physical layer;
- instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element
based on the value reported by the physical layer;
- start or restart periodicPHR-Timer;
- start or restart prohibitPHR-Timer;
- cancel all triggered PHR(s).
[TS 36.321, clause 6.1.3.6]
The Power Headroom MAC control element is identified by a MAC PDU sub header with LCID as specified in table
6.2.1-1. It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.6-1):
- R: reserved bit, set to "0";
- Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The
reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6.1-1 below (the
corresponding measured values in dB can be found in subclause 9.1.8.4 of [17]).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 383
383
Power Headroom Oct 1 R R

Figure 6.1.3.6-1: Power Headroom MAC control element

Table 6.1.3.6-1: Power Headroom levels for PHR
PH Power Headroom Level
0
POWER_HEADROOM_0
1
POWER_HEADROOM_1
2 POWER_HEADROOM_2
3 POWER_HEADROOM_3


System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 384
384
U - S Message
Allocation Type 2. SS is configured to transmit
UL grant for UE at every TTI for FDD, and only
at DL subframes for TDD.
- - - -
2 SS transmits an
provide Power Headroom parameters
<-- RRCConnectionReconfiguration - -
message to confirm the setup of Power
Headroom parameters.
--> - - -
4 Wait for T1=10% of prohibitPHR-Timer. - - - -
5 Reduce SS power level so as to cause a
DL_Pathloss change at UE by 5dB.
- - - -
6 Check : for 80% of prohibitPHR-Timer since
step 3, doesthe UE transmit a MAC PDU
Element?
--> MAC PDU 1 F
7 Check: after prohibitPHR-Timer after step 3,
does the UE transmit a MAC PDU containing
Power Headroom MAC Control Element?
--> MAC PDU 2 P
8 Increase SS power level so as to cause a
DL_Pathloss change at UE by 5dB.
- - - -
9 Check : for 80% of prohibitPHR-Timer since
step 7, does the UE transmit a MAC PDU
Element?
--> MAC PDU 1 F
10 Check: after prohibitPHR-Timer after step 7,
does the UE transmit a MAC PDU containing
Power Headroom MAC Control Element?
--> MAC PDU 2 P
Note: Steps 3 in main behaviour and step 1 in parallel behaviour can happen in 2 MAC PDUs, or may be
combined in one MAC PDU.

U - S Message
1 The UE transmit a MAC PDU containing
Power Headroom MAC Control Element.
--> MAC PDU - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 385
385
Table 7.1. 4.16.3.3-1: RRCConnectionReconfiguration (step 2, Table 7.1.4.16.3.2-1)
c1 CHOICE{
explicit SEQUENCE {
phr-Configuration CHOICE {
enable SEQUENCE {
periodicPHR-Timer infinity
dl-PathlossChange dB3
}
}
}
}
}
}
}
}
}

7.1.5 PUSCH Hopping
7.1.5.1 Inter-TTI PUSCH hopping by uplink grant
(1)
with { UE in E-UTRA RRC_CONNECTED state and Hopping-mode is set to InterSubFrame}
ensure that {
when { UE receives for a TTI an uplink grant with Hopping flag set as 1, N
UL_hop
bits indicating
Type 1 PUSCH Hopping }
then { UE transmits UL data on resource blocks as per type 1 PUSCH hopping}
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.212 clause
5.3.3.1.1 and 36.213 clause 8.4, 8.4.1 & 8.4,2.
[TS 36.212, clause 5.3.3.1.1]
DCI format 0 is used for the scheduling of PUSCH.
The following information is transmitted by means of the DCI format 0:
- Flag for format0/format1A differentiation 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
- Hopping flag 1 bit as defined in section 8.4 of [3]
- Resource block assignment and hopping resource allocation
(
) 2 / ) 1 ( ( log
UL
RB
UL
RB 2
+ N N bits
- For PUSCH hopping:
- N
UL_hop
MSB bits are used to obtain the value of ) (
~
i n
PRB
as indicated in subclause [8.4] of [3]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 386
386
-
( |
.
|
\
|
+
UL_hop
UL
RB
UL
RB 2
) 2 / ) 1 ( ( log N N N bits provide the resource allocation of the first slot in the UL
subframe
- For non-hopping PUSCH:
-
( |
.
|
\
|
+ ) 2 / ) 1 ( ( log
UL
RB
UL
RB 2
N N bits provide the resource allocation in the UL subframe as defined in section
8.1 of [3]
[TS 36.213, clause 8.4]
The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding
PDCCH with DCI format 0 is set to 1 otherwise no PUSCH frequency hopping is performed.
A UE performing PUSCH frequency hopping shall determine its PUSCH resource allocation (RA) for the first slot of a
subframe (S1) including the lowest index PRB ( ) (
1
n n
S
PRB
) in subframe n from the resource allocation field in the latest
PDCCH with DCI format 0 for the same transport block. If there is no PDCCH for the same transport block, the UE
shall determine its hopping type based on
- the hopping information in the most recent semi-persistent scheduling assignment PDCCH, when the initial
PUSCH for the same transport block is semi-persistently scheduled or
- the random access response grant for the same transport block, when the PUSCH is initiated by the random
access response grant.
The resource allocation field in DCI format 0 excludes either 1 or 2 bits used for hopping information as indicated by
Table 8.4-1 below where the number of PUSCH resource blocks is defined as
( )
>
=

=
hopping PUSCH 1 N 2 Type
~
hopping PUSCH 1 Type 2 mod
~
sb
sb
HO
RB
UL
RB
UL
RB
UL
RB
HO
RB
UL
RB
PUSCH
RB
N N
N
N N N
N
For type 1 and type 2 PUSCH hopping, 1
~
HO
RB
HO
RB
+ = N N if
HO
RB
N

is an odd number where
HO
RB
N defined in [3].
HO
RB
HO
RB
~
N N = in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits
shall be
( hop UL
N N N y
_
UL
RB
UL
RB 2
) 2 / ) 1 ( ( log + = , where N
UL_hop
=1 or 2 bits. The number of contiguous RBs
that can be assigned to a type-1 hopping user is limited to

UL
RB
/ 2 N
y
. The number of contiguous RBs that can be
assigned to a type-2 hopping user is limited to
min(

UL
RB
/ 2 N
y
,
sb
N N /
PUSCH
RB
)
,where the number of sub-bands
sb
N is given by higher layers.
A UE performing PUSCH frequency hopping shall use one of two possible PUSCH frequency hopping types based on
the hopping information. PUSCH hopping type 1 is described in section 8.4.1 and type 2 is described in section 8.4.2.
Table 8.4-1: Number of Hopping Bits N
UL_hop
vs. System Bandwidth
System BW
UL
RB
N

#Hopping bits for
2nd slot RA
(N
UL_hop
)
6-49 1
50-110 2

The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is inter-subframe
or intra and inter-subframe.
[TS 36.213, clause 8.4.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 387
387
For PUSCH hopping type 1 the hopping bit or bits indicated in Table 8.4-1 determine ) (
~
i n
PRB
as defined in Table 8.4-2.
The lowest index PRB (
1 S
PRB
n ) of the 1
st
slot RA in subframe i is defined as 2 /
~
) (
~
) (
HO
RB
1 1
N i n i n
S
PRB
S
PRB
+ = , where
START
S
PRB
RB i n = ) (
1
, and
START
RB is obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
The lowest index PRB ( ) (i n
PRB
) of the 2
nd
slot RA in subframe i is defined as 2 /
~
) (
~
) (
HO
RB
N i n i n
PRB PRB
+ = .
The set of physical resource blocks to be used for PUSCH transmission are
CRBs
L contiguously allocated resource
blocks from PRB index
1 S
PRB
n for the 1
st
slot, and from PRB index ) (i n
PRB
for the 2
nd
slot, respectively, where
CRBs
L is
obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
If the Hopping-mode is "inter-subframe", the 1
st
slot RA is applied to even CURRENT_TX_NB, and the 2
nd
slot RA is
applied to odd CURRENT_TX_NB, where CURRENT_TX_NB is defined in [8].
[TS 36.213, clause 8.4.2]
Table 8.4-2: PDCCH DCI Format 0 Hopping Bit Definition
System BW
UL
RB
N

Number of
Hopping bits
Information in
hopping bits
) (
~
i n
PRB

6 49 1
0

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
2 /
1
|
.
|
\
|
+ ,
1 Type 2 PUSCH Hopping
50 110 2
00

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
4 /
1
|
.
|
\
|
+
01

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
4 /
1
|
.
|
\
|
+
10

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
2 /
1
|
.
|
\
|
+

System Simulator
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 388
388
U - S Message
- - - -
Exception: Steps 2 to 5 are executed as per
table 7.1.5.1.3.3-2

2 SS transmits a MAC PDU including 8
(FDD)/4(TDD) RLC SDUs
<-- MAC PDU - -
3 The SS waits for 60 ms - - - -
Exception: Steps 4 and 5 are repeated such
that UE sends data in 8 ([FDD)/4(TDD)
consecutive UL TTIs.

allowing the UE to return 1 RLC SDU as
received in step 2. Hopping flag set as 1, all
bits in N
UL_hop
are set as per table 7.1.5.3.3-2
for various execution runs
- - 1 P
Note 1: Steps 4 and 5 are repeated for 8 times corresponding to 8 sub frames for FDD and 4 for default TDD
configuration 1.
Note 2: The grant allocated in step 4 is such that the loop back PDU's are received in 8 (FDD)/4(TDD) UL TTI's

Table 7.1.5.1.3.3-2: Bandwidth dependent parameters
System BW
Number of Hopping
bits
Execution Counter K
Information in hopping
bits
5 MHz 1 1
0
10/20 MHz 2
1
00
2 01
3 10

None
7.1.5.2 Predefined intra-TTI PUSCH hopping (N_sb=1)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands 'N-sb' is set to 1 and Hopping-mode
is set to 'intraAndInterSubFrame'}
ensure that {
when { UE receives for a TTI an uplink grant with 'Hopping flag' set as 1, 'N
UL_hop
' bits all set to
1(Type 2 predefined hopping) }
then { UE transmits data with predefined, intra-TTI PUSCH hopping}
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.211 clause 5.3.4 ,
36.212 clause 5.3.3.1.1 and 36.213 clause 8.4, 8.4.2.
[TS 36.211, clause 5.3.4]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 389
389
If uplink frequency-hopping with predefined hopping pattern is enabled, the set of physical resource blocks to be used
for transmission in slot
s
n is given by the scheduling grant together with a predefined pattern according to
( ) ( ) ( ) ( ) ( )

(
(
>
=
=
> +
=
=
=
+ + =
1 2
1
~
1 2 ) (
~
1 ) (
~
) (
hopping subframe inter and intra
hopping subframe inter 2
) mod( ) ( mod
~
2 1
~
) (
~
HO
RB VRB
VRB
VRB
HO
RB s PRB
s PRB
s PRB
s
s
sb
sb
RB m
sb
RB VRB
sb
RB
sb
RB hop VRB s PRB
sb
sb
sb
sb
N N n
N n
n
N N n n
N n n
n n
n
n
i
N N i f N n N N i f n n n

where
VRB
n is obtained from the scheduling grant as described in Section 8.1 in [4]. The parameter pusch-
HoppingOffset,
HO
RB
N , is provided by higher layers.. The size
sb
RB
N of each sub-band is given by,
( )

>
=
=
1 2 mod
1
sb sb
HO
RB
HO
RB
UL
RB
sb
UL
RB
sb
RB
N N N N N
N N
N
where the number of sub-bands
sb
N is given by higher layers. The function { } 1 , 0 ) (
m
i f determines whether mirroring
is used or not. The parameter Hopping-mode provided by higher layers determines if hopping is inter-subframe or
intra and inter-subframe.
The hopping function ) (
hop
i f and the function ) (
m
i f are given by
> + |
.
|
\
|
+
= +
=
=
+
+ =
+
+
+ =
+
2 mod ) 1 ) 1 mod( 2 ) ( ) 1 ( (
2 mod ) 2 ) ( ) 1 ( (
1 0
) (
9 10
1 10
) 1 10 (
9 10
1 10
) 1 10 (
hop
sb sb sb
i
i k
i k
hop
sb sb
i
i k
i k
hop
sb
N N N k c i f
N N k c i f
N
i f

>
=
=
=
1 ) 10 (
hopping subframe inter and 1
hopping subframe inter and intra and 1
2 mod _ _
2 mod
) (
m
sb
sb
sb
N i c
N
N
NB TX CURRENT
i
i f
where ) 1 (
hop
f =0 and the pseudo-random sequence ) (i c is given by section 7.2 and CURRENT_TX_NB indicates
the transmission number for the transport block transmitted in slot
s
n as defined in [8]. The pseudo-random sequence
generator shall be initialised with
cell
ID init
N c = for FDD and
cell
ID
9
init
) 4 mod ( 2 N n c
f
+ = for TDD

at the start of
each frame.
[TS 36.212, clause 5.3.3.1.1]
(
) 2 / ) 1 ( ( log
UL
RB
UL
RB 2
+ N N bits
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 390
390
- N
UL_hop
~
i n
PRB
-
( |
.
|
\
|
+
UL_hop
UL
RB
UL
RB 2
subframe
-
( |
.
|
\
|
+ ) 2 / ) 1 ( ( log
UL
RB
UL
RB 2
N N bits provide the resource allocation in the UL subframe as defined in section
8.1 of [3]
[TS 36.213, clause 8.4]
The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding
PDCCH with DCI format 0 is set to 1 otherwise no PUSCH frequency hopping is performed.
A UE performing PUSCH frequency hopping shall determine its PUSCH resource allocation (RA) for the first slot of a
subframe (S1) including the lowest index PRB ( ) (
1
n n
S
PRB
) in subframe n from the resource allocation field in the latest
PDCCH with DCI format 0 for the same transport block. If there is no PDCCH for the same transport block, the UE
shall determine its hopping type based on
- the hopping information in the most recent semi-persistent scheduling assignment PDCCH, when the initial
PUSCH for the same transport block is semi-persistently scheduled or
- the random access response grant for the same transport block, when the PUSCH is initiated by the random
The resource allocation field in DCI format 0 excludes either 1 or 2 bits used for hopping information as indicated by
Table 8.4-1 below where the number of PUSCH resource blocks is defined as
( )
>
=

=
~
hopping PUSCH 1 Type 2 mod
~
sb
sb
HO
RB
UL
RB
UL
RB
UL
RB
HO
RB
UL
RB
PUSCH
RB
N N
N
N N N
N
For type 1 and type 2 PUSCH hopping, 1
~
HO
RB
HO
RB
+ = N N if
HO
RB
N

is an odd number where
HO
RB
N defined in [3].
HO
RB
HO
RB
~
N N = in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits
shall be
( hop UL
N N N y
_
UL
RB
UL
RB 2
) 2 / ) 1 ( ( log + = , where N
UL_hop
=1 or 2 bits. The number of contiguous RBs
that can be assigned to a type-1 hopping user is limited to

UL
RB
/ 2 N
y
. The number of contiguous RBs that can be
assigned to a type-2 hopping user is limited to
min(

UL
RB
/ 2 N
y
,
sb
N N /
PUSCH
RB
)
,where the number of sub-bands
sb
N is given by higher layers.
A UE performing PUSCH frequency hopping shall use one of two possible PUSCH frequency hopping types based on
the hopping information. PUSCH hopping type 1 is described in section 8.4.1 and type 2 is described in section 8.4.2.
Table 8.4-1: Number of Hopping Bits N
UL_hop
vs. System Bandwidth
System BW
UL
RB
N

#Hopping bits for
2nd slot RA
(N
UL_hop
)
6-49 1
50-110 2

The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is inter-subframe
or intra and inter-subframe.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 391
391
[TS 36.213, clause 8.4.2]
In PUSCH hopping type 2 the set of physical resource blocks to be used for transmission in slot
s
n is given by the
scheduling grant together with a predefined pattern according to [3] section 5.3.4. If the system frame number is not
acquired by the UE yet, the UE shall not transmit PUSCH with type-2 hopping and N
sb
>1 for TDD, where N
sb
is defined
in [3].
Table 8.4-2: PDCCH DCI Format 0 Hopping Bit Definition
System BW
UL
RB
N

Number of
Hopping bits
Information in
hopping bits
) (
~
i n
PRB

6 49 1
0

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
2 /
1
|
.
|
\
|
+ ,
50 110 2
00

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
4 /
1
|
.
|
\
|
+
01

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
4 /
1
|
.
|
\
|
+
10

PUSCH
RB
S
PRB
PUSCH
RB
N i n N mod ) (
~
2 /
1
|
.
|
\
|
+

System Simulator
- Cell 1
UE:
None.
Preamble:
U - S Message
- - - -
2 SS transmits a MAC PDU including 8
(FDD)/4(TDD) RLC SDUs
<-- MAC PDU - -
3 The SS waits for 60 ms - - - -
Exception: Steps 4 and 5 are repeated such
that UE sends data in 8 ([FDD)/4(TDD)
consecutive UL TTIs.

allowing the UE to return 1 RLC SDU as
bits in N
UL_hop
are set to 1.
--> MAC PDU 1 P
Note 1: steps 4 and 5 are repeated for 8 times corresponding to 8 sub frames for FDD and 4 for default TDD
configuration 1.
Note 2: The grant allocated in step 4 is such that the loop back PDU's are received in 8 (FDD)/4(TDD) UL TTI's

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 392
392
Table 7.1.5.2.3.3-1: SystemInformationBlockType2(preamble)
SEQUENCE {

radioResourceConfigCommon SEQUENCE {} RadioResourceCo
nfigCommonSIB-
DEFAULT-7152

}

Table 7.1.5.2.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7152(Table 7.1.5.2.3.3-1)
RadioResourceConfigCommonSIB-DEFAULT-
7152 ::=SEQUENCE {

pusch-Config PUSCH-ConfigCommon-
DEFAULT-7152

}

Table 7.1.5.2.3.3-3: PUSCH-ConfigCommon-DEFAULT-7152(Table 7.1.5.2.3.3-2)
PUSCH-ConfigCommon-DEFAULT-7152 ::=
SEQUENCE {

pusch-ConfigBasic SEQUENCE {
n-SB 1 Default value
hoppingMode intraAndInterSubFrame
pusch-HoppingOffset See subclause
4.6.8[36.508]
Default value
}
}

7.1.5.3 Predefined intra-TTI PUSCH hopping (N_sb=2/3/4)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands N-sb is set to 2/3/4 and Hopping-
mode is set to intraAndInterSubFrame}
ensure that {
UL_hop
bits all set to
then { UE transmits data with predefined, inter-TTI PUSCH hopping}
}

Same Conformance requirements as in clause 7.1.5.2.2
System Simulator
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 393
393
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode, Test Mode Activated (State 2A) according to [18].
U - S Message
EXCEPTION: Step 0 to 7 are repeated for
execution counter k=1 to 3

0 The SS transmits a Paging message in a
paging occasion including a
systemInfoModification.
<-- Paging - -
0a From the begining of the next modification
period the SS transmits a modified
SystemInformationBlockType2 as specified.
- - - -
1 The UE is brought to state Loopback
Activated (state 4) according to [18]
- - - -
- - - -
SDU
<-- MAC PDU 1 -
4 The SS waits for 60 ms - - -
received in step 2. Hopping flag set as 1,
N
UL_hop
is set to 1.
- - 1 P
7 The SS releases the RRC connection - - - -

Table 7.1.5.3.3.3-1: SystemInformationBlockType2(Step 0 of Table 7.1.5.3.3.2-1)
SEQUENCE {

ac-BarringInfo SEQUENCE {} Not present
nfigCommonSIB-
DEFAULT-7153

}

Table 7.1.5.3.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7153
7153 ::=SEQUENCE {

DEFAULT-7153

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 394
394
Table 7.1.5.3.3.3-3: PUSCH-ConfigCommon-DEFAULT-7153
SEQUENCE {

n-SB 2 Execution
counter k =1
n-SB 3 Execution
counter k =2
n-SB 4 Execution
counter k =3
hoppingMode intraAndInterSubFrame
pusch-HoppingOffset See subclause 4.6.8 Default value
enable64QAM FALSE Default value
}
}

7.1.5.4 Predefined inter-TTI PUSCH hopping (N_sb=1)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands 'N-sb' is set to 1 and 'Hopping-mode'
is set to 'interSubFrame'}
ensure that {
when { UE receives for a TTI an uplink grant with 'Hopping flag' set as 1, 'N
UL_hop
' bits all set to
}
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands 'N-sb' is set to 1, 'Hopping-mode' is
set to 'interSubFrame' has transmitted a transport block with predefined, inter-TTI PUSCH hopping }
ensure that {
when { UE has to make a non adaptive retransmission) }
}

Same Pre-test conditions as in clause 7.1.5.2.3.1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 395
395
U - S Message
- - - -
SDU
<-- MAC PDU 1 -
3 The SS waits for 60 ms. - - - -
bits in N
UL_hop
are set to 1.
- MAC PDU 1 P
6 The SS transmits a HARQ NACK <-- HARQ NACK - -
corresponding to grant in step 4, for same
HARQ process as in step 5?
--> MAC PDU 2 P
--> MAC PDU 2 P
--> MAC PDU 2 P
12 The SS transmits an HARQ ACK <-- HARQ ACK - -
Note: 4 HARQ transmissions is selected to be less than MaxHARQ-Tx (=5)

None
7.1.5.5 Predefined inter-TTI PUSCH hopping (N_sb=2/3/4)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands N-sb is set to 2/3/4 and Hopping-
mode is set to interSubFrame}
ensure that {
UL_hop
bits are all
set to 1(Type 2 predefined hopping) }
}

Same Pre-test conditions as in clause 7.1.5.3.3.1
Same Test procedure sequence as in table 7.1.5.3.3.2-1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 396
396
Table 7.1.5.5.3.3-1: SystemInformationBlockType2(Step 0 of Table 7.1.5.3.3.2-1)
SEQUENCE {

ac-BarringInfo SEQUENCE {} Not present
nfigCommonSIB-
DEFAULT-7155

}

Table 7.1.5.5.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7155
7155 ::=SEQUENCE {

DEFAULT-7155

}

Table 7.1.5.5.3.3-3: PUSCH-ConfigCommon-DEFAULT-7155
SEQUENCE {

n-SB 2 Execution
counter k =1
n-SB 3 Execution
counter k =2
n-SB 4 Execution
counter k =3
hoppingMode interSubFrame Default value
pusch-HoppingOffset See subclause 4.6.8 Default value
enable64QAM FALSE Default value
}
}

7.1.6 DRX operation
7.1.6.1 DRX operation / Short cycle not configured / Parameters configured by RRC
(1)
with { UE in CONNECTED mode }
ensure that {
when { Long DRX cycle is configured and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) =
drxStartOffset }
then { UE starts the OnDurationTimer and monitors the PDCCH for OnDurationTimer PDCCH-
subframes }
}

(2)
ensure that {
when { Long DRX cycle is configured and a new DL transmission is indicated on the PDCCH during
Active Time }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 397
397
then { UE starts or restarts the Drx-InactivityTimer and monitors the PDCCH for Drx-
InactivityTimer PDCCH sub-frames starting from the next PDCCH sub-frame of the PDCCH sub-frame where
the DL new transmission was indicated }
}

(3)
ensure that {
when { Long DRX cycle is configured and if a HARQ RTT Timer expires in this subframe and the data
in the soft buffer of the corresponding HARQ process was not successfully decoded }
then { UE starts the drx-RetransmissionTimer for the corresponding HARQ process and monitors the
PDCCH for drx-RetransmissionTimer consecutive PDCCH-subframes }
}

(4)
ensure that {
when { Long DRX cycle is configured and an uplink grant for a pending HARQ retransmission can
occur in this subframe }
then { UE monitors the PDCCH in this subframe }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH
in PDCCH-subframes.
...
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure
3.1-1 below).
UE shall monitor
PDCCH
On Duration
DRX Cycle
Opportunity for DRX

Figure 3.1-1: DRX Cycle

drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH
indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL
retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
...
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission
is expected by the UE.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 398
398
...
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and
subframes including DwPTS.
[TS 36.321, clause 5.7]
The UE may be configured by RRC with a DRX functionality that controls the UEs PDCCH monitoring activity for
the UEs C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and Semi-Persistent Scheduling C-RNTI (if configured).
When in RRC_CONNECTED, if DRX is configured, the UE is allowed to monitor the PDCCH discontinuously using
the DRX operation specified in this subclause; otherwise the UE monitors the PDCCH continuously. When using DRX
operation, the UE shall also monitor PDCCH according to requirements found in other subclauses of this specification.
RRC controls DRX operation by configuring the timers onDurationTimer, drx-InactivityTimer, drx-
RetransmissionTimer (one per DL HARQ process except for the broadcast process), the longDRX-Cycle, the value of
the drxStartOffset and optionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timer per DL HARQ
process (except for the broadcast process) is also defined (see subclause 7.7).
When a DRX cycle is configured, the Active Time includes the time while:
- onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or mac-ContentionResolutionTimer (as
described in subclause 5.1.5) is running; or
- a Scheduling Request sent on PUCCH is pending (as described in subclause 5.4.4); or
- an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ
buffer; or
- a PDCCH indicating a new transmission addressed to the C-RNTI of the UE has not been received after
successful reception of a Random Access Response for the explicitely signaled preamble (as described in
subclause 5.1.4).
When DRX is configured, the UE shall for each subframe:
- If the Short DRX Cycle is used and [(SFN * 10) +subframe number] modulo (shortDRX-Cycle) =
(drxStartOffset) modulo (shortDRX-Cycle); or
- if the Long DRX Cycle is used and [(SFN * 10) +subframe number] modulo (LongDRX-Cycle) =
drxStartOffset:
- start onDurationTimer.
- if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ
process was not successfully decoded:
- start the drx-RetransmissionTimer for the corresponding HARQ process.
- if a DRX Command MAC control element is received:
- stop onDurationTimer;
- stop drx-InactivityTimer.
- if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
- if the short DRX cycle is configured:
- start or restart drxShortCycleTimer;
- use the Short DRX Cycle.
- else:
- use the Long DRX cycle.
- if drxShortCycleTimer expires in this subframe:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 399
399
- use the long DRX cycle.
- during the Active Time, for a PDCCH-subframe if the subframe is not required for uplink transmission for half-
duplex FDD UE operation and if the subframe is not part of a configured measurement gap:
- monitor the PDCCH;
- if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
- start the HARQ RTT Timer for the corresponding HARQ process;
- stop the drx-RetransmissionTimer for the corresponding HARQ process.
- if the PDCCH indicates a new transmission (DL or UL):
- start or restart drx-InactivityTimer.
- when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such
is expected.
NOTE: A UE may optionally choose to not send CQI/PMI/RI reports on PUCCH and/or SRS transmissions for
up to 4 subframes following a PDCCH indicating a new transmission (UL or DL) received in the last
subframe of active time. The choice not to send CQI/PMI/RI reports on PUCCH and/or SRS
transmissions is not applicable for subframes where onDurationTimer is running.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] configured to return no data in UL with the
exceptions as listed in Table 7.1.6.1.3.3-1.
For FDD, NormalSF(current SFN,current subframe number,y)=y; For TDD, NormalSF(current SFN,current subframe
number,y) counts the minimum number of normal subframes needed to cover y number of PDCCH-subframes until
next PDCCH-subframe available, starting from current subframe number on current SFN.For example at step 1,
drxStartOffset can point to UL or DL subframe for TDD. If it points to a UL subframe, NormalSF(current SFN,current
subframe number,0) counts the number of normal subframes until reach the first DL/special subframe available. If
drxStartOffset points to a DL subframe, NormalSF(current SFN,current subframe number,0)=0.
For example at step 13, assuming drxStartOffset points to subframe number 0 at frame number A, NormalSF(A, 0,
onDurationTimer-2) is first added, which counts 18 PDCCH-subframes/30 normal subframes in this case. The current
subframe becomes subframe number 0 at frame number A+3. Secondly, HARQ RTT timer is added, which is 11 normal
subframes. The current subframe becomes subframe number 1 at frame number A+4. To further add in NormalSF(A+4,
1, drx-RetransmissionTimer-1), which is to counts 5 PDCCH-subframes/9 normal subframes, the current subframe is
subframe number 0 at frame number A+5.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 400
400
Table 7.1.6.1.3.2-1: Main Behaviour
U - S Message
1 In the first PDCCH sub frame when the
OnDurationTimer is running, the SS indicates
the transmission of a DL MAC PDU on the
PDCCH.

i.e., on the subframe with the subframe
number =[csfn1 +NormalSF(SFN1, csfn1, 0)]
modulo 10, and system frame number =SFN1
+floor([csfn1 +NormalSF(SFN1, csfn1,
0)]/10); where [(SFN1 * 10) +csfn1] modulo
(LongDRX-Cycle) =drxStartOffset
<-- MAC PDU - -
2 Check: Does the UE transmit a HARQ ACK for
the DL MAC PDU in Step 1?
--> HARQ ACK 1 P
3 At least drx-InactivityTimer PDCCH-sub
frames after the transmission of the MAC PDU
in Step 1 has been indicated(This means the
next DRX cycle or later after Step 1) in the last
PDCCH sub frame while the onDurationTimer
is still runnin, the SS indicates the transmission
a DL MAC PDU on the PDDCH. (Note 4).

number =[csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer-1)]
+floor([csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer-
<-- MAC PDU - -
--> HARQ ACK 1 P
5 drx-InactivityTimer PDCCH-subframes after
the transmission of the MAC PDU transmitted
in step 3 was indicated on the PDCCH, the SS
indicates the transmission of a DL MAC PDU
on the PDCCH. (Note 4)

i.e. on the subframe with the subframe number
=[csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer +drx-
InactivityTimer-1)] modulo 10, and system
frame number =SFN2 +floor([csfn2 +
NormalSF(SFN2,csfn2,onDurationTimer+drx-
InactivityTimer-1)]/10)

<-- MAC PDU - -
--> HARQ ACK 2 P
7 At least drx-InactivityTimer PDCCH sub frames
after the transmission of the MAC PDU in Step
5 has been indicated (This means the next
DRX cycle or later after Step 3) and 1 PDCCH
sub-frame before the OnDurationTimer
expires, the SS indicates the transmission of a
DL MAC PDU on the PDDCH. The DL MAC
PDU transmitted is invalid. (Note 1, Note 4)

number =[csfn3 +NormalSF(SFN3, csfn3,
onDurationTimer-2)] mod 10, and system
frame number =SFN3 +floor([csfn3 +
NormalSF(SFN3, csfn3, onDurationTimer-

<-- Invalid MAC PDU - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 401
401
8 Check: Does the UE transmit a HARQ NACK
for the DL MAC PDU in Step 7?
--> HARQ NACK 1 P
9 In the first PDCCH sub frame when the Drx-
RetransmissionTimer for the MAC PDU in Step
7 is started, the SS indicates the transmission
of a DL MAC PDU on the PDCCH.

number =[csfn4 +NormalSF(SFN4, csfn4, 0)]
+floor([csfn4 +NormalSF(SFN4, csfn4,
0)]/10); where csfn4 =[csfn3 +
2)+HARQ RTT timer] modulo 10 and
SFN4=SFN3+floor([csfn3 +NormalSF(SFN3,
csfn3, onDurationTimer-2)+HARQ RTT
timer]/10)

For TDD the HARQ RTT timer is the HARQ
RTT timer for the DL transmission in Step 7.
<-- MAC PDU - -
--> HARQ ACK 3 P
11 At least drx-InactivityTimer PDCCH sub frames
after the transmission of the DL MAC PDU in
Step 9 has been indicated (This means the
next DRX cycle or later after Step 9) and 1
PDCCH sub-frame before the
OnDurationTimer expires, the SS indicates the
transmission of DL MAC PDU on the PDCCH.
The DL MAC PDU transmitted is invalid(Note
1, Note 4)

onDurationTimer-2)] modulo 10 and system
frame number=SFN5+floor([csfn5 +
2)]/10) ; where [(SFN5 * 10) +csfn5] modulo

<-- Invalid MAC PDU - -
--> HARQ NACK 1 P
13 In the last PDCCH sub frame when the drx-
RetransmissionTimer for MAC PDU in Step 11
is still running, the SS indicates the
transmission of a DL MAC PDU on the
PDCCH.

i.e. on the subframe with subframe number =
[csfn6 +NormalSF(SFN6,csfn6,drx-
RetransmissionTimer -1)] modulo 10 and the
system frame number=SFN6+floor([csfn6 +
NormalSF(SFN6,csfn6,drx-
RetransmissionTimer -1)]/10); where the csfn6
=[csfn5 +NormalSF(SFN5, csfn5,
onDurationTimer-2)+HARQ RTT timer] modulo
10 and SFN6=SFN5+floor([csfn5 +
2)+HARQ RTT timer]/10);

<-- MAC PDU - -
--> HARQ ACK 3 P
Allocation Type 2. At least drx-InactivityTimer
PDCCH sub frames after the transmission of
the DL MAC PDU in Step 13 has been
<-- UL grant on PDCCH - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 402
402
indicated in the last sub-frame when the
onDuratiopnTimer is still running (This means
the next DRX cycle or later after Step 7), the
SS indicates an UL grant to the UE on the
PDCCH. (Note 4)

onDurationTimer-1)] modulo 10 and system
frame number=SFN7 +floor([csfn7 +
16 Check: Does the UE transmit a Buffer Status
Report on the UL indicating an empty buffer?
--> Buffer Status Report MAC control
element
- -
17 X sub frames after the sub frame in which the
UL grant was indicated on the PDCCH for the
UL MAC PDU sent in the previous step the SS
indicates the transmission of a DL MAC PDU
on the PDCCH.

X is the number of sub frames required to do a
retransmission of the UL MAC PDU
transmitted in the previous Step maxHARQ-Tx
-1 times (for FDD this is 8x maxHARQ-Tx sub
frames, for TDD this is 10x maxHARQ-Tx sub
frames considering the default configuration
1.).
<-- MAC PDU - -
--> HARQ ACK 4 P
Note 1: Invalid MAC PDU is a MAC PDU that fails the CRC check.
Note 2: All the DL MAC PDU are transmitted with the NDI set on the PDCCH.
Note 3: Timer tolerances for the MAC DRX related timers measured in subframes or PDCCH subframes is 0. These
timers are: drx-InactivityTimer, drx-RetransmissionTimer, HARQ RTT Timer.
Note 4: The drx-InactivityTimer is started in the next PDCCH sub-frame of the PDCCH sub-frame where DL new
transmission is indicated.

Table 7.1.6.1.3.3-1: specific Parameters in RRCConnectionReconfiguration in the preamble
maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
onDurationTimer psf20
drx-InactivityTimer psf6
drx-RetransmissionTimer psf6
longDRX-CycleStartOffset CHOICE {
sf640 1
}
shortDRX Not present
}
}
timeAlignmentTimerDedicated infinity
phr-Config CHOICE {
release NULL
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 403
403
7.1.6.2 DRX Operation / Short cycle not configured / DRX command MAC control
element reception
(1)
ensure that {
when { long DRX cycle is configured and a DRX Command MAC control element is received }
then { UE successfully decodes the MAC control PDU }
}

(2)
ensure that {
when { long DRX cycle is configured and the HARQ RTT Timer is running and a DRX Command MAC
control element is received }
then { UE continues running the HARQ RTT timer }
}

(3)
ensure that {
when { long DRX cycle is configured and the drx-RetransmissionTimer is running and a DRX Command
MAC control element is received }
then { UE continues running the drx-RetransmissionTimer and monitors the PDCCH }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH
in PDCCH-subframes.
...
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure
3.1-1 below).
UE shall monitor
PDCCH
On Duration
DRX Cycle
Opportunity for DRX

Figure 3.1-1: DRX Cycle

drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH
indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL
retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 404
404
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
...
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission
is expected by the UE.
...
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and
subframes including DwPTS.
[TS 36.321, clause 5.7]
- if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ
process was not successfully decoded:
- start the drx-RetransmissionTimer for the corresponding HARQ process.
- if a DRX Command MAC control element is received:
- stop onDurationTimer;
- stop drx-InactivityTimer.
- if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
- if the short DRX cycle is configured:
- start or restart drxShortCycleTimer;
- use the Short DRX Cycle.
- else:
- use the Long DRX cycle.
- if drxShortCycleTimer expires in this subframe:
- use the long DRX cycle.
- during the Active Time, for a PDCCH-subframe except if the subframe is required for uplink transmission for
half-duplex FDD UE operation and except if the subframe is part of a configured measurement gap:
- monitor the PDCCH;
- if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
- start the HARQ RTT Timer for the corresponding HARQ process;
- stop the drx-RetransmissionTimer for the corresponding HARQ process.
- if the PDCCH indicates a new transmission (DL or UL):
- start or restart drx-InactivityTimer.
- when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such
is expected.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 405
405
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] configured to return no data in UL with the
exceptions as listed in Table 7.1.6.2.3.3-1.
The definition of NormalSF(current SFN,current subframe number,y) can be found in clause 7.1.6.1.3.2.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 406
406
Table 7.1.6.2.3.2-1: Main Behavior
U - S Message
1 In a PDCCH sub frame which is X PDCCH sub
frames before the PDCCH sub-frame in which
the onDurationTimer expires,
with drx-InactivityTimer<X <the number of
PDCCH subframes encapsulated by HARQ
RTT timer, the SS indicates the transmission
of a DL MAC PDU on the PDCCH. The SS
transmits an invalid MAC PDU.(Note 1)

number csfn2 =[csfn1+NormalSF(SFN1,
csfn1, onDurationTimer-1-X)] modulo 10, and
the system frame number SFN2 =
SFN1+floor([csfn1+NormalSF(SFN1, csfn1,
onDurationTimer-1-X)]/10); and [(SFN1 * 10) +
csfn1] modulo (Long DRX Cycle) =
drxStartOffset.

<--
MAC PDU - -
-->
HARQ NACK 1 P
3 In a PDCCH sub frames before the
onDurationTimer expires, the SS indicates the
transmission of a DL MAC PDU on the
PDCCH. The SS transmits a DL MAC PDU
with DRX MAC Control element.
UE successfully decodes the MAC PDU.

csfn1, onDurationTimer-1-X+Y)] modulo 10,
and the system frame number SFN3 =
onDurationTimer-1-X+Y)]/10); and 0<Y<X)

<--
MAC PDU(DRX MAC Control
element)
- -
-->
HARQ ACK 1 P
5 In the PDCCH sub frame when the drx-
RetransmissionTimer for the MAC PDU
indicated in Step 1 on the PDCCH is started
the SS indicates the transmission of a DL MAC
PDU. The SS transmits an invalid MAC
PDU.(Note 1)

csfn4, 0)] modulo 10, and the system frame
number SFN5 =
0)]/10); where csfn4 =[csfn2+HARQ RTT
Timer] modulo 10, and the SFN4 =
SFN2+floor([csfn2+HARQ RTT Timer]/10);

RTT timer for the DL transmission in Step 1
<--
MAC PDU - -
-->
HARQ NACK 2,3 P
7 Z PDCCH sub frames,
where Z>drx-InactivityTimer, before the
PDCCH sub-frame in which the drx-
RetransmissionTimer for the DL MAC PDU in
Step 5 expires, the SS indicates the
transmission of a DL MAC PDU. The SS
transmits a DL MAC PDU with DRX MAC
Control element.
<--
MAC PDU(DRX MAC Control
element)
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 407
407

number =[csfn6+NormalSF(SFN6, csfn6, drx-
RetransmissionTimer Z)] modulo 10, and the
system frame number =
drx-RetransmissionTimer Z)]/10); where
csfn6 =[csfn5+HARQ RTT Timer] modulo 10,
and the SFN6 =SFN5+floor([csfn5+HARQ
RTT Timer]/10);


-->
HARQ ACK 2,3,
1
P
9 In the last sub frame when the Drx-
RetransmissionTimer for the DL MAC PDU
indicated on the PDCCH in Step 5 is still
running, the SS indicates the transmission of a
DL MAC PDU.

number =[csfn6+NormalSF(SFN6, csfn6, drx-
RetransmissionTimer 1)] modulo 10, and the
system frame number =
drx-RetransmissionTimer 1)]/10);
<--
MAC PDU - -
-->
HARQ ACK 2,3 P
Note 1: Invalid MAC PDU is a MAC PDU that fails the CRC check.
Note 2: All DL MAC PDUs are transmitted with the NDI set on the PDCCH.
Note 3: Timer tolerances for the MAC DRX related timers measured in subframes or PDCCH subframes is 0. These
timers are: drx-InactivityTimer, drx-RetransmissionTimer, HARQ RTT Timer.

Table 7.1.6.2.3.3-1: specific Parameters in RRCConnectionReconfiguration in the preamble
maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
drx-RetransmissionTimer psf6
sf640 0
}
}
}
phr-Config CHOICE {
release NULL
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 408
408
7.1.7 Transport block size selection
7.1.7.0 Specific configurations
The configurations defined in table 7.1.7.0-1 is used after step 7 of table 4.5.3.3-1 [18] in the preamble and in all steps
in the main behaviour of the test cases in clause 7.1.7.
Table 7.1.7.0-1: Power allocation for OFDM symbols and reference signals, single SS Tx antenna
Physical Channel EPRE Ratio Comment
PBCH PBCH_RA =0 dB
PBCH_RB =0 dB
PSS PSS_RA =0 dB
SSS SSS_RA =0 dB
PCFICH PCFICH_RB =0 dB
PDCCH PDCCH_RA =0 dB
PDCCH_RB =0 dB
PDSCH PDSCH_RA =0 dB
PDSCH_RB =0 dB
PHICH PHICH_RB =0 dB

The configurations defined in table 7.1.7.0-2 is used in step 8 of table 4.5.3.3-1 [18] in the preamble of the test cases in
clause 7.1.7.
Table 7.1.7.0-2: PDSCH-ConfigDedicated-DEFAULT
PDSCH-ConfigDedicated-DEFAULT ::=SEQUENCE
{

p-a dB0 1TX
dB-3 2TX
}

7.1.7.1 DL-SCH transport block size selection
7.1.7.1.1 DL-SCH transport block size selection / DCI format 1 / RA type 0
7.1.7.1.1.1 Test Purpose (TP)
(1)
ensure that {
when { UE on PDCCH receives DCI format 1 indicating Resource Allocation Type 0, a resource block
assignment correspondent to
PRB
N physical resource blocks and a modulation and coding scheme
MCS
I }
then { UE decodes the received transport block of size correspondent to the read
PRB
N and
MCS
I
and forwards it to higher layers }
}

7.1.7.1.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.212, clause 5.3.3.1.2; TS
36.213, clauses 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
DCI format 1 is used for the scheduling of one PDSCH codeword.
- Resource allocation header (resource allocation type 0 / type 1) 1 bit as defined in section 7.1.6 of [3]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 409
409
If downlink bandwidth is less than or equal to 10 PRBs, there is no resource allocation header and resource
allocation type 0 is assumed.
- Resource block assignment:
- For resource allocation type 0 as defined in section 7.1.6.1 of [3]:
-
(
P N /
DL
RB
bits provide the resource allocation
...
where the value of P depends on the number of DL resource blocks as indicated in section 7.1. 6 of [3]
- Modulation and coding scheme 5 bits as defined in section 7.1.7 of [3]
If the number of information bits in format 1 is equal to that for format 0/1A, one bit of value zero shall be appended to
format 1.
If the number of information bits in format 1 belongs to one of the sizes in Table 5.3.3.1.2-1, one or more zero bit(s)
shall be appended to format 1 until the payload size of format 1 does not belong to one of the sizes in Table 5.3.3.1.2-1
and not equal to that of format 0/1A.
Table 5.3.3.1.2-1: Ambiguous Sizes of Information Bits
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

[TS 36.213 clause 7.1.6.1]
In resource allocations of type 0, resource block assignment information includes a bitmap indicating the resource block
groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive physical resource blocks
(PRBs). Resource block group size (P) is a function of the system bandwidth as shown in Table 7.1.6.1-1. The total
number of RBGs (
RBG
N ) for downlink system bandwidth of
DL
RB
N PRBs is given by
(
P N N
RBG
/
DL
RB
= where

P N /
DL
RB
of the RBGs are of size P and if 0 mod
DL
RB
> P N then one of the RBGs is of size

P N P N /
DL
RB
DL
RB
. The
bitmap is of size
RBG
N bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be
indexed in the order of increasing frequency and non-increasing RBG sizes starting at the lowest frequency. The order
of RBG to bitmap bit mapping is in such way that RBG 0 to RBG 1
RBG
N are mapped to MSB to LSB of the bitmap.
The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE
otherwise.
Table 7.1.6.1-1: Type 0 Resource Allocation RBG Size vs. Downlink System Bandwidth
System Bandwidth RBG Size
DL
RB
N
(P)
10 1
11 26 2
27 63 3
64 110 4

[TS 36.213 clause 7.1.7]
To determine the modulation order and transport block size(s) in the physical downlink shared channel, the UE shall
first
read the 5-bit modulation and coding scheme field (
MCS
I ) in the DCI
and second if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then
...
else
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 410
410
set the Table 7.1.7.2.1-1 column indicator
PRB
N to the total number of allocated PRBs based on the procedure
defined in Section 7.1.6.
if the transport block is transmitted in DwPTS of the special subframe in frame structure type 2, then
{ }
PRB
max 0.75 , 1
PRB
N N ( =

,
else, set the Table 7.1.7.2.1-1 column indicator
PRB PRB
N N = .
The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than
0.930, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits)
divided by the number of physical channel bits on PDSCH. If the UE skips decoding, the physical layer indicates to
higher layer that the transport block is not successfully decoded. For the special subframe configurations 0 and 5 with
normal CP or configurations 0 and 4 with extended CP, shown in table 4.2-1 [3], there shall be no PDSCH transmission
in DwPTS of the special subframe.
[TS 36.213 clause 7.1.7.1]
The UE shall use
m
Q = 2 if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI, otherwise, the UE shall
use
MCS
I and Table 7.1.7.1-1 to determine the modulation order (
m
Q ) used in the physical downlink shared channel.
Table 7.1.7.1-1: Modulation and TBS index table for PDSCH
MCS Index
MCS
I
Modulation Order
m
Q
TBS Index
TBS
I
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
reserved 30 4
31 6

[TS 36.213 clause 7.1.7.2]
If the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 411
411
- for DCI format 1A:
- the UE shall set the TBS index (
TBS
I ) equal to
MCS
I and determine its TBS by the procedure in Section
7.1.7.2.1.
...
else
- for 28 0
MCS
I , the UE shall first determine the TBS index (
TBS
I ) using
MCS
I and Table 7.1.7.1-1 except if the
transport block is disabled in DCI formats 2 and 2A as specified below. For a transport block that is not mapped
to two-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.1. For a transport
block that is mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in Section
7.1.7.2.2.
- for 31 29
MCS
I , the TBS is assumed to be as determined from DCI transported in the latest PDCCH for the
same transport block using 28 0
MCS
I . If there is no latest PDCCH for the same transport block
using 28 0
MCS
I , and if the initial PDSCH for the same transport block is semi-persistently scheduled, the
TBS shall be determined from the most recent semi-persistent scheduling assignment PDCCH.
- In DCI formats 2 and 2A a transport block is disabled if 0
MCS
= I and if rv
idx
=1 otherwise the transport block is
enabled.
The NDI and HARQ process ID, as signalled on PDCCH, and the TBS, as determined above, shall be delivered to
higher layers.
[TS 36.213 clause 7.1.7.2.1]
For 110 1
PRB
N , the TBS is given by the (
TBS
I ,
PRB
N ) entry of Table 7.1.7.2.1-1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 412
412
Table 7.1.7.2.1-1: Transport block size table (dimension 27110)
TBS
I
PRB
N
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
TBS
I

PRB
N

11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
TBS
I
PRB
N
21 22 23 24 25 26 27 28 29 30
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 413
413
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
TBS
I
PRB
N
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
TBS
I
PRB
N
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 414
414
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
TBS
I
PRB
N
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
TBS
I
PRB
N
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 415
415
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
TBS
I
PRB
N
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
TBS
I
PRB
N
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 416
416
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
TBS
I
PRB
N
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
TBS
I
PRB
N
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 417
417
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376

[TS 36.306 clause 4.1]
The field ue-Category defines a combined uplink and downlink capability. The parameters set by the UE Category are
defined in subclause 4.2. Tables 4.1-1 and 4.1-2 define the downlink and, respectively, uplink physical layer parameter
values for each UE Category.
Table 4.1-1: Downlink physical layer parameter values set by the field ue-Category
UE Category Maximum number of
DL-SCH transport
block bits recei ved
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

Table 4.1-2: Uplink physical layer parameter values set by the field ue-Category
bits of an UL-SCH
transport block
transmitted within a
TTI
Support for
64QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No
Category 5 75376 Yes

7.1.7.1.1.3 Test description
7.1.7.1.1.3.1 Pre-test conditions
System Simulator:
- Cell 1.
- Uplink and downlink bandwidth set to the maximum bandwidth for the E-UTRA Band under test as specified in
Table 5.6.1-1 in [31] (to enable testing of
PRB
N up to maximum value).
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 418
418
7.1.7.1.1.3.2 Test procedure sequence
Table 7.1.7.1.1.3.2-1: Maximum TB
size
for different UE categories
bits of a DL-SCH
transport block
recei ved within a TTI
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776

Table 7.1.7.1.1.3.2-2: Number of downlink PDCP SDUs and PDCP SDU size used as test data
TB
size

[bits]
Number of
PDCP SDUs
PDCP SDU size
[bits]
See note 1
104 TB
size
12096note 2 1 8*FLOOR((TB
size
96)/8)
12097 TB
size
24128 2 8*FLOOR((TB
size
128)/16))
24129 TB
size
36152 3 8*FLOOR((TB
size
152)/24))
36153 TB
size
48184 4 8*FLOOR((TB
size
184)/32))
48185 TB
size
60208 5 8*FLOOR((TB
size
208)/40))
60209 TB
size
72240 6 8*FLOOR((TB
size
240)/48))
TB
size
>72240 7 8*FLOOR((TB
size
264)/56))
Note 1. Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS
24.301 clause 9.9.4.12).

The PDCP SDU size of each PDCP SDU is

PDCP SDU size =(TB
size
N*PDCP header size - AMD PDU header size - MAC header size Size of
Timing Advance RLC Status PDU size) / N, where

PDCP header size is 16 bits for the RLC AM and 12-bit SN case;
AMD PDU header size is CIEL[(16+(N-1)*12)/8] bytes which includes 16 standard AM header and (N-1)
Length indicators; and

MAC header size =40 bits as MAC header size can be
1) R/R/E/LCID MAC subheader (8 bits for Timing Advance) +R/R/E/LCID MAC subheader (16 bits for
MAC SDU for RLC Status PDU)R/R/E/LCID MAC subheader (8 bits for MAC SDU) =for AMD PDU 8 +8
16+bits =32 bits
Or
MAC SDU for AMD PDU, Note: Length can be of 2 bytes depending upon the size of AMD PDU)+
R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Status PDU) +=8+24 +8 bits =40 bits

Therefore Maximum MAC header size can be 40 bits

Size of Timing Advance MAC CE is 8 bits (if no Timing Advance and/or RLC status needs to be sent,
padding will occur instead)

RLC Status PDU size =16 bits

This gives:

PDCP SDU size =8*FLOOR((TB
size
N*16- 8*CIEL((16+(N-1)*12)/8) 64)/(8*N)) bits
Note 2: According to TS 36.213 Table 7.1.7.2.1-1 and the final PDCP SDU size formula in Note 1, the smallest
TB
size
that can be tested is 104 bits.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 419
419
Table 7.1.7.1.1.3.2-2a: Bandwidth Dependent Parameters
Max Bandwidth
Max
PRB
N Allowed
PRB
N Values
10 Mhz 50 2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18, 20, 21, 23, 24, 26,
27, 29, 30, 32, 33, 35, 36, 38, 39, 41, 42, 44, 45, 47, 48,
50
15 Mhz 75 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32,
35, 36, 39, 40, 43, 44 ,47, 48, 51, 52, 55, 56, 59, 60, 63,
64, 67, 68, 71, 72, 75
20 Mhz 100 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64,
68, 72, 76, 80, 84, 88, 92, 96, 100
Note : Maximum bandwidth for EUTRA bands is 10/15/20 Mhz.

Table 7.1.7.1.1.3.2-2b: Ambiguous Sizes of Information Bits
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U S Message
- EXCEPTION: Steps 1 to 4 are
repeated for allowed values of
PRB
N as per table 7.1.7.1.1.3.2-
2a and
MCS
I from 0 to 28.
- - - -
1
SS looks up
TBS
I in table 7.1.7.1-
1 in TS 36.213 based on the value
of
MCS
I . SS looks up TB
size
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS
I .
- - - -
performed if TB
size
is less than or
equal to UE capability Maximum
number of DL-SCH transport
block bits received within a TTI
as specified in Table 7.1.7.1.1.3.2-
1 and larger than or equal to 104
bits as specified in Table
7.1.7.1.1.3.2-2, and the effective
channel code rate, as defined in
TS 36.213 clause 7.1.7, is lower
than or equal to 0.930.
- - - -
2 SS creates one or more PDCP
SDUs, depending on TB
size
, in
accordance with Table
7.1.7.1.1.3.2-2.
- - - -
3 SS transmits the PDCP SDUs
concatenated into a MAC PDU
and indicates on PDCCH DCI
Format 1 with RA type 0 and a
resource block assignment (RBA)
correspondent to
PRB
N as
specified in 7.1.6.1 in TS 36.213
and modulation and coding
scheme
MCS
I .

If the number of information bits in
format 1 is equal to that for format
0/1A, one bit of value zero shall
<-- MAC PDU (NxPDCP
SDUs)
DCI: (DCI Format 1, RA
type 0, RBA(
PRB
N ),
MCS
I )
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 420
420

7.1.7.1.1.3.3 Specific Message Contents
Table 7.1.7.1.1.3.3.1: MAC-MainConfig-RBC (preamble Table 4.5.3.3-1 [18]: Step 8)
Derivation Path: 36.508 Table 4.8.2.1.5-1
retxBSR-Timer sf320

7.1.7.1.2 DL-SCH transport block size selection / DCI format 1 / RA type 1
(1)
ensure that {
when { UE on PDCCH receives DCI format 1 indicating Resource Allocation Type 1, a resource block
assignment correspondent to
PRB
MCS
I }
PRB
N and
MCS
I
}

36.213, clauses 7.1.6.2, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
DCI format 1 is used for the scheduling of one PDSCH codeword.

be appended to format 1 by the
SS.

format 1 belongs to one of the
sizes in Table 7.1.7.1.1.3.2-2b,
one or more zero bit(s) shall be
appended to format 1 by the SS
until the payload size of format 1
does not belong to one of the
sizes in Table 7.1.7.1.1.3.2-2b
and not equal to that of format
0/1A.
3A At the reception of scheduling
request the SS transmits UL Grant
for transmitting loop back PDCP
SDUs.
<-- (UL Grant) - -
4 CHECK: Does UE return the
same number of PDCP SDUs with
same content as transmitted by
the SS in step 3?
--> (NxPDCP SDUs) 1 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 421
421
- For resource allocation type 1 as defined in section 7.1.6.2 of [3]:
- ( )
(
P
2
log bits of this field are used as a header specific to this resource allocation type to indicate the
selected resource blocks subset
- 1 bit indicates a shift of the resource allocation span
-
(
( )
(
( ) 1 log /
2
DL
RB
P P N bits provide the resource allocation
where the value of P depends on the number of DL resource blocks as indicated in section 7.1. 6 of [3]
If the number of information bits in format 1 is equal to that for format 0/1A, one bit of value zero shall be appended to
format 1.
If the number of information bits in format 1 belongs to one of the sizes in Table 5.3.3.1.2-1, one or more zero bit(s)
shall be appended to format 1 until the payload size of format 1 does not belong to one of the sizes in Table 5.3.3.1.2-1
and not equal to that of format 0/1A.
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
[TS 36.213 clause 7.1.6.2]
In resource allocations of type 1, a resource block assignment information of size
RBG
N indicates to a scheduled UE
the PRBs from the set of PRBs from one of P RBG subsets. Also P is the RBG size associated with the system
bandwidth as shown in Table 7.1.6.1-1. A RBG subset p , where P p < 0 , consists of every P th RBG starting
from RBG p . The resource block assignment information consists of three fields [4].
The first field with
(
) ( log
2
P bits is used to indicate the selected RBG subset among P RBG subsets.
The second field with one bit is used to indicate a shift of the resource allocation span within a subset. A bit value of 1
indicates shift is triggered. Shift is not triggered otherwise.
The third field includes a bitmap, where each bit of the bitmap addresses a single PRB in the selected RBG subset in
such a way that MSB to LSB of the bitmap are mapped to the PRBs in the increasing frequency order. The PRB is
allocated to the UE if the corresponding bit value in the bit field is 1, the PRB is not allocated to the UE otherwise. The
portion of the bitmap used to address PRBs in a selected RBG subset has size
TYPE1
RB
N and is defined as
( (
1 ) ( log /
2
DL
RB
TYPE1
RB
= P P N N
The addressable PRB numbers of a selected RBG subset start from an offset, ) (
shift
p to the smallest PRB number
within the selected RBG subset, which is mapped to the MSB of the bitmap. The offset is in terms of the number of
PRBs and is done within the selected RBG subset. If the value of the bit in the second field for shift of the resource
allocation span is set to 0, the offset for RBG subset p is given by 0 ) (
shift
= p . Otherwise, the offset for RBG
subset p is given by
TYPE1
RB
subset RBG
RB shift
) ( ) ( N p N p = , where the LSB of the bitmap is justified with the highest
PRB number within the selected RBG subset. ) (
subset RBG
RB
p N is the number of PRBs in RBG subset p and can be
calculated by the following equation,
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 422
422
P
P
N
p
P
P
N
p
P
P
N
p
P
P
N
P N P
P
N
P P
P
N
p N
mod
1
,
mod
1
,
mod
1
,
1
1 mod ) 1 (
1
1
) (
DL
RB
DL
RB
DL
RB
2
DL
RB
DL
RB
2
DL
RB
2
DL
RB
subset RBG
RB
(

>
(

=
(

<

+ +
(

+
(

=

Consequently, when RBG subset p is indicated, bit i for
TYPE1
RB
0,1, , 1 i N = in the bitmap field indicates PRB
number,
( ) P p i P p P
P
p i
p n mod ) (
) (
) (
shift
2 shift subset RBG
PRB
+ + +
(
+
=
[TS 36.213 clause 7.1.7]
first
MCS
I ) in the DCI
...
else
PRB
{ }
PRB
max 0.75 , 1
PRB
N N ( =

,
PRB PRB
N N = .
[TS 36.213 clause 7.1.7.1]
The UE shall use
m
use
MCS
m
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 423
423
MCS Index
MCS
I
Modulation Order
m
Q
TBS Index
TBS
I
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
reserved 30 4
31 6

[TS 36.213 clause 7.1.7.2]
for DCI format 1A:
o the UE shall set the TBS index (
TBS
I ) equal to
MCS
I and determine its TBS by the procedure in
Section 7.1.7.2.1.
...
else
for 28 0
MCS
TBS
I ) using
MCS
I and Table 7.1.7.1-1 except if
the transport block is disabled in DCI formats 2 and 2A as specified below. For a transport block that is not
mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.1. For a
transport block that is mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in
Section 7.1.7.2.2.
for 31 29
MCS
MCS
using 28 0
MCS
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 424
424
In DCI formats 2 and 2A a transport block is disabled if 0
MCS
= I and if rv
idx
=1 otherwise the transport block
is enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
For 110 1
PRB
TBS
I ,
PRB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 425
425
TBS
I
PRB
N
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
TBS
I

PRB
N

11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
TBS
I
PRB
N
21 22 23 24 25 26 27 28 29 30
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 426
426
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
TBS
I
PRB
N
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
TBS
I
PRB
N
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 427
427
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
TBS
I
PRB
N
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
TBS
I
PRB
N
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 428
428
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
TBS
I
PRB
N
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
TBS
I
PRB
N
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 429
429
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
TBS
I
PRB
N
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
TBS
I
PRB
N
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 430
430
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376

[TS 36.306 clause 4.1]
The field ue-Category parameter defines a combined uplink and downlink capability. The parameters set by the UE
Category are defined in subclause 4.2. Tables 4.1-1 and 4.1-2 define the downlink and, respectively, uplink physical
layer parameter values for each UE Category.
DL-SCH transport
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

bits of an UL-SCH
transport block
TTI
Support for
64QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No

System Simulator:
- Cell 1.
PRB
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 431
431
size
bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776

TB
size

[bits]
Number of
PDCP SDUs
PDCP SDU size
[bits]
See note 1
104 TB
size
12096
note 2
1 8*FLOOR((TB
size
- 96)/8)
12097 TB
size
24128 2 8*FLOOR((TB
size
128)/16))
24129 TB
size
36152 3 8*FLOOR((TB
size
152)/24))
36153 TB
size
48184 4 8*FLOOR((TB
size
184)/32))
48185 TB
size
60208 5 8*FLOOR((TB
size
- 208)/40))
60209 TB
size
72240 6 8*FLOOR((TB
size
240)/48))
TB
size
>72240 7 8*FLOOR((TB
size
264)/56))
Note 1: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS
24.301 clause 9.9.4.12).


PDCP SDU size =(TB
size
N*PDCP header size - AMD PDU header size - MAC header size Size of


MAC header size =40 bits as MAC header can be

R/R/E/LCID MAC subheader (8 bits for Timing Advance) +R/R/E/LCID MAC subheader (16 bits for MAC
SDU for RLC Status PDU) +R/R/E/LCID MAC subheader (8 bits for MAC SDU for AMD PDU) =8 +16+8
bits =32 bits
OR
SDU for AMD PDU, Note: Length can be 2 bytes depending on the size of AMD PDU) +R/R/E/LCID MAC
subheader (8 bits for MAC SDU for RLC Status PDU) =8 +24+8 bits =40 bits

Therefore maximum MAC header size can be 40 bits


This gives:

size
N*16- 8*CIEL((16+(N-1)*12)/8) 64)/(8*N)) bits
TB
size

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 432
432
Max Bandwidth
Max
PRB
N
TYPE1
RB
N
10 Mhz 50 14
15 Mhz 75 16
20 Mhz 100 22

{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U S Message
repeated for values of
PRB
N from
1 to
TYPE1
RB
N as per table
7.1.7.1.2.3.2-2a and
MCS
I from 0
to 28.
- - - -
1
SS looks up
TBS
I in table 7.1.7.1-
of
MCS
I . SS looks up TB
size
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS
I .
- - - -
performed if TB
size
is less than or
- - - -
size
, in
7.1.7.1.2.3.2-2.
- - - -
Format 1 with RA type 1 and a
resource block assignment (RBA)
correspondent to
PRB
N as
scheme
MCS
I .

format 1 is equal to that for format
0/1A, one bit of value zero shall
be appended to format 1 by the
SS.

<-- MAC PDU (NxPDCP
SDUs)
DCI: (DCI Format 1, RA
type 1, RBA(
PRB
N ),
MCS
I )
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 433
433


retxBSR-Timer sf320

7.1.7.1.3 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Localised
VRB
(1)
ensure that {
when { UE on PDCCH receives DCI format 1A indicating Resource Allocation Type 2 with Localized VRB,
a resource block assignment correspondent to
PRB
N physical resource blocks and a modulation and
coding scheme
MCS
I }
PRB
N and
MCS
I
}

References: The conformance requirements covered in the current TC are specified in: TS 36.212, clauses 5.3.3.1.2 and
5.3.3.1.3; TS 36.213, clauses 7.1.6.3, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

[TS 36.212 clause 5.3.3.1.3]
DCI format 1A is used for the compact scheduling of one PDSCH codeword and random access procedure initiated by a
PDCCH order.
format 1 belongs to one of the
one or more zero bit(s) shall be
appended to format 1 by the SS
until the payload size of format 1
does not belong to one of the
sizes in Table 7.1.7.1.2.3.2-2b
and not equal to that of format
0/1A.
SDUs.
<-- (UL Grant)
the SS in step 3?
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 434
434
The following information is transmitted by means of the DCI format 1A:

Otherwise,
- Localized/Distributed VRB assignment flag 1 bit as defined in 7.1.6.3 of [3]
- Resource block assignment
(
) 2 / ) 1 ( ( log
DL
RB
DL
RB 2
+ N N bits as defined in section 7.1.6.3 of [3]:
- For localized VRB:
(
) 2 / ) 1 ( ( log
DL
RB
DL
RB 2
+ N N bits provide the resource allocation
- For distributed VRB:
- If 50
DL
RB
< N or if the format 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI
-
(
) 2 / ) 1 ( ( log
DL
RB
DL
RB 2
- Else
- 1 bit, the MSB indicates the gap value, where value 0 indicates
gap,1 gap
N N = and value 1 indicates
gap,2 gap
N N =
-
(
) 1 ) 2 / ) 1 ( ( log (
DL
RB
DL
RB 2
- Modulation and coding scheme 5bits as defined in section 7.1.7 of [3]
If the number of information bits in format 1A is less than that of format 0, zeros shall be appended to format 1A until
the payload size equals that of format 0.
If the number of information bits in format 1A belongs to one of the sizes in Table 5.3.3.1.2-1, one zero bit shall be
appended to format 1A.
...
[TS 36.213 clause 7.1.6.3]
In resource allocations of type 2, the resource block assignment information indicates to a scheduled UE a set of
contiguously allocated localized virtual resource blocks or distributed virtual resource blocks. In case of resource
allocation signalled with PDCCH DCI format 1A, 1B or 1D, one bit flag indicates whether localized virtual resource
blocks or distributed virtual resource blocks are assigned (value 0 indicates Localized and value 1 indicates Distributed
VRB assignment) while distributed virtual resource blocks are always assigned in case of resource allocation signalled
with PDCCH DCI format 1C. Localized VRB allocations for a UE vary from a single VRB up to a maximum number
of VRBs spanning the system bandwidth. For DCI format 1A the distributed VRB allocations for a UE vary from a
single VRB up to
DL
VRB
N
VRBs, where
DL
VRB
N
is defined in [3], if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or
SI-RNTI. With PDCCH DCI format 1B, 1D, or 1A with a CRC scrambled with C-RNTI, distributed VRB allocations
for a UE vary from a single VRB up to
DL
VRB
N
VRBs if
DL
RB
N
is 6-49 and vary from a single VRB up to 16 if
DL
RB
N
is 50-
110. With PDCCH DCI format 1C, distributed VRB allocations for a UE vary from
step
RB
N
VRB(s) up to

step
RB
step
RB
DL
VRB
/ N N N
VRBs with an increment step of
step
RB
N
, where
step
RB
N
value is determined depending on the downlink
system bandwidth as shown in Table 7.1.6.3-1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 435
435
Table 7.1.6.3-1:
step
RB
N
values vs. Downlink System Bandwidth
System BW
(
DL
RB
N )
step
RB
N

DCI format 1C
6-49 2
50-110 4

For PDCCH DCI format 1A, 1B or 1D, a type 2 resource allocation field consists of a resource indication value (RIV)
corresponding to a starting resource block (
start
RB ) and a length in terms of virtually contiguously allocated resource
blocks
CRBs
L . The resource indication value is defined by
if

2 / ) 1 (
DL
RB CRBs
N L then
start CRBs
DL
RB
RB L N RIV + = ) 1 (
else
) 1 ( ) 1 (
start
DL
RB CRBs
DL
RB
DL
RB
RB N L N N RIV + + =
where
CRBs
L 1 and shall not exceed
start
DL
VRB
RB N .
For PDCCH DCI format 1C, a type 2 resource block assignment field consists of a resource indication value (RIV)
start
RB =0,
step
RB
N
,
step
RB
2N
,,

step
RB
step
RB
DL
VRB
) 1 / ( N N N
) and a length in terms
of virtually contiguously allocated resource blocks (
CRBs
L =
step
RB
N
,
step
RB
2N
,,

step
RB
step
RB
DL
VRB
/ N N N
). The resource
indication value is defined by
if

2 / ) 1 (
DL
VRB CRBs
N L then
start CRBs
DL
VRB
B R L N RIV + = ) 1 (
else
) 1 ( ) 1 (
start
DL
VRB CRBs
DL
VRB
DL
VRB
B R N L N N RIV + + =
where
step
RB CRBs CRBs
N L L / = ,
step
RB start start
N RB B R / = and

step
RB
DL
VRB
DL
VRB
N N N / = . Here,
CRBs
start
DL
VRB
B R N .
[TS 36.213 clause 7.1.7]
first
MCS
I ) in the DCI
...
else
PRB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 436
436
{ }
PRB
max 0.75 , 1
PRB
N N ( =

,
PRB PRB
N N = .
[TS 36.213 clause 7.1.7.1]
The UE shall use
m
use
MCS
m
MCS Index
MCS
I
Modulation Order
m
Q
TBS Index
TBS
I
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
reserved 30 4
31 6

[TS 36.213 clause 7.1.7.2]
TBS
I ) equal to
MCS
7.1.7.2.1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 437
437
...
else
for 28 0
MCS
TBS
I ) using
MCS
I and Table 7.1.7.1-1 except if
the transport block is disabled in DCI formats 2 and 2A as specified below. For a transport block that is not
mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.1. For a
transport block that is mapped to two-layer spatial multiplexing, the TBS is determined by the procedure in
Section 7.1.7.2.2.
for 31 29
MCS
MCS
using 28 0
MCS
In DCI formats 2 and 2A a transport block is disabled if 0
MCS
= I and if rv
idx
=1 otherwise the transport block
is enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
For 110 1
PRB
TBS
I ,
PRB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 438
438
TBS
I
PRB
N
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
TBS
I

PRB
N

11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
TBS
I
PRB
N
21 22 23 24 25 26 27 28 29 30
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 439
439
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
TBS
I
PRB
N
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
TBS
I
PRB
N
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 440
440
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
TBS
I
PRB
N
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
TBS
I
PRB
N
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 441
441
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
TBS
I
PRB
N
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
TBS
I
PRB
N
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 442
442
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
TBS
I
PRB
N
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
TBS
I
PRB
N
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 443
443
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376

[TS 36.306 clause 4.1]
DL-SCH transport
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

bits of an UL-SCH
transport block
TTI
Support for
64QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No

System Simulator:
- Cell 1.
PRB
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 444
444
size
bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776

TB
size

[bits]
Number of
PDCP SDUs
PDCP SDU size
[bits]
See note 1
104 TB
size
12096
note 2
1 8*FLOOR((TB
size
- 96)/8)
12097 TB
size
24128 2 8*FLOOR((TB
size
128)/16))
24129 TB
size
36152 3 8*FLOOR((TB
size
152)/24))
36153 TB
size
48184 4 8*FLOOR((TB
size
184)/32))
48185 TB
size
60208 5 8*FLOOR((TB
size
- 208)/40))
60209 TB
size
72240 6 8*FLOOR((TB
size
240)/48))
TB
size
>72240 7 8*FLOOR((TB
size
264)/56))
24.301 clause 9.9.4.12).


PDCP SDU size =(TB
size
N*PDCP header size -AMD PDU header size - MAC header size Size of


SDU for RLC Status PDU) +R/R/E/LCID MAC subheader (8 bits for MAC SDU for AMD PDU) =8 +16+8
bits =32 bits
Or
SDU for AMD PDU, Note: Length can be 2 bytes depending on the size of AMD PDU) +R/R/E/LCID MAC
subheader (8 bits for MAC SDU for RLC Status PDU) =8 +24+8 bits =40 bits



This gives:

size
N*16- 8*CIEL((16+(N-1)*12)/8) 64)/(8*N)) bits.
TB
size

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 445
445
Max Bandwidth
Max
PRB
N
10 Mhz 50
15 Mhz 75
20 Mhz 100

{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U S Message
PRB
N from
1 to Max
PRB
N as per table
7.1.7.1.3.3.2-2a and
MCS
I from 0
to 28.
- - - -
1
SS looks up
TBS
I in table 7.1.7.1-
of
MCS
I . SS looks up TB
size
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS
I .
- - - -
performed if TB
size
is less than or
- - - -
size
, in
7.1.7.1.3.3.2-2.
- - - -
Format 1A with RA type 2 using
Localized VRB and a resource
block assignment (RBA)
correspondent to
PRB
N as
scheme
MCS
I .

format 1A is less than that of
format 0, zeros shall be appended
by the SS to format 1A until the
payload size equals that of format
<-- MAC PDU (NxPDCP
SDUs)
DCI: (DCI Format 1A, RA
type 2,
Localized/Distributed VRB
assignment flag =0,
RBA(
PRB
N ),
MCS
I )
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 446
446

retxBSR-Timer sf320

7.1.7.1.4 DL-SCH transport block size selection / DCI format 1A / RA type 2 / Distributed
VRB
(1)
ensure that {
when { UE on PDCCH receives DCI format 1A indicating Resource Allocation Type 2 with Distributed
VRB, a resource block assignment correspondent to
PRB
N physical resource blocks and a modulation
and coding scheme
MCS
I }
PRB
N and
MCS
I
}

References: The conformance requirements covered in the current TC are specified in: TS 36.212, clauses 5.3.3.1.2 and
5.3.3.1.3; TS 36.213, clauses 7.1.6.3, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

[TS 36.212 clause 5.3.3.1.3]
DCI format 1A is used for the compact scheduling of one PDSCH codeword and random access procedure initiated by a
PDCCH order.

0.

format 1A belongs to one of the
one zero bit shall be appended by
the SS to format 1A.
request the SS transmits UL
Grantfor transmitting loop back
PDCP SDUs.
<-- (UL Grant) - -
the SS in step 3?
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 447
447
Otherwise,
- Localized/Distributed VRB assignment flag 1 bit as defined in 7.1.6.3 of [3]
- Resource block assignment
(
) 2 / ) 1 ( ( log
DL
RB
DL
RB 2
+ N N bits as defined in section 7.1.6.3 of [3]:
- For localized VRB:
(
) 2 / ) 1 ( ( log
DL
RB
DL
RB 2
- For distributed VRB:
- If 50
DL
RB
< N or if the format 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI
-
(
) 2 / ) 1 ( ( log
DL
RB
DL
RB 2
- Else
- 1 bit, the MSB indicates the gap value, where value 0 indicates
gap,1 gap
N N = and value 1 indicates
gap,2 gap
N N =
-
(
) 1 ) 2 / ) 1 ( ( log (
DL
RB
DL
RB 2
- Modulation and coding scheme 5bits as defined in section 7.1.7 of [3]
If the number of information bits in format 1A is less than that of format 0, zeros shall be appended to format 1A until
the payload size equals that of format 0.
...
[TS 36.213 clause 7.1.6.3]
In resource allocations of type 2, the resource block assignment information indicates to a scheduled UE a set of
contiguously allocated localized virtual resource blocks or distributed virtual resource blocks. In case of resource
allocation signalled with PDCCH DCI format 1A, 1B or 1D, one bit flag indicates whether localized virtual resource
blocks or distributed virtual resource blocks are assigned (value 0 indicates Localized and value 1 indicates Distributed
VRB assignment) while distributed virtual resource blocks are always assigned in case of resource allocation signalled
with PDCCH DCI format 1C. Localized VRB allocations for a UE vary from a single VRB up to a maximum number
of VRBs spanning the system bandwidth. For DCI format 1A the distributed VRB allocations for a UE vary from a
single VRB up to
DL
VRB
N
VRBs, where
DL
VRB
N
is defined in [3], if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or
SI-RNTI. With PDCCH DCI format 1B, 1D, or 1A with a CRC scrambled with C-RNTI, distributed VRB allocations
for a UE vary from a single VRB up to
DL
VRB
N
VRBs if
DL
RB
N
is 6-49 and vary from a single VRB up to 16 if
DL
RB
N
is 50-
110. With PDCCH DCI format 1C, distributed VRB allocations for a UE vary from
step
RB
N
VRB(s) up to

step
RB
step
RB
DL
VRB
/ N N N
VRBs with an increment step of
step
RB
N
, where
step
RB
N
value is determined depending on the downlink
system bandwidth as shown in Table 7.1.6.3-1.
Table 7.1.6.3-1:
step
RB
N
values vs. Downlink System Bandwidth
System BW
(
DL
RB
N )
step
RB
N

DCI format 1C
6-49 2
50-110 4

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 448
448
For PDCCH DCI format 1A, 1B or 1D, a type 2 resource allocation field consists of a resource indication value (RIV)
start
RB ) and a length in terms of virtually contiguously allocated resource
blocks
CRBs
L . The resource indication value is defined by
if

2 / ) 1 (
DL
RB CRBs
N L then
start CRBs
DL
RB
RB L N RIV + = ) 1 (
else
) 1 ( ) 1 (
start
DL
RB CRBs
DL
RB
DL
RB
where
CRBs
start
DL
VRB
RB N .
For PDCCH DCI format 1C, a type 2 resource block assignment field consists of a resource indication value (RIV)
start
RB =0,
step
RB
N
,
step
RB
2N
,,

step
RB
step
RB
DL
VRB
) 1 / ( N N N
) and a length in terms
of virtually contiguously allocated resource blocks (
CRBs
L =
step
RB
N
,
step
RB
2N
,,

step
RB
step
RB
DL
VRB
/ N N N
). The resource
indication value is defined by
if

2 / ) 1 (
DL
VRB CRBs
N L then
start CRBs
DL
VRB
B R L N RIV + = ) 1 (
else
) 1 ( ) 1 (
start
DL
VRB CRBs
DL
VRB
DL
VRB
B R N L N N RIV + + =
where
step
RB CRBs CRBs
N L L / = ,
step
RB start start
N RB B R / = and

step
RB
DL
VRB
DL
VRB
N N N / = . Here,
CRBs
start
DL
VRB
B R N .
[TS 36.213 clause 7.1.7]
first
MCS
I ) in the DCI
...
else
PRB
{ }
PRB
max 0.75 , 1
PRB
N N ( =

,
PRB PRB
N N = .
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 449
449
[TS 36.213 clause 7.1.7.1]
The UE shall use
m
use
MCS
m
MCS Index
MCS
I
Modulation Order
m
Q
TBS Index
TBS
I
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
reserved 30 4
31 6

[TS 36.213 clause 7.1.7.2]
TBS
I ) equal to
MCS
7.1.7.2.1.
...
else
- for 28 0
MCS
TBS
I ) using
MCS
7.1.7.2.2.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 450
450
- for 31 29
MCS
MCS
using 28 0
MCS
MCS
= I and if rv
idx
enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
For 110 1
PRB
TBS
I ,
PRB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 451
451
TBS
I
PRB
N
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
TBS
I

PRB
N

11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
TBS
I
PRB
N
21 22 23 24 25 26 27 28 29 30
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 452
452
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
TBS
I
PRB
N
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
TBS
I
PRB
N
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 453
453
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
TBS
I
PRB
N
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
TBS
I
PRB
N
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 454
454
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
TBS
I
PRB
N
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
TBS
I
PRB
N
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 455
455
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
TBS
I
PRB
N
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
TBS
I
PRB
N
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 456
456
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376

[TS 36.306 clause 4.1]
DL-SCH transport
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

bits of an UL-SCH
transport block
TTI
Support for
64QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No

System Simulator:
- Cell 1.
PRB
- DCI format 1C shall be used for BCCH, PCH and RAR (note).
UE:
None.
Preamble:
NOTE: To maximize resources for DL-SCH TB size testing for DCI format 1A/RA type 2/Distributed VRB then
the SS need to use DCI Format 1C for BCCH, PCH and RAR
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 457
457
size
bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776

TB
size

[bits]
Number of
PDCP SDUs
PDCP SDU size
[bits]
See note 1
104 TB
size
12096
note 2
1 8*FLOOR((TB
size
- 96)/8)
12097 TB
size
24128 2 8*FLOOR((TB
size
128)/16))
24129 TB
size
36152 3 8*FLOOR((TB
size
152)/24))
36153 TB
size
48184 4 8*FLOOR((TB
size
184)/32))
48185 TB
size
60208 5 8*FLOOR((TB
size
- 208)/40))
60209 TB
size
72240 6 8*FLOOR((TB
size
240)/48))
TB
size
>72240 7 8*FLOOR((TB
size
264)/56))
24.301 clause 9.9.4.12).


PDCP SDU size =(TB
size
N*PDCP header size - AMD PDU header size - MAC header size
Size of Timing Advance RLC Status PDU size) / N, where

AMD PDU header size is CIEL[(16+(N-1)*12)/8] bytes which includes 16 standard AM header
and (N-1) Length indicators; and


R/R/E/LCID MAC subheader (8 bits for Timing Advance) +R/R/E/LCID MAC subheader (16 bits
for MAC SDU for RLC Status PDU) +R/R/E/LCID MAC subheader (8 bits for MAC SDU for
AMD PDU) =8 +16 +8 bits =32 bits
OR
R/R/E/LCID MAC subheader (8 bits for Timing Advance) +R/R/E/LCID MAC subheader (24 bits
for MAC SDU for AMD PDU, Note: Length can be 2 bytes depending on the size of AMD PDU)
+R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Status PDU) =8 +24+8 bits =40
bits


This gives:

size
N*16- 8*CIEL((16+(N-1)*12)/8) 64)/(8*N)) bits.
TB
size

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 458
458
Max Bandwidth
Max
PRB
N
MAX VRB
10 Mhz 50 16
15 Mhz 75 16
20 Mhz 100 16

{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U S Message
PRB
N from
1 to 16[MAX VRB] and
MCS
I from
0 to 28.
- - - -
1
SS looks up
TBS
I in table 7.1.7.1-
of
MCS
I . SS looks up TB
size
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS
I .
- - - -
performed if TB
size
is less than or
TS 36.213 clause 7.1.7 is lower
- - - -
size
, in
7.1.7.1.4.3.2-2.
- - - -
Format 1A with RA type 2 using
Distributed VRB and a resource
block assignment (RBA)
correspondent to
PRB
N as
scheme
MCS
I .

format 1A is less than that of
format 0, zeros shall be appended
by the SS to format 1A until the
payload size equals that of format
0.

<-- MAC PDU (NxPDCP
SDUs)
type 2,
Localized/Distributed VRB
assignment flag =1,
RBA(
PRB
N ),
MCS
I )
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 459
459

retxBSR-Timer sf320

7.1.7.1.5 DL-SCH transport block size selection / DCI format 2A / RA type 0 / Two
transport blocks enabled / Transport block to codeword swap flag value set to 0
(1)
ensure that {
when { UE has two transport blocks enabled and on PDCCH receives DCI format 2A indicating Resource
Allocation Type 0, a resource block assignment correspondent to
PRB
N physical resource blocks, the
Transport block to codeword swap flag value set to 0 and a modulation and coding scheme
MCS
I for
two transport blocks }
then { UE decodes the received transport blocks of sizes correspondent to the read
PRB
N and
MCS
I for transport block 1 and
MCS
I for transport block 2 and forwards it to higher layers }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.212, clauses 5.3.3.1.2,
5.3.3.1.5 and 5.3.3.1.5A; TS 36.213, clauses 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

[TS 36.212 clause 5.3.3.1.5]
format 1A belongs to one of the
one zero bit shall be appended by
the SS to format 1A.
SDUs.
<-- (UL Grant) - -
the SS in step 3?
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 460
460
Table 5.3.3.1.5-1: Transport block to codeword mapping
(two transport blocks enabled)
transport block
to codeword
swap flag value
codeword 0
(enabled)
codeword 1
(enabled)
0 transport block 1 transport block 2

(one transport block enabled)
Transport block 1 transport block 2
codeword 0
(enabled)
codeword 1
(disabled)
enabled disabled
transport
block 1
-
disabled enabled
transport
block 2
-

[TS 36.212 clause 5.3.3.1.5A]
- For resource allocation type 0 as defined in section 7.1.6.1 of [3]
-
(
P N /
DL
RB
bits provide the resource allocation
...
where the value of P depends on the number of DL resource blocks as indicated in subclause [7.1.6.1] of [3]
...
- Transport block to codeword swap flag 1 bit
In addition, for transport block 1:
- New data indicator 1 bit
- Redundancy version 2 bits
...
Precoding information number of bits as specified in Table 5.3.3.1.5A-1
If both transport blocks are enabled, the transport block to codeword mapping is specified according to Table
5.3.3.1.5-1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 461
461
In case one of the transport blocks is disabled, the transport block to codeword swap flag is reserved and the transport
block to codeword mapping is specified according to Table 5.3.3.1.5-2.
The precoding information field is defined according to Table 5.3.3.1.5A-2. For a single enabled codeword, index 1 in
Table 5.3.3.1.5A-2 is only supported for retransmission of the corresponding transport block if that transport block has
previously been transmitted using two layers with open-loop spatial multiplexing.
For transmission with 2 antenna ports, the precoding information field is not present. The number of transmission layers
is equal to 2 if both codewords are enabled; transmit diversity is used if codeword 0 is enabled while codeword 1 is
disabled.
Table 5.3.3.1.5A-1: Number of bits for precoding information
Number of antenna ports at eNodeB Number of bits for precoding information
2 0
4 2

Table 5.3.3.1.5A-2: Content of precoding information field for 4 antenna ports
One codeword:
Codeword 0 enabled,
Codeword 1 disabled
Two codewords:
Codeword 0 enabled,
Codeword 1 enabled
Bit field
mapped to
index
Message
Bit field
mapped
to index
Message
0 4 layers: Transmit
diversity
0 2 layers: precoder
cycling with large delay
CDD
CDD
CDD
2 reserved 2 4 layers: precoder
CDD
3 reserved 3 reserved

[TS 36.213 clause 7.1.6.1]
number of RBGs (
RBG
DL
RB
N PRBs is given by
(
P N N
RBG
/
DL
RB
= where

P N /
DL
RB
DL
RB

P N P N /
DL
RB
DL
RB
. The
bitmap is of size
RBG
RBG
otherwise.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 462
462
DL
RB
N
(P)
10 1
11 26 2
27 63 3
64 110 4

[TS 36.213 clause 7.1.7]
first
MCS
I ) in the DCI
...
else
PRB
{ }
PRB
max 0.75 , 1
PRB
N N ( =

,
PRB PRB
N N = .
[TS 36.213 clause 7.1.7.1]
The UE shall use
m
use
MCS
m
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 463
463
MCS Index
MCS
I
Modulation Order
m
Q
TBS Index
TBS
I
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
reserved 30 4
31 6

[TS 36.213 clause 7.1.7.2]
TBS
I ) equal to
MCS
7.1.7.2.1.
...
else
- for 28 0
MCS
TBS
I ) using
MCS
7.1.7.2.2.
- for 31 29
MCS
MCS
using 28 0
MCS
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 464
464
MCS
= I and if rv
idx
enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
For 110 1
PRB
TBS
I ,
PRB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 465
465
TBS
I
PRB
N
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
TBS
I

PRB
N

11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
TBS
I
PRB
N
21 22 23 24 25 26 27 28 29 30
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 466
466
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
TBS
I
PRB
N
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
TBS
I
PRB
N
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 467
467
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
TBS
I
PRB
N
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
TBS
I
PRB
N
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 468
468
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
TBS
I
PRB
N
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
TBS
I
PRB
N
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 469
469
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
TBS
I
PRB
N
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
TBS
I
PRB
N
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 470
470
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376

[TS 36.306 clause 4.1]
DL-SCH transport
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

bits of an UL-SCH
transport block
TTI
Support for
64QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No

...
System Simulator
- Cell 1.
PRB
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] condition 2TX to configure MIMO.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 471
471
size
bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 472
472
Table 7.1.7.1.5.3.2-2: Number of downlink PDCP SDUs and PDCP SDU size used as test data for
transport block 1 and transport block 2
Total TB
size
(sum of the sizes of TB
size#1
and TB
size#2
)
(bits)
Number of
PDCP SDUs
PDCP SDU size
(bits]
See note 1
12120 136
size
TB See note 2
1 8*FLOOR((TB
size
- 120)/8)
24152 12121
size
TB

2 8*FLOOR((TB
size
152)/16))
36176 24153
size
TB
3 8*FLOOR((TB
size
176)/24))
48208 36177
size
TB
4 8*FLOOR((TB
size
208)/32))
60232 48209
size
TB
5 8*FLOOR((TB
size
- 232/40))
72264 60233
size
TB
6 8*FLOOR((TB
size
264)/48))
72288 72265
size
TB
7 8*FLOOR((TB
size
288)/56))
84320 72289
size
TB
8 8*FLOOR((TB
size
320)/64))
96348 84321
size
TB
9 8*FLOOR((TB
size
348)/72))
108376 96349
size
TB
10 8*FLOOR((TB
size
376)/80))
120400 108377
size
TB
11 8*FLOOR((TB
size
400)/88))
132432 120401
size
TB
12 8*FLOOR((TB
size
432)/96))
144456 132433
size
TB
13 8*FLOOR((TB
size
456)/104))
144457
size
TB
14 8*FLOOR((TB
size
488)/112))
24.301 clause 9.9.4.12).


PDCP SDU size =(Total TBsize N*PDCP header size - AMD PDU header size - - MAC header size
Size of Timing Advance RLC Status PDU size) / N, where


AMD PDU header size is CEIL[(Number of TBs *16+(N-1)*12)/8] bytes which includes one 16 bit standard
AM header per TB and N-1 Length indicators of 12 bits correspondig to the worst case when one of the
PDCP SDU is split between the two transport blocks. If no PDCP SDU is split between the transport blocks
then there will be only N-2 LIs and MAC padding will occur instead of one LI;

MAC header size =R/R/E/LCID MAC subheader (8 bits for Timing Advance) +R/R/E/LCID MAC
subheader (24 bits for MAC SDU for RLC data PDU)+Number of TBs R/R/E/LCID MAC subheaders (8
bits for MAC SDU for RLC status PDU) =8 +24 +Number of TBs * 8 bits;If status PDU is not included or,
MAC LI is included for MAC SDU for RLC status PDU instead of RLC data PDU, MAC padding will occur in
place of unused bits;.

Size of Timing Advance MAC CE is 8 bits (if no Timing Advance needs to be sent, MAC padding will occur
instead);

RLC Status PDU size =16 bits (including one ACK SQN triggered in execution X+1, due to loop back
transmission in execution X and as all loop backed PDUs in execution X have been correctly received, the
status PDU will carry an ACK SQN only.

This gives:

PDCP SDU size =8*FLOOR((Total TBsize N*16- 8*CEIL((2*16+(N-1)*12)/8) 72)/(8*N)) bits

total TBsize that can be tested (corresponding to N=1, and PDCP SDU size of 16) is 136 bits.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 473
473
Max Bandwidth
Max
PRB
N Allowed
PRB
N Values
10 Mhz 50 2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18, 20, 21, 23, 24, 26,
27, 29, 30, 32, 33, 35, 36, 38, 39, 41, 42, 44, 45, 47, 48,
50
15 Mhz 75 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32,
35, 36, 39, 40, 43, 44 ,47, 48, 51, 52, 55, 56, 59, 60, 63,
64, 67, 68, 71, 72, 75
20 Mhz 100 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64,
68, 72, 76, 80, 84, 88, 92, 96, 100

{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

U S Message
PRB
N as per table 7.1.7.1.5.3.2-
2a and for each
MCS#1
I from 0 to
28 and
MCS#2
I from 0 to 28
- - - -
1
SS looks up
TBS#1
I for transport
block 1 and in table 7.1.7.1-1 in
TS 36.213 based on the value of
MCS#1
I . SS looks up TB
size#1
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS#1
I .

SS looks up
TBS#2
I for transport
MCS#2
I . SS looks up TB
size#2
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS#2
I .
- - - -
performed if the sum of the sizes
of TB
size#1
and TB
size#2
is less than
or equal to UE capability
Maximum number of DL-SCH
transport block bits received within
a TTI as specified in Table
7.1.7.1.5.3.2-1 and larger than or
equal to 136 bits as specified in
Table 7.1.7.1.5.3.2-2, and the
effective channel code rate, as
defined in TS 36.213 clause 7.1.7,
is lower than or equal to 0.930.
- - - -
SDUs for transport block 1 and 2
depending on TB
size#1
, and
- - - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 474
474

None
7.1.7.1.6 DL-SCH Transport Block Size selection / DCI format 2A / RA type 1 / Two
transport blocks enabled / Transport block to codeword swap flag value set to 1
(1)
ensure that {
when { UE has two transport blocks enabled and on PDCCH receives DCI format 2A indicating Resource
Allocation Type 1, a resource block assignment correspondent to
PRB
N physical resource blocks, the
Transport block to codeword swap flag value set to 1 and a modulation and coding scheme
MCS
I for
two transport blocks }
then { UE decodes the two transport blocks of sizes correspondent to the read
PRB
N and
MCS
I for
transport block 1 and
MCS
I for transport block 2 and forwards it to higher layers }
}

5.3.3.1.5 and 5.3.3.1.5A; TS 36.213, clauses 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2 and 7.1.7.2.1; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.2]
...
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

[TS 36.212 clause 5.3.3.1.5]
TB
size#2
in accordance with Table
7.1.7.1.5.3.2-2.

3 SS transmits the PDCP SDUs for
transport block 1 and 2
per transport block and indicates
on PDCCH DCI Format 2A with
RA type 0 and a resource block
assignment (RBA) correspondent
to
PRB
N as specified in 7.1.6.1 in
TS 36.213 and modulation and
coding scheme
MCS#1
I for
transport block 1 and
MCS#2
I for
transport block 2. The N PDCP
SDUs are split between MAC
PDU 1 and 2;
<-- Transport block 1:
MAC PDU
Transport block 2:
MAC PDU
type 0, RBA(
PRB
N ),
MCS#1
I ,
MCS#2
I )
- -
3a SS transmits one or more UL
Grants sufficient for transmitting
loop back PDCP SDUs.
<-- (UL Grant) - -
the SS in step 3?
--> ( N

x PDCP SDUs) 1 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 475
475
(two transport blocks enabled)
transport block
to codeword
swap flag value
codeword 0
(enabled)
codeword 1
(enabled)

[TS 36.212 clause 5.3.3.1.5A]
...
- For resource allocation type 1 as defined in section 7.1.6.2 of [3]
- ( )
(
P
2
log bits of this field are used as a header specific to this resource allocation type to indicate the
selected resource blocks subset
- 1 bit indicates a shift of the resource allocation span
-
(
( )
(
( ) 1 log /
2
DL
RB
P P N bits provide the resource allocation
where the value of P depends on the number of DL resource blocks as indicated in subclause [7.1.6.1] of [3]
...
- Transport block to codeword swap flag 1 bit
...
If both transport blocks are enabled, the transport block to codeword mapping is specified according to Table
5.3.3.1.5-1.
...
[TS 36.213 clause 7.1.6.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 476
476
number of RBGs (
RBG
DL
RB
N PRBs is given by
(
P N N
RBG
/
DL
RB
= where

P N /
DL
RB
DL
RB

P N P N /
DL
RB
DL
RB
. The
bitmap is of size
RBG
RBG
otherwise.
DL
RB
N
(P)
10 1
11 26 2
27 63 3
64 110 4

[TS 36.213 clause 7.1.7]
first
MCS
I ) in the DCI
...
else
PRB
{ }
PRB
max 0.75 , 1
PRB
N N ( =

,
PRB PRB
N N = .
[TS 36.213 clause 7.1.7.1]
The UE shall use
m
use
MCS
m
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 477
477
MCS Index
MCS
I
Modulation Order
m
Q
TBS Index
TBS
I
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
reserved 30 4
31 6

[TS 36.213 clause 7.1.7.2]
TBS
I ) equal to
MCS
7.1.7.2.1.
...
else
- for 28 0
MCS
TBS
I ) using
MCS
7.1.7.2.2.
- for 31 29
MCS
MCS
using 28 0
MCS
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 478
478
MCS
= I and if rv
idx
enabled.
higher layers.
[TS 36.213 clause 7.1.7.2.1]
For 110 1
PRB
TBS
I ,
PRB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 479
479
TBS
I
PRB
N
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
TBS
I

PRB
N

11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
TBS
I
PRB
N
21 22 23 24 25 26 27 28 29 30
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 480
480
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
TBS
I
PRB
N
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
TBS
I
PRB
N
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 481
481
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
TBS
I
PRB
N
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
TBS
I
PRB
N
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 482
482
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
TBS
I
PRB
N
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
TBS
I
PRB
N
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 483
483
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
TBS
I
PRB
N
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
TBS
I
PRB
N
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 484
484
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376

[TS 36.306 clause 4.1]
DL-SCH transport
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

bits of an UL-SCH
transport block
TTI
Support for
64QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No

...
System Simulator
- Cell 1.
PRB
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] condition 2TX to configure MIMO.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 485
485
size
bits of a DL-SCH
transport block
Category 1 10296
Category 2 51024
Category 3 75376
Category 4 75376
Category 5 149776

Table 7.1.7.1.6.3.2-2: Number of downlink PDCP SDUs and PDCP SDU size used as test data for each
MIMO flow
TB
size

[bits]
Number of
PDCP SDUs
per MIMO
flow
PDCP SDU size
[bits]
See note 1
12056 72
size
TB
note 2
1 8*FLOOR((TB
size
- 56)/8)
24088 12057
size
TB
2 8*FLOOR((TB
size
88)/16))
36112 24089
size
TB
3 8*FLOOR((TB
size
112)/24))
48144 36113
size
TB
4 8*FLOOR((TB
size
144)/32))
60168 48145
size
TB
5 8*FLOOR((TB
size
- 168)/40))
72200 60169
size
TB
6 8*FLOOR((TB
size
200)/48))
72201
size
TB
7 8*FLOOR((TB
size
224)/56))
24.301 clause 9.9.4.12).


PDCP SDU size =(TB
size
Number of MIMO flows*N*PDCP header size - AMD PDU header size - MAC
header size Size of Timing Advance) / (Number of MIMO flows *N), where

AMD PDU header size is CEIL[(16+(N-1)*12)/8] bytes which includes 16 standard AM header and (N-1)
MAC header size =R/R/E/LCID MAC subheader (8 bits for Timing Advance) +R/R/E/LCID MAC
subheader (8 bits for MAC SDU) =8 +8 bits
Size of Timing Advance MAC CE is 8 bits (if no Timing Advance needs to be sent, padding will occur
instead)

This gives:

size
N*16- 8*CEIL((16+(N-1)*12)/8) 24)/(8*N)) bits
Note 2: According to TS 36.213 Table 7.1.7.2.1-1 and the final PDCP SDU size formula in Note 1, the smallest TB
size


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 486
486
Max Bandwidth
Max
PRB
N Allowed
PRB
N Values
10 Mhz 50 2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18, 20, 21, 23, 24, 26,
27, 29, 30, 32, 33, 35, 36, 38, 39, 41, 42, 44, 45, 47, 48,
50
15 Mhz 75 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31, 32,
35, 36, 39, 40, 43, 44 ,47, 48, 51, 52, 55, 56, 59, 60, 63,
64, 67, 68, 71, 72, 75
20 Mhz 100 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64,
68, 72, 76, 80, 84, 88, 92, 96, 100
Note: Maximum bandwidth for EUTRA bands is 10/15/20 Mhz.

{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}

Table 7.1.7.1.6.3.2-2c:
MCS#1
I and
MCS#2
I test points for transport block 1 and transport block 2 for
different UE Categories
MCS test
point index
MCS Index
transport
block 1
MCS#1
I
MCS Index transport block 2,
MCS#2
I
(Note 1)
UE
Category 1
UE
Category 2
UE
Category 3
UE
Category 4
UE
Category 5
0 0 FFS FFS FFS FFS FFS
Note 1: The MCS index for transport block 2 has been selected to avoid limitations due to UE
capabilities for the different UE Categories.

U S Message
- EXCEPTION: Steps 1 to 4 are - - - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 487
487
PRB
N as per table 7.1.7.1.6.3.2-
2a and for each
MCS#1
I and
MCS#2
I value for MCS test points
0 to 28 as per table 7.1.7.1.6.3.2-
2c.
1
SS looks up
TBS#1
I for transport
MCS#1
I . SS looks up TB
size#1
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS#1
I .

SS looks up
TBS#2
I for transport
MCS#2
I . SS looks up TB
size#2
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS#2
I .

- - - -
performed if the sum of the sizes
of TB
size#1
and TB
size#2
is less than
or equal to UE capability
Maximum number of DL-SCH
transport block bits received within
a TTI as specified in Table
7.1.7.1.6.3.2-1 and larger than or
equal to 72 bits as specified in
Table 7.1.7.1.6.3.2-2, and the
effective channel code rate, as
defined in TS 36.213 clause 7.1.7,
is lower than or equal to 0.930.
- - - -
SDUs for transport block 1
depending on TB
size#1
, in
7.1.7.1.6.3.2-2.

SS creates one or more PDCP
SDUs for transport block 2
depending on TB
size#2
, in
7.1.7.1.6.3.2-2.
- - - -
3 SS transmits the PDCP SDUs for
transport block 1 and 2
per transport block and indicates
on PDCCH DCI Format 2A with
RA type 1 and a resource block
assignment (RBA) correspondent
to
PRB
N as specified in 7.1.6.1 in
TS 36.213, transport block to
codeword swap flag value set
to 1 and modulation and coding
scheme
MCS#1
I for transport block
<-- Transport block 1:
MAC PDU (N
1
x PDCP
SDUs)
Transport block 2:
MAC PDU (N
2
x PDCP
SDUs)
type 1, RBA(
PRB
N ),
Transport block to
codeword swap flag value
set to=1,
MCS#1
I ,
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 488
488

None
7.1.7.2 UL-SCH transport block size support
7.1.7.2.1 UL-SCH transport block size selection / DCI format 0
(1)
ensure that {
when { UE has pending data for transmission and receives a Resource Block Assignment correspondent
to
PRB
MCS
I for PUSCH scheduling }
then { UE transmits MAC PDU on PUSCH on the granted resources using a transport block size
correspondent to the read
PRB
N and
MCS
I }
}

36.213, clauses 8.1, 8.6, 8.6.1, 8.6.2 and 7.1.7.2.1; TS 36.211, clause 5.3.3; and TS 36.306 clause 4.1.
[TS 36.212 clause 5.3.3.1.1]
- Flag for format0/format1A differentiation 1 bit, where value 0 indicates format 0 and value 1 indicates format
1A
(
) 2 / ) 1 ( ( log
UL
RB
UL
RB 2
+ N N bits
- N
UL_hop
~
i n
PRB
-
( |
.
|
\
|
+
UL_hop
UL
RB
UL
RB 2
subframe
1 and
MCS#2
I for transport block
2.

MCS#2
I )
3a SS transmits one or more UL
Grants sufficient for transmitting
loop back PDCP SDUs.
<-- (UL Grant) - -
the SS in step 3?
--> ( N
1
x PDCP SDUs,
N
2
x PDCP SDUs)
1 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 489
489
-
( |
.
|
\
|
+ ) 2 / ) 1 ( ( log
UL
RB
UL
RB 2
N N bits provide the resource allocation in the UL subframe as defined in
section 8.1 of [3]
- Modulation and coding scheme and redundancy version 5 bits as defined in section 8.6 of [3]
[TS 36.213 clause 8.1]
The resource allocation information indicates to a scheduled UE a set of contiguously allocated virtual resource block
indices denoted by
VRB
n . A resource allocation field in the scheduling grant consists of a resource indication value
(RIV) corresponding to a starting resource block (
START
RB ) and a length in terms of contiguously allocated resource
blocks (
CRBs
L 1). The resource indication value is defined by
if

2 / ) 1 (
UL
RB CRBs
N L then
START CRBs
UL
RB
) 1 ( RB L N RIV + =
else
) 1 ( ) 1 (
START
UL
RB CRBs
UL
RB
UL
RB
A UE shall discard PUSCH resource allocation in the corresponding PDCCH with DCI format 0 if consistent control
information is not detected.
[TS 36.213 clause 8.6]
To determine the modulation order, redundancy version and transport block size for the physical uplink shared channel,
the UE shall first
- read the 5-bit modulation and coding scheme and redundancy version field (
MCS
I ) in the DCI, and
- check the CQI request bit in DCI, and
- compute the total number of allocated PRBs (
PRB
N ) based on the procedure defined in Section 8.1, and
- compute the number of coded symbols for control information..
[TS 36.213 clause 8.6.1]
For 28 0
MCS
I , the modulation order (
m
Q ) is determined as follows:
If the UE is capable of supporting 64QAM in PUSCH and has not been configured by higher layers to transmit
only QPSK and 16QAM, the modulation order is given by
'
m
Q in Table 8.6.1-1.
If the UE is not capable of supporting 64QAM in PUSCH or has been configured by higher layers to transmit
only QPSK and 16QAM,
'
m
Q is first read from Table 8.6.1-1. The modulation order is set to ) , 4 min(
'
m m
Q Q = .
If the parameter ttiBundling provided by higher layers is set to TRUE, then the resource allocation size is
restricted to 3
PRB
N and the modulation order is set to 2 =
m
Q .
For 31 29
MCS
I , If 29
MCS
= I , the CQI request bit in DCI format 0 is set to 1 and 4
PRB
N , the modulation order
is set to 2 =
m
Q . Otherwise, the modulation order shall be determined from the DCI transported in the latest PDCCH
with DCI format 0 for the same transport block using 28 0
MCS
I . If there is no PDCCH with DCI format 0 for the
MCS
I , the modulation order shall be determined from
the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport
block is semi-persistently scheduled, or,
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 490
490
the random access response grant for the same transport block, when the PUSCH is initiated by the random access
response grant.
The UE shall use
MCS
I and Table 8.6.1-1 to determine the redundancy version (rv
idx
) to use in the physical uplink shared
channel.
Table 8.6.1-1: Modulation, TBS index and redundancy version table for PUSCH
MCS Index
MCS
I
Modulation Order
'
m
Q
TBS Index
TBS
I
Redundancy
Version
rv
idx

0 2 0 0
1 2 1 0
2 2 2 0
3 2 3 0
4 2 4 0
5 2 5 0
6 2 6 0
7 2 7 0
8 2 8 0
9 2 9 0
10 2 10 0
11 4 10 0
12 4 11 0
13 4 12 0
14 4 13 0
15 4 14 0
16 4 15 0
17 4 16 0
18 4 17 0
19 4 18 0
20 4 19 0
21 6 19 0
22 6 20 0
23 6 21 0
24 6 22 0
25 6 23 0
26 6 24 0
27 6 25 0
28 6 26 0
29
reserved
1
30 2
31 3

[TS 36.213 clause 8.6.2]
For 28 0
MCS
TBS
I ) using
MCS
I and Table 8.6.1-1. The UE shall then
follow the procedure in Section 7.1.7.2.1 to determine the transport block size.
For 31 29
MCS
I , If 29
MCS
= I , the CQI request bit in DCI format 0 is set to 1 and 4
PRB
N , then there is no
transport block for the UL-SCH and only the control information feedback for the current PUSCH reporting mode is
transmitted by the UE. Otherwise, the transport block size shall be determined from the initial PDCCH for the same
transport block using 28 0
MCS
I . If there is no initial PDCCH with DCI format 0 for the same transport block using
28 0
MCS
I , the transport block size shall be determined from
the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport
block is semi-persistently scheduled, or,
the random access response grant for the same transport block, when the PUSCH is initiated by the random
[TS 36.213 clause 7.1.7.2.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 491
491
For 110 1
PRB
TBS
I ,
PRB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 492
492
TBS
I
PRB
N
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
TBS
I

PRB
N

11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
TBS
I
PRB
N
21 22 23 24 25 26 27 28 29 30
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 493
493
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
TBS
I
PRB
N
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
TBS
I
PRB
N
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 494
494
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
TBS
I
PRB
N
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
TBS
I
PRB
N
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 495
495
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
TBS
I
PRB
N
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
TBS
I
PRB
N
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 496
496
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
TBS
I
PRB
N
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
TBS
I
PRB
N
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 497
497
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376

[TS 36.211 clause 5.3.3]
The block of complex-valued symbols ) 1 ( ),..., 0 (
symb
M d d is divided into
PUSCH
sc symb
M M sets, each corresponding
to one SC-FDMA symbol. Transform precoding shall be applied according to
1 ,..., 0
1 ,..., 0
) (
1
) (
PUSCH
sc symb
PUSCH
sc
1
0
2
PUSCH
sc
PUSCH
sc
PUSCH
sc
PUSCH
sc
PUSCH
sc
=
=
+ = +

M M l
M k
e i M l d
M
k M l z
M
i
M
ik
j

resulting in a block of complex-valued symbols ) 1 ( ),..., 0 (
symb
M z z . The variable
RB
sc
PUSCH
RB
PUSCH
sc
N M M = , where
PUSCH
RB
M represents the bandwidth of the PUSCH in terms of resource blocks, and shall fulfil
UL
RB
PUSCH
RB
5 3 2
5 3 2 N M =

where
5 3 2
, , is a set of non-negative integers.
[TS 36.306 clause 4.1]
DL-SCH transport
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

bits of an UL-SCH
transport block
TTI
Support for
64QAM in UL
Category 1 5160 No
Category 2 25456 No
Category 3 51024 No
Category 4 51024 No

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 498
498
System Simulator:
- Cell 1.
Table 5.6.1-1 in [31](to enable testing of
PRB
UE:
None.
Preamble:
size
bits of an UL-SCH
transport block
TTI
Category 1 5160
Category 2 25456
Category 3 51024
Category 4 51024
Category 5 75376

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 499
499
TB
size

[bits]
Number of
PDCP SDUs,
N
SDUs

PDCP SDU size
[bits]
See note 1
104 TB
size
12096
note 2
1 8*FLOOR((TB
size
96)/8)
12097 TB
size
24128 2 8*FLOOR((TB
size
128)/16))
24129 TB
size
36152 3 8*FLOOR((TB
size
152)/24))
36153 TB
size
48184 4 8*FLOOR((TB
size
184)/32))
48185 TB
size
60208 5 8*FLOOR((TB
size
208)/40))
60209 TB
size
72240 6 8*FLOOR((TB
size
240)/48))
TB
size
>72240 7 8*FLOOR((TB
size
264/56))
24.301 clause 9.9.4.12).

N PDCP SDUs are transmitted in N AMD PDUs concatenated into a MAC PDU. The PDCP SDU size of
each PDCP SDU is

PDCP SDU size =(TB
size
N*PDCP header size - N*AMD PDU header size - MAC header Size of
Timing Advance RLC Status PDU size size) / N, where

AMD PDU header size is 16 bits;
MAC header si40 bits as MAC header size can be:

MAC SDU for RLC Status PDU) +R/R/E/LCID MAC subheader (8 bits for MAC SDU for AMD PDU) =8 +
16 +8 bits=32 bits
or

MAC SDU for AMD PDU, Note: Length can be of 2 bytes depending upon the size of AMD PDU)+
R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Status PDU) +=8+24 +8 bits =40 bits

Therefore Maximum MAC header size can be 40 bits


RLC Status PDU size =16 bitsze =

This gives:

size
N*16- 8*CIEL((16+(N-1)*12)/8) 64)/(8*N)) bits.
TB
size

Max Bandwidth
Max
PRB
N
10 Mhz 50
15 Mhz 75
20 Mhz 100
Note: Maximum bandwidth for EUTRA bands is 10/15/20 Mhz.

U S Message
1 The SS ignores scheduling
requests and does not allocate
any uplink grant.
- - - -
- EXCEPTION: Steps 2 to 7 are - - - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 500
500

None.
PRB
N from
1 to Max
PRB
N and
MCS
I from 0
to 28, where
PRB
N
satisfies
values equal to
UL
RB
5 3 2
5 3 2 N

and
where
5 3 2
, ,
is a set of non-
negative integers.
2
SS looks up
TBS
I in table 8.6.1-1
in TS 36.213 based on the value
of
MCS
I . SS looks up TB
size
in
table 7.1.7.2.1-1 in TS 36.213
based on values of
PRB
N and
TBS
I .
- - - -
performed if TB
size
is less than or
number of UL-SCH transport
7.1.7.2.1.3.2-2.
- - - -
size
, in
7.1.7.2.1.3.2-2.
- - - -
4 SS transmits all PDCP SDUs
(N
SDUs
) as created in step 3 in a
MAC PDU.
<-- MAC PDU (N
SDUs
x PDCP
SDU)
- -
5 The SS responds to any
scheduling requests by a PUSCH
scheduling indicating DCI Format
0 with a RVI correspondent to
PRB
N as specified in 8.1 in TS
36.213 and modulation and
coding scheme
MCS
I as specified
in Table 8.6.1-1 in TS 36.213.
<-- (UL Grant)
DCI: (DCI Format 0, RVI
(
PRB
N ),
MCS
I )
- -
6 The SS ignores scheduling
requests and does not allocate
any uplink grant.
- - - -
the SS in step 4 using the
Resource Block Assignment and
modulation and coding scheme as
configured by the SS in step 5?
--> MAC PDU (N
SDUs
x PDCP
SDU)
1 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 501
501
7.1.8 Reporting of Rank Indicator (RI)
7.1.8.1 Periodic RI reporting using PUCCH / Category 1 UE / Transmission mode 3/4
(1)
ensure that {
when { Category 1 UE is configured to transmission mode 3}
then { UE always reports RI equals to one}
}

(2)
ensure that {
when { Category 1 UE is configured to transmission mode 4}
then { UE always reports RI equals to one}
}

References: The conformance requirements covered in the present TC are specified in: TS 36.306 clause 4 and clause
4.1, TS 36.213 clause 7.2.2.
[TS 36.306, clause 4]
The following subclauses define the UE radio access capability parameters. Only parameters for which there is the
possibility for UEs to signal different values are considered as UE radio access capability parameters. Therefore,
mandatory capabilities that are the same for all UEs are not listed here.
[TS 36.306, clause 4.1]
DL-SCH transport
within a TTI
Maximum number
of bits of a DL-
SCH transport
block recei ved
within a TTI
Total number of
soft channel bits
Maximum number
of supported
layers for spatial
multiplexing in DL
Category 1 10296 10296 250368 1
Category 2 51024 51024 1237248 2
Category 3 102048 75376 1237248 2
Category 4 150752 75376 1827072 2
Category 5 299552 149776 3667200 4

[TS 36.213, clause 7.2.2]
A UE is semi-statically configured by higher layers to periodically feed back different CQI, PMI, and RI on the PUCCH
using the reporting modes given in Table 7.2.2-1 and described below.
Table 7.2.2-1: CQI and PMI Feedback Types for PUCCH reporting Modes
PMI Feedback Type
No PMI Single PMI
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 502
502
P
U
C
C
H

C
Q
I

F
e
e
d
-
b
a
c
k

T
y
p
e

Wideband Mode 1-0 Mode 1-1
(wideband CQI)

UE Selected Mode 2-0 Mode 2-1
(subband CQI)

For each of the transmission modes defined in Section 7.1, the following reporting modes are supported on PUCCH:
- Transmission mode 1 : Modes 1-0, 2-0
- Transmission mode 8 : Modes 1-1, 2-1 if the UE is configured with PMI/RI reporting; modes 1-0, 2-0 if the UE is
configured without PMI/RI reporting
Four CQI/PMI and RI reporting types with distinct periods and offsets are supported for each PUCCH reporting mode
as given in Table 7.2.2-3:
- Type 1 report supports CQI feedback for the UE selected sub-bands
- Type 2 report supports wideband CQI and PMI feedback.
- Type 3 report supports RI feedback
- Type 4 report supports wideband CQI
The periodicity
p
N (in subframes) and offset
, OFFSET CQI
N (in subframes) for CQI/PMI reporting are determined based on
the parameter cqi-pmi-ConfigIndex (
/ CQI PMI
I ) given in Table 7.2.2-1A for FDD and table 7.2.2-1C for TDD. The periodicity
RI
M and relative offset
, OFFSET RI
N for RI reporting are determined based on the parameter ri-ConfigIndex (
RI
I ) given in
Table 7.2.2-1B. Both cqi-pmi-ConfigIndex and ri-ConfigIndex are configured by higher layer signalling. The relative
reporting offset for RI
, OFFSET RI
N takes values from the set {0, 1,..., ( 1)}
p
N
- Wideband feedback
- Mode 1-1 description:
- In the subframe where RI is reported (only for transmission mode 4 and transmission mode 8):
- A UE shall determine a RI assuming transmission on set S subbands.
- The UE shall report a type 3 report consisting of one RI
- In the subframe where CQI/PMI is reported:
- A single precoding matrix is selected from the codebook subset assuming transmission on set S
subbands
- A UE shall report a type 2 report on each respective successive reporting opportunity consisting of
- A single wideband CQI value which is calculated assuming the use of a single precoding matrix in
all subbands and transmission on set S subbands.
- The selected single precoding matrix indicator (wideband PMI)
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 503
503
- When RI>1, a 3-bit wideband spatial differential CQI, which is shown in Table 7.2-2.
- For transmission mode 4 and transmission mode 8, the PMI and CQI are calculated conditioned on the
last reported periodic RI. For other transmission modes they are calculated conditioned on
transmission rank 1.
System Simulator:
- Cell 1
- System Simulator transmits according to the rank reported by UE
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 504
504
U - S Message
a matched identity.
- - - -
3 SS responses with Random Access Preamble <-- Random Access Response - -
RRCConnectionRequest message
--> MAC PDU
- -
element with matching Contention Resolution
Identity
<-- MAC PDU
- -
RRCConnectionSetupComplete message to
confirm the successful completion of the
connection establishment and to initiate the
session management procedure by including
the SERVICE REQUEST message..
--> MAC PDU
- -
- EXCEPTION: Step 7 is repeated 5 times - - - -
7 CHECK: Does the UE transmit PUCCH type 3
report with RI set to 1? (NOTE)
--> (RI) 1 P
SecurityModeCommand
<-- MAC PDU
(SecurityModeCommand)
- -
9 The UE transmits MAC PDU containing a
SecurityModeComplete
--> MAC PDU
(SecurityModeComplete)
- -
reconfigure the UE transmission mode to tm4
<-- MAC PDU
(RRCConnectionReconfiguration)
- -
message
--> MAC PDU
(RRCConnectionReconfigurationC
omplete)
- -
- EXCEPTION: Step 12 is repeated 5 times - - - -
12 CHECK: Does the UE transmit PUCCH type 3
report with RI set to 1? (NOTE)
--> (RI) 2 P
13 Check: Does the test result of CALL generic
indicate that UE is in E-UTRA
- - 2 -
Note: The period P that report the RI is calculated as such: according to the default configuration in 35.508, the cqi-
pmi-ConfigIndex =25(FDD)/24(TDD), ri-ConfigIndex =483(FDD) / 484(TDD), P =1.6s(FDD)/1.6s(TDD)
and RI offset
, OFFSET CQI
N =6ms(FDD)/7ms(TDD)

Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 505
505
Table 7.1.8.1.3.3-2: PhysicalConfigDedicated-DEFAULT (step 10, Table 7.1.8.1.3.2-1)
PhysicalConfigDedicated-DEFAULT ::=SEQUENCE {
antennaInfo CHOICE {
defaultValue NULL
explicitValue SEQUENCE { 2TX
transmissionMode tm4
codebookSubsetRestriction CHOICE {
n2TxAntenna-tm4 '111111' BIT STRING
(SIZE (6))

}
ue-TransmitAntennaSelection CHOICE {
Release NULL
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 510
510
7.2 RLC
7.2.1 General
For UM tests, the UM test DRB is set up using the Generic Procedure described in clause 4.5 of [18], with the
parameters described in clause 4.8.2.1.3.1 of [18], except for the tests that explicitly specify a different DRB
configuration.
For AM tests, the AM test DRB is set up using the Generic Procedure described in clause 4.5 of [18], with the
parameters described in clause 4.8.2.1.3.2 of [18], except for the tests that explicitly specify a different DRB
configuration.
Unless specified otherwise in the test procedure sequence, the data field of each RLC PDU transmitted by the SS
contains a complete RLC SDU.
7.2.2 Unacknowledged mode
7.2.2.1 UM RLC / Segmentation and reassembly / 5-bit SN / Framing info field
(1)
ensure that {
when { UE receives a 5 bit SN configured UMD PDU containing a FI field set to 00 }
then { UE correctly decodes the received UMD PDU }
}
(2)
ensure that {
}
(3)
ensure that {
}
(4)
ensure that {
}

6.2.2.6.
[TS 36.322, clause 6.2.1.3]

An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. When the 5 bit SN is configured, the
length of the fixed part of the UMD PDU header is one byte. When the 10 bit SN is configured, the fixed part of the
UMD PDU header is identical to the fixed part of the AMD PDU header, except for D/C, RF and P fields all being
replaced with R1 fields. The extension part of the UMD PDU header is identical to the extension part of the AMD PDU
header (regardless of the configured SN size).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 511
511

[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
The FI field indicates whether a RLC SDU is segmented at the beginning and/or at the end of the Data field.
Specifically, the FI field indicates whether the first byte of the Data field corresponds to the first byte of a RLC SDU,
and whether the last byte of the Data field corresponds to the last byte of a RLC SDU. The interpretation of the FI field
is provided in Table 6.2.2.6-1.
Table 6.2.2.6-1: FI field interpretation
Value Description
00 First byte of the Data field corresponds to the first byte of a RLC SDU.
Last byte of the Data field corresponds to the last byte of a RLC SDU.
Last byte of the Data field does not correspond to the last byte of a RLC SDU.
10 First byte of the Data field does not correspond to the first byte of a RLC SDU.

System Simulator:
- Cell 1.
UE:
None.
Preamble:
applicable for the configured UM DRB.
Table 7.2.2.1.3.1-1: RLC parameters
Uplink RLC
sn-FieldLength size5
Downlink RLC

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 512
512
U - S Message
1 The SS transmits UMD PDU#1 containing a
complete RLC SDU#1 (FI field =00).
<-- UMD PDU#1 - -
2 Check: Does the UE transmit RLC SDU#1? --> (RLC SDU#1) 1 P
3 The SS transmits UMD PDU#2 containing the
first segment of RLC SDU#2 (FI field =01).
<-- UMD PDU#2 - -
second segment of RLC SDU#2 (FI field =11).
<-- UMD PDU#3 - -
last segment of RLC SDU#2 (FI field =10).
<-- UMD PDU#4 - -
6 Check: Does the UE transmit RLC SDU#2? --> (RLC SDU#2) 2,3,
4
P

None.
7.2.2.2 UM RLC / Segmentation and reassembly / 10-bit SN / Framing info field
(1)
ensure that {
}
(2)
ensure that {
}
(3)
ensure that {
}
(4)
ensure that {
}
6.2.2.6.
[TS 36.322, clause 6.2.1.3]

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 513
513

[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
Value Description

System Simulator:
- Cell 1.
UE:
None.
Preamble:
U - S Message
1 The SS transmits UMD PDU#1 containing a
<-- UMD PDU#1 - -
<-- UMD PDU#2 - -
<-- UMD PDU#3 - -
<-- UMD PDU#4 - -
6 Check: Does the UE transmit RLC SDU#2? --> (RLC SDU#2) 2, 3,
4
P

None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 514
514
7.2.2.3 UM RLC / Reassembly / 5-bit SN / LI value >PDU size
(1)
ensure that {
when { UE receives a 5 bit SN configured RLC PDU with Length Indicator value larger than RLC PDU
size }
then { UE discards the RLC PDU }
}

See TS 36.322 clauses 6.2.2.5 and 5.5.1
References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1 and
6.2.2.5.
[TS 36.322, clause 5.5.1]
When an RLC entity receives an RLC PDU that contains reserved or invalid values, the RLC entity shall:
[TS 36.322, clause 6.2.2.5]
Length: 11 bits.
The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU
delivered/received by an UM or an AM RLC entity. The first LI present in the RLC data PDU header corresponds to the
first Data field element present in the Data field of the RLC data PDU, the second LI present in the RLC data PDU
header corresponds to the second Data field element present in the Data field of the RLC data PDU, and so on. The
value 0 is reserved.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Uplink RLC
Downlink RLC

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 515
515
U - S Message
- EXCEPTION: the behaviour described in table
7.2.2.3.3.2-2 runs in parallel with steps 1 to 5
below.
- - - -
1 The SS transmits UMD PDU#1 containing first
segment of RLC SDU#1.
<-- UMD PDU#1 (SN=0) - -
2 The SS transmits UMD PDU#2 containing last
segment of RLC SDU#1 and first segment of
RLC SDU#2.
<-- UMD PDU#2 (SN=1) - -
segment of RLC SDU#2, first segment of RLC
SDU#3 and with Length Indicator that points
beyond the end of the UMD PDU#3.
<-- UMD PDU#3 (SN=2) - -
<-- UMD PDU#4 (SN=3) - -
5 The SS transmits UMD PDU#5 containing RLC
SDU#4.
<-- UMD PDU#5 (SN=4) - -

U - S Message
1 The UE transmits RLC SDU#1. --> (RLC SDU#1) - -
2 Check: Does the UE transmit RLC SDU#2? --> (RLC SDU#2) 1 F

None.
7.2.2.4 UM RLC / Reassembly / 10-bit SN / LI value >PDU size
(1)
ensure that {
when { UE receives an RLC PDU with Length Indicator value larger than RLC PDU size }
then { UE discards the RLC PDU }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1.
[TS 36.322, clause 5.5.1]
System Simulator:
- Cell 1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 516
516
UE:
None.
Preamble:
U - S Message
- EXCEPTION: The behaviour described in table
7.2.2.4.3.2-2 runs in parallel with steps 1 to 5
below.
- - - -
<-- UMD PDU#1 (SN=0) - -
segment of RLC SDU#1 and first segment of
RLC SDU#2.
<-- UMD PDU#2 (SN=1) - -
segment of RLC SDU#2, first segment of RLC
SDU#3 and with Length Indicator that points
beyond the end of the RLC PDU#3.
<-- UMD PDU#3 (SN=2) - -
<-- UMD PDU#4 (SN=3) - -
5 The SS transmits UMD PDU#5 containing RLC
SDU#4.
<-- UMD PDU#5 (SN=4) - -

U - S Message

None.
7.2.2.5 UM RLC / Correct use of sequence numbering
7.2.2.5.1 UM RLC / 5-bit SN / Correct use of sequence numbering
(1)
ensure that {
when { UE transmits the first PDU }
then { UE sets the sequence Number field equal to 0 }
}
(2)
ensure that {
when { UE transmits subsequent PDUs }
then { SN incremented by 1 for each PDU transmitted }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 517
517
(3)
with { UE in E-UTRA RRC_CONNECTED state and an UM RLC DRB is configured using 5 bit SN }
ensure that {
when { UE transmits more than 32 PDUs }
then { UE wraps the Sequence Number after transmitting the 32 PDU }
}
(4)
ensure that {
when { more than 32 PDUs are sent to UE }
then { UE accepts PDUs with SNs that wrap around every 32

PDU }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause
5.1.2.1.1, 5.1.2.2, 6.2.1.3, 6.2.2.3 and 7.1.
[TS 36.322, clause 5.1.2.1.1]
When delivering a new UMD PDU to lower layer, the transmitting UM RLC entity shall:
- set the SN of the UMD PDU to VT(US), and then increment VT(US) by one.
[TS 36.322, clause 5.1.2.2]
The receiving UM RLC entity shall maintain a reordering window according to state variable VR(UH) as follows:
- a SN falls within the reordering window if (VR(UH) UM_Window_Size) <=SN <VR(UH);
- a SN falls outside of the reordering window otherwise.
When receiving an UMD PDU from lower layer, the receiving UM RLC entity shall:
- either discard the received UMD PDU or place it in the reception buffer (see sub clause 5.1.2.2.2);
- if the received UMD PDU was placed in the reception buffer:
- update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop t-Reordering as
needed (see sub clause 5.1.2.2.3);

When an UMD PDU with SN =x is received from lower layer, the receiving UM RLC entity shall:
- if VR(UR) <x <VR(UH) and the UMD PDU with SN =x has been received before; or
- if (VR(UH) UM_Window_Size) <=x <VR(UR):
- discard the received UMD PDU;
- else:
- place the received UMD PDU in the reception buffer.

When an UMD PDU with SN =x is placed in the reception buffer, the receiving UM RLC entity shall:
- if x falls outside of the reordering window:
- update VR(UH) to x +1;
- reassemble RLC SDUs from any UMD PDUs with SN that falls outside of the reordering window, remove
RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the
RLC SN if not delivered before;
- if VR(UR) falls outside of the reordering window:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 518
518
- set VR(UR) to (VR(UH) UM_Window_Size);
- if the reception buffer contains an UMD PDU with SN =VR(UR):
- update VR(UR) to the SN of the first UMD PDU with SN >current VR(UR) that has not been received;
- reassemble RLC SDUs from any UMD PDUs with SN <updated VR(UR), remove RLC headers when doing
so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered
before;

[TS 36.322, clause 6.2.1.3]


[TS 36.322, clause 6.2.2.3]

The SN field indicates the sequence number of the corresponding UMDThe sequence number is incremented by one
for every UMD...
[TS 36.322, clause 7.1]

All state variables and all counters are non-negative integers.

All state variables related to UM data transfer can take values from 0 to [2
[sn-FieldLength]
1]. All arithmetic operations
contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e.
final value =[value from arithmetic operation] modulo 2
[sn-FieldLength]
.

When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.

VR(UH) UM_Window_Size shall be assumed as the modulus base at the receiving side of an UM RLC entity. This
modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. (VR(UH)
UM_Window_Size) <=SN <VR(UH) is evaluated as [(VR(UH) UM_Window_Size) (VR(UH)
UM_Window_Size)] modulo 2
[sn-FieldLength]
<=[SN (VR(UH) UM_Window_Size)] modulo 2
[sn-FieldLength]
<[VR(UH)
(VR(UH) UM_Window_Size)] modulo 2
[sn-FieldLength]
).

Each transmitting UM RLC entity shall maintain the following state variables:
a) VT(US)
This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU. It is initially set to
0, and is updated whenever the UM RLC entity delivers an UMD PDU with SN =VT(US).
Each receiving UM RLC entity shall maintain the following state variables:
a) VR(UR) UM receive state variable
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 519
519
This state variable holds the value of the SN of the earliest UMD PDU that is still considered for reordering. It is
initially set to 0.
b) VR(UX) UM t-Reordering state variable
This state variable holds the value of the SN following the SN of the UMD PDU which triggered t-Reordering.
c) VR(UH) UM highest received state variable
This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received
UMD PDUs, and it serves as the higher edge of the reordering window. It is initially set to 0.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.5.1.3.1-1
Table 7.2.2.5.1.3.1-1: RLC parameters
Uplink RLC
Downlink RLC

U - S Message/PDU/SDU
- EXCEPTION: Step 3 to 4 is executed 31 times. - - - -
1 The SS transmits an UMD PDU. SN equals 0. <-- UMD PDU - -
2 Check: Does the UE transmit an UMD PDU
with SN =0?
--> UMD PDU 1 P
3 The SS transmits an UMD PDU. SN equals 1
and is incremented for each PDU transmitted.
<-- UMD PDU - -
with SN increased by 1 compared with the
previous one?
--> UMD PDU 2 P
with SN=0?
--> UMD PDU 3, 4 P

7.2.2.5.1.3.3 Specific message contents
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 520
520
7.2.2.5.2 UM RLC / 10-bit SN / Correct use of Sequence numbering
(1)
ensure that {
then { UE sets the Sequence Number field equal to 0 }
}
(2)
ensure that {
}
(3)
ensure that {
when { UE transmits more than 1024

PDUs }
}
(4)
ensure that {
when { more than 1024

PDUs are sent to UE }

PDU }
}
5.1.2.1.1, 5.1.2.2, 6.2.1.3, 6.2.2.3 and 7.1.
[TS 36.322, clause 5.1.2.1.1]
When delivering a new UMD PDU to lower layer, the transmitting UM RLC entity shall:
- set the SN of the UMD PDU to VT(US), and then increment VT(US) by one.
[TS 36.322, clause 5.1.2.2]
- update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop t-Rreordering as

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 521
521
- else:

before;

[TS 36.322, clause 6.2.1.3]


[TS 36.322, clause 6.2.2.3]

The SN field indicates the sequence number of the corresponding UMDThe sequence number is incremented by one
for every UMD...
[TS 36.322, clause 7.1]


All state variables related to UM data transfer can take values from 0 to [2
[sn-FieldLength]
1]. All arithmetic operations
contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e.
final value =[value from arithmetic operation] modulo 2
[sn-FieldLength]
).

When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 522
522
VR(UH) UM_Window_Size shall be assumed as the modulus base at the receiving side of an UM RLC entity. This
modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. (VR(UH)
UM_Window_Size) <=SN <VR(UH) is evaluated as [(VR(UH) UM_Window_Size) (VR(UH)
UM_Window_Size)] modulo 2
[sn-FieldLength]
<=[SN (VR(UH) UM_Window_Size)] modulo 2
[sn-FieldLength]
<[VR(UH)
(VR(UH) UM_Window_Size)] modulo 2
[sn-FieldLength]
).

Each transmitting UM RLC entity shall maintain the following state variables:
a) VT(US)
This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU. It is initially
set to 0, and is updated whenever the UM RLC entity delivers an UMD PDU with SN =VT(US).
Each receiving UM RLC entity shall maintain the following state variables:
a) VR(UR) UM receive state variable
This state variable holds the value of the SN of the earliest UMD PDU that is still considered for reordering. It is
initially set to 0.
b) VR(UX) UM t-Reordering state variable
This state variable holds the value of the SN following the SN of the UMD PDU which triggered t-Reordering.
c) VR(UH) UM highest received state variable
This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received
UMD PDUs, and it serves as the higher edge of the reordering window. It is initially set to 0.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with PDCP Data PDUs using 7 bit SN length.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 523
523
- EXCEPTION: Steps 3 to 4 are executed 1023
times.
- - - -
with SN =0?
--> UMD PDU 1 P
3 The SS transmits an UMD PDU. SN equals 1
and is incremented for each PDU transmitted.
<-- UMD PDU - -
previous one?
--> UMD PDU 2 P
with SN=0?
--> UMD PDU 3, 4 P

None.
7.2.2.6 UM RLC / Concatenation, segmentation and reassembly
(1)
ensure that {
when { The UE has multiple RLC SDUs in the transmission buffer that fits into the available UMD
PDU size }
then { The UE concatenates the RLC SDUs in the transmission buffer into one UMD PDU and
transmits it}
}
(2)
ensure that {
when { The UE receives UMD PDUs containing concatenated RLC SDUs}
then { The UE reassembles the RLC SDUs in accordance with the Framing Info and Length Indicators
indicated in UMD PDUs }
}
(3)
ensure that {
when { The UE has RLC SDU in the transmission buffer that does not fit into the available UMD PDU
size }
then { The UE segments the RLC SDU in accordance with the Framing Info and Length Indicators
indicated in UMD PDUs }
}

4.2.1.2.2, 4.2.1.2.3, 4.4, 6.2.1.3 and 6.2.2.6.
[TS 36.322, clause 4.2.1.2.2]
When a transmitting UM RLC entity forms UMD PDUs from RLC SDUs, it shall:
- segment and/or concatenate the RLC SDUs so that the UMD PDUs fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity notified by lower layer;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 524
524
- include relevant RLC headers in the UMD PDU.
[TS 36.322, clause 4.2.1.2.3]
When a receiving UM RLC entity receives UMD PDUs, it shall:

- reassemble RLC SDUs from the reordered UMD PDUs (not accounting for RLC PDUs for which losses have
been detected) and deliver the RLC SDUs to upper layer in ascending order of the RLC SN;

[TS 36.322, clause 4.4]
The following functions are supported by the RLC sub layer:

- concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer);

[TS 36.322, clause 6.2.1.3]
UMD PDU consists of a Data field and an UMD PDU header.
UMD PDU header consists of a fixed part (fields that are present for every UMD PDU) and an extension part (fields
that are present for an UMD PDU when necessary). The fixed part of the UMD PDU header itself is byte aligned and
consists of a FI, an E and a SN. The extension part of the UMD PDU header itself is byte aligned and consists of E(s)
and LI(s).
An UMD PDU header consists of an extension part only when more than one Data field elements are present in the
UMD PDU, in which case an E and a LI are present for every Data field element except the last. Furthermore, when an
UMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI.
E FI SN
Data
...
Oct N
Oct 1
Oct 2

Figure 6.2.1.3-1: UMD PDU with 5 bit SN (No LI)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 525
525
R1 R1 R1 FI E SN
SN
Data
...
Oct 3
Oct N
Oct 1
Oct 2

Figure 6.2.1.3-2: UMD PDU with 10 bit SN (No LI)

LI
2
E LI
2
(ifK>=3)
E LI
1
LI
1
E FI SN
Data
OctN
Oct1
Oct2
Oct3
Oct4
...
LI
K-1
E LI
K-1
E LI
K-2
LI
K-2
...
Padding
E LI
K
LI
K
Oct[2.5+1.5*K-1]
Oct[2.5+1.5*K-2]
Oct[2.5+1.5*K-3]
Oct[2.5+1.5*K-4]
Oct[2.5+1.5*K-5]
Oct[2.5+1.5*K]
Present
ifK>=3

Figure 6.2.1.3-3: UMD PDU with 5 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, )

LI
2
E LI
2
E LI
1
LI
1
E FI SN
Data
OctN
Oct1
Oct2
Oct3
Oct4
...
LI
K
E LI
K
E LI
K-1
LI
K-1
Oct[2+1.5*K-1]
...
Oct[2+1.5*K-2]
Oct[2+1.5*K-3]
Oct[2+1.5*K]

Figure 6.2.1.3-4: UMD PDU with 5 bit SN (Even number of LIs, i.e. K = 2, 4, 6, )

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 526
526
LI
2
E LI
2
(ifK>=3)
E LI
1
LI
1
R1 R1 R1 FI E SN
SN
Data
OctN
Oct1
Oct2
Oct3
Oct4
Oct5
...
LI
K-1
E LI
K-1
E LI
K-2
LI
K-2
...
Padding
E LI
K
LI
K
Oct[2.5+1.5*K]
Oct[2.5+1.5*K-1]
Oct[2.5+1.5*K-2]
Oct[2.5+1.5*K-3]
Oct[2.5+1.5*K-4]
Oct[2.5+1.5*K+1]
Present
ifK>=3

Figure 6.2.1.3-5: UMD PDU with 10 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, )

LI
2
E LI
2
E LI
1
LI
1
R1 R1 R1 FI E SN
SN
Data
OctN
Oct1
Oct2
Oct3
Oct4
Oct5
...
LI
K
E LI
K
E LI
K-1
LI
K-1
Oct[2+1.5*K]
...
Oct[2+1.5*K-1]
Oct[2+1.5*K-2]
Oct[2+1.5*K+1]

Figure 6.2.1.3-6: UMD PDU with 10 bit SN (Even number of LIs, i.e. K = 2, 4, 6, )

[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 527
527
Value Description

System Simulator:
- Cell 1.
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 528
528
U - S Message
1 The SS does not allocate any uplink grant. - - - -
2 The SS transmits UMD PDU#1. This PDU
carries SDU#1 with size of 50 bytes.
<-- UMD PDU#1 (RLC SDU#1) - -
4 SS transmits UL grants to enable UE to return
RLC SDU#1 and RLC SDU#2 both in one
UMD PDU.
<-- (UL grants) - -
5 Check: Does UE transmit RLC SDU#1 and
RLC SDU#2 within UMD PDU with FI field set
to 00, E field in the fixed part set to 1, first E
field in the extension part set to 0 and first LI
field set to 50 bytes?
--> UMD PDU#1 (RLC SDU#1 and
RLC SDU#2)
1 P
5A The SS does not allocate any uplink grant. - - - -
6 SS transmits an UMD PDU#3 including RLC
SDU#3 and RLC SDU#4 each with size of 50
bytes. Header of UMD PDU#3 contains
FI=00, E=1, SN=2, E
1
=0, LI
1
=50.
<-- UMD PDU#3 (RLC SDU#3 and
RLC SDU#4)
- -
7 The SS waits for 60 ms and then allocates 2
UL grants (UL grant allocation type 2) to
enable UE to return each RLC SDU in one
UMD PDU.
<-- (UL grants) - -
8 Check: Does UE transmit RLC SDU#3 within
an UMD PDU with FI field set to 00 and E
field in the fixed part set to 0?
--> UMD PDU#3 (RLC SDU#3) 2 P
9 Check: Does UE transmit RLC SDU#4 within
an UMD PDU with FI field set to 00 and E
field in the fixed part set to 0?
--> UMD PDU#4 (RLC SDU#4) 2 P
11 The SS waits for 60 ms and then allocates 2
UL grants (UL grant allocation type 2) to
enable UE to return RLC SDU#5 in two UMD
PDUs.
<-- (UL grants) - -
12 Check: Does UE transmit 1
st
part of RLC
SDU#5 within UMD PDU#5 with FI field set to
01 and E field in the fixed part set to 0?
--> UMD PDU#5 3 P
13 Check: Does UE transmit last part of RLC
SDU#5 within an UMD PDU#6 with FI field set
to 10and E field in the fixed part set to 0?
--> UMD PDU#6 3 P

None.
7.2.2.7 UM RLC / In sequence delivery of upper layer PDUs without residual loss of
RLC PDUs / Maximum re-ordering delay below t-Reordering
(1)
with { UE in E-UTRAN RRC_CONNECTED state }
ensure that {
when { UE receives missing PDUs whose SN is within the reordering window before t-Reordering has
expired }
then { RLC reassembles and reorders the UMD PDUs and delivers them to the upper layer in
sequence }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 529
529
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 5.1.2.2.
[TS 36.322, clause 5.1.2.2]

- else:

before;
- if t-Reordering is running:
- if VR(UX) <=VR(UR); or
- if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH)::
- stop and reset t-Reordering;
- if t-Reordering is not running (includes the case when t-Reordering is stopped due to actions above):
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 530
530
- if VR(UH) >VR(UR):
- start t-Reordering;
- set VR(UX) to VR(UH).
System Simulator:
- Cell 1.
UE:
None.
Preamble
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.7.3.1-1
Downlink RLC
t-Reordering ms200

U - S Message
1 The SS transmits an UMD PDU. This PDU
carries SDU#1. SN equals 0.
<-- UMD PDU#1 - -
2A The SS does not allocate any uplink grant. - - - -
contains the last part of SDU#4. SN equals 3.
The UE starts t-Reordering.
<-- UMD PDU#4 - -
contains the last part of SDU#3, and the 1
st

part of SDU#4. SN equals 2.
<-- UMD PDU#3 - -
carries SDU#2 and the 1
st
part of SDU#3. SN
equals 1. (Note)
<-- UMD PDU#2 - -
5A The SS waits for 60 ms and then allocates 3
UL grants (UL grant allocation type 2) of size
enough for the UE to loop back one SDU in
one UMD PDU
- - - -
Note: The UE stops t-Reordering, reassembles UMD PDUs and delivers RLC SDU#2, RLC SDU#3 and RLC
SDU#4 to the upper layer in sequence.

None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 531
531
7.2.2.8 UM RLC / In sequence delivery of upper layer PDUs without residual loss of
RLC PDUs / Maximum re-ordering delay exceeds t-Reordering
(1)
ensure that {
when { a PDU is received out of order after t-Reordering has expired }
then { UE discards the corresponding PDU and delivers all correctly received RLC SDUs to upper
layer in the correct order }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.1.2.2.2,
5.1.2.2.3 and 5.1.2.2.4.
[TS 36.322, clause 5.1.2.2.2]
- else:
[TS 36.322, clause 5.1.2.2.3]
before;
- if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH):
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 532
532
[TS 36.322, clause 5.1.2.2.4]
When t-Reordering expires, the receiving UM RLC entity shall:
- update VR(UR) to the SN of the first UMD PDU with SN >=VR(UX) that has not been received;
- reassemble RLC SDUs from any UMD PDUs with SN <updated VR(UR), remove RLC headers when doing so
and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Downlink RLC
t-Reordering ms200

U - S Message
1 The SS transmits RLC PDU#1 containing first
Note T
1

<-- UMD PDU#1 - -
2 The SS does not transmit RLC PDU#2
containing last segment of RLC SDU#1.
- - - -
3 The SS transmits RLC PDU#3 containing RLC
SDU#2.
<-- UMD PDU#3 - -
3A Check 1: Does the UE transmit RLC SDU#2
after t-Reordering (200 ms) expiry?
Note T
2

Check 2: Is (T
2
T
1
) >t-reordering?
--> (RLC SDU#2) 1 P
3B The SS transmits RLC PDU#2 containing last
<-- UMD PDU#2 - -
4 Check: Does the UE transmit RLC SDU#1
within 100 ms?
--> (RLC SDU#1) 1 F

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 533
533
None.
7.2.2.9 UM RLC / In sequence delivery of upper layer PDUs with residual loss of
RLC PDUs / Maximum re-ordering delay exceeds t-Reordering
(1)
ensure that {
when { UE detects that RLC PDUs constructing different RLC SDUs are lost }
then { UE delivers all received RLC SDUs to upper layer in the correct order }
}

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.1.2.2.2,
5.1.2.2.3 and 5.1.2.2.4.
[TS 36.322, clause 5.1.2.2.2]
- else:
[TS 36.322, clause 5.1.2.2.3]
before;
- if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH):
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 534
534
[TS 36.322, clause 5.1.2.2.4]
When t-Reordering expires, the receiving UM RLC entity shall:
- update VR(UR) to the SN of the first UMD PDU with SN >=VR(UX) that has not been received;
- reassemble RLC SDUs from any UMD PDUs with SN <updated VR(UR), remove RLC headers when doing so
and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;
- start t-Reordering.;
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.9.3.1-1
Downlink RLC
t-Reordering ms200

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 535
535
U - S Message
<-- UMD PDU#1 - -
2 The SS does not transmit UMD PDU#2
- - - -
<-- UMD PDU#3 - -
<-- UMD PDU#4 - -
<-- UMD PDU#5 - -
6 The SS does not transmit UMD PDU#6
- - - -
<-- UMD PDU#7 - -
<-- UMD PDU#8 - -
9 Wait for 200 ms to ensure that t-Reordering for
the UMD PDU#2 expires.
- - - -
11 Wait for 200 ms to ensure that t-Reordering for
the UMD PDU#6 expires.
- - - -

None.
7.2.2.10 UM RLC / Duplicate detection of RLC PDUs
(1)
ensure that {
when { UE receives duplicate UMD PDUs }
then { UE discards the duplicate UMD PDUs }
}
(2)
ensure that {
when { UE receives UMD PDUs whose SN is within the reordering window and duplicate UMD PDUs }
then { UE discards the duplicate UMD PDUs }
}

4.2.1.2.3 and 5.1.2.2.2.
[TS 36.322, clause 4.2.1.2.3]
When a receiving UM RLC entity receives UMD PDUs, it shall:
- detect whether or not the UMD PDUs have been received in duplication, and discard duplicated UMD PDUs;
- reorder the UMD PDUs if they are received out of sequence;
- detect the loss of UMD PDUs at lower layers and avoid excessive reordering delays;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 536
536
- reassemble RLC SDUs from the reordered UMD PDUs (not accounting for RLC PDUs for which losses have
been detected) and deliver the RLC SDUs to upper layer in ascending order of the RLC SN;

[TS 36.322, clause 5.1.2.2.2]

System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.10.3.1-1.
Table 7.2.2.10.3.1-1: RLC settings
Parameter Value
t-Reordering ms100

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 537
537
U - S Message
<-- UMD PDU#1 - -
<-- UMD PDU#1 - -
contains SDU#2 and the 1
st
part of SDU#3.
SN equals 1.
<-- UMD PDU#2 - -
6 The UE transmit RLC SDU#2. --> (RLC SDU#2) - -
contains SDU#2 and the 1
st
part of SDU#3. SN
equals 1.
<-- UMD PDU#2 - -
<-- UMD PDU#3 - -
10
A
The SS ignores scheduling requests and does
- - - -
10
B
The SS enables the indication of scheduling
requests till step 15.
- - - -
11 After 100ms the SS transmits an UMD PDU.
This PDU carries SDU#5. SN equals 4.
<-- UMD PDU#5 - -
<-- UMD PDU#6 - -
<-- UMD PDU#3 - -
14 Check: Does the UE transmit scheduling
request before transmission of UMD PDU at
step 15?
--> (SR) 2 F
15 After 75ms from step 13 the SS transmits an
UMD PDU. This PDU carries SDU#4. SN
equals 3.
<-- UMD PDU#4 - -
15
A
The SS waits for 60 ms and then allocates 1
UL grant of size enough for the UE to loop
back 3 RLC SDU in one UMD PDU
<-- (UL Grant) - -
16 SS receives SDU#4, SDU#5 and SDU#6 in a
single PDU
--> (RLC SDU#4, RLC SDU#5 and
RLC SDU#6)
1,2 P
17 Void
18 Void

None.
7.2.2.11 UM RLC / RLC re-establishment procedure
(1)
ensure that {
when { RLC re-establishment is performed upon request by RRC }
then { The UE discards all UMD PDUs where no RLC SDUs can be reassembled }
}
(2)
ensure that {
when { RLC re-establishment is performed upon request by RRC }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 538
538
then { The UE resets variable VT(US), VR(UH) and VR(UR) to its initial value }
}
4.2.1.2.3 and 5.4.
[TS 36.322, clause 4.2.1.2.3]
At the time of RLC re-establishment, the receiving UM RLC entity shall:
- if possible, reassemble RLC SDUs from the UMD PDUs that are received out of sequence and deliver them to
upper layer;
- discard any remaining UMD PDUs that could not be reassembled into RLC SDUs;
- initialize relevant state variables and stop relevant timers.
[TS 36.322, clause 5.4]
RLC re-establishment is performed upon request by RRC, and the function is applicable for AM, UM and TM RLC
entities.
When RRC indicates that an RLC entity should be re-established, the RLC entity shall:

- if it is a receiving UM RLC entity:
- when possible, reassemble RLC SDUs from UMD PDUs with SN <VR(UH), remove RLC headers when
doing so and deliver all reassembled RLC SDUs to upper layer in ascending order of the RLC SN, if not
delivered before;
- discard all remaining UMD PDUs;

- reset all state variables to their initial values.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- UE is in Loopback Activated state (state 4) according to TS 36.508 clause 4.5 [18] with the exceptions listed in
table 7.2.2.11.3.1-1 applicable for the configured UM DRB.
Downlink RLC
t-Reordering ms200

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 539
539
U - S Message
1 The SS transmits UMD PDU#1. Header of
UMD PDU#1 contains SN=0. This PDU carries
RLC SDU#1.
<-- UMD PDU#1 - -
the 1
st
segment of SDU#2.
<-- UMD PDU#2 - -
4 SS performs a RRC Connection
Reconfiguration procedure including the
mobilityControlInfo IE in
RRCConnectionReconfiguration triggering
RLC re-establishment.
- - - -
the last segment of RLC SDU#2. The UE
starts t-Reordering.
<-- UMD PDU#3 - -
7 300ms (1.5 * t-Reordering) after step 5 the SS
transmits UMD PDU#4. Header of UMD
PDU#4 contains SN=3. This PDU carries RLC
SDU#3.
<-- UMD PDU#4 - -
8 The UE transmit RLC SDU#3. Header of UMD
PDU carrying RLC SDU#3 contains SN=0.
--> (RLC SDU#3) - -
RLC SDU#4.
<-- UMD PDU#5 - -
10 The UE transmits RLC SDU#4. Header of
UMD PDU carrying RLC SDU#4 contains
SN=1.
--> (RLC SDU#4) - -
11 SS performs a RRC Connection
Reconfiguration procedure including the
MobilityControlInfo IE in
RRCConnectionReconfiguration triggering
RLC re-establishment.
- - - -
RLC SDU#5.
<-- UMD PDU#6 - -
13 Check 1: Does the UE transmit RLC SDU#5?
Check 2: Does header of UMD PDU carrying
RLC SDU#5 contain SN=0?
--> (RLC SDU#5) 2 P

Table 7.2.2.11.3.3-1: RRCConnectionReconfiguration (step 4 and step 11, Table 7.2.2.11.3.2-1)
Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 7.2.2.11.3.3-2: MobilityControlInfo (step 4 and step 11, Table 7.2.2.11.3.2-1)
MobilityControlInfo ::=SEQUENCE {
Cell 1

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 540
540
7.2.3 Acknowledged mode
7.2.3.1 AM RLC / Concatenation and reassembly
(1)
ensure that {
when { The UE has multiple RLC SDUs in the transmission buffer that fits into the available AMD
PDU size }
then { The UE concatenates the RLC SDUs in the transmission buffer into an AMD PDU and transmits
it}
}
(2)
ensure that {
when { The UE receives an AMD PDUs containing concatenated RLC }
then { The UE reassembles the RLC SDUs in accordance with the Framing Info and Length Indicators
indicated in AMD PDUs }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.322, clauses 4.2.1.3.2 ,
4.2.1.3.3, 6.2.1.4 and 6.2.2.6.
[TS 36.322, clause 4.2.1.3.2]
When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs, it shall:
- segment and/or concatenate the RLC SDUs so that the AMD PDUs fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity notified by lower layer.

[TS 36.322, clause 4.2.1.3.3]
When the receiving side of an AM RLC entity receives RLC data PDUs, it shall:
....
- reassemble RLC SDUs from the reordered RLC data PDUs and deliver the RLC SDUs to upper layer in
sequence.

[TS 36.322, clause 6.2.1.4]
AMD PDU consists of a Data field and an AMD PDU header.
AMD PDU header consists of a fixed part (fields that are present for every AMD PDU) and an extension part (fields
that are present for an AMD PDU when necessary). The fixed part of the AMD PDU header itself is byte aligned and
consists of a D/C, a RF, a P, a FI, an E and a SN. The extension part of the AMD PDU header itself is byte aligned and
consists of E(s) and LI(s).
An AMD PDU header consists of an extension part only when more than one Data field elements are present in the
AMD PDU, in which case an E and a LI are present for every Data field element except the last. Furthermore, when an
AMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 541
541
D/C RF P FI E SN
SN
Data
...
Oct 3
Oct N
Oct 1
Oct 2

Figure 6.2.1.4-1: AMD PDU (No LI)

LI
2
E LI
2
(if K>=3)
E LI
1
LI
1
D/C RF P FI E SN
SN
Data
Oct N
Oct 1
Oct 2
Oct 3
Oct 4
Oct 5
...
LI
K-1
E LI
K-1
E LI
K-2
LI
K-2
...
Padding
E LI
K
LI
K
Oct [2.5+1.5*K]
Oct [2.5+1.5*K-1]
Oct [2.5+1.5*K-2]
Oct [2.5+1.5*K-3]
Oct [2.5+1.5*K-4]
Oct [2.5+1.5*K+1]
Present if
K >= 3

Figure 6.2.1.4-2: AMD PDU (Odd number of LIs, i.e. K = 1, 3, 5, ...)

LI
2
E LI
2
E LI
1
LI
1
D/C RF P FI E SN
SN
Data
Oct N
Oct 1
Oct 2
Oct 3
Oct 4
Oct 5
...
LI
K
E LI
K
E LI
K-1
LI
K-1
Oct [2+1.5*K]
...
Oct [2+1.5*K-1]
Oct [2+1.5*K-2]
Oct [2+1.5*K+1]

Figure 6.2.1.4-3: AMD PDU (Even number of LIs, i.e. K = 2, 4, 6, ...)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 542
542
[TS 36.322, clause 6.2.2.6]
Value Description

System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.3.1.3.1-1.
Parameter Value
t-StatusProhibit 500 ms

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 543
543
U - S Message
1 During the whole test sequence, the SS should
not allocate UL grants unless when explicitly
stated so in the procedure.
- - - -
2 The SS transmits an AMD PDU including two
RLC SDUs of size 40 bytes each with poll bit
set to 1.
<-- AMD PDU(AMD PDU
header(D/C=1, RF=0, P=1,
FI=00,E=1, SN=0,E
1
=0,
LI
1
=40 bytes), 2 RLC SDUs of 40
bytes)
- -
3 The SS waits for 60 ms and the allocates an
UL grant (UL grant allocation type 3) of size
776 bits (Note 1).
<-- (UL grant, 776 bits) - -
4 Check: Does the UE transmit a STATUS PDU
with positive acknowledgement?
--> STATUS PDU (ACK SN=1) 2 P
5 Check: Does the UE transmit two RLC SDUs
within an AMD PDU with FI field set to 00,
first E field in the fixed part set to 1, first E
field in the extension part set to 0, first LI field
set to 40 bytes?
--> AMD PDU(AMD PDU
header(P=1, FI=00, E=1,SN=0,
E
1
=0, LI
1
=40) ), two RLC SDUs
of size 40 bytes)
1, 2 P
6 The SS transmits a STATUS PDU. <-- STATUS PDU (ACK SN=1) - -
7 After 500ms the SS transmits an AMD PDU
including three RLC SDU of size 40 bytes with
P field set to "1".
<-- AMD PDU(AMD PDU
header(D/C=1, RF=0, P=1,
FI=00,E=1, SN=1, E
1
=1,
LI
1
=40 bytes, E
2
=0, LI
2
=40
bytes), three RLC SDUs of size 40
bytes)
- -
8 The SS waits for 60 ms and then allocates an
UL grant (UL grant allocation type 3) of size
1096 bits. (Note 2).
<-- (UL grant, 1096 bits) - -
with positive acknowledgement?
--> STATUS PDU (ACK SN=2) 2 P
10 Check: Does the UE transmit three RLC SDUs
within an AMD PDU with FI field set to 00,
first E field in the fixed part set to 1, first E
field in the extension part set to 1, first LI field
set to 40 bytes, second E field in the extension
part set to 0, second LI field set to 40 bytes
and P field set to 1?
--> AMD PDU(AMD PDU
header(P=1, FI=00, SN=1,
E
1
=1, LI
1
=40, E
2
=0, LI
2
=40),
three RLC SDUs of size 40 bytes)
1, 2 P
Note 1 UL grant of 776 bits (I
TBS
=11, N
PRB
=4, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will fit two
RLC SDUs of 40 bytes within one AMD PDU. MAC PDU of 776 bits=97 bytes fits an AMD PDU payload of
80 bytes (two 40 byte RLC SDUs) +4 bytes AMD PDU header +13 bytes spare for MAC header and
possible RLC STATUS PDU and BSR report.
TBS
=8, N
PRB
=8, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will fit three
RLC SDUs of 40 bytes within one AMD PDU. MAC PDU of 1096 bits=137 bytes fits an AMD PDU payload
of 120 bytes (three 40 byte RLC SDUs) +5 bytes AMD PDU header +12 bytes spare for MAC header and
possible RLC STATUS PDU and BSR report.

None.
7.2.3.2 AM RLC / Segmentation and reassembly / No PDU segmentation
(1)
ensure that {
when { the UE has a RLC SDU with larger size than available AMD PDU size in the transmission
buffer }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 544
544
then { the UE segments the RLC SDU in accordance with the available AMD PDU size }
}
(2)
ensure that {
when { the UE receives AMD PDUs containing a segmented RLC SDU }
then { the UE reassembles the RLC SDUs in accordance with the Framing Info and Length Indicators
indicated in the AMD PDUs }
}
4.2.1.3.3 and 6,2.2.6.
[TS 36.322, clause 4.2.1.3.2]

[TS 36.322, clause 4.2.1.3.3]
....
sequence.

[TS 36.322, clause 6.2.2.6]

Value Description

System Simulator:
- Cell 1.
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 545
545
Preamble:
- - - -
2 The SS transmits a RLC SDU of size 80 bytes
segmented into two AMD PDUs. The two AMD
PDUs are transmitted in separate TTIs.
<-- (RLC SDU#1)
AMD PDU#1(FI=01,SN=0)
- -
3 60 ms after step 2 the SS allocates 2 UL
grants (UL grant allocation type 2) of size 392
bits. (Note 1).
<-- (UL grants) - -
4 Check: Does the UE return a RLC SDU with
equal content as sent in downlink in step 2
segmented into two AMD PDUs and received
in different TTIs?
(Note2: Details for AMD PDU#2)
--> (RLC SDU#1)
AMD PDU#1
AMD PDU#2
1,2 P
6 The SS sends a RLC SDU of size 120 bytes
octets segmented into three AMD PDUs.
<-- (RLC SDU#2)
- -
7 60 ms after step 6 the SS allocates 3 UL
grants (UL grant allocation type 2) of size 392
bits. (Note 1).
<-- (UL grants) - -
8 Check: Does the UE return a RLC SDU with
equal content as sent in downlink in step 6
segmented into three AMD PDUs where each
AMD PDU is received in different TTI?
(Note2: Details for AMD PDU#3)
--> (RLC SDU#2)
AMD PDU#1
AMD PDU#2
AMD PDU#3
1,2 P
TBS
=8, N
PRB
=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen to force the UE to
segment the returned UL RLC SDU into multiple AMD PDUs. An UL grant of 392 bits=49 bytes allows the
UE to transmit one AMD PDU of maximum 46 bytes (49 bytes 2 byte AMD PDU header - minimum 1 byte
MAC header). UE at step 4 and step 8 during transmission of AMD PDU#1 will transmit BSR MCE which
will take 2 bytes and hence AMD PDU size will be 44 bytes.
Note2: Polling bit will be set for this PDU by the UE and SS transmits a STATUS PDU.

None.
7.2.3.3 AM RLC / Segmentation and reassembly / Framing info field
(1)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment containing a FI field set to 00 }
then { UE correctly decodes the received AMD PDU or AMD PDU segment }
}
(2)
ensure that {
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 546
546
(3)
ensure that {
then { UE correctly decodes the received AMD PDU or AMD PDU segment}
}
(4)
ensure that {
}

[TS 36.322, clause 6.2.2.6]
Length: 2 bits.
Value Description

System Simulator:
- Cell 1.
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 547
547
U - S Message
1 The SS transmits AMD PDU#1 containing a
<-- AMD PDU#1 - -
2A The SS transmits a STATUS PDU. <-- STATUS PDU (ACK SN=1) - -
3 The SS transmits AMD PDU#2 containing the
<-- AMD PDU#2 - -
<-- AMD PDU#3 - -
<-- AMD PDU#4 - -
4
P
7 The t-PollRetransmit timer for RLC PDU#5
expires and SS assumes that the transmission
of AMD PDU#5 containing a complete RLC
SDU#3 and a complete RLC SDU#4 is failed
and consider RLC PDU#5 for re-transmission
- - - -
8 The SS transmits AMD PDU segment
containing a complete RLC SDU#3 (FI field =
00).
<-- AMD PDU segment - -
containing the first segment of RLC SDU#4 (FI
field =01).
containing the second segment of RLC SDU#4
(FI field =11).
containing the last segment of RLC SDU#4 (FI
field =10).
4
P

None.
7.2.3.4 AM RLC / Segmentation and reassembly / Different numbers of length
indicators
(1)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment with no LI field }
}
(2)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment with one LI field }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 548
548
(3)
ensure that {
when { UE receives an AMD PDU or an AMD PDU segment with two LI fields }
}
[TS 36.322, clause 6.2.2.5]
Length: 11 bits.
The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU
delivered/received by an UM or an AM RLC entity. The first LI present in the RLC DATA PDU header corresponds to
the first Data field element present in the Data field of the RLC DATA PDU, the second LI present in the RLC DATA
PDU header corresponds to the second Data field element present in the Data field of the RLC DATA PDU, and so on.
The value 0 is reserved.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.3.4.3.1-1.
Parameter Value
t-Reordering 150 ms

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 549
549
U - S Message
- During the whole test sequence, the SS should
- - - -
complete RLC SDU#1 without LI field.
<-- AMD PDU#1 - -
2 The SS transmits an uplink grant allowing the
UE to transmit 1 RLC SDU.
<-- (UL grant) - -
3 Check: Does the UE transmit an AMD PDU
containing RLC SDU#1?
--> AMD PDU (RLC SDU#1) 1 P
complete RLC SDU#2 and a complete RLC
SDU#3 with one LI field.
<-- AMD PDU#2 - -
5 The SS waits for 60 ms then assigns an UL
grant sufficient for the UE to loopback RLC
SDU#2 and RLC SDU#3.
<-- (UL grant) - -
containing RLC SDU#2 and RLC SDU#3 in its
data field?
--> AMD PDU (RLC SDU#2, RLC
SDU#3)
2 P
complete RLC SDU#4, a complete RLC
SDU#5 and a complete RLC SDU#6 with two
LI fields.
<-- AMD PDU#3 - -
9 The SS waits for 60 ms then assigns an UL
grant sufficient for the UE to loopback RLC
SDU#4, RLC SDU#5 and RLC SDU#6.
<-- (UL grant) - -
containing RLC SDU#4, RLC SDU#5 and RLC
SDU#6 in its data field?
SDU#5, RLC SDU#6)
3 P
12 Void - - - -
13 The t-PollRetransmit timer for AMD PDU#4
expires and SS assumes that the transmission
of AMD PDU#4 containing a complete RLC
SDU#7, a complete RLC SDU#8, a complete
RLC SDU#9, a complete RLC SDU#10, a
SDU#12 is failed and consider AMD PDU#4
for re-transmission.
- - - -
containing a complete RLC SDU#7 without LI
field.
15 The SS waits for 60 ms and then assigns an
uplink grant (UL grant allocation type 3)
allowing the UE to transmit 1 RLC SDU.
<-- (UL grant) - -
containing RLC SDU#7?
--> AMD PDU (RLC SDU#7) 1 P
16
A
The SS transmits a STATUS PDU. <-- STATUS PDU (ACK SN=4) - -
containing a complete RLC SDU#8 and a
complete RLC SDU#9 with one LI field.
UL grant (UL grant allocation type 3) sufficient
for the UE to loopback RLC SDU#8 and RLC
SDU#9.
<-- (UL grant) - -
containing RLC SDU#8 and RLC SDU#9 in its
data field?
SDU#9)
2 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 550
550
containing a complete RLC SDU#10, a
SDU#12 with two LI fields.
UL grant (UL grant allocation type 3) sufficient
for the UE to loopback RLC SDU#10, RLC
SDU#11 and RLC SDU#12.
<-- (UL grant) - -
containing RLC SDU#10, RLC SDU#11 and
RLC SDU#12 in its data field?
SDU#11, RLC SDU#12)
3 P
25 Void - - - -

None.
7.2.3.5 AM RLC / Reassembly / LI value >PDU size
(1)
ensure that {
when { UE receives PDU with "Length Indicators" that point beyond the end of the PDU }
then { UE discards PDU }
}

and 6.2.2.5.
[TS 36.322, clause 5.5.1]
[TS 36.322, clause 6.2.2.5]
Length: 11 bits.
The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU. The
first LI present in the RLC data PDU header corresponds to the first Data field element present in the Data field of the
RLC data PDU, the second LI present in the RLC data PDU header corresponds to the second Data field element
present in the Data of the RLC data PDU, and so on. The value 0 is reserved.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with the loopback size set to 98 bytes.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 551
551
- - - -
1 The SS transmits an AMD PDU containing the
first half (50 bytes) of SDU#1 in its data field to
the UE.
<-- AMD PDU#1 (SN =0) - -
second half (50 bytes) of SDU#1 and the first
half (50 bytes) of SDU#2 in its data field to the
UE. LI associated with PDU#2 has a value >
PDU size, i.e. >100.
<-- AMD PDU#2 (SN=1) - -
UE.
<-- AMD PDU#3 (SN=2) - -
second half (50 bytes) of SDU#3 in its data
field to the UE.
<-- AMD PDU#4 (SN=3) - -
4a 100 ms after step 4 t he SS assigns an UL
grant (UL grant allocation type 3) of size 56
bits (Note 1).
<-- (UL grant, 56 bits) - -
with NACK_SN field set to 1?
--> STATUS PDU 1 P
UE. The LI is correct.
<-- AMD PDU#2 (SN=1) - -
6a The SS waits for 60 ms to ensure UE RLC has
all the required SDU available in UL for
loopback.

6b The SS transmits an UL grant (UL grant
allocation type 3) of size 2536 bits (Note 2).
<-- (UL grant, 2536 bits) - -
7 Check: Does the UE transmit RLC SDU#1,
SDU#2, and SDU#3?
(Note 3: Details for RLC PDU carrying RLC
SDU#3)
--> AMD PDU(RLC SDU#1, RLC
SDU#2, RLC SDU#3)
1 P
TBS
=1, N
PRB
=2, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will be enabled
to send the status PDU.
TBS
=13, N
PRB
=10, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will fit all 3
SDU in one AMD PDU.
Note 3: In step 7, poll is set so SS will send STATUS PDU to UE in step 8.

None.
7.2.3.6 AM RLC / Correct use of sequence numbering
(1)
ensure that {
then { UE sets the Sequence Number field equal to 0 }
}
(2)
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 552
552
ensure that {
}
(3)
ensure that {
when { UE transmits more than 1024 PDUs }
}
(4)
ensure that {
when { more than 1024 PDUs are sent to UE }

PDU }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clauses
5.1.3.1.1, 6.2.2.3 and 7.1.
[TS 36.322, clause 5.1.3.1.1]
The transmitting side of an AM RLC entity shall prioritize transmission of RLC control PDUs over RLC data PDUs.
The transmitting side of an AM RLC entity shall prioritize retransmission of RLC data PDUs over transmission of new
AMD PDUs.
The transmitting side of an AM RLC entity shall maintain a transmitting window according to state variables VT(A)
and VT(MS) as follows:
- a SN falls within the transmitting window if VT(A) <=SN <VT(MS);
- a SN falls outside of the transmitting window otherwise.
The transmitting side of an AM RLC entity shall not deliver to lower layer any RLC data PDU whose SN falls outside
of the transmitting window.
When delivering a new AMD PDU to lower layer, the transmitting side of an AM RLC entity shall:
- set the SN of the AMD PDU to VT(S), and then increment VT(S) by one.
The transmitting side of an AM RLC entity can receive a positive acknowledgement (confirmation of successful
reception by its peer AM RLC entity) for a RLC data PDU by the following:
- STATUS PDU from its peer AM RLC entity.
When receiving a positive acknowledgement for an AMD PDU with SN =VT(A), the transmitting side of an AM RLC
entity shall:
- set VT(A) equal to the SN of the AMD PDU with the smallest SN, whose SN falls within the range VT(A) <=
SN <=VT(S) and for which a positive acknowledgment has not been received yet.
- if positive acknowledgements have been received for all AMD PDUs associated with a transmitted RLC SDU :-
send an indication to the upper layers of successful delivery of the RLC SDU.
[TS 36.322, clause 6.2.2.3]
Length: 10bits for AMD PDU, AMD PDU segments and STATUS PDUs. ...
The SN field indicates the sequence number of the corresponding ... AMD PDU. For an AMD PDU segment, the SN
field indicates the sequence number of the original AMD PDU from which the AMD PDU segment was constructed
from. The sequence number is incremented by one for every ... AMD PDU.
[TS 36.322, clause 7.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 553
553
...
All state variables related to AM data transfer can take values from 0 to 1023. All arithmetic operations contained in the
present document on state variables related to AM data transfer are affected by the AM modulus (i.e. final value =
[value from arithmetic operation] modulo 1024).
AMD PDUs ... are numbered integer sequence numbers (SN) cycling through the field: 0 to 1023 for AMD PDU ...
...
c) VT(S) Send state variable
This state variable holds the value of the SN to be assigned for the next newly generated AMD PDU. It is initially set to
0, and is updated whenever the AM RLC entity delivers an AMD PDU with SN =VT(S).
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the expectations listed in table 7.2.3.6.3.1-1.
Table 7.2.3.6.3.1-1: RLC Settings
Parameter Value
PollPDU pInfinity
PollByte kBinfinity

- EXCEPTION: Step 2 is executed 1024 times. - - - -
- EXCEPTION: In parallel to step 2, the
behaviour described in table 7.2.3.6.3.2-2 is
running.
- - - -
1 The SS transmits 1 UL grant (UL grant
allocation type 2) in each radio frame to enable
the UE to return each received AMD PDU in
one looped back AMD PDU.
<-- (UL grants) - -
2 The SS transmits an AMD PDU to the UE.
SN equals 0 and is incremented for each PDU
transmitted.

<-- AMD PDU - -
3 The SS transmits an AMD PDU to the UE in
the next TTI. SN equals 0.
<-- AMD PDU - -
4 Void - - - -
with SN=0?
--> AMD PDU 3,4 P
6 The SS transmits a STATUS PDU with
ACK_SN =1.
<-- STATUS PDU - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 554
554
U - S Message
with SN =0?
--> AMD PDU 1 P
- EXCEPTION: Step 2 is executed 1023 times. - - - -
previous one?
--> AMD PDU 2 P
EXCEPTION: Step 3a1 describes behaviour
that depends on the contents of the AMD PDU
transmitted at Step 2.
- - - -
3a1 IF the UE has set the poll bit in the AMD PDU
transmitted at Step 2 THEN the SS transmits a
Status Report.
<-- STATUS PDU - -

None.
7.2.3.7 AM RLC / Control of transmit window
(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and pending uplink data for
transmission}
ensure that {
when { AMD PDUs in transmission buffer fall outside VT(A) <= SN < VT(MS) }
then { UE does not transmit these AMD PDUs }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with DRB established and pending uplink data for
transmission }
ensure that {
when { receiving a STATUS PDU where ACK_SN acknowledges at least one AMD PDU not yet
acknowledged }
then { UE transmits AMD PDUs within updated window range}
}
5.1.3.1.1, 7.1 and 7.2.
[TS 36.322, clause 5.1.3.1.1]
...
The transmitting side of an AM RLC entity shall maintain a transmitting window according to state variables VT(A)
and VT(MS) as follows:
- a SN falls within the transmitting window if VT(A) <=SN <VT(MS);
- a SN falls outside of the transmitting window otherwise.
The transmitting side of an AM RLC entity shall not deliver to lower layer any RLC data PDU whose SN falls outside
of the transmitting window.
When delivering a new AMD PDU to lower layer, the transmitting side of an AM RLC entity shall:
- set the SN of the AMD PDU to VT(S), and then increment VT(S) by one.
The transmitting side of an AM RLC entity can receive a positive acknowledgement (confirmation of successful
reception by its peer AM RLC entity) for a RLC data PDU by the following:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 555
555
When receiving a positive acknowledgement for an AMD PDU with SN =VT(A), the transmitting side of an AM RLC
entity shall:
- set VT(A) equal to the SN of the AMD PDU with the smallest SN, whose SN falls within the range VT(A) <=
SN <=VT(S) and for which a positive acknowledgment has not been received yet.
- if positive acknowledgements have been received for all AMD PDUs associated with a transmitted RLC SDU :
- send an indication to the upper layers of successful delivery of the RLC SDU.
[TS 36.322, clause 7.2]
a) AM_Window_Size
This constant is used by both the transmitting side and the receiving side of each AM RLC entity to calculate VT(MS)
from VT(A), and VR(MR) from VR(R). AM_Window_Size =512.
...
[TS 36.322, clause 7.1]

a) VT(A) Acknowledgement state variable
This state variable holds the value of the SN of the next AMD PDU for which a positive acknowledgment is to be
received in-sequence, and it serves as the lower edge of the transmitting window). It is initially set to 0, and is
updated whenever the AM RLC entity receives a positive acknowledgment for an AMD PDU with SN =VT(A).
b) VT(MS) Maximum send state variable
This state variable equals VT(A) +AM_Window_Size, and it serves as the higher edge of the transmitting window.
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the loopback size set to 100 bytes, and with
the expectations listed in table 7.2.3.7.3.1-1.
Parameter Value
PollPDU pInfinity
PollByte kBinfinity

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 556
556
U - S Message
- The SS does not allocate any uplink grant. - - - -
- EXCEPTION: Step 1 is repeated W+1 times,
where W =AM_Window_Size. The
transmission is performed in subsequent TTIs.
- - - -
1 The SS transmits an AMD PDU containing a
SDU to the UE.
<-- AMD PDU - -
1A In the following steps the SS transmits 1 UL
grant (UL grant allocation type 2) in each radio
frame to enable the UE to return each received
AMD PDU in one looped back AMD PDU.
<-- (UL grants) - -
- EXCEPTION: Step 1B is repeated W-1 times. - - - -
1B The UE transmits an AMD PDU with the same
data as received in the corresponding DL AMD
PDU.
--> AMD PDU - -
1C Check: Does the UE transmit an AMD PDU
with the Poll bit set and with the contents of the
SDU?
--> AMD PDU(SN=W-1), Poll 1 P
within t-PollRetransmit/2?
--> AMD PDU 1 F
3 The SS transmits a STATUS PDU to
acknowledge the W uplink AMD PDUs with
SN=0 to SN=W-1. ACK_SN =W.
<-- STATUS PDU - -
3A Check: Does the UE transmit an AMD PDU
with the Poll bit set and with the contents of the
SDU?
--> AMD PDU(SN=W), Poll 2 P
3B The SS transmits a STATUS PDU with
ACK_SN =W+1.
<-- STATUS PDU - -
Note: SDUs are numbered 1,2, , W+1

None.
7.2.3.8 AM RLC / Control of receive window
(1)
ensure that {
when { the UE receives AMD PDUs with SN outside the upper boundary of the receive window }
then { the UE discards these AMD PDUs }
}
(2)
ensure that {
when { the receive window has been moved }
then { UE continues accepting AMD PDUs within updated window range }
}
5.1.3.2.1 and 7.2.
[TS 36.322, clause 5.1.3.2.1]
The receiving side of an AM RLC entity shall maintain a receiving window according to state variables VR(R) and
VR(MR) as follows:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 557
557
- a SN falls within the receiving window if VR(R) <=SN <VR(MR);
- a SN falls outside of the receiving window otherwise.
When receiving a RLC data PDU from lower layer, the receiving side of an AM RLC entity shall:
- either discard the received RLC data PDU or place it in the reception buffer (see sub clause 5.1.3.2.2);
- if the received RLC data PDU was placed in the reception buffer:
needed (see sub clause 5.1.3.2.3).
When t-Reordering expires, the receiving side of an AM RLC entity shall:
- update state variables and start t-Reordering as needed (see sub clause 5.1.3.2.4).
[TS 36.322, clause 7.2]
a) AM_Window_Size
This constant is used by both the transmitting side and the receiving side of each AM RLC entity to calculate
VT(MS) from VT(A), and VR(MR) from VR(R). AM_Window_Size =512.
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loopback size of 0 byte.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 558
558
- EXCEPTION: Step 1 shall be repeated W
times, where W is AM_Window_Size. Polling
bit enabled for the Wth RLC PDU transmitted.
The SS shall set the Sequence Number field
for the first AMD PDU to 0 and increment it by
1 for every execution of Step 1.
- - - -
1 The SS transmits an AMD PDU to the UE <-- AMD PDU
acknowledging W PDUs? (ACK_SN =W)
--> STATUS PDU 1 P
3 The SS transmits the (W+1)th AMD PDU to
the UE with the Sequence Number field set to
((2W mod 1024) =0) and the Polling bit set
<-- AMD PDU - -
4 Check: does the UE transmit a STATUS PDU
acknowledging W PDUs? (ACK_SN =W)
(Note 1)
--> STATUS PDU 1 P
5 The SS transmits the (W+2)th AMD PDU to
the UE with the Sequence Number field set to
W and the Polling bit set.
<-- AMD PDU - -
acknowledging W +1 PDUs? (ACK_SN field =
W+1) (Note 2)

--> STATUS PDU 2 P
Note 1: This shows that the UE has discarded the (W+1)th PDU.
Note 2: This shows that the UE did not discard the (W+2)th PDU and has updated the Receive Window correctly

None.
7.2.3.9 AM RLC / Polling for status
(1)
with { UE in E-UTRA RRC_CONNECTED state and using AM RLC }
ensure that {
when { last data in the buffer was transmitted }
then { UE transmits a Poll }
}
(2)
ensure that {
when { the t-PollRetransmit timer expires }
}
(3)
ensure that {
when { PDU_WITHOUT_POLL=pollPDU }
}
(4)
ensure that {
when { BYTE_WITHOUT_POLL=pollByte }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 559
559
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clauses 5.2.2.
[TS 36.322, clause 5.2.2]

Upon assembly of a new AMD PDU, the transmitting side of an AM RLC entity shall:
- increment PDU_WITHOUT_POLL by one;
- increment BYTE_WITHOUT_POLL by every new byte of Data field element that it maps to the Data field of
the RLC data PDU;
- if PDU_WITHOUT_POLL >=pollPDU; or
- if BYTE_WITHOUT_POLL >=pollByte;
- include a poll in the RLC data PDU as described below.
Upon assembly of an AMD PDU or AMD PDU segment, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC data
PDU awaiting for acknowledgements) after the transmission of the RLC data PDU; or
- if no further RLC data PDU can be transmitted after the transmission of the RLC data PDU (e.g. due to window
stalling);
To include a poll in a RLC data PDU, the transmitting side of an AM RLC entity shall:
- set the P field of the RLC data PDU to "1";
- set PDU_WITHOUT_POLL to 0;
- set BYTE_WITHOUT_POLL to 0;
After delivering a RLC data PDU including a poll to lower layer and after incrementing of VT(S) if necessary, the
transmitting side of an AM RLC entity shall:
- set POLL_SN to VT(S) 1;
- if t-PollRetransmit is not running:
- start t-PollRetransmit;
- else:
- restart t-PollRetransmit;
[TS 36.322, clause 5.2.2.3]
Upon expiry of t-PollRetransmit, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer are empty (excluding transmitted RLC data PDU
awaiting for acknowledgements); or
- if no new RLC data PDU can be transmitted (e.g. due to window stalling):
- consider the AMD PDU with SN =VT(S) 1 for retransmission;
- consider any AMD PDU which has not been positively acknowledged for retransmission;
- include a poll in a RLC data PDU as described in section 5.2.2.1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 560
560
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.3.9.3.1-1.
Parameter Value
pollPDU p256
pollByte kB25

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 561
561
U - S Message
- During the whole test sequence, the SS should
- - - -
1 The SS transmits 4 AMD PDUs, each
containing an RLC SDU of size 5 120 bits.
<-- AMD PDU (SN=0)
AMD PDU (SN=1)
AMD PDU (SN=2)
AMD PDU (SN=3)
- -
- EXCEPTION: In parallel to the events
described in step 1A, the step specified in
Table 7.2.3.9.3.2-2 should take place.
- - - -
1A The SS waits for 60 ms, then starts assigning
UL grants (UL grant allocation type 2) of size 5
160 bits. (Note 1)
- - - -
2 Check 1: Does the UE transmit an AMD PDU
with a SN in range 0 to 3 and P=1?
Record time T
B
.
Check 2: Is (T
B
T
A
) =t-PollRetransmit?
--> AMD PDU 2 P
3 Upon receiving the Poll, the SS transmits an
RLC Status Report.
<-- STATUS PDU - -
4 Check: Does the UE retransmit an AMD PDU
within 1 sec?
--> AMD PDU 2 F
5 SS performs an RRC Connection
Reconfiguration procedure changing pollPDU
to p4.
- - - -
containing an RLC SDU of 5 120 bits.
<-- AMD PDU (SN=4)
AMD PDU (SN=5)
...
AMD PDU (SN=11)
- -
described in step 6A, the step specified in
- - - -
6A The SS waits for 60 ms, then starts assigning
160 bits. (Note 1)
- - - -
7 The SS transmits a Status Report with
ACK_SN=12, NACK_SN=4, NACK_SN=5,
NACK_SN=6, NACK_SN=8 and NACK_SN=9.
<-- STATUS PDU - -
8 Check: Does the UE transmit AMD PDUs with
the following SN and P values?
AMD PDU, SN=4, P=0
AMD PDU, SN=5, P=0
AMD PDU, SN=6, P=0
AMD PDU, SN=8, P=0
AMD PDU, SN=9, P=1
--> AMD PDU (SN=4, P=0)
AMD PDU (SN=5, P=0)
AMD PDU (SN=6, P=0)
AMD PDU (SN=8, P=0)
AMD PDU (SN=9, P=1)
3 P
8A The SS transmits a Status Report with
ACK_SN=12 and no NACK_SN.
<-- STATUS PDU - -
9 SS performs an RRC Connection
Reconfiguration procedure changing pollPDU
to p256.
- - - -
containing an RLC SDU of size 5 120 bits.
<-- AMD PDU (SN=12)
AMD PDU (SN=13)
...
AMD PDU (SN=93)
- -
described in step 10A, the steps specified in
- - - -
10
A
The SS waits for 60 ms, then starts assigning
160 bits. (Note 1)
- - - -
TBS
=13, N
PRB
=20, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to
loop back one SDU of size 5120 bits and one short BSR (8 bits) into each MAC PDU sent in the uplink
(5160 bits - 16 bit AMD PDU header - 8 bit MAC BSR subheader - 8 bit MAC PDU subheader). The UE will
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 562
562
include an SDU of size 5120 bits and one short BSR in the looped back MAC PDU.

U - S Message
1 Check: Does the UE transmit 4 AMD PDUs,
with only the last one having the poll bit set?
Record time T
A
when the PDU with the poll bit
set is received at the SS.
--> AMD PDUs 1 P

U - S Message
with the poll bit set only in the 4
th
and the 8
th

PDUs?
--> AMD PDUs 3 P

U - S Message
with the poll bit set only in the last (40
th
) one?
--> AMD PDUs 1,4 P
2 The SS transmits an RLC Status Report. <-- STATUS PDU - -
th
) one?
--> AMD PDUs 1,4 P
nd
) one?
--> AMD PDUs 1,4 P

None.
7.2.3.10 AM RLC / Receiver status triggers
(1)
ensure that {
when { Reception failure of an RLC data PDU is detected }
then { UE initiates Status Reporting when t-Reordering expires }
}
(2)
ensure that {
when { Status Reporting is triggered and t-StatusProhibit is running}
then { UE wait until t-StatusProhibit has expired to send Status Report }
}
(3)
ensure that {
when { Polling from peer AM RLC entity is detected and the sequence number of the PDU that carries
the Poll is less than VR(MS) }
then { UE initiates Status Reporting }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 563
563
(4)
ensure that {
when { Polling from peer AM RLC entity is detected and the sequence number of the PDU that carries
the Poll is greater than or equal to VR(MS) }
then { UE waits until VR(MS) becomes greater than the sequence number of the PDU with the Poll
before initiating Status Reporting }
}
(5)
ensure that {
when { the UE needs to send a Status Report and the UL grant is not large enough to accommodate
the whole report }
then { UE includes as many NACK SNs in the Status Report as allowed by the UL grant }
}
[TS 36.322, clause 5.2.3]
An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative
acknowledgements of RLC PDUs (or portions of them).
RRC configures whether or not the status prohibit function is to be used an AM RLC entity.
Triggers to initiate STATUS reporting include:
- Polling from its peer AM RLC entity:
- When a RLC data PDU with SN =x and the P field set to "1" is received from lower layer, the receiving side
of an AM RLC entity shall:
- if the PDU is to be discarded as specified in subclause 5.1.3.2.2; or
- if x <VR(MS) or x >=VR(MR):
- trigger a STATUS report;
- else:
- delay triggering the STATUS report until x <VR(MS) or x >=VR(MR).
NOTE: This ensures that the RLC Status report is transmitted after HARQ reordering.
- Detection of reception failure of an RLC data PDU:
- The receiving side of an AM RLC entity shall trigger a STATUS report when t-Reordering expires.
NOTE: The expiry of T_reordering triggers both VR(MS) to be updated and a STATUS report to be triggered,
but the STATUS report shall be triggered after VR(MS) is updated.
When STATUS reporting has been triggered, the receiving side of an AM RLC entity shall:
- if t-StatusProhibit is not running:
- at the first transmission opportunity indicated by lower layer, construct a STATUS PDU and deliver it to
lower layer;
- else:
- at the first transmission opportunity indicated by lower layer after t-StatusProhibit expires, construct a single
STATUS PDU even if status reporting was triggered several times while t-StatusProhibit was running and
deliver it to lower layer;
When a STATUS PDU has been delivered to lower layer, the receiving side of an AM RLC entity shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 564
564
- start t-StatusProhibit.
When constructing a STATUS PDU, the AM RLC entity shall:
- for the AMD PDUs with SN such that VR(R) <=SN <VR(MS) that has not been completely received yet, in
increasing SN order of PDUs and increasing byte segment order within PDUs, starting with SN =VR(R) up to
the point where the resulting STATUS PDU still fits to the total size of RLC PDU(s) indicated by lower layer:
- for an AMD PDU for which no byte segments have been received yet for an AMD PDU:
- include in the STATUS PDU a NACK_SN which is set to the SN of the AMD PDU;
- for a continuous sequence of byte segments of a partly received AMD PDU that have not been received yet :
- include in the STATUS PDU a set of NACK_SN, SOstart and SOend
- set the ACK_SN to the SN of the next not received RLC Data PDU which is not indicated as missing in the
resulting STATUS PDU.
System Simulator:
- Cell 1.
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.3.10.3.1-
1.
Parameter Value
t-Reordering ms150
t-StatusProhibit ms300

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 565
565
U - S Message
- The SS ignores scheduling requests and does
- - - -
1 The SS transmits 4 AMD PDUs with SN=0, 1,
2, and 4. The SS sets the P field of all the
AMD PDUs to 0.
Record time T
A
when the AMD PDU with SN=4
is sent.
<-- AMD PDU (SN=0, P=0)
AMD PDU (SN=1, P=0)
AMD PDU (SN=2, P=0)
AMD PDU (SN=4, P=0)
- -
1A The SS waits for 60 ms to ensure UE RLC has
all the required SDUs available and then
assigns 3 UL grants (UL grant allocation type
2) of size 840 bits (UL Grant Allocation type 2).
(Note 1)
<-- (UL grants, 840 bits) - -
1B The UE transmits RLC SDU#1. --> (RLC SDU#1) - -
1C The UE transmits RLC SDU#2. --> (RLC SDU#2) - -
1D The UE transmits RLC SDU#3. --> (RLC SDU#3) - -
1E The SS transmits a STATUS PDU <-- STATUS PDU - -
1F The SS starts the UL default grant
transmission
- - - -
2 Check 1: Does the UE transmit a Status
Report with NACK_SN=3 and ACK_SN=5?
Record time T
B

Check 2: (T
B
T
A
) =t-Reordering
--> STATUS PDU 1 P
3 100 ms after the Status Report is received at
Step 2, the SS transmits 4 AMD PDUs with
SN=5, 6, 8 and 9. The SS sets the P field of all
the AMD PDUs to 0.
<-- AMD PDU (SN=5, P=0)
AMD PDU (SN=6, P=0)
AMD PDU (SN=8, P=0)
AMD PDU (SN=9, P=0)
- -
3A Void - - - -
3B Check 1: Does the UE transmit a Status
Report with NACK_SN=3, ACK_SN=7?
Record time T
C

Check 2: (T
C
T
B
) =t-StatusProhibit
--> STATUS PDU 2 P
3C Void - - - -
4 The UE transmit a Status Report with
NACK_SN=3, NACK_SN=7 and ACK_SN=10
--> STATUS PDU
4A The SS ignores scheduling requests unless
otherwise specified and does not allocate any
uplink grant and is configured for Uplink Grant
Allocation Type 3.
- - - -
5 Void - - - -
6 After 300ms the SS transmits 2 AMD PDUs
with SN=3, SN=7. The SS sets the P field of all
the AMD PDUs to 0 except for that of the AMD
PDU with SN=7.
<-- AMD PDU (SN=3, P=0)
AMD PDU (SN=7, P=1)
- -
assigns 1 UL grant (UL grant allocation type 3)
of size 40 bits. (Note 2)
7 Check: Does the UE transmit a Status Report
with no NACK_SN and ACK_SN =10?
--> STATUS PDU 3 P
7A In the subframe following the one scheduled in
step 6A the SS assigns 7 UL grants (UL grant
allocation type 2) of size 840 bits. (Note 1)
<-- (UL grant, 840 bits) - -
7E The UE transmits RLC SDU#7. --> (RLC SDU#7) - -
7F The UE transmits RLC SDU#8. --> (RLC SDU#8) - -
7G The UE transmits RLC SDU#9. --> (RLC SDU#9) - -
7H The UE transmits RLC SDU#10. --> (RLC SDU#10) - -
7I The SS transmits a STATUS PDU <-- STATUS PDU - -
8 Void - - - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 566
566
9 After 300 ms the SS transmits an AMD PDU
with SN=10 and P=0, and an AMD PDU with
SN=12 and P=1.
<-- AMD PDU (SN=10, P=0)
AMD PDU (SN=12, P=1)
- -
9A Check: Does the UE transmits a scheduling
request within t-Reordering / 2 ms?
--> (SR) 4 F
10 Within t-Reordering / 2 ms after Step 9, the SS
transmits an AMD PDU with SN=11 and P=0.
Note: AMD PDUs with SN 10,11 and 12 carry
RLC SDU #11.
<-- AMD PDU (SN=11, P=0) - -
10
A
The SS waits for 60 ms to ensure UE RLC has
assigns 1 UL grant (UL grant allocation type 3)
of size 40 bits. (Note 2)
with no NACK_SN and ACK_SN=13?
--> STATUS PDU 4 P
11
A
The SS assigns 1 UL grant (UL grant
allocation type 2) of size 840 bits. (Note 1)
11
B
The UE transmit RLC SDU#11. --> (RLC SDU#11) - -
11
C
The SS transmits a STATUS PDU <-- STATUS PDU - -
12 Void - - - -
13 Void - - - -
with SN=13 and P=0, and an AMD PDU with
SN=19 and P=1.
<-- AMD PDU (SN=13, P=0)
- -
15 The SS waits for t-Reordering ms to ensure
expiry.
- - - -
16 Void - - - -
17 60 ms after step 15 the SS assigns an UL
bits. (Note 3)
<-- (UL Grant) - -
with ACK_SN=16 and 2 NACK_SNs: 14 and
15?
--> STATUS PDU 5 P
19 Void - - - -
20 Void - - - -
21 After 300 ms tThe SS transmits an AMD PDU
with SN=14 and P=1.
<-- AMD PDU (SN=14, P=1) - -
22 60 ms after step 21 the SS assigns an UL
bits. (Note 4)
<-- (UL Grant) - -
with ACK_SN=20 and 4 NACK_SNs: 15, 16,
17 and 18?
--> STATUS PDU 5 P
24 60 ms after step 22 t he SS transmits 4 AMD
PDU with SN=15, 16, 17, 18.
Note: AMD PDUs with SN 13 to 19 carry RLC
SDU #12.
<-- AMD PDU (SN=15, P=0)
- -
24
A
60 ms after step 24 the SS assigns 1 UL grant
(UL grant allocation type 2) of size 840 bits.
(Note 1)
25 The UE loopbacks the complete RLC SDU. --> (RLC SDU#12) - -
26 The SS transmits a STATUS PDU <-- STATUS PDU - -
TBS
=14, N
PRB
=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit
one PDU at a time.
TBS
=3, N
PRB
=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit a
Status Report with ACK_SN and (16-bit short BSR +8-bit MAC PDU subheader +4-bit D/C/CPT +10-bit
ACK_SN +1-bit E1 +1bit padding).
TBS
=1, N
PRB
Status Report with ACK_SN and 2 NACK_SNs (8-bit MAC PDU subheader +4-bit D/C/CPT +10-bit
ACK_SN +1-bit E1 +2 x (12-bit NACK_SN/E1/E2)).
TBS
=2, N
PRB
Status Report with ACK_SN and 4 NACK_SNs (8-bit MAC PDU subheader +4-bit D/C/CPT +10-bit
ACK_SN +1-bit E1 +4 x (12-bit NACK_SN/E1/E2)).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 567
567
None.

7.2.3.11 Void

7.2.3.12 Void

7.2.3.13 AM RLC / Reconfiguration of RLC parameters by upper layers
(1)
ensure that {
when { t-PollRetransmit value is changed during reconfiguration of RLC parameters by upper
layers }
then { UE starts using new t-PollRetransmit value }
}
(2)
ensure that {
when { t-Reordering value is changed during reconfiguration of RLC parameters by upper layers }
then { UE starts using new t-Reordering value }
}
(3)
ensure that {
when { t-StatusProhibit value is changed during reconfiguration of RLC parameters by upper layers}
then { UE starts using new t-StatusProhibit value }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clause 5.2.2,
5.2.2.1, 5.2.2.2, 5.2.2.3 and 5.2.3.
[TS 36.322, clause 5.2.2]
An AM RLC entity can poll its peer AM RLC entity in order to trigger STATUS reporting at the peer AM RLC entity.
[TS 36.322, clause 5.2.2.1]
Upon assembly of a new AMD PDU, the transmitting side of an AM RLC entity shall:
- increment PDU_WITHOUT_POLL by one;
- increment BYTE_WITHOUT_POLL by every new byte of Data field element that it maps to the Data field of
the RLC data PDU;
- if PDU_WITHOUT_POLL >=pollPDU; or
- if BYTE_WITHOUT_POLL >=pollByte;
Upon assembly of a AMD PDU or AMD PDU segment, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC data
PDU awaiting for acknowledgements) after the transmission of the RLC data PDU; or
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 568
568
- if no new RLC data PDU can be transmitted after the transmission of the RLC data PDU (e.g. due to window
stalling);
To include a poll in a RLC data PDU, the transmitting side of an AM RLC entity shall:
- set the P field of the RLC data PDU to "1";
- set PDU_WITHOUT_POLL to 0;
- set BYTE_WITHOUT_POLL to 0;
After delivering a RLC data PDU including a poll to lower layer and after incrementing of VT(S) if necessary, the
transmitting side of an AM RLC entity shall:
- set POLL_SN to VT(S) 1;
- if t-PollRetransmit is not running:
- start t-PollRetransmit;
- else:
- restart t-PollRetransmit;
[TS 36.322, clause 5.2.2.2]
Upon reception of a STATUS report from the receiving RLC AM entity the transmitting side of an AM RLC entity
shall:
- if the STATUS report comprises a positive or negative acknowledgement for the RLC data PDU with sequence
number equal to POLL_SN:
- if the t-PollRetransmit is running:
- stop and reset t-PollRetransmit.
[TS 36.322, clause 5.2.2.3]
Upon expiry of t-PollRetransmit, the transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer are empty (excluding transmitted RLC data PDU
awaiting for acknowledgements); or
- if no new RLC data PDU can be transmitted (e.g. due to window stalling):
- consider the AMD PDU with SN =VT(S) 1 for retransmission; or
- consider any AMD PDU which has not been positively acknowledged for retransmission;
- include a poll in a RLC data PDU as described in section 5.2.2.1.
[TS 36.322, clause 5.2.3]
An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative
acknowledgements of RLC PDUs (or portions of them).
RRC configures whether or not the status prohibit function is to be used for an AM RLC entity.
Triggers to initiate STATUS reporting include:
- Polling from its peer AM RLC entity:
- When a RLC data PDU with SN =x and the P field set to 1 is received from lower layer, the receiving side
of an AM RLC entity shall:
- if the PDU is to be discarded as specified in subclause 5.1.3.2.2; or
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 569
569
- if x <VR(MS) or x >=VR(MR):
- trigger a STATUS report;
- else:
- delay triggering the STATUS report until x <VR(MS) or x >=VR(MR).
NOTE: This ensures that the RLC Status report is transmitted after HARQ reordering.
- Detection of reception failure of an RLC data PDU:
- The receiving side of an AM RLC entity shall trigger a STATUS report when t-Reordering expires.
NOTE: The expiry of T_reordering triggers both VR(MS) to be updated and a STATUS report to be triggered,
but the STATUS report shall be triggered after VR(MS) is updated.
When STATUS reporting has been triggered, the receiving side of an AM RLC entity shall:
- if t-StatusProhibit is not running:
- at the first transmission opportunity indicated by lower layer, construct a STATUS PDU and deliver it to
lower layer;
- else:
- at the first transmission opportunity indicated by lower layer after t-StatusProhibit expires, construct a single
STATUS PDU even if status reporting was triggered several times while T_status_prohibit was running and
deliver it to lower layer;
When a STATUS PDU has been delivered to lower layer, the receiving side of an AM RLC entity shall:
- start t-StatusProhibit.
When constructing a STATUS PDU, the AM RLC entity shall:
- for the AMD PDUs with SN such that VR(R) <=SN <VR(MS) that has not been completely received yet, in
increasing SN order of PDUs and increasing byte segment order within PDUs, starting with SN =VR(R) up to
the point where the resulting STATUS PDU still fits to the total size of RLC PDU(s) indicated by lower layer:
- for an AMD PDU for which no byte segments have been received yet :
- include in the STATUS PDU a NACK_SN which is set to the SN of the AMD PDU;
- for a continuous sequence of byte segments of a partly received AMD PDU that have not been received yet
- include in the STATUS PDU a set of NACK_SN, SOstart and SOend
- set the ACK_SN to the SN of the next not received RLC Data PDU which is not indicated as missing in the
resulting STATUS PDU.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 570
570
Parameter Value
t-Reordering ms150
pollPDU pInfinity
pollByte kBinfinity

1 Void - - - -
The SS ignores scheduling requests and does
- - - -
2 The SS transmits 4 AMD PDUs with P=0 and
SN=0, 1, 2 and 4.
The SS record time T
A
when AMD PDU#5
(with SN=4) is sent.
<-- AMD PDU#1 (SN=0, P=0)
AMD PDU#2 (SN=1, P=0)
- -
assigns 3 UL grants of size 840 bits (UL Grant
Allocation type 2). (Note 2)
2E The SS transmits a STATUS PDU <-- STATUS PDU - -
transmission
- - - -
3 Check 1: Does the UE transmit a STATUS
PDU with NACK_SN=3 and ACK_SN=5?
Record time T
B
.
Check 2: Is (T
B
T
A
) =t-Reordering?
--> STATUS PDU - -
4 100 ms after the Status Report received at
Step 3, he SS sends 4 AMD PDUs with P=0
and SN=5, 6, 8 and 9.
<-- AMD PDU#6 (SN=5, P=0)
- -
4A Check 1: Does the UE transmit a Status
Report with NACK_SN=3, ACK_SN=7?
Record time T
C

Check 2: (T
C
T
B
) =t-StatusProhibit?
--> STATUS PDU - -
5 The UE transmits a STATUS PDU with
NACK_SN=3, NACK_SN=7 and ACK_SN=10.
--> STATUS PDU - -
- - - -
with SN=3, 7 and 9. The SS sets the P field of
all the AMD PDUs to 0 except for that of the
AMD PDU with SN=9.
<-- AMD PDU#4 (SN=3, P=0)
- -
assigns 1 UL grant of size 40 bits (UL Grant
8 The UE transmits a Status Report with no
NACK_SN and ACK_SN =10.
--> STATUS PDU - -
8A In the subframe following the one scheduled in
step 7A the SS assigns 7 UL grants of size
840 bits (UL Grant Allocation type 2). (Note 2)
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 571
571
8E The UE transmits RLC SDU#7. --> (RLC SDU#7) - -
8G The UE transmits RLC SDU#9. --> (RLC SDU#9) - -
8H The UE transmits RLC SDU#10. --> (RLC SDU#10) - -
9 The SS transmits an AMD PDU to the UE. <-- AMD PDU#11 (SN=10, P=0) - -
9A The SS starts the UL default grant
transmission
- - - -
10 The UE transmits an AMD PDU with the same
PDU. Record time T
D
.
--> AMD PDU#11 (SN=10, P=1) - -
11 Check 1: Does the UE set the poll bit as both
the transmission and retransmission buffers
become empty? Record time T
E
.
Check 2: Is (T
E
T
D
) =t-PollRetransmit?
--> AMD PDU#11 (SN=10, P=1) 1 P
11
A
12 The SS reconfigures RLC in the UE and sets:
- t-Reordering to ms200,
- t-StatusProhibit to ms400,
- t-PollRetransmit to ms500.
(Note 1)
- - - -
- - - -
13 The SS transmits 4 AMD PDUs with P=0 and
SN=11, 12, 13 and 15.
The SS record time T
F
when AMD PDU#16
(with SN=15) is sent.
<-- AMD PDU#12 (SN=11, P=0)
AMD PDU#13 (SN=12, P=0)
AMD PDU#14 (SN=13, P=0)
AMD PDU#16 (SN=15, P=0)
- -
13
A
assigns 3 UL grants of size 840 bits (UL Grant
13
B
The UE transmits RLC SDU#12. --> (RLC SDU#12) - -
13
C
13
D
13
E
transmission
- - - -
14 Check 1: Does the UE transmit a STATUS
Record time T
G
.
Check 2: Is (T
G
T
F
) =updated value of t-
Reordering?
--> STATUS PDU 2 P
15 100 ms after the Status Report received at
Step 14, t he SS sends 4 AMD PDUs with P=0
and SN=16, 17, 19 and 20.
<-- AMD PDU#17 (SN=16, P=0)
AMD PDU#18 (SN=17, P=0)
AMD PDU#20 (SN=19, P=0)
AMD PDU#21 (SN=20, P=0)
- -
15
A
Check 1: Does the UE transmit a STATUS
Record time T
H
.
Check 2: Is (T
H
T
G
StatusProhibit?
--> STATUS PDU 3 P
NACK_SN=14, NACK_SN=18 and
ACK_SN=21.
--> STATUS PDU - -
- - - -
with SN=14, 18 and 20. The SS sets the P
field of all the AMD PDUs to 0 except for that
<-- AMD PDU#15 (SN=14, P=0)
AMD PDU#19 (SN=18, P=0)
AMD PDU#21 (SN=20, P=1)
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 572
572
of the AMD PDU with SN=20.
18
A
assigns 1 UL grant of size 40 bits (UL Grant
19 The UE transmits a Status Report with no
NACK_SN and ACK_SN =21.
--> STATUS PDU - -
19
A
In the subframe following the one scheduled in
step 18A the SS assigns 7 UL grants of size
840 bits (UL Grant Allocation type 2). (Note 2)
19
B
19
C
19
D
19
E
19
G
19
H
20
A
The SS starts the UL default grant
transmission
- - - -
PDU. Record time T
I
.
--> AMD PDU#22 (SN=21, P=1) - -
22 Check 1: Does the UE set the poll bit as both
the transmission and retransmission buffers
become empty? Record time T
J
.
Check 2: Is (T
J
T
I
PollRetransmit?
--> AMD PDU#22 (SN=21, P=1) 1 P
23 The SS transmits a STATUS PDU <-- STATUS PDU - -
Note 1: The RRC Connection Reconfiguration procedure is performed.
Note 2: UL grant of 840 bits (ITBS=14, NPRB=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to
transmit one PDU at a time.
Note 3: UL grant of 40 bits (ITBS=3, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit
a Status Report with ACK_SN and (16-bit short BSR +8-bit MAC PDU subheader +4-bit D/C/CPT +10-bit
ACK_SN +1-bit E1 +1bit padding).
Note 4: Every DL AMD PDU contains 1 RLC SDU size of 100 bytes.

None.
7.2.3.14 AM RLC / In sequence delivery of upper layers PDUs
(1)
ensure that {
when { UE receives duplicate AMD PDUs }
then { UE discards the duplicate AMD PDUs }
}
(2)
ensure that {
when { UE receives an AMD PDU with a SN gap }
then { UE sends STATUS PDU to request retransmissions of PDUs in the SN gap}
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 573
573
(3)
ensure that {
when { UE receives PDUs within a SN gap }
then { RLC reassembles and reorders the AMD PDUs and deliver them to the upper layer in sequence }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322 clause 4.2.1.3.3.
[TS 36.322, clause 4.2.1.3.3]
- detect whether or not the RLC data PDUs have been received in duplication, and discard duplicated RLC data
PDUs;
- reorder the RLC data PDUs if they are received out of sequence;
- detect the loss of RLC data PDUs at lower layers and request retransmissions to its peer AM RLC entity;
sequence.
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 574
574
U - S Message
1 The SS transmits an AMD PDU to the UE. This
PDU carries SDU#1.
<-- AMD PDU#1 (SN=0)
PDU carries SDU#1.
<-- AMD PDU#1 (SN=0) - -
3 Check: Does the UE transmit RLC SDU#1?
(Note)
--> (RLC SDU#1) 1 P
PDU contains SDU#2, and the 1
st
part of
SDU#3.
<-- AMD PDU#2 (SN=1) - -
st
part of
SDU#3.
<-- AMD PDU#2 (SN=1) - -
PDU contains the 2
nd
part of SDU#3.
<-- AMD PDU#3 (SN=2) - -
PDU contains the last part of SDU#6.
<-- AMD PDU#6 (SN=5) - -
PDU contains the 2
nd
part of SDU#5, and the
1
st
part of SDU#6.
<-- AMD PDU#5 (SN=4) - -
11
A
The SS does not allocate any uplink grant. - - - -
PDU carries SDU#4 and the 1
st
part of SDU#5.
<-- AMD PDU#4 (SN=3) - -
12
A
The SS waits for 60 ms then assigns an UL
grant sufficient for the UE to loopback SDU#4,
SDU#5 and SDU#6.
<-- (UL grant) - -
SDU#5, RLC SDU#6)
3 P
15 Void - - - -
16 The SS transmits an AMD RLC PDU to the
UE. This PDU contains the last part of SDU#9.
<-- AMD PDU#9 (SN=8, P=1) - -
NACK_SN/E1/E2 fields set correctly to inform
SS of missing PDUs #7, #8, (ACK_SN =9,
NACK_SN =6, NACK_SN =7)?
--> STATUS PDU 2 P
st
part of
SDU#9.
<-- AMD PDU#8 (SN=7) - -
18
A
The SS does not allocate any uplink grant. - - - -
PDU carries SDU#7.
<-- AMD PDU#7 (SN=6) - -
19
A
The SS waits for 60 ms then assigns an UL
grant sufficient for the UE to loopback SDU#7,
SDU#8 and SDU#9.
<-- (UL grants) - -
SDU#8, RLC SDU#9)
3 P
22 Void - - - -
Note: UE may transmit RLC SDU #1 between Step 1 and Step 2.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 575
575
None.
7.2.3.15 AM RLC / Re-ordering of RLC PDU segments
(1)
ensure that {
when { UE receives RLC AM PDU segments }
then { UE reorders RLC AMD PDU segments received out of sequence }
}
(2)
ensure that {
when { t-Reordering expires }
then { Set VR(MS) to SN of the first AMD PDU with SN >= VR(X) for which not all byte segments
have been received }
}
4.2.1.3.3, 5.1.3.2.1, 5.1.3.2.2, 5.1.2.3.3 and 5.1.2.3.4.
[TS 36.322, clause 4.2.1.3.3]
...
sequence.
...
[TS 36.322, clause 5.1.3.2.1]
The receiving side of an AM RLC entity shall maintain a receiving window according to state variables VR(R) and
VR(MR) as follows:
- a SN falls within the receiving window if VR(R) <=SN <VR(MR);
- a SN falls outside of the receiving window otherwise.
When receiving a RLC data PDU from lower layer, the receiving side of an AM RLC entity shall:
- either discard the received RLC data PDU or place it in the reception buffer (see sub clause 5.1.3.2.2);
- if the received RLC data PDU was placed in the reception buffer:
needed (see sub clause 5.1.3.2.3).
- update state variables and start t-Reordering as needed (see sub clause 5.1.3.2.4).
[TS 36.322, clause 5.1.3.2.2]
When a RLC data PDU is received from lower layer, where the RLC data PDU contains byte segment numbers y to z of
an AMD PDU with SN =x, the receiving side of an AM RLC entity shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 576
576
- if x falls outside of the receiving window; or
- if byte segment numbers y to z of the AMD PDU with SN =x have been received before:
- discard the received RLC data PDU;
- else:
- place the received RLC data PDU in the reception buffer;
- if some byte segments of the AMD PDU contained in the RLC data PDU have been received before:
- discard the duplicate byte segments.
[TS 36.322, clause 5.1.3.2.3]
When a RLC data PDU with SN =x is placed in the reception buffer, the receiving side of an AM RLC entity shall:
- if all byte segments of the AMD PDU with SN =VR(MS) are received:
- update VR(MS) to the SN of the first AMD PDU with SN >current VR(MS) for which not all byte segments
have been received;
- if x =VR(R):
- if all byte segments of the AMD PDU with SN =VR(R) are received:
- update VR(R) to the SN of the first AMD PDU with SN >current VR(R) for which not all byte segments
have been received;
- update VR(MR) to the updated VR(R) +AM_Window_Size;
- reassemble RLC SDUs from any byte segments of AMD PDUs with SN that falls outside of the receiving
window and in-sequence byte segments of the AMD PDU with SN =VR(R), remove RLC headers when
doing so and deliver the reassembled RLC SDUs to upper layer in sequence if not delivered before;
- if x >=VR(H)
- update VR(H) to x+1;
- if VR(X) =VR(R); or
- if VR(X) falls outside of the receiving window and VR(X) is not equal to VR(MR):
- if t-Reordering is not running (includes the case t-Reordering is stopped due to actions above):
- if VR (H) >VR(R):
- set VR(X) to VR(H).
[TS 36.322, clause 5.1.3.2.4]
- update VR(MS) to the SN of the first AMD PDU with SN >=VR(X) for which not all byte segments have been
received;
- if VR(H) >VR(MS):
- set VR(X) to VR(H).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 577
577
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loop back size of 98 bytes.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 578
578
1 The SS transmits one AMD PDU containing
SDU#8 (100 bytes) in its data field to the UE.
SN=7 indicates the loss of 7 PDUs.
<-- AMD PDU#8 (SN=7) - -
2 The SS transmits one AMD PDU segment
containing 50 bytes of SDU#1 in its data field
to the UE. This AMD PDU segment carries
part 1 of AMD PDU#1, which contained
SDU#1 (100 bytes) in its data field. SO=0 and
LSF=0.
segment 1
- -
LSF=1.
segment 2
- -
LSF=0.
segment 1
- -
LSF=1.
segment 2
- -
part 1of AMD PDU#4, which contained SDU#4
(100 bytes) in its data field. SO=0 and LSF=0.
segment 1
- -
LSF=1.
segment 2
- -
8 Void
LSF=0.
segment 1
- -
10 Void
part 2 of PDU#3, which contained SDU#3 (100
bytes) in its data field. SO=50 and LSF=1.
segment 2
- -
11
A
The SS transmits one AMD PDU segment
part 1 of PDU #7, which contained SDU#7
(100 bytes) in its data field. SO=0 and LSF=0.
segment 1
- -
11
B
The SS transmits one AMD PDU segment
segment 2 of AMD PDU#6, which contained
LSF=1.
segment 2
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 579
579
11
C
The SS waits for 60 ms then SS transmits an
<-- (UL grant) - -
11
D
Check: Does the UE transmit an RLC SDU
containing SDU#1 in its data field?
--> (RLC SDU#1) 1 P
11
E
Check: Does the UE transmit an RLC SDU
--> (RLC SDU#2) 1 P
12 Check: Does the UE transmit an RLC SDU
--> (RLC SDU#3) 1 P
--> (RLC SDU#4) 1 P
UE. This PDU acks PDUs up to those
including SDU#4. ACK_SN=4.
<-- STATUS PDU - -
15 Void
16 Void
17 Wait for t-Reordering to run out at the UE side. - - - -
with NACK_SN=4, NACK_SN=5 with
SOStart=0 and SOEnd=49, and NACK_SN=6
with SOStart=50 and SOEnd=32767 (special
SOEnd value), and ACK_SN=8?
--> STATUS PDU 2 P
LSF=1.
segment 2
- -
LSF=0.
segment 1
- -
LSF=0.
segment 1
- -
22 Wait for t-Reordering to run out at the UE side. - - - -
with NACK_SN=4 with SOStart=50 and
SOEnd=32767 (special SOEnd value), and
ACK_SN=8?
--> STATUS PDU 2 P
LSF=1.
segment 2
- -
24
A
The SS waits for 60 ms then SS transmits an
<-- (UL grant) - -
--> (RLC SDU#5) 1 P
--> (RLC SDU#6) 1 P
--> (RLC SDU#7) 1 P
--> (RLC SDU#8) 1 P
UE. This PDU acks PDUs up to those
including SDU#7. ACK_SN=8.
<-- STATUS PDU - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 580
580
None.
7.2.3.16 AM RLC / Re-transmission of RLC PDU without re-segmentation
(1)
ensure that {
when { UE receives a STATUS PDU including a NACK_SN for missing AMD PDUs and missing AMD PDUs can
fit into within the total size of RLC PDU(s) indicated by lower layer at the particular transmission
opportunity}
then { UE successfully retransmits missing AMD PDUs without re-segmentation}
}
(2)
ensure that {
when { NACK received for missing AMD PDUs and RETX_COUNT < maxRetxThreshold }
then { UE retransmits AMD PDUs }
}
(3)
ensure that {
when { an AMD PDU or a portion of an AMD PDU is considered for retransmission and if RETX_COUNT =
maxRetxThreshold }
then { UE indicates to upper layers that max retransmission has been reached }
}

[TS 36.322 clause 5.2.1]
The transmitting side of an AM RLC entity can receive a negative acknowledgement (notification of reception failure
by its peer AM RLC entity) for an AMD PDU or a portion of an AMD PDU by the following:
When receiving a negative acknowledgement for an AMD PDU or a portion of an AMD PDU by a STATUS PDU from
its peer AM RLC entity, the transmitting side of the AM RLC entity shall:
- if the SN of the corresponding AMD PDU falls within the range VT(A) <=SN <VT(S):
- consider the AMD PDU or the portion of the AMD PDU for which a negative acknowledgement was
received for retransmission.
When an AMD PDU or a portion of an AMD PDU is considered for retransmission, the transmitting side of the AM
RLC entity shall:
- if the AMD PDU is considered for retransmission for the first time:
- set the RETX_COUNT associated with the AMD PDU to zero;
- else, if it (the AMD PDU or the portion of the AMD PDU that is considered for retransmission) or a portion of it
is not pending for retransmission already:
- increment the RETX_COUNT;
- if RETX_COUNT =maxRetxThreshold:
- indicate to upper layers that max retransmission has been reached.
When retransmitting an AMD PDU, the transmitting side of an AM RLC entity shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 581
581
- if the AMD PDU can entirely fit within the total size of RLC PDU(s) indicated by lower layer at the particular
transmission opportunity:
- deliver the AMD PDU as it is except for the P field (the P field should be set according to sub clause 5.2.2) to
lower layer;
- otherwise:
- segment the AMD PDU form a new AMD PDU segment which will fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity and deliver the new AMD PDU segment
to lower layer.
When retransmitting a portion of an AMD PDU, the transmitting side of an AM RLC entity shall:
- segment the portion of the AMD PDU as necessary, form a new AMD PDU segment which will fit within the
total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity and deliver the new
AMD PDU segment to lower layer.
When forming a new AMD PDU segment, the transmitting side of an AM RLC entity shall:
- only map the Data field of the original AMD PDU to the Data field of the new AMD PDU segment;
- set the header of the new AMD PDU segment in accordance with the description in sub clause 6.;
- set the P field according to sub clause 5.2.2.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) according to [18] with a loopback size of 98 bytes.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 582
582
U - S Message
SDU#1 (100 bytes) in its data field.
<-- AMD PDU#1 - -
2 The UE transmits one AMD PDU containing
SDU#1 in its data field.
--> AMD PDU#1 (SN=0)

- -
<-- AMD PDU#2 - -
4 The UE transmits one AMD PDU containing
--> AMD PDU#2 (SN=1)

- -
5 The SS transmits an RLC STATUS PDU.
ACK_SN=2, NACK_SN=0.
<-- STATUS PDU - -
6 Check: Does the UE transmit the AMD PDU
not yet acknowledged?
--> AMD PDU#1 (SN=0) 1 P
ACK_SN=2.
<-- STATUS PDU - -
<-- AMD PDU#3 - -
9 The UE transmits an AMD PDU containing
--> AMD PDU#3 (SN=2) - -
- EXCEPTION: Step 10 to 11 shall be repeated
maxRetxThreshold times
- - - -
ACK_SN =3 and NACK_SN =2.
<-- STATUS PDU - -
11 Check: Does the UE retransmit the AMD PDU
not yet acknowledged?
--> AMD PDU#3 (SN=2) 2 P
ACK_SN =3 and NACK_SN =2.
<-- STATUS PDU - -
Connection Re-establishment Request
message?
Note 1
- 3 P
14 The SS transmits
RRCConnectionReestablishment message.
- - - -
15 The UE transmits
RRCConnectionReestablishmentComplete
message.
- - - -
resume SRB2 and DRB1.
- - - -
message.
- - - -
Note 1: The RRC Connection Re-establishment procedure is initiated. See 36.331 cl. 5.3.7.2 and 5.3.11.3.


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 583
583
c1 CHOICE{
dicated-HO

}
}
}
}

7.2.3.17 AM RLC / Re-segmentation RLC PDU / SO, FI, LSF
(1)
ensure that {
when { AMD PDU to be retransmitted does not fit in new allocated TBS }
then { UE segments AMD PDU into AMD PDU segments }
}
(2)
ensure that {
when { AMD PDU segment to be retransmitted does not fit in new allocated TBS }
then { UE resegments AMD PDU segment to fit TBS }
}

4.2.1.3.2, 5.2.1, 6.2.1.4 and 6.2.1.5.
[TS 36.322, clause 4.2.1.3.2]
The transmitting side of an AM RLC entity supports retransmission of RLC data PDUs (ARQ):
- if the RLC data PDU to be retransmitted does not fit within the total size of RLC PDU(s) indicated by lower
layer at the particular transmission opportunity notified by lower layer, the AM RLC entity can re-segment the
RLC data PDU into AMD PDU segments;
- the number of re-segmentation is not limited.
When the transmitting side of an AM RLC entity forms AMD PDUs from RLC SDUs received from upper layer or
AMD PDU segments from RLC data PDUs to be retransmitted, it shall:
- include relevant RLC headers in the RLC data PDU.
[TS 36.322 clause 5.2.1]
...
When retransmitting an AMD PDU, the transmitting side of an AM RLC entity shall:
- if the AMD PDU can entirely fit within the total size of RLC PDU(s) indicated by lower layer at the particular
transmission opportunity:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 584
584
- deliver the AMD PDU as it is except for the P field (the P field should be set according to sub clause 5.2.2) to
lower layer;
- otherwise:
- segment the AMD PDU form a new AMD PDU segment which will fit within the total size of RLC PDU(s)
indicated by lower layer at the particular transmission opportunity and deliver the new AMD PDU segment
to lower layer.
When retransmitting a portion of an AMD PDU, the transmitting side of an AM RLC entity shall:
- segment the portion of the AMD PDU as necessary form a new AMD PDU segment which will fit within the
total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity and deliver the new
AMD PDU segment to lower layer.
When forming a new AMD PDU segment, the transmitting side of an AM RLC entity shall:
- only map the Data field of the original AMD PDU to the Data field of the new AMD PDU segment;
- set the header of the new AMD PDU segment in accordance with the description in sub clause 6.;
- set the P field according to sub clause 5.2.2.
[TS 36.322, clause 6.2.1.4]
AMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI
....
[TS 36.322, clause 6.2.1.5]
AMD PDU segment consists of a Data field and an AMD PDU segment header.
AMD PDU segment header consists of a fixed part (fields that are present for every AMD PDU segment) and an
extension part (fields that are present for an AMD PDU segment when necessary). The fixed part of the AMD PDU
segment header itself is byte aligned and consists of a D/C, a RF, a P, a FI, an E, a SN, a LSF and a SO. The extension
part of the AMD PDU segment header itself is byte aligned and consists of E(s) and LI(s).
An AMD PDU segment header consists of an extension part only when more than one Data field elements are present
in the AMD PDU segment, in which case an E and a LI are present for every Data field element except the last.
Furthermore, when an AMD PDU segment header consists of an odd number of LI(s), four padding bits follow after the
last LI.
...
System Simulator:
- Cell 1.
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 585
585
Preamble:
<-- AMD PDU#1 - -
data contents as received in the corresponding
part of DL PDU#1?
--> AMD PDU#1 (SN=0) - -
<-- AMD PDU#2 - -
data contents as received in the corresponding
part of DL PDU#2?
--> AMD PDU#2 (SN=1) - -
5 SS responds to any scheduling requests from
the UE by transmitting UL grants of size 472
bits (Note 1).
6 The SS transmits a STATUS PDU. This PDU
nacks the AMD PDU with SN=0. NACK_SN=0
and ACK_SN=2.
<-- STATUS PDU - -
segment with SO=0, LSF=0 and the same data
contents at the received positions as in the
original AMD PDU?
--> AMD PDU#1 segment 1 (SN=0) 1 P
segment with SO=<x>, LSF=1 and the same
data contents at the received positions as in
the original AMD PDU? (Note 3)
--> AMD PDU#1 segment 2 (SN=0) 1 P
9 SS responds to any scheduling requests from
the UE by transmitting UL grants of size 328
bits (Note 2).
nacks the AMD PDU with SN=0. NACK_SN=0,
SOStart=0, SOEnd=<x-1>and ACK_SN =2.
(Note 3)
<-- STATUS PDU - -
segment with SO=0, LSF=0 and the same data
contents at the received positions as in the
original AMD PDU?
--> AMD PDU#1 segment 1, 1
st
part
(SN=0)
2 P
segment with SO=<y>, LSF=0 and the same
data contents at the received positions as in
the original AMD PDU? (Note 3)
--> AMD PDU#1 segment 1, 2
nd
part
(SN=0)
2 P
acks the AMD PDUs with SN=0 and SN=1.
ACK_SN=2.
<-- STATUS PDU - -
TBS
=7, N
PRB
=4, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will segment
into 2 AMD PDUs. MAC PDU of 472 bits=59 bytes fits an AMD PDU payload of >=50 bytes +2 bytes AMD
PDU header +2 bytes of segment header + ? bytes spare for MAC header and possible RLC STATUS
PDU and BSR report.
TBS
=5, N
PRB
=4, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE will segment
into 2 AMD PDUs. MAC PDU of 328 bits=41 bytes fits an AMD PDU payload of >=25 bytes +2 bytes AMD
PDU header +2 bytes of segment header + ? bytes spare for MAC header and possible RLC STATUS
PDU and BSR report.
Note 3 The values x and y depend upon the need of the UE to add RLC STATUS PDU and BSR report. The TBS
has been chosen to ensure that the PDUs to be resegmented can be carried in 2 segments.

None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 586
586
7.2.3.18 AM RLC / Reassembly / AMD PDU reassembly from AMD PDU segments,
Segmentation Offset and Last Segment Flag fields
(1)
ensure that {
when { UE receives AM PDU segments }
then { UE delivers reassembled RLC SDU to upper layer}
}
(2)
ensure that {
when { UE receives RLC AM PDU segments without segment header extension part }
then { UE correctly reassembles RLC AMD PDU segments into RLC AMD PDUs }
}
(3)
ensure that {
when { UE receives RLC AM PDU segments with segment header extension part }
then { UE correctly reassembles RLC AMD PDU segments into RLC AMD PDUs }
}
(4)
ensure that {
when { UE receives duplicate RLC AM PDU segments }
then { UE discards duplicate RLC AMD PDU segments }
}
(5)
ensure that {
when { UE receives RLC AM PDU segments out of sequence }
then { UE delivers reassembled RLC SDU to upper layer }
}
(6)
ensure that {
when { UE receives RLC AMD PDU segments with segments lost }
then { UE transmits STATUS PDU to request retransmission of missing segments }
}
(7)
ensure that {
when { UE receives overlapping RLC AMD PDU segments }
then { UE discards duplicate RLC AMD PDU byte segments }
}

4.2.1.3.3, 5.1.3.2.2, 6.2.1.4 and 6.2.1.5.
[TS 36.322, clause 4.2.1.3.3]
PDUs;
- reorder the RLC data PDUs if they are received out of sequence;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 587
587
sequence.
...
[TS 36.322, clause 5.1.3.2.2]
When a RLC data PDU is received from lower layer, where the RLC data PDU contains byte segment numbers y to z of
an AMD PDU with SN =x, the receiving side of an AM RLC entity shall:
- if x falls outside of the receiving window; or
- if byte segment numbers y to z of the AMD PDU with SN =x have been received before:
- discard the received RLC data PDU;
- else:
- place the received RLC data PDU in the reception buffer;
- if some byte segments of the AMD PDU contained in the RLC data PDU have been received before:
- discard the duplicate byte segments.
[TS 36.322, clause 6.2.1.4]
AMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI.
...
[TS 36.322, clause 6.2.1.5]
AMD PDU segment consists of a Data field and an AMD PDU segment header.
AMD PDU segment header consists of a fixed part (fields that are present for every AMD PDU segment) and an
extension part (fields that are present for an AMD PDU segment when necessary). The fixed part of the AMD PDU
segment header itself is byte aligned and consists of a D/C, a RF, a P, a FI, an E, a SN, a LSF and a SO. The extension
part of the AMD PDU segment header itself is byte aligned and consists of E(s) and LI(s).
An AMD PDU segment header consists of an extension part only when more than one Data field elements are present
in the AMD PDU segment, in which case an E and a LI are present for every Data field element except the last.
Furthermore, when an AMD PDU segment header consists of an odd number of LI(s), four padding bits follow after the
last LI.
...
System Simulator:
- Cell 1.
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 588
588
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 589
589
first half (50 bytes) of SDU#1 in its data field.
This PDU is in error (SN falls outside of the
receiving window) and is to be discarded by
the UE.
<-- AMD PDU#1 (SN=WindowSize+3) - -
2 The SS transmits an AMD PDU containing
SDU#2 (100 bytes) in its data field with the P-
bit set.
<-- AMD PDU#2 (SN=1, P=1) - -
NACK_SN field indicating missing PDU#1.
ACK_SN=2, NACK_SN=0.
--> STATUS PDU - -
3A The SS stops the UL grant transmission. - - - -
segment of AMD PDU#1 (AMD PDU#1 carries
SDU#1) containing the first 50 bytes of SDU#1
in its data field. SO=0 and LSF=0. No header
extension part is provided.
segment 1
- -
5 The SS transmits an AMD PDU segment of
AMD PDU#1 (AMD PDU#1 carries SDU#1)
containing the last 50 bytes of SDU#1 in its
data field with the P-bit set. SO=50 and
LSF=1. No header extension part is provided.
<-- AMD PDU #1 (SN=0, P=1)
segment 2
- -
assigns one default UL grant (UL grant
allocation type 3).
<-- (UL grant) - -
with ACK_SN=2, thus acknowledging the
reception of PDUs with SN=0 and SN=1, and
no NACK_SN provided?
--> STATUS PDU 2 P
7 Check: Does the UE transmit RLC SDU#1 and
RLC SDU#2?
SDU#2)
1 P
8 Void - - - -
SDU#3 and SDU#4) containing the last 50
bytes of SDU#4 in its data field, with the P-bit
set. FI=10, SO=150 and LSF=1. No header
<-- AMD PDU#3 (SN=2, P=1)
segment 2
- -
9A 100 ms after step 9 the SS assigns one default
grant (UL grant allocation type 3).
<-- (UL grant) - -
10 The UE transmits a STATUS PDU NACK_SN
field for receipt of PDU#3. ACK_SN=3,
NACK_SN=2, SOStart=0/SOEnd=149.
--> STATUS PDU - -
SDU#3 and SDU#4) containing SDU#3 (100
bytes) and the first 50 bytes of SDU#4 in its
data field, with the P-bit set. FI=01, SO=0 and
LSF=0. Header extension part present: E in
fixed part header=1, E in extension part
header=0, LI=100.
<-- AMD PDU#3 (SN=2, P=1)
segment 1
- -
11
A
assigns one default UL grant.
<-- (UL grant) - -
with ACK_SN=3?
--> STATUS PDU 3 P
13 Void - - - -
RLC SDU#4?
SDU#4)
1,5 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 590
590
14
A
segment 1
- -
containing the first 50 bytes of SDU#5 in its
data field. SO=0 and LSF=0. No header
segment 1
- -
containing the last 50 bytes of SDU#5 in its
data field, with the P-bit set. SO=50 and
<-- AMD PDU#4 (SN=3, P=1)
segment 2
- -
17
A
allocation type 3).
<-- (UL grant) - -
reception of PDUs with SN=0 to SN=3, and no
NACK_SN provided?
--> STATUS PDU 4 P
19
A
SDU#7) containing the last 50 bytes of SDU#7
in its data field, with the P-bit set. This AMD
PDU segment is sent with SN=5. SO=50 and
<-- AMD PDU#6 (SN=5, P=1)
segment 2
- -
20
A
100 ms after step 20 the SS assigns one
default grant (UL grant allocation type 3).
<-- (UL grant) - -
reception of PDUs with SN=0 to SN=5, and
NACK_SN=4, E1/E2 field for receipt of PDU#5
and NACK_SN=5, SOStart=0/SOEnd=49 for
segment 1 of PDU#6?
--> STATUS PDU 6 P
segment 1
- -
SDU#6 (100 bytes) in its data field, with the P-
bit set.
<-- AMD PDU#5 (SN=4, P=1)

- -
23
A
allocation type 3).
<-- (UL grant) - -
ACK_SN=6, thus acknowledging the reception
of PDUs with SN=0 to SN=5, and no
NACK_SN provided.
--> STATUS PDU - -
RLC SDU#7?
SDU#7)
2,5 P
26
A
SDU#8, SDU#9 and SDU#10) containing the
last 20 bytes of SDU#9 and the complete
SDU#10 (100 bytes) in its data field, with the
<-- AMD PDU#7 (SN=6, P=1)
segment 3
- -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 591
591
P-bit set. FI=10, SO=180 and LSF=1. Header
extension part present: E in fixed part
header=1, E in extension part header=0,
LI=20.
27
A
100 ms after step 27 the SS assigns one
default grant (UL grant allocation type 3).
<-- (UL grant) - -
--> STATUS PDU - -
SDU#8, SDU#9 and SDU#10) containing the
last 20 bytes of SDU#8 and the complete
SDU#9 in its data field, with the P-bit set.
FI=10, SO=80 and LSF=0. Header extension
part present: E in fixed part header=1, E in
extension part header=0, LI=20.
<-- AMD PDU#7 (SN=6, P=1)
segment 2
- -
29
A
30 ms after step 29 the SS assigns one default
grant (UL grant allocation type 3).
<-- (UL grant) - -
--> STATUS PDU 7 P
31 60 ms after step 29 the SS transmits an AMD
PDU segment of AMD PDU#7 (AMD PDU#7
carries SDU#8, SDU#9 and SDU#10)
containing the first 80 bytes of SDU#8 in its
data field, with the P-bit set. SO=0 and LSF=0.
No header extension part is provided.
Note 4
<-- AMD PDU#7 (SN=6, P=1)
segment 1
- -
31
A
allocation type 3).
<-- (UL grant) - -
reception of PDUs with SN=0 to SN=6, and no
NACK_SN provided?
--> STATUS PDU 7 P
33 Void - - - -
34 Void - - - -
35 Check: Does the UE transmit RLC SDU#8,
RLC SDU#9 and RLC SDU#10?
SDU#9, RLC SDU#10)
7 P
Note 1: From steps 4 onwards, the transmission of AMD PDUs is scheduled. The activation time of 100 ms for the
first of possibly several AMD PDUs is greater than t-StatusProhibit, and therefore there is no need to wait
for the expiry of this timer. Subsequent AMD PDU transmissions are using subsequent TTIs.
Note 2: In steps 6-8, 12-14, 18-19, 24-26, 32-35 the STATUS PDU and the AMD PDU consisting of one or more
RLC SDUs are received as a PDU list in one TTI.
Note 3: In step 29A it is assumed that the UE will react upon the AMD PDU within 30 ms.
Note 4: Step 31 shall be executed within 60ms after step 29 to ensure that the UE receives the AMD PDU before
the expiry of t-Reordering at the UE.

None.
7.2.3.19 Void
7.2.3.20 AM RLC / Duplicate detection of RLC PDUs
(1)
ensure that {
when { UE is in AM mode and receives duplicated RLC data PDUs having the same sequence number}
then { UE discards the duplicated RLC data PDUs }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 592
592
}
References: The conformance requirements covered in the current TC are specified in: TS 36.322, clause 4.2.1.3.3.
[TS 36.322, clause 4.2.1.3.3]
PDUs;

System Simulator:
- Cell 1.
UE:
None.
Preamble:
U - S Message
1 SS creates 3 RLC SDUs of size 40 bytes
segmented into two AMD PDUs each. AMD
PDU#1 and AMD PDU#2 belong to RLC
SDU#1, AMD PDU#3 and #4 belong to RLC
SDU#2 and AMD PDU#5 and #6 belong to
RLC SDU#3.

SS transmits AMD PDU#1 with SN=0, AMD
PDU#2 with SN=1 and AMD PDU#3 twice with
SN=2.
<-- RLC AMD PDU#1 (SN=0)
RLC AMD PDU#2 (SN=1)
- -
2 Check: Does the UE transmit RLC SDU#1?
(Note 1)
--> (RLC SDU#1) 1 P
3 SS transmits AMD PDU#4 with SN=3. <-- RLC AMD PDU#4 (SN=3) - -
5 SS transmits AMD PDU#6 twice with SN=5.

<-- RLC AMD PDU#6 (SN=5)

- -
6 SS transmits AMD PDU#5 twice with SN=4. <-- RLC AMD PDU#5 (SN=4)
- -
7 Check: Does the UE transmit RLC SDU#3
once?
(Note 2)
--> (RLC SDU#3) 1 P
Note 1: The duplicated AMD PDU#3 have been discarded by the conformant UE in step 1.
Note 2: The duplicated AMD PDU#5 and AMD PDU#6 have been discarded by the conformant UE in steps 5 and
6.

7.2.3.20.3.3 Specific message content
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 593
593
7.2.3.21 AM RLC / RLC re-establishment at RRC connection reconfiguration including
mobilityControlInfo IE
(1)
ensure that {
when { UE is requested to perform a RRC Connection reconfiguration including mobilityControlInfo
IE }
then { UE discards the remaining AMD PDUs; and discards all RLC SDUs in the transmitting side;
and reset all state variables to their initial values. }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.322, clause 5.4 and TS
36.331 clause 5.3.5.4.
[TS 36.322, clause 5.4]
RLC re-establishment is performed upon request by RRC, and the function is applicable for AM, UM and TM RLC
entities.
When RRC indicates that an RLC entity should be re-established, the RLC entity shall:

- if it is an AM RLC entity:
- when possible, reassemble RLC SDUs from any byte segments of AMD PDUs with SN <VR(MR) in the
receiving side, remove RLC headers when doing so and deliver all reassembled RLC SDUs to upper layer in
ascending order of the RLC SN, if not delivered before;
- discard the remaining AMD PDUs and byte segments of AMD PDUs in the receiving side;
- discard all RLC SDUs and AMD PDUs in the transmitting side;
- discard all RLC control PDUs.
- stop and reset all timers;
- reset all state variables to their initial values.
[TS 36.331, clause 5.3.5.4]
If the RRCConnectionReconfiguration message includes the mobilityControlInfo and theUE is able to comply with the
configuration included in this message, the UE shall:
.
1>re-establish RLC for all RBs that are established;

System Simulator:
- Cell 1.
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 594
594
Preamble:
1.
Parameter Value
t-Reordering ms150

U - S Message
- - - -
1 SS creates 3 RLC SDUs of size 40 bytes
segmented into two AMD PDUs each. AMD
PDU#1 and AMD PDU#2 belong to RLC
SDU#1, AMD PDU#3 and #4 belong to RLC
SDU#2 and AMD PDU#5 and #6 belong to
RLC SDU#3. SS transmits AMD PDU#1
(SN=0), AMD PDU#2 (SN=1) and AMD
PDU#4 (SN=3).
<-- AMD PDU#1
AMD PDU#2
AMD PDU#4
- -
1A 60 ms after step 1 the SS allocates 1 UL grant
of default size
<-- (UL grant)
2 The UE returns RLC SDU#1. --> (RLC SDU#1) - -
3 SS does not acknowledge the reception of
RLC SDU#1.
- - - -
4 90 ms after step 1 SS performs a RRC
Connection Reconfiguration procedure
including the mobilityControlInfo IE triggering
RLC-reestablishment.
(Note 1)
- - - -
4A
A
The SS starts the UL default grant
transmissions
- - - -
4A The UE retransmits RLC SDU #1.
(Note 1A)
--> (RLC SDU#1) - -
4B SS transmits a STATUS PDU (ACK_SN =1). <-- STATUS PDU - -
5 SS transmits AMD PDU#5 with SN=0 and the
P field set to "1"
<-- AMD PDU#5 - -
6 Check: Does the UE transmit a STATUS
PDU?
(Note 2)
--> STATUS PDU (ACK_SN =1) 1 P
7 SS transmits AMD PDU#6 with
SN=Receiving_AM_Window_Size+2
<-- AMD PDU#6 - -
8 Check: Does the UE return RLC SDU#3 within
1s?
(Note 3)
-->
(RLC SDU#3) 1 F
9 SS transmits AMD PDU#6 with SN=1 <-- AMD PDU#6 - -
10 Check: Does the UE return RLC SDU#3 with
its first AMD PDU set to SN=1?
-->
(RLC SDU#3) 1 P
Note 1: Upon a RLC re-establishment a conformant UE discards any remaining AMD PDUs in the receiver and
transmitter side, stops and resets all timers and resets all state variables to their initial values.
Note 1A: The UE will retransmit the PDCP SDU associated with RLC SDU#1 in accordance to TS 36.323 clause
5.2.1.1.
Note 2: AMD PDU#4 is discarded by a conformant UE in step 4.
Note 3: AMD PDU#6 is discarded by a conformant UE due to being outside the receiving window size.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 595
595
Derivation Path: 36.508 table 4.6.1-8: RRCConnectionReconfiguration, condition HO
c1 CHOICE{
mobilityControlInfo SEQUENCE {
targetPhysCellId Set to the physical cell
identity of cell 1

}
radioResourceConfigCommon Not present
}
}
}
}

7.3 PDCP
7.3.1 Maintenance of PDCP sequence numbers for radio bearers
7.3.1.1 Maintenance of PDCP sequence numbers / User plane / RLC AM
(1)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on AM RLC }
then { UE increments SN with 1 for each transmitted PDU for SN=0 to Maximum_PDCP_SN }
}
(2)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on AM RLC and, after incrementation,
Next_PDCP_TX_SN is larger than the Maximum_PDCP_SN }
then { UE sets SN to 0 in the next transmitted PDCP SDU}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.1.1,
5.1.2.2 and 6.2.3.
[TS 36.323, clause 5.1.1]
At reception of a PDCP SDU from upper layers, the UE shall:
- discardTimerstart the associated with this PDCP SDU (if configured);
For a PDCP SDU received from upper layers, the UE shall:
- associate the PDCP SN corresponding to Next_PDCP_TX_SN to this PDCP SDU;
- perform header compression of the PDCP SDU (if configured) as specified in the subclause 5.5.4;
- perform integrity protection (if applicable), and ciphering (if applicable) using COUNT based on TX_HFN and
the PDCP SN associated with this PDCP SDU as specified in the subclause 5.7 and 5.6, respectively;
- increment Next_PDCP_TX_SN by one;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 596
596
- if Next_PDCP_TX_SN >Maximum_PDCP_SN:
- set Next_PDCP_TX_SN to 0;
- increment TX_HFN by one;
- submit the resulting PDCP Data PDU to lower layer.
[TS 36.323, clause 5.1.2.1.2]
For DRBs mapped on RLC AM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- if received PDCP SN Last_Submitted_PDCP_RX_SN >Reordering_Window or 0 <=
Last_Submitted_PDCP_RX_SN received PDCP SN <Reordering_Window:
- if received PDCP SN >Next_PDCP_RX_SN:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN - 1 and the
received PDCP SN;
- else:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN and the
received PDCP SN;
- perform header decompression (if configured) as specified in the subclause 5.5.5;
- discard this PDCP SDU;
- else if Next_PDCP_RX_SN received PDCP SN >Reordering_Window:
- increment RX_HFN by one;
- use COUNT based on RX_HFN and the received PDCP SN for deciphering the PDCP PDU;
- set Next_PDCP_RX_SN to the received PDCP SN +1;
- else if received PDCP SN Next_PDCP_RX_SN >=Reordering_Window:
- use COUNT based on RX_HFN 1 and the received PDCP SN for deciphering the PDCP PDU;
- else if received PDCP SN >=Next_PDCP_RX_SN:
- if Next_PDCP_RX_SN is larger than Maximum_PDCP_SN:
- set Next_PDCP_RX_SN to 0;
- else if received PDCP SN <Next_PDCP_RX_SN:
- if the PDCP PDU has not been discarded in the above:
- perform deciphering and header decompression (if configured) for the PDCP PDU as specified in the
subclauses 5.6 and 5.5.5, respectively;
- if a PDCP SDU with the same PDCP SN is stored:
- else:
- store the PDCP SDU;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 597
597
- if the PDCP PDU received by PDCP is not due to the re-establishment of lower layers:
- deliver to upper layers in ascending order of the associated COUNT value:
- all stored PDCP SDU(s) with an associated COUNT value less than the COUNT value associated with
the received PDCP SDU;
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT value
associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers;
- else if received PDCP SN =Last_Submitted_PDCP_RX_SN +1 or received PDCP SN =
Last_Submitted_PDCP_RX_SN Maximum_PDCP_SN:
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT value
associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers.
[TS 36.323, clause 6.2.3]
Figure 6.2.3.1 shows the format of the PDCP Data PDU when a 12 bit SN length is used. This format is applicable for
PDCP Data PDUs carrying data from DRBs mapped on RLC AM or RLC UM.
...
PDCP SN (cont.)
Data
D/C PDCP SN R R R Oct 1
Oct 2
Oct 3

Figure 6.2.3.1: PDCP Data PDU format for DRBs using a 12 bit SN

System Simulator
- Cell 1
- SS PDCP set to Transparent Mode
UE:
None.
Preamble
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 598
598

None
7.3.1.2 Maintenance of PDCP sequence numbers / User plane / RLC UM / Short
PDCP SN (7 bits)
(1)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for short PDCP SN
size (7 bits)}
}
(2)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for short PDCP SN
size (7 bits); and, after incrementation, Next_PDCP_TX_SNis larger than the Maximum_PDCP_SN }
}
5.1.2.1.3 and 6.2.4.
[TS 36.323, clause 5.1.1]
- start the discardTimer associated with this PDCP SDU (if configured);
U - S Message
- EXCEPTION: Steps 1 and 2 shall be repeated
for k=0 to Maximum_PDCP_SN (increment=1).

1 SS transmits a PDCP Data PDU on DRB1
containing one IP packet without header
compression.
<-- PDCP Data PDU (SN =k)
2 CHECK: Does UE transmit a PDCP Data PDU
with SN=0 for the first iteration and then
incremented by 1 at each iteration?
--> PDCP Data PDU (SN =k) 1 P
3 SS transmits a PDCP Data PDU on DRB1
compression.
<-- PDCP Data PDU (SN =0)
with SN=0?
--> PDCP Data PDU (SN =0) 2 P
5 SS sends a PDCP Data PDU on DRB1
compression.
with SN=1?
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 599
599
[TS 36.323, clause 5.1.2.1.3]
For DRBs mapped on RLC UM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- if received PDCP SN <Next_PDCP_RX_SN:
- decipher the PDCP Data PDU using COUNT based on RX_HFN and the received PDCP SN as specified in the
subclause 5.6;
- if Next_PDCP_RX_SN >Maximum_PDCP_SN:
- perform header decompression (if configured) of the deciphered PDCP Data PDU as specified in the subclause
5.5.5;
- deliver the resulting PDCP SDU to upper layer.
[TS 36.323, clause 6.2.4]
PDCP Data PDUs carrying data from DRBs mapped on RLC UM.
...
D/C PDCP SN Oct 1
Oct 2 Data

Figure 6.2.4.1: PDCP Data PDU format for DRBs using 7 bit SN

System Simulator
- Cell 1
UE:
None.
Preamble
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 600
600

None
7.3.1.3 Maintenance of PDCP sequence numbers / User plane / RLC UM / Long
PDCP SN (12 bits)
(1)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for long PDCP SN size
(12 bits)}
}
(2)
ensure that {
when { UE transmits a PDCP Data SDU on a DRB mapped on UM RLC and configured for long PDCP SN size
(12 bits); and,after incrementation, Next_PDCP_TX_SN is larger than the Maximum_PDCP_SN limit }
}
5.1.2.1.3 and 6.2.3.
[TS 36.323, clause 5.1.1]
- start the discardTimer associated with this PDCP SDU (if configured);
U - S Message

1 SS transmits a PDCP Data PDU on UM DRB
compression.
compression.
with SN=0?
5 SS sends a PDCP Data PDU on UM DRB
compression.
with SN=1?
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 601
601
[TS 36.323, clause 5.1.2.1.3]
For DRBs mapped on RLC UM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- decipher the PDCP Data PDU using COUNT based on RX_HFN and the received PDCP SN as specified in the
subclause 5.6;
- perform header decompression (if configured) of the deciphered PDCP Data PDU as specified in the subclause
5.5.5;
- deliver the resulting PDCP SDU to upper layer.
[TS 36.323, clause 6.2.3]
PDCP Data PDUs carrying data from DRBs mapped on RLC AM or RLC UM.
...
PDCP SN (cont.)
Data
D/C PDCP SN R R R Oct 1
Oct 2
Oct 3

Figure 6.2.3.1: PDCP Data PDU format for DRBs using a 12 bit SN

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 602
602
System Simulator
- Cell 1
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] with the RLC UM bearer configured for long
PDCP SN size (12 bits).

None
7.3.2 Void
7.3.3 PDCP ciphering and deciphering
7.3.3.1 Ciphering and deciphering / Correct functionality of EPS AS encryption
algorithms / SNOW 3G
(1)
with { UE in RRC_IDLE/E-UTRA RRC_CONNECTED state }
ensure that {
when { Functionality of EPS AS encription algorithms with SNOW 3G is taken into use }
then { UE performs correct AS ciphering function in PDCP entities associated with SRBs. }
}
U - S Message

compression.
compression.
with SN=0?
5 SS sends a PDCP Data PDU on UM DRB
compression.
with SN=1?
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 603
603

[TS 36.323, clause 5.6]
The ciphering function includes both ciphering and deciphering and is performed in PDCP. For the control plane, the
data unit that is ciphered is the data part of the PDCP PDU (see subclause 6.3.3) and the MAC-I (see subclause 6.3.4).
For the user plane, the data unit that is ciphered is the data part of the PDCP PDU (see subclause 6.3.3); ciphering is not
applicable to PDCP Control PDUs.
The ciphering algorithm and key to be used by the PDCP entity are configured by upper layers [3] and the ciphering
method shall be applied as specified in [6].
The ciphering function is activated by upper layers [3]. After security activation, the ciphering function shall be applied
to all PDCP PDUs indicated by upper layers [3] for the downlink and the uplink, respectively.
The parameters that are required by PDCP for ciphering are defined in [6] and are input to the ciphering algorithm. The
required inputs to the ciphering function include the COUNT value, and DIRECTION (direction of the transmission: set
as specified in [6]).The parameters required by PDCP which are provided by upper layers [3] are listed below:
- BEARER (defined as the radio bearer identifier in [6]. It will use the value RB identity 1 as in [3]);
- KEY (the ciphering keys for the control plane and for the user plane are K
RRCenc
and K
UPenc
, respectively).
System Simulator:
- Cell 1.
UE:
- None.
Preamble:
- The UE shall be in Registered Idle Mode (State 2) according to [18].
U - S Message
1 The SS sends a Paging message to the UE on the
appropriate paging block, and including the UE
identity in one entry of the IE pagingRecordLists.
<-- Paging (PCCH) - -
2 Check: Does The UE transmit a
RRCConnectionRequest message withoutrelated
PDCP Data PDU being ciphered?
message. This message related PDCP Data PDU
should not be integrity protected and ciphered.
<--
RRCConnectionSetup - -
4 Check: Does the UE transmit a
session management procedure by including the
SERVICE REQUEST message (State3), and
without related PDCP Data PDU being ciphered?
--> RRCConnectionSetupCompl
ete
1 P
5 The SS transmits a SecurityModeCommand
message to activate EPS AS encryption algorithm
<-- SecurityModeCommand - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 604
604

Table 7.3.3.1.3.3-1 SecurityModeCommand (step 6, Table 7.3.3.1.3.2-1)
Derivation Path: TS36.508 clause 4.6.1 table 4.6.1-19
SecurityModeCommand ::=SEQUENCE {

c1 CHOICE{
securityModeCommand-r8 SEQUENCE {
securityConfigSMC SEQUENCE {
securityAlgorithmConfig SEQUENCE {
cipheringAlgorithm eea1
integrityProtAlgorithm Default value specified
in TS 36.508

}
}
}
}
}
}

7.3.3.2 Ciphering and deciphering / Correct functionality of EPS UP encryption
algorithms / SNOW 3G
(1)
ensure that {
when { UE is requested to achieve functionality of EPS UP encription algorithms with SNOW 3G }
then { UE performs correct UP ciphering function in PDCP entities associated with DRBs. }
}

[TS 36.323, clause 5.6]
security. The message related PDCP Data PDU
should be integrity protected but not ciphered.
SecurityModeComplete message and establishes
the initial security configuration withoutthe
message related PDCP Data PDU being
ciphered?
--> SecurityModeComplete 1 P
7 The SS configures a new data radio bearer,
associated with the default EPS bearer context.
This message related PDCP Data PDU should be
integrity protected and ciphered. The COUNT of
this message related PDCP Data PDU can be
used for deciphering.
<-- RRCConnectionReconfigurat
ion
- -
8 The UE transmits a
message to confirm the establishment of the new
data radio bearer, associated with the default
EPS bearer context. This message related PDCP
Data PDU should be integrity protected and
ciphered. The COUNT of this message related
PDCP Data PDU can be used for deciphering.
--> RRCConnectionReconfigurat
ionComplete
1 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 605
605
The ciphering function includes both ciphering and deciphering and is performed in PDCP. For the control plane, the
data unit that is ciphered is the data part of the PDCP PDU (see subclause 6.3.3) and the MAC-I (see subclause 6.3.4).
For the user plane, the data unit that is ciphered is the data part of the PDCP PDU (see subclause 6.3.3); ciphering is not
applicable to PDCP Control PDUs.
The ciphering algorithm and key to be used by the PDCP entity are configured by upper layers [3] and the ciphering
method shall be applied as specified in [6].
The ciphering function is activated by upper layers [3]. After security activation, the ciphering function shall be applied
to all PDCP PDUs indicated by upper layers [3] for the downlink and the uplink, respectively.
The parameters that are required by PDCP for ciphering are defined in [6] and are input to the ciphering algorithm. The
required inputs to the ciphering function include the COUNT value, and DIRECTION (direction of the transmission: 0
for uplink, 1 for downlink).The parameters required by PDCP which are provided by upper layers [3] are listed below:
- KEY (the ciphering keys for the control plane and for the user plane are K
RRCenc
and K
UPenc
, respectively).
System Simulator:
- Cell 1.
UE:
- None.
Preamble
- The UE shall be in Loopback Activation state (State 4) according to TS36.508.
Table 7.3.3.2.3.2-1: Main Behavior

U - S Message
1 SS Transmits PDCP PDU on DRB ciphered. <-- PDCP PDU - -
2 Check: Does the UE transmit loop backed PDCP
PDU ciphered.
--> PDCP PDU 1 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 606
606
Table 7.3.3.2.3.3-1 SecurityModeCommand (in the preamble)
c1 CHOICE{

}
}
}
}
}

7.3.3.3 Ciphering and deciphering / Correct functionality of EPS AS encryption
algorithms / AES
(1)
ensure that {
when { UE is requested to achieve functionality of EPS AS encription algorithms with AES }
then { UE performs correct AS ciphering function in PDCP entities associated with SRBs. }
}

Same Pre-test conditions as in clause 7.3.3.1.3.1.
Same Test procedure sequence as in Table 7.3.3.1.3.2.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 607
607
Table 7.3.3.3.3.3-1 SecurityModeCommand (step 6)

c1 CHOICE{
}
}
}
}
}

7.3.3.4 Ciphering and deciphering / Correct functionality of EPS UP encription
algorithms / AES
(1)
ensure that {
when { UE is requested to achieve functionality of EPS UP encription algorithms with AES }
then { UE performs correct UP ciphering function in PDCP entities associated with DRBs. }
}

Same Conformance requirements as in clause 7.3.3.2.2.
Same Test procedure sequence as in Table 7.3.3.2.3.2.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 608
608
Table 7.3.3.4.3.3-1 SecurityModeCommand (in the preamble)

c1 CHOICE{
securityConfigSMC SEQUENCE
{securityModeCommand-r8 SEQUENCE {

Not present
}
}
}
}
}

7.3.4 PDCP integrity protection
7.3.4.1 Integrity protection / Correct functionality of EPS AS integrity algorithms /
SNOW3G
(1)
ensure that {
when { Functionality of EPS AS integrity algorithms with SNOW3G is taken into use }
then { UE performs the integrity protection function in PDCP entities associated with SRBs. }
}

(2)
ensure that {
when { SecurityModeCommand fails the integrity protection check }
then { UE transmits SecurityModeFailure message and continues using the configuration used
prior to the reception of the SecurityModeCommand message }
}

(3)
ensure that {
when { UE has AS security activated and integrity check fails }
then { UE initiates RRC connection re-establishment procedure }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.7
[TS 36.323, clause 5.7]
The integrity protection function includes both integrity protection and integrity verification and is performed in PDCP
for PDCP entities associated with SRBs. The data unit that is integrity protected is the PDU header and the data part of
the PDU before ciphering.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 609
609
The integrity protection algorithm and key to be used by the PDCP entities are configured by upper layers [3] and the
integrity protection method shall be applied as specified in [6].
The integrity protection function is activated by upper layers [3]. After security activation, the integrity protection
function shall be applied to all PDUs including and subsequent to the PDU indicated by upper layers [3] for the
downlink and the uplink, respectively.
NOTE: As the RRC message which activates the integrity protection function is itself integrity protected with the
configuration included in this RRC message, this message needs first be decoded by RRC before the
integrity protection verification could be performed for the PDU in which the message was received.
The parameters that are required by PDCP for integrity protection are defined in [6] and are input to the integrity
protection algorithm. The required inputs to the integrity protection function include the COUNT value, and
DIRECTION (direction of the transmission: set as specification in [6]). The parameters required by PDCP which are
provided by upper layers [3] are listed below:
- KEY (K
RRCint
).
At transmission, the UE computes the value of the MAC-I field and at reception it verifies the integrity of the PDCP
PDU by calculating the X-MAC based on the input parameters as specified above. If the calculated X-MAC
corresponds to the received MAC-I, integrity protection is verified successfully.
[TS 36.323, clause 5.1.2.2]
- if integrity verification is not applicable:
- deliver the resulting PDCP SDU to upper layer;
- else, if integrity verification is applicable and the integrity verification fails:
- discard the received PDCP Data PDU;
- indicate the integrity verification failure to upper layer.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Registered, Idle Mode (State 2) according to [18].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 610
610
U - S Message
1 The SS sends a Paging message to the UE on
the appropriate paging block, and including the
UE identity in one entry of the IE
pagingRecordLists.
- Paging (PCCH) - -
RRCConnectionRequest message without
related PDCP Data PDU being integrity
protected?
>-
RRC
Conn
ection
Requ
est-
1 P
message. The message related PDCP Data
PDU is not integrity protected.
4 Does: The UE transmit a
session management procedure by including
the SERVICE REQUEST message without
related PDCP Data PDU being integrity
protected?
message to activate AS security with
SNOW3G integrity algorithms protected.
SecurityModeComplete message with
SNOW3G integrity algorithms and RRC
integrity key protected and establish the initial
security configuration.
7 Check: Does the SecurityModeComplete
message from the UE pass the SS integrity
protection check.
- - 1 P
message.
9 Wait for 5 s for the UE to enter E-UTRA
RRC_IDLE state.
- -
a matched identity.
<-- Paging - -
11 The UE transmit an RRCConnectionRequest
message.
message.
This message includes a SERVICE REQUEST
message.
message. MAC-I is calculated in such way, it
will result in integrity check failure on UE side.
SecurityModeFailure message without integrity
protection nor ciphering?
--> SecurityModeFailure 2 P
message to activate AS security with
SNOW3G integrity algorithms protected.
17 The UE transmits a SecurityModeComplete
message. The message related PDCP Data
PDU should be integrity protected but not
ciphered.
--> SecurityModeComplete - -
18 The SS transmits an UECapabilityEnquiry
message to initiate the UE radio access
capability transfer procedure. MAC-I is
<-- UECapabilityEnquiry - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 611
611
calculated in such way, it will result in integrity
check failure on UE side.
RRCConnectionReestablishmentRequest
message on Cell 1?
--> RRCConnectionReestablishment
Request
3 P
20 The SS transmits a
RRCConnectionReestablishment message
<-- RRCConnectionReestablishment - -
21 The UE transmits
message.
Complete
- -
indicate that the UE is in E-UTRA
- - - -

Table 7.3.4.1.3.3-1: SecurityModeCommand message (steps 5, 14 and 16, Table 7.3.4.1.3.2-1)

c1 CHOICE{
integrityProtAlgorithm eia1 128-EIA1
SNOW 3G

}
}
}
}
}
}

Table 7.3.4.1.3.3-2: RRCConnectionReestablishmentRequest (step 19, Table 7.3.4.1.3.2-1)
RRCConnectionReestablishmentRequest ::=
SEQUENCE {

rrcConnectionReestablishmentRequest-r8
SEQUENCE {

ue-Identity SEQUENCE {
c-RNTI the value of the C-RNTI
of the UE

physCellId PhysicalCellIdentity of
Cell 1

shortMAC-I The same value as the
16 least significant bits of
the XMAC-I value
calculated by SS

}
reestablishmentCause otherFailure
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 612
612
7.3.4.2 Integrity protection / Correct functionality of EPS AS integrity algorithms /
AES
(1)
ensure that {
when { Functionality of EPS AS integrity algorithms with AES is taken into use }
then { UE performs the integrity protection function in PDCP entities associated with SRBs. }
}
(2)
ensure that {
when { SecurityModeCommand fails the integrity protection check }
then { UE transmits SecurityModeFailure message and continues using the configuration used
prior to the reception of the SecurityModeCommand message }
}

(3)
ensure that {
when { UE has AS security activated and integrity check fails }
then { UE initiates RRC connection re-establishment procedure }
}

Same Test procedure sequence as in table 7.3.4.1.3.2-1, except the integrity protection algorithm is AES.
Table 7.3.4.2.3.3-1: SecurityModeCommand message (step 5, 14 and 16, Table 7.3.4.1.3.2-1)

c1 CHOICE{
integrityProtAlgorithm eia2 128-EIA2 AES
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 613
613
SEQUENCE {

SEQUENCE {

of the UE

Cell 1

the XMAC-I value
calculated by SS

}
}
}
}

7.3.5 PDCP handover
7.3.5.1 Void
7.3.5.2 PDCP handover / Lossless handover / PDCP sequence number
maintenance
(1)
with {UE in E-UTRA RRC_CONNECTED state with default RB using RLC-AM}
ensure that {
when { UE is requested to make a lossless handover by SS }
then { UE retransmits the unacknowledged data}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.2.1.1.
[TS 36.323, clause 5.2.1.1]
When upper layers request a PDCP re-establishment, the UE shall:
- reset the header compression protocol for uplink (if configured);
- apply the ciphering algorithm and key provided by upper layers during the re-establishment procedure;
- from the first PDCP SDU for which the successful delivery of the corresponding PDCP PDU has not
been confirmed by lower layers, perform retransmission or transmission of all the PDCP SDUs already
associated with PDCP SNs in ascending order of the COUNT values associated to the PDCP SDU prior
to the PDCP re-establishment as specified below:
- perform ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in
the subclause 5.6;
- submit the resulting PDCP Data PDU to lower layer
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 614
614
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
Table 7.3.5.2.3.2.0-1: Time instances of cell power level
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 615
615
U - S Message
1 The SS creates 5 PDCP Data PDUs and the
Next_PDCP_TX_SN is set to "0".
- - - -
- EXCEPTION: Step 2 and 3 shall be repeated
for k=0 to 1(increment=1).
- - - -
2 The SS sends the PDCP Data PDU#k via
RLC-AM RB with the following content to the
UE:
D/C field =1 (PDCP Data PDU) and PDCP
SN =k.
After having sent a PDU, the SS set
Next_PDCP_TX_SN=k+1.
<-- PDCP PDU DATA #k - -
3 The UE sends the PDCP Data PDU#k via
UE:
SN =k.
Data is previously received data from PDU #k.
(Note 1)
--> PDCP PDU DATA #k - -
4 Configure SS not to allocate UL grant to the
UE in Cell 1.
- - - -
- EXCEPTION: Step 5 shall be repeated for
m=2 to 4 (increment=1).
- -
5 The SS sends the PDCP Data PDU #m via
UE:
D/C field =1 (PDCP Data PDU) and PDCP SN
=m.
Next_PDCP_TX_SN =m+1.
<-- PDCP PDU DATA #m - -
5A The SS changes Cell 2 parameters according
to the row "T1" in table 7.3.5.2.3.2.0-1.
- - - -
5B Configure SS to allocate Default UL grant to
the UE in Cell 2
Note: These grants will be requested by the
UE to send data after the handover
- - - -
6 The SS requests UE to make a handover to
Cell2 with the RRCConnectionReconfiguration
message sent on Cell 1.
7 SS assigns UL grant during the Random
Access procedure to allow the UE to send only
message.
- - - -
8 The UE on Cell 2 transmits a
message.
--> RRCConnectionReconfigurationC
omplete
- -
8A The UE send PDCP Control PDUs via RLC-
AM RB with the following content to the SS:
D/C field =0 (PDCP control PDU) and PDU
Type =000, FMS field =5.
--> PDCP STATUS REPORT - -
8B The SS generates a PDCP status report
message and sends it to UE: D/C field =0
(PDCP control PDU) and PDU Type =000,
FMS field =2.
<-- PDCP STATUS REPORT - -
EXCEPTION: Step 9 shall be repeated for
m=2 to 4 (increment=1).
- - - -
9 Check: Does the UE send the PDCP Data
PDU #m via RLC-AM RB with the following
content to the SS:
=m?
Data is previously received data from PDU #m.
(Note 2).
--> PDCP PDU DATA #m 1 P
Note 1: The SS acknowledges the received data.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 616
616

c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityControlInfo
-HO

Cell 2

}
}
}
}
}

7.3.5.3 PDCP handover / Non-lossless handover PDCP sequence number
maintenance
(1)
with {UE in E-UTRA RRC_CONNECTED state with bearer using RLC-UM}
ensure that {
when {UE is requested to make a non-lossless handover by SS}
then {UE transmits next PDCP Data PDU with SN value 0 }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.2.1.2.
[TS 36.323, clause 5.2.1.2]
When upper layers request a PDCP re-establishment, the UE shall:
- reset the header compression protocol for uplink (if configured);
- set Next_PDCP_TX_SN, and TX_HFN to 0;
- apply the ciphering algorithm and key provided by upper layers during the re-establishment procedure;
- for each PDCP SDU already associated with a PDCP SN but for which a corresponding PDU has not
previously been submitted to lower layers:
- consider the PDCP SDUs as received from upper layer;
- perform transmission of the PDCP SDUs in ascending order of the COUNT value associated to the PDCP SDU
prior to the PDCP re-establishment, as specified in the subclause 5.1.1 without restarting the discard-Timer.
System Simulator:
- Cell 1 and Cell 2
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 617
617
UE:
None.
Preamble:
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 618
618
U - S Message
- - - -
EXCEPTION: Step 2 and 3 shall be repeated
for k=0 to 1 (increment=1).

2 The SS sends the PDCP Data PDU #k via
RLC-UM RB with the following content to the
UE:
SN =k.
<-- PDCP PDU DATA #k - -
3 The UE sends the PDCP Data PDU #k via
SS:
SN =k.
Data is previously received data PDU #k.
--> PDCP PDU DATA #k
- - - -
the UE in Cell 2
- - - -
Cell 2 with the RRCConnectionReconfiguration
message.
<-- RRCConnectionReconfiguration
4A SS assigns UL grant during the Random
message.
- - - -
message.
omplete
-
6 The SS sends the PDCP Data PDU #2 via
UE:
SN =2.
<-- PDCP PDU DATA #2
7 Check: Does the UE send the PDCP Data
PDU #2 via RLC-UM RB with the following
content back to the SS:
=0.
Data is previously received data PDU #2.
--> PDCP PDU DATA #2 1 P

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 619
619
Table 7.3.5.3.3-1: RRCConnectionReconfiguration (step 4, 7.3.5.3.3.2-1)
c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityControlInfo
-HO

Cell 2

}
}
}
}
}

7.3.5.4 PDCP handover / Lossless handover / PDCP status report to convey the
information on missing or acknowledged PDCP SDUs at handover
(1)
with { UE in E-UTRA RRC_CONNECTED state with default RB used RLC-AM mode }
ensure that {
when { UE is requested to make a handover by SS }
then { UE creats a PDCP status report to SS}}
(2)
with { UE in E-UTRA RRC_CONNECTED state with default RB used RLC-AM mode }
ensure that {
then { UE discards the corresponding PDCP PDU and PDCP SDU according to the PDCP satus report
from SS }}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.3 and
5.4
[TS 36.323, clause 5.3.1]
When upper layers request a PDCP re-establishment, for radio bearers that are mapped on RLC AM, the UE shall:
- if the radio bearer is configured by upper layers to send a PDCP status report in the uplink, compile a status
report as indicated below after processing the PDCP Data PDUs that are received from lower layers due to the
re-establishment of the lower layers as specified in the subclause 5.2.2.1, and submit it to lower layers as the first
PDCP PDU for the transmission, by:
- setting the FMS field to the PDCP SN of the first missing PDCP SDU;
- if there is at least one out-of-sequence PDCP SDU stored, allocating a Bitmap field of length in bits equal to
the number of PDCP SNs from and not including the first missing PDCP SDU up to and including the last
out-of-sequence PDCP SDUs, rounded up to the next multiple of 8;
- setting as 0 in the corresponding position in the bitmap field for all PDCP SDUs that have not been
received as indicated by lower layers, and optionally PDCP SDUs for which decompression have failed;
- indicating in the bitmap field as 1 for all other PDCP SDUs.
[TS 36.323, clause 5.3.2]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 620
620
When a PDCP status report is received in the downlink, for radio bearers that are mapped on RLC AM:
- for each PDCP SDU, if any, with the bit in the bitmap set to '1', or with the associated COUNT value less than
the COUNT value of the PDCP SDU identified by the FMS field, the successful delivery of the corresponding
PDCP SDU is confirmed, and the UE shall process the PDCP SDU as specified in the subclause 5.4.
[TS 36.323, clause 5.4]
When the Discard_Timer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP
status report, the UE shall discard the PDCP SDU along with the corresponding PDCP PDU. If the corresponding
PDCP PDU has already been submitted to lower layers the discard is indicated to lower layers.
TC is applicable to:
- All UEs supporting E-UTRA.
System Simulator:
- Cell 1 and Cell 2
- ROHC is not used for headerCompression settings.
UE:
- UE in UE Loopback Activated test state (state 4) with default RB using RLC-AM in Cell 1.
Table 7.3.5.4.3.2-1: Time instances of cell power level
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 621
621
U - S Message
1 Next_PDCP_TX_SN is set to "0". The SS
creates 4 PDCP Data PDUs.
- - -
UE:
=0.
The SS sets Next_PDCP_TX_SN =1.
<-- PDCP DATA PDU #0 - -
3 The UE sends a PDCP Data PDU #0 via RLC-
AM RB with the following content back to the
SS:
SN =0
data: previously received packet.

(Note 1)
--> PDCP DATA PDU #0 - -
4 The SS is configured on Cell 1 not to send
RLC acknowledgements (RLC ACK s) to the
UE.

UE:
=1.
The SS set Next_PDCP_TX_SN =2.
<-- PDCP DATA PDU#1
6 The UE sends a PDCP Data PDU #1 via RLC-
SS:
SN =1
--> PDCP DATA PDU#1
- - - -
the UE in Cell 2 (Note 2).
- - - -
Cell2 with the RRCConnectionReconfiguration
message sent on Cell1.
message.
- -
message.
- - - -
message on Cell2.
omplete message.
- -
9 Check: Does the UE send PDCP Control
PDUs via RLC-AM RB with the following
content to the SS: D/C field =0 (PDCP control
PDU) and PDU Type =000, FMS field =2.
--> PDCP status report 1 P
10 The SS generates a PDCP status report
FMS field =2.
<-- PDCP status report - -
10
A
Configure SS to allocate Default UL grant to
the UE in Cell 2
- - - -
EXCEPTION: Step 11 shall be repeated for
k=2 to 3 (increment=1).

11 The SS sends the PDCP Data PDU #k via
UE:
=k.
<-- PDCP DATA PDU #k - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 622
622
Next_PDCP_TX_SN =k +1.
12 Check:Does the UE send a PDCP Data
PDU#2 via RLC-AM RB with the following
SN =2
--> PDCP DATA PDU #2 2 P
13 Check:Does the UE send a PDCP Data
PDU#3 via RLC-AM RB with the following
=3
Note 1: The SS sends RLC ACK to the UE
Note 2: SS transmit an UL grant of 72 bits (ITBS=2, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit
only PDCP Status report.

Table 7.3.5.4.3.3-1: RRCConnectionReconfiguration (Step 7, table 7.3.5.4.3.2-2)
c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityControlInf
o-HO

Cell 2

carrierFreq CarrierFreq of Cell 2
}
RadioResourceConfigDedicated-HO {
drb-ToAddModifyList {
PDCP-Configuration-DRB-AM {
discardTimer infinity
rlc-AM SEQUENCE {
statusReportRequired TRUE
}
}
}
}
}
}
}
}

7.3.5.5 PDCP handover / In-order delivery and duplicate elimination in the downlink
(1)
with { UE in E-UTRA RRC_CONNECTED state with default RB using RLC-AM }
ensure that {
then { UE achieves in-order delivery and duplicate elimination in the downlink }
}

5.1.2.1.2.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 623
623
[TS 36.323, clause 5.1.2.1.2]
For DRBs mapped on RLC AM, at reception of a PDCP Data PDU from lower layers, the UE shall:
- if received PDCP SN Last_Submitted_PDCP_RX_SN >Reordering_Window or 0 <=
Last_Submitted_PDCP_RX_SN received PDCP SN <Reordering_Window:
- if received PDCP SN >Next_PDCP_RX_SN:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN - 1 and the
received PDCP SN;
- else:
- decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN and the
received PDCP SN;
- perform header decompression (if configured) as specified in the subclause 5.5.5;
- else if Next_PDCP_RX_SN received PDCP SN >Reordering_Window:
- else if received PDCP SN Next_PDCP_RX_SN >=Reordering_Window:
- use COUNT based on RX_HFN 1 and the received PDCP SN for deciphering the PDCP PDU;
- else if received PDCP SN >=Next_PDCP_RX_SN:
- if Next_PDCP_RX_SN is larger than Maximum_PDCP_SN:
- else if received PDCP SN <Next_PDCP_RX_SN:
- if the PDCP PDU has not been discarded in the above:
- perform deciphering and header decompression (if configured) for the PDCP PDU as specified in the
subclauses 5.6 and 5.5.5, respectively;
- if a PDCP SDU with the same PDCP SN is stored:
- else:
- store the PDCP SDU;
- if the PDCP PDU received by PDCP is not due to the re-establishment of lower layers:
- all stored PDCP SDU(s) with an associated COUNT value less than the COUNT value associated
with the received PDCP SDU;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 624
624
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT
value associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers;
- else if received PDCP SN =Last_Submitted_PDCP_RX_SN +1 or received PDCP SN =
Last_Submitted_PDCP_RX_SN Maximum_PDCP_SN:
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT
value associated with the received PDCP SDU;
- set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers.
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 625
625
U - S Message
1 The Next PDCP_TX_SN is set to 0. The SS
creates a PDCP Data PDU#0.
- - - -
2 The SS sends the PDCP Data PDU#0 via
UE:
PDCP Data PDU #0 (
SN=0 )

(Note 1)

<-- PDCP DATA PDU#0 - -
3 The UE transmits a PDCP Data PDU via RLC-
SS
SN=0
data: previously received packet in PDCP Data
PDU#0

(Note 2)

--> PDCP DATA PDU #0 - -
4 Next_PDCP_TX_SN is set to 1.

The SS creates a PDCP Data PDU#1 (not
transmitted).
- - - -
5 The Next_PDCP_TX_SN is set to 2. The SS
creates a PDCP Data PDU #2.
- - - -
UE:
PDCP Data PDU#1;
SN=2

(Note 3)
7 Check: Does the UE transmit a PDCP DATA
PDU#2?
--> PDCP DATA PDU#2 1 F
- - - -
the UE in Cell 2 (Note 6).
- - - -
Cell 2 with the RRCConnectionReconfiguration
message.
<--- RRCConnectionReconfiguration - -
message.
- - - -
message in the new cell.
omplete
- -
9A The UE send PDCP Control PDUs via RLC-
AM RB with the following content to the SS:
D/C field =0 (PDCP control PDU) and PDU
Type =000, FMS field =1, Bitmap =0x80.
--> PDCP STATUS REPORT - -
9B The SS generates a PDCP status report
FMS field =1.
<-- PDCP STATUS REPORT - -
9C Configure SS to allocate Default UL grant to
the UE in Cell 2
- - - -
10 The SS sends the PDCP Data PDU#0 via <-- PDCP DATA PDU #0 - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 626
626
UE:
PDCP Data PDU #0(
SN=0)

(Note 4)
11 Check: Does the UE transmit PDCP Data PDU
via RLC-AM RB with the following content
back to the SS?
SN=0
PDU #0
--> PDCP DATA PDU #0 1 F
UE:
PDCP Data PDU#1 (
SN=1)

(Note 5)

13 Check: Does the UE transmit a PDCP Data
PDU via RLC-AM RB with the following
content back to the SS?
SN=1
PDU#1
14 Check: Does the UE transmit PDCP Data PDU
via RLC-AM RB with the following content
back to the SS?
SN=2
PDU#2
Note 1: PDCP Data PDU#0 is sent in RLC PDU#0: SN=0.
Note 2: The SS sends RLC ACK to the UE
Note 3: PDCP Data PDU #2 is sent in RLC PDU#2: SN=2
Note 4: PDCP Data PDU #0 is sent in RLC PDU#1: SN=1
Note 5: PDCP Data PDU #1 is sent in RLC PDU #2:SN =2
Note 6: SS transmit an UL grant of 72 bits (ITBS=2, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit
only PDCP Status report.

Table 7.3.5.5.3.3-1: RRCConnectionReconfiguration (Step 4, Table 7.3.5.5.3.2-1)
c1 CHOICE{
mobilityControlInfo SEQUENCE { MobilityContr
olInfo-HO

targetPhysCellId PhysicalCellIdentity
of Cell 2

}
radioResourceConfigDedicated {
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 627
627
7.3.6 PDCP Others
7.3.6.1 PDCP Discard
(1)
ensure that {
when { the Discard Timer for a PDCP SDU expires }
then { UE discards the corresponding PDCP SDU }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.9.
[TS 36.323, clause 5.4]
When the Discard_Timer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP
status report, the UE shall discard the PDCP SDU along with the corresponding PDCP PDU. If the corresponding
PDCP PDU has already been submitted to lower layers the discard is indicated to lower layers.
System Simulator:
- Cell 1
UE:
None.
Preamble
- The UE is in state Loopback Activated (state 4) according to [18 with the exceptions listed in table 7.3.6.1.3.1-1
applicable for the configured UM DRB and table 7.3.6.1.3.1-2 for SR configuration.
Table 7.3.6.1.3.1-1: PDCP Settings
Parameter Value
Discard_Timer 500ms

Table 7.3.6.1.3.1-2: SchedulingRequest-Config (preamble Table 4.5.3.3-1: Step8)
dsr-TransMax n64

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 628
628
U - S Message
- - -
2 The SS ignores scheduling requests and does not
allocate any uplink grant.
- - - -
EXCEPTION: Step 3 shall be repeated for k=0 to 2
(increment=1).

3 The SS sends a PDCP Data PDU via RLC-UM RB
with the following content to the UE:
D/C field =1 (PDCP Data PDU) and PDCP SN =k
After having sent a PDU, the SS sets
Next_PDCP_TX_SN =k+1.
<-- PDCP DATA PDU (SN=k) - -
4 Wait for Discard_Timer

Note: According to TS36.508, timer tolerance
should be 10% of Discard_Timer or 5 x RTT,
whichever is greater. RTT =8 TTIs for FDD and
RTT =16 TTIs for TDD
- - - -
EXCEPTION: Step 5 shall be repeated for k=3 to 4
(increment=1).

5 The SS sends a PDCP Data PDU via RLC-UM RB
with the following content to the UE:
D/C field =1 (PDCP Data PDU) and PDCP SN =k
Next_PDCP_TX_SN =k+1.
<-- PDCP DATA PDU (SN=k) - -
6 The SS resumes normal UL grant allocation. - - -
7 Check: Does UE transmit a PDCP Data PDU with
PDCP SN =3?
8 Check: Does UE transmit a PDCP Data PDU with
PDCP SN =4?

None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 629
629
8 RRC
8.1 RRC connection management procedures
8.1.1 Paging
8.1.1.1 RRC / Paging for connection in idle mode
(1)
ensure that {
when { UE receives a Paging message including an ue-Identity set an unmatched S-TMSI i.e. other
than the one allocated to the UE at the UE registration procedure }
then { UE does not establish an RRC connection }
}

(2)
ensure that {
when { UE receives a Paging message including an ue-Identity set to the S-TMSI which was allocated
to the UE at the UE registration procedure }
then { UE establishes an RRC connection }
}
5.3.3.2, 5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.2.3]
Upon receiving the Paging message, the UE shall:
1>if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:
2>if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:
3>forward the ue-Identity, and the cn-Domain to the upper layers.
...
[TS 36.331, clause 5.3.3.2]
The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in
RRC_IDLE.
Upon initiation of the procedure, the UE shall:
...
1>if access to the cell, as specified above, is not barred:
2>apply the default physical channel configuration as specified in 9.2.4;
2>apply the default semi-persistent scheduling configuration as specified in 9.2.3;
2>apply the default MAC main configuration as specified in 9.2.2;
2>apply the CCCH configuration as specified in 9.1.1.2;
2>apply the timeAlignmentTimerCommon included in SystemInfoBlockType2;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 630
630
2>start timer T300;
2>initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;
NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up
to date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to
perform system information acquisition upon cell re-selection.
...
[TS 36.331, clause 5.3.3.3]
The UE shall set the contents of RRCConnectionRequest message as follows:
1>set the ue-Identity as follows:
2>if upper layers provide an S-TMSI:
3>set the ue-Identity to the value received from upper layers;
2>else:
3>draw a random value in the range 0 .. 2
40
-1 and set the ue-Identity to this value;
NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.
1>set the establishmentCause in accordance with the information received from upper layers;
The UE shall submit the RRCConnectionRequest message to lower layers for transmission.
The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for
cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.
[TS 36.331, clause 5.3.3.4]
NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];
The UE shall:
1>stop timer T300;
2> if upper layers provide the Registered MME, include and set the registeredMME as follows:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 631
631
3>if the PLMN identity of the Registered MME is different from the PLMN selected by the upper layers:
4>include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the
Registered MME received from upper layers;
3>set the mmegi and the mmec to the value received from upper layers;
2>set the dedicatedInfoNAS to include the information received from upper layers;
procedure ends.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
U - S Message
an unmatched identity (incorrect S-TMSI).
<-- Paging - -
RRCConnectionRequest message within 5 s?
a matched identity.
<-- Paging - -
RRCConnectionRequest message?
message.
including SERVICE REQUEST to confirm the
successful completion of the connection
establishment?
6A-
6D
- - - -
- - 1, 2 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 632
632
pagingRecordList SEQUENCE (SIZE
(1..maxPageRec)) OF SEQUENCE {
1 entry
ue-Identity[1] CHOICE {
s-TMSI SEQUENCE {
mmec Set to the different value
from the S-TMSI of the
UE

m-TMSI Set to the different value
UE

}
}
}
}

RRCConnectionRequest ::=SEQUENCE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause mt-Access
}
}
}

8.1.1.2 RRC / Paging for notification of BCCH modification in idle mode
(1)
ensure that {
when { UE receives a Paging message including a systemInfoModification }
then { UE re-acquires and applies the new system information about the correct prach-ConfigIndex
in random access }
}

5.2.2.3, and 5.2.2.4.
[TS 36.331, clause 5.3.2.3]
1>if in RRC_IDLE, for each of the PagingRecord, if any included in the Paging message:
3>forward the ue-Identity and the cn-Domain to the upper layers;
1>if the systemInfoModification is included:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 633
633
2>re-acquire the required system information using the system information acquisition procedure as specified in
5.2.2.
...
[TS 36.331, clause 5.2.2.3]
The UE shall:
1>ensure having a valid version, as defined below, of (at least) the following system information, also referred to as
the 'required' system information:
2>if in RRC_IDLE:
3>the MasterInformationBlock and SystemInformationBlockType1 as well as SystemInformationBlockType2
through SystemInformationBlockType8, depending on support of the concerned RATs;
...
[TS 36.331, clause 5.2.2.4]
The UE shall:
1>apply the specified BCCH configuration defined in 9.1.1.1;
1>if the procedure is triggered by a system information change notification:
2>start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification
period following the one in which the change notification was received;
...
The UE may apply the received SIBs immediately, i.e. the UE does not need to delay using a SIB until all SI messages
have been received. The UE may delay applying the received SIBs until completing lower layer procedures associated
with a received or a UE originated RRC message, e.g. an ongoing random access procedure.
NOTE 3: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer
present, the UE should stop trying to acquire the particular SIB.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 634
634
U - S Message
a matched identity.
<-- Paging - -
message.
3A The UE transmits an
message.
3B The SS transmits a SecurityModeCommand
message.
3C The UE transmits a SecurityModeComplete
message.
3D The SS transmits an
RRCConnectionReconfiguration message.
3E The UE transmits an
message.
omplete
- -
3F The SS transmits an RRCConnectionRelease
message.
3G Wait for 5 s for the UE to enter E-UTRA
RRC_IDLE state.
- - - -
4 The SS changes the prach-ConfigIndex in the
system information
- - - -
a systemInfoModification.
<-- Paging - -
6 Wait for 15s for the UE to receive system
information.
- - - -
a matched identity.
<-- Paging - -
7A Check: Does the UE re-transmit a random
access using prach-ConfigIndex given in step
4?
- - 1 P
8 The UE transmit an RRCConnectionRequest
message.
message.
message.
message.
message.
message.
omplete
- -
message.
RRC_IDLE state.
- - - -
indicate that the UE is in E-UTRA RRC_IDLE
state on Cell 1?
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 635
635
Table 8.1.1.2.3.3-1: RRCConnectionRequest (step 2 and step 8, Table 8.1.1.2.3.2-1)
}
}
}

Table 8.1.1.2.3.3-2A: RRCConnectionReconfiguration (step 3D and step 9D, Table 8.1.1.2.3.2-1)
Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(1, 0)

}

Table 8.1.1.2.3.3-2A: SystemInformationBlockType1 (step 6, table 8.1.1.2.3.2-1)
systemInfoValueTag 1 Default value is 0
}

Table 8.1.1.2.3.3-3: SystemInformationBlockType2 (step 6, Table 8.1.1.2.3.2-1)
prach-ConfigIndex 5 FDD
prach-ConfigIndex FFS Set to index which
denote subframe
numbers different
from the default
one.
TDD
}
}
}
}

FDD FDD cell environment
TDD TDD cell environment

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 636
636
8.1.1.3 RRC / Paging for connection in idle mode / Multiple paging records
(1)
ensure that {
when { UE receives a Paging message including only unmatched identities }
then { UE does not establish any RRC connection }
}
(2)
ensure that {
when { UE receives a Paging message including any matched indentity }
}
5.3.3.2, 5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.2.3]
Upon receiving the Paging message, the UE shall
1>If in RRC_IDLE, for each of the Paging records included in the Paging message:
2>If the ue-identity included in the pagingRecordList matches one of the UE identities allocated by upper
layers:
3>forward the ue-Identity, the cn-Domain and the pagingCause to the upper layers.
...
[TS 36.331, clause 5.3.3.2]
RRC_IDLE state.
...
1>If access to the cell, as specified above, is not barred:
2>apply the default configuration applicable for the antennaInformation as specified in 9.2.3, until explicitly
receiving a configuration;
2>start timer T300;
perform system information acquisition upon re-selection.
...
[TS 36.331, clause 5.3.3.3]
1>set the IE ue-Identity as follows:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 637
637
2>else
3>draw a random value and set the ue-Identity to this value;
NOTE 1 Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.
1>Set the establishmentCause in accordance with the information received from upper layers;
[TS 36.331, clause 5.3.3.4]
NOTE: Prior to this, lower layers allocate a C-RNTI. For further details see TS 36.321 [6];
The UE shall:
1>establish SRB1 in accordance with the received radioResourceConfiguration and as specified in 5.3.10;
1>if stored, discard the Inter-frequency priority information and the Inter-RAT priority information provided via
dedicated signalling using the IE idleModeMobilityControlInfo;
1>stop timer T300;
1>enter RRC_CONNECTED state;
2>set the selectedPLMN-Identity to the PLMN selected by upper layers [TS 23.122, TS 24.008] from the
PLMN(s) included in the plmn-IdentityList broadcast, within SystemInformationBlockType1, in the cell
where the RRC connection was established;
2> if upper layers provide the Registered MME, set the registeredMME as follows:
3>if the PLMN identity of the Registered MME is different from the PLMN selected by the upper layers,
set the IE plmnIdentity to the value received from upper layers;
3>set the IEs mmegi and mmec to the value received from upper layers;
2>set the nas-DedicatedInformation to include the information received from upper layers;
procedure ends.
System Simulator:
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 638
638
UE:
None.
Preamble:
U - S Message
only unmatched identities (incorrect S-TMSI).
<-- Paging 1 -
RRCConnectionRequest message within 10s?
two unmatched identities and a matched
identity.
<-- Paging 2 -
message.
including SERVICE REQUEST to confirm the
establishment.
6A-
6D
establishment procedure in TS 36.508
subclause 4.5.3.3 are executed to successfully
complete the service request procedure.
- - - -
- - 1,2 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 639
639
3 entries
s-TMSI Set to the different value
UE

}
cn-Domain [1] ps
UE

}
cn-Domain [2] ps
UE

}
cn-Domain [3] ps
}
}

3 entries
UE

}
cn-Domain [1] ps
UE

}
cn-Domain [2] ps
s-TMSI Set to the value of the S-
TMSI of the UE

}
cn-Domain [3] ps
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 640
640
}
}
}

8.1.1.4 RRC / Paging for connection in idle mode / Shared network environment
(1)
with { UE in E-UTRA RRC_IDLE state having been registered in the TA of the current cell which has
broadcasted a SystemInformationBlockType1 message including multiple PLMN identities }
ensure that {
when { UE receives a Paging message including an IE ue-Identity set to the S-TMSI which was
allocated to the UE at the UE registration procedure }
}

5.3.3.2, 5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.2.3]
1>if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:
3>forward the ue-Identity and the cn-Domain to the upper layers.
...
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
2>apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;
2>start timer T300
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 641
641
...
[TS 36.331, clause 5.3.3.3]
2>else
40
[TS 36.331, clause 5.3.3.4]
The UE shall:
1>stop timer T300;
3>if the PLMN identity of the 'Registered MME' is different from the PLMN selected by the upper layers;
'Registered MME' received from upper layers;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 642
642
procedure ends.
System Simulator:
- Cell 1
UE:
None.
Preamble:
U - S Message
a matched identity.
<-- Paging - -
3 The SS transmit an RRCConnectionSetup
message.
including SERVICE REQUEST and an IE
selectedPLMN-Identity corresponding to the
PLMN on which the UE has been registered to
connection establishment?
4A-
4D
- - - -
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 643
643
Table 8.1.1.4.3.3-1: SystemInformationBlockType1 (all steps, Table 8.1.1.4.3.2-1)
SEQUENCE {
2 entries
plmn-Identity[1] SEQUENCE {
mcc See Table 8.1.1.4.3.3-1A
mnc See Table 8.1.1.4.3.3-1A
}
cellReservedForOperatorUse[1] notReserved
mcc See Table 8.1.1.4.3.3-1A
mnc See Table 8.1.1.4.3.3-1A
}
}
}
}

The PLMN Identity list broadcasted on the BCCH in Cell 1 shall be configured as defined in the table below.
Table 8.1.1.4.3.3-1A: PLMN Identity List broadcasted for Cell 1
Cell PLMN Identity (1) PLMN Identity (2)
MCC digits MNC digits MCC digits MNC digits
1 PLMN 1 PLMN 1 PLMN 2 PLMN 2

The definition of each PLMN code is found in table below.
PLMN MCC digit MNC digit
1 2 3 1 2 3
1 (NOTE 2) (NOTE 2)
2 (NOTE 3) 0 2 -

NOTE 1: (dash) denotes not present
NOTE 2: Set to the same Mobile Country Code and Mobile Network Code stored in EF
IMSI
on the test USIM card
for PLMN 1.
NOTE 3: Set to the same Mobile Country Code stored in EF
IMSI
on the test USIM card for PLMN 2.
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 644
644
c1 CHOICE{
selectedPLMN-Identity Set to the PLMN selected
by upper layers

}
}
}
}

8.1.1.5 Void
8.1.1.6 RRC / BCCH modification in connected mode
with { the UE is in E-UTRA RRC_CONNECTED }
ensure that {
when { the UE receives a Paging message including the systemInfoModification }
then { the UE re-acquires the MasterInformationBlock, SystemInformationBlockType1 and
SystemInformationBlockType2 }

References: The conformance requirements covered in the present test case are specified in: TS 36.331 clauses 5.3.2.3,
5.2.2.3 and 5.2.2.4.
[TS 36.331, clause 5.3.2.3]
...
1>if the systemInfoModification is included:
2>re-acquire the required system information using the system information acquisition procedure as specified in
5.2.2.
...
[TS 36.331, clause 5.2.2.3]
The UE shall:
1>ensure having a valid version, as defined below, of (at least) the following system information, also referred to as
the 'required' system information:
...
2>if in RRC_CONNECTED:
3>the MasterInformationBlock, SystemInformationBlockType1 and SystemInformationBlockType2 as well as
SystemInformationBlockType8, depending on support of CDMA2000;
...
[TS 36.331, clause 5.2.2.4]
The UE shall:
1>apply the specified BCCH configuration defined in 9.1.1.1;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 645
645
1>if the procedure is triggered by a system information change notification:
2>start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification
period following the one in which the change notification was received;
NOTE 1: The UE continues using the previously received system information until the new system information has
been acquired.
...
The UE may apply the received SIBs immediately, i.e. the UE does not need to delay using a SIB until all SI messages
have been received. The UE may delay applying the received SIBs until completing lower layer procedures associated
with a received or a UE originated RRC message, e.g. an ongoing random access procedure.
NOTE 2: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer
present, the UE should stop trying to acquire the particular SIB.
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18], and using the condition
no_periodic_BSR_or_PHR.
U - S Message
1 The SS transmits a Paging message paging
occasion including a systemInfoModification.
<-- Paging - -
2 From the begining of the next modification
period the SS transmits a modified
SystemInformationBlockType1 and
SystemInformationBlockType2 as specified.
- - - -
3 During the first on duration period after the end
of the modification period where
SystemInformationBlockType2 was modified
(see step 2), the SS transmits a PDCCH order
including a dedicated preamble.
- - - -
4 Check: Does the UE initiate a random access
procedure using prach-ConfigIndex given in
step 2 (i.e. in subframe number 7 and not 1)?
- - 1 P
with RAPID corresponding to preamble in
steps 3 and 4.
- - - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 646
646
Table 8.1.1.6.3.3-1: RRCConnectionReconfiguration (preamble, step 8, TS 36.508 table
8.1.1.6.34.5.3.3-1)
c1 CHOICE {
rrcConnectionReconfiguration-r8 {
radioResourceConfigDedicated {
mac-MainConfig {
explicitValue {
Drx-Config Not present
}
}
}
}
}
}
}

Table 8.1.1.6.3.3-2: SystemInformationBlockType1 (step 2, table 8.1.1.6.3.2-1)
systemInfoValueTag 1 Default value is 0
}

Table 8.1.1.6.3.3-3: SystemInformationBlockType2 (step 2, table 8.1.1.6.3.2-1)
prach-ConfigIndex 5 The default is 3 FDD
prach-ConfigIndex 53 The default is 51 TDD
}
}
}
}

8.1.2 RRC connection establishment
8.1.2.1 RRC connection establishment / Ks=1.25/ Success
(1)
with {UE in E-UTRA RRC_IDLE state}
ensure that {
when { UE is requested to make an outgoing call }
then { UE establishes an RRC Connection }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 647
647
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.3.2,
5.3.3.3 and 5.3.3.4.
[TS 36.331, clause 5.3.3.2]
The UE initiates the procedure when upper layers request establishment of a signalling connection while the UE is in
RRC_IDLE state.
...
2>start timer T300;
NOTE 2 Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up
...
[TS 36.331, clause 5.3.3.3]
2>else
40
...
[TS 36.331, clause 5.3.3.4]
...
The UE shall:
1>perform the radio resource configuration procedure in accordance with the received radioResourceConfiguration
and as specified in 5.3.10;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 648
648
1>stop timer T300;
1>set the contents of RRCConnectionSetupComplete message as follows:
from the PLMNs included in the plmn-IdentityList in SystemInformationBlockType1;
3>set the mmegi and mmec to the value received from upper layers;
2>set the nas-DedicatedInformation to include the information received from upper layers;
procedure ends.
System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 649
649
U - S Message
1 SS sends a Paging message to the UE on the
identity in one entry of the IE
pagingRecordLists.
<-- Paging - -
message with SRB1 configuration (Note 1).
<--
RRCConnectionSetupComplete including
SERVICE REQUEST message to confirm the
establishment?
4A-
4D
- - - -
- - 1 -
Note 1: Contains a SERVICE REQUEST NAS message.

Table 8.1.2.1.3.3-1: RRCConnectionSetup-DeltaMCS (step 3, Table 8.1.2.1.3-1)
RRCConnectionSetup-DeltaMCS ::=SEQUENCE {
c1 CHOICE {
rrcConnectionSetup-r8 SEQUENCE {
dicated-SRB1-DeltaMCS

}
}
}
}
Table 8.1.2.1.3.3-2: RadioResourceConfigDedicated-SRB1-DeltaMCS (Table 8.1.2.1.3.3-1)
Derivation Path: 36.508, Table 4.6.3-15,
RadioResourceConfigDedicated-SRB1-DeltaMCS ::=
SEQUENCE {

physicalConfigDedicated PhysicalConfigDedicated
--DeltaMCS using
condition SRB1

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 650
650
Table 8.1.2.1.3.3-3: PhysicalConfigDedicatedDeltaMCS (Table 8.1.2.1.3.3-2)
Derivation Path: 36.508, Table 4.8.2.1.6-1
PhysicalConfigDedicated--DeltaMCS ::=SEQUENCE
{

uplinkPowerControlDedicated UplinkPowerControlDedic
ated--DeltaMCS
SRB1
}

Table 8.1.2.1.3.3-4: UplinkPowerControlDedicated--DeltaMCS (Table 8.1.2.1.3.3-3)
UplinkPowerControlDedicated--DeltaMCS ::=
SEQUENCE {

deltaMCS-Enabled en1 Corresponds to
Ks value 1.25
corresponding to
enabled.

}

8.1.2.2 RRC connection establishment / Reject with wait time
(1)
with { UE in E-UTRA RRC_IDLE state and has sent an RRCConnectionRequest message }
ensure that {
when { UE receives an RRCConnectionReject message including an IE waitTime set to non-zero value }
then { UE doesn't re-send RRCConnectionRequest before the waitTime is expired}
}

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.3.2,
5.3.3.3 and 5.3.3.8.
[TS 36.331, clause 5.3.3.2]

1> if the UE is establishing the RRC connection for mobile terminating calls:
2> if timer T302 is running:
3>consider access to the cell as barred;
2> else:
3>consider access to the cell as not barred;
1>else if the UE is establishing the RRC connection for emergency calls:
...
1>else if the UE is establishing the RRC connection for mobile originating calls:
2>if timer T302 or T303 is running:
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 651
651
2>start timer T300;
...
[TS 36.331, clause 5.3.3.3]
2>else
40
...
[TS 36.331, clause 5.3.3.8]
The UE shall:
1>stop timer T300;
1>reset MAC and release the MAC configuration;
1>start timer T302, with the timer value set to the waitTime;
1>inform upper layers about the failure to establish the RRC connection and that access barring for mobile
originating calls, mobile originating signalling and mobile terminating access is applicable, upon which the
procedure ends.
System Simulator:
- Cell 1
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 652
652
Preamble:
- The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE
B on Cell 1 (serving cell) according to [18].8.1.2.2.3.2 Test procedure sequence
U - S Message
1 The SS transmits one IP packet to the UE on
the DRB associated with the default EPS
bearer context on Cell 1.
- - - -
1A Wait for 1 s after the IP packet has been
transmitted in step 1. (Note 3)

1B The SS transmits an RRCConnectionRelease
message on Cell 1.
<-- RRCConnectionRelease
1C The SS transmits a Paging message with a
matching UE identity.
<-- Paging
message.
3 The SS responds with RRCConnectionReject
message with IE waitTime set to 10s.
<-- RRCConnectionReject - -
- EXCEPTION: the behaviour in table
8.1.2.2.3.2-2 runs in parallel with steps 4 and 5
below.
- - - -
4 Void - - - -
5 The SS transmits a Paging message with a
matching UE identity.
<-- Paging - -
6 The SS starts timer Timer_1 =5 s (Note 1) - - - -
- EXCEPTION: Steps 7a1 to 7a9 describe a
transaction that depends on the UE behaviour;
the "lower case letter" identifies a step
sequence that takes place if a specific
behaviour happens.(Note 2)
- - - -
7a1 Check: Does UE transmit
RRCConnectionRequest message when the
Cell is treated as normal cell and access is
granted for originating call?
- RRCConnectionRequest 1 P
7a2
-
7a6
are executed.
- - - -
EXCEPTION: Step 7a7 and 7a8 can occur in
any order

7a7 The UE transmits an
message on Cell 1.
omplete

7a8 The UE loop backs the IP packet received in
step 1 on the DRB associated with the default
EPS bearer context on Cell 1.

7a9 Check: Does the test result of generic test
1
7b1 The SS waits for Timer_1 expiry - - - -
7b2 Check: Does the test result of generic test
state on Cell 1?
- - 1 -
Note 1: Test step 6 is always executed 10s after step 3, i.e. when the reject timer is expired in the UE and the UE
is allowed to answer paging and initiate calls again. This is because test steps 4 and 5 of the main
behaviour run in parallel with test step 1 of the parallel behaviour, which lasts 10s unless the verdict is
"Failed".
Note 2: A UE may send RRCConnectionRequest for the pending data sent at step 1.
Note 3: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted
by the SS in step 1 to the UE test loop function before the RRCConnectionRelease message is sent by the
SS in step 1B.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 653
653
U - S Message
RRCConnectionRequest message within 10s.

Table 8.1.2.2.3.3-1: RRCConnectionReject (step 3, table 8.1.2.2.3.2-1)
RRCConnectionReject ::=SEQUENCE {
c1 CHOICE {
rrcConnectionReject-r8 SEQUENCE {
waitTime 10 10 seconds
}
}
}
}

Table 8.1.2.2.3.3-2: CLOSE UE TEST LOOP (preamble, Table 8.1.2.2.3.2-1)
Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
UE test loop mode B LB setup
IP PDU delay '0000 0101'B 5 seconds

8.1.2.3 RRC connection establishment / Return to idle state after T300 timeout
(1)
with {UE in E-UTRA RRC_IDLE state having sent an RRCConnectionRequest message}
ensure that {
when { the SS does not answer to the UE during T300}
then {UE goes to RRC_IDLE}
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.3.6.
[TS 36.331, clause 5.3.3.6]
The UE shall:
1>if timer T300 expires
2>reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;
2>inform upper layers about the failure to establish the RRC connection, upon which the procedure ends.
System Simulator:
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 654
654
UE:
None.
Preamble:
U - S Message
1 Make the UE attempt an outgoing call - - - -
message.
3 The SS waits for 2s.

Note: the UE may transmit one or more
RRCConnectionRequest messages but the SS
does not answer to these messages.
state on Cell 1?
- - 1 -

None.
8.1.2.4 Void
8.1.2.5 RRC connection establishment / 0% access probability for MO calls, no
restriction for MO signalling
(1)
with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating 0%
access probability for MO calls }
ensure that {
when { UE has user data pending }
then { UE does not transmit any RRCConnectionRequest message }
}
(2)
ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts a
SystemInformationBlockType2 indicating no restriction for MO signalling }
then { UE transmits an RRCConnectionRequest message }
}

[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
1>if the UE is establishing the RRC connection for mobile terminating calls:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 655
655
...
...
2>else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:
3>if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which
is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and
3>for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in
ac-BarringForMO-Data is set to zero:
3>else:
4>draw a random number 'rand' uniformly distributed in the range: 0 rand <1;
4>if 'rand' is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-Data:
4>else:
2>else:
1>else (the UE is establishing the RRC connection for mobile originating signalling):
2>else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is
present:
ac-BarringForMO-Signalling is set to zero:
3>else:
4>if 'rand' is lower than the value indicated by ac-BarringFactor included in ac-BarringForMO-
Signalling:
4>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 656
656
2>else:
2>start timer T300;
1>else:
2>if the UE is establishing the RRC connection for mobile originating calls and if both timers T302 and T303
are not running:
3>draw a random number 'rand' that is uniformly distributed in the range 0 rand <1;
3>start timer T303 with the timer value calculated as follows, using the ac-BarringTime included in ac-
BarringForMO-Data:
T303=(0.7+0.6
*
rand)
*
ac-BarringTime
originating calls is applicable, upon which the procedure ends;
...
System Simulator:
- Cell 1 and Cell 11 (HPLMN in different TA).
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 (serving
cell) according to [18].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 657
657
T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 -79
assigned to satisfy RCell 1 <RCell
11.

U - S Message
1 Void - - - -
2 Void - - - -
2A The SS transmits an RRCConnectionRelease
message on Cell 1.
2B Wait for 5 s for the UE to enter E-UTRA
RRC_IDLE state.
- - - -
- - - -
3A Check: Does the UE transmit an
3B-
3F
TS 36.508 [18] subclause 6.4.2.7 are
Note: The UE performs a TAU procedure and
- - - -
4-9 Void - - - -
RRC_IDLE state.
- - - -
10
A
Generic test procedure in TS 36.508
NOTE: The UE performs the establishment of
the new data radio bearer associated with the
default EPS bearer context.
- - - -
10
B
The SS transmits one IP packet to the UE on
- - - -
10
C
Wait for 1 s after the IP packet has been
transmitted in step 10B. (Note 1)
- - - -
11-
13
Void - - - -
message on Cell 11.
within 30s?
16 Void - - - -
- EXCEPTION: Step 26 and Step 27a1 can
happen in any order
- - - -
17 -
26
Check: Does the test result of steps 1 to 10
generic test procedure in TS 36.508 subclause
6.4.2.2 indicate that the UE is in E-UTRA
RRC_IDLE state on Cell 11?
- - 1,2 -
- EXCEPTION: Step 27a1 describes behaviour
that depends on UE implementation; the
"lower case letter" identifies a step sequence
that takes place if the UE has user data
pending.
- - - -
27a
1
IF the UE has user data pending THEN the UE
loop backs the IP packet received in step 10C
on the DRB associated with the default EPS
bearer context on Cell 11 within 10s.
- - - -
by the SS in step 10B to the UE test loop function before the RRCConnectionRelease message is sent by
the SS in step 14.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 658
658
8.1.2.5.3.2-2)
ac-BarringInfo SEQUENCE {
ac-BarringForEmergency FALSE
ac-BarringForMO-Signalling Not present
ac-BarringForMO-Data SEQUENCE {
ac-BarringFactor p00
ac-BarringTime s512
ac-BarringForSpecialAC '11111'B
}
}
}

Table 8.1.2.5.3.3-1A: CLOSE UE TEST LOOP (preamble, Table 8.1.2.5.3.2-2)

Table 8.1.2.5.3.3-2: RRCConnectionRequest (step 3A, Table 8.1.2.5.3.2-2)
establishmentCause mo-Signalling
}
}
}

8.1.2.6 RRC connection establishment / Non-zero percent access probability for MO
calls, no restriction for MO signalling
(1)
with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating non zero
percent access probability for MO calls }
ensure that {
then { UE does not transmit any RRCConnectionRequest message or UE transmits an
RRCConnectionRequest message }
}

(2)
ensure that {
SystemInformationBlockType2 indicating no restriction for MO signalling }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 659
659
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
1> else if the UE is establishing the RRC connection for emergency calls:
...
1> else if the UE is establishing the RRC connection for mobile originating calls:
2> if timer T302 or T303 is running:
3> consider access to the cell as barred;
2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is
present:
3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15,
which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and
3> for at least one of these Access Classes the corresponding bit in the ac-BarringForSpecialAC contained
in ac-BarringForMO-Data is set to zero:
3> else:
5> consider access to the cell as not barred;
4>else:
2> else:
1> else (the UE is establishing the RRC connection for mobile originating signalling):
2> else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is
present:
...
2> else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 660
660
2>start timer T300;
1>else:
are not running:
BarringForMO-Data:
T303=(0.7+0.6
*
rand)
*
ac-BarringTime
2>else if the UE is establishing the RRC connection for mobile originating signalling and if both timers T302
and T305 are not running:
BarringForMO-Signalling:
T305=(0.7+0.6
*
rand)
*
ac-BarringTime
originating signalling is applicable, upon which the procedure ends;
System Simulator:
UE:
None.
Preamble:
T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 -79
Cell 1
<R
Cell 11
.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 661
661
U - S Message
1 The SS initializes an internal counter K to 0
and L to 0.
- - - -
- EXCEPTION: Steps 2 to 3b14 shall be
repeated maximum 50 times unless K >0 and
L >0. (Note 1)
- - - -
2 Cause the UE to request connectivity to an
additional PDN. (Note 2)
- - - -
- EXCEPTION: Steps 3a1 to 3b14 describe
behaviours which vary depending on whether
the UE transmits an RRCConnectionRequest
message or not.
- - - -
3a1 IF the UE does not transmit any
RRCConnectionRequest message within 5s
(Note 3) THEN the SS waits for 90 s to ensure
that T303 expires and increments the counter
K by 1.
- - - -
3b1 ELSE IF the UE transmits an
THEN the SS increments the counter L by 1.
3b2 Void - - - -
3b3-
3b10
Cell 1.
NOTE: The UE performs a SERVICE
REQUEST procedure.
- - - -
3b11 The UE transmits an ULInformationTransfer
message on Cell 1.
This message includes a PDN
CONNECTIVITY REQUEST message.
--> ULInformationTransfer - -
3b12 The SS transmits a DLInformationTransfer
message on Cell 1.
This message includes a PDN
CONNECTIVITY REJ ECT message.
<-- DLInformationTransfer - -
3b13 The SS transmits an RRCConnectionRelease
message on Cell 1.
3b14 Wait for 5 s for the UE to enter E-UTRA
RRC_IDLE state.
- - - -
4 Check: Is the counter K >0 and L >0? - - 1 P
- - - -
RRCConnectionRequest message on Cell 11?
Cell 11.
- - - -
state on Cell 11?
- - 1,2 -
Note 1: There is an extremely low probability that the UE originating calls are barred, or not barred, 50 times
consecutively. (The probability is 1.7810
-15
). Therefore, 50 times is enough number of trials for this test
case.
Note 2: The trigger in step 2 and the RRC messages in steps 3b1 to 3b9 are the same as in the generic procedure in
36.508 clause 6.4.3.2.
Note 3: The UE starts T303.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 662
662
Table 8.1.2.6.3.2-2)
ac-BarringForMO-Signalling Not present
ac-BarringTime s64
ac-BarringForSpecialAC 11111B
}
}
}

Table 8.1.2.6.3.3-2: RRCConnectionRequest (step 3b1, Table 8.1.2.6.3.2-2)
establishmentCause mo-Data
}
}
}

Table 8.1.2.6.3.3-3: PDN CONNECTIVITY REJECT (step 3b12, Table 8.1.2.6.3.2-2)
ESM cause '0010 0110'B Network failure

}
}
}

8.1.2.7 RRC connection establishment / 0% access probability for AC 0 to 9, AC 10
is barred, AC 11 to 15 are not barred, access for UE with access class in the
range 11 to 15 is allowed
(1)
with { UE in E-UTRA RRC_IDLE state having an Access Class with a value in the range 11..15 and
having received a SystemInformationBlockType2 indicating 0% access probability for AC 0..9 for both
MO call and MO signalling, access restriction for AC 10 and no restriction for AC 11..15 for both MO
call and MO signalling }
ensure that {
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 663
663
}

(2)
with { UE in E-UTRA RRC_IDLE state having an Access Class with a value in the range 11..15 }
ensure that {
SystemInformationBlockType2 indicating 0% access probability for AC 0..9 for both MO call and MO
signalling, access restriction for AC 10 and no restriction for AC 11..15 for both MO call and MO
signalling }
}

[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
1>if the UE is establishing the RRC connection for mobile terminating calls:
2>if timer T302 is running:
...
2>else:
...
...
2>else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Data is present:
ac-BarringForMO-Data is set to zero:
3>else:
...
1>else (the UE is establishing the RRC connection for mobile originating signalling):
...
2>else if SystemInformationBlockType2 includes the ac-BarringInfo and the ac-BarringForMO-Signalling is
present:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 664
664
3>else:
...
2>start timer T300;
...
System Simulator:
- Cell 1 and Cell 11 (HPLMN in different TA).
UE:
- USIM set to Type C in 34.108[5] subclause 8.3.2.15 is inserted.
Preamble:
- The UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on Cell 1 according
to [18].
T0
Cell-specific RS
EPRE
dBm/15
kHz
-85 -91
assigned to satisfy SrxlevCell 1 >
SrxlevCell 11.
T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 -79
assigned to satisfy RCell 1 <RCell
11.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 665
665
U - S Message
- - - -
0A Wait for 1 s after the IP packet has been
- - - -
message on Cell 1.
RRCConnectionRequest message on Cell 1?
message on Cell 1.
Cell 1.
message.
message on Cell 1.
message on Cell 1.
Cell 1.
- EXCEPTION: Step 3E and 3EA can occur in
any order
- - - -
message on Cell 1.
omplete
- -
3E
A
The UE loop backs the IP packet received in
step 0 on the DRB associated with the default
EPS bearer context on Cell 1.
- - - -
message on Cell 1.
RRC_IDLE state.
- - - -
- - - -
4A Check: Does the test result of generic test
Cell 11 and that the UE has performed TAU
procedure with establishment cause high
priority access?
- - 2 -
5-
10
Void - - - -
RRC_IDLE state.
- - - -
12-
20
Void - - - -
state on Cell 11 and that the UE has
performed TAU procedure with establishment
cause high priority access?
- - 1,2 -
Note 1: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by
the SS in step 0 to the UE test loop function before the RRCConnectionRelease message is sent by the SS
in step 1.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 666
666
Table 8.1.2.7.3.3-1: SystemInformationBlockType2 for Cell 1 and Cell 11 (preamble, Table 8.1.2.7.3.2-
2)
ac-BarringForEmergency TRUE
ac-BarringForMO-Signalling SEQUENCE {
ac-BarringTime s4
}
ac-BarringTime s4
}
}
}

Table 8.1.2.7.3.3-1A: CLOSE UE TEST LOOP (preamble, Table 8.1.2.7.3.2-2)

Table 8.1.2.7.3.3-2: RRCConnectionRequest (step 2, step 4A and step 21, Table 8.1.2.7.3.2-2)
establishmentCause highPriorityAccess
}
}
}

Table 8.1.2.7.3.3-3: Void
Table 8.1.2.7.3.3-4: Void
Table 8.1.2.7.3.3-5: Void
Table 8.1.2.7.3.3-6: Void
Table 8.1.2.7.3.3-7: Void
Table 8.1.2.7.3.3-8: RRCConnectionReconfiguration (step 3D, Table 8.1.2.7.3.2-2)

8.1.2.8 RRC connection establishment / Range of access baring time
(1)
with { UE in E-UTRA RRC_IDLE state with T303 running }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 667
667
ensure that {
}
(2)
with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 with no restriction }
ensure that {
}
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
2>if timer T302 is running:
2>else:
2>if SystemInformationBlockType2 includes the ac-BarringInfo:
3>if the ac-BarringForEmergency is set to FALSE:
3>else if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15,
which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11]:
NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the
HPLMN/ EHPLMN.
4>if the ac-BarringInfo includes ac-BarringForMO-Data, and for all of the valid Access Classes for the
UE, the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-Data is set
to one:
4>else:
3>else:
2> else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 668
668
present:
3> else:
4>else:
2> else:
present:
3>else:
Signalling:
4>else:
2> else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 669
669
2>start timer T300;
1>else:
are not running:
BarringForMO-Data:
T303=(0.7+0.6
*
rand)
*
ac-BarringTime
T305=(0.7+0.6
*
rand)
*
ac-BarringTime
3>inform upper layers about the failure to establish the RRC connection and that access barring for
emergency calls is applicable, upon which the procedure ends;
2>else:
3>inform upper layers about the failure to establish the RRC connection, upon which the procedure ends;
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in Registered, Idle mode state (state 2) according to [18].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 670
670
U - S Message
systemInfoModification. (Note 3)
<-- Paging - -
2 The SS changes
SystemInformationBlockType2 parameters to
0% access probability for MO calls.
- - - -
information.
- - - -
4 Void - - - -
- - - -
5a The UE does not transmit any
RRCConnectionRequest message (The UE
starts T303) (Note 2)
- - - -
5b Void - - - -
- - - -
8 Wait for 20 s to ensure that T303 expires. - - - -
systemInfoModification (Note 3).
<-- Paging - -
10 The SS changes
default values (Note 4).
- - - -
information.
- - - -
- - - -
RRCConnectionRequest message. The UE
starts T300(Note 1)?
14-
23
Steps 2a2 to 6 of the generic test procedure in
TS 36.508 [18] subclause 6.4.3.2 are
performed on Cell 1
- - - -
Note 1: If access the cell as not barred, start timer T300, initiate transmission of the RRCConnectionRequest
message.
Note 2: The UE is establishing the RRC connection for mobile originating calls,and consider access to the cell as
barred, the UE should draw a rand number rand in the range 0 rand <1, and start T303 with value set
to the maximum value: T303=(0.7+0.6
*
rand)
*
ac-BarringTime.
Note 3: To guarantee that the UE will receive at least one Paging in the Modification Period preceding the SysInfo
change, SS should send the Paging message in every eligible PO in this Modification Period.
Note 4: The default values refer to TS36.508 table 4.4.3.3-1.
Note 5: The triggers in step 5, step 6 and step 12 are the same as in the generic procedure in 36.508 clause
6.4.3.2.

Table 8.1.2.8.3.3-1: Paging (step 1 and step 9, Table 8.1.2.8.3.2-1)
systemInfoModification True
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 671
671
Table 8.1.2.8.3.3-2: SystemInformationBlockType2 (step 2, Table 8.1.2.8.3.2-1)
ac-BarringForEmergency FALSE For AC 10
ac-BarringTime s16
}
ac-BarringTime s16
ac-BarringForSpecialAC '11111'B For AC 11..15
}
}
}

8.1.2.9 RRC Connection Establishment / 0% access probability for MO calls, non-
zero percent access probability for MO signalling
(1)
ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts
SystemInformationBlockType2 indicating non zero percent access probability for MO signalling }
then { UE does not transmit any RRCConnectionRequest message or UE transmits an
RRCConnectionRequest message }
}

(2)
with { UE in E-UTRA RRC_IDLE state having received SystemInformationBlockType2 indicating 0% access
probability for MO call }
ensure that {
}

[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 672
672
present:
3> else:
4>else:
2> else:
present:
3>else:
Signalling:
4>else:
2> else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 673
673
2>start timer T300;
1>else:
are not running:
...
T305=(0.7+0.6
*
rand)
*
ac-BarringTime
System Simulator:
UE:
None.
Preamble:
to [18].
T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 -79
Cell 1
<R
Cell 11
.
T2
Cell-specific RS
EPRE
dBm/15
kHz
-85 -91
Cell 1
>R
Cell 11
.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 674
674
U - S Message
message on Cell 1.
RRC_IDLE state.
- - - -
3 The SS initializes internal counters: K to 0 and
L to 0.
- - - -
- EXCEPTION: Steps 4 to 5b15 shall be
repeated maximum 50 times unless K >0 and
L >0. (Note 1)
- - - -
- - - -
behaviours which vary depending on whether
the UE transmits an RRCConnectionRequest
message or not.
- - - -
5a1 IF the UE does not transmit any
RRCConnectionRequest message within 5 s
(Note 2) THEN the SS increments the counter
K by 1.
- - - -
5a2 The SS changes the power level setting
- - - -
5a3 The SS waits for 20s for the UE to perform cell
reselection procedure. (Note 3)
- - - -
5b1 ELSE IF the UE transmits an
THEN the SS increments the counter L by 1.
5b2-
5b6
TS 36.508 [18] subclause 6.4.2.7 are
- - - -
RRC_IDLE state.
- - - -
5b8 The SS changes the power level setting
- - - -
5b9 The UE transmits an RRCConnectionRequest
message on Cell 1.
5b10
-
5b14
TS 36.508 [18] subclause 6.4.2.7 are
- - - -
RRC_IDLE state.
- - - -
6 Check: Is the counter K >0 and L >0? - - 1 P
- - - -
- - - -
9 Wait for 1 s after the IP packet has been
- - - -
message on Cell 1.
within 30s?
- EXCEPTION: Step 21 and Step 22a1 can
happen in any order.
- - - -
12- Check: Does the test result of steps 1 to 10 - - 1,2 -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 675
675
21 generic test procedure in TS 36.508 subclause
pending.
- - - -
22a1 IF the UE has user data pending THEN the UE
loop backs the IP packet received in step 8 on
bearer context on Cell 1 within 10 s.
- - - -
Note 1: There is an extremely low probability that the UE originating calls are barred, or not barred, 50 times
consecutively. (The probability is 1.7810
-15
). Therefore, 50 times is enough number of trials for this test
case.
Note 3: The UE stops T305 upon cell reselection.
in step 10.

8.1.2.9.3.2-2)
ac-BarringForMO-Signalling SEQUENCE {} Not present
ac-BarringFactor p0
ac-BarringTime s512
}
}
}

8.1.2.9.3.2-2)
ac-BarringTime s8
}
ac-BarringForMO-Data SEQUENCE {} Not present
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 676
676

Table 8.1.2.9.3.3-4: RRCConnectionRequest (step 5b1 and step 5b9, Table 8.1.2.9.3.2-2)
}
}
}

8.1.2.10 RRC connection establishment / 0% access probability for MO calls, 0%
access probability for MO signalling
(1)
ensure that {
when { UE reselects a new cell which belongs to different TA and broadcasts
SystemInformationBlockType2 indicating 0% access probability for MO signalling }
}

(2)
probability for MO call and for MO signalling }
ensure that {
when { UE receives a Paging message }
}

(3)
probability for MO call }
ensure that {
}

[TS 36.331, clause 5.3.3.2]
RRC_IDLE.
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 677
677
...
present:
3> else:
4>else:
2> else:
present:
3>else:
Signalling:
4>else:
2> else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 678
678
2>start timer T300;
NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up to
date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to perform
system information acquisition upon cell re-selection.
1>else:
are not running:
...
T305=(0.7+0.6
*
rand)
*
ac-BarringTime
System Simulator:
UE:
None.
Preamble:
to [18].
T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 -79
Cell 1
<R
Cell 11
.
T2
Cell-specific RS
EPRE
dBm/15
kHz
-85 -91
Cell 1
>R
Cell 11
.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 679
679
U - S Message
message on Cell 1.
RRC_IDLE state.
- - - -
1.
- - - -
(Note 1)
a matched identity allocated in Cell 1.
<-- Paging - -
within 30s? (Note 2)
1 and changes the
SystemInformationBlockType2 on Cell 1.
- - - -
8 The SS waits for 40s the UE to perform cell
reselection procedure (Note 3).
- - - -
pagingRecordLists on Cell 1.
<-- Paging - -
message on Cell 1.
11-
16
Cell 1.
the data radio bearer associated with the
- - - -
- - - -
18 Wait for 1 s after the IP packet has been
- - - -
message on Cell 1.
within 30s?
21-
30
Check: Does the test result of steps 1 to 10
- - 1,2,
3
-
pending.
- - - -
31a1 IF the UE has user data pending THEN the UE
loop backs the IP packet received in step 17
bearer context on Cell 1 within 10 s.
- - - -
Note 2: In case that the UE did not response to paging on Cell 1, it is considered that the UE is camped on Cell 11.
Note 3: The UE stops T305 upon cell reselection.
in step 19.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 680
680

ac-BarringFactor p0
ac-BarringTime s8
}
ac-BarringFactor p0
ac-BarringTime s512
}
}
}

}

8.1.2.10.3.2-2)
ac-BarringFactor p0
ac-BarringTime s512
}
ac-BarringForMO-Data SEQUENCE {} Not present
}
}


8.1.2.11 RRC connection establishment of emergency call
(1)
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 681
681
ensure that {
when { UE is requested to make an outgoing emergency call }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.331 clause 5.3.3.2.
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.

2> if SystemInformationBlockType2 includes the ac-BarringInfo:

2> else:

2>start timer T300;
[TS 36.331, clause 5.3.3.3]

System Simulator:
- Cell 1
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 682
682
Preamble:
U - S Message
1 Make the UE attempt an IMS emergency call - - - -
- EXCEPTION: The behaviour in table
8.1.2.11.3.2-2 occurs in parallel with step 8
(generic radio bearer establishment procedure
step 9)
- - - -
3-8 Steps 4 to 9 of the generic radio bearer
- - - -
- - 1 -

U S Message
Emergency session setup procedure
according TS 34.229-1 [nn]. Details FFS.
- - - -

establishmentCause emergency
}
}
}

8.1.2.12 RRC connection establishment of emergency call / Limited Service
(1)
ensure that {
when { UE camp on an acceptable cell and is requested to make an outgoing emergency call }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.304 clause 4.3, 5.2.3.1
and TS 36.331 clause 5.3.3.2.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 683
683
[TS 36.304, clause 4.3]
This clause defines the level of service that may be provided by the network to a UE in Idle mode.
The action of camping on a cell is necessary to get access to some services. Three levels of services are defined for UE:
- Limited service (emergency calls, ETWS and CMAS on an acceptable cell)
- Normal service (for public use on a suitable cell)
- Operator service (for operators only on a reserved cell)
Furthermore, the cells are categorised according to which services they offer:
acceptable cell:
An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls and
receive ETWS and CMAS notifications). Such a cell shall fulfil the following requirements, which is the minimum set
of requirements to initiate an emergency call and to receive ETWS and CMAS notification in a E-UTRAN network:
suitable cell:
A "suitable cell" is a cell on which the UE may camp on to obtain normal service. The UE shall have a valid USIM and
such a cell shall fulfil all the following requirements.
- The cell is part of at least one TA that is not part of the list of "forbidden tracking areas for roaming", which
- For a CSG cell, the CSG ID is part of the CSG whitelist of the UE.
[TS 36.304, clause 5.2.3.1]
The UE shall use one of the following two cell selection procedures:
a) Initial Cell Selection
This procedure requires no prior knowledge of which RF channels are E-UTRA carriers. The UE shall scan
all RF channels in the E-UTRA bands according to its capabilities to find a suitable cell. On each carrier
frequency, the UE need only search for the strongest cell. Once a suitable cell is found this cell shall be
selected.
b) Stored Information Cell Selection
This procedure requires stored information of carrier frequencies and optionally also information on cell
parameters, from previously received measurement control information elements or from previously detected
cells. Once the UE has found a suitable cell the UE shall select it. If no suitable cell is found the Initial Cell
Selection procedure shall be started.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 684
684
NOTE: Priorities between different frequencies or RATs provided to the UE by system information or dedicated
signalling are not used in the cell selection process.
[TS 36.331, clause 5.3.3.2]
RRC_IDLE.

2> if SystemInformationBlockType2 includes the ac-BarringInfo:

2> else:

2>start timer T300;
[TS 36.331, clause 5.3.3.3]

System Simulator:
- Cell 1
- The PLMN is defined in Table 8.1.2.12.3.1-1.
Table 8.1.2.12.3.11: PLMN identifier
Cell PLMN name
1 PLMN4

UE:
- The UE is equipped with a USIM containing default values except for those listed in Table 8.1.2.12.3.1-2.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 685
685
EF
IMSI

EF
FPLMN
PLMN4
EF
PLMNwAcT
1 Default E-UTRAN
EF
OPLMNwACT
1 PLMN1 E-UTRAN
EF
HPLMNwAcT
1 PLMN1 E-UTRAN

Preamble:
- The UE is Switched OFF (State 1) according to [18].
U - S Message
2 Wait 60s for the UE to camp on Cell 1 as an
acceptable cell.
- - - -
3 Make the UE attempt an IMS emergency call - - - -
in step 17 (generic UE registration procedure
step 16) below the procedure for IMS
signalling in the U-plane specified in table
8.1.2.12.3.2-2 takes place if requested by the
UE. (Note 1)
- - - -
5-
17
Steps 2 to 4 and 7 to 16 of the generic UE
registration procedure (TS 36.508 4.5.2.3-1)
service request procedure. (Note 1)
- - - -
- - 1 -
Note 1: The exception step in table 8.1.2.12.3.2-1 supersedes the IMS exception step prior to step 16 in TS 36.508
table 4.5.2.3-1.

U S Message
Emergency session setup procedure
according TS 34.229-1 [35]. Details FFS.
- - - -

establishmentCause emergency
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 686
686
8.1.3 RRC connection release
8.1.3.1 RRC connection release / Success
(1)
with { UE in RRC_CONNECTED state}
ensure that {
when { UE receives an RRCConnectionRelease message }
then { UE releases the signalling connection, the established EPS bearer and all radio resources
and enters in RRC_IDLE state }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.8.3
and 5.3.12.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1>delay the following actions defined in this sub-clause 60ms from the moment the RRCConnectionRelease
...
1>if the releaseCause received in the RRCConnectionRelease message indicates loadBalancingTAURequired:
2>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause load
balancing TAU required;
1>else:
2>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause other.
[TS 36.331, clause 5.3.12]
Upon leaving RRC_CONNECTED, the UE shall:
1>reset MAC;
1>stop all timers that are running except T320;
1>release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP
entity for all established RBs;
1>indicate the release of the RRC connection to upper layers together with the release cause;
1>if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:
2>enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the
case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].
System Simulator:
- Cell 1
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 687
687
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18].
U - S Message
1 SS transmits an RRCConnectionRelease
message to release the RRC connection.
2 SS waits for 5s. - - - -
state on Cell 1?
- - 1 -

None.
8.1.3.2 Void
8.1.3.3 Void
8.1.3.4 RRC connection release / Redirection to another E-UTRAN frequency
(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE RedirectionInformation with E-
UTRA-CarrierFreq different from the frequency UE was on in RRC_CONNECTED state}
then { UE enters RRC_IDLE state on new frequency included in IE RedirectionInformation }
}

5.3.12 and TS 36.304, clauses 5.2.4.1, 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:

1>else:

1>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 688
688
[TS 36.331, clause 5.3.12]

[TS 36.304, clause 5.2.4.1]

UE shall only perform cell reselection evaluation for E-UTRAN frequencies and inter-RAT frequencies that are given
in system information and for which the UE has a priority provided.

[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to
redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on
an EUTRA carrier. If no suitable cell is found, the UE shall perform a cell selection starting with Stored Information
Cell Selection procedure in order to find a suitable cell to camp on.
...
System Simulator:
- 2 cells on different E-UTRA frequencies and different tracking areas:
- Cell 1 serving cell
- Cell 23 suitable neighbour inter-frequency cell
- Cell power levels are selected according to [18] so that camping on Cell 1 is guaranteed
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 689
689
U - S Message
message (IE redirectionInformation including
eutra-CarrierFreq of Cell 23).

Cell 23?
- - 1 -

Table 8.1.3.4.3.3-1: Conditions for tables 8.1.3.4.3.3-2 and 8.1.3.4.3.3-3
Condition descriptions
Cell 1
This condition applies to system information transmitted on Cell 1.
Cell 23

Table 8.1.3.4.3.3-2: Void
Table 8.1.3.4.3.3-3: SystemInformationBlockType5 for cells 1 and 3 (preamble and all steps, Table
8.1.3.4.3.2-1)

as used for Cell 23
Cell 1
as used for Cell 1
Cell 23
cellReselectionPriority[n] Not present
}
}

Table 8.1.3.4.3.3-4 RRCConnectionRelease message (step 1, Table 8.1.3.4.3.2-1)
c1 CHOICE {
redirectedCarrierInfo ::=CHOICE {
eutra Downlink EARFCN of cell
23

}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 690
690
8.1.3.5 RRC connection release / Success / With priority information
(1)
with { UE in E-UTRA RRC_IDLE state having received an RRCConnectionRelease message with the
freqPriorityListEUTRA with higher priority frequency}
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher
priority frequency }
then { UE reselects the cell which belongs to the higher priority frequency }
}
TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5.
[TS 36.331, clause 5.3.8.3]
The UE shall:
1>delay the following actions defined in this sub-clause 60 ms from the moment the RRCConnectionRelease
2>store the cell reselection priority information provided by the idleModeMobilityControlInfo;
2>if the t320 is included:
3>start timer T320, with the timer value set according to the value of t320;
1>else:
...
1>if the releaseCause received in the RRCConnectionRelease message indicates 'loadBalancingTAURequired':
2>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'load
balancing TAU required';
1>else:
[TS 36.304, clause 5.2.4.1]
priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG cell,
the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 691
691
information.
[TS 36.304, clause 5.2.4.2]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided
by the serving cell.
- If the serving cell fulfils Srxlev

>S
IntraSearchP
and Squal >S
IntraSearchQ
, the UE may choose not to perform intra-
frequency measurements.
- Otherwise, the UE shall perform intra-frequency measurements.
- If the serving cell fulfils Srxlev >S
nonIntraSearchP
and Squal >S
nonIntraSearchQ
, the UE may choose not to
perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower
priority.
- Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency
cells of equal or lower priority according to [10].
[TS 36.304, clause 5.2.4.5]
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a higher priority E-
UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
- A cell of a higher priority EUTRAN or UTRAN RAT/ frequency fulfils Squal >Thresh
X, HighQ
during a time
interval Treselection
RAT
; or
- A cell of a higher priority GERAN or CDMA2000 RAT/ frequency fulfils Srxlev >Thresh
X, HighP
during a time
interval Treselection
RAT
; and
X, HighP
RAT
;
and
More than 1 second has elapsed since the UE camped on the current serving cell.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 692
692
If threshServingLowQ is provided in SystemInformationBlockType3, cell reselection to a cell on a lower priority E-
UTRAN frequency or inter-RAT frequency than the serving frequency shall be performed if:
Serving, LowQ
and a cell of a lower priority EUTRAN or UTRAN RAT/
frequency fulfils Squal >Thresh
X, LowQ
RAT
; or
Serving, LowQ
and a cell of a lower priority GERAN or CDMA2000 RAT/
frequency fulfils Srxlev >Thresh
X, LowP
RAT
; and
Serving, LowP
Thresh
X, LowP
RAT
; and
X, HighP
and Thresh
X, LowP
RAT
- If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the
highest priority frequency(ies) meeting the criteria of that RAT.
System Simulator:
- Cell 1, Cell 3 and Cell6.
NOTE: For Cell 3 and 6 TAI is set to TAI-2
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 693
693
T0
Cell-specific RS
EPRE
dBm/
15kH
z
-85 "off "off
Cell 1
>
S
intrasearch
. (NOTE 1)
T1
Cell-specific RS
EPRE
dBm/
15kH
z
-85 -73 -73
assigned to satisfy both
Thresh
x, low
<Srxlev
Cell 3
and
Thresh
x, high
<Srxlev
Cell 6
.

U - S Message
message including the freqPriorityListEUTRA
on Cell 1.
RRC_IDLE state on Cell 1.
- - - -
3 The SS changes Cell 1, Cell 3 and Cell 6 level
- - - -
4 Void - - - -
Cell 6?
- - 1 -

c1 CHOICE {
freqPriorityListEUTRA SEQUENCE (SIZE
3 entries
as used for Cell 1

as used for Cell 3

as used for Cell 6

}
freqPriorityListUTRA-FDD Not present
freqPriorityListUTRA-TDD Not present
t320 Not present
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 694
694
8.1.3.5.3.2-2)

as used for Cell 3

dl-CarrierFreq[m] Same downlink EARFCN
as used for Cell 6

threshX-Low[n] 11
threshX-High[m] 11
}
}

Table 8.1.3.5.3.3-3: SystemInformationBlockType5 for Cell 6 (all steps, Table 8.1.3.5.3.2-2)
2 entries
dl-CarrierFreq[1] Same downlink EARFCN
as used for Cell 1

dl-CarrierFreq[2] Same downlink EARFCN
as used for Cell 3

cellReselectionPriority [2] 1
}
}

8.1.3.6 RRC connection release / Redirection from E-UTRAN to UTRAN
(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectionInformation with
utra-CarrierFreq UTRA frequency }
then { UE enters RRC_IDLE state on UTRA frequency included in IE redirectionInformation }
}

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.8.3, 5.3.12
and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:

1>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 695
695

1>else:
[TS 36.331, clause 5.3.12]

[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, UE shall select a suitable cell to camp on according to
redirectedCarrierInfo, if included in the RRCConnectionRelease message. Otherwise UE shall select a suitable cell on
an EUTRA carrier.
...
System Simulator:
- 2 cells, one E-UTRA and one UTRA cell and different location areas:
- Cell 1 E-UTRA serving cell
- Cell 5 suitable neighbour UTRA cell
- The parameters settings and power levels for Cell 1 and Cell 5 are selected according to [18], [5] and Table
8.1.3.6.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 5 can take place (utra
priority is lower than serving and S
Cell 1
>Thresh
Cell 1,low
).
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) on cell 1 according to [18].
Table 8.1.3.6.3.2-0 shows the cell power levels after the preamble.
T0
Cell-specific RS EPRE dBm/15kHz -75 - The power levels are such that
camping on Cell 1 is guaranteed. CPICH_Ec dBm/3.84 MHz - -70

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 696
696
U - S Message
message (IE redirectionInformation including
UTRA-CarrierFreq of Cell 5).
5?
- - 1 -

Table 8.1.3.6.3.3-1: Conditions for tables 8.1.3.6.3.3-2 and 8.1.3.6.3.3-3
Condition descriptions
Cell 1
Cell 5

Table 8.1.3.6.3.3-2: Void
Table 8.1.3.6.3.3-3: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 8.1.3.6.3.2-
1)
UTRA-
FDD
as used for cell 5

cellReselectionPriority[n] 3 Lower priority than
E-UTRA

}
UTRA-
TDD
as used for cell 5

E-UTRA

}
}

Table 8.1.3.6.3.3-4 RRCConnectionRelease message (step 1, Table 8.1.3.6.3.2-1)
c1 CHOICE {
utra-FDD Downlink UARFCN of cell
5
UTRA-
FDD
utra-TDD Downlink UARFCN of cell
5
UTRA-
TDD
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 697
697
8.1.3.7 RRC connection release / Redirection from UTRAN to E-UTRAN
(1)
with { UE in UTRA Idle state }
ensure that {
when { UE is requested to make an outgoing PS call }
then { UE includes in the RRC CONNECTION REQUEST the IE Pre-Redirection info" }
}
(2)
with { UE in UTRA CELL_DCH state }
ensure that {
when { UE receives an RRC CONNECTION RELEASE message including an IE Redirection info with E-UTRA
target info E-UTRA frequency }
then { UE enters RRC_IDLE state on E-UTRAN Carrier included in IE Redirection info }
}

8.1.4.3 and clause 8.5.2.
[TS 25.331, clause 8.1.3.3]
The UE shall, in the transmitted RRC CONNECTION REQUEST message:

1>if the UE supports E-UTRA:
2>if the variable EUTRA_FREQUENCY_INFO_LIST contains no E-UTRA frequencies;
3>include the IE "Pre-Redirection info";
3>if the UE supports E-UTRA FDD:
4>set the IE "Support of E-UTRA FDD" to TRUE.
3>if the UE supports E-UTRA TDD:
4>set the IE "Support of E-UTRA TDD" to TRUE.
2>if the UE supports any of the bands that the E-UTRA frequencies included in the variable
EUTRA_FREQUENCY_INFO_LIST belong to;
3>if the UE supports any of the bands that the E-UTRA FDD frequencies included in the variable
EUTRA_FREQUENCY_INFO_LIST belong to:
3>if the UE supports any of the bands that the E-UTRA TDD frequencies included in the variable
[TS 25.331, clause 8.1.4.3]
The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH
and CELL_PCH (FDD only). 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
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 698
698
1>if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable
U_RNTI; or
1>if the message is received on DCCH:
the UE shall perform the RRC connection release procedure as specified below.
When the UE receives the first RRC CONNECTION RELEASE message; and
1>if the message is received on the CCCH, the IE "UTRAN group identity" is present and there is a group identity
match according to subclause 8.6.3.13:
the UE shall perform the RRC connection release procedure as specified below.
The UE shall:
1>in state CELL_DCH:
2>initialise the counter V308 to zero;
2>set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the
value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the
table "Accepted transactions" in the variable TRANSACTIONS;
2>submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using
UM RLC on the DCCH to the UTRAN;
2>if the IE "Rplmn information" is present:
3>the UE may:
4>store the IE on the ME together with the PLMN id for which it applies;
3>the UE may then:
4>utilise this information, typically indicating where a number of BCCH frequency ranges of a RAT
may be expected to be found, during subsequent Rplmn selections of the indicated PLMN.
2>if the IE "UE Mobility State Indicator" is present:
3>consider the High-mobility state to have being detected when entering idle mode.
2>start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio
interface.
1>in state CELL_FACH:
2>if the RRC CONNECTION RELEASE message was received on the DCCH:
3>set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to
the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in
the table "Accepted transactions" in the variable TRANSACTIONS;
3>submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission
using AM RLC on the DCCH to the UTRAN.
3>when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been
confirmed by the lower layers:
4>release all its radio resources; and
4>indicate the release of the established signalling connections (as stored in the variable
ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in
the variable ESTABLISHED_RABS) to upper layers; and
4>clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions"
and "Rejected transactions" in the variable TRANSACTIONS;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 699
699
4>clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
4>clear the variable ESTABLISHED_RABS;
4>pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to
upper layers;
4>enter idle mode;
4>perform the actions specified in subclause 8.5.2 when entering idle mode.
3>and the procedure ends.
2>if the RRC CONNECTION RELEASE message was received on the CCCH:
3>release all its radio resources;
3>indicate the release of the established signalling connections (as stored in the variable
ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the
variable ESTABLISHED_RABS) to the upper layers;
3>clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions"
and "Rejected transactions" in the variable TRANSACTIONS;
3>clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
3>clear the variable ESTABLISHED_RABS;
3>pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to
upper layers;
3>enter idle mode;
3>perform the actions specified in subclause 8.5.2 when entering idle mode;
3>and the procedure ends.
[TS 25.331, clause 8.5.2]
When entering idle mode from connected mode, the UE shall:
1>clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4;
1>if the RRC CONNECTION RELEASE message was received and the IE "Redirection info" was present therein:
2>if the IE "Frequency info" is present, attempt to camp on a suitable cell on the indicated UTRA carrier
included in the RRC CONNECTION RELEASE message;
2>if the IE "GSM target cell info" is present, attempt to camp on a suitable cell of the list of cells for the
indicated RAT included in the RRC CONNECTION RELEASE message. If no cells were indicated for that
RAT or no suitable cell of the indicated cells for that RAT is found within 10s, attempt to camp on any
suitable cell of that RAT; or
2>if the IE "E-UTRA target info" is present, attempt to camp on any of the frequencies for the indicated RAT
included in the RRC CONNECTION RELEASE message, excluding any cell indicated in the list of not
allowed cells for that RAT, if present. If no suitable cell on the indicated frequencies for that RAT is found
within 10s, attempt to camp on any suitable cell of that RAT, excluding any cell indicated in the list of not
allowed cells for that RAT; or
2>if no suitable cell is found on the indicated UTRA carrier or RAT camp on any suitable cell.
System Simulator:
- 2 cells, one UTRA and one E-UTRA cell:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 700
700
- Cell 5 UTRA serving cell (priority 4 default)
- Cell 1 suitable neighbour E-UTRA cell (priority 3)
UE:
UTRAN Idle state
Preamble:
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.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 701
701
U - S Message
1 Make the UE initiate an outgoing PS call. - - - -
2 Check: does the UE include the IE Pre-
redirection info with Support of E-UTRA set to
TRUE?
3 The SS transmit a RRC CONNECTION
SETUP on SRB1 on Cell 5.
<--
RRC CONNECTION SETUP - -
SETUP COMPLETE message
COMPLETE
- -
5 The UE transmits the SERVICE REQUEST
message for PS data call
--> INITIAL DIRECT TRANSFER - -
- UTRAN FDD: EXCEPTION:
IF pc_UTRA_CompressedModeRequired
THEN Steps 6a1, 6a2

IF pc_UTRA_FeatrGrp_2 THEN 6b1 to 6b2

describe behaviour that depends on the UE
capability; the "lower case letter" identifies a
step sequence that takes place if a capability is
supported.

UTRAN TDD: go to step 6b1

6a1 The SS transmits a PHYSICAL CHANNEL
RECONFIGURATION message on Cell 5
including the DPCH compressed mode info.
<-- PHYSICAL CHANNEL
RECONFIGURATION
- -
6a2 The UE transmits a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message
on Cell 5.
--> PHYSICAL CHANNEL
RECONFIGURATION
COMPLETE
- -
6b1 The SS configures the Inter-RAT periodic
measurement with E-UTRA frequency list
including the DL Carrier frequency of Cell 1
<-- MEASUREMENT CONTROL - -
6b2 The UE starts sending MEASUREMENT
REPORT messages during the Authentication
Phase
--> MEASUREMENT REPORT - -
7-9 void
10 The SS starts the Authentication and Ciphering
Request procedure
11 The UE transmits the Authentication and
Ciphering Response
12 The SS transmits a SECURITY MODE
COMMAND message
<-- SECURITY MODE COMMAND - -
13 The UE transmits a SECURITY MODE
COMPLETE message
--> SECURITY MODE COMPLETE - -
14 If the measurement reports is received during
the authentication and security phase (from
step 9 to 13) goto next step otherwise the SS
waits for MEASUREMENT REPORT message.
RELEASE message (IE E-UTRA target info
including DL Carrier frequency of Cell 1).
<-- RRC CONNECTION RELEASE - -
16 The UE transmits a RRC CONNECTION
RELEASE COMPLETE message
COMPLETE
- -
17 The UE transmits a RRC CONNECTION
RELEASE COMPLETE message
COMPLETE
- -
Cell 1?
- - 2 -
NOTE: pc_FeatrGrp_2 is always set to TRUE when pc_UTRA_CompressedModeRequired is TRUE

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 702
702
Table 8.1.3.7.3.3-1 System Information Block type 19 for cell 5 (preamble and all steps, Table
8.1.3.7.3.2-1)
Derivation Path: 36.508 table Table 4.4.4.1-1
priority 4
}
1 entry
earfcn[1] Downlink EARFCN of
Cell 1

priority[1] 3
}
}

Table 8.1.3.7.3.3-2: RRC CONNECTION REQUEST (UTRA Rel-8)
Derivation path: 34.108 default RRC CONNECTION REQUEST in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA
TDD
Pre-redirection info The presence of
this IE indicates
the UE support of
radio access
technologies that
the UE could be
directed to

Support of E-UTRA FDD TRUE E-UTRA-
FDD
Support of E-UTRA TDD TRUE E-UTRA-
TDD

Table 8.1.3.7.3.3-3: MEASUREMENT CONTROL (UTRA Rel-8)
Derivation Path: 36.508, clause 4.7B.1 Table 4.7B.1-3
CHOICE Measurement type Inter-RAT measurement
CHOICE report criteria Inter-RAT measurement
reporting criteria

Parameters required for each event 1 entry
Inter-RAT event identity 3c

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 703
703
Table 8.1.3.7.3.3-4: RRC CONNECTION RELEASE (UTRA Rel-8)
Derivation path: 34.108 default RRC CONNECTION RELEASE in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA TDD
N308 1
Redirection info
Frequency info Omitted
Inter-RAT info E-UTRA
E-UTRA target info
E-UTRA Target Frequency Info List 1 Entry
FDD E-UTRA-FDD
DL Carrier frequency The DL Carrier frequency
of Cell 1

Blacklisted cells per freq list Omitted
TDD E-UTRA-TDD
DL Carrier frequency The DL Carrier frequency
of Cell 1

Blacklisted cells per freq list Omitted

8.1.3.8 RRC connection release / Redirection from E-UTRAN to GERAN
(1)
ensure that {
when { UE receives an RRCConnectionRelease message including an IE redirectedCarrierInfo set to
geran }
then { UE enters Idle mode on GERAN Cell included in IE redirectedCarrierInfo }
}

and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:

1>else:

1>else:
[TS 36.331, clause 5.3.12]

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 704
704
2>enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of
leaving RRC_CONNECTED, as specified in TS 36.304 [4].
[TS 36.304, clause 5.2.7]
On transition from RRC_CONNECTED to RRC_IDLE, a UE shall attempt to camp on the last cell for which it was in
RRC_CONNECTED or any cell on a frequency or frequency of RAT assigned by RRC in the state transition message.
...
System Simulator:
- 2 cells, one E-UTRA and one GERAN cell and different location areas:
- Cell 1 E-UTRA serving cell (priority 4 default)
- Cell 24 GERAN neighbouring cell (priority 3)
- The parameters settings and power levels for Cell 1 and Cell 24 are selected according to [18], [5], [25] and
Table 8.1.3.8.3.2-0 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 24 can take place
(GERAN priority is lower than serving and S
Cell 1
>Thresh
Cell 1,low
)
UE:
None.
Preamble:
T0
camping on Cell 1 is guaranteed. GERAN Cell Power dBm - -70

U - S Message
message (IE redirectedCarrierInfo including
startingARFCN of Cell 24).
24?
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 705
705
Table 8.1.3.8.3.3-1: Void
Table 8.1.3.8.3.3-2: SystemInformationBlockType7 for cell 1 (preamble and all steps, Table 8.1.3.8.3.2-
1)
carrierFreqsInfoList SEQUENCE (SIZE
(1..maxGNFG)) OF SEQUENCE {

CarrierFreqsGERAN SEQUENCE [n] {
}
}
}
}
}
}

Table 8.1.3.8.3.3-3: RRCConnectionRelease message (step 1, Table 8.1.3.8.3.2-1)
c1 CHOICE {
redirectedCarrierInfo CHOICE {
geran SEQUENCE {
startingARFCN Downlink ARFCN of Cell
24

bandIndicator The same band indicator
of the Cell 24

explicitListOfARFCNs 0 Entries
}
}
}
}
}
}
}

8.1.3.9 RRC connection release / Redirection from E-UTRAN to CDMA2000-HRPD
(1)
ensure that {
cdma2000-HRPD }
then { UE enters cdma2000-HRPD mode }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 706
706
and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:

1>else:
2>use the idle mobility parameters broadcast in the system information;

1>else:
[TS 36.331, clause 5.3.12]

[TS 36.304, clause 5.2.7]
...
System Simulator:
- 2 cells, one E-UTRA and one HRPD cell:
- Cell 15 suitable neighbour HRPD cell
- The parameters settings and power levels for Cell 1 and Cell 15 are selected according to [18], [xx] and Table
8.1.3.9.3.2-1 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 15 can take place (hrpd
Cell 1
>Thresh
Cell 1,low
).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 707
707
UE:
None.
Preamble:
Note: UE is not pre-registered in Cell 15.
T0
camping on Cell 1 is guaranteed. or/Ioc dB - -5
Pilot Ec /Io (Note 1) dB - -6

U - S Message
message (IE redirectedCarrierInfo including
cdma2000-HRPD of Cell 15).
on Cell 15 to initiate registration?

Table 8.1.3.9.3.3-1: Void
c1 CHOICE {
cdma2000-HRPD cdma2000-CarrierInfo for
Cell 15

}
}
}
}
}

8.1.3.10 RRC connection release / Redirection from E-UTRAN to CDMA2000-1xRTT
(1)
ensure that {
cdma2000-1xRTT }
then { UE enters cdma2000-1xRTT mode }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 708
708
}

and TS 36.304, clause 5.2.7.
[TS 36.331, clause 5.3.8.3]
The UE shall:

1>else:

1>else:
[TS 36.331, clause 5.3.12]

[TS 36.304, clause 5.2.7]
...
System Simulator:
- 2 cells, one E-UTRA and one 1xRTT cell:
- Cell 19 suitable neighbour 1xRTT cell
- The parameters settings and power levels for Cell 1 and Cell 19 are selected according to [18], [yy] and Table
8.1.3.10.3.2-1 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 19 can take place
(1xRTT priority is lower than serving and S
Cell 1
>Thresh
Cell 1,low
).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 709
709
UE:
- UE is not pre-registered in Cell 19.
Preamble:
T0
camping on Cell 1 is guaranteed. or/Ioc dB - 0

U - S Message
message.
on Cell 19 to initiate registration?

Table 8.1.3.10.3.3-1: Void
c1 CHOICE {
cdma2000-1xRTT cdma2000-CarrierInfo for
Cell 19

}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 710
710
8.2 RRC connection reconfiguration
8.2.1 Radio bearer establishment
8.2.1.1 RRC connection reconfiguration / Radio bearer establishment for transition
from RRC_IDLE to RRC_CONNECTED / Success / Default bearer / Early
bearer establishment
(1)
with { UE having completed the RRC connection establishment procedure }
ensure that {
when { SS sends in sequence a SecurityModeCommand and an RRCConnectionReconfiguration message }
then { UE establishes the initial security configuration in accordance with the received
securityConfigSMC included in SecurityModeCommand and successfully completes the connection
reconfiguration }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.1.2,
5.3.1.1, 5.3.5.3, 5.3.10.1 and 5.3.10.3. The following represent an extraction of the requirements relevant to the test
purpose.
[TS 36.331, clause 5.1.2]
The UE shall:
1>process the received messages in order of reception by RRC, i.e. the processing of a message shall be completed
before starting the processing of a subsequent message;
NOTE: 1 E-UTRAN may initiate a subsequent procedure prior to receiving the UEs response of a previously
initiated procedure.
[TS 36.331, clause 5.3.1.1]
After having initiated the initial security activation procedure, E-UTRAN initiates the establishment of SRB2 and DRBs,
i.e. E-UTRAN may do this prior to receiving the confirmation of the initial security activation from the UE. In any case,
E-UTRAN will apply both ciphering and integrity protection for the RRC connection reconfiguration messages used to
establish SRB2 and DRBs.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and theUE is able to comply
with the configuration included in this message, the UE shall:
1>if this is the first RRCConnectionReconfiguration message after successful completion of the RRC
Connection Re-establishment procedure:
...
1>else:
2>If the RRCConnectionReconfiguration message includes theradioResourceConfigDedicated:
3>perform the radio resource configuration procedure as specified in 5.3.10;
NOTE 2: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than
SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an
outstanding acknowledgment of the SecurityModeComplete message.
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 711
711
1>submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new
configuration, upon which the procedure ends;
[TS 36.331, clause 5.3.10.1]
The UE shall:
1>for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration
(SRB establishment):
2>apply the specified configuration defined in 9.1.2 for the corresponding SRB;
2>establish a PDCP entity and configure it with the current security configuration, if applicable;
2>establish an RLC entity in accordance with the received rlc-Config;
2>establish a DCCH logical channel in accordance with the received logicalChannelConfig and with the logical
channel identity set in accordance with 9.1.2
[TS 36.331, clause 5.3.10.3]
The UE shall:
1>for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration
(DRB establishment):
2>establish a PDCP entity and configure it with the current security configuration and in accordance with the
received pdcp-Config;
2>establish a DTCH logical channel in accordance with the received logicalChannelIdentity and the received
logicalChannelConfig;
1>indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;
System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 712
712
U - S Message
1 SS sends a Paging message to the UE on the
identity in one entry of the IE
pagingRecordLists.
<-- Paging - -
2 UE transmits an RRCConnectionRequest
message.
3 SS transmit an RRCConnectionSetup
message
<--
RRCConnectionSetupComplete to confirm the
establishment. (Note 1)
5 SS transmits a SecurityModeCommand
message to activate AS security.
6 Using the same TTI as the
SecurityModeCommand message in step 5,
the SS transmits an
establish a data radio bearer.
SecurityModeComplete message?
message to confirm the establishment of data
radio bearer?
omplete
1 P
indicate that UE is in E-UTRA
- - 1 -
Note 1: Contains a SERVICE REQUEST NAS message.


8.2.1.2 Void
8.2.1.3 RRC connection reconfiguration / Radio bearer establishment / Success /
Dedicated bearer
(1)
ensure that {
when { SS sends an RRCConnectionReconfiguration message including a drb-Identity that is not part
of the current UE configuration and a dedicatedInfoNASList}
then { UE successfully establish the radio bearer according to IE radioResourceConfigDedicated }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.3
and 5.3.10.3.
The following represent an extraction of the requirements relevant to the test purpose.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 713
713
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInformation and theUE is able to
comply with the configuration included in this message, the UE shall:
1>if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection
Re-establishment procedure:

1>else:
1>if the RRCConnectionReconfiguration message includes thededicatedInfoNASList:
2>forward each element of the dedicatedInfoNASList to upper layers;

[TS 36.331, clause 5.3.10.3]
The UE shall:
1>for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration
(DRB establishment):
2>establish a PDCP entity and configure it with the current security configuration and in accordance with the
received pdcp-Config;
2>establish a DTCH logical channel in accordance with the received logicalChannelIdentity and the received
logicalChannelConfig;
1>indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;
System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 714
714
U - S Message
message?

omplete
1 P
3 The UE transmits an ULInformationTransfer
message. This message includes an
ACTIVATE DEDICATED EPS BEARER
CONTEXT ACCEPT message.
- - 1 -

Derivation Path: 36.508 table 4.6.1-8, condition DRB(1,0)
c1 CHOICE{
dedicatedInfoNASList SEQUENCE
(SIZE(1..maxDRB)) OF
1 entry
dedicatedInfoNAS [1] ACTIVATE DEDICATED
EPS BEARER
CONTEXT REQUEST
with EPS bearer identity
corresponding to drb-
Identity 2
According 36.508
table 4.7.3-3

}
}
}
}

8.2.1.4 Void
from RRC_Idle to RRC CONNECTED / Success / Latency check
(1)
with { UE in E-UTRA RRC_IDLE state and has sent an RRCConnectionRequest message }
ensure that {
when { UE receive a RRCConnectionSetup message and 15 subframes later receives an UL grant }
then { UE successfully transmit RRCConnectionSetupComplete message }
}

(2)
ensure that {
when { UE receive a SecurityModeCommand message and 10 subframes later receives an UL grant }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 715
715
then { UE successfully establish the initial AS security activation according to IE
securityConfigSMC }
}

(3)
ensure that {
when { UE receive a RRCConnectionReconfiguration message including a drb-Identity that is not part
of the current UE configuration and a nas-DedicatedInformation and 15 subframes later receives an UL
grant }
then { UE successfully establish the radio bearer according to IE radioResourceConfiguration }
}

(4)
ensure that {
when { UE receives an UECapabilityEnquiry message after AS security is activated and at 10
subframes later receives an UL grant }
then { UE successfully transmits an UECapabilityInformation message including UE radio access
capability information corresponding to the ue-RadioAccessCapRequest variable }
}

5.3.4.3, 5.3.5.3, 5.6.3.3 and 11.2.
[TS 36.331, clause 5.3.3.4]
The UE shall:
1>stop timer T300;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 716
716
procedure ends;
[TS 36.331, clause 5.3.4.3]
The UE shall:
1>derive the K
eNB
key, as specified in TS 33.401 [32];
1>derive the K
RRCint
key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.401 [32];
1>request lower layers to verify the integrity protection of the SecurityModeCommand message, using the
algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the
K
RRCint
key;
1>if the SecurityModeCommand message passes the integrity protection check:
2>derive the K
RRCenc
key and the K
UPenc
key associated with the cipheringAlgorithm indicated in the
SecurityModeCommand message, as specified in TS 33.401 [32];
2>configure lower layers to apply integrity protection using the indicated algorithm and the K
RRCint
key
immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE,
including the SecurityModeComplete message;
2>configure lower layers to apply ciphering using the indicated algorithm, the K
RRCenc
key and the K
UPenc
key
after completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent
by the UE, except for the SecurityModeComplete message which is sent unciphered;
2>consider AS security to be activated;
2>submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends;
[TS 36.331, clause 5.3.5.3]

1>else:
2>if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:
1>if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:

[TS 36.331, clause 5.6.3.3]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 717
717
1>set the contents of UECapabilityInformation message as follows:
2>if the ue-CapabilityRequest includes eutra:
3>include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to
eutra;
2>if the ue-CapabilityRequest includes geran-cs and if the UE supports GERAN CS domain:
3>include the UE radio access capabilities for GERAN CS within a ue-CapabilityRAT-Container and with
the rat-Type set to geran-cs;
2>if the ue-CapabilityRequest includes geran-ps and if the UE supports GERAN PS domain:
3>include the UE radio access capabilities for GERAN PS within a ue-CapabilityRAT-Container and with
the rat-Type set to geran-ps;
2>if the ue-CapabilityRequest includes utra and if the UE supports UTRA:
3>include the UE radio access capabilities for UTRA within a ue-CapabilityRAT-Container and with the
rat-Type set to utra;

1>submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;
[TS 36.331, clause 11.2]
The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:
N =the number of 1ms subframes from the end of reception of the E-UTRAN ->UE message on the UE physical layer
up to when the UE shall be ready for the reception of uplink grant for the UE ->E-UTRAN response message with no
access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or
physical layer synchronisation).
RRC DL
command
U
L

G
r
a
n
t
RRC UL
response
RRC procedure delay
DL
UL

Figure 11.2-1: Illustration of RRC procedure delay

Procedure title: E-UTRAN -> UE UE -> E-UTRAN N Notes
RRC Connection Control Procedures
RRC connection
establishment
RRCConnectionSetu
p
RRCConnectionSetupCo
mplete
15
RRC connection re-
configuration (radio
resource configuration)
RRCConnectionReco
nfiguration
RRCConnectionReconfigu
rationComplete
15
Initial security
activation
SecurityModeComma
nd
SecurityModeCommandC
omplete/SecurityModeCo
mmandFailure
10
Other procedures
UE capability transfer UECapabilityEnquiry UECapabilityInformation 10

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 718
718
System Simulator:
- Cell 1
UE:
None.
Preamble:
U - S Message
pagingRecordList.
<-- Paging - -
message.
message. (Note 3)
<--
RRCConnectionSetup
within 19 (FDD)/22 (TDD) subframes after
successful completion of step 3? (Note 2)
message to activate AS security. (Note 3)
<-- SecurityModeCommand
SecurityModeComplete message within 14
(FDD)/17 (TDD) subframes after successful
completion of step 5? (Note 2)
establish a data radio bearer. (Note 3)
message within 19 (FDD)/22 (TDD) subframes
after successful completion of step 7? (Note 2)
omplete
3 P
9 The SS transmits a UECapabilityEnquiry
message to request UE radio access capability
information for E UTRA only. (Note 3)
UECapabilityInformation message within 14
--> UECapabilityInformation 4 P
Note 1: The SS is configured for RRC procedure delay testing according to TS 36.523-3 clause 7.12.1.
Note 2: 4 (FDD) / 7 (TDD) subframes is added on top of RRC processing delay requirement, because of
transmission delay after UL grant. For TDD, consider the max 7 TTI transmission delay after UL grant.
Note 3: The DL resource allocation sent on PDCCH is big enough to guarantee transmission of all DL RRC PDU in
single TTI.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 719
719
}
}
}


from RRC_Idle to RRC CONNECTED / Success / Latency check /
SecurityModeCommand and RRCConnectionReconfiguration transmitted in
the same TTI
(1)
ensure that {
when { UE received SecurityModeCommand message and RRCConnectionReconfiguration message including
a drb-Identity that is not part of the current UE configuration and a nas-DedicatedInformation in
the same TTI and 20 subframes later receives an UL grant }
then { UE successfully establish the initial AS security activation according to IE
securityConfigSMC and the radio bearer according to IE radioResourceConfiguration }
}

5.3.5.3 and 11.2.
[TS 36.331, clause 5.3.4.3]
The UE shall:
1>derive the K
eNB
1>derive the K
RRCint
key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.401 [32];
1>request lower layers to verify the integrity protection of the SecurityModeCommand message, using the
algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the
K
RRCint
key;
1>if the SecurityModeCommand message passes the integrity protection check:
2>derive the K
RRCenc
key and the K
UPenc
key associated with the cipheringAlgorithm indicated in the
SecurityModeCommand message, as specified in TS 33.401 [32];
2>configure lower layers to apply integrity protection using the indicated algorithm and the K
RRCint
key
immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE,
including the SecurityModeComplete message;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 720
720
2>configure lower layers to apply ciphering using the indicated algorithm, the K
RRCenc
key and the K
UPenc
key
after completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent
by the UE, except for the SecurityModeComplete message which is sent unciphered;
2>consider AS security to be activated;
2>submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends;
[TS 36.331, clause 5.3.5.3]

1>else:
1>if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:

[TS 36.331, clause 11.2]
The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:
N =the number of 1ms subframes from the end of reception of the E-UTRAN ->UE message on the UE physical layer
up to when the UE shall be ready for the reception of uplink grant for the UE ->E-UTRAN response message with no
access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or
physical layer synchronisation).
RRC DL
command
U
L

G
r
a
n
t
RRC UL
response
RRC procedure delay
DL
UL

Figure 11.2-1: Illustration of RRC procedure delay

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 721
721
RRC Connection Control Procedures
Initial security
activation +RRC
connection re-
configuration (RB
establishment)
SecurityModeComma
nd,
RRCConnectionReco
nfiguration
RRCConnectionReconfigu
rationComplete
20 The two DL messages are
transmitted in the same TTI

System Simulator:
- Cell 1
UE:
None.
Preamble:
U - S Message
pagingRecordList.
<-- Paging - -
message.
message.
<--
4 The UE transmit an
message to activate AS security. (Note 3)
establish a data radio bearer. (Note 3)
SecurityModeComplete message within 24
message within 24 (FDD)/27 (TDD) subframes
after successful completion of step 6? (Note 2)
omplete
1 P
Note 1: The SS is configured for RRC procedure delay testing according to TS 36.523-3 clause 7.12.1.
Note 2: 4 (FDD) / 7 (TDD) subframes is added on top of RRC processing delay requirement, because of
transmission delay after UL grant. For TDD, consider the max 7 TTI transmission delay after UL grant.
Note 3: The DL resource allocation sent on PDCCH is big enough to guarantee transmission of all DL RRC PDU in
single TTI.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 722
722
}
}
}


8.2.1.7 RRC connection reconfiguration / Radio bearer establishment / Success /
SRB2
with { UE in E-UTRA RRC_CONNECTED state without SRB2}
ensure that {
when { SS sends an RRCConnectionReconfiguration message including SRB2 configuration }
then { UE successfully establish the signalling radio bearer }
}
and 5.3.10.1.
[TS 36.331, clause 5.3.5.3]

1>else:

[TS 36.331, clause 5.3.10.1]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 723
723
1>for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration
(SRB establishment):
2>apply the specified configuration defined in 9.1.2 for the corresponding SRB;
2>establish a PDCP entity and configure it with the current security configuration, if applicable;
2>establish a DCCH logical channel in accordance with the received logicalChannelConfig and
with the logical channel identity set in accordance with 9.1.2;
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Registered, Idle Mode (State 2) according to [18].
U - S Message
1-7 Generic Radio Bearer Establishment (State 3)
step 1 to 7 in TS 36.508 subclause 4.5.3.3.
- -
establish SRB2.
9 Check: Does the UE transmits an
message?
omplete
1 P
indicates that UE is in E-UTRA
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 724
724
Table 8.2.1.7.3.3-1: RRCConnectionReconfiguration (step 8, Table 8.2.1.7.3.2-1))
C1 CHOICE{
radioResourceConfigDedicated SEQUENCE {
srb-ToAddModList SEQUENCE (SIZE (1..2))
OF SEQUENCE {

srb-ToAddMod[1] SEQUENCE {
rlc-Config CHOICE {
explicitValue RLC-Config-NON-
DEFAULT-SRB2

}
}
}
}
}
}
}
}
}

Table 8.2.1.7.3.3-2: RLC-Config-NON-DEFAULT-SRB2 ( Table 8.2.1.7.3.3-1))
Derivation Path: 36.331 clauses 6.3.2, 9.2.1.2
RLC-Config-NON-DEFAULT-SRB2 ::=CHOICE {
am SEQUENCE {
pollPDU p16
pollByte kb500
maxRetxThreshold t6
}
dl-AM-RLC SEQUENCE {
t-Reordering ms100
}
}
}

8.2.2 Radio resource reconfiguration
8.2.2.1 RRC connection reconfiguration / Radio resource reconfiguration / Success
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a
radioResourceConfigDedicated with SRB, DRB, transport channel and physical channel reconfiguration }
then { UE reconfigures the data and signalling radio bearers and sends an
RRCConnectionReconfigurationComplete message }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 725
725
References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.5.3,
5.3.10.1, 5.3.10.3, 5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.3]
1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection

1>else:
2>If the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

[TS 36.331, clause 5.3.10.1]
The UE shall:

1>for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration (SRB
reconfiguration):
2>reconfigure the RLC entity in accordance with the received rlc-Config;
2>reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;
[TS 36.331, clause 5.3.10.3]

1>for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration (DRB
reconfiguration):
2>if the pdcp-Config is included:
3>reconfigure the PDCP entity in accordance with the received pdcp-Config;
2>if the rlc-Config is included:
3>reconfigure the RLC entity or entities in accordance with the received rlc-Config;
2>if the logicalChannelConfig is included:
3>reconfigure the DTCH logical channel in accordance with the received logicalChannelConfig;
NOTE: Removal and addition of the same drb-Identity in single radioResourceConfiguration is not supported.
[TS 36.331, clause 5.3.10.4]
1>reconfigure the MAC main configuration in accordance with the received mac-MainConfig;
[TS 36.331, clause 5.3.10.6]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 726
726
The UE shall:
1>reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated;
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The condition SRB2-DRB(2, 0) is used for step 8 in 4.5.3.3 according to [18].
U - S Message
RRCConnectionReconfiguration message
containing a radioResourceConfigDedicated
with SRBs, DRB, transport channel and
physical channel reconfiguration.
message?
omplete
1 P
- - 1 -

c1 CHOICE{
dicated-RECONFIG

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 727
727
Table 8.2.2.1.3.3-2: RadioResourceConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-1)
RadioResourceConfigDedicated ::=SEQUENCE {
srb-ToAddModList SRB-ToAddModList-
RECONFIG
TS 36.508 Table
4.6.3-22A

drb-ToAddModList DRB-ToAddModList-
RECONFIG
TS 36.508 Table
4.6.3-2A

explicitValue MAC-MainConfig-
RECONFIG

}
physicalConfigDedicated PhysicalConfigDedicated
-RECONFIG

}

Table 8.2.2.1.3.3-3: MAC-MainConfig-RECONFIG (Table 8.2.2.1.3.3-2)
Derivation Path: 36.508 table 4.8.2.1.5-1
MAC-MainConfig ::=SEQUENCE {
periodicBSR-Timer sf32
}
phr-Config CHOICE {
setup SEQUENCE {
periodicPHR-Timer sf1000
}
}
}

Table 8.2.2.1.3.3-4: PhysicalConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-2)
PhysicalConfigDedicated ::=SEQUENCE {
pdsch-ConfigDedicated PDSCH-
ConfigDedicated-
RECONFIG

pucch-ConfigDedicated Not present
pusch-ConfigDedicated Not present
uplinkPowerControlDedicated Not present
tpc-PDCCH-ConfigPUCCH Not present
tpc-PDCCH-ConfigPUSCH Not present
cqi-ReportConfig Not present
soundingRsUL-ConfigDedicated Not present
antennaInfo CHOICE {
defaultValue NULL
}
schedulingRequestConfig Not present
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 728
728
Table 8.2.2.1.3.3-5: PDSCH-ConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-4)
PDSCH-ConfigDedicated ::=SEQUENCE {
p-a dB1
}

8.2.2.2 RRC connection reconfiguration / SRB/DRB reconfiguration / Success
(1)
with { UE in E-UTRA RRC_CONNECTED state}
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing SRB reconfiguration }
then { UE reconfigures affected SRBs and sends an RRCConnectionReconfigurationComplete message }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state}
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing DRB reconfiguration }
then { UE reconfigures affected DRBs and sends an RRCConnectionReconfigurationComplete message }
}
References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3,
5.3.10.1 and 5.3.10.3.
[TS 36.331, clause 5.3.5.3]

1>else:
3>perform the Radio resource configuration procedure as specified in 5.3.10;
[TS 36.331, clause 5.3.10.1]
The UE shall:

1>for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration (SRB
reconfiguration):
2>reconfigure the RLC entity in accordance with the received rlc-Config;
2>reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;
[TS 36.331, clause 5.3.10.3]
The UE shall:

1>for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration (DRB
reconfiguration):
2>if the pdcp-Config is included:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 729
729
3>reconfigure the PDCP entity in accordance with the received pdcp-Config;
2>if the rlc-Config is included:
3>reconfigure the RLC entity or entities in accordance with the received rlc-Config;
2>if the logicalChannelConfig is included:
3>reconfigure the DTCH logical channel in accordance with the received logicalChannelConfig;
NOTE: Removal and addition of the same drb-Identity in single radioResourceConfiguration is not supported.
8.2.2.2.3 Test Description
System Simulator:
- Cell 1
UE:
None.
Preamble:
U - S Message
RRConnectionReconfiguration message
containing a radioResourceConfigDedicated
with SRB reconfiguration.
message?
omplete
1 P
3 SS transmits RRCConnectionReconfiguration
message containing a
radioResourceConfigDedicated with DRB
reconfiguration.
message?
omplete
2 P

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 730
730
c1 CHOICE{
dicated-SRBRECONFIG

}
}
}
}

Table 8.2.2.2.3.3-2: RadioResourceConfigDedicated-SRBRECONFIG (Table 8.2.2.2.3.3-1)
srb-ToAddModList SRB-ToAddModList-
RECONFIG
TS 36.508 Table
4.6.3-22A

physicalConfigDedicated Not present
}

c1 CHOICE{
dicated-DRBRECONFIG

}
}
}
}

Table 8.2.2.2.3.3-4: RadioResourceConfigDedicated-DRBRECONFIG (Table 8.2.2.2.3.3-3)
drb-ToAddModList DRB-ToAddModList-
RECONFIG
TS 36.508 Table
4.6.3-2A

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 731
731
Table 8.2.2.2.3.3-5: (Void)
Table 8.2.2.2.3.3-6: (Void)

8.2.3 Radio bearer release
8.2.3.1 RRC connection reconfiguration / Radio bearer release / Success
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a drb-ToReleaseList }
then { for each drb-Identity release the PDCP entity and RLC entity and DTCH logical channel
and indicate release of the DRB(s) to upper layers }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clause 5.3.5.3
and 5.3.10.2.
[TS 36.331, clause 5.3.5.3]
2> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection

1>else:

[TS 36.331, clause 5.3.10.2]
The UE shall:
1>for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration (DRB
release):
2>release the PDCP entity;
2>release the RLC entity;
2>release the DTCH logical channel;
1>indicate the release of the DRB(s) and the eps-BearerIdentity of the released DRB(s) to upper layers;
System Simulator:
- Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 732
732
UE:
None.
Preamble:
U - S Message
RRCConnectionReconfiguration message with
a drb-ToReleaseList.
message?
omplete
1 P
2a The UE transmits an ULInformationTransfer
message.
- - 1 -

c1 CHOICE{
1 entry
DedicatedInfoNAS[1] DEACTIVATE EPS
BEARER CONTEXT
REQUEST with EPS
bearer identity
corresponding to drb-
Identity 2 and ESM
cause #36
According 36.508
table 4.7.3-12 and
regular
deactivation of a
second DRB

dicated-DRB-RELEASE
Table 8.2.3.1.3.3-
2

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 733
733
Table 8.2.3.1.3.3-2: RadioResourceConfigDedicated-DRB-RELEASE (Table 8.2.3.1.3.3-1)
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB))
OF
1 entry
drb-Identity[1] 2
mac-MainConfig CHOICE {} Not present
}

8.2.4 Handover
8.2.4.1 RRC connection reconfiguration / Handover / Success / Dedicated preamble
(1)
with { UE having completed the radio bearer establishment and initial security activation procedure
and performed the intra frequency measurement}
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo with a
rach-ConfigDedicated }
then { UE transmits an RRCConnectionReconfigurationComplete message }
}

(2)
and performed the intra frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a nextHopChainingCount which
is different from the NCC associated with the currently active K
eNB
}
then { UE derives new K
eNB
key from the nextHopChainingCount }
}
(3)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a nextHopChainingCount which
is same as the NCC associated with the currently active K
eNB
}
eNB
key from the currently active K
eNB
}
}

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4,
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1>start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;
1>if the carrierFreq is included:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 734
734
2>consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity
indicated by the targetPhysCellId;
1>else:
2>consider the target cell to be one on the current frequency with a physical cell identity indicated by the
targetPhysCellId;
1>start synchronising to the DL of the target cell;
NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message
triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this
message.
1>reset MAC;
1>re-establish PDCP for all RBs that are established;
NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the
re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling
of the SN and the HFN, is specified in TS 36.323 [8].
1>apply the value of the newUE-Identity as the C-RNTI;
1>configure lower layers in accordance with the received radioResourceConfigCommon;
1>configure lower layers in accordance with any additional fields, not covered in the previous, if included in the
received mobilityControlInfo;
1>if the keyChangeIndicator received in the securityConfigHO is set to TRUE:
2>update the K
eNB
key based on the fresh K
ASME
key taken into use with the previous successful NAS SMC
procedure, as specified in TS 33.401 [32];
1>else:
2>update the K
eNB
key based on the current K
eNB
or the NH, using the nextHopChainingCount value indicated
in the securityConfigHO, as specified in TS 33.401 [32];
1>store the nextHopChainingCount value;
1>if the securityAlgorithmConfig is included in the securityConfigHO:
2>derive the K
RRCint
key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];
2>derive the K
RRCenc
key and the K
UPenc
key associated with the cipheringAlgorithm, as specified in TS 33.401
[32];
1>else:
2>derive the K
RRCint
key associated with the current integrity algorithm, as specified in TS 33.401 [32];
2>derive the K
RRCenc
key and the K
UPenc
key associated with the current ciphering algorithm, as specified in TS
33.401 [32];
1>configure lower layers to apply the integrity protection algorithm and the K
RRCint
key, i.e. the integrity protection
configuration shall be applied to all subsequent messages received and sent by the UE, including the message
used to indicate the successful completion of the procedure;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 735
735
1>configure lower layers to apply the ciphering algorithm, the K
RRCenc
key and the K
UPenc
key, i.e. the ciphering
1>perform the measurement related actions as specified in 5.5.6.1;
1>if the RRCConnectionReconfiguration message includes the measConfig:
2>perform the measurement configuration procedure as specified in 5.5.2;
1>submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;
1>if MAC successfully completes the random access procedure:
2>stop timer T304;
2>apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS
configuration that do not require the UE to know the SFN of the target cell, if any;
2>apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN
of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding
RS configuration), if any, upon acquiring the SFN of the target cell;
NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it
applies the new configuration, except for the cases addressed by the above statements.
2>the procedure ends;
NOTE 4: The UE is not required to determine the SFN of the target cell by acquiring system information from that
cell before performing RACH access in the target cell.
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
1>if the antennaInfo is included and set to 'explicitValue':
2>if the configured transmissionMode is not 'tm3' or 'tm4' release ri-ConfigIndex in cqi-ReportPeriodic, if
previously configured;
1>else if the antennaInfo is included and set to 'defaultValue':
2>release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;
System Simulator:
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 736
736
columns marked "T1", "T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -91 Off
that measurement results for
Cell 1 (M1) and Cell 4 (M4)
satisfy exit condition for event
A3 (M4 <M1)(NOTE 1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79 Off
satisfy entry condition for event
A3 (M4 >M1)(NOTE 1).
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -91 "Off"
A3 (M1 >M4)(NOTE 1).
T3
Cell-specific RS
EPRE
dBm/15k
Hz
-85 Off -79
The power level value are such
A3 (M11 >M1).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 737
737
U - S Message
setup intra frequency measurement on Cell 1.
message on Cell 1.
omplete
- -
parameters according to the row "T1" in table
8.2.4.1.3.2-1.
- - - -
4 The UE transmits a MeasurementReport
message to report event A3 on Cell 1 with the
--> MeasurementReport - -
handover to Cell 4.
message on Cell 4 using dedicated preamble
to confirm the successful completion of the
intra frequency handover?
Check2: Does the UE transmit an
using the security key derived from the
currently active K
eNB
?
omplete
1,3 P
8.2.4.1.3.2-1.
- - - -
handover to Cell 1.
nextHopChainingCount?
omplete
1,2 P
11 The SS changes Cell 1 and Cell 11
parameters and switches Cell 4 off according
- - - -
measured RSRP,RSRQ value for Cell 11.
handover to Cell 11.
nextHopChainingCount?
omplete
1,2 P
14A The UE transmit a TRACKING AREA UPDATE - - - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 738
738
REQUEST message on Cell 11.
14B SS responds with a TRACKING AREA
UPDATE ACCEPT message.
- - - -
14C The UE transmits a TRACKING AREA
UPDATE COMPLETE message.
- - - -
- - 1 -

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.1.3.3-2: MeasConfig (Table 8.2.4.1.3.3-1)
MeasConfig ::=SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE
(1..maxObjectId)) OF SEQUENCE {
1 entry
measObjectId[1] IdMeasObject-f1
measObject[1] MeasObjectEUTRA-
GENERIC(f1)

}
reportConfigToAddModList SEQUENCE (SIZE
(1..maxReportConfigId)) OF SEQUENCE {
1 entry
reportConfigId[1] IdReportConfig-A3
reportConfig[1] ReportConfigEUTRA-A3
}
measIdToAddModList SEQUENCE (SIZE
(1..maxMeasId)) OF SEQUENCE {
1 entry
measId[1] 1
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 739
739
Table 8.2.4.1.3.3-3: MeasurementReport (step 4, Table 8.2.4.1.3.2-2)
MeasurementReport ::=SEQUENCE {
c1 CHOICE{
measurementReport-r8 SEQUENCE {
measResults SEQUENCE {
measId 1
measResultServCell SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultNeighCells CHOICE {
measResultListEUTRA SEQUENCE (SIZE
(1..maxCellReport)) OF SEQUENCE {
1 entry
physCellId[1] PhysicalCellIdentity of
Cell 4

cgi-Info[1] Not present
measResult[1] SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Table 8.2.4.1.3.3-5: MobilityControlInfo (Table 8.2.4.1.3.3-4)
Cell 4

ra-PreambleIndex 63
ra-PRACH-MaskIndex 0
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 740
740
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 1

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 1

ra-PreambleIndex 63 -
}
}

Table 8.2.4.1.3.3-9: SecurityConfigHO (step 9, Table 8.2.4.1.3.2-2)
SecurityConfigHO ::=SEQUENCE {
handoverType CHOICE {
intraLTE SEQUENCE {
nextHopChainingCount 1
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 741
741
c1 CHOICE{
measuredResults SEQUENCE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 11

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 11

ra-PreambleIndex 63
}
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 742
742
Table 8.2.4.1.3.3-13: SecurityConfigHO (Table 8.2.4.1.3.3-11)
intraLTE SEQUENCE {
}
}
}

8.2.4.2 RRC connection reconfiguration / Handover / Success / Common preamble
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo without
a rach-ConfigDedicated }
}

5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1>else:
targetPhysCellId;
message.
1>reset MAC;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 743
743
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc
2>stop timer T304;
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 744
744
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
UE:
None.
Preamble:
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -91
A3 (M2 <M1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79
A3 (M2 >M1).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 745
745
U - S Message
message on Cell 1.
omplete
- -
- - - -
Cell 1 to order the UE to perform intra
frequency handover to Cell 2.
message on Cell 2 using common preamble to
confirm the successful completion of the intra
frequency handover?
omplete
1 P
- - 1 -


MeasConfig SEQUENCE {
1 entry
GENERIC(f1)

}
1 entry
}
1 entry
measId[1] 1
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 746
746
Table 8.2.4.2.3.3-3 MeasurementReport (step 4, Table 8.2.4.2.3.2-2)
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 2

}

8.2.4.3 RRC connection reconfiguration / Handover / Success / Intra-cell / Security
reconfiguration
(1)
with { UE having completed the radio bearer establishment and initial security activation
procedure }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a securityConfigHO }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 747
747
[TS 36.331, clause 5.3.5.4]
If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the
1>if thecarrierFreq is included:
2>consider the target cell to be one on the frequency indicated by the eutra-CarrierFreq with a physical cell
identity indicated by the targetPhysCellId;
1>else:
targetPhysCellId;
message.
1>reset MAC;
1>applythe value of the newUE-Identity; as the C-RNTI
1> configure lower layers in accordance with the received radioResourceConfigCommon;
2>update the K
eNB
key based on the K
ASME
key taken into use with the previous successful NAS SMC procedure,
as specified in TS 33.401 [32];
1>else:
2>update the K
eNB
key based on the K
ASME
key to which the current K
eNB
is associated, using the
nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 748
748
RRCint
RRCenc
key and the K
UPenc
2>stop timer T304;
2>apply the parts of the configuration that do not require the UE to know the SFN of the target cell;
...
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 749
749
U - S Message
1 The SS transmits an AUTHENTICATION
REQUEST message to initiate the EPS
authentication and AKA procedure.
2 The UE transmits an AUTHENTICATION
RESPONSE message and re-establishes
mutual authentication.
3 The SS transmits a NAS SECURITY MODE
COMMAND message to reactivate NAS
security.
4 The UE transmits a NAS SECURITY MODE
COMPLETE message and re-establishes the
security configuration.
perform intra cell handover and security
reconfiguration.
message using the security key indicated by
the keyChangeIndicator and
nextHopChainingCount, as well as the
indicated algorithms, to confirm the successful
completion of the intra cell handover and
security reconfiguration?
omplete
1 P
- - 1 -


Cell 1

}

intraLTE SEQUENCE {
keyChangeIndicator TRUE
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 750
750
8.2.4.4 RRC connection reconfiguration / Handover / Failure / Intra-cell / Security
reconfiguration
(1)
and after receiving an RRCConnectionReconfiguration message including a SecurityConfigHO }
ensure that {
when { UE detects handover failure and the initial cell is selectable }
then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA
RRC_CONNECTED state }
}

5.3.5.4, 5.3.5.6, 5.3.7.4 and 5.3.7.5.
[TS 36.331, clause 5.3.5.3]
2>re-establish PDCP for SRB2 and for all DRBs that are established, if any;
2>re-establish RLC for SRB2 and for all DRBs that are established, if any;
2>resume SRB2 and all DRBs that are suspended, if any;

[TS 36.331, clause 5.3.5.4]
1>else:
targetPhysCellId;
message.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 751
751
1>reset MAC;
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc
2>stop timer T304;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 752
752

[TS 36.331, clause 5.3.5.6]
The UE shall:
1>if T304 expires (handover failure):
NOTE: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not
available for use by the UE anymore.
2>revert back to the configuration used in the source cell, excluding the configuration configured by the
physicalConfigDedicated, the mac-MainConfig and the sps-Config;
2>initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection
reconfiguration procedure ends;
[TS 36.331, clause 5.3.7.4]
The UE shall set the contents of RRCConnectionReestablishmentRequest message as follows:
2>set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used
in the cell in which the trigger for the re-establishment occurred (other cases);
2>set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA
failure) or of the cell in which the trigger for the re-establishment occurred (other cases);
2>set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:
3>over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;
3>with the K
RRCint
key and integrity protection algorithm that was used in the source cell (handover and
mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other
cases); and
3>with all input bits for COUNT, BEARER and DIRECTION set to binary ones;
1>set the reestablishmentCause as follows:
2>if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is
unable to comply with the reconfiguration):
3>set the reestablishmentCause to the value 'reconfigurationFailure';
2>else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE
handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):
3>set the reestablishmentCause to the value 'handoverFailure';
2>else:
3>set the reestablishmentCause to the value 'otherFailure';
The UE shall submit the RRCConnectionReestablishmentRequest message to lower layers for transmission.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 753
753
[TS 36.331, clause 5.3.7.5]
The UE shall:
1>stop timer T301;
1>re-establish PDCP for SRB1;
1>re-establish RLC for SRB1;
1>resume SRB1;
1>update the K
eNB
key based on the K
ASME
eNB
nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS
33.401 [32];
1>derive the K
RRCint
key associated with the previously configured integrity algorithm, as specified in TS 33.401
[32];
1>derive the K
RRCenc
key and the K
UPenc
key associated with the previously configured ciphering algorithm, as
specified in TS 33.401 [32];
1>configure lower layers to activate integrity protection using the previously configured algorithm and the K
RRCint

key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the
UE, including the message used to indicate the successful completion of the procedure;
1>configure lower layers to apply ciphering using the previously configured algorithm, the K
RRCenc
key and the
K
UPenc
key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE,
including the message used to indicate the successful completion of the procedure;
1>submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the
procedure ends;
System Simulator:
- Cell 1.
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 754
754
U - S Message
perform intra cell handover and security
reconfiguration.
described in step 2 the steps specified in Table
8.2.4.4.3.2-2 should take place.
- - - -
2 Wait for 1 s to ensure that T304 expires. - - - -
message?
Request
1 P
RRCConnectionReestablishment message to
resume SRB1 operation and reactivate
security.
message.
Complete
- -
resume the existing radio bearer.
message.
omplete
- -
indicates that the UE is in E-UTRA
- - 1 -

U - S Message
- EXCEPTION: The steps 1 and 2 below are
repeated for the duration of T304.
- - - -
1 The UE attempts to perform the intra cell
handover using MAC Random Access
Preamble.
- - - -
2 The SS does not respond. - - - -


Cell 1

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 755
755
intraLTE SEQUENCE {
}
}
}

SEQUENCE {

SEQUENCE {

of the UE

Cell 1

the XMAC-I value
calculated by SS.

}
reestablishmentCause handoverFailure
}
}
}

c1 CHOICE{
dicated-HO

}
}
}
}

8.2.4.5 RRC connection reconfiguration / Handover / All parameters included
(1)
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo is
provided with all parameters included }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 756
756
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1>else:
targetPhysCellId;
message.
1>reset MAC;
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 757
757
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc
2>stop timer T304;
...
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 758
758
System Simulator:
UE:
None.
Preamble:
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -91
A3 (M2 <M1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79
A3 (M2 >M1).

U - S Message
message on Cell 1 to confirm the setup of intra
frequency measurement.
omplete
- -
- - - -
measured RSRP and RSRQ values for Cell 2.
message on Cell 2 to confirm the successful
completion of the intra frequency handover?
omplete
1 P
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 759
759

1 entry
GENERIC(f1)

}
1 entry
}
1 entry
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 760
760

Cell 2

carrierFreq SEQUENCE {
dl-CarrierFreq Same downlink EARFCN
as used for Cell 2

ul-CarrierFreq Same uplink EARFCN as
used for Cell 2
FDD
ul-CarrierFreq Not present TDD
}
carrierBandwidth SEQUENCE {
dl-Bandwidth Same downlink system
bandwidth as used for
Cell 2

ul-Bandwidth Same uplink system
bandwidth as used for
Cell 2
FDD
ul-Bandwidth Not present TDD
}
additionalSpectrumEmission Same
additionalSpectrumEmis
sion as used for Cell 2

t304 ms1000
newUE-Identity SS arbitrarily selects a
value between 003CH
and FFF2H.

rach-ConfigCommon RACH-ConfigCommon-
DEFAULT

prach-Config PRACH-Config-
DEFAULT

pdsch-ConfigCommon PDSCH-ConfigCommon-
DEFAULT

pusch-ConfiCommon PUSCH-ConfigCommon-
DEFAULT

phich-Config PHICH-Config-DEFAULT
pucch-ConfigCommon PUCCH-ConfigCommon-
DEFAULT

soundingRS-UL-ConfigCommon SoundingRsUl-
ConfigCommon-
DEFAULT

uplinkPowerControlCommon UplinkPowerControlCom
mon-DEFAULT

antennaInfoCommon SEQUENCE {
antennaPortsCount an1
}
p-Max Not present
tdd-Config Not present FDD
TDD-Config-DEFAULT TDD
ul-CyclicPrefixLength len1
}
rach-ConfigDedicated Not present
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 761
761

8.2.4.6 RRC connection reconfiguration / Handover / Success / Inter-frequency
(1)
and performed the inter frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo
indicating a different E-UTRA frequency}
}

5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1>else:
targetPhysCellId;
message.
1>reset MAC;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 762
762
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc
2>stop timer T304;
...
[TS 36.331, clause 5.3.10.4]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 763
763
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
UE:
None.
Preamble:
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -97
A3 (M3 <M1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -73
A3 (M3 >M1).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 764
764
U - S Message
Cell 1 to setup inter frequency measurement.
message on Cell 1.
omplete
- -
- - - -
Cell 1 to order the UE to perform inter
completion of the inter frequency handover?
omplete
1 P
indicates that the UE is in E-UTRA
- - 1 -


Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ
2 entries
GENERIC(f1)

GENERIC(f2)

}
1 entry
}
1 entry
measId[1] 1
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 765
765
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 3

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 3

as used for Cell 3

ul-CarrierFreq Not present
}
}

8.2.4.7 RRC connection reconfiguration / Handover / Failure / Re-establishment
successful
(1)
and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo
indicating a different E-UTRA cell having attempted intra frequency handover }
ensure that {
when { UE detects handover failure and the initial cell is selectable }
then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 766
766
}
(2)
with { UE having transmitted an RRCConnectionReestablishmentRequest message }
ensure that {
when { UE receives an RRCConnectionReestablishment message with a nextHopChainingCount which is
different from the NCC associated with the currently active K
eNB
}
eNB
from the nextHopChainingCount }
}
(3)
with { UE having transmitted an RRCConnectionReestablishmentRequest message }
ensure that {
when { UE receives an RRCConnectionReestablishment message with a nextHopChainingCount which is
same as the NCC associated with the currently active K
eNB
}
eNB
from the currently active K
eNB
}
}

5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1>else:
targetPhysCellId;
message.
1>reset MAC;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 767
767
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc
2>stop timer T304;
...
[TS 36.331, clause 5.3.5.6]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 768
768
[TS 36.331, clause 5.3.7.2]
The UE shall only initiate the procedure when AS security has been activated. The UE initiates the procedure when one
of the following conditions is met:
...
1>upon handover failure, in accordance with 5.3.5.6; or
...
1>start timer T311;
1>suspend all RBs except SRB0;
1>reset MAC;
1>perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];
[TS 36.331, clause 5.3.7.4]
2>set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used
in the cell in which the trigger for the re-establishment occurred (other cases);
2>set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA
failure) or of the cell in which the trigger for the re-establishment occurred (other cases);
3>over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;
3>with the K
RRCint
key and integrity protection algorithm that was used in the source cell (handover and
mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other
cases); and
3>with all input bits for COUNT, BEARER and DIRECTION set to binary ones;
1>set the reestablishmentCause as follows:
2>if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is
unable to comply with the reconfiguration):
3>set the reestablishmentCause to the value 'reconfigurationFailure';
3>set the reestablishmentCause to the value 'handoverFailure';
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 769
769
...
[TS 36.331, clause 5.3.7.5]
The UE shall:
1>stop timer T301;
1>re-establish PDCP for SRB1;
1>re-establish RLC for SRB1;
1>resume SRB1;
1>update the K
eNB
key based on the K
ASME
eNB
nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS
33.401 [32];
1>derive the K
RRCint
key associated with the previously configured integrity algorithm, as specified in TS 33.401
[32];
1>derive the K
RRCenc
key and the K
UPenc
key associated with the previously configured ciphering algorithm, as
specified in TS 33.401 [32];
1>configure lower layers to activate integrity protection using the previously configured algorithm and the K
RRCint

key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the
UE, including the message used to indicate the successful completion of the procedure;
1>configure lower layers to apply ciphering using the previously configured algorithm, the K
RRCenc
key and the
K
UPenc
key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE,
including the message used to indicate the successful completion of the procedure;
1>submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the
procedure ends;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 770
770
System Simulator:
UE:
None.
Preamble:
columns marked "T1", "T2", "T3", "T4", "T5" and "T6" are to be applied subsequently. The exact instants on which
these values shall be applied are described in the texts in this clause.
T0
Cell-specific
RS EPRE
dBm/15kHz -85 -91 -91
measurement results for Cell 1 (M1) Cell
4 (M4) and Cell 11(M11) satisfy exit
condition for event A3 (M4 <M1 and M11
<M1).
T1
Cell-specific
RS EPRE
dBm/15kHz -85 -79 -91
Cell 4 (M4) satisfy entry condition for
event A3 (M4 >M1).
T2
Cell-specific
RS EPRE
dBm/15kHz "Off" -79 "Off"
The power level values are assigned to
satisfy SrxlevCell 1 <0 and SrxlevCell 11
<0 such that selecting Cell 4 is
guaranteed
(NOTE 1).
T3
Cell-specific
RS EPRE
dBm/15kHz -73 -79 "Off"
event A3 (M1>M4).
(NOTE 1).
T4
Cell-specific
RS EPRE
dBm/15kHz -73 "Off" "Off"
satisfy SrxlevCell 4 <0 and SrxlevCell 11
<0 such that selecting Cell 1 is
guaranteed.
(NOTE 1).
T5
Cell-specific
RS EPRE
dBm/15kHz -73 "Off" -67
event A3 (M11>M1).
(NOTE 1).
T6
Cell-specific
RS EPRE
dBm/15kHz "Off" "Off" -67
satisfy SrxlevCell 1 <0 and SrxlevCell 4 <
0 such that selecting Cell 11 is
guaranteed.
(NOTE 1).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 771
771
U - S Message
message on Cell 1.
omplete
- -
8.2.4.7.3.2-1.
- - - -
- - - -
8.2.4.7.3.2-1.
- - - -
message on Cell 4?
Request
1 P
resume SRB1 operation and re-activate
security on Cell 4.
message using the security key derived from
the currently active K
eNB
on Cell 4?
Complete
3 P
resume existing radio bearer on Cell 4.
message on Cell 4.
--> RRCConnectionReconfigurationtC
omplete
- -
8.2.4.7.3.2-1.
- - - -
described in step 15 the steps specified in
- - - -
8.2.4.7.3.2-1.
- - - -
message on Cell 1?
Request
1 P
security on Cell 1.
18 Check: Does the UE transmit an --> RRCConnectionReestablishment 2 P
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 772
772
the nextHopChainingCount on Cell 1?
Complete
message on Cell 1.
omplete
- -
8.2.4.7.3.2-1.
- - - -
described in step 24 the steps specified in
- - - -
8.2.4.7.3.2-1.
- - - -
message on Cell 11?
Request
1 P
security on Cell 11.
the nextHopChainingCount on Cell 11?
Complete
2 P
message on Cell 11.
omplete
- -
29A The UE transmit a TRACKING AREA UPDATE
- - - -
29B SS responds with TRACKING AREA UPDATE
ACCEPT message.
- - - -
29C The UE transmits a TRACKING AREA
UPDATE COMPLETE.
- - - -
- - 1 -

U - S Message
- - - -
1 The UE attempts to perform the intra
frequency handover using MAC Random
Access Preamble on Cell 4.
- - - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 773
773
U - S Message
- - - -
- - - -

U - S Message
- - - -
- - - -


1 entry
GENERIC(f1)

}
1 entry
}
1 entry
measId[1] 1
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 774
774
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 4

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 4

ra-PreambleIndex 63
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 775
775
SEQUENCE {

SEQUENCE {

of the UE

Cell 1

the XMAC-I value
calculated by SS.

}
}
}
}

Table 8.2.4.7.3.3-7: RRCConnectionReestablishment (step 8, Table 8.2.4.7.3.2-2)
RRCConnectionReestablishment ::=SEQUENCE {
c1 CHOICE{
rrcConnectionReestablishment-r8 SEQUENCE {
}
}
}
}

Table 8.2.4.7.3.3-8: RRCConnectionReconfiguration (step 10, step 19 and step 28, Table 8.2.4.7.3.2-2)
c1 CHOICE{
dicated-HO

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 776
776
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 1

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 1

ra-PreambleIndex 63
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 777
777
SEQUENCE {

SEQUENCE {

of the UE

Cell 4

the XMAC-I value
calculated by SS.

}
}
}
}

c1 CHOICE{
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 778
778
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 11

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 11

ra-PreambleIndex 63
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 779
779
SEQUENCE {

SEQUENCE {

of the UE

Cell 1

the XMAC-I value
calculated by SS.

}
}
}
}

c1 CHOICE{
}
}
}
}

8.2.4.8 RRC connection reconfiguration / Handover / Failure / Re-establishment
failure
(1)
and after receiving an RRCConnectionReconfiguration message including an IE
mobilityControlInformation indicating a different E-UTRA cell having attempted intra frequency
handover }
ensure that {
when { UE detects handover failure and fails an RRC connection re-establishment procedure }
then { UE enters the E-UTRA RRC_IDLE state and trigger TAU procedure in order to recover RRC
connection }
}
5.3.5.6, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.7 and 5.3.12.
[TS 36.331, clause 5.3.5.4]
...
If the RRCConnectionReconfiguration message includes the mobilityControlInformation and the UE is able to comply
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 780
780
1>start timer T304 with the timer value set to t304, as included in the mobilityControlInformation;
1>request PDCP to initiate the PDCP Re-establishment procedure for all RBs that are established;
NOTE 2: The handling of the radio bearers after the successful completion of the L2 re-establishment, e.g. the re-
transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of
the SN and the HFN, is specified in [8].
1>reset MAC and re-establish RLC for all RBs that are established;
1>If the RRCConnectionReconfiguration message includes the radioResourceConfiguration:
2>perform the Radio resource configuration procedure as specified in 5.3.10;
1>set the C-RNTI to the value of the newUE-Identity;
1>if the eutra-CarrierFreq is included:
2>consider the target cell to be one on the frequency indicated by the eutra-CarrierFreq with a physical cell
identity indicated by the targetCellIdentity;
1>else:
targetCellIdentity;
1>if the dl-Bandwidth is included:
2>for the target cell, apply the downlink bandwidth indicated by the dl-Bandwidth;
1>else:
2>for the target cell, apply the same downlink bandwidth as for the current cell;
1>if the ul-Bandwidth is included:
2>for the target cell, apply the uplink bandwidth indicated by the ul-Bandwidth;
1>else:
2>for the target cell, apply the same uplink bandwidth as for the current cell;
1>If the RRCConnectionReconfiguration message includes the securityConfiguration:
2>apply the AS-derived keys associated with the AS-base key indicated by the keyIndicator;
2>configure lower layers to apply the indicated integrity protection algorithm, i.e. the indicated integrity
protection configuration shall be applied to all subsequent messages received and sent by the UE in the target
cell, including the message used to indicate the successful completion of the procedure;
2>configure lower layers to apply the indicated ciphering algorithm, i.e. the indicated ciphering configuration
shall be applied to all subsequent messages received and sent by the UE in the target cell, including the
message used to indicate the successful completion of the procedure;
1>If the RRCConnectionReconfiguration message includes the measurementConfiguration:
2>perform the Measurement configuration procedure as specified in 5.5.2;
1>synchronise to the DL of the target cell;
configuration;
1>If MAC successfully completes the random access procedure:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 781
781
2>stop timer T304;
2>If the physicalConfigDedicated is included in the RRCConnectionReconfiguration message:
3>If the UE needs the SFN of the target cell to apply the PUCCH and Sounding RS configuration:
4>apply the new PUCCH and Sounding RS configuration upon acquiring the SFN of the target cell;
3>else:
4>apply the new PUCCH and Sounding RS configuration;
2>indicate to PDCP to complete the PDCP Re-establishment procedure for all DRBs that are established, if any;
2>the procedure ends.
...
[TS 36.331, clause 5.3.5.6]
The UE shall:
1>If T304 expires (handover failure):
NOTE 1: Following T304 expiry dedicated preambles, if provided within the rach-ConfigDedicated, are not
2>revert back to the configuration used in the source cell, excluding the physical layer configuration;
NOTE 2: The UE reverts to the RRC configuration as well as the layer 2 configuration (PDCP/RLC/MAC) used in
the source cell.
reconfiguration procedure ends.
[TS 36.331, clause 5.3.7.2]
The UE shall only initiate the procedure when security has been activated. The UE initiates the procedure when one of
the following conditions is met:
...
...
...
1>start timer T311;
1>request PDCP to initiate the PDCP Re-establishment procedure for all RBs that are established;
NOTE 1: The handling of the radio bearers after the successful completion of the L2 re-establishment, e.g. the re-
transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and
the HFN, is specified in [8].
1>select a suitable cell in accordance with the cell selection process as specified in [4];
[TS 36.331, clause 5.3.7.3]
...
2>initiate transmission of the RRCConnectionReestablishmentRequest message in accordance with 5.3.7.4;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 782
782
...
[TS 36.331, clause 5.3.7.4]
2>set the c-RNTI to the C-RNTI used in the source cell (handover failure case) or used in the cell in which the
trigger for the re-establishment occurred (other cases);
2>set the cellIdentity to the Physical layer identity of the source cell (handover failure case) or of the cell in
which the trigger for the re-establishment occurred (other cases);
3>over the concatenation of the ASN.1 encoded CellIdentity of the current cell, PhysicalCellIdentity of the
cell the UE was connected to prior to the failure and C-RNTI that the UE had in the cell it was connected
to prior to the failure;
3>with the integrity protection key and integrity protection algorithm that was used in the cell the UE was
connected to prior to the failure; and
3>with all input bits for COUNT, BEARER and DIRECTION set to binary ones.
1>set the IE reestablishmentCause as follows:
...
3>set the reestablishmentCause to the value handoverFailure;
...
[TS 36.331, clause 5.3.7.7]
Upon T311 expiry, the UE shall:
1>perform the actions upon moving from RRC_CONNECTED to RRC_IDLE as specified in 5.3.12.
...
[TS 36.331, clause 5.3.12]
Upon moving from RRC_CONNECTED to RRC_IDLE, the UE shall:
...
1>release all radio resources, including release of the RLC entity and the associated PDCP entity for all established
RBs;
1>indicate the release of the RRC connection to upper layers;
1>enter RRC_IDLE.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 783
783
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
T0 Cell-
specific RS
EPRE
dBm/15
kHz
-85 -91 The power level values are such that measurement
results for Cell 1 (M1) and Cell 2 (M2) satisfy entry
condition for event A3 (M1 >M2)
T1 Cell-
specific RS
EPRE
dBm/15
kHz
-85 -79 The power level values are such that measurement
results for Cell 1 (M1) and Cell 2 (M2) satisfy entry
condition for event A3 (M2 >M1)
T2 Cell-
specific RS
EPRE
dBm/15
kHz
-85 "Off" The power level values are such that Srxlev
Cell 1
>
Srxlev
Cell 2
and Srxlev
Cell 2
<0.(NOTE 1).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 784
784
U - S Message
message on Cell 1.
omplete
- -
- - - -
measured RSRP and RSRQ value for Cell 2.
- - - -
- - - -
message on Cell 1.
Request
- -
8 The SS does not respond to any
message and waits for 2s to ensure that T301
expires and the UE goes to RRC_IDLE state
on Cell 1.
- - - -
9-
13
The UE will perform TAU procedure based on
steps 1 to 5 of subclause 6.4.2.7 in TS 36.508
on Cell 1.
NOTE: The UE performs a TAU procedure due
to NAS signaling connection recovery.
- - - -
- - 1 -

U - S Message
repeated for the duration of T304
- - - -
Access Preamble on Cell 2
- - - -

Derivation path: 36.508 Table 4.6.1-8, condition MEAS

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 785
785
Table 8.2.4.8.3.3-1A: MeasConfig (Table 8.2.4.8.3.3-1)
1 entry
GENERIC(f1)

}
1 entry
}
1 entry
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Derivation path: 36.508 Table 4.6.1-8, condition HO

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 786
786
Table 8.2.4.8.3.3-3A: MobilityControlInfo (Table 8.2.4.8.3.3-4)
Cell 2

}

Table 8.2.4.8.3.3-4: Void

SEQUENCE {

SEQUENCE {

c-RNTI The value of the C-RNTI
of the UE.

Cell 1

the XMAC-I value
calculated by SS

}
}
}
}

8.2.4.9 RRC connection reconfiguration / Handover / Inter-band blind handover /
Success
(1)
procedure }
ensure that {
indicating an E-UTRA frequency on different frequency band }
}

5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 787
787
1>else:
targetPhysCellId;
message.
1>reset MAC;
...
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 788
788
2>stop timer T304;
...
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
System Simulator:
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 789
789
U - S Message
Cell 1 to order the UE to perform inter band
handover to Cell 10.
message on Cell 10?
omplete
1 P
- - 1 -


Cell 10

as used for Cell 10

}
}

8.2.4.10 RRC connection reconfiguration / Handover (between FDD and TDD)
(1)
and performed the inter frequency measurement in FDD mode}
ensure that {
when { UE receives an RRCConnectionReconfiguration message including an IE
mobilityControlInformation with TDD configuration parameters included }
}

(2)
and performed the inter frequency measurement in TDD mode}
ensure that {
when { UE receives an RRCConnectionReconfiguration message including an IE
mobilityControlInformation with FDD configuration parameters included }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 790
790
5.3.10.4 and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]
1>else:
targetPhysCellId;
message.
1>reset MAC;
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 791
791
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc
2>stop timer T304;
[TS 36.331, clause 5.3.10.4]
The UE shall:
[TS 36.331, clause 5.3.10.6]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 792
792
System Simulator:
- Cell 1 in FDD and Cell 10 in TDD
UE:
None.
Preamble:
U - S Message
including TDD-Config to order the UE to
perform inter band handover to Cell 10.
message on Cell 10?
omplete
1 P
3
Check: Does the test result of generic test
- - 1 -
without including TDD-Config to order the UE
to perform inter band handover to Cell 1.
message on Cell 1?
omplete
2 P
- - 2 -


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 793
793
MobilityControlInfo-HO ::=SEQUENCE {
targetPhysCellId PhysicalCellIdentity of Cell 10
dl-CarrierFreq Same downlink EARFCN as used
for Cell 10

}
dl-Bandwidth Same downlink system bandwidth
as used for Cell 10

ul-Bandwidth Not present
}
additionalSpectrumEmission as
used for Cell 10

tdd-Config TDD-Config-DEFAULT
}


targetPhysCellId PhysicalCellIdentity of Cell 1
dl-CarrierFreq Same downlink EARFCN as used
for Cell 1

ul-CarrierFreq Same uplink EARFCN as used for
Cell 1

}
dl-Bandwidth Same downlink system bandwidth
as used for Cell 1

ul-Bandwidth Same uplink system bandwidth as
used for Cell 1

}
additionalSpectrumEmission as
used for Cell 1

tdd-Config Not present
}

8.2.4.11 Void
8.2.4.12 RRC connection reconfiguration / Handover / Setup and release of MIMO
(1)
procedure }
ensure that {
indicating a cell with 2 antenna ports }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 794
794

(2)
procedure }
ensure that {
indicating a cell with 1 antenna port }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.4
and 5.3.10.6.
[TS 36.331, clause 5.3.5.4]

1>else:
targetPhysCellId;
message.
1>reset MAC;
of the SN and the HFN, is specified in TS 36.323.


1>else:
2>update the K
eNB
eNB
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 795
795

1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
RRCenc
key and the K
UPenc

2>stop timer T304;
[TS 36.331, clause 5.3.10.6]
The UE shall:
2>if the configured transmissionMode is not 'tm3' or 'tm4' or 'tm8':
2>if the configured transmissionMode is 'tm8' and pmi-RI-Report is not present:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 796
796
System Simulator:
- Cell 1 and Cell 2 (2 antenna ports MIMO)
UE:
None.
Preamble:
U - S Message
handover to Cell 2.
message on Cell 2?
omplete
1 P
3
- - 1 -
handover to Cell 1.
message on Cell 1?
omplete
2 P
- - 2 -


Cell 2

radioResourceConfigCommon RadioResourceConfigCo
mmon-DEFAULT

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 797
797
Table 8.2.4.12.3.3-3: RadioResourceConfigCommon (Table 8.2.4.12.3.3-2)
Derivation Path: 36.508, Table 4.6.3-13, condition 2TX


Cell 1

}

8.3 Measurement configuration control and reporting
8.3.1 Intra E-UTRAN measurements
8.3.1.1 Measurement configuration control and reporting / Intra E-UTRAN
measurements / Event A1
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A1 with event based
periodical reporting }
ensure that {
when { Serving cell becomes better than absolute threshold plus hysteresis }
then { UE sends MeasurementReport message at regular intervals while entering conditions for
event A1 are satisfied }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and periodical measurement reporting triggered by event A1
ongoing}
ensure that {
when { Serving cell becomes worse than absolute threshold minus hysteresis }
then { UE stops sending MeasurementReport message }
}
5.5.4.1, 5.5.4.2 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 798
798
The UE shall:
1>for each measId included in the measIdList within VarMeasConfig:

2>else:
...
3>if the corresponding measObject concerns EUTRA:
4>consider any neighbouring cell detected on the associated frequency to be applicable when the
concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for
this measId;
...
2>if the triggerType is set to event and if the entry condition applicable for this event, i.e. the event
corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one
or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for
this event within the VarMeasConfig, while the VarMeasReportList does not include an entry for this measId
(a first cell triggers the event):
3>include a measurement reporting entry within the VarMeasReportList for this measId;
3>set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;
3>include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;
3>initiate the measurement reporting procedure, as specified in 5.5.5;
or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering
taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the
event):
measId;
2>if the triggerType is set to event and if the leaving condition applicable for this event is fulfilled for one or
more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for
all measurements after layer 3 filtering taken during of timeToTrigger defined within the
VarMeasurementConfiguration for this event:
3>remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;
3>if reportOnLeave is set to TRUE for the corresponding reporting configuration:
3>if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:
4>remove the measurement reporting entry within the VarMeasReportList for this measId;
4>stop the periodical reporting timer for this measId, if running;

2>upon expiry of the periodical reporting timer for this measId:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 799
799

NOTE 2: The UE does not stop the periodical reporting with triggerType set to event or to periodical while the
corresponding measurement is not performed due to the serving cell RSRP being equal to or better than s-
Measure or due to the measurement gap not being setup.

[TS 36.331, clause 5.5.4.2]
The UE shall:
1>consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled;
1>consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled;
InequalityA1-1 (Entering condition)
Thresh Hys Ms >

InequalityA1-2 (Leaving condition)
Thresh Hys Ms < +

The variables in the formula are defined as follows:
Ms is the measurement result of the serving cell, not taking into account any offsets.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigEUTRA for this
event).
Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Hys is expressed in dB.
Thresh is expressed in the same unit as Ms.
[TS 36.331, clause 5.5.5]

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within
the MeasurementReport message as follows:
1>set the measId to the measurement identity that triggered the measurement reporting;
1>set the measResultServCell to include the quantities of serving cell;
1>if there is at least one applicable neighbouring cell to report:
...
1>increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;
1>stop the periodical reporting timer, if running;
1>if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the
reportAmount as defined within the corresponding reportConfigfor this measId;
2>start the periodical reporting timer with the value of reportInterval as defined within the reportConfig for this
measId;

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 800
800
1>submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.
System Simulator:
- Cell 1
Preamble:
Table 8.3.1.1.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test
execution. Row marked "T0" denotes the conditions after the preamble, while rows 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.3.1.1.3.2-1: Power levels
T0
Cell-specific RS
EPRE
dBm/15
kHz
-85 Power level is such that Ms + Hys < Thresh
T1
Cell-specific RS
EPRE
dBm/15
kHz
-59 Power level is such that entry condition for event
A1 is satisfied Ms Hys > Thresh
T2
Cell-specific RS
EPRE
dBm/15
kHz
-85 Power level is such that exit condition for event
A1 is satisfied Ms + Hys < Thresh
Note: The total test tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1)
and absolute UE measurement accuracy (TS 36.133 clause 9).

U - S Message
1 SS transmits an
including MeasConfig to setup intra LTE
measurement and reporting for event A1.
RCConnectionReconfigrationComplete
message.
omplete
- -
level according to row "T1" in table 8.3.1.1.3.2-
1.
- - - -
MeasurementReport message to report event
A1 with the measured RSRP and RSRQ value
for Cell 1?
--> MeasurementReport 1 P
- EXCEPTION: Step 5 below is repeated until 3
MeasurementReport messages are received
from the UE
- - - -
MeasurementReport message, with the
measured RSRP and RSRQ value for Cell 1?
1.
- - - -
7 Wait and ignore MeasurementReport
messages for 5 s to allow change of power
levels for Cell 1.
- - - -
8 Check: Does the UE attempt to transmit an
uplink message within the next 10s?
- - 2 F

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 801
801
Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 8.3.1.1.3.3-2: MeasConfig (step 1, Table 8.3.1.1.3.2-2)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-1
measConfig ::=SEQUENCE {
1 entry
GENERIC(f1)

}
1 entry
reportConfig[1] ReportConfig-A1-H
}
1 entry
measId[1] 1
}
}

Table 8.3.1.1.3.3-3: ReportConfig-A1-H (step 1, Table 8.3.1.1.3.2-2)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-4 ReportConfigEUTRA-A1(-72)
ReportConfigEUTRA ::=SEQUENCE {
triggerType CHOICE {
event SEQUENCE {
hysteresis 6 3dB
}
}
reportAmount infinity
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 802
802
Table 8.3.1.1.3.3-4: MeasurementReport (steps 4 and 5, Table 8.3.1.1.3.2-2)
Derivation path: 36.508 4.6.1 table 4.6.1-5
c1 CHOICE {
measResults ::=SEQUENCE {
measId 1
measResultServCell ::=SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultNeighCells CHOICE {} Not present
}
}
}
}
}

measurements / Event A2
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A2 with event based
periodical reporting }
ensure that {
when { Serving cell becomes worse than absolute threshold minus hysteresis }
then { UE sends MeasurementReport message at regular intervals while entering conditions for
event A2 are satisfied }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state and periodical meausurement reporting triggered by event A2
ongoing}
ensure that {
when { Serving cell becomes better than absolute threshold plus hysteresis }
then { UE stops sending MeasurementReport message }
}

5.5.4.1, 5.5.4.3 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 803
803

2>else:
3>if the corresponding measObject concerns EUTRA:
4>consider any neighbouring cell detected on the associated frequency to be applicable when the concerned
cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;
...
this event within the VarMeasConfig while the VarMeasReportList does not include a measurement reporting
entry for this measId (a first cell triggers the event):
measId;
event):
measId;
2> if the triggerType is set to event and if the leaving condition applicable for this event is fulfilled for one or
all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for
this event:
measId;


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 804
804

[TS 36.331, clause 5.5.4.3]
The UE shall:
InequalityA2-1 (Entering condition)
Thresh Hys Ms < +
InequalityA2-2 (Leaving condition)
Thresh Hys Ms >
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within the reportConfigEUTRA for this
event).
Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within the reportConfigEUTRA for
this event).
[TS 36.331, clause 5.5.5]

...
reportAmount as defined within the corresponding reportConfigfor this measId :
2>start the periodical reporting timer with the value of reportInterval as defined within the corresponding
reportConfig for this measId;
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 805
805
System Simulator:
- Cell 1
Preamble:
Table 8.3.1.2.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test
T0 -70 Power level is such that Ms > Thresh + Hys
T1
Cell-specific RS
EPRE
dBm/15
kHz
-96 Power level is such that entry condition for event
A2 is satisfied Ms + Hys < Thresh
T2

-70 Power level is such that exit condition for event
A2 is satisfied Ms > Thresh + Hys
Note: The total tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1) and
absolute UE measurement accuracy (TS 36.133 clause 9).

U - S Message
1 SS transmits an
including measConfig to setup intra LTE
message.
omplete
- -
1.
- - - -
A2 with the measured RSRP and RSRQ value
for Cell 1?
- EXCEPTION: Step 5 below is repeated until 3
MeasurementReport messages are received
from the UE
- - - -
MeasurementReport message, with the
measured RSRP and RSRQ value for Cell 1?
1.
- - - -
levels for Cell 1.
- - - -
uplink message within the next 10s?
- 2 F

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 806
806

1 entry
GENERIC(f1)

}
1 entry
}
1 entry
measId[1] 1
}
}

event SEQUENCE {
hysteresis 6 3 dB
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 807
807
Derivation path: 36.508 table clause 4.6.1 table 4.6.1-5
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}

measurements / Two simultaneous events A3 (intra and inter-frequency
measurements)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurements configured for two event A3 at the same
time}
ensure that {
when { Entry condition for event A3 is not met }
then { UE does not send MeasurementReport }
}
(2)
time}
ensure that {
when { Neighbour becomes offset better than serving }
then { UE sends MeasurementReport with correct measId for event A3 }
}

5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply
...
1>If the RRCConnectionReconfiguration message includes the measConfig:
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 808
808
2>if the corresponding reportConfig includes a purpose set to reportStrongestCellsForSON:
3>consider any neighbouring cell detected on the associated frequency to be applicable;
2>else if the corresponding reportConfig includes a purpose set to reportCGI:
3>consider any neighbouring cell detected on the associated frequency/ set of frequencies (GERAN) which
has a physical cell identity matching the value of the cellForWhichToReportCGI included in the
corresponding measObject within the VarMeasConfig to be applicable;
2>else:
3>if the corresponding measObject concerns E-UTRA:
this measId;
3>else if the corresponding measObject concerns UTRA or CDMA2000:
4>consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is
included in the cellsToAddModList defined within the VarMeasConfig for this measId (i.e. the cell is
included in the white-list);
3>else if the corresponding measObject concerns GERAN:
4>consider a neighbouring cell on the associated set of frequencies to be applicable when the concerned
cell matches the ncc-Permitted defined within the VarMeasConfig for this measId;
this event within the VarMeasConfig, while the VarMeasReportList does not include an measurement
reporting entry for this measId (a first cell triggers the event):
measId;
event):
measId;
this event:
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 809
809
2>if the purpose is included and set to reportStrongestCells or to reportStrongestCellsForSON and if a
(first) measurement result is available for one or more applicable cells:
NOTE 1: If the purpose is set to reportStrongestCells, the UE initiates a first measurement report immediately
after the quantity to be reported becomes available for at least either serving cell or one of the applicable
cells. If the purpose is set to reportStrongestCellsForSON, the UE initiates a first measurement report
when it has determined the strongest cells on the associated frequency.
2>if the purpose is included and set to reportCGI and if the UE acquired the information needed to set all
fields of cellGlobalId for the requested cell:
3>stop timer T321;
2>upon expiry of the T321 for this measId:
NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered and
periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].
[TS 36.331, clause 5.5.4.4]
The UE shall:
Inequality A3-1 (Entering condition)
Off Ocs Ofs Ms Hys Ocn Ofn Mn + + + > + +

Inequality A3-2 (Leaving condition)
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 810
810
Off Ocs Ofs Ms Hys Ocn Ofn Mn + + + < + + +

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the frequency of the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Ofs is the frequency specific offset of the serving frequency (i.e. offsetFreq as defined within measObjectEUTRA
corresponding to the serving frequency).
Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the serving frequency), and is set to zero if not configured for the serving cell.
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA for this event).
Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Ofs, Ocs, Hys, Off are expressed in dB.
[TS 36.331, clause 5.5.5]

MeasurementReport
UE EUTRAN

Figure 5.5.5-1: Measurement reporting

The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN.
2>set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with
the following:
3>if the triggerType is set to event:
4>include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this
measId;
3>else:
4>include the applicable cells for which the new measurement results became available since the last
periodical reporting or since the measurement was initiated or reset;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 811
811
NOTE: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency)
depends on the measurement configuration i.e. the reportInterval. The related performance requirements
are specified in TS 36.133 [16].
3>for each cell that is included in the measResultNeighCells, include the physCellId;
3>if the triggerType is set to event; or the purpose is set to reportStrongestCells or to
reportStrongestCellsForSON:
4>for each included cell, include the layer 3 filtered measured results in accordance with the
reportConfig for this measId, ordered as follows:
5>if the measObject associated with this measId concerns E-UTRA:
6>set the measResult to include the quantity(ies) indicated in the reportQuantity within the
concerned reportConfig in order of decreasing triggerQuantity, i.e. the best cell is included
first;
5>else:
6>set the measResult to the quantity as configured for the concerned RAT within the
quantityConfig in order of decreasing quantity, i.e. the best cell is included first;
3>else if the purpose is set to reportCGI:
4>if the mandatory present fields of the cellGlobalId for the cell indicated by the
cellForWhichToReportCGI in the associated measObject have been obtained:
5>include the cgi-Info containing all the fields that have been successfully acquired;
reportAmount as defined within the corresponding reportConfig for this measId:
1>else:
2>if the triggerType is set to periodical:
3>remove the entry within the VarMeasReportList for this measId;
3>remove this measId from the measIdList within VarMeasConfig;
1>if the measured results are for CDMA2000 HRPD:
2>set the preRegistrationStatusHRPD to the UEs CDMA2000 upper layers HRPD preRegistrationStatus;
1>if the measured results are for CDMA2000 1xRTT:
2>set the preRegistrationStatusHRPD to FALSE;
1>submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends;
System Simulator:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 812
812
UE:
None.
Preamble:
Table 8.3.1.3.3.2-1 illustrates the downlink power levels to be applied for Cell 1, Cell 2 and Cell 3 at various time
instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows 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.
(DL only)
Cell 3
(DL only)
Remark
T0 Cell-specific
RS EPRE
dBm/15kHz -85 -91 Off Power levels are such that entry condition for
event A3 (measId 1 & 2) is not satisfied:

T1 Cell-specific
RS EPRE
dBm/15kHz -85 -79 Off Power levels are such that entry condition for
event A3 (measId 1) is satisfied:

T2 Cell-specific
RS EPRE
dBm/15kHz -85 Off -73 Power levels are such that entry condition for
event A3 (measId 2) is satisfied:

U - S Message
1 SS transmits an
including MeasConfig to setup intra E-UTRAN
measurement and reporting for two event A3
(measId 1 and measId 2) (intra and inter
frequency measurement).
message.
omplete
- -
MeasurementReport message within the next
10s?
--> MeasurementReport 1 F
1.
- - - -
A3 (measId 1) with the measured RSRP value
for Cell 2?
1.
- - - -
7 Void - - - -
for Cell 3?

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 813
813

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1, condition INTER-FREQ
2 entries
GENERIC(f1)

GENERIC(f2)

}
1 entry
}
2 entries
measId[1] 1
measId[2] 2
}
}

Derivation path: 36.508 clause 4.6.6 table 4.6.6-6 ReportConfigEUTRA-A3
ReportConfigEUTRA-A3 ::=SEQUENCE {
event SEQUENCE {
timeToTrigger ms0
}
}
reportQuantity sameAsTriggerQuantity
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 814
814
c1 CHOICE {
measId 1
measResultServCell::=SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
MeasResultEUTRA ::=SEQUENCE (SIZE
Report Cell 2
physCellId physCellId of the Cell 2.
measResult SEQUENCE{
rsrpResult (0..97)
rsrqResult Not present
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 2
measResultServCell::=SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 3
physCellId physCellId of the Cell 3.
rsrpResult (0..97)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 815
815
measurements / Periodic reporting (intra and inter-frequency measurements)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for periodic reporting of intra
frequency cells and inter frequency cells on specified frequency }
ensure that {
when { The UE receives reference signal power for cells on the serving frequency and cells on the
frequency where measurements are configured }
then { UE sends MeasurementReport message at regular intervals for these cells }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and a MeasurementReport message for a configured periodic
measurement reporting of intra and inter frequency cells was sent }
ensure that {
when { A previously reported cell become unavailable or the UE receives reference signal power on
a reported frequency for a cell which was previously not reported }
then { UE sends MeasurementReport message at regular intervals for the available intra and inter
frequency cells }
}
(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting ongoing}
ensure that {
when { The UE receives a RRCConnectionReconfiguration message removing measIds for periodic
reporting }
then { UE stops sending MeasurementReport messages for these measIds }
}
5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.2.2]
The UE shall:
1>for each measId value included in the received measIdToRemoveList that is part of the current UE configuration
in varMeasConfig:
2>remove the entry with the matching measId from the measIdList within theVarMeasConfig;
2>remove the measurement reporting entry for this measId from the VarMeasReportList, if included;
2>stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;
[TS 36.331, clause 5.5.4.1]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 816
816

2>else:
this measId;


...
[TS 36.331, clause 5.5.5]

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measuredResults
within the MeasurementReport message as follows:
2>set the measResultsNeighCells to include the best neighbouring cells up to maxReportCells in accordance
with the following:
measId;
3>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 817
817
3>for each cell that is included in the measResultsNeighCells, include the physCellId;
first;

1>if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than to
reportAmount as defined corresponding reportConfig for this measId:
...
1>submit the MEASUREMENT REPORT message to lower layers for transmission, upon which the procedure
ends.
System Simulator:
- Cell 1, Cell 2, Cell 3, Cell 4 and Cell 6
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18] on Cell 1.
Table 8.3.1.4.3.2-1 illustrates the downlink power levels to be applied for the cells at various time instants of the test
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 818
818
(DL
only)
Cell 3
(DL
only)
Cell 4
(DL
only)
Cell 6
(DL
only)
Remark
T0 Cell-specific
RS EPRE
dBm/
15kH
z
-85 -91 -85 Off Off
T1 Cell-specific
RS EPRE
dBm/
15kH
z
-85 Off -85 -91 Off
T2 Cell-specific
RS EPRE
dBm/
15kH
z
-85 Off Off -91 -85

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 819
819
U - S Message
1 SS transmits an
measurements and periodical reporting for
intra and inter frequency cells.
message.
omplete
- -
- EXCEPTION: In parallel to events described in
step 3 the steps specified in table 8.3.1.4.3.2-3
and table 8.3.1.4.3.2-4 shall take place

3 Wait for 30 s to ensure that the UE performs a
periodical intra frequency reporting and a
periodical inter frequency reporting.
- - 1 -
4 SS sets the cell-specific reference signal levels
and switches Cell 2 Off and Cell 4 On
- - - -
messages for 5 s to allow for the switching of
cells.
- - - -
and table 8.3.1.4.3.2-5 shall take place.

- - 1, 2 -
and switches Cell 3 Off and Cell 6 On
- - - -
cells.
- - - -
steps 9 to 11 the steps specified in table
8.3.1.4.3.2-5 and table 8.3.1.4.3.2-6 shall take
place
- - - -
- - 1, 2 -
10 SS transmits an
including measConfig to remove measIds for
periodical reporting.
message
omplete
- -
uplink message for the next 10s?
- - 3 F

U - S Message
- EXCEPTION: After the 1st message is
received, step 1 below shall be repeated every
time the duration indicated in the IE
reportInterval has elapsed
- - - -
MeasurementReport message to perform
periodical intra frequency reporting for Cell 2?

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 820
820
U - S Message
reportInterval has elapsed.
- - - -
periodical inter frequency reporting for Cell 3?

NOTE1: Cell 2 may be included in the MeasurementReport due to UE averages power levels over a period of time.
U - S Message
- EXCEPTION: Step 1 below shall be repeated
every time the duration indicated in the IE
- - - -
periodical intra frequency reporting for Cell
4(NOTE1)?
--> MeasurementReport 1, 2 P

U - S Message

periodical inter frequency reporting for Cell
6(NOTE2)?

Table 8.3.1.4.3.3-1: RRCConnectionReconfiguration (step 1 and step 10, Table 8.3.1.4.3.2-2)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 821
821
Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ
3 entries
GENERIC(f1)

GENERIC(f2)

GENERIC(f3)

}
reportConfigToAddModiList SEQUENCE (SIZE
1 entry
reportConfigId[1] IdReportConfig-
PERIODICAL

reportConfig[1] ReportConfigEUTRA-
PERIODICAL

}
3 entries
measId[1] 1
PERIODICAL

measId[2] 2
PERIODICAL

measId[3] 3
PERIODICAL

}
}

Table 8.3.1.4.3.3-3 ReportConfigEUTRA-PERIODICAL (step 1, Table 8.3.1.4.3.2-2)
Derivation path: 36.508 table 4.6.6-7 ReportConfigEUTRA-PERIODICAL
ReportConfigEUTRA-PERIODICAL ::=SEQUENCE {
maxReportCells 2 Report Cell 2, Cell
3, Cell 4 or Cell 6

}

measIdToRemoveList SEQUENCE (SIZE
3 entries
MeasId[1] 1
MeasId[2] 2
MeasId[3] 3
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 822
822
Derivation Path: 36.508 clause 4.6.1 table 4.6.1-5
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListEUTRA ::=SEQUENCE (SIZE
Report Cell 2
physCellId [1] physicalCellIdentity-Cell2
measResult [1] SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 4
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 823
823
c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 3
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 6
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 824
824
measurements / Two simultaneous event A3 (intra-frequency measurements)
(1)
time}
ensure that {
when { Entry condition for event A3 is not met }
then { UE does not send MeasurementReport }
}
(2)
time}
ensure that {
then { UE sends MeasurementReport with correct measId for event A3 }
}
5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>else:
this measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 825
825
measId;
event):
measId;
this event:
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 826
826
3>stop timer T321;
[TS 36.331, clause 5.5.4.4]
The UE shall:


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 827
827
[TS 36.331, clause 5.5.5]

MeasurementReport
UE EUTRAN


the following:
measId;
3>else:
first;
5>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 828
828
4>if the mandatory present fields of the cellGlobalId for the cell indicated by the
1>else:
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 3) on Cell 1 according to [18]
Table 8.3.1.5.3.2-1 illustrates the downlink power levels to be applied for Cell 1 and Cell 2 at various time instants of
the test execution. Row marked "T0" denotes the conditions after the preamble, while rows 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.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 829
829
(DL
only)
Remark
T0 Cell-specific RS
EPRE
dBm/1
5kHz
-85 -110 Power levels are such that entry condition for event A3
(measId 1 & 2) is not satisfied:

T1 Cell-specific RS
EPRE
dBm/1
5kHz
(measId 1) is satisfied:

T2 Cell-specific RS
EPRE
dBm/1
5kHz
(measId 2) is satisfied:

U - S Message
1 SS transmits an
including MeasConfig to setup intra E-UTRAN
measurement and reporting for two event A3
(measId 1 and measId 2) with different
parameters.
RCConnectionReconfigurationComplete
message.
omplete
- -
10s?
1.
- - - -
for Cell 2?
1.
- - - -
for Cell 2?


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 830
830
1 entry
GENERIC(f1)

}
2 entries
reportConfigId[1] 1
reportConfig[1] ReportConfig-A3-
Lowerthreshold

reportConfigId[2] 2
reportConfig[2] ReportConfig-A3-
Higherthreshold

}
2 entries
measId[1] 1
reportConfigId[1] IdReportConfig-A3-
Lowerthreshold

measId[2] 2
reportConfigId[2] IdReportConfig-A3-
Higherthreshold

}
}

Table 8.3.1.5.3.3-3: ReportConfig-A3-Lowerthreshold (step 1, Table 8.3.1.5.3.2-2)
event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset -20 -10 dB
}
}
timeToTrigger ms0
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 831
831
Table 8.3.1.5.3.3-4: ReportConfig-A3-Higherthreshold (step 1, Table 8.3.1.5.3.2-2)
event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset 0 0 dB
}
}
timeToTrigger ms0
}
}
}

c1 CHOICE {
MeasResults ::=SEQUENCE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 2
physCellId PhysCellId of the Cell 2.
rsrpResult (0..97)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 832
832
c1 CHOICE {
MeasResults ::=SEQUENCE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 2
rsrpResult (0..97)
}
}
}
}
}
}
}
}

measurements / Two simultaneous events A2 and A3 (inter-frequency
measurements)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurements configured for event A2 and event A3 }
ensure that {
when { Serving becomes worse than threshold }
then { UE sends MeasurementReport for event A2 }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and measurements configured for event A2 and event A3 }
ensure that {
}
5.5.4.1, 5.5.4.3, 5.5.4.4 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 833
833
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>else:
4>if the ue-RxTxTimeDiffPeriodical, eventA1 or eventA2 is configured in the corresponding
reportConfig:
5>consider only the serving cell to be applicable;
4>else:
concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig
for this measId;

2>if the triggerType is set to 'event' and if the entry condition applicable for this event, i.e. the event
measId;
event):
measId;
2> if the triggerType is set to 'event' and if the leaving condition applicable for this event is fulfilled for one or
this event:
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 834
834
2>if the purpose is included and set to 'reportStrongestCells' or to 'reportStrongestCellsForSON' and if a (first)
measurement result is available for one or more applicable cells:
NOTE 1: If the purpose is set to 'reportStrongestCells', the UE initiates a first measurement report immediately
cells. If the purpose is set to 'reportStrongestCellsForSON', the UE initiates a first measurement report
2>if the purpose is included and set to 'reportCGI' and if the UE acquired the information needed to set all
fields of cgi-Info for the requested cell:
3>stop timer T321;
NOTE 2: The UE does not stop the periodical reporting with triggerType set to 'event' or to 'periodical' while the
NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered
and periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].
[TS 36.331, clause 5.5.4.3]
The UE shall:
Thresh Hys Ms < +

Thresh Hys Ms >

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 835
835
event).
[TS 36.331, clause 5.5.4.4]
The UE shall:


[TS 36.331, clause 5.5.5]
the following:
3>if the triggerType is set to 'event':
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 836
836
measId;
3>else:
3>if the triggerType is set to 'event'; or the purpose is set to 'reportStrongestCells' or to
'reportStrongestCellsForSON':
first;
5>else:
quantityConfig in order of either decreasing quantity for UTRA and GERAN or increasing
quantity for CDMA2000 pilotStrength, i.e. the best cell is included first;


System Simulator:
- Cell 1 and Cell 3
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 837
837
the test execution. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1"and "T2" are to
clause.
Table 8.3.1.6.3.2-1 : Power levels
(DL
only)
Remark
T0 Cell-specific RS
EPRE
dBm/1
5kHz
and event A3 is not satisfied:
Thresh Hys Ms >

AND

T1 Cell-specific RS
EPRE
dBm/1
5kHz
-93 -105 Power level of Cell 1 is such that entry condition for
event A2 is satisfied:
Thresh Hys Ms < +

AND
Power levels of Cell 1 and Cell 3 are such that entry
condition for event A3 is not satisfied:

T2 Cell-specific RS
EPRE
dBm/1
5kHz
-85 -73 Power levels are such that entry condition for event A3 is
satisfied:

U - S Message
1 SS transmits an
measurement and reporting for event A2 and
event A3 (inter frequency measurement)
RRCConnectionReconfigrationComplete
message.
omplete
- -
10s?
level according to row "T1" in table 8.3.1.6.32.-
1.
- - - -
A2 with the measured RSRP value for Cell 1?
level according to row "T2" in table 8.3.1.6.32.-
1.
- - - -


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 838
838
Derivation path: 36.508 clause 4.6.6 table 4.6.6-1, condition INTER-FREQ
2 entries
GENERIC(f1)

GENERIC(f2)

}
2 entries
reportConfig[1] ReportConfig-A2
}
2 entries
measId[1] 1
measId[2] 2
}
}

Table 8.3.1.6.3.3-3: ReportConfig-A2 (step 1, Table 8.3.1.6.3.2-2)
event SEQUENCE {
hysteresis 6 3 dB
}
}
}

event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset 0 0 dB
}
}
timeToTrigger ms0
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 839
839
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultEUTRA ::=SEQUENCE (SIZE
Report Cell 3
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultEUTRA ::=SEQUENCE (SIZE
Report Cell 3
rsrpResult (0..97)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 840
840
measurements / Blacklisting
(1)
with { UE in E-UTRA RRC_CONNECTED state and meausurement configured for event A3 reporting }
ensure that {
when { Blacklisted neighbour cell satisfies entry condition for event A3 }
then { It is not considered in event evaluation and UE does not send MeasurementReport message }
}

(2)
with { UE in E-UTRA RRC_CONNECTED state and meausurement reporting triggered by event A3 is ongoing}
ensure that {
when { Blacklisted neighbour cell satisfies entry condition for event A3 }
then { It is not considered in measurement reporting }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.5.1, 5.5.4.1,
and 5.5.5.
[TS 36.331, clause 5.5.1]
The UE reports measurement information in accordance with the measurement configuration as provided by E-UTRAN.
E-UTRAN provides the measurement configuration applicable for a UE in RRC_CONNECTED state by means of
dedicated signalling, i.e. using the RRCConnectionReconfiguration message.
...
- For intra-frequency and inter-frequency measurements a measurement object is a single E-UTRA carrier
frequency. Associated with this carrier frequency, E-UTRAN can configure a list of cell specific offsets and a
list of blacklisted cells. Blacklisted cells are not considered in event evaluation or measurement reporting.
...
[TS 36.331, clause 5.5.4.1]
The UE shall:

2>else:

3> if the corresponding measObject concerns EUTRA:
this measId;

corresponding with the eventId of the corresponding reportConfig within VarMeaConfig, is fulfilled for one
this event within the VarMeasConfig while the VarMeasReportList does not include a measurement reporting
entry for this measId (a first cell triggers the event):
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 841
841
measId;

event):
measId;

this event:
measId;
4> stop the periodical reporting timer for this measId, if running;

[TS 36.331, clause 5.5.5]

1>set the IE measId to the measurement identity that triggered the measurement reporting;
with the following:
measId;

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 842
842
4>for each included cell include the layer 3 filtered measured results in accordance with the
reportConfigList for this measId, ordered as follows:
6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the
first;
...

System Simulator:
- Cell 1, Cell 2 and Cell 4:
- Cell 1 is the serving cell
- Cell 2 and Cell 4 are intra-frequency neighbour cells
UE:
None.
Preamble:
Table 8.3.1.7.3.2-1 illustrates the downlink power levels to be applied for Cell 1, Cell 2 and Cell 4 at various time
instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows 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.3.1.7.3.2-1 : Power level
(DL only)
Cell 4
(DL only)
Remark
T0 -85 -97 -97 Power levels are such that that exit condition
for event A3 is satisfied for all cells (M2 + Hys
< M1 + Off and M4 + Hys < M1 + Off) with all
offset parameters set to 0 dB.
T1 Cell-specific
RS EPRE
dBm/
15kH
z
-85 -79 -97 Power level of Cell 2 is set such that
measurement results for Cell 1 (M1) and Cell 2
(M2) satisfy entry condition for event A3 (M2 -
Hys > M1 + Off).
T2 -85 -79 -79 Power level of Cell 4 is set such that
(M4) satisfy entry condition for event A3 (M4 -
Hys > M1 + Off).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 843
843
Table 8.3.1.7.3.2-2 : Main behaviour
U - S Message
1 SS transmits an
including measConfig to setup intraLTE
message.
omplete
- -
8.3.1.7.3.2.-1.
- - - -
4 Check: does the UE transmit a
MeasurementReport messages within the next
10s?
- MeasurementReport 1 F
8.3.1.7.3.2.-1.
- - - -
A3 with the measured RSRP values for Cell 1
and Cell 4 without Cell 2 results?
7 SS transmits an
including meastConfig to remove Cell 2 from
the blacklisted cell list.
message
omplete
- -
A3 with the measured RSRP values for Cell 1,
Cell 2 and Cell 4?


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 844
844
1 entry
GENERIC(f1)

}
1 entry
}
1 entry
measId[1] 1
}
}

Table 8.3.1.7.3.3-3; MeasObjectEUTRA-GENERIC (Table 8.3.1.7.3.3-2)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-3 MeasObjectEUTRA-GENERIC(f1)
MeasObjectEUTRA-GENERIC(f1) ::=SEQUENCE {
blackCellsToAddModList ::=SEQUENCE (SIZE
(1..maxCellMeas)) OF SEQUENCE {
1 entry Add Cell 2
cellIndex[1] 1
physCellIdRange[1] physicalCellIdentity-Cell2
}
}

Table 8.3.1.7.3.3-4: ReportConfig-A3 (Table 8.3.1.7.3.3-2)
maxReportCells 3 Report Cell 1, Cell
2 and Cell 4

reportInterval Not present
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 845
845
1 entry
GENERIC(f1)

}
}

Table 8.3.1.7.3.3-7: MeasObjectEUTRA-GENERIC (Table 8.3.1.7.3.3-6)
Derivation path: 36.508 clause 4.6.6 table 4.6.6-3 MeasObjectEUTRA-GENERIC(f1)
MeasObjectEUTRA-GENERIC(f1) ::=SEQUENCE {
blackCellsToRemoveList ::=SEQUENCE (SIZE
(1..maxCellMeas)) OF SEQUENCE {
1 entry Remove Cell 2
CellIndex[1] 1
}
}

c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 4
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 846
846
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 2 and
Cell 4

rsrpResult (0..97)
rsrqResult (0..34)
}
physCellId[2] physicalCellIdentity-Cell4
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

measurements / Handover / IE measurement configuration present
(1)
with { UE having completed the radio bearer establishment, initial security activation procedure and
performed the intra frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and a
measConfig for removing intra frequency measurement }
then { UE performs intra frequency handover and stops the intra frequency measurement }
}

5.5.2.2, 5.5.2.6 and 5.5.4.4.
[TS 36.331, clause 5.3.5.4]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 847
847
1>else:
targetPhysCellId;
message.
1>reset MAC;
2>update the K
eNB
ASME
1>else:
2>update the K
eNB
eNB
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
[32];
1>else:
2>derive the K
RRCint
2>derive the K
RRCenc
key and the K
UPenc
33.401 [32];
RRCint
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 848
848
RRCenc
key and the K
UPenc
2>stop timer T304;

[TS 36.331, clause 5.5.2.2]
The UE shall:
1>for each measId included in the received measIdToRemoveList that is part of the current UE configuration in
varMeasConfig:

[TS 36.331, clause 5.5.2.6]
The UE shall:
1>for each reportConfigId included in the received reportConfigToRemoveList that is part of the current UE
configuration in varMeasConfig:
2>removethe entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
2>remove all measId associated with the reportConfigId from the measIdList within the VarMeasConfig, if any;
2>if a measId is removed from the measIdList:
NOTE: The UE does not consider the message as erroneous if the reportConfigToRemoveList includes any
reportConfigId value that is not part of the current UE configuration.
[TS 36.331, clause 5.5.4.4]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 849
849


System Simulator:
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 850
850
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -91
measurement re85sults for Cell 1 (M1) and
A3 (M2 <M1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -79
A3 (M2 >M1).

U - S Message
message on Cell 1 to confirm the setup of intra
frequency measurement.
omplete
- -
- - - -
message on Cell 1 to report event A3.
a measConfig on Cell 1 for removing event A3
reporting, to order the UE to perform intra
message on Cell 2?
omplete
1 P
- - - -
MeasurementReport message on Cell 2 to
perform event A3 reporting during the next
30s?
- - 1 -


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 851
851
1 entry
GENERIC(f1)

}
1 entry
}
1 entry
measId[1] 1
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

measResult SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Derivation Path: 36.508, Table 4.6.1-8, condition HO and MEAS

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 852
852
measObjectToRemoveList SEQUENCE (SIZE (1..
maxObjectId)) OF SEQUENCE {
1 entry
}
reportConfigToRemoveList SEQUENCE (SIZE
1 entry
}
1 entry
measId[1] 1
}
}

Cell 2

}

measurements / Intra-frequency handover / IE measurement configuration
not present
(1)
performed the intra frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and not
including a measConfig }
then { UE performs intra frequency handover and continues the intra frequency measurement }
}
(2)
performed the inter frequency measurement }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and not
including a measConfig }
then { UE performs intra frequency handover and continues the inter frequency measurement after
the activation of the measurement gaps }
}

5.5.6.1.
[TS 36.331, clause 5.5.4.4]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 853
853


[TS 36.331, clause 5.5.6.1]
E-UTRAN applies the handover procedure as follows:
- when performing the handover procedure, as specified in 5.3.5.4, ensure that a measObjectId corresponding to
the handover target carrier frequency is configured as a result of the procedures described in this sub-clause and
in 5.3.5.4;
...
The UE shall:
2>if the triggerType is set to 'periodical':
3>remove this measId from the measIdList within VarMeasConfig:
1>if the procedure was triggered due to inter-frequency handover or successful re-establishment to an inter-
frequency cell, update the measId values in the measIdList within VarMeasConfig as follows:
2>if a measObjectId value corresponding to the target carrier frequency exists in the measObjectList within
VarMeasConfig:
3>for each measId value in the measIdList:
4>if the measId value is linked to the measObjectId value corresponding to the source carrier frequency:
5>link this measId value to the measObjectId value corresponding to the target carrier frequency;
4>else if the measId value is linked to the measObjectId value corresponding to the target carrier
frequency:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 854
854
5>link this measId value to the measObjectId value corresponding to the source carrier frequency;
2>else:
3>remove all measId values that are linked to the measObjectId value corresponding to the source carrier
frequency;
1>remove all measurement reporting entries within VarMeasReportList;
1>reset the periodical reporting timer or timer T321, whichever one is running, as well as associated information
(e.g. timeToTrigger) for all measId;
1>release the measurement gaps, if activated;
NOTE: If the UE requires measurement gaps to perform inter-frequency or inter-RAT measurements, the UE
resumes the inter-frequency and inter-RAT measurements after the E-UTRAN has setup the measurement
gaps.
System Simulator:
UE:
None.
Preamble:
columns marked "T1", "T2","T3" and "T4" are to be applied subsequently. The exact instants on which these values
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 855
855
(DL
only)
Remark
T0
Cell-specific
RS EPRE
dBm/15k
Hz
-85 "Off" -97
(M3) do not satisfy entry condition for event A3
(M3 <M1).
(NOTE 1)
T1
Cell-specific
RS EPRE
dBm/15k
Hz
-85 "Off" -73
(M3) satisfy entry condition for event A3 (M3 >
M1).
(NOTE 1)
T2
Cell-specific
RS EPRE
dBm/15k
Hz
-85 -79 "Off"
M1).
(NOTE 1)
T3
Cell-specific
RS EPRE
dBm/15k
Hz
"Off" -85 -73
M2).
(NOTE 1)
T4
Cell-specific
RS EPRE
dBm/15k
Hz
-79 -85 "Off"
M2).
(NOTE 1)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 856
856
U - S Message
setup intra and inter frequency measurements
on Cell 1.
message to confirm the setup of intra and inter
frequency measurements on Cell 1.
omplete
- -
- EXCEPTION: Steps 3a1 to 3a2 describe
behaviour that depends on the UE capability;
sequence that takes place if a capability is
supported.
- - - -
3a1 IF pc_FeatrGrp_25 THEN the SS changes Cell
1, Cell 2 and Cell 3 parameters according to
the row "T1" in table 8.3.1.9.3.2-1.
- - - -
3a2 The UE transmits a MeasurementReport
message on Cell 1 to report event A3 for Cell
3.
8.3.1.9.3.2-1.
- - - -
2.
without a measConfig message on Cell 1, to
handover to Cell 2.
message on Cell 2?
omplete
1 P
supported.
- - - -
8a1 IF pc_FeatrGrp_25 THEN the SS transmits an
activate the measurement gaps on Cell 2.
message to confirm the activation of the
measurement gaps on Cell 2.
omplete
- -
8a3 The SS changes Cell 1, Cell 2 and Cell 3
8.3.1.9.3.2-1.
- - - -
8a4 Check: Does the UE transmit a
report event A3 for Cell 3?
8.3.1.9.3.2-1.
- - - -
- - 1,2 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 857
857

1entry or 2 entries number of entry
depending on the
UE capability

GENERIC(f1)

measObjectId[2] IdMeasObject-f2 pc_FeatrGr
p_25
GENERIC(f2)
pc_FeatrGr
p_25
}
1 entry
}
1entry or 2 entries number of entry
depending on the
UE capability

measId[1] 1 Intra frequency
measId[2] 2 Inter frequency pc_FeatrGr
p_25
p_25
reportConfigId[2] IdReportConfig-A3 pc_FeatrGr
p_25
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 858
858
Table 8.3.1.9.3.3-3: MeasurementReport (step 3a2 and 8a4, Table 8.3.1.9.3.2-2)
c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 3

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 859
859

Cell 2

}

Table 8.3.1.9.3.3-7: RRCConnectionReconfiguration (step 8a1, Table 8.3.1.9.3.2-2)


c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 1

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 860
860
measurements / Inter-frequency handover / IE measurement configuration
not present
(1)
performed the intra frequency and inter frequency measurements }
ensure that {
indicating a different E-UTRA frequency and not including a measConfig }
then { UE performs inter frequency handover, continues the intra frequency measurement and
continues inter frequency measurement after the activation of the measurement gaps }
}
[TS 36.331, clause 5.5.6.1]
E-UTRAN applies the handover procedure as follows:
- when performing the handover procedure, as specified in 5.3.5.4, ensure that a measObjectId corresponding to
the handover target carrier frequency is configured as a result of the procedures described in this subclause and
in 5.3.5.4;
...
The UE shall:
VarMeasConfig
5>link this measId value to the measObjectId value corresponding to the target carrierfrequency;
frequency:
2>else:
frequency;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 861
861
gaps.
System Simulator:
- Cell 1, Cell 2, Cell 3 and Cell 12.
UE:
None.
Preamble:
columns marked "T1", "T2","T3", and "T4" are to be applied subsequently. The exact instants on which these values
(DL
only)
Cell 3 Cell 12
(DL
only)
Remark
T0
Cell-specific RS
EPRE
dBm/15
kHz
-85 -91 -97 "Off"
that measurement results for Cell 1
(M1) and Cell 2 (M2) do not satisfy
entry condition for event A3 (M2 <
M1).
(NOTE 1).
T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 -79 -97 "Off"
(M1) and Cell 2 (M2) satisfy entry
condition for event A3 (M2 >M1).
(NOTE 1).
T2
Cell-specific RS
EPRE
dBm/15
kHz
-85 "Off" -73 "Off"
(NOTE 1).
T3
Cell-specific RS
EPRE
dBm/15
kHz
-97 "Off" -85 -79
(NOTE 1).
T4
Cell-specific RS
EPRE
dBm/15
kHz
-73 "Off" -85 "Off"
(NOTE 1).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 862
862
U - S Message
on Cell 1.
omplete
- -
3 The SS changes the cell-specific reference
signal levels of Cell 2 according to the row "T1"
in table 8.3.1.10.3.2-1.
- - - -
message on Cell 1 to perform event A3 intra
frequency reporting for Cell 2 during the next
30 s.
- MeasurementReport - -
5 The SS changesthe cell-specific reference
signal levels of Cell 3 and switches "Off" Cell 2
- - - -
message on Cell 1 to perform event A3 inter
frequency reporting for Cell 3 during the next
30 s.
without a measConfig, to order the UE to
perform inter frequency handover to Cell 3.
message to Cell 3?
omplete
1 P
omplete
- -
signal levels of Cell 1 and Cell 3 and switches
"On" Cell 12 according to the row "T3" in table
8.3.1.10.3.2-1.
- - - -
perform event A3 intra frequency reporting for
Cell 12 during the next 30 s?
signal levels of Cell 1 and switches Cell 12 off
- - - -
perform event A3 inter frequency reporting for
Cell 1 during the next 30 s?
- - 1 -


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 863
863
2 entries
GENERIC(f1)

GENERIC(f2)

}
1 entry
}
2 entries
measId[1] 1
measId[2] 2
}
}

Table 8.3.1.10.3.3-3: Void
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 864
864
c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 3

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


Cell 3

carrierFreq Same DL EARFCN as
used for Cell 3

}



Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 865
865
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 12

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 1

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 866
866
measurements / Continuation of the measurements after RRC connection re-
establishment
(1)
performed the intra frequency measurement and after receiving an RRCConnectionReconfiguration
message including a mobilityControlInfo indicating a different E-UTRA cell having attempted intra
frequency handover}
ensure that {
when { UE detects handover failure and the intra frequency cell is selectable }
then {UE performs RRC Connection Re-establishment, continues the intra frequency measurement }
}

(2)
performed the inter frequency measurement and after receiving an RRCConnectionReconfiguration
message including a mobilityControlInfo indicating a different E-UTRA cell having attempted intra
frequency handover}
ensure that {
when { UE detects handover failure and the intra frequency cell is selectable }
then {UE performs RRC Connection Re-establishment, continues the inter frequency measurement
after the activation of the measurement gaps }
}

5.3.5.6, 5.3.7.2 and 5.5.6.1.
[TS 36.331,clause 5.3.5.4]
1>else:
targetPhysCellId;
message.
1>reset MAC;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 867
867

2>stop timer T304;
[TS 36.331,clause 5.3.5.6]
The UE shall:
[TS 36.331,clause 5.3.7.2]
1>upon detecting radio link failure, in accordance with 5.3.11; or
1>upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or
1>upon integrity check failure indication from lower layers; or
1>upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5;
1>start timer T311;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 868
868
1>reset MAC;
[TS 36.331,clause 5.5.6.1]
E-UTRAN applies the re-establishment procedure as follows:
- when performing the connection re-establishment procedure, as specified in 5.3.7, ensure that a measObjectId
corresponding to the target carrier frequency is configured as a result of the procedure described in this sub-
clause and the subsequent connection reconfiguration procedure immediately following the re-establishment
procedure;
The UE shall:
VarMeasConfig:
5>link this measId value to the measObjectId value corresponding to the target carrier frequency;
frequency:
2>else:
frequency;
gaps.
System Simulator:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 869
869
UE:
None.
Preamble:
columns marked "T1", "T2","T3", "T4", "T5" are to be applied subsequently. The exact instants on which these values
Table 8.3.1.11.3.2-1: Time instances of cell power levels
(DL
only)
Remark
T0
Cell-specific RS
EPRE
dBm/15
kHz
-85 off off

T1
Cell-specific RS
EPRE
dBm/15
kHz
-85 off -73
condition for event A3 (M3 - Hys >
M1).
T2
Cell-specific RS
EPRE
dBm/15
kHz
-85 -79 off
M1).
T3
Cell-specific RS
EPRE
dBm/15
kHz
off -79 off
assigned values to satisfy
SrxlevCell 1 <0 and SrxlevCell 3 <
0 such that selecting Cell 2 is
guaranteed
T4
Cell-specific RS
EPRE
dBm/15
kHz
-79 -85 off
M2).
T5
Cell-specific RS
EPRE
dBm/15
kHz
off -85 -73
M2).

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 870
870
U - S Message
on Cell 1.
omplete
- -
supported.
- - - -
3a1 IF pc_FeatrGrp_25 THEN the SS changes Cell
3 power levels according to the row "T1" in
Table 8.3.1.11.3.2-1.
- - - -
3a2 The UE transmits a MeasurementReport
3.
4 The SS changes Cell 2 and Cell 3 power levels
according to the row "T2" in Table
8.3.1.11.3.2-1.
- - - -
message on Cell 1 to perform event A3 intra
frequency reporting for Cell 2.
including a mobilityControlInfo, to order the UE
to perform intra frequency handover to Cell 2.
- - - -
7 The SS changes Cell 1 power levels according
to the row "T3" in Table 8.3.1.11.3.2-1.
- - - -
message on Cell 2?
--> RRCConnectionReestablishmentR
equest
1,2 P
security on Cell 2.
message on Cell 2.
--> RRCConnectionReestablishmentC
omplete
- -
message on Cell 2.
omplete
- -
13 The SS changes Cell 1 and Cell 2 power levels
8.3.1.11.3.2-1.
- - - -
perform event A3 intra frequency reporting for
Cell 1?
supported.
- - - -
15a1 IF pc_FeatrGrp_25 THEN the SS transmits an
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 871
871
omplete
- -
15a3 The SS changes Cell 1 and Cell 3 power levels
8.3.1.11.3.2-1.
- - - -
15a4 Check: Does the UE transmit a
test procedure in 36.508 subclause 6.2,4.3
- - 1,2 -

U - S Message
- - - -
- - - -


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 872
872
2 entries
GENERIC(f1)

p_25
GENERIC(f2)
pc_FeatrGr
p_25
}
1 entry
}
2 entries
measId[1] 1
measId[2] 2 pc_FeatrGr
p_25
p_25
reportConfigId[2] IdReportConfig-A3 pc_FeatrGr
p_25
}
}

Derivation path: 36.508 clause 4.6.6 Table 4.6.6-6 ReportConfigEUTRA-A3
reportAmount r1
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 873
873
Table 8.3.1.11.3.3-4: MeasurementReport (step 3a2,Table 8.3.1.11.3.2-2)
c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 3

rsrpResult (0..97)
}
}
}
}
}
}
}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

rsrpResult (0..97)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 874
874
Table 8.3.1.11.3.3-6: RRCConnectionReconfiguration (step 6,Table 8.3.1.11.3.2-2)

Table 8.3.1.11.3.3-7: MobilityControlInfo (step 6, Table 8.1.3.11.3.2-2)
Cell 2

}

SEQUENCE {

SEQUENCE {

of the UE

Cell 2

the XMAC-I value
calculated by SS.

}
}
}
}

c1 CHOICE{
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 875
875
c1 CHOICE{
dicated-HO

}
}
}
}

Table 8.3.1.11.3.3-11: MeasurementReport (step 14,Table 8.3.1.11.3.2-2)
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 1

rsrpResult (0..97)
}
}
}
}
}
}
}
}

Table 8.3.1.11.3.3-12: RRCConnectionReconfiguration (step 15a1,Table 8.3.1.11.3.2-2)
Derivation Path: 36.508, Table 4.6.1-8 condition MEAS

Table 8.3.1.11.3.3-13: MeasConfig (step 15a1,Table 8.3.1.11.3.2-2)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 876
876
Table 8.3.1.11.3.3-14: MeasurementReport (step 15a4, Table 8.3.1.11.3.2-2)
c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 3

rsrpResult (0..97)
}
}
}
}
}
}
}
}

8.3.2 Inter-RAT measurements
8.3.2.1 Measurement configuration control and reporting / Inter-RAT measurements /
Event B2 / Measurement of GERAN cells
(1)
performed the inter RAT measurement for GERAN cell and not detected entering condition for the event
B2 is met }
ensure that {
when { UE detects entering condition for the event B2 is not met }
then { UE does not transmit any MeasurementReport }
}
(2)
B2 is met }
ensure that {
when { UE detects entering condition for the event B2 is met }
then { UE transmits a MeasurementReport }
}
(3)
performed the inter RAT measurement for GERAN cell and detected entering condition for the event B2
is met }
ensure that {
when { UE detects leaving condition for the event B2 is met }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 877
877
5.5.4.8 and 5.5.5.
[TS 36.331, clause 5.5.4.1]
The UE shall:

2>else:

measId;
event):
measId;
this event:
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 878
878

[TS 36.331, clause 5.5.4.8]
The UE shall:
1>for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;
1>consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as
specified below, are fulfilled;
1>consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least
one of the two, as specified below, is fulfilled;
Inequality B2-1 (Entering condition 1)
1 Thresh Hys Ms < +

2 Thresh Hys Ofn Mn > +

Inequality B2-3 (Leaving condition 1)
1 Thresh Hys Ms >

2 Thresh Hys Ofn Mn < + +

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell (i.e. offsetFreq as defined
within the measObject corresponding to the frequency of the inter-RAT neighbour cell).
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 879
879
Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRAT for
this event).
this event).
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.
Ofn, Hys are expressed in dB.
Thresh1 is expressed in the same unit as Ms.
Thresh2 is expressed in the same unit as Mn.
[TS 36.331, clause 5.5.5]
with the following:
measId;
3>else:
first;
5>else:

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 880
880

System Simulator:
UE:
None.
Preamble:
columns marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
that entering conditions for event B2
are not satisfied. RSSI dBm - [-85]
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-80 -
are satisfied. RSSI dBm - [-65]
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
that leaving conditions for event B2
are satisfied. RSSI dBm - [-85]

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 881
881
U - S Message
setup inter RAT measurement on Cell 1.
message to confirm the setup of inter RAT
measurement on Cell 1.
omplete
- -
MeasurementReport message to report the
event B2 during the next 10s?
8.3.2.1.3.2-1.
- - - -
event B2 for Cell 24?
8.3.2.1.3.2-1.
- - - -
levels for Cells 1 and Cell 24.
- - - -
- - 1, 2,
3
-


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 882
882
Derivation Path: 36.508, Table 4.6.6-1, condition GERAN
1 entry
measObject[1] MeasObjectGERAN-
GENERIC(f11)

}
1 entry
reportConfigId[1] IdReportConfig-B2-
GERAN

reportConfig[1] ReportConfigInterRAT-
B2-GERAN(-69, [-79])

}
1 entry
measId[1] 1
GERAN

}
quantityConfig SEQUENCE {
quantityConfigGERAN SEQUENCE {
measQuantityGERAN rssi
filterCoefficient fc0
}
}
}

Table 8.3.2.1.3.3-2A: ReportConfigInterRAT-B2-GERAN (Table 8.3.2.1.3.3-2)
Derivation path: 36.508, Table 4.6.6-7E ReportConfigInterRAT-B2-GERAN(-69, [-79])
ReportConfigInterRAT-B2-GERAN ::=SEQUENCE {
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 883
883
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultsNeighCells CHOICE {
measResultListGERAN SEQUENCE (SIZE
1 entry
carrierFreq[1] SEQUENCE {
arfcn Not checked
bandIndicator Not checked
}
Cell 24

cgi-info[1] Not present
rssi (0..63)
}
}
}
}
}
}
}
}

Periodic reporting / Measurement of GERAN cells
(1)
performed the inter RAT measurement for GERAN cell }
ensure that {
when { The UE receives reference signal power for cells on the GERAN frequencies where
measurements are configured }
then { UE sends MeasurementReport message at regular intervals for these GERAN cells }
}

(2)
measurement reporting of GERAN cells on a configured frequency were sent }
ensure that {
when { A previously reported cell become unavailable and the UE receives reference signal power on
a reported GERAN frequency for a cell which was previously not reported }
then { UE sends MeasurementReport message at regular intervals for the available GERAN cells }
}

(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting of GERAN cells ongoing }
ensure that {
when { The UE receives a RRCConnectionReconfiguration message removing the measId of periodic
reporting of GERAN cells }
then { UE stops sending MeasurementReport message for GERAN cells }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 884
884
}

5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]

2> perform the measurement configuration procedure as specified in 5.5.2;
[TS 36.331, clause 5.5.2.2]
The UE shall:
varMeasConfig:
NOTE: The UE does not consider the message as erroneous if the measIdToRemoveList includes any measId
value that is not part of the current UE configuration.
[TS 36.331, clause 5.5.4.1]
The UE shall:

2>else:


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 885
885

[TS 36.331, clause 5.5.5]
the following:
...
3>else:
first;
5>else:
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 886
886
1>else:
...
System Simulator:
UE:
None.
Preamble:
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
that camping on Cell 1 is guarantee.
RSSI dBm - Off Off
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
that Cell 25 is satisfied for periodic
reporting. RSSI dBm - [-70] Off
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
reporting and Cell 25 become
unavailable.
RSSI dBm - Off [-70]

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 887
887
U - S Message
setup inter-RAT measurement.
message to confirm the setup of inter-RAT
measurement.
omplete
- -
3 The SS power "On" Cell 25 according to the
row "T1" in table 8.3.2.2.3.2-1.
- - - -
messages for 5s to allow power "On" for Cell
25.
- - - -
8.3.2.2.3.2-3 shall take place
- - - -
inter-RAT periodical reporting.
- - - -
6 The SS power "Off" Cell 25 and power "On"
Cell 26 according to the row "T2" in table
8.3.2.2.3.2-1.
- - - -
messages for 5s to allow power "Off" and
power "On" for Cell 25 and Cell 26
respectively.
- - - -
- - - -
- - - -
remove inter-RAT measurement.
message to confirm the remove of inter-RAT
measurement.
omplete
- -
- - 3 F

U - S Message
- - - -
periodical reporting for Cell 25?

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 888
888
U - S Message
- - - -
periodical reporting for Cell 26(NOTE1)?


2 entries
GENERIC(f12)

GENERIC(f13)

}
1 entry
reportConfigId[1] IdReportConfigInterRAT -
PERIODICAL

PERIODICAL

}
2 entries
measId[1] 1
PERIODICAL

measId[2] 2
PERIODICAL

}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 889
889
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
arfcn Not checked
}
Cell 25

rssi (0..63)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 890
890
c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
arfcn Not checked
}
Cell 26

rssi (0..63)
}
}
}
}
}
}
}
}


2 entries
measId[1] 1
measId[2] 2
}
}

Event B2 / Measurement of UTRAN cells
(1)
performed the inter RAT measurement for UTRA cell and not detected entering condition for the event
B2 is met }
ensure that {
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 891
891
}
(2)
performed the inter RAT measurement for UTRA cell and not detected entering condition for the event
B2 is met }
ensure that {
}
(3)
performed the inter RAT measurement for UTRA cell and detected entering condition for the event B2
is met }
ensure that {
}
5.5.4.8 and 5.5.5.
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>if the corresponding reportConfig includes a purpose set to 'reportStrongestCellsForSON':
...
2>else:
...
cell matches the ncc-Permitted defined within the for this measId;
reporting entry for this measId:(a first cell triggers the event)
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 892
892
event):
...
2> if the triggerType is set to 'event' and if the leaving condition applicable for this event is fulfilled for one or
more of the cells included in the cellsTriggeredList defined within the VarMeasReportListfor this measId for
all measurements after layer 3 filtering taken duringtimeToTrigger defined within the VarMeasConfigfor this
event:
measId;
2>if the purpose is included and set to 'reportCGI' and if the UE acquired the information needed to set all
3>stop timer T321;
...
[TS 36.331, clause 5.5.4.8]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 893
893
The UE shall:
1 Thresh Hys Ms < +

1 Thresh Hys Ms >


within the measObject corresponding to the frequency of the inter-RAT neighbour cell)
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event)
this event)
this event)
Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell
Ofn, Hys are expressed in dB
Thresh1 is expressed in the same unit as Ms
Thresh2 is expressed in the same unit as Mn
[TS 36.331, clause 5.5.5]
2>set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the
following:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 894
894
3>if the triggerType is set to 'event':
4>include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId
3>else:
4>include the applicable calls for which the new measurement results became available since the last
3>for each cell that is included in the measResultNeighCells include the physCellId;
4>for each included cell include the layer 3 filtered measured results in accordance with the
...
5>else:
...
reportAmount as defined within the corresponding reportConfig for this measId
1>else:
2>set the preRegistrationStatusHRPD to the UE's CDMA2000 upper layers HRPD preRegistrationStatus;
2>set the preRegistrationStatusHRPD to 'FALSE';
System Simulator:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 895
895
UE:
None.
Preamble:
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
are not satisfied. CPICH_Ec/Io
(Note 1)
CPICH Ec=-
83.5[dBm/3.84
MHz]
dB - -23.5
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-80 -
are satisfied. CPICH_Ec/Io
(Note 1)
CPICH Ec=-
72.3[dBm/3.84
MHz]
dB - -12.3
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
that leaving conditions for event B2
are satisfied. CPICH_Ec/Io
(Note 1)
CPICH Ec=-
83.5[dBm/3.84
MHz]
dB - -23.5

NOTE 1: This parameter is not directly settable, but are derived by calculation from the other parameters set by the
SS.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 896
896
U - S Message
omplete
- -
report the event B2 during the next 10s?
- - - -
event B2 for Cell 7?
- - - -
6A Wait and ignore MeasurementReport
levels for Cells 1 and Cell 7.
- - - -
report the event B2 during the next 10s?
- - 1,2,
3
-


Derivation Path: 36.508, Table 4.6.6-1, condition UTRAN
1 entry
measObject[1] MeasObjectUTRA-f8
}
1 entry
reportConfigId[1] IdReportConfig-B2-UTRA
B2-UTRA(-69, -18)

}
1 entry
measId[1] 1
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 897
897
Table 8.3.2.3.3.3-2A: QuantityConfig (Table 8.3.2.3.3.3-1)
Derivation Path: 36.508, Table 4.6.6-3A, condition UTRAN
QuantityConfig SEQUENCE {
quantityConfigUTRA SEQUENCE {
measQuantityUTRA-FDD cpich-EcN0 UTRA-FDD
measQuantityUTRA-TDD pccpch-RSCP UTRA-TDD
}
}


Table 8.3.2.3.3.3-2B MeasObjectUTRA-f8 (Table 8.3.2.3.3.3-2)
Derivation path: 36.508 table 4.6.6-3 MeasObjectUTRA-GENERIC(f8)
MeasObjectUTRA-GENERIC(f8) ::=SEQUENCE {
carrierFreq UTRA DL carrier
frequency of the cell 7

cellsToAddModList CHOICE {
cellsToAddModListUTRA-FDD ::=SEQUENCE
(SIZE (1.. maxCellMeas)) OF SEQUENCE {
UTRA-
FDD
cellIndex [1] 1
physCellId [1] physicalCellIdentity
Cell 7

}
cellsToAddModListUTRA-TDD ::=SEQUENCE
(SIZE (1..maxMeasId)) OF SEQUENCE {
UTRA-
TDD
cellIndex [1] 1
Cell 7

}
}
}

UTRA-FDD UTRA-FDD cell environment
UTRA-TDD UTRA-TDD cell environment

Table 8.3.2.3.3.3-3: ReportConfigInterRAT-B2-UTRA (Table 8.3.2.3.3.3-2)
Derivation path: 36.508, Table 4.6.6-8 ReportConfigInterRAT-B2-UTRA(-69, -18)
ReportConfigInterRAT-B2-UTRA ::=SEQUENCE {
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 898
898
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListUTRA SEQUENCE (SIZE
1 entry
Cell 7

utra-RSCP (-5..91) UTRA-TDD
utra-EcN0 (0..49) UTRA-FDD
}
}
}
}
}
}
}
}


Periodic reporting / Measurement of UTRAN cells
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for periodic reporting of UTRA
cells }
ensure that {
when { The UE receives reference signal power for cells on the UTRA frequency where measurements
are configured }
then { UE sends MeasurementReport message at regular intervals for these UTRA cells }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and a Measurement Report message for a configured periodic
measurement reporting of UTRA cells on a configured frequency were sent }
ensure that {
a reported UTRA frequency for a cell which was previously not reported }
then { UE sends MeasurementReport message at regular intervals for the available UTRA cells }
}
(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting of UTRA cells ongoing}
ensure that {
reporting of UTRA cells }
then { UE stops sending MeasurementReport message for UTRA cells }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 899
899
}

5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
[TS 36.331, clause 5.5.2.2]
The UE shall:
1>for each measId value included in the received measIdToRemoveList that is part of the current UE configuration
in varMeasConfig:
[TS 36.331, clause 5.5.4.1]
The UE shall:

2>else:
this measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 900
900

[TS 36.331, clause 5.5.5]
with the following:
measId;
3>else:
first;
5>else:
1>if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than to
reportAmount as defined corresponding reportConfig for this measId:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 901
901

1>submit the MEASUREMENT REPORT message to lower layers for transmission, upon which the procedure
ends.
System Simulator:
UE:
None.
Preamble:
execution. Row marked "T0" denotes the initial conditions after preamble, while rows marked "T1" and "T2" are to be
Parameter Unit Cell 1 Parameter Unit Cell 5 Cell 7 Remark
E-UTRA Cell UTRA Cells
T0 Cell-
specific RS
EPRE
dBm/
15kH
z
-75 CPICH_Ec dBm/
3.84
MHz
-85 Off Power levels shall be such that
T1 -75 -85 -85
T2 -75 Off -85

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 902
902
U - S Message
including measConfig to setup measurements
and periodical reporting for UTRA cells.
message.
omplete
- -

periodical reporting of UTRA cells.
- - 1 -
4 The SS sets the cell-specific reference signal
levels and switches Cell 7 on according to row
"T1" in table 8.3.2.4.3.2-1.
- - - -
cells.
- - - -

- - 1, 2 -
7 The SS sets the cell-specific reference signal
levels and switches Cell 5 "Off" according to
row "T2" in table 8.3.2.4.3.2-1.
- - - -
cells.
- - - -

- - 1, 2 -
including measConfig to remove measId for
periodic reporting.
message
omplete
- -
- - 3 F

U - S Message


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 903
903
U - S Message

periodical reporting for Cell 5 and Cell 7?

U - S Message
- EXCEPTION: Step 1 shall be repeated every

periodical reporting for Cell 7(NOTE1)?

Table 8.3.2.4.3.3-1 RRCConnectionReconfiguration (step 1 and step 10, Table 8.3.2.4.3.2-2)
Derivation path: 36.508 table table 4.6.1-8 with condition MEAS

Table 8.3.2.4.3.3-2 MeasConfig (step 1, Table 8.3.2.4.3.2-2)
Derivation Path: 36.508, Table 4.6.6-1 with condition UTRAN
1 entry
measObject[1] MeasObjectUTRA-f8 UTRA frequency
}
1 entry
PERIODICAL

PERIODICAL-UTRA

}
1 entry
measId[1] 1
PERIODICAL

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 904
904

Table 8.3.2.4.3.3-3 MeasObjectUTRA-f8 (step 1, Table 8.3.2.4.3.2-2)
frequency of Cell
5 and Cell 7

UTRA-
FDD
cellIndex [1] 1
Cell 5

cellIndex [2] 2
Cell 7

}
UTRA-
TDD
cellIndex [1] 1
Cell 5

cellIndex [2] 2
Cell 7

}
}
}


Table 8.3.2.4.3.3-4 ReportConfigInterRAT-PERIODICAL-UTRA (step 1, Table 8.3.2.4.3.2-2)
Derivation path: 36.508 table 4.6.6-9 ReportConfigInterRAT-PERIODICAL
ReportConfigInterRAT-PERIODICAL-UTRA ::=
SEQUENCE {

maxReportCells 2 Report Cell 5 and
Cell 7

}

1 entry
measId[1] 1
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 905
905
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListUTRA ::=SEQUENCE (SIZE

physCellId[1] CHOICE {
fdd physicalCellIdentity Cell
5
Report Cell 5 UTRA-
FDD
tdd physicalCellIdentity Cell
5
Report Cell 5 UTRA-
TDD
}
measResult [1] ::=SEQUENCE {
utra-RSCP (-5..91) UTRA-
TDD
utra-EcN0 (0..49) UTRA-
FDD
}
}
}
}
}
}
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 906
906
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}

5
Report Cell 5 UTRA-
FDD
5
Report Cell 5 UTRA-
TDD
}
TDD
FDD
}
7
Report Cell 7 UTRA-
FDD
7
Report Cell 7 UTRA-
TDD
}
TDD
FDD
}
}
}
}
}
}
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 907
907
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}

7
Report Cell 7 UTRA-
FDD
7
Report Cell 7 UTRA-
TDD
}
TDD
FDD
}
}
}
}
}
}
}


Periodic reporting / Measurements of E-UTRAN, UTRAN and GERAN cells
(1)
performed the inter RAT measurement for UTRAN and GERAN cells }
ensure that {
when { The UE receives reference signal power for cells on either UTRAN or GERAN frequency where
measurements are configured }
then { UE sends MeasurementReport message at regular intervals for UTRAN or GERAN cell }
}

(2)
measurement reporting of UTRAN or GERAN cell on a configured frequency was sent }
ensure that {
when { A previously reported cell become unavailable and the UE receives reference signal power on
a reported UTRAN or GERAN frequency for a cell which was previously not reported }
then { UE sends MeasurementReport message at regular intervals for the available UTRAN or GERAN
cell }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 908
908
(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting of UTRAN or GERAN cells
ongoing }
ensure that {
when { The UE receives reference signal power on a reported UTRAN or GERAN frequency for a cell
which was previously not reported }
then { UE sends MeasurementReport messages at regular intervals for the available UTRAN and
GERAN cells }
}

(4)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting of UTRAN and GERAN cells
ongoing }
ensure that {
reporting of UTRAN and GERAN cells }
then { UE stops sending MeasurementReport message for UTRAN and GERAN cells }
}

5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]

3> perform the measurement configuration procedure as specified in 5.5.2;
[TS 36.331, clause 5.5.2.2]
The UE shall:
varMeasConfig:
[TS 36.331, clause 5.5.4.1]
The UE shall:
...
2>else:
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 909
909
...
...
[TS 36.331, clause 5.5.5]
the following:
...
3>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 910
910
first;
5>else:
...
1>else:
...
System Simulator:
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 911
911
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
that camping on Cell 1 is guarantee.
CPICH_Ec/Io dB - Off -
RSSI dBm - - Off
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
reporting. CPICH_Ec/Io dB - -18 -
RSSI dBm - - Off
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
reporting and Cell 5 become
unavailable.
CPICH_Ec/Io dB - Off -
RSSI dBm - - -70
T3
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
that Cell 5 and Cell 24 are satisfied
for periodic reporting. CPICH_Ec/Io dB - -18 -
RSSI dBm - - -70

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 912
912
U - S Message
setup inter-RAT measurement.
message to confirm the setup of inter-RAT
measurement.
omplete
- -
3 The SS power "On" Cell 5 according to the row
"T1" in table 8.3.2.5.3.2-1.
- - - -
5.
- - - -
shall take place
- - - -
- - - -
6 The SS power "Off" Cell 5 and power "On" Cell
24 according to the row "T2" in table
8.3.2.5.3.2-1.
- - - -
messages for 5s to allow power "Off" and
power "On" for Cell 5 and Cell 24 respectively.
- - - -
shall take place
- - - -
- - - -
9 The SS power "On" for Cell 5 according to the
row "T3" in table 8.3.2.5.3.2-1.
- - - -
5.
- - - -
8.3.2.5.3.2-3 and 8.3.2.5.3.2-4 shall take
place
- - - -
- - - -
remove inter-RAT measurement.
message to confirm the remove of inter-RAT
measurement.
omplete
- -
- - 4 F

U - S Message
- - - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 913
913
U - S Message
- - - -
--> MeasurementReport 1, 2,
3
P


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 914
914
2 entry
GENERIC(f11)

}
1 entry
PERIODICAL

PERIODICAL

}
2 entry
measId[1] 1
PERIODICAL

measId[2] 2
PERIODICAL

}
}
}
}
measGapConfig CHOICE {
setup SEQUENCE {
gapOffset CHOICE {
gp1 0
}
}
}
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 915
915
Table 8.3.2.5.3.3-2A MeasObjectUTRA-f8 (Table 8.3.2.5.3.3-2)

UTRA-
FDD
cellIndex [1] 1
Cell 5

}
UTRA-
TDD
cellIndex [1] 1
Cell 5

}
}
}


c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
fdd PhysicalCellIdentity of
Cell 5
UTRA-FDD
tdd PhysicalCellIdentity of
Cell 5
UTRA-TDD
}
utra-RSCP (-5..91)
utra-EcN0 (0..49) UTRA-FDD
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 916
916

c1 CHOICE{
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
arfcn Not checked
}
Cell 24

rssi (0..63)
}
}
}
}
}
}
}
}


2 entries
measId[1] 1
measId[2] 2
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 917
917
Simultaneous A2 and two B2 / Measurements of E-UTRAN, UTRAN and
GERAN cells
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurements configured for A2 on E-UTRAN, B2 on UTRAN
and B2 on GERAN at the same time }
ensure that {
when { UE detects entering condition for the events A2 and B2 are not met }
then { UE does not transmit any MeasurementReport messages}
}
(2)
ensure that {
when { UE detects entering condition for the event A2 is met }
then { UE transmits a MeasurementReport message}
}
(3)
ensure that {
when { UE detects entering condition for the event B2 for UTRAN is met }
then { UE transmits a MeasurementReport message }
}
(4)
ensure that {
when { UE detects entering condition for the event B2 for GERAN is met }
then { UE transmits a MeasurementReport message }
}

5.5.4.3, 5.5.4.8 and 5.5.5.
[TS 36.331, clause 5.5.4.1]
The UE shall:

2>else:
this measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 918
918
measId;
[TS 36.331, clause 5.5.4.3]
The UE shall:
Thresh Hys Ms < +

Thresh Hys Ms >

event).
[TS 36.331, clause 5.5.4.8]
The UE shall:
1 Thresh Hys Ms < +

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 919
919

1 Thresh Hys Ms >


this event).
this event).
[TS 36.331, clause 5.5.5]
with the following:
measId;
3>else:

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 920
920
first;
5>else:

System Simulator:
UE:
None.
Preamble:
execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied
subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
T0
RS EPRE dBm/15kHz -85 - - Entry conditions for A2 and B2 events are
not fulfilled. CPICH_Ec/
PCCPCH
RSCP
dBm/3.84
MHz/dBm
- -80 -
GERAN Cell
Power
dBm - - -85
T1
RS EPRE dBm/15kHz -105 - - Entry conditions for A2 and B2 events are
fullfilled. CPICH_Ec/
PCCPCH
RSCP
dBm/3.84
MHz/dBm
- -60 -
GERAN Cell
Power
dBm - - -65

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 921
921
U - S Message
setup intra and inter RAT measurements on
Cell 1.
message.
omplete
- -
3 Check: Does the UE transmit any
MeasurementReport messages during the next
10s?
parameters according to row T1 in table
8.3.2.6.3.2-1.
- - - -
- EXCEPTION: In parallel to step 5 the steps
specified in Table 8.3.2.6.3.2-3 shall take
place.
- - - -
5 The SS waits for 10s. - - - -
- - 1, 2,
3, 4
-

U - S Message
- EXCEPTION: The steps 1-3 may occur in any
order.
- - - -
A2 for Cell 1 ?
B2 for Cell 5 ?
B2 for Cell 24 ?

Derivation Path: 36.508 table 4.6.1-8 with condition MEAS

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 922
922
Derivation path: 36.508 table 4.6.6-1 with condition INTER-RAT
3 entries
measObjectId[1] IdMeasObject-EUTRA
GENERIC(f1)

measObjectId[2] IdMeasObject-UTRA
measObjectId[3] IdMeasObject-GERAN
GENERIC(f11)

}
3 entries
reportConfig[1] ReportConfigEUTRA-
A2(-95)

B2-UTRA(-95, -70)

GERAN

B2-GERAN(-95,-75)

}
3 entries
measId[1] 1
measObjectId[1] IdMeasObject-EUTRA
measId[2] 2
measObjectId[2] IdMeasObject-UTRA
measId[3] 3
measObjectId[3] IdMeasObject-GERAN
GERAN

}
measQuantityUTRA-FDD cpich-EcN0 UTRA-
FDD
measQuantityUTRA-TDD pccpch-RSCP UTRA-
TDD
}
}
}
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 923
923
Table 8.3.2.6.3.3-3: MeasObjectUTRA-f8 (Table 8.3.2.6.3.3-2)

UTRA-
FDD
cellIndex [1] 1
Cell 5

}
UTRA-
TDD
cellIndex [1] 1
Cell 5

}
}
}


Table 8.3.2.6.3.3-4: Void
Table 8.3.2.6.3.3-5: Void
Table 8.3.2.6.3.3-6: MeasurementReport (step 1 Table 8.3.2.6.3.2-3)
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 924
924
c1 CHOICE {
measId 2
measResultServCell ::=SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultNeighCells CHOICE { Report Cell 5
(1..maxCellReport)) OF MeasResultUTRA
SEQUENCE {
1 entry
physCellId [1] physCellId of cell 5
cgi-Info [1] Not present
TDD
FDD
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 925
925
c1 CHOICE {
measId 3
measResultServCell ::=SEQUENCE {
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultNeighCells CHOICE { Report Cell 24
(1..maxCellReport)) OF MeasResultGERAN
SEQUENCE {
1 entry
carrierFreq [1] Not checked
physCellId [1] physCellId of cell 24
cgi-Info [1] Not present
rssi (0..63)
}
}
}
}
}
}
}
}

Event B2 (measurement HRPD cells)
(1)
performed the inter RAT measurement for HRPD cell and not detected entering condition for the event
B2 is met }
ensure that {
}

(2)
performed the inter RAT measurement for HRPD cell and not detected entering condition for the event
B2 is met }
ensure that {
}

(3)
performed the inter RAT measurement for HRPD cell and detected entering condition for the event B2
is met }
ensure that {
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 926
926
5.5.4.8, and 5.5.5.
[TS 36.331, clause 5.5.4.1]
The UE shall:
1> for each measId included in the measIdList within VarMeasConfig:
2>else:

3>if the corresponding measObject concerns UTRA or CDMA2000:
included in the cellsToAddModifyList defined within the VarMeasurementConfiguration for this
measId (i.e. the cell is included in the white-list);

corresponding with the eventId of the corresponding reportConfig within VarMeasurementConfiguration, is
fulfilled for one or more applicable cells for a duration exceeding the value of timeToTrigger defined for this
event within the VarMeasurementConfiguration while the VarMeasurementReports does not include an entry
for this measId (a first cell triggers the event):
measId;
event):
measId;
this event:
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 927
927

Measure or due to the measurement gap not being setup .
[TS 36.331, clause 5.5.4.8]
The UE shall:
1>apply inequality B2-1 and inequality B2-2 i.e. both have to be fulfilled, as specified below, as the entry condition
for this event;
1>apply inequality B2-3 and inequality B2-4 i.e. at least one of the two has to be fulfilled, as specified below, as
the leaving condition for this event;
1 Thresh Hys Ms < +


1 Thresh Hys Ms >


Ms is the measurement result of the serving cell, not taking into account any offset.
this event).
this event).
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter RAT neighbour cell.
[TS 36.331, clause 5.5.5]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 928
928
1> set the measResultServCell to include the quantities of serving cell;
1> if there is at least one applicable neighbouring cell to report:
2>set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the
following:
4>include the cells included in the cellsTriggeredList as defined within the VarMeasurementReports for this
measId;

> for each cell that is included in the measResultNeighCells, include the physCellId;
4>for each included cell include the layer 3 filtered measured results in accordance with the reportConfig
for this measId, ordered as follows:
6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the
first;
5>else:
6> set the measResult to the quantity as configured for the concerned RAT within the
quantityConfig in order of decreasing triggerQuantity, i.e. the best cell is included first;

reportAmount as defined within the corresponding reportConfigfor this measId :

2>set the preRegistrationStatusHRPD to `FALSE';
System Simulator:
- Cell 1 is high quality cell on E-UTRA
- Cell 15 and Cell 16 are high quality cell on HRPD.
UE:
None.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 929
929
Preamble:
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while columns marked "T1",
T2 T3 and "T4" are to be applied subsequently. The exact instants on which these values shall be applied are
T0
Cell-specific RS EPRE dBm/15 kHz -60 - - The power level values are
such that entering conditions
for event B2 are not satisfied.
or/Ioc dB - -20 -20
Ioc dBm/1.23 MHz - -55 -55
Pilot_Ec/Io (Note 1) dB - -20 -20
T1
for event B2 are satisfied.
or/Ioc dB - -5 -20
Ioc dBm/1.23 MHz - -55 -55
T2
such that leaving conditions for
event B2 are satisfied.
or/Ioc dB - -20 -20
Ioc dBm/1.23 MHz - -55 -55
T3
for event B2 are satisfied.
or/Ioc dB - -5 -20
Ioc dBm/1.23 MHz - -55 -55
T4
such that leaving conditions for
event B2 are satisfied.
or/Ioc dB - -20 -20
Ioc dBm/1.23 MHz - -55 -55
SS.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 930
930
U - S Message
omplete
- -
8.3.2.7.3.2-1.
- - - -
event B2 for Cell 15, not including Cell 16?
6 Void - - - -
8.3.2.7.3.2-1.
- - - -
8.3.2.7.3.2-1.
- - - -
11 Void - - - -
8.3.2.7.3.2-1.
- - - -
- - - -

c1 CHOICE{
radioResourceConfiguration Not present
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 931
931
1 entry
measObject[1] MeasObjectCDMA2000-
GENERIC

}
1 entry
CDMA2000

B2-CDMA2000(-69, -18)

}
1 entry
measId[1] 1
CDMA2000

}
quantityConfigCDMA2000 SEQUENCE {
measQuantityCDMA2000 pilotStrength
}
}
measGapConfig SEQUENCE {
gapActivation CHOICE {
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

Table 8.3.2.7.3.3-3: MeasObjectCDMA2000-GENERIC (Table 8.3.2.7.3.3-2)
Derivation Path: 36.508, Table 4.6.6-1C
MeasObjectCDMA2000-GENERIC ::=SEQUENCE {
cdma2000-Type TypeHRPD
bandClass Band Class of frequency
under test

arfcn f14
}
searchWindowSize 15
offsetFreq db0
cellsToRemoveList Not present
cellsToAddModList CHOICE {} [Not present]
cellForWhichToReportCGI Not present
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 932
932
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultsCDMA2000 :=SEQUENCE {
preRegistrationStatusHRPD FALSE
measResultListCDMA2000 ::=SEQUENCE
(SIZE (1..maxCellReport)) OF SEQUENCE {
1 entry
physCellId [1] PhysicalCellIdentity of
Cell 15

pilotStrength (0..63)
}
}
}
}
}
}
}
}
}

Periodic reporting / Measurement of HRPD cells)
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for periodic reporting of HRPD
cells }
ensure that {
when { The UE receives reference signal power for cells on the HRPD frequency where measurements
are configured }
then { UE sends MeasurementReport message at regular intervals for these HRPD cells }
}

(2)
measurement reporting of HRPD cells on a configured frequency were sent }
ensure that {
a reported HRPD frequency for a cell which was previously not reported }
then { UE sends MeasurementReport message at regular intervals for the available HRPD cells }

}
(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting of HRPD cells ongoing}
ensure that {
when { The UE receives a RRCConnectionReconfiguration message removing the measID of periodic
reporting of HRPD cells }
then { UE stops sending MeasurementReport message for HRPD cells }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 933
933

5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInformation and theUE is able to
comply with the configuration included in this message, the UE shall:
..
1>if the RRCConnectionReconfiguration message includes the measurementConfiguration:
[TS 36.331, clause 5.5.2.2]
The UE shall:
1>for each measId value included in the measIdToRemoveList:
2>remove the entry, from the parameter measIdList within VarMeasurementConfiguration, with the
corresponding measId value;
2>remove the entry within the VarMeasurementReports for this measId, if included;
2>reset the periodical reporting timer or timer T321, whichever one is running, as well as associated
information (e.g. timeToTrigger) for this measId.
[TS 36.331, clause 5.5.4.1]
The UE shall:
1>for each measId included in the measIdList within VarMeasurementConfiguration:
included in the cellsToAddModifyList defined within the VarMeasurementConfiguration for this
cell matches the ncc-Permitted defined within the VarMeasurementConfiguration for this measId;
3>else if the corresponding measObject concerns EUTRA:
concerned cell is not included in the blackListedCellsToAddModifyList defined within the
VarMeasurementConfiguration for this measId;
2>else consider a neighbouring cell on the associated frequency/ set of frequencies (GERAN) to be applicable
as follows:
3>if the corresponding reportingConfig includes a purpose set to reportStrongestCellsForSON:
4>consider any neighbouring cell detected on the associated frequency to be applicable
3>if the corresponding reportingConfig includes a purpose set to reportCGI:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 934
934
4>consider any neighbouring cell detected on the associated frequency/ set of frequencies (GERAN)
which has a physicalCellIdentity matching the value of the cellForWhichToReportCGI included in
the corresponding measObject within the VarMeasurementConfiguration to be applicable
3>else:
5>consider a neighbouring cell on the associated frequency to be applicable when the concerned cell
is included in the cellsToAddModifyList defined within the VarMeasurementConfiguration for this
..
2>if the triggerType is set to periodical and a (first) measurement result is available for one or more
applicable cells:
3>include an entry within the VarMeasurementReports for this measId;
3>set the numberOfReportsSent defined within the VarMeasurementReports for this measId to 0;
NOTE 1: If the purpose is set to reportStrongestCells or to reportStrongestCellsForSON, the UE initiates a first
measurement report immediately after the requested reportQuantity becomes available for at least either
serving cell or one of the applicable cells
2>Upon expiry of the periodical reporting timer for this measId:
[TS 36.331, clause 5.5.5]
1>set the neighbouringMeasResults to include the best neighbouring cells up to maxReportCells in accordance with
the following:
3>include the cells included in the cellsTriggeredList as defined within the VarMeasurementReports for this
measId;
2>else:
3>set the neighbouringMeasResults to include the applicable cells for which the requested reportQuantity
has been available since the last periodical reporting or since the measurement was initiated or reset;
2>for each cell that is included in the neighbouringMeasResults, include the physicalCellIdentity;
1>increment the numberOfReportsSent as defined within the VarMeasurementReports for this measId by 1;
1>if the numberOfReportsSent as defined within the VarMeasurementReports for this measId is less than the
reportAmount as defined within the corresponding reportingConfiguration as defined in the
VarMeasurementConfiguration:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 935
935
2>start the periodical reporting timer with the value of reportInterval as defined within the
VarMeasurementConfiguration for this measId;
1>else if the numberOfReportsSent as defined within the VarMeasurementReports for this measId is equal to the
reportAmount as defined within the corresponding reportingConfiguration as defined in the
VarMeasurementConfiguration:
3>remove the entry within the VarMeasurementReports for this measId;
1>if the measured results are for CDMA HRPD:
2>set the hrpdPreRegistrationStatus to the UEs CDMA upper layers HRPD preRegistrationStatus;
1>if the measured results are for CDMA 1xRTT:
2>set the hrpdPreRegistrationStatus to `0;
System Simulator:
- Cell 1 is high quality cell on E-UTRA
- Cell 15 and Cell 16 are high quality cell on HRPD
UE:
None.
Preamble:
- The UE is brought to state Generic RB Established (state 3) according to [18] on Cell 1
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 936
936
T0
Cell-specific RS
EPRE
dBm/15 kHz -60 - -
Power levels shall be such
guaranteed. or/Ioc dB - -5 -20
Ioc
dBm/1.23
MHz
- -55 -55
CPICH_Ec/Io
(Note 1)
dB - -6 -20
T1
Cell-specific RS
EPRE
dBm/15 kHz -60 - -

or/Ioc dB - -5 -5
Ioc
dBm/1.23
MHz
- -55 -55
CPICH_Ec/Io
(Note 1)
dB - -6 -6
T2
Cell-specific RS
EPRE
dBm/15 kHz -60 - -

or/Ioc dB - -20 -5
Ioc
dBm/1.23
MHz
- -55 -55
CPICH_Ec/Io
(Note 1)
dB - -20 -6
Note 1: This parameter is not directly settable, but is derived by calculation from the other parameters
set by the SS.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 937
937
U - S Message
including measConfig to setup measurements
and periodical reporting for HRPD cells.
message to confirm measurement on Cell 15.
omplete
- -
steps 3 and 4, the steps specified in table
- - - -
periodical reporting of HRPD cells.
- - - -
for Cell 1, Cell 15 and Cell 16 according to row
"T1" in table 8.3.2.8.3.2-1.
- - - -
cells.
- - - -
- - - -
- - - -
for Cell 1, Cell 15 according to row "T2" in
table 8.3.2.4.3.2-1.
- - - -
cells.
- - - -
- - - -
- - - -
10 SS transmits an
including measConfig to remove measId for
periodic reporting.
message
omplete
- -

U - S Message
- - - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 938
938
U - S Message
- - - -
periodical intra frequency reporting for Cell 15
and Cell 16?

U - S Message


c1 CHOICE{
radioResourceConfiguration Not present
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 939
939
measObjectToAddModifyList SEQUENCE (SIZE
1 entry
GENERIC

}
1 entry
CDMA2000

PERIODICAL

}
1 entry
measId[1] 1
CDMA2000

}
}
}
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

carrier Freq SEQUENCE {
under test

bandClassfrequency f14
}
searchWindowSize 15
offsetFreq db0
cellsToAddModifyList CHOICE {} Not present
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 940
940
Table 8.3.2.8.3.3-4: MeasurementReport (step 1 Table 8.3.2.8.3.2-3, Table 8.3.2.8.3.2-4, Table
8.3.2.8.3.2-5)
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry Table
8.3.2.8.3.2-
3
Cell 15

}
}
2 entries Table
8.3.2.8.3.2-
4
Cell 15

}
Cell 16

}
}
1 entry Table
8.3.2.8.3.2-
5
Cell 16

}
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 941
941

1 entry
measId[1] 1
}
}

Event B2 / Measurement of 1xRTT cells)
(1)
performed the inter RAT measurement for 1xRTT cell and not detected entering condition for the event
B2 is met }
ensure that {
}

(2)
performed the inter RAT measurement for 1xRTT cell and not detected entering condition for the event
B2 is met }
ensure that {
}

(3)
performed the inter RAT measurement for 1xRTT cell and detected entering condition for the event B2
is met }
ensure that {
}

5.5.4.8 and 5.5.5.
[TS 36.331, clause 5.5.4.1]
The UE shall:
1>for each measId included in the measIdList within VarMeasConfig

2>else :

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 942
942

measId;
event):
measId;
all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfign for
this event:
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 943
943
[TS 36.331, clause 5.5.4.8]
The UE shall:
1 Thresh Hys Ms < +


1 Thresh Hys Ms >


this event).
this event).
[TS 36.331, clause 5.5.5]
with the following:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 944
944
measId;
3>else:
first;
5>else:
4>if the mandatory present fields of the globalCellIdentity for the cell indicated by the
1>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 945
945
System Simulator:
UE:
None.
Preamble:
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while rows marked "T1",
T2, "T3" and T4 are to be applied subsequently. The exact instants on which these values shall be applied are
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 946
946
Parameter Unit Cell 1 Cell
19
Cell 20 Remark
T0
Cell-specific
RS EPRE
dBm/15
kHz
-60 - -
that entering conditions for
event B2 are not satisfied. or/Ioc dB - -15 -15
Pilot Ec/Ior dB - -7 -7
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot Ec/Io
(Note 1)
dB - -22 -22
T1
Cell-specific
RS EPRE
dBm/15
kHz
-80 - -
event B2 are satisfied. or/Ioc dB - 0 -15
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot _Ec/Io
(Note 1)
dB - -10 -22
T2
Cell-specific
RS EPRE
dBm/15
kHz
-60 - -
that leaving conditions for event
B2 are satisfied. or/Ioc dB - -15 -15
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot Ec/Io
(Note 1)
dB - -22 -22
T3
Cell-specific
RS EPRE
dBm/15
kHz
-80 - -
event B2 are satisfied. or/Ioc dB - 0 -15
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot Ec/Io
(Note 1)
dB - -10 -22
T4
Cell-specific
RS EPRE
dBm/15
kHz
-60 - -
that leaving conditions for event
B2 are satisfied. or/Ioc dB - -15 -15
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot Ec/Io
(Note 1)
dB - -22 -22
Note 1: This parameter is not directly settable, but is derived by calculation from the other
parameters set by the SS.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 947
947
U - S Message
omplete
- -
8.3.2.9.3.2-1.
- - - -
6 Void - - - -
8.3.2.9.3.2-1.
- - - -
8.3.2.9.3.2-1.
- - - -
11 Void - - - -
12 The SS changes Cell 1, Cell 19 and Cell20
8.3.2.9.3.2-1.
- - - -
- - - -


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 948
948
1 entry
GENERIC

}
1 entry
CDMA2000

B2-CDMA2000(-69, -18)

}
1 entry
measId[1] 1
CDMA2000

}
}
}
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

cdma2000-Type Type1XRTT
CarrierFreqCDMA2000 SEQUENCE {
under test

arfcn f17
}
searchWindowSize 15
offsetFreq db0
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 949
949
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResults NeighCells CHOICE {
1 entry
Cell 19

}
}
}
}
}
}
}
}
}

Periodic reporting / Measurement of 1xRTT cells
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for periodic reporting of 1xRTT
cells }
ensure that {
when { The UE receives reference signal power for cells on the 1xRTT frequency where measurements
are configured }
then { UE sends MeasurementReport message at regular intervals for these 1xRTT cells }
}

(2)
measurement reporting of 1xRTT cells on a configured frequency was sent }
ensure that {
a reported 1xRTT frequency for a cell which was previously not reported }
then { UE sends MeasurementReport message at regular intervals for the available 1xRTT cells }
}

(3)
with { UE in E-UTRA RRC_CONNECTED state and periodic measurement reporting of 1xRTT cells ongoing}
ensure that {
when { The UE receives an RRCConnectionReconfiguration message removing the measID of periodic
reporting of 1xRTT cells }
then { UE stops sending MeasurementReport message for 1xRTT cells }
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 950
950

5.5.2.2, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
[TS 36.331, clause 5.5.2.2]
The UE shall:
varMeasConfig:
[TS 36.331, clause 5.5.4.1]
The UE shall:


2>else:


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 951
951

[TS 36.331, clause 5.5.5]
with the following:

3>else:

5>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 952
952

1>else:

System Simulator:
UE:
None.
Preamble:
execution. Row marked "T0" denotes the initial conditions, while rows marked "T1" and "T2" are to be applied
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 953
953
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -
Power levels shall be such that
or/Ioc dB - 0 -15
Pilot Ec/ Ior dB - -7 -7
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot Ec/Io
(Note 1)
dB - -10 -22
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -

or/Ioc dB - 0 0
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot Ec/Io
(Note 1)
dB - -10 -10
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-60 - -

or/Ioc dB - -15 -0
Ioc
dBm/1.2
3 MHz
- -75 -75
Pilot Ec/Io
(Note 1)
dB - -22 -10
set by the SS.

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 954
954
U - S Message
1 SS transmits an
including measurementConfiguration to setup
measurements and periodical reporting for
1xRTT cells.
message.
omplete
- -
described in steps 3 to 4, the steps specified in
table 8.3.2.10.3.2-3 shall take place.
- - - -
periodical reporting of 1xRTT cells.
- - 1 -
and switches Cell 20 on according to row "T1"
in table 8.3.2.10.3.2-1.
- - - -
cells.
- - - -
table 8.3.2.10.3.2-4 shall take place.
- - - -
- - 1, 2 -
and switches Cell 19 off according to row "T2"
in table 8.3.2.10.3.2-1.
- - - -
cells.
- - - -
described in steps 9 to 10, the steps specified
in table 8.3.2.10.3.2-5 shall take place.
- - - -
- - 1, 2 -
10 SS transmits an
including measurementConfiguration to
remove measId for periodic reporting.
message
omplete
- -

U - S Message
- - - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 955
955
U - S Message
- - - -
periodical intra frequency reporting for Cell 20
and Cell20?

U - S Message
- - - -


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 956
956
1 entry
measObject[1] MeasObjectCDMA2000
}
1 entry
reportConfigId[1] IdReportConfig-f17
PERIODICAL

}
1 entry
measId[1] 1
reportConfigId[1] IdReportConfig-f17
}
quantityConfigEUTRA Not present
quantityConfigUTRA Not present
quantityConfigGERAN Not present
quantityConfigCDMA2000 SEQUENCE { Not present
}
}
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

Table 8.3.2.10.3.3-3: MeasObjectCDMA2000 (step 1, Table 8.3.2.10.3.2-2)
under test

arfcn f17
}
SearchWindowSize 15
offsetFreq db0
cellsToAddModList CHOICE {} Not present
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 957
957
c1 CHOICE{
measurementConfiguration ::=SEQUENCE {
measIdToRemoveList::=SEQUENCE (SIZE
1 entry
measId[1] 1
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 958
958
Table 8.3.2.10.3.3-5: MeasurementReport (step 1, Table 8.3.2.10.3.2-3, Table 8.3.2.10.3.2-4, Table
8.3.2.10.3.2-5)
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry Table
8.3.2.10.3.
2-3 physCellId[1] PhysicalCellIdentity of
Cell 19

cfg-Info[1] Not present
}
}
2 entries Table
8.3.2.10.3.
Cell 19

}
Cell 20

}
}
1 entry Table
8.3.2.10.3.
Cell 20

}
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 959
959
8.3.3 Measurements for self optimized networks
8.3.3.1 Measurement configuration control and reporting / SON / ANR / CGI
reporting of E-UTRAN cell
(1)
ensure that {
}
(2)
ensure that {
when { UE is commanded to report the global cell identity of the neighbour cell }
then { UE determines the global cell identity of the cell included in the associated measurement
object by acquiring the relevant system information from the concerned cell and reports the global
cell identity in the MeasurementReport }
}

5.5.2.3, 5.5.3.1, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.2.3]
The UE shall:
...
The UE shall:
1>for each measId included in the received measIdToAddModList:
2>if an entry with the matching measId exists in the measIdList within the VarMeasConfig:
3>replace the entry with the value received for this measId;
2>else:
3>add a new entry for this measId within the VarMeasConfig ;
2>if the triggerType is set to periodical and the purpose is set to reportCGI in the reportConfig associated
with this measId:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 960
960
4>start timer T321 with the timer value set to 1 second for this measId;
3>else:
4>start timer T321 with the timer value set to 8 seconds for this measId;
[TS 36.331, clause 5.5.3.1]
The UE supports measurements using a reporting configuration with the purpose set to reportCGI, if the network
provides sufficient idle periods.
The UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting
criteria or for measurement reporting.
The UE shall:
2>if a measurement gap configuration is setup; or
2>the UE does not require measurement gaps to perform the concerned measurement:
3>if s-Measure is not configured; or
3>if s-Measure is configured and the serving cell RSRP, after layer 3 filtering, is lower than this value; or
3>if the purpose for the associated reportConfig is set to reportCGI:
4>perform the corresponding measurements of neighbouring cells on the frequencies and RATs
indicated in the concerned measObject;
2>perform the evaluation of reporting criteria as specified in section 5.5.4;
1>if a measId is configuredfor which the purpose within the associated reportConfig is set to reportCGI:
2>try to acquire the global cell identity of the cell indicated by the cellForWhichToReportCGI in the associated
measObject by acquiring the relevant system information from the concerned cell;
2>if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is an E-UTRAN
cell:
3>try to acquire the list of additional PLMN Identities, as included in the plmn-IdentityList, if multiple
PLMN identities are broadcast in the concerned cell;
NOTE: The primary PLMN is part of the global cell identity.
2>if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a UTRAN
cell:
3>try to acquire the LAC, the RAC and the list of additional PLMN Identities, if multiple PLMN identities
are broadcast in the concerned cell;
2>if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a GERAN
cell:
3>try to acquire the RAC in the concerned cell;
2>if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a
CDMA2000 cell and the cdma2000-Type included in the measObject is typeHRPD:
3>try to acquire the Sector ID in the concerned cell;
CDMA2000 cell and the cdma2000-Type included in the measObject is type1XRTT:
3>try to acquire the BASE ID, SID and NID in the concerned cell;
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 961
961
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>else:
this measId;
measId;
event):
measId;
this event:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 962
962
measId;
3>stop timer T321;
[TS 36.331, clause 5.5.5]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 963
963

MeasurementReport
UE EUTRAN


the following:
measId;
3>else:
first;
5>else:
4>if the mandatory present fields of the cgi-Info for the cell indicated by the cellForWhichToReportCGI
in the associated measObject have been obtained:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 964
964
1>else:
...
System Simulator:
- Cell 1 and Cell 2
Preamble:
the test execution. Row marked "T0" denotes the conditions after the preamble, while row marked "T1" is to be applied
(DL only)
Remark
T0 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 -91 Power levels shall be such that entry condition for event A3
is not satisfied:

T1 Cell-
specific RS
EPRE
dBm/
15kH
z
-85 -79 Power levels shall be such that entry condition for event A3
is satisfied:

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 965
965
U - S Message
measurement and reporting for event A3 (intra
frequency measurement) and set
timeAlignmentTimerDedicated to infinity.
message.
omplete
- -
signal level according to row "T1" in table
8.3.3.1.3.2-1.
- - - -
including measConfig including reportCGI for
Cell 2 and sufficient idle periods for UE to
acquire the relevant system information from
Cell 2.
message.
omplete
- -
MeasurementReport message with
cellGlobalId of Cell 2 within 1 sec.

Table 8.3.3.1.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble and all the steps in Table
8.3.3.1.3.2-2)
Derivation Path: 36.508 clause 4.4.3.3-1
RadioResourceConfigCommonSIB-DEFAULT ::=
SEQUENCE {

pcch-Config PCCH-Config-
LONGCYCLE

}
PCCH-Config-LONGCYCLE::=SEQUENCE {
defaultPagingCycle rf256
nB oneT
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 966
966
Table 8.3.3.1.3.3-1A: SystemInformationBlockType1 for Cell 2 (preamble and all steps, Table
8.3.3.1.3.2-2)
SEQUENCE {
2 entries
mcc See Table 8.3.3.1.3.3-1B
mnc See Table 8.3.3.1.3.3-1B
}
mcc See Table 8.3.3.1.3.3-1B
mnc See Table 8.3.3.1.3.3-1B
}
}
}
}

The PLMN Identity list broadcasted on the BCCH in Cell 2 shall be configured as defined in the table below.
Table 8.3.3.1.3.3-1B: PLMN Identity List broadcasted for Cell 2
Cell PLMN Identity (1) PLMN Identity (2)
2 PLMN 1 PLMN 1 PLMN 2 PLMN 2

1 2 3 1 2 3
1 0 0 1 0 1 -
2 0 0 1 0 2 -

NOTE: (dash) denotes not present
ul-SCH-Config Not present
drx-Config Not present
phr-Config Not present
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 967
967
measIdToAddModList ::=SEQUENCE (SIZE
1 entry
measId[1] 1
}
measObjectToAddModList ::=SEQUENCE (SIZE
1 entry
GENERIC(f1)

}
reportConfigToAddModList ::=SEQUENCE (SIZE
1 entry
}
}

Table 8.3.3.1.3.3-4 ReportConfig-A3-H (step 1, Table 8.3.3.1.3.2-2)
event SEQUENCE {
eventId CHOICE {
eventA3 SEQUENCE {
}
}
timeToTrigger ms0
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 968
968
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
Report Cell 2
cgi-Info Not present
rsrpResult (0..97)
}
}
}
}
}
}
}

dicated-DRX

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 969
969
1 entry
measId[1] 2
measObjectId[1] IdMeasObject-f1-CGI
reportConfigId[1] ReportConfigId-CGI
}
1 entry
measObject[1] MeasObjectEUTRA-CGI
}
reportConfigToRemoveList ::=SEQUENCE (SIZE

reportConfigId IdReportConfig-A3
}
1 entry
reportConfig[1] ReportConfig-CGI
}
}

Table 8.3.3.1.3.3-8: MeasObjectEUTRA-CGI (step 5, Table 8.3.3.1.3.2-2)
MeasObjectEUTRA-CGI ::=SEQUENCE {
carrierFreq SEQUENCE {} Downlink EARFCN for f1
cellForWhichToReportCGI PhysCellId of the Cell 2.
}

Table 8.3.3.1.3.3-9: ReportConfig-CGI (step 5, Table 8.3.3.1.3.2-2)
periodical SEQUENCE {
purpose CHOICE {
reportCGI NULL
}
}
reportAmount r1
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 970
970
Table 8.3.3.1.3.3-10: RadioResourceConfigDedicated-DRX (step 5, Table 8.3.3.1.3.2-2)
RadioResourceConfigDedicated-DRX ::=
SEQUENCE {

maxHARQ-Tx n5
periodicBSR-Timer infinity
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
drx-RetransmissionTimer sf16
sf2560 0
}
}
}
phr-Config CHOICE {
release NULL
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 971
971
c1 CHOICE {
measId 2
measResultServCell SEQUENCE { Report Cell 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
physCellId[1] PhysCellId of Cell 2
cgi-Info[1] SEQUENCE {
cellGlobalId cellGlobalIdof formed
from the first entry in
plmn-IdentityList and
cellIdentity Cell 2

trackingAreaCode trackingAreaCode of Cell
2

plmn-IdentityList {} List of identities starting
from the second entry of
plmn-IdentityList of Cell 2

}
rsrpResult (0..97)
}
}
}
}
}
}
}
}

reporting of UTRAN cell
(1)
with { UE in E-UTRA RRC_CONNECTED state and measurement configured for periodic reporting of UTRA
cells with the purpose of SON }
ensure that {
when { The UE receives reference signal power for cells on the UTRA frequency where measurements
are configured }
then { UE sends MeasurementReport message at regular intervals for these UTRA cells }
}
(2)
ensure that {
when { UE is commanded to report the global cell identity of the inter-RAT(UTRAN) neighbour cell }
then { UE determines the global cell identity of the inter-RAT(UTRAN) cell included in the
associated measurement object by acquiring the relevant system information from the concerned cell
and reports the global cell identity in the MeasurementReport message}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 972
972
5.5.2.3, 5.5.3, 5.5.4.1and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
...
[TS 36.331, clause 5.5.2.3]
The UE shall:
...
with this measId:
3>else:
[TS 36.331, clause 5.5.3]
The UE shall:

cell:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 973
973
...
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>else:


3>stop timer T321;
[TS 36.331, clause 5.5.5]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 974
974
the following:
measId;
3>else:
first;
5>else:
1>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 975
975

System Simulator:
UE:
None.
Preamble:
Table 8.3.3.2.3.2-1 illustrates the downlink power levels to be applied for cells at various time instants of the test
execution. Row marked "T0" denotes the conditions after the preamble, while row marked "T1" is to be applied
Table 8.3.3.2.3.2-1: Time instance of cell power levels
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-80 -
CPICH_Ec
dBm/3.8
4MHz
- Off For Cell 5 is a UTRA FDD Cell
P-CCPCH
dBm/1.2
8 MHz
Off For Cell 5 is a UTRA TDD Cell
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
CPICH_Ec
dBm/3.8
4MHz
- -75 For Cell 5 is a UTRA FFDD Cell
P-CCPCH
dBm/1.2
8 MHz
-78 For Cell 5 is a UTRA TDD Cell

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 976
976
U - S Message
including measConfig to setup inter RAT
measurement for the purpose of SON and set
timeAlignmentTimerDedicated to infinity.
message.
omplete
- -
- - - -
measured result for Cell 5?
Cell 5.
message.
omplete
- -
cellGlobalId of Cell 5 within 8 sec?

8.3.3.2.3.2-2)
SEQUENCE {

pcch-Configuration PCCH-
Configuration-
LONGCYCLE

}
PCCH-Configuration-LONGCYCLE::=
SEQUENCE {

}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 977
977
Table 8.3.3.2.3.3-1A: Master Information Block for Cell 5 (preamble and all the steps in Table
8.3.3.2.3.2-2)
MasterInformationBlock ::=SEQUENCE {
plmn-Type ::=CHOICE {
gsm-MAP SEQUENCE {
plmn-Identity SEQUENCE {
mcc See Table
8.3.3.2.3.3-2B
(SIZE (3)) OF Digit
mnc See Table
8.3.3.2.3.3-2B
(SIZE (2..3)) OF Digit
}
}
}
masterInformationBlock-v690ext SEQUENCE {
multiplePLMN-List SEQUENCE {
mibPLMN-Identity TRUE
multiplePLMNs SEQUENCE (SIZE (1..5)) OF
SEQUENCE {
1 entry
mcc See Table
8.3.3.2.3.3-2B
(SIZE (3)) OF Digit
mnc See Table
8.3.3.2.3.3-2B
(SIZE (2..3)) OF Digit
}
}
}
}
}

The MIB PLMN Identity and PLMN codes broadcasted on the BCCH in Cell 5 shall be configured as defined in the
table below.
Cell MIB
PLMN
Identity
PLMN Identity Multiple PLMNs (1)
5 TRUE PLMN 3 PLMN 3 PLMN 2 PLMN 2
Table 8.3.3.2.3.3-2B: PLMN Identity List broadcasted for Cell 5

1 2 3 1 2 3
1 0 0 1 0 1 -
2 0 0 1 0 2 -
3 0 0 1 0 3 -

NOTE: (dash) denotes not present

Table 8.3.3.2.3.3-1C: System Information Block type 1 for Cell 5 (preamble and all the steps in Table
8.3.3.2.3.2-2)
Derivation Path: 34.108 clause 6.1.0b with Condition A1 "UTRAN cell environment"

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 978
978
Table 8.3.3.2.3.3-1D: System Information Block type 3 (FDD) for Cell 5 (preamble and all the steps in
Table 8.3.3.2.3.2-2)

}
}
}

Derivation Path: 36.508, Table 4.6.6-1 condition UTRAN
1 entry
measObject[1] MeasObjectUTRA-f8 UTRA frequency
}
1 entry
reportConfigId[1] IdReportConfig-P-UTRA
reportConfig[1] ReportConfigInterRAT-P-
UTRA

}
1 entry
measId[1] 1
reportConfigId[1] IdReportConfig-P-UTRA
}
}
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 979
979
Table 8.3.3.2.3.3-4 MeasObjectUTRA-f8 (step 1, Table 8.3.3.2.3.2-2)

UTRA-
FDD
cellIndex [1] 1
Cell 5

}
UTRA-
TDD
cellIndex [1] 1
Cell 5

}
}
}


Table 8.3.3.2.3.3-5: ReportConfigInterRAT-P-UTRA (step 1, Table 8.3.2.3.3.2-2)
Derivation Path: 36.508, Table 4.6.6-9 ReportConfigInterRAT-PERIODICAL
ReportConfigInterRAT-PERIODICAL ::=SEQUENCE
{

purpose CHOICE {
reportStrongestCellsForSON NULL
}
}
}
reportAmount r1
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 980
980
C1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry Report Cell 5
the Cell 5.

cgi-Info Not present
TDD
FDD
}
}
}
}
}
}
}
}


radioResourceConfiguration RadioResourceConfigDe
dicated-DRX

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 981
981
1 entry
measObject[1] MeasObjectUTRA-CGI
}
1 entry
reportConfig[1] ReportConfigUTRA-CGI
}
1 entry
measId[1] 2
}
}

Table 8.3.3.2.3.3-9: MeasObjectUTRA-CGI (step 5, Table 8.3.3.2.3.2-2)
MeasObjectUTRA-CGI ::=SEQUENCE {
carrierFreq Downlink UARFCN of f8
cellForWhichToReportCGI PhysicalCellIdentity of
the Cell 5.

}

Table 8.3.3.2.3.3-10: ReportConfigUTRA-CGI (step 5, Table 8.3.3.2.3.2-2)
{

purpose CHOICE {
reportCGI NULL
}
}
}
reportAmount r1
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 982
982
SEQUENCE {

maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
Sf2560 0
}
}
}
phr-Config CHOICE {
release NULL
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 983
983
c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 5

cellGlobalId cellGlobalId formed
from PLMN Identity
and Cell identity of Cell
5

locationAreaCode locationAreaCode of Cell
5

routingAreaCode routingAreaCode of Cell
5

plmn-IdentityList 'Multiple PLMN List of
Cell 5

}
TDD
FDD
}
}
}
}
}
}
}
}


reporting of GERAN cell
(1)
B2 is met }
ensure that {
}
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 984
984
(2)
ensure that {
when { UE is commanded to report the global cell identity of the inter-RAT(GERAN) neighbour cell }
then { UE determines the global cell identity of the inter-RAT(GERAN) cell included in the
associated measurement object by acquiring the relevant system information from the concerned cell
and reports the global cell identity in the MeasurementReport }
}

5.5.2.3, 5.5.3, 5.5.4.1 and 5.5.5.
[TS 36.331, clause 5.3.5.3]
...
[TS 36.331, clause 5.5.2.3]
The UE shall:
...
with this measId:
3>else:
[TS 36.331, clause 5.5.3]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 985
985
cell:
cell:
cell:
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>else:

...
3>stop timer T321;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 986
986
[TS 36.331, clause 5.5.5]
the following:
measId;
3>else:
first;
5>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 987
987
1>else:

System Simulator:
UE:
None.
Preamble:
Table 8.3.3.3.3.2-1: Time instances of cell power levels
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
Power levels are shall be such that
entry condition for event B2 is not
satisfied: RSSI dBm - -85
T1
Cell-specific RS
EPRE
dBm/15k
Hz
[-80] -
Power levels are shall be such that
entry condition for event B2 is
satisfied: RSSI dBm - -65

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 988
988
U - S Message
including measConfig to setup inter-RAT
measurements and reporting for event B2 and
set timeAlignmentTimerDedicated to infinity.
message.
omplete
- -
8.3.3.3.3.2-1.
- - - -
B2 for Cell 24?
Cell 24.
message.
omplete
- -

8.3.3.3.3.2-2)
SEQUENCE {

pcch-Configuration PCCH-
Configuration-
LONGCYCLE

}
PCCH-Configuration-LONGCYCLE::=
SEQUENCE {

}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 989
989
}
}
}

Derivation Path: 36.508, Table 4.6.6-1 with condition GERAN
1 entry
GENERIC(f11)

}
1 entry
GERAN

B2-GERAN(-69, -79)
EUTRA-Thres =-
69;
GERAN-Thres =-
79;
threshold-RSRP =
EUTRA-
Thres+140 =71;
b2-
Threshold2GERA
N = GERAN-
Thres +110 =31.

}
1 entry
measId[1] 1
GERAN

}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 990
990
Table 8.3.3.3.3.3-4: MeasObjectGERAN-GENERIC(f11) (step 1, Table 8.3.3.3.3.2-2)
Derivation Path: 36.508 Table 4.6.6-2A
MeasObjectGERAN-GENERIC(Freq) ::=SEQUENCE
{

carrierFreqs SEQUENCE {
startingARFCN Same as Cell 24
bandIndicator Same as Cell 24
explicitListOfARFCNs Same as Cell 24
}
}
ncc-Permitted 11111111
}

Table 8.3.3.3.3.3-5: Void

Derivation path: 36.508, Table 4.6.1-5
c1 CHOICE {
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
carrierFreq[1] SEQUENCE { CarrierFreq of Cell
24

Arcfn Downlink arcfn of Cell 24
bandIndicator Same bandindicator as
Cell 24

}
Cell 24.

measResult[1] SEQUENCE{
rssi (0..63)
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 991
991
dicated-DRX

}

1 entry
measObject[1] CHOICE {
measObjectGERAN MeasObjectGERAN-CGI
}
1 entry
reportConfig[1] CHOICE {
reportConfigGERAN ReportConfigGERAN-
CGI

}
1 entry
measId[1] 2
}
}

Table 8.3.3.3.3.3-9: MeasObjectGERAN-CGI (step 5, Table 8.3.3.3.3.2-2)
Derivation Path: 36.308, Table 4.6.6-2A
MeasObjectGERAN-GENERIC(Freq) ::=SEQUENCE
{

carrierFreqs SEQUENCE {
startingARFCN Same as Cell 24
bandIndicator Same as Cell 24
explicitListOfARFCNs Same as Cell 24
}
}
offsetFreq Not present
ncc-Permitted 11111111
Cell 24.

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 992
992
Table 8.3.3.3.3.3-10: ReportConfigGERAN-CGI (step 5, Table 8.3.3.3.3.2-2)
ReportConfigInterRAT ::=SEQUENCE {
purpose CHOICE {
reportCGI NULL
}
}
}
reportAmount r1
}

SEQUENCE {

maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
sf2560 0
}
}
}
phr-Config CHOICE {
release NULL
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 993
993
c1 CHOICE {
measId 2
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultListGERAN ::=SEQUENCE (SIZE
carrierFreq[1] SEQUENCE { CarrierFreq of Cell
24

arcfn Downlink arcfn of Cell 24
bandIndicator Same bandIndicator as
Cell 24

}
Cell 24

cellGlobalId SEQUENCE { CellGlobalIdentity of Cell
24

plmn-Identity PLMN Identity of Cell 24
locationAreaCode Location Area Code of
Cell 24

cellIdentity Cell Identity of Cell 24
}
routingAreaCode Routing Area Code of
Cell 24

}
rssi (0..63)
}
}
}
}
}
}
}
}

reporting of HRPD cell
(1)
ensure that {
when { UE detects that entering conditions for event B2 are met }
then { UE sends MeasurementReport for event B2 }
}
(2)
ensure that {
when { UE is commanded to report the global cell identity of the
neighbour cell }
then { UE determines the global cell identity of the cell included
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 994
994
in the associated measurement object by acquiring the
relevant system information from the concerned cell and
reports the global cell identity in the MeasurementReport }
}

5.5.2.3, 5.5.3.1 , 5.5.4.1, 5.5.4.8, 5.5.5.
[TS 36.331, clause 5.3.5.3]
[TS 36.331, clause 5.5.2.3]
The UE shall:
with this measId:
3>else:
[TS 36.331, clause 5.5.3.1]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 995
995
cell:
cell:
cell:
CDMA2000 cell and the cdma2000-Type included in the measObject is typeHRPD:
3>try to acquire the Sector ID in the concerned cell;
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>else:
this measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 996
996
measId;
event):
measId;
this event:
measId;
3>stop timer T321;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 997
997
[TS 36.331, clause 5.5.4.8]
The UE shall:
specified below, are fulfilledapply inequality B2-1 and inequality B2-2 i.e. both have to be fulfilled, as specified
below, as the entry condition for this event;
one of the two, as specified below, is fulfilledapply inequality B3-3 and inequality B2-4 i.e. at least one of the
two has to be fulfilled, as specified below, as the leaving condition for this event;
1 Thresh Hys Ms < +

1 Thresh Hys Ms >

Ms is the measurement result of the serving cell, not taking into account any cell individual offsets.
Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsetsneighbouring inter
RAT cell.
within the measObject corresponding to the frequency of the inter-RAT neighbour cell)neighbour cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT the
VarMeasurementConfiguration for this event).
Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRATthe
Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2 as defined within reportConfigInterRAT the
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbourneighbouring
inter RAT cell.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 998
998
Thresh1 is expressed in the same unit as MndBm in case Ms is expressed in dBm; otherwise it is expressed in dB.
Thresh2 is expressed in the same unit as MndBm in case Mn is expressed in dBm; otherwise it is expressed in dB.
[TS 36.331, clause 5.5.5]
the following:
measId;
3>else:
first;
5>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 999
999
1>else:
System Simulator:
Preamble:
UE:
None.
T0
Cell-specific RS EPRE dBm/15kHz -60 - The power level values are
for event B2 are not satisfied:
Inequality B2-1 (Entering
condition 1)
Ms + Hys > Thresh1
condition 2)
Mn +Ofn Hys < Thresh2
or/Ioc dB - -20
Ioc dBm/1.23MHz - -55
Pilot_Ec/Io (Note 1) dB - -20
T1
for event B2 are satisfied:

condition 1)
Ms + Hys< Thresh1
condition 2)
Mn +Ofn Hys > Thresh2
or/Ioc dB - -5
Ioc dBm/1.23MHz - -55
Pilot_Ec/Io (Note 1) dB - -6
set by the SS

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1000
1000
U - S Message
measurement and reporting for event B2 and
message.
omplete
- -
8.3.3.4.3.2-1.
- - - -
B2 on Cell 15?
Cell 15.
message.
omplete
- -

8.3.3.4.3.2-2)
Derivation Path: TS 36.508 clause 4.4.3.3-1
SEQUENCE {

LONGCYCLE

}
nB oneT
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1001
1001
}
}
}

1 entry
GENERIC

}
1 entry
CDMA2000

B2-CDMA2000(-69, -18)

}
1 entry
measId[1] 1
CDMA2000

}
}
}
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1002
1002
Table 8.3.3.4.3.3-4: MeasObjectCDMA2000-GENERIC (step 1, Table 8.3.3.4.3.2-2)
Derivation Path: TS 36.508, Table 4.6.6-1C
under test

arfcn f14
}
searchWindowSize 15
}

Derivation Path: TS 36.508, Table 4.6.1-5
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
measResultsCDMA2000 SEQUENCE {
preRegistrationStatusHRPD TRUE
measResultListCDMA2000 SEQUENCE
1 entry
}
}
}
}
}
}
}
}
}

Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS
dicated-DRX

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1003
1003
Derivation Path: TS 36.508 clause 4.6.6 table 4.6.6-1
1 entry
measId[1] 2
}
1 entry
CGI

}

reportConfigId IdReportConfig-B2
}
1 entry
reportConfig[1] ReportConfigCDMA2000-
CGI

}
}

Table 8.3.3.4.3.3-7A: MeasObjectCDMA2000-CGI (step 5, Table 8.3.3.4.3.2-2)
under test

arfcn f14
}
searchWindowSize 15
Cell 15

}

Table 8.3.3.4.3.3-8: ReportConfigCDMA2000-CGI (step 5, Table 8.3.3.4.3.2-2)
{

purpose CHOICE {
reportCGI NULL
}
}
}
reportAmount r1
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1004
1004
Derivation Path: TS 36.508 clause 4.6.3.19
SEQUENCE {

maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
sf2560 0
}
}
}
timeAlignmentTimerDedicated sf750
phr-Config CHOICE {
release NULL
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1005
1005
Derivation path: TS 36.508 4.6.1 table 4.6.1-5
c1 CHOICE{
measId 2
measResultServing SEQUENCE { Report Cell 15
rsrpResult (0..97)
rsrqResult (0..34)
}
preRegistrationStatusHRPD TRUE
1 entry
Cell 15

cgi-Info[1] CHOICE {
cellGlobalIdHRPD cellGlobalId of Cell 15
}
}
}
}
}
}
}
}
}
}

reporting of 1xRTT cell
(1)
ensure that {
when { UE detects that entering conditions for event B2 are met }
then { UE sends MeasurementReport for event B2 }
}
(2)
ensure that {
when { UE is commanded to report the global cell identity of the
neighbour cell }
then { UE determines the global cell identity of the cell included
in the associated measurement object by acquiring the
relevant system information from the concerned cell and
reports the global cell identity in the MeasurementReport }
}

5.5.2.3, 5.5.3.1 , 5.5.4.1, 5.5.4.8, 5.5.5.
[TS 36.331, clause 5.3.5.3]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1006
1006
[TS 36.331, clause 5.5.2.3]
The UE shall:
with this measId:
3>else:
[TS 36.331, clause 5.5.3.1]
The UE shall:
cell:
cell:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1007
1007
cell:
CDMA2000 cell and the cdma2000-Type included in the measObject is type1XRTT:
3>try to acquire the BASE ID, SID and NID in the concerned cell;
[TS 36.331, clause 5.5.4.1]
The UE shall:
2>else:
this measId;
measId;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1008
1008
event):
measId;
this event:
measId;
3>stop timer T321;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1009
1009
[TS 36.331, clause 5.5.4.8]
The UE shall:
specified below, are fulfilledapply inequality B2-1 and inequality B2-2 i.e. both have to be fulfilled, as specified
below, as the entry condition for this event;
one of the two, as specified below, is fulfilledapply inequality B3-3 and inequality B2-4 i.e. at least one of the
two has to be fulfilled, as specified below, as the leaving condition for this event;
1 Thresh Hys Ms < +

1 Thresh Hys Ms >

Ms is the measurement result of the serving cell, not taking into account any cell individual offsets.
Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsetsneighbouring inter
RAT cell.
within the measObject corresponding to the frequency of the inter-RAT neighbour cell)neighbour cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT the
Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRATthe
Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2 as defined within reportConfigInterRAT the
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbourneighbouring
inter RAT cell.
Thresh1 is expressed in the same unit as MndBm in case Ms is expressed in dBm; otherwise it is expressed in dB.
Thresh2 is expressed in the same unit as MndBm in case Mn is expressed in dBm; otherwise it is expressed in dB.
[TS 36.331, clause 5.5.5]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1010
1010
the following:
measId;
3>else:
first;
5>else:
1>else:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1011
1011
System Simulator:
Preamble:
UE:
None.
T0
for event B2 are not satisfied:
condition 1)
Ms + Hys > Thresh1

condition 2)
Mn +Ofn Hys < Thresh2
or/Ioc dB - -15
T1
for event B2 are satisfied:

condition 1)
Ms + Hys< Thresh1

condition 2)
Mn +Ofn Hys > Thresh2
or/Ioc dB - 0
set by the SS

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1012
1012
U - S Message
measurement and reporting for event B2 and
message.
omplete
- -
8.3.3.5.3.2-1.
- - - -
B2 on Cell 19?
Cell 19.
message.
omplete
- -

8.3.3.5.3.2-2)
Derivation Path: TS 36.508 clause 4.4.3.3-1
SEQUENCE {

LONGCYCLE

}
nB oneT
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1013
1013
}
}
}

1 entry
GENERIC

}
1 entry
CDMA2000

B2-CDMA2000(-69, -18)

}
1 entry
measId[1] 1
CDMA2000

}
}
}
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1014
1014
CarrierFreqCDMAcdma2000 SEQUENCE {
under test

arfcn f17
}
searchWindowSize 15
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
}
}
}
}
}
}
}
}
}

Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS
dicated-DRX

}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1015
1015
Derivation Path: TS 36.508 clause 4.6.6 table 4.6.6-1
1 entry
measId[1] 2
}
1 entry
CGI

}

reportConfigId IdReportConfig-B2
}

reportConfig[1] ReportConfigCDMA2000-
CGI

}
}

Table 8.3.3.5.3.3-7A: MeasObjectCDMA2000-CGI (step 5, Table 8.3.3.5.3.2-2)
CarrierFreqCDMAcdma2000 SEQUENCE {
under test

arfcn f17
}
searchWindowSize 15
Cell 19

}

Table 8.3.3.5.3.3-8: ReportConfigCDMA2000-CGI (step 5, Table 8.3.3.5.3.2-2)
{

purpose CHOICE {
reportCGI NULL
}
}
}
reportAmount r1
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1016
1016
Derivation Path: TS 36.508 clause 4.6.3.19
SEQUENCE {

maxHARQ-Tx n5
ttiBundling FALSE
}
drx-Config CHOICE {
setup SEQUENCE {
sf2560 0
}
}
}
phr-Config CHOICE {
release NULL
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1017
1017
Derivation path: TS 36.508 4.6.1 table 4.6.1-5
c1 CHOICE {
measId 2
measResultServing SEQUENCE { Report Cell 19
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 19

cgi-Info[1] CHOICE {
cellGlobalId1XRTT GlobalCellId of Cell 19
}
}
}
}
}
}
}
}
}
}

8.4 Inter-RAT handover
8.4.1
8.4.1.1 Void
8.4.1.2 Inter-RAT handover / From E-UTRA to UTRA PS / Data
(1)
ensure that {
when { UE receives a MobilityFromEUTRACommand message and a DPCH PS RAB combination is configured
for an UTRA cell}
then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra cell}
}

[TS 36.331, clause 5.4.3.3]
The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN,
even if no prior UE measurements have been performed on the target cell.
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1018
1018
1>if the MobilityFromEUTRACommand message includes the purpose set to handover:
2>if the targetRAT-Type is set to utra or geran:
3>consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in
the MobilityFromEUTRACommand message;
3>forward the nas-SecurityParamFromEUTRA to the upper layers;
3>access the target cell indicated in the inter-RAT message in accordance with the specifications of the
target RAT;
System Simulator:
UE:
None.
Preamble:
U - S Message
1 The SS configures UTRA cell 5 to reference
configuration according 36.508 table 4.8.3-1,
condition UTRA PS RB.
- - - -
MobilityFromEUTRACommand message on
Cell 1.
<-- MobilityFromEUTRACommand - -
3 Check: Does the UE transmit a HANDOVER
TO UTRAN COMPLETE message on cell 5?
--> HANDOVER TO UTRAN
COMPLETE
1 P

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1019
1019
Table 8.4.1.2.3.3-1: MobilityFromEUTRACommand (step 2, Table 8.4.1.2.3.2-1)
Derivation Path: 36.508t able 4.6.1-6
MobilityFromEUTRACommand ::=SEQUENCE {
c1 CHOICE{
mobilityFromEUTRACommand-r8 SEQUENCE {
purpose CHOICE {
handover SEQUENCE {
targetRAT-Type utra
targetRAT-MessageContainer HANDOVER TO UTRAN
COMMAND

nas-SecurityParamFromEUTRA The 4 least significant
bits of the NAS downlink
COUNT value

systemInformation Not present
}
}
}
}
}
}

Table 8.4.1.2.3.3-2: HANDOVER TO UTRAN COMMAND (Table 8.4.1.2.3.3-1)
Derivation Path: 36.508 table 4.7B.1-1, condition UTRA PS RB

8.4.1.3 Void
8.4.1.4 Inter-RAT handover / From E-UTRA to UTRA HSDPA / Data
(1)
ensure that {
when { UE receives a MobilityFromEUTRACommand message and a DPCH and HS-PDSCH PS RAB combination
is configured for an UTRA cell}
then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra cell}
}

[TS 36.331, clause 5.4.3.3]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1020
1020
target RAT;
System Simulator:
UE:
None.
Preamble:
U - S Message
1 The SS configures UTRA cell 5 to reference
configuration according 36.508 table 4.8.3-1,
condition UTRA HSDPA RB..
- - - -
Cell 1.
COMPLETE
1 P

Derivation Path: 36.508t able 4.6.1-6
c1 CHOICE{
purpose CHOICE {
handover SEQUENCE {
targetRAT-Type utra
COMMAND

COUNT value

}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1021
1021
Derivation Path: 36.508 table 4.7B.1-1, condition UTRA HSDPA RB

8.4.2
8.4.2.1 Void
8.4.2.2 Inter-RAT handover / From UTRA PS to E-UTRA / Data
(1)
with { UE in UTRA CELL_DCH(PS-DCCH+DTCH_DCH) state }
ensure that {
when { UE receives a HANDOVER FROM UTRAN COMMAND message including the eutra-Message }
then { UE transmits an RRCConnectionReconfigurationComplete message and enters E-UTRA
}

[TS 36.331, clause 5.4.2.3]
If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE
shall:
1>for the target cell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;
1>forward the nas-SecurityParamToEUTRA to the upper layers;
1>derive the K
eNB
1>derive the K
RRCint
1>derive the K
RRCenc
key and the K
UPenc
key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];
1>configure lower layers to apply the indicated integrity protection algorithm and the K
RRCint
key immediately, i.e.
the indicated integrity protection configuration shall be applied to all subsequent messages received and sent by
the UE, including the message used to indicate the successful completion of the procedure;
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1022
1022
1>configure lower layers to apply the indicated ciphering algorithm, the K
RRCenc
key and the K
UPenc
key
immediately, i.e. the indicated ciphering configuration shall be applied to all subsequent messages received and
sent by the UE, including the message used to indicate the successful completion of the procedure;
configuration;
1>use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;
2>stop timer T304;
2>enter E-UTRA RRC_CONNECTED, upon which the procedure ends;
System Simulator:
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configurations marked "T1" and "T2" are applied at the points
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-90 -
x,high
<
Srxlev
cell 5
.
CPICH Ec
dBm/3.8
4 MHz
- -65
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-70 -
that entering conditions for event 3a
are satisfied.
CPICH Ec
dBm/3.8
4 MHz
-

-100

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1023
1023
U - S Message
1.
- - - -
- - - -
3-4 Void - - - -
4A-
4E
Step 7 to 11 of test procedure in TS 34.123-1
NOTE: The UE performs Network initiated
RAB re-establishment in a UTRAN cell.
- - - -
- For UTRAN FDD, EXCEPTION: Steps 5a1
to 5a2 describe behaviour that depends on
the UE capability; the "lower case letter"
identifies a step sequence that takes place if
a capability is supported.

For UTRAN TDD, goto step8.

5a1 IF pc_UTRA_CompressedModeRequired
THEN the SS transmits a PHYSICAL
CHANNEL RECONFIGURATION message
on Cell 5 including the DPCH compressed
mode info.
RECONFIGURATION
- -
on Cell 5.
RECONFIGURATION
COMPLETE
- -
6-7 Void - - - -
8 The SS transmits a MEASUREMENT
CONTROL message to setup inter-RAT
1.
- - - -
10 The UE transmits a MEASUREMENT
REPORT message on Cell 5 including the E-
UTRA event results.
11 The SS transmits a HANDOVER FROM
UTRAN COMMAND message on Cell 5.
<-- HANDOVER FROM UTRAN
COMMAND
- -
message on Cell 1 using the security key
derived from the new K
eNB
?
omplete
1 P
12
A
NOTE: The UE performs tracking area
updating procedure without ISR and security
reconfiguration after successful completion
of handover from UTRA.
- - - -
13-
19
Void - - - -
indicate that the UE is in E-UTRA RRC
CONNECTED state on Cell 1?
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1024
1024
Table 8.4.2.2.3.3-1: Void
Table 8.4.2.2.3.3-2: SystemInformationBlockType6 for Cell 1 (preamble, Table 8.4.2.2.3.2-2)
UTRA-FDD
as used for Cell 5

p-MaxUTRA[1] 0
}
The same number of
UTRA TDD carriers
UTRA-TDD
as used for Cell 5

p-MaxUTRA[n] 0
}
}


Table 8.4.2.2.3.3-3: Void
Table 8.4.2.2.3.3-4: Void

Table 8.4.2.2.3.3-5: HANDOVER FROM UTRAN COMMAND (step 11, Table 8.4.2.2.3.2-2)
Derivation Path: 36.508, Table 4.7B.1-2

Table 8.4.2.2.3.3-6: RRCConnectionReconfiguration (Table 8.4.2.2.3.3-5)
Derivation Path: 36.508, Table 4.6.1-8, condition HO-TO-EUTRA(1,0)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1025
1025
Cell 1.

as used for Cell 1.

}
dl-Bandwidth Downlink system
bandwidth under test.

ul-Bandwidth Uplink Bandwidth under
test.
FDD
}
additionalSpectrumEmission 1
}


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1026
1026
interRAT SEQUENCE {
cipheringAlgorithm Set according to PIXIT
parameter for default
ciphering protection
algorithm

integrityProtAlgorithm Set according to PIXIT
integrity algorithm

}
nas-SecurityParamToEUTRA Octets 1 to 4 are
arbitrarily selected.

Bits 1 to 3 of octet 5 are
set according to PIXIT
integrity protection
algorithm.

ciphering algorithm.

arbitrarily selected
between '000'B and
'110'B, different from the
valid NAS key set
identifier of the UE if such
a value exists.

Bit 4 of octet 6 is set to 1.
Octets 1 to 4
include the
NonceMME value.

Bits 1 to 3 of octet
5 include the Type
of integrity
protection
algorithm

5 include the Type
of ciphering
algorithm.

6 include the NAS
key set identifier.

}
}
}

8.4.2.3 Void
8.4.2.4 Inter-RAT handover / From UTRA HSPA to E-UTRA / Data
(1)
with { UE in UTRA CELL_DCH(PS-DCCH+DTCH_HS-DSCH) state }
ensure that {
when { UE receives a HANDOVER FROM UTRAN COMMAND message including the eutra-Message }
then { UE transmits an RRCConnectionReconfigurationComplete message and enters E-UTRA
}

[TS 36.331, clause 5.4.2.3]
If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE
shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1027
1027
1>for the target cell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;
1>forward the nas-SecurityParamToEUTRA to the upper layers;
1>derive the K
eNB
1>derive the K
RRCint
1>derive the K
RRCenc
key and the K
UPenc
key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];
1>configure lower layers to apply the indicated integrity protection algorithm and the K
RRCint
key immediately, i.e.
the indicated integrity protection configuration shall be applied to all subsequent messages received and sent by
the UE, including the message used to indicate the successful completion of the procedure;
1>configure lower layers to apply the indicated ciphering algorithm, the K
RRCenc
key and the K
UPenc
key
immediately, i.e. the indicated ciphering configuration shall be applied to all subsequent messages received and
sent by the UE, including the message used to indicate the successful completion of the procedure;
configuration;
1>use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;
2>stop timer T304;
2>enter E-UTRA RRC_CONNECTED, upon which the procedure ends;
System Simulator:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1028
1028
UE:
None.
Preamble:
various time instants of the test execution. Subsequent configurations marked "T1" and "T2" are applied at the points
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-90 -
x,high
<
Srxlev
cell 5
.
CPICH Ec
dBm/3.8
4 MHz
- -65
T2
Cell-specific RS
EPRE
dBm/15k
Hz
-70 -
that entering conditions for event 3a
are satisfied.
CPICH Ec
dBm/3.8
4 MHz
-

-100

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1029
1029
U - S Message
1.
- - - -
- - - -
3-4 Void - - - -
4A-
4E
Step 7 to 11 of test procedure in TS 34.123-1
NOTE: The UE performs Network initiated
RAB re-establishment in a UTRAN cell.
- - - -
- UTRAN FDD: EXCEPTION: Steps 5a1 to
5a2 describe behaviour that depends on the
UE capability; the "lower case letter"
identifies a step sequence that takes place if
a capability is supported.

UTRAN TDD : go to step 8

5a1 IF pc_UTRA_CompressedModeRequired
THEN the SS transmits a PHYSICAL
CHANNEL RECONFIGURATION message
on Cell 5 including the DPCH compressed
mode info.
RECONFIGURATION
- -
on Cell 5.
RECONFIGURATION
COMPLETE
- -
6-7 Void - - - -
8 The SS transmits a MEASUREMENT
CONTROL message to setup inter-RAT
1.
- - - -
10 The UE transmits a MEASUREMENT
REPORT message on Cell 5 including the E-
UTRA event results.
11 The SS transmits a HANDOVER FROM
UTRAN COMMAND message on Cell 5.
<-- HANDOVER FROM UTRAN
COMMAND
- -
message on Cell 1 using the security key
derived from the new K
eNB
?
omplete
1 P
12
A
NOTE: The UE performs tracking area
updating procedure without ISR and security
reconfiguration after successful completion
of handover from UTRA.
- - - -
13-
19
Void - - - -
indicate that the UE is in E-UTRA RRC
CONNECTED state on Cell 1?
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1030
1030
Table 8.4.2.4.3.3-1: Void
Table 8.4.2.4.3.3-2: SystemInformationBlockType6 for Cell 1 (preamble, Table 8.4.2.4.3.2-2)
UTRA-FDD
as used for Cell 5

p-MaxUTRA[n] 0
}
UTRA-TDD
as used for Cell 5

p-MaxUTRA[n] 0
}
}


Table 8.4.2.4.3.3-3: Void
Table 8.4.2.4.3.3-4: Void
Table 8.4.2.4.3.3-5: HANDOVER FROM UTRAN COMMAND (step 11, Table 8.4.2.4.3.2-2)
Derivation Path: 36.508, Table 4.7B.1-2

Table 8.4.2.4.3.3-6: RRCConnectionReconfiguration (Table 8.4.2.4.3.3-5)
Derivation Path: 36.508, Table 4.6.1-8, condition HO-TO-EUTRA(1,0)

Cell 1.

as used for Cell 1.

}
dl-Bandwidth Downlink system
bandwidth under test.

ul-Bandwidth Uplink Bandwidth under
test.
FDD
}
additionalSpectrumEmission 1
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1031
1031

interRAT SEQUENCE {
cipheringAlgorithm Set according to PIXIT
ciphering protection
algorithm

integrityProtAlgorithm Set according to PIXIT
integrity algorithm

}
nas-SecurityParamToEUTRA Octets 1 to 4 are
arbitrarily selected.

algorithm.

ciphering algorithm.

arbitrarily selected
between '000'B and
'110'B, different from the
valid NAS key set
identifier of the UE if such
a value exists.

Bit 4 of octet 6 is set to 1.
Octets 1 to 4
include the
NonceMME value.

5 include the Type
of integrity
protection
algorithm

5 include the Type
of ciphering
algorithm.

6 include the NAS
key set identifier.

}
}
}

8.4.2.5 Void
8.4.2.6 Void
8.4.3
8.4.3.1 Void
8.4.3.2 Inter-RAT cell change order / From E-UTRA data RRC_CONNECTED to
GPRS / Without NACC
(1)
with { UE in E-UTRA (data) RRC_CONNECTED state }
ensure that {
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1032
1032
when { UE receives a MobilityFromEUTRACommand message including information facilitating access of
the target cell }
then { UE successfully completing the cell change order and leaves the RRC_CONNECTED,enter the
GPRS_Paccket_Idle}
}

8.4.3.2.2 Conformance requirements[D]
5.4.3.4.
[TS 36.331, clause 5.4.3.3]
The UE shall:
target RAT;
3>if the targetRAT-Type is set to geran:
4>use the contents of systemInformation, if provided for PS Handover, as the system information to
begin access on the target GERAN cell;
NOTE 1: If there are DRBs for which no radio bearers are established in the target RAT as indicated in the
targetRAT-MessageContainer in the message, the E-UTRA RRC part of the UE does not indicate the
release of the concerned DRBs to the upper layers. Upper layers may derive which bearers are not
established from information received from the AS of the target RAT.
2>else if the targetRAT-Type is set to cdma2000-1XRTT or cdma2000-HRPD:
3>forward the targetRAT-Type and the targetRAT-MessageContainer to the CDMA2000 upper layers for
the UE to access the cell indicated in the inter-RAT message in accordance with the specifications of the
CDMA2000 target-RAT;
1>else if the MobilityFromEUTRACommand message includes the purpose set to cellChangeOrder:
2>start timer T304 with the timer value set to t304, as included in the MobilityFromEUTRACommand message;
3>if networkControlOrder is included in the MobilityFromEUTRACommand message:
4>apply the value as specified in TS 44.060 [36];
3>else:
4>acquire networkControlOrder and apply the value as specified in TS 44.060 [36];
3>use the contents of systemInformation, if provided, as the system information to begin access on the target
GERAN cell;
NOTE 2: The systemInformation is constructed in the same way as in 2G to 2G NACC, i.e. the PSI messages are
encoded as such, whereas the SI messages exclude 2 octets of headers, see TS 44.060[36].
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1033
1033
2>establish the connection to the target cell indicated in the CellChangeOrder;
NOTE 3: The criteria for success or failure of the cell change order to GERAN are specified in TS 44.060[36].
[TS 36.331, clause 5.4.3.4]
Upon successfully completing the handover or the cell change order, the UE shall:
1>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause other;
System Simulator:
- Cell 1and Cell 24 - Cell 1 is an E-UTRAN cell, Cell 24 is a GERAN cell.
- All cells belong to the same PLMN.
UE:
- None.
Preamble:
- UE is in state3 (Generic RB Established)in cell 1 as specified in clause 4.5.3 of TS 36.508.
various time instants of the test execution. Row marked "T0" denotes the initial condition after preamble, while
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
-
RSSI dBm - [-85]
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-80 -
-
RSSI dBm - [-65]

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1034
1034
U - S Message
omplete
- -
3 The SS changes Cell 1and Cell 24 parameters
- - - -
4 The UE transmit a MeasurementReport
message to report the event B2 for Cell 24.
Cell 1.
24?
- - 1 P


1 entry
GENERIC(f11)

}
1 entry
GERAN

B2-GERAN(-69, [-79])

}
1 entry
measId[1] 1
GERAN

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1035
1035
TransactionIdentifi
er-DL

c1 CHOICE {
mobilityFromEUTRACommand-r8::=SEQUENCE {
csFallbackIndicator False
purpose CHOICE {
cellChangeOrder::=SEQUENCE {
t304 ms1000
targetRAT-Type CHOICE{
geran::=SEQUENCE {
physCellId 0001H
carrierFreq ::=SEQUENCE {
arfcn Downlink ARFCN
of Cell 24

bandIndicator The same band
indicator of the
Cell 24

}
}
}
}
}
}
}
}
}

8.4.3.3 Inter-RAT cell change order / From E-UTRA data to GPRS / With NACC
(1)
with { UE in E-UTRA (data) RRC_CONNECTED state }
ensure that {
when { UE receives a MobilityFromEUTRACommand message including information facilitating access of
the target cell }
then { UE successfully completing the cell change order and leaves the RRC_CONNECTED,enter the
GPRS_Paccket_Idle}
}

8.4.3.3.2 Conformance requirements[D]
5.4.3.4.
[TS 36.331, clause 5.4.3.3]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1036
1036
target RAT;
4>use the contents of systemInformation, if provided for PS Handover, as the system information to
begin access on the target GERAN cell;
NOTE 1: If there are DRBs for which no radio bearers are established in the target RAT as indicated in the
targetRAT-MessageContainer in the message, the E-UTRA RRC part of the UE does not indicate the
release of the concerned DRBs to the upper layers. Upper layers may derive which bearers are not
established from information received from the AS of the target RAT.
1>else if the MobilityFromEUTRACommand message includes the purpose set to cellChangeOrder:
2>start timer T304 with the timer value set to t304, as included in the MobilityFromEUTRACommand message;
3>if networkControlOrder is included in the MobilityFromEUTRACommand message:
4>apply the value as specified in TS 44.060 [36];
3>else:
4>acquire networkControlOrder and apply the value as specified in TS 44.060 [36];
3>use the contents of systemInformation, if provided, as the system information to begin access on the target
GERAN cell;
NOTE 2: The systemInformation is constructed in the same way as in 2G to 2G NACC, i.e. the PSI messages are
encoded as such, whereas the SI messages exclude 2 octets of headers, see TS 44.060[36].
2>establish the connection to the target cell indicated in the CellChangeOrder;
NOTE 3: The criteria for success or failure of the cell change order to GERAN are specified in TS 44.060[36].
[TS 36.331, clause 5.4.3.4]
Upon successfully completing the handover or the cell change order, the UE shall:
System Simulator:
- Cell 1and Cell 24 - Cell 1 is an E-UTRAN cell, Cell 24 is a GERAN cell.
- All cells belong to the same PLMN.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1037
1037
UE:
- None.
Preamble:
- UE is in state3 (Generic RB Established)in cell 1 as specified in clause 4.5.3 of TS 36.508.
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-60 -
-
RSSI dBm - [-85]
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-80 -
-
RSSI dBm - [-65]

U - S Message
omplete
- -
3 The SS changes Cell 1and Cell 24 parameters
- -
4 The UE transmit a MeasurementReport
message to report the event B2 for Cell 24.
Cell 1.
24?
- - 1 P


Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1038
1038
1 entry
GENERIC(f11)

}
1 entry
GERAN

B2-GERAN(-69, [-79])

}
1 entry
measId[1] 1
GERAN

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1039
1039
TransactionIdentifi
er-DL

c1 CHOICE {
mobilityFromEUTRACommand-r8::=SEQUENCE {
purpose CHOICE {
cellChangeOrder::=SEQUENCE {
t304 ms1000
targetRAT-Type CHOICE{
geran::=SEQUENCE {
physCellId 0001H
carrierFreq ::=SEQUENCE {
arfcn Downlink ARFCN
of Cell 24

bandIndicator The same band
indicator of the
Cell 24

}
networkControlOrder 00 NC0: MS
controlled cell re-
selection, no
measurement
reporting

systemInformation FFS As specified in TS
44.060

}
}
}
}
}
}
}
}

8.4.4 Void
8.4.5 Inter-RAT handover E-UTRA to HRPD
8.4.5.1 Void
8.4.5.2 Void
8.4.5.3 Void
8.4.5.4 Pre-registration at HRPD and inter-RAT handover / From E-UTRA to HRPD
Active / Data
(1)
with { UE in E-UTRA RRC_CONNECTED state and UE has performed pre-registration on HRPD neighbor
cell }
ensure that {
when { UE receives a HandoverFromEUTRAPreparationRequest message with cdma2000-type set to
HRPD }
then { UE transmits a ULHandoverPreparationTransfer message containing a tunneled HRPD
ConnectionRequest message }
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1040
1040
}
(2)
with { UE in E-UTRA RRC_CONNECTED state and UE has performed pre-registration on HRPD neighbor
cell }
ensure that {
when { UE receives a MobilityFromEUTRACommand message containing a tunneled HRPD
TrafficChannelAssignment message }
then { UE transmits a TrafficChannelComplete message on the target HRPD cell }
}

5.4.4.3, 5.4.5.1 and 5.4.5.3, TS 23.402, clause 9.3.2 and 3GPP2 X.S0057-0, clause 13.1.2.
[TS 36.331, clause 5.4.3.3]
The UE shall:

[TS 36.331, clause 5.4.4.3]
Upon reception of the HandoverFromEUTRAPreparationRequest message, the UE shall:
1>indicate the request to prepare handover and forward the cdma2000-Type to the CDMA2000 upper layers;
1>if cdma2000-Type is set to type1XRTT:
2>forward the rand and the mobilityParametersCDMA2000 to the CDMA2000 upper layers;
[TS 36.331, clause 5.4.5.1]

ULHandoverPreparationTransfer
UE EUTRAN

Figure 5.4.5.1-1: UL handover preparation transfer

The purpose of this procedure is to tunnel the handover related CDMA2000 dedicated information from UE
to E-UTRAN when requested by the higher layers. The procedure is triggered by the higher layers on
receipt of HandoverFromEUTRAPreparationRequest message. This procedure applies to CDMA2000
capable UEs only.
[TS 36.331, clause 5.4.5.3]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1041
1041
The UE shall set the contents of the ULHandoverPreparationTransfer message as follows:
1>include the cdma2000-Type and the dedicatedInfoCDMA2000;
1>if the cdma2000-Type is set to type1XRTT:
2>include the meid and set it to the value received from the CDMA2000 upper layers;
1>submit the ULHandoverPreparationTransfer message to lower layers for transmission, upon which the
procedure ends;
[TS 23.402, clause 9.3.2]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1042
1042
Figure 9.3.2-1 illustrates a high-level call flow for the optimised E-UTRAN to HRPD handover procedure, Handover
phase. The prerequisite of the handover phase is the successfully performed Pre-registration phase as it is specified in
clause 9.3.1.

1. CDMA measurements
3. Handover from E-UTRA preparation request
7. A11 Signalling
11. Data Forwarding
13. HRPD TCC
16. UE Context Release
15a. Notification Request (HO Complete)
0. UE connected via E-UTRAN

2. Handover
decision
6. Direct Transfer Request
9a. Create forwarding tunnels Request

9b. Create forwarding tunnels Response
10. Downlink S1 CDMA2000 Tunneling
11. Mobility from E-UTRA
17a. Delete Bearer Request
17b. Delete Bearer Response
4. UL handover preparation transfer
5. Uplink S1 CDMA2000 Tunneling
8. Direct Transfer Request
UE MME
HRPD Access
Network AAA HSGW E-UTRAN PCRF S-GW
PDN
GW
14b. Proxy Binding Update
14a. A11 Request Signalling
14c. Proxy Binding Acknowledge
15b. Notification Response
12. HRPD AN acquires UE

14d. A11 Response Signalling
18. P-GW initiates resource allocation deactivation procedure at E-UTRAN
14e. PCEF Initiated IP-CAN Session
Modification Procedure

Figure 9.3.2-1: E-UTRAN to HRPD handover

[3GPP2 X.S0057-0, clause 13.1.2]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1043
1043
UE eAN/ePCF HSGW
3GPP2
AAA
P-GW
HSS/
AAA
1a. Decision to
handover to
HRPD
vPCRF
3GPP AAA
Proxy
hPCRF eNB
0. Attached to E-UTRAN (UE has preregistered on HRPD)
S-GW MME
1b. HRPD Conn. Req.
1c. S101( HRPD Conn.
Req., P-GW
Address(es), GRE
Key(s) )
2a. A11-RRQ (P-GW
Address(es), GRE
Key(s) )
2b. A11-RRP (HSGW
Address, GRE Key )
3. S101 (HRPD TCA,
HSGW Address, GRE Key)
4a. Create forwarding tunnel (HSGW
Address, GRE Key)
4b. HRPD TCA
5. Indirect data forwarding over S103-U (optional)
6a. UE acquires HRPD Radio
6b. HRPC TCC
7b. A11-RRP
7a. A11-RRQ
(Active Start)
8b. Proxy Binding Update
Ack (UE IPv4 address or
IPv6 prefix)
8a. Proxy Binding Update
8c. Modify IP-CAN Session/Ack
8d. S101 HO
complete
Indication/Ack
9. IP Packets Flowing 9. IP Packets Flowing 9. IP Packets Flowing
10. 3GPP EPS Resource Release
Roaming

Figure 9.3.2-2

System Simulator:
UE:
None.
Preamble:
- The UE has performed HRPD pre-registration on Cell 15.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1044
1044
various time instants of the test execution. Row marked "T0" denotes the initial conditions, while row marked "T1" is to
clause.
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-75 -
guaranteed. or/Ioc dB - -20
Ioc
dBm/1.23
MHz
- -55
Pilot Ec/Io (Note
1)
dB - -20
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-80 -
on Cell 15 are satisfied. or/Ioc dB - -5
Ioc
dBm/1.23
MHz
- -55
Pilot Ec/Io (Note
1)
dB - -6

U - S Message
Cell 1 to setup inter RAT measurement on
Cell 15.
message on Cell 1 to confirm the setup of
inter RAT measurement.
omplete
- -
8.4.5.4.3.2-1.
- - - -
message on Cell 1 to report event B2 for Cell
15,
HandoverFromEUTRAPreparationRequest
on Cell 1.
<-- HandoverFromEUTRAPreparation
Request
- -
6 Check: Does the UE transmit a tunneled
HRPD Connection Request message
contained in an
ULHandoverPreparationTransfer message
on Cell 1?
--> ULHandoverPreparationTransfer 1 P
7 The SS transmits a tunneled HRPD Traffic
Channel Assignment message contained in
a MobilityFromEUTRACommand on Cell1 to
order the UE to perform inter RAT handover
to Cell 15.
8 The UE tunes to HRPD radio. - - - -
9 Check: Does the UE transmit a Traffic
Channel Complete message on Cell 15?
--> Traffic Channel Complete 2 P

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1045
1045

1 entry
GENERIC

}
1 entry
CDMA2000

B2-CDMA2000(-69, -18)

}
1 entry
measId[1] 1
CDMA2000

}
}
}
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1046
1046
under test

arfcn f14
}
SearchWindowSize 15
offsetFreq db0
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry Note 1
Cell 15

}
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1047
1047
Table 8.4.5.4.3.3-5: HandoverFromEUTRAPreparationRequest (step 5, Table 8.4.5.4.3.2-2)
HandoverFromEUTRAPreparationRequest ::=
SEQUENCE {

c1 CHOICE {
handoverFromEUTRAPreparationRequest-r8
SEQUENCE {

cdma2000-Type typeHRPD
rand Not present
mobilityParameters Not present
}
}
}
}

Table 8.4.5.4.3.3-6: ULHandoverPreparationTransfer (step 6, Table 8.4.5.4.3.2-2)
ULHandoverPreparationTransfer ::=SEQUENCE {
c1 CHOICE {
ulHandoverPreparationTransfer-r8 SEQUENCE {
cdma2000-Type typeHRPD
meid Not present
dedicatedInfo Set according to Table
8.4.5.4.3.3-7
HRPD Connection
Request

}
}
}
}

Table 8.4.5.4.3.3-7: HRPD Connection Request (step 6, Table 8.4.5.4.3.2-2)
MessageID 0000001
TransactionID Any allowed value 8 bit field
RequestReason 0000 Access Terminal
Initiated

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1048
1048
c1 CHOICE{
purpose CHOICE{
handover SEQUENCE {
targetRAT-Type cdma2000-HRPD
targetRAT-MessageContainer Set according to Table
8.4.5.4.3.3-8
HRPD Traffic
Channel
Assignment

}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1049
1049
Table 8.4.5.4.3.3-9: HRPD Traffic Channel Assignment (step 7, Table 8.4.5.4.3.2-2)
MessageID 00000001
MessageSequence Set by SS 8 bit field
ChannelIncluded 1 Channel record
included

Channel FFS channel record for
Cell 15

FrameOffset FFS frame offset for
Cell 15

DRCLength FFS DRCLength for
Cell 15

DRCChannelGainBase FFS ratio of the power
level of the DRC
Channel (when it is
transmitted) to the
power level of the
Reverse Traffic
Pilot Channel
expressed as 2's
complement value
in units of 0.5 dB

ACKChannelGain FFS ratio of the power
level of the Ack
Channel (when it is
transmitted) to the
power level of the
Reverse Traffic
Pilot Channel
expressed as 2's
complement value
in units of 0.5 dB

NumPilots 1
PilotPN FFS PN Offset of target
sector (Cell 15)

SofterHandoff 0 Set to 0since only
1 pilot included in
message

MACIndexLSBs Set by SS 6 least significant
bits of the
MACIndex
assigned to UE

DRCCover FFS index of the DRC
cover associated
with target sector
(Cell 15)

RABLength FFS 2 bit field
RABOffset FFS 3 bit field

Table 8.4.5.4.3.3-10: HRPD Traffic Channel Complete (step 9, Table 8.4.5.4.3.2-2)
MessageID 00000010
MessageSequence Same value as
MessageSequence in
HRPD Traffic Channel
Assignment message
(Table 8.4.5.4.3.3-9)

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1050
1050
8.4.6 Void
8.4.7 Inter-RAT handover E-UTRA to 1xRTT
8.4.7.1 Inter-RAT handover / SRVCC from E-UTRA to 1xRTT(CS) / Speech
(1)
ensure that {
when { UE receives a HandoverFromEUTRAPreparationRequest message with cdma2000-type set to
type1XRTT }
then { UE transmits an ULHandoverPreparationTransfer message containing a tunneled 1xRTT
Origination message }
}

(2)
ensure that {
when { UE receives a MobilityFromEUTRACommand message containing a tunneled 1xRTT Handoff
Direction message }
then { UE transmits a 1xRTT Handoff Completion message on the target 1xRTT cell }
}

5.4.4.3, 5.4.5.1 and 5.4.5.3, TS 23.216, clause 6.1.3 and 3GPP2 X.S0042-A, clause 4.5.1.
[TS 36.331, clause 5.4.3.3]
The UE shall:

[TS 36.331, clause 5.4.4.3]
Upon reception of the HandoverFromEUTRAPreparationRequest message, the UE shall:
1>indicate the request to prepare handover and forward the cdma2000-Type to the CDMA2000 upper layers;
1>if cdma2000-Type is set to type1XRTT:
2>forward the rand and the mobilityParametersCDMA2000 to the CDMA2000 upper layers;
[TS 36.331, clause 5.4.5.1]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1051
1051

ULHandoverPreparationTransfer
UE EUTRAN

Figure 5.4.5.1-1: UL handover preparation transfer

The purpose of this procedure is to tunnel the handover related CDMA2000 dedicated information from UE to E-
UTRAN when requested by the higher layers. The procedure is triggered by the higher layers on receipt of
HandoverFromEUTRAPreparationRequest message. This procedure applies to CDMA2000 capable UEs only.
[TS 36.331, clause 5.4.5.3]
The UE shall set the contents of the ULHandoverPreparationTransfer message as follows:
1>include the cdma2000-Type and the dedicatedInfoCDMA2000;
1>if the cdma2000-Type is set to type1XRTT:
2>include the meid and set it to the value received from the CDMA2000 upper layers;
1>submit the ULHandoverPreparationTransfer message to lower layers for transmission, upon which the
procedure ends;
[TS 23.216, clause 6.1.3]
Figure 6.1.3-1 illustrates a high-level call flow for the E-UTRAN-to-1x voice service continuity procedure.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1052
1052
1xCS
SRVCC
UE
eNB MME
1xCS
IWS
1xRTT
MSC

. -

12. 1x radio interface procedures to acquire a traffic channel
13. 1x handoff completion message
1. Ongoing VoIP session over the IMS access leg established over E-UTRA access
3. Handover decision
15. Ongoing voice call over the CS access leg established over 1xRTT access
4. HO from EUTRA preparation
request (3G1x Parameters)
6. UL S1 cdma2000 tunnelling
(MEID, RAND, 1x Origination) 7. S102 Direct Transfer (1x Air
Interface Signalling (Origination))
9. S102 Direct Transfer (1x Air Interface
Signalling (Handoff Direction))
10. DL cdma2000 tunnelling
(Handoff Direction)
11. Mobility from EUTRA
command (Handoff Direction)
18. S1 UE Context Release
8. 1x traffic assignment/handoff initiation
14. 1x handoff done
16. S1 UE Context
Release Request
S-GW
1xRTT
CS
access
17. Suspend Request/Ack
2.Measurement Reports
5. UL Handover prep. transfer
(MEID, 1x Origination)

Figure 6.1.3-1: LTE VoIP-to-1x CS voice service continuity

1. Ongoing VoIP session over the IMS access leg established over EPS/E-UTRAN access.
2. 1xCS SRVCC UE sends measurement reports to eNodeB.
3. The E-UTRAN (e.g., based on some trigger, measurement reports) makes a determination to initiate an
inter-technology handover to cdma2000 1xRTT.
4. The E-UTRAN signals the UE to perform an inter-technology handover by sending a Handover from EUTRA
Preparation Request (3G1x Overhead Parameters, RAND value) message.
5. The UE initiates signalling for establishment of the CS access leg by sending a UL handover preparation
message containing the 1xRTT Origination message.
6. The E-UTRAN sends an Uplink S1 cdma2000 Tunnelling (MEID, RAND, 1x Origination, Reference CellID)
message to the MME. The eNodeB will also include CDMA2000 HO Required Indication IE to Uplink S1
CDMA2000 Tunnelling message, which indicates to the MME that the handover preparation has started.
7. Upon reception of the Uplink S1 cdma2000 Tunnelling message, the MME selects a 3GPP2 1xCS IWS based on
Reference CellID and encapsulates the 1x Origination Message along with the MEID and RAND in a S102
Direct Transfer message (as "1x Air Interface Signalling").
8. The traffic channel resources are established in the 1x RTT system and 3GPP2 1xCS procedures for initiation of
Session Transfer are performed as per 3GPP2 X.S0042 [4].
NOTE 1: Step 9 and 3GPP2 1xCS procedures in step 8 are independent of each other.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1053
1053
NOTE 2: The "VDN" parameter referred to in 3GPP2 X.S0042 [4] corresponds to the STN-SR parameter defined
in TS 23.237 [14].
9. The 3GPP2 1xCS IWS creates a 1x message and encapsulates it in a S102 Direct Transfer message (1x ,
Handover indication). If the 3GPP2 access was able to allocate resources successfully, the 1x message is a 1x
Handover Direction message and the handover indicator indicates successful resource allocation. Otherwise, the
handover indicator indicates to the MME that handover preparation failed and the embedded 1x message
indicates the failure to the UE.
10. The MME sends the 1x message and CDMA2000 HO Status IE in a Downlink S1 cdma2000 Tunnelling
message to the E-UTRAN. The CDMA2000 HO Status IE is set according to the handover indicator received
over the S102 tunnel.
11. If the CDMA2000 HO Status IE indicates successful handover preparation, the E-UTRAN forwards the 1x
Handoff Direction message embedded in a Mobility from EUTRA Command message to the UE. This is
perceived by the UE as a Handover Command message. If handover preparation failed, DL Information transfer
message will be sent instead, with the embedded 1xRTT message that indicates the failure to the UE.
12. Once the UE receives the traffic channel information from the cdma2000 1xRTT system, the UE retunes to the
1xRTT radio access network and performs traffic channel acquisition with the 1xRTT CS access (e.g., 1xRTT
BSS).
13. The UE sends a 1xRTT handoff completion message to the 1xRTT CS access (e.g., 1xRTT BSS).
14. The 1xRTT CS Access sends message to 1xRTT MSC to indicate of handoff done. The resources between 1x CS
IWS and 1xRTT MSC may be released at this step.
15. Ongoing voice call over the CS access leg established over 1xRTT access. The E-UTRAN/EPS context may be
released based on the normal E-UTRAN/EPS procedure.
16. The eNodeB sends an S1 UE Context Release Request (Cause) message to the MME. Cause indicates the S1
release procedure is caused by handover from E-UTRAN to 1xRTT.
17. The MME exchanges Suspend Request/ Acknowledge messages with the Serving GW. The S1-U bearers are
released for all EPS bearers and the GBR bearers are deactivated by the MME. The non-GBR bearers are
preserved and are marked as suspended in the S-GW. Upon receipt of downlink data the S-GW should not send a
downlink data notification message to the MME.
18. S1 UE Context in the eNodeB is released as specified in TS 23.401 [2].
[3GPP2 X.S0042-A, clause 4.5.1]
Figure 16 illustrates a detailed call flow for the single radio VoIP-to-1x CS voice DT procedure.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1054
1054

Pre-condition:
It is assumed that initially there is an IMS VoIP call setup between a single radio, dual mode UE 1 and the Other End
Point (OEP). SIP call dialog 1 for this voice call is illustrated by a heavy dashed double arrow between the VCC AS and
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1055
1055
the OEP. SIP call dialog 2 for this voice call is illustrated by a heavy dashed double arrow between the VCC AS and
UE 1. The voice bearer path is illustrated by a heavy solid double arrow between UE 1 and the OEP.
1. UE 1 and the packet data AN interact to initiate a DT. See [A.S0008] and [A.S0009] or SRVCC] for signaling
details.
2. UE 1 sends a 1x call origination to the MSC/VLR via the packet data AN (and optionally, the 1x BS) and
includes the VDN. The specific messages and any acknowledgements are not shown for brevity. See [A.S0008]
and [A.S0009] or [SRVCC] for signaling details.
NOTE 1: steps 3-6 are optional, depending on whether the UE 1 has previously been 1xCS registered and
authenticated.
3. The Visited MSC/VLR may initiate a 1x registration procedure on behalf of UE 1. The Visited MSC sends a
MAP AUTHREQ message to UE 1s HLR to authenticate UE 1 prior to allowing registration and prior to
allocating a 1x traffic channel to UE 1.
4. UE 1s HLR responds by sending an MAP authreq message to the Visited MSC.
5. The Visited MSC sends an MAP REGNOT message to UE 1s HLR.
6. UE 1s HLR responds by sending an MAP regnot message to the Visited MSC.
NOTE 2: Steps 7-8 are shown using the MAP ORREQ operation. Optionally, a post digit analysis trigger using the
MAP ANLYZD operation may be used instead to obtain routing information for the DT.
NOTE 3: If either origination triggers are not supported by the MSC/VLR or origination triggers are not armed for
this subscriber, proceed to Step 9.
7. Once the visited MSC/VLR has obtained the service profile for the originating subscriber (i.e., by Step 4), the
Visited MSC/VLR invokes a call origination trigger to obtain routing information. The Visited MSC/VLR sends
a MAP RREQ message to the WIN SCP (or to the HLR), containing the Calling Party Number (MDN) of UE 1
(derived from the IMSI) and the Called Party Number from the call origination. The WIN SCP (or HLR) sends
the ORREQ message on to the VCC AS. Optionally, the Visited MSC/VLR may send the ORREQ message
directly to a VCC AS that has an integrated WIN SCP function.
8. The VCC AS determines that this is a DT scenario based on the VDN in the Called Party Number (and the
Calling Party Number) in the ORREQ message, and then allocates an IMS Routing Number, which is an E.164
temporary routing number associated with this DT. The VCC AS then sends back the MAP orreq message to
WIN SCP (or HLR), which returns the orreq message to the MSC/VLR. Optionally, the VCC AS has an
integrated WIN SCP function and sends the orreq message directly to the MSC/VLR.
9. Anytime after Step 2 the MSC/VLR sends a 1x traffic assignment/handoff initiation to UE 1 via the packet data
AN and the packet data air interface. This instructs UE 1 to perform the handoff and acquire the 1x traffic
channel. See [A.S0008] and [A.S0009] or [SRVCC] for signaling details.
10. The 1x BS acquires UE 1s reverse traffic channel and the voice path is established with the MSC.
System Simulator:
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1056
1056
clause.
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-75 -
Cell 19 is off.
or/Ioc dB - -
Pilot Ec/Ior dB - -
Ioc
dBm/1.23
MHz
- -
Pilot Ec/Io (Note
1)
dB - -
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-75 -
on Cell 19 are satisfied. or/Ioc dB - 0
Pilot Ec/Ior dB - -7
Ioc
dBm/1.23
MHz
- -75
Pilot Ec/Io (Note
1)
dB - -10

U - S Message
Cell 1 to setup inter RAT measurement on
Cell 19.
message on Cell 1 to confirm the setup of
inter RAT measurement.
omplete
- -
8.4.7.1.3.2-1.
- - - -
19,
HandoverFromEUTRAPreparationRequest
on Cell 1.
<-- HandoverFromEUTRAPreparation
Request
- -
6 Check: Does the UE transmit a tunneled
1xRTT Origination message contained in an
ULHandoverPreparationTransfer message
on Cell 1?
--> ULHandoverPreparationTransfer 1 P
7 The SS transmits a tunneled 1xRTT Handoff
Direction message contained in a
MobilityFromEUTRACommand on Cell1 to
order the UE to perform inter RAT handover
to Cell 19.
8 The UE tunes to 1xRTT radio. - - - -
9 Check: Does the UE transmit a 1xRTT
Handoff Completion message on Cell 19?
--> Handoff Completion 2 P

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1057
1057

1 entry
GENERIC

}
1 entry
CDMA2000

B2-CDMA2000(-69, -18)

}
1 entry
measId[1] 1
CDMA2000

}
quantityConfigEUTRA Not present
quantityConfigUTRA Not present
quantityConfigGERAN Not present
quantityConfigCDMA2000 SEQUENCE { Not present
}
}
activate SEQUENCE {
gapPattern CHOICE {
gp1 SEQUENCE {
gapOffset 0
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1058
1058
under test

arfcn f17
}
SearchWindowSize 15
offsetFreq db0
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 19

}
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1059
1059
Table 8.4.7.1.3.3-5: HandoverFromEUTRAPreparationRequest (step 5, Table 8.4.7.1.3.2-2)
HandoverFromEUTRAPreparationRequest ::=
SEQUENCE {

c1 CHOICE {
handoverFromEUTRAPreparationRequest-r8
SEQUENCE {

Rand Set by SS Random
Challenge Data as
broadcast on Cell
19

mobilityParameters Set according to Table
8.4.7.1.3.3-6
3G1x Overhead
Parameters

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1060
1060
Table 8.4.7.3.3.3-6: mobilityParameters (step 5, Table 8.4.7.1.3.2-2)
Field Value/remark Comment Condition
SIDIncluded FFS
SID FFS
NIDIncluded FFS
NID FFS
REG_ZONEIncluded FFS
REG_ZONE FFS
TOTAL_ZONESIncluded FFS
TOTAL_ZONES FFS
ZONE_TIMERIncluded FFS
ZONE_TIMER FFS
PACKET_ZONE_IDIncluded FFS
PACKET_ZONE_ID FFS
PZIDHystParametersIncluded FFS
PZ_HYST_ENABLED FFS
PZ_HYST_INFO_INCL FFS
PZ_HYST_LIST_LEN FFS
PZ_HYST_ACT_TIMER FFS
PZ_HYST_TIMER_MUL FFS
PZ_HYST_TIMER_EXP FFS
P_REVIncluded FFS
P_REV FFS
NEG_SLOT_CYCLE_INDEX_SUPIncluded FFS
NEG_SLOT_CYCLE_INDEX_SUP FFS
ENCRYPT_MODEIncluded FFS
ENCRYPT_MODE FFS
ENC_SUPPORTEDIncluded FFS
ENC_SUPPORTED FFS
SIG_ENCRYPT_SUPIncluded FFS
SIG_ENCRYPT_SUP FFS
MSG_INTEGRITY_SUPIncluded FFS
MSG_INTEGRITY_SUP FFS
SIG_INTEGRITY_SUP_INCLIncluded FFS
SIG_INTEGRITY_SUP_INCL FFS
SIG_INTEGRITY_SUPIncluded FFS
SIG_INTEGRITY_SUP FFS
AUTHIncluded FFS
AUTH FFS
MAX_NUM_ALT_SOIncluded FFS
MAX_NUM_ALT_SO FFS
USE_SYNC_IDIncluded FFS
USE_SYNC_ID FFS
MS_INIT_POS_LOC_SUP_INDIncluded FFS
MS_INIT_POS_LOC_SUP_IND FFS
MOB_QOSIncluded FFS
MOB_QOS FFS
BAND_CLASS_INFO_REQIncluded FFS
BAND_CLASS_INFO_REQ FFS
ALT_BAND_CLASSIncluded FFS
ALT_BAND_CLASS FFS
MAX_ADD_SERV_INSTANCEIncluded FFS
MAX_ADD_SERV_INSTANCE FFS
HOME_REGIncluded FFS
HOME_REG FFS
FOR_SID_REGIncluded FFS
FOR_SID_REG FFS
FOR_NID_REGIncluded FFS
FOR_NID_REG FFS
POWER_UP_REGIncluded FFS
POWER_UP_REG FFS
POWER_DOWN_REGIncluded FFS
POWER_DOWN_REG FFS
PARAMETER_REGIncluded FFS
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1061
1061
PARAMETER_REG FFS
REG_PRDIncluded FFS
REG_PRD FFS
REG_DISTIncluded FFS
REG_DIST FFS
PREF_MSID_TYPEIncluded FFS
PREF_MSID_TYPE FFS
EXT_PREF_MSID_TYPEIncluded FFS
EXT_PREF_MSID_TYPE FFS
MEID_REQDIncluded FFS
MEID_REQD FFS
MCCIncluded FFS
MCC FFS
IMSI_11_12Included FFS
IMSI_11_12 FFS
IMSI_T_SUPPORTEDIncluded FFS
IMSI_T_SUPPORTED FFS
RECONNECT_MSG_INDIncluded FFS
RECONNECT_MSG_IND FFS
RER_MODE_SUPPORTEDIncluded FFS
RER_MODE_SUPPORTED FFS
TKZ_MODE_SUPPORTEDIncluded FFS
TKZ_MODE_SUPPORTED FFS
TKZ_IDIncluded FFS
TKZ_ID FFS
PILOT_REPORTIncludedPILOT_REPORT FFS
PILOT_REPORT FFS
SDB_SUPPORTEDIncluded FFS
SDB_SUPPORTED FFS
AUTO_FCSO_ALLOWEDIncluded FFS
AUTO_FCSO_ALLOWED FFS
SDB_IN_RCNM_INDIncluded FFS
SDB_IN_RCNM_IND FFS
FPC_FCH_Included FFS
FPC_FCH_INIT_SETPT_RC3 FFS
T_ADD_Included FFS
T_ADD FFS
PILOT_INC_Included FFS
PILOT_INC FFS

Table 8.4.7.1.3.3-7: ULHandoverPreparationTransfer (step 6, Table 8.4.7.1.3.2-2)
ULHandoverPreparationTransfer ::=SEQUENCE {
c1 CHOICE {
ulHandoverPreparationTransfer-r8 SEQUENCE {
Meid UEs meid
dedicatedInfo Set according to Table
8.4.7.1.3.3-8
1xRTT Origination
message

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1062
1062
Table 8.4.7.1.3.3-8: 1xRTT Origination (step 6, Table 8.4.7.1.3.2-2)
MessageID 00000001B 1xCircuitService
message

GCSNARevision FFS
MessageSequence Any allowed value
1xLogicalChannel 0B
PDU 1x LAC
encapsulated PDU

MSG_ID 000100B Origination
Message

SPECIAL_SERVICE 1B
SERVICE_OPTION Any value mapping to a
voice service option

c1 CHOICE{
purpose CHOICE{
handover SEQUENCE {
targetRAT-Type cdma2000-1XRTT
targetRAT-MessageContainer Set according to Table
8.4.7.1.3.3-10
1xRTT Handoff
Direction message

}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1063
1063
Table 8.4.7.1.3.3-10: 1xRTT Handoff Direction (step 7, Table 8.4.7.1.3.2-2)
message

GCSNARevision FFS
MessageSequence Set by SS
1xLogicalChannel 1B
PDU 1x LAC
encapsulated PDU

MSG_ID 00010001B Extended Handoff
Direction Message

USE_TIME 0B
ACTION_TIME 000000B
HDM_SEQ Set by SS
SEARCH_INCLUDED 0B
HARD_INCLUDED 1B
FRAME_OFFSET Set by SS Forward and
Reverse Traffic
Channel frame
offset on Cell 19

PRIVATE_LCM 0B
RESET_L2 1B
RESET_FPC 1B
SERV_NEG_TYPE 0B Service option
negotiation

ENCRYPT_MODE Set by SS
NOM_PWR_EXT 0B
NOM_PWR Set by SS Correction factor to
be used by UE in
open loop power
estimate

NUM_PREAMBLE Set by SS Traffic Channel
Preamble length to
be used by UE

BAND_CLASS Band class of Cell 19 Band class for f17
CDMA_FREQ CDMA chanel number of
Cell 19
CDMA channel
number for f17

ADD_LENGTH 000B
PILOT_PN Set by SS Pilot PN sequence
offset for Cell 19

PWR_COMB_IND 0B
CODE_CHAN Set by SS Code channel
index to be used
by UE as the
Forward
Fundamental
Channel
associated with
pilot on Cell 19

Table 8.4.7.1.3.3-11: 1xRTT Handoff Completion (step 9, Table 8.4.7.1.3.2-2)
MSG_ID 00001010
LAST_HDM_SEQ Same value as
HDM_SEQ in 1xRTT
Handoff Direction
message at Step 7

PILOT_PN Same value as
PILOT_PN included in
1xRTT Handoff Direction
message at Step 7

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1064
1064
8.4.7.2 Void
8.4.7.3 Pre-registration at 1xRTT and inter-RAT Handover / CS fallback from E-
UTRA RRC_IDLE to 1xRTT
(1)
with { UE in E-UTRA RRC_IDLE state having completed the 1xRTT CS pre-registration procedure and
having received a DLInformationTransfer message containing a 1xRTT CS Paging message }
ensure that {
when { CS paging for the CS Fallback to 1xRTT is accepted at the UE }
then { UE transmits an ULInformationTranfer message containing an EXTENDED SERVICE REQUEST
message with Service Type IE set to "mobile terminating CS fallback or 1xCS fallback }
}
(2)
with { UE having transmitted an ULInformationTranfer message containing an EXTENDED SERVICE REQUEST
message with Service Type IE set to "mobile terminating CS fallback or 1xCS fallback in response to
a 1xRTT CS Paging message }
ensure that {
when { SS transmits an RRCConnectionRelease message with redirection to 1xRTT }
then { UE tunes to 1xRTT cell and transmits a 1xRTT Page Response message on 1xRTT cell }
}

References: The conformance requirements covered in the present TC are specified in: TS 23.272, clause B.2.3.
[TS 23.272, clause B.2.3]
This clause describes the mobile terminating call procedures when the UE accepts or rejects CS paging for the CS
Fallback to 1xRTT.
When the 1x MSC receives a registration from a UE, it makes note of the RAN equipment from which it received the
registration. Subsequent paging activities may thus be directed toward that RAN equipment. However, paging activities
by the 1xMSC are not limited to the single RAN equipment from which the registration was received. The MSC may
choose to page a wider area, including inter-system paging. If the 1xMSC has direct interfaces to 1xCS IWS, as well as
to 1xRTT access, the MSC may choose to do direct paging activities to both E-UTRAN and 1x RAN equipments in its
attempts to contact the UE.
The 1x paging request sent by the 1xMSC to the 1xCS IWS is delivered to the UE via the tunnel. The UE tunes to
1xRTT access, acknowledges the 1x page and performs the 1xCS procedures for mobile terminated call. When the UE
receives a page message, it may not want to accept it based on Caller Line Identification or pre-provisioned local policy.
In that case, the UE sends the 1x Release Order to 1xCS IWS over a tunnel in E-UTRAN and EPC.
The detailed procedure is described in figure B.2.3-1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1065
1065
1xCS
CSFB
UE
E-
UTRAN
MME
1xCS
IWS
1xRTT
MSC
. -
3.1xRTTCSPaging
5b.UL/DLInformation
Transfer
5a.UL/DLS1cdma2000
Tunnelling
S102DirectTransfer
5.1xRTTCSPaging
1.UEisE-UTRANattachedandregisteredwith1xRTTCS
4.IfUEisidle,MMEperformsNetwork-initiated
servicerequest
2.PagingRequest
15.1xMTcallestablishmentper3GPP2specifications
. -
14.1xRTTCSPageResponseMessage
7.S1UEContext
Modification
6b.ServiceRequest
S-GW
8.Optionalmeasurementreport
solicitation
10.S1UEContextRelease
Request
11.SuspendRequest
12.SuspendRequestAck
13.S1UEContextRelease
9.E-UTRANtriggersRRCconnection
releasewithredirection
6a.1xRTTReleaseOrder
6a.1xRTTReleaseOrder
6a.Rejection

6b. Extended Service Request

Figure B.2.3-1: CS MT call using fallback to CDMA 1x RTT network

1. UE is E-UTRAN attached and pre-registered with 1xRTT CS as defined in clause B.2.1.1.
2. 1xMSC sends a paging request to the 1xCS IWS node with Caller Line Identification if available.
3. 1xCS IWS node forwards the 1x RTT CS paging request with Caller Line Identification if available via the S102
tunnel to the MME.
4. If the UE is in idle state, the MME performs the network initiated Service Request procedure in order to bring
the UE to active state prior to tunnelling of the 1x RTT CS paging request toward the UE.
5. MME forwards the 1xRTT CS paging request to the UE.
6a. If the UE decides to reject CSFB based on e.g. user decision by Caller Line Identification or UE locally pre-
provisioned policy, then the UE rejects the 1x CS paging by sending an 1x Release Order to the MME. The
MME forwards the 1x Release Order in an S102 Direct Transfer message to the 1xCS IWS and the 1x IWS
sends a Rejection to the 1x MSC. This completes the procedure.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1066
1066
6b. If the UE accepts CS paging for the CS Fallback to 1xRTT, the UE sends an Extended Service Request (CS
Fallback Indicator) to the MME and proceeds with step 7 to step 15 below.
7. MME sends S1-AP: UE Context Modification (UE capabilities, CS Fallback Indicator) to indicate the
E-UTRAN to move the UE to 1xRTT.
8. E-UTRAN may optionally solicit a measurement report from the UE to determine the target 1xRTT cell to which
the CS Fallback will be performed.
9. E-UTRAN triggers RRC connection release with redirection to 1xCS.
10. E-UTRAN sends an S1 UE Context Release Request (Cause) message to the MME. Cause indicates that the S1
UE Context Release was caused by CS fallback to 1xRTT.
11. MME sets the UE context to suspended status and sends to the S-GW a Suspend Request (IMSI) message that
requests the suspension of EPS bearers for the UE. The S1-U bearers are released for all EPS bearers by the
MME and all GBR bearers are deactivated. The non-GBR bearers are preserved and are marked as suspended in
the S-GW.
12. S-GW acknowledges the Suspend Request message and marks the UE as suspended. When a downlink data
arrives at the S-GW, the S-GW should not send a downlink data notification message to the MME if the UE is
marked as suspended.
13. S1 UE Context in the E-UTRAN is released as specified in TS 23.401 [2].
14. UE tunes to 1xRTT and acknowledges the page by transmitting a 1xRTT Paging Response message over the 1x
Access Channel.
15. Subsequently UE performs the procedure for mobile terminated call establishment as specified in 3GPP2
A.S0013 [18].
System Simulator:
- Cell 19 has a lower reselection priority than Cell 1.
UE:
None.
Preamble:
- The UE has completed the 1xRTT CS pre-registration procedure on Cell 19.
clause.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1067
1067
T0
Cell-specific
RS EPRE
dBm/15kHz -60 -
Srxlev
Cell 1
>0 and Cell 19 is off
such that camping on Cell 1 is
guaranteed. or/Ioc dB - -
Pilot Ec/Ior dB - -
Ioc
dBm/1.23
MHz
- -
Pilot Ec/Io
(Note 1)
dB - -
T1
Cell-specific
RS EPRE
dBm/15kHz -60 -
Cell 19 in on, with S
ServingCell
>
Thresh
serving, low
and S
nonServingCell, x
<Thresh
x, low
. or/Ioc dB - 0
Ioc
dBm/1.23
MHz
- -75
Pilot Ec/Io
(Note 1)
dB - -10

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1068
1068
U - S Message
1 The SS transmits a Paging message to the UE
on Cell 1 using S-TMSI with CN domain
indicator set to ''PS.
<-- Paging - -
message on Cell 1.
message with SRB1 configuration on Cell 1.
containing a SERVICE REQUEST message
on Cell 1.
on Cell 1.
SRB2-DRB(1,1) configuration on Cell 1.
<-- RRCConnectionReconfiguation - -
message on Cell 1.
message on Cell 1.
omplete
- -
9 The SS changes the cell power levels
according to T1 in Table 8.4.7.3.3.2-1.

10 The SS transmits a DLInformationTransfer
containing a 1x RTT CS Paging message on
Cell 1.
11 The CS paging for the CS Fallback to 1xRTT is
accepted at the UE.
- - - -
ULInformationTransfer containing an
EXTENDED SERVICE REQUEST with
Service Type IE set to "mobile terminating CS
fallback or 1xCS fallback on Cell 1?
--> ULInformationTransfer 1 P
message on Cell 1 redirecting the UE to Cell
19.
15 Check: Does the UE transmit a Page
Response message on Cell 19?
--> Page Response 2 P
16 The SS transmits an Extended Channel
Assignment message on Cell 19.
<-- Extended Channel Assignment - -
17 After the SS detects that Traffic Channel
Initialization is successful, it transmits an
Acknowledgement Order message on Cell 19.
<-- Acknowledgement Order - -
18 The SS transmits a Service Connect message
on Cell 19.
<-- Service Connect - -
19 The UE transmits a Service Connect
Completion message on Cell 19.
--> Service Connect Completion - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1069
1069
Table 8.4.7.3.3.3-1: Void
Table 8.4.7.3.3.3-2: SystemInformationBlockType8 for Cell 1 (all steps, Table 8.4.7.3.3.2-2)
Derivation Path: 36.508 Table 4.4.3.3-7, condition 1XRTT
parameters1XRTT SEQUENCE {
csfb-RegistrationParam1XRTT SEQUENCE {
Sid FFS Sid of Cell 19
Nid FFS Nid of Cell 19
multipleSID FFS BOOLEAN
multipleNID FFS BOOLEAN
homeReg FFS BOOLEAN
foreignSIDReg FFS BOOLEAN
foreignNIDReg FFS BOOLEAN
parameterReg FFS BOOLEAN
powerUpReg FFS BOOLEAN
registrationPeriod FFS BIT STRING
(SIZE (7))

registrationZone FFS BIT STRING
(SIZE (12))

totalZone FFS BIT STRING
(SIZE (3))

zoneTimer FFS BIT STRING
(SIZE (3))

}
longCodeState1XRTT Set by SS BIT STRING
(SIZE (42))
OPTIONAL

cellReselectionParameters1XRTT SEQUENCE {
bandClassList SEQUENCE (SIZE (1..maxCDMA
-BandClass)) OF SEQUENCE {
1 entry
bandClass FFS ENUMERATED
{bc0, bc1, bc2,
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2,
spare1, ...}

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1070
1070
Table 8.4.7.3.3.3-3: DLInformationTransfer (step 10, Table 8.4.7.3.3.2-2)
DLInformationTransfer ::=SEQUENCE {
c1 CHOICE {
dlInformationTransfer-r8 SEQUENCE {
dedicatedInfoType CHOICE {
dedicatedInfoCDMA2000-1XRTT Set according to Table
8.4.7.3.3.3-4

}
}
}
}
}

Table 8.4.7.3.3.3-4: 1xRTT CS Paging message (step 10, Table 8.4.7.3.3.2-2)
message

GCSNARevision FFS
MessageSequence Set by SS
1xLogicalChannel 0B
PDU 1x LAC
encapsulated
PDU

MSG_ID 010001B General Page
Message

PAGE_CLASS Set as per identity type
of UE, for a mobile-
addressed page

PAGE_SUBCLASS Set as per identity type
of UE, for a mobile-
addressed page

Page Type-specific fields Set to match UEs
identity

Table 8.4.7.3.3.3-5: ULInformationTransfer (step 12, Table 8.4.7.3.3.2-2)
ULInformationTransfer ::=SEQUENCE {
c1 CHOICE {
ulInformationTransfer-r8 SEQUENCE {
dedicatedInfoNAS Set according to Table
8.4.7.3.3.3-6
EXTENDED
SERVICE
REQUEST

}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1071
1071
Table 8.4.7.3.3.3-6: EXTENDED SERVICE REQUEST (step 12, Table 8.4.7.3.3.2-2)
Protocol discriminator EMM
Service type '0001'B mobile terminating
CS fallback or
1xCS fallback

CSFB response 001B CS fallback
accepted by the
UE

c1 CHOICE {
redirectionInformation ::=CHOICE {
interRAT-target CHOICE {
Cell 19

}
}
}
}
}
}

Table 8.4.7.3.3.3-8: Page Response (step 15, Table 8.4.7.3.3.2-2)
FIeld Value/remark Comment Condition
MSG_ID 000101B Page Response
Message

MOB_TERM 1B

Table 8.4.7.3.3.3-9: Extended Channel Assignment (step 16, Table 8.4.7.3.3.2-2)
MSG_ID 010101B Extended Channel
Assignment
Message

ASSIGN_MODE 000B Traffic Channel
Assignment

Table 8.4.7.3.3.3-10: Acknowledgment Order (step 17, Table 8.4.7.3.3.2-2)
MSG_ID 00000001B Order Message
ORDER 010000B Base Station
Acknowledgment
Order

ORDQ 00000000B

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1072
1072
Table 8.4.7.3.3.3-11: Service Connect (step 18, Table 8.4.7.3.3.2-2)
MSG_ID 00010100B Service Connect
Message

SERV_CON_SEQ Set by SS

Table 8.4.7.3.3.3-12: Service Connect Completion (step 19, Table 8.4.7.3.3.2-2)
Completion
Message

SERV_CON_SEQ Same value as
SERV_CON_SEQ
received in Service
Connect Message (Table
8.4.7.3.3.3-15)

8.4.7.4 Pre-registration at 1xRTT and inter-RAT handover / CS fallback caused by
addition of CS service / From E-UTRA (Data) to 1xRTT
(1)
with { UE in E-UTRA RRC_CONNECTED state and having completed the 1xRTT CS pre-registration
procedure }
ensure that {
when { a voice call is originated at the UE }
then { UE transmits an EXTENDED SERVICE REQUEST message with Service Type IE set to "mobile
originating CS fallback or 1xCS fallback }
}
(2)
message with Service Type IE set to "mobile originating CS fallback or 1xCS fallback }
ensure that {
when { SS transmits a RRCConnectionRelease message with redirection to 1xRTT }
then { UE tunes to 1xRTT cell and transmits a 1xRTT Origination message on 1xRTT cell }
}

References: The conformance requirements covered in the present TC are specified in: TS 23.272, clause B.2.2.
[TS 23.272, clause B.2.2]
This clause describes the mobile originating call procedures for the CS Fallback to 1xRTT.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1073
1073
1xCS
CSFB
UE
E-
UTRAN
MME
1xCS
IWS
1xRTT
MSC
1. UE is E-UTRAN attached and registered with 1xRTT CS
11. 1x MO call establishment per 3GPP2 specifications

. -
4. S1 UE Context
Modification
3. Extended Service Request
S-GW
5. Optional measurement report
solicitation
Request
8. Suspend Request
9. Suspend Request Ack
2. UE decision
to perform MO
call in 1xCS
6. E-UTRAN triggers RRC connection
release with redirection

Figure B.2.2-1: CS MO call using fallback to CDMA 1x RTT network

1. UE is E-UTRAN attached and registered with 1xRTT CS as defined in clause B.2.1.1.
2. UE makes a decision to perform a mobile originated CS call.
3. UE sends an Extended Service Request (CS Fallback Indicator) to the MME.
4. MME sends S1-AP: UE Context Modification (UE capabilities, CS Fallback Indicator) to indicate the
E-UTRAN to move the UE to 1xRTT.
5. E-UTRAN may optionally solicit a measurement report from the UE to determine the target 1xRTT cell to which
the CS Fallback will be performed.
6. E-UTRAN triggers RRC connection release with redirection to 1xCS.
7. E-UTRAN sends an S1 UE Context Release Request (Cause) message to the MME. Cause indicates that the S1
UE Context Release was caused by CS fallback to 1xRTT.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1074
1074
8. MME sets the UE context to suspended status and sends to the S-GW a Suspend Request (IMSI) message that
requests the suspension of EPS bearers for the UE. The S1-U bearers are released for all EPS bearers by the
MME and all GBR bearers are deactivated. The non-GBR bearers are preserved and are marked as suspended in
the S-GW.
9. S-GW acknowledges the Suspend Request message and marks the UE as suspended. When a downlink data
arrives at the S-GW, the S-GW should not send a downlink data notification message to the MME if the UE is
marked as suspended.
10. S1 UE Context in the E-UTRAN is released as specified in TS 23.401 [2].
11.UE moves to 1xRTT and performs the procedure for mobile originating call as specified in 3GPP2 A.S0013 [18].
System Simulator:
- Cell 19 has a lower reselection priority than Cell 1.
UE:
None.
Preamble:
- The UE has completed the 1xRTT CS pre-registration procedure on Cell 19.
clause.
T0
Cell-specific
RS EPRE
dBm/15kHz -60 -
Srxlev
Cell 1
>0 and Cell 19 is off
such that camping on Cell 1 is
guaranteed. or/Ioc dB - -
Pilot Ec/Ior dB - -
Ioc
dBm/1.23
MHz
- -
Pilot Ec/Io
(Note 1)
dB - -
T1
Cell-specific
RS EPRE
dBm/15kHz -60 -
Cell 19 in on, with S
ServingCell
>
Thresh
serving, low
and S
nonServingCell, x
<Thresh
x, low
. or/Ioc dB - 0
Ioc
dBm/1.23
MHz
- -75
Pilot Ec/Io
(Note 1)
dB - -10

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1075
1075
U - S Message
1 A voice call is originated at the UE - - - -
ULInformationTransfer containing an
Service Type IE set to "mobile originating CS
--> ULInformationTransfer 1 P
3 The SS changes the cell power levels
according to T1 in Table 8.4.7.3.3.2-1 and
waits for [2] seconds.
- - - -
message on Cell 1 redirecting the UE to Cell
19.
6 Check: Does the UE transmit an Origination
message on Cell 19?
--> Origination 2 P
7 The SS transmits an Extended Channel
Assignment message on Cell 19.
<-- Extended Channel Assignment - -
8 After the SS detects that Traffic Channel
Initialization is successful, it transmits an
Acknowledgement Order message on Cell 19.
<-- Acknowledgement Order - -
9 The SS transmits a Service Connect message
on Cell 19.
<-- Service Connect - -
10 The UE transmits a Service Connect
Completion message on Cell 19.
--> Service Connect Completion - -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1076
1076
Table 8.4.7.4.3.3-1: Void
Derivation Path: 36.508 Table 4.4.3.3-7, condition 1XRTT
parameters1XRTT SEQUENCE {
csfb-RegistrationParam1XRTT SEQUENCE {
Sid FFS Sid of Cell 19
Nid FFS Nid of Cell 19
multipleSID FFS BOOLEAN
multipleNID FFS BOOLEAN
homeReg FFS BOOLEAN
foreignSIDReg FFS BOOLEAN
foreignNIDReg FFS BOOLEAN
parameterReg FFS BOOLEAN
powerUpReg FFS BOOLEAN
registrationPeriod FFS BIT STRING
(SIZE (7))

registrationZone FFS BIT STRING
(SIZE (12))

totalZone FFS BIT STRING
(SIZE (3))

zoneTimer FFS BIT STRING
(SIZE (3))

}
longCodeState1XRTT Set by SS BIT STRING
(SIZE (42))
OPTIONAL

cellReselectionParameters1XRTT SEQUENCE {
bandClassList SEQUENCE (SIZE (1..maxCDMA
-BandClass)) OF SEQUENCE {
1 entry
bandClass FFS ENUMERATED
{bc0, bc1, bc2,
bc3, bc4, bc5,
bc6, bc7, bc8,
bc9, bc10, bc11,
bc12, bc13, bc14,
bc15, bc16, bc17,
spare14, spare13,
spare12, spare11,
spare10, spare9,
spare8, spare7,
spare6, spare5,
spare4, spare3,
spare2,
spare1, ...}

}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1077
1077
Table 8.4.7.4.3.3-3: ULInformationTransfer (step 2, Table 8.4.7.4.3.2-2)
c1 CHOICE {
8.4.7.4.3.3-4
EXTENDED
SERVICE
REQUEST

}
}
}
}
}

Table 8.4.7.4.3.3-4: EXTENDED SERVICE REQUEST (step 2, Table 8.4.7.4.3.2-2)
Protocol discriminator EMM
Service type '0001'B mobile originating
CS fallback or
1xCS fallback

CSFB response Not present

c1 CHOICE {
redirectionInformation ::=CHOICE {
interRAT-target CHOICE {
Cell 19

}
}
}
}
}
}

Table 8.4.7.4.3.3-6: Origination (step 6, Table 8.4.7.4.3.2-2)
MSG_ID 000100B Origination
Message

SPECIAL_SERVICE 1B
SERVICE_OPTION Any value mapping to a
voice service option

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1078
1078
Table 8.4.7.4.3.3-7: Extended Channel Assignment (step 7, Table 8.4.7.4.3.2-2)
MSG_ID 010101B Extended Channel
Assignment
Message

ASSIGN_MODE 000B Traffic Channel
Assignment

Table 8.4.7.4.3.3-8: Acknowledgment Order (step 8, Table 8.4.7.4.3.2-2)
MSG_ID 00000001B Order Message
ORDER 010000B Base Station
Acknowledgment
Order

ORDQ 00000000B

Table 8.4.7.4.3.3-9: Service Connect (step 9, Table 8.4.7.4.3.2-2)
Message

SERV_CON_SEQ Set by SS

Table 8.4.7.4.3.3-10: Service Connect Completion (step 10, Table 8.4.7.4.3.2-2)
Completion
Message

SERV_CON_SEQ Same value as
SERV_CON_SEQ
received in Service
Connect Message (Table
8.4.7.4.3.3-9

8.5 RRC others
8.5.1 Radio link failure
8.5.1.1 Radio link failure / RRC connection re-establishment success
(1)
ensure that {
when { UE detecting physical layer problems}
then { UE shall start timer T310 and UE does not initiate any RRC Connection re-establishment
procedure before expiring of timer T310}
}

(2)
ensure that {
when { UE detecting radio link failure on expiring of timer T310 }
then { UE starts timer T311 and UE initiates the RRC Connection re-establishment procedure }
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1079
1079
(3)
ensure that {
when { UE sucsessfully completes the RRC Connection re-establishment procedure }
then { UE is in E-UTRA RRC_CONNECTED state }
}

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.7.2,
5.3.10.1, 5.3.10.3 and 5.3.10.4.
[TS 36.331 clause 5.3.7.2]
1>start timer T311;
1>reset MAC;
[TS 36.331 clause 5.3.11.1]
The UE shall:
1>upon receiving N310 consecutive "out-of-sync" indications from lower layers while neither T300, T301, T304
nor T311 is running:
2>start timer T310;
[TS 36.331 clause 5.3.11.3]
The UE shall:
1>upon T310 expiry; or
1>upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is running; or
1>upon indication from RLC that the maximum number of retransmissions has been reached:
2>consider radio link failure to be detected;
2>if AS security has not been activated:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1080
1080
2>else:
3>initiate the connection re-establishment procedure as specified in 5.3.7;
System Simulator:
- 2 cells on same E-UTRA frequency:
- Cell 1 (default parameters) serving cell
- Cell 2 intra-frequency cell
UE:
None.
Preamble:
T1
Cell-specific RS
EPRE
dBm/15k
Hz
Off -85
Power level Off is defined in TS36.508 Table 6.2.2.1-1.

U - S Message
in order that the radio link quality of Cell 1 is
degraded and cell 2 is suitable for camping.
- - - -
2 Check: Does the UE initiate an RRC
connection re-establishment procedure on Cell
1 or Cell 2. This is checked during the time
T=T310.
- - 1 F
message on Cell 2?
Request
2 P
4 The SS transmits
RRCConnectionReestablishment message.
5 The UE transmits
message.
Complete
- -
resume existing radio bearer.
message.
omplete
- -
- 3 P

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1081
1081
SEQUENCE {

SEQUENCE {

of the UE

Cell 1

the XMAC-I value
calculated by SS

}
}
}
}

c1 CHOICE{
dicated-HO

}
}
}
}

8.5.1.2 Radio link failure / T301 expiry
(1)
ensure that {
when { UE having sent an RRCConnectionReestablishmentRequest message on starting of timer T301 }
then { UE goes to RRC_IDLE state after timer T301 is expired and trigger TAU procedure in order
to recover RRC connection}
}
References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.7.2,
5.3.7.3, 5.3.7.7, 5.3.11.1 and 5.3.11.3. The following represent an extraction of the requirements relevant to the test
purpose.
[TS 36.331 clause 5.3.7.2]
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1082
1082
1>start timer T311;
1>reset MAC;
[TS 36.331 clause 5.3.7.3]
Upon selecting a suitable E-UTRA cell, the UE shall:
1>stop timer T311;
1>start timer T301;
1>initiate transmission of the RRCConnectionReestablishmentRequest message in accordance with 5.3.7.4;
NOTE: This procedure applies also if the UE returns to the source cell.
Upon selecting an inter-RAT cell, the UE shall:
1>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';
[TS 36.331 clause 5.3.7.7]
The UE shall:
1>if timer T301 expires; or
1>if the selected cell becomes no longer suitable according to the cell selection criteria as specified in TS 36.304
[4]:
[TS 36.331 clause 5.3.11.1]
The UE shall:
2>start timer T310;
[TS 36.331 clause 5.3.11.3]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1083
1083
2>else:
System Simulator:
UE:
None.
Preamble:
U - S Message
1 The SS changes the power level of Cell 1 to
non-suitable Off and changes the power level
of Cell 2 to suitable according to TS 36.508
subclause 6.2.2.1 in order that the radio link
quality of Cell 1 is degraded.
- - - -
2 The UE sends
message on Cell 2.
Request
- -
3 The SS does not respond to any
message for 2s (T301).
- - - -
4-8 The UE will perform TAU procedure based on
on Cell 2.
- - - -
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1084
1084
Table 8.5.1.2.3.3-1: SystemInformationBlockType2 for Cell 2 (all steps)
ue-TimersAndConstants SEQUENCE {
t301 ms2000
}
}

SEQUENCE {

SEQUENCE {

of the UE

Cell 1

the XMAC-I value
calculated by SS

}
}
}
}

8.5.1.3 Radio link failure / T311 expiry
(1)
with { UE in E-UTRA RRC_CONNECTED state with default bearer established and radio link failure was
detected and UE attempts to select a suitable E-UTRA cell to re-establish the RRC connection }
ensure that {
when { UE can not find a suitable cell within T311 }
then { UE does not try to re-establish the RRC connection and goes to RRC_IDLE state after T311
expired }
}
The conformance requirements covered in the current test case are specified in TS 36.331 clause 5.3.7.2, 5.3.7.6 and
5.3.12.
[TS 36.331 clause 5.3.7.2]
...
1>start timer T311;
...
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1085
1085
[TS 36.331 clause 5.3.7.6]
Upon T311 expiry, the UE shall:
1>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause RRC
connection failure.
[TS 36.331 clause 5.3.12]
1>reset MAC;
1>indicate the release of the RRC connection to upper layers with the release cause;
System simulator:
2 cells on same E-UTRA frequency:
UE:
None.
Preamble:
- The UE is in Generic RB Established (state 3) according to [18] on Cell 1.
U - S Message
non-suitable Off according to TS 36.508
- - - -
2 Wait for 12s (T311 (10s) is transmitted in
SIB2).
- - - -
Serving Cell according to TS 36.508
subclause 6.2.2.1.
- - - -
Cell 11?
- - 1 -

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1086
1086
None.
8.5.1.4 Radio link failure / RRC connection re-establisment reject
(1)
with { UE in E-UTRA RRC_CONNECTED state with default bearer established and radio link failure was
detected and UE initiates the re-establishment procedure}
ensure that {
when { the UE receives a RRCConnectionReestablishmentReject message }
then { UE goes to RRC_IDLE and trigger TAU procedure in order to recover RRC connection }
}
The conformance requirements covered in the current test case are specified in TS 36.331 clause 5.3.7.8 and 5.3.12.
[TS 36.331 clause 5.3.7.8]
Upon receiving the RRCConnectionReestablishmentReject message, the UE shall:
1>perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause RRC
connection failure.
[TS 36.331 clause 5.3.12]
1>reset MAC;
case of leaving RRC_CONNECTED, as specified in TS 36.304 [4];
System simulator:
- Cell 1(default parameters) serving cell
UE:
None.
Preamble:
- The UE is in Generic RB Established (state 3) according to [18] on Cell 1.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1087
1087
U - S Message
non-suitable cell according to TS 36.508
quality of Cell 1 is degraded and set the power
level of Cell 2 to suitable cell.
- - - -
message on Cell 2.
--> RRCConnectionRestablishmentR
equest
- -
RRCConnectionReestablishmentReject
message
<-- RRCConnectionReestablishment
Reject
- -
4-8 The UE will perform TAU procedure based on
on Cell 2.
- - - -
- - 1 -

None.
8.5.1.5 Radio link failure / Radio link recovery while T310 is running
(1)
ensure that {
when { UE detecting physical layer recovery while T310 was running }
then { the UE resumes the RRC connection without explicit signalling }
}
References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.11.1 and
5.3.11.2.
[TS 36.331, clause 5.3.11.1]
The UE shall:
1>upon receiving N310 consecutive "out of sync" indications from lower layers while neither T300, T301, T304
2>start timer T310.
[TS 36.331, clause 5.3.11.2]
Upon receiving N311 consecutive "in-sync" indications from lower layers while T310 is running, the UE shall:1>
stop timer T310.
NOTE 1: In this case, the UE resumes the RRC connection without explicit signalling, i.e. the UE resumes the
entire radio resource configuration.
NOTE 2: 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 "in-sync" or "out-of-sync" indications
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1088
1088
System Simulator:
- Cell 1
UE:
None.
Preamble:
Table 8.5.1.5.3.2-1 illustrates the downlink power level to be applied for the cell at various time instants of the test
execution. Row marked "T0" denotes the initial condition, while column marked "T1"is applied according the
procedure.
Table 8.5.1.5.3.2-1: Time instances of cell power level
T0 RS EPRE
dBm/
15kH
z
P
default

Power level from 36.508
clause 6.2.2.1. P
default
as
serving cell.

T1 RS EPRE
dBm/
15kH
z
P
off

P
off
as as non-suitable Off
cell.

U - S Message
SS wait for the 660ms to ensure that DL
Timing Advance is sent at least once and UE
apply the value of
timeAlignmentTimerDedicated which is
updated during the preamble.
- - - -
row "T1" in table 8.5.1.5.3.2-1.
- - - -
2 SS waits for 1.5s. The T310 is 2s. - - - -
row "T0" in table 8.5.1.5.3.2-1.
- - - -
4 SS waits for 5s.
Check: Does the UE transmit any signalling
message?
- - 1 F
- - 1 -

Table 8.5.1.5.3.3-1: SystemInformationBlockType2 (preamble and all steps, Table 8.5.1.5.3.2-2)
ue-TimersAndConstants SEQUENCE {
t310 ms2000
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1089
1089
Table 8.5.1.5.3.3-2: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1 [18], step 8)
c1 CHOICE{
}
}
}
}
}
}

NOTE: As per test model SS is not configured to transmit PDCCH orders and it expects UE to be PUCCH
synchronized throughout the test sequence.
8.5.2
8.5.2.1 Redirection to E-UTRAN / From UTRAN upon reception of RRC
CONNECTION REJ ECT
(1)
with { UE in UTRA Idle state }
ensure that {
when { UE is requested to make an outgoing PS call }
then { UE includes in the RRC CONNECTION REQUEST the IE Pre-Redirection info" }
}
(2)
with { UE in UTRA CELL_DCH state }
ensure that {
when { UE receives an RRC CONNECTION REJECT message including an IE Redirection info with E-UTRA
target info E-UTRA frequency }
then { UE enters RRC_IDLE state on E-UTRAN Carrier included in IE Redirection info }
}

8.1.4.3 and clause 8.5.2.
[TS 25.331, clause 8.1.3.3]
The UE shall, in the transmitted RRC CONNECTION REQUEST message:

1>if the UE supports E-UTRA:
2>if the variable EUTRA_FREQUENCY_INFO_LIST contains no E-UTRA frequencies:
3>if the UE supports E-UTRA FDD:
3>if the UE supports E-UTRA TDD:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1090
1090
2>if the UE supports any of the bands that the E-UTRA frequencies included in the variable
3>if the UE supports any of the bands that the E-UTRA FDD frequencies included in the variable
3>if the UE supports any of the bands that the E-UTRA TDD frequencies included in the variable
[TS 25.331, clause 8.1.3.9]
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 REJECT message with the value of the variable
INITIAL_UE_IDENTITY:

1>if the IE "inter-RAT info" is present:
2>if the IE "wait time" ='0':
3>the UE behaviour is not specified.
2>if V300 is equal to or smaller than N300:
3>if the IE "GSM target cell info" is present:
4>attempt to camp on a suitable cell of the list of cells indicated for that RAT;
4>if the UE selects and camps on one of the cells indicated for that RAT:
5>disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed.
4>if the UE cannot find any suitable cell from the indicated ones within 10s, the UE is allowed to camp
on any suitable cell on that RAT.
5>after having selected and camped on a suitable cell on the designated RAT:
6>the UE may disable cell reselection to the original RAT until the time stated in the IE "wait
time" has elapsed.
3>if the IE "E-UTRA target info" is present:
4>attempt to camp on a suitable cell on one of the frequencies indicated for that RAT, excluding any cell
indicated in the list of not allowed cells for that RAT (e.g. the "E-UTRA Target Cell Blackist" for E-
UTRA), if present;
4>if the UE selects and camps on one such cell:
5>disable cell reselection to the original RAT until the time stated in the IE "wait time" has elapsed.
4>if the UE cannot find any suitable cell on the indicated frequencies within 10s, the UE is allowed to
camp on any suitable cell on that RAT:
5>after having selected and camped on a suitable cell on the designated RAT:
6>disable cell reselection to the original RAT until the time stated in the IE "wait time" has
elapsed.
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1091
1091
System Simulator:
- 2 cells, one UTRA and one E-UTRA cell:
- Cell 5 UTRA serving cell (priority 4 default)
- Cell 1 suitable neighbour E-UTRA cell (priority 3)
UE:
UTRAN Idle state
Preamble:
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.
U - S Message
1 Make the UE initiate an outgoing PS call. - - - -
2 Check: does the UE include the IE Pre-
redirection info with Support of E-UTRA set to
TRUE?
3 The SS transmit a RRC CONNECTION
REJ ECT
<--
RRC CONNECTION REJ ECT - -
Cell 1?
- - 2 -

Table 8.5.2.1.3.3-1 System Information Block type 19 for cell 5 (preamble and all steps, Table
8.5.2.1.3.2-1)
Derivation Path: 36.508 table Table 4.4.4.1-1
priority 4
}
1 entry
earfcn[1] Downlink EARFCN of
Cell 1

priority[1] 3
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1092
1092
Table 8.5.2.1.3.3-2: RRC CONNECTION REQUEST (UTRA Rel-8)
Derivation path: 34.108 default RRC CONNECTION REQUEST in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA
TDD
Pre-redirection info The presence of
this IE indicates
the UE support of
radio access
technologies that
the UE could be
directed to

Support of E-UTRA FDD TRUE E-UTRA-
FDD
Support of E-UTRA TDD TRUE E-UTRA-
TDD
Domain indicator

PS domain

Table 8.5.2.1.3.3-2: RRC CONNECTION REJECT (UTRA Rel-8)
Derivation path: 34.108 default RRC CONNECTION REJ ECT in section 9.1.1 for UTRA FDD or 9.1.2 for UTRA TDD
Wait Time 15
Redirection info
Inter-RAT info E-UTRA
E-UTRA target info
E-UTRA Target Frequency Info List 1 Entry
DL Carrier frequency EARFCN of the downlink
Cell 1 carrier frequency

8.5.3 Void
8.5.4 UE capability transfer
8.5.4.1 UE capability transfer / Success
(1)
with { UE in RRC_CONNECTED state }
ensure that {
when { UE receives an UECapabilityEnquiry message before AS security is activated }
then { UE transmits an UECapabilityInformation message including UE radio access capability
information corresponding to the ue-CapabilityRequest variable }
}
(2)
with { UE in RRC_CONNECTED state }
ensure that {
when { UE receives an UECapabilityEnquiry message after AS security is activated }
then { UE transmits an UECapabilityInformation message including UE radio access capability
information corresponding to the ue-CapabilityRequest variable }
}

[TS 36.331, clause 5.6.3.3]
The UE shall:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1093
1093
1>set the contents of UECapabilityInformation message as follows:
2>if the ue-CapabilityRequest includes eutra:
3>include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to
eutra;
2>if the ue-CapabilityRequest includes geran-cs and if the UE supports GERAN CS domain:
3>include the UE radio access capabilities for GERAN CS within a ue-CapabilityRAT-Container and with
the rat-Type set to geran-cs;
2>if the ue-CapabilityRequest includes geran-ps and if the UE supports GERAN PS domain:
3>include the UE radio access capabilities for GERAN PS within a ue-CapabilityRAT-Container and with
the rat-Type set to geran-ps;
2>if the ue-CapabilityRequest includes utra and if the UE supports UTRA:
3>include the UE radio access capabilities for UTRA within a ueCapabilityRAT-Container and with the rat-
Type set to utra;
2>if the ue-CapabilityRequest includes cdma2000-1XRTT and if the UE supports CDMA2000-1xRTT:
3>include the UE radio access capabilities for CDMA 2000 within a ueCapabilityRAT-Container and with
the rat-Type set to cdma2000-1XRTT;
1>submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends.
System Simulator:
- Cell 1
UE:
None.
Preamble:
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1094
1094
U - S Message
message.
message.
<--
RRCConnectionSetupComplete.
This message includes an ATTACH
REQUEST and a PDN CONNECTIVITY
REQUEST message.
message.
This message includes an AUTHENTICATION
REQUEST message.
6 The UE transmits a ULInformationTransfer
message.
This message includes an AUTHENTICATION
RESPONSE message.
message.
This message includes a SECURITY MODE
COMMAND message.
message.
This message includes a SECURITY MODE
COMPLETE message.
9 The SS transmits a UECapabilityEnquiry
information for E UTRA only.
UECapabilityInformation message?
message to activate AS security.
message and establishes the initial security
configuration.
behaviour that depends on UE configuration;
sequence that take place if the UE has ESM
information which needs to be transferred after
SECURITY MODE COMPLETE message.
- - - -
13a
1
IF the UE sets the ESM information transfer
flag in the last PDN CONNECTIVITY
REQUEST message THEN the SS transmits a
DLInformationTransfer message.
This message includes an ESM
INFORMATION REQUEST message.
13a
2
The UE transmits a ULInformationTransfer
message.
This message includes an ESM
INFORMATION RESPONSE message.
RRCConnectionReconfigurationComplete.
omplete
- -
message.
This message includes an ATTACH
COMPLETE message.
17 The SS transmits a UECapabilityEnquiry <-- UECapabilityEnquiry - -
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1095
1095
information for E UTRA only.
behaviour that depends on the UE capability.
- - - -
19a
1
IF pc_FDD, pc_TDD_HCR, pc_TDD_LCR,
pc_TDD_VHCR, pc_GERAN, pc_1xRTT or
pc_HRPD THEN the SS transmits a
UECapabilityEnquiry message to request UE
radio access capability information for every
other supported RATs.
19a
2
Check: Does the UE transmit a

Table 8.5.4.1.3.3-1: UEcapabilityEnquiry (step 9 and 17, Table 8.5.4.1.3.2-1)
UECapabilityEnquiry ::=SEQUENCE {
c1 CHOICE {
ueCapabilityEnquiry-r8 SEQUENCE {
ue-CapabilityRequest SEQUENCE (SIZE
(1..maxRAT-Capabilities)) OF SEQUENCE {
1 entry E-UTRA only
RAT-Type[1] eutra
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1096
1096
Table 8.5.4.1.3.3-2: UECapabilityInformation (step 10 and 18, Table 8.5.4.1.3.2-1)
UECapabilityInformation ::=SEQUENCE {
c1 CHOICE{
ueCapabilityInformation-r8 SEQUENCE {SIZE
1 entry only
rat-Type[1] eutra E-UTRA only
ueCapabilitiesRAT-Container[1] OCTET
STRING {

UE-EUTRA-Capability SEQUENCE {
accessStratumRelease rel8 Release 8 only
ue-Category px_eUE_Category_Type
pdcp-Parameters Not checked
phyLayerParameters SEQUENCE {
ul-AntennaSelectionSupported Not checked
ue-SpecificRefSigsSupported Not checked
}
rf-Parameters SEQUENCE (SIZE
(1..maxBands)) OF SEQUENCE {

supportedEUTRA-BandList SEQUENCE { n entries where n is the
sum of pc_eBand_Supp
for =1 to 64
n is the number of
supported EUTRA
bands

eutra-Band[ =1..n] Any value such that
pc_eBand_Supp is
TRUE and different from
all eutra-Band[k] where k
=1 to - 1

halfDuplex[ =1..n] Not checked
}
}
measurementParameters SEQUENCE {
eutra-BandList SEQUENCE (SIZE

interFreqEUTRA-BandList SEQUENCE
(SIZE (1..maxBands)) OF SEQUENCE {
same number of entries
like in supportedEUTRA-
BandList

interFreqNeedForGaps[1..n] Not checked
}
interRAT-BandList SEQUENCE (SIZE
m entries (contents not
checked, but m shall be
equal to the number of
bands listed in each IE
present in interRAT-
Parameters)

interRAT-NeedForGaps[1..m] Not checked
}
}
}
featureGroupIndicators Bits 1 to 26 shall be set
according to
pcFeatGrp_1 to
pcFeatGrp_26, other bits
shall be set to 0.

interRAT-Parameters SEQUENCE { m elements are present
utraFDD Present but value not
checked
pc_FDD
utraTDD128 Present but value not
checked
pc_TDD_L
CR
checked
pc_TDD_H
CR
checked
pc_TDD_V
HCR
geran Present but value not
checked
pc_GERA
N
Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1097
1097
cdma2000-HRPD Present but value not
checked
pc_HRPD
cdma2000-1xRTT Present but value not
checked
pc_1xRTT
}
nonCriticalExtension SEQUENCE {} Not checked
}
}
}
}
}
}

Table 8.5.4.1.3.3-3: UEcapabilityEnquiry (step 19a1, Table 8.5.4.1.3.2-1)
UECapabilityEnquiry ::=SEQUENCE {
c1 CHOICE {
ueCapabilityEnquiry-r8 SEQUENCE { Numbering of entries is
according to conditions
met
According to inter-
RAT capabilities
of UE

ue-RadioAccessCapRequest[i1] utran This entry is
present if the UE
is capable of any
mode (FDD/TDD)
in UMTS.
pc_FDD,
pc_TDD_H
CR,
pc_TDD_L
CR,
pc_TDD_V
HCR
ue-RadioAccessCapRequest[i2] geran-cs pc_GERA
N and
pc_CS
ue-RadioAccessCapRequest[i3] geran-ps pc_GERA
N and
pc_PS
ue-RadioAccessCapRequest[i4] cdma2000-1XRTT pc_1xRTT,
pc_HRPD
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1098
1098
Table 8.5.4.1.3.3-4: UECapabilityInformation (step 19a2, Table 8.5.4.1.3.2-1)
UECapabilityInformation ::=SEQUENCE {
c1 CHOICE{
ueCapabilityInformation-r8 SEQUENCE {SIZE
Stated capability
shall be
compatible with
3GPP TS 36.523-
2 (ICS
statements) and
the user settings

rat-Type[i1] utran pc_FDD,
pc_TDD_H
CR,
pc_TDD_L
CR,
pc_TDD_V
HCR
ueCapabilitiesRAT-Container[i1] OCTET
STRING {}
ueCapabilitiesRAT-
Container-UTRAN
Encoded as an
INTER RAT
HANDOVER
INFO messages
as defined in
3GPP TS 25.331
[17].
pc_FDD,
pc_TDD_H
CR,
pc_TDD_L
CR,
pc_TDD_V
HCR
rat-Type[i2] geran-cs pc_GERA
N and
pc_CS
ueCapabilitiesRAT-Container [i2] OCTET
STRING {}
ueCapabilitiesRAT-
Container-GERAN-CS
Encoded as the
concatenation of
IEs MS classmark
2 and MS
classmark 3 as
defined in 3GPP
TS 24.008 [32].
pc_GERA
N and
pc_CS
rat-Type[i3] geran-ps pc_GERA
N and
pc_PS
STRING {}
ueCapabilitiesRAT-
Container-GERAN-PS
Encoded as MS
radio access
capability IE as
defined in 3GPP
TS 24.008 [32].
pc_GERA
N and
pc_PS
rat-Type[i4] cdma2000-1XRTT pc_1xRTT,
pc_HRPD
STRING {}
Not checked Encoded as A21
Mobile
Subscription
Information as
defined in 3GPP2
A.S0008 [33].
pc_1xRTT,
pc_HRPD
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1099
1099
Table 8.5.4.1.3.3-5: ueCapabilitiesRAT-Container-UTRAN
Derivation path: 25.331 clause 11.2
ueCapabilitiesRAT-Container-UTRAN ::=
SEQUENCE {

predefinedConfigStatusList CHOICE {
absent NULL
}
uE-SecurityInformation Not checked The value of start
CS is not used for
LTE to UMTS
handover in Rel-8

ue-CapabilityContainer CHOICE {
present Not checked Container
including UE radio
access capability

}
v390NonCriticalExtensions CHOICE {
present SEQUENCE {
interRATHandoverInfo-v390ext Not checked Positioning
capability and
dummy field

v3a0NonCriticalExtensions SEQUENCE {
interRATHandoverInfo-v3a0ext Not checked Positioning
capability

laterNonCriticalExtensions SEQUENCE {
interRATHandoverInfo-v3d0ext Not checked Deprecated
information

interRATHandoverInfo-r3-add-ext Not checked UE radio access
capability for
bands VIII to XIV,
UE radio access
capability
extension, support
of 2 DRX
schemes in
CELL_PCH,
support of E-
DPDCH power
interpolation

v3g0NonCriticalExtensions SEQUENCE {
interRATHandoverInfo-v3g0ext Not checked Positioning
capability
extension

v4b0NonCriticalExtensions SEQUENCE {
interRATHandoverInfo-v4b0ext Not checked Access Stratum
Release indicator

v4d0NonCriticalExtensions SEQUENCE {
interRATHandoverInfo-v4d0ext Not checked LCR TDD UE
capability

interRATHandoverInfo-v590ext Not checked Predefined
configuration
status information
compressed, UE
radio access
capability
compressed

interRATHandoverInfo-v690ext
SEQUENCE {

ue-SecurityInformation2 0 START PS
ue-RadioAccessCapabilityComp Not checked RF capability for
bands VIII to XIV

ue-RadioAccessCapabilityComp2 Not checked UE radio access
capability comp 2

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1100
1100
}
v6b0NonCriticalExtensions SEQUENCE
{

interRATHandoverInfo-v6b0ext Not checked Support for
SIB11bis

v6e0NonCriticalExtensions SEQUENCE
{

interRATHandoverInfo-v6e0ext Not checked Support of
FDPCH

v770NonCriticalExtensions
SEQUENCE {

interRATHandoverInfo-v770ext Note checked TDD RF and
physical channel
capability
extensions in Rel-
7, support of
GANSS, support
of MAC-ehs, LCR
TDD UE specific
capability
information

v790nonCriticalExtensions
SEQUENCE {

interRATHandoverInfo-v790ext Note checked Support of E-
DPCCH power
boosting

SEQUENCE {

interRATHandoverInfo-v860ext Note checked UE radio access
capability for
additional bands,
Rel-8 HS-DSCH
physical layer
category, support
of MAC-iis

SEQUENCE {
interRATHandoverInfo-v880ext Note checked Support for priority
reselection in
UTRAN, Rel-8
radio access
capability
extensions for
LCR TDD (e.g.
multi-carrier
operation)

nonCriticalExtensions
SEQUENCE {}
}
}
}
}
}
}
}
}
}
}
}
}
}
}
}
}

Release 9
3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1101
1101
Table 8.5.4.1.3.3-6: ueCapabilitiesRAT-Container-GERAN-CS
Mobile Station Classmark 2 First byte is 33H
Second byte is 3.
Third, Fourth and Fith
bytes are ignored.

Mobile Station Classmark 3 CSN.1 decoding shall be
successfull and the
contents shall indicate
that E-UTRA FDD or
EUTRA TDD or both is
supported.
Other values are not
checked.

Table 8.5.4.1.3.3-7: ueCapabilitiesRAT-Container-GERAN-PS
MS Radio Access Capability CSN.1 decoding shall be
successfull and the
contents shall indicate
that E-UTRA FDD or
EUTRA TDD or both is
supported.
Other values are not
checked.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1102 Release 9
1102
9 EPS mobility management
9.1 EMM common procedures
9.1.1 Void
9.1.1.1 Void
9.1.1.2 Void
9.1.2 Authentication procedure
9.1.2.1 Authentication accepted
(1)
with { a NAS signalling connection existing }
ensure that {
when { the UE receives an AUTHENTICATION REQUEST message }
then { the UE responds with a correct AUTHENTICATION RESPONSE message and establishes correct
EPS security context }
}
5.4.2.3 and TS 33.401, clause 6.1.1.
[TS 24.301, clause 5.4.2.1]
The UE shall support the EPS authentication challenge only if a USIM is present.
An EPS security context is established in the UE and the network when an EPS authentication is successfully performed.
During a successful EPS authentication, the CK and IK keys are computed. CK and IK are then used as key material to
compute a new key,K
ASME.
K
ASME
is stored in the EPS security contexts (see 3GPP TS 33.401 [19]) of both the network
and the UE, and is the root for the EPS integrity protection and ciphering key hierarchy.
[TS 24.301, clause 5.4.2.3]
The UE shall respond to an AUTHENTICATION REQUEST message. With the exception of the cases described in
subclause 5.4.2.6, the UE shall process the authentication challenge data and respond with an AUTHENTICATION
RESPONSE message to the network.
Upon a successful EPS authentication challenge, the new K
ASME
calculated from the authentication challenge data shall
be stored in a new EPS security context.
[TS 33.401, clause 6.1.1]
UE shall compute K
ASME
from CK, IK, and serving network's identity (SN id) using the KDF as specified in Annex A.
SN id binding implicitly authenticates the serving network's identity when the derived keys from K
ASME
are successfully
used.
...
UE shall respond with User authentication response message including RES in case of successful AUTN verification as
described in TS 33.102[4] and successful AMF verification as described above. Otherwise UE shall send User
authentication reject message with a proper CAUSE value.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1103 Release 9
1103
System Simulator:
- cell A.
UE:
- the UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and registered
on cell A using default message contents according to TS 36.508 [18]..
Preamble:
- the UE is in state Switched OFF (State 1) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1104 Release 9
1104
U - S Message
1 Switch the UE on - - - -
2 The UE transmit an ATTACH REQUEST
including a GUTI and a PDN CONNECTIVITY
REQUEST message
--> ATTACH REQUEST - -
3 SS transmits an AUTHENTICATION
REQUEST message, KSI
ASME
value is different
to the KSI
ASME
value provided in the ATTACH
REQUEST
<-- AUTHENTICATION REQUEST - -
4 Check: Does the UE respond with
AUTHENTICATION RESPONSE message
within 6 seconds and the included RES is
equal to the XRES calculated in the SS?
--> AUTHENTICATION RESPONSE 1 P
5 SS transmits a NAS SECURITY MODE
COMMAND message including the KSI
ASME
of
the new EPS security context (as provided in
step 3)
6 Check: Does the UE respond with NAS
SECURITY MODE COMPLETE message
integrity protected and ciphered with the new
EPS security context identified by the KSI
ASME

received in the SECURITY MODE COMMAND
message in step 5
--> SECURITY MODE COMPLETE 1 P
information which needs to be transferred.
- - - -
7a1 IF the UE sets the ESM information transfer
REQUEST message THEN the SS transmits
an ESM INFORMATION REQUEST message
to initiate exchange of protocol configuration
options and/or APN.
<-- ESM INFORMATION REQUEST - -
7a2 The UE transmits an ESM INFORMATION
RESPONSE message to transfer protocol
configuration options and/or APN.
--> ESM INFORMATION RESPONSE - -
8 SS responds with ATTACH ACCEPT
message. The ACTIVATE DEFAULT EPS
BEARER CONTEXT REQUEST message is
piggybacked in ATTACH ACCEPT message
<-- ATTACH ACCEPT - -
in step 9 below the generic procedure for IP
address allocation in the U-plane specified in
TS 36.508 subclause 4.5A.1 takes place
performing IP address allocation in the U-plane
if requested by the UE.
- - - -
9 The UE transmits an ATTACH COMPLETE
message including an ACTIVATE DEFAULT
EPS BEARER CONTEXT ACCEPT message
--> ATTACH COMPLETE - -
10a1 Void - - - -
11 SS releases the RRC connection - - - -
12 SS pages the UE using S-TMSI with CN
domain indicator set to "PS".
- - - -
13 Check: Does the UE respond with SERVICE
REQUEST message providing KSI
ASME
value
that equals the value provided in the
AUTHENTICATION REQUEST message in
Step 3, and, integrity protected with new EPS
security context?
--> SERVICE REQUEST 1 P
14-
17
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1105 Release 9
1105

Table 9.1.2.1.3.3-1: AUTHENTICATION RESPONSE (step 4, Table 9.1.2.1.3.2-1)
Authentication response parameter RES equal to the XRES
calculated in the SS with
the parameters
provided/indicated in the
AUTHENTICATION
REQUEST

9.1.2.2 Void
9.1.2.3 Authentication not accepted by the network / GUTI used / Authentication
reject and re-authentication
(1)
with { UE having sent an initial NAS message with type of identity GUTI }
ensure that {
when { as a result of failure of an Authentication procedure intiated by the network the UE
receives an AUTHENTICATION REJECT message }
then { the UE shall set the update status to EU3 ROAMING NOT ALLOWED, delete the stored GUTI,
TAI list, last visited registered TAI and KSI
ASME
and enter state EMM-DEREGISTERED }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses 5.4.2.5.
[TS 24.301, clause 5.4.2.5]
Upon receipt of an AUTHENTICATION REJ ECT message, the UE shall set the update status to EU3 ROAMING NOT
ALLOWED, delete the stored GUTI, TAI list, last visited registered TAI and KSI
ASME
. The USIM shall be considered
invalid until switching off the UE or the UICC containing the USIM is removed.
If the AUTHENTICATION REJ ECT message is received by the UE, the UE shall abort any EMM signalling procedure,
stop any of the timers T3410, T3417 or T3430 (if running) and enter state EMM-DEREGISTERED.
System Simulator:
- cell A.
UE:
- the UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and
registered on cell A using default message contents according to TS 36.508 [18].
Preamble:
- the UE is in state Switched OFF (state 1) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1106 Release 9
1106
U - S Message
message including a GUTI and a PDN
CONNECTIVITY REQUEST message
REQUEST message without integrity
protection and ciphering
RESPONSE.
--> AUTHENTICATION RESPONSE - -
REJ ECT message without integrity protection
and ciphering
<-- AUTHENTICATION REJ ECT - -
6 SS releases the RRC connection - - - -
7 Check: Does the UE transmit an ATTACH
REQUEST message in the next 30 seconds?
--> ATTACH REQUEST 1 F
procedure "Test procedure for no response to
paging (for NAS testing)" clause 6.4.2.5 [18]
indicates that the UE responds to paging when
paged with GUTI-1 and with CN domain
indicator set to "PS"?
- - 1 -
paged with IMSI and with CN domain indicator
set to "PS"?
- - 1 -
10 If possible (see ICS) switch off is performed or
the USIM is removed.
Otherwise the power is removed.
- - - -
11 The UE is brought back to operation or the
USIM is inserted.
- - - -
12 Check: Does UE transmit a NOT integrity
protected ATTACH REQUEST message
including IMSI and a PDN CONNECTIVITY
REQUEST message?
--> ATTACH REQUEST 1 P
13-
24
The attach procedure is completed by
executing steps 5 to 16 of the UE registration
procedure in TS 36.508 sub clause 4.5.2.3.
- - - -
- At the end of this test procedure sequence, the
UE is in end state E-UTRA connected (E2)
according to TS 36.508.
- - - -

Table 9.1.2.3.3.3-1a: ATTACH REQUEST (step 2, Table 9.1.2.3.3.2-1)
Old GUTI or IMSI GUTI-1 GUTI allocated in
pre-test
conditions.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1107 Release 9
1107
Table 9.1.2.3.3.3-1: ATTACH REQUEST (step 12, Table 9.1.2.3.3.2-1)
NAS key set identifier '111'B no key is available
Old GUTI or IMSI IMSI
Last visited registered TAI Not Present

9.1.2.4 Authentication not accepted by the UE / MAC code failure
(1)
ensure that {
when { the UE receives an AUTHENTICATION REQUEST message with invalid MAC code }
then { the UE shall send an AUTHENTICATION FAILURE message to the network, with the reject cause
#20 "MAC failure" }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses 5.4.2.6.
[TS 24.301, clause 5.4.2.6]
In an EPS authentication challenge, the UE shall check the authenticity of the core network by means of the AUTN
parameter received in the AUTHENTICATION REQUEST message. This enables the UE to detect a false network.
During an EPS authentication procedure, the UE may reject the core network due to an incorrect AUTN parameter (see
3GPP TS 33.401 [19]). This parameter contains three possible causes for authentication failure:
a) MAC code failure:
If the UE finds the MAC code (supplied by the core network in the AUTN parameter) to be invalid, the UE shall
send an AUTHENTICATION FAILURE message to the network, with the EMM cause #20 "MAC failure". The
UE shall then follow the procedure described in subclause 5.4.2.7, item c.
[TS 24.301, clause 5.4.2.7]
c) Authentication failure (EMM cause #20 "MAC failure"):
The UE shall send an AUTHENTICATION FAILURE message, with EMM cause #20 "MAC failure" according
to subclause 5.4.2.6, to the network and start timer T3418 (see example in figure 5.4.2.7.1). Furthermore, the UE
shall stop any of the retransmission timers that are running (e.g. T3410, T3417, T3421 or T3430). Upon the first
receipt of an AUTHENTICATION FAILURE message from the UE with EMM cause #20 "MAC failure", the
network may initiate the identification procedure described in subclause 5.4.4. This is to allow the network to
obtain the IMSI from the UE. The network may then check that the GUTI originally used in the authentication
challenge corresponded to the correct IMSI. Upon receipt of the IDENTITY REQUEST message from the
network, the UE shall send the IDENTITY RESPONSE message.
...
If the GUTI/IMSI mapping in the network was incorrect, the network should respond by sending a new
AUTHENTICATION REQUEST message to the UE. Upon receiving the new AUTHENTICATION REQUEST
message from the network, the UE shall stop the timer T3418, if running, and then process the challenge
information as normal.
System Simulator:
- cell A.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1108 Release 9
1108
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1109 Release 9
1109
U - S Message
2 The UE transmits an ATTACH REQUEST
message including a PDN CONNECTIVITY
REQUEST message
REQUEST message which contains an invalid
MAC code
4 Check: Does the UE respond with a
AUTHENTICATION FAILURE message, with
reject cause "MAC failure"?
--> AUTHENTICATION FAILURE 1 P
5 SS transmits an IDENTITY REQUEST
message requesting IMSI in the IE Identity
type
<-- IDENTITY REQUEST - -
6 The UE responds with a correct IDENTITY
RESPONSE message providing its IMSI in the
IE Mobile Identity
--> IDENTITY RESPONSE - -
7 SS transmits a correct AUTHENTICATION
REQUEST message, RAND different to the
one send in Step 3
8 Check: Does the UE respond with a correct
with RES that is equal to the XRES calculated
in the SS?
ASME
of
step 8)
10 UE transmits a NAS SECURITY MODE
COMPLETE message integrity protected and
ciphered with the new EPS security context
identified by the KSI
ASME
received in the
SECURITY MODE COMMAND message in
step 9
- - - -
11a
1
options and/or APN.
11a
2
The UE transmits an ESM INFORMATION
12 SS responds with ATTACH ACCEPT. The
ACTIVATE DEFAULT EPS BEARER
CONTEXT REQUEST message is
performing IP address allocation in the U-
plane if requested by the UE.
- - - -
14a
1
Void - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1110 Release 9
1110

Table 9.1.2.4.3.3-1: AUTHENTICATION REQUEST (step 3, Table 9.1.2.4.3.2-1)
Authentication parameter AUTN Invalid MAC SS shall calculate
the correct MAC
value as specified
in TS 33.102 and
use any different
value, e.g.
correct_MAC+5.

the parameters
AUTHENTICATION
REQUEST

9.1.2.5 Authentication not accepted by the UE / SQN failure
(1)
ensure that {
when { the UE receives an AUTHENTICATION REQUEST message with SQN out of range }
then { the UE sends an AUTHENTICATION FAILURE message to the network, with EMM cause "synch
failure" and a re-synchronization token }
}

(2)
with { UE having sent an AUTHENTICATION FAILURE message to the network, with EMM cause "synch
failure" }
ensure that {
when { the UE receives a new correct AUTHENTICATION REQUEST message while T3420 is running }
then { the UE sends a corect AUTHENTICATION RESPONSE message }
}

5.4.2.7.
[TS 24.301, clause 5.4.2.6]
In an EPS authentication challenge, the UE shall check the authenticity of the core network by means of the AUTN
parameter received in the AUTHENTICATION REQUEST message. This enables the UE to detect a false network.
During an EPS authentication procedure, the UE may reject the core network due to an incorrect AUTN parameter (see
3GPP TS 33.401 [19]). This parameter contains three possible causes for authentication failure:
...
c) SQN failure:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1111 Release 9
1111
If the UE finds the SQN (supplied by the core network in the AUTN parameter) to be out of range, the UE
shall send an AUTHENTICATION FAILURE message to the network, with the EMM cause #21 "synch
failure" and a re-synchronization token AUTS provided by the USIM (see 3GPP TS 33.102 [18]). The UE
shall then follow the procedure described in subclause 5.4.2.7, item e.
[TS 24.301, clause 5.4.2.7]
e) Authentication failure (EMM cause #21 "synch failure"):
The UE shall send an AUTHENTICATION FAILURE message, with EMM cause #21 "synch failure", to the
network and start the timer T3420 (see example in figure 5.4.2.7.2). Furthermore, the UE shall stop any of the
retransmission timers that are running (e.g. T3410, T3417, T3421 or T3430). Upon the first receipt of an
AUTHENTICATION FAILURE message from the UE with the EMM cause #21 "synch failure", the network
shall use the returned AUTS parameter from the authentication failure parameter IE in the AUTHENTICATION
FAILURE message, to re-synchronise. The re-synchronisation procedure requires the MME to delete all unused
authentication vectors for that IMSI and obtain new vectors from the HSS. When re-synchronisation is complete,
the network shall initiate the authentication procedure. Upon receipt of the AUTHENTICATION REQUEST
message, the UE shall stop the timer T3420, if running.
...
If the network is validated successfully (a new AUTHENTICATION REQUEST is received which contains a
valid SQN and MAC) while T3420 is running, the UE shall send the AUTHENTICATION RESPONSE
message to the network and shall start any retransmission timers (e.g. T3410, T3417, T3421 or T3430), if they
were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message.
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1112 Release 9
1112
U - S Message
REQUEST message
3 SS transmits AUTHENTICATION REQUEST
message with the AMF field in the IE
"Authentication parameter AUTN" set to
"AMF
RESYNCH
" value to trigger SQN re-
synchronisation procedure in test USIM
4 Check: Does the UE respond with a
AUTHENTICATION FAILURE message, with
EMM cause "synch failure"?
--> AUTHENTICATION FAILURE 1 P
type
6 The UE responds with IDENTITY RESPONSE
message providing its IMSI in the IE Mobile
Identity
--> IDENTITY RESPONSE - -
7 SS transmits AUTHENTICATION REQUEST
message
(Note 1)
8 Check: Does the UE respond with
with RES that is equal to the XRES calculated
in the SS?
ASME
of
step 8)
10 UE transmits a NAS SECURITY MODE
COMPLETE message integrity protected and
ciphered with the new EPS security context
identified by the KSI
ASME
received in the
SECURITY MODE COMMAND message in
step 9
- - - -
options and/or APN.
12 SS responds with ATTACH ACCEPT. The
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1113 Release 9
1113
14a1 Void - - - -
Note 1: The SS shall ensure that the AUTHENTICATION REQUEST message sent in step 7 is sent less than
(T3420-10%) sec after the message sent in step 4 otherwise it cannot be ensured that the UE will behave as
specified in step 8.

Authentication parameter AUTN AMF field set to
"AMF
RESYNCH
"

Table 9.1.2.5.3.3-2: AUTHENTICATION FAILURE (step 4, Table 9.1.2.5.3.2-1)
EMM cause '0001 0101'B Synch failure
Authentication failure parameter '1111 1111 1111 1111'B AMF
RESYNCH
see
TS 34.108, 8.1.2.2

the parameters
AUTHENTICATION
REQUEST

9.1.2.6 Abnormal cases / Network failing the authentication check
(1)
with { UE in EMM-REGISTERED state / EMM-CONNECTED mode}
ensure that {
when { UE receives an AUTHENTICATION REQUEST message but UE deems that the network failed the
authentication check }
then { UE locally release the RRC connection and treat the active cell as barred }
}

[TS 24.301, clause 5.4.2.7]
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 EMM cause #20 "MAC failure" the
timer T3418 expires;

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 proceed as described in item f.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1114 Release 9
1114
f) Network failing the authentication check:
If the UE deems that the network has failed the authentication check, then it shall request RRC to locally release
the RRC connection and treat the active cell as barred (see 3GPP TS 36.331 [22]). The UE shall start any
retransmission timers (e.g. T3410, T3417, T3421 or T3430), if they were running and stopped when the UE
received the first AUTHENTICATION REQUEST message containing an invalid MAC or SQN.
System Simulator:
- Cell A and Cell I are configured according to table 6.3.2.2-1 in TS 36.508 [18];
- cell A and cell I belong to different PLMNs and different frequencies.
UE:
none.
Preamble:
- the UE is in state Switched OFF (state 1) according to clause [18].
U - S Message
1 The SS configures:
- Cell A as the "Serving cell".
- Cell I as a " Suitable cell".
- - - -
- The following messages are to be observed on
Cell A unless explicitly stated otherwise.
- - - -
REQUEST message.
REQUEST message which contains an invalid
MAC code
5 UE responds with an AUTHENTICATION
FAILURE message, with reject cause "MAC
failure" .
--> AUTHENTICATION FAILURE - -
6 SS responds nothingand waits for the
expiration of T3418.

Cell I unless explicitly stated otherwise.
- - - -
REQUEST message including a PDN
CONNECTIVITY REQUEST message in the
next 30 seconds after T3418 expired?
8-
19
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1115 Release 9
1115
Authentication parameter AUTN Invalid MAC SS shall calculate
the correct MAC
value as specified
in TS 33.401 and
use any different
value, e.g.
correct_MAC+5.

Table 9.1.2.6.3.3-2: AUTHENTICATION FAILURE (step 5, Table 9.1.2.6.3.2-1)
EMM cause '0001 0100'B MAC failure
Authentication failure parameter Not present

9.1.3 Security mode control procedure
9.1.3.1 NAS security mode command accepted by the UE
(1)
with { succesful completion of EPS authentication and key agreement (AKA) procedure }
ensure that {
when { UE receives an integrity protected SECURITY MODE COMMAND message including replayed
security capabilities and IMEISV request }
then { UE sends an integrity protected and ciphered SECURITY MODE COMPLETE message including
IMEISV and starts applying the NAS Security in both UL and DL }
(2)
with { NAS Security Activated and EPS Authentication and key agreement procedure is executed for new
Key generation}
ensure that {
when { UE receives an integrity protected SECURITY MODE COMMAND message corresponding to NAS count
reset to zero including replayed security capabilities and IMEISV request }
then { UE sends integrity protected and ciphered SECURITY MODE COMPLETE message [with NAS count
set to zero] including IMEISV and starts applying the NAS Security in both UL and DL}
}
References: The conformance requirements covered in the current TC are specified in: TS 24.301 clause 4.4.3.1, 5.4.3.1,
5.4.3.2 and 5.4.3.3.
[TS 24.301, clause 4.4.3.1]
Each EPS NAS security context shall be associated with two separate counters NAS COUNT: one related to uplink
NAS messages and one related to downlink NAS messages. The NAS COUNT counters use 24 bit internal
representation and are independently maintained by UE and MME. The NAS COUNT shall be constructed as a NAS
sequence number (8 least significant bits) concatenated with a NAS overflow counter (16 most significant bits).
When NAS COUNT is input to NAS ciphering or NAS integrity algorithms it shall be considered to be a 32-bit entity
which shall be constructed by padding the 24-bit internal representation with 8 zeros in the most significant bits.
During the handover from UTRAN/GERAN to E-UTRAN, if the mapped EPS security context is taken into use, the
NAS COUNT values for this EPS security context shall be initialized to zero in the UE and the network for uplink and
downlink NAS messages.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1116 Release 9
1116
The NAS sequence number part of the NAS COUNT shall be exchanged between the UE and the MME as part of the
NAS signalling. After each new or retransmitted outbound security protected NAS message, the sender shall increase
the NAS COUNT number by one. Specifically, on the sender side, the NAS sequence number shall be increased by one,
and if the result is zero (due to wrap around), the NAS overflow counter shall also be incremented by one (see
subclause 4.4.3.5). The receiving side shall estimate the NAS COUNT used by the sending side. Specifically, if the
estimated NAS sequence number wraps around, the NAS overflow counter shall be incremented by one.
[TS 24.301, clause 5.4.3.1]
The purpose of the NAS security mode control procedure is to take an EPS security context into use, and initialise and
start NAS signalling security between the UE and the MME with the corresponding NAS keys and security algorithms.
[TS 24.301, clause 5.4.3.2]
The MME initiates the NAS security mode control procedure by sending a SECURITY MODE COMMAND message
to the UE and starting timer T3460 (see example in figure 5.4.3.2.1).
If the security mode control procedure is initiated further to a successful execution of the authentication procedure, the
MME shall use the reset downlink NAS COUNT to integrity protect the SECURITY MODE COMMAND message.
The MME shall send the SECURITY MODE COMMAND message unciphered, but shall integrity protect the message
with the NAS integrity key based on K
ASME
or mapped K'
ASME
indicated by the eKSI included in the message. The
MME shall set the security header type of the message to "integrity protected with new EPS security context".
...
The MME shall include the replayed security capabilities of the UE (including the security capabilities with regard to
NAS, RRC and UP (user plane) ciphering as well as NAS, RRC integrity, and other possible target network security
capabilities, i.e. UTRAN/GERAN if UE included them in the message to network), the replayed nonce
UE
if the UE
included it in the message to the network, the selected NAS ciphering and integrity algorithms and the Key Set
Identifier (eKSI).
Additionally, the MME may request the UE to include its IMEISV in the SECURITY MODE COMPLETE message.
NOTE: The AS and NAS security capabilities will be the same, i.e. if the UE supports one algorithm for NAS it is
also be supported for AS.
[TS 24.301, clause 5.4.3.3]
Upon receipt of the SECURITY MODE COMMAND message, the UE shall check whether the security mode
command can be accepted or not. This is done by performing the integrity check of the message and by checking that
the received UE security capabilities and the received nonce
UE
have not been altered compared to what the UE provided
in the initial layer 3 message that triggered this procedure.
If the type of security context flag is set to "native security context" and if the KSI matches a valid native EPS security
context held in the UE while the UE has a mapped EPS security context as the current security context, the UE shall
take the native EPS security context into use. The UE shall store the native EPS security context, as specified in
annex C.
If the security mode command can be accepted, the UE shall reset the uplink NAS COUNT and the UE shall take the
new EPS security context into use when:
a) the SECURITY MODE COMMAND message is received further to a successful execution of the authentication
procedure; or
b) the type of security context flag is set to "mapped security context" in the NAS KSI IE included in the SECURITY
MODE COMMAND message.
If the security mode command can be accepted and the eKSI was included in the SECURITY MODE COMMAND
message, the UE shall send a SECURITY MODE COMPLETE message integrity protected with the selected NAS
integrity algorithm and the NAS integrity key based on the K
ASME
or mapped K'
ASME
if the type of security context flag
is set to "mapped security context"indicated by the eKSI. If the SECURITY MODE COMMAND message includes the
type of security context flag set to "mapped security context" in the NAS KSI IE, nonce
MME
and nonce
UE
, the UE shall
generate K'
ASME
from both nonces as indicated in 3GPP TS 33.401 [19] and reset the downlink NAS COUNT to check
whether the SECURITY MODE COMMAND can be accepted or not. The UE shall cipher the SECURITY MODE

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1117 Release 9
1117
COMPLETE message with the selected NAS ciphering algorithm and the NAS ciphering key based on the K
ASME
or
mapped K'
ASME
indicated by the eKSI. The UE shall set the security header type of the message to "integrity protected
and ciphered with new EPS security context".
From this time onwards the UE shall cipher and integrity protect all NAS signalling messages with the selected NAS
ciphering and NAS integrity algorithms.
If the MME indicated in the SECURITY MODE COMMAND message that the IMEISV is requested, the UE shall
include its IMEISV in the SECURITY MODE COMPLETE message.
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1118 Release 9
1118
U - S Message
REQUEST message.
RESPONSE message and establishes mutual
authentication.
COMMAND message to activate NAS security.
It is integrity protected and includes request to
include IMEISV
6 Check: Does the UE transmit a SECURITY
MODE COMPLETE message and does it
establish the initial security configuration?
- EXCEPTION: Steps 6Aa1 to 6Aa2 describe
- - - -
6A
a1
options and/or APN.
6A
a2
7 The SS transmits an ATTACH ACCEPT
--> ATTACH COMPLETE -
9 The SS Transmits an IDENTITY REQUEST
message [Security protected]
<- IDENTITY REQUEST - -
10 Check: Does the UE transmit an IDENTIY
RESPONSE message [Security Protected]?
-> IDENTITY RESPONSE 1 P
authentication and AKA procedure for new key
set generation.
authentication.
13 SS resets UL and DL NAS Count to zero - - - -
include IMEISV
COMPLETE message and establishes the
initial security configuration.
Exception : Steps 16 and 17 are executed 100
times to check UE is applying security correctly

16 The SS transmits an IDENTITY REQUEST
message [Security protected]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1119 Release 9
1119
17 Check: Does the UE transmit an IDENTIY
RESPONSE message [Security Protected]?

Table 9.1.3.1.3.3-1: SECURITY MODE COMMAND (Steps 5 and 14)
IMEISV request Present

Table 9.1.3.1.3.3-2: SECURITY MODE COMPLETE (Steps 6 and 15)
IMEISV Present

9.1.3.2 NAS security mode command not accepted by the UE
(1)
with { succesful completion of EPS authentication and key agreement (AKA) procedure[ }
ensure that {
when { UE receives an integrity protected SECURITY MODE COMMAND message including not mathcing
replayed security capabilities}
then { UE sends SECURITY MODE REJECT and does not start applying the NAS security in both UL and
DL}
}
5.4.3.3 and 5.4.3.5.
[TS 24.301, clause 5.4.3.1]
[TS 24.301, clause 5.4.3.2]
ASME
or mapped K'
ASME
...
UE
if the UE
Identifier (eKSI).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1120 Release 9
1120
[TS 24.301, clause 5.4.3.3]
UE
[TS 24.301, clause 5.4.3.5]
If the security mode command cannot be accepted, the UE shall send a SECURITY MODE REJ ECT message, which
shall not be integrity protected. The SECURITY MODE REJ ECT message contains an EMM cause that typically
indicates one of the following cause values:
#23: UE security capabilities mismatch;
#24: security mode rejected, unspecified.
.
Upon receipt of the SECURITY MODE REJ ECT message, the MME shall stop timer T3460. The MME shall also abort
the ongoing procedure that triggered the initiation of the NAS security mode control procedure.
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1121 Release 9
1121
U - S Message
REQUEST message.
authentication.
It is integrity protected and includes un
matched replayed security capabilities.
6 Check: Does the UE transmit a NAS
SECURITY MODE REJ ECT message with
cause#23: UE security capabilities mismatch?
--> SECURITY MODE REJ ECT 1 P
message for IMSI (Security not applied)
8 Check: Does the UE Transmits a non security
protected IDENTIY RESPONSE message?
include IMEISV
- - - -
10
Aa
1
options and/or APN.
10
A
a2

Table 9.1.3.1.3.3-1: SECURITY MODE COMMAND (Step 5)
Replayed UE security capabilities Set to mismatch the
security capability of UE
under test

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1122 Release 9
1122
Table 9.1.3.1.3.3-2: SECURITY MODE REJECT (Step 6 )
EMM cause #23

9.1.4 Identification procedure
9.1.4.1 Void
9.1.4.2 Identification procedure / IMEI requested
(1)
with { UE in EMM-REGISTERED state / EMM-CONNECTED mode}
ensure that {
when { UE receives an IDENTITY REQUEST message with IMEI in the IE Identity type }
then { UE sends an IDENTITY RESPONSE message providing its IMEI }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.4.4.3.
[TS 24.301, clause 5.4.4.3]
A UE shall be ready to respond to an IDENTITY REQUEST message at any time whilst in EMM-CONNECTED mode.
Upon receipt of the IDENTITY REQUEST message the UE shall send an IDENTITY RESPONSE message to the
network. The IDENTITY RESPONSE message shall contain the identification parameters as requested by the network.
System Simulator:
- cell A.
UE:
none.
Preamble:
- the UE is in state Generic RB established (state 3) on cell A according to TS 36.508 [18].
U - S Message
message requesting IMEI in the IE Identity
type.
2 Check: Does the UE respond with an
IDENTITY RESPONSE message providing its
IMEI?
--> IDENTITY RESPONSE 1 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1123 Release 9
1123
Table 9.1.4.2.3.3-1: Message IDENTITY REQUEST (step 1, Table 9.1.4.2.3.2-1)
Deri vation Path: 36.508, Table 4.7.2-17
Identity Type 0010 IMEI

Table 9.1.4.2.3.3-2: IDENTITY RESPONSE (step 2, Table 9.1.4.2.3.2-1)
Deri vation path: 36.508, Table 4.7.2-18
Mobile Identity
Type of identity 010 IMEI
Identity digits UE's IMEI

9.1.5 EMM information procedure
9.1.5.1 EMM information procedure
(1)
with { UE in EMM-REGISTERED state and UE supporting the EMM information message }
ensure that {
when { UE receives an EMM Information message }
then { UE accepts the message and uses the contents to update appropriate information stored
within the UE }
}

[TS 24.301, clause 5.4.5.3]
When the UE (supporting the EMM information message) receives an EMM INFORMATION message, it shall accept
the message and optionally use the contents to update appropriate information stored within the UE.
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1124 Release 9
1124
U - S Message
1 The SS transmits an EMM INFORMATION
message.
<-- EMM INFORMATION - -
2 Check: Does the UE transmit in the next 5
seconds an EMM STATUS message with
cause #97 "message type non-existent or not
implemented"?
--> EMM STATUS 1 F
sequence that take place if a capability is
supported.
- - - -
3a1 IF pc_EMM_Information AND
pc_FullNameNetwork THEN
Check: Does the UE associate the "full length
name of the network" with the MCC and MNC
contained in the last visited tracking area
identification and is presented to the MS user
at the earliest opportunity? (Note 1)
- - 1 P
3b1 IF pc_EMM_Information AND
pc_ShortNameNetwork THEN
Check: Does the UE associate the
"abbreviated name of the network" with the
MCC and MNC contained in the last visited
tracking area identification and is presented to
the MS user at the earliest opportunity? (Note
1)
- - 1 P
3c1 IF pc_EMM_Information AND
pc_LocalTimeZone THEN
Check: Does the UE assume that this time
zone applies to the tracking area of the current
cell and is presented to the MS user at the
earliest opportunity? (Note 2)
- - 1 P
3d1 IF pc_EMM_Information AND
pc_UniversalAndLocalTimeZone THEN
Check: Does the UE assume that this time
zones applies to the tracking area of the
current cell and is presented to the MS user at
the earliest opportunity? (Note 2)
- - 1 P
Note 1: AT command +COPS is assumed to be used for check.
Note 2: AT command +CCLK is assumed to be used for check.

Table 9.1.5.1.3.3-1: EMM INFORMATION (step 1, Table 9.1.5.1.3.2-1)
Full name for network "FullName1234567890" Note
Short name for network "ShortName123" Note
Local time zone "GMT+1" Note
Universal time and local time zone "2010 12 April 13:38 52s
GMT+1"
Note
Network daylight saving time "+1 hour adjustment for
Daylight Saving Time"
Note
Note: Hardcoded values have been chosen to allow for consistent/comparable SS behaviour.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1125 Release 9
1125
Table 9.1.5.1.3.3-2: Message EMM STATUS (step 2, Table 9.1.5.1.3.2-1)
EMM cause '0110 0001'B Message type
non-existent or
not implemented

9.1.5.2 EMM information procedure not supported by the UE
(1)
with { UE in EMM-REGISTERED state }
ensure that {
when { UE receives an EMM Information message }
then { UE ignore the contents of the message and return an EMM STATUS message with cause #97
"message type non-existent or not implemented" }
}

[TS 24.301, clause 5.4.5.3]
If the UE does not support the EMM information message the UE shall ignore the contents of the message and return an
EMM STATUS message with cause #97 "message type non-existent or not implemented".
System Simulator:
- cell A.
UE:
none.
Preamble:
U - S Message
1 The SS transmits an EMM INFORMATION
message.
<-- EMM INFORMATION - -
2 Check: Does the UE transmit an EMM
STATUS message with cause #97 "message
type non-existent or not implemented".
--> EMM STATUS 1 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1126 Release 9
1126
Table 9.1.5.2.3.3-1: EMM INFORMATION (step 1, Table 9.1.5.2.3.2-1)
Full name for network Not present
Short name for network Not present
Local time zone Not present
Universal time and local time zone Not present
Network daylight saving time 00B No adjustment for
Daylight Saving
Time

Table 9.1.5.2.3.3-2: Message EMM STATUS (step 2, Table 9.1.5.2.3.2-1)
EMM cause '0110 0001'B Message type
non-existent or
not implemented

9.2 EMM specific procedures
9.2.1 Attach procedure
9.2.1.1 Attach procedure for EPS services
9.2.1.1.1 Attach / Success / Valid GUTI
(1)
with { the UE is switched-off with a valid USIM inserted and the USIM contains a valid GUTI and last
visited registered TAI }
ensure that {
when { UE is powered on in a cell not belonging to the last visited registered TAI and in a
different PLMN }
then { the UE establishes the RRC connection without S-TMSI, with registeredMME and with the RRC
establishmentCause set to 'mo-Signalling' }
}
(2)
with { UE is switched-off with a valid USIM inserted and the USIM contains a valid GUTI and last
visited registered TAI }
ensure that {
when { UE is powered on in a cell not belonging to the last visited registered TAI }
then { the UE transmits an ATTACH REQUEST message with the EPS attach type set to "EPS attach",
including the GUTI and last visited registered TAI copied from the USIM, and, a PDN CONNECTIVITY
REQUEST message with the request type set to "initial request" and not including APN }
}
(3)
with { UE has sent an ATTACH REQUEST message }
ensure that {
when { UE receives an ATTACH ACCEPT message with EPS attach result matching the requested
service(s), the TAI list the UE is registered to and including an ACTIVATE DEFAULT EPS CONTEXT
BEARER message with IE EPS Bearer Identity for the default EPS bearer context activated for the UE }
then { UE accepts the allocated GUTI, deletes the old TAI list and transmits an ATTACH COMPLETE
message, together with ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and enters EMM-REGISTERED
state }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1127 Release 9
1127
5.5.1.2.1, 5.5.1.2.2, 5.5.1.2.4, 6.2.2, 6.4.1.3, 6.5.1.2 and Annex D, and TS 36.331, clauses 5.3.3.3 and 5.3.3.4.
[TS 24.301, clause 5.3.1.1]
When the UE is in EMM-IDLE mode and needs to transmit an initial NAS message, the UE shall request the lower
layer to establish a RRC connection. In this request to the lower layer the NAS shall provide to the lower layer the RRC
establishment cause and the call type as specified in annex D of this specification.
...
For the routing of the initial NAS message to the appropriate MME, the UE NAS provides the lower layers with either
the S-TMSI or the registered globally unique MME identifier (GUMMEI) that consists of the PLMN ID, the MME
group ID, and the MME code (see 3GPP TS 23.003 [2]) according to the following rules:
- When the UE is registered in the tracking area of the current cell during the NAS signalling connection
establishment, the UE NAS shall provide the lower layers with the S-TMSI, but shall not provide the registered
MME identifier to the lower layers. Exceptionally, when the UE in EMM-IDLE mode initiates a tracking area
updating or combined tracking area updating procedure for load balancing purposes, the UE NAS shall provide
the lower layers with neither S-TMSI nor registered MME identifier.
- When the UE is not registered in the tracking area of the current cell during the NAS signalling connection
establishment, the UE NAS does not provide the lower layers with the S-TMSI. Instead,
a) if the TIN indicates "GUTI" or "RAT-related TMSI", or the TIN is not available, and the UE holds a valid
GUTI, the UE NAS shall provide the lower layers with the MME identifier part of the valid GUTI; or
b) if the TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and RAI, the UE NAS shall provide the lower
layers with the MME identifier part of the mapped GUTI, which is generated from the P-TMSI and RAI.
[TS 24.301, clause 5.5.1.1]
The attach procedure is used to attach to an EPC for packet services in EPS.
The attach procedure is used for two purposes:
- by a UE in PS mode of operation to attach for EPS services only; or
- by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for both EPS and non-EPS services.
With a successful attach procedure, a context is established for the UE in the MME, and a default bearer is established
between the UE and the PDN GW, thus enabling always-on IP connectivity to the UE. The network may also initiate
the activation of dedicated bearers as part of the attach procedure.
...
[TS 24.301, clause 5.5.1.2.1]
This procedure is used by a UE to attach for EPS services only. When the UE initiates the EPS attach procedure, the UE
shall indicate "EPS attach" in the EPS attach type IE.
[TS 24.301, clause 5.5.1.2.2]
In state EMM-DEREGISTERED, the UE initiates the attach procedure by sending an ATTACH REQUEST message to
the MME, starting timer T3410 and entering state EMM-REGISTERED-INITIATED (see example in
figure 5.5.1.2.2.1). If timer T3402 is currently running, the UE shall stop timer T3402. If timer T3411 is currently
running, the UE shall stop timer T3411.
If the UE supports neither A/Gb mode nor Iu mode, the UE shall handle the Old GUTI or IMSI IE in the ATTACH
REQUEST message as follows:
- The UE shall include in the ATTACH REQUEST message a valid GUTI together with the last visited registered
TAI, if available. If there is no valid GUTI available, the UE shall include the IMSI in the ATTACH REQUEST
message.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1128 Release 9
1128
...
The UE shall send the ATTACH REQUEST message together with a PDN CONNECTIVITY REQUEST message
contained in the ESM message container information element to request PDN connectivity.
...
If a valid NAS security context exists, the UE shall integrity protect the ATTACH REQUEST message combined with
the PDN CONNECTIVITY REQUEST message. When the UE does not have a valid NAS security context, the
ATTACH REQUEST message combined with the PDN CONNECTIVITY REQUEST message is not integrity
protected.
...
[TS 24.301, clause 5.5.1.2.4]
...
If the ATTACH ACCEPT message contains a GUTI, the UE shall use this GUTI as the new temporary identity. The
UE shall delete its old GUTI and store the new assigned GUTI. If no GUTI has been included by the MME in the
ATTACH ACCEPT message, the old GUTI, if any available, shall be kept.
...
When the UE receives the ATTACH ACCEPT message combined with the ACTIVATE DEFAULT EPS BEARER
CONTEXT REQUEST message, it shall forward the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST
message to the ESM sublayer. Upon receipt of an indication from the ESM sublayer that the default EPS bearer context
has been activated, the UE shall send an ATTACH COMPLETE message together with an ACTIVATE DEFAULT
EPS BEARER CONTEXT ACCEPT message contained in the ESM message container information element to the
network.
...
[TS 24.301, clause 6.2.2]
The UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message based on its IP stack
configuration as follows:
a) A UE, which is IPv6 and IPv4 capable and
- has not been allocated an IP address for this APN, shall set the PDN type IE to IPv4v6.
- has been allocated an IPv4 address for this APN and received the ESM cause #52, "single address bearers
only allowed", and is requesting an IPv6 address, shall set the PDN type IE to IPv6.
- has been allocated an IPv6 address for this APN and received the ESM cause #52, "single address bearers
b) A UE, which is only IPv4 capable, shall set the PDN type IE to IPv4.
c) A UE, which is only IPv6 capable, shall set the PDN type IE to IPv6.
d) When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are
separated and the capability of the TE is not known in the MT), the UE shall set the PDN type IE to IPv4v6.
...
[TS 24.301, clause 6.4.1.3]
Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall send an
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT
ACTIVE. When the default bearer is activated as part of the attach procedure, the UE shall send the ACTIVATE
DEFAULT EPS BEARER CONTEXT ACCEPT message together with ATTACH COMPLETE message. When the
default bearer is activated as the response to the stand-alone PDN CONNECTIVITY REQUEST message, the UE shall
send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message alone.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1129 Release 9
1129
The UE checks the PTI in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to identify the
UE requested PDN connectivity procedure to which the default bearer context activation is related (see subclause 6.5.1).
...
[TS 24.301, clause 6.5.1.2]
When the PDN CONNECTIVITY REQUEST message is sent together with an ATTACH REQUEST message, the UE
shall not include the APN.
NOTE: If the UE needs to provide PCO which require ciphering or provide an APN, or both, during the attach
procedure, the ESM information transfer flag is included in the PDN CONNECTIVITY REQUEST. The
MME then at a later stage in the PDN connectivity procedure initiates the ESM information request
procedure in which the UE can provide the MME with PCO or APN or both.
...
The UE shall set the request type to "initial request" when the UE is establishing connectivity to a PDN for the first time,
i.e. when it is an initial attach to that PDN. The UE shall set the request type to "handover" when the connectivity to a
PDN is established upon handover from a non-3GPP access network and the UE was connected to that PDN before the
handover to the 3GPP access network.
...
[TS 24.301, Annex D]
...
Table D.1.1: Mapping of NAS procedure to establishment cause and call type
NAS procedure RRC establishment cause (according 3GPP TS 36.331 [22]) Call type
Attach MO signalling (See Note 1) "originating signalling"
...
Note 1: For these NAS procedures initiated by UEs of access class 12, 13 or 14 in their home country, the RRC
establishment cause will be set to "High priority access AC 11 15". For this purpose the home country is
defined as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A].
For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN or (if the EHPLMN list
is not present or is empty) EHPLMN, (if the EHPLMN list is present) the RRC establishment cause will be
set to "High priority access AC 11 15".

[TS 36.331, clause 5.3.3.3 Actions related to transmission of RRCConnectionRequest message]
2>else
40
[TS 36.331 clause 5.3.3.4]
...
The UE shall:
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1130 Release 9
1130
...
procedure ends;
System Simulator:
- cell A.
UE:
- the UE is configured to initiate EPS attach;
- The UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and
registered on cell H using default message contents according to TS 36.508 [18].
NOTE: For cell H, (MNC, MCC, TAI) is (MCC stored in EF
IMSI
, 02, TAI-8).
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1131 Release 9
1131
U - S Message
RRCConnectionRequest message not
including S-TMSI and with
establishmentCause set to mo-Signalling?
- - 1 P
3 The SS transmits a RRCConnectionSetup
message.
- - - -
including PLMN ID, MME group ID and MME
code with ATTACH REQUEST message
including a GUTI and a PDN CONNECTIVITY
REQUEST message?
authentication.
behaviour that depends on UE configuration
sequence that take place depending on the
last sent by the UE PDN CONNECTIVITY
REQUEST message, IE Protocol configuration
options setting.
- - - -
options and/or APN.
10 SS responds with ATTACH ACCEPT message
including a valid TAI list. The ACTIVATE
DEFAULT EPS BEARER CONTEXT
REQUEST message is piggybacked in
ATTACH ACCEPT message
- - - -
11 Check: does the UE transmit an ATTACH
COMPLETE message including an ACTIVATE
DEFAULT EPS BEARER CONTEXT ACCEPT
message?
--> ATTACH COMPLETE 2 P
12 Void - - - -
13 The SS releases the RRC connection. - - - -
procedure [18] clause 6.4.2.4 indicate that the
UE is in E-UTRA EMM-REGISTERED state on
Cell A?
- - 3 -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1132 Release 9
1132
UE is in end state E-UTRA idle (E1) according
to TS 36.508.
- - - -

Table 9.2.1.1.1.3.3-1: Message RRCConnectionRequest (step 2, Table 9.2.1.1.1.3.2-1)
ue-Identity CHOICE {
randomValue Not checked
}
}
}
}

Table 9.2.1.1.1.3.3-2: Message RRCConnectionSetupComplete (step 2, Table 9.2.1.1.1.3.2-2)
c1 CHOICE {
registeredMME {
plmn-Identity PLMN ID(MCC as stored
in EF
IMSI
on the test
USIM card and MNC 02)

mmegi 0000000000001000 Bit 0 is LSB
mmec 00000001 Bit 0 is LSB
}
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1133 Release 9
1133
Table 9.2.1.1.1.3.3-3: Message ATTACH REQUEST (step 4, Table 9.2.1.1.1.3.2-1)
Derivation path: TS 36.508 table 4.7.2-4
Old GUTI or IMSI GUTI(belonging to PLMN
with same MCC as
stored in EF
IMSI
on the
test USIM card and MNC
02 )
GUTI copied from
USIM
Old and valid
GUTI is included
by the UE

ESM message container PDN CONNECTIVITY
REQUEST message as
specified in table
9.2.1.1.1.3.3-3.

Last visited registered TAI TAI8 GUTI copied from
USIM
If available, the
last TAI is
included by UE
and will be used
to establish a
good list of TAIs
in subsequent
ATTACH
ACCEPT
message.

Table 9.2.1.1.1.3.3-4: Void

Table 9.2.1.1.1.3.3-5: Message ATTACH ACCEPT (step 10, Table 9.2.1.1.1.3.2-1)
ESM message container Contains the ACTIVATE
DEFAULT EPS BEARER
CONTEXT REQUEST
message specified in
table 9.2.1.1.1.3.3-6.

Table 9.2.1.1.1.3.3-6: Void

Table 9.2.1.1.1.3.3-7: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 11, Table
9.2.1.1.1.3.2-1)
EPS bearer identity Default EBId Same value as in
ACTIVATE
DEFAULT EPS
BEARER
CONTEXT
REQUEST

Procedure transaction identity PTI-0 Same value as in
PDN
CONNECTIVITY
REQUEST

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1134 Release 9
1134
9.2.1.1.1a Attach Procedure / Success / Last visited TAI, TAI list and equivalent PLMN list
handling
9.2.1.1.1a.1 Test Purpose (TP)
(1)
with { UE attached to the network with a valid USIM inserted and a valid GUTI}
ensure that {
when { UE is powered off and then powered on }
then { the UE transmits an ATTACH REQUEST message with the EPS attach type set to "initial EPS
attach", including GUTI and last visited registered TAI and a PDN CONNECTIVITY REQUEST message with
the request type set to "initial attach" and not including APN }
}

(2)
with { UE having a valid NAS security context and the UE switched-off }
ensure that {
when { UE is powered on}
then { the UE transmits an integrity protected ATTACH REQUEST message combined with the PDN
CONNECTIVITY REQUEST message}
}
(3)
ensure that {
service(s), the TAI list the UE is registered to, a set of equivalent PLMNs matching the PLMNs
within the TAI list, and including an ACTIVATE DEFAULT EPS CONTEXT BEARER message with IE EPS Bearer
Identity for the default EPS bearer context activated for the UE }
then { UE deletes the old TAI list, stores the new TAI list, and does not perform a TAU while
moving within this set of TAs }
}

(4)
ensure that {
service(s), the TAI list the UE is registered to, a set of equivalent PLMNs matching the PLMNs
within the TAI list, and including an ACTIVATE DEFAULT EPS CONTEXT BEARER message with IE EPS Bearer
Identity for the default EPS bearer context activated for the UE }
then { UE deletes the old TAI list, stores the new TAI list, and performs a TAU when moving out
of this set of TAs}
}

(5)
with { UE has received a set of equivalent PLMNs in an ATTACH ACCEPT message }
ensure that {
when { the UE has been switched off; then switched on; and then the UE receives an ATTACH_ACCEPT
message with a new set of equivalent PLMNs}
then { UE deletes the old equivalent PLMN list, and uses the new equivalent PLMN list}
}

9.2.1.1.1a.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses 5.3.3,
5.5.1.2.2, 5.5.1.2.4, 6.5.1.2 and 9.9.3.33, and TS 36.304 clause 4.3.
[TS 24.301, clause 5.3.3]
The UE shall store a list of equivalent PLMNs. These PLMNs shall be regarded by the UE as equivalent to each other
for PLMN selection and cell selection/re-selection. The same list is used by EMM, GMM and MM.
The UE shall update or delete this list at the end of each attach or tracking area updating procedure. The stored list
consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that
downloaded the list. When the UE is switched off, it shall keep the stored list so that it can be used for PLMN selection

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1135 Release 9
1135
after switch on. The UE shall delete the stored list if the USIM is removed. The maximum number of possible entries in
the stored list is 16.
[TS 24.301, clause 5.5.1.2.2]
the MME, starting timer T3410 and entering state EMM-REGISTERED-INITIATED (see figure 5.5.1.2.2.1).
...
The UE shall include in the ATTACH REQUEST message a valid GUTI together with the last visited registered TAI, if
available. If there is no valid GUTI available, the UE shall include the IMSI in the ATTACH REQUEST message.
The UE shall send the ATTACH REQUEST message together with a PDN CONNECTIVITY REQUEST message to
request PDN connectivity to the default PDN (see subclause 6.5.1).
...
If a valid NAS security context exists, the UE shall integrity protect the ATTACH REQUEST message combined with
the PDN CONNECTIVITY REQUEST message.
...[TS 24.301, clause 5.5.1.2.4]
...
The MME shall assign and include the TAI list the UE is registered to in the ATTACH ACCEPT message. The UE,
upon receiving an ATTACH ACCEPT message, shall delete its old TAI list and store the received TAI list.

If the ATTACH ACCEPT message contains a GUTI, the UE shall use this GUTI as the new temporary identity and set
its TIN to "GUTI". The UE shall delete its old GUTI and store the new assigned GUTI. If no GUTI has been included
by the MME in the ATTACH ACCEPT message, the old GUTI, if any available, shall be kept.
...
The MME may also include a list of equivalent PLMNs in the ATTACH ACCEPT message. Each entry in the list
contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, after having removed
from the list any PLMN code that is already in the list of forbidden PLMNs. In addition, the UE shall add to the stored
list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the
ATTACH ACCEPT message. If the ATTACH ACCEPT message does not contain a list, then the UE shall delete the
stored list.

[TS 24.301, clause 5.5.3.2.2, Normal and periodic tracking area updating procedure initiation]
The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING
AREA UPDATE REQUEST message to the MME,
a) when the UE detects entering a tracking area that is not in the list of tracking areas that the UE previously
registered in the MME;

[TS 24.301, clause 6.5.1.2, UE requested PDN connectivity procedure initiation]
In order to request connectivity to the default PDN, the UE shall not include any APN in the PDN CONNECTIVITY
REQUEST message.

[TS 24.301, clause 9.9.3.33, Tracking area identity list]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1136 Release 9
1136
The Tracking area identity list is a type 4 information element, with a minimum length of 8 octets and a maximum
length of 98 octets. The list can contain a maximum of 16 different tracking area identities.

The value part of the Tracking area identity list information element consists of one or several partial tracking area
identity lists. The length of each partial tracking area identity list can be determined from the 'type of list' field and the
'number of elements' field in the first octet of the partial tracking area identity list.

Partial tracking area identity list:

Type of list (octet 1)
Bits
7 6
0 0 list of TACs belonging to one PLMN, with non-consecutive TAC values
0 1 list of TACs belonging to one PLMN, with consecutive TAC values
1 0 list of TAIs belonging to different PLMNs

For type of list ="001" and number of elements =k:

octet 2 to 4 contain the MCC+MNC, and
octet 5 and 6 contain the TAC of the first TAI belonging to the partial list.
The TAC values of the other k-1 TAIs are TAC+1, TAC+2, , TAC+k-1.

The MNC shall consist of 2 or 3 digits.

[TS 36.304, clause 4.3]

suitable cell:

9.2.1.1.1a.3 Test description
9.2.1.1.1a.3.1 Pre-test conditions
System Simulator:
NOTE: while this test describes the uses of 8 cells, it is intended that this test only requires 2 cells to be active at
any one instant.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1137 Release 9
1137
Table 9.2.1.1.1a-1: Cell TAI values
Cell MCC MNC TAC (hex) Remark Freq List of frequencies
in SIB5
Remark
A 001 01 0000 2 digit MNC f1 f2, f3 HPLMN
I 310 102 0000 3 digit MNC f3 f1, f2 See Note 1
B 001 01 0001 f1 f2, f3 HPLMN
C 001 01 0027 f1 f2, f3 HPLMN
G 004 07 fff0 f2 f1, f3 See Note 2
H 004 07 fff9 f2 f1, f3 See Note 2
K 316 002 0003 3 digit MNC f3 f1, f2 See Note 1
E 004 02 0003 f2 f1, f3 See Note 2
Note 1: Cell I and Cell K do not co-exist; the same frequency f3 is used.
Note 2: Cell E and Cells G and H do not co-exist; the same frequency f2 is used.

- System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;
- with the exception of the Physical Cell Identity and the list of frequences in SIB5, all other parameters for these
cells are the same as defined for cell 1 in TS 36.508 [18];
- the power level of cell A is the Serving Cell level defined in table 6.2.2.1-1 of TS 36.508 [18];
- the power levels of cells B to K are set to the Non-suitable Off level defined in table 6.2.2.1-1 of TS 36.508 [18].
Table 9.2.1.1.1a-2: Time instances of cell power level and parameter changes
Parameter Unit Cell A Cell I Cell B Cell C Cell G Cell H Cell K Cell E
T0
Cell-specific
RS EPRE
dBm/
15kHz
[-85] Off Off Off Off Off Off Off
T1
Cell-specific
RS EPRE
dBm/
15kHz
[-97] [-85] Off Off Off Off Off Off
T2
Cell-specific
RS EPRE
dBm/
15kHz
Off Off [-85] Off Off Off Off Off
T3
(N=3)
Cell-specific
RS EPRE
dBm/
15kHz
Off Off [-97] [-85] Off Off Off Off
T3
(N=4)
Cell-specific
RS EPRE
dBm/
15kHz
Off Off Off [-97] [-85] Off Off Off
T3
(N=5)
Cell-specific
RS EPRE
dBm/
15kHz
Off Off Off Off [-97] [-85] Off Off
T3
(N=6)
Cell-specific
RS EPRE
dBm/
15kHz
Off Off Off Off Off [-97] [-85] Off
T3
(N=7)
Cell-specific
RS EPRE
dBm/
15kHz
Off Off Off Off Off Off [-97] [-85]
T4
Cell-specific
RS EPRE
dBm/
15kHz
Off [-85] Off Off Off Off Off [-97]
T5
Cell-specific
RS EPRE
dBm/
15kHz
[-85] Off Off Off Off Off Off [-97]

UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1138 Release 9
1138
9.2.1.1.1a.3.2 Test procedure sequence
Table 9.2.1.1.1a.3.2-1: Main behaviour
U S Message
- - - -
message on cell A including a PDN
--> ATTACH REQUEST
authentication.
- - - -
options and/or APN.
7a2 The UE transmits the ESM INFORMATION
REQUEST message to transfer protocol
including a valid TAI list containing the TAIs of
Cell A and Cell I; with PLMN ID of Cell A
included in the GUTI; and with the PLMN ID of
Cell I included in the Equivalent PLMNs IE.
The ACTIVATE DEFAULT EPS BEARER
- - - -
EPS BEARER CONTEXT ACCEPT message.
10 Void - - - -
12 The signal strength of Cell I is raised to that of
the Serving Cell and that of Cell A is lowered
to that of a Suitable Neighbour Cell as defined
in table 6.2.2.1-1 of TS 36.508 [18].

Note: Cell A is still suitable but the UE shall
select Cell I

- - - -
13 Wait 70 seconds for mobile to camp on Cell I

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1139 Release 9
1139
- EXCEPTION: Step 15 describes behaviour
that depends on the UE capability.

15 If pc_SwitchOnOff or pc_USIM_Removal then
Check: does the UE send DETACH REQUEST
message?
--> DETACH REQUEST 3 P
16 Cells A and I are set to the Non-suitable Off
level and Cell B is set to the Serving Cell level.

Cell B unless explicitly stated otherwise.
- - - -
USIM is inserted.

18 Check: does the UE send an integrity
protected ATTACH REQUEST message
(including a PDN CONNECTIVITY REQUEST
message) with the last visited TAI correctly
indicating the TAI of cell I; the GUTI allocated
in step 8 and the KSI
ASME
allocated in step 3?
--> ATTACH REQUEST 1, 2 P
18
A
VOID - - - -
18
B
VOID - - - -
- - - -
18a
1
options and/or APN.
18a
2
The UE transmits the ESM INFORMATION
19 The SS sends an ATTACH ACCEPT message
allocating 16 TAIs and an aligned set of
equivalent PLMNs. The ACTIVATE DEFAULT
EPS BEARER CONTEXT REQUEST
message is piggybacked in ATTACH ACCEPT
message.
<-- ATTACH ACCEPT
- - - -
20 The UE sends ATTACH COMPLETE including
an ACTIVATE DEFAULT EPS BEARER
--> ATTACH COMPLETE
21 Void - -
23 The SS waits [5] seconds - - - -
- EXCEPTION steps 24 to 26 are repeated for N
=3 to N =7 with cells C,G,H,K,E according to
T3 in table 9.2.1.1.1a-2.

24 Cell power levels are set according to T3 and
the value of N.

25 Check: does the UE transmit a TRACKING
AREA UPDATE REQUEST message in the
next 70 seconds?
--> TRACKING AREA UPDATE
REQUEST
3 F
26 Using the procedure of clause 6.4.2.2 of TS
36.508 [18],
Check: does the UE camp on the strongest
3 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1140 Release 9
1140
cell ?
27 Cell K is is set to the Non-suitable Off level.
The signal strength of Cell E is lowered to that
of a Suitable Neighbour Cell and that of Cell I
is raised to the Serving Cell level.

Note: the new list of equivalent PLMNs
allocated in step 19 means that list of
equivalent PLMNs allocated in step 8 should
have been deleted. Hence the PLMN of Cell I
shall not be selected by a cell reselection
process, and the UE shall remain camped on
Cell E.

28 Check: Does the UE transmit a TRACKING
AREA UPDATE REQUEST message on cell I
in the next 70 seconds?
REQUEST
5 F
29 Using the procedure of clause 6.4.2.2 of TS
36.508 [18], page the UE on Cells E and I.

Check: Does the UE camp on cell E and not
on Cell I?
5 P
30 Cell I is set to the Non-suitable Off level. The
signal strength of Cell A is raised to the
Serving Cell level such that the UE shall select
Cell A.

AREA UPDATE REQUEST message on cell A
with the last visted TAI set to the TAI of cell E;
the GUTI allocated in step 8 and the KSI
ASME

REQUEST
4 P
32 SS responds with TRACKING AREA UPDATE
ACCEPT message
<-- TRACKING AREA UPDATE
ACCEPT
- -
33 The UE transmits a TRACKING AREA
UPDATE COMPLETE message
COMPLETE
- -

9.2.1.1.1a.3.3 Specific message contents
Table 9.2.1.1.1a.3.3-1: Message ATTACH ACCEPT (step 8, Table 9.2.1.1.1a.3.2-1)
TAI list List of 2 TAIs
Length of tracking area identity list contents 11 The value in the
length field

Number of elements 00001
Type of list 010 More than one
PLMN

Partial tracking area identity list First TAI =TAI of Cell I;
Second TAI =TAI of Cell
A

GUTI MCC=001, MNC=01,
MMEGI =1, MMEC=1,
M-TMSI arbitrarily
allocated but compliant to
rules of TS 23.003 sub
clause 2.8
Includes PLMN ID
of cell A

Equivalent PLMNs MCC=310, MNC=102 PLMN ID of cell I

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1141 Release 9
1141
Table 9.2.1.1.1a.3.3-2: Message ATTACH REQUEST (step 18, Table 9.2.1.1.1a.3.2-1)
Sent in SECURITY PROTECTED NAS MESSAGE
with valid integrity check

Old GUTI or IMSI GUTI allocated in step 8
NAS key set identifier KSI allocated in step 3
Last visited registered TAI TAI of cell 2

Table 9.2.1.1.1a.3.3-3: Message ATTACH ACCEPT (step 19, Table 9.2.1.1.1a.3.2-1)
TAI list Contains 3
separate partial
tracking area ID
lists

Length of tracking area identity list contents 32 The decimal value
of the value in the
length field

Type of first partial tracking area identity list 010 More than one
PLMN

Number of elements 00010 3 elements
First TAI MCC =004,
MNC =02,
TAC =0003

Second TAI MCC =005,
MNC =002,
TAC =0003

Third TAI MCC =316,
MNC =002,
TAC =0003

Type of second partial tracking area identity list 001 Consecutive
TACs on same
PLMN

Number of consecutive TACS 01001 10 elements
TAI MCC =004
MNC =07
TAC =fff0
TAI with lowest
numbered TAC

Type of third partial tracking area identity list 000 Individual TACs
on same PLMN

Number of elements 00010 3
MCC MCC =001
MNC MNC =01
First TAC TAC =0001
Second TAC TAC =0002
Third TAC TAC =0027
GUTI MCC=001, MNC =01,
MMEGI =64000,
MMEC=127, M-TMSI
arbitrarily allocated but
compliant to rules of
TS 23.003 sub clause 2.8
Includes PLMN ID
of cell B.

Equivalent PLMNs MCC=004, MNC=02;
MCC=004, MNC=03;
MCC=004, MNC=07;
MCC=316, MNC=002;
4 equivalent
PLMNs

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1142 Release 9
1142
Table 9.2.1.1.1a.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 37, Table 9.2.1.1.1a.3.2-1)
Old GUTI GUTI allocated in step 19
NAS key set identifier
ASME
Same as allocated in
step 3

Last visited registered TAI TAI of cell 8

9.2.1.1.2 Attach Procedure / Success / With IMSI / GUTI reallocation
(1)
with { UE in EMM-DEREGISTERED state }
ensure that {
when { there is no valid GUTI available in UE }
then { UE sends ATTACH REQUEST message, containing IMSI as the EPS mobile identity }
}
(2)
with { UE having received reallocated GUTI in the ATTACH ACCEPT message }
ensure that {
when { UE detaches from the EPS services }
then { UE sends DETACH REQUEST message, containing GUTI as the EPS mobile identity }
}
[TS 24.301, clause 5.5.1.2.2]
the MME, starting timer T3410 and entering state EMM-REGISTERED-INITIATED (see example in figure
5.5.1.2.2.1). If timer T3402 is currently running, the UE shall stop timer T3402. If timer T3411 is currently running, the
UE shall stop timer T3411.
message.
[TS 24.301, clause 5.5.1.2.4]
If the attach request is accepted by the network, the MME shall send an ATTACH ACCEPT message to the UE and
start timer T3450. The MME shall send the ATTACH ACCEPT message together with anACTIVATE DEFAULT EPS
BEARER CONTEXT REQUEST message contained in the ESM message container information element to activate the
default bearer (see subclause 6.4.1). The network may also initiate the activation of dedicated bearers towards the UE
by invoking the dedicated EPS bearer context activation procedure (see subclause 6.4.2).

Upon receiving the ATTACH ACCEPT message, the UE shall stop timer T3410.
The GUTI reallocation may be part of the attach procedure. When the ATTACH REQUEST message includes the IMSI,
the MME considers the GUTI provided by the UE is invalid, or the GUTI provided by the UE was assigned by another
MME, the MME shall allocate a new GUTI to the UE. The MME shall include in the ATTACH ACCEPT message the
new assigned GUTI together with the assigned TAI list. In this case the MME shall enter state EMM-COMMON-
PROCEDURE-INITIATED as described in subclause 5.4.1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1143 Release 9
1143
For a shared network, the TAIs included in the TAI list can contain different PLMN identities. The MME indicates the
selected core network operator PLMN identity to the UE in the GUTI (see 3GPP TS 23.251).If the ATTACH ACCEPT
message contains a GUTI, the UE shall use this GUTI as the new temporary identity. The UE shall delete its old GUTI
and store the new assigned GUTI. If no GUTI has been included by the MME in the ATTACH ACCEPT message, the
old GUTI, if any available, shall be kept.
If A/Gb mode or Iu mode is supported in the UE, the UE shall set its TIN to "GUTI" when receiving the ATTACH
ACCEPT message.
System Simulator:
- cell A (HPLMN).
UE:
- the UE is configured to initiate EPS attach.
Preamble:
- the UE is in state Registered, Idle Mode (State 2) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1144 Release 9
1144
U - S Message
1 The SS transmits Paging on cell A with IMSI.
Upon reception of paging with IMSI the UE
shall locally deactivate any EPS bearer
context(s), locally detach from EPS and delete
the GUTI-1. After local detach the UE shall
perform an EPS attach procedure.
- - - -
REQUEST message including IMSI in the EPS
mobile identity IE including a PDN
CONNECTIVITY REQUEST message?
authentication.
- - - -
6A
a1
options and/or APN.
6A
a2
with a new GUTI-2 included in the EPS mobile
identity IE. The ACTIVATE DEFAULT EPS
piggybacked in ATTACH ACCEPT message.
9 Cause UE to detach from the EPS services - - - -
10 Check: Does the UE transmit a DETACH
REQUEST message including GUTI-2 in the
EPS mobile identity IE?
11 SS responds with DETACH ACCEPT message <-- DETACH ACCEPT - -

Table 9.2.1.1.2.3.3-1: ATTACH REQUEST (step 2, Table 9.2.1.1.2.3.2-1)
Last visited registered TAI Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1145 Release 9
1145
Table 9.2.1.1.2.3.3-2: DETACH REQUEST (step 10, Table 9.2.1.1.2.3.2-1)
GUTI or IMSI GUTI-2

9.2.1.1.3 Attach Procedure / Success / Request for obtaining the IPv6 address of the home
agent
(1)
with { UE is configured to request the IPv6 address of the Home Agent during Attach procedure }
ensure that {
when { UE is switched on and has established the RRC connection }
then { UE transmits an ATTACH REQUEST message and a PDN CONNECTIVITY REQUEST message indicating
a request for DSMIPv6 Home Agent Address in the protocol configuration options }
}

(2)
with { UE and is configured to request the IPv6 address of the Home Agent during Attach procedure,
and has indicated in the PDN CONNECTIVITY REQUEST a request for DSMIPv6 Home Agent Address }
ensure that {
when { the SS responds to the ATTACH REQUEST with an IPv6 Home Agent address }
then { the UE transmits an ATTACH COMPLETE message }
}

6.5.1.2, and TS 24.008, clause 10.5.6.3.
[24.301 clause 5.5.1.1]
During the attach procedure, the UE may also obtain the home agent IPv4 and IPv6 addresses.
[24.301 clause 6.5.1.2]
If the UE supports DSMIPv6, the UE may include a request for obtaining the IPv6 address and optionally the IPv4
address of the home agent in the Protocol configuration options IE in the PDN CONNECTIVITY REQUEST message.
The UE may also include a request for obtaining the IPv6 Home Network Prefix. The UE shall request the IPv6 Home
Network Prefix only if the UE has requested the home agent IPv6 address. The requested home agent address(es) and
the Home Network Prefix are related to the APN the UE requested connectivity for.
[24.008 clause 10.5.6.3]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1146 Release 9
1146
Table 10.5.154/3GPP TS 24.008: Protocol configuration options information element
Additional parameters list (octets w+1 to z)
The additional parameters list is included when special parameters and/or requests
(associated with a PDP context) need to be transferred between the MS and the
network. These parameters and/or requests are not related to a specific
configuration protocol (e.g. PPP), and therefore are not encoded as the "Packets"
contained in the configuration protocol options list.
The additional parameters list contains a list of special parameters, each one in a
separate container. The type of the parameter carried in a container is identified by
a specific container identifier. In this version of the protocol, the following container
identifiers are specified:
MS to network direction:
- 0001H (P-CSCF Address Request);
- 0002H (IM CN Subsystem Signaling Flag);
- 0003H (DNS Server Address Request);
- 0004H (Not Supported);
- 0005H (MS Support of Network Requested Bearer Control indicator);
- 0006H (Reserved);
- 0007H (DSMIPv6 Home Agent Address Request;
- 0008H (DSMIPv6 Home Network Prefix Request);
- 0009H (DSMIPv6 IPv4 Home Agent Address Request);
- 000AH (IP address allocation via NAS signalling); and
- 000BH (IPv4 address allocation via DHCPv4).
Network to MS direction:
- 0001H (P-CSCF Address);
- 0003H (DNS Server Address);
- 0004H (Policy Control rejection code);
- 0005H (Selected Bearer Control Mode;
- 0006H (Reserved);
- 0007H (DSMIPv6 Home Agent Address) ;
- 0008H (DSMIPv6 Home Network Prefix); and
- 0009H (DSMIPv6 IPv4 Home Agent Address).
If the additional parameters list contains a container identifier that is not supported
by the receiving entity the corresponding unit shall be discarded.
The container identifier field is encoded as the protocol identifier field and the length
of container identifier contents field is encoded as the length of the protocol identifier
contents field.
When the container identifier indicates P-CSCF Address Request or DNS Server
Address Request, the container identifier contents field is empty and the length of
container identifier contents indicates a length equal to zero. If the container
identifier contents field is not empty, it shall be ignored.
When the container identifier indicates IM CN Subsystem Signaling Flag (see 3GPP

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1147 Release 9
1147
TS 24.229 [95]), the container identifier contents field is empty and the length of
identifier contents field is not empty, it shall be ignored. In Network to MS direction
this information may be used by the MS to indicate to the user whether the
requested dedicated signalling PDP context was successfully established.
When the container identifier indicates P-CSCF Address, the container identifier
contents field contains one IPv6 address corresponding to a P-CSCF address (see
3GPP TS 24.229 [95]). This IPv6 address is encoded as an 128-bit address
according to RFC 3513 [99]. When there is need to include more than one P-CSCF
address, then more logical units with container identifier indicating P-CSCF Address
are used.
When the container identifier indicates DNS Server Address, the container identifier
contents field contains one IPv6 DNS server address (see 3GPP TS 27.060 [36a]).
This IPv6 address is encoded as an 128-bit address according to RFC 3513 [99].
When there is need to include more than one DNS server address, then more
logical units with container identifier indicating DNS Server Address are used.
When the container identifier indicates Policy Control rejection code, the container
identifier contents field contains a Go interface related cause code from the GGSN
to the UE (see 3GPP TS 29.207 [100]). The length of container identifier contents
indicates a length equal to one. If the container identifier contents field is empty or
its actual length is greater than one octect, then it shall be ignored by the receiver.
When the container identifier indicates MS Support of Network Requested Bearer
Control indicator, the container identifier contents field is empty and the length of
When the container identifier indicates Selected Bearer Control Mode, the container
identifier contents field contains the selected bearer control mode, where 01H
indicates that MS only mode has been selected and 02H indicates that MS/NW
mode has been selected. The length of container identifier contents indicates a
length equal to one. If the container identifier contents field is empty or its actual
length is greater than one octect, then it shall be ignored by the receiver.
When the container identifier indicates DSMIPv6 Home Agent Address Request, the
container identifier contents field is empty and the length of container identifier
contents indicates a length equal to zero. If the container identifier contents field is
not empty, it shall be ignored.
When the container identifier indicates DSMIPv6 Home Network Prefix Request, the
When the container identifier indicates DSMIPv6 IPv4 Home Agent Address
Request, the container identifier contents field is empty and the length of container
identifier contents indicates a length equal to zero. If the container identifier contents
field is not empty, it shall be ignored.
When the container identifier indicates DSMIPv6 Home Agent Address, the
container identifier contents field contains one IPv6 address corresponding to a
DSMIPv6 HA address (see 3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]).
This IPv6 address is encoded as an 128-bit address according to
IETF RFC 3513 [99].
When the container identifier indicates DSMIPv6 Home Network Prefix, the
container identifier contents field contains one IPv6 Home Network Prefix (see
3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]). This IPv6 prefix is encoded as
an IPv6 address according to RFC 3513 [99] followed by 8 bits which specifies the
prefix length.
When the container identifier indicates DSMIPv6 IPv4 Home Agent Address, the
DSMIPv6 IPv4 Home Agent address (see 3GPP TS 24.303 [124] and
3GPP TS 24.327 [125]).
When the container identifier indicates IP address allocation via NAS signalling, the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1148 Release 9
1148
When the container identifier indicates IP address allocation DHCPv4, the container
identifier contents field is empty and the length of container identifier contents
indicates a length equal to zero. If the container identifier contents field is not empty,
it shall be ignored.
NOTE 1: The additional parameters list and the configuration protocol options list
are logically separated since they carry different type of information. The
beginning of the additional parameters list is marked by a logical unit,
which has an identifier (i.e. the first two octets) equal to a container
identifier (i.e. it is not a protocol identifier).

System Simulator:
- cell A.
UE:
registered on cell A using default message contents according to [18];
- the UE is configured to request the IPv6 address of the Home Agent in the protocol configuration options IE as
part of the Attach / PDN connectivity request procedure.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1149 Release 9
1149
U - S Message
CONNECTIVITY REQUEST message with IE
PROTOCOL CONFIGURATION OPTIONS
indicating a DSMIPv6 Home Agent Address
Request?
3-
11
TS 36.508 Table 4.5.2.3-1 (Attach procedure)
are performed on Cell A,

- - - -
ATTACH ACCEPT message, including the IE
indicating a DSMIPv6 Home Agent Address.
- - - -
message?

Derivation path: TS 36.508 table 4.7.2.-4
REQUEST message as
specified in table
9.2.1.1.3.3.3-2.

Table 9.2.1.1.3.3.3-2: PDN CONNECTIVITY REQUEST (step 2, Table 9.2.1.1.3.3.2-1)
Protocol configuration options The IE Protocol
configuration options
contains a configuration
protocol option =0007H
(DSMIPv6 Home Agent
Address Request, length
of contents =0).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1150 Release 9
1150
DEFAULT EPS BEARER
CONTEXT REQUEST
table 9.2.1.1.3.3.3-4.

Table 9.2.1.1.3.3.3-4: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 12,
Table 9.2.1.1.3.3.2-1)
(DSMIPv6 Home Agent
Address, non-zero
length), with the value set
to the IPv6 address of
the Home Agent.

9.2.1.1.4 Attach Procedure / Success / Request for obtaining the IPv4 address of the home
agent
(1)
with { UE and is configured to request the DSMIPv6 IPv4 Home Agent Address }
ensure that {
when { UE is switched on and has established the RRC connection }
then { the UE transmits a ATTACH REQUEST and a PDN CONNECTIVITY REQUEST message indicating a
request for DSMIPv6 IPv4 Home Agent Address in the protocol configuration options }
}

(2)
with { UE and is configured to request the DSMIPv6 IPv4 Home Agent Address, and has indicated in the
PDN CONNECTIVITY REQUEST a request for DSMIPv6 IPv4 Home Agent Address }
ensure that {
when { the SS responds to the ATTACH REQUEST with a DSMIPv6 IPv4 Home Agent Address }
then { the UE transmits an ATTACH COMPLETE message }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses 5.5.1.1, and
6.5.1.2, and TS 24.008, clause 10.5.6.3.
[24.301 clause 5.5.1.1]
During the attach procedure, the UE may also obtain the home agent IPv4 and IPv6 addresses.
[24.301 clause 6.5.1.2]
If the UE supports DSMIPv6, the UE may include a request for obtaining the IPv6 address and optionally the IPv4
address of the home agent in the Protocol configuration options IE in the PDN CONNECTIVITY REQUEST message.
The UE may also include a request for obtaining the IPv6 Home Network Prefix. The UE shall request the IPv6 Home
Network Prefix only if the UE has requested the home agent IPv6 address. The requested home agent address(es) and
the Home Network Prefix are related to the APN the UE requested connectivity for.
[24.008 clause 10.5.6.3]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1151 Release 9
1151
Table 10.5.154/3GPP TS 24.008: Protocol configuration options information element
Additional parameters list (octets w+1 to z)
The additional parameters list is included when special parameters and/or requests
(associated with a PDP context) need to be transferred between the MS and the
network. These parameters and/or requests are not related to a specific
configuration protocol (e.g. PPP), and therefore are not encoded as the "Packets"
contained in the configuration protocol options list.
The additional parameters list contains a list of special parameters, each one in a
separate container. The type of the parameter carried in a container is identified by
a specific container identifier. In this version of the protocol, the following container
identifiers are specified:
MS to network direction:
- 0001H (P-CSCF Address Request);
- 0003H (DNS Server Address Request);
- 0004H (Not Supported);
- 0005H (MS Support of Network Requested Bearer Control indicator);
- 0006H (Reserved);
- 0007H (DSMIPv6 Home Agent Address Request;
- 0008H (DSMIPv6 Home Network Prefix Request);
- 0009H (DSMIPv6 IPv4 Home Agent Address Request);
- 000AH (IP address allocation via NAS signalling); and
- 000BH (IPv4 address allocation via DHCPv4).
Network to MS direction:
- 0001H (P-CSCF Address);
- 0003H (DNS Server Address);
- 0004H (Policy Control rejection code);
- 0005H (Selected Bearer Control Mode;
- 0006H (Reserved);
- 0007H (DSMIPv6 Home Agent Address) ;
- 0008H (DSMIPv6 Home Network Prefix); and
- 0009H (DSMIPv6 IPv4 Home Agent Address).
If the additional parameters list contains a container identifier that is not supported
by the receiving entity the corresponding unit shall be discarded.
The container identifier field is encoded as the protocol identifier field and the length
of container identifier contents field is encoded as the length of the protocol identifier
contents field.
When the container identifier indicates P-CSCF Address Request or DNS Server
Address Request, the container identifier contents field is empty and the length of
When the container identifier indicates IM CN Subsystem Signaling Flag (see 3GPP

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1152 Release 9
1152
TS 24.229 [95]), the container identifier contents field is empty and the length of
identifier contents field is not empty, it shall be ignored. In Network to MS direction
this information may be used by the MS to indicate to the user whether the
requested dedicated signalling PDP context was successfully established.
When the container identifier indicates P-CSCF Address, the container identifier
contents field contains one IPv6 address corresponding to a P-CSCF address (see
3GPP TS 24.229 [95]). This IPv6 address is encoded as an 128-bit address
according to RFC 3513 [99]. When there is need to include more than one P-CSCF
address, then more logical units with container identifier indicating P-CSCF Address
are used.
When the container identifier indicates DNS Server Address, the container identifier
contents field contains one IPv6 DNS server address (see 3GPP TS 27.060 [36a]).
This IPv6 address is encoded as an 128-bit address according to RFC 3513 [99].
When there is need to include more than one DNS server address, then more
logical units with container identifier indicating DNS Server Address are used.
When the container identifier indicates Policy Control rejection code, the container
identifier contents field contains a Go interface related cause code from the GGSN
to the UE (see 3GPP TS 29.207 [100]). The length of container identifier contents
indicates a length equal to one. If the container identifier contents field is empty or
its actual length is greater than one octect, then it shall be ignored by the receiver.
When the container identifier indicates MS Support of Network Requested Bearer
Control indicator, the container identifier contents field is empty and the length of
When the container identifier indicates Selected Bearer Control Mode, the container
identifier contents field contains the selected bearer control mode, where 01H
indicates that MS only mode has been selected and 02H indicates that MS/NW
mode has been selected. The length of container identifier contents indicates a
length equal to one. If the container identifier contents field is empty or its actual
length is greater than one octect, then it shall be ignored by the receiver.
When the container identifier indicates DSMIPv6 Home Agent Address Request, the
When the container identifier indicates DSMIPv6 Home Network Prefix Request, the
When the container identifier indicates DSMIPv6 IPv4 Home Agent Address
Request, the container identifier contents field is empty and the length of container
identifier contents indicates a length equal to zero. If the container identifier contents
field is not empty, it shall be ignored.
When the container identifier indicates DSMIPv6 Home Agent Address, the
DSMIPv6 HA address (see 3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]).
This IPv6 address is encoded as an 128-bit address according to
IETF RFC 3513 [99].
When the container identifier indicates DSMIPv6 Home Network Prefix, the
container identifier contents field contains one IPv6 Home Network Prefix (see
3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]). This IPv6 prefix is encoded as
an IPv6 address according to RFC 3513 [99] followed by 8 bits which specifies the
prefix length.
When the container identifier indicates DSMIPv6 IPv4 Home Agent Address, the
DSMIPv6 IPv4 Home Agent address (see 3GPP TS 24.303 [124] and
3GPP TS 24.327 [125]).
When the container identifier indicates IP address allocation via NAS signalling, the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1153 Release 9
1153
When the container identifier indicates IP address allocation DHCPv4, the container
identifier contents field is empty and the length of container identifier contents
indicates a length equal to zero. If the container identifier contents field is not empty,
it shall be ignored.
NOTE 1: The additional parameters list and the configuration protocol options list
are logically separated since they carry different type of information. The beginning
of the additional parameters list is marked by a logical unit, which has an identifier
(i.e. the first two octets) equal to a container identifier (i.e. it is not a protocol
identifier).

System Simulator:
- cell A.
UE:
registered on cell A using default message contents according to TS 36.508 [18];
- the UE is configured to request the DSMIPv6 IPv4 Home Agent Address in the protocol configuration options
IE as part of the Attach / PDN connectivity request procedure.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1154 Release 9
1154
U - S Message
RRCConnectionRequest message not
including S-TMSI and with
establishmentCause set to mo-Signalling?
- - - -
3 The SS transmits a RRCConnectionSetup
message.
- - - -
including a PDN CONNECTIVITY REQUEST
message with IE PROTOCOL
CONFIGURATION OPTIONS indicating a
DSMIPv6 IPv4 Home Agent Address Request?
5-
13
TS 36.508 Table 4.5.2.3-1 (Attach procedure)
are performed on Cell A,

- - - -
ATTACH ACCEPT message, including the IE
indicating a DSMIPv6 IPv4 Home Agent
Address
- - - -
message?

randomValue Not checked
}
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1155 Release 9
1155
REQUEST message as
specified in table
9.2.1.1.4.3.3-3.

Table 9.2.1.1.4.3.3-3: PDN CONNECTIVITY REQUEST (step 4, Table 9.2.1.1.4.3.2-1)
(DSMIPv6 IPv4 Home
Agent Address Request,
lenght of contents =0).

DEFAULT EPS BEARER
CONTEXT REQUEST
table 9.2.1.1.4.3.3-5.

Table 9.2.1.1.4.3.3-5: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 11,
Table 9.2.1.1.4.3.2-1)
(DSMIPv6 IPv4 Home
Agent Address, non-
zero length), with the
value set to TBD.

9.2.1.1.5 Void
9.2.1.1.6 Void
9.2.1.1.7 Attach Procedure / Success / List of equivalent PLMNs in the ATTACH ACCEPT
message
(1)
with { UE in EMM-REGISTERED-INITIATED state }
ensure that {
when { the UE receives ATTACH ACCEPT message including a list of equivalent PLMNs }
then { the UE stores correctly the list and does not consider forbidden PLMNs as equivalent
PLMNs }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1156 Release 9
1156

(2)
ensure that {
when { the UE receives ATTACH ACCEPT message without a list of equivalent PLMNs }
then { the UE deletes the stored list and applies a normal PLMN selection process }
}

[TS 24.301, clause 5.5.1.2.4]
The MME may also include a list of equivalent PLMNs in the ATTACH ACCEPT message. Each entry in the list
contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, after having removed
from the list any PLMN code that is already in the list of forbidden PLMNs. In addition, the UE shall add to the stored
list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the
ATTACH ACCEPT message. If the ATTACH ACCEPT message does not contain a list, then the UE shall delete the
stored list.
System Simulator:
- Cell A (PLMN1, HPLMN), cell G (PLMN2, visited PLMN), cell I (PLMN3, another visited PLMN) and cell J
(PLMN4, another visited PLMN, different than cell I and switched OFF) are configured according to table
6.3.2.2-1 in TS 36.508 [18];
- at most 3 cells are active simultaneously.
UE:
- the UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE last attempted to register on cell
I and received reject cause "forbidden PLMN".
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1157 Release 9
1157
Table: 9.2.1.1.7.3.2-1: Main behaviour
U - S Message
- Cell G as a "Non-Suitable cell".
- Cell I as a "Non-Suitable cell".
- - - -
- - - -
REQUEST message.
authentication.
- - - -
7A
a1
options and/or APN.
7A
a2
including PLMN2, PLMN3 and PLMN4 in the
list of equivalent PLMNs. The ACTIVATE
ATTACH ACCEPT message.
--> ATTACH COMPLETE
- -

10a If pc_SwitchOnOff or pc_USIM_Removal then
UE sends DETACH REQUEST message
--> DETACH REQUEST
- Cell A as the "Non-Suitable cell".
- Cell G as a "Suitable cell".
- Cell I as a "Serving cell".

Note: Cell I belongs to the forbidden PLMN.
- - - -
Cell G unless explicitly stated otherwise.
- - - -
USIM is inserted.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1158 Release 9
1158
9.2.1.1.7.3.2-2 occurs in parallel with step 13.

13
A
Void - - - -
13
B
Void - - - -
- - - -
13
Aa
1
options and/or APN.
13
A
a2
- - - -
message without the Equivalent PLMNs list.
The ACTIVATE DEFAULT EPS BEARER
message on Cell G (PLMN2) including an
15
A
The SS configures:
- Cell A as a "Suitable cell".
- Cell I as a "Non-suitable "Off cell".
- Cell J as a "Serving cell".
- - - -
- - - -
9.2.1.1.7.3.2-3 occurs in parallel with step 15B.

15
B
Check: Does the UE transmit a TRACKING
AREA UPDATE REQUEST message?
REQUEST
2 P
15
C
SS responds with TRACKING AREA UPDATE
ACCEPT message.
ACCEPT
- -
15
D
The UE transmits a TRACKING AREA
COMPLETE

16-
34
Void - - - -

Table: 9.2.1.1.7.3.2-2: Parallel behaviour
U - S Message
REQUEST message on Cell I (PLMN3) ?

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1159 Release 9
1159
Table: 9.2.1.1.7.3.2-3: Parallel behaviour
U - S Message
AREA UPDATE REQUEST message on Cell J
(PLMN4)?
REQUEST
2 F
,
Equivalent PLMNs - Includes MCC and
MNC digits for
PLMN2, PLMN3
and PLMN4.

Equivalent PLMNs Not present

9.2.1.1.8 Void
9.2.1.1.9 Attach / Rejected / IMSI invalid
(1)
with { UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message }
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "Illegal UE" }
then { UE considers the USIM as invalid for EPS services and non-EPS services and enters state
EMM-DEREGISTERED }
}
(2)
with { UE receives an ATTACH REJECT message with the reject cause set to "Illegal UE" }
ensure that {
when { the UE has been switched off, then switched on }
then { the UE sends an ATTACH REQUEST message with IMSI, including a PDN CONNECTIVITY REQUEST
message }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.1.2.5.
[TS 24.301, clause 5.5.1.2.5]
...
Upon receiving the ATTACH REJ ECT message, the UE shall stop timer T3410 and take the following actions
depending on the reject cause value received.
#3 (Illegal UE); or
...
The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI. The UE shall consider the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1160 Release 9
1160
USIM as invalid for EPS services and non-EPS services until switching off or the UICC containing the USIM is
removed. Additionally, the UE shall delete the list of equivalent PLMNs and enter state EMM-
DEREGISTERED.
If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update
status, TMSI, LAI and ciphering key sequence number, and the GMM parameters GMM state, GPRS update
status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in
3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM cause with the
same value.
NOTE: The possibility to configure a UE so that the radio transceiver for a specific RAT is not active, although it
is implemented in the UE, is out of scope of the present specification.
...
System Simulator:
- cell A, cell B and cell G:
- Cell A and Cell B (home PLMN, different TAs),
- Cell G (another PLMN);;
- the different cells may not be simultaneously activated (at most 2 cells are active simultaneously).
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1161 Release 9
1161
U - S Message
- cell A as the "Serving cell".
- cell B as a "Non-Suitable cell".
- Cell G as a "Non-Suitable Off cell".
- - - -
cell A unless explici;tly stated otherwise.
- - - -
REQUEST message on cell A.
4 The SS transmits an ATTACH REJ ECT
message with EMM cause ="Illegal UE" as
specified.
<-- ATTACH REJ ECT - -
- Cell A as a "Non-Suitable cell".
- Cell B as the "Serving cell".
- - - -
- - - -

Note: Cell B belongs to the same PLMN where
the UE was rejected but a different TA
8 The operator initiates an attach by MMI or by
AT command.
- - - -
10 Void - - - -
procedure (TS 36.508 subclause 6.4.2.5)
indicate that the UE ignores paging on cell B
for PS domain with GUTI-1?
- - 1 -
- Cell A as a Non-Suitable Off cell.
- Cell B as a "Non-Suitable cell".
- Cell G as the "Serving cell".
- - - -
- - - -

Note: Cell G belongs to a PLMN which is not
the same like the one on which the UE was
rejected.
14 The user initiates an attach by MMI or by AT
command.
- - - -
16 if possible (see ICS) switch off is performed or

USIM is inserted.

18 Void - - - -
REQUEST message with IMSI-1?
20-
31
- - - -
- At the end of this test procedure sequence, the - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1162 Release 9
1162

Table 9.2.1.1.9.3.3-1: Message ATTACH REJECT (steps 4 and 20, Table 9.2.1.1.9.3.2-1)
Security header type 0000 " Plain NAS
message, not
security protected
"

EMM cause 00000011 #3 "Illegal UE"
ESM message container Not present

Old GUTI or IMSI IMSI-1
REQUEST message to
request PDN connectivity
to the default PDN

Old LAI Not present
TMSI status Not present

9.2.1.1.10 Attach / Rejected / Illegal ME
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "Illegal ME" }
EMM-DEREGISTERED }
}
(2)
with { UE receives an ATTACH REJECT message with the reject cause set to "Illegal ME" }
ensure that {
message }
}

[TS 24.301, clause 5.5.1.2.5]
...
#6 (Illegal ME);

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1163 Release 9
1163
DEREGISTERED.
...
The test description is identical to the one of subclause 9.2.1.1.9 except that in the test procedure and in the specific
message contents, the reject cause #3 "Illegal UE" is replaced with the reject cause #6 "Illegal ME".
9.2.1.1.11 Attach / Rejected / EPS services and non-EPS services not allowed
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "EPS services and non-EPS
services not allowed" }
EMM-DEREGISTERED }
}
(2)
with { UE receives an ATTACH REJECT message with the reject cause set to "EPS services and non-EPS
ensure that {
message }
}
(3)
with { UE receives an ATTACH REJECT message with the reject cause set to "EPS services and non-EPS
ensure that {
when { the UE has been switched off, then switched on and a UMTS or GSM cell is found }
then { the UE sends an ATTACH REQUEST message with IMSI and TMSI status indicated invalid TMSI }
}

[TS 24.301, clause 5.5.1.2.5]
...
#8 (EPS services and non-EPS services not allowed);
DEREGISTERED.
3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM cause with the
same value.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1164 Release 9
1164
...
[TS 24.008, clause 4.7.3.2.4]
...
The MS shall then take one of the following actions depending upon the reject cause:
#8 (GPRS services and non-GPRS services not allowed);
...
The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (shall store it according to
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence
number. The new GMM state is GMM-DEREGISTERED. The new MM state is MM IDLE.
The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and
ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS
services until switching off or the SIM/USIM is removed.
The test description is identical to the one of subclause 9.2.1.1.9 with the following exceptions:
System Simulator:
- cell A, Cell B (home PLMN, different TAs) and Cell G TS 36.508 (another PLMN)
- If pc_UTRAN Cell 5 and if (NOT pc_UTRAN AND pc_GERAN) Cell 24 are configured according to Table
4.4.4-2 in [18];
- if pc_UTRAN, cell 5 (only active when stated);
- if pc_GERAN and NOT pc_UTRAN, cell 24 (only active when stated);
- system information combination 4 as defined in TS 36.508[18] clause 4.4.3.1 is applied in E-UTRA cells
except if NOT pc_UTRAN and pc_GERAN then system information combination 5 is applied;
- the different cells may not be simultaneously activated.
UE:
- if pc_UTRAN (respectively if pc_GERAN and NOT pc_UTRAN), the UE is previously registered on UTRAN
(respectively GERAN), and when on UTRAN (respectively GERAN), the UE is last registered on cell 5
(respectively cell 24) using default message contents according to TS 36.508 [18].
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1165 Release 9
1165
U - S Message

IF pc_GERAN or pc_UTRAN THEN the SS
configures Cell 24 (GERAN) or Cell 5
(UTRAN) as "Non-Suitable cell".
- - - -
- - - -
REQUEST message.
message with EMM cause ="EPS services
and non-EPS services not allowed" as
specified.
- - - -
- - - -

Note: Cell B belongs to the same PLMN where
the UE was rejected but a different TA
AT command.
- - - -
10 Void - - - -
procedure (TS 36.508 subclause 6.4.2.5)
indicate that the UE ignores paging on cell B
for PS domain with GUTI-1?
- - 1 -
- - - -
- - - -

rejected.
command.
- - - -

USIM is inserted.

18 The following message is sent on Cell G.
REQUEST message with IMSI-1?

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1166 Release 9
1166
message with EMM cause ="EPS services
and non-EPS services not allowed" as
specified.
- - - -
21a
1
IF pc_UTRAN or pc_GERAN THEN
the SS configures
- Cell 24 (GERAN) or Cell 5 (UTRAN) as the
"Serving cell".
- - - -
Cell 24 or Cell 5 (depending on which cell was
set as "Serving cell" in the preceding step)
unless explicitly stated otherwise.
- - - -
21a
2
Check: Does the UE transmit an ATTACH
21a
3
The user initiates an attach by MMI or by AT
command.
- - - -
21a
4
21a
5
If possible (see ICS) switch off is performed or
- - - -
21a
6
The UE is brought back to operation or the
USIM is inserted.
- - - -
21a
7
Void - - - -
21a
8
REQUEST message with IMSI-1and TMSI
status indicated invalid TMSI?
22-
33
- - - -
- - - -

message, not
security protected
"

EMM cause 00001000 #8 "EPS services
and non-EPS
services not
allowed"


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1167 Release 9
1167
REQUEST message to
request PDN connectivity
to the default PDN

Old LAI Not present

Table 9.2.1.1.11.3.3-3: Message ATTACH REQUEST (step 21a8, Table 9.2.1.1.11.3.2-1)
Derivation path: TS 24.008 table 9.4.1
MS network capability Not checked
Attach type Not checked
GPRS ciphering key sequence number 111 No key is
available

DRX parameter Not checked
P-TMSI or IMSI IMSI-1
Old routing area identification Deleted RAI-1 The MNC and the
MCC in the
coding of the RAI
are replaced by
the RAC of RAC-1

MS Radio Access capability Not checked
Old P-TMSI signature Not present
Requested READY timer
Value
Not checked
TMSI status 0 no valid TMSI
available

PS LCS Capability Not checked
Mobile station classmark 2 Not checked
Supported Codecs Not checked
UE network capability Not checked
Additional mobile identity Not present
Additional old routing area identification Not present

9.2.1.1.12 Attach / Rejected / EPS services not allowed
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "EPS services not
allowed" }
then { UE deletes the GUTI and the last visited registered TAI and KSI and considers the USIM as
invalid for EPS services until switching off or the UICC containing the USIM is removed and deletes
the list of equivalent PLMNs and UE enters state EMM-DEREGISTERED }
}
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.5.1.2.2 and
5.5.1.2.5.
[TS 24.301, clause 5.5.1.2.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1168 Release 9
1168
message.

[TS 24.301, clause 5.5.1.2.5]

#7 (EPS services not allowed);
USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed. Additionally,
the UE shall delete the list of equivalent PLMNs and enter state EMM-DEREGISTERED.
If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM
state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as
specified in 3GPP TS 24.008 [6] for the case when the normal attach procedure is rejected with the GMM cause
with the same value.
System Simulator:
- cell A, cell B and cell G:
- cell A and cell B (HPLMN, different TAs), cell G (another PLMN);
- if pc_UTRAN, cell 5 (HPLMN, UTRAN, NMO 2);
- if NOT pc_UTRAN and pc_GERAN, cell 24 (HPLMN, GERAN, NMO 2);
- system information combination 4 as defined in TS 36.508[18] clause 4.4.3.1 is applied in E-UTRA cells except
if NOT pc_UTRAN and pc_GERAN then system information combination 5 is applied;

- the different cells may not be simultaneously activated (at most 2 cells are active simultaneously);
- cells B and G can be implemented as minimum uplink cells.
UE:
- if pc_GERAN or pc_UTRAN (respectively if pc_GERAN and NOT pc_UTRAN)supported by UE, the UE is
previously registered on UTRAN (respectively GERAN), and when on UTRAN (respectively GERAN), the UE
is last registered on cell 5 (respectively cell 24) using default message contents according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1169 Release 9
1169
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1170 Release 9
1170
U - S Message
- Cell B as a " Suitable neighbour cell".
- Cell G as a "Non-Suitable Off cell".
- If present, Cell 5 or 24 as a "Non-Suitable Off
cell".
- - - -
- - - -
2 The user switches the UE on. - - - -
REQUEST message.
message with EMM cause ="EPS services not
allowed".
6 The SS reconfigures:
Cell A as a " Suitable neighbour cell".
Cell B as the "Serving cell".

Note: Cell A and Cell B are in different TAIs
same PLMN.
- - - -
- - - -
command.
- - - -
- - - -
10a
1
IF pc_UTRAN or pc_GERAN THEN
the SS configures
- Cell A as "Non-suitable Off cell"
- Cell B as a " Suitable neighbour cell".
- Cell 24 (GERAN) or 5 (UTRAN) as the
"Serving cell".

Note: Cell B and Cell 24 (GERAN) or 5
(UTRAN) are in different PLMNs
- - - -
10a
2
The following messages are to be observed on
Cell 24 or Cell 5 (depending on which cell was
set as "Serving cell" in the preceding step)
unless explicitly stated otherwise.
- - - -
9.2.1.1.12.3.2-2 occurs in parallel with step
10a3.

10a
3
REQUEST message in the next 2 minutes?
10a
4
The user initiates an attach by MMI or by AT
command.
- - - -
10a
5
Check : Does the UE transmit an ATTACH
10a
6
The SS configures cell 24 or cell 5 as "Suitable
Neighbour cell".
- - - -
- Cell B as a "Non-Suitable Off cell".

Note: Cell B and Cell G are different PLMNs.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1171 Release 9
1171
- - - -
AT command.
- - - -
UE is in end state E-UTRA deregistered (E4)
- - - -

Table 9.2.1.1.12.3.2-2: Parallel behaviour
U - S Message
- EXCEPTION: Steps 1a and 1b describe a
behaviour which depends on the UE capability.
- - - -
1a IF pc_CS THEN the UE transmits a
LOCATION UPDATING REQUEST message.
--> LOCATION UPDATING
REQUEST
- -
1b The SS transmits a LOCATION UPDATING
ACCEPT message including IMSI-1
<-- LOCATION UPDATING ACCEPT - -

Table 9.2.1.1.12.3.3-1: Message ATTACH REJECT (step 4, Table 9.2.1.1.12.3.2-1)
Derivation path: 36.508 table 4.7.2-3 (This message is transmitted as a "plain NAS message")
Security header type 0000 "Plain NAS
message, not
security
protected"

EMM cause 00000111 #7 "EPS services
not allowed"


9.2.1.1.13 Attach / Rejected / PLMN not allowed
(1)
with { the UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message }
ensure that {
when { the UE receives an ATTACH REJECT message with the reject cause set to "PLMN not allowed" }
then { the UE deletes the GUTI, the last visited registered TAI, KSI, the list of equivalent
PLMNs and UE enters state EMM-DEREGISTERED.PLMN-SEARCH and UE stores the PLMN in the "forbidden PLMN
list" in the USIM }
}
(2)
with { the UE is switched off and a PLMN is stored in the "forbidden PLMN list" in the USIM }
ensure that {
when { the UE is switched on }
then { the UE doesn't attempt to attach on this PLMN }
}
(3)
with { the UE in E-UTRA EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden
PLMN list" }
ensure that {
when { the UE detects a cell belonging to a PLMN which is not in the "forbidden PLMN list" }
then { the UE attaches to this PLMN }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1172 Release 9
1172
(4)
with {the UE in E-UTRA EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden
PLMN list" }
ensure that {
when { the forbidden PLMN is selected manually }
then { the UE attaches to the forbidden PLMN and deletes this PLMN from the USIM}
}
5.5.1.2.5.
[TS 24.301, clause 5.5.1.2.2]
5.5.1.2.2.1). If timer T3402 is currently running, the UE shall stop timer T3402. If timer T3411 is currently running, the
UE shall stop timer T3411.

message.
If the UE supports A/Gb mode or Iu mode, the UE shall handle the Old GUTI or IMSI IE as follows:
...
- If the TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI, the UE shall indicate the
GUTI in the Old GUTI or IMSI IE.
...
- Otherwise the UE shall include the IMSI in the Old GUTI or IMSI IE.
...
[TS 24.301, clause 5.5.1.2.5]
If the attach request cannot be accepted by the network, the MME shall send an ATTACH REJ ECT message to the UE
including an appropriate EMM cause value.
...
depending on the EMM cause value received.
...
#11 (PLMN not allowed);
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI. Additionally, the UE shall
delete the list of equivalent PLMNs and reset the attach attempt counter, and enter state EMM-
DEREGISTERED.PLMN-SEARCH.
In S1 mode, the UE shall store the PLMN identity in the "forbidden PLMN list" and enter state EMM-
DEREGISTERED.PLMN-SEARCH. The UE shall perform a PLMN selection according to 3GPP TS 23.122 [6].
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1173 Release 9
1173
status, TMSI, LAI, ciphering key sequence number and location update attempt counter, and the GMM
parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence
number and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal
attach procedure is rejected with the GMM cause with the same value and no RR connection exists.
System Simulator:
- cell G, cell H (VPLMN, same MCC like HPLMN, different TAs) and cell I (VPLMN, different MCC from
HPLMN);
- the cells may not be simultaneously activated.
UE:
registered on cell G using default message contents according to TS 36.508 [18];
- the "forbidden PLMN list" is empty;
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1174 Release 9
1174
U - S Message
- Cell H as a " Suitable Neighbour cell".
- Cell I as a "Non-Suitable Off cell".

Note: Cell G and Cell H are in the different TAI
same PLMN.
- - - -
- - - -
REQUEST message.
message including EMM cause ="PLMN not
allowed".
REQUEST message on cell G or H in the next
30 seconds?
- - - -
USIM is inserted.
- - - -
- Cell G as the "Serving cell"
- Cell H as a "Non-Suitable Off cell"
- Cell I as a " Suitable neigbour cell".

- - - -
11 The following messages are to be observed on
- - - -
CONNECTIVITY REQUEST message as
specified?
12
A-
12
M
The attach procedure is completed and the
RRC connection is released by executing
steps 5 to 17 of the UE registration procedure
in TS 36.508 clause 4.5.2.3.
- - -
13 -
19
Void - - - -
- - - -

the UE transmits a DETACH REQUEST
message.
--> DETACH REQUEST - -
- Cell G as the "Serving cell"
- Cell I as a "Non-suitable Off cell".

Note: Cell G belongs to the forbidden PLMN.
- - - -
USIM is inserted.
- - - -
24 The following messages are to be observed on
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1175 Release 9
1175
25 The user sets the UE in manual PLMN
selection mode or requests a PLMN search.
- - - -
26 The user selects PLMN of cell G. - - - -
specified?
28-
40
RRC connection is released by executing
steps 5 to 17 of the UE registration procedure
in TS 36.508 clause 4.5.2.3.
- - - -
to TS 36.508.
- - - -

Derivation path: 36.508 table 4.7.2-3 (Plain NAS message)
Security header type 0000 "No security
protection"

EMM cause 00001011 #11 "PLMN not
allowed"


Old GUTI or IMSI IMSI-1 GUTI has been
deleted after
receiving
ATTACH REJ ECT
at step 5; only
IMSI is available.

Last visited registered TAI Not present TAI has been
deleted after
receiving
ATTACH REJ ECT
at step 5.

Old GUTI or IMSI GUTI allocated in step 18
Last visited registered TAI TAI-9 TAI 9 is allocated
on Cell I
according to
36.508 table
6.3.2.2-1

9.2.1.1.14 Attach / Rejected / Tracking area not allowed
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "Tracking area not
allowed" }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1176 Release 9
1176
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, UE deletes the GUTI, last
visited registered TAI and KSI, UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE and UE stores
the current TAI in the list of "forbidden tracking areas for regional provision of service" }
}
(2)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden
tracking areas for regional provision of service"}
ensure that {
when { serving cell belongs to TAI where UE was rejected }
then { UE does not attempt to attach on any other cell }
}
(3)
ensure that {
when { UE re-selects a new cell in the same TAI it was already rejected }
then { UE does not attempt to attach }
}
(4)
ensure that {
when { UE enters a cell belonging to a tracking area not in the list of "forbidden tracking areas
for regional provision of service"}
then { UE attempts to attach with IMSI }
}
(5)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the list of "forbidden tracking areas for
regional provision of service" contains more than one TAI}
ensure that {
when { UE re-selects a cell belonging to one of the TAIs in the list of "forbidden tracking areas
for regional provision of service" }
}
(6)
with { UE is switched off }
ensure that {
when { UE is powered on in the cell belonging to the TAI which was in the list of "forbidden
tracking areas for regional provision of service" before the UE was swithed off }
then { UE performs registration on that cell }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.3.2,
5.5.1.2.2, 5.5.1.2.5, 5.2.2.3.2, Annex C and TS 36.304 clause 4.3.
[TS 24.301, clause 5.3.2]
The UE shall store a list of "forbidden tracking areas for roaming", as well as a list of "forbidden tracking areas for
regional provision of service". These lists shall be erased when the UE is switched off or when the UICC containing the
USIM is removed, and periodically (with a period in the range 12 to 24 hours).
...
In S1 mode, the UE shall update the suitable list whenever an ATTACH REJ ECT, TRACKING AREA UPDATE
REJ ECT, SERVICE REJ ECT or DETACH REQUEST message is received with the EMM cause #12 "tracking area not
allowed", #13 "roaming not allowed in this tracking area", or #15 "no suitable cells in tracking area".
Each list shall accommodate 40 or more TAIs. When the list is full and a new entry has to be inserted, the oldest entry
shall be deleted.
[TS 24.301, clause 5.5.1.2.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1177 Release 9
1177
5.5.1.2.2.1).
...
message.
...
...
...
[TS 24.301, clause 5.5.1.2.5]
...
...
#12 (Tracking area not allowed);
reset the attach attempt counter.
In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of
service" and enter the state EMM-DEREGISTERED.LIMITED-SERVICE.
...
[TS 24.301, clause 5.2.2.3.2]
The UE shall perform an attach or combined attach procedure when entering a cell which provides normal service.
[TS 24.301, Annex C (normative)]
The following EMM parameters shall be stored on the USIM if the corresponding file is present:
- GUTI;
- last visited registered TAI;
- EPS update status;
- Allowed CSG list; and
- EPS security context parameters from a full native EPS security context (see 3GPP TS 33.401 [19]).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1178 Release 9
1178
The presence and format of corresponding files on the USIM is specified in 3GPP TS 31.102 [17].
If the corresponding file is not present on the USIM, these EMM parameters except allowed CSG list are stored in a
non-volatile memory in the ME together with the IMSI from the USIM. The allowed CSG list is stored in a non-volatile
memory in the ME if the UE supports CSG selection. These EMM parameters can only be used if the IMSI from the
USIM matches the IMSI stored in the non-volatile memory; else the UE shall delete the EMM parameters.

[TS 36.304, clause 4.3]

suitable cell:

Following exceptions to these definitions are applicable for UEs:
- camped on a cell that belongs to a registration area that is forbidden for regional provision of service; a cell that
belongs to a registration area that is forbidden for regional provision service ([5], [16]) is suitable but provides
only limited service.

System Simulator:
- cell A (home PLMN) and cell B (home PLMN, another TA) are configured according to table 6.3.2.2-1 in TS
36.508 [18] and belong to the same frequency as specified in TS 36.523-3 [20].
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1179 Release 9
1179
U - S Message
- Cell B as a "Suitable Neighbour cell".
- - - -
- - - -
REQUEST message.
message, EMM cause ="Tracking area not
allowed".
(The list of "forbidden tracking areas for
regional provision of service " in the UE should
now contain TAI-1)
6 Check: Does the UE transmit the ATTACH
REQUEST message in the next 30 seconds on
Cell A or Cell B?
--> ATTACH REQUEST 1, 2 F
command.
- - - -
Cell A as a "Suitable Neighbour cell",
- - - -
- - - -
--> ATTACH REQUEST 1,4 P
message, EMM cause ="Tracking area not
allowed".
regional provision of service " in the UE should
now contain TAI-1 and TAI-2)
Cell A as the "Serving cell".
Cell B as a " Suitable Neighbour cell".

- - - -
- - - -
--> ATTACH REQUEST 1, 3,
5
F
- - - -
Cell A as the "Serving cell",
Cell B as a "Non-Suitable cell".
- - - -
- - - -
USIM is inserted.
- - - -
18 Void - - - -
specified?

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1180 Release 9
1180
20-
32
RRC connection released by executing steps 5
to 17 of the UE registration procedure in TS
36.508 clause 4.5.2.3.
- - - -
to TS 36.508.
- - - -

Security header type 0000 "No security
protection"

EMM cause 00001100 #12 "Tracking
area not allowed"


Table 9.2.1.1.14.3.3-2: Message ATTACH REQUEST (steps 10 and 18 Table 9.2.1.1.14.3.2-1)
deleted after
receiving
ATTACH REJ ECT
at step 4; only
IMSI is available.

deleted after
receiving
ATTACH REJ ECT
at step 4.

9.2.1.1.15 Attach / Rejected / Roaming not allowed in this tracking area
(1)
ensure that {
when { the UE receives an ATTACH REJECT message with the reject cause set to "roaming not allowed
in this tracking area" }
then { the UE sets the EPS update status to EU3 ROAMING NOT ALLOWED and the UE deletes the GUTI,
the last visited registered TAI and KSI and the UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE
or optionally EMM-DEREGISTERED.PLMN-SEARCH and the UE stores the current TAI in the list of
"forbidden tracking areas for roaming" }
}
(2)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.PLMN-SEARCH state and the
TAI of the current cell belongs to the list of "forbidden tracking areas for roaming"}
ensure that {
when { the UE enters a cell belonging to a tracking area not in the list of "forbidden tracking
areas for roaming"}
then { the UE attempts to attach with IMSI }
}
(3)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.PLMN-SEARCH state and the
list of "forbidden tracking areas for roaming" contains more than one TAI}
ensure that {
when { the UE selects a cell belonging to one of the TAIs in the list of "forbidden tracking areas
for roaming" }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1181 Release 9
1181
then { the UE does not attempt to attach }
}
(4)
with { the UE is switched off or the UICC containing the USIM is removed }
ensure that {
tracking areas for roaming" before the UE was swithed off or the USIM is inserted again on that
cell }
}
(5)
ensure that {
when { the UE receives an ATTACH REJECT message with the reject cause set to "roaming not allowed
in this tracking area" }
then { the UE performs a PLMN selection }
}

5.5.1.2.2, 5.5.1.2.5 and in TS 36.304 clause 5.2.4.4.
[TS 24.301, clause 5.3.2]
...
shall be deleted.
[TS 24.301, clause 5.5.1.2.2]
figure 5.5.1.2.2.1).
...
message.If the UE supports A/Gb mode or Iu mode, the UE shall handle the Old GUTI or IMSI IE as follows:
...

...
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1182 Release 9
1182
[TS 24.301, clause 5.5.1.2.5]
...
...
#13 (Roaming not allowed in this tracking area);
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI. The UE shall delete the list of
equivalent PLMNs and reset the attach attempt counter.
In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for roaming". Additionally,
the UE shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE or optionally EMM-
DEREGISTERED.PLMN-SEARCH. The UE shall perform a PLMN selection according to 3GPP TS 23.122 [6].
...
[TS 36.304 subclause 5.2.4.4]
...
If the highest ranked cell is an intra-frequency or inter-frequency cell which is not suitable due to being part of the "list
of forbidden TAs for roaming" or belonging to a PLMN which is not indicated as being equivalent to the registered
PLMN, the UE shall not consider this cell and other cells on the same frequency, as candidates for reselection for a
maximum of 300s. If the UE enters into state any cell selection, any limitation shall be removed. If the UE is redirected
under E-UTRAN control to a frequency for which the timer is running, any limitation on that frequency shall be
removed.
...
System Simulator:
- cell C (home PLMN), cell I (visited PLMN) and cell E (same visited PLMN, another TA), but at most two cells
are simultaneously activated.
NOTE 1: Cell E shall not use the same frequency as cell I.
NOTE 2: The requirement in 3GPP TS 24.301 to store at least 40 entries in the list of "forbidden tracking areas for
roaming" is not fully tested.
NOTE 3: Different types of UE may use different methods to periodically clear the list of forbidden areas (e.g.
every day at 12 am) for roaming. If the list is cleared while the test is being run, it may be necessary to re-
run the test.
UE:
registered on cell I using default message contents according to TS 36.508 [18].
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1183 Release 9
1183
U - S Message
Cell I as the "Serving cell".
cell E as a " Non-Suitable Off cell",
cell C as a "Non-Suitable Off cell".
- - - -
cell I unless explicitly stated otherwise.
- - - -
REQUEST message.
message, EMM cause ="roaming not allowed
in this tracking area ".
roaming" in the UE should now contain TAI-9)
--> ATTACH REQUEST 1,5 F
command.
- - - -
Cell E unless explicitly stated otherwise.
- - - -
8A The SS configures:
Cell E as a " Suitable Neighbour celTS 36.508
l",
Cell C as a "Non-Suitable Off cell".
- - - -
CONNECTIVITY REQUEST message on Cell
E as specified?

Note: according to TS 24.301, the UE has the
choice to enter "LIMITED-SERVICE" or
"PLMN- SEARCH" state. But in any case it
shall do a PLMN selection. In the first option,
the UE shall apply reselection so it will select
cell E and then attempt to attach; in the
second option it will select the same PLMN
again and exclude cells from forbidden TAs so
it will select cell E.
in this tracking area".
roaming" in the UE should now contain TAI-9
and TAI-12)
Cell I or Cell E?
- - - -
Cell I as the "Serving cell",
Cell E as a "Non-Suitable Off cell",
Cell C as a "Non-Suitable Off cell".
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1184 Release 9
1184
USIM is inserted.
- - - -
REQUEST message as specified.
in this tracking area ".
Cell E as a "Non-Suitable Off cell",
Cell C as a "Suitable neigbour cell".
- - - -
Cell C unless explicitly stated otherwise.
- - - -
specified?
20-
32
36.508 clause 4.5.2.3.
- - - -
to TS 36.508.
- - - -

Table 9.2.1.1.15.3.3-1: Message ATTACH REJECT (steps 4, 10 and 17 in table 9.2.1.1.15.3.2-1)
Security header type 0000 "Plain NAS
message, not
security
protected"

EMM cause 00001101 #13 " roaming not
allowed in this
tracking area "


Table 9.2.1.1.15.3.3-2: Message ATTACH REQUEST (steps 9,12, 16 and 19 in table 9.2.1.1.15.3.2-1)
Old GUTI or IMSI IMSI1 GUTI has been
deleted after
receiving
ATTACH REJ ECT
at step 4; only
IMSI is available.

deleted after
receiving
ATTACH REJ ECT
at step 4.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1185 Release 9
1185
9.2.1.1.16 Attach / Rejected / EPS services not allowed in this PLMN
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "EPS services not allowed
in this PLMN" }
then { UE deletes any GUTI, last visited registered TAI, KSI and enters EMM-DEREGISTERED.PLMN-
SEARCH state}
}
(2)
with { UE in E-UTRA EMM-DEREGISTERED.PLMN-SEARCH state, and a PLMN is stored in the "forbidden PLMNs
for GPRS service list" }
ensure that {
when { UE detects a cell which belongs to a PLMN which is in the "forbidden PLMNs for GPRS service
list" }
then { UE doesnt perform an attach procedure }
}
(3)
ensure that {
when { UE detects a cell which belongs to a PLMN which is not in the "forbidden PLMNs for GPRS
service list" }
then { UE performs an attach procedure }
}
(4)
with { UE is switched off when a PLMN is stored in the "forbidden PLMNs for GPRS service list" }
ensure that {
when { UE is powered on a cell which belongs to this PLMN }
}
(5)
ensure that {
when { UE is in the cell which belongs to the rejected PLMN and when that PLMN is selected
manually }

TS23.122, clause 3.1.
[TS24.301 clause 5.5.1.2.5]
including an appropriate EMM cause value. If the attach procedure fails due to a default EPS bearer setup failure, an
ESM procedure failure, or operator determined barring is applied on default EPS bearer context activation during attach
procedure, the MME shall combine the ATTACH REJ ECT message with a PDN CONNECTIVITY REJ ECT message
contained in the ESM message container information element. In this case the EMM cause value in the ATTACH
REJ ECT message shall be set to #19 "ESM failure".

#14 (EPS services not allowed in this PLMN);

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1186 Release 9
1186
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI.
In S1 mode, the UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. Additionally,
the UE shall enter state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall perform a PLMN selection
according to 3GPP TS 23.122 [6]:
In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to
prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and
enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE.
If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state,
GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt
counter as specified in 3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM
cause with the same value.

[TS23.122 clause 3.1]

If a message with cause value "GPRS services not allowed in this PLMN" is received by an MS in response to an GPRS
attach, GPRS detach, routing area update, attach or tracking area update request (see 3GPP TS 24.008 [23] and
3GPP TS 24.301 [23A]) from a VPLMN, that VPLMN is added to a list of "forbidden PLMNs for GPRS service"
which is stored in the MS and thereafter that VPLMN will not be accessed by the MS for GPRS service when in
automatic mode. This list is deleted when the MS is switched off or when the SIM is removed. A PLMN is removed
from the list of "forbidden PLMNs for GPRS service" if, after a subsequent manual selection of that PLMN, there is a
successful GPRS attach. The maximum number of possible entries in this list is implementation dependant, but must be
at least one entry. The HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is
present) shall not be stored on the list of "forbidden PLMNs for GPRS service".

System Simulator:
- cell G, Cell H and cell I are configured according to Table 6.3.2.2-1 in; [18].
- cell G and Cell H with MCC-1/MNC-2 (visi;ted PLMN, different TAs)
- Cell I with MCC-2/MNC-101 (visited PLMN)
- the cells may not be simultaneously activated.
UE:
- the "forbidden PLMNs for GPRS service list" is empty.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1187 Release 9
1187
Table 9.2.1.1.16.3.2-1: Main Behaviour
U - S Message
- Cell H as a "Non-Suitable cell".
- - - -
- - - -
2 Void - - - -
REQUEST message.
message including EMM cause ="EPS
services not allowed in this PLMN".
Cell G as a "Non-Suitable cell".
Cell H as the "Serving cell".

Note: Cell G and Cell H are in the different TAI
same PLMN.
- - - -
Cell H unless explicitly stated otherwise.
- - - -
9 Void - - - -
Cell H as a "Non-Suitable cell".

Note: Cell G and Cell I are different PLMNs.
- - - -
- - - -
12 Void - - - -
REQUEST message including and a PDN
specified?
13
A
The SS completes the attach procedure
successfully and then releases the RRC -
connection by executing steps 5 to 17 of UE
registration procedure in TS 36.508 clause
4.5.2.3.

14 -
20
Void - - - -
- - - -
22 The SS configures
- - - -
- - - -
USIM is inserted.

24 Void - - - -
26 The SS transmits an ATTACH REJ ECT <-- ATTACH REJ ECT - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1188 Release 9
1188
message including EMM cause ="EPS
services not allowed in this PLMN".
27 The user sets the UE in manual PLMN
selection mode or requests a PLMN search.

28 The user selects PLMN (MCC-1/MNC-2)
specified?
30-
42
36.508 clause 4.5.2.3.
- - - -
to TS 36.508.
- - - -

EMM cause 00001110 #14 "EPS
services not
allowed in this
PLMN "


Table 9.2.1.1.16.3.3-2: Message ATTACH REQUEST (step 13 and step 29, Table 9.2.1.1.16.3.2-1)
deleted after
receiving
ATTACH REJ ECT
at step 5 and
step25; only IMSI
is available.

deleted after
receiving
ATTACH REJ ECT
at step 5 and
step26.

EMM cause 00001110 #14 "EPS
services not
allowed in this
PLMN "


9.2.1.1.17 Attach / Rejected / No suitable cells in tracking area
(1)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1189 Release 9
1189
ensure that {
when { the UE receives an ATTACH REJECT message with the EMM cause set to "No suitable cells in
tracking area" }
then { the UE set the EPS update status to EU3 ROAMING NOT ALLOWED, UE deletes any GUTI, last
visited registered TAI and KSI and the UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE and the
UE stores the current TAI in the list of "forbidden tracking areas for roaming" }
}
(2)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of
"forbidden tracking areas for roaming"}
ensure that {
when { the UE re-selects a cell that belongs to the TAI where UE was rejected }
then { the UE does not attempt to attach }
}
(3)
"forbidden tracking areas for roaming" and KSI was deleted }
ensure that {
when { in the same PLMN, the UE enters a cell which provides normal service and belongs to a
tracking area not in the list of "forbidden tracking areas for roaming" }
then { the UE attempts to attach with IMSI }
}
(4)
"forbidden tracking areas for roaming"}
ensure that {
when { there are cells in the same PLMN and other PLMN that provide normal service and belong to
tracking areas not in the list of "forbidden tracking areas for roaming" }
then { UE attempts to attach to the cell in the same PLMN }
}
(5)
roaming" contains more than one TAI}
ensure that {
when { UE re-selects a cell that belongs to one of the TAIs in the list of "forbidden tracking
areas for roaming" }
}
(6)
with { UE is swithched off }
ensure that {
tracking areas for roaming" before the UE was swithed off }
then { UE attempts to attach }
}

5.5.1.2.2 and 5.5.1.2.5, and in TS 36.304 clause 5.2.4.4.
[TS 24.301, clause 5.3.2]
...
shall be deleted.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1190 Release 9
1190
...
[TS 24.301, clause 5.5.1.2.2]
5.5.1.2.2.1).
...
message.
...
...
- Otherwise the UE shall include the IMSI in the Old GUTI or IMSI IE.

...
[TS 24.301, clause 5.5.1.2.5]
...
...
#15 (No suitable cells in tracking area);
reset the attach attempt counter.
In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for roaming" and enter the
state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking
area or in another location area in the same PLMN according to 3GPP TS 36.304 [21].
...
[TS 36.304 subclause 5.2.4.4]
...
If the highest ranked cell is an intra-frequency or inter-frequency cell which is not suitable due to being part of the "list
of forbidden TAs for roaming" or belonging to a PLMN which is not indicated as being equivalent to the registered
PLMN, the UE shall not consider this cell and other cells on the same frequency, as candidates for reselection for a
maximum of 300s. If the UE enters into state any cell selection, any limitation shall be removed. If the UE is redirected

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1191 Release 9
1191
under E-UTRAN control to a frequency for which the timer is running, any limitation on that frequency shall be
removed.
...
System Simulator:
- cell I, cell J , cell K and cell L are configured according to table 6.3.2.2-1 in TS 36.508 [18] (maximum 3 cells
are simultaneously active):
- cell I and cell K (visited PLMN, same TA);
- cell L (same visited PLMN, another TA);
- cell J (another VPLMN).
NOTE: Different types of UE may use different methods to periodically clear the list of forbidden areas (e.g.
run the test.
UE:
registered on cell I using default message contents according to TS 36.508 [18].
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1192 Release 9
1192
U - S Message
Cell K as a "Suitable Neighbour cell",
Cell L as a "Non-Suitable Off cell",
Cell J as a "Non-Suitable Off cell".
- - - -
- - - -
REQUEST message.
message,
EMM cause =No suitable cells in tracking
area.
(The list of forbidden tracking areas for
roaming in the UE should now contain TAI-9)
Cell I or Cell K?
Cell I as a "Suitable neighbour cell",
Cell K as the "Serving cell",
Cell J as a "Non-Suitable Off cell ".
- - - -
Cell K or Cell I?
8A If possible (see ICS) switch off is performed or
- - - -
Cell I as a " Serving cell",
Cell K is the " Non-Suitable Off cell ",
- - - -
9A The UE is brought back to operation or the
USIM is inserted.

9B The UE transmits an ATTACH REQUEST
REQUEST message.
9C The SS reconfigures:
Cell L as a "Suitable Neighbour cell",
Cell J as a "Suitable Neighbour cell.
- -
9D The SS transmits an ATTACH REJ ECT
message,
EMM cause =No suitable cells in tracking
area.
9E The SS releases the RRC connection. - - - -
specified on Cell L?
message, EMM cause =Tracking area not
allowed.
roaming in the UE should now contain TAI-9

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1193 Release 9
1193
and TAI-11)
Cell K as a Non-Suitable Off cell,
Cell L as a " Suitable Neighbour cell",
- - - -
- - - -
15 If possible (see ICS) switch off is performed.
- - - -
16 The UE is brought back to operation. - - - -
17 Void - - - -
19-
31
36.508 clause 4.5.2.3.
- - - -
to TS 36.508.
- - - -

Table 9.2.1.1.17.3.3-1: Message ATTACH REJECT (step 4 and 11 Table 9.2.1.1.17.3.2-1)
Derivation Path: TS 36.508 Table 4.7.2-3
Security header type 0000 No security
protection

EMM cause 0000 1111 #15 No suitable
cells in tracking
area


Table 9.2.1.1.17.3.3-2: Message ATTACH REQUEST (step 10 Table 9.2.1.1.17.3.2-1)
NAS key set identifier 111 "No key is
available"

deleted after
receiving
ATTACH REJ ECT
at step 4; only
IMSI is available.

deleted after
receiving
ATTACH REJ ECT
at step 4.

9.2.1.1.18 Attach / Rejected / Not authorized for this CSG
(1)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1194 Release 9
1194
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to " Not authorized for this
CSG " }
then { UE shall remove the CSG ID from the allowed CSG list and search for a suitable cell in
the same PLMN }
}
(2)
with { UE in state EMM-REGISTERED and EMM-IDLE mode and the CSG ID is removed from the Allowed CSG
list }
ensure that {
when { UE detects entering new tracking areas not included in the TAI list }
then { UE attempts to enter a normal cell and does not choose a cell which not included in the
allowed CSG list }
}

[TS 24.301, clause 5.5.1.2.5]
#25 (Not authorized for this CSG);
Cause #25 is only applicable when received from a CSG cell. Cause #25 received from a non-CSG cell is
considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.6.
If the ATTACH REJ ECT message with cause #25 was received without integrity protection, then the UE shall
discard the message.
subclause 5.1.3.3). Additionally, the UE shall reset the attach attempt counter and shall enter the state EMM-
DEREGISTERED.LIMITED-SERVICE.
The UE shall remove the CSG ID of the cell where the UE has sent the ATTACH REQUEST message from the
Allowed CSG list.
The UE shall search for a suitable cell in the same PLMN according to 3GPP TS 36.304 [21].
state, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case
when the normal attach procedure is rejected with the GMM cause with the same value.
System Simulator:
- cell A (TAC 1, frequency 1, not a CSG cell);
- cell B(TAC 2, frequency 1, is a CSG cell);
- cell C(TAC 3, frequency 2, not a CSG cell).
UE:
- the UE is previously registered on cell B using manual CSG selection (so the allowed CSG list includes CSG ID
of cell B);
registered in E-UTRAN using default message contents according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1195 Release 9
1195
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1196 Release 9
1196
U - S Message
- Cell A as a "Not Suitable cell".
- Cell B as a "Serving cell".
- Cell C as a "Not Suitable cell".
- - - -
- - - -
3 UE initiate attach procedure and send
ATTACH REQUEST including a PDN
message with EMM cause =" Not authorized
for this CSG " as specified.
- Cell A as a " Not Suitable cell".
- Cell B as a " Serving cell".
- Cell C as a " Suitable cell".
- - - -
- - - -
Note: The UE shall search for a suitable cell in
the same PLMN
authentication.
behaviour that depends on UE configuration.
- - - -
12a
1
options and/or APN.
12a
2
in step14 below the generic procedure for IP
- - - -
14 The UE transmit an ATTACH COMPLETE
15 The SS configures: - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1197 Release 9
1197
- Cell C as a "Not Suitable cell".
- - - -
16 Check: does the UE transmits a TRACKING
next 30 seconds?
REQUEST
2 F
- Cell A as a " Serving cell".
- Cell B as the "Not Suitable cell".
- Cell C as a " Non-Suitable cell".
- - - -
- - - -
next 30 seconds?
REQUEST
2 P
19 The SS transmits a TRACKING AREA
ACCEPT
- -
COMPLETE
- -

message, not
security protected "

EMM cause 00011001 #25 " Not authorized
for this CSG "


Table 9.2.1.1.18.3.3-2: SystemInformationBlockType1 for Cell A, B, C(Pre-test conditions and all steps
in Table 9.2.1.1.18.3.2-1)
csg-Indication TRUE Cell B
FALSE Cell A
FALSE Cell C
csg-Identity Not present Cell A
Not present Cell C
'000 0000 0000 0000
0000 0000 0010'B
Cell B

9.2.1.1.19 Attach / Abnormal case / Failure due to non integrity protection
(1)
with { UE has not performed NAS security mode control procedure }
ensure that {
when { UE receives an ATTACH ACCEPT messages without NAS integrity protection }
then { UE discards this message }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1198 Release 9
1198
(2)
with { a valid NAS security context exists and the NAS security mode control procedure has been
successfully completed in the network and the UE }
ensure that {
when { UE receives a NAS signalling message without integrity protection }
then { UE discards this NAS signalling message }
}
(3)
ensure that {
when { UE receives a security protected NAS signalling message with the Message authentication
code set to an incorrect value }
then { UE discards this NAS signalling message }
}
(4)
ensure that {
when { UE receives a NAS signalling message with integrity protection }
then { UE sends the response as a security protected NAS message }
}

4.4.4.2 and 5.5.2.2.
[TS 24.301, clause 4.4.4.1]
For the UE, integrity protected signalling is mandatory for the NAS messages once a valid EPS security context exists
and has been taken into use. For the network, integrity protected signalling is mandatory for the NAS messages once a
secure exchange of NAS messages has been established for the NAS signalling connection. Integrity protection of all
NAS signalling messages is the responsibility of the NAS. It is the network which activates integrity protection.

[TS 24.301, clause 4.4.4.2]
Except the messages listed below, no NAS signalling messages shall be processed by the receiving EMM entity in the
UE or forwarded to the ESM entity, unless the secure exchange of NAS messages has been established for the NAS
signalling connection:

- EMM messages:
- IDENTITY REQUEST (if requested identification parameter is IMSI);
- AUTHENTICATION REQUEST;
- AUTHENTICATION REJ ECT;
- ATTACH REJECT;
- DETACH REQUEST;
- DETACH ACCEPT (for non switch off);
- TRACKING AREA UPDATE REJ ECT;
- SERVICE REJECT.
NOTE: These messages are accepted by the UE without integrity protection, as in certain situations they are sent
by the network before security can be activated.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1199 Release 9
1199
All ESM messages are integrity protected.
Once the secure exchange of NAS messages has been established, the receiving EMM or ESM entity in the UE shall not
process any NAS signalling messages unless they have been successfully integrity checked by the NAS. If NAS
signalling messages, having not successfully passed the integrity check, are received, then the NAS in the UE shall
discard that message. If any NAS signalling message is received as not integrity protected even though the secure
exchange of NAS messages has been established by the network, then the NAS shall discard this message.
[TS 24.301, clause 5.5.2.2.1]
...
If the UE is to be switched off, the UE shall:
- delete the current EPS security context stored in the UE as specified in annex C, if it is a mapped EPS security
context;
- store the native EPS security context (if it is valid), as specified in annex C; and
- try for a period of 5 seconds to send the DETACH REQUEST message. During this period, the UE may be
switched off as soon as the DETACH REQUEST message has been sent.
...
System Simulator:
- cell A.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1200 Release 9
1200
U - S Message
REQUEST message.

Note: The ATTACH REQUEST message
shall be sent as a security protected NAS
message (see TS 24.301 clause 9.1).
- - - -
2A
a1
options and/or APN.
2A
a2
although UE has not successfully completed
any NAS security mode control procedure.

Note: The ATTACH ACCEPT message is
sent as a plain NAS message (see TS 24.301
clause 9.1).
COMPLETE message within the next 1s?

Note: the UE discards ATTACH ACCEPT
message without security protection
--> ATTACH COMPLETE 1 F
RESPONSE message to establish mutual
authentication.
without integrity protection.

Note: The ATTACH ACCEPT message is sent
as a plain NAS message (see TS 24.301
clause 9.1).

message without security protection
11 The SS transmits an ATTACH ACCEPT with
integrity protection with the Message
authentication code set to an incorrect value.

as a security protected NAS message (see TS

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1201 Release 9
1201
24.301 clause 9.1).

message because the integrity check is failed.
EPS BEARER CONTEXT REQUEST.
as a security protected NAS message (see TS
24.301 clause 9.1).

Nota 1: SS allocates a PDN address of a PDN
type which is compliant with from the PDN type
requested by the UE.
- - - -
COMPLETE message including a ACTIVATE
message as specified?

Note: The ATTACH COMPLETE message is
sent as a security protected NAS message
(see TS 24.301 clause 9.1).
16 Check : Does the test results of CALL generic
procedure [18] indicate that the UE is in E-
UTRA EMM-REGISTERED state with S-TMSI-
2?

Note: This step verifies that the UE has
correctly stored the GUTI-4 which was
included in the protected ATTACH ACCEPT
messages.
- - 4 -
to TS 36.508.
- - - -

Table 9.2.1.1.19.3.3-1: Message ATTACH ACCEPT (steps 3 and 9, Table 9.2.1.1.19.3.2-1)
GUTI GUTI-2 The SS chooses a
value different
from GUTI-1.

NOTE: This message is voluntarily sent as a plain NAS message (see TS 24.301 clause 9.1).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1202 Release 9
1202
Table 9.2.1.1.19.3.3-2: Message SECURITY PROTECTED NAS MESSAGE (step 11, Table
9.2.1.1.19.3.2-1)
Derivation path: 36.508 table 4.7.1 -1 with condition CIPHERED
Message authentication code Incorrect value The SS chooses
an incorrect value
which fails
integrity checks.
(e.g. 00000000)

NAS message ATTACH ACCEPT (see
table 9.2.1.1.19.3.3-3)

Derivation path: 36.508 table 4.7.2-1 (Security protected NAS message)
value different
from GUTI-1 and
GUTI-2.

value different
from GUTI-1,
GUTI-2 and GUTI-
3.

9.2.1.1.20 Attach / Abnormal case / Access barred because of access class barring or NAS
signalling connection establishment rejected by the network
(1)
with { UE switched-on, and not yet attached to EPS }
ensure that {
when { Access is barred for signalling in the cell UE is camping [Access Class barred in System
information] }
then { the UE will not initiate any Attach procedure on the current cell }
}
(2)
ensure that {
when { Access is barred for signalling in the cell UE is camping [T302 runiing due to
RRCConnectionReject message reception] }
then { the UE will not initiate any Attach procedure on the current cell }
}
(3)
ensure that {
when { Access is not barred for signalling in the cell UE is camping }
then { the UE will initiate Attach procedure on the current cell }
}
(4)
ensure that {

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1203 Release 9
1203
when { Access was barred for signalling in the cell and UE has reselected an new cell where access
for "signalling" is granted }
then { the UE will initiate Attach procedure on the new cell }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.1.2.6 and
TS 36.331, clause 5.3.3.2
[TS 24.301, clause 5.5.1.2.6]
The following abnormal cases can be identified:
a) Access barred because of access class barring or NAS signalling connection establishment rejected by the
network
If access is barred for "signalling" (see 3GPP TS 36.331 [22]), the attach procedure shall not be started. The UE
stays in the current serving cell and applies the normal cell reselection process. The attach procedure is started as
soon as possible, i.e. when access for "signalling" is granted on the current cell or when the UE moves to a cell
where access for "signalling" is granted.
[TS 36.331, clause 5. 3.3.2]
2> else if SystemInformationBlockType2 includes the ac-BarringInformation and the ac-BarringForMO-
Signalling is present:
3>else:
4>draw a random number rand uniformly distributed in the range: 0 rand <1;
4>if rand is lower than the value indicated by accessProbabilityFactor included in
accessBarringForSignalling:
4>else:
2> else:
System Simulator:
- cell I and cell K are configured according to table 6.3.2.2-1 in TS 36.508 [18].
- cell I and cell K belong to TAI-9 (home PLMN)
UE:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1204 Release 9
1204
registered on cell K using default message contents according to TS 36.508 [18].
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1205 Release 9
1205
U - S Message
1 The SS set the cell type of cell I to the ''Serving
cell'', set the cell type of cell K to the '' Non-
Suitable cell'', and set
SystemInformationBlockType2 parameters as
described below.
The UE is switched on.
- - - -
- - - -
2 Check: for 5 seconds if UE initiates Attach
procedure and hence transmits RRC
Connection Request?
- - 1 F
systemInfoModification.
- - - -
4 The SS changes
default parameters defined in [18].
- - - -
5 The UE transmits RRC Connection Request - - - -
6 SS responds with RRCConnectionReject
message with IE waitTime set to 10
seconds(Max Value).
- - - -
Connection Request?
- - 2 F
authentication.
- - - -
12
Aa
1
options and/or APN.
12
Aa
2

Note: The IP addresses of the UE are not
allocated in this test so PDN address is not
included in the message..
14 Check: does the UE transmit an ATTACH --> ATTACH COMPLETE - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1206 Release 9
1206
message?
- - - -
- EXCEPTION: Step 16a describes behaviour

--> DETACH REQUEST
17 The SS set the cell type of cell I to the ''Serving
cell'', set the cell type of cell K to the '' Non-
Suitable cell'', and set
SystemInformationBlockType2 parameters as
described below.
The UE is brought back to operation or the
USIM is inserted.
- - - -
Connection Request?
- - 1 F
19 The SS set the cell type of cell K to the ''
serving cell'' and cell I to suitable Cell.

Cell K unless explicitly stated otherwise.
- - - -
21-
32
- - - -
- - - -

Table 9.2.1.1.20.3.3-1: SystemInformationBlockType2 for Cell I (step 1 and 17)
accessBarringInformation SEQUENCE {
accessBarringForEmergencyCalls FALSE
accessBarringForSignalling SEQUENCE {
accessProbabilityFactor p00
accessBarringTime s4
accessClassBarringList SEQUENCE (SIZE
(maxAC)) OF SEQUENCE {
5 entries
accessClassBarring[1] TRUE
}
}
accessBarringForOriginatingCalls Not present
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1207 Release 9
1207
Table 9.2.1.1.20.3.3-2: SystemInformationBlockType1 for Cell I (step 17)
intraFreqReselection allowed
}
}

9.2.1.1.21 Attach / Abnormal case / Success after several attempts due to no network
response
(1)
with { UE has sent an ATTACH REQUEST message and started T3410 timer}
ensure that {
when { T3410 timer epires }
then { the UE release NAS signalling connection locally}
}
(2)
with { UE has sent an ATTACH REQUEST message and T3410 timer expired}
ensure that {
when { T3411 timer epires and attach attempt counter is less than 5 }
then { the UE restarts the attach procedure}

(3)
ensure that {
when { Lower Layer failure (RRC Connection is released) before the ATTACH ACCEPT or ATTACH REJECT
message is received, T3411 has expired and attach attempt counter is less than 5}
then { the UE restarts the attach procedure }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.1.2.6 &
10.2
[TS 24.301, clause 5.5.1.2.6]

b) Lower layer failure or release of the NAS signalling connection before the ATTACH ACCEPT or ATTACH
REJ ECT message is received
The attach procedure shall be aborted, and the UE shall proceed as described below.
c) T3410 timeout
The UE shall abort the attach procedure and proceed as described below. The NAS signalling connection shall
be released locally.

For the cases b, c, and d the UE shall proceed as follows:
- Timer T3410 shall be stopped if still running. The attach attempt counter shall be incremented, unless it was
already set to 5.
If the attach attempt counter is less than 5:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1208 Release 9
1208
- timer T3411 is started and the state is changed to EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH.
When timer T3411 expires the attach procedure shall be restarted.
[TS 24.301, clause 10.2]
Table 10.2.1: EPS mobility management timers UE side
TIMER
NUM.
TIMER
VALUE
STATE CAUSE OF START NORMAL STOP ON
EXPIRY

T3410 15s EMM-
REGISTERED-
INITIATED
ATTACH REQUEST sent ATTACH ACCEPT
received
ATTACH REJ ECT
received
Start T3411 or
T3402 as described
in
subclause 5.5.1.2.6
T3411 10s EMM-
DEREGISTERED.
ATTEMPTING-
TO-ATTACH

EMM-
REGISTERED.
ATTEMPTING-
TO-UPDATE
At attach failure due to lower
layer failure, T3410 timeout or
attach rejected with other EMM
cause values than those treated
in subclause 5.5.1.2.5.

At tracking area updating failure
due to lower layer failure, T3430
timeout or TAU rejected with
other EMM cause values than
those treated in
ATTACH REQUEST
sent
TRACKING AREA
UPDATE
REQUEST sent
Retransmission of
the ATTACH
REQUEST or
TRACKING AREA
UPDATE
REQUEST

System Simulator:
- cell A.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1209 Release 9
1209
U - S Message
message.
3 The SS waits 20 seconds (15 seconds T3410
and 5 seconds half of T3411).
- - -
type
Exception: In parallel with steps 5 and 6, the
parallel behaviour defined in table
9.2.1.1.1.3.2-2 is running.

5 The SS waits 5 seconds (half of T3411) - - - -
6 Check: The UE transmit an ATTACH
REQUEST message?
7 The SS releases the RRC connection.
8 The SS waits 10 seconds (T3411).
9 Check: The UE transmits an ATTACH
REQUEST message?
10-
21
- - - -
- - - -

Table 9.2.1.1.21.3.2-2 : Parallel behaviour
U - S Message
1 Check: Does the UE sends an IDENTITY
RESPONSE message?
--> IDENTITY RESPONSE 1 F

None
9.2.1.1.22 Attach / Abnormal case / Unsuccessful attach after 5 attempts
(1)
ensure that {
when { T3411 has expired and attach attempt counter is equal to 5}
then { the UE stops attach attempts and starts timer T3402 }
}

10.2
[TS 24.301, clause 5.5.1.2.6]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1210 Release 9
1210
b) Lower layer failure or release of the NAS signalling connection before the ATTACH ACCEPT or ATTACH
REJ ECT message is received
The attach procedure shall be aborted, and the UE shall proceed as described below.
c) T3410 timeout

already set to 5.
If the attach attempt counter is equal to 5:
- the UE shall delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs and KSI, shall set
the update status to EU2 NOT UPDATED, and shall start timer T3402. The state is changed to EMM-
DEREGISTERED.ATTEMPTING-TO-ATTACH or optionally to EMM-DEREGISTERED.PLMN-SEARCH in
order to perform a PLMN selection according to 3GPP TS 23.122 [6].
specified in 3GPP TS 24.008 [13] for the abnormal case when a normal attach procedure fails and the attach
attempt counter is equal to 5.
[TS 24.301, clause 10.2]
TIMER
NUM.
TIMER
VALUE
EXPIRY
T3402 Default 12
min.
NOTE 1
EMM-
DEREGISTERED
EMM-
REGISTERED
At attach failure and the attempt
counter is equal to 5.
and the attempt counter is equal
to 5.
ATTACH REQUEST
sent
TRACKING AREA
UPDATE
REQUEST sent
Initiation of the
attach procedure or
TAU procedure

T3410 15s EMM-
REGISTERED-
INITIATED
received
ATTACH REJ ECT
received
Start T3411 or
T3402 as described
in
subclause 5.5.1.2.6
T3411 10s EMM-
DEREGISTERED.
ATTEMPTING-
TO-ATTACH

EMM-
REGISTERED.
ATTEMPTING-
TO-UPDATE

those treated in
ATTACH REQUEST
sent
TRACKING AREA
UPDATE
REQUEST sent
Retransmission of
the ATTACH
REQUEST or
TRACKING AREA
UPDATE
REQUEST

Note 1: The default value of this timer is used if the network does not indicate another value in an EMM signalling
procedure.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1211 Release 9
1211
System Simulator:
- cell A.
Note:- T3402 is set to default (12 min.).
UE:
Preamble:
U S Message
message. (Attach attempt counter =1)
and 10 seconds T3411).
- - -
6 The SS waits 10 seconds ( T3411).
and 10 seconds T3411).
- - -
11 The SS waits 10 seconds ( T3411).
--> ATTACH REQUEST
14 Check: Does the UE transmits an ATTACH
REQUEST message after 12 minutes (default
value of T3402, after step 13?
15-
26
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1212 Release 9
1212
available"

deleted; only IMSI
is available.

deleted.

9.2.1.1.23 Attach / Abnormal case / Repeated rejects for network failures
(1)
with { UE having valid GUTI, has sent an ATTACH REQUEST message }
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to #17 or #22 and attach
attempt counter is less than 5}
then { UE starts timer T3411 and shall not deleate stored GUTI }
when { Timer T3411 expires}
then { UE restarts attach procedure }
}

(2)
with { UE having valid GUTI, has sent an ATTACH REQUEST message }
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to #22 and attempt counter
is set to 5}
then { the UE stops attach attempts and starts timer T3402, shall delete stored GUTI }
}

NOTE: Only representative coverage for various abnormal reject causes is provided.
5.5.1.2.6, 9.9.3.9 & 10.2
[TS 24.301, clause 5.5.1.2.5]
including an appropriate EMM cause value. If the attach procedure fails due to a default EPS bearer setup failure, an
ESM procedure failure, or operator determined barring is applied on default EPS bearer context activation during attach
procedure, the MME shall combine the ATTACH REJ ECT message with a PDN CONNECTIVITY REJ ECT message
contained in the ESM message container information element. In this case the EMM cause value in the ATTACH
REJ ECT message shall be set to #19 "ESM failure".
...
Other values are considered as abnormal cases. The behaviour of the UE in those cases is specified in
[TS 24.301, clause 5.5.1.2.6]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1213 Release 9
1213
d) ATTACH REJECT, other EMM cause values than those treated in subclause 5.5.1.2.5
Upon reception of the EMM cause #19, "ESM failure", the UE may set the attach attempt counter to 5. Upon
reception of the EMM causes #95, #96, #97, #99 and #111 the UE should set the attach attempt counter to 5.
The UE shall proceed as described below.

already set to 5.
[TS 24.301, clause 9.9.3.9]
Table 9.9.3.9.1: EMM cause information element
Cause value (octet 2)

Bits
8 7 6 5 4 3 2 1
...
0 0 0 1 0 0 0 1 Network failure
0 0 0 1 0 0 1 0 CS domain not available
0 0 0 1 0 0 1 1 ESM failure
0 0 0 1 0 1 0 0 MAC failure
0 0 0 1 0 1 0 1 Synch failure
0 0 0 1 0 1 1 0 Congestion
0 0 0 1 0 1 1 1 UE security capabilities mismatch
...
Any other value received by the mobile station shall be treated as 0110 1111, "protocol
error, unspecified". Any other value received by the network shall be treated as 0110
1111, "protocol error, unspecified".

[TS 24.301, clause 10.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1214 Release 9
1214
TIMER
NUM.
TIMER
VALUE
EXPIRY
T3402 Default 12
min.
NOTE 1
EMM-
DEREGISTERED
EMM-
REGISTERED
At attach failure and the attempt
counter is equal to 5.
and the attempt counter is equal
to 5.
ATTACH REQUEST
sent
TRACKING AREA
UPDATE
REQUEST sent
Initiation of the
attach procedure or
TAU procedure

T3410 15s EMM-
REGISTERED-
INITIATED
received
ATTACH REJ ECT
received
Start T3411 or
T3402 as described
in
subclause 5.5.1.2.6
T3411 10s EMM-
DEREGISTERED.
ATTEMPTING-
TO-ATTACH

EMM-
REGISTERED.
ATTEMPTING-
TO-UPDATE

those treated in
ATTACH REQUEST
sent
TRACKING AREA
UPDATE
REQUEST sent
Retransmission of
the ATTACH
REQUEST or
TRACKING AREA
UPDATE
REQUEST

Note 1: The default value of this timer is used if the network does not indicate another value in an EMM signalling
procedure.

System Simulator:
- cell A.
Note: T3402 is set to default (12 min.).
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1215 Release 9
1215
U S Message
message, EMM cause =Network failure (#17)
5 The SS waits 10 seconds (T3411). - - - -
REQUEST message? (Attach attempt counter
=2)
message, EMM cause =Network failure (#17)
=3)
message, EMM cause =Congestion (#22)
=4)
<-- ATTACH REJ ECT 1 -
17 The SS waits 10 seconds ( T3411). - - - -
21 The SS waits 12 minutes (default value of
T3402).
- - - -
REQUEST message?
23-
34
- - - -
- - - -

Table 9.2.1.1. 23.3.3-1: Message ATTACH REQUEST (step 2, 6, 10 &14 Table 9.2.1.1.24.2-1)
NAS key set identifier Any allowed value other
than '111'B
"Stored key is
available"

Old GUTI or IMSI GUTI-1 As stored in USIM
Last visited registered TAI TAI-1 Stored TAI.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1216 Release 9
1216
Table 9.2.1.1. 23.3.3-2: Message ATTACH REJECT (steps 3 & 7 Table 9.2.1.1.23.3.2-1)
message, not
security protected
"

EMM cause 00010001 #17 " Network
failure "


Table 9.2.1.1. 23.3.3-3: Message ATTACH REJECT (steps 11, 15 & 19 Table 9.2.1.1.23.3.2-1)
message, not
security protected
"

EMM cause 00010110 #22 "Congestion "

Derivation Path: TS 36.508 Table 4.7.2.4
available"

deleted; only IMSI
is available.

deleted.

9.2.1.1.24 Attach / Abnormal case / Change of cell into a new tracking area
(1)
with { UE has sent an ATTACH Request message and ATTACH ACCEPT message is not received }
ensure that {
when { UE reselects a cell belonging to a new tracking area }
then { the UE restarts the attach procedure }
}

(2)
with { UE has sent an ATTACH REQUEST message and received ATTACH ACCEPT message containing GUTI}
ensure that {
when { UE reselects a cell belonging to a new tracking area}}
then { the UE restarts the attach procedure}
}

[TS 24.301, clause 5.5.1.2.6]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1217 Release 9
1217
e) Change of cell into a new tracking area
If a cell change into a new tracking area occurs before the attach procedure is completed, the attach procedure
shall be aborted and re-initiated immediately. If a tracking area border is crossed when the ATTACH ACCEPT
message has been received but before an ATTACH COMPLETE message is sent, the attach procedure shall be
re-initiated. If a GUTI was allocated during the attach procedure, this GUTI shall be used in the attach procedure.
System Simulator:
- cells A and B:
- cell A is the serving cell with TAI 1 (PLMN1+TAC1);
- cell B is the non-suitable cell with TAI 2 (PLMN1+TAC2).
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1218 Release 9
1218
U - S Message
message in Cell A including a PDN
- Cell B as a serving cell
- Cell A as a "non-suitable cell".
- - -
- - - -
REQUEST message in Cell B including a PDN
4A The SS transmits an AUTHENTICATION
authentication.
EXCEPTION: Steps 8a to 8b describe
- - - -
8a IF the UE sets the ESM information transfer
options and/or APN.
8b The UE transmits an ESM INFORMATION
- Cell A as a serving cell
- - - -
10 SS is configured to not allocate any UL grant
or respond to any PRACH preambles for
ATTACH COMPLETE in Cell B.
- - - -
ATTACH ACCEPT message. GUTI-1 is
allocated.
- Cell B as a "non-suitable cell".
- - - -
13 UE transmits
message in Cell A
- - - -
14 SS Sends RRCConnectionReestablishment - - - -
message
- - - -
- - - -
REQUEST message, containing GUTI 1?

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1219 Release 9
1219
- - - -
NOTE 1: UE already has NAS security context in step 17 and just sending a DL message with Integrity and Ciphering
will start enable NAS security

Table 9.2.1.1.24.3-1: Message ATTACH ACCEPT step 11, Table 9.2.1.1.24.3.2-1)
GUTI GUTI-1

9.2.1.1.25 Attach / Abnormal case / Mobile originated detach required
(1)
ensure that {
when { the UE initiates mobile originated detach }
then { the UE aborts the attach procedure }
}

[TS 24.301, clause 5.5.1.2.6]
f) Mobile originated detach required
The attach procedure shall be aborted, and the UE initiated detach procedure shall be performed.

System Simulator:
- cell A.
UE:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1220 Release 9
1220
Preamble:
U - S Message
message.
authentication.
7 The SS does not respond to ATTACH
REQUEST message.
- - - -
8 Check: Does the UE initiate mobile originated
detach and abort the attach procedure while
T3410 is running.
9 The SS transmits DETACH ACCEPT
message.
<-- DETACH ACCEPT - -
paged with GUTI-1 and with CN domain
indicator set to "PS"?
- - 1 -
11 Void - - - -
Note: T3410 value is specified as 15s in TS 24.301.

Table 9.2.1.1.25.3.3-1: Message DETACH REQUEST (step 8, Table 9.2.1.1.25.3.2-1)
Detach type 0001 Normal EPS
detach

9.2.1.1.26 Attach / Abnormal case / Detach procedure collision
(1)
with { UE in EMM-REGISTERED-INITIATED state}
ensure that {
when { UE receives a DETACH REQUEST message and detach type indicates re-attach not required}
then { the UE sends DETACH ACCEPT }

(2)
with { UE in EMM-REGISTERED-INITIATED state}
ensure that {
when { UE receives a DETACH REQUEST message and detach type indicates re-attach required}
then { the UE continues with ATTACH procedure }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1221 Release 9
1221
}

10.2
[TS 24.301, clause 5.5.1.2.6]

g) Detach procedure collision
If the UE receives a DETACH REQUEST message from the network in state EMM-REGISTERED-INITIATED
and the detach type indicates "re-attach not required", the detach procedure shall be progressed and the attach
procedure shall be aborted. Otherwise the attach procedure shall be progressed and the DETACH REQUEST
message shall be ignored.
System Simulator:
- cell A.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1222 Release 9
1222
U - S Message
REQUEST message.
3

The SS initiates Detach procedure with the
Detach Type IE "re-attach not required"
<-- DETACH REQUEST - -
4 Check: Does the UE send DETACH ACCEPT
message?
--> DETACH ACCEPT 1 P
- - - -
6a The UE is brought back to operation or the
USIM is inserted.

authentication and AKA procedure
authentication.
- - - -
12a
1
options and/or APN.
12a
2
13 The SS initiates Detach procedure with the
Detach Type IE "re-attach required"
Exception: In parallel with steps 13 to 15, the
parallel behaviour defined in table
9.2.1.1.26.3.2-2 is running.

ATTACH ACCEPT message. GUTI-1 is
allocated.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1223 Release 9
1223
EPS BEARER CONTEXT ACCEPT message?
16 The SS waits 5 seconds - - - -
NOTE 1: Step 16 is added to additionally guarantee UE has neglected DETACH REQUEST message.

Table 9.2.1.1.26.3.2-2 : Parallel behaviour
U - S Message
message?
--> DETACH ACCEPT 2 F

Detach type '010'B "re-attach not
required"

EMM cause 08H EPS services and
non-EPS services
not allowed

Detach type 001'B "re-attach
required"

EMM cause NOT PRESENT

9.2.1.2 Combined attach procedure for EPS services and non-EPS services
9.2.1.2.1 Combined attach procedure / Success / EPS and non-EPS services
(1)
with { UE in state EMM-DEREGISTERED and is switched off }
ensure that {
when { UE is powered up or switched on}
then { UE sends ATTACH REQUEST message with EPS attach type IE 'combined EPS/IMSI attach' }
}
(2)
with { UE in state EMM-REGISTERED-INITIATED}
ensure that {
when { UE receives ATTACH ACCEPT message with EPS attach result 'combined EPS/IMSI attach' }
then { UE sends ATTACH COMPLETE message and enters EMM state EMM-REGISTERED and MM state MM-IDLE
and UE responds to a paging message with CS or PS domain}
}
(3)
with { UE in state EMM-REGISTERED and state MM-IDLE}
ensure that {
when { SS sends Paging message with CS domain }
then { UE sends EXTENDED SEREVICE REQUEST message }
}

(4)
with { UE in state EMM-REGISTERED and EMM-IDLE mode}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1224 Release 9
1224
ensure that {
when { UE enters a new tracking area already included in the TAI list }
then { UE does not send TRACKING AREA UPDATE REQUEST message and UE responds to a paging message
with CS or PS domain}
}
(5)
ensure that {
when { UE enters a new tracking area not included in the TAI list }
then { UE sends TRACKING AREA UPDATE REQUEST message with 'EPS update type = combined TA/LA
updated '}
}
(6)
with { UE in state EMM-DEREGISTERED and is switched off and has a valid TAI value in 'Last visited
registered TAI' IE and a valid GUTI}
ensure that {
when { UE is powered up or switched on}
then { UE sends ATTACH REQUEST message with EPS attach type IE 'combined EPS/IMSI attach'and with
the value in 'Last visited registered TAI' and the valid GUTI}
}

5.5.1.3.1, 5.5.1.3.4.1 and 5.5.1.3.4.2.
[TS24.301 clause5.5.1.3.1]
The combined EPS attach procedure is used by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for both
EPS and non-EPS services.
The combined EPS attach procedure is also used by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for
EPS services if it is already attached for non-EPS services.
When the UE initiates a combined EPS attach procedure, the UE shall indicate "combined EPS/IMSI attach" in the EPS
attach type IE.
The combined EPS attach procedure follows the attach procedure for EPS described in subclause 5.5.1.2.
[TS24.301 clause5.5.1.3.2]
If the UE is in EMM state EMM-DEREGISTERED, the UE initiates the combined attach procedure by sending an
ATTACH REQUEST message to the network, starting timer T3410 and entering state EMM-REGISTERED-
INITIATED (see example in figure 5.5.1.2.2.1).
The UE shall include the TMSI status IE if no valid TMSI is available. Furthermore, if the UE has stored a valid
location area identification, the UE shall include it in the Old location area identification IE in the ATTACH REQUEST
message.
[TS24.301 clause5.5.1.3.4.1]
Depending on the value of the EPS attach result IE received in the ATTACH ACCEPT message, two different cases
can be distinguished:
1) The EPS attach result IE value indicates "combined EPS/IMSI attach": attach for EPS and non-EPS services
have been successful.

[TS24.301 clause5.5.1.3.4.2]
The description for attach for EPS services as specified in subclause 5.5.1.2.4 shall be followed. In addition, the
following description for attach for non-EPS services applies.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1225 Release 9
1225
The TMSI reallocation may be part of the combined attach procedure. The TMSI allocated is then included in the
ATTACH ACCEPT message, together with the location area identification (LAI). In this case the MME shall start timer
T3450 and enter state EMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.4.1.
The UE, receiving an ATTACH ACCEPT message, stores the received location area identification, stops timer T3410,
resets the location update attempt counter and sets the update status to U1 UPDATED. If the message contains an IMSI,
the UE is not allocated any TMSI, and shall delete any TMSI accordingly. If the message contains a TMSI, the UE shall
use this TMSI as the new temporary identity. The UE shall delete its old TMSI and shall store the new TMSI. If neither
a TMSI nor an IMSI has been included by the network in the ATTACH ACCEPT message, the old TMSI, if any
available, shall be kept.IThe UE, when receiving the ATTACH ACCEPT message combined with the ACTIVATE
DEFAULT EPS BEARER CONTEXT REQUEST message, shall send an ATTACH COMPLETE message combined
with an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message to the network after which it shall enter
state EMM-REGISTERED and MM state MM-IDLE and set the EPS update status to EU1 UPDATED.
System Simulator:
- cell A, cell B and cell C are configured according to Table 6.3.2.2-1 in [18]:
- cell A belongs to TAI-1 (home PLMN);
- cell B belongs to TAI-2 (home PLMN, another TAC);
- cell C belongs to TAI-3 (home PLMN, another TAC).
- The different cells may not be simultaneously activated (at most 2 cells are active simultaneously).
UE:
- the UE is configured to initiate combined EPS/IMSI attach;
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1226 Release 9
1226
U - S Message
- Cell A as the Serving cell.
- Cell B as a Non-Suitable cell.
- Cell C as a Non-Suitable Off cell.
cell
- - - -
- - - -
2 The UE is powered up or switched on. - -
3 Check: Does the UE ATTACH REQUEST
message with a PDN CONNECTIVITY
REQUEST message to request PDN
connectivity to the default PDN. EPS attach
type ="combined EPS/IMSI attach"?
4 The SS starts an authentication procedure <-- AUTHENTICATION REQUEST - -
5 The UE responds properly to the
authentication procedure
6 The SS starts a NAS security mode command
procedure to perform NAS integrity protection.
7 The UE responds properly to the NAS security
mode command procedure
- - - -
7A
a1
options and/or APN.
7A
a2
8 The SS sends ATTACH ACCEPT message
with the ACTIVATE DEFAULT EPS BEARER
CONTEXT REQUEST message.
9 Check: Does the UE send ATTACH
COMPLETE message with the ACTIVATE
message?
10 The SS releases the RRC connection. - -
11 Check: Does the UE respond to paging on cell
A with S-TMSI in GUTI-2 for PS domain?
(Generic Procedure TS36.508 cl. 6.2.4.2)
- - 2 -
12 The SS transmits a paging on cell A with S-
TMSI in GUTI-2 for CS domain.
- - - -
13 Check: Does the UE send EXTENDED
SERVICE REQUEST message?
--> EXTENDED SERVICE REQUEST 3 P
14 The SS transmits SERVICE REJ ECT with
cause #39 'CS domain temporarily not
available' with T3442 =5s and the SS waits 5
sec.
<-- SERVICE REJ ECT
15 Void
- Cell A as a Non-Suitable cell.
- Cell B as the Serving cell.
- Cell C as a Non-Suitable Off cell.

- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1227 Release 9
1227
next 30 seconds?
- - 4 F
B with S-TMSI in GUTI-2 for PS domain?
- - 4 -
B with S-TMSI in GUTI-2 for CS domain?
- - 4 -
- Cell A as a Non-Suitable Off cell.
- Cell B as a Non-Suitable cell.
- Cell C as the Serving cell.

- - - -
- - - -
REQUEST
5 P
ACCEPT
- -
UPDATE COMPLETE message?
COMPLETE
- -
- - - -

the UE transmit a DETACH REQUEST.
USIM is inserted.
- - - -
REQUEST message with a PDN
CONNECTIVITY REQUEST message to
request PDN connectivity to the default PDN.
29-
30

NOTE: For the content of the ATTACH
ACCEPT message to be used in the
UE registration procedure in TS
36.508 clause 4.5.2.3 see Table
9.2.1.2.1.3.3-8 below
- - - -
- - - -

EPS attach type '0010'B ''combined
EPS/IMSI attach''

Old GUTI or IMSI GUTI-1
Last visited registered TAI TAI-1
Old location area identification LAI-1
TMSI status Not Present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1228 Release 9
1228
EPS attach result '010'B ''Combined
EPS/IMSI attach''

TAI list
Number of elements '00001'B
Type of list '00'B ''list of TACs
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAC 2
PLMN=MCC/MNC
TAC 1=1
TAC 2=2
''PLMN is set to
the same
MCC/MNC stored
in EF
IMSI
''
''TAI-1''
''TAI-2''

GUTI GUTI-2
LAI LAI-1
MS identity TMSI-1

Table 9.2.1.2.1.3.3-3: Message EXTENDED SERVICE REQUEST (step 13, Table 9.2.1.2.1.3.2-1)
Derivation Path: 36.508 table 4.7.2.-14A
M-TMSI M-TSMI2 ''M-TMSI2 is a
part of GUTI-2''

Table 9.2.1.2.1.3.3-4: Message SERVICE REJECT (step 14, Table 9.2.1.2.1.3.2-1)
EMM cause '0010 0111'B #39 'CS domain
temporarily not
available'

T3442 value 5 sec

Table 9.2.1.2.1.3.3-5: Message TRACKING AREA UPDATE REQUEST (step 21, Table 9.2.1.2.1.3.2-1)
EPS update type
EPS update type value '001'B ''Combined TA/LA
updating''

Old GUTI GUTI-2 ''Old GUTI is
included by UE if
valid, IMSI
otherwise''


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1229 Release 9
1229
Table 9.2.1.2.1.3.3-6: Message TRACKING AREA UPDATE ACCEPT (step 22, Table 9.2.1.2.1.3.2-1)
EPS update result '001'B ''combined TA/LA
updated''

GUTI GUTI-3
TAI list
Length of tracking area identity list contents '00000110'B
Partial tracking area identity list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAI-3
Location area identification LAI-3
MS identity TMSI-3

EPS/IMSI attach''


Table 9.2.1.2.1.3.3-8: Message ATTACH ACCEPT (For the UE registration procedure in TS 36.508
clause 4.5.2.3)
EPS/IMSI attach''

TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAI-3
GUTI GUTI-3

9.2.1.2.1b Combined attach procedure / Success / SMS only
9.2.1.2.1b.1 Test Purpose (TP)
(1)
with { UE operating in CS/PS mode 1, in state EMM-REGISTERED-INITIATED}
ensure that {
when { UE receives ATTACH ACCEPT message with EPS attach result 'combined EPS/IMSI attach' and
Additional update result IE 'SMS only'}
then { UE sends ATTACH COMPLETE message and enters EMM state EMM-REGISTERED and MM state MM-IDLE}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1230 Release 9
1230
}

(2)
with { UE operating in CS/PS mode 1 with "IMS voice not available", in state EMM-REGISTERED and
state MM-IDLE}
ensure that {
when { SS activate UTRAN cell or GERAN cell}
then { UE automatically disable to E-UTRAN capability and performs a registration to UTRAN cell
or GERAN cell(depending on the UE capability)}
}

(3)
with { UE operating in CS/PS mode 1 without "IMS voice not available" or in CS/PS mode2, in state
EMM-REGISTERED and state MM-IDLE}
ensure that {
when { SS sends Paging message with PS domain }
then { UE sends SERVICE REQUEST message }
}

(4)
with { UE operating in CS/PS mode 1 without "IMS voice not available" or in CS/PS mode2, in state
ensure that {
then { UE does not respond paging message}

9.2.1.2.1b.2 Conformance requirements
5.5.1.3.1, 5.5.1.3.4.1 5.5.1.3.4.2 and 5.6.2.4.
[TS24.301 clause5.5.1.3.1]
The combined attach procedure is used by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for both EPS
and non-EPS services, or both EPS services and "SMS only".
The combined attach procedure is also used by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for EPS
services if it is already IMSI attached for non-EPS services.
When the UE initiates a combined attach procedure, the UE shall indicate "combined EPS/IMSI attach" in the EPS
attach type IE.
The combined attach procedure follows the attach procedure for EPS described in subclause 5.5.1.2.
[TS24.301 clause5.5.1.3.2]
message.
If the UE initiates a combined attach procedure for EPS services and "SMS only", the UE shall indicate "SMS only" in
the Additional update type IE.
[TS24.301 clause5.5.1.3.4.1]
Depending on the value of the EPS attach result IE received in the ATTACH ACCEPT message, the following different
cases can be distinguished:
1) The EPS attach result IE value indicates "combined EPS/IMSI attach": attach for EPS and non-EPS services, or
for EPS services and "SMS only" have been successful.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1231 Release 9
1231

[TS24.301 clause5.5.1.3.4.2]
following description for attach for non-EPS services or "SMS only" applies.

If the UE requested "SMS only" in the Additional update type IE, the network shall indicate "SMS only" in the
Additional update result IE.
If the ATTACH ACCEPT message includes the Additional update result IE with value "SMS only" or "CS Fallback not
preferred", a UE operating in CS/PS mode 1 with "IMS voice not available" shall attempt to select GERAN or UTRAN
radio access technology rather than E-UTRAN for the selected PLMN or equivalent PLMN. The UE shall disable the E-
UTRA capability (see subclause 4.5). If the UE is in the EMM-CONNECTED mode, the UE shall locally release the
established NAS signalling connection and enter the EMM-IDLE mode before selecting GERAN or UTRAN radio
access technology.
If the ATTACH ACCEPT message includes the Additional update result IE with value "SMS only", a UE operating in
CS/PS mode 2 shall not attempt to use CS fallback for mobile originating services.
.
[TS24.301 clause5.6.2.4]
The network shall initiate the paging procedure when it receives an incoming mobile terminating SMS to the UE that is
IMSI attached for non-EPS services or for "SMS only", and no NAS signalling connection exists.
To initiate the procedure for SMS when no NAS signalling connection exists, the EMM entity in the network requests
the lower layer to start paging (see 3GPP TS 36.413 [23]). The paging message shall include a CN domain indicator set
to "PS". The paging procedure is performed according to subclause 5.6.2.2.1. The MME shall not start timer T3413 for
this procedure.
9.2.1.2.1b.3 Test description
9.2.1.2.1b.3.1 Pre-test conditions
System Simulator:
- Cell A is configured according to Table 6.3.2.2-1 in [18].
- If pc_UTRAN supported by UE, Cell 5.
- If the UE does not support UTRAN and supports GERAN, Cell 24.
- Cell 24 belongs to LAI-1 and RAI-1(home PLMN)
UE:
- The UE is configured to initiate combined EPS/IMSI attach and to be voice centric (UE operates in CS/PS mode
1). If the UE does not support to be configured voice centric initiate combined EPS/IMSI attach and to be data
centric (UE operates in CS/PS mode 2).
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1232 Release 9
1232
9.2.1.2.1b.3.2 Test procedure sequence
Table 9.2.1.2.1b.3.2-1: Main Behaviour
U - S Message
The following messages are sent and shall
be received on cell A.

1 Set the cell type of cell A to the ''Serving
cell''.
Set the cell type of cell 5 or cell 24 to the ''
Non-Suitable cell ''.
- - - -
3 UE sends ATTACH REQUEST message
with a PDN CONNECTIVITY REQUEST
message to request PDN connectivity to the
default PDN. EPS attach type ="combined
EPS/IMSI attach".
6 The SS starts a NAS security mode
command procedure to perform NAS
integrity protection.
7 The UE responds properly to the NAS
security mode command procedure
- - - -
7Aa1 IF the UE sets the ESM information transfer
an ESM INFORMATION REQUEST
message to initiate exchange of protocol
7Aa2 The UE transmits an ESM INFORMATION
with the ACTIVATE DEFAULT EPS
BEARER CONTEXT REQUEST message.
COMPLETE message with the ACTIVATE
ACCEPT message?
supported

11a1 IF CS/PS mode 1 of operation is configured
on the UE THEN set the cell type of cell A to
the ''Serving cell'' and set the cell type of cell
5 or cell 24 to the ''Suitable neighbour cell ''.

11a2 The following messages are sent and shall
be received on Cell 5 or Cell 24.
- - - -
11a3 Check: Does the UE transmit an ROUTING
next 30 seconds?
--> ROUTING AREA UPDATE
REQUEST
2 P
11a4 The SS transmits a ROUTING AREA
<-- ROUTING AREA UPDATE
ACCEPT
- -
11a5 The UE transmits a ROUTING AREA
COMPLETE
- -
11a6 The SS releases the RRC connection. - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1233 Release 9
1233
11b1 ELSE no change cell configuration.
11b2 Check: Does the UE respond to paging on
cell A with S-TMSI in GUTI-2 for PS
domain?(Generic Procedure TS36.508
6.4.2.4)
- - 3 -
11b3 The SS transmits a paging on cell A with S-
- - - -
11b4 Check: Does the UE send EXTENDED
--> EXTENDED SERVICE REQUEST 4 F

9.2.1.2.1b.3.3 Specific message contents
Table 9.2.1.2.1b.3.3-1: Message ATTACH REQUEST (step 3, Table 9.2.1.2.1b.3.2-1)
Derivation path: 36.508 table 4.7.2.-4
EPS/IMSI attach''


Table 9.2.1.2.1b.3.3-2: Message ATTACH ACCEPT (step 8, Table 9.2.1.2.1b.3.2-1)
Derivation path: 36.508 table xxx
EPS/IMSI attach''

EPS network feature support '0000 0000'B IMS voice over PS
session in S1
mode NOT
supported

Additional update result '10'B0000 SMS only

9.2.1.2.1c Combined attach procedure / Success / EPS and CS Fallback not preferred
9.2.1.2.1c.1 Test Purpose (TP)
(1)
with { UE operating in CS/PS mode 1 in state EMM-REGISTERED-INITIATED}
ensure that {
when { UE receives ATTACH ACCEPT message with EPS network feature support IE indicating that
IMS voice over PS session in S1 mode NOT supported and Additional update result IE indicating
CS Fallback not preferred}
then { UE attempts to register on UTRAN cell and disables its E-UTRAN capability.}
}

(2)
with { UE operating in CS/PS mode 1 in OFF state after having its E-UTRAN capability disabled}
ensure that {
when { UE is switched on }
then { UE re-enables its E-UTRA capability and registers on the E-UTRAN cell}
}

9.2.1.2.1c.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 4.3.1,
4.5 and 5.5.1.3.4.2.
[TS 24.301 clause 4.3.1]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1234 Release 9
1234
The behaviour of the UE in CS/PS mode 1 of operation, upon failure to access the CS domain or upon reception of a
"CS fallback not preferred" or "SMS only" indication, will depend on the availability of voice over IMS. In the present
document, "IMS voice not available" refers to one of the following conditions:
- the UE is not configured to use IMS;
- the UE is not configured to use IMS voice, i.e. when the voice domain preference for E-UTRAN, as defined in
3GPP TS 24.167 [13B], indicates that voice communication services are allowed to be invoked only over the CS
domain;
- the UE is configured to use IMS voice, but the network indicates in the ATTACH ACCEPT message or the
TRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions are not supported; or
- the UE is configured to use IMS voice, the network indicates in the ATTACH ACCEPT message or the
TRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions are supported, but the upper
layers indicate that the UE is not available for voice calls in the IMS.
[TS 24.301 clause 4.5]
The UE shall enable the E-UTRA capability again in the following cases:
- the UE mode of operation changes from CS/PS mode 1 of operation to CS/PS mode 2 of operation;
- the UE mode of operation changes from PS mode 1 of operation to PS mode 2 of operation;
- the UE powers off and powers on again; or
- for the PLMN selection purpose.
[TS 24.301 clause 5.5.1.3.4.2]
If the ATTACH ACCEPT message includes the Additional update result IE with value "SMS only" or "CS Fallback not
preferred", a UE operating in CS/PS mode 1 with "IMS voice not available" shall attempt to select GERAN or UTRAN
radio access technology rather than E-UTRAN for the selected PLMN or equivalent PLMN. The UE shall disable the E-
UTRA capability (see subclause 4.5). If the UE is in the EMM-CONNECTED mode, the UE shall locally release the
established NAS signalling connection and enter the EMM-IDLE mode before selecting GERAN or UTRAN radio
access technology.
If the ATTACH ACCEPT message includes the Additional update result IE with value "SMS only", a UE operating in
CS/PS mode 2 shall not attempt to use CS fallback for mobile originating services.
If the ATTACH ACCEPT message includes the Additional update result IE with value "CS Fallback not preferred", this
indicates to a UE operating in CS/PS mode 2 that it is attached for EPS and non-EPS services and that it can use CS
fallback.
9.2.1.2.1c.3 Test description
9.2.1.2.1c.3.1 Pre-test conditions
System Simulator:
- cell 1 and cell 5
UE:
- the UE is configured to be voice centric

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1235 Release 9
1235
Table 9.2.1.2.1c.3.11: USIM configuration
technology
Comment
EF
PLMNwAcT
3GPP TS 31.102,
Annex E
The EF is empty.
EF
OPLMNwAcT
1 PLMN2 E-UTRAN
2 PLMN2 UTRAN

Preamble:
9.2.1.2.1c.3.2 Test procedure sequence
Table 9.2.1.2.1c.3.2-1: Cell PLMN identities
Cell PLMN name
A PLMN2
5 PLMN2

Table 9.2.1.2.1c.3.2-2: instances of cell power level and parameter changes
Parameter
name
Unit Cell A Cell 5
T0 RS EPRE dBm/15kHz Serving cell
CPICH_Ec dBm/3.84 MHz Suitable cell
P-CCPCH dBm/1.28 MHz Suitable cell

Table 9.2.1.2.1c.3.2-3: Main Behaviour
U - S Message
- The following messages are to be
observed on Cell A unless explicitly
stated otherwise.
- - - -
2-16 Steps 2-16 of the registration procedure
described in TS 36.508 table 4.5.2.3-1
are performed.
- -
17 Check: Does the UE send RRC
18-26 Steps 2-10 of the test procedure as
described in table 6.4.2.8-1 of TS 36.508
are performed.
- -
- The UE is switched off then turned back
on again.
- - - -
RRCConnectionRequest on Cell A?
28-43 Steps 2-17 of the registration procedure
described in TS 36.508 table 4.5.2.3-1
are performed.
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1236 Release 9
1236
9.2.1.2.1c.3.3 Specific message contents
Table 9.2.1.2.1c.3.3-1: Message ATTACH ACCEPT (step 14, Table 9.2.1.2.1c.3.2-3)
EPS/IMSI attach''

ESM message container Empty There is no
message
piggypacked in it.

session in S1
mode NOT
supported

Additional update result 01b CS Fallback not
preferred

9.2.1.2.2 Combined attach procedure / Success / EPS services only / IMSI unknown in
HSS
(1)
with { UE in state EMM-DEREGISTERED and is switched off }
ensure that {
when { the UE is powered up or switched on }
then { the UE transmits an ATTACH REQUEST message with the EPS attach type set to "combined
EPS/IMSI attach" and enters EMM-REGISTERED-INITIATED state }
}
(2)
with { UE in state EMM-REGISTERED-INITIATED }
ensure that {
when { the UE receives an ATTACH ACCEPT message with EPS attach result set to "EPS only" and EMM
cause set to "IMSI unknown in HSS" }
then { the UE transmits an ATTACH COMPLETE message, the UE set the update status to U3 ROAMING
NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and enters EMM-
REGISTERED.NORMAL-SERVICE state and MM IDLE state. The USIM shall be considered as invalid for non-
EPS services until switching off or the UICC containing the USIM is removed }
}
(3)
with { UE in E-UTRA EMM-REGISTERED.NORMAL-SERVICE state and MM IDLE state and USIM is invalidated by
network for non-EPS services }
ensure that {
when { SS sends DETACH REQUEST message with the Detach type IE "re-attach required" }
then { the UE sends DETACH ACCEPT message, and then the UE sends ATTACH REQUEST message with EPS
attach type set to 'EPS attach', including the value in 'Last visited registered TAI' and the valid
GUTI and initiates an attach procedure }
}
(4)
with { UE in EMM-REGISTERED.NORMAL-SERVICE state and MM IDLE state and USIM is invalidated by
network for non-EPS services }
ensure that {
when { the UE is switch off and then powered up or switched on }
then { the UE sends ATTACH REQUEST message with EPS attach type IE 'combined EPS/IMSI attach' }
}
(5)
ensure that {
when { the UE receives ATTACH ACCEPT message with EPS attach result 'combined EPS/IMSI attach' }
then { UE sends ATTACH COMPLETE message and enters EMM-REGISTERED.NORMAL-SERVICE state and MM
IDLE state }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1237 Release 9
1237

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 4.3, 5.5.1.2.2,
5.5.1.2.4, 5.5.1.3.1, 5.5.1.3.2, 5.5.1.3.4.1, 5.5.1.3.4.2, and 5.5.1.3.4.3.
[TS24.301 clause 4.3]
A UE attached for EPS services may operate in one of the following operation modes:
...
- CS/PS mode 1 of operation: the UE registers to both EPS and non-EPS services, and UE's usage setting is "voice
centric"; and
- CS/PS mode 2 of operation: the UE registers to both EPS and non-EPS services, and UE's usage setting is "data
centric" or the UE has no CS voice capability.
A UE configured to use CS fallback, shall operate in CS/PS mode 1 or CS/PS mode 2. Such UE may also be configured
to use IMS, in which case the voice domain preference as defined in 3GPP TS 24.167 [13B] shall be used for the
selection of the domain for originating voice communication services.
...
[TS 24.301, clause 5.5.1.2.2]

message.
...
[TS 24.301, clause 5.5.1.2.4]
start timer T3450. The MME shall send the ATTACH ACCEPT message together with an ACTIVATE DEFAULT EPS
...
or the MME considers the GUTI provided by the UE is invalid, or the GUTI provided by the UE was assigned by
another MME, the MME shall allocate a new GUTI to the UE. The MME shall include in the ATTACH ACCEPT
message the new assigned GUTI together with the assigned TAI list. In this case the MME shall enter state EMM-
COMMON-PROCEDURE-INITIATED as described in subclause 5.4.1.
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1238 Release 9
1238
ACCEPT message.
...
network.
Additionally, the UE shall reset the attach attempt counter and tracking area updating attempt counter, enter state EMM-
REGISTERED and set the EPS update status to EU1 UPDATED.

Upon receiving an ATTACH COMPLETE message, the MME shall stop timer T3450, enter state EMM-REGISTERED
and consider the GUTI sent in the ATTACH ACCEPT message as valid.
[TS 24.301, clause 5.5.1.3.1]
and non-EPS services.
attach type IE.
[TS 24.301, clause 5.5.1.3.2]
message.
[TS 24.301, clause 5.5.1.3.4.1]
...
2) The EPS attach result IE value indicates "EPS only": attach for EPS services has been successful but attach for
non-EPS services has failed.
[TS 24.301, clause 5.5.1.3.4.2]
...
[TS 24.301, clause 5.5.1.3.4.3]
Apart from the actions on the tracking area updating attempt counter, the description for attach for EPS services as
specified in subclause 5.5.1.2.4 shall be followed. In addition, the following description for attach for non-EPS services
applies.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1239 Release 9
1239
The UE receiving the ATTACH ACCEPT message takes one of the following actions depending on the EMM cause
value:
#2 (IMSI unknown in HSS)
The UE shall stop T3410 if still running and shall reset the tracking area updating attempt counter. The UE
shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering
key sequence number. The UE shall enter state EMM-REGISTERED.NORMAL-SERVICE. The new MM
state is MM IDLE. The USIM shall be considered as invalid for non-EPS services until switching off or the
UICC containing the USIM is removed.
...
Other EMM cause values and the case that no EMM cause IE was received are considered as abnormal cases. The
combined attach procedure shall be considered as failed for EPS and non-EPS services. The behaviour of the UE in
those cases is specified in subclause 5.5.1.3.6.
[TS 24.301, clause 5.5.2.3.2]
When receiving the DETACH REQUEST message and the detach type indicates "re-attach required", the UE shall
deactivate the EPS bearer context(s) including the default EPS bearer context locally without peer-to-peer signalling
between the UE and the MME. The UE shall then send a DETACH ACCEPT message to the network and enter state
EMM-DEREGISTERED. Furthermore, the UE shall, after the completion of the detach procedure, and the existing
NAS signalling connection has been released, initiate an attach or combined attach or combined attach procedure
NOTE 1: When detach type indicates "re-attach required", user interaction is necessary in some cases when the UE
cannot re-activate the EPS bearer(s) automatically.
A UE which receives a DETACH REQUEST message with detach type indicating "re-attach required" or "re-attach not
required" and no EMM cause IE, is detached only for EPS services.

If the detach type indicates "IMSI detach" or "re-attach required", then the UE shall ignore the EMM cause IE if
received.
System Simulator:
- Cell A.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1240 Release 9
1240
U - S Message
1 The UE is powered up or switched on. - - - -
2 The UE transmits ATTACH REQUEST
connectivity to the default PDN with EPS
attach type set to "combined EPS/IMSI attach"
authentication.
- - - -
6A
a1
options and/or APN.
6A
a2
7 The SS transmits ATTACH ACCEPT message
with EPS Attach result IE set to EPS only and
EMM cause set to "IMSI unknown in HSS",
including the ACTIVATE DEFAULT EPS
BEARER CONTEXT REQUEST message as
specified.

- - - -
10 -
12
Void

13 The SS sends DETACH REQUEST message
with Detach Type set to "re-attach required"
message?
- EXCEPTION: Step 15a describes a behaviour
which depends on the UE capability
- - - -
15a IF NOT pc_Automatic_Re_Attach, the user
initiates an attach by MMI or by AT command.
- - - -
REQUEST message with EPS attach type set
to EPS attach, including the PDN

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1241 Release 9
1241
17 The SS sends ATTACH ACCEPTmessage
including the ACTIVATE DEFAULT EPS
BEARER CONTEXT REQUEST message
- - - -
COMPLETE message?
- - - -

--> DETACH REQUEST
USIM is inserted.
- - - -
21 Check: Does the UE transmits ATTACH
to "combined EPS/IMSI attach", including PDN
22 The SS transmits ATTACH ACCEPT message
with EPS Attach result IE set to combined
EPS/IMSI attach , including the ACTIVATE
REQUEST message.
- - - -
COMPLETE message including the
CONTEXT ACCEPT message?
- - - -

NOTE: It is assumed in the test procedure sequence that the UE initially has a valid GUTI, hence it is included in
ATTACH REQUEST message in step 2. However, it is not important for the test procedure sequence.
EPS attach type 010 combined
EPS/IMSI attach

REQUEST message


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1242 Release 9
1242
EPS attach result 001 "EPS only"

The SS accepts
Combined attach
for EPS services
only.

ESM message container ACTIVATE DEFAULT
EPS BEARER
CONTEXT REQUEST
message

GUTI GUTI-2 The SS assigns a
new GUTI

LAI Not present
MS identity Not Present No TMSI is
assigned

EMM cause 00000010 #2 IMSI unknown
in HSS

Detach type 001 "re-attach
required"

EPS attach type 001 EPS attach
REQUEST message

Old location area identification Not present

EPS attach result 001 '' EPS only ''
EPS BEARER
CONTEXT REQUEST
message

GUTI Not present The SS doesnt
assign a new
GUTI

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1243 Release 9
1243
EPS attach type 010 combined
EPS/IMSI attach

REQUEST message

available

EPS attach result 010 ''Combined
EPS/IMSI attach''

EPS BEARER
CONTEXT REQUEST
message

assign a new
GUTI

9.2.1.2.3 Successful combined attach procedure / EPS service only / MSC temporarily not
reachable
(1)
with { the UE has sent a combined ATTACH REQUEST message }
ensure that {
when { the UE receives an ATTACH ACCEPT message with EPS attach result set to "EPS only" and EMM
reject cause set to "MSC temporarily not reachable" or "Network failure" or "Congestion" and
including an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity
matching the ATTACH REQUEST message and including a PDN address, an APN and an uplink TFT }
then { UE transmits an ATTACH COMPLETE message, containing the EPS bearer identity, together
with ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and the UE resets the attach attempt counter
and tracking area updating attempt counter and the UE increments tracking area updating attempt
counter and starts timer T3411 and enters EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM state }
}
(2)
with { the UE is in E-UTRA EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM state }
ensure that {
when { timer T3411 expires or timer T3402 expires }
then { the UE initiates a combined tracking area update procedure indicating "combined TA/LA
updating with IMSI attach" }
}
(3)
with { the UE is in E-UTRA EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM state }
ensure that {
when { UE receives a TRACKING AREA UPDATE ACCEPT with EPS update result set to "EPS only" and EMM
reject cause set to "MSC temporarily not reachable" or "Network failure" or "Congestion" }
then { UE increments tracking area updating attempt counter unless it was already set to 5 and
starts timer T3411 if tracking area updating attempt counter is less than 5 or starts timer T3402 if
tracking area updating attempt counter is equal to 5 }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1244 Release 9
1244
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.5.1.2.4,
5.5.1.3.1, 5.5.1.3.2, 5.5.1.3.4.1, 5.5.1.3.4.2, 5.5.1.3.4.3, and 5.5.3.3.4.3.
[TS 24.301, clause 5.5.1.2.4]
If the attach request is accepted by the network, the MME shall delete the stored UE radio capability information, if any.
If the UE has included the UE network capability IE or the MS network capability IE or both in the ATTACH
REQUEST message, the MME shall store all octets received from the UE, up to the maximum length defined for the
respective information element.
NOTE: This information is forwarded to the new MME during inter-MME handover or to the new SGSN during
inter-system handover to A/Gb mode or Iu mode.

ACCEPT message.

network.

[TS 24.301, clause 5.5.1.3.1]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1245 Release 9
1245
attach type IE.
[TS 24.301, clause 5.5.1.3.2]
message.
[TS 24.301, clause 5.5.1.3.4.1]
[TS 24.301, clause 5.5.1.3.4.2]

[TS 24.301, clause 5.5.1.3.4.3]
applies.
value:

#16 (MSC temporarily not reachable);
#17 (Network failure); or
#22 (Congestion)
The UE shall stop timer T3410 if still running. The tracking area updating attempt counter shall be
incremented, unless it was already set to 5.
If the tracking area updating attempt counter is less than 5:
- the UE shall start timer T3411, shall set the EPS update status to EU1 UPDATED and shall enter state
EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3411 expires the combined
tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered.
If the tracking area updating attempt counter is equal to 5:
- a UE operating in CS/PS mode 2 of operation shall start timer T3402, shall set the EPS update status to
EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When
timer T3402 expires the combined tracking area updating procedure indicating "combined TA/LA
updating with IMSI attach" is triggered;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1246 Release 9
1246
- a UE operating in CS/PS mode 1 of operation with "IMS voice not available" shall attempt to select
GERAN or UTRAN radio access technology and proceed with appropriate MM or GMM specific
procedures. The UE shall disable the E-UTRA capability (see subclause 4.5). If the UE is in the EMM-
CONNECTED mode, the UE shall locally release the established NAS signalling connection and enter
the EMM-IDLE mode before selecting GERAN or UTRAN radio access technology.
NOTE 1: It is up to the UE implementation when to enable E-UTRAN radio access technology selection.

[TS 24.301, clause 5.5.3.3.4.3]
Apart from the actions on the tracking area updating attempt counter, the description for tracking area for EPS services
as specified in subclause 5.5.3.2.4 shall be followed. In addition, the following description for location updating for
non-EPS services applies.
The UE receiving the TRACKING AREA UPDATE ACCEPT message takes one of the following actions depending
on the EMM cause value:

#22 (Congestion)
tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered
again.
updating with IMSI attach" is triggered again;
NOTE 1: It is up to the UE implementation when to enable E-UTRAN radio access technology selection.

System Simulator:
- cell A.
Note: T3402 is set to default (12 min.).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1247 Release 9
1247
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1248 Release 9
1248
The sequence is executed for execution counter k =1, 2, 3.
U - S Message
2 The UE transmit a combined ATTACH
specified.
authentication.
- - - -
6A
a1
options and/or APN.
6A
a2
message with EPS attach result indicating
"EPS only" and MM cause indicating according
to specific message contents and with IE EPS
Bearer Identity set to default EPS bearer
context. The ACTIVATE DEFAULT EPS
piggybacked in ATTACH ACCEPT.

Note 1: SS allocates a PDN address of a PDN
type which is compliant with from the PDN type
- - - -
10 Check1: Does the UE transmit a TRACKING
AREA UPDATE REQUEST message with
"combined TA/LA updating with IMSI attach"?
Check2: Is the time between the previous
ATTACH ACCEPT and TRACKING AREA
UPDATE REQUEST equal to T3411?

REQUEST
1,2 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1249 Release 9
1249
Note: Tracking area updating attempt
counter=2
11 SS transmits a TRACKING AREA UPDATE
ACCEPT message with EPS update result
indicating "TA updated" and MM cause
indicating according to specific message
contents.
ACCEPT
- -
TRACKING AREA UPDATE ACCEPT and
TRACKING AREA UPDATE REQUEST equal
to T3411?

counter=3
REQUEST
2,3 P
contents.
ACCEPT
- -
to T3411?

counter=4
REQUEST
2,3 P
contents
ACCEPT
- -
to T3411?

counter=5
REQUEST
2,3 P
contents.
ACCEPT
- -
18 Check1: Does the UE send TRACKING AREA
UPDATE REQUEST message with "combined
TA/LA updating with IMSI attach"?
to T3402?

counter=5
REQUEST
2,3 P
indicating " combined TA/LA updated "
according to default message contents.
ACCEPT
- -
20 Check: Does the result of test procedure in
36.508 clause 6.4.2.3 indicate that the UE
- - 3 -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1250 Release 9
1250
answer to paging with S-TMSI-1 (associated
with GUTI-1) for PS domain?
to TS 36.508.
- - - -

EPS attach type 010 "combined
EPS/IMSI attach"


GUTI Not present
Location area identification Not present SS doesnt
provide LAI

MS identity Not Present

SS doesnt
provide TMSI

EMM cause 00010000 for k=1or
00010001 for k=2 or
00010110 for k=3
#16 (MSC
temporarily not
reachable) for k=1
#17 (Network
failure) for k=2
#22 (Congestion)
for k=3

Table 9.2.1.2.3.3.3-3: Message TRACKING AREA UPDATE REQUEST (steps 10-12-14-16-18, Table
9.2.1.2.3.3.2-1)
EPS update type 010 "combined TA/LA
updating with IMSI
attach"

Old GUTI GUTI-1
Old P-TMSI signature Not present This IE is included
when the UE
holds a valid P-
TMSI signature.

Additional GUTI Not present TIN ='GUTI'

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1251 Release 9
1251
Table 9.2.1.2.3.3.3-4: Message TRACKING AREA UPDATE ACCEPT (steps 11-13-15-17, Table
9.2.1.2.3.3.2-1)
EPS update result 000 "TA updated"
SS accepts
Combined TAU
for EPS services
only.

GUTI Not present
provide LAI


SS doesnt
provide TMSI

EMM cause 00010000 for k=1 or
00010001 for k=2 or
00010110 for k=3
#16 (MSC
temporarily not
reachable) for k=1
#17 (Network
failure) for k=2
#22 (Congestion)
for k=3

9.2.1.2.4 Successful combined attach procedure / EPS service only / CS domain not
available
(1)
with { UE is switched-off }
ensure that {
when { UE is powered on and a valid GUTI is available }
then { the UE transmits an ATTACH REQUEST message with the EPS attach type set to "combined
EPS/IMSI attach", including GUTI, last visited registered TAI and a PDN CONNECTIVITY REQUEST message
with the request type set to "initial attach" }
}
(2)
with { UE has sent a combined ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message }
ensure that {
when { UE receives an ATTACH ACCEPT message including EPS attach result set to "EPS only" and EMM
reject cause set to "CS domain not available" and including an ACTIVATE DEFAULT EPS BEARER CONTEXT
REQUEST message with IE EPS Bearer Identity matching the PDN CONNECTIVITY REQUEST message }
then { UE transmits ATTACH COMPLETE message, containing the EPS bearer identity, including an
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and sets the update status to U2 NOT UPDATED and
enters EMM-REGISTERED state }
}
(3)
with { The UE received an ATTACH ACCEPT message with EPS attach result set to "EPS only" and EMM
cause set to "CS domain not available" }
ensure that {
when { UE enters a TA where it is not registered and which belongs to the PLMN where the UE
received the EMM cause "CS domain not available" }
then { UE initiates a normal tracking area update procedure indicating "TA updating" without
valid LAI, TMSI, GSM ciphering key, UMTS integrity key, UMTS ciphering key or ciphering key sequence
number }
}
(4)
with { The UE received an ATTACH ACCEPT message with EPS attach result set to "EPS only" and EMM
cause set to "CS domain not available" }
ensure that {
when { UE is powered up or switched on }
then { UE initiates a combined attach procedure indicating "combined EPS/IMSI attach" }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1252 Release 9
1252

5.5.1.3.1, 5.5.1.3.2, 5.5.1.3.4.1, 5.5.1.3.4.2 and 5.5.1.3.4.3, and TS 24.008, clause 4.1.2.2.
[TS 24.301, clause 5.5.1.2.4]
If the attach request is accepted by the network, the MME shall delete the stored UE radio capability information, if any.
If the UE has included the UE network capability IE or the MS network capability IE or both in the ATTACH
REQUEST message, the MME shall store all octets received from the UE, up to the maximum length defined for the
respective information element.
NOTE: This information is forwarded to the new MME during inter-MME handover or to the new SGSN during
inter-system handover to A/Gb mode or Iu mode.
...
ACCEPT message.
...
network.

[TS 24.301, clause 5.5.1.3.1]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1253 Release 9
1253
attach type IE.
[TS 24.301, clause 5.5.1.3.2]
...
message.
[TS 24.301, clause 5.5.1.3.4.1]
[TS 24.301, clause 5.5.1.3.4.2]
...
[TS 24.301, clause 5.5.1.3.4.3]
applies.
value:
...
#18 (CS domain not available)
The UE shall stop timer T3410 if still running, shall reset the tracking area updating attempt counter, shall set
the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE.
The UE shall set the update status to U2 NOT UPDATED.
A UE in CS/PS mode 1 of operation with "IMS voice not available" shall attempt to select GERAN or
UTRAN radio access technology rather than E-UTRAN for the selected PLMN or equivalent PLMN. The
UE shall disable the E-UTRA capability (see subclause 4.5). If the UE is in the EMM-CONNECTED mode,
the UE shall locally release the established NAS signalling connection and enter the EMM-IDLE mode
before selecting GERAN or UTRAN radio access technology.
A UE in CS/PS mode 2 of operation may provide a notification to the user or the upper layers that the CS
domain is not available.

The UE shall not attempt combined attach or combined tracking area update procedure with current PLMN
until switching off the UE or the UICC containing the USIM is removed.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1254 Release 9
1254
[TS 24.008, clause 4.1.2.2]
In parallel with the sublayer states described in subclause 4.1.2.1 and which control the MM sublayer protocol, an
update status exists.
The update status pertains to a specific subscriber embodied by a SIM/USIM. This status is defined even when the
subscriber is not activated (SIM/USIM removed or connected to a switched-off ME). It is stored in a non volatile
memory in the SIM/USIM. The update status is changed only as a result of a location updating procedure attempt (with
the exception of an authentication failure and of some cases of CM service rejection). In some cases, the update status is
changed as a result of a GPRS attach, GPRS routing area update, service request or network initiated GPRS detach
procedure.
...
U2 NOT UPDATED
The last location updating attempt made failed procedurally (no significant answer was received from the
network, including the cases of failures or congestion inside the network).
For this status, the SIM/USIM does not contain any valid LAI, TMSI, GSM ciphering key, UMTS integrity
key, UMTS ciphering key or ciphering key sequence number. For compatibility reasons, all these fields must
be set to the "deleted" value at the moment the status is set to NOT UPDATED. However the presence of
other values shall not be considered an error by the mobile station. The "Location update status" stored on the
SIM/USIM shall be "not updated".
...
System Simulator:
- cell A (TAI-1, home PLMN) and cell B (TAI-2, home PLMN).
UE:
- Preamble:
- the UE is in state Switched OFF (state 1) according to TS.36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1255 Release 9
1255
U - S Message
1 Set the cell type of cell A to the "Serving cell"
Set the cell type of cell B to the "Non-suitable
cell"
- - - -
- - - -
3 Check : Does the UE transmit a combined
ATTACH REQUEST message including a
PDN CONNECTIVITY REQUEST message?
authentication.
- - - -
7A
a1
options and/or APN.
7A
a2
with IE EPS Bearer Identity set to default EPS
bearer context. The ACTIVATE DEFAULT
message is piggybacked in ATTACH
ACCEPT.

- - - -
11
state on Cell 1?
- - 2 -
12 Set the cell type of cell B to the "Serving cell"
Set the cell type of cell A to the "Non-suitable
cell"
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1256 Release 9
1256
13 Check: Does the UE transmit TRACKING
REQUEST
3 P
ACCEPT message
ACCEPT
- -
15 UE sends TRACKING AREA UPDATE
COMPLETE
COMPLETE

- -
- - - -

--> DETACH REQUEST
USIM is inserted.
- - - -
18 Check : Does the UE transmit a combined
ATTACH REQUEST message including a
PDN CONNECTIVITY REQUEST message?
with IE EPS Bearer Identity set to default EPS
bearer context. The ACTIVATE DEFAULT
message is piggybacked in ATTACH
ACCEPT.
- - - -
according to TS 36.508 but attached for EPS
services only.
- - - -

EPS/IMSI attach"


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1257 Release 9
1257
GUTI Not Present
provide LAI


SS doesnt
provide TMSI

EMM cause 00010010 #18 "CS domain
not available"

EPS update type 000 TA updating
Old GUTI GUTI-1
Last visited registered TAI TAI-1 If available, the
last TAI is
included by UE
and will be used
to establish a
good list of TAIs in
subsequent
ATTACH
ACCEPT
message.

Old location area identification Not present Entering in U2
NOT UPDATED
state, UE deletes
LAI


EPS update result 000 "TA only"
GUTI GUTI-2
provide LAI


SS doesnt
provide TMSI

not available"

EPS/IMSI attach"

available

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1258 Release 9
1258
EPS attach result 010 ''Combined
EPS/IMSI attach''

GUTI GUTI-2
MS identity TMSI-2

9.2.1.2.5 Combined attach / Rejected / IMSI invalid
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'Illegal UE' }
then { UE deletes GUTI, last visited registered TAI and KSI and considers the USIM as invalid
for EPS services and non-EPS services and enters state EMM-DEREGISTERED }
}

(2)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'Illegal UE' }
then { UE deletes P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number, TMSI, LAI
and ciphering key sequence number }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.1.3.5 and
TS 24.008, clause 4.7.3.2.4.
[TS 24.301, clause 5.5.1.3.5]
Upon receiving the ATTACH REJ ECT message, the UE shall stop timer T3410, enter MM state MM IDLE, and take
the following actions depending on the EMM cause value received.
#3 (Illegal UE);

subclause5.1.3.3) and shall delete any GUTI, last visited registered TAI and eKSI.
The UE shall consider the USIM as invalid for EPS and non-EPS services until switching off or the UICC
containing the USIM is removed. Additionally, the UE shall delete the list of equivalent PLMNs and shall enter
the state EMM-DEREGISTERED.
3GPP TS 24.008 [13] for the case when the combined attach procedure is rejected with the GMM cause with the
same value.
[TS 24.008, clause 4.7.3.2.4]
#3 (Illegal MS);
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1259 Release 9
1259
System Simulator:
- cell A and cell B;
- if pc_UTRAN, cell 5 (, LAI-1 and RAI-1;home PLMN) ; system information combination 9 as defined in TS
36.508[18] clause 4.4.3.1 is used in E-UTRA cells;
- if pc_GERAN and NOT pc_UTRAN, Cell 24 (, LAI-1 and RAI-1.home PLMN) ; system information
combination 12 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;

UE:
- if pc_GERAN or pc_UTRAN (respectively if pc_GERAN and NOT pc_UTRAN), the UE is previously
registered on UTRAN (respectively GERAN), and when on UTRAN (respectively GERAN), the UE is last
registered on cell 5 (respectively cell 24) using default message contents according to TS 36.508 [18].
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1260 Release 9
1260
U - S Message
- Cell A as the "Serving cell",
- Cell B as a "Non-Suitable cell",
- Cell 5 or Cell 24 as a "Non-Suitable cell".
- - - -
- - - -
REQUEST message.
message with the EMM cause set to 'Illegal
UE'.
- - - -
Cell B or on Cell A?
supported
- - - -
8a1 IF pc_UTRAN or pc_GERAN THEN the SS
configures:
- Cell 5 or Cell 24 as the "Serving cell".
- - - -
Cell 5 or Cell 24 unless explicitly stated
otherwise.
- - - -
8a2 Void - - - -
8a3 Check: Does the UE transmit an ATTACH
8a4 If possible (see ICS) switch off is performed or
- - - -
8a5 The UE is brought back to operation or the
USIM is inserted.
- - - -
REQUEST message?
Otherwise the power is removed. (Note 1)
(Note 2)
- - - -
- - - -
- - - -
USIM is inserted.
- - - -
REQUEST message?
13-
14
Void - - - -
15a1
-
15a9
Void - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1261 Release 9
1261
16-
27
- - - -
- - - -
Note 1: To make UEs behaviour more predictable, UE is switched off or USIM is removed without receiving the
response of ATTACH REQUEST message in step 8a6.
Note 2: Switching off, USIM removal, or power removal shall be done before T3310 and T3311 expire (30 seconds)
so that the UE does not retransmit ATTACH REQUEST message.

EMM cause '0000 0011'B Illegal UE

TSC Any allowed value TSC does not
apply for NAS key
set identifier value
"111".

TMSI status '0'B no valid TMSI
available

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1262 Release 9
1262
Derivation Path: TS 24.008 , Table 9.4.1
MS network capability Any allowed value
Attach type '011'B Combined
GPRS/IMSI attach

GPRS ciphering key sequence number '111'B No key is
available (MS to
network)

DRX parameter Any allowed value
Old routing area identification All bits of octets 5 and 6
are set to 1, except bit 1
of octet 6 which is set to
0.
Other bits are not
checked.

MS Radio Access capability Any allowed value
value
Not present or any
allowed value

available

PS LCS Capability Not present or any
allowed value

Mobile station classmark 2 Not present or any
allowed value

allowed value

Supported Codecs Not present or any
allowed value

UE network capability Not present or any
allowed value


9.2.1.2.6 Combined attach / Rejected / Illegal ME
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'Illegal ME' }
}

(2)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'Illegal ME' }
}

TS 24.008, clause 4.7.3.2.4.
[TS 24.301, clause 5.5.1.3.5]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1263 Release 9
1263

#6 (Illegal ME); or

same value.
[TS 24.008, clause 4.7.3.2.4]
...
#6 (Illegal ME), or
...
System Simulator:
- if pc_UTRAN, cell 5 (LAI-1 and RAI-1, home PLMN); system information combination 9 as defined in TS
36.508[18] clause 4.4.3.1 is used in E-UTRA cells;
- if pc_GERAN and NOT pc_UTRAN, cell 24 (LAI-1 and RAI-1, home PLMN) ; system information
UE:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1264 Release 9
1264
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1265 Release 9
1265
U - S Message
- - - -
- - - -
REQUEST message.
ME'.
- - - -
8-9 Void - - - -
supported
- - - -
configures:
- - - -
otherwise.
- - - -
10a2 Void - - - -
10a4
-
10a5
Void - - - -
- - - -
USIM is inserted.
- - - -
REQUEST message?
(Note 2)
- - - -
- - - -
- - - -
USIM is inserted.
- - - -
REQUEST message?
15- Void - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1266 Release 9
1266
16
17a1
-
17a9
Void - - - -
18-
29
- - - -
- - - -

EMM cause '0000 0110'B Illegal ME

apply for NAS key
"111".

available

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1267 Release 9
1267
GPRS/IMSI attach

available (MS to
network)

0.
Other bits are not
checked.

value
Not present or any
allowed value

available

allowed value

allowed value

allowed value

allowed value

allowed value


9.2.1.2.7 Combined attach / Rejected / EPS services and non-EPS services not allowed
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'EPS services and non-EPS
services not allowed' }
}

(2)
with { UE has sent an ATTACH REQUEST }
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'EPS services and non-EPS
services not allowed' }
}

TS 24.008, clause 4.7.3.2.4.
[TS 24.301, clause 5.5.1.3.5]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1268 Release 9
1268

same value.
[TS 24.008, clause 4.7.3.2.4]
...
#8 (GPRS services and non-GPRS services not allowed);
System Simulator:
- if pc_UTRAN, cell 5 (home PLMN); system information combination 9 as defined in TS 36.508[18] clause
4.4.3.1 is used in E-UTRA cells;
- if pc_GERAN and NOT pc_UTRAN, cell 24 (home PLMN) ; system information combination 12 as defined in
TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;
UE:
- The UE is configured to initiate combined EPS/IMSI attach;
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1269 Release 9
1269
U - S Message
- - - -
- - - -
REQUEST message.
message with the EMM cause set to 'EPS
services and non-EPS services not allowed'.
- - - -
supported
- - - -
configures:
- - - -
otherwise.
- - - -
8a2 Void - - - -
- - - -
USIM is inserted.
- - - -
REQUEST message?
(Note 2)
- - - -
- - - -
- - - -
USIM is inserted.
- - - -
REQUEST message?
13-
14
Void - - - -
15a1
-
15a9
Void - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1270 Release 9
1270
16-
27
- - - -
- - - -

EMM cause '0000 1000'B EPS services and
non-EPS services
not allowed

apply for NAS key
"111".

available

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1271 Release 9
1271
GPRS/IMSI attach

available (MS to
network)

0.
Other bits are not
checked.

value
Not present or any
allowed value

available

allowed value

allowed value

allowed value

allowed value

allowed value


9.2.1.2.8 Combined attach / Rejected / EPS services not allowed
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "EPS services not
allowed" }
then { UE considers the USIM as invalid for EPS services and enters state EMM-DEREGISTERED and
UE does not attempt to attach on any other cell }
}

[TS 24.301, clause 5.5.1.3.5]
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and eKSI. The UE shall consider the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1272 Release 9
1272
USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed. Additionally,
the UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.
A UE which is not yet IMSI attached for non-EPS services shall select GERAN or UTRAN radio access
technology and perform an IMSI attach for non-EPS services, using the MM IMSI attach procedure as described
in 3GPP TS 24.008 [13]. The UE shall not reselect E-UTRAN radio access technology until switching off or the
A UE which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services in the
network. The UE shall select GERAN or UTRAN radio access technology and shall proceed with the
appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN
radio access technology until switching off or the UICC containing the USIM is removed.
NOTE: Some interaction is required with the access stratum to disable E-UTRAN cell reselection.
specified in 3GPP TS 24.008 [13] for the case when the combined attach procedure is rejected with the GMM
System Simulator:
- if pc_UTRAN, cell 5 (home PLMN) system information combination 9 as defined in TS 36.508[18] clause
4.4.3.1 is used in E-UTRA cells.
- if pc_GERAN and NOT pc_UTRAN, cell 24 (home PLMN) ; system information combination 12 as defined in
TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
- the UE is configured to initiate combined EPS/IMSI attach.
registered on cell 5 (respectively cell 24) using default message contents according to TS 36.508 [18]".
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1273 Release 9
1273
U - S Message
- Cell B as a "Suitable neighbour cell".
- Cell 5 or Cell 24 as a "Suitable neighbour
cell".
- - - -
- - - -
REQUEST message.
allowed" as specified.
supported
- - - -
6a1 IF pc_UTRAN or pc_GERAN THEN the
following messages are sent and shall be
received on cell 5 or Cell 24.
- - - -
6a2 Check: Does the UE transmit a LOCATION
UPDATING REQUEST message on Cell 5 or
Cell 24?
REQUEST
1 P
6a3 The SS transmits a LOCATION UPDATING
ACCEPT message with Location updating type
="IMSI attach" as specified in 3GPP TS
24.008.
- Cell A as the "Suitable neighbour cell".
- Cell B as the "Suitable neighbour cell".
- - - -
Cell A or on Cell B?
- - - -

EMM cause '0000 0111'B EPS services not
allowed

9.2.1.2.9 Combined attach / Rejected / PLMN not allowed
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "PLMN not allowed" }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1274 Release 9
1274
then { UE deletes the GUTI, the last visited registered TAI and KSI and UE deletes the list of
equivalent PLMNs and UE enters state EMM-DEREGISTERED.PLMN-SEARCH and UE stores the PLMN in the
"forbidden PLMN list" }
}

(2)
with { UE is switched off and a PLMN is stored in the "forbidden PLMN list" }
ensure that {
when { UE is powered on this PLMN }
then { UE does not attempt to attach on the cell }
}

(3)
with { UE in E-UTRA EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden PLMN
list" }
ensure that {
when { UE enters a PLMN which is not in the "forbidden PLMN list" }
then { UE attempts to attach on the cell }
}

[TS 24.301, clause 5.5.1.3.5]
...
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, and KSI, and reset the attach attempt
counter. The UE shall delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-
SEARCH.
The UE shall store the PLMN identity in the "forbidden PLMN list".
The UE shall perform a PLMN selection according to 3GPP TS 23.122 [6].
number and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the combined
attach procedure is rejected with the GMM cause with the same value and no RR connection exists.
...
System Simulator:
- cell I (belongs to TAI-9, visited PLMN) and cell G (belongs to TAI-7, another visited PLMN);
- if pc_UTRAN, cell 5 (belongs to RAI-1, same PLMN as cell I); system information combination 4 as defined in
- if pc_GERAN and NOT pc_UTRAN, cell 24 (belongs to RAI-1, same PLMN as cell I); system information
combination 5 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1275 Release 9
1275
UE:
- the "forbidden PLMN list" is empty.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1276 Release 9
1276
U - S Message
- Cell I as the "Serving cell".
- - - -
- - - -
REQUEST message.
message with EMM cause ="PLMN not
allowed".
- ATTACH REQUEST 1 F
- - - -
USIM is insertedThe UE is powered on or
switched on.
- - - -
supported
- - - -
configures:

Note: Cell I, Cell 5 and Cell 24 are in the same
PLMN.
- - - -
otherwise.
- - - -
9a2 Void - - - -
Cell I as a "Non-Suitable cell".
Cell G as the "Serving cell".
Cell 5 or Cell 24 as a "Non-Suitable cell".

Note: Cell G belongs to PLMN different from
PLMN belonging to Cell I.
- - - -
- - - -
specified?
12-
23
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1277 Release 9
1277
EMM cause '0000 1011'B PLMN not allowed

apply for NAS key
"111".

Old GUTI or IMSI IMSI1

9.2.1.2.10 Combined attach / Rejected / Tracking area not allowed
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "Tracking area not
allowed" }
then { UE deletes the GUTI, last visited registered TAI and KSI, UE enters the state EMM-
DEREGISTERED.LIMITED-SERVICE and UE stores the current TAI in the list of "forbidden tracking areas
}

(2)
tracking areas for regional provision of service" }
ensure that {
then { UE does not attempt to attach on any cell }
}

(3)
tracking areas for regional provision of service" }
ensure that {
when { UE re-selects a new cell in the same TAI it was rejected }
then { UE does not attempt to attach on the cell }
}

(4)
ensure that {
tracking areas for regional provision of service" before the UE was swithed off }
then { UE attempts to attach on the cell }
}


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1278 Release 9
1278
[TS 24.301, clause 5.5.1.3.5]
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI. The UE shall reset the attach
attempt counter and enter the state EMM-DEREGISTERED.LIMITED-SERVICE.
The UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service".
attach procedure is rejected with the GMM cause with the same value.
System Simulator:
- cell A, cell B and cell M.
- System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1279 Release 9
1279
U - S Message
- Cell B as a "Suitable neighbour cell".
- Cell M as a "Non-Suitable cell".
- - - -
- - - -
REQUEST message.
message with EMM cause ="Tracking area
not allowed".
Cell A or Cell B?
- ATTACH REQUEST 1,2 F
- Cell A as the "Non-Suitable cell".
- Cell M as a "Serving cell".
- - - -
Cell M?
- ATTACH REQUEST 3 F
Cell M unless explicitly stated otherwise.
- - - -
- - - -
USIM is inserted
- - - -
specified?
12-
23
- - - -
- - - -

EMM cause '0000 1100'B Tracking Area not
allowed

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1280 Release 9
1280
apply for NAS key
"111".


9.2.1.2.11 Combined attach / Rejected / Roaming not allowed in this tracking area
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to "Roaming not allowed in this
tracking area" }
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED and UE deletes the GUTI, the
last visited registered TAI and KSI and UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE or
optionally EMM-DEREGISTERED.PLMN-SEARCH and UE stores the current TAI in the list of "forbidden
tracking areas for roaming" and deletes the TMSI, the LAI and the ciphering key sequence number }
}
(2)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.PLMN-SEARCH state and the
current TAI is in the list of "forbidden tracking areas for roaming" }
ensure that {
when { UE re-selects a new cell in the same TA where it was rejected }
}

(3)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.PLMN-SEARCH state and the TAI
of the current cell belongs to the list of "forbidden tracking areas for roaming" }
ensure that {
when { UE enters a cell belonging to a tracking area not in the list of "forbidden tracking areas
for roaming" }
then { UE attempts to attach with IMSI }
}

(4)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.PLMN-SEARCH state and the list
of "forbidden tracking areas for roaming" contains more than one TAI }
ensure that {
when { UE selects a cell belonging to one of the TAIs in the list of "forbidden tracking areas for
roaming" }
}

(5)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to "Roaming not allowed in this
tracking area" }
then { UE deletes RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number and sets
the GPRS update status to GU3 ROAMING NOT ALLOWED }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1281 Release 9
1281
(6)
with { UE is switched off or the UICC containing the USIM is removed }
ensure that {
tracking areas for roaming" before UE was switched off or the USIM is inserted again on that cell }
}

(7)
with { a cell of the HPLMN is available }
ensure that {
when { UE performs a PLMN selection }
then { UE returns to a cell of the HPLMN }
}

5.5.1.3.5 and TS 24.008, clause 4.7.3.2.4.
[TS 24.301, clause 5.3.2]
USIM is removed, and periodically (with a period in the range 12 to 24 hours). One or more tracking areas is removed
from the list of "forbidden tracking areas for roaming" in the UE, as well as the list of "forbidden tracking areas for
regional provision of service" if, after a subsequent procedure e.g. attach procedure, tracking area updating procedure
and GUTI reallocation procedure, one or more tracking areas in the lists is received from the network.
shall be deleted.
[TS 24.301, clause 5.5.1.3.5]
If the attach request can neither be accepted by the network for EPS nor for non-EPS services, the MME shall send an
ATTACH REJECT message to the UE including an appropriate EMM cause value. If the attach procedure fails due to a
default EPS bearer setup failure or an ESM procedure failure, the MME shall combine the ATTACH REJ ECT message
with a PDN CONNECTIVITY REJ ECT message. In this case the EMM cause value in the ATTACH REJ ECT message
shall be set to #19, "ESM failure".
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI. The UE shall delete the list of
equivalent PLMNs and reset the attach attempt counter. Additionally the UE enter the state EMM-
DEREGISTERED.LIMITED-SERVICE or optionally EMM-DEREGISTERED.PLMN-SEARCH.
The UE shall store the current TAI in the list of "forbidden tracking areas for roaming".

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1282 Release 9
1282
...
[TS 24.008, clause 4.7.3.2.4]
If the attach request can neither be accepted by the network for GPRS nor for non-GPRS services, an ATTACH
REJ ECT message is transferred to the MS. The MS receiving the ATTACH REJ ECT message stops timer T3310, and
for all causes except #12, #14, #15 and #25 deletes the list of "equivalent PLMNs".
...
#13 (Roaming not allowed in this location area);
The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set
the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and
shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-
SERVICE or optionally to GMM-DEREGISTERED.PLMN-SEARCH.
The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt
counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE.
...
System Simulator:
- cell C (home PLMN);
- if pc_UTRAN, cell 5 (only active when stated):
- same PLMN like visited PLMN above;
- RAI-1 (RAC & LAC values chosen by SS);
- System information indicate that NMO 1 is used;
- if pc_GERAN and NOT pc_UTRAN, cell 24 (only active when stated):
- RAC-1 (RAC & LAC values chosen by SS);
- at most two cells are simultaneously active.
NOTE 1: Cell K is present to confirm that UE does not attempt attach to the cell in same TAI after reject from the
SS.
NOTE 2: Cell C is present to confirm that UE does attempt attach to the cell in HPLMN after reject from the SS.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1283 Release 9
1283
run the test.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1284 Release 9
1284
U - S Message
Cell K as a "Non-Suitable cell",
Cell L as a "Non-Suitable cell",
Cell C as a "Non-Suitable cell".
- - - -
- - - -
REQUEST message.
message with the EMM cause set to "Roaming
not allowed in this tracking area" on Cell I.
Cell I?
Cell I as a "Suitable cell",
- - - -
any cell?
Cell I as a "Non-Suitable cell",
Cell K as a "Suitable cell",
Cell L as the "Serving cell",
- - - -
L?
not allowed in this tracking area" on Cell L.
roaming" in the UE should now contain TAI-9
and TAI-11)
Cell L or Cell K?
Cell I as a "Serving cell",
Cell K as a " Non-Suitable cell",
Cell L as a "Suitable cell",
Cell C as the "Non-Suitable cell".
- - - -
any cell?
supported
- - - -
reconfigures:
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1285 Release 9
1285
Cell I as "Serving cell",
Cell K as "Non-suitable cell",
Cell 5 or Cell 24 as "Suitable cell".
REQUEST message without P-TMSI, P-TMSI
signature, RAI, TMSI on Cell 5 or Cell 24?
16a3 The SS transmits an ATTACH REJ ECT
message with the GMM cause set to "Roaming
not allowed in this location area" on Cell 5 or
Cell 24.
- - - -
- - - -
USIM is inserted.
- - - -
REQUEST message on Cell I.
not allowed in this tracking area" on Cell I.
Cell C as a "Suitable cell".
- - - -
- - - -
24-
35
- - - -
- - - -

Table 9.2.1.2.11.3.3-1: Message ATTACH REJECT (step 4, step 11 and step 21, Table 9.2.1.2.11.3.2-1)
EMM cause '0000 1101'B Roaming not
allowed in this
tracking area

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1286 Release 9
1286
Table 9.2.1.2.11.3.3-2: Message ATTACH REQUEST (step 10, step 20 and step23, Table 9.2.1.2.11.3.2-
1)
apply for NAS key
"111".

available

GPRS/IMSI attach

available (MS to
network)

0.
Other bits are not
checked.

value
Not present or any
allowed value

available

allowed value

allowed value

allowed value

allowed value

allowed value


Table 9.2.1.2.11.3.3-4: Message ATTACH REJECT (step 16a3, Table 9.2.1.2.11.3.2-1)
GMM cause '0000 1101'B Roaming not
allowed in this
location area

T3302 value Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1287 Release 9
1287
9.2.1.2.12 Combined attach / Rejected / EPS services not allowed in this PLMN
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "EPS services not allowed
in this PLMN" }
then { UE stores the PLMN identity in the "forbidden PLMNs for GPRS service" list and deletes
any GUTI, last visited registered TAI, KSI and enters EMM-DEREGISTERED.PLMN-SEARCH state}
}

(2)
for GPRS service" list }
ensure that {
when { UE detects a cell which belongs to a PLMN which is not in the "forbidden PLMNs for GPRS
service" list }
}

(3)
with { UE is switched off when a PLMN is stored in the "forbidden PLMNs for GPRS service" list }
ensure that {
when { UE is powered on in a cell which belongs to this PLMN }
}

[TS 24.301, clause5.5.1.3.5]
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI. Additionally the UE shall
reset the attach attempt counter and enter the state EMM-DEREGISTERED.PLMN-SEARCH.
The UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list.
A UE operating in CS/PS mode 1 which is not yet IMSI attached for non-EPS services may select GERAN or
UTRAN radio access technology and perform an IMSI attach for non-EPS services, using the MM IMSI attach
procedure as described in 3GPP TS 24.008 [13]. In this case the UE shall not reselect E-UTRAN radio access
technology for the duration the UE is on the PLMN or an equivalent PLMN.
A UE operating in CS/PS mode 1 which is already IMSI attached for non-EPS services in the network is still
IMSI attached for non-EPS services in the network. The UE may select GERAN or UTRAN radio access
technology and proceed with the appropriate MM specific procedure according to the MM service state. In this
case the UE shall not reselect E-UTRAN radio access technology for the duration the UE is on the PLMN or an
equivalent PLMN.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1288 Release 9
1288
A UE in CS/PS mode 1 of operation may perform a PLMN selection according to 3GPP TS 23.122 [6].
A UE operating in CS/PS mode 2 which is already IMSI attached for non-EPS services in the network is still
IMSI attached for non-EPS services in the network.
A UE operating in CS/PS mode 2 of operation shall perform a PLMN selection according to 3GPP TS 23.122 [6].
state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS
attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the combined attach procedure is
rejected with the GMM cause with the same value.
System Simulator:
- cell I, cell J and Cell A (belonging to different PLMNs and different frequencies).
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1289 Release 9
1289
U - S Message
- Cell I as a "Not suitable neighbour cell".
- Cell J as a "Suitable cell".
- - - -
- - - -
REQUEST message.
allowed in this PLMN" as specified.
- EXCEPTION: In parallel with step 6 below, the
test steps in the parallel behaviour in table
9.2.1.2.12.3.2-2 is taking place if the UE is
operating in CS/PS mode 2.
- - - -
indicate that the UE does not respond to
paging when paged with GUTI-1 and with CN
domain indicator set to "PS"?
- - 1 -
paging when paged with IMSI and with CN
- - 1 -
- Cell I as a "Suitable cell".
- Cell J as a "Not suitable neighbour cell".
- - - -
- - - -
allowed in this PLMN" .
--> - -
- The SS configures:
- Cell A as the "Not Suitable off cell".
- Cell I as the "Serving cell".
- - - -
- - - -
USIM is inserted..
- - - -
REQUEST message on Cell I?
15-
26

ACCEPT message to be used in the
UE registration procedure in TS
36.508 clause 4.5.2.3 see Table
9.2.1.2.12.3.3-4 below
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1290 Release 9
1290
- - - -

U - S Message
- The following messages are sent and shall be
received on Cell J .
- - - -
REQUEST message?
RESPONSE message.
COMMAND message.
COMPLETE message.
6 The SS responds with an ATTACH ACCEPT
message.
message.


Table 9.2.1.2.12.3.3-2: Message ATTACH REJECT (step 4, step 10, Table 9.2.1.2.12.3.2-1)
allowed in this
PLMN

Table 9.2.1.2.12.3.3-3: Message ATTACH REQUEST (step 9, step 14, Table 9.2.1.2.12.3.2-1)
apply for NAS key
"111".

Last visited registered TAI

Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1291 Release 9
1291
clause 4.5.2.3)
GUTI Not Present
provide LAI


SS doesnt
provide TMSI

not available"

9.2.1.2.13 Combined attach / Rejected / No suitable cells in tracking area
(1)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'No Suitable Cells In
tracking area' }
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, deletes any GUTI, last visited
registered TAI and KSI, resets the attach attempt counter, enters the state EMM-
DEREGISTERED.LIMITED-SERVICE and stores the current TAI in the list of "forbidden tracking areas for
roaming" }
}

(2)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI is in the list of
ensure that {
when { UE re-selects a cell that belongs to the TAI where UE was rejected }
}

(3)
"forbidden tracking areas for roaming" and KSI was deleted }
ensure that {
when { in the same PLMN, UE enters a cell which provides normal service and belongs to the
tracking area not in the list of "forbidden tracking areas for roaming" }
then { UE attempts to attach with IMSI indicated that no key is available }
}

(4)
ensure that {
when { there are cells in the same PLMN and other PLMN that provide normal service and belong to
the tracking area not in the list of "forbidden tracking areas for roaming" }
then { UE attempts to attach to the cell in the same PLMN }
}

(5)
roaming" contains more than one TAI }
ensure that {
when { UE re-selects a cell that belongs to one of the TAIs in the list of "forbidden tracking
areas for roaming" }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1292 Release 9
1292
(6)
ensure that {
when { UE receives an ATTACH REJECT message with the EMM cause set to 'No Suitable Cells In
tracking area' }
then { UE deletes RAI, P-TMSI, P-TMSI signature, GPRS ciphering key sequence number, TMSI, LAI
}

(7)
with { UE is swithched off }
ensure that {
tracking areas for roaming" before UE was switched off }
}

5.5.1.3.5 and TS 24.008, clause 4.7.3.2.4.
[TS 24.301, clause 5.3.2]
USIM is removed, and periodically (with a period in the range 12 to 24 hours). One or more tracking areas is removed
from the list of "forbidden tracking areas for roaming" in the UE, as well as the list of "forbidden tracking areas for
regional provision of service" if, after a subsequent procedure e.g. attach procedure, tracking area updating procedure
and GUTI reallocation procedure, one or more tracking areas in the lists is received from the network.
shall be deleted.
[TS 24.301, clause 5.5.1.3.5]
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and KSI. Additionally the UE shall
reset the attach attempt counter and enter the state EMM-DEREGISTERED.LIMITED-SERVICE.
The UE shall store the current TAI in the list of "forbidden tracking areas for roaming".
The UE shall search for a suitable cell in another tracking area or in another location area in the same PLMN
according to 3GPP TS 36.304 [21].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1293 Release 9
1293
...
[TS 24.008, clause 4.7.3.2.4]
...
...
#15 (No Suitable Cells In Location Area);
The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set
the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and
shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-
SERVICE.
The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt
counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE.
...
System Simulator:
- cell J (another VPLMN);
- system information indicate that NMO 1 is used;
- System information combination 4 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells
- if pc_GERAN and NOT pc_UTRAN, cell 24 (only active when stated:
- maximum 3 cells are simultaneously active.
NOTE 1: Cell L is present to confirm that UE searches in the same PLMN after reject from the SS.
NOTE 2: Cell K is present to confirm that UE shall not attempt attach to the cell in same TAI it was once rejected
from.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1294 Release 9
1294
run the test.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1295 Release 9
1295
U - S Message
Cell K as a "Suitable cell",
Cell J as a "Non-Suitable cell".
- - - -
- - - -
REQUEST message.
message with the EMM cause set to 'No
suitable cells in tracking area' on Cell I.
Cell I as a "Suitable cell",
Cell J as a "Non-Suitable cell ".
- - - -
Cell K or Cell I?
Cell K is the "Serving cell",
Cell J as a "Suitable cell".
- - - -
L?
4, 6
P
message with the EMM cause set to 'No
suitable cells in tracking area' on Cell L.
roaming in the UE should now contain TAI-9
and TAI-11)
Cell K as a Non-Suitable cell,
Cell J as a "Non-Suitable cell".
- - - -
Cell I?
supported
- - - -
configures:
Cell 5 or Cell 24 as the "Serving cell".
- - - -
otherwise.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1296 Release 9
1296
14a2 Void - - - -
REQUEST message?
14a4 The SS transmits an ATTACH REJ ECT
message with the GMM cause set to 'No
Suitable Cells In Location Area'.
Cell K as a Non-Suitable cell,
Cell J as a "Non-Suitable cell",
Cell 5 or Cell 24 as the "Non-Suitable cell".
- - - -
- - - -
- - - -
USIM is inserted.
- - - -
19-
30
- - - -
- - - -

Table 9.2.1.2.13.3.3-1: Message ATTACH REJECT (step 4 and step 10, Table 9.2.1.2.13.3.2-1)
EMM cause '0000 1111'B No Suitable Cells
In tracking area

Table 9.2.1.2.13.3.3-2: Message ATTACH REQUEST (step 9 and step 18, Table 9.2.1.2.13.3.2-1)
apply for NAS key
"111".

available

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1297 Release 9
1297
GPRS/IMSI attach

available (MS to
network)

0.
Other bits are not
checked.

value
Not present or any
allowed value

available

allowed value

allowed value

allowed value

allowed value

allowed value


Table 9.2.1.2.13.3.3-4: Message ATTACH REJECT (step 14a4, Table 9.2.1.2.13.3.2-1)
GMM cause '0000 1111'B No Suitable Cells
In Location Area


9.2.1.2.14 Combined attach / Rejected / Not authorized for this CSG
(1)
with { UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message on a CSG
cell }
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "Not authorized for this
CSG" and without integrity protection }
then { UE discards this message }
}

(2)
cell which is contained in the Allowed CSG list }
ensure that {
CSG" and with integrity protection }
then { UE removes the CSG ID from the Allowed CSG list }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1298 Release 9
1298

(3)
cell }
ensure that {
CSG" and with integrity protection }
then { UE searches for a suitable cell in the same PLMN }

[TS 24.301, clause 5.5.1.2.5]

If the ATTACH REJ ECT message with cause #25 was received without integrity protection, then the UE shall
subclause 5.1.3.3). Additionally, the UE shall reset the attach attempt counter and shall enter the state EMM-
DEREGISTERED.LIMITED-SERVICE.
The UE shall remove the CSG ID of the cell where the UE has sent the ATTACH REQUEST message from the
Allowed CSG list.
state, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case
when the normal attach procedure is rejected with the GMM cause with the same value.
System Simulator:
- cell A (TAC-1, frequency 1, not a CSG cell);
- cell B (TAC-2, frequency 1, a CSG cell whose CSG Identity is included in Allowed CSG list);
- cell G (another PLMN, frequency 2 and not a CSG cell).
UE:
of cell B);
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1299 Release 9
1299
U - S Message
- Cell G as a "Not Suitable cell".
- - - -
3 UE initiate attach procedure and send
ATTACH REQUEST including a PDN
CONNECTIVITY REQUEST message on cell
B.
message with EMM cause ="Not authorized
for this CSG" without integrity protection.
REQUEST message on Cell B after the expiry
of timer T3410 and T3411?
Note 1: IF UE initiate ATTACH procedure
again, it can prove that this UE has discard the
unprotected ATTACH REJ ECT message.
Note 2: Default value of T3410 is 15s; default
value of T3411 is 10s. In this TC, the network
will wait for total 30 seconds.
message with EMM cause =""Not authorized
for this CSG" with integrity protection.
9 The UE is switched off and switched on. - - - -
REQUEST message on Cell B in the next 30
seconds?
11

The SS configures:
- Cell B as a "Not Suitable cell".
- Cell G as a "Serving cell".
- Cell A as a "Suitable cell".

Cell A?
13-
24
- - - -
- - - -

Table 9.2.1.2.14.3.3-1: Message ATTACH REQUEST (step 3, step 6, step 12,Table 9.2.1.2.14.3.2-1)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1300 Release 9
1300
Security header type '0000'B " Plain NAS
message, not
security protected "

EMM cause '00011001'B #25 " Not authorized
for this CSG"

for this CSG"

Table 9.2.1.2.14.3.3-4: SystemInformationBlockType1 for Cell A, B, G (Pre-test conditions and all
steps in Table 9.2.1.2.14.3.2-1)
FALSE Cell G
FALSE Cell A
'000 0000 0000 0000
0000 0000 0010'B
Cell B
Not present Cell G

9.2.1.2.15 Combined attach / Abnormal case / Handling of the EPS attach attempt counter
(1)
with { UE has detected T3410 expiry after sending an ATTACH REQUEST message and has the attach
attempt counter set to the value less than four }
ensure that {
when { UE detects T3411 expiry }
then { UE restarts the attach procedure }
}

(2)
with { UE has sent an ATTACH REQUEST message and has the attach attempt counter set to four }
ensure that {
then { UE deletes GUTI, TAI list, last visited registered TAI and KSI }
}

(3)
with { UE has sent an ATTACH REQUEST message and has the attach attempt counter set to four }
ensure that {
then { UE deletes LAI, TMSI, ciphering key sequence number, RAI, P-TMSI, P-TMSI signature, and
GPRS ciphering key sequence number }
}

(4)
with { UE has started T3402 }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1301 Release 9
1301
ensure that {
then { UE restarts the attach procedure }
}

5.5.1.2.6 and 5.5.1.3.6 and TS 24.008, clause 4.7.3.1.5.
[TS 24.301, clause 5.5.1.1]
...
An attach attempt counter is used to limit the number of subsequently rejected attach attempts. The attach attempt
counter shall be incremented as specified in subclause 5.5.1.2.6. Depending on the value of the attach attempt counter,
specific actions shall be performed. The attach attempt counter shall be reset when:
- the UE is powered on;
- a USIM is inserted;
- an attach or combined attach procedure is successfully completed;
- a combined attach procedure is completed for EPS services only with cause #2, #16, #17, #18 or #22;
- an attach or combined attach procedure is rejected with cause #11, #12, #13, #14, #15 or #25; or
- a network initiated detach procedure is completed with cause #11, #12, #13, #14, #15 or #25.
Additionally the attach attempt counter shall be reset when the UE is in substate EMM-
DEREGISTERED.ATTEMPTING-TO-ATTACH and:
- a new tracking area is entered; or
- T3402 expires.
[TS 24.301, clause 5.5.1.2.6]
...
c) T3410 timeout
...
already set to 5.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1302 Release 9
1302
[TS 24.301, clause 5.5.1.3.6]
...
If the attach attempt counter is incremented according to subclause 5.5.1.2.6 the next actions depend on the value of the
attach attempt counter:
- if the update status is U1 UPDATED and the attach attempt counter is less than 5, then the UE shall keep the
update status to U1 UPDATED, the new MM state is MM IDLE substate NORMAL SERVICE;
- if the attach attempt counter is less than 5 and, additionally, the update status is different from U1 UPDATED,
then the UE shall delete any LAI, TMSI, ciphering key sequence number and list of equivalent PLMNs and set
the update status to U2 NOT UPDATED. The MM state remains MM LOCATION UPDATING PENDING; or
- if the attach attempt counter is equal to 5, then the UE shall delete any LAI, TMSI, ciphering key sequence
number and list of equivalent PLMNs and set the update status to U2 NOT UPDATED. A UE operating in
CS/PS mode 1 of operation shall select GERAN or UTRAN radio access technology and proceed with
appropriate MM or GMM specific procedures.
NOTE: It is up to the UE implementation when to enable E-UTRAN radio access technology selection.
[TS 24.008, clause 4.7.3.1.5]
...
If the GPRS attach attempt counter is greater than or equal to 5:
- the MS shall delete any RAI, P-TMSI, P-TMSI signature, list of equivalent PLMNs, and GPRS ciphering key
sequence number, shall set the GPRS update status to GU2 NOT UPDATED, shall start timer T3302. The state
is changed to GMM-DEREGISTERED. ATTEMPTING-TO-ATTACH or optionally to GMM-
DEREGISTERED.PLMN-SEARCH (see subclause 4.2.4.1.2) in order to perform a PLMN selection according
to 3GPP TS 23.122 [14].
...
System Simulator:
- cell A;
- if pc_GERAN and NOT pc_UTRAN, cell 24 (only active when stated;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1303 Release 9
1303
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1304 Release 9
1304
U - S Message
Cell A as "Serving cell",
Cell 5 or Cell 24 as "Non-Suitable cell".
- - - -
- - - -
2 The UE is powered on or switched on. - - - -
REQUEST message.
4 Wait for 25s to ensure that T3410 and T3411
expire and the UE releases locally the NAS
signalling connection.
NOTE 1: The attach attempt counter is 1.
- - - -
- - - -
REQUEST message.
- - - -
REQUEST message.
- - - -
REQUEST message.
12 Wait for 25s to ensure that T3410 expire and
the UE releases locally the NAS signalling
connection.
- - - -
supported
- - - -
reconfigures:
Cell A as "Non-suitable cell",
Cell 5 or Cell 24 as "Serving cell".
- - - -
REQUEST message without P-TMSI, P-TMSI
signature, RAI, TMSI on Cell 5 or Cell 24?
Cell A as "Serving cell",
Cell 5 or Cell 24 as "Non-Suitable cell".
- - - -
- - - -
the USIM is removed. Otherwise the power is
removed.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1305 Release 9
1305
USIM is inserted.
NOTE 6: The attach attempt counter is reset.
- - - -
REQUEST message.
- - - -
REQUEST message.
- - - -
REQUEST message.
- - - -
REQUEST message.
- - - -
REQUEST message.
26 Wait for 15s to ensure that T3410 expire and
the UE releases locally the NAS signalling
connection.
NOTE 12: The attach attempt counter is 5 and
the UE starts T3402.
- - - -
CONNECTIVITY REQUEST message after 12
minutes?
28-
49
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1306 Release 9
1306
GPRS/IMSI attach

available (MS to
network)

0.
Other bits are not
checked.

value
Not present or any
allowed value

available

allowed value

allowed value

allowed value

allowed value

allowed value


Table 9.2.1.2.15.3.3-2: Message ATTACH REQUEST (step 17, step19, step 21, step 23, step 25 and 27,
Table 9.2.1.2.15.3.2-1)
apply for NAS key
"111".

available

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1307 Release 9
1307
9.2.2 Detach procedure
9.2.2.1 UE initiated detach procedure
9.2.2.1.1 UE initiated detach / UE switched off
(1)
ensure that {
when { the UE is switched off }
then { the UE establishes the RRC connection with the RRC establishmentCause set to mo-
Signalling and sends DETACH REQUEST message, keeps the native security context, and deactivates the
EPS bearer context(s) locally }
}
5.5.2.2.1, 5.5.2.2.2 and Annex D and TS 36.331 clause 5.3.3.3.
[TS 24.301 clause 5.3.1.1]
layer to establish a NAS signalling connection. In this request to the lower layer the NAS shall provide to the lower
layer the RRC establishment cause and the call type as specified in annex D of this specification.
[TS24.301 clause 5.5.2.2.1]
The detach procedure is initiated by the UE by sending a DETACH REQUEST message. The Detach type IE included
in the message indicates whether detach is due to a "switch off" or not. The Detach type IE also indicates whether the
detach is for EPS services only, for non-EPS services only, or for both. If the UE has a mapped EPS security context as
the current EPS security context, the UE shall set the type of security context flag to "mapped security context".
Otherwise, the UE shall set the type of security context flag to "native security context".
...
If the UE is to be switched off, the UE shall try for a period of 5 seconds to send the DETACH REQUEST message.
During this period, the UE may be switched off as soon as the DETACH REQUEST message has been sent.
After the last DETACH REQUEST message is sent, the UE shall proceed as follows:
- if the current EPS security context is a native EPS security context, then the UE shall store the current EPS
security context as specified in annex C and mark it as valid;
- else if the current EPS security context is a mapped EPS security context and a non-current full native EPS security
context exists, then the UE shall store the non-current EPS security context as specified in annex C and mark it as valid,
and finally the UE shall delete any mapped EPS security context or partial native EPS security context.
[TS24.301 clause 5.5.2.2.2]
When the DETACH REQUEST message is received by the network, the network shall send a DETACH ACCEPT
message to the UE and store the current EPS security context, if the Detach type IE does not indicate "switch off".
Otherwise, the procedure is completed when the network receives the DETACH REQUEST message. On reception of a
DETACH REQUEST message indicating "switch off", the MME shall delete the current EPS security context, if it is a
mapped EPS security context.
The network and the UE shall deactivate the EPS bearer context(s) for this UE locally without peer-to-peer signalling
between the UE and the MME.
The UE, when receiving the DETACH ACCEPT message, shall stop timer T3421.
The UE is marked as inactive in the network for EPS services. State EMM-DEREGISTERED is entered in the network.
The UE in PS mode of operation shall enter the EMM-DEREGISTERED state.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1308 Release 9
1308
The UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, disable
E-UTRAN and select GERAN or UTRAN access technology and enter the EMM-NULL state.
...
...
Detach MO signalling (See Note 1) "originating signalling"
...
For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN or EHPLMN, the RRC
establishment cause will be set to "High priority access AC 11 15".

[TS 36.331, clause 5.3.3.3]
...
2>else
System Simulator:
- cell A (HPLMN).
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (State 2) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1309 Release 9
1309
U - S Message
1 Cause switch off - - - -
RRCConnectionRequest message with
establishmentCause set to mo-Signalling
followed by a DETACH REQUEST with the
Detach Type IE indicating "switch off"?
3-7 Void - - - -
8 The UE is switched on - - - -
9 Check: Does the UE transmit ATTACH
REQUEST message using KSI
ASME
of the
previously allocated EPS native security
context?
10-
21
- - - -
- - - -

}
}
}

TSC native security context
(for KSI
ASME
)

9.2.2.1.2 UE initiated detach / USIM removed from the UE
(1)
with { UE in EMM-REGISTERED }
ensure that {
when { the USIM is removed from the UE }
then { the UE sends DETACH REQUEST message and indicates that the detach is for both EPS services
and non-EPS services or for EPS services depending on the EPS attach type used }
}
5.5.2.2.1 and 5.5.2.2.3.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1310 Release 9
1310
[TS24.301 clause 5.5.2.2.1]
If the UE has a valid GUTI, the UE shall populate the GUTI or IMSI IE with the valid GUTI. If the UE does not have a
valid GUTI, the UE populates the GUTI or IMSI IE with its IMSI.
If the detach is not due to switch off and the UE is in the state EMM-REGISTERED or EMM-REGISTERED-
INITIATED, timer T3421 shall be started in the UE after the DETACH REQUEST message has been sent. If the detach
type indicates that the detach is for non-EPS services only the UE shall enter the state EMM-REGISTERED.IMSI-
DETACH-INITIATED, otherwise the UE shall enter the state EMM-DEREGISTERED-INITIATED. If the detach type
indicates that the detach is for non-EPS services or both EPS and non-EPS services, the UE shall enter the state MM
IMSI DETACH PENDING.
[TS24.301 clause 5.5.2.2.3]
When the DETACH REQUEST message is received by the network, a DETACH ACCEPT message shall be sent to the
UE, if the Detach type IE value indicates that the detach request has not been sent due to switching off. Depending on
the value of the Detach type IE the following applies:
- combined EPS/IMSI detach:
The UE is marked as inactive in the network for EPS and for non-EPS services. The states EMM-
DEREGISTERED and MM-NULL are entered in both the UE and the network.
System Simulator:
- cell A (HPLMN).
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (State 2) according to TS 36.508 [18]
U - S Message
1 Cause removal of USIM from the UE without
powering down
- - - -
2 Check: does the UE transmit a DETACH
REQUEST with the Detach Type IE indicating
"normal detach" and "combined EPS/IMSI
detach" or "EPS detach" depending on the UE
configuration?
- - 1 -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1311 Release 9
1311
Table 9.2.2.1.2.3.3-1: DETACH REQUEST (step 2, Table 9.2.2.1.2.3.2-1)
Detach type
Type of detach 001 EPS detach EPSOnlyAtt
ach
011 combined
EPS/IMSI detach
CombinedAt
tach
Switch off 0 normal detach
GUTI or IMSI GUTI-1

9.2.2.1.3 UE initiated detach / EPS capability of the UE is disabled
(1)
ensure that {
when { EPS capability of the UE is disabled }
then { UE sends the DETACH REQUEST message on the cell registered and indicates that the detach
is for EPS services }
}

References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clause 4.5,clause
5.5.2.1 and clauses 5.5.2.2
[TS 24.301,clause 4.5]
When the UE supporting the A/Gb and/or Iu mode together with the S1 mode needs to stay in A/Gb or Iu mode, in
order to prevent unwanted handover or cell reselection from UTRAN/GERAN to E-UTRAN, the UE shall disable the
E-UTRA capability.
- The UE shall not set the E-UTRA support bits of the MS Radio Access capability IE (see 3GPP TS 24.008 [13],
subclause 10.5.5.12a), the E-UTRA support bits of Mobile Station Classmark 3 IE (see 3GPP TS 24.008 [13],
subclause 10.5.1.7) and the ISR support bit of the MS network capability IE (see 3GPP TS 24.008 [13],
subclause 10.5.5.12) in the ATTACH REQUEST message and the ROUTING AREA UPDATE REQUEST
message after it selects GERAN or UTRAN; and
- the UE NAS layer shall indicate the access stratum layer(s) of disabling of the E-UTRA capability.
NOTE: The UE can only disable the E-UTRAN capabilities when in EMM-IDLE mode.

[TS 24.301,clause 5.5.2.1]

The detach procedure with appropriate detach type shall be invoked by the UE if the UE is switched off, the USIM card
is removed from the UE or the EPS capability of the UE is disabled or the UE wishes to detach for non-EPS services.

If the detach procedure for EPS services is performed, the EPS bearer context(s) for this particular UE are deactivated
locally without peer-to-peer signalling between the UE and the MME.
Upon successful completion of the detach procedure, if the UE and the MME enter the EMM-DEREGISTERED state,
the UE and the MME shall delete any mapped EPS security context or partial native EPS security context.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1312 Release 9
1312
If the UE supports A/Gb mode or Iu mode, the UE shall store the TIN in the non-volatile memory in the ME, as
described in annex C, for a subsequent attach procedure.
[TS 24.301, clause 5.5.2.2.1]

[TS 24.301, clause 5.5.2.2.2]

The network and the UE shall deactivate the EPS bearer context(s) for this UE locally without peer-to-peer signalling
between the UE and the MME.
The UE, when receiving the DETACH ACCEPT message, shall stop timer T3421.
The UE is marked as inactive in the network for EPS services. State EMM-DEREGISTERED is entered in the network.
The UE in PS mode of operation shall enter the EMM-DEREGISTERED state.
The UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, disable
E-UTRAN and select GERAN or UTRAN access technology and enter the EMM-NULL state.
System Simulator:
- Cell A.
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1313 Release 9
1313
U - S Message
1 Cause EPS capability of the UE to be
disabled.
- - - -
2 Check:Does the UE transmits a DETACH
REQUEST message with the Detach type IE
indicating EPS detach and normal detach.
3 The SS responds the DETACH ACCEPT
message.
- DETACH ACCEPT - -
- - 1 -

Table 9.2.2.1.3.3.3-1: DETACH REQUEST (steps 2 in Table 9.2.2.1.3.3.2-1)
Detach type
Type of detach 001 EPS detach only
GUTI or IMSI GUTI-1

9.2.2.1.4 Void
9.2.2.1.5 Void
9.2.2.1.6 UE initiated detach / Abnormal case / Local detach after 5 attempts due to no
network response
(1)
ensure that {
when { the UE receives no response to the UE initiated DETACH REQUEST }
then { the UE re-transmits the DETACH REQUEST up to 4 times on the expiry of timer T3421 }
}

(2)
ensure that {
when { the UE receives no response to the UE initiated DETACH REQUEST }
then { the UE aborts the detach procedure and perform local detach on the 5
th
expiry of timer
T3421 }
}

[TS 24.301, clause 5.5.2.2.1]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1314 Release 9
1314
[TS 24.301, clause 5.5.2.2.4 c)]

c) T3421 timeout
On the first four expiries of the timer, the UE shall retransmit the DETACH REQUEST message and shall reset
and restart timer T3421. On the fifth expiry of timer T3421, the detach procedure shall be aborted and the UE
shall change to state:
- EMM-REGISTERED.NORMAL-SERVICE and MM-NULL if "IMSI detach" was requested;
- EMM-DEREGISTERED if "EPS detach" was requested;
- EMM-DEREGISTERED and MM-NULL if "combined EPS/IMSI detach" was requested.
System Simulator:
- cell A (HPLMN).
UE:
none.
Preamble:
- the UE is in state Registered, Idle Mode (State 2) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1315 Release 9
1315
U - S Message
1 Cause UE to initiate detach from the EPS
services only.
- - - -
2 The UE transmits a DETACH REQUEST
message with the Detach type IE indicating
EPS detach and normal detach? The UE
starts timer T3421.
3 The SS does not respond to the DETACH
REQUEST message.
- - - -
4 Check: When the timer T3421 expires does
the UE re-transmit DETACH REQUEST
message. Timer T3421 is re-started (1
st

expiry).
REQUEST message.
- - - -
nd

expiry).
REQUEST message.
- - - -
rd

expiry).
REQUEST message.
- - - -
th

expiry).
REQUEST message.
- - - -
12 When the timer T3421 expires the UE aborts
the detach procedure and performs a local
detach (5
th
expiry).
- - 2 P
13 The SS starts the EPS bearer context
modification procedure using the previously
allocated EPS bearer identity
<-- MODIFY EPS BEARER
CONTEXT REQUEST
- -
14 Check: does the UE transmit a MODIFY EPS
BEARER CONTEXT ACCEPT message within
the next 10s?
--> MODIFY EPS BEARER
CONTEXT ACCEPT
2 F
Note: T3421 value is specified as 15s in TS 24.301.

Table 9.2.2.1.6.3.3-1: DETACH REQUEST (steps 2, 4, 6, 8 and 10 Table 9.2.2.1.6.3.2-1)
Detach type
Type of detach 001 EPS detach
GUTI or IMSI GUTI-1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1316 Release 9
1316
9.2.2.1.7 UE initiated detach / Abnormal case / Detach procedure collision
(1)
with { UE in EMM-DEREGISTERED-INITIATED state }
ensure that {
when { the UE receives the DETACH REQUEST message from the network }
then { the UE aborts the UE initiated detach procedure and completes the network initiated detach
procedure }
}

(2)
with { UE in EMM-DEREGISTERED state }
ensure that {
when { the UE has completed the network initiated detach procedure with re-attach required }
then { the UE initiates the attach procedure }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.2.2.4 and
5.5.2.3.2.
[TS 24.301, clause 5.5.2.2.4]

d) Detach procedure collision
If the UE receives a DETACH REQUEST message before the UE initiated detach procedure has been completed,
it shall treat the message as specified in subclause 5.5.2.3.2 and send a DETACH ACCEPT message to the
network.
[TS 24.301, clause 5.5.2.3.2]
NAS signalling connection has been released, initiate an attach or combined attach procedure.
System Simulator:
- cell A.
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (State 2) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1317 Release 9
1317
U - S Message
services.
- - - -
EPS detach and normal detach. The UE
starts timer T3421.
REQUEST message.
- - - -
4 With T3421 still running the SS shall send
DETACH REQUEST message with the Detach
type IE indicating "re-attach required".
ACCEPT message?
- - - -
- - - -
8-
19
- - - -
- - - -

Table 9.2.2.1.7.3.3-1: DETACH REQUEST (step 2 Table 9.2.2.1.7.3.2-1)
Detach type
GUTI or IMSI GUTI-1

Table 9.2.2.1.7.3.3-2: DETACH REQUEST (step 4 Table 9.2.2.1.7.3.2-1)
Detach type
Type of detach 001 re-attach required

9.2.2.1.8 UE initiated detach / Abnormal case / Detach and EMM common procedure
collision
(1)
with { UE in EMM-DEREGISTERED-INITIATED state due to switch off }
ensure that {
when { the UE receives an EMM common procedure message from the network }
then { the UE ignores the message and continues the detach procedure }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1318 Release 9
1318
(2)
with { UE in EMM-DEREGISTERED-INITIATED state due to normal detach }
ensure that {
when { the UE receives GUTI REALLOCATION COMMAND from the network }
then { the UE ignores the message and continues the detach procedure }
}

(3)
with { UE in EMM-DEREGISTERED-INITIATED state due to normal detach }
ensure that {
when { the UE receives AUTHENTICATION REQUEST, SECURITY MODE COMMAND or IDENTITY REQUEST message
from the network }
then { the UE responds to the message and then continues the detach procedure }
}

[TS 24.301, clause 5.5.2.2.4]

e) Detach and EMM common procedure collision
Detach containing cause "switch off":
- If the UE receives a message used in an EMM common procedure before the detach procedure has been
completed, this message shall be ignored and the detach procedure shall continue
Detach containing other causes than "switch off":
- If the UE receives a GUTI REALLOCATION COMMAND, an EMM STATUS or an EMM
INFORMATION message before the detach procedure is completed, this message shall be ignored and the
detach procedure shall continue.
- If the UE receives an AUTHENTICATION REQUEST, SECURITY MODE COMMAND or IDENTITY
REQUEST message before the detach procedure has been completed, the UE shall respond to it as described
in subclause 5.4.2, 5.4.3 and 5.4.4 respectively and the detach procedure shall continue.
System Simulator:
- cell A.
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (State 2) according to TS 36.508[18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1319 Release 9
1319
U - S Message
1 Cause switch off. - - - -
switch off.
3 The SS transmits a GUTI REALLOCATION
COMMAND message.
<-- GUTI REALLOCATION
COMMAND
- -
4 Check: Does the UE transmit an GUTI
REALLOCATION COMPLETE message?
--> GUTI REALLOCATION
COMPLETE
1 F
- - 1 -
6 The UE is switched on and performs an
ATTACH procedure.
- - - -
services only.
- - - -
starts timer T3421.
REQUEST message.
- - - -
GUTI REALLOCATION COMMAND.
<-- GUTI REALLOCATION
COMMAND
- -
11 Check: Does the UE transmit a GUTI
REALLOCATION COMPLETE message?
--> GUTI REALLOCATION
COMPLETE
2 F
12 SS responds with DETACH ACCEPT
message.
14 Cause UE to initiate attach for the EPS
services. The generic procedure in 36.508
clause 4.5.2.3-1 is executed so as to complete
the attach procedure.
- - - -
services only.
- - - -
starts timer T3421.
REQUEST message.
- - - -
AUTHENTICATION REQUEST.
AUTHENTICATION RESPONSE message?
message.
- - - -
services only.
- - - -
starts timer T3421.
REQUEST message.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1320 Release 9
1320
SECURITY MODE COMMAND.
27 Check: Does the UE transmit a SECURITY
MODE COMPLETE message?
message.
- - - -
services only.
- - - -
starts timer T3421.
REQUEST message.
- - - -
IDENTITY REQUEST.
35 Check: Does the UE transmit an IDENTITY
RESPONSE message?
message.

Table 9.2.2.1.8.3.3-1: DETACH REQUEST (steps 8, 16, 24 and 32 Table 9.2.2.1.8.3.2-1)
Detach type

Table 9.2.2.1.8.3.3-2: GUTI REALLOCATION COMMAND (step 3 Table 9.2.2.1.8.3.2-1)
GUTI GUTI-2
TAI list Not present

Table 9.2.2.1.8.3.3-3: GUTI REALLOCATION COMMAND (step 10 Table 9.2.2.1.8.3.2-1)
GUTI GUTI-3
TAI list Not present

9.2.2.1.9 UE initiated detach / Abnormal case / Change of cell into a new tracking area
(1)
with { UE in EMM-DEREGISTERED-INITIATED state }
ensure that {
when { the UE changes into a new tracking area that is not in the stored TAI list }
then { the UE aborts the detach procedure and initiates a Tracking Area Updating procedure }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1321 Release 9
1321
(2)
with { UE in EMM-TRACKING-AREA-UPDATING-INITIATED state }
ensure that {
when { the UE receives TRACKING AREA UPDATE ACCEPT message }
then { the UE re-initiates the detach procedure after completing the Tracking Area Updating
procedure }
}

[TS 24.301, clause 5.5.2.2.4]

f) Change of cell into a new tracking area
If a cell change into a new tracking area that is not in the stored TAI list occurs before the UE initiated detach
procedure is completed, the detach procedure shall be aborted and re-initiated after successfully performing a
tracking area updating procedure. If the detach procedure was initiated due to removal of the USIM, the UE shall
abort the detach procedure and enter the state EMM-DEREGISTERED.
System Simulator:
- cell A belongs to TAI-1 (home PLMN) is set to ''Serving cell''
- cell B belongs to TAI-2 (home PLMN) is set to ''Non-Suitable cell''.
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (State 2) according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1322 Release 9
1322
U - S Message
- - - -
services.
- - - -
EPS detach and normal detach. The UE
starts timer T3421.
REQUEST message.
- - - -
4 Set the cell type of cell A to the ''Non-Suitable
cell''.
Set the cell type of cell B to the ''Serving cell''.

Note: T3421 value is specified as 15s in TS
24.301 and it is assumed that SS can
configure cells within this time.
- - - -
- - - -
REQUEST
1 P
ACCEPT
- -
AREA UPDATE COMPLETE message?
COMPLETE
- -
EPS detach and normal detach.
- - - -

Table 9.2.2.1.9.3.3-1: DETACH REQUEST (steps 2 and 8 Table 9.2.2.1.9.3.2-1)
Detach type
GUTI or IMSI GUTI-1

GUTI GUTI-2

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1323 Release 9
1323
9.2.2.2 Network initiated detach procedure
9.2.2.2.1 NW initiated detach / Re-attach required
(1)
ensure that {
when { SS sends DETACH REQUEST message with the Detach type IE "re-attach required" }
then { UE sends DETACH ACCEPT message and UE intiates an attach procedure with the current EPS
security context}
}

References: The conformance requirement covered in the present TC is specified in: 3GPP TS 24.301 clauses 5.5.2.3.2.
[TS24.301 clause5.5.2.3.2]
NAS signalling connection has been released, initiate an attach or combined attach procedure.
A UE which receives a DETACH REQUEST message with detach type indicating "re-attach required" or "re-attach not
required" and no EMM cause IE, is detached only for EPS services.
...If the detach type indicates "IMSI detach" or "re-attach required" then the UE shall ignore the EMM cause IE if
received.
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1324 Release 9
1324
1 The SS initiates Detach procedure with the
Detach Type IE "re-attach required"
message?
3 The SS releases RRC connection.
- - - -
- - - -
- - - -
4Aa1 IF the UE sets the ESM information transfer
options and/or APN.
4Aa2 The UE transmits an ESM INFORMATION
5 The SS sends ATTACH ACCEPT to assign the
new GUTI (GUTI-2). The ACTIVATE
message?

Detach type '001'B "re-attach
required"

TSC '0'B native security
context

NAS key set identifier The value is a same
value to be allocated by
SS in Preamble.


NOTE: This message is sent within the SECURITY NAS PROTECTED MESSAGE in Table 9.2.2.2.1.3.3-3.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1325 Release 9
1325
Table 9.2.2.2.1.3.3-3: Message SECURITY PROTECTED NAS MESSAGE (step 4, Table 9.2.2.2.1.3.2-1)
Security header type '0001'B Integrity protected
NAS message '01000001'B ''ATTACH
REQUEST''

TAI list
Length of tracking area identity list contents 00000110B 6 octets
Number of elements 00000B 1 element
Type of list 00B "list of TACs
belonging to one
PLMN, with non-
consecutive TAC
values"

Partial tracking area identity list TAI-1
GUTI GUTI-2

9.2.2.2.2 NW initiated detach / IMSI detach
(1)
with { UE in EMM-REGISTERED state}
ensure that {
when { UE receives DETACH REQUEST message with the Detach type IE = IMSI detach }
then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type IE = Combined TA/LA
updating with IMSI attach }
}
(2)
ensure that {
when { UE recieves TRACKING AREA UPDATE ACCEPT message }
then { UE enters EMM-REGISTERED and enters MM IDLE and sends TRACKING AREA UPDATE COMPLETE
message }
}

[TS24.301 clause5.5.2.3.2]
...
When receiving the DETACH REQUEST message and the Detach type IE indicates "IMSI detach", the UE shall not
deactivate the EPS bearer context(s) including the default EPS bearer context. The UE shall set the MM update status to
U2 NOT UPDATED. A UE may send a DETACH ACCEPT message to the network, and shall re-attach to non-EPS
services by performing the combined tracking area updating procedure according to subclause 5.5.3.3, sending a
TRACKING AREA UPDATE REQUEST message with EPS update type IE indicating "combined TA/LA updating
with IMSI attach".

If the detach type IE indicates "IMSI detach" or "re-attach required", then the UE shall ignore the EMM cause IE if
received.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1326 Release 9
1326
System Simulator:
- cell A.
UE:
Preamble:
1 Force the SS to initiate Detach procedure with
the Detach Type IE IMSI detach
2 The UE may send DETACH ACCEPT
message.(Optional)
--> DETACH ACCEPT - -
3 Check: Does the UE send TRACKING AREA
UPDATE REQUEST message?
REQUEST
1 P
4 Void - - - -
5 Void - - - -
6 The SS sends TRACKING AREA UPDATE
ACCEPT message.

ACCEPT
- -
COMPLETE
2 P
A with S-TMSI2 for CS domain?
Generic Procedure (TS36.508 subclause
6.4.2.4)
- - 2 -
A with S-TMSI2 for PS domain?
Generic Procedure (TS36.508 subclause
6.4.2.4)
- - 2 -

Detach type 011B IMSI detach

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1327 Release 9
1327
EPS update type
EPS update type value 010B Combined TA/LA
updating with
IMSI attach

Old GUTI GUTI-1
Old location area identification Not Present
TMSI status 0B " no valid TMSI
available"

GUTI GUTI-2
TAI list
Length of tracking area identity list contents 00001000B
Number of elements 00000B
Type of list 00B list of TACs
belonging to one
PLMN, with non-
consecutive TAC
values

MCC
MNC
TAC 1
TAI-1
MS identity TMSI-1

9.2.2.2.3 to 9.2.2.2.13 Void
9.2.2.2.14 NW initiated detach / Abnormal case / EMM cause not included
(1)
ensure that {
when { UE receives a DETACH REQUEST message with the Detach type IE re-attach not required and
with no EMM cause IE included }
then { UE delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, KSI,
set the update status to EU2 NOT UPDATED and start timer T3402. when T3402 expired, the UE attempts
to attach again }
}

[TS24.301 clause5.5.2.3.4]

b) DETACH REQUEST, other EMM cause values than those treated in subclause 5.5.2.3.2 or no EMM cause IE is
included, and the Detach type IE indicates "re-attach not required".
The UE shall delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, KSI, shall set the
update status to EU2 NOT UPDATED and shall start timer T3402. The UE may enter the state EMM-

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1328 Release 9
1328
DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [6];
otherwise the UE shall enter the state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH.
System Simulator:
- cell I (VPLMN and set as a serving cell) configured according to table 6.3.2.2-3 in TS 36.508 [18].
UE:
None.
Preamble:
- the UE is in state Generic RB established (state 3) on cell I according to TS 36.508 [18];
- T3402 in the UE is set to 2 minutes.
1 SS initiates Detach procedure with the Detach
Type IE re-attach not required and no EMM
cause IE included
2 The UE transmits a DETACH ACCEPT
message on Cell I.
Note: Now UE should start timer T3402
--> DETACH ACCEPT - -
the UE transmit ATTACH REQUEST message
on cell I?
5-16 The attach procedure is completed by
- - - -
- - - -

Detach type 010B re-attach not
required

EMM cause Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1329 Release 9
1329
apply for NAS key
"111".


Table 9.2.2.2.14.3.3-3: Message ATTACH ACCEPT ( preamble, 9.2.2.2.14.3.1)
T3402 value 2 minute The default value
is 12 minutes, use
2 minute to
shorten the whole
TC execute time

9.2.3 Tracking area updating procedure (S1 mode only)
9.2.3.1 Normal and periodic tracking area updating
9.2.3.1.1 Normal tracking area update / Accepted
(1)
ensure that {
when { UE detects entering a new tracking area already included in the TAI list }
then { UE does not send TRACKING AREA UPDATE REQUEST message }
}
(2)
ensure that {
when { UE detects entering a new tracking area not included in the TAI list }
then { UE sends TRACKING AREA UPDATE REQUEST message with 'EPS update type = TA updating'}
}
(3)
with { UE in state EMM-REGISTERED and EMM-IDLE mode and has a valid TAI value }
ensure that {
when { UE detects entering a new tracking area not included in the TAI list }
then { UE sends TRACKING AREA UPDATE REQUEST message with the TAI value in 'Last visited
registered TAI' IE }
}

5.5.3.2.2 and 5.5.3.2.4.
[TS24.301 clause5.5.3.1]
The tracking area updating procedure is always initiated by the UE and is used for the following purposes:
- normal tracking area updating to update the registration of the actual tracking area of a UE in the network;
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1330 Release 9
1330
[TS24.301 clause5.5.3.2.2]
...
After sending the TRACKING AREA UPDATE REQUEST message to the MME, the UE shall start timer T3430 and
enter state EMM-TRACKING-AREA-UPDATING-INITIATED (see example in figure 5.5.3.2.2). If timer T3402 is
currently running, the UE shall stop timer T3402. If timer T3411 is currently running, the UE shall stop timer T3411. If
timer T3442 is currently running, the UE shall stop timer T3442.
If the UE supports A/Gb mode or Iu mode, the UE shall handle the Old GUTI IE as follows:
- If the TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and RAI, the UE shall map the P-TMSI and
RAI into the Old GUTI IE. Additionally, if the UE holds a valid GUTI, the UE shall indicate the GUTI in the
Additional GUTI IE.
NOTE: The mapping of the P-TMSI and RAI to the GUTI is specified in 3GPP TS 23.003 [2].
GUTI in the Old GUTI IE.

[TS24.301 clause5.5.3.2.4]
...
Upon receiving a TRACKING AREA UPDATE ACCEPT message, the UE shall stop timer T3430, reset the routing
area updating attempt counter, enter state EMM-REGISTERED and set the EPS update status to EU1 UPDATED. If the
message contains a GUTI, the UE shall use this GUTI as new temporary identity for EPS services and shall store the
new GUTI. If no GUTI was included by the MME in the TRACKING AREA UPDATE ACCEPT message, the old
GUTI shall be used. If the UE receives a new TAI list in the TRACKING AREA UPDATE ACCEPT message, the UE
shall consider the new TAI list as valid and the old TAI list as invalid; otherwise, the UE shall consider the old TAI list
as valid.
...
If the TRACKING AREA UPDATE ACCEPT message contained a GUTI, the UE shall return a TRACKING AREA
UPDATE COMPLETE message to the MME to acknowledge the received GUTI.
System Simulator:
- cell A (belongs to TAI-1, home PLMN) is set to ''Serving cell'';
- cell C (belongs to TAI-3, home PLMN) is set to ''Non- Suitable cell'';
- cell D (belongs to TAI-4, home PLMN) is set to ''Non- Suitable cell''.
UE:
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell A according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1331 Release 9
1331
U - S Message
The following messages are sent and shall be
received on cell C.
- - - -
1 Set the cell type of cell A to the "Non-Suitable
cell ".
Set the cell type of cell C to the " Serving cell"
- - - -
REQUEST
2, 3 P
ACCEPT
- -
COMPLETE
2 P
indicate that the UE is in EMM-REGISTERED
state on cell C with Paging UE-Identity =S-
TMSI2 and with CN domain indicator set to
"PS"?

- - 2 -
7 Set the cell type of cell C to the "Non-Suitable
cell ".
Set the cell type of cell D to the " Serving cell"
- - - -
next 30 seconds?
- - 1 F
state on cell D with Paging UE-Identity =S-
"PS"?

- - 1 -
received on cell A.
- - - -
10 Set the cell type of cell D to the "Non-Suitable
cell ".
Set the cell type of cell A to the " Serving cell"
- - - -
REQUEST
2, 3 P
ACCEPT
- -
COMPLETE
- -

included by UE if
valid, IMSI
otherwise''

Last visited registered TAI TAI 1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1332 Release 9
1332
GUTI GUTI-2
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
PLMN=MCC/MNC
TAC 1=3
TAC 2=4
''PLMN is set to
the same
MCC/MNC stored
in EF
IMSI
''
''TAI-3''
''TAI-4''

Old GUTI GUTI-2

GUTI GUTI-3
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
PLMN=MCC/MNC
TAC 1=1
TAC 2=2
''PLMN is set to
the same
MCC/MNC stored
in EF
IMSI
''
''TAI-1''
''TAI-2''

9.2.3.1.2 Normal tracking area update / Accepted / "Active" flag set
(1)
with { UE in state EMM-SERVICE-REQUEST-INITIATED and EMM-CONNECTED}
ensure that {
when { UE detects entering a new tracking area already not included in the TAI list }
then { UE sends TRACKING AREA UPDATE REQUEST message with ''Active'' flag}
}
(2)
with { UE in state EMM-REGISTERED and EMM-CONNECTED}
ensure that {
when { UE sends TRACKING AREA UPDATE COMPLETE to NW }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1333 Release 9
1333
then { UE keeps the NAS signalling connection }
}
5.5.3.2.2, 5.5.3.2.4 and 5.6.1.5.
[TS24.301 clause5.5.3.1]
- normal tracking area updating to update the registration of the actual tracking area of a UE in the network;
...
[TS24.301 clause5.5.3.2.2]
i) when the UE detects entering a tracking area that is not in the list of tracking areas that the UE previously
..
enter state EMM-TRACKING-AREA-UPDATING-INITIATED (see figure 5.5.3.2.2). If timer T3402 is currently
running, the UE shall stop timer T3402. If timer T3411 is currently running, the UE shall stop timer T3411. If timer
T3442 is currently running, the UE shall stop timer T3442.

Additional GUTI IE.
In the TRACKING AREA UPDATE REQUEST message the UE shall set the value of the EPS update type IE to
"periodic updating", if the procedure initiated due to expiry of T3412; otherwise, the UE shall set the value to "TA
updating". If a UE has uplink user data pending when it initiates the tracking area updating procedure, or uplink
signalling not related to the tracking area updating procedure, it may also set an "active" flag in the TRACKING AREA
UPDATE REQUEST message to indicate the request to establish the user plane to the network and to keep the NAS
signalling connection after the completion of the tracking area updating procedure.
...
When the tracking area updating procedure is initiated in EMM-IDLE mode to perform an inter-system change from
A/Gb mode or Iu mode to S1 mode and the TIN is set to "P-TMSI", the UE shall include the GPRS ciphering key
sequence number applicable for A/Gb mode or Iu mode and a nonce
UE
in the TRACKING AREA UPDATE REQUEST
message.
[TS24.301 clause5.5.3.2.4]
...
If the "active" flag is included in the TRACKING AREA UPDATE REQUEST message, the MME shall re-establish
the radio and S1 bearers for all active EPS bearer contexts.
Upon receiving a TRACKING AREA UPDATE ACCEPT message, the UE shall stop timer T3430, reset the tracking

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1334 Release 9
1334
as valid.
...
...
[TS24.301 clause5.6.1.5]
...
f) Tracking area updating procedure is triggered
The UE shall abort the service request procedure, stop timer T3417 and perform the tracking area updating
procedure. The "active" flag shall be set in the TRACKING AREA UPDATE REQUEST message.

...
i) Transmission failure of SERVICE REQUEST message indication with TAI change from lower layers
If the current TAI is not in the TAI list, the service request procedure shall be aborted to perform the tracking
area updating procedure. The "active" flag shall be set in the TRACKING AREA UPDATE REQUEST message.

If the current TAI is still part of the TAI list, the UE shall restart the service request procedure.
...
System Simulator:
- cell A (TAI-1:MCC1/MNC1/TAC1) (HPLMN);
- cell B(TAI-2:MCC1/MNC1/TAC2) (HPLMN with different TAC);
- cell A is set to the "Serving cell";
- cell B is set to the "Suitable neighbour cell";
UE;
none.
Preamble:
- the UE is in state Loopback Activated (state 4) with condition UE TEST LOOP MODE B on cell A according to
TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1335 Release 9
1335
U - S Message
0A The SS transmits one IP Packet to the UE. <-- IP PACKET - -
0B The SS waits 1 second after the IP packet has
been transmitted in step 1 and then transmits
an RRCConnectionRelease message.
- - - -
1 Void - - - -
2 The UE transmits SERVICE REQUEST
message.
--> SERVICE REQUEST - -
3 The SS does not perform a radio bearer
establishment procedure. (Note2)
- - - -
received on cell B.
- - - -
4 Set the cell type of cell A to the "Non-suitable
cell". Set the cell type of cell B to the "Serving
cell".
- - - -
4A SS sends RRC Connection release on Cell A. - - - -
"Active" flag?
REQUEST
1 P
6 Void - - - -
7 Void - - - -
8 Void - - - -
ACCEPT
- -
COMPLETE
1 P
11 The SS waits 10seconds (T3440). - - - -
message
13 Check: does the UE transmit an IDENTIY
RESPONSE message?
Note1: Void.
Note2: The SS does not send any AS or NAS messages to UE.

EPS update type
"Active" flag 1B Bearer
establishment
requested

Old GUTI GUTI-1 Old GUTI is
included by UE if
valid, IMSI
otherwise.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1336 Release 9
1336
GUTI GUTI-2
TAI list
Length of tracking area identity list contents 00000110B 6 octets
Number of elements 00000B 1 element
Type of list 00B "list of TACs
belonging to one
PLMN, with non-
consecutive TAC
values"

MCC
MNC
TAC 1
TAI-2

9.2.3.1.3 Void
9.2.3.1.4 Normal tracking area update / List of equivalent PLMNs in the TRACKING AREA
UPDATE ACCEPT message
(1)
ensure that {
when { the UE receives TRACKING AREA UPDATE ACCEPT message including a list of equivalent PLMNs }
then { the UE stores correctly the list and considers a forbidden PLMN if the forbidden PLMN is
included in the equivalent list }
}

(2)
ensure that {
when { the UE receives TRACKING AREA UPDATE ACCEPT message without a list of equivalent PLMNs }
then { the UE deletes the stored list and applies a normal PLMN selection process }
}

[TS 24.301, clause 5.5.3.2.4]
The MME may also include of list of equivalent PLMNs in the TRACKING AREA UPDATE ACCEPT message. Each
entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, after
having removed from the list any PLMN code that is already in the list of forbidden PLMNs. In addition, the UE shall
add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on
each receipt of the TRACKING AREA UPDATE ACCEPT message. If the TRACKING AREA UPDATE ACCEPT
message does not contain a list, then the UE shall delete the stored list.
System Simulator:
- cell A (belongs to TAI-1, PLMN1);
- cell B (belongs to TAI-2, PLMN1);
- cell G (belongs to TAI-7, PLMN2);

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1337 Release 9
1337
- cell I (belongs to TAI-9, PLMN3);
- cell J (belongs to TAI-10, PLMN4);
UE:
- the UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE last attempted to register on cell
I and received reject cause "forbidden PLMN" (so the "forbidden PLMN list" contains PLMN3).
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell A according to TS 36.508[18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1338 Release 9
1338
U - S Message
cell''.
Set the cell type of cell G to the '' Non-Suitable
off cell''
Set the cell type of cell I to the '' Non-Suitable
off cell''
Set the cell type of cell J to the '' Non-Suitable
off cell''
- - - -
UPDATE REQUEST message.
REQUEST
- -
3 Void. - - - -
4 Void. - - - -
5 SS responds with a TRACKING AREA
UPDATE ACCEPT message including PLMN2
and PLMN3 in the list of equivalent PLMNs.
ACCEPT
- -
COMPLETE
- -
7 Set the cell type of cell B to the ''Non-Suitable
off cell''.
Set the cell type of cell G to the '' Suitable cell''
Set the cell type of cell J to the '' Suitable cell''
- - - -
AREA UPDATE REQUEST message on cell G
(PLMN2)?
REQUEST
1 P
9 Void. - - - -
10 Void. - - - -
UPDATE ACCEPT message including PLMN1
and PLMN3 in the list of equivalent PLMNs.
ACCEPT
- -
COMPLETE
1 P
13 Set the cell type of cell G to the ''Non-Suitable
off cell''
Set the cell type of cell I to the '' Serving cell''
Set the cell type of cell J to the '' Non-Suitable
off cell''

Note: Cell I (PLMN3) belongs to the forbidden
PLMN.
- - - -
AREA UPDATE REQUEST message on cell I
(PLMN3) in next 30 seconds?
REQUEST
1 F
15 The UE is switched to manual PLMN selection
mode and is made to select PLMN3 in order to
remove PLMN3 in the forbidden PLMN list in
the UE.
- - - -
16 Check: The UE transmits a TRACKING AREA
UPDATE REQUEST message on cell I
(PLMN3).
REQUEST
- -
17 Void. - - - -
18 Void. - - - -
UPDATE ACCEPT message without the list of
equivalent PLMNs.
ACCEPT
- -
COMPLETE
1 P
20
A
SS releases the RRC connection - - - -
21 The UE is switched back to automatic PLMN
selection mode.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1339 Release 9
1339
22 Set the cell type of cell I to the '' Non-Suitable
off cell''
Set the cell type of cell B to the ''Suitable cell''
Set the cell type of cell G to the ''Serving cell''

- - - -
AREA UPDATE REQUEST message on Cell B
(PLMN1)?
REQUEST
2 P
UPDATE REJ ECT message with EMM cause
No suitable cells in tracking area.
REJ ECT
- -
AREA UPDATE REQUEST message on Cell
G (PLMN2)?
REQUEST
2 P
No suitable cells in tracking area.
REJ ECT
- -

MNC digits for
PLMN2 and
PLMN3.

MNC digits for
PLMN1 and
PLMN3.

Table 9.2.3.1.4.3.3-3: Message TRACKING AREA UPDATE REJECT (steps 24 and 26, Table
9.2.3.1.4.3.2-1)
EMM cause 00001111 B No suitable cells
in tracking area

9.2.3.1.5 Periodic tracking area update / Accepted
(1)
ensure that {
when { the periodic tracking area updating timer T3412 expires }
then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type = 'Periodic updating'}
}

(2)
with { UE in 'out of E-UTRAN coverage' and the periodic tracking area updating timer T3412 expires }
ensure that {
when { the UE enters E-UTRAN coverage }
then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type = 'Periodic updating'}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1340 Release 9
1340
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS23.401 clause 4.3.5.2
and TS 24.301 clauses 5.3.5, 5.5.3.2.1, 5.5.3.2.2 and 5.5.3.2.4.
[TS23.401 clause 4.3.5.2]

An EMM-REGISTERED UE performs periodic Tracking Area Updates with the network after the expiry of the
periodic TAU timer.
If the UE is out of E-UTRAN coverage (including the cases when the UE is camped on 2G/3G cells) when its periodic
TAU update timer expires, and ISR is activated the UE shall start the E-UTRAN Deactivate ISR timer. After the E-
UTRAN Deactivate ISR timer expires the UE shall deactivate ISR by setting its TIN to "P-TMSI". The EMM-
REGISTERED UE shall remember it has to perform a Tracking Area Update when it next returns to E-UTRAN
coverage.
[TS24.301 clause5.3.5]
Periodic tracking area updating is used to periodically notify the availability of the UE to the network. The procedure is
controlled in the UE by the periodic tracking area update timer (timer T3412). The value of timer T3412 is sent by the
network to the UE in the ATTACH ACCEPT message and can be sent in the TRACKING AREA UPDATE ACCEPT
message. The UE shall apply this value in all tracking areas of the list of tracking areas assigned to the UE, until a new
value is received.
The timer T3412 is reset and started with its initial value, when the UE goes from EMM-CONNECTED to EMM-IDLE
mode. The timer T3412 is stopped when the UE enters EMM-CONNECTED mode or EMM-DEREGISTERED state.
When timer T3412 expires, the periodic tracking area updating procedure shall be started and the timer shall be set to its
initial value for the next start.
If the UE is in another state than EMM-REGISTERED.NORMAL-SERVICE when the timer expires the periodic
tracking area updating procedure is delayed until the UE returns to EMM-REGISTERED.NORMAL-SERVICE.

The mobile reachable timer shall be reset and started with its initial value, when the MME releases the NAS signalling
connection for the UE. The mobile reachable timer shall be stopped when a NAS signalling connection is established
for the UE.
.
[TS24.301 clause5.5.3.2.1]
The periodic tracking area updating procedure is controlled in the UE by timer T3412. When timer T3412 expires, the
periodic tracking area updating procedure is started. Start and reset of timer T3412 is described in subclause 5.5.3.2.
[TS24.301 clause5.5.3.2.2]
...
b) when the periodic tracking area updating timer T3412 expires;
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1341 Release 9
1341
Additional GUTI IE.

When the tracking area updating procedure is initiated in EMM-IDLE mode, the UE may also include an EPS bearer
context status IE in the TRACKING AREA UPDATE REQUEST message, indicating which EPS bearer contexts are
active in the UE.
[TS24.301 clause5.5.3.2.4]
...
as valid.
...
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1342 Release 9
1342
U - S Message
1 The UE is powered up or switched on. - - -
connectivity to the default PDN
4 The UE responds to the authentication
procedure
6 The UE responds to the NAS security mode
command procedure
- - - -
6A
a1
options and/or APN.
6A
a2
message with GUTI-1 and with the ACTIVATE
REQUEST message.
message with the ACTIVATE DEFAULT EPS
BEARER CONTEXT ACCEPT message
10 The SS waits 6minutes. (Expire of T3412) -
REQUEST
1 P
ACCEPT.
ACCEPT
- -
COMPLETE
1 P
state on cell A with PagingUE-Identity =S-
"PS"?

- 1 -
16 Set the cell type of cell A to the ''non-Suitable
cell''.
- - -
17 The SS waits 8minutes. - - -
18 Set the cell type of cell A to the ''Serving cell''. - - -
UPDATE REQUEST message?
REQUEST
2 P
ACCEPT.
ACCEPT
- -
COMPLETE
2 P
23 Check: Does the test result of generic test - - 2 -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1343 Release 9
1343
state in cell A with PagingUE-Identity =S-
"PS"?

T3412 value
Unit '010' ''value is
incremented in
multiples of
decihours''

Timer value '00001' ''6 minutes''
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAI-1
GUTI GUTI-1

EPS update type
EPS update type value '011'B ''Periodic
updating''

Old GUTI GUTI-1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1344 Release 9
1344
T3412 value
Unit '010' ''value is
incremented in
multiples of
decihours''

Timer value '00001' ''6 minutes''
GUTI GUTI-2
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1

TAI-1

EPS update type
EPS update type value '011'B ''Periodic
updating''

Old GUTI GUTI-2

GUTI GUTI-3
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAI-1

9.2.3.1.6 Normal tracking area update / UE with ISR active moves to E-UTRAN
(1)
with { ISR activated UE in state EMM-REGISTERED and ECM_IDLE mode}
ensure that {
when { ISR activated UE reselects from E-UTRAN to UTRAN/GERAN cell belonging to the RA where the
UE is registered }
then { UE does not send ROUTING AREA UPDATE REQUEST message }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1345 Release 9
1345
(2)
with { ISR activated UE in state EMM-REGISTERED and ECM_IDLE mode }
ensure that {
when { ISR activated UE reselects from E-UTRAN to UTRAN/GERAN cell belonging to a RA which is not
the RA where the UE is registered }
then { UE sends ROUTING AREA UPDATE REQUEST message }
}

(3)
with { ISR activated UE in state GMM-REGISTERED and PMM_IDLE mode }
ensure that {
when { ISR activated UE reselects from UTRAN/GERAN to E-UTRAN cell belonging to one of the TAs of
the list of TAs where the UE is registered }
then { UE does not send TRACKING AREA UPDATE REQUEST message }
}
(4)
with { ISR activated UE in state GMM-REGISTERED and PMM_IDLE mode }
ensure that {
when { ISR activated UE reselects from UTRAN/GERAN to E-UTRAN cell belonging to a TA which is not
in the list of TAs where the UE is registered }
then { UE sends TRACKING AREA UPDATE REQUEST message }
}
(5)
with { ISR activated UE has a stored TIN value = "RAT-related TMSI" }
ensure that {
when { SS sends a Paging with "P-TMSI" to ISR activated UE on UTRAN/GERAN cell }
then { UE responds to the paging message }
}
(6)
with { ISR activated UE has a stored TIN value = "RAT-related TMSI" }
ensure that {
when { SS sends a Paging with "GUTI" to ISR activated UE on E-UTRAN cell }
then { UE responds to the paging message }
}

References: The conformance requirements covered in the present TC are specified in: 3GPP TS23.401 clause 4.3.5.6,
3GPP TS24.008 clauses 4.7.5.1.1 and 4.7.5.1.3 and 3GPP TS 24.301 clauses 5.5.3.2.2 and 5.5.3.2.4.
[TS23.401 clause 4.3.5.6]
The Idle mode Signalling Reduction (ISR) function provides a mechanism to limit signalling during inter-RAT cell-
reselection in idle mode (ECM-IDLE, PMM-IDLE, GPRS STANDBY states).
NOTE: The Idle mode Signalling Reduction function is mandatory for E-UTRAN UEs that support GERAN
and/or UTRAN and optional for core network. The UE's ISR capability in the UE Network Capability
element is for test purpose.
ISR is activated by decision of the CN nodes and shall be explicitly signalled to the UE as "ISR activation" in the RAU
and TAU signalling. The UE may have valid MM parameters both from MME and from SGSN. The "Temporary
Identity used in Next update" (TIN) is a parameter of the UE's MM context, which identifies the UE identity that the UE
shall indicate in the next RAU Request or TAU Request message. The TIN also identifies the status of ISR activation in
the UE.
The TIN can take one of the three values, "P-TMSI", "GUTI" or "RAT-related TMSI". The UE shall set the TIN when
receiving an Attach Accept, a TAU Accept or RAU Accept message according to the rules in table 4.3.5.6-1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1346 Release 9
1346
Table 4.3.5.6-1: Setting of the TIN
Message received by UE Current TIN value stored
by UE
TIN value to be set by
the UE when
recei ving message
Attach Accept via E-UTRAN
(never indicates ISR
activation)
Any value GUTI
Attach Accept via
GERAN/UTRAN
(never indicates ISR
activation)
Any value P-TMSI
TAU Accept not indicating
ISR
Any value GUTI
TAU Accept indicating ISR GUTI
P-TMSI or RAT-related
TMSI
GUTI
RAT-related TMSI
RAU Accept not indicating
ISR
Any value P-TMSI
RAU Accept indicating ISR P-TMSI
GUTI or RAT-related TMSI
P-TMSI
RAT-related TMSI

When ISR activation is indicated by the RAU/TAU Accept message but the UE shall not set the TIN to "RAT-related
TMSI" is a special situation. Here the UE has deactivated ISR due to special situation handling. By maintaining the old
TIN value the UE remembers to use the RAT specific TMSI indicated by the TIN when updating with the CN node of
the other RAT.
Only if the TIN is set to "RAT-related TMSI" ISR behaviour is enabled for the UE, i.e. the UE can change between all
registered areas and RATs without any update signalling and it listens for paging on the RAT it is camped on. If the
TIN is set to "RAT-related TMSI", the UE's P-TMSI and RAI as well as its GUTI and TAI(s) shall remain registered
with the network and shall remain valid in the UE.
Table 4.3.5.6-1: Old temporary UE Identity that the UE shall indicate in TAU/RAU Request (as old
GUTI or as old P-TMSI/RAI)
Message to be sent
by UE
TIN value: P-TMSI TIN value: GUTI TIN value: RAT-
related TMSI
TAU Request GUTI mapped from
P-TMSI/RAI
GUTI GUTI
RAU Request P-TMSI/RAI P-TMSI/RAI mapped
from GUTI
P-TMSI/RAI
Attach Request via E-
UTRAN
GUTI mapped from
P-TMSI/RAI
GUTI GUTI
Attach Request via
GERAN/UTRAN
P-TMSI/RAI P-TMSI/RAI mapped
from GUTI
P-TMSI/RAI

Table 4.3.5.2-1 shows which temporary identity the UE shall indicate in a Tracking or Routing Area Update Request of
in an Attach Request message, when the UE stores these as valid parameters.
Situations may occur that cause unsynchronized state information in the UE, MME and SGSN. Such special situations
trigger a deactivation of ISR locally in the UE.

[TS24.008 clause 4.7.5.1.1]

If the MS supports S1 mode, the MS shall handle the P-TMSI IE as follows:
- If the TIN indicates "GUTI" and the MS holds a valid GUTI, the MS shall map the GUTI into a P-TMSI,
P-TMSI signature and RAI as specified in 3GPP TS 23.003 [4]. The MS shall include the mapped RAI in the
Old routing area identification IE and the mapped P-TMSI signature in the P-TMSI signature IE. When the
routing area updating procedure is initiated in Iu mode, the MS shall also include the mapped P-TMSI in the
P-TMSI IE. Additionally, in Iu mode and A/Gb mode, if the MS holds a valid P-TMSI and RAI, the MS shall

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1347 Release 9
1347
indicate the P-TMSI in the Additional mobile identity IE and the RAI in the Additional old routing area
identification IE.
- If the TIN indicates "P-TMSI" or "RAT-related TMSI" and the MS holds a valid P-TMSI and RAI, the MS shall
indicate the RAI in the Old routing area identification IE. When the routing area updating procedure is initiated
in Iu mode, the MS shall also include the P-TMSI in the P-TMSI IE.

[TS24.008 clause 4.7.5.1.3]

In order to indicate to the MS that the GUTI and TAI list assigned to the MS remain registered with the network and are
valid in the MS, the network shall indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT
message that ISR is activated.
If the ROUTING AREA UPDATE ACCEPT message contains
i) no indication that ISR is activated, an MS supporting S1 mode shall set the TIN to "P-TMSI"; or
ii) an indication that ISR is activated, the MS shall regard the available GUTI and TAI list as valid and registered
with the network. If the TIN currently indicates "GUTI", the MS shall set the TIN to "RAT-related TMSI".
[TS24.301 clause5.5.3.2.2]

If the UE supports neither A/Gb mode nor Iu mode, the UE shall include a valid GUTI in the Old GUTI IE in the
TRACKING AREA UPDATE REQUEST message.
Additional GUTI IE.

[TS24.301 clause5.5.3.2.4]
The network may also indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that
ISR is active. If the TRACKING AREA UPDATE ACCEPT message contains:
i) no indication that ISR is activated, the UE shall set the TIN to "GUTI";
ii) an indication that ISR is activated, the UE shall regard a previously assigned P-TMSI and RAI as valid and
registered with the network. If the TIN currently indicates "P-TMSI", the UE shall set the TIN to "RAT-related
TMSI".
System Simulator:
- cell A (belongs to TAI-1, home PLMN) is set to ''Non- Suitable cell'';
- cell B (belongs to TAI-2, home PLMN) is set to ''Non- Suitable cell'';

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1348 Release 9
1348
- if pc_UTRAN, cell 5 and cell 7 (belong to RAI-1, home PLMN) are configured;
system information combination 9 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;- if NOT
pc_UTRAN and pc_GERAN, cell 24 and cell 25 are configured;.
system information combination 12 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;
- cell 5 / cell 24 belong to RAI-1 (home PLMN) as specified TS34.123-1 clause 12 and is set to ''Serving cell'';
- cell 7 / cell 25 belong to RAI-2 (home PLMN) as specified TS34.123-1 clause 12 and is set to ''Non- Suitable
cell'';
- system information indicate that NMO 1 is used.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1349 Release 9
1349
U S Message
- The following messages are sent on Cell 5 or
24
- - - -
message on Cell 5 or 24
3 The SS transmits an AUTHENTICATION AND
CIPHERING REQUEST message.
<-- AUTHENTICATION AND
CIPHERING REQUEST
- -
4 The UE transmits an AUTHENTICATION AND
CIPHERING RESPONSE message.
--> AUTHENTICATION AND
CIPHERING RESPONSE
- -
including P-TMSI-1 (TIN set to P-TMSI) and
RAI-1.

message.
7 The UE transmits an ACTIVATE PDP
CONTEXT REQUEST message
--> ACTIVATE PDP CONTEXT
REQUEST
- -
8 The SS responds with an ACTIVATE PDP
CONTEXT ACCEPT message
<-- ACTIVATE PDP CONTEXT
ACCEPT
- -
9 Set the cell type of cell 5 or 24 to the ''Non-
Suitable cell''.
Set the cell type of cell A to the ''Serving cell''.
- - - -
10 The UE sends TRACKING AREA UPDATE
REQUEST message.
REQUEST
- -
ACCEPT including GUTI-1(TIN set to RAT-
related TMSI) and TAI-1.
ACCEPT
- -
COMPLETE message.
COMPLETE
- -
cell''.
Set the cell type of cell 5 or 24 to the ''Serving
cell''.
- - - -
14 Check: Does the UE transmit a ROUTING
next 30 seconds on cell 5 or 24?
REQUEST
1 F
5 or 24 with P-TMSI-1 for PS domain?

Note: There is no appreciate generic
procedures in TS36.508/TS51.010-1.(FFS)
- - 1, 5 -
Suitable cell''.
Set the cell type of cell A to the ''Serving cell''.
- - - -
REQUEST
3 F
state on cell A with PagingUE-Identity =S-
"PS"?

- - 3, 6 -
18
A
Set the cell type of cell A to the ''Non-Suitable
cell''.
cell''.
- - - -
18
B
Check: Does the UE transmit a ROUTING
next 30 seconds on cell 5 or 24?
REQUEST
1 F
19 Set the cell type of cell 5 or 24 to the ''Non- - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1350 Release 9
1350
Suitable cell''.
REQUEST
4 P
ACCEPT including GUTI-2 and TAI-2.
ACCEPT
- -
COMPLETE message.
COMPLETE
- -
state on cell B with PagingUE-Identity =S-
"PS"?

- - 6 -
24 Set the cell type of cell B to the ''Non-Suitable
cell''.
cell''.
- - - -
AREA UPDATE REQUEST message with P-
TMSI and RAI on cell 7 or 25?
REQUEST
2 P
26 The SS sends ROUTING AREA UPDATE
ACCEPT message with P-TMSI-2 and RAI-2.
ACCEPT
- -
27 The UE sends ROUTING AREA UPDATE
COMPLETE message.
COMPLETE
- -
Suitable cell''.
- - - -
state on cell B with PagingUE-Identity =S-
"PS"?

- - 6 -

Old GUTI Mapped from the P-TMSI
and RAI allocated in step
5

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1351 Release 9
1351
EPS update result '100'B ''TA updated and
ISR activated''
TA only
'101'B ''combined TA/LA
updated and ISR
activated''
combined_
TA_LA
GUTI GUTI-1
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAI-1

Old GUTI GUTI-1

EPS update result '001'B ''TA updated and
ISR activated''

GUTI GUTI-2
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAI-2

9.2.3.1.7 Void
9.2.3.1.8 UE receives an indication that the RRC connection was released with cause
"load balancing TAU required"
(1)
with { UE in state EMM-REGISTERED and EMM-CONNECTED mode}
ensure that {
when { UE receives RRC CONNECTION RELEASE message with cause "load balancing TAU required" and
enters EMM-REGISTERED and EMM-IDLE mode}
then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type = "TA updating"}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1352 Release 9
1352
5.5.3.2.2 and 5.5.3.2.4.
[TS24.301 clause5.5.3.1]

- MME load balancing;

[TS24.301 clause5.5.3.2.2]

e) when the UE receives an indication from the lower layers that the RRC connection was released with cause "load
balancing TAU required";

[TS24.301 clause5.5.3.2.4]
If the tracking area update request has been accepted by the network, the MME shall send a TRACKING AREA
UPDATE ACCEPT message to the UE. If the MME assigns a new GUTI for the UE, a GUTI shall be included in the
TRACKING AREA UPDATE ACCEPT message. In this case, the MME shall start timer T3450 and enter state EMM-
COMMON-PROCEDURE-INITIATED as described in subclause 5.4.1. The MME may include a new TAI list for the
UE in the TRACKING AREA UPDATE ACCEPT message.

Upon receiving a TRACKING AREA UPDATE ACCEPT message, the UE shall stop timer T3430, reset the tracking
as valid.

System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1353 Release 9
1353
U - S Message
1 The SS transmits RRCConnectionReleaese
with cause "load balancing TAU required".
- - - -
REQUEST
1 P
ACCEPT. (Note)
ACCEPT
- -
COMPLETE message.
COMPLETE
- -
Note: The SS assigns a different MME Identifier (MMEI) value in a GUTI.

GUTI GUTI-2

9.2.3.1.9a Normal tracking area update / NAS signalling connection recovery
(1)
with { UE in state EMM-REGISTERED and EMM-CONNECTED }
ensure that {
when { UE receives an indication of "RRC Connection failure" from the lower layers }
then { UE initiates the tracking area updating procedure }
}

5.5.3.2.2 and TS 36.331, clause 5.3.7.8 and 5.3.12.
[TS 24.301, clause 5.5.3.1]
...
- recovery from certain error cases (for details see subclauses 5.5.3.2.2 and subclause 5.5.3.3.2);
[TS 24.301, clause 5.5.3.2.2]
...
i) when the UE receives an indication of "RRC Connection failure" from the lower layers and has no signalling or
user uplink data pending (i.e when the lower layer requests NAS signalling connection recovery);
...
For all cases except case b, the UE shall set the EPS update type IE to "TA updating". For case b, the UE shall set the
EPS update type IE to "periodic updating".
[TS 36.331, clause 5.3.7.8]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1354 Release 9
1354
Upon receiving the RRCConnectionReestablishmentReject message, the UE shall:
[TS 36.331, clause 5.3.12]
...
System Simulator:
- cell A and cell M (same TA);
- cell A is "Serving cell" and cell M is "non-Suitable cell";
UE:
none.
Preamble:
- the UE is in state Generic RB Established (state 3) with EPSOnlyAttachForced on cell A according to TS 36.508
[18].
U - S Message
1 Set the cell type of Cell A to the non-Suitable
cell. Set the cell type of Cell M to the "Serving
cell".
- - - -
- - - -
RRCConnectionReestablishmentRequest.
- - - -
RRCConnectionReestablishmentReject.
- - - -
AREA UPDATE REQUEST with the EPS
update type set to 'TA updating' in the next 10
seconds?
REQUEST
1 P
ACCEPT
- -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1355 Release 9
1355
Old GUTI GUTI-1

Table 9.2.3.1.9a.3.3-2: Message TRACKING AREA UPDATE ACCEPT (step 5, Table 9.2.3.1.9a.3.2-1)
GUTI Not present

9.2.3.1.10 Normal tracking area update / Rejected / IMSI invalid
(1)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to ''Illegal
UE'' }
EMM-DEREGISTERED }

(2)
with { The UE is in the state EMM-DEREGISTERED }
ensure that {
when { UE is powered up }
then { UE send ATTACH REQUEST message with Old GUTI or IMSI IE = ''IMSI''}

5.5.3.2.5.
[TS24.301 clause5.5.3.2.5]
If the tracking area updating cannot be accepted by the network, the MME sends a TRACKING AREA UPDATE
REJ ECT message to the UE including an appropriate EMM cause value.
Upon receiving the TRACKING AREA UPDATE REJ ECT message, the UE shall stop timer T3430, stop any
transmission of user data, and take the following actions depending on the EMM cause value received.
#3 (Illegal UE); or
.
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall
consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed.
The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS
update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and the MM
parameters update status, TMSI, LAI and ciphering key sequence number as specified in 3GPP TS 24.008 [13]
for the case when the normal routing area updating procedure is rejected with the GMM cause with the same
value. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC
containing the USIM is removed.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1356 Release 9
1356
System Simulator:,
- cell B (belongs to TAI-2, home PLMN) is set to ''Non-suitable cell'';
- cell G (belongs to TAI-7 ,visited PLMN) is set to ''Non-suitable cell'';
- if pc_UTRAN, cell 5 (UTRAN, belong to RAI-1) is set to "Non-suitable cell";
- if pc_GERAN and NOT pc_UTRAN, cell 24 (GERAN, belong to RAI-1) is set to "Non-suitable cell". is set to
''Non- Suitable cell''.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1357 Release 9
1357
U - S Message
1 Set the cell type of cell A to the ''Non-
Suitable cell''.
Set the cell type of cell B to the ''Serving
cell''.
- - - -
UPDATE REQUEST on Cell B.
REQUEST
- -
UPDATE REJ ECT message with EMM
cause ="Illegal UE" as specified.
REJ ECT
- -
cell''.
Set the cell type of cell B to the ''Non-
Suitable cell''.
- - - -
REQUEST message in the next 30 seconds
on cell A?

Note: Cell A belongs to the same PLMN
where the UE was rejected but a different
TAC
command.
- - - -
on cell A?
9 Set the cell type of cell A to the '' Non-
Suitable cell''.
Set the cell type of cell G to the ''Serving
cell''.
- - - -
on cell G?

rejected.
command.
- - - -
on cell G?
13 Set the cell type of cell G to the ''Non-
Suitable cell''.
Set the cell type of cell 5 or 24 to the
''Serving cell''.

EXCEPTION: Steps 14a1 to 14a2 describe
supported

14a1 IF pc_GERAN or pc_UTRAN THEN the user
initiates an attach by MMI or by AT
command.
- - - -
on cell 5 or 24?
15 If possible (see ICS) switch off is performed
or the USIM is removed.
- - - -
cell''.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1358 Release 9
1358
Set the cell type of cell G to the ''Non-
Suitable cell''.
Set the cell type of cell 5 or 24 to the ''Non-
Suitable cell''.
USIM is inserted.
- - - -
on cell A?
19-
30
- - - -
- At the end of this test procedure sequence,
the UE is in end state E-UTRA connected
(E2) according to TS 36.508.
- - - -

Old GUTI GUTI-1
Old P-TMSI signature P-TMSI Signature-1

Table 9.2.3.1.10.3.3-2: Message TRACKING AREA UPDATE REJECT (step 3, Table 9.2.3.1.10.3.2-1)
EMM cause 00000011 #3 "Illegal UE"


9.2.3.1.11 Normal tracking area update / Rejected / Illegal ME
(1)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to "Illegal
ME" }
EMM-DEREGISTERED }

(2)
ensure that {
when { UE is powered up }
then { UE send ATTACH REQUEST message with Old GUTI or IMSI IE = ''IMSI''}

5.5.3.2.5.
[TS24.301 clause5.5.3.2.5]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1359 Release 9
1359

#6 (Illegal ME);
for the case when the normal routing area updating procedure is rejected with the GMM cause with the same
value. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC
containing the USIM is removed.
The test description is identical to the one of subclause 9.2.3.1.10 except that the reject cause #3 "Illegal UE" is replaced
with the reject cause #6 "Illegal ME".
9.2.3.1.12 Normal tracking area update / Rejected / EPS service not allowed
(1)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to ''EPS
service not allowd'' }
then { UE considers the USIM as invalid for EPS services and enters state EMM-DEREGISTERED }

(2)
ensure that {
when { UE is powered up or switched on }
then { UE sends ATTACH REQUEST message with 'Old GUTI or IMSI IE = 'IMSI''}

5.5.3.2.5.
[TS24.301 clause5.5.3.2.5]


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1360 Release 9
1360
update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in
3GPP TS 24.008 [13] for the case when the normal routing area updating procedure is rejected with the GMM
System Simulator:
- cell G (belongs to TAI-7, visited PLMN) is set to ''Non-suitable cell'';
- if pc_UTRAN, cell 5 (UTRAN, belongs to RAI-1) is set to "Non-suitable cell";
- if pc_GERAN and NOT pc_UTRAN, cell 24 (GERAN, belongs to RAI-1) is set to "Non-suitable cell".
UE:
- The UE is configured to initiate EPS attach;
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1361 Release 9
1361
U - S Message
Suitable cell''.
cell''.
- - - -
REQUEST
- -
cause =''EPS services not allowed'' as
specified.
REJ ECT
- -
cell''.
Set the cell type of cell B to the ''Non-
Suitable cell''.
- - - -
on cell A?

TAC
command.
- - - -
on cell A?
9 Set the cell type of cell A to the '' Non-
Suitable cell''.
Set the cell type of cell G to the ''Serving
cell''.
- - - -
on cell G?

rejected.
command.
- - - -
on cell G?
13 Set the cell type of cell G to the ''Non-
Suitable cell''.
Set the cell type of cell 5 or 24 to the
''Serving cell''.
- - - -
EXCEPTION: Steps 14a1 to 14b2 describe
supported

14a1 IF pc_CS THEN the UE registers on CS
domain See TS 34.108 or TS 51.010
- - - -
14b1 IF pc_GERAN or pc_UTRAN THEN the user
initiates an attach by MMI or by AT
command.
- - - -
14b2 Check: Does the UE transmit an ATTACH
on cell 5 or 24?
15 If possible (see ICS) switch off is performed
or the USIM is removed.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1362 Release 9
1362
cell''.
Set the cell type of cell G to the ''Non-
Suitable cell''.
Set the cell type of cell 5 or 24 to the ''Non-
Suitable cell''.
- - - -
USIM is inserted.
- - - -
on cell A?
19-
30
- - - -
- - - -

Old GUTI GUTI-1
Old P-TMSI signature P-TMSI Signature-1

EMM cause '00000111'B #7 "EPS service
not allowed''


9.2.3.1.13 Normal tracking area update / Rejected / UE identity cannot be derived by the
network
(1)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to ''UE
identity cannot be derived by the network'' }
then { UE deletes any GUTI, last visited registered TAI, TAI list and KSI and enters the state
EMM-DEREGISTERED and subsequently, UE automatically initiates the attach procedure}

5.5.3.2.5.
[TS24.301 clause5.5.3.2.5]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1363 Release 9
1363

#9 (UE identity cannot be derived by the network);
The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall delete
the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.
Subsequently, the UE shall automatically initiate the attach procedure.
System Simulator:
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1364 Release 9
1364
U - S Message
cell''.
- - - -
REQUEST
- -
='' UE identity cannot be derived by the
network '' as specified.
REJ ECT
- -
EXCEPTION: Steps 4 describe the behaviour
that depends on UE behaviour (Note 1).

cell B?
6-
17
- - - -
- - - -
Note 1: SS should wait for 1 second to receive the Attach Request on the existing RRC Connection. In case
ATTACH REQUEST is not received within 1 second than existing RRC Connection should be released.

Old GUTI GUTI-1
Old P-TMSI signature Absent or any allowed
value

EMM cause '00001001'B #9 ''UE identity
cannot be derived
by the network''


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1365 Release 9
1365
EMM cause '0000 1111'B #15 ''No suitable
cells in tracking
area''

9.2.3.1.14 Normal tracking area update / Rejected / UE implicitly detached
(1)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to ''UE
implicitly detached'' }
then { UE enters the state EMM-DEREGISTERED.NORMAL-SERVICE and sends ATTACH REQUEST message}

5.5.3.2.5.
[TS24.301 clause5.5.3.2.5]

#10 (Implicitly detached);
The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NORMAL-
SERVICE. The UE shall then perform a new attach procedure.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM state as specified in
System Simulator:
- cell A belongs to TAI-1, home PLMN) is set to ''Serving cell'';
- cell B belongs to TAI-2, home PLMN is set to ''Non- Suitable cell'';
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1366 Release 9
1366
U - S Message
cell''.
- - - -
REQUEST
- -
=''UE implicitly detached'' as specified.
REJ ECT
- -
cell B?
5-
16
- - - -
- - - -

Old GUTI GUTI-1
Old P-TMSI signature P-TMSI signature-1 pc_GERA
N or
pc_UTRAN

EMM cause '00001010'B #10 ''UE implicitly
detached''

N or
pc_UTRAN

9.2.3.1.15 Normal tracking area update / Rejected / PLMN not allowed
(1)
with { UE has sent a TRACKING AREA UPDATE REQUEST message }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to "PLMN not
allowed" }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1367 Release 9
1367
"forbidden PLMN list" }
}

(2)
with { UE is switched off having a PLMN stored in the "forbidden PLMN list" }
ensure that {
when { UE is powered up on this PLMN }
}

(3)
with { UE in EMM-DEREGISTERED.PLMN-SEARCH state having a PLMN stored in the "forbidden PLMN list" }
ensure that {
when { UE enters a cell which is not in the "forbidden PLMN list" }
then { UE initiates an attach procedure }
}

(4)
with { UE in E-UTRA EMM-DEREGISTERED.PLMN-SEARCH state having a PLMN stored in the "forbidden PLMN
list" }
ensure that {
when { UE is in a forbidden PLMN cells and when the PLMN is selected manually }
}

5.5.3.2.5.
[TS24.301 clause5.5.3.2.5]

subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall reset
the tracking area updating attempt counter, delete the list of equivalent PLMNs and enter the state EMM-
update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating
attempt counter and the MM parameters update status, TMSI, LAI, ciphering key sequence number and the
location update attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal routing area
updating procedure is rejected with the GMM cause with the same value and no RR connection exists.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1368 Release 9
1368
System Simulator:
- cell G (belongs to TAI-7, visited PLMN) and is set to ''Serving cell'';
- cell H (belongs to TAI-8, visited PLMN) is set to ''Non-suitable cell";
- cell I (belongs to TAI-9, visited PLMN) is set to ''Non-suitable cell'';
- if pc_UTRAN, cell 5 (UTRAN, belongs to RAI-1) is set to "Non-suitable cell";
- if pc_GERAN and NOT pc_UTRAN, cell 24 (GERAN, belongs to RAI-1) is set to "Non-suitable cell".
UE:
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell G according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1369 Release 9
1369
U - S Message
cell''.
Set the cell type of cell H to the ''Serving cell''.
Note: cell G and cell H are in the same PLMN.
- - - -
UPDATE REQUEST on Cell H.
REQUEST
- -
=''PLMN not allowed''.
REJ ECT
- -
cell H?
- - - -
7 Set the cell type of cell G to the ''Serving cell''.
Set the cell type of cell H to the ''Non-Suitable
cell''.
- - - -
USIM is inserted.
- - - -
cell G?
command.
- - - -
cell G?
cell''.
cell''.

Note: Cell G and Cell 5 or 24 are in the same
PLMN.
- - - -
supported
- - - -
13a
1
IF pc_GERAN or pc_UTRAN THEN the user
- - - -
13a
2
cell 5 or 24?
14 The following messages are sent and shall be
received on cell I.
- - - -
15 Set the cell type of cell 5 or 24 to the '' Non-
Suitable cell''.
Set the cell type of cell I to the ''Serving cell''.

Note: cell 5 or 24 and cell I are in different
PLMNs.
- - - -
request PDN connectivity to the default PDN?
18 The UE responds properly to the --> AUTHENTICATION RESPONSE - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1370 Release 9
1370
- - - -
20
Aa
1
options and/or APN.
20
Aa
2
- - - -

received on cell G.
- - - -
27 Set the cell type of cell G to the '' Serving cell''.
cell''.

Note: Cell G belongs to the forbidden PLMN.
- - - -
USIM is inserted.
- - - -
mode and is made to select the forbidden
PLMN.
- - - -
31-
42
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1371 Release 9
1371
Old GUTI GUTI-7
N or
pc_UTRAN

EMM cause '00001011'B #11 '' PLMN not
allowed ''

Old P-TMSI signature Not present pc_GERA
N or
pc_UTRAN

TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC '002'B ''TAI-9''
MNC '101'B ''TAI-9''
TAC 1 '1'B ''TAI-9''
GUTI GUTI-9


9.2.3.1.16 Normal tracking area update / Rejected / Tracking area not allowed
(1)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to ''Tracking
area not allowed '' }
then { shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall reset
the tracking area updating attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1372 Release 9
1372
SERVICE and store the current TAI in the list of "forbidden tracking areas for regional provision of
service" }

(2)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and has a TAI in the list of "forbidden
ensure that {
when { UE is in the serving cell which the UE is rejected }
then { UE does not attempt an attach procedure on any other cell}
}
(3)
ensure that {
when { UE entess a new cell in the same TAI it was rejected }
then { UE does not initiate an attach procedure}
}
(4)
ensure that {
when { UE enters a new cell with defferent TAI without in the list of "forbidden tracking areas
for regional provision of service"}
then { UE initiates attach procedure with IMSI }
}
(5)
ensure that {
when { UE is powered on and enters the cell with "forbidden tracking areas for regional provision
of service" before the UE was swithed off }
then { UE initiates attach procedure on the cell }

5.5.3.2.5.
[TS24.301 clause5.5.3.2.5]

subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall reset
SERVICE.
attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal routing area updating
procedure is rejected with the GMM cause with the same value.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1373 Release 9
1373
System Simulator:
- cell A and cell M (belong to TAI-1, home PLMN) are set to ''Non-suitable cell';'
- cell B (belongs to TAI-2, home PLMN) is set to ''Serving cell'';
- cell G (belongs to TAI-7, visited PLMN) is set to ''Non-suitable cell'';
- cell H (belongs to TAI-8, visited PLMN) is set to ''Non-suitable cell''.
UE:
- The UE is configured to initiate EPS attach.
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell B according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1374 Release 9
1374
U - S Message
1 Set the cell type of cell A to the ''Serving cell''.
Set the cell type of cell B to the ''Non-Suitable
cell''.
Set the cell type of cell G to the ''Suitable
neighbour cell''.
Set the cell type of cell H to the ''Suitable
neighbour cell''.
- - - -
UPDATE REQUEST on Cell A.
REQUEST
- -
=''Tracking area not allowed'' as specified.
REJ ECT
- -
cell G and H?
command.
- - - -
cell A?
8 Set the cell type of cell A to the '' Non-Suitable
cell ''.
Set the cell type of cell M to the ''Serving cell''.
- - - -
cell M?
Set the cell type of cell M to the ''Non-Suitable
cell ''.

- - - -
cell G including a PDN CONNECTIVITY
- - - -
15
Aa
1
options and/or APN.
15
Aa
2
17 The UE transmits an ATTACH COMPLETE --> ATTACH COMPLETE - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1375 Release 9
1375
19 The UE is switched off. - - - -
20 The UE transmit a DETACH REQUEST. --> DETACH REQUEST - -
received on cell A.
- - - -
22 Set the cell type of cell A to the '' Serving cell''.
Set the cell type of cell G to the '' Non-Suitable
cell''.

- - - -
23 The UE is powered up or switched on. - - - -
24 The UE transmits ATTACH REQUEST
connectivity to the default PDN.
25 The SS sends ATTACH REJ ECT message. <-- ATTACH REJ ECT - -

Old GUTI GUTI-7
N or
pc_UTRAN

EMM cause '00001100'B #12 ''Tracking
area not allowed''

Old P-TMSI signature Not present pc_GERA
N or
pc_UTRAN

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1376 Release 9
1376
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
PLMN=MCC/02
TAC 1=1
''MCC is set to the
same MCC stored
in EF
IMSI
''
''TAI-7''

GUTI GUTI-7


EMM cause '00001100'B #12 "Tracking
area not allowed"

9.2.3.1.17 Normal tracking area update / Rejected / Roaming not allowed in this tracking
area
(1)
with { the UE has sent TRACKING AREA UPDATE REQUEST message }
ensure that {
when { the UE receives TRACKING AREA UPDATE REJECT message with the reject cause set to "roaming
not allowed in this tracking area" }
then { the UE sets the EPS update status to EU3 ROAMING NOT ALLOWED and the UE deletes the last
visited registered TAI and the UE enters the state EMM-REGISTERED.PLMN-SEARCH and the UE stores the
current TAI in the list of "forbidden tracking areas for roaming" }
}
(2)
with { the UE is in EMM-REGISTERED.PLMN-SEARCH state and the current TAI in the list of "forbidden
tracking areas for roaming"}
ensure that {
when { the serving cell belongs to TAI where UE was rejected }
then { the UE does not attempt to send TRACKING AREA UPDATE REQUEST message }
}
(3)
with { the UE is in EMM-REGISTERED.PLMN-SEARCH state and the TAI of the current cell belongs to the
list of "forbidden tracking areas for roaming"}
ensure that {
when { the UE enters a cell belonging to same PLMN and TAI not in the list of "forbidden tracking
areas for roaming"}
then { the UE sends TRACKING AREA UPDATE REQUEST message }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1377 Release 9
1377
(4)
ensure that {
when { the UE enters a cell belonging to another PLMN }
then { the UE sends TRACKING AREA UPDATE REQUEST message }
}

(5)
with { the UE, which A/Gb mode or Iu mode is supported by the UE, in EMM-DEREGISTERED.PLMN-SEARCH
state and the list of "forbidden tracking areas for roaming" contains more than one TAI }
ensure that {
when { the UE move to UTRAN or GERAN cell }
then { the UE sends ROUTING AREA UPDATE REQUEST message }

[TS 24.301, clause 5.5.3.2.5]
...
subclause 5.1.3.3) and shall delete the list of equivalent PLMNs. The UE shall reset the tracking area updating
attempt counter and shall change to state EMM-REGISTERED.PLMN-SEARCH.
The UE shall store the current TAI in the list of "forbidden tracking areas for roaming" and shall remove the
current TAI from the stored TAI list if present.
update status and routing area updating attempt counter as specified in 3GPP TS 24.008 [13] for the case when
the normal routing area updating procedure is rejected with the GMM cause with the same value.
...
System Simulator:
- cell G (belongs to TAI-7, visited PLMN) is set to ''Serving cell'';
- cell H (belongs to TAI-8, same visited PLMN) is set to ''Non-suitable cell'';
- cell I (belongs to TAI-9, another visited PLMN) is set to ''Non-suitable cell'';
- if pc_UTRAN, cell 5 (belongs to RAI-8, visited PLMN) is set to "Non-suitable cell"; system information
- if NOT pc_UTRAN and pc_GERAN, cell 24 (belongs to RAI-8, visited PLMN) is set to "Non-suitable cell";
system information combination 5 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1378 Release 9
1378
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1379 Release 9
1379
U - S Message
cell''.
- - - -
2 The UE transmits TRACKING AREA UPDATE
REQUEST on Cell H.
REQUEST
- -
=''Roaming not allowed in this tracking area''
as specified.
REJ ECT
- -
next 30 seconds on cell H?
REQUEST
1, 2 F
cell''.
- - - -
next 30 seconds on cell G?
REQUEST
1, 3 P
8 The SS transmits TRACKING AREA UPDATE
REJ ECT message with EMM cause =
''Roaming not allowed in this tracking area'' as
specified.
REJ ECT
- -
cell''.
cell''.

PLMN.
- - - -
supported

11a
1
Check: Does the UE transmit ROUTING AREA
UPDATE REQUEST message in the next 30
seconds on cell 5 or 24?
REQUEST
5 P
11a
2
The SS transmits a ROUTING AREA UPDATE
REJ ECT message with cause ='' Roaming not
allowed in this tracking area '' as specified.
REJ ECT
- -
11a
3
The SS releases the RRC connection.
Suitable cell''.

PLMNs.
- - - -
AREA REQUEST message in the next 30
seconds on cell I?
REQUEST
1, 4 P
14 The SS sends TRACKING AREA ACCEPT
message.
ACCEPT
- -
15 The UE transmits TRACKING AREA
COMPLETE message.
COMPLETE
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1380 Release 9
1380
Table 9.2.3.1.17.3.3-1: Message TRACKING AREA UPDATE REQUEST (step 2, 7 and 13, Table
9.2.3.1.17.3.2-1)
Old GUTI GUTI-7
N or
pc_UTRAN

Table 9.2.3.1.17.3.3-2: TRACKING AREA UPDATE REJECT (step 3 and 8, Table 9.2.3.1.17.3.2-1)
allowed in this
tracking area

9.2.3.1.18 Normal tracking area update / Rejected / EPS services not allowed in this PLMN
(1)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to 'EPS
services not allowed in this PLMN' }
"forbidden PLMNs for GPRS service" }

(2)
with { UE in E-UTRA EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden PLMNs
for GPRS service" }
ensure that {
when { UE enters a cell which is in the "forbidden PLMNs for GPRS service" }
}
(3)
with { UE in EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden PLMNs for
GPRS service" }
ensure that {
when { UE enters a cell which is not in the "forbidden PLMNs for GPRS service" }
}
(4)
with { UE is switched off and a PLMN is stored in the 'forbidden PLMNs for GPRS service' }
ensure that {
when { UE is power ON in a cell with forbidden PLMNs for GPRS service }

[TS 24.301, clause 5.5.3.2.5]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1381 Release 9
1381
...
subclause 5.1.3.3). Furthermore the UE shall delete any GUTI, last visited registered TAI, TAI list and KSI. The
UE shall reset the tracking area updating attempt counter and shall enter the state EMM-
attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal routing area updating
...
System Simulator:
- cell G belongs to TAI-7(visited PLMN) and is set to ''Serving cell'';
- cell H belongs to TAI-8(visited PLMN, another TAC) and is set to ''Non-suitable cell'';
- cell I belongs to TAI-9(visited PLMN, another PLMN) and is set to ''Non-suitable cell'';
- if pc_UTRAN, cell 5 (belongs to RAI-8, visited PLMN) is set to "Non-suitable cell";
- if NOT pc_UTRAN and pc_GERAN, cell 24 (belongs to RAI-8, visited PLMN) is set to "Non-suitable cell";
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1382 Release 9
1382
U - S Message
cell''.
- - - -
UPDATE REQUEST on Cell H.
REQUEST
- -
=''EPS services not allowed in this PLMN'' as
specified.
REJ ECT
- -
on cell H?
cell''.
- - - -
command.
- - - -
on cell G?
cell''.
cell''.

PLMN.
- - - -
supported

10a
1
IF pc_GERAN or pc_UTRAN THEN the user
- - - -
10a
2
on cell 5 or 24?
received on cell I.
- - - -
Suitable cell''.

PLMNs.
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1383 Release 9
1383
17a
1
options and/or APN.
17a
2

message.
- - - -

received on cell G.

23 Set the cell type of cell G to the '' Serving cell''.
cell''.

Note: Cell G belongs to the forbidden PLMNs
for GPRS service.

USIM is inserted.
- - - -
26-
37
- - - -
- - - -

Old GUTI GUTI-7
N or
pc_UTRAN

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1384 Release 9
1384
EMM cause '0001 0000'B #16 '' EPS
services not
allowed in this
PLMN ''


TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
PLMN=002/101
TAC 1=1
''TAI-9''
GUTI GUTI-9


9.2.3.1.19 Normal tracking area update / Rejected / No suitable cells in tracking Area
(1)
with { UE is sending a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'No Suitable
Cells In tracking area' }
then { UE selects a suitable cell in another tracking area in the same PLMN and performs the
tracking area updating procedure and UE does not select a suitable cell in another PLMN}
}

[TS 24.301, clause 5.5.3.2.5]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1385 Release 9
1385
...
subclause 5.1.3.3). The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-
REGISTERED.LIMITED-SERVICE.
update status and routing area updating attempt counter as specified in 3GPP TS 24.008 [13] for the case when
the normal routing area updating procedure is rejected with the GMM cause with the same value.
...
System Simulator:
- cell C (belongs to TAI-3, home PLMN) is set to ''Non-suitable cell'';
- cell G (belongs to TAI-7, visited PLMN) is set to ''Non-suitable cell''.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1386 Release 9
1386
U - S Message
1 Set the cell type of Cell A to the "non-Suitable
cell".
Set the cell type of Cell B to the "Serving cell".
Set the cell type of Cell C to the "Suitable
neighbour cell".
Set the cell type of Cell G to the " Serving cell".
- - - -
received on Cell B.
- - - -
REQUEST
- -
UPDATE REJ ECT message with the EMM
cause set to 'No Suitable Cells In tracking
area'.
REJ ECT
- -
received on Cell C.
- - - -
REQUEST
1 P
ACCEPT
- -
COMPLETE
- -

Table 9.2.3.1.19.3.3-1: TRACKING AREA UPDATE REJECT (step 3, Table 9.2.3.1.19.3.2-1)
In tracking area

Old GUTI GUTI-1

9.2.3.1.20 Void
9.2.3.1.21 Void
9.2.3.1.22 Void
9.2.3.1.23 Normal tracking area update / Abnormal case / Success after several attempts
due to no network response / TA belongs to TAI list and status is UPDATED / TA
does not belong to TAI list or status is not UPDATED
(1)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to 'Periodic
updating' and has the tracking area updating attempt counter set to the value less than four, the
TAI of the current serving cell is included in the TAI list and the update status is equal to EU1
UPDATED }
ensure that {
when { UE detects release of the NAS signalling connection }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1387 Release 9
1387
then { UE keeps the update status to EU1 UPDATED, enters state EMM-REGISTERED.NORMAL-SERVICE and
starts timer T3411 }
}

(2)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to 'Periodic
updating', has the tracking area updating attempt counter set to the value less than four, has
detected T3430 expiry, the TAI of the current serving cell is included in the TAI list and the
update status is equal to EU1 UPDATED }
ensure that {
}

(3)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to 'TA updating'
and has the tracking area updating attempt counter set to the value less than four and the TAI of
the current serving cell is not included in the TAI list or the update status is different to EU1
UPDATED }
ensure that {
then { UE starts timer T3411, sets the update status to EU2 NOT UPDATED and changes to state
EMM-REGISTERED.ATTEMPTING-TO-UPDATE }
}

(4)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to 'TA updating',
has the tracking area updating attempt counter set to the value less than four, has detected T3430
expiry and the TAI of the current serving cell is not included in the TAI list or the update status
is different to EU1 UPDATED }
ensure that {
}

5.5.3.2.6.
[TS 24.301, clause 5.5.3.1]
A tracking area updating attempt counter is used to limit the number of subsequently rejected tracking area update
attempts. The tracking area updating attempt counter shall be incremented as specified in subclause 5.5.3.2.6.
Depending on the value of the tracking area updating attempt counter, specific actions shall be performed. The tracking
area updating attempt counter shall be reset when:
- a normal or periodic tracking area updating or a combined tracking area updating procedure is successfully
completed; or
- a normal or periodic tracking area updating or a combined tracking area updating procedure is rejected with
EMM cause #11, #12, #13, #14, #15 or #25.
Additionally the tracking area updating attempt counter shall be reset when the UE is in substate EMM-
REGISTERED.ATTEMPTING-TO-UPDATE or EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, and:
- timer T3402 expires.
[TS 24.301, clause 5.5.3.2.6]
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1388 Release 9
1388
b) Lower layer failure or release of the NAS signalling connection before the TRACKING AREA UPDATE
ACCEPT or TRACKING AREA UPDATE REJ ECT message is received
The tracking area updating procedure shall be aborted, and the UE shall proceed as described below.
c) T3430 timeout
The UE shall abort the procedure and proceed as described below. The NAS signalling connection shall be
released locally.
...
For the cases b, c, d, e, and f, the UE shall stop any ongoing transmission of user data.
For the cases b, c and d the UE shall proceed as follows:
Timer T3430 shall be stopped if still running. The tracking area updating attempt counter shall be incremented,
unless it was already set to 5.
If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is included in
the TAI list and the EPS update status is equal to EU1 UPDATED:
- the UE shall keep the EPS update status to EU1 UPDATED and enter state EMM-
REGISTERED.NORMAL-SERVICE. The UE shall start timer T3411. When timer T3411 expires the
tracking area updating procedure is triggered again.
If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is not included
in the TAI list or the EPS update status is different to EU1 UPDATED:
- the UE shall start timer T3411, shall set the EPS update status to EU2 NOT UPDATED and change to state
EMM-REGISTERED.ATTEMPTING-TO-UPDATE. When timer T3411 expires the tracking area updating
procedure is triggered again.
If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GPRS update status as
specified in 3GPP TS 24.008 [13] for the abnormal case when a normal or periodic routing area updating
procedure fails and the routing area updating attempt counter is less than 5 and the GPRS update status is
different from GU1 UPDATED.
System Simulator:
- cell A and cell B
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1389 Release 9
1389
U - S Message
1 Set the cell type of Cell A to the "Serving cell".
Set the cell type of Cell B to the "Suitable
neighbour intra-frequency cell".
- - - -
- - - -
message. The PDN CONNECTIVITY
ATTACH REQUEST message.
authentication.
NAS SECURITY MODE COMPLETE
message.
- - - -
options and/or APN.
8A The SS activates UE radio bearer test mode. - - - -
message with the T3412 value indicating 6
min. The ACTIVATE DEFAULT EPS BEARER
- - - -
NOTE: The tracking area updating attempt
counter is reset.
12 Wait for 6 min to ensure that T3412 expires. - - - -
UPDATE REQUEST message with the EPS
update type value set to 'Periodic updating'.
REQUEST
- -
counter is 1.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1390 Release 9
1390
15 The SS pages the UE using S-TMSI with CN
- - - -
16 Check: Does the UE transmit a SERVICE
REQUEST message?
17 The SS transmits a SERVICE REJ ECT
message with EMM cause set to "Congestion".
<-- SERVICE REJ ECT - -
19 Wait for 10s after step 14 to ensure that T3411
expires.
- - - -
AREA UPDATE REQUEST message with the
EPS update type value set to 'Periodic
updating'?
REQUEST
2 P
counter is reset.
ACCEPT
- -
22A Generic test procedure in TS 36.508
subclause 4.5.3A.3 is performed.
- - - -
22B Generic test procedure in TS 36.508
subclause 4.5.4.3 is performed.
NOTE: The UE enters the UE test loop mode.
- - - -
22C The SS transmits one IP packet to the UE on
bearer context.
- - - -
22D Wait for 1 s after the IP packet has been
transmitted in step 22C. (Note 1)
- - - -
22E The SS releases the RRC connection. - - - -
cell". Set the cell type of Cell B to the "Serving
cell".
- - - -
- - - -
update type value set to 'TA updating'.
REQUEST
- -
24A Wait for 15s after step 24 to ensure that IP
PDU delay timer expires.
- - - -
counter is 1.
- - - -
26 Void - - - -
REQUEST message within 5s?
--> SERVICE REQUEST 3 F
28 Wait for 10s after step 25 to ensure that T3411
expires.
- - - -
EPS update type value set to 'TA updating'?
REQUEST
4 P
ACCEPT
- -
counter is reset.
COMPLETE
- -
- - - -
the SS in step 22C to the UE test loop function before the RRCConnectionRelease message is sent by the
SS in step 22E.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1391 Release 9
1391
Table 9.2.3.1.23.3.3-0: ACTIVATE TEST MODE (step 8A, Table 9.2.3.1.23.3.2-1)

Derivation Path: 36.508, Table 4.7.2-1, condition EPSOnlyAttachForced
T3412 value 6 minutes
Timer value '0 0001'B
Unit '010'B value is
incremented in
multiples of
decihours

GUTI GUTI-1

Table 9.2.3.1.23.3.3-2: Message TRACKING AREA UPDATE REQUEST (step 13 and step 20, Table
9.2.3.1.23.3.2-1)
EPS update type
EPS update type Value '011'B Periodic updating
Old GUTI GUTI-1

GUTI Not present

Table 9.2.3.1.23.3.3-3A: CLOSE UE TEST LOOP (step 22B, Table 9.2.3.1.23.3.2-1)

Old GUTI GUTI-1

EPS update type
"Active" flag Any allowed value The UE may set
this flag due to
failing SERVICE
REQUEST
procedure.

Old GUTI GUTI-1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1392 Release 9
1392
GUTI GUTI-2

9.2.3.1.24 Void

9.2.3.1.25 Normal tracking area update / Abnormal case / Failure after 5 attempts due to no
network response
(1)
with { UE has sent a TRACKING AREA UPDATE REQUEST message and has the tracking area updating attempt
counter set to four }
ensure that {
then { UE starts timer T3402, sets the update status to EU2 NOT UPDATED, changes to state EMM-
REGISTERED.ATTEMPTING-TO-UPDATE or optionally to EMM-REGISTERED.PLMN-SEARCH in order to perform a
PLMN selection }
}

5.5.3.2.6.
[TS 24.301, clause 5.5.3.1]
completed; or
EMM cause #11, #12, #13, #14, #15 or #25.
[TS 24.301, clause 5.5.3.2.6]
...
b) Lower layer failure or release of the NAS signalling connection before the TRACKING AREA UPDATE
ACCEPT or TRACKING AREA UPDATE REJ ECT message is received
The tracking area updating procedure shall be aborted, and the UE shall proceed as described below.
...
For the cases b, c, d, e, and f, the UE shall stop any ongoing transmission of user data.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1393 Release 9
1393
...
- the UE shall start timer T3402, shall set the EPS update status to EU2 NOT UPDATED, shall delete the list
of equivalent PLMNs and shall change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE or
optionally to EMM-REGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to
3GPP TS 23.122 [6].
procedure fails and the routing area updating attempt counter is equal to 5.
System Simulator:
- cell A, cell B and cell G.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1394 Release 9
1394
U - S Message
Set the cell type of Cell B to the "non-Suitable
cell".
Set the cell type of Cell G to the "non-Suitable
cell".
- - - -
- - - -
message. The PDN CONNECTIVITY
ATTACH REQUEST message.
authentication.
message.
- - - -
options and/or APN.
- - - -
NOTE 1: The tracking area updating attempt
counter is reset.
REQUEST
- -
expire.
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1395 Release 9
1395
counter is 1.
REQUEST
- -
expire.
counter is 2.
- - - -
REQUEST
- -
expire.
counter is 3.
- - - -
REQUEST
- -
expire.
counter is 4.
- - - -
REQUEST
- -
counter is 5.
- - - -
counter is reset.
REQUEST
1 P
ACCEPT
- -
cell".
- - - -
- - - -
counter is reset.
REQUEST
- -
expire.
counter is 1.
- - - -
REQUEST
- -
expire.
counter is 2.
- - - -
REQUEST
- -
expire.
counter is 3.
- - - -
REQUEST
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1396 Release 9
1396
expire.
counter is 4.
- - - -
REQUEST
- -
counter is 5 and reset.
- - - -
37 Set the cell type of Cell B to the "non-Suitable
cell". Set the cell type of Cell G to the "Serving
cell".
- - - -
- - - -
REQUEST
1 P
ACCEPT
- -
COMPLETE
- -
- - - -

T3412 value 6 minutes
Timer value '0 0001'B
incremented in
multiples of
decihours

GUTI GUTI-1

Table 9.2.3.1.25.3.3-2: Message TRACKING AREA UPDATE REQUEST (step 13, step 15, step 17, step
19 and step 21, Table 9.2.3.1.25.3.2-1)
EPS update type
EPS update type Value '011'B Periodic updating
Old GUTI GUTI-1

Table 9.2.3.1.25.3.3-3: Message TRACKING AREA UPDATE REQUEST (step 24, step 27, step 29, step
31, step 33, step 35 and step 38, Table 9.2.3.1.25.3.2-1)
Old GUTI GUTI-1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1397 Release 9
1397
GUTI Not present

GUTI GUTI-7

9.2.3.1.26 Normal tracking area update / Abnormal case / TRACKING AREA UPDATE
REJ ECT
(1)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #95"semantically
incorrect message" }
then { the UE set the tracking area updating attempt counter to 5, start timer T3402, and
perform tracking area updating on the expiry of timers T3402}

(2)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #96" invalid mandatory
information" }

(3)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #97"message type non-
existent or not implemented" }

(4)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #99"information element
non-existent or not implemented" }

(5)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #111"protocol error,
unspecified" }

5.5.3.2.6.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1398 Release 9
1398
[TS24.301 clause5.5.3.2.6]
...
d) TRACKING AREA UPDATE REJ ECT, other causes than those treated in subclause 5.5.3.2.5
Upon reception of the EMM causes #95, #96, #97, #99 and #111 the UE should set the tracking area updating
attempt counter to 5. The UE shall proceed as described below.
- the UE shall start timer T3402, shall set the EPS update status to EU2 NOT UPDATED, shall delete the list of
equivalent PLMNs and shall change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE or optionally
to EMM-REGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to
3GPP TS 23.122 [6].
System Simulator:
- cell A and cell B.
UE:
none.
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell A according to TS 36.508 [18];
- timer T3402 value is set to 1 minute to shorten the whole TC execute time in ATTACH ACCEPT message when
bringing UE to state Registered, Idle Mode (state 2).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1399 Release 9
1399
U S Message
Suitable cell''.
cell''.
- - - -
REQUEST
- -
cause #95"semantically incorrect message"
as specified.(Note)
REJ ECT
- -
the UE re-transmit TRACKING AREA
UPDATE REQUEST message on cell B?.
REQUEST
1 P
ACCEPT
- -
7 the UE transmit a TRACKING AREA
COMPLETE
- -
8 Set the cell type of cell B to the ''Non-
Suitable cell''.
Set the cell type of cell A to the ''Serving
cell''.
- - - -
REQUEST
- -
cause #96" invalid mandatory information"
as specified. (Note)
REJ ECT
- -
UPDATE REQUEST message on cell A?
REQUEST
2 P
ACCEPT
- -
COMPLETE
- -
Suitable cell''.
cell''.
- - - -
REQUEST
- -
cause #97"message type non-existent or not
implemented".(Note)
REJ ECT
- -
UPDATE REQUEST message on cell B?
REQUEST
3 P
ACCEPT
- -
COMPLETE
- -
22 Set the cell type of cell B to the ''Non-
Suitable cell''.
Set the cell type of cell A to the ''Serving
cell''.
- - - -
REQUEST
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1400 Release 9
1400
cause #99"information element non-existent
or not implemented" as specified. (Note)
REJ ECT
- -
UPDATE REQUEST message on cell A?
REQUEST
4 P
ACCEPT
- -
COMPLETE
- -
Suitable cell''.
cell''.
- - - -
REQUEST
- -
cause #111"protocol error, unspecified" as
specified. (Note)
REJ ECT
- -
UPDATE REQUEST message on cell B?
REQUEST
5 P
ACCEPT
- -
COMPLETE
- -
Note: Upon reception of TRACKING AREA UPDATE REJ ECT message with EMM causes #95, #96, #97, #99 and
#111, timer T3402 shall be started

EMM cause 01011111 #95 "semantically
incorrect message "

EMM cause 01100000 #96 " invalid
mandatory
information "

EMM cause 01100001 #97 " message
type non-existent
or not
implemented "

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1401 Release 9
1401
EMM cause 01100011 #99 " information
element non-
existent or not
implemented "

EMM cause 01101111 #111 " protocol
error, unspecified
"

Table 9.2.3.1.26.3.3-6: Message TRACKING AREA UPDATE ACCEPT (step 6, 13, 20, 27, 34 of table
9.2.3.1.26.3.2-1)
T3402 value 1 minute The default value
is 12 minutes, use
1 minute to
shorten the whole
TC execute time

9.2.3.1.27 Normal tracking area update / Abnormal case / Change of cell into a new tracking
area
(1)
ensure that {
when { cell change into a new tracking area occurs before the tracking area updating procedure is
completed }
then { UE abort the tracking area updating procedure and re-initiate it in the new tracking area
immediately }

5.5.3.2.6.
[TS24.301 clause5.5.3.2.6]

e) Change of cell into a new tracking area
If a cell change into a new tracking area occurs before the tracking area updating procedure is completed, the
tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update
status to EU2 NOT UPDATED.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1402 Release 9
1402
System Simulator:
- cell A, cell B, cell C.
UE:
none.
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell A according to 36.508 [18].
U - S Message
cell''.
Set the cell type of cell C to the Non-Suitable
cell''.
- - - -
REQUEST
- -
3 SS does not send TRACKING AREA UPDATE
ACCEPT to the UE.
- - - -
cell''.
Set the cell type of cell B to the ''Non-Suitable
cell''.
Set the cell type of cell C to the Serving cell''.
Note: change of cell power level should
happen before timer T3430 expired.
- - - -
5 UE initiates RRC connection establishment
procedure on cell C.
- - - -
AREA UPDATE REQUEST message on cell C
REQUEST
1 P
ACCEPT message
ACCEPT
- -
8 UE sends TRACKING AREA UPDATE
COMPLETE
COMPLETE
- -

Table 9.2.3.1.27.3.3-1: Message TRACKING AREA UPDATE REQUEST (step 2, step 6, Table
9.2.3.1.27.3.2-1)
Old GUTI GUTI-1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1403 Release 9
1403
Table 9.2.3.1.27.3.3-2: Message TRACKING AREA UPDATE ACCEPT (step 7, 9.2.3.1.27.3.2-1)
GUTI GUTI-3
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAC =3

''PLMN is set to
the same
MCC/MNC stored
in EF
IMSI
''
''TAI-3''

9.2.3.1.28 Normal tracking area update / Abnormal case / Tracking area updating and
detach procedure collision
(1)
ensure that {
when { UE receives a DETACH REQUEST message before the tracking area updating procedure has been
completed }
then { the tracking area updating procedure shall be aborted and the detach procedure shall be
progressed }

5.5.3.2.6.
[TS24.301 clause5.5.3.2.6]

f) Tracking area updating and detach procedure collision
If the UE receives a DETACH REQUEST message before the tracking area updating procedure has been
completed, the tracking area updating procedure shall be aborted and the detach procedure shall be progressed.
System Simulator:
- cell A, cell B.
UE:
none.
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on Cell A according to 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1404 Release 9
1404
U - S Message
cell''.
- - - -
REQUEST
- -
3 SS does not send TRACKING AREA UPDATE
ACCEPT to the UE.
- - - -
4 The SS transmits a DETACH REQUEST
message with Detach type ='re-attach not
required' on Cell B.
Note: this message should be sent before
timer T3430 expired.
5 Check: Does The UE transmit a DETACH
ACCEPT message on Cell B in the next 6
seconds?
Note: the default value for timer T3422 is 6
seconds
paging (for NAS testing)" defined in clause
6.4.2.5 of TS36.508 indicates that the UE does
not respond to paging when paged with S-
"PS" on Cell B?
- - 1 -

Detach type 010B re-attach not
required

EMM cause '00001100'B ''Tracking area not
allowed''

9.2.3.2 Combined tracking area updating
9.2.3.2.1 Combined tracking area update / Successful
(1)
with { a combined EPS/IMSI attached UE in state EMM-REGISTERED and EMM-IDLE mode}
ensure that {
when { UE enters a tracking area included in the TAI list }
then { UE does not transmit a TRACKING AREA UPDATE REQUEST message }
}
(2)
with { a combined EPS/IMSI attached UE in state EMM-REGISTERED and EMM-IDLE mode}
ensure that {
when { UE enters a tracking area not included in the TAI list }
then { UE transmits a TRACKING AREA UPDATE REQUEST message with "EPS update type = combined TA/LA
updating" }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1405 Release 9
1405
(3)
with { UE has sent a combined TRACKING AREA UPDATE REQUEST message }
ensure that {
when { UE receives a TRACKING AREA UPDATE ACCEPT message containing a GUTI and/or a mobile
identity }
then { UE transmits a TRACKING AREA UPDATE COMPLETE message and enters EMM-REGISTERED state }
}
5.5.3.2.2, 5.5.3.2.4, 5.5.3.3.1, 5.5.3.3.2, 5.5.3.3.4.1 and 5.5.3.3.4.2.
[TS24.301 clause 5.5.3.1]
...- combined tracking area updating to update the registration of the actual tracking area for a UE in CS/PS mode 1
or CS/PS mode 2 of operation;

...
[TS24.301 clause 5.5.3.2.2]
...
...
...
...
If a UE has uplink user data pending when it initiates the tracking area updating procedure, or uplink signalling not
related to the tracking area updating procedure, it may also set an "active" flag in the TRACKING AREA UPDATE
REQUEST message to indicate the request to establish the user plane to the network and to keep the NAS signalling
connection after the completion of the tracking area updating procedure.
If the UE has a current EPS security context, the UE shall include the eKSI (either KSI
ASME
or KSI
SGSN
) in the NAS
Key Set Identifier IE in the TRACKING AREA UPDATE REQUEST message. Otherwise, the UE shall set the NAS
Key Set Identifier IE to the value "no key is available". If the UE has a current EPS security context, the UE shall
integrity protect the TRACKING AREA UPDATE REQUEST message with the current EPS security context.
Otherwise the UE shall not integrity protect the TRACKING AREA UPDATE REQUEST message.
...
When the tracking area updating procedure is initiated in EMM-IDLE mode, the UE may also include an EPS bearer
context status IE in the TRACKING AREA UPDATE REQUEST message, indicating which EPS bearer contexts are
active in the UE.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1406 Release 9
1406
...
[TS24.301 clause 5.5.3.2.4]
...
as valid.
...
...
[TS24.301 clause 5.5.3.3.1]
Within a combined tracking area updating procedure the messages TRACKING AREA UPDATE ACCEPT and
TRACKING AREA UPDATE COMPLETE carry information for the tracking area updating and the location area
updating.
The combined attach procedure basically follows the normal tracking area updating procedure described in subclause
5.5.3.2.
[TS24.301 clause 5.5.3.3.2]
...
To initiate a combined tracking area updating procedure the UE sends the message TRACKING AREA UPDATE
REQUEST to the network, starts timer T3430 and changes to state EMM-TRACKING-AREA-UPDATING-
INITIATED. The value of the EPS update type IE in the message shall indicate "combined TA/LA updating" unless
explicitly specified otherwise.
location area identification, the UE shall include it in the Old location area identification IE in the TRACKING AREA
[TS24.301 clause 5.5.3.3.4.1]
Depending on the value of the EPS update result IE received in the TRACKING AREA UPDATE ACCEPT message,
two different cases can be distinguished:
1) The EPS update result IE value indicates "combined TA/LA updated": Tracking and location area updating is
successful;
...
A TRACKING AREA UPDATE COMPLETE message shall be returned to the network if the TRACKING AREA
UPDATE ACCEPT message contains a GUTI and/or a mobile identity.
[TS24.301 clause 5.5.3.3.4.2]
The description for normal tracking area update as specified in subclause 5.5.3.2.4 shall be followed. In addition, the
following description for location area updating applies.
The TMSI reallocation may be part of the combined tracking area updating procedure. The TMSI allocated is then
included in the TRACKING AREA UPDATE ACCEPT message together with the location area identification (LAI). In
this case the MME shall change to state EMM-COMMON-PROCEDURE-INITIATED and shall start the timer T3450
as described in subclause 5.4.1. The LAI may be included in the TRACKING AREA UPDATE ACCEPT message
without TMSI.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1407 Release 9
1407
The UE, receiving a TRACKING AREA UPDATE ACCEPT message, stores the received location area identification,
resets the location update attempt counter, sets the update status to U1 UPDATED and enters MM state MM IDLE.
...
How to handle the old TMSI stored in the UE depends on the mobile identity included in the TRACKING AREA
- If the TRACKING AREA UPDATE ACCEPT message contains an IMSI, the UE is not allocated any TMSI,
and shall delete any old TMSI accordingly.
- If the TRACKING AREA UPDATE ACCEPT message contains a TMSI, the UE shall use this TMSI as new
temporary identity. The UE shall delete its old TMSI and shall store the new TMSI. In this case, a TRACKING
AREA UPDATE COMPLETE message is returned to the network to confirm the received TMSI.
- If neither a TMSI nor an IMSI has been included by the network in the TRACKING AREA UPDATE ACCEPT
message, the old TMSI, if any is available, shall be kept.
...
System Simulator:
- cell A, cell C and cell D (HPLMN, different TAs);
- at most 2 cells are active simultaneously.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1408 Release 9
1408
U - S Message
received on cell C.
- - - -
1-
13
Void - - - -
14 Set the cell type of cell A to the " non-Suitable
neighbour cell ". Set the cell type of cell C to
the " Serving cell"
- - - -
15 Check: Does the UE transmit a combined
TRACKING AREA UPDATE REQUEST
REQUEST
2 P
ACCEPT message including GUTI, TMSI and
LAI. The TAI list includes TAI for cell C and cell
D.
ACCEPT
- -
COMPLETE
2,3 P
19 Check: Does the test results of generic
procedure in TS 36.508 [18] subclause 6.4.2.4
indicate that the UE is in E-UTRA EMM-
REGISTERED state on cell C with PagingUE-
Identity =S-TMSI2?
- - 2 -
received on cell 1.
- - - -
20 Set the cell type of cell A to the " non-Suitable
off cell ". Set the cell type of cell C to the
"Suitable neighbour cell". Set the cell type of
cell D1 to the " Serving cell"
- - - -
20
A
next 30 seconds?
REQUEST
1 F
20
B
Check: Does the test results of generic
procedure in TS 36.508 [18] subclause 6.4.2.4
indicate that the UE is in E-UTRA EMM-
REGISTERED state on cell D with PagingUE-
Identity =S-TMSI2?
- - 1
20
C
Set the cell type of cell A to the "Serving cell".
Set the cell type of cell C to the "Non-suitable
off cell". Set the cell type of cell D to the
"Suitable neighbour cell".

message?
REQUEST
2 P
ACCEPT message. Note: GUTI not present
and MS identity present
ACCEPT
- -
COMPLETE
2,3 P
- - - -

NOTE 1: It is assumed in the test procedure sequence that the UE initially has a valid GUTI.
NOTE 2: NAS security procedures are not checked in this TC.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1409 Release 9
1409
NAS key set identifier KSI sent during the test
case preamble in step 7.

context (for
KSI
ASME
)

Old GUTI GUTI-1 GUTI-1 was
allocated in cell A
during the
preamble

Last visited registered TAI TAI-1 TAI of cell A
Old location area identification LAI-1 LAI received in
the ATTACH
ACCEPT
message in the
preamble

TMSI status Not Present Valid TMSI
available

GUTI GUTI-2
TAI list
Length of tracking area identity list contents '00001000'B 8 octets
Type of lis't 'B0''list of TACs
belonging to one PLMN,
with non-consecutive
TAC values''0

Number of elements '000001' 2 elements
Partial tracking area identity list PLMN =MCC/MNC
stored in EF
IMSI

TAC 1 =3
TAC 2 =4
TAI-3 and TAI-4

Old GUTI GUTI-2
TMSI status Not present Valid TMSI
available

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1410 Release 9
1410
assign a new
GUTI

TAI list
Length of tracking area identity list contents 00001000 8 octets
Number of elements 000001 1 element
Type of list 000 One PLMN with
non-consecutive
TACs

stored in EF
IMSI

TAC 1 =TAC-1
TAI-1
LAI Not present
MS identity TMSI-3 SS provides a
new TMSI

9.2.3.2.1a Combined tracking area update / Successful / Check of last visited TAI and
handling of TAI list, LAI and TMSI
(1)
with { a combined EPS/IMSI attached UE has sent a combined TRACKING AREA UPDATE REQUEST message with
EPS update type set to 'Combined TA/LA updating', including a last visited registered TAI }
ensure that {
when { the UE receives a TRACKING AREA UPDATE ACCEPT message containing a new TAI list, a location
area information(LAI) and a TMSI as the mobile identity }
then { the UE shall delete its old TMSI and shall store the new TMSI and transmits a TRACKING
AREA UPDATE COMPLETE message and enters EMM-REGISTERED state }
}
(2)
with { UE in state EMM-REGISTERED, EMM-IDLE mode and ISR not activated }
ensure that {
when { UE performs a cell reselection from E-UTRAN to UTRAN and enters a location area stored on
the USIM }
then { the UE does not perform location updating }
}
(3)
with { UE in state GMM-REGISTERED mode }
ensure that {
when { the UE receives a Paging message including an ue-Identity set to an unmatched TMSI i.e.
other than the one allocated to the UE at the UE registration procedure }
then { the UE doesnt establishe an RRC connection to answer the paging }
}
(4)
ensure that {
when { the UE receives a Paging message including an ue-Identity set to the TMSI which was
allocated to the UE }
then { the UE establishes an RRC connection to answer the paging and the TMSI and the location
area information(LAI) as Initial UE Identity are included in RRCConnectionRequest message }
}
(5)
ensure that {
area information(LAI) (Neither a TMSI nor an IMSI as the mobile identity is included) }
then { the UE shall keep the old TMSI if any available and enters EMM-REGISTERED state }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1411 Release 9
1411
(6)
ensure that {
the USIM }
}
(7)
ensure that {
when { the UE receives a Paging message including an ue-Identity set to the TMSI which was
allocated to the UE }
then { the UE establishes an RRC connection to answer the paging and the TMSI and the location
area information(LAI) as Initial UE Identity are included in RRCConnectionRequest message }
}
(8)
ensure that {
area information(LAI) and an IMSI as the mobile identity }
then { the UE shall delete any old TMSI and enters EMM-REGISTERED state }
}
(9)
ensure that {
the USIM }
}
(10)
ensure that {
when { the UE receives a Paging message including an ue-Identity set to a TMSI }
then { the UE doesnt establishe an RRC connection to answer the paging }
}

5.5.3.3.2 , 5.5.3.3.4.1 and 5.5.3.3.4.2.
[TS24.301 clause 5.5.3.3.1]
updating.
The combined tracking area updating procedure follows the normal tracking area updating procedure described in
subclause 5.5.3.2.
[TS24.301 clause 5.5.3.3.2]
The UE operating in CS/PS mode 1 or CS/PS mode 2, in state EMM-REGISTERED, shall initiate the combined
tracking area updating procedure:
a) when the UE that is attached for both EPS and non-EPS services detects entering a tracking area that is not in the
list of tracking areas that the UE previously registered in the MME;
b) when the UE that is attached for EPS services wants to perform an attach for non-EPS services. In this case the
EPS update type IE shall be set to "Combined TA/LA updating with IMSI attach";
c) when the UE performs an intersystem change from A/Gb mode to S1 mode and the EPS services were
previously suspended in A/Gb mode;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1412 Release 9
1412
d) when the UE performs an intersystem change from A/Gb or Iu mode to S1 mode and the UE previously
performed a location area update procedure in A/Gb or Iu mode, in order to re-establish the SGs association;
e) when the UE enters EMM-REGISTERED.NORMAL-SERVICE and the UE's TIN indicates "P-TMSI";
f) when the UE receives an indication from the lower layers that the RRC connection was released with cause "load
balancing TAU required";
g) when the UE deactivated EPS bearer context(s) locally while in EMM-REGISTERED.NO-CELL-AVAILABLE,
and then returns to EMM-REGISTERED.NORMAL-SERVICE;
h) when the UE changes the UE core network capability information or the UE specific DRX parameter or both;
i) when the UE receives an indication of "RRC Connection failure" from the lower layers and has no user uplink
data pending; or
j) when the UE has selected a CSG cell whose CSG identity is not included in the UE's Allowed CSG list.
[TS24.301 clause 5.5.3.3.4.1]
two different cases can be distinguished:
successful;
2) The EPS update result IE value indicates "TA updated": Tracking area updating is successful, but location area
updating is not successful.
UPDATE ACCEPT message contains a GUTI or a mobile identity or both.
[TS24.301 clause 5.5.3.3.4.2]
without TMSI.
How to handle the old TMSI stored in the UE depends on the mobile identity included in the TRACKING AREA
- If the TRACKING AREA UPDATE ACCEPT message contains an IMSI, the UE is not allocated any TMSI,
and shall delete any old TMSI accordingly.
- If the TRACKING AREA UPDATE ACCEPT message contains a TMSI, the UE shall use this TMSI as new
temporary identity. The UE shall delete its old TMSI and shall store the new TMSI. In this case, a TRACKING
AREA UPDATE COMPLETE message is returned to the network to confirm the received TMSI.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1413 Release 9
1413
- If neither a TMSI nor an IMSI has been included by the network in the TRACKING AREA UPDATE ACCEPT
message, the old TMSI, if any is available, shall be kept.
The network receiving a TRACKING AREA UPDATE COMPLETE message stops timer T3450, changes to state
EMM-REGISTERED and considers the new TMSI as valid.
System Simulator:
- cell A (belongs to TAI-1) is set to ''Serving cell'';
- cell B (belongs to TAI-2) is set to ''Non-suitable cell'';
- if pc_UTRAN:
- cell 5 (UTRA FDD or UTRA TDD, belongs to LAI-1) is set to ''Non-suitable cell''.
- cell X (UTRA FDD or UTRA TDD, belongs to LAI-2) is set to ''Non-suitable cell''.
- UTRAN is NOT using Gs interface. (NMO in System Information Block 1 indicates NMO II).
Editors note: Cell X belongs to LAI other than LAI-1 need to be defined in Table 4.4.4-2 in [18].
UE:
Preamble:
- the UE is in state Registered, Idle mode (state 2) with condition CombinedAttach on Cell A according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1414 Release 9
1414
U - S Message
received on Cell B.
- - - -
1 Set cell type of Cell A to the "non-Suitable cell"
Set cell type of Cell B to the "Serving cell".

message with Last visited registered TAI set to
TAI-1?
REQUEST
1 P
ACCEPT message including with LAI set to
LAI-2, including a new TMSI(TMSI-2) as MS
identity.
ACCEPT
- -
COMPLETE
1 P
received on Cell X.
- - - -
6 Set cell type of Cell B to the "non-Suitable cell"
Set cell type of Cell X to the "Serving cell".
- - - -
7 The UE performs Cell Reselection from Cell
B(E-UTRAN cell) to Cell X(UTRAN cell).
- - - -
8 Check: Does UE perform Location updating
procedure?
REQUEST
2 F
9 Check: Does UE perform Routing area
updating procedure?
REQUEST
- P
10 The SS send Paging message including an
unmatched identity.
<-- Paging - -
11 Check: Does the UE transmit
RRCConnectionRequest to answer the
Paging ?
12 The SS send Paging message including a
matched identity(UE Identity =TMSI-2).
<-- Paging - -
13 Check: Does the test results of Mobile
terminated establishment of Radio Resource
Connection [5] indicate that the UE transmit
RRCConnectionRequest with Initial UE identity
set to TMSI-2 and LAI-2 to answers on Paging
message ?
- - 4 P
received on Cell A.
- - - -
15 Set cell type of Cell X to the "non-Suitable cell"
Set cell type of Cell A to the "Serving cell".
- - - -
X(UTRAN cell) to Cell A(E-UTRAN cell) .

TAI-2?
REQUEST
5 P
ACCEPT message with LAI set to LAI-1, not
including MS identity.
ACCEPT
- -
received on Cell 5.
- - - -
20 Set cell type of Cell A to the "non-Suitable cell"
Set cell type of Cell 5 to the "Serving cell".
- - - -
A(E-UTRAN cell) to Cell 5(UTRAN cell).
- - - -
22 Check: Does UE perform Location updating? --> LOCATION UPDATING
REQUEST
6 F

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1415 Release 9
1415
updating procedure?
REQUEST
- P
matched identity(UE Identity =TMSI-2).
<-- Paging - -
25 Check: Does the test results of Mobile
terminated establishment of Radio Resource
Connection [5] indicate that the UE transmit
RRCConnectionRequest with Initial UE identity
set to TMSI-2 and LAI-1 to answers on Paging
message ?
- - 7 P
received on Cell B.
- - - -
27 Set cell type of Cell 5 to the "non-Suitable cell"
Set cell type of Cell B to the "Serving cell".
- - - -
5(UTRAN cell) to Cell B(E-UTRAN cell) .
- - - -
TAI-1?
REQUEST
8 P
ACCEPT message with LAI set to LAI-2,
including the IMSI as MS identity.
ACCEPT
- -
received on Cell X.
- - - -
32 Set cell type of Cell B to the "non-Suitable cell"
Set cell type of Cell X to the "Serving cell".
- - - -
B(E-UTRAN cell) to Cell X(UTRAN cell).
- - - -
34 Check: Does UE perform Location updating? --> LOCATION UPDATING
REQUEST
9 F
updating procedure?
REQUEST
- P
TMSI.
<-- Paging - -
37 Check: Deoe UE transmit
RRCConnectionRequest to answer the
Paging ?

included by UE if
if valid, IMSI
otherwise.

last TAI is
included by UE
and will be used
to establish a
good list of TAIs
in subsequent
ATTACH
ACCEPT
message.

Old LAI Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1416 Release 9
1416
GUTI Not present This IE may be
included to assign
a new GUTI

TAI list
non-consecutive
TACs

MCC
MNC
TAC 1
TAI-2
LAC 2 (LAI-2)
MS identity TMSI-2

Table 9.2.3.2.1a.3.3-3: Message PAGING TYPE 1 (step 10, Table 9.2.3.2.1a.3.2-1)
Derivation path: 34.108 sec 7.1.2.4.1
Paging record list
Paging record
CN originator
Paging cause
CN domain identity
UE identity
Terminating Speech Call
CS domain
TMSI other than TMSI-2

Paging record list
Paging record
CN originator
Paging cause
CN domain identity
UE identity
CS domain
TMSI-2

Table 9.2.3.2.1a.3.3-5: Message RRCConnectionRequest (step 13, Table 9.2.3.2.1a.3.2-1)
Derivation path: 34.108 sec 9.1.1
Initial UE identity
TMSI(GSM-MAP)
LAI (GSM-MAP)
TMSI-2
LAI-2

Establishment cause Terminating
Conversational Call

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1417 Release 9
1417
Table 9.2.3.2.1a.3.3-6 Message TRACKING AREA UPDATE REQUEST (step 17, Table 9.2.3.2.1a.3.2-1)
included by UE if
if valid, IMSI
otherwise.

last TAI is
included by UE
and will be used
to establish a
good list of TAIs
in subsequent
ATTACH
ACCEPT
message.

Old LAI LAI-2

included to assign
a new GUTI

TAI list
non-consecutive
TACs

MCC
MNC
TAC 1
TAI-1
LAC 1 (LAI-1)
MS identity Not present

Paging record list
Paging record
CN originator
Paging cause
CN domain identity
UE identity
CS domain
TMSI-2

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1418 Release 9
1418
Table 9.2.3.2.1a.3.3-9: Message RRCConnectionRequest (step 25, Table 9.2.3.2.1a.3.2-1)
Derivation path: 34.108 sec 9.1.1
Initial UE identity
TMSI(GSM-MAP)
LAI (GSM-MAP)
TMSI-2
LAI-1

Establishment cause Terminating
Conversational Call

Table 9.2.3.2.1a.3.3-10: Message TRACKING AREA UPDATE REQUEST (step 29, Table 9.2.3.2.1a.3.2-
1)
included by UE if
if valid, IMSI
otherwise.

last TAI is
included by UE
and will be used
to establish a
good list of TAIs
in subsequent
ATTACH
ACCEPT
message.

Old LAI LAI-1

EPS update result 001 "combined TA/LA"
included to assign
a new GUTI

TAI list
non-consecutive
TACs

MCC
MNC
TAC 1
TAI-2
LAC 2(LAI-2)
MS identity IMSI

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1419 Release 9
1419
Paging record list
Paging record
CN originator
Paging cause
CN domain identity
UE identity
CS domain
TMSI (any value)

9.2.3.2.1b Combined tracking area update / Success / SMS only
9.2.3.2.1b.1 Test Purpose (TP)
(1)
with { UE, operating in CS/PS mode 1, has sent a combined TRACKING AREA UPDATE REQUEST message }
ensure that {
when { UE receives a TRACKING AREA UPDATE ACCEPT message containing a GUTI and/or a mobile
identity and Additional update result IE 'SMS only'}
then { UE does not transmit a TRACKING AREA UPDATE COMPLETE message and enters EMM-REGISTERED
state }
}
(2)
with { UE, operating in CS/PS mode 1 with "IMS voice not available", in state EMM-REGISTERED and
state MM-IDLE}
ensure that {
when { SS activate UTRAN cell or GERAN cell}
then { UE automatically disable to E-UTRAN capability and performs a registration to UTRAN cell
or GERAN cell}
}
(3)
with { UE, operating in CS/PS mode 1 without "IMS voice not available" or in CS/PS mode2, in state
ensure that {
when { SS sends Paging message with PS domain }
then { UE sends SERVICE REQUEST message }
}

(4)
with { UE, operating in CS/PS mode 1 without "IMS voice not available" or in CS/PS mode2, in state
ensure that {
then { UE does not respond paging message}

9.2.3.2.1b.2 Conformance requirements
5.5.3.3.2, 5.5.3.3.4.1, 5.5.3.3.4.2 and 5.6.2.4.
[TS24.301 clause 5.5.3.3.1]
updating.
The combined tracking area updating procedure follows the normal tracking area updating procedure described in
subclause 5.5.3.2.
[TS24.301 clause 5.5.3.3.2]
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1420 Release 9
1420
If the UE initiates the combined tracking area updating procedure for EPS services and "SMS only", the UE shall
indicate "SMS only" in the Additional update Type IE.
[TS24.301 clause 5.5.3.3.4.1]
the following different cases can be distinguished:
successful for EPS and non-EPS services, or for EPS services and "SMS only";
...
UPDATE ACCEPT message contains a GUTI or a mobile identity or both.
[TS24.301 clause 5.5.3.3.4.2]
without TMSI.
...
If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "SMS only"
or "CS Fallback not preferred", a UE operating in CS/PS mode 1 with "IMS voice not available" shall attempt to select
GERAN or UTRAN radio access technology rather than E-UTRAN for the selected PLMN or equivalent PLMN. The
UE shall disable the E-UTRA capability (see subclause 4.5). If the UE is in the EMM-CONNECTED mode, the UE
shall locally release the established NAS signalling connection and enter the EMM-IDLE mode before selecting
GERAN or UTRAN radio access technology.
If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "SMS only",
a UE operating in CS/PS mode 2 shall not attempt to use CS fallback for mobile originating services.

[TS24.301 clause5.6.2.4]
The network shall initiate the paging procedure when it receives an incoming mobile terminating SMS to the UE that is
IMSI attached for non-EPS services or for "SMS only", and no NAS signalling connection exists.
To initiate the procedure for SMS when no NAS signalling connection exists, the EMM entity in the network requests
the lower layer to start paging (see 3GPP TS 36.413 [23]). The paging message shall include a CN domain indicator set
to "PS". The paging procedure is performed according to subclause 5.6.2.2.1. The MME shall not start timer T3413 for
this procedure.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1421 Release 9
1421
9.2.3.2.1b.3 Test description
9.2.3.2.1b.3.1 Pre-test conditions
System Simulator:
- Cell A and Cell B are configured according to Table 6.3.2.2-1 in [18].
- Cell A belongs to TAI-1(home PLMN) is set to ''Serving Cell''.
- Cell B belongs to TAI-2(home PLMN and another TAC) is set to ''Non-Suitable cell''
- If pc_UTRAN supported by UE, Cell 5.
- If pc_GERAN and NOT pc_UTRAN supported by UE, Cell 24.
Set the cell type of cell 5 or cell 24 to the '' Non-Suitable cell ''.
UE:
- The UE is configured to initiate combined EPS/IMSI attach.
Preamble:
- The UE is in state Registered, Idle Mode (state 2) on cell A according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1422 Release 9
1422
9.2.3.2.1b.3.2 Test procedure sequence
Table 9.2.3.2.1b.3.2-1: Main Behaviour
U - S Message
The following messages are sent and shall
be received on Cell B
- - - -
Suitable cell''.
cell''.

2 UE transmits a combined TRACKING AREA
REQUEST
- -
ACCEPT message including GUTI, TMSI
and LAI. The TAI list includes TAI for cell C
and cell D.
ACCEPT
- -
COMPLETE
1 F
EXCEPTION: Steps 6a1 to 6b4 describe
supported

6a1 IF CS/PS mode 1 of operation is configured
on the UE THEN set the cell type of cell A to
the ''Serving cell'' and set the cell type of cell
5 or cell 24 to the ''Suitable neighbour cell ''.
- - - -
6a2 The following messages are sent and shall
be received on Cell 5 or Cell 24.
- - - -
6a3 Check: Does the UE transmit ROUTING
next 30 seconds?
REQUEST
2 P
6a4 The SS transmits a ROUTING AREA
ACCEPT
- -
6a5 The UE transmits a ROUTING AREA
COMPLETE
- -
6b1 ELSE no change cell configuration. - - - -
6b2 Check: Does the UE respond to paging on
cell B with S-TMSI in GUTI-2 for PS
domain?(Generic Procedure TS36.508
6.4.2.4)
- - 3 -
6b3 The SS transmits a paging on cell B with S-
- - - -
6b4 Check: Does the UE send EXTENDED

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1423 Release 9
1423
9.2.3.2.1b.3.3 Specific message contents
Table 9.2.3.2.1b.3.3-1: Message TRACKING AREA UPDATE REQUEST (step 2, Table 9.2.3.2.1b.3.2-1)
Derivation path: 36.508 table 4.7.2-27 with condition CombinedAttach
Old GUTI GUTI-1 GUTI-1 was
allocated in cell A
during the
preamble

Last visited registered TAI TAI-1 TAI of cell A
Old location area identification LAI-1 LAI received in
the ATTACH
ACCEPT
message in the
preamble

available

Table 9.2.3.2.1b.3.3-2: Message TRACKING AREA UPDATE ACCEPT (step 3, Table 9.2.3.2.1b.3.2-1)
Derivation path: 36.508 table 4.7.2-24 with condition CombinedAttach
GUTI GUTI-2
TAI list
Length of tracking area identity list contents '00000110'B 6 octets
Type of lis't 'B0''list of TACs
belonging to one PLMN,
with non-consecutive
TAC values''0

Number of elements '00000' 1 elements
stored in EF
IMSI

TAC 1 =2
TAI-2
Additional update result '10'B SMS only

Table 9.2.3.2.1b.3.3-3: Message EXTENDED SERVICE REQUEST (step 6b4, Table 9.2.3.2.1b.3.2-1)
Derivation Path: 36.508 table 4.7.2.-14A
Service type '0001'B ''mobile
terminating CS
fallback or 1xCS
fallback''

M-TMSI M-TSMI2 ''M-TMSI2 is a
part of GUTI-2''

CSFB response '001'B

9.2.3.2.1c Combined tracking area update / Success / CS Fallback not preferred
9.2.3.2.1c.1 Test Purpose (TP)
(1)
with { UE operating in CS/PS mode 2 in state EMM-REGISTERED-INITIATED}
ensure that {
when { UE receives a TRACKING AREA UPDATE ACCEPT message with EPS network feature support IE
indicating that IMS voice over PS session in S1 mode NOT supported and Additional update result
IE indicating CS Fallback not preferred}
then { UE stays on the E-UTRAN cell.}
}

(2)
with { UE operating in CS/PS mode 2}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1424 Release 9
1424
ensure that {
when receives a TRACKING AREA UPDATE ACCEPT message with EPS network feature support IE
IE indicating CS Fallback not preferred }
then { The UE is able to initiate an MO-CS fallback call}
}

(3)
with { UE operating in CS/PS mode 2}
ensure that {
when receives a TRACKING AREA UPDATE ACCEPT message with EPS network feature support IE
IE indicating CS Fallback not preferred }
then { The UE is able to receive MT CS fallback call}
}

9.2.3.2.1c.2 Conformance requirements
and 5.5.3.3.4.2.
[TS 24.301 clause 4.3.1]
The behaviour of the UE in CS/PS mode 1 of operation, upon failure to access the CS domain or upon reception of a
"CS fallback not preferred" or "SMS only" indication, will depend on the availability of voice over IMS. In the present
document, "IMS voice not available" refers to one of the following conditions:
- the UE is not configured to use IMS;
- the UE is not configured to use IMS voice, i.e. when the voice domain preference for E-UTRAN, as defined in
3GPP TS 24.167 [13B], indicates that voice communication services are allowed to be invoked only over the CS
domain;
- the UE is configured to use IMS voice, but the network indicates in the ATTACH ACCEPT message or the
TRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions are not supported; or
- the UE is configured to use IMS voice, the network indicates in the ATTACH ACCEPT message or the
TRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions are supported, but the upper
layers indicate that the UE is not available for voice calls in the IMS.
[TS 24.301 clause 5.5.3.3.4.2]
If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "SMS only"
or "CS Fallback not preferred", a UE operating in CS/PS mode 1 with "IMS voice not available" shall attempt to select
GERAN or UTRAN radio access technology rather than E-UTRAN for the selected PLMN or equivalent PLMN. The
UE shall disable the E-UTRA capability (see subclause 4.5). If the UE is in the EMM-CONNECTED mode, the UE
shall locally release the established NAS signalling connection and enter the EMM-IDLE mode before selecting
GERAN or UTRAN radio access technology.
If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "SMS only",
a UE operating in CS/PS mode 2 shall not attempt to use CS fallback for mobile originating services.
If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "CS
Fallback not preferred", this indicates to a UE operating in CS/PS mode 2 that it is attached for EPS and non-EPS
services and that it can use CS fallback.
9.2.3.2.1c.3 Test description
9.2.3.2.1c.3.1 Pre-test conditions
System Simulator:
- cell 1 and cell 5
UE:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1425 Release 9
1425
- - the UE is configured to be data centric
Preamble:
- if possible, the UE is configured to operate in CS/PS mode 2
- The UE is in state Registered, Idle mode (state 2) on Cell A(serving cell) according to [18].
9.2.3.2.1c.3.2 Test procedure sequence
Table 9.2.3.2.1c.3.2-1illustrates the downlink power levels and other changing parameters to be applied for the cells at
various time instants of the test execution. Configurations marked "T1" is applied at the point indicated in the Main
behaviour description in Table 9.2.3.2.1c.3.2-2.
Table 9.2.3.2.1c.3.2-1: instances of cell power level and parameter changes
Parameter
name
Unit Cell A Cell B Cell 5
T1 RS EPRE dBm/15kHz -91 -85

Table 9.2.3.2.1c.3.2-2: Main Behaviour
U - S Message
1 SS adjust the cell power levels according
to row T1 in table 9.2.3.2.1c.3.2-1..
- -
2-7 Steps 2-7 of the tracking area updating
procedure on cell B as described in TS
36.508 table 4.5A.2.1-1 are performed.
- -
8 Check: Does the UE try to access te
UTRAN cell (cell 5) in the next 20s?
1 F
10-13 Steps 1-4 of the procedure in table
13.1.4.3.2-2 are performed.
- - - -
- The UE accepts CS fallback - - - -
containing an EXTENDED SERVICE
REQUEST with message content set the
same as in step 5 table 13.1.4.3.2-2 ?
--> RRCConnectionSetupComplete
NAS: EXTENDED SERVICE
REQUEST
3 P
15-26 Steps 6-17 of the procedure described in
table 13.1.4.3.2-2 are performed.
- - - -
27 Steps 1-3 of the procedure in table
13.1.2.3.2-1. (A CS call is initiated) are
performed

28 Check: Does the UE transmit EXTENDED
SERVICE REQUEST message with the
content set as in step 4 of table 13.1.2.3.2-
1?

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1426 Release 9
1426
9.2.3.2.1c.3.3 Specific message contents
Table 9.2.3.2.1c.3.3-1: Message TRACKING AREA UPDATE ACCEPT (step 4, Table 9.2.3.2.1c.3.2-2)
EPS/IMSI attach''

session in S1
mode NOT
supported

Additional update result 01b CS Fallback not
preferred

9.2.3.2.2 Combined tracking area update / Successful for EPS services only / IMSI
unknown in HSS
(1)
with { UE has sent a combined TRACKING AREA UPDATE REQUEST message with EPS update type set to
'Combined TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE ACCEPT message with EPS update result set to "TA
updated" and EMM cause set to "IMSI unknown in HSS" }
then { UE considers the USIM as invalid for non-EPS services and enters EMM-REGISTERED.NORMAL-
SERVICE state and MM idle state }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.5.3.3.4.3.
[TS24.301 clause 5.5.3.3.4.3]
The UE receiving the TRACKING AREA UPDATE ACCEPT message takes one of the following actions depending
on the EMM cause value:
#2 (IMSI unknown in HSS)
The UE shall stop T3430 if still running and shall reset the tracking area updating attempt counter. The UE
shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering
key sequence number. The UE shall enter state EMM-REGISTERED.NORMAL-SERVICE. The new MM
state is MM IDLE. The USIM shall be considered as invalid for non-EPS services until switching off or the

System Simulator:
- cell A (belongs to TAI-1) is set to ''Serving cell'';
- cell B (belongs to TAI-2) is set to ''Non-suitable cell''.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1427 Release 9
1427
UE:
none.
Preamble:
U - S Message
1 Set the cell type of cell A to the "non-Suitable
cell". Set the cell type of cell B to the "Serving
cell".
- - - -
received on cell B.

2 The UE transmit a combined TRACKING
AREA UPDATE REQUEST message.
REQUEST
- -
UPDATE ACCEPT message with EPS update
result set to "TA updated" and EMM cause set
to "IMSI unknown in HSS"
ACCEPT
- -
domain indicator set to PS.
<-- - - -
6 The UE transmits a SERVICE REQUEST
message.
message with Detach Type set to "re-attach
required"
8 The UE sends a DETACH ACCEPT message. --> DETACH ACCEPT - -
- - - -
- - - -
to EPS attach, including a PDN
CONNECTIVITY REQUEST message ?
11-
22

ACCEPT message to be used in the UE
registration procedure in TS 36.508 clause
4.5.2.3 see Table 9.2.3.2.2.3.3-5 below
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1428 Release 9
1428
Table 9.2.3.2.2.3.3-1: Message TRACKING AREA UPDATE REQ (step 2, Table 9.2.3.2.2.3.2-1)
EPS update type 001 "combined TA/LA
updating"

included by UE if
valid, IMSI
otherwise.

last TAI is
included by UE
and will be used
to establish a
good list of TAIs
in subsequent
ATTACH
ACCEPT
message.

Old LAI LAI-1

EPS update result 000 " TA updated "
GUTI GUTI-2
TAI list
non-consecutive
TACs

MCC
MNC
TAC 1
TAI-2
LAC Not present
MS identity Not present
EMM cause 00000010 "IMSI unknown in
HSS"

Detach type 001 "re-attach
required"

EPS attach type 001 EPS attach

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1429 Release 9
1429
clause 4.5.2.3)
EPS attach result '001'B ''EPS only''

9.2.3.2.3 Combined tracking area update / Successful for EPS services only / MSC
temporarily not reachable
(1)
with { UE having sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to 'Combined
TA/LA updating' or 'Combined TA/LA updating with IMSI attach' and having the tracking area updating
attempt counter set to the value less than four }
ensure that {
when { UE receives a TRACKING AREA UPDATE ACCEPT message with the EPS update result set to 'TA
updated' and the EMM cause set to 'MSC temporarily not reachable', 'Network failure' or
'Congestion' }
then { UE sends TRACKING AREA UPDATE REQUEST message after T3411 expiry }
}

(2)
TA/LA updating with IMSI attach', having the tracking area updating attempt counter set to four and
operating in CS/PS mode 2 of operation }
ensure that {
'Congestion' }
then { UE sends TRACKING AREA UPDATE REQUEST message after T3402 expiry }
}

(3)
TA/LA updating with IMSI attach', having the tracking area updating attempt counter set to four and
operating in CS/PS mode 1 of operation }
ensure that {
'Congestion' }
then { UE attempts to select GERAN or UTRAN radio access technology }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.3.3.4.3.
[TS 24.301, clause 5.5.3.3.4.3]
...
#22 (Congestion)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1430 Release 9
1430
tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered
again.
updating with IMSI attach" is triggered again;
...
System Simulator:
- if pc_UTRAN, cell 5 (belongs to LAI-1 and RAI-1, home PLMN); system information combination 9 as defined
in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;
- if pc_GERAN and NOT pc_UTRAN, cell 24 (belongs to LAI-1 and RAI-1, home PLMN); system information
UE:
Preamble:
The sequence is executed for execution counter k =1, 2, 3.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1431 Release 9
1431
U - S Message
cell".
Set the cell type of Cell 5 or Cell 24 to the
"non-Suitable cell".
- - - -
- - - -
0A The UE is powered on or switched on. - - - -
0B Generic test procedure in TS 36.508
subclause 4.5.2.3 is performed.
NOTE: The UE performs an ATTACH
procedure and the RRC connection is
released.
- - - -
cell".
- - - -
- - - -
-->
TRACKING AREA UPDATE
REQUEST
1 P
3 Void - - - -
4 Void - - - -
<--
ACCEPT
- -
-->
COMPLETE
- -
- EXCEPTION: The step 8 to 13 shall be
repeated 4 times.
-
- - -
8 Wait for 10s (T3411). - - - -
AREA UPDATE REQUEST message at the
time which T3411 expired?
-->
REQUEST
1 P
10 Void - - - -
11 Void - - - -
<--
ACCEPT
- -
14-
19
Void - - - -
sequence that takes place according to UE
mode of operation.
- - - -
20a1 IF the UE is configured to operate in CS/PS
mode 2 THEN the SS waits for 12 min
(T3402).
- - - -
20a2 Check: Does the UE transmit a TRACKING
-->
REQUEST
2 P
20a3 The SS transmits a TRACKING AREA
<--
ACCEPT
- -
20a4 The UE transmits a TRACKING AREA
-->
COMPLETE
- -
20b1 ELSE the SS configures:
- - - -
otherwise.
- - - -
20b2 Void - - - -
20b3 Check: Does the UE transmit a ROUTING --> ROUTING AREA UPDATE 3 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1432 Release 9
1432
AREA UPDATE REQUEST message? REQUEST
20b4 The SS transmits a ROUTING AREA UPDATE
ACCEPT message.
<--
ROUTING AREA UPDATE
ACCEPT
- -
20b5 The UE transmits a ROUTING AREA UPDATE
COMPLETE message.
-->
ROUTING AREA UPDATE
COMPLETE
- -
20b6 The SS releases the RRC connection. - - - -
-
- - -

Table 9.2.3.2.3.3.3-1: TRACKING AREA UPDATE ACCEPT (step 5, Table 9.2.3.2.3.3.2-1)
GUTI GUTI-2
EMM cause '0001 0000'B for k=1 or
'0001 0001'B for k=2 or
'0001 0110'B for k=3
MSC temporarily
not reachable for
k=1
Network failure for
k=2
Congestion for
k=3

Table 9.2.3.2.3.3.3-2: TRACKING AREA UPDATE REQUEST (step 9 and 20a2, Table 9.2.3.2.3.3.2-1)
EPS update type
EPS update type value '010'B Combined TA/LA
updating with IMSI
attach

GUTI Not present
EMM cause '0001 0000'B for k=1 or
'0001 0001'B for k=2 or
'0001 0110'B for k=3
MSC temporarily
not reachable for
k=1
Network failure for
k=2
Congestion for
k=3

Table 9.2.3.2.3.3.3-4: TRACKING AREA UPDATE ACCEPT (step 20a3, Table 9.2.3.2.3.3.2-1)
GUTI Not present
MS identity TMSI-1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1433 Release 9
1433
9.2.3.2.4 Combined tracking area update / Successful for EPS services only / CS domain
not available
(1)
TA/LA updating' }
ensure that {
updated' and the EMM cause set to 'CS domain not available' }
then { UE transmits TRACKING AREA UPDATE COMPLETE message and set the update status to U2 NOT
UPDATED and enters EMM-REGISTERED state }
}

(2)
with { UE receives a TRACKING AREA UPDATE ACCEPT message with the EPS update result set to 'TA
updated' and the EMM cause set to 'CS domain not available' }
ensure that {
when { UE enters a new tracking area }
then { UE initiates the tracking area updating procedure with EPS update type as "TA updating" }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.3.3.4.3.
[TS 24.301, clause 5.5.3.3.4.3]
...
#18 (CS domain not available)
The UE shall stop timer T3430 if still running, shall reset the tracking area updating attempt counter, shall set
the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE.
The UE shall set the update status to U2 NOT UPDATED.
A UE in CS/PS mode 1 of operation with "IMS voice not available" shall attempt to select GERAN or
UTRAN radio access technology rather than E-UTRAN for the selected PLMN or equivalent PLMN. The
UE shall disable the E-UTRA capability (see subclause 4.5). If the UE is in the EMM-CONNECTED mode,
the UE shall locally release the established NAS signalling connection and enter the EMM-IDLE mode
before selecting GERAN or UTRAN radio access technology.
A UE in CS/PS mode 2 of operation may provide a notification to the user or the upper layers that the CS
domain is not available.
The UE shall not attempt combined attach or combined tracking area updating procedure with current PLMN
until switching off the UE or the UICC containing the USIM is removed.
System Simulator:
- cell A (belongs to TAI-1, home PLMN) is set to "Serving cell''
- cell B (belongs to TAI-2, home PLMN) is set to ''Non-suitable cell'.'
UE:
none.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1434 Release 9
1434
Preamble:
U - S Message
1 Set the cell type of Cell B to the "Serving cell".
Set the cell type of Cell A to the "non-Suitable
cell".
- - - -
received on Cell B.
- - - -
2 The UE transmit a TRACKING AREA UPDATE
REQUEST message.
-->
REQUEST
- -
<--
ACCEPT
- -
-->
COMPLETE
- -
domain indicator set to "CS"?
- - 1 P
indicate that the UE is in state Registered, Idle
Mode on Cell B?
- - 1 P
cell".
- - - -
AREA UPDATE REQUEST message with EPS
update type as "TA updating"?
-->
REQUEST
2 P
<--
ACCEPT
- -
-->
COMPLETE
- -

EPS update type
EPS update type Value '001'B " combined TA/LA
updating

GUTI GUTI-2
EMM cause '00010010'B

"CS domain not
available"

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1435 Release 9
1435
EPS update type
EPS update type Value '000'B " TA updating "

9.2.3.2.5 Combined tracking area update / Rejected / IMSI invalid
(1)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'Illegal UE' }
EMM-DEREGISTERED }
}

[TS 24.301, clause 5.5.3.3.5]
If the combined tracking area updating cannot be accepted by the network, the MME shall send a TRACKING AREA
UPDATE REJECT message to the UE including an appropriate EMM cause value.
transmission of user data, enter state MM IDLE, and take the following actions depending on the EMM cause value
received.
#3 (Illegal UE);

subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI Listand eKSI.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI,
LAI and ciphering key sequence number, and the GMM parameters GMM state, GPRS update status, P-TMSI,
P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008 [13] for the
case when the combined routing area updating procedure is rejected with the GMM cause with the same value.
System Simulator:
- cell A, cell B and cell C;
- If pc_UTRAN, cell 5 (belongs to RAI-1, home PLMN);
- If pc_GERAN and NOT pc_UTRAN, cell 24 (belongs to RAI-1, home PLMN);
- system information combination 9 as defined in TS 36.508 [18] clause 4.4.3.1 is applied in E-UTRA cells
except if NOT pc_UTRAN and pc_GERAN then system information combination 12 is applied;
- cell A is "Serving cell" and cell B, cell C, cell 5 and cell 24 are "Non-suitable "off" cell".

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1436 Release 9
1436
UE:
Preamble:
U - S Message
"off" cell". Set the cell type of Cell B to the
"Serving cell".
- - - -
- - - -
REQUEST
- -
cause set to 'Illegal UE'.
REJ ECT
- -
"off" cell". Set the cell type of Cell C to the
"Serving cell".
- - - -
- - - -
supported
- - - -
sets the cell type of the cell other than Cell 5
and Cell 24 to the "non-Suitable "off" cell" and
sets the cell type of Cell 5 or Cell 24 to the
"Serving cell".
- - - -
otherwise.
- - - -
8 Set the cell type of the cell other than Cell A to
the "non-Suitable "off" cell". Set the cell type of
Cell A to the "Serving cell".
- - - -
- - - -
- - - -


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1437 Release 9
1437
9.2.3.2.6 Combined tracking area update / Rejected / Illegal ME
(1)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'Illegal ME' }
EMM-DEREGISTERED }
}

[TS 24.301, clause 5.5.3.3.5]
received.

#6 (Illegal ME); or

subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI Listand eKSI.
LAI and ciphering key sequence number, and the GMM parameters GMM state, GPRS update status, P-TMSI,
P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008 [13] for the
case when the combined routing area updating procedure is rejected with the GMM cause with the same value.
System Simulator:
- if pc_UTRAN, cell 5 (belongs to RAI-1, home PLMN);
- system information combination 9 as defined in TS 36.508 [18] clause 4.4.3.1 is applied in E-UTRA cells except
- if pc_GERAN and NOT pc_UTRAN, cell 24 (belongs to RAI-1, home PLMN);
- cell A is "Serving cell" and cell B, cell C, cell 5 and cell 24 are "Non-suitable cell".
UE:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1438 Release 9
1438
Preamble:
U - S Message
cell".
- - - -
- - - -
REQUEST
- -
cause set to 'Illegal ME'.
REJ ECT
- -
cell". Set the cell type of Cell C to the "Serving
cell".
- - - -
- - - -
supported
- - - -
sets the cell type of the cell other than Cell 5
and Cell 24 to the "non-Suitable cell" and sets
the cell type of Cell 5 or Cell 24 to the "Serving
cell".
- - - -
otherwise.
- - - -
7a2 Void - - - -
8 Set the cell type of the cell other than Cell A to
the "non-Suitable cell". Set the cell type of Cell
A to the "Serving cell".
- - - -
- - - -
- - - -


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1439 Release 9
1439
9.2.3.2.7 Combined tracking area update / Rejected / EPS services and non-EPS services
not allowed
(1)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'EPS services
and non-EPS services not allowed' }
EMM-DEREGISTERED }
}

[TS 24.301, clause 5.5.3.3.5]

#3 (Illegal UE);
#6 (Illegal ME); or
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI Listand KSI.
containing the USIM is removed. Additionally, the UE shall delete the list of equivalent PLMNs and shall enter the
state EMM-DEREGISTERED.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI, LAI
and ciphering key sequence number, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI
signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008 [13] for the case when the
combined routing area updating procedure is rejected with the GMM cause with the same value.

The pre-test conditions are indentical to the one of subclause 9.2.3.2.6.
The test procedure sequence is indentical to the one of subclause 9.2.3.2.6.
EMM cause '0000 1000'B EPS services and
non-EPS services
not allowed

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1440 Release 9
1440
9.2.3.2.8 Combined tracking area update / Rejected / EPS services not allowed
(1)
TA/LA updating' }
ensure that {
not allowed' }
then { UE considers the USIM as invalid for EPS services and enters state EMM-DEREGISTERED }
}

(2)
with { UE in CS/PS mode 1 or CS/PS mode 2 of operation and have been IMSI attached for non-EPS
services }
ensure that {
when { UE sends a TRACKING AREA UPDATE REQUEST message with EPS update type set to 'Combined TA/LA
updating' and receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'EPS services
not allowed' }
then { The UE shall still IMSI attached for non-EPS services }
}

[TS 24.301, clause 5.5.3.3.5]
received.

subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and KSI. The UE shall
consider then USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed.
A UE in CS/PS mode 1 or CS/PS mode 2 of operation is still IMSI attached for non-EPS services. The UE shall
set the update status to U2 NOT UPDATED, shall select GERAN or UTRAN radio access technology and
proceed with appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-
UTRAN radio access technology until switching off or the UICC containing the USIM is removed.
NOTE: Some interaction is required with the access stratum to disable E-UTRAN cell reselection.
specified in 3GPP TS 24.008 [13] for the case when the combined routing area updating procedure is rejected
with the GMM cause with the same value.
System Simulator:
- cell B (belongs to TAI-2(, home PLMN) is set to ''Non-suitable off cell'';

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1441 Release 9
1441
- cell G (belongs to TAI-7, visited PLMN) is set to ''Non-suitable off cell'';
- If pc_UTRAN cell 5 and if (NOT pc_UTRAN AND pc_GERAN) cell 24 is set to ''Non-suitable off cell'';
- If pc_UTRAN, system information combination 4 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA
cells;
- If NOT pc_UTRAN and pc_GERAN, system information combination 5 as defined in TS 36.508[18] clause
4.4.3.1 is used in E-UTRA cells;
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1442 Release 9
1442
U - S Message
Cell A as the "non-Suitable cell".
- - - -
REQUEST
- -
cause set to as ''EPS services not allowed''
as specified.
REJ ECT
- -
Cell A as the "Serving cell".
Cell B as the "non-Suitable cell".
- - - -
on cell A?
TAI
command.
- - - -
on cell A?
Cell A as the "non-Suitable off cell".
- - - -
on cell G?

rejected.
command.
- - - -
on cell G?
Cell 5 or 24 as the "Suitable cell".
- - - -
supported

14a1 IF pc_GERAN or pc_UTRAN THEN the
received on Cell 5 or 24.
- - - -
14a2 Check: Does the UE transmit a LOCATION
24?
REQUEST
2 P
14a3 The SS transmits an AUTHENTICATION
REQUEST message to initiate the
14a4 The UE transmits an AUTHENTICATION
RESPONSE message.
ACCEPT message with Location updating
type ="IMSI attach" as specified in 3GPP TS
24.008.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1443 Release 9
1443
Cell 5 or 24 as the "non-Suitable cell".
- - - -
16 The user initiates attach by MMI or by AT
command.
- - - -
on cell G?

EPS update type
EPS update type Value '001'B " combined TA/LA
updating "

Old GUTI GUTI-1

EMM cause '00000111'B "EPS services not
allowed''

9.2.3.2.9 Combined tracking area update / Rejected / UE identity cannot be derived by the
network
(1)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to 'Combined
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'UE identity
cannot be derived by the network' }
then { UE deletes GUTI, last visited registered TAI, TAI list and KSI, enters the state EMM-
DEREGISTERED, subsequently, automatically initiates the attach procedure and is still IMSI attached
for non-EPS services }
}

(2)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'UE identity
cannot be derived by the network' }
then { UE deletes P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number }
}

TS 24.008, clause 4.7.5.2.4.
[TS 24.301, clause 5.5.3.3.5]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1444 Release 9
1444
received.
...
The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI. The UE shall delete
the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.
specified in 3GPP TS 24.008 [13] for the case when the combined routing area updating procedure is rejected
with the GMM cause with the same value.
A UE in CS/PS mode 1 or CS/PS mode 2 of operation is still IMSI attached for non-EPS services.
[TS 24.008, clause 4.7.5.2.4]
The MS shall then take different actions depending on the received reject cause:
...
#9 (MS identity cannot be derived by the network);
The MS shall set the GPRS update status to GU2 NOT UPDATED (and shall store it according to
subclause 4.1.3.2), enter the state GMM-DEREGISTERED, and shall delete any P-TMSI, P-TMSI signature,
RAI and GPRS ciphering key sequence number. Subsequently, the MS may automatically initiate the GPRS
attach procedure.
System Simulator:
- if pc_UTRAN, cell 5 (belongs to RAI-1, home PLMN) is set to '"Non-Suitable cell"; system information
combination 9 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cell;
- if pc_GERAN and NOT pc_UTRAN, cell 24 (belongs to RAI-1, home PLMN) is set to '"Non-Suitable cell";
system information combination 12 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cell;
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1445 Release 9
1445
U - S Message
1 Set the cell type of Cell A to the ''Non-Suitable
cell''.
Set the cell type of Cell B to the ''Serving cell''.
- - - -
- - - -
UPDATE REQUEST.
REQUEST
- -
set to ''UE identity cannot be derived by the
network''.
REJ ECT
- -
supported.
- - - -
4Aa1
-
4Aa1
3
IF NOT pc_UTRAN and NOT pc_GERAN
THEN Steps 5 to 17 of the generic test
procedure in TS 36.508 subclause 4.5.2.3 are
NOTE: The UE performs an Attach procedure.
- - - -
supported
- - - -
sets the cell type of Cell B to the non-Suitable
cell" and sets the cell type of Cell 5 or Cell 24
to the "Serving cell".
- - - -
otherwise.
- - - -
5a2 Void - - - -
REQUEST message?
5a4-
5a7
Void - - - -
5a8 The SS sets the cell type of cell 5 or cell 24 to
the non-Suitable cell" and sets the cell type of
Cell A to the Suitable cell". (Note)
- - - -
cell A unless explicitly stated otherwise.
- - - -
5a9-
5a24
- - - -
- - - -
Note: To make UEs behaviour more predictable, cell type is changed without receiving the response of ATTACH
REQUEST message in step 5a3.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1446 Release 9
1446
Old GUTI GUTI-1
Old P-TMSI signature P-TMSI signature-1

EMM cause '0000 1001'B UE identity cannot
be derived by the
network

apply for NAS key
"111".


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1447 Release 9
1447
GPRS/IMSI attach

available (MS to
network)

0.
Other bits are not
checked.

value
Not present or any
allowed value

allowed value

allowed value

allowed value

allowed value

allowed value


9.2.3.2.10 Combined tracking area update / Rejected / UE implicitly detached
(1)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'Implicitly
detached' }
then { UE sends an ATTACH REQUEST message }
}

[TS 24.301, clause 5.5.3.3.5]
received.
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1448 Release 9
1448
The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NORMAL-
SERVICE. The UE shall then perform a new attach procedure.
...
System Simulator:
- cell A is set to the "Serving cell" and cell B is set to the "non-Suitable cell".
UE:
Preamble:
- the UE is in state Registered, Idle mode (state 2) on cell A according to 36.508 [18].
U - S Message
cell".
- - - -
- - - -
REQUEST
- -
cause set to 'Implicitly detached'.
REJ ECT
- -
- - - -
- - - -

EMM cause '0000 1010'B Implicitly detached

9.2.3.2.11 Combined tracking area update / Rejected / PLMN not allowed
(1)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1449 Release 9
1449
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'PLMN not
allowed' }
then { UE deletes GUTI, last visited registered TAI, TAI list and KSI, enters the state EMM-
DEREGISTERED.PLMN-SEARCH, stores the PLMN identity in the "forbidden PLMN list" }
}

(2)
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'PLMN not
allowed' }
then { UE deletes P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key sequence number GPRS
ciphering key sequence number }
}

(3)
with { UE is switched off and a PLMN is stored in the "forbidden PLMN list" }
ensure that {
when { UE is powered on this PLMN }
}

(4)
with { UE in EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden PLMN list" }
ensure that {
when { UE enters a cell belonging to a PLMN which is not in the"forbidden PLMN list" }
}

(5)
with { UE in EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden PLMN list" }
ensure that {
when { UE is in a forbidden PLMN cells and when the PLMN is selected manually }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.3.3.5, TS
24.008, clause 4.7.5.2.4, and TS 23.122, clause 4.4.3.1.2.
[TS 24.301, clause 5.5.3.3.5]
received.
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI, and reset the
tracking area updating attempt counter. The UE shall delete the list of equivalent PLMNs and enter the state
EMM-DEREGISTERED.PLMN-SEARCH.
The UE shall then perform a PLMN selection according to 3GPP TS 23.122 [6].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1450 Release 9
1450
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle and the MM parameters update status,
TMSI, LAI, ciphering key sequence number and the location update attempt counter, and the GMM parameters
GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and
routing area updating attempt counter as specified in 3GPP TS 24.008 [13] for the case when the combined
routing area updating procedure is rejected with the GMM cause with the same value and no RR connection
exists.
[TS 24.008, clause 4.7.5.2.4]
The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the update status to U3
ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and enter the state GMM-
DEREGISTERED. Furthermore, it shall delete any P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key
sequence number GPRS ciphering key sequence number, and reset the routing area updating attempt counter and
the location update attempt counter.
[TS 23.122, clause 4.4.3.1.2]
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 TAs
for roaming", "forbidden LAs for regional provision of service", "forbidden TAs for regional provision of service",
"forbidden PLMNs for GPRS service" and "forbidden PLMNs" lists.
System Simulator:
- cell H (belongs to TAI-8, visited PLMN) is set to ''Non-suitable off cell'';
- cell I (belongs to TAI-9, visited PLMN, another PLMN) is set to ''Non-suitable off cell'';
- if pc_UTRAN, cell 5 (belongs to RAI-1 and LAI-1) is set to ''Non-suitable off cell'';
- if pc_GERAN and NOT pc_UTRAN, cell 24 (belongs to RAI-1 and LAI-1) is set to ''Non-suitable off cell'';
- cell G, cell 5 and cell 24 are in same PLMN.
- system information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is applied in E-UTRA cells except
UE:
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell G according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1451 Release 9
1451
U - S Message
1 Set the cell type of Cell G to the ''Non-Suitable
"off" cell''. Set the cell type of Cell H to the
''Serving cell''.
- - - -
Cell H unless explicitly stated otherwise.
- - - -
REQUEST
- -
cause set to 'PLMN not allowed'.
REJ ECT
- -
- - - -
7 Set the cell type of Cell G to the ''Serving cell'''.
Set the cell type of Cell H to the ''Non-Suitable
"off" cell''.
NOTE: Cell G and Cell H are in the same
PLMN.
- - - -
- - - -
USIM is inserted.
- - - -
supported
- - - -
10a1 IF pc_UTRAN or pc_GERAN THEN sets the
cell type of Cell G to the non-Suitable "off"
- - - -
otherwise.
- - - -
11 Set the cell type of Cell G to the non-Suitable
"off" cell". Set the cell type of Cell I to the
Serving cell". Set the cell type of Cell 5 or Cell
24 to the non-Suitable "off" cell".
- - - -
- - - -
4
P
13-
21
procedure.
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1452 Release 9
1452
- - - -
message.
27 Set the cell type of Cell G to the ''Serving cell'''.
Set the cell type of Cell I to the ''Non-Suitable
"off" cell''.
- - - -
- - - -
USIM is inserted.
- - - -
mode and is made to select the forbidden
PLMN cell.
- - - -
31-
43
procedure and the RRC connection is
released.
- - - -
to TS 36.508.
- - - -

Old GUTI GUTI-7
Old P-TMSI signature P-TMSI signature-1

EMM cause '0000 1011'B PLMN not allowed

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1453 Release 9
1453
apply for NAS key
"111".

Additional GUTI Not present
available

GUTI GUTI-9
MS identity TMSI-9

Additional GUTI Not present

9.2.3.2.12 Combined tracking area update / Rejected / Tracking area not allowed
(1)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'Tracking Area
not allowed' }
registered TAI, TAI List and KSI, enters the state EMM-DEREGISTERED.LIMITED-SERVICE and stores the
current TAI in the list of "forbidden tracking areas for regional provision of service" }
}

(2)
with { UE in EMM-DEREGISTERED.LIMITED-SERVICE state having the list of "forbidden tracking areas for
regional provision of service" }
ensure that {
}

(3)
with { UE in EMM-DEREGISTERED.LIMITED-SERVICE state having the list of "forbidden tracking areas for
regional provision of service" }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1454 Release 9
1454
ensure that {
when { UE reselects a new cell which belongs to the TAI in the list of "forbidden tracking areas
}

(4)
with { UE is powered off or switched off }
ensure that {
when { UE is powered on or switched on in the cell belonging to the TAI which was in the list of
"forbidden tracking areas for regional provision of service" before the UE was powered off or
switched off }
}

[TS 24.301, clause 5.5.3.3.5]
received.
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and KSI. The UE shall reset
SERVICE.
LAI, ciphering key sequence number and the location update attempt counter, and the GMM parameters GMM
state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing
area updating attempt counter as specified in 3GPP TS 24.008 [13] for the case when the combined routing area
updating procedure is rejected with the GMM cause with the same value.
...
System Simulator:
- cell A, cell B and cell M;
- cell A is set to the "Serving cell", and cell B and cell M is set to the "non-Suitable cell".
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1455 Release 9
1455
U - S Message
1 Set the cell type of Cell A to the "Suitable
neighbour cell". Set the cell type of Cell B to
the "Serving cell".
- - - -
- - - -
REQUEST
- -
cause set to 'Tracking Area not allowed'.
REJ ECT
- -
Cell A or Cell B?
cell". Set the cell type of Cell B to the "non-
Suitable cell". Set the cell type of Cell M to the
"Serving cell".
- - - -
- - - -
Set the cell type of Cell M to the "non-Suitable
cell".
- - - -
- - - -
- - - -
USIM is inserted.
- - - -
13-
24
- - - -
- - - -

EMM cause '0000 1100'B Tracking Area not
allowed

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1456 Release 9
1456
Table 9.2.3.2.12.3.3-2: ATTACH REQUEST (step 12, Table 9.2.3.2.12.3.2-1)
apply for NAS key
"111".

Old GUTI or IMSI IMSI of the UE

9.2.3.2.13 Combined tracking area update / Rejected / Roaming not allowed in this tracking
area
(1)
TA/LA updating' }
ensure that {
when { the UE receives TRACKING AREA UPDATE REJECT message with the reject cause set to "roaming
not allowed in this tracking area" }
then { the UE sets the EPS update status to EU3 ROAMING NOT ALLOWED and the UE deletes the last
visited registered TAI and the UE enters the state EMM-REGISTERED.PLMN-SEARCH and the UE stores the
current TAI in the list of "forbidden tracking areas for roaming" }
}

(2)
with { the UE is in EMM-REGISTERED.PLMN-SEARCH state and the current TAI in the list of "forbidden
tracking areas for roaming"}
ensure that {
when { the serving cell belongs to TAI where UE was rejected }
then { the UE does not attempt to send TRACKING AREA UPDATE REQUEST message }
}

(3)
ensure that {
when { the UE enters a cell belonging to same PLMN and TAI not in the list of "forbidden tracking
areas for roaming"}
then { the UE sends TRACKING AREA UPDATE REQUEST message with EPS update type set to "combined
TA/LA updating with IMSI attach"}
}

(4)
ensure that {
when { the UE enters a cell belonging to another PLMN }
then { the UE sends TRACKING AREA UPDATE REQUEST message with EPS update type set to "combined
TA/LA updating with IMSI attach" }
}
(5)
with { the UE, which A/Gb mode or Iu mode is supported by the UE, in EMM-DEREGISTERED.PLMN-SEARCH
state and the list of "forbidden tracking areas for roaming" contains more than one TAI }
ensure that {
when { the UE move to UTRAN or GERAN cell }
then { the UE sends ROUTING AREA UPDATE REQUEST message }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1457 Release 9
1457
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.3.3.5
[TS 24.301, clause 5.5.3.3.5]
received.
...
subclause 5.1.3.3) and shall delete the list of equivalent PLMNs. The UE shall reset the tracking area updating
attempt counter and shall change to state EMM-REGISTERED.PLMN-SEARCH.
The UE shall indicate the Update type IE "combined TA/LA updating with IMSI attach" when performing the
tracking area updating procedure following the PLMN selection.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status and the
location update attempt counter, and the GMM parameters GMM state, GPRS update status and routing area
updating attempt counter as specified in 3GPP TS 24.008 [13] for the case when the combined routing area

System Simulator:
- cell H (belongs to TAI-8, same visited PLMN) is set to ''Non-suitable off cell'';
- cell I (belongs to TAI-9, another visited PLMN) is set to ''Non-suitable off cell'';
- if pc_UTRAN, cell 5 (belongs to RAI-8, visited PLMN) is set to "Non-suitable off cell";
- if NOT pc_UTRAN and pc_GERAN, cell 24 (belongs to RAI-8, visited PLMN) is set to "Non-suitable off cell";
- system information indicate that NMO 1 is used..
UE:
- The UE is configured to initiate combined EPS/IMSI attach.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1458 Release 9
1458
U - S Message
off cell''.
- - - -
2 The UE transmits TRACKING AREA UPDATE
REQUEST on Cell H.
REQUEST
- -
=''Roaming not allowed in this tracking area''
as specified.
REJ ECT
- -
next 30 seconds on cell H?
REQUEST
1, 2 F
off cell''.
- - - -
next 30 seconds on cell G?
REQUEST
1, 3 P
8 The SS transmits TRACKING AREA UPDATE
REJ ECT message with EMM cause =
''Roaming not allowed in this tracking area'' as
specified.
REJ ECT
- -
off cell''.
cell''.

PLMN.
- - - -
supported

11a
1
Check: Does the UE transmit ROUTING AREA
UPDATE REQUEST message in the next 30
seconds on cell 5 or 24?
REQUEST
5 P
11a
2
REJ ECT message with cause ='' Roaming not
allowed in this routing area '' as specified.
REJ ECT
- -
11a
3
The SS releases the RRC connection.
Suitable off cell''.

PLMNs.
- - - -
AREA REQUEST message in the next 30
seconds on cell I?
REQUEST
1, 4 P
14 The SS sends TRACKING AREA ACCEPT
message.
ACCEPT
- -
15 The UE transmits TRACKING AREA
COMPLETE message.
COMPLETE
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1459 Release 9
1459
Old GUTI GUTI-7
N or
pc_UTRAN

Table 9.2.3.1.17.3.3-2: TRACKING AREA UPDATE REJECT (step 3 and 8, Table 9.2.3.1.17.3.2-1)
allowed in this
tracking area

Table 9.2.3.2.11.3.3-3: Message TRACKING AREA UPDATE REQUEST (step 7 and 13, Table
9.2.3.2.11.3.2-1)
EPS update type
updating with IMSI
attach

9.2.3.2.14 Combined tracking area update / Rejected / EPS services not allowed in the
PLMN
(1)
TA/LA updating' }
ensure that {
not allowed in this PLMN' }
then { UE deletes any GUTI, last visited registered TAI, TAI List and eKSI, and UE stores the
PLMN identity in the "forbidden PLMNs for GPRS service" list }
}

(2)
with { UE is in EMM-DEREGISTERED.PLMN-SEARCH state }
ensure that {
when { UE detects a E-UTRAN cell which belongs to the same PLMN which is stored in the "forbidden
PLMNs for GPRS service" list }
then { UE does not attempt to access on this cell }
}

(3)
with { UE is IMSI attached for non-EPS services and is in EMM-DEREGISTERED.PLMN-SEARCH state and one
PLMN stored in the "forbidden PLMNs for GPRS service" list }
ensure that {
when { UE update status is U2 NOT UPDATED and detects a new GERAN or UTRAN cell which belongs to
the PLMN }
then { UE initiates location update procedure in this GERAN or UTRAN cell }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1460 Release 9
1460
(4)
with { UE is in EMM-DEREGISTERED.PLMN-SEARCH state }
ensure that {
when { UE detects a E-UTRAN cell which belongs to another PLMN which is not stored in the
"forbidden PLMNs for GPRS service" list }
then { UE attempts to access on this cell }
}

[TS 24.301, clause 5.5.3.3.5]
received.

subclause 5.1.3.3). Furthermore the UE shall delete any GUTI, last visited registered TAI, TAI List and eKSI.
The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-
The UE operating in CS/PS mode 1 or CS/PS mode 2 of operation is still IMSI attached for non-EPS services
and shall set the update status to U2 NOT UPDATED.
A UE operating in CS/PS mode 1 of operation may select GERAN or UTRAN radio access technology and
proceed with the appropriate MM specific procedure according to the MM service state. In this case the UE shall
not reselect E-UTRAN radio access technology for the duration the UE is on the PLMN or equivalent PLMN.
A UE in CS/PS mode 1 of operation may perform a PLMN selection according to 3GPP TS 23.122 [6].
A UE operating in CS/PS mode 2 of operation shall perform a PLMN selection according to 3GPP TS 23.122 [6].
attempt counter as specified in 3GPP TS 24.008 [13] for the case when the combined routing area updating
System Simulator:
- cell E (belongs to TAI-12, visited PLMN, frequency 2) is set to ''Serving cell'';
- cell I (belongs to TAI-9, visited PLMN, frequency 3) is set to ''Non-suitable off cell'';
- cell J (belongs to TAI-10, another visited PLMN, frequency 4) is set to ''Non-suitable off cell'';
- if pc_UTRAN cell 5 (NMO 2) is set to ''Non- Suitable off cell''; system information combination 4 as defined in
- if pc_GERAN and NOT pc_UTRAN, cell 24 (NMO 2) is set to ''Non- Suitable off cell'; system information

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1461 Release 9
1461
UE:
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell E according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1462 Release 9
1462
U - S Message
Cell E as the "non-Suitable cell".
- - - -
UPDATE REQUEST on Cell I.
REQUEST
- -
cause set to as ''EPS services not allowed in
this PLMN'' as specified.
REJ ECT
- -
Cell I as the "non-Suitable cell".
Cell E as the "Serving cell".
- - - -
on cell E?
Cell E as a "non-Suitable cell".
Cell 5 or 24 as the "Serving cell".
- - - -
supported.
- - - -
8a1 IF pc_GERAN or pc_UTRAN, THEN the
received on Cell 5 or 24.
Check: Does the UE transmit a LOCATION
cell 24 in the next 30 seconds?
REQUEST
3 P
8a2 The SS transmits an AUTHENTICATION
REQUEST message to initiate the
8a3 The UE transmits an AUTHENTICATION
RESPONSE message.
ACCEPT message with Location updating
type ="IMSI attach" as specified in 3GPP TS
24.008.
Cell J as the " Serving cell".
Cell 5 or 24 as the "non-Suitable off cell".
- - - -
10 Check: Does the UE transmit ATTACH
request PDN connectivity to the default PDN
on cell J ?
11-
22
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1463 Release 9
1463
EPS update type
EPS update type Value '001'B "combined TA/LA
updating "

Old GUTI GUTI-7

EMM cause '00001110'B " EPS services
not allowed in this
PLMN ''


9.2.3.2.15 Combined tracking area update / Rejected / No suitable cells in tracking area
(1)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the EMM cause set to 'No Suitable
Cells In tracking area' }
then { UE selects a suitable cell in another tracking area in the same PLMN and performs the
tracking area updating procedure with EPS update type set to 'combined TA/LA updating with IMSI
attach' }
}

[TS 24.301, clause 5.5.3.3.5]
received.
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1464 Release 9
1464
tracking area updating procedure.
System Simulator:
- cell A is set to the "Serving cell" and cell B and cell C is set to the "Non-suitable cell".
UE:
Preamble:
U - S Message
cell". Set the cell type of Cell C to the "Suitable
neighbour cell".
- - - -
- - - -
REQUEST
- -
cause set to 'No Suitable Cells In tracking
area'.
REJ ECT
- -
- - - -
AREA UPDATE REQUEST message with EPS
update type set to 'combined TA/LA updating
with IMSI attach'?
REQUEST
1 P
ACCEPT
- -
COMPLETE
- -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1465 Release 9
1465
In tracking area

Table 9.2.3.2.15.3.3-2: TRACKING AREA UPDATE REQUEST (step 5, Table 9.2.3.2.15.3.2-1)
EPS update type
updating with IMSI
attach

9.2.3.2.16 Combined tracking area update / Rejected / Not authorized for this CSG
(1)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to "Not
authorized for this CSG" and with integrity protection }
then { UE removes the CSG ID from the Allowed CSG list }
}

(2)
TA/LA updating' }
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to "Not
authorized for this CSG" and with integrity protection }
then { UE searches for a suitable cell in the same PLMN and sent a TRACKING AREA UPDATE REQUEST
message with EPS update type set to ' combined TA/LA updating with IMSI attach ' }
}

[TS 24.301, clause 5.5.3.3.5]
If the TRACKING AREA UPDATE REJ ECT message with cause #25 was received without integrity protection,
then the UE shall discard the message.
If the CSG ID of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST message is
contained in the Allowed CSG list, the UE shall remove the CSG ID from the Allowed CSG list.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1466 Release 9
1466
If the CSG ID of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST message is
contained in the Operator CSG list, the UE shall apply the procedures defined in 3GPP TS 23.122 [6]
subclause 3.1A.
tracking area updating procedure.
System Simulator:
- cell A (TAI-1, frequency 1, HPLMN, not a CSG cell) is set to ''Serving cell'';
- cell B (TAI-2, frequency 1, HPLMN, is a CSG cell) is set to ''Non-suitable off cell'';
- cell C (TAI-3, frequency 1, HPLMN, not a CSG cell) is set to ''Non-suitable off cell''.
UE:
of cell B).
Preamble:
- the UE is in state Registered, Idle mode (state 2) with condition CombinedAttach on cell A according to TS
36.508 [18]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1467 Release 9
1467
U - S Message
- - - -
REQUEST
- -
3 The SS transmits an TRACKING AREA
="Not authorized for this CSG" with integrity
protection.
REJ ECT
- -
5 Check: Does the UE transmit an TRACKING
AREA UPDATE REQUEST message on Cell B
REQUEST
1 F
- Cell A as a "Not Suitable off cell".
- Cell B as a "Not Suitable cell".
- Cell C as a "Suitable cell".
- - - -
next 30 seconds on Cell C?
REQUEST
2 P
ACCEPT
- -
COMPLETE
- -
- Cell A as a "Not Suitable off cell".
- Cell B as a " Serving cell".
- Cell C as a " Not Suitable cell".
- - - -
next 30 seconds on Cell B?
REQUEST
1 F

EPS update type 001B "combined TA/LA
updating"

for this CSG"

EPS update type 010B " combined TA/LA
updating with IMSI
attach "

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1468 Release 9
1468
Table 9.2.3.2.16.3.3-4: SystemInformationBlockType1 for Cell A, B, C (Pre-test conditions and all
steps in Table 9.2.3.2.16.3.2-1)
FALSE Cell A
FALSE Cell C
'000 0000 0000 0000
0000 0000 0010'B
Cell B
Not present Cell C
}
}

9.2.3.2.17 Combined tracking area update / Abnormal case / handling of the EPS tracking
area updating attempt counter
(1)
with { UE has initiated combined tracking area updating procedure and has the tracking area updating
attempt counter less than 5 }
ensure that {
when { UE detects release of the NAS signalling connection and in a EPS update status different to
EU1 UPDATED and update status different from U1 UPDATED }
then { UE starts timer T3411, deletes any LAI, TMSI, ciphering key sequence number and list of
equivalent PLMNs and set the update status to U2 NOT UPDATED }
}

(2)
with { UE has initiated combined tracking area updating procedure and has the tracking area updating
attempt counter equal to 5 }
ensure that {
then { UE starts timer T3402, deletes any LAI, TMSI, ciphering key sequence number and list of
equivalent PLMNs and set the update status to U2 NOT UPDATED }
}

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clause 5.5.3.1, clause
5.5.3.2.6 and clause 5.5.3.3.6.
[TS 24.301, clause 5.5.3.1]
...
completed; or
EMM cause #11, #12, #13, #14, #15 or #25.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1469 Release 9
1469
[TS 24.301, clause 5.5.3.2.6]

c) T3430 timeout
The UE shall abort the procedure and proceed as described below. The NAS signalling connection shall be
released locally.

If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is included in
the TAI list and the EPS update status is equal to EU1 UPDATED:
- the UE shall keep the EPS update status to EU1 UPDATED and enter state EMM-
REGISTERED.NORMAL-SERVICE. The UE shall start timer T3411. When timer T3411 expires the
tracking area updating procedure is triggered again.
If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is not included
in the TAI list or the EPS update status is different to EU1 UPDATED:
- the UE shall start timer T3411, shall set the EPS update status to EU2 NOT UPDATED and change to state
EMM-REGISTERED.ATTEMPTING-TO-UPDATE. When timer T3411 expires the tracking area updating
procedure is triggered again.
procedure fails and the routing area updating attempt counter is less than 5 and the GPRS update status is
different from GU1 UPDATED.
- the UE shall start timer T3402, shall set the EPS update status to EU2 NOT UPDATED, shall delete the list
of equivalent PLMNs and shall change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE or
optionally to EMM-REGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to
3GPP TS 23.122 [6].
procedure fails and the routing area updating attempt counter is equal to 5.
[TS 24.301, clause 5.5.3.3.6]

If the tracking area updating attempt counter is incremented according to subclause 5.5.3.2.6 the next actions depend on
the value of the tracking area updating attempt counter.
- if the update status is U1 UPDATED and the tracking area updating attempt counter is less than 5, then the UE
shall keep the update status to U1 UPDATED, the new MM state is MM IDLE substate NORMAL SERVICE;
- if the tracking area updating attempt counter is less than 5 and, additionally, the update status is different from
U1 UPDATED UE shall delete any LAI, TMSI, ciphering key sequence number and list of equivalent PLMNs

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1470 Release 9
1470
and set the update status to U2 NOT UPDATED. The MM state remains MM LOCATION UPDATING
PENDING; or
- if the tracking area updating attempt counter is equal to 5, the UE shall delete any LAI, TMSI, ciphering key
sequence number and list of equivalent PLMNs and set the update status to U2 NOT UPDATED. A UE
operating in CS/PS mode 1 of operation shall select GERAN or UTRAN radio access technology and proceed
with appropriate MM or GMM specific procedures.
System Simulator:
- cell A and cell B.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1471 Release 9
1471
U - S Message
cell".
- - - -
received on Cell B.
- - - -
2 Check: Does the UE transmits a TRACKING
REQUEST
1 P
expire.
counter is 1.
- - - -
REQUEST
1 P
expire.
counter is 2.
- - - -
REQUEST
1 P
expire.
counter is 3.
- - - -
REQUEST
1 P
expire.
counter is 4.
- - - -
REQUEST
1 P
counter is 5 and reset.
- - - -
REQUEST
2 P
ACCEPT
- -
COMPLETE
- -

EPS update type
updating"

Old GUTI GUTI-1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1472 Release 9
1472
Table 9.2.3.2.17.3.3-2: Message TRACKING AREA UPDATE REQUEST (step 4, step 6, step 8, step 10,
and step 13, Table 9.2.3.2.17.3.2-1)
EPS update type
updating"

Old GUTI GUTI-1
available

GUTI GUTI-2

9.2.3.3 Iu mode to S1 mode inter-system change in idle mode
9.2.3.3.1 First Iu mode to S1 mode inter-system change after attach
(1)
with { the UE is powered on in UTRAN with a USIM containing valid EPS identities and EPS security
context and has attached in UTRAN and activated a PDP context }
ensure that {
when { the UE reselects a E-UTRAN cell }
then { the UE transmits a TRACKING AREA UPDATE REQUEST message including eKSI stored in the
USIM, old GUTI mapped from RAI and P-TMSI, GPRS ciphering sequence number, nonceUE and the UE radio
capability information update needed IE, the message is integrity protected using the EPS security
context stored in the USIM and encapsulated in an RRCConnectionSetupComplete message whith
registeredMME set to the MME part of the mapped GUTI }

(2)
with { the UE has performed a TAU procedure in EUTRAN after initial registration at power on in
UTRAN }
ensure that {
when { the UE reselects a UTRAN cell }
then { the UE transmits a ROUTING AREA UPDATE REQUEST message including P-TMSI and P-TMSI
signature mapped from GUTI, previously allocated P-TMSI as additional mobile identity, RAI where P-
TMSI was allocated as additional old routing area identification, eKSI allocated in UTRAN as GPRS
ciphering key sequence number, the message is encapsulated in an INITIAL DIRECT TRANSFER message
including IDNSS mapped from P-TMSI, START value set to 0 and PLMN identity }

(3)
with { the UE has performed a TAU procedure in EUTRAN after initial registration at power on in
UTRAN and has transmitted a ROUTING AREA UPDATE REQUEST message and received an AUTHENTICATION AND
CIPHERING REQUSET message }
ensure that {
when { the UE receives a SECURITY MODE COMMAND message }
then { the UE transmits a SECURITY MODE COMPLETE and starts performing ciphering an integrity
protection using new CK and IK }

(4)
with { the UE has performed initial registration at power on in UTRAN and has EPS security context }
ensure that {
when { UE performes a TAU procedure in E-UTRAN }
then { the UE starts performing ciphering an integrity protection using EPS security context }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1473 Release 9
1473
NOTE: ISR considered not in the scope of this test case, so it is never activated.
TS 23.401 clauses 5.3.1.1, 5.3.3.1, 5.3.3.3 and Annex D; TS 25.331 clauses 8.1.8.2 and 10.3.1.6 (on IDNNS); TS
24.008 [NAS msg contents]; TS 24.301 clause 5.5.3.2.2; and TS 36.331 clauses 5.3.3.3 and 5.3.3.4.
[TS 23.003, clause 2.8.2.1]
The mapping of the GUTI shall be done to the combination of RAI of GERAN / UTRAN and the P-TMSI:
E-UTRAN <MCC>maps to GERAN/UTRAN <MCC>
E-UTRAN <MNC>maps to GERAN/UTRAN <MNC>
E-UTRAN <MME Group ID>maps to GERAN/UTRAN <LAC>
E-UTRAN <MME Code>maps to GERAN/UTRAN <RAC>and is also copied into the 8 most significant bits
of the NRI field within the P-TMSI;
E-UTRAN <M-TMSI> maps as follows:
- 6 bits of the E-UTRAN <M-TMSI>starting at bit 29 and down to bit 24 are mapped into bit 29 and down to
bit 24 of the GERAN/UTRAN <P-TMSI>;
- and the remaining 8 bits of the E-UTRAN <M-TMSI>are mapped into the 8 MBS bits of the <P-TMSI
signature>field.
For UTRAN, the 10-bit long NRI bits are masked out from the P-TMSI and also supplied to the RAN node as IDNNS
(Intra Domain NAS Node Selector). However, the RAN configured NRI length should not exceed 8 bits.
[TS 23.003, clause 2.8.2.2]
The mapping of P-TMSI (TLLI) and RAI in GERAN/UTRAN to GUTI in E-UTRAN shall be performed as follows:
GERAN/UTRAN <MCC> maps to E-UTRAN <MCC>
GERAN/UTRAN <MNC>maps to E-UTRAN <MNC>
GERAN/UTRAN <LAC> maps to E-UTRAN <MME Group ID>
GERAN/UTRAN <RAC> maps into bit 23 and down to bit 16 of the M-TMSI
The 8 most significant bits of GERAN/UTRAN <NRI>map to the MME code.
GERAN/UTRAN <P-TMSI>maps as follows:
- 6 bits of the GERAN/UTRAN <P-TMSI>starting at bit 29 and down to bit 24 are mapped into bit 29 and
down to bit 24 of the E-UTRAN <M-TMSI>;
down to bit 0 of the E-UTRAN <M-TMSI>.
The values of <LAC>and <MME group id>shall be disjoint, so that they can be differentiated. The most significant bit
of the <LAC>shall be set to zero; and the most significant bit of <MME group id>shall be set to one. Based on this
definition, the most significant bit of the <MME group id>can be used to distinguish the node type, i.e. whether it is an
MME or SGSN.
[TS 24.301 clause 5.3.1.1]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1474 Release 9
1474
...
[TS 23.401, clause 5.3.3.1, step 2, Tracking Area Update procedure with Serving GW change]
...
If the UE's TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are
indicated as the old GUTI.
...
[TS 23.401, clause 5.3.3.3, step 2, Routeing Area Update with MME interaction and without S-GW change]
...
If the UE's internal TIN indicates "GUTI" and the UE holds a valid GUTI then the UE indicates the GUTI as the old
P-TMSI and old RAI
...
[TS 24.301, clause 5.5.3.2.2 Normal and periodic tracking area updating procedure initiation]
...
If the UE supports A/Gb mode or Iu mode, the UE shall handle the GUTI as follows:
- if the TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and RAI, the UE shall map the P-TMSI and
RAI into the old GUTI IE. If a P-TMSI signature is associated with the P-TMSI, the UE shall include it in the
Old P-TMSI signature IE. Additionally, if the UE holds a valid GUTI, the UE shall indicate the GUTI in the
Additional GUTI IE.
NOTE: Mapping the P-TMSI and RAI to the GUTI is specified in Annex H of 3GPP TS 23.401 [10].
- if the TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI, the UE shall indicate the
...
ASME
or KSI
SGSN
) in the NAS
...
UE
message.

If the UE initiates the first tracking area updating procedure following an attach in A/Gb mode or Iu mode, the UE shall
include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message.
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1475 Release 9
1475
Tracking Area Update MO signalling (See Note 1) "originating signalling"

[TS 36.331, clause 5.3.3.3]
2>else
40
[TS 36.331, clause 5.3.3.4]
...
...
[TS 24.008, clause 4.7.5]
This procedure is used for:
...
- S1 mode to Iu mode or S1 mode to A/Gb mode intersystem change and ISR is not activated;
...
[TS 24.008, clause 4.7.5.1.1]
To initiate the normal routing area updating procedure, the MS sends the message ROUTING AREA UPDATE
REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-AREA-UPDATING-INITIATED.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1476 Release 9
1476
identification IE.
...
If the routing area updating procedure is initiated by the MS due to an S1 mode to Iu mode or S1 mode to A/Gb mode
inter-system change in idle mode and the TIN indicates "GUTI", the message ROUTING AREA UPDATE REQUEST
shall include a P-TMSI signature filled with a NAS token as specified in 3GPP TS 33.401 [119]. In the GPRS ciphering
key sequence number IE the MS shall indicate the value of the eKSI associated with the current EPS security context.
NOTE: When the MS includes a P-TMSI signature filled with a NAS token, 8 bits of the NAS token will be filled
with bits from the M-TMSI (see 3GPP TS 23.003 [4]).
If the routing area updating procedure is initiated by the MS due to the S1 mode to Iu mode or S1 mode to A/Gb mode
inter-system change in connected mode, the MS shall derive CK' and IK' from K
ASME
and from the NAS downlink
COUNT value indicated by lower layers as specified in 3GPP TS 33.401 [119]. If the routing area updating procedure is
initiated by the MS due to the S1 mode to Iu mode or S1 mode to A/Gb mode inter-system change in idle mode when
the TIN indicates "GUTI", the MS shall derive CK' and IK' from the K
ASME
and the NAS uplink COUNT value
corresponding to the NAS token derived as specified in 3GPP TS 33.401 [119]. The MS shall indicate the eKSI value in
the CKSN field of the GPRS ciphering key sequence number IE in the ROUTING AREA UPDATE REQUEST
message. Then, the MS shall reset the START value and store the mapped UMTS security context replacing the
established UMTS security context.
[TS 25.331, clause 8.1.8.2]
...
The UE shall, in the INITIAL DIRECT TRANSFER message:
1>set the IE "NAS message" as received from upper layers; and
1>set the IE "CN domain identity" as indicated by the upper layers; and
1>set the IE "Intra Domain NAS Node Selector" as follows:
2>derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and
2>provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:
1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a
valid TMSI/PTMSI is available;
2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;
3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.
1>if the UE, on the existing RRC connection, has received a dedicated RRC message containing the IE "Primary
PLMN Identity" in the IE "CN Information Info":
2>set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the latest PLMN information
received via dedicated RRC signalling. If NAS has indicated the PLMN towards which a signalling
connection is requested, and this PLMN is not in agreement with the latest PLMN information received via
dedicated RRC signalling, then the initial direct transfer procedure shall be aborted, and NAS shall be
informed.
1>if the UE, on the existing RRC connection, has not received a dedicated RRC message containing the IE "CN
Information Info" , and if the IE "Multiple PLMN List" was broadcast in the cell where the current RRC
connection was established:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1477 Release 9
1477
2>set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the PLMN chosen by higher
layers [5, 25] amongst the PLMNs in the IE "Multiple PLMN List" broadcast in the cell where the RRC
connection was established.
1>if the IE "Activated service list" within variable MBMS_ACTIVATED_SERVICES includes one or more
MBMS services with the IE "Service type" set to "Multicast" and;
1>if the IE "CN domain identity" as indicated by the upper layers is set to "CS domain" and;
1>if the variable ESTABLISHED_SIGNALLING_CONNECTIONS does not include the CN domain identity 'PS
domain':
2>include the IE "MBMS joined information";
2>include the IE "P-TMSI" within the IE "MBMS joined information" if a valid PTMSI is available.
1>if the UE is in CELL_FACH state and the IE "CN domain identity" as indicated by the upper layers is set to "CS
domain":
2>if the value of the variable ESTABLISHMENT_CAUSE is set to "Originating Conversational Call" or
"Emergency Call":
3>set the value of the IE "Call type" to "speech", "video" or "other" according to the call being initiated.
1>if the variable ESTABLISHMENT_CAUSE is initialised:
2>set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE;
2>clear the variable ESTABLISHMENT_CAUSE.
1>calculate the START according to subclause 8.5.9 for the CN domain as set in the IE "CN Domain Identity"; and
1>include the calculated START value for that CN domain in the IE "START".

System Simulator:
- cell A and cell 5 (UTRA cell in LAI-1/RAI-1);
- cell 5 is configured as Serving cell, cell A as Non-Suitable Off cell.
NOTE: For Cell 5, power levels are defined in TS 34.108 subclause 6.1.5 (FDD) or 6.1.6 (TDD).
UE:
registered on cell B using default message contents according to TS 36.508 [18].
Note: Cell B belongs to TAI-2 (unlike cell A).
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1478 Release 9
1478
U S Message
message on Cell 5
3 The SS transmits an AUTHENTICATION AND
CIPHERING REQUEST message.
CIPHERING REQUEST
- -
4 The UE transmits an AUTHENTICATION AND
CIPHERING RESPONSE
- -
including P-TMSI-1 and RAI-1.
message.
10 The activation of a PDP context is triggered by
MMI or AT command.
- - - -
12 The SS establishes a radio bearer associated
with the requested PDP context.
- - - -
- EXCEPTION: In parallel with step 13, IP
address allocation as specified in xx.xxx
subclause yy may occur on the radio bearer
setup in step 12..
- - - -
14 Cell A is configured as the Serving Cell, Cell 5
is configured as a Suitable Neighbour Cell.
- - - -
RRCConnectionRequest with the InitialUE-
Identity set to randomValue and the
establishmentcause set to MO-signalling?
- - 1 P
16 The SS responds with RRCConnectionSetup. - -
RRCConnectionSetupComplete message with
the mmegi and mmec are set to the values
derived from the mapped RAI and P-TMSI,
and containing a TRACKING AREA UPDATE
REQUEST message as described in the
specific message contents?
Check2: Does the UE transmit a TRACKING
AREA UPDATE REQUEST message integrity
protected using IK derived from K
ASME
?
REQUEST
1, 4 P
18 The SS responds with a TRACKING AREA
UPDATE ACCEPT allocating a new GUTI and
TAI list . This message is ciphered and
integrity protected using CK and IK derived
from K
ASME
.
ACCEPT
- -
18
A
AREA UPDATE COMPLETE message
ciphered and integrity protected using CK and
IK derived from K
ASME
.
COMPLETE
4 P
19 The SS releases the RRC connection -
20 Void -
21 Cell 5 is configured as the Serving Cell and
Cell A is configured as a Suitable Neighbour
Cell as defined in table 6.2.2.1-1 of TS 36.508
[18].

Note: Cell A is still suitable but the UE shall
select Cell 5.
-
22 Void -
23 Check: does the UE transmit a ROUTING
AREA UPDATE REQUEST message as
specified in the specific message contents
included in an INITIAL DIRECTE TRANSFER
message with intraDomainNasNodeSelector
REQUEST
2 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1479 Release 9
1479
mapped from GUTI allocationed in step 18?
23
AA
The SS sends an AUTHENTICATION AND
CIPHERING REQUEST message to perform a
UMTS AKA procedure.
CIPHERING REQUEST
- -
23
AB
The UE sends an AUTHENTICATION AND
CIPHERING RESPONSE
- -
23
A
The SS sends a SECURITY MODE
COMMAND message to activate integrity
protection and ciphering. This message is
integrity protected using new IK.
- - - -
23
B
Check: Does the UE transmit a SECURITY
MODE COMPLETE message integrity
protected using new IK?
- - 3 P
24 The SS transmits a ROUTING AREA UPDATE
ACCEPT message (no new P-TMSI nor RAI).
This message is ciphered and integrity
protected using CK and IK derived at step
23AA.
ACCEPT
- -
25 After the activation time indicated at step 23A,
the SS transmits a UE CAPABILITY
ENQUIRY message requesting the UE E-
UTRAN capabilty. This message is ciphered
and integrity protected using CK and IK
derived at step 23AA.
- - - -
26 Check: Does the UE transmit a UE
CAPABILITY INFORMATION message?

Note: the purpose of this message is to show
that the UE uses CK and IK derived at step
23AA, and not the CK and IK allocated at step
4.
- - 3 P
27 The SS transmits a UE CAPABILITY
INFORMATION CONFIRM message.
- - - -
28 The SS releases the RRC connection -

random-Value Any allowed value
}
establishmentCause Mo-Signalling
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1480 Release 9
1480
c1 CHOICE {
selectedPLMN-Identity 1
registeredMME {
plmn-Identity Not present
mmegi LAC sent to the UE in
step 8

mmec Bit 23 to bit 16 of P-TMSI
sent to the UE in step 8

}
dedicatedInfoNAS See table 9.2.3.3.1.3.3.-3
nonCriticalExtension SEQUENCE {}
}
}
}
}
Details to be added

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1481 Release 9
1481
Derivation path: 36.508 table 4.7.2-24 with condition UNCIPHERED (the message is integrity protected using the key
stored in the USIM).
EPS update type 000 or 001 'TA updating' or
'combined TA/LA
updating'

NAS key set identifier The valid NAS key set
identifier stored in the
USIM

context (for
KSI
ASME
)

Old GUTI or IMSI
Type of identity 110 GUTI
MNC/MCC Mobile Country Code and
Mobile Network Code
stored in EF
IMSI
on the
test USIM

MME Group ID LAI allocated at step 8
MME Code Bit 23 to bit 16 of P-TMSI
allocated at step 8

M-TMSI Value is specified bit by
bit below:
- bit 31 and bit 30: FFS
- bit 29 to bit 24: bit 29 to
bit 24 of P-TMSI
allocated at step 8
- bit 23 to bit 16: RAC
allocated at step 8
bit 0 of P-TMSI allocated
at step 8

GPRS ciphering key sequence number GPRS ciphering key
sequence number
allocated at step 3

Old P-TMSI signature P-TMSI signature
allocated at step 8

Additional GUTI GUTI-1
Nonce
UE
Any allowed value (must
be present)

UE network capability Any allowed value (must
be present)

Last visited registered TAI TAI stored in the test
USIM

UE radio capability information update needed 1 UE radio
capability
information
update needed

MS network capability Any allowed value (must
be present)

Old location area identification Not present if "EPS
update type" is 'TA
updating', LAI-1 is "EPS
update type" is
'combined TA/LA
updating'


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1482 Release 9
1482
Table 9.2.3.3.1.3.3-4: INITIAL DIRECT TRANSFER (step 23, Table 9.2.3.3.1.3.2-1)
Derivation path: 25.331 clause 11
InitialDirectTransfer ::=SEQUENCE {
cn-DomainIdentity ps-domain
intraDomainNasNodeSelector SEQUENCE {
version CHOICE {
release99 SEQUENCE {
gsm-Map-IDNNS SEQUENCE {
routingbasis CHOICE {
localPTMSI {
routingparameter bit 23 to bit 14 of P-TMSI
allocated at step 8

}
}
}
}
}
}
}
nas-Message See table 9.2.3.3.1.3.3-5
measuredResultsOnRACH Not checked
initialDirectTransfer-v3a0ext SEQUENCE {
start-Value 00000000000000000000
0

}
initialDirectTransfer-r3-add-ext Not checked
v590NonCriticalExtension SEQUENCE {
initialDirectTransfer-v590ext Not checked
initialDirectTransfer-v690ext SEQUENCE {
mcc Mobile Country Code
stored in EF
IMSI
on the
test USIM

mnc Mobile Network Code
stored in EF
IMSI
on the
test USIM

}
measuredResultsOnRACHinterFreq Not checked
mbms-J oinedInformation Not checked
}
v770NonCriticalExtensions Not checked
}
}
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1483 Release 9
1483
Table 9.2.3.3.1.3.3-5: Message ROUTING AREA UPDATE REQUEST (step 23, Table 9.2.3.3.1.3.2-1)
Derivation path: 24.008 table 9.4.14
Update type 000 RA updating
GPRS ciphering key sequence number eKSI stored on the test
USIM

Old routing area identification GUTI-1 right shifted by
32bits

Old P-TMSI signature Value is specified bit by
bit below:
bit 16 of M-TMSI
allocated in step 18
- bit 15 to bit 0: FFS

Requested READY timer value Not checked
P-TMSI Value is specified bit by
bit below:
- bit 31 and bit 30: 1
bit 24 of M-TMSI
allocated in step 18
- bit 23 to bit 16: MME
code allocated in step 18
bit 0 of M-TMSI allocated
in step 18

PDP context status Not checked
MBMS context status Not checked
UE network capability Any allowed value
Additional mobile identity P-TMSI allocated in step
8

Additional old routing area identification RAI-1

9.2.3.3.2 Iu mode to S1 mode intersystem change / ISR is active / Expiry of T3312 in E-
UTRAN or T3412 in UTRAN and further intersystem change
(1)
with { the UE is camped on a E-UTRAN cell, ISR is active, T3312 has expired, T3323 hasn't expired }
ensure that {
when { UE enters a UTRAN cell belonging to the RA where the UE was last updated }
then { the UE performs a RAU procedure including the UE P-TMSI and RAI }
}
(2)
with { the UE is camped on a E-UTRAN cell, ISR is active, T3312 and T3323 have expired }
ensure that {
when { UE enters a UTRAN cell belonging to the RA where the UE was last updated }
then { the UE performs a RAU procedure including mapped identities from E-UTRAN and additional
P-TMSI and old RAI }
}
(3)
with { the UE is camped on a UTRAN cell, ISR is active, T3412 has expired, T3423 hasn't expired }
ensure that {
when { UE enters a E-UTRAN cell in a TA belonging to the current TA list }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1484 Release 9
1484
then { the UE performs a TAU procedure including the UE GUTI and last visited TAI}
}

(4)
with { the UE is camped on a UTRAN cell, ISR is active, T3412 and T3423 have expired }
ensure that {
when { the UE enters a E-UTRAN cell in a TA belonging to the current TA list }
then { the UE performs a TAU procedure incliding mapped GUTI from UTRAN, P-TMSI signature and
additional GUTI}

References: The conformance requirements covered in the present TC are specified in: TS 24.301 clauses 5.3.5 and
5.5.3.2.2 and TS 24.008 clauses 4.7.2.2 and 4.7.5.1.1.
[24.301, clause 5.3.5]
If ISR is activated, the UE shall keep both the periodic tracking area update timer (timer T3412) and the periodic
routeing area update timer (timer T3312). The two separate timers run in the UE for updating MME and SGSN
independently. If the periodic tracking area update timer expires and the UE cannot initiate the tracking area updating
procedure, as it is in state EMM-REGISTERED.NO-CELL-AVAILABLE, the UE shall start the E-UTRAN deactivate
ISR timer T3423. The UE shall initiate the tracking area updating procedure and stop the timer T3423 when it enters
state EMM-REGISTERED.NORMAL-SERVICE before timer T3423 expires. After expiry of timer T3423 the UE shall
set its TIN to "P-TMSI" in order to initiate the tracking area updating procedure when it returns to state EMM-
REGISTERED.NORMAL-SERVICE.
If the UE is attached to both EPS and non-EPS services, and if timer T3412 expires or timer T3423 expires when the
UE is in EMM-REGISTERED.NO-CELL-AVAILABLE state, then the UE shall initiate the combined tracking area
updating procedure indicating "combined TA/LA updating with IMSI attach" when the UE returns to EMM-
REGISTERED.NORMAL-SERVICE state.
[24.301, clause 5.5.3.2.2]
...
If the UE supports neither A/Gb mode nor Iu mode, the UE shall include a valid GUTI in the Old GUTI IE in the
TRACKING AREA UPDATE REQUEST message.
RAI into the Old GUTI IE. If a P-TMSI signature is associated with the P-TMSI, the UE shall include it in the
Additional GUTI IE.
[24.008, clause 4.7.2.2]
If ISR is activated, the MS shall keep both the periodic tracking area update timer (timer T3412) and the periodic
routeing area update timer (timer T3312). The two separate timers run in the MS for updating MME and SGSN
independently. If the periodic routeing area update timer expires and the MS is in state GMM-REGISTERED.NO-
CELL-AVAILABLE, the MS shall set its TIN to "RAT-related TMSI" and start the GERAN/UTRAN Deactivate ISR
timer T3323. The MS shall initiate the routeing area updating procedure and stop the timer T3323 when the MS enters
the state GMM-REGISTERED.NORMAL-SERVICE before timer T3323 expires. After expiry of timer T3323 the MS
shall deactivate ISR by setting its TIN to "GUTI" and initiate the routing area updating procedure when the MS enters
the state GMM-REGISTERED.NORMAL-SERVICE.
...
If the MS is both IMSI attached for GPRS and non-GPRS services, and if the MS lost coverage of the registered PLMN
and timer T3312 expires or timer T3323 expires, then:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1485 Release 9
1485
a) if the MS returns to coverage in a cell that supports GPRS and that indicates that the network is in network
operation mode I, then the MS shall either perform the combined routing area update procedure indicating
"combined RA/LA updating with IMSI attach"; or
b) if the MS returns to coverage in a cell in the same RA that supports GPRS and that indicates that the network is
in network operation mode II or III, then the MS shall perform the periodic routing area updating procedure
indicating "Periodic updating"; or
c) if the MS was both IMSI attached for GPRS and non-GPRS services in network operation mode I and the MS
returns to coverage in a cell in the same LA that does not support GPRS, then the MS shall perform the periodic
location updating procedure. In addition, the MS shall perform a combined routing area update procedure
indicating "combined RA/LA updating with IMSI attach" when the MS enters a cell that supports GPRS and that
indicates that the network is in network operation mode I; or
d) if the MS returns to coverage in a new RA the description given in subclause 4.7.5 applies.
If the MS is both IMSI attached for GPRS and non-GPRS services in a network that operates in network operation
mode I, and if the MS has camped on a cell that does not support GPRS, and timer T3312 expires or timer T3323
expires, then the MS shall start an MM location updating procedure. In addition, the MS shall perform a combined
routing area update procedure indicating "combined RA/LA updating with IMSI attach" when the MS enters a cell that
supports GPRS and indicates that the network is in operation mode I.
If timer T3312 expires or timer T3323 expires during an ongoing CS connection, then a MS operating in MS operation
mode B shall treat the expiry of T3312 when the MM state MM-IDLE is entered, analogous to the descriptions for the
cases when the timer expires out of coverage or in a cell that does not support GPRS.
In A/Gb mode, timer T3312 and timer T3323 shall not be stopped when a GPRS MS enters state GMM-
REGISTERED.SUSPENDED.
[24.008, clause 4.7.5.1.1]
...
identification IE.
System Simulator:
- cell A and cell 5 (HPLMN);
- cell 5 indicates NMO 2.
UE:
none.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1486 Release 9
1486
Preamble:
- the UE is in state Registered, Idle Mode (state 2) on cell A according to TS 36.508 [18] and with M-TMSI =
9a26319c (arbitrary value chosen for this test case).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1487 Release 9
1487
U - S Message
1 The SS sets the cell type of Cell 5 to "Serving
Cell" and the cell type of Cell A to "Non-
suitable cell".
- - - -
2 The UE transmits a ROUTING AREA UPDATE
message on cell 5.
REQUEST
- -
ACCEPT message on Cell 5 with Update
result 'RA updated and ISR activated', T3312
set to 1 minute and T3323 set to 2 minutes.
ACCEPT
- -
COMPLETE
- -
5 The SS sets the cell type of Cell A to "Serving
cell" and the cell type of Cell 5 to "Non-suitable
cell".
- - - -
6 90s after step 3, the SS sets the cell type of
Cell 5 to "Serving Cell" and the cell type of Cell
A to "Non-suitable cell".
- - - -
5?
REQUEST
1 P
ACCEPT message on Cell 5 with with Update
result 'RA updated and ISR activated', T3312
set to 1 minute and T3323 set to 1 minutes.
ACCEPT
- -
cell".
- - - -
Cell 5 to "Serving Cell" and the cell type of Cell
A to "Non-suitable cell".
- - - -
5?
REQUEST
2 P
result value =000 (RA updated).
ACCEPT
- -
cell".
- - - -
UPDATE REQUEST message
REQUEST
- -
result indicating that ISR is active, T3412 set to
1 minute and T3423 set to 2 minutes.
ACCEPT
- -
COMPLETE
- -
suitable cell".
- - - -
Cell A to "Serving cell" and the cell type of Cell
5 to "Non-suitable cell".
- - - -
A?
REQUEST
3 P
result indicating that ISR is active, T3412 set to
1 minute and T3423 set to 1 minute.
ACCEPT
- -
suitable cell".
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1488 Release 9
1488
Cell A to "Serving cell" and the cell type of Cell
5 to "Non-suitable cell".
- - - -
A?
REQUEST
4 P
ACCEPT
- -
- The UE is in end state E-UTRA connected
(E2).
- - - -

Table 9.2.3.3.2.3.3-1: Message ROUTING AREA UPDATE ACCEPT (step 3, table 9.2.3.3.2.3.2-1)
Update result 100 RA updated and
ISR activated
TA only
101 combined TA/LA
updated and ISR
activated
combined_
TA_LA
Periodic RA update timer 00100001 1 minute
Routing area identification See 36.508 table 4.4.4-2 RAI of Cell 5
P-TMSI signature Not present
Allocated P-TMSI
RAI
TMSI

See 36.508 table 4.4.4-2
efb1ee97
TMSI is an
arbitrary value
chosen different
from M-TMSI in
the preamble

T3323 value 00100010 2 minutes

Table 9.2.3.3.2.3.3-2: Message ROUTING AREA UPDATE REQUEST (step 7, table 9.2.3.3.2.3.2-1)
Update type Any allowed value
GPRS ciphering key sequence number Any allowed value
Old routing area identification RAI of Cell 5 according to
36.508 table 4.4.4-2
The UE includes
the RAI from
UTRAN

P-TMSI Same value like allocated
at step 3, see table
9.2.3.3.2.3.3-1
The UE includes
the P-TMSI
assigned from
UTRAN


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1489 Release 9
1489
ISR activated
TA only
101 combined TA/LA
updated and ISR
activated
combined_
TA_LA
Periodic RA update timer 00100001 1 minute
Allocated P-TMSI Not present
T3323 value 00100001 1 minute

Table 9.2.3.3.2.3.3-4: Message ROUTING AREA UPDATE REQUEST (step 11, table 9.2.3.3.2.3.2-1)
GPRS ciphering key sequence number Any allowed value
Old routing area identification TAI of cell A The value is the
same as the RAI
of cell 5

P-TMSI da01319c Mapped from M-
TMSI and MME
code assigned in
the preamble
(start with 11 and
MME code in 2
nd

most significant
byte).

Additionnal mobile identity Same value like allocated
at step 3, see table
9.2.3.3.2.3.3-1

Additional routing area identification RAI of cell 5 The value is the
same as the TAI
of cell A

Update result 000 RA updated
Periodic RA update timer 01010101 54 minutes
Allocated P-TMSI Not present

Table 9.2.3.3.2.3.3-6: Message TRACKING AREA UPDATE REQUEST (step 14, table 9.2.3.3.2.3.2-1)
EPS update type Any allowed value

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1490 Release 9
1490
Table 9.2.3.3.2.3.3-7: Message TRACKING AREA UPDATE ACCEPT (step 15, table 9.2.3.3.2.3.2-1)
EPS update result 100 TA updated and
ISR activated
TA_only
101 combined TA/LA
updated and ISR
activated
combined_
TA_LA
GUTI
M-TMSI 9a26319c Same value like in
preamble,
different from P-
TMSI

Old GUTI Same GUTI as in step 15
see table 9.2.3.3.2.3.3-7

Last visited registered TAI RAI of cell 5 The value is the
same as the TAI
of cell A

EPS update result 100 TA updated and
ISR activated
TA_only
101 combined TA/LA
updated and ISR
activated
combined_
TA_LA
GUTI Not present

Old GUTI
M-TMSI ef01ee97 Mapped from P-
TMSI assigned in
the preamble and
RAI of cell 5 (start
with 11 and RAI in
2
nd
most
significant byte).

Last visited registered TAI RAI of cell 5
Additional GUTI Same GUTI as in step 15
see table 9.2.3.3.2.3.3-7

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1491 Release 9
1491
EPS update result 000 TA updated TA_only
001 combined TA/LA
updated
combined_
TA_LA
GUTI Not present

9.2.3.3.3 Void
9.2.3.3.4 First S1 mode to Iu mode inter-system change after attach
(1)
with { the UE powered on in E-UTRAN with a USIM containing valid E-UTRAN NAS and Security parameters
including a valid GUTI, and has successfully performed a combined EPS/IMSI attach, established PDN
connectivity, and performed TRACKING AREA UPDATE REQUEST }
ensure that {
when { the UE reselects UTRAN configured in MNO=II and TIN is set to the temporary ID belonging to
the currently used RAT (i.e. ISR not active) }
then { the UE transmits a LOCATION UPDATING REQUEST to the MSC/VLR and derives the IDNNS from
the MSC/VLR TMSI, and transmits a ROUTING AREA UPDATE REQUEST message including P-TMSI, P-TMSI
signature including the NAS token, and RAI mapped from GUTI, the old routing area identification
mapped from the RAI, the GPRS ciphering key sequence number indicating the eKSI associated with the
EPS security context. Old P-TMSI signature and Old routing area identifion are mapped from the GUTI.
The message is encapsulated in an INITIAL DIRECT TRANSFER message including IDNSS mapped from GUTI,
Establishment cause set to inter-RAT cell-selection, START value set to 0 and PLMN identity }

(2)
with { the UE camped on E-UTRAN and has a valid GUTI and P-TMSI }
ensure that {
when { the UE reselects UTRAN and receives a new P-TMSI as part of the RAU procedure }
then { the UE uses the new P-TMSI (and not GUTI or old P-TMSI) for subsequent IDNNS network
access (e.g. via the Service Request procedure }
}

(3)
with { the UE has performed a RAU procedure in UTRAN after initial registration at power on in E-
UTRAN }
ensure that {
when { the UE reselects a E-UTRAN cell with the same LA as previously selected}
then { the UE transmits a TRACKING AREA UPDATE REQUEST message including eKSI stored in the USIM,
old GUTI mapped from RAI and P-TMSI, GPRS ciphering sequence number, nonceUE. The UE encodes the RRC
parameters in the RRC Connection Establishment messages correctly (i.e. in the RRCConnectionRequest
message, the InitialUE-Identity is set to "Random value and the establishmentcause is set to MO-
signalling; and, in the RRCConnectionSetupComplete message the selectedPLMN-identity, mmegi and mmec
indicate the value of the registered MME (e.g. as retrieved from the USIM at power-on, or, as
received in the last TRACKING AREA UPDATE ACCEPT message) }
}

(4)
with { the UE has transmitted a ROUTING AREA UPDATE REQUEST message after initial registration at
power on in E-UTRAN }
ensure that {
protection using CK' and IK' derived from K
ASME
and UL NAS COUNT }

(5)
with { the UE has received an AUTHENTICATION AND CIPHERING REQUSET message after it has performed
ciphering an integrity protection using CK' and IK' derived from K
ASME
and UL NAS COUNT }
ensure that {

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1492 Release 9
1492
protection using new CK and IK }

NOTE: ISR considered not in the scope of this test case, so it is never activated.
TS 23.401 Annex J.2; TS 24.301 clause 5.5.3.2.2 and Annex D; TS 25.331 clauses 8.1.8.2 and 8.1.8.3 (on IDNNS); TS
24.008 clause 4.7.5.1.1 and 4.7.5.1.3; TS 23.236 clause 5.1; and TS 36.331 clauses 5.3.3.3 and 5.3.3.4.
[TS 23.003, clause 2.8.2.1]
E-UTRAN <MME Code>maps to GERAN/UTRAN <RAC>and is also copied into the 8 most significant bits
of the NRI field within the P-TMSI;
signature>field.
[TS 23.003, clause 2.8.2.2]
GERAN/UTRAN <MCC> maps to E-UTRAN <MCC>
GERAN/UTRAN <LAC> maps to E-UTRAN <MME Group ID>
GERAN/UTRAN <RAC> maps into bit 23 and down to bit 16 of the M-TMSI
The values of <LAC>and <MME group id>shall be disjoint, so that they can be differentiated. The most significant bit
of the <LAC>shall be set to zero; and the most significant bit of <MME group id>shall be set to one. Based on this
definition, the most significant bit of the <MME group id>can be used to distinguish the node type, i.e. whether it is an
MME or SGSN.
[TS 23.401, Annex J .2 "Usage of TIN]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1493 Release 9
1493

When ISR is not active the TIN is always set to the temporary ID belonging to the currently used RAT. This guarantees
that always the most recent context data are used, which means during inter-RAT changes there is always context
transfer from the CN node serving the last used RAT. The UE identities, old GUTI IE and additional GUTI IE,
indicated in the next TAU Request message, and old P-TMSI IE and additional P-TMSI/RAI IE, indicated in the next
RAU Request message depend on the setting of TIN and are specified in table 4.3.5.6-2.
[TS 24.301, clause 5.5.3.2.2 "Normal and periodic tracking area updating procedure initiation]
...
If the UE supports A/Gb mode or Iu mode, the UE shall handle the GUTI as follows:
RAI into the old GUTI IE. If a P-TMSI signature is associated with the P-TMSI, the UE shall include it in the
Additional GUTI IE.
...
ASME
or KSI
SGSN
) in the NAS
...
UE
message.

...
...
Tracking Area Update MO signalling (See Note 1) "originating signalling"
...

[TS 36.331, clause 5.3.3.3]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1494 Release 9
1494
2>else
40
[TS 36.331, clause 5.3.3.4]
...
...
[TS 24.008, clause 4.7.5.1.1]
identification IE.
...
inter-system change in idle mode and the TIN indicates "GUTI", the message ROUTING AREA UPDATE REQUEST
shall include a P-TMSI signature filled with a NAS token as specified in 3GPP TS 33.401 [119]. In the GPRS ciphering
key sequence number IE the MS shall indicate the value of the eKSI associated with the current EPS security context.
NOTE: When the MS includes a P-TMSI signature filled with a NAS token, 8 bits of the NAS token will be filled
with bits from the M-TMSI (see 3GPP TS 23.003 [4]).
inter-system change in connected mode, the MS shall derive CK' and IK' from K
ASME
and from the NAS downlink
COUNT value indicated by lower layers as specified in 3GPP TS 33.401 [119]. If the routing area updating procedure is
initiated by the MS due to the S1 mode to Iu mode or S1 mode to A/Gb mode inter-system change in idle mode when
the TIN indicates "GUTI", the MS shall derive CK' and IK' from the K
ASME
and the NAS downlink COUNT value
corresponding to the NAS token derived as specified in 3GPP TS 33.401 [119]. The MS shall indicate the eKSI value in
the CKSN field of the GPRS ciphering key sequence number IE in the ROUTING AREA UPDATE REQUEST
message. Then, the MS shall reset the START value and store the mapped UMTS security context replacing the
established UMTS security context.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1495 Release 9
1495
[TS 24.008, clause 4.7.5.1.3]

A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA
UPDATE ACCEPT message contained any of:
- a P-TMSI;
- Receive N-PDU Numbers (see 3GPP TS 44.065 [78] and 3GPP TS 25.322 [19b]); or
- a request for the provision of Inter RAT handover information or E-UTRAN inter RAT handover information or
both.
If Receive N-PDU Numbers were included, the Receive N-PDU Numbers values valid in the MS, shall be included in
the ROUTING AREA UPDATE COMPLETE message.
If the network has requested the provision of Inter RAT handover information or E-UTRAN inter RAT handover
information or both, the MS shall return a ROUTING AREA UPDATE COMPLETE message including the Inter RAT
handover information IE or E-UTRAN inter RAT handover information IE or both to the network.
NOTE 1: In Iu mode, after a routing area updating procedure, the mobile station can initiate Service Request
procedure to request the resource reservation for the active PDP contexts if the resources have been
released by the network or send upper layer message (e.g. ACTIVATE PDP CONTEXT REQUEST) to
the network via the existing PS signaling connection.
In Iu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has
indicated "follow-on request pending" in ROUTING AREA UPDATE REQUEST message) the network shall indicate
the "follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. If the network wishes to release the PS
signalling connection, the network shall indicate "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT
message.
After that in Iu mode, the mobile station shall act according to the follow-on proceed flag included in the Update result
information element in the ROUTING AREA UPDATE ACCEPT message (see subclause 4.7.13).
[TS 23.236, clause 5.1 "MS Functions]
...
In Iu mode the MS provides the IDNNS to the RNC in the access stratum part of the RRC_initial_DT message as
described in TS 25.331 [5].
If the MS is E-UTRAN capable, then TS 23.401 [22], TS 23.060 [2] and TS 23.003 [18] define rules as to how the MS
shall select and encode the identity to place in the P-TMSI/TLLI parameters used in the Routing Area Update procedure.
For the PS domain, the E-UTRAN capable MS shall use this P-TMSI parameter to derive the UTRAN IDNNS
parameter. For the CS domain, the E-UTRAN temporary identities shall not be used to derive the IDNNS: instead the
MS shall use its (MSC supplied) TMSI, if that TMSI is valid, to derive the IDNNS.

When the MS in Iu mode replies to IMSI paging, it shall derive IDNNS from (P)TMSI if a valid one is available. If
(P)TMSI is not available, the MS shall derive IDNNS from IMSI.
[TS 25.331, clause 8.1.8.2]
...
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

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1496 Release 9
1496
2>provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:
1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a
valid TMSI/PTMSI is available;
2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;
3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.
1>if the UE, on the existing RRC connection, has received a dedicated RRC message containing the IE "Primary
PLMN Identity" in the IE "CN Information Info":
2>set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the latest PLMN information
received via dedicated RRC signalling. If NAS has indicated the PLMN towards which a signalling
connection is requested, and this PLMN is not in agreement with the latest PLMN information received via
dedicated RRC signalling, then the initial direct transfer procedure shall be aborted, and NAS shall be
informed.
1>if the UE, on the existing RRC connection, has not received a dedicated RRC message containing the IE "CN
Information Info" , and if the IE "Multiple PLMN List" was broadcast in the cell where the current RRC
connection was established:
2>set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the PLMN chosen by higher
layers [5, 25] amongst the PLMNs in the IE "Multiple PLMN List" broadcast in the cell where the RRC
connection was established.
[TS 25.331, clause 8.1.8.3]
On reception of the INITIAL DIRECT TRANSFER message the NAS message should be routed using the IE "CN
Domain Identity". UTRAN may also use the IE "Intra Domain NAS Node Selector" and the IE "PLMN identity" for
routing among the CN nodes for the addressed CN domain.
If no signalling connection exists towards the chosen node, then a signalling connection is established.
When the UTRAN receives an INITIAL DIRECT TRANSFER message, it shall not affect the state of any other
ongoing RRC procedures, when not stated otherwise elsewhere.
The UTRAN should:
1>set the START value for the CN domain indicated in the IE "CN domain identity" to the value of the IE
"START".
System Simulator:
- cell A is configured as Serving cell, cell 5 as Non-Suitable Off cells;
- cell 5 is operating in network operation mode II (No Gs interface present);
- cell A has the absolute priorities set to LTE.
NOTE: For cell 5, power levels are defined in TS 34.108 subclause 6.1.5 (FDD) or 6.1.6 (TDD).
UE:
- the UE is previously registered on UTRAN, and when on UTRAN, the UE is last registered on cell 5 using
default message contents according to TS 36.508 [18].
Preamble:
- the UE is in state Registered Idle Mode (state 2) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1497 Release 9
1497
U S Message
1 The signal strength of Cell 5 is raised to that of
the Serving Cell and that of Cell A is lowered
to that of a non-Suitable Neighbour Cell as
defined in table 6.2.2.1-1 of TS 36.508 [18].
- - - -
2 Wait [10] seconds for mobile to camp on cell 5 - - - -
3 Check: The UE transmits a LOCATION
UPDATING REQUEST on cell 5 to the MSC
as specified in the specific message contents
included in an INITIAL DIRECT TRANSFER
mapped from MSC TMSI allocated in the
ATTACH ACCEPT message (step 14 table
4.5.2.3-1 of TS 36.508 [18])).
REQUEST
1 P
4 The SS transmits a LOCATION UPDATING
ACCEPT message.
5 Check: Does the UE transmits a ROUTING
AREA UPDATE REQUEST message on Cell 5
as specified in the specific message contents
included in an INITIAL DIRECT TRANSFER
mapped from GUTI-1 and Establishment
Cause set to inter-RAT cell-selection.

Note: This step is run in parallel with step 3.
REQUEST
1 P
5A The SS sends a SECURITY MODE
protection and ciphering. This message is
integrity protected using IK' derived from K
ASME

and UL NAS COUNT.
- - - -
5B Check: Does the UE transmit a SECURITY
MODE COMPLETE message integrity
protected using IK' derived from K
ASME
and UL
NAS COUNT?
- - 4 P
ACCEPT message with Update result ="RA
updated and new P-TMSI allocated with a
different NRI (=IDNNS) to that in the GUTI and
the P-TMSI that was stored on the USIM. This
message is ciphered and integrity protected
using CK' and IK' derived from K
ASME
and UL
NAS COUNT.
ACCEPT
- -
AREA UPDATE COMPLETE message
ciphered and integrity protected using CK' and
IK' derived from K
ASME
and UL NAS COUNT?
COMPLETE
4 P
9 The SS transmits Paging with new P-TMSI
allocated in step 6 on cell 5
<-- Page - -
10 Check: Does the UE send a Service Request
to access the PS domain using IDNNS
mapped from the P-TMSI allocated in step 6.
10
A
The SS sends an AUTHENTICATION AND
CIPHERING REQUEST message to perform a
UMTS AKA procedure.
CIPHERING REQUEST
- -
10
B
The UE sends an AUTHENTICATION AND
CIPHERING RESPONSE
- -
11 The SS sends a SECURITY MODE
protection and ciphering . This message is
integrity protected using new IK.
- - - -
11 Check: Does the UE transmit a SECURITY - - 5 -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1498 Release 9
1498
A MODE COMPLETE message integrity
protected using new IK?
11
B
The SS transmits a UE CAPABILITY
ENQUIRY message requesting the UE E-
UTRAN capability. This message is ciphered
and integrity protected using new CK and IK.

Check: Does the UE transmit a UE
CAPABILITY INFORMATION message?

Note: the purpose of this message is to show
that the UE uses new CK and IK, and not CK'
and IK' used in step 7.
- - 5 P
12
A
Cell A is configured as the Serving cell and cell
5 is configured as a Suitable Neighbour Cell.
- - - -
12
B
Check: does the UE transmit an
Identity set to "random value and the
establishmentcause set to MO-signalling?
13 The SS responds with RRCConnectionSetup. <-- RRCConnectionSetup
RRCConnectionSetupComplete message with
the mmegi and mmec set to the values derived
from the mapped RAI and P-TMSI, and
containing a TRACKING AREA UPDATE
REQUEST message as described in the
specific message contents?

NOTE: The UE should not include "radio
capability information in the TAU request.
REQUEST
3 P
ACCEPT


Table 9.2.3.3.4.3.3-1: Void
Table 9.2.3.3.4.3.3-2: Void
Table 9.2.3.3.4.3.3-3: LOCATION UPDATING REQUEST (step 3, Table 9.2.3.3.4.3.2-1)
Update type 1000 LA updating
Ciphering key sequence number eKSI stored on the test
USIM

Location area identification PLMN=MCC/MNC
TAC 1=1

''PLMN is set to
the same
MCC/MNC stored
in EF
IMSI
''
''TAI-1''

Mobile identity TMSI-1 Allocated in
preamble

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1499 Release 9
1499
Table 9.2.3.3.4.3.3-4: INITIAL DIRECT TRANSFER (step 5, Table 9.2.3.3.4.3.2-1)
Derivation path: 25.331 clause 11
InitialDirectTransfer ::=SEQUENCE {
cn-DomainIdentity ps-domain
intraDomainNasNodeSelector SEQUENCE {
version CHOICE {
release99 SEQUENCE {
gsm-Map-IDNNS SEQUENCE {
routingbasis CHOICE {
localPTMSI {
Routingparameter bit 23 to bit 14 of P-TMSI
allocated in pre-test

}
}
}
}
}
}
}
nas-Message See table 9.2.3.3.4.3.3-5
measuredResultsOnRACH Not checked
initialDirectTransfer-v3a0ext SEQUENCE {
start-Value 00000000000000000000
0

}
initialDirectTransfer-r3-add-ext Not checked
v590NonCriticalExtension SEQUENCE {
establishmentCause Inter-RAT cell re-
selection

}
Mcc Mobile Country Code
stored in EF
IMSI
on the
test USIM

Mnc Mobile Network Code
stored in EF
IMSI
on the
test USIM

}
measuredResultsOnRACHinterFreq Not checked
mbms-J oinedInformation Not checked
}
v770NonCriticalExtensions Not checked
}
}
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1500 Release 9
1500
GPRS ciphering key sequence number eKSI stored on the test
USIM

Old routing area identification GUTI-1 right shifted by
32bits

Old P-TMSI signature Mapped from GUTI-1
Requested READY timer value Not checked
P-TMSI Value is specified bit by
bit below:
- bit 31 and bit 30: 1
bit 24 of M-TMSI
allocated in preamble
- bit 23 to bit 16: MME
code allocated in
preamble
bit 0 of M-TMSI allocated
in preamble

PDP context status Not checked
MBMS context status Not checked
UE network capability Any allowed value
Additional mobile identity P-TMSI allocated in pre-
test

Additional old routing area identification RAI-1

Table 9.2.3.3.4.3.3-6: Message SERVICE REQUEST (step 10, Table 9.2.3.3.4.3.2-1)
Ciphering key sequence number FFS
Service Type 010 (Paging Response)
P-TMSI P-TMSI allocated in step
6.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1501 Release 9
1501
Table 9.2.3.3.4.3.3-6A: SECURITY MODE COMMAND (step 11, Table 9.2.3.3.4.3.2-1)
RRC transaction identifier Arbitrarily selects an
integer between 0 and 3

Integrity check info
- Message authentication code Set to MAC-I value
computed by the SS. The
first/ leftmost bit of the bit
string contains the most
significant bit of the MAC-
I.

- RRC Message Sequence Number Set to an arbitrarily
selected integer between
0 and 15

Security capability Set same value as
originally sent by UE in
the RRC CONNECTION
SETUP COMPLETE
message in step 10.

Ciphering mode info
- Ciphering mode command Start/restart
- Ciphering algorithm Set one of the algorithms
supported by the UE as
indicated in the IE
"security capability" in the
RRC CONNECTION
SETUP COMPLETE
message in step 10.

- Ciphering activation time for DPCH Not Present
- Radio bearer downlink ciphering activation
time info

- Radio bearer activation time
- RB identity 1
- RLC sequence number Current RLC SN stored in
the SS

- RB identity 2
the SS +2

- RB identity 3
the SS

- RB identity 4
the SS

Integrity protection mode info
- Integrity protection mode command startIntegrityProtection
- Integrity protection initialisation number Arbitrary selects 32 bits
number for FRESH

- Integrity protection algorithm Set one of the algorithms
supported by the UE as
indicated in the IE
"security capability" in the
RRC CONNECTION
SETUP COMPLETE
message in step 10.

CN domain identity PS
UE system specific security capability Not present not GSM
UE system specific security capability GSM
- Inter-RAT UE security capability
- CHOICE system GSM
- GSM security capability Set the same as the
algorithms supported by
the UE as indicated in
the IE "UE system
specific capability" in the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1502 Release 9
1502
RRC CONNECTION
SETUP COMPLETE
message in step 10.

GSM UE supporting GSM

Table 9.2.3.3.4.3.3-6B: SECURITY MODE COMPLETE (step 11 A , Table 9.2.3.3.4.3.2-1)
RRC transaction identifier The value of this IE is
checked to see that it
matches the value of the
same IE transmitted in
the downlink SECURITY
MODE COMMAND
message.

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. The first/ leftmost
bit of the bit string
contains the most
significant bit of the MAC-
I.

- RRC Message Sequence Number The value is used by SS
to compute the XMAC-I
value.

Uplink integrity protection activation info
- 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
- Radio bearer activation time
- RB Identity 1
- RLC sequence number Check to see if the RLC
SN for RB1is present

- RB Identity 2
SN for RB2is present

- RB Identity 3
SN for RB3 is present

- RB Identity 4
SN for RB4 is present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1503 Release 9
1503
Table 9.2.3.3.4.3.3-7: Message RRCConnectionRequest (step 12 B, Table 9.2.3.3.4.3.2-1)
}
}
}
}

c1 CHOICE {
selectedPLMN-Identity 1
registeredMME {
plmn-Identity Not present
Mmegi LAC sent to the UE in
step 6

Mmec Bit 23 to bit 16 of P-TMSI
sent to the UE in step 6

}
dedicatedInfoNAS See table 9.2.3.3.4.3.3-9
nonCriticalExtension SEQUENCE {}
}
}
}
}
Details to be added

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1504 Release 9
1504
Derivation path: 36.508 table 4.7.2-24 with condition UNCIPHERED (the message is integrity protected using the key
stored in the USIM).
EPS update type 000 or 001 'TA updating' or
'combined TA/LA
updating'

identifier stored in the
USIM

context (for
KSI
ASME
)

Old GUTI or IMSI
Type of identity 110 GUTI
MNC/MCC Mobile Country Code and
Mobile Network Code
stored in EF
IMSI
on the
test USIM

MME Group ID LAI allocated at step 8
MME Code Bit 23 to bit 16 of P-TMSI
allocated at step 6

M-TMSI Value is specified bit by
bit below:
- bit 31 and bit 30: FFS
bit 24 of P-TMSI
allocated at step 6
- bit 23 to bit 16: RAC
allocated at step 6
bit 0 of P-TMSI allocated
at step 6

GPRS ciphering key sequence number GPRS ciphering key
sequence number
allocated at step 10A

Old P-TMSI signature P-TMSI signature
allocated at step 6

Additional GUTI GUTI-1
Nonce
UE
Any allowed value (must
be present)

UE network capability Any allowed value (must
be present)

Last visited registered TAI TAI stored in the test
USIM

UE radio capability information update needed 1 UE radio
capability
information
update needed

MS network capability Any allowed value (must
be present)

Old location area identification Not present if "EPS
update type" is 'TA
updating', LAI-1 is "EPS
update type" is
'combined TA/LA
updating'


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1505 Release 9
1505
9.2.3.3.5 Periodic routing area update
(1)
with { UE is camped on an E-UTRAN cell or in ECM-CONNECTED state and ISR is activated }
ensure that {
when { UE performs E-UTRA RRC state transitions }
then { UE keeps the periodic routing area update timer T3312 running }
}
(2)
with { UE is camped on an E-UTRAN cell or ECM-CONNECTED state and ISR is activated }
ensure that {
when { the periodic routing area update timer T3312 expires }
then { UE does not change RAT }
}
(3)
with { UE is in state GMM-REGISTERED.NO-CELL-AVAILABLE and ISR is activated and the periodic routing
area update timer T3312 expires }
ensure that {
when { UE enters the state GMM-REGISTERED.NORMAL-SERVICE }
then { UE initiates the routing area updating procedure }
}
TS 23.401, clause 4.3.5.2.
[TS 24.008, clause 4.7.2.2]
If ISR is activated, the MS shall keep both the periodic tracking area update timer (timer T3412) and the periodic
routeing area update timer (timer T3312). The two separate timers run in the MS for updating MME and SGSN
independently. If the periodic routeing area update timer expires and the MS is in state GMM-REGISTERED.NO-
CELL-AVAILABLE, the MS shall set its TIN to "RAT-related TMSI" and start the GERAN/UTRAN Deactivate ISR
timer T3323. The MS shall initiate the routeing area updating procedure and stop the timer T3323 when the MS enters
the state GMM-REGISTERED.NORMAL-SERVICE before timer T3323 expires. After expiry of timer T3323 the MS
shall deactivate ISR by setting its TIN to "GUTI" and initiate the routing area updating procedure when the UE enters
the state GMM-REGISTERED.NORMAL-SERVICE.
[TS 23.401, clause 4.3.5.2]
If the UE is camped on an E-UTRAN cell or is in ECM-CONNECTED state when the UE's periodic RAU or periodic
LAU timer expires and ISR is activated the UE shall start the GERAN/UTRAN Deactivate ISR timer. After the
GERAN/UTRAN Deactivate ISR timer expires the UE shall deactivate ISR by setting its TIN to "GUTI". The
GMM/PMM-REGISTERED UE shall remember it has to perform a Routeing Area Update to the SGSN or a Location
Area Update to the MSC when it next returns to 2G/3G coverage.
The E-UTRAN Deactivate ISR timer is stopped when the UE performs a successful TAU; and the GERAN/UTRAN
Deactivate ISR timer is stopped when the UE performs a successful RAU/LAU.
Expiry of the periodic TAU timer, or, the periodic RAU timer, or, the periodic LAU timer shall not cause the UE to
change RAT.

E-UTRAN RRC state transitions shall have no impact on the periodic RAU timer or periodic LAU timer except that
handover from 2G/3G to E-UTRAN shall cause the periodic RAU timer to be started from its initial value.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1506 Release 9
1506
System Simulator:
- cell A (belongs to TAI-1, home PLMN) is set to "Serving cell";
- if pc_UTRAN cell 5 (home PLMN, RAI-1, NMO 1) is set to "Non-suitable cell"; system information
- if (NOT pc_UTRAN AND pc_GERAN) cell 24 (home PLMN, RAI-1, NMO 1) is set to "Non-suitable cell";
system information combination 5 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1507 Release 9
1507
U - S Message
supported.
- - - -
1a1 IF pc_UTRAN THEN the SS sets the cell type
of Cell 5 to "Serving cell" and the cell type of
Cell A to "Non-suitable cell".
- - - -
1a2 The UE transmits a ROUTING AREA UPDATE
REQUEST
- -
1a3 The SS transmits a ROUTING AREA UPDATE
result value =100 (RA updated and ISR
activated).
ACCEPT
- -
COMPLETE
- -
1a5 The SS sets the cell type of Cell A to "Serving
cell".
- - - -
1b1 ELSE IF pc_GERAN THEN the SS sets the
cell type of Cell 24 to "Serving cell" and the cell
type of Cell A to "Non-suitable cell".
- - - -
REQUEST
- -
activated).
ACCEPT
- -
COMPLETE
- -
1b5 The SS sets the cell type of Cell A to "Serving
cell" and the cell type of Cell 24 to "Non-
suitable cell".
- - - -
- EXCEPTION: Steps 2 to 8 shall take place
within (T3312 3 min) of Step 1a3/1b3.
- - - -
2 The SS waits for [1] min. - - - -
3 The SS pages the UE on Cell A using S-TMSI
with .CN domain indicator set to PS.
<-- - - -
message on Cell A.
5 The SS transmits an ACTIVATE DEDICATED
message on Cell A activating a new EPS
bearer context.

This message is included in an
setup the new radio bearer associated with the
dedicated EPS bearer context activated by the
NAS message.
<-- ACTIVATE DEDICATED EPS
BEARER CONTEXT REQUEST
- -
6 The UE transmits an ACTIVATE DEDICATED
on Cell A.
--> ACTIVATE DEDICATED EPS
BEARER CONTEXT ACCEPT
- -
7 The SS transmits a DEACTIVATE EPS
BEARER CONTEXT REQUEST message on
Cell A deactivating the dedicated EPS bearer
context activated at Step 5.

<-- DEACTIVATE EPS BEARER
CONTEXT REQUEST
- -
8 The UE transmits a DEACTIVATE EPS --> DEACTIVATE EPS BEARER - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1508 Release 9
1508
BEARER CONTEXT ACCEPT message on
Cell A.
CONTEXT ACCEPT
supported.
- - - -
9a1 IF pc_UTRAN THEN the SS sets the cell type
- - - -
9a2 Check: Does the UE transmit a ROUTING
AREA UPDATE REQUEST on Cell 5, T3312
after Step 1a3?
REQUEST
1 P
9a3 The SS transmits a ROUTING AREA UPDATE
activated).
ACCEPT
- -
COMPLETE on Cell 5.
COMPLETE
- -
9a5 The SS sets the cell type of Cell A to "Serving
cell".
- - - -
9b1 ELSE IF pc_GERAN THEN the SS sets the
- - - -
9b2 Check: Does the UE transmit a ROUTING
AREA UPDATE REQUEST on Cell 24, T3312
after Step 1b3?
REQUEST
1 P
activated).
ACCEPT
- -
COMPLETE on Cell 24.
COMPLETE
- -
9b5 The SS sets the cell type of Cell A to "Serving
cell" and the cell type of Cell 24 to "Non-
suitable cell".
- - - -
10 The SS waits for [1] min. - - - -
11 The SS pages the UE on Cell A using S-TMSI
with CN domain indicator set to PS.
<-- - - -
message on Cell A.
message on Cell A activating a new EPS
bearer context.

setup the new radio bearer associated with the
dedicated EPS bearer context activated by the
NAS message.
- -
on Cell A.
- -
15 The SS waits until T3312 timer started at Step
9a3/9b3 has expired.
- - - -
indicate that a dedicated EPS bearer context is
active on cell A?
- - 2 -
BEARER CONTEXT REQUEST message on
Cell A deactivating the dedicated EPS bearer
context activated at Step 13.

CONTEXT REQUEST
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1509 Release 9
1509
18 The UE transmits a DEACTIVATE EPS
BEARER CONTEXT ACCEPT message on
Cell A.
--> DEACTIVATE EPS BEARER
CONTEXT ACCEPT
- -
19 The SS waits for 2 min. - - - -
indicate that the UE is in state Registered, Idle
Mode on Cell A?
- - 2 -
supported.
- - - -
21a
1
IF pc_UTRAN THEN the SS sets the cell type
- - - -
21a
2
AREA UPDATE REQUEST message on Cell 5
within [30] sec?
REQUEST
3 P
21a
3
activated).
ACCEPT
- -
21a
4
The UE transmits a ROUTING AREA UPDATE
COMPLETE
- -
21b
1
ELSE IF pc_GERAN THEN the SS sets the
- - - -
21b
2
24 within [30] sec?
REQUEST
3 P
21b
3
activated).
ACCEPT
- -
21b
4
The UE transmits a ROUTING AREA UPDATE
COMPLETE
- -

Table 9.2.3.3.5.3.3-1: Message ROUTING AREA UPDATE REQUEST (steps 1a2/1b2, Table 9.2.3.3.5.3.2-
1)
P-TMSI P-TMSI mapped from
GUTI assigned to UE
during preamble
pc_UTRAN
MS network capability
ISR support 1

Table 9.2.3.3.5.3.3-2: Message ROUTING AREA UPDATE REQUEST (steps 9a2/9b2 and 21a2/21b2,
Table 9.2.3.3.5.3.2-1)
Update type 011 Periodic
updating

P-TMSI P-TMSI mapped from
GUTI assigned to UE
during preamble
pc_UTRAN
MS network capability
ISR support 1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1510 Release 9
1510
Table 9.2.3.3.5.3.3-3: Message ROUTING AREA UPDATE ACCEPT (steps 1a3/1b3, 9a3/9b3 and
21a3/21b3, Table 9.2.3.3.5.3.2-1)
ISR activated

Periodic RA update timer 00100111 7 min

9.2.3.3.5a Periodic Location Update
(1)
with { UE in EMM-REGISTERED.NORMAL-SERVICE and camped on E-UTRAN with periodic location update timer
T3212 running, and ISR deactivated }
ensure that {
when { UE camps on a GERAN/UTRAN cell within the same LA where UE last successfully registered }
then { the UE does not initiate a periodic location update procedure until the expiry of T3212 }
}

(2)
with { UE in MM IDLE substate NORMAL SERVICE with periodic location update timer T3212 running, and
ISR deactivated}
ensure that {
when { UE camps on a E-UTRAN cell and successfully performs a Tracking Area Update and T3212
expires}
then { the UE does not perform a periodic location update whilst in E-UTRAN coverage and does
not change RAT because T3212 has expired}
}

(3)
with { UE in EMM-REGISTERED.NORMAL-SERVICE and camped on E-UTRAN and the periodic location update
timer T3212 expired, and ISR deactivated }
ensure that {
when { UE camps on a GERAN/UTRAN cell within the same LA where UE last successfully registered }
then { the UE performs a periodic location update procedure }
}

References: The conformance requirements covered in the current TC are specified in: TS 23.401 clauses 4.3.5.2; and
TS 24.008 clauses 4.7.1.4.1 and 4.7.5.1.1.
[TS 23.401, clause 4.3.5.2 "Reachability Management for UE in ECM-IDLE state"]

If the UE is EPS attached only and either camps on an E UTRAN cell or is in ECM CONNECTED state when the UE's
periodic LAU timer expires, the UE shall perform a Location Area Update procedure in NMO II/III or combined
RA/LA update in NMO I when it next returns to GERAN/UTRAN coverage.

Expiry of the periodic TAU timer, or, the periodic RAU timer, or, the periodic LAU timer shall not cause the UE to
change RAT.

E-UTRAN RRC state transitions shall have no impact on the periodic RAU timer or periodic LAU timer except that
handover from GERAN/UTRAN to E-UTRAN shall cause the periodic RAU timer to be started from its initial value.
[TS 24.008, 4.2.2.1 "Service State, NORMAL SERVICE"]
When in state MM IDLE and service state NORMAL SERVICE, the mobile station shall:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1511 Release 9
1511
- perform normal location updating when a new location area is entered;
- perform location updating procedure at expiry of timer T3211 or T3213;
- perform periodic updating at expiration of timer T3212;
- perform IMSI detach;
- support requests from the CM layer;
- respond to paging; and
- for an eCall only mobile station (as determined by information configured in USIM), perform the eCall inactivity
procedure at expiry of timer T3242 or timer T3243.
[TS 24.008, 4.4.1 "Location updating procedure"]

Upon successful location updating the mobile station sets the update status to UPDATED in the SIM/USIM, and stores
the Location Area Identification received in the LOCATION UPDATING ACCEPT message in the SIM/USIM. The
attempt counter shall be reset.
[TS 24.008, 4.4.2 "Periodic updating"]

The procedure is controlled by the timer T3212 in the mobile station. If the timer is not already started, the timer is
started each time the mobile station enters the MM IDLE substate NORMAL SERVICE or ATTEMPTing TO
UPDATE. When the MS leaves the MM Idle State the timer T3212 shall continue running until explicitly stopped.

When the timer T3212 expires, the location updating procedure is started and the timer shall be set to its initial value for
the next start. If the mobile station is in other state than MM Idle when the timer expires the location updating
procedure is delayed until the MM Idle State is entered.

If the mobile station is in service state NO CELL AVAILABLE, LIMITED SERVICE, PLMN SEARCH or PLMN
SEARCH-NORMAL SERVICE when the timer expires the location updating procedure is delayed until this service
state is left.
System Simulator:
- cell A is configured as Non-suitable off cell;
- cell 24 is configured as Serving cell, operating in network operation mode II and does not support Dual Transfer
Mode (DTM_SUPPORT is configured as default (see TS 51.010-1 clause 40.2.1.1 [23]. The value of T3212
(Octet 4 of the Control Channel Description IE) is 0110 (6 minutes);
- cell 24 does not transmit any "absolute priorities";
- cell A has the absolute priorities set to LTE.
UE:
- the UE is previously registered on GERAN, and when on GERAN, the UE is last registered on cell 24 using
default message contents according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1512 Release 9
1512
- the UE is configured such that "EPS only TAU accept" does not cause RAT reselection to GSM.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1513 Release 9
1513
U S Message
1 The UE is switched on and camps on GERAN
cell 24.

The Periodic LU timer T3212 is configured to 6
minutes. (see NOTE 1)

(* mobile is mandated to start the LU update
before starting the GPRS attach *)
- - - -
2 The UE transmits a LOCATION UPDATING
REQUEST with location updating type set to
"Attach.
REQUEST
- -
ACCEPT, and the UE stores the received LAI
and sets the update status to UPDATED on
the USIM.
4 The SS releases the RR Connection -
message on Cell 24 indicating "GPRS attach.
message indicating "combined GPRS attach.
The UE sets the update status to UPDATED
on the USIM. The SS allocates a P-TMSI.
7 The UE transmits an ATTACH COMPLETE to
acknowledge the P-TMSI allocation.
--> ATTACH COMPLETE
8 The UE requests the activation of a default
PDP context
--> ACTIVATE PDP CONTEXT
REQUEST

9 The SS accepts the request for default PDP
contect request and return an ACTIVATE PDP
CONTEXT ACCEPT
<-- ACTIVATE PDP CONTEXT
ACCEPT

10 The signal strength of Cell A is raised to that of
the Serving Cell and Cell 24 is lowered to that
of a Suitable Neighbour Cell as defined in table
6.2.2.1-1 of TS 36.508 [18].

Note: Cell 24 is still suitable but the UE shall
select Cell A
- - -
11 The UE camps on E-UTRAN cell A and
transmits a TRACKING AREA UPDATE
REQUEST message.
REQUEST
- -
authentication.
ACCEPT message including a valid TAI list
containing the TAI of Cell A; with PLMN ID of
Cell A included in the GUTI. The UE sets the
TIN =GUTI.

Note: This is an EPS-only Accept message
(update type =TA updated)
ACCEPT
- -
COMPLETE
- -
18 The SS releases the RRC Connection - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1514 Release 9
1514
19 The signal strength of Cell 24 is raised to that
of the Serving Cell and Cell A is lowered to
that of a Non-Suitable Neighbour Cell as
- - - -
20 The UE camps on cell 24. - - -
21 Check: Does the UE transmit a LOCATION
UPDATING REQUEST? Continue checking
until 4 mins after step 4.

Note: This step is run in parallel with steps 22
and 23.
- - 1 F
REQUEST with Update type set to "RA
updating.
REQUEST
- -
updated.
ACCEPT
- -
the Serving Cell and Cell 24 is lowered to that
of a Suitable Neighbour Cell as defined in table
6.2.2.1-1 of TS 36.508 [18].

Note: Cell 24 is still suitable but the UE shall
select Cell A
- - -
25 The UE camps on cell A. - - -
UPDATE REQUEST message with EPS
update set to "TA updating.
REQUEST
- -
UPDATE ACCEPT.
ACCEPT
- -
28 UE camps on cell A - - - -
29 Check: Does UE transmit a LOCATION
UPDATING REQUEST (on cell 24) and
changes RAT. Chech this until 7 minutes after
step 4 (RR release after LU)
- - 2 F
of the Serving Cell and Cell A is lowered to
that of a non-Suitable Neighbour Cell as
- - - -
32 Check: Does the UE transmits a LOCATION
UPDATING REQUEST with location updating
type set to "Periodic updating.
REQUEST
3 P
ACCEPT.
34 The SS releases the RR Connection - (* we may need to permit the RA
update to happen before the LA
update "exception*)
- -
REQUEST with Update type set to "RA
updating.
REQUEST
- -
updated.
ACCEPT
- -

NOTE 1: Default message settings for GSM procedures and system information messages see TS 51.010-1 clause
26.7 [23]. The value of T3212 (Octet 4 of the Control Channel Description IE) is 0110.
None

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1515 Release 9
1515
9.2.3.3.6 E-UTRAN RRC connection failure / Reselection of UTRAN cell / NAS signaling to
release old S1 interface connection
(1)
with { UE is E-UTRA RRC_CONNECTED state and ISR not activated }
ensure that {
when { Radio link failure is detected and UE attempts to select a suitable E-UTRA cell to re-
establish the RRC connection }
then { UE can not find a suitable cell for T311 and leaves RRC_CONNECTED state with release
cause RRC connection failure }
(2)
with { UE searches for a suitable cell after an indication of E-UTRAN RRC connection failure}
ensure that {
when { UE detects an UTRA cell and returns to coverage }
then { UE performs a routing area update }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.008, clause 4.7.5,
TS36.331 clauses 5.3.7.2, 5.3.11.1, 5.3.11.3 and 5.3.12 and TS36.304 clauses 5.2.7.
[TS24.008 clause 4.7.5]
This procedure is used for:

- in Iu mode and A/Gb mode after intersystem change from S1 mode, and the GMM receives an indication of
"RRC connection failure" from lower layers due to lower layer failure while in S1 mode;

[TS 36.331 clause 5.3.7.2]
...
1>start timer T311;
1>reset MAC;
[TS 36.304 clause 5.3.11.1]
The UE shall:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1516 Release 9
1516
2>start timer T310;
[TS 36.304 clause 5.3.11.3]
The UE shall:
2>else:
[TS36.331 clause 5.3.12]
1>reset MAC;
leaving RRC_CONNECTED, as specified in TS 36.304 [4];
[TS 36.304 clause 5.2.7]
If no suitable cell is found, the UE shall perform a cell selection starting with Stored Information Cell Selection
procedure in order to find a suitable cell to camp on.
When returning to idle mode after UE moved to RRC_CONNECTED state from camped on any cell state, UE shall
attempt to camp on the last cell for which it was in RRC_CONNECTED state or any cell on a frequency or frequency
of RAT assigned by RRC in the state transition message. If no acceptable cell is found, the UE shall continue to search
for an acceptable cell of any PLMN in state any cell selection.
System Simulator:
- cell A (belongs to TAI-1) is set to "Serving cell";
- cell 5 (belongs to RAI-1) is set to ''Non-suitable cell'';
- system information indicates that NMO 1 is used.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1517 Release 9
1517
UE:
none.
Preamble:
U - S Message
1 The SS drops Cell A level for UE to detect
physical layer recovery and waits for 1s (i.e.
T310 transmitted in SIB2.)
- - - -
2 The SS raises Cell 5 level as Serving cell,
switches Cell A off and waits for 10s (i.e. T311
transmitted in SIB2)
- - - -
9.2.3.3.6.3.2-2 is taking place
- - - -
messages within the next 60s?
Request
1 F
UE is in end state UTRA connected (U2)
according to TS 36.508 but attached for EPS
services only.
- - - -

U - S Message
updating procedure on Cell 5?

Note: No message contents other than
message type needs checking.
REQUEST
2 P
2 The SS completes the routing area update
procedure according to generic procedure tbd
in TS 36.508.
- - - -

None
9.2.3.4
9.2.3.4.1 TAU/RAU procedure for inter-system cell reselection between A/Gb and S1
modes
(1)
with { UE attached to GERAN with a PDP context active, and, E-UTRAN NAS and Security parameters
inclding a valid GUTI stored on the USIM }
ensure that {
when { UE performs a cell reselection to E-UTRAN and performs a Tracking Area Update }
then { the UE encodes the RRC parameters in the RRC Connection Establishment messages correctly
(i.e. in the RRCConnectionRequest message, the InitialUE-Identity is set to randomValue and the
establishmentcause is set to MO-signalling; and, in the RRCConnectionSetupComplete message the
selectedPLMN-identity, mmegi and mmec indicate the value of the registered MME (e.g. as retrieved
from the USIM at power-on, or, as received in the last TRACKING AREA UPDATE ACCEPT message) }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1518 Release 9
1518

(2)
with { UE attached to GERAN with a PDP context active, and, E-UTRAN NAS and EPS Security parameters
including a valid GUTI stored on the USIM, and ISR not activated }
ensure that {
when { UE performs a cell reselection to E-UTRAN and performs a Tracking Area Update }
then { the UE encodes the parameters in the TRACKING AREA UPDATE REQUEST correctly i.e.:
- the NAS key set identifier
ASME
IE is set to the value stored in the USIM/allocated in
the last TRACKING AREA UPDATE ACCEPT message;
- the Old GUTI IE is derived from the mapped P-TMSI and RAI;
- the Additional GUTI IE is set to the GUTI stored in the USIM/allocated in the last
TRACKING AREA UPDATE ACCEPT message;
- the GPRS cipherign key sequence number IE is set to the value allocated in the
AUTHENTICATION AND CIPHERING REQUEST message; and
- the NONCEue IE is included;
- the DRX parameter IE is not included. }
}

(3)
with { UE powered on in GERAN }
ensure that {
when { UE makes its first Tracking Area Update to E-UTRAN}
then { UE sends the UE radio capability information update needed IE }
}

(4)
with { UE registered in E-UTRAN, and, GERAN NAS and Security parameters including a valid P-TMSI
available in the UE and ISR not activated }
ensure that {
when { UE performs a cell reselection to GERAN and performs a Routeing Area Update }
then { the UE derives the TLLI parameter in the RLC/MAC header from the GUTI allocated in the
TRACKING AREA UPDATE ACCEPT message }
}
(5)
with { UE registered in E-UTRAN, and, GERAN NAS and GERAN Security parameters including a valid P-
TMSI available in the UE, and ISR not activated }
ensure that {
when { UE performs a cell reselection to GERAN and performs a Routeing Area Update }
then { the UE encodes the parameters in the ROUTING AREA UPDATE REQUEST correctly i.e.:
- [the GPRS ciphering key sequence number IE is set to the value mapped from
KSI-ASME;;] - the Old routing area identification IE, and the Old P-
TMSI signature IE are
mapped from the GUTI allocated in the TRACKING AREA UPDATE ACCEPT message;
- the Additional mobile identity IE contains the P-TMSI allocated in the last received
ATTACH ACCEPT/ROUTING AREA UPDATE ACCEPT message;
- the Additional old routing area identification IE contains the RAI allocated in the
last received ATTACH ACCEPT/ROUTING AREA UPDATE ACCEPT message; and
- [the DRX parameter IE is not included]. }
}

(6)
with { UE registered }
ensure that {
when { UE makes its second Tracking Area Update to E-UTRAN}
then { UE does not send the UE radio capability information update needed IE }
}

References: The conformance requirements covered in the current TC are specified in: TS 23.003 clauses 2.8.2.1 and
2.8.2.2; TS 23.401 clauses 4.3.5.6, 5.3.3.1 and 5.3.3.3; TS 24.008 clauses 4.7.1.4.1 and 4.7.5.1.1; and TS 24.301 clauses
5.3.1.1 and 5.5.3.2.2.
[TS 23.003, clause 2.8.2.1 Mapping from GUTI to RAI, P-TMSI and P-TMSI signature]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1519 Release 9
1519
E-UTRAN <MME Code>maps to GERAN/UTRAN <RAC>and is also copied into the 8 most significant bits of
the NRI field within the P-TMSI;
signature>field.
[TS 23.003, clause 2.8.2.2 Mapping from RAI and P-TMSI to GUTI]
GERAN/UTRAN <MCC>maps to E-UTRAN <MCC>
GERAN/UTRAN <LAC>maps to E-UTRAN <MME Group ID>
GERAN/UTRAN <RAC>maps into bit 23 and down to bit 16 of the M-TMSI

[TS 23.401, clause 4.3.5.6, Idle mode signalling reduction function]
The TIN can take one of the three values, "P-TMSI", "GUTI" or "RAT-related TMSI". The UE shall set the TIN when
receiving an Attach Accept, a TAU Accept or RAU Accept message according to the rules in table 4.3.5.6-1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1520 Release 9
1520
Table 4.3.5.6-1: Setting of the TIN
Message received by UE Current TIN value stored by
UE
TIN value to be set by the
UE when receiving
message
Attach Accept via E-UTRAN
(never indicates ISR activation)
Any value GUTI
Attach Accept via
GERAN/UTRAN
(never indicates ISR activation)
Any value P-TMSI
TAU Accept not indicating ISR Any value GUTI
TAU Accept indicating ISR GUTI
P-TMSI or RAT-related TMSI
GUTI
RAT-related TMSI
RAU Accept not indicating ISR Any value P-TMSI
RAU Accept indicating ISR P-TMSI
GUTI or RAT-related TMSI
P-TMSI
RAT-related TMSI

[TS 23.401, clause 5.3.3.1, step 2, Tracking Area Update procedure with Serving GW change]
.
If the UE's TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are
indicated as the old GUTI.

[TS 23.401, clause 5.3.3.3, step 2, Routeing Area Update with MME interaction and without S-GW change]

If the UE's internal TIN indicates "GUTI" and the UE holds a valid GUTI then the UE indicates the GUTI as the old
P-TMSI and old RAI

[TS 24.008, clause 4.7.1.4.1, Radio resource sublayer address handling (A/Gb mode only)]
For an MS supporting S1 mode, the following five cases can be distinguished:
a) the TIN indicates "P-TMSI" or "RAT-related TMSI" and the MS holds a valid P-TMSI and a RAI;
b) the TIN indicates "GUTI" and the MS holds a valid GUTI;
c) the TIN is deleted and the UE holds a valid P-TMSI and RAI;
d) the TIN is deleted and the UE holds a valid GUTI, but no valid P-TMSI and RAI; or
e) none of the previous cases is fulfilled.
In case a) the MS shall derive a foreign TLLI from the P-TMSI and proceed as specified for case i) above.
In case b), the MS shall derive a P-TMSI from the GUTI and then a foreign TLLI from this P-TMSI and proceed as
specified for case i) above.

[TS 24.008, clause 4.7.5.1.1, Normal and periodic routing area updating procedure initiation]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1521 Release 9
1521
identification IE.
If the routing area updating procedure is not initiated by the MS due to an S1 mode to Iu mode or S1 mode to A/Gb
mode intersystem change, the message ROUTING AREA UPDATE REQUEST shall contain the P-TMSI signature
when received within a previous ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message.
inter-system change in idle mode and the MS does not have a valid current UMTS security context, the message
ROUTING AREA UPDATE REQUEST shall include a P-TMSI signature filled with a NAS token as specified in
3GPP TS 33.401 [119]. If the MS has a valid current UMTS security context, the MS shall indicate it in the GPRS
ciphering key sequence number IE.
NOTE: If the TIN indicates "GUTI", 8 bits of the NAS token will be filled with bits from the M-TMSI (see
3GPP TS 23.003 [4]).
inter-system change in connected mode or in idle mode if the MS does not have a valid current security context, the MS
shall derive CK' and IK' from the K
ASME
and the NAS downlink COUNT value corresponding to the NAS token derived
as specified in 3GPP TS 33.401 [119]. The MS shall indicate the eKSI value in the CKSN field of the GPRS ciphering
key sequence number IE in the ROUTING AREA UPDATE REQUEST message. Then, the MS shall reset the START
value and store the mapped UMTS security context replacing the current UMTS security context.

In order to indicate the new DRX parameter while in GERAN or UTRAN coverage, the MS shall send the ROUTING
AREA UPDATE REQUEST message containing the DRX parameter in the DRX parameter IE to the network, with the
exception of the case if the MS had indicated its UE specific DRX parameter (3GPP TS 24.301 [120]) to the network
while in E-UTRAN coverage. In this case, when the MS enters GERAN or UTRAN coverage and initiates a routing
area updating procedure, the MS shall not include the DRX parameter in the DRX parameter IE in the ROUTING
AREA UPDATE REQUEST message.
[TS 24.301, clause 5.3.1.1 Establishment of the NAS signalling connection]
For the routing of the initial NAS message to the appropriate MME, the UE NAS provides the lower layers with either
the S-TMSI or the registered globally unique MME identifier (GUMMEI) that consists of the PLMN ID, the MME
group ID, and the MME code (see 3GPP TS 23.003 [2]).
- When the UE is registered in the tracking area of the current cell during the NAS signalling connection
establishment, the UE NAS shall provide the lower layers with the S-TMSI, but shall not provide the registered
MME identifier to the lower layers. Exceptionally, when the UE in EMM-IDLE mode initiates a tracking area
updating procedure for load balancing purposes, the UE NAS shall provide the lower layers with neither S-TMSI
nor registered MME identifier.
- When the UE is not registered in the tracking area of the current cell during the NAS signalling connection
establishment, the UE NAS does not provide the lower layers with the S-TMSI. If the UE has a valid registered
MME identifier from a previous registration, the UE NAS shall provide the lower layers with the registered
MME identifier.
[TS 24.301, clause 5.5.3.2.2 Normal and periodic tracking area updating procedure initiation]

In order to indicate its UE specific DRX parameter while in E-UTRAN coverage, the UE shall send the TRACKING
AREA UPDATE REQUEST message containing the UE specific DRX parameter in the DRX parameter IE to the
network, with the exception of the case if the UE had indicated its DRX parameter (3GPP TS 24.008 [13]) to the
network while in GERAN or UTRAN coverage. In this case, when the UE enters E-UTRAN coverage and initiates a
tracking area updating procedure, the UE shall not include the UE specific DRX parameter in the DRX parameter IE in
the TRACKING AREA UPDATE REQUEST message.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1522 Release 9
1522

When initiating a tracking area updating procedure as a result of an Iu mode to S1 mode or A/Gb mode to S1 mode
inter-system change, the UE shall handle the GUTI as follows:
RAI into the old GUTI IE. Additionally, if the UE holds a valid GUTI, the UE shall indicate the GUTI in the
Additional GUTI IE.
NOTE: Mapping the P-TMSI and RAI to the GUTI is specified in Annex H of 3GPP TS 23.401 [10].

When the tracking area updating procedure is initiated to perform an inter-system change from A/Gb mode or Iu mode
to S1 mode, the UE shall include the KSI
ASME
in the TRACKING AREA UPDATE REQUEST message if the UE has a
cached EPS security context. Otherwise, the UE shall set the KSI
ASME
to the value "no key is available".
A/Gb mode or Iu mode to S1 mode, the UE shall include the KSI
SGSN
message. If the UE does not have a cached EPS security context, the UE shall include the Nonce
UE
IE in the
TRACKING AREA UPDATE REQUEST message. The TRACKING AREA UPDATE REQUEST message shall be
integrity protected with the cached EPS security context if the UE has one. If the UE does not have a cached EPS
security context, the TRACKING AREA UPDATE REQUEST message shall not be integrity protected.

A/Gb mode or Iu mode to S1 mode, the UE shall include the KSI
SGSN
message. If the UE does not have a cached EPS security context, the UE shall include the Nonce
UE
IE in the
TRACKING AREA UPDATE REQUEST message. The TRACKING AREA UPDATE REQUEST message shall be
integrity protected with the cached EPS security context if the UE has one. If the UE does not have a cached EPS
security context, the TRACKING AREA UPDATE REQUEST message shall not be integrity protected.


[TS 24.301, clause 4.4.2 Handling of EPS security contexts]

The key set identifier eKSI is assigned by the MME either during the authentication procedure or, for the mapped
security context, during the handover procedure. The eKSI consists of a value and a type of security context parameter
indicating whether an EPS security context is a native EPS security context or a mapped EPS security context. When
the EPS security context is a native EPS security context, the eKSI has the value of KSI
ASME
, and when the current EPS
security context is a mapped EPS security context, the eKSI has the value of KSI
SGSN
.

System Simulator:
NOTE: while this test describes the uses of 3 cells, it is intended that this test only requires 2 cells to be active at
any one instant.
- cell A (E-UTRAN), cell 24 and cell 26 (GERAN)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1523 Release 9
1523
- with the exception of the MCC and MNC, cell 24 and cell 26 take the default parameters of the GERAN cells as
defined in clause 6.3.1 of TS 36.508 [18], cells 24 and 26 are configured with the same MCC and MNC as cell A.
Cells 24 and 26 are in the same routing area;
- as defined in clause 40.1 of TS 51.010 [23], the GERAN cells are configured to use Network Mode of Operation
I;
- the power level of Cell 24 is the Serving Cell level defined in table 6.2.2.1-1 of TS 36.508 [18];
- the power levels of Cells A and 26 are set to the Non-suitable Off level defined in table 6.2.2.1-1 of TS 36.508
[18].
UE:
- the UE was previously registered on E-UTRAN, and when on E-UTRAN, the UE was last authenticated and
registered on a cell (no name assigned) frequency 2 belonging to a PLMN with (MCC, MNC) =(65, 987) and
allocated a GUTI with (MMEGI, MMEC) =(0xfedc, 0xba) and an arbitrary M-TMSI value..
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1524 Release 9
1524
U S Message
message on Cell 24
REQUEST message.
RESPONSE message.
COMMAND message
COMPLETE message ciphered with the new
EPS security context identified by the KSI
ASME

received in the SECURITY MODE COMMAND
message in step 5
including valid TMSI, P-TMSI (TIN set to P-
TMSI) and RAI.

Editors Note: the default message contents in
51.010 clause 40.2.4.3 allocate a Negotiated
READY timer value of 32 seconds.
message.
- ATTACH COMPLETE - -
10 Void - - - -
11 Void - - - -
12 Void - - - -
the Serving Cell and that of Cell 24 is lowered
in table 6.2.2.1-1 of TS 36.508 [18].

Note: Cell 24 is still suitable but the UE is
expected to select Cell A.
- - - -
14 Void - - - -
15 Check: does the UE send an
Identity set to randomValue and the
establishmentcause set to MO-signalling on
Cell A?

Editors Note: Cell reselection to E-UTRAN
might not occur until the GPRS READY timer
has expired. Hence this step might occur up to
40 seconds after step 13.
--> RRCConnectionRequest 1 -
16 The SS responds with RRCConnectionSetup <-- RRCConnectionSetup
17 Check: does the UE send an
RRCConnectionSetupComplete with the
selectedPLMN-identity set to the value of the
registered MME (i.e. to the value in the GUTI
stored on the USIM in EF
EPSLOCI
), and, the
mmegi and mmec are set to the values derived
from the GUTI stored on the USIM in
EF
EPSLOCI
;

Check: are the contents of the TRACKING
AREA UPDATE REQUEST with the correct
parameters?
--> RRCConnectionSetupComplete(R
RC parameters, TRACKING
AREA UPDATE REQUEST)
1,

2, 3
P
ACCEPT

Note: the default message contents cause the
ACCEPT
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1525 Release 9
1525
allocation of a new GUTI and new TAI list
COMPLETE
COMPLETE
- -
20 the SS releases the RRC connection - - - -
21 Cell 24 is switched off - - - -
of the Serving Cell and that of Cell A is
lowered to that of a Suitable Neighbour Cell as

Note: Cell A is still suitable but the UE is
expected to select Cell 26.
- - - -
23 Check: does the UE send on Cell 26 an
RLC/MAC header with the TLLI derived from
the P-TMSI that is derived from the GUTI
- - 4 P
24 Check: does the UE send on Cell 26 a
ROUTING AREA UPDATE REQUEST with the
correct parameters?
REQUEST
5 P
25 The SS sends ROUTING AREA UPDATE
ACCEPT (without the allocated P-TMSI IE, but
with the Requested MS Information IE
indicating E-UTRAN inter RAT information
container IE requested).
ACCEPT
- -
26 UE sends ROUTING AREA UPDATE
COMPLETE message
COMPLETE
- -
the Serving Cell and that of Cell 26 is lowered
in table 6.2.2.1-1 of TS 36.508 [18].

Note: Cell 26 is still suitable but the UE is
expected to select Cell A.
- - - -
28 Check: does the UE send on Cell A an
RRCConnectionSetupComplete with the
selectedPLMN-identity indicating the
registered MME (i.e. the PLMN in the GUTI
allocated in step 18 ), and, the mmegi and
mmec are set to the values in the GUTI

Check: does the UE send a TRACKING AREA
UPDATE REQUEST with the correct
parameters?
--> RRCConnectionSetupComplete(R
RC parameters, TRACKING
AREA UPDATE REQUEST)
1,

2, 6
P
ACCEPT

Note: the default message contents cause the
allocation of a new GUTI.
ACCEPT
- -
COMPLETE
COMPLETE
- -

InitialUE-Identity CHOICE {
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1526 Release 9
1526
TransactionIdentifier-UL

c1 CHOICE {
selectedPLMN-Identity Indicates the PLMN of
cell 24.

registeredMME SEQUENCE {
plmn-Identity

987-65 From GUTIx,
stored on the
USIM in
EF
EPSLOCI
.

Mmegi 1111 1110 1101 1100 B fedc hex, from
GUTIx stored on
the USIM in
EF
EPSLOCI
.

Mmec 1011 1010 B ba hex, from
GUTIx stored on
the USIM in
EF
EPSLOCI

}
nas-DedicatedInformation Not checked at RRC
layer

}
}
}
}


ASME

identifier KSI
ASME
of the
UE
As stored on the
USIM in EF
EPSNSC

context

8

Additional GUTI GUTI1 Set to the value
stored in the
USIM in EF
EPSLOCI

DRX parameter Not present
UE radio capability information update needed 1B UE radio
capability
information
update needed

GPRS ciphering key sequence number Value mapped from the
AUTHENTICATION AND
CIPHERING REQUEST
message

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1527 Release 9
1527
Protocol discriminator GMM
Skip indicator 0000
Routing area update request message identity 0000 1000 B
GPRS ciphering key sequence number set to the value to KSI-
ASME
With ISR inactive
and TIN indicates
GUTI, then eKSI
value is set to
KSI-ASME

Old routing area identification Mapped from the GUTI
received in step 18.

Old P-TMSI signature Mapped from the GUTI
received in step 18.

Requested READY timer value If present, any allowed
value.

DRX parameter Not present Shall be absent
TMSI status If present, any allowed
value.

P-TMSI Not present
MS network capability Any allowed value.
PDP context status If present, any allowed
value.

PS LCS Capability If present, any allowed
value.

MBMS context status If present, any allowed
value.

UE network capability Any allowed value.
Additional mobile identity Set to the P-TMSI
allocated in step 8

Additional old routing area identification Set to the RAI allocated
in step 8

Mobile station classmark 2 If present, any allowed
value.

Mobile station classmark 3 If present, any allowed
value.

Supported Codecs If present, any allowed
value.

Table 9.2.3.4.1.3.3-5: Message ROUTING AREA UPDATE ACCEPT (step 25, Table 9.2.3.4.1.3.2-1)

allocated P-TMSI Absent
Requested MS Information 0100 B E-UTRAN inter
RAT information
container IE
requested

Table 9.2.3.4.1.3.3-6: Message ROUTING AREA UPDATE COMPLETE (step 26, Table 9.2.3.4.1.3.2-1)
E-UTRAN inter RAT handover information Any allowed value

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1528 Release 9
1528
Rrc-TransactionIdentifier RRC-

C1 CHOICE {
selectedPLMN-Identity Indicates the PLMN of
cell 24.

registeredMME SEQUENCE {
plmn-Identity

Not present Shall be absent
because the
registered MME is
the same as the
selected PLMN.

Mmegi The MMEGI part of the
GUTI in the TRACKING
AREA UPDATE ACCEPT
message sent in step 18

Mmec The MMEC part of the
GUTI in the TRACKING
AREA UPDATE ACCEPT
message sent in step 18

}
nas-DedicatedInformation Not checked at RRC
layer

}
}
}
}


ASME

identifier KSI
ASME
of the
UE
As stored on the
USIM in EF
EPSNSC

in the pre-test
conditions

context

8

Additional GUTI GUTI1 Set to the value
allocated in step
18

DRX parameter Not present
UE radio capability information update needed Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1529 Release 9
1529
9.3 EMM connection management procedures (S1 mode only)
9.3.1 Service request procedure
9.3.1.1 Service request initiated by UE for user data
(1)
with { UE in EMM-REGISTERED state and EMM-IDLE mode }
ensure that {
then { UE establishes the RRC connection with the RRC establishmentCause set to mo-Data and
sends a SERVICE REQUEST message }
}
The conformance requirements covered in the current TC are specified in: TS 24.301 clauses 5.3.1.1, 5.1.3.2.2.4,
5.3.1.1, 5.6.1.1, 5.6.1.2, 5.6.1.4 and Annex D and TS 36.331 clause 5.3.3.3.
[TS 24.301 clause 5.3.1.1]
[TS 24.301 clause 5.1.3.2.2.4]
In the state EMM-REGISTERED an EMM context has been established and a default EPS bearer context has been
activated in the UE.

The UE may initiate sending and receiving user data and signalling information and reply to paging. Additionally,
tracking area updating procedure is performed (see subclause 5.5.3).
[TS 24.301 clause 5.3.1.1]
In S1 mode, when the RRC connection has been established successfully, the UE shall enter EMM-CONNECTED
mode and consider the NAS signalling connection established.
[TS 24.301 clause 5.6.1.1]
The purpose of the service request procedure is to transfer the EMM mode from EMM-IDLE to EMM-CONNECTED
mode and establish the radio and S1 bearers when uplink user data or signalling is to be sent.
...
The UE shall invoke the service request procedure when:
....
b) the UE, in EMM-IDLE mode, has pending user data to be sent;
[TS 24.301 clause 5.6.1.2]
If the UE has pending uplink data or uplink signalling in EMM-IDLE mode to be transmitted or it responds to paging
with CN domain indicator set to "PS", the UE initiates the service request procedure by sending a SERVICE REQUEST
message to the MME, starts the timer T3417, and enters the state EMM-SERVICE-REQUEST-INITIATED.
[TS 24.301 clause 5.6.1.4]
For cases a, b and c in subclause 5.6.1.1, the UE shall treat the indication from the lower layers that the user plane radio
bearer is set up as successful completion of the procedure.
....

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1530 Release 9
1530
Upon successful completion of the procedure, the UE shall stop the timer T3417 and enter the state EMM-
REGISTERED.
...
...
Service Request If a SERVICE REQUEST is to request user plane radio
resources, the RRC establishment cause shall be set to MO
data. (See Note1)

"originating calls"

If a SERVICE REQUEST is to request resources for UL
signalling, the RRC establishment cause shall be set to MO
data. (See Note 1)

"originating calls"


[TS 36.331, clause 5.3.3.3]
...
2>else
System Simulator:
- cell A.
UE:
none.
Preamble:
- the UE is in state Loopback Activated (State 4) according to TS 36.508 [18] using the specific message content
for ACTIVATE TEST MODE and CLOSE UE TEST LOOP messages in table 9.3.1.1.3.3-1 and table
9.3.1.1.3.3-2.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1531 Release 9
1531
U - S Message
1 The SS transmits one IP Packet to the UE. <-- IP packet - -
2 The SS waits 1 second after the IP packet has
been transmitted in step 1 and then transmits
an RRCConnectionRelease message. (Note 2)
- - - -
establishmentCause set to mo-Data followed
by a SERVICE REQUEST message? (Note 1)
- - - -
Note 1: Triggered when timer T_delay_modeB (IP PDU delay time) expires and pending uplink data exist in
buffered PDCP SDUs according to [25] clause 5.4.4.3.
by the SS in step 1 to the UE test loop function before the RRCConnectionRelease message is sent by the
SS in step 2.

Table 9.3.1.1.3.3-1: ACTIVATE TEST MODE (preamble)

Table 9.3.1.1.3.3-2: CLOSE UE TEST LOOP (preamble)
IP PDU delay 0 0 0 0 0 1 0 1 5 seconds

Table 9.3.1.1.3.3-3: Message RRCConnectionRequest (step 3, Table 9.3.1.1.3.2-1)
}
}
}

9.3.1.2 Void
9.3.1.3 Service request / Mobile originating CS fallback
(1)
ensure that {
when { UE initiates mobile originating CS fallback }
then { UE sends EXTENDED SERVICE REQUEST message }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1532 Release 9
1532
(2)
ensure that {
when { UE initiates mobile originating CS fallback }
sends EXTENDED SERVICE REQUEST message }
}

5.6.1.1, 5.6.1.2 and Annex D and TS 36.331 clause 5.3.3.3.[TS 24.301 clause 5.3.1.1]
[TS24.301 clause5.6.1.1]
mode and establish the radio and S1 bearers when uplink user data or signalling is to be sent. Another purpose of this
procedure is to invoke MO/MT CS fallback procedures.
This procedure is used when:

- the UE in EMM-IDLE or EMM-CONNECTED mode has requested to perform mobile originating/terminating
CS fallback; or

The service request procedure is initiated by the UE, however, for the downlink transfer of signalling or user data in
EMM-IDLE mode, the trigger is given by the network by means of the paging procedure (see subclause 5.6.2).

d) the UE, in EMM-IDLE or EMM-CONNECTED mode, has a mobile originating CS fallback request;.

[TS24.301 clause5.6.1.2]
The UE shall send an EXTENDED SERVICE REQUEST message,
- regardless of the EMM mode, if the UE has a mobile originating CS fallback request; and

...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1533 Release 9
1533
...
Service Request If a EXTENDED SERVICE REQUEST has service type set to
"mobile originating CS fallback", the RRC establishment cause
shall be set to MO data. (See Note1).
"originating calls"
...

[TS 36.331, clause 5.3.3.3]
...
2>else
System Simulator:
- cell A.
UE:
none.Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1534 Release 9
1534
U - S Message
1 Force the UE to initiate CS Voice call. (Note 1) - - -
3 The SS sends SERVICE REJ ECT message in
order that the UE enters EMM-
4 The SS releases the RRC connection - - -
5 Force the UE to initiate CS Voice call. (Note1) - - -
establishmentCause set to mo-Data followed by
EXTENDED SERVICE REQUEST message?
Note 1: This could be done by e.g. MMI or by AT command.

Table 9.3.1.3.3.3-1: Message EXTENDED SERVICE REQUEST (step 2/6, Table 9.3.1.3.3.2-1)
Derivation Path: 36.508 clause 4.7.2-14A
CS fallback

M-TMSI M-TMSI1

Table 9.3.1.3.3.3-2: Message SERVICE REJECT (step 3, Table 9.3.1.3.3.2-1)
EMM cause 0010 0110 CS fallback call
establishment not
allowed

}
}
}

9.3.1.4 Service request / Rejected / IMSI invalid
(1)
with { UE having sent a SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to 'Illegal UE' }
registered TAI, TAI list and KSI, considers the USIM as invalid for EPS services until switching off
or the UICC containing the USIM is removed, enters the state EMM-DEREGISTERED }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1535 Release 9
1535
(2)
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to 'Illegal UE' }
then { UE handles the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature,
RAI and GPRS ciphering key sequence number and the MM parameters update status, TMSI, LAI and
ciphering key sequence number }
}

TS 24.008, clause 4.7.13.4.
[TS 24.301, clause 5.6.1.5]
If the service request cannot be accepted, the network shall return a SERVICE REJ ECT message to the UE including an
appropriate EMM cause value. When the EMM cause value is #39 "CS domain temporarily not available", the MME
shall include a value for timer T3442 in the SERVICE REJECT message.
On receipt of the SERVICE REJ ECT message, the UE shall stop timer T3417 and take the following actions depending
on the received EMM cause value.
#3 (Illegal UE); or
...
subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall
The UE shall enter the state EMM-DEREGISTERED.
for the case when the service request procedure is rejected with the GMM cause with the same value. The USIM
shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is
removed.
NOTE 1: The possibility to configure a UE so that the radio transceiver for a specific radio access technology is not
active, although it is implemented in the UE, is out of scope of the present specification.
[TS 24.008, clause 4.7.13.4]
If the Service request cannot be accepted, the network returns a SERVICE REJ ECT message to the mobile station. An
MS that receives a SERVICE REJ ECT message stops timer T3317. The MS shall then take different actions depending
on the received reject cause value:
#3 (Illegal MS); or
...
- The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to
subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. Furthermore, it shall delete any P-TMSI, P-
TMSI signature, RAI and GPRS ciphering key sequence number and shall consider the SIM/USIM as invalid for
GPRS services until switching off or the SIM/USIM is removed.
- A GPRS MS operating in MS operation mode A shall in addition set the update status to U3 ROAMING NOT
ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS
operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call
is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the
SIM/USIM is removed.
If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status,
GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the
service request procedure is rejected with the EMM cause with the same value.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1536 Release 9
1536
System Simulator:
- if pc_UTRAN, cell 5 (belongs to LAI-1 and RAI-1, home PLMN); system information combination 9 as defined
in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;
- if pc_GERAN and NOT pc_UTRAN, cell 24 (belongs to LAI-1 and RAI-1, home PLMN); system information
combination 12 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells

- cell A is "Serving cell" and cell B, cell 5 and cell 24 are "non-Suitable cell".
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1537 Release 9
1537
U - S Message
- - - -
- - - -
message.
UE'.
cell".
- - - -
- - - -
supported
- - - -
6Aa1 IF pc_UTRAN or pc_GERAN THEN the SS
sets the cell type of Cell B to the "non-Suitable
- - - -
otherwise.
- - - -
6Aa2 Void - - - -
6Aa3 Check: Does the UE transmit an ATTACH
6Aa4 If possible (see ICS) switch off is performed or
the USIM is removed, otherwise the power is
removed.
- - - -
6Aa5 The UE is brought back to operation or the
USIM is inserted.
- - - -
6Aa6 Check: Does the UE transmit an ATTACH
REQUEST message?
7-10 Void
(Note 2)
- - - -
11A Set the cell type of the Cell B to the "non-
Suitable cell". Set the cell type of Cell A to the
"Serving cell". Set the cell type of Cell 5 or Cell
24 to the "non-Suitable cell.
- - - -
- - - -
USIM is inserted.
- - - -
14-
30
Void <-- - - -
31a1
-
31a9
Void - - - -
32- The attach procedure is completed by - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1538 Release 9
1538
43 executing steps 5 to 16 of the UE registration
- - - -
response of ATTACH REQUEST message in step 6Aa6.

Table 9.3.1.4.3.3-1: SERVICE REJECT (step 3, Table 9.3.1.4.3.2-1)

apply for NAS key
"111".

Old GUTI or IMSI IMSI of the UE
'0'B no valid TMSI
available

pc_CS_fall
back OR
pc_SMS_S
Gs_MT OR
pc_SMS_S
Gs_MO

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1539 Release 9
1539
Table 9.3.1.4.3.3-3: ATTACH REQUEST (step 6Aa6, Table 9.3.1.4.3.2-1)
Attach type Any allowed value
available (MS to
network)

P-TMSI or IMSI IMSI of the UE
0.
Other bits are not
checked.

value
Not present or any
allowed value

'0'B no valid TMSI
available
pc_CS_fall
back OR
pc_SMS_S
Gs_MT OR
pc_SMS_S
Gs_MO
allowed value

allowed value

allowed value

allowed value

allowed value


9.3.1.5 Service request / Rejected / Illegal ME
(1)
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to 'Illegal ME' }
or the UICC containing the USIM is removed, enters the state EMM-DEREGISTERED }
}

(2)
with { UE supporting A/Gb mode or Iu mode and having sent a SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to 'Illegal ME' }
then { UE sets the GPRS update status to GU3 ROAMING NOT ALLOWED, deletes any P-TMSI, P-TMSI
signature, TMSI, LAI, RAI and GPRS ciphering key sequence number and considers the SIM/USIM as
invalid for GPRS services until switching off or the SIM/USIM is removed }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1540 Release 9
1540
TS 24.008, clause 4.7.13.4.
[TS 24.301, clause 5.6.1.5]
...
#6 (Illegal ME);
for the case when the service request procedure is rejected with the GMM cause with the same value. The USIM
shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is
removed.
NOTE 1: The possibility to configure a UE so that the radio transceiver for a specific radio access technology is not
active, although it is implemented in the UE, is out of scope of the present specification.
[TS 24.008, clause 4.7.13.4]
...
#6 (Illegal ME);
subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. Furthermore, it shall delete any P-TMSI, P-
TMSI signature, RAI and GPRS ciphering key sequence number and shall consider the SIM/USIM as invalid for
GPRS services until switching off or the SIM/USIM is removed.
- A GPRS MS operating in MS operation mode A shall in addition set the update status to U3 ROAMING NOT
ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS
operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call
is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the
SIM/USIM is removed.
System Simulator:
Same as in 9.3.1.4.3.1
UE:
Same as in 9.3.1.4.3.1
Preamble:
Same as in 9.3.1.4.3.1

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1541 Release 9
1541
Same as in 9.3.1.4.3.2 with the exception that all occurances of EMM cause set to 'Illegal UE' shall be replaced with
EMM cause set to 'Illegal ME'.
For the Specific message contets refer to with the following exceptions.
Table 9.3.1.5.3.3-1: SERVICE REJECT (step 3 and step 29, Table 9.3.1.4.3.2-1)

9.3.1.6 Service request / Rejected / EPS services not allowed
(1)
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to 'EPS services not allowed' }
or the UICC containing the USIM is removed and enters the state EMM-DEREGISTERED }
}

(2)
with { UE supporting A/Gb mode or Iu mode and having sent a SERVICE REQUEST message }
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to 'EPS services not allowed' }
then { UE sets the GPRS update status to GU3 ROAMING NOT ALLOWED, deletes any P-TMSI, P-TMSI
signature, RAI and GPRS ciphering key sequence number and considers the SIM/USIM as invalid for GPRS
services until switching off or the SIM/USIM is removed }
}

TS 24.008, clause 4.7.13.4.
[TS 24.301, clause 5.6.1.5]
...
...
3GPP TS 24.008 [13] for the case when the service request procedure is rejected with the GMM cause with the
same value.
[TS 24.008, clause 4.7.13.4]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1542 Release 9
1542
...
#7 (GPRS services not allowed);
number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM
is removed. The new state is GMM-DEREGISTERED.
System Simulator:
- cell A is configured as the "Serving cell";
- if pc_UTRAN, cell 5 (belongs to LAI-1 and RAI-1, home PLMN) is configured as a 'Non-suitable "Off" cell';
system information combination 4 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells
- if pc_GERAN, cell 24 (belongs to LAI-1 and RAI-1, home PLMN) is configured as a 'Non-suitable "Off" cell';
system information combination 5 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
Preamble:
- The UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1543 Release 9
1543
U - S Message
additional PDN (see Note 1).
- - - -
- - - -
2 UE transmits a SERVICE REQUEST
message.
3 The SS transmits an SERVICE REJ ECT
allowed".
- - 1 -
supported
- - - -
7a1 IF pc_UTRAN THEN SS configures:
- Cell A as 'Non-suitable cell'
- Cell 5 as 'Serving cell'
- IF pc_GERAN THEN Cell 24 as 'Non-suitable
"Off" cell'
- - - -
Cell 5 unless explicitly stated otherwise.
- - - -
9.3.1.6.3.2-2 occurs in parallel with steps 7a2
to 7a4.
- - - -
7a3 The user initiates an attach by MMI or by AT
command.
- - - -
7b1 IF pc_GERAN THEN SS configures:
- IF pc_UTRAN THEN Cell 5 as 'Non-suitable
"Off" cell'
- - - -
- - - -
9.3.1.6.3.2-2 occurs in parallel with steps 7b2
to 7b4.
- - - -
7b3 The user initiates an attach by MMI or by AT
command.
- - - -
8 IF pc_USIM_Removal THEN USIM is removed
ELSE the UE is powered down or switched off.
- - - -
- Cell A as the 'Serving cell'.
- IF pc_UTRAN THEN Cell 5 'Non-suitable
"Off" cell'.
- IF pc_GERAN THEN Cell 24 'Non-suitable
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1544 Release 9
1544
"Off" cell'.
10 IF pc_USIM_Removal THEN USIM is incerted
ELSE the UE is powered up or switched on.
- - - -
message on cell A including a PDN
authentication.
- - - -
options and/or APN.
16a2 The UE transmits the ESM INFORMATION
- - - -
- EXCEPTION: Step 19a1 to 19b6 describe
supported
- - - -
19a1 IF pc_UTRAN THEN SS configures:
- IF pc_GERAN THEN Cell 24 'Non-suitable
"Off" cell'.
- - - -
- - - -
19a2 IF Automatic PS attach procedure at switch on
or power on=FALSE THEN The user initiates
an attach by MMI or by AT command.
- - - -
REQUEST message?
19a4 The SS transmits an AUTHENTICATION AND
CIPHERING REQUEST message to initiate
the authentication and AKA procedure.
CIPHERING REQUEST
- -
19a5 The UE transmits an AUTHENTICATION AND
CIPHERING RESPONSE
- -
19a6 The SS transmits an ATTACH ACCEPT <-- ATTACH ACCEPT - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1545 Release 9
1545
message.
19a7 The UE transmits an ATTACH COMPLETE
message.
19b1 IF pc_GERAN THEN SS configures:
- Cell 5 as 'Non-suitable "Off" cell'
- - - -
- - - -
19b2 IF Automatic PS attach procedure at switch on
or power on=FALSE THEN The user initiates
an attach by MMI or by AT command.
- - - -
REQUEST message?
19b4 The SS transmits an AUTHENTICATION AND
CIPHERING REQUEST message to initiate
the authentication and AKA procedure.
CIPHERING REQUEST
- -
19b5 The UE transmits an AUTHENTICATION AND
CIPHERING RESPONSE
- -
19b6 The SS transmits an ATTACH ACCEPT
message.
19b7 The UE transmits an ATTACH COMPLETE
message.
Note 1: The request of connectivity to an additional PDN and the sending of data may be performed by MMI or AT
command.

U - S Message
- EXCEPTION: Steps 1a1 and 1a2 describe a
behaviour which depends on the UE capability;
supported.
- - - -
1a1 IF pc_CS THEN the UE transmits a
LOCATION UPDATING REQUEST message.
REQUEST
- -
ACCEPT message including IMSI-1

allowed

Table 9.3.1.6.3.3-2: Message ATTACH REQUEST (step 11, Table 9.3.1.6.3.2-1)
Old LAI Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1546 Release 9
1546
Table 9.3.1.6.3.3-3: Message ATTACH REQUEST (step 19a3 and 19b3, Table 9.3.1.6.3.2-1)
Derivation path: TS 24.008 table 9.4.1
GPRS ciphering key sequence number '111'B no key is available
P-TMSI or IMSI IMSI1
Old routing area identification all bits of the location
area code shall be set to
one with the exception of
the least significant bit
which shall be set to zero
RAI is deleted

9.3.1.7 Service request / Rejected / UE identity cannot be derived by the network
(1)
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause value = 9 (UE identity cannot be
derived by the network) }
then { UE sets the EPS update status to EU2 NOT UPDATED and deletes any GUTI, last visited
registered TAI, TAI list and KSI and automatically initiate the attach procedure }
}
[TS 24.301, clause 5.6.1.5]

The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to subclause
5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall enter the state
EMM-DEREGISTERED.
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1547 Release 9
1547
U - S Message
- - - -
message.
message with the EMM cause set to #9 (UE
identity cannot be derived by the network).
REQUEST message including IMSI and
without integrity protection?
- - - -
- - - -

EMM cause '0000 1001'B UE identity cannot
be derived by the
network


9.3.1.7a Service request / Rejected / UE implicitly detached
9.3.1.7a.1 Test Purpose (TP)
(1)
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to 'Implicitly detached' }
then { UE enters the state EMM-DEREGISTERED.NORMAL-SERVICE, delete the EPS mapped EPS security
context if any and performs a new attach procedure }
}

9.3.1.7a.2 Conformance requirements
[TS 24.301, clause 5.6.1.5]
appropriate EMM cause value.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1548 Release 9
1548

The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete the EPS
mapped EPS security context if any. The UE shall then perform a new attach procedure.
9.3.1.7a.3 Test description
9.3.1.7a.3.1 Pre-test conditions
System Simulator:
- cell A.
UE:
none.
Preamble:
9.3.1.7a.3.2 Test procedure sequence
Table 9.3.1.7a.3.2-1: Main behaviour
U - S Message
- - - -
message.
message with the EMM cause set to 'Implicitly
detached'.
CONNECTIVITY REQUEST message and
integrity protected using the native security
context resulting from authentication during the
test preamble?
- - - -
- - - -

9.3.1.7a.3.3 Specific message contents
Table 9.3.1.7a.3.3-1: SERVICE REJECT (step 3, Table 9.3.1.7a.3.2-1)
EMM cause '0000 1010'B Implicitly detached

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1549 Release 9
1549
Table 9.3.1.7a.3.3-2: ATTACH REQUEST (step 4, Table 9.3.1.7a.3.2-1)
NAS key set identifier NAS key set identifier
allocated to UE during
authentication in test
preamble

TSC 0B Native security
context

Old GUTI or IMSI GUTI allocated to UE
during previous attach on
Cell A.

'0'B no valid TMSI
available
pc_CS_fall
back

9.3.1.8 to 9.3.1.12 Void
9.3.1.12a Extended service request / Rejected / CS domain temporarily not available
(1)
with { UE has received a SERVICE REJECT message with the EMM cause set to 'CS domain temporarily not
available' and has started T3442 }
ensure that {
when { UE is requested to initiate a CS call }
then { UE does not transmit any EXTENDED SERVICE REQUEST message }
}

[TS 24.301, clause 5.6.1.5]
appropriate EMM cause value. When the EMM cause value is #39 "CS domain temporarily not available", the MME
shall include a value for timer T3442 in the SERVICE REJECT message.
...
#39 (CS domain temporarily not available);
The UE shall start timer T3442 and enter the state EMM-REGISTERED.NORMAL-SERVICE.
The UE shall not try to send an EXTENDED SERVICE REQUEST message for mobile originating services to
the network, except for mobile originating CS fallback for emergency calls, until timer T3442 expires or the UE
sends a TRACKING AREA UPDATE REQUEST message.
System Simulator:
- cell A.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1550 Release 9
1550
UE:
none.
Preamble:
- the UE is in state Registered, Idle Mode (state 2) according to TS 36.508 [18].
U - S Message
domain indicator set to "CS".
- - - -
2 The UE transmits an EXTENDED SERVICE
REQUEST message.
--> EXTENDED SERVICE REQUEST - -
message with the EMM cause set to 'CS
domain temporarily not available'.
5 Cause the UE to originate CS call. (Note 1) - - - -
6 Check: Does the UE transmit an EXTENDED
SERVICE REQUEST message in the next 30
seconds?
the USIM is removed. Otherwise the power is
removed. (Note 2)
- - - -
Note 1: The trigger in step 5 is the same as in the generic procedure in 36.508 clause 6.4.3.5.
Note 2: The UE is powered off, switched off, or the USIM is removed because the UE may retry a transmission of an
EXTENDED SERVICE REQUEST message depending on the UE implementation after timer T3442 expires.
Additionally, it is not clear which postamble procedure is performed, since the UE may search the
UTRAN/GERAN cell after step 3.

Table 9.3.1.12a.3.3-1: Message SERVICE REJECT (step 3, Table 9.3.1.12a.3.2-1)
EMM cause '0010 0111'B CS domain
temporarily not
available

T3442 value
Timer value '0 0001'B 1 minute
incremented in
multiples of 1
minute

9.3.1.13 Void
9.3.1.14 Void
9.3.1.15 Service request / Abnormal case / Tracking area update procedure is
triggered
(1)
ensure that {
when { Tracking area updating procedure is triggered }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1551 Release 9
1551
then { The UE abort the service request procedure, stop timer T3417 if running and perform the
tracking area updating procedure, in the TRACKING AREA UPDATE REQUEST message, the "active" flag
shall be set to 1}
}

(2)
with { UE having sent a EXTENDED SERVICE REQUEST message }
ensure that {
when { Tracking area updating procedure is triggered }
then { The UE shall abort the service request procedure, stop timer T3417ext if running and
perform the tracking area updating procedure. after the completion of tracking area update procedure,
UE restart the CSFB procedure }
}

[TS 24.301, clause 5.6.1.6]
...
f) Tracking area updating procedure is triggered
The UE shall abort the service request procedure, stop timer T3417 or T3417ext if running and perform the
tracking area updating procedure. The "active" flag shall be set in the TRACKING AREA UPDATE REQUEST
message. If the service request was initiated for CS fallback or 1xCS fallback, the UE shall send the
EXTENDED SERVICE REQUEST message to the MME by using the existing NAS signalling connection after
the completion of the tracking area updating procedure.
System Simulator:
- cell A, cell B.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1552 Release 9
1552
U - S Message
1 The SS pages the UE using S-TMSI1 with CN
- - - -
message.
3 The SS does not perform a radio bearer
establishment procedure.
Note: e.g. SS does not send any AS or NAS
messages to UE.
- - - -
cell''.
Note: cell type should be set before timer
T3417 expired.
- - - -
procedure on cell B.
- - - -
AREA UPDATE REQUEST message on cell B
REQUEST
1 P
ACCEPT
- -
COMPLETE
- -
- EXCEPTION: Steps 9 to 27 describe
IF pc_CSfallback is true, from Step 9 to step
27should be executed, or else test case is
terminated in step 8
- - - -
- - - -

the UE transmit a DETACH REQUEST
message.
USIM is inserted.
- - - -
including a PDN CONNECTIVITY REQUEST
message on cell B.
- - - -
options and/or APN.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1553 Release 9
1553
17 Force the UE to initiate CS Voice call. (Note 1) - - -
18 The UE transmits an EXTENDED SERVICE
REQUEST message.
19 The SS does not respond to this request.
Note: e.g. SS does not send any AS or NAS
messages to UE.
- - - -
20 Set the cell type of cell A to the '' Serving cell ''.
Set the cell type of cell B to the '' Non-Suitable
cell ''.
Note: cell type should be set before timer
T3417ext expired.
- - - -
procedure on cell A.

REQUEST
2 P
ACCEPT
- -
COMPLETE

SERVICE REQUEST message on cell A?
Note 1: This could be done by e.g. MMI or by AT command.

Table 9.3.1.15.3.3-1: Message TRACKING AREA UPDATE REQUEST (step 6, Table 9.3.1.15.3.2-1)
"Active" flag 1B Bearer
establishment
requested

included by UE if
valid, IMSI
otherwise''

Table 9.3.1.15.3.3-2: Message TRACKING AREA UPDATE ACCEPT (step 7, Table 9.3.1.15.3.2-1)
GUTI GUTI-2
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1
TAI-2

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1554 Release 9
1554
Table 9.3.1.15.3.3-3: Message EXTENDED SERVICE REQUEST (step 18, Table 9.3.1.15.3.2-1)
CS fallback

M-TMSI M-TMSI2

Table 9.3.1.15.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 22, Table 9.3.1.15.3.2-1)
included by UE if
valid, IMSI
otherwise''

Table 9.3.1.15.3.3-5: Message TRACKING AREA UPDATE ACCEPT (step 23, Table 9.3.1.15.3.2-1)
GUTI GUTI-1
TAI list
belonging to one
PLMN, with non-
consecutive TAC
values''

MCC
MNC
TAC 1

TAI-1

CS fallback

M-TMSI M-TMS1

EMM cause '0001 0010'B ''CS domain not
available''

9.3.1.16 Service request / Abnormal case / Switch off
(1)
ensure that {
when { UE is switched off }
then { UE performs the detach procedure }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1555 Release 9
1555
}

[TS 24.301, clause 5.6.1.6]
...
g) Switch off
If the UE is in state EMM-SERVICE-REQUEST-INITIATED at switch off, the detach procedure shall be
performed.
...
System Simulator:
- cell A.
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (state 2) according to Ts 36.508 [18].
U - S Message
- - - -
message.
3 The SS does not respond to the SERVICE
REQUEST message.
NOTE: The SS does not transmit both
SecurityModeCommand message and
- - - -
4 The UE is switched off. - - - -
REQUEST message?
indicates that the UE does not respond to
- - 1 -

None.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1556 Release 9
1556
9.3.1.17 Service request / Abnormal case / Procedure collision
(1)
ensure that {
when { UE receives a DETACH REQUEST message with the Type of detach set to 're-attach required' }
then { UE sends a DETACH ACCEPT message and performs the attach procedure }
}

(2)
with { UE having sent a SERVICE REQUEST message or an EXTENDED SERVICE REQUEST message}
ensure that {
when { UE receives a DETACH REQUEST message with the Type of detach set to the value other than
're-attach required' }
then { UE sends a DETACH ACCEPT message }
}

[TS 24.301, clause 5.6.1.6]
...
h) Procedure collision
If the UE receives a DETACH REQUEST message with detach type "re-attach required" or "re-attach not
required" with EMM cause other than #2 "IMSI unknown in HSS" from the network in state EMM-SERVICE-
REQUEST-INITIATED, the detach procedure shall be progressed and the service request procedure shall be
aborted.
Additionally, if the service request was initated for CS fallback or 1xCS fallback, the EMM sublayer shall
indicate to the MM sublayer or the cdma2000
upper layers that the CS fallback or 1xCS fallback procedure has

failed.
If the Detach type IE in the DETACH REQUEST message indicated "re-attach required", the attach procedure
shall be performed.
System Simulator:
- cell A.
UE:
none.
Preamble:
- the UE is in state Registered, Idle mode (state 2) according to TS 36.508 [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1557 Release 9
1557
U - S Message
- - - -
message.
message with the Type of detach set to 're-
attach required'.
ACCEPT message?
- - - -
- - - -
authentication.
message.
- - - -
options and/or APN.
- - - -
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1558 Release 9
1558
supported
15a1 IF pc_CSfallback is true THEN the SS pages
the UE using S-TMSI with CN domain indicator
set to "CS".
- - - -
15a2 The UE transmits an EXTENDED SERVICE
REQUEST message.
15b1 ELSE the SS pages the UE using S-TMSI with
CN domain indicator set to "PS".
- - - -
15b2 The UE transmits a SERVICE REQUEST
message.
message with the Type of detach set to the
value other than 're-attach required'.
ACCEPT message?
- - - -

Table 9.3.1.17.3.3-1: Message DETACH REQUEST (step 3, Table 9.3.1.17.3.2-1)
Detach type
Type of detach '001'B re-attach required
EMM cause Not present If the detach type
IE indicates "IMSI
detach" or "re-
attach required",
then the UE shall
ignore the EMM
cause IE if
received.

Table 9.3.1.17.3.3-2: Message DETACH REQUEST (step 16, Table 9.3.1.17.3.2-1)
Detach type
Type of detach '010'B re-attach not
required


9.3.1.18 Service Request / Rejected / Not authorized for this CSG
(1)
ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause value = 25 (Not authorized for this
CSG) and this SERVICE REJECT message is not without integrity protection }
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, removes the CSG ID of the cell
that sent SERVICE REJECT message from the Allowed CSG list, searches for a suitable cell in the same
PLMN }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1559 Release 9
1559
(2)
with { UE in state EMM-REGISTERED and EMM-IDLE mode and the CSG ID is removed from the Allowed CSG
list }
ensure that {
when { UE detects entering new tracking areas not included in the TAI list }
then { UE attempts to enter a normal cell and does not select a cell which is not included in
the allowed CSG list }
}

[TS 24.301, clause 5.6.1.5]

considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.6.
If the SERVICE REJ ECT message with cause #25 was received without integrity protection, then the UE shall
subclause 5.1.3.3). The UE shall enter the state EMM-REGISTERED.LIMITED-SERVICE.
The UE shall remove the CSG ID of the cell where the UE has initiated the service request procedure from the
Allowed CSG list.
System Simulator:
- cell A(TAC1, frequency 1, is a CSG cell);
- cell B(TAC2, frequency 1, not a CSG cell);
- cell A is "Serving cell" and cell B " Non-suitable cell".
UE:
of cell A).
Preamble:
- The UE is in state Registered, Idle mode (state 2) on cell A according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1560 Release 9
1560
U - S Message
- - - -
received on Cell A.
- - - -
message.
message with the EMM cause =" Not
authorized for this CSG " as specified.
- Cell B as a " Suitable Neighbour cell ".
- - - -
AREA UPDATE REQUEST message on cell B
REQUEST
1 P
ACCEPT
- -
COMPLETE
- -
- Cell B as a " Not Suitable cell".
- - - -
REQUEST
2 F

EMM cause '00011001'B #25 " Not
authorized for this
CSG "

Table 9.3.1.18.3.3-2: SystemInformationBlockType1 for Cell A, B(Pre-test conditions and all steps in
Table 9.3.1.18.3.2-1)
csg-Indication TRUE Cell A
FALSE Cell B
csg-Identity Not present Cell B
'000 0000 0000 0000
0000 0000 0010'B
Cell A

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1561 Release 9
1561
9.3.2 Paging procedure
9.3.2.1 Paging procedure
(1)
with { UE in ECM-IDLE }
ensure that {
when { the network initiates a paging procedure for EPS services using S-TMSI }
then { the UE responds to the paging with a SERVICE REQUEST message providing correct S-TMSI in
the RRCConnectionRequest }
}

5.6.2.2.1, TS 33.401 clause 7.2.6.2, TS 36.331 clause 5.3.3.3.
[TS 24.301, clause 5.6.2.2.1]
To initiate the procedure the EMM entity in the network requests the lower layer to start paging (see
3GPP TS 36.300 [20], 3GPP TS 36.413 [23]) and starts the timer T3413 for this paging procedure. Upon reception of a
paging indication, the UE shall respond to the paging with a SERVICE REQUEST message (see 3GPP TS 23.401 [10]
and 3GPP TS 36.413 [23]). If the paging for EPS services was received during an ongoing UE initiated EMM specific
procedure or service request procedure, then the UE shall ignore the paging and the UE and the network shall proceed
with the EMM specific procedure or the service request procedure.
[TS 24.301, clause 5.6.1.1]
a) the UE in EMM-IDLE mode receives a paging request with CN domain indicator set to "PS" from the network;
[TS 33.401 clause 7.2.6.2]
The procedure the UE uses to transit from ECM-IDLE to ECM-CONNECTED when in EMM-REGISTERED state is
initiated by a NAS Service Request message from the UE to the MME. As the UE is in EMM-REGISTERED state, a
EPS security context exists in the UE and the MME, and this EPS security context further contains uplink and downlink
NAS COUNTs. The NAS Service Request message sent in EMM-REGISTERED shall be integrity protected and
contain the uplink NAS sequence number.
[TS 36.331, clause 5.3.3.3]
System Simulator:
- cell A.
UE:
- none.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1562 Release 9
1562
Preamble:
- the UE is in Registered, Idle Mode (state 2) according to TS 36.508 [18].
U - S Message
1 SS pages the UE using S-TMSI with CN
domain indicator set to "PS"
- - - -
2 Check: Does the UE transmit
RRCConnectionRequest message providing
correct S-TMSI?
- - 1 P
3 Check: Does the UE respond with a SERVICE
REQUEST message?

- - - -

Derivation Path: Table 4.6.1-16
TMSI of the UE

}
}
}
}

9.3.2.2 Paging for CS fallback / Idle mode
(1)
ensure that {
when { UE received Paging for mobile termination CS fallback from NW }
then { UE establishes the RRC connection with the RRC establishmentCause set to mt-Access and
sends EXTENDED SERVICE REQUEST message }
}

5.6.1.1, 5.6.2.3 and Annex D and TS 36.331 clause 5.3.3.3.
[TS 24.301 clause 5.3.1.1]
[TS24.301 clause5.6.1.1]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1563 Release 9
1563

CS fallback; or


e) the UE, in EMM-IDLE or EMM-CONNECTED mode, has a CS fallback response to be sent to the network; or

[TS24.301 clause5.6.2.3]
The network may initiate the paging procedure for non-EPS services when the UE is IMSI attached for non-EPS
services.
To initiate the procedure when no NAS signalling connection exists, the EMM entity in the network requests the lower
layer to start paging (see 3GPP TS 36.300 [2012], 3GPP TS 36.413 [2315]) and starts the timer T3413 for this paging
procedure. The paging message includes a CN domain indicator set to ''CS'' in order to indicate that this is paging for
CS fallback. Upon reception of a paging indication, the UE may respond to the paging immediately or may request
upper layers input i.e. to accept or reject CS fallback. The response is indicated in the CSFB response information
element in the EXTENDED SERVICE REQUEST message in both EMM-IDLE and EMM-CONNECTED modes.
The network shall stop the timer T3413 for the paging procedure when a response is received from the UE.
To notify the UE about an incoming mobile terminating CS service when a NAS signalling connection exists, the EMM
entity in the network shall send a CS SERVICE NOTIFICATION message.
...
...
"mobile terminating CS fallback", the RRC establishment cause
shall be set to MT access. (See Note1).
"terminating calls"

...

[TS 36.331, clause 5.3.3.3]
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1564 Release 9
1564
2>else
System Simulator:
- cell A.
UE:
none.
Preamble:
U - S Message
1 The SS sends a paging message which CN
domain indicates ''CS'' domain to the UE.
- - - -
2 The UE accepts CS fallback - - - -
establishmentCause set to mt-Access
followed by EXTENDED SERVICE REQUEST
message?

}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1565 Release 9
1565
M-TMSI M-TMSI1

EMM cause '0010 0110'B ''CS fallback call
establishment not
allowed''

9.3.2.2a Paging for CS fallback / Connected mode
(1)
ensure that {
when { UE receives a CS SERVICE NOTIFICATION message for mobile termination CS fallback from NW }
then { UE sends EXTENDED SERVICE REQUEST message }
}

5.6.1.1, 5.6.2.3 and Annex D and TS 36.331 clause 5.3.3.3.
[TS 24.301 clause 5.3.1.1]
[TS24.301 clause5.6.1.1]

CS fallback; or


e) the UE, in EMM-IDLE or EMM-CONNECTED mode, has a CS fallback response to be sent to the network; or

[TS24.301 clause5.6.2.3]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1566 Release 9
1566
services.
layer to start paging (see 3GPP TS 36.300 [2012], 3GPP TS 36.413 [2315]) and starts the timer T3413 for this paging
procedure. The paging message includes a CN domain indicator set to ''CS'' in order to indicate that this is paging for
CS fallback. Upon reception of a paging indication, the UE may respond to the paging immediately or may request
upper layers input i.e. to accept or reject CS fallback. The response is indicated in the CSFB response information
element in the EXTENDED SERVICE REQUEST message in both EMM-IDLE and EMM-CONNECTED modes.
The network shall stop the timer T3413 for the paging procedure when a response is received from the UE.
entity in the network shall send a CS SERVICE NOTIFICATION message.
...
...
"mobile terminating CS fallback", the RRC establishment cause
shall be set to MT access. (See Note1).
"terminating calls"

...

System Simulator:
- Cell A(TAI-1) is set to ''Serving cell''
UE:
None.
Preamble:
- The UE is in state Generic RB established (state 3) on cell A according to [18].
U - S Message
1 The SS sends a CS SERVICE NOTIFICATION
message to the UE.
<-- CS SERVICE NOTIFICATION - -
2 The UE accepts CS fallback - - -
SERVICE REQUEST message to SS?
4 The SS sends a SERVICE REJ ECT message
in order that the UE enters EMM-

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1567 Release 9
1567
Table 9.3.2.2a.3.3-1: Message EXTENDED SERVICE REQUEST (step 3, Table 9.3.2.2a.3.2-1)
M-TMSI M-TMSI1

Table 9.3.2.2a.3.3-2: Message SERVICE REJECT (step 4, Table 9.3.2.2a.3.2-1)
EMM cause '0010 0110'B ''CS fallback call
establishment not
allowed''

9.4 NAS Security
9.4.1 Integrity protection / Correct functionality of EPS NAS integrity
algorithm / SNOW3G
(1)
ensure that {
when { UE receives a an integrity protected SECURITY MODE COMMAND message instructing to start
integrity protection using algorithm SNOW3G }
then { UE transmits an integrity protected SECURITY MODE COMPLETE using SNOW3G and starts
applying the NAS Integrity protection in both UL and DL }
(2)
with { Integrity protection succesfull started by executing Security Mode Procedure}
ensure that {
when { UE receives an IDENTITY REQUEST message without integrity protected }
then { UE foes not transmit an IDENTITY RESPONSE message }
}
5.4.3.1, 5.4.3.2 and 5.4.3.3.
[TS 24.301, clause 4.4.4.1]
For the UE, integrity protected signalling is mandatory for the NAS messages once a valid EPS security context exists
and has been taken into use. For the network, integrity protected signalling is mandatory for the NAS messages once a
secure exchange of NAS messages has been established for the NAS signalling connection. Integrity protection of all
NAS signalling messages is the responsibility of the NAS. It is the network which activates integrity protection.
[TS 24.301, clause 4.4.4.2]
Once the secure exchange of NAS messages has been established, the receiving EMM or ESM entity in the UE shall not
process any NAS signalling messages unless they have been successfully integrity checked by the NAS. If NAS
signalling messages, having not successfully passed the integrity check, are received, then the NAS in the UE shall
discard that message. If any NAS signalling message is received as not integrity protected even though the secure
exchange of NAS messages has been established by the network, then the NAS shall discard this message.
[TS 24.301, clause 5.4.3.1]
[TS 24.301, clause 5.4.3.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1568 Release 9
1568
ASME
or mapped K'
ASME
...
UE
if the UE
Identifier (eKSI).
[TS 24.301, clause 5.4.3.3]
UE
take the native EPS security context into use.
procedure; or
b) the type of security context flag is set to "mapped security context" in the NAS KSI IE included in the SECURITY
MODE COMMAND message
If the security mode command can be accepted, the UE shall send a SECURITY MODE COMPLETE message integrity
protected with the selected NAS integrity algorithm and the NAS integrity key based on the K
ASME
or mapped K'
ASME
if
the type of security context flag is set to "mapped security context" indicated by the eKSI. If the SECURITY MODE
COMMAND message includes the type of security context flag set to "mapped security context" in the NAS KSI IE,
nonce
MME
and nonce
UE
, the UE shall generate K'
ASME
from both nonces as indicated in 3GPP TS 33.401 [19] and reset
the downlink NAS COUNT to check whether the SECURITY MODE COMMAND can be accepted or not. The UE
shall cipher the SECURITY MODE COMPLETE message with the selected NAS ciphering algorithm and the NAS
ciphering key based on the K
ASME
or mapped K'
ASME
indicated by the eKSI. The UE shall set the security header type of
the message to "integrity protected and ciphered with new EPS security context".
From this time onward the UE shall cipher and integrity protect all NAS signalling messages with the selected NAS
System Simulator:
- cell A.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1569 Release 9
1569
UE:
none.
Preamble:
U - S Message
REQUEST message
authentication.
COMMAND message to activate NAS
security. . It is integrity protected.
6 Check: does the UE transmit a NAS
SECURITY MODE COMPLETE message and
starts applying the NAS Integrity protection in
both UL and DL?
- - - -
6A
a1
options and/or APN.
6A
a2
7 The SS transmits with an ATTACH ACCEPT
message with Integrity protected and with
default ciphering
RESPONSE message with Integrity Protected
and with default ciphering?
message (not Integrity protected)
12 Check: does the UE transmits an IDENTIY
RESPONSE message within the next 5
seconds?
-> IDENTITY RESPONSE 2 F

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1570 Release 9
1570
Table 9.4.1.3.3-1: SECURITY MODE COMMAND (Step 5)
Selected NAS security algorithms
- Type of integrity protection algorithm 001 EPS integrity
algorithm 128-
EIA1[SNOW3G]

9.4.2 Integrity protection / Correct functionality of EPS NAS integrity
algorithm / AES
(1)
ensure that {
when { UE receives an integrity protected SECURITY MODE COMMAND message, to start integrity
protection using algorithm AES }
then { UE sends SECURITY MODE COMPLETE, integrity protected with AES and starts applying the NAS
Integrity protection in both UL and DL}
(2)
with { Integrity protection succesfull started by executing Security Mode Procedure}
ensure that {
when { UE receives a IDENTITY REQUEST message (requested identification parameter is not IMSI),
without integrity protected }
then { UE Does not transmit IDENTITY Response}
}
Same Conformance requirements as in clause 9.4.1.2
Same Pre-test conditions as in clause 9.4.1.3.1
Same Test procedure sequence as in table 9.4.1.3.2.1, except the integrity protection algorithm is AES.
Table 9.4.2.3.3-1: SECURITY MODE COMMAND (Step 6 )
- Type of integrity protection algorithm 010 EPS integrity
algorithm 128-
EIA2 (AES)

9.4.3 Ciphering and deciphering / Correct functionality of EPS NAS
encryption algorithm / SNOW3G
(1)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1571 Release 9
1571
ensure that {
when { UE receives a SECURITY MODE COMMAND instructing to start ciphering using algorithm SNOW3G }
then { UE sends a SECURITY MODE COMPLETE message ciphered with SNOW3G and starts applying the
NAS ciphering in both UL and DL}
}
References: The conformance requirements covered in the current TC are specified in: TS 24.301 clause 5.4.3.1, 5.4.3.2
and 5.4.3.3.
[TS 24.301, clause 5.4.3.1]
[TS 24.301, clause 5.4.3.2]
ASME
or mapped K'
ASME
...
UE
if the UE
Identifier (eKSI).
[TS 24.301, clause 5.4.3.3]
UE
take the native EPS security context into use.
procedure; or
b) the type of security context flag is set to "mapped security context" in the NAS KSI IE included in the
SECURITY MODE COMMAND message
If the security mode command can be accepted, the UE shall send a SECURITY MODE COMPLETE message integrity
protected with the selected NAS integrity algorithm and the NAS integrity key based on the K
ASME
or mapped K'
ASME
if
the type of security context flag is set to "mapped security context" indicated by the eKSI. If the SECURITY MODE
COMMAND message includes the type of security context flag set to "mapped security context" in the NAS KSI IE,
nonce
MME
and nonce
UE
, the UE shall generate K'
ASME
from both nonces as indicated in 3GPP TS 33.401 [19] and reset
the downlink NAS COUNT to check whether the SECURITY MODE COMMAND can be accepted or not. The UE

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1572 Release 9
1572
shall cipher the SECURITY MODE COMPLETE message with the selected NAS ciphering algorithm and the NAS
ciphering key based on the K
ASME
or mapped K'
ASME
indicated by the eKSI. The UE shall set the security header type of
the message to "integrity protected and ciphered with new EPS security context".
From this time onward the UE shall cipher and integrity protect all NAS signalling messages with the selected NAS
System Simulator:
- cell A.
UE:
none.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1573 Release 9
1573
U - S Message
REQUEST message
authentication.
6 Check: does the UE transmit a SECURITY
MODE COMPLETE message ciphered and
starts applying the NAS ciphering in both UL
and DL?
- - - -
6A
a1
options and/or APN.
6A
a2
7 The SS transmits with an ATTACH ACCEPT
message The ACTIVATE DEFAULT EPS
message Ciphered
RESPONSE message Ciphered?

- Type of ciphering algorithm 001 EPS encryption
algorithm 128-
EEA1 [SNOW3G]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1574 Release 9
1574
9.4.4 Ciphering and deciphering / Correct functionality of EPS NAS
encryption algorithm / AES
(1)
ensure that {
when { UE receives a SECURITY MODE COMMAND, to start encryption using algorithm AES}
then { UE sends SECURITY MODE COMPLETE, encrypted with AES and starts applying the NAS
encryption in both UL and DL }
}
Same Conformance requirements as in clause 9.4.3.2
Same Pre-test conditions as in clause 9.4.3.3.1
Same Test procedure sequence as in Table 9.4.3.3.2-1, except the integrity ciphering algorithm is AES.
- Type of ciphering algorithm 002 EPS encryption
algorithm 128-
EEA2 (AES)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1575 Release 9
1575
10 EPS session management
10.1 Void
10.2 Dedicated EPS bearer context activation
10.2.1 Dedicated EPS bearer context activation / Success
(1)
with { UE is in EMM-REGISTERED state and a PDN address for an active default EPS bearer was received
in an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message }
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message linked to the existing
default EPS bearer }
then { UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }
}
[TS 24.301, clause 6.4.2.3]
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall first
check the received TFT before taking it into use. Then the UE shall send an ACTIVATE DEDICATED EPS BEARER
CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. The ACTIVATE DEDICATED EPS
BEARER CONTEXT ACCEPT message shall include the EPS bearer identity.
The linked EPS bearer identity included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
message indicates to the UE to which default bearer, IP address and PDN the dedicated bearer is linked.
If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE uses
the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource
modification procedure to which the dedicated bearer context activation is related.
If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message and the PTI is
associated to a UE requested bearer resource allocation procedure or a UE requested bearer resource modification
procedure, the UE shall release the traffic flow aggregate description associated to the PTI value provided.
The UE shall use the received TFT to apply mapping of uplink traffic flows to the radio bearer if the TFT contains
packet filters for the uplink direction.
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message, the MME shall stop the
timerT3485 and enter the state BEARER CONTEXT ACTIVE.
System Simulator:
UE:
None.

Preamble:
- The UE is in Registered, Ile Mode state (state 2) according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1576 Release 9
1576

U - S Message
1 The SS pages the UE in order to establish a
dedicated EPS bearer context.
- - - -
2 The UE transmits a SERVICE REQUEST for
downlink signalling.
2A The SS establishes SRB2 and DRB
associated with the default EPS bearer context
activated during the preamble (a first PDN
obtained during the attach procedure).
- - - -
EPS BEARER CONTEXT REQUEST with
particular settings (use Reference dedicated
EPS bearer context #1 see table 6.6.2-1 in
TS 36.508) (See Note 1).

Note: The SS implicitly reuses the PDN
address defined in ACTIVATE DEFAULT EPS
- -
4 Check: Does the UE transmit an ACTIVATE
DEDICATED EPS BEARER CONTEXT
ACCEPT message as specified?
1 P
procedure indicate that the UE accepts a
modification of the newly activated EPS bearer
context ? (clause 6.4.2.6 in [18])
- - 1 -
Note 1: The ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message is included in a
RRCConnectionReconfiguration message including a DRB setup for the same EPS bearer ID

Table 10.2.1.3.3-1: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 3, Table
10.2.1.3.2-1)
Derivation path: 36.508 table 4.7.3-3 and table 4.6.1-8 with condition UM-DRB-ADD(2)
EPS bearer identity 6
Procedure transaction identity 0 "No procedure
transaction
identity assigned"

Linked EPS bearer identity 5 SS re-uses the
EPS bearer
identity of the
default EPS
bearer context.

EPS QoS According to reference
dedicated EPS bearer
context #1 - see [18]

TFT According to reference
context #1- see [18]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1577 Release 9
1577
Table 10.2.1.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT (step 4, Table
10.2.1.3.2-1)
EPS bearer identity 6 Same value as in
ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST

transaction
identity assigned"

10.3 EPS bearer context modification
10.3.1 EPS bearer context modification / Success
(1)
with { the UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode }
ensure that {
when { the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message with new TFT}
then { the UE sets the new TFT and then ransmits a MODIFY EPS BEARER CONTEXT ACCEPT }
}

6.4.3.2 and .4.3.3,.
[TS 24.301, clause 6.4.3.1]
The purpose of the EPS bearer context modification procedure is to modify an EPS bearer context with a specific QoS
and TFT. The EPS bearer context modification procedure is initiated by the network, but it may also be initiated as part
of the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure.

[TS 24.301, clause 6.4.3.2]
The MME shall initiate the EPS bearer context modification procedure by sending a MODIFY EPS BEARER
CONTEXT REQUEST message to the UE, starting the timer T3486, and entering the state BEARER CONTEXT
MODIFY PENDING (see example in figure 6.4.3.2.1).
The MME shall include an EPS bearer identity that identifies the EPS bearer context to be modified in the MODIFY
EPS BEARER CONTEXT REQUEST message.
[TS 24.301, clause 6.4.3.3]
Upon receipt of the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall first check the received
TFT before taking it into use and then send a MODIFY EPS BEARER CONTEXT ACCEPT message to the MME.
If the PTI is included in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE uses the PTI to identify
the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to
which the EPS bearer context modification is related (see subclause 6.5.3 and subclause 6.5.4).
If the PTI is included in the MODIFY EPS BEARER CONTEXT REQUEST message and the PTI is associated to a UE
requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the UE shall
release the traffic flow aggregate description associated to the PTI value provided.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1578 Release 9
1578
Upon receipt of the MODIFY EPS BEARER CONTEXT ACCEPT message, the MME shall stop the timer T3486 and
enter the state BEARER CONTEXT ACTIVE.
System Simulator:
UE:
None.
Preamble:
- The UE is in Loopback Activated(state 4) with Reference default EPS bearer context #1 and Reference dedicated
EPS bearer context #1 according to [18] on Cell A.

U - S Message
1 The SS transmits a MODIFY EPS BEARER
CONTEXT REQUEST message with new TFT.
This message is included in a
CONTEXT REQUEST
- -
2 Check: Does the UE transmit a MODIFY EPS
BEARER CONTEXT ACCEPT message as
specified?
CONTEXT ACCEPT
1 P
3 Void - - - -
4 The SS transmits one IP Packet matching with
new TFT (reference packet filter #3) but not
existing uplink packet filters (reference packet
filter #2).
- - - -
5 Check: Does UE send the IP Packet on the
data radio bearer associated with the
dedicated EPS bearer context?
- - 1 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1579 Release 9
1579
Table 10.3.1.3.3-1: Message MODIFY EPS BEARER CONTEXT REQUEST (step 1, Table 10.3.1.3.2-1)
Derivation path: 36.508 table 4.7.3-16 and table 4.6.1-3
EPS bearer identity 6 SS assigns the
current dedicated
EPS bearer
context.

transaction
identity assigned"

context #2 except for TFT
operation code - see [18]
SS modifies the
current packet
filters of the
dedicated EPS
bearer context.

TFT operation code Replace packet filters in
existing TFT

Table 10.3.1.3.3-2: Message MODIFY EPS BEARER CONTEXT ACCEPT (step 2, Table 10.3.1.3.2-1)
MODIFY EPS
BEARER
CONTEXT
REQUEST

transaction
identity assigned"

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1580 Release 9
1580
Table 10.3.1.3.3-2: IP packet (step 4, Table 10.3.1.3.2-1)
Derivation path: IETF RFC 791 section 3.1 (IPv4) or RFC 2460 section 3 (IPv6) and RFC 769 introduction
Protocol 17 UDP

Same value as
reference packet
filter #2.
Reference packet
filter #3 can match
all values of
'Protocol'

Source Address remoteIPv4 Same value as in
reference packet
filters#2 and #3

remoteIPv6 Same value as in
reference packet
filters#2 and #3
IPv6-only
Destination Address remoteIPv4 Same value as in
reference packet
filters#2 and #3

remoteIPv6 Same value as in
reference packet
filters #2 and #3
IPv6-only
Source Port 60000 Not significant for
IP packet
classification

Destination Port 60000 Value does not
match with
reference packet
filter #2.
Reference packet
filter #3 can match
all values of
"Destination port"

Table 10.3.1.3.3-3: Condition for IP packet contents (step 4, Table 10.3.1.3.2-1)
IPv6-only This condition applies if the UE have transmitted a PDN
CONNECTIVITY REQUEST message in the preamble with PDN type
set to 'IPv6'.

10.4 EPS bearer context deactivation
10.4.1 EPS bearer context deactivation / Success
(1)
with { UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode }
ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message }
then { UE deletes the EPS bearer context identified by the EPS bearer identity and transmits a
DEACTIVATE EPS BEARER CONTEXT ACCEPT }
}
(2)
ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message indicating the EPS bearer
identity of the default bearer to a PDN }
then { UE deletes all EPS bearer contexts identified to the PDN and transmits a DEACTIVATE EPS
BEARER CONTEXT ACCEPT }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1581 Release 9
1581
}
(3)
ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message that does not point to an
existing EPS bearer context }
then { UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT with EPS bearer identity set to the
received EPS bearer identity }
}
(4)
with { UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-IDLE mode }
ensure that {
when { UE initiates an EMM-IDLE to EMM-CONNECTED transition (i.e. SERVICE REQUEST, TRACKING AREA
UPDATE REQUEST) }
then { UE only synchronises EPS bearer context state(s) which are explicitly activated by SS in
signalling messages }
}

5.5.3.2.4, 5.6.1.4, 6.4.4.3 and 6.4.4.6.
[TS 24.301, clause 6.4.4.2]

When the MME wants to deactivate all EPS bearer contexts to a PDN and thus disconnect the UE from the PDN, the
MME shall include the EPS bearer identity of the default bearer associated to the PDN in the DEACTIVATE EPS
If no NAS signalling connection exists when the MME initiates the EPS bearer context deactivation, the ESM entity in
the MME shall locally deactivate the EPS bearer context towards the UE without any peer-to-peer ESM signalling
between the MME and the UE.
NOTE: The EPS bearer context state(s) can be synchronized between the UE and the MME at the next EMM-
IDLE to EMM-CONNECTED transition, e.g. during a service request or tracking area updating
procedure.
[TS 24.301, clause 5.6.1.4]
...
The UE shall locally deactivate the EPS bearer contexts that do not have a user plane radio bearer established after the
successful completion of the service request procedure.
...
[TS 24.301, clause 5.5.3.2.4]

If an EPS bearer context status IE is included in the TRACKING AREA UPDATE REQUEST message, the MME shall
deactivate all those EPS bearer contexts locally (without peer-to-peer signalling between the MME and the UE) which
are active on the network side, but are indicated by the UE as being inactive. If a default EPS bearer context is marked
as inactive in the EPS bearer context status IE included in the TRACKING AREA UPDATE REQUEST message, and
this defaut bearer is not associated with the last PDN of the user in the MME, the MME shall locally deactivate all EPS
bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM
signalling to the UE.
If the EPS bearer context status IE is included in the TRACKING AREA UPDATE REQUEST, the MME shall include
an EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message, indicating which EPS bearer
contexts are active in the MME.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1582 Release 9
1582
If an EPS bearer context status IE is included in the TRACKING AREA UPDATE ACCEPT message, the UE shall
deactivate all those EPS bearers contexts locally (without peer-to-peer signalling between the UE and the MME) which
are active in the UE, but are indicated by the MME as being inactive.

[TS 24.301, clause 6.4.4.3]
Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall delete the EPS bearer
context identified by the EPS bearer identity. After deactivating the identified EPS bearer context, the UE shall respond
to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT.
If the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST is that of the default
bearer to a PDN, the UE shall delete all EPS bearer contexts associated to the PDN. After deactivating all EPS bearer
contexts, the UE shall respond to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT.
Upon sending the DEACTIVATE EPS BEARER CONTEXT ACCEPT message, the UE shall enter the state BEARER
CONTEXT INACTIVE
If the PTI is included in the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE uses the PTI to
identify the UE requested bearer resource modification procedure or UE requested PDN disconnect procedure to which
the EPS bearer context deactivation is related (see subclause 6.5.4).
If the PTI is included in the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall release the
traffic flow aggregate description associated to the PTI value provided.
...
[TS 24.301, clause 7.3.2]

The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen EPS bearer identity
received in the header of an ESM message:
i) If the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message which includes an
unassigned or reserved EPS bearer identity value or an assigned EPS bearer identity value that does not match an
existing EPS bearer context, the UE shall respond with a DEACTIVATE EPS BEARER CONTEXT ACCEPT
message with the EPS bearer identity set to the received EPS bearer identity.

[TS 24.301, clause 6.4.4.6]
The UE and the MME deactivate EPS bearer contexts locally without peer-to-peer ESM signalling in the following
cases:
1) during the service request procedure, if the E-UTRAN fails to establish the user plane radio bearers for one or
more EPS bearer contexts e.g. due to radio access control;
For those cases, based on the indication from the lower layers, the UE and the MME shall locally deactivate the EPS
bearer contexts for which no user plane radio bearers are set up.

When the user plane radio bearer for a default EPS bearer context is not established during the service request
procedure or tracking area updating procedure with "active" flag, the UE shall locally deactivate all EPS bearer contexts
associated to the PDN connection with the default EPS bearer context. The MME shall locally deactivate all EPS bearer
contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to
the UE.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1583 Release 9
1583
System Simulator:
- Cell A and Cell B are configured according to Table 6.3.2.2-1 in [18].
- Cell A, Cell B (home PLMN, different TAs).
UE:
None.

Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18] on Cell 1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1584 Release 9
1584
U S Message
- Cell A is the serving cell
Cell B is a suitable cell
- - - -
additional PDN (see Note 1)
- - - -
1A The UE transmits a SERVICE REQUEST --> SERVICE REQUEST - -
1B The SS establishes SRB2 and DRB
associated with default EPS bearer context
obtained during the attach procedure.
- - - -
2 The UE transmits a PDN CONNECTIVITY
REQUEST message as specified to request an
additional PDN.
--> PDN CONNECTIVITY REQUEST - -
3 The SS transmits an ACTIVATE DEFAULT
message with IE EPS Bearer Identity set to
new EPS bearer context.

Note: the SS allocates a PDN address of a
PDN type which is compliant with the PDN
type requested by the UE.
<-- ACTIVATE DEFAULT EPS
- -
4 The UE transmits an ACTIVATE DEFAULT
as specified.
--> ACTIVATE DEFAULT EPS
- -
EPS BEARER CONTEXT REQUEST relative
to the additional PDN.

Note: the same PDN address is applicable
because the linked EPS bearer ID refers to the
default EBC allocated in step 3.
- -
as specified.
- -
using S-TMSI with CN domain indicator set to
''PS.
<-- - - -
9 The UE transmits the SERVICE REQUEST
message
9A The SS establishes SRB2 and DRBs
associated with two default EPS bearer
context (a first PDN obtained during the attach
procedure and an additional PDN).
- - - -
BEARER CONTEXT REQUEST including the
EPS bearer identity of the dedicated EPS
bearer to the additional PDN.
CONTEXT REQUEST
- -
11 Check: Does the UE transmit a DEACTIVATE
EPS BEARER CONTEXT ACCEPT?
CONTEXT ACCEPT
1 P

- -
as specified.
- -
EPS bearer identity of the default EPS bearer
CONTEXT REQUEST
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1585 Release 9
1585
(see Note 3)
CONTEXT ACCEPT
2 P
CONTEXT REQUEST message including the
bearer. This message is included in a
CONTEXT REQUEST
- -
17 Check: Does UE transmits a MODIFY EPS
BEARER CONTEXT REJ ECT message with
ESM cause #43? (see Note 4)
CONTEXT REJ ECT
2 P
BEARER CONTEXT REQUEST that does not
point an existing EPS bearer context.
CONTEXT REQUEST
- -
CONTEXT ACCEPT
3 P
additional PDN (see note 1)
- - - -
21
A
The UE transmits a SERVICE REQUEST --> SERVICE REQUEST - -
21
B
The SS establishes SRB2 and DRBs
- - - -
additional PDN.
- -
24 The UE transmit an ACTIVATE DEFAULT
as specified.
- -
to additional PDN.

- -
26 The UE transmit an ACTIVATE DEDICATED
as specified.
- -
using S-TMSI with CN domain indicator set to
''PS.
<-- - - -
29 The UE transmits SERVICE REQUEST
message
30 The SS performs a radio bearer establishment
procedure. (Note 2)

The RRCConnectionReconfiguration message
doesnt include the EPS bearer ID of the
additional PDN.
- - - -
31 Check: Does UE transmit a
message? (Note 2)
- - 4 P
to the additional PDN. This message is
included in a DLInformationTransfer message.
CONTEXT REQUEST
- -
32
A
Check: Does UE transmits a MODIFY EPS
CONTEXT REJ ECT
4 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1586 Release 9
1586
ESM cause #43?(see Note 3)

32
B
The SS transmits a MODIFY EPS BEARER
bearer.
CONTEXT REQUEST
- -
32
C

CONTEXT REJ ECT
4 P
additional PDN (see note 1)
- - - -
34
A
The UE transmits a SERVICE REQUEST --> SERVICE REQUEST - -
34
B
The SS establishes SRB2 and DRB
obtained during the attach procedure
- - - -
additional PDN.

Note: SS allocates a PDN address of a PDN
type which is compliant with the PDN type
- -
as specified.
- -
to additional PDN.

- -
as specified.
- -
41 Cell A is a suitable cell
Cell B is the serving cell
- - - -
42 The UE transmit a TRACKING AREA UPDATE
REQUEST message as specified on Cell B.
REQUEST

UPDATE ACCEPT indicating only one EPS
bearer (default EBId-1) active in the EPS
bearer context status IE.

Note:
The EPS bearer ID linked to the additional
PDN is deactivated by SS.
ACCEPT
- -
43
AA
The UE transmits TRACKING AREA UPDATE
COMPLETE message
COMPLETE
- -
43
AB
The SS establishes SRB2 - - - -
43
A
to the additional PDN. This message is
CONTEXT REQUEST
- -
43
B
ESM cause #43?(see Note 3)

CONTEXT REJ ECT
4 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1587 Release 9
1587
43
C
bearer. This message is included in a
CONTEXT REQUEST
- -
43
D

CONTEXT REJ ECT
4 P
45 Cause the UE to request bearer resource
allocation of dedicated EPS bearer associated
with additional PDN connectivity.
- - - -
46 Check: Does the UE transmit SERVICE
REQUEST?
Note 1: The request of connectivity to an additional PDN and the sending of data may be performed by MMI or AT
command.
Note 2: After a correct SERVICE REQUEST is received then the SS performs the Radio Bearer Establishment
procedure. The UE transmission of the RRCConnectionReconfigurationComplete message indicates the
completion of the radio bearer establishment procedure and that the UE has changed EMM mode from
EMM-IDLE to EMM-CONNECTED.
Note 3: It can be confirmed that the additional default EPS bearer has been deactivated by UE.
Note 4: It can be confirmed that the dedicated EPS bearer has been deactivated by UE.

Table 10.4.1.3.3-1: Message PDN CONNECTIVITY REQUEST (step 2, 22 and 35, Table 10.4.1.3.2-1)
EPS bearer identity 0000 No EPS bearer
identity assigned

Procedure transaction identity PTI-1 UE assigns a
particular PTI not
yet used between
1 and 254

ESM information transfer flag Not present This IE is only
used during an
attach procedure.

Access point name APN-1 (New PDN name) The requested
PDN is different
from default PDN

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1588 Release 9
1588
Table 10.4.1.3.3-2: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 3, 23 and
36, Table 10.4.1.3.2-1)
EPS bearer identity 6 SS assigns an
additional EPS
Bearer Id different
from default EPS
Bearer Id between
5 and 15.

Procedure transaction identity PTI-1 SS re-uses the
particular PTI
defined by UE for
this present
additional PDN
connectivity
request
procedure.

Access point name APN-1 SS re-uses the
particular APN
defined by UE for
this present
additional PDN
connectivity
request procedure

Table 10.4.1.3.3-3: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 4, 24 and 37,
Table 10.4.1.3.2-1)
ACTIVATE
DEFAULT EPS
BEARER
CONTEXT
REQUEST

Procedure transaction identity 0 No procedure
transaction
identity assigned

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1589 Release 9
1589
Table 10.4.1.3.3-4: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 5, 12,
25 and 38, Table 10.4.1.3.2-1)
EPS bearer identity 7 SS assigns a
dedicated bearer
Id different from
default EBId and
additional EBId
and between 5
and 15.

transaction
identity assigned

Linked EPS bearer identity Default EBId-2 (same
value like in table
10.4.1.3.3-2)

SS defines an
additional
dedicated EPS
QoS


Table 10.4.1.3.3-5: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT (step 6, 13, 26
and 39, Table 10.4.1.3.2-1)
ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST in step
5

transaction
identity assigned

Table 10.4.1.3.3-6: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 10, Table
10.4.1.3.2-1)
Derivation path: 36.508 table 4.7.3-12 and table 4.6.1-8 with condition DRB-REL(3)
ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST of step
5

transaction
identity assigned

ESM cause 00100100 regular
deactivation

Protocol configuration options Not present

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1590 Release 9
1590
Table 10.4.1.3.3-7: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 11, Table
10.4.1.3.2-1)
ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST of step
5

transaction
identity assigned

10.4.1.3.2-1)
EPS bearer identity Default EBId-2 Same value as in
ACTIVATE
DEFAULT EPS
BEARER
CONTEXT
REQUEST of step
3

transaction
identity assigned

deactivation


10.4.1.3.2-1)
ACTIVATE
DEFAULT EPS
BEARER
CONTEXT
REQUEST of step
3

transaction
identity assigned

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1591 Release 9
1591
Table 10.4.1.3.3-9b: Message MODIFY EPS BEARER CONTEXT REQUEST (step 16, Table 10.4.1.3.2-1)
EPS bearer identity 7 Dedicated EPS
bearer context
which should have
been deactivated

transaction
identity assigned"

SS modifies the
current packet
filters of the
dedicated EPS
bearer context.

TFT operation code Replace packet filters in
existing TFT

10.4.1.3.2-1)
EPS bearer identity 6 This value does
not refer to an
existing EPS
bearer

transaction
identity assigned

deactivation


10.4.1.3.2-1)
DEACTIVATE
EPS BEARER
CONTEXT
REQUEST of step
16

transaction
identity assigned

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1592 Release 9
1592
Table 10.4.1.3.3-11a: Message RRCConnectionReconfiguration (step 30, Table 10. 4.1.3.2-1)
Derivation path: 36.508 table 4.6.1-8 with condition SRB2-DRB(0, 1)

Table 10.4.1.3.3-12: Message MODIFY EPS BEARER CONTEXT REQUEST (step 32 and 43A, Table
10.4.1.3.2-1)
additional default
EPS bearer
context which isnt
present.

transaction
identity assigned

Table 10.4.1.3.3-13: Message MODIFY EPS BEARER CONTEXT REJECT (step 32A and 43B, Table
10.4.1.3.2-1)
MODIFY EPS
BEARER
CONTEXT
REQUEST

transaction
identity assigned

ESM cause 00101011 invalid EPS
bearer identity

Table 10.4.1.3.3-14: Message MODIFY EPS BEARER CONTEXT REQUEST (step 16, 32B and 43C,
Table 10.4.1.3.2-1)
dedicated EPS
bearer context
which isnt
present.

transaction
identity assigned

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1593 Release 9
1593
Table 10.4.1.3.3-15: Message MODIFY EPS BEARER CONTEXT REJECT (step 17, 32C and 43D, Table
10.4.1.3.2-1)
MODIFY EPS
BEARER
CONTEXT
REQUEST

transaction
identity assigned

ESM cause 00101011 invalid EPS
bearer identity

Table 10.4.1.3.3-16: Message TRACKING AREA UPDATE REQUEST (step 42, Table 10.4.1.3.2-1)
EPS bearer context status optional This IE may be
present

EPS bearer context status IEI 57
Length of EPS bearer context status contents 2 2 octets
EBI(0)-EBI(4) 0
EBI(5)-EBI(7) 7 EPS bearer
contexts activated
in preamble, step
36 and step 38.

EBI(8)-EBI(15) 0

Table 10.4.1.3.3-17: Message TRACKING AREA UPDATE ACCEPT (step 43, Table 10.4.1.3.2-1)
EPS bearer context status present The SS
deactivates the
EPS bearer Id of
the additional
PDN given at step
30.

EBI(0)-EBI(4) 0
EBI(5-7) 1 EPS bearer
contexts activated
in preamble

EBI(8)-EBI(15) 0

10.5 UE requested PDN connectivity
10.5.1 UE requested PDN connectivity accepted by the network
(1)
with { UE in EMM-REGISTERED state and EMM-IDLE mode }
ensure that {
when { UE has uplink signalling pending }
sends a SERVICE REQUEST message }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1594 Release 9
1594
(2)
with { UE is in EMM-REGISTERED mode }
ensure that {
when { UE is triggered to request connectivity to an additional PDN }
then { the UE transmits a PDN CONNECTIVITY REQUEST message with the request type set to "initial
request" and including APN }
}
(3)
with { UE has sent a PDN CONNECTIVITY REQUEST message }
ensure that {
when { UE receives an RRCConnectionReconfiguration message including an ACTIVATE DEFAULT EPS
BEARER CONTEXT REQUEST message with IE Procedure transaction identity matching the PDN CONNECTIVITY
REQUEST message and an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message linked to the EPS
bearer context activated in the first message}
then { UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and an ACTIVATE
DEDICATED EPS BEARER CONTEXT ACCEPT message both containing the EPS bearer identity and enters EMM-
REGISTERED state }
}

5.6.1.1, 5.6.1.2, 5.6.1.4, 6.2.2, 6.4.1.3, 6.4.2.3, 6.5.1.2 and Annex D, and TS 25.331 clause 5.3.3.3.
[TS 24.301 clause 5.3.1.1]
...
[TS 24.301 clause 5.6.1.1]
...
c) the UE, in EMM-IDLE mode, has uplink signalling pending;
...
[TS 24.301 clause 5.6.1.2]
...
[TS 24.301 clause 5.6.1.4]
For cases a, b, c and h in subclause 5.6.1.1, the UE shall treat the indication from the lower layers that the user plane
radio bearer is set up as successful completion of the procedure. The UE shall stop the timer T3417 and enter the state
EMM-REGISTERED.
Upon successful completion of the procedure, the UE shall stop the timer T3417 and enter the state EMM-
REGISTERED.
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1595 Release 9
1595
...
Service Request If a SERVICE REQUEST is to request user plane radio
resources, the RRC establishment cause shall be set to MO
data. (See Note1)

"originating calls"

If a SERVICE REQUEST is to request resources for UL
signalling, the RRC establishment cause shall be set to MO
data. (See Note 1)

"originating calls"

If a SERVICE REQUEST is a response to paging where the CN
domain indicator is set to "PS", the RRC establishment cause
shall be set to MT access. (See Note 1)

"terminating calls"

If a EXTENDED SERVICE REQUEST has service type set to
"mobile originating CS fallback or 1xCS fallback", the RRC
establishment cause shall be set to MO data. (See Note1).

"originating calls"

"mobile terminating CS fallback or 1xCS fallback", the RRC
establishment cause shall be set to MT access. (See Note1).
"terminating calls"

"mobile originating CS fallback emergency call or 1xCS fallback
emergency call", the RRC establishment cause shall be set to
Emergency call.
(See Note1).
"emergency calls"

...
For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN (if the EHPLMN list is
not present or is empty) or EHPLMN (if the EHPLMN list is present), the RRC establishment cause will be
set to "High priority access AC 11 15".

[TS 36.331, clause 5.3.3.3]
2>else:
40
...
[TS 24.301, clause 6.2.2]
The UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message, based on its IP stack

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1596 Release 9
1596
- has been allocated an IPv4 address for this APN and received the ESM cause #52 "single address bearers
...
[TS 24.301, clause 6.4.1.3]
Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall send an
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT
ACTIVE. When the default bearer is activated as part of the attach procedure, the UE shall send the ACTIVATE
DEFAULT EPS BEARER CONTEXT ACCEPT message together with ATTACH COMPLETE message. When the
default bearer is activated as the response to the stand-alone PDN CONNECTIVITY REQUEST message, the UE shall
send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message alone.
The UE checks the PTI in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to identify the
UE requested PDN connectivity procedure to which the default bearer context activation is related (see subclause 6.5.1).
...
[TS 24.301, clause 6.4.2.3]
Upon receipt of the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall first
check the received TFT before taking it into use. Then the UE shall send an ACTIVATE DEDICATED EPS BEARER
CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. The ACTIVATE DEDICATED EPS
BEARER CONTEXT ACCEPT message shall include the EPS bearer identity.
If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message and the PTI is
associated to a UE requested bearer resource allocation procedure or a UE requested bearer resource modification
procedure, the UE shall release the traffic flow aggregate description associated to the PTI value provided.
...
[TS 24.301, clause 6.5.1.2]
...
In order to request connectivity to a PDN using the default APN, the UE includes the access point name IE in the PDN
CONNECTIVITY REQUEST message or, when applicable, in the ESM INFORMATION RESPONSE message,
according to the following conditions:
- if use of a PDN using the default APN requires PAP/CHAP, then the UE should include the access point name
IE; and
- in all other conditions, the UE need not include the access point name IE.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1597 Release 9
1597
In order to request connectivity to an additional PDN, the UE shall send a PDN CONNECTIVITY REQUEST message
including a requested APN to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION
PENDING (see example in figure 6.5.1.2.1). In the PDN type information element the UE shall indicate the IP version
capability of the IP stack associated with the UE as specified in subclause 6.4.1
...
System Simulator:
- Cell A
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18].10.5.1.3.2 Test procedure sequence
Table 10.5.1.3.2-1: Main Behaviour
U - S Message
additional PDN (see Note)
- - - -
1A Check: Does UE transmit an
establishmentCause set to mo-Data followed
by a SERVICE REQUEST message?
associated with default EPS bearer context (a
first PDN obtained during the attach
procedure).
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1598 Release 9
1598
2 Check: Does the UE transmit a PDN
specified to request an additional PDN?
--> PDN CONNECTIVITY REQUEST 2 P
new EPS bearer context and ACTIVATE
REQUEST message with IE Linked EPS
bearer identity set to the new EPS bearer
context..

Note:
CONTEXT REQUEST and ACTIVATE
REQUEST are included in
dedicatedInfoNASList of


ACTIVATE DEDICATED EPS
- -
10.5.1.3.2-2 is taking place

message for the additional default EPS
Bearer?
3 P
5-6 Void - - - -
Note: The request of connectivity to an additional PDN may be performed by MMI or AT command.

Table 10.5.1.3.2-2: Parallel behaviour
U - S Message
ACCEPT message for the dedicated EPS
Bearer?
3 P

Table 10.5.1.3.3-0: Message RRCConnectionRequest (step 1a, Table 10.5.1.3.2-1)
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1599 Release 9
1599
Table 10.5.1.3.3-1: Message PDN CONNECTIVITY REQUEST (step 2, Table 10.5.1.3.2-1)
identity assigned

particular PTI not
yet used between
1 and 254

used during an
attach procedure.

Access point name APN-1(New PDN name) The requested
PDN is different
from default PDN

Table 10.5.1.3.3-1a: Message RRCConnectionReconfiguration (step 3, Table 10.5.1.3.2-1)
Derivation path: 36.508 table 4.6.1-8 using condition DRB(2,0)
c1 CHOICE{
dedicatedInfoNASList SEQUENCE { 2 entries
dedicatedInfoNAS[1] See table 10.5.1.3.3-2
dedicatedInfoNAS[2] See table 10.5.1.3.3-3
}
}
}
}
}

Table 10.5.1.3.3-2: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 3, Table
10.5.1.3.2-1)
particular PTI
defined by UE for
this present
additional PDN
connectivity
request
procedure.

particular APN
defined by UE for
this present
additional PDN
connectivity
request procedure

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1600 Release 9
1600
10.5.1.3.2-1)
transaction
identity assigned

Linked EPS bearer identity 6
SS defines an
additional
dedicated EPS
QoS


Table 10.5.1.3.3-4: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 4, Table
10.5.1.3.2-1)
transaction
identity assigned

10.5.1.3.2-2)
transaction
identity assigned

10.5.2 Void
10.5.3 UE requested PDN connectivity not accepted
(1)
with { the UE has sent a PDN CONNECTIVITY REQUEST message to an additional PDN }
ensure that {
when { the UE receives an PDN CONNECTIVITY REJECT message with PTI matching the PDN CONNECTIVITY
REQUEST message and including a ESM cause value }
then { the UE enters the state PROCEDURE TRANSACTION INACTIVE }
}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.2.2, 6.4.1.3,
6.4.2.3 and 6.5.1.2.
[TS 24.301, clause 6.2.2]
The UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message, based on its IP stack

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1601 Release 9
1601
...
[TS 24.301, clause 6.5.1.2]
...
In order to request connectivity to an additional PDN, the UE shall send a PDN CONNECTIVITY REQUEST message
including a requested APN to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION
PENDING (see example in figure 6.5.1.2.1). In the PDN type information element the UE shall indicate the IP version
capability of the IP stack associated with the UE as specified in subclause 6.4.1
...
[TS 24.301, clause 6.5.1.4]
...
Upon receipt of the PDN CONNECTIVITY REJ ECT message, the UE shall stop timer T3482 and enter the state
PROCEDURE TRANSACTION INACTIVE.
The PDN CONNECTIVITY REJ ECT message contains an ESM cause IE that typically indicates one of the following
ESM cause values:
#8: operator determined barring;
#26: insufficient resources;
#27: missing or unknown APN;
#28: unknown PDN type;
#29: user authentication failed;
#30: request rejected by Serving GW or PDN GW;
#31: request rejected, unspecified;
#32: service option not supported;
#33: requested service option not subscribed;
#34: service option temporarily out of order;
#35: PTI already in use;
#38: network failure;
#50: PDN type IPv4 only allowed;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1602 Release 9
1602
#51: PDN type IPv6 only allowed;
#53: ESM information not received;
#54: PDN connection does not exist;
#55: multiple PDN connections for a given APN not allowed;
#95 111: protocol errors;
#112: APN restriction value incompatible with active EPS bearer context.
System Simulator:
- Cell A.
UE:
None.

Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18] (1 default EPS bearer context is active).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1603 Release 9
1603
U - S Message
- - - -
- - - -
additional PDN.
3 The SS transmits a PDN CONNECTIVITY
REJ ECT message.
<-- PDN CONNECTIVITY REJ ECT - -
4 Void - - - -
5 Void - - - -
- - - -
message.
9 The SS establishes a DRB associated with the
default EPS bearer context activated during
the preamble.
- - - -
9A Check: Does the UE transmit a PDN
CONNECTIVITY REQUEST as specified to
request an additional PDN?
--> PDN CONNECTIVITY REQUEST 1 P
9B The SS transmits an ACTIVATE DEFAULT

Note:
CONTEXT REQUEST is included in
dedicatedInfoNASList of
- -
message for the additional default EPS
bearer?
1 P
Note: The trigger in step 1 and the RRC messages in steps 1A to 2 and in steps 8 to 10 are the same as in the
generic procedure in 36.508 clause 6.4.3.2. The request of connectivity to an additional PDN may be
performed by MMI or AT command.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1604 Release 9
1604
Table 10.5.3.3.3-1: Message PDN CONNECTIVITY REQUEST (step 2, table 10.5.3.3.2-1)
identity assigned

particular PTI not
yet used between
1 and 254

activable during
an attach
procedure.

Access point name APN-1(New PDN name) The requested
PDN is different
from default PDN

Table 10.5.3.3.3-2: Message PDN CONNECTIVITY REJECT (step 3, table 10.5.3.3.2-1)
identity assigned

Procedure transaction identity PTI-1 The SS indicates
the same value
like received in
the PDN
CONNECTIVITY
REQUEST

ESM cause 01101111 Protocol error,
unspecified


Table 10.5.3.3.3-3: Void
Table 10.5.3.3.3-4: Message PDN CONNECTIVITY REQUEST (step 9A, table 10.5.3.3.2-1)
identity assigned

particular PTI not
yet used between
1 and 254 (may
be identical to
PTI-1)

activable during
an attach
procedure.

Access point name APN-2 (New PDN name) The requested
PDN is different
from default PDN
(may be identical
to APN-1)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1605 Release 9
1605
Table 10.5.3.3.3-5: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 9B, table
10.5.3.3.2-1)
Derivation Path: TS 36.508 Table 4.7.3-6 and table 4.6.1-8 with condition AM-DRB-ADD(2)
particular PTI
defined by UE for
this present
additional PDN
connectivity
request
procedure.

particular APN
defined by UE for
this present
additional PDN
connectivity
request procedure

Table 10.5.3.3.3-6: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 10, table
10.5.3.3.2-1)
ACTIVATE
DEFAULT EPS
BEARER
CONTEXT
REQUEST

transaction
identity assigned"

10.6 UE requested PDN disconnect
10.6.1 UE requested PDN disconnect procedure accepted by the network
(1)
with { UE is in BEARER CONTEXT ACTIVE STATE state }
ensure that {
when { UE is triggered to disconnect from a PDN }
then { UE sends a PDN DISCONNECT REQUEST message including the default EPS bearer identity
associated with this PDN }
}
(2)
with { UE is in PROCEDURE TRANSACTION PENDING state }
ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message with any valid ESM cause }
then { UE deactivates the default EPS bearer context for this PDN connection between the UE and
the SS }

}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.5.2.2, and
6.5.2.4.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1606 Release 9
1606
[TS 24.301, clause 6.5.2.2]
In order to request PDN disconnection from a PDN, the UE shall send a PDN DISCONNECT REQUEST message to
the MME, start the timer T3492 and enter the state PROCEDURE TRANSACTION PENDING (see example in
figure 6.5.2.2.1). The PDN DISCONNECT REQUEST message shall include the EPS bearer identity of the default
bearer associated with the PDN to disconnect from as the linked EPS bearer identity in the PDN DISCONNECT
REQUEST message.
[TS 24.301, clause 6.5.2.3]
...
Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall stop the timer T3492
and enter the state PROCEDURE TRANSACTION INACTIVE. The behaviour of the UE is described in
subclause 6.4.4.
...
[TS 24.301, clause 6.4.4.2]
If a NAS signalling connection exists when the MME initiates the EPS bearer context deactivation procedure, the MME
shall initiate the EPS bearer context deactivation procedure by sending a DEACTIVATE EPS BEARER CONTEXT
REQUEST message to the UE, start the timer T3495, and enter the state BEARER CONTEXT INACTIVE PENDING
(see example in figure 6.4.4.2.1). The DEACTIVATE EPS BEARER CONTEXT REQUEST message contains an ESM
cause typically indicating one of the following:
#8: operator determined barring;
#36: regular deactivation;
#38: network failure; or
#112: APN restriction value incompatible with active EPS bearer context.
The procedure transaction identity (PTI) shall also be included if the deactivation is triggered by a UE initiated bearer
resource modification procedure or UE requested PDN disconnect procedure.
...
System Simulator:
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18] on Cell A.
- Two default EPS bearer context are activated and present on UE side (a first PDN obtained during the attach

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1607 Release 9
1607
U - S Message
1 Cause the UE to request disconnection from
the additional PDN (see Note 1)
- - - -
1B The SS establishes SRB2 and DRBs
- - - -
2 Check: Does the UE transmit a PDN
DISCONNECT REQUEST message as
specified (to disconnect from the additional
PDN)?
--> PDN DISCONNECT REQUEST 1 P
BEARER CONTEXT REQUEST message
included in an RRCConnectionReconfiguration
message.
CONTEXT REQUEST
- -
4 The UE transmits a DEACTIVATE EPS
BEARER CONTEXT ACCEPT message.
CONTEXT ACCEPT
2 P
5 Void - - - -
5A The SS releases the RRC connection. - - - -
Note 1: The request to disconnect from a PDN may be performed by MMI or AT command.

Table 10.6.1.3.3-1: Message PDN DISCONNECT REQUEST (step 2, Table 10.6.1.3.2-1)
EPS bearer identity 0000 "no EPS bearer
identity assigned"

particular PTI not
yet used between
1 and 254


Table 10.6.1.3.3-1a: Message RRCConnectionReconfiguration (step 3, Table 10.6.1.3.2-1)
Derivation path: 36.508 table 4.6.1-8 using condition DRB-REL(2)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1608 Release 9
1608
10.6.1.3.2-1)
EPS bearer identity 6 SS re-uses the
EPS Bearer Id
defined by UE for
this present PDN
disconnection
procedure.

particular PTI
defined by UE for
this present PDN
disconnection
procedure.
UE-
INITIATED
ESM cause #36 regular
deactivation

Table 10.6.1.3.3-3: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 4, Table 10.6.1.3.2-
1)
EPS bearer identity 6 The same value
as the value set in
DEACTIVATE
EPS BEARER
CONTEXT
REQUEST
message.

transaction
identity assigned

10.6.2 UE requested PDN disconnect procedure not accepted by the
network
(1)
with { the UE is in PROCEDURE TRANSACTION PENDING state }
ensure that {
when { the UE receives a PDN DISCONNECT REJECT message with a cause #49:last PDN disconnection not
allowed }
then { the UE aborts the PDN disconnection procedure and does not deactivates the default EPS
bearer context for this PDN connection }

}

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.5.2.2, and
6.5.2.4.
[TS 24.301, clause 6.5.2.2]
In order to request PDN disconnection from a PDN, the UE shall send a PDN DISCONNECT REQUEST message to
the MME, start the timer T3492 and enter the state PROCEDURE TRANSACTION PENDING (see example in
figure 6.5.2.2.1). The PDN DISCONNECT REQUEST message shall include the EPS bearer identity of the default
bearer associated with the PDN to disconnect from as the linked EPS bearer identity in the PDN DISCONNECT
REQUEST message.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1609 Release 9
1609

[TS 24.301, clause 6.5.2.4]
Upon receipt of the PDN DISCONNECT REQUEST message, if it is not accepted by the network, the MME shall send
a PDN DISCONNECT REJ ECT message to the UE. The PDN DISCONNECT REJ ECT message shall contain the PTI
and an ESM cause IE that typically indicates one of the following ESM cause values:
#43: invalid EPS bearer identity;
#49: last PDN disconnection not allowed;
#95 111: protocol errors.
Upon receipt of the PDN DISCONNECT REJ ECT message, the UE shall stop the timer T3492, enter the state
PROCEDURE TRANSACTION INACTIVE and abort the PDN disconnection procedure. Additionally, in all cases
with the exception of the UE having received ESM cause #49 "last PDN disconnection not allowed", the UE shall
deactivate all EPS bearer contexts for this PDN connection locally without peer-to-peer signalling between the UE and
the MME.
System Simulator:
- Cell A
UE:
None.
Preamble:
- The UE is in state Registered, Idle mode (state 2) according to [18] on Cell A.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1610 Release 9
1610
U - S Message
1 Cause the UE to request PDN disconnection
from the default PDN (see note 1)
- - - -
- EXCEPTION: steps 2a1 to 2b2 describe two
alternative behaviours allowed for the UE.
- - - -
2a1 IF the UE transmits a SERVICE REQUEST
within the next 10s, THEN all steps until step
2a4 are executed.
2a2 The SS establishes the DRB associated with
the default EPS bearer context activated
during the preamble.
- - - -
2a3 The UE transmits a PDN DISCONNECT
REQUEST message for the default PDN
connection.
--> PDN DISCONNECT REQUEST - -
2a4 The SS transmits a PDN DISCONNECT
REJ ECT message with cause #49 last PDN
disconnection not allowed.
<-- PDN DISCONNECT REJ ECT - -
2b1 ELSE, the SS pages the UE. - - - -
2b2 The UE transmits a SERVICE REQUEST
message.
3 The SS tansmits an ACTIVATE DEDICATED
EPS BEARER CONTEXT REQUEST with a
linked EPS bearer ID referring to the default
EPS bearer context activated during the
preamble
- -
ACCEPT message? (see Note 2)
1 P
Note 1: The request of disconnection to a PDN and the sending of data may be performed by MMI or AT
command.
Note 2: This confirms that the additional default EPS bearer has not been deactivated by UE.

Table 10.6.2.3.3-1: Message PDN DISCONNECT REQUEST (step 2a3, table 10.6.2.3.2-1)
identity assigned"

particular PTI not
yet used between
1 and 254


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1611 Release 9
1611
Table 10.6.2.3.3-2: Message PDN DISCONNECT REJECT (step 2a4, table 10.6.2.3.2-1)
identity assigned"

particular PTI
defined by UE for
this present PDN
disconnection
procedure.

ESM cause #49 last PDN
disconnection not
allowed

Table 10.6.2.3.3-3: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 3, table
10.6.2.3.2-1)
transaction
identity assigned"

SS defines an
additional
dedicated EPS
QoS


10.6.2.3.2-1)
transaction
identity assigned"

10.7 UE requested bearer resource allocation
10.7.1 UE requested bearer resource allocation accepted by the network /
New EPS bearer context
(1)
with { UE in PROCEDURE TRANSACTION INACTIVE state and in EMM-IDLE mode }
ensure that {
when { UE is requested to allocate of bearer resource }
then { UE sends a BEARER RESOURCE ALLOCATION REQUEST message }
}

(2)
with { UE has sent the BEARER RESOURCE ALLOCATION REQUEST message }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1612 Release 9
1612
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with the procedure
transaction identity (PTI) indicated in the BEARER RESOURCE ALLOCATION REQUEST message }
then { UE sends an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }
}

6.5.3.3.
[TS 24.301, clause 6.5.3.2]
In order to request the allocation of bearer resources for one traffic flow aggregate, the UE shall send a BEARER
RESOURCE ALLOCATION REQUEST message to the MME, start timer T3480 and enter the state PROCEDURE
TRANSACTION PENDING (see example in figure 6.5.3.2.1).
The UE shall include the EPS bearer identity of the default EPS bearer associated with the requested bearer resource in
the Linked EPS bearer identity IE. The UE shall set the TFT operation code in the Traffic flow aggregate IE to "Create
new TFT". In the Required traffic flow QoS IE, the UE shall indicate a QCI and, if the UE also includes a GBR, the
additional GBR required for the traffic flow aggregate.
...
[TS 24.301, clause 6.5.3.3]
...
If the bearer resource allocation requested is accepted by the network, the MME shall initiate either a dedicated EPS
bearer context activation procedure or an EPS bearer context modification procedure. Upon receipt of an ACTIVATE
DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST with a PTI
which matches the value used for the BEARER RESOURCE ALLOCATION REQUEST, the UE shall stop timer
T3480 and enter the state PROCEDURE TRANSACTION INACTIVE.
If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST is received, the UE shall verify that the EPS
bearer identity given in the EPS bearer identity IE is not already used by any dedicated EPS bearer contexts associated
with the included linked EPS bearer identity. The UE shall then proceed as described in subclause 6.4.2.3 or subclause
6.4.2.4.
...
System Simulator:
- Cell A
UE:
None.
Preamble:
- A default EPS bearer is established between the first PDN and the UE.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1613 Release 9
1613
U - S Message
with first PDN connectivity. (see Note)
- - - -
message.
- - - -
3 Check: Does the UE transmit a BEARER
RESOURCE ALLOCATION REQUEST
message?
--> BEARER RESOURCE
ALLOCATION REQUEST
1 P
message.
- -
ACCEPT message?
2 P
Note: The trigger in step 1 and the RRC messages in steps 2 to 5 are the same as in the generic procedure in
36.508 clause 6.4.3.1.

Table 10.7.1.3.3-1: Message BEARER RESOURCE ALLOCATION REQUEST (step 3, Table 10.7.1.3.2-1)
Derivation path: 36.508 table 4.7.3-6B

10.7.1.3.2-1)
Derivation path: 36.508 table 4.7.3-3, condition UE-INITIATED and table 4.6.1-8 with condition AM-DRB-ADD(2)

10.7.2 UE requested bearer resource allocation accepted by the network /
Existing EPS bearer context
(1)
with { UE in PROCEDURE TRANSACTION INACTIVE state and in EMM-IDLE mode }
ensure that {
when { UE is requested to allocate of bearer resource }
then { UE sends a BEARER RESOURCE ALLOCATION REQUEST message }
}

(2)
with { UE has sent a BEARER RESOURCE ALLOCATION REQUEST message }
ensure that {
when { UE receives a MODIFY EPS BEARER CONTEXT REQUEST message with the procedure transaction
identity (PTI) indicated in the BEARER RESOURCE ALLOCATION REQUEST message }
then { UE sends a MODIFY EPS BEARER CONTEXT ACCEPT message }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1614 Release 9
1614
6.5.3.3.
[TS 24.301, clause 6.5.3.2]
The UE shall include the EPS bearer identity of the default EPS bearer associated with the requested bearer resource in
the Linked EPS bearer identity IE. The UE shall set the TFT operation code in the Traffic flow aggregate IE to "Create
new TFT". In the Required traffic flow QoS IE, the UE shall indicate a QCI and, if the UE also includes a GBR, the
additional GBR required for the traffic flow aggregate.
...

[TS 24.301, clause 6.5.3.3]
...
If the bearer resource allocation requested is accepted by the network, the MME shall initiate either a dedicated EPS
bearer context activation procedure or an EPS bearer context modification procedure. Upon receipt of an ACTIVATE
DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST with a PTI
which matches the value used for the BEARER RESOURCE ALLOCATION REQUEST, the UE shall stop timer
T3480 and enter the state PROCEDURE TRANSACTION INACTIVE.
...
If the MODIFY EPS BEARER CONTEXT REQUEST is received, the UE verifies that the EPS bearer identity given in
the EPS bearer identity IE is any of the active EPS bearer contexts. The UE shall then proceed as described in subclause
6.4.3.3 or subclause 6.4.3.4.
System Simulator:
- Cell A
UE:
None.
Preamble:
- A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.
U - S Message

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1615 Release 9
1615
with first PDN connectivity.(see Note)
- - - -
message.
2A The SS establishes SRB2 and DRBs
and a dedicated bearer context (a first PDN
- - - -
message?
--> BEARER RESOURCE
ALLOCATION REQUEST
1 P
CONTEXT REQUEST message. This
message is included in a
CONTEXT REQUEST
- -
BEARER CONTEXT ACCEPT message?
CONTEXT ACCEPT
2 P
36.508 clause 6.4.3.1.


Derivation path: 36.508 table 4.7.3-18, condition UE-INITIATED
New EPS QoS According to reference

SS modifies the
current packet
filters of the
dedicated EPS
bearer context.

TFT operation code '011'B Add packet filters
to existing TFT

10.7.3 UE requested bearer resource allocation not accepted by the
network
(1)
with { UE has sent the BEARER RESOURCE ALLOCATION REQUEST message }
ensure that {
when { UE receives a BEARER RESOURCE ALLOCATION REJECT message with the procedure transaction
identity (PTI) indicated in the BEARER RESOURCE ALLOCATION REQUEST message and a cause Protocol
error, unspecified }
then { UE enters state PROCEDURE TRANSACTION INACTIVE }
}

7.3.1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1616 Release 9
1616
[TS 24.301, clause 6.5.3.4]
If the bearer resource allocation requested cannot be accepted by the network, the MME shall send a BEARER
RESOURCE ALLOCATION REJ ECT message to the UE. The message shall contain the PTI and an ESM cause value
indicating the reason for rejecting the UE requested bearer resource allocation.
The ESM cause value typically indicates one of the following:
#37: EPS QoS not accepted;
#41: semantic error in the TFT operation;
#42: syntactical error in the TFT operation;
#44: semantic error(s) in packet filter(s);
#45: syntactical error(s) in packet filter(s);
#56: collision with network initiated request;
#59: unsupported QCI value; or
...
Upon receipt of a BEARER RESOURCE ALLOCATION REJ ECT message, the UE shall stop the timer T3480, release
the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE TRANSACTION
INACTIVE.
The further actions to be performed by the UE are implementation dependent as part of upper layers responsibility.
[TS 24.301, clause 7.3.1]
...
The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in an ESM
message:
...
h) If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message in which the
PTI value is an assigned value that does not match any PTI in use, the UE shall respond with an ACTIVATE
DEDICATED EPS BEARER CONTEXT REJ ECT message including ESM cause #47 "PTI mismatch".
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1617 Release 9
1617
System Simulator:
- Cell A
UE:
None.
Preamble:
U - S Message
- - - -
message.
- - - -
3 The UE transmits a BEARER RESOURCE
ALLOCATION REQUEST message.
--> BEARER RESOURCE
ALLOCATION REQUEST
- -
4 The SS transmits a BEARER RESOURCE
ALLOCATION REJ ECT message.
<-- BEARER RESOURCE
ALLOCATION REJ ECT
- -
message.
- -
REJ ECT message?
BEARER CONTEXT REJ ECT
1 P
36.508 clause 6.4.3.1.


Table 10.7.3.3.3-2: Message BEARER RESOURCE ALLOCATION REJECT (step 4, Table 10.7.3.3.2-1)
Derivation path: 36.508 table 4.7.3-6A
ESM cause 0110 1111B Protocol error,
unspecified

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1618 Release 9
1618
10.7.3.3.2-1)
Derivation path: 36.508 table 4.7.3-3 and table 4.6.1-8 with condition AM-DRB-ADD(2)
Procedure transaction identity The same value as the
value set in BEARER
RESOURCE
ALLOCATION
REQUEST message in
step 3.


Table 10.7.3.3.3-4: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT (step 6, Table
10.7.3.3.2-1)
ESM cause 0010 1111B PTI mismatch

10.7.4 UE requested bearer resource allocation / Expiry of timer T3480
(1)
with { UE has sent a BEARER RESOURCE ALLOCATION REQUEST message }
ensure that {
when { UE detects less than fifth expiry of timer T3480 }
then { UE re-sends a BEARER RESOURCE ALLOCATION REQUEST message }
}

(2)
with { UE has sent the BEARER RESOURCE ALLOCATION REQUEST message 5 times }
ensure that {
when { UE detects fifth expiry of timer T3480 }
then { UE does not re-send a BEARER RESOURCE ALLOCATION REQUEST message }
}

6.5.3.5.
[TS 24.301, clause 6.5.3.2]
...
[TS 24.301, clause 6.5.3.5]
a) Expiry of timer T3480:
On the first expiry of the timer T3480, the UE shall resend the BEARER RESOURCE ALLOCATION
REQUEST and shall reset and restart timer T3480. This retransmission is repeated four times, i.e. on the fifth
expiry of timer T3480, the UE shall abort the procedure, release the PTI allocated for this activation and enter
the state PROCEDURE TRANSACTION INACTIVE.
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1619 Release 9
1619
System Simulator:
- Cell A
UE:
None.
Preamble:
U - S Message
- - - -
message.
- - - -
--> BEARER RESOURCE
ALLOCATION REQUEST
- -
4 Wait for 8 s to ensure that T3480 expires (1
st

expiry).
- - - -
5 Check: Does the UE re-transmit a BEARER
message?
--> BEARER RESOURCE
ALLOCATION REQUEST
1 P
nd

expiry).
- - - -
message?
--> BEARER RESOURCE
ALLOCATION REQUEST
1 P
rd

expiry).
- - - -
message?
--> BEARER RESOURCE
ALLOCATION REQUEST
1 P
th

expiry).
- - - -
message?
--> BEARER RESOURCE
ALLOCATION REQUEST
1 P
th

expiry).
- - - -
message?
--> BEARER RESOURCE
ALLOCATION REQUEST
2 F
36.508 clause 6.4.3.1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1620 Release 9
1620
Table 10.7.4.3.3-1: Message BEARER RESOURCE ALLOCATION REQUEST (step 3,5,7,9,11, Table
10.7.4.3.2-1)

10.7.5 UE requested bearer resource allocation / BEARER RESOURCE
ALLOCATION REJ ECT message including cause #43 "invalid EPS
bearer identity"
(1)
with { UE has sent the BEARER RESOURCE ALLOCATION REQUEST message in order to establish dedicated
EPS bearer between the additional PDN and the UE }
ensure that {
when { UE receives a BEARER RESOURCE ALLOCATION REJECT message with the procedure transaction
identity (PTI) indicated in the BEARER RESOURCE ALLOCATION REQUEST message and a cause invalid EPS
bearer identity }
then { UE deactivates the EPS bearer context(s) corresponding to the additional PDN locally }
}

6.5.1.3, 6.5.3.4 and 6.5.3.5.
[TS 24.301, clause 6.5.1.1]
The purpose of the UE requested PDN connectivity procedure is for a UE to request the setup of a default EPS bearer to
a PDN. The UE requests connectivity to a PDN by sending a PDN CONNECTIVITY REQUEST message to the
network. If accepted by the network, this procedure initiates the establishment of a default EPS bearer context. The
procedure is used either to establish the first default bearer by including the PDN CONNECTIVITY REQUEST
message into the initial attach message, or to establish subsequent default bearers to additional PDNs in order to allow
the UE simultaneous access to multiple PDNs by sending the message stand-alone.
[TS 24.301, clause 6.5.1.3]
...
If connectivity with the requested PDN is accepted by the network, the MME shall initiate the default EPS bearer
context activation procedure (see subclause 6.4.1).
...
[TS 24.301, clause 6.5.3.4]
If the bearer resource allocation requested cannot be accepted by the network, the MME shall send a BEARER
RESOURCE ALLOCATION REJ ECT message to the UE. The message shall contain the PTI and an ESM cause value
indicating the reason for rejecting the UE requested bearer resource allocation.
...
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1621 Release 9
1621
Upon receipt of a BEARER RESOURCE ALLOCATION REJ ECT message, the UE shall stop the timer T3480, release
the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE TRANSACTION
INACTIVE.
[TS 24.301, clause 6.5.3.5]
...
b) Unknown EPS bearer context
Upon receipt of the BEARER RESOURCE ALLOCATION REJ ECT message including ESM cause #43
"invalid EPS bearer identity", the UE shall deactivate the existing default EPS bearer context locally without
peer-to-peer signalling between the UE and the MME.
System Simulator:
- Cell A
UE:
None.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1622 Release 9
1622
U - S Message
additional PDN.(see Note 1)
- - - -
message.
- - - -
REQUEST message.
message.
- -
- -
with additional PDN connectivity. (see Note 2)
- - - -
--> BEARER RESOURCE
ALLOCATION REQUEST
- -
ALLOCATION REJ ECT message.
<-- BEARER RESOURCE
ALLOCATION REJ ECT
- -
message.
- -
REJ ECT message?
1 P
Note 1: The trigger in step 1 and the RRC messages in steps 2 to 5 are the same as in the generic procedure in
36.508 clause 6.4.3.2.
Note 2: The trigger in step 6 and the RRC messages in steps 7 to 10 are the same as in the generic procedure in
36.508 clause 6.4.3.1.

Table 10.7.5.3.3-1: Message PDN CONNECTIVITY REQUEST (step 3, Table 10.7.5.3.2-1)
ESM information transfer flag Not present
Access point name Arbitrary name different from first
PDN

Table 10.7.5.3.3-2: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 4, Table
10.7.5.3.2-1)

Table 10.7.5.3.3-3: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 5, Table
10.7.5.3.2-1)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1623 Release 9
1623

Table 10.7.5.3.3-5: Message BEARER RESOURCE ALLOCATION REJECT (step 8, Table 10.7.5.3.2-1)
ESM cause 0010 1011B Invalid EPS
bearer identity

10.7.5.3.2-1)
Derivation path: 36.508 table 4.7.3-3 with condition NETWORK-INITIATED and table 4.6.1-8 with condition AM-DRB-
ADD(3)

10.7.5.3.2-1)
ESM cause 0010 1011B invalid EPS
bearer identity

10.8 UE requested bearer resource modification
10.8.1 UE requested bearer resource modification accepted by the network
/ New EPS bearer context
(1)
with { UE in PROCEDURE TRANSACTION INACTIVE state and in EMM-CONNECTED mode }
ensure that {
when { UE is requested to modify of bearer resource corresponding to the dedicated bearer }
then { UE sends a BEARER RESOURCE MODIFICATION REQUEST message }
}
(2)
with { UE having sent the BEARER RESOURCE MODIFICATION REQUEST message }
ensure that {
when { UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with the procedure
transaction identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message }
then { UE sends an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }
}

6.5.4.2 and 6.5.4.3.
[TS 24.301, clause 6.4.2.3]
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1624 Release 9
1624
...
[TS 24.301, clause 6.5.4.2]
In order to request the modification of bearer resources for one traffic flow aggregate, the UE shall send a BEARER
RESOURCE MODIFICATION REQUEST message to the MME, start timer T3481 and enter the state PROCEDURE
...
[TS 24.301, clause 6.5.4.3]
Upon receipt of the BEARER RESOURCE MODIFICATION REQUEST message, the MME checks whether the
resources requested by the UE can be established, modified or released by verifying the EPS bearer identity given in the
EPS bearer identity for packet filter IE.
If the bearer resource modification requested is accepted by the network, the MME shall initiate either a dedicated EPS
bearer context activation procedure, an EPS bearer context modification procedure or an EPS bearer context
deactivation procedure.
Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER
CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST with a PTI which matches the value
used for the BEARER RESOURCE MODIFICATION REQUEST, the UE shall stop timer T3481 and enter the state
PROCEDURE TRANSACTION INACTIVE.
i) If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST is received, the UE shall verify that the
EPS bearer identity given in the EPS bearer identity IE is not already used by any dedicated EPS bearer contexts
associated with the included linked EPS bearer identity. The UE shall then proceed as described in
subclause 6.4.2.3 or subclause 6.4.2.4.
...
System Simulator:
- Cell A
UE:
None.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1625 Release 9
1625
U - S Message
modification of dedicated EPS bearer
associated with first PDN connectivity.(see
Note)
- - - -
RESOURCE MODIFICATION REQUEST
message?
--> BEARER RESOURCE
MODIFICATION REQUEST
1 P
message.
- -
ACCEPT message?
-->
ACTIVATE DEDICATED EPS
2 P
36.508 clause 6.4.3.3.

10.8.1.3.2-1)
Derivation path: 36.508 table 4.7.3-3, condition UE-INITIATED and table 4.6.1-8 with condition AM-DRB-ADD(3)


10.8.2 UE requested bearer resource modification accepted by the network
/ Existing EPS bearer context
(1)
ensure that {
when { UE is requested to modify of bearer resource corresponding to the dedicated bearer }
then { UE sends a BEARER RESOURCE MODIFICATION REQUEST message }
}
(2)
ensure that {
when { UE receives a MODIFY EPS BEARER CONTEXT REQUEST message with the procedure transaction
identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message }
then { UE sends a MODIFY EPS BEARER CONTEXT ACCEPT message }
}

6.5.4.3 and 6.4.3.3.
[TS 24.301, clause 6.5.4.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1626 Release 9
1626
In order to request the modification of bearer resources for one traffic flow aggregate, the UE shall send a BEARER
RESOURCE MODIFICATION REQUEST message to the MME, start timer T3481 and enter the state PROCEDURE
TRANSACTION PENDING (see example in figure 6.5. 4.2.1).
...
[TS 24.301, clause 6.5.4.3]
CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST message with a PTI which matches
the value used for the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall stop timer T3481
and enter the state PROCEDURE TRANSACTION INACTIVE.
...
ii) If the MODIFY EPS BEARER CONTEXT REQUEST message is received, the UE verifies that the EPS bearer
identity given in the EPS bearer identity IE is any of the active EPS bearer contexts. The UE shall then proceed
as described in subclause 6.4.3.3 or subclause 6.4.3.4.
...
[TS 24.301, clause 6.4.3.3]
...
If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure
transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]), the UE uses the PTI to identify the UE
requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the
EPS bearer context modification is related (see subclause 6.5.3 and subclause 6.5.4).
If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure
transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]) and the PTI is associated to a UE requested
bearer resource allocation procedure or a UE requested bearer resource modification procedure, the UE shall release the
traffic flow aggregate description associated to the PTI value provided.
...
System Simulator:
- Cell A
UE:
None
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1627 Release 9
1627
U - S Message
Note)
- - - -
message?
--> BEARER RESOURCE
1 P
CONTEXT REQUEST
- -
BEARER CONTEXT ACCEPT message?
CONTEXT ACCEPT
2 P
36.508 clause 6.4.3.3.

Table 10.8.2.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, Table 10.8.2.3.2-
1)
EPS bearer identity for packet filter 6

Derivation path: 36.508 table 4.7.3-18, condition UE-INITIATED


TFT operation code 100B Replace packet
filters in existing
TFT

10.8.3 UE requested bearer resource modification not accepted by the
network
(1)
with { UE has sent the BEARER RESOURCE MODIFICATION REQUEST message }
ensure that {
when { UE receives a BEARER RESOURCE MODIFICATION REJECT message with the procedure transaction
identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message and a cause Protocol
error, unspecified }
then { UE enters state PROCEDURE TRANSACTION INACTIVE }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1628 Release 9
1628
7.3.1.
[TS 24.301, clause 6.5.4.4]
If the bearer resource modification requested cannot be accepted by the network, the MME shall send a BEARER
RESOURCE MODIFICATION REJ ECT message to the UE. The message shall contain the PTI and an ESM cause
value indicating the reason for rejecting the UE requested bearer resource modification.
#37: EPS QoS not accepted;
#41: semantic error in the TFT operation;
#42: syntactical error in the TFT operation;
#44: semantic error(s) in packet filter(s);
#45: syntactical error(s) in packet filter(s);
#56: collision with network initiated request;
#59: unsupported QCI value; or
...
Upon receipt of a BEARER RESOURCE MODIFICATION REJ ECT message, the UE shall stop the timer T3481,
release the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE
TRANSACTION INACTIVE. If the ESM cause included in the BEARER RESOURCE MODIFICATION REJ ECT
message is #43 "invalid EPS bearer identity", the UE locally deactivates the EPS bearer context(s) without peer-to-peer
ESM signalling.
...
[TS 24.301, clause 7.3.1]
...
The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in an ESM
message:
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1629 Release 9
1629
h) If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message in which the
PTI value is an assigned value that does not match any PTI in use, the UE shall respond with an ACTIVATE
DEDICATED EPS BEARER CONTEXT REJ ECT message including ESM cause #47 "PTI mismatch".
...
System Simulator:
- Cell A
UE:
None.
Preamble:
U - S Message
Note)
- - - -
MODIFICATION REQUEST message.
--> BEARER RESOURCE
- -
MODIFICATION REJ ECT message.
<-- BEARER RESOURCE
MODIFICATION REJ ECT
- -
message.
- -
REJ ECT message?
1 P
36.508 clause 6.4.3.3.

1)

Table 10.8.3.3.3-2: Message BEARER RESOURCE MODIFICATION REJECT (step 3, Table 10.8.3.3.2-1)
ESM cause 0110 1111B Protocol error,
unspecified

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1630 Release 9
1630
10.8.3.3.2-1)
value set in BEARER
RESOURCE
MODIFICATION
REQUEST message in
step 2.



10.8.3.3.2-1)
ESM cause 0010 1111B PTI mismatch

10.8.4 UE requested bearer resource modification / Cause #36 "regular
deactivation"
(1)
ensure that {
when { UE is requested to release of bearer resources corresponding to the dedicated bearer }
then { UE sends a BEARER RESOURCE MODIFICATION REQUEST message with a cause regular
deactivation }
}
(2)
ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message with the procedure transaction
identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message and the EPS bearer
identity pointing an existing EPS bearer context }
then { UE deactivates the EPS bearer context identified by the EPS bearer identity indicated in
the DEACTIVATE EPS BEARER CONTEXT REQUEST message and sends a DEACTIVATE EPS BEARER CONTEXT ACCEPT
message }
}

6.4.4.3 and 7.3.2.
[TS 24.301, clause 6.5.4.3]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1631 Release 9
1631
CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST message with a PTI which matches
the value used for the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall stop timer T3481
and enter the state PROCEDURE TRANSACTION INACTIVE.
...
iii) If the DEACTIVATE EPS BEARER CONTEXT REQUEST message is received, the UE verifies that the EPS
bearer identity given in the EPS bearer identity IE is any of the active EPS bearer contexts associated with the
included linked EPS bearer identity The UE shall then proceed as described in subclause 6.4.4.3.
...
[TS 24.301, clause 6.4.4.3]
Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall delete the EPS bearer
context identified by the EPS bearer identity. After deactivating the identified EPS bearer context, the UE shall respond
to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT.
...
Upon sending the DEACTIVATE EPS BEARER CONTEXT ACCEPT message, the UE shall enter the state BEARER
CONTEXT INACTIVE
If the DEACTIVATE EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure
transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]), the UE uses the PTI to identify the UE
requested bearer resource modification procedure or UE requested PDN disconnect procedure to which the EPS bearer
context deactivation is related (see subclause 6.5.4).
If the DEACTIVATE EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure
transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]), the UE shall release the traffic flow aggregate
description associated to the PTI value provided.
...
[TS 24.301, clause 7.3.2]
...
...
i) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which includes an unassigned or
reserved EPS bearer identity value or an assigned EPS bearer identity value that does not match an existing EPS
bearer context, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including
ESM cause #43 "invalid EPS bearer identity".
...
System Simulator:
- Cell A
UE:
None.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1632 Release 9
1632
Preamble:
U - S Message
release of dedicated EPS bearer associated
with first PDN connectivity (see Note).
- - - -
message?
--> BEARER RESOURCE
1 P
CONTEXT REQUEST
- -
CONTEXT ACCEPT
2 P
CONTEXT REQUEST
- -
BEARER CONTEXT REJ ECT message?
CONTEXT REJ ECT
2 P
Note: The trigger in step 1 and the RRC messages in steps 2 to 4 are the same as in the generic procedure in 36.508
clause 6.4.3.4.

1)
Derivation path: 36.508 table 4.7.3-8, condition RELEASE-REQUESTED
ESM cause 0010 0100B Regular
deactivation

10.8.4.3.2-1)
Derivation path: 36.508 table 4.7.3-12, condition UE-INITIATED and table 4.6.1-8 with condition DRB-REL(2)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1633 Release 9
1633
Derivation path: 36.508 table 4.7.3-18, condition NETWORK-INITIATED


filters in existing
TFT

Table 10.8.4.3.3-4: Message MODIFY EPS BEARER CONTEXT REJECT (step 6, Table 10.8.4.3.2-1)
bearer identity

10.8.5 UE requested bearer resource modification / BEARER RESOURCE
MODIFICATION REJ ECT message including cause #43 "invalid
EPS bearer identity"
(1)
with { UE has sent the BEARER RESOURCE MODIFICATION REQUEST message }
ensure that {
when { UE receives a BEARER RESOURCE MODIFICATION REJECT message with the procedure transaction
identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message and a cause invalid
EPS bearer identity }
then { UE deactivates the EPS bearer context identified by the EPS bearer identity indicated in
the BEARER RESOURCE MODIFICATION REQUEST message }
}

6.5.4.5 and 7.3.2.
[TS 24.301, clause 6.5.4.4]
If the bearer resource modification requested cannot be accepted by the network, the MME shall send a BEARER
RESOURCE MODIFICATION REJ ECT message to the UE. The message shall contain the PTI and an ESM cause
value indicating the reason for rejecting the UE requested bearer resource modification.
...
...
Upon receipt of a BEARER RESOURCE MODIFICATION REJ ECT message, the UE shall stop the timer T3481,
release the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE
TRANSACTION INACTIVE. If the ESM cause included in the BEARER RESOURCE MODIFICATION REJ ECT
message is #43 "invalid EPS bearer identity", the UE locally deactivates the EPS bearer context(s) without peer-to-peer
ESM signalling.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1634 Release 9
1634
[TS 24.301, clause 6.5.4.5]
...
b) Unknown EPS bearer context
Upon receipt of the BEARER RESOURCE MODIFICATION REJ ECT message including ESM cause #43
"invalid EPS bearer identity", the UE shall deactivate the existing EPS bearer context locally without peer-to-
peer signalling between the UE and the MME.
...
[TS 24.301, clause 7.3.2]
...
...
h) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which includes an unassigned or
...
System Simulator:
- Cell A
UE:
None.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1635 Release 9
1635
U - S Message
Note)
- - - -
--> BEARER RESOURCE
- -
MODIFICATION REJ ECT message.
<-- BEARER RESOURCE
MODIFICATION REJ ECT
- -
CONTEXT REQUEST
- -
CONTEXT REJ ECT
1 P
36.508 clause 6.4.3.3.

1)

Table 10.8.5.3.3-2: Message BEARER RESOURCE MODIFICATION REJECT (step 3, Table 10.8.5.3.2-1)
bearer identity

value set in BEARER
RESOURCE
MODIFICATION
REQUEST message in
step 2.



filters in existing
TFT

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1636 Release 9
1636
bearer identity

10.8.6 UE requested bearer resource modification / Collision of a UE
requested bearer resource modification procedure and EPS bearer
context deactivation procedure
(1)
ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message with an unassigned PTI value
and the EPS bearer identity indicated in the BEARER RESOURCE MODIFICATION REQUEST message }
then { UE aborts the UE requested bearer resource modification procedure and deactivates the EPS
bearer context identified by the EPS bearer identity indicated in DEACTIVATE EPS BEARER CONTEXT
REQUEST message and sends a DEACTIVATE EPS BEARER CONTEXT ACCEPT message }
}

7.3.2.
[TS 24.301, clause 6.5.4.5]
...
c) Collision of a UE requested bearer resource modification procedure and an EPS bearer context deactivation
procedure.
When the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message during the bearer
resource modification procedure, and the EPS bearer identity indicated in the DEACTIVATE EPS BEARER
CONTEXT REQUEST message is a EPS bearer context the UE indicated in the UE requested bearer resource
modification procedure, then the UE shall abort the UE requested bearer resource modification procedure and
proceed with the EPS bearer context deactivation procedure.
[TS 24.301, clause 7.3.2]
...
...
i) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which includes an unassigned or
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1637 Release 9
1637
System Simulator:
- Cell A
UE:
None.
Preamble:
U - S Message
Note)
- - - -
--> BEARER RESOURCE
- -
CONTEXT REQUEST
- -
CONTEXT ACCEPT
1 P
CONTEXT REQUEST
- -
CONTEXT REJ ECT
1 P
36.508 clause 6.4.3.4.

1)

10.8.6.3.2-1)
Derivation path: 36.508 table 4.7.3-12, condition NETWORK-INITIATED and table 4.6.1-8 with condition DRB-REL(2)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1638 Release 9
1638
Derivation path: 36.508 table 4.7.3-18, condition NETWORK-INITIATED


filters in existing
TFT

bearer identity

10.8.7 UE requested bearer resource modification / Expiry of timer T3481
(1)
with { UE has sent a BEARER RESOURCE MODIFICATION REQUEST message }
ensure that {
when { UE detects less than fifth expiry of timer T3481 }
then { UE re-sends a BEARER RESOURCE MODIFICATION REQUEST message }
}

(2)
with { UE is in EMM-REGISTERED.NO-CELL-AVAILABLE state and has deactivated the EPS bearer context
without peer-to-peer signalling between the UE and the MME }
ensure that {
when { UE receives indication of "back to E-UTRAN coverage" from the lower layers }
then { UE sends TRACKING AREA UPDATE REQUEST message }
}

6.5.4.5.
[TS 24.301, clause 5.5.3.2.2]
...
f) when the UE deactivated EPS bearer context(s) locally while in EMM-REGISTERED.NO-CELL-AVAILABLE,
and then returns to EMM-REGISTERED.NORMAL-SERVICE;
...
[TS 24.301, clause 6.5.4.5]
a) Expiry of timer T3481:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1639 Release 9
1639
On the first expiry of the timer T3481, the UE shall resend the BEARER RESOURCE MODIFICATION
REQUEST and shall reset and restart timer T3481. This retransmission is repeated four times, i.e. on the fifth
expiry of timer T3481, the UE shall abort the procedure, release the PTI allocated for this activation and enter
the state PROCEDURE TRANSACTION INACTIVE. In addition, if the UE had initiated resource release for all
the traffic flows for the bearer, it shall deactivate the EPS bearer context locally without peer-to-peer signalling
between the UE and the MME. In order to synchronize the EPS bearer context status with the MME, on
indication of "back to E-UTRAN coverage" from the lower layers, the UE shall send a TRACKING AREA
UPDATE REQUEST message that includes the EPS bearer context status IE to the MME.
...
System Simulator:
- Cell A
UE:
None.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1640 Release 9
1640
U - S Message
release of dedicated EPS bearer associated
- - - -
--> BEARER RESOURCE
- -
st

expiry).
- - - -
message?
--> BEARER RESOURCE
1 P
nd

expiry).
- - - -
message?
--> BEARER RESOURCE
1 P
rd

expiry).
- - - -
message?
--> BEARER RESOURCE
1 P
th

expiry).
- - - -
message?
--> BEARER RESOURCE
1 P
11 Set the cell type of Cell A to the "Non-suitable
Off cell".
- - - -
th

expiry).
- - - -
13 Set the cell type of Cell A to the "Suitable cell". - - - -
REQUEST
2 P
ACCEPT
- -
COMPLETE
- -
36.508 clause 6.4.3.3.

Table 10.8.7.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, step 4, step 6,
step 8 and step 10, Table 10.8.7.3.2-1)
Derivation path: 36.508 table 4.7.3-8, condition RELEASE-REQUESTED

Table 10.8.7.3.3-2: Message TRACKING AREA UPDATE REQUEST (step 14, Table 10.8.7.3.2-1)
EPS bearer context status
EBI(0)-EBI(4) 0 0000B
EBI(5-7) 001B
EBI(8)-EBI(15) 0000 0000B

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1641 Release 9
1641
Table 10.8.7.3.3-3: Message TRACKING AREA UPDATE ACCEPT (step 15, Table 10.8.7.3.2-1)
EPS bearer context status
EBI(0)-EBI(4) 0 0000B
EBI(5-7) 001B
EBI(8)-EBI(15) 0000 0000B

10.9 UE routing of uplink packets
10.9.1 UE routing of uplinks packets
(1)
with { the UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode with a default EPS
bearer and two dedicated EPS bearers active }
ensure that {
when { the UE receives IP packets where each IP packet matches at least one of the different
packet filters configured in the UL TFTs for the dedicated EPS bearers }
then { the UE evaluates the packet filters in the correct evaluation order and transmits IP
packets in uplink on the dedicated EPS bearer associated with the matched packet filter }
}

(2)
ensure that {
when { the UE receives an IP packet where the IP header does not satisfy any of the configured
packet filters configured in the UL TFT for the dedicated EPS bearers AND no packet filter is
configured for the default EPS bearer }
then { the UE transmits the IP packet in uplink on the default EPS bearer }
}

(3)
ensure that {
when { the UE receives an IP packet where the IP header only satisfies a packet filter configured
in the UL TFT for the default EPS bearers }
then { the UE transmits the IP packet in uplink on the default EPS bearer }
}

(4)
ensure that {
when { the UE receives an IP packet where the IP header does not satisfy any of the configured
packet filters in the UL TFT configured for the default and dedicated EPS bearers }
then { the UE discards the IP packet }
}

[TS 24.008, clause 10.5.6.12]
The purpose of the traffic flow template information element is to specify the TFT parameters and operations for a PDP
context. In addition, this information element may be used to transfer extra parameters to the network (e.g. the
Authorization Token; see 3GPP TS 24.229 [95]). The TFT may contain packet filters for the downlink direction, the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1642 Release 9
1642
uplink direction or packet filters that apply for both directions. The packet filters determine the traffic mapping to PDP
contexts. The downlink packet filters shall be applied by the network and the uplink packet filters shall be applied by
the MS. A packet filter that applies for both directions shall be applied by the network as a downlink packet filter and
by the MS as an uplink filter.
The traffic flow template is a type 4 information element with a minimum length of 3 octets. The maximum length for
the IE is 257 octets.
NOTE 1: The IE length restriction is due to the maximum length that can be encoded in a single length octet.
NOTE 2: A maximum size IPv4 packet filter can be 32 bytes. Therefore, 7 maximum size IPv4 type packet filters,
plus the last packet filter which can contain max 30 octets can fit into one TFT, i.e. if needed not all
packet filter components can be defined into one message. A maximum size Ipv6 packet filter can be 60
bytes. Therefore, only 4 maximum size IPv6 packet filters can fit into one TFT. However, using "Add
packet filters to existing TFT", it's possible to create a TFT including 16 maximum size Ipv4 or IPv6
filters.
The traffic flow template information element is coded as shown in figure 10.5.144/3GPP TS 24.008 and table
10.5.162/3GPP TS 24.008.
8 7 6 5 4 3 2 1
Traffic flow template IEI Octet 1
Length of traffic flow template IE Octet 2
TFT operation code E bit Number of packet filters Octet 3

Packet filter list

Octet 4

Octet z

Parameters list

Octet z+1

Octet v
Figure 10.5.144/3GPP TS 24.008: Traffic flow template information element

8 7 6 5 4 3 2 1
Packet filter identifier 1 Octet 4

Packet filter identifier N Octet N+3
Figure 10.5.144a/3GPP TS 24.008: Packet filter list when the TFT operation is " delete packet filters
from existing TFT" (z=N+3)

8 7 6 5 4 3 2 1
Packet filter evaluation precedence 1 Octet 5
Length of Packet filter contents 1 Octet 6
Packet filter contents 1 Octet 7
Octet m
Packet filter identifier 2 Octet m+1
Packet filter evaluation precedence 2 Octet m+2
Length of Packet filter contents 2 Octet m+3
Packet filter contents 2 Octet m+4
Octet n
Octet n+1
Octet y
Packet filter identifier N Octet y+1
Packet filter evaluation precedence N Octet y+2
Length of Packet filter contents N Octet y+3
Packet filter contents N Octet y+4
Octet z
Figure 10.5.144b/3GPP TS 24.008: Packet filter list when the TFT operation is " create new TFT" , or
" add packet filters to existing TFT" or " replace packet filters in existing TFT"

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1643 Release 9
1643

8 7 6 5 4 3 2 1
Parameter identifier 1 Octet z+1
Length of Parameter contents 1 Octet z+2
Parameter contents 1 Octet z+3
Octet k
Parameter identifier 2 Octet k+1
Length of Parameter contents 2 Octet k+2
Parameter contents 2 Octet k+3
Octet p
Octet p+1
Octet q
Parameter identifier N Octet q+1
Length of Parameter contents N Octet q+2
Parameter contents N Octet q+3
Octet v
Figure 10.5.144c/3GPP TS 24.008: Parameters list

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1644 Release 9
1644
Table 10.5.162/3GPP TS 24.008: Traffic flow template information element

TFT operation code (octet 3)
Bits
8 7 6
0 0 0 Spare
0 0 1 Create new TFT
0 1 0 Delete existing TFT
0 1 1 Add packet filters to existing TFT
1 0 0 Replace packet filters in existing TFT
1 0 1 Delete packet filters from existing TFT
1 1 0 No TFT operation
1 1 1 Reserved
The TFT operation code "No TFT operation" shall be used if a parameters list is
included but no packet filter list is included in the traffic flow template information
element.

E bit (bit 5 of octet 3)
The E bit indicates if a parameters list is included in the TFT IE and it is encoded
as follows:
0 parameters list is not included
1 parameters list is included

Number of packet filters (octet 3)
The number of packet filters contains the binary coding for the number of packet
filters in the packet filter list. The number of packet filters field is encoded in bits 4
through 1 of octet 3 where bit 4 is the most significant and bit 1 is the least
significant bit. For the "delete existing TFT" operation and for the "no TFT
operation", the number of packet filters shall be coded as 0. For all other operations,
the number of packet filters shall be greater than 0 and less than or equal to 16.

Packet filter list (octets 4 to z)
The packet filter list contains a variable number of packet filters. For the "delete
existing TFT" operation and the "no TFT operation", the packet filter list shall be
empty.
For the "delete packet filters from existing TFT" operation, the packet filter list shall
contain a variable number of packet filter identifiers. This number shall be derived
from the coding of the number of packet filters field in octet 3.
For the "create new TFT", "add packet filters to existing TFT" and "replace packet
filters in existing TFT" operations, the packet filter list shall contain a variable
number of packet filters. This number shall be derived from the coding of the
number of packet filters field in octet 3.
Each packet filter is of variable length and consists of
- a packet filter identifier and direction (1 octet);
- a packet filter evaluation precedence (1 octet);
- the length of the packet filter contents (1 octet); and
- the packet filter contents itself (v octets).
The packet filter identifier field is used to identify each packet filter in a TFT. The
least significant 4 bits are used.
The packet filter direction is used to indicate, in bits 5 and 6, for what traffic direction

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1645 Release 9
1645
the filter applies:

00 - pre Rel-7 TFT filter
01 - downlink only
10 - uplink only
11 - bidirectional
Bits 8 through 7 are spare bits.
The packet filter evaluation precedence field is used to specify the precedence for
the packet filter among all packet filters in all TFTs associated with this PDP
address. Higher the value of the packet filter evaluation precedence field, lower the
precedence of that packet filter is. The first bit in transmission order is the most
significant bit.
The length of the packet filter contents field contains the binary coded
representation of the length of the packet filter contents field of a packet filter. The
first bit in transmission order is the most significant bit.
The packet filter contents field is of variable size and contains a variable number (at
least one) of packet filter components. Each packet filter component shall be
encoded as a sequence of a one octet packet filter component type identifier and a
fixed length packet filter component value field. The packet filter component type
identifier shall be transmitted first.
In each packet filter, there shall not be more than one occurrence of each packet
filter component type. Among the "IPv4 remote address type" and "IPv6 remote
address type" packet filter components, only one shall be present in one packet
filter. Among the "single local port type" and "local port range type" packet filter
components, only one shall be present in one packet filter. Among the "single
remote port type" and "remote port range type" packet filter components, only one
shall be present in one packet filter.
The term local refers to the MS and the term remote refers to an external network
entity.
Packet filter component type identifier
Bits
8 7 6 5 4 3 2 1
0 0 0 1 0 0 0 0 IPv4 remote address type
0 0 1 0 0 0 0 0 IPv6 remote address type
0 0 1 1 0 0 0 0 Protocol identifier/Next header type
0 1 0 0 0 0 0 0 Single local port type
0 1 0 0 0 0 0 1 Local port range type
0 1 0 1 0 0 0 0 Single remote port type
0 1 0 1 0 0 0 1 Remote port range type
0 1 1 0 0 0 0 0 Security parameter index type
0 1 1 1 0 0 0 0 Type of service/Traffic class type
1 0 0 0 0 0 0 0 Flow label type
All other values are reserved.
For "IPv4 remote address type", the packet filter component value field shall be
encoded as a sequence of a four octet IPv4 address field and a four octet IPv4
address mask field. The IPv4 address field shall be transmitted first.
For "IPv6 remote address type", the packet filter component value field shall be
encoded as a sequence of a sixteen octet IPv6 address field and a sixteen octet
IPv6 address mask field. The IPv6 address field shall be transmitted first.
For "Protocol identifier/Next header type", the packet filter component value field
shall be encoded as one octet which specifies the IPv4 protocol identifier or IPv6
next header.
For "Single local port type" and "Single remote port type", the packet filter
component value field shall be encoded as two octet which specifies a port number.
For "Local port range type" and "Remote port range type", the packet filter
component value field shall be encoded as a sequence of a two octet port range low

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1646 Release 9
1646
limit field and a two octet port range high limit field. The port range low limit field
shall be transmitted first.
For "Security parameter index", the packet filter component value field shall be
encoded as four octet which specifies the IPSec security parameter index.
For "Type of service/Traffic class type", the packet filter component value field shall
be encoded as a sequence of a one octet Type-of-Service/Traffic Class field and a
one octet Type-of-Service/Traffic Class mask field. The Type-of-Service/Traffic
Class field shall be transmitted first.
For "Flow label type", the packet filter component value field shall be encoded as
three octet which specifies the IPv6 flow label. The bits 8 through 5 of the first octet
shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label.
Parameters list (octets z+1 to v)
The parameters list contains a variable number of parameters that may be
transferred. If the parameters list is included, the E bit is set to 1; otherwise, the E bit
is set to 0.
Each parameter included in the parameters list is of variable length and consists of:
- a parameter identifier (1 octet);
- the length of the parameter contents (1 octet); and
- the parameter contents itself (v octets).
The parameter identifier field is used to identify each parameter included in the
parameters list and it contains the hexadecimal coding of the parameter identifier.
Bit 8 of the parameter identifier field contains the most significant bit and bit 1
contains the least significant bit. In this version of the protocol, the following
parameter identifiers are specified:
- 01H (Authorization Token);
- 02H (Flow Identifier) ; and
- 03H (Packet Filter Identifier).
If the parameters list contains a parameter identifier that is not supported by the
receiving entity the corresponding parameter shall be discarded.
The length of parameter contents field contains the binary coded representation of
the length of the parameter contents field. The first bit in transmission order is the
most significant bit.
When the parameter identifier indicates Authorization Token, the parameter
contents field contains an authorization token, as specified in 3GPP TS 29.207
[100]. The first octet is the most significant octet of the authorization token and the
last octet is the least significant octet of the authorization token.
The parameters list shall be coded in a way that an Authorization Token (i.e. a
parameter with identifier 01H) is always followed by one or more Flow Identifiers
(i.e. one or more parameters with identifier 02H).
If the parameters list contains two or more consecutive Authorization Tokens without
any Flow Identifiers in between, the receiver shall treat this as a semantical TFT
error.
When the parameter identifier indicates Flow Identifier, the parameter contents field
contains the binary representation of a flow identifier. The Flow Identifier consists of
four octets. Octets 1 and 2 contains the Media Component number as specified in
3GPP TS 29.207 [100]. Bit 1 of octet 2 is the least significant bit, and bit 8 of octet 1
is the most significant bit. Octets 3 and 4 contains the IP flow number as specified in
3GPP TS 29.207 [100]. Bit 1 of octet 4 is the least significant bit, and bit 8 of octet 3
is the most significant bit.
When the parameter identifier indicates Packet Filter Identifier, the parameter
contents field contains the binary representation of one or more packet filter
identifiers. Each packet filter identifier is encoded in one octet, in the 4 least
significant bits. This parameter is used by the MS to identify one or more packet
filters in a TFT when modifying the QoS of a PDP context without modifying the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1647 Release 9
1647
packet filter itself.

System Simulator:
UE:
- None.
Preamble:
- The UE is in Loopback Activated (state 4) with Reference default EPS bearer context #1 (DRB1) according to
[18] and two dedicated EPS bearers (DRB2 and DRB3) with EPS bearer context as specified as in ACTIVATE
DEDICATED EPS BEARER CONTEXT REQUEST message for DRB2 and DRB3 in subclause 10.9.1.3.3 on
Cell A.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 864 Release 9
864
Editors note: The content of the packet filters in Table 10.9.1.3.2-1 is FFS.
Table 10.9.1.3.2-1: Packet filters
Packet filter components
Packet
filter ID
UL TFT Packet filter
evaluation
precedence
Protocol
Number
(IPv4) /
Next
Header
(IPv6)

Remote
address and
Subnet mask

Single
Local
Port
(UE)
Local
Port
Range
(UE)

Single
Remote
Port
Range
(NW)
Remote
Port
Range
(NW)
IPSec SPI range Type of
Service
(IPv4) /
Traffic
Class
(IPv6)
and
Mask
Flow
Label
(IPv6)
Comments
1 DRB2 6 17
(UDP)
IPv4:
172.168.8.0
[255.255.255.0]
IPv6:
2001:0ba0::
[ffff:ffff::]
60001 - - - - - - TCP application identified by
source address and specific
local port number
2 DRB3 7 17
(UDP)
IPv4:
172.168.8.0
[255.255.255.0]
IPv6:
2001:0ba0::
[ffff:ffff::]
- 60000:
60100
- - - - - TCP application identified by
source address and range of
local port numbers
3 DRB2 2 17
(UDP)
- - - 60301 - - - - UDP application identified by
specific destination address
4 DRB3 3 17
(UDP)
- - - - 60300:
60400
- - - UDP application identified by
range of destination addresses
5 DRB3 5 50
IPSec
(ESP)
- - - - - 0x0F80F0000 - - IPSec session. Example from
TS 23.060 cl 15.3.3.3
6 DRB3 1 - - - - - - - 00101000,
Mask=
11111100
- TOS/TC-based filtering
7 DRB3 6 - - - - - - - - TBD IPv6 Flow Label filter
8 DRB1
(default
bearer)
255 6
(TCP)
- 60101 - - - - - - TCP application identified by
source address and specific
local port number

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 967 Release 9
967
Table 10.9.1.3.2-2: Sub-test test parameters and test requirements
Sub-test
Index
Test data
(IP packet)
Note 1
Expected DRB
associated with
the EPS bearer
context for the
matching
packet filter
Comment
Note 2
1 IP packet#1 DRB2 IP packet match Packet Filter 1 and 2
in Table 10.9.1.3.2-1. IP packet
returned on DRB2 as Packet Filter 1
is evaluated before Packet Filter 2.
2 IP packet#2 DRB3 IP packet is only matching Packet
Filter 2 in Table 10.9.1.3.2-1.
3 IP packet#3 DRB2 IP packet match Packet Filter 1, 2 and
3 in Table 10.9.1.3.2-1. IP packet is
is evaluated before Packet Filter 1
and 2.
4 IP packet#4 DRB3 IP packet match Packet Filter 1,2 and
4 in Table 10.9.1.3.2-1. IP packet is
is evaluated before Packet Filter 1
and 2.
8 IP packet#8 DRB1 (default
bearer)
IP packet does not match any of the
packet filters 1 to 7 in Table
10.9.1.3.2-1. As no TFT is assigned
to the default EPS bearer then shall
the UE send the IP packet on the
default EPS bearer (match all
packets).
9 IP packet#9 DRB1 (default
bearer)
IP packet is only matching Packet
10 IP packet#10 None IP packet does not match any Packet
Filters.
Note 1: IP Packet details are specified in Tables 10.9.1.3.3-5 to 10.9.1.3.3-14 in clause
10.9.1.3.3.
Note 2: IP packets for sub-test index 1 to 8 are sent by the SS while no TFT is assigned to
the default EPS bearer (associated by DRB1). IP packets for sub-test index 9 and
10 are sent by the SS after adding a TFT to the default EPS bearer.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 968 Release 9
968
U S Message
EXCEPTION: Test steps 1 to 2 are repeated
for N=1 to 7

1 The SS transmits one IP Packet according to
Table 10.9.1.3.2-2 for Sub-test index=N
- - - -
data radio bearer as specified by Table
10.9.1.3.2-2 for Sub-test index=N?
- - 1 P
Table 10.9.1.3.2-2 for Sub-test index=8
- - - -
10.9.1.3.2-2 for Sub-test index=8?
- - 2 P
CONTEXT REQUEST message to add TFT to
the default EPS bearer. This message is
CONTEXT REQUEST
- -
6 UE transmits a MODIFY EPS BEARER
CONTEXT ACCEPT message
CONTEXT ACCEPT
- -
- - - -
10.9.1.3.2-2 for Sub-test index=9?
- - 3 P
- - - -
10 Check: Does UE send an IP Packet on any of
the dedicated or default data radio bearers?
- - 4 F

Table 10.9.1.3.3-1: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (preamble,
DRB2)
FFS
Table 10.9.1.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (preamble,
DRB3)
FFS
Derivation path: 36.508 table 4.7.3-16 and table 4.6.1-3
EPS bearer identity The same value as the
value set in ACTIVATE
DEFAULT EPS BEARER
CONTEXT REQUEST
message
SS assigns the
current default
EPS bearer
context.

transaction
identity assigned"

TFT
TFT operation code Create new TFT
E bit 0
Packet filters Packet Filter 8, see Table
10.9.1.3.2-1
SS adds packet
filter to the default
EPS bearer
context.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 969 Release 9
969
Table 10.9.1.3.3-4: Message MODIFY EPS BEARER CONTEXT ACCEPT (step 6, Table 10.9.1.3.2-3)
EPS bearer identity The same value as the
value set in ACTIVATE
DEFAULT EPS BEARER
CONTEXT REQUEST
message
Same value as in
MODIFY EPS
BEARER
CONTEXT
REQUEST

transaction
identity assigned"

Table 10.9.1.3.3-5: IP packet#1 (Table 10.9.1.3.2-2)
FFS
FFS
FFS
FFS
FFS
FFS
FFS
FFS
FFS
FFS

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 970 Release 9
970
11 General tests
11.1 SMS over SGs
11.1.1 MT-SMS over SGs / Idle mode
(1)
with { UE is IMSI attached for non-EPS services and UE has received a paging request with CN domain
indicator set to "PS" in EMM-IDLE mode and UE has sent a SERVICE REQUEST message}
ensure that {
when { UE receives a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a
Downlink NAS transport message }
then { UE sends a CP-ACK encapsulated in an Uplink NAS transport message followed by a CP-DATA
containing an RP-ACK RPDU (SMS DELIVER REPORT TPDU) encapsulated in an Uplink NAS transport message}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.6.3.1,
5.6.3.3 and 9.9.3.22.

[TS 24.301, clause 5.6.3.1]
The purpose of the transport of NAS messages procedure is to carry SMS messages in an encapsulated form between
the MME and the UE. The procedure may be initiated by the UE or the network and can only be used when the UE is
attached for EPS services and IMSI attached for non-EPS services and is in EMM-CONNECTED mode.
[TS 24.301, clause 5.6.3.3]
The network initiates the procedure by sending a DOWNLINK NAS TRANSPORT message. When receiving the
DOWNLINK NAS TRANSPORT message, the EMM entity in the UE shall forward the contents of the NAS message
container IE to the SMS entity.
[TS 24.301, clause 9.9.3.22]
This information element is used to encapsulate the SMS messages transferred between the UE and the network. The
NAS message container information element is coded as shown in figure 9.9.3.22.1 and table 9.9.3.22.1.
The NAS message container is a type 4 information element with a minimum length of 4 octets and a maximum length
of 253 octets.
8 7 6 5 4 3 2 1
NAS message container IEI octet 1
Length of NAS message container contents octet 2

octet 3
NAS message container contents
octet n
Figure 9.9.3.22.1: NAS message container information element

Table 9.9.3.22.1: NAS message container information element
NAS message container contents (octet 3 to octet n)

This IE can contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as
defined in subclause 7.2 in 3GPP TS 24.011 [13A].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 971 Release 9
971
System Simulator:
- Cell A belongs TAI-1.
- Cell A is set to the ''Serving cell''.
UE:
- The UE does not have any stored SMS message.
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell A according to [18].
U - S Message
domain indicator set to ''PS'.
- - - -
message.
3 The SS transmits a CP-DATA containing an
RP-DATA RPDU (SMS DELIVER TPDU)
encapsulated in a Downlink NAS transport
message to the UE.
<-- DOWNLINK NAS TRANSPORT - -
4 Check: Does the UE transmit a CP-ACK
encapsulated in an Uplink NAS transport
message?
--> UPLINK NAS TRANSPORT 1 P
5 Check: Does the UE transmit a CP-DATA
containing an RP-ACK RPDU (SMS DELIVER
REPORT TPDU) encapsulated in an Uplink
NAS transport message?
6 The SS transmits a CP-ACK encapsulated in a
Downlink NAS transport message to the UE.

Table 11.1.1.3.3-1: Message DOWNLINK NAS TRANSPORT (step 3, Table 11.1.1.3.2-1)
NAS message container Set according to Table
11.1.1.3.3-2

Table 11.1.1.3.3-2: Message CP-DATA (step 3, Table 11.1.1.3.2-1)
Protocol discriminator 1001B SMS messages
Messsage type 00000001B CP-DATA
CP-User data Set according to Table
11.1.1.3.3-3

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 972 Release 9
972
Table 11.1.1.3.3-3: Message RP-DATA RPDU (step 3, Table 11.1.1.3.2-1)
RP-Message Type 001B RP-DATA_PDU
downlink

RP-Message Reference present
RP-Originator Address present 1-12 octets
RP-Destination Address present 1 octet
RP-User Data Set according to Table
11.1.1.3.3-4

Table 11.1.1.3.3-4: Message SMS DELIVER TPDU (step 3, Table 11.1.1.3.2-1)
TP-PID Different from Type 0:
01000000B

TP-UDL 160
TP-UD (140 octets) text of message (160
characters)
The 160
characters in TP-
UD shall include
at least one
occurrence of
each character in
the default
alphabet (see
3GPP TS 23.038,
clause 6.2.1).

Table 11.1.1.3.3-5: Message UPLINK NAS TRANSPORT (step 4, Table 11.1.1.3.2-1)
11.1.1.3.3-6

Table 11.1.1.3.3-6: Message CP-ACK (step 4, Table 11.1.1.3.2-1)
Messsage type 00000100B CP-ACK

11.1.1.3.387

11.1.1.3.3-9

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 973 Release 9
973
Table 11.1.1.3.3-9: Message RP-ACK RPDU (step 5, Table 11.1.1.3.2-1)
RP-Message Type 010B RP-ACK_PDU
uplink

11.1.3.3.3-10

Table 11.1.1.3.3-10: Message SMS DELIVER REPORT TPDU (step 5, Table 11.1.1.3.2-1)
TP-MTI 00B SMS-DELIVER
REPORT

TP-FCS Not present

11.1.1.3.3-12


11.1.2 MT-SMS over SGs / Active mode
(1)
with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode }
ensure that {
when { UE receives a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a
then { UE sends a CP-ACK encapsulated in an Uplink NAS transport message followed by a CP-DATA
containing an RP-ACK RPDU (SMS DELIVER REPORT TPDU) encapsulated in an Uplink NAS transport message}
}
5.6.3.3, and 9.9.3.22.
[TS 24.301, clause 5.6.3.1]
[TS 24.301, clause 5.6.3.3]
The network initiates the procedure by sending a DOWNLINK NAS TRANSPORT message. When receiving the
DOWNLINK NAS TRANSPORT message, the EMM entity in the UE shall forward the contents of the NAS message
container IE to the SMS entity.
[TS 24.301, clause 9.9.3.22]
This information element is used to encapsulate the SMS messages transferred between the UE and the network.The

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 974 Release 9
974
of 253 octets.
8 7 6 5 4 3 2 1

octet 3
octet n



System Simulator:
UE:
Preamble:
- UE is in state Generic RB Established (state 3) on Cell A according to [18].
U - S Message
RP-DATA RPDU (SMS DELIVER TPDU)
encapsulated in a Downlink NAS transport
message to the UE.
encapsulated in an Uplink NAS transport
message?
containing an RP-ACK RPDU (SMS DELIVER
REPORT TPDU) encapsulated in an Uplink
NAS transport message?
Downlink NAS transport message to the UE.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 975 Release 9
975
11.1.2.3.3-2

11.1.2.3.3-3

downlink

RP-Originator Address present 1-12 octets
RP-Destination Address present 1 octet
11.1.2.3.3-4

Table 11.1.2.3.3-4: Message SMS DELIVER TPDU (step 1, Table 11.1.2.3.2-1)
01000000B

TP-UDL 160
characters)
The 160
characters in TP-
UD shall include
at least one
occurrence of
each character in
the default
alphabet (see
3GPP TS 23.038,
clause 6.2.1).

11.1.2.3.3-6


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 976 Release 9
976
11.1.2.3.3-8

11.1.3.3.3-9

uplink

11.1.2.3.3-10

Table 11.1.2.3.3-10: Message SMS DELIVER REPORT TPDU (step 3, Table 11.1.2.3.2-1)
TP-MTI 00B SMS-DELIVER
REPORT

TP-FCS Not present

11.1.2.3.3-12


11.1.3 MO-SMS over SGs / Idle mode
(1)
with { UE is IMSI attached for non-EPS services and in EMM-IDLE mode }
ensure that {
when { a MO SMS is initiated at the UE }
then { UE sends an SERVICE REQUEST message followed by a CP-DATA containing an RP-DATA RPDU
(SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }
}

(2)
with { UE is IMSI attached for non-EPS services and UE has sent an SERVICE REQUEST message triggered
by MO SMS followed by a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an
Uplink NAS transport message }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 977 Release 9
977
ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU (SMS SUBMIT REPORT TPDU) encapsulated in a
then { UE sends a CP-ACK encapsulated in an Uplink NAS Transport message }
}

5.6.3.2 and 9.9.3.22., TS 23.401 clause 5.3.4.1.
[TS 24.301, clause 5.6.3.1]
[TS 24.301, clause 5.6.3.2]
Upon request from the SMS entity to send an SMS message, the EMM entity in the UE initiates the procedure by
sending an UPLINK NAS TRANSPORT message including the SMS message in the NAS message container IE.
[TS 24.301, clause 9.9.3.22]
This information element is used to encapsulate the SMS messages transferred between the UE and the network. The
of 253 octets.
8 7 6 5 4 3 2 1

octet 3
octet n



[TS 23.401, clause 5.3.4.1]
1. The UE sends NAS message Service Request towards the MME encapsulated in an RRC message to the eNodeB.
The RRC message(s) that can be used to carry the S-TMSI and this NAS message are described in TS 36.300 [5].
2. The eNodeB forwards NAS message to MME. NAS message is encapsulated in an S1-AP: Initial UE Message
(NAS message, TAI+ECGI of the serving cell, S-TMSI, CSG ID, CSG access Mode). Details of this step are
described in TS 36.300 [5]. If the MME can't handle the Service Request it will reject it. CSG ID is provided if
the UE sends the Service Request message via a CSG cell or a hybrid cell. CSG access mode is provided if the
UE sends the Service Request message via a hybrid cell. If the CSG access mode is not provided but the CSG ID
is provided, the MME shall consider the cell as a CSG cell.
If a CSG ID is indicated and CSG access mode is not provided, and there is no subscription data for this CSG ID
or the CSG subscription is expired, the MME rejects the Service Request with an appropriate cause. The UE
shall remove the CSG ID of the cell where the UE has initiated the service request procedure from the Allowed
CSG list, if present.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 978 Release 9
978
For UEs with emergency EPS bearers, i.e. at least one EPS bearer has an ARP values reserved for emergency
services, if CSG access restrictions do not allow the UE to get normal services the MME shall deactivate all non-
emergency bearers and accept the Service Request.
3. NAS authentication/security procedures as defined in clause 5.3.10 on "Security function" may be performed.
4. The MME sends S1-AP Initial Context Setup Request (Serving GW address, S1-TEID(s) (UL), EPS Bearer
QoS(s), Security Context, MME Signalling Connection Id, Handover Restriction List, CSG Membership
Indication) message to the eNodeB. This step activates the radio and S1 bearers for all the active EPS Bearers.
The eNodeB stores the Security Context, MME Signalling Connection Id, EPS Bearer QoS(s) and S1-TEID(s) in
the UE RAN context. The step is described in detail in TS 36.300 [5]. Handover Restriction List is described in
clause 4.3.5.7 "Mobility Restrictions".
The MME shall only request to establish Emergency EPS Bearer if the UE is not allowed to access the cell
where the UE initiated the service request procedure due to CSG access restriction.
If the Service Request is performed via a hybrid cell, CSG Membership Indication indicating whether the UE is a
CSG member shall be included in the S1-AP message from the MME to the RAN. Based on this information the
RAN can perform differentiated treatment for CSG and non-CSG members.
5. The eNodeB performs the radio bearer establishment procedure. The user plane security is established at this
step, which is described in detail in TS 36.300 [5]. When the user plane radio bearers are setup. EPS bearer state
synchronization is performed between the UE and the network, i.e. the UE shall locally remove any EPS bearer
for which no radio bearers are setup and, if the radio bearer for a default EPS bearer is not established, the UE
shall locally deactivate all EPS bearers associated to that default EPS bearer.

System Simulator:
UE:
Preamble:
- UE is in state Registered, Idle Mode (state 2) on Cell A according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 979 Release 9
979
U - S Message
1 Sending of a 160 character MO SMS is
initiated at the UE via MMI or AT command
- - - -
2 Check: Does the UE transmit an SERVICE
REQUEST message?
containing an RP-DATA RPDU (SMS SUBMIT
TPDU) encapsulated in an Uplink NAS
transport message?
Downlink NAS Transport message.
RP-ACK RPDU (SMS SUBMIT REPORT
TPDU) encapsulated in an Downlink NAS
transport message
encapsulated in an Uplink NAS Transport
message?

11.1.3.3.3-2

11.1.3.3.3-3

uplink

RP-Originator Address present 1 octet
RP-Destination Address present 1-12 octets
11.1.3.3.3-4

Table 11.1.3.3.3-4: Message SMS SUBMIT TPDU (step 3, Table 11.1.3.3.2-1)
TP-MTI 01B SMS-SUBMIT
01000000B

TP-UDL 160
characters)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 980 Release 9
980
11.1.3.3.3-6


11.1.3.3.3-8

11.1.3.3.3-9

downlink

11.1.3.3.3-10

Table 11.1.3.3.3-10: Message SMS SUBMIT REPORT TPDU (step 4, Table 11.1.3.3.2-1)
REPORT

TP-FCS Not present

11.1.3.3.3-12


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 981 Release 9
981
11.1.4 MO-SMS over SGs / Active mode
(1)
with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode }
ensure that {
when { a MO SMS is initiated at the UE }
then { UE sends a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink
NAS transport message }
}
(2)
with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode and UE has sent a CP-DATA
containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }
ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU (SMS SUBMIT REPORT TPDU) encapsulated in a
then { UE sends a CP-ACK encapsulated in an Uplink NAS Transport message }
}

5.6.3.2 and 9.9.3.22, and TS 23.401, clause 5.3.4.1.
[TS 24.301, clause 5.6.3.1]
[TS 24.301, clause 5.6.3.2]
Upon request from the SMS entity to send an SMS message, the EMM entity in the UE initiates the procedure by
sending an UPLINK NAS TRANSPORT message including the SMS message in the NAS message container IE.
[TS 24.301, clause 9.9.3.22]
This information element is used to encapsulate the SMS messages transferred between the UE and the network.The
NAS message container information element is coded as shown in Table 9.9.3.22.1 and 9.9.3.22.2.
of 253 octets.
8 7 6 5 4 3 2 1

octet 3
octet n



[TS 23.401, clause 5.3.4]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 982 Release 9
982
1. The UE sends NAS message Service Request towards the MME encapsulated in an RRC message to the eNodeB.
The RRC message(s) that can be used to carry the S-TMSI and this NAS message are described in TS 36.300 [5].
2. The eNodeB forwards NAS message to MME. NAS message is encapsulated in an S1-AP: Initial UE Message
(NAS message, TAI+ECGI of the serving cell, S-TMSI, CSG ID, CSG access Mode). Details of this step are
described in TS 36.300 [5]. If the MME can't handle the Service Request it will reject it. CSG ID is provided if
the UE attaches via a closed or hybrid mode CSG cell. CSG access mode is provided if the UE sends the Service
Request message via a hybrid mode CSG cell. If the CSG access mode is not provided but the CSG ID is
provided, the MME shall consider the CSG cell as a closed mode CSG cell.
If a CSG ID is indicated and CSG access mode is "closed" or CSG access mode is not provided, and there is no
subscription data for this CSG ID or the CSG subscription is expired, the MME rejects the Service Request with
an appropriate cause. The UE shall remove the CSG ID of the cell where the UE has initiated the service request
procedure from the Allowed CSG list.
3. NAS authentication procedures may be performed.
4. The MME sends S1-AP Initial Context Setup Request (Serving GW address, S1-TEID(s) (UL), EPS Bearer
QoS(s), Security Context, MME Signalling Connection Id, Handover Restriction List) message to the eNodeB.
This step activates the radio and S1 bearers for all the active EPS Bearers. The eNodeB stores the Security
Context, MME Signalling Connection Id, EPS Bearer QoS(s) and S1-TEID(s) in the UE RAN context. The step
is described in detail in TS 36.300 [5]. Handover Restriction List is described in clause 4.3.5.7 "Mobility
Restrictions".
5. The eNodeB performs the radio bearer establishment procedure. The user plane security is established at this
step, which is described in detail in TS 36.300 [5]. When the user plane radio bearers are setup the Service
Request is completed and EPS bearer state is synchronized between the UE and the network, i.e. the UE should
remove the EPS bearer for which no radio bearers are setup.

System Simulator:
UE:
Preamble:
- UE is in state Generic RB Established (state 3) on Cell A according to [18].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 983 Release 9
983
U - S Message
1 Sending of a 160 character MO SMS is
initiated at the UE via MMI or AT command
- - - -
containing an RP-DATA RPDU (SMS SUBMIT
TPDU) encapsulated in an Uplink NAS
transport message?
Downlink NAS Transport message.
RP-ACK RPDU(SMS SUBMIT REPORT
TPDU) encapsulated in an Downlink NAS
transport message
encapsulated in an Uplink NAS Transport
message?

11.1.4.3.3-2

11.1.4.3.3-3

RP-Message Type 000B RP-DATA uplink
RP-Originator Address present 1 octet
RP-Destination Address present 1-12 octets
11.1.4.3.3-4

Table 11.1.4.3.3-4: Message SMS SUBMIT TPDU (step 2, Table 11.1.4.3.2-1)
01000000B

TP-UDL 160
characters)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 984 Release 9
984
11.1.4.3.3-6

Table 11.1.4.3.3-6: Message CP-ACK (step 3 Table 11.1.4.3.2-1)

11.1.4.3.3-8

11.1.4.3.3-9

downlink

11.1.4.3.3-10

Table 11.1.4.3.3-10: Message SMS SUBMIT REPORT TPDU (step 4, Table 11.1.4.3.2-1)
REPORT

TP-FCS Not present

11.1.4.3.3-12


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 985 Release 9
985
12 E-UTRA radio bearer tests
12.1 General
The present clause defines radio bearer combinations as well as generic E-UTRA radio bearer test procedures. The
generic E-UTRA radio bearer test procedures include generic TPs and test description. The TCs that follow verify
specific E-UTRA radio bearer combinations by indicating the relevant combinations and making reference to the
generic procedures' TPs and test description as appropriate. The reference to the generic TP shall be understood not as
having the same TP rather as applying the same TP to a different E-UTRA radio bearer combination.
12.1.0 Definition of radio bearer combinations
The radio bearer combinations tested are listed in table 12-1. The radio bearer combinations and identifiers (1 to 13) are
according to the radio bearer combinations and identifier in TS 36.331 Annex B.1.
Table 12-1: Radio Bearer Combinations
RB
combination
identifier
Radio bearer combination
1 SRB1 and SRB2 for DCCH +1xAM DRB
2 SRB1 and SRB2 for DCCH +1xAM DRB +1xUM DRB

12.1.1 Generic E-UTRA radio bearer test procedure / MIMO not configured
(1)
with { UE in E-UTRA RRC_CONNECTED state with a "n x AM DRB + m x UM DRB" radio bearer combination
established and physical layer configured for SISO transmission}
ensure that {
when { UE receives a PDCP SDU on each configured AM and UM DRB within the same TTI }
then { UE forward the received PDCP SDUs to upper layer }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with "an x AM DRB + m x UM DRB" radio bearer combination
established }
ensure that {
when { UE has pending data in the transmission buffer corresponding to a complete PDCP SDU on each
configured AM and UM DRB and UE receives an UL Grant allowing UE to transmit all pending data }
then { UE transmits a PDCP SDU on each configured AM and UM DRB within the same TTI }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36-series Layer 1,
Layer 2 and Layer 3 core specifications.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 986 Release 9
986
System Simulator
- Cell 1
UE:
- None
Preamble
- Radio bearer for combination SRB1 and SRB2 for n x AM DRB +m x UM DRB is used where n and m are
specified in the test case.
Table 12.1.1.3.1-1: RLC settings
Parameter Value
t-PollRetransmit 250 ms

NOTE: In case of multiple iterations of this procedure, the generic test procedures in TS 36.508 Tables 4.5.3.3-1 and
4.5.4.3-1 are performed between each iteration to bring the UE back to state Loopback Activated (state 4).
U - S Message
- - - -
2 The SS transmits a PDCP SDU of size 40
bytes on each configured AM DRB and a
PDCP SDU of size 40 bytes on each
configured UM DRB in the same TTI
<-- PDCP SDUs - -
2A SS respond to any scheduling request from the
UE by an UL Grant of 32 bits. (Note 1)
3 SS waits until UE transmit a BSR with Buffer
size field set to value indicating that all data
received in step 2 is pending for transmission.
- - - -
4 After 100ms SS transmits an UL grants to
enable UE to return all pending data in one TTI
<-- (UL grant) - -
5 Check: Does UE transmit a PDCP SDU on
each configure AM and UM DRB of the same
size and content as transmitted by the SS in
step 2?
--> PDCP SDUs 1,2 P
5A The SS transmits an OPEN UE TEST LOOP
message to enter the UE test loop mode.
<-- RRC: DLInformationTransfer
TC: OPEN UE TEST LOOP
- -
5B The UE transmits an OPEN UE TEST LOOP
COMPLETE message.
--> RRC: ULInformationTransfer
TC: OPEN UE TEST LOOP
COMPLETE
- -
6 The SS releases the connection. - - - -
BSR (3 byte).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 987 Release 9
987
12.1.1.3.3 Specific Message Contents
Table 12.1.1.3.3-1: PDCP-Config-DRB-UM (preamble: Table 4.5.3.3-1, step 8)
PDCP-Config-DRB-UM ::=SEQUENCE {
discardTimer ms300

12.1.2 Generic E-UTRA radio bearer test procedure / MIMO configured
(1)
established and physical layer configured for MIMO transmission}
ensure that {
when { UE receives PDCP SDUs from one or more logical channles multiplexed on transport block 1
and transport block 2within the same TTI }
then { UE forward the received PDCP SDUs to upper layer }
}
(2)
established }
ensure that {
when { UE has pending data in the transmission buffer corresponding to two complete PDCP SDUs on
each configured AM and UM DRB and UE receives an UL Grant allowing UE to transmit all pending data }
then { UE transmits two PDCP SDUs on each configured AM and UM DRB }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36-series Layer 1,
Layer 2 and Layer 3 core specifications.
System Simulator
- Cell 1 (MIMO)
UE:
- None
Preamble
- The UE is in state Loopback Activated (state 4) according to [18] using condition 2TX to configure MIMO.
- Radio bearer for combination SRB1 and SRB2 for n x AM DRB +m x UM DRB is used where n and m are
specified in the test case.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 988 Release 9
988
U - S Message
- - - -
2 The SS transmits two PDCP SDUs of size 40
bytes on each configured AM DRB and two
PDCP SDUs of size 40 bytes on each
configured UM DRB in the same TTI. The
PDCP SDUs are multiplexed on transport
block 1 and 2 based on logical channel priority
with data from higher MAC logical channel
priority mapped to transport block 1. If more
than one DRB have same logical channel
priority then data from DRB with lower DRB-ID
value gets mapped on transport block 1.
<-- PDCP SDUs - -
2a SS respond to any scheduling request from the
UE by an UL Grant of 32 bits. (Note 1)
3 SS waits until UE transmit a BSR with
Buffer size field set to value indicating
that all data received in step 2 is pending
for transmission.
- - - -
4 After 100ms SS transmits an UL grants to
enable UE to return all pending data in one TTI
- - - -
5 Check: Does UE transmit two PDCP SDUs on
each configured AM and UM DRB of the same
size and content as transmitted by the SS in
step 2?
--> PDCP SDUs 1,2 P
6 The SS releases the connection - - - -
BSR (3 byte).

Table 12.1.2.3.3-1: PDCP-Config-DRB-UM (preamble: Table 4.5.3.3-1, step 8)
PDCP-Config-DRB-UM ::=SEQUENCE {
discardTimer ms300

12.2 MIMO not configured
12.2.1 Data transfer of E-UTRA radio bearer combinations 1,3,6 and 9
See 12.1.1.1
See 12.1.1.2
System Simulator
- See 12.1.1.3

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 989 Release 9
989
UE:
- See 12.1.1.3
Preamble
- The number of AM data radio bearers (n) and UM data radio bearers (m) for each execution is specified in table
12.2.1.3.1-1.
Table 12.2.1.3.1-1: Test parameters (m,n) for each execution (k)
Execution
k
Number
of AM
DRBs
n
Number
of UM
DRBs
m
1 1 - 1: SRB1 and SRB2 for DCCH +1xAM DRB

U - S Message
EXCEPTION: Step 1 is repeated for execution
counter k=1 to 4
- - - -
1 Generic test procedure in 12.1.1 is executed
for execution k with number of AM DRB (n)
and number of UM DRB (m) as specified in
table 12.2.1.3.1-1.
- - - -
None
See 12.1.1.1
See 12.1.1.2
System Simulator
- See 12.1.1.3
UE:
- See 12.1.1.3
Preamble
12.2.2.3.1-1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 990 Release 9
990
Table 12.2.2.3.1-1: Test parameters (m,n) for each execution (k)1
Execution
k
Number
of AM
DRBs
n
Number
of UM
DRBs
m
1 1 1 2: SRB1 and SRB2 for DCCH +1xAM DRB +1xUM DRB

U - S Message
counter k=1 to 4
- - - -
table 12.2.2.3.1-1.
- - - -

None
See 12.1.1.1
See 12.1.1.2
System Simulator
- See 12.1.1.3
UE:
- See 12.1.1.3
Preamble
12.2.3.3.1-1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 991 Release 9
991
Execution
K
Number
of AM
DRBs
n
Number
of UM
DRBs
m

U - S Message
counter k=1 to 4
- - - -
table 12.2.3.3.1-1.
- - - -

None
12.2.4 Data transfer of E-UTRA radio bearer combination 13
See 12.1.1.1
See 12.1.1.2
System Simulator
- See 12.1.1.3
UE:
- See 12.1.1.3
Preamble
- The number of AM data radio bearers (n) and UM data radio bearers (m) is specified in table 12.2.4.3.1-1.
Table 12.2.4.3.1-1: Test parameters (m,n) for execution (k)
Execution
k
Number
of AM
DRBs
n
Number
of UM
DRBs
m
1 8 0 13: SRB1 and SRB2 for DCCH +8xAM DRB

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 992 Release 9
992
U - S Message
for execution 1 with number of AM DRB (n)
table 12.2.4.3.1-1.
- - - -

None
12.3 MIMO configured
12.3.1 Data transfer of E-UTRA radio bearer combinations 1,3,6 and 9 /
MIMO
See 12.1.2.1
See 12.1.2.2
System Simulator
- See 12.1.2.3
UE:
- See 12.1.2.3
Preamble
12.3.1.3.1-1.
Execution
k
Number of
AM DRBs
n
Number of
UM DRBs
m

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 993 Release 9
993
U - S Message
counter k=1 to 4
- - - -
table 12.3.1.3.1-1.
- - - -

None
MIMO
See 12.1.2.1
See 12.1.2.2
System Simulator
- See 12.1.2.3
UE:
- See 12.1.2.3
Preamble
12.3.2.3.1-1.
Execution
k
Number of
AM DRBs
n
Number of
UM DRBs
M

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 994 Release 9
994
U - S Message
counter k=1 to 4
- - - -
table 12.3.2.3.1-1.
- - - -

None
MIMO
See 12.1.2.1
See 12.1.2.2
System Simulator
- See 12.1.2.3
UE:
- See 12.1.2.3
Preamble
12.3.3.3.1-1.
Execution
K
Number
of AM
DRBs
n
Number
of UM
DRBs
m

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 995 Release 9
995
U - S Message
counter k=1 to 4
- - - -
table 12.3.3.3.1-1.
- - - -

None
12.3.4 Data transfer of E-UTRA radio bearer combination 13 / MIMO
See 12.1.2.1
See 12.1.2.2
System Simulator
- See 12.1.2.3
UE:
- See 12.1.2.3
Preamble
- The number of AM data radio bearers (n) and UM data radio bearers (m) is specified in table 12.3.4.3.1-1.
Execution
k
Number
of AM
DRBs
n
Number
of UM
DRBs
m
1 8 0 13: SRB1 and SRB2 for DCCH +8xAM DRB

U - S Message
for execution 1 with number of AM DRB (n)
table 12.3.4.3.1-1.
- - - -

None

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 996 Release 9
996
13 Multi layer Procedures
13.1 Call setup
13.1.1 Activation and deactivation of additional data radio bearer in E-
UTRA
(1)
with { UE has a default EPS bearer context and dedicated EPS bearer context active and the
associated DRBs are established }
ensure that {
when { UE receives donwlink data on the radio bearer associated with the default or the dedicated
EPS bearer context }
then { UE delivers the downlink data to upper layers }
}
(2)
with { UE has a default EPS bearer context and dedicated EPS bearer context active and the
associated DRBs are established }
ensure that {
when { uplink data are submitted for transmission }
then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer
context or the dedicated EPS bearer context according to configured TFT}
}
(3)
with { UE has a default EPS bearer context and the dedicated EPS bearer context was deactivated }
ensure that {
when { UE receives donwlink data on the radio bearer associated with the default EPS bearer
context }
}
(4)
with { UE has a default EPS bearer context and the dedicated EPS bearer context was deactivated }
ensure that {
context }
}

Same Conformance requirements as in clause 8.2.1.3, 8.2.3.1, 10.2.1 and 10.4.1
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE is in state Generic RB Established, UE test mode activated (state 3A) according to [18] using the UE TEST
LOOP MODE B.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 997 Release 9
997
U - S Message
1 SS transmits an
The SS transmits a ACTIVATE DEDICATED
message activating a new EPS bearer context.

The NAS message is included in a
NAS: ACTIVATE DEDICATED
EPS BEARER CONTEXT
REQUEST
- -
2 The UE transmit a
message to confirm the establishment of data
radio bearer.
omplete
- -
3 The UE transmits an ACTIVATE DEDICATE
--> ULInformationTransfer
NAS: ACTIVATE DEDICATE EPS
- -
4 The SS closes the UE test loop mode. - - - -
bearer context.
<-- IP packet - -
6 Check: Does the UE loop back the IP packet
bearer context?
--> IP packet 1,2 P
the DRB associated with the dedicated EPS
bearer context.
<-- IP packet - -
on the DRB associated with the dedicated
EPS bearer context?
--> IP packet 1,2 P
9 SS transmits an
release a data radio bearer.
The SS transmits a DEACTIVATE EPS
bearer.

The NAS message is included in a
NAS: DEACTIVATE EPS
- -
message.
omplete
- -
11 The UE transmit a DEACTIVATE EPS
BEARER CONTEXT ACCEPT.
NAS:DEACTIVATE EPS BEARER
CONTEXT ACCEPT
- -
bearer context.
<-- IP packet - -
bearer context?
--> IP packet 3, 4 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 998 Release 9
998
Table 13.1.1.3.3-1: Message RRCConnectionReconfiguration (step 1, Table 13.1.1.3.2-1)
Derivation Path: 36.508 table 4.6.1-8, condition DRB(1,0)
c1 CHOICE{
1 entry
dedicatedInfoNAS [1] octet string ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST
according 36.508
table 4.7.3-3

}
}
}
}

13.1.1.3.2-1)
EPS bearer identity EBId-1 SS defines a
dedicated bearer
Id different from
default EBId and
between 5 and 15.

transaction
identity assigned"

Linked EPS bearer identity Default EBId SS re-uses the
EPS bearer
identity of the
default EPS
bearer context.


context #1- see [18]

Table 13.1.1.3.3-3: Message ACTIVATE DEDICATE EPS BEARER CONTEXT ACCEPT (step 3, Table
13.1.1.3.2-1)
EPS bearer identity EBId-1 Same value as in
ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST

transaction
identity assigned"

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 999 Release 9
999
Table 13.1.1.3.3-4: Message RRCConnectionReconfiguration (step 9, Table 13.1.1.3.2-1)
c1 CHOICE{
(SIZE(1..maxDRB)) OF SEQUENCE {

DedicatedInfoNAS[1] DEACTIVATE EPS
BEARER CONTEXT
REQUEST

}
dicated-DRB-RELEASE

}
}
}
}

Table 13.1.1.3.3-5: Message RadioResourceConfigDedicated-DRB-RELEASE (step 9, Table 13.1.1.3.2-
1)
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB))
OF SEQUENCE {
1 entry
drb-Identity[1] 2
}
mac-MainConfig CHOICE {} Not present
}

Table 13.1.1.3.3-6: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 9, Table 13.1.1.3.2-1)
ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST of step
1

transaction
identity assigned

ESM cause 00100100 Regular
deactivation


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1000 Release 9
1000
Table 13.1.1.3.3-7: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 11, Table 13.1.1.3.2-1)
ACTIVATE
DEDICATED EPS
BEARER
CONTEXT
REQUEST of step
1

transaction
identity assigned

13.1.2 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with
redirection / MO call
(1)
with { the UE is in E-UTRA RRC_IDLE state }
ensure that {
when { the user initiates a CS voice call }
then { the UE transmits an EXTENDED SERVICE REQUEST message with Service Type IE set to "mobile
originating CS fallback or 1xCS fallback" }
}

(2)
with { the UE transmitted an EXTENDED SERVICE REQUEST message with Service Type IE set to "mobile
originating CS fallback or 1xCS fallback" }
ensure that {
when { the UE receives an RRCConnectionRelease message with redirection to a UMTS cell which
belongs to the LA allocated to the UE during the previous registration procedure in E-UTRAN }
then { UE establishes a connection to the designated UMTS cell, performs a RA update procedure
and establishes a CS call }
}

The conformance requirements covered in the present TC are specified in: TS 24.301 clauses 5.6.1.1 and TS 24.008,
clause 4.5.1.1.
[TS 24.301, clause 5.6.1.1]
...
...
d) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use CS fallback and has a mobile
originating CS fallback request from the upper layer;

[TS 24.008, clause 4.5.1.1]
...
In order to establish an MM connection, the mobile station proceeds as follows:
...

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1001 Release 9
1001
d) When the MS is IMSI attached for CS services via EMM combined procedures, as described in 3GPP TS 24.301
[120], and the MS is camping on an E-UTRAN cell, the MM sublayer requests EMM to initiate a service request
procedure for CS fallback. The MM connection establishment is delayed until the MS changes to a GERAN or
UTRAN cell.
If the MS enters a GERAN or UTRAN cell, then the MS shall initiate the MM connection establishment and
send a CM SERVICE REQUEST message. If the MS determines that it is in a different location area than the
stored location area, the MS shall first initiate a normal location updating procedure or a combined routing area
update procedure, depending on Network Mode of Operation. If the location area of the current cell is not
available, the MS may initiate a normal location updating procedure directly. The MM connection establishment
is delayed until successful completion of the normal location updating or combined routing area update
procedure. The MS may perform location area updating procedure instead of combined routing area update
procedure in NMO I. If the normal location updating procedure is initiated, the MS shall indicate the "follow-on
request pending" in the LOCATION UPDATING REQUEST message.
System Simulator:
- cell 1 (E-UTRA) and cell 5 (UTRA);
- power levels are constant and as defined in table 13.1.2.3.1-1;
- cell 5 is in NMO 1.
Table 13.1.2.3.1-1: Cell power levels
Parameter Unit Cell1 Cell 5 Remark
Cell-specific RS EPRE dBm/15kHz -75 - The power levels are such that the UE
camps on cell 1. CPICH_Ec dBm/3.84 MHz - -70

UE:
- the UE is configured to initate combined EPS/IMSI attach.
Preamble:
- the UE is in state Registered, Idle Mode (state 2) according to TS 36.508 [18].
Note: During the registration procedure, the UE is allocated the LAI of cell 5.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1002 Release 9
1002
U - S Message
1 A CS call is initiated (see Note 1)
message.
3 The SS tr;ansmits an RRCConnectionSetup
message
5 Void - -
6 Void - -
7 Void - -
message indicating redirection to cell 5
REQUEST with an establishment cause
indicating ' Originating Conversational Call '.
--> RRC CONNECTION REQUEST - -
SETUP message.
SETUP COMPLETE message.
COMPLETE
- -
- EXCEPTION: In parallel to step 12, the parallel
behaviour in table 13.1.2.3.2-2 is taking place.
- - - -
12 Check: Does the UE transmit a CM SERVICE
REQUEST message?
--> CM SERVICE REQUEST 2 P
COMMAND message for the PS domain. See
Note 2.
COMPLETE message.
ACCEPT message not including P-TMSI.
ACCEPT

16 Steps 8 to 16 of the generic test procedure in
Cell 5 (the SS performs a SMC procedure and
the CS call is set up).
- - - -
- The UE is in end state UTRA CS call (U5). - - - -
Note 2: A real network will initiate the security mode command procedure for the CS domain immediately after
receiving the CM SERVICE REQUEST, but in this test case it was chosen to complete the procedure for
PS domain first in order to avoid the possibility of a security mode command procedure running in parallel
with another RRC procedure.

U - S Message
REQUEST
2 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1003 Release 9
1003
Table 13.1.2.3.3-1: SystemInformationBlockType6 for cell 1 (preamble and all steps, table 13.1.2.3.2-1)
FDD
carrierFreq[n] Same as cell 5
cellReselectionPriority[n] 3 Lower than cell 1
priority (priority =
4)

}
1 entry TDD
carrierFreq[n] Same as cell 5
cellReselectionPriority[n] 3 Lower than cell 1
priority (priority =
4)

}
}

Table 13.1.2.3.3-2: EXTENDED SERVICE REQUEST (step 4, table 13.1.2.3.2-1)
Service type 0000 'mobile originating
CS fallback or 1xCS
fallback'

EPS bearer context status Not present or any
allowed value

Table 13.1.2.3.3-3: RRCConnectionRelease (step 8, table 13.1.2.3.2-1)
c1 CHOICE {
5
FDD
5
TDD
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1004 Release 9
1004
Table 13.1.2.3.3-4: CM SERVICE REQUEST (step 12, table 13.1.2.3.2-1)
CM service type 0001 'Mobile originating
call establishment or
packet mode connection
establishment'

Ciphering key sequence
number
Any allowed value
Mobile station
classmark
Any allowed value
Mobile identity
TMSI TMSI-1
Priority Not present or any
allowed value

Table 13.1.2.3.3-5: ROUTING AREA UPDATE ACCEPT (step 15, table 13.1.2.3.2-1)
PTMSI Not present
PTMSI signature Not present

13.1.3 Call setup from E-UTRAN RRC_CONNECTED / CS fallback to
UTRAN with Redirection / MT call
(1)
ensure that {
when { UE receives a DLInformationTransfer message containing a CS SERVICE NOTIFICATION message }
then { UE transmits an ULInformationTransfer message containing an EXTENDED SERVICE REQUEST
}

(2)
ensure that {
when { SS transmits an RRCConnectionRelease message with redirection to a UTRA cell in a different
location area and operating in NMO I }
then { UE tunes to UTRA cell and performs a RA Update procedure }
}

(3)
message with Service Type IE set to "mobile terminating CS fallback or 1xCS fallback and tuned to
UTRA cell and initiated a RA Update procedure }
ensure that {
when { UE completes the RA Update procedure }
then { UE transmits a PAGING RESPONSE on UTRA cell to set up MT CS call }
}

(4)
UTRA cell and initiated a RA Update procedure and having pending UL data to send}
ensure that {
then { UE transmits a SERVICE REQUEST to set up PS bearers on UTRA cell }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1005 Release 9
1005
(5)
UTRA cell and initiated a RA Update procedure and having pending UL data to send}
ensure that {
when { PS bearers have been set up on UTRA cell }
then { UE transmits pending UL data }
}

References: The conformance requirements covered in the current TC are those listed in TC 8.1.3.6, plus those specified
in: TS 23.272, clause 7.4, and TS 24.301, clause 5.6.2.3.
[TS 23.272, clause 7.4]
9a. Connection Reject
1a. CS Paging Notification 1a. Paging Request
If the
MSC is
changed
SGSN
10. CS Call Establishment procedure
6. LA Update or Combined RA/LA Update or RA Update or LA Update and RA Update
BSS/RNS
4. S1-AP: S1 UE Context Release Request
1a. Service Request
UE/MS
MME
MSC
3a. NACC, 3b. Signalling connection release
eNodeB
2. Optional Measurement Report
9. Paging Response
9b. Location Area Update or Combined RA/LA Update
9a. Signalling Connection Release
S-GW
1d. S1-AP message with CS Fallback indicator
1c. CS Paging Reject
7a. Suspend (see TS 23.060)
8. Update bearer(s)
7b. Suspend Request / Response

Figure 7.4-1: CS Page in E-UTRAN, Call in GERAN/UTRAN without PS HO

1a. The MSC receives an incoming voice call and responds by sending a Paging Request (IMSI or TMSI, optional
Caller Line Identification and Connection Management information, priority indication) to the MME over a SGs
interface. The MSC only sends a CS Page for an UE that provides location update information using the SGs
interface. In active mode the MME has an established S1 connection and if the MME did not return the "SMS-
only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME reuses the existing
connection to relay the CS Service Notification to the UE.
If the MME returned the "SMS-only" indication to the UE during Attach or Combined TA/LA Update
procedures, the MME shall not send the CS Page to the UE and sends CS Paging Reject towards MSC to stop
CS Paging procedure, and this CSFB procedure stops.
The eNB forwards the paging message to the UE. The message contains CN Domain indicator and, if received
from the MSC, the Caller Line Identification.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1006 Release 9
1006
The MME immediately sends the SGs Service Request message to the MSC containing an indication that the UE
was in connected mode. The MSC uses this connected mode indication to start the Call Forwarding on No Reply
timer for that UE and the MSC should send an indication of user alerting to the calling party. Receipt of the SGs
Service Request message stops the MSC retransmitting the SGs interface Paging message.
NOTE 1: The pre-configured policy may be used by UE to avoid being disturbed without Caller Line Identification
display and the detailed handling is to be decided by CT WG1 and CT WG6.
NOTE 2: This procedure can also take place immediately after MSC receives MAP_PRN from HSS, if pre-paging
is deployed. Caller Line Identification is also provided in the case of pre-paging.
If the MME receives paging request message with priority indication, e.g. eMLPP priority, from the MSC, then
the MME processes this message and also the subsequent CS fallback procedure preferentially compared to other
normal procedures.
1b. UE sends an Extended Service Request (CS Fallback Indicator, Reject or Accept) message to the MME.
Extended Service Request message is encapsulated in RRC and S1-AP messages. CS Fallback Indicator
indicates MME to perform CS Fallback. The UE may decide to reject CSFB based on Caller Line Identification.
1c. Upon receiving the Extended Service Request (CSFB, Reject), the MME sends Paging Reject towards MSC to
stop CS Paging procedure and this CSFB procedure stops.
1d. The MME sends an S1-AP UE Context Modification Request message to eNodeB that includes a CS Fallback
Indicator. This message indicates to the eNB that the UE should be moved to UTRAN/GERAN.
If MME received priority indication in Step 1a, the MME sends S1-AP UE Context Modification Request
message to the eNodeB with priority indication, i.e. "CSFB High Priority", as specified in TS 36.413 [35].
1e. The eNB shall reply with S1-AP UE Context Modification Response message.
2. The eNodeB may optionally solicit a measurement report from the UE to determine the target GERAN cell to
which the redirection procedure will be performed.
The network performs one of steps 3a or 3b or 3c.
3a. If the UE and network support inter-RAT cell change order to GERAN and the target cell is GERAN:
The eNodeB can trigger an inter-RAT cell change order (optionally with NACC) to a GERAN neighbour cell by
sending an RRC message to the UE. The inter-RAT cell change order may contain a CS Fallback Indicator
which indicates to UE that the cell change order is triggered due to a CS fallback request. If the inter-RAT cell
change order contains a CS Fallback Indicator and the UE fails to establish connection to the target RAT, then
the UE considers that CS fallback has failed. Service Request procedure is considered to be successfully
completed when cell change order procedure is completed successfully.
3b. If the UE or the network does not support inter-RAT PS handover from E-UTRAN to GERAN/UTRAN nor
inter-RAT cell change order to GERAN:
The eNodeB can trigger RRC connection release with redirection to GERAN or UTRAN instead of PS HO or
NACC.
3c. If the UE and network support "RRC connection release with redirection and Multi Cell System Information to
GERAN/UTRAN":
The eNodeB can trigger RRC connection release with redirection to GERAN or UTRAN and include one or
more physical cell identities and their associated System Information.
NOTE 3: Service Request procedure supervision timer shall be sufficiently long considering the optional
measurement reporting at step 2.NOTE 4: Service Request procedure supervision timer shall be
sufficiently long considering the optional measurement reporting at step 2.
4. The eNodeB sends an S1 UE Context Release Request message to the MME. If the target cell is GERAN and
either the target cell or the UE does not support DTM the message includes an indication that the UE is not
available for PS service.
5. The MME releases the UE Context in the eNodeB as well as all eNodeB related information in the S-GW as
specified in TS 23.401 [2].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1007 Release 9
1007
In case the Cause indicates that RRC was released due to abnormal conditions, e.g. radio link failure, the MME
suspends the EPS bearers (Step 8).
The UE performs one of steps 6a or 6b or 6c and THEN performs step 6d.
6a. (Step 6a is performed if step 3a, Cell Change Order to GERAN, was performed)
The UE moves to the new cell in GERAN. The UE uses the NACC information and/or receives the broadcast
System Information and when it has the necessary information to access the GERAN cell, establishes a radio
6b. (Step 6b is performed if step 3b, RRC release with redirection, was performed)
The UE moves to the target RAT, identifies a suitable cell preferably of the same PLMN as received in LAI IE of
combined EPS/IMSI Attach/TAU Accept message,, receives the broadcast System Information and when it has
the necessary information to access GERAN/UTRAN, establishes a radio signalling connection.
6c. (Step 6c is performed if step 3c, RRC connection release with redirection and Multi Cell System Information,
was performed)
The UE moves to the target RAT and identifies a suitable cell preferably of the same PLMN as received in LAI
IE of combined EPS/IMSI Attach/TAU Accept message. The UE uses the NACC information and/or receives
the broadcast System Information and when it has the necessary information to access GERAN/UTRAN, the UE
establishes the radio signalling connection.
6d. If the LA of the new cell is different from the one stored in the UE, the UE shall initiate a Location Area Update
or a Combined RA/LA Update as specified in TS 23.060 [3] for the different Network Modes of Operation
(NMO). The UE shall set the "CSMT" flag in the LAU Request. The "CSMT" flag is used to avoid missing MT
call in roaming retry case. In NMO I, the UE in GERAN may perform LA update over the RR connection
instead of combined RA/LA update over the packet access as defined in TS 24.008 [21], clause 4.7.5.2.5, unless
enhanced CS establishment in DTM is supported. Further the UE performs any Routing Area Update procedure
as specified in TS 23.060 [3].
In NMO I a CSFB UE should perform LAU (and if it does so, shall set the "CSMT" flag) and RAU procedures
instead of a Combined RA/LA Update procedure to speed up the CSFB procedure.
When the MSC receives a LA Update Request, it shall check for pending terminating CS calls and, if the
"CSMT" flag is set, maintain the CS signalling connection after the Location Area Update procedure for pending
terminating CS calls.
7. If the target RAT is GERAN and DTM is not supported, the UE starts the Suspend procedure specified in
TS 23.060 [3], clause 16.2.1.1.2. This triggers the SGSN to send a Suspend Request message to the MME. The
MME returns a Suspend Response to the SGSN even though GUTI cannot be derived from the P-TMSI and RAI
pair.
8. If the S1-AP UE Context Release Request message, received from the eNodeB in step 4, indicates that the UE is
not available for the PS services in the target cell, the MME deactivates GBR bearers towards S-GW and P-
GW(s) by initiating MME-initiated Dedicated Bearer Deactivation procedure as specified in TS 23.401 [2], and
starts the preservation and suspension of non-GBR bearers by sending Suspend Notification message to the S-
GW. The S-GW releases all eNodeB related information (address and TEIDs) for the UE, and sends Suspend
Notification message to the P-GW(s). The MME stores in the UE context that the UE is in suspended status. All
the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW(s). The P-GW should
discard packets if received for the suspended UE.
NOTE 4: Step 8 can not be triggered by the Suspend procedure since the full GUTI can not be derived from the
P-TMSI and RAI included in the Suspend Request message.
9. If the UE does not initiate a LAU procedure, the UE responds to the paging by sending a Paging Response
message as specified in TS 44.018 [4] or TS 25.331 [7]. When received at the BSS/RNS, the Paging Response is
forwarded to the MSC.
NOTE 6: The MSC should be prepared to receive a Paging Response after a relatively long time from when the CS
Paging Request was sent (step 1a).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1008 Release 9
1008
9a. If UE is registered in the MSC serving the 2G/3G cell and the UE is allowed in the LA the MSC shall establish
the CS call.
9b. If the UE is not registered in the MSC that receives the Paging Response or the UE is not allowed in the LA, the
MSC shall reject the Paging Response by releasing the A/Iu-cs connection. The BSS/RNS in turn releases the
signalling connection for CS domain.
9c. The signalling connection release shall trigger the UE to obtain the LAI, which causes the initiation of a
Location Area Update or a Combined RA/LA procedure as specified in TS 23.060 [3] for the different Network
Modes of Operation (NMO).
The Location Area Update triggers the Roaming Retry for CS Fallback procedure as defined in clause 7.5.
After performing the LAU procedure the MSC shall establish the CS call if the UE is allowed in the LA.
[TS 24.301, clause 5.6.2.3]
services (see example in figure 5.6.2.3.1).
UE
MME
EXTENDED SERVICE REQUEST
AS
Request paging
Paging

Figure 5.6.2.3.1: Paging procedure for CS fallback to A/Gb or Iu mode

layer to start paging (see 3GPP TS 36.300 [20], 3GPP TS 36.413 [23]). The paging message includes a CN domain
indicator set to "CS" in order to indicate that this is paging for CS fallback.
NOTE: The timer T3413 is not started in the network when the paging procedure is initiated for CS fallback.
entity in the network shall send a CS SERVICE NOTIFICATION message. This message may also include CS service
related parameters (e.g. Calling Line Identification, SS or LCS related parameters).
Upon reception of a paging indication, the UE shall respond with an EXTENDED SERVICE REQUEST. If the paging
is received in EMM-IDLE mode, the UE shall respond immediately. If the paging is received as NAS CS
NOTIFICATION message in EMM-CONNECTED mode, the UE may request upper layers input i.e. to accept or reject
CS fallback before responding with an EXTENDED SERVICE REQUEST. The response is indicated in the CSFB
response information element in the EXTENDED SERVICE REQUEST message in both EMM-IDLE and EMM-
CONNECTED modes.
System Simulator:
- 2 cells, one E-UTRA and one UTRA cell and different location areas:
- Cell 5 suitable neighbour UTRA cell

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1009 Release 9
1009
- The parameters settings and power levels for Cell 1 and Cell 5 are selected according to [18], [5] and Table
13.1.3.3.2-1 so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 5 can take place (utra
Cell 1
>Thresh
Cell 1,low
).
UE:
- the UE is configured to initate combined EPS/IMSI attach.
Preamble:
- The UE is in state Loopback actived (state 4) on cell 1 according to [18] using UE test loop mode B with
IP_PDU_delay set to 255 sec.
Table 13.1.3.3.2-1 shows the cell power levels after the preamble.
T0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1010 Release 9
1010
U - S Message
<-- IP packet - -
message on Cell 1 containing a CS SERVICE
NOTIFICATION message.
<-- DLInformationTransfer
NAS: CS SERVICE
NOTIFICATION
- -
that depends on the UE capability; the "lower
case letter" identifies a step sequence that
takes place if a capability is supported.
- - - -
3a1 IF the UE needs to request upper layer input
before accepting the CS fallback, the incoming
CS call is accepted at the UE through MMI or
AT command.
- - - -
ULInformationTranfer message containing an
Service Type IE set to "mobile terminating CS
REQUEST
1 P
message on Cell 1 with IE
redirectionInformation including UTRA-
CarrierFreq of Cell 5.
CONNECTION REQUEST message with
Establishment cause Registration'?
6A
1
The SS transmits an RRC CONNECTION
SETUP message.
<-- RRC: RRC CONNECTION
SETUP
- -
6A
2
The UE transmits an RRC CONNECTION
SETUP COMPLETE message.
--> RRC: RRC CONNECTION
SETUP COMPLETE
- -
- EXCEPTION: Steps 7 to 11 describe
sequence that depends on UE behaviour. The
sequence takes place if UE initiates combined
LA/RA updated procedure after step 6a2.
- - - -
7-
11
Cell 5.
- - - -
described in steps 12 to 23, the steps specified
should take place.
- - - -
described in steps 12 to 23, if combined RA/LA
update procedure does not happen in step 7
then the steps specified in Table 13.1.3.3.2-4
should take place
- - - -
12 Check: Does the UE transmit a PAGING
RESPONSE on Cell 5?
--> PAGING RESPONSE 3 P
sequence that depends on UE behaviour
- - - -
13
a1-
13a
11
IF combined RA/LA update procedure is
performed in step 7 then steps 7 to 17 of the
NOTE: Mobile terminating CS call is set up.
- - - -
13b
1-
13b
9
IF combined RA/LA update procedure is NOT
performed in step 7 then steps 9 to 17 of the
- - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1011 Release 9
1011
U - S Message
REQUEST message on Cell 5?
2 Void - -
3 Void - -
Cell 5.
NOTE: Mobile originating packet switched
session is set up.
- - - -
received in Step 1 on the RAB associated with
the PDP context active on Cell 5?
--> IP packet 5 P

U - S Message
Table 13.1.3.3.2-5 should take place
- - - -
1 The UE transmits a LOCATION UPDATING
REQUEST message.
REQUEST
- -
2 The SS transmits a AUTHENTICATION
REQUEST message.
3 The UE transmits a AUTHENTICATION
RESPONSE message.
COMMAND message.
COMPLETE message.
ACCEPT message.
7 The UE transmits a TMSI REALLOCATION
COMPLETE message.
--> TMSI REALLOCATION
COMPLETE
- -
COMMAND message.
COMPLETE message.
ACCEPT message.
ACCEPT
- -
COMPLETE message.
COMPLETE
- -

U - S Message
REQUEST message with Update type =RA
Update'.
REQUEST
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1012 Release 9
1012
Table 13.1.3.3.3-1: Void
Table 13.1.3.3.3-2: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 13.1.3.3.2-
2)
UTRA-
FDD
as used for cell 5

E-UTRA

}
UTRA-
TDD
as used for cell 5

E-UTRA

}
}

Table 13.1.3.3.3-3: DLInformationTransfer (step 2, Table 13.1.3.3.2-2)
DLInformationTransfer ::=SEQUENCE {
c1 CHOICE {
dlInformationTransfer-r8 SEQUENCE {
dedicatedInfoNAS Set according to 36.508
Table 4.7.2-8A
CS SERVICE
NOTIFICATION

}
}
}
}
}

Table 13.1.3.3.3-4: ULInformationTransfer (step 4, Table 13.1.3.3.2-2)
c1 CHOICE {
Table 4.7.2-14A
EXTENDED
SERVICE
REQUEST

}
}
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1013 Release 9
1013
Table 13.1.3.3.3-5: Void
Table 13.1.3.3.3-6: RRCConnectionRelease (step 5, Table 13.1.3.3.2-2)
c1 CHOICE {
5
UTRA-
FDD
5
UTRA-
TDD
}
}
}

Table 13.1.3.3.3-7: RRC CONNECTION REQUEST (step 6, Table 13.1.3.3.2-2)
Establishment cause Registration

Table 13.1.3.3.3-8: SERVICE REQUEST (step 1, Table 13.1.3.3.2-3)
Derivation Path: 24.008 Table 9.4.20
Service type 001B Data

Handover / MT call
(1)
ensure that {
when { UE receives a Paging message with CN domain indicator set to CS }
}

(2)
ensure that {
when { SS transmits a MobilityFromEUTRACommand message with handover to a UTRA cell in a different
then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra cell and performs a RA
Update procedure }
}

(3)
UTRA cell and initiated a RA Update procedure }
ensure that {
then { UE transmits a PAGING RESPONSE on UTRA cell to set up MT CS call }
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1014 Release 9
1014

References: The conformance requirements covered in the current TC are specified in: TS 23.272, clause 7.2, 7.3, and
TS 24.301, clause 5.6.2.3.
[TS 23.272, clause 7.2]
The procedure for Mobile Terminating Call in idle mode is illustrated in figure 7.2-1.

1. IAM
3. IAM
4. Paging Request
5. Paging
6. Paging
2. SRI procedure in TS 23.018
G-MSC
eNodeB
RNC/BSC
UE MME
HSS
MSC
VLR
8. After the UE context setup the procedure continues as described the active
mode mobile terminated call procedures described in Clause 7.3 and 7.4.

If the eNodeB knows that PS HO is supported the procedure in clause 7.3 Mobile
Terminating call in Active Mode - PS HO supported is applied from step 2, in
Clause 7.3, and onwards

If the eNodeB knows that PS HO is not supported the procedure in clause 7.4
Mobile Terminating call in Active Mode No PS HO support is applied from step
2 in Clause 7.4, and onwards

7a. Extended Service Request
7b. Initial UE Context Setup
7a. Service Request

Figure 7.2-1: Mobile Terminating Call in idle mode

1. G-MSC receives IAM.
2. G-MSC retrieves routing information of the terminating UE by Send Routing Info procedures as specified in
TS 23.018 [5].
3. G-MSC sends IAM to the MSC on the terminating side as specified in TS 23.018 [5].
4. The MME receives a Paging Request (IMSI, VLR TMSI, Location Information) message from the MSC over a
SGs interface. The TMSI (or IMSI) received from the MSC is used by the MME to find the S-TMSI which is
used as the paging address on the radio interface If location information is reliably known by MME (i.e. MME
stores the list of TAs), the MME shall page the UE in all the TAs. If the MME does not have a stored TA list for
the UE, the MME should use the location information received from the MSC to page the UE.
NOTE 1: This procedure takes place before step 3, immediately after MSC receives MAP_PRN from HSS, if pre-
paging is deployed.
5. If the MME did not return an "SMS-only" indication to the UE during Attach or Combined TA/LA Update
procedures, the MME sends a Paging (as specified in TS 23.401 [2]) message to each eNodeB. The Paging
message includes a suitable UE Identity (i.e. S-TMSI or IMSI) and a CN Domain Indicator that indicates which
domain (CS or PS) initiated the paging message. In this case it shall be set to "CS" by the MME.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1015 Release 9
1015
procedures, the MME shall not send the paging to the eNodeBs and sends Paging Reject towards MSC to stop
CS Paging procedure and this CSFB procedure stops.
6. The radio resource part of the paging procedure takes place. The message contains a suitable UE Identity (i.e.
S-TMSI or IMSI) and a CN Domain indicator.
7a.The UE establishes an RRC connection and sends an Extended Service Request (CS Fallback Indicator) to MME.
The UE indicates its S-TMSI in the RRC signalling. The Extended Service Request message is encapsulated in
RRC and S1-AP messages. The CS Fallback Indicator indicates to the MME that CS Fallback for this UE is
required. The MME sends the SGs Service Request message to the MSC containing an indication that the UE
was in idle mode (and hence, for example, that the UE has not received any Calling Line Identification
information). Receipt of the SGs Service Request message stops the MSC retransmitting the SGs interface
Paging message.
NOTE 2: In order to avoid the calling party experiencing a potentially long period of silence, the MSC may use the
SGs Service Request message containing the idle mode indication as a trigger to inform the calling party
that the call is progressing.
7b. MME sends S1-AP: Initial UE Context Setup (UE capabilities, CS Fallback Indicator and other parameters
specified in TS 23.401 [2]) to indicate the eNodeB to move the UE to UTRAN/GERAN.
7c. The eNB shall reply with S1-AP: Initial UE Context Setup Response message.
8a. If the eNodeB knows that both the UE and the network support PS handover: The information flow continues as
described in clause 7.3 "Mobile Terminating call in Active Mode - PS HO supported" from step 2, in clause 7.3,
and onwards.
. If the eNodeB knows that either the UE or the network does not support PS handover: The information flow
continues as described in clause 7.4 "Mobile Terminating call in Active Mode No PS HO support" from step 2,
in clause 7.4, and onwards.
[TS 23.272, clause 7.3]

UE/MS
MME BSS/RNS
MSC
eNodeB SGSN
Serving
GW
2. Optional Measurement Report Solicitation
4. A/Iu-cs message (with Paging Response)
4. Paging Response
Location Area Update or Combined RA/LA Update
5. Signalling Connection Release 5. Connection Reject
If the MSC
is changed
3. PS HO as specified in 23.401 [2] (preparation phase and start of execution phase)
6. CS call establishment procedure
1d. S1-AP Message with CS Fallback indicator
7. PS HO as specified in 23.401 [2] (continuation of execution phase)
1a. Paging Request
1a. CS Paging Notification
1c. CS Paging Reject
1a. Service Request

Figure 7.3-1: CS Page in E-UTRAN, Call in GERAN/UTRAN Preparation Phase

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1016 Release 9
1016

1a. The MSC receives an incoming voice call and responds by sending a Paging Request (IMSI or TMSI, optional
Caller Line Identification and Connection Management information, CS call indicator) to the MME over a SGs
interface. The MSC only sends a CS Page for an UE that provides location update information using the SGs
interface. In active mode the MME has an established S1 connection and if the MME did not return the
"SMS-only" indication to the UE during Attach or Combined TA/LA Update procedures, the MME reuses the
existing connection to relay the CS Page to the UE.
procedures, the MME shall not send the CS Service Notification to the UE and shall send Paging Reject towards
MSC to stop CS Paging procedure, and this CSFB procedure stops.
The eNB forwards the paging message to the UE. The message contains CN Domain indicator and, if received
from the MSC, the Caller Line Identification.
The MME immediately sends the SGs Service Request message to the MSC. Receipt of the SGs Service Request
message stops the MSC retransmitting the SGs interface Paging message.
NOTE 1: The pre-configured policy may be used by UE to avoid being disturbed without Caller Line Identification
display and the detailed handling is to be decided by CT1 and CT6.
NOTE 2: This procedure can also take place immediately after MSC receives MAP_PRN from HSS, if pre-paging
is deployed. Caller Line Identification and CS call indicator are also provided in the case of pre-paging.
NOTE 3: In order to avoid the calling party experiencing a potentially long period of silence, the MSC may use the
SGs Service Request message as a trigger to inform the calling party that the call is progressing.
1b. UE sends an Extended Service Request (CS Fallback Indicator, Reject or Accept) message to MME. Extended
Service Request message is encapsulated in RRC and S1-AP messages. CS Fallback Indicator indicates to the
MME to perform CS Fallback. The UE may decide to reject CSFB based on Caller Line Identification.
1c. Upon receiving the Extended Service Request (CSFB, Reject), the MME sends Paging Reject towards MSC to
stop CS Paging procedure and this CSFB procedure stops.
1d. MME sends an S1-AP Request message to eNB that includes the UE Radio Capabilities and a CS Fallback
Indicator. This message: indicates to the eNB that the UE should be moved to UTRAN/GERAN.
2. The eNodeB may optionally solicit a measurement report from the UE to determine the target GERAN/UTRAN
cell to which PS handover will be performed.
3. The eNodeB triggers PS handover to a GERAN/UTRAN neighbour cell by sending a Handover Required
message to MME. In the following an inter-RAT handover from E-UTRAN to UTRAN or GERAN as specified
in TS 23.401 [2] begins. As part of this handover, the UE receives a HO from E-UTRAN Command and tries to
connect to a cell in the target RAT. The HO from E-UTRAN Command may contain a CS Fallback Indicator
which indicates to UE that the handover was triggered due to a CS fallback request. If the HO from E-UTRAN
Command contains a CS Fallback Indicator and the UE fails to establish connection to the target RAT, then the
UE considers that CS fallback has failed.
NOTE 4: During the PS HO the SGSN does not create a Gs association with the MSC/VLR.
4. If the Target RAT is UTRAN or GERAN Iu mode: The UE establishes an RRC connection and responds to the
paging by sending an RRC Paging Response as specified in TS 25.331 [7]. The CN Domain Indicator is set to
"CS" in the Initial Direct Transfer message.
If the Target RAT is GERAN A/Gb mode: The UE establishes an RR connection and responds to paging by
using the procedures specified in TS 44.018 [4] (i.e. UE requests and is assigned a dedicated channel where it
sends a SABM containing a Paging Response to the BSS and the BSS responds by sending a UA). Upon
receiving the SABM (containing a Paging Response message) the BSS sends a COMPLETE LAYER 3
INFORMATION message (containing a Paging Response message) to the MSC which indicates CS resources
have been allocated in the GERAN cell. After the establishment of the main signalling link as described in
TS 44.018 [4] the UE enters Dual Transfer Mode and the CS call establishment procedure completes.
NOTE 5: The BSS should be prepared to receive a Paging Response even when the corresponding Paging Request
has not been sent by this BSS.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1017 Release 9
1017
5. If the MSC serving the 2G/3G target cell is different from the MSC that served the UE while camped on
E-UTRAN, the MSC shall reject the Paging Response message by releasing the Iu connection for UTRAN or the
A/Gb connection for GERAN. The BSC/RNC in turn releases the signalling connection for UTRAN or GERAN
CS domain. The signalling connection release shall trigger the UE to perform a Location Area Update as
follows:
- If the target system operates in Network Mode of Operation (NMO) I the UE shall perform a combined
RA/LA update, as defined in TS 23.060 [3]. In this case, the SGSN establishes a Gs association with the
MSC/VLR as specified in TS 23.060 [3], which replaces the SGs association with the MME.
- If the target system operates in NMO II or III the UE performs a Location Area Update towards the MSC. In
this case, the MSC will release the SGs association with the MME.
6. The CS call establishment procedure is initiated.
7. After the UE moves to a cell in the target RAT, the inter-RAT handover from E-UTRAN to UTRAN or GERAN
as specified in TS 23.401 [2] is completed. At the end of this handover the UE may trigger the Routing Area
Update procedure when the sending of uplink packet data is possible. The detailed steps performed are as per
TS 23.401 [2].
With the exception of step 1c, above, Call Forwarding (see TS 23.082 [28]) is performed on the basis of the
TS 24.008 [21] signalling received on the GERAN/UTRAN cell.
If the UE remains on UTRAN/GERAN after the CS voice call is terminated the UE performs normal mobility
management procedures as defined in TS 23.060 [3] and TS 24.008 [21], i.e. if the UE is not registered in the current
RA/LA, the UE performs combined RA/LA update procedure when the target system operates in NMO I, or LA update
procedure when the target system operates in NMO II/III. Also for NMO I if the UE performed only RA update due to
the CS call the UE performs a combined RA/LA update (see TS 23.060 [3], clause 6.3.1) which creates the Gs
association.
[TS 24.301, clause 5.6.2.3]
The network may initiate the paging procedure for CS fallback when the UE is IMSI attached for non-EPS services (see
example in figure 5.6.2.3.1).
UE
MME
AS
Request paging
Paging


To notify the UE about an incoming mobile terminating CS service excluding SMS when a NAS signalling connection
exists, the EMM entity in the network shall send a CS SERVICE NOTIFICATION message. This message may also
include CS service related parameters (e.g. Calling Line Identification, SS or LCS related parameters).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1018 Release 9
1018
Upon reception of a paging indication, a UE that is IMSI attached for non-EPS services shall respond with an
EXTENDED SERVICE REQUEST. If the paging is received in EMM-IDLE mode, the UE shall respond immediately.
If the paging is received as NAS CS NOTIFICATION message in EMM-CONNECTED mode, the UE may request
upper layers input i.e. to accept or reject CS fallback before responding with an EXTENDED SERVICE REQUEST.
The response is indicated in the CSFB response information element in the EXTENDED SERVICE REQUEST
message in both EMM-IDLE and EMM-CONNECTED modes.
System Simulator:
- Cell 1 serving cell
- Cell 5 suitable neighbour cell
UE:
Preamble:
- The UE is in state Registered, Idle Mode (state 2) on Cell 1 according to [18].
Table 13.1.4.3.2-1 shows the cell power levels after the preamble.
T0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1019 Release 9
1019
U - S Message
on Cell 1 using S-TMSI with CN domain
indicator set to CS.
<-- Paging - -
that depends on the UE capability; the "lower
case letter" identifies a step sequence that
takes place if a capability is supported.
- - - -
2a1 IF the UE needs to request upper layer input
before accepting the CS fallback, the incoming
CS call is accepted at the UE through MMI or
AT command.
- - - -
message on Cell1.
message on Cell1.
containing an EXTENDED SERVICE
REQUEST with Service Type IE set to "mobile
terminating CS fallback or 1xCS fallback on
Cell 1?
--> RRCConnectionSetupComplete
REQUEST
1 P
Cell 1 with IE handover.
COMPLETE
2 P
RESPONSE on Cell 5?
COMMAND message on Cell 5 in order to
activate integrity protection.
described in steps 711 to 1417, the steps
specified in Table 13.1.4.3.2-3 should take
place.
- - - -
11-
17
Cell 5 using the UTRA reference radio bearer
parameters and combination UTRA PS RB +
Speech according to TS 36.508 subclause
4.8.3 and Table 4.8.3-1.
- - - -

U - S Message
AREA UPDATE message on Cell 5?
REQUEST
2 P
ACCEPT on Cell 5.
ACCEPT
- -
3 The UE sends ROUTING AREA UPDATE
COMPLETE message.
COMPLETE
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1020 Release 9
1020
Table 13.1.4.3.3-1: Void
Table 13.1.4.3.3-2: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 13.1.4.3.2-
2)
UTRA-
FDD
as used for cell 5

E-UTRA

}
UTRA-
TDD
as used for cell 5

E-UTRA

}
}


Table 13.1.4.3.3-3: Message Paging (step 1, Table 13.1.4.3.2-2)
1 entry
TMSI of the UE

}
cn-Domain[1] cs
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1021 Release 9
1021
Table 13.1.4.3.3-4: RRCConnectionSetupComplete (step 5, Table 13.1.4.3.2-2)

c1 CHOICE {
selectedPLMN-Identity Set to the PLMN selected
by upper layers

registeredMME Not present
Table 4.7.2-14A
EXTENDED
SERVICE
REQUEST

}
}
}
}

Table 13.1.4.3.3-5: Void
Table 13.1.4.3.3-6: Message MobilityFromEUTRACommand (step 6, Table 13.1.4.3.2-2)
c1 CHOICE {
csFallbackIndicator True
purpose CHOICE {
handover SEQUENCE {
targetRAT-Type Utra
COMMAND

COUNT value

}
}
}
}
}
}

Table 13.1.4.3.3-7: HANDOVER TO UTRAN COMMAND (step 6, Table 13.1.4.3.2-2)

13.1.5 Call setup from E-UTRAN RRC_CONNECTED / CS fallback to
UTRAN with handover / MO call
(1)
with { UE in E-UTRA RRC_CONNECTED state having requested CS call setup }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1022 Release 9
1022
ensure that {
when { UE receives a MobilityFromEUTRACommand message including a cs-FallbackIndicator set to
'true' and a targetRAT-Type set to 'utra' }
then { UE transmits a HANDOVER TO UTRAN COMPLETE message and continues the PS data service }
}

[TS 36.331, clause 5.4.3.3]
The UE shall:
1>if the MobilityFromEUTRACommand message includes the purpose set to 'handover':
2>if the targetRAT-Type is set to 'utra' or 'geran':
target RAT;
System Simulator:
UE:
None.
Preamble:
to [18].
- The UE has a valid TMSI (TMSI-1) and is registered in LAI-1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1023 Release 9
1023
U - S Message
<-- IP packet - -
2 The UE loops back the IP packet on the DRB
on Cell 1.
--> IP packet - -
3 Cause the UE to originate CS call. (see Note
1)
- - - -
4 The UE transmits an ULInformationTransfer
message on Cell 1.
This message includes an EXTENDED
SERVICE REQUEST message.
Cell 1.
TO UTRAN COMPLETE message on Cell 5?
COMPLETE
1 P
- Generic test procedure in TS 34.108
subclause 7.4.2.9.2.2 is performed on Cell 5
using the UTRA reference radio bearer
4.8.3 and Table 4.8.3-1.
NOTE: The UE performs Radio Bearer
Establishment in a UTRAN cell.
- - - -
COMMAND message on Cell 5 in order to
activate integrity protection.
9 The SS transmits an UTRAN MOBILITY
INFORMATION message to notify CN
information on Cell 5.
<-- UTRAN MOBILITY
INFORMATION
- -
10 The UE transmits an UTRAN MOBILITY
INFORMATION CONFIRM message on Cell 5.
--> UTRAN MOBILITY
INFORMATION CONFIRM
- -
This message includes a ROUTING AREA
the PS RAB on Cell 5.
<-- IP packet - -
on the PS RAB on Cell 5?
--> IP packet 1 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1024 Release 9
1024
Table 13.1.5.3.3-1: MobilityFromEUTRACommand (step 5, Table 13.1.5.3.2-1)
c1 CHOICE{
cs-FallbackIndicator true
purpose CHOICE{
handover SEQUENCE {
targetRAT-Type utra
COMMAND(UTRA RRC
message)

COUNT value

}
}
}
}
}
}

Table 13.1.5.3.3-2: HANDOVER TO UTRAN COMMAND (Table 13.1.5.3.3-1)
Derivation Path: 36.508, Table 4.7B.1-1, condition UTRA PS RB

Table 13.1.5.3.3-3: EXTENDED SERVICE REQUEST (step 4, table 13.1.5.3.2-1)
Service type 0000 'mobile originating
CS fallback or 1xCS
fallback'


13.1.6 Void
13.1.7 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with
redirection / MT call
(1)
with {UE in E-UTRA RRC_IDLE state }
ensure that {
when { UE receives a Paging message for CS service, and UE has Set up RRCConnection with the E-
UTRA CELL}
}
(2)
ensure that {
when { SS transmits an RRCConnectionRelease message with redirection to a GSM cell in a different

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1025 Release 9
1025
then { UE tunes to GSM cell and performs a RA Update procedure }
}

(3)
GSM cell and initiated a RA Update procedure }
ensure that {
then { UE transmits a PAGING RESPONSE on GSM cell to set up MT CS call }
}

in: TS 23.272, clause 7.4, and TS 24.301, clause 5.6.2.3..
[TS 23.272, clause 7.2]
The procedure for Mobile Terminating Call in idle mode is illustrated in figure 7.2-1.

1. IAM
3. IAM
4. Paging
5. Paging
6. Paging
8a. PS handover
8b. eNB assisted cell change
8d. Paging Response
9a. Establish CS connection
2. SRI procedure in TS 23.018
G-MSC
eNodeB
RNC/BSC
UE MME
HSS
MSC
VLR
Location Area Update and Roaming Retry for CS Fallback (clause 7.5)
9b. RRC Release
Option 2:
MSC is
changed
Option 1:
MSC is not
changed
9b. Connection Reject
8d. Paging Response
8c. Location Area Update
7b. Initial UE Context Setup

Figure 7.2-1: Mobile Terminating Call in idle mode

1. G-MSC receives IAM.
2. G-MSC retrieves routing information of the terminating UE by Send Routing Info procedures as specified in
TS 23.018 [5].
3. G-MSC sends IAM to the MSC on the terminating side as specified in TS 23.018 [5].
4. The MME receives a Paging (IMSI, VLR TMSI, Location Information) message from the MSC over a SGs
interface. The TMSI (or IMSI) received from the MSC is used by the MME to find the S-TMSI which is used as
the paging address on the radio interface If location information is reliably known by MME (i.e. MME stores the

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1026 Release 9
1026
list of TAs), the MME shall page the UE in all the TAs. If the MME does not have a stored TA list for the UE,
the MME should use the location information received from the MSC to page the UE.
NOTE 1: This procedure takes place before step 3, immediately after MSC receives MAP_PRN from HSS, if pre-
paging is deployed.
5. The MME sends a Paging (as specified in TS 23.401 [2]) message to each eNodeB. The Paging message
includes a suitable UE Identity (i.e. S-TMSI or IMSI) and a CN Domain Indicator that indicates which domain
(CS or PS) initiated the paging message. In this case it shall be set to "CS" by the MME.
6. The radio resource part of the paging procedure takes place. The message contains a suitable UE Identity (i.e.
S-TMSI or IMSI) and a CN Domain indicator.
7a.The UE establishes an RRC connection and sends an Extended Service Request (CS Fallback Indicator) to MME.
The UE indicates its S-TMSI in the RRC signalling. The Extended Service Request message is encapsulated in
RRC and S1-AP messages. The CS Fallback Indicator indicates to the MME that CS Fallback for this UE is
required.
7b. MME sends S1-AP: Initial UE Context Setup (UE capabilities, CS Fallback Indicator and other parameters
specified in TS 23.401 [2]) to indicate the eNodeB to move the UE to UTRAN/GERAN.
8a. Target RAT has PS HO capability: Upon receipt of the Initial UE Context Setup message with a CS Fallback
Indicator the eNodeB may optionally solicit measurement reports from the UE to determine the target cell to
which PS handover will be performed. A PS handover is then performed as specified in TS 23.401 [2]. As part of
this PS handover, the UE receives a HO from E-UTRAN Command that may contain a CS Fallback Indicator,
which indicates to UE that the handover is triggered due to a CS fallback request. If the HO from E-UTRAN
Command contains a CS Fallback Indicator and the UE fails to establish connection to the target RAT, then the
UE considers that CS fallback has failed.
8b. Target RAT has no PS HO capability. Upon receipt of the Initial UE Context Setup message with a CS Fallback
Indicator the eNodeB may optionally solicit measurement reports from the UE to determine the target cell to
redirect the UE to. After that, the eNB releases the RRC Connection with a redirection info to change to CS
capable RATs (RAT, frequency, cell info). As an option the inter-RAT system information might be provided by
the eNodeB using the NACC procedure for GERAN. In this case the UE receives in inter-RAT cell change order
that may contain a CS Fallback Indicator which indicates to UE that the cell change order is triggered due to a
CS fallback request. If the inter-RAT cell change order contains a CS Fallback Indicator and the UE fails to
establish connection to the target RAT, then the UE considers that CS fallback has failed.
8c. If the UE obtains LA/RA information of the new UTRAN/GERAN cell (e.g. based on the system information or
redirection info) and the LA/RA of the new cell is different from the one stored in the UE, it performs a Location
Area Update or a Combined RA/LA procedure if the target system operates in Network Mode of Operation
(NMO) I, according to TS 23.060 [3].
8d. The UE responds with a page response message to the MSC as follows:
- If Target RAT is UTRAN or GERAN Iu mode, the UE establishes an RRC connection and responds to the
paging in an RRC Initial Direct Transfer message as specified in TS 25.331 [7]. The CN Domain Indicator is
set to "CS" in the Initial Direct Transfer message. When received at the RNC, the Paging Response message
is sent in an RANAP Initial UE message to the MSC.
- If Target RAT is GERAN A/Gb mode: the UE establishes an RR connection by using the procedures
specified in TS 44.018 [6] (i.e. UE requests and is assigned a dedicated channel where it sends a SABM
containing a layer 3 Service Request message =PAGING RESPONSE to the BSS and the BSS responds by
sending a UA). After the establishment of the main signalling link as described in TS 44.018 [4] the UE
enters either Dual Transfer Mode or Dedicated Mode and the CS call establishment procedure completes.
When received at the BSC, the Paging Response message is sent in a BSSAP COMPLETE LAYER 3
INFORMATION message to the MSC as specified in TS 48.008 [6].
NOTE 2: The BSS should be prepared to receive a PAGING RESPONSE even when a corresponding PAGING
REQUEST has not been sent by this BSS. Also, the MSC should be prepared to receive a paging response
after a relatively long time from when the CS Paging was sent (step 4).
9a. In case the MSC serving the 2G/3G cell is the same as the MSC that served the UE while camped on LTE, it
shall stop the paging response timer and establish the CS connection.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1027 Release 9
1027
9b. If the MSC that receives the paging response is different from the MSC that sent the paging request and if the
Location Area Update / Combined RA/LA Update was not performed in step 8c, the MSC shall reject the page
response by releasing the A/Iu-cs connection. The BSC/RNC in turn releases the RRC/RR connection. The
RRC/RR release shall trigger the UE to perform a Location Area Update as follows:
- If the target system operates in Network Mode of Operation (NMO) I the UE shall perform a combined
RA/LA update, as defined in TS 23.060 [3].
- If the target system operates in NMO II or III the UE performs a Location Area Update towards the MSC.
When the target system operates in Network Mode of Operation (NMO) I then, if the UE is still in UTRAN/GERAN
after the CS voice call is terminated, and if a combined RA/LA update has not already been performed, the UE
performs a combined RA/LA update procedure. This procedure is used to create a Gs association between the
MSC/VLR and the SGSN, and to release the SGs association.
When the target system operates in Network Mode of Operation (NMO) II or III then, if the UE is still in
UTRAN/GERAN after the CS voice call is terminated, and if a LA update has not already been performed, the UE
performs a LA update procedure. This procedure is used to release the SGs association between the MSC/VLR and the
MME.
[TS 24.301, clause 5.6.2.3]
services (see example in figure 5.6.2.3.1).
UE
MME
AS
Request paging
Paging


entity in the network shall send a CS SERVICE NOTIFICATION message. This message may also include CS service
related parameters (e.g. Calling Line Identification, SS or LCS related parameters).
Upon reception of a paging indication, the UE shall respond with an EXTENDED SERVICE REQUEST. If the paging
is received in EMM-IDLE mode, the UE shall respond immediately. If the paging is received as NAS CS
NOTIFICATION message in EMM-CONNECTED mode, the UE may request upper layers input i.e. to accept or reject
CS fallback before responding with an EXTENDED SERVICE REQUEST. The response is indicated in the CSFB
response information element in the EXTENDED SERVICE REQUEST message in both EMM-IDLE and EMM-
CONNECTED modes.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1028 Release 9
1028
System Simulator:
UE:
None.
Preamble:
Table 13.1. 7.3.2-1 shows the cell power levels after the preamble.
T0
camping on Cell 1 is guaranteed. GERAN Cell Power dBm - -80

U - S Message - -
1 The SS transmits a Paging message on Cell1. <-- Paging - -
message on Cell1.
message on Cell1.
Cell1.
5 Check: Does the UE transmint an
ULInformationTransfer message on Cell1? The
meesage includes an EXTENDED SERVICE
REQUEST message.
1 P
6 The SS transmits a RRCConnectionRelease
redirectedCarrierInfo including geran
frequency of Cell 24.
7 Check: Does the UE transmit a CHANNEL
REQUEST message on Cell 24?
TS 36.508 subclause 6.4.2.9are performed on
Cell 24.
Note: Routing area updating procedure is
performed.
-
-
- -
RESPONSE on Cell 24?
19-
36
TS 51.010-1 subclause 10.1.3 are performed
on Cell 24.
-
-
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1029 Release 9
1029
Table 13.1.7.3.3-1: Void
Table 13.1.7.3.3-2: Void
Table 13.1.7.3.3-3: Paging (step1, Table 13.1.7.3.2-2)
1 entry
imsi Set to the value of the
IMSI of the UE

}
cn-Domain[1] Cs
}
}

c1 CHOICE {
Table 4.7.2-14A
EXTENDED
SERVICE
REQUEST

}
}
}
}
}

Table 13.1.7.3.3-5: Void
c1 CHOICE {
geran f11
}
}
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1030 Release 9
1030
13.1.8 Call setup from E-UTRA RRC_CONNECTED/ CS fallback to GSM
with Redirection / MO call
(1)
ensure that {
when { UE is triggered by upper layers to perform a circuit switched voice call }
}

(2)
ensure that {
when { SS transmits an RRCConnectionRelease message with redirection to a GERAN cell in a
different location area and operating in NMO I }
then { UE tunes to GERAN cell and performs combined LA/RA update procedure, or alternatively LA
Update procedure only}
}
(3)
ensure that {
when { UE has tuned to GERAN cell and performed LA Update procedure }
then { UE transmits GPRS SUSPENSION REQUEST to suspend data services over GPRS }
}
(4)
message with Service Type IE set to "mobile originating CS fallback or 1xCS fallback and tuned to
GERAN cell and initiated a LA Update procedure }
ensure that {
when { After UE tuned to GERAN cell and performed LA Update procedure }
then { UE completes MO circuit switched voice call setup procedure on GERAN }
}

in: TS 23.272, clause 6.3, and TS 24.301, clause 5.6.1.1.
[TS 23.272, clause 6.3]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1031 Release 9
1031

UE/MS
MME BSS/RNS
MSC
eNodeB
2. Optional Measurement Report Solicitation
9. CS MO call
10b. Location Area Update
10a. Service Reject
In case MSC is
changed
10c. CS MO call
6. LA Update or Combined RA/LA Update or RA Update or LA Update and RA Update
3a. NACC,
S-GW
4. S1-AP: S1 UE Context Release Request
1b. S1-AP message with CS Fallback indicator
7a. Suspend (see 23.060)
8. Update bearer(s)
SGSN
7b. Suspend Request / Response
11. Routing Area Update or Combined RA/LA Update
3b. RRC connection release

Figure 6.3-1: CS Call Request in E-UTRAN, Call in GERAN/UTRAN without PS HO

1a. The UE sends an Extended Service Request (CS Fallback Indicator) to the MME. Extended Service Request
message is encapsulated in RRC and S1-AP messages. CS Fallback Indicator indicates MME to perform CS
Fallback. The UE only transmits this request if it is attached to CS domain (with a combined EPS/IMSI Attach)
and can not initiate an IMS voice session (because e.g. the UE is not IMS registered or IMS voice services are
not supported by the serving IP-CAN, home PLMN or UE).
1b. The MME sends an S1-AP Request message to eNB that includes a CS Fallback Indicator. This message
indicates to the eNB that the UE should be moved to UTRAN/GERAN.
2. The eNodeB may optionally solicit a measurement report from the UE to determine the target GERAN cell to
which the redirection procedure will be performed.
3a. If the UE and network support inter-RAT cell change order to GERAN and the target cell is GERAN: The
eNodeB triggers an inter-RAT cell change order (optionally with NACC) to a GERAN neighbour cell by
sending an RRC message to the UE. The inter-RAT cell change order may contain a CS Fallback Indicator
which indicates to UE that the cell change order is triggered due to a CS fallback request. If the inter-RAT cell
change order contains a CS Fallback Indicator and the UE fails to establish connection to the target RAT, then
the UE considers that CS fallback has failed. Service Request procedure is considered to be successfully
completed when cell change order procedure is completed successfully.
3b. If the UE or the network does not support inter-RAT handover from E-UTRAN to GERAN/UTRAN nor inter-
RAT cell change order to GERAN: The eNodeB triggers RRC connection release with redirection to
GERAN/UTRAN instead of PS HO or NACC.
NOTE 2: Service Request procedure supervision timer shall be sufficiently long considering the optional
measurement reporting at step 2.
4. The eNodeB sends an S1 UE Context Release Request (Cause) message to the MME. Cause indicates that the
UE is not available for the PS service.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1032 Release 9
1032
5. S1 UE Context in the eNodeB is released as specified in TS 23.401 [2].
6. The UE moves to the new cell in GERAN/UTRAN and establishes a radio signalling connection.
If the UE obtains LA information of the new cell (e.g. based on the system information) and the LA of the new
cell is different from the one stored in the UE, it performs a Location Area Update or a Combined RA/LA
Update procedure in case the target system operates in Network Mode of Operation (NMO) I. Alternatively, in
NMO I, the UE in GERAN may perform LA update over the RR connection instead of combined RA/LA update
over the packet access, as defined in TS 24.008 [21], clause 4.7.5.2.5, unless enhanced CS establishment in DTM
is supported.
If the UE moves to an UTRAN cell and ISR is not active or the RA of the cell is different to the one the UE is
registered in, the UE performs a Routing Area Update. This can be performed as part of the combined RA/LA
Update procedure when the LA of the new cell is different from the one stored in the UE and the target system
operates in NMO I.
7. If the target RAT is GERAN and DTM is not supported, the UE starts the Suspend procedure specified in
TS 23.060 [3], clause 16.2.1.1.2. This triggers the SGSN to send a Suspend Request message to the MME. The
MME returns a Suspend Response to the SGSN, which contains the MM and PDP contexts of the UE.
8. If PS services are suspended, the MME starts the preservation of non-GBR bearers and the deactivation of GBR
bearers.
9. The UE continues with the MO call setup procedure.
10a. In case the MSC serving the 2G/3G cell is different from the MSC that served the UE while camped on
E-UTRAN and if the Location Area Update / Combined RA/LA Update was not performed in step 6, the MSC
shall reject the call setup service request, if implicit location update is not performed.
10b. A UE detecting that the MSC rejected the service request shall perform the Location Area Update according
to existing GERAN or UTRAN procedures.
10c. After completion of the Location Area Update the UE continues with a MO call setup procedure.
11. After the CS voice call is terminated and if the UE is in GERAN and PS services are suspended, then (as
specified in TS 23.060 [3]) the UE shall resume PS services by sending a Routing Area Update Request message
to the SGSN. The Update Type depends on the mode of operation of the GERAN network, e.g. in mode I a
Combined RA/LA Update is used and in mode II or III Routing Area Update is used.
If the UE remains on UTRAN/GERAN after the CS voice call is terminated the UE performs normal mobility
management procedures as defined in TS 23.060 [3] and TS 24.008 [21], i.e. if the UE is not registered in the current
RA/LA, the UE performs combined RA/LA update procedure when the target system operates in NMO I, or separate
LA update and RA update procedures when the target system operates in NMO II/III. Also for NMO I if the UE
performed only RA update due to the CS call the UE performs a combined RA/LA update (see TS 23.060 [3],
clause 6.3.1) which creates the Gs association.
[TS 24.301, clause 5.6.1.1]
- the network has downlink signalling pending;
- the UE has uplink signalling pending;
- the UE or the network has user data pending and the UE is in EMM-IDLE mode;
CS fallback;
- the network has downlink cdma2000
signalling pending; or
- the UE has uplink cdma2000
signalling pending.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1033 Release 9
1033
The service request procedure is initiated by the UE, however, for the downlink transfer of signalling, cdma2000

signalling or user data in EMM-IDLE mode, the trigger is given by the network by means of the paging procedure (see
subclause 5.6.2).
a) the UE in EMM-IDLE mode receives a paging request with CN domain indicator set to "PS" from the network;
b) the UE, in EMM-IDLE mode, has pending user data to be sent;
c) the UE, in EMM-IDLE mode, has uplink signalling pending;
d) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use CS fallback and has a mobile
originating CS fallback request from the upper layer;
e) the UE in EMM-IDLE mode is configured to use CS fallback and receives a paging request with CN domain
indicator set to "CS", or the UE in EMM-CONNECTED mode is configured to use CS fallback and receives a
CS SERVICE NOTIFICATION message;
f) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use 1xCS fallback and has a mobile
originating 1xCS fallback request from the upper layer;
g) the UE in EMM-CONNECTED mode is configured to use 1xCS fallback and accepts cdma2000
signalling
messages containing a 1xCS paging request; or
h) the UE, in EMM-IDLE mode, has uplink cdma2000
signalling pending.
[TS 24.008, clause 4.5.1.1, item d)]
d) When the MS is IMSI attached for CS services via EMM combined procedures, as described in
3GPP TS 24.301 [120], and the MS is camping on an E-UTRAN cell, the MM sublayer requests EMM to initiate
a service request procedure for CS fallback. The MM connection establishment is delayed until the MS changes
to a GERAN or UTRAN cell.
If the MS enters a GERAN or UTRAN cell, then the MS shall initiate the MM connection establishment and
send a CM SERVICE REQUEST message. If the MS determines that it is in a different location area than the
stored location area, the MS shall first initiate a normal location updating procedure or a combined routing area
update procedure, depending on Network Mode of Operation. The MM connection establishment is delayed until
successful completion of the normal location updating or combined routing area update procedure. In A/Gb
mode, if the MS is a non DTM MS, or a DTM MS in a cell not supporting DTM, the MS may perform location
area updating procedure instead of combined routing area update procedure in NMO I.
System Simulator:
- 2 cells, one E-UTRA and one GERAN cell:
- Cell 24 suitable neighbour GERAN cell
o Cell 24 system information indicates that NMO 1 is used
- The parameters settings and power levels for Cell 1 and Cell 24 are selected according to [18], [5] so that
camping on Cell 1 is guaranteed and no cell re-selection to Cell 24 can take place (GERAN priority is lower
than serving and S
Cell 1
>Thresh
Cell 1,low
).
UE:
None

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1034 Release 9
1034
Preamble:
- The UE is in state Generic RB Established (state 3) according to [18], with ATTACH ACCEPT message
content modified as indicated in table 13.1.8.3.3-1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1035 Release 9
1035
U - S Message
1 Cause the UE to originate CS call. (see
Note 1)
- - - -
ULInformationTranfer message containing
an EXTENDED SERVICE REQUEST with
Service Type IE set to "mobile originated
CS fallback or 1xCS fallback on Cell 1?
REQUEST
1 P
RRCConnectionRelease message on Cell
1 with IE redirectedCarrierInfo including
ARFCN of Cell 24.
EXCEPTION: In case the UE does not
choose to perform combined RA/LA
procedure, the UE will perform LA update.
In this case steps 4a1-4a8 are executed.

4a1 UE transmits CHANNEL REQUEST
message to initiate LA Update procedure
--> CHANNEL REQUEST - -
4a2 A RR connection is established <-- IMMEDIATE ASSIGNMENT - -
4a3 Check: Does the UE transmit LOCATION
UPDATING REQUEST?
REQUEST
2 P
4a4 The SS transmits AUTHENTICATION
REQUEST
4a5 The UE transmits AUTHENTICATION
RESPONSE
4a6 The SS transmits CIPHERING MODE
COMMAND
<-- CIPHERING MODE COMMAND - -
4a7 The UE transmits CIPHERING MODE
COMPLETE
--> CIPHERING MODE COMPLETE - -
4a8 The SS transmits MM LOCATION
UPDATING ACCEPT
- EXCEPTION: In case UE chooses to
perform combined RA/LA procedure, steps
4b1-4b13 are executed.
- - - -
4b1 UE transmits CHANNEL REQUEST
message to initiate combined LA/RA
Update procedure
--> CHANNEL REQUEST - -
4b2 An uplink TBF is established - - - -
4b3 -
4b12
UE will perform steps 1 to 10 of the generic
test procedure in TS 36.508 table 6.4.2.9-1
(Routing area update procedure on a new
GERAN cell) are performed on Cell 24.
NOTE: UE performing combined RA/LA
updating procedure.
- - - -
4b13 Check: Does the UE transmit a ROUTING
--> ROUTING AREA UPDATING
COMPLETE
2 P
5 Check: The UE transmits GPRS
SUSPENSION REQUEST to indicate to
the network to suspend transmission of
data on GPRS.
--> GPRS SUSPENSION REQUEST 3 P
6-21 UE will perform steps 1 to 16 of the generic
test procedure in TS 51.010 subclause
10.2.3 (mobile originating speech calls) are

- - - -
22 Check: Does the UE send CONNECT
ACKNOWLEDGE to complete the MO
circuit switched voice call setup
procedure?
--> CONNECT ACKNOWLEDGE 4 P
23 The voice call is ended on the UE - - - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1036 Release 9
1036
Table 13.1.8.3.3-1: ATTACH ACCEPT for cell 1 (preamble)
Location area identification
LAC 2

Table 13.1.8.3.3-2: Void
Table 13.1.8.3.3-3: SystemInformationBlockType7 for cell 1 (preamble and all steps, Table 13.1.8.3.2-2
and Table 13.1.8.3.2-3)
carrierFreqsInfoList SEQUENCE (SIZE (1..
maxGNFG)) OF SEQUENCE {

CarrierFreqsGERAN SEQUENCE [n] {
}
}
}
cellReselectionPriority 3 Lower priority than
E-UTRA

}
}

c1 CHOICE {
13.1.8.3.3-5
EXTENDED
SERVICE
REQUEST

}
}
}
}
}

Table 13.1.8.3.3-5: EXTENDED SERVICE REQUEST (step 2, Table 13.1.8.3.2-2)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1037 Release 9
1037
c1 CHOICE {
Geran f11
}
}
}

Table 13.1.8.3.3-7: GPRS SUSPENSION REQUEST (step 5, Table 13.1.8.3.2-2)
Protocol discriminator RR
Service type '00110100'B GPRS
SUSPENSION
REQUEST

Suspension cause '00000000'B Mobile originating
call

13.1.9 to 13.1.14 Void
redirection / MT call / UTRAN cell is barred
(1)
with { UE in E-UTRA RRC_CONNECTED state having transmitted EXTENDED SERVICE REQUEST message for
mobile terminating CS call and a UTRA cell which broadcasts SystemInformationBlockType3 indicating
access barred for mobile originating CS call is available }
ensure that {
when { UE receives an RRCConnectionRelease message with redirection to a UTRA carrier }
then { UE transmits a PAGING RESPONSE message in the UTRA cell }
}

[TS 25.331, clause 8.1.1.6.3]
The UE shall apply the following handling with respect to any Access Class Barring information:
1>if in idle mode:
...
2>if neither the IE "Paging Permission with Access Control Parameters For PLMN Of MIB", the IE "Paging
Permission with Access Control Parameters For OperatorN" nor the IE "Paging Permission with Access
Control Parameters For All" to be applied according to the requirements above is included in System
Information Block Type 3:
3>if the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", the IE "Domain Specific
Access Restriction Parameters For OperatorN" or the IE "Domain Specific Access Restriction Parameters
For All" to be applied according to the requirements above is included in System Information Block Type
3 the UE shall:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1038 Release 9
1038
4>act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific
Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT
TRANSFER message to the CS domain, as specified in [4]. If "no restriction" was indicated in
restriction status, the UE shall act as if no Access Class is barred in the IE "Domain Specific Access
Class Barred List", and ignore the IE "Access Class Barred List" in the IE "Cell Access Restriction";
4>act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific
Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT
TRANSFER message to the PS domain, as specified in [4]. If "no restriction" was indicated in
restriction status, the UE shall act as if no Access Class is barred in the IE "Domain Specific Access
Class Barred List", and ignore the IE "Access Class Barred List" in the IE "Cell Access Restriction";
4>upon transition to UTRA RRC connected, the UE shall:
5>store that Domain Specific Access Restriction Parameters to the variable "DSAC_PARAM" and
maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC
connection is released;
5>act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain
Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS
domain, as specified in [4];
5>act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain
Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS
domain, as specified in [4].
System Simulator:
- System information combination 4 as defined in TS 36.508 section 4.4.3.1 is used in E-UTRA cells.
UE:
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1039 Release 9
1039
U - S Message
1 The SS transmits a Paging message on Cell 1. <-- Paging - -
message on Cell 1.
message on Cell 1.
Cell 1.
This message includes an EXTENDED
SERVICE REQUEST message.
message on Cell 1.
message on Cell 1.
Cell 1.
message on Cell 1.
omplete
- -
redirectionInformation including UTRA-
CarrierFreq of Cell 5.
--> RRC CONNECTION REQUEST - -
SETUP message on Cell 5.
SETUP COMPLETE message on Cell 5.
COMPLETE
- -
described in step 13 to 24 the steps specified
in Table 13.1.15.3.2-2 should take place.
- - - -
13 The UE transmits a PAGING RESPONSE
message.
14-
24
Cell 5 using the UTRA reference radio bearer
4.8.3 and Table 4.8.3-1.
- - - -

U - S Message
REQUEST message.
REQUEST
- -
ACCEPT message.
ACCEPT
- -
COMPLETE message.
COMPLETE
- -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1040 Release 9
1040
Table 13.1.15.3.3-1: System Information Block type3 for Cell 5 (preamble and all steps, Table
13.1.15.3.2-1)
Information Element Value/remark
Access Class Barred List
- Access Class Barred0 barred
Domain Specific Access Restriction Parameters For
PLMN Of MIB

-CS Domain Specific Access Restriction restriction
-Domain Specific Access Class Barred List
-Access Class Barred List
-PS Domain Specific Access Restriction no restriction
Paging Permission with Access Control Parameters For
PLMN Of MIB

- Paging Response Restriction Indication none
- Location/Registration Restriction Indicator All
- Location/Registration
- Location/Registration Access Restriction no restriction

Table 13.1.15.3.3-2: Paging (step 1, Table 13.1.15.3.2-1)
1 entry
cn-Domain cs
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1041 Release 9
1041
Table13.1.15.3.3-3: RRCConnectionReconfiguration (step 7, Table 13.1.15.3.2-1)

c1 CHOICE {
5
UTRA-
FDD
5
UTRA-
TDD
}
}
}
}
}


13.2 RRC connection reconfiguration
13.2.1 RRC connection reconfiguration / E-UTRA to E-UTRA
(1)
with { UE has a default EPS bearer context }
ensure that {
context }
}
(2)
ensure that {
context }
}
(3)
with { UE has a default EPS bearer context and successful completion of the intra-frequency
handover }
ensure that {
context }
}
(4)
with { UE has a default EPS bearer context and successful completion of the intra-frequency
handover }
ensure that {

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1042 Release 9
1042
context }
}

Same Conformance requirements as in clause 8.2.4.2.
References: The conformance requirements covered in the present TC are specified in: TS23.401, clause 5.5.1.1.1.
[TS 23.401, clause 5.5.1.1.1]
These procedures are used to hand over a UE from a source eNodeB to a target eNodeB using the X2 reference point. In
these procedures the MME is unchanged. Two procedures are defined depending on whether the Serving GW is
unchanged or is relocated. In addition to the X2 reference point between the source and target eNodeB, the procedures
rely on the presence of S1-MME reference point between the MME and the source eNodeB as well as between the
MME and the target eNodeB.
The handover preparation and execution phases are performed as specified in TS 36.300 [5].
If the serving PLMN changes during handover, the source eNB shall initiate an S1-based handover instead of an X2-
based handover.
When the UE receives the handover command it will remove any EPS bearers for which it did not receive the
corresponding EPS radio bearers in the target cell. As part of handover execution, downlink packets are forwarded from
the source eNodeB to the target eNodeB. When the UE has arrived to the target eNodeB, downlink data forwarded from
the source eNodeB can be sent to it. Uplink data from the UE can be delivered via the (source) Serving GW to the PDN
GW. Only the handover completion phase is affected by a potential change of the Serving GW, the handover
preparation and execution phases are identical.
If the MME receives a rejection to a NAS procedure (e.g. dedicated bearer establishment/modification/release; location
reporting control; NAS message transfer; etc.) from the eNodeB with an indication that an X2 handover is in progress
(see TS 36.300 [5]), the MME shall reattempt the same NAS procedure either when the handover is complete or the
handover is deemed to have failed. The failure is known by expiry of the timer guarding the NAS procedure.
System Simulator:
- Cell 1 and Cell 2
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.
various time instants of the test execution. Row marked "T0" denotes the initial conditions after Preamble, while

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1043 Release 9
1043
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -91
The power level value shall be such that
A3 (M2 +Hys <M1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-91 -85
The power level value shall be such that
A3 (M2 - Hys >M1).

U - S Message - -
<-- IP packet - -
bearer context on Cell 1?
- - 1,2 P
message on Cell 1.
omplete
- -
- - - -
completion of the intra frequency handover.
omplete
- -
<-- IP packet - -

- - 3,4 P

Table 13.2.1.3.3-1: ACTIVATE TEST MODE (preamble)

Table 13.2.1.3.3-2: RRCConnectionReconfiguration (Step 3, Table 13.2.1.3.2-2)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1044 Release 9
1044
Table 13.2.1.3.3-3: MeasurementConfiguration (Step 3, Table 13.2.1.3.2-2)
1 entry
GENERIC(f1)

}
reportConfigToAddModifyList SEQUENCE (SIZE
1 entry
}
measIdToAddModifyList SEQUENCE (SIZE
1 entry
measId[1] 1
}

Table 13.2.1.3.3-4: MeasurementReport (Step 6, Table 13.2.1.3.2-2)
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 2

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}

Table 13.2.1.3.3-5: RRCConnectionReconfiguration (Step 7, Table 13.2.1.3.2-2)

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1045 Release 9
1045
Table 13.2.1.3.3-6: MobilityControlInfo (step 7, Table 13.2.1.3.2-2)
Cell 2

}
}

13.3
13.3.1 Intra-system connection re-establishment
13.3.1.1 Intra-system connection re-establishment / Radio link recovery while T310 is
running
(1)
with { UE in E-UTRA RRC_CONNECTED state and has data to transmit}
ensure that {
when { UE detects radio link recovery while T310 is running}
then { UE resumes the RRC connection without explicit signalling and continues data transfer}
}

Refer to TS 36.523-1 clause 8.5.1.5.2.
System Simulator:
- Cell 1
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.
clause.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1046 Release 9
1046
T0 RS EPRE
dBm/1
5kHz
P
default

Power level from 36.508
clause 6.2.2.1. P
default
as
serving cell.

T1 RS EPRE
dBm/1
5kHz
P
off

P
off
as as non-suitable Off
cell.
T2 RS EPRE
dBm/1
5kHz
P
default

P
default
as serving cell.

U - S Message - -
<-- IP packet - -
2 The SS reduce DL RS TX power level of Cell 1
from T0 to T1 in table 13.3.1.1.3.2-1.
- - - -
3 The SS waits for 1.5s. T310 is 2s. - - - -
4 The SS recovers DL RS TX power level of Cell
1 from T1 to T2 in table 13.3.1.1.3.2-1.
- - - -
bearer context on Cell 1?( Note 1)

--> IP packet 1 P
Note 1: Triggered when timer T_delay_modeB (IP PDU delay time) expires and pending uplink data exist in
buffered PDCP SDUs according to [25] clause 5.4.4.3.

Table 13.3.1.1.3.3-1: ACTIVATE TEST MODE (preamble, Table 13.3.1.1.3.2-2)

IP PDU delay 0 0 0 0 0 1 0 1 5 seconds

Table 13.3.1.1.3.3-3: SystemInformationBlockType2 (preamble and all steps, Table 13.3.1.1.3.2-2)
ue-TimersAndConstants {
t310 ms2000
}
}

13.3.1.2 Intra-system connection re-establishment / Re-establishment of a new
connection when further data is to be transferred
(1)
ensure that {

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1047 Release 9
1047
when { UE detects radio link failure on expiry of timer T310 }
then { UE starts timer T311 and UE initiates the RRC Connection re-establishment procedure }
}

(2)
ensure that {
when { UE detects radio link failure and successfully completes the RRC Connection re-
establishment procedure and has data available for transmission }
then { UE use the DRB configured by network side and resume the data transfer }
}

Refer to TS 36.523-1 clause 8.5.1.1.2.
System Simulator:
UE:
None.
Preamble:
- The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1048 Release 9
1048
U - S Message - -
<-- IP packet - -
2 The SS changes the power level of cell 1 to
non-suitable Off and changes the power level
of cell 2 to suitable according to TS 36.508
- - - -
3 Check: Does the UE initiate an RRC
connection re-establisment procedure and
transmit an
message on Cell 2?
Request
1 P
4 The SS transmits
RRCConnectionReestablishment message
5 UE transmits an
message
Complete
- -
6 The SS transmits
7 UE transmits an
RRCConnectionConfigurationComplete
message
omplete
- -
--> IP packet 2 P

None.
13.4 Mobility
13.4.1 Intra-system mobility
13.4.1.2 Inter-frequency mobility / E-UTRA to E-UTRA packet
(1)
ensure that {
when { UE receives downlink data on the radio bearer associated with the default EPS bearer
context }
}

(2)
ensure that {
context }
}

(3)
with { UE has a default EPS bearer context and successful completion of the inter-frequency
handover }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1049 Release 9
1049
ensure that {
context }
}

(4)
with { UE has a default EPS bearer context and successful completion of the inter-frequency
handover }
ensure that {
context }
}

References: The conformance requirements covered in the present TC are specified in: TS 23.401, clauses 5.5.1.1.1.
[TS 23.401, clause 5.5.1.1.1]
These procedures are used to hand over a UE from a source eNodeB to a target eNodeB using the X2 reference point. In
these procedures the MME is unchanged. Two procedures are defined depending on whether the Serving GW is
unchanged or is relocated. In addition to the X2 reference point between the source and target eNodeB, the procedures
rely on the presence of S1-MME reference point between the MME and the source eNodeB as well as between the
MME and the target eNodeB.
The handover preparation and execution phases are performed as specified in TS 36.300 [5].
If the serving PLMN changes during handover, the source eNB shall initiate an S1-based handover instead of an X2-
based handover.
When the UE receives the handover command it will remove any EPS bearers for which it did not receive the
corresponding EPS radio bearers in the target cell. As part of handover execution, downlink packets are forwarded from
the source eNodeB to the target eNodeB. When the UE has arrived to the target eNodeB, downlink data forwarded from
the source eNodeB can be sent to it. Uplink data from the UE can be delivered via the (source) Serving GW to the PDN
GW. Only the handover completion phase is affected by a potential change of the Serving GW, the handover
preparation and execution phases are identical.
If the MME receives a rejection to a NAS procedure (e.g. dedicated bearer establishment/modification/release; location
reporting control; NAS message transfer; etc.) from the eNodeB with an indication that an X2 handover is in progress
(see TS 36.300 [5]), the MME shall reattempt the same NAS procedure either when the handover is complete or the
handover is deemed to have failed. The failure is known by expiry of the timer guarding the NAS procedure.
System Simulator:
- Cell 1 and Cell 3
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 4) on Cell 1 according to [18] using the UE TEST LOOP
MODE B.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1050 Release 9
1050
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -97
A3 (M3 <M1).
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -73
A3 (M3 >M1).

U - S Message - -
<-- IP packet - -
--> IP packet 1,2 P
Cell 1 to setup inter frequency measurement
and reporting for event A3.
message on Cell 1.
omplete
- -
5 The SS changes Cell 3 parameters according
to the row "T1" in table 13.4.1.2.3.2-1
- - - -
Cell 1 to order the UE to perform inter
completion of the inter frequency handover.
omplete
- -
<-- IP packet - -
--> IP packet 3,4 P



3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1051 Release 9
1051
Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition INTER-FREQ
1 entry
GENERIC(f2)

}
1 entry
reportConfigId[1] IdReportConfigEUTRA-
A3

}
1 entry
measId[1] 1
reportConfigId[1] IdReportConfigEUTRA-
A3

}
}

c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 3

rsrpResult (0..97)
rsrqResult (0..34)
}
}
}
}
}
}
}
}


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1052 Release 9
1052
Table 13.4.1.2.3.3-6: MobilityControlInfo (step 7, Table 13.4.1.2.3.2-2)
Cell 3

as used for Cell 3

}
}

13.4.2 Inter-system mobility packet
13.4.2.1 Inter-system mobility / E-UTRA to UTRA packet
(1)
ensure that {
context }
}
(2)
ensure that {
context }
}
(3)
with { UE has a radio access bearer context and successful completion of the inter-system handover }
ensure that {
when { UE receives downlink data on the radio bearer associated with the radio access bearer
context }
}
(4)
with { UE has a radio access bearer context and successful completion of the inter-system handover }
ensure that {
then { UE transmits the uplink data on the radio bearer associated with the radio access bearer
context }
}

in: TS 23.401, clauses 5.5.2.1.2, 5.5.2.1.3.
[TS 23.401, clause 5.5.2.1.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1053 Release 9
1053

UE
Source
eNodeB
Target RNC Source MME Target SGSN
Serving GW
HSS
1. Handover Initiation
2. Handover Required
3. Forward Relocation Request
5. Relocation Request
5a. Relocation Request Acknowledge
8 . Create Indirect Data Forwarding Tunnel Request
7. Forward Relocation Response
PDN GW
8 a. Create Indirect Data Forwarding Tunnel Response
Uplink and Downlink User Plane PDUs

Target
Serving GW
4. Create Session Request
4a. Create Session Response
6. Create Indirect Data Forwarding Tunnel Request
6a. Create Indirect Data Forwarding Tunnel Response
Source

Figure 5.5.2.1.2-1: E-UTRAN to UTRAN Iu mode Inter RAT HO, preparation phase

1. The source eNodeB decides to initiate an Inter-RAT handover to the target access network, UTRAN Iu mode. At
this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and source
eNodeB, GTP tunnel(s) between source eNodeB, Serving GW and PDN GW.
NOTE 1: The process leading to the handover decision is outside of the scope of this specification.
2. The source eNodeB sends a Handover Required (S1AP Cause, Target RNC Identifier, Source eNodeB Identifier,
Source to Target Transparent Container) message to the source MME to request the CN to establish resources in
the target RNC, target SGSN and the Serving GW. The bearers that will be subject to data forwarding (if any)
are identified by the target SGSN in a later step (see step 7 below).
3. The source MME determines from the 'Target RNC Identifier' IE that the type of handover is IRAT Handover to
UTRAN Iu mode. The Source MME initiates the Handover resource allocation procedure by sending a Forward
Relocation Request (IMSI, Target Identification, MM Context, PDN Connections, MME Tunnel Endpoint
Identifier for Control Plane, MME Address for Control plane, Source to Target Transparent Container, RAN
Cause, MS Info Change Reporting Action (if available), ISR Supported, TI(s)) message to the target SGSN. The
information ISR Supported is indicated if the source MME is capable to activate ISR for the UE. When ISR is
activated the message should be sent to the SGSN that maintains ISR for the UE when this SGSN is serving the
target identified by the Target Identification. This message includes all PDN Connections active in the source
system and for each PDN Connection includes the associated APN, the address and the uplink Tunnel endpoint
parameters of the Serving GW for control plane, and a list of EPS Bearer Contexts. RAN Cause indicates the
S1AP Cause as received from source eNodeB.
The target SGSN maps the EPS bearers to PDP contexts 1-to-1 and maps the EPS Bearer QoS parameter values
of an EPS bearer to the pre-Rel-8 QoS parameter values of a bearer context as defined in Annex E
Prioritization of PDP Contexts is performed by the target core network node, i.e. target SGSN.
The MM context contains security related information, e.g. supported ciphering algorithms as described in
TS 29.274 [43]. Handling of security keys is described in TS 33.401 [41].
The target SGSN shall determine the Maximum APN restriction based on the APN Restriction of each bearer
context in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction
value.
4. The target SGSN determines if the Serving GW is to be relocated, e.g., due to PLMN change. If the Serving GW
is to be relocated, the target SGSN selects the target Serving GW as described under clause 4.3.8.2 on "Serving

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1054 Release 9
1054
GW selection function", and sends a Create Session Request message (IMSI, SGSN Tunnel Endpoint Identifier
for Control Plane, SGSN Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s)
for user plane, PDN GW address(es) for control plane, and PDN GW TEID(s) for control plane, the Protocol
Type over S5/S8) per PDN connection to the target Serving GW. The Protocol Type over S5/S8 is provided to
Serving GW which protocol should be used over S5/S8 interface.
The target SGSN establishes the EPS Bearer context(s) in the indicated order. The SGSN deactivates the EPS
Bearer contexts which cannot be established.
4a. The target Serving GW allocates its local resources and returns a Create Session Response (Serving GW
address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane,
Serving GW TEID for control plane) message to the target SGSN.
5. The target SGSN requests the target RNC to establish the radio network resources (RABs) by sending the
message Relocation Request (UE Identifier, Cause, CN Domain Indicator, Integrity protection information (i.e.
IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering
algorithms), RAB to be setup list, Source RNC to Target RNC Transparent Container, Service Handover related
information). If the Access Restriction is present in the MM context, the Service Handover related information
shall be included by the target SGSN for the Relocation Request message in order for RNC to restrict the UE in
connected mode to handover to the RAT prohibited by the Access Restriction.
For each RAB requested to be established, RABs To Be Setup shall contain information such as RAB ID, RAB
parameters, Transport Layer Address, and Iu Transport Association. The RAB ID information element contains
the NSAPI value, and the RAB parameters information element gives the QoS profile. The Transport Layer
Address is the Serving GW Address for user plane (if Direct Tunnel is used) or the SGSN Address for user plane
(if Direct Tunnel is not used), and the Iu Transport Association corresponds to the uplink Tunnel Endpoint
Identifier Data in Serving GW or SGSN respectively.
Ciphering and integrity protection keys are sent to the target RNC to allow data transfer to continue in the new
RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure.
Information that is required to be sent to the UE (either in the Relocation Command message or after the
handover completion message) from RRC in the target RNC shall be included in the RRC message sent from the
target RNC to the UE via the transparent container. More details are described in TS 33.401 [41].
In the target RNC radio and Iu user plane resources are reserved for the accepted RABs. Cause indicates the
RAN Cause as received from source MME. The Source RNC to Target RNC Transparent Container includes the
value from the Source to Target Transparent Container received from the source eNodeB.
5a. The target RNC allocates the resources and returns the applicable parameters to the target SGSN in the message
Relocation Request Acknowledge (Target RNC to Source RNC Transparent Container, RABs setup list, RABs
failed to setup list).
Upon sending the Relocation Request Acknowledge message the target RNC shall be prepared to receive
downlink GTP PDUs from the Serving GW, or Target SGSN if Direct Tunnel is not used, for the accepted RABs.
Each RAB in the RABs setup list is defined by a Transport Layer Address, which is the target RNC Address for
user data, and the Iu Transport Association, which corresponds to the downlink Tunnel Endpoint Identifier for
user data.
Any EPS Bearer contexts for which a RAB was not established are maintained in the target SGSN and the UE.
These EPS Bearer contexts shall be deactivated by the target SGSN via explicit SM procedures upon the
completion of the routing area update (RAU) procedure.
6. If 'Indirect Forwarding' and relocation of Serving GW apply and Direct Tunnel is used, the target SGSN sends a
Create Indirect Data Forwarding Tunnel Request message (Target RNC Address and TEID(s) for data
forwarding) to the Serving GW. If 'Indirect Forwarding' and relocation of Serving GW apply and Direct Tunnel
is not used, then the target SGSN sends a Create Indirect Data Forwarding Tunnel Request message (SGSN
Address and TEID(s) for data forwarding) to the Serving GW.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the
anchor point for the UE.
6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es)
and TEID(s) for data forwarding) message to the target SGSN.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1055 Release 9
1055
7. The target SGSN sends the message Forward Relocation Response (Cause, SGSN Tunnel Endpoint Identifier for
Control Plane, SGSN Address for Control Plane, Target to Source Transparent Container, Cause, RAB Setup
Information, Additional RAB Setup Information, Address(es) and TEID(s) for User Traffic Data Forwarding,
Serving GW change indication) to the source MME. Serving GW change indication indicates a new Serving GW
has been selected. The Target to Source Transparent Container contains the value from the Target RNC to
Source RNC Transparent Container received from the target RNC.
The IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' defines the destination tunnelling endpoint
for data forwarding in target system, and it is set as follows:
- If 'Direct Forwarding' applies, or if 'Indirect Forwarding' and no relocation of Serving GW apply and Direct
Tunnel is used, then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the
addresses and GTP-U tunnel endpoint parameters to the Target RNC received in step 5a.
- If 'Indirect Forwarding' and relocation of Serving GW apply, then the IE 'Address(es) and TEID(s) for User
Traffic Data Forwarding' contains the addresses and GTP-U tunnel endpoint parameters to the Serving GW
received in step 6a. This is independent from using Direct Tunnel or not.
- If 'Indirect Forwarding' applies and Direct Tunnel is not used and relocation of Serving GW does not apply,
then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the addresses and GTP-U
tunnel endpoint parameters to the Target SGSN.
8. If "Indirect Forwarding" applies, the Source MME sends the message Create Indirect Data Forwarding Tunnel
Request (Address(es) and TEID(s) for Data Forwarding (received in step 7)), EPS Bearer ID(s)) to the Serving
GW used for indirect forwarding.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the
anchor point for the UE.
8a. The Serving GW returns the forwarding parameters by sending the message Create Indirect Data Forwarding
Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding). If the Serving GW
doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es)
and TEID(s) will not be included in the message.
[TS 23.401, clause 5.5.2.1.3]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1056 Release 9
1056

UE
Source
eNodeB
Target RNC Source MME Target SGSN
Serving GW
HSS PDN GW
Uplink and Downlink User Plane PDUs
1. Handover Command
2. HO from E-UTRAN Command
-
Sending of
uplink data
possible
4. UTRAN Iu Access Procedures
5. Relocation Complete
6. Forward Relocation Complete Notification
6a. Forward Relocation Complete Acknowledge
7. Modify Bearer Request
8a. Modify Bearer Response
9. Modify Bearer Response
Uplink and Downlink User Plane PDUs (Via Target SGSN if Direct Tunnel is not used)
4a. Handover to UTRAN Complete
Downlink User Plane PDUs
If Direct Forwarding applies
If Indirect Forwarding applies.
Target
Serving GW
(A)
8. Modify Bearer Request
Via Target SGSN in case Direct Tunnel is not used
10. Routeing Area Update procedure
11. Delete Session Request
(B)
11a. Delete Session Response
11b. Release Resources
For Serving GW relocation Steps 7, 8 and 9,
and the following User Plane path, will be
handled by Target Serving GW
12. Delete Indirect Data Forwarding Tunnel Request
Source
12a. Delete Indirect Data Forwarding Tunnel Response
13. Delete Indirect Data Forwarding Tunnel Request
13a. Delete Indirect Data Forwarding Tunnel Response

Figure 5.5.2.1.3-1: E-UTRAN to UTRAN Iu mode Inter RAT HO, execution phase

NOTE: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402 [2]. Step (B) shows PCRF
interaction in the case of PMIP-based S5/S8. Steps 8 and 8a concern GTP based S5/S8
The source eNodeB continues to receive downlink and uplink user plane PDUs.
1. The source MME completes the preparation phase towards source eNodeB by sending the message Handover
Command (Target to Source Transparent Container, E-RABs to Release List, Bearers Subject to Data
Forwarding List). The "Bearers Subject to Data forwarding list" IE may be included in the message and it shall
be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation
phase (Step 7 of the preparation phase) when 'Direct Forwarding' applies, or the parameters received in Step 8a
of the preparation phase when 'Indirect Forwarding' applies.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1057 Release 9
1057
The source eNodeB initiates data forwarding for bearers specified in the "Bearers Subject to Data Forwarding
List". The data forwarding may go directly to target RNC or alternatively go via the Serving GW if so decided
by source MME and or/ target SGSN in the preparation phase.
2. The source eNodeB will give a command to the UE to handover to the target access network via the message HO
from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that
the target RNC has set-up in the preparation phase. The details of this E-UTRAN specific signalling are
described in TS 36.300 [5].
Upon the reception of the HO from E-UTRAN Command message containing the Handover Command message,
the UE shall associate its bearer IDs to the respective RABs based on the relation with the NSAPI and shall
suspend the uplink transmission of the user plane data.
3. Void.
4. The UE moves to the target UTRAN Iu (3G) system and executes the handover according to the parameters
provided in the message delivered in step 2. The procedure is the same as in step 6 and 8 in clause 5.2.2.2 in
TS 43.129 [8] with the additional function of association of the received RABs and existing Bearer Id related to
the particular NSAPI.
The UE may resume the user data transfer only for those NSAPIs for which there are radio resources allocated in
the target RNC.
The UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI", if any EPS bearer
context activated after the ISR was activated in the UE exists.
System Simulator:
- Cell 1 and Cell 5
UE:
None.
Preamble:
- The UE is in state Generic RB Established (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.
T0
Cell-specific RS
EPRE
dBm/15k
Hz
-85 -
entering conditions for event B2 are not
satisfied.
CPICH_Ec
dBm/3.8
4 MHz
- -22.5
T1
Cell-specific RS
EPRE
dBm/15k
Hz
-100 -
entering conditions for event B2 are
satisfied.
CPICH_Ec
dBm/3.8
4 MHz
- -12

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1058 Release 9
1058
U - S Message - -
<-- IP packet - -
--> IP packet 1,2 P
Cell 1 to setup inter RAT measurement and
reporting for event B2.
message on Cell 1.
omplete
- -
5 The SS changes the power level for Cell 1 and
Cell 5 according to the row "T1" in table
13.4.2.1.3.2-1
- - - -
5.
Cell 1 to order the UE to perform inter system
handover to Cell 5.
8 The UE transmit a HANDOVER TO UTRAN
COMPLETE message on Cell 5 to confirm the
successful completion of the inter system
handover.
COMPLETE
- -
9-
15
NOTE: The UE performs RAU procedure.
- - - -
the DRB associated with the RAB context on
Cell 5.
<-- IP packet - -
on the DRB associated with the RAB context
on Cell 5?
--> IP packet 3,4 P



3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1059 Release 9
1059
Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition UTRAN
1 entry
measObject[1] MeasObjectUTRA-
GENERIC(f8)

}
1 entry
reportConfigId[1] IdReportConfigInterRAT-
B2-UTRA

B2-UTRA (-90, -18)

}
1 entry
measId[1] 1
reportConfigId[1] IdReportConfigInterRAT-
B2-UTRA

}
}

Derivation Path: 36.508, table 4.6.1-5
c1 CHOICE{
measId 1
rsrpResult (0..97)
rsrqResult (0..34)
}
1 entry
Cell 5

utra-RSCP (-5..91)
utra-EcN0 (0..49)
}
}
}
}
}
}
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1060 Release 9
1060
c1 CHOICE{
purpose CHOICE {
handover SEQUENCE {
targetRAT-Type utra
COMMAND

COUNT value

}
}
}
}
}
}


14 ETWS
14.1 ETWS reception in RRC_IDLE state / Duplicate detection
14.1.1 Test Purpose (TP)
(1)
with { UE in RRC_IDLE state and follow the reception of Paging message with etws-Indication }
ensure that {
when { UE start to acquire ETWS message from SIB10 and SIB11 }
then { UE successfully received the ETWS message and activated the User Alerting popup
display }
}

14.1.2 Conformance requirements
5.2.2.17, 5.2.2.18, 5.3.2.3; TS 23.041 clause 9.1.2.
[TS 36.331, clause 5.2.2.4]
The UE shall:

1>if the UE is ETWS capable:
2>upon entering a cell during RRC_IDLE, following successful handover or upon connection re-establishment:
3> discard any previously buffered warningMessageSegment;
3>clear, if any, the current values of messageIdentifier and serialNumber for
SystemInformationBlockType11;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1061 Release 9
1061
2>when the UE acquires SystemInformationBlockType1 following ETWS indication, upon entering a cell
during RRC_IDLE, following successful handover or upon connection re-establishment:
3>if schedulingInfoList indicates that SystemInformationBlockType10 is present:
4>start acquiring SystemInformationBlockType10 immediately;
NOTE 2: UEs shall start acquiring SystemInformationBlockType10 and SystemInformationBlockType11 as
described above even when systemInfoValueTag in SystemInformationBlockType1 has not changed.
[TS 36.331, clause 5.2.2.17]
Upon receiving SystemInformationBlockType10, the UE shall:
1>forward the received warningType, warningSecurityInfo (if present), messageIdentifier and serialNumber to
upper layers;
[TS 36.331, clause 5.2.2.18]
1>if there is no current value for messageIdentifier and serialNumber for SystemInformationBlockType11; or
1>if either the received value of messageIdentifier or of serialNumber or of both are different from the current
values of messageIdentifier and serialNumber for SystemInformationBlockType11:
2>use the received values of messageIdentifier and serialNumber for SystemInformationBlockType11 as the
current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2>discard any previously buffered warningMessageSegment;
2>if all segments of a warning message have been received:
3>assemble the warningMessage from the received warningMessageSegment;
3>forward the received warningMessage, messageIdentifier, serialNumber and dataCodingScheme to upper
layers;
3>stop reception of SystemInformationBlockType11;
3>discard the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;
2>else:
3>store the received warningMessageSegment;
3>continue reception of SystemInformationBlockType11;
1>else if all segments of a warning message have been received:
2>forward the received complete warningMessage, messageIdentifier, serialNumber and dataCodingScheme to
upper layers;
1>else:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1062 Release 9
1062
[TS 36.331, clause 5.3.2.3]

1>if the etws-Indication is included and the UE is ETWS capable:
2>re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information
modification period boundary;
2>if the schedulingInfoList indicates that SystemInformationBlockType10 is present:
3>acquire SystemInformationBlockType10;
[TS 23.041, clause 9.1.2]
...

RNC
UE
5-b. Paging
5-a. Broadcast
information
7. Report-Success
3. Write-Replace
8. Ack
SGSN
NodeB
1. Registration and Security procedures;
Current time
4. Broadcast Request
6. User
Alerting
5-c. Primary
Notification
with Security
CBC
2. Information
GEC

Figure 4b
...
6. The UE alert the user immediately, using "warning type" value,
- upon the reception of the paging message, if the UE has been configured to receive ETWS warnings over the
paging message, and the UE has authenticated the core network of the NodeB it is camped on, or
- if the UE has not been configured to receive ETWS warnings over the paging message, and it received the
optional primary notification and security checks based on "timestamp" and "digital signature" for this
notification passed.
NOTE: If the UE received the ETWS warnings over the paging and also received the optional primary
notification, it will silently discard the optional primary notification.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1063 Release 9
1063
NOTE: When the "warning type" is 'test', the UE silently discards the paging message, and the optional primary
notification, and do not perform the reception of the broadcast message described below. However, the
UE specially designed for testing purposes may perform user alerting described above and proceed to the
reception of the broadcast message described below
NOTE: If the UE has been configured to receive ETWS warnings over paging message but it has not
authenticated the core network of the NodeB it is camped on, the UE does not receive the paging message
and the optional primary notification, and do not perform the reception of the broadcast message
described below.
Upon the reception of the paging message, whether the UE is configured to receive ETWS warnings over paging
message or not, the UE activates the reception of the broadcast messages containing the "warning message".as
the secondary notification, as follows:
- If both the "digital signature" and "timestamp" are present in the "warning message" and security checks fail,
then the UE notifies the user of this fact and stops the user alerting.
- If both the "digital signature" and "timestamp" are present and security checks pass, then the UE indicates the
contents of the "warning message" to the user along with an indication that the message has been
authenticated.
- In other cases, the UE indicates the contents of the "warning message" to the user along with an indication
that the message has not been authenticated.
Unless both the "digital signature" and "timestamp" are present and the security checks pass, the UE shall ignore
the message, return to normal idle mode, and ignore paging messages with the "ETWS indication" for the next
[X] seconds.
NOTE: Repetition period [X] is subject to regulatory requirements.
The UE shall consider a message duplicated if the combination of "message identifier" and "serial number"
matches that of the previous message received from the same PLMN. The UE shall ignore messages detected as
duplicated. If both the "digital signature" and "timestamp" are present, the UE shall perform security check
before duplicate message detection. Duplicate message detection shall be performed independently for primary
and secondary notifications.
7. The RNC node sends a BMC REPORT-SUCCESS to the CBC in response to Write-Replace.
8. CBC sends acknowledgement message to CBE.
14.1.3 Test description
14.1.3.1 Pre-test conditions
System Simulator:
- Cell 1
UE:
None.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1064 Release 9
1064
14.1.3.2 Test procedure sequence
Table 14.1.3.2-1: Main behaviour
U - S Message - -
1 The SS include an ETWS message with new
messageIdentifier and serialNumber in
SystemInformationBlockType11 and transmit a
Paging message including etws-Indication on
Cell 1 (NOTE1).
<-- Paging - -
2 Check: Does the UE indicate the contents of
the "warning message" to the user?
- - 1 P
3 The SS wait for 10s. - - - -
4 The SS include an ETWS message with same
Cell 1 (NOTE1).
<-- Paging - -
- - 1 F
NOTE1: SystemInformationBlockType11 contain 3 segments.

14.1.3.3 Specific message contents
Table 14.1.3.3-1: SystemInformationBlockType1 for Cell 1 (all steps, Table 14.1.3.2-1)
Combination 8 in TS
36.508 section 4.4.3.1
SIB2, SIB3, SIB10
and SIB11 are
transmitted

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1065 Release 9
1065
Table 14.1.3.3-2: SystemInformationBlockType10 for Cell 1 (all steps, Table 14.1.3.2-1 )
messageIdentifier '0001 0001 0000 0010'B ETWS message
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber
- Geographical Scope (2 bit)

- Message Code (10 bit)

- Emergency User Alert (1 bit)

- Popup (1 bit)

- Update Number (4 bit)
'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

Octet 1 bit 5 ~Octet 2 bit
4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

warningType
- Warning Type Value (7 bit)


- Popup (1 bit)

- Padding (7 bit)
'0000 0101 1000 0000'B
Octet 1 bit 7 ~1

Octet 1 bit 0

Octet 2 bit 7

Octet 2 bit 6 ~bit 0

Earthquake and
Tsunami;
Activate
emergency user
alert;
Activate Popup.
[see TS 23.041]
'000 0000'B

warningSecurityInfo Not present
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1066 Release 9
1066
Table 14.1.3.3-3: SystemInformationBlockType11 (1
st
Segment) for Cell 1 (all steps, Table 14.1.3.2-1)
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

warningMessageSegmentType notLastSegment
warningMessageSegmentNumber 0
warningMessageSegment Octetstring of N where N 1 and
less than 1246.
[see TS 23.041]

dataCodingScheme Bitstring (8) ID of the
alphabet/coding and the
applied language [see TS
23.041]

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1067 Release 9
1067
nd
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

less than 1246.
[see TS 23.041]

dataCodingScheme Not present
}

rd
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

warningMessageSegmentType lastSegment
less than 1246.
[see TS 23.041]

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1068 Release 9
1068
Table 14.1.3.3-6: Paging (step 1 and step 4, Table 14.1.3.2-1)
systemInfoModification Not present
etws-Indication true
}

14.2 ETWS reception in RRC_CONNECTED state / Duplicate
detection
(1)
with { UE in RRC_CONNECTED state and follow the reception of Paging message with etws-Indication }
ensure that {
when { UE start to acquire ETWS message from SIB10 and SIB11 }
display }
}

5.2.2.17, 5.2.2.18, 5.3.2.3; TS 23.041 clause 9.1.2.
[TS 36.331, clause 5.2.2.4]
The UE shall:

[TS 36.331, clause 5.2.2.17]
upper layers;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1069 Release 9
1069
[TS 36.331, clause 5.2.2.18]
layers;
2>else:
upper layers;
1>else:
[TS 36.331, clause 5.3.2.3]

[TS 23.041, clause 9.1.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1070 Release 9
1070
...

RNC
UE
5-b. Paging
5-a. Broadcast
information
7. Report-Success
3. Write-Replace
8. Ack
SGSN
NodeB
Current time
6. User
Alerting
5-c. Primary
Notification
with Security
CBC
2. Information
GEC

Figure 4b
...
described below.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1071 Release 9
1071
authenticated.
[X] seconds.
System Simulator:
- Cell 1
UE:
None.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1072 Release 9
1072
U - S Message - -
Cell 1 (NOTE1).
<-- Paging - -
- - 1 P
Cell 1 (NOTE1).
<-- Paging - -
- - 1 F

Combination 8 in TS
36.508 section 4.4.3.1
SIB2, SIB3, SIB10
and SIB11 are
transmitted

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1073 Release 9
1073
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

warningType


- Popup (1 bit)

- Padding (7 bit)
'0000 0101 1000 0000'B
Octet 1 bit 7 ~1

Octet 1 bit 0

Octet 2 bit 7


Earthquake and
Tsunami;
Activate
emergency user
alert;
Activate Popup.
[see TS 23.041]
'000 0000'B

warningSecurityInfo Not present
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1074 Release 9
1074
st
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

less than 1246.
[see TS 23.041]

23.041]

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1075 Release 9
1075
nd
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

less than 1246.
[see TS 23.041]

}

rd
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

less than 1246.
[see TS 23.041]

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1076 Release 9
1076
}

14.3 ETWS reception in RRC_IDLE state / NITZ timestamp
security check
(1)
with { UE in RRC_IDLE state and follow the reception of Paging message with etws-Indication }
ensure that {
when { UE start to acquire ETWS message from SIB10 with warningSecurityInfo and SIB11 }
display }
}

5.2.2.17, 5.2.2.18, 5.3.2.3; TS 23.041 clause 9.1.2.
[TS 36.331, clause 5.2.2.4]
The UE shall:

[TS 36.331, clause 5.2.2.17]
upper layers;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1077 Release 9
1077
[TS 36.331, clause 5.2.2.18]
layers;
2>else:
upper layers;
1>else:
[TS 36.331, clause 5.3.2.3]

[TS 23.041, clause 9.1.2]

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1078 Release 9
1078
...

RNC
UE
5-b. Paging
5-a. Broadcast
information
7. Report-Success
3. Write-Replace
8. Ack
SGSN
NodeB
Current time
6. User
Alerting
5-c. Primary
Notification
with Security
CBC
2. Information
GEC

Figure 4b
...
described below.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1079 Release 9
1079
authenticated.
[X] seconds.
System Simulator:
- Cell 1
UE:
None.
Preamble:
U - S Message - -
Cell 1 (NOTE1, NOTE2).
<-- Paging - -
- - 1 F
Cell 1 (NOTE1, NOTE3).
<-- Paging - -
- - 1 P
NOTE2: SystemInformationBlockType10 include IE "warningSecurityInfo" with illegal security information (e.g.
incorrect timestamp).
NOTE3: SystemInformationBlockType10 include IE "warningSecurityInfo" with legal security information.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1080 Release 9
1080
Combination 8 in TS
36.508 section 4.4.3.1
SIB2, SIB3, SIB10
and SIB11 are
transmitted

}

Table 14.3.3.3-2: SystemInformationBlockType10 for Cell 1 (all steps, Table 14.3.3.2-1 )
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

warningType


- Popup (1 bit)

- Padding (7 bit)
'0000 0101 1000 0000'B
Octet 1 bit 7 ~1

Octet 1 bit 0

Octet 2 bit 7


Earthquake and
Tsunami;
Activate
emergency user
alert;
Activate Popup.
[see TS 23.041]
'000 0000'B

warningSecurityInfo
- Year
- Month
- Day
- Hour
- Minute
- Second
- Time zone
- Digital Signature
Octet 1 ~Octet 50
Octet 1, bits 1-8
Octet 2, bits 1-8
Octet 3, bits 1-8
Octet 4, bits 1-8
Octet 5, bits 1-8
Octet 6, bits 1-8
Octet 7, bits 1-8
Octet 8 ~Octet 50, bits
1-8

2 Digits: (Semi-
octets) - Year,
Month, Day, Hour,
Minute, Second &
Time zone
[see TS 23.040]

43 byte digital
signature
[see TS 23.040]

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1081 Release 9
1081
st
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

less than 1246.
[see TS 23.041]

23.041]

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1082 Release 9
1082
nd
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

less than 1246.
[see TS 23.041]

}

rd
identifier for
earthquake and
tsunami message
[see TS 23.041]

serialNumber



- Popup (1 bit)

'0011 0000 0000 0000'B
Octet 1 bit 7 ~6

4
Octet 1 bit 5

Octet 1 bit 4

Octet 2 bit 3 ~0

Cell wide;

'11 0000 0000'B

Activate
emergency user
alert;
Activate popup;

For each update,
incremented by
one.
[see TS 23.041]

less than 1246.
[see TS 23.041]

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1083 Release 9
1083
}

15 Mobility management based on DSMIPv6 (Dual-
Stack Mobile IPv6)
15.1 Discovery of the home agent via DNS
(1)
with { UE has acquired an IP address and UE is configured with a DNS server address and UE is
configured with the HA-APN Network Identifier }
ensure that {
when { UE is configured to discover IP address of Home Agent via DNS }
then { UE transmits a DNS Query with QNAME set to FQDN of the Home Agent }
}

5.1.2.1.2.
[TS 24.303, clause 5.1.2.1.1]
The first procedure the UE needs to perform for DSMIPv6 initial attach is the discovery of the node acting as the HA.
The UE can discover the IP addresses of the HA in one of the four following ways:
- via DNS;
- via attach procedure for 3GPP access or trusted non-3GPP access (if supported) based on protocol configuration
options;
- via IKEv2 during tunnel setup to ePDG for untrusted non-3GPP accesses;
- via DHCPv6.
If the UE does not obtain the IP addresses of the HA via PCO during the 3GPP or trusted non-3GPP (if supported)
attach or via IKEv2 signalling, it shall follow either the procedures described in subclause 5.1.2.1.5 or the procedures
described in subclause 5.1.2.1.2. The UE may be configured to perform both procedures in parallel or one of the two
procedures only in case the other failed.
[TS 24.303, clause 5.1.2.1.2]
A UE performing Home Agent discovery based on DNS shall support the implementation of standard DNS mechanisms.
The UE shall perform DNS Lookup by Home Agent Name as specified in IETF RFC 5026 [10].The QNAME shall be
set to the requested HA-APN. The HA-APN shall be constructed as specified in 3GPP TS 23.003 [17]. If a HA has both
an IPv4 and an IPv6 address, the corresponding DNS record should be configured with both 'AAAA' and 'A' records.
Accordingly the UE should perform one DNS lookup procedure to retrieve both 'AAAA' and 'A' records. The DNS
server replies with one 'AAAA' and one 'A' record.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1084 Release 9
1084
System Simulator:
- Cell 1.
UE:
- The UE is configured to discover the Home Agent address via DNS.
- The UE is configured with a DNS server address.
- The UE is configured with the HA-APN Network Identifier.
Preamble:
- The UE has acquired an IP address.
U - S Message
1 The UE transmits a DNS Query message with
QNAME set to FQDN of the Home Agent
(derived from HA-APN Network Identifier and
PLMN information).
--> DNS Query 1 P
2 The SS transmits a DNS Response message
with the IPv6 and IPv4 addresses of the Home
Agent.
<-- DNS Response - -

Table 15.1.3.3-1: Message DNS Query (step 1, Table 15.1.3.2-1)
QR= 0 query
OPCODE= 0000 QUERY
QNAME= Fully Qualified Domain
Name of the Home Agent
Derived from HA-
APN Network
Identifier and
PLMN information
as per TS 23.003
clause 21.2

QTYPE= A This is the query
for the IPv4
address

QCLASS= IN
QNAME= Fully Qualified Domain
Name of the Home Agent
Derived from HA-
APN Network
Identifier and
PLMN information
as per TS 23.003
clause 21.2

QTYPE= AAAA This is the query
for the IPv6
address

QCLASS= IN

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1085 Release 9
1085
Table 15.1.3.3-2: Message DNS Response (step 2, Table 15.1.3.2-1)
QR= 1 response
OPCODE= 0000 QUERY
QNAME= Same as received in
DNS Query

QTYPE= A
QCLASS= IN
QNAME= Same as received in
DNS Query

QTYPE= AAAA
QCLASS= IN
RR {
NAME Same as received in
DNS Query

TYPE A
CLASS IN
RDATA IPv4 address of HA
}
RR {
NAME Same as received in
DNS Query

TYPE AAAA
CLASS IN
RDATA IPv6 address of HA
}

15.2 Discovery of the Home Agent via DHCP
(1)
with { UE has acquired an IP address and UE is configured with the HA-APN Network Identifier }
ensure that {
when { UE is configured to discover IP address of Home Agent via DHCP }
then { UE transmits a DHCP Information-Request with Home Network Identifier Option containing
the FQDN of the Home Agent}
}

5.1.2.1.5.
[TS 24.303, clause 5.1.2.1.1]
The first procedure the UE needs to perform for DSMIPv6 initial attach is the discovery of the node acting as the HA.
The UE can discover the IP addresses of the HA in one of the four following ways:
- via DNS;
- via attach procedure for 3GPP access or trusted non-3GPP access (if supported) based on protocol configuration
options;
- via IKEv2 during tunnel setup to ePDG for untrusted non-3GPP accesses;
- via DHCPv6.
If the UE does not obtain the IP addresses of the HA via PCO during the 3GPP or trusted non-3GPP (if supported)
attach or via IKEv2 signalling, it shall follow either the procedures described in subclause 5.1.2.1.5 or the procedures
described in subclause 5.1.2.1.2. The UE may be configured to perform both procedures in parallel or one of the two
procedures only in case the other failed.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1086 Release 9
1086
[TS 24.303, clause 5.1.2.1.5]
The HA address discovery via DHCPv6 is possible in the following cases:
- in 3GPP access, or
- in trusted non-3GPP access, when a DHCPv6 relay exists in the trusted non-3GPP access and the PDN GW is
the DHCPv6 server, or
- in trusted non-3GPP access, when the DHCPv6 server is in the trusted non-3GPP access and it has the HA
addresse information from static configuration, or received via STa reference point as specified in
3GPP TS 29.273 [20].
A UE performing HA discovery based on DHCPv6 shall support the implementation of stateless DHCPv6 as specified
in IETF RFC 3736 [13] and the DHCPv6 options as specified in draft-ietf-mip6-hiopt [12].
In order to discover the address of the HA the UE shall send an Information-Request message including the Home
Network Identifier Option.
In order to connect to a HA for a specific target PDN, the UE shall set the id-type to 1 and include the desired HA-APN
in the Home Network Identifier field.
The HA information is provided to the UE within a Home Network Information Option as described in draft-ietf-mip6-
hiopt [12]. This option shall include either the available HA addresses (both the IPv6 address and the IPv4 address of
the HA, if available) or the HA FQDN. In the latter case the UE shall perform a DNS Lookup by Home Agent Name as
specified in IETF RFC 5026 [10]. The QNAME shall be set to the received HA FQDN.
If a HA has both an IPv4 and an IPv6 address, the corresponding DNS record should be configured with both 'AAAA'
and 'A' records. Accordingly the UE should perform one DNS lookup procedure to retrieve both 'AAAA' and 'A'
records. The DNS server replies with one 'AAAA' and one 'A' record.
System Simulator:
- Cell 1.
UE:
- The UE is configured to discover the address of the Home Agent via DHCPv6.
- The UE is configured with the HA-APN Network Identifier.
Preamble:
- The UE has acquired an IPv6 address.
U - S Message
1 Check: Does the UE transmit a DHCP
Information-Request including a Home
Network Information Option?
--> DHCP Information-Request 1 P
2 The SS transmits a DHCP Reply message
including a Home Network Information Option.
<-- DHCP Reply message - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1087 Release 9
1087
Table 15.2.3.3-1: DHCP Information-Request (step 1, Table 15.2.3.2-1)
msg-type 00001011B Information-
Request

Transaction- id Set by UE
option-code 0000000000000001B Option Client ID
DUID Set by UE
option-code 0000000000000110B Option ORO
Requested-option-code-1 FFS Home Network
Identifier Option

Id-type 00000001B Target network
identity present

Sub-opt-code 00000001B Home network
identifier

Home Network Parameter Fully Qualified Domain
Name
Derived from HA-
APN Network
Identifier and
PLMN information
as per TS 23.003
clause 21.2

Table 15.2.3.3-2: DHCP Reply message (step 2, Table 15.2.3.2-2)
msg-type 00000111B Reply
Transaction- id Set as the same value of
Transaction-id in step 1

option-code 0000000000000001B Option Client ID
DUID Set as the DUID of the
client received in in step
1

option-code 0000000000000010B Option Server ID
DUID Set by SS
Home Network Identifier Option FFS Home Network
Identifier Option

Id-type 00000001B Target network
identity present

Sub-opt-code 00000001B Home network
identifier

Home Network Parameter Fully Qualified Domain
Name
Derived from HA-
APN Network
Identifier and
PLMN information
as per TS 23.003
clause 21.2

Sub-opt-code 00000011B IPv6 address
Home Network Parameter IPv6 address of the
Home Agent

Sub-opt-code 00000100B IPv4 address
(optional value)

Home Network Parameter IPv4 address of the
Home Agent

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1088 Release 9
1088
15.3 Void
15.4 Security association establishment with Home Agent
reallocation procedure
(1)
with { UE has acquired an IP address }
ensure that {
when { UE has acquired the IP address of the Home Agent }
then { UE transmits an IKE_SA_INIT message addressed to the Home Agent to initiate security
association establishment }
}
(2)
with { UE has transmitted an IKE_SA_INIT message addressed to the Home Agent to initiate security
ensure that {
when { UE receives an IKE_SA_INIT response message }
then { UE transmits an IKE_AUTH Request message containing the configuration payload
MIP6_HOME_PREFIX to receive the prefix to use for Home Address configuration }
}
(3)
with { UE has transmitted an IKE_AUTH Request message containing the configuration payload
ensure that {
when { UE receives an IKE_AUTH Response message including an EAP-Request/AKA Challenge }
then { UE transmits an IKE_AUTH Request message containing the correct EAP-Response/AKA-
Challenge }
}
(4)
with { UE has transmitted an IKE_AUTH Request message containing an EAP-Response/AKA-Challenge }
ensure that {
when { UE receives an IKE_AUTH Response message including EAP-Success }
then { UE transmits an IKE_AUTH Request message with Authentication payload }
}
(5)
with { UE has transmitted an IKE_AUTH Request message with Authentication payload }
ensure that {
when { UE receives an IKE_AUTH Response message with Notify payload with a REDIRECT attribute
containing the HOME AGENT address to connect to }
then { UE transmits an IKE_SA_INIT message addressed to the Home Agent whose address was
received in the Notify Payload to initiate security association establishment }
}

5.1.3.1.
[TS 24.303, clause 5.1.2.2]
The UE shall support the IKEv2 protocol (see IETF RFC 4306 [14]) for negotiating the IPsec security association to
secure DSMIPv6 signalling and shall support EAP over IKEv2 as described in IETF RFC 4306 [14] to perform
authentication with an AAA server. In a case an additional authentication and authorization of the IPSec security
association is needed with an external AAA server, then the additional authentication steps during the IKEv2 exchange
shall be supported as specified in IETF RFC 4739 [23] and described in 3GPP TS 33.234 [24].
The UE shall support IPsec ESP (see IETF RFC 4303 [11]) in order to provide authentication of Binding Update and
Binding Acknowledgement messages as specified in IETF RFC 4877 [4]. The UE shall support multiple authentication
exchanges in the IKEv2 protocol as specified in IETF RFC 4739 [23] in order to support authentication with an external
AAA server. The UE shall support the redirect mechanism as defined in draft-ietf-ipsecme-ikev2-redirect [30].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1089 Release 9
1089
The UE shall initiate the security association establishment procedure by sending the IKE_SA_INIT request message
defined in IETF RFC 4306 [14] to the HA. The UE shall indicate support for the HA reallocation by including a
REDIRECT_SUPPORTED payload in the IKE_SA_INIT request as specified in draft-ietf-ipsecme-ikev2-redirect [30].
On receipt of an IKE_SA_INIT response, the UE shall send an IKE_AUTH request message including the MN-NAI in
the IDi payload and the Access Point Name (APN) of the target PDN the UE wants to connect to in the IDr payload.
The APN shall be formatted as defined in 3GPP TS 23.003 [17]. The username part of the MN-NAI included in "IDi"
payload may be an IMSI, pseudonym or re-authentication ID. The UE shall include in the IDi payload the same MN-
NAI it includes in the EAP-Response/Identity within the EAP-AKA exchange.
In the very first EAP-Response/Identity within the IKEv2 exchange the UE shall include a NAI whose username is
derived from IMSI. In subsequent exchanges the UE should use pseudonyms and re-authentication identities provided
by the 3GPP AAA server as specified in IETF RFC 4187 [26].
NOTE: Fast re-authentication mechanism is optional, and therefore is an implementation option in the UE and
operator configuration issue (i.e. it also depends on whether the AAA server sent a re-authentication ID
during previous EAP authentication) whether to use it during security association establishment.
EAP-AKA over IKEv2 shall be used to authenticate UE in the IKE_AUTH exchange, while public key signature based
authentication with certificates shall be used to authenticate the HA.

During the IKEv2 exchange, the UE shall request the allocation of an IPv6 home prefix through the Configuration
Payload in the IKE_AUTH. Since in EPS a unique IPv6 prefix is assigned to the UE, the UE shall include a
MIP6_HOME_PREFIX attribute in the CFG_REQUEST message as described in IETF RFC 5026 [10]. In addition the
UE may include the INTERNAL_IP6_DNS attribute in the CFG_REQUEST as described in IETF RFC 4306 [14] to
request the DNS server IPv6 address of the PLMN it is connecting to via DSMIPv6. In the same way the UE may
include the INTERNAL_IP4_DNS attribute in the CFG_REQUEST to request the IPv4 address of the DNS server.
The UE shall then auto-configure a Home Address from the IPv6 prefix received from the HA and shall run a
CREATE_CHILD_SA exchange to create the security association for the new Home Address. In the
CREATE_CHILD_SA exchange the UE shall include the Home Address and the appropriate selectors in the TSi
(Traffic Selector-initiator) payload to negotiate the IPsec security association for protecting the Binding Update and
Binding Acknowledgement messages as specified in IETF RFC 4877 [4].
[TS 24.303, clause 5.1.3.1]
The HA shall support the IKEv2 protocol (see IETF RFC 4306 [14]) for negotiating the IPsec security association to
secure DSMIPv6 signalling and shall support EAP over IKEv2 as described in IETF RFC 4306 [14] to perform UE
authentication with an AAA server. If an additional authentication and authorization of the IPSec security association
were needed with an external AAA server, then the additional authentication steps during the IKEv2 exchange shall be
supported as specified in IETF RFC 4739 [23] and defined in 3GPP TS 33.234 [24]. The HA shall support IPsec ESP
(see IETF RFC 4303 [11]) in order to provide authentication of Binding Update and Binding Acknowledgement
messages as specified in IETF RFC 4877 [4]. The HA shall support multiple authentication exchanges in the IKEv2
protocol as specified in IETF RFC 4739 [23] in order to support authentication with an external AAA server.
The HA shall complete the IKE_SA_INIT exchange as specified in IETF RFC 4306 [14]. The HA shall include in the
IDr the same value included by the UE in the IDr payload of the request.
Upon successful authorization and authentication, the HA shall accept the security association establishment request by
sending the IKE_AUTH response message with the CFG_REPLY payload including the IPv6 Home Network Prefix
allocated to the UE in the MIP6_HOME_PREFIX attribute. This prefix information shall include the prefix length as
specified in IETF RFC 5026 [10]. If the UE included the INTERNAL_IP6_DNS or the INTERNAL_IP4_DNS in the
CFG_REQUEST, the HA shall include the same attribute in the CFG_REPLY including zero or more DNS server
addresses as specified in IETF RFC 4306 [14]
If the 3GPP AAA server triggers the HA to perform a HA reallocation procedure as specified in 3GPP TS 33.402 [18],
the HA learns the IP address of the target HA as specified in 3GPP TS 29.273 [20]. The HA shall provide to the UE the
target HA IP address in the REDIRECT payload during IKE_AUTH exchange as specified in 3GPP TS 33.402 [18].
The encoding of the REDIRECT payload in the IKE_AUTH response message is specified in draft-ietf-ipsecme-ikev2-
redirect [30]. The HA shall not assign an IPv6 prefix to the UE in the IKE_AUTH exchange. The HA shall remove the
states of the IKEv2 security association with the UE after receiving an IKEv2 Informational message with a DELETE
payload from the UE.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1090 Release 9
1090
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE has discovered the IP address of the Home Agent (either via DNS, DHCPv6, IKEv2 signalling or during
Attach Procedure via PCO).
U - S Message
1 Check: Does the UE transmit an IKE_SA_INIT
message addressed to the Home Agent?
--> IKE_SA_INIT 1 P
2 The SS transmits an IKE_SA_INIT message. <-- IKE_SA_INIT - -
3 Check: Does the UE transmit an IKE_AUTH
Request message containing the configuration
payload MIP6_HOME_PREFIX, a MN-NAI
derived from UE IMSI in the IDi field and an
APN in the IDr field?
--> IKE_AUTH Request 2 P
4 The SS transmits an IKE_AUTH Response
message including an EAP-Request/AKA-
Challenge.
<-- IKE_AUTH Response - -
Request message including the EAP-
Response/AKA-Challenge?
message including EAP-Success.
Request message with Authentication
payload?
message with Notify payload containing
REDIRECT attribute with the Home Agent to
be used
message addressed to the Home Agent whose
address was provided in the REDIRECT Notify
payload?.
--> IKE_SA_INIT 5 P

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1091 Release 9
1091
Table 15.4.3.3-1: Message IKE_SA_INIT (step 1, Table 15.4.3.2-1)
IKE Header
Initiators IKE_SA SPI Set by the UE
Responders IKE_SA SPI 0 First message jn
IKE_SA_INIT
exchange

Next Payload 00100001B SA
Exchange Type 00100010B IKE_SA_INIT
Security Association Payload
Next Payload 00100010B KE
More proposal 00000010B
Proposal # 00000001B First cryptographic
suite (section 6.5
of TS 33.234)

Protocol ID 00000001B IKE
SPI size 00000000B
Number of transforms 00000010B
More transform 00000011B This is the
transform for
confidentiality

Transform type 00000001B Encription
Transform ID 00000011B 3DES in CBC
mode
(ENCR_3DES)

transform for prf

Transform type 00000010B PRF
Transform ID 00000010B PRF_HMAC_SHA
1 (HMAC-SHA1)

transform for
integrity

Transform type 00000011B Integrity
Transform ID 00000010B HMAC-SHA1-96
(AUTH_HMAC_S
HA1_96)

Last transform 00000000B This is the
transform for DH

Transform type 00000100B DH
Transform ID 00000010B Diffie-Hellman
group 2 (1024-bit
MODP)

Last proposal 00000000B
Proposal # 00000010B Second
cryptographic
suite (section 6.5
of TS 33.234)

SPI size 00000000B
transform for
confidentiality

Transform ID 00001011B AES with 128-bit
keys in CBC
mode
(ENCR_AES_CB
C)

transform for prf

Transform ID 00000100B PRF_AES128_XC

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1092 Release 9
1092
BC_ AES-XCBC-
PRF-128
transform for
integrity

Transform ID 00000101B AES-XCBC-MAC-
96 (AUTH_ AES-
XCBC -96)

transform for DH

group 2 (1024-bit
MODP)

Key Exchange Payload
Next Payload 00101000B Nonce
DH Group # 0000000000000010B DH group 2
Key Exchange data Set by the UE
Nonce Payload
Next Payload 00101001B Notify
(REDIRECT_SUP
PORTED)

Nonce data Random number set by
the UE

REDIRECT_SUPPORTED Notify Payload
Next Payload 00000000B No Next Payload
Protocol ID 00000000B Notification is not
specific to a
particular security
association

SPI size 00000000B SPI field not
present

Notify Message Type '0100000000010110'B REDIRECT_SUP
PORTED

IKE Header
Initiators IKE_SA SPI Same as that set by the
UE in IKE_SA_INIT as
Step 1

Responders IKE_SA SPI Set by the SS
Proposal One of the 2 proposals
included in IKE_SA_INIT
at Step 1

Next payload 00 101000B Nonce
Key Exchange data Set by the SS
Nonce Payload
Nex t payload 00000000B No Next Payload
Nonce data Set by the SS

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1093 Release 9
1093
Table 15.4.3.3-3: Message IKE_AUTH Request (step 3, Table 15.4.3.2-1)
IKE Header
UE at Step 1

Responders IKE_SA SPI Same as that set by the
SS at Step 2

Next Payload 00101110B E
Exchange Type 00100011B IKE_AUTH
Encrypted Payload
Next Payload 00100011B IDi
Initialization Vector Random value set by the
UE

Encrypted IKE Payloads
Identification Initiator Payload
Next Payload 00101111B CP
ID Type 00000010B
ID Set to MN-NAI
Configuration Payload
CFG Type 00000001B Request
Configuration Attribute 00010000B MIP6_HOME_PR
EFIX attribute

Length 0000000000000000B
Next Payload 00101100B TSi
Proposals Any set of allowed values
Traffic Selector Initiator Payload
Next Payload 00101100B TSr
Traffic selector data Any allowed set of values
Traffic Selector Responder Payload
Next Payload 00100100B IDr
Identification Responder Payload
ID Type 00000010B
ID APN
Padding Set by the UE Fields from
Encrypted
payload

Pad Length Set by the UE Fields from
Encrypted
payload

Integrity checksum data Set by the UE Fields from
Encrypted
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1094 Release 9
1094
Table 15.4.3.3-4: Message IKE_AUTH Response (step 4, Table 15.4.3.2-1)
IKE Header
UE at Step 1

SS at Step 2

Encrypted Payload
Initialization Vector Set by the SS
Next Payload 00100101B CERT
ID Type 00000010B
ID APN
Certificate Payload
Next Payload 00110000B EAP
Cert encoding 00000100B X.509 certificate -
signature

Certificate data Set by the SS DER encoded
X.509 certificate

Extensible Authentication Payload
Code 00000001B Request
Type 00010111B AKA
Subtype AKA-Challenge
Attribute type 00000001B AT_RAND
AT_RAND An arbitrarily selected
128 bits value

Attribute Type 00000010B AT_AUTN
AT_AUTN See TS 24.301 [28]
subclause 9.9.3.2

Padding Set by the SS Fields from
Encryption
payload

Pad Length Set by the SS Fields from
Encryption
payload

Integrity checksum data Set by the SS Fields from
Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1095 Release 9
1095
IKE Header
Initiators IKE_SA SPI Same as that set by UE
at Step 1

SS at Step 2

Encrypted Payload
UE

Code 00000010B Response
Type 00010111B AKA
Attribute type 00000011B AT_RES
AT_RES See TS 24.301 [28]
subclause 9.9.3.4

Encryption
payload

Encryption
payload

Encryption
payload

IKE Header
UE at Step 1

SS at Step 2

Encrypted Payload
Code 00000011B Success
Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1096 Release 9
1096
IKE Header
UE at Step 1

SS at Step 2

Exchange Type 00100011 IKE_AUTH
Encrypted Payload
Next Payload 00100111B AUTH
UE

Authentication Payload
Auth Method 00000010B Shared Key
Integrity code

Auth Data derived from the MSK
obtained from AKA
exchange
RFC 4306 defines
the function to
derive this key
(section 2.15)

Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1097 Release 9
1097
IKE Header
UE at Step 1

SS at Step 2

Encrypted Payload
Integrity code

obtained from AKA
exchange
RFC 4306 defines
the function to
derive this key
(section 2.15)

Notify Payload
specific to a
particular security
association

SPI Size 00000000B SPI field not
present

Notify Message Type Length 0100000000010111B REDIRECT
GW Ident Type 00000101B
New Responder GW Identity IPv6 address of the HA
to relocate

GW Ident Type 00000001B
New Responder GW Identity IPv4 address of the HA
to relocate
Optional
Next Payload 00101101 TSi
included in IKE_AUTH
Request at Step 3

Traffic Selector data Any allowed set of values
Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1098 Release 9
1098
IKE Header
IKE_SA_INIT
exchange

suite (section 6.5
of TS 33.234)

SPI size 00000000B
transform for
confidentiality

mode
(ENCR_3DES)

transform for prf

1 (HMAC-SHA1)

transform for
integrity

(AUTH_HMAC_S
HA1_96)

transform for DH

group 2 (1024-bit
MODP)

cryptographic
suite (section 6.5
of TS 33.234)

SPI size 00000000B
transform for
confidentiality

keys in CBC
mode
(ENCR_AES_CB
C)

transform for prf

BC_ AES-XCBC-
PRF-128

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1099 Release 9
1099
transform for
integrity

96 (AUTH_ AES-
XCBC -96)

transform for DH

group 2 (1024-bit
MODP)

Nonce Payload
(REDIRECT_SUP
PORTED)

the UE

(REDIRECT_FRO
M)

specific to a
particular security
association

present

PORTED

Notify Payload
Next Payload 00000000B No next payload
specific to a
particular security
association

SPI Size 00000000B SPI field not
present

Notify Message Type 0100000000011000B REDIRECT_From
GW Ident Type Any allowed value (IPv6
or IPv4 or HA FQDN)
Set depending on
how the UE has
discovered the HA
in the preamble

New Responder GW Identity Depends on GW Ident
type

15.5 Security association establishment without home agent
(1)
with { UE has acquired an IP address }
ensure that {
when { UE has acquired the IP address of the Home Agent }
then { UE transmits an IKE_SA_INIT message addressed to the Home Agent to initiate security
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1100 Release 9
1100
(2)
with { UE has transmitted an IKE_SA_INIT message addressed to the Home Agent to initiate security
ensure that {
when { UE receives an IKE_SA_INIT response message }
then { UE transmits an IKE_AUTH Request message containing the configuration payload
}
(3)
with { UE has transmitted an IKE_AUTH Request message containing the configuration payload
ensure that {
when { UE receives an IKE_AUTH Response message including an EAP-Request/AKA Challenge }
then { UE transmits an IKE_AUTH Request message containing the correct EAP-Response/AKA-
Challenge }
}
(4)
with { UE has transmitted an IKE_AUTH Request message containing an EAP-Response/AKA-Challenge }
ensure that {
when { UE receives an IKE_AUTH Response message including EAP-Success }
then { UE transmits an IKE_AUTH Request message with Authentication payload }
}
(5)
with { UE has transmitted an IKE_AUTH Request message with Authentication payload }
ensure that {
when { UE receives an IKE_AUTH Response message with configuration payload MIP6_HOME_PREFIX
containing the Home Network Prefix HNP associated to the UE }
then { UE transmits a CREATE_CHILD_SA Request message including traffic selectors fields (TSi
and TSr) that contain the parameters identifying the Binding Update (BU)/Binding Acknowledgments
(BA) messages }
}

[TS 24.303, clause 5.1.2.2]
The UE shall support the IKEv2 protocol (see IETF RFC 4306 [14]) for negotiating the IPsec security association to
secure DSMIPv6 signalling and shall support EAP over IKEv2 as described in IETF RFC 4306 [14] to perform
authentication with an AAA server. In a case an additional authentication and authorization of the IPSec security
association is needed with an external AAA server, then the additional authentication steps during the IKEv2 exchange
shall be supported as specified in IETF RFC 4739 [23] and described in 3GPP TS 33.234 [24].
The UE shall support IPsec ESP (see IETF RFC 4303 [11]) in order to provide authentication of Binding Update and
Binding Acknowledgement messages as specified in IETF RFC 4877 [4]. The UE shall support multiple authentication
exchanges in the IKEv2 protocol as specified in IETF RFC 4739 [23] in order to support authentication with an external
AAA server. The UE shall support the redirect mechanism as defined in draft-ietf-ipsecme-ikev2-redirect [30].
The UE shall initiate the security association establishment procedure by sending the IKE_SA_INIT request message
defined in IETF RFC 4306 [14] to the HA. The UE shall indicate support for the HA reallocation by including a
REDIRECT_SUPPORTED payload in the IKE_SA_INIT request as specified in draft-ietf-ipsecme-ikev2-redirect [30].
On receipt of an IKE_SA_INIT response, the UE shall send an IKE_AUTH request message including the MN-NAI in
the IDi payload and the Access Point Name (APN) of the target PDN the UE wants to connect to in the IDr payload.
The APN shall be formatted as defined in 3GPP TS 23.003 [17]. The username part of the MN-NAI included in "IDi"
payload may be an IMSI, pseudonym or re-authentication ID. The UE shall include in the IDi payload the same MN-
NAI it includes in the EAP-Response/Identity within the EAP-AKA exchange.
In the very first EAP-Response/Identity within the IKEv2 exchange the UE shall include a NAI whose username is
derived from IMSI. In subsequent exchanges the UE should use pseudonyms and re-authentication identities provided
by the 3GPP AAA server as specified in IETF RFC 4187 [26].

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1101 Release 9
1101
NOTE: Fast re-authentication mechanism is optional, and therefore is an implementation option in the UE and
operator configuration issue (i.e. it also depends on whether the AAA server sent a re-authentication ID
during previous EAP authentication) whether to use it during security association establishment.
EAP-AKA over IKEv2 shall be used to authenticate UE in the IKE_AUTH exchange, while public key signature based
authentication with certificates shall be used to authenticate the HA.

During the IKEv2 exchange, the UE shall request the allocation of an IPv6 home prefix through the Configuration
Payload in the IKE_AUTH. Since in EPS a unique IPv6 prefix is assigned to the UE, the UE shall include a
MIP6_HOME_PREFIX attribute in the CFG_REQUEST message as described in IETF RFC 5026 [10]. In addition the
UE may include the INTERNAL_IP6_DNS attribute in the CFG_REQUEST as described in IETF RFC 4306 [14] to
request the DNS server IPv6 address of the PLMN it is connecting to via DSMIPv6. In the same way the UE may
include the INTERNAL_IP4_DNS attribute in the CFG_REQUEST to request the IPv4 address of the DNS server.
The UE shall then auto-configure a Home Address from the IPv6 prefix received from the HA and shall run a
CREATE_CHILD_SA exchange to create the security association for the new Home Address. In the
CREATE_CHILD_SA exchange the UE shall include the Home Address and the appropriate selectors in the TSi
(Traffic Selector-initiator) payload to negotiate the IPsec security association for protecting the Binding Update and
Binding Acknowledgement messages as specified in IETF RFC 4877 [4].
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE has discovered the IP address of the Home Agent (either via DNS, DHCPv6, IKEv2 signalling or during
Attach Procedure via PCO).

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1102 Release 9
1102
U - S Message
message addressed to the Home Agent?
--> IKE_SA_INIT 1 P
2 The SS transmits an IKE_SA_INIT message. <-- IKE_SA_INIT - -
Request message containing the configuration
payload MIP6_HOME_PREFIX, a MN-NAI
derived from UE IMSI in the IDi field and an
APN in the IDr field?
message including an EAP-Request/AKA-
Challenge.
Request message including the EAP-
Response/AKA-Challenge?
message including EAP-Success.
Request message with Authentication
payload?
message with configuration payload
MIP6_HOME_PREFIX containing the Home
Network Prefix HNP associated to the UE.
CREATE_CHILD_SA Request message
including traffic selectors fields (TSi and TSr)
that contain the parameters identifying the
Binding Update (BU) / Binding
Acknowledgments (BA) messages?
--> CREATE_CHILD_SA Request 5 P
10 The SS transmits a CREATE_CHILD_SA
Response message.
<-- CREATE_CHILD_SA Response - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1103 Release 9
1103
IKE Header
IKE_SA_INIT
exchange

suite (section 6.5
of TS 33.234)

SPI size 00000000B
transform for
confidentiality

mode
(ENCR_3DES)

transform for prf

1 (HMAC-SHA1)

transform for
integrity

(AUTH_HMAC_S
HA1_96)

transform for DH

group 2 (1024-bit
MODP)

cryptographic
suite (section 6.5
of TS 33.234)

SPI size 00000000B
transform for
confidentiality

keys in CBC
mode
(ENCR_AES_CB
C)

transform for prf


3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1104 Release 9
1104
BC_ AES-XCBC-
PRF-128
transform for
integrity

96 (AUTH_ AES-
XCBC -96)

transform for DH

group 2 (1024-bit
MODP)

Nonce Payload
(REDIRECT_SUP
PORTED)

the UE

specific to a
particular security
association

present

PORTED

IKE Header
UE in IKE_SA_INIT as
Step 1

Responders IKE_SA SPI Set by the SS
included in IKE_SA_INIT
at Step 1

Next payload 00 101000B Nonce
Key Exchange data Set by the SS
Nonce Payload
Nex t payload 00000000B No Next Payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1105 Release 9
1105
IKE Header
UE at Step 1

SS at Step 2

Encrypted Payload
Next Payload 00100011B IDi
UE

Identification Initiator Payload
ID Type 00000010B
ID Set to MN-NAI
CFG Type 00000001B Request
EFIX attribute

Length 0000000000000000B
Proposals Any set of allowed values
ID Type 00000010B
ID APN
Encrypted
payload

Encrypted
payload

Encrypted
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1106 Release 9
1106
IKE Header
UE at Step 1

SS at Step 2

Encrypted Payload
Next Payload 00100101B CERT
ID Type 00000010B
ID APN
Certificate Payload
Cert encoding 00000100B X.509 certificate -
signature

Certificate data Set by the SS DER encoded
X.509 certificate

Code 00000001B Request
Type 00010111B AKA
Attribute type 00000001B AT_RAND
AT_RAND An arbitrarily selected
128 bits value

Attribute Type 00000010B AT_AUTN
AT_AUTN See TS 24.301 [28]
subclause 9.9.3.2

Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1107 Release 9
1107
IKE Header
Initiators IKE_SA SPI Same as that set by UE
at Step 1

SS at Step 2

Encrypted Payload
UE

Code 00000010B Response
Type 00010111B AKA
Attribute type 00000011B AT_RES
AT_RES See TS 24.301 [28]
subclause 9.9.3.4

Encryption
payload

Encryption
payload

Encryption
payload

IKE Header
UE at Step 1

SS at Step 2

Encrypted Payload
Code 00000011B Success
Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1108 Release 9
1108
IKE Header
UE at Step 1

SS at Step 2

Exchange Type 00100011 IKE_AUTH
Encrypted Payload
UE

Integrity code

obtained from AKA
exchange
RFC 4306 defines
the function to
derive this key
(section 2.15)

Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1109 Release 9
1109
IKE Header
UE at Step 1

SS at Step 2

Encrypted Payload
Integrity code

obtained from AKA
exchange
RFC 4306 defines
the function to
derive this key
(section 2.15)

CFG Type 00000010B Reply
EFIX attribute

Length 0000000000010101B
Prefix lifetime Any allowed value
Home Prefix IPv6 prefix 16 bytes
Prefix length 10000000B Prefix length must
be 64

Next Payload 00101101 TSi
included in IKE_AUTH
Request at Step 3

Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1110 Release 9
1110
Table 15.5.3.3-9: Message CREATE_CHILD_SA Request (step 9, Table 15.5.3.2-1)
IKE Header
UE at Step 1

SS at Step 2

Exchange Type 00 100100B CREATE_CHILD_
SA

Encrypted Payload
UE

Next Payload 00101000B Ni
suite (section 6.6
of TS 33.234)

Protocol ID 00000011B ESP
SPI size 00000100B
#of transforms 00000010B
SPI Set by the UE
transform for
confidentiality

mode
(ENCR_3DES)

transform for
integrity

Transform attribute ID 00000010B HMAC-SHA1-96
(AUTH_HMAC_S
HA1_96)

cryptographic
suite (section 6.6
of TS 33.234)

SPI size 00000100B
#of transforms 00000010B
SPI Set by the UE
transform for
confidentiality

keys in CBC
mode
(ENCR_AES_CB
C)

transform for
integrity

96 (AUTH_ AES-
XCBC -96)

Nonce Payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1111 Release 9
1111
the UE

Traffic Selector data Any set of values
containing the traffic
selector of the
CREATE_CHILD_SA
Response at Step 10

Next Payload 00101001B Notify (Use
transport mode)

Traffic Selector data Any set of values
containing the traffic
selector of the
CREATE_CHILD_SA
Response at Step 10

Use transport mode Notify Payload
Next payload 00101001B Notify (Use
transport mode)

SPI size 00000100B
Notify Message Type 1000000000000111B Use transport
mode

SPI Same as that set by the
UE in SA proposal #1

Next payload 00000000B No Next Payload
SPI size 00000100B
mode

UE in SA proposal #1

Encryption
payload

Encryption
payload

Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1112 Release 9
1112
Table 15.5.3.3-10: Message CREATE_CHILD_SA Response (step 10, Table 15.5.3.2-1)
IKE Header
UE at Step 1

SS at Step 2

Exchange Type 00 100100B CREATE_CHILD_
SA

Encrypted Payload
Next Payload 00100001 SA
Next Payload 00101000B Nr
Proposal # One of the 2 proposals
included in the
CREATE_CHILD_SA
Request at Step 9

SPI size 00000100B
SPI Set by the SS
First transform 00000011B This is the
transform for
confidentiality

Transform attribute type The corresponding value
of the chosen proposal

transform for
integrity

Transform attribute type The corresponding value
of the chosen proposal

Nonce Payload
Number of traffic selectors 00000010B
TS type 00001000B IPv6 range
IP protocol 10000111B Mobility header
Start port 0000010100000000B BU
End port 0000010100000000B BU
Starting-address HoA address derived
from HNP

Ending address HoA address derived
from HNP

Start port 0000011000000000B BA
End port 0000011000000000B BA
Starting-address HoA address derived
from HNP

Ending address HoA address derived
from HNP

Next Payload 00101001B Notify (Use
transport mode)

Number of traffic selectors 00000010B
Ts type 00001000B IPv6 range
Start port 0000010100000000B BU

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1113 Release 9
1113
End port 0000010100000000B BU
Starting-address HA address
Ending address HA address
Start port 0000011000000000B BA
End port 0000011000000000B BA
Starting-address HA address
Ending address HA address
Next Payload 00000000B
SPI size Set by the SS
mode

SS in the accepted SA
proposal

Encryption
payload

Encryption
payload

Encryption
payload

15.6 Registration of a new IPv6 CoA (Binding
Update/Acknowledgment procedure in IPv6 network)
(1)
with { UE has established a security association with the Home Agent and received the IPv6 Home
Address }
ensure that {
when { UE receives a Router Advertisement containing an IPv6 prefix different from the Home
Network Prefix assigned to the UE during the preamble and different from the prefixes contained in
the UEs Prefix list }
then { UE transmits a Binding Update message in order to register it Home Address and Care-of-
Address at the Home Agent }
}

5.1.2.4, and 5.2.2.3.
[TS 24.303, clause 5.1.2.3]
The DSMIPv6 Home Link Detection Function is used by the UE to detect if an access interface is on the home link for
a PDN from a DSMIPv6 perspective. The Home Link Detection function shall be performed before sending DSMIPv6
Binding Update via the same access interface.
To perform the Home Link Detection procedure, the UE shall compare the assigned Home Network Prefix for a PDN
with the IPv6 prefix or prefixes included in the Prefix Information Option in the Router Advertisements received on the
local link. The Home Network Prefix can be assigned in a 3GPP access via PCO, as specified in 3GPP TS 24.301 [15],
or via IKEv2 as specified in subclause 5.1.2.2. If there is a match between the Home Network Prefix and one of the
local prefixes, the UE is attached on the home link over the respective access interface and shall not send a Binding
Update to the HA unless the UE currently has a valid DSMIPv6 Binding Update list entry. If the UE has a valid
DSMIPv6 Binding Update list entry, the UE shall proceed to perform the action specified in subclause 5.2.2.4. If there
is not any match, the UE shall proceed as specified in subclause 5.1.2.4.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1114 Release 9
1114
NOTE: The UE does not need to run IKEv2 for home link detection if the Home Network prefix is dynamically
received in a PCO Information Element.
[TS 24.303, clause 5.1.2.4]
After establishing the security association and obtaining the IPv6 Home Address, the UE shall send a Binding Update
message as specified in IETF RFC 3775 [6] and IETF RFC 5555 [2] in order to register its Home Address and Care-of
Address at the HA, if it detects it is in the foreign network.
If both IPv4 and IPv6 Care-of Address are received at the foreign network, the UE shall first attempt to use the IPv6
Care-of Address for its binding registration. The UE shall not register both IPv4 and IPv6 Care-of Address to its HA.
If IPv6 Care-of Address is used for initial binding registration, the UE shall send the Binding Update message to the
IPv6 address of the HA. In this Binding Update message the H (home registration) and A (acknowledge) bits shall be
set. If the UE needs an IPv4 Home Address, the UE shall include the 0.0.0.0 address in the IPv4 Home Address option
to request a dynamic IPv4 Home Address.
When IPv6 Care-of Address is used for initial binding registration, the Alternate Care-of Address option shall be used
by the UE to carry the Care-of Address inside a Mobility Header which is protected by ESP. If this option is present, the
address included in this option is the same address present in the source address of the IPv6 packet.
If IPv4 Care-of Address is used for initial binding registration, the UE shall send the Binding Update as follows (see
IETF RFC 5555 [2]):
- The IPv6 packet, with the IPv6 Home Address as the Source Address field of the IPv6 header, shall be
encapsulated in UDP.
- The UE shall include the IPv4 Care-of Address as the Source Address field of the IPv4 header and the HA IPv4
address as the Destination Address field of the IPv4 header.
- The UE shall include the IPv4 Care-of Address option containing the IPv4 Care-of Address.
- The UE shall set the H (home registration) and A (acknowledge) flags.
- The UE shall set the F (UDP encapsulation required) flag to 0.
- The UE shall set the R (Mobile Router Flag) flag to 1.
- If the UE needs an IPv4 Home Address, the UE shall include an IPv4 Home Address option with the 0.0.0.0
address in the Binding Update message, as defined in IETF RFC 5555 [2].
When the UE receives the Binding Acknowledgement from the HA, it shall validate it based on the rules described in
IETF RFC 3775 [6] and IETF RFC 5555 [2]. If the Binding Acknowledgement contains the successful status code 0
("Binding Update Accepted"), the UE shall create an entry for the registered Home Address in its Binding Update List
and may start sending packets containing its IPv6 Home Address or other IPv6 addresses auto-configured from the
assigned home network prefix.
If the Binding Acknowledgement contains a value of 128, the UE may re-send the BU as specified in
IETF RFC 3775 [6]. If the Binding Acknowledgement contains a value from 129 to 133 as specified in
IETF RFC 3775 [6] or a value from 140 to 143 as specified in IETF RFC 3963 [29], the UE shall not send the BU to the
HA and should discover another HA.
If the Binding Acknowledgment contains an IPv4 Address Acknowledgement option with status code value from 0 to
127 (indicating success), the UE shall create two entries in its Binding Update List, one for the IPv6 Home Address and
another for the IPv4 Home Address. If the Binding Acknowledgement contains an IPv4 Address Acknowledgment
option with status code indicating error (i.e. 128 or higher), the UE shall create an entry only for the IPv6 HoA in its
binding update list. Moreover, if the status code is 129 ("Administratively prohibited") or 132 ("Dynamic IPv4 home
address assignment not available"), the UE shall not re-send the Binding Update and it shall use only the IPv6 HoA. If
the Binding Acknowledgement contains an IPv4 Address Acknowledgement option with status 128 ("Failure, reason
unspecified"), 130 ("Incorrect IPv4 home address"), 131 ("Invalid IPv4 address") or 133 ("Prefix allocation
unauthorized") it shall re-send the Binding Update including the 0.0.0.0 address in the IPv4 Home Address option. If
the Binding Acknowledgement does not contain an IPv4 Address Acknowledgment option, the UE shall create an entry
only for the IPv6 HoA in its binding update list.
NOTE: The value to be used to identify the IPv4 address acknowledgement option in the mobility header is 30;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1115 Release 9
1115
The UE may then send data traffic either with the IPv6 Home Address or with the IPv4 Home Address. If the UE is
located on an IP6-enabled link, it shall send IPv6 packets as described in IETF RFC 3775 [6]; IPv4 traffic shall be
encapsulated in IPv6 packets as described in IETF RFC 5555 [2]. If the UE is located on an IPv4-only link and the
Binding Acknowledgement contains the NAT detection option with the F flag set, the UE shall send IPv6 and IPv4
packets following the vanilla UDP encapsulation rules specified in IETF RFC 5555 [2]. Otherwise the UE shall send
IPv6 and IPv4 packets encapsulated in IPv4 as specified in IETF RFC 5555 [2].
Once the DSMIPv6 tunnel is established, the UE may build a DHCPv4 or DHCPv6 message as described in
IETF RFC 4039 [26] or IETF RFC 3736 [13] respectively and send it via the DSMIPv6 tunnel as described in
IETF RFC 3775 [6] in order to retrieve additional parameters, e.g. Vendor-specific options.
[TS 24.303, clause 5.2.2.3]
If the access network supports IPv6, as soon as the UE has received via a Router Advertisement at least an IPv6 prefix
which is not present in its Prefix List, the UE shall perform the Home Link detection as specified in subclause 5.1.2.3.
If the UE detects it is not attached to the home link, the UE shall send a Binding Update to the HA including the newly
configured IP address as the Care-of Address in the Source IP address of the packet and optionally in the Alternate
Care-of Address Option [6]. The UE build the Binding Update message as specified in IETF RFC 3775 [6].
If the UE has been assigned also an IPv4 Home Address and wants to update also the binding for it, the UE shall
include the IPv4 Home Address option including the assigned IPv4 Home Address in the same Binding Update message.
If the UE has been assigned also an IPv4 Home Address and wants to release it, the UE shall not include any IPv4
Home Address option in the same Binding Update.
If the UE does not have an IPv4 Home Address but wants to configure one, the UE shall include the IPv4 Home
Address option with the 0.0.0.0 address as specified in subclause 5.1.2.4.
If the access network supports only IPv4, as soon as the UE has configured an IPv4 Care-of Address which is different
from the previous Care-of Address, the UE shall send a Binding Update tunnelled in UDP as specified in draft-ietf-
mext-nemo-v4traversal [2]. The UE shall set the F flag to "0". The UE shall set the R flag to "1".
Independent of an IPv6 or IPv4 access network the UE shall set the Key Management Capability (K) bit in the Binding
Update message.
System Simulator:
- Cell 1.
UE:
- The UEs Prefix List has been cleared.
Preamble:
- The UE has established a security association with the Home Agent and obtained an IPv6 Home Address, by
executing the steps in test case 15.5 with the following exception: the IPv6 home prefix assigned to the UE by
the SS shall be the same as the prefix used during IP address acquisition by the UE.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1116 Release 9
1116
U - S Message
1 The SS broadcasts a Router Advertisement
with a Prefix Information Option containing an
IPv6 prefix different from the Home Network
Prefix assigned to the UE during the preamble.
- - - -
2 Check: Does the UE transmit a Binding Update
with its IPv6 CoA in the IP Source Address
field of the IP Header and the IPv6 Home
Agent address in the IP destination Address
field of the IP header?
--> Binding Update 1 P
3 The SS transmits a Binding Acknowledgement
accepting the Binding Update.
<-- Binding Acknowledgement - -

Table 15.6.3.3-1: Router Advertisement (step 1, Table 15.6.3.2-1)
Derivation path: 36.508, Table 4.7C.2-1
Prefix IPv6 prefix different from
the Home Network Prefix
assigned to the UE
during the preamble

15.7 Registration of a new IPv4 CoA (Binding
Update/Acknowledgment procedure in IPv4 network)
(1)
Address }
ensure that {
when { UE is connected to a network supporting IPv4 only}
then { UE transmits a Binding Update message in order to register its Home Address and Care-of-
Address at the Home Agent }
}

5.1.2.4, and 5.2.2.3.
[TS 24.303, clause 5.1.2.3]
The DSMIPv6 Home Link Detection Function is used by the UE to detect if an access interface is on the home link for
a PDN from a DSMIPv6 perspective. The Home Link Detection function shall be performed before sending DSMIPv6
Binding Update via the same access interface.
To perform the Home Link Detection procedure, the UE shall compare the assigned Home Network Prefix for a PDN
with the IPv6 prefix or prefixes included in the Prefix Information Option in the Router Advertisements received on the
local link. The Home Network Prefix can be assigned in a 3GPP access via PCO, as specified in 3GPP TS 24.301 [15],
or via IKEv2 as specified in subclause 5.1.2.2. If there is a match between the Home Network Prefix and one of the
local prefixes, the UE is attached on the home link over the respective access interface and shall not send a Binding
Update to the HA unless the UE currently has a valid DSMIPv6 Binding Update list entry. If the UE has a valid
DSMIPv6 Binding Update list entry, the UE shall proceed to perform the action specified in subclause 5.2.2.4. If there
is not any match, the UE shall proceed as specified in subclause 5.1.2.4.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1117 Release 9
1117
NOTE: The UE does not need to run IKEv2 for home link detection if the Home Network prefix is dynamically
received in a PCO Information Element.
[TS 24.303, clause 5.1.2.4]
After establishing the security association and obtaining the IPv6 Home Address, the UE shall send a Binding Update
message as specified in IETF RFC 3775 [6] and IETF RFC 5555 [2] in order to register its Home Address and Care-of
Address at the HA, if it detects it is in the foreign network.
If both IPv4 and IPv6 Care-of Address are received at the foreign network, the UE shall first attempt to use the IPv6
Care-of Address for its binding registration. The UE shall not register both IPv4 and IPv6 Care-of Address to its HA.
If IPv6 Care-of Address is used for initial binding registration, the UE shall send the Binding Update message to the
IPv6 address of the HA. In this Binding Update message the H (home registration) and A (acknowledge) bits shall be
set. If the UE needs an IPv4 Home Address, the UE shall include the 0.0.0.0 address in the IPv4 Home Address option
to request a dynamic IPv4 Home Address.
When IPv6 Care-of Address is used for initial binding registration, the Alternate Care-of Address option shall be used
by the UE to carry the Care-of Address inside a Mobility Header which is protected by ESP. If this option is present, the
address included in this option is the same address present in the source address of the IPv6 packet.
If IPv4 Care-of Address is used for initial binding registration, the UE shall send the Binding Update as follows (see
IETF RFC 5555 [2]):
- The IPv6 packet, with the IPv6 Home Address as the Source Address field of the IPv6 header, shall be
encapsulated in UDP.
- The UE shall include the IPv4 Care-of Address as the Source Address field of the IPv4 header and the HA IPv4
address as the Destination Address field of the IPv4 header.
- The UE shall include the IPv4 Care-of Address option containing the IPv4 Care-of Address.
- The UE shall set the H (home registration) and A (acknowledge) flags.
- The UE shall set the F (UDP encapsulation required) flag to 0.
- The UE shall set the R (Mobile Router Flag) flag to 1.
- If the UE needs an IPv4 Home Address, the UE shall include an IPv4 Home Address option with the 0.0.0.0
address in the Binding Update message, as defined in IETF RFC 5555 [2].
When the UE receives the Binding Acknowledgement from the HA, it shall validate it based on the rules described in
IETF RFC 3775 [6] and IETF RFC 5555 [2]. If the Binding Acknowledgement contains the successful status code 0
("Binding Update Accepted"), the UE shall create an entry for the registered Home Address in its Binding Update List
and may start sending packets containing its IPv6 Home Address or other IPv6 addresses auto-configured from the
assigned home network prefix.
If the Binding Acknowledgement contains a value of 128, the UE may re-send the BU as specified in
IETF RFC 3775 [6]. If the Binding Acknowledgement contains a value from 129 to 133 as specified in
IETF RFC 3775 [6] or a value from 140 to 143 as specified in IETF RFC 3963 [29], the UE shall not send the BU to the
HA and should discover another HA.
If the Binding Acknowledgment contains an IPv4 Address Acknowledgement option with status code value from 0 to
127 (indicating success), the UE shall create two entries in its Binding Update List, one for the IPv6 Home Address and
another for the IPv4 Home Address. If the Binding Acknowledgement contains an IPv4 Address Acknowledgment
option with status code indicating error (i.e. 128 or higher), the UE shall create an entry only for the IPv6 HoA in its
binding update list. Moreover, if the status code is 129 ("Administratively prohibited") or 132 ("Dynamic IPv4 home
address assignment not available"), the UE shall not re-send the Binding Update and it shall use only the IPv6 HoA. If
the Binding Acknowledgement contains an IPv4 Address Acknowledgement option with status 128 ("Failure, reason
unspecified"), 130 ("Incorrect IPv4 home address"), 131 ("Invalid IPv4 address") or 133 ("Prefix allocation
unauthorized") it shall re-send the Binding Update including the 0.0.0.0 address in the IPv4 Home Address option. If
the Binding Acknowledgement does not contain an IPv4 Address Acknowledgment option, the UE shall create an entry
only for the IPv6 HoA in its binding update list.
NOTE: The value to be used to identify the IPv4 address acknowledgement option in the mobility header is 30;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1118 Release 9
1118
The UE may then send data traffic either with the IPv6 Home Address or with the IPv4 Home Address. If the UE is
located on an IP6-enabled link, it shall send IPv6 packets as described in IETF RFC 3775 [6]; IPv4 traffic shall be
encapsulated in IPv6 packets as described in IETF RFC 5555 [2]. If the UE is located on an IPv4-only link and the
Binding Acknowledgement contains the NAT detection option with the F flag set, the UE shall send IPv6 and IPv4
packets following the vanilla UDP encapsulation rules specified in IETF RFC 5555 [2]. Otherwise the UE shall send
IPv6 and IPv4 packets encapsulated in IPv4 as specified in IETF RFC 5555 [2].
Once the DSMIPv6 tunnel is established, the UE may build a DHCPv4 or DHCPv6 message as described in
IETF RFC 4039 [26] or IETF RFC 3736 [13] respectively and send it via the DSMIPv6 tunnel as described in
IETF RFC 3775 [6] in order to retrieve additional parameters, e.g. Vendor-specific options.
[TS 24.303, clause 5.2.2.3]
If the access network supports IPv6, as soon as the UE has received via a Router Advertisement at least an IPv6 prefix
which is not present in its Prefix List, the UE shall perform the Home Link detection as specified in subclause 5.1.2.3.
If the UE detects it is not attached to the home link, the UE shall send a Binding Update to the HA including the newly
configured IP address as the Care-of Address in the Source IP address of the packet and optionally in the Alternate
Care-of Address Option [6]. The UE build the Binding Update message as specified in IETF RFC 3775 [6].
If the UE has been assigned also an IPv4 Home Address and wants to update also the binding for it, the UE shall
include the IPv4 Home Address option including the assigned IPv4 Home Address in the same Binding Update message.
If the UE has been assigned also an IPv4 Home Address and wants to release it, the UE shall not include any IPv4
Home Address option in the same Binding Update.
If the UE does not have an IPv4 Home Address but wants to configure one, the UE shall include the IPv4 Home
Address option with the 0.0.0.0 address as specified in subclause 5.1.2.4.
If the access network supports only IPv4, as soon as the UE has configured an IPv4 Care-of Address which is different
from the previous Care-of Address, the UE shall send a Binding Update tunnelled in UDP as specified in draft-ietf-
mext-nemo-v4traversal [2]. The UE shall set the F flag to "0". The UE shall set the R flag to "1".
Independent of an IPv6 or IPv4 access network the UE shall set the Key Management Capability (K) bit in the Binding
Update message.
System Simulator:
- Cell 1.
Preamble:
executing the steps in test case 15.5.
U - S Message
field of the IP Header and the Binding Update
encapsulated in an UDP header?

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1119 Release 9
1119
None.
15.8 Re-registration of IPv6 CoA
(1)
Address and registered its IPv6 Home Address and IPv6 Care-of-Address at the Home Agent }
ensure that {
when { registration of its Care-of-Address is about the expire }
then { UE initiates the re-registration procedure to extend lifetime of the registration of its
Care-of-Address }
}

[TS 24.303, clause 5.3.2]
As specified in IETF RFC 3775 [6], if the UE wants to extend the validity of an existing binding at the HA, the UE
shall send a new Binding Update to the HA before the expiration of the lifetime indicated in the received Binding
Acknowledgement, even if it is not changing its primary Care-of Address. This Binding Update is usually referred as
periodic Binding Update.
The UE shall follow the rules described in IETF RC 3775 [6], IETF RFC 5555 [2] and in subclause 5.1.2.4 to send a
periodic Binding Update and handle the associated Binding Acknowledgement. As the UE has not performed any
handover, the UE shall confirm the already registered Care of Address and shall indicate the desired lifetime value. In a
periodic Binding Update the UE may request an IPv4 Home Address.
System Simulator:
- Cell 1.
UE:
- The UEs Prefix List has been cleared.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1120 Release 9
1120
U - S Message
1-3 Steps 1 to 3 of test case 15.6 are performed
on Cell 1.
NOTE: The UE transmits an initial Binding
Update to register its IPv6 Home Address and
IPv6 Care-of-Address at the Home Agent. The
SS accepts the Binding Update by transmitting
a Binding Acknowledgement with a Lifetime
set to 10 min.
- - - -
Agent address in the IP Destination Address
field of the IP header within 10 min of Step 3?

None.
15.9 Re-registration of IPv4 CoA
(1)
ensure that {
when { registration of its Care-of-Address is about the expire }
then { UE initiates the re-registration procedure to extend lifetime of the registration of its
Care-of-Address }
}

15..2 Conformance requirements
[TS 24.303, clause 5.3.2]
As specified in IETF RFC 3775 [6], if the UE wants to extend the validity of an existing binding at the HA, the UE
shall send a new Binding Update to the HA before the expiration of the lifetime indicated in the received Binding
Acknowledgement, even if it is not changing its primary Care-of Address. This Binding Update is usually referred as
periodic Binding Update.
The UE shall follow the rules described in IETF RC 3775 [6], IETF RFC 5555 [2] and in subclause 5.1.2.4 to send a
periodic Binding Update and handle the associated Binding Acknowledgement. As the UE has not performed any
handover, the UE shall confirm the already registered Care of Address and shall indicate the desired lifetime value. In a
periodic Binding Update the UE may request an IPv4 Home Address.
System Simulator:
- Cell 1.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1121 Release 9
1121
Preamble:
U - S Message
1-2 Steps 1 to 2 of test case 15.7 are performed
on Cell 1.
NOTE: The UE transmits an initial Binding
Update to register its IPv6 Home Address and
IPv4 Care-of-Address at the Home Agent. The
SS accepts the Binding Update by transmitting
a Binding Acknowledgement with a Lifetime
set to 10 min.
- - - -
Agent address in the IP destination Address
field of the IP header within 10 min of Step 2?

None.
15.10 Return to home link
(1)
ensure that {
when { UE detects it is attached to the home link }
then { UE transmits a Binding Update message with the lifetime field set to 0 }
}

[TS 24.303, clause 5.2.2.4]
If the access network supports IPv6, as soon as the UE has received via a Router Advertisement message at least an
IPv6 prefix which is not present in its Prefix List, the UE shall perform the Home Link detection as specified in
subclause 5.1.2.3 to detect if the UE is attaching to the home link. If the UE detects it is attached to the home link and
there is a valid DSMIPv6 Binding Update list entry at the UE, the UE shall send a Binding Update with the Lifetime
field set to "0" in order to remove the binding at the HA, as specified in IETF RFC 3775 [6]. If an IPv4 home address
was assigned to the UE, as an optimization the UE may not include the IPv4 home address option as the binding for the
IPv4 home address will be removed by the HA. Independent of an IPv6 or IPv4 access network the UE shall set the Key
Management Capability (K) bit in the de-registration Binding Update message. The UE may preserve the IKEv2 session
in order to avoid re-establishing the session when the next handover occurs. If there is not a safe assumption that the UE
will remain in the home link (e.g. switching off the non-3GPP radio interface in case of a dual radio terminal), the UE
should preserve the IKEv2 session.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1122 Release 9
1122
System Simulator:
- Cell 1.
UE:
None.
Preamble:
- The UE has registered its IPv6 Home Address and its Care-of-Address (acquired IPv6 address) at the Home
Agent, by executing the steps in test case 15.6.
U - S Message
1 The SS broadcasts a Router Advertisement
with a Prefix Information Option containing an
IPv6 prefix matching the Home Network Prefix
assigned to the UE during the preamble.
- - - -
message with the lifetime field set to 0?
accepting the Binding Update with the lifetime
field set to 0.

Table 15.10.3.3-1: Router Advertisement (step 1, Table 15.10.3.2-1)
Derivation path: 36.508 table 4.7C.2-1
Prefix IPv6 prefix equal to
Home Network Prefix
assigned to the UE
during preamble

Table 15.10.3.3-2: Binding Update (step 2, Table 15.10.3.2-1)
Lifetime 0000000000000000B

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1123 Release 9
1123
Table 15.10.3.3-3: Binding Acknowledgement (step 3, Table 15.10.3.2-1)
Lifetime 0000000000000000B

15.11 Dual-Stack Mobile IPv6 detach in IPv6 network
(1)
ensure that {
when { UE receives a Binding Revocation Indication message from the HA }
then { UE transmits a Binding Revocation Acknowledgement message with the status field set to
Success }
}
(2)
with { UE has received a Binding Revocation Indication message from the HA }
ensure that {
when { UE has transmitted a Binding Revocation Acknowledgement message with the status field set
to Success }
then { UE transmits an IKEv2 INFORMATIONAL message containing a DELETE payload to remove the
Ipsec security association associated with the DSMIPv6 registration }
}

5.4.2.2.
[TS 24.303, clauses 5.4.2.1]
Upon receiving a Binding Revocation Indication (BRI) message according to draft-ietf-mext-binding-revocation [19]
from the HA, the UE first shall perform the required validity checks on the BRI according to draft-ietf-mext-binding-
revocation [19].
The UE shall send a Binding Revocation Acknowledgement (BRA) as specified in draft-ietf-mext-binding-
revocation [19]. In this message the UE shall set the status field to Success to reflect that it has received the BRI
message. The BRA message may be tunnelled in UDP or IPv4 as specified in subclause 5.1.2.4 for Binding Update
messages.
The UE then shall remove the entry identified in the BRI as deregistered from its binding update list and shall use the
procedures defined in IETF RFC 4306 [14] to remove the IPsec security associations associated with the DSMIPv6
registration as described in subclause 5.4.2.2.
[TS 24.303, clause 5.4.2.2]
To detach from a specific PDN to which it is connected through a DSMIPv6 session, the UE shall send a Binding
Update with the Lifetime field set to 0 as specified in IETF RFC 3775 [6].
The UE shall use the procedures defined in the IKEv2 protocol in IETF RFC 4306 [14] to remove the IPsec security
associations associated with the DSMIPv6 registration. The UE shall close the security associations associated with the
DSMIPv6 registration and instruct the HA to do the same by sending the INFORMATIONAL request message
including a DELETE payload. The Protocol ID in the DELETE payload shall be set to "1" (IKE) to indicate that all
IPsec ESP security associations that were negotiated within the IKEv2 exchange shall be deleted.

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1124 Release 9
1124
System Simulator:
- Cell 1.
UE:
None.
Preamble:
U - S Message
1 The SS transmits a Binding Revocation
Indication message to the UE.
<-- Binding Revocation Indication - -
2 Check: Does the UE transmit a Binding
Revocation Acknowledgement message with
the status field set to Success?
--> Binding Revocation
Acknowledgement
1 P
3 Check: does the UE transmit an IKEv2
INFORMATIONAL message containing a
DELETE payload?
--> IKEv2 INFORMATIONAL 2 P
4 The SS transmits an IKEv2 INFORMATIONAL
message containing a DELETE payload back
to the UE.
<-- IKEv2 INFORMATIONAL - -

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1125 Release 9
1125
Table 15.11.3.3-1: IKEv2 INFORMATIONAL (step 3, Table 15.11.3.2-1)
IKE Header
Initiators IKE_SA SPI The one identifying the
UE in the SA set up
during the preamble

Responders IKE_SA SPI The one identifying the
HA in the SA set up
during the preamble

Exchange Type 00100101B INFORMATIONAL
Encrypted Payload
Next Payload 00101010B DELETE
Delete Payload
Protocol ID 00000001B IKE SA
Encryption
payload

Encryption
payload

Encryption
payload

Table 15.11.3.3-2: IKEv2 INFORMATIONAL (step 4, Table 15.11.3.2-1)
IKE Header
UE at Step 3

SS at Step 3

Encrypted Payload
Delete Payload
Encryption
payload

Encryption
payload

Encryption
payload

15.12 Dual-Stack Mobile IPv6 detach in IPv4 network
(1)
ensure that {
when { UE receives a Binding Revocation Indication message from the HA with the A flag set }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1126 Release 9
1126
then { UE transmits a Binding Revocation Acknowledgement message with the status field set to
Success }
}
(2)
with { UE has received a Binding Revocation Indication message from the HA with the A flag set }
ensure that {
when { UE has transmitted a Binding Revocation Acknowledgement message with the status field set
to Success }
then { UE transmits an IKEv2 INFORMATIONAL message containing a DELETE payload to remove the
Ipsec security association associated with the DSMIPv6 registration }
}

5.4.2.2.
[TS 24.303, clauses 5.4.2.1]
Upon receiving a Binding Revocation Indication (BRI) message according to draft-ietf-mext-binding-revocation [19]
from the HA, the UE first shall perform the required validity checks on the BRI according to draft-ietf-mext-binding-
revocation [19].
If the A (Acknowledge) flag is set in the BRI message, the UE shall send a Binding Revocation Acknowledgement
(BRA) as specified in draft-ietf-mext-binding-revocation [19]. In this message the UE shall set the status field to
Success to reflect that it has received the BRI message. The BRA message may be tunnelled in UDP or IPv4 as
specified in subclause 5.1.2.4 for Binding Update messages.
The UE then shall remove the entry identified in the BRI as deregistered from its binding update list and shall use the
procedures defined in IETF RFC 4306 [14] to remove the IPsec security associations associated with the DSMIPv6
registration as described in subclause 5.4.2.2.
[TS 24.303, clause 5.4.2.2]
The UE shall use the procedures defined in the IKEv2 protocol in IETF RFC 4306 [14] to remove the IPsec security
associations associated with the DSMIPv6 registration. The UE shall close the security associations associated with the
DSMIPv6 registration and instruct the HA to do the same by sending the INFORMATIONAL request message
including a DELETE payload. The Protocol ID in the DELETE payload shall be set to "1" (IKE) to indicate that all
IPsec ESP security associations that were negotiated within the IKEv2 exchange shall be deleted.
System Simulator:
- Cell 1.
UE:
None.
Preamble:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1127 Release 9
1127
U - S Message
1 The SS transmits a Binding Revocation
Indication message with the A flag set to the
UE.
<-- Binding Revocation Indication - -
2 Check: Does the UE transmit a Binding
Revocation Acknowledgement message with
the status field set to Success?
--> Binding Revocation
Acknowledgement
1 P
3 Check: does the UE transmit an IKEv2
INFORMATIONAL message containing a
DELETE payload?
--> IKEv2 INFORMATIONAL 2 P
4 The SS transmits an IKEv2 INFORMATIONAL
message containing a DELETE payload back
to the UE.
<-- IKEv2 INFORMATIONAL - -

Table 15.12.3.3-1: IKE_INFORMATIONAL (step 3, Table 15.12.3.2-1)
IKE Header
Initiators IKE_SA SPI The one identifying UE in
the SA set up during the
preamble

Responders IKE_SA SPI The one identifying the
HA in the SA set up
during the preamble

Encrypted Payload
Delete Payload
Padding Set by UE Fields from
Encryption
payload

Pad Length Set by UE Fields from
Encryption
payload

Integrity checksum data Set by UE Fields from
Encryption
payload

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1128 Release 9
1128
Table 15.12.3.3-2: IKE_INFORMATIONAL (step 4, Table 15.12.3.2-1)
IKE Header
UE at Step 3

SS at Step 3

Encrypted Payload
Delete Payload
Encryption
payload

Encryption
payload

Encryption
payload

16 Home (e)NB related
16.1 UE Idle Mode Operations
16.1.1 Cell Selection and Reselection
16.1.1.1 Inter-RAT Cell reselection from E-UTRA idle non-CSG cell to a UTRA CSG
cell
(1)
with { UE in E-UTRA RRC_IDLE state and UEs Allowed CSG list is not empty }
ensure that {
when { UE detects a suitable UTRA CSG cell previously visited }
then { UE selects the suitable UTRA CSG cell irrespective of its lower priority than EUTRA
cells}
}

TS 25.304, clause 5.6.1, 5.2.3.1.2 and TS 25.367, clause 6.1, 7.2.3.
[TS 36.304, clause 5.2.4.8]
In addition to normal cell reselection, the UE shall use an autonomous search function to detect allowed CSG cells on
non-serving frequencies, including inter-RAT frequencies, when at least one CSG ID is included in the UEs CSG
whitelist. The UE may also use autonomous search on the serving frequency. The UE shall disable the autonomous
search function for CSG cells if the UEs CSG whitelist is empty.
If the UE detects one or more suitable CSG cells on another RAT, the UE shall reselect to one of them, if allowed
according to [19].
[TS 36.304, clause 4.3]
suitable cell:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1129 Release 9
1129
[TS 25.304, clause 5.6.1]
[TS 25.304, clause 5.2.3.1.2]

Where:

Squal =Q
qualmeas
Srxlev =Q
rxlevmeas

Where:

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1130 Release 9
1130
Q
qualmeas
c
/N
0

for FDD cells.
Q
rxlevmeas

[TS 25.367, clause 6.1]
[TS 25.367, clause 7.2.3]
Inter-RAT reselection to an allowed CSG cell is supported when the UE is camped on another RAT. The UE
requirements are defined in the specifications of the concerned RAT.
System Simulator:
UE:
Preamble:
rows marked "T1","T2" and "T3" are to be applied subsequently. The exact instants on which these values shall be

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1131 Release 9
1131
Table 16.1.1.1.3.2-1: Time instances of cell power level and parameter changes for E-UTRA Cell 1
T0
Cell-specific RS
EPRE
dBm/15kHz -85

Qrxlevminoffset dB 0 Default value
Qhyst dB 0 Default value
Srxlev* dB 21 Cell 1 is the strongest cell
T1
Cell-specific RS
EPRE
dBm/15kHz -85

Srxlev* dB 21
T2
Cell-specific RS
EPRE
dBm/15kHz -85

Srxlev* dB 21
T3
Cell-specific RS
EPRE
dBm/15kHz -85

Srxlev* dB 21

Table 16.1.1.1.3.2-2: Time instances of cell power level and parameter changes for UTRA Cell 5 and
Cell 7
T0
CPICH_Ec dBm/3.84 MHz OFF OFF Camping on Cell 1 is guaranteed
PCCPCH RSCP dBm/1.28 MHz OFF OFF Camping on Cell 1 is guaranteed
Qrxlevmin (TDD) dBm -81 -81 Default value
Srxlev* dB N/A N/A
Cell 5
>0, for FDD
Cell 5
>0, for TDD
T2 CPICH_Ec dBm/3.84 MHz OFF -60
PCCPCH RSCP dBm/1.28 MHz OFF -62
Srxlev* dB N/A 19
Cell 5
>0,for FDD
Cell 5
>0, for TDD

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1132 Release 9
1132
U - S Message
1 The SS changes Cell 1,Cell 5 and Cell7 levels
1 and table 16.1.1.1.3.2-2.
- - - -
2 UE performs manual CSG ID selection. CSG
Identity ('000 0000 0000 0000 0000 0000
- - - -
3 The UE executes the generic test procedure
described in TS 36.508 subclause 6.4.2.8 and
UE should camp on UTRA CSG Cell 5.
- - - -
16.1.1.1.3.2-1 and table 16.1.1.1.3.2-2.
- - - -
5 The registration procedure described in TS
36.508 subclause 6.4.2.7 is performed on Cell
1.
- - - -
16.1.1.1.3.2-1 and table 16.1.1.1.3.2-2.
- - - -
indicate that the UE is camped on UTRAN
CSG Cell 5 in [FFS] mins?
- - 1 -

Table 16.1.1.1.3.3-1: Conditions for Tables 16.1.1.1.3.3-2, 16.1.1.1.3.3-3, 16.1.1.1.3.3-4, 16.1.1.1.3.3-5
and 16.1.1.1.3.3-6

16.1.1.1.3.2-3)
Combination 4 in TS
36.508 section 4.4.3.1.1
Only SIB2, SIB3
and SIB6 are
transmitted

}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1133 Release 9
1133
16.1.1.1.3.2-3)
E-UTRA

}
E-UTRA

}
}

Table 16.1.1.1.3.3-4: Master Information Block for Cell 5 (preamble and all steps, Table 16.1.1.1.3.2-3)

16.1.1.1.3.2-3)
- CSG Identity '000 0000 0000 0000
0000 0000 0010'B

- Start PSC 100
- Number of PSCs 5

Table 16.1.1.1.3.3-6: System Information Block type 19 for Cell 5 and Cell 7 (preamble and all steps,
Table 16.1.1.1.3.2-3)
E-UTRA
Cell 5
Cell 7
}
priority[1] 4 Cell 5
Cell 7
}
}

16.1.1.2 Inter-RAT CSG Cell Reselection from E-UTRA CSG cell to UTRA CSG cell
(1)
with { UE in E-UTRA RRC_IDLE state and UEs Allowed CSG list is not empty }
ensure that {
when { UE detects a suitable UTRA CSG cell previously visited }

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1134 Release 9
1134
then { UE selects the suitable UTRA CSG cell irrespective of its lower priority than EUTRA
cells }
}

TS 25.304, clause 4.3, 5.6.1, 5.2.3.1.2 and TS 25.367, clause 6.1, 7.4.
[TS 36.304, clause 5.2.4.8]
To search for suitable CSG cells on non-serving frequencies, the UE may use an autonomous search function. If the UE
detects a CSG cell on a non-serving frequency, the UE may reselect to the detected CSG cell if it is the highest ranked
cell on its frequency.
If the UE detects one or more suitable CSG cells on another RAT, the UE may reselect to one of them if allowed
according to [19].
[TS 36.304, clause 4.3]
suitable cell:
[TS 25.304, clause 4.3]
suitable cell:
- The cell shall be part of either:
according to the latest information provided by the NAS.
- The cell is not barred, see subclause 5.3.1.1;

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1135 Release 9
1135
- The cell is part of at least one LA that is not part of the list of "forbidden LAs for roaming" [9], which belongs to
a PLMN that fulfills the first bullet above;
- The cell selection criteria are fulfilled, see subclause 5.2.3.1.2.
- For a CSG cell the CSG ID is part of the Allowed CSG list of the UE.
If the IE Multiple PLMN List [4] is broadcast in the cell, the cell is considered to be part of all LAs with LAIs
constructed from the PLMN identities in the Multiple PLMN List and the LAC broadcast in the cell.
[TS 25.304, clause 5.6.1]
[TS 25.304, clause 5.2.3.1.2]

Where:

Squal =Q
qualmeas
Srxlev =Q
rxlevmeas

Where:
Q
qualmeas
c
/N
0

for FDD cells.
Q
rxlevmeas

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1136 Release 9
1136
[TS 25.367, clause 6.1]
[TS 25.367, clause 7.4]
For reselection between allowed CSG cells, the UE follows the same cell ranking rules as those defined for the UTRA
case in [2].
System Simulator:
- Cell 1 is an E-UTRA CSG cell
UE:
- If pc_Allowed_CSG_list, the UEs Allowed CSG list is not empty and it includes a CSG Identity ('000 0000
0000 0000 0000 0000 0010'B).
Preamble:
rows marked "T1", "T2" and "T3" is to be applied subsequently. The exact instants on which these values shall be
Table 16.1.1.2.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cells
T0
Srxlev* dB 21 15 Cell 1 is the strongest cell and
T1
Srxlev* dB 21 15
T2
Srxlev* dB 21 15
T3
Srxlev* dB 15 21

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1137 Release 9
1137
T0
CPICH_Ec dBm/3.84 MHz OFF Camping on Cell 1 is guaranteed
PCCPCH RSCP dBm/1.28 MHz OFF Camping on Cell 1 is guaranteed
Qrxlevmin (FDD) dBm -79
Qrxlevmin (TDD) dBm -81 Default value
Srxlev* dB N/A
Cell 5
>0, for FDD
Cell 5
>0, for TDD
Srxlev* dB 19
T2
CPICH_Ec dBm/3.84 MHz OFF
PCCPCH RSCP dBm/1.28 MHz OFF
Srxlev* dB N/A
Cell 5
>0, for FDD
Cell 5
>0, for TDD
Srxlev* dB 19

U - S Message
16.1.1.2.3.2-1 and table 16.1.1.2.3.2-2.
- - - -
2 UE performs manual CSG ID selection and
CSG Identity ('000 0000 0000 0000 0000 0000
- - - -
3 The UE executes the generic test procedure
described in TS 36.508 subclause 6.4.2.8 and
UE should camp on UTRA CSG Cell 5.
- - - -
1 and table 16.1.1.2.3.2-2.
- - - -
5 The UE executes the generic procedure
described in TS 36.508 subclause 6.4.2.7. and
UE should camp on Cell 1.
- - - -
1 and table 16.1.1.2.3.2-2.
- - - -
5 in [FFS] mins?
- - 1 -

Table 16.1.1.2.3.3-1: Conditions for Tables 16.1.1.2.3.3-2, 16.1.1.2.3.3-3, 16.1.1.2.3.3-4, 16.1.1.2.3.3-5,
16.1.1.2.3.3-6 and 16.1.1.2.3.3-7

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1138 Release 9
1138
Table 16.1.1.2.3.2-3)
csg-Identity '000 0000 0000 0000
0000 0000 0010'B
Cell 1
}
q-RxLevMin -53 (-106 dBm) Cell 1
Cell 2
}
36.508 section 4.4.3.1
SIB2, SIB3, SIB4
and SIB6 are
transmitted
Cell 1
Combination 4 in TS
36.508 section 4.4.3.1
Only SIB2, SIB3
and SIB6 are
transmitted
Cell 2
}

16.1.1.2.3.2-3)
Start 2
apply value 1 in
case the field is
absent, in which
case only the
physical cell
identity value
indicated by start
applies.

}
}

Table 16.1.1.2.3.2-3)
E-UTRA
Cell 1
Cell 2
}
E-UTRA
Cell 1
Cell 2
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1139 Release 9
1139
Table 16.1.1.2.3.3-5: Master Information Block for Cell 5 (preamble and all steps, Table 16.1.1.2.3.2-3)

16.1.1.2.3.2-3)
- CSG Identity '000 0000 0000 0000
0000 0000 0100'B

- Start PSC 100
- Number of PSCs 5

16.1.1.2.3.2-3)
E-UTRA

}
priority[1] 4
}
}

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1140 Release 9
1140
Annex A (informative):
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Version
Old
Version
New
2007-08 R5-072514 Initial version 0.0.1
2007-11 Template updated 0.0.1 0.0.2
2008-02 Addition 6 new RRC test cases 0.0.2 0.1.0
2008-04 Addition of new RRC and PDCP test cases
agreed in RAN5#39.
Alignment with latest core specifications.
0.1.0 0.2.0
2008-07 Addition of new MAC, RLC, RRC and EMM test
cases and corrections agreed in RAN5#39bis.
Alignment with latest core specifications.
0.2.0 0.3.0
2008-09 Addition of new MAC, RLC, PDCP and RRC
test cases and corrections agreed in RAN5#40.
0.3.0 1.0.0
2008-10 Addition of new test cases agreed by email
after RAN5#40 and at RAN5#40bis.
1.0.0 1.1.0
2008-11 Addition of new test cases and test case
corrections agreed at RAN5#41.
1.1.0 2.0.0
2008-12 RAN#42 R5-080969 Approval of version 2.0.0 at RAN#42, then put
to version 8.0.0.
2.0.0 8.0.0
2008-01 Editorial corrections 8.0.0 8.0.1
2009-03 RAN#43 R5-090102 0060 - Correction to E-UTRA RLC test case 7.2.3.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090103 0061 - Correction to E-UTRA RLC test case 7.2.3.2 8.0.1 8.1.0
2009-03 RAN#43 R5-090124 0062 - Batch 2 -Update to test case 7.2.2.8 8.0.1 8.1.0
2009-03 RAN#43 R5-090125 0063 - Batch 1B -Update to test case 7.2.2.9 8.0.1 8.1.0
2009-03 RAN#43 R5-090128 0064 - Batch 1A -Update to test case 8.1.1.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090132 0065 - Batch 1A - Update to test case 8.2.4.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090133 0066 - Batch 2 - Update to test case 8.2.4.2 8.0.1 8.1.0
2009-03 RAN#43 R5-090144 0070 - Batch 2 - Addition of new test case 8.4.1.8 8.0.1 8.1.0
2009-03 RAN#43 R5-090145 0071 - Batch 2 - Correction to Idle mode test method 8.0.1 8.1.0
2009-03 RAN#43 R5-090146 0072 - Batch 1A - Update to test case 8.5.4.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090151 0073 - Batch 2 - Addition of new test case 9.2.3.2.10 8.0.1 8.1.0
2009-03 RAN#43 R5-090199 0075 - Removal of EMM test cases 9.2.2.2.4,
9.2.2.2.6, 9.2.2.2.7 and 9.2.2.2.8.
8.0.1 8.1.0
2009-03 RAN#43 R5-090201 0076 - Batch 1:Corrections to MAC test case 7.1.2.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090347 0081 - Batch 2 - Update to MAC test case 7.1.4.3 8.0.1 8.1.0
2009-03 RAN#43 R5-090453 0082 - Batch 1A - Update of E-UTRA RLC (AM) test
case 7.2.3.5
8.0.1 8.1.0
2009-03 RAN#43 R5-090455 0083 - Batch 2 - Update of E-UTRA RLC (AM) test
case 7.2.3.16
8.0.1 8.1.0
2009-03 RAN#43 R5-090498 0084 - Batch 1B: Correction to E-UTRA RLC test case
7.2.2.7
8.0.1 8.1.0
2009-03 RAN#43 R5-090511 0085 - Addition of a new LTE test case 7.3.3.2
Correct functionality of EPS UP encription
algorithms (SNOW 3G)
8.0.1 8.1.0
Correct functionality of EPS AS encription
8.0.1 8.1.0
Correct functionality of EPS AS encription
algorithms (AES)
8.0.1 8.1.0
algorithms (AES)
8.0.1 8.1.0
2009-03 RAN#43 R5-090554 0091 - .Bacth 1:Corrections to MAC test case 7.1.3.4 8.0.1 8.1.0
2009-03 RAN#43 R5-090570 0095 - Update of 36.523-1 Reference list 8.0.1 8.1.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1141 Release 9
1141
2009-03 RAN#43 R5-090605 0096 - Batch 2: Update of LTE TC 8.1.2.3 RRC - RRC
Connection Establishment in RRC Idle state:
return to idle state after T300 timeout
8.0.1 8.1.0
2009-03 RAN#43 R5-090607 0097 - Batch 2: Addition of EMM TC 9.2.1.2.4 for
Successful combined attach procedure, EPS
service only / CS domain not available.
8.0.1 8.1.0
2009-03 RAN#43 R5-090611 0098 - Batch 1:Corrections to EMM test case 9.1.3.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090631 0099 - Batch 1B: Correction to E-UTRA RLC test case
7.2.2.3
8.0.1 8.1.0
2009-03 RAN#43 R5-090645 0100 - Batch 1B: Update of E-UTRAN test case
6.1.1.1
8.0.1 8.1.0
2009-03 RAN#43 R5-090649 0101 - Batch-1B: Introduction of a new EMM test case,
9.2.3.1.4 Normal tracking area update / list of
equivalent PLMNs in the TRACKING AREA
8.0.1 8.1.0
2009-03 RAN#43 R5-090653 0103 - Batch 1: Addition of new MAC test case
7.1.3.9 : MAC reset
8.0.1 8.1.0
2009-03 RAN#43 R5-090654 0104 - Batch 1: Addition of new MAC test case
7.1.4.12 : MAC reset
8.0.1 8.1.0
2009-03 RAN#43 R5-090655 0105 - Batch 1A - Update of E-UTRA MAC test case:
7.1.3.3
8.0.1 8.1.0
2009-03 RAN#43 R5-090656 0106 - Batch 2 - Update of E-UTRA MAC test case:
7.1.2.9
8.0.1 8.1.0
2009-03 RAN#43 R5-090665 0107 - Batch 1B - New E-UTRA PDCP test case -
7.3.1.2 Maintenance of PDCP sequence
numbers (user plane, RLC UM)
8.0.1 8.1.0
2009-03 RAN#43 R5-090666 0108 - Batch 1B - Correction to E-UTRA PDCP test
case 7.3.1.1
8.0.1 8.1.0
2009-03 RAN#43 R5-090667 0109 - Batch 1B - New E-UTRA PDCP test case -
7.3.1.3 Maintenance of PDCP sequence
numbers (user plane, RLC UM, long PDCP SN
(12 bits))
8.0.1 8.1.0
2009-03 RAN#43 R5-090669 0110 - Batch 1B -Update to test case 7.2.2.4 8.0.1 8.1.0
2009-03 RAN#43 R5-090672 0113 - Removal of TC 7.3.5.1 8.0.1 8.1.0
case 7.2.3.17
8.0.1 8.1.0
case 7.2.3.15
8.0.1 8.1.0
2009-03 RAN#43 R5-090676 0116 - Batch 1B - Update of test case 8.2.2.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090677 0117 - Update of RRC batch 1B test case 8.2.2.2 RRC
Connection Reconfiguration / SRB/DRB
Reconfiguration: Success
8.0.1 8.1.0
2009-03 RAN#43 R5-090678 0118 - Batch-1: Update to RRC part 3 test case
8.3.3.1
8.0.1 8.1.0
2009-03 RAN#43 R5-090679 0119 - Batch 1A - TC 9.1.2.1 Authentication accepted -
Update of conformance requirements
8.0.1 8.1.0
2009-03 RAN#43 R5-090680 0120 - Batch 1A - TC 9.3.2.1 Paging procedure
revisited
8.0.1 8.1.0
2009-03 RAN#43 R5-090688 0122 - Update of TC 7.3.6.1 PDCP Discard 8.0.1 8.1.0
2009-03 RAN#43 R5-090689 0123 - Addition of new TC 7.3.5.4 8.0.1 8.1.0
2009-03 RAN#43 R5-090690 0124 - Batch 2 - Update of LTE TC 8.5.1.3 RRC - RRC
Connection Re-establishment: Failure: T311
Expiry
8.0.1 8.1.0
2009-03 RAN#43 R5-090691 0125 - Batch 2 -Update to test case 8.1.2.5 8.0.1 8.1.0
2009-03 RAN#43 R5-090695 0129 - Batch 1B - Update to test case 8.2.4.5 8.0.1 8.1.0
2009-03 RAN#43 R5-090707 0130 - Batch 1A - Update of test case 8.2.4.1 8.0.1 8.1.0
2009-03 RAN#43 R5-090709 0131 - Batch 2: Update of RRC part1 TC 8.1.3.6 RRC
Connection Release: redirection from E-
UTRAN to UTRAN
8.0.1 8.1.0
2009-03 RAN#43 R5-090710 0132 - Batch 2: Update of RRC part3 TC 8.3.1.7
Measurement configuration control and
reporting / intra E-UTRAN measurements:
blacklisting
8.0.1 8.1.0
2009-03 RAN#43 R5-090711 0133 - Corrections to LTE idle mode test cases 8.0.1 8.1.0
2009-03 RAN#43 R5-090712 0134 - Batch 1B: Update of test case 6.1.2.6 8.0.1 8.1.0
2009-03 RAN#43 R5-090713 0135 - Batch 2: Update of LTE TC 8.1.2.2 RRC, Reject
with wait time
8.0.1 8.1.0
2009-03 RAN#43 R5-090714 0136 - Update to test case 8.1.3.1 8.0.1 8.1.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1142 Release 9
1142
2009-03 RAN#43 R5-090715 0137 - Batch 1B: update of E-UTRA PDCP test case
7.3.6.1
8.0.1 8.1.0
2009-03 RAN#43 R5-090716 0138 - Batch 1B: update of E-UTRA PDCP test case
7.3.6.1
8.0.1 8.1.0
8.3.1.3
8.0.1 8.1.0
8.3.1.5
8.0.1 8.1.0
2009-03 RAN#43 R5-090722 0142 - Batch 2: Addition of new EMM TC 9.2.1.2.3:
Successful combined attach procedure, EPS
service only / MSC temporarily not reachable
8.0.1 8.1.0
2009-03 RAN#43 R5-090730 0143 - Bacth 1:Corrections to MAC test case 7.1.2.3 8.0.1 8.1.0
2009-03 RAN#43 R5-090736 0148 - Batch 2: Update of RRC part1 TC 8.1.3.4 RRC
Connection Release: redirection to another E-
UTRAN frequency
8.0.1 8.1.0
2009-03 RAN#43 R5-090740 0149 4 Batch 1A - Update of E-UTRA RLC (AM) test
case 7.2.3.18
8.0.1 8.1.0
2009-05 RAN#44 R5-092052 0150 - GCF Priority 1 - Update of 9.1.2.1 test
procedure sequence and editorials
8.1.0 8.2.0
2009-05 RAN#44 R5-092053 0151 - GCF Priority 2 - Update of TC 9.1.2.3
Authentication not accepted by the network,
GUTI used, authentication reject and re-
authentication
8.1.0 8.2.0
2009-05 RAN#44 R5-092054 0152 - GCF Priority 2 - Update TC 9.1.2.4
Authentication not accepted by the UE MAC
code failure
8.1.0 8.2.0
2009-05 RAN#44 R5-092055 0153 - GCF Priority 2 - New TC 9.1.2.5 Authentication
not accepted by the UE, SQN failure
8.1.0 8.2.0
2009-05 RAN#44 R5-092061 0154 - GCF Priority 1 - Update of RRC test case
9.3.1.1
8.1.0 8.2.0
2009-05 RAN#44 R5-092076 0155 - GCF Priority 2: First Iu mode to S1 mode
intersystem change after attach: go to E-
UTRAN RRC idle: RAU to UTRAN (9.2.3.3.1)
8.1.0 8.2.0
2009-05 RAN#44 R5-092077 0156 - Batch 2: Addition of 8.1.3.9 RRC Redirection
from E-UTRAN to HRPD
8.1.0 8.2.0
2009-05 RAN#44 R5-092078 0157 - Batch 2: Addition of 8.1.3.10 RRC Redirection
from E-UTRAN to CDMA2000-1XRTT
8.1.0 8.2.0
2009-05 RAN#44 R5-092107 0158 - GCF Priority 1 - Update of E-UTRA MAC test
case 7.1.3.1
8.1.0 8.2.0
case 7.1.4.1
8.1.0 8.2.0
case 7.1.4.4
8.1.0 8.2.0
case 7.1.4.5
8.1.0 8.2.0
case 7.1.4.8
8.1.0 8.2.0
case 7.1.4.10
8.1.0 8.2.0
case 7.1.4.13
8.1.0 8.2.0
2009-05 RAN#44 R5-092115 0165 - GCF Priority 1 - Proposal to remove E-UTRA
RLC test case 7.2.3.19
8.1.0 8.2.0
2009-05 RAN#44 R5-092181 0166 - GCF Priority 2 - Update of test case 8.5.1.5 8.1.0 8.2.0
2009-05 RAN#44 R5-092190 0168 - GCF Priority 1 - Update of E-UTRA RLC (AM)
test case 7.2.3.1
8.1.0 8.2.0
test case 7.2.3.2
8.1.0 8.2.0
test case 7.2.3.18
8.1.0 8.2.0
test case 7.2.3.18
8.1.0 8.2.0
2009-05 RAN#44 R5-092213 0172 - Addition of new RRC test case 8.3.2.9 8.1.0 8.2.0
2009-05 RAN#44 R5-092228 0173 - GCF Priority 2 - Update to test case 6.1.2.15 8.1.0 8.2.0
2009-05 RAN#44 R5-092245 0178 - GCF Priority-2: A new EMM test case, 9.2.3.1.8 8.1.0 8.2.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1143 Release 9
1143
UE receives an indication that the RRC
connection was released with cause 'load
balancing TAU required''
2009-05 RAN#44 R5-092247 0179 - Introduction of new EMM test cases, 9.2.3.1.10
and 9.2.3.1.11 Normal tracking area update /
Rejected
8.1.0 8.2.0
2009-05 RAN#44 R5-092248 0180 - Introduction of 9.2.3.1.12 ' Normal tracking area
update / rejected / EPS service not allowed'
8.1.0 8.2.0
2009-05 RAN#44 R5-092249 0181 - Introduction of 9.2.3.1.13 'Normal tracking area
update / rejected / UE identity cannot be
derived by the network'
8.1.0 8.2.0
2009-05 RAN#44 R5-092250 0182 - GCF Priority 2 - Addition of a new test case
6.1.2.11 Inter-frequency cell reselection
8.1.0 8.2.0
update / rejected / UE implicitly detached'
8.1.0 8.2.0
update / rejected / PLMN not allowed'
8.1.0 8.2.0
2009-05 RAN#44 R5-092253 0185 - Introduction of 9.2.3.1.16 ' Normal tracking
area update / rejected / Tracking area not
allowed'
8.1.0 8.2.0
2009-05 RAN#44 R5-092258 0186 - GCF Priority 2 - Update of RRC part1 TC
8.1.3.4 RRC Connection Release: redirection to
another E-UTRAN frequency
8.1.0 8.2.0
2009-05 RAN#44 R5-092260 0187 - GCF Priority 2 - Update of RRC part1 TC
8.1.3.6 RRC Connection Release: redirection
from E-UTRAN to UTRAN
8.1.0 8.2.0
2009-05 RAN#44 R5-092262 0188 - GCF Priority 2 - Correction to idle mode test
cases 6.1.2.3 and 6.1.2.6
8.1.0 8.2.0
2009-05 RAN#44 R5-092272 0189 - LTE-SIG:TDD related updates in RRC sections 8.1.0 8.2.0
2009-05 RAN#44 R5-092276 0190 - "GCF priority 1 - Update of the LTE test case
7.3.3.1 Correct functionality of EPS AS
encription algorithms (SNOW 3G)"
8.1.0 8.2.0
2009-05 RAN#44 R5-092278 0191 - GCF priority 1 - Update of test case 7.3.3.2
8.1.0 8.2.0
2009-05 RAN#44 R5-092295 0198 - Addition of new test case 9.2.1.2.8 8.1.0 8.2.0
2009-05 RAN#44 R5-092300 0202 - Addition of new test case 9.3.1.4 8.1.0 8.2.0
2009-05 RAN#44 R5-092301 0203 - Addition of new test case to test case 10.X.X 8.1.0 8.2.0
2009-05 RAN#44 R5-092327 0204 - GCF Priority 1: Update E-UTRA PDCP TC
7.3.4.1
8.1.0 8.2.0
7.3.4.2
8.1.0 8.2.0
7.3.5.2
8.1.0 8.2.0
7.3.5.3
8.1.0 8.2.0
7.3.5.5
8.1.0 8.2.0
case 7.1.4.6
8.1.0 8.2.0
2009-05 RAN#44 R5-092396 0210 - GCF Priority 2 - Addition of new test case
6.2.2.3
8.1.0 8.2.0
6.2.3.7
8.1.0 8.2.0
6.2.3.8
8.1.0 8.2.0
2009-05 RAN#44 R5-092406 0213 - "GCF Priority 2 - Addition of new LTE test case
7.2.2.11 UM RLC / RLC re-establishment
procedure"
8.1.0 8.2.0
2009-05 RAN#44 R5-092417 0214 - GCF Priority 2:Corrections to EMM test case
9.1.3.2
8.1.0 8.2.0
2009-05 RAN#44 R5-092418 0215 - GCF Priority 1:Corrections to MAC test case
7.1.3.4
8.1.0 8.2.0
7.1.3.5
8.1.0 8.2.0
2009-05 RAN#44 R5-092420 0217 - GCF Priority 1:Corrections to MAC test case 8.1.0 8.2.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1144 Release 9
1144
7.1.4.1
2009-05 RAN#44 R5-092421 0218 - GCF Priority 2: Attach / Abnormal case /
Access barred because of access class barring
or NAS signalling connection establishment
rejected by the network
8.1.0 8.2.0
2009-05 RAN#44 R5-092422 0219 - GCF Priority 2: Corrections to EMM test case
9.4.1
8.1.0 8.2.0
2009-05 RAN#44 R5-092423 0220 - GCF Priority 2:Corrections to EMM test case
9.4.3
8.1.0 8.2.0
7.1.1.2
8.1.0 8.2.0
2009-05 RAN#44 R5-092451 0222 - Update of RSRP / RSRQ measurement result
checking to the RRC part 3 test cases
8.1.0 8.2.0
2009-05 RAN#44 R5-092471 0223 - GCF Priority 2-Correction of the EMM test case
9.2.3.1.4
8.1.0 8.2.0
7.1.2.1
8.1.0 8.2.0
7.1.2.2
8.1.0 8.2.0
7.1.2.5
8.1.0 8.2.0
7.1.2.7
8.1.0 8.2.0
7.1.2.8
8.1.0 8.2.0
2009-05 RAN#44 R5-092500 0229 - GCF priority 2: Update of 10.2.1 for Dedicated
EPS bearer context activation / Success
8.1.0 8.2.0
2009-05 RAN#44 R5-092501 0230 - GCF priority 2: Addition of TC 10.4.1 for EPS
bearer context deactivation / Success
8.1.0 8.2.0
2009-05 RAN#44 R5-092502 0231 - GCF priority 2: Addition of TC 10.5.1 for UE
requested PDN connectivity accepted by the
network
8.1.0 8.2.0
2009-05 RAN#44 R5-092504 0232 - GCF priority TBC: Addition of TC 10.5.2 for UE
requested PDN connectivity accepted by the
network / no PDN address allocated
8.1.0 8.2.0
2009-05 RAN#44 R5-092505 0233 - GCF priority 3: Addition of TC 10.5.3 for UE
requested PDN connectivity not accepted
8.1.0 8.2.0
2009-05 RAN#44 R5-092506 0234 - GCF priority 2: Addition of ESM TC 10.6.1 for
UE requested PDN disconnect procedure
accepted by the network
8.1.0 8.2.0
2009-05 RAN#44 R5-092507 0235 - GCF Priority 3: Addition of ESM TC 10.6.2 for
UE requested PDN disconnect procedure not
8.1.0 8.2.0
2009-05 RAN#44 R5-092510 0236 - GCF priority 2 - Update of 9.2.1.1.17 Attach /
rejected / no suitable cells in tracking area
8.1.0 8.2.0
2009-05 RAN#44 R5-092512 0237 - GCF priority 1: Update of EMM TC 9.3.1.2
Service Request initiated by UE for uplink
signalling
8.1.0 8.2.0
2009-05 RAN#44 R5-092513 0238 - GCF priority 2: Update of 9.2.1.1.17 Attach /
rejected / no suitable cells in tracking area
8.1.0 8.2.0
2009-05 RAN#44 R5-092514 0239 - GCF priority 1: Update of 9.2.1.1.1 Attach
Procedure / Success (valid GUTI)
8.1.0 8.2.0
2009-05 RAN#44 R5-092515 0240 - GCF priority 2: Update of 9.2.1.1.5 Attach
Procedure/ Success / ATTACH ACCEPT
includes the PDN address assigned to the UE
8.1.0 8.2.0
rejected / IMSI invalid
8.1.0 8.2.0
rejected / illegal ME
8.1.0 8.2.0
2009-05 RAN#44 R5-092518 0243 - GCF priority TBC: Update of 9.2.1.1.12 Attach /
rejected / GPRS services not allowed
8.1.0 8.2.0
2009-05 RAN#44 R5-092539 0244 - GCF Priority 1 - Update of RLC section 8.1.0 8.2.0
2009-05 RAN#44 R5-092567 0245 - GCF Priority 2 - Addition of a new test case
6.2.3.5 Inter-RAT Cell Reselection / from E-
UTRA RRC_IDLE to UTRA_Idle
8.1.0 8.2.0
2009-05 RAN#44 R5-092569 0246 - GCF Priority 2: Inter-RAT cell Selection / from
E-UTRA RRC_IDLE to UTRA_Idle, serving cell
becomes non-suitable (SServingCell<0,barred)
8.1.0 8.2.0
2009-05 RAN#44 R5-092570 0247 - GCF Priority 2: Inter-RAT cell Selection / from
E-UTRA RRC_IDLE to GSM_Idle/GPRS
Packet_idle, serving cell becomes non-suitable
(SServingCell<0,barred)
8.1.0 8.2.0
2009-05 RAN#44 R5-092571 0248 - GCF Priority 1 - New E-UTRA MAC test case -
7.1.7.1.1 DL-SCH Transport Block Size support
/ DCI format 1 / RA type 0
8.1.0 8.2.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1145 Release 9
1145
2009-05 RAN#44 R5-092575 0249 - GCF Priority 1 - New E-UTRA MAC test case
7.1.7.1.2 - DL-SCH Transport Block Size
selection / DCI format 1 / RA type 1
8.1.0 8.2.0
7.1.7.2.1 - UL-SCH Transport Block Size
selection / DCI format 0
8.1.0 8.2.0
2009-05 RAN#44 R5-092578 0251 - GCF priority 2: New MAC test case: 7.1.6.1
DRX Operation / (short cycle not configured)
/Parameters configured by RRC (radio resource
configuration)
8.1.0 8.2.0
2009-05 RAN#44 R5-092579 0252 - GCF Priority 2 - New RRC part1 TC 8.1.3.8
RRC Connection Release: redirection from E-
UTRAN to GERAN
8.1.0 8.2.0
2009-05 RAN#44 R5-092583 0254 - GCF Priority 2: Attach Procedure / Success
(last visited TAI, TAI list and equivalent PLMN
list handling) 9.2.1.1.1a
8.1.0 8.2.0
2009-05 RAN#44 R5-092589 0256 - GCF Priority 2 - Addition of new EMM test case
9.3.1.7a
8.1.0 8.2.0
2009-05 RAN#44 R5-092593 0257 - GCF priority 2 - Update of 9.2.1.1.15 Attach /
rejected / roaming not allowed in this tracking
area
8.1.0 8.2.0
7.1.1.1
8.1.0 8.2.0
7.1.4.12
8.1.0 8.2.0
8.3.2.1
8.1.0 8.2.0
2009-05 RAN#44 R5-092701 0262 - GCF Priority-1: Correction to 9.2.3.1.1 'Normal
tracking area update / accepted'
8.1.0 8.2.0
2009-05 RAN#44 R5-092702 0263 - GCF Priority-1: Correction to 9.2.3.1.5'Periodic
tracking area update / accepted'
8.1.0 8.2.0
2009-05 RAN#44 R5-092703 0264 - GCF Priority 2 - Addition of E-UTRAN test case
6.1.2.7 for Cell reselection: Equivalent PLMN
8.1.0 8.2.0
2009-05 RAN#44 R5-092706 0265 - GCF Priority 1 - Update to RRC test cases 8.1.0 8.2.0
2009-05 RAN#44 R5-092712 0266 - GCF Priority 2: New MAC test case 7.1.4.14 8.1.0 8.2.0
2009-05 RAN#44 R5-092715 0269 - GCF Priority 2 - Addition of RRC test case
8.3.2.6
8.1.0 8.2.0
case 7.1.4.7
8.1.0 8.2.0
selection / DCI format 1A / RA type 2 /
Distributed VRB
8.1.0 8.2.0
selection / DCI format 1A / RA type 2 /
Localised VRB
8.1.0 8.2.0
2009-05 RAN#44 R5-092730 0273 - GCF priority 2: New MAC test case: 7.1.6.2
DRX Operation / Parameters (short cycle not
configured) / DRX command MAC control
element reception
8.1.0 8.2.0
2009-05 RAN#44 R5-092731 0274 - GCF Priority 2 - Updates to E-UTRAN Idle
Mode test case 6.1.2.9
8.1.0 8.2.0
2009-05 RAN#44 R5-092732 0275 - GCF Priority 2 - Updates to E-UTRAN Idle
Mode test case 6.1.2.8
8.1.0 8.2.0
2009-05 RAN#44 R5-092741 0276 - GCF Priority 1 - Update to idle mode test cases 8.1.0 8.2.0
2009-05 RAN#44 R5-092751 0277 - Addition of new idle mode test case for ignoring
CSG cells in cell selection when Allowed CSG
list is empty or not supported
8.1.0 8.2.0
2009-05 RAN#44 R5-092752 0278 - GCF Priority 2: New idle mode test case 6.2.3.1 8.1.0 8.2.0
2009-05 RAN#44 R5-092758 0281 - GCF Priority 2 - Updates to E-UTRAN test case
6.1.1.1
8.1.0 8.2.0
2009-05 RAN#44 R5-092760 0282 - GCF Priority 2: New idle mode test case 6.2.3.2 8.1.0 8.2.0
2009-05 RAN#44 R5-092761 0283 - Move common test procedure from sections
6.0.1, 6.0.2, 6.0.3 to TS 36.508
8.1.0 8.2.0
2009-05 RAN#44 R5-092762 0284 - Batch 2 - Addition of new RRC test case 8.3.2.7 8.1.0 8.2.0
2009-05 RAN#44 R5-092763 0285 - Batch 2 - Addition of new RRC test case 8.3.2.8 8.1.0 8.2.0
2009-05 RAN#44 R5-092764 0286 - LTE-SIG:TDD related updates in MAC sections 8.1.0 8.2.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1146 Release 9
1146
2009-05 RAN#44 R5-092768 0287 - GCF Priority-1: Correction to 9.2.2.2.1 'NW
initiated detach / re-attach required'
8.1.0 8.2.0
7.1.2.4
8.1.0 8.2.0
2009-05 RAN#44 R5-092528 0290 4 GCF Priority 1 - Update of E-UTRA MAC test
case 7.1.2.3
8.1.0 8.2.0
2009-05 RAN#44 R5-092785 0291 - GCF priority 2: A/Gb mode READY state to S1
mode cell reselection and E-UTRAN - GERAN
RAU (9.2.3.4.1, 9.2.3.4.2)
8.1.0 8.2.0
2009-05 RAN#44 R5-092786 0292 - GCF Priority 2 - Update of TC 9.2.1.1.14 Attach
/ rejected / tracking area not allowed
8.1.0 8.2.0
- - - - - Editorial corrections and split into sections 8.2.0 8.2.1
2009-09 RAN#45 R5-094075 0293 - GCF Priority 1 - Update of MAC test case
7.1.2.6
8.2.1 8.3.0
7.1.3.1
8.2.1 8.3.0
7.1.3.3
8.2.1 8.3.0
7.1.3.4
8.2.1 8.3.0
7.1.3.5
8.2.1 8.3.0
7.1.3.6
8.2.1 8.3.0
7.1.3.7
8.2.1 8.3.0
7.1.4.1
8.2.1 8.3.0
7.1.4.6
8.2.1 8.3.0
7.1.4.7
8.2.1 8.3.0
7.1.4.8
8.2.1 8.3.0
7.1.4.11
8.2.1 8.3.0
7.1.4.13
8.2.1 8.3.0
7.1.4.15
8.2.1 8.3.0
2009-09 RAN#45 R5-094091 0307 - GCF Priority 1 - Update of PDCP test case
7.3.1.1
8.2.1 8.3.0
8.2.1.1
8.2.1 8.3.0
7.1.4.16
8.2.1 8.3.0
2009-09 RAN#45 R5-094094 0310 - GCF Priority 2 - Update of Idle Mode test case
6.1.2.3
8.2.1 8.3.0
8.1.3.4
8.2.1 8.3.0
8.1.3.6
8.2.1 8.3.0
10.7.1
8.2.1 8.3.0
10.7.2
8.2.1 8.3.0
2009-09 RAN#45 R5-094114 0315 - Addition of new test case 6.2.2.5 8.2.1 8.3.0
2009-09 RAN#45 R5-094122 0317 - Remove TC 8.4.1.8 from TS 36.523-1 8.2.1 8.3.0
8.4.2.4
8.2.1 8.3.0
2009-09 RAN#45 R5-094187 0319 - GCF Priority 2 - New EMM TC 9.1.4.2 8.2.1 8.3.0
2009-09 RAN#45 R5-094189 0320 - GCF Priority 2 - Removal of EMM TC 9.1.2.2 8.2.1 8.3.0
7.1.4.10
8.2.1 8.3.0
2009-09 RAN#45 R5-094196 0322 - GCF Priority 2 - Update of RLC test case
7.2.3.21
8.2.1 8.3.0
8.3.2.6
8.2.1 8.3.0
2009-09 RAN#45 R5-094202 0324 - GCF Priority 2 - Add new RRC test case 8.4.1.2 8.2.1 8.3.0
2009-09 RAN#45 R5-094203 0325 - GCF Priority 2 - Add new RRC test case 8.4.1.4 8.2.1 8.3.0
2009-09 RAN#45 R5-094205 0326 - GCF Priority 3 - Remove RRC test case 8.1.3.3 8.2.1 8.3.0
2009-09 RAN#45 R5-094284 0327 - Removal of the GUTI reallocation procedures
test cases
8.2.1 8.3.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1147 Release 9
1147
2009-09 RAN#45 R5-094289 0328 - GCF Priority 2 - TDD formulation update in
7.1.6.1 DRX Operation / (short cycle not
configured) /Parameters configured by RRC
(radio resource configuration)
8.2.1 8.3.0
2009-09 RAN#45 R5-094290 0329 - GCF Priority 2 - TDD formulation update in
7.1.6.2 DRX Operation / Parameters (short
cycle not configured) / DRX command MAC
control element reception
8.2.1 8.3.0
2009-09 RAN#45 R5-094366 0330 - GCF Priority 2 - Corrections to E-UTRAN test
case 6.1.1.1
8.2.1 8.3.0
2009-09 RAN#45 R5-094369 0331 - GCF Priority 2 - Updates to E-UTRAN test case
6.1.2.7
8.2.1 8.3.0
2009-09 RAN#45 R5-094372 0332 - GCF Priority 2 - Corrections to E-UTRAN test
cases 6.1.2.8 and 6.1.2.9
8.2.1 8.3.0
2009-09 RAN#45 R5-094387 0333 - GCF Priority 2 - Update to test case 9.2.2.1.6 8.2.1 8.3.0
2009-09 RAN#45 R5-094392 0334 - GCF Priority 2 - Correction of discard timer
value to be consistent with test tolerances
8.2.1 8.3.0
2009-09 RAN#45 R5-094399 0335 - GCF Priority 2 - Addition new test case 6.2.3.3 8.2.1 8.3.0
2009-09 RAN#45 R5-094426 0336 - GCF Priority 1 - Corrections to MAC test case
7.1.4.6
8.2.1 8.3.0
7.1.4.10
8.2.1 8.3.0
7.1.4.16
8.2.1 8.3.0
8.3.1.1
8.2.1 8.3.0
8.3.1.3
8.2.1 8.3.0
8.3.1.5
8.2.1 8.3.0
8.3.3.1
8.2.1 8.3.0
2009-09 RAN#45 R5-094577 0343 - GCF Priority 1 - Update of EMM part TC 9.1.3.1
NAS security mode command accepted by the
UE
8.2.1 8.3.0
2009-09 RAN#45 R5-094627 0344 - GCF Priority 2 - Update of MAC TC 7.1.3.2 DL
SPS
8.2.1 8.3.0
2009-09 RAN#45 R5-094628 0345 - GCF Priority 2 - Update of MAC TC 7.1.4.2 UL
SPS
8.2.1 8.3.0
7.1.3.9
8.2.1 8.3.0
2009-09 RAN#45 R5-094635 0347 - GCF Priority 1 - Correction to E-UTRAN RLC
test case 7.2.3.1
8.2.1 8.3.0
2009-09 RAN#45 R5-094636 0348 - GCF Priority 1 - Adding Test Coverage for
Verification of UE setting of the RRC
Establishment Cause in EMM test case
9.2.1.1.1
8.2.1 8.3.0
7.1.4.3
8.2.1 8.3.0
2009-09 RAN#45 R5-094662 0350 - GCF Priority 1 - Corrections to RLC section 8.2.1 8.3.0
7.2.3.9
8.2.1 8.3.0
9.2.3.3.5
8.2.1 8.3.0
8.3.2.8
8.2.1 8.3.0
8.3.2.9
8.2.1 8.3.0
2009-09 RAN#45 R5-094707 0355 - GCF Priority 1 - Correction to E-UTRAN MAC
test case 7.1.2.3
8.2.1 8.3.0
6.2.2.3
8.2.1 8.3.0
6.2.3.7
8.2.1 8.3.0
6.2.3.8
8.2.1 8.3.0
8.1.3.9
8.2.1 8.3.0
8.1.3.10
8.2.1 8.3.0
8.3.2.7
8.2.1 8.3.0
8.3.2.8
8.2.1 8.3.0
2009-09 RAN#45 R5-094833 0363 - GCF Priority 2 - Correction of EMM TC 8.2.1 8.3.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1148 Release 9
1148
9.2.1.1.9 Attach / rejected / IMSI invalid
2009-09 RAN#45 R5-094866 0364 2 GCF Priority 1: Corrections to E-UTRA MAC
test case 7.1.7.1.1
8.2.1 8.3.0
test case 7.1.7.1.2
8.2.1 8.3.0
test case 7.1.7.1.3
8.2.1 8.3.0
test case 7.1.7.1.4
8.2.1 8.3.0
test case 7.2.3.2
8.2.1 8.3.0
2009-09 RAN#45 R5-095004 0369 - GCF Priority 2 - Update of 9.1.2.4 8.2.1 8.3.0
2009-09 RAN#45 R5-095008 0371 - GCF Priority 2 - Update of MAC TC 7.1.4.14
TTI Bundling
8.2.1 8.3.0
2009-09 RAN#45 R5-095028 0372 - GCF Priority 1 - Various corrections to RLC
section of 36.523-1
8.2.1 8.3.0
2009-09 RAN#45 R5-095032 0373 - GCF Priority 2 - Addition of new SMS over SGs
test case 11.1.1
8.2.1 8.3.0
2009-09 RAN#45 R5-095036 0374 - GCF Priority 2 - Correction to 9.2.2.2.2 NW
initiated detach / IMSI detach
8.2.1 8.3.0
2009-09 RAN#45 R5-095037 0375 - GCF Priority 2 - Correction of PDCP status
report
8.2.1 8.3.0
2009-09 RAN#45 R5-095038 0376 - GCF Priority 2 - Correction of PDCP handover
test procedure
8.2.1 8.3.0
Establishment Cause in EMM test case
9.2.2.1.1
8.2.1 8.3.0
Establishment Cause in EMM test case 9.3.1.1
8.2.1 8.3.0
8.2.1 8.3.0
8.2.1 8.3.0
8.2.1 8.3.0
2009-09 RAN#45 R5-095073 0383 - GCF Priority 2 - Update of EMM test case
9.3.1.7a
8.2.1 8.3.0
7.1.4.1
8.2.1 8.3.0
7.1.4.8
8.2.1 8.3.0
7.1.4.13
8.2.1 8.3.0
7.1.4.5
8.2.1 8.3.0
2009-09 RAN#45 R5-095086 0388 - GCF Priority 1 - Various corrections to RLC
section of 36.523-1
8.2.1 8.3.0
2009-09 RAN#45 R5-095087 0389 - GCF Priority 2 - New EMM TC 9.3.1.7 8.2.1 8.3.0
2009-09 RAN#45 R5-095089 0391 - Update to GCF Priority 2 test case 9.2.1.1.7 8.2.1 8.3.0
2009-09 RAN#45 R5-095094 0393 - Update to preamble in L2 UM test cases 8.2.1 8.3.0
2009-09 RAN#45 R5-095097 0394 - Add reference to test procedure for Idle Mode
section
8.2.1 8.3.0
2009-09 RAN#45 R5-095103 0395 - GCF Priority 1 - Update of MAC part TC 7.1.2.1 8.2.1 8.3.0
7.1.4.11
8.2.1 8.3.0
2009-09 RAN#45 R5-095105 0397 - Addition new test case 6.2.3.13 8.2.1 8.3.0
test case 7.1.3.1
8.2.1 8.3.0
2009-09 RAN#45 R5-095112 0400 - GCF Priority 2 - Correction of EMM TC
9.2.1.1.12 Attach / rejected / EPS services not
allowed
8.2.1 8.3.0
2009-09 RAN#45 R5-095113 0401 - GCF Priority 2 - Corrections to test case
9.2.1.1.13 Attach / rejected / PLMN not allowed
8.2.1 8.3.0
2009-09 RAN#45 R5-095116 0402 - GCF Priority 2 - Correction of EMM 9.2.1.1.17
TC Attach / rejected / no suitable cells in
8.2.1 8.3.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1149 Release 9
1149
tracking area
2009-09 RAN#45 R5-095118 0403 - GCF Priority 3 - Correction to EMM TC
9.2.1.2.3 Combined attach procedure / Success
/ EPS services only / MSC temporarily not
reachable
8.2.1 8.3.0
2009-09 RAN#45 R5-095120 0404 - GCF Priority 1 - Various corrections to other
section of 36.523-1
8.2.1 8.3.0
2009-09 RAN#45 R5-095121 0405 - GCF Priority 1 - Various corrections to RRC
Part1 section of 36.523-1
8.2.1 8.3.0
2009-09 RAN#45 R5-095125 0406 - GCF Priority 1 - Update of MAC TC 7.1.4.4 SR 8.2.1 8.3.0
2009-09 RAN#45 R5-095127 0408 - Priority 2 - Update of test case 6.2.2.1 8.2.1 8.3.0
2009-09 RAN#45 R5-095131 0409 2 GCF Priority 1 - Addition of new Multi-layer
Procedures test case 13.1.1
8.2.1 8.3.0
2009-09 RAN#45 R5-095132 0410 2 GCF Priority 1 - Addition of new Multi-layer
Procedures test case 13.2.1
8.2.1 8.3.0
test case 7.2.3.5
8.2.1 8.3.0
2009-09 RAN#45 R5-095135 0412 - GCF Priority 2 - Update of cell reselection test
case 6.1.2.15
8.2.1 8.3.0
handover / In-order delivery and duplicate
elimination in the downlink
8.2.1 8.3.0
2009-09 RAN#45 R5-095139 0414 - GCF Priority 2 - Addition of test case 11.1.3
MO-SMS over SGs in idle mode
8.2.1 8.3.0
2009-09 RAN#45 R5-095140 0415 - GCF Priority 2 - Correction to 9.2.3.1.2 Normal
tracking area update / accepted / 'Active' flag
set
8.2.1 8.3.0
2009-09 RAN#45 R5-095141 0416 - GCF Priority 2 - Correction of TC 9.2.1.1.14
Attach / rejected / tracking area not allowed
8.2.1 8.3.0
2009-09 RAN#45 R5-095148 0417 - GCF Priority 2 - Correction of EMM TC
9.2.1.1.15 Attach / rejected / roaming not
allowed in this tracking area
8.2.1 8.3.0
9.2.3.3.6 for E-UTRAN RRC connection failure /
reselection of UTRAN cell / NAS signaling to
release old S1 interface connection
8.2.1 8.3.0
2009-09 RAN#45 R5-095150 0419 - GCF Priority 2 - Update to test case 10.8.1 8.2.1 8.3.0
2009-09 RAN#45 R5-095151 0420 - GCF Priority 2 - Addition of new SMS over SGs
test case 11.1.2
8.2.1 8.3.0
2009-09 RAN#45 R5-095161 0421 - GCF Priority 1 - Various corrections to Idle
Mode section of 36.523-1
8.2.1 8.3.0
case 7.1.2.4
8.2.1 8.3.0
2009-09 RAN#45 R5-095172 0423 - GCF Priority 4 - New TC 8.1.3.7 RRC
Connection Release: redirection from UTRAN
to E-UTRAN
8.2.1 8.3.0
2009-09 RAN#45 R5-095173 0424 1 GCF Priority 3 - Update to test case 9.2.2.1.2 8.2.1 8.3.0
2009-09 RAN#45 R5-095175 0425 1 GCF Priority 3 - Correction to 9.2.1.2.1
''Combined attach procedure / Success / EPS
and non-EPS services''
8.2.1 8.3.0
2009-09 RAN#45 R5-095177 0426 - GCF Priority 3 - CR to EMM TC 9.2.1.1.19
Attach / Abnormal case / Failure due to non
8.2.1 8.3.0
2009-09 RAN#45 R5-095178 0427 - GCF Priority 3 - New EMM TC 9.2.3.2.1a
Combined tracking area update / successful /
check of last visited TAI and handling of TAI
list, LAI and TMSI
8.2.1 8.3.0
6.2.2.4
8.2.1 8.3.0
test case 7.1.7.2.1
8.2.1 8.3.0
8.4.2.2
8.2.1 8.3.0
2009-09 RAN#45 R5-095208 0431 - GCF Priority 1 - Corrections to RLC test case
7.2.3.7
8.2.1 8.3.0
2009-09 RAN#45 R5-095217 0432 - GCF Priority 1 - Corrections to PDCP test
cases 7.5.3.2 and 7.5.3.3
8.2.1 8.3.0
Part2 section of 36.523-1
8.2.1 8.3.0
Part 3 section of 36.523-1
8.2.1 8.3.0
2009-10 - - - - Minor CR 414 implementation corrections 8.3.0 8.3.1
2009-10 - - - - Minor CR 354 implementation corrections 8.3.1 8.3.2
2009-11 GERAN#GP-092405 0435 - Addition of new Test Case 6.2.3.21 8.3.2 8.4.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1150 Release 9
1150
44
2009-12 RAN#46 R5-095444 0436 - Removal of TC 8.1.2.10 from TS 36.523-1 8.3.2 8.4.0
8.3.2 8.4.0
2009-12 RAN#46 R5-095462 0442 - GCF Priority 3 - Addition of test case 9.2.3.1.9a 8.3.2 8.4.0
2009-12 RAN#46 R5-095467 0443 - GCF Priority 3 - Addition of test case 9.3.1.16 8.3.2 8.4.0
2009-12 RAN#46 R5-095505 0444 - GCF Priority 2 - Update test case 6.1.2.11 8.3.2 8.4.0
2009-12 RAN#46 R5-095507 0445 - GCF Priority 2 - Correction for Measurement
test cases
8.3.2 8.4.0
7.2.3.14
8.3.2 8.4.0
9.2.3.3.5
8.3.2 8.4.0
9.3.1.7a
8.3.2 8.4.0
8.3.1.11
8.3.2 8.4.0
9.2.3.1.5
8.3.2 8.4.0
2009-12 RAN#46 R5-095621 0451 - GCF Priority 2 - Removal of TC 8.4.2.6 8.3.2 8.4.0
2009-12 RAN#46 R5-095774 0452 - GCF Priority 2 - Correction to test case 6.1.1.1 8.3.2 8.4.0
2009-12 RAN#46 R5-095795 0457 - Addition of new DSMIPv6 test case for
Discovery of the Home Agent via DNS
8.3.2 8.4.0
2009-12 RAN#46 R5-095796 0458 - Addition of new DSMIPv6 test case for Security
association establishment without Home Agent
8.3.2 8.4.0
2009-12 RAN#46 R5-095802 0459 - GCF Priority 3 - Addition of new RRC test case
8.4.5.4
8.3.2 8.4.0
8.4.7.3
8.3.2 8.4.0
8.4.7.4
8.3.2 8.4.0
Attach Procedure / Success (valid GUTI)
8.3.2 8.4.0
2009-12 RAN#46 R5-095885 0463 - GCF Priority x - Proposed removal of TC
9.3.1.2 Service Request initiated by UE for
uplink signalling
8.3.2 8.4.0
2009-12 RAN#46 R5-095886 0464 - GCF Priority 2 - Proposed removal of TC
9.2.1.1.5 Attach Procedure / Success /
ATTACH ACCEPT message includes the PDN
address assigned to the UE
8.3.2 8.4.0
2009-12 RAN#46 R5-095901 0465 - GCF Priority 2 - Correction of TC 9.2.3.3.6 E-
UTRAN RRC connection failure / reselection of
UTRAN cell / NAS signaling to release old S1
interface connection
8.3.2 8.4.0
test case 7.1.4.6
8.3.2 8.4.0
2009-12 RAN#46 R5-095963 0467 - GCF Priority 2 - Update of TC 9-1-2-5 for IP
handling over U-plane
8.3.2 8.4.0
8.3.2 8.4.0
8.3.2 8.4.0
8.3.2 8.4.0
2009-12 RAN#46 R5-095980 0471 - GCF Priority 2 - Test Case 9.1.4.2 Clause title
formatting error
8.3.2 8.4.0
2009-12 RAN#46 R5-095997 0472 - GCF Priority 2 - Correction to RRC test case
8.5.1.1
8.3.2 8.4.0
test case 7.2.3.5
8.3.2 8.4.0
2009-12 RAN#46 R5-096024 0474 - GCF Priority 1: Cell number allignment in Test
case 9.1.3.1
8.3.2 8.4.0
2009-12 RAN#46 R5-096027 0475 - GCF Priority 2 - Cell number allignment in Test
case 9.1.3.2
8.3.2 8.4.0
2009-12 RAN#46 R5-096029 0476 - GCF Priority 2 - Cell number allignment in Test
case 9.4.1
8.3.2 8.4.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1151 Release 9
1151
2009-12 RAN#46 R5-096031 0477 - GCF Priority 2: Cell number allignment in Test
case 9.4.3
8.3.2 8.4.0
2009-12 RAN#46 R5-096034 0478 - GCF Priority 2: Correction to Test case 7.1.4.2 8.3.2 8.4.0
2009-12 RAN#46 R5-096149 0480 - GCF Priority 2 - update test case 8.5.1.3 8.3.2 8.4.0
7.2.3.13
8.3.2 8.4.0
8.3.2 8.4.0
2009-12 RAN#46 R5-096161 0483 - GCF Priority 1 and Priority 2- EMM Successful
Attach consistent description
8.3.2 8.4.0
2009-12 RAN#46 R5-096178 0484 - GCF Priority 2 - Correction test cases 8.3.2.1,
8.3.2.7
8.3.2 8.4.0
2009-12 RAN#46 R5-096192 0485 - GCF Priority 1 - Various editorial corrections to
RLC section
8.3.2 8.4.0
2009-12 RAN#46 R5-096193 0486 - GCF Priority 1 - Update to Idle Mode test case
6.1.2.2
8.3.2 8.4.0
2009-12 RAN#46 R5-096194 0487 - GCF Priority 2 - Updated to test case 6.1.2.6 8.3.2 8.4.0
2009-12 RAN#46 R5-096196 0488 - GCF Priority 2 - Correction to test case 6.3.6 8.3.2 8.4.0
test case 7.1.2.9
8.3.2 8.4.0
2009-12 RAN#46 R5-096414 0491 - GCF Priority 2 & 3 - Correction to test cases
9.2.1.1.9 and 9.2.1.1.12
8.3.2 8.4.0
2009-12 RAN#46 R5-096421 0492 - GCF Priority 1: Update of MAC TC 7.1.7.1.1
DL-SCH TBS selection/DCI format 1/RA type0
8.3.2 8.4.0
DL-SCH TBS selection/DCI format 1/RA type1
8.3.2 8.4.0
DL-SCH TBS selection/DCI format 1A/RA
type2/Localized VRB
8.3.2 8.4.0
DL-SCH TBS selection/DCI format 1A/RA
type2/Distributed VRB
8.3.2 8.4.0
UL-SCH TBS selection/DCI format 0
8.3.2 8.4.0
2009-12 RAN#46 R5-096426 0497 1 GCF Priority 1: Update of E-UTRA MAC test
case 7.1.4.7
8.3.2 8.4.0
2009-12 RAN#46 R5-096428 0498 - GCF Priority 1: Update of E-UTRA MAC test
case 7.1.3.7
8.3.2 8.4.0
2009-12 RAN#46 R5-096435 0500 - GCF Priority 3: Introduction of a new EMM test
case 9.2.3.1.6' Normal tracking area update /
UE with ISR active moves to E-UTRAN '
8.3.2 8.4.0
2009-12 RAN#46 R5-096436 0501 - GCF Priority 3: Introduction of 9.2.3.1.17
Normal tracking area update / rejected /
Roaming not allowed in this tracking area
8.3.2 8.4.0
Normal tracking area update / rejected / EPS
services not allowed in this PLMN
8.3.2 8.4.0
2009-12 RAN#46 R5-096443 0503 - GCF Priority 3: Addition of new test case
9.2.1.1.24: Attach / Abnormal case / Change of
cell into a new tracking area
8.3.2 8.4.0
9.2.1.1.26: Attach / Abnormal case / Detach
procedure collision
8.3.2 8.4.0
2009-12 RAN#46 R5-096446 0506 - GCF Priority 1: Correction to EMM test case
9.3.1.1
8.3.2 8.4.0
2009-12 RAN#46 R5-096451 0507 - GCF Priority 2 - Correction of test cases
9.2.1.1.9, 9.2.1.1.10, 9.2.1.1.11 Attach /
rejected / IMSI invalid / Illegal UE / EPS and
non-EPS services not allowed
8.3.2 8.4.0
Combined tracking area update / successful
8.3.2 8.4.0
2009-12 RAN#46 R5-096454 0509 - GCF Priority 2 - Correction of TC 9.2.3.3.1 First
Iu mode to S1 mode intersystem change after
attach: go to E-UTRAN RRC idle: RAU to
UTRAN
8.3.2 8.4.0
2009-12 RAN#46 R5-096459 0510 - Disabling PHR and periodic BSR for L2 test
cases in 36.523-1
8.3.2 8.4.0
2009-12 RAN#46 R5-096466 0511 - Correction of test case 6.1.2.13 8.3.2 8.4.0
test case 7.1.4.13
8.3.2 8.4.0
2009-12 RAN#46 R5-096468 0513 - GCF Priority 1 - Correction to E-UTRAN MAC 8.3.2 8.4.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1152 Release 9
1152
test case 7.1.4.10
8.3.3.3 for Measurement configuration control
and reporting / SON / ANR: CGI reporting of
GERAN cell
8.3.2 8.4.0
8.3.3.2 :Measurement configuration control and
reporting / SON / ANR: CGI reporting of
UTRAN cell
8.3.2 8.4.0
2009-12 RAN#46 R5-096472 0516 - GCF Priority 1 - Update of Multi-layer
Procedures part TC 13.1.1 Activation and
deactivation of additional data radio bearer in
E-UTRA
8.3.2 8.4.0
2009-12 RAN#46 R5-096476 0517 - GCF Priority 3 - Update of RRC part TC 8.5.1.2
RRC Connection Re-establishment: Success
(after Radio Link Failure)
8.3.2 8.4.0
8.2.1.7
8.3.2 8.4.0
2009-12 RAN#46 R5-096482 0520 - GCF Priority 1 - Correction of TC 8.5.4.1 UE
capability transfer / Success
8.3.2 8.4.0
7.3.3.1 : Ciphering and Deciphering: Correct
functionality of EPS AS encription algorithms
(SNOW 3G)
8.3.2 8.4.0
2009-12 RAN#46 R5-096484 0522 - GCF Priority 1: Correction to RRC test case
8.2.1.1
8.3.2 8.4.0
9.2.3.1.1
8.3.2 8.4.0
Mode section of 36.523-1
8.3.2 8.4.0
8.3.2 8.4.0
2009-12 RAN#46 R5-096492 0528 - GCF Priority 1 - Correction to E-UTRA DRB
test case 12.2
8.3.2 8.4.0
2009-12 RAN#46 R5-096493 0529 3 GCF Priority 1 - Update of Multi-layer
Procedures part TC 13.2.1 RRC Connection
Reconfiguration: E-UTRA to E-UTRA
8.3.2 8.4.0
2009-12 RAN#46 R5-096494 0530 - GCF Priority 1 - Update of applicabilty entry for
DRB test case 12.3
8.3.2 8.4.0
2009-12 RAN#46 R5-096495 0531 - GCF Priority 2 - Update of the test case 6.2.3.3 8.3.2 8.4.0
2009-12 RAN#46 R5-096496 0532 - GCF Priority 2 - Update of Idle Mode
Operations test case 6.1.2.5 Cell reselection for
inter-band operation
8.3.2 8.4.0
2009-12 RAN#46 R5-096497 0533 - GCF Priority 2 - Update of Idle Mode
Operations test case 6.6.2.3.7
8.3.2 8.4.0
2009-12 RAN#46 R5-096502 0534 - GCF Priority 2: Correction to the MAC DRX test
cases preamble
8.3.2 8.4.0
Attach / rejected / PLMN not allowed
8.3.2 8.4.0
Attach / rejected / tracking area not allowed
8.3.2 8.4.0
Attach / rejected / roaming not allowed in this
tracking area
8.3.2 8.4.0
2009-12 RAN#46 R5-096508 0538 - GCF Priority 3 - New TC 9.2.1.1.16 Attach /
rejected / EPS services not allowed in this
PLMN
8.3.2 8.4.0
Attach / rejected / no suitable cells in tracking
area
8.3.2 8.4.0
Combined attach procedure / Success / EPS
services only / MSC temporarily not reachable
8.3.2 8.4.0
2009-12 RAN#46 R5-096511 0541 - GCF Priority 2 - Correction of TC 10.2.1
Dedicated EPS bearer context activation /
Success
8.3.2 8.4.0
2009-12 RAN#46 R5-096512 0542 - GCF Priority 2 - Correction of TC 10.3.1 EPS
bearer context modification / Success
8.3.2 8.4.0
2009-12 RAN#46 R5-096514 0543 - GCF Priority 2 - Correction of TC 10.6.1 UE
requested PDN disconnect procedure accepted
by the network
8.3.2 8.4.0
2009-12 RAN#46 R5-096605 0544 - GCF Priority 2 - Update of RRC test case 8.3.2 8.4.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1153 Release 9
1153
8.3.2.7 : Measurement configuration control
and reporting / inter-RAT measurements: event
B2 (measurement HRPD cells)
8.3.2.6
8.3.2 8.4.0
8.4.1.4
8.3.2 8.4.0
8.4.1.2
8.3.2 8.4.0
2009-12 RAN#46 R5-096619 0554 - GCF Priority 2: Updates to TAU/RAU procedure
for inter-system cell re-selection between A/Gb
and S1 modes
8.3.2 8.4.0
2009-12 RAN#46 R5-096620 0555 - GCF Priority 2: Updates to Attach Procedure /
Success (last visited TAI, TAI list and
equivalent PLMN list handling)
8.3.2 8.4.0
2009-12 RAN#46 R5-096621 0556 - GCF Priority 2 - Correction to TC 8.1.3.8 8.3.2 8.4.0
8.2.2.1
8.3.2 8.4.0
8.2.2.2
8.3.2 8.4.0
2009-12 RAN#46 R5-096629 0560 - GCF Priority 3 - Various corrections to EMM
section of 36.523-1
8.3.2 8.4.0
9.2.1.2.5
8.3.2 8.4.0
2009-12 RAN#46 R5-096632 0563 - GCF Priority 3 - Addition of test case 9.2.1.2.7 8.3.2 8.4.0
2009-12 RAN#46 R5-096633 0564 - GCF Priority 3 - Addition of test case 9.2.1.2.11 8.3.2 8.4.0
2009-12 RAN#46 R5-096634 0565 1 GCF Priority 3 - Addition of test case 9.2.1.2.13 8.3.2 8.4.0
9.2.1.2.15
8.3.2 8.4.0
2009-12 RAN#46 R5-096636 0567 - GCF Priority 3 - Addition of test cases
9.2.3.1.23 and 9.2.3.1.24
8.3.2 8.4.0
9.2.3.1.25
8.3.2 8.4.0
9.2.3.2.9
8.3.2 8.4.0
7.2.3.9
8.3.2 8.4.0
8.3.3.4
8.3.2 8.4.0
8.3.3.5
8.3.2 8.4.0
10.7.3
8.3.2 8.4.0
10.7.4
8.3.2 8.4.0
2009-12 RAN#46 R5-096649 0576 - GCF Priority TBC - Addition of new test case
10.7.5
8.3.2 8.4.0
10.8.2
8.3.2 8.4.0
10.8.3
8.3.2 8.4.0
2009-12 RAN#46 R5-096652 0579 - GCF Priority TBC - Addition of new test case
10.8.4
8.3.2 8.4.0
10.8.5
8.3.2 8.4.0
10.8.6
8.3.2 8.4.0
10.8.7
8.3.2 8.4.0
2009-12 RAN#46 R5-096656 0583 - GCF Priority 2 - Correction of TC 10.5.1 UE
requested PDN connectivity procedure
8.3.2 8.4.0
2009-12 RAN#46 R5-096657 0584 - GCF Priority 2 - Addition of test case 11.1.4
MO-SMS over SGs in active mode
8.3.2 8.4.0
2009-12 RAN#46 R5-096658 0585 - GCF Priority 2 - Correction of TC 10.4.1 EPS
bearer context deactivation / Success
8.3.2 8.4.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1154 Release 9
1154
2009-12 RAN#46 R5-096660 0586 - GCF Priority 3 - Addition of EMM test case
9.1.2.6
8.3.2 8.4.0
9.1.5.2
8.3.2 8.4.0
9.2.1.1.18
8.3.2 8.4.0
9.2.1.2.12
8.3.2 8.4.0
9.2.2.2.14
8.3.2 8.4.0
9.2.3.1.26
8.3.2 8.4.0
9.2.3.1.27
8.3.2 8.4.0
9.2.3.1.28
8.3.2 8.4.0
9.3.1.15
8.3.2 8.4.0
9.3.1.17
8.3.2 8.4.0
services only / IMSI unknown in HSS
8.3.2 8.4.0
services only / MSC temporarily not reachable
8.3.2 8.4.0
Normal tracking area update / rejected / No
Suitable Cells in tracking Area
8.3.2 8.4.0
2009-12 RAN#46 R5-096692 0599 - GCF Priority 3 - Update of E-UTRAN test case
9.2.1.1.20
8.3.2 8.4.0
Attach / Abnormal case / Failure due to non
8.3.2 8.4.0
9.2.1.1.21: Attach / Abnormal case / success
after several attempts due to no network
response
8.3.2 8.4.0
9.2.1.1.22: : Attach / Abnormal case /
unssuccesful attach after 5 attempts
8.3.2 8.4.0
2009-12 RAN#46 R5-096697 0603 1 GCF Priority 3 - Addition of test case 13.3.1.1 8.3.2 8.4.0
Registration of a new IPv6 CoA (Binding
Update/Acknowledgment procedure in IPv6
network)
8.4.0 8.5.0
2010-03 RAN#47 R5-100059 0605 - Addition of new DSMIPv6 test case for Re-
registration of IPv6 CoA
8.4.0 8.5.0
2010-03 RAN#47 R5-100060 0606 - Addition of new DSMIPv6 test case for Return
to home link
8.4.0 8.5.0
2010-03 RAN#47 R5-100061 0607 - Addition of new DSMIPv6 test case for Dual-
Stack Mobile IPv6 detach in IPv6 network
8.4.0 8.5.0
2010-03 RAN#47 R5-100089 0608 - GCF priority 2 - Correction of test case 10.5.1
for UE requested PDN connectivity accepted by
the network
8.4.0 8.5.0
2010-03 RAN#47 R5-100096 0609 - GCF priority 3 - Correction of test case
9.2.1.2.2 for Combined attach procedure /
Success / EPS services only / IMSI unknown in
HSS
8.4.0 8.5.0
2010-03 RAN#47 R5-100100 0610 - GCF priority 2: correction of test case 9.2.3.3.1
First Iu mode to S1 mode intersystem change
after attach: go to E-UTRAN RRC idle: RAU to
UTRAN
8.4.0 8.5.0
2010-03 RAN#47 R5-100173 0611 - Update of test case 9.2.3.1.28 8.4.0 8.5.0
2010-03 RAN#47 R5-100175 0612 - Update of test case 9.1.5.2 8.4.0 8.5.0
2010-03 RAN#47 R5-100182 0614 - Priority 2-Update of the case 6.2.2.1 8.4.0 8.5.0
2010-03 RAN#47 R5-100242 0615 - GCF Priority 1: Update of MAC TC 7.1.2.3 8.4.0 8.5.0
2010-03 RAN#47 R5-100263 0616 - Correcction to MAC TBS selection TCs not to
use RS power boosting
8.4.0 8.5.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1155 Release 9
1155
2010-03 RAN#47 R5-100383 0635 - GCF Priority 1- Update of MAC test cases
7.1.4.6, 7.1.4.7, 7.1.4.8
8.4.0 8.5.0
2010-03 RAN#47 R5-100415 0636 - GCF Priority 2 - Correction to remark in 6.2.2.1,
6.2.2.2 and 6.2.3.2
8.4.0 8.5.0
2010-03 RAN#47 R5-100443 0638 - GCF Priority 2: Update to test case 9.2.3.1.4 8.4.0 8.5.0
Registration of a new IPv4 CoA (Binding
Update/Acknowledgment procedure in IPv4
network)
8.4.0 8.5.0
2010-03 RAN#47 R5-100468 0641 - Addition of new DSMIPv6 test case for Re-
registration of IPv4 CoA
8.4.0 8.5.0
2010-03 RAN#47 R5-100469 0642 - Addition of new DSMIPv6 test case for Dual-
Stack Mobile IPv6 detach in IPv4 network
8.4.0 8.5.0
2010-03 RAN#47 R5-100470 0643 - GCF Priority 2 - Update to P2 EMM test case
9.2.2.1.1
8.4.0 8.5.0
2010-03 RAN#47 R5-100471 0644 - Update to P3 EMM test case 9.2.2.1.2 8.4.0 8.5.0
2010-03 RAN#47 R5-100472 0645 - GCF Priority 2 - Update to P2 EMM test case
9.2.2.1.6
8.4.0 8.5.0
2010-03 RAN#47 R5-100475 0646 - Removal of TC 10.5.2 8.4.0 8.5.0
2010-03 RAN#47 R5-100488 0647 - GCF priority 1 - Update of RRC test case
8.2.2.1
8.4.0 8.5.0
8.2.2.2
8.4.0 8.5.0
8.2.3.1
8.4.0 8.5.0
2010-03 RAN#47 R5-100500 0650 - GCF Priority 1: Clarification to UE initial state
for test case 7.1.2.6
8.4.0 8.5.0
2010-03 RAN#47 R5-100501 0651 - GCF Priority 2 - Clarification to UE initial state 8.4.0 8.5.0
2010-03 RAN#47 R5-100537 0652 - GCF Priority 1 - Correction to E-UTRA RLC test
case 7.2.3.21
8.4.0 8.5.0
test case 7.1.2.3
8.4.0 8.5.0
test case 7.1.4.7
8.4.0 8.5.0
2010-03 RAN#47 R5-100592 0655 - GCF Priority 3 - Correction to P3 EMM test
case 9.2.1.2.12
8.4.0 8.5.0
2010-03 RAN#47 R5-100625 0656 - GCF Priority 1: Corrections to E-UTRA MAC
test case 7.1.7.1.1
8.4.0 8.5.0
7.2.2.5.2
8.4.0 8.5.0
7.2.2.6
8.4.0 8.5.0
7.2.2.7
8.4.0 8.5.0
7.2.3.2
8.4.0 8.5.0
7.2.3.3
8.4.0 8.5.0
7.2.3.5
8.4.0 8.5.0
7.2.3.6
8.4.0 8.5.0
test case 7.1.7.1.2
8.4.0 8.5.0
test case 7.1.7.1.3
8.4.0 8.5.0
2010-03 RAN#47 R5-100738 0666 - Priority 2 - Incorrect ATTACH procedure to
UTRAN and GERAN cells
8.4.0 8.5.0
2010-03 RAN#47 R5-100741 0667 - GCF Priority x - Clarification to E-UTRA Radio
Bearer Tests section
8.4.0 8.5.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1156 Release 9
1156
2010-03 RAN#47 R5-100742 0668 - Priority 3 - TC 9.2.3.1.15 Normal tracking area
update / rejected / PLMN not allowed -
problems with Test procedure sequence
8.4.0 8.5.0
2010-03 RAN#47 R5-100745 0669 - GCF Priority 3 - Adding new TC 9.1.5.1 EMM
Information Procedure
8.4.0 8.5.0
7.1.4.3
8.4.0 8.5.0
2010-03 RAN#47 R5-101011 0671 - Priority ALL - Update of section 6 Idle Mode
Operations to comply with RAN5 PRD13
8.4.0 8.5.0
2010-03 RAN#47 R5-101012 0672 - Priority ALL - Update of section 9.1.x and
9.2.1.x to indicate on which cell events are to
be observed in multi cell environment
8.4.0 8.5.0
2010-03 RAN#47 R5-101013 0673 - GCF Priority 2 - Removal of test case 9.2.3.2.3 8.4.0 8.5.0
2010-03 RAN#47 R5-101032 0675 2 GCF Priority 2 - Correction of RRC test cases
8.3.1.3 and 8.3.1.5
8.4.0 8.5.0
2010-03 RAN#47 R5-101033 0676 1 GCF Priority 3 - Correction of RRC test cases
8.3.1.7 and 8.3.1.11
8.4.0 8.5.0
2010-03 RAN#47 R5-101039 0678 - Correction for Measurement related test cases 8.4.0 8.5.0
8.2.1.3
8.4.0 8.5.0
2010-03 RAN#47 R5-101056 0680 - Priority ALL - Update of section 7 Layer 2 to
comply with RAN5 PRD13
8.4.0 8.5.0
Mode section 6.1 of 36.523-1
8.4.0 8.5.0
2010-03 RAN#47 R5-101062 0682 - GCF Priority 1 - Correction to E-UTRAN PDPC
test case 7.1.4.4
8.4.0 8.5.0
2010-03 RAN#47 R5-101063 0683 - GCF Priority 1:Update of MAC TC 7.1.2.5 8.4.0 8.5.0
2010-03 RAN#47 R5-101069 0689 - GCF Priority 3 - Corrections to TC 8.5.1.2 RRC
Connection Re-establishment: Success (after
Radio Link Failure)
8.4.0 8.5.0
test case 7.1.4.13
8.4.0 8.5.0
2010-03 RAN#47 R5-101074 0691 - New priority 3 test case: Periodic Location
Updating Procedure (PLU Timer handling, non-
cell reselection to GERAN)
8.4.0 8.5.0
9.2.3.3.4
8.4.0 8.5.0
test case 7.1.3.4
8.4.0 8.5.0
2010-03 RAN#47 R5-101078 0695 - GCF Priority 1 - Update of MAC Procedures
part TC 7.1.2.2
8.4.0 8.5.0
2010-03 RAN#47 R5-101079 0696 - GCF Priority 1 - Correction to MAC test case
7.1.4.10
8.4.0 8.5.0
test case 7.1.7.1.4
8.4.0 8.5.0
2010-03 RAN#47 R5-101085 0701 - GCF Priority 1 - Update of Acknowledged Mode
Procedures part TC 7.2.3.15 AM RLC / Re-
ordering of RLC PDU segments"
8.4.0 8.5.0
7.2.3.14
8.4.0 8.5.0
7.2.3.4
8.4.0 8.5.0
7.2.3.1
8.4.0 8.5.0
2010-03 RAN#47 R5-101089 0705 1 GCF Priority 1 - Update of RLC test case
7.2.3.7
8.4.0 8.5.0
2010-03 RAN#47 R5-101090 0706 2 GCF Priority 1 - Update of RLC test case
7.2.3.18
8.4.0 8.5.0
2010-03 RAN#47 R5-101092 0707 - GCF priority 2 - EPS bearer context ID values
and RRC messages carrying ESM messages
for EPS bearer context (de)activation and
modification
8.4.0 8.5.0
2010-03 RAN#47 R5-101093 0708 - GCF priority 3 - Small correction to TC
9.2.1.1.11 Attach / rejected / EPS services and
8.4.0 8.5.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1157 Release 9
1157
non-EPS services not allowed
9.2.1.1.15 for Attach / rejected / roaming not
allowed in this tracking area
8.4.0 8.5.0
8.2.1.1
8.4.0 8.5.0
2010-03 RAN#47 R5-101108 0712 - GCF Priority 2 - Correction to EUTRAN RLC
test case 7.2.2.10
8.4.0 8.5.0
9.2.1.2.4 for Successful combined attach
procedure, EPS service only / CS domain not
available
8.4.0 8.5.0
2010-03 RAN#47 R5-101113 0714 - GCF Priority 1 - Correction to E-UTRA PDCP
test case 7.3.4.1 and 7.3.4.2
8.4.0 8.5.0
2010-03 RAN#47 R5-101114 0715 - GCF Priority 1 - Enhancement test case 8.1.2.1 8.4.0 8.5.0
2010-03 RAN#47 R5-101117 0716 - GCF Priority 1 - Correction to EMM test cases
to bring the UE to stable state at the end of
expected sequence
8.4.0 8.5.0
Procedures part TC 13.1.1 Activation and
deactivation of additional data radio bearer in
E-UTRA
8.4.0 8.5.0
Procedures part TC 13.2.1 RRC Connection
Reconfiguration: E-UTRA to E-UTRA
8.4.0 8.5.0
2010-03 RAN#47 R5-101121 0720 - GCF Priority 1 - Correction to EPC test case
9.2.1.1.1
8.4.0 8.5.0
2010-03 RAN#47 R5-101122 0721 - Priority 2 - section 9 alignment IP handling at
wrong place - Missing security activation -
Editorial changes
8.4.0 8.5.0
test case 7.2.3.15
8.4.0 8.5.0
test case 7.2.3.9
8.4.0 8.5.0
2010-03 RAN#47 R5-101130 0724 - GCF Priority 1 - Correction of RRC test case
8.3.3.1
8.4.0 8.5.0
2010-03 RAN#47 R5-101131 0725 1 GCF Priority 1 - Correction to MAC test cases
expected sequence
8.4.0 8.5.0
2010-03 RAN#47 R5-101132 0726 - GCF Priority 1 - Correction to RRC test cases
expected sequence
8.4.0 8.5.0
8.4.7.1
8.4.0 8.5.0
8.3.2.10
8.4.0 8.5.0
2010-03 RAN#47 R5-101145 0732 - General note for test cases with statistical
behaviour
8.4.0 8.5.0
2010-03 RAN#47 R5-101158 0740 - GCF Priority 3: New PUSCH-Hopping test case
7.1.5.2:Predefined intra-TTI PUSCH hopping
(N_sb=1)
8.4.0 8.5.0
7.1.5.4: Predefined inter-TTI PUSCH hopping
(N_sb=1)
8.4.0 8.5.0
2010-03 RAN#47 R5-101162 0742 1 GCF priority 3 - New test case 8.1.1.6 RRC /
BCCH modification in connected mode
8.4.0 8.5.0
2010-03 RAN#47 R5-101163 0743 - GCF Priority 3 - New TC 8.5.2.1 RRC
Connection Reject: redirection from UTRAN to
E-UTRAN
8.4.0 8.5.0
2010-03 RAN#47 R5-101164 0744 - GCF Priority 3 - addition of new EMM test case
9.2.1.2.14
8.4.0 8.5.0
2010-03 RAN#47 R5-101166 0746 - Update of test case 9.2.1.1.18 8.4.0 8.5.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1158 Release 9
1158
2010-03 RAN#47 R5-101167 0747 - GCF Priority 3: Update to test case 9.2.3.1.6 8.4.0 8.5.0
for UE requested PDN connectivity procedure
not accepted
8.4.0 8.5.0
2010-03 RAN#47 R5-101169 0749 - GCF Priority 3 - Addition of new multi-layer test
case 13.1.3
8.4.0 8.5.0
13.4.1.2
8.4.0 8.5.0
Procedures part TC 13.3.1.1 Intra System
Connection Reestablishment / Radio Link
Recovery while T310 is running
8.4.0 8.5.0
2010-03 RAN#47 R5-101172 0752 - GCF Priority 3 - update of test case 13.3.1.2 8.4.0 8.5.0
2010-03 RAN#47 R5-101173 0753 - GCF Priority 2 : Correction to MAC test case
7.1.6.1
8.4.0 8.5.0
2010-03 RAN#47 R5-101174 0754 - GCF Priority 2 : Correction to MAC test cases
7.1.6.2
8.4.0 8.5.0
2010-03 RAN#47 R5-101175 0755 2 GCF Priority 1 - Correction to E-UTRAN RLC
test case 7.2.3.10
8.4.0 8.5.0
2010-03 RAN#47 R5-101177 0756 - Update to GCF Priority 1 layer 2 UM test cases
to increase the drx-Inactivity Timer to psf200
8.4.0 8.5.0
2010-03 RAN#47 R5-101179 0757 - GCF Priority 1 - Enhancement and update to
MAC test case 7.1.4.6
8.4.0 8.5.0
2010-03 RAN#47 R5-101186 0759 - Update of test case and section titles 8.4.0 8.5.0
2010-03 RAN#47 R5-101191 0762 - Corrections related to UE mode of operation
and UE capability for CS fallback and SMS over
SGs
8.4.0 8.5.0
for UE requested PDN disconnect procedure
not accepted by the network
8.4.0 8.5.0
2010-03 GERAN#
45
GP-100543 0605 - Addition of new Test Case 6.2.3.22 8.4.0 8.5.0
2010-03 RAN#47 - - - Moved to v9.0.0 with no change 8.5.0 9.0.0
2010-05 GERAN#
46
GP-100625 0764 - New Test case 6.2.3.28- Inter-RAT Cell
Reselection from GPRS Packet_transfer to E-
UTRA Cell (Network Assisted Cell Change)
9.0.0 9.1.0
2010-05 GERAN#
46
GP-100626 0765 - New Test Case 6.2.3.30 - Inter-RAT Cell
Reselection failure from GPRS Packet transfer
to E-UTRA (Network Assisted Cell Change)
9.0.0 9.1.0
2010-05 GERAN#
46
selection / From GSM_Idle/GPRS Packet_idle
to E-UTRA_RRC_IDLE / Serving cell becomes
non-suitable (ServingCell<0)
9.0.0 9.1.0
2010-05 GERAN#
46
selection / From GSM_Idle/GPRS Packet_idle
to E-UTRA_RRC_IDLE ,when the serving cell
is barred.
9.0.0 9.1.0
2010-06 RAN#48 R5-103077 0768 - GCF Priority 2 - Correction of Minimum Cell
Configuration
9.0.0 9.1.0
2010-06 RAN#48 R5-103086 0769 - GCF Priority 3: New TC 9.3.1.5 Service request
/ Rejected / Illegal ME
9.0.0 9.1.0
test case 7.1.2.3
9.0.0 9.1.0
7.1.4.10
9.0.0 9.1.0
2010-06 RAN#48 R5-103089 0772 - GCF Priority 3 - Update of TC 9.1.5.1 EMM
Information Procedure
9.0.0 9.1.0
2010-06 RAN#48 R5-103090 0773 - GCF Priority 2 - Correction to TC 9.1.2.4
Authentication not accepted by the UE / MAC
code failure
9.0.0 9.1.0
2010-06 RAN#48 R5-103091 0774 - GCF Priority 2 - Correction to TC 9.1.2.5
Authentication not accepted by the UE / SQN
failure
9.0.0 9.1.0
2010-06 RAN#48 R5-103093 0775 - GCF Priority 2 - Correction of SIB in RRC TCs
8.4.2.2 and 8.4.2.4
9.0.0 9.1.0
2010-06 RAN#48 R5-103131 0777 - GCF Priority 1 - Correction to PDSCH power
allocation of MAC TBS selection TCs
9.0.0 9.1.0
2010-06 RAN#48 R5-103132 0778 - GCF Priority 3 - Correction of test case 6.2.3.13 9.0.0 9.1.0
8.3.2.2
9.0.0 9.1.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1159 Release 9
1159
8.3.2.5
9.0.0 9.1.0
2010-06 RAN#48 R5-103139 0782 - GCF Priority 3 - Correction for test case
13.4.1.2
9.0.0 9.1.0
13.4.2.1
9.0.0 9.1.0
2010-06 RAN#48 R5-103141 0784 - GCF Priority 2 - Update test case 6.1.2.11 &
6.1.2.15
9.0.0 9.1.0
2010-06 RAN#48 R5-103144 0785 - GCF Priority 4 Addition of new test case 14.1 9.0.0 9.1.0
2010-06 RAN#48 R5-103145 0786 - GCF Priority 4 Addition of new test case 14.2 9.0.0 9.1.0
2010-06 RAN#48 R5-103157 0787 - GCF Priority 4: New MAC TBS test case
7.1.7.1.6:DCI format 2A / RA type 1
9.0.0 9.1.0
2010-06 RAN#48 R5-103158 0788 - GCF Priority 4: New MAC TBS test case
7.1.7.1.5:DCI format 2A / RA type 0
9.0.0 9.1.0
2010-06 RAN#48 R5-103159 0789 - GCF Priority 4: Correction to E-UTRA DRB test
case 12.3.1
9.0.0 9.1.0
case 12.3.2
9.0.0 9.1.0
case 12.3.3
9.0.0 9.1.0
case 12.3.4
9.0.0 9.1.0
2010-06 RAN#48 R5-103163 0793 - GCF Priority 4: Correction to generic test
procedure 12.1.2 for E-UTRA DRB MIMO test
cases
9.0.0 9.1.0
7.1.5.1: Inter-TTI PUSCH hopping by uplink
grant
9.0.0 9.1.0
7.1.5.3: Predefined intra-TTI PUSCH hopping
(N_sb=2/3/4)
9.0.0 9.1.0
7.1.5.5: Predefined inter-TTI PUSCH hopping
(N_sb=2/3/4)
9.0.0 9.1.0
2010-06 RAN#48 R5-103242 0799 - GCF Priority 1 - Clarification of the cells where
the messages are observed in EMM test cases
9.0.0 9.1.0
2010-06 RAN#48 R5-103246 0802 - Applicability of new TC 13.1.5 9.0.0 9.1.0
Radio link failure / T301 expiry
9.0.0 9.1.0
2010-06 RAN#48 R5-103272 0804 - GCF Priority 4 - Addition of new EPS mobility
management procedure test case 9.2.3.2.7
Combined tracking area update / Rejected /
EPS services and non-EPS services not
allowed
9.0.0 9.1.0
2010-06 RAN#48 R5-103273 0805 - GCF Priority 3 - Update Multi-layer test cases
13.3.1.1
9.0.0 9.1.0
2010-06 RAN#48 R5-103276 0806 - GCF Priority 2 - Correct the Test Purpose 2 of
PDCP part TC 7.3.1.2 and 7.3.1.3
9.0.0 9.1.0
2010-06 RAN#48 R5-103277 0807 - GCF Priority 1 - Correct PDCP part TC 7.3.1.1 9.0.0 9.1.0
management procedure test case 9.2.3.2.7

9.0.0 9.1.0
2010-06 RAN#48 R5-103302 0809 - GCF Priority 1: Correction to test case 7.1.3.9 9.0.0 9.1.0
2010-06 RAN#48 R5-103303 0810 - GCF Priority 1: Correction to E-UTRA MAC test
case 7.1.2.1
9.0.0 9.1.0
9.2.3.1.1
9.0.0 9.1.0
9.2.1.1.1
9.0.0 9.1.0
9.2.2.2.1
9.0.0 9.1.0
2010-06 RAN#48 R5-103313 0814 - GCF Priority 1: Correction to EUTRA MAC test
cases 7.1.7.1 test cases
9.0.0 9.1.0
2010-06 RAN#48 R5-103321 0815 - GCF Priority 2: Correction to EUTRA PDCP
test case 7.3.6.1
9.0.0 9.1.0
2010-06 RAN#48 R5-103323 0816 - GCF Priority 2: Correction to EUTRA RRC test
case 8.5.1.5
9.0.0 9.1.0
2010-06 RAN#48 R5-103327 0817 - GCF Priority 2: Correction to EPC test case
9.2.2.1.1
9.0.0 9.1.0
2010-06 RAN#48 R5-103341 0818 - GCF Priority 2: Adding UE pre-conditions for
UE to be configured for combined EPS/IMSI
9.0.0 9.1.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1160 Release 9
1160
attach in 9.2.3.2.x combined TAU test cases
2010-06 RAN#48 R5-103364 0819 - GCF Priority 2 - Correction to generic test
procedure reference in Idle mode section
9.0.0 9.1.0
2010-06 RAN#48 R5-103365 0820 - GCF Priority 2 - Correction to TC 8.1.3.7 RRC
connection release / Redirection from UTRAN
to E-UTRAN
9.0.0 9.1.0
2010-06 RAN#48 R5-103367 0821 - GCF Priority 3 - Correction to TC 8.5.2.1 RRC
Connection Reject / Redirection from UTRAN to
E-UTRAN
9.0.0 9.1.0
2010-06 RAN#48 R5-103394 0822 - GCF Priority 4 - New TC 9.3.1.18 Service
Reject CSG not authorized
9.0.0 9.1.0
8.4.3.2
9.0.0 9.1.0
8.4.3.3
9.0.0 9.1.0
2010-06 RAN#48 R5-103416 0825 - Priority 4 - Addition of test case 9.2.3.2.17 9.0.0 9.1.0
2010-06 RAN#48 R5-103418 0826 - Priority 4 - Addition of new test case 9.2.3.2.4 9.0.0 9.1.0
2010-06 RAN#48 R5-103421 0829 - Priority 3 - update of test case 9.2.2.2.14

9.0.0 9.1.0
2010-06 RAN#48 R5-103456 0830 - GCF Priority 4 - New TC 9.2.3.3.2 Iu mode to
S1 mode intersystem change / ISR is active /
Expiry of T3312 in E-UTRAN or T3412 in
UTRAN and further intersystem change
9.0.0 9.1.0
2010-06 RAN#48 R5-103457 0831 - GCF Priority 4 - New test case 6.1.2.10 Cell
reselection in shared network environment
9.0.0 9.1.0
2010-06 RAN#48 R5-103458 0832 - GCF Priority 4 - New Test case 6.1.2.12 Cell
reselection / Cell-specific reselection
parameters provided by the network in a
neighbouring cell list
9.0.0 9.1.0
2010-06 RAN#48 R5-103459 0833 - GCF Priority 4 - addition of new test case
6.1.1.4: PLMN selection in shared network
environment / Automatic mode
9.0.0 9.1.0
9.2.2.1.7
9.0.0 9.1.0
9.2.2.1.8
9.0.0 9.1.0
9.2.2.1.9
9.0.0 9.1.0
2010-06 RAN#48 R5-103486 0837 - GCF Priority 2 Correction to test case 6.1.2.3,
6.2.3.1 & 6.2.3.6
9.0.0 9.1.0
2010-06 RAN#48 R5-103498 0838 - GCF Priority 2 to 3 - Correction to RRC part 3
test cases
9.0.0 9.1.0
8.2.4.5
9.0.0 9.1.0
2010-06 RAN#48 R5-103514 0840 - GCF Priority 3 - New EMM test case 9.2.2.1.3 9.0.0 9.1.0
Discovery of the Home Agent address via
DHCPv6
9.0.0 9.1.0
2010-06 RAN#48 R5-103579 0842 - Addition of new DSMIPv6 test case for Security
association establishment with Home Agent
9.0.0 9.1.0
2010-06 RAN#48 R5-103646 0843 - GCF Priority 2 - Corrections to C2K TCs
8.3.2.7, 8.3.2.8 and 8.3.2.9
9.0.0 9.1.0
Discovery of the Home Agent address via
IKEv2 during tunnel setup to ePDG
9.0.0 9.1.0
2010-06 RAN#48 R5-103676 0845 - GCF Priority 4 - Addition of test case 8.2.4.10
RRC Connection Reconfiguration / Handover
(between FDD and TDD)
9.0.0 9.1.0
2010-06 RAN#48 R5-103696 0846 - GCF Priority 1 - Correction to MAC, RRC and
EMM test cases to bring the UE to stable state
at the end of test
9.0.0 9.1.0
2010-06 RAN#48 R5-103697 0847 - GCF Priority 1: Correction to EUTRA MAC test
case 7.1.4.8
9.0.0 9.1.0
2010-06 RAN#48 R5-103800 0880 1 GCF Priority 1: Correction to EUTRA RLC test
case 7.2.3.6
9.0.0 9.1.0
2010-06 RAN#48 R5-103801 0881 1 GCF Priority 1: Correction to EUTRA RLC test
case 7.2.3.7
9.0.0 9.1.0
2010-06 RAN#48 R5-103802 0849 - GCF Priority 1 - Update of RRC test cases
8.2.2.1
9.0.0 9.1.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1161 Release 9
1161
2010-06 RAN#48 R5-103803 0850 - GCF Priority 1: Correction to EUTRA RLC test
case 7.2.3.10
9.0.0 9.1.0
2010-06 RAN#48 R5-103804 0851 - GCF priority 2 - Correction to test case 6.1.1.1 9.0.0 9.1.0
case 7.2.2.8
9.0.0 9.1.0
case 7.2.2.10
9.0.0 9.1.0
case 7.2.3.13
9.0.0 9.1.0
2010-06 RAN#48 R5-103809 0856 - GCF Priority 2: Correction to EPC test case
9.1.3.2
9.0.0 9.1.0
UE to be configured for EPS attach in 9.2.1.1.x
EPS attach test cases
9.0.0 9.1.0
UE to be configured for EPS attach in 9.2.3.1.x
TAU test cases
9.0.0 9.1.0
UE to be configured for EPS attach in 9.2.2.x
detach test cases
9.0.0 9.1.0
UE to be configured for combined EPS/IMSI
attach in 9.2.1.2.x combined attach test cases
9.0.0 9.1.0
2010-06 RAN#48 R5-103816 0895 - Correction to MAC and RLC handover test
cases to set IE "statusReportRequired" to
FALSE
9.0.0 9.1.0
2010-06 RAN#48 R5-103817 0882 1 GCF Priority 2: Correction to EMM test case
9.2.3.1.2
9.0.0 9.1.0
2010-06 RAN#48 R5-103818 0861 - GCF Priority 2 - Correction to EPS test case
9.4.1
9.0.0 9.1.0
2010-06 RAN#48 R5-103819 0883 - GCF Priority 2 - Update of General tests part
TC 11.1.4
9.0.0 9.1.0
2010-06 RAN#48 R5-103820 0862 - GCF Priority 2 - Correction to 'SMS over SGs'
test case 11.1.1
9.0.0 9.1.0
test case 11.1.2
9.0.0 9.1.0
test case 11.1.3
9.0.0 9.1.0
2010-06 RAN#48 R5-103823 0894 - GCF priority 3 - New test case 6.2.1.2 Inter-
RAT PLMN Selection /Selection of correct RAT
for UPLMN/Automatic mode
9.0.0 9.1.0
2010-06 RAN#48 R5-103824 0884 1 GCF priority 3 - Inter-RAT PLMN Selection/
Selection of correct PLMN and RAT in shared
network environment, Automatic mode
9.0.0 9.1.0
2010-06 RAN#48 R5-103825 0885 1 GCF priority 4 - New test case 6.2.1.4 Inter-
RAT PLMN Selection/ Selection of correct RAT
from the OPLMN list/ Manual mode
9.0.0 9.1.0
2010-06 RAN#48 R5-103826 0886 - GCF priority 3 - New test case 6.2.1.1 Inter-
RAT PLMN Selection /Selection of correct RAT
for OPLMN/Automatic mode
9.0.0 9.1.0
2010-06 RAN#48 R5-103827 0887 - GCF Priority 3 - Update test case 8.2.4.8,
8.5.1.2 and 8.5.1.4
9.0.0 9.1.0
2010-06 RAN#48 R5-103829 0888 - GCF Priority 3 - Update RRC test case 8.3.1.4 9.0.0 9.1.0
2010-06 RAN#48 R5-103830 0866 - GCF Priority 3: New EMM test case, 9.2.1.1.23:
Attach / Abnormal case / Repeated rejects for
network failures
9.0.0 9.1.0
2010-06 RAN#48 R5-103831 0867 - GCF Priority 3: New TC 9.3.1.6 Service request
/ Rejected / EPS services not allowed
9.0.0 9.1.0
2010-06 RAN#48 R5-103832 0868 - Priority 3 - update of test case 9.2.1.1.24 9.0.0 9.1.0
2010-06 RAN#48 R5-103833 0889 1 GCF Priority 2 - Correction of EMM test case
9.1.2.3
9.0.0 9.1.0
13.1.5
9.0.0 9.1.0
2010-06 RAN#48 R5-103837 0889 - GCF Priority 3 - Update of Multilayer
Procedures part TC 13.3.1.2
9.0.0 9.1.0
2010-06 RAN#48 R5-103838 0870 - GCF Priority 3 - Update of Multilayer
Procedures part TC 13.1.3
9.0.0 9.1.0
RRC / Paging for connection in idle mode
/Multiple paging records
9.0.0 9.1.0
8.2.1.5
9.0.0 9.1.0
2010-06 RAN#48 R5-103841 0872 - GCF Priority 4 - Addition of new test case 9.0.0 9.1.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1162 Release 9
1162
8.2.1.6
2010-06 RAN#48 R5-103842 0873 - GCF Priority 4 - New TC 9.2.1.1.4 Attach
Procedure Success Request for obtaining the
IPv4 address of the home agent
9.0.0 9.1.0
2010-06 RAN#48 R5-103844 0892 1 GCF Priority 4 - New TC 13.1.8 Connected
CSFB to GSM with Redirection MO call
9.0.0 9.1.0
2010-06 RAN#48 R5-103848 0875 - GCF Priority 2 - Update RRC test case 8.2.4.6 9.0.0 9.1.0
2010-06 RAN#48 R5-103849 0876 - Addition of UE end state for 15 EMM test cases
and termination of ongoing signalling procedure
for 3 EMM test cases
9.0.0 9.1.0
7.1.4.5
9.0.0 9.1.0
2010-06 RAN#48 R5-103873 0878 - GCF Priority 4 - Addition of Multi-layer
Procedures part test case 13.1.7
9.0.0 9.1.0
9.2.3.2.2 for combined tracking area update /
successful for EPS services only / IMSI
unknown in HSS
9.0.0 9.1.0
2010-06 - - - - Typo correction of clause title 9.2.1.1.3.3 9.1.0 9.1.1
2010-09 RAN#49 GP-101502 0898 - CR 36.523-1-0898 New test case 6.2.3.14
Inter-RAT Cell Reselection / from
GSM_Idle/GPRS Packet_Idle to E-UTRA
(priority of E-UTRA cells are higher than the
serving cell)
9.1.1 9.2.0
2010-09 RAN#49 GP-101503 0899 - CR 36.523-1-0899 New test case 6.2.3.15
Inter-RAT Cell Reselection / from
GSM_Idle/GPRS Packet_Idle to E-UTRA
(priority of E-UTRA cells are lower than the
serving cell)
9.1.1 9.2.0
2010-09 RAN#49 GP-101510 0896 - CR 36.523-1-0896 6.2.3.19 : Redirection to E-
UTRA upon the release of the CS connection
9.1.1 9.2.0
2010-09 RAN#49 GP-101521 0897 - CR 36.523-1-0897 6.2.3.20: Redirection to E-
UTRA upon the release of the CS connection
and no suitable cell available
9.1.1 9.2.0
2010-09 RAN#49 GP-101562 0902 - CR 36.523-1-0902 New Test case 6.2.3.27-
Inter-RAT Cell selection from GPRS
Packet_transfer to E-UTRA Cell (NC2 mode).
9.1.1 9.2.0
2010-09 RAN#49 GP-101603 1016 - CR 36.523-1-1016 New Test Case 6.2.3.23 -
Inter-RAT Cell Reselection from GPRS Packet
transfer to E-UTRA in CCN mode (PACKET
CELL CHANGE CONTINUE)
9.1.1 9.2.0
2010-09 RAN#49 R5-104073 0903 - GCF Priority 2 - Corrections to EUTRA idle
mode test cases
9.1.1 9.2.0
2010-09 RAN#49 R5-104083 0904 - GCF Priority 2 - Review of detach at
switch/power off procedure in EMM test cases
9.1.1 9.2.0
2010-09 RAN#49 R5-104084 0905 - GCF Priority 2 - Review of switch/power off
procedure
9.1.1 9.2.0
2010-09 RAN#49 R5-104107 0906 - GCF Priority 1 - Correction to remove special
configurations for UM Bearer test cases
9.1.1 9.2.0
2010-09 RAN#49 R5-104130 0907 - GCF Priority 2 - Correction to EUTRA RRC test
case 8.1.2.7
9.1.1 9.2.0
2010-09 RAN#49 R5-104136 0908 - GCF Priority 2 - Correction to Generic E-UTRA
radio bearer test procedure 12.1.1 and 12.1.2
9.1.1 9.2.0
2010-09 RAN#49 R5-104142 0909 - GCF Priority 2 - Correction to EMM test case
9.2.3.1.2
9.1.1 9.2.0
7.1.2.8
9.1.1 9.2.0
case 8.1.2.5
9.1.1 9.2.0
2010-09 RAN#49 R5-104147 0912 - GCF Priority 2 - Correction to EUTRA MAC test
case 7.1.4.3
9.1.1 9.2.0
2010-09 RAN#49 R5-104148 0913 - GCF Priority 1 - Correction to EUTRA RLC test
case 7.2.3.1
9.1.1 9.2.0
case 7.1.2.6
9.1.1 9.2.0
case 7.1.3.1
9.1.1 9.2.0
case 7.1.3.6
9.1.1 9.2.0
case 7.1.4.11
9.1.1 9.2.0
2010-09 RAN#49 R5-104168 0919 - GCF Priority 2 - Correction of ESM test case
10.8.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104173 0920 - GCF Priority 4 - Addition of new test case 9.1.1 9.2.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1163 Release 9
1163
6.1.2.14
9.2.3.2.5
9.1.1 9.2.0
2010-09 RAN#49 R5-104238 0923 - GCF Priority 2 - Correction of EMM test case
9.2.1.1.17
9.1.1 9.2.0
2010-09 RAN#49 R5-104265 0924 - GCF Priority 2 - Update of TC 8.1.2.5 9.1.1 9.2.0
2010-09 RAN#49 R5-104283 0925 - GCF Priority 4 Update test case 8.3.2.5 9.1.1 9.2.0
2010-09 RAN#49 R5-104286 0926 - GCF Priority 4 - Correction of test cases 14.1 &
14.2
9.1.1 9.2.0
2010-09 RAN#49 R5-104287 0927 - GCF Priority 4 - Addition of new test case 14.3 9.1.1 9.2.0
2010-09 RAN#49 R5-104389 0928 - Update of DSMIPv6 test cases 9.1.1 9.2.0
2010-09 RAN#49 R5-104390 0929 - Removal of DSMIPv6 test case 15.3 9.1.1 9.2.0
2010-09 RAN#49 R5-104512 0931 - GCF Priority 2 - Update to EMM test case
9.2.2.1.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104632 0933 - GCF Priority 1 - Correction of RRC test case
8.5.4.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104637 0934 - GCF priority 4 - Addition of new test case
8.2.4.12
9.1.1 9.2.0
cases 7.1.7.1.1, 7.1.7.1.2, 7.1.7.1.3, 7.1.7.1.4
9.1.1 9.2.0
case 7.1.7.2.1
9.1.1 9.2.0
case 7.1.3.4
9.1.1 9.2.0
case 7.1.3.9
9.1.1 9.2.0
2010-09 RAN#49 R5-104712 0939 - GCF Priority 1 - Correction to GCF WI-081 LTE
Testcases 7.1.4.11, 7.1.4.14
9.1.1 9.2.0
2010-09 RAN#49 R5-104713 0940 - GCF Priority 2 - Correction to ETURA RRC test
case 8.2.4.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104714 0941 - Correction to GCF WI-082 EMM Testcase
9.1.2.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104715 0942 - GCF Priority 2 - Corrections to EUTRA GERAN
idle mode test cases
9.1.1 9.2.0
2010-09 RAN#49 R5-104716 0943 - GCF Priority 2 - Corrections to idle mode test
case 6.2.2.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104717 0944 - GCF Priority 2 - Review of detach at
switch/power off procedure in Idle Mode test
cases
9.1.1 9.2.0
2010-09 RAN#49 R5-104718 0945 - GCF Priority 2 - Correction to Inter RAT HRPD
test case 6.2.2.3
9.1.1 9.2.0
test case 6.2.3.7
9.1.1 9.2.0
test case 6.2.3.8
9.1.1 9.2.0
6.2.3.4
9.1.1 9.2.0
2010-09 RAN#49 R5-104722 0949 - Addition of modified value tag after System
Information modification
9.1.1 9.2.0
case 7.2.3.21
9.1.1 9.2.0
2010-09 RAN#49 R5-104724 0951 - GCF Priority 2 - Correction to GCF Priority 2
Inter RAT HRPD test case 8.1.3.9
9.1.1 9.2.0
9.2.1.1.9 and 9.2.1.1.10
9.1.1 9.2.0
9.2.1.1.20
9.1.1 9.2.0
2010-09 RAN#49 R5-104730 0955 - GCF Priority 2 - update of test case 9.2.3.1.8 9.1.1 9.2.0
9.2.1.2.1
9.1.1 9.2.0
9.2.1.1.1a about reference cell information
9.1.1 9.2.0
10.6.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104734 0959 - GCF Priority 2 - Correction to ESM test case
10.5.1
9.1.1 9.2.0
10.4.1
9.1.1 9.2.0
2010-09 RAN#49 R5-104736 0961 - Add test case for RRC connection
establishment of emergency call
9.1.1 9.2.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1164 Release 9
1164
2010-09 RAN#49 R5-104744 0964 - GCF priority 3: Correction to MAC TBS (MIMO
configured) test case 7.1.7.1.5
9.1.1 9.2.0
2010-09 RAN#49 R5-104745 0965 - GCF priority 3: Correction to MAC TBS (MIMO
configured) test case 7.1.7.1.6
9.1.1 9.2.0
management procedure test case 9.3.2.2a
Paging for CS fallback / Connected mode
9.1.1 9.2.0
10.5.3
9.1.1 9.2.0
2010-09 RAN#49 R5-104751 0971 - GFC Prirotity 3 and 4: Correction of generic test
procedure used in MIMO DRB test cases
9.1.1 9.2.0
2010-09 RAN#49 R5-104752 0972 - GCF Priority 3 - Addition of new Multilayer
Procedures test case 13.1.4 Call setup from E-
UTRAN RRC_IDLE / CS fallback to UTRAN
with Handover / MT call
9.1.1 9.2.0
2010-09 RAN#49 R5-104753 0973 - Addition of new LTE test case 13.1.2 CS
fallback UTRAN with redirection / MO call
9.1.1 9.2.0
2010-09 RAN#49 R5-104754 0974 - GCF Priority 3 - Addition of New TC for cell
reselection when 1xRTT is higher priority
9.1.1 9.2.0
2010-09 RAN#49 R5-104755 0975 - GCF Priority 3 - Addition of New TC for cell
reselection when 1xRTT is lower priority
9.1.1 9.2.0
6.1.1.6
9.1.1 9.2.0
8.1.2.6
9.1.1 9.2.0
2010-09 RAN#49 R5-104765 0985 - GCF Priority 2 - Correction to EUTRA RRC
Test Case 8.2.4.7
9.1.1 9.2.0
9.2.1.1.3
9.1.1 9.2.0
9.2.3.2.11
9.1.1 9.2.0
9.3.1.12a
9.1.1 9.2.0
2010-09 RAN#49 R5-104773 0990 - GCF Priority X: Addition of New TC for Inter-
RAT Cell reselection from E-UTRA idle non-
CSG cell to a UTRA CSG cell
9.1.1 9.2.0
2010-09 RAN#49 R5-104774 0991 - GCF Priority X: Addition of New TC for Inter-
RAT CSG Cell Reselection from E-UTRA CSG
cell to UTRA CSG cell
9.1.1 9.2.0
2010-09 RAN#49 R5-104776 0992 - GCF Priority X: Introduction of new ESM test
case 10.9.1 for UE routing of uplinks packets
9.1.1 9.2.0
2010-09 RAN#49 R5-104777 0993 - GCF priority 2 - Cell detection timing related
correction to test case 6.1.2.3
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1165 Release 9
1165
9.1.1 9.2.0
9.1.1 9.2.0
9.1.1 9.2.0
2010-09 RAN#49 R5-104792 1008 - GCF Priority 2 - Correction to EUTRA Idle
mode test case 6.1.2.6
9.1.1 9.2.0
case 8.1.2.2
9.1.1 9.2.0
2010-09 RAN#49 R5-104794 1010 - GCF Priority 2 - Correction to EUTRA PDCP
test cases 7.3.5.2, 7.3.5.3, 7.3.5.4, 7.3.5.5
9.1.1 9.2.0
2010-09 RAN#49 R5-104795 1011 - Correction to Generic E-UTRA radio bearer test
procedure
9.1.1 9.2.0
2010-09 RAN#49 R5-104797 1012 - GCF Priority 2 - Update test cases in clause
8.5.1
9.1.1 9.2.0
7.1.4.3
9.1.1 9.2.0
2010-09 RAN#49 R5-105000 1014 - GCF Priority 3 - New TC 6.3.3 Inter-RAT cell
reselection / From UTRA_Idle to E-UTRA
RRC_IDLE CSG cell
9.1.1 9.2.0
2010-09 RAN#49 R5-105001 1015 - GCF Priority 1 - Correction to GCF Priority 1
MAC test cases for AP#47.05
9.1.1 9.2.0
2010-09 RAN#49 R5-105002 1017 - GCF Priority 1 - Correction of new test cases in
8.3.3
9.1.1 9.2.0
2010-09 RAN#49 R5-105005 1019 - 36523-1: Update of attach procedure
specification
9.1.1 9.2.0
2010-09 RAN#49 R5-105007 1021 - GCF Priority 1 - Correction of EUTRA MAC test
case 7.1.4.5
9.1.1 9.2.0
2010-09 RAN#49 R5-105009 1022 - GCF Priority 2 - Correction of EUTRA test case
8.5.1.3
9.1.1 9.2.0
2010-09 RAN#49 R5-105010 1023 - GCF Priority 2 - Correction to ETURA RRC test
case 8.5.1.1
9.1.1 9.2.0
2010-09 RAN#49 R5-105011 1024 - GCF Priority 2 - Correction of EUTRA test case
8.3.1.3
9.1.1 9.2.0
10.7.2
9.1.1 9.2.0
2010-09 RAN#49 R5-105016 1029 - GCF Priority 1+2: Correction to RLC test cases
for AP#47.05
9.1.1 9.2.0
case 7.2.3.18
9.1.1 9.2.0
2010-09 RAN#49 R5-105070 1026 - Harmonising EMM test case pre-test conditions
specification
9.1.1 9.2.0
2010-09 RAN#49 R5-105071 1030 - GCF Priority x - Correction to 36.523-1 Test
Case 8.3.1.5
9.1.1 9.2.0
10.3.1
9.2.0 9.3.0
8.2.2.2
9.2.0 9.3.0
9.2.3.1.1
9.2.0 9.3.0
10.4.1
9.2.0 9.3.0
9.2.3.1.2
9.2.0 9.3.0
10.7.2
9.2.0 9.3.0
9.2.3.1.13
9.2.0 9.3.0
2010-12 RAN#50 R5-106160 1034 - GCF Priority 1 - Correction to TC 9.2.3.1.5 9.2.0 9.3.0
2010-12 RAN#50 R5-106177 1036 - GCF Priority 2 - Correction of test cases in
6.2.3.4
9.2.0 9.3.0
8.3.2.1, 8.3.2.3, 8.3.2.5 and 8.3.2.6
9.2.0 9.3.0
8.3.3
9.2.0 9.3.0
9.2.1.2.2
9.2.0 9.3.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1166 Release 9
1166
9.2.2.1.7
9.2.0 9.3.0
9.2.2.2.1
9.2.0 9.3.0
9.2.3.2.2.
9.2.0 9.3.0
9.3.1.17
9.2.0 9.3.0
2010-12 RAN#50 R5-106204 1044 - GCF Priority 1 - Corrections to test case 7.1.4.1 9.2.0 9.3.0
2010-12 RAN#50 R5-106214 1045 - GCF Priority 2 - Correction to EMM test cases
9.2.1.1.13, 9.2.1.1.15 and 9.2.1.1.17
9.2.0 9.3.0
9.2.1.1.7
9.2.0 9.3.0
9.2.1.2.1
9.2.0 9.3.0
9.2.1.2.4
9.2.0 9.3.0
9.2.3.1.4
9.2.0 9.3.0
2010-12 RAN#50 R5-106268 1050 - GCF Priority 4 - Editorial correction to test case
6.1.1.6
9.2.0 9.3.0
2010-12 RAN#50 R5-106280 1056 - GCF Priority 3 - Update to test case 9.2.1.2.15
and 9.3.1.12a
9.2.0 9.3.0
2010-12 RAN#50 R5-106284 1057 - GCF Priority 3 - Update to test cases 10.8.2,
10.8.4 and 10.8.6
9.2.0 9.3.0
2010-12 RAN#50 R5-106294 1058 - CR to 36.523-1: Correction to UTRA cell
minimum power level
9.2.0 9.3.0
2010-12 RAN#50 R5-106326 1059 - GCF Priority 3 - Corrections to ESM test case
10.6.2
9.2.0 9.3.0
2010-12 RAN#50 R5-106333 1060 - GCF Priority 2 - Corrections to RRC test case
8.2.4.6
9.2.0 9.3.0
2010-12 RAN#50 R5-106335 1061 - GCF Priority 1-4 - Editorial corrections to
EUTRA RRC test cases
9.2.0 9.3.0
2010-12 RAN#50 R5-106336 1062 - GCF Priority 1-4 - Editorial corrections to EMM
test cases
9.2.0 9.3.0
2010-12 RAN#50 R5-106524 1063 - Update test case 8.1.2.11 with IMS emergency
session setup
9.2.0 9.3.0
2010-12 RAN#50 R5-106525 1064 - Update references with IMS 9.2.0 9.3.0
6.1.2
9.2.0 9.3.0
case 7.1.2.8
9.2.0 9.3.0
case 7.1.4.12
9.2.0 9.3.0
case 7.1.4.13
9.2.0 9.3.0
2010-12 RAN#50 R5-106559 1069 - GCF Priority 2 - Making compressed mode
configuration optional for FDD and removal of
compressed mode requirement for TDD for
InterRAT HO test cases 8.4.2.2
9.2.0 9.3.0
2010-12 RAN#50 R5-106560 1070 - GCF Priority 2 - Making compressed mode
configuration optional for FDD and removal of
InterRAT HO test cases 8.4.2.4
9.2.0 9.3.0
7.1.4.13
9.2.0 9.3.0
2010-12 RAN#50 R5-106564 1072 - Resolve timing issue in P1 RLC TCs 9.2.0 9.3.0
2010-12 RAN#50 R5-106566 1074 - GCF Priority 1 - Update of Radio Bearer test
procedure used by TC 12.2.1
9.2.0 9.3.0
2010-12 RAN#50 R5-106567 1075 - GCF Priority 2 - Correction to Idle mode test
case 6.1.2.7
9.2.0 9.3.0
6.1.2.8 and 6.1.2.9
9.2.0 9.3.0
6.2.2.1 and 6.2.2.2
9.2.0 9.3.0
case 8.1.3.5
9.2.0 9.3.0
8.3.1.8 ~8.3.1.11
9.2.0 9.3.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1167 Release 9
1167
2010-12 RAN#50 R5-106573 1080 - GCF Priority 2 - Update to test case 8.4.2.2 and
8.4.2.4
9.2.0 9.3.0
2010-12 RAN#50 R5-106574 1081 - GCF Priority 2 - Correction to contents for
message Extended Service Request
9.2.0 9.3.0
9.1.2.3
9.2.0 9.3.0
2010-12 RAN#50 R5-106595 1083 - Add test case for RRC connection
establishment of emergency call / Limited
Service
9.2.0 9.3.0
case 8.2.4.1
9.2.0 9.3.0
9.2.2.2.2
9.2.0 9.3.0
9.2.3.2.1
9.2.0 9.3.0
2010-12 RAN#50 R5-106602 1087 - GCF Priority 3 - Corrections to test case 7.1.5.1
and 7.1.5.2
9.2.0 9.3.0
2010-12 RAN#50 R5-106603 1088 - GCF Priority 3 - Addition new test case 6.1.2.13 9.2.0 9.3.0
9.2.1.1.1a
9.2.0 9.3.0
2010-12 RAN#50 R5-106605 1090 - GCF Priority 3 - Various corrections to EMM
section 9 of 36.523-1
9.2.0 9.3.0
2010-12 RAN#50 R5-106607 1092 - GCF Priority 3: Correction to multi-layer test
cases 13.1.4 and 13.1.5
9.2.0 9.3.0
2010-12 RAN#50 R5-106619 1094 - GCF Priority 1 - Correction to TC 7.3.3.1,
7.3.3.2, 7.3.3.3 and 7.3.3.4
9.2.0 9.3.0
8.3.1.6
9.2.0 9.3.0
2010-12 RAN#50 R5-106623 1097 - GCF Priority 4 - Update to test case 9.2.3.2.5,
9.2.3.2.11, and 9.3.1.12a
9.2.0 9.3.0
2010-12 RAN#50 R5-106624 1098 - 9.2.1.3.3 Attach GCF Priority 4 -
Addition of new test case 9.2.3.2.13
9.2.0 9.3.0
2010-12 RAN#50 R5-106625 1099 - GCF Priority 4: Addition of a new test case
9.2.3.2.1b
9.2.0 9.3.0
2010-12 RAN#50 R5-106626 1100 - Addition of system information combination in
Idle Mode test cases
9.2.0 9.3.0
EMM test cases
9.2.0 9.3.0
RRC test cases
9.2.0 9.3.0
Multilayer test cases
9.2.0 9.3.0
2010-12 RAN#50 R5-106630 1104 - Clarification of measurements requirements for
Inter-RAT
9.2.0 9.3.0
2010-12 RAN#50 R5-106631 1105 - GCF Priority X - Addition new test case
6.2.3.31
9.2.0 9.3.0
2010-12 RAN#50 R5-106632 1106 - GCF Priority 1 Correction to EUTRA MAC
test case 7.1.4.8
9.2.0 9.3.0
2010-12 RAN#50 R5-106635 1107 - GCF Priority TBD - Addition of new idle mode
test case for inter-freq cell reselection based on
CSG autonomous search
9.2.0 9.3.0
2010-12 RAN#50 R5-106636 1108 - GCF Priority TBD - Correction to TC 16.1.1.1
Inter-RAT Cell reselection from E-UTRA idle
non-CSG cell to a UTRA CSG cell
9.2.0 9.3.0
2010-12 RAN#50 R5-106637 1109 - GCF Priority TBD - Movement of TC 16.1.1.2 to
section 6.3.8
9.2.0 9.3.0
2010-12 RAN#50 R5-106638 1110 - GCF Priority 4 - Addition of new TC 6.3.4 Inter-
RAT cell reselection / From UTRA CELL_PCH
state to E-UTRA RRC_IDLE CSG cell
9.2.0 9.3.0

2010-12 RAN#50 R5-106641 1112 - GCF Pririty 4 -Making measurement and
reporting optional for FDD and removal
Redirection test cases 8.1.3.7
9.2.0 9.3.0
2010-12 RAN#50 R5-106642 1113 - Periodic RI Reporting using PUCCH / Category
1 UE / Transmission mode 3/4
9.2.0 9.3.0
2010-12 RAN#50 R5-106647 1116 - GCF Priority X - Addition of new test case
13.1.X
9.2.0 9.3.0
2010-12 RAN#50 R5-106655 1117 - GCF Priority 4 - New test case 6.1.1.2 PLMN
selection of 'Other PLMN/access technology
combinations' / Automatic mode
9.2.0 9.3.0

3GPP
3GPP TS 36.523-1 V9.3.0 (2010-12) 1168 Release 9
1168
2010-12 RAN#50 R5-106659 1120 - GCF Priority 1 - Corrections and enhancements
to EUTRA PDCP test cases 7.3.3.1, 7.3.3.3,
7.3.4.1 and 7.3.4.2
9.2.0 9.3.0
2010-12 RAN#50 R5-106661 1122 - GCF Priority 2 - Corrections to E-UTRA RRC
test case 8.1.2.7
9.2.0 9.3.0
2010-12 RAN#50 R5-106662 1123 - GCF Priority 4: Addition of a new test case
9.2.1.2.1b
9.2.0 9.3.0
case 7.1.4.16
9.2.0 9.3.0
various ESM test cases
9.2.0 9.3.0
EUTRA Idle Mode test cases
9.2.0 9.3.0
2010-12 RAN#50 R5-106679 1127 - GCF Priority 2 - Corrections to E-UTRA PDCP
test case 7.3.5.5
9.2.0 9.3.0
2010-12 RAN#50 R5-106680 1128 - GCF Priority 2 Correction to EUTRA RLC test
case 7.2.3.16
9.2.0 9.3.0
2010-12 RAN#50 R5-106681 1129 - GCF Priority 2 - Update to test case 9.2.3.3.1
and 9.2.3.3.4
9.2.0 9.3.0
2010-12 RAN#50 R5-106707 1131 - GCF priority X: New test case 9.2.3.2.1c
Combined tracking area update / Success / CS
Fallback not preferred
9.2.0 9.3.0
2010-12 RAN#50 R5-106875 1114 - GCF Priority X - Addition of new test case
8.1.2.10
9.2.0 9.3.0
2010-12 RAN#50 R5-106876 1118 - Cell detection timing related correction to test
case 6.2.2.3, 6.2.2.4, 6.2.3.7 and 6.2.3.8
9.2.0 9.3.0
2010-12 RAN#50 R5-106877 1115 - GCF priority X: New test case 9.2.1.2.1c
and CS Fallback not preferred
9.2.0 9.3.0
2010-12 RAN#50 RP-101255 1132 - GCF Priority 2 - Correction to EUTRA RLC test
case 7.2.3.21
9.2.0 9.3.0

3GPP TS 36.523-1: Technical Specification

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

3GPP TS 36.523-1: Technical Specification

Diunggah oleh

Hak Cipta:

Format Tersedia

3GPP TS 36.523-1 V9.3.

upper layers that the CS fallback or 1xCS fallback procedure has

Anda mungkin juga menyukai