Lte Parametros

ETSI TS 138 523-1 V16.9.
0 (2021-12)
TECHNICAL SPECIFICATION
5G;
LTE;
5GS;
User Equipment (UE) conformance specification;
Part 1: Protocol
(3GPP TS 38.523-1 version 16.9.0 Release 16)
3GPP TS 38.523-1 version 16.9.0 Release 16 1 ETSI TS 138 523-1 V16.9.0 (2021-12)
Reference
RTS/TSGR-0538523-1vg90
Keywords
5G,LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B

Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Notice of disclaimer & limitation of liability

The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2021.
All rights reserved.
ETSI
Intellectual Property Rights

Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
oneM2M Partners. GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
Legal notice
This Technical Specification (TS) has been produced by the ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
Contents
Intellectual Property Rights ................................................................................................................................2
Legal notice ........................................................................................................................................................2
Modal verbs terminology....................................................................................................................................2
Foreword...........................................................................................................................................................20
1 Scope ......................................................................................................................................................22
2 References ..............................................................................................................................................22
3 Definitions, symbols and abbreviations .................................................................................................24
3.1 Definitions ........................................................................................................................................................ 24
3.2 Symbols ............................................................................................................................................................ 24
3.3 Abbreviations ................................................................................................................................................... 24
4 Overview ................................................................................................................................................24
4.1 Test methodology ............................................................................................................................................. 24
4.1.1 Testing of optional functions and procedures ............................................................................................. 24
4.1.2 Test interfaces and facilities........................................................................................................................ 25
4.2 Implicit testing.................................................................................................................................................. 25
4.3 Repetition of tests ............................................................................................................................................. 25
4.4 Handling of differences between conformance requirements in different releases of core specifications ....... 25
5 Reference conditions, generic and test procedures, test parameters.......................................................26
5.1 Reference conditions ........................................................................................................................................ 26
5.2 Generic and test procedures.............................................................................................................................. 26
5.3 Test parameters ................................................................................................................................................ 26
5.3.1 PLMNs........................................................................................................................................................ 26
5.3.2 Cells ............................................................................................................................................................ 26
5.3.3 USIM .......................................................................................................................................................... 27
5.3.4 Messages and Information Elements (IEs) ................................................................................................. 27
6 Idle mode and RRC Inactive state operations ........................................................................................27
6.1 NR idle mode operations .................................................................................................................................. 27
6.1.1 NG-RAN Only PLMN Selection ................................................................................................................ 27
6.1.1.1 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode ............. 27
6.1.1.2 PLMN selection of "Other PLMN/access technology combinations" / Automatic mode ..................... 36
6.1.1.3 Cell reselection of ePLMN in manual mode ......................................................................................... 42
6.1.1.4 PLMN selection in shared network environment / Automatic mode .................................................... 46
6.1.1.5 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
User reselection): .................................................................................................................................. 52
6.1.1.6 PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer ............................................. 58
6.1.1.7 PLMN selection of RPLMN or (E)HPLMN; Automatic mode ............................................................ 63
6.1.1.8 PLMN selection of RPLMN or (E)HPLMN; Manual mode ................................................................. 66
6.1.2 NG-RAN Only Cell Selection .................................................................................................................... 69
6.1.2.1 Cell selection / Qrxlevmin & Cell reselection (Intra NR) ..................................................................... 69
6.1.2.2 Cell selection / Qqualmin / Intra NR / Serving cell becomes non-suitable (Srxlev > 0, Squal < 0)...... 79
6.1.2.3 Cell selection / Intra NR / Serving cell becomes non-suitable (S<0, MIB Indicated barred)................ 89
6.1.2.4 Cell reselection for interband operation ................................................................................................ 94
6.1.2.5 Cell reselection for interband operation using Pcompensation / Between FDD and TDD ................... 98
6.1.2.6 Void..................................................................................................................................................... 102
6.1.2.7 Cell reselection / Equivalent PLMN ................................................................................................... 102
6.1.2.8 Cell reselection / Equivalent PLMN / Single Frequency operation .................................................... 107
6.1.2.9 Cell reselection using Qhyst, Qoffset and Treselection ...................................................................... 110
6.1.2.10 Void..................................................................................................................................................... 119
6.1.2.11 Area Specific SIBs using systemInformationAreaID.......................................................................... 119
6.1.2.12 Cell reselection using cell status and cell reservations / cellReservedForOtherUse ........................... 125
6.1.2.13 Cell reselection using cell status and cell reservations / Access Identity 0, 1, 2 and 12 to 14 –
cellReservedForOperatorUse .............................................................................................................. 129
ETSI
6.1.2.14 Cell reselection using cell status and cell reservations / Access Identity 11 or 15 -
cellReservedForOperatorUse .............................................................................................................. 131
6.1.2.15 Cell reselection in shared network environment ................................................................................. 134
6.1.2.16 Inter-frequency cell reselection (equal priority) .................................................................................. 138
6.1.2.17 Cell reselection / Cell-specific reselection parameters provided by the network in a neighbouring
cell list ................................................................................................................................................. 140
6.1.2.18 Cell reselection, Sintrasearch, Snonintrasearch................................................................................... 142
6.1.2.19 Speed-dependent cell reselection ........................................................................................................ 149
6.1.2.20 Inter-frequency cell reselection according to cell reselection priority provided by SIBs .................... 156
6.1.2.21 Cell reselection, SIntraSearchQ and SnonIntraSearchQ ..................................................................... 161
6.1.2.22 Inter-frequency cell reselection based on common priority information with parameters ThreshX,
HighQ, ThreshX, LowQ and ThreshServing, LowQ .......................................................................... 171
6.1.2.23 Cell reselection / MFBI ....................................................................................................................... 180
6.2 Multi-mode environment ................................................................................................................................ 188
6.2.1 Inter-RAT PLMN selection ...................................................................................................................... 188
6.2.1.1 Inter-RAT PLMN Selection / Selection of correct RAT for OPLMN / Automatic mode ................... 188
6.2.1.2 Inter-RAT PLMN Selection / Selection of correct RAT for UPLMN / Automatic mode ................... 190
6.2.1.3 Inter-RAT PLMN Selection / Selection of correct PLMN and RAT in shared network
environment / Automatic mode ........................................................................................................... 193
6.2.1.4 Inter-RAT PLMN Selection / Selection of correct RAT from the OPLMN list / Manual mode......... 197
6.2.1.5 Inter-RAT Background HPLMN Search / Search for correct RAT for HPLMN / Automatic
Mode ................................................................................................................................................... 200
6.2.2 Inter-RAT Cell Selection .......................................................................................................................... 205
6.2.2.1 Inter-RAT cell selection / From NR RRC_IDLE to EUTRA_Idle / Serving cell becomes non-
suitable ................................................................................................................................................ 205
6.2.2.2 Inter-RAT cell selection / From E-UTRA_Idle to NR RRC_IDLE / Serving cell becomes non-
suitable ................................................................................................................................................ 212
6.2.3 Inter-RAT Cell Reselection ...................................................................................................................... 220
6.2.3.1 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE (lower priority & higher
priority, Srxlev based) ......................................................................................................................... 220
6.2.3.2 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE (lower priority & higher
priority, Squal based) .......................................................................................................................... 229
6.2.3.3 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE (lower priority & higher
priority, Srxlev based) ......................................................................................................................... 237
6.2.3.4 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE (lower priority & higher
priority, Squal based) .......................................................................................................................... 244
6.2.3.5 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE according to RAT priority
provided by dedicated signalling (RRCRelease) ................................................................................. 252
6.2.3.6 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE according to RAT priority
provided by dedicated signalling (RRConnRelease) ........................................................................... 260
6.2.3.7 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA RRC_IDLE, Snonintrasearch.......... 267
6.2.3.8 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to NR RRC_IDLE, Snonintrasearch ......... 271
6.2.3.9 Void..................................................................................................................................................... 277
6.2.3.10 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE / schedulingInfoList-v12j0... 277
6.2.3.11 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE / schedulingInfoListExt-
r12 ....................................................................................................................................................... 286
6.3 5GS Steering of Roaming............................................................................................................................... 294
6.3.1 Steering of Roaming ................................................................................................................................. 294
6.3.1.1 Steering of UE in roaming during registration/security check successful using List Type 1 .............. 294
6.3.1.2 Steering of UE in roaming during registration/security check successful but SOR Transparent
container indicates ACK has been NOT been requested ..................................................................... 302
6.3.1.3 Steering of UE in roaming during registration/security check unsuccessful/Automatic mode ........... 310
6.3.1.4 Steering of UE in roaming during registration/security check unsuccessful/Manual mode ................ 316
6.3.1.5 Steering of UE in roaming during registration/UE configured to receive Steering of Roaming
information but does not receive Steering of Roaming from Network ............................................... 321
6.3.1.6 Void..................................................................................................................................................... 327
6.3.1.7 Steering of UE in roaming during registration/security check unsuccessful but emergency service
pending to be activated........................................................................................................................ 327
6.3.1.8 Steering of UE in roaming after registration/Automatic PLMN selection mode ................................ 333
6.3.1.9 Steering of UE in roaming after registration/Manual PLMN selection mode ..................................... 337
6.3.1.10 Steering of UE in roaming during mobility update registration .......................................................... 340
6.4 UE Procedures in RRC_INACTIVE state ...................................................................................................... 345
ETSI
6.4.1 NG-RAN Only PLMN Selection in RRC_INACTIVE state .................................................................... 345

6.4.1.1 PLMN Selection/Higher priority/HPLMN in Automatic PLMN Selection Mode .............................. 345
6.4.1.2 Cell reselection of ePLMN in manual mode ....................................................................................... 354
6.4.2 Cell Selection/Qrxlevmin & Cell Reselection (Intra NR in RRC_INACTIVE state)............................... 361
6.4.2.1 Cell Selection/Qrxlevmin & Cell Reselection (Intra NR in RRC_INACTIVE state) ......................... 361
6.4.2.2 Inter-frequency cell reselection according to cell reselection priority provided by SIBs in
RRC_INACTIVE state........................................................................................................................ 369
6.4.3 Inter-RAT Cell Reselection ...................................................................................................................... 374
6.4.3.1 Inter-RAT cell reselection From NR RRC_INACTIVE to E-UTRA RRC_IDLE (lower priority
& higher priority, Srxlev based).......................................................................................................... 374
6.5 SNPN and CAG Selection .............................................................................................................................. 381
6.5.1 SNPN Only Selection ............................................................................................................................... 381
6.5.1.1 SNPN Selection in Manual Mode ....................................................................................................... 381
6.5.1.2 SNPN Selection in Automatic Mode................................................................................................... 384
6.5.2 CAG (Closed Access Group) .................................................................................................................... 387
6.5.2.1 CAG Selection in Manual Mode ......................................................................................................... 387
6.5.2.2 CAG Selection in Automatic Mode .................................................................................................... 392
7 Layer 2..................................................................................................................................................398
7.1 NR Layer 2 ..................................................................................................................................................... 398
7.1.0 Common test case specific values for Layer 2 .......................................................................................... 398
7.1.1 MAC ......................................................................................................................................................... 398
7.1.1.0 Default Pre-Test Conditions for all MAC test cases ........................................................................... 398
7.1.1.1 Random Access Procedures ................................................................................................................ 400
7.1.1.1.1 Correct selection of RACH parameters / Random access preamble and PRACH resource
explicitly signalled to the UE by RRC / contention free random access procedure ...................... 400
7.1.1.1.1a Correct selection of RACH parameters / Random access preamble and PRACH resource
explicitly signalled to the UE by PDCCH Order / contention free random access procedure ....... 407
7.1.1.1.2 Random access procedure / Successful / C-RNTI Based / Preamble selected by MAC itself....... 414
7.1.1.1.3 Random access procedure / Successful / SI request ...................................................................... 430
7.1.1.1.4 Random access procedure / Successful / Beam Failure / Preamble selected by MAC itself /
Non Contention Free RACH procedure ........................................................................................ 440
7.1.1.1.5 Random access procedure / Successful / Supplementary Uplink .................................................. 456
7.1.1.1.6 Random access procedure / Successful/ Temporary C-RNTI Based / Preamble selected by
MAC itself ..................................................................................................................................... 461
7.1.1.1.7 Random access procedure / Successful/ Temporary C-RNTI Based / Preamble selected by
MAC itself ..................................................................................................................................... 474
7.1.1.1.8 Correct selection of RACH parameters / 2-step RACH/MSGA and PRACH resource
explicitly signalled to the UE by RRC / contention free random access procedure ...................... 480
7.1.1.1.9 Random access procedure / Successful / 2-step RACH/C-RNTI Based / Preamble selected by
MAC itself ..................................................................................................................................... 486
7.1.1.1.10 Random access procedure / 2-step RACH/not complete/ RA_TYPE to 4-stepRA ....................... 501
7.1.1.2 Downlink Data Transfer ...................................................................................................................... 505
7.1.1.2.1 Correct Handling of DL MAC PDU / Assignment / HARQ process ............................................ 505
7.1.1.2.2 Correct Handling of DL HARQ process PDSCH Aggregation ..................................................... 516
7.1.1.2.3 Correct HARQ process handling / CCCH ..................................................................................... 522
7.1.1.2.4 Correct HARQ process handling / BCCH ..................................................................................... 527
7.1.1.3 Uplink Data Transfer........................................................................................................................... 530
7.1.1.3.1 Correct Handling of UL MAC PDU / Assignment / HARQ process ............................................ 530
7.1.1.3.2 Logical channel prioritization handling ......................................................................................... 542
7.1.1.3.2b Logical channel prioritization handling with Mapping restrictions ............................................... 546
7.1.1.3.3 Correct handling of MAC control information / Scheduling requests ........................................... 554
7.1.1.3.4 Correct handling of MAC control information / Buffer status / UL data arrive in the UE Tx
buffer / Regular BSR ..................................................................................................................... 559
7.1.1.3.5 Correct handling of MAC control information / Buffer Status / UL resources are allocated /
Padding BSR ................................................................................................................................. 569
7.1.1.3.6 Correct handling of MAC control information / Buffer status / Periodic BSR timer expires ........ 576
7.1.1.3.7 UE power headroom reporting / Periodic reporting / DL pathloss change reporting .................... 583
7.1.1.3.8 UE power headroom reporting / SCell activation / DL pathloss change reporting........................ 590
7.1.1.3.8.1 UE power headroom reporting / SCell activation / DL pathloss change reporting/ Intra-
band Contiguous CA ................................................................................................................ 590
ETSI
7.1.1.3.8.2 UE power headroom reporting / SCell activation / DL pathloss change reporting / Inter-
band CA ................................................................................................................................... 599
7.1.1.3.8.3 UE power headroom reporting / SCell activation / DL pathloss change reporting / Intra-
band non-Contiguous CA ........................................................................................................ 599
7.1.1.3.9 Correct Handling of UL HARQ process / PUSCH Aggregation ................................................... 599
7.1.1.3.10 Correct Handling of HARQ process / Multiple CORESETPoolIndex .......................................... 606
7.1.1.3.11 Correct handling of UL grant prioritization................................................................................... 609
7.1.1.3.12 Correct Handling of UL HARQ process / PUSCH Repetition Type B ......................................... 615
7.1.1.4 Transport Size Selection ..................................................................................................................... 626
7.1.1.4.1 DL-SCH Transport Block Size Selection ...................................................................................... 626
7.1.1.4.1.0 Common parameters for DL-SCH Transport Block Size Selection......................................... 626
7.1.1.4.1.1 DL-SCH Transport Block Size selection / DCI format 1_0 ..................................................... 626
7.1.1.4.1.2 Void ......................................................................................................................................... 634
7.1.1.4.1.3 DL-SCH transport block size selection / DCI format 1_1 / RA type 0/RA Type 1 / 2
Codewords enabled .................................................................................................................. 634
Codewords enabled / 256QAM................................................................................................ 647
7.1.1.4.1.5 DL-SCH transport block size selection / DCI format 1_2 ....................................................... 661
7.1.1.4.2 UL-SCH Transport Block Size Selection ...................................................................................... 672
7.1.1.4.2.0 Common parameters for UL-SCH Transport Block Size Selection......................................... 672
7.1.1.4.2.1 UL-SCH Transport Block Size selection / DCI format 0_0 / Transform precoding
disabled .................................................................................................................................... 673
7.1.1.4.2.2 Void ......................................................................................................................................... 685
7.1.1.4.2.3 UL-SCH transport block size selection / DCI format 0_1 / RA type 0/RA Type 1 /
Transform precoding disabled ................................................................................................. 685
256QAM / Transform precoding disabled ............................................................................... 702
7.1.1.4.2.5 UL-SCH Transport Block Size selection / DCI format 0_0 / Transform precoding and
64QAM .................................................................................................................................... 717
7.1.1.4.2.6 UL-SCH Transport Block Size selection / DCI format 0_2 ..................................................... 729
7.1.1.5 Discontinuous reception ...................................................................................................................... 746
7.1.1.5.0 DRX Common Definitions ............................................................................................................ 746
7.1.1.5.1 DRX operation / Short cycle not configured / Parameters configured by RRC ............................ 746
7.1.1.5.2 DRX operation / Short cycle not configured / Long DRX command MAC control element
reception ........................................................................................................................................ 752
7.1.1.5.3 DRX operation / Short cycle configured / Parameters configured by RRC .................................. 758
7.1.1.5.4 DRX operation / Short cycle configured / DRX command MAC control element reception........ 761
7.1.1.5.5 DRX operation / Short cycle configured / Long DRX command MAC control element
reception ........................................................................................................................................ 767
7.1.1.6 Semi-Persistent Scheduling ................................................................................................................. 772
7.1.1.6.1 Correct handling of DL assignment / Semi-persistent case ........................................................... 772
7.1.1.6.2 Correct handling of UL grant / configured grant Type 1 ............................................................... 780
7.1.1.6.3 Correct handling of UL grant / configured grant Type 2 ............................................................... 790
7.1.1.6.4 Correct handling of DL assignment / Multi Semi-persistent configuration ................................... 801
7.1.1.6.5 Correct handling of UL grant / Multi configured uplink grants .................................................... 808
7.1.1.7 Activation/Deactivation of SCells ....................................................................................................... 819
7.1.1.7.1 Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception /
sCellDeactivationTimer ................................................................................................................. 819
7.1.1.7.1.1 Activation/Deactivation of SCells / Activation/Deactivation MAC control element
reception / sCellDeactivationTimer / Intra-band Contiguous CA ............................................ 819
reception / sCellDeactivationTimer / Inter-Band CA .............................................................. 825
reception / sCellDeactivationTimer / Intra-band non-Contiguous CA..................................... 825
7.1.1.8 Bandwidth Part (BWP) operation ....................................................................................................... 825
7.1.1.8.1 Bandwidth Part (BWP) operation UL/DL ..................................................................................... 825
7.1.1.9 MAC Reconfiguration and Reset ........................................................................................................ 846
7.1.1.9.1 MAC Reset .................................................................................................................................... 846
7.1.1.10 Other Procedures ................................................................................................................................. 851
7.1.1.10.1 DataInactivityTimer expiry ........................................................................................................... 851
7.1.1.10.2 Recommended Bit Rate ................................................................................................................. 853
7.1.1.11 NR Dual Connectivity ......................................................................................................................... 858
ETSI
7.1.1.11.1 DC power headroom reporting / PSCell activation and DL pathloss change reporting ................ 858
7.1.1.12 UE power saving ................................................................................................................................. 862
7.1.1.12.1 Void ............................................................................................................................................... 862
7.1.1.12.2 Void ............................................................................................................................................... 862
7.1.1.12.3 DRX adaptation / UE wakeup indication ...................................................................................... 862
7.1.1.12.4 DRX adaptation / SCell dormancy indication ............................................................................... 874
7.1.1.12.4.1 DRX adaptation / SCell dormancy indication / Intra-band Contiguous CA ............................ 874
7.1.1.12.4.2 DRX adaptation / SCell dormancy indication / Intra-band non Contiguous CA ..................... 884
7.1.1.12.4.3 DRX adaptation / SCell dormancy indication / Inter-band CA................................................ 884
7.1.2 RLC .......................................................................................................................................................... 884
7.1.2.1 Default Pre-Test Conditions for all RLC test cases............................................................................. 884
7.1.2.1.1 Default Pre-Test Conditions for AM RLC test cases..................................................................... 884
7.1.2.1.2 Default Pre-Test Conditions for UM RLC test cases..................................................................... 885
7.1.2.2 RLC Unacknowledged mode .............................................................................................................. 886
7.1.2.2.1 UM RLC / Segmentation and reassembly / 6-bit SN / Segmentation Info (SI) field ..................... 886
7.1.2.2.2 UM RLC / Segmentation and reassembly / 12-bit SN / Segmentation Info (SI) field ................... 890
7.1.2.2.3 UM RLC / 6-bit SN / Correct use of sequence numbering ............................................................ 892
7.1.2.2.4 UM RLC / 12-bit SN / Correct use of sequence numbering .......................................................... 896
7.1.2.2.5 UM RLC / Receive Window operation and t-Reassembly expiry ................................................. 900
7.1.2.2.6 UM RLC / RLC re-establishment procedure ................................................................................. 905
7.1.2.3 RLC Acknowledged Mode ................................................................................................................. 909
7.1.2.3.1 AM RLC / 12-bit SN / Segmentation and reassembly / Segmentation Info (SI) field ................... 909
7.1.2.3.2 AM RLC / 18-bit SN / Segmentation and reassembly / Segmentation Info (SI) field ................... 913
7.1.2.3.3 AM RLC / 12-bit SN / Correct use of sequence numbering .......................................................... 915
7.1.2.3.4 AM RLC / 18-bit SN / Correct use of sequence numbering .......................................................... 919
7.1.2.3.5 AM RLC / 12-bit SN / Control of transmit window / Control of receive window ........................ 920
7.1.2.3.5a AM RLC / 18-bit SN / Control of transmit window / Control of receive window ........................ 924
7.1.2.3.6 AM RLC / Polling for status.......................................................................................................... 925
7.1.2.3.7 AM RLC / Receiver status triggers ............................................................................................... 931
7.1.2.3.8 AM RLC / Reconfiguration of RLC parameters by upper layers .................................................. 936
7.1.2.3.9 AM RLC / Reassembling of AMD PDUs ..................................................................................... 942
7.1.2.3.10 AM RLC / Re-transmission of RLC PDU with and without re-segmentation .............................. 950
7.1.2.3.11 AM RLC / RLC re-establishment procedure ................................................................................. 957
7.1.3 PDCP ........................................................................................................................................................ 962
7.1.3.0 Default Pre-Test Conditions for all PDCP test cases .......................................................................... 962
7.1.3.1 Maintenance of PDCP sequence numbers for radio bearers ............................................................... 963
7.1.3.1.1 Maintenance of PDCP sequence numbers / User plane / 12 bit SN .............................................. 963
7.1.3.1.2 Maintenance of PDCP sequence numbers / User plane / 18 bit SN .............................................. 968
7.1.3.2 PDCP integrity protection ................................................................................................................... 968
7.1.3.2.1 Integrity protection / Correct functionality of integrity algorithm SNOW3G / SRB / DRB ......... 968
7.1.3.2.2 Integrity protection / Correct functionality of integrity algorithm AES / SRB / DRB .................. 976
7.1.3.2.3 Integrity protection / Correct functionality of integrity algorithm ZUC / SRB / DRB .................. 977
7.1.3.3 PDCP Ciphering and deciphering ....................................................................................................... 978
7.1.3.3.1 Ciphering and deciphering / Correct functionality of encryption algorithm SNOW3G / SRB /
DRB ............................................................................................................................................... 978
7.1.3.3.2 Ciphering and deciphering / Correct functionality of encryption algorithm AES / SRB / DRB ... 983
7.1.3.3.3 Ciphering and deciphering / Correct functionality of encryption algorithm ZUC / SRB / DRB ... 984
7.1.3.4 PDCP Handover .................................................................................................................................. 985
7.1.3.4.1 PDCP handover / Lossless handover / PDCP sequence number maintenance / PDCP status
report to convey the information on missing or acknowledged PDCP SDUs at handover / In-
order delivery and duplicate elimination in the downlink ............................................................. 985
7.1.3.4.2 PDCP handover / Non-lossless handover / PDCP sequence number maintenance ....................... 994
7.1.3.4.3 PDCP handover / DAPS handover / Status reporting / Intra-frequency ........................................ 998
7.1.3.5 PDCP other ....................................................................................................................................... 1006
7.1.3.5.1 PDCP Discard.............................................................................................................................. 1006
7.1.3.5.2 PDCP Uplink Routing / Split DRB ............................................................................................. 1008
7.1.3.5.3 PDCP Data Recovery .................................................................................................................. 1013
7.1.3.5.4 PDCP reordering / Maximum re-ordering delay below t-Reordering / t-Reordering timer
operations .................................................................................................................................... 1020
7.1.3.5.5 PDCP Duplication ....................................................................................................................... 1025
7.1.3.5.6 PDCP Duplication / 3 RLC entities ............................................................................................. 1031
ETSI
7.1.3.5.7 Ethernet header compression and decompression / Correct functionality of ethernet header
compression and decompression ................................................................................................. 1036
7.1.4 SDAP ...................................................................................................................................................... 1039
7.1.4.1 SDAP Data Transfer and PDU Header Handling UL/DL ................................................................. 1039
7.1.4.2 SDAP Data Transfer handling without Header UL/DL .................................................................... 1048
8 RRC ....................................................................................................................................................1055
8.1 NR RRC ....................................................................................................................................................... 1055
8.1.1 RRC connection management procedures .............................................................................................. 1055
8.1.1.1 Paging ............................................................................................................................................... 1055
8.1.1.1.1 RRC / Paging for connection / Multiple paging records.............................................................. 1055
8.1.1.1.2 RRC / Paging for connection / Shared network environment ...................................................... 1060
8.1.1.2 RRC connection establishment ......................................................................................................... 1066
8.1.1.2.1 RRC connection establishment / Return to idle state after T300 expiry /
connEstFailOffsetValidity / T300 expired................................................................................... 1066
8.1.1.2.2 Void ............................................................................................................................................. 1071
8.1.1.2.3 RRC connection establishment / RRC Reject with wait time ...................................................... 1071
8.1.1.2.4 RRC connection establishment / Extended and spare fields in SI ............................................... 1074
8.1.1.3 RRC release....................................................................................................................................... 1077
8.1.1.3.1 RRC connection release / Redirection to another NR frequency................................................. 1077
8.1.1.3.2 RRC connection release / Redirection from NR to E-UTRA ...................................................... 1080
8.1.1.3.3 RRC connection release / Success / With priority information / T320 expiry............................. 1083
8.1.1.3.4 RRC connection release / Success / With priority information / T320 expiry / E-UTRA ........... 1094
8.1.1.3.5 Void ............................................................................................................................................. 1103
8.1.1.3.6 Void ............................................................................................................................................. 1103
8.1.1.3.7 RRC connection release / Success / Deprioritisation / Frequency / T325 expiry ........................ 1103
8.1.1.3.7a RRC connection release / Success / Deprioritisation / NR / T325 expiry ................................... 1105
8.1.1.4 RRC resume ...................................................................................................................................... 1107
8.1.1.4.1 RRC resume / Suspend-Resume / RNA update / Success / Short message for SI update ........... 1107
8.1.1.4.2 RRC resume / Suspend-Resume / RRC setup / T319 expiry ....................................................... 1118
8.1.1.4.3 Void ............................................................................................................................................. 1123
8.1.1.4.4 RRC resume / Suspend-Resume / RRC reconfiguration / Active MCG SCell addition / Intra-
band Contiguous CA ................................................................................................................... 1123
8.1.1.4.5 RRC resume / Suspend-Resume / RRC reconfiguration / Active MCG SCell addition / Intra-
band non-Contiguous CA ............................................................................................................ 1124
8.1.1.4.6 RRC resume / Suspend-Resume / RRC reconfiguration / Active MCG SCell addition / Inter-
band CA....................................................................................................................................... 1125
8.1.1.4.7 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Intra-band
Contiguous CA ............................................................................................................................ 1125
8.1.1.4.8 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Intra-band non-
Contiguous CA ............................................................................................................................ 1126
8.1.1.4.9 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Inter-band CA ..... 1127
8.1.2 RRC reconfiguration ............................................................................................................................... 1127
8.1.2.1 Radio bearer establishment / reconfiguration / release ...................................................................... 1127
8.1.2.1.1 RRC reconfiguration / DRB / SRB / Establishment / Modification / Release / Success ............. 1127
8.1.2.1.2 RRC reconfiguration / RRC bearer establishment / uplinkTxDirectCurrentList ......................... 1136
8.1.2.1.3 Void ............................................................................................................................................. 1139
8.1.2.1.4 RRC reconfiguration / Dedicated RLF timer ............................................................................... 1139
8.1.2.1.5 NR CA / RRC reconfiguration / SCell addition / modification / release / Success ..................... 1142
8.1.2.1.5.1 NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Intra-
band Contiguous CA .............................................................................................................. 1142
8.1.2.1.5.2 NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Inter-
band CA ................................................................................................................................. 1146
band non-contiguous CA ....................................................................................................... 1146
8.1.3 Measurement configuration control and reporting .................................................................................. 1147
8.1.3.1 Intra NR measurements ..................................................................................................................... 1147
8.1.3.1.1 Measurement configuration control and reporting / Intra NR measurements / Event A1 /
Event A2 ...................................................................................................................................... 1147
8.1.3.1.2 Measurement configuration control and reporting / Event A3 / Measurement of Neighbour
NR cell / Intra-frequency measurements ..................................................................................... 1158
ETSI

NR cell / Inter-frequency measurements ..................................................................................... 1168
NR cell / Inter-band measurements ............................................................................................. 1170
8.1.3.1.11 Measurement configuration control and reporting / Intra NR measurements / Two
simultaneous events A3 (intra and inter-frequency measurements) / RSRQ based
measurements .............................................................................................................................. 1199
simultaneous events A5 (intra and inter-frequency measurements) / SINR based
measurements .............................................................................................................................. 1209
8.1.3.1.13 Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based
intra-frequency measurements / Measurement of Neighbour NR cell......................................... 1219
8.1.3.1.14 Void ............................................................................................................................................. 1239
8.1.3.1.14A Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based
inter-frequency measurements / Measurement of Neighbour NR cell......................................... 1239
8.1.3.1.15 Void ............................................................................................................................................. 1245
8.1.3.1.15A Measurement configuration control and reporting / Intra NR measurements / Blacklisting ....... 1245
8.1.3.1.16 Measurement configuration control and reporting / Intra NR measurements / Whitelisting ....... 1259
8.1.3.1.17 NR CA / Measurement configuration control and reporting / Intra NR measurements / Event
A6 ................................................................................................................................................ 1268
8.1.3.1.17.1 NR CA / Measurement configuration control and reporting / Intra NR measurements /
Event A6 / Intra-band Contiguous CA ................................................................................... 1268
Event A6 / Inter-band CA ...................................................................................................... 1278
Event A6 / Intra-band non Contiguous CA ............................................................................ 1280
8.1.3.1.18 NR CA / Measurement configuration control and reporting / Intra NR measurements /
Additional measurement reporting .............................................................................................. 1280
Additional measurement reporting / Intra-band Contiguous CA ........................................... 1280
Additional measurement reporting / Inter-band CA .............................................................. 1292
Additional measurement reporting / Intra-band non Contiguous CA .................................... 1294
8.1.3.1.19 Measurement configuration control and reporting / Inter-frequency measurements/ SFTD ....... 1294
8.1.3.1.20 Measurement configuration control and reporting / Measurement Gaps / gapFR1 ..................... 1300
8.1.3.1.21 Measurement configuration control and reporting / Measurement Gaps / gapFR2 ..................... 1309
8.1.3.1.22 Void ............................................................................................................................................. 1317
8.1.3.1.23 Measurement configuration control and reporting / Intra NR measurements / Periodic
reporting / Continuation of the measurements after RRC Resume .............................................. 1317
8.1.3.2 Inter-RAT measurements .................................................................................................................. 1324
8.1.3.2.1 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 /
Measurement of E-UTRA cells ................................................................................................... 1324
Measurement of E-UTRA cells ................................................................................................... 1334
Measurement of E-UTRA cells / RSRQ based measurements .................................................... 1344
Measurement of E-UTRA cells / SINR based measurements ..................................................... 1353
8.1.3.2.5 Void ............................................................................................................................................. 1363
ETSI
8.1.3.2.6 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / NR

to UMTS ...................................................................................................................................... 1363
8.1.3.2.7 Measurement configuration control and reporting / Inter-RAT measurements / Event B2 / NR
to UMTS ...................................................................................................................................... 1370
8.1.3.2.8 Measurement configuration control and reporting / Inter-RAT measurements / Periodic
reporting / NR to UTRA .............................................................................................................. 1379
8.1.3.3 Measurement for self-optimized networks ........................................................................................ 1388
8.1.3.3.1 Measurement configuration control and reporting / CGI reporting of NR cell ........................... 1388
8.1.3.3.2 Measurement configuration control and reporting / CGI reporting of E-UTRA cell .................. 1399
8.1.4 Handover ................................................................................................................................................ 1411
8.1.4.1 Intra NR handover ............................................................................................................................. 1411
8.1.4.1.1 Void ............................................................................................................................................. 1411
8.1.4.1.2 Intra NR handover / Success / Inter-frequency ............................................................................ 1411
8.1.4.1.3 Void ............................................................................................................................................. 1427
8.1.4.1.4 Void ............................................................................................................................................. 1427
8.1.4.1.5 Intra NR handover / Failure / Re-establishment successful ......................................................... 1427
8.1.4.1.6 Intra NR handover / Failure / Re-establishment failure ............................................................... 1434
8.1.4.1.7 NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release ......... 1438
8.1.4.1.7.1 NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell release /
Intra-band Contiguous CA ..................................................................................................... 1438
Inter-band CA ........................................................................................................................ 1443
Intra-band non-contiguous CA............................................................................................... 1444
8.1.4.1.8 NR CA / Intra NR handover / Success / PCell Change / SCell no Change ................................. 1445
8.1.4.1.8.1 NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Intra-band
Contiguous CA ...................................................................................................................... 1445
8.1.4.1.8.2 NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Inter-band CA.. 1450
8.1.4.1.8.3 NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Intra-band non-
contiguous CA ....................................................................................................................... 1450
8.1.4.1.9 NR CA / Intra NR handover / Failure / Re-establishment successful .......................................... 1451
8.1.4.1.9.1 NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band
Contiguous CA ...................................................................................................................... 1451
8.1.4.1.9.2 NR CA / Intra NR handover / Failure / Re-establishment successful / Inter-band CA .......... 1462
8.1.4.1.9.3 NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band non-
contiguous CA ....................................................................................................................... 1463
8.1.4.2 Inter-RAT handover .......................................................................................................................... 1463
8.1.4.2.1 Inter-RAT handover from NR ..................................................................................................... 1463
8.1.4.2.1.1 Inter-RAT handover / From NR to E-UTRA / Success ......................................................... 1463
8.1.4.2.1.2 Inter-RAT handover / From NR to EN-DC / Success ................................................................. 1469
8.1.4.2.2 Inter-RAT handover to NR .......................................................................................................... 1476
8.1.4.2.2.1 Inter-RAT handover / From E-UTRA to NR / Success ......................................................... 1476
8.1.4.3 DAPS handover................................................................................................................................. 1482
8.1.4.3.1 DAPS handover with key change / Success / Intra-frequency..................................................... 1482
8.1.4.3.2 DAPS handover / HO Failure and source link available / HO Success and RLF in source /
Intra-frequency ............................................................................................................................ 1493
8.1.4.3.3 1508
8.1.4.3.4 DAPS handover / Success / Inter-frequency................................................................................ 1508
8.1.4.4 Conditional handover ........................................................................................................................ 1509
8.1.4.4.1 Conditional handover / Success / A3 / A5 / A3+A5 .................................................................... 1509
8.1.4.4.2 Conditional handover / modify conditional handover configuration ........................................... 1520
8.1.4.4.3 Conditional handover / Failure .................................................................................................... 1530
8.1.5 RRC others.............................................................................................................................................. 1541
8.1.5.1 UE capability transfer ....................................................................................................................... 1541
8.1.5.1.1 UE capability transfer / Success .................................................................................................. 1541
8.1.5.2 SI change / On-demand SIB .............................................................................................................. 1560
8.1.5.2.1 Void ............................................................................................................................................. 1560
8.1.5.2.2 SI change / Notification of BCCH modification / Short message for SI update in NR
RRC_CONNECTED state ........................................................................................................... 1560
8.1.5.3 PWS notification ............................................................................................................................... 1563
8.1.5.3.1 PWS notification / PWS reception in NR RRC_IDLE state........................................................ 1563
8.1.5.3.2 PWS notification / PWS reception in NR RRC_INACTIVE state .............................................. 1565
ETSI
8.1.5.3.3 PWS notification / PWS reception in NR RRC_CONNECTED state......................................... 1566

8.1.5.3.4 PWS notification / PWS reception using dedicatedSystemInformationDelivery ........................ 1567
8.1.5.4 Counter check ................................................................................................................................... 1573
8.1.5.4.1 Counter check / Reception of CounterCheck message by the UE ............................................... 1573
8.1.5.5 Redirection to NR ............................................................................................................................. 1578
8.1.5.5.1 Redirection to NR / From E-UTRA / Success ............................................................................. 1578
8.1.5.6 Radio link failure .............................................................................................................................. 1582
8.1.5.6.1 Radio link failure / RRC connection re-establishment success ................................................... 1582
8.1.5.6.2 Void ............................................................................................................................................. 1590
8.1.5.6.3 Radio link failure / T311 expiry .................................................................................................. 1590
8.1.5.6.4 Void ............................................................................................................................................. 1593
8.1.5.6.5 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell ..................... 1593
8.1.5.6.5.1 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-
band Contiguous CA .............................................................................................................. 1593
8.1.5.6.5.2 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Inter-
band CA ................................................................................................................................. 1597
8.1.5.6.5.3 NR CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-
band non-Contiguous CA ...................................................................................................... 1598
8.1.5.7 Failure information............................................................................................................................ 1598
8.1.5.7.1 Failure information / RLC failure / MCG .................................................................................... 1598
8.1.5.7.1.1 Failure information / RLC failure / MCG / Intra-band Contiguous CA................................. 1598
8.1.5.7.1.2 Failure information / RLC failure / MCG / Inter-band CA .................................................... 1605
8.1.5.7.1.3 Failure information / RLC failure / MCG / Intra-band non Contiguous CA .......................... 1606
8.1.5.8 Processing delay ................................................................................................................................ 1606
8.1.5.8.1 Processing delay / RRC_Idle to RRC_Connected / RRC_Inactive to RRC_Connected /
Success / Latency check .............................................................................................................. 1606
8.1.5.8.2 Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell
addition ........................................................................................................................................ 1616
8.1.5.8.2.1 Processing delay / RRC_Inactive to RRC_Connected / Success / Latency check / SCell
addition / Intra-band Contiguous CA ..................................................................................... 1616
addition / Inter-band CA ........................................................................................................ 1621
addition / Intra-band non-Contiguous CA.............................................................................. 1622
8.1.5.9 RACS / UL Message Segment transfer ............................................................................................. 1622
8.1.5.9.1 RACS / UL Message Segment transfer / UECapabilityInformation ........................................... 1622
8.1.5.10 UE Assistance Information ............................................................................................................... 1629
8.1.5.10.1 UE Assistance Information/ Release Preference ......................................................................... 1629
8.1.6 SON and MDT support for NR............................................................................................................... 1634
8.1.6.1 Intra NR MDT ................................................................................................................................... 1634
8.1.6.1.1 Immediate MDT .......................................................................................................................... 1634
8.1.6.1.1.1 Immediate MDT / Measurement reporting / Location information ....................................... 1634
8.1.6.1.1.2 Immediate MDT / Measurement / Latency metrics for UL PDCP Packet Delay per DRB ... 1641
8.1.6.1.2 Logged MDT ............................................................................................................................... 1646
8.1.6.1.2.1 Logged MDT / RRC_IDLE / Logging and reporting / Intra-frequency measurement........... 1646
8.1.6.1.2.2 Logged MDT / RRC_INACTIVE / Logging and reporting / Inter-frequency measurement . 1654
8.1.6.1.2.3 Logged MDT / Intra-frequency measurement, logging and reporting ................................... 1662
8.1.6.1.2.4 Logged MDT/ RRC_IDLE / Logging and reporting / periodic measurement trigger ............ 1673
8.1.6.1.2.5 Logged MDT/ RRC_IDLE / Logging and reporting / event-based trigger ............................ 1682
8.1.6.1.2.6 Logged MDT/ RRC_IDLE / Logging and reporting / event-based trigger/ out-of-coverage 1690
8.1.6.1.2.7 Logged MDT / Logging and reporting / Indication of logged measurements at NR
reestablishment ...................................................................................................................... 1699
8.1.6.1.2.8 Logged MDT / Logging and reporting / Reporting at RRC reconfiguration ......................... 1702
8.1.6.1.2.9 Logged MDT / Location information .................................................................................... 1710
8.1.6.1.2.10 Logged MDT / Maintaining logged measurement configuration / UE mobility .................... 1715
8.1.6.1.2.11 Logged MDT / UE state transitions ....................................................................................... 1722
8.1.6.1.2.12 Logged MDT / Release of logged MDT measurement configuration / Expire of duration
timer ....................................................................................................................................... 1728
8.1.6.1.2.13 Logged MDT / Release of logged MDT measurement configuration / Reception of new
logged measurement configuration ........................................................................................ 1736
8.1.6.1.3 Radio Link Failure report ............................................................................................................ 1743
8.1.6.1.3.1 Radio Link Failure / Reporting of Intra-frequency measurements ........................................ 1743
ETSI
8.1.6.1.3.2 Radio Link Failure / Reporting of Inter-frequency measurements ........................................ 1754

8.1.6.1.3.3 Radio Link Failure / Reporting at RRC connection establishment and reestablishment ....... 1756
8.1.6.1.3.4 Radio Link Failure / Reporting at NR handover .................................................................... 1765
8.1.6.1.3.5 Radio Link Failure / Location information ............................................................................ 1772
8.1.6.1.3.6 Radio Link Failure / RACH failure report ............................................................................. 1778
8.1.6.1.3.7 Radio Link Failure / Logging and reporting / Reporting at intra NR handover / PLMN list . 1784
8.1.6.1.4 Connection Establishment Failure ............................................................................................... 1792
8.1.6.1.4.1 Connection Establishment Failure / Logging and reporting / T300 expiry ............................ 1792
8.1.6.1.4.2 Connection Establishment Failure / Logging and reporting / RRC Resume .......................... 1796
8.1.6.1.4.3 Connection Establishment Failure / Logging and reporting / Reporting at intra-NR
handover ................................................................................................................................ 1801
8.1.6.1.4.4 Connection Establishment Failure / Logging and reporting / Reporting at RRC connection
re-establishment ..................................................................................................................... 1807
8.1.6.1.4.5 Connection Establishment Failure / Logging and reporting / Location Information ............. 1810
8.1.6.1.4.6 Connection Establishment Failure / Logging and reporting / Reporting of Intra-frequency
measurements......................................................................................................................... 1815
8.1.6.1.4.7 Connection Establishment Failure / Logging and reporting / Reporting of Inter-frequency
measurements......................................................................................................................... 1820
8.1.6.1.4.8 Connection Establishment Failure / Logging and reporting / RACH failure report .............. 1825
8.1.6.2 Inter-RAT MDT ................................................................................................................................ 1830
8.1.6.2.1 Inter-RAT MDT / Immediate MDT / Periodic reporting of E-UTRAN/ Location information .. 1830
8.1.6.2.2 Inter-RAT MDT / Logged MDT / E-UTRA Inter-RAT measurement, logging and reporting ... 1837
8.1.6.2.3 Inter-RAT MDT / Radio Link Failure / Reporting at E-UTRA Inter-RAT handover ................. 1844
8.1.6.2.4 Inter-RAT MDT / Connection Establishment Failure / Logging and reporting / Reporting of
E-UTRA Inter-RAT handover ..................................................................................................... 1856
8.1.6.3 Inter-System MDT ............................................................................................................................ 1861
8.1.6.3.1 Inter-System MDT / Immediate MDT ......................................................................................... 1861
8.1.6.3.1.1 Inter-System MDT / Immediate MDT / Measurement reporting / Bluetooth measurement
collection................................................................................................................................ 1861
8.1.6.3.1.2 Inter-System MDT / Immediate MDT / Measurement reporting / WLAN measurement
collection................................................................................................................................ 1869
8.1.6.3.1.3 Inter-System MDT / Immediate MDT / Measurement reporting / sensor information .......... 1877
8.1.6.3.2 Inter-System MDT / Logged MDT.............................................................................................. 1882
8.1.6.3.2.1 Inter-System MDT / Logged MDT / Logging and reporting / Bluetooth measurement
collection................................................................................................................................ 1882
8.1.6.3.2.2 Inter-System MDT / Logged MDT / Logging and reporting / WLAN measurement
collection................................................................................................................................ 1887
8.1.6.3.2.3 Inter-System MDT / Logged MDT / Logging and reporting / sensor information ................ 1892
8.1.6.3.3 Inter-System MDT / Radio Link Failure ..................................................................................... 1896
8.1.6.3.3.1 Inter-System MDT / Radio Link Failure / Logging and reporting / Bluetooth measurement
collection................................................................................................................................ 1896
8.1.6.3.3.2 Inter-System MDT / Radio Link Failure / Logging and reporting / WLAN measurement
collection................................................................................................................................ 1901
8.1.6.3.3.3 Inter-System MDT / Radio Link Failure / Logging and reporting / sensor information ........ 1908
8.1.6.3.4 Inter-System MDT / Connection Establishment Failure ............................................................. 1913
8.1.6.3.4.2 Inter-System MDT / Connection Establishment Failure / Logging and reporting / WLAN
measurement collection ......................................................................................................... 1919
8.1.6.3.4.3 Inter-System MDT / Connection Establishment Failure / Logging and reporting / sensor
information............................................................................................................................. 1924
8.2 MR-DC RRC ................................................................................................................................................ 1928
8.2.1 UE Capability ......................................................................................................................................... 1928
8.2.1.1 UE capability transfer / Success ........................................................................................................ 1928
8.2.1.1.1 UE capability transfer / Success / EN-DC ................................................................................... 1928
8.2.1.2 Void................................................................................................................................................... 1964
8.2.2 Radio Bearer Addition, Modification and Release ................................................................................. 1964
8.2.2.1 Radio Bearer Addition, Modification and Release / SRB ................................................................. 1964
8.2.2.1.1 SRB3 Establishment, Reconfiguration and Release / NR addition, modification and release /
EN-DC ......................................................................................................................................... 1964
8.2.2.1.2 SRB3 Establishment, Reconfiguration and Release / NR addition, modification and release /
NR-DC......................................................................................................................................... 1973
8.2.2.2 Split SRB Establishment and Release ............................................................................................... 1981
8.2.2.2.1 Split SRB Establishment and Release / EN-DC .......................................................................... 1981
ETSI
8.2.2.3 Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB ................. 1992
8.2.2.3.1 Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB with
one UL path / EN-DC .................................................................................................................. 1992
8.2.2.3.2 Simultaneous SRB3 and Split SRB / Sequential message flow on SRB3 and Split SRB with
one UL path / NR-DC.................................................................................................................. 2002
8.2.2.4 PSCell addition, modification and release / SCG DRB .................................................................... 2012
8.2.2.4.1 PSCell addition, modification and release / SCG DRB / EN-DC ................................................ 2012
8.2.2.4.2 PSCell addition, modification and release / SCG DRB / NR-DC ............................................... 2022
8.2.2.5 PSCell addition, modification and release / Split DRB ..................................................................... 2029
8.2.2.5.1 PSCell addition, modification and release / Split DRB / EN-DC ................................................ 2029
8.2.2.5.2 PSCell addition, modification and release / Split DRB / NR-DC ................................................ 2039
8.2.2.6 Bearer Modification / MCG DRB ..................................................................................................... 2048
8.2.2.6.1 Bearer Modification / MCG DRB / SRB / PDCP version change / EN-DC................................ 2048
8.2.2.7 Bearer Modification / Handling for bearer type change without security key change ...................... 2060
8.2.2.7.1 Bearer Modification / Handling for bearer type change without security key change / EN-DC . 2060
8.2.2.7.2 Bearer Modification / Handling for bearer type change without security key change / NR-DC . 2074
8.2.2.8 Bearer Modification / Handling for bearer type change with security key change ........................... 2086
8.2.2.8.1 Bearer Modification / Handling for bearer type change with security key change / EN-DC ...... 2086
8.2.2.8.2 Bearer Modification / Handling for bearer type change with security key change / NR-DC ...... 2110
8.2.2.9 Bearer Modification / Uplink data path / Split DRB Reconfiguration .............................................. 2132
8.2.2.9.1 Bearer Modification / Uplink data path / Split DRB Reconfiguration / EN-DC ......................... 2132
8.2.2.9.2 Bearer Modification / Uplink data path / Split DRB Reconfiguration / NR-DC ......................... 2140
8.2.3 Measurement Configuration Control and Reporting / Handovers .......................................................... 2145
8.2.3.1 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 /
Measurement of NR cells .................................................................................................................. 2145
Measurement of NR cells / EN-DC ............................................................................................. 2145
Measurement of NR cells / RSRQ based measurements ................................................................... 2156
Measurement of NR cells / RSRQ based measurements / EN-DC .............................................. 2156
8.2.3.3 Measurement configuration control and reporting / Inter-RAT measurements / Periodic reporting
/ Measurement of NR cells ................................................................................................................ 2166
8.2.3.3.1 Measurement configuration control and reporting / Inter-RAT measurements / Periodic
reporting / Measurement of NR cells / EN-DC ........................................................................... 2166
8.2.3.4 Measurement configuration control and reporting / Event A1 / Measurement of NR PSCell .......... 2177
8.2.3.4.1 Measurement configuration control and reporting / Event A1 / Measurement of NR PSCell /
EN-DC ......................................................................................................................................... 2177
8.2.3.5 Measurement configuration control and reporting / Event A2 / Measurement of NR PSCell .......... 2186
8.2.3.5.1 Measurement configuration control and reporting / Event A2 / Measurement of NR PSCell /
EN-DC ......................................................................................................................................... 2186
8.2.3.6 Measurement configuration control and reporting / Event A3 / Measurement of Neighbour NR
cells ................................................................................................................................................... 2192
NR cells / Intra-frequency measurements / EN-DC .................................................................... 2192
8.2.3.6.1a Measurement configuration control and reporting / Event A3 / Measurement of Neighbour
NR cell / Inter-frequency measurements / EN-DC ...................................................................... 2200
8.2.3.6.1b Measurement configuration control and reporting / Event A3 / Measurement of Neighbour
NR cell / Inter-band measurements / EN-DC .............................................................................. 2203
8.2.3.7 Measurement configuration control and reporting / Event A4 (intra-frequency, inter-frequency
and inter-band measurements) / Measurement of Neighbour NR cell .............................................. 2206
NR cell / Intra-frequency measurements / EN-DC ...................................................................... 2206
8.2.3.8 Measurement configuration control and reporting / Event A5 / Measurement of Neighbour NR
cell ..................................................................................................................................................... 2222
NR cell / Intra-frequency measurements / EN-DC ...................................................................... 2222
ETSI

8.2.3.9 Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based intra-
frequency measurements / Measurement of Neighbour NR cell ....................................................... 2240
8.2.3.9.1 Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based
Intra-frequency measurements / Measurement of Neighbour NR Cell / EN-DC ........................ 2240
8.2.3.10 Measurement configuration control and reporting / SS/PBCH block based / CSI-RS based inter-
frequency measurements / Measurement of Neighbour NR cell ....................................................... 2261
8.2.3.10.1 Measurement configuration control and reporting / SS/PBCH block based /CSI-RS based
Inter-frequency measurements/ Measurement of Neighbour NR Cell / EN-DC ......................... 2261
8.2.3.11 Measurement configuration control and reporting / Measurement Gaps .......................................... 2284
8.2.3.11.1 Measurement configuration control and reporting / Measurement Gaps / NR FR1 / EN-DC ..... 2284
8.2.3.11.2 Measurement configuration control and reporting / Measurement Gaps / NR FR2 / EN-DC ..... 2300
8.2.3.11.3 Measurement configuration control and reporting / Measurement Gaps / NR-DC ..................... 2309
Measurement of NR cells .................................................................................................................. 2316
Measurement of NR cells / EN-DC ............................................................................................. 2316
8.2.3.13 PCell Handover with SCG change / Reconfiguration with sync / SCG DRB ................................... 2327
8.2.3.13.1 PCell Handover with SCG change / Reconfiguration with sync / SCG DRB / EN-DC .............. 2327
8.2.3.14 SCG change / Reconfiguration with sync / Split DRB ...................................................................... 2334
8.2.3.14.1 SCG change / Reconfiguration with sync / Split DRB / EN-DC ................................................. 2334
8.2.3.14.2 SCG change / Reconfiguration with sync / Split DRB / NR-DC................................................. 2340
8.2.3.15 Measurement configuration control and reporting / Two simultaneous events A2 and A3 (intra-
frequency measurements) / Measurement of Neighbour NR cells .................................................... 2346
8.2.3.15.1 Measurement configuration control and reporting / Two simultaneous events A2 and A3
(intra-frequency measurements) / Measurement of Neighbour NR cells / EN-DC ..................... 2346
8.2.3.16 Measurement configuration control and reporting / SRB3 ............................................................... 2356
8.2.3.16.1 Measurement configuration control and reporting / SRB3 / Intra NR measurements / EN-DC .. 2356
8.2.3.16.2 Measurement configuration control and reporting / SRB3 / Intra NR measurements / NR-DC.. 2363
8.2.3.17 Measurement configuration control and reporting / SFTD: .............................................................. 2370
8.2.3.17.1 Measurement configuration control and reporting / SFTD / EN-DC .......................................... 2370
8.2.3.17.2 Measurement configuration control and reporting / SFTD / NR-DC .......................................... 2379
8.2.3.18 Conditional PSCell change ............................................................................................................... 2386
8.2.3.18.1 Conditional PSCell change / Success .......................................................................................... 2386
8.2.4 Carrier Aggregation ................................................................................................................................ 2395
8.2.4.1 NR CA / NR SCell addition / modification / release / Success ......................................................... 2395
8.2.4.1.1 NR CA / NR SCell addition / modification / release / Success / EN-DC .................................... 2395
8.2.4.1.1.1 NR CA / NR SCell addition / modification / release / Success / EN-DC / Intra-band
Contiguous CA ...................................................................................................................... 2395
8.2.4.1.1.2 NR CA / NR SCell addition / modification / release / Success / EN-DC / Intra-band non-
Contiguous CA ...................................................................................................................... 2405
8.2.4.1.1.3 NR CA / NR SCell addition / modification / release / Success / EN-DC / Inter-band CA .... 2405
8.2.4.2 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release .......... 2406
8.2.4.2.1 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release/
EN-DC ......................................................................................................................................... 2406
8.2.4.2.1.1 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA
Release / EN-DC / Intra-band Contiguous CA ...................................................................... 2406
8.2.4.2.1.2 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release /
EN-DC / Intra-band non-Contiguous CA .................................................................................... 2420
8.2.4.2.1.3 NR CA / Simultaneous PSCell and SCell addition / PSCell and SCell change / CA Release /
EN-DC / Inter-band CA............................................................................................................... 2421
8.2.4.3 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 ................................................... 2421
8.2.4.3.1 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC .............................. 2421
8.2.4.3.1.1 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Intra-band
Contiguous CA ............................................................................................................................ 2421
8.2.4.3.1.2 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Intra-band non-
Contiguous CA ............................................................................................................................ 2435
8.2.4.3.1.3 NR CA / SCell change / Intra-NR measurement event A6 / SRB3 / EN-DC / Inter-band CA .... 2435
8.2.5 Reconfiguration Failure / Radio link failure ........................................................................................... 2437
ETSI
8.2.5.1 Radio link failure / PSCell addition failure ....................................................................................... 2437

8.2.5.1.1 Radio link failure / Random access problem / EN-DC ................................................................ 2437
8.2.5.1.2 Radio link failure / Random access problem / NR-DC................................................................ 2439
8.2.5.2 Radio link failure / PSCell out of sync indication ............................................................................. 2442
8.2.5.2.1 Radio link failure / PSCell out of sync indication / EN-DC ........................................................ 2442
8.2.5.2.2 Radio link failure / PSCell out of sync indication / NR-DC ........................................................ 2445
8.2.5.3 Radio link failure / rlc-MaxNumRetx failure .................................................................................... 2449
8.2.5.3.1 Radio link failure / rlc-MaxNumRetx failure / EN-DC ............................................................... 2449
8.2.5.3.2 Radio link failure / rlc-MaxNumRetx failure / NR-DC ............................................................... 2452
8.2.5.4 Reconfiguration failure / SCG change failure ................................................................................... 2455
8.2.5.4.1 Reconfiguration failure / SCG change failure / EN-DC .............................................................. 2455
8.2.5.4.2 Reconfiguration failure / SCG change failure / NR-DC .............................................................. 2460
8.2.5.5 Reconfiguration failure / SCG Reconfiguration failure / SRB3 ........................................................ 2464
8.2.5.5.1 Void ............................................................................................................................................. 2465
8.2.5.6 Reconfiguration failure / SCG Reconfiguration failure / SRB1 ........................................................ 2465
8.2.5.6.1 Void ............................................................................................................................................. 2465
8.2.6 MR-DC RRC others................................................................................................................................ 2465
8.2.6.1 Failure information / RLC failure / SCG........................................................................................... 2465
8.2.6.1.1 Failure information / RLC failure / SCG / EN-DC ...................................................................... 2465
8.2.6.1.1.1 Failure information / RLC failure / SCG / EN-DC / Intra-band Contiguous CA ........................ 2465
8.2.6.1.1.2 Failure information / RLC failure / SCG / EN-DC / Inter-band CA............................................ 2474
8.2.6.1.1.3 Failure information / RLC failure / SCG / EN-DC / Intra-band non Contiguous CA ................. 2475
8.2.6.1.2 Failure information / RLC failure / SCG / NR-DC...................................................................... 2475
8.2.6.1.2.1 Failure information / RLC failure / SCG / NR-DC / Intra-band Contiguous CA ........................ 2475
8.2.6.1.2.2 Failure information / RLC failure / SCG / NR-DC / Inter-band CA ........................................... 2485
8.2.6.1.2.3 Failure information / RLC failure / SCG / NR-DC / Intra-band non Contiguous CA ................. 2486
8.2.6.2 Processing delay ................................................................................................................................ 2486
8.2.6.2.1 Processing delay / PSCell addition / SCG DRB / Success / Latency check / EN-DC ................. 2486
8.2.6.2.2 Processing delay / Latency check / NR-DC................................................................................. 2489
9 Mobility management.........................................................................................................................2493
9.1 5GS mobility management ........................................................................................................................... 2493
9.1.1 Primary authentication and key agreement ............................................................................................. 2493
9.1.1.1 EAP based primary authentication and key agreement / EAP-AKA' related procedures.................. 2493
9.1.1.2 EAP based primary authentication and key agreement / Reject ........................................................ 2497
9.1.1.3 EAP based primary authentication and key agreement / EAP message transport / Abnormal .......... 2502
9.1.1.4 5G AKA based primary authentication and key agreement / 5G-AKA related procedures .............. 2507
9.1.1.5 5G AKA based primary authentication and key agreement / Reject ................................................. 2514
9.1.1.6 5G AKA based primary authentication and key agreement / Abnormal ........................................... 2517
9.1.2 Security mode control ............................................................................................................................. 2522
9.1.2.1 NAS security mode command........................................................................................................... 2522
9.1.2.2 Protection of initial NAS signalling messages .................................................................................. 2528
9.1.2.3 Integrity protection / Correct functionality of 5G NAS integrity algorithm / SNOW3G .................. 2530
9.1.2.4 Integrity protection / Correct functionality of 5G NAS integrity algorithm / AES ........................... 2533
9.1.2.5 Integrity protection / Correct functionality of 5G NAS integrity algorithm / ZUC........................... 2534
9.1.2.6 Ciphering and deciphering / Correct functionality of 5G NAS encryption algorithm / SNOW3G ... 2535
9.1.2.7 Ciphering and deciphering / Correct functionality of 5G NAS encryption algorithm / AES ............ 2537
9.1.2.8 Ciphering and deciphering / Correct functionality of 5G NAS encryption algorithm / ZUC ........... 2538
9.1.3 Identification ........................................................................................................................................... 2539
9.1.3.1 Identification procedure .................................................................................................................... 2539
9.1.4 Generic UE configuration update ........................................................................................................... 2544
9.1.4.1 Generic UE configuration update / New 5G-GUTI, NITZ, registration requested, network slicing
indication, new allowed NSSAI / Acknowledgement from the UE .................................................. 2544
9.1.5 Registration ............................................................................................................................................. 2556
9.1.5.1 Initial registration .............................................................................................................................. 2556
9.1.5.1.1 Initial registration / Success / 5G-GUTI reallocation, last visited TAI........................................ 2556
9.1.5.1.2 Initial registration / 5GS services / Equivalent PLMN list handling ........................................... 2561
9.1.5.1.3 Initial registration / 5GS services / NSSAI handling ................................................................... 2565
9.1.5.1.3a Initial registration / 5GS services / NSSAI handling / NSSAI storage ........................................ 2575
9.1.5.1.4 Initial registration / 5GS services / MICO mode / TAI list handling ........................................... 2586
9.1.5.1.5 Initial registration / Abnormal / Failure after 5 attempts ............................................................. 2589
9.1.5.1.6 Initial registration / Rejected / Illegal UE .................................................................................... 2593
ETSI
9.1.5.1.7 Void ............................................................................................................................................. 2596

9.1.5.1.8 Initial registration / Rejected / Serving network not authorized .................................................. 2596
9.1.5.1.9 Initial registration / Abnormal / Change of cell into a new tracking area .................................... 2598
9.1.5.1.10 Initial registration / Rejected / PLMN not allowed...................................................................... 2600
9.1.5.1.11 Initial registration / Rejected / Tracking area not allowed ........................................................... 2603
9.1.5.1.12 Initial registration / Rejected / Roaming not allowed in this tracking area .................................. 2607
9.1.5.1.13 Initial registration / Rejected / No suitable cells in tracking area ................................................ 2611
9.1.5.1.14 Initial registration / Rejected / Congestion / Abnormal / T3346.................................................. 2614
9.1.5.1.15 Initial registration / Success / Extended and spare fields in UE network capability .................... 2618
9.1.5.2 Mobility and periodic registration update ......................................................................................... 2625
9.1.5.2.1 Mobility registration update / TAI list handling .......................................................................... 2625
9.1.5.2.2 Periodic registration update / Accepted ....................................................................................... 2632
9.1.5.2.3 2634
9.1.5.2.4 Mobility registration update / The lower layer requests NAS signalling connection recovery ... 2634
9.1.5.2.5 Void ............................................................................................................................................. 2638
9.1.5.2.6 Void ............................................................................................................................................. 2638
9.1.5.2.7 Mobility and periodic registration update / Rejected / UE identity cannot be derived by the
network ........................................................................................................................................ 2638
9.1.5.2.8 Mobility and periodic registration update / Rejected / Implicitly de-registered .......................... 2640
9.1.5.2.9 Void ............................................................................................................................................. 2644
9.1.6 De-registration ........................................................................................................................................ 2644
9.1.6.1 UE-initiated de-registration ............................................................................................................... 2644
9.1.6.1.1 UE-initiated de-registration / Switch off / Abnormal / De-registration and 5GMM common
procedure collision ...................................................................................................................... 2644
9.1.6.1.2 UE-initiated de-registration / Normal de-registration / Abnormal / Transmission failure
without TAI change from lower layers, de-registration and 5GMM common procedure
collision, T3521 timeout .............................................................................................................. 2648
9.1.6.1.3 UE-initiated de-registration / Abnormal / Change of cell into a new tracking area..................... 2652
9.1.6.1.4 Void ............................................................................................................................................. 2655
9.1.6.2 Network-initiated de-registration ...................................................................................................... 2655
9.1.6.2.1 Network-initiated de-registration / De-registration for 3GPP access / Re-registration required . 2655
9.1.6.2.2 Network-initiated de-registration / De-registration for 3GPP access / Re-registration not
required........................................................................................................................................ 2657
9.1.7 Service request ........................................................................................................................................ 2659
9.1.7.1 Service request / Idle mode uplink user data transport / Rejected / Restricted service area,
abnormal / T3517, T3525 .................................................................................................................. 2659
9.1.7.2 Service request / Connected mode user data transport / Abnormal / T3517 ..................................... 2665
9.1.8 SMS over NAS ....................................................................................................................................... 2671
9.1.8.1 SMS over NAS / MO and MT SMS over NAS / Idle mode ............................................................. 2671
9.1.8.2 SMS over NAS / Multiple MO and MT SMS over NAS / Connected mode .................................... 2678
9.1.9 RACS ...................................................................................................................................................... 2683
9.1.9.1 RACS / Network assigned UE radio capability ID ........................................................................... 2683
9.1.9.2 RACS / UE configuration update / UE radio capability ID .............................................................. 2686
9.1.9.3 2690
9.1.9.4 2690
9.1.9.5 RACS / Handling of delete indication for NW assigned UE radio capability ID.............................. 2690
9.1.10 Network slice-specific authentication and authorization ........................................................................ 2696
9.1.10.1 NSSAA / EAP message transport / Success ...................................................................................... 2696
9.1.10.2 to 9.1.10.5 ........................................................................................................................................................ 2703
9.1.10.6 NSSAA / UE configuration update / Rejected NSSAI ...................................................................... 2703
9.1.11 SNPN / Mobility management aspects ................................................................................................... 2708
9.1.11.1 SNPN / Initial registration / Rejected / Temporarily not authorized for this SNPN......................... 2708
9.1.11.2 SNPN / Initial registration / Rejected / Permanently not authorized for this SNPN ......................... 2713
9.2 5GS Non-3GPP Access Mobility Management ........................................................................................... 2717
9.2.1 Primary authentication and key agreement procedure ............................................................................ 2717
9.2.1.1 EAP based primary authentication and key agreement ..................................................................... 2717
9.2.1.2 5G AKA based primary authentication and key agreement .............................................................. 2719
9.2.2 Security Mode Control............................................................................................................................ 2723
9.2.2.1 NAS security mode command........................................................................................................... 2723
9.2.2.2 Protection of initial NAS signalling messages .................................................................................. 2729
9.2.3 Void ........................................................................................................................................................ 2731
9.2.4 Generic UE configuration ....................................................................................................................... 2731
ETSI
9.2.4.1 Generic UE configuration update ...................................................................................................... 2731

9.2.5 Registration ............................................................................................................................................. 2741
9.2.5.1 Initial Registration............................................................................................................................. 2741
9.2.5.1.1 Initial registration / Success / 5G-GUTI reallocation, Last visited TAI ...................................... 2741
9.2.5.1.2 Initial registration / 5GS services / NSSAI handling ................................................................... 2744
9.2.5.1.3 Void ............................................................................................................................................. 2753
9.2.5.1.4 Initial registration / Rejected / Congestion / Abnormal cases / T3346 ........................................ 2753
9.2.5.2 Mobility Registration ........................................................................................................................ 2757
9.2.5.2.1 Void ............................................................................................................................................. 2757
9.2.5.2.2 Mobility registration update/Change of SMS over NAS capability ............................................ 2757
9.2.6 De-registration ........................................................................................................................................ 2759
9.2.6.1 UE-initiated de-registration ............................................................................................................... 2759
9.2.6.1.1 UE-initiated de-registration / switch off ...................................................................................... 2759
9.2.6.2 Network-initiated de-registration ...................................................................................................... 2763
9.2.6.2.1 Network-initiated de-registration / De-registration for Non-3GPP access / Re-registration
required........................................................................................................................................ 2763
9.2.6.2.2 Network-initiated de-registration / De-registration for Non 3GPP access / Re-registration not
required........................................................................................................................................ 2765
9.2.7 Service request ........................................................................................................................................ 2769
9.2.7.1 Service request / IDLE mode uplink user data transport / Rejected / Restricted service area,
Abnormal / T3517 ............................................................................................................................. 2769
9.2.7.2 Service request / CMM CONNECTED mode/uplink user data transport / Abnormal / T3517 ........ 2773
9.2.8 SMS over NAS ....................................................................................................................................... 2775
9.2.8.1 SMS over NAS / MO SMS over NAS - 5GMM-Idle mode .............................................................. 2775
9.3 Inter-system mobility ................................................................................................................................... 2778
9.3.1 5GS-EPC Inter-system mobility ............................................................................................................. 2778
9.3.1.1 Inter-system mobility registration update / Single-registration mode with N26 / 5GMM-IDLE /
5GC to EPC....................................................................................................................................... 2778
9.3.1.2 Inter-system mobility registration update / Single-registration mode with N26 / 5GMM-IDLE /
EPC to 5GC....................................................................................................................................... 2780
9.3.1.3 Inter-system mobility and periodic registration update / Rejected / Single-registration mode with
N26 / Handling of EPC relevant parameters ..................................................................................... 2784
10 Session management ..........................................................................................................................2787
10.1 5GS session management ............................................................................................................................. 2787
10.1.1 PDU session authentication and authorization........................................................................................ 2787
10.1.1.1 PDU session authentication and authorization / During the UE-requested PDU session procedure . 2787
10.1.1.2 PDU session authentication and authorization / After the UE-requested PDU session procedure.... 2792
10.1.2 Network-requested PDU session modification ....................................................................................... 2798
10.1.2.1 Network-requested PDU session modification / Accepted ............................................................... 2798
10.1.2.2 Network-requested PDU session modification / Abnormal / PDU session in state PDU SESSION
INACTIVE ........................................................................................................................................ 2809
10.1.3 Network-requested PDU session release ................................................................................................ 2812
10.1.3.1 Void................................................................................................................................................... 2812
10.1.3.2 Network-requested PDU session release / Insufficient resources, insufficient resources for
specific slice and DNN, abnormal / Invalid PDU session identity .................................................... 2812
10.1.4 UE-requested PDU session establishment .............................................................................................. 2822
10.1.4.1 UE-requested PDU session establishment / Abnormal / T3580 ........................................................ 2822
10.1.5 UE-requested PDU session modification ................................................................................................ 2826
10.1.5.1 UE-requested PDU session modification .......................................................................................... 2826
10.1.6 UE-requested PDU session release ......................................................................................................... 2828
10.1.6.1 UE-requested PDU session release / Abnormal / Collision with network-requested PDU session
modification procedure ..................................................................................................................... 2828
release procedure............................................................................................................................... 2831
10.2 EN-DC session management ........................................................................................................................ 2834
10.2.1 Network initiated procedures .................................................................................................................. 2834
10.2.1.1 Default EPS bearer context activation............................................................................................... 2834
10.2.1.2 Dedicated EPS bearer context activation .......................................................................................... 2839
10.2.2 UE initiated procedures .......................................................................................................................... 2843
10.2.2.1 EPS bearer resource allocation / modification .................................................................................. 2843
10.3 5GS Non-3GPP Access Session Management ............................................................................................. 2852
ETSI
10.3.1 PDU session authentication and authorization........................................................................................ 2852

10.3.1.1 PDU session authentication and authorization / during the UE-requested PDU session procedure.. 2852
10.3.2 Network-requested PDU session modification ....................................................................................... 2855
10.3.2.1 Network-requested PDU session modification /Accepted/Rejected ................................................. 2855
10.3.3 Network-requested PDU session Release ............................................................................................... 2860
10.3.3.1 Network-requested PDU session release / accepted/ with and without reactivation ......................... 2860
10.3.4 UE-requested PDU session establishment .............................................................................................. 2865
10.3.4.1 UE-requested PDU session establishment / Abnormal / T3580 .................................................. 2865
10.3.5 UE-requested PDU session modification ................................................................................................ 2866
10.3.5.1 UE-requested PDU session modification/Success ............................................................................ 2866
10.3.6 UE-requested PDU session release ......................................................................................................... 2866
modification procedure ..................................................................................................................... 2866
11 Multi-layer and Services ....................................................................................................................2868
11.1 5GS / EPS Fallback ...................................................................................................................................... 2868
11.1.1 MO MMTEL voice call setup from NR RRC_IDLE / EPS Fallback with redirection / Single
registration mode with N26 interface / Success ...................................................................................... 2868
registration mode without N26 interface / Success ................................................................................. 2874
11.1.3 MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with handover / Single
registration mode with N26 interface / Success ...................................................................................... 2887
11.1.4 MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with redirection /
Single registration mode with N26 interface / E-UTRAN cell selection using cell status barred /
Success.................................................................................................................................................... 2896
11.1.5 MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with redirection /
Single registration mode without N26 interface / E-UTRAN cell selection using cell status
reservation / Success ............................................................................................................................... 2908
11.1.6 MT MMTEL voice call setup from NR RRC_IDLE / EPS Fallback with redirection / Single
registration mode without N26 interface / Success ................................................................................. 2919
11.1.7 Emergency call setup from NR RRC_IDLE / Emergency Services Fallback to EPS with redirection /
Single registration mode with N26 interface / Success ........................................................................... 2930
11.1.8 MO MMTEL voice call setup from NR RRC_CONNECTED / EPS Fallback with handover / Single
registration mode with N26 interface / voiceFallbackIndication ............................................................ 2937
registration mode with N26 interface / voiceFallbackIndication ............................................................ 2945
11.2 5G-SRVCC................................................................................................................................................... 2951
11.2.1 5G-SRVCC from NG-RAN to 3GPP UTRAN ....................................................................................... 2951
11.3 Unified Access Control (UAC) .................................................................................................................... 2959
11.3.1 UAC / Access Identity 0 / 0% access probability / MTSI MO speech call/SMSoIP .............................. 2959
11.3.1a UAC / Access Identity 0 / 0% access probability / Uplink User data transfer / RRC_INACTIVE ........ 2970
11.3.2 UAC / Access Identity 0 / 0% access probability / Paging for MT Access/Emergency Call.................. 2981
11.3.3 UAC / Access Identity 0 / AC8 / RRC_INACTIVE / RNAUpdate/RRC Resume ................................. 2993
11.3.4 UAC / Access Identity 0 / Registration procedure for mobility and periodic registration update /
BarringPerPLMN/Implicit AC Barring List ........................................................................................... 2998
11.3.5 UAC / Access Identity 1 / New cell not in the country of its HPLMN/EHPLMN 0% access
probability/MPS indicator / HPLMN/0%/100% accessibility AC5/MMTEL-Video call....................... 3007
11.3.6 UAC / Access Identity 2 / New cell not in the country of its HPLMN/EHPLMN 0% access
probability/MCS indicator / HPLMN/0%/100% accessibility AC7/RRC_INACTIVE.......................... 3020
11.3.7 UAC / Access Identity 11..15 / High Priority Access / HPLMN/0% accessibility AC2/Emergency
call .......................................................................................................................................................... 3034
11.3.8 UAC / Access Identity 0 / NR RRC_IDLE / Cell re-selection while T390 is running ........................... 3043
11.3.9 UAC / Access Identity 0 / ODAC / PLMN / RPLMN / not EPLMN ..................................................... 3053
11.4 Emergency Services ..................................................................................................................................... 3061
11.4.1 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / Utilising
emergency number stored on the USIM / New emergency PDU session / Network failing the
authentication check (5G AKA) ............................................................................................................. 3061
11.4.2 5GMM-DEREGISTERED.LIMITED-SERVICE / Emergency call / Utilisation of emergency
numbers stored on the ME / Initial registration for emergency services / Handling of forbidden
PLMNs.................................................................................................................................................... 3065
11.4.3 5GMM-DEREGISTERED.NO-SUPI / Emergency call / Utilisation of emergency numbers stored on
the ME / Initial registration for emergency services ............................................................................... 3071
ETSI
11.4.4 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE T3346 running / Emergency

call establishment / 5GMM-REGISTERED.NORMAL-SERVICE / Emergency call establishment
before T3396 expiry................................................................................................................................ 3076
11.4.5 5GMM-REGISTERED.LIMITED-SERVICE / 5GMM-IDLE / Emergency call establishment and
release / Handling of 5GS forbidden tracking areas for roaming............................................................ 3081
11.4.6 5GMM-REGISTERED.NON-ALLOWED-SERVICE / Emergency call establishment and release /
Handling of non-allowed tracking areas ................................................................................................. 3084
11.4.7 Handling of Local and Extended emergency numbers / Mobility .......................................................... 3087
11.4.8 Handling of Local and extended emergency numbers / Switch-off and maximum local numbers
storage ..................................................................................................................................................... 3099
11.4.9 5GMM-DEREGISTERED.LIMITED-SERVICE No suitable cells in tracking area / Emergency call
establishment and release........................................................................................................................ 3105
11.4.10 5GMM-REGISTERED.NORMAL-SERVICE / N26 interface not supported / N1 mode to S1 mode
transfer of an existing emergency PDU session...................................................................................... 3110
11.4.11 5GMM-REGISTERED.NORMAL-SERVICE / N26 interface not supported / S1 mode to N1 mode
transfer of an existing emergency PDN connection ................................................................................ 3114
12 NR sidelink.........................................................................................................................................3119
12.1 PC5-only operation....................................................................................................................................... 3119
12.1.1 to 12.1.6 .............................................................................................................................................................. 3119
12.1.7 PC5-only operation / Sidelink UE capability transfer via PC5 RRC ...................................................... 3119
12.1.7.1 PC5-only operation / Sidelink UE capability transfer via PC5 RRC / One-way and two-way
transfer .............................................................................................................................................. 3119
12.2 Inter-carrier concurrent operation................................................................................................................. 3125
12.2.1 Inter-carrier concurrent operation / Sidelink communication ................................................................. 3125
12.2.1.1 3125
12.2.1.2 3125
12.2.1.3 Inter-carrier concurrent operation / Sidelink communication / RRC_CONNECTED /
Transmission / Network scheduling .................................................................................................. 3125
12.2.2 3133
12.2.3 Inter-carrier concurrent operation / Measurement configuration and reporting via Uu RRC ................. 3133
12.2.3.1 Inter-carrier concurrent operation / Measurement configuration and reporting via Uu RRC / CBR
measurement reporting / Event C1 and C2 ....................................................................................... 3133
Annex A (informative): Change history ...........................................................................................3140

History ..........................................................................................................................................................3175
ETSI
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
The present document is part 1 of a multi-part deliverable covering the 5G System (5GS) User Equipment (UE)
protocol conformance specification, as identified below:
- 3GPP TS 38.523-1: "5GS; User Equipment (UE) conformance specification; Part 1: Protocol" (the present
document).
- 3GPP TS 38.523-2 [2]: "5GS; User Equipment (UE) conformance specification; Part 2: Applicability of protocol
test cases".
- 3GPP TS 38.523-3 [3]: "5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test Suites".
ETSI
1 Scope
The present document specifies the protocol conformance testing for the 3GPP UE connecting to the 5G System (5GS)
via its radio interface(s).
The following information can be found in the present document (first part of a multi-part test specification):
- the overall test structure;
- the test configurations;
- the conformance requirement and references 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 applicability of the individual test cases is specified in the ICS proforma specification (3GPP TS 38.523-2 [2]). The
Test Suites are specified in part 3 (3GPP TS 38.523-3 [3]).
The present document is valid for UE implemented according to 3GPP Releases starting from Release 15 up to the
Release indicated on the cover page of the present document.
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.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 38.523-2: "5GS; UE conformance specification; Part 2: Implementation Conformance

Statement (ICS) proforma specification".
[3] 3GPP TS 38.523-3: "5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test
Suites".
[4] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test
environment".
[5] 3GPP TS 38.508-2: "5GS; User Equipment (UE) conformance specification; Part 2: Common
Implementation Conformance Statement (ICS) proforma"
[6] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment (UE)".
[7] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access (E-UTRAN); Common Test Environments for User Equipment (UE)
Conformance Testing".
[8] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Special conformance testing functions for User
Equipment (UE)".
[9] 3GPP TS 38.113: "New Radio (NR); Requirements for support of radio resource management".
ETSI
[10] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".
[11] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification".
[12] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[13] 3GPP TS 36.523-1: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet
Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol conformance
specification".
[14] 3GPP TS 38.212: "NR; Multiplexing and channel coding".
[15] 3GPP TS 38.214: "NR; Physical layer procedures for data".
[16] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1
Standalone".
[17] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2
Standalone".
[18] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[19] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification".
[20] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System ".
[21] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".
[22] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3"
[23] 3GPP TS 38.306: "NR: User Equipment (UE) radio access capabilities"[24] 3GPP TS 38.211:
"NR; Physical channels and modulation".
[25] 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)".
[26] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[27] 3GPP TS 38.322: "NR; Radio Link Control (RLC) protocol specification".
[28] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".
[29] 3GPP TS 36.523-2: " Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet
Core (EPC); User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
[30] 3GPP TS 38.133: " NR; Requirements for support of radio resource management".
[31] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[32] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2)".
[33] 3GPP TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access
Networks (N3AN); Stage 3"
[34] 3GPP TS 23.003: "Numbering, addressing and identification"
[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".
[36] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM)
application".
ETSI
[37] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[38] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[39] GSMA PRD IR.88: "LTE and EPC Roaming Guidelines".
[40] 3GPP TS 27.007: "AT command set for User Equipment (UE)".
[41] 3GPP TS 34.229-5: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE)
conformance specification; Part 5: Protocol conformance specification using 5G System (5GS)".
[42] 3GPP TS 22.101: "Service aspects; Service principles".
[43] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
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], specifications referred to in
the tests' Conformance requirements clauses and the following apply. A term defined in the present document takes
precedence.
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 Symbols
For the purposes of the present document, symbols defined in specifications referred to in the tests' Conformance
requirements clauses and the following apply. A symbol defined in the present document takes precedence.
None.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1]], specifications referred to in the
tests' Conformance requirements clauses and the following apply. An abbreviation defined in the present document
takes precedence.
ICS Implementation Conformance Statement

FFS For Further Study
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.
ETSI
4.1.2 Test interfaces and facilities

Detailed descriptions of the UE test interfaces and special facilities for testing are provided in TS 38.509 [6].
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.
Implicit testing of 5GS requirements may be done also in tests specified in other 3GPP conformance test specifications.
For clarity these are listed below:
- Indication for support of EN-DC: if the UE supports E-UTRA-NR dual connectivity, then the UE shall set the
DCNR bit to "dual connectivity with NR supported" in the UE network capability IE of the ATTACH
REQUEST/TRACKING AREA UPDATE REQUEST message; verified implicitly (the setting of the DCNR bit
to 1) by tests specified in TS 36.523-1 [13].
NOTE 1: It is assumed that an UE supporting EN-DC will support EPS (legacy LTE) and therefore it will be tested
against all relevant legacy LTE 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%" [8], [9]. Additionally, in some of the test cases, presented in TS 38.523-3
[3], HARQ retransmissions are not tolerated, because of characteristics of the test case. In such cases a repetition of test
may be required. Details are FFS.
4.4 Handling of differences between conformance requirements

in different releases of core specifications
The conformance requirements which determine the scope of each test case are explicitly copy-pasted from relevant
core specifications in the especially dedicated for this clause of each test with the title 'Conformance requirements'.
NOTE: When in the copy/pasted text there are references to other specifications the reference numbers will not
match the reference numbers used in the present document. This approach has been taken in order to
allow easy copy and then search for conformance requirements in those specifications.
When differences between conformance requirements in different releases of the cores specifications have impact on
the Pre-test conditions, Test procedure sequence or/and the Specific message contents, the Conformance requirements
related to different releases are specified separately with clear indication of the Release of the spec from which they
were copied.
When there is no Release indicated for a conformance requirement text, this should be understood either as the
Conformance requirements in the latest version of the spec with release = the TC Applicability release (which can be
found in the column 'Release' for the relevant for the test case entry in the tables in TS 38.523-2 [2], subclause 4.1, or,
as the Conformance requirements in the latest version of the spec of the release when the feature was introduced to the
core specs.
ETSI
5 Reference conditions, generic and test procedures,

test parameters
5.1 Reference conditions

The reference environments used by all signalling tests in the present document are specified in TS 38.508-1 [4]. If a
test requires an environment that is different to those specified in TS 38.508-1 [4] then, this shall be specified in the test
itself.
5.2 Generic and test procedures

A set of basic generic procedures for bringing the UE into a specific signalling state, as well as, test procedures
comprising well defined actions after the UE enters a specific state are specified in TS 38.508-1 [4]. These procedures
are used (referred to) in numerous test cases throughout the present document.
5.3 Test parameters

5.3.1 PLMNs
PLMN identifiers such as PLMN1, PLMN2, etc. are used in test cases to associate a cell with an MCC and MNC for
that cell.
Whenever a PLMN identifier is provided explicitly in a test description without explicit MCC and MNC values, the
MCC and MNC values corresponding to the PLMN identifier shall be understood as those specified in TS 36.523-1
[42], Table 6.0.1-1.
If no PLMN is explicitly specified in the test then the PLMN(s) specified for the relevant cell(s) in TS 38.508-1 [4] (NR
cells) or 36.508 [2] (E-UTRA cells) apply. If no PLMN is explicitly specified in the test nor in the TS 38.508-1 [4] (NR
cells) or 36.508 [2] (E-UTRA cells) for the used in the test cell(s) then the PLMN used in the test is the one defined as
PLMN1 in TS 36.523-1 [42], Table 6.0.1-1.
5.3.2 Cells
Cell identifiers such as NR Cell 1 and NGC Cell A (for NR cells), or, Cell 1 and Cell A (for E-UTRA cells). are used in
test cases to associate a cell with various parameters.
Cells used in the tests throughout the present document are defined in TS 38.508-1 [4], subclauses 4.4.2 and 6.3.2.2 for
NR cells, and, TS 36.508 [2], subclauses 4.4.2 and 6.3.2 for E-UTRA cells respectively. Signal levels for signalling
tests are defined in TS 38.508-1 [4], subclause 6.2.2 and TS 36.508 [2], subclause 6.2.2.
Associated with the Cells used in the test cases are a number of parameters e.g. Tracing Area Identifiers (TAIs) such as
TAI-1, TAI-2, etc., specific MCC and MNC values for the simulated PLMN, etc. For Default NAS parameters for
simulated NR cells and Simulated network scenarios for NAS test cases for 5GS these are defined in TS 38.508-1 [4],
subclauses 4.4.2 and 6.3.2.1 respectfully. Similarly such parameters are defined in TS 36.508 [2] for E-UTRA cells.
Whenever a Cell identifier is provided explicitly in a test description without explicit definition of parameters, the
parameters values corresponding to the Cell identifier shall be understood as those specified in TS 38.508-1 [4] or TS
36.523-1 [42] respectively for the cell with that identifier.
Whenever a test in the present document requires cells characteristics, e.g. power level settings, TAIs, MCC/MNC
which differ to those specified in TS 38.508-1 [4] for NR cells or in TS 36.508 [2] for E-UTRA cells then, these shall
be specified explicitly in the test itself.
ETSI
5.3.3 USIM
Default USIM fields and signalling test case specific USIM Configurations are specified in TS 38.508-1 [4], subclause
6.4.
Whenever a test in the present document does not provide an explicit reference to a specific USIM Configurations
specified in TS 38.508-1 [4], subclause 6.4 then, the default parameters specified in TS 38.508-1 [4], subclause 4.8.3
shall be assumed.
Whenever a test in the present document requires specific USIM settings which do not exist in any of the defined USIM
Configurations in TS 38.508-1 [4], it is recommended that a new USIM Configuration is defined and then the
configuration is referred from the test. Defining specific USIM setting within a test definition should be avoided.
5.3.4 Messages and Information Elements (IEs)

Default Messages and IE contents, and where applicable IE fields values, used by the tests defined in the present
document are specified in TS 38.508-1 [4], subclauses 4.6, 4.7 and 4.7A. For messages exchanged on other RAT e.g. E-
UTRAN/EPC these can be found in TS 36.508 [2].
If a test requires a message and/or IE contents and/or IE field value which is different to those specified in TS 38.508-1
[4] then, specific message content shall be specified in the test itself with a derivation path referring to the relevant
default message in TS 38.508-1 [4]. Whenever a specific message content is not explicitly provided in a test then this
shall be understood as the message having exactly the same content as the default message specified in TS 38.508-1 [4].
NOTE: Similar rules apply to messages exchanged on other RATs and defined elsewhere e.g. in TS 36.508 [2].
6 Idle mode and RRC Inactive state operations
6.1 NR idle mode operations

6.1.1 NG-RAN Only 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 in Automatic network selection mode and RPLMN, HPLMN, UPLMN and OPLMN NR cells available
and UE is fitted with a USIM indicating RPLMN should be selected }
ensure that {
when { UE is switched on or return to coverage }
then { UE selects a cell of the RPLMN and UE attempts Registration on the selected cell }
}
(2)
with { UE camped on an NG-RAN VPLMN cell and cells of a higher priority NG-RAN PLMN available }
ensure that {
when { higher priority PLMN search timer T expires }
then { UE selects and camps on a cell of the highest priority PLMN and UE attempts Registration
with mobility on the selected cell }
}
(3)
with { UE in Automatic network selection mode and HPLMN, UPLMN and OPLMN NG-RAN cells available and
UE is fitted with a USIM with Access Technology data files for each PLMN and there are no equivalent
HPLMNs defined}
ETSI
ensure that {
then { UE selects a cell of the highest priority PLMN and UE attempts Registration with mobility
on the selected cell }
}
(4)
with { UE camped on an NR VPLMN cell and cells of a NG-RAN HPLMN available }
ensure that {
then { UE selects and camps on a cell of HPLMN and UE attempts Registration on the selected cell
}
}
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.1. Unless otherwise stated these are Rel-15 requirements.
[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.
NOTE 1: The MS in automatic network selection mode can end the PLMN search procedure once the registered
PLMN or equivalent PLMN is found on an access technology.
NOTE 2: An MS in automatic network selection mode can use location information to determine which PLMNs can
be available in its present location.
EXCEPTION: As an alternative option to this, if the MS is in automatic network selection mode and it finds coverage
of an EHPLMN, the MS may register to that EHPLMN and not return to the registered PLMN or equivalent PLMN. If
the EHPLMN list is not present or is empty, and the HPLMN is available, the MS may register on the HPLMN and not
return to the registered PLMN or equivalent PLMN. The operator shall be able to control by SIM configuration whether
an MS that supports this option is permitted to perform this alternative behaviour.
EXCEPTION: In A/Gb mode an MS with voice capability, shall not search for CPBCCH carriers. In A/Gb mode an MS
not supporting packet services shall not search for CPBCCH carriers.
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. Otherwise, the MS shall use the PLMN selection mode that was used before
switching off.
EXCEPTION: At switch on, if the MS is in manual mode and neither registered PLMN nor PLMN that is equivalent to
it is available but EHPLMN is available, then instead of performing the manual network selection mode procedure of
subclause 4.4.3.1.2 the MS may select and attempt registration on the highest priority EHPLMN. If the EHPLMN list is
not available or is empty and the HPLMN is available, then the MS may select and attempt registration on the HPLMN.
The MS shall remain in manual mode.
NOTE 3: 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.
EXCEPTION: If registration is not possible on recovery from lack of coverage due to the registered PLMN being
unavailable, an MS attached to GPRS services, attached via E-UTRAN or registered via the NG-RAN may, optionally,
continue looking for the registered PLMN for an implementation dependent time.
NOTE 4: An MS attached to GPRS services, attached via E-UTRAN or registered via the NG-RAN should use the
above exception only if one or more PDP contexts, PDN connections or PDU sessions are currently
active.
[TS 23.122, clause 4.4.3.1.1]
ETSI
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) 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.
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.
NOTE 1: For f) and g), the MS in automatic network selection mode can end the PLMN search procedure once the
HPLMN or the highest priority EHPLMN is found on an access technology.
NOTE 2: For i, ii and iii, the MS can use location information to determine which PLMNs can be available in its
present location.
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 3: 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.
ETSI
NOTE 4: 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 5: High quality signal is defined in the appropriate AS specification.
i) In i to v, the MS shall not consider PLMNs where voice service was not possible as PLMN selection candidate,
unless such PLMN is available in GERAN or UTRAN or no other allowed PLMN is available.
j) In i to v, if the MS only supports EMM-REGISTERED without PDN connection (see TS 24.301 [23A]), the MS
shall not consider PLMNs which do not advertise support of EMM-REGISTERED without PDN connection.
k) In i to v, if the MS only supports control plane CIoT EPS optimization (see TS 24.301 [23A]) and the UE camps
on a E-UTRA cell which is not NB-IoT cell (see TS 36.304 [43], TS 36.331 [22]), the MS shall not consider
PLMNs which do not advertise support of EPS services with control plane CIoT EPS optimization.
l) In i to v, if the MS is in eCall only mode, the MS shall not consider PLMNs which do not advertise support for
eCall over IMS, unless such PLMNs are available in GERAN or UTRAN.
NOTE 6: As an implementation option, an MS in eCall only mode that was not able to select any PLMN according
to l) can perform a second iteration of i to v with no restriction.
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 location areas for roaming", "forbidden tracking areas for
roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service",
"forbidden tracking areas for regional provision of service" or "5GS forbidden tracking areas for regional provision of
service" prevented a registration attempt, the MS selects the first such PLMN again and enters a limited service state.
[TS 23.122, clause 4.4.3.3.1]
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 subclause 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 of timer T may be stored in the SIM. The interpretation of the
stored value depends on the radio capabilities supported by the MS:
- For an MS that does not support any of the following: EC-GSM-IoT, Category M1 or Category NB1 (as defined
in TS 36.306 [54]), 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 for T is stored in the SIM, a default value of 60 minutes is used for T.
- For an MS that only supports any of the following or a combination of: EC-GSM-IoT, Category M1 or Category
NB1 (as defined in TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using 2 hour steps from
2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no periodic attempts shall be
made. If no value for T is stored in the SIM, a default value of 72 hours is used.
- For an MS that supports both:
a) any of the following or a combination of: EC-GSM-IoT, Category M1 or Category NB1 (as defined in
3GPP TS 36.306 [54]); and
b) any access technology other than the following: EC-GSM-IoT, Category M1 or Category NB1 (as defined in
3GPP TS 36.306 [54]),
then T is interpreted depending on the access technology in use as specified below:
1) if the MS is using any of the following at the time of starting timer T: EC-GSM-IoT, Category M1 or
Category NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using
2 hour steps from 2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no
ETSI
periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 72 hours is used;
and
2) if the MS is not using any of the following at the time of starting timer T: EC-GSM-IoT, Category M1 or
Category NB1 (as defined in 3GPP TS 36.306 [54]), 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 for T is stored in the
SIM, a default value of 60 minutes is used for T.
If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or

3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the
value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the
MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer.
The MS does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates
power saving mode (PSM) (see 3GPP TS 23.682 [27A]).
The MS can be configured for Fast First Higher Priority PLMN search as specified in 3GPP TS 31.102 [40] or
3GPP TS 24.368 [50]. Fast First Higher Priority PLMN search is enabled if the corresponding configuration parameter
is present and set to enabled. Otherwise, Fast First Higher Priority PLMN search is disabled.
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, and not while the
MS is attached for emergency bearer services, is registered for emergency services, has a PDU session for
emergency services or has a PDN connection for emergency bearer services;
b) The MS shall make the first attempt after a period of at least 2 minutes and at most T minutes:
- only after switch on if Fast First Higher Priority PLMN search is disabled; or
- after switch on or upon selecting a VPLMN if Fast First Higher Priority PLMN search is enabled.
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;
d1) Periodic attempts may be postponed while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]).
d2) Periodic attempts may be postponed while the MS is receiving eMBMS transport service in idle mode (see
3GPP TS 23.246 [68]).
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) Only the priority levels of Equivalent PLMNs of the same country as the current serving VPLMN, as defined in
Annex B, shall be taken into account to compare with the priority level of a selected PLMN.
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.
6.1.1.1.3 Test description
6.1.1.1.3.1 Pre-test conditions
System Simulator:
- Four multi-PLMN NR Cells as specified in TS 38.508-1 [4] Table 4.4.2.1 are configured broadcasting PLMNs
as indicated in Table 6.1.1.1.3.1-1.
ETSI
- The PLMNs are identified in the test by the identifiers in Table 6.1.1.1.3.1-1 and the PLMN settings are defined
in TS 36.523-1 [13] table 6.0.1-1.
Table 6.1.1.1.3.1-1: PLMN identifiers

NR Cell PLMN name
1 PLMN1
12 PLMN15
13 PLMN16
2 PLMN17
All NR cells are high quality
All NR cells are suitable cells;
System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells
UE:
The UE is in Automatic PLMN selection mode.
The UE is registered to PLMN1 before it is switched off.
USIM configuration as defined in TS 38.508-1 [4] Table 6.4.1-1 will be loaded except for PLMN identifiers in
Table 6.1.1.1.3.1-1.
Preamble:
- The UE is made to camp on NR Cell 12 and then Switched OFF (State 0N-B) as defined in TS 38.508-1 [4]
Table 4.4A.2-0
6.1.1.1.3.2 Test procedure sequence
Table 6.1.1.1.3.2-1 for FR1 and Table 6.1.1.1.3.2-2 for FR2 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 preamble, while columns marked "T1", "T2" and "T3" are to be applied subsequently in the Main
behaviour. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 6.1.1.1.3.2-1: Cell configuration changes over time for FR1

Parameter Unit NR Cell NR Cell NR Cell NR Cell Remarks
1 12 13 2
T0 SS/PBCH dBm/SCS "Off" -88 "Off" "Off" Power level “Off” is
SSS EPRE defined in TS 38.508-1
Table 6.2.2.1-3
T1 SS/PBCH dBm/SCS -88 -88 -88 "Off" Power level “Off” is
Table 6.2.2.1-3
T2 SS/PBCH dBm/SCS "Off" -88 -88 "Off" Power level “Off” is
Table 6.2.2.1-3
T3 SS/PBCH dBm/SCS "Off" -88 -88 -88 Power level “Off” is
Table 6.2.2.1-3
ETSI

1 12 13 2
T0 SS/PBCH dBm/SCS “Off” [-85] “Off” “Off” Power level “Off” is
Table 6.2.2.1-3
T1 SS/PBCH dBm/SCS [-85] [-85] [-85] ”Off” Power level “Off” is
Table 6.2.2.1-3
T2 SS/PBCH dBm/SCS “Off” [-85] [-85] “Off” Power level “Off” is
Table 6.2.2.1-3
T3 SS/PBCH dBm/SCS “Off” [-85] [-85] [-85] Power level “Off” is
Table 6.2.2.1-3
ETSI
Table 6.1.1.1.3.2-2: Main behaviour
ETSI
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 for FR1 and table
6.1.1.1.3.2-2 for FR2
2 Power on the UE. - - - -
3 Check: Does the UE send a --> RRCSetupRequest 1 P
RRCSetupRequest on NR Cell 12?
4- Steps 3 to 20a1 of the registration procedure - - - -
21 described in TS 38.508-1 subclause 4.5.2.2-2
are performed on NR Cell 12.
NOTE: The UE performs registration and the
RRC connection is released.
RRCSetupRequest on NR Cell 1 after 120
seconds, but before 660seconds (Note 1 and
2) from power on?
22 Steps 3-4 of Table 4.5.2.2-2 of the generic - - - -
A- procedure in TS 38.508-1 [4] are performed.
22 (Note 3)
B
- EXCEPTION: Steps 23a1 to 23b5a1 describe - - - -
behaviour that depends on events happening
prior to their execution; the "lower case letter"
identifies a step sequence that take place if a
specific prior event takes place.
23a IF 5GS registration type is set as Initial - - - -
1- Registration in step 22B, THEN Steps 5 to
23a 20a1of the generic test procedure in TS
16a 38.508-1 Table 4.5.2.2-2 are performed on NR
1 Cell 1.
23b Void - - - -
1-
23b
2
23b IF 5GS registration type is set as Mobility - - - -
3- Registration in step 22B, THEN Steps 4 to 6a1
23b of the generic test procedure in TS 38.508-1
5a1 Table 4.9.5.2.2-1 are performed on NR Cell 1.
24- Void - - - -
27
6.1.1.1.3.2-2 for FR2
29 (Note 3)
B
1 Cell 13.
29b Void. - - - -
1-
29b
2
ETSI

5a1 Table 4.9.5.2.2-1 are performed on NR Cell
13.
6.1.1.1.3.2-2 for FR2
seconds, but before 660 seconds after step
30? (Note 1 and 2)
31 (Note 3)
B
1 Cell 2.
32b Void - - - -
1-
32b
2
5a1 Table 4.9.5.2.2-1 are performed on NR Cell 2.
33- Void - - - -
36
Note 1: Following attempts to access the HPLMN/EHPLMN/higher priority PLMN in VPLMN is operator specific
setting (Refer to TS 23.122 Rel-15).Hence, window between 120s to T+Tolerance is being used, where the
high priority PLMN search timer T defined by EFHPPLMN.
Note 2: Tolerance of 5min is added to allow time for the UE to find the proper PLMN.
Note 3: The 5GS registration type shall be only set as Mobility Registration for R16 UEs according to TS 24.501
subclause 5.2.3.2.5 specified in Release 16. The EXCEPTION description applies only to R15 UEs.
6.1.1.1.3.3 Specific message contents
None
6.1.1.2 PLMN selection of "Other PLMN/access technology combinations" /

Automatic mode
(1)
with { UE in Automatic network selection mode and EHPLMN, UPLMN and OPLMN/access technology
combinations cells available and UE is fitted with a USIM with Access Technology data files for each
PLMN }
ensure that {
then { UE selects a cell of the EHPLMN and UE attempts a Registration on the selected cell }
}
ETSI
(2)
with { UE in Automatic network selection mode and UPLMN, OPLMN and other PLMN/access technology
PLMN }
ensure that {
then { UE selects a cell of the UPLMN and UE attempts a Registration on the selected cell }
}
(3)
with { UE in Automatic network selection mode and OPLMN and other PLMN/access technology
PLMN }
ensure that {
then { UE selects a cell of the OPLMN and UE attempts a Registration on the selected cell }
}
(4)
with { UE in Automatic network selection mode and other PLMN/access technology combinations cells
not belonging to any of EHPLMN, UPLMN or OPLMN available }
ensure that {
then { UE selects a cell of other PLMN/access technology combinations and UE attempts a
Registration on the selected cell }
}
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.4.3.1.1.
Unless otherwise stated these are Rel-15 requirements.
[TS 23.122, clause 4.4.3.1.1]
COMPACT.
ETSI
select.
access technology.
present location.
j) In i to v, if the MS only supports EMM-REGISTERED without PDN connection (see 3GPP TS 24.301 [23A]),
the MS shall not consider PLMNs which do not advertise support of EMM-REGISTERED without PDN
connection.
k) In i to v, if the MS only supports control plane CIoT EPS optimization (see 3GPP TS 24.301 [23A]) and the UE
camps on a E-UTRA cell which is not NB-IoT cell (see 3GPP TS 36.304 [43], 3GPP TS 36.331 [22]), the MS
shall not consider PLMNs which do not advertise support of EPS services with control plane CIoT EPS
optimization.
ETSI
System Simulator:
- Four inter-frequency multi-PLMN cells as specified in TS 38.508-1 [4] clause 4.4.1.1.3 are configured
broadcasting default PLMNs as indicated in TS 38.508-1 [4] Table 4.4.2-3.
- The PLMNs are identified in the test by the identifiers in Table 6.1.1.2.3.1-1.

NR Cell PLMN name
1 PLMN1
12 PLMN2
13 PLMN3
11 PLMN4
UE:
- The UE is in Automatic PLMN selection mode.
- The UE is equipped with a USIM configuration as defined in TS 38.508-1 [4] Table 6.4.1-4.
Preamble:
- The UE is in state Switched OFF (state 0-A).
Table 6.1.1.2.3.2-1/2 shows the cell configurations used during the test. Subsequent configurations marked “T1”, “T2”
“T3” “T4”etc are applied at the points indicated in the Main behaviour description in Table 6.1.1.2.3.2-3. Cell powers
are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and
Table 6.2.2.2-2 for FR2.
ETSI
Table 6.1.1.2.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter Unit NR NR NR NR Remarks
Cell 1 Cell 12 Cell 13 Cell 11
T1 SS/PBCH dBm/SCS -88 -88 -88 “Off” Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.1-
3.
T2 SS/PBCH dBm/SCS “Off” -88 -88 -88 Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.1-
3.
T3 SS/PBCH dBm/SCS “Off” “Off” -88 -88 Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.1-
3.
T4 SS/PBCH dBm/SCS “Off” “Off” “Off” -88 Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.1-
3.
Parameter Unit NR NR NR NR Remarks

T1 SS/PBCH dBm/SCS -82 -82 -82 “Off” Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.2-
2.
T2 SS/PBCH dBm/SCS “Off” -82 -82 -82 Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.2-
2.
T3 SS/PBCH dBm/SCS “Off” “Off” -82 -82 Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.2-
2.
T4 SS/PBCH dBm/SCS “Off” “Off” “Off” -82 Power level “Off” is defined in
SSS EPRE TS 38.508-1 [4] Table 6.2.2.2-
2.
ETSI

U-S Message
table 6.1.1.2.3.2-1/2.
3 Check: Does the UE send an --> NR RRC: RRCSetupRequest 1 P
21 described in TS 38.508-1 [4] subclause 4.5.2.2
RRC connection is not released.
21 The UE is switched off by executing generic - - - -
A procedure in Table 4.9.6.3-1 in TS 38.508-1 [4]
table 6.1.1.2.3.2-1/2.
22 Void - - - -
A
22 The UE is Switched ON. - - - -
B
23 Check: Does the test result of generic test --> - 2 P
procedure in TS 38.508-1 [4] Table 4.5.2.2-2
indicate that the UE is camped on NR Cell 12?
24- Void - - - -
27b
1
procedure in Table 4.9.6.3-1 in TS 38.508-1
[4].
table 6.1.1.2.3.2-1/2.
29 Void. - - - -
A
B
31- Void. - - - -
34b
1
35 The UE is switched off by executing generic
procedure in Table 4.9.6.3-1 in TS 38.508-1 [4]
table 6.1.1.2.3.2-1/2.
36 Void. - - - -
A
B
38- Void. - - - -
42b
1
None
ETSI
6.1.1.3 Cell reselection of ePLMN in manual mode
(1)
with { UE camped normally on a cell and network has downloaded a list of equivalent PLMNs during the
Registration procedure }
ensure that {
when { Higher ranked cell is a cell of a PLMN in the downloaded equivalent PLMN list }
then { UE reselects to the equivalent PLMN cell }
}
(2)
with { UE camped normally on a cell and network has downloaded a list of equivalent PLMNs during
Registration procedure for mobility }
ensure that {
when { Highest ranked cell is a cell of a PLMN not in the downloaded equivalent PLMN list }
then { UE does not reselect to the cell }
}
References: The conformance requirements covered in the current TC are specified in: TS 23.122, clauses 4.4.3.1.2.
[TS 23.122, clause 4.4.3.1.2]
COMPACT.
select.
ETSI
access technology.
present location.
connection.
optimization.
ETSI
System Simulator
- Three inter-frequency multi-PLMN NR cells.
- Each NR cell has only a single PLMN identity. The PLMNs are identified in the test by the identifiers in Table
6.1.1.3.3.1-1.

NR Cell PLMN name
1 PLMN1
12 PLMN2
13 PLMN3
- System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cell 1 and
NR cell 12.
- System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cell 13.
UE
- The UE is in Manual PLMN selection mode.
Preamble
- The UE is registered on PLMN1 (NR Cell 1) using the procedure described in TS 38.508-1 [4] clause 4.5.2.2-2
except that the REGISTRATION ACCEPT message indicates PLMN2 in the Equivalent PLMN list as described
in Table 6.1.1.3.3.3-3.
- The UE is in state Registered, Idle Mode (state 1N-A) on NR Cell 1 according to TS 38.508-1 [4];
Parameter Unit NR NR NR Remarks
Cell 1 Cell 12 Cell 13
T1 SS/PBCH dBm/SCS -99 -88 -78
SSS EPRE
T2 SS/PBCH dBm/SCS "Off" "Off" "Off" Power level "Off" is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3
T1 SS/PBCH dBm/SCS FFS FFS FFS
SSS EPRE
T2 SS/PBCH dBm/SCS "Off" "Off" "Off" Power level "Off" is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.2-2
ETSI

U-S Message
1 SS adjusts cell levels according to row T1 of -
- - -
table 6.1.1.3.3.2-1/2.
2 Check: Does the test result of generic test - - 1 -
procedure in TS 38.508-1 [4] subclause
4.9.5.2.2-1 indicate that the UE is camped on
NR Cell 12?
NOTE: The REGISTRATION REQUEST is
accepted with PLMN1 listed as an Equivalent
PLMN.
3 Check: Does the UE send an --> NR RRC: RRCSetupRequest 2 F
RRCSetupRequest on NR Cell 13 within 60s?
table 6.1.1.3.3.2-1/2.
5 Set UE to Automatic PLMN selection mode. - - - -
(Note 1)
Note 1: Step 5 is to ensure UE is set back to automatic PLMN selection mode for the next test case.
Table 6.1.1.3.3.3-1: SIB4 for NR Cell 1 (preamble and all steps, Table 6.1.1.3.3.2-3)
Derivation path: TS 38.508-1 [4] Table 4.6.2-3

Information Element Value/Remark Comment Condition
SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE 2 entries
(1..maxFreq)) OF InterFreqCarrierFreqInfo {
InterFreqCarrierFreqInfo[1] SEQUENCE { entry 1
dl-CarrierFreq Same downlink NR
ARFCN as used for NR
Cell 12
cellReselectionPriority 4
}
Cell 13
}
}
}
ETSI

SIB4 ::= SEQUENCE {
(1..maxFreq)) OF nterFreqCarrierFreqInfo {
Cell 1
}
Cell 13
}
}
}
Table 6.1.1.3.3.3-3: REGISTRATION ACCEPT for NR Cell 1 (preamble)

Equivalent PLMNs PLMN2 NR Cell 1
Table 6.1.1.3.3.3-4: REGISTRATION ACCEPT for NR Cell 12 (step 2, Table 6.1.1.3.3.2-3)

Equivalent PLMNs PLMN1 NR Cell 12
Allowed NSSAI
S-NSSAI
Length of S-NSSAI contents ‘0000 0010’B
Mapped HPLMN SST Same as SST
6.1.1.4 PLMN selection in shared network environment / Automatic mode
(1)
with { The UE is in automatic network selection mode and there is a suitable cell with multiple PLMN
identities among which the HPLMN but not the registered PLMN }
ensure that {
when { the UE is switched on }
then { the UE attaches to the HPLMN on the shared cell }
}
(2)
with { the UE in automatic network selection mode and there is a suitable cell with multiple PLMN
identities among which the registered PLMN }
ensure that {
when { the UE returns to coverage }
then { the UE performs a registration procedure due to mobility to the registered PLMN on the
shared cell }
}
ETSI
References: The conformance requirements covered in the current TC are specified in: TS 38.304 clause 5.1.1.2, TS
23.122 clauses 4.4.3 and 4.4.3.1.1, TS 38.331 clauses 5.3.3.4, and TS 24.501 clause 5.3.1.1. Unless otherwise stated
these are Rel-15 requirements.
[TS 38.304 clause 5.1.1.2]
The UE shall scan all RF channels in the NR 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 TS 38.331 [3]) shall be reported to the NAS as a high quality PLMN,
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 clauses 4.4.3]
When the MS reselects to a cell in a shared network, and the cell is a suitable cell for multiple PLMN identities received
on the BCCH or on the EC-BCCH the AS indicates these multiple PLMN identities to the NAS according to
3GPP TS 44.018 [34], 3GPP TS 44.060 [39], 3GPP TS 25.304 [32] and 3GPP TS 36.304 [43]. 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.
The MS shall not use the PLMN codes contained in the "HPLMN Selector with Access Technology" data file.
It is possible for the home network operator to identify alternative Network IDs as the HPLMN. If the EHPLMN list is
present, and not empty, the entries in the EHPLMN list are used in the network selection procedures. When attempting
to select a network the highest priority EHPLMN that is available shall be selected. If the EHPLMN list is present and
is empty or if the EHPLMN list is not present, the HPLMN derived from the IMSI is used for network selection
procedures.
NOTE 1: The "HPLMN Selector with Access Technology" data file is only used by the MS to get the HPLMN
access technologies related to the HPLMN code which corresponds to the PLMN code included in the
IMSI if the EHPLMN list is not present or is empty. If the EHPLMN list is present then this data field is
applicable to all the entries within the EHPLMN list.
NOTE 2: Different GSM frequency bands (e.g. 900, 1800, 1900, 400) are all considered GSM access technology.
An MS supporting more than one band should scan all the bands it’s supports when scanning for GSM
frequencies. However GSM COMPACT systems which use GSM frequency bands but with the CBPCCH
broadcast channel are considered as a separate access technology from GSM.
NOTE 3: The inclusion of the HPLMN derived from the IMSI in the EHPLMN list is allowed. The priority of the
HPLMN derived from the IMSI is given by its position in the EHPLMN list, see 3GPP TS 31.102 [40]
[TS 23.122 clause 4.4.3.1.1]
ETSI
COMPACT.
select.
access technology.
present location.
connection.
ETSI
optimization.
[TS 38.331 clause 5.3.3.4]
The UE shall perform the following actions upon reception of the RRCSetup:
...
1> set the content of RRCSetupComplete message as follows:
2> if upper layers provide an 5G-S-TMSI:
3> if the RRCSetup is received in response to an RRCSetupRequest:
4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI-Part2;
3> else:
4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI;
2> set the selectedPLMN-Identity to the PLMN selected by upper layers (TS 24.501 [23]) from the PLMN(s)
included in the plmn-IdentityList in SIB1;
...
1> submit the RRCSetupComplete message to lower layers for transmission, upon which the procedure ends
[TS 24.501 clause 5.3.1.1]
The UE NAS also provides the lower layers with the identity of the selected PLMN (see 3GPP TS 38.331 [30]). In a
shared network, the UE shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [5].
System Simulator:
- NR Cells 1 and 2, as specified in TS 38.508-1 [4] clause 4.4.1.1.3 are configured according to Table 4.4.2-3 in
TS 38.508-1 [4] except for multiple broadcasted PLMN identities as shown in Table 6.1.1.4.3.1-1: PLMN
identifiers broadcasted by cells in shared network, and NR Cells 1 and 2 with different tracking area codes as
shown in Table 6.1.1.4.3.1-2.
ETSI

NR Cell PLMN names
1 PLMN4 (for preamble)
PLMN15, PLMN1 (for test body)
2 PLMN15, PLMN1, PLMN16
Table 6.1.1.4.3.1-2: Tracking area codes

NR Cell TAC TAI
1 1 TAI-1
2 2 TAI-2
UE:
- The UE is registered to PLMN4 before it is switched off.
Preamble:
- The UE is in state Switched OFF (state 0N-B) according to TS 38.508-1 [4].
Table 6.1.1.4.3.2-1/2 shows the cell configurations used during the test. The configuration T0 indicates the initial
conditions. Subsequent configuration marked “T1”is applied at the points indicated in the Main behaviour description in
Table 6.1.1.4.3.2-2. Cell powers are chosen for a serving cell and a non-suitable cell as defined in TS 38.508-1 [4]
Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Parameter Unit NR NR Remarks
Cell 1 Cell 2
T0 SS/PBCH dBm/SCS -88 “Off” Power level “Off” is defined in TS 38.508-1 [4] Table
SSS EPRE 6.2.2.1-3,
T1 SS/PBCH dBm/SCS “Off” “Off” Close the NR Cell 1 to make sure the UE lose
SSS EPRE coverage. Power level “Off” is defined in TS 38.508-1
[4] Table 6.2.2.1-3,
T2 SS/PBCH dBm/SCS “Off” -88 Power level “Off” is defined in TS 38.508-1 [4] Table
SSS EPRE 6.2.2.1-3,
Parameter Unit NR NR Remarks
Cell 1 Cell 2
T0 SS/PBCH dBm/SCS -95 “Off” Power level “Off” is defined in TS 38.508-1 [4] Table
SSS EPRE 6.2.2.2-2.
T1 SS/PBCH dBm/SCS “Off” “Off” Close the NR Cell 1 to make sure the UE lose
SSS EPRE coverage.
Power level “Off” is defined in TS 38.508-1 [4] Table
6.2.2.2-2.
T2 SS/PBCH dBm/SCS “Off” -95 Power level “Off” is defined in TS 38.508-1 [4] Table
SSS EPRE 6.2.2.2-2.
ETSI

U-S Message
1 The SS adjusts cell levels according to row T0 - - - -
of table 6.1.1.4.3.2-1/2.
3 Check: Does the UE transmit an --> NR RRC: RRCSetupRequest 1 P
4 The SS transmits an RRCSetup message. <-- NR RRC: RRCSetup - -
5 Check: Does the UE transmit an --> NR RRC: RRCSetupComplete 1 P
RRCSetupComplete message indicating the
HPLMN (second PLMN in the list)?
Note: This message contains an
REGISTRATION REQUEST message
according to default message contents.
6- Steps 5 to 20 of the registration procedure - - - -
21 described in TS 38.508-1 [4] subclause
4.5.2.2-2 are performed on NR Cell 1.
of table 6.1.1.4.3.2-1/2 to ensure UE to lose
coverage.
23 Wait for 15s to allow UE to go out of service - - - -
of table 6.1.1.4.3.2-1/2.
26 SS transmits an RRCSetup message. <-- NR RRC: RRCSetup - -
27- Steps 2 to 6b1 of the generic test procedure in - - - -
31b TS 38.508-1 [4] subclause 4.9.5.2.2-1 are
1 performed on NR Cell 2.
NOTE: The UE performs a registration for
mobility procedure and the RRC connection is
released.
Table 6.1.1.4.3.3-1: SIB1 for NR Cell 1 (all steps, Table 6.1.1.4.3.2-1)
Derivation Path: 38.508-1 [4] Table 4.6.1-28

Information Element Value/remark Comment Condition
SIB1 ::= SEQUENCE {
CellAccessRelatedInfo SEQUENCE {
PLMN-IdentityInfoList SEQUENCE (SIZE 1 entry
(1..maxPLMN)) OF PLMN-IdentityInfo {
PLMN-IdentityInfo[1] SEQUENCE { entry 1
plmn-IdentityList SEQUENCE (SIZE 2 entries
(1..maxPLMN)) OF PLMN-Identity {
plmn-Identity[1] PLMN15 entry 1
}
}
}
}
}
ETSI

SIB1 ::= SEQUENCE {
}
}
}
}
}
Table 6.1.1.4.3.3-3: RRCSetupComplete (step 5 and 27, Table 6.1.1.4.3.2-2)
Derivation Path: 38.508-1 [4], Table 4.6.1-22

RRCSetupComplete ::= SEQUENCE {
criticalExtensions CHOICE {
rrcSetupComplete SEQUENCE {
selectedPLMN-Identity 2 PLMN1
}
}
}
6.1.1.5 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /

Automatic mode / User reselection
(1)
with { UE in Automatic network selection mode registered to UPLMN and RPLMN, UPLMN and OPLMN NG-RAN
cells available }
ensure that {
when { UE is requested to initiate reselection and registration onto an available PLMN }
then { UE reselects to the cell which belongs to higher priority OPLMN }
}
(2)
with { UE in Automatic network selection mode registered to OPLMN and only RPLMN NG-RAN cells
available }
ensure that {
then { UE remains on the current cell which belongs to RPLMN }
}
(3)
with { UE in Automatic network selection mode registered to OPLMN and RPLMN, UPLMN and OPLMN NG-RAN
cells available }
ensure that {
then { UE reselects to the cell which belongs to UPLMN }
}
ETSI
(4)
with { UE in Automatic network selection mode registered to UPLMN and RPLMN, UPLMN, OPLMN and HPLMN
NG-RAN cells available }
ensure that {
then { UE reselects to the cell which belongs to HPLMN }
}
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.4.3.2 and
4.4.3.2.1. Unless otherwise stated these are Rel-15 requirements.
[TS 23.122, clause 4.4.3.2]
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 PLMN/access technology combinations, 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.
When following the above procedure the requirements a), b), c), e), f), g), h), j), k) and l) in subclause 4.4.3.1.1 apply:
Requirement d) shall apply as shown below:
d) In iv, v, and vi, the MS shall search for all access technologies it is capable of before deciding which
PLMN/access technology combination to select.
ETSI
System Simulator:
- Four inter-frequency multi-PLMN cells as specified in TS 38.508-1 [4] clause 4.4.1.2 are configured
broadcasting default NAS parameters as indicated in TS 38.508-1 [4] Table 4.4.2-3.

NR Cell PLMN name
1 PLMN1
12 PLMN2
3 PLMN3
13 PLMN4
UE:
Preamble:
- The UE is in state Registered, Idle Mode (state 1N-A) on NR Cell 1 according to TS 38.508-1 [4].
Parameter Unit NR NR NR NR Remark

The power level values are
SS/PBCH assigned to satisfy RNRCell 1 = RNRCell
T1 dBm/ SCS -88 -88 "Off" -88
SSS EPRE 12 = RNRCell 13.
(NOTE 1).
SS/PBCH
T2 dBm/ SCS "Off" -88 "Off" "Off"
SSS EPRE
T3 dBm/ SCS -88 "Off" -88 -88
(NOTE 1).
NOTE 1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3.
ETSI
T1 dBm/ SCS FFS FFS "Off" FFS
(NOTE 1).
SS/PBCH
T2 dBm/ SCS "Off" FFS "Off" "Off"
SSS EPRE
T3 dBm/ SCS FFS "Off" FFS FFS
(NOTE 1).
ETSI
ETSI

U-S Message
1 The SS changes the power level setting - - - -
according to the row “T1” in table 6.1.1.5.3.2-
1/2.
2 Cause the UE in Automatic network selection - - - -
mode to initiate user reselection and
registration onto an available PLMN. (Note 1)
3A- Steps 3-4 of Table 4.5.2.2-2 of the generic - - - -
3B procedure in TS 38.508-1 [4] are performed.
(Note 2)
4a1- IF 5GS registration type is set as Initial - - - -
4a16 Registration in step 3B, THEN Steps 5 to
a1 20a1of the generic test procedure in TS
38.508-1 Table 4.5.2.2-2 are performed on NR
Cell 12.
4b1- Void - - - -
4b2
4b3- IF 5GS registration type is set as Mobility - - - -
4b5a Registration in step 3B, THEN Steps 4 to 6a1
1 of the generic test procedure in TS 38.508-1
Table 4.9.5.2.2-1 are performed on NR Cell
12.
5-8 Void - - - -
1/2.
RRCSetupRequest on NR Cell 12 within 90 s?
1/2.
(Note 2)
15a1 IF 5GS registration type is set as Initial - - - -
- Registration in step 14B, THEN Steps 5 to
15a1 20a1of the generic test procedure in TS
6a1 38.508-1 Table 4.5.2.2-2 are performed on NR
Cell 1.
151- Void - - - -
15b2
15b3 IF 5GS registration type is set as Mobility - - - -
- Registration in step 14B, THEN Steps 4 to 6a1
15b5 of the generic test procedure in TS 38.508-1
a1 Table 4.9.5.2.2-1 are performed on NR Cell 1.
ETSI
16- Void - - - -
19
1/2.
(Note 2)
23a1 IF 5GS registration type is set as Initial - - - -
- Registration in step 22B, THEN Steps 5 to
23a1 20a1of the generic test procedure in TS
6a1 38.508-1 Table 4.5.2.2-2 are performed on NR
Cell 3.
23b1 Void - - - -
-
23b2
23b3 IF 5GS registration type is set as Mobility - - - -
- Registration in step 22B, THEN Steps 4 to 6a1
23b5 of the generic test procedure in TS 38.508-1
a1 Table 4.9.5.2.2-1 are performed on NR Cell 3.
24- Void - - - -
27
Note 1: MMI command “TRIGGER_USER_RESELECTION” to be used. AT command AT+COPS is not suitable to
achieve the test purpose.
None
6.1.1.6 PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer
(1)
with { UE configured with “MinimumPeriodicSearchTimer” }
ensure that {
when { UE camps on an NG-RAN VPLMN cell upon switch on and cells of a higher priority NG-RAN PLMN
available }
then { the MS shall make the first attempt to access the HPLMN or an EHPLMN or higher priority
PLMN after a period of at least 2 minutes }
}
(2)
with { UE configured with “MinimumPeriodicSearchTimer”, having made first attempt to higher priority
PLMN and camped on an NG-RAN VPLMN cell and cells of a higher priority NG-RAN PLMN available }
ensure that {
when { the higher priority PLMN search timer T stored in the USIM or the default value for T is
less than the “MinimumPeriodicSearchTimer” }
then { UE shall not use a value for T that is less than the “MinimumPeriodicSearchTimer” and
selects and camps on a cell of the highest priority PLMN and attempts a location registration on the
selected cell upon expiry of “MinimumPeriodicSearchTimer” }
}
ETSI
References: The conformance requirements covered in the present test case are specified in: TS 23.122, clause 4.4.3.3.1
[TS 23.122, clause 4.4.3.3.1]

power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or mobile initiated connection only mode (MICO) as described
in 3GPP TS 24.501 [64].
6.1.1.6.3 Test Description
System Simulator:
- 3 NR cells: NR Cell 11, 12 and 13 as specified in TS 38.508-1 [4] table 4.4.2-3 are configured as shown in Table
6.1.1.6.3.1–1.
- PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.

NR Cell PLMN names
NR Cell 11 PLMN1
NR Cell 12 PLMN15
NR Cell 13 PLMN16
UE:
- The UE is configured with a value of MinimumPeriodicSearchTimer set to 7 minutes.
- The UE is equipped with a USIM configuration 11 as per TS 38.508-1 [4] Table 6.4.1-11.
ETSI
Preamble:
- The UE performs a successful registration on PLMN15 after which it is switched OFF (State 0N-B) as per TS
38.508-1 [4] table 4.4A.2-0.
Table 6.1.1.6.3.2-1 and Table 6.1.1.6.3.2-2 shows the cell configurations used during the test. The configuration T0
indicates the initial conditions. Subsequent configurations marked “T1” & “T2” are applied at the point indicated in the
Main behaviour description in Table 6.1.1.6.3.2-3. Cell powers are chosen for a serving cell and a non-suitable "Off"
cell as defined in TS 38.508-1 [4] table 6.2.2.1-3.
Parameter Unit NR Cell NR Cell NR Cell Remark
11 12 13
SS/PBCH dBm/SC Off -88 Off
T0
SSS EPRE S
SS/PBCH dBm/SC Off -88 -88
T1
SSS EPRE S
SS/PBCH dBm/SC -88 -88 -88
T2
SSS EPRE S
11 12 13
SS/PBCH dBm/SC Off -82 Off
T0
SSS EPRE S
Qrxlevmin dBm - -91+ -
Delta(N
Rf2)
SS/PBCH dBm/SC Off -82 -82
T1
SSS EPRE S
- -91+ -91+
Qrxlevmin Delta(N Delta(NRf
Rf2) 3)
SS/PBCH dBm/SC -82 -82 -82
T2
SSS EPRE S
-91+ -91+ -91+
Qrxlevmin Delta(N Delta(N Delta(NRf
Rf1) Rf2) 3)
ETSI
ETSI

U-S Message
table 6.1.1.6.3.2-1/2.
22a described in TS 38.508-1 [4] table 4.5.2.2-2
1 are performed on NR Cell 12.
seconds, but before 720 seconds
(“MinimumPeriodicSearchTimer”) from power
on? (Note 1 and Note 3)
23 (Note 2)
B
- EXCEPTION: Steps 23Ca1 to 23Cb3a1 - - - -
describe behaviour that depends on events
happening prior to their execution; the "lower
case letter" identifies a step sequence that
take place if a specific prior event takes place.
23 IF 5GS registration type is set as Initial - - - -
Ca Registration in step 23B, THEN Steps 5 to
1- 20a1of the generic test procedure in TS
23 38.508-1 Table 4.5.2.2-2 are performed on NR
Ca Cell 13.
16a
1
23 IF 5GS registration type is set as Mobility - - - -
Cb Registration in step 23B, THEN Steps 4 to 6a1
1- of the generic test procedure in TS 38.508-1
23 Table 4.9.5.2.2-1 are performed on NR Cell
Cb 13.
3a1
24- Void - - - -
28a
1
table 6.1.1.6.3.2-1/2.
seconds (“MinimumPeriodicSearchTimer”)
from step 24? (Note 1)
30 (Note 2)
B
- EXCEPTION: Steps 30Ca1 to 30Cb3a1 - - - -
describe behaviour that depends on events
happening prior to their execution; the "lower
case letter" identifies a step sequence that
take place if a specific prior event takes place.
30 IF 5GS registration type is set as Initial - - - -
Ca Registration in step 30B, THEN Steps 5 to
1- 20a1of the generic test procedure in TS
30 38.508-1 Table 4.5.2.2-2 are performed on NR
Ca Cell 11.
16a
1
30 IF 5GS registration type is set as Mobility - - - -
Cb Registration in step 30B, THEN Steps 4 to 6a1
1- of the generic test procedure in TS 38.508-1
30 Table 4.9.5.2.2-1 are performed on NR Cell
Cb 11.
3a1
ETSI
31- Void - - - -
35a
1
Note 1: Timers in Steps 23 and 30 are derived from the value defined by the “MinimumPeriodicSearchTimer”.
Note 3: Tolerance of 5min is added to allow time for the UE to find the proper PLMN.
None
6.1.1.7 PLMN selection of RPLMN or (E)HPLMN; Automatic mode
(1)
with { UE in Automatic network selection mode and RPLMN, EHPLMN and HPLMN cells available and UE is
fitted with a USIM containing the EHPLMN list and the USIM indicates RPLMN or (E)HPLMN should be
selected }
ensure that {
when { UE is switched on }
then { UE selects a cell of the RPLMN or EHPLMN. }
}
(2)
with { UE in Automatic network selection mode and RPLMN, HPLMN and VPLMN cells available and UE is
fitted with a USIM not containing or containing empty EHPLMN list and the USIM indicates RPLMN or
(E)HPLMN should be selected }
ensure that {
then { UE selects a cell of the RPLMN or HPLMN. }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.304 clause 5.1.2.2, TS
23.122 clauses 1.2, 4.4.3.1 and 4.4.3.1.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304 clause 5.1.2.2]
PLMN reading in TS 38.331 [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 NR Cell, the measured RSRP value shall be greater than or equal to -110 dBm.
...
[TS 23.122, clause 1.2]
Equivalent HPLMN list: To allow provision for multiple HPLMN codes, PLMN codes that are present within this list
shall replace the HPLMN code derived from the IMSI for PLMN selection purposes. This list is stored on the USIM
and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the
HPLMN code derived from the IMSI is not present in the EHPLMN list then it shall be treated as a Visited PLMN for
PLMN selection purposes.
[TS 23.122 clause 4.4.3.1]
ETSI
NOTE 2: An MS in automatic network selection mode can use location information to determine which PLMNs
can be available in its present location.
[TS 23.122 clause 4.4.3.1.1]
available (if the EHPLMN list is present);
System Simulator:
- 4 NR Cells as specified in TS 38.508-1 [4] table 4.4.2-3 are configured as shown in Table 6.1.1.7.3.1–1. PLMN
settings are defined in TS 36.523-1 [13] table 6.0.1-1.

NR Cell PLMN names
NR Cell 12 PLMN4
NR Cell 1 PLMN1
NR Cell 11 PLMN15
NR Cell 13 PLMN3
UE:
- USIM configurations 2 and 3 will be used as specified in tables 6.4.1-2 and 6.4.1-3 in TS 38.508-1 [4]. The
points at which each USIM configuration is used is specified in 6.1.1.7.3.2-2.
Preamble:
- The UE performs a successful registration on PLMN4 after which the UE is brought into the state Switched OFF
(state 0N-B) according to Table 4.4A.2-0 TS 38.508-1 [4].
ETSI
Table 6.1.1.7.3.2-1 for FR1 and table 6.1.1.7.3.2-2 for FR2 illustrate the downlink power levels to be applied for the
cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while
columns marked "T1" is to be applied subsequently in the Main behaviour. The exact instants on which these values
shall be applied are described in the texts in this clause.

Paramet Unit NR Cell 1 NR Cell 12 NR Cell 11 NR Cell 13 Remarks
er
T0 SS/PBCH dBm/SC "Off" -88 -88 "Off" Power level
SSS S “Off” is defined
EPRE in TS 38.508-1
[4] Table
6.2.2.1-3
T1 SS/PBCH dBm/SC -88 -88 "Off" -88 Power level
SSS S “Off” is defined
EPRE in TS 38.508-1
[4] Table
6.2.2.1-3

Paramet Unit NR Cell 1 NR Cell 12 NR Cell 11 NR Cell 13 Remarks
er
T0 SS/PBCH dBm/SCS "Off" -82 -82 "Off" Power level “Off” is
SSS defined in TS 38.508-1
EPRE [4] Table 6.2.2.1-3
Qrxlevmi dBm - -91+ -91+ -
n Delta(NRf2) Delta(NRf1)
T1 SS/PBCH dBm/SCS -82 -82 "Off" -82 Power level “Off” is
EPRE [4] Table 6.2.2.1-3
Qrxlevmi dBm -91+ -91+ - -91+
n Delta(NRf1) Delta(NRf2) Delta(NRf3)
ETSI
Table 6.1.1.7.3.2-3 Main behaviour

U- Message
S
1 Power on the UE with the USIM configuration 2 - - - -
specified in table 6.4.1-2 TS 38.508-1 [4].
2 Check: Does the UE transmit an --> NR RRC:RRCSetupRequest 1 P
RRCSetupRequest on NR Cell 12 or NR Cell 11?
3-20 Steps 3-20a1 of the registration procedure - - - -
described in TS 38.508-1 [4] table 4.5.2.2-2 are
performed on NR Cell 12 or NR Cell 11.
NOTE: The UE performs registration with valid
stored security context (see preamble) and the
21 Void - - - -
22 The generic test procedure in TS 38.508-1 [4] - - - -
Table 4.9.6.1-1 of Switch off procedure in
RRC_IDLE are performed.
23 Void - - - -
24 The SS adjusts cell levels according to row T1 of - - - -
table 6.1.1.7.3.2-1.
25 The UE is brought back to operation with the - - - -
USIM configuration 3 specified in table 6.4.1-3 TS
38.508-1 [4].
RRCSetupRequest on NR Cell 12 or NR Cell 1?
44 described in TS 38.508-1 [4] table 4.5.2.2-2 are
performed on NR Cell 12 or NR Cell 1.
None
6.1.1.8 PLMN selection of RPLMN or (E)HPLMN; Manual mode
(1)
with { UE in Manual network selection mode and EHPLMN and HPLMN cells available and (E)RPLMN cell is
not available and UE is fitted with a USIM containing the EHPLMN list and the UE supports the
exception to manual mode selection mode }
ensure that {
then { UE is switched on }
then { UE selects a cell of the highest priority EHPLMN. }
}
(2)
with { UE in Manual network selection mode and HPLMN and VPLMN cells available and (E)RPLMN cell is
not available and UE is fitted with a USIM not containing or containing empty EHPLMN list and the
UE supports the exception to manual mode selection mode }
ensure that {
then { UE selects a cell of the HPLMN. }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.304 clause 5.1.2.2, TS
23.122 clauses 1.2, 4.4.3.1 and 4.4.3.1.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304 clause 5.1.2.2]
ETSI
PLMN reading in TS 38.331 [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 NR cell, the measured RSRP value shall be greater than or equal to -110 dBm.
...
[TS 23.122, clause 1.2]
Equivalent HPLMN list: To allow provision for multiple HPLMN codes, PLMN codes that are present within this list
shall replace the HPLMN code derived from the IMSI for PLMN selection purposes. This list is stored on the USIM
and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the
HPLMN code derived from the IMSI is not present in the EHPLMN list then it shall be treated as a Visited PLMN for
PLMN selection purposes.
[TS 23.122 clause 4.4.3.1]
NOTE 2: An MS in automatic network selection mode can use location information to determine which PLMNs
can be available in its present location.
[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, "forbidden PLMNs for GPRS service" 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:
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.
ETSI
System Simulator:
- 3 NR cells: NR Cells 1, 13 and 12 as specified in TS 38.508-1 [4] table 6.3.2.2-1 are configured as shown in
Table 6.1.1.8.3.1–1. PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.

NR Cell PLMN
names
NR Cell 1 (configured PLMN4
during preamble)
NR Cell 1 (configured PLMN1
in test body all steps)
NR Cell 13 PLMN15
NR Cell 12 PLMN3
UE:
- USIM configurations 2 and 3 will be used as specified in tables 6.4.1-2 and 6.4.1-3 in TS 38.508-1 [4]. The
points at which each USIM configuration is used is specified in 6.1.1.8.3.2-2.
Preamble:
- The UE performs a successful registration on PLMN4 after which the UE is brought into the state Switched OFF
(state 0N-B) according to Table 4.4A.2-0 TS 38.508-1 [4].

Parameter Unit NR Cell 1 NR Cell 13 NR Cell 12 Remark
T0 SS/PBCH dBm/SCS -88 -88 "Off" Power level “Off”
SSS is defined in TS
EPRE 38.508-1 Table
6.2.2.1-3
T1 SS/PBCH dBm/SCS -88 "Off" -88 Power level “Off”
EPRE 38.508-1 Table
6.2.2.1-3
ETSI

T0 SS/PBCH dBm/SCS -82 -82 "Off" Power level “Off”
EPRE 38.508-1 Table
6.2.2.1-3
Qrxlevmin dBm -91+ -91+ -
Delta(NRf1) Delta(NRf3)
T1 SS/PBCH dBm/SCS -82 "Off" -82 Power level “Off”
EPRE 38.508-1 Table
6.2.2.1-3
Qrxlevmin dBm -91+ - -91+

U-S Message
1 Power on the UE with the USIM configuration - - - -
2 specified in table 6.4.1-2 TS 38.508-1 [4]..
20 described in TS 38.508-1 [4] table 4.5.2.2-2
NOTE: The UE performs registration with valid
stored security context (see preamble) and the
21 Void - - - -
22 The generic test procedure in TS 38.508-1 [4] - - - -
Table 4.9.6.1-1 of Switch off procedure in
RRC_IDLE are performed.
23 Void - - - -
24 The SS adjusts cell according to row T1 of - - - -
table 6.1.1.8.3.2-1.
25 The UE is brought back to operation with the - - - -
USIM configuration 3 specified in table 6.4.1-3
TS 38.508-1 [4].
44 described in TS 38.508-1 [4] table 4.5.2.2-2
None
6.1.2 NG-RAN Only Cell Selection
6.1.2.1 Cell selection / Qrxlevmin & Cell reselection (Intra NR)
(1)
with { UE in NR RRC_IDLE state }
ensure that {
ETSI
when { a cell fulfils all requirements for a suitable cell except the cell selection criteria
which are not fulfilled (Srxlev<0) }
then { the UE does not consider the cell suitable and no camping on this cell can take place }
}
(2)
ensure that {
when { a cell fulfils all requirements for a suitable cell including the cell selection criteria
for a cell which are also fulfilled (Srxlev>0) }
then { the UE considers the cell suitable and camps on it }
}
(3)
ensure that {
when { UE detects the cell ranked as the best cell }
then { UE reselects the new cell }
}
(4)
ensure that {
when { a cell fulfils cell selection criteria but trackingAreaCode is not provided for that PLMN }
then { the UE considers the cell as barred and no camping on this cell can take place }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.300 clauses 9.2.1.1,
3GPP TS 38.304 clause 4.1, 4.5, 5.2.1, 5.2.3.1, 5.2.3.2 , 5.2.4.6 and 5.3.1. Unless otherwise stated these are Rel-15
requirements.
[TS 38.300, clause 9.2.1.1]
The principles of PLMN selection in NR are based on the 3GPP PLMN selection principles. Cell selection is required
on transition from RM-DEREGISTERED to RM-REGISTERED, from CM-IDLE to CM-CONNECTED and from CM-
CONNECTED to CM-IDLE and is based on the following principles:
- The UE NAS layer identifies a selected PLMN and equivalent PLMNs;
- Cell selection is always based on CD-SSBs located on the synchronization raster (see subclause 5.2.4):
- The UE searches the NR frequency bands and for each carrier frequency identifies the strongest cell as per
the CD-SSB. It then 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.
Transition to RRC_IDLE:
On transition from RRC_CONNECTED to RRC_IDLE, a UE should camp on the last cell for which it was in
RRC_CONNECTED or a cell/any cell of set of cells or frequency be assigned by RRC in the state transition
message.
ETSI
Recovery from out of coverage:
The UE should attempt to find a suitable cell in the manner described for stored information or initial cell
selection above. If no suitable cell is found on any frequency or RAT, the UE should attempt to find an
acceptable cell.
In multi-beam operations, the cell quality is derived amongst the beams corresponding to the same cell (see subclause
9.2.4).
[TS 38.304, clause 4.1]
The RRC_IDLE state and RRC_INACTIVE state tasks can be subdivided into three processes:
- PLMN selection;
- Cell selection and reselection;
- Location registration and RNA update.
PLMN selection, cell reselection procedures, and location registration are common for both RRC_IDLE state and
RRC_INACTIVE state. RNA update is only applicable for RRC_INACTIVE state. When UE selects a new PLMN, UE
transitions from RRC_INACTIVE to RRC_IDLE.
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 3GPP TS 23.122 [9]. The NAS shall provide a list of equivalent PLMNs, if available, that
the AS shall use for cell selection and cell reselection.
With cell selection, the UE searches for a suitable cell of the selected PLMN, chooses that cell to provide available
services, and monitors its control channel. This procedure is defined as "camping on the cell".
The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of
the chosen cell. As an outcome of a successful Location Registration, the selected PLMN then becomes the registered
PLMN 3GPP TS 23.122 [9].
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. In RRC_INACTIVE state, if the new cell does not belong to the configured RNA, an RNA update
procedure is performed.
If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in 3GPP TS 23.122
[9] and search for a suitable cell if another PLMN has been selected by NAS.
If the UE loses coverage of the registered PLMN, either a new PLMN is selected automatically (automatic mode), or an
indication of available PLMNs is given to the user so that a manual selection can be performed (manual mode).
Registration is not performed by UEs only capable of services that need no registration.
The purpose of camping on a cell in RRC_IDLE state and RRC_INACTIVE state is fourfold:
a) It enables the UE to receive system information from the PLMN.
b) When registered and if the UE wishes to establish an RRC connection or resume a suspended RRC connection, it
can do this by initially accessing the network on the control channel of the cell on which it is camped.
c) If the network needs to send a message or deliver data to the registered UE, it knows (in most cases) the set of
tracking areas (in RRC_IDLE state) or RNA (in RRC_INACTIVE state) in which the UE is camped. It can then
send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas. The
UE will then receive the paging message and can respond.
d) It enables the UE to receive ETWS and CMAS notifications.
[TS 38.304, clause 4.5]
The cells are categorised according to which services they offer:
acceptable cell:
ETSI
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 an NR network:
- The cell is not barred, see subclause 5.3.1;
- The cell selection criteria are fulfilled, see subclause 5.2.3.2.
suitable cell:
A cell is considered as suitable if the following conditions are fulfilled:
- The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list and
trackingAreaCode is provided for that PLMN;
According to the latest information provided by NAS:
- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas" (TS 22.261 [12]),
which belongs to a PLMN that fulfils the first bullet above.
barred cell:
A cell is barred if it is so indicated in the system information, as specified in TS 38.331 [3].
reserved cell:
A cell is reserved if it is so indicated in system information, as specified in TS 38.331 [3].
Following exception to these definitions are applicable for UEs:
- if a UE has an ongoing emergency call, all acceptable cells of that PLMN are treated as suitable for the duration
of the emergency call.
[TS 38.304, clause 5.2.1]
UE shall perform measurements for cell selection and reselection purposes as specified in TS 38.133 [8].
The NAS can control the RAT(s) in which the cell selection should be performed, for instance by indicating RAT(s)
associated with the selected PLMN, and by maintaining a list of forbidden registration area(s) and a list of equivalent
PLMNs. The UE shall select a suitable cell based on RRC_IDLE or RRC_INACTIVE state measurements and cell
selection criteria.
In order to expedite the cell selection process, stored information for several RATs, if available, may be used by the UE.
When camped on a cell, the UE shall regularly search for a better cell according to the cell reselection criteria. If a
better cell is found, that cell is selected. The change of cell may imply a change of RAT. Details on performance
requirements for cell reselection can be found in TS 38.133 [8].
The NAS is informed if the cell selection and reselection result in changes in the received system information relevant
for NAS.
For normal service, the UE shall camp on a suitable cell, monitor control channel(s) of that cell so that the UE can:
- receive system information from the PLMN; and
- receive registration area information from the PLMN, e.g., tracking area information; and
- receive other AS and NAS Information; and
- if registered:
- receive paging and notification messages from the PLMN; and
- initiate transfer to Connected mode.
ETSI
For cell selection in multi-beam operations, measurement quantity of a cell is up to UE implementation.
For cell reselection in multi-beam operations, using a maximum number (nrofSS-BlocksToAverage) of beams to be
considered and a threshold (absThreshSS-BlocksConsolidation) which are configured for a cell, the measurement
quantity of this cell is derived amongst the beams corresponding to the same cell based on SS/PBCH block as follows:
- if the highest beam measurement quantity value is below the threshold:
- derive a cell measurement quantity as the highest beam measurement quantity value, where each beam
measurement quantity is described in TS 38.215 [11].
- else:
- derive a cell measurement quantity as the linear average of the power values of up to the maximum number
of highest beam measurement quantity values above the threshold.
[TS 38.304, clause 5.2.3.1]
Cell selection is performed by one of the following two procedures:
a) Initial cell selection (no prior knowledge of which RF channels are NR frequencies):
1. The UE shall scan all RF channels in the NR bands according to its capabilities to find a suitable cell.
2. On each frequency, the UE need only search for the strongest cell.
3. Once a suitable cell is found, this cell shall be selected.
b) Cell selection by leveraging stored information:
1. This procedure requires stored information of frequencies and optionally also information on cell parameters
from previously received measurement control information elements or from previously detected cells.
2. Once the UE has found a suitable cell, the UE shall select it.
3. If no suitable cell is found, the initial cell selection procedure in a) shall be started.
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 38.304, clause 5.2.3.2]
The cell selection criterion S is fulfilled when:
Srxlev > 0 AND Squal > 0
where:Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset )– Pcompensation - Qoffsettemp
Squal = Qqualmeas – (Qqualmin + Qqualminoffset) - Qoffsettemp
where:
ETSI
Srxlev Cell selection RX level value (dB)

Squal Cell selection quality value (dB)
Qoffsettemp Offset temporarily applied to a cell as specified in TS 38.331 [3] (dB)
Qrxlevmeas Measured cell RX level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qrxlevmin Minimum required RX level in the cell (dBm). If the UE supports SUL
frequency for this cell, Qrxlevmin is obtained from RxLevMinSUL, if
present, in SIB1, SIB2 and SIB4, additionally, if QrxlevminoffsetcellSUL is
present in SIB3 and SIB4 for the concerned cell, this cell specific
offset is added to the corresponding Qrxlevmin to achieve the
required minimum RX level in the concerned cell;
else Qrxlevmin is obtained from q-RxLevMin in SIB1, SIB2 and SIB4,
additionally, if Qrxlevminoffsetcell is present in SIB3 and SIB4 for the
concerned cell, this cell specific offset is added to the corresponding
Qrxlevmin to achieve the required minimum RX level in the concerned
cell.
Qqualmin Minimum required quality level in the cell (dB). Additionally, if
Qqualminoffsetcell is signalled for the concerned cell, this cell specific offset
is added to achieve the required minimum quality level in the
concerned cell.
Qrxlevminoffset Offset to the signalled Qrxlevmin 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 3GPP TS 23.122 [9]
Qqualminoffset Offset to the signalled Qqualmin taken into account in the Squal
Pcompensation If the UE supports the additionalPmax in the NS-PmaxList, if present,
in SIB1, SIB2 and SIB4:
max(PEMAX1 –PPowerClass, 0) – (min(PEMAX2, PPowerClass) – min(PEMAX1,
PPowerClass)) (dB);
else:
max(PEMAX1 –PPowerClass, 0) (dB)
PEMAX1, PEMAX2 Maximum TX power level of a UE may use when transmitting on the
uplink in the cell (dBm) defined as PEMAX in TS 38.101 [15]. PEMAX1
and PEMAX2 are obtained from the p-Max and NS-PmaxList
respectively in SIB1, SIB2 and SIB4 as specified in TS 38.331 [3].
PPowerClass Maximum RF output power of the UE (dBm) according to the UE
power class as defined in TS 38.101 [15]
The signalled values Qrxlevminoffset and Qqualminoffset 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 (3GPP TS 23.122 [9]). 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.
[TS 38.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
Rs = Qmeas,s +Qhyst - Qoffsettemp
Rn = Qmeas,n -Qoffset - Qoffsettemp
where:
Qmeas 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 Qoffsets,n plus Qoffsetfrequency, if
Qoffsets,n is valid, otherwise this equals to Qoffsetfrequency.
Qoffsettemp Offset temporarily applied to a cell as specified in TS 38.331 [3].
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2.
The cells shall be ranked according to the R criteria specified above by deriving Qmeas,n and Qmeas,s and calculating the R
values using averaged RSRP results.
ETSI
If rangeToBestCell is not configured, the UE shall perform cell reselection to the highest ranked cell. If this cell is
found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
If rangeToBestCell is configured, then the UE shall perform cell reselection to the cell with the highest number of
beams above the threshold (i.e. absThreshSS-BlocksConsolidation) among the cells whose R value is within
rangeToBestCell of the R value of the highest ranked cell. If there are multiple such cells, the UE shall perform cell
reselection to the highest ranked cell among them. If this cell is found to be not-suitable, the UE shall behave according
to subclause 5.2.4.4.
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 TreselectionRAT;
- more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 38.304, clause 5.3.1]
Cell status and cell reservations are indicated in the MIB or SIB1 message as specified in TS 38.331 [3] by means of
three fields:
- cellBarred (IE type: "barred" or "not barred")

Indicated in MIB message. In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs
- cellReservedForOperatorUse (IE type: "reserved" or "not reserved")

Indicated in SIB1 message. In case of multiple PLMNs indicated in SIB1, this field is specified per PLMN.
- cellReservedForOtherUse (IE type: "true")

Indicated in SIB1 message. In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs.
When cell status is indicated as "not barred" and "not reserved" for operator use and not "true" for other use,
- All UEs shall treat this cell as candidate during the cell selection and cell reselection procedures.
When cell status is indicated as "true" for other use,
- The UE shall treat this cell as if cell status is "barred".
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN and not "true" for other use,
- UEs assigned to Access Identity 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate
during the cell selection and reselection procedures if the field cellReservedForOperatorUse for that PLMN set
to "reserved".
- UEs assigned to an Access Identity 0, 1, 2 and 12 to 14 shall behave as if the cell status is "barred" in case the
cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
NOTE 1: Access Identities 11, 15 are only valid for use in the HPLMN/ EHPLMN; Access Identities 12, 13, 14 are
only valid for use in the home country as specified in TS 22.261 [12].
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
- The UE is not permitted to select/reselect this cell, not even for emergency calls.
- The UE shall select another cell according to the following rule:
- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the MIB:
- the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds.
- the UE may select another cell on the same frequency if the selection criteria are fulfilled.
- else:
- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the SIB1 or due to
trackingAreaCode being absent in SIB1 as specified in TS 38.331 [3]:
- The UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds.
ETSI
- If the field intraFreqReselection in MIB message 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 field intraFreqReselection in MIB message 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.
The cell selection of another cell may also include a change of RAT.
System Simulator:
- NR Cell 1 and NR Cell 11.
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.
UE:
- None.
Preamble:
- The UE is in state Switched OFF (state 0-A) according to TS 38.508-1 [4].
Table 6.1.2.1.3.2-1/2 illustrate 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", "T2", "T3" and "T4" are applied at the points indicated in the Main
behaviour description in Table 6.1.2.1.3.2-3.
Parameter Unit NR Cell 1 NR Cell 11 Remark
T1 SS/PBCH dBm/ -98 Off The power level value is such to satisfy SrxlevNRCell1 <
SSS EPRE SCS 0 but the UE is able to read the PLMN identity
Qrxlevmin dBm -90 -
Qrxlevminoffset dB 0 -
Pcompensation dB 0 -
T2 SS/PBCH dBm/ -80 Off The power level is such that SrxlevNRCell1 > 0
SSS EPRE SCS
Qrxlevmin dBm -90 -
T3 SS/PBCH dBm/ -87 -78 The power level values are assigned to satisfy RNRCell
SSS EPRE SCS 1 < RNRCell 11.
Qrxlevmin dBm -90 -90
Qrxlevminoffset dB 0 0
Pcompensation dB 0 0
SSS EPRE SCS 1 > RNRCell 11.
Note: The downlink signal level uncertainty is specified in TS 38.508-1 [4] clause 6.2.2.1.
ETSI
T1 SS/PBCH dBm/ -100 Off The power level value is such to satisfy SrxlevNRCell1 <
SSS EPRE SCS 0 but the UE is able to read the PLMN identity
Qrxlevmin dBm - -
91+Delta(N
Rf1)
T2 SS/PBCH dBm/ -82 Off The power level is such that SrxlevNRCell1 > 0
SSS EPRE SCS
Qrxlevmin dBm - -
91+Delta(N
Rf1)
SSS EPRE SCS 1< RNRCell 11.
Qrxlevmin dBm - -
100+Delta( 100+Delta(
NRf1) NRf1)
SSS EPRE SCS 1> RNRCell 11.
Qrxlevmin dBm - -
100+Delta( 100+Delta(
NRf1) NRf1)
ETSI

U-S Message
1 SS adjusts the SS/PBCH EPRE level of NR - - - -
Cell 1 according to row "T1" in table
6.1.2.1.3.2-1/2.
2 The UE is switched on. - - - -
RRCSetupRequest on NR Cell 1 within the
next 60 s?
4 SS re-adjusts the SS/PBCH EPRE level of NR - - - -
Cell 1 level according to row "T2" in table
6.1.2.1.3.2-1/2.
23 described in TS 38.508-1 [4] Table 4.5.2.2-2
- EXCEPTION: Step 23Aa1 should be executed - - - -
in case of FR2
23 SS change NR Cell 1 SIB1 with modification of - - - -
Aa Qrxlevmin.
1
24 The SS changes SS/PBCH - - - -
EPRE level of NR Cell 11 according to the row
"T3" in table 6.1.2.1.3.2-1/2.
25- Check: Does the test result of generic test - - 3 P
31 procedure in TS 38.508-1 [4] clause 4.9.5
NOTE 1: The UE performs registration and the
32 SS change NR Cell 1 SIB1 - - - -
32 Wait for 2.1* modification period second for the
A SS to transmit modified system information
(Note 1)
EPRE level of NR Cell 1 and 11 according to
the row "T4" in table 6.1.2.1.3.2-1/2.
34 Check: Does the UE send an - - 4 F
next 60 s?
Note 1: The modification period, expressed in number of radio frames = modificationPeriodCoeff *
defaultPagingCycle.
Table 6.1.2.1.3.3-1: SIB1 for NR Cell 1 (preamble) and NR Cell 11 (preamble)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28

SIB1 ::= SEQUENCE {
cellSelectionInfo SEQUENCE {
q-RxLevMin -45 -90 dBm FR1
q-RxLevMin ROUND((- FR2
91+Delta(NRf1))/2)
}
}
ETSI
Table 6.1.2.1.3.3-1A: SIB1 for NR Cell 1 (Step23Aa1, Table 6.1.2.1.3.2-3)

SIB1 ::= SEQUENCE {
q-RxLevMin ROUND([- FR2
100+Delta(NRf1)]/2)
}
}
Table 6.1.2.1.3.3-2: SIB1 for NR Cell 1 (Step32, Table 6.1.2.1.3.2-3)

SIB1 ::= SEQUENCE {
q-RxLevMin ROUND((- -91+Delta(NRf1) FR2
91+Delta(NRf1))/2) dBm
}
cellAccessRelatedInfo CellAccessRelatedInfo
}
Table 6.1.2.1.3.3-3: CellAccessRelatedInfo (Table 6.1.2.1.3.3-2)

CellAccessRelatedInfo ::= SEQUENCE {
plmn-IdentityList PLMN-IdentityInfoList
cellReservedForOtherUse Not present
}
Table 6.1.2.1.3.3-4: PLMN-IdentityInfoList (Table 6.1.2.1.3.3-3)

PLMN-IdentityInfoList ::= SEQUENCE (SIZE 1 entry
trackingAreaCode Not present
}
}
6.1.2.2 Cell selection / Qqualmin / Intra NR / Serving cell becomes non-suitable

(Srxlev > 0, Squal < 0)
(1)
ensure that {
when { a cell fulfils all requirements for a suitable cell except the cell selection criteria
which are not fulfilled (Srxlev>0 AND Squal<0) }
then { the UE does not consider the cell suitable and no camping on this cell can take place }
}
ETSI
(2)
ensure that {
when { a cell fulfils all requirements for a suitable cell including the cell selection criteria
for a cell which are also fulfilled (Srxlev>0 AND Squal>0) }
then { the UE considers the cell suitable and camps on it }
}
(3)
ensure that {
when { the serving cell becomes non-suitable (Srxlev > 0 and Squal < 0)and there is a suitable
neighbour cell (Srxlev > 0 and Squal > 0) }
then { UE selects the suitable neighbour cell }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.300 clauses 9.2.1.1,
3GPP TS 38.304 clause 4.1, 4.5, 5.2.1, 5.2.3.1, 5.2.3.2, 5.2.4.6 and 5.3.1. Unless otherwise stated these are Rel-15
requirements.
[TS 38.300, clause 9.2.1.1]
is not barred.
On transition from RRC_CONNECTED to RRC_IDLE, a UE should camp on the last cell for which it was in
RRC_CONNECTED or a cell/any cell of set of cells or frequency be assigned by RRC in the state transition
message.
acceptable cell.
9.2.4).
[TS 38.304, clause 4.1]
ETSI
- PLMN selection;
PLMN 3GPP TS 23.122 [9].
[TS 38.304, clause 4.5]
acceptable cell:
suitable cell:
ETSI
- The cell is part of either:
- the selected PLMN, or:
- the registered PLMN, or:
- a PLMN of the Equivalent PLMN list.
- The cell selection criteria are fulfilled, see subclause 5.2.3.2;
- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas" TS 22.261 [12],
barred cell:
A cell is barred if it is so indicated in the system information TS 38.331 [3].
reserved cell:
A cell is reserved if it is so indicated in system information TS 38.331 [3].
[TS 38.304, clause 5.2.1]
selection criteria.
for NAS.
- if registered:
For cell reselection in multi-beam operations, using a maximum number (nrofSS-BlocksToAverage) of beams to be
considered and a threshold (absThreshSS-BlocksConsolidation) which are configured for a cell, the measurement
ETSI
- if the highest beam measurement quantity value is below the threshold:
- else:
- derive a cell measurement quantity as the linear average of the power values of up to the maximum number
of highest beam measurement quantity values above the threshold.
[TS 38.304, clause 5.2.3.1]
[TS 38.304, clause 5.2.3.2]
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset )– Pcompensation - Qoffsettemp
where:
where:
ETSI

cell.
concerned cell.
PPowerClass)) (dB);
else:
[TS 38.304, clause 5.2.4.6]
where:

ETSI
[TS 38.304, clause 5.3.1]
Cell status and cell reservations are indicated in the MIB or SIB1 message TS 38.331 [3] by means of three fields:



to "reserved".
- UEs assigned to an Access Identity in the range of 0 to 10 and 12 to 14 shall behave as if the cell status is
"barred" in case the cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
only valid for use in the home country as specified in 3GPP TS 22.261 [12].
- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the MIB or the SIB1:
- else
- If the field intraFreqReselection in MIB message is set to "allowed", the UE may select another cell on
the same frequency if re-selection criteria are fulfilled;
ETSI
- If the field intraFreqReselection in MIB message is set to "not allowed" the UE shall not re-select a cell
on the same frequency as the barred cell;
System Simulator:
- NR Cell 1 and NR Cell 11 have different tracking areas according to TS 38.508-1 [4] Table 4.4.2-3.
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.2, and message contents
defined in is used in NR cells.
UE:
- None.
Preamble:
texts in this clause. Configurations marked "T1" "T2" and "T3" are applied at the points indicated in the Main
behaviour description in Table 6.1.2.2.3.2-3.
Parameter Unit NR NR Remark
Cell 1 Cell 11
T1 SS/PBCH dBm/ -91 Off The power level value is such to satisfy SrxlevNRCell1 > 0 and
SSS EPRE SCS SqualNRCell1< 0 but the UE is able to read the PLMN identity
RSRQ dB -12.56 -
Noc dBm/ -94 Noc is applied for NRf1
SCS
Qrxlevmin dBm -110 -
Qqualmin dB -12 -
Qqualminoffset dB 0 -
ETSI
T2 SS/PBCH dBm/ -78 -115 The power level is such that SrxlevNRCell1 > 0 and SqualNRCell1 >
SSS EPRE SCS 0
RSRQ dB -10.89 -31.83
Noc dBm/ -94
SCS
Qqualmin dB -12 -12
Qqualminoffset dB 0 -0
Pcompensation dB 0 -0
T3 SS/PBCH SSS dBm/ SrxlevNRCell1 > 0 and SqualNRCell1 < 0
-91 -78
EPRE SCS
RSRQ dB -12.56 -10.89
Noc dBm/ -94
SCS
Qqualmin dB -12 -12
Qqualminoffset dB 0 0
Srxlev* dB 19 32 NR Cell 11 is suitable cell
Squal* dB -0.56 1.11
Note: The downlink signal level uncertainty is specified in TS 38.508-1 [4] clause 6.2.2.1
Cell 1 Cell 11
T1 SS/PBCH dBm/ FFS Off The power level value is such to satisfy SrxlevNRCell1 > 0 and
SSS EPRE SCS SqualNRCell1< 0 but the UE is able to read the PLMN identity
RSRQ dB FFS -
Noc dBm/ FFS Noc is applied for NRf1
SCS
Qrxlevmin dBm FFS -
Qqualmin dB FFS -
T2 SS/PBCH dBm/ FFS Off The power level is such that SrxlevNRCell1 > 0 and SqualNRCell1 >
SSS EPRE SCS 0
RSRQ dB FFS -
Noc dBm/ FFS
SCS
Qrxlevmin dBm FFS -
Qqualmin dB FFS -
T3 SS/PBCH SSS dBm/ SrxlevNRCell1 > 0 and SqualNRCell1 < 0
FFS FFS
EPRE SCS
RSRQ dB FFS FFS
Noc dBm/ FFS
SCS
Qrxlevmin dBm FFS FFS
Qqualmin dB FFS FFS
Qqualminoffset dB 0 0
Srxlev* dB FFS FFS NR Cell 11 is suitable cell
Squal* dB FFS FFS
Note: The downlink signal level uncertainty is specified in TS 38.508-1 [4] clause FFS.
ETSI

U-S Message
6.1.2.2.3.2-1/2.
next 60 s?
Cell 1 level according to row "T2" in table
6.1.2.2.3.2-1/2.
Cell 1 and NR Cell 11 according to row "T3" in
table 6.1.2.2.3.2-1/2.
25 Check: Does the test result of generic test - - 3 P
procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1
released.
Table 6.1.2.2.3.3-1: SIB1 (NR Cell 1, Preamble and all steps of Table 6.1.2.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 with Condition QBASED

SIB1 ::= SEQUENCE {
q-QualMin -12 FR1
FFS FR2
}
}
Table 6.1.2.2.3.3-2: SIB2 (NR Cell 1, Preamble and all steps of Table 6.1.2.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.2-1 with Condition QBASED

SIB2 ::= SEQUENCE {
intraFreqCellReselectionInfo SEQUENCE {
q-QualMin -12 -12dB FR1
FFS FR2
}
}
ETSI
6.1.2.3 Cell selection / Intra NR / Serving cell becomes non-suitable (S<0, MIB
Indicated barred)
(1)
ensure that {
when { the serving cell becomes non-suitable (S<0)and there is a suitable neighbour cell (S>0) }
}
(2)
ensure that {
when { the serving cell becomes barred and there is a suitable neighbour cell }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.304 clause 4.1,
5.2.3.2 and 5.3.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 4.1]
- PLMN selection;
PLMN 3GPP TS 23.122 [9].
ETSI
[TS 38.304, clause 5.2.3.2]
where:
where:

cell.
concerned cell.
PPowerClass)) (dB);
else:
ETSI
[TS 38.304, clause 5.3.1]
Cell status and cell reservations are indicated in the MIB or SIB1 message TS 38.331 [3] by means of three fields:



to "reserved".
- UEs assigned to an Access Identity in the range of 0 to 10 and 12 to 14 shall behave as if the cell status is
"barred" in case the cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
only valid for use in the home country as specified in 3GPP TS 22.261 [12].
- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the MIB or the SIB1:
- else
- If the field intraFreqReselection in MIB message is set to "allowed", the UE may select another cell on
the same frequency if re-selection criteria are fulfilled;
- If the field intraFreqReselection in MIB message is set to "not allowed" the UE shall not re-select a cell
on the same frequency as the barred cell;
ETSI
System Simulator:
- NR Cell 1 and NR Cell 11 have different tracking areas according to TS 38.508-1 [4] Table 4.4.2-3.
UE:
None.
Preamble:
- UE is in state 1N-A on NR Cell 1(serving cell) according to 38.508-1 [4].
Table 6.1.2.3.3.2-1/2 illustrate the downlink power levels and other changing parameters to be applied for the cells at
texts in this clause. The configuration T0 indicates the initial conditions for preamble. Configurations marked "T1"and
"T2"are applied at the points indicated in the Main behaviour description in Table 6.1.2.3.3.2-3.
T0 dBm/ The power level values are assigned to
SS/PBCH SSS EPRE -88 "Off"
SCS ensure the UE registered on NR Cell 1.
dBm/ SrxlevNRCell 1 < 0 (NOTE 1)
SS/PBCH SSS EPRE "Off" -88
T1 SCS
Qrxlevmin dBm - -110
SS/PBCH SSS EPRE dBm/ -94 -88 SrxlevNRCell 11 > 0, SrxlevNRCell 1 > 0
SCS
T2
cellBarred - notBarred barred Serving cell becomes barred
T0 dBm/ The power level values are assigned to
SS/PBCH SSS EPRE FFS "Off"
SCS ensure the UE registered on NR Cell 1.
Qrxlevmin dBm FFS -
dBm/ SrxlevNRCell 1 < 0 (NOTE 1)
SS/PBCH SSS EPRE "Off" FFS
T1 SCS
Qrxlevmin dBm - FFS
SS/PBCH SSS EPRE dBm/ FFS FFS SrxlevNRCell 11 > 0, SrxlevNRCell 1 > 0
SCS
T2
Qrxlevmin dBm FFS FFS
cellBarred - notBarred barred Serving cell becomes barred
NOTE: If the UE fails the test because of a failure to detect and reselect to a right cell, then the operator may re-run
the test.
ETSI

U-S Message
table 6.1.2.3.3.2-1/2.
procedure in TS 38.508-1 [4] clause 4.9.5
released.
3 SS changes NR Cell 11 SS/PBCH EPRE level - - - -
and MIB IE cellBarred according to row "T2" in
table 6.1.2.3.3.2-1/2. And SS transmits Short
Message on PDCCH addressed to P-RNTI
using Short Message field in DCI format 1_0.
Bit 1 of Short Message field is set to 1 to
indicate the SysInfo Modification.
NOTE: The RRC connection is released and
UE is in RRC_IDLE mode.
Table 6.1.2.3.3.3-1: SIB1 for NR Cells 1 and 11 (Preamble and all steps, table 6.1.2.3.3.2-3)

SIB1 ::= SEQUENCE {
FFS FR2
}
}
Table 6.1.2.3.3.3-2: SIB2 for NR Cells 1 and 11 (Preamble and all steps, table 6.1.2.3.3.2-3)

SIB2 ::= SEQUENCE {
cellReselectionInfoCommon SEQUENCE {
rangeToBestCell Not present
}
intraFreqCellReselectionInfo SEQUENCE {
FFS FR2
t-ReselectionNR 7
}
}
Table 6.1.2.3.3.3-3: MIB for NR Cell 11 (step 3, Table 6.1.2.3.3.2-3)

MIB ::= SEQUENCE {
cellBarred barred
}
ETSI
6.1.2.4 Cell reselection for interband operation
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell on the different frequency
band }
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 5.2.3.2 and
5.2.4.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.3.2]
where:
where:
ETSI

cell.
concerned cell.
while camped normally in a VPLMN, as specified in TS 23.122 [9]
Pcompensation If the UE supports the additionalPmax in the NR-NS-PmaxList, if
present, in SIB1, SIB2 and SIB4:
PPowerClass)) (dB);
else:
uplink in the cell (dBm) defined as PEMAX in TS 38.101 [15]. If UE
supports SUL frequency for this cell, PEMAX1 and PEMAX2 are obtained
from the p-Max for SUL in SIB1 and NR-NS-PmaxList for SUL
respectively in SIB1, SIB2 and SIB4 as specified in TS 38.331 [3],
else PEMAX1 and PEMAX2 are obtained from the p-Max and NR-NS-
PmaxList respectively in SIB1, SIB2 and SIB4 for regular UL as
specified in TS 38.331 [3].
a periodic search for a higher priority PLMN while camped normally in a VPLMN (TS 23.122 [9]). 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.[TS 38.304, clause 5.2.4.5]
If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on
the current serving cell, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the
serving frequency shall be performed if:
- A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > ThreshX, HighQ during a time interval
TreselectionRAT
Otherwise, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving
frequency shall be performed if:
- A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT;
and
- More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a cell on an equal priority NR frequency shall be based on ranking for intra-frequency cell reselection
as defined in subclause 5.2.4.6.
ETSI
the current serving cell, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the
- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority NR or E-UTRAN RAT/ frequency
fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT.
Otherwise, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving
- The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils Srxlev >
ThreshX, LowP during a time interval TreselectionRAT; 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.
If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
- If the highest-priority frequency is an NR frequency, the highest ranked cell among the cells on the highest
priority frequency(ies) meeting the criteria according to clause 5.2.4.6;
- If the highest-priority frequency is from another RAT, the highest ranked cell among the cells on the highest
priority frequency(ies) meeting the criteria of that RAT.
System Simulator:
- System information combination NR-4 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in NR cells.
UE:
None.
Preamble:
- The UE is in state 1N-A on NR Cell 1(serving cell) according to TS 38.508-1 [4] Table 4.4A.2-1.
Table 6.1.2.6.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the NR 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. The configuration "T0" indicates the initial conditions. Subsequent configurations marked "T1"
is applied at the points indicated in the Main behaviour description in Table 6.1.2.4.3.2-3.
Cell 1 Cell 10
T0 SS/PBCH dBm/SCS -88 Off The power level values are
SSS EPRE assigned to ensure the UE
registered on NR Cell 1.
T1 SS/PBCH dBm/SCS -88 -78 NR Cell 10 become
SSS EPRE stronger than ThreshNR Cell
10, high.
Note: Power level “Off” is defined in TS38.508-1 [4] Table 6.2.2.1-3.
ETSI
Cell 1 Cell 10
T0 SS/PBCH dBm/SCS FFS Off The power level values are
T1 SS/PBCH dBm/SCS FFS FFS NR Cell 10 become
SSS EPRE stronger than ThreshNR Cell
10, high.
Note: The uncertain downlink signal level is specified in TS 38.508-1 [4] clause
FFS.

U-S Message
1 The SS changes NR Cell 10 SS/PBCH EPRE - - - -
level according to the row "T1" in table 6.1.2.
4.3.2-1/2.
2 Wait for 34 seconds to allow UE to recognise - - - -
the change.
procedure in TS 38.508-1 [4] Table 4.9.4-1
Table 6.1.2.4.3.3-1: Conditions for specific message contents in Tables below
Condition Explanation
NR Cell 1 This condition applies to system information transmitted on NR Cell 1.
Table 6.1.2.4.3.3-2: SIB2 of NR Cell 1 and NR Cell10 (preamble and all steps, Table 6.1.2.4.3.2-3)

SIB2::= SEQUENCE {
cellReselectionServingFreqInfo
SEQUENCE{
cellReselectionPriority 1 NR Cell 1
5 NR Cell 10
}
}
ETSI
Table 6.1.2.4.3.3-3: SIB4 of NR Cell 1 and NR Cell 10 (preamble and all steps, Table 6.1.2.4.3.2-3)

SIB4::= SEQUENCE {
InterFreqCarrierFreqList SEQUENCE 1 entry
(SIZE (1..maxFreq)) OF
InterFreqCarrierFreqInfo {
InterFreqCarrierFreqInfo[1] SEQUENCE entry 1
{
dl-CarrierFreq Same downlink ARFCN as used NR Cell 1
for NR Cell 10
Same downlink ARFCN as used NR Cell 10
for NR Cell 1
t-ReselectionNR 7 seconds
threshX-HighP 10 20 dB
1 NR Cell 10
}
}
}
6.1.2.5 Cell reselection for interband operation using Pcompensation / Between FDD
and TDD
(1)
with { UE in NR RRC_IDLE state on a FDD band }
ensure that {
when { UE detects the cell selection using Pcompensation & reselection criteria is met for the
cell on a TDD band }
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 5.2.3.2 and
[TS 38.304, clause 5.2.3.2]
where:
where:
ETSI

cell.
concerned cell.
PPowerClass)) (dB);
else:
PmaxList respectively in SIB1, SIB2 and SIB4 for regular UL as
different cell of this higher priority PLMN.[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
as defined in subclause 5.2.4.6.
ETSI
System Simulator:
- NR Cell 1 is set to NR FDD mode and NR Cell 10 is set to NR TDD mode.
UE:
None.
Preamble:
the texts in this clause. The configuration "T0" indicates the initial conditions. Subsequent configuration marked "T1" is
applied at the points indicated in the Main behaviour description in Table 6.1.2.5.3.2-3.
ETSI
Cell 1 Cell 10
T0 SS/PBCH dBm/SCS -88 Off The power level values are
T1 SS/PBCH dBm/SCS -88 -80 NR Cell 1 become lower
SSS EPRE than Threshserving, low and
NR Cell 10 become
stronger than ThreshNR Cell
10, low.
Cell 1 Cell 10
T0 SS/PBCH dBm/SCS FFS Off The power level values are
T1 SS/PBCH dBm/SCS FFS FFS NR Cell 1 become lower
SSS EPRE than Threshserving, low and
NR Cell 10 become
stronger than ThreshNR Cell
10, low.
Note: The uncertain downlink signal level is specified in TS 38.508-1 [4] section
FFS.

U-S Message
level according to the row "T1" in table
6.1.2.5.3.2-1/2.
the change.
ETSI
Table 6.1.2.5.3.3-2: SIB1 of NR Cell 1 (preamble and all steps, Table 6.1.2.5.3.2-3)

SIB1::= SEQUENCE {
servingCellConfigCommon SEQUENCE{
uplinkConfigCommon SEQUENCE{
FrequencyInfoUL SEQUENCE {
p-Max 33dBm
}
}
}
}
Table 6.1.2.5.3.3-3: SIB2 of NR Cell 1 and NR Cell10 (preamble and all steps, Table 6.1.2.5.3.2-3)

SIB2::= SEQUENCE {
SEQUENCE{
threshServingLowP 9 18 dB NR Cell 1
1 NR Cell 10
}
}

SIB4::= SEQUENCE {
{
for NR Cell 10
for NR Cell 1
p-Max 33dBm NR Cell 1
threshX-HighP 14 28 dB
threshX-LowP 6 12 dB
5 NR Cell 10
}
}
}
6.1.2.6 Void
6.1.2.7 Cell reselection / Equivalent PLMN
(1)
Registration procedure}
ETSI
ensure that {
when { a suitable neighbour cell on an equivalent PLMN becomes better ranked than the suitable
Serving cell}
then { UE reselects to this equivalent PLMN cell}
}
(2)
ensure that {
when { the Serving cell becomes unsuitable due to S<0 and a suitable cell exists on an equivalent
PLMN}
then {UE reselects to this equivalent PLMN cell}
}
(3)
ensure that {
when { the UE evaluates cells for reselection}
then { UE ignores suitable cells for which the UE has no reselection priority provided}
}
References: The conformance requirements covered in the present test case are specified in: TS 23.122, clause 4.4.3, TS
38.304, clause 5.2.4.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.4.1]
The UE shall only perform cell reselection evaluation for NR 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, GPRS attach procedure, tracking area update procedure, EPS attach
procedure, and registration procedure. The list is deleted by an MS attached for emergency bearer services after detach
or registered for emergency services after deregistration. 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 NR Cells as specified in TS 38.508-1 Table 4.4.2.1 are configured
broadcasting PLMNs as indicated in Table 6.1.2.7.3.1-1.
The PLMNs are identified in the test by the identifiers in Table 6.1.2.7.3.1-1.

NR Cell PLMN name MCC MNC
11 PLMN1 001 11
12 PLMN2 002 21
13 PLMN3 003 31
All NR cells are high quality.
ETSI
All cells are suitable cells.
System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells
UE:
The UE is in Automatic PLMN selection mode.
Preamble:
The UE is registered on PLMN1 (NR Cell 11) using the procedure described in TS 38.508-1 [4] clause 4.5.2.2
in Table 6.1.2.7.3.3-1.
The UE is in state Registered, Idle Mode (State 1N-A) on NR Cell 11 according to 38.508-1 [4];
conditions after preamble, while columns marked "T1" and "T2" are to be applied subsequently in the Main behaviour.
The exact instants on which these values shall be applied are described in the texts in this clause.

Parameter Unit NR Cell 11 NR Cell 12 NR Cell 13 Remarks
T0 SS/PBCH dBm/SCS -78 -89 -100 All NR cells S>0
SSS
EPRE
T1 SS/PBCH dBm/SCS -115 -89 -100 NR Cell 11 S < 0 as described
SSS in TS 38.508-1 clause FFS
EPRE
T2 SS/PBCH dBm/SCS -78 -100 -89 All NR cells S>0
SSS
EPRE
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 38.508-1 clauses FFS.

T0 SS/PBCH FFS FFS FFS FFS All NR cells S>0
SSS
EPRE
T1 SS/PBCH FFS FFS FFS FFS NR Cell 1 S < 0 as described in
SSS TS 38.508-1 clause FFS
EPRE
T2 SS/PBCH FFS FFS FFS FFS All NR cells S>0
SSS
EPRE
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 38.508-1 clauses FFS.
ETSI

U-S Message
1 Check: Does the UE transmit an NR RRC: RRCSetupRequest 1 F
RRCSetupRequest message within T -->
seconds? (Note 1)
table 6.1.2.7.3.2-1 for FR1 (or table
6.1.2.7.3.2-2 for FR2)
3 Check: Does the test result of generic test - 2 -
procedure in TS 38.508-1 Table 4.9.5.2.2-1
NOTE: The UE performs a " REGISTRATION
REQUEST procedure with type "mobility
registration updating” with PLMN1 and PLMN2
listed as an Equivalent PLMN in the
REGISTRATION ACCEPT message; the RRC
connection is released.
4 Check: Does the test result of generic test - 1 -
connection is released.
5 SS adjusts cell levels according to row T0 of - - -
6.1.2.7.3.2-2 for FR2)
6 Check: Does the UE transmit an NR RRC RRCSetupRequest 1,3 F
RRCSetupRequest message within T -->
seconds? (Note 1)
6.1.2.7.3.2-2 for FR2)
8 Check: Does the test result of generic test - 3 P
connection is released. (Note 2)
Note 1: In Steps 1 and 6, wait T seconds to ensure that the UE has detected, measured and evaluated the
neighbour inter-frequency NR cells is provided, see TS 38.133 clause 4.2.2.4, where in T = 100sec for FR1
and 300sec for FR2
Note 2: In Step 8, the UE moves to Cell 13 because no reselection priority is defined for Cell 1, see Table
6.1.2.7.3.3-4.
Derivation path: TS 38.508-1 Table 4.7.1-7

Equivalent PLMNs PLMN3
ETSI
Table 6.1.2.7.3.3-2: REGISTRATION ACCEPT for NR Cell 13 (step 3 and 18, Table 6.1.2.7.3.2-3)

Equivalent PLMNs PLMN1, 2

Table 6.1.2.7.3.3-4: SystemInformationBlockType4 for Cell 12 (preamble and all steps, Table
6.1.2.7.3.2-3)
Derivation Path: TS 38.508-1 Table 4.6.2-3

SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE 2 entries n denotes the
(1..maxFreq)) OF InterFreqCarrierFreqInfo { index of the entry
dl-CarrierFreq Same downlink EARFCN
as used for Cell 11
cellReselectionPriority Not present UE does not have
a priority for
frequency of Cell
11
}
as used for Cell 13
}
lateNonCriticalExtension Not present
}
Table 6.1.2.7.3.3-5: SystemInformationBlockType4 for Cell 13 (preamble and all steps, Table
6.1.2.7.3.2-3)

SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE 2 entries n denotes the
(1..maxFreq)) OF InterFreqCarrierFreqInfo { index of the entry
as used for Cell 11
cellReselectionPriority Not present UE does not have
a priority for
frequency of Cell
11
}
as used for Cell 12
}
}
ETSI
6.1.2.8 Cell reselection / Equivalent PLMN / Single Frequency operation
(1)
ensure that {
when { a suitable neighbour cell on an equivalent PLMN becomes better ranked than the suitable
Serving cell }
then { UE reselects to this equivalent PLMN cell }
}
(2)
ensure that {
when { the Serving cell becomes unsuitable due to S<0 and a suitable cell exists on an equivalent
PLMN }
then { UE reselects to this equivalent PLMN cell }
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 5.2.4.1. Unless
otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.4.1]
System Simulator:
- Three intra-frequency multi-PLMN cells.
- System information combination NR-3 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells

Cell PLMN name
1 PLMN1
2 PLMN2
4 PLMN3
- All cells are high quality.
- All cells are suitable cells.
UE:
ETSI
Preamble:
- The UE is registered on PLMN1 (NR Cell 1) using the procedure described in TS 38.508-1 [4] clause 4.5.2.2
in Table 6.1.2.8.3.3-1.
- The UE is in state Registered, Idle Mode (State 1N-A) on NR Cell 1 according to TS 38.508-1 [4] Table 4.4A.2-
1.
conditions after preamble, while columns marked "T1" and "T2" are to be applied subsequently in the Main behaviour.

T0 SS/PBCH dBm/SC -78 -84 -90 All NR cells S > 0
SSS S
EPRE
T1 SS/PBCH dBm/SC -115 -88 -82 NR Cell 1 S < 0 as described in
SSS S TS 38.508-1 [4] clause 6.2.2.1
EPRE
T2 SS/PBCH dBm/SC -115 -82 -88
SSS S
EPRE

T0 SS/PBCH FFS FFS FFS FFS All NR cells S > 0
SSS
EPRE
T1 SS/PBCH FFS FFS FFS FFS NR Cell 1 S < 0 as described in
SSS TS 38.508-1 [4] clause 6.2.2.2
EPRE
T2 SS/PBCH FFS FFS FFS FFS
SSS
EPRE
ETSI

U-S Message
1 Check: Does the UE send an RRCSetupRequest --> NR RRC: RRCSetupRequest 1 F
within the next T seconds?
NOTE: The wait period of T seconds is to ensure
that the UE has detected, measured and
evaluated the neighbour inter-frequency NR cells
is provided, see TS 38.133[30] clause 4.2.2.4,
where in T = 100sec for FR1 and 300sec for FR2.
2 SS adjusts cell levels according to row T1 of table - - - -
6.1.2.8.3.2-1 for FR1 (or table 6.1.2.8.3.2-2 for
FR2).
procedure in TS 38.508-1 [4] subclause 4.9.5
NOTE: The UE performs a Registration procedure
for mobility registration update with PLMN1 and
PLMN2 listed as an Equivalent PLMN in the
REGISTRATION ACCEPT message.
FR2).
FR2).
indicate that the UE is camped on NR Cell 4,
'connected without release'?

Table 6.1.2.8.3.3-2: REGISTRATION ACCEPT for NR Cell 4 (steps 3 & 7, Table 6.1.2.8.3.2-3)

Allowed NSSAI
S-NSSAI
ETSI

Allowed NSSAI
S-NSSAI
6.1.2.9 Cell reselection using Qhyst, Qoffset and Treselection
(1)
with { UE in NR RRC_IDLE state, and the UE is not in high mobility state }
ensure that {
when { Qhyst is non-zero or its value changes in system information }
then { UE reselects the highest ranked cell taking the actual Qhyst value into account }
}
(2)
with { UE in NR RRC_IDLE state, and the UE is not in high mobility }
ensure that {
when { cell reselection criteria are fulfilled during a time interval Treselection }
then { UE reselects the highest ranked cell after the Treselection interval expires }
}
(3)
with { UE in NR RRC_IDLE state, and the UE is not in high mobility }
ensure that {
when { Qoffset is non-zero or its value changes in system information }
then { UE reselects the highest ranked cell taking the actual Qoffset value into account }
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 5.2.4.6. Unless
[TS 38.304, clause 5.2.4.6]
where:

ETSI
- the new cell is better than the serving cell according to the cell reselection criteria specified above during a time
interval TreselectionRAT;
System Simulator:
- NR Cell 1, NR Cell 2 and NR Cell 11.
UE:
None.
Preamble:
the texts in this clause. The configuration "T0" indicates the initial conditions. Subsequent configurations marked "T1",
"T2" and so on are applied at the points indicated in the Main behaviour description in Table 6.1.2.9.3.2-3.
ETSI
Table 6.1.2.9.3.2-1: Time instances of cell power level and parameter changes For FR1
Parameter Unit NR NR NR Remark
Cell 1 Cell 2 Cell
11
T0 SS/PBCH dBm/SCS -88 Off Off The power level values are assigned to
SSS EPRE ensure the UE registered on NR Cell 1.
Qhysts dB 24 0 0
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T1 SS/PBCH dBm/SCS -94 -88 Off NR Cell 2 becomes stronger than NR
SSS EPRE Cell 1 but NR Cell 1 remains the
Qhysts dB 24 0 0 highest ranked one due to Qhysts NR Cell
Qoffsets,n dB 0 0 0 1
Treselectio 0 0 0
S
nNR
T2 SS/PBCH dBm/SCS -94 -88 Off Qhysts NR Cell 1 change causes NR Cell 2
SSS EPRE to become highest ranked cell
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T3 SS/PBCH dBm/SCS -88 -94 Off NR Cell 1 becomes the strongest and
SSS EPRE highest ranked one due to power
Qhysts dB 0 0 0 adjustment
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T4 SS/PBCH dBm/SCS -88 -94 Off Qoffsets,n NR Cell1 change to 24dB,
SSS EPRE Qoffsets,n NR Cell 2 remains zero
Qhysts dB 0 0 0
Qoffsets,n dB 24 0 0
Treselectio 0 0 0
S
nNR
T5 SS/PBCH dBm/SCS -94 -88 Off NR Cell 1 becomes weaker but it
SSS EPRE remains the highest ranked one due to
Qhysts dB 0 0 0 Qoffsets,n NR Cell 1
Treselectio 0 0 0
S
nNR
T6 SS/PBCH dBm/SCS -94 -88 Off NR Cell 2 becomes the highest ranked
SSS EPRE one due to Qoffsets,n NR Cell 1 change
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T7 SS/PBCH dBm/SCS Off NR Cell 1 becomes the highest ranked
-88 -94
SSS EPRE one
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T8 SS/PBCH dBm/SCS TreselectionNR of NR Cell 1 change to
-88 Off -94
SSS EPRE 7S
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 7 0 0
S
nNR
T9 SS/PBCH dBm/SCS NR Cell 2 becomes the highest ranked
-94 Off -88
SSS EPRE one
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 7 0 0
S
nNR
ETSI
ETSI
Table 6.1.2.9.3.2-2: Time instances of cell power level and parameter changes For FR2
Cell 1 Cell 2 Cell
11
T0 SS/PBCH dBm/SCS -82 Off Off The power level values are assigned
SSS EPRE to ensure the UE registered on NR
Qhysts dB 24 0 0 Cell 1.
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T1 SS/PBCH dBm/SCS -91 -82 Off NR Cell 2 becomes stronger than NR
SSS EPRE Cell 1 but NR Cell 1 remains the
Qhysts dB 24 0 0 highest ranked one due to Qhysts NR
Qoffsets,n dB 0 0 0 Cell 1
Treselectio 0 0 0
S
nNR
T2 SS/PBCH dBm/SCS -91 -82 Off Qhysts NR Cell 1 change causes NR Cell
SSS EPRE 2 to become highest ranked cell
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T3 SS/PBCH dBm/SCS -82 -91 Off NR Cell 1 becomes the strongest and
SSS EPRE highest ranked one due to power
Qhysts dB 0 0 0 adjustment
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T4 SS/PBCH dBm/SCS -82 -91 Off Qoffsets,n NR Cell1 change to 24dB,
SSS EPRE Qoffsets,n NR Cell 2 remains zero
Qhysts dB 0 0 0
Treselectio 0 0 0
S
nNR
T5 SS/PBCH dBm/SCS -91 -82 Off NR Cell 1 becomes weaker but it
SSS EPRE remains the highest ranked one due
Qhysts dB 0 0 0 to Qoffsets,n NR Cell 1
Treselectio 0 0 0
S
nNR
T6 SS/PBCH dBm/SCS -91 -82 Off NR Cell 2 becomes the highest
SSS EPRE ranked one due to Qoffsets,n NR Cell 1
Qhysts dB 0 0 0 change
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T7 SS/PBCH dBm/SCS Off NR Cell 1 becomes the highest
-82 -91
SSS EPRE ranked one
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 0 0 0
S
nNR
T8 SS/PBCH dBm/SCS TreselectionNR of NR Cell 1 change
-82 Off -94
SSS EPRE to 7S
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 7 0 0
S
nNR
T9 SS/PBCH dBm/SCS NR Cell 2 becomes the highest
-91 Off -82
SSS EPRE ranked one
Qhysts dB 0 0 0
Qoffsets,n dB 0 0 0
Treselectio 7 0 0
S
nNR
ETSI
ETSI

U-S Message
1 SS re-adjusts the SSS levels according to row - - - -
"T1" in table 6.1.2.9.3.2-1/2.
1A Wait for 34[FR1]/130[FR2] seconds, the SS <-- NR RRC: Paging - -
transmits a Paging message on NR Cell 2.
2 Check:Does the UE send an NR: RRCSetup --> NR RRC: RRCSetupRequest 1 F
Request on NR Cell 2 within the next 10
seconds?
3 SS notifies UE of the system information <-- NR RRC: Paging - -
change on NR Cell 1 by send Short Message
on PDCCH using P-RNTI.
4 SS resets Qhysts NR Cell 1 according to row "T2" - - - -
in table 6.1.2.9.3.2-1/2, The ValueTag of SIB2
in the SI-SchedulingInfo of SIB1 is increased
on NR Cell 1.
5 Wait for 2.1* modification period to allow the - - - -
new system information to take effect.
5A Wait for 8[FR1]/27[FR2] seconds. - - - -
7 SS re-adjusts SSS levels according to rows - - - -
"T3" in table 6.1.2.9.3.2-1/2.
8 Wait for 8[FR1]/27[FR2] seconds to allow UE - - - -
to recognise the change.
9 The test result of generic test procedure in TS - - - -
38.508-1 [4] Table 4.9.4-1 indicate that the UE
is camped on NR Cell 1.
11 SS changes Qoffsets,n NR Cell 1 according to rows - - - -
"T4" in table 6.1.2.9.3.2-1/2. The ValueTag of
SIB3 in the SI-SchedulingInfo of SIB1 is
increased on NR Cell 1.
13 SS re-adjusts SSS levels according to row - - - -
"T5" in table 6.1.2.9.3.2-1/2.
indicate that the UE is still camped on NR Cell
1?
17 SS resets Qoffsets,n NR Cell1 according to row - - - -
"T6" in table 6.1.2.9.3.2-1/2, The ValueTag of
SIB3 in the SI-SchedulingInfo of SIB1 is
increased on NR Cell 1.
18 Wait for 8[FR1]/27[FR2] seconds. - - - -
A
"T7" in table 6.1.2.9.3.2-1/2.
ETSI
23 SS sends notification of the system information <-- NR RRC: Paging - -

24 SS changes TreselectionNR Cell 1 according to - - - -
rows "T8" in table 6.1.2.9.3.2-1/2, The
ValueTag of SIB2 in the SI-SchedulingInfo of
SIB1 is increased on NR Cell 1.
25 SS re-adjusts cell power levels according to - - - -
rows "T8" in table 6.1.2.9.3.2-1/2.
26 Wait for 34[FR1]/130[FR2] seconds to allow - - - -
UE to detect Cell 11.
"T9" in table 6.1.2.9.3.2-1/2.
28 Check: Does the UE send an NR: --> NR RRC: RRCSetupRequest 2 F
RRCSetupRequest on NR Cell 11 within
Timer=TreselectionNR from step 27?
29 SS waits for Timer=TreselectionNR Cell 1 expires
after step 27
30 Check: Does the UE send an NR: --> NR RRC: RRCSetupRequest 2 P
RRCsetupRequest on NR Cell 11?
31- Steps 2 to 5 of the generic test procedure in - - - -
34 TS 38.508-1 [4] Table 4.9.5.2.2-1 are
performed on NR Cell 11.
Note: The wait time at steps 2 and 26 is Tdetect,NR_Intra and at Steps 8,14 and 21 it is Tevaluate,NR_Intra (as per TS
38.133 [30], clause 4.2.2.3) plus the time to read the system information TSI-NR.

SIB1 ::= SEQUENCE {
si-SchedulingInfo SI-SchedulingInfo
}
Table 6.1.2.9.3.3-2: SI-SchedulingInfo (si-SchedulingInfo in Table 6.1.2.9.3.3-1)

SI-SchedulingInfo ::= SEQUENCE {
schedulingInfoList SEQUENCE 1 entry
(SIZE(1..maxSI-Message)) OF
SchedulingInfo {
SchedulingInfo[1] SEQUENCE { entry 1
sib-MappingInfo SEQUENCE (SIZE 2 entries
(1..maxSIB)) OF SIB-TypeInfo {
SIB-TypeInfo[1] SEQUENCE { entry 1
Type[1] sibType2
valueTag[1] 0 The value is
increased by 1 in step
4 and step 24
}
Type[2] sibType3
valueTag[2] 0 The value is
increased by 1 in step
11 and step 17
}
}
}
}
}
ETSI
Table 6.1.2.9.3.3-3: SIB2 of NR Cell 1 (preamble, Table 6.1.2.9.3.2-3)

SIB2 ::= SEQUENCE {
cellReselectionInfoCommon SEQUENCE
{
q-Hyst dB24
}
}
Table 6.1.2.9.3.3-4: SIB2 of NR Cell 1 (step 4, Table 6.1.2.9.3.2-3)

SIB2 ::= SEQUENCE {
{
q-Hyst dB0
}
}

SIB3 ::= SEQUENCE {
intraFreqNeighCellList SEQUENCE (SIZE (1.. 1 entry
maxCellIntra)) OF IntraFreqNeighCellInfo {
IntraFreqNeighCellInfo[1] SEQUENCE{ entry 1
q-OffsetCell dB24
}
}
}

SIB3 ::= SEQUENCE {
IntraFreqNeighCellInfo[1] SEQUENCE { entry 1
q-OffsetCell dB0
}
}
}

SIB2 ::= SEQUENCE {
intraFreqCellReselectionInfo SEQUENCE
{
}
}
ETSI
6.1.2.10 Void
6.1.2.11 Area Specific SIBs using systemInformationAreaID
(1)
with { UE is in NR RRC_IDLE state }
ensure that {
when { SIB1 does not include si-RequestConfig and si-BroadcastStatus set to notBroadcasting }
then { UE sends RRCSystemInfoRequest message and acquires the necessary SIBs }
}
(2)
with { UE in NR_RRC Idle State }
ensure that {
when { UE reselects to neighbor cell with same systemInformationAreaID and SIB1 does not include
si-RequestConfig and si-BroadcastStatus set to notBroadcasting }
then { UE applies system information parameters of previous cell for reselection purposes }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.304, clause 5.2.4.4,
[TS 38.304, clause 5.2.4.2]
Following rules are used by the UE to limit needed measurements:
- If the serving cell fulfils Srxlev > SIntraSearchP and Squal > SIntraSearchQ, the UE may choose not to perform intra-
frequency measurements.
- Otherwise, the UE shall perform intra-frequency measurements.
- The UE shall apply the following rules for NR 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 a NR inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection
priority of the current NR frequency, the UE shall perform measurements of higher priority NR inter-
frequency or inter-RAT frequencies according to TS 38.133 [8].
- For a NR inter-frequency with an equal or lower reselection priority than the reselection priority of the
current NR frequency and for inter-RAT frequency with lower reselection priority than the reselection
priority of the current NR frequency:
- If the serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE may choose not to
perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority;
- Otherwise, the UE shall perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or
lower priority according to TS 38.133 [8].
[TS 38.304, clause 5.2.4.6]
TreselectionRAT
ETSI
and
as defined in clause 5.2.4.6.
- If the highest-priority frequency is from another RAT, the strongest cell among the cells on the highest priority
frequency(ies) meeting the criteria of that RAT.
[TS 38.331, clause 5.2.2.2.1]
The UE shall apply the SI acquisition procedure as defined in clause 5.2.2.3 upon cell selection (e.g. upon power on),
cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network
from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS
notification; and whenever the UE does not have a valid version of a stored SIB.
When the UE acquires a MIB or a SIB1 or an SI message in a serving cell as described in clause 5.2.2.3, and if the UE
stores the acquired SIB, then the UE shall store the associated areaScope, if present, the first PLMN-Identity in the
PLMN-IdentityInfoList, the cellIdentity, the systemInformationAreaID, if present, and the valueTag, if present, as
indicated in the si-SchedulingInfo for the SIB. The UE may use a valid stored version of the SI except MIB, SIB1, SIB6,
SIB7 or SIB8 e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication.
NOTE: The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is
left to UE implementation.
The UE shall:
1> delete any stored version of a SIB after 3 hours from the moment it was successfully confirmed as valid;
1> for each stored version of a SIB:
2> if the areaScope is associated and its value for the stored version of the SIB is the same as the value received
in the si-SchedulingInfo for that SIB from the serving cell:
3> if the first PLMN-Identity included in the PLMN-IdentityInfoList, the systemInformationAreaID and the
valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are
identical to the PLMN-Identity, the systemInformationAreaID and the valueTag associated with the stored
version of that SIB:
4> consider the stored SIB as valid for the cell;
ETSI
[TS 38.331, clause 5.2.2.3.3]
The UE shall:
1> else:
2> apply the timeAlignmentTimerCommon included in SIB1;
2> apply the CCCH configuration as specified in 9.1.1.2;
2> initiate transmission of the RRCSystemInfoRequest message in accordance with 5.2.2.3.4;
2> if acknowledgement for RRCSystemInfoRequest message is received from lower layers:
3> acquire the requested SI message(s) as defined in subclause 5.2.2.3.2, immediately;
….
[TS 38.331, clause 5.2.2.3.4]
The UE shall set the contents of RRCSystemInfoRequest message as follows:
1> set the requested-SI-List to indicate the SI message(s) that the UE requires to operate within the cell, and for
which si-BroadcastStatus is set to notBroadcasting.
The UE shall submit the RRCSystemInfoRequest message to lower layers for transmission.
System Simulator:
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR Cells.
UE:
None.
Preamble:
- The UE is in NR RRC Idle mode (state 1N-A) on NR Cell 1 according to 38.508-1 [4] Table 4.4A.2-1.
texts in this clause. The configuration T0 indicates the initial conditions for preamble. Configurations marked "T1" and
"T2" is applied at the points indicated in the Main behaviour description in Table 6.1.2.11.3.2-3.
ETSI
T0 SS/PBCH dBm/SCS -88 Off Off
SSS
EPRE
T1 SS/PBCH dBm/SCS -95 -80 Off The power level values are assigned to
SSS satisfy SrxlevNRCell3 > ThreshX, HighP
EPRE
T2 SS/PBCH dBm/SCS Off -88 -80 The power level values are assigned to
SSS satisfy RNRCell 3 < RNRCell 6
EPRE

T0 SS/PBCH dBm/SCS FFS Off Off
SSS
EPRE
T1 SS/PBCH dBm/SCS FFS FFS Off The power level values are assigned to
SSS satisfy SrxlevNRCell3 > ThreshX, HighP
EPRE
T2 SS/PBCH dBm/SCS Off FFS FFS The power level values are assigned to
SSS satisfy RNRCell 3 < RNRCell 6
EPRE
ETSI

U-S Message
0 The SS changes SIB1 as specified as Table - - - -
6.1.2.11.3.3-1.
Note: The sysinfo combination of NR cell 1 is
changed to NR-4.
0A The SS notifies the UE of change of System <-- NR PDCCH (DCI 1_0): Short - -
Information on NR Cell 1 by send Short Message
Message on PDCCH using P-RNTI.
1 Void - - - -
2 UE sends RRCSystemInfoRequest message --> NR RRC: RRCSystemInfoRequest 1 P
to NR Cell 1 to request SIB4.
3 NR Cell 1 starts broadcasting <-- NR RRC: SystemInformation - -
SystemInformation message which including
SIB4.
3A The SS re-adjusts the SS/PBCH EPRE levels - - - -
and according to row "T1" in table 6.1.2.11.3.2-
1/2.
4 Wait 34s to let UE to perform inter-frequency - - - -
cell reselection to NR Cell 3 (Note 1).
4A Does the UE send RRCSystemInfoRequest 2 F
message on NR Cell 3 to request SIB4 in the
next 5s?
4B The test result of generic test procedure in TS - - - -
38.508-1 [4] Table 4.9.4.2.2-1 indicate that the
UE is camped on NR Cell 3.
5 The SS re-adjusts the SS/PBCH EPRE levels - - - -
1/2.
6 Void
6A Wait 34s to let UE to perform inter-frequency - - - -
cell reselection to NR Cell 6.(Note 1)
Note 1: The wait time for cell reselection procedure is selected to cover Tdetect, NR_inter (32s) + TSI-NR (1280 ms) =
33.28s rounded up to 34s.
Table 6.1.2.11.3.3-1: SIB1 of NR cell 1 and NR cell 3 (All steps in Table 6.1.2.11.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28 with Condition SIG AND FR1
SIB1 ::= SEQUENCE {
si-SchedulingInfo SI-SchedulingInfo-Area Table
6.1.2.11.3.3-2
}
ETSI
Table 6.1.2.11.3.3-2: SI-SchedulingInfo-Area (Table 6.1.2.11.3.3-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-173 with Condition FR1

schedulingInfoList SEQUENCE (SIZE (1..maxSI- 2 entries
Message)) OF SchedulingInfo {
si-BroadcastStatus broadcasting
si-Periodicity rf32
sib-MappingInfo SEQUENCE (SIZE (1..maxSIB)) 1 entry
OF SIB-TypeInfo {
type sibType2
}
}
}
si-BroadcastStatus not broadcasting
si-Periodicity rf64
sib-MappingInfo SEQUENCE (SIZE (1..maxSIB)) 1 entry
OF SIB-TypeInfo {
type sibType4
valueTag 0
areaScope true
}
}
}
}
systemInformationAreaID ’0000 0000 0000 0000
0000 0011’B
}
Table 6.1.2.11.3.3-3: RRCSystemInfoRequest (Step 2, Table 6.1.2.11.3.2-3)

RRCSystemInfoRequest ::= SEQUENCE {
rrcSystemInfoRequest-r15 SEQUENCE {
requested-SI-List 01000000000000000000 Bit corresponds to
000000000000 SIB4 in
schedulingInfoList
}
}
}
ETSI
Table 6.1.2.11.3.3-4: SystemInformation (Step 3, Table 6.1.2.11.3.2-3)

SystemInformation ::= SEQUENCE {
systemInformation-r15 SEQUENCE {
sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB)) 1 entry
OF CHOICE {
SIB4 SEQUENCE { As per TS 38.508-1 [4]
Table 4.6.2-3
Cell 3
smtc SSB-MTC as defined in
TS 38.508-1 [4] Table
4.6.3-185 with condition
INTER-FREQ_ODD
}
Cell 6
smtc SSB-MTC as defined in smtc of the inter-
TS 38.508-1 [4] Table freq carrier for NR
4.6.3-185 with condition Cell 6 is
INTER-FREQ_ODD calculated with
respect to NR Cell
3
}
}
}
}
}
}
}
6.1.2.12 Cell reselection using cell status and cell reservations /

cellReservedForOtherUse
(1)
with { UE camped normally in state NR RRC_IDLE }
ensure that {
when { A higher ranked cell is found with cell status "true" for other use }
then { UE does not attempt to reselect to the higher ranked cell }
}
[TS 38.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,
for the best cell according to absolute priority reselection criteria specified in subclause 5.2.4.5, the UE shall check if
the access is restricted according to the rules in subclause 5.3.1.
ETSI
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.
If the highest ranked cell or best cell according to absolute priority reselection rules is an intra-frequency or inter-
frequency cell which is not suitable due to being part of the "list of 5GS 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 300 seconds. If the UE enters into state any
cell selection, any limitation shall be removed. If the UE is redirected under NR control to a frequency for which the
timer is running, any limitation on that frequency shall be removed.
If the highest ranked cell or best cell according to absolute priority reselection rules is an inter-RAT 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 300 seconds. If the UE enters into state any cell selection, any limitation
shall be removed. If the UE is redirected under NR control to a frequency for which the timer is running, any limitation
on that frequency shall be removed.
[TS 38.304, clause 5.2.4.6]
where:

[TS 38.304, clause 5.3.1]
three fields:


ETSI

to "reserved".
- UEs assigned to an Access Identity 1, 2 and 12 to 14 shall behave as if the cell status is "barred" in case the cell
is "reserved for operator use" for the registered PLMN or the selected PLMN.
- else:
- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the SIB1:
System Simulator:
- NR Cell 1 and NR Cell 11 in different tracking areas.
ETSI
UE:
None.
Preamble:
- The UE is in NR RRC Idle mode (state 1N-A) on NR Cell 1 according to 38.508-1 [4] Table 4.4A.2-1.
texts in this clause. The configuration T0 indicates the initial conditions for preamble. Configurations marked "T1" is
applied at the points indicated in the Main behaviour description in Table 6.1.2.12.3.2-3.
T0 SS/PBCH dBm/ -88 Off
SSS EPRE SCS
T1 SS/PBCH dBm/ -88 -80 The power level values are assigned to satisfy
SSS EPRE SCS RNRCell 1 < RNRCell 11
cellReservedFor - - True
OtherUse
T0 SS/PBCH dBm/ FFS Off
SSS EPRE SCS
T1 SS/PBCH dBm/ FFS FFS The power level values are assigned to satisfy
cellReservedFor - - True
OtherUse

U-S Message
1/2.
2 Check: Does the UE initiate a random access - - 1 F
procedure on NR Cell 11 within the next 120s?
indicate that check UE is in state NR
RRC_IDLE on NR Cell 1?
Table 6.1.2.12.3.3-1: SIB1 for NR Cell 11 (Preamble, Table 6.1.2.12.3.2-3)

SIB1 ::= SEQUENCE {
cellAccessRelatedInfo SEQUENCE {
cellReservedForOtherUse true
}
}
ETSI
6.1.2.13 Cell reselection using cell status and cell reservations / Access Identity 0, 1,
2 and 12 to 14 – cellReservedForOperatorUse
(1)
with { UE camped normally in state NR RRC_IDLE and UE fitted with a USIM with at least one of the
following Access Identities set: 0,1,2,12,13,14}
ensure that {
when { a higher ranked cell is found "reserved" for Operator use }
then { UE does not attempt to reselect to the higher ranked cell }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.304, clause 5.3.1.
[TS 38.304, clause 5.3.1]
three fields:



When cell status is in+dicated as "true" for other use,
to "reserved".
- UEs assigned to an Access Identity 0, 1, 2 and 12 to 14 shall behave as if the cell status is "barred" in case the
cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
- else:
ETSI
- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the SIB1 or due to
trackingAreaCode being absent in SIB1 as specified in TS 38.331 [3]:- The UE may exclude the barred
cell as a candidate for cell selection/reselection for up to 300 seconds.
System Simulator:
- NR Cell 1 and NR Cell 12 with different tracking areas.
- NR Cell 1 and NR Cell 12 are HPLMN.
UE:
None.
Preamble:
- The UE is in NR RRC Idle mode (state 1N-A) on NR Cell 1 according to TS 38.508-1 [4] Table 4.4A.2-1.
- The UE switches off and then switches on.
texts in this clause. Configurations marked "T0" is applied for Preamble. Configurations marked "T1 is applied at the
points indicated in the Main behaviour description in Table 6.1.2.13.3.2-3.
SSS EPRE SCS
cellReservedFor - - Reserved
OperatorUse
ETSI
SSS EPRE SCS
OperatorUse

U-S Message
1 The SS adjusts the SS/PBCH EPRE levels - - - -
according to row "T1" in table 6.1.2.13.3.2-1/2.
indicate that check UE is in state NR

SIB1 ::= SEQUENCE {
plmn-IdentityList SEQUENCE (SIZE 1 entry
PLMN-Identity[1] Set to the same PLMN- entry 1
Identity with NR Cell 1
cellReservedForOperatorUse Reserved
}
}
}
}
6.1.2.14 Cell reselection using cell status and cell reservations / Access Identity 11 or
15 - cellReservedForOperatorUse
(1)
with { UE camped normally in state NR RRC_IDLE operating in their HPLMN/EHPLMN and fitted with a
USIM with access class11 or 15}
ensure that {
when { a higher ranked cell is found "reserved" for Operator use }
then { UE re-selects to the higher ranked cell }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.304, clause 5.3.1.
[TS 38.304, clause 5.3.1]
ETSI
three fields:



to "reserved".
- UEs assigned to an Access Identity 1, 2 and 12 to 14 shall behave as if the cell status is "barred" in case the cell
is "reserved for operator use" for the registered PLMN or the selected PLMN.
- else:
- If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the SIB1:
ETSI
System Simulator:
- NR Cell 1 and NR Cell 3 in different tracking areas.
- NR Cell 1 and NR Cell 3 are HPLMN.
UE:
- The UE is equipped with a USIM containing default values and USIM Configuration 17.
Preamble:
texts in this clause. Configurations marked "T0" is applied for Preamble. Configurations marked "T1 is applied at the
points indicated in the Main behaviour description in Table 6.1.2.14.3.2-3.
SSS EPRE SCS
OperatorUse
SSS EPRE SCS
OperatorUse

U-S Message
2 Check: Does the test result of test steps 1 to 5 - - 1 P
of generic test procedure in TS 38.508-1 [4]
Table 4.9.5.2.2-1 indicate that the UE is
camped on NR Cell 3?
ETSI

SIB1 ::= SEQUENCE {
plmn-IdentityList SEQUENCE (SIZE
cellReservedForOperatorUse Reserved
}
}
}
Table 6.1.2.14.3.3-2: SERVICE REQUEST (Preamble, Table 6.1.2.14.3.2-3; step 4 ,Table 4.5.2.2-4, TS
38.508-1 [4])
Derivation Path: Table 4.7.1-16.

Service type ‘0101’B high priority
access
6.1.2.15 Cell reselection in shared network environment
(1)
with { the UE is in NR RRC_Idle and registered on the HPLMN }
ensure that {
when { a cell of a different PLMN but shared with the HPLMN becomes highest ranked cell }
then { the UE reselects the cell shared with the HPLMN }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 23.122, clause 4.4.3,
and TS 38.304, clause 5.2.4.6. Unless otherwise stated these are Rel-15 requirements.
[TS 23.122, clause 4.4.3]
The registration on the selected PLMN and the location registration are only necessary if the MS is capable of services
which require registration. Otherwise, the PLMN selection procedures are performed without registration.
The ME shall utilise all the information stored in the SIM related to the PLMN selection; e.g. "HPLMN Selector with
Access Technology", "User Controlled PLMN Selector with Access Technology", "Forbidden PLMNs", "Equivalent
HPLMN", see 3GPP TS 31.102 [40].
The ME shall either utilise the "Operator controlled PLMN Selector with Access Technology" that it has stored locally
on the ME, or the Operator controlled PLMN Selector with Access Technology" stored in the SIM, for the purposes of
PLMN selection.
The "HPLMN Selector with Access Technology", "User Controlled PLMN Selector with Access Technology" and
"Operator Controlled PLMN Selector with Access Technology" data files in the SIM include associated access
technologies for each PLMN entry, see 3GPP TS 31.102 [40]. The PLMN/access technology combinations are listed in
priority order. If an entry indicates more than one access technology, then no priority is defined for the access
technologies within this entry and the priority applied to each access technology within this entry is an implementation
issue. If no particular access technology is indicated in an entry, it shall be assumed that all access technologies
supported by the ME apply to the entry. If an entry only indicates access technologies not supported by the ME, the
entry shall be ignored. If an entry indicates at least one access technology supported by the ME, the entry shall be used
in the PLMN selection procedures if the other criteria defined for the specific PLMN selection procedures are fulfilled.
ETSI
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, GPRS attach procedure, tracking area update procedure, EPS attach
procedure, and registration procedure. The list is deleted by an MS attached for emergency bearer services after detach
or registered for emergency services after deregistration. 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.
PLMN.
The MS shall not use the PLMN codes contained in the "HPLMN Selector with Access Technology" data file.
It is possible for the home network operator to identify alternative Network IDs as the HPLMN. If the EHPLMN list is
present, and not empty, the entries in the EHPLMN list are used in the network selection procedures. When attempting
to select a network the highest priority EHPLMN that is available shall be selected. If the EHPLMN list is present and
is empty or if the EHPLMN list is not present, the HPLMN derived from the IMSI is used for network selection
procedures.
NOTE 1: The "HPLMN Selector with Access Technology" data file is only used by the MS to get the HPLMN
access technologies related to the HPLMN code which corresponds to the PLMN code included in the
IMSI if the EHPLMN list is not present or is empty. If the EHPLMN list is present then this data field is
applicable to all the entries within the EHPLMN list.
NOTE 2: Different GSM frequency bands (e.g. 900, 1800, 1900, 400) are all considered GSM access technology.
An MS supporting more than one band should scan all the bands it’s supports when scanning for GSM
frequencies. However GSM COMPACT systems which use GSM frequency bands but with the CBPCCH
broadcast channel are considered as a separate access technology from GSM.
NOTE 3: The inclusion of the HPLMN derived from the IMSI in the EHPLMN list is allowed. The priority of the
HPLMN derived from the IMSI is given by its position in the EHPLMN list, see 3GPP TS 31.102 [40]
[TS 38.304, clause 5.2.4.6]
where:

ETSI
System Simulator:
- NR Cell 1 (HPLMN)
- NR Cell 11 (primary PLMN: same MCC like HPLMN but different MNC, secondary PLMN: HPLMN)
UE:
- None.
Preamble:
- The UE is in NR RRC Idle mode (state 1N-A) on NR Cell 1 according to 38.508-1 [4] Table 4.4A.2-1
texts in this clause. Row marked "T0" denotes the conditions after the preamble. Configurations marked "T1" is applied
at the points indicated in the Main behaviour description in Table 6.1.2.15.3.2-3.
SSS EPRE SCS
SSS EPRE SCS SrxlevNRCell 11 > SrxlevNRCell 1

SSS EPRE SCS
SSS EPRE SCS SrxlevNRCell 11 > SrxlevNRCell 1
ETSI

U-S Message
table 6.1.2.1.3.2-1/2.
RRCSetupRequest message on NR Cell 11?
4 Check; Does the UE transmit an --> NR RRC: RRCSetupComplete 1 P
RRCSetupComplete message indicating the
HPLMN (second PLMN in the list)?
Note: this message contains an
indicating "mobility registration updating" to
update the registration of the actual tracking
area according to default message contents.
7 described in TS 38.508-1 [4] Table 4.9.5.2.2-1
Table 6.1.2.15.3.3-1: SIB1 for NR Cell 1 (Preamble and all steps, Table 6.1.2.15.3.2-3)

SIB1 ::= SEQUENCE {
plmn-Identity[1] Set to the same Mobile
Country Code and Mobile
Network Code stored in
EFIMSI on the test USIM
card
}
}
}
Table 6.1.2.15.3.3-2: SIB1 for NR Cell 11 (Preamble and all steps, Table 6.1.2.15.3.2-3)

SIB1 ::= SEQUENCE {
plmn-Identity[1] Set to the same Mobile Same MCC like
Country Code stored in PLMN for NR Cell
EFIMSI on the test USIM, 1 but different
MNC=02 MNC
plmn-Identity[2] Set to the same Mobile This is the same
Country Code and Mobile PLMN as NR Cell
Network Code stored in 1
EFIMSI on the test USIM
card
}
}
}
ETSI
Table 6.1.2.15.3.3-3: RRCSetupComplete (step 4, Table 6.1.2.15.3.2-3)

RRCSetupComplete::= SEQUENCE {
selectedPLMN-Identity 2 HPLMN
}
}
}
6.1.2.16 Inter-frequency cell reselection (equal priority)
(1)
ensure that {
when { UE detects both intra-frequency and equal priority inter-frequency neighbour cells and the
inter-frequency cell is the highest ranked cell }
then { UE reselects the inter-frequency cell }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.304, clause 5.2.4.6.
[TS 38.304, clause 5.2.4.6]
where:

ETSI
System Simulator:
- NR Cell 1, NR Cell 2 and NR Cell 3 have different tracking areas.
UE:
None.
Preamble:
- The UE is in NR RRC Idle mode (state 1N-A) on NR Cell 1(according to 38.508-1 [4] Table 4.4A.2-1.
texts in this clause. Row marked "T0" denotes the conditions after the preamble. Configurations marked "T1", "T2" and
"T3" are applied at the points indicated in the Main behaviour description in Table 6.1.2.16.3.2-3.
1 2 3
T0 SS/PBCH dBm/ -88 -94 -78 The power level values are set so that RNRCell
SSS EPRE SCS 2< RNRCell 1 < R NRCell 3.
1 2 3
T0 SS/PBCH dBm/ FFS FFS FFS
SSS EPRE SCS

U-S Message
None.
ETSI
6.1.2.17 Cell reselection / Cell-specific reselection parameters provided by the

network in a neighbouring cell list
(1)
with { the UE is in NR RRC_IDLE and SystemInformationBlockType3 contain a cell-specific Qoffset for
a neighbour intra frequency cell }
ensure that {
when { the neighbour cell has lower power than the serving cell but it is higher ranked due to the
cell-specific Qoffset }
then { the UE reselects the neighbour cell with cell-specific Qoffset }
}
(2)
with { the UE is in RRC_IDLE and SystemInformationBlockType3 contain a black listed cell }
ensure that {
when { a black listed intra-freq cell becomes higher ranked than the serving cell }
then { the UE remains camped on the serving cell }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.304, clause 5.2.4.6.
[TS 38.304, clause 5.2.4.6]
where:

ETSI
System Simulator:
- NR Cell 1, NR Cell 2 and NR Cell 4 in different tracking areas.
- NR Cell 1 is transmitting SIB3 according to specific message contents (Qoffset1,2 is -24dB).
- NR Cell 2 is transmitting SIB3 according to specific message contents (NR Cell 4 is on black list)
UE:
None.
Preamble:
- The UE is in NR RRC Idle mode (state 1N-A) on NR Cell 1(according to 38.508-1 [4] Table 4.4A.2-1.
texts in this clause. Row marked "T0" denotes the conditions after the preamble. Configurations marked "T1", "T2" and
1 2 4
T0 SS/PBCH dBm/ -88 Off Off Only NR Cell 1 is on
SSS EPRE SCS
T1 SS/PBCH dBm/ -88 -94 Off NR Cell 2 has lower power but is higher
SSS EPRE SCS ranked due to cell-specific Qoffset1,2
T2 SS/PBCH dBm/ Off -94 Off
SSS EPRE SCS
T3 SS/PBCH dBm/ Off -94 -88 NR Cell 4 has higher power than NRCell 2
SSS EPRE SCS but is black listed
1 2 4
T0 SS/PBCH dBm/ -82 Off Off Only NR Cell 1 is on
SSS EPRE SCS
T1 SS/PBCH dBm/ -82 -91 Off NR Cell 2 has lower power but is higher
SSS EPRE SCS ranked due to cell-specific Qoffset1,2
T2 SS/PBCH dBm/ Off -91 Off
SSS EPRE SCS
T3 SS/PBCH dBm/ Off -91 -82 NR Cell 4 has higher power than NRCell 2
SSS EPRE SCS but is black listed
ETSI

U-S Message
2-6 Check: Does the test result of test steps 1 to 5 - - 1 P
Table 4.9.5.2.2-1 indicate that the UE is
camped on NR Cell 2?
8 Wait for 1 second to allow UE to recognise the - - - -
change.
9 The SS transmits an RRCRelease message to <-- NR RRC: RRCRelease - -
release RRC connection and move to
RRC_IDLE.

SIB3 ::= SEQUENCE {
intraFreqNeighCellList SEQUENCE {
physCellId The cell identity of NR
Cell 2 defined in 38.508-
1 [4] clause 4.4.2
q-OffsetCell dB-24
}
}

SIB3 ::= SEQUENCE {
intraFreqBlackCellList SEQUENCE { 1 entry
start PhysicalCellID of NR Cell
4
range Not present
}
}
6.1.2.18 Cell reselection, Sintrasearch, Snonintrasearch
(1)
ensure that {
when { Sintrasearch is non-zero in system information }
then { UE performs measurement and reselects the highest ranked cell upon Srxlev <
Sintrasearch }
}
ETSI
(2)
ensure that {
when { Snonintrasearch is non-zero in system information }
then { UE perform measurement and reselects the cell which belong to the equal priority
frequency cell upon Srxlev < Snonintrasearch }
}
(3)
ensure that {
then { UE perform measurement and reselects the cell which belong to the high priority
frequency cell upon Srxlev > Snonintrasearch }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.304, clauses 5.2.4.1,
5.2.4.5 and 5.2.4.6.
[TS 38.304, clause 5.2.4.1]
Absolute priorities of different NR frequencies or inter-RAT frequencies may be provided to the UE in the system
information, in the RRCRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case
of system information, an NR 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 and deprioritisationReq received in RRCRelease 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 any of the network configured values).
In case UE receives RRCRelease with deprioritisationReq, UE shall consider current frequency and stored frequencies
due to the previously received RRCRelease with deprioritisationReq or all the frequencies of NR to be the lowest
priority frequency (i.e. lower than any of the network configured values) while T325 is running irrespective of camped
RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection is performed on request by
NAS (TS 23.122 [9]).
NOTE: UE should search for a higher priority layer for cell reselection as soon as possible after the change of
priority. The minimum related performance requirements specified in TS 38.133 [8] are still applicable.
The UE shall delete priorities provided by dedicated signalling when:
- the UE enters a different RRC state; or
- the optional validity time of dedicated priorities (T320) expires; or
- a PLMN selection is performed on request by NAS (TS 23.122 [9]).
NOTE 2: Equal priorities between RATs are not supported.
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 NR and
E-UTRA), if configured, at inter-RAT cell (re)selection.
NOTE 3: The network may assign dedicated cell reselection priorities for frequencies not configured by system
information.
[TS 38.304, clause 5.2.4.5]
ETSI
- A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > ThreshX, HighQ during a time
interval TreselectionRAT
- A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval
TreselectionRAT; and
- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority NR or E-UTRAN RAT/
frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT.
- The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils
Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
[TS 38.304, clause 5.2.4.6]
where:

ETSI
found to be not-suitable, the UE shall behave according to clause 5.2.4.4.
to clause 5.2.4.4.
NOTE: If rangeToBestCell is configured but absThreshSS-BlocksConsolidation is not configured on an NR

frequency, the UE considers that there is one beam above the threshold for each cell on that frequency.
System Simulator:
- NR Cell 1, NR Cell 2 and NR Cell 3 as defined in TS 38.508-1 [4] Table 4.4.2-2 is used.
- NR Cell 1 uses System information combination NR-3 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in
NR cells.
- NR Cell 2 and NR Cell 3 uses System information combination NR-4 as defined in TS 38.508-1 [4] Table
4.4.3.1.2-1 is used in NR cells.
UE:
- None.
Preamble:
Table 6.1.2.18.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the NR
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", "T2" and "T3" are applied at the points indicated in
the Main behaviour description in Table 6.1.2.13.3.2-2.
ETSI
T0 SS/PBCH The power level values are assigned to
dBm/SCS -88 Off Off
SS/PBCH Srxlev of NR Cell 1 is less than
dBm/SCS -102 -94 -118
SSS EPRE Sintrasearch.
T1
SIntraSearch dB 20 20 20
Srxlev dB 8 16 -8
dBm/SCS -118 -102 -94
SSS EPRE Snonintrasearch.
T2
SnonIntraSearch dB 20 20 20
Srxlev dB -8 8 16
T3 SnonIntraSearch dB 20 20 2
SS/PBCH Srxlev of NR Cell 3 is greater than
dBm/SCS -88 -118 -88
T4 SSS EPRE Snonintrasearch but Cell 1 is high priority
Srxlev dB 22 22 22 cell.

dBm/SCS FFS Off Off
dBm/SCS FFS FFS FFS
SSS EPRE Sintrasearch.
T1
SIntraSearch dB 20 20 20
Srxlev dB FFS FFS FFS
dBm/SCS FFS FFS FFS
SSS EPRE Snonintrasearch.
T2
SnonIntraSearch dB 20 20 20
T3 SnonIntraSearch dB 20 20 2
SS/PBCH Srxlev of NR Cell 3 is greater than
dBm/SCS FFS FFS FFS
T4 SSS EPRE Snonintrasearch but Cell 1 is high priority
Srxlev dB FFS FFS FFS cell.
Note: The uncertain downlink signal level is specified in TS 38.508-1 [4] section FFS
ETSI

U-S Message
according to row "T1" in table 6.1.2.18.3.2-
1/2.
the change.
4 The SS re-adjusts the SSS levels according - - - -
to row "T2" in table 6.1.2.18.3.2-1/2.
the change.
7 The SS notifies the UE of change of System <-- NR RRC: Paging - -
Information on NR Cell 3 by sending Short
8 The SS changes the SnonIntraSearch for NR - - - -
6.1.2.18.3.2-1/2, The ValueTag of SIB2 in the
SI-SchedulingInfo of SIB1 is increased on NR
Cell 3.
9 Wait for 2.1* modification period to allow the - - -
to row "T4" in table 6.1.2.18.3.2-1/2.
11 Wait for 120 seconds to allow UE to - - - -
recognise the change.
ETSI
Table 6.1.2.18.3.3-2: SIB2 of NR Cell 1, NR Cell 2 and NR Cell 3 (preabmle and all steps, Table
6.1.2.18.3.2-3)

SIB2 ::= SEQUENCE {
SEQUENCE {
s-NonIntraSearch 10 20 dB
1 NR Cell 2 and Cell
3
}
{
s-IntraSearchP 10 20 dB
}
}
Table 6.1.2.18.3.3-3: SIB4 of NR Cell 2 and NR Cell 3 (preabmle and all steps, Table 6.1.2.18.3.2-3)

SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE 1 entry
{
for NR Cell 3
for NR Cell 1
t-ReselectionNR 1
threshX-HighP 7 14 dBm NR Cell 3
1 NR Cell 2
}
}
}

SIB1 ::= SEQUENCE {
}
ETSI

SchedulingInfo {
sib-MappingInfo SEQUENCE (SIZE 1 entry
type sibType2
valueTag 1
}
}
}
}
}

SIB2 ::= SEQUENCE {
SEQUENCE {
s-NonIntraSearchP 1 20 dB
}
}
6.1.2.19 Speed-dependent cell reselection
(1)
with { UE in NR RRC_IDLE state and in high mobility state }
ensure that {
when { UE detects the cell ranked as the best cell taking into account scaling factor }
}
(2)
with { UE in NR RRC_IDLE state and in medium mobility state }
ensure that {
when { UE detects the cell ranked as the best cell taking into account scaling factor }
}
References: The conformance requirements covered in the present test case are specified in: TS 38.304, clauses
5.2.4.3.0 and 5.2.4.3.1. TS 38.133, clause 4.2.2.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.4.3.0]
The UE mobility state is determined if the parameters (TCRmax, NCR_H, NCR_M and TCRmaxHyst) are broadcasted
in system information for the serving cell.
State detection criteria:
ETSI
Medium-mobility state criteria:
- If number of cell reselections during time period TCRmax is greater than or equal to NCR_M but less than or equal to
NCR_H.
High-mobility state criteria:
- If number of cell reselections during time period TCRmax is greater than NCR_H.
The UE shall not consider consecutive reselections where a cell is reselected again right after one reselection for
mobility state detection criteria.
State transitions:
The UE shall:
- if the criteria for High-mobility state is detected:
- enter High-mobility state.
- else if the criteria for Medium-mobility state is detected:
- enter Medium-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 38.304, clause 5.2.4.3.1]
UE shall apply the following scaling rules:
- If neither Medium- nor High-mobility state is detected:
- no scaling is applied.
- If High-mobility state is detected:
- Add the sf-High of "Speed dependent ScalingFactor for Qhyst" to Qhyst if broadcasted in system information;
- For NR cells, multiply TreselectionNR by the sf-High of "Speed dependent ScalingFactor for TreselectionNR"
if broadcasted in system information;
- If Medium-mobility state is detected:
- Add the sf-Medium of "Speed dependent ScalingFactor for Qhyst" to Qhyst if broadcasted in system
information;
- For NR cells, multiply TreselectionNR by the sf-Medium of "Speed dependent ScalingFactor for
TreselectionNR" if broadcasted in system information;
In case scaling is applied to any TreselectionRAT parameter, the UE shall round up the result after all scalings to the
nearest second.
[TS 38.133, clause 4.2.2.3]
The UE shall be able to identify new intra-frequency cells and perform SS-RSRP and SS-RSRQ measurements of the
identified intra-frequency cells without an explicit intra-frequency neighbour list containing physical layer cell
identities.
ETSI
The UE shall be able to evaluate whether a newly detectable intra-frequency cell meets the reselection criteria defined
in TS38.304 within Tdetect,NR_Intra when that Treselection= 0 . An intra frequency cell is considered to be detectable
according to the conditions defined in Annex B.1.2 for a corresponding Band.
The UE shall measure SS-RSRP and SS-RSRQ at least every Tmeasure,NR_Intra (see table 4.2.2.3-1) for intra-frequency
cells that are identified and measured according to the measurement rules.
The UE shall filter SS-RSRP and SS-RSRQ measurements of each measured intra-frequency cell using at least 2
measurements. Within the set of measurements used for the filtering, at least two measurements shall be spaced by at
least Tmeasure,NR_Intra/2.
The UE shall not consider a NR neighbour cell in cell reselection, if it is indicated as not allowed in the measurement
control system information of the serving cell.
For an intra-frequency cell that has been already detected, but that has not been reselected to, the filtering shall be such
that the UE shall be capable of evaluating that the intra-frequency cell has met reselection criterion defined [1] within
Tevaluate,NR_Intra when Treselection = 0 as specified in table 4.2.2.3-1 provided that:
- when rangeToBestCell is not configured, the cell has at least [3]dB in FR1 or [TBD]dB in FR2 better ranked or
- when rangeToBestCell is configured, the cell which has the highest number of beams above the threshold
absThreshSS-BlocksConsolidation among the cells whose cell-ranking criterion R value as specified in TS
38.304 [1, Section 5.2.4.6] is within rangeToBestCell of the R value of the best cell where the best cell has at
least [TBD] in FR1 or [TBD]dB in FR2 better ranked, and if there are multiple such cells the UE shall perform
cell reselection to the highest ranked cell among them.
When evaluating cells for reselection, the SSB side conditions apply to both serving and non-serving intra-frequency
cells.
If Treselection timer has a non-zero value and the intra-frequency cell is satisfied with the reselection criteria which are
defined in TS38.304 [1], the UE shall evaluate this intra-frequency cell for the Treselection time. If this cell remains
satisfied with the reselection criteria within this duration, then the UE shall reselect that cell.
Table 4.2.2.3-1: Tdetect,NR_Intra, Tmeasure,NR_Intra and Tevaluate,NR_Intra

DRX cycle Scaling Factor (N1) Tdetect,NR_Intra [s] Tmeasure,NR_Intra [s] Tevaluate,NR_Intra
length [s] (number of DRX (number of DRX [s] (number of DRX
FR1 FR2Note1
cycles) cycles) cycles)
0.32 [8] 11.52 x N1 x M2 (36 x 1.28 x N1 x M2 (4 x N1 5.12 x N1 x M2 (16 x
N1 x M2) x M2) N1 x M2)
0.64 1 [5] 17.92 x N1 (28 x N1) 1.28 x N1 (2 x N1) 5.12 x N1 (8 x N1)
1.28 [4] 32 x N1 (25 x N1) 1.28 x N1 (1 x N1) 6.4 x N1 (5 x N1)
2.56 [TBD] 58.88 x N1 (23 x N1) 2.56 x N1 (1 x N1) 7.68 x N1 (3 x N1)
Note 1: Applies for UE supporting power class 2&3&4. For UE supporting power class 1, N1 = [8] for all DRX cycle
length.
Note 2: M2 = 1.5 if SMTC periodicity of measured intra-frequency cell > 20 ms; otherwise M2=1.
System Simulator:
- 3 NR Cells: NR Cell 1, 2 and 4 as specified in TS 38.508-1 [4] table 4.4.2-3.
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cell.
UE:
- None.
ETSI
Preamble:
- NR Cell 1 is set to "Serving Cell" and NR Cell 2 and NR Cell 4 are set to non-suitable "Off" as defined in TS
38.508-1 [4] table 6.2.2.1-3 for FR1 and table 6.2.2.2-2 for FR2.
- The UE is in NR RRC_IDLE state (state 1N-A with PDU session inactive) as defined in TS 38.508-1 [4], table
4.4A.2-1 on NR Cell 1.
Table 6.1.2.19.3.2-1 and Table 6.1.2.19.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. The exact instants on which these values shall be
applied are described in the texts in this clause.
Parameter Unit NR Cell NR Cell NR Remark
1 2 Cell 4
SS/PBCH dBm/SC NR Cell 2 becomes the highest
T1 -94 -88 -94
SSS EPRE S ranked cell.
T2 -94 -94 -88
T3 -88 -94 -94
Parameter Unit NR Cell NR Cell NR Remark
1 2 Cell 4
T1 FFS FFS FFS
T2 FFS FFS FFS
T3 FFS FFS FFS
ETSI
ETSI

U-S Message
1 The SS changes the power level setting - - -
-
according to the row "T1".
2 Wait for 40s for FR1 or 136s for FR2 for the - - - -
UE to perform cell reselection procedure.
(Note 1, Note 5)
4 Wait for 14s for FR1 or 33s for FR2 for the UE - - - -
to perform cell reselection procedure. (Note 2,
Note 6)
6 Wait for 14s for FR1 or 33s for FR2 for the UE - - - -
to perform cell reselection procedure. (Note 3,
Note 6)
7-8 Void - - - -
9 The SS changes the TAC of NR Cell 2 to 2. - - - -
(Note 7)
RRCSetupRequest on NR Cell 2 within 6s for
FR1 and 27s for FR2 after step 11? (Note 8,
Note 9)
13- Steps 2 to 6 of the mobility registration - - - -
17 updating procedure described in TS 38.508-1
[4] Table 4.9.5.2.2-1 are performed on NR Cell
2.
18 Void - - - -
20- Void - - - -
25
(Note 12)
RRCSetupRequest on NR Cell 4 within 7s for
FR1 and 26s for FR2 after step 26? (Note 13)
28- Steps 2 to 6 of the mobility registration - - - -
32 updating procedure described in TS 38.508-1
[4] Table 4.9.5.2.2-1 are performed on NR Cell
4.
ETSI
Note 1: NCR (number of cell reselection) is 1.

Note 2: NCR is 2.
Note 3: NCR is 3 and the UE enters medium mobility state because number of cell reselections during time period
TCRmax equals NCR_M.
Note 4: Void.
Note 5: The wait time for reselection to a newly detected intra frequency cell is selected to cover
Tdetect,NR_Intra(25*1280ms=32s for FR1 and 25*4*1280ms=128s for FR2) + Treselection (7s) + 320 ms system
information block type scheduling = 39.32s rounded up to 40s for FR1 and 135.32s rounded up to 136s for
FR2.
Note 6: The wait time for reselection to an already detected intra frequency cell is selected to cover
Tevaluate,NR_intra(6.4s for FR1 and 25.6 for FR2) + Treselection (7s) + 320 ms system information block type
scheduling = 13.72s rounded up to 14s for FR1 and 32.92s rounded up to 33s for FR2.
Note 7: The wait time for evaluating an intra-frequency cell is Treselection after scaling (3.5s). This wait time is
rounded down to nearest second (i.e. 3s in this case).
Note 8: The wait time for cell reselection procedure is selected to cover Tevaluate,NR_intra (6.4s for FR1 and 25.6 for
FR2) + Treselection after scaling (7*0.5) + 320 ms system information block type scheduling = 10.22s
rounded up to 11s for FR1 and 29.42s rounded up to 30s for FR2. The actual wait time is 6s which covers
9s - 3s (wait time in step 11) for FR1 and 27s which covers 30s – 3s (wait time in step 11) for FR2.
Note 9: NCR is 4 and the UE enters high mobility state because number of cell reselections during time period
TCRmax greater than NCR_H
Note 10: Void.
Note 11: Void.
Note 12: The wait time for evaluating an intra-frequency cell is Treselection after scaling (2s).
Note 13: The wait time for cell reselection procedure is selected to cover Tevaluate,NR_intra (6.4s for FR1 and 25.6 for
FR2) + Treselection after scaling (7*0.25) + 320 ms system information block type scheduling = 8.47s
rounded up to 9s for FR1 and 27.92s rounded up to 28s for FR2. The actual wait time is 7s which covers
9s - 2s (wait time in step 26) for FR1 and 26s which covers 28s – 2s (wait time in step 26) for FR2.
Table 6.1.2.19.3.3-1: SystemInformationBlockType2 for NR Cell 1, NR Cell 2, and NR Cell 4 (preamble

and all steps, Table 6.1.2.19.3.2-3)

SIB2 ::= SEQUENCE {
{
speedStateReselectionPars SEQUENCE
{
MobilityStateParameters SEQUENCE {
t-Evaluation s240
t-HystNormal s240
n-CellChangeMedium 3
n-CellChangeHigh 3
}
q-HystSF SEQUENCE {
sf-Medium dB0
sf-High dB0
}
}
}
{
t-ReselectionNR 7
t-ReselectionNR-SF SEQUENCE {
sf-Medium oDot50
sf-High oDot25
}
}
}
ETSI
Table 6.1.2.19.3.3-2: SystemInformationBlockType1 for NR Cell 4 (step 9, Table 6.1.2.19.3.2-3)

SIB1 ::= SEQUENCE {
PLMN-IdentityInfoList SEQUENCE {
trackingAreaCode 2
}
}
}
6.1.2.20 Inter-frequency cell reselection according to cell reselection priority provided

by SIBs
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the equal
priority frequency }
then { UE reselects the cell which belongs to the equal priority frequency }
}
(2)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher
then { UE reselects the cell which belongs to the higher priority frequency }
}
(3)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the lower
then { UE reselects the cell which belongs to the lower priority frequency }
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 5.2.4.1,
5.2.4.2, 5.2.4.5 and 5.2.4.6. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.4.1]
ETSI
NAS (TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.2]
- Otherwise, the UE shall perform measurements of NR inter-frequencies or inter-RAT frequency cells of

equal or lower priority according to TS 38.133 [8].
[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
ETSI
[TS 38.304, clause 5.2.4.6]
where:

ETSI
System Simulator:
UE:
None.
Preamble:
described in the texts in this clause. The configuration "T0" indicates the initial conditions. Subsequent configurations
marked "T1", "T2" and "T3" are applied at the points indicated in the Main behaviour description in Table 6.1.2.20.3.2-
3.
T0 SS/PBCH dBm/SCS -88 Off Off The power level values are assigned to ensure
SSS EPRE the UE registered on NR Cell 1.
T1 SS/PBCH dBm/SCS -88 -78 Off The power level values are assigned to satisfy
SSS EPRE RNR Cell 1 < RNR Cell 3.
T2 SS/PBCH dBm/SCS Off -78 -78 The power level values are assigned to satisfy
SSS EPRE SrxlevNR Cell 1 < 0 and SrxlevNR Cell 6 > ThreshNR
Cell 6, high.
SSS EPRE SrxlevNR Cell 6 < Threshserving, low and SrxlevNR Cell 3
> ThreshNR Cell 3, low, SrxlevNR Cell 1< 0.
Cell 6, high.
SSS EPRE SrxlevNR Cell 6 < Threshserving, low and SrxlevNR Cell 3
> ThreshNR Cell 3, low, SrxlevNR Cell 1< 0.
ETSI

U-S Message
1 The SS changes NR Cell 3 SS PBCH SSS - - - -
EPRE level according to the row "T1" in table
6.1.2.20.3.2-1/2.
4 The SS changes NR Cell 1 and NR Cell 6 SSS - - - -
levels according to the row "T2" in table
6.1.2.20.3.2-1/2.
7 The SS changes NR Cell 6 SSS level according - - - -
to the row "T3" in table 6.1.2.20.3.2-1/2.
8 Wait for 8[FR1]/27[FR2] seconds to allow UE to - - - -
Note: The wait time at steps 2 and 5 is Kcarrier*Tdetect,NR_Inter and at Step 8 it is Kcarrier*Tevaluate,NR_Inter (as per TS 38.133
[30], clause 4.2.2.4) plus the time to read the system information TSI-NR.

SIB2 ::= SEQUENCE {
SEQUENCE {
threshServingLowP 10 20 dB
}
}
ETSI
Table 6.1.2.20.3.3-3: SIB4 of NR Cell 1, NR Cell 3 and NR Cell 6 (preamble and all steps, Table
6.1.2.20.3.2-3)

SIB4 ::= SEQUENCE {
SIZE (1..maxFreq) OF SEQUECNCE {
dl-CarrierFreq[1] Same downlink ARFCN as used NR Cell 1
for NR Cell 6
for NR Cell 6
for NR Cell 3
threshX-HighP[1] 10 20 dB NR Cell 3
and FR1
9 18 dB NR Cell 3
and FR2
cellReselectionPriority[1] 5 NR Cell 1
5 NR Cell 3
for NR Cell 3
}
}
6.1.2.21 Cell reselection, SIntraSearchQ and SnonIntraSearchQ
(1)
ensure that {
when { UE receives non-zero SIntraSearchQ in system information }
then { UE performs measurement and reselects the highest ranked cell upon Squal <
SIntraSearchQ }
}
(2)
ensure that {
when { UE receives non-zero SnonIntraSearchQ in system information }
then { UE performs measurement and reselects the cell which belongs to the equal priority
frequency cell upon Squal < SnonIntraSearchQ }
}
(3)
ensure that {
when { UE receives non-zero SnonIntraSearchQ in system information }
then { UE performs measurement and reselects the cell which belongs to the high priority
frequency cell upon Squal > SnonIntraSearchQ }
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 5.2.4.1,
5.2.4.2, 5.2.4.5, 5.2.4.6 and 5.2.4.7. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.4.1]
ETSI
NAS (TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.2]

ETSI
[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
[TS 38.304, clause 5.2.4.6]
where:

ETSI
[TS 38.304, clause 5.2.4.7]
5.2.4.7.0 General reselection parameters
Cell reselection parameters are broadcast in system information and are read from the serving cell as follows:
absThreshSS-BlocksConsolidation
This specifies minimum threshold of the beam which can be used for selection of the highest ranked cell, if
rangeToBestCell is configured.
cellReselectionPriority
This specifies the absolute priority for NR frequency or E-UTRAN frequency.
cellReselectionSubPriority
This specifies the fractional priority value added to cellReselectionPriority for NR frequency or E-UTRAN frequency.
Qoffsets,n
This specifies the offset between the two cells.
Qoffsetfrequency
Frequency specific offset for equal priority NR frequencies.
Qhyst
This specifies the hysteresis value for ranking criteria.
Qoffsettemp
This specifies the additional offset to be used for cell selection and re-selection. It is temporarily used in case the RRC
Connection Establishment fails on the cell as specified in TS 38.331 [3].
Qqualmin
This specifies the minimum required quality level in the cell in dB.
Qrxlevmin
This specifies the minimum required Rx level in the cell in dBm.
Qrxlevminoffsetcell
This specifies the cell specific Rx level offset in dB to Qrxlevmin.
Qqualminoffsetcell
ETSI
This specifies the cell specific quality level offset in dB to Qqualmin.
rangeToBestCell
This specifies the R value range which the cells whose R value is within the range can be a candidate for the highest
ranked cell.
TreselectionRAT
This specifies the cell reselection timer value. For each target NR frequency and for each RAT other than NR, a specific
value for the cell reselection timer is defined, which is applicable when evaluating reselection within NR or towards
other RAT (i.e. TreselectionRAT for NR is TreselectionNR, for E-UTRAN TreselectionEUTRA).
NOTE: TreselectionRAT is not broadcast in system information but used in reselection rules by the UE for each
RAT.
TreselectionNR
This specifies the cell reselection timer value TreselectionRAT for NR. The parameter can be set per NR frequency as
TreselectionEUTRA
This specifies the cell reselection timer value TreselectionRAT for E-UTRAN.
ThreshX, HighP
This specifies the Srxlev threshold (in dB) used by the UE when reselecting towards a higher priority RAT/ frequency
than the current serving frequency. Each frequency of NR and E-UTRAN might have a specific threshold.
ThreshX, HighQ
This specifies the Squal threshold (in dB) used by the UE when reselecting towards a higher priority RAT/ frequency
ThreshX, LowP
This specifies the Srxlev threshold (in dB) used by the UE when reselecting towards a lower priority RAT/ frequency
ThreshX, LowQ
This specifies the Squal threshold (in dB) used by the UE when reselecting towards a lower priority RAT/ frequency
ThreshServing, LowP
This specifies the Srxlev threshold (in dB) used by the UE on the serving cell when reselecting towards a lower priority
RAT/ frequency.
ThreshServing, LowQ
This specifies the Squal threshold (in dB) used by the UE on the serving cell when reselecting towards a lower priority
RAT/ frequency.
SIntraSearchP
This specifies the Srxlev threshold (in dB) for intra-frequency measurements.
SIntraSearchQ
This specifies the Squal threshold (in dB) for intra-frequency measurements.
SnonIntraSearchP
This specifies the Srxlev threshold (in dB) for NR inter-frequency and inter-RAT measurements.
SnonIntraSearchQ
ETSI
This specifies the Squal threshold (in dB) for NR inter-frequency and inter-RAT measurements.
5.2.4.7.1 Speed dependent reselection parameters
Speed dependent reselection parameters are broadcast in system information and are read from the serving cell as
follows:
TCRmax
This specifies the duration for evaluating allowed amount of cell reselection(s).
NCR_M
This specifies the maximum number of cell reselections to enter Medium-mobility state.
NCR_H
This specifies the maximum number of cell reselections to enter High-mobility state.
TCRmaxHyst
This specifies the additional time period before the UE can enter Normal-mobility state.
Speed dependent ScalingFactor for Qhyst
This specifies scaling factor for Qhyst in sf-High for High-mobility state and sf-Medium for Medium-mobility state.
Speed dependent ScalingFactor for TreselectionNR
This specifies scaling factor for TreselectionNR in sf-High for High-mobility state and sf-Medium for Medium-mobility
state.
Speed dependent ScalingFactor for TreselectionEUTRA
This specifies scaling factor for TreselectionEUTRA in sf-High for High-mobility state and sf-Medium for Medium-
mobility state.
System Simulator:
- NR Cell 1, NR Cell 2 and NR Cell 3
- System information combination NR-4 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1, and message contents
defined in clause 4.6.1 and clause 4.6.2 with QBASED condition is used in NR cells.
UE:
None.
Preamble:
marked "T1", "T2", "T3" and "T4" are applied at the points indicated in the Main behaviour description in Table
6.1.2.21.3.2-3.
ETSI
dBm/SCS -88 Off Off
T1 SS/PBCH dBm/SCS -94 -80 -118 Squal of NR Cell 1 is less than SIntraSearchQ.
SSS EPRE
RSRQ dB -13.78 -10.96 -34.81
Qrxlevmin dBm -110 -110 -110
Qqualmin dB -20 -20 -20
SIntraSearchQ dB 20 20 20
Noc dBm/SCS -94 -94 -94
Srxlev dB 16 30 -8
Squal dB 6.22 9.04 -14.81
T2 SS/PBCH dBm/SCS -118 -94 -80 Squal of NR Cell 2 is less than SnonIntraSearchQ.
SSS EPRE
RSRQ dB -34.81 -13.78 -10.96
SnonIntraSearchQ dB 20 20 20
Noc dBm/SCS -94 -94 -94
Srxlev dB -8 16 30
Squal dB -14.81 6.22 9.04
SS/PBCH dBm/SCS -118 -118 -80
T3
SSS EPRE
RSRQ dB -34.81 -34.81 -10.96
Noc dBm/SCS -94 -94 -94
Srxlev dB -8 -8 30
Squal dB -14.81 -14.81 9.04
T4 SS/PBCH dBm/SCS -80 -118 -80 Squal of NR Cell 3 is greater than
SSS EPRE SnonIntraSearchQ but NR Cell 1 is high priority cell.
RSRQ dB -10.96 -34.81 -10.96
Noc dBm/SCS -94 -94 -94
Srxlev dB 30 -8 30
Squal dB 9.04 -14.81 9.04
ETSI
dBm/SCS FFS Off Off
T1 SS/PBCH dBm/SCS FFS FFS FFS Squal of NR Cell 1 is less than
SSS EPRE SIntraSearchQ.
RSRQ dB FFS FFS FFS
Qrxlevmin dBm - - -
110+D 110+D 110+D
elta(N elta(N elta(N
Rf1) Rf1) Rf1)
SIntraSearchQ dB 20 20 20
Noc dBm/SCS FFS FFS FFS
Squal dB FFS FFS FFS
T2 SS/PBCH dBm/SCS FFS FFS FFS Squal of NR Cell 2 is less than
SSS EPRE SnonIntraSearchQ.
RSRQ dB FFS FFS FFS
Qrxlevmin dBm - - -
110+D 110+D 110+D
Rf1) Rf1) Rf1)
SS/PBCH FFS FFS FFS
T3 dBm/SCS
SSS EPRE
RSRQ dB FFS FFS FFS
Qrxlevmin dBm - - -
110+D 110+D 110+D
Rf1) Rf1) Rf1)
T4 SS/PBCH dBm/SCS FFS FFS FFS Squal of NR Cell 3 is greater than
SSS EPRE SnonIntraSearchQ but NR Cell 1 is high
RSRQ dB FFS FFS FFS priority cell.
Qrxlevmin - - -
110+D 110+D 110+D
dBm
Rf1) Rf1) Rf1)
Note: The uncertain downlink signal level is specified in TS 38.508-1 [4] section FFS
ETSI

U-S Message
according to row "T1" in table 6.1.2.21.3.2-
1/2.
the change.
to row "T2" in table 6.1.2.21.3.2-1/2.
the change.
6A The SS re-adjusts the SSS levels according - - - -
to row "T3" in table 6.1.2.21.3.2-1/2.
7 Void.
8 The SS changes the SnonIntraSearchQ for NR Cell - - - -
3 according to row "T3" in table 6.1.2.21.3.2-
1/2, The ValueTag of SIB2 in the SI-
SchedulingInfo of SIB1 is increased on NR
Cell 3.
8A The SS notifies the UE of change of System <-- NR RRC: Paging - -
Information on NR Cell 3 by send Short
9 Wait for 2.1* modification period to allow the - - -
to row "T4" in table 6.1.2.21.3.2-1/2.
11 Wait for 120 seconds to allow UE to - - - -
ETSI
Table 6.1.2.21.3.3-2: SIB2 of NR Cell 1, NR Cell 2 and NR Cell 3 (preabmle, Table 6.1.2.21.3.2-3)

SIB2 ::= SEQUENCE {
SEQUENCE {
s-NonIntraSearchQ 20 20 dB
1 NR Cell 2 and Cell
3
}
{
s-IntraSearchP 0 0 dB
s-IntraSearchQ 20 20 dB
}
}
Table 6.1.2.21.3.3-3: SIB4 of NR Cell 2 and NR Cell 3 (preabmle and all steps, Table 6.1.2.21.3.2-3)

SIB4 ::= SEQUENCE {
{
for NR Cell 3
for NR Cell 1
t-ReselectionNR 1
threshX-Q SEQUENCE { NR Cell 3
threshX-HighQ 20
threshX-LowQ 5
}
1 NR Cell 2
}
}
}

SIB1 ::= SEQUENCE {
}
ETSI
Table 6.1.2.21.3.3-4a: SIB4 of NR Cell 3 (step 8, Table 6.1.2.21.3.2-3)

SIB4 ::= SEQUENCE {
{
threshX-Q SEQUENCE { NR Cell 3
threshX-HighQ 5
threshX-LowQ 5
}
}
}
}

SchedulingInfo {
sib-MappingInfo SEQUENCE (SIZE 2 entries
type sibType2
valueTag 1
}
type sibType4
valueTag 1
}
}
}
}
}

SIB2 ::= SEQUENCE {
SEQUENCE {
s-NonIntraSearchQ 2 2 dB
}
}
6.1.2.22 Inter-frequency cell reselection based on common priority information with

parameters ThreshX, HighQ, ThreshX, LowQ and ThreshServing, LowQ
(1)
ETSI
ensure that {
}
(2)
ensure that {
then { UE reselects the cell which belongs to the lower priority frequency }
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 5.2.4.5, and
[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
[TS 38.304, clause 5.2.4.7]
ETSI
5.2.4.7.0 General reselection parameters
Cell reselection parameters are broadcast in system information and are read from the serving cell as follows:
absThreshSS-BlocksConsolidation
This specifies minimum threshold of the beam which can be used for selection of the highest ranked cell, if
rangeToBestCell is configured.
cellReselectionPriority
This specifies the absolute priority for NR frequency or E-UTRAN frequency.
cellReselectionSubPriority
This specifies the fractional priority value added to cellReselectionPriority for NR frequency or E-UTRAN frequency.
Qoffsets,n
This specifies the offset between the two cells.
Qoffsetfrequency
Frequency specific offset for equal priority NR frequencies.
Qhyst
This specifies the hysteresis value for ranking criteria.
Qoffsettemp
This specifies the additional offset to be used for cell selection and re-selection. It is temporarily used in case the RRC
Connection Establishment fails on the cell as specified in TS 38.331 [3].
Qqualmin
This specifies the minimum required quality level in the cell in dB.
Qrxlevmin
This specifies the minimum required Rx level in the cell in dBm.
Qrxlevminoffsetcell
This specifies the cell specific Rx level offset in dB to Qrxlevmin.
Qqualminoffsetcell
This specifies the cell specific quality level offset in dB to Qqualmin.
rangeToBestCell
This specifies the R value range which the cells whose R value is within the range can be a candidate for the highest
ranked cell.
TreselectionRAT
This specifies the cell reselection timer value. For each target NR frequency and for each RAT other than NR, a specific
value for the cell reselection timer is defined, which is applicable when evaluating reselection within NR or towards
other RAT (i.e. TreselectionRAT for NR is TreselectionNR, for E-UTRAN TreselectionEUTRA).
NOTE: TreselectionRAT is not broadcast in system information but used in reselection rules by the UE for each
RAT.
TreselectionNR
This specifies the cell reselection timer value TreselectionRAT for NR. The parameter can be set per NR frequency as
ETSI
TreselectionEUTRA
This specifies the cell reselection timer value TreselectionRAT for E-UTRAN.
ThreshX, HighP
This specifies the Srxlev threshold (in dB) used by the UE when reselecting towards a higher priority RAT/ frequency
ThreshX, HighQ
This specifies the Squal threshold (in dB) used by the UE when reselecting towards a higher priority RAT/ frequency
ThreshX, LowP
This specifies the Srxlev threshold (in dB) used by the UE when reselecting towards a lower priority RAT/ frequency
ThreshX, LowQ
This specifies the Squal threshold (in dB) used by the UE when reselecting towards a lower priority RAT/ frequency
ThreshServing, LowP
This specifies the Srxlev threshold (in dB) used by the UE on the serving cell when reselecting towards a lower priority
RAT/ frequency.
ThreshServing, LowQ
This specifies the Squal threshold (in dB) used by the UE on the serving cell when reselecting towards a lower priority
RAT/ frequency.
SIntraSearchP
This specifies the Srxlev threshold (in dB) for intra-frequency measurements.
SIntraSearchQ
This specifies the Squal threshold (in dB) for intra-frequency measurements.
SnonIntraSearchP
This specifies the Srxlev threshold (in dB) for NR inter-frequency and inter-RAT measurements.
SnonIntraSearchQ
This specifies the Squal threshold (in dB) for NR inter-frequency and inter-RAT measurements.
5.2.4.7.1 Speed dependent reselection parameters
Speed dependent reselection parameters are broadcast in system information and are read from the serving cell as
follows:
TCRmax
This specifies the duration for evaluating allowed amount of cell reselection(s).
NCR_M
This specifies the maximum number of cell reselections to enter Medium-mobility state.
NCR_H
This specifies the maximum number of cell reselections to enter High-mobility state.
TCRmaxHyst
ETSI
This specifies the additional time period before the UE can enter Normal-mobility state.
Speed dependent ScalingFactor for Qhyst
This specifies scaling factor for Qhyst in sf-High for High-mobility state and sf-Medium for Medium-mobility state.
Speed dependent ScalingFactor for TreselectionNR
This specifies scaling factor for TreselectionNR in sf-High for High-mobility state and sf-Medium for Medium-mobility
state.
Speed dependent ScalingFactor for TreselectionEUTRA
This specifies scaling factor for TreselectionEUTRA in sf-High for High-mobility state and sf-Medium for Medium-
mobility state.
System Simulator:
- System information combination NR-4 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1, and message contents
UE:
None.
Preamble:
marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in Table 6.1.2.22.3.2-3.
Parameter Unit NR Cell NR Cell Remark
1 3
T0 SS/PBCH dBm/SCS -88 Off The power level values are assigned to
T1 SS/PBCH dBm/SCS -88 -88 The power level values are assigned to
SSS EPRE satisfy SrxlevNR Cell 1 > 0, SrxlevNR Cell 3 <
RSRQ dB -10.76 -10.76 ThreshNR Cell 3, highP, SqualNR Cell 1 > 0 and
Qqualmin dB -20 -20 SqualNR Cell 3 > ThreshNR Cell 3, highQ.
Noc dBm/SCS -145 -145
ETSI
T2 SS/PBCH dBm/SCS -88 -94 The power level values are assigned to
SSS EPRE satisfy SrxlevNR Cell 3 > Threshserving, lowP and
RSRQ dB -10.76 -10.76 SqualNR Cell 1 > ThreshNR Cell 1, lowQ. But
Qqualmin dB -20 -20 SqualNR Cell 3 is larger than Threshserving, lowQ
Noc dBm/SCS -145 -145
T3 threshServi dB 4 26 The values are assigned to satisfy SqualNR
ngLowQ Cell 3 < Threshserving, lowQ and SqualNR Cell 3 <
thresh NR dB 20 - ThreshNR Cell 3, highQ.
Cell 3 -
HighQ
1 3
T0 SS/PBCH dBm/SCS FFS Off The power level values are assigned to
T1 SS/PBCH dBm/SCS FFS FFS The power level values are assigned to
SSS EPRE satisfy SrxlevNR Cell 1 > 0, SrxlevNR Cell 3 <
RSRQ dB FFS FFS ThreshNR Cell 3, highP, SqualNR Cell 1 > 0 and
Qqualmin dB -20 -20 SqualNR Cell 3 > ThreshNR Cell 3, highQ.
Noc dBm/SCS FFS FFS
T2 SS/PBCH dBm/SCS FFS FFS The power level values are assigned to
SSS EPRE satisfy SrxlevNR Cell 3 > Threshserving, lowP and
RSRQ dB FFS FFS SqualNR Cell 1 > ThreshNR Cell 1, lowQ. But
Qqualmin dB -20 -20 SqualNR Cell 3 is larger than Threshserving, lowQ
Noc dBm/SCS FFS FFS
T3 threshServi dB 4 26 The values are assigned to satisfy SqualNR
ngLowQ Cell 3 < Threshserving, lowQ and SqualNR Cell 3 <
thresh NR dB 20 - ThreshNR Cell 3, highQ.
Cell 3 -
HighQ
Note: The uncertain downlink signal level is specified in TS 38.508-1 [4] section FFS.
ETSI

U–S Message
level according to the row "T1" in table
6.1.2.22.3.2-1/2.
the change.
3 Check: Does the test result of generic test - - 1
4 The SS changes the SSS level according to - - - -
the row "T2" in table 6.1.2.22.3.2-1/2.
the change.
6 The SS transmits a Paging message on NR <-- NR RRC: Paging - -
Cell 1.
6A Check: Does the UE send an RRCSetup --> NR RRC: RRCSetupRequest 2 F
Request on NR Cell 1 within the next 10s?
7 The SS changes threshServingLowQ of NR - - - -
Cell 3 according to the row "T3" in table
6.1.2.22.3.2-1/2. The ValueTag of SIB2 in the
SI-SchedulingInfo of SIB1 is increased on NR
Cell 3.
The SS changes threshX-HighQ of NR Cell 1
according to the row "T3" in table 6.1.2.22.3.2-
1/2. The ValueTag of SIB4 in the SI-
SchedulingInfo of SIB1 is increased on NR
Cell 1.
The SS notifies the UE of change of System
Information on NR Cell 3 and cell1 by send SM
9 Check: Does the test result of generic test - - 2

SIB2 ::= SEQUENCE {
cellReselectionServingFreqInfo 1 entry
SEQUENCE {
threshServingLowP 1 2 dB NR Cell 3
threshServingLowQ 4 4 dB
}
}
ETSI

SIB4 ::= SEQUENCE {
{
for NR Cell 3
for NR Cell 1
q-RxLevMin -50 -100 dBm
q-QualMin -20 -20 dB
t-ReselectionNR 1
threshX-Q SEQUENCE {
threshX-HighQ 4 4 dB NR Cell 1
threshX-LowQ 2 2 dB NR Cell 3
}
4 NR Cell 3
}
}
}

SIB1 ::= SEQUENCE {
}

SchedulingInfo {
type sibType2
valueTag 1
}
}
}
}
}
ETSI

SIB2::= SEQUENCE {
cellReselectionServingFreqInfo 1 entry
SEQUENCE {
threshServingLowQ 26 26 dB
}
}

SIB1 ::= SEQUENCE {
}

SchedulingInfo {
type sibType4
valueTag 1
}
}
}
}
}

SIB4 ::= SEQUENCE {
{
dl-CarrierFreq Same downlink ARFCN as used
for NR Cell 3
threshX-HighQ 20 20dB
}
}
}
}
ETSI
6.1.2.23 Cell reselection / MFBI
(0)
with { UE is switched off }
ensure that {
when { UE is switched on a MFBI cell with the SIB1 of the first frequency band indicated in
freqBandIndicator is not supported by UE and the second frequency band indicated in
freqBandIndicator is supported by UE}
then { the UE selects the cell}
}
(1)
ensure that {
when { an equal priority NG-RAN Intra-frequency neighbouring cell which has been included in the
frequencyBandList provided by the serving cell becomes available, and, is better ranked than the
serving cell during a time interval TreselectionNR, and, more than 1 second has elapsed since the UE
camped on the current serving cell }
then { the UE reselects the new cell}
(2)
ensure that {
when { an equal priority NG-RAN Inter-frequency neighbouring cell which has been included in the
(3)
ensure that {
when { an equal priority NG-RAN Inter-band neighbouring cell which has been included in the
References: The conformance requirements covered in the present TC are specified in: TS 38.304, clause 5.2.4.2,
5.2.4.5, 5.2.4.6 and TS 38.331, clause 5.2.2.4.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.4.2]
ETSI

[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
[TS 38.304, clause 5.2.4.6]
where:
ETSI

to clause 5.2.4.4.

[TS 38.331, clause 5.2.2.4.2]
Upon receiving the SIB1 the UE shall:
1> store the acquired SIB1;
1> if in RRC_CONNECTED while T311 is not running:
2> disregard the frequencyBandList, if received, while in RRC_CONNECTED;
2> forward the cellIdentity to upper layers;
2> forward the trackingAreaCode to upper layers;
2> apply the configuration included in the servingCellConfigCommon;
1> else:
2> if the UE supports one or more of the frequency bands indicated in the frequencyBandList for downlink, and
one or more of the frequency bands indicated in the frequencyBandList for uplink for FDD, and they are not
downlink only bands, and
2> if the UE supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for a supported band in
the downlink and a supported band in uplink for FDD, and
2> if the UE supports the bandwidth of the initial uplink BWP and of the initial downlink BWPs indicated in the
locationAndBandwidth fields in uplinkConfigCommon:
3> select the first frequency band in the frequencyBandList which the UE supports and for which the UE
supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present;
ETSI
3> forward the PLMN identity to upper layers;
2> else:
3> consider the cell as barred in accordance with TS 38.304 [20]; and
3> perform barring as if intraFreqReselection is set to notAllowed;
System Simulator:
- NR Cell 1, NR Cell 2, NR Cell 3 and NR Cell 10 are configured according to TS 38.508-1 [4] Table 4.4.2-3. NR
Cell 1, NR Cell 2 and NR Cell 3 are MFBI capable cells.
- Cell 1 belongs to the frequency which overlaps between bands controlled by IXITs
px_NR_OverlappingNotSupportedBand_MFBI and px_NR_PrimaryBand.
- Cell 10 is defined by IXIT px_NR_SecondaryBand.
- System information combination NR-4 as defined in TS 38.508 [4] clause 4.4.3.1.2 is used in NR cells.
UE:
- UE does not support the px_NR_OverlappingNotSupportedBand_MFBI band.
Preamble:
- UE is in state Switched OFF (state 0N-B) according to 38.508-1 [4].
Table 6.1.2.23.3.2-1/2 illustrate the downlink power levels and other changing parameters to be applied for the cells at
texts in this clause. The configuration marked "T1", "T2", "T3", "T4" and "T5" are applied at the points indicated in the
Main behaviour description in Table 6.1.2.23.3.2-3.
ETSI
T1 SS/PBCH dBm/ -88 “Off” “Off” “Off” The power level values are assigned
SSS EPRE SCS to ensure the UE registered on NR
Cell 1.
T2 SS/PBCH dBm/ -94 -88 “Off” ”Off” The power level values are set so that
SSS EPRE SCS RCell 1 < RCell 2.
T3 SS/PBCH dBm/ "Off" -94 -80 “Off” The power level values are set so that
T4 SS/PBCH dBm/ “Off” “Off” -94 -80 The power level values are assigned
Cell 10.
T5 SS/PBCH dBm/ -80 “Off” “Off” -94 The power level values are set so that
T1 SS/PBCH dBm/ -91 “Off” “Off” “Off” The power level values are assigned
Cell 1.
T2 SS/PBCH dBm/ -91 -82 “Off” ”Off” The power level values are set so that
T3 SS/PBCH dBm/ “Off” -91 -82 “Off” The power level values are set so that
T4 SS/PBCH dBm/ “Off” “Off” -91 -82 The power level values are assigned
Cell 10.
T5 SS/PBCH dBm/ -82 “Off” “Off” -91 The power level values are set so that
ETSI

U-S Message
1 The SS changes the SS/PBCH EPRE level - - - -

3- Steps 1 to 20a1 of the registration procedure - - 0 P
22a described in TS 38.508-1 [4] Table 4.5.2.2-2
23 Wait 1 second. (to ensure than 1 second has - - - -
elapsed since the UE camped on the current
serving cell)
24 Wait for 34s for FR1 or 130s for FR2 for the
A UE to perform cell reselection procedure.
(Note 1)
26 Void
27 Void
28 Void
29- Void
48a
1
(Note 2)
52 Void
according to row "T4" in table 6.1.2.23.3.2-1/2
54 Void
55- Void
74a
1
(Note 2)
75 The test result of generic test procedure in TS
A 38.508-1 [4] clause 4.9.4 indicates that the UE
is camped on NR Cell 10.
76 Wait for 34s for FR1 or 130s for FR2 for the
A UE to perform cell reselection procedure.
(Note 2)
indicate that the UE is camped on NR Cell 1
belonging to the MFBI band
(px_NR_PrimaryBand)?
Note 1: The wait time for reselection to a newly detected intra frequency cell is selected to cover Tdetect,NR_Intra
(25*1280ms=32s for FR1 and 25*4*1280ms=128s for FR2) + TSI-NR (1.28s for FR1 and FR2) = 33.28s
rounded up to 34s for FR1 and 129.28s rounded up to 130s for FR2.
Note 2: The wait time for reselection to a newly detected inter frequency cell is selected to cover Tdetect,NR_Inter
(25*1280ms=32s for FR1 and 25*4*1280ms=128s for FR2) + TSI-NR (1.28s for FR1r and FR2) = 33.28s
ETSI
Table 6.1.2.23.3.3-1: Conditions for specific message contents in Table 6.1.2.23.3.3-4
Cell 3 This condition applies to system information transmitted on Cell 3.
Cell 10 This condition applies to system information transmitted on Cell 10.
Table 6.1.2.23.3.3-2: SIB1 for NR Cell 1, NR Cell 2 and NR Cell 3 (preamble and all steps, Table
6.1.2.23.3.2-3)

SIB1::= SEQUENCE {
servingCellConfigCommon SEQUENCE{
downlinkConfigCommon SEQUENCE{
frequencyInfoDL SEQUENCE {
frequencyBandlist SEQUENCE (SIZE 2 entries
(1.. maxNrofMultiBands)) OF NR-
MultiBandInfo {
NR-MultiBandInfo[1] SEQUENCE { entry 1
freqBandIndicatorNR An overlapping not supported

frequency band MFBI under
test
(px_NR_OverlappingNotSupp
ortedBand_MFBI).
}
freqBandIndicatorNR An overlapping Band under

test (px_NR_PrimaryBand).
}
}
}
}
}
ETSI
Table 6.1.2.23.3.3-3: SIB4 for NR Cell 1 and NR Cell 2 (preamble and all steps, Table 6.1.2.23.3.2-3)

SIB4::= SEQUENCE {
InterFreqCarrierFreqList SEQUENCE 2 entries
{
for NR Cell 10
}
{
for NR Cell 3
frequencyBandlist SEQUENCE (SIZE 1 entry
(1.. maxNrofMultiBands)) OF
MultiBandInfo {
freqBandIndicatorNR An overlapping Band under test
(px_NR_PrimaryBand).
}
}
}
}
}
Table 6.1.2.23.3.3-4: SIB4 for NR Cell 3 and NR Cell 10 (preamble and all steps, Table 6.1.2.23.3.2-3)

SIB4::= SEQUENCE {
{
for NR Cell 1
for NR Cell 10
frequencyBandList SEQUENCE (SIZE 1 entry
(1.. maxNrofMultiBands)) OF
MultiBandInfo {
freqBandIndicatorNR An overlapping Band under test NR Cell 10
(px_NR_PrimaryBand)
Band for interBand NR Cell 10 NR Cell 3

(px_NR_SecondaryBand).
}
}
}
}
}
ETSI
6.2 Multi-mode environment

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 pre-set in Automatic network selection mode }
ensure that {
when { UE is switched on and there are suitable NR and E-UTRAN cells some on the OPLMN list and
some not on the OPLMN list, none of them being part of the RPLMN }
then { UE selects the highest priority OPLMN and RAT combination, attaches on the selected
cell.}
}
(2)
with { UE in Automatic network selection mode }
ensure that {
when { UE returns to coverage and there are suitable NR and E-UTRAN cells some on the OPLMN list
and some not on the OPLMN list , none of them being part of the RPLMN }
then { UE selects the highest priority OPLMN and RAT combination, attaches on the selected cell.
}
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1 and
[TS 23.122, clause 4.4.3.1]
...
[TS 23.122, clause 4.4.3.1.1]
ETSI
System Simulator
- 3 NR cells as specified in TS 38.508-1 [4] table 4.4.2-3. System information combination NR-1 as defined in
Ts 38.508-1 [4] sub-clause 4.4.3.1.2 is applied to all the NR cells.
- 1 cell belongs to E-UTRA. System information combination 1 as defined in TS 36.508 [7] clause 4.4.3.1 is
used.
Table 6.2.1.1.3.1-1: Cell PLMN identities

Cell PLMN name
NR Cell 1 PLMN2
NR Cell 12 PLMN13
NR Cell 13 PLMN14
E-UTRA Cell 1 PLMN13
UE
- The HPLMN is PLMN1.
- USIM configuration 12 as specified in tables 6.4.1-12 in TS 38.508-1 [4] will be used.
Preamble
Table 6.2.1.1.3.2-1 for FR1 and table 6.2.1.1.3.2-2 FR2 illustrate the downlink power levels to be applied for the cells at
various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while

Paramete Unit NR Cell 1 NR Cell 12 NR Cell 13 E-UTRA Remarks
r Cell 1
T0 SS/PBCH dBm/SCS -88 "Off" -88 Power level
SSS “Off” is
EPRE defined in
TS 38.508-
1 [4] Table
6.2.2.1-3
RS EPRE dBm/15kH -85
z
T1 SS/PBCH dBm/SCS "Off" -88 -88 Power level
SSS “Off” is
EPRE defined in
TS 38.508-
1 [4] Table
6.2.2.1-3
RS EPRE dBm/15kH -85
z
ETSI

Paramete Unit NR Cell 1 NR Cell 12 NR Cell 13 E-UTRA Remarks
r Cell 1
T0 SS/PBCH dBm/SCS -82 "Off" -82 Power level
SSS “Off” is
EPRE defined in
TS 38.508-
1 [4] Table
6.2.2.1-3
RS EPRE dBm/15kH - - - -85
z
Qrxlevmin dBm -91+ - -91+ -
T1 SS/PBCH dBm/SCS "Off" -82 -82 Power level
SSS “Off” is
EPRE defined in
TS 38.508-
1 [4] Table
6.2.2.1-3
RS EPRE dBm/15kH - - - -85
z
Qrxlevmin dBm - -91+ -91+ -

U–S Message
2 Check: Does the UE send RRCSetupRequest --> NR RRC: RRCSetupRequest 1 P
on NR Cell 1?
3-20a1 Steps 3-20a1 of the registration procedure - - - -
described in TS 38.508-1 [4] table 4.5.2.2-2
of table 6.2.1.1.3.2-1.
22-28a1 Check: Does the test result of generic test - - 2 P
procedure in TS 38.508-1 [4] table 4.9.7.2.2-1
is performed and the UE is camped on E-
UTRAN Cell 1?
None.
6.2.1.2 Inter-RAT PLMN Selection / Selection of correct RAT for UPLMN / Automatic
mode
(1)
with { UE in Automatic network selection mode and UPLMN and OPLMN cells available on NR and E-UTRAN}
ensure that {
when { UE is switched on}
then { UE selects the highest priority UPLMN and RAT combination and UE attempts to register on
the selected cell }
}
(2)
with { UE in Automatic network selection mode and UPLMN and OPLMN cells available on NR and E-UTRAN}
ETSI
ensure that {
when { UE returns to coverage}
then { UE selects the highest priority VPLMN and RAT combination and UE attempts to attach on
the selected cell }
}
[TS 23.122, clause 4.4.3.1]
...
[TS 23.122, clause 4.4.3.1.1]
System Simulator
- NR Cell 1 and NR Cell 12 as specified in TS 38.508-1 [4] table 4.4.2-3 are configured as shown in Table
6.2.1.2.3.2-1. System information combination NR-1 as defined in Ts 38.508-1 [4] sub-clause 4.4.3.1.2 is
applied to all the NR cells.
- E-UTRA Cell 1 belongs to E-UTRA (defined in TS 36.508 [7]). System information combination 1 as
defined in TS 36.508 [7] clause 4.4.3.1 is used.

Cell PLMN name
NR Cell 1 PLMN2
NR Cell 12 PLMN13
UE
ETSI
Preamble

Parameter Unit NR Cell 1 NR Cell 12 E-UTRA Remarks
Cell 1
T0 SS/PBCH dBm/SCS -88 -88 -
SSS
EPRE
RS EPRE dBm/15kHz -85
T1 SS/PBCH dBm/SCS -88 "Off" - Power level
SSS “Off” is
EPRE defined in
TS 38.508-1
[4] Table
6.2.2.1-3

Parameter Unit NR Cell 1 NR Cell 12 E-UTRA Cell 1 Remarks
SSS
EPRE
RS EPRE dBm/15kHz - - -85
T1 SS/PBCH dBm/SCS -82 "Off" - Power level “Off” is
SSS defined in TS
EPRE 38.508-1 [4] Table
6.2.2.1-3
Qrxlevmin dBm -91+ - -
Delta(NRf1)
ETSI

U–S Message
2 Check: Does the UE send --> RRCSetupRequest 1 P
described in TS 38.508-1 [4] table 4.5.2.2-2
21 The SS adjusts cell levels according to row - - - -
T1 of table 6.2.1.2.3.2-1/2.
procedure in TS 38.508-1 [4] table 4.9.7.2.2-
1 is performed and the UE is camped on E-
UTRAN Cell 1 with condition 'connected
without release'?
23 At the end of this test procedure sequence, - - - -
the UE is in end state E-UTRA connected
(E2_T3440) according to TS 36.508 [7].
None.
6.2.1.3 Inter-RAT PLMN Selection / Selection of correct PLMN and RAT in shared
network environment / Automatic mode
(1)
with { UE in Automatic network selection mode and shared OPLMN cells available on NR and E-UTRAN }
ensure that {
then { UE selects the highest priority OPLMN and RAT combination and UE attempts to register on
the selected cell and PLMN }
}
(2)
with { UE in Automatic network selection mode and shared OPLMN cells available on NR and E-UTRAN }
ensure that {
when { UE returns to coverage }
then { UE selects the highest priority OPLMN and RAT combination and UE attempts to attach on
the selected cell and PLMN }
}
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. Unless otherwise stated these are Rel-15 requirements.
[TS 23.122, clause 4.4.3]
PLMN.
[TS 23.122, clause 4.4.3.1]
ETSI
...
[TS 23.122, clause 4.4.3.1.1]
System Simulator
- 2 NR cells as specified in TS 38.508-1 [4] table 4.4.2-3 are configured as shown in Table 6.2.1.3.3.2-1. System
information combination NR-1 as defined in Ts 38.508-1 [4] sub-clause 4.4.3.1.2 is applied to all the NR cells.
- 1 cell belongs to E-UTRA. System information combination 1 as defined in TS 36.508 [7] clause 4.4.3.1 is used.

Cell PLMN name
NR Cell 1 PLMN16
PLMN15
NR Cell 12 PLMN16
PLMN17
PLMN16
UE
Preamble
Table 6.2.1.3.3.2-1 for FR1 and table 6.2.1.3.3.2-2 FR2 illustrate the downlink power levels to be applied for the cells at
ETSI

T0 SS/PBCH dBm/SCS -88 -88
SSS
EPRE
T1 SS/PBCH dBm/SCS "Off" -88 Power level
SSS “Off” is defined
EPRE in TS 38.508-1
[4] Table
6.2.2.1-3

SSS
EPRE
T1 SS/PBCH dBm/SCS "Off" -82 - Power level “Off” is
EPRE [4] Table 6.2.2.1-3
Qrxlevmin dBm - -91+ -
Delta(NRf2)

U– Message
S
2 Check: Does the UE send --> NR RRC: RRCSetupRequest 1 P
described in TS 38.508-1 [4] Table 4.5.2.2-2
21 The SS adjusts cell levels according to row - - - -
T1 of table 6.2.1.3.3.2-1/2.
procedure in TS 38.508-1 [4] table 4.9.7.2.2-
1 is performed and the UE is camped on E-
UTRAN Cell 1 with condition 'connected
without release'?
23 At the end of this test procedure sequence, - - - -
the UE is in end state E-UTRA connected
ETSI
Derivation path: 38.508-1 [4] Table 4.6.1-28

SIB1 ::= SEQUENCE {
PLMN-Identity[1] SEQUENCE { entry 1
mcc PLMN16 MCC
mnc PLMN16 MNC
}
mcc PLMN15 MCC
mnc PLMN15 MNC
}
}
}
}
}
}
}
Table 6.2.1.3.3.3-2: SIB1 for NR Cell 12 (all steps, Table 6.2.1.3.3.2-)

SIB1 ::= SEQUENCE {
mcc PLMN16 MCC
mnc PLMN16 MNC
}
mcc PLMN17 MCC
mnc PLMN17 MNC
}
}
}
}
}
}
}
ETSI
Table 6.2.1.3.3.3-3: SystemInformationBlockType1 for E-UTRAN Cell 1 (all steps, Table 6.2.1.3.3.2-3)
Derivation path: 36.508[7] Table 4.4.3.2-3

SystemInformationBlockType1 ::= SEQUENCE {
plmn-IdentityList SEQUENCE (SIZE (1..6)) OF 2 entries
PLMN-IdentityInfo {
plmn-Identity PLMN17
}
plmn-Identity PLMN16
}
}
}
}
Table 6.2.1.3.3.3-4: RRCSetupComplete (Step 6, Table 6.2.1.3.3.2-3)

}
}
}
Table 6.2.1.3.3.3-5: RRCConnectionSetupComplete (Step 22, Table 6.2.1.3.3.2-3)
Derivation Path: 36.331 [11] clause 6.2.2

RRCConnectionSetupComplete ::= SEQUENCE {
c1 CHOICE {
rrcConnectionSetupComplete-r8 SEQUENCE {
}
}
}
}
6.2.1.4 Inter-RAT PLMN Selection / Selection of correct RAT from the OPLMN list /
Manual mode
(1)
with { UE in Manual network selection mode and OPLMN cells available on NR and E-UTRA}
ensure that {
when { the USER selects an OPLMN}
then { UE selects the highest priority RAT for the OPLMN and UE attempts to attach on the
selected cell and when successfully registered indicates the PLMN to the user }
}
(2)
with { UE in Manual network selection mode and OPLMN cells available on NR and E-UTRA}
ensure that {
ETSI
when { the USER selects an OPLMN and RAT combination}

then {UE attempts to attach on the selected OPLMN and RAT combination and when successfully
registered indicates the PLMN to the 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 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 location areas for roaming",
"forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for
regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking
areas 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:
- NR Cell 1 and NR Cell 12 as specified in TS 38.508-1 [4] table 4.4.2-3 are configured as shown in Table
6.2.1.2.3.2-1. System information combination NR-1 as defined in Ts 38.508-1 [4] sub-clause 4.4.3.1.2 is
applied to all the NR cells.
- E-UTRA Cell 1 belongs to E-UTRA (defined in TS 36.508 [7]). System information combination 1 as defined in
TS 36.508 [7] clause 4.4.3.1 is used.
ETSI

Cell PLMN name
NR Cell 1 PLMN2
NR Cell 12 PLMN13
E-UTRA Cell 1 PLMN2
UE
- USIM configuration 13 as specified in table 6.4.1-13 in TS 38.508-1 [4] will be used.
Preamble
- The UE is attached to PLMN1 and the UE is set to Manual PLMN selection mode before it is in state Switched
OFF (state 0N-B) according to TS 38.508-1 [4].
cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after
preamble.Configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in
Table 6.2.1.4.3.2-3.

Parameter Unit NR Cell 1 NR Cell 12 E-UTRA Cell 1
SSS
EPRE
T1 SS/PBCH dBm/SCS OFF OFF
SSS
EPRE
T2 SS/PBCH dBm/SCS -88 OFF
SSS
EPRE
RS EPRE dBm/15kHz OFF
Parameter Unit NR Cell 1 NR Cell 12 E-UTRA Cell 1

SSS
EPRE
T1 SS/PBCH dBm/SCS OFF OFF
SSS
EPRE
T2 SS/PBCH dBm/SCS -82 OFF
SSS
EPRE
RS EPRE dBm/15kHz OFF
ETSI

U–S Message
2 Make the UE display the list of available - - - -
PLMNs.
- EXCEPTION: Steps 2a1 to 2b5 describe - - - -
behaviour that depends on UE capabilities;
the "lower case letter" identifies a step
sequence that takes place if the condition is
met.
2a1 IF pc_Available_PLMNs_AcT_Ind[29] - - - -
(Support of Access Technology Indication in
available PLMNs list) THEN PLMN2 (E-
UTRAN) is selected
2a2 Check: Does the test result of generic test - - 2
procedure in TS 38.508-1 [4] table 4.5.2.2-5
UTRA Cell 1?
2a3 Check: Is PLMN2 indicated as registered - - 2 P
PLMN by the UE?
2a4 The SS adjusts the NR Cell power levels
2a5 Set the UE in Automatic PLMN selection
mode.
2b1 ELSE (No Access Technology shown to the
User)
PLMN2 is selected
2b2 Check: Does the test result of generic test - 1
procedure in TS 38.508-1 [4] table 4.5.2.2-2
is performed and the UE is camped on NR
Cell 1?
2b3 Check: Is PLMN2 indicated as registered - - 1 P
PLMN by the UE?
2b4 The SS adjusts the E-UTRA and NR Cell
power levels according to row "T2" in table
6.2.1.4.3.2-1/2.
2b5 Set the UE in Automatic PLMN selection
mode.
3 Wait for 300s to allow the UE to switch to - - - -
automatic PLMN selection mode.
None.
6.2.1.5 Inter-RAT Background HPLMN Search / Search for correct RAT for HPLMN /
Automatic Mode

with { UE in Automatic network selection mode is camped on a E-UTRAN VPLMN cell and HPLMN cell
available on NR}
ensure that {
then { UE detects NR cell and camps on the NR cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.3.1.
[TS 23.122, clause 4.4.3.3.1]
ETSI
in 3GPP TS 36.306 [54]), 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 for T is stored in the SIM, a default value of 60 minutes is used for
T.
NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using 2 hour steps from
3GPP TS 36.306 [54]); and
3GPP TS 36.306 [54]),
and
SIM, a default value of 60 minutes is used for T.

ETSI
d1) periodic attempts may be postponed while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]).
combination.
System Simulator
- E-UTRA Cell 1 as specified in TS 36.508 [7]. System information combination 1 as defined in TS 36.508 [7]
clause 4.4.3.1 is used.
- NR Cell 1 as specified in TS 38.508-1 [4] table 4.4.2-3. System information combination NR-1 as defined in TS
38.508-1 [4] sub-clause 4.4.3.1.2 is applied to the NR cell.

Cell PLMN name
NR Cell 1 PLMN1
UE
- USIM configuration 9 as specified in table 6.4.1-9 in TS 38.508-1 [4] will be used.
Preamble
- With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1
[4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using generic procedure parameter Connectivity (E-
UTRA/EPC) and Unrestricted nr PDN (On) in accordance with the procedure described in TS 38.508-1 [4],
clause 4.5.2. 4G GUTI and eKSI are assigned and security context established.
- the UE is switched-off.
- With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1
[4], Table 6.2.2.1-3, the UE is brought to state 0N-B, RRC_IDLE Connectivity (NR), in accordance with the
procedure described in TS 38.508-1 [4], Table 4.5.5.2-1. 5G-GUTI and ngKSI are assigned and security context
established.
ETSI

Parameter Unit NR Cell 1 E-UTRA Cell 1 Remarks
T0 SS/PBCH dBm/SCS "Off" Power level
EPRE in TS 38.508-1
[4] Table
6.2.2.1-3
T1 SS/PBCH dBm/SCS -88
SSS
EPRE

Parameter Unit NR Cell 1 E-UTRA Cell 1 Remarks
T0 SS/PBCH dBm/SCS "Off" Power level
EPRE in TS 38.508-1
[4] Table
6.2.2.1-3
RS EPRE dBm/15kHz - -85
Qrxlevmin dBm - -
T1 SS/PBCH dBm/SCS -82
SSS
EPRE
RS EPRE dBm/15kHz - -85
Qrxlevmin dBm -91+ -
Delta(NRf1)
ETSI

U–S Message
2 Void - - - -
3- Steps 1-10b8 of the registration procedure - - - -
12b described in TS 38.508-1 [4] table 4.5.2.2-1
8 take place on E-UTRAN Cell 1.
13- Void - - - -
18
18 SS starts timer of tmin = 2 minutes and tmax - - - -
A =6 minutes *(1+10% tolerance) (Note 1)
of table 6.2.1.5.3.2-1.
RRCSetupRequest on NR Cell 1 after tmin but
before tmax expires?
(Note 1)
20 Steps 3-4 of Table 4.5.2.2-2 of the generic
20 (Note 2)
B
behaviours which depend on procedure
parameters; the "lower case letter" identifies a
step sequence that take place if a procedure
parameter has a particular value.
1- Registration in step 20B, THEN steps 5 to
21a 20a1 of the registration procedure described in
16a TS 38.508-1 [4] Table 4.5.2.2-2 are performed
1 on NR Cell 1.
21b ELSE IF 5GS registration type is set as - - - -
1- Mobility Registration in step 20B, THEN steps
21b 4 to 11 of the tracking area update procedure
8 described in TS 38.508-1 [4] table 4.9.9.2.2-1
are performed without connection release on
NR Cell 1.
21b Steps 19a1-20a1 of the procedure described
9a1 in TS 38.508-1c [4] table 4.5.2.2-2 are
- performed with connection release on NR Cell
21b 1.
10a
1
22- Void - - - -
27a
1
Note 1: Timers tmin and tmax in step 12b are derived from the high priority PLMN search timer T defined by
EFHPPLMN. The timer tmax shall be set to 396s (6 minutes *(1+10% tolerance)), where the high priority
PLMN search timer T is defined in EFHPPLMN.
[22] subclause 5.2.3.2.5 specified in Release 16. The EXCEPTION description applies only to R15 UEs.
Table 6.2.1.5.3.3-1: REGISTRATION ACCEPT (Step 21b7 of Table 6.2.1.5.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.7.1-6.

PDU session status 0X 00 00
ETSI
6.2.2 Inter-RAT Cell Selection
6.2.2.1 Inter-RAT cell selection / From NR RRC_IDLE to EUTRA_Idle / Serving cell

becomes non-suitable
(1)
ensure that {
when { the serving cell becomes non-suitable and there is a suitable E-UTRA neighbour cell }
then { UE selects the suitable E-UTRA neighbour cell }
}
(2)
ensure that {
when { the serving cell becomes barred and there is a suitable E-UTRA neighbour cell }
then { UE selects the suitable E-UTRA neighbour cell }
}
5.2.3.1, 5.2.3.2 and TS 36.304, clause 5.2.1, 5.2.3.1, 5.2.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.1]
When evaluating Srxlev and Squal of non-serving cells for reselection evaluation purposes, the UE shall use parameters
provided by the serving cell and for the final check on cell selection criterion, the UE shall use parameters provided by
the target cell for cell reselection.
selection criteria.
for NAS.
- receive system information from the PLMN or SNPN; and
- receive registration area information from the PLMN or SNPN, e.g., tracking area information; and
- if registered:
- receive paging and notification messages from the PLMN or SNPN; and
ETSI
For cell reselection in multi-beam operations, including inter-RAT reselection from E-UTRA to NR, the measurement
- if nrofSS-BlocksToAverage (maxRS-IndexCellQual in E-UTRA) is not configured in SIB2/SIB4 (SIB24 in E-

UTRA); or
- if absThreshSS-BlocksConsolidation (threshRS-Index in E-UTRA) is not configured in SIB2/SIB4 (SIB24 in E-

UTRA); or
- if the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation

(threshRS-Index in E-UTRA):
- else:
- derive a cell measurement quantity as the linear average of the power values of up to nrofSS-
BlocksToAverage (maxRS-IndexCellQual in E-UTRA) of highest beam measurement quantity values above
absThreshSS-BlocksConsolidation (threshRS-Index in E-UTRA).
[TS 38.304, clause 5.2.3.1]
2. On each frequency, the UE need only search for the strongest cell, except for operation with shared spectrum
channel access where the UE may search for the next strongest cell(s).
[TS 38.304, clause 5.2.3.2]
where:
where:
ETSI

frequency for this cell, Qrxlevmin is obtained from q-RxLevMinSUL, if
cell.
concerned cell.
while camped normally in a VPLMN, as specified in TS 23.122 [9].
Pcompensation For FR1, if the UE supports the additionalPmax in the NR-NS-
PmaxList, if present, in SIB1, SIB2 and SIB4:
PPowerClass)) (dB);
else:
For FR2, Pcompensation is set to 0.

PmaxList respectively in SIB1, SIB2 and SIB4 for normal UL as
power class as defined in TS 38.101-1 [15].
different cell of this higher priority PLMN.
[TS 36.304, clause 5.2.1]
PLMNs. The UE shall select a suitable cell based on idle mode measurements and cell selection criteria.
In order to speed up the cell selection process, stored information for several RATs may be available in the UE.
better cell is found, that cell is selected. The change of cell may imply a change of RAT, or if the current and selected
cell are both E-UTRA cells, a change of the CN type. Details on performance requirements for cell reselection can be
found in TS 36.133 [10].
ETSI
The NAS is informed if the cell selection and reselection results in changes in the received system information relevant
for NAS.
For normal service, the UE shall camp on a suitable cell, tune to that cell's control channel(s) so that the UE can:
- Receive system information from the PLMN; and
- if registered:
- initiate transfer to connected mode.
[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 or NB-IoT 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.
NOTE 1: Priorities between different frequencies or RATs provided to the UE by system information or dedicated
NOTE 2: If BL UE, UE in enhanced coverage or NB-IoT UE has been provisioned with EARFCN, the UE may use
this information during Initial Cell Selection and Stored Information Cell Selection to find a suitable cell.
[TS 36.304, clause 5.2.3.2]
For NB-IoT the cell selection criterion is defined in clause 5.2.3.2a.
The cell selection criterion S in normal coverage is fulfilled when:

where:
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) – Pcompensation - Qoffsettemp

where:
ETSI

Qrxlevmin Minimum required RX level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
while camped normally in a VPLMN TS 23.122 [5]
PPowerClass)) (dB);
else:
if PPowerClass is 14 dBm:
max(PEMAX1 –(PPowerClass – Poffset), 0) (dB);
else:
PEMAX1, PEMAX2 Maximum TX power level an UE may use when transmitting on the
uplink in the cell (dBm) defined as PEMAX in TS 36.101 [33]. PEMAX1 and
PEMAX2 are obtained from the p-Max and the NS-PmaxList respectively
in SIB1, SIB3 and SIB5 as specified in TS 36.331 [3].
a periodic search for a higher priority PLMN while camped normally in a VPLMN TS 23.122 [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
If cell selection criterion S in normal coverage is not fulfilled for a cell, UE shall consider itself to be in enhanced
coverage if the cell selection criterion S for enhanced coverage is fulfilled, where:
Qrxlevmin UE applies coverage specific value Qrxlevmin_CE (dBm)

Qqualmin UE applies coverage specific value Qqualmin_CE (dB)
If cell selection criteria S in normal coverage is fulfilled for a cell, UE [may] consider itself to be in enhanced coverage
if SystemInformationBlockType1 cannot be acquired but UE is able to acquire MasterInformationBlock,
SystemInformationBlockType1-BR and SystemInformationBlockType2.
If cell selection criterion S in normal coverage is not fulfilled for a cell and UE does not consider itself in enhanced
coverage based on coverage specific values Qrxlevmin_CE and Qqualmin_CE, UE shall consider itself to be in enhanced
coverage if UE supports CE Mode B and CE mode B is not restricted by upper layers and the cell selection criterion S
for enhanced coverage is fulfilled, where:
Qrxlevmin UE applies coverage specific value Qrxlevmin_CE1 (dBm)

Qqualmin UE applies coverage specific value Qqualmin_CE1 (dB)
For the UE in enhanced coverage, coverage specific values Qrxlevmin_CE and Qqualmin_CE (or Qrxlevmin_CE1 and Qqualmin_CE1) are
only applied for the suitability check in enhanced coverage (i.e. not used for measurement and reselection thresholds).
System Simulator:
- E-UTRA Cell 1, NR Cell 1.
ETSI
- System information combination 31 as defined in TS 36.508-1 [7] clause 4.4.3.1 is used in E-UTRA Cell.
- System information combination NR-6 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR Cell.
UE:
- None.
Preamble:
[4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using generic procedure parameters Connectivity (E-
[4], Table 6.2.2.1-3, the UE is brought to state 1N-A, RRC_IDLE Connectivity (NR), in accordance with the
established.
texts in this clause. Row marked "T0" denotes the conditions in the preamble. Configurations marked "T1", "T2" and
Table 6.2.2.1.3.2-1: Time instances of cell power level and parameter changes for E-UTRA Cell 1 and
NR Cell 1 in FR1
Parameter Unit E-UTRA NR Remark
Cell 1 Cell 1
T0 Cell-specific The power level values are assigned to
dBm/15kHz Off -
RS EPRE ensure UE registered on NR cell 1
SS/PBCH
dBm/SCS - -85
SSS EPRE
T1 Cell-specific The power level value is such to satisfy
dBm/15kHz -85 -
RS EPRE SrxlevNR cell 1 < 0 and ensure UE
SS/PBCH registered on E-UTRA cell 1
dBm/SCS - -115
SSS EPRE
dBm/15kHz Off -
SS/PBCH
dBm/SCS - -85
SSS EPRE
dBm/15kHz -85 -
RS EPRE ensure UE registered on E-UTRA cell 1
SS/PBCH
dBm/SCS - -85
SSS EPRE
Note1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3.
NR Cell 1 in FR2
Cell 1 Cell 1
dBm/15kHz Off -
SS/PBCH
dBm/SCS - FFS
SSS EPRE
ETSI

dBm/15kHz FFS -
RS EPRE SrxlevNR cell 1 < 0 and ensure UE
SS/PBCH registered on E-UTRA cell 1
dBm/SCS - FFS
SSS EPRE
dBm/15kHz Off -
SS/PBCH
dBm/SCS - FFS
SSS EPRE
dBm/15kHz FFS -
SS/PBCH
dBm/SCS - FFS
SSS EPRE

U-S Message
1 The SS adjusts the E-UTRA and NR Cells power - - - -
levels according to row "T1" in table 6.2.2.1.3.2-
1/2.
indicate that the UE is camped on E-UTRA Cell
1?
1/2.
UE is camped on NR Cell 1. (NOTE 1)
5 The SS changes SIB1 of NR Cell 1 according to <-- PDCCH (DCI 1_0): Short - -
table 6.2.2.1.3.3-3 and notifies the UE of change Message
of System Information on NR Cell 1 by sending
Short Message on PDCCH using P-RNTI.
6 Wait for 2.1* modification period to allow the new - - - -
system information to take effect.
7 The SS adjusts the NR and E-UTRAN Cell - - - -
6.2.2.1.3.2-1/2.
1?
Note 1: This is the first time in this test case that the UE moves from S1 to N1.
Table 6.2.2.1.3.3-1: SIB5 of NR Cell 1(preamble and all steps, Table 6.2.2.1.3.2-3)

SIB5 ::= SEQUENCE {
carrierFreqListEUTRA SEQUENCE (SIZE 1 entry
(1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA {
CarrierFreqEUTRA[1] SEQUENCE { entry 1
carrierFreq Downlink EUTRA
ARFCN as E-UTRA Cell
1 used
}
}
}
ETSI
Table 6.2.2.1.3.3-2: SystemInformationBlockType24 of EUTRA Cell 1 (preamble and all steps, Table
6.2.2.1.3.2-3)
Derivation path: TS 36.508 [7], Table 4.4.3.3-20

SystemInformationBlockType24-r15 ::= SEQUENCE {
carrierFreqListNR-r15 SEQUENCE (SIZE 1 entry
(1..maxFreq)) OF CarrierFreqNR-r15 {
CarrierFreqNR-r15[1] SEQUENCE { entry 1
carrierFreq-r15 Same downlink SSB ARFCN
as used for NR Cell 1
}
}
}
Table 6.2.2.1.3.3-3: SIB1 for NR Cell 1 (step 5, Table 6.2.2.1.3.2-3)

SIB1 ::= SEQUENCE {
cellReservedForOtherUse true The UE shall treat this
cell as if cell status is
"barred"
}
}
Table 6.2.2.1.3.3-4: REGISTRATION REQUEST (step 4, Table 6.2.2.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.9.9.2.3-1.

EPS NAS message container TRACKING AREA See Table
UPDATE REQUEST 6.2.2.1.3.3-5
message
Table 6.2.2.1.3.3-5: TRACKING AREA UPDATE REQUEST (Table 6.2.2.1.3.3-4)
Derivation Path: TS 38.508-1 [4], Table 4.9.9.2.3-2 with condition Mapped EPS security context.
6.2.2.2 Inter-RAT cell selection / From E-UTRA_Idle to NR RRC_IDLE / Serving cell

becomes non-suitable
(1)
with { UE in E-UTRA RRC_IDLE state }
ensure that {
when { the serving cell becomes non-suitable and there is a suitable NR neighbour cell }
then { UE selects the suitable NR neighbour cell }
}
(2)
ensure that {
when { the serving cell becomes barred and there is a suitable NR neighbour cell }
then { UE selects the suitable NR neighbour cell }
}
ETSI
5.2.3.1, 5.2.3.2 and TS 36.304, clause 5.2.1, 5.2.3.1, 5.2.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.1]
selection criteria.
for NAS.
- receive system information from the PLMN or SNPN; and
- receive registration area information from the PLMN or SNPN, e.g., tracking area information; and
- if registered:
- receive paging and notification messages from the PLMN or SNPN; and
For cell reselection in multi-beam operations, including inter-RAT reselection from E-UTRA to NR, the measurement
- if nrofSS-BlocksToAverage (maxRS-IndexCellQual in E-UTRA) is not configured in SIB2/SIB4 (SIB24 in E-

UTRA); or
- if absThreshSS-BlocksConsolidation (threshRS-Index in E-UTRA) is not configured in SIB2/SIB4 (SIB24 in E-

UTRA); or
- if the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation

(threshRS-Index in E-UTRA):
- else:
BlocksToAverage (maxRS-IndexCellQual in E-UTRA) of highest beam measurement quantity values above
absThreshSS-BlocksConsolidation (threshRS-Index in E-UTRA).
[TS 38.304, clause 5.2.3.1]
ETSI
2. On each frequency, the UE need only search for the strongest cell, except for operation with shared spectrum
channel access where the UE may search for the next strongest cell(s).
[TS 38.304, clause 5.2.3.2]
where:
where:
ETSI

cell.
concerned cell.
Pcompensation For FR1, if the UE supports the additionalPmax in the NR-NS-
PmaxList, if present, in SIB1, SIB2 and SIB4:
PPowerClass)) (dB);
else:
For FR2, Pcompensation is set to 0.

[TS 36.304, clause 5.2.1]
PLMNs. The UE shall select a suitable cell based on idle mode measurements and cell selection criteria.
In order to speed up the cell selection process, stored information for several RATs may be available in the UE.
better cell is found, that cell is selected. The change of cell may imply a change of RAT, or if the current and selected
cell are both E-UTRA cells, a change of the CN type. Details on performance requirements for cell reselection can be
found in TS 36.133 [10].
ETSI
The NAS is informed if the cell selection and reselection results in changes in the received system information relevant
for NAS.
For normal service, the UE shall camp on a suitable cell, tune to that cell's control channel(s) so that the UE can:
- Receive system information from the PLMN; and
- if registered:
- initiate transfer to connected mode.
[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 or NB-IoT 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.
NOTE 1: Priorities between different frequencies or RATs provided to the UE by system information or dedicated
NOTE 2: If BL UE, UE in enhanced coverage or NB-IoT UE has been provisioned with EARFCN, the UE may use
this information during Initial Cell Selection and Stored Information Cell Selection to find a suitable cell.
[TS 36.304, clause 5.2.3.2]
For NB-IoT the cell selection criterion is defined in clause 5.2.3.2a.
The cell selection criterion S in normal coverage is fulfilled when:
where:
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset) – Pcompensation - Qoffsettemp

where:
ETSI

Qrxlevmin Minimum required RX level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
PPowerClass)) (dB);
else:
if PPowerClass is 14 dBm:
max(PEMAX1 –(PPowerClass – Poffset), 0) (dB);
else:
PEMAX1, PEMAX2 Maximum TX power level an UE may use when transmitting on the
uplink in the cell (dBm) defined as PEMAX in TS 36.101 [33]. PEMAX1 and
PEMAX2 are obtained from the p-Max and the NS-PmaxList respectively
in SIB1, SIB3 and SIB5 as specified in TS 36.331 [3].
a periodic search for a higher priority PLMN while camped normally in a VPLMN TS 23.122 [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
If cell selection criterion S in normal coverage is not fulfilled for a cell, UE shall consider itself to be in enhanced
coverage if the cell selection criterion S for enhanced coverage is fulfilled, where:
Qrxlevmin UE applies coverage specific value Qrxlevmin_CE (dBm)

Qqualmin UE applies coverage specific value Qqualmin_CE (dB)
If cell selection criteria S in normal coverage is fulfilled for a cell, UE [may] consider itself to be in enhanced coverage
if SystemInformationBlockType1 cannot be acquired but UE is able to acquire MasterInformationBlock,
SystemInformationBlockType1-BR and SystemInformationBlockType2.
If cell selection criterion S in normal coverage is not fulfilled for a cell and UE does not consider itself in enhanced
coverage based on coverage specific values Qrxlevmin_CE and Qqualmin_CE, UE shall consider itself to be in enhanced
coverage if UE supports CE Mode B and CE mode B is not restricted by upper layers and the cell selection criterion S
for enhanced coverage is fulfilled, where:
Qrxlevmin UE applies coverage specific value Qrxlevmin_CE1 (dBm)

Qqualmin UE applies coverage specific value Qqualmin_CE1 (dB)
For the UE in enhanced coverage, coverage specific values Qrxlevmin_CE and Qqualmin_CE (or Qrxlevmin_CE1 and Qqualmin_CE1) are
only applied for the suitability check in enhanced coverage (i.e. not used for measurement and reselection thresholds).
System Simulator:
ETSI
UE:
- None.
Preamble:
established.
- The UE is switched-off
NR Cell 1 in FR1
Cell 1 Cell 1
dBm/15kHz -85 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -115 -
RS EPRE SrxlevE-UTRA cell 1 < 0 and ensure UE
SS/PBCH registered on NR cell 1
dBm/SCS - -85
SSS EPRE
dBm/15kHz -85 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -85 -
SS/PBCH
dBm/SCS - -85
SSS EPRE
NR Cell 1 in FR2
Cell 1 Cell 1
dBm/15kHz FFS -
SS/PBCH
dBm/SCS - Off
SSS EPRE
ETSI

dBm/15kHz FFS -
RS EPRE SrxlevE-UTRA cell 1 < 0 and ensure UE
SS/PBCH registered on NR cell 1
dBm/SCS - FFS
SSS EPRE
dBm/15kHz FFS -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz FFS -
SS/PBCH
dBm/SCS - FFS
SSS EPRE

U-S Message
1/2.
indicate that the UE is camped on NR Cell 1?.
(NOTE 1)
1/2.
UE is camped on E-UTRA Cell 1.
5 The SS changes SystemInformationBlockType1 <-- Paging - -
of E-UTRA Cell 1 according to table 6.2.2.2.3.3-
3 and notifies the UE of change of System
Information on E-UTRA Cell 1.
1/2.
Note 1: This is the first time in this test case that the UE moves from S1 to N1.

SIB5 ::= SEQUENCE {
carrierFreqListEUTRA SEQUENCE (SIZE
1 used
}
}
}
ETSI
6.2.2.2.3.2-3)

}
}
}
Table 6.2.2.2.3.3-3: SystemInformationBlockType1 for E-UTRA Cell 1 (step 5, Table 6.2.2.2.3.2-3)
Derivation Path: TS 36.508-1 [7], Table 4.4.3.2-3

SystemInformationBlockType1 ::=
SEQUENCE {
cellBarred barred
}
}
Table 6.2.2.2.3.3-4: REGISTRATION REQUEST (step 4, Table 6.2.2.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.9.9.2.3-1.

message
Derivation Path: TS 38.508-1 [4], Table 4.9.9.2.3-2 with condition Mapped EPS security context.
6.2.3 Inter-RAT Cell Reselection
6.2.3.1 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE (lower

priority & higher priority, Srxlev based)
6.2.3.1.1 Test Purpose (TP)`
(1)
with { UE in E-UTRA RRC_Idle state }
ensure that {
priority inter-RAT NR cell }
then { UE reselects the cell which belongs to the lower priority inter-RAT NR cell }
}
(2)
with { UE in E-UTRA RRC_Idle state }
ensure that {
priority inter-RAT NR cell }
ETSI
then { UE reselects the cell which belongs to the higher priority inter-RAT NR cell }
}
5.2.4.2 and 5.2.4.5. Unless otherwise stated these are Rel-15 requirements.
[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 and deprioritisationReq received in RRCConnectionReject 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 any of the network
configured values). While the UE is camped on a suitable CSG cell in normal coverage, the UE shall always consider
the current frequency to be the highest priority frequency (i.e. higher than any of the network configured values),
irrespective of any other priority value allocated to this frequency. When the HSDN capable UE is in High-mobility
state, the UE shall always consider the HSDN cells to be the highest priority (i.e. higher than any other network
configured priorities). When the HSDN capable UE is not in High-mobility state, the UE shall always consider HSDN
cells to be the lowest priority (i.e. lower than network configured priorities). If the UE capable of sidelink
communication is configured to perform sidelink communication and can only perform the sidelink communication
while camping on a frequency, the UE may consider that frequency to be the highest priority. If the UE capable of V2X
sidelink communication is configured to perform V2X sidelink communication and can only perform the V2X sidelink
communication while camping on a frequency, the UE may consider that frequency to be the highest priority. If the UE
capable of V2X sidelink communication is configured to perform V2X sidelink communication and can only use pre-
configuration while not camping on a frequency, the UE may consider the frequency providing inter-carrier V2X
sidelink configuration to be the highest priority. If the UE capable of sidelink discovery is configured to perform Public
Safety related sidelink discovery and can only perform the Public Safety related sidelink discovery while camping on a
frequency, the UE may consider that frequency to be the highest priority.
NOTE 1: The prioritization among the frequencies which UE considers to be the highest priority frequency is left to
UE implementation.
If the UE is capable either of MBMS Service Continuity or of SC-PTM reception and is receiving or interested to
receive an MBMS service and can only receive this MBMS service while camping on a frequency on which it is
provided, the UE may consider that frequency to be the highest priority during the MBMS session TS 36.300 [2] as
long as the two following conditions are fulfilled:
1) Either:
- the UE is capable of MBMS service continuity and the reselected cell is broadcasting SIB13; or
- the UE is capable of SC-PTM reception and the reselected cell is broadcasting SIB20;
2) Either:
- SIB15 of the serving cell indicates for that frequency one or more MBMS SAIs included and associated with that
frequency in the MBMS User Service Description (USD) TS 26.346 [22] of this service; or
- SIB15 is not broadcast in the serving cell and that frequency is included in the USD of this service.
receive an MBMS service provided on a downlink only MBMS frequency, on a frequency used by dedicated MBMS
cells, on a frequency used by FeMBMS/Unicast-mixed cells as defined in TS 36.300 [2], or on a frequency belonging to
PLMN different from its registered PLMN, the UE may consider cell reselection candidate frequencies at which it can
not receive the MBMS service to be of the lowest priority during the MBMS session TS 36.300 [2], as long as the
above mentioned condition 1) is fulfilled for the cell on the MBMS frequency which the UE monitors or this cell
broadcasts SIB1-MBMS and as long as the above mentioned condition 2) is fulfilled for the serving cell.
ETSI
NOTE 2: Example scenarios in which the previous down-prioritisation may be needed concerns the cases where
camping is not possible, while the UE can only receive this MBMS frequency when camping on a subset
of cell reselection candidate frequencies, e.g. the MBMS frequency is a downlink only carrier, the MBMS
frequency is used by dedicated MBMS cells, the MBMS frequency is used by FeMBMS/Unicast-mixed
cells TS 36.300 [2], or the MBMS frequency belongs to a PLMN different from UE's registered PLMN.
If the UE is not capable of MBMS Service Continuity but has knowledge on which frequency an MBMS service of
interest is provided, it may consider that frequency to be the highest priority during the MBMS session TS 36.300 [2] as
long as the reselected cell is broadcasting SIB13.
If the UE is not capable of MBMS Service Continuity but has knowledge on which downlink only frequency, on which
frequency used by dedicated MBMS cells, on which frequency used by FeMBMS/Unicast-mixed cells as defined in TS
36.300 [2] or on which frequency belonging to PLMN different from its registered PLMN an MBMS service of interest
is provided, it may consider cell reselection candidate frequencies at which it can not receive the MBMS service to be
of the lowest priority during the MBMS session TS 36.300 [2] as long as the cell on the MBMS frequency which the
UE monitors is broadcasting SIB13 or SIB1-MBMS.
NOTE 3: The UE considers that the MBMS session is ongoing using the session start and end times as provided by
upper layers in the USD i.e. the UE does not verify if the session is indicated on MCCH.
In case UE receives RRCConnectionReject with deprioritisationReq, UE shall consider current carrier frequency and
stored frequencies due to the previously received RRCConnectionReject with deprioritisationReq or all the frequencies
of EUTRA to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is
running irrespective of camped RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection
is performed on request by NAS TS 23.122 [5].
NOTE 4: Connecting to CDMA2000 does not imply PLMN selection.
NOTE 5: UE should search for a higher priority layer for cell reselection as soon as possible after the change of
- a PLMN selection is performed on request by NAS TS 23.122 [5].
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.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e., T320 in E-
UTRA and NR, T322 in UTRA and T3230 in GERAN), if configured, at inter-RAT cell (re)selection.
information.
While T360 is running, redistribution target is considered to be the highest priority (i.e. higher than any of the network
configured values). UE shall continue to consider the serving frequency as the highest priority until completion of E-
UTRAN Inter-frequency Redistribution procedure specified in 5.2.4.10 if triggered on T360 expiry/ stop.
[TS 36.304, clause 5.2.4.2]
For NB-IoT measurement rules for cell re-selection is defined in sub-clause 5.2.4.2.a.
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided
by the serving cell.
ETSI
- 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 or inter-RAT frequencies according to TS 36.133 [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:
perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency cells of equal or lower
priority unless the UE is triggered to measure an E-UTRAN inter-frequency which is configured with
redistributionInterFreqInfo.
- Otherwise, the UE shall perform measurements of E-UTRAN inter-frequencies or inter-RAT frequency

cells of equal or lower priority according to TS 36.133 [10].
- If the UE supports relaxed monitoring and s-SearchDeltaP is present in SystemInformationBlockType3, the UE may
further limit the needed measurements, as specified in sub-clause 5.2.4.12.
[TS 36.304, clause 5.2.4.5]
For NB-IoT inter-frequency cell reselection shall be based on ranking as defined in sub-clause 5.2.4.6.
If threshServingLowQ is provided in SystemInformationBlockType3 and more than 1 second has elapsed since the UE
camped on the current serving cell, 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, NR or UTRAN FDD RAT/ frequency fulfils Squal > ThreshX, HighQ during
a time interval TreselectionRAT; or
- A cell of a higher priority UTRAN TDD, GERAN or CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, HighP
during a time interval TreselectionRAT.
Otherwise, cell reselection to a cell on a higher priority E-UTRAN frequency or inter-RAT frequency than the serving
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.
camped on the current serving cell, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT
- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority EUTRAN, NR or UTRAN FDD
RAT/ frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT; or
- The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority UTRAN TDD, GERAN or
CDMA2000 RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT.
Otherwise, cell reselection to a cell on a lower priority E-UTRAN frequency or inter-RAT frequency than the serving
ETSI
Cell reselection to a higher priority RAT/ frequency shall take precedence over a lower priority RAT/ frequency, if
The UE shall not perform cell reselection to NR or UTRAN FDD cells for which the cell selection criterion S is not
fulfilled.
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, ThreshX, HighP and ThreshX, LowP are equal to -1 times the values signalled for the corresponding
parameters in the system information.
In all the above criteria the value of TreselectionRAT 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 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 clause 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.
Cell reselection to another RAT, for which Squal based cell reselection parameters are broadcast in system information,
shall be performed based on the Squal criteria if the UE supports Squal (RSRQ) based cell reselection to E-UTRAN
from all the other RATs provided by system information which UE supports. Otherwise, cell reselection to another
RAT shall be performed based on Srxlev criteria.
Cell reselection to NR, for which a cell reselection parameter, q-RxLevMinSUL is broadcast in system information and
the UE supports SUL, shall be performed based on Srxlev criteria taking the parameter into account.
System Simulator:
UE:
- None.
Preamble:
established.
- the UE is switched-off
ETSI
NR Cell 1 in FR1
Cell 1 Cell 1
dBm/15kHz -85 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -95 -
RS EPRE satisfy both SrxlevNR Cell 1 > Threshx, low
SS/PBCH and SrxlevE-UTRA Cell 1 < Threshserving, low
dBm/SCS - -80
SSS EPRE
dBm/15kHz -80 -
SS/PBCH , SrxlevE-UTRA Cell 1 > Threshx, high
dBm/SCS - -95
SSS EPRE
T3 Cell-specific The Priority and power level values are
dBm/15kHz -95 -
RS EPRE assigned to satisfy SrxlevNR Cell 1 >
SS/PBCH Threshx, high
dBm/SCS - -80
SSS EPRE
NR Cell 1 in FR2
Parameter Unit E-UTRA NRCell 1 Remark

Cell 1
dBm/15kHz FFS -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz FFS -
dBm/SCS - FFS
SSS EPRE
dBm/15kHz FFS -
SS/PBCH , SrxlevE-UTRA Cell 1 > Threshx, high
dBm/SCS - FFS
SSS EPRE
T3 Cell-specific The Priority and power level values are
dBm/15kHz FFS -
RS EPRE assigned to satisfy SrxlevNR Cell 1 >
SS/PBCH Threshx, high
dBm/SCS - FFS
SSS EPRE
ETSI

U-S Message
1 The SS adjusts the E-UTRAN and NR Cell - - - -
6.2.3.1.3.2-1/2.
change.
4 Void. - - - -
6.2.3.1.3.2-1/2.
change.
UE is camped on E-UTRAN Cell 1.
8 The SS notifies the UE of change of System <-- Paging - -
Information on E-UTRAN Cell 1.
9 The SS changes Priority of NR cell 1 in - - - -
SystemInformationBlockType24. And the
systemInfoValueTag in the
SystemInformationBlockType1 of E-UTRA Cell
1 is increased.
10 Wait for 6 s for UE to receive system - - - -
information.
11 The SS re-adjusts the E-UTRAN and NR Cell - - - -
levels according to row "T3" in table
6.2.3.1.3.2-1/2.
13 Void. - - - -
6.2.3.1.3.2-3)
Derivation Path: TS 36.508 [7], Table 4.4.3.3-2

cellReselectionServingFreqInfo SEQUENCE {
threshServingLow 10 20 dB
}
}
ETSI
Table 6.2.3.1.3.3-2: SystemInformationBlockType24 of EUTRA Cell 1 (preamble, Table 6.2.3.1.3.2-3)

carrierFreq-r15 Downlink NR ARFCN of
SSB for NR Cell 1
cellReselectionPriority-r15 3
threshX-High-r15 20 40 dB
threshX-Low-r15 10 20 dB
}
}
t-ReselectionNR-r15 7
}

SIB2 ::= SEQUENCE {
}
}

SIB5 ::= SEQUENCE {
1 used
threshX-High 10 20 dB
threshX-Low 20 40 dB
}
}
t-ReselectionEUTRA 7
}
Table 6.2.3.1.3.3-5: Paging (step 8, Table 6.2.3.1.3.2-3)
Derivation path: TS 36.508 [7], Table 4.6.1-7

Paging ::= SEQUENCE {
systemInfoModification True
}
ETSI
Table 6.2.3.1.3.3-6: SystemInformationBlockType1 of EUTRA Cell 1 (step 9, Table 6.2.3.1.3.2-3)

systemInfoValueTag 1 Previous value is 0
}
Table 6.2.3.1.3.3-7: SystemInformationBlockType24 of EUTRA Cell 1 (step 9, Table 6.2.3.1.3.2-3)

}
}
t-ReselectionNR-r15 7 7 Seconds
}
Table 6.2.3.1.3.3-8: TRACKING AREA UPDATE REQUEST (Step 7, Table 6.2.3.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.9.7.2.3-1

EPS update type
EPS update type Value '010'B Combined TA/LA combined_T
updating A_LA
'000'B TA updating TA_only
NOTE: The message shall be integrity protected using the 5GS security context available in the UE.
TA_only This condition applies if the UE is configured to initiate EPS attach
or if explicitly specified.
combined_TA_LA This condition applies if the UE is configured to initiate combined
EPS/IMSI attach or if explicitly specified.
Table 6.2.3.1.3.3-9: REGISTRATION REQUEST (Step 12, Table 6.2.3.1.3.2-3)

message
Derivation Path: TS 38.508-1 [4], Table 4.9.9.2.3-2 with condition Mapped EPS security context
ETSI
6.2.3.2 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE (lower

priority & higher priority, Squal based)
(1)
ensure that {
priority inter-RAT NR cell}
then { UE reselects the cell which belongs to the lower priority inter-RAT NR cell }
}
(2)
ensure that {
priority inter-RAT NR cell}
then { UE reselects the cell which belongs to the higher priority inter-RAT NR cell }
}
[TS 36.304, clause 5.2.4.1]
UE implementation.
1) Either:
ETSI
2) Either:
ETSI
information.
[TS 36.304, clause 5.2.4.2]

[TS 36.304, clause 5.2.4.5]
and
ETSI
fulfilled.
System Simulator:
- E-UTRA Cell 1 and NR Cell 1.
- System information combination 31 as defined in TS 36.508 [7] clause 4.4.3.1, and message contents defined
in clause 4.4.3.3 with QBASED condition is used in E-UTRA cell.
defined in clause 4.6.1 and clause 4.6.2 with QBASED condition is used in NR Cell.
UE:
None.
Preamble:
ETSI
With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1
established.
The UE is switched-off.
With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1
clause 4.5.2. 4G-GUTI and eKSI are assigned and security context established.
texts in this clause. Configurations marked "T1","T2" and "T3" are applied at the points indicated in the Main behaviour
description in Table 6.2.3.2.3.2-3.
Table 6.2.3.2.3.2-1: Time instances of cell power level and parameter changes for E-UTRA Cell and
NR Cell in FR1
Cell 1 Cell 1
Cell-specific The power level values are assignen to
dBm/15kHz -95 -
RS EPRE ensure UE reselected to NR Cell 1: both
SS/PBCH Squal ServingCell, E-UTRA Cell1 < ThreshServing,
dBm/SCS - -80
SSS EPRE LowQ and SqualnonServingCell, NR Cell1 > ThreshNR
T1
RSRQ dB -11.46 -11.17 Cell1,LowQ
Qqualmin dB -20 -25
NocE-UTRA dBm/15kHz -95 -
NocNR dBm/SCS - -90
dBm/15kHz -80 -
RS EPRE ensure UE reselected back to E-UTRA Cell
SS/PBCH 1: Squal nonServingCell, E-UTRA Cell1 > ThreshE-
dBm/SCS - -95
SSS EPRE UTRA Cell1, HighQ
T2
RSRQ dB -3.76 -16.98
Qqualmin dB -20 -25
NocNR dBm/SCS - -90
dBm/15kHz -95 -
RS EPRE ensure UE reselected to NR Cell 1: Squal
SS/PBCH nonServingCell, NR Cell1 > Thresh NR Cell1, HighQ
dBm/SCS - -80
SSS EPRE
T3
RSRQ dB -11.46 -11.17
Qqualmin dB -20 -25
NocNR dBm/SCS - -90
NR Cell in FR2
Cell 1 Cell 1
dBm/15kHz FFS -
RS EPRE ensure UE reselected to NR Cell 1: both
SS/PBCH Squal ServingCell, E-UTRA Cell1 < ThreshServing,
dBm/SCS - FFS
SSS EPRE LowQ and SqualnonServingCell, NR Cell1 > ThreshNR
T1
RSRQ dB FFS FFS Cell1,LowQ
Qqualmin dB -20 -25
NocE-UTRA dBm/15kHz FFS -
NocNR dBm/SCS - FFS
ETSI

dBm/15kHz FFS -
RS EPRE ensure UE reselected back to E-UTRA Cell
SS/PBCH 1: Squal nonServingCell, E-UTRA Cell1 > ThreshE-
dBm/SCS - FFS
SSS EPRE UTRA Cell1, HighQ
T2
RSRQ dB FFS FFS
Qqualmin dB -20 -25
NocNR dBm/SCS - FFS
dBm/15kHz FFS -
RS EPRE ensure UE reselected to NR Cell 1: Squal
SS/PBCH nonServingCell, NR Cell1 > Thresh NR Cell1, HighQ
dBm/SCS - FFS
SSS EPRE
T3
RSRQ dB FFS FFS
Qqualmin dB -20 -25
NocNR dBm/SCS - FFS

U-S Message
1 The SS changes Cell-specific RS EPRE level - - - -
for E-UTRA Cell 1 and SS/PBCH SSS EPRE
level for NR Cell 1 according to row "T1" in
table 6.2.3.2.3.2-1/2.
2 Check: Does the test result of generic test 1 -
NOTE: This is the first time in this test case
that the UE moves from S1 to N1.
3 The SS transmits an RRCRelease message <-- NR RRC: RRCRelease
on NR Cell 1.
table 6.2.3.2.3.2-1/2.
5 The UE selects E-UTRAN Cell 1 and performs - - - -
the generic test procedure in TS 38.508-1 [4]
Table 4.9.7.2.2 from steps 1-6.
6 The SS transmits an RRCConnectionRelease <-- E-UTRA RRC: - -
message to release RRC connection and RRCConnectionRelease
move to RRC_IDLE on E-UTRAN Cell 1.
7 The SS changes the NR cell priority broadcast - - - -
in system information on E-UTRAN Cell 1.
8 Notify UE change of System Information on E- <-- E-UTRA RRC: Paging
UTRAN Cell 1.
information.
table 6.2.3.2.3.2-1/2.
12 Void. - - - -
ETSI
Table 6.2.3.2.3.3-1: SystemInformationBlockType1 for E-UTRA Cell 1 (preamble and all steps, Table
6.2.3.2.3.2-3)
Derivation path: TS 36.508-1 [7], Table 4.4.3.2-3

nonCriticalExtension SEQUENCE {
cellSelectionInfo-v920 SEQUENCE {
q-QualMin-r9 -20
}
}
}
}
Table 6.2.3.2.3.3-2:SystemInformationBlockType3 for E-UTRA Cell 1 (preamble and all steps, Table
6.2.3.2.3.2-3)

lateNonCriticalExtension {
q-QualMin-r9 -20
threshServingLowQ-r9 12
}
}
Table 6.2.3.2.3.3-3:SystemInformationBlockType24 for E-UTRA Cell 1 (preamble, Table 6.2.3.2.3.2-3)

SystemInformationBlockType24-r15 ::= SEQUENCE
{
carrierFreq-r15 Downlink NR
ARFCN of SSB
for NR Cell 1
threshX-Q-r15 SEQUENCE {
threshX-HighQ-r15 20
threshX-LowQ-r15 5
}
q-QualMin-r15 -25
}
}
}
Table 6.2.3.2.3.3-4:SIB1 for NR Cell 1 (preamble and all steps, Table 6.2.3.2.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28

SIB1 ::= SEQUENCE {
q-QualMin -25 -25dB
}
}
ETSI

SIB2 ::= SEQUENCE {
threshServingLowQ 26
}
}

SIB5 ::= SEQUENCE {
carrierFreq Downlink
EUTRA ARFCN
as E-UTRA Cell
1 used
threshX-HighQ 12
threshX-LowQ 5
}
}
}
}
Table 6.2.3.2.3.3-7:SystemInformationBlockType24 for E-UTRA Cell 1 (step 7, Table 6.2.3.2.3.2-3)

{
ARFCN of SSB
for NR Cell 1
threshX-HighQ-r15 5
threshX-LowQ-r15 20
}
q-QualMin-r15 -25
}
}
}
ETSI
Table 6.2.3.2.3.3-8: Paging for E-UTRA Cell 1 (step 8, Table 6.2.3.2.3.2-3)

pagingRecordList Not present
systemInfoModification True
etws-PrimaryNotificationIndication Not present
nonCriticalExtension Not present
}
Table 6.2.3.2.3.3-9: SystemInformationBlockType1 for E-UTRA Cell 1 (step 9, Table 6.2.3.2.3.2-3)

systemInfoValueTag 1
}

message
6.2.3.3 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE (lower

priority & higher priority, Srxlev based)
(1)
with { UE in NR RRC_Idle state }
ensure that {
priority E-UTRA frequency }
then { UE reselects to the E-UTRA cell }
}
(2)
ensure that {
when { UE detects the cell re-selection criteria are met for the neighour cell which belongs to
the lower priority E-UTRA frequency }
then { UE reselects to the E-UTRA cell }
}
[TS 38.304, clause 5.2.4.1]
ETSI
NAS (TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.1]

ETSI
[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
as defined in sub-clause 5.2.4.6.
System Simulator:
- NR Cell 1, E-UTRA Cell 1is different priority inter-RAT Cell.
UE:
None.
ETSI
Preamble:
established.
NR Cell 1 in FR1
Parameter Unit NR E-UTRA Remark
Cell 1 Cell 1
T0 Cell-specific The power level values are assigned
dBm/15kHz - -Off
RS EPRE to ensure UE registered on NR Cell 1
SS/PBCH
dBm/SCS -88 -
SSS EPRE
dBm/15kHz - -75
RS EPRE to satisfy SrxlevE-UTRA Cell 1> Threshx,
SS/PBCH high
dBm/SCS -95 -
SSS EPRE
dBm/15kHz - -95
RS EPRE to ensure UE reselected back to NR
Cell 1: both SrxlevE-UTRA Cell 1 <
SS/PBCH
dBm/SCS -78 - Threshserving, low and SrxlevNR Cell 1 >
SSS EPRE
Threshx, low.
dBm/15kHz - -75
RS EPRE to satisfy both SrxlevNR Cell 1 <
SS/PBCH Threshserving, low and SrxlevE-UTRA Cell 1 >
dBm/SCS -95 -
SSS EPRE Threshx, low.
NR Cell 1 in FR2

Cell 1 Cell 1
dBm/15kHz - -Off
SS/PBCH
dBm/SCS FFS -
SSS EPRE
dBm/15kHz - -75
RS EPRE to satisfy SrxlevE-UTRA Cell 1> Threshx,
SS/PBCH high
dBm/SCS FFS -
SSS EPRE
dBm/15kHz - -95
RS EPRE to ensure UE reselected back to NR
Cell 1: both SrxlevE-UTRA Cell 1 <
SS/PBCH
dBm/SCS FFS - Threshserving, low and SrxlevNR Cell 1 >
SSS EPRE
Threshx, low.
ETSI

dBm/15kHz - -75
RS EPRE to satisfy both SrxlevNR Cell 1 <
SS/PBCH Threshserving, low and SrxlevE-UTRA Cell 1 >
dBm/SCS FFS -

U-S Message
6.2.3.3.3.2-1/2.
2 Void - - - -
UTRAN Cell 1?
6.2.3.3.3.2-1/2.
5 Void - - - -
6 Generic test procedure in TS 38.508-1 [4] - - - -
Table 4.9.9.2.2-1 take place and UE is
camped on NR Cell 1
7 The SS transmits RRCRelease message on <-- NR:RRCRelease
NR Cell 1.
8 The SS notifies the UE of change of System <-- NR: ShortMessage - -
Information on NR Cell 1 by send Short
9 The SS changes Priority of E-UTRA cell 1 in - - - -
the SIB5 of NR Cell 1, The ValueTag of SIB5
in the SIB1 is increased on NR Cell 1.
6.2.3.3.3.2-1/2.
12 Void - - - -
UTRAN Cell 1?

SIB2 ::= SEQUENCE {
}
}
ETSI

SIB5 ::= SEQUENCE {
1 used
}
}
t-ReselectionEUTRA 7 7 Seconds
}
6.2.3.3.3.2-3)

6.2.3.3.3.2-3)

}
}
}
ETSI
Table 6.2.3.3.3.3-5: SIB5 of NR Cell 1(Step 9, Table 6.2.3.3.3.2-3)

SIB5 ::= SEQUENCE {
1 used
}
}
}

SIB1 ::= SEQUENCE {
}
Derivation Path: TS 38.508-1 [4], Table 4.6.3-130A

SchedulingInfo {
type sibType5
valueTag 1
}
}
}
}
}
Derivation Path: TS 38.508-1 [4], Table 4.9.7.2.3-1 with condition First-N1-to-S1 = TRUE
Derivation Path: TS 38.508-1 [4], Table 4.9.7.2.3-1 with condition First-N1-to-S1 = FALSE
ETSI

message
Derivation Path: TS 36.508 [2], Table 4.7.2-27.

EPS update type
EPS update type Value '000'B TA updating
"Active" flag '0'B No bearer
establishment
requested
NAS key set identifier
NAS key set identifier the eKSI value for the
current mapped EPS
security context
TSC '1'B mapped security
context
6.2.3.4 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE (lower

priority & higher priority, Squal based)
(1)
ensure that {
priority inter-RAT E-UTRA cell }
then { UE reselects the cell which belongs to the lower priority inter-RAT E-UTRA cell }
}
(2)
ensure that {
priority inter-RAT E-UTRA cell }
then { UE reselects the cell which belongs to the higher priority inter-RAT E-UTRA cell }
}
[TS 38.304, clause 5.2.4.1]
ETSI
NAS (TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.1]

[TS 38.304, clause 5.2.4.5]
TreselectionRAT
ETSI
and
System Simulator:
- NR Cell 1 and E-UTRA Cell 1
- System information combination NR-6 as defined in TS 38.508-1 [7] clause 4.4.3.1, and message contents
defined in clause 4.6.1 and clause 4.6.2 with QBASED condition is used in NR cell.
- System information combination 31 as defined in TS 36.508 [7] clause 4.4.3.1, and message contents defined
in clause 4.4.3.3 with QBASED condition is used in E-UTRA cell.
UE:
None.
Preamble:
With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1
UTRA/EPC) and Unrestricted nr PDN (On) in accordance with the procedure described in TS 38.508-1 [4], clause
4.5.2. 4G-GUTI and eKSI are assigned and security context established
The UE is switched-off.
With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1
ETSI
established..
texts in this clause. Configurations marked "T1","T2" and "T3" are applied at the points indicated in the Main behaviour
description in Table 6.2.3.4.3.2-3.
Table 6.2.3.4.3.2-1: Time instances of cell power level and parameter changes for NR Cell (FR1)
Parameter Unit NR Cell E-UTRA Remark
1 Cell 1
Cell-specific The power level values are assigned to
dBm/15kHz - -80
RS EPRE ensure UE reselected to E-UTRA Cell 1:
SS/PBCH both Squal ServingCell, NR Cell1 < ThreshServing,
dBm/SCS -95 -
SSS EPRE LowQ and SqualnonServingCell, E-UTRA Cell1 >
T1 ThreshX, LowQ
RSRQ dB -21.20 -3.76
Qqualmin dB -25 -20
NocE-UTRA dBm/15kHz - -95
NocNR dBm/SCS -85 -
dBm/15kHz - -95
RS EPRE ensure UE reselected back to NR Cell 1:
SS/PBCH Squal nonServingCell, NR Cell1 > ThreshX, HighQ
dBm/SCS -80 -
SSS EPRE
T2
RSRQ dB -11.96 -11.46
Qqualmin dB -25 -20
NocNR dBm/SCS -85 -
dBm/15kHz - -80
SS/PBCH Squal nonServingCell, E-UTRA Cell1 > ThreshX, HighQ
dBm/SCS -95 -
SSS EPRE
T3
RSRQ dB -21.20 -3.76
Qqualmin dB -25 -20
NocNR dBm/SCS -85 -
ETSI
Table 6.2.3.4.3.2-2: Time instances of cell power level and parameter changes for NR Cell (FR2)
Parameter Unit NR Cell E-UTRA Remark
1 Cell 1
dBm/15kHz - FFS
SS/PBCH both Squal ServingCell, NR Cell1 < ThreshServing,
dBm/SCS FFS -
SSS EPRE LowQ and SqualnonServingCell, E-UTRA Cell1 >
T1 ThreshX, LowQ
RSRQ dB FFS FFS
Qqualmin dB -25 -20
NocE-UTRA dBm/15kHz - FFS
NocNR dBm/SCS FFS -
dBm/15kHz - FFS
RS EPRE ensure UE reselected back to NR Cell 1:
SS/PBCH Squal nonServingCell, NR Cell1 > ThreshX, HighQ
dBm/SCS FFS -
SSS EPRE
T2
RSRQ dB FFS FFS
Qqualmin dB -25 -20
NocNR dBm/SCS FFS -
Cell-specific The power level values are assignee to
dBm/15kHz - FFS
SS/PBCH Squal nonServingCell, E-UTRA Cell1 > ThreshX, HighQ
dBm/SCS FFS -
SSS EPRE
T3
RSRQ dB FFS FFS
Qqualmin dB -25 -20
NocNR dBm/SCS FFS -
ETSI

U-S Message
1 The SS changes SS/PBCH SSS EPRE level - - - -
for NR Cell 1 and Cell-specific RS EPRE level
for E-UTRA Cell 1 according to row "T1" in
table 6.2.3.4.3.2-1/2/3.
2 Check: Does the test result of test steps 1 to 6 - - 1 -
Table 4.9.7.2.2 indicate that the UE is camped
on E-UTRA Cell 1?
table 6.2.3.4.3.2-1/2/3.
5 The UE selects NR Cell 1 and performs the - - - -
generic test procedure in TS 38.508-1 Table
4.9.9.2.2-1 with condition 'connected without
release'.
6 The SS transmits an RRCRelease message <-- NR RRC: RRCRelease - -
on NR Cell 1.
7 The SS changes the E-UTRA cell priority - - - -
broadcast in system information on NR Cell 1.
8 Notify UE change of System Information on <-- NR RRC: ShortMessage
NR Cell 1.
information.
table 6.2.3.4.3.2-1/2/3.
11 Check: Does the test result of test steps 1 to 6 - - 2 -
Table 4.9.7.2.2 indicate that the UE is camped
on E-UTRA Cell 1?

SIB1 ::= SEQUENCE {
q-QualMin -25
}
}

SIB2 ::= SEQUENCE {
threshServingLowQ 9
}
ETSI
Table 6.2.3.4.3.3-3:SIB5 NR Cell 1 (preamble, Table 6.2.3.4.3.2-3)

SIB5 ::= SEQUENCE {
carrierFreq Downlink E-UTRA
ARFCN for E-
UTRA Cell 1
threshX-HighQ 20
threshX-LowQ 10
}
}
}
}
6.2.3.4.3.2-3)

cellSelectionInfo-v920 SEQUENCE {
q-QualMin-r9 -20
}
}
}
}
Table 6.2.3.4.3.3-5:SystemInformationBlockType3 for E-UTRA Cell 1 preamble and all steps, Table
6.2.3.4.3.2-3)

lateNonCriticalExtension {
q-QualMin-r9 -20
threshServingLowQ-r9 26
}
}
ETSI
Table 6.2.3.4.3.3-6:SystemInformationBlockType24 for E-UTRA Cell 1 (preamble and all steps, Table
6.2.3.4.3.2-3)

{
ARFCN of SSB
for NR Cell 1
threshX-HighQ-r15 10
threshX-LowQ-r15 20
}
q-QualMin-r15 -25
}
}
}
Table 6.2.3.4.3.3-7: SIB5 NR Cell 1 (step 7, Table 6.2.3.4.3.2-3)

SIB5 ::= SEQUENCE {
carrierFreq Downlink E-UTRA
ARFCN for E-
UTRA Cell 1
q-QualMin -20
threshX-HighQ 12
threshX-LowQ 20
}
}
}
}

SIB1 ::= SEQUENCE {
q-QualMin -25
}
}
ETSI

schedulingInfoList SEQUENCE (SIZE(1..maxSI- 1 entry
Message)) OF SchedulingInfo {
type sibType5
valueTag 1
}
}
}
}
}

message
6.2.3.5 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA_IDLE according

to RAT priority provided by dedicated signalling (RRCRelease)
(1)
with { UE in NR RRC_IDLE state having received an RRCRelease message including
cellReselectionPriorities }
ensure that {
priority RAT }
then { UE reselects the cell which belongs to the higher priority RAT }
}
}
(2)
with { UE in NR RRC_IDLE state having received an RRCRelease message including a
ensure that {
priority RAT }
then { UE reselects the cell which belongs to the lower priority RAT }
}
}
(3)
with { UE in NR RRC_IDLE state having received an RRCRelease message including a
ensure that {
ETSI
when { T320 expires }

then { UE reselects a cell by applying the cellReselectionPriority broadcast in the system
information }
}
}
(4)
with { UE in NR RRC_IDLE state and reselection priorities have been provided in dedicated
signalling }
ensure that {
when { T320 has not expired }
then { The UE shall ignore all the priorities provided in system information, and not perform
cell reselection evaluation for NR frequencies and E-UTRA frequencies for which the UE doesn’t have
a priority provided }
}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.304: clause 5.2.4.1
and 5.2.4.5, 3GPP TS 38.331:clause 5.3.8.3 and 5.3.8.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 5.2.4.1]
NAS (TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.2]
ETSI

[TS 38.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 RRCRelease message was
received or optionally when lower layers indicate that the receipt of the RRCRelease message has been
successfully acknowledged, whichever is earlier;
1> stop timer T380, if running;
1> if T390 is running:
2> stop timer T390 for all access categories;
2> perform the actions as specified in 5.3.14.4;
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the
release cause 'other' upon which the procedure ends;
1> if the RRCRelease message includes redirectedCarrierInfo indicating redirection to eutra:
2> if cnType is included:
3> after the cell selection, indicate the available CN Type(s) and the received cnType to upper layers;
NOTE: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type
specified by the cnType, is up to UE implementation.
1> if the RRCRelease message includes the cellReselectionPriorities:
2> store the cell reselection priority information provided by the cellReselectionPriorities;
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 deprioritisationReq is included:
2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;
ETSI
2> store the deprioritisationReq until T325 expiry;
1> if the RRCRelease includes suspendConfig:
2> apply the received suspendConfig;
2> reset MAC and release the default MAC Cell Group configuration, if any;
2> re-establish RLC entities for SRB1;
2> if the RRCRelease message with suspendConfig was received in response to an RRCResumeRequest or an
RRCResumeRequest1:
3> stop the timer T319 if running;
3> in the stored UE Inactive AS context:
4> replace the KgNB and KRRCint keys with the current KgNB and KRRCint keys;
4> replace the C-RNTI with the temporary C-RNTI in the cell the UE has received the RRCRelease
message;
4> replace the cellIdentity with the cellIdentity of the cell the UE has received the RRCRelease message;
4> replace the physical cell identity with the physical cell identity of the cell the UE has received the
RRCRelease message;
4> replace the suspendConfig with the current suspendConfig;
2> else:
3> store in the UE Inactive AS Context the configured suspendConfig, the current KgNB and KRRCint keys, the
ROHC state, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the
source PCell, and all other parameters configured except with ReconfigurationWithSync;
2> suspend all SRB(s) and DRB(s), except SRB0;
2> indicate PDCP suspend to lower layers of all DRBs;
3> start timer T380, with the timer value set to t380;
2> if the RRCRelease message is including the waitTime:
3> start timer T302 with the value set to the waitTime;
3> inform the upper layer that access barring is applicable for all access categories except categories '0' and
'2';
2> indicate the suspension of the RRC connection to upper layers;
2> enter RRC_INACTIVE and perform cell selection as specified in TS 38.304 [20];
1> else
2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with the release cause 'other'.
[TS 38.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 cellReselectionPriorities or
inherited from another RAT;
2> apply the cell reselection priority information broadcast in the system information.
ETSI
System Simulator:
- NR Cell 1, E-UTRA Cell 1 is inter-RAT cell.
UE:
None.
Preamble:
[4], Table 6.2.2.1-3, the UE is brought to state 3N-A, RRC_CONNECTED Connectivity (NR), in accordance
with the procedure described in TS 38.508-1 [4], Table 4.5.4.2-3. 5G-GUTI and ngKSI are assigned and security
context established.
texts in this clause. Row marked "T0" denotes the conditions in the preamble. Configurations marked "T1", "T2" and so
on are applied at the points indicated in the Main behaviour description in Table 6.1.3.5.3.2-3.
Table 6.2.3.5.3.2-1: Time instances of cell power level and parameter changes for E-UTRA cell 1 and
NR cell 1 in FR1
Cell 1 Cell 1
dBm/15kHz - OFF
RS EPRE satisfy Srxlev NR Cell 1 > 0 and SrxlevE-
SS/PBCH UTRA Cell 1 < 0. And UE camping on NR
dBm/SCS -88 -
SSS EPRE Cell 1 is guaranteed.
dBm/15kHz - -70
RS EPRE satisfy SrxlevE-UTRA cell 1 > Threshx,high.
SS/PBCH
dBm/SCS -90 -
SSS EPRE
T2 Cell-specific The power level values are such that
dBm/15kHz - -104
RS EPRE camping on NR Cell 1 is guaranteed.
SS/PBCH
dBm/SCS -78 -
SSS EPRE
dBm/15kHz - -88
RS EPRE satisfy both SrxlevNR Cell 1 <
Threshserving, low and SrxlevE-UTRA Cell 1
SS/PBCH
dBm/SCS -104 - > Threshx, low.
SSS EPRE
dBm/15kHz - -104
SS/PBCH
dBm/SCS -78 -
SSS EPRE
ETSI

dBm/15kHz - -70
RS EPRE satisfy SrxlevNR cell 1 > Threshserving, low
SS/PBCH and SrxlevE-UTRA cell 1 > Threshx,high.
dBm/SCS -90 -
SSS EPRE
NR Cell 1 in FR2
Cell 1 Cell 1
dBm/15kHz - OFF
RS EPRE satisfy Srxlev NR Cell 1 > 0 and SrxlevE-
SS/PBCH UTRA Cell 1 < 0. And UE camping on NR
dBm/SCS FFS -
SSS EPRE Cell 1 is guaranteed.
dBm/15kHz - -70
RS EPRE satisfy SrxlevE-UTRA cell 1 > Threshx,high.
SS/PBCH
dBm/SCS FFS -
SSS EPRE
dBm/15kHz - -104
SS/PBCH
dBm/SCS FFS -
SSS EPRE
dBm/15kHz - -88
RS EPRE satisfy both SrxlevNR Cell 1 < Threshserving,
SS/PBCH low and SrxlevE-UTRA Cell 1 > Threshx, low.
dBm/SCS FFS -
SSS EPRE
dBm/15kHz - -104
SS/PBCH
dBm/SCS FFS -
SSS EPRE
dBm/15kHz - -70
RS EPRE satisfy SrxlevNR cell 1 > Threshserving, low
SS/PBCH and SrxlevE-UTRA cell 1 > Threshx,high.
dBm/SCS FFS -
SSS EPRE
ETSI

U-S Message
1 The SS transmits RRCRelease message - NR:RRCRelease - -
including cellReselectionPriorities on NR Cell
1.
6.2.3.5.3.2-1/2.
3 Check: Does the UE transmit an RRC - - 4 F
CONNECTION REQUEST on E-UTRA Cell 1
within the next 30 Seconds?
4 The test steps 1 to 8 of generic test procedure - - - -
in TS 38.508-1 [4] Table 4.5.4.2-3 are
performed on NR Cell 1.
5 The SS transmits RRCRelease message <-- NR:RRCRelease - -
1.
UTRAN Cell 1?
6.2.3.5.3.2-1/2.
Table 4.9.9.2.2-1 take place and the UE is
camped on NR Cell 1.
6.2.3.5.3.2-1/2.
1.
UTRAN Cell 1?
6.2.3.5.3.2-1/2.
Table 4.9.9.2.2-1 take place and the UE is
camped on NR Cell 1.
1.
6.2.3.5.3.2-1/2.
16 Wait for 5 minutes from step 17 to ensure that - - - -
T320 expires.
UTRAN Cell 1?
ETSI

SIB2 ::= SEQUENCE {
threshServingLowP 5 10dB
}
}

SIB5 ::= SEQUENCE {
carrierFreq Downlink EARFCN as E-
UTRA Cell 1 used
threshX-Low 5 10 dB
}
}
}
Table 6.2.3.5.3.3-3: SystemInformationBlockType3 for EUTRA Cell 1 (preamble and all steps, Table
6.2.3.5.3.2-3)
Derivation Path: TS 36.508 [7], Table 4.4.3.2

threshServingLow 5 10dB
}
}
6.2.3.5.3.2-3)

threshX-High-r15 20 40dB
threshX-Low-r15 10 20dB
}
}
}
ETSI
Table 6.2.3.5.3.3-5 RRCRelease (step1, Table 6.2.3.5.3.2-3)

RRCRelease ::= SEQUENCE {
rrcRelease SEQUENCE {
cellReselection Priorities SEQUENCE {
freqPriorityListEUTRA Not present Step1
freqPriorityListEUTRA SEQUENCE (SIZE 1 entry
(1..maxFreq)) OF FreqPriorityEUTRA {
FreqPriorityListEUTRA[1] SEQUENCE { entry 1
carrierFreq Downlink ARFCN of E-
UTRA Cell 1
cellReselectionPriority 5 Step5
3 Step10
3 Step14
}
}
freqPriorityListNR SEQUENCE (SIZE 1 entry
(1..maxFreq)) OF FreqPriorityNR {
FreqPriorityNR[1] SEQUENCE { entry 1
carrierFreq Downlink SSB ARFCN of
NR Cell 1
cellReselectionPriority 4 Step1
4 Step5
4 Step10
4 Step14
}
}
t320 Not present Step1
Not present Step5
Not present Step10
min5 5 minutes Step14
}
}
}
}
Table 6.2.3.5.3.3-6: REGISTRATION REQUEST (Step 8 and Step13, Table 6.2.3.5.3.2-3)

message
6.2.3.6 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE according

to RAT priority provided by dedicated signalling (RRConnRelease)
(1)
with { UE in E-UTRA RRC_Idle state having received RRCConnectionRelease including
IdleModeMobilityControlInfo containing cellReselectionPriority for NR cell}
ensure that {
ETSI
priority inter-RAT NR cell based on the configured RAT priority provided by dedicated signaling}
then { UE reselects the cell which belongs to the lower priority inter-RAT NR cell}
}
(2)
with { UE in NR RRC_IDLE state having inherit RAT priority provided by dedicated signaling with the
remaining validity time}
ensure that {
when { UE discard the inherit RAT priority upon connection establishment}
then { UE reselects a cell by applying the cellReselectionPriority broadcast in the system
information}
and 3GPP TS 38.304, clause 5.2.4.1. Unless otherwise stated these are Rel-15 requirements.
[TS 36.304, clause 5.2.4.1]
UE implementation.
1) Either:
2) Either:
ETSI
information.
[TS 38.304, clause 5.2.4.1]
ETSI
NAS (TS 23.122 [9]).
information.
System Simulator:
- E-UTRA Cell 1, NR Cell 1 is different priority inter-RAT NR cell.
UE:
- None.
Preamble:
established.
ETSI
[4], Table 6.2.2.1-3, the UE is brought to state RRC_CONNECTED using generic procedure parameters
Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On) in accordance with the procedure described in TS
38.508-1 [4], clause 4.5.4. 4G GUTI and eKSI are assigned and security context established.
NR Cell 1 in FR1
Cell 1 Cell 1
dBm/15kHz -85 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -95 -
RS EPRE satisfy both SrxlevE-UTRA Cell 1 <
SS/PBCH Threshserving, low and SrxlevNR Cell 1 >
dBm/SCS - -80
dBm/15kHz -80 -
SS/PBCH low and SrxlevE-UTRA Cell 1 > Threshx, low
dBm/SCS - -95
SSS EPRE
NR Cell 1 in FR2
Cell 1 Cell 1
dBm/15kHz FFS -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz FFS -
RS EPRE satisfy both SrxlevE-UTRA Cell 1 <
SS/PBCH Threshserving, low and SrxlevNR Cell 1 >
dBm/SCS - FFS
dBm/15kHz FFS -
SS/PBCH low and SrxlevE-UTRA Cell 1 > Threshx, low
dBm/SCS - FFS
SSS EPRE
ETSI

U-S Message
1 The SS transmmits RRCConnectionRelease <-- E-UTRA: RRCConnectionRelease - -
message with dedicated priority information
and validtity timer to the UE on E-UTRA cell 1.
6.2.3.6.3.2-1/2.
4 Void. - - - -
6.2.3.6.3.2-1/2.
UTRAN Cell 1?
6.2.3.6.3.2-3)

}
}
6.2.3.6.3.2-3)

}
}
}
ETSI

SIB2 ::= SEQUENCE {
}
}

SIB5 ::= SEQUENCE {
1 used
}
}
}
Table 6.2.3.6.3.3-5: RRCConnectionRelease message for EUTRA Cell 1 (step 1 of Table 6.2.3.6.3.2-3)

RRCConnectionRelease ::= SEQUENCE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
IdleModeMobilityControlInfo SEQUENCE {
freqPriorityListEUTRA SEQUENCE (SIZE (1.. 1 entry
maxFreq)) OF FreqPriorityEUTRA {
freqPriorityListEUTRA[1] SEQUENCE { entry 1
carrierFreq DownLink ARFCN-Value
of E-UTRA cell 1
}
}
t320 Not present
freqPriorityListNR-r15 SEQUENCE (SIZE 1 entry
(1..maxFreq)) OF FreqPriorityNR-r15 {
FreqPriorityNR-r15[1] SEQUENCE { entry 1
carrierFreq-r15 Same Downlink SSB
Cell 1
}
}
}
}
}
}
}
ETSI
6.2.3.7 Inter-RAT cell reselection / From NR RRC_IDLE to E-UTRA RRC_IDLE,

Snonintrasearch
(1)
ensure that {
then { UE perform measurement and reselects to cell which belongs to the high priority E-UTRA
cell even if Srxlev>Snonintrasearch }
}
[TS 38.304, clause 5.2.4.1]
NAS (TS 23.122 [9]).
NOTE 3: The network may assign dedicated cell
[TS 38.304, clause 5.2.4.2]
ETSI
[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
ETSI
System Simulator:
- NR Cell 1, E-UTRA Cell 1 is higher priority inter-RAT cell.
UE:
None.
Preamble:
established.
texts in this clause. Row marked "T0" denotes the conditions in the preamble. Configurations marked "T1"is applied at
the points indicated in the Main behaviour description in Table 6.2.3.7.3.2-3.
NR Cell 1 in FR1
Cell 1 Cell 1
dBm/15kHz - Off
SS/PBCH
dBm/SCS -88 -
SSS EPRE
dBm/15kHz - -75
RS EPRE to satisfy Srxlev NR Cell 1 >Snonintrasearch
SS/PBCH and SrxlevE-UTRA Cell 1> Threshx, high.
dBm/SCS -90 -
SSS EPRE
NR Cell 1 in FR2
Cell 1 Cell 1
dBm/15kHz - Off
SS/PBCH
dBm/SCS FFS -
SSS EPRE
ETSI

dBm/15kHz - -75
RS EPRE to satisfy Srxlev NR Cell 1 >Snonintrasearch
SS/PBCH and SrxlevE-UTRA Cell 1> Threshx, high.
dBm/SCS FFS -
SSS EPRE

U-S Message
6.2.3.7.3.2-1/2.
UTRAN Cell 1?
Table 6.2.3.7.3.3-1: SIB2 of NR Cell 1 (preabmle and all steps, Table 6.2.3.7.3.2-3)

SIB2 ::= SEQUENCE {
SEQUENCE {
}
}

SIB5 ::= SEQUENCE {
1 used
}
}
}
6.2.3.7.3.2-3)

}
}
ETSI
6.2.3.7.3.2-3)

}
}
6.2.3.8 Inter-RAT cell reselection / From E-UTRA RRC_IDLE to NR RRC_IDLE,

Snonintrasearch
(1)
with { UE in E-UTRA RRC_Idle state, and the UE is not in high mobility state }
ensure that {
then { UE perform measurement and reselects to cell which belongs to the high priority NR cell
even if Srxlev>Snonintrasearch }
}
[TS 36.304, clause 5.2.4.1]
ETSI
UE implementation.
1) Either:
2) Either:
ETSI
information.
[TS 36.304, clause 5.2.4.2]

[TS 36.304, clause 5.2.4.5]
ETSI
and
fulfilled.
ETSI
System Simulator:
- E-UTRA Cell 1, NR Cell 1 is higher priority inter-RAT NR cell.
UE:
- None.
Preamble:
established.
texts in this clause. Row marked "T0" denotes the conditions in the preamble. Configurations marked "T1"is applied at
the points indicated in the Main behaviour description in Table 6.2.3.8.3.2-3.
NR Cell in FR1
Cell 1 Cell 1
dBm/15kHz -85 -
RS EPRE to ensure UE registered on E-UTRA
SS/PBCH Cell 1
dBm/SCS - Off
SSS EPRE
dBm/15kHz -90 -
RS EPRE to satisfy Srxlev E-UTRA Cell 1 >Snonintrasearch
SS/PBCH and and SrxlevNR Cell 1> Threshx, high.
dBm/SCS - -80
SSS EPRE
NR Cell in FR2
Cell 1 Cell 1
dBm/15kHz FFS -
RS EPRE to ensure UE registered on E-UTRA
SS/PBCH Cell 1
dBm/SCS - Off
SSS EPRE
ETSI

dBm/15kHz FFS -
RS EPRE to satisfy Srxlev E-UTRA Cell 1 >Snonintrasearch
SS/PBCH and and SrxlevNR Cell 1> Threshx, high.
dBm/SCS - FFS
SSS EPRE

U-S Message
6.2.3.8.3.2-1/2.
3 Void. - - - -
6.2.3.8.3.2-3)

s-NonIntraSearch 3 6 dB
}
6.2.3.8.3.2-3)

}
}
}
ETSI
Table 6.2.3.8.3.3-3: SIB2 of NR Cell 1 (preabmle and all steps, Table 6.2.3.8.3.2-3)

SIB2 ::= SEQUENCE {
SEQUENCE {
}
}
Derivation Path: TS 38.508 [6], Table 4.6.2-4

SIB5 ::= SEQUENCE {
1 used
}
}
}
6.2.3.9 Void
6.2.3.10 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE /

schedulingInfoList-v12j0
(1)
with { the UE is in E-UTRA IDLE state and SystemInformationBlockType24 scheduled by optional
extended field schedulingInfoList-v12j0 in SystemInformationBlockType1 is broadcasted }
ensure that {
when { UE detects the cell re-selection criteria is met for a lower priority NR cell }
then { UE reselects to the NR cell }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.2.3 and
5.2.3a and TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5. Unless otherwise stated these are Rel-15 requirements.
[TS 36.331, clause 5.2.3]
When acquiring an SI message, the UE shall:
1> determine the start of the SI-window for the concerned SI message as follows:
2> if the concerned SI message is configured in the schedulingInfoList, schedulingInfoListExt (if present) or if
the concerned SI message is configured in the pos-schedulingInfoList and si-posOffset is not configured;
ETSI
3> for the concerned SI message, determine the number n which corresponds to the order of entry in the
concatenated list of SI messages configured by schedulingInfoList, schedulingInfoListExt (if present) and
posSchedulingInfoList in SystemInformationBlockType1;
3> determine the integer value x = (n – 1)*w, where w is the si-WindowLength;
3> the SI-window starts at the subframe #a, where a = x mod 10, in the radio frame for which SFN mod T =
FLOOR(x/10), where T is the si-Periodicity of the concerned SI message;
2> else if the concerned SI message is configured by the posSchedulingInfoList and si-posOffset is configured
determine the start of the SI-window for the concerned SI message as follows:
3> determine the number m which corresponds to the number of SI messages with an associated si-
Periodicity of 8 radio frames (80 ms), configured by schedulingInfoList and schedulingInfoListExt (if
present) in SystemInformationBlockType1;
3> for the concerned SI message, determine the number n which corresponds to the order of entry in the list
of SI messages configured by posSchedulingInfoList in SystemInformationBlockType1;
3> determine the integer value x = m*w + (n – 1)*w, where w is the si-WindowLength
FLOOR(x/10) + 8, where T is the si-posPeriodicity of the concerned SI message;
NOTE: E-UTRAN should configure an SI-window of 1 ms only if all SIs are scheduled before subframe #5 in
radio frames for which SFN mod 2 = 0.
1> receive DL-SCH using the SI-RNTI from the start of the SI-window and continue until the end of the SI-window
whose absolute length in time is given by si-WindowLength, or until the SI message was received, excluding the
following subframes:
2> subframe #5 in radio frames for which SFN mod 2 = 0;
2> any MBSFN subframes;
2> any uplink subframes in TDD;
1> if the SI message was not received by the end of the SI-window, repeat reception at the next SI-window occasion
for the concerned SI message;
[TS 36.331, clause 5.2.3a]
When acquiring an SI message, the BL UE or UE in CE or NB-IoT UE shall:
concatenated list of SI messages configured by schedulingInfoList, schedulingInfoListExt (if present) in
SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) and
posSchedulingInfoList in SystemInformationBlockType1-BR;
3> determine the integer value x = (n – 1)*w, where w is the si-WindowLength-BR (or si-WindowLength in
NB-IoT);
present) in SystemInformationBlockType1-BR;
of SI messages configured by posSchedulingInfoList in SystemInformationBlockType1-BR;
ETSI
3> determine the integer value x = m*w + (n – 1)*w, where w is the si-WindowLength-BR;
2> if the UE is a NB-IoT UE:
3> the SI-window starts at the subframe #0 in the radio frame for which (H-SFN * 1024 + SFN) mod T =
FLOOR(x/10) + Offset, where T is the si-Periodicity of the concerned SI message and, Offset is the offset
of the start of the SI-Window (si-RadioFrameOffset);
2> else:
3> the SI-window starts at the subframe #0 in the radio frame for which SFN mod T = FLOOR(x/10), where
T is the si-Periodicity of the concerned SI message;
2> receive and accumulate SI message transmissions on DL-SCH from the start of the SI-window and continue
until the end of the SI-window whose absolute length in time is given by si-WindowLength, starting from the
radio frames as provided in si-RepetitionPattern and in subframes as provided in downlinkBitmap, or until
successful decoding of the accumulated SI message transmissions excluding the subframes used for
transmission of NPSS, NSSS, MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB and
SystemInformationBlockType1-NB. If there are not enough subframes for one SI message transmission in the
radio frames as provided in si-RepetitionPattern, the UE shall continue to receive the SI message
transmission in the radio frames following the radio frame indicated in si-RepetitionPattern;
1> else:
2> receive and accumulate SI message transmissions on DL-SCH on narrowband provided by si-Narrowband,
from the start of the SI-window and continue until the end of the SI-window whose absolute length in time is
given by si-WindowLength-BR, only in radio frames as provided in si-RepetitionPattern and subframes as
provided in fdd-DownlinkOrTddSubframeBitmapBR in bandwidthReducedAccessRelatedInfo, or until
successful decoding of the accumulated SI message transmissions;
1> if the SI message was not possible to decode from the accumulated SI message transmissions by the end of the
SI-window, continue reception and accumulation of SI message transmissions on DL-SCH in the next SI-
window occasion for the concerned SI message;
[TS 36.304, clause 5.2.4.1]
ETSI
UE implementation.
1) Either:
2) Either:
PLMN different from its registered PLMN, the UE may consider cell reselection candidate frequencies at which it
cannot receive the MBMS service to be of the lowest priority during the MBMS session TS 36.300 [2], as long as the
is provided, it may consider cell reselection candidate frequencies at which it cannot receive the MBMS service to be of
the lowest priority during the MBMS session TS 36.300 [2] as long as the cell on the MBMS frequency which the UE
monitors is broadcasting SIB13 or SIB1-MBMS.
ETSI
information.
[TS 36.304, clause 5.2.4.2]

[TS 36.304, clause 5.2.4.5]
ETSI
and
fulfilled.
ETSI
System Simulator:
- System information combination 1 as defined in TS 36.508 [7] clause 4.4.3.1 is used in E-UTRA Cell 1.
SystemInformationBlockType1 is broadcasted with extended fields as specified in Table 6.2.3.10.3.3-1. And
SystemInformationBlockType24 is broadcasted according to scheduling information specified in Table
6.2.3.10.3.3-1.
- System information combination NR-1 defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR Cell 1.
UE:
- None.
Preamble:
[4], Table 6.2.2.1-3, the UE is brought to state RRC_CONNECTED 1N-A, Connectivity (NR), in accordance
- The UE is switched-off
clause 4.5. 4. 4G GUTI and eKSI are assigned and security context established.
NR Cell 1 in FR1
Cell 1 Cell 1
dBm/15kHz -85 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -95 -
dBm/SCS - -80
SSS EPRE
ETSI
NR Cell 1 in FR2
Cell 1 Cell 1
dBm/15kHz -82 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -98 -
dBm/SCS - -78
SSS EPRE

U-S Message
6.2.3.10.3.2-1/2.
1A Wait for 1s (Note 2). - - - -
1B The SS transmits an RRCConnectionRelease <-- RRC: RRCConnectionRelease - -
message to release RRC connection and
move to E-UTRA RRC_IDLE.
within 34s for FR1 or 130s for FR2? (Note 1)
Note 1: The wait time for reselection to an newly detected Inter-RAT NR cell is selected to cover Tdetect,NR (32s for
FR1 and 4*32s=128s for FR2) + TSI-NR (1280 ms system information block type scheduling) = 33.28s
Note 2: The wait time 1 sec is added to allow the NR cell to be setup before RRC is released on E-UTRAN. This
will avoid the UE to miss the Tdetect,NR window if the NR cell is not up.
ETSI
Table 6.2.3.10.3.3-1: SystemInformationBlockType1 for cell 1 (preamble and all steps, Table
6.2.3.11.3.2-3)

lateNonCriticalExtension SEQUENCE {
schedulingInfoList-v12j0 SEQUENCE (SIZE 2 entries It includes the same
(1..maxSI-Message)) OF SEQUENCE { number of entries, and
listed in the same order,
as in schedulingInfoList
(without suffix).
SchedulingInfo-v12j0[1] SEQUENCE { entry 1
SIB-MappingInfo-v12j0 Not present
}
SchedulingInfo-v12j0[2] SEQUENCE { entry 2
SIB-MappingInfo-v12j0 SEQUENCE 1 entry
(SIZE (1..maxSIB-1)) OF SIB-Type-v12j0 {
SIB-Type-v12j0[1] sibType24-v1530 entry 2, SIB24 is
mapped into the SI
message scheduled via
the second entry of
schedulingInfoList
(without suffix)
}
}
}
}
}
}
}
}
}
}
}
6.2.3.10.3.2-3)

}
}
ETSI
6.2.3.10.3.2-3)

SSB for NR Cell 1
}
}
}
6.2.3.11 Inter-RAT cell reselection / From E-UTRA_IDLE to NR RRC_IDLE /

schedulingInfoListExt-r12
(1)
with { the UE is in E-UTRA IDLE state and SystemInformationBlockType24 scheduled by optional
extended field schedulingInfoListExt-r12 in SystemInformationBlockType1 is broadcasted }
ensure that {
when { UE detects the cell re-selection criteria is met for a lower priority NR cell }
then { UE reselects to the NR cell }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.2.3 and
5.2.3a and TS 36.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5. Unless otherwise stated these are Rel-15 requirements.
[TS 36.331, clause 5.2.3]
When acquiring an SI message, the UE shall:
concatenated list of SI messages configured by schedulingInfoList, schedulingInfoListExt (if present) and
posSchedulingInfoList in SystemInformationBlockType1;
3> determine the integer value x = (n – 1)*w, where w is the si-WindowLength;
FLOOR(x/10), where T is the si-Periodicity of the concerned SI message;
present) in SystemInformationBlockType1;
of SI messages configured by posSchedulingInfoList in SystemInformationBlockType1;
ETSI
3> determine the integer value x = m*w + (n – 1)*w, where w is the si-WindowLength
NOTE: E-UTRAN should configure an SI-window of 1 ms only if all SIs are scheduled before subframe #5 in
radio frames for which SFN mod 2 = 0.
1> receive DL-SCH using the SI-RNTI from the start of the SI-window and continue until the end of the SI-window
whose absolute length in time is given by si-WindowLength, or until the SI message was received, excluding the
following subframes:
2> subframe #5 in radio frames for which SFN mod 2 = 0;
2> any MBSFN subframes;
2> any uplink subframes in TDD;
1> if the SI message was not received by the end of the SI-window, repeat reception at the next SI-window occasion
for the concerned SI message;
[TS 36.331, clause 5.2.3a]
When acquiring an SI message, the BL UE or UE in CE or NB-IoT UE shall:
concatenated list of SI messages configured by schedulingInfoList, schedulingInfoListExt (if present) in
SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) and
posSchedulingInfoList in SystemInformationBlockType1-BR;
3> determine the integer value x = (n – 1)*w, where w is the si-WindowLength-BR (or si-WindowLength in
NB-IoT);
present) in SystemInformationBlockType1-BR;
of SI messages configured by posSchedulingInfoList in SystemInformationBlockType1-BR;
3> determine the integer value x = m*w + (n – 1)*w, where w is the si-WindowLength-BR;
3> the SI-window starts at the subframe #0 in the radio frame for which (H-SFN * 1024 + SFN) mod T =
FLOOR(x/10) + Offset, where T is the si-Periodicity of the concerned SI message and, Offset is the offset
of the start of the SI-Window (si-RadioFrameOffset);
2> else:
3> the SI-window starts at the subframe #0 in the radio frame for which SFN mod T = FLOOR(x/10), where
T is the si-Periodicity of the concerned SI message;
ETSI
2> receive and accumulate SI message transmissions on DL-SCH from the start of the SI-window and continue
until the end of the SI-window whose absolute length in time is given by si-WindowLength, starting from the
radio frames as provided in si-RepetitionPattern and in subframes as provided in downlinkBitmap, or until
successful decoding of the accumulated SI message transmissions excluding the subframes used for
transmission of NPSS, NSSS, MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB and
SystemInformationBlockType1-NB. If there are not enough subframes for one SI message transmission in the
radio frames as provided in si-RepetitionPattern, the UE shall continue to receive the SI message
transmission in the radio frames following the radio frame indicated in si-RepetitionPattern;
1> else:
2> receive and accumulate SI message transmissions on DL-SCH on narrowband provided by si-Narrowband,
from the start of the SI-window and continue until the end of the SI-window whose absolute length in time is
given by si-WindowLength-BR, only in radio frames as provided in si-RepetitionPattern and subframes as
provided in fdd-DownlinkOrTddSubframeBitmapBR in bandwidthReducedAccessRelatedInfo, or until
successful decoding of the accumulated SI message transmissions;
1> if the SI message was not possible to decode from the accumulated SI message transmissions by the end of the
SI-window, continue reception and accumulation of SI message transmissions on DL-SCH in the next SI-
window occasion for the concerned SI message;
[TS 36.304, clause 5.2.4.1]
UE implementation.
1) Either:
2) Either:
ETSI
PLMN different from its registered PLMN, the UE may consider cell reselection candidate frequencies at which it
cannot receive the MBMS service to be of the lowest priority during the MBMS session TS 36.300 [2], as long as the
is provided, it may consider cell reselection candidate frequencies at which it cannot receive the MBMS service to be of
the lowest priority during the MBMS session TS 36.300 [2] as long as the cell on the MBMS frequency which the UE
monitors is broadcasting SIB13 or SIB1-MBMS.
information.
ETSI
[TS 36.304, clause 5.2.4.2]

[TS 36.304, clause 5.2.4.5]
and
ETSI
fulfilled.
System Simulator:
- System information combination 1 as defined in TS 36.508 [7] clause 4.4.3.1 is used in E-UTRA Cell 1.
SystemInformationBlockType1 is broadcasted with extended fields as specified in Table 6.2.3.11.3.3-1. And
SystemInformationBlockType24 is broadcasted according to scheduling information specified in Table
6.2.3.11.3.3-1.
- System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR Cell 1.
ETSI
UE:
- None.
Preamble:
[4], Table 6.2.2.1-3, the UE is brought to state RRC_CONNECTED 1N-A, Connectivity (NR), in accordance
NR Cell 1 in FR1
Cell 1 Cell 1
dBm/15kHz -85 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -95 -
dBm/SCS - -80
SSS EPRE
NR Cell 1 in FR2
Parameter Unit E-UTRA NRCell 1 Remark
Cell 1
dBm/15kHz -82 -
SS/PBCH
dBm/SCS - Off
SSS EPRE
dBm/15kHz -98 -
dBm/SCS - -78
SSS EPRE
ETSI

U-S Message
6.2.3.11.3.2-1/2.
1A Wait for 1s (Note 2). - - - -
1B The SS transmits an RRCConnectionRelease <-- RRC: RRCConnectionRelease - -
message to release RRC connection and
move to E-UTRA RRC_IDLE.
within 34s for FR1 or 130s for FR2? (Note 1)
Note 1: The wait time for reselection to an newly detected Inter-RAT NR cell is selected to cover Tdetect,NR (32s for
FR1 and 4*32s=128s for FR2) + TSI-NR (1280 ms system information block type scheduling) = 33.28s
Note 2: The wait time 1 sec is added to allow the NR cell to be setup before RRC is released on E-UTRAN. This
will avoid the UE to miss the Tdetect,NR window if the NR cell is not up.
Table 6.2.3.11.3.3-1: SystemInformationBlockType1 for E-UTRA Cell 1 (Preamble and all steps)

lateNonCriticalExtension SEQUENCE {
schedulingInfoListExt-r12 SEQUENCE 1 entry
(SIZE (1..maxSI-Message)) OF SchedulingInfoExt-r12
{
SchedulingInfoExt-r12[1] SEQUENCE { entry 1
si-Periodicity-r12 rf64
SIB-MappingInfo-v12j0 SEQUENCE 1 entry
(SIZE (1..maxSIB-1)) OF SIB-Type-v12j0 {
SIB-Type-v12j0[1] sibType24-v1530 entry 1
}
}
}
}
}
}
}
}
}
}
}
ETSI
Table 6.2.3.11.3.3-2: SystemInformationBlockType3 of E-UTRA Cell 1 (preamble and all steps , Table
6.2.3.11.3.2-3)

}
}
Table 6.2.3.11.3.3-3: SystemInformationBlockType24 of E-UTRA Cell 1 (preamble and all steps, Table
6.2.3.11.3.2-3)

SSB for NR Cell 1
}
}
}
6.3 5GS Steering of Roaming

6.3.1 Steering of Roaming
6.3.1.1 Steering of UE in roaming during registration/security check successful using

List Type 1
(1)
with {UE being in automatic PLMN selection mode, current VPLMN not part of “PLMNs where registration
was aborted due to SOR” List and not part of "User Controlled PLMN Selector with Access Technology"
list and UE's USIM configured with indication that the UE is to receive Steering of Roaming
information due to initial registration in a VPLMN}
ensure that {
when {SOR Transparent container indicates ACK has been requested & List Type indicates PLMN ID and
Access technology list in REGISTRATION ACCEPT and security check is successful}
then {UE sends ACK in REGISTRATION COMPLETE, waits for network release of the NAS signalling
connection and selects higher priority PLMN}
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause C.2. Unless
[TS 23.122, clause C.2]
6) The VPLMN AMF to the UE: The VPLMN AMF shall transparently send the received steering of roaming
information to the UE in the REGISTRATION ACCEPT message;
ETSI
7) If the steering of roaming information is received and the security check is successful, then:
a) if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]):
- if the UDM has not requested an acknowledgement from the UE the UE shall send the REGISTRATION
COMPLETE message;
- the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41].
NOTE 1: How the ME handles UICC responses and failures in communication between the ME and UICC is
implementation specific and out of scope of this release of the specification.
- if the UDM has not requested an acknowledgement from the UE and the ME receives a USAT REFRESH
command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming" it shall perform items a), b) and
c) of the procedure for steering of roaming in subclause 4.4.6 and if the UE has a list of available and
allowable PLMNs in the area and based on this list the UE determines that there is a higher priority
PLMN than the currently camped chosen VPLMN and the UE is in automatic network selection mode,
then the UE shall either:
i) release the current N1 NAS signalling connection locally and then attempt to obtain service on a
higher priority PLMN as specified in subclause 4.4.3.3 by acting as if timer T that controls periodic
attempts has expired. In this case, steps 8 to 11 are skipped; or
ii) not release the current N1 NAS signalling connection locally and skip steps 8 to 10;
b) if the steering of roaming information contains the list of preferred PLMN/access technology combinations,
the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access
Technology" list stored in the ME with the received list of preferred PLMN/access technology combinations.
Additionally, if the UDM has not requested an acknowledgement from the UE and if the UE has a list of
available and allowable PLMNs in the area and based on this list the UE determines that there is a higher
priority PLMN than the currently camped chosen VPLMN and the UE is in automatic network selection
mode, then the UE shall send the REGISTRATION COMPLETE message to the serving AMF without
including an SOR transparent container and then either:
i) release the current N1 NAS signalling connection locally and then attempt to obtain service on a higher
priority PLMN as specified in subclause 4.4.3.3 by acting as if timer T that controls periodic attempts has
expired. In this case, steps 8 to 11 are skipped; or
ii) not release the current N1 NAS signalling connection locally and skip steps 8 and 10;
8) If:
a) the UE's USIM is configured with indication that the UE is to receive the steering of roaming information
due to initial registration in a VPLMN, but neither the list of preferred PLMN/access technology
combinations nor the secured packet nor the HPLMN indication that 'no change of the "Operator Controlled
PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred
PLMN/access technology combinations is provided' is received in the REGISTRATION ACCEPT message,
when the UE performs initial registration in a VPLMN or if the steering of roaming information is received
but the security check is not successful; and
b) the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to
SOR", not part of "User Controlled PLMN Selector with Access Technology" list, the UE is not in manual
mode of operation and the PDU session for emergency services is not pending to be activated;
then the UE shall send the REGISTRATION COMPLETE message to the serving AMF without including an
SOR transparent container, release the current N1 NAS signalling connection locally, store the PLMN identity in
the list of "PLMNs where registration was aborted due to SOR" and attempt to obtain service on a higher priority
PLMN as specified in subclause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with
an exception that the current PLMN is considered as lowest priority, and skip steps 9 to 12;
NOTE 2: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User
Controlled PLMN Selector with Access Technology" list, the UE stays on the VPLMN.
9) The UE to the VPLMN AMF: If the UDM has requested an acknowledgement from the UE:
ETSI
the UE verified that the steering of roaming information has been provided by the HPLMN in step 7, the UE
sends the REGISTRATION COMPLETE message to the serving AMF with an SOR transparent container
including the UE acknowledgement; and
if the steering of roaming information contained a secured packet and the security check was successful, then
when the UE receives the USAT REFRESH command qualifier of type "Steering of Roaming", it performs
items a), b) and c) of the procedure for steering of roaming in subclause 4.4.6.
10) The AMF to the UDM: If an SOR transparent container is received in the REGISTRATION COMPLETE
message, the AMF uses the Nudm_SDM_Info service operation to provide the received SOR transparent
container to the UDM. If the HPLMN decided that the UE is to acknowledge the successful security check of the
received steering of roaming information in step 4, the UDM verifies that the acknowledgement is provided by
the UE as specified in 3GPP TS 33.501 [66];
11) If the UE has a list of available PLMNs in the area and based on this list the UE determines that there is a higher
priority PLMN than the currently camped chosen VPLMN and the UE is in automatic network selection mode,
then the UE shall attempt to obtain service on a higher priority PLMN as specified in subclause 4.4.3.3 by acting
as if timer T that controls periodic attempts has expired after the release of the N1 NAS signalling connection. If
the N1 NAS signaling connection is not released after implementation dependent time, the UE may locally
release the N1 signaling connection except when the UE is registered for emergency services or the UE has an
established emergency PDU session (see 3GPP TS 24.501 [64]); and
12) The UE deletes the list of "PLMNs where registration was aborted due to SOR".
The list of "PLMNs where registration was aborted due to SOR" is deleted when the UE is switched off or the
USIM is removed.
System Simulator:
Three inter-frequency multi-PLMN NR Cells as specified in TS 38.508-1 [4] Table 4.4.2-1 are configured
The PLMNs are identified in the test by the identifiers in Table 6.3.1.1.3.1-1. The MCC and MNC values
corresponding to the PLMN identifier shall understood as those specified in TS 36.523-1 [42], Table 6.0.1-1.
Table 6.3.1.1.3.1–1: PLMN identifiers

NR Cell PLMN names
NR Cell 11 PLMN2
NR Cell 12 PLMN13
NR Cell 13 PLMN14
NR Cell 11 is set to ''Serving Cell”;
NR Cell 12 is set to ''Serving Cell'';
NR Cell 13 is set to “Serving Cell'';
System Information Combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells.
UE:
- USIM configuration as defined in Table 6.4.1-10 in TS 38.508-1 [4] will be used.
ETSI
Preamble:
- The UE is in Switched OFF (State 0-A) as defined in TS 38.508-1 [4] Table 4.4A.2-0.
ETSI
6.3.1.1.4 Test procedure sequence
Table 6.3.1.1.4-1: Main behaviour
ETSI

U-S Message
1 Power on the UE - - -
4.5.2.2-2 are performed on NR Cell 13
15 The SS transmits an DLInformationTransfer <-- NR RRC: DLInformationTransfer - -
message and an REGISTRATION ACCEPT 5G MM: REGISTRATION
message containing steering of roaming ACCEPT
information indicating list of preferred
PLMN/access technology combination
provided with acknowledgment requested from
the UE for successful reception
16 SS starts timer of tmax =(6 minutes + cell
selection time)
(Note 1, 2 and 3)
17 The UE transmits an ULInformationTransfer --> NR RRC: ULInformationTransfer 1 P
message and REGISTRATION COMPLETE 5G MM: REGISTRATION
message carrying acknowledgement of COMPLETE
successful reception of the steering of roaming
information
- EXCEPTION: Step 18a1 is performed in - - - -
pc_noOf_PDUsSameConnection > 0.
18a The generic procedure for UE-requested PDU - - - -
1 session establishment, specified in subclause
4.5A.2, takes place performing establishment
of UE-requested PDU session(s) with
ExpectedNumberOfNewPDUSessions =
pc_noOf_PDUsSameConnection.
18a Void. - - - -
2-
18a
5a1
18 The SS transmits an RRCRelease message. <-= NR RRC: RRCRelease
A
- EXCEPTION: Step 18Ba1 is performed if - - - -
pc_noOf_PDUsNewConnection > 0 and the
UE starts PDU session establishment
automatically
18 The generic procedure for UE-requested PDU - - - -
Ba session establishment, specified in subclause
1 4.5.2.2-4, takes place from step 2 to 9a1
performing establishment of UE-requested
PDU session(s) with
pc_noOf_PDUsNewConnection on NR Cell 13
and then release the RRC Connection.
19 Check: Does the UE transmits an --> NR RRC: RRCSetupRequest 1 P
RRCSetupRequest on NR Cell 11 before tmax
expires?
(Note 1, 2 and 3)
20- Steps 3-4 of Table 4.5.2.2-2 of the generic - - - -
21 procedure in TS 38.508-1 [4] are performed.
(Note 4)
1- Registration in step 21, THEN steps 5 to 20a1
22a of the registration procedure described in TS
16a 38.508-1 [4] Table 4.5.2.2-2 are performed on
1 NR Cell 11.
22b Void - - - -
1-
22b
2
ETSI

3- Mobility Registration in step 21, THEN steps 4
22b to 6a1 of the generic test procedure in TS
5a1 38.508-1 [4] Table 4.9.5.2.2-1 are performed
on NR Cell 11.
Note 1: Timer tmax in step 16 and 19 are derived from the high priority PLMN search timer T defined by
EFHPPLMN
setting (Refer to TS 23.122 Rel-12).Hence, window between 120s to T+Tolerance is being used , where
the high priority PLMN search timer T defined by EFHPPLMN
Note 3: Tolerance of 5min is added to allow time for the UE to find the proper PLMN
6.3.1.1.5 Specific message contents
Table 6.3.1.1.5-1: REGISTRATION ACCEPT for NR Cell 13 (step 15, Table 6.3.1.1.4-1)
Derivation Path: 38.508-1 Table 4.7.1-7

SOR Transparent Container Present The SOR
transparent
container carries
steering of
roaming
information.
SoR-MAC-IAUS Set to match the
calculated SoR-MAC-
IAUS as the way defined
in TS 33.501 A.17
CounterSOR Value generated as per
TS 33.501 Cl 6.14.2.3
SOR data type 0 The SOR
transparent
container carries
steering of
roaming
information.
List indication value 1 List of preferred
PLMN/access
technology
combinations is
provided
List type 1 The list type is a
PLMN ID and
access
technology list
Acknowledgement (ACK) value 1 Acknowledgement
requested
PLMN ID 1 PLMN2
Access Technology Identifier 1 NG-RAN
Table 6.3.1.1.5-2: Void
ETSI
Table 6.3.1.1.5-3: REGISTRATION COMPLETE for NR Cell 13 (step 17, Table 6.3.1.1.4-1)

transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
Table 6.3.1.1.5-4: Void
Table 6.3.1.1.5-5: REGISTRATION ACCEPT for NR Cell 11 (step 22a10, Table 6.3.1.1.4-1)

transparent
container carries
steering of
roaming
information.
calculated SoR-MAC-
IAUS as the way
defined in TS 33.501
A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
requested
PLMN ID 1 PLMN2
ETSI
Table 6.3.1.1.5-6: REGISTRATION COMPLETE for NR Cell 11 (step 22a11, Table 6.3.1.1.4-1)

transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
6.3.1.2 Steering of UE in roaming during registration/security check successful but

SOR Transparent container indicates ACK has been NOT been requested
(1)
with {UE being in automatic PLMN selection mode, current VPLMN not part of “PLMNs where registration
ensure that {
when {SOR Transparent container indicates ACK has NOT been requested & List Type indicates PLMN ID
and Access technology list in REGISTRATION ACCEPT and security check is successful and if the UE has
a list of available and allowable PLMNs in the area and based on this list the UE determines that
there is a higher priority PLMN than the currently camped chosen VPLMN}
then {the UE shall send the REGISTRATION COMPLETE message to the serving AMF without including
an SOR transparent container and then either releases N1 NAS Signaling connection locally and then
attempt to obtain service on a higher priority PLMN or optionally wait for network release of the
NAS signalling connection and then selects higher priority PLMN}
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause C.2, TS
24.501 clause 4.4.4.2 and 5.5.1.2.4. Unless otherwise stated these are Rel-15 requirements.
[TS 23.122, clause C.2]
COMPLETE message;
- the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41].
ETSI
ii) not release the current N1 NAS signalling connection locally and skip steps 8 and 10;
8) If:
ETSI
the N1 NAS signaling connection is not released after implementation dependent time, the UE may locally
release the N1 signaling connection except when the UE is registered for emergency services or the UE has an
The list of "PLMNs where registration was aborted due to SOR" is deleted when the UE is switched off or the USIM is
removed.
[TS 24.501 clause 4.4.4.2]
The network can provide the SOR transparent container IE during the registration procedure to the UE in the
REGISTRATION ACCEPT message. The SOR transparent container IE is integrity protected by the HPLMN as
specified in 3GPP TS 33.501 [24].
[TS 24.501 clause 5.5.1.2.4]
If the REGISTRATION ACCEPT message includes the SOR transparent container IE and the SOR transparent
container IE successfully passes the integrity check (see 3GPP TS 33.501 [24]):
a) the UE shall proceed with the behaviour as specified in 3GPP TS 23.122 [5] annex C; and
b) if the registration procedure is performed over 3GPP access and the UE attempts obtaining service on another
PLMNs as specified in 3GPP TS 23.122 [5] annex C, then the UE may locally release the established N1 NAS
signalling connection after sending a REGISTRATION COMPLETE message. Otherwise the UE shall send a
REGISTRATION COMPLETE message and not release the current N1 NAS signalling connection locally. If an
acknowledgement is requested in the SOR transparent container IE of the REGISTRATION ACCEPT message,
the UE acknowledgement is included in the SOR transparent container IE of the REGISTRATION COMPLETE
message.
If the SOR transparent container IE successfully passes the integrity check (see 3GPP TS 33.501 [24]), indicates list of
preferred PLMN/access technology combinations is provided and the list type indicates:
a) "PLMN ID and access technology list", then the ME shall replace the highest priority entries in the "Operator
Controlled PLMN Selector with Access Technology" list stored in the ME and shall proceed with the behaviour
as specified in 3GPP TS 23.122 [5] annex C; or
b) "secured packet", then the ME shall behave as if a SMS is received with protocol identifier set to SIM data
download, data coding scheme set to class 2 message and SMS payload as secured packet contents of SOR
transparent container IE. The SMS payload is forwarded to UICC as specified in 3GPP TS 23.040 [4A] and the
ME shall proceed with the behaviour as specified in 3GPP TS 23.122 [5] annex C.
ETSI
System Simulator:
- Three inter-frequency multi-PLMN NR Cells as specified in TS 38.508-1 [4] Table 4.4.2-1 are configured
- The PLMNs are identified in the test by the identifiers in Table 6.3.1.2.3.1-1. The MCC and MNC values

NR Cell PLMN names
NR Cell 11 PLMN2
NR Cell 12 PLMN13
NR Cell 13 PLMN14
NR Cell 11 is set to ''Serving Cell”;
System Information Combination NR-4 as defined in TS38.508-1 [4] clause 4.4.3.1.3 is used in NR cells.
UE:
Preamble:
ETSI
ETSI

U-S Message
1 Power on the UE. - - -
message and a REGISTRATION ACCEPT 5G MM: REGISTRATION
information indicating that acknowledgment is
not requested from the UE for successful
reception.
16 The SS also starts timer of tmax = (6 minutes - - - -
+ cell selection time) (Note 1, 2 and 3)
17 The UE transmits an ULInformationTransfer --> NR RRC: ULInformationTransfer -1 -
message without Steering of Roaming COMPLETE
Transparent container.
- EXCEPTION: Steps 18a1-18a5 are performed - - - -
IF pc_SOR_ACKNotReqLocalRel is False,
ELSE step 18b1 is performed.
- EXCEPTION: Step 18a1a1 is performed in - - - -
1a1 session establishment, specified in subclause
4.5A.2, takes place performing establishment
18a The SS transmits an RRCRelease message. <-= NR RRC: RRCRelease - -
2
- EXCEPTION: Step 18a2a1 is performed if - - - -
automatically
3a1 session establishment, specified in subclause
4.5.2.2-4, takes place from step 2 to 9a1
PDU session(s) with
pc_noOf_PDUsNewConnection and then
release the RRC Connection.
18a Void - - - -
4-
18a
5a1
18b The SS locally releases the RRC connection. - - - -
1
19 Void - - - -
RRCSetupRequest message on NR Cell 11
(Note 1, 2 and 3)
21 The SS transmits an RRCSetup message on <-- NR RRC: RRCSetup - -
NR Cell 11.
22 The UE transmits an RRCSetupComplete --> NR RRC: RRCSetupComplete - -
message and a REGISTRATION REQUEST 5GMM: REGISTRATION
message on NR Cell 11. REQUEST
(Note 4)
parameter has a particular value
ETSI

1 NR Cell 11.
23b Void - - - -
1-
23b
2
on NR Cell 11.
24- Void - - - -
26
Note 1: Timer tmax in step 16 and 20 are derived from the high priority PLMN search timer T defined by
EFHPPLMN
setting (Refer to TS 23.122 Rel-12). Hence, window between 120s to T+Tolerance is being used, where
Note 4: The 5GS registration type shall be only set as Mobility Registration for Rel-16 UEs according to TS 24.501
subclause 5.2.3.2.5 specified in Release 16. The EXCEPTION description applies only to Rel-15 UEs.
ETSI

transparent
container carries
steering of
roaming
information.
calculated SoR-MAC-
in TS 33.501 A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
is NOT requested
PLMN ID 1 PLMN2
PLMN ID 2 PLMN13
PLMN ID 3 PLMN14
Table 6.3.1.2.5-2: Void

SOR Transparent Container Not Present The SOR
transparent
container should
not be present
when ACK is not
requested by
UDM.
ETSI

transparent
container carries
steering of
roaming
information.
calculated SoR-MAC-
IAUS as the way
A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
is NOT requested
PLMN ID 1 PLMN2
PLMN ID 2 PLMN13
PLMN ID 3 PLMN14
6.3.1.3 Steering of UE in roaming during registration/security check

unsuccessful/Automatic mode
(1)
with {UE being in automatic PLMN selection mode and current VPLMN not part of “PLMNs where
registration was aborted due to SOR” List and not part of "User Controlled PLMN Selector with Access
Technology" list and UE's USIM configured with indication that the UE is to receive Steering of
Roaming information due to initial registration in a VPLMN}
ensure that {
when {Security check on the steering of roaming information SOR Transparent container is
unsuccessful}
then {UE sends REGISTRATION COMPLETE message to the serving AMF without including an SOR
transparent container and releases the current N1 NAS signalling connection locally and attempts to
obtain service on a higher priority PLMN}
}
ETSI
[TS 23.122, clause C.2]
COMPLETE message;
- the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41];
8) If:
ETSI
the N1 NAS signalling connection is not released after implementation dependent time, the UE may locally
release the N1 signalling connection except when the UE is registered for emergency services or the UE has an
removed.
System Simulator:

NR Cell PLMN names
NR Cell 11 PLMN2
NR Cell 12 PLMN13
NR Cell 13 PLMN14
UE:
ETSI
- USIM configuration as defined in Table 6.4.1-10 of TS 38.508-1 [4] will be used.
Preamble:
ETSI

U-S Message
1 Power on the UE - - - -
are performed on NR Cell 13
15 The SS transmits a DLInformationTransfer <-- NR RRC: DLInformationTransfer - -
information, includes unmatched SOR-MAC-
IAUSF that will result in unsuccessful security
check while on UE reception
16 SS starts timer of tmax =(6 minutes + cell - - - -
selection time)
(Note 1, 2 and 3)
message without including an SOR COMPLETE
transparent container
18- Void - - - -
21a
1
22 The SS locally releases the RRC connection. - - - -
(Note 1, 2 and 3)
NR Cell 12.
(Note 4)
1 NR Cell 12.
26b Void - - - -
1-
26b
2
on NR Cell 12.
27- Void. - - - -
28a
1
Note 1: Timer tmax in step 16 and 23 are derived from the high priority PLMN search timer T defined by EFHPPLMN
setting (Refer to TS 23.122 Rel-12). Hence, window between 120s to T+Tolerance is being used , where
ETSI
Derivation Path: TS 38.508-1 [4] Table 4.7.1-7

transparent
container carries
steering of
roaming
information.
SoR-MAC-IAUS Set to mismatch the
calculated SoR-MAC-
IAUS as the way
A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
requested
PLMN ID 1 PLMN2
Table 6.3.1.3.5-2: Void

transparent
container is not
included in
REGISTRATION
COMPLETE
message
ETSI

transparent
container carries
steering of
roaming
information.
calculated SoR-MAC-
in TS 33.501 A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
requested
PLMN ID 1 PLMN13
Table 6.3.1.3.5-5: REGISTRATION COMPLETE for NR Cell 13 (step 26a11, Table 6.3.1.3.4-1)

transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
6.3.1.4 Steering of UE in roaming during registration/security check

unsuccessful/Manual mode
ETSI
(1)
with {UE being in manual PLMN selection mode and current VPLMN not part of “PLMNs where registration
ensure that {
when {Security check on the steering of roaming information SOR Transparent container is
unsuccessful}
then {UE sends REGISTRATION COMPLETE message to the serving AMF without including an SOR
transparent container and stays on this VPLMN}
}
[TS 23.122, clause C.2]
COMPLETE message;
8) If:
ETSI
removed.
System Simulator:
- Two inter-frequency multi-PLMN NR Cells as specified in TS 38.508-1 [4] Table 4.4.2-1 are configured
ETSI

NR Cell PLMN names
NR Cell 11 PLMN2
NR Cell 12 PLMN13
NR Cell 11 is set to "Serving Cell";
System Information Combination NR-4 as defined in TS 38.508 [4] clause 4.4.3.1.3 is used in NR cells.
UE:
Preamble:
- The UE is in Switched OFF (State 0-A) as defined in TS 38.508-1 [4] Table 4.4A.2-0

U-S Message
2 PLMN13 is manually selected - - - -
21a described in TS 38.508-1 [4] Table 4.5.2.2-2
1
23 SS starts timer of 1 minute and waits this timer - - - -
expires
24 Check: Does the UE is in state 5GC - - 1 P
RRC_IDLE on NR Cell 12 as specified in TS
38.508-1 [4] Table 4.9.4.2.2-1?
25 The SS configures: - - - -
- NR Cell 11 as a "Non-Suitable "off" cell ".
26 The user sets the UE in Automatic PLMN - - - -
selection mode.
ETSI

transparent
container carries
steering of
roaming
information.
Table 6.3.1.4.5-2: SOR Transparent Container in REGISTRATION ACCEPT for NR Cell 12 (step 16,
Table 6.3.1.4.4-1)
Derivation Path: TS 24.501 [22] Figure 9.11.3.51.1

calculated SoR-MAC-
in TS 33.501 A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
requested
PLMN ID 1 PLMN2

transparent
container is not
included in
REGISTRATION
COMPLETE
message
ETSI
6.3.1.5 Steering of UE in roaming during registration/UE configured to receive

Steering of Roaming information but does not receive Steering of Roaming
from Network
(1)
with {the UE in Automatic PLMN Selection mode, VPLMN not part of “PLMNs where registration was
aborted due to SOR” List and not part of “User Controlled PLMN Selector with Access Technology” &
UE's USIM configured with indication that the UE is to receive Steering of Roaming information due
to initial registration in a VPLMN and the PDU session for emergency services is not pending to be
activated}
ensure that {
when {neither the list of preferred PLMN/access technology combinations nor the HPLMN indication
that “no change of the ‘Operator Controlled PLMN Selector with Access Technology’ list stored in the
UE is needed and thus no list of preferred PLMN/access technology combinations is provided” is
received in the REGISTRATION ACCEPT message}
then {UE releases N1 NAS Signalling connection locally, adds PLMN to “PLMNs where registration
was aborted due to SOR” and performs PLMN selection with current VPLMN considered as lowest
priority}
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clauses C.1 and C.2.
[TS 23.122, clause C.1]
If:
- the UE's USIM is configured to indicate that the UE shall expect to receive the steering of roaming information
during initial registration procedure but did not receive it or security check on the steering of roaming
information fails;
- the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR";
- the current chosen VPLMN is not part of "User Controlled PLMN Selector with Access Technology" list; and
- the UE is not in manual mode of operation;
then the UE will perform PLMN selection with the current VPLMN considered as lowest priority.
[TS 23.122, clause C.2]
COMPLETE message;
ETSI
8) If:
ETSI
removed.
System Simulator:

NR Cell PLMN names
NR Cell 11 PLMN2
NR Cell 12 PLMN13
NR Cell 13 PLMN14
UE:
Preamble:
ETSI
ETSI

U-S Message
selection time)
(Note 1, 2 and 3)
17 The UE transmits an ULInformationTransfer --> NR RRC: ULInformationTransfer - -
- EXCEPTION: Step 17Aa1a1 is performed in - - - -
Aa session establishment, specified in subclause
1a1 4.5A.2, takes place performing establishment
17 The SS transmits an RRCRelease message. <-= NR RRC: RRCRelease - -
Aa
2
- EXCEPTION: Step 17Aa3a1 is performed if - - - -
automatically
Aa session establishment, specified in subclause
3a1 4.5.2.2-4, takes place from step 2 to 9a1
PDU session(s) with
pc_noOf_PDUsNewConnection and then
release the RRC Connection.
18 Void - - - -
19 Check: Does the UE transmits an --> NR RRC: RRCSetupRequest 1 F
(Note 1, 2 and 3)
(Note 1, 2 and 3)
NR Cell 12.
(Note 4)
1 NR Cell 12.
23b Void - - - -
1-
23b
2
ETSI

on NR Cell 12.
Note 1: Timer tmax in step 16, 19 and 20 are derived from the high priority PLMN search timer T defined by
EFHPPLMN
Table 6.3.1.5.5-1: REGISTRATION COMPLETE for NR Cell 13 (step 17 Table 6.3.1.5.4-1)

transparent
container is not
included in
REGISTRATION
COMPLETE
message
ETSI
Table 6.3.1.5.5-1A: REGISTRATION ACCEPT for NR Cell 13 (step 23a10 Table 6.3.1.5.4-1)

transparent
container carries
steering of
roaming
information.
calculated SoR-MAC-
IAUS as the way
A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
is NOT requested
PLMN ID 1 PLMN13
PLMN ID 2 PLMN14
PLMN ID 3 PLMN2
Table 6.3.1.5.5-2: Void
6.3.1.6 Void
6.3.1.7 Steering of UE in roaming during registration/security check unsuccessful but

emergency service pending to be activated
(1)
with {the UE in Automatic PLMN Selection mode and current VPLMN not part of “PLMNs where
Roaming information due to initial registration in a VPLMN and there is a PDU session for emergency
services pending to be activated}
ensure that {
when {Steering of information is received but security check is unsuccessful}
then {UE will continue with the registration procedure on the VPLMN so as to be able to
establish the emergency PDU session}
}
ETSI
[TS 23.122, clause C.2]
COMPLETE message;
8) If:
ETSI
removed.
When the UE performs registration procedure for emergency services (see 3GPP TS 24.501 [64] and
3GPP TS 23.502 [63]) while the UE has a valid USIM and the AMF performs the authentication procedure, then based
on HPLMN policy, the SOR procedure described in this subclause may apply.
NOTE 3: The HPLMN/UDM cannot distinguish between "initial registration" and "emergency registration" thus
SOR implicitly applies for emergency registration.
System Simulator:
- One inter-frequency multi-PLMN NR Cell as specified in TS 38.508-1 [4] Table 4.4.2-1 are configured

NR Cell PLMN names
NR Cell 11 PLMN2
ETSI
UE:
Preamble:
ETSI

U-S Message
1A Steps 1 to 13 of the registration procedure - - - -
1- described in TS 38.508-1 [4] Table 4.5.2.2-2
1A are performed on NR Cell 11.
13
1B SS transmits a REGISTRATION REJECT <-- NR RRC: DLInformationTransfer - -
message with cause #22 (Congestion) and 5GMM: REGISTRATION
T3346 set to 3 minutes. REJECT
(Note 1)
1C The SS releases the RRC connection. - - - -
2 Cause the UE to originate Emergency call. - - - -
(Note 2)
3 The UE transmits an RRCSetupRequest --> NR RRC: RRCSetupRequest - -
message on NR Cell 11 with
establishmentCause set to 'emergency'.
4-5 Steps 3 to 4 of the registration procedure - - - -
described in TS 38.508-1 [4] Table 4.5.2.2-2
are performed.
6 The UE transmit a REGISTRATION --> 5G MM: REGISTRATION - -
REQUEST message with IE 5GS registration REQUEST
type set to "Emergency registration" or “Initial
registration”.
(Note 3)
17 Check: Does the UE transmit an UL NAS --> 5GMM: UL NAS TRANSPORT 1 P
TRANSPORT message with "Request type" 5GSM: PDU SESSION
set to "initial emergency request", and a PDU ESTABLISHMENT REQUEST
SESSION ESTABLISHMENT REQUEST
message on NR Cell 11
18- Steps 9 to 13 of the procedure of "IMS - - - -
22 Emergency call establishment in 5GC with
IMS emergency registration" described in TS
38.508-1 [4] Table 4.9.11.2.2-1 are
performed.
23 Generic procedure of "Test Procedure for IMS - - - -
MO Emergency call release" described in TS
38.508-1 [4] Table 4.9.12A.2.2-1 are
performed.
24 The SS releases the RRC connection. <-- NR RRC: RRCRelease - -
Note 1: T3346 is set to 3 minutes.This is checked for 3 minutes less tolerance.
Note 2: This can be done by an AT/MMI command.
Note 3: 5GS registration type can set to either "initial registration" according to TS 24.501 clause5.2.2.3.3 or
"emergency registration" according to TS 24.501 clause 5.5.1.2.
ETSI
Table 6.3.1.7.5-0: REGISTRATION REJECT for NR Cell 11 (step 1B Table 6.3.1.7.4-1)

5GMM cause ‘00010110’B Cause #22
(Congestion)
T3346 value ‘00100011’B 3 minutes
Table 6.3.1.7.5-1: REGISTRATION REQUEST for NR Cell 11 (step 6 Table 6.3.1.7.4-1)
Derivation Path: TS 38.508-1 [4], Table 4.7.1-6, Condition EMERGENCY or INITIAL.
Table 6.3.1.7.5-2: REGISTRATION ACCEPT for NR Cell 11 11 (step 15, Table 6.3.1.7.4-1)

transparent
container carries
steering of
roaming
information.
Table 6.3.1.7.5-3: SOR Transparent Container in REGISTRATION ACCEPT for NR Cell 13 (step 15,
Table 6.3.1.7.4-1)

calculated SoR-MAC-
in TS 33.501 A.17
CounterSOR Value generated as
per TS 33.501 Cl
6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
requested
PLMN ID 1 PLMN2
ETSI
Table 6.3.1.7.5-4: REGISTRATION COMPLETE for NR Cell 11 (step 16 Table 6.3.1.7.4-1)

transparent
container is not
included in
REGISTRATION
COMPLETE
message
Table 6.3.1.7.5-5: UL NAS TRANSPORT (step 17, Table 6.3.1.7.4-1)
Derivation Path: TS 38.508-1 [4] Table 4.7.1-10, condition INITIAL_PDU_REQUEST.

Request type ‘011’B initial emergency
request
S-NSSAI Not Present
DNN Not Present
Table 6.3.1.7.5-6: PDU SESSION ESTABLISHMENT REQUEST (step 17, Table 6.3.1.7.4-1)
Derivation Path: TS 38.508-1 [4] Table 4.7.2-1.

PDU session ID A value that is not
currently being used by
another PDU session
PTI A value currently not
used
SSC mode ‘001’B SSC mode 1
6.3.1.8 Steering of UE in roaming after registration/Automatic PLMN selection mode
(1)
with {UE being in automatic PLMN selection mode and UE has registered onto a VPLMN}
ensure that {
when {SOR Transparent container included in DL NAS TRANSPORT message contains steering of roaming
information and indicates ACK has been requested and security check is successful}
then {UE sends an SOR transparent container with ACK in UL NAS TRANSPORT message and waits until
it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication before attempting to
obtain service on a higher priority PLMN
}
otherwise stated these are Rel-15 requirements
[TS 23.122, clause C.3]
2) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in
the DL NAS TRANSPORT message the steering of roaming information received from the UDM.
3) Upon receiving the steering of roaming information, the UE shall perform a security check on the list of
preferred PLMN/access technology combinations included in the DL NAS TRANSPORT message to verify that
the list of preferred PLMN/access technology combinations is provided by HPLMN, and:
a) if the security check is successful and:
ETSI
- if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]), the ME shall
upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41];
When the ME receives a USAT REFRESH command qualifier (see 3GPP TS 31.111 [41]) of type
"Steering of Roaming" it performs the procedure for steering of roaming in subclause 4.4.6 with an
exception that if the UE is in automatic network selection mode, then the UE shall wait until it moves to
idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64])
before attempting to obtain service on a higher priority PLMN (specified in subclause 4.4.6 bullet d);
- otherwise, the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector
with Access Technology" list stored in the ME with the received list of preferred PLMN/access
technology combinations. If the UE is in automatic network selection mode, then the UE shall wait until it
moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see
3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in
subclause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired.
If the last established PDU session is an emergency PDU session then the UE shall attempt to perform the
PLMN selection after the release of the emergency PDU session and expiration of timer T.
If the UDM has not requested an acknowledgement from the UE then steps 4 and 5 are skipped; and
b) if the security check is not successful and the UE is in automatic network selection mode, then the UE shall
wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see
subclause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that
the current PLMN is considered as lowest priority. If the last established PDU session is an emergency PDU
session then the UE shall attempt to perform the PLMN selection after the release of the emergency PDU
session and expiration of timer T.
If the UDM has not requested an acknowledgement from the UE then steps 4 and 5 are skipped;
4) The UE to the AMF: if the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT
message and the security check in step 2 was successful, the UE sends an UL NAS TRANSPORT message to
the serving AMF with an SOR transparent container including the UE acknowledgement;
System Simulator:
- The PLMNs are identified in the test by the identifiers in Table 6.3.1.8.3.1-1. The MCC and MNC values of
PLMN identifiers are specified in TS 36.523-1 [13], Table 6.0.1-1.

NR Cell PLMN names
NR Cell 11 PLMN2
NR Cell 12 PLMN13
NR Cell 13 PLMN14
ETSI
UE:
Preamble:

U-S Message
2 Whole registration procedure described in TS - - - -
38.508-1 [4] Table 4.5.2.2-2 are performed on
NR Cell 13, with “connected without release”
message containing steering of roaming 5GMM: DL NAS TRANSPORT
the UE for successful reception
selection time)
(Note 1, 2 and 3)
message carrying acknowledgement of 5GMM:UL NAS TRANSPORT
information
RRCSetupRequest on NR Cell 11 before tmax
expires?
(Note 1, 2 and 3)
8-9 Steps 3-4 of Table 4.5.2.2-2 of the generic - - - -
procedure in TS 38.508-1 [4] are performed.
(Note 4)
1 NR Cell 11.
10b Void. - - - -
1-
10b
2
on NR Cell 11.
ETSI
11- Void. - - - -
12a
1
Note 1: Timer tmax in step 4 and 7 are derived from the high priority PLMN search timer T defined by EFHPPLMN
Table 6.3.1.8.5-1: DL NAS TRANSPORT Message for NR Cell 13 (step 3, Table 6.3.1.8.4-1)

Payload Container Present The SOR
transparent
container in the
payload container
IE carries steering
of roaming
information.
calculated SoR-MAC-
IAUS as the way
A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
requested
PLMN ID 1 PLMN2
Table 6.3.1.8.5-2: Void
ETSI
Table 6.3.1.8.5-3: UL NAS TRANSPORT Message for NR Cell 13 (step 5, Table 6.3.1.8.4-1)

transparent
container in the
payload container
IE carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
Table 6.3.1.8.5-4: Void
6.3.1.9 Steering of UE in roaming after registration/Manual PLMN selection mode
(1)
with {UE being in manual PLMN selection mode and UE has registered onto a VPLMN}
ensure that {
when {SOR Transparent container included in DL NAS TRANSPORT message contains steering of roaming
information and indicates ACK has been requested and security check is successful}
then {UE sends an SOR transparent container with ACK in UL NAS TRANSPORT message and stays on
the VPLMN
}
[TS 23.122, clause C.3]
2) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in
the DL NAS TRANSPORT message the steering of roaming information received from the UDM.
3) Upon receiving the steering of roaming information, the UE shall perform a security check on the list of
preferred PLMN/access technology combinations included in the DL NAS TRANSPORT message to verify that
the list of preferred PLMN/access technology combinations is provided by HPLMN, and:
a) if the security check is successful and:
- if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]), the ME shall
upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41];
When the ME receives a USAT REFRESH command qualifier (see 3GPP TS 31.111 [41]) of type
"Steering of Roaming" it performs the procedure for steering of roaming in subclause 4.4.6 with an
ETSI
exception that if the UE is in automatic network selection mode, then the UE shall wait until it moves to
idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64])
before attempting to obtain service on a higher priority PLMN (specified in subclause 4.4.6 bullet d);
- otherwise, the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector
with Access Technology" list stored in the ME with the received list of preferred PLMN/access
technology combinations. If the UE is in automatic network selection mode, then the UE shall wait until it
moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see
subclause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired.
If the last established PDU session is an emergency PDU session then the UE shall attempt to perform the
PLMN selection after the release of the emergency PDU session and expiration of timer T.
If the UDM has not requested an acknowledgement from the UE then steps 4 and 5 are skipped; and
b) if the security check is not successful and the UE is in automatic network selection mode, then the UE shall
wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see
subclause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that
the current PLMN is considered as lowest priority. If the last established PDU session is an emergency PDU
session then the UE shall attempt to perform the PLMN selection after the release of the emergency PDU
session and expiration of timer T.
If the UDM has not requested an acknowledgement from the UE then steps 4 and 5 are skipped;
4) The UE to the AMF: if the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT
message and the security check in step 2 was successful, the UE sends an UL NAS TRANSPORT message to
the serving AMF with an SOR transparent container including the UE acknowledgement;
System Simulator:
- Two inter-frequency multi-PLMN NR Cells as specified in TS 38.508-1 [4] Table 4.4.2-1 are configured

NR Cell PLMN names
NR Cell 11 PLMN2
NR Cell 12 PLMN13
System Information Combination NR-4 as defined in TS38.508 clause 4.4.3.1.3 is used in NR cells.
UE:
ETSI
Preamble:

U-S Message
2 PLMN13 is manually selected. - - - -
3 Whole registration procedure described in TS - - - -
38.508-1 [4] Table 4.5.2.2-2 are performed on
NR Cell 12, with “connected without release”.
message containing steering of roaming 5GMM: DL NAS TRANSPORT
the UE for successful reception.
message carrying acknowledgement of 5GMM:UL NAS TRANSPORT
information.
6 The SS transmits an RRCRelease message. <-- NR RRC: RRCRelease - -
7 SS starts timer of 1 minute and waits this timer - - - -
expires.
8 Check: Does the UE is in state 5GC - - 1 P
RRC_IDLE on NR Cell 12 as specified in TS
38.508-1 [4] Table 4.9.4.2.2-1?
- NR Cell 11 as a "Non-Suitable "off" cell ".
10 The user sets the UE in Automatic PLMN - - - -
selection mode.
Table 6.3.1.9.5-1: DL NAS TRANSPORT Message for NR Cell 12 (step 4, Table 6.3.1.9.4-1)

transparent
container in the
payload container
IE carries steering
of roaming
information.
ETSI
Table 6.3.1.9.5-2: SOR Transparent Container in Payload Container IE of DL NAS TRANSPORT

Message for NR Cell 12 (step 4, Table 6.3.1.9.4-1)

calculated SoR-MAC-
in TS 33.501 A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
requested
PLMN ID 1 PLMN2
Table 6.3.1.9.5-3: UL NAS TRANSPORT Message for NR Cell 12 (step 5, Table 6.3.1.9.4-1)

transparent
container in the
payload container
IE carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
Table 6.3.1.9.5-4: SOR Transparent Container in Payload Container IE of UL NAS TRANSPORT

Message for NR Cell 12 (step 5, Table 6.3.1.9.4-1)

transparent
container carries
acknowledgement
of successful
reception of the
steering of
roaming
information.
6.3.1.10 Steering of UE in roaming during mobility update registration
ETSI
(1)
with {UE being in automatic PLMN selection mode , current VPLMN not part of “PLMNs where
Roaming information due to initial registration in a VPLMN}
ensure that {
when {UE performs mobility update Registration Procedure to cell belonging to VPLMN and chosen
VPLMN does not provide Steering of Roaming info}
then {UE continues to camp on the chosen VPLMN}
}
[TS 23.122, clause C.2]
2) Upon receiving REGISTRATION REQUEST message, the VPLMN AMF executes the registration procedure as
defined in subclause 4.2.2.2.2 of 3GPP TS 23.502 [63]. As part of the registration procedure:
a) if the VPLMN AMF does not have subscription data for the UE, the VPLMN AMF invokes
Nudm_SDM_Get service operation to the HPLMN UDM to get amongst other information the Access and
Mobility Subscription data for the UE (see step 14b in subclause 4.2.2.2.2 of 3GPP TS 23.502 [63]); or
b) if the VPLMN AMF already has subscription data for the UE and:
i) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "initial
registration" and the "SoR Update Indicator for Initial Registration" field in the UE context is set to 'the
UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type "initial
registration"' as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]); or
ii) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "emergency
registration" and the "SoR Update Indicator for Emergency Registration" field in the UE context is set to
'the UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type
"emergency registration"' as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]);
then the VPLMN AMF invokes Nudm_SDM_Get service operation message to the HPLMN UDM to
retrieve the steering of roaming information (see step 14b in subclause 4.2.2.2.2 of 3GPP TS 23.502 [63]);
otherwise the VPLMN AMF sends a REGISTRATION ACCEPT message without the steering of roaming
information to the UE and steps 3a, 3b, 3c, 3d, 4, 5, 6 are skipped;
priority PLMN than the selected VPLMN and the UE is in automatic network selection mode, then the UE shall
attempt to obtain service on a higher priority PLMN as specified in subclause 4.4.3.3 by acting as if timer T that
controls periodic attempts has expired after the release of the N1 NAS signalling connection. If the N1 NAS
signalling connection is not released after implementation dependent time, the UE may locally release the N1
signalling connection except when the UE has an established emergency PDU session (see 3GPP TS 24.501
[64]).
System Simulator:
ETSI

NR Cell PLMN names
NR Cell 1 PLMN14
NR Cell 12 PLMN13
NR Cell 11 PLMN14
- NR Cell 1 is set to ''Serving Cell'';
- NR Cell 12 is set to ''Not-Suitable Cell'';
- NR Cell 11 is set to ''Not-Suitable Cell'';
- TAI of NR Cell 11 is set to ''TAI-2'' and TAI of NR Cell 1 is set to ''TAI-1';'
- System Information Combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR cells.
UE:
Preamble:
- Ensure that the UE has cleared the RPLMN. And the UE is in Switched OFF (State 0-A) as defined in TS
38.508-1 [4] Table 4.4A.2-0.
ETSI

U-S Message
1 Power on the UE. - - -
information indicating that acknowledgement is
not requested from the UE for successful
reception.
message without SOR transparent container. COMPLETE
- NR Cell 11 as "Serving cell"
- NR Cell 1 as "Non-Suitable cell"
- NR Cell 12 as "Non-Suitable cell".
message on NR Cell 11.
20 SS transmits an RRCSetup message on NR NR RRC: RRCSetup - -
<--
Cell 11.
message to confirm the successful completion 5GMM: REGISTRATION
of the connection establishment and a REQUEST
indicating "mobility registration updating" on
NR Cell 11.
22 SS sends a REGISTRATION <-- NR RRC: DLInformationTransfer - -
ACCEPT message without including SOR 5GMM: REGISTRATION
transparent container on NR Cell 11. ACCEPT
23 Check: Does the UE send a REGISTRATION --> NR RRC: ULInformationTransfer 1 P
COMPLETE without including SOR 5GMM: REGISTRATION
transparent container on NR Cell 11? COMPLETE
on NR Cell 11.
- NR Cell 11 as "Serving cell"
- NR Cell 1 as "Non-Suitable cell"
- NR Cell 12 as "Serving cell".
26 Check: Does the UE transmit an - - 1 F
within timer T=6 minutes *(1+10% tolerance)?
NOTE: The timer T shall be set to 396s (6
minutes *(1+10% tolerance)), where the high
priority PLMN search timer is defined in
EFHPPLMN.

ETSI

transparent
container carries
steering of
roaming
information.
calculated SoR-MAC-
in TS 33.501 A.17
TS 33.501 Cl 6.14.2.3
transparent
container carries
steering of
roaming
information.
PLMN/access
technology
combinations is
provided
PLMN ID and
access
technology list
is not requested
PLMN ID 1 PLMN 14
PLMN ID 2 PLMN 13

SOR Transparent Container Not Present


ETSI
6.4 UE Procedures in RRC_INACTIVE state

6.4.1 NG-RAN Only PLMN Selection in RRC_INACTIVE state
6.4.1.1 PLMN Selection/Higher priority/HPLMN in Automatic PLMN Selection Mode
(1)
with { UE in NR RRC_INACTIVE state on an NG-RAN VPLMN cell }
ensure that {
when { UE performs PLMN Selection to a PLMN that is equivalent PLMN of the registered PLMN }
then { UE remains in RRC_INACTIVE state after moving to the Equivalent PLMN cell. }
}
(2)
with { UE in NR RRC_INACTIVE state on an NG-RAN VPLMN cell and cells of a higher priority NG-RAN
PLMN available }
ensure that {
when { Higher priority PLMN search timer T expires }
then { UE selects the higher priority PLMN cell, moves to RRC_IDLE and attempts Registration on
the selected cell. }
}
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.4.3.3, TS
38.304 clauses 4.1 and clauses 4.2 and TS 24.501 clauses 5.3.1.4. Unless otherwise stated these are Rel-15
requirements.
[TS 23.122, clause 4.4.3.3]
in 3GPP TS 36.306 [54]), 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 for T is stored in the SIM, a default value of 60 minutes is used for
T.
NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using 2 hour steps from
3GPP TS 36.306 [54]); and
3GPP TS 36.306 [54]),
ETSI
and
SIM, a default value of 60 minutes is use
for T.

d1) Periodic attempts may be postponed while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]).
d2) Periodic attempts may be postponed while the MS is receiving eMBMS transport service in idle mode (see
3GPP TS 23.246 [68]).
combination.
[TS 38.304, clause 4.1]
- PLMN selection;
ETSI
transitions from RRC_INACTIVE to RRC_IDLE, as specified in TS 24.501 [14].
associated RAT(s) may be set, as specified in TS 23.122 [9]. The NAS shall provide a list of equivalent PLMNs, if
available, that the AS shall use for cell selection and cell reselection.
PLMN, as specified in TS 23.122 [9].
If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in TS 23.122 [9] and
search for a suitable cell if another PLMN has been selected by NAS.
When the UE is in RRC_IDLE state, upper layers may deactivate AS layer when MICO mode is activated as specified
in TS 24.501 [14]. When MICO mode is activated, the AS configuration (e.g. priorities provided by dedicated
signalling) is kept and all running timers continue to run but the UE need not perform any idle mode tasks. If a timer
expires while MICO mode is activated it is up to the UE implementation whether it performs the corresponding action
immediately or the latest when MICO mode is deactivated. When MICO mode is deactivated, the UE shall perform all
idle mode tasks.
[TS 38.304, clause 4.2]
Table 4.2-1 presents the functional division between UE non-access stratum (NAS) and UE access stratum (AS) in
RRC_IDLE state and RRC_INACTIVE states. The NAS part is specified in TS 23.122 [9] and the AS part in the
present document.
ETSI
Table 4.2-1: Functional division between AS and NAS in RRC_IDLE state and RRC_INACTIVE state
RRC_IDLE and UE Non-Access Stratum UE Access Stratum
RRC_INACTIVE
state Process
PLMN Selection Maintain a list of PLMNs in priority order according Search for available PLMNs.
to TS 23.122 [9]. Select a PLMN using automatic
or manual mode as specified in TS 23.122 [9] and If associated RAT(s) is (are) set for the
request AS to select a cell belonging to this PLMN, search in this (these) RAT(s) and
PLMN. For each PLMN, associated RAT(s) may other RAT(s) for that PLMN as specified in
be set. TS 23.122 [9].
Evaluate reports of available PLMNs from AS for Perform measurements to support PLMN
PLMN selection. selection.
Maintain a list of equivalent PLMN identities. Synchronise to a broadcast channel to

identify found PLMNs.
Report available PLMNs with associated

RAT(s) to NAS on request from NAS or
autonomously.
Cell Control cell selection for example by indicating Perform measurements needed to support
Selection RAT(s) associated with the selected PLMN to be cell selection.
used initially in the search of a cell in the cell
selection. Detect and synchronise to a broadcast
channel. Receive and handle broadcast
Maintain a list of "Forbidden Tracking Areas" and information. Forward NAS system
provide the list to AS. information to NAS.
Search for a suitable cell. The cells

broadcast one or more 'PLMN identity' in
the system information. Respond to NAS
whether such cell is found or not.
If associated RATs is (are) set for the

PLMN, perform the search in this (these)
RAT(s) and other RATs for that PLMN as
If a cell is found which satisfies cell

selection criteria, camp on that cell.
Cell Maintain a list of equivalent PLMN identities and Perform measurements needed to support
Reselection provide the list to AS. cell reselection.
Maintain a list of "Forbidden Tracking Areas" and Detect and synchronise to a broadcast
provide the list to AS. channel. Receive and handle broadcast
information. Forward NAS system
information to NAS.
Change cell if a more suitable cell is found.

Location Register the UE as active after power on. Report registration area information to
registration NAS.
Register the UE's presence in a registration area,
for instance regularly or when entering a new
tracking area.
Deregister UE when shutting down.
Maintain a list of "Forbidden Tracking Areas".

RAN Notification Not applicable. Register the UE's presence in a RAN-
Area Update based notification area (RNA), periodically
or when entering a new RNA.
ETSI
[TS 24.501, clause 5.3.1.4]
This subclause is only applicable for UE's 5GMM mode over 3GPP access.
The UE is in 5GMM-CONNECTED mode with RRC inactive indication when the UE is in:
a) 5GMM-CONNECTED mode over 3GPP access at the NAS layer; and
b) RRC_INACTIVE state at the AS layer (see 3GPP TS 38.300 [27]).
Unless stated otherwise, the UE behaviour in 5GMM-CONNECTED mode with RRC inactive indication follows the
UE behaviour in 5GMM-CONNECTED over 3GPP access, except that:
a) the UE shall apply the mobility restrictions; and
b) the UE shall perform the PLMN selection procedures as in 5GMM-IDLE mode over 3GPP access.
The UE shall transition from 5GMM-CONNECTED mode over 3GPP access to 5GMM-CONNECTED mode with
RRC inactive indication upon receiving an indication from the lower layers that the UE has transitioned to
RRC_INACTIVE state.
The UE shall trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE
mode upon selection of a PLMN that is not an equivalent PLMN to the registered PLMN. The UE shall not trigger a
transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon entering a new
PLMN which is in the list of equivalent PLMNs.
System Simulator:
- NR Cell 12, NR Cell 13 and NR Cell 1 are configured according to TS 38.508-1 [4], Table 4.4.2-3.
in TS 36.523-1 [13] table 6.0.1-1..

NR Cell PLMN name
12 PLMN15
13 PLMN16
1 PLMN1
- System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cells.
UE:
- USIM configuration as defined in TS 38.508-1 [4] Table 6.4.1-1 will be loaded. The high priority PLMN search
timer T defined by EFHPPLMN is 6min.
Preamble:
ETSI
conditions after preamble, while column marked "T1"is to be applied subsequently in the Main behaviour. The exact
instants on which these values shall be applied are described in the texts in this clause.

Parameter Unit NR Cell NR Cell NR Cell Remarks
12 13 1
T0 SS/PBCH dBm/SCS -88 “Off” “Off” Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3
T1 SS/PBCH dBm/SCS -115 -78 “Off” Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3
T2 SS/PBCH dBm/SCS “Off” -88 -88 Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3

Parameter Unit NR Cell NR Cell NR Cell 1 Remarks
12 13
T0 SS/PBCH dBm/SCS -82 “Off” ”Off” Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.2-2
T1 SS/PBCH dBm/SCS FFS FFS ”Off” Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.2-2
T2 SS/PBCH dBm/SCS “Off” FFS FFS Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.2-2
ETSI
ETSI

U-S Message
0A SS adjusts cell levels according to row T0 of - - - -
table 6.4.1.1.3.2-1/2.
0B The UE is switched on. - - - -
0C SS starts timers of tmin = 2min and tmax = (6 - - - -
min + 5min) (Note 1).
0D The steps specified in generic procedure TS - - - -
38.508-1 Table 4.5.3.2-1 are performed
table 6.4.1.1.3.2-1/2.
2 Check: Does the UE transmit an - NR RRC: RRCResumeRequest 1 P
RRCResumeRequest message on NR Cell
13?
3 The SS transmits an RRCResume message. <-- NR RRC: RRCResume - -
4 The UE transmits an RRCResumeComplete --> NR RRC: RRCResumComplete - -
message indicating "mobility registration REQUEST
updating" is sent to update the registration of
NR Cell13.
4A- Steps 4 to 5 of the generic test procedure in - - - -
4B TS 38.508-1 [4] Table 4.9.5.2.2-1 with
condition MOBILITY are performed.
with suspend.
6 Void. - - - -
7 The SS transmits a Paging message including <-- NR RRC: Paging - -
a matched identity (correct fullI-RNTI) on NR
Cell 13.
8 Check: Does the UE transmit an --> NR RRC: RRCResumeRequest 1 P
RRCResumeRequest message to resume
RRC Connection by setting resumeIdentity to
the stored shortI-RNTI value on NR Cell 13?
10 The UE transmits an RRCResumeComplete --> NR RRC: RRCResumeComplete - -
message.
with suspend.
table 6.4.1.1.3.2-1/2.
after tmin expires but before tmax expires
(Note 1)?
14 Steps 3-4 of Table 4.5.2.2-2 of the generic - - 2 P
procedure in TS 38.508-1 [4] are performed
1 NR Cell 1. Note 2
on NR Cell 1. Note 2
ETSI
setting (Refer to TS 23.122 [38] Rel-15).Hence, window between 2min to T+Tolerance is being used,
where the high priority PLMN search timer T defined by EFHPPLMN. Tolerance of 5min is added to allow time
for the UE to find the proper PLMN.

SIB4 ::= SEQUENCE {
Cell 13
}
Cell 1
}
}
}

SIB4 ::= SEQUENCE {
Cell 12
}
Cell 1
}
}
}
Table 6.4.1.1.3.3-3: REGISTRATION ACCEPT for NR Cell 12 (step 0D, Table 6.4.1.1.3.2-3; step 14, TS
38.508-1 [4], Table 4.5.3.2-1)

ETSI
6.4.1.2 Cell reselection of ePLMN in manual mode
(1)
with { UE in NR RRC_INACTIVE state on a NR cell in manual PLMN Selection mode and network has
downloaded a list of equivalent PLMNs during the Registration procedure }
ensure that {
when { Higher ranked cell is a cell of a PLMN in the downloaded equivalent PLMN list }
then { UE reselects to the equivalent PLMN cell , and attempts Registration with mobility on the
selected cell. }
}
(2)
with { UE in NR RRC_INACTIVE state on a cell and network has downloaded a list of equivalent PLMNs
during Registration procedure for mobility }
ensure that {
when { Highest ranked cell is a cell of a PLMN not in the downloaded equivalent PLMN list }
then { UE does not reselect to the cell. }
}
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.4.3.1.2 and
TS 38.304, clauses 4.1 and clauses 4.2. Unless otherwise stated these are Rel-15 requirements.
[TS 23.122, clause 4.4.3.1.2]
In ii and iii, 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 present the PLMNs contained in the "PLMN Selector" data file in the SIM (in priority order).
In v, requirement h) in subclause 4.4.3.1.1 applies.
In i to v, requirements j), k) and l) in subclause 4.4.3.1.1 apply.
In GSM COMPACT, the non support of voice services shall be indicated to the user.
The HPLMN may provide on the SIM additional information on the available PLMNs. If this information is provided
then the MS shall indicate it to the user. This information, provided as free text may include:
- preferred partner,
ETSI
- roaming agreement status,
- supported services
Furthermore, the MS may indicate whether the available PLMNs are present on the EHPLMN list, the Forbidden list,
the User Controlled PLMN List or the Operator Controlled PLMN List. The MS may also indicate that the PLMN is not
present on any of these lists.
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 location areas for roaming",
"forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for
regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking
areas 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.
Once the MS has registered on a PLMN selected by the user, the MS shall not automatically register on a different
PLMN unless:
i) the new PLMN is declared as an equivalent PLMN by the registered PLMN;
ii) the user selects automatic mode;
iii) the user initiates an emergency call while the MS is in limited service state and either the network does not
broadcast the indication of support of emergency calls in limited service state, the registration request for
emergency services is rejected by the network or the attach request for emergency bearer services is rejected by
the network; or
iv) the user initiates access to RLOS, while the MS is in limited service state and either the network does not
broadcast the indication of support of RLOS in limited service state, or the EPS attach request for access to
RLOS is rejected by the network.
NOTE 2: If case iii) or iv) occurs, the MS can provide an indication to the upper layers that the MS has exited
manual network selection mode.
If the user does not select a PLMN, the selected PLMN shall be the one that was selected before the PLMN selection
procedure started. If no such PLMN was selected or that PLMN is no longer available, then the MS shall attempt to
camp on any acceptable cell and enter the limited service state.
[TS 38.304, clause 4.1]
- PLMN selection;
ETSI
idle mode tasks.
[TS 38.304, clause 4.2]
Table 4.2-1 presents the functional division between UE non-access stratum (NAS) and UE access stratum (AS) in
RRC_IDLE state and RRC_INACTIVE states. The NAS part is specified in TS 23.122 [9] and the AS part in the
present document.
ETSI
Table 4.2-1: Functional division between AS and NAS in RRC_IDLE state and RRC_INACTIVE state
RRC_IDLE and UE Non-Access Stratum UE Access Stratum
RRC_INACTIVE
state Process
PLMN Selection Maintain a list of PLMNs in priority order according Search for available PLMNs.
to TS 23.122 [9]. Select a PLMN using automatic
or manual mode as specified in TS 23.122 [9] and If associated RAT(s) is (are) set for the
request AS to select a cell belonging to this PLMN, search in this (these) RAT(s) and
PLMN. For each PLMN, associated RAT(s) may other RAT(s) for that PLMN as specified in
be set. TS 23.122 [9].
Evaluate reports of available PLMNs from AS for Perform measurements to support PLMN
PLMN selection. selection.
Maintain a list of equivalent PLMN identities. Synchronise to a broadcast channel to

identify found PLMNs.
Report available PLMNs with associated

RAT(s) to NAS on request from NAS or
autonomously.
Cell Control cell selection for example by indicating Perform measurements needed to support
Selection RAT(s) associated with the selected PLMN to be cell selection.
used initially in the search of a cell in the cell
selection. Detect and synchronise to a broadcast
channel. Receive and handle broadcast
Maintain a list of "Forbidden Tracking Areas" and information. Forward NAS system
provide the list to AS. information to NAS.
Search for a suitable cell. The cells

broadcast one or more 'PLMN identity' in
the system information. Respond to NAS
whether such cell is found or not.
If associated RATs is (are) set for the

PLMN, perform the search in this (these)
RAT(s) and other RATs for that PLMN as
If a cell is found which satisfies cell

selection criteria, camp on that cell.
Cell Maintain a list of equivalent PLMN identities and Perform measurements needed to support
Reselection provide the list to AS. cell reselection.
Maintain a list of "Forbidden Tracking Areas" and Detect and synchronise to a broadcast
provide the list to AS. channel. Receive and handle broadcast
information. Forward NAS system
information to NAS.
Change cell if a more suitable cell is found.

Location Register the UE as active after power on. Report registration area information to
registration NAS.
Register the UE's presence in a registration area,
for instance regularly or when entering a new
tracking area.
Deregister UE when shutting down.
Maintain a list of "Forbidden Tracking Areas".

RAN Notification Not applicable. Register the UE's presence in a RAN-
Area Update based notification area (RNA), periodically
or when entering a new RNA.
ETSI
System Simulator:
- NR Cell 1, NR Cell 12 and NR Cell 13 are configured according to TS 38.508-1, Table 4.4.2-3.
- System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cell 1 and
NR cell 12.
- System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cell 13.
UE:
Preamble:
- The UE is registered on NR Cell 1 except that the REGISTRATION ACCEPT message indicates the PLMN of
NR Cell 12 in the Equivalent PLMN list as described in Table 6.4.1.2.3.3-4.
- The UE is in state 2N-A as defined in TS 38.508-1 [4], Table 4.4A.2-2 on NR Cell 1.
conditions after preamble, while columns marked "T1", "T2" and "T3" are to be applied subsequently in the Main
behaviour. The exact instants on which these values shall be applied are described in the texts in this clause.

1 12 13
SSS EPRE
T1 SS/PBCH dBm/SCS “Off” “Off” “Off” Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3

1 12 13
SSS EPRE
T1 SS/PBCH dBm/SCS “Off” “Off” “Off” Power level “Off” is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.2-2
ETSI

U-S Message
table 6.4.1.2.3.2-1/2.
RRCResumeRequest message on NR Cell
12?
3-6 Steps 2 to 5 of the generic test procedure in - - - -
TS 38.508-1 Table 4.9.5.2.2-1 with condition
MOBILITY are performed. (Note 1)
6A- Steps 5 to 8 of the generic test procedure in - - - -
6D TS 38.508-1 Table 4.5.4.2-3. (Note 3)
7 The SS transmits an RRCRelease message --> NR RRC: RRCRelease - -
with suspend.
8 Check: Does the UE send an --> NR RRC: RRCResumeRequest 2 F
RRCResumeRequest on NR Cell 13 and NR
Cell 1 within 60s?
table 6.4.1.2.3.2-1/2.
10 Set UE to Automatic PLMN selection mode. - - - -
(Note 2)
Note 1: The REGISTRATION REQUEST is accepted with the PLMN of NR Cell 1 listed as an Equivalent PLMN.
Note 2: Steps 10 is to ensure UE is set back to automatic PLMN selection mode for the next test case.
Note 3: No SERVICE ACCEPT message should be included in step 6C (corresponding to step 7 of Table 4.5.4.2-3
in TS 38.508-1 [4]).

SIB4 ::= SEQUENCE {
Cell 12
}
Cell 13
}
}
}
ETSI

SIB4 ::= SEQUENCE {
Cell 1
}
Cell 13
}
}
}

Equivalent PLMNs The PLMN of NR Cell 12

Equivalent PLMNs The PLMN of NR Cell 1
Allowed NSSAI
S-NSSAI
Table 6.4.1.2.3.3-4A: RRCReconfiguration for NR Cell 12 (step 6C, Table 6.4.1.2.3.2-2)
Derivation path: 38.508-1 [4] Table 4.6.1-13 with condition NR

dedicatedNAS-MessageList Not Present
ETSI
Table 6.4.1.2.3.3-5: RRCRelease (step 7, Table 6.4.1.2.3.2-2)
Derivation Path: 38.508-1 [4], Table 4.6.1-4B

suspendConfig SEQUENCE { NR_RRC_I
NACTIVE
ran-NotificationAreaInfo CHOICE {
cellList SEQUENCE {
plmn-Identity PLMN ID of NR
Cell 12
ran-AreaCells SEQUENCE {
cellIdentity See Table 4.4.2-2 and Cell Identity of NR
4.4.2-3 in TS 38.508-1 [4] Cell 12
}
}
}
}
}
}
}
6.4.2 Cell Selection/Qrxlevmin & Cell Reselection (Intra NR in

RRC_INACTIVE state)
6.4.2.1 Cell Selection/Qrxlevmin & Cell Reselection (Intra NR in RRC_INACTIVE

state)
(1)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { serving cell fulfils all requirements for a suitable cell except the cell selection
criteria which are not fulfilled (Srxlev<0) }
then { UE does not consider the cell as suitable , leaves RRC_INACTIVE state and does not remain
camped on that cell }
}
(2)
ensure that {
when { UE detects a cell ranked as the best cell }
then { UE reselects to the new cell and continues to remain in RRC_INACTIVE state }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.300, clause 9.2.1.1, and
TS 38.304, clause 4.1, 4.5, 5.2.1, 5.2.3.1 and 5.2.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.300, clause 9.2.1.1]
ETSI
is not barred.
On transition from RRC_CONNECTED or RRC_INACTIVE to RRC_IDLE, a UE should camp on a cell as

result of cell selection according to the frequency be assigned by RRC in the state transition message if any.
acceptable cell.
9.2.4).
[TS 38.304, clause 4.1]
- PLMN selection;
ETSI
idle mode tasks.
[TS 38.304, clause 4.5]
acceptable cell:
suitable cell:
- The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list and
trackingAreaCode is provided for that PLMN;
- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas" (TS 22.261 [12]),
barred cell:
A cell is barred if it is so indicated in the system information, as specified in TS 38.331 [3].
reserved cell:
A cell is reserved if it is so indicated in system information, as specified in TS 38.331 [3].
- 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 (TS 23.122 [9], TS 24.501 [14]) is
suitable but provides only limited service.
[TS 38.304, clause 5.2.1]
ETSI
selection criteria.
for NAS.
- if registered:
For cell reselection in multi-beam operations, the measurement quantity of this cell is derived amongst the beams
corresponding to the same cell based on SS/PBCH block as follows:
- if nrofSS-BlocksToAverage is not configured in SIB2/SIB4; or
- if absThreshSS-BlocksConsolidation is not configured in SIB2/SIB4; or
- if the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation:
- else:
BlocksToAverage of highest beam measurement quantity values above absThreshSS-BlocksConsolidation.
[TS 38.304, clause 5.2.3.1]
ETSI
[TS 38.304, clause 5.2.3.2]
where:
where:

cell.
concerned cell.
PPowerClass)) (dB);
else:
ETSI
System Simulator:
- NR Cell 1, NR Cell 2.
UE:
None.
Preamble:
and "T2" are applied at the points indicated in the Main behaviour description in Table 6.4.2.1.3.2-3.
1 2
T0 SS/PBCH dBm/SCS -88 Off The power level values are assigned to ensure the
SSS EPRE UE registered on NR Cell 1.
T1 SS/PBCH dBm/SCS -115 Off The power level values are assigned to satisfy Srxlev
SSS EPRE NR Cell 1 < 0.
T2 SS/PBCH dBm/SCS -88 -78 The power level values are assigned to satisfy RNR Cell
SSS EPRE 2 > RNR Cell 1.
Note 1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3.
1 2
T0 SS/PBCH dBm/SCS FFS Off The power level values are assigned to ensure the
SSS EPRE UE registered on NR Cell 1.
T1 SS/PBCH dBm/SCS FFS Off The power level values are assigned to satisfy Srxlev
SSS EPRE NR Cell 1 < 0.
T2 SS/PBCH dBm/SCS FFS FFS The power level values are assigned to satisfy RNR Cell
SSS EPRE 2 > RNR Cell 1.
Note 1: The uncertain downlink signal level is specified in TS 38.508-1 [4] section FFS.
ETSI

U-S Message
2 Void - - - -
2A Wait 15s. (Note 1) - - - -
3 The SS transmits a Paging message. <-- NR RRC: Paging - -
4 Check: Does the UE attempt to transmit an - - 1 F
uplink message within the next 10s?
5 The UE is switched off. - - - -
6 Void - - - -
6A Void - - - -
6B The SS changes NR Cell 1 SSS levels - - - -
1/2.
6C The UE is switched on. - - - -
7 Generic procedure specified in TS 38.508-1 - - - -
Table 4.5.3.2-1 are performed, in which the
RRCRelease message includes the
suspendConfig with NR_RRC_INACTIVE
condition thereby moving the UE to
RRC_INACTIVE.
8- Void - - - -
15
17 Void - - - -
RRCResumeRequest message on the NR Cell
2?
A
18 The UE transmit an RRCResumeComplete --> NR RRC: - -
B message. RRCResumeComplete
including suspendConfig with
NR_RRC_INACTIVE condition.
Note 1: As specified in TS 38.133 [30] clause 4.2.2.2, UE will wait DRXCycle * 2 to evaluate serving cell. If the UE
in RRC_IDLE has not found any new suitable cell based on searches and measurements using the intra-
frequency, inter-frequency and inter-RAT information indicated in the system information for 10 s, the UE
shall initiate cell selection procedures for the selected PLMN.The wait time is selected to cover DRXCycle *
2 = 1280ms * 2 = 2.56s + 10s = 12.56s rounded up to 13s. Therefore, the actual wait time is selected to
15s, in order to be greater than 13s.

SIB3 ::= SEQUENCE {
IntraFreqNeighCellInfo[1] SEQUENCE{ entry 1
physCellId Physical cell identity
of NR Cell 2
q-OffsetCell 0
}
}
}
ETSI
Table 6.4.2.1.3.3-2: RRCResume (step 18A, Table 6.4.2.1.3.2-3)

RRCResume ::= SEQUENCE {
rrcResume SEQUENCE {
masterCellGroup := SEQUENCE { CellGroupConfig Table 6.4.2.1.3.3-
3
}
}
}
Table 6.4.2.1.3.3-3: CellGroupConfig (Table 6.4.2.1.3.3-2)
Derivation Path: 38.508-1 [4], Table 4.6.3-19 with condition RESUME

CellGroupConfig ::= SEQUENCE {
spCellConfigDedicated ServingCellConfig
}
Table 6.4.2.1.3.3-4: ServingCellConfig (Table 6.4.2.1.3.3-3: CellGroupConfig)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-167 with condition RESUME

ServingCellConfig ::= SEQUENCE {
initialDownlinkBWP BWP-DownlinkDedicated
}
Table 6.4.2.1.3.3-5: BWP-DownlinkDedicated (Table 6.4.2.1.3.3-4: ServingCellConfig)

BWP-DownlinkDedicated ::= SEQUENCE {
pdcch-Config Not present
pdsch-Config CHOICE {
setup PDSCH-Config
}
}
Table 6.4.2.1.3.3-6: PDSCH-Config (Table 6.4.2.1.3.3-5: BWP-DownlinkDedicated)

PDSCH-Config ::= SEQUENCE {
dmrs-DownlinkForPDSCH-MappingTypeA Not present
tci-StatesToAddModList SEQUENCE(SIZE (1.. 1 entry
maxNrofTCI-States)) OF TCI-State {
TCI-State[1] SEQUENCE { entry 1
tci-StateId 0
qcl-type1 SEQUENCE {
referenceSignal CHOICE {
ssb SSB index #n SSB index of NR
Cell 2
}
}
}
}
prb-BundlingType Not present
}
ETSI
6.4.2.2 Inter-frequency cell reselection according to cell reselection priority provided

by SIBs in RRC_INACTIVE state
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the equal
then { UE reselects to the cell which belongs to the equal priority frequency and remains in
RRC_INACTIVE state }
}
(2)
ensure that {
then { UE reselects to the cell which belongs to the higher priority frequency and remains in
}
(3)
ensure that {
then { UE reselects to the cell which belongs to the lower priority frequency and remains in
}
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 4.1, 5.2.4.1,
[TS 38.304, clause 4.1]
- PLMN selection;
ETSI
idle mode tasks.
[TS 38.304, clause 5.2.4.1]
NAS (3GPP TS 23.122 [9]).
- a PLMN selection is performed on request by NAS (3GPP TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.2]
ETSI

[TS 38.304, clause 5.2.4.5]
TreselectionRAT
and
ETSI
- If the highest-priority frequency is an NR 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;
System Simulator:
UE:
- None.
Preamble:
the texts in this clause. The configuration "T0" indicates the initial conditions. Subsequent configurations marked "T1",
"T2" and "T3" are applied at the points indicated in the Main behaviour description in Table 6.4.2.2.3.2-3.
Cell 6, highP.
SSS EPRE SrxlevNR Cell 6 < Threshserving, lowP and SrxlevNR Cell
3 > ThreshNR Cell 3, lowP, SrxlevNR Cell 1< 0.
Note 1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3.
ETSI
T0 SS/PBCH dBm/SCS FFS Off Off The power level values are assigned to ensure
T1 SS/PBCH dBm/SCS FFS FFS Off The power level values are assigned to satisfy
T2 SS/PBCH dBm/SCS Off FFS FFS The power level values are assigned to satisfy
Cell 6, highP.
T3 SS/PBCH dBm/SCS Off FFS FFS The power level values are assigned to satisfy
SSS EPRE SrxlevNR Cell 6 < Threshserving, lowP and SrxlevNR Cell
3 > ThreshNR Cell 3, lowP, SrxlevNR Cell 1< 0.

U-S Message
2 Void - - - -
RRCResumeRequest message on the cell 3?
5 The SS changes NR Cell 1 and NR Cell 6 SSS - - - -
levels according to the row "T2" in table
6.4.2.2.3.2-1/2.
6 Void - - - -
10 Void - - - -
ETSI

SIB2 ::= SEQUENCE {
SEQUENCE {
}
}
Table 6.4.2.2.3.3-3: SIB4 of NR Cell 1, NR Cell 3 and NR Cell 6 (preamble and all steps, Table
6.4.2.2.3.2-3)

SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE 2 entries NR Cell 1
SIZE (1..maxFreq) OF SEQUECNCE { 1 entry NR Cell 3
and NR Cell
6
for NR Cell 6
for NR Cell 6
for NR Cell 3
threshX-HighP[1] 10 20 dB NR Cell 3
5 NR Cell 3
4 NR Cell 6
for NR Cell 3
}
}
6.4.3 Inter-RAT Cell Reselection
6.4.3.1 Inter-RAT cell reselection From NR RRC_INACTIVE to E-UTRA RRC_IDLE

(lower priority & higher priority, Srxlev based)
(1)
ensure that {
when { UE detects the cell re-selection criteria are met for the neighbour cell which belongs to
the higher priority E-UTRA frequency }
then { UE reselects to the E-UTRA cell and transitions to E-UTRA RRC_IDLE State }
}
(2)
ensure that {
when { UE detects the cell re-selection criteria are met for the neighbour cell which belongs to
the lower priority E-UTRA frequency }
then { UE reselects to the E-UTRA cell and transitions to E-UTRA RRC_IDLE State }
}
ETSI
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 4.1, 5.2.4.1,
[TS 38.304, clause 4.1]
- PLMN selection;
idle mode tasks.
[TS 38.304, clause 5.2.4.1]
ETSI
NAS (3GPP TS 23.122 [9]).
- a PLMN selection is performed on request by NAS (3GPP TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.2]

[TS 38.304, clause 5.2.4.5]
TreselectionRAT
ETSI
and
- If the highest-priority frequency is an NR 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;
System Simulator:
- NR Cell 1.
- System information combination NR-6 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in NR cell.
- E-UTRA Cell 1 and E-UTRA Cell 3.
- System information combination 31 as defined in TS 36.508 [7] Table 4.4.3.1.1-1 is used in E-UTRA cell 1 and
E-UTRA cell 3.
UE:
- None.
Preamble:
clause 4.5.2. 4G GUTI and eKSI are assigned and security context established
ETSI
[4], Table 6.2.2.1-3, the UE is brought to state 2N-A, RRC_INACTIVE Connectivity (NR), in accordance with
the procedure described in TS 38.508-1 [4], Table 4.5.3.2-1. 5G-GUTI and ngKSI are assigned and security
and "T2" are applied at the points indicated in the Main behaviour description in Table 6.4.3.1.3.2-3.
Parameter Unit NR E-UTRA E-UTRA Remark

dBm/15kHz - Off Off
RS EPRE ensure the UE registered on NR Cell 1.
T0
SS/PBCH
dBm/SCS -88 - -
SSS EPRE
dBm/15kHz - -78 Off
RS EPRE satisfy SrxlevE-UTRA Cell 1 > ThreshE-UTRA Cell
T1
SS/PBCH 1, HighP.
dBm/SCS -88 - -
SSS EPRE
dBm/15kHz - Off -76
RS EPRE satisfy SrxlevNR Cell 1 < Threshserving, LowP,
T2
SS/PBCH SrxlevE-UTRA Cell 3 > ThreshE-UTRA Cell 3, lowP,
dBm/SCS -98 - -
SSS EPRE and SrxlevE-UTRA Cell 1 < 0.
Note 1: Power level “Off” of NR cell is defined in TS 38.508-1 [4] Table 6.2.2.1-3.
Note 2: Power level “Off” of E-UTRA cell is defined in TS 36.508 [7] Table 6.2.2.1-3.

dBm/15kHz - Off Off
RS EPRE ensure the UE registered on NR Cell 1.
T0
SS/PBCH
dBm/SCS FFS - -
SSS EPRE
dBm/15kHz - FFS Off]
RS EPRE satisfy SrxlevE-UTRA Cell 1 > ThreshE-UTRA Cell
T1
SS/PBCH 1, HighP.
dBm/SCS FFS - -
SSS EPRE
dBm/15kHz - Off FFS
RS EPRE satisfy SrxlevNR Cell 1 < Threshserving, LowP,
T2
SS/PBCH SrxlevE-UTRA Cell 3 > ThreshE-UTRA Cell 3, lowP,
dBm/SCS FFS - -
SSS EPRE and SrxlevE-UTRA Cell 1 < 0.
ETSI

U-S Message
1 The SS changes E-UTRA Cell 1 SSS level - - - -
1/2.
2 Void - - - -
1?
4 The SS changes NR Cell 1 SSS levels - - - -
1/2.
5 Void - - - -
6 Steps of the generic test procedure in TS - - - -
38.508-1 [4] Table 4.9.9.2.2-1 are performed on
NR Cell 1.
7A- Steps 1-8 as defined in TS 38.508-1 [4] Table - - - -
7H 4.5.4.2-3
7I The SS transmits an RRCRelease message <-- NR RRC: RRCRelease - -
8 The SS changes NR Cell 1, E-UTRA Cell 1 and - - - -
E-UTRA Cell 3 SSS level according to the row
"T2" in table 6.4.3.1.3.2-1/2.
9 Void - - - -
3 with condition 'connected without release'?
11 At the end of this test procedure sequence, the - - - -
UE is in end state E-UTRA connected

SIB2 ::= SEQUENCE {
SEQUENCE {
}
}
ETSI

SIB5 ::= SEQUENCE {
carrierFreqListEUTRA SEQUENCE 2 entries
(SIZE (1..maxEUTRA-Carrier)) OF
CarrierFreqEUTRA {
carrierFreq Same downlink ARFCN as used
for E-UTRA Cell 1
}
carrierFreq Same downlink ARFCN as used
for E-UTRA Cell 3
}
}
}
6.4.3.1.3.2-3)
Derivation path: 36.508 [7] table 4.4.3.3-20

carrierFreq-r15 Same downlink
ARFCN as used
for NR Cell 1
}
}
}

EPS update type
updating with IMSI A_LA
attach

EPS update type
updating A_LA
UE radio capability information update needed Not Check UE radio
capability
information
update needed
ETSI
TA_only This condition applies if the UE is configured to initiate EPS attach or
if explicitly specified.
combined_TA_LA This condition applies if the UE is configured to initiate combined
EPS/IMSI attach or if explicitly specified.

message
6.4.3.1.3.2-3)
Derivation path: 36.508 [7] table 4.4.3.3-20

carrierFreq-r15 Same downlink
ARFCN as used
for NR Cell 1
threshX-High-r15 10
}
}
}
6.5 SNPN and CAG Selection

6.5.1 SNPN Only Selection
6.5.1.1 SNPN Selection in Manual Mode
(1)
with { UE in Manual network/SNPN selection mode and an SNPN cell is available for which an entry
does not exist in the "list of subscriber data" }
ensure that {
then { UE does not indicate to the user any available SNPNs }
}
(2)
with { UE in Manual network/SNPN selection mode }
ensure that {
when { an SNPN cell is available for which an entry exists in the "list of subscriber data" }
then { UE indicates to the user that an SNPN is available and user selects the SNPN }
}
ETSI
(3)
with { UE in Manual network/SNPN selection mode and has registered on an SNPN selected by the user }
ensure that {
when { an SNPN cell is available for which an entry exists in the "list of subscriber data" }
then { UE does not automatically register on the SNPN cell until the user selects automatic SNPN
selection mode }
}
[TS 23.122, clause 4.9.3.1.0]
At switch on, or following recovery from lack of coverage, the MS selects the registered SNPN (if it is available) using
NG-RAN access technology and if necessary (in the case of recovery from lack of coverage, see subclause 4.5.2)
attempts to perform an LR.
NOTE 1: The MS in automatic SNPN selection mode can end the SNPN search procedure once the registered
SNPN is found on NG-RAN access technology.
NOTE 2: An MS in automatic SNPN selection mode can use location information to determine which SNPNs can
If successful registration is achieved, the MS indicates the selected SNPN.
If there is no registered SNPN, or registration is not possible due to the SNPN being unavailable or registration failure,
the MS follows the procedure in subclause 4.9.3.1.1 or subclause 4.9.3.1.2 depending on its SNPN selection mode. At
switch on, the MS shall use the SNPN selection mode that was used before switching off.
NOTE 3: If successful registration is achieved, then the current serving SNPN becomes the registered SNPN and
the MS does not store the previous registered SNPN for later use.
If registration is not possible on recovery from lack of coverage due to the registered SNPN being unavailable, an MS
may, optionally, continue looking for the registered SNPN for an implementation dependent time.
NOTE 4: An MS registered to an SNPN should behave as described above only if one or more PDU sessions are
currently active.
[TS 23.122, clause 4.9.3.1.2]
The MS indicates to the user one or more SNPNs, which are available and each of them is identified by an SNPN
identity in an entry of the "list of subscriber data" in the ME. This includes SNPNs in the list of "permanently forbidden
SNPNs", and the list of "temporarily forbidden SNPNs". The MS may indicate to the user whether the available SNPNs
are present in the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs". The order in
which those SNPNs are indicated is MS implementation specific.
For each of the SNPNs indicated to the user, the UE shall forward a human-readable network name along with the
SNPN identity to the upper layers if the system information broadcasted for the SNPN includes the human-readable
network name for the SNPN.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
The user may select his desired SNPN and the MS then initiates registration on this SNPN using the NG-RAN access
technology, the subscriber identifier and the credentials from an entry of the "list of subscriber data", with the SNPN
identity matching the selected SNPN (this may take place at any time during the presentation of SNPNs).
Once the MS has registered on an SNPN selected by the user, the MS shall not automatically register on a different
SNPN unless the user selects automatic SNPN selection mode.
NOTE: Emergency services are not supported in SNPN access mode.
ETSI
If the user does not select an SNPN, the selected SNPN shall be the one that was selected either automatically or
manually before the SNPN selection procedure started. If no such SNPN was selected or that SNPN is no longer
available, then the MS shall attempt to camp on any acceptable cell and enter the limited service state.
System Simulator:
- 3 SNPN cells: NR Cell 1, NR Cell 2, and NR Cell 4 are configured broadcasting default SNPN IDs as indicated
in TS 38.508-1 [4] Table 4.4.2-4.
UE:
- The UE is in Manual SNPN selection mode.
- The UE is provisioned with a “list of subscriber data” to allow access to SNPN identified by NR Cell 2 and NR
Cell 4.
Preamble:
- Ensure that the UE has cleared the Registered SNPN and the UE is in state Switched OFF (state 0-A).
“T3” “T4”etc are applied at the points indicated in the Main behaviour description in Table 6.5.1.1.3.2-3. Cell powers
are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and
Table 6.2.2.2-2 for FR2.
T1 SS/PBCH dBm/SCS -88 “Off” “Off”
SSS EPRE
T2 SS/PBCH dBm/SCS -88 -88 “Off”
SSS EPRE
SSS EPRE
T4 SS/PBCH dBm/SCS -88 “Off” -78
SSS EPRE
SSS EPRE
SSS EPRE
SSS EPRE
SSS EPRE
ETSI

U-S Message
table 6.5.1.1.3.2-1/2.
3 The UE is made to perform manual SNPN - - - -
search and select SNPN identified by NR Cell
1.
4 Check: Does the UE transmit an --> RRCSetupRequest 1 F
next 60 s?
table 6.5.1.1.3.2-1/2.
6 The UE is made to perform manual SNPN - - - -
selection and select SNPN identified by NR
Cell 2.
table 6.5.1.1.3.2-1/2.
27 Check: Does the UE send a --> RRCSetupRequest 3 F
next 60 s?
28 The user sets the UE in Automatic - - - -
SNPN/Network selection mode.
table 6.5.1.1.3.2-1/2.
30 Check: Does the UE send an --> RRCSetupRequest 3 P
6.5.1.2 SNPN Selection in Automatic Mode
(1)
with { UE in Automatic SNPN selection mode and SNPN cell is available for which an entry does not
exist in the "list of subscriber data" }
ensure that {
then { UE does not only select the SNPN cell and continues searching for an allowable SNPN Cell
}
}
(2)
with { UE in Automatic SNPN selection mode and a Registered SNPN cell along with another better
ranked allowable SNPN cell becomes available }
ensure that {
then { UE selects the Registered SNPN cell and UE attempts a Registration on the selected cell }
}
(3)
with { UE in Automatic SNPN selection mode and Registration on a SNPN cell is unsuccessful}
ensure that {
ETSI
when { UE continues searching for an allowable SNPN Cell and a new allowable SNPN cell becomes
available }
then { the UE registers on the new SNPN cell }
}
[TS 23.122, clause 4.9.3.1.0]
At switch on, or following recovery from lack of coverage, the MS selects the registered SNPN (if it is available) using
NG-RAN access technology and if necessary (in the case of recovery from lack of coverage, see subclause 4.5.2)
attempts to perform an LR.
NOTE 1: The MS in automatic SNPN selection mode can end the SNPN search procedure once the registered
SNPN is found on NG-RAN access technology.
NOTE 2: An MS in automatic SNPN selection mode can use location information to determine which SNPNs can
If there is no registered SNPN, or registration is not possible due to the SNPN being unavailable or registration failure,
the MS follows the procedure in subclause 4.9.3.1.1 or subclause 4.9.3.1.2 depending on its SNPN selection mode. At
switch on, the MS shall use the SNPN selection mode that was used before switching off.
NOTE 3: If successful registration is achieved, then the current serving SNPN becomes the registered SNPN and
the MS does not store the previous registered SNPN for later use.
If registration is not possible on recovery from lack of coverage due to the registered SNPN being unavailable, an MS
may, optionally, continue looking for the registered SNPN for an implementation dependent time.
NOTE 4: An MS registered to an SNPN should behave as described above only if one or more PDU sessions are
currently active.
[TS 23.122, clause 4.9.3.1.0]
The MS selects another SNPN, if available, allowable, and identified by an SNPN identity in an entry of the "list of
subscriber data" in the ME. If more than one SNPN are available, allowable, and each of them is identified by an SNPN
identity in an entry of the "list of subscriber data" in the ME, how the MS selects one of those SNPNs is MS
implementation specific.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
Once the MS selects the SNPN, the MS attempts registrations on the selected SNPN using the NG-RAN access
technology, the subscriber identifier and the credentials from an entry of the "list of subscriber data" with the SNPN
identity matching the selected SNPN.
If registration cannot be achieved because no SNPNs are available, allowable, and identified by an SNPN identity in an
entry of the "list of subscriber data" in the ME, the MS indicates "no service" to the user, waits until a new SNPN is
available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME and then
repeats the procedure.
If there were one or more SNPNs which were available, allowable, and identified by an SNPN identity in an entry of the
"list of subscriber data" in the ME but an LR failure made registration on those SNPNs unsuccessful, the MS selects one
of those SNPNs again and enters a limited service state.
ETSI
System Simulator:
- 3 SNPN cells NR Cell 1, NR cell 2, NR Cell 3 are configured broadcasting default SNPN IDs as indicated in TS
38.508-1 [4] Table 4.4.2-4.
UE:
- The UE is in Automatic SNPN selection mode.
- The UE is provisioned with a “list of subscriber data” to allow access to SNPN identified by NR cell 1 and NR
cell 3.
Preamble:
- Ensure that the UE has cleared the Registered SNPN. And the UE is in state Switched OFF (state 0-A).
and “T3” are applied at the points indicated in the Main behaviour description in Table 6.5.1.2.3.2-3. Cell powers are
chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table
6.2.2.2-2 for FR2.
T1 SS/PBCH dBm/SCS “Off” -88 “Off” Power level “Off” is defined in TS 38.508-1 [4]
SSS EPRE Table 6.2.2.1-3.
T2 SS/PBCH dBm/SCS -88 -88 “Off” Power level “Off” is defined in TS 38.508-1 [4]
T3 SS/PBCH dBm/SCS -88 “Off” -78 Power level “Off” is defined in TS 38.508-1 [4]

T1 SS/PBCH dBm/SCS “Off” FFS “Off” Power level “Off” is defined in TS 38.508-1 [4]
T2 SS/PBCH dBm/SCS FFS FFS “Off” Power level “Off” is defined in TS 38.508-1 [4]
T3 SS/PBCH dBm/SCS FFS “Off” FFS Power level “Off” is defined in TS 38.508-1 [4]
ETSI

U-S Message
table 6.5.1.2.3.2-1/2.
3 Check: Does the UE transmit an --> NR RRC: RRCSetupRequest 1 F
next 60 s?
table 6.5.1.2.3.2-1/2.
5 Check: Does the UE send a --> NR RRC: RRCSetupRequest 1 P
table 6.5.1.2.3.2-1/2.
28- Steps 2-9 of Table 4.5.2.2-2 in TS38.508-1 [4] - - - -
36 The SS transmits a REGISTRATION REJECT <-- NR RRC: DLInformationTransfer - -
with cause #15 (No suitable cells in tracking 5GMM: REGISTRATION REJECT
area).
37 The SS releases the RRC connection - - - -
Table 6.5.1.2.3.3-1: REGISTRATION REJECT for NR Cell 1 (step 36 Table 6.5.1.2.3.2-3)

5GMM cause ‘00001111’B #15 (No suitable
cells in tracking
area).
6.5.2 CAG (Closed Access Group)
6.5.2.1 CAG Selection in Manual Mode
(1)
with { UE in Manual network selection mode and provided with CAG information list }
ensure that {
ETSI
when { there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the
CAG-ID is included in the "Allowed CAG list" }
then { UE manually selects the CAG cell }
}
(2)
with { UE in Manual network selection mode and PLMN ID of the PLMN in the "CAG information list" and
the CAG-ID are not included in the "Allowed CAG list" }
ensure that {
when { the available CAG cell broadcasts that the PLMN allows a user to manually select the CAG-ID
}
then { UE manually selects the CAG cell that is outside the UE's Allowed CAG list}
}
(3)
with { UE in Manual network selection mode }
ensure that {
when { there exists an entry for the presented PLMN in the "CAG information list" and the entry
includes an "indication that the MS is only allowed to access 5GS via CAG cells" }
then { UE manually selects the CAG cell }
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause 4.4.3.1.2.
[TS 23.122, clause 4.4.3.1.2]
Technology" data file in the SIM (in priority order) or stored in the ME (in priority order);
In i to v, if the MS supports CAG, for each PLMN/access technology combination of NG-RAN access technology, the
MS shall present to the user:
a) the PLMN/access technology combination and a list of CAG-IDs composed of one or more CAG-IDs such that
for each CAG-ID:
1) there is an available CAG cell which broadcasts the CAG-ID for the PLMN; and
2) the following is true:
i) there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is
included in the "Allowed CAG list" of the entry; or
ETSI
ii) the available CAG cell broadcasting the CAG-ID for the PLMN also broadcasts that the PLMN allows a
user to manually select the CAG-ID.
For each of the presented CAG-ID, the MS may indicate to the user whether the CAG-ID is present in the
"Allowed CAG list" stored in the UE; and
b) the PLMN/access technology combination without a list of CAG-IDs, if there is an available NG-RAN cell
which is not a CAG cell for the PLMN. If there exists an entry for the presented PLMN in the "CAG information
list" and the entry includes an "indication that the MS is only allowed to access 5GS via CAG cells", the MS
may indicate to the user that the MS is only allowed to access the PLMN via CAG cells.
System Simulator:
- NR Cell 2 and NR Cell 4 are CAG cells.
- System information combination NR-2 as defined in TS 38.508[4] clause 4.4.3.1.2 is used for NR Cell 1, NR
Cell 2 and NR Cell 4.
in TS 36.523-1 [13] table 6.0.1-1.
Table 6.5.2.1.3.1–1: PLMN and CAG identifiers

NR Cell PLMN name CAG IDs
1 PLMN 1 -
2 PLMN 1 1
4 PLMN 2 2
UE:
None.
Preamble:
- The UE is registered on NR Cell 1 using the procedure described in TS 38.508-1 [4] clause 4.5.2.2 except that
the REGISTRATION ACCEPT message includes CAG information list with CAG-ID 1.
- The UE is set to Manual PLMN selection mode before it is in state Switched OFF (State 0N-B) as per TS
38.508-1 [4] Table 4.4A.2-0.
Table 6.5.2.1.3.2-1 for FR1 and Table 6.5.2.1.3.2-2 for FR2 illustrate the downlink power to be applied for the cells at
various time instants of the test execution. The configuration T0 indicates the initial conditions for preamble.
Configurations marked "T1", "T2" and "T3"are applied at the points indicated in the Main behaviour description in
Table 6.5.2.1.3.2-3.
ETSI
T0 SS/PBCH dBm/SCS -88 "Off" "Off" Power level "Off" is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3
T1 SS/PBCH dBm/SCS "Off" -88 "Off" Power level "Off" is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3
T2 SS/PBCH dBm/SCS "Off" "Off" -88 Power level "Off" is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3
T3 SS/PBCH dBm/SCS -88 -88 "Off" Power level "Off" is defined in TS
SSS EPRE 38.508-1 [4] Table 6.2.2.1-3
SSS EPRE
SSS EPRE
SSS EPRE
SSS EPRE
ETSI

U-S Message
1 The SS changes cell power levels according to - - - -
row "T1" in Table 6.5.2.1.3.2-1 for FR1 and
Table 6.5.2.1.3.2-2 for FR2.
3 The UE is made to perform manual CAG - - - -
selection and selects NR Cell 2.
5- Steps 3-20a1 of Table 4.5.2.2-2 of the generic - - - -
22 procedure in TS 38.508-1 [4] are performed on
NR Cell 2.
Note: The UE performs registration procedure
and the RRC connection is released.
Table 6.5.2.1.3.2-2 for FR2.
24 The UE is made to perform manual CAG - - - -
selection and select NR Cell 4.
Note: The UE starts registration.
message including CAG information list with ACCEPT
PLMN ID 1 and CAG only indication.
Note: The UE completes registration and the
Table 6.5.2.1.3.2-2 for FR2.
45 The UE is made to perform manual PLMN - - - -
46 Check: Does the UE send a --> NR RRC: RRCSetupRequest 3 F
47 The UE is made to perform manual CAG - -
49- Steps 3-20a1 of Table 4.5.2.2-2 of the generic - - - -
66 procedure in TS 38.508-1 [4] are performed on
NR Cell 2.
Note: The UE completes registration and the
Table 6.5.2.1.3.3-1: REGISTRATION REQUEST (Preamble)

5GS registration type '0000 0001'B Initial registration
5GMM capability
CAG ‘1’B CAG supported
ETSI
Table 6.5.2.1.3.3-2: REGISTRATION ACCEPT (Preamble)

CAG information list MCC : 001; MNC :
01; CAG only : 0;
CAG-ID 1 : 1
Length of CAG information list contents ‘0000 1001’B
Entry 1
Length of entry contents ‘0000 1000’B
MCC MCC of NR Cell 2 See TS 38.508-1 [4]
Table 4.4.2-3
MNC MNC of NR Cell 2 See TS 38.508-1 [4]
Table 4.4.2-3
CAG only ‘0’B
CAG_ID 1 1 CAG ID is coded as
a 32 bit BITSTRING
Table 6.5.2.1.3.3-3: REGISTRATION ACCEPT (Step 37, Table 6.5.2.1.3.2-3)

01; CAG only : 1;
CAG-ID 1 : 1
Entry 1
MCC MCC of NR Cell 2 See TS 38.508-1 [4]
Table 4.4.2-3
MNC MNC of NR Cell 2 See TS 38.508-1 [4]
Table 4.4.2-3
CAG only ‘1’B
CAG_ID 1 1 CAG ID is coded as
a 32 bit BITSTRING
6.5.2.2 CAG Selection in Automatic Mode
(1)
with { UE in Automatic network selection mode and provisioned with an empty "CAG information list” }
ensure that {
when { UE is switched on or returned to coverage, and a cell which is not a CAG cell becomes
available}
then { UE selects the cell }
}
(2)
with { UE in Automatic network selection mode provisioned with a "CAG information list” }
ensure that {
when { UE is switched on or returned to coverage, and a CAG cell with a CAG-ID present in the
"Allowed CAG list" becomes available}
then { UE selects the CAG cell }
}
(3)
with { UE in Automatic network selection mode provisioned with a "CAG information list” }
ensure that {
ETSI
when { UE is switched on and a cell which is not a CAG cell becomes available, and there is an
entry with the PLMN ID of the PLMN in the "CAG information list" but the "indication that the MS is
only allowed to access 5GS via CAG cells" is not included in the entry}
then { UE selects the cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 3.8, and
[TS 23.122, clause 3.8]
The MS may support CAG.
If the MS supports CAG, the MS can be provisioned with a "CAG information list", consisting of zero or more entries,
each containing:
a) a PLMN ID;
b) an "Allowed CAG list". The "Allowed CAG list" contains zero or more CAG-IDs; and
c) an optional "indication that the MS is only allowed to access 5GS via CAG cells".
The "CAG information list" is stored in the ME.
NOTE: When the UE is registering or registered to a PLMN other than the HPLMN or EHPLMN, then the
HPLMN will send a "CAG information list" consisting of CAG subscription information related to the
serving PLMN only. When the UE is registering or registered to the HPLMN or EHPLMN then the
HPLMN or EHPLMN can send CAG subscription information related to any PLMN in the "CAG
information list".
If the MS supports CAG and a PLMN is selected as described in subclause 4.4.3.1.1, the automatic CAG selection is
performed as part of subclause 4.4.3.1.1.
If the MS supports CAG and a PLMN is selected as described in subclause 4.4.3.1.2, the manual CAG selection is
performed as part of subclause 4.4.3.1.2.
The NAS shall provide the AS with a "CAG information list", if available. If the contents of the "CAG information list"
have changed, the NAS shall provide an updated "CAG information list" to the AS.
[TS 23.122, clause 4.4.3.1.1]
Technology" data file in the SIM (in priority order) or stored in the ME (in priority order);
m) In i to v, if the MS supports CAG and:
1) is provisioned with a non-empty "CAG information list", the MS shall consider a PLMN indicated by an NG-
RAN cell only if:
ETSI
A) the cell is a CAG cell and broadcasts a CAG-ID for the PLMN such that there exists an entry with the
PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is included in the "Allowed CAG
list" of the entry; or
B) the cell is not a CAG cell and:
- there is no entry with the PLMN ID of the PLMN in the "CAG information list"; or
- there exists an entry with the PLMN ID of the PLMN in the "CAG information list" but the
"indication that the MS is only allowed to access 5GS via CAG cells" is not included in the entry; or
2) is provisioned with an empty "CAG information list" or is not provisioned with a "CAG information list", the
MS shall consider a PLMN indicated by an NG-RAN cell only if the cell is not a CAG cell.
n) In i to v, if the MS only supports control plane CIoT 5GS optimization (see 3GPP TS 23.501 [62]) and the MS
camps on an E-UTRA cell connected to 5GCN, which is not NB-IoT cell (see 3GPP TS 36.304 [43],
3GPP TS 36.331 [22]), the MS shall not consider PLMNs which do not advertise support of 5GS services with
control plane CIoT 5GS optimization.
o) In i to v, if the MS supports CIoT 5GS optimizations, the MS shall not consider the PLMN/access technology
combinations for which the MS preferred CIoT network behaviour is not advertised as supported by the
PLMN/access technology combination (see 3GPP TS 24.501 [64]).
NOTE 7: As an implementation option, the MS supporting CIoT 5GS optimizations that was not able to select any
PLMN according to o) can perform a second iteration of i to v with no restriction.
p) In iii, the MS shall use the PLMN/access technology combination in the "Operator Controlled PLMN Selector
with Access Technology" stored in the ME, if the last received steering of roaming information contains the "list
of preferred PLMN/access technology combinations"(see annex C) and is stored in the ME. Otherwise, the MS
shall use the "Operator Controlled PLMN Selector with Access Technology" list retrieved from the SIM.
If registration cannot be achieved because no PLMNs are available and allowable, and the MS does not support access
to RLOS, the MS indicates "no service" to the user, waits until a new PLMN is available and allowable and then repeats
the procedure.
"forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of
service", or "CAG information list" prevented a registration attempt, the MS selects the first such PLMN again and
enters a limited service state.
System Simulator:
- NR Cell 1, NR Cell 2, NR Cell 4 and NR Cell 11.
- NR Cell 2 and NR Cell 4 are CAG cells.
- System information combination NR-2 as defined in TS 38.508[4] clause 4.4.3.1.2 is used for NR Cell 1, NR
Cell 2 and NR Cell 4.
in TS 36.523-1 [13] table 6.0.1-1.
ETSI

NR Cell PLMN name CAG IDs
2 PLMN2 1
4 PLMN3 2
UE:
- There is no “CAG information list” provisioned in the UE.
Preamble:
- The UE is in state Switched OFF (state 0-A).
Table 6.5.2.2.3.2-1 for FR1 and 6.5.2.2.3.2-2 for FR2 illustrate the downlink power levels to be applied for the cells at
columns marked "T1", "T2" and "T3" are to be applied subsequently in the Main behaviour. The exact instants on
which these values shall be applied are described in the texts in this clause. Cell powers are chosen for a serving cell
and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.

1 2 4 11
T0 SS/PBCH dBm/SCS -88 "Off" -88 "Off"
SSS EPRE
T1 SS/PBCH dBm/SCS "Off" "Off" -88 "Off"
SSS EPRE
T2 SS/PBCH dBm/SCS "Off" -88 -88 "Off"
SSS EPRE
T3 SS/PBCH dBm/SCS "Off" "Off" "Off" -88
SSS EPRE

1 2 4 11
T0 SS/PBCH dBm/SCS FFS "Off" FFS "Off"
SSS EPRE
T1 SS/PBCH dBm/SCS "Off" "Off" FFS "Off"
SSS EPRE
T2 SS/PBCH dBm/SCS "Off" FFS FFS "Off"
SSS EPRE
T3 SS/PBCH dBm/SCS "Off" "Off" "Off" FFS
SSS EPRE
ETSI

U-S Message
NOTE: The UE starts registration.
message containing the CAG information list ACCEPT
with the CAG ID of NR Cell 2
20a described in TS 38.508-1 [4] subclause 4.5.2.2
NOTE: The UE completes registration and the
6.5.2.2.3.2-2 for FR2
24 Check: Does the UE send a --> NR RRC: RRCSetupRequest 2 F
next 60 s?
6.5.2.2.3.2-2 for FR2
NOTE: The UE completes registration and the
6.5.2.2.3.2-2 for FR2
ETSI
Table 6.5.2.2.3.3-1: Message REGISTRATION ACCEPT (step 14, Table 6.5.2.2.3.2-3)
Derivation path: TS 38.508-1 [4], table 4.7.1-7

11; CAG only :
0;CAG-ID 1 : 1
Entry 1
MCC MCC of NR Cell 2 See TS 38.508-1
[4] Table 4.4.2-3
MNC MNC of NR Cell 2 See TS 38.508-1
[4] Table 4.4.2-3
CAG only ‘0’B
CAG_ID 1 1 CAG ID is coded
as a 32 bit
BITSTRING
ETSI
7 Layer 2
7.1 NR Layer 2
7.1.0 Common test case specific values for Layer 2
For all layer 2 test cases, default values for periodicBSR-Timer, retxBSR-Timer and phr-Config shall be taken
according to the table 7.1.0-1 unless test case specific values are given in the test case.
Table 7.1.0-1: MAC-CellGroupConfig
Derivation Path: TS 38.308 [6], clause Table 4.6.3-49

MAC-CellGroupConfig ::= SEQUENCE {
bsr-Config SEQUENCE {
periodicBSR-Timer infinity
retxBSR-Timer sf10240
}
phr-Config CHOICE {
release NULL
}
}
7.1.1 MAC
7.1.1.0 Default Pre-Test Conditions for all MAC test cases

The following pre-test conditions shall be applied in all MAC test cases until the test case explicitly over writes these
conditions
System Simulator:
- The SS configures the test environment in accordance to the execution conditions in Table 7.1.1.0-1.
UE:
- None
Preamble:
- The SS performs the generic procedure in [4] to get UE in state RRC_CONNECTED in accordance to the
execution conditions in Table 7.1.1.0-2 and using the message condition UE TEST LOOP MODE A to return
one PDCP SDU per DL PDCP SDU.
ETSI
Table 7.1.1.0-1: Test environment

Execution Condition Cell configuration System Information
Combination
IF pc_NG_RAN_NR NR Cell 1 NR: System information
Combination NR-1
ELSE IF pc_EN_DC E-UTRA Cell 1 is PCell, EUTRA: System information

NR Cell 1 is PSCell Combination 1
NR: N/A
ELSE IF pc_NGEN_DC NG-RAN E-UTRA Cell 1 is PCell, EUTRA: System information
NR: N/A
Table 7.1.1.0-2: Preamble parameters

Execution Condition
Multi-PDN / Multi- Generic Procedure Parameters Primary DRB used for
PDU Sessions Data testing
Condition
IF pc_NG_RAN_NR FALSE Connectivity(NR), Default DRB of the first
Test loop function(On) PDU session on NR Cell
One DRB
TRUE Connectivity(NR),
Test loop function(On)
N DRBs (N ≥ 2)
ELSE IF pc_EN_DC FALSE Connectivity(EN-DC), SN Terminated SCG
DC bearer(One MN Terminated MCG bearer unless explicitly
bearer and One SN terminated SCG specified in test case
bearer),
TRUE Connectivity(EN-DC),
DC bearer(Two MN Terminated MCG
bearer and One SN terminated SCG
bearer),
ELSE IF pc_NGEN_DC FALSE Connectivity(NGEN-DC), SN Terminated SCG
bearer),
bearer),
Table 7.1.1.0-3: Message conditions

Execution Message condition exceptions
Condition
IF Message with condition AM is used for step 7 in 4.5.4.2
pc_NG_RAN_NR according to [4]
ELSE IF Message condition MCG_and_SCG with condition AM
pc_EN_DC is used for step 7 in 4.5.4.2 according to [4]
pc_NGEN_DC is used for step 7 in 4.5.4.2 according to [4]
ETSI
Table 7.1.1.0-4: SDAP Configuration Settings for pc_NG_RAN_NR

Parameter Value DRB1 Value DRB2 Value DRB3
default DRB true false false
mappedQoS-FlowsToAdd QFI 1 in Table 4.8.2.3- QFI 2 in Table QFI 3 in Table
1 according to 4.8.2.3-2 4.8.2.3-3
TS38.508-1 according to according to
TS38.508-1 TS38.508-1
7.1.1.1 Random Access Procedures
7.1.1.1.1 Correct selection of RACH parameters / Random access preamble and PRACH
resource explicitly signalled to the UE by RRC / contention free random access
procedure
7.1.1.1.1.1 Test Purpose (TP)
(1)
with { UE in RRC_Connected }
ensure that {
when { SS sends an RRCReconfiguration message including RACH-ConfigDedicated information element }
then { UE sends a prach preamble given in the RACH-ConfigDedicated on the target cell }
}
(2)
with { UE in RRC_Connected state after transmission of a PRACH preamble on NR SpCell received in
RACH-ConfigDedicated on the target cell }
ensure that {
when { UE does not receive a matching Random Access response in ra-ResponseWindowSize (hence
considers RACH attempt as failed) and PREAMBLE_TRANSMISSION_COUNTER is less than PREAMBLE_TRANS_MAX
}
then { UE retransmits a PRACH preamble received in RACH-ConfigDedicated on the target cell }
}
7.1.1.1.1.2 Conformance requirements
References: The conformance requirements covered in the present test case are specified in: TS 38.321, clauses 5.1.2,
5.1.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.1.2]
The MAC entity shall:
1> else if the ra-PreambleIndex has been explicitly provided by PDCCH; and
1> if the ra-PreambleIndex is not 0b000000:
2> set the PREAMBLE_INDEX to the signalled ra-PreambleIndex;
2> select the SSB signalled by PDCCH.
1> else if the contention-free Random Access Resources associated with SSBs have been explicitly provided in
rach-ConfigDedicated and at least one SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated
SSBs is available:
2> select an SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated SSBs;
2> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected SSB.
ETSI
1> else if an SSB is selected above:
2> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected
SSB permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured or indicated by
PDCCH (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the
consecutive PRACH occasions according to clause 8.1 of TS 38.213 [6], corresponding to the selected SSB;
the MAC entity may take into account the possible occurrence of measurement gaps when determining the
next available PRACH occasion corresponding to the selected SSB).
1> else if a CSI-RS is selected above:
2> if there is no contention-free Random Access Resource associated with the selected CSI-RS:
3> determine the next available PRACH occasion from the PRACH occasions, permitted by the restrictions
given by the ra-ssb-OccasionMaskIndex if configured, corresponding to the SSB in candidateBeamRSList
which is quasi-collocated with the selected CSI-RS as specified in TS 38.214 [7] (the MAC entity shall
select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions
according to clause 8.1 of TS 38.213 [6], corresponding to the SSB which is quasi-collocated with the
selected CSI-RS; the MAC entity may take into account the possible occurrence of measurement gaps
when determining the next available PRACH occasion corresponding to the SSB which is quasi-
collocated with the selected CSI-RS).
2> else:
3> determine the next available PRACH occasion from the PRACH occasions in ra-OccasionList
corresponding to the selected CSI-RS (the MAC entity shall select a PRACH occasion randomly with
equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers,
corresponding to the selected CSI-RS; the MAC entity may take into account the possible occurrence of
measurement gaps when determining the next available PRACH occasion corresponding to the selected
CSI-RS).
1> perform the Random Access Preamble transmission procedure (see clause 5.1.3).
NOTE: When the UE determines if there is an SSB with SS-RSRP above rsrp-ThresholdSSB or a CSI-RS with CSI-
RSRP above rsrp-ThresholdCSI-RS, the UE uses the latest unfiltered L1-RSRP measurement.
[TS 38.321, clause 5.1.4]
Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the
MAC entity shall:
1> if the contention-free Random Access Preamble for beam failure recovery request was transmitted by the MAC
entity:
2> start the ra-ResponseWindow configured in BeamFailureRecoveryConfig at the first PDCCH occasion as
specified in TS 38.213 [6] from the end of the Random Access Preamble transmission;
2> monitor for a PDCCH transmission on the search space indicated by recoverySearchSpaceId of the SpCell
identified by the C-RNTI while ra-ResponseWindow is running.
1> else:
2> start the ra-ResponseWindow configured in RACH-ConfigCommon at the first PDCCH occasion as specified
in TS 38.213 [6] from the end of the Random Access Preamble transmission;
2> monitor the PDCCH of the SpCell for Random Access Response(s) identified by the RA-RNTI while the ra-
ResponseWindow is running.
1> if notification of a reception of a PDCCH transmission on the search space indicated by recoverySearchSpaceId
is received from lower layers on the Serving Cell where the preamble was transmitted; and
1> if PDCCH transmission is addressed to the C-RNTI; and
entity:
ETSI
2> consider the Random Access procedure successfully completed.
1> else if a downlink assignment has been received on the PDCCH for the RA-RNTI and the received TB is
successfully decoded:
2> if the Random Access Response contains a MAC subPDU with Backoff Indicator:
3> set the PREAMBLE_BACKOFF to value of the BI field of the MAC subPDU using Table 7.2-1,
multiplied with SCALING_FACTOR_BI.
2> else:
3> set the PREAMBLE_BACKOFF to 0 ms.
2> if the Random Access Response contains a MAC subPDU with Random Access Preamble identifier
corresponding to the transmitted PREAMBLE_INDEX (see clause 5.1.3):
3> consider this Random Access Response reception successful.
2> if the Random Access Response reception is considered successful:
3> if the Random Access Response includes a MAC subPDU with RAPID only:
4> consider this Random Access procedure successfully completed;
4> indicate the reception of an acknowledgement for SI request to upper layers.
3> else:
4> apply the following actions for the Serving Cell where the Random Access Preamble was transmitted:
5> process the received Timing Advance Command (see clause 5.2);
5> indicate the preambleReceivedTargetPower and the amount of power ramping applied to the latest
Random Access Preamble transmission to lower layers (i.e.
(PREAMBLE_POWER_RAMPING_COUNTER – 1) × PREAMBLE_POWER_RAMPING_STEP);
5> if the Random Access procedure for an SCell is performed on uplink carrier where pusch-Config is
not configured:
6> ignore the received UL grant.
5> else:
6> process the received UL grant value and indicate it to the lower layers.
4> if the Random Access Preamble was not selected by the MAC entity among the contention-based
Random Access Preamble(s):
4> else:
5> set the TEMPORARY_C-RNTI to the value received in the Random Access Response;
5> if this is the first successfully received Random Access Response within this Random Access
procedure:
6> if the transmission is not being made for the CCCH logical channel:
7> indicate to the Multiplexing and assembly entity to include a C-RNTI MAC CE in the
subsequent uplink transmission.
6> obtain the MAC PDU to transmit from the Multiplexing and assembly entity and store it in the
Msg3 buffer.
ETSI
NOTE: If within a Random Access procedure, an uplink grant provided in the Random Access Response for the
same group of contention-based Random Access Preambles has a different size than the first uplink grant
allocated during that Random Access procedure, the UE behaviour is not defined.
1> if ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if a PDCCH transmission on the

search space indicated by recoverySearchSpaceId addressed to the C-RNTI has not been received on the Serving
Cell where the preamble was transmitted; or
1> if ra-ResponseWindow configured in RACH-ConfigCommon expires, and if the Random Access Response
containing Random Access Preamble identifiers that matches the transmitted PREAMBLE_INDEX has not been
received:
2> consider the Random Access Response reception not successful;
2> increment PREAMBLE_TRANSMISSION_COUNTER by 1;
2> if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:
3> if the Random Access Preamble is transmitted on the SpCell:
4> indicate a Random Access problem to upper layers;
4> if this Random Access procedure was triggered for SI request:
5> consider the Random Access procedure unsuccessfully completed.
3> else if the Random Access Preamble is transmitted on an SCell:
2> if the Random Access procedure is not completed:
3> select a random backoff time according to a uniform distribution between 0 and the
PREAMBLE_BACKOFF;
3> if the criteria (as defined in clause 5.1.2) to select contention-free Random Access Resources is met
during the backoff time:
4> perform the Random Access Resource selection procedure (see clause 5.1.2);
3> else:
4> perform the Random Access Resource selection procedure (see clause 5.1.2) after the backoff time.
The MAC entity may stop ra-ResponseWindow (and hence monitoring for Random Access Response(s)) after
successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the
transmitted PREAMBLE_INDEX.
HARQ operation is not applicable to the Random Access Response reception.
7.1.1.1.1.3 Test description
7.1.1.1.1.3.1 Pre-test conditions
Same Pre-test conditions as in clause 7.1.1.0 except the following:
- 2 NR cells (NR Cell 1 and NR Cell 2) are configured.
- Test loop function(Off)
ETSI
7.1.1.1.1.3.2 Test procedure sequence
Table 7.1.1.1.1.3.2-1: Main behaviour

U-S Message
1 The SS transmits an RRCReconfiguration <-- RRCReconfiguration - -
message to handover NR Cell 1 to target NR
Cell 2, including RACH-ConfigDedicated
information element
(Note 1, Note 3)
2 Void
3 Check: Does the UE transmit Preamble on --> (PRACH Preamble) 1 P
PRACH corresponding to ra-PreambleIndex in
step 1 on NR Cell2?
4 Check: Does the UE re-transmits Preamble on --> (PRACH Preamble) 2 P
step 1 on NR Cell2?
5 The SS transmits Random Access Response <-- Random Access Response - -
on NR cell 2, with RAPID corresponding to ra-
PreambleIndex in step 1
6 Check: Does the UE transmit an --> RRCReconfigurationComplete - -
RRCReconfigurationComplete message?
(Note 2)
Note 1: For EN-DC the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration 36.508 [7],
Table 4.6.1-8 using condition EN-DC_PSCell_HO AND RBConfig_NoKeyChange.
Note 2: For EN-DC the NR RRCReconfigurationComplete message is contained in
RRCConnectionReconfigurationComplete.
Note 3: For FR1,PRACH preamble format 0 as per TS 38.211[24] Table 6.3.3.1-1 is configured (real network
deployment).
7.1.1.1.1.3.3 Specific message contents
Table 7.1.1.1.1.3.3-1: Void
Table 7.1.1.1.1.3.3-2: RRCReconfiguration for EN-DC (step 1, Table 7.1.1.1.1.3.2-1)
Derivation Path: 38.508-1 [4], Table 4.6.1-13 with condition EN-DC_HO.

RRCReconfiguration ::= SEQUENCE {
rrcReconfiguration ::= SEQUENCE {
secondaryCellGroup CellGroupConfig
}
}
}
ETSI
Table 7.1.1.1.1.3.3-2A: RRCReconfiguration for NR/5GC (step 1, Table 7.1.1.1.1.3.2-1)

radioBearerConfig RadioBearerConfig as n set to the default NR
per TS 38.508-1[4] Table DRB of the first
4.6.3-132 with conditions PDU session
DRBn and
Recover_PDCP
masterCellGroup CellGroupConfig
}
}
}
}
Table 7.1.1.1.1.3.3-3: CellGroupConfig for EN-DC (Table 7.1.1.1.1.3.3-2)
Derivation Path: 38.508-1 [4], Table 4.6.3-19 with condition PSCell_change

spCellConfig SEQUENCE {
spCellConfigCommon ServingCellConfigComm
on
reconfigurationWithSync SEQUENCE {
rach-ConfigDedicated CHOICE {
uplink RACH-ConfigDedicated
}
newUE-Identity UE identity different from
NR cell 1 UE identity
}
}
}
Table 7.1.1.1.1.3.3-3A: CellGroupConfig for NR/5GC (Table 7.1.1.1.1.3.3-2A)
Derivation Path: 38.508-1 [4], Table 4.6.3-19 with condition PCell_change

on
}
newUE-Identity UE identity different from
NR cell 1 UE identity
}
}
}
ETSI
Table 7.1.1.1.1.3.3-4: RACH-ConfigDedicated (Table 7.1.1.1.1.3.3-3 and Table 7.1.1.1.1.3.3-3A)

RACH-ConfigDedicated::= SEQUENCE {
cfra SEQUENCE {
occasions SEQUENCE {
rach-ConfigGeneric RACH-ConfigGeneric FR1,
PRACH
Preamble
format 0
used
}
resources CHOICE {
ssb SEQUENCE {
ssb-ResourceList SEQUENCE (SIZE(1..maxRA- 1 entry
SSB-Resources)) OF CFRA-SSB-Resource {
CFRA-SSB-Resource[1] SEQUENCE { entry 1
ssb 0
ra-PreambleIndex 52 Randomly
selected
}
}
}
}
}
Table 7.1.1.1.1.3.3-5: RACH-ConfigGeneric (Table 7.1.1.1.1.3.3-4)

RACH-ConfigDedicated::= SEQUENCE {
prach-ConfigurationIndex 14 FR1
149 FR2
zeroCorrelationZoneConfig 12 FR1
15 FR2
}
Table 7.1.1.1.1.3.3-6: ServingCellConfigCommon (Table 7.1.1.1.1.3.3-3 and Table 7.1.1.1.1.3.3-3A)

ServingCellConfigCommon ::= SEQUENCE {
uplinkConfigCommon SEQUENCE {
initialUplinkBWP BWP-UplinkCommon
}
tdd-UL-DL-ConfigurationCommon TDD-UL-DL-
ConfigCommon
}
Table 7.1.1.1.1.3.3-7: BWP-UplinkCommon (Table 7.1.1.1.1.3.3-6)

BWP-UplinkCommon ::= SEQUENCE {
rach-ConfigCommon CHOICE {
setup RACH-ConfigCommon
}
}
ETSI
Table 7.1.1.1.1.3.3-8: RACH-ConfigCommon (Table 7.1.1.1.1.3.3-7)

RACH-ConfigCommon::= SEQUENCE {
rach-ConfigGeneric RACH-ConfigGeneric
ssb_perRACH_OccasionAndCB_PreamblesPerSSB
CHOICE {
one n36
}
prach-RootSequenceIndex CHOICE {
l139 Set according to table
4.4.2-2 in TS 38.508-1 [4]
for the NR Cell..
l839 Set according to table PRACH Preamble FR1,
4.4.2-2 in TS 38.508-1 [4] format 0 used
for the NR Cell.
}
}
Table 7.1.1.1.1.3.3-9: TDD-UL-DL-ConfigCommon (Table 7.1.1.1.1.3.3-6)

TDD-UL-DL-ConfigCommon ::= SEQUENCE {
referenceSubcarrierSpacing SubcarrierSpacing
pattern1 SEQUENCE {
dl-UL-TransmissionPeriodicity ms5 FR1
ms0p625 FR2
nrofDownlinkSlots 3 FR1
3 FR2
nrofDownlinkSymbols 6 FR1
10 FR2
nrofUplinkSlots 2 FR1
1 FR2
nrofUplinkSymbols 4 FR1
2 FR2
dl-UL-TransmissionPeriodicity-v1530 ms3 FR1
}
pattern2 Not present
pattern2 SEQUENCE { FR1
dl-UL-TransmissionPeriodicity ms2
nrofDownlinkSlots 4
nrofDownlinkSymbols 0
nrofUplinkSlots 0
nrofUplinkSymbols 0
}
}
7.1.1.1.1a Correct selection of RACH parameters / Random access preamble and PRACH
resource explicitly signalled to the UE by PDCCH Order / contention free random
access procedure
7.1.1.1.1a.1 Test Purpose (TP)
(1)
ensure that {
when { PDCCH control command is received in NR SpCell providing Random Access Preamble }
then { UE sends a PRACH preamble given in the PDCCH Order in NR SpCell }
}
ETSI
(2)
with { UE in RRC_Connected state after transmission of a PRACH preamble on NR SpCell received in
PDCCH control command on NR SpCell }
ensure that {
when { UE does not receive a matching Random Access response in ra-ResponseWindowSize (hence
considers RACH attempt as failed) and PREAMBLE_TRANSMISSION_COUNTER is less than PREAMBLE_TRANS_MAX
}
then { UE retransmits a PRACH preamble received in PDCCH control command on NR SpCell }
}
7.1.1.1.1a.2 Conformance requirements
5.1.4 and TS 38.212 clause 7.3.1.2.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.1.2]
1> else if the ra-PreambleIndex has been explicitly provided by either PDCCH or RRC; and
1> if the ra-PreambleIndex is not 0b000000; and
1> if contention-free Random Access Resource associated with SSBs or CSI-RS have not been explicitly provided
by RRC:
2> set the PREAMBLE_INDEX to the signalled ra-PreambleIndex.
1> if an SSB is selected above and an association between PRACH occasions and SSBs is configured:
SSB permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured (the MAC entity
may take into account the possible occurrence of measurement gaps when determining the next available
PRACH occasion corresponding to the selected SSB).
1> else if a CSI-RS is selected above and an association between PRACH occasions and CSI-RSs is configured:
2> determine the next available PRACH occasion from the PRACH occasions in ra-OccasionList corresponding
to the selected CSI-RS (the MAC entity may take into account the possible occurrence of measurement gaps
when determining the next available PRACH occasion corresponding to the selected CSI-RS).
1> else:
2> determine the next available PRACH occasion (the MAC entity may take into account the possible
occurrence of measurement gaps when determining the next available PRACH occasion).
1> perform the Random Access Preamble transmission procedure (see clause 5.1.3).
[TS 38.321, clause 5.1.4]
MAC entity shall:
...
1> else:
ETSI
1> if notification of a reception of a PDCCH transmission is received from lower layers; and
...
2> if the Random Access Response contains a Backoff Indicator subheader:
3> set the PREAMBLE_BACKOFF to value of the BI field of the Backoff Indicator subheader using Table
7.2-1.
2> else:
2> if the Random Access Response contains a Random Access Preamble identifier corresponding to the
transmitted PREAMBLE_INDEX (see subclause 5.1.3):
3> if the Random Access Response includes RAPID only:
4> indicate the reception of an acknowledgement for the SI request to upper layers.
3> else:
5> process the received Timing Advance Command (see subclause 5.2);
(PREAMBLE_POWER_RAMPING_COUNTER – 1) × preamblePowerRampingStep);
5> if the Serving Cell for the Random Access procedure is SRS-only SCell:
5> else:
...
received; or:
1> if ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if the PDCCH addressed to the
C-RNTI has not been received:
2> if PREAMBLE_TRANSMISSION_COUNTER = preambleTxMax + 1:
ETSI
4> indicate a Random Access problem to upper layers.
3> else if the Random Access Preamble is transmitted on a SCell:
2> if in this Random Access procedure, the Random Access Preamble was selected by MAC among the
contention-based Random Access Preambles:
PREAMBLE_BACKOFF;
3> delay the subsequent Random Access Preamble transmission by the backoff time.
2> perform the Random Access Resource selection procedure (see subclause 5.1.2).
HARQ operation is not applicable to the Random Access Response transmission.
[TS 38.212, 7.3.1.2.1]
If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field
are of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining
fields set as follows:
- Random Access Preamble index – 6 bits according to ra-PreambleIndex in Subclause 5.1.2 of [8, TS38.321]
- UL/SUL indicator – 1 bit. If the value of the "Random Access Preamble index" is not all zeros and if the UE is
configured with SUL in the cell, this field indicates which UL carrier in the cell to transmit the PRACH
according to Table 7.3.1.1.1-1; otherwise, this field is reserved
- SS/PBCH index – 6 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates
the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this
field is reserved.
- PRACH Mask index – 4 bits. If the value of the "Random Access Preamble index" is not all zeros, this field
indicates the RACH occasion associated with the SS/PBCH indicated by "SS/PBCH index" for the PRACH
transmission, according to Subclause 5.1.1 of [8, TS38.321]; otherwise, this field is reserved
- Reserved bits – 10 bits
7.1.1.1.1a.3 Test description
7.1.1.1.1a.3.1 Pre-test conditions
Same Pre-test conditions as in clause 7.1.1.0 except that Test loop function(Off).
ETSI
7.1.1.1.1a.3.2 Test procedure sequence
Table 7.1.1.1.1a.3.2-1: Main behaviour

U-S Message
0A SS transmits an RRCReconfiguration message <-- RRCReconfiguration - -
to configure specific parameters. Note 1, Note
3
0B The UE transmits --> RRCReconfigurationComplete - -
RRCReconfigurationComplete message. Note
2
1 The SS transmits a PDCCH order providing <-- (PDCCH Order) - -
Random Access Preamble ID 37 on NR
SpCell.
step 1?
step 1?
step 1?
step 1?
on NR SpCell, with RAPID corresponding to
ra-PreambleIndex in step 1
Note 1: for EN-DC the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration.
Note 2: for EN-DC the NR RRCReconfigurationComplete message is contained in
Note 3: For FR1, PRACH preamble format 0 as per TS 38.211[24] Table 6.3.3.1-1 is configured in order to provide
coverage for PRACH preamble format 0 testing
7.1.1.1.1a.3.3 Specific message contents
Table 7.1.1.1.1a.3.3-1: RRCReconfiguration (step 0A, Table7.1.1.1.1a.3.2-1)

TS 38.508-1 [4], 2
secondaryCellGroup CellGroupConfig OCTET STRING EN-DC
(CONTAINING
CellGroupConfig)
nonCriticalExtension SEQUENCE { NR
masterCellGroup CellGroupConfig OCTET STRING
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI
Table 7.1.1.1.1a.3.3-2: CellGroupConfig (Table 7.1.1.1.1a.3.3-1)

on
newUE-Identity RNTI-Value
t304 ms2000
rach-ConfigDedicated Not Present
}
Table 7.1.1.1.1a.3.3-3: ServingCellConfigCommon (Table 7.1.1.1.1a.3.3-2)

}
ConfigCommon
}
Table 7.1.1.1.1a.3.3-4: BWP-UplinkCommon (Table 7.1.1.1.1a.3.3-3)

}
}
Table 7.1.1.1.1a.3.3-5: RACH-ConfigCommon (Table 7.1.1.1.1a.3.3-4)

ssb_perRACH_OccasionAndCB_PreamblesPerSSB
CHOICE {
one n36
}
l139 Set according to table
4.4.2-2 in TS 38.508-1 [4]
for the NR Cell
l839 Set according to table PRACH Preamble FR1,
4.4.2-2 in TS 38.508-1 [4] format 0 used
for the NR Cell.
}
}
ETSI
Table 7.1.1.1.1a.3.3-6: RACH-ConfigGeneric (Table 7.1.1.1.1a.3.3-5)

RACH-ConfigGeneric ::= SEQUENCE {
preambleTransMax n4
prach-ConfigurationIndex 14 FR1
149 FR2
zeroCorrelationZoneConfig 12 FR1
15 FR2
}
Table 7.1.1.1.1a.3.3-7: TDD-UL-DL-ConfigCommon (Table 7.1.1.1.1a.3.3-3)

pattern1 SEQUENCE {
ms0p625 FR2
nrofDownlinkSlots 3 FR1_30kHz
1 FR1_15kHz
3 FR2
10 FR2
nrofUplinkSlots 2 FR1_30kHz
1 FR1_15kHz
1 FR2
nrofUplinkSymbols 4
2 FR2
}
pattern2 Not present
pattern2 SEQUENCE { FR1
dl-UL-TransmissionPeriodicity ms2
nrofDownlinkSlots 4 FR1_30kHz
2 FR1_15kHz
nrofDownlinkSymbols 0
nrofUplinkSlots 0
nrofUplinkSymbols 0
}
}
Table 7.1.1.1.1a.3.3-8: ServingCellConfig (Table 7.1.1.1.1a.3.3-2)

uplinkConfig SEQUENCE {
initialUplinkBWP BWP-UplinkDedicated
}
}
ETSI
Table 7.1.1.1.1a.3.3-9: BWP-UplinkDedicated (Table 7.1.1.1.1a.3.3-8)

BWP-UplinkDedicated ::= SEQUENCE {
pucch-Config CHOICE {
setup PUCCH-Config
}
}
Table 7.1.1.1.1a.3.3-10: PUCCH-Config (Table 7.1.1.1.1a.3.3-9)

PUCCH-Config ::= SEQUENCE {
schedulingRequestResourceToAddModList 1 entry
SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF
SchedulingRequestResourceConfig {
SchedulingRequestResourceConfig SchedulingRequestReso entry 1
urceConfig
}
}
Table 7.1.1.1.1a.3.3-11: SchedulingRequestResourceConfig (Table 7.1.1.1.1a.3.3-10)

SchedulingRequestResourceConfig ::= SEQUENCE {
periodicityAndOffset CHOICE {
sl10 2 With SCS = SCS_15kHz
kHz15 results in
repetition every 10
ms
kHz30 results in
repetition every 10
ms
sl80 4 With SCS = SCS_120kH
kHz120 results in z
repetition every 10
ms
}
}
7.1.1.1.2 Random access procedure / Successful / C-RNTI Based / Preamble selected by

MAC itself
(1)
with { UE in RRC_Connected NR SpCell TimeAlignmentTimer expired, and has UL Data to send }
ensure that {
when { the UL MAC PDU Size is less than messageSizeGroupA }
then { UE transmits a random access preamble using a preamble in group A of random access
preambles }
}
(2)
with { UE in RRC_Connected state after transmission of a PRACH preamble on NR SpCell }
ensure that {
ETSI
when { SS does not answer with a matching Random Access Response within ra-ResponseWindowSize }
then { UE retransmits a PRACH preamble from same group }
}
(3)
ensure that {
when { UE receives while ra-ResponseWindowSizeTimer is running MAC PDU containing multiple RARs
but none of the subheaders contains a RAPID corresponding to the UE }
then { UE retransmits a PRACH preamble from same group }
}
(4)
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
from same group }
}
(5)
ensure that {
when { UE receives while ra-ResponseWindowSizeTimer is running MAC PDU containing multiple RARs
and one of the subheaders contains a RAPID corresponding to the UE and containing Backoff Indicator
}
then { UE stores Backoff Indicator UE transmits RACH procedure MSG3 }
}
(6)
with { UE in RRC_Connected state after transmission of Msg3 on NR SpCell 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 { 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 }
}
(7)
with { UE in RRC_Connected state after transmission of Msg3 on NR SpCell without dedicated preamble
}
ensure that {
when { UE receive PDCCH transmission addressed to its C-RNTI before Contention resolution timer
expiry }
then { UE considers RACH procedure as complete }
}
(8)
with { UE in RRC CONNECTED state and Random Access Preambles group B is configured }
ensure that {
when { UE has data available for transmission and the MAC PDU Size carrying this data is greater
than ra-Msg3SizeGroupA and TimeAlignmentTimer expires }
then {UE transmits a random access preamble using a preamble in group B of random access
preambles}
}
(9)
with { UE in RRC_Connected state and having initiated a random access procedure in NR SpCell }
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 }
}
ETSI
5.1.3, 5.1.4, 5.1.5, 5.2, 6.1.3.2, 6.1.5 and 6.2.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.1.2]
1> else (i.e. for the contention-based Random Access preamble selection):
2> if at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB is available:
3> select an SSB with SS-RSRP above rsrp-ThresholdSSB.
2> else:
3> select any SSB.
2> if Msg3 has not yet been transmitted:
3> if Random Access Preambles group B is configured:
4> if the potential Msg3 size (UL data available for transmission plus MAC header and, where required,
MAC CEs) is greater than ra-Msg3SizeGroupA and the pathloss is less than PCMAX (of the Serving Cell
performing the Random Access Procedure) –preambleReceivedTargetPower – msg3-DeltaPreamble –
messagePowerOffsetGroupB; or
4> if the Random Access procedure was initiated for the CCCH logical channel and the CCCH SDU size
plus MAC subheader is greater than ra-Msg3SizeGroupA:5> select the Random Access Preambles
group B.
4> else:
5> select the Random Access Preambles group A.
3> else:
2> else (i.e. Msg3 is being retransmitted):
3> select the same group of Random Access Preambles as was used for the Random Access Preamble
transmission attempt corresponding to the first transmission of Msg3.
2> if the association between Random Access Preambles and SSBs is configured:
3> select a Random Access Preamble randomly with equal probability from the Random Access Preambles
associated with the selected SSB and the selected Random Access Preambles group.
2> else:
within the selected Random Access Preambles group.
2> set the PREAMBLE_INDEX to the selected ra-PreambleIndex.
1> if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]); and
1> if ra-AssociationPeriodIndex and si-RequestPeriod are configured:
SSB in the association period given by ra-AssociationPeriodIndex in the si-RequestPeriod permitted by the
restrictions given by the ra-ssb-OccasionMaskIndex (the MAC entity shall select a PRACH occasion
ETSI
randomly with equal probability amongst the consecutive PRACH occasions according to subclause 8.1 of
TS 38.213 [6] corresponding to the selected SSB).
shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions
according to subclause 8.1 of TS 38.213 [6], corresponding to the selected SSB; the MAC entity may take
into account the possible occurrence of measurement gaps when determining the next available PRACH
occasion corresponding to the selected SSB).
which is quasi-collocated with the selected CSI-RS as specified in TS 38.214 [7] (the MAC entity may
take into account the possible occurrence of measurement gaps when determining the next available
PRACH occasion corresponding to the SSB which is quasi-collected with the selected CSI-RS).
2> else:
3> determine the next available PRACH occasion from the PRACH occasions in ra-OccasionList corresponding to
the selected CSI-RS (the MAC entity shall select a PRACH occasion randomly with equal probability amongst
the PRACH occasions occurring simultaneously but on different subcarriers, corresponding to the selected CSI-
RS; the MAC entity may take into account the possible occurrence of measurement gaps when determining the
next available PRACH occasion corresponding to the selected CSI-RS).
1> perform the Random Access Preamble transmission procedure (see subclause 5.1.3).
[TS 38.321, clause 5.1.3]
The MAC entity shall, for each Random Access Preamble:
1> if PREAMBLE_TRANSMISSION_COUNTER is greater than one; and
1> if the notification of suspending power ramping counter has not been received from lower layers; and
1> if SSB selected is not changed (i.e. same as the previous Random Access Preamble transmission):
2> increment PREAMBLE_POWER_RAMPING_COUNTER by 1.
1> select the value of DELTA_PREAMBLE according to subclause 7.3;
1> set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE +

(PREAMBLE_POWER_RAMPING_COUNTER – 1) × PREAMBLE_POWER_RAMPING_STEP;
1> except for contention-free Random Access Preamble for beam failure recovery request, compute the RA-RNTI
associated with the PRACH occasion in which the Random Access Preamble is transmitted;
1> instruct the physical layer to transmit the Random Access Preamble using the selected PRACH, corresponding
RA-RNTI (if available), PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER.
The RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as:
RA-RNTI= 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id
where s_id is the index of the first OFDM symbol of the specified PRACH (0 ≤ s_id < 14), t_id is the index of the first
slot of the specified PRACH in a system frame (0 ≤ t_id < 80), f_id is the index of the specified PRACH in the
frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for NUL carrier, and
1 for SUL carrier).
[TS 38.321, clause 5.1.4]
ETSI
MAC entity shall:
1> else:
1> if notification of a reception of a PDCCH transmission is received from lower layers on the Serving Cell where
the preamble was transmitted; and
entity:
2> else:
corresponding to the transmitted PREAMBLE_INDEX (see subclause 5.1.3):
3> if the Random Access Response includes RAPID only:
4> indicate the reception of an acknowledgement for the SI request to upper layers.
3> else:
(PREAMBLE_POWER_RAMPING_COUNTER – 1) × preamblePowerRampingStep).
5> else:
ETSI
4> else:
received; or
C-RNTI has not been received on the Serving Cell where the preamble was transmitted:
> else if the Random Access Preamble is transmitted on a SCell:
PREAMBLE_BACKOFF;
3> if the criteria (as defined in subclause 5.1.2) to select contention-free Random Access Resources is met
4> perform the Random Access Resource selection procedure (see subclause 5.1.2);
3> else:
4> perform the Random Access Resource selection procedure (see subclause 5.1.2) after the backoff
time.
[TS 38.321, clause 5.1.5]
Once Msg3 is transmitted, the MAC entity shall:
1> start the ra-ContentionResolutionTimer and restart the ra-ContentionResolutionTimer at each HARQ
retransmission in the first symbol after the end of the Msg3 transmission;
1> monitor the PDCCH while the ra-ContentionResolutionTimer is running regardless of the possible occurrence of
a measurement gap;
1> if notification of a reception of a PDCCH transmission of the SpCell is received from lower layers:
2> if the C-RNTI MAC CE was included in Msg3:
ETSI
3> if the Random Access procedure was initiated by the MAC sublayer itself or by the RRC sublayer and the
PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new transmission; or
3> if the Random Access procedure was initiated by a PDCCH order and the PDCCH transmission is
addressed to the C-RNTI; or
3> if the Random Access procedure was initiated by a beam failure indication from lower layer and the
PDCCH transmission is addressed to the C-RNTI:
4> consider this Contention Resolution successful;
4> stop ra-ContentionResolutionTimer;
4> discard the TEMPORARY_C-RNTI;
4> consider this Random Access procedure successfully completed.
1> if ra-ContentionResolutionTimer expires:
2> consider the Contention Resolution not successful.
1> if the Contention Resolution is considered not successful:
2> flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer;
PREAMBLE_BACKOFF;
3> else:
time.
[TS 38.321, clause 5.2]
RRC configures the following parameters for the maintenance of UL time alignment:
- timeAlignmentTimer (per TAG) which controls how long the MAC entity considers the Serving Cells belonging
to the associated TAG to be uplink time aligned.
1> when a Timing Advance Command MAC CE is received, and if a NTA (as defined in TS 38.211 [8]) has been
maintained with the indicated TAG:
2> apply the Timing Advance Command for the indicated TAG;
ETSI
2> start or restart the timeAlignmentTimer associated with the indicated TAG.
1> when a timeAlignmentTimer expires:
2> if the timeAlignmentTimer is associated with the PTAG:
3> flush all HARQ buffers for all Serving Cells;
3> notify RRC to release PUCCH for all Serving Cells, if configured;
3> notify RRC to release SRS for all Serving Cells, if configured;
3> clear any configured downlink assignments and configured uplink grants;
3> clear any PUSCH resource for semi-persistent CSI reporting;
3> consider all running timeAlignmentTimers as expired;
3> maintain NTA (defined in TS 38.211 [8]) of all TAGs.
2> else if the timeAlignmentTimer is associated with an STAG, then for all Serving Cells belonging to this TAG:
3> flush all HARQ buffers;
3> notify RRC to release PUCCH, if configured;
3> notify RRC to release SRS, if configured;
3> maintain NTA (defined in TS 38.211 [8]) of this TAG.
When the MAC entity stops uplink transmissions for an SCell due to the fact that the maximum uplink transmission
timing difference between TAGs of the MAC entity or the maximum uplink transmission timing difference between
TAGs of any MAC entity of the UE is exceeded, the MAC entity considers the timeAlignmentTimer associated with the
SCell as expired.
The MAC entity shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble
transmission when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not running.
Furthermore, when the timeAlignmentTimer associated with the pTAG is not running, the MAC entity shall not perform
any uplink transmission on any Serving Cell except the Random Access Preamble transmission on the SpCell.
[TS 38.321, clause 6.1.3.2]
The C-RNTI MAC CE is identified by MAC PDU subheader with LCID as specified in Table 6.2.1-2.
It has a fixed size and consists of a single field defined as follows (Figure 6.1.3.2-1):
- C-RNTI: This field contains the C-RNTI of the MAC entity. The length of the field is 16 bits.
C-RNTI Oct 1
C-RNTI Oct 2
Figure 6.1.3.2-1: C-RNTI MAC CE
[TS 38.321, clause 6.1.5]
ETSI
A MAC PDU consists of one or more MAC subPDUs and optionally padding. Each MAC subPDU consists one of the
following:
- a MAC subheader with Backoff Indicator only;
- a MAC subheader with RAPID only (i.e. acknowledgment for SI request);
- a MAC subheader with RAPID and MAC RAR.
A MAC subheader with Backoff Indicator consists of five header fields E/T/R/R/BI as described in Figure 6.1.5-1. A
MAC subPDU with Backoff Indicator only is placed at the beginning of the MAC PDU, if included. 'MAC subPDU(s)
with RAPID only' and 'MAC subPDU(s) with RAPID and MAC RAR' can be placed anywhere between MAC subPDU
with Backoff Indicator only (if any) and padding (if any).
A MAC subheader with RAPID consists of three header fields E/T/RAPID as described in Figure 6.1.5-2.
Padding is placed at the end of the MAC PDU if present. Presence and length of padding is implicit based on TB size,
size of MAC subPDU(s).
E T R R BI Oct 1
Figure 6.1.5-1: E/T/R/R/BI MAC subheader
E T RAPID Oct 1
Figure 6.1.5-2: E/T/RAPID MAC subheader
E/T/R/R/BI E/T/RAPID E/T/RAPID

MAC RAR
subheader subheader subheader
MAC subPDU 1
(BI only)
MAC subPDU 2
(RAPID only)
MAC subPDU 2
(RAPID and RAR)
MAC subPDU 3 ... MAC subPDU n Padding (opt)
Figure 6.1.5-3: Example of MAC PDU consisting of MAC RARs
[TS 38.321, clause 6.2.3]
The MAC RAR is of fixed size as depicted in Figure 6.2.3-1, and consists of the following fields:
- R: Reserved bit, set to "0";
- Timing Advance Command: The Timing Advance Command field indicates the index value TA used to control
the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6]. The size of the Timing
Advance Command field is 12 bits;
- UL Grant: The Uplink Grant field indicates the resources to be used on the uplink in TS 38.213 [6]. The size of
the UL Grant field is 27 bits;
ETSI
- Temporary C-RNTI: The Temporary C-RNTI field indicates the temporary identity that is used by the MAC
entity during Random Access. The size of the Temporary C-RNTI field is 16 bits.
The MAC RAR is octet aligned.
R Timing Advance Command

Oc t 2 Oc t 1
Timing Advance Command
Oct2 UL Grant Oc t 2
UL Grant Oc t 3
UL Grant Oc t 4
UL Grant Oc t 5
Temporary C-RNTI Oc t 6
Temporary C-RNTI Oc t 7
Figure 6.2.3-1: MAC RAR
Same Pre-test conditions as in clause 7.1.1.0.
ETSI

U-S Message
- EXCEPTION: Step 0AA is performed IF - - - -
pc_NG_RAN_NR only.
0AA The SS transmits an updated system - - - -
information as specified in Table 7.1.1.1.2.3.3-
1A.
to configure specific parameters. (Note 1)
RRCReconfigurationComplete message. (Note
2)
1 SS transmits Timing Advance command to <-- MAC PDU (Timing Advance - -
SpCell. SS does not send any subsequent Command MAC Control Element)
timing alignments. Start Timer_T1 = Time
Alignment timer value on SS.
2 40 to 50 TTI before Timer_T1 expires the SS <-- MAC PDU - -
transmits a MAC PDU containing a PDCP
SDU of size 56 bits, less then ra-
Msg3SizeGroupA (208 bits) on SpCell. (Note
3)
3 The SS ignores scheduling requests and does - - - -
not allocate any uplink grant.
4 Check: Does the UE transmit preamble on --> PRACH Preamble 1 P
PRACH using a preamble in group A defined
in CellGroupConfig in RRCReconfiguration
(totalNumberOfRA-Preambles, ssb-perRACH-
OccasionAndCB-PreamblesPerSSB and
numberOfRA-PreamblesGroupA) on SpCell in
frame number X meeting condition nSFN mod 8
=1, subframe number 2,6,9 (FDD FR1), frame
number X meeting condition nSFN mod 2 =1,
subframe number 4,9 (FR1 TDD) and frame
number X meeting condition nSFN mod 4 =1
and slot number 8, 9, 18, 19, 28, 29, 38, 39 ,
48, 49, 58, 59, 68, 69, 78, 79 (FR2 120 kHz)?
5 Check: Does the UE transmit a preamble on --> PRACH Preamble 2 P
PRACH, in frame number X+8 subframe
number 2,6,9 (FDD FR1), in frame number X
or X+2 in subrame number 4,9 (FR1 TDD) and
frame number X or X+4 and slot number 8, 9,
18, 19, 28, 29, 38, 39 , 48, 49, 58, 59, 68, 69,
78, 79 (FR2 120 kHz) using the same group
A?
6 The SS transmits a MAC PDU addressed to <-- Random Access Response - -
UE RA-RNTI, containing multiple RARs but
none of the MAC sub headers contains a
matching RAPID on SpCell.
- EXCEPTION: In parallel with step 7, parallel - - - -
behaviour defined in table 7.1.1.1.2.3.2-2 is
executed.
7 Check: Does the UE re-transmit a preamble on --> PRACH Preamble 3 P
PRACH on SpCell using the same group A?
8 The SS transmits a Random Access Response <-- Random Access Response(BI, - -
with the back off parameter set to value Index RAPID)
field '12' and with the Random Access
Preamble identifier different from the value
received from the UE in the Random Access
Preamble.
The SS sets Timer_T2 to the Back off value
‘960’ associated with the Index value ‘12’ and
starts Timer_T2.
ETSI
9 Check: Does UE send a Random Access --> Random Access Preamble 4 P

Preamble on SpCell while Timer_T2 is
running?
10 SS sends Random Access Response with an <-- Random Access Response(BI, - -
UL Grant of 56-bits, a back off parameter set RAPID)
to value Index field ‘13’ and the Random
Access Preamble identifier value set to the
same value as received from the UE in the
Random Access Preamble. (Note 4)
11 Check: Does UE sends a msg3 in the grant --> msg3 (C-RNTI MAC CONTROL 5 P
associated to the Random Access ´Response ELEMENT)
received in step 10 on SpCell?
12 SS does not schedule any PDCCH - - - -
transmission for UE C-RNTI.
The SS sets Timer_T3 to the Back off value
‘1920’ associated with the Index value ‘13’ plus
Contention Resolution Timer and starts
Timer_T3.
PRACH using a preamble belonging to group
A for time equal to Timer_T3 on SpCell?
with an UL Grant of 56-bits and RAPID
corresponding to the transmitted Preamble in
step 13, including T-CRNTI.
15 UE sends a msg3 using the grant associated --> msg3 (C-RNTI MAC CONTROL - -
to the Random Access ´Response received in ELEMENT)
step 14 on SpCell?
16 SS schedules PDCCH transmission for UE <-- Contention Resolution - -
C_RNTI and allocate uplink grant.
executed.
17 Check: Does the UE transmit a MAC PDU with --> MAC PDU 7 P
C-RNTI containing looped back PDCP SDU?
- EXCEPTION: Step 17AA is performed IF - - - -
pc_NG_RAN_NR only.
17A The SS transmits an updated system - - - -
A information as specified in Table 7.1.1.1.2.3.3-
1A.
17A The SS transmits an RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
message to configure specific parameters.
(Note 1)
17B The UE transmits an --> NR RRC: - -
RRCReconfigurationComplete message. (Note RRCReconfigurationtComplete
2)
SDU of size > ra-Msg3SizeGroupA (208 bits).
PRACH using a preamble in group B defined
in CellGroupConfig in RRCReconfiguration
(ssb-perRACH-OccasionAndCB-
PreamblesPerSSB, numberOfRA-
PreamblesGroupA and numberOfRA-
Preambles) on SpCell?
with an UL Grant of 56-bits and RAPID
corresponding to the transmitted Preamble in
step 21, including T-CRNTI.
ETSI
to the Random Access ´Response received in ELEMENT)
step 22 on SpCell?
23A SS schedules PDCCH transmission for UE <-- Contention Resolution - -
C-RNTI containing looped back PDCP SDU?
Note 3: MAC PDU size of 56bits is selected to allow UE send status PDU and still stays below the limit of ra-
Msg3SizeGrioupA.
Note 4: UL grant of 56bits is to make UE not send any loopback data in uplink with msg3.
Table 7.1.1.1.2.3.2-2: Parallel behaviour

U-S Message
1 Check: Does the UE transmit msg3 message --> msg3 (C-RNTI MAC CONTROL - F
on SpCell? ELEMENT)

U-S Message
1 Check: Does the UE transmit an PRACH --> PRACH Preamble - F
preamble on SpCell?
Table 7.1.1.1.2.3.3-1: MAC-CellGroupConfig (preamble)

tag-Config SEQUENCE {
tag-ToAddModList SEQUENCE (SIZE 1 entry
(1..maxNrofTAGs)) OF TAG {
TAG[1] SEQUENCE { entry 1
timeAlignmentTimer ms750
}
}
}
}
Table 7.1.1.1.2.3.3-1A: SystemInformationBlockType1 (step 0AA and 17AA, Table 7.1.1.1.2.3.2-1)
Derivation path: 38.508-1 [4] table 4.6.1-28

SIB1 ::= SEQUENCE {
servingCellConfigCommon ServingCellConfigComm Same contents as
on in Table
7.1.1.1.2.3.3-4
}
ETSI
Table 7.1.1.1.2.3.3-2: RRCReconfiguration (step 0A and step 17A, Table 7.1.1.1.2.3.2-1)

TS 38.508-1 [4],
2.
(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}
Table 7.1.1.1.2.3.3-3: CellGroupConfig (Table 7.1.1.1.2.3.3-2)

on
t304 ms2000
}
Table 7.1.1.1.2.3.3-4: ServingCellConfigCommon (Table 7.1.1.1.2.3.3-3, Table 7.1.1.1.2.3.3-1A)

}
}

}
}
ETSI

totalNumberOfRA-Preambles 42
ssb-perRACH-OccasionAndCB-PreamblesPerSSB
CHOICE {
One n32
}
groupBconfigured SEQUENCE {
ra-Msg3SizeGroupA b208
messagePowerOffsetGroupB minusinfinity
numberOfRA-PreamblesGroupA 28
}
ra-ContentionResolutionTimer sf48
}
ETSI

prach-ConfigurationIndex 119 As per Table FR1 FDD
6.3.3.2-2: of TS
38.211 [24], this
results in PRACH
preamble
transmission in a
radio frame
meeting nSFN mod
2=1, subframe
number 2, 6, 9
and starting
symbol 0 using
preamble Format
A2.
prach-ConfigurationIndex 94 As per Table FR1 TDD
6.3.3.2-3: of TS
38.211 [24], this
results in PRACH
preamble
transmission in a
radio frame
meeting nSFN mod
2=1, subframe
number 4, 9 and
starting symbol 0
using preamble
Format A2.
prach-ConfigurationIndex 6 As per Table FR2 (120
6.3.3.2-4: of TS kHz)
38.211 [24] and
clause 5.3.2 of TS
38.211 this results
in PRACH
preamble
transmission in
radio frame
meeting nSFN
mod 4 = 1, slot
number 8, 9, 18,
19, 28, 29, 38, 39
, 48, 49, 58, 59,
68, 69, 78, 79 and
starting symbol 0
using preamble
format A1.
preambleReceivedTargetPower dBm-104
preambleTransMax n10
powerRampingStep dB2
ra-ResponseWindow sl8 FR1 FDD
and FR2
(120 kHz)
sl20 FR1 TDD
}
ETSI
Table 7.1.1.1.2.3.3-8: Void
7.1.1.1.3 Random access procedure / Successful / SI request
(1)
with { UE in RRC_Idle State and need for Updated System information }
ensure that {
when { UE transmitted PRACH preamble and ra-ResponseWindow has expired}
then { UE retransmits the PRACH Preamble }
}
(2)
with { UE in RRC_Idle State and transmitted PRACH preamble for System information request }
ensure that {
when { UE received a RAR message addressed to RA-RNTI and including matching RAPID only }
then { UE considers the RACH procedure to be successfully completed and informs the upper layer
}
}
(3)
Void
5.1.3, 5.1.4, and 6.1., 3GPP TS 38.331 clause 5.2.2.2.25. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.1.2]
1> if the Random Access procedure was initiated for beam failure recovery (as specified in subclause 5.17); and
1> if the beamFailureRecoveryTimer (in subclause 5.17) is either running or not configured; and
1> if the contention-free Random Access Resources for beam failure recovery request associated with any of the
SSBs and/or CSI-RSs have been explicitly provided by RRC; and
1> if at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB amongst the SSBs in candidateBeamRSList
or the CSI-RSs with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the CSI-RSs in candidateBeamRSList is
available:
2> select an SSB with SS-RSRP above rsrp-ThresholdSSB amongst the SSBs in candidateBeamRSList or a CSI-
RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the CSI-RSs in candidateBeamRSList;
2> if CSI-RS is selected, and there is no ra-PreambleIndex associated with the selected CSI-RS:
3> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the SSB in candidateBeamRSList

which is quasi-collocated with the selected CSI-RS as specified in TS 38.214 [7].
2> else:
3> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected SSB or CSI-RS from
the set of Random Access Preambles for beam failure recovery request.
1> else if the ra-PreambleIndex has been explicitly provided by either PDCCH or RRC; and
1> if the ra-PreambleIndex is not 0b000000; and
ETSI
1> if contention-free Random Access Resource associated with SSBs or CSI-RSs have not been explicitly provided
by RRC:
2> set the PREAMBLE_INDEX to the signalled ra-PreambleIndex.
1> else if the contention-free Random Access Resources associated with SSBs have been explicitly provided by
RRC and at least one SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated SSBs is available:
1> else if the contention-free Random Access Resources associated with CSI-RSs have been explicitly provided by
RRC and at least one CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the associated CSI-RSs is
available:
2> select a CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the associated CSI-RSs;
2> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected CSI-RS.
1> else:
2> else:
3> select any SSB.
MAC CEs) is greater than ra-Msg3SizeGroupA and the pathloss is less than PCMAX (of the Serving
Cell performing the Random Access Procedure) – preambleReceivedTargetPower – msg3-
DeltaPreamble – messagePowerOffsetGroupB; or
plus MAC subheader is greater than ra-Msg3SizeGroupA:
5> select the Random Access Preambles group B.
4> else:
3> else:
3> select a ra-PreambleIndex randomly with equal probability from the Random Access Preambles
2> else:
3> select a ra-PreambleIndex randomly with equal probability from the Random Access Preambles within
the selected Random Access Preambles group.
2> set the PREAMBLE_INDEX to the selected ra-PreambleIndex.
ETSI
1> if an SSB is selected above and an association between PRACH occasions and SSBs is configured:
shall select a PRACH occasion randomly with equal probability amongst the PRACH occasions occurring
simultaneously but on different subcarriers, corresponding to the selected SSB; the MAC entity may take into
account the possible occurrence of measurement gaps when determining the next available PRACH occasion
corresponding to the selected SSB).
1> else if a CSI-RS is selected above and an association between PRACH occasions and CSI-RSs is configured:
2> determine the next available PRACH occasion from the PRACH occasions in ra-OccasionList corresponding
to the selected CSI-RS (the MAC entity shall select a PRACH occasion randomly with equal probability
amongst the PRACH occasions occurring simultaneously but on different subcarriers, corresponding to the
selected CSI-RS; the MAC entity may take into account the possible occurrence of measurement gaps when
determining the next available PRACH occasion corresponding to the selected CSI-RS).
1> else if Random Access procedure was initiated for beam failure recovery; and
1> if a CSI-RS is selected above and there is no contention-free Random Access Resource associated with the
selected CSI-RS:
which is quasi-collocated with the selected CSI-RS as specified in TS 38.214 [7] (the MAC entity may take
occasion corresponding to the SSB which is quasi-collected with the selected CSI-RS).
1> else:
2> determine the next available PRACH occasion (the MAC entity shall select a PRACH occasion randomly
with equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers;
next available PRACH occasion).
[TS 38.321, clause 5.1.3]
1> if SSB selected is not changed (i.e. same as the previous Random Access Preamble transmission):

1> instruct the physical layer to transmit the Random Access Preamble using the selected PRACH, corresponding
RA-RNTI (if available), PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER.
The RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as:
where s_id is the index of the first OFDM symbol of the specified PRACH (0 ≤ s_id < 14), t_id is the index of the first
slot of the specified PRACH in a system frame (0 ≤ t_id < 80), f_id is the index of the specified PRACH in the
ETSI
frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for NUL carrier, and
1 for SUL carrier).
[TS 38.321, clause 5.1.4]
MAC entity shall:
entity:
2> monitor the PDCCH of the SpCell for response to beam failure recovery request identified by the C-RNTI
while ra-ResponseWindow is running.
1> else:
1> if notification of a reception of a PDCCH transmission is received from lower layers; and
entity:
2> else:
3> else:
ETSI
5> else:
4> else:
procedure:
Msg3 buffer.
received; or
C-RNTI has not been received:
3> if in this Random Access procedure, the Random Access Preamble was selected by MAC among the
contention-based Random Access Preambles:
PREAMBLE_BACKOFF;
4> delay the subsequent Random Access Preamble transmission by the backoff time.
ETSI
[TS 38.321, clause 6.1.5]
following:
E T R R BI Oct 1
E T RAPID Oct 1

MAC RAR
MAC subPDU 1
(BI only)
MAC subPDU 2
(RAPID only)
MAC subPDU 2
(RAPID and RAR)
[38.331, clause 5.2.2.2.2]
UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for SI change indication in its own paging occasion every
DRX cycle. UEs in RRC_CONNECTED shall monitor for SI change indication in any paging occasion at least once per
ETSI
modification period if the UE is provided with common search space on the active BWP to monitor paging, as specified
in TS 38.213 [13], clause 13.
ETWS or CMAS capable UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for indications about PWS
notification in its own paging occasion every DRX cycle. ETWS or CMAS capable UEs in RRC_CONNECTED shall
monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle if the UE
is provided with common search space on the active BWP to monitor paging.
For Short Message reception in a paging occasion, the UE monitors the PDCCH monitoring occasion(s) for paging as
specified in TS 38.304 [20] and TS 38.213 [13].
If the UE receives a Short Message, the UE shall:
1> if the UE is ETWS capable or CMAS capable, the etwsAndCmasIndication bit of Short Message is set, and the
UE is provided with searchSpaceOtherSystemInformation on the active BWP:
2> immediately re-acquire the SIB1;
2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB6:
3> acquire SIB6, as specified in clause 5.2.2.3.2, immediately;
3> acquire SIB7, as specified in clause 5.2.2.3.2, immediately;
2> if the UE is CMAS capable and si-SchedulingInfo includes scheduling information for SIB8:
3> acquire SIB8, as specified in sub-clause 5.2.2.3.2, immediately;
1> if the systemInfoModification bit of Short Message is set:
2> apply the SI acquisition procedure as defined in sub-clause 5.2.2.3 from the start of the next modification period.
System Simulator:
- System information combination NR-3 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in NR Cell 1.
UE:
- None.
Preamble:
- The UE is in NR RRC_Idle mode (state 1N-A) on NR Cell 1 according to 38.508-1 [4] Table 4.4A.2-1.
Table 7.1.1.1.3.3.2-1/2 illustrate the downlink power levels and other changing parameters to be applied for the cell at
texts in this clause. Configurations marked "T0" is applied for Preamble. Configurations marked "T1" and "T2" are
applied at the points indicated in the Main behaviour description in Table 7.1.1.1.3.3.2-3.
ETSI
Table 7.1.1.1.3.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter Unit NR Cell 1 NR Cell Remark
11
T0 SS/PBCH dBm/SC -90 Off The power level is such that SrxlevNRCell1 > 0
SSS EPRE S
Qoffset dB 16 -
T1 SS/PBCH dBm/SC -90 -84 The power level values are assigned to satisfy
SSS EPRE S RNRCell 1 > RNRCell 11
Qoffset dB 16 -
SSS EPRE S RNRCell 1 < RNRCell 11
Qoffset dB -10 -
Note: The downlink signal level uncertainty is specified in TS 38.508-1 [4] clause 6.2.2.1.
Parameter Unit NR Cell 1 NR Cell Remark
11
T0 SS/PBCH dBm/SC -91 Off The power level is such that SrxlevNRCell1 > 0
SSS EPRE S
Qrxlevmin dBm 2* -
ROUND((-
110+Delta
(NRfs))/2)
Qoffset dB 16 -
SSS EPRE S RNRCell 1 > RNRCell 11
Qrxlevmin dBm 2* 2*
ROUND((- ROUND((-
110+Delta 110+Delta
(NRfs))/2) (NRfs))/2)
Qoffset dB 16 -
SSS EPRE S RNRCell 1 < RNRCell 11
Qrxlevmin dBm 2* 2*
ROUND((- ROUND((-
110+Delta 110+Delta
(NRfs))/2) (NRfs))/2)
Qoffset dB -10 -
Note: The downlink signal level uncertainty is specified in TS 38.508-1 [4] section 6.2.2.2.
ETSI

U-S Message
EPRE level of NR Cell 11 according to the row
"T1" in Table 7.1.1.1.3.3.2-1/2.
2 Wait 60s to ensure UE detects NR Cell 11. - - - -
3 SS transmits Short Message on PDCCH <-- (Short Message) - -
addressed to P-RNTI using Short Message
field in DCI format 1_0. Bit 1 of Short Message
field is set to 1 to indicate the SI modification.
4 The valueTag for SIB3 in the SIB1 message is <-- - -
increased and si-BroadcastStatus for SIB3 is
set to ‘notBroadcasted’ and SS stops
broadcasting SIB3.
PRACH using the preamble indicated by ra-
PreambleStartIndex defined in SI-
RequestConfig in SIB1 in Table 7.1.1.1.3.3.3-
1?
PRACH after ra-ResponseWindow using the
preamble indicated by ra-PreambleStartIndex
defined in SI-RequestConfig in SIB1 in Table
7.1.1.1.3.3.3-1?
7.1.1.1.3.3.3-1?
7.1.1.1.3.3.3-1?
9 The SS transmits a RAR message addressed <-- Random Access Response - -
to UE RA-RNTI including a MAC subPDU with
a matching RAPID only. (Note 1)
9A The SS changes the parameter ‘Qoffset’ in
SIB3 of NR Cell 1 according to the row "T2" in
Table 7.1.1.1.3.3.2-1/2 and starts broadcasting
SIB3.
10 Check: Does UE send Msg3 containing an --> RRCSetupRequest 2 F
RRCSetupRequest message in the grant
associated to the Random Access Response
received in step 9?
belonging to a new TA?
Note 1: The UE will indicate the reception of an acknowledgement for SI request to upper layers after UE receives
the RAR message including a MAC subPDU with a matching RAPID only, according to TS 38.321 [18]
clause 5.1.4.
ETSI
Table 7.1.1.1.3.3.3-1: SIB1 on NR Cell 1 (Step 4, Table 7.1.1.1.3.3.2-3)

SIB1 ::= SEQUENCE {
si-SchedulingInfo SEQUENCE {
schedulingInfoList SEQUENCE { 2 entries
si-BroadcastStatus[1] Broadcasting
si-Periodicity[1] rf32
sib-MappingInfo[1] SEQUENCE {
type SibType2
valueTag 0
areaScope Not present
}
si-BroadcastStatus[2] notBroadcasting
si-Periodicity[2] rf64
sib-MappingInfo[2] SEQUENCE {
type SibType3
valueTag 1
areaScope Not present
}
}
si-Request-Config SEQUENCE {
rach-OccasionsSI SEQUENCE {
rach-ConfigSI RACH-ConfigGeneric TS 38.508-1 [4],
Table 4.6.3-130
ssb-perRACH-Occasion one
}
si-RequestPeriod two
si-RequestResources SEQUENCE {
ra-PreambleStartIndex 52
ra-AssociationPeriodIndex 0
ra-ssb-OccasionMaskIndex 0
}
}
si-Request-ConfigSUL Not present
}
}
Table 7.1.1.1.3.3.3-2: SIB3 on NR Cell 1 (Preamble and Step 9A, Table 7.1.1.1.3.3.2-3)

SIB3 ::= SEQUENCE {
intraFreqNeighCellList SEQUENCE {
physCellId The cell identity of NR
Cell 11 defined in
38.508-1 [4] clause 4.4.2
q-OffsetCell 16 Preamble
-10 Step 9A
}
}
ETSI
7.1.1.1.4 Random access procedure / Successful / Beam Failure / Preamble selected by

MAC itself / Non Contention Free RACH procedure
(1)
with { UE in RRC_CONNECTED state with no failureDetectionResources configured and RACH procedure due
to beam failure is triggered }
ensure that {
when { contention free random access resources for beam failure recovery request associated with
SS blocks are not provided by RRC }
then { UE selects initiates the non-contention free Random Access Procedure }
}
(2)
with { UE in RRC_CONNECTED state and RACH procedure due to beam failure is triggered }
ensure that {
SS blocks are explicitly provided by RRC }
then { UE selects the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected SS
block and initiates the contention free Random Access Procedure }
}
(3)
with { UE in RRC_CONNECTED state and RACH procedure due to beam failure is triggered }
ensure that {
CSI-RS are explicitly provided by RRC }
then { UE selects the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected CSI-RS
and initiates the contention free Random Access Procedure }
}
(4)
with { UE in RRC_CONNECTED state with Preamble transmitted for contention free RACH procedure for
beam failure }
ensure that {
when { ra-ResponseWindowBFR expires and the PDCCH addressed to the C-RNTI has not been received }
then { UE retransmits the PRACH Preamble }
}
(5)
with { UE in RRC_CONNECTED state with Preamble transmitted for contention free RACH procedure for
beam failure }
ensure that {
when { before expiry of ra-ResponseWindowBFR the PDCCH addressed to the C-RNTI is received }
then { UE considers the RACH procedure to be successfully completed and stops retransmitting
PRACH preambles }
}
References: The conformance requirements covered in the present test case are specified in: TS 38.321, clause 5.1.2,
5.1.3, 5.1.4 and 5.17. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.1.2]
ETSI
available:

which is quasi-collocated with the selected CSI-RS as specified in TS 38.214 [7].
2> else:
1> else if the contention-free Random Access Resources associated with SSBs have been explicitly provided by
RRC and at least one SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated SSBs is available:
1> else if the contention-free Random Access Resources associated with CSI-RSs have been explicitly provided by
RRC and at least one CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the associated CSI-RSs is
available:
1> else if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]); and
1> if the Random Access Resources for SI request have been explicitly provided by RRC:
2> else:
3> select any SSB.
2> select a Random Access Preamble corresponding to the selected SSB, from the Random Access Preamble(s)
determined according to ra-PreambleStartIndex as specified in TS 38.331 [5];
2> set the PREAMBLE_INDEX to selected Random Access Preamble.
2> else:
3> select any SSB.
ETSI
4> else:
3> else:
2> else:
within the selected Random Access Preambles group.
2> set the PREAMBLE_INDEX to the selected Random Access Preamble.
1> if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]); and
restrictions given by the ra-ssb-OccasionMaskIndex (the MAC entity shall select a PRACH occasion
randomly with equal probability amongst the consecutive PRACH occasions according to subclause 8.1 of
TS 38.213 [6] corresponding to the selected SSB).
shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions
according to subclause 8.1 of TS 38.213 [6], corresponding to the selected SSB; the MAC entity may take
occasion corresponding to the selected SSB).
which is quasi-collocated with the selected CSI-RS as specified in TS 38.214 [7] (the MAC entity may
take into account the possible occurrence of measurement gaps when determining the next available
PRACH occasion corresponding to the SSB which is quasi-collected with the selected CSI-RS).
2> else:
ETSI
CSI-RS).
NOTE: When the UE determines if there is an SSB with SS-RSRP above rsrp-ThresholdSSB or a CSI-RS with
CSI-RSRP above rsrp-ThresholdCSI-RS, the UE uses the latest unfiltered L1-RSRP measurement.
[TS 38.321, clause 5.1.4]
MAC entity shall:
entity:
2> monitor the PDCCH of the SpCell for response to beam failure recovery request identified by the C-RNTI
while ra-ResponseWindow is running.
1> else:
1> if notification of a reception of a PDCCH transmission is received from lower layers on the Serving Cell where
the preamble was transmitted; and
entity:
2> else:
ETSI
3> else:
5> else:
4> else:
procedure:
Msg3 buffer.
received; or
C-RNTI has not been received on the Serving Cell where the preamble was transmitted:
ETSI
PREAMBLE_BACKOFF;
3> else:
time.
Same Pre-test conditions as in clause 7.1.1.0 except that set to return no data in uplink.
Table 7.1.1.1.4.3.2-1/1A 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 preamble, while
columns marked "T1"and "T2"are to be applied subsequently. The exact instants on which these values shall be applied
are described in the texts in this clause.
Parameter Unit E-UTRA NR Cell 1 NR Cell 1 NR Cell 1 Remark
Cell 1 Beam Beam
index #1 index #0
Cell-specific RS dBm/15 Beam#1 Switch ON and
-85 - - - Beam#0 Switch OFF
EPRE kHz
Reference dBm/SC
T0 - -88 - -
Power S
CSI-RS EPRE
SS/PBCH dB - - 0 -57
SSS EPRE,
Cell-specific RS dBm/15 Beam#1 Switch OFF and
-85 - - -
EPRE kHz Beam#0 Switch ON
Reference dBm/SC
- -88 - -
T1 Power S
CSI-RS EPRE
SS/PBCH dB - - -57 0
SSS EPRE,
-85 - - -
EPRE kHz Beam#0 Switch OFF
Reference dBm/SC
- -88 - -
T2 Power S
CSI-RS EPRE
SSS EPRE,
NOTE: "Beam index #1" refers to transmission of the SS/PBCH block with SSB index #1 (according to the ssb-
PositionsInBurst) and CSI-RS with index #1 (according to the CSI-MeasConfig being signalled to the UE at
step 1/8/17); "Beam index #0" refers to transmission of the SS/PBCH block with SSB index #0 (according to
the ssb-PositionsInBurst) and CSI-RS with index #0 (according to the CSI-MeasConfig being signalled to the
UE at step 1/8/17).
ETSI
Table 7.1.1.1.4.3.2-1A: Time instances of cell power level and parameter changes for FR2
Parameter Unit E-UTRA NR Cell 1 NR Cell 1 NR Cell 1 Remark
Cell 1 Beam Beam
index #1 index #0
-96 - - - Beam#0 Switch OFF
EPRE kHz
Reference dBm/SC
T0 - -82 - -
Power S
CSI-RS EPRE
SSS EPRE,
Cell-specific RS dBm/15 Beam#1 Switch OFF and
-96 - - -
EPRE kHz Beam#0 Switch ON
Reference dBm/SC
- -82 - -
T1 Power S
CSI-RS EPRE
dBm/SC
SS/PBCH - - -63 0
S
SSS EPRE,
-96 - - -
EPRE kHz Beam#0 Switch OFF
Reference dBm/SC
- -82 - -
T2 Power S
CSI-RS EPRE
dBm/SC
SS/PBCH - - 0 -63
S
SSS EPRE,
NOTE: "Beam index #1" refers to transmission of the SS/PBCH block with SSB index #1 (according to the ssb-
PositionsInBurst) and CSI-RS with index #1 (according to the CSI-MeasConfig being signalled to the UE at
step 1/8/17); "Beam index #0" refers to transmission of the SS/PBCH block with SSB index #0 (according to
the ssb-PositionsInBurst) and CSI-RS with index #0 (according to the CSI-MeasConfig being signalled to the
UE at step 1/8/17).
ETSI

U-S Message
1 The SS transmits an NR RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
message to configure parameters for BFR.
Note 1.
2 UE responses NR --> NR RRC: - -
RRCReconfigurationComplete message. Note RRCReconfigurationComplete
2.
3 The SS changes NR Cell 1 power level - - - -
according to the row "T1" in table 7.1.1.1.4.3.2-
1/1A.
PRACH for the non-contention free Random
Access Procedure on NR Cell 1 Beam index
#1?
UE RA-RNTI, containing multiple RAR’s and
one of the MAC sub headers contains a
matching RAPID on NR Cell 1.
to the Random Access Response received in ELEMENT)
Step 5 on NR Cell 1.
7 SS schedules PDCCH transmission for UE C- <-- Contention Resolution - -
RNTI.
8 The SS transmits an NR RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
to establish random access resources for BFR
associated with SS blocks explicitly. Note 1.
2.
1/1A.
PRACH using a preamble with
PREAMBLE_INDEX to a ra-PreambleIndex
corresponding to the selected SS block
provided by RRC on NR Cell 1 Beam index
#0?
12 The SS waits for ra-ResponseWindowBFR - - - -
expire.
NOTE: The SS does not transmit Random
Access Response to the UE.
13 Check: Does the UE retransmit a preamble on --> PRACH Preamble 4 P
PRACH with ra-PreambleIndex same as the
Step 11?
UE C-RNTI, containing multiple RAR’s and
expire.
16 Check: Does the UE retransmit a preamble on - - 5 F
PRACH?
- EXCEPTION: Steps 17 to 25 describe - - - -
behaviour that depends on the UE capability.
17 IF pc_csi_RS_CFRA_ForHO THEN the SS <-- NR RRC: RRCReconfiguration - -
transmits an NR RRCReconfiguration
message to establish random access
resources for BFR associated with CSI-RS
explicitly. Note 1.
2.
ETSI

1/1A.
PRACH using a preamble with
PREAMBLE_INDEX to a ra-PreambleIndex
corresponding to the selected CSI-RS
provided by RRC on NR Cell 1 Beam index
#1?
expire.
NOTE: The SS does not transmit Random
Access Response to the UE.
22 Check: Does the UE retransmit a preamble on --> PRACH Preamble 4 P
PRACH with ra-PreambleIndex same as the
Step 20?
UE C-RNTI, containing multiple RAR’s and
expire.
25 Check: Does the UE retransmit a preamble on - - 5 F
PRACH?
Note 1: for EN-DC the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration 36.508 [7],
Table 4.6.1-8 using condition EN-DC_EmbedNR_RRCRecon.
Table 7.1.1.1.4.3.3-1: Void
Table 7.1.1.1.4.3.3-2: Void
Table 7.1.1.1.4.3.3-3: RRCReconfiguration (Step 1, Step8, Step17 Table 7.1.1.1.4.3.2-2)
Derivation path: 38.508-1 [4], Table 4.6.1-13

RRCReconfiguration::=SEQUENCE{
criticalExtensions CHOICE{
rrcReconfiguration SEQUENCE{
(CONTAINING
CellGroupConfig)
}
}
}
}
Table 7.1.1.1.4.3.3-4: CellGroupConfig (Table 7.1.1.1.4.3.3-3: RRCReconfiguration)

}
}
ETSI
Table 7.1.1.1.4.3.3-5: ServingCellConfig (Table 7.1.1.1.4.3.3-4: CellGroupConfig)

}
csi-MeasConfig CHOICE { Step 1
setup CSI-MeasConfig
}
}
Table 7.1.1.1.4.3.3-6: BWP-DownlinkDedicated (Table 7.1.1.1.4.3.3-5: ServingCellConfig)

pdcch-Config Not present Step 17
pdcch-Config CHOICE { Step 1, Step
8
setup PDCCH-Config
}
setup PDSCH-Config
}
radioLinkMonitoringConfig CHOICE {
setup RadioLinkMonitoringConf
ig
}
}
ETSI
Table 7.1.1.1.4.3.3-7: RadioLinkMonitoringConfig (Table 7.1.1.1.4.3.3-6: BWP-DownlinkDedicated)

RadioLinkMonitoringConfig ::= SEQUENCE {
failureDetectionResourcesToAddModList 2 entries
SEQUENCE
(SIZE(1..maxNrofFailureDetectionResources)) OF
RadioLinkMonitoringRS {
RadioLinkMonitoringRS[1] SEQUENCE { entry 1
radioLinkMonitoringRS-Id 0
purpose rlf Step 1, Step
17
both Step 8
detectionResource CHOICE {
csi-rs 0 NR Cell 1 Beam
index #0
}
}
RadioLinkMonitoringRS[2] SEQUENCE { entry 2
radioLinkMonitoringRS-Id 1
purpose rlf Step 1, Step
8
both Step 17
detectionResource CHOICE {
csi-rs 1 NR Cell 1 Beam
index #1
}
}
}
beamFailureInstanceMaxCount n1
beamFailureDetectionTimer pbfd1
}
ETSI
Table 7.1.1.1.4.3.3-8: PDSCH-Config (Table 7.1.1.1.4.3.3-6: BWP-DownlinkDedicated)

tci-StatesToAddModList SEQUENCE(SIZE (1.. 3 entries
tci-StateId 0
cell ServCellIndex of NR Cell ID
SpCell
bwp-id 0 BWP ID
ssb 1 SSB index #1
}
qcl-Type type C
}
qcl-type2 Not present
qcl-type2 SEQUENCE { FR2
SpCell
bwp-id 0 BWP ID
ssb 1 SSB index #1
}
qcl-Type type D
}
}
tci-StateId 1
SpCell
bwp-id 0 BWP ID
ssb 0 SSB index #0
}
qcl-Type type C
}
SpCell
bwp-id 0 BWP ID
ssb 0 SSB index #0
}
qcl-Type type D
}
}
tci-StateId 2
SpCell
bwp-id 0 BWP ID
csi-rs 1 Csi-Rs index #1
}
qcl-Type type A
}
SpCell
ETSI
bwp-id 0 BWP ID
Csi-rs 1 Csi-Rs index #1
}
qcl-Type type D
}
}
}
}
Table 7.1.1.1.4.3.3-9: PDCCH-Config (Table 7.1.1.1.4.3.3-6: BWP-DownlinkDedicated)
Derivation Path: TS 38.508-1 [4],Table 4.6.3-95

PDCCH-Config::= SEQUENCE {
controlResourceSetToAddModList 2 entries
SEQUENCE(SEQUENCE(SIZE (1..3)) OF
ControlResourceSet {
ControlResourceSet[1] ControlResourceSetid1 entry 1
}
searchSpacesToAddModList SEQUENCE(SIZE 2 entries
(1..10)) OF SearchSpace {
SearchSpace[1] SearchSpace with entry 1
condition USS
SearchSpace[2] SearchSpaceBFR entry 2
}
}
Table 7.1.1.1.4.3.3-10: ControlResourceSetId1 (Table 7.1.1.1.4.3.3-9: PDCCH-Config)

ControlResourceSet ::= SEQUENCE {
controlResourceSetId 1
tci-StatesPDCCH-ToAddList SEQUENCE (SIZE 1 entry Step 1
(1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId {
TCI-StateId[1] 2 entry 1
TCI-State Id 2
}
tci-StatesPDCCH-ToReleaseList SEQUENCE (SIZE 1 entry Step 8
(1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId {
TCI-StateId[1] 2 entry 1
TCI-State Id 2
}
}

}
ETSI
Table 7.1.1.1.4.3.3-12: SearchSpaceBFR (Table 7.1.1.1.4.3.3-9: PDCCH-Config)

SearchSpace ::= SEQUENCE {
searchSpaceId 4
searchSpaceType CHOICE {
ue-Specific SEQUENCE {
dci-Formats formats0-0-And-1-0
}
}
}
Table 7.1.1.1.4.3.3-13: CSI-MeasConfig (Table 7.1.1.1.4.3.3-5: ServingCellConfig)

CSI-MeasConfig::= SEQUENCE {
nzp-CSI-RS-ResourceToAddModList SEQUENCE { 2 entries
NZP-CSI-RS-Resource[1] NZP-CSI-RS-
ResourceId0
NZP-CSI-RS-Resource[2] NZP-CSI-RS-
ResourceId1
}
nzp-CSI-RS-ResourceSetToAddModList 1 entry
SEQUENCE {
NZP-CSI-RS-ResourceSet[1] NZP-CSI-RS-
ResourceSetid0
}
csi-IM-ResourceToAddModList Not present
csi-IM-ResourceSetToAddModList Not present
csi-SSB-ResourceSetToAddModList Not present
csi-ReportConfigToAddModList Not present
reportTriggerSize Not present
aperiodicTriggerStateList Not present
}
Table 7.1.1.1.4.3.3-14: NZP-CSI-RS-ResourceId0 (Table 7.1.1.1.4.3.3-13: CSI-MeasConfig)

NZP-CSI-RS-Resource ::= SEQUENCE {
nzp-CSI-RS-ResourceId 0
resourceMapping CSI-RS- TS 38.508-1 [4],
ResourceMapping with Table 4.6.3-45
condition TRS
qcl-InfoPeriodicCSI-RS 0 QCL to SSB #0
}
ETSI
Table 7.1.1.1.4.3.3-15: NZP-CSI-RS-ResourceId1 (Table 7.1.1.1.4.3.3-13: CSI-MeasConfig)

nzp-CSI-RS-ResourceId 1
resourceMapping CSI-RS- TS 38.508-1 [4],
ResourceMapping with Table 4.6.3-45
condition TRS
periodicityAndOffset CSI-
ResourcePeriodicityAnd
Offset_Id1
qcl-InfoPeriodicCSI-RS 1 QCL to SSB #1
}
Table 7.1.1.1.4.3.3-16: CSI-ResourcePeriodicityAndOffset_Id1 (Table 7.1.1.1.4.3.3-15: NZP-CSI-RS-

ResourceId1)

CSI-ResourcePeriodicityAndOffset ::= CHOICE {
slots80 11 FR1
slots320 41 FR2
}
Table 7.1.1.1.4.3.3-17: NZP-CSI-RS-ResourceSetid0 (Table 7.1.1.1.4.3.3-13: CSI-MeasConfig)

NZP-CSI-RS-ResourceSet ::= SEQUENCE {
nzp-CSI-ResourceSetId 0
nzp-CSI-RS-Resources SEQUENCE (SIZE 2 entries
(1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF
NZP-CSI-RS-ResourceId {
NZP-CSI-RS-ResourceId[1] 0 entry 1
}
trs-Info true
}
Table 7.1.1.1.4.3.3-18: BWP-UplinkDedicated (Table 7.1.1.1.4.3.3-5: ServingCellConfig)

setup PUCCH-Config
}
pusch-Config CHOICE {
setup PUSCH-Config
}
beamFailureRecoveryConfig BeamFailureRecoveryCo Step8
nfig_SSB
BeamFailureRecoveryCo Step17
nfig_CSIRS
Not Present Step1
}
ETSI
Table 7.1.1.1.4.3.3-19: BeamFailureRecoveryConfig_SSB (Table 7.1.1.1.4.3.3-18: BWP-

UplinkDedicated)

BeamFailureRecoveryConfig ::= SEQUENCE {
rootSequenceIndex-BFR 0 See TS 38.508-1
[4] clause 4.4.2,
Table 4.4.2-2
rach-ConfigBFR RACH-ConfigGeneric 38.508-1 [4] Table
4.6.3-130
rsrp-ThresholdSSB 57(-99dBm)
candidateBeamRSList SEQUENCE
(SIZE(1..maxNrofCandidateBeams)) OF PRACH-
ResourceDedicatedBFR CHOICE{
ssb SEQUENCE {
ssb 1 NR Cell Beam#1
ra-PreambleIndex 56 (0..63)
}
}
ssb-perRACH-Occasion one
ra-ssb-OccasionMaskIndex 0
recoverySearchSpaceID 4
ra-Prioritization Not Present
beamFailureRecoveryTimer ms200
}
Table 7.1.1.1.4.3.3-20: BeamFailureRecoveryConfig_CSIRS (Table 7.1.1.1.4.3.3-18: BWP-

UplinkDedicated)

BeamFailureRecoveryConfig ::= SEQUENCE {
rootSequenceIndex-BFR 0 See TS 38.508-1
[4] clause 4.4.2,
Table 4.4.2-2
rach-ConfigBFR RACH-ConfigGeneric 38.508-1 [4] Table
4.6.3-130
rsrp-ThresholdSSB 57(-99dBm)
candidateBeamRSList SEQUENCE
(SIZE(1..maxNrofCandidateBeams)) OF PRACH-
ResourceDedicatedBFR CHOICE{
csi-RS SEQUENCE {
csi-RS 0
ra-OccasionList SEQUENCE (SIZE(1..maxRA- 1 entry
OccasionsPerCSIRS)) OF INTEGER (0..maxRA-
Occasions-1) {
INTEGER[1] 0 entry 1
NR Cell Beam#0
}
ra-PreambleIndex 59
}
}
ssb-perRACH-Occasion Not Present
ra-ssb-OccasionMaskIndex Not Present
recoverySearchSpaceID 4
ra-Prioritization Not Present
beamFailureRecoveryTimer ms200
}
ETSI
Table 7.1.1.1.4.3.3-21: PUCCH-Config (Table 7.1.1.1.4.3.3-18: BWP-UplinkDedicated)

pucch-Config::= SEQUENCE {
pucch-PowerControl SEQUENCE {
pathlossReferenceRSs SEQUENCE (SIZE 1 entry
(1..maxNrofPUCCH-PathlossReferenceRSs)) OF
PUCCH-PathlossReferenceRS {
PUCCH-PathlossReferenceRS[1] SEQUENCE { entry 1
ssb-Index 1 Step1,
Step17
0 Step8
}
}
}
}
}
Table 7.1.1.1.4.3.3-22: PUSCH-Config (Table 7.1.1.1.4.3.3-18: BWP-UplinkDedicated)

pusch-Config::= SEQUENCE {
pusch-PowerControl SEQUENCE {
pathlossReferenceRSToAddModList SEQUENCE 1 entry
(SIZE (1..maxNrofPUSCH-PathlossReferenceRSs))
OF PUSCH-PathlossReferenceRS {
PUSCH-PathlossReferenceRS[1] SEQUENCE { entry 1
referenceSignal CHOICE{
ssb-Index 1 Step1,
Step17
0 Step8
}
}
}
}
}
7.1.1.1.5 Random access procedure / Successful / Supplementary Uplink
(1)
with { UE in RRC_CONNECTED state with supplementary uplink configured and RACH procedure is
triggered }
ensure that {
when { RSRP of the downlink pathloss reference is less than rsrp-ThresholdSSB-SUL }
then { UE performs the Random Access Procedure on the Supplementary Uplink carrier }
}
References: The conformance requirements covered in the present TC are specified in TS 38.321: clause 5.1.1 and
clause 5.16. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.1.1]
The Random Access procedure described in this clause is initiated by a PDCCH order, by the MAC entity itself, or by
RRC for the events in accordance with TS 38.300 [2]. There is only one Random Access procedure ongoing at any
ETSI
point in time in a MAC entity. The Random Access procedure on an SCell shall only be initiated by a PDCCH order
with ra-PreambleIndex different from 0b000000.
NOTE 1: If a new Random Access procedure is triggered while another is already ongoing in the MAC entity, it is
up to UE implementation whether to continue with the ongoing procedure or start with the new procedure
(e.g. for SI request).
RRC configures the following parameters for the Random Access procedure:
- prach-ConfigurationIndex: the available set of PRACH occasions for the transmission of the Random Access
Preamble;
- preambleReceivedTargetPower: initial Random Access Preamble power;
- rsrp-ThresholdSSB: an RSRP threshold for the selection of the SSB. If the Random Access procedure is initiated
for beam failure recovery, rsrp-ThresholdSSB used for the selection of the SSB within candidateBeamRSList
refers to rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE;
- rsrp-ThresholdCSI-RS: an RSRP threshold for the selection of CSI-RS. If the Random Access procedure is
initiated for beam failure recovery, rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in
BeamFailureRecoveryConfig IE;
- rsrp-ThresholdSSB-SUL: an RSRP threshold for the selection between the NUL carrier and the SUL carrier;
- candidateBeamRSList: a list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for
recovery and the associated Random Access parameters;
- recoverySearchSpaceId: the search space identity for monitoring the response of the beam failure recovery
request;
- powerRampingStep: the power-ramping factor;
- powerRampingStepHighPriority: the power-ramping factor in case of prioritized Random Access procedure;
- scalingFactorBI: a scaling factor for prioritized Random Access procedure;
- ra-PreambleIndex: Random Access Preamble;
- ra-ssb-OccasionMaskIndex: defines PRACH occasion(s) associated with an SSB in which the MAC entity may
transmit a Random Access Preamble (see clause 7.4);
- ra-OccasionList: defines PRACH occasion(s) associated with a CSI-RS in which the MAC entity may transmit a
Random Access Preamble;
- ra-PreambleStartIndex: the starting index of Random Access Preamble(s) for on-demand SI request;
- preambleTransMax: the maximum number of Random Access Preamble transmission;
- ssb-perRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH

occasion and the number of contention-based Random Access Preambles mapped to each SSB;
- if groupBconfigured is configured, then Random Access Preambles group B is configured.
- Amongst the contention-based Random Access Preambles associated with an SSB (as defined in TS 38.213
[6]), the first numberOfRA-PreamblesGroupA Random Access Preambles belong to Random Access
Preambles group A. The remaining Random Access Preambles associated with the SSB belong to Random
Access Preambles group B (if configured).
NOTE 2: If Random Access Preambles group B is supported by the cell Random Access Preambles group B is
included for each SSB.
- if Random Access Preambles group B is configured:
- ra-Msg3SizeGroupA: the threshold to determine the groups of Random Access Preambles;
- msg3-DeltaPreamble: ∆PREAMBLE_Msg3 in TS 38.213 [6];
ETSI
- messagePowerOffsetGroupB: the power offset for preamble selection;
- numberOfRA-PreamblesGroupA: defines the number of Random Access Preambles in Random Access

Preamble group A for each SSB.
- the set of Random Access Preambles and/or PRACH occasions for SI request, if any;
- the set of Random Access Preambles and/or PRACH occasions for beam failure recovery request, if any;
- the set of Random Access Preambles and/or PRACH occasions for reconfiguration with sync, if any;
- ra-ResponseWindow: the time window to monitor RA response(s) (SpCell only);
- ra-ContentionResolutionTimer: the Contention Resolution Timer (SpCell only).
In addition, the following information for related Serving Cell is assumed to be available for UEs:
- if Random Access Preambles group B is configured:
- if the Serving Cell for the Random Access procedure is configured with supplementary uplink as specified in
TS 38.331 [5], and SUL carrier is selected for performing Random Access Procedure:
- PCMAX,f,c of the SUL carrier as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16].
- else:
- PCMAX,f,c of the NUL carrier as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16].
The following UE variables are used for the Random Access procedure:
- PREAMBLE_INDEX;
- PREAMBLE_TRANSMISSION_COUNTER;
- PREAMBLE_POWER_RAMPING_COUNTER;
- PREAMBLE_POWER_RAMPING_STEP;
- PREAMBLE_RECEIVED_TARGET_POWER;
- PREAMBLE_BACKOFF;
- PCMAX;
- SCALING_FACTOR_BI;
- TEMPORARY_C-RNTI.
When the Random Access procedure is initiated on a Serving Cell, the MAC entity shall:
1> flush the Msg3 buffer;
1> set the PREAMBLE_TRANSMISSION_COUNTER to 1;
1> set the PREAMBLE_POWER_RAMPING_COUNTER to 1;
1> set the PREAMBLE_BACKOFF to 0 ms;
1> if the carrier to use for the Random Access procedure is explicitly signalled:
2> select the signalled carrier for performing Random Access procedure;
2> set the PCMAX to PCMAX,f,c of the signalled carrier.
1> else if the carrier to use for the Random Access procedure is not explicitly signalled; and
1> if the Serving Cell for the Random Access procedure is configured with supplementary uplink as specified in TS
38.331 [5]; and
ETSI
1> if the RSRP of the downlink pathloss reference is less than rsrp-ThresholdSSB-SUL:
2> select the SUL carrier for performing Random Access procedure;
2> set the PCMAX to PCMAX,f,c of the SUL carrier.
1> else:
2> select the NUL carrier for performing Random Access procedure;
2> set the PCMAX to PCMAX,f,c of the NUL carrier.
1> perform the BWP operation as specified in clause 5.15;
1> set PREAMBLE_POWER_RAMPING_STEP to
powerRampingStep;1> set SCALING_FACTOR_BI to 1;
1> if the Random Access procedure was initiated for beam failure recovery (as specified in clause 5.17); and
1> if beamFailureRecoveryConfig is configured for the active UL BWP of the selected carrier:
2> start the beamFailureRecoveryTimer, if configured;
2> apply the parameters powerRampingStep, preambleReceivedTargetPower, and preambleTransMax

configured in the beamFailureRecoveryConfig;
2> if powerRampingStepHighPriority is configured in the beamFailureRecoveryConfig:
3> set PREAMBLE_POWER_RAMPING_STEP to the powerRampingStepHighPriority.
2> else:
3> set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep.
2> if scalingFactorBI is configured in the beamFailureRecoveryConfig:
3> set SCALING_FACTOR_BI to the scalingFactorBI.
1> else if the Random Access procedure was initiated for handover; and
1> if rach-ConfigDedicated is configured for the selected carrier:
2> if powerRampingStepHighPriority is configured in the rach-ConfigDedicated:
3> set PREAMBLE_POWER_RAMPING_STEP to the powerRampingStepHighPriority.
2> if scalingFactorBI is configured in the rach-ConfigDedicated:
3> set SCALING_FACTOR_BI to the scalingFactorBI.
1> perform the Random Access Resource selection procedure (see clause 5.1.2).
[TS 38.321, clause 5.16]
The Supplementary UL (SUL) carrier can be configured as a complement to the normal UL (NUL) carrier. Switching
between the NUL carrier and the SUL carrier means that the UL transmissions move from one carrier to the other
carrier, which is done by:
- an indication in DCI;
- the Random Access procedure as specified in clause 5.1.1.
If the MAC entity receives a UL grant indicating an SUL switch while a Random Access procedure is ongoing, the
MAC entity shall ignore the UL grant.
The Serving Cell configured with supplementaryUplink belongs to a single TAG.
ETSI
Same Pre-test conditions as in clause 7.1.1.0 except that supplementary uplink (SUL) carrier is configured on NR Cell
33.
Table 7.1.1.1.5.3.2-1 illustrates the downlink power levels to be applied for the NR cells at various time instants of the
test execution. Row marked "T0" denotes the initial conditions, while row marked "T1" are to be applied subsequently.
Table 7.1.1.1.5.3.2-1: Time instances of cell power level changes

NR Cell 1 NR Cell 33
Parameter Unit Remark
(NUL) (SUL)
NR Cell1 Power level
SS/PBCH
T0 dBm/SCS -75 N/A is higher than rsrp-
SSS EPRE
ThresholdSSB-SUL.
NR Cell1 Power level
SS/PBCH
T1 dBm/SCS -85 N/A is lower than rsrp-
SSS EPRE
ThresholdSSB-SUL.

U-S Message
1 The SS ignores scheduling requests and does - - -
not allocate any uplink grant
2 The SS transmits a MAC PDU containing a <-- MAC PDU - -
PDCP SDU on NR Cell 1.
3 The SS changes NR Cell 1’s power level - - - -
1. (Note 1)
4 Void. - - - -
5 Check: Does the UE initiate the random --> PRACH Preamble 1 P
access procedure on SUL carrier on NR Cell
33?
with an UL Grant of 56-bits on NR Cell 1 and
RAPID corresponding to the transmitted
preamble in step 5. (Note 2)
7 Check: Does the UE send a msg3 using the --> Msg3 (C-RNTI MAC CE) 1 P
grant associated to the Random Access
Response received in Step 6 on SUL carrier
on NR Cell 33?
8 The SS schedules PDCCH transmission on <-- Contention Resolution - -
NR Cell 1 for UE C-RNTI with uplink grant’s
UL/SUL indicator set to 1.
C-RNTI containing looped back PDCP SDU on
SUL carrier on NR Cell 33?
Note 1: Reduce the NR Cell 1 SS/PBCH EPRE level to ensure that RSRP of the downlink pathloss reference is lower
than rsrp-ThresholdSSB-SUL, while UE is still able to receive msg2 and msg4 correctly.
Note 2: UL grant of 56 bits is to make UE not send any loopback data in uplink with msg3, according to TS 38.321
[18] clause 5.4.3.1.
ETSI
Table 7.1.1.1.5.3.3-1: SIB1 of NR Cell 1 (preamble and all steps, Table 7.1.1.1.5.3.2-2)

SIB1::= SEQUENCE {
servingCellConfigCommon ServingCellConfigCommonSIB
}
Table 7.1.1.1.5.3.3-2: ServingCellConfigCommonSIB (Table 7.1.1.1.5.3.3-1)

ServingCellConfigCommonSIB ::=
SEQUENCE {
supplementaryUplink SEQUENCE {
}
}

BWP-UplinkCommon::= SEQUENCE {
}
}

rsrp-ThresholdSSB-SUL 76 IE value 76 means -80dBm SUL
}
Table 7.1.1.1.5.3.3-5: DCI Format 0-1 (Step 8 of Table 7.1.1.1.5.3.2-2)
Derivation Path: TS 38.508-1 [4], Table 4.3.6.1.1.2-1

UE configured with SUL in the
UL/SUL indicator 1
cell
7.1.1.1.6 Random access procedure / Successful/ Temporary C-RNTI Based / Preamble

selected by MAC itself
(1)
with { UE in RRC Idle state has UL CCCH PDU to send and Random Access Preambles group B is
configured }
ensure that {
when { the UL CCCH MAC PDU Size is less than messageSizeGroupA }
then { UE transmits a random access preamble using a preamble in group A of random access
preambles }
}
ETSI
(2)
with { UE in RRC Idle state initiated Random Access procedure to transmit UL CCCH PDU and
transmitted MSG3 }
ensure that {
when { The SS schedules any PDCCH transmission addressed to UE Temporary C-RNTI before Contention
resolution timer expiry with MAC PDU does not contain a matching UE Contention Resolution Identity
MAC CE }
then {UE re 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)
transmitted MSG3 }
ensure that {
when { The SS does not schedule any PDCCH transmission addressed to UE Temporary C-RNTI before
Contention resolution timer expiry }
then {UE re 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)
transmitted MSG3 }
ensure that {
when { The SS schedules a PDCCH transmission addressed to UE Temporary C-RNTI before Contention
resolution timer expiry }
then {UE assumes RACH procedure as complete }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38,321, clause 5.1.2,
5.1.3, 5.1.4, 5.1.5, 5.2, 6.1.3.2, 6.1.5 and 6.2.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.1.2]
available:

which is quasi-colocated with the selected CSI-RS as specified in TS 38.214 [7].
2> else:
ETSI
1> else if the contention-free Random Access Resources associated with SSBs have been explicitly provided in
rach-ConfigDedicated and at least one SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated
SSBs is available:
1> else if the contention-free Random Access Resources associated with CSI-RSs have been explicitly provided in
rach-ConfigDedicated and at least one CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the
associated CSI-RSs is available:
1> else if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]); and
1> if the Random Access Resources for SI request have been explicitly provided by RRC:
2> else:
3> select any SSB.
2> select a Random Access Preamble corresponding to the selected SSB, from the Random Access Preamble(s)
determined according to ra-PreambleStartIndex as specified in TS 38.331 [5];
2> set the PREAMBLE_INDEX to selected Random Access Preamble.
2> else:
3> select any SSB.
4> else:
3> else:
ETSI
> select a Random Access Preamble3 randomly with equal probability from the Random Access Preambles
> else:
11> ifthe Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]); and
restrictions given by the ra-ssb-OccasionMaskIndex if configured (the MAC entity shall select a PRACH
occasion randomly with equal probability amongst the consecutive PRACH occasions according to subclause
8.1 of TS 38.213 [6] corresponding to the selected SSB).
> else if an SSB is selected above:
SSB permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured or indicated by
PDCCH (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the
consecutive PRACH occasions according to subclause 8.1 of TS 38.213 [6], corresponding to the selected
SSB; the MAC entity may take into account the possible occurrence of measurement gaps when determining
the next available PRACH occasion corresponding to the selected SSB).
given by the ra-ssb-OccasionMaskIndex if configured, corresponding to the SSB in
candidateBeamRSList which is quasi-colocated with the selected CSI-RS as specified in TS 38.214 [7]
(the MAC entity shall select a PRACH occasion randomly with equal probability amongst the
consecutive PRACH occasions according to subclause 8.1 of TS 38.213 [6], corresponding to the SSB
which is quasi-colocated with the selected CSI-RS; the MAC entity may take into account the possible
occurrence of measurement gaps when determining the next available PRACH occasion corresponding to
the SSB which is quasi-colocated with the selected CSI-RS).
2> else:
CSI-RS).
1> else if Random Access procedure was initiated for beam failure recovery; and
1> if a CSI-RS is selected above and there is no contention-free Random Access Resource associated with the
selected CSI-RS:
which is quasi-collocated with the selected CSI-RS as specified in TS 38.214 [7] (the MAC entity may take
occasion corresponding to the SSB which is quasi-collected with the selected CSI-RS).
ETSI
1> else:
2> determine the next available PRACH occasion (the MAC entity shall select a PRACH occasion randomly
with equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers;
next available PRACH occasion).
NOTE: When the UE determines if there is an SSB with SS-RSRP above rsrp-ThresholdSSB or a CSI-RS with
CSI-RSRP above rsrp-ThresholdCSI-RS, the UE uses the latest unfiltered L1-RSRP measurement.
[TS 38.321, clause 5.1.3]
1> if SSB or CSI-RS selected is not changed from the selection in the last Random Access Preamble transmission:

1> instruct the physical layer to transmit the Random Access Preamble using the selected PRACH occasion,
corresponding RA-RNTI (if available), PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER.
The RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, is computed
as:
where s_id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id < 14), t_id is the index of the first
slot of the PRACH occasion in a system frame (0 ≤ t_id < 80), f_id is the index of the PRACH occasion in the
frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random Access Preamble transmission (0
for NUL carrier, and 1 for SUL carrier).
[TS 38.321, clause 5.1.4]
MAC entity shall:
entity:
2> monitor for a PDCCH transmission on the search space indicated by recoverySearchSpaceId of the SpCell
identified by the C-RNTI while ra-ResponseWindow is running.
1> else:
ETSI
1> if notification of a reception of a PDCCH transmission on the search space indicated by recoverySearchSpaceId
is received from lower layers on the Serving Cell where the preamble was transmitted; and
entity:
2> else:
3> else:
5> else:
4> else:
procedure:
ETSI
Msg3 buffer.
NOTE: If within a Random Access procedure, an uplink grant provided in the Random Access Response for the
same group of contention-based Random Access Preambles has a different size than the first uplink grant
allocated during that Random Access procedure, the UE behavior is not defined.
1> if ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if a PDCCH transmission on the

search space indicated by recoverySearchSpaceId addressed to the C-RNTI has not been received on the Serving
Cell where the preamble was transmitted; or
> if ra-ResponseWindow configured in RACH-ConfigCommon expires, and if the Random Access Response
received1:
PREAMBLE_BACKOFF;
3> else:
time.
HARQ operation is not applicable to the Random Access Response reception.
[TS 38.321, clause 5.1.5]
Once Msg3 is transmitted, the MAC entity shall:
a measurement gap;
ETSI
3> if the Random Access procedure was initiated for beam failure recovery (as specified in subclause 5.17)
and the PDCCH transmission is addressed to the C-RNTI; or
PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new transmission; or
addressed to the C-RNT:I
> if the Random Access procedure was initiated for beam failure recovery (as specified in subclause 5.17)
and the PDCCH transmission is addressed to the C-RNTI:
2> else if the CCCH SDU was included in Msg3 and the PDCCH transmission is addressed to its
TEMPORARY_C-RNTI:
3> if the MAC PDU is successfully decoded:
4> if the MAC PDU contains a UE Contention Resolution Identity MAC CE; and
4> if the UE Contention Resolution Identity in the MAC CE matches the CCCH SDU transmitted in
Msg3:
5> consider this Contention Resolution successful and finish the disassembly and demultiplexing of
the MAC PDU;
5> if this Random Access procedure was initiated for SI request:
5> else:
6> set the C-RNTI to the value of the TEMPORARY_C-RNTI;
4> else:
5> consider this Contention Resolution not successful and discard the successfully decoded MAC
PDU.
ETSI
PREAMBLE_BACKOFF;
3> else:
time.
[TS 38.321, clause 5.2]
1> when a Timing Advance Command MAC CE is received, and if an NTA (as defined in TS 38.211 [8]) has been
1> when a Timing Advance Command is received in a Random Access Response message for a Serving Cell
belonging to a TAG:
2> if the Random Access Preamble was not selected by the MAC entity among the contention-based Random
Access Preamble:
3> apply the Timing Advance Command for this TAG;
3> start or restart the timeAlignmentTimer associated with this TAG.
2> else if the timeAlignmentTimer associated with this TAG is not running:
3> start the timeAlignmentTimer associated with this TAG;
3> when the Contention Resolution is considered not successful as described in subclause 5.1.5; or
3> when the Contention Resolution is considered successful for SI request as described in subclause 5.1.5,
after transmitting HARQ feedback for MAC PDU including UE Contention Resolution Identity MAC
CE:
4> stop timeAlignmentTimer associated with this TAG.
2> else:
3> ignore the received Timing Advance Command.
ETSI
SCell as expired.
The MAC entity shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble
transmission when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not running.
Furthermore, when the timeAlignmentTimer associated with the PTAG is not running, the MAC entity shall not perform
any uplink transmission on any Serving Cell except the Random Access Preamble transmission on the SpCell.
[TS 38.321, clause 6.1.3.2]
The C-RNTI MAC CE is identified by MAC PDU subheader with LCID as specified in Table 6.2.1-2.
It has a fixed size and consists of a single field defined as follows (Figure 6.1.3.2-1):
- C-RNTI: This field contains the C-RNTI of the MAC entity. The length of the field is 16 bits.
C-RNTI Oct 1
C-RNTI Oct 2
Figure 6.1.3.2-1: C-RNTI MAC CE
[TS 38.321, clause 6.1.5]
following:
ETSI
E T R R BI Oct 1
E T RAPID Oct 1

MAC RAR
MAC subPDU 1
(BI only)
MAC subPDU 2
(RAPID only)
MAC subPDU 3
(RAPID and RAR)
[TS 38.321, clause 6.2.3]
The MAC RAR is of fixed size as depicted in Figure 6.2.3-1, and consists of the following fields:
- Timing Advance Command: The Timing Advance Command field indicates the index value TA used to control
the amount of timing adjustment that the MAC entity has to apply in TS 38.213 [6]. The size of the Timing
Advance Command field is 12 bits;
- UL Grant: The Uplink Grant field indicates the resources to be used on the uplink in TS 38.213 [6]. The size of
the UL Grant field is 27 bits;
- Temporary C-RNTI: The Temporary C-RNTI field indicates the temporary identity that is used by the MAC
entity during Random Access. The size of the Temporary C-RNTI field is 16 bits.
ETSI
The MAC RAR is octet aligned.
R Timing Advance Command Oct 1
Timing Advance Command UL Grant Oct 2
UL Grant Oct 3
UL Grant Oct 4
UL Grant Oct 5
Temporary C-RNTI Oct 6
Temporary C-RNTI Oct 7
Figure 6.2.3-1: MAC RAR
ETSI
Same Pre-test conditions as in clause 7.1.1.0 except that Test loop function(Off).7.1.1.1.6.3.2 Test
procedure sequence

U-S Message
1 The SS transmits a Paging message including <-- Paging - -
a matched UE identity.
PRACH using a preamble in group A defined
in servingCellConfigCommon in SIB1
(totalNumberOfRA-Preambles, ssb-perRACH-
OccasionAndCB-PreamblesPerSSB and
numberOfRA-PreamblesGroupA)?
with RAPID corresponding to the transmitted
Preamble in step 2, including TC-RNTI and not
including Back off Indicator subheader.
4 The UE transmits a MAC PDU containing an --> MAC PDU (RRCSetupRequest) - -
RRCSetupRequest message. (Note 1)
5 Before the contention resolution timer expires,
the SS does not schedule any PDCCH.
PRACH using a preamble in the same group
A?
Preamble in step 6, including TC-RNTI and not
including Back off Indicator subheader.
9 The SS schedules PDCCH transmission <-- MAC PDU - -
addressed to TC-RNTI to transmit a valid MAC (RRCSetup)
PDU containing an RRCSetup message, but
not including a matching ‘UE Contention
Resolution Identity’ MAC control element.
- EXCEPTION: In parallel with step 10, the - - - -
parallel behaviour in table 7.1.1.1.6.3.2-2 is
running.
PRACH using a preamble in the same group
A?
11 The SS transmits Random Access Response <-- Random Access Response -
Preamble in step 10, including TC-RNTI and
not including Back off Indicator subheader.
13 The SS schedules PDCCH transmission <-- MAC PDU - -
addressed to TC-RNTI to transmit a valid MAC (RRCSetup and UE Contention
PDU containing an RRCSetup message and Resolution Identity MAC CE)
‘UE Contention Resolution Identity’ MAC
control element with matched ‘Contention
Resolution Identity’.
14 Check: Does UE transmit a MAC PDU --> MAC PDU (RRCSetupComplete) 4 P
containing an RRCSetupComplete message
indicating acceptance of RRCSetup message?
Note 1: Size of RRCSetupRequest message is 45 bits, octet aligned = 48 bits. With 16 bits of MAC Header the
minimum size of MAC PDU carrying RRCSetupRequest is 64 bits.
ETSI

U-S Message
1 Check: UE transmits a MAC PDU containing --> MAC PDU (RRCSetupComplete) 2 F
an RRCSetupComplete message indicating
acceptance of RRCSetup message?
Table 7.1.1.1.6.3.3-1: SIB1 (Preamble, Table 7.1.1.1.6.3.2-1)

SIB1 ::= SEQUENCE {
servingCellConfigCommon SEQUENCE {
}
}
}

}
}

totalNumberOfRA-Preambles 42
ssb-perRACH-OccasionAndCB-PreamblesPerSSB
CHOICE {
One n32
}
groupBconfigured SEQUENCE {
ra-Msg3SizeGroupA b208
}
ra-ContentionResolutionTimer sf48
}
7.1.1.1.7 Random access procedure / Successful/ Temporary C-RNTI Based / Preamble

selected by MAC itself
(1)
with { UE in RRC_Connected and NR SpCell TimeAlignmentTimer expired, and has UL Data to send }
ensure that {
ETSI
when { the BWP selected for Random Access procedure is configured with both 2-step and 4-step RA
type Random Access Resources and the RSRP of the downlink pathloss reference is above msgA-RSRP-
Threshold }
then { UE SET RA_TYPE to 2-step AND sends a MSGA on the NR SpCell }
}
(2)
with { UE in RRC_Connected NR SpCell TimeAlignmentTimer expired, and has UL Data to send }
ensure that {
when { BWP selected for Random Access procedure is only configured with 2-step RA type Random
Access resources }
then { UE SET RA_TYPE to 2-step AND sends a MSGA on the NR SpCell }
}
5.1.2a and 5.1.3a . Unless otherwise stated these are Rel-16 requirements.
[TS 38.321, clause 5.1.1]
1> if the Random Access procedure was initiated for SpCell beam failure recovery (as specified in clause 5.17) and
if the contention-free Random Access Resources for beam failure recovery request for 4-step RA type have been
explicitly provided by RRC for the BWP selected for Random Access procedure; or
1> if the Random Access procedure was initiated for reconfiguration with sync and if the contention-free Random
Access Resources for 4-step RA type have been explicitly provided in rach-ConfigDedicated for the BWP
selected for Random Access procedure:
2> set the RA_TYPE to 4-stepRA.
1> else if the BWP selected for Random Access procedure is configured with both 2-step and 4-step RA type
Random Access Resources and the RSRP of the downlink pathloss reference is above msgA-RSRP-Threshold; or
1> if the BWP selected for Random Access procedure is only configured with 2-step RA type Random Access
resources (i.e. no 4-step RACH RA type resources configured); or
1> else:
1> perform initialization of variables specific to Random Access type as specified in clause 5.1.1a;
1> if RA_TYPE is set to 2-stepRA:
2> perform the Random Access Resource selection procedure for 2-step RA type (see clause 5.1.2a).
1> else:
[TS 38.321, clause 5.1.2a]
If the selected RA_TYPE is set to 2-stepRA, the MAC entity shall:
1> if the contention-free 2-step RA type Resources associated with SSBs have been explicitly provided in rach-
ConfigDedicated and at least one SSB with SS-RSRP above msgA-RSRP-ThresholdSSB amongst the associated
SSBs is available:
2> select an SSB with SS-RSRP above msgA-RSRP-ThresholdSSB amongst the associated SSBs;
ETSI
1> else (i.e. for the contention-based Random Access Preamble selection):
2> if at least one of the SSBs with SS-RSRP above msgA-RSRP-ThresholdSSB is available:
3> select an SSB with SS-RSRP above msgA-RSRP-ThresholdSSB.
2> else:
3> select any SSB.
2> if contention-free Random Access Resources for 2-step RA type have not been configured and if Random
Access Preambles group has not yet been selected during the current Random Access procedure:
3> if Random Access Preambles group B for 2-step RA type is configured:
4> if the potential MSGA payload size (UL data available for transmission plus MAC subheader and,
where required, MAC CEs) is greater than the ra-MsgA-SizeGroupA and the pathloss is less than
PCMAX (of the Serving Cell performing the Random Access Procedure) – msgA-
PreambleReceivedTargetPower – msgA-DeltaPreamble – messagePowerOffsetGroupB; or
plus MAC subheader is greater than ra-MsgA-SizeGroupA:
4> else:
3> else:
2> else if contention-free Random Access Resources for 2-step RA type have been configured and if Random
3> if Random Access Preambles group B for 2-step RA type is configured; and
3> if the transport block size of the MSGA payload configured in the rach-ConfigDedicated corresponds to
the transport block size of the MSGA payload associated with Random Access Preambles group B:
3> else:
2> else (i.e. Random Access preambles group has been selected during the current Random Access procedure):
transmission attempt corresponding to the earlier transmission of MSGA.
2> select a Random Access Preamble randomly with equal probability from the 2-step RA type Random Access
Preambles associated with the selected SSB and the selected Random Access Preambles group;
1> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB
permitted by the restrictions given by the msgA-SSB-SharedRO-MaskIndex if configured and ra-ssb-
OccasionMaskIndex if configured (the MAC entity shall select a PRACH occasion randomly with equal
probability among the consecutive PRACH occasions allocated for 2-step RA type according to clause 8.1 of TS
38.213 [6], corresponding to the selected SSB; the MAC entity may take into account the possible occurrence of
measurement gaps when determining the next available PRACH occasion corresponding to the selected SSB);
ETSI
Access Preamble(s):
2> select a PUSCH occasion from the PUSCH occasions configured in msgA-CFRA-PUSCH corresponding to
the PRACH slot of the selected PRACH occasion, according to msgA-PUSCH-resource-Index corresponding
to the selected SSB;
2> determine the UL grant and the associated HARQ information for the MSGA payload in the selected PUSCH
occasion;
2> deliver the UL grant and the associated HARQ information to the HARQ entity.
1> else:
2> select a PUSCH occasion corresponding to the selected preamble and PRACH occasion according to clause
8.1A of TS 38.213 [6];
2> determine the UL grant for the MSGA payload according to the PUSCH configuration associated with the
selected Random Access Preambles group and determine the associated HARQ information;
2> if the selected preamble and PRACH occasion is mapped to a valid PUSCH occasion as specified in clause
8.1A of TS 38.213 [6]:
1> perform the MSGA transmission procedure (see clause 5.1.3a).
NOTE: To determine if there is an SSB with SS-RSRP above msgA-RSRP-ThresholdSSB, the UE uses the latest
unfiltered L1-RSRP measurement.
[TS 38.321, clause 5.1.3a]
The MAC entity shall, for each MSGA:
1> if LBT failure indication was not received from lower layers for the last MSGA Random Access Preamble
transmission; and
1> if SSB selected is not changed from the selection in the last Random Access Preamble transmission:
1> select the value of DELTA_PREAMBLE according to clause 7.3;
1> set PREAMBLE_RECEIVED_TARGET_POWER to msgA-PreambleReceivedTargetPower +

DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER – 1) ×
PREAMBLE_POWER_RAMPING_STEP;
1> if this is the first MSGA transmission within this Random Access procedure:
3> indicate to the Multiplexing and assembly entity to include a C-RNTI MAC CE in the subsequent uplink
transmission.
2> if the Random Access procedure was initiated for SpCell beam failure recovery and spCell-BFR-CBRA with
value true is configured:
3> indicate to the Multiplexing and assembly entity to include a BFR MAC CE or a Truncated BFR MAC
CE in the subsequent uplink transmission.
2> obtain the MAC PDU to transmit from the Multiplexing and assembly entity according to the HARQ
information determined for the MSGA payload (see clause 5.1.2a) and store it in the MSGA buffer.
ETSI
1> compute the MSGB-RNTI associated with the PRACH occasion in which the Random Access Preamble is
transmitted;
1> instruct the physical layer to transmit the MSGA using the selected PRACH occasion and the associated PUSCH
resource of MSGA (if the selected preamble and PRACH occasion is mapped to a valid PUSCH occasion), using
the corresponding RA-RNTI, MSGB-RNTI, PREAMBLE_INDEX,
PREAMBLE_RECEIVED_TARGET_POWER, msgA-PreambleReceivedTargetPower, and the amount of power
ramping applied to the latest MSGA preamble transmission (i.e. (PREAMBLE_POWER_RAMPING_COUNTER
– 1) × PREAMBLE_POWER_RAMPING_STEP);
ETSI

U-S Message
to configure both 2-Step and 4-Step RA type
Random Access Resources. Note 1
2
SDU
4 Check: Does the UE MSGA using the selected --> MAC PDU (including C-RNTI MAC 1 P
PRACH occasion and the associated PUSCH CE)
resource of MSGA
5 SS schedules PDCCH transmission for UE <-- MAC PDU(Absolute Timing - -
C_RNTI and DL MAC PDU containing Advance
Absolute Timing Advance Command MAC CE. Command MAC Control Element)
6 SS transmits an RRCReconfiguration message <-- RRCReconfiguration - -
to configure only 2-Step RA type Random
Access Resources. Note 1
7 The UE transmits --> RRCReconfigurationComplete - -
2
SDU
11 Check: Does the UE MSGA using the selected --> MAC PDU (including C-RNTI MAC 2 P
resource of MSGA
FFS
ETSI
7.1.1.1.8 Correct selection of RACH parameters / 2-step RACH/MSGA and PRACH

resource explicitly signalled to the UE by RRC / contention free random access
procedure
(1)
ensure that {
when { SS sends an RRCReconfiguration message including RACH-ConfigDedicated information element
and the contention-free Random Access Resources for 2-step RA type have been explicitly provided in
rach-ConfigDedicated }
then { UE SET RA_TYPE to 2-step AND sends a MSGA on the NR PSCell }
}
(2)
with { UE in RRC_Connected state after transmission of a MSGA on NR SpCell received in RACH-
ConfigDedicated on the target cell }
ensure that {
when { UE does not receive a matching MSGB in msgB-ResponseWindow and
PREAMBLE_TRANSMISSION_COUNTER is less than msgA-TransMax + 1 }
then { UE retransmits a MSGA in RACH-ConfigDedicated on the target cell }
}
5.1.2a, 5.1.3a and 5.1.4a . Unless otherwise stated these are Rel-16 requirements.
[TS 38.321, clause 5.1.1]
1> else:
1> else:
ETSI
[TS 38.321, clause 5.1.2a]
SSBs is available:
2> else:
3> select any SSB.
4> else:
3> else:
3> else:
ETSI
Access Preamble(s):
occasion;
1> else:
8.1A of TS 38.213 [6];
8.1A of TS 38.213 [6]:
[TS 38.321, clause 5.1.3a]
transmission; and

transmission.
ETSI
transmitted;
[TS 38.321, clause 5.1.4a]
Once the MSGA preamble is transmitted, regardless of the possible occurrence of a measurement gap, the MAC entity
shall:
1> start the msgB-ResponseWindow at the PDCCH occasion as specified in TS 38.213 [6], clause 8.2A;
1> monitor the PDCCH of the SpCell for a Random Access Response identified by MSGB-RNTI while the msgB-
ResponseWindow is running;
1> if C-RNTI MAC CE was included in the MSGA:
2> monitor the PDCCH of the SpCell for Random Access Response identified by the C-RNTI while the msgB-
2> if the C-RNTI MAC CE was included in MSGA:
3> if the Random Access procedure was initiated for SpCell beam failure recovery (as specified in clause
5.17) and the PDCCH transmission is addressed to the C-RNTI:
4> consider this Random Access Response reception successful;
4> stop the msgB-ResponseWindow;
3> else if the timeAlignmentTimer associated with the PTAG is running:
4> if the PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new
transmission:
3> else:
4> if a downlink assignment has been received on the PDCCH for the C-RNTI and the received TB is
5> if the MAC PDU contains the Absolute Timing Advance Command MAC CE:
ETSI
6> consider this Random Access procedure successfully completed and finish the disassembly and
demultiplexing of the MAC PDU.
2> if a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the
MSGB-RNTI and the received TB is successfully decoded:
3> if the MSGB contains a MAC subPDU with Backoff Indicator:
3> else:
3> if the MSGB contains a fallbackRAR MAC subPDU; and
3> if the Random Access Preamble identifier in the MAC subPDU matches the transmitted
PREAMBLE_INDEX (see clause 5.1.3a):
4> apply the following actions for the SpCell:
5> indicate the msgA-PreambleReceivedTargetPower and the amount of power ramping applied to
the latest Random Access Preamble transmission to lower layers (i.e.
6> consider the Random Access procedure successfully completed;
5> else:
6> if the Msg3 buffer is empty:
7> obtain the MAC PDU to transmit from the MSGA buffer and store it in the Msg3 buffer;
6> process the received UL grant value and indicate it to the lower layers and proceed with Msg3
transmission.
NOTE: If within a 2-step RA type procedure, an uplink grant provided in the fallback RAR has a different size
than the MSGA payload, the UE behaviour is not defined.
3> else if the MSGB contains a successRAR MAC subPDU; and
3> if the CCCH SDU was included in the MSGA and the UE Contention Resolution Identity in the MAC
subPDU matches the CCCH SDU:
4> stop msgB-ResponseWindow;
4> else:
ETSI
5> set the C-RNTI to the value received in the successRAR;
6> indicate the msgA-PreambleReceivedTargetPower and the amount of power ramping applied
to the latest Random Access Preamble transmission to lower layers (i.e.
(PREAMBLE_POWER_RAMPING_COUNTER – 1) ×
PREAMBLE_POWER_RAMPING_STEP).
4> deliver the TPC, PUCCH resource Indicator, ChannelAccess-CPext (if indicated), and HARQ
feedback Timing Indicator received in successRAR to lower layers.
4> finish the disassembly and demultiplexing of the MAC PDU.
1> if msgB-ResponseWindow expires, and the Random Access Response Reception has not been considered as
successful based on descriptions above:
4> consider this Random Access procedure unsuccessfully completed.
3> if msgA-TransMax is applied (see clause 5.1.1a) and PREAMBLE_TRANSMISSION_COUNTER = msgA-

TransMax + 1:
4> set the RA_TYPE to 4-stepRA;
4> flush HARQ buffer used for the transmission of MAC PDU in the MSGA buffer;
4> discard explicitly signalled contention-free 2-step RA type Random Access Resources, if any;
4> perform the Random Access Resource selection procedure as specified in clause 5.1.2.
3> else:
PREAMBLE_BACKOFF;
4> if the criteria (as defined in clause 5.1.2a) to select contention-free Random Access Resources is met
5> perform the Random Access Resource selection procedure for 2-step RA type Random Access
(see clause 5.1.2a).
4> else:
(see clause 5.1.2a) after the backoff time.
ETSI
Upon receiving a fallbackRAR, the MAC entity may stop msgB-ResponseWindow once the Random Access Response
reception is considered as successful.
Same Pre-test conditions as in clause 7.1.1.0 except that Test loop function(Off).

U-S Message
with reconfiguration with sync and contention-
free Random Access Resources for 2-step RA
type have been explicitly provided in rach-
ConfigDedicated. Note 1
- Exception: Steps 2 to 3 are run msgA- - - - -
TransMax times
2 The UE transmits MSGA including --> MAC PDU (including C-RNTI MAC 1,2 P
RRCReconfigurationComplete message using CE,
the Random Access Resources for 2-step RA RRCReconfigurationComplete)
type explicitly provided. Note 2
3 SS does not schedulePDCCH transmission for - - - -
UE C_RNTI until msgB-ResponseWindow
expires
4 The UE transmits MSGA including --> MAC PDU (including C-RNTI MAC 2 P
RRCReconfigurationComplete message using CE,
the Random Access Resources for 2-step RA RRCReconfigurationComplete)
type explicitly provided. Note 2
RRCConnectionReconfigurationComplete and sent in E-UTRA cell. In NR Cell a MAC PDU containing C-
RNTI MAC CE is sent.
FFS
7.1.1.1.9 Random access procedure / Successful / 2-step RACH/C-RNTI Based /

Preamble selected by MAC itself
(1)
with { UE in RRC_Connected state after NR SpCell TimeAlignmentTimer expired, and has UL Data to send
}
ensure that {
when { the UL MAC PDU Size is less than ra-MsgA-SizeGroupA }
then { UE transmits a MSGA using a preamble in group A of random access preambles }
}
(2)
with { UE in RRC_Connected state after transmission of a MSGA on NR SpCell }
ETSI
ensure that {
when { SS does not answer with a matching MSGB within msgB-ResponseWindow }
then { UE retransmits a MSGA using a preamble from same group }
}
(3)
ensure that {
when { SS sends a MSGB including a Backoff Indicator and the Random Access Preamble identifier is
different from the value received from UE }
then { UE performs the Random Access Resource selection procedure for 2-step RA type Random
Access after a random time between 0 and the indicated Backoff parameter from same group }
}
(4)
with { UE in RRC_Connected state after NR SpCell TimeAlignmentTimer expired, and has UL Data to send
}
ensure that {
when { the UL MAC PDU Size is greater than messageSizeGroupA }
then { UE transmits a MSGA using a preamble in group B of random access preambles }
}
(5)
with { UE in RRC_Connected state and having initiated a 2-step RA type Random Access procedure in NR
SpCell }
ensure that {
when { SS transmits a Timing Advance Command in a MSGB message }
then { UE applies the received Timing Advance value in the next transmitted MAC PDU }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38,321, clause 5.1.2a,
5.1.3a, 5.1.4a, 5.1.5 and 5.2. Unless otherwise stated these are Rel-16 requirements.
[TS 38.321, clause 5.1.2a]
SSBs is available:
2> else:
3> select any SSB.
ETSI
4> else:
3> else:
3> else:
Access Preamble(s):
occasion;
1> else:
8.1A of TS 38.213 [6];
8.1A of TS 38.213 [6]:
ETSI
[TS 38.321, clause 5.1.3a]
transmission; and

transmission.
transmitted;
1> if LBT failure indication is received from lower layers for the transmission of this MSGA Random Access
Preamble:
2> instruct the physical layer to cancel the transmission of the MSGA payload on the associated PUSCH
resource;
2> if lbt-FailureRecoveryConfig is configured:
2> else:
ETSI
4> if msgA-TransMax is applied (see clause 5.1.1a) and PREAMBLE_TRANSMISSION_COUNTER =

msgA-TransMax + 1:
4> else:
NOTE: The MSGA transmission includes the transmission of the PRACH Preamble as well as the contents of the
MSGA buffer in the PUSCH resource corresponding to the selected PRACH occasion and
PREAMBLE_INDEX (see TS 38.213 [6])
The MSGB-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, is
computed as:
MSGB-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id + 14 × 80 × 8 × 2
where s_id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id < 14), t_id is the index of the first
slot of the PRACH occasion in a system frame (0 ≤ t_id < 80), where the subcarrier spacing to determine t_id is based
on the value of μ specified in clause 5.3.2 in TS 38.211 [8], f_id is the index of the PRACH occasion in the frequency
domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random Access Preamble transmission (0 for NUL
carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3.
[TS 38.321, clause 5.1.4a]
shall:
1> start the msgB-ResponseWindow at the PDCCH occasion as specified in TS 38.213 [6], clause 8.2A;
1> monitor the PDCCH of the SpCell for a Random Access Response identified by MSGB-RNTI while the msgB-
ResponseWindow is running;
1> if C-RNTI MAC CE was included in the MSGA:
2> monitor the PDCCH of the SpCell for Random Access Response identified by the C-RNTI while the msgB-
2> if the C-RNTI MAC CE was included in MSGA:
5.17) and the PDCCH transmission is addressed to the C-RNTI:
ETSI
3> else if the timeAlignmentTimer associated with the PTAG is running:
4> if the PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new
transmission:
3> else:
4> if a downlink assignment has been received on the PDCCH for the C-RNTI and the received TB is
5> if the MAC PDU contains the Absolute Timing Advance Command MAC CE:
6> consider this Random Access procedure successfully completed and finish the disassembly and
demultiplexing of the MAC PDU.
2> if a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the
MSGB-RNTI and the received TB is successfully decoded:
3> if the MSGB contains a MAC subPDU with Backoff Indicator:
3> else:
3> if the MSGB contains a fallbackRAR MAC subPDU; and
3> if the Random Access Preamble identifier in the MAC subPDU matches the transmitted
PREAMBLE_INDEX (see clause 5.1.3a):
5> indicate the msgA-PreambleReceivedTargetPower and the amount of power ramping applied to
the latest Random Access Preamble transmission to lower layers (i.e.
6> consider the Random Access procedure successfully completed;
5> else:
ETSI
6> process the received UL grant value and indicate it to the lower layers and proceed with Msg3
transmission.
NOTE: If within a 2-step RA type procedure, an uplink grant provided in the fallback RAR has a different size
than the MSGA payload, the UE behaviour is not defined.
3> else if the MSGB contains a successRAR MAC subPDU; and
3> if the CCCH SDU was included in the MSGA and the UE Contention Resolution Identity in the MAC
subPDU matches the CCCH SDU:
4> stop msgB-ResponseWindow;
4> else:
5> set the C-RNTI to the value received in the successRAR;
6> indicate the msgA-PreambleReceivedTargetPower and the amount of power ramping applied
to the latest Random Access Preamble transmission to lower layers (i.e.
(PREAMBLE_POWER_RAMPING_COUNTER – 1) ×
PREAMBLE_POWER_RAMPING_STEP).
4> deliver the TPC, PUCCH resource Indicator, ChannelAccess-CPext (if indicated), and HARQ
feedback Timing Indicator received in successRAR to lower layers.
4> finish the disassembly and demultiplexing of the MAC PDU.

TransMax + 1:
ETSI
3> else:
PREAMBLE_BACKOFF;
4> else:
[TS 38.321, clause 5.1.5]
Once Msg3 is transmitted the MAC entity shall:
a measurement gap;
5.17) and the PDCCH transmission is addressed to the C-RNTI; or
addressed to the C-RNTI; or
PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new transmission:
2> else if the CCCH SDU was included in Msg3 and the PDCCH transmission is addressed to its
TEMPORARY_C-RNTI:
3> if the MAC PDU is successfully decoded:
4> if the MAC PDU contains a UE Contention Resolution Identity MAC CE; and
ETSI
4> if the UE Contention Resolution Identity in the MAC CE matches the CCCH SDU transmitted in
Msg3:
5> consider this Contention Resolution successful and finish the disassembly and demultiplexing of
the MAC PDU;
5> else:
6> set the C-RNTI to the value of the TEMPORARY_C-RNTI;
4> else:
5> consider this Contention Resolution not successful and discard the successfully decoded MAC
PDU.
3> if the RA_TYPE is set to 4-stepRA:
PREAMBLE_BACKOFF;
4> if the criteria (as defined in clause 5.1.2) to select contention-free Random Access Resources is met
5> perform the Random Access Resource selection procedure (see clause 5.1.2);
4> else:
5> perform the Random Access Resource selection procedure (see clause 5.1.2) after the backoff
time.
3> else (i.e. the RA_TYPE is set to 2-stepRA):
4> if msgA-TransMax is applied (see clause 5.1.1a) and PREAMBLE_TRANSMISSION_COUNTER =

msgA-TransMax + 1:
ETSI
5> perform the Random Access Resource selection as specified in clause 5.1.2.
4> else:
PREAMBLE_BACKOFF;
5> if the criteria (as defined in clause 5.1.2a) to select contention-free Random Access Resources is
met during the backoff time:
6> perform the Random Access Resource selection procedure for 2-step RA type as specified in
clause 5.1.2a.
5> else:
6> perform the Random Access Resource selection for 2-step RA type procedure (see clause
5.1.2a) after the backoff time.
[TS 38.321, clause 5.2]
1> when a Timing Advance Command MAC CE is received, and if an NTA (as defined in TS 38.211 [8]) has been
1> when a Timing Advance Command is received in a Random Access Response message for a Serving Cell
belonging to a TAG or in a MSGB for an SpCell:
Access Preamble:
3> start or restart the timeAlignmentTimer associated with this TAG.
2> else if the timeAlignmentTimer associated with this TAG is not running:
3> start the timeAlignmentTimer associated with this TAG;
3> when the Contention Resolution is considered not successful as described in clause 5.1.5; or
3> when the Contention Resolution is considered successful for SI request as described in clause 5.1.5, after
transmitting HARQ feedback for MAC PDU including UE Contention Resolution Identity MAC CE:
4> stop timeAlignmentTimer associated with this TAG.
2> else:
3> ignore the received Timing Advance Command.
ETSI
1> when an Absolute Timing Advance Command is received in response to a MSGA transmission including C-
RNTI MAC CE as specified in clause 5.1.4a:
2> apply the Timing Advance Command for PTAG;
2> start or restart the timeAlignmentTimer associated with PTAG.
SCell as expired.
The MAC entity shall not perform any uplink transmission on a Serving Cell except the Random Access Preamble and
MSGA transmission when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not
running. Furthermore, when the timeAlignmentTimer associated with the PTAG is not running, the MAC entity shall not
perform any uplink transmission on any Serving Cell except the Random Access Preamble and MSGA transmission on
the SpCell.
ETSI

U-S Message
- EXCEPTION: Step 1 is performed IF - - - -
pc_NG_RAN_NR only.
1 The SS transmits an updated system - - - -
2.
to configure 2-Step and RA type Random
Access Resources. (Note 1)
2)
SpCell. SS does not send any subsequent Command MAC CE)
SDU of size 56 bits, less than ra-MsgA-
SizeGroupA (208 bits) on SpCell. (Note 3)
7 Check: Does the UE transmit MSGA using --> MAC PDU (including C-RNTI MAC 1 P
preamble on PRACH in group A? CE)
8 Check: Does the UE re-transmit MSAG using a --> MAC PDU (including C-RNTI MAC 2 P
preamble on PRACH in the same group A after CE)
expiry of msgB-ResponseWindow?
9 The SS transmits a MSGB with the Backoff <-- MAC PDU(BI, RAPID) - -
parameter set to value Index field '12' and with
the RAPID different from the value received
from the UE.
The SS sets Timer_T2 to the Backoff value
‘960’ associated with the Index value ‘12’ and
starts Timer_T2.
10 Check: Does UE transmit MSGA using --> MAC PDU (including C-RNTI MAC 3 P
preamble on PRACH in group A while CE)
Timer_T2 is running?
11 The SS schedules PDCCH transmission for <-- MAC PDU(Absolute Timing - -
UE C_RNTI and DL MAC PDU containing Advance Command MAC CE)
Absolute Timing Advance Command MAC CE.
- EXCEPTION: Step 12 is performed IF - - - -
pc_NG_RAN_NR only.
12 The SS transmits an updated system - - - -
2.
to configure 2-Step RA type Random Access
Resources. (Note 1)
2)
SpCell. SS does not send any subsequent Command MAC CE)
ETSI

SDU of size 256 bits, more than ra-MsgA-
SizeGroupA (208 bits) on SpCell. (Note 4)
18 Check: Does the UE transmit MSGA using --> MAC PDU (including C-RNTI MAC 4 P
preamble on PRACH in group B? CE)
19 SS schedules PDCCH transmission for UE <-- MAC PDU(Timing Advance - -
C_RNTI and DL MAC PDU containing Timing Command MAC CE)
Advance Command MAC CE.
20 Check: Does the UE transmits a MAC PDU --> MAC PDU 5 P
with C-RNTI containing looped back PDCP
SDU using the new Timing Advance value?
Note 1: For EN-DC the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration.
Note 3: MAC PDU size of 56bits is selected to allow UE send status PDU and stays below the limit of ra-MsgA-
SizeGroupA.
Note 4: MAC PDU size of 256bits is selected to allow UE send status PDU and stays above the limit of ra-MsgA-
SizeGroupA.

tag-Config SEQUENCE {
tag-ToAddModList SEQUENCE (SIZE 1 entry
(1..maxNrofTAGs)) OF TAG {
TAG[1] SEQUENCE { entry 1
timeAlignmentTimer ms750
}
}
}
}
Table 7.1.1.1.9.3.3-2: SystemInformationBlockType1 (step 1 and 12, Table 7.1.1.1.9.3.2-1)

SIB1 ::= SEQUENCE {
servingCellConfigCommon ServingCellConfigComm
on
}
Table 7.1.1.1.9.3.3-3: ServingCellConfigCommon (Table 7.1.1.1.9.3.3-2, Table 7.1.1.1.9.3.3-1A)

}
}
ETSI

msgA-ConfigCommon-r16 CHOICE {
setup MsgA-ConfigCommon-
r16
}
}
Table 7.1.1.1.9.3.3-5: MsgA-ConfigCommon-r16 (Table 7.1.1.1.9.3.3-4)

MsgA-ConfigCommon-r16 :: = SEQUENCE {
rach-ConfigCommonTwoStepRA-r16 RACH-
ConfigCommonTwoStep
RA-r16
msgA-PUSCH-Config-r16 MsgA-PUSCH-Config-r16
}
Table 7.1.1.1.9.3.3-6: RACH-ConfigCommonTwoStepRA-r16 (Table 7.1.1.1.9.3.3-5)

RACH-ConfigCommonTwoStepRA-r16 ::=
SEQUENCE {
rach-ConfigGenericTwoStepRA-r16 RACH-
ConfigGenericTwoStepR
A-r16
msgA-TotalNumberOfRA-Preambles-r16 8
msgA-SSB-PerRACH-OccasionAndCB-
PreamblesPerSSB-r16 CHOICE {
two n4
}
groupB-ConfiguredTwoStepRA-r16 GroupB-
ConfiguredTwoStepRA-
r16
msgA-PRACH-RootSequenceIndex-r16 CHOICE {
l839 100
}
msgA-TransMax-r16 n4
msgA-RSRP-Threshold-r16 56
msgA-RSRP-ThresholdSSB-r16 56
msgA-SubcarrierSpacing-r16 SubcarrierSpacing TS 38.508-1 [4],
Table 4.6.3-188
msgA-RestrictedSetConfig-r16 unrestrictedSet
ra-PrioritizationForAccessIdentityTwoStep-r16
SEQUENCE {
ra-Prioritization-r16 RA-Prioritization TS 38.508-1 [4],
Table 4.6.3-131
ra-PrioritizationForAI-r16 ‘00’B
}
ra-ContentionResolutionTimer-r16 sf32
}
ETSI
Table 7.1.1.1.9.3.3-7: RACH-ConfigGenericTwoStepRA-r16 (Table 7.1.1.1.9.3.3-6)

RACH-ConfigGenericTwoStepRA-r16 ::= SEQUENCE
{
msgA-PRACH-ConfigurationIndex-r16 0
msgA-RO-FDM-r16 one
msgA-RO-FrequencyStart-r16 0
msgA-ZeroCorrelationZoneConfig-r16 0
msgA-PreamblePowerRampingStep-r16 dB2
msgA-PreambleReceivedTargetPower-r16 -200
msgB-ResponseWindow-r16 sl80
preambleTransMax-r16 n4
}
Table 7.1.1.1.9.3.3-8: GroupB-ConfiguredTwoStepRA-r16 (Table 7.1.1.1.9.3.3-6)
Derivation Path: TS 38.331 [6] clause 6.3.2

GroupB-ConfiguredTwoStepRA-r16 ::= SEQUENCE {
ra-MsgA-SizeGroupA b208
}
Table 7.1.1.1.9.3.3-9: MsgA-PUSCH-Config-r16 (Table 7.1.1.1.9.3.3-5)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-81B

MsgA-PUSCH-Config-r16 ::= SEQUENCE {
msgA-PUSCH-ResourceGroupA-r16 MsgA-PUSCH-Resource-
r16
msgA-PUSCH-ResourceGroupB-r16 MsgA-PUSCH-Resource-
r16
}
Table 7.1.1.1.9.3.3-10: MsgA-PUSCH-Resource-r16 (Table 7.1.1.1.9.3.3-9)

MsgA-PUSCH-Resource-r16 ::= SEQUENCE {
msgA-MCS-r16 0
nrofSlotsMsgA-PUSCH-r16 1
nrofMsgA-PO-PerSlot-r16 one
msgA-PUSCH-TimeDomainOffset-r16 1
guardBandMsgA-PUSCH-r16 0
frequencyStartMsgA-PUSCH-r16 0
nrofPRBs-PerMsgA-PO-r16 24
nrofMsgA-PO-FDM-r16 one
msgA-DMRS-Config-r16 MsgA-DMRS-Config-r16
nrofDMRS-Sequences-r16 1
}
ETSI
Table 7.1.1.1.9.3.3-11: MsgA-DMRS-Config-r16 (Table 7.1.1.1.9.3.3-10)

MsgA-DMRS-Config-r16 ::= SEQUENCE {
msgA-DMRS-AdditionalPosition-r16 pos0
msgA-MaxLength-r16 len2
}
Table 7.1.1.1.9.3.3-12: RRCReconfiguration (step 2 and step 13, Table 7.1.1.1.9.3.2-1)

(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}

spCellConfigCommon ServingCellConfigComm Same contents as
on in Table
7.1.1.1.9.3.3-3
t304 ms2000
}
7.1.1.1.10 Random access procedure / 2-step RACH/not complete/ RA_TYPE to 4-stepRA
(1)
ensure that {
when { UE does not receive a matching MSGB in msgB-ResponseWindow and
PREAMBLE_TRANSMISSION_COUNTER is equal to msgA-TransMax+1 }
then { UE triggers 4-step RACH procedure on NR SpCell }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.321, clauses 5.1.1, and
5.1.4a.
[TS 38.321, clause5.1.1]
ETSI
The Random Access procedure described in this clause is initiated by a PDCCH order, by the MAC entity itself, or by
RRC for the events in accordance with TS 38.300 [2]. There is only one Random Access procedure ongoing at any
point in time in a MAC entity. The Random Access procedure on an SCell shall only be initiated by a PDCCH order
with ra-PreambleIndex different from 0b000000.
1> if the Random Access procedure is initiated by PDCCH order and if the ra-PreambleIndex explicitly provided
by PDCCH is not 0b000000; or
1> if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]) and the Random
Access Resources for SI request have been explicitly provided by RRC; or
1> else:
1> else:
[TS 38.321, clause 5.1.4a]
shall:
ETSI

TransMax + 1:
3> else:
PREAMBLE_BACKOFF;
4> else:
ETSI

U-S Message
to configure both 2-Step and 4-Step RA type
Random Access Resources. Note 1
2
SDU
- Exception: Step 6 will be repeated - - - -
preambleTransMax times and SS does not
response the MSGA in STEP 6, to make
PREAMBLE_TRANSMISSION_COUNTER =
msgA-TransMax+1.
6 The UE transmits MSGA using the selected --> MAC PDU (including C-RNTI MAC - -
resource of MSGA
PRACH?
and RAPID corresponding to the transmitted
Preamble in step 7.
to the Random Access Response received in ELEMENT)
step 8
10 SS schedules PDCCH transmission for UE <-- Contention Resolution - -
11 The UE transmits a MAC PDU with C-RNTI --> MAC PDU - -
containing looped back PDCP SDU
FFS
ETSI
7.1.1.2 Downlink Data Transfer
7.1.1.2.1 Correct Handling of DL MAC PDU / Assignment / HARQ process
(1)
with { UE in RRC_CONNECTED state }
ensure that {
when { UE receives downlink assignment on the PDCCH for the UE’s C-RNTI and receives data in the
associated Slot and UE performs HARQ operation }
then { UE sends a HARQ feedback on the HARQ process }
}
(2)
ensure that {
when { SS transmits downlink assignment on the PDCCH with a C-RNTI unknown by the UE and data is
available in the associated Slot }
then { UE does not send any HARQ feedback on the HARQ process }
}
(3)
ensure that {
when { the UE receives a MAC PDU addressed to its C-RNTI and decode fails in the associated Slot }
then { the UE transmits a NACK for the corresponding HARQ process }
}
(4)
ensure that {
when { the UE receives a MAC PDU retransmission addressed to its C-RNTI, and results in successful
decode in the associated Slot}
then { the UE transmits an ACK for the corresponding HARQ process and forward to higher layer }
}
(5)
ensure that {
when { UE receives a MAC PDU containing multiple MAC sub PDUs each containing a MAC SDU that is
larger than 256 bytes (16 bits L field used) with padding MAC sub PDU at the end }
then { UE successfully decodes the MAC PDU and forward to higher layer }
}
(6)
ensure that {
when { UE receives a MAC PDU containing multiple MAC sub PDUs each containing a MAC SDU that is
smaller than 256 bytes (8 bits L field used) with padding MAC sub PDU at the end }
}
(7)
ensure that {
when { UE receives a MAC PDU containing MAC sub PDU containing a MAC SDU and no padding MAC sub
PDU}
}
ETSI
(8)
ensure that {
when { UE receives a MAC PDU containing MAC sub PDU containing a MAC SDU that is smaller than 256
bytes (8 bits L field used) plus MAC sub PDU containing a MAC SDU that is greater than 256 bytes (16
bits L field used)and no padding }
then { UE successfully decodes the MAC PDU and forwards the AMD PDUs to higher layer }
}
(9)
with { UE in RRC_CONNECTED state and configured with a specific TDD-UL-DL-ConfigCommon including
configuration of pattern2}
ensure that {
when { UE receives downlink assignment on the PDCCH associated with pattern2 for the UE’s C-RNTI
and receives data in the associated Slot and UE performs HARQ operation }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.321, clauses 5.3.1,
5.3.2.1, 5.3.2.2 and 6.1.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.3.1]
Downlink assignments received on the PDCCH both indicate that there is a transmission on a DL-SCH for a particular
MAC entity and provide the relevant HARQ information.
When the MAC entity has a C-RNTI, Temporary C-RNTI, or CS-RNTI, the MAC entity shall for each PDCCH
occasion during which it monitors PDCCH and for each Serving Cell:
1> if a downlink assignment for this PDCCH occasion and this Serving Cell has been received on the PDCCH for
the MAC entity’s C-RNTI, or Temporary C-RNTI:
2> if this is the first downlink assignment for this Temporary C-RNTI:
3> consider the NDI to have been toggled.
2> if the downlink assignment is for the MAC entity’s 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
MAC entity’s CS-RNTI or a configured downlink assignment:
3> consider the NDI to have been toggled regardless of the value of the NDI.
2> indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ
entity.
1> else if a downlink assignment for this PDCCH occasion has been received for this Serving Cell on the PDCCH
for the MAC entity’s CS-RNTI:
2> if the NDI in the received HARQ information is 1:
3> consider the NDI for the corresponding HARQ process not to have been toggled;
3> indicate the presence of a downlink assignment for this Serving Cell and deliver the associated HARQ
information to the HARQ entity.
3> if PDCCH contents indicate SPS deactivation:
4> clear the configured downlink assignment for this Serving Cell (if any);
4> if the timeAlignmentTimer associated with the PTAG is running:
5> indicate a positive acknowledgement for the SPS deactivation to the physical layer.
ETSI
3> else if PDCCH content indicates SPS activation:
4> store the downlink assignment for this Serving Cell and the associated HARQ information as
configured downlink assignment;
4> initialise or re-initialise the configured downlink assignment for this Serving Cell to start in the
associated PDSCH duration and to recur according to rules in subclause 5.8.1;
4> set the HARQ Process ID to the HARQ Process ID associated with this PDSCH duration;
4> consider the NDI bit for the corresponding HARQ process to have been toggled;
4> indicate the presence of a configured downlink assignment for this Serving Cell and deliver the stored
HARQ information to the HARQ entity.
For each Serving Cell and each configured downlink assignment, if configured and activated, the MAC entity shall:
1> if the PDSCH duration of the configured downlink assignment does not overlap with the PDSCH duration of a
downlink assignment received on the PDCCH for this Serving Cell:
2> instruct the physical layer to receive, in this PDSCH duration, transport block on the DL-SCH according to
the configured downlink assignment and to deliver it to the HARQ entity;
2> consider the NDI bit to have been toggled;
2> indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the
HARQ entity.
For configured downlink assignments, the HARQ Process ID associated with the slot where the DL transmission starts
is derived from the following equation:
HARQ Process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame × semiPersistSchedIntervalDL))] modulo

nrofHARQ-Processes
where CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + slot number in the frame] and numberOfSlotsPerFrame
refers to the number of consecutive slots per frame as specified in TS 38.211 [8].
When the MAC entity needs to read BCCH, the MAC entity may, based on the scheduling information from RRC:
1> if a downlink assignment for this PDCCH occasion has been received on the PDCCH for the SI-RNTI;
2> indicate a downlink assignment and redundancy version for the dedicated broadcast HARQ process to the
HARQ entity.
[TS 38.321, clause 5.3.2.2]
When a transmission takes place for the HARQ process, one or more (in case of downlink 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:
1> if the NDI, when provided, has been toggled compared to the value of the previous received transmission
corresponding to this TB; or
1> if the HARQ process is equal to the broadcast process, and this is the first received transmission for the TB
according to the system information schedule indicated by RRC; or
1> if this is the very first received transmission for this TB (i.e. there is no previous NDI for this TB):
2> consider this transmission to be a new transmission.
1> else:
2> consider this transmission to be a retransmission.
The MAC entity then shall:
ETSI
1> if this is a new transmission:
2> attempt to decode the received data.
1> else if this is a retransmission:
2> if the data for this TB has not yet been successfully decoded:
3> instruct the physical layer to combine the received data with the data currently in the soft buffer for this
TB and attempt to decode the combined data.
1> if the data which the MAC entity attempted to decode was successfully decoded for this TB; or
1> if the data for this TB was successfully decoded before:
2> if the HARQ process is equal to the broadcast process:
3> deliver the decoded MAC PDU to upper layers.
2> else if this is the first successful decoding of the data for this TB:
3> deliver the decoded MAC PDU to the disassembly and demultiplexing entity.
1> else:
2> instruct the physical layer to replace the data in the soft buffer for this TB with the data which the MAC
entity attempted to decode;
1> 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
1> if the HARQ process is equal to the broadcast process; or
1> if the timeAlignmentTimer, associated with the TAG containing the Serving Cell on which the HARQ feedback
is to be transmitted, is stopped or expired:
2> not instruct the physical layer to generate acknowledgement(s) of the data in this TB.
1> else:
2> instruct the physical layer to generate acknowledgement(s) of the data in this TB.
The MAC entity 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.
[TS 38.321, clause 6.1.2]
A MAC PDU consists of one or more MAC subPDUs. Each MAC subPDU consists of one of the following:
- A MAC subheader only (including padding);
- A MAC subheader and a MAC SDU;
- A MAC subheader and a MAC CE;
- A MAC subheader and padding.
The MAC SDUs are of variable sizes.
Each MAC subheader corresponds to either a MAC SDU, a MAC CE, or padding.
A MAC subheader except for fixed sized MAC CE and padding consists of the four header fields R/F/LCID/L. A MAC
subheader for fixed sized MAC CE and padding consists of the two header fields R/LCID.
ETSI
R F LCID Oct 1
L Oct 2
Figure 6.1.2-1: R/F/LCID/L MAC subheader with 8-bit L field
R F LCID Oct 1
L Oct 2
L Oct 3
R R LCID Oct 1
Figure 6.1.2-3: R/LCID MAC subheader
MAC CEs are placed together. DL MAC subPDU(s) with MAC CE(s) is placed before any MAC subPDU with MAC
SDU and MAC subPDU with padding as depicted in Figure 6.1.2-4. UL MAC subPDU(s) with MAC CE(s) is placed
after all the MAC subPDU(s) with MAC SDU and before the MAC subPDU with padding in the MAC PDU as
depicted in Figure 6.1.2-5. The size of padding can be zero.
R/LCID Fixed-sized R/F/LCID/L Variable-sized R/F/LCID/L

MAC SDU
subheader MAC CE subheader MAC CE subheader
MAC subPDU
including MAC CE 1
MAC subPDU
including MAC CE 2
MAC subPDU including
MAC SDU
... MAC subPDU including MAC subPDU including
MAC SDU padding (opt)
Figure 6.1.2-4: Example of a DL MAC PDU
ETSI
R/F/LCID/L R/LCID Fixed-sized R/F/LCID/L Variable-sized

MAC SDU
subheader subheader MAC CE subheader MAC CE
MAC subPDU
including MAC SDU
MAC subPDU
including MAC SDU
... MAC subPDU
including MAC CE 1
MAC subPDU
including MAC CE 2
padding (opt)
Figure 6.1.2-5: Example of a UL MAC PDU
A maximum of one MAC PDU can be transmitted per TB per MAC entity.
Same Pre-test conditions as in clause 7.1.1.0 except that set to return no data in uplink and parameters as in Table
7.1.1.2.1.3.1-1.
Table 7.1.1.2.1.3.1-1: MAC Parameters
nrofHARQ-ProcessesForPDSCH n16
ETSI

U-S Message
1 SS transmits a downlink assignment <-- (PDCCH (C-RNTI)) - -
addressed to the C-RNTI assigned to the UE
2 SS transmits in the indicated downlink <-- MAC PDU - -
assignment a MAC PDU including a RLC PDU
with poll bit not set.
3 Check: Does the UE transmit an HARQ ACK --> HARQ ACK 1 P
on PUCCH?
4 SS transmits a downlink assignment to <-- (PDCCH (unknown C-RNTI)) - -
including a C-RNTI different from the assigned
to the UE
assignment a RLC PDU in a MAC PDU
including a RLC PDU with poll bit not set.
6 Check: Does the UE send any HARQ --> HARQ ACK/NACK 2 F
ACK/NACK on PUCCH?
- EXCEPTION: Steps 7 to 10 are run repeated - - - -
using test parameter values as given for each
iteration in table 7.1.1.2.1.3.2.-2.
7 The SS indicates a new transmission on <-- MAC PDU - -
PDCCH and transmits a MAC PDU including a
RLC PDU with poll bit not set, with content set
so that UE could not successfully decode the
data from its soft buffer. (Note 1)
8 Check: Does the UE transmit a HARQ NACK? --> HARQ NACK 3 P
- EXCEPTION: Step 9 shall be repeated till - - - -
HARQ ACK is received at step 10 or until
HARQ retransmission count = 4 is reached for
MAC PDU at step 9 (Note 2).
9 The SS indicates a retransmission on PDCCH <-- MAC PDU - -
and transmits the same MAC PDU like step 7
(Note 1).
- EXCEPTION: Up to [3] HARQ NACK from the - - - -
UE should be allowed at step 10 (Note 2).
10 Check: Does the UE send a HARQ ACK? --> HARQ ACK 4 P
11 The SS transmits a MAC PDU containing three <-- MAC PDU - -
MAC sub PDUs each containing a MAC
SDU(RLC PDU) that is of 260 bytes (16 bits L
field used) and a padding MAC sub PDU at the
end. The third RLC PDU contained will have
poll bit set.
12 Check: Does the UE transmit a MAC PDU --> MAC PDU (RLC STATUS PDU ) 5 P
containing an RLC STATUS PDU
acknowledging the reception of all the AMD
PDUs in step 11?
13 The SS transmits a MAC PDU containing three <-- MAC PDU - -
MAC sub PDUs each containing a MAC
SDU(RLC PDU) that is of 128 bytes (8 bits L
field used) and a padding MAC sub PDU at the
end. The third RLC PDU contained will have
poll bit set.
PDUs in step 13?
15 The SS transmits a MAC PDU containing one <-- MAC PDU - -
MAC sub PDU containing a MAC SDU(RLC
PDU) that is of [128] bytes (8 bits L field used)
and no padding MAC sub PDU at the end. The
RLC PDU contained will have poll bit set.
ETSI
acknowledging the reception of the AMD PDU

in step 15?
17 The SS transmits a MAC PDU containing one <-- MAC PDU - -
MAC sub PDU containing a MAC SDU(RLC
PDU) that is of [128] bytes (8 bits L field used),
one MAC sub PDU containing a MAC
SDU(RLC PDU) that is of [260] bytes (16 bits L
field used) and no padding MAC sub PDU at
the end. The second RLC PDU contained will
have poll bit set.
PDUs in step 17?
- EXCEPTION : Steps 19a0 to 19a5 are - - - -
executed for operation on NR TDD band only
19a0 The SS transmits an updated system - - - -
14. (Note 5)
19a1 The SS transmits NR RRCReconfiguration <-- RRCReconfiguration - -
message including TDD-UL-DL-
ConfigCommon with pattern1 and pattern2
specified in Table 7.1.1.2.1.3.3-5 (Note 3)
19a2 The UE transmits a NR --> RRCReconfigurationComplete - -
RRCReconfigurationComplete message.
(Note 4)
19a3 SS transmits a downlink assignment <-- (PDCCH (C-RNTI)) - -
addressed to the C-RNTI assigned to the UE
indicating downlink reception in a symbol in a
slot part of pattern2.
19a4 SS transmits in the indicated downlink <-- MAC PDU - -
assignment a MAC PDU including a RLC PDU
with poll bit not set.
19a5 Check: Does the UE transmit an HARQ ACK --> HARQ ACK 9 P
on PUCCH?
Note 1: SS should transmit this PDU so as to ensure at least one NACK.
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.
Note 5: if pc_NG_RAN_NR only
Table 7.1.1.2.1.3.2-2: Test Parameters
Iteration DL HARQ process

(X)
K=1 to 16 X=K-1
ETSI
Table 7.1.1.2.1.3.3-1: Void
Table 7.1.1.2.1.3.3-2: RRCReconfiguration (step19a1, Table 7.1.1.2.1.3.2-1)

secondaryCellGroup CellGroupConfig EN-DC
}
RRCReconfiguration-v1530-IEs::= SEQUENCE { NR
}
}
}

on
}
}
}
Table 7.1.1.2.1.3.3-4, 7.1.1.2.1.3.3-13: ServingCellConfigCommon (Table 7.1.1.2.1.3.3-3)

}
ConfigCommon
}
ETSI

pattern1 SEQUENCE {
ms0p625 FR2
2 FR2
6 FR2
2 FR2
2 FR2
}
pattern2 SEQUENCE {
ms0p625 FR2
3 FR2
6 FR2
1 FR2
2 FR2
}
}

}
}

}

prach-configurationIndex 156
}
ETSI
Table 7.1.1.2.1.3.3-9: ServingCellConfig (Table 7.1.1.2.1.3.3-3)

}
}
Table 7.1.1.2.1.3.3-10: BWP-UplinkDedicated (Table 7.1.1.2.1.3.3-9)

setup PUCCH-Config
}
}
Table 7.1.1.2.1.3.3-11: PUCCH-Config (Table 7.1.1.2.1.3.3-10)

SchedulingRequestResourceConfig[1] SchedulingRequestReso entry 1
urceConfig
}
}
Table 7.1.1.2.1.3.3-12: SchedulingRequestResourceConfig (Table 7.1.1.2.1.3.3-11)

kHz15 results in
repetition every 10
ms
kHz30 results in
repetition every 10
ms
kHz120 results in z
repetition every 10
ms
}
}
ETSI
Table 7.1.1.2.1.3.3-13: SystemInformationBlockType1 (step 19a0, Table 7.1.1.2.1.3.2-1)

SIB1 ::= SEQUENCE {
on in Table
7.1.1.2.1.3.3-5
}
7.1.1.2.2 Correct Handling of DL HARQ process PDSCH Aggregation
(1)
with { UE in RRC_CONNECTED state and pdsch-AggregationFactor > 1 }
ensure that {
when { UE receives downlink assignment on the PDCCH for the UE’s C-RNTI and receives data in the
associated slot and successive pdsch-AggregationFactor – 1 HARQ retransmissions within a bundle and
UE performs HARQ operation }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.321, clauses 5.3.1, 5.3.2.1
and 5.3.2.2, TS 38.214, clause 5.1.2.1.
[TS 38.321, clause 5.3.1]
the MAC entity's C-RNTI, or Temporary C-RNTI:
2> if the downlink assignment is for the MAC entity's C-RNTI, and if the previous downlink assignment
MAC entity's CS-RNTI or a configured downlink assignment:
entity.
for the MAC entity's CS-RNTI:
ETSI
4> if the timeAlignmentTimer associated with the PTAG is running:
4> indicate the presence of a configured downlink assignment for this Serving Cell and deliver the stored
HARQ information to the HARQ entity.
HARQ entity.
HARQ Process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame × periodicity))] modulo nrofHARQ-

Processes
HARQ entity.
[TS 38.321, clause 5.3.2.1]
The MAC entity includes a HARQ entity for each Serving Cell, 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 parallel DL HARQ processes per HARQ entity is specified in TS 38.214 [7]. The dedicated broadcast
HARQ process is used for BCCH.
The HARQ process supports one TB when the physical layer is not configured for downlink spatial multiplexing. The
HARQ process supports one or two TBs when the physical layer is configured for downlink spatial multiplexing.
ETSI
When the MAC entity is configured with pdsch-AggregationFactor > 1, the parameter pdsch-AggregationFactor
provides the number of transmissions of a TB within a bundle of the dynamic downlink assignment. Bundling operation
relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle.
After the initial transmission, pdsch-AggregationFactor – 1 HARQ retransmissions follow within a bundle.
1> if a downlink assignment has been indicated:
2> allocate the TB(s) received from the physical layer and the associated HARQ information to the HARQ
process indicated by the associated HARQ information.
1> if a downlink assignment has been indicated for the broadcast HARQ process:
2> allocate the received TB to the broadcast HARQ process.
[TS 38.321, clause 5.3.2.2]
When a transmission takes place for the HARQ process, one or two (in case of downlink spatial multiplexing) TBs and
the associated HARQ information are received from the HARQ entity.
1> else:
1> else:
entity attempted to decode.
ETSI
1> else:
[TS 38.214, clause 5.1.2.1]
When the UE is scheduled to receive PDSCH by a DCI, the Time domain resource assignment field value m of the DCI
provides a row index m + 1 to an allocation table. The determination of the used resource allocation table is defined in
sub-clause 5.1.2.1.1. The indexed row defines the slot offset K0, the start and length indicator SLIV, or directly the start
symbol S and the allocation length L, and the PDSCH mapping type to be assumed in the PDSCH reception.
Given the parameter values of the indexed row:
 2 μ PDSCH 
- The slot allocated for the PDSCH is n ⋅  + K0 , where n is the slot with the scheduling DCI, and K0 is

 2 μ PDCCH 

based on the numerology of PDSCH, and μ PDSCH and μPDCCH are the subcarrier spacing configurations for
PDSCH and PDCCH, respectively, and
- The starting symbol S relative to the start of the slot, and the number of consecutive symbols L counting from the
symbol S allocated for the PDSCH are determined from the start and length indicator SLIV:
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and
- The PDSCH mapping type is set to Type A or Type B as defined in sub-clause 7.4.1.1.2 of [4, TS 38.211].
The UE shall consider the S and L combinations defined in table 5.1.2.1-1 as valid PDSCH allocations:
Table 5.1.2.1-1: Valid S and L combinations
PDSCH Normal cyclic prefix Extended cyclic prefix

mapping type S L S+L S L S+L
Type A {0,1,2,3} {3,…,14} {3,…,14} {0,1,2,3} {3,…,12} {3,…,12}
(Note 1) (Note 1)
Type B {0,…,12} {2,4,7} {2,…,14} {0,…,10} {2,4,6} {2,…,12}
Note 1: S = 3 is applicable only if dmrs-TypeA-Position = 3
When the UE is configured with aggregationFactorDL > 1, the same symbol allocation is applied across the
aggregationFactorDL consecutive slots. The UE may expect that the TB is repeated within each symbol allocation
among each of the aggregationFactorDL consecutive slots and the PDSCH is limited to a single transmission layer. The
redundancy version to be applied on the nth transmission occasion of the TB is determined according to table 5.1.2.1-2.
ETSI
Table 5.1.2.1-2: Applied redundancy version when aggregationFactorDL > 1

rvid indicated by the DCI rvid to be applied to nth transmission occasion
scheduling the PDSCH n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3
0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
If the UE procedure for determining slot configuration as defined in Subclause 11.1 of [6, TS 38.213] determines
symbol of a slot allocated for PDSCH as uplink symbols, the transmission on that slot is omitted for multi-slot PDSCH
transmission.
The UE is not expected to receive a PDSCH with mapping type A in a slot, if the PDCCH scheduling the PDSCH was
received in the same slot and was not contained within the first three symbols of the slot.
The UE is not expected to receive a PDSCH with mapping type B in a slot, if the first symbol of the PDCCH scheduling
the PDSCH was received in a later symbol than the first symbol indicated in the PDSCH time domain resource
allocation.
Same Pre-test conditions as in clause 7.1.1.0 except that set to return no data in uplink and parameters as in Table
7.1.1.2.2.3.1-1.
Table 7.1.1.2.2.3.1-1: Void
ETSI

U-S Message
1 SS transmits in the indicated downlink <-- - - -
assignment an NR RRCReconfiguration. (Note
1)
2 UE transmits NR --> - - -
RRCReconfigurationComplete message to the
SS. (Note 2)
3 The SS transmits a downlink assignment <-- - - -
addressed to the C-RNTI assigned to the UE,
the rv_idx is 0.
4 The SS transmits in the indicated downlink <-- MAC PDU - -
assignment a MAC PDU including a RLC PDU,
The CRC is calculated in such a way, it will
result in CRC error on UE side.
5 In the following 3 consecutive slots, the SS <-- MAC PDU - -
transmits on the same downlink assignment a
MAC PDU including a RLC PDU, The CRC is
calculated in such a way, it will result in CRC
error on UE side. (Note3)
5A Void - - - -
6 Check: Does the UE transmit a HARQ NACK --> HARQ NACK 1 P
on slot n3+k1? (Note 4)
7 The SS transmits a downlink assignment <-- - - -
addressed to the C-RNTI assigned to the UE,
the rv_idx is 0.
8 The SS transmits in the indicated downlink <-- MAC PDU - -
assignment a MAC PDU including a RLC PDU,
The CRC is calculated in such a way, it will
result in CRC pass on UE side.
9 In the following 3 consecutive slots, the SS <-- MAC PDU - -
transmits on the same downlink assignment a
MAC PDU including a RLC PDU, The CRC is
pass on UE side. (Note3)
10 Check: Does the UE transmit a HARQ ACK on --> HARQ ACK 1 P
slot n3+k1? (Note 4)
Note 1: For EN-DC the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration 36.508
[7], Table 4.6.1-8 using condition EN-DC_EmbedNR_RRCRecon.
Note 3: For aggregationFactorDL=4, the PDSCH will repeat in following 4-1=3 slots with same resource allocation
but different redundancy version, if the slot can be used for downlink transmission.
Note 4: n0 is the index of slot when 1st transmission of MAC PDU in step 4/8 happens, n1, n2, n3 are indices of
slots when 2nd, 3rd, 4th transmission of MAC PDU in step 5/9 may happen, k1 is obtained from "PDSCH-to-
HARQ_feedback timing indicator" of downlink assignment in step 3/7.
ETSI
Table 7.1.1.2.2.3.3-1: RRCReconfiguration (step 1, Table 7.1.1.2.2.3.2-1)

rrcReconfiguration SEQUENCE {
(CONTAINING
CellGroupConfig)
}
RRCReconfiguration-v1530-IEs ::= SEQUENCE { NR
}
}
}
Table 7.1.1.2.2.3.3-2: cellGroupConfig (Table 7.1.1.2.2.3.3-1: RRCReconfiguration)

cellGroupConfig::= SEQUENCE {
cellGroupId 0
1 EN-DC
spCellConfigDedicated SEQUENCE {
servingCellConfig SEQUENCE {
initialDownlinkBWP SEQUENCE {
pdsch-Config SEQUENCE {
pdsch-AggregationFactor n4
}
}
}
}
}
}
Table 7.1.1.2.2.3.3-3: Physical layer parameters for DCI format 1_1 (Steps 3, 7, Table 7.1.1.2.2.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.3.6.1.2.2-1

Parameter Value Value in binary Condition
PDSCH-to-HARQ_feedback timing Corresponding to K1=5 slots as per dl- “011”B
indicator DataToUL-ACK in Table 4.6.3-112 TS
38.508-1 [4].
7.1.1.2.3 Correct HARQ process handling / CCCH
(1)
with { UE in 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 the HARQ feedback for the corresponding HARQ process }
}
(2)
ETSI
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI without UE Contention Resolution Identity
corresponding the transmitted RRCSetupRequest message }
}
(3)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI and cannot decode properly }
}
(4)
ensure that {
when { UE receives a MAC PDU addressed to T-CRNTI with UE Contention Resolution Identity
corresponding the transmitted RRCSetupRequest message }
then { UE transmits the HARQ ACK for the corresponding HARQ process }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.321, clauses 5.3.2.1 and
5.3.2.2.
[TS 38.321, clause 5.3.2.1]
[TS 38.321, clause 5.3.2.2]
ETSI
1> else:
1> else:
1> else:
NOTE: If the MAC entity receives a retransmission with a TB size different from the last TB size signalled for
this TB, the UE behavior is left up to UE implementation.
System Simulator:
- NR Cell 1.
ETSI
UE:
- None
Preamble:
- The UE is in 1N-A state on NR Cell 1 using generic procedure parameter Connectivity (NR) according to TS
38.508-1 [4].
ETSI

U-S Message
1 The SS transmits a Paging message including <-- - - -
a matched identity.
2 The UE transmits Preamble on PRACH. --> PRACH Preamble - -
with matching RA-RNTI and including
Temporary C-RNTI. 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 --> HARQ ACK/NACK 1 F
ACK/NACK?
Temporary C-RNTI. The CRC is calculated in
such a way, it will result in CRC pass on UE
side.
ACK/NACK?
8 The UE transmits a MAC PDU containing an --> MAC PDU - -
RRCSetupRequest message.
9 The SS transmits a valid MAC PDU containing <-- MAC PDU - -
RRCSetup, and including ‘UE Contention
Resolution Identity’ MAC control element with
not matching ‘Contention Resolution Identity’.
ACK/NACK?
Temporary C-RNTI.
matching ‘Contention Resolution Identity’. The
CRC is calculated in such a way that it will
result in CRC error on UE side.
15 Check: Does UE transmit a HARQ --> HARQ ACK/NACK 3 F
ACK/NACK?
Temporary C-RNTI.
matching ‘Contention Resolution Identity’. The
CRC is calculated in such a way that it will
result in CRC pass on UE side.
20 Check: does the UE transmit a HARQ ACK? --> HARQ ACK 4 P
RRCSetupComplete message including
SERVICE REQUEST message indicating
acceptance of RRCSetup message
22- Steps 5 to 8 of the generic radio bearer - - - -
25 establishment procedure (TS 38.508 table
4.5.4.2-3) are executed to successfully
complete the service request procedure.
ETSI
None.
7.1.1.2.4 Correct HARQ process handling / BCCH
(1)
ensure that {
when { UE receives a MAC PDU addressed to SI-RNTI on the broadcast HARQ process }
then { UE does not transmit the HARQ feedback for the broadcast HARQ process }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.321, clauses 5.3.2.1 and
5.3.2.2.
[TS 38.321, clause 5.3.2.1]
[TS 38.321, clause 5.3.2.2]
ETSI
1> else:
1> else:
1> else:
NOTE: If the MAC entity receives a retransmission with a TB size different from the last TB size signalled for
this TB, the UE behaviour is left up to UE implementation.
System Simulator:
- NR Cell 1
ETSI
UE:
- None.
Preamble:
- The UE is in state 3N-A with UE test loop mode A activated as defined in 38.508-1 [4].

U-S Message
1 The SS transmits a Short message on PDCCH <-- PDCCH (DCI 1_0): Short - -
using P-RNTI indicating a Message
systemInfoModification. (Note 1)
2 At the start of the modification period, the SS <-- - - -
transmits an updated system information with
SI-RNTI addressed in L1/L2 header. CRC is
fail on UE side. Dedicated HARQ process for
broadcast is used. (Note 5)
3 Check: Does the UE transmit a HARQ --> HARQ ACK/NACK 1 F
ACK/NACK? (Note 2 and 3)
4 After 400ms of step 2, the SS transmits an <-- - - -
updated system information contents same as
in step 2 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.
5 Check: Does the UE transmit a HARQ -> HARQ ACK/NACK 1 F
ACK/NACK? (Note 2 and 4)
6 After 100 ms of Step 4, SS is configured to not - - - -
allocate UL Grants on Scheduling Request.
7 The SS transmits MAC PDU containing an <-- MAC PDU - -
RLC PDU.
8 The UE transmits a HARQ ACK. --> HARQ ACK - -
9 Check: Does the UE transmit PRACH --> PRACH Preamble 1 P
Preamble, using PRACH resources as in new
SI?
11 The UE transmits a MAC PDU with C-RNTI --> MAC PDU - -
containing loop backed RLC PDU.
12 SS sends PDCCH transmission for UE C-RNTI <-- - - -
to complete contention resolution.
Note 1: The Short Message was transmitted in controlResourceSetZero as Configured in SIB1, need 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 38.213 section 9 for a normal
HARQ process.
Note 3: For duration of 400ms, the SS shall check HARQ ACK/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 100 ms, The SS shall check for HARQ ACK/NACK for all broadcast SIBs. This duration is
sufficient to ensure that SS transmits few times SIBs after CRC corruption is removed.
Note 5: The modification period boundaries are defined by SFN values for which SFN mod m = 0, where m is the
number of radio frames comprising the modification period. Value of m is caluclated based on the
parameters specified in TS 38.508-1 [4] i.e m = (modificationPeriodCoeff=4) * (defaultPagingCycle=128
ETSI
Table 7.1.1.2.4.3.3-1: SystemInformationBlockType1 (steps 2 and 4 of table 7.1.1.2.4.3.2-1)

SIB1 ::= SEQUENCE {
initialUplinkBWP SEQUENCE {
rach-ConfigCommon SEQUENCE {
l139 20 FDD
l139 2 TDD
}
}
}
}
}
}
7.1.1.3 Uplink Data Transfer
7.1.1.3.1 Correct Handling of UL MAC PDU / Assignment / HARQ process
(1)
ensure that {
when { UE receives for a Slot an uplink grant with valid C-RNTI }
then { UE transmits data and associated HARQ information to the HARQ entity for this Slot }
}
(2)
ensure that {
when { SS transmits for a Slot an uplink grant with not allocated C-RNTI }
then { UE does not transmits data and associated HARQ information to the HARQ entity for this
Slot }
}
(3)
ensure that {
when { UE receives an UL Grant with toggled NDI and has data available for transmission }
then { UE transmits a new MAC PDU }
}
(4)
with { UE in RRC_CONNECTED state and having transmitted a MAC PDU on a HARQ process }
ensure that {
when { UE receives an uplink grant on PDCCH for the next Slot corresponding to the HARQ process
with old NDI not toggled}
then { UE performs an adaptive retransmission of the MAC PDU with redundancy version as received
on PDCCH }
}
(5)
with { UE in E-UTRA RRC_CONNECTED state }
ETSI
ensure that {
when { UE receives an uplink grant on PDCCH for the next Slot corresponding to the HARQ process
with toggled NDI, and data is not available for transmission }
then { UE transmits any MAC Padding PDU }
}
(6)
ensure that {
when { UE has a MAC SDU to be transmitted that is smaller or equal to 256 bytes }
then { UE sets F field to 0 and includes 8 bit L field in the MAC sub PDU}
}
(7)
ensure that {
when { UE has a MAC SDU to be transmitted that is larger than 256 bytes }
then { UE sets F field to 1 and includes 16 bit L field in the MAC sub PDU }
}
(8)
ensure that {
when { UE has to insert padding in a MAC PDU }
then { UE inserts the last MAC sub PDU as a padding sub PDU }
}
(9)
with { UE in RRC_CONNECTED state and configured with a specific TDD-UL-DL-ConfigCommon including
configuration of pattern2}
ensure that {
when { UE receives for a Slot an uplink grant associated with pattern2 with valid C-RNTI }
then { UE transmits data and associated HARQ information to the HARQ entity for this Slot }
}
[TS 38.321, clause 5.4.1]
Uplink grant is either received dynamically on the PDCCH, in a Random Access Response, or configured semi-
persistently by RRC. The MAC entity shall have an uplink grant to transmit on the UL-SCH. To perform the requested
transmissions, the MAC layer receives HARQ information from lower layers.
If the MAC entity has a C-RNTI, a Temporary C-RNTI or CS-RNTI, the MAC entity shall for each PDCCH occasion
and for each Serving Cell belonging to a TAG that has a running timeAlignmentTimer and for each grant received for
this PDCCH occasion:
1> if an uplink grant for this Serving Cell has been received on the PDCCH for the MAC entity’s C-RNTI or
Temporary C-RNTI; or
1> if an uplink grant has been received in a Random Access Response:
2> if the uplink grant is for MAC entity’s 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 MAC entity’s CS-RNTI or a
configured uplink grant:
3> consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the
NDI.
2> deliver the uplink grant and the associated HARQ information to the HARQ entity.
ETSI
1> else if an uplink grant for this PDCCH occasion has been received for this serving cell on the PDCCH for the
MAC entity’s CS-RNTI:
3> stop the ConfiguredGrantTimer for the corresponding HARQ process, if running;
2> else if the NDI in the received HARQ information is 0:
3> if PDCCH contents indicate configured grant Type 2 deactivation:
4> trigger configured grant confirmation.
3> else if PDCCH contents indicate configured grant Type 2 activation:
4> trigger configured grant confirmation;
4> store the uplink grant for this serving cell and the associated HARQ information as configured uplink
grant;
4> initialise or re-initialise the configured uplink grant for this serving cell to start in the associated
PUSCH duration and to recur according to rules in subclause 5.8.2;
4> set the HARQ Process ID to the HARQ Process ID associated with this PUSCH duration;
4> stop the ConfiguredGrantTimer for the corresponding HARQ process, if running;
4> deliver the configured uplink grant and the associated HARQ information to the HARQ entity.
For each Serving Cell and each configured uplink grant, if configured and activated, the MAC entity shall:
1> if the ConfiguredGrantTimer for the corresponding HARQ process is not running:
NOTE 1: For the same serving cell, an uplink grant addressed to C-RNTI shall override a configured uplink grant
in case of overlap in time domain.
For configured uplink grants, the HARQ Process ID associated with this symbol is derived from the following equation:
HARQ Process ID = [floor(CURRENT_symbol/periodicity)] modulo numberOfConfGrant-Processes
where CURRENT_symbol=(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + slot number in the frame *

numberOfSymbolsPerSlot + symbol number in the slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot
refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively as
NOTE 2: CURRENT_symbol refers to the symbol index of the first transmission of a repetition bundle that takes
place. [TS 36.322, clause 5.4.2.1]
The MAC entity includes a HARQ entity for each Serving Cell with configured uplink (including the case when it is
configured with supplementaryUplink),which maintains a number of parallel HARQ processes.
The number of parallel UL HARQ processes per HARQ entity is specified in TS 38.214 [7].
Each HARQ process supports one TB.
ETSI
Each HARQ process is associated with a HARQ process identifier. For UL transmission with UL grant in RA
Response, HARQ process identifier 0 is used.
When repetition is configured with repK >1, the parameter repK provides the number of repetitions of a TB within a
bundle. Repetition 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 repK.
For each uplink grant, the HARQ entity shall:
1> identify the HARQ process(es) associated with this grant, and for each identified HARQ process:
2> if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the
associated HARQ information has been toggled compared to the value in the previous transmission of this
TB of this HARQ process; or
2> if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is
empty; or
2> if the uplink grant was received in a Random Access Response:
3> if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access
Response:
4> obtain the MAC PDU to transmit from the Msg3 buffer.
3> else:
4> obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity, if any;
3> if a MAC PDU to transmit has been obtained:
4> deliver the MAC PDU and the uplink grant and the HARQ information of the TB to the identified
HARQ process;
4> instruct the identified HARQ process to trigger a new transmission.
4> if the uplink grant is addressed to CS-RNTI or the uplink grant is a configured uplink grant:
5> start or restart the ConfiguredGrantTimer, if configured, for the corresponding HARQ process
when the transmission is performed.
2> else:
3> if the uplink grant received on PDCCH was addressed to CS-RNTI and if the HARQ buffer of the
identified process is empty:
4> ignore the uplink grant.
3> else:
4> deliver the uplink grant and the HARQ information (redundancy version) of the TB to the identified
HARQ process;
4> instruct the identified HARQ process to trigger a retransmission;
4> if the uplink grant is addressed to CS-RNTI or the uplink grant is a configured uplink grant:
5> start or restart the ConfiguredGrantTimer, if configured, for the corresponding HARQ process
When determining if NDI has been toggled compared to the value in the previous transmission the MAC entity shall
ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.
[TS 38.321, clause 5.4.2.2]
Each HARQ process is associated with a HARQ buffer.
ETSI
New transmissions are performed on the resource and with the MCS indicated on either PDCCH, Random Access
Response, or RRC. Retransmissions are performed on the resource and, if provided, with the MCS indicated on
PDCCH.
If the HARQ entity requests a new transmission for a TB, the HARQ process shall:
1> store the MAC PDU in the associated HARQ buffer;
1> store the uplink grant received from the HARQ entity;
1> generate a transmission as described below.
If the HARQ entity requests a retransmission for a TB, the HARQ process shall:
To generate a transmission for a TB, the HARQ process shall:
1> if the MAC PDU was obtained from the Msg3 buffer; or
1> 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:
2> instruct the physical layer to generate a transmission according to the stored uplink grant.
[TS 38.321, clause 6.1.2]
A MAC PDU consists of one or more MAC subPDUs. Each MAC subPDU consists of one of the following:
- A MAC subheader only (including padding);
- A MAC subheader and a MAC SDU;
- A MAC subheader and a MAC CE;
- A MAC subheader and padding.
The MAC SDUs are of variable sizes.
Each MAC subheader corresponds to either a MAC SDU, a MAC CE, or padding.
A MAC subheader except for fixed sized MAC CE and padding consists of the four header fields R/F/LCID/L. A MAC
subheader for fixed sized MAC CE and padding consists of the two header fields R/LCID.
R F LCID Oct 1
L Oct 2
ETSI
R F LCID Oct 1
L Oct 2
L Oct 3
R R LCID Oct 1
Figure 6.1.2-3: R/LCID MAC subheader
MAC CEs are placed together. DL MAC subPDU(s) with MAC CE(s) is placed before any MAC subPDU with MAC
SDU and MAC subPDU with padding as depicted in Figure 6.1.2-4. UL MAC subPDU(s) with MAC CE(s) is placed
after all the MAC subPDU(s) with MAC SDU and before the MAC subPDU with padding in the MAC PDU as
depicted in Figure 6.1.2-5. The size of padding can be zero.
R/LCID Fixed-sized R/F/LCID/L Variable-sized R/F/LCID/L

MAC SDU
subheader MAC CE subheader MAC CE subheader
MAC subPDU
including MAC CE 1
MAC subPDU
including MAC CE 2
MAC SDU
... MAC subPDU including MAC subPDU including
MAC SDU padding (opt)
Figure 6.1.2-4: Example of a DL MAC PDU
R/F/LCID/L R/LCID Fixed-sized R/F/LCID/L Variable-sized

MAC SDU
subheader subheader MAC CE subheader MAC CE
MAC subPDU
including MAC SDU
MAC subPDU
including MAC SDU
... MAC subPDU
including MAC CE 1
MAC subPDU
including MAC CE 2
padding (opt)
Figure 6.1.2-5: Example of a UL MAC PDU
A maximum of one MAC PDU can be transmitted per TB per MAC entity.
ETSI
ETSI

U-S Message
2 SS transmits a MAC PDU including a RLC <-- MAC PDU - -
SDU
- EXCEPTION: Step 3 runs in parallel with - - - -
behaviour in table 7.1.1.3.1.3.2-2
3 For 100 ms SS transmits an UL Grant every 10 <-- (UL Grant (unknown C-RNTI)) - -
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.
4 Check: Does the UE transmit a MAC PDU --> MAC PDU 2 F
corresponding to grant in step 3?
5 SS transmits an UL Grant, allowing the UE to <-- (UL Grant (C-RNTI)) - -
return the RLC SDU as received in step 2, on
PDCCH with the C-RNTI assigned to the UE.
6 Check: Does the UE transmit a MAC PDU --> MAC PDU 1 P
corresponding to grant in step 6?
6A SS transmits a MAC PDU containing an RLC <-- MAC PDU (RLC STATUS PDU) - -
STATUS PDU acknowledging the reception of
the AMD PDUs in step 6.
7 The SS Transmits a valid MAC PDU <-- MAC PDU - -
containing RLC PDU
8 The SS allocates an UL Grant for one HARQ <-- Uplink Grant - -
process X, sufficient for one RLC SDU to be
looped back in a Slot, and NDI indicates new
transmission redundancy version to be used
as 0
including one RLC SDU, in HARQ process X?
10 The SS transmits an UL grant corresponding <-- Uplink Grant - -
to slot for HARQ process X, with NDI not
toggled and redundancy version to be used as
1
11 Check: Does the UE retransmit the MAC PDU --> MAC PDU 4 P
in for HARQ process X, using redundancy
version1?
12 The SS transmits an UL grant corresponding <-- Uplink Grant - -
to SLOT for HARQ process X, with NDI
0
containing padding for HARQ process X, using
redundancy version 0?
PDU of size 128 bytes
15 The SS transmits an UL Grant, allowing the <-- (UL Grant (C-RNTI)) - -
UE to return the RLC SDU as received in step
14 and padding.
16 Check: Does the UE transmit a MAC PDU --> MAC PDU 6,8 P
corresponding to grant in step 14 with F field
set to 0 and includes 8 bit L field in the MAC
sub PDU and includes a padding sub PDU at
end?
ETSI
PDU of size 512 bytes

18 The SS transmits an UL Grant, allowing the <-- (UL Grant (C-RNTI)) - -
UE to return the RLC SDU as received in step
17 and padding.
19 Check: Does the UE transmit a MAC PDU --> MAC PDU 7,8 P
corresponding to grant in step 17 with F field
set to 1 and includes 16 bit L field in the MAC
sub PDU and includes a padding sub PDU at
end?
- EXCEPTION : Steps 20a0 to 20a6 are - - - -
executed for operation on NR TDD band only
20a0 The SS transmits an updated system
14.
20a1 The SS transmits a NR RRCReconfiguration <-- RRCReconfiguration - -
message including TDD-UL-DL-
ConfigCommon with pattern1 and pattern 2
specified in Table 7.1.1.3.1.3.3-5 (Note 1)
20a2 The UE transmit a NR --> RRCReconfigurationComplete - -
(Note 2)
20a3 SS transmits a MAC PDU including a RLC <-- MAC PDU - -
SDU
20a4 SS transmits an UL Grant, allowing the UE to <-- (UL Grant (C-RNTI)) - -
return the RLC SDU as received in step 20a3,
on PDCCH with the C-RNTI assigned to the
UE.
20a5 Check: Does the UE transmit a MAC PDU --> MAC PDU 9 P
corresponding to grant in step 20a4?
20a6 SS transmits a MAC PDU containing an RLC <-- MAC PDU (RLC STATUS PDU) - -
the AMD PDUs in step 20a5.

U-S Message
1 UE transmits a Scheduling Request. --> (SR) - -
ETSI
Table 7.1.1.3.1.3.3-1: Void
Table 7.1.1.3.1.3.3-2: Void
Table 7.1.1.3.1.3.3-3: RRCReconfiguration (step20a1, Table 7.1.1.3.1.3.2-1)

}
RRCReconfiguration-v1530-IEs::= SEQUENCE { NR
}
}
}

on
}
}
}
Table 7.1.1.3.1.3.3-5: ServingCellConfigCommon (Table 7.1.1.3.1.3.3-4, Table 7.1.1.3.1.3.3-14)

}
ConfigCommon
}
ETSI

pattern1 SEQUENCE {
ms0p625 FR2
2 FR2
6 FR2
2 FR2
2 FR2
}
pattern2 SEQUENCE {
ms0p625 FR2
3 FR2
6 FR2
1 FR2
2 FR2
}
}

}
}

}

prach-configurationIndex 156
}
ETSI

}
}

setup PUCCH-Config
}
}
Table 7.1.1.3.1.3.3-12: PUCCH-Config (Table 7.1.1.3.1.3.3-11)

SchedulingRequestResourceConfig[1] SchedulingRequestReso entry 1
urceConfig
}
}
Table 7.1.1.3.1.3.3-13: SchedulingRequestResourceConfig (Table 7.1.1.3.1.3.3-12)

kHz15 results in
repetition every 10
ms
kHz30 results in
repetition every 10
ms
kHz120 results in z
repetition every 10
ms
}
}
ETSI
Table 7.1.1.3.1.3.3-14: SystemInformationBlockType1 (step 20a0, Table 7.1.1.3.1.3.2-1)

SIB1 ::= SEQUENCE {
on in Table
7.1.1.3.1.3.3-5
}
7.1.1.3.2 Logical channel prioritization handling
(1)
with {UE in RRC_CONNECTED state}
ensure that {
when { UE is 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: TS 38.321, clause 5.4.3.1.1,
5.4.3.1.2, 5.4.3.1.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.4.3.1.1]
The Logical Channel Prioritization procedure is applied whenever a new transmission is performed.
RRC controls the scheduling of uplink data by signalling for each logical channel per MAC entity:
- 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).
RRC additionally controls the LCP procedure by configuring mapping restrictions for each logical channel:
- allowedSCS-List which sets the allowed Subcarrier Spacing(s) for transmission;
- maxPUSCH-Duration which sets the maximum PUSCH duration allowed for transmission;
- configuredGrantType1Allowed which sets whether a Configured Grant Type 1 can be used for transmission;
- allowedServingCells which sets the allowed cell(s) for transmission.
The following UE variable is used for the Logical channel prioritization procedure:
- Bj which is maintained for each logical channel j.
The MAC entity shall initialize Bj of the logical channel to zero when the logical channel is established.
For each logical channel j, the MAC entity shall:
1> increment Bj by the product PBR × T before every instance of the LCP procedure, where T is the time elapsed
since Bj was last updated;
1> if the value of Bj is greater than the bucket size (i.e. PBR × BSD):
2> set Bj to the bucket size.
NOTE: The exact moment(s) when the UE updates Bj between LCP procedures is up to UE implementation, as
long as Bj is up to date at the time when a grant is processed by LCP.
ETSI
[TS 38.321, clause 5.4.3.1.2]
The MAC entity shall, when a new transmission is performed:
1> select the logical channels for each UL grant that satisfy all the following conditions:
2> the set of allowed Subcarrier Spacing index values in allowedSCS-List, if configured, includes the Subcarrier
Spacing index associated to the UL grant; and
2> maxPUSCH-Duration, if configured, is larger than or equal to the PUSCH transmission duration associated
to the UL grant; and
2> configuredGrantType1Allowed, if configured, is set to TRUE in case the UL grant is a Configured Grant
Type 1; and
2> allowedServingCells, if configured, includes the Cell information associated to the UL grant.
NOTE: The Subcarrier Spacing index, PUSCH transmission duration and Cell information are included in Uplink
transmission information received from lower layers for the corresponding scheduled uplink transmission.
[TS 38.321, clause 5.4.3.1.3]
1> allocate resources to the logical channels as follows:
2> logical channels selected in subclause 5.4.3.1.2 for the UL grant with Bj > 0 are allocated resources in a
decreasing priority order. If the PBR of a logical channel is set to "infinity", the MAC entity shall allocate
resources for all the data that is available for transmission on the logical channel before meeting the PBR of
the lower priority logical channel(s);
2> decrement Bj by the total size of MAC SDUs served to logical channel j above;
NOTE: The value of Bj can be negative.
2> if any resources remain, all the logical channels selected in subclause 5.4.3.1.2 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 of the
associated MAC entity;
- if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill the
grant of the associated MAC entity as much as possible;
- the UE should maximise the transmission of data;
- if the MAC entity is given an UL grant size that is equal to or larger than 8 bytes while having data available for
transmission, the MAC entity shall not transmit only padding BSR and/or padding.
The MAC entity shall not generate a MAC PDU for the HARQ entity if the following conditions are satisfied:
- the MAC entity is configured with skipUplinkTxDynamic and the grant indicated to the HARQ entity was
addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant; and
- the MAC PDU includes zero MAC SDUs; and
- the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU
includes only the padding BSR.
Logical channels shall be prioritised in accordance with the following order (highest priority listed first):
- MAC CE for C-RNTI or data from UL-CCCH;
ETSI
- MAC CE for SPS confirmation;
- MAC CE for BSR, with exception of BSR included for padding;
- MAC CE for single entry PHR or multiple entry PHR;
- data from any Logical Channel, except data from UL-CCCH;
- MAC CE for BSR included for padding.
Same Pre-test conditions as in clause 7.1.1.0 with the exception of 3 UM SN terminated SCG bearers configured
according to Table 7.1.1.3.2.3.1-1.
Table 7.1.1.3.2.3.1-1: Priority, PBR and Bucket Delay settings

DRB priority prioritizedBitRate bucketSizeDuration
(kbytes/s) (ms)
DRB1 6 8 100
DRB2 7 16 100
DRB3 8 32 100
Table 7.1.1.3.2.3.1-2: PDCP Settings

Parameter Value
Discard_Timer ms1500
ETSI

U-S Message
- EXCEPTION: Steps 1 to 3 are run 4 times - - - -
using the parameters specified for each run in
table 7.1.1.3.2.3.2-3.
1 The SS transmits N1 320-octet RLC SDUs on <-- (RLC SDUs) - -
DRB1, N2 320-octet RLC SDUs on DRB2, and
N3 320-octet RLC SDUs on DRB3.
1A Start WatchDog_Timer set to 5 seconds - - - -
- EXCEPTION: In parallel to the event described - - - -
in step 2 the events specified in Table
7.1.1.3.2.3.2-2 shall take place.
2 The SS is configured for Uplink Grant <-- (UL grants) - -
Allocation Type 2 as defined in TS 38.523-3
[3]. 150 ms after Step 1 (Note1), for a duration
of T2, the SS transmits an UL grant of D octets
every T1.
3 Check: Are the total number of octets of the UL - - 1 P
RLC SDUs received at the SS for each DRB
as follows:
- total number of octets received for DRB1 is
D1 octets +/- 10%
D2 octets +/- 10%
D3 octets +/- 10% ?
4 Wait for WatchDog_Timer expiry(Note2) - - - -
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 i.e.
the bucket size of the corresponding logical channel before the first UL grant is received.
Note 2: Several PDUs on DRB3 after second run and on DRB2 after third run and on DRB1 after fourth run would
be awaiting on PDCP Tx Buffer. Timer 5 seconds ensures the PDCP Data PDUs are discarded after expiry
of Discard_timer(1500ms).

U-S Message
1 Check: Does the UE transmit the RLC SDUs --> - 1 P
back to the SS?
Table 7.1.1.3.2.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) 1153 576 1153 1153
T1 (ms) 20 20 20 10
T2 (ms) 500 700 500 500
D1 (octets) 4160 4160 2240 33350 (Note 1)
D2 (octets) 8000 8000 10435 (Note 1) 8000
D3 (octets) 16000 7790 (Note 1) 16000 16000
Note 1: Calculated using the following equation for the case of the least header size:
(D1 + D2 + D3) = (D - 6) * T2 / T1
NOTE: The Test parameter values above and the test procedure assume that the UE has a loopback buffer of at
least 57280 octets.
ETSI
Table 7.1.1.3.2.3.3-1: SchedulingRequest-Config (Preamble)

sr-TransMax n64
7.1.1.3.2b Logical channel prioritization handling with Mapping restrictions
7.1.1.3.2b.1 Test Purpose (TP)
(1)
with {UE in RRC_CONNECTED state with allowedSCS-List configured }
ensure that {
then { UE serves the logical channels according to their priority and configured PBR and
respecting allowedSCS-List }
}
(2)
with {UE in RRC_CONNECTED state with maxPUSCH-Duration configured }
ensure that {
respecting maxPUSCH-Duration }
}
(3)
with { UE in RRC_CONNECTED state with configuredGrantType1Allowed configured and supporting Type 1
PUSCH transmissions with configured grant }
ensure that {
respecting configuredGrantType1Allowed }
}
7.1.1.3.2b.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.321, clause 5.4.3.1.1,
5.4.3.1.2, 5.4.3.1.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.4.3.1.1]
The Logical Channel Prioritization (LCP) procedure is applied whenever a new transmission is performed.
RRC controls the scheduling of uplink data by signalling for each logical channel per MAC entity:
- 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).
RRC additionally controls the LCP procedure by configuring mapping restrictions for each logical channel:
- allowedSCS-List which sets the allowed Subcarrier Spacing(s) for transmission;
- maxPUSCH-Duration which sets the maximum PUSCH duration allowed for transmission;
- configuredGrantType1Allowed which sets whether a configured grant Type 1 can be used for transmission;
- allowedServingCells which sets the allowed cell(s) for transmission.
ETSI
The following UE variable is used for the Logical channel prioritization procedure:
- Bj which is maintained for each logical channel j.
The MAC entity shall initialize Bj of the logical channel to zero when the logical channel is established.
For each logical channel j, the MAC entity shall:
1> increment Bj by the product PBR × T before every instance of the LCP procedure, where T is the time elapsed
since Bj was last incremented;
1> if the value of Bj is greater than the bucket size (i.e. PBR × BSD):
2> set Bj to the bucket size.
NOTE: The exact moment(s) when the UE updates Bj between LCP procedures is up to UE implementation, as
long as Bj is up to date at the time when a grant is processed by LCP.
[TS 38.321, clause 5.4.3.1.2]
1> select the logical channels for each UL grant that satisfy all the following conditions:
2> the set of allowed Subcarrier Spacing index values in allowedSCS-List, if configured, includes the Subcarrier
Spacing index associated to the UL grant; and
2> maxPUSCH-Duration, if configured, is larger than or equal to the PUSCH transmission duration associated
to the UL grant; and
2> configuredGrantType1Allowed, if configured, is set to true in case the UL grant is a Configured Grant Type
1; and
2> allowedServingCells, if configured, includes the Cell information associated to the UL grant. Does not apply
to logical channels associated with a DRB configured with PDCP duplication within the same MAC entity
(i.e. CA duplication) for which PDCP duplication is deactivated.
NOTE: The Subcarrier Spacing index, PUSCH transmission duration and Cell information are included in Uplink
transmission information received from lower layers for the corresponding scheduled uplink transmission.
[TS 38.321, clause 5.4.3.1.3]
1> allocate resources to the logical channels as follows:
2> logical channels selected in subclause 5.4.3.1.2 for the UL grant with Bj > 0 are allocated resources in a
decreasing priority order. If the PBR of a logical channel is set to infinity, the MAC entity shall allocate
resources for all the data that is available for transmission on the logical channel before meeting the PBR of
the lower priority logical channel(s);
2> decrement Bj by the total size of MAC SDUs served to logical channel j above;
2> if any resources remain, all the logical channels selected in subclause 5.4.3.1.2 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.
NOTE: The value of Bj can be negative.
If the MAC entity is requested to simultaneously transmit multiple MAC PDUs, or if the MAC entity receives the
multiple UL grants within one or more coinciding PDCCH occasions (i.e. on different Serving Cells), it is up to UE
implementation in which order the grants are processed.
The UE shall also follow the rules below during the scheduling procedures above:
ETSI
- 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 of the
associated MAC entity;
- if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill the
grant of the associated MAC entity as much as possible;
- the UE should maximise the transmission of data;
- if the MAC entity is given a UL grant size that is equal to or larger than 8 bytes while having data available and
allowed (according to subclause 5.4.3.1) for transmission, the MAC entity shall not transmit only padding BSR
and/or padding.
The MAC entity shall not generate a MAC PDU for the HARQ entity if the following conditions are satisfied:
- the MAC entity is configured with skipUplinkTxDynamic with value true and the grant indicated to the HARQ
entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant; and
- there is no aperiodic CSI requested for this PUSCH transmission as specified in TS 38.212 [9]; and
- the MAC PDU includes zero MAC SDUs; and
- the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU
includes only the padding BSR.
- C-RNTI MAC CE or data from UL-CCCH;
- Configured Grant Confirmation MAC CE;
- Single Entry PHR MAC CE or Multiple Entry PHR MAC CE;
- MAC CE for Recommended bit rate query;
7.1.1.3.2b.3 Test description
7.1.1.3.2b.3.1 Pre-test conditions
Same Pre-test conditions as in clause 7.1.1.0 with the exception of 3 UM NR DRBs configured according to Table
7.1.1.3.2b.3.1-1.
Table 7.1.1.3.2b.3.1-1: Priority, PBR, Bucket Delay allowed-SCSList settings

DRB priority prioritizedBitRate bucketSize allowed-SCSList
(kbytes/s) Duration
FR1 FR2
(ms)
DRB1 6 8 100 {15KHz, {60KHz,
30KHz} 120KHz}
DRB2 7 16 100 {60KHz} {60KHz}
DRB3 8 32 100 {15KHz, {120KHz}
30KHz,60KH
z}
ETSI
Table 7.1.1.3.2b.3.1-2: allowed-SCSList and maxPUSCH-Duration settings

DRB allowed-SCSList maxPUSCH-
Duration
DRB1 Not Present ms0p02
Table 7.1.1.3.2b.3.1-2a: PUSCH-TimeDomainResourceAllocationList
Derivation Path: TS 38.508-1 [4], table 4.6.3-122

PUSCH-TimeDomainResourceAllocationList ::= 2 entry
SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF
PUSCH-TimeDomainResourceAllocation {
PUSCH-TimeDomainResourceAllocation[1] entry 1
SEQUENCE {
k2 2 FR1
4 FR2
mappingType typeB
startSymbolAndLength 52 Start FR1
symbol(S)=10,
Length(L)=4
symbol(S)=0,
Length(L)=4
}
PUSCH-TimeDomainResourceAllocation[2] entry 2
SEQUENCE {
k2 2 FR1
4 FR2
mappingType typeB
startSymbolAndLength 27 Start
symbol(S)=0,
Length(L)=14
}
}
Table 7.1.1.3.2b.3.1-3: maxPUSCH-Duration and configuredGrantType1Allowed settings

DRB maxPUSCH- configuredGrant
Duration Type1Allowed
DRB1 Not Present true

DRB2 Not Present false
DRB3 Not Present true
Table 7.1.1.3.2b.3.1-4: PDCP Settings

Parameter Value
Discard_Timer ms1500
ETSI
7.1.1.3.2b.3.2 Test procedure sequence
Table 7.1.1.3.2b.3.2-1: Main behaviour

U-S Message
- EXCEPTION: Steps 1 to 3 are run using the - - - -
parameters specified for first run in table
7.1.1.3.2b.3.2-3.
7.1.1.3.2b.3.2-2 shall take place.
every T1.
as follows:
D1 octets +/- 10%
- total number of octets received for DRB2 is 0
D3 octets +/- 10% otherwise?
4 SS transmits NR RRCReconfiguration <-- (NR RRC: RRCReconfiguration) - -
message to configure allowed-SCSList and
maxPUSCH-Duration as per Table
7.1.1.3.2b.3.1-2. (Note 2)
7.1.1.3.2b.3.2-2a shall take place on DRB2
5 The UE transmits NR --> (NR RRC: - -
RRCReconfigurationComplete message. (Note RRCReconfigurationComplete)
3)
parameters specified for second run in table
7.1.1.3.2b.3.1-2.
every T1.
as follows:
- total number of octets received for DRB1 are
0
D2 octets +/- 10%
D3 octets +/- 10%?
- EXCEPTION: Steps 9 to 14 describe - - - -
behaviour that depends on the UE capability.
9 IF pc_configuredUL_GrantType1 the SS <-- (NR RRC: RRCReconfiguration) - -
transmits NR RRCReconfiguration message to
configure UL configured grant type 1 with UL
grant configured 150 ms after Step 11 (Note1),
ETSI
for a duration of T2 and an UL grant of D

octets every T1. It also configures
maxPUSCH-Duration and
configuredGrantType1Allowed as per Table
7.1.1.3.2b.3.1-3 (Note 2)
7.1.1.3.2b.3.2-2a shall take place on DRB1
3)
parameters specified for third run in table
7.1.1.3.2b.3.1-1.
as follows:
D1 octets +/- 10%
0
D3 octets +/- 10%?
13 The SS sends one Uplink Grant to send loop <-- (UL grants) - -
back PDU on DRB 2.
14 The UE transmits the RLC SDU back to the --> - - -
SS.
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 i.e.
the bucket size of the corresponding logical channel before the first UL grant is received.
RRCConnectionReconfigurationComplete
Table 7.1.1.3.2b.3.2-2: Parallel behaviour

U–S Message
1 Check: Does the UE transmit the RLC SDUs --> - 1,2, P
back to the SS? 3
Table 7.1.1.3.2b.3.2-2a: Parallel behaviour

U–S Message
1 The UE may transmit the RLC SDU back to --> - - -
the SS within one second.
ETSI
Table 7.1.1.3.2b.3.2-3: Test parameter values

Parameter First run Second run Third run
N1 (SDUs) 13 1 13
N2 (SDUs) 1 25 1
N3 (SDUs) 50 50 50
D (octets) 1153 576 1153
T1 (ms) 20 20 20
T2 (ms) 360 860 360
D1 (octets) 4160 0 4160
D2 (octets) 0 8000 0
D3 (octets) 16000 16000 16000
Note 1: Calculated using the following equation for the case of the least header
size:(D1 + D2 + D3) = (D - 6) * T2 / T1.
7.1.1.3.2b.3.3 Specific message contents
Table 7.1.1.3.2b.3.3-1: SchedulingRequest-Config (Preamble)
Derivation Path: 36.508 [7], Table 4.6.3-20

sr-TransMax n64
Table 7.1.1.3.2b.3.3-2: RRCReconfiguration (step 9, Table 7.1.1.3.2b.3.2-1)

radioBearerConfig Not present
(CONTAINING
CellGroupConfig)
nonCriticalExtension := SEQUENCE {} Not present EN-DC
nonCriticalExtension := SEQUENCE{ NR
(CONTAINING
CellGroupConfig)
dedicatedNAS-MessageList SEQUENCE Not present
(SIZE(1..maxDRB)) OF DedicatedNAS-Message {}
}
}
}
}
ETSI
Table 7.1.1.3.2b.3.3-3: CellGroupConfig (Table 7.1.1.3.2b.3.3-2: RRCReconfiguration)

rlc-BearerToAddModList Not present
mac-CellGroupConfig Not present
physicalCellGroupConfig SEQUENCE {
cs-RNTI CHOICE {
setup SEQUENCE{
RNTI-Value ‘FFE0’H
}
}
}
spCellConfig SEQUENCE{
servCellIndex Not present NR
1 EN-DC
reconfigurationWithSync Not present
spCellConfigDedicated SEQUENCE{
setup SEQUENCE {
schedulingRequestResourceToAddModList {
schedulingRequestResourceId 1
schedulingRequestID 0
sl20 10
}
}
}
}
configuredGrantConfig CHOICE {
setup SEQUENCE {
cg-DMRS-Configuration DMRS-UplinkConfig Reference TS
38.508-1[4], Table
4.6.3-51
uci-OnPUSCH CHOICE {
setup SEQUENCE {
semiStatic SEQUENCE { BetaOffsets
betaOffsetACK-Index1 9
betaOffsetCSI-Part1-Index1 6
}
}
}
resourceAllocation ResourceAllocationType
1
powerControlLoopToUse n0
p0-PUSCH-Alpha 1
nrofHARQ-Processes 16
repK n1
periodicity Sym20x14 15kHz
rrc-ConfiguredUplinkGrant SEQUENCE{
timeDomainOffset 0
timeDomainAllocation 0 Reference TS
38.508-1 [4], Table
4.6.3-122
frequencyDomainAllocation BIT STRING (SIZE(18) BIT STRING
ETSI
(SIZE(18), Equal to
NBWPsize * (LRB-
1) + RBstart),
where
LRB = 23 PRB,
RBstart = 0,
NBWPsize is the
size [PRBs] of the
active carrier
bandwidth part and
ontained in
TS.38.508-1 [4]
clause 4.3.1.1.
antennaPort 0
precodingAndNumberOfLayers 0
srs-ResourceIndicator Not present
mcsAndTBS 16
pathlossReferenceIndex 0
}
}
}
7.1.1.3.3 Correct handling of MAC control information / Scheduling requests
(1)
with { UE in RRC_CONNECTED state with SR resource on PUCCH is configured }
ensure that {
when { UE has UL data available for transmission and UE has no UL-SCH resources available and
SR_COUNTER is less than sr-TransMax }
then { the UE transmits a SR on every available PUCCH until resources are granted }
}
(2)
ensure that {
when { UE receives an UL grant for a new transmission }
then { UE cancels all pending SR(s) }
}
(3)
ensure that {
when { UE has UL data available for transmission and UE has no UL-SCH resources available and
SR_COUNTER becomes equal to sr-TransMax }
then { the UE transmits a PRACH Preamble to initiate a Random Access procedure }
}
(4)
with { UE in RRC_CONNECTED state with SR resource on PUCCH is configured and logicalChannelSR-
DelayTimer is configured }
ensure that {
when { UE has UL data available for transmission on LCH for which logicalChannelSR-DelayTimer is
configured and UE has no UL-SCH resources available and SR_COUNTER is less than sr-TransMax }
then { the UE delays transmission of SR until logicalChannelSR-DelayTimer expires }
}
(5)
ensure that {
ETSI
when { UE has UL data available for transmission on LCH for which logicalChannelSR-DelayTimer is
not configured and UE has no UL-SCH resources available and SR_COUNTER is less than sr-TransMax }
then { the UE transmits a SR on every available PUCCH until resources are granted }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.321, clauses 5.4.4 and
[TS 38.321, clause 5.4.4]
The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.
The MAC entity may be configured with zero, one, or more SR configurations. An SR configuration consists of a set of
PUCCH resources for SR across different BWPs and cells. For a logical channel, at most one PUCCH resource for SR
is configured per BWP.
Each SR configuration corresponds to one or more logical channels. Each logical channel may be mapped to zero or
one SR configuration, which is configured by RRC. The SR configuration of the LCH that triggered the BSR (subclause
5.4.5) (if such a configuration exists) is considered as corresponding SR configuration for the triggered SR. For BSR
triggered by retxBSR-Timer expiry, the corresponding SR configuration for the triggered SR is that of the highest
priority LCH (if such a configuration exists) that has data available for transmission at the time the BSR is triggered.
RRC configures the following parameters for the scheduling request procedure:
- sr-ProhibitTimer (per SR configuration);
- sr-TransMax (per SR configuration);
- sr-ConfigIndex.
The following UE variables are used for the scheduling request procedure:
- SR_COUNTER (per SR configuration).
If an SR is triggered and there are no other SRs pending corresponding to the same SR configuration, the MAC entity
shall set the SR_COUNTER of the corresponding SR configuration to 0.
When an SR is triggered, it shall be considered as pending until it is cancelled. All pending SR(s) shall be cancelled and
each respective sr-ProhibitTimer shall be stopped when a MAC PDU is assembled and this PDU includes a BSR which
contains buffer status up to (and including) the last event that triggered a BSR (see subclause 5.4.5), or when the UL
grant(s) can accommodate all pending data available for transmission.
Only PUCCH resources on a BWP which is active at the time of SR transmission occasion are considered valid.
As long as at least one SR is pending, the MAC entity shall for each pending SR:
1> if the MAC entity has no valid PUCCH resource configured for the pending SR:
2> initiate a Random Access procedure (see subclause 5.1) on the SpCell and cancel the pending SR.
1> else, for the SR configuration corresponding to the pending SR:
2> when the MAC entity has an SR transmission occasion on the valid PUCCH resource for SR configured; and
2> if sr-ProhibitTimer is not running at the time of the SR transmission occasion; and
2> if the PUCCH resource for the SR transmission occasion does not overlap with a measurement gap; and
2> if the PUCCH resource for the SR transmission occasion does not overlap with a UL-SCH resource:
3> if SR_COUNTER < sr-TransMax:
4> increment SR_COUNTER by 1;
4> instruct the physical layer to signal the SR on one valid PUCCH resource for SR;
ETSI
4> start the sr-ProhibitTimer.
3> else:
4> notify RRC to release PUCCH for all serving cells;
4> notify RRC to release SRS for all serving cells;
4> clear any configured downlink assignments and uplink grants;
4> initiate a Random Access procedure (see subclause 5.1) on the SpCell and cancel all pending SRs.
NOTE: The selection of which valid PUCCH resource for SR to signal SR on when the MAC entity has more
than one overlapping valid PUCCH resource for the SR transmission occasion is left to UE
implementation.
[TS 38.321, clause 5.4.5]
For Regular BSR, the MAC entity shall:
1> if the BSR is triggered for a logical channel for which logicalChannelSR-Delay is configured by upper layers:
2> start or restart the logicalChannelSR-DelayTimer.
1> else:
2> if running, stop the logicalChannelSR-DelayTimer.
1> if the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:
2> if UL-SCH resources are available for a new immediate transmission:
3> instruct the Multiplexing and Assembly procedure to generate the BSR MAC CE(s);
3> start or restart periodicBSR-Timer except when all the generated BSRs are long or short Truncated BSRs;
3> start or restart retxBSR-Timer.
2> else if a Regular BSR has been triggered and logicalChannelSR-DelayTimer is not running:
3> if an uplink grant is not a configured grant; or
3> if the Regular BSR was not triggered for a logical channel for which logical channel SR masking
(logicalChannelSR-Mask) is setup by upper layers:
4> trigger a Scheduling Request.
Same Pre-test conditions as in clause 7.1.1.0 with the exception of 2 AM DRBs configured according to Table
7.1.1.3.3.3.1-1 and Table 7.1.1.3.3.3.1-2.
ETSI
Table 7.1.1.3.3.3.1-1: Logical Channel Configuration Settings

Parameter DRB1 DRB2
LogicalChannelIdentity LCH4(DRB- LCH5(DRB-
Identity +3) Identity +3)
Priority 7 6
prioritizedBitRate 0kbs 0kbs
logicalChannelGroup 2 (LCG ID#2) 1 (LCG ID#1)
logicalChannelSR- False True
DelayTimerApplied
logicalChannelSR-DelayTimer Not Present sf512
Table 7.1.1.3.3.3.1-2: RLC parameters
t-PollRetransmit ms80
ETSI

U-S Message
1 The SS transmits a MAC PDU containing A <-- MAC PDU (containing 1 MAC sub - -
MAC Sub PDU containing a RLC SDU on LCH PDU)
5
2 Check: Does the UE transmit Scheduling --> (SR) 4 F
Requests for logicalChannelSR-DelayTimer
(sf512) from step 1?
3 Check: Does the UE transmit [x] Scheduling --> (SR) 1,4 P
Requests separately on [x] consecutively
available PUCCHs after logicalChannelSR-
DelayTimer expiry? (Note 1)
4 The SS transmits an UL grant to allocate UL- <-- (UL Grant) - -
SCH resources that are enough to transmit
looped back PDU
5 Check: Does the UE transmit a MAC PDU --> MAC PDU (containing 1 MAC sub 1 P
containing MAC Sub PDU containing a RLC PDU containing RLC SDU)
SDU on LCH5?
6 The SS transmits a MAC PDU containing A <-- MAC PDU (containing 1 MAC sub - -
MAC Sub PDU containing a RLC SDU on LCH PDU)
4
7 Check: Does the UE transmit Scheduling --> (SR) 1,5 P
Requests separately on [x] consecutively
available PUCCHs? (Note 1)
8 The SS transmits an UL grant to allocate UL- <-- (UL Grant ) - -
SCH resources that are enough to transmit
looped back PDU
9 Check: Does the UE transmit a MAC PDU --> MAC PDU (containing 1 MAC sub 1 P
containing MAC Sub PDU containing a RLC PDU containing RLC SDU)
SDU on LCH4?
10 Check: For 1 second, does the UE transmit a --> (SR) 1,2 F
Scheduling Request?
11 The SS transmits a MAC PDU containing a <-- MAC PDU (Timing Advance - -
Timing Advance Command MAC Control Command)
Element, but does not send any subsequent
alignments.
12 The SS transmits a MAC PDU containing a <-- MAC PDU (MAC SDU) - -
MAC SDU on LCH 4
- EXCEPTION: Step 13 is repeated less than sr- - - - -
TransMax times
13 The UE may transmit Scheduling Requests --> (SR) - -
before time alignment timer expires. The SS
shall not respond to the Scheduling Requests
in this step. (Note 2)
14 Check: does the UE transmit a preamble on --> (PRACH Preamble) 3 P
PRACH?
15 The SS transmits a Random Access Response <-- 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 14.
16 The UE transmit a MAC PDU including a C- --> MAC PDU (MAC Sub PDU - -
RNTI MAC Control Element and a MAC SDU. containing C-RNTI control
(Note 3) element, MAC sub PDU
containing MAC SDU)
17 The SS sends PDCCH transmission for UE C- <-- - - -
RNTI
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 10 Scheduling Requests.
Note 2: In step 8, SR repetition of [63] times (sr-TransMax (64)) will take at least [63*10 = 630] ms which is smaller
than TA timer [infinity].
Note 3: The UE transmission of the MAC PDU ensures that the random access procedure was successful.
ETSI
Table 7.1.1.3.3.3.3-1: SchedulingRequestConfig (Preamble)

SchedulingRequestConfig ::= SEQUENCE { 1 entry
schedulingRequestToAddModList
(SIZE(1..maxNrofSR-ConfigPerCellGroup)) OF
SSchedulingRequestToAddMod {
SchedulingRequestToAddMod[1] SEQUENCE { entry 1
sr-TransMax n64 MAX Value
}
}
7.1.1.3.4 Correct handling of MAC control information / Buffer status / UL data arrive in the
UE Tx buffer / Regular BSR
(1)
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 available 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) }
}
(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 available 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 that {
when { retxBSR-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)
ensure that {
when { a Regular BSR has been triggered and UE has pending data for transmission and UE has only
resources to send either BSR report or data }
then { UE transmits the BSR report }
ETSI
(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)
Void.
(8)
ensure that {
when { a Regular BSR has been triggered and UE has pending data on several logical channels for
transmission and UE has UL resources to send all pending data including BSR }
then { UE transmits the UL data and reports buffer status reporting (BSR) that indicates there
is no more data in the buffer }
}
6.1.3.1, 6.2.1 and TS 38.323 clause 5.6. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.4.3.1.3]
- C-RNTI MAC CE or data from UL-CCCH;
- Configured Grant Confirmation MAC CE;
- Single Entry PHR MAC CE or Multiple Entry PHR MAC CE;
- MAC CE for Recommended bit rate query;
[TS 38.321, clause 5.4.5]
The Buffer Status reporting (BSR) procedure is used to provide the serving gNB with information about UL data
volume in the MAC entity.
RRC configures the following parameters to control the BSR:
- periodicBSR-Timer;
- retxBSR-Timer;
- logicalChannelSR-Delay;
- logicalChannelSR-DelayTimer;
- logicalChannelGroup.
Each logical channel may be allocated to an LCG using the logicalChannelGroup. The maximum number of LCGs is
eight.
ETSI
The MAC entity determines the amount of UL data available for a logical channel according to the data volume
calculation procedure in TSs 38.322 and 38.323 [3] [4].
A BSR shall be triggered if any of the following events occur:
- the MAC entity has new UL data available for a logical channel which belongs to an LCG; and either
- the new UL data belongs to a logical channel with higher priority than the priority of any logical channel
containing available UL data which belong to any LCG; or
- none of the logical channels which belong to an LCG contains any available UL data.
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 CE plus its subheader, in which case the BSR is referred below to as 'Padding BSR';
- retxBSR-Timer expires, and at least one of the logical channels which belong to an LCG contains UL data, 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'.
1> else:
For Regular and Periodic BSR, the MAC entity shall:
1> if more than one LCG has data available for transmission when the BSR is to be transmitted:
2> report Long BSR for all LCGs which have data available for transmission.
1> else:
2> report Short BSR.
For Padding BSR:
1> 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:
3> if the number of padding bits is equal to the size of the Short BSR plus its subheader:
4> report Short Truncated BSR of the LCG with the highest priority logical channel with data available
for transmission.
3> else:
4> report Long Truncated BSR of the LCG(s) with the logical channels having data available for
transmission following a decreasing order of priority, and in case of equal priority, in increasing order
of LCGID.
2> else:
3> report Short BSR;
1> else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader:
ETSI
A MAC PDU shall contain at most one BSR MAC CE, even when multiple events have triggered a BSR by the time.
The Regular BSR and the Periodic BSR shall have precedence over the padding BSR.
The MAC entity shall restart retxBSR-Timer upon reception of a grant for transmission of new data on any UL-SCH.
All triggered BSRs may be cancelled when the UL grant(s) 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.
The MAC entity shall transmit at most one BSR in one MAC PDU. Padding BSR shall not be included when the MAC
PDU contains a Regular or Periodic BSR.
[TS 38.321, clause 6.1.3.1]
Buffer Status Report (BSR) MAC CEs consist of either:
- Short BSR format (fixed size); or
- Long BSR format (variable size); or
- Short Truncated BSR format (fixed size); or
- Long Truncated BSR format (variable size).
The BSR formats are identified by MAC PDU subheaders with LCIDs as specified in Table 6.2.1-2.
The fields in the BSR MAC CE are defined as follows:
- LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) whose buffer status is
being reported. The length of the field is 3 bits;
- LCGi: For the Long BSR format, this field indicates the presence of the Buffer Size field for the logical channel
group i. The LCGi field set to "1" indicates that the Buffer Size field for the logical channel group i is reported.
The LCGi field set to "0" indicates that the Buffer Size field for the logical channel group i is not reported. For
the Long Truncated BSR format, this field indicates whether logical channel group i has data available. The
LCGi field set to "1" indicates that logical channel group i has data available. The LCGi field set to "0" indicates
that logical channel group i does not have data available;
- Buffer Size: The Buffer Size field identifies the total amount of data available according to the data volume
calculation procedure in TSs 38.322 and 38.323 [3] [4] across all logical channels of a logical channel group
after the MAC PDU has been built (i.e. after the logical channel prioritization procedure, which may result the
value of the Buffer Size field to zero). The amount of data is indicated in number of bytes. The size of the RLC
and MAC headers are not considered in the buffer size computation. The length of this field for the Short BSR
format and the Short Truncated BSR format is 5 bits. The length of this field for the Long BSR format and the
Long Truncated BSR format is 8 bits. The values for the 5-bit and 8-bit Buffer Size fields are shown in Tables
6.1.3.1-1 and 6.1.3.1-2, respectively. For the Long BSR format and the Long Truncated BSR format, the Buffer
ETSI
Size fields are included in ascending order based on the LCGi. For the Long Truncated BSR format the number
of Buffer Size fields included is maximised, while not exceeding the number of padding bits.
NOTE: The number of the Buffer Size fields in the Long Truncated BSR format can be zero.
LCG ID Buffer Size Oct 1
Figure 6.1.3.1-1: Short BSR and Short Truncated BSR MAC CE
LCG7 LCG6 LCG5 LCG4 LCG3 LCG2 LCG1 LCG0 Oct 1
Buffer Size 1 Oct 2
Buffer Size 2 Oct 3
...
Buffer Size m Oct m+1
Figure 6.1.3.1-2: Long BSR and Long Truncated BSR MAC CE
Table 6.1.3.1-1: Buffer size levels (in bytes) for 5-bit Buffer Size field
Index BS value Index BS value Index BS value Index BS value

0 0 8 ≤ 102 16 ≤ 1446 24 ≤ 20516
1 ≤ 10 9 ≤ 142 17 ≤ 2014 25 ≤ 28581
2 ≤ 14 10 ≤ 198 18 ≤ 2806 26 ≤ 39818
3 ≤ 20 11 ≤ 276 19 ≤ 3909 27 ≤ 55474
4 ≤ 28 12 ≤ 384 20 ≤ 5446 28 ≤ 77284
5 ≤ 38 13 ≤ 535 21 ≤ 7587 29 ≤ 107669
6 ≤ 53 14 ≤ 745 22 ≤ 10570 30 ≤ 150000
7 ≤ 74 15 ≤ 1038 23 ≤ 14726 31 > 150000
ETSI

0 0 64 ≤ 560 128 ≤ 31342 192 ≤ 1754595
1 ≤ 10 65 ≤ 597 129 ≤ 33376 193 ≤ 1868488
2 ≤ 11 66 ≤ 635 130 ≤ 35543 194 ≤ 1989774
3 ≤ 12 67 ≤ 677 131 ≤ 37850 195 ≤ 2118933
4 ≤ 13 68 ≤ 720 132 ≤ 40307 196 ≤ 2256475
5 ≤ 14 69 ≤ 767 133 ≤ 42923 197 ≤ 2402946
6 ≤ 15 70 ≤ 817 134 ≤ 45709 198 ≤ 2558924
7 ≤ 16 71 ≤ 870 135 ≤ 48676 199 ≤ 2725027
8 ≤ 17 72 ≤ 926 136 ≤ 51836 200 ≤ 2901912
9 ≤ 18 73 ≤ 987 137 ≤ 55200 201 ≤ 3090279
10 ≤ 19 74 ≤ 1051 138 ≤ 58784 202 ≤ 3290873
11 ≤ 20 75 ≤ 1119 139 ≤ 62599 203 ≤ 3504487
12 ≤ 22 76 ≤ 1191 140 ≤ 66663 204 ≤ 3731968
13 ≤ 23 77 ≤ 1269 141 ≤ 70990 205 ≤ 3974215
14 ≤ 25 78 ≤ 1351 142 ≤ 75598 206 ≤ 4232186
15 ≤ 26 79 ≤ 1439 143 ≤ 80505 207 ≤ 4506902
16 ≤ 28 80 ≤ 1532 144 ≤ 85730 208 ≤ 4799451
17 ≤ 30 81 ≤ 1631 145 ≤ 91295 209 ≤ 5110989
18 ≤ 32 82 ≤ 1737 146 ≤ 97221 210 ≤ 5442750
19 ≤ 34 83 ≤ 1850 147 ≤ 103532 211 ≤ 5796046
20 ≤ 36 84 ≤ 1970 148 ≤ 110252 212 ≤ 6172275
21 ≤ 38 85 ≤ 2098 149 ≤ 117409 213 ≤ 6572925
22 ≤ 40 86 ≤ 2234 150 ≤ 125030 214 ≤ 6999582
23 ≤ 43 87 ≤ 2379 151 ≤ 133146 215 ≤ 7453933
24 ≤ 46 88 ≤ 2533 152 ≤ 141789 216 ≤ 7937777
25 ≤ 49 89 ≤ 2698 153 ≤ 150992 217 ≤ 8453028
26 ≤ 52 90 ≤ 2873 154 ≤ 160793 218 ≤ 9001725
27 ≤ 55 91 ≤ 3059 155 ≤ 171231 219 ≤ 9586039
28 ≤ 59 92 ≤ 3258 156 ≤ 182345 220 ≤ 10208280
29 ≤ 62 93 ≤ 3469 157 ≤ 194182 221 ≤ 10870913
30 ≤ 66 94 ≤ 3694 158 ≤ 206786 222 ≤ 11576557
31 ≤ 71 95 ≤ 3934 159 ≤ 220209 223 ≤ 12328006
32 ≤ 75 96 ≤ 4189 160 ≤ 234503 224 ≤ 13128233
33 ≤ 80 97 ≤ 4461 161 ≤ 249725 225 ≤ 13980403
34 ≤ 85 98 ≤ 4751 162 ≤ 265935 226 ≤ 14887889
35 ≤ 91 99 ≤ 5059 163 ≤ 283197 227 ≤ 15854280
36 ≤ 97 100 ≤ 5387 164 ≤ 301579 228 ≤ 16883401
37 ≤ 103 101 ≤ 5737 165 ≤ 321155 229 ≤ 17979324
38 ≤ 110 102 ≤ 6109 166 ≤ 342002 230 ≤ 19146385
39 ≤ 117 103 ≤ 6506 167 ≤ 364202 231 ≤ 20389201
40 ≤ 124 104 ≤ 6928 168 ≤ 387842 232 ≤ 21712690
41 ≤ 132 105 ≤ 7378 169 ≤ 413018 233 ≤ 23122088
42 ≤ 141 106 ≤ 7857 170 ≤ 439827 234 ≤ 24622972
43 ≤ 150 107 ≤ 8367 171 ≤ 468377 235 ≤ 26221280
44 ≤ 160 108 ≤ 8910 172 ≤ 498780 236 ≤ 27923336
45 ≤ 170 109 ≤ 9488 173 ≤ 531156 237 ≤ 29735875
46 ≤ 181 110 ≤ 10104 174 ≤ 565634 238 ≤ 31666069
47 ≤ 193 111 ≤ 10760 175 ≤ 602350 239 ≤ 33721553
48 ≤ 205 112 ≤ 11458 176 ≤ 641449 240 ≤ 35910462
49 ≤ 218 113 ≤ 12202 177 ≤ 683087 241 ≤ 38241455
50 ≤ 233 114 ≤ 12994 178 ≤ 727427 242 ≤ 40723756
51 ≤ 248 115 ≤ 13838 179 ≤ 774645 243 ≤ 43367187
52 ≤ 264 116 ≤ 14736 180 ≤ 824928 244 ≤ 46182206
53 ≤ 281 117 ≤ 15692 181 ≤ 878475 245 ≤ 49179951
54 ≤ 299 118 ≤ 16711 182 ≤ 935498 246 ≤ 52372284
55 ≤ 318 119 ≤ 17795 183 ≤ 996222 247 ≤ 55771835
56 ≤ 339 120 ≤ 18951 184 ≤ 1060888 248 ≤ 59392055
57 ≤ 361 121 ≤ 20181 185 ≤ 1129752 249 ≤ 63247269
58 ≤ 384 122 ≤ 21491 186 ≤ 1203085 250 ≤ 67352729
59 ≤ 409 123 ≤ 22885 187 ≤ 1281179 251 ≤ 71724679
60 ≤ 436 124 ≤ 24371 188 ≤ 1364342 252 ≤ 76380419
61 ≤ 464 125 ≤ 25953 189 ≤ 1452903 253 ≤ 81338368
ETSI
62 ≤ 494 126 ≤ 27638 190 ≤ 1547213 254 > 81338368

63 ≤ 526 127 ≤ 29431 191 ≤ 1647644 255 Reserved
[TS 38.321, clause 6.2.1]
Table 6.2.1-2 Values of LCID for UL-SCH
Index LCID values

000000 CCCH
000001–100000 Identity of the logical channel
100001–110110 Reserved
110111 Configured Grant Confirmation
111000 Multiple Entry PHR
111001 Single Entry PHR
111010 C-RNTI
111011 Short Truncated BSR
111100 Long Truncated BSR
111101 Short BSR
111110 Long BSR
111111 Padding
[TS 38.323, clause 5.6]
For the purpose of MAC buffer status reporting, the transmitting PDCP entity shall consider the following as PDCP
data volume:
- the PDCP SDUs for which no PDCP Data PDUs have been constructed;
- the PDCP Data PDUs that have not been submitted to lower layers;
- the PDCP Control PDUs;
- for AM DRBs, the PDCP SDUs to be retransmitted according to subclause 5.1.2;
- for AM DRBs, the PDCP Data PDUs to be retransmitted according to subclause 5.5.
[TS 38.322, clause 5.5]For the purpose of MAC buffer status reporting, the UE shall consider the following as RLC
data volume:
- RLC SDUs and RLC SDU segments that have not yet been included in an RLC data PDU;
- RLC data PDUs that are pending for initial transmission;
- RLC data PDUs that are pending for retransmission (RLC AM).
In addition, if a STATUS PDU has been triggered and t-StatusProhibit is not running or has expired, the UE shall
estimate the size of the STATUS PDU that will be transmitted in the next transmission opportunity, and consider this as
part of RLC data volume.
Same Pre-test conditions as in clause 7.1.1.0 with the exception of 3 AM DRBs on NR cell configured according to
Table 7.1.1.3.4.3.1-1.
ETSI

Parameter Value DRB1 Value DRB2 Value DRB3
LogicalChannelIdentity LCH4((DRB-Identity +3) LCH5(DRB-Identity +3) LCH6(DRB-Identity +3)
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)
ETSI

U-S Message
2 The SS transmits a MAC PDU containing two <-- MAC PDU (2 RLC SDUs on - -
RLC SDUs of size 12 bytes on LCH4 LCH4)
3 SS allocates an UL Grant of 40 bits. (Note 1) <-- (UL Grant, 40 bits) - -
4 Check: Does the UE transmit a Short BSR with --> MAC PDU (MAC Short BSR (LCG 2,5 P
‘LCG ID’ field set to ‘2’ and ‘Buffer size’ field ID=‘2’, Buffer Size=’4’ or bigger))
set to value ‘4’ or bigger? (Note 2)
5 Wait for retxBSR-Timer expiry on UE side. - - - -
6 Check: Does the UE transmit a scheduling --> (SR) 6 P
request?
7 The SS responds to the scheduling request in <-- (UL Grant, 40 bits) - -
step 6 by an UL Grant of 40 bits. (Note 1)
‘LCG ID’ field set to ‘2’ and ‘Buffer size’ field ID=‘2’, Buffer Size=’4’ or bigger))
9 The SS transmits a MAC PDU containing one <-- MAC PDU (1 RLC SDU on LCH5) - -
RLC SDU of size 12 bytes on LCH5
request?
11 The SS respond to the scheduling request in <-- (UL Grant, 40 bits) - -
step 10 by an UL Grant of 40 bits. (Note 1)
‘LCG ID’ field set to ‘2’ and ‘Buffer size#1’ field ID=‘2’, Buffer Size=’5’ or bigger))
13 The SS transmits a MAC PDU containing two <-- MAC PDU (2 RLC SDUs on - -
RLC SDUs of size 5 bytes on LCH6 LCH6)
request?
15 The SS responds to the scheduling request in <-- (UL Grant, 40 bits) - -
step 14 by one UL Grant of 40 bits. (Note 1)
16 Check: Does the UE transmit a Long BSR with --> MAC PDU (MAC Long BSR 1,5 P
‘Buffer size#1’ field set to value ‘1’, ‘Buffer (Buffer size#1=’1’ or bigger, Buffer
size#2’ field set to value ‘20’ or bigger? (Note size#2=’20’ or bigger)
3)
17 Wait for retxBSR-Timer expiry on the UE side. - - -
request?
19 SS allocates an UL Grant of 608 bits. (Note 4) <-- (UL Grant, 608 bits) - -
20 Check: Does the UE transmit a MAC PDU --> MAC PDU (17-Byte 2 MAC sub - -
including five RLC SDUs and BSR? (Note 5) PDUs from LCH4, 17-Byte 1 MAC
sub PDU from LCH5 and 10-Byte
2 MAC Sub PDUs from LCH6)
21 SS transmits an RLC STATUS PDU to <-- RLC STATUS PDU (ACK_SN=2) - -
acknowledge correctly received
data(LCID=’000100’)
24 The SS transmits a MAC PDU containing two <-- MAC PDU - -
MAC SDUs, the first containing a 8 byte RLC
SDU with LCID set to LCH4 and the second
containing a 7 byte RLC SDU with LCID set to
LCH6.
25 The UE sends Scheduling Request --> (SR) - -
26 The SS transmits an uplink grant of size 256 <-- (UL grant, 256 bits) - -
bits. (Note 6)
ETSI
27 Check: Does the UE return a MAC PDU of --> MAC PDU (13-Byte MAC Sub 8 P
length 256 bits including RLC SDUs, Padding PDU from LC 4 and 12-Byte MAC
and Short BSR or LongBSR with Buffer size(s) Sub PDU from LCH6 and 5-Byte
set to ‘0’? (Note 5) MAC Sub PDU containing Long
BSR and 2-Byte MAC Sub PDU
containing Padding)
Or
MAC PDU (13-Byte MAC Sub
PDU from LCH4 and 12-Byte
MAC Sub PDU from LCH6 and 2-
Byte MAC Sub PDU containing
short BSR and 5-Byte MAC Sub
PDU containing Padding)
data(LCID=LCH4)
data(LCID=LCH6)
Note 1: 40 bits enables UE to transmit a MAC PDU with a 1 byte MAC BSR header and a Short BSR (1 byte) or a
2 bytes MAC BSR header and a Long BSR (3 bytes with 2 LCG configured).
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 46 bytes of RLC SDU data (received in steps 2, 9 and 13) in the transmission buffer.608 bits
enables UE to transmit user data in MAC PDU 2 RLC SDUs of 12 bytes on LCH4, each 3 Bytes RLC
Header and 2 Bytes MAC Header resulting in 2 MAC Sub PDUs of 17 Bytes Each. Similarly one 17 Bytes
MAC Sub PDU for 12 Bytes RLC SDU on LCH5. Two 5 Bytes RLC SDUs on LCH6 with 3 Bytes RLC
header each and 2 Bytes MAC header each, will result in 2 MAC sub PDUs of 10 bytes each. Total comes
to 17+17+17+10+10 +3 B LongBSR(2 Bytes LongBSR header + 1 Byte LongBSR) + 2 B padding =76
Bytes.
Note 5: The MAC SDUs for the different logical channels may be in any order in the MAC PDU.
Note 6: UL grant of 256 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to enable UE to transmit two MAC
SDUs of size 11 and 10 bytes in a MAC PDU (8 bytes RLC SDU + 3 bytes AMD PDU header +2 Bytes
MAC sub Header + 7 bytes RLC SDU+ 3 bytes AMD PDU header+2 Bytes MAC sub Header + 2 Bytes
Long BSR MAC Sub Header + 3 Bytes Long BSR + 2 Bytes MAC Padding Sub PDU) or (8 bytes RLC SDU
+ 3 bytes AMD PDU header +2 Bytes MAC sub Header + 7 bytes RLC SDU+ 3 bytes AMD PDU header+2
Bytes MAC sub Header + 1 Byte Short BSR MAC Sub Header + 1 Byte Short BSR + 7 Bytes MAC
Padding Sub PDU) = 32 Bytes
Table 7.1.1.3.4.3.3: MAC-CellGroupConfig (preamble)
Derivation Path: TS 38.508-1 [4], clause Table 4.6.3-68

periodicBSR-Timer infinity
retxBSR-Timer sf320
}
phr-Config CHOICE {
release NULL
}
}
ETSI
7.1.1.3.5 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 the size of a Short 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 short 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 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 long 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 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 only one LCG in the TTI where the BSR is transmitted }
then { UE reports a Short BSR }
}
(4)
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 }
}
[TS 38.321, clause 5.4.5]
- retxBSR-Timer;
eight.
ETSI
1> else:
1> else:
For Padding BSR:
for transmission.
3> else:
of LCGID.
2> else:
ETSI
[TS 38.321, clause 6.1.3.1]
ETSI
Buffer Size 1 Oct 2
Buffer Size 2 Oct 3
...

0 0 8 ≤ 102 16 ≤ 1446 24 ≤ 20516
1 ≤ 10 9 ≤ 142 17 ≤ 2014 25 ≤ 28581
2 ≤ 14 10 ≤ 198 18 ≤ 2806 26 ≤ 39818
3 ≤ 20 11 ≤ 276 19 ≤ 3909 27 ≤ 55474
4 ≤ 28 12 ≤ 384 20 ≤ 5446 28 ≤ 77284
5 ≤ 38 13 ≤ 535 21 ≤ 7587 29 ≤ 107669
6 ≤ 53 14 ≤ 745 22 ≤ 10570 30 ≤ 150000
7 ≤ 74 15 ≤ 1038 23 ≤ 14726 31 > 150000
ETSI

0 0 64 ≤ 560 128 ≤ 31342 192 ≤ 1754595
1 ≤ 10 65 ≤ 597 129 ≤ 33376 193 ≤ 1868488
2 ≤ 11 66 ≤ 635 130 ≤ 35543 194 ≤ 1989774
3 ≤ 12 67 ≤ 677 131 ≤ 37850 195 ≤ 2118933
4 ≤ 13 68 ≤ 720 132 ≤ 40307 196 ≤ 2256475
5 ≤ 14 69 ≤ 767 133 ≤ 42923 197 ≤ 2402946
6 ≤ 15 70 ≤ 817 134 ≤ 45709 198 ≤ 2558924
7 ≤ 16 71 ≤ 870 135 ≤ 48676 199 ≤ 2725027
8 ≤ 17 72 ≤ 926 136 ≤ 51836 200 ≤ 2901912
9 ≤ 18 73 ≤ 987 137 ≤ 55200 201 ≤ 3090279
10 ≤ 19 74 ≤ 1051 138 ≤ 58784 202 ≤ 3290873
11 ≤ 20 75 ≤ 1119 139 ≤ 62599 203 ≤ 3504487
12 ≤ 22 76 ≤ 1191 140 ≤ 66663 204 ≤ 3731968
13 ≤ 23 77 ≤ 1269 141 ≤ 70990 205 ≤ 3974215
14 ≤ 25 78 ≤ 1351 142 ≤ 75598 206 ≤ 4232186
15 ≤ 26 79 ≤ 1439 143 ≤ 80505 207 ≤ 4506902
16 ≤ 28 80 ≤ 1532 144 ≤ 85730 208 ≤ 4799451
17 ≤ 30 81 ≤ 1631 145 ≤ 91295 209 ≤ 5110989
18 ≤ 32 82 ≤ 1737 146 ≤ 97221 210 ≤ 5442750
19 ≤ 34 83 ≤ 1850 147 ≤ 103532 211 ≤ 5796046
20 ≤ 36 84 ≤ 1970 148 ≤ 110252 212 ≤ 6172275
21 ≤ 38 85 ≤ 2098 149 ≤ 117409 213 ≤ 6572925
22 ≤ 40 86 ≤ 2234 150 ≤ 125030 214 ≤ 6999582
23 ≤ 43 87 ≤ 2379 151 ≤ 133146 215 ≤ 7453933
24 ≤ 46 88 ≤ 2533 152 ≤ 141789 216 ≤ 7937777
25 ≤ 49 89 ≤ 2698 153 ≤ 150992 217 ≤ 8453028
26 ≤ 52 90 ≤ 2873 154 ≤ 160793 218 ≤ 9001725
27 ≤ 55 91 ≤ 3059 155 ≤ 171231 219 ≤ 9586039
28 ≤ 59 92 ≤ 3258 156 ≤ 182345 220 ≤ 10208280
29 ≤ 62 93 ≤ 3469 157 ≤ 194182 221 ≤ 10870913
30 ≤ 66 94 ≤ 3694 158 ≤ 206786 222 ≤ 11576557
31 ≤ 71 95 ≤ 3934 159 ≤ 220209 223 ≤ 12328006
32 ≤ 75 96 ≤ 4189 160 ≤ 234503 224 ≤ 13128233
33 ≤ 80 97 ≤ 4461 161 ≤ 249725 225 ≤ 13980403
34 ≤ 85 98 ≤ 4751 162 ≤ 265935 226 ≤ 14887889
35 ≤ 91 99 ≤ 5059 163 ≤ 283197 227 ≤ 15854280
36 ≤ 97 100 ≤ 5387 164 ≤ 301579 228 ≤ 16883401
37 ≤ 103 101 ≤ 5737 165 ≤ 321155 229 ≤ 17979324
38 ≤ 110 102 ≤ 6109 166 ≤ 342002 230 ≤ 19146385
39 ≤ 117 103 ≤ 6506 167 ≤ 364202 231 ≤ 20389201
40 ≤ 124 104 ≤ 6928 168 ≤ 387842 232 ≤ 21712690
41 ≤ 132 105 ≤ 7378 169 ≤ 413018 233 ≤ 23122088
42 ≤ 141 106 ≤ 7857 170 ≤ 439827 234 ≤ 24622972
43 ≤ 150 107 ≤ 8367 171 ≤ 468377 235 ≤ 26221280
44 ≤ 160 108 ≤ 8910 172 ≤ 498780 236 ≤ 27923336
45 ≤ 170 109 ≤ 9488 173 ≤ 531156 237 ≤ 29735875
46 ≤ 181 110 ≤ 10104 174 ≤ 565634 238 ≤ 31666069
47 ≤ 193 111 ≤ 10760 175 ≤ 602350 239 ≤ 33721553
48 ≤ 205 112 ≤ 11458 176 ≤ 641449 240 ≤ 35910462
49 ≤ 218 113 ≤ 12202 177 ≤ 683087 241 ≤ 38241455
50 ≤ 233 114 ≤ 12994 178 ≤ 727427 242 ≤ 40723756
51 ≤ 248 115 ≤ 13838 179 ≤ 774645 243 ≤ 43367187
52 ≤ 264 116 ≤ 14736 180 ≤ 824928 244 ≤ 46182206
53 ≤ 281 117 ≤ 15692 181 ≤ 878475 245 ≤ 49179951
54 ≤ 299 118 ≤ 16711 182 ≤ 935498 246 ≤ 52372284
55 ≤ 318 119 ≤ 17795 183 ≤ 996222 247 ≤ 55771835
56 ≤ 339 120 ≤ 18951 184 ≤ 1060888 248 ≤ 59392055
57 ≤ 361 121 ≤ 20181 185 ≤ 1129752 249 ≤ 63247269
58 ≤ 384 122 ≤ 21491 186 ≤ 1203085 250 ≤ 67352729
59 ≤ 409 123 ≤ 22885 187 ≤ 1281179 251 ≤ 71724679
60 ≤ 436 124 ≤ 24371 188 ≤ 1364342 252 ≤ 76380419
61 ≤ 464 125 ≤ 25953 189 ≤ 1452903 253 ≤ 81338368
ETSI
62 ≤ 494 126 ≤ 27638 190 ≤ 1547213 254 > 81338368

63 ≤ 526 127 ≤ 29431 191 ≤ 1647644 255 Reserved
[TS 38.321, clause 6.2.1]
Table 6.2.1-2: Values of LCID for UL-SCH
Index LCID values

000000 CCCH
100001–110110 Reserved
111010 C-RNTI
111101 Short BSR
111110 Long BSR
111111 Padding
Same Pre-test conditions as in clause 7.1.1.0 with the exception of 2 AM DRBs on NR cell configured according to
Table 7.1.1.3.5.3.1-1.

Parameter DRB1 DRB2
Priority 7 6
ETSI

U-S Message
- EXCEPTION: Step 2 shall be repeated for 3 - - - -
times
2 The SS transmits a MAC PDU including an <-- MAC PDU (RLC SDU on LCH5) - -
RLC PDU of size 13 bytes on LCH5.
3 The SS transmits a MAC PDU including an <-- MAC PDU (RLC SDU on LCH4) - -
RLC PDU of size 12 bytes on LCH4.
4 UE transmits a Scheduling Request on --> (SR) - -
PUCCH.
5 The SS sends an uplink grant of size 40 bits. <-- (UL grant) - -
(Note 1)
6 The UE transmit a Long BSR report. --> MAC PDU (Long BSR header - -
(LCID=’ 111110’), Long BSR)
(Note 2)
8 Check: Does UE transmit a MAC PDU --> MAC PDU (MAC sub PDU header 1 P
containing an RLC SDU and a short truncated for RLC PDU, RLC PDU, short
BSR indicating pending data (‘Buffer size’ field truncated BSR header (LCID=’
> ‘0’) for logicalChannelGroup 1 (‘LCG ID’ field 111011’), short
set to ‘01’)? truncatedBSR(LCG ID =’01’,
Buffer size>’0’))
(Note 3)
containing an RLC SDU and a long truncated for RLC PDU, RLC PDU, long
BSR indicating pending data available for truncated BSR header (LCID=’
LCG1 and LCG2 and ‘Buffer size’ field > ‘0’ for 111100’), long truncatedBSR(
logicalChannelGroup 1? LCG1=1, LCG2=1, Buffer
size1>’0’))
(Note 4)
containing an RLC SDU and with a Short BSR for RLC PDU, RLC PDU, Short
indicating pending data (‘Buffer size’ field > ‘0’) BSR header(LCID=’11101’), Short
for logicalChannelGroup 2 (‘LCG ID’ field BSR(LCG ID =’10’,Buffer
=’10’)? size>’0’))
A acknowledge correctly received data
(LCID=LCH5)
(Note 5)
containing a RLC SDU and a Long BSR? for RLC PDU, RLC PDU, Long
BSR header (LCID=’11110’), Long
BSR))
acknowledge correctly received data
(LCID=LCH4)
Note 1: 40 bits (LRBs & IMCS as per 38.523-3[3] annex B) enables UE to transmit a MAC PDU with a MAC BSR
header (1 byte) and a Short BSR (1 byte) or a MAC BSR header (2 bytes) a Long BSR (3 bytes when 2
LCG configured).
Note 2: UE triggers a truncated Short BSR of type "Padding BSR" to report buffer status for one LCG for that TTI.
(2 Bytes MAC Data sub PDU header + 13 Bytes MAC SDU + 1 Byte Short truncated BSR sub header + 1
Byte Short truncated BSR = 17 bytes)
Note 3: UE triggers a truncated Long BSR of type "Padding BSR" to report buffer status for one LCG for that TTI.
(2 Bytes MAC Data sub PDU header + 13 Bytes MAC SDU + 2 Bytes Long truncated BSR sub header + 2
Bytes Long truncated BSR = 19 bytes)
Note 4: UE triggers a Short BSR of type "Padding BSR" to report buffer status for one LCG for that TTI. (2 Bytes
MAC Data sub PDU header + 13 Bytes MAC SDU + 1 Byte Short BSR sub header + 1 Byte short BSR =
17 bytes)
ETSI
Note 5: UE triggers a long BSR of type "Padding BSR" to report buffer status for one LCG for that TTI. (2 Bytes
MAC Data sub PDU header + 12 Bytes MAC SDU + 2 Bytes long BSR sub header + 1 Byte long BSR + 1
byte Padding sub header + 2 bytes Padding = 20 bytes)
None
7.1.1.3.6 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 }
then { UE triggers a Periodic BSR and reports Long BSR and restarts the periodicBSR-Timer }
}
(2)
ensure that {
when { periodicBSR-Timer expires and one LCG has buffered data }
then { UE triggers a Periodic BSR and reports Short BSR and restarts the periodicBSR-Timer }
}
[TS 38.321, clause 5.4.5]
- retxBSR-Timer;
eight.
ETSI
1> else:
1> else:
For Padding BSR:
for transmission.
3> else:
of LCGID.
2> else:
ETSI
[TS 38.321, clause 6.1.3.1]
ETSI
Buffer Size 1 Oct 2
Buffer Size 2 Oct 3
...

0 0 8 ≤ 102 16 ≤ 1446 24 ≤ 20516
1 ≤ 10 9 ≤ 142 17 ≤ 2014 25 ≤ 28581
2 ≤ 14 10 ≤ 198 18 ≤ 2806 26 ≤ 39818
3 ≤ 20 11 ≤ 276 19 ≤ 3909 27 ≤ 55474
4 ≤ 28 12 ≤ 384 20 ≤ 5446 28 ≤ 77284
5 ≤ 38 13 ≤ 535 21 ≤ 7587 29 ≤ 107669
6 ≤ 53 14 ≤ 745 22 ≤ 10570 30 ≤ 150000
7 ≤ 74 15 ≤ 1038 23 ≤ 14726 31 > 150000
ETSI
0 0 64 ≤ 526 128 ≤ 29431 192 ≤ 1647644
1 ≤ 10 65 ≤ 560 129 ≤ 31342 193 ≤ 1754595
2 ≤ 11 66 ≤ 597 130 ≤ 33376 194 ≤ 1868488
3 ≤ 12 67 ≤ 635 131 ≤ 35543 195 ≤ 1989774
4 ≤ 13 68 ≤ 677 132 ≤ 37850 196 ≤ 2118933
5 ≤ 13 69 ≤ 720 133 ≤ 40307 197 ≤ 2256475
6 ≤ 14 70 ≤ 767 134 ≤ 42923 198 ≤ 2402946
7 ≤ 15 71 ≤ 817 135 ≤ 45709 199 ≤ 2558924
8 ≤ 16 72 ≤ 870 136 ≤ 48676 200 ≤ 2725027
9 ≤ 17 73 ≤ 926 137 ≤ 51836 201 ≤ 2901912
10 ≤ 18 74 ≤ 987 138 ≤ 55200 202 ≤ 3090279
11 ≤ 19 75 ≤ 1051 139 ≤ 58784 203 ≤ 3290873
12 ≤ 20 76 ≤ 1119 140 ≤ 62599 204 ≤ 3504487
13 ≤ 22 77 ≤ 1191 141 ≤ 66663 205 ≤ 3731968
14 ≤ 23 78 ≤ 1269 142 ≤ 70990 206 ≤ 3974215
15 ≤ 25 79 ≤ 1351 143 ≤ 75598 207 ≤ 4232186
16 ≤ 26 80 ≤ 1439 144 ≤ 80505 208 ≤ 4506902
17 ≤ 28 81 ≤ 1532 145 ≤ 85730 209 ≤ 4799451
18 ≤ 30 82 ≤ 1631 146 ≤ 91295 210 ≤ 5110989
19 ≤ 32 83 ≤ 1737 147 ≤ 97221 211 ≤ 5442750
20 ≤ 34 84 ≤ 1850 148 ≤ 103532 212 ≤ 5796046
21 ≤ 36 85 ≤ 1970 149 ≤ 110252 213 ≤ 6172275
22 ≤ 38 86 ≤ 2098 150 ≤ 117409 214 ≤ 6572925
23 ≤ 40 87 ≤ 2234 151 ≤ 125030 215 ≤ 6999582
24 ≤ 43 88 ≤ 2379 152 ≤ 133146 216 ≤ 7453933
25 ≤ 46 89 ≤ 2533 153 ≤ 141789 217 ≤ 7937777
26 ≤ 49 90 ≤ 2698 154 ≤ 150992 218 ≤ 8453028
27 ≤ 52 91 ≤ 2873 155 ≤ 160793 219 ≤ 9001725
28 ≤ 55 92 ≤ 3059 156 ≤ 171231 220 ≤ 9586039
29 ≤ 59 93 ≤ 3258 157 ≤ 182345 221 ≤ 10208280
30 ≤ 62 94 ≤ 3469 158 ≤ 194182 222 ≤ 10870913
31 ≤ 66 95 ≤ 3694 159 ≤ 206786 223 ≤ 11576557
32 ≤ 71 96 ≤ 3934 160 ≤ 220209 224 ≤ 12328006
33 ≤ 75 97 ≤ 4189 161 ≤ 234503 225 ≤ 13128233
34 ≤ 80 98 ≤ 4461 162 ≤ 249725 226 ≤ 13980403
35 ≤ 85 99 ≤ 4751 163 ≤ 265935 227 ≤ 14887889
36 ≤ 91 100 ≤ 5059 164 ≤ 283197 228 ≤ 15854280
37 ≤ 97 101 ≤ 5387 165 ≤ 301579 229 ≤ 16883401
38 ≤ 103 102 ≤ 5737 166 ≤ 321155 230 ≤ 17979324
39 ≤ 110 103 ≤ 6109 167 ≤ 342002 231 ≤ 19146385
40 ≤ 117 104 ≤ 6506 168 ≤ 364202 232 ≤ 20389201
41 ≤ 124 105 ≤ 6928 169 ≤ 387842 233 ≤ 21712690
42 ≤ 132 106 ≤ 7378 170 ≤ 413018 234 ≤ 23122088
43 ≤ 141 107 ≤ 7857 171 ≤ 439827 235 ≤ 24622972
44 ≤ 150 108 ≤ 8367 172 ≤ 468377 236 ≤ 26221280
45 ≤ 160 109 ≤ 8910 173 ≤ 498780 237 ≤ 27923336
46 ≤ 170 110 ≤ 9488 174 ≤ 531156 238 ≤ 29735875
47 ≤ 181 111 ≤ 10104 175 ≤ 565634 239 ≤ 31666069
48 ≤ 193 112 ≤ 10760 176 ≤ 602350 240 ≤ 33721553
49 ≤ 205 113 ≤ 11458 177 ≤ 641449 241 ≤ 35910462
50 ≤ 218 114 ≤ 12202 178 ≤ 683087 242 ≤ 38241455
51 ≤ 233 115 ≤ 12994 179 ≤ 727427 243 ≤ 40723756
52 ≤ 248 116 ≤ 13838 180 ≤ 774645 244 ≤ 43367187
53 ≤ 264 117 ≤ 14736 181 ≤ 824928 245 ≤ 46182206
54 ≤ 281 118 ≤ 15692 182 ≤ 878475 246 ≤ 49179951
55 ≤ 299 119 ≤ 16711 183 ≤ 935498 247 ≤ 52372284
56 ≤ 318 120 ≤ 17795 184 ≤ 996222 248 ≤ 55771835
57 ≤ 339 121 ≤ 18951 185 ≤ 1060888 249 ≤ 59392055
58 ≤ 361 122 ≤ 20181 186 ≤ 1129752 250 ≤ 63247269
59 ≤ 384 123 ≤ 21491 187 ≤ 1203085 251 ≤ 67352729
60 ≤ 409 124 ≤ 22885 188 ≤ 1281179 252 ≤ 71724679
61 ≤ 436 125 ≤ 24371 189 ≤ 1364342 253 ≤ 76380419
ETSI
62 ≤ 464 126 ≤ 25953 190 ≤ 1452903 254 ≤ 81338368

63 ≤ 494 127 ≤ 27638 191 ≤ 1547213 255 > 81338368
[TS 38.321, clause 6.2.1]
Table 6.2.1-2: Values of LCID for UL-SCH
Index LCID values

000000 CCCH
100001–110110 Reserved
111010 C-RNTI
111101 Short BSR
111110 Long BSR
111111 Padding
Same Pre-test conditions as in clause 7.1.1.0 with the exception of 2 SN terminated SCG bearers configured according
to Table 7.1.1.3.6.3.1-1.

Parameter DRB1 DRB2
Priority 7 6
ETSI

U-S Message
2 The SS transmits a MAC PDU containing an <-- MAC PDU (RLC PDU)
RLC PDU on LCH4 (LCG ID 2), which contains
1 RLC SDU of size 14 bytes.
(Note 1)
4 The UE transmits a short BSR report and --> MAC PDU ((LCID=’ 111101’, LCG - -
restarts periodicBSR-Timer ID='10', Buffer size index > 0)
- EXCEPTION: Steps 5 to 7 shall be repeated - - - -
two times (Note 2)
5 Wait for periodicBSR-Timer expiry. - - - -
6 The SS sends an uplink grant of size 32 bits - - - -
7 Check: Does UE transmit a MAC PDU --> MAC PDU (LCID=’111101’, LCG 2 P
containing a Short BSR with ‘LCG ID’ field set ID=’10’, Buffer Size index > 0)
to ‘10’ (logicalChannelGroup 2) and Buffer
Size Index > 0?
8 The SS transmits a MAC PDU containing an <-- MAC PDU (RLC PDU) - -
RLC PDU on LCH5 (LCG ID 1), which contains
1 RLC SDU of size 14 bytes.
9 The SS sends an uplink grant of size 40 bits <-- (UL grant) - -
(Note 3)
10 The UE transmits a long BSR report with --> MAC PDU (( ‘Buffer size#1 index’ - -
‘Buffer size#1’ (LCG ID=1) and ‘Buffer size#2’ > 0, ‘Buffer size#2 index=’ >0’)
(LCG ID=2) fields set to value > ‘0’
- EXCEPTION: Step 11 to 13 shall be repeated - - - -
twice. (Note 4)
11 Wait for periodicBSR-Timer expiry. - - - -
12 The SS sends an uplink grant of size 40 bits - - - -
13 Check: Does UE transmit a MAC PDU --> MAC PDU 1 P
containing a Long BSR with ‘Buffer size#1’
(LCG ID=1) and ‘Buffer size#2’ (LCG ID=2)
fields set to value > ‘0’?
14 The SS transmits 1 UL grant of size 320 bits to - -
enable the UE to loopback RLC SDU on LCH4
and LCH5.
15 The UE transmits MAC PDU containing the --> MAC PDU - -
remaining RLC SDUs as sent by the SS in
steps 2 and 8.
Note 1: SS transmits an UL grant of 32 bits(LRBs & IMCS as per 38.523-3[3] annex B) to allow UE to transmit a
Regular BSR triggered by the new data received logicalChannelGroup 1 in step 2.
Note 2: One short BSR due to first expiry of periodicBSR-Timer and one short BSR due to second expire of
periodicBSR-Timer.
Note 3: SS transmits an UL grant of 40 bits(LRBs & IMCS as per 38.523-3[3] annex B) to allow UE to transmit a
Regular BSR triggered by the new data received on higher priority logicalChannelGroup 1 in step 8.
Note 4: One long BSR due to expire of periodicBSR-Timer and one long BSR due to second expiry of
periodicBSR-Timer.
ETSI
Table 7.1.1.3.6.3.3: MAC-CellGroupConfig (preamble)
Derivation Path: TS 38.308 [6], clause Table 4.6.3-49

periodicBSR-Timer sf160
retxBSR-Timer sf10240
}
phr-Config CHOICE {
release NULL
}
}
7.1.1.3.7 UE power headroom reporting / Periodic reporting / DL pathloss change reporting
(1)
ensure that {
when { phr-PeriodicTimer is configured in UE }
then { UE transmits a MAC PDU containing Power Headroom MAC Control Element }
}
(2)
with { UE in RRC_CONNECTED state with periodic power headroom reporting configured }
ensure that {
when { phr-PeriodicTimer expires and UL resources allocated for new transmission }
}
(3)
with { UE in RRC_CONNECTED state with periodic power headroom reporting configured }
ensure that {
when { power headroom reporting is disabled }
then { UE stops transmitting Power Headroom MAC Control Element }
}
(4)
with { UE in RRC_Connected state with Power headroom reporting for phr-Tx-PowerFactorChange
configured }
ensure that {
when { the DL Pathloss has changed more than phr-Tx-PowerFactorChange dB and phr-ProhibitTimer is
running }
then { UE does not transmit a MAC PDU containing Power Headroom MAC Control Element }
}
(5)
with { UE in RRC_Connected state with Power headroom reporting for phr-Tx-PowerFactorChange
configured }
ensure that {
when { phr-ProhibitTimer expires and power headroom report is triggered due to DL Pathloss change
}
}
ETSI
References: The conformance requirements covered in the current TC are specified in: TS 38.321 clause 5.4.6 and
[TS 38.321, clause 5.4.6]
The Power Headroom reporting procedure is used to provide the serving gNB with the following information:
- Type 1 power headroom: the difference between the nominal UE maximum transmit power and the estimated power
for UL-SCH transmission per activated Serving Cell;
- Type 2 power headroom: the difference between the nominal UE maximum transmit power and the estimated
power for UL-SCH and PUCCH transmission on SpCell of the other MAC entity (i.e. E-UTRA MAC entity in
EN-DC case only);
power for SRS transmission per activated Serving Cell.
RRC controls Power Headroom reporting by configuring the following parameters:
- phr-PeriodicTimer;
- phr-ProhibitTimer;
- phr-Tx-PowerFactorChange;
- phr-Type2PCell;
- phr-Type2OtherCell;
- phr-ModeOtherCG;
- multiplePHR.
A Power Headroom Report (PHR) shall be triggered if any of the following events occur:
- phr-ProhibitTimer expires or has expired and the path loss has changed more than phr-Tx-PowerFactorChange
dB for at least one activated Serving Cell of any MAC entity which is used as a pathloss reference since the last
transmission of a PHR in this MAC entity when the MAC entity has UL resources for new transmission;
NOTE 1: The path loss variation for one cell assessed above is between the pathloss measured at present time on
the current pathloss reference and the pathloss measured at the transmission time of the last transmission
of PHR on the pathloss reference in use at that time, irrespective of whether the pathloss reference has
changed in between.
- phr-PeriodicTimer expires;
- upon configuration or reconfiguration of the power headroom reporting functionality by upper layers, which is
not used to disable the function;
- activation of an SCell of any MAC entity with configured uplink;
- addition of the PSCell (i.e. PSCell is newly added or changed);
- phr-ProhibitTimer expires or has expired, when the MAC entity has UL resources for new transmission, and the
following is true for any of the activated Serving Cells of any MAC entity with configured uplink:
- there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the
required power backoff due to power management (as allowed by P-MPRc as specified in TS 38.101-1 [14],
TS 38.101-2 [15], and TS 38.101-3 [16]) for this cell has changed more than phr-Tx-PowerFactorChange dB
since the last transmission of a PHR when the MAC entity had UL resources allocated for transmission or
PUCCH transmission on this cell.
ETSI
NOTE 2: The MAC entity should avoid triggering a PHR when the required power backoff due to power
management decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid
reflecting such temporary decrease in the values of PCMAX,f,c/PH when a PHR is triggered by other
triggering conditions.
If the MAC entity has UL resources allocated for a new transmission the MAC entity shall:
1> if it is the first UL resource allocated for a new transmission since the last MAC reset:
2> start phr-PeriodicTimer;
1> if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not
cancelled; and
1> if the allocated UL resources can accommodate the MAC CE for PHR which the MAC entity is configured to
transmit, plus its subheader, as a result of LCP as defined in subclause 5.4.3.1:
2> if multiplePHR is configured:
3> for each activated Serving Cell with configured uplink associated with any MAC entity:
4> obtain the value of the Type 1 or Type 3 power headroom for the corresponding uplink carrier as
specified in subclause 7.7 of TS 38.213 [6];
4> if this MAC entity has UL resources allocated for transmission on this Serving Cell; or
4> if the other MAC entity, if configured, has UL resources allocated for transmission on this Serving
Cell and phr-ModeOtherCG is set to real by upper layers:
5> obtain the value for the corresponding PCMAX,f,c field from the physical layer.
3> if phr-Type2OtherCell is configured:
4> if the other MAC entity is E-UTRA MAC entity:
5> obtain the value of the Type 2 power headroom for the SpCell of the other MAC entity (i.e. E-
UTRA MAC entity);
5> if phr-ModeOtherCG is set to real by upper layers:
6> obtain the value for the corresponding PCMAX,f,c field for the SpCell of the other MAC entity (i.e. E-
UTRA MAC entity) from the physical layer.
3> instruct the Multiplexing and Assembly procedure to generate and transmit the Multiple Entry PHR MAC
CE as defined in subclause 6.1.3.9 based on the values reported by the physical layer.
2> else (i.e. Single Entry PHR format is used):
3> obtain the value of the Type 1 power headroom from the physical layer for the corresponding uplink
carrier of the PCell;
3> obtain the value for the corresponding PCMAX,f,c field from the physical layer;
3> instruct the Multiplexing and Assembly procedure to generate and transmit the Single Entry PHR MAC
CE as defined in subclause 6.1.3.8 based on the values reported by the physical layer.
2> start or restart phr-PeriodicTimer;
2> start or restart phr-ProhibitTimer;
2> cancel all triggered PHR(s).
[TS 38.321, clause 6.1.3.8]
The Single Entry PHR MAC CE is identified by a MAC PDU subheader with LCID as specified in Table 6.2.1-2.
It has a fixed size and consists of two octet defined as follows (figure 6.1.3.8-1):
ETSI
- 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.8-1 below (the
corresponding measured values in dB are specified in TS 38.133 [11]);
- PCMAX,f,c: This field indicates the PCMAX,f,c (as specified in TS 38.213 [6]) used for calculation of the preceding
PH field. The reported PCMAX,f,c and the corresponding nominal UE transmit power levels are shown in Table
6.1.3.8-2 (the corresponding measured values in dBm are specified in TS 38.133 [11]).
R R PH (Type X, PCell)
R R PCMAX,c
Figure 6.1.3.8-1: Single Entry PHR MAC CE
Table 6.1.3.8-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
Table 6.1.3.8-2: Nominal UE transmit power level for PHR
PCMAXf,,c Nominal UE transmit power level

0 PCMAX_C_00
1 PCMAX_C_01
2 PCMAX_C_02
… …
61 PCMAX_C_61
62 PCMAX_C_62
63 PCMAX_C_63
ETSI

U-S Message
1 The SS transmits UL grant to the UE at every <-- - - -
10ms in PDCCH occasion.
2 SS transmits NR <-- (RRCReconfiguration) - -
RRCReconfigurationmessage to configure
specific Power Headroom parameters for NR
Cell(Note 1).
3 Check: does the UE transmit a MAC PDU --> MAC PDU 1 P
containing Power Headroom MAC Control
Element?
(Note 2, 5)
4 The UE transmits an NR --> (RRCReconfigurationComplete) - -
RRCReconfigurationComplete message to
confirm the setup of Power Headroom
parameters.
(Note 2,3)
Element 500ms after step 3? (Note 5)
6 The SS transmits an NR RRCReconfiguration <-- (RRCReconfiguration) - -
message to disable Power Headroom
reporting.(Note 1)
confirm the disabling of Power Headroom
parameters.(Note 3)
8 Check: for 2 seconds, does the UE transmit a --> MAC PDU 3 F
MAC PDU containing Power Headroom MAC
Control Element? (Note 5)
9 SS transmits NR <-- (RRCReconfiguration) - -
specific Power Headroom parameters for NR
Cell.(Note 1)
Element?
(Note 4, 5)
parameters.
(Note 3,4)
12 Wait for T1= 20% of prohibitPHR-Timer. - - - -
13 Reduce SS power level for NR Cell so as to - - - -
cause a DL_Pathloss change at UE by 5dB.
14 Check: for 80% of prohibitPHR-Timer since --> MAC PDU 4 F
step 10, does the UE transmit a MAC PDU
Element? (Note 5)
15 Check: after prohibitPHR-Timer after step 10, --> MAC PDU 5 P
does the UE transmit a MAC PDU containing
Power Headroom MAC Control Element?
(Note 5)
16 Increase SS power level for NR Cell so as to - - - -
cause a DL_Pathloss change at UE by 5dB.
17 Check: for 80% of prohibitPHR-Timer since --> MAC PDU 4 F
Element? (Note 5)
ETSI
18 Check: after prohibitPHR-Timer after step 15, --> MAC PDU 5 P

(Note 5)
reporting.(Note 1)
parameters.(Note 3)
Note 1: for EN-DC the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration 36.508
Note 2: Steps 3 and 4 can happen in any order.
Note 5: For NR5GC the received MAC PDU will contain Single-entry PHR MAC CE. For MR-DC the received MAC
PDU will contain Multiple-Entry PHR MAC CE.
Table 7.1.1.3.7.3.3-1: RRCReconfiguration (step 2 Table 7.1.1.3.7.3.2-1)

(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}

mac-CellGroupConfig SEQUENCE {
phr-Config CHOICE {
setup SEQUENCE {
phr-PeriodicTimer sf500
phr-ProhibitTimer sf1000
phr-Tx-PowerFactorChange infinity
multiplePHR false
multiplePHR true MR-DC
phr-Type2PCell false
phr-Type2OtherCell false
phr-ModeOtherCG real
}
}
}
}
ETSI
Table 7.1.1.3.7.3.3-3: RRCReconfiguration (step 6,19 Table 7.1.1.3.7.3.2-1)

(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}

phr-Config CHOICE {
release NULL
}
}
}

(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

phr-Config CHOICE {
setup SEQUENCE {
phr-PeriodicTimer infinity
phr-Tx-PowerFactorChange 3dB
multiplePHR false
multiplePHR true MR-DC
phr-Type2PCell false
}
}
}
}
7.1.1.3.8 UE power headroom reporting / SCell activation / DL pathloss change reporting
7.1.1.3.8.1 UE power headroom reporting / SCell activation / DL pathloss change reporting/ Intra-
band Contiguous CA
7.1.1.3.8.1.1 Test Purpose (TP)
(1)
with { UE in RRC_Connected state with multiple Power headroom reporting and an SCell with uplink is
configured }
ensure that {
when { UE receives an Activation MAC Control Element activating the SCell }
then { UE transmits a MAC PDU containing Power Headroom Report MAC Control Element including PH
type1 for SpCell and Scell }
}
(2)
with { UE in RRC_Connected state with multiple Power headroom reporting for phr-dl-PathlossChange
configured }
ensure that {
when { the DL Pathloss changes and phr-ProhibitTimer is running }
then { UE does not transmit a MAC PDU containing Power Headroom Report MAC Control Element
including PH type1 for SpCell and Scell }
}
(3)
with { UE in RRC_Connected state with Power headroom reporting for phr-dl-PathlossChange configured
}
ensure that {
when { phr-ProhibitTimer expires and power headroom report is triggered due to DL Pathloss change
}
then { UE transmits a MAC PDU containing Power Headroom Report MAC Control Element including PH
type1 for SpCell and Scell }
}
7.1.1.3.8.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.321 clause 5.4.6 and
[TS 38.321, clause 5.4.6]
ETSI
The Power Headroom reporting procedure is used to provide the serving gNB with the following information:
power for UL-SCH transmission per activated Serving Cell;
power for UL-SCH and PUCCH transmission on SpCell of the other MAC entity (i.e. E-UTRA MAC entity in
EN-DC, NE-DC, and NGEN-DC cases);
power for SRS transmission per activated Serving Cell.
RRC controls Power Headroom reporting by configuring the following parameters:
- phr-PeriodicTimer;
- phr-ProhibitTimer;
- phr-Tx-PowerFactorChange;
- phr-Type2OtherCell;
- phr-ModeOtherCG;
- multiplePHR.
changed in between.
ETSI
cancelled; and
transmit, plus its subheader, as a result of LCP as defined in clause 5.4.3.1:
2> if multiplePHR with value true is configured:
specified in clause 7.7 of TS 38.213 [6] for NR Serving Cell and clause 5.1.1.2 of TS 36.213 [17] for
E-UTRA Serving Cell;
3> if phr-Type2OtherCell with value true is configured:
UTRA MAC entity);
6> obtain the value for the corresponding PCMAX,f,c field for the SpCell of the other MAC entity
(i.e. E-UTRA MAC entity) from the physical layer.
CE as defined in clause 6.1.3.9 based on the values reported by the physical layer.
[TS 38.321, clause 6.1.3.9]
The Multiple Entry PHR MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-2.
It has a variable size, and includes the bitmap, a Type 2 PH field and an octet containing the associated PCMAX,f,c field (if
reported) for SpCell of the other MAC entity, a Type 1 PH field and an octet containing the associated PCMAX,f,c field (if
reported) for the PCell. It further includes, in ascending order based on the ServCellIndex, one or multiple of Type X
PH fields and octets containing the associated PCMAX,f,c fields (if reported) for Serving Cells other than PCell indicated
in the bitmap. X is either 1 or 3 according to TS 38.213 [6] and TS 36.213 [17].
The presence of Type 2 PH field for SpCell of the other MAC entity is configured by phr-Type2OtherCell with value
true.
A single octet bitmap is used for indicating the presence of PH per Serving Cell when the highest ServCellIndex of
Serving Cell with configured uplink is less than 8, otherwise four octets are used.
ETSI
The MAC entity determines whether PH value for an activated Serving Cell is based on real transmission or a reference
format by considering the configured grant(s) and downlink control information which has been received until and
including the PDCCH occasion in which the first UL grant for a new transmission that can accommodate the MAC CE
for PHR as a result of LCP as defined in clause 5.4.3.1 is received since a PHR has been triggered if the PHR MAC CE
is reported on an uplink grant received on the PDCCH or until the first uplink symbol of PUSCH transmission minus
PUSCH preparation time as defined in clause 7.7 of TS 38.213 [6] if the PHR MAC CE is reported on a configured
grant.
For a band combination in which the UE does not support dynamic power sharing, the UE may omit the octets
containing Power Headroom field and PCMAX,f,c field for Serving Cells in the other MAC entity except for the PCell in
the other MAC entity and the reported values of Power Headroom and PCMAX,f,c for the PCell are up to UE
implementation.
The PHR MAC CEs are defined as follows:
- Ci: This field indicates the presence of a PH field for the Serving Cell with ServCellIndex i as specified in TS
38.331 [5]. The Ci field set to 1 indicates that a PH field for the Serving Cell with ServCellIndex i is reported.
The Ci field set to 0 indicates that a PH field for the Serving Cell with ServCellIndex i is not reported;
- R: Reserved bit, set to 0;
- V: This field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, the
V field set to 0 indicates real transmission on PUSCH and the V field set to 1 indicates that a PUSCH reference
format is used. For Type 2 PH, the V field set to 0 indicates real transmission on PUCCH and the V field set to 1
indicates that a PUCCH reference format is used. For Type 3 PH, the V field set to 0 indicates real transmission
on SRS and the V field set to 1 indicates that an SRS reference format is used. Furthermore, for Type 1, Type 2,
and Type 3 PH, the V field set to 0 indicates the presence of the octet containing the associated PCMAX,f,c field,
and the V field set to 1 indicates that the octet containing the associated PCMAX,f,c field is omitted;
- 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.8-1 (the corresponding
measured values in dB for the NR Serving Cell are specified in TS 38.133 [11] while the corresponding
measured values in dB for the E-UTRA Serving Cell are specified in TS 36.133 [12]);
- P: This field indicates whether the MAC entity applies power backoff due to power management (as allowed by
P-MPRc as specified in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]). The MAC entity shall set
the P field to 1 if the corresponding PCMAX,f,c field would have had a different value if no power backoff due to
power management had been applied;
- PCMAX,f,c: If present, this field indicates the PCMAX,f,c (as specified in TS 38.213 [6]) for the NR Serving Cell and
the PCMAX,c or P̃ CMAX,c (as specified in TS 36.213 [17]) for the E-UTRA Serving Cell used for calculation of the
preceding PH field. The reported PCMAX,f,c and the corresponding nominal UE transmit power levels are shown in
Table 6.1.3.8-2 (the corresponding measured values in dBm for the NR Serving Cell are specified in TS 38.133
[11] while the corresponding measured values in dBm for the E-UTRA Serving Cell are specified in TS 36.133
[12]).
ETSI
C7 C6 C5 C4 C3 C2 C1 R
PH (Type 2, SpCell of the other

P V
MAC entity)
R R PCMAX,f,c 1
P V PH (Type 1, PCell)
R R PCMAX,f,c 2
P V PH (Type X, Serving Cell 1)
R R PCMAX,f,c 3
.. .
P V PH (Type X, Serving Cell n)
R R PCMAX,f,c m
Figure 6.1.3.9-1: Multiple Entry PHR MAC CE with the highest ServCellIndex of Serving Cell with
configured uplink is less than 8
7.1.1.3.8.1.3 Test description
7.1.1.3.8.1.3.1 Pre-test conditions
Same Pre-test conditions as in clause 7.1.1.0 except that Test loop function(Off) System information combination NR-4
and in addition NR Cell 3 is configured as NR Active Scell.
7.1.1.3.8.1.3.2 Test procedure sequence
Table 7.1.1.3.8.1.3.2-0: Cell configuration power level changes over time for FR1
Parameter Unit NR Cell 1 NR Cell 3 Remarks
T0 Cell- dBm/SC -88 -88
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
ETSI
Table 7.1.1.3.8.1.3.2-0A: Cell configuration power level changes over time for FR2
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
ETSI
Table 7.1.1.3.8.1.3.2-1: Main behaviour

U-S Message
to configure SCell (NR Cell 3). Note 1
2
3 The SS is configured for Uplink Grant - - - -
Allocation Type 2. SS is configured to transmit
UL grant for UE at every 10 ms.
to provide Power Headroom parameters. Note
1
EXCEPTION: In parallel with step 5, UE - - - -
executes parallel behaviour defined in Table
7.1.1.3.8.1.3.2-2
parameters. Note 2
6 The SS transmits an Activation MAC control <-- MAC PDU (SCell - -
element to activate SCell. Activation/Deactivation MAC CE
of one octet (C1=1))
containing Multiple Entry PHR MAC CE
containing Type 1 PH of NR SpCell and Scell?
Note 3
8 Void - - - -
Table 7.1.1.3.8.3.1.2-0/0A.
10 Check: For 80% of prohibitPHR-Timer since --> MAC PDU 2 F
containing Multiple Entry PHR MAC CE?
11 Check: After prohibitPHR-Timer after step 7, --> MAC PDU 3 P
Multiple Entry PHR MAC CE containing Type 1
PH of NR SpCell and Scell? Note 3
Table 7.1.1.3.8.1.3.2-0/0A.
containing Multiple Entry PHR MAC CE ?
Multiple Entry PHR MAC CE containing Type
1PH of NR SpCell and Scell? Note 3
Table 7.1.1.3.8.1.3.2-0/0A.
containing Multiple Entry PHR MAC CE
containing?
Table 7.1.1.3.8.1.3.2-0/0A.
containing Multiple Entry PHR MAC CE?
ETSI

reporting.(Note 1)
parameters.(Note 3)
Note 3: For EN-DC the Type 1 PHR report for EUTRA Pcell is also included.
Table 7.1.1.3.8.1.3.2-2: Parallel behaviour

U-S Message
1 The UE transmits a MAC PDU containing --> MAC PDU - -
PH of NR SpCell.
7.1.1.3.8.1.3.3 Specific message contents
Table 7.1.1.3.8.1.3.3-1: RRCReconfiguration (step 1, Table 7.1.1.3.8.1.3.2-1)

c1 CHOICE {
(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}
}
Table 7.1.1.3.8.1.3.3-2: CellGroupConfig (Table 7.1.1.3.8.1.3.3-1)

sCellToAddModList SEQUENCE (SIZE 1 entry
(1..maxMeasId)) OF SCellConfig {
SCellConfig[1] SEQUENCE { entry 1
sCellIndex SCellIndex as per TS
38.508-1 [4] table 4.6.3-
154
sCellConfigCommon ServingCellConfigComm
on
sCellConfigDedicated ServingCellConfig
}
}
ETSI
Table 7.1.1.3.8.1.3.3-3: ServingCellConfigCommon (Table 7.1.1.3.8.1.3.3-2)

physCellId Physical Cell Identity of
NR Cell 3
}
Table 7.1.1.3.8.1.3.3-3A: Void
Table 7.1.1.3.8.1.3.3-4: RRCReconfiguration ( Step 4, Table 7.1.1.3.8.1.3.2-1)

(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}

CellGroupConfig::= SEQUENCE {
cellGroupId CellGroupId as per TS
38.508-1 [4] table 4.6.3-
20
phr-Config CHOICE {
setup SEQUENCE {
phr-Tx-PowerFactorChange 3db
multiplePHR true
dummy true
}
}
}
}
ETSI
Table 7.1.1.3.8.1.3.3-6: ServingCellConfig (Table 7.1.1.3.8.1.3.3-2)

}
}
Table 7.1.1.3.8.1.3.3-7: BWP-UplinkDedicated(Table 7.1.1.3.8.1.3.3-6)

pucch-Config Not present
}

NR Cell 3
uplinkConfigCommon UplinkConfigCommon
}
7.1.1.3.8.2 UE power headroom reporting / SCell activation / DL pathloss change reporting / Inter-
band CA
The scope and description of the present TC is the same as test case 7.1.1.3.8.1 with the following differences:
- CA configuration: Inter-band CA replaces Intra-band Contiguous CA
- Cells configuration: NR Cell 10 replaces NR Cell 3
7.1.1.3.8.3 UE power headroom reporting / SCell activation / DL pathloss change reporting / Intra-
band non-Contiguous CA
- CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
7.1.1.3.9 Correct Handling of UL HARQ process / PUSCH Aggregation
(1)
with { UE in RRC_CONNECTED state and PUSCH Aggregation > 1 }
ensure that {
then { UE transmits a new MAC PDU and repeats the MAC PDU pusch-AggregationFactor-1 times after
first transmission and selects the redundancy version correctly }
}
6.1.4, TS 38.321 clauses 5.4.1, 5.4.2.1 and 5.4.2.2. Unless otherwise stated these are Rel-15 requirements.
ETSI
[TS 38.214, clause 6.1.2.1]
When the UE is scheduled to transmit a transport block and no CSI report, or the UE is scheduled to transmit a transport
block and a CSI report on PUSCH by a DCI, the Time domain resource assignment field value m of the DCI provides a
row index m + 1 to an allocated table. The determination of the used resource allocation table is defined in sub-clause
6.1.2.1.1. The indexed row defines the slot offset K2, the start and length indicator SLIV, or directly the start symbol S
and the allocation length L, and the PUSCH mapping type to be applied in the PUSCH transmission.
When the UE is scheduled to transmit a PUSCH with no transport block and with a CSI report by a CSI request field on
a DCI, the Time-domain resource assignment field value m of the DCI provides a row index m + 1 to an allocated table.
The determination of the applied resource allocation table is defined in sub-clause 6.1.2.1.1. The indexed row defines
the start and length indicator SLIV, or directly the start symbol S and the allocation length L, and the PUSCH mapping
type to be applied in the PUSCH transmission and K2 is determined based on the corresponding list entries
Y j , j = 0,..., N Rep − 1 of the higher layer parameter reportSlotConfig in CSI-ReportConfig for the N Rep triggered CSI
Reporting Settings. The ith codepoint of K2 s determined as K 2 = max Y j where Y j (i ) is the ith codepoint of Y j .
j
 2 μ PUSCH 
- The slot where the UE shall transmit the PUSCH is determined by K2 as n ⋅  + K2 where n is the slot

 2 μ PDCCH 

with the scheduling DCI, K2 is based on the numerology of PUSCH, and μ PUSCH and μ PDCCH are the subcarrier
spacing configurations for PUSCH and PDCCH, respectively, and
symbol S allocated for the PUSCH are determined from the start and length indicator SLIV of the indexed row:
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and
- The PUSCH mapping type is set to Type A or Type B as defined in Subclause 6.4.1.1.3 of [4, TS 38.211] as
given by the indexed row.
The UE shall consider the S and L combinations defined in table 6.1.2.1-1 as valid PUSCH allocations
PUSCH Normal cyclic prefix Extended cyclic prefix

Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
Type B {0,…,13} {1,…,14} {1,…,14} {0,…,12} {1,…,12} {1,…,12}
When the UE is configured with aggregationFactorUL > 1, the same symbol allocation is applied across the
aggregationFactorUL consecutive slots and the PUSCH is limited to a single transmission layer. The UE shall repeat
the TB across the aggregationFactorUL consecutive slots applying the same symbol allocation in each slot. The
ETSI
Table 6.1.2.1-2: Redundancy version when aggregationFactorUL > 1

scheduling the PUSCH n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3
0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
If the UE procedure for determining slot configuration, as defined in subclause 11.1 of [6, TS 38.213], determines
symbols of a slot allocated for PUSCH as downlink symbols, the transmission on that slot is omitted for multi-slot
PUSCH transmission.
[TS 38.214, clause 6.1.4]
To determine the modulation order, target code rate, redundancy version and transport block size for the physical uplink
shared channel, the UE shall first
- read the 5-bit modulation and coding scheme field (I MCS ) in the DCI to determine the modulation order (Om )
and target code rate (R) based on the procedure defined in Subclause 6.1.4.1
- read redundancy version field (rv) in the DCI to determine the redundancy version, and
- [check the "CSI request" bit field]
and second
- the UE shall use the number of layers (υ ) , the total number of allocated PRBs (n PRB ) to determine the transport
block size based on the procedure defined in Subclause 6.1.4.2.
[TS 38.321, clause 5.4.1]
If the MAC entity has a C-RNTI, a Temporary C-RNTI, or CS-RNTI, the MAC entity shall for each PDCCH occasion
1> if an uplink grant for this Serving Cell has been received on the PDCCH for the MAC entity's C-RNTI or
2> if the uplink grant is for MAC entity's 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 MAC entity's CS-RNTI or a
NDI.
2> if the uplink grant is for MAC entity's C-RNTI, and the identified HARQ process is configured for a
3> start or restart the configuredGrantTimer for the correponding HARQ process, if configured.
1> else if an uplink grant for this PDCCH occasion has been received for this Serving Cell on the PDCCH for the
MAC entity's CS-RNTI:
ETSI
3> start or restart the configuredGrantTimer for the corresponding HARQ process, if configured;
4> trigger configured uplink grant confirmation.
4> trigger configured uplink grant confirmation;
4> store the uplink grant for this Serving Cell and the associated HARQ information as configured uplink
grant;
4> initialise or re-initialise the configured uplink grant for this Serving Cell to start in the associated
4> stop the configuredGrantTimer for the corresponding HARQ process, if running;
1> if the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink
grant received on the PDCCH for this Serving Cell:
2> if the configuredGrantTimer for the corresponding HARQ process is not running:
For configured uplink grants, the HARQ Process ID associated with the first symbol of a UL transmission is derived
from the following equation:
HARQ Process ID = [floor(CURRENT_symbol/periodicity)] modulo nrofHARQ-Processes
where CURRENT_symbol=(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot number in the frame ×

NOTE 1: CURRENT_symbol refers to the symbol index of the first transmission occasion of a repetition bundle
that takes place.
NOTE 2: A HARQ process is configured for a configured uplink grant if the configured uplink grant is activated
and the associated HARQ process ID is less than nrofHARQ-Processes.
[TS 38.321, clause 5.4.2.1]
configured with supplementaryUplink), which maintains a number of parallel HARQ processes.
Each HARQ process is associated with a HARQ process identifier. For UL transmission with UL grant in RA
Response, HARQ process identifier 0 is used.
ETSI
When the MAC entity is configured with pusch-AggregationFactor > 1, the parameter pusch-AggregationFactor
provides the number of transmissions of a TB within a bundle of the dynamic grant. After the initial transmission,
pusch-AggregationFactor – 1 HARQ retransmissions follow within a bundle. When the MAC entity is configured with
repK > 1, the parameter repK provides the number of transmissions of a TB within a bundle of the configured uplink
grant. After the initial transmission, HARQ retransmissions follow within a bundle. For both dynamic grant and
configured uplink grant, 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 triggered without waiting for
feedback from previous transmission according to pusch-AggregationFactor for a dynamic grant and repK for a
configured uplink grant, respectively. Each transmission within a bundle is a separate uplink grant after the initial
uplink grant within a bundle is delivered to the HARQ entity.
For each transmission within a bundle of the dynamic grant, the sequence of redundancy versions is determined
according to subclause 6.1.4 of TS 38.214 [7]. For each transmission within a bundle of the configured uplink grant, the
sequence of redundancy versions is determined according to subclause 6.1.2.3 of TS 38.214 [7].
1> identify the HARQ process associated with this grant, and for each identified HARQ process:
empty; or
2> if the uplink grant was received in a Random Access Response; or
2> if the uplink grant is part of a bundle of the configured uplink grant, and may be used for initial transmission
according to subclause 6.1.2.3 of TS 38.214 [7], and if no MAC PDU has been obtained for this bundle:
3> if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access
Response:
3> else:
4> obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any;
HARQ process;
4> instruct the identified HARQ process to trigger a new transmission;
4> if the uplink grant is addressed to CS-RNTI; or
4> if the uplink grant is a configured uplink grant; or
4> if the uplink grant is addressed to C-RNTI, and the identified HARQ process is configured for a
5> start or restart the configuredGrantTimer, if configured, for the corresponding HARQ process
3> else:
4> flush the HARQ buffer of the identified HARQ process.
2> else (i.e. retransmission):
identified process is empty; or
3> if the uplink grant is part of a bundle and if no MAC PDU has been obtained for this bundle; or
ETSI
3> if the uplink grant is part of a bundle of the configured uplink grant, and the PUSCH of the uplink grant
overlaps with a PUSCH of another uplink grant received on the PDCCH for this Serving Cell:
3> else:
HARQ process;
[TS 38.321, clause 5.4.2.2]
Each HARQ process is associated with a HARQ buffer.
New transmissions are performed on the resource and with the MCS indicated on either PDCCH, Random Access
Response, or RRC. Retransmissions are performed on the resource and, if provided, with the MCS indicated on
PDCCH, or on the same resource and with the same MCS as was used for last made transmission attempt within a
bundle.
If the HARQ entity requests a new transmission for a TB, the HARQ process shall:
1> store the MAC PDU in the associated HARQ buffer;
If the HARQ entity requests a retransmission for a TB, the HARQ process shall:
To generate a transmission for a TB, the HARQ process shall:
1> if the MAC PDU was obtained from the Msg3 buffer; or
1> 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:
2> instruct the physical layer to generate a transmission according to the stored uplink grant.
ETSI

U-S Message
0A SS transmits in the indicated <--- - - -

downlink assignment an NR
RRCReconfiguration. (Note 1)
0B UE transmits NR --> - - -
RRCReconfigurationComplete
message to the SS. (Note 2)
1 The SS transmits a valid MAC <--- MAC PDU - -
PDU containing one RLC PDU.
2 The UE transmits a Scheduling --> (SR) - -
Request.
3 The SS allocates an UL Grant for <-- UL Grant - -
HARQ process 1, sufficient for
one RLC SDU to be looped back
in a slot n, and NDI indicates new
transmission and DCI scheduling
the PUSCH indicates rvID = 0.
4 Check: Does the UE transmit a --> MAC PDU 1 P
MAC PDU including one RLC
SDU, in HARQ process 1 and in
slot n+4 and repeats in following
pusch-AggregationFactor-1 slots
with same resource allocation but
different redundancy version
(Note 3), if the slot can be used
for uplink transmission (Note 4)
5 SS transmits a MAC PDU <-- MAC PDU (RLC STATUS -
containing an RLC STATUS PDU PDU)
acknowledging the reception of
the AMD PDU in step 4.
Note 1: For EN-DC the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration
36.508 [7], Table 4.6.1-8 using condition EN-DC_EmbedNR_RRCRecon.
Note 3: The redundancy version for the first transmission and all possible repetitions are set in the following
order {0, 2, 3, 1} according to TS 38.214 [15] Table 6.1.2.1-2, first row.
Note 4: Usage of correct redundancy version is implicitely checked upon correct decoding by the SS of the
UE UL repetitions.
Table 7.1.1.3.9.3.3-0A: RRCReconfiguration (step 0A, Table 7.1.1.3.9.3.2-1)

(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI
Table 7.1.1.3.9.3.3-0B: CellGroupConfig (Table 7.1.1.3.9.3.3-0A: RRCReconfiguration)

cellGroupId 0
1 EN-DC
servingCellConfig ServingCellConfig
}
}
}
Table 7.1.1.3.9.3.3-1: ServingCellConfig (Table 7.1.1.3.9.3.3-0B: CellGroupConfig)

}
}

pusch-Config CHOICE { Not present
Setup PUSCH-Config
}
}
Table 7.1.1.3.9.3.3-3: PUSCH-Config (Table 7.1.1.3.9.3.3-2)

PUSCH-Config ::= SEQUENCE {
pusch-AggregationFactor n4
n8 (TDD AND
SCS15) OR
FR2
}
7.1.1.3.10 Correct Handling of HARQ process / Multiple CORESETPoolIndex
7.1.1.3.10.1. Test Purpose (TP)
(1)
with { UE in RRC_CONNECTED state and is configured with PDCCH-Config that contains two different
values of CORESETPoolIndex in ControlResourceSet }
ensure that {
when { UE receives PDCCHs that schedule two non-overlapping in time domain PUSCHs are associated
to different ControlResourceSets having different values of CORESETPoolIndex }
then { UE sends PUSCHs following the scheduling information of PDCCHs }
}
ETSI
(2)
with(UE in RRC_CONNECTED state and is configured with PDCCH-Config that contains two different
values of CORESETPoolIndex in ControlResourceSet)
ensure that {
when{ UE receives PDCCHs that schedule two overlapping in time domain PDSCHs are associated to
different ControlResourceSets having different values of CORESETPoolIndex }
then { UE Receives PDSCHs following the scheduling information of PDCCHs }
}
[TS 38.214, clause 5.11]
If a UE is configured by higher layer parameter PDCCH-Config that contains two different values of
CORESETPoolIndex in ControlResourceSet, the UE may expect to receive multiple PDCCHs scheduling
fully/partially/non-overlapped PDSCHs in time and frequency domain. The UE may expect the reception of
full/partially-overlapped PDSCHs in time only when PDCCHs that schedule two PDSCHs are associated to different
ControlResourceSets having different values of CORESETPoolIndex. For a ControlResourceSet without
CORESETPoolIndex, the UE may assume that the ControlResourceSet is assigned with CORESETPoolIndex as 0.
When the UE is scheduled with full/partially/non-overlapped PDSCHs in time and frequency domain, the full
scheduling information for receiving a PDSCH is indicated and carried only by the corresponding PDCCH, the UE is
expected to be scheduled with the same active BWP and the same SCS. When the UE is scheduled with full/partially-
overlapped PDSCHs in time and frequency domain, the UE can be scheduled with at most two codewords
simultaneously. When PDCCHs that schedule two PDSCHs are associated to different ControlResourceSets having
different values of CORESETPoolIndex, the following operations are allowed:
- For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH
starting in symbol j by a PDCCH associated with a value of CORESETpoolIndex ending in symbol i, the UE can
be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH associated with
a different value of CORESETpoolIndex that ends later than symbol i.
- In a given scheduled cell, the UE can receive a first PDSCH in slot i, with the corresponding HARQ-ACK
assigned to be transmitted in slot j, and a second PDSCH associated with a value of CORESETpoolindex
different from that of the first PDSCH starting later than the first PDSCH with its corresponding HARQ-ACK
assigned to be transmitted in a slot before slot j.
If PDCCHs that schedule corresponding PDSCHs are associated to the same or different ControlResourceSets having
the same value of CORESETPoolIndex, the UE procedure for receiving the PDSCH upon detection of a PDCCH
follows Clause 5.1.
[TS 38.214, clause 6.1]
If a UE is configured by higher layer parameter PDCCH-Config that contains two different values of
CORESETPoolIndex in ControlResourceSet for the active BWP of a serving cell and PDCCHs that schedule two non-
overlapping in time domain PUSCHs are associated to different ControlResourceSets having different values of
CORESETPoolIndex, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first
PUSCH transmission starting in symbol j by a PDCCH associated with a value of CORESETpoolIndex ending in
symbol i, the UE can be scheduled to transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH
associated with a different value of CORESETpoolIndex that ends later than symbol i.
ETSI

U-S Message
1 SS transmits NR RRCReconfiguration <-- - - -
message to configure two different values of
CORESETPoolIndex in ControlResourceSet,
(Note1)
2 The UE transmitNR --> - - -
RRCReconfigurationComplete messages
(Note 2)
3 The SS transmits 2 MAC PDU’s on <-- MAC PDU 1, MAC PDU 2 - -
overlapping PDSCH’s scheduled by two
different values of CORESETPoolIndex in
ControlResourceSet
4 100 ms after step 4, the SS transmits a two UL <-- (UL Grant 1, UL Grant 2) - -
grants scheduling two non-overlapping in time
domain PUSCHs associated to different
ControlResourceSets having different values
of CORESETPoolIndex
5 Check: The UE transmits 2 MAC PDU’s loop --> MAC PDU 1, MAC PDU 2 1,2 P
backed PDU’s from step 4
Table 7.1.1.3.10.3.3-1: PDCCH-Config (Preamble)

controlResourceSetToAddModList 2 entries
ControlResourceSet {
}
}

coresetPoolIndex-r16 0
}

coresetPoolIndex-r16 1
}
ETSI
7.1.1.3.11 Correct handling of UL grant prioritization
(1)
，
with { UE in RRC_CONNECTED and configured with lch-basedPrioritization and a resource conflict
happened when the UE is sending data based on a UL grant which is addressed to CS-RNTI with NDI = 1
or C-RNTI }
ensure that {
when { the data causes the resource conflict is based on a configured UL grant whose priority is
lower than or equal to the UL grant’s }
then { UE determines the UL grant to be prioritized and sends the corresponding MAC PDU.}
}
(2)
，
with { UE in RRC_CONNECTED and configured with lch-basedPrioritization a resource conflict happened
when the UE is sending data based on a UL grant which is addressed to CS-RNTI with NDI = 1 or C-
RNTI, and UE determines the UL grant to be prioritized }
ensure that {
when { UE sends out the MAC PDU associated with the prioritized grant }
then { autonomously re-transmit the MAC PDU associated with the de-prioritized grant.}
}
[TS 38.321, clause 5.4.1]
For the MAC entity configured with lch-basedPrioritization, priority of an uplink grant is determined by the highest
priority among priorities of the logical channels with data available that are multiplexed or can be multiplexed in the
MAC PDU, according to the mapping restrictions as described in clause 5.4.3.1.2. The priority of an uplink grant for
which no data for logical channels is multiplexed or can be multiplexed in the MAC PDU is lower than either the
priority of an uplink grant for which data for any logical channels is multiplexed or can be multiplexed in the MAC
PDU or the priority of the logical channel triggering an SR.
If the corresponding PUSCH transmission of a configured uplink grant is cancelled by CI-RNTI as specified in clause
11.2A of TS 38.213 [6] or cancelled by a high PHY-priority PUCCH transmission as specified in clause 9 of TS 38.213
[6], this uplink grant is considered as a de-prioritized uplink grant.
When the MAC entity is configured with lch-basedPrioritization, for each uplink grant whose associated PUSCH can
be transmitted by lower layers, the MAC entity shall:
1> if this uplink grant is addressed to CS-RNTI with NDI = 1 or C-RNTI:
2> if there is no overlapping PUSCH duration of a configured uplink grant which was not already de-prioritized,
in the same BWP whose priority is higher than the priority of the uplink grant; and
2> if there is no overlapping PUCCH resource with an SR transmission which was not already de-prioritized and
the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant:
3> consider this uplink grant as a prioritized uplink grant;
3> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s);
3> consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s).
1> else if this uplink grant is a configured uplink grant:
2> if there is no overlapping PUSCH duration of another configured uplink grant which was not already de-
prioritized, in the same BWP, whose priority is higher than the priority of the uplink grant; and
ETSI
2> if there is no overlapping PUSCH duration of an uplink grant addressed to CS-RNTI with NDI = 1 or C-
RNTI which was not already de-prioritized, in the same BWP, whose priority is higher than or equal to the
priority of the uplink grant; and
2> if there is no overlapping PUCCH resource with an SR transmission which was not already de-prioritized and
the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant:
3> consider this uplink grant as a prioritized uplink grant;
3> consider the other overlapping uplink grant(s), if any, as a de-prioritized uplink grant(s);
3> consider the other overlapping SR transmission(s), if any, as a de-prioritized SR transmission(s).
NOTE 6: If the MAC entity is configured with lch-basedPrioritization and if there is overlapping PUSCH duration
of at least two configured uplink grants whose priorities are equal, the prioritized uplink grant is
determined by UE implementation.
NOTE 7: If the MAC entity is not configured with lch-basedPrioritzation and if there is overlapping PUSCH
duration of at least two configured uplink grants, it is up to UE implementation to choose one of the
configured uplink grants.
[TS 38.321, clause 5.4.2.1]
Each HARQ process is associated with a HARQ process identifier. For UL transmission with UL grant in RA Response
or for UL transmission for MSGA payload, HARQ process identifier 0 is used.
NOTE: When a single DCI is used to schedule multiple PUSCH, the UE is allowed to map generated TB(s)
internally to different HARQ processes in case of LBT failure(s), i.e. UE may transmit a new TB on any
HARQ process in the grants that have the same TBS, the same RV and the NDIs indicate new
transmission.
The number of transmissions of a TB within a bundle of the dynamic grant or configured grant is given by
REPETITION_NUMBER as follows:
- For a dynamic grant, REPETITION_NUMBER is set to a value provided by lower layers, as specified in clause
6.1.2.1 of TS 38.214 [7];
- For a configured grant, REPETITION_NUMBER is set to a value provided by lower layers, as specified in clause
6.1.2.3 of TS 38.214 [7].
If REPETITION_NUMBER > 1, after the first transmission within a bundle, REPETITION_NUMBER – 1 HARQ
retransmissions follow within the bundle. For both dynamic grant and configured uplink grant, 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 triggered without waiting for feedback from previous transmission according to
REPETITION_NUMBER for a dynamic grant or configured uplink grant. Each transmission within a bundle is a
separate uplink grant delivered to the HARQ entity.
according to clause 6.1.2.1 of TS 38.214 [7]. For each transmission within a bundle of the configured uplink grant, the
sequence of redundancy versions is determined according to clause 6.1.2.3 of TS 38.214 [7].
ETSI
empty; or
2> if the uplink grant was received in a Random Access Response (i.e. in a MAC RAR or a fallback RAR); or
2> if the uplink grant was determined as specified in clause 5.1.2a for the transmission of the MSGA payload; or
2> if the uplink grant was received on PDCCH for the C-RNTI in ra-ResponseWindow and this PDCCH
successfully completed the Random Access procedure initiated for beam failure recovery; or
according to clause 6.1.2.3 of TS 38.214 [7], and if no MAC PDU has been obtained for this bundle:
3> if there is a MAC PDU in the MSGA buffer and the uplink grant determined as specified in clause 5.1.2a
for the transmission of the MSGA payload was selected; or
3> if there is a MAC PDU in the MSGA buffer and the uplink grant was received in a fallbackRAR and this
fallbackRAR successfully completed the Random Access procedure:
4> obtain the MAC PDU to transmit from the MSGA buffer.
3> else if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a fallbackRAR:
3> else if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a MAC RAR; or:
3> if there is a MAC PDU in the Msg3 buffer and the uplink grant was received on PDCCH for the C-RNTI
in ra-ResponseWindow and this PDCCH successfully completed the Random Access procedure initiated
for beam failure recovery:
4> if the uplink grant size does not match with size of the obtained MAC PDU; and
4> if the Random Access procedure was successfully completed upon receiving the uplink grant:
5> indicate to the Multiplexing and assembly entity to include MAC subPDU(s) carrying MAC SDU
from the obtained MAC PDU in the subsequent uplink transmission;
5> obtain the MAC PDU to transmit from the Multiplexing and assembly entity.
3> else if this uplink grant is a configured grant configured with autonomousTx; and
3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and
3> if a MAC PDU had already been obtained for this HARQ process; and
3> if the uplink grant size matches with size of the obtained MAC PDU; and
3> if a transmission of the obtained MAC PDU has not been performed:
4> consider the MAC PDU has been obtained.
3> else if the MAC entity is not configured with lch-basedPrioritization; or
3> if this uplink grant is a prioritized uplink grant:
4> if the uplink grant is not a configured grant configured with autonomousTx; or
4> if the uplink grant is a prioritized uplink grant:
HARQ process;
ETSI
5> if the uplink grant is a configured uplink grant:
when the transmission is performed if LBT failure indication is not received from lower layers;
6> start or restart the cg-RetransmissionTimer, if configured, for the corresponding HARQ process
when the transmission is performed if LBT failure indication is not received from lower layers.
5> if cg-RetransmissionTimer is configured for the identified HARQ process; and
5> if the transmission is performed and LBT failure indication is received from lower layers:
6> consider the identified HARQ process as pending.
3> else:
3> if the uplink grant is part of a bundle of the configured uplink grant, and the PUSCH duration of the
uplink grant overlaps with a PUSCH duration of another uplink grant received on the PDCCH or an
uplink grant received in a Random Access Response (i.e. MAC RAR or fallbackRAR) or an uplink grant
determined as specified in clause 5.1.2a for MSGA payload for this Serving Cell; or:
3> if the MAC entity is configured with lch-basedPrioritization and this uplink grant is not a prioritized
uplink grant:
3> else:
HARQ process;
5> if the identified HARQ process is pending:
ETSI
4> if the identified HARQ process is pending and the transmission is performed and LBT failure
indication is not received from lower layers:
5> consider the identified HARQ process as not pending.
When configuredGrantTimer or cg-RetransmissionTimer is started or restarted by a PUSCH transmission, it shall be

started at the beginning of the first symbol of the PUSCH transmission.
Same Pre-test conditions as in clause 7.1.1.0 except that the UM DRB is configured and the logical channels are
configured according to 7.1.1.3.11.3.1-1.

Parameter DRB1 DRB2
Priority 6 7
ETSI

U-S Message
1
SS transmits NR RRCReconfiguration <-- RRCReconfiguration - -
message to configure type 2 configured uplink
grant. (Note 1)
2 The UE transmits NR --> RRCReconfigurationComplete - -
RRCReconfigurationComplete. (Note 2)
4 SS transmits a MAC PDU including a RLC <-- MAC PDU (1 RLC SDU of 40 - -
SDU-1 on LCH 4. bytes on DRB)
5 The SS allocates an UL Grant (with size 384 <-- (UL Grant (C-RNTI)) - -
bits that only sufficient for one RLC SDU to be
looped back in a Slot) for one HARQ process
X and NDI indicates new transmission
redundancy version to be used as 0.
6 The UE transmit a MAC PDU including the --> MAC PDU - -
RLC SDU-1, in HARQ process X.
7 SS transmits a MAC PDU including a RLC <-- MAC PDU (1 RLC SDU of 40 - -
SDU-2 on LCH 5. bytes on DRB)
8 SS transmits a configured UL Grant (with size <-- (UL Grant (CS-RNTI)) - -
384 bits that only sufficient for one RLC SDU
to be looped back in a Slot), on PDCCH with
the CS-RNTI assigned to the UE, allowing the
UE to return the RLC SDU-2 (as received in
step 5) in Slot P.
9 The SS transmits an UL grant corresponding <-- (UL Grant (C-RNTI)) - -
to slot for HARQ process X, with NDI not
1. (Note 3)
including RLC SDU-1 in slot P?
11 Check: Does the UE transmit the MAC PDU --> MAC PDU 2 P
including RLC SDU-2 after slot P?
Note 3: The UL grant slot is equal to the configured slot in step 8.

(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

mac-CellGroupConfig MAC-CellGroupConfig Table
7.1.1.3.11.3.3-3
physicalCellGroupConfig PhysicalCellGroupConfig Table
7.1.1.3.11.3.3-4
}
Table 7.1.1.3.11.3.3-3: MAC-CellGroupConfig (Table 7.1.1.3.11.3.3-2)

lch-BasedPrioritization-r16 enabled
}
Table 7.1.1.3.11.3.3-4: PhysicalCellGroupConfig (Table 7.1.1.3.11.3.3-2)

PhysicalCellGroupConfig ::= SEQUENCE {
cs-RNTI ‘FFE0’H
}
7.1.1.3.12 Correct Handling of UL HARQ process / PUSCH Repetition Type B
(1)
with { UE in RRC_CONNECTED state and is configured with PUSCH repetition type B}
ensure that {
then { UE transmits a new MAC PDU and repeats the MAC PDU in pusch-AggregationFactor-1 times
after first transmission and selects the redundancy version correctly }
}
6.1.4, TS 38.321 clause 5.4.2.1. Unless otherwise stated these are Rel-16 requirements.
[TS 38.214, clause 6.1.2.1]
- for PUSCH scheduled by DCI format 0_1, if pusch-RepTypeIndicatorDCI-0-1 is set to 'pusch-RepTypeB', the
UE applies PUSCH repetition Type B procedure when determining the time domain resource allocation. For
PUSCH scheduled by DCI format 0_2, if pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeB', the UE
applies PUSCH repetition Type B procedure when determining the time domain resource allocation. Otherwise,
the UE applies PUSCH repetition Type A procedure when determining the time domain resource allocation for
PUSCH scheduled by PDCCH.
- For PUSCH repetition Type A, the starting symbol S relative to the start of the slot, and the number of
consecutive symbols L counting from the symbol S allocated for the PUSCH are determined from the start and
length indicator SLIV of the indexed row:
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
ETSI
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤14− S , and
- For PUSCH repetition Type B, the starting symbol S relative to the start of the slot, and the number of
consecutive symbols L counting from the symbol S allocated for the PUSCH are provided by startSymbol and
length of the indexed row of the resource allocation table, respectively.
- For PUSCH repetition Type A, the PUSCH mapping type is set to Type A or Type B as defined in Clause
6.4.1.1.3 of [4, TS 38.211] as given by the indexed row.
- For PUSCH repetition Type B, the PUSCH mapping type is set to Type B.

Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
(repetition Type
A only)
Type B {0,…,13} {1,…,14} {1,…,14} for {0,…, 11} {1,…,12} {1,…,12} for
repetition Type A, repetition Type A,
{1,…,27} for {1,…,23} for
repetition Type B repetition Type B
For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCI format 0_1 or 0_2 in PDCCH with CRC
scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, the number of repetitions K is determined as
- if numberOfRepetitions is present in the resource allocation table, the number of repetitions K is equal to
numberOfRepetitions;
- elseif the UE is configured with pusch-AggregationFactor, the number of repetitions K is equal to pusch-
AggregationFactor;
- otherwise K=1.
If a UE is configured with higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH, the UE does not

expect to be configured with pusch-AggregationFactor.
For PUSCH repetition Type A, in case K>1, the same symbol allocation is applied across the K consecutive slots and
the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the K consecutive slots applying
the same symbol allocation in each slot. The redundancy version to be applied on the nth transmission occasion of the
TB, where n = 0, 1, … K-1, is determined according to table 6.1.2.1-2.
Table 6.1.2.1-2: Redundancy version for PUSCH transmission

rvid indicated by the DCI rvid to be applied to nth transmission occasion (repetition Type A) or nth
scheduling the PUSCH actual repetition (repetition Type B)
n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3
0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
When transmitting MsgA PUSCH on a non-initial UL BWP, if the UE is configured with startSymbolAndLengthMsgA-
PO, the UE shall determine the S and L from startSymbolAndLengthMsgA-PO.
ETSI
When transmitting MsgA PUSCH, if the UE is not configured with startSymbolAndLengthMsgA-PO, and if the TDRA
list PUSCH-TimeDomainResourceAllocationList is provided in PUSCH-ConfigCommon, the UE shall use msgA-
PUSCH-TimeDomainAllocation to indicate which values are used in the list. If PUSCH-
TimeDomainResourceAllocationList is not provided in PUSCH-ConfigCommon, the UE shall use parameters S and L
from table 6.1.2.1.1-2 or table 6.1.2.1.1-3 where msgA-PUSCH-TimeDomainAllocation indicates which values are used
in the list. The time offset for PUSCH transmission is described in [6, TS38.213].
For PUSCH repetition Type A, a PUSCH transmission in a slot of a multi-slot PUSCH transmission is omitted
according to the conditions in Clause 9, Clause 11.1 and Clause 11.2A of [6, TS38.213].
For PUSCH repetition Type B, except for PUSCH transmitting CSI report(s) with no transport block, the number of
nominal repetitions is given by numberOfRepetitions. For the n-th nominal repetition, n = 0, …, numberOfRepetitions -
1,
S + n⋅ L
- The slot where the nominal repetition starts is given by Ks +  slot , and the starting symbol relative to the
 Nsymb 
(
start of the slot is given by mod S + n ⋅ L, Nsymb .
slot
)
S + ( n + 1) ⋅ L − 1
- The slot where the nominal repetition ends is given by K s +  slot , and the ending symbol relative
 N symb 
(
to the start of the slot is given by mod S + ( n +1) ⋅ L −1, Nsymb .
slot
)
Here K s is the slot where the PUSCH transmission starts, and N symb
slot
is the number of symbols per slot as defined in
Clause 4.3.2 of [4, TS38.211].
For PUSCH repetition Type B, the UE determines invalid symbol(s) for PUSCH repetition Type B transmission as
follows:
- A symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-

ConfigurationDedicated is considered as an invalid symbol for PUSCH repetition Type B transmission.
- For operation in unpaired spectrum, symbols indicated by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst

in ServingCellConfigCommon for reception of SS/PBCH blocks are considered as invalid symbols for PUSCH
repetition Type B transmission.
- For operation in unpaired spectrum, symbol(s) indicated by pdcch-ConfigSIB1 in MIB for a CORESET for
Type0-PDCCH CSS set are considered as invalid symbol(s) for PUSCH repetition Type B transmission.
- For operation in unpaired spectrum, if numberOfInvalidSymbolsForDL-UL-Switching is configured,

numberOfInvalidSymbolsForDL-UL-Switching symbol(s) after the last symbol that is indicated as downlink in
each consecutive set of all symbols that are indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-
UL-DL-ConfigurationDedicated are considered as invalid symbol(s) for PUSCH repetition Type B transmission.
The symbol(s) given by numberOfInvalidSymbolsForDL-UL-Switching are defined using the reference SCS
configuration referenceSubcarrierSpacing provided in tdd-UL-DL-ConfigurationCommon.
- The UE may be configured with the higher layer parameter invalidSymbolPattern, which provides a symbol
level bitmap spanning one or two slots (higher layer parameter symbols given by invalidSymbolPattern). A bit
value equal to 1 in the symbol level bitmap symbols indicates that the corresponding symbol is an invalid symbol
for PUSCH repetition Type B transmission. The UE may be additionally configured with a time-domain pattern
(higher layer parameter periodicityAndPattern given by invalidSymbolPattern), where each bit of
periodicityAndPattern corresponds to a unit equal to a duration of the symbol level bitmap symbols, and a bit
value equal to 1 indicates that the symbol level bitmap symbols is present in the unit. The periodicityAndPattern
can be {1, 2, 4, 5, 8, 10, 20 or 40} units long, but maximum of 40 msec. The first symbol of
periodicityAndPattern every 40 msec/P periods is a first symbol in frame ݂݊ mod 4 = 0, where P is the duration
of periodicityAndPattern-r16 in units of msec. When periodicityAndPattern is not configured, for a symbol level
bitmap spanning two slots, the bits of the first and second slots correspond respectively to even and odd slots of a
radio frame, and for a symbol level bitmap spanning one slot, the bits of the slot correspond to every slot of a
radio frame. If invalidSymbolPattern is configured, when the UE applies the invalid symbol pattern is
determined as follows:
ETSI
- if the PUSCH is scheduled by DCI format 0_1, or corresponds to a Type 2 configured grant activated by DCI
format 0_1, and if invalidSymbolPatternIndicatorDCI-0-1 is configured,
- if invalid symbol pattern indicator field is set 1, the UE applies the invalid symbol pattern;
- otherwise, the UE does not apply the invalid symbol pattern;
- if the PUSCH is scheduled by DCI format 0_2, or corresponds to a Type 2 configured grant activated by DCI
format 0_2, and if invalidSymbolPatternIndicatorDCI-0-2 is configured,
- if invalid symbol pattern indicator field is set 1, the UE applies the invalid symbol pattern;
- otherwise, the UE does not apply the invalid symbol pattern;
- otherwise, the UE applies the invalid symbol pattern.
- If the UE
- is configured with multiple serving cells and is provided half-duplex-behavior = 'enable', and
- is not capable of simultaneous transmission and reception on any of the multiple serving cells, and
- indicates support of capability for half-duplex operation in CA with unpaired spectrum, and
- is not configured to monitor PDCCH for detection of DCI format 2-0 on any of the multiple serving cells,
- a symbol is considered as an invalid symbol in any of the multiple serving cells for PUSCH repetition Type B
transmission if the symbol is indicated to the UE for reception of SS/PBCH blocks in any of the multiple serving
cells by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, and
a symbol is considered as an invalid symbol in any of the multiple serving cells for PUSCH repetition Type B
transmission with Type 1 or Type 2 configured grant except for the first Type 2 PUSCH transmission (including
all repetitions) after activation if the symbol is indicated as downlink by tdd-UL-DL-ConfigurationCommon or
tdd-UL-DL-ConfigurationDedicated on the reference cell, or the UE is configured by higher layers to receive
PDCCH, PDSCH, or CSI-RS on the reference cell in the symbol.
For PUSCH repetition Type B, after determining the invalid symbol(s) for PUSCH repetition type B transmission for
each of the K nominal repetitions, the remaining symbols are considered as potentially valid symbols for PUSCH
repetition Type B transmission. If the number of potentially valid symbols for PUSCH repetition type B transmission is
greater than zero for a nominal repetition, the nominal repetition consists of one or more actual repetitions, where each
actual repetition consists of a consecutive set of all potentially valid symbols that can be used for PUSCH repetition
Type B transmission within a slot. An actual repetition with a single symbol is omitted except for the case of L=1. An
actual repetition is omitted according to the conditions in Clause 9, Clause 11.1 and Clause 11.2A of [6, TS38.213]. The
redundancy version to be applied on the nth actual repetition (with the counting including the actual repetitions that are
omitted) is determined according to table 6.1.2.1-2.
For PUSCH repetition Type B, when a UE receives a DCI that schedules aperiodic CSI report(s) or activates semi-
persistent CSI report(s) on PUSCH with no transport block by a 'CSI request' field on a DCI, the number of nominal
repetitions is always assumed to be 1, regardless of the value of numberOfRepetitions. When the UE is scheduled to
transmit a PUSCH repetition Type B with no transport block and with aperiodic or semi-persistent CSI report(s) by a
'CSI request' field on a DCI, the first nominal repetition is expected to be the same as the first actual repetition. For
PUSCH repetition Type B carrying semi-persistent CSI report(s) without a corresponding PDCCH after being activated
on PUSCH by a 'CSI request' field on a DCI, if the first nominal repetition is not the same as the first actual repetition,
the first nominal repetition is omitted; otherwise, the first nominal repetition is omitted according to the conditions in
Clause 9, Clause 11.1 and Clause 11.2A of [6, TS38.213].
For PUSCH repetition Type B, when a UE is scheduled to transmit a transport block and aperiodic CSI report(s) on
PUSCH by a 'CSI request' field on a DCI, the CSI report(s) is multiplexed only on the first actual repetition. The UE
does not expect that the first actual repetition has a single symbol duration.
[TS 38.214, clause 6.1.4]
To determine the modulation order, target code rate, redundancy version and transport block size for the physical uplink
shared channel, the UE shall first
ETSI
- read the 5-bit modulation and coding scheme field (I MCS ) in the DCI scheduling PUSCH or provided in a DCI
activating a configured grant Type 2 PUSCH, or as provided by mcsAndTBS as described in Clause 6.1.2.3 for a
configured grant Type 1 PUSCH to determine the modulation order (Om ) and target code rate (R) based on the
procedure defined in Clause 6.1.4.1
- read redundancy version field (rv) in the DCI to determine the redundancy version for PUSCH scheduled by
DCI, or determine the redundancy version according to Clause 6.1.2.3.1 for configured grant Type 1 and Type 2
PUSCH,
and second
- use the number of layers (υ ) , the total number of allocated PRBs (n PRB ) to determine the transport block size
based on the procedure defined in Clause 6.1.4.2.
When the UE is scheduled with multiple PUSCHs by a DCI, as described in clause 6.1.2.1, the bits of rv field and NDI
field, respectively, in the DCI are one to one mapped to the scheduled PUSCH(s) with the corresponding transport
block(s) in the scheduled order where the LSB bits of the rv field and NDI field, respectively, correspond to the last
scheduled PUSCH.
Within a cell group, a UE is not required to handle PUSCH(s) transmissions in slot sj in serving cell-j, and for j = 0,1,2..
J-1, slot sj overlapping with any given point in time, if the following condition is not satisfied at that point in time:
where
- J is the number of configured serving cells belong to a frequency range
- for the j-th serving cell,
- M is the number of TB(s) transmitted in slot-sj. For PUSCH repetition Type B, each actual repetition is
counted separately.
- Tslotμ(j) =10-3/2μ(j), where μ(j) is the numerology for PUSCH(s) in slot sj of the j-th serving cell.
- for the m-th TB,
- A is the number of bits in the transport block as defined in Clause 6.2.1 [5, TS 38.212]
- C is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212].
- is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1
[5,38.212]
- [Mbps] is computed as the maximum data rate summed over all the carriers in the frequency range
for any signalled band combination and feature set consistent with the configured servings cells, where the data
rate value is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor f(i).
For a j-th serving cell, if higher layer parameter processingType2Enabled of PUSCH-ServingCellConfig is configured
for the serving cell and set to 'enable', or if at least one IMCS > W for a PUSCH, where W = 28 for MCS tables 5.1.3.1-1
and 5.1.3.1-3, and W = 27 for MCS tables 5.1.3.1-2, 6.1.4.1-1, and 6.1.4.1-2, or if it is an actual repetition for PUSCH
repetition Type B, the UE is not required to handle PUSCH transmissions, if the following condition is not satisfied:
where
- is the number of symbols assigned to the PUSCH
- M is the number of TB in the PUSCH
ETSI
- where μ is the numerology of the PUSCH
- for the m-th TB,
- A is the number of bits in the transport block as defined in Clause 6.2.1 [5, TS 38.212]
- C is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212]
- is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, TS 38.212]
- [Mbps] is computed as the maximum data rate for a carrier in the frequency band of the serving
cell for any signalled band combination and feature set consistent with the serving cell, where the data rate value
is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor f(i)
- each actual repetition for PUSCH repetition type B is treated as one PUSCH.
[TS 38.321, clause 5.4.2.1]
Each HARQ process is associated with a HARQ process identifier. For UL transmission with UL grant in RA Response
or for UL transmission for MSGA payload, HARQ process identifier 0 is used.
NOTE: When a single DCI is used to schedule multiple PUSCH, the UE is allowed to map generated TB(s)
internally to different HARQ processes in case of LBT failure(s), i.e. UE may transmit a new TB on any
HARQ process in the grants that have the same TBS, the same RV and the NDIs indicate new
transmission.
The maximum number of transmissions of a TB within a bundle of the dynamic grant or configured grant is given by
REPETITION_NUMBER as follows:
- For a dynamic grant, REPETITION_NUMBER is set to a value provided by lower layers, as specified in clause
6.1.2.1 of TS 38.214 [7];
- For a configured grant, REPETITION_NUMBER is set to a value provided by lower layers, as specified in clause
6.1.2.3 of TS 38.214 [7].
If REPETITION_NUMBER > 1, after the first transmission within a bundle, at most REPETITION_NUMBER – 1
HARQ retransmissions follow within the bundle. For both dynamic grant and configured uplink grant, 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 triggered without waiting for feedback from previous transmission
according to REPETITION_NUMBER for a dynamic grant or configured uplink grant unless they are terminated as
specified in clause 6.1 of TS 38.214 [7]. Each transmission within a bundle is a separate uplink grant delivered to the
HARQ entity.
according to clause 6.1.2.1 of TS 38.214 [7]. For each transmission within a bundle of the configured uplink grant, the
sequence of redundancy versions is determined according to clause 6.1.2.3 of TS 38.214 [7].
empty; or
ETSI
2> if the uplink grant was received in a Random Access Response (i.e. in a MAC RAR or a fallback RAR); or
2> if the uplink grant was determined as specified in clause 5.1.2a for the transmission of the MSGA payload; or
2> if the uplink grant was received on PDCCH for the C-RNTI in ra-ResponseWindow and this PDCCH
successfully completed the Random Access procedure initiated for beam failure recovery; or
according to clause 6.1.2.3 of TS 38.214 [7], and if no MAC PDU has been obtained for this bundle:
3> if there is a MAC PDU in the MSGA buffer and the uplink grant determined as specified in clause 5.1.2a
for the transmission of the MSGA payload was selected; or
3> if there is a MAC PDU in the MSGA buffer and the uplink grant was received in a fallbackRAR and this
fallbackRAR successfully completed the Random Access procedure:
4> obtain the MAC PDU to transmit from the MSGA buffer.
3> else if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a fallbackRAR:
3> else if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a MAC RAR; or:
3> if there is a MAC PDU in the Msg3 buffer and the uplink grant was received on PDCCH for the C-RNTI
in ra-ResponseWindow and this PDCCH successfully completed the Random Access procedure initiated
for beam failure recovery:
4> if the uplink grant size does not match with size of the obtained MAC PDU; and
4> if the Random Access procedure was successfully completed upon receiving the uplink grant:
5> indicate to the Multiplexing and assembly entity to include MAC subPDU(s) carrying MAC SDU
from the obtained MAC PDU in the subsequent uplink transmission;
5> obtain the MAC PDU to transmit from the Multiplexing and assembly entity.
3> else if this uplink grant is a configured grant configured with autonomousTx; and
3> if the previous configured uplink grant, in the BWP, for this HARQ process was not prioritized; and
3> if a MAC PDU had already been obtained for this HARQ process; and
3> if the uplink grant size matches with size of the obtained MAC PDU; and
3> if none of PUSCH transmission(s) of the obtained MAC PDU has been completely performed:
4> consider the MAC PDU has been obtained.
3> else if the MAC entity is not configured with lch-basedPrioritization; or
3> if this uplink grant is a prioritized uplink grant:
4> if the uplink grant is not a configured grant configured with autonomousTx; or
4> if the uplink grant is a prioritized uplink grant:
HARQ process;
ETSI
5> if cg-RetransmissionTimer is configured for the identified HARQ process; and
5> if the transmission is performed and LBT failure indication is received from lower layers:
6> consider the identified HARQ process as pending.
3> else:
3> if the uplink grant is part of a bundle of the configured uplink grant, and the PUSCH duration of the
uplink grant overlaps with a PUSCH duration of another uplink grant received on the PDCCH or an
uplink grant received in a Random Access Response (i.e. MAC RAR or fallbackRAR) or an uplink grant
determined as specified in clause 5.1.2a for MSGA payload for this Serving Cell; or:
3> if the MAC entity is configured with lch-basedPrioritization and this uplink grant is not a prioritized
uplink grant:
3> else:
HARQ process;
5> if the identified HARQ process is pending:
ETSI
4> if the identified HARQ process is pending and the transmission is performed and LBT failure
indication is not received from lower layers:
5> consider the identified HARQ process as not pending.
When configuredGrantTimer or cg-RetransmissionTimer is started or restarted by a PUSCH transmission, it shall be

started at the beginning of the first symbol of the PUSCH transmission.

U-S Message
0A SS transmits in the indicated <--- - - -
downlink assignment an NR
RRCReconfiguration. (Note 1)
0B UE transmits NR --> - - -
message to the SS. (Note 2)
1 The SS transmits a valid MAC <--- MAC PDU - -
PDU containing one RLC PDU.
2 The UE transmits a Scheduling --> (SR) - -
Request.
3 The SS allocates an UL Grant for <-- UL Grant - -
HARQ process 1, sufficient for
one RLC SDU to be looped back
in a slot n, and NDI indicates new
transmission and DCI scheduling
the PUSCH indicates rvID = 0. The
slot n is selected such that slot
n+4 is the first UL slot in subframe
m satisfying (m mod 20) = 9.
SDU, in HARQ process 1 and in
slot n+4 and repeats in actual
repetitions according to Table
7.1.1.3.12.3.2-2 with same
resource allocation but different
redundancy version (Note 3), if
the slot can be used for uplink
transmission (Note 4)
5 SS transmits a MAC PDU <-- MAC PDU (RLC STATUS -
containing an RLC STATUS PDU PDU)
acknowledging the reception of
the AMD PDU in step 4.
Note 3: The redundancy version for the first transmission and all possible actual repetitions (including skipped
ones) are set in the following order {0, 2, 3, 1} according to TS 38.214 [15] Table 6.1.2.1-2, first row.
Note 4: Usage of correct redundancy version is implicitly checked upon correct decoding by the SS of the UE
UL repetitions.
ETSI
Table 7.1.1.3.12.3.2-2: Transmitted actual repetition in each nominal repetition

Nominal repetition 0 Nominal repetition 1 Nominal repetition 2 Nominal repetition 3
(NOTE 1) (NOTE 1) (NOTE 2) (NOTE 3)
FR1 15kHz Actual repetition 0 Actual repetition 0 N/A (NOTE 4, 5) N/A (NOTE 6)
FR1 30kHz Actual repetition 0 Actual repetition 0 Actual repetition 1 Actual repetition 0
(NOTE 4)
FR1 60kHz Actual repetition 0 Actual repetition 0 Actual repetition 1 Actual repetition 0
(NOTE 4)
FR2 120kHz Actual repetition 0 Actual repetition 0 N/A (NOTE 4, 5) N/A (NOTE 6)
NOTE 1: The nominal repetition is in slot n+4 and only one actual repetition expected.
NOTE 2: The nominal repetition is split into two actual repetitions in slot n+4 and n+5 respectively.
NOTE 3: The nominal repetition is in slot n+5 and only one actual repetition expected.
NOTE 4: The actual repetition 0 is skipped due to only 1 valid symbol left according to invalidSymbolPattern-
r16.
NOTE 5: The actual repetition 1 is skipped due to being located in DL symbols
NOTE 6: The actual repetition 0 is skipped due to being located in DL symbols
Table 7.1.1.3.12.3.3-0A: RRCReconfiguration (step 0A, Table 7.1.1.3.12.3.2-1)

(CONTAINING
CellGroupConfig)
}
}
}
}
Table 7.1.1.3.12.3.3-0B: CellGroupConfig (Table 7.1.1.3.12.3.3-0A: RRCReconfiguration)

cellGroupId 0
1 EN-DC
servingCellConfig ServingCellConfig
}
}
}
ETSI
Table 7.1.1.3.12.3.3-1: ServingCellConfig (Table 7.1.1.3.12.3.3-0B: CellGroupConfig)

}
}

pusch-Config CHOICE { Not present
Setup PUSCH-Config
}
}
Table 7.1.1.3.12.3.3-3: PUSCH-Config (Table 7.1.1.3.12.3.3-2)

pusch-TimeDomainAllocationListDCI-0-1-r16
CHOICE {
Setup SEQUENCE (SIZE(1..maxNrofUL-
Allocations-r16)) OF SEQUENCE {
k2-r16 4
puschAllocationList-r16 SEQUENCE
(SIZE(1..maxNrofMultiplePUSCHs-r16)) OF
SEQUENCE {
mappingType-r16 Not present
startSymbolAndLength-r16 Not present
startSymbol-r16 4
length-r16 4
numberOfRepetitions-r16 n4
}
}
}
invalidSymbolPatternIndicatorDCI-0-1-r16 enabled
pusch-RepTypeIndicatorDCI-0-1-r16 pusch-RepTypeB
invalidSymbolPattern-r16 SEQUENCE {
Symbols-r16 CHOICE {
Oneslot 00000000000001
}
periodicityAndPattern-r16 Not present
}
}
ETSI
7.1.1.4 Transport Size Selection
7.1.1.4.1 DL-SCH Transport Block Size Selection
7.1.1.4.1.0 Common parameters for DL-SCH Transport Block Size Selection
Table 7.1.1.4.1.0-1: PDSCH-TimeDomainResourceAllocationList

PDSCH-TimeDomainResourceAllocationList ::= 2 entries
SEQUENCE(SIZE(1..maxNrofDL-Allocations)) OF
PDSCH-TimeDomainResourceAllocation {
PDSCH-TimeDomainResourceAllocation[1] entry 1
SEQUENCE {
k0 Not present
mappingType typeA
startSymbolAndLength 53 S=2, L=12
}
SEQUENCE {
k0 Not present
mappingType typeA
}
}
7.1.1.4.1.1 DL-SCH Transport Block Size selection / DCI format 1_0
(1)
ensure that {
when { UE on PDCCH receives DCI format 1_0 indicating a resource block assignment correspondent to
physical resource blocks , Time domain resource assignment and a modulation and coding }
then { UE decodes the received transport block of size correspondent as per Modulation Coding
scheme, time domain resource allocation and PRB's and forwards it to higher layers }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.212 clause 7.3.1.2.1, TS
38.214 clause 5.1.2.1, 5.1.2.2, 5.1.2.2.2, 5.1.3, 5.1.3.1 and 5.1.3.2. Unless otherwise stated these are Rel-15
requirements.
[TS 38.212, clause 7.3.1.2.1]
DCI format 1_0 is used for the scheduling of PDSCH in one DL cell.
The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-
RNTI or new-RNTI:
- Identifier for DCI formats – 1 bits
- The value of this bit field is always set to 1, indicating a DL DCI format
- Frequency domain resource assignment – log 2 ( N RB

DL,BWP DL,BWP
( N RB + 1) / 2) bits
ETSI
DL,BWP
- N RB is the size of the active DL bandwidth part in case DCI format 1_0 is monitored in the UE specific
search space and satisfying
- the total number of different DCI sizes monitored per slot is no more than 4 for the cell, and
- the total number of different DCI sizes with C-RNTI monitored per slot is no more than 3 for the cell
DL,BWP
otherwise, NRB is the size of the initial DL bandwidth part.
If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field are
of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining fields
set as follows:
- UL/SUL indicator – 1 bit. If the value of the “Random Access Preamble index” is not all zeros and if the UE is
configured with SUL in the cell, this field indicates which UL carrier in the cell to transmit the PRACH according to
Table 7.3.1.1.1-1; otherwise, this field is reserved
- SS/PBCH index – 6 bits. If the value of the “Random Access Preamble index” is not all zeros, this field indicates the
SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this field is
reserved.
- PRACH Mask index – 4 bits. If the value of the “Random Access Preamble index” is not all zeros, this field
indicates the RACH occasion associated with the SS/PBCH indicated by “SS/PBCH index” for the PRACH
Otherwise, all remaining fields are set as follows:
- Time domain resource assignment – 4 bits as defined in Subclause 5.1.2.1 of [6, TS38.214]
- VRB-to-PRB mapping – 1 bit according to Table 7.3.1.1.2-33
- Modulation and coding scheme – 5 bits as defined in Subclause 5.1.3 of [6, TS38.214]
- New data indicator – 1 bit
- Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2
- HARQ process number – 4 bits
- Downlink assignment index – 2 bits as defined in Subclause 9.1.3 of [5, TS38.213], as counter DAI
- TPC command for scheduled PUCCH – 2 bits as defined in Subclause 7.2.1 of [5, TS38.213]
- PUCCH resource indicator – 3 bits as defined in Subclause 9.2.3 of [5, TS38.213]
- PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Subclause 9.2.3 of [5, TS38.213]
[TS 38.214, clause 5.1.2.1]
 2 μ PDSCH 

 2 μ PDCCH 
ETSI
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and
- The PDSCH mapping type is set to Type A or Type B as defined in sub-clause 7.4.1.1.2 of [4, TS 38.211] .

Type A {0,1,2,3} {3,…,14} {3,…,14} {0,1,2,3} {3,…,12} {3,…,12}
(Note 1) (Note 1)
Type B {0,…,12} {2,4,7} {2,…,14} {0,…,10} {2,4,6} {2,…,12}
[38.214 clause 5.1.2.2]
Two downlink resource allocation schemes, type 0 and type 1, are supported. The UE shall assume that when the
scheduling grant is received with DCI format 1_0, then downlink resource allocation type 1 is used.
[38.214 clause 5.1.2.2.2]
In downlink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set
of contiguously allocated non-interleaved or interleaved virtual resource blocks within the active bandwidth part of size
size
N BWP PRBs except for the case when DCI format 1_0 is decoded in any common search space in CORESET 0 in
size
which case the initial bandwidth part of size NBWP,0 shall be used.
A downlink type 1 resource allocation field consists of a resource indication value (RIV) corresponding to a starting
virtual resource block ( RBstart ) and a length in terms of contiguously allocated resource blocks L RBs . The resource
indication value is defined by

if ( L RBs − 1) ≤ N BWP
size
/2  then
RIV = N BWP
size
( LRBs − 1) + RBstart
else
RIV = N BWP
size size
( N BWP − LRBs + 1) + ( N BWP
size
− 1 − RBstart )
where L RBs ≥ 1 and shall not exceed N BWP − RBstart .

size
[TS 38.214, clause 5.1.3]
To determine the modulation order, target code rate, and transport block size(s) in the physical downlink shared
channel, the UE shall first
- read the 5-bit modulation and coding scheme field (IMCS) in the DCI to determine the modulation order (Qm) and
target code rate (R) based on the procedure defined in Subclause 5.1.3.1, and
- read redundancy version field (rv) in the DCI to determine the redundancy version..
ETSI
and second
- the UE shall use the number of layers (ʋ), the total number of allocated PRBs before rate matching (nPRB) to
determine to the transport block size based on the procedure defined in Subclause 5.1.3.2.
The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than
0.95, 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.
[TS 38.214, clause 5.1.3.1]
For the PDSCH scheduled by a PDCCH with DCI format 1_0 or format 1_1 with CRC scrambled by C-RNTI, new-
RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, or P-RNTI,
if the higher layer parameter mcs-Table given by PDSCH-Config is set to 'qam256', and the PDSCH is scheduled by a
PDCCH with a DCI format 1_1 and the CRC is scrambled by C-RNTI or CS-RNTI
- the UE shall use IMCS and Table 5.1.3.1-2 to determine the modulation order (Qm) and Target code rate (R) used
in the physical downlink shared channel.
elseif the UE is not configured with new-RNTI, the higher layer parameter mcs-Table given by PDSCH-Config is set to
'qam64LowSE', and the PDSCH is scheduled with C-RNTI, and the PDSCH is assigned by a PDCCH in a UE-specific
search space
elseif the UE is configured with new-RNTI, and the PDSCH is scheduled with new-RNTI
elseif the UE is not configured with the higher layer parameter mcs-Table given by SPS-config, the higher layer
parameter mcs-Table given by PDSCH-Config is set to 'qam256', the PDSCH is scheduled with CS-RNTI, and the
PDSCH is assigned by a PDCCH with DCI format 1_1
elseif the UE is configured with the higher layer parameter mcs-Table given by SPS-config set to 'qam64LowSE', and
the PDSCH is scheduled with CS-RNTI
else
End
The UE is not expected to decode a PDSCH scheduled with P-RNTI, RA-RNTI, SI-RNTI and Qm > 2
ETSI
Table 5.1.3.1-1: MCS index table 1 for PDSCH

MCS Index Modulation Order Target code Rate R x [1024] Spectral
IMCS Qm efficiency
0 2 120 0.2344
1 2 157 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 438 2.5664
18 6 466 2.7305
19 6 517 3.0293
20 6 567 3.3223
21 6 616 3.6094
22 6 666 3.9023
23 6 719 4.2129
24 6 772 4.5234
25 6 822 4.8164
26 6 873 5.1152
27 6 910 5.3320
28 6 948 5.5547
29 2 reserved
30 4 reserved
31 6 reserved
[TS 38.214, clause 5.1.3.2]
In case the higher layer parameter maxNrofCodeWordsScheduledByDCI indicates that two codeword transmission is
enabled, then a transport block is disabled by DCI format 1_1 if IMCS = 26 and if rvid = 1 for the corresponding transport
block, otherwise the transport block is enabled. If both transport blocks are enabled, transport block 1 and 2 are mapped
to codeword 0 and 1 respectively. If only one transport block is enabled, then the enabled transport block is always
mapped to the first codeword.
For the PDSCH assigned by a PDCCH with DCI format 1_0 or format 1_1 with CRC scrambled by C-RNTI, new-
RNTI, TC-RNTI, CS-RNTI, or SI-RNTI, if Table 5.1.3.1-2 is used and 0 ≤ I MCS ≤ 27 , or a table other than Table
5.1.3.1-2 is used and 0 ≤ I MCS ≤ 28 , the UE shall, except if the transport block is disabled in DCI format 1_1, first
determine the TBS as specified below:
1) The UE shall first determine the number of REs (NRE) within the slot.
'
- A UE first determines the number of REs allocated for PDSCH within a PRB ( N RE ) by
'
N RE = N scRB ⋅ N symb
sh
− N DMRS
PRB
− N oh
PRB RB
, where N sc = 12 is the number of subcarriers in a physical resource
sh PRB
block, N symb is the number of symbols of the PDSCH allocation within the slot, N DMRS is the number of
REs for DM-RS per PRB in the scheduled duration including the overhead of the DM-RS CDM groups
PRB
without data, as indicated by DCI format 1_1 or as described for format 1_0 in Subclause 5.1.6.2, and N oh
is the overhead configured by higher layer parameter xOverhead in PDSCH-ServingCellConfig. If the
PRB
xOverhead in PDSCH-ServingCellconfig is not configured (a value from 0, 6, 12, or 18), the Noh is set to
ETSI
PRB
0. If the PDSCH is scheduled by PDCCH with a CRC scrambled by SI-RNTI, RA-RNTI or P-RNTI, Noh
is assumed to be 0.
- A UE determines the total number of REs allocated for PDSCH ( N RE ) by NRE = min 156, NRE ⋅ nPRB ,( '
)
where nPRB is the total number of allocated PRBs for the UE.
2) Intermediate number of information bits (Ninfo) is obtained by N inf o = N RE · R·Qm ·υ .
If N inf o ≤ 3824
Use step 3 as the next step of the TBS determination
else
end if
3) When N inf o ≤ 3824 , TBS is determined as follows
  N inf o  
o = max
'
- quantized intermediate number of information bits N inf 
24,2 n · n 
, where
  2 
n = max(3, log2 (N inf o ) − 6) .
'
- use Table 5.1.3.2-2 find the closest TBS that is not less than N inf o.
Table 5.1.3.2-2: TBS for N inf o ≤ 3824
Index TBS Index TBS Index TBS Index TBS

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
ETSI
4) When N inf o > 3824 , TBS is determined as follows.
  Ninf o − 24  
- quantized intermediate number of information bits Ninf' o = max  3840, 2n × round    , where
  2 
n
n = log 2 (N inf o − 24) − 5 and ties in the round function are broken towards the next largest integer.
- if R ≤ 1 / 4
N' + 24  N'
inf o + 24

TBS = 8· C·  inf o
 − 24 , where C =  


8· C 
 
3816 
else
o > 8424
'
if N inf
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
end if
Same Pre-test conditions as in clause 7.1.1.0 except set the NR Cell bandwidth and applicable BWP to maximum for
the NR Band under test as specified in Table 5.3.5-1 in TS 38.101-1 [16] / TS 38.101-2 [17] (to enable testing of nPRB
up to maximum value) and Short_DCI condition is applied in NR Serving cell configuration.
Test frequency NRf1 is as specified in TS 38.508-1 [4] clause 4.3.1 using the common highest mandatory UL and DL
channel bandwidth and using the default subcarrier spacing specified in TS 38.508-1 [4] clause 6.2.3.1.
Table 7.1.1.4.1.1.3.2-1: Maximum TBS for different UE categories

UE Category Maximum number of bits of a UL-SCH transport
block received within a TTI
TS 38.306 [23] clause 4.1.2 require UE without ue-CategoryDL and ue-
CategoryUL, to support Max TBS achievable based on max bandwidth of
the Band under test.
ETSI
Table 7.1.1.4.1.1.3.2-2: Number of downlink PDCP SDUs and PDCP SDU size used as test data
TBS Number of PDCP SDU size
[bits] PDCP SDUs [bits]
(Note 1)
136 ≤ TBS ≤12128 note 2 1 8*FLOOR((TBS – 128)/8)
12129 ≤ TBS ≤24200 2 8*FLOOR((TBS – 200)/16)
24201 ≤ TBS ≤ 36272 3 8*FLOOR((TBS – 272)/24)
36273 ≤ TBS ≤48344 4 8*FLOOR((TBS – 344)/32)
48345≤ TBS ≤60416 5 8*FLOOR((TBS – 416)/40)
60417 ≤ TBS ≤ 72488 6 8*FLOOR((TBS –488)/48)
72489 ≤ TBS ≤84560 7 8*FLOOR((TBS – 560)/56)
84561 ≤ TBS ≤96632 8 8*FLOOR((TBS –632)/64)
96633< TBS ≤108704 9 8*FLOOR((TBS –704)/72)
10705 ≤ TBS ≤120776 10 8*FLOOR((TBS – 776)/80)
120777≤ TBS ≤132848 11 8*FLOOR((TBS –848)/88)
132849 ≤ TBS ≤ 144920 12 8*FLOOR((TBS – 920)/96)
144921 ≤ TBS ≤ 156992 13 8*FLOOR((TBS – 992)/104)
156993 ≤ TBS ≤ 169064 14 8*FLOOR((TBS – 1064)/112)
169065 ≤ TBS ≤ 181136 15 8*FLOOR((TBS – 1136)/120)
181137 ≤ TBS ≤ 193208 16 8*FLOOR((TBS – 1208)/128)
193209 ≤ TBS ≤ 205280 17 8*FLOOR((TBS – 1280)/136)
205281 ≤ TBS ≤ 217352 18 8*FLOOR((TBS – 1352)/144)
217353 ≤ TBS ≤ 229424 19 8*FLOOR((TBS – 1424)/152)
TBS> 229424 20 8*FLOOR((TBS –1496)/160)
Note 1: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS
24.301 [21] clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is
PDCP SDU size = (TBS – N*PDCP header size – N*AMD PDU header size - N*MAC header size – Size
of Timing Advance – RLC Status PDU size- MAC header for RLC Status PDU) / N, where
PDCP header size is 24 bits for the RLC AM and 18-bit SN case;
AMD PDU header size is 24 bits with 18 bit SN;
MAC header size for AMD PDU = 16 or 24 bits depending on L=8 or 16 bits. Worst case 24 is taken.
Size of Timing Advance MAC CE with header is 16 bits (if no Timing Advance and/or RLC status needs to
be sent, padding will occur instead).
RLC Status PDU size = 24 bits with 1 ACK_SN, With a MAC header of 16 bits.
This gives:
PDCP SDU size = 8*FLOOR((TBS – N*24- N*24 – N*24 -56 )/(8*N)) bits.
Note 2: According to the final PDCP SDU size formula in Note 1, the smallest TBS that can be tested is 136 bits.
Table 7.1.1.4.1.1.3.2-3: Specific Parameters
Parameter Value Comment

number of layers (ʋ) 1
mcs-Table qam64
xoh-PDSCH Not Present Results in value 0(xoh0)
ETSI

U-S Message
- EXCEPTION: Steps 1 to 5 are - - - -
repeated for allowed values of
DL,BWP
N PRB 1 to N RB in BWP, time
domain resource as per table
7.1.1.4.1.0-1 and I MCS from 0 to
28.
NOTE: Skip the execution of steps
for which the TBS size results in
coding rate exceeding 0.95.
1 The SS calculates or looks up - - - -
TBS in TS 38.214 [15] based on
the value of S, L, I MCS and nPRB.
performed if TBS 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.1.4.1.1.3.2-1 and larger than
or equal to 132 bits as specified in
Table 7.1.1.4.1.1.3.2-2
2 The SS creates one or more - - - -
PDCP SDUs, depending on TBS,
in accordance with Table
7.1.1.4.1.1.3.2-2.
3 The SS transmits the PDCP SDUs <-- MAC PDU (NxPDCP - -
concatenated into a MAC PDU SDUs)
and indicates on PDCCH DCI DCI: (DCI Format 1_0, S,
Format 1_0 and values of S, L, I MCS and nPRB.)
L, I MCS and nPRB.
4 At the reception of scheduling <-- (UL Grant) - -
request the SS transmits UL Grant
for transmitting loop back PDCP
SDUs.
5 CHECK: Does UE return the --> (NxPDCP SDUs) 1 P
same number of PDCP SDUs with
same content as transmitted by
the SS in step 3?
None.
7.1.1.4.1.2 Void
Codewords enabled
(1)
with { UE in RRC_CONNECTED state and maxNrofCodeWordsScheduledByDCI set to 'n2' }
ensure that {
when { UE on PDCCH receives DCI format 1_1 indicating resource allocation type 0 a resource block
assignment correspondent to physical resource blocks , Time domain resource assignment and a
modulation and coding }
ETSI
}
(2)
with { UE in RRC_CONNECTED state and maxNrofCodeWordsScheduledByDCI set to 'n2' }
ensure that {
}
38.214 clause 5.1.2.1, 5.1.2.2.1, 5.1.2.2.2, 5.1.3, 5.1.3.1 and 5.1.3.2. Unless otherwise stated these are Rel-15
requirements.
[TS 38.212, clause 7.3.1.2.2]
DCI format 1_1 is used for the scheduling of PDSCH in one cell.
RNTI or new-RNTI:
- Carrier indicator – 0 or 3 bits as defined in Subclause 10.1 of [5, TS38.213].
- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of DL BWPs nBWP,RRC configured by
higher layers, excluding the initial DL bandwidth part. The bit width for this field is determined as
log 2 (nBWP )  bits, where
- nBWP = nBWP,RRC + 1 if nBWP,RRC ≤ 3 , in which case the bandwidth part indicator is equivalent to the higher
layer parameter BWP-Id;
- otherwise nBWP = nBWP, RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
If a UE does not support active BWP change via DCI, the UE ignores this bit field.
DL,BWP
- Frequency domain resource assignment – number of bits determined by the following, where N RB is the size
of the active DL bandwidth part:
- N RBG bits if only resource allocation type 0 is configured, where N RBG is defined in Subclause 5.1.2.2.1 of
[6, TS38.214],
- log 2 ( N RBDL,BWP ( N RBDL,BWP + 1) / 2) bits if only resource allocation type 1 is configured, or
- (
max log 2 ( N RB
DL, BWP DL, BWP
( N RB )
+ 1) / 2 )  , N RBG + 1 bits if both resource allocation type 0 and 1 are
configured.
- If both resource allocation type 0 and 1 are configured, the MSB bit is used to indicate resource allocation
type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit
value of 1 indicates resource allocation type 1.
- For resource allocation type 0, the N RBG LSBs provide the resource allocation as defined in Subclause
5.1.2.2.1 of [6, TS38.214].
ETSI
- For resource allocation type 1, the log 2 ( N RB

DL,BWP DL,BWP
( N RB + 1) / 2) LSBs provide the resource allocation as
defined in Subclause 5.1.2.2.2 of [6, TS38.214]
If “Bandwidth part indicator” field indicates a bandwidth part other than the active bandwidth part and if both
resource allocation type 0 and 1 are configured for the indicated bandwidth part, the UE assumes resource
allocation type 0 for the indicated bandwidth part if the bit width of the “Frequency domain resource
assignment” field of the active bandwidth part is smaller than the bit width of the “Frequency domain
resource assignment” field of the indicated bandwidth part.
- Time domain resource assignment – 0, 1, 2, 3, or 4 bits as defined in Subclause 5.1.2.1 of [6, TS38.214]. The
bit width for this field is determined as log 2 ( I )  bits, where I is the number of entries in the higher layer
parameter pusch-AllocationList.
- VRB-to-PRB mapping – 0 or 1 bit
- 0 bit if only resource allocation type 0 is configured;
- 1 bit according to Table 7.3.1.1.2-33 otherwise, only applicable to resource allocation type 1, as defined in
Subclause 7.3.1.6 of [4, TS38.211].
- PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingType is not configured or is set to
‘static’, or 1 bit if the higher layer parameter prb-BundlingType is set to ‘dynamic’, according to Subclause
5.1.2.3 of [6, TS38.214].
- Rate matching indicator – 0, 1, or 2 bits according to higher layer parameter rateMatchPattern.
- ZP CSI-RS trigger – 0, 1, or 2 bits as defined in Subclause 5.1.4.2 of [6, TS38.214]. The bit width for this field is
determined as log 2 ( n ZP + 1)  bits, where nZP is the number of ZP CSI-RS resource sets in the higher layer
parameterzp-CSI-RS-Resource.
For transport block 1:
- Modulation and coding scheme – 5 bits as defined in Subclause 5.1.3.1 of [6, TS38.214]
For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2
If “Bandwidth part indicator” field indicates a bandwidth part other than the active bandwidth part and the value of
maxNrofCodeWordsScheduledByDCI for the indicated bandwidth part equals 2 and the value of
maxNrofCodeWordsScheduledByDCI for the active bandwidth part equals 1, the UE assumes zeros are padded
when interpreting the “Modulation and coding scheme”, “New data indicator”, and “Redundancy version” fields
of transport block 2 according to Subclause 12 of [5, TS38.213], and the UE ignores the “Modulation and coding
scheme”, “New data indicator”, and “Redundancy version” fields of transport block 2 for the indicated
bandwidth part.
- Downlink assignment index – number of bits as defined in the following
- 4 bits if more than one serving cell are configured in the DL and the higher layer parameter pdsch-HARQ-
ACK-Codebook=dynamic, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI;
- 2 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-
Codebook=dynamic, where the 2 bits are the counter DAI;
- 0 bits otherwise.
ETSI
- PDSCH-to-HARQ_feedback timing indicator – 3 0, 1, 2, or bits as defined in Subclause 9.2.3 of [5, TS38.213].

The bit width for this field is determined as log 2 ( I ) bits, where I is the number of entries in the higher layer
parameter dl-DataToUL-ACK.
- Antenna port(s) – 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4, where the number of CDM groups
without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports
{ }
p0,..., pυ −1 shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4.
If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-

MappingTypeB, the bit width of this field equals max { xA , xB } , where x A is the “Antenna ports” bit width
derived according to dmrs-DownlinkForPDSCH-MappingTypeA and x B is the “Antenna ports” bit width
derived according to dmrs-DownlinkForPDSCH-MappingTypeB. A number of xA − xB zeros are padded in the
MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of x A and x B .
- Transmission configuration indication – 0 bit if higher layer parameter tci-PresentInDCI is not enabled;
otherwise 3 bits as defined in Subclause 5.1.5 of [6, TS38.214].
If “Bandwidth part indicator” field indicates a bandwidth part other than the active bandwidth part and the
“Transmission configuration indication” field is not present in the DCI format 1_1, the UE assumes tci-
PresentInDCI is not enabled for the indicated bandwidth part.
- SRS request – 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with SUL in the cell; 3 bits for UEs
configured SUL in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and
the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-
RS according to Subclause 6.1.1.2 of [6, TS 38.214].
- CBG transmission information (CBGTI) – 0, 2, 4, 6, or 8 bits as defined in Subclause 5.1.7 of [6, TS38.214],
determined by the higher layer parameters maxCodeBlockGroupsPerTransportBlock and Number-MCS-HARQ-
DL-DCI for the PDSCH.
- CBG flushing out information (CBGFI) – 0 or 1 bit as defined in Subclause 5.1.7 of [6, TS38.214], determined
by higher layer parameter codeBlockGroupFlushIndicator.
- DMRS sequence initialization – 1 bit if both scramblingID0 and scramblingID1 are configured in DMRS-
DownlinkConfig for nSCID selection defined in Subclause 7.4.1.1.1 of [4, TS38.211]; 0 bit otherwise.
[TS 38.214, clause 5.1.2.1]
 2 μ PDSCH 

if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
ETSI
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and

Type A {0,1,2,3} {3,…,14} {3,…,14} {0,1,2,3} {3,…,12} {3,…,12}
(Note 1) (Note 1)
Type B {0,…,12} {2,4,7} {2,…,14} {0,…,10} {2,4,6} {2,…,12}
Note 1: S = 3 is applicable only if dmrs-TypeA-Posiition = 3
[TS 38.214, clause 5.1.2.2.1]
In downlink resource allocation of type 0, the 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 virtual
resource blocks defined by higher layer parameter rbg-Size configured for PDSCH and the size of the carrier bandwidth
part as defined in Table 5.1.2.2.1-1.
Table 5.1.2.2.1-1: Nominal RBG size P

Bandwidth Part Size Configuration 1 Configuration 2
1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
size
The total number of RBGs ( N RBG ) for a downlink carrier bandwidth part i of size N BWP, i PRBs is given by
(
N RBG = N BWP
size
( )) 
,i + N BWP ,i mod P / P , where
start
- the size of the first RBG is RBG0size = P − N BWP

start
,i mod P ,
- size
the size of last RBG is RBGlast = N BWP(
start size
) (start size
)
,i + N BWP ,i mod P if N BWP ,i + N BWP ,i mod P > 0 and P otherwise,
- the size of all other RBGs is P.
The bitmap is of size N RBG 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 starting at the lowest frequency of the carrier bandwidth part. The
order of RBG bitmap is such that RBG 0 to RBG N RBG − 1 are mapped from MSB to LSB. 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.
[TS 38.214, clause 5.1.2.2.2]
of contiguously allocated localized or distributed virtual resource blocks within the active carrier bandwidth part of size
size
N BWP PRBs except for the case when DCI format 1_0 is decoded in the common search space in CORESET 0 in
size
which case the initial bandwidth part of size N BWP shall be used.
virtual resource block ( RBstart ) and a length in terms of contiguously allocated resource blocks LRBs . The resource
ETSI

size
/2  then
RIV = N BWP
size
else
RIV = N BWP
size size
size
− 1 − RBstart )

size
[TS 38.214, clause 5.1.3]
- read redundancy version field (rv) in the DCI to determine the redundancy version.
and second
[TS 38.214, clause 5.1.3.1]
search space
ETSI
else
End

IMCS Qm efficiency
0 2 120 0.2344
1 2 157 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 438 2.5664
18 6 466 2.7305
19 6 517 3.0293
20 6 567 3.3223
21 6 616 3.6094
22 6 666 3.9023
23 6 719 4.2129
24 6 772 4.5234
25 6 822 4.8164
26 6 873 5.1152
27 6 910 5.3320
28 6 948 5.5547
29 2 reserved
30 4 reserved
31 6 reserved
[TS 38.214, clause 5.1.3.2]
ETSI
'
'
sh
− N DMRS
PRB
− N oh
PRB RB
sh PRB
PRB
PRB
PRB
is assumed to be 0.
- (
A UE determines the total number of REs allocated for PDSCH ( N RE ) by NRE = min 156, NRE ⋅ nPRB ,
'
)
If N inf o ≤ 3824
else
end if
  N inf o  
o = max
'
24,2 n · n 
, where
  2 
n = max(3, log 2 (N inf o ) − 6) .
'
ETSI

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
- if R ≤ 1 / 4
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  3816 
else
o > 8424
'
if N inf
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
ETSI
end if
up to maximum value).

UE Category Maximum number of bits of a UL-SCH transport block received
within a TTI
TS 38.306 [23] clause 4.1.2 require UE without ue-CategoryDL and ue-CategoryUL, to
support Max TBS achievable based on max bandwidth of the Band under test.
ETSI
(Note 1)
12185≤ TBS ≤24256 2 8*FLOOR((TBS – 256)/16)
24257≤ TBS ≤ 36328 3 8*FLOOR((TBS – 328)/24)
36329 ≤ TBS ≤48400 4 8*FLOOR((TBS –400)/32)
48401≤ TBS ≤60472 5 8*FLOOR((TBS – 472)/40)
60473 ≤ TBS ≤ 72544 6 8*FLOOR((TBS – 544)/48)
72545≤ TBS ≤84616 7 8*FLOOR((TBS – 616)/56)
84617 ≤ TBS ≤96688 8 8*FLOOR((TBS – 688)/64)
96689< TBS ≤108760 9 8*FLOOR((TBS – 760)/72)
108761 ≤ TBS ≤120832 10 8*FLOOR((TBS –832)/80)
120833≤ TBS ≤132904 11 8*FLOOR((TBS – 904)/88)
132905 ≤ TBS ≤ 144976 12 8*FLOOR((TBS – 976)/96)
TBS> 144976 13 8*FLOOR((TBS – 1048)/104)
24.301 [21] clause 9.9.4.12).
of Timing Advance – RLC Status PDU size- MAC header for RLC Status PDU – 32 bit Additional RLC
header with SO if one RLC SDU gets split in 2 TBS and 24 bit MAC header for this additional PDU) / N,
where
IF RLC SDU does not get split the 32 bits additional padding gets added instead
This gives:
PDCP SDU size = 8*FLOOR((TBS – N*24- N*24– N*24 -112 )/(8*N)) bits.
ETSI
Table 7.1.1.4.1.3.3.2-2A: Bandwidth part Dependent Parameters for Resource allocation 0 with start of
BWP assumed as 0
DL,BWP
N RB Nominal RBG Size N PRB
= size P of Allowed Values
size
N BWP, i (Configuration1) last
RBG
11 2 1 All 1…11
18 2 2 2,4,6,8,10,12,16,18
24 2 2 2,4,6,8,10,12,16,18,20,22,24
25 2 1 All 1…25
31 2 1 All 1…31
32 2 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32
38 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38
51 4 3 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 4 4 4,8,12,16,20,24,28,32,36,40,44,48,52
65 4 1 1,4,5,8,9,12,13,16,17,20,21,24,25,28,29,32,33,36,37,40,41,44,45,48,49,
52,53,56,57,60,61,64,65
66 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,
54,56,58,60,62,64,66
79 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79
106 8 2 2,8,10,16,18,24,26,32,34,40,42,48,50,56,58,64,66,72,74,80,82,88,90,96,
92,104,106
107 8 3 3,8,11,16,19,24,27,32,35,40,43,48,51,56,59,64,67,72,75,80,83,88,91,96,
99,104,107
132 8 4 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,104, 108,112,116,120,124,128,132
133 8 5 5,8,13,16,21,24,29,32,37,40,45,48,53,56,61,64,69,72,77,80,85,88,93,96,
101,104, 109,112,117,120,125,128,133
135 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79,80,87,88,95,96,
103,104, 111,112,119,120,127,128,135
160 16 16 16,32,48,64,80,96,112,128,144,160
216 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152,160,
168, 176,184,192,200,208,216
217 16 9 9,16,25,32,41,48,57,64,73,80,89,96,105,112,121,128,137,144,153,160,
169,176,185,192,201,208,217
264 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,160,168,
176,184,192,200,208,216,224,232,240,248,256,264
270 16 14 14,16,30,32,46,44,62,64,78,80,94,96,110,112, 126,128,142,144,158,
160,174, 176,190,192, 206,208,222,224,238,240, 254,256,270
273 16 1 1,16,17,32,33,48,49,64,65,80,81,96,97,112,113,128,129,144,145,160,
161,176,171, 192,193, 208,209, 224,225,240,241,256,257,272,273
Table 7.1.1.4.1.3.3.2-3: Specific Parameter

Parameter Value Comments Condition
mcs-Table qam64
resourceAllocation dynamicSwitch pc_dynamicSwitchRA_Type0_1_PDSCH
resourceAllocationType0 NOT
pc_dynamicSwitchRA_Type0_1_PDSCH
AND Steps 1-5
AND Steps 6-10
maxNrofCodeWordsScheduledByDCI n2 both
codewords
enabled
NstartBWP 0
ETSI

U-S Message
- EXCEPTION: Steps 1 to 5 are repeated for - - - -
allowed values of N PRB as per table
7.1.1.4.1.3.3.2-2A in BWP, time domain
resource as per table 7.1.1.4.1.0-1 and I MCS
from 0 to 28.
NOTE: Skip the execution of steps for which
the TBS size results in coding rate exceeding
0.95.
1 SS calculates or looks up TBS in TS 38.214 - - - -
[15] based on the value of S, L, I MCS and
nPRB.
The SS uses the same I MCS and TBS for
both transport blocks:
I MCS#1 = I MCS#2 = I MCS

TBS 1= TBS 2= TBS
- EXCEPTION: Steps 2 to 5 are performed if - - - -
TBS1 + TBS2 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.1.4.1.3.3.2-1 and
larger than or equal to 192 bits as specified
in Table 7.1.1.4.1.3.3.2-2.
2 SS creates one or more PDCP SDUs for - - - -
transport block 1 and 2 depending on TBS1,
and TBS2 in accordance with Table
7.1.1.4.1.3.3.2-2.
3 SS transmits the PDCP SDUs concatenated <-- Transport block 1: - -
into a MAC PDU and indicates on PDCCH MAC PDU
DCI Format 1_1 resource allocation 0 and Transport block 2:
values of S, L, I MCS#1 , I MCS#2 and nPRB. MAC PDU
DCI: (DCI Format 1_1, S,
L, I MCS#1 , I MCS#2 and nPRB.)
4 At the reception of scheduling request the <-- (UL Grant) - -
SS transmits UL Grant for transmitting loop
back PDCP SDUs.
5 CHECK: Does UE return the same number --> (NxPDCP SDUs) 1 P
of PDCP SDUs with same content as
transmitted by the SS in step 3?
- EXCEPTION : Steps 5Aa1 to 5Aa2 are - - - -
executed if NOT
5A The SS transmits a NR RRCReconfiguration <-- RRCReconfiguration - -
a1 message including PDSCH-Config with IE
resourceAllocation set to
resourceAllocationType1 (Note 1)
5A The UE transmit a NR --> RRCReconfigurationComplete - -
a2 RRCReconfigurationComplete message.
(Note 2)
DL,BWP
allowed values of N PRB 1 to N RB in
BWP, time domain resource as per table
7.1.1.4.1.0-1 and I MCS from 0 to 28.
ETSI

nPRB.

TBS 1= TBS 2= TBS
in Table 7.1.1.4.1.3.3.2-2.
7.1.1.4.1.3.3.2-2.
8 SS transmits the PDCP SDUs concatenated <-- Transport block 1: - -
into a MAC PDU and indicates on PDCCH MAC PDU
DCI Format 1_1 resource allocation 1 and Transport block 2:
values of S, L, I MCS#1 , I MCS#2 and nPRB. MAC PDU
DCI: (DCI Format 1_1, S,
L, I MCS#1 , I MCS#2 and nPRB.)
back PDCP SDUs.
None.
Codewords enabled / 256QAM
(1)
with { UE in RRC_CONNECTED state, maxNrofCodeWordsScheduledByDCI set to 'n2' and mcs-Table is set
as ‘qam256‘ }
ensure that {
}
(2)
with { UE in RRC_CONNECTED state, maxNrofCodeWordsScheduledByDCI set to 'n2' and mcs-Table is set
as ‘qam256‘ }
ensure that {
ETSI
}
38.214 clauses 5.1.2.1, 5.1.2.2.1, 5.1.2.2.2, 5.1.3, 5.1.3.1 and 5.1.3.2. Unless otherwise stated these are Rel-15
requirements.
[TS 38.212, clause 7.3.1.2.2]
RNTI or new-RNTI:
- Carrier indicator – 0 or 3 bits as defined in Subclause 10.1 of [5, TS38.213].
higher layers, excluding the initial DL bandwidth part. The bit width for this field is determined as
log 2 (nBWP )  bits, where
- otherwise nBWP = nBWP, RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
DL,BWP
of the active DL bandwidth part:
[6, TS38.214],
- log 2 ( N RBDL,BWP ( N RBDL,BWP + 1) / 2) bits if only resource allocation type 1 is configured, or
- (
max log 2 ( N RB
DL, BWP DL, BWP
( N RB )
configured.
5.1.2.2.1 of [6, TS38.214].
- For resource allocation type 1, the log 2 ( N RB

DL,BWP DL,BWP
defined in Subclause 5.1.2.2.2 of [6, TS38.214]
If “Bandwidth part indicator” field indicates a bandwidth part other than the active bandwidth part and if both
allocation type 0 for the indicated bandwidth part if the bit width of the “Frequency domain resource
ETSI
assignment” field of the active bandwidth part is smaller than the bit width of the “Frequency domain resource
assignment” field of the indicated bandwidth part.
- Time domain resource assignment – 0, 1, 2, 3, or 4 bits as defined in Subclause 5.1.2.1 of [6, TS38.214]. The bit
width for this field is determined as log 2 ( I )  bits, where I is the number of entries in the higher layer parameter
pusch-AllocationList.
- VRB-to-PRB mapping – 0 or 1 bit
- 0 bit if only resource allocation type 0 is configured;
Subclause 7.3.1.6 of [4, TS38.211].
- PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingType is not configured or is set to
‘static’, or 1 bit if the higher layer parameter prb-BundlingType is set to ‘dynamic’, according to Subclause
5.1.2.3 of [6, TS38.214].
- Rate matching indicator – 0, 1, or 2 bits according to higher layer parameter rateMatchPattern.
- ZP CSI-RS trigger – 0, 1, or 2 bits as defined in Subclause 5.1.4.2 of [6, TS38.214]. The bit width for this field is
determined as log 2 ( n ZP + 1)  bits, where nZP is the number of ZP CSI-RS resource sets in the higher layer
parameterzp-CSI-RS-Resource .
For transport block 1:
For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2
If “Bandwidth part indicator” field indicates a bandwidth part other than the active bandwidth part and the value of
maxNrofCodeWordsScheduledByDCI for the indicated bandwidth part equals 2 and the value of
maxNrofCodeWordsScheduledByDCI for the active bandwidth part equals 1, the UE assumes zeros are padded
when interpreting the “Modulation and coding scheme”, “New data indicator”, and “Redundancy version” fields
of transport block 2 according to Subclause 12 of [5, TS38.213], and the UE ignores the “Modulation and coding
scheme”, “New data indicator”, and “Redundancy version” fields of transport block 2 for the indicated
bandwidth part.
- Downlink assignment index – number of bits as defined in the following
- 4 bits if more than one serving cell are configured in the DL and the higher layer parameter pdsch-HARQ-
ACK-Codebook=dynamic, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI;
- 2 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-
Codebook=dynamic, where the 2 bits are the counter DAI;
- 0 bits otherwise.
ETSI
- PDSCH-to-HARQ_feedback timing indicator – 0, 1, 2, or 3 bits as defined in Subclause 9.2.3 of [5, TS38.213].

The bit width for this field is determined as log 2 ( I ) bits, where I is the number of entries in the higher layer
parameter dl-DataToUL-ACK.
- Antenna port(s) – 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4, where the number of CDM groups
without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports
{ }
p0,..., pυ −1 shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4.
If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-

derived according to dmrs-DownlinkForPDSCH-MappingTypeA and x B is the “Antenna ports” bit width
derived according to dmrs-DownlinkForPDSCH-MappingTypeB. A number of xA − xB zeros are padded in the
MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of x A and x B .
- Transmission configuration indication – 0 bit if higher layer parameter tci-PresentInDCI is not enabled;
otherwise 3 bits as defined in Subclause 5.1.5 of [6, TS38.214].
“Transmission configuration indication” field is not present in the DCI format 1_1, the UE assumes tci-
PresentInDCI is not enabled for the indicated bandwidth part.
- CBG transmission information (CBGTI) – 0, 2, 4, 6, or 8 bits as defined in Subclause 5.1.7 of [6, TS38.214],
determined by the higher layer parameters maxCodeBlockGroupsPerTransportBlock and Number-MCS-HARQ-
DL-DCI for the PDSCH.
- CBG flushing out information (CBGFI) – 0 or 1 bit as defined in Subclause 5.1.7 of [6, TS38.214], determined
by higher layer parameter codeBlockGroupFlushIndicator.
- DMRS sequence initialization – 1 bit if both scramblingID0 and scramblingID1 are configured in DMRS-
DownlinkConfig for nSCID selection defined in Subclause 7.4.1.1.1 of [4, TS38.211]; 0 bit otherwise.
[TS 38.214, clause 5.1.2.1]
 2 μ PDSCH 

if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
ETSI
where 0 < L ≤ 14 − S , and

Type A {0,1,2,3 {3,…,14} {3,…,14} {0,1,2,3 {3,…,12} {3,…,12}
(Note 1)} (Note 1)}
Type B {0,…,12} {2,4,7} {2,…,14} {0,…,10} {2,4,6} {2,…,12}
Note 1: S = 3 is applicable only if dmrs-TypeA-Posiition = 3
[TS 38.214, clause 5.1.2.2.1]
resource blocks defined by higher layer parameter rbg-Size configured for PDSCH and the size of the carrier bandwidth

1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
size
The total number of RBGs ( N RBG ) for a downlink carrier bandwidth part i of size N BWP, i PRBs is given by
(
N RBG = N BWP
size
( )) 
,i + N BWP ,i mod P / P , where
start
- the size of the first RBG is RBG 0size = P − N BWP

start
,i mod P ,
- size
the size of last RBG is RBGlast (
= N BWP
start size
) ( start size
)
,i + N BWP ,i mod P if N BWP ,i + N BWP ,i mod P > 0 and P otherwise,
- the size of all other RBGs is P.
indexed in the order of increasing frequency and starting at the lowest frequency of the carrier bandwidth part. The
order of RBG bitmap is such that RBG 0 to RBG N RBG − 1 are mapped from MSB to LSB. 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.
[TS 38.214, clause 5.1.2.2.2]
of contiguously allocated localized or distributed virtual resource blocks within the active carrier bandwidth part of size
size
N BWP PRBs except for the case when DCI format 1_0 is decoded in the common search space in CORESET 0 in
size
which case the initial bandwidth part of size N BWP shall be used.

size
/2  then
ETSI
RIV = N BWP
size
else
RIV = N BWP
size size
size
− 1 − RBstart )

size
[TS 38.214, clause 5.1.3]
and second
[TS 38.214, clause 5.1.3.1]
search space
else
ETSI
End

IMCS Qm efficiency
0 2 120 0.2344
1 2 193 0.3770
2 2 308 0.6016
3 2 449 0.8770
4 2 602 1.1758
5 4 378 1.4766
6 4 434 1.6953
7 4 490 1.9141
8 4 553 2.1602
9 4 616 2.4063
10 4 658 2.5703
11 6 466 2.7305
12 6 517 3.0293
13 6 567 3.3223
14 6 616 3.6094
15 6 666 3.9023
16 6 719 4.2129
17 6 772 4.5234
18 6 822 4.8164
19 6 873 5.1152
20 8 682.5 5.3320
21 8 711 5.5547
22 8 754 5.8906
23 8 797 6.2266
24 8 841 6.5703
25 8 885 6.9141
26 8 916.5 7.1602
27 8 948 7.4063
28 2 reserved
29 4 reserved
30 6 reserved
31 8 reserved
[TS 38.214, clause 5.1.3.2]
ETSI
'
'
sh
− N DMRS
PRB
− N oh
PRB RB
sh PRB
PRB
PRB
PRB
is assumed to be 0.
- (
A UE determines the total number of REs allocated for PDSCH ( N RE ) by NRE = min 156, NRE ⋅ nPRB ,
'
)
If N inf o ≤ 3824
else
end if
  N inf o  
o = max
'
24,2 n · n 
, where
  2 
n = max(3, log2 (N inf o ) − 6) .
'
ETSI

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
- if R ≤ 1 / 4
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  3816 
else
o > 8424
'
if N inf
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
ETSI
end if
Test frequency NRf1 is as specified in TS 38.508-1[4] clause 4.3.1 using the common highest UL and DL channel
bandwidth and using the default subcarrier spacing specified in TS 38.508-1[4] clause 6.2.3.1.

CategoryUL, to support Max TBS achievable based on max bandwidth of the
Band under test.
ETSI
(Note 1)
12185≤ TBS ≤24256 2 8*FLOOR((TBS – 256)/16)
24257≤ TBS ≤ 36328 3 8*FLOOR((TBS – 328)/24)
36329 ≤ TBS ≤48400 4 8*FLOOR((TBS –400)/32)
48401≤ TBS ≤60472 5 8*FLOOR((TBS – 472)/40)
60473 ≤ TBS ≤ 72544 6 8*FLOOR((TBS – 544)/48)
72545≤ TBS ≤84616 7 8*FLOOR((TBS – 616)/56)
84617 ≤ TBS ≤96688 8 8*FLOOR((TBS – 688)/64)
96689< TBS ≤108760 9 8*FLOOR((TBS – 760)/72)
108761 ≤ TBS ≤120832 10 8*FLOOR((TBS –832)/80)
120833≤ TBS ≤132904 11 8*FLOOR((TBS – 904)/88)
132905 ≤ TBS ≤ 144976 12 8*FLOOR((TBS – 976)/96)
144785 ≤ TBS ≤ 157048 13 8*FLOOR((TBS – 1048)/104)
157049 ≤ TBS ≤ 169120 14 8*FLOOR((TBS – 1120)/112)
169121< TBS ≤ 181192 15 8*FLOOR((TBS – 1192)/120)
181193 ≤ TBS ≤193264 16 8*FLOOR((TBS – 1264)/128)
193337 ≤ TBS ≤ 205336 17 8*FLOOR((TBS – 1336)/136)
205409 ≤ TBS ≤ 217408 18 8*FLOOR((TBS – 1408)/144)
TBS> 217408 19 8*FLOOR((TBS – 1480)/152)
24.301 [21] clause 9.9.4.12).
of Timing Advance – RLC Status PDU size- MAC header for RLC Status PDU – 32 bit Additional RLC
header with SO if one RLC SDU gets split in 2 TBS and 24 bit MAC header for this additional PDU) / N,
where
IF RLC SDU does not get split the 32 bits additional padding gets added instead
This gives:
PDCP SDU size = 8*FLOOR((TBS – N*24- N*24– N*24 -112 )/(8*N)) bits.
ETSI
BWP assumed as 0
DL,BWP
size
RBG
11 2 1 All 1…11
18 2 2 2,4,6,8,10,12,16,18
24 2 2 2,4,6,8,10,12,16,18,20,22,24
25 2 1 All 1…25
31 2 1 All 1…31
32 2 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32
38 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38
51 4 3 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 4 4 4,8,12,16,20,24,28,32,36,40,44,48,52
65 4 1 1,4,5,8,9,12,13,16,17,20,21,24,25,28,29,32,33,36,37,40,41,44,45,48,49,
52,53,56,57,60,61,64,65
66 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,
54,56,58,60,62,64,66
79 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79
106 8 2 2,8,10,16,18,24,26,32,34,40,42,48,50,56,58,64,66,72,74,80,82,88,90,96,
92,104,106
107 8 3 3,8,11,16,19,24,27,32,35,40,43,48,51,56,59,64,67,72,75,80,83,88,91,96,
99,104,107
132 8 4 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,104, 108,112,116,120,124,128,132
133 8 5 5,8,13,16,21,24,29,32,37,40,45,48,53,56,61,64,69,72,77,80,85,88,93,96,
101,104, 109,112,117,120,125,128,133
135 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79,80,87,88,95,96,
103,104, 111,112,119,120,127,128,135
160 16 16 16,32,48,64,80,96,112,128,144,160
216 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152,160,168,
176,184,192,200,208,216
217 16 9 9,16,25,32,41,48,57,64,73,80,89,96,105,112,121,128,137,144,153,160,169,
176,185,192,201,208,217
264 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,160,168,
176,184,192,200,208,216,224,232,240,248,256,264
270 16 14 14,16,30,32,46,44,62,64,78,80,94,96,110,112, 126,128,142,144,158,160,
174, 176,190,192, 206,208,222,224,238,240, 254,256,270
273 16 1 1,16,17,32,33,48,49,64,65,80,81,96,97,112,113,128,129,144,145,160,
161,176,171, 192,193, 208,209, 224,225,240,241,256,257,272,273
ETSI

Parameter Value Comments Condition
PDSCH mappingType typeA
starting symbol S 0 0r 3 to avoid clash with
PDCCH symbols
number of consecutive symbols L 3..14-S
k0 0 or 1 (if S=0)
mcs-Table qam256
xoh-PDSCH Not present Results in value 0(xoh0)
dmrs-AdditionalPosition pos0 Results in 1 DMRS symbol
per two carrier ( )for
Duration in symbols >=3
(TS 38.211 [24], table
7.4.1.1.2-3)
resourceAllocation dynamicSwitch pc_dynamicSwitchRA_Type0_1_PDSCH
AND Steps 1-5
AND Steps 6-10
maxNrofCodeWordsScheduledByDCI n2 both codewords enabled
rbg-Size Not present configuration 1 applicable
NstartBWP 0
ETSI

U-S Message
allowed values of N PRB as per Table
resource as per table 7.1.1.4.1.0-1 and I MCS
from 0 to 27.
NOTE: Skip the execution of steps for which
the TBS size results in coding rate exceeding
0.95.
nPRB.

TBS 1= TBS 2= TBS
in Table 7.1.1.4.1.4.3.2-2.
7.1.1.4.1.4.3.2-2.
3 SS transmits the PDCP SDUs concatenated <-- Transport block 1: MAC PDU - -
into a MAC PDU and indicates on PDCCH Transport block 2: MAC PDU
DCI Format 1_1 resource allocation 0 and DCI: (DCI Format 1_1, S,
values of S, L, I MCS#1 , I MCS#2 and nPRB. I I MCS#2
L, MCS#1 , and nPRB.)
back PDCP SDUs.
executed if NOT
a1 message including PDSCH-Config with IE
(Note 2)
DL,BWP
allowed values of N PRB 1 to N inRB
BWP, time domain resource length L 3 to 14-
S and I MCS from 0 to 27.
ETSI

nPRB.

TBS 1= TBS 2= TBS
in Table 7.1.1.4.1.4.3.2-2
7.1.1.4.1.4.3.2-2.
8 SS transmits the PDCP SDUs concatenated <-- Transport block 1: MAC PDU - -
into a MAC PDU and indicates on PDCCH Transport block 2: MAC PDU
DCI Format 1_1 resource allocation 1 and DCI: (DCI Format 1_1, S,
values of S, L, I MCS#1 , I MCS#2 and nPRB. I I MCS#2
L, MCS#1 ,
and nPRB.)
back PDCP SDUs.
None.
7.1.1.4.1.5 DL-SCH transport block size selection / DCI format 1_2
(1)
ensure that {
when { UE on PDCCH receives DCI format 1_0 indicating a resource block assignment correspondent to
physical resource blocks , Time domain resource assignment and a modulation and coding }
}
38.214 clause 5.1.2.1, 5.1.2.2, 5.1.2.2.1, 5.1.2.2.2, 5.1.3, 5.1.3.1 and 5.1.3.2. Unless otherwise stated these are Rel-15
requirements.
[TS 38.212, clause 7.3.1.2.1]
DCI format 1_0 is used for the scheduling of PDSCH in one DL cell.
ETSI
RNTI or new-RNTI:

DL,BWP DL,BWP
( N RB + 1) / 2) bits
DL,BWP
- N RB is the size of the active DL bandwidth part in case DCI format 1_0 is monitored in the UE specific
DL,BWP
otherwise, NRB is the size of the initial DL bandwidth part.
If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field are
of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining fields
set as follows:
- UL/SUL indicator – 1 bit. If the value of the “Random Access Preamble index” is not all zeros and if the UE is
configured with SUL in the cell, this field indicates which UL carrier in the cell to transmit the PRACH according to
Table 7.3.1.1.1-1; otherwise, this field is reserved
- SS/PBCH index – 6 bits. If the value of the “Random Access Preamble index” is not all zeros, this field indicates the
SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this field is
reserved.
- PRACH Mask index – 4 bits. If the value of the “Random Access Preamble index” is not all zeros, this field
indicates the RACH occasion associated with the SS/PBCH indicated by “SS/PBCH index” for the PRACH
Otherwise, all remaining fields are set as follows:
- Time domain resource assignment – 4 bits as defined in Subclause 5.1.2.1 of [6, TS38.214]
- VRB-to-PRB mapping – 1 bit according to Table 7.3.1.1.2-33
- Modulation and coding scheme – 5 bits as defined in Subclause 5.1.3 of [6, TS38.214]
- Downlink assignment index – 2 bits as defined in Subclause 9.1.3 of [5, TS38.213], as counter DAI
- PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Subclause 9.2.3 of [5, TS38.213]
[TS 38.214, clause 5.1.2.1]
Clause 5.1.2.1.1. The indexed row defines the slot offset K0, the start and length indicator SLIV, or directly the start
ETSI
- The slot allocated for the PDSCH is Ks, where

   CA CA  
2 μPDSCH N slot ,offset , PDCCH N slot ,offset , PDSCH
KS = n ⋅  + K0 +  −  ⋅ 2 μPDSCH  , if UE is configured with ca-
 2 μPDCCH   2
μoffset , PDCCH
2
μoffset , PDSCH  
    
 2 μPDSCH 
SlotOffset for at least one of the scheduled and scheduling cell, and Ks =  n ⋅  + K0 , otherwise, and
 2 μPDCCH 
where n is the slot with the scheduling DCI, and K0 is based on the numerology of PDSCH, and μPDSCH and
μ PDCCH are the subcarrier spacing configurations for PDSCH and PDCCH, respectively, and
- and are the and the μ offset , respectively, which are determined by higher-
layer configured ca-SlotOffset, for the cell receiving the PDCCH respectively, and
are the and the μ offset , respectively, which are determined by higher-layer configured ca-SlotOffset for
the cell receiving the PDSCH, as defined in clause 4.5 of [4, TS 38.211].
- The reference point S0 for starting symbol S is defined as:
- if configured with referenceOfSLIVDCI-1-2, and when receiving PDSCH scheduled by DCI format 1_2 with
CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI with K0=0, and PDSCH mapping Type B, the starting
symbol S is relative to the starting symbol S0 of the PDCCH monitoring occasion where DCI format 1_2 is
detected;
- otherwise, the starting symbol S is relative to the start of the slot using S0=0.
- The number of consecutive symbols L counting from the starting symbol S allocated for the PDSCH are
determined from the start and length indicator SLIV:
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and
- the PDSCH mapping type is set to Type A or Type B as defined in Clause 7.4.1.1.2 of [4, TS 38.211].
The UE shall consider the S and L combinations defined in table 5.1.2.1-1 satisfying S0 + S + L ≤ 14 for normal cyclic
prefix and S0 + S + L ≤ 12 for extended cyclic prefix as valid PDSCH allocations:

Type A {0,1,2,3} {3,…,14} {3,…,14} {0,1,2,3} {3,…,12} {3,…,12}
(Note 1) (Note 1)
Type B {0,…,12} {2,…,13} {2,…,14} {0,…,10} {2,4,6} {2,…,12}
Note 1: S = 3 is applicable only if dmrs-TypeA-Position = 3
[38.214 clause 5.1.2.2]
Two downlink resource allocation schemes, type 0 and type 1, are supported. The UE shall assume that when the
scheduling grant is received with DCI format 1_0, then downlink resource allocation type 1 is used.
If the scheduling DCI is configured to indicate the downlink resource allocation type as part of the 'Frequency domain
resource assignment' field by setting a higher layer parameter resourceAllocation in PDSCH-Config to
ETSI
'dynamicSwitch', for DCI format 1_1 or setting a higher layer parameter resourceAllocationDCI-1-2 in PDSCH-Config
to 'dynamicSwitch' for DCI format 1_2, the UE shall use downlink resource allocation type 0 or type 1 as defined by
this DCI field. Otherwise the UE shall use the downlink frequency resource allocation type as defined by the higher
layer parameter resourceAllocation for DCI format 1_1 or by the higher layer parameter resourceAllocationDCI-1-2 for
DCI format 1_2.
[38.214 clause 5.1.2.2.1]
resource blocks defined by higher layer parameter rbg-Size configured by PDSCH-Config and the size of the bandwidth

1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
[38.214 clause 5.1.2.2.2]
When the scheduling grant is received with DCI format 1_2, a downlink type 1 resource allocation field consists of a
resource indication value (RIV) corresponding to a starting resource block group RBGstart=0, 1, …, NRBG-1 and a length
in terms of virtually contiguously allocated resource block groups LRBGs=1, …, NRBG, where the resource block groups
are defined as in 5.1.2.2.1 with P defined by resourceAllocationType1GranularityDCI-1-2 if the UE is configured with
higher layer parameter resourceAllocationType1GranularityDCI-1-2, and P=1 otherwise. The resource indication value
is defined by
if (LRBGs −1) ≤  NRBG / 2 then
RIV = N RBG ( L RBGs − 1) + RBG start
else
RIV = N RBG ( N RBG − L RBGs + 1) + ( N RBG − 1 − RBG start )
where LRBGs ≥ 1 and shall not exceed N RBG − RBGstart .
[TS 38.214, clause 5.1.3]
and second
[TS 38.214, clause 5.1.3.1]
For the PDSCH scheduled by a PDCCH with DCI format 1_0, format 1_1 or format 1_2 with CRC scrambled by C-
RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, MSGB-RNTI, or P-RNTI, or for the PDSCH
ETSI
scheduled without corresponding PDCCH transmissions using the higher-layer-provided PDSCH configuration SPS-
Config,
if the higher layer parameter mcs-TableDCI-1-2 given by PDSCH-Config is set to 'qam256', and the PDSCH is
scheduled by a PDCCH with DCI format 1_2 with CRC scrambled by C-RNTI
elseif the UE is not configured with MCS-C-RNTI, the higher layer parameter mcs-TableDCI-1-2 given by PDSCH-
Config is set to 'qam64LowSE', and the PDSCH is scheduled by a PDCCH with DCI format 1_2 scrambled by C-RNTI

MCS Index Modulation Order Spectral
Target code Rate R x [1024]
IMCS Qm efficiency
0 2 30 0.0586
1 2 40 0.0781
2 2 50 0.0977
3 2 64 0.1250
4 2 78 0.1523
5 2 99 0.1934
6 2 120 0.2344
7 2 157 0.3066
8 2 193 0.3770
9 2 251 0.4902
10 2 308 0.6016
11 2 379 0.7402
12 2 449 0.8770
13 2 526 1.0273
14 2 602 1.1758
15 4 340 1.3281
16 4 378 1.4766
17 4 434 1.6953
18 4 490 1.9141
19 4 553 2.1602
20 4 616 2.4063
21 6 438 2.5664
22 6 466 2.7305
23 6 517 3.0293
24 6 567 3.3223
25 6 616 3.6094
26 6 666 3.9023
27 6 719 4.2129
28 6 772 4.5234
29 2 reserved
30 4 reserved
31 6 reserved
[TS 38.214, clause 5.1.3.2]
enabled, then one of the two transport blocks is disabled by DCI format 1_1 if IMCS = 26 and if rvid = 1 for the
corresponding transport block. If both transport blocks are enabled, transport block 1 and 2 are mapped to codeword 0
and 1 respectively. If only one transport block is enabled, then the enabled transport block is always mapped to the first
codeword.
For the PDSCH assigned by a PDCCH with DCI format 1_0, format 1_1 or format 1_2 with CRC scrambled by C-
RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or SI-RNTI, if Table 5.1.3.1-2 is used and 0 ≤ I MCS ≤ 27 , or a table other
ETSI
than Table 5.1.3.1-2 is used and 0 ≤ I MCS ≤ 28 , the UE shall, except if the transport block is disabled in DCI format
1_1, first determine the TBS as specified below:
'
'
NRE = Nsc
RB
⋅ Nsymb
sh
− NDMRS
PRB
− Noh
PRB
, where N scRB = 12 is the number of subcarriers in a physical resource
sh
block, N symb is the number of symbols of the PDSCH allocation within the slot, N DMRS
PRB
is the number of
without data, as indicated by DCI format 1_1 or format 1_2 or as described for format 1_0 in Clause 5.1.6.2,
and N ohPRB is the overhead configured by higher layer parameter xOverhead in PDSCH-ServingCellConfig.
PRB
If the xOverhead in PDSCH-ServingCellconfig is not configured (a value from 6, 12, or 18), the Noh is set
to 0. If the PDSCH is scheduled by PDCCH with a CRC scrambled by SI-RNTI, RA-RNTI, MSGB-RNTI or
PRB
P-RNTI, Noh is assumed to be 0.
- (
A UE determines the total number of REs allocated for PDSCH ( NRE ) by NRE = min 156, NRE ⋅ nPRB ,
'
)
2) Unquantized intermediate variable (Ninfo) is obtained by N inf o = N RE · R·Q m ·υ .
If N inf o ≤ 3824
else
end if
 n  N inf o  
quantized intermediate number of information bits Ninf o = max 24,2 ·
'
- 
n  , where
  2 
n = max (3, log 2 (N inf o ) − 6 ) .
'
ETSI

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
n = log 2 (N inf o − 24 ) − 5 and ties in the round function are broken towards the next largest integer.
- if R ≤ 1/ 4
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C   3816 
else
'
if N inf o > 8424
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C  
8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
ETSI
end if
up to maximum value) is applied in NR Serving cell configuration.
Test frequency NRf1 is as specified in TS 38.508-1 [4] clause 4.3.1 using the common highest UL and DL channel
bandwidth and using the default subcarrier spacing specified in TS 38.508-1 [4] clause 6.2.3.1.

CategoryUL, to support Max TBS achievable based on max bandwidth of
the Band under test.
ETSI
(Note 1)
12129 ≤ TBS ≤24200 2 8*FLOOR((TBS – 200)/16)
24201 ≤ TBS ≤ 36272 3 8*FLOOR((TBS – 272)/24)
36273 ≤ TBS ≤48344 4 8*FLOOR((TBS – 344)/32)
48345≤ TBS ≤60416 5 8*FLOOR((TBS – 416)/40)
60417 ≤ TBS ≤ 72488 6 8*FLOOR((TBS –488)/48)
72489 ≤ TBS ≤84560 7 8*FLOOR((TBS – 560)/56)
84561 ≤ TBS ≤96632 8 8*FLOOR((TBS –632)/64)
96633< TBS ≤108704 9 8*FLOOR((TBS –704)/72)
10705 ≤ TBS ≤120776 10 8*FLOOR((TBS – 776)/80)
120777≤ TBS ≤132848 11 8*FLOOR((TBS –848)/88)
132849 ≤ TBS ≤ 144920 12 8*FLOOR((TBS – 920)/96)
TBS> 144920 13 8*FLOOR((TBS – 992)/104)
Note 1: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in
TS 24.301 [21] clause 9.9.4.12).
PDCP SDU size = (TBS – N*PDCP header size – N*AMD PDU header size - N*MAC header size –
Size of Timing Advance – RLC Status PDU size- MAC header for RLC Status PDU) / N, where
Size of Timing Advance MAC CE with header is 16 bits (if no Timing Advance and/or RLC status needs
to be sent, padding will occur instead).
This gives:
Note 2: According to the final PDCP SDU size formula in Note 1, the smallest TBS that can be tested is 136
bits.
ETSI
Table 7.1.1.4.1.5.3.2-2A: Bandwidth part Dependent Parameters for RBG’s with start of BWP assumed
as 0
DL,BWP
size
RBG
11 2 1 All 1…11
18 2 2 2,4,6,8,10,12,16,18
24 2 2 2,4,6,8,10,12,16,18,20,22,24
25 2 1 All 1…25
31 2 1 All 1…31
32 2 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32
38 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38
51 4 3 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 4 4 4,8,12,16,20,24,28,32,36,40,44,48,52
65 4 1 1,4,5,8,9,12,13,16,17,20,21,24,25,28,29,32,33,36,37,40,41,44,45,48,49,
52,53,56,57,60,61,64,65
66 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,
54,56,58,60,62,64,66
79 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79
106 8 2 2,8,10,16,18,24,26,32,34,40,42,48,50,56,58,64,66,72,74,80,82,88,90,96,
92,104,106
107 8 3 3,8,11,16,19,24,27,32,35,40,43,48,51,56,59,64,67,72,75,80,83,88,91,96,
99,104,107
132 8 4 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,104, 108,112,116,120,124,128,132
133 8 5 5,8,13,16,21,24,29,32,37,40,45,48,53,56,61,64,69,72,77,80,85,88,93,96,
101,104, 109,112,117,120,125,128,133
135 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79,80,87,88,95,96,
103,104, 111,112,119,120,127,128,135
160 16 16 16,32,48,64,80,96,112,128,144,160
216 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152,160,
168, 176,184,192,200,208,216
217 16 9 9,16,25,32,41,48,57,64,73,80,89,96,105,112,121,128,137,144,153,160,
169,176,185,192,201,208,217
264 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,160,168,
176,184,192,200,208,216,224,232,240,248,256,264
270 16 14 14,16,30,32,46,44,62,64,78,80,94,96,110,112, 126,128,142,144,158,
160,174, 176,190,192, 206,208,222,224,238,240, 254,256,270
273 16 1 1,16,17,32,33,48,49,64,65,80,81,96,97,112,113,128,129,144,145,160,
161,176,171, 192,193, 208,209, 224,225,240,241,256,257,272,273

mcs-TableDCI-1-2-r16 qam64LowSE
resourceAllocationDCI-1-2-r16 resourceAllocationType1
ETSI

U-S Message
- EXCEPTION: EXCEPTION: Steps - - - -
1 to 5 are repeated for allowed
values of N PRB as per table
7.1.1.4.5.3.3.2-2A in BWP, time
domain resource as per table
7.1.1.4.5.0-1 and I MCS from 0 to
28.
NOTE: Skip the execution of steps
for which the TBS size results in
coding rate exceeding 0.95.
number of DL-SCH transport
7.1.1.4.1.5.3.2-1 and larger than
Table 7.1.1.4.1.5.3.2-2
7.1.1.4.1.5.3.2-2.
3 The SS transmits the PDCP SDUs <-- MAC PDU (NxPDCP - -
concatenated into a MAC PDU SDUs)
and indicates on PDCCH DCI DCI: (DCI Format 1_0, S,
Format 1_0 and values of S, L, I MCS and nPRB.)
L, I MCS and nPRB.
4 At the reception of scheduling <-- (UL Grant) - -
request the SS transmits UL Grant
for transmitting loop back PDCP
SDUs.
5 CHECK: Does UE return the --> (NxPDCP SDUs) 1 P
same number of PDCP SDUs with
the SS in step 3?
None.
ETSI
7.1.1.4.2 UL-SCH Transport Block Size Selection
7.1.1.4.2.0 Common parameters for UL-SCH Transport Block Size Selection
Table 7.1.1.4.2.0-1: PUSCH-TimeDomainResourceAllocationList

PUSCH-TimeDomainResourceAllocationList ::= 2 entry
SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF
PUSCH-TimeDomainResourceAllocation {
PUSCH-TimeDomainResourceAllocation[1] entry 1 FR1
SEQUENCE {
k2 2 FR1
4 FR2
mappingType typeB
symbol(S)=10,
Length(L)=4
symbol(S)=0,
Length(L)=4
}
PUSCH-TimeDomainResourceAllocation[2] entry 2 FR1
SEQUENCE {
k2 2 FR1
4 FR2
mappingType typeB
symbol(S)=0,
Length(L)=14
}
}
Table 7.1.1.4.2.0-2: PUSCH-Config

dmrs-UplinkForPUSCH-MappingTypeB CHOICE {
setup DMRS-UplinkConfig See Table
7.1.1.4.2.0-3
}
}
Table 7.1.1.4.2.0-3: DMRS-UplinkConfig
ETSI
Table 7.1.1.4.2.0-4: SchedulingRequestResourceConfig

SchedulingRequestResourceConfig ::= SEQUENCE
{
schedulingRequestResourceId SchedulingRequestReso
urceId
schedulingRequestID SchedulingRequestId
sl40 9 With SCS = SCS15
kHz15 results in
repetition every 40
ms
kHz30 results in
repetition every 40
ms
kHz120 results in
repetition every 40
ms
}
resource 6 ID of the PUCCH
resource as
configured by
PUCCH-Config
(Table 4.6.3-84)
}
Table 7.1.1.4.2.0-5: PDSCH-TimeDomainResourceAllocationList

PDSCH-TimeDomainResourceAllocationList ::= 2 entries
PDSCH-TimeDomainResourceAllocation {
SEQUENCE {
k0 Not present
mappingType typeA
}
SEQUENCE {
k0 1
mappingType typeA
}
}
7.1.1.4.2.1 UL-SCH Transport Block Size selection / DCI format 0_0 / Transform precoding
disabled
(1)
ensure that {
when { UE has pending data for transmission and receives on PDCCH DCI format 0_0 indicating a
resource block assignment correspondent to physical resource blocks , Time domain resource
assignment and modulation and coding }
ETSI
then { UE transmits MAC PDU on PUSCH as per Modulation Coding scheme, time domain resource
allocation and PRB's }
}
38.214 clause 6.1.2.1, 6.1.2.2, 6.1.2.2.2, 6.1.4.1, 5.1.3.1, 6.1.4.2 and 5.1.3.2. Unless otherwise stated these are Rel-15
requirements.
[TS 38.212, clause 7.3.1.1.1]
DCI format 0_0 is used for the scheduling of PUSCH in one cell.
RNTI or new-RNTI:
- Identifier for DCI formats – 1 bit
- The value of this bit field is always set to 0, indicating an UL DCI format
- Frequency domain resource assignment – log2 ( N RB

UL,BWP UL,BWP
( N RB + 1) / 2) bits where
UL,BWP
- N RB is the size of the active UL bandwidth part in case DCI format 0_0 is monitored in the UE specific
- otherwise, N RB
UL, BWP is the size of the initial UL bandwidth part.
- For PUSCH hopping with resource allocation type 1:
- N UL_hop MSB bits are used to indicate the frequency offset according to Subclause 6.3 of [6, TS 38.214],
where N UL_hop = 1 if the higher layer parameter frequencyHoppingOffsetLists contains two offset values
and N UL_hop = 2 if the higher layer parameter frequencyHoppingOffsetLists contains four offset values
- log2 ( NRBUL,BWP ( NRBUL,BWP + 1) / 2) − N UL_hop bits provides the frequency domain resource allocation
according to Subclause 6.1.2.2.2 of [6, TS 38.214]
- For non-PUSCH hopping with resource allocation type 1:
- log ( N
2
UL,BWP
RB
UL,BWP
( N RB + 1) / 2) bits provides the frequency domain resource allocation according to
Subclause 6.1.2.2.2 of [6, TS 38.214]
- Time domain resource assignment – 4 bits as defined in Subclause 6.1.2.1 of [6, TS 38.214]
- Frequency hopping flag – 1 bit.
- Modulation and coding scheme – 5 bits as defined in Subclause 6.1.3 of [6, TS 38.214]
- TPC command for scheduled PUSCH – 2 bits as defined in Subclause 7.1.1 of [5, TS 38.213]
- Padding bits, if required.
- UL/SUL indicator – 1 bit for UEs configured with SUL in the cell as defined in Table 7.3.1.1.1-1 and the
number of bits for DCI format 1_0 before padding is larger than the number of bits for DCI format 0_0 before
ETSI
padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0_0,
after the padding bit(s).
- If the UL/SUL indicator is present in DCI format 0_0 and the higher layer parameter pusch-Config is not
configured on both UL and SUL the UE ignores the UL/SUL indicator field in DCI format 0_0, and the
corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer
parameter pucch-Config is configured;
- If the UL/SUL indicator is not present in DCI format 0_0, the corresponding PUSCH scheduled by the DCI
format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured.
The following information is transmitted by means of the DCI format 0_0 with CRC scrambled by TC-RNTI:
- Frequency domain resource assignment – log2 ( N RB

UL,BWP UL,BWP
( N RB + 1) / 2) bits where
UL,BWP
- N RB is the size of the initial UL bandwidth part.
where N UL_hop = 1 if N RB
UL,BWP
< 50 and N UL_hop = 2 otherwise
- log2 ( NRBUL,BWP ( NRBUL,BWP + 1) / 2)

− N UL_hop bits provides the frequency domain resource allocation
- log ( N
2
UL,BWP
RB
UL,BWP
( N RB + 1) / 2) bits provides the frequency domain resource allocation according to
Subclause 6.1.2.2.2 of [6, TS 38.214]
- Modulation and coding scheme – 5 bits as defined in Subclause 6.1.3 of [6, TS 38.214], using Table 5.1.3.1-1
- New data indicator – 1 bit, reserved
- HARQ process number – 4 bits, reserved
- UL/SUL indicator – 1 bit if the cell has two ULs and the number of bits for DCI format 1_0 before padding is
larger than the number of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if
present, locates in the last bit position of DCI format 0_0, after the padding bit(s).
- If 1 bit, reserved, and the corresponding PUSCH is always on the same UL carrier as the previous
transmission of the same TB
If DCI format 0_0 is monitored in common search space and if the number of information bits in the DCI format 0_0
prior to padding is less than the payload size of the DCI format 1_0 monitored in common search space for scheduling
the same serving cell, zeros shall be appended to the DCI format 0_0 until the payload size equals that of the DCI
format 1_0.
prior to padding is larger than the payload size of the DCI format 1_0 monitored in common search space for
ETSI
scheduling the same serving cell, the bit width of the frequency domain resource allocation field in the DCI format 0_0
is reduced by truncating the first few most significant bits such that the size of DCI format 0_0 equals to the size of the
DCI format 1_0.
If DCI format 0_0 is monitored in UE specific search space but does not satisfy at least one of the following
and if the number of information bits in the DCI format 0_0 prior to padding is less than the payload size of the DCI
format 1_0 monitored in common search space for scheduling the same serving cell, zeros shall be appended to the DCI
format 0_0 until the payload size equals that of the DCI format 1_0.
and if the number of information bits in the DCI format 0_0 prior to padding is larger than the payload size of the DCI
format 1_0 monitored in common search space for scheduling the same serving cell, the bit width of the frequency
domain resource allocation field in the DCI format 0_0 is reduced by truncating the first few most significant bits such
that the size of DCI format 0_0 equals to the size of the DCI format 1_0.
If DCI format 0_0 is monitored in UE specific search space and satisfies both of the following
format 1_0 monitored in UE specific search space for scheduling the same serving cell, zeros shall be appended to the
DCI format 0_0 until the payload size equals that of the DCI format 1_0.
[TS 38.214, clause 6.1.2.1]
Reporting Settings. The ith codepoint of K2 s determined as K 2 = maxY j where Y j (i ) is the ith codepoint of Y j .
j
 2 μ PUSCH 
 2 μ PDCCH 
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
ETSI
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and

Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
Type B {0,…,13} {1,…,14} {1,…,14} {0,…,12} {1,…,12} {1,…,12}

0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
PUSCH transmission.
[38.214 clause 6.1.2.2]
The UE shall determine the resource block assignment in frequency domain using the resource allocation field in the
detected PDCCH DCI. Two uplink resource allocation schemes type 0 and type 1 are supported. Uplink resource
allocation scheme type 0 is supported for PUSCH only when transform precoding is disabled. Uplink resource
allocation scheme type 1 is supported for PUSCH for both cases when transform precoding is enabled or disabled.
If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the Frequency domain
resource assignment field by setting a higher layer parameter resourceAllocation in pusch-Config to ‘dynamicswitch’,
the UE shall use uplink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise the UE shall use the
uplink frequency resource allocation type as defined by the higher layer parameter resourceAllocation.
The UE shall assume that when the scheduling PDCCH is received with DCI format 0_0, then uplink resource
allocation type 1 is used.
If a bandwidth part indicator field is not configured in the scheduling DCI, the RB indexing for uplink type 0 and type 1
resource allocation is determined within the UE's active bandwidth part. If a bandwidth part indicator field is configured
in the scheduling DCI, the RB indexing for uplink type 0 and type 1 resource allocation is determined within the UE's
bandwidth part indicated by bandwidth part indicator field value in the DCI, except for the case when DCI format 0_0 is
decoded in any PDCCH common search space in CORESET 0 in which case the initial bandwidth part shall be used.
The UE shall upon detection of PDCCH intended for the UE determine first the uplink bandwidth part and then the
resource allocation within the bandwidth part.
[38.214 clause 6.1.2.2.2]
ETSI
In uplink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set of
size
contiguously allocated non-interleaved virtual resource blocks within the active carrier bandwidth part of size N BWP
PRBs except for the case when DCI format 0_0 is decoded in the Type0-PDCCH common search space in CORESET 0
size
in which case the initial bandwidth part of size N BWP shall be used.
An uplink type 1 resource allocation field consists of a resource indication value (RIV) corresponding to a starting

if ( LRBs − 1) ≤ N BWP
size
/2  then
RIV = N BWP
size
else
RIV = N BWP
size size
size
− 1 − RBstart )
where LRBs ≥ 1 and shall not exceed N BWP − RBstart .

size
[TS 38.214, clause 6.1.4.1]
For the PUSCH assigned by a DCI format 0_0/0_1 with CRC scrambled by C-RNTI, new-RNTI, TC-RNTI, or SP-CSI-
RNTI, the transform precoding is enabled if transformPrecoder in PUSCH-Config is set to 'enabled', or if
transformPrecoder in PUSCH-Config is not configured and msg3-transformPrecoding in rach-ConfigCommon is set to
'enabled'; otherwise the transform precoding is disabled.
For the PUSCH assigned by a DCI format 0_0/0_1 with CRC scrambled by CS-RNTI, or the PUSCH with configured
grant using CS-RNTI, the transform precoding is enabled if transformPrecoder in ConfiguredGrantConfig is set to
For a PUSCH scheduled by RAR UL grant or for a PUSCH scheduled by a DCI format 0_0/0_1 with CRC scrambled
by C-RNTI, TC-RNTI, or CS-RNTI, or SP-CSI-RNTI, or for a PUSCH with configured grant using CS-RNTI,
if transformPrecoder is disabled for this PUSCH transmission
- if mcs-Table in PUSCH-Config is set to 'qam256', and PUSCH is scheduled with C-RNTI or SP-CSI-RNTI, and
PUSCH is assigned by DCI format 0_1,
- the UE shall use IMCS and Table 5.1.3.1-2 to determine the modulation order (Qm) and Target code rate (R)
used in the physical uplink shared channel.
- elseif the UE is not configured with new-RNTI, mcs-Table in PUSCH-Config is set to 'qam64LowSE', the
PUSCH is scheduled with C-RNTI, or SP-CSI-RNTI, and the PUSCH is assigned by a PDCCH in a UE-specific
search space,
- elseif the UE is configured with new-RNTI, and the PUSCH is scheduled with new-RNTI,
- elseif mcs-Table in ConfiguredGrantConfig is set to 'qam256', and PUSCH is scheduled with CS-RNTI,
- elseif mcs-Table in ConfiguredGrantConfig is set to 'qam64LowSE', and PUSCH is scheduled with CS-RNTI,
ETSI
- else
[TS 38.214, clause 5.1.3.1]

IMCS Qm efficiency
0 2 120 0.2344
1 2 157 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 438 2.5664
18 6 466 2.7305
19 6 517 3.0293
20 6 567 3.3223
21 6 616 3.6094
22 6 666 3.9023
23 6 719 4.2129
24 6 772 4.5234
25 6 822 4.8164
26 6 873 5.1152
27 6 910 5.3320
28 6 948 5.5547
29 2 reserved
30 4 reserved
31 6 reserved
[TS 38.214, clause 6.1.4.2]
by C-RNTI, new-RNTI, TC-RNTI, CS-RNTI, or SP-CSI-RNTI.
if
- 0 ≤ I MCS ≤ 27 and transform precoding is disabled and Table 5.1.3.1-2 is used, or
- 0 ≤ I MCS ≤ 28 and transform precoding is disabled and a table other than Table 5.1.3.1-2 is used, or
- 0 ≤ I MCS ≤ 27 and transform precoding is enabled and , the UE shall first determine the TBS as specified below:
The UE shall first determine the number of REs (NRE) within the slot:
- '
A UE first determines the number of REs allocated for PUSCH within a PRB N RE by ( )
ETSI
- '
N RE = N scRB ∗ N symb
sh
− N DMRS
PRB
− N oh
PRB RB
, where N sc = 12 is the number of subcarriers in the frequency
sh
domain in a physical resource block, N symb is the number of symbols of the PUSCH allocation within the
PRB
slot, N DMRS is the number of REs for DM-RS per PRB in the scheduled duration including the overhead of
the DM-RS CDM groups without data, as indicated by DCI format 0_1 or as described for DCI format 0_0 in
PRB
Subclause 6.2.2, and N oh is the overhead configured by higher layer parameter xOverhead in PUSCH-
PRB PRB
ServingCellConfig. If the Noh is not configured (a value from 0, 6, 12, or 18), the Noh is assumed to be
PRB
0. For MSG3 transmission the Noh is always set to 0..
- A UE determines the total number of REs allocated for PUSCH N RE by ( )

NRE = min ( '
156, NRE )⋅n PRB where n PRB is the total number of allocated PRBs for the UE.
- Next, proceed with steps 2-5 as defined in Subclause 5.1.3.2
else if
- 28 ≤ I MCS ≤ 31 and transform precoding is enabled,
- the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport
block using 0 ≤ I MCS ≤ 27 . If there is no PDCCH for the same transport block using 0 ≤ I MCS ≤ 27 , and if the
initial PUSCH for the same transport block is transmitted with configured grant, the TBS shall be determined
from the most recent configured scheduling PDCCH.
else
[TS 38.214, clause 5.1.3.2]
2 Intermediate number of information bits (Ninfo) is obtained by N inf o = N RE · R·Qm ·υ .
If N inf o ≤ 3824
else
end if
  N inf o  
o = max
'
24,2 n · n 
, where
  2 
n = max(3, log2 (N inf o ) − 6) .
'
ETSI

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
- if R ≤ 1 / 4
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  3816 
else
o > 8424
'
if N inf
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
ETSI
end if

UE Category Maximum number of bits of a UL-SCH transport block
received within a TTI
ETSI
Table 7.1.1.4.2.1.3.2-2: Number of uplink PDCP SDUs and PDCP SDU size used as test data
(Note 1)
12129 ≤ TBS ≤24200 2 8*FLOOR((TBS – 200)/16)
24201 ≤ TBS ≤ 36272 3 8*FLOOR((TBS – 272)/24)
36273 ≤ TBS ≤48344 4 8*FLOOR((TBS – 344)/32)
48345≤ TBS ≤60416 5 8*FLOOR((TBS – 416)/40)
60417 ≤ TBS ≤ 72488 6 8*FLOOR((TBS –488)/48)
72489 ≤ TBS ≤84560 7 8*FLOOR((TBS – 560)/56)
84561 ≤ TBS ≤96632 8 8*FLOOR((TBS –632)/64)
96633< TBS ≤108704 9 8*FLOOR((TBS –704)/72)
10705 ≤ TBS ≤120776 10 8*FLOOR((TBS – 776)/80)
120777≤ TBS ≤132848 11 8*FLOOR((TBS –848)/88)
132849 ≤ TBS ≤ 144920 12 8*FLOOR((TBS – 920)/96)
144921 ≤ TBS ≤ 156992 13 8*FLOOR((TBS – 992)/104)
156993 ≤ TBS ≤ 169064 14 8*FLOOR((TBS – 1064)/112)
169065 ≤ TBS ≤ 181136 15 8*FLOOR((TBS – 1136)/120)
181137 ≤ TBS ≤ 193208 16 8*FLOOR((TBS – 1208)/128)
193209 ≤ TBS ≤ 205280 17 8*FLOOR((TBS – 1280)/136)
205281 ≤ TBS ≤ 217352 18 8*FLOOR((TBS – 1352)/144)
217353 ≤ TBS ≤ 229424 19 8*FLOOR((TBS – 1424)/152)
TBS> 229424 20 8*FLOOR((TBS – 1496)/160)
24.301 [21] clause 9.9.4.12).
This gives:

mcs-Table qam64
ETSI

U-S Message
N PRB 1 to N RB
UL,BWP
in BWP, time
domain resource as per Table
7.1.1.4.2.0-1 and I MCS from 0 to
28.
number of UL-SCH transport
7.1.1.4.2.1.3.2-1 and larger than
Table 7.1.1.4.2.1.3.2-2.
Skip the execution of steps 2 to 5
for which the TBS size equal to
3824 or 3840. (Note 2)
Skip the execution of steps for

> 27 and < 5.
(Note 1)
7.1.1.4.2.1.3.2-2.
3 The SS transmits all PDCP SDUs <-- MAC PDU (NxPDCP - -
(NSDUs) as created in step 2 in a SDUs)
MAC PDU.
4 After the reception of 2 <-- (UL Grant) (DCI Format - -
Scheduling Request, , SS 0_0, S, L, I MCS and nPRB.)
transmits UL Grant DCI 0_0, and
values of S, L, I MCS and nPRB..
5 CHECK: Does UE return the --> MAC PDU (N x PDCP 1 P
same number of PDCP SDUs with SDU)
the SS in step 3 using Time,
frequency Resources and
modulation and coding scheme as
configured by the SS in step 4?
Note 1: For > 27 and < 5, the combination results in higher coding rate and therefore leading
to CRC errors in decoding UL data.
Note 2: There is ambiguity of TBS calculation when 3824.0 < Ninfo < 3825.0 in clause 5.1.3.2 of TS 38.214
[15].
None.
ETSI
7.1.1.4.2.2 Void
Transform precoding disabled
(1)
ensure that {
when { UE has pending data for transmission and receives DCI format 0_1 indicating resource
allocation type 0 a resource block assignment correspondent to physical resource blocks , Time
domain resource assignment and a modulation and coding }
then { UE transmits MAC PDU's on PUSCH as per Modulation Coding scheme, time domain resource
}
(2)
ensure that {
}
38.214 clause 6.1.2.1, 6.1.2.2, 6.1.2.2.1, 6.1.2.2.2, 6.1.4.1, 5.1.3.1, 6.1.4.2 and 5.1.3.2. Unless otherwise stated these are
Rel-15 requirements.
[TS 38.212, clause 7.3.1.1.2]
RNTI or SP-CSI-RNTI or new-RNTI:
- Carrier indicator – 0 or 3 bits, as defined in Subclause 10.1 of [5, TS38.213].
- UL/SUL indicator – 0 bit for UEs not configured with SUL in the cell or UEs configured with SUL in the cell
but only PUCCH carrier in the cell is configured for PUSCH transmission; 1 bit for UEs configured with SUL in
the cell as defined in Table 7.3.1.1.1-1.
- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of UL BWPs nBWP,RRC configured by
higher layers, excluding the initial UL bandwidth part. The bit width for this field is determined as
log2 (nBWP ) bits, where
- nBWP = nBWP,RRC + 1 if , in which case the bandwidth part indicator is equivalent to the higher layer parameter
BWP-Id;
- otherwise nBWP = nBWP,RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
UL,BWP
of the active UL bandwidth part:
ETSI
[6, TS 38.214],
- log2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits if only resource allocation type 1 is configured, or
(
max log 2 ( N RB
UL, BWP UL, BWP
( N RB )
configured.
6.1.2.2.1 of [6, TS 38.214].
- For resource allocation type 1, the log2 ( N RB

UL,BWP UL,BWP
follows:
N UL_hop
- MSB bits are used to indicate the frequency offset according to Subclause 6.3 of [6, TS
N =1
38.214], where UL_hop if the higher layer parameter frequencyHoppingOffsetLists contains two
N =2
offset values and UL_hop if the higher layer parameter frequencyHoppingOffsetLists contains four
offset values
- log2 ( NRBUL,BWP ( NRBUL,BWP + 1) / 2)

− N UL_hop bits provides the frequency domain resource allocation
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if both
allocation type 0 for the indicated bandwidth part if the bit width of the "Frequency domain resource
assignment" field of the active bandwidth part is smaller than the bit width of the "Frequency domain
resource assignment" field of the indicated bandwidth part.
- log2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits provides the frequency domain resource allocation according to
Subclause 6.1.2.2.2 of [6, TS 38.214]
width for this field is determined as log 2 ( I ) bits, where I the number of entries in the higher layer parameter
- Frequency hopping flag – 0 or 1 bit:
- 0 bit if only resource allocation type 0 is configured or if the higher layer parameter frequencyHopping is not
configured;
Subclause 6.3 of [6, TS 38.214].
- Modulation and coding scheme – 5 bits as defined in Subclause 6.1.4.1 of [6, TS 38.214]
- 1st downlink assignment index – 1 or 2 bits:
ETSI
- 1 bit for semi-static HARQ-ACK codebook;
- 2 bits for dynamic HARQ-ACK codebook.
- 2nd downlink assignment index – 0 or 2 bits:
- 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks;
- 0 bit otherwise.
- TPC command for scheduled PUSCH – 2 bits as defined in Subclause 7.1.1 of [5, TS38.213]
  min {Lmax , N SRS } N SRS  

- SRS resource indicator – log 2 
  

  or
 log2 (NSRS) bits, where NSRS is the number of
  k =1  k  
configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value
'codeBook' or 'nonCodeBook', and LPUSCH
max
is the maximum number of supported layers for the PUSCH.
  min{Lmax , NSRS} N 
PUSCH
 SRS 
- log 

2

  
  bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter
k =1  k  
  
txConfig = nonCodebook, where NSRS is the number of configured SRS resources in the SRS resource set
associated with the higher layer parameter usage of value 'nonCodeBook';
- log2 (NSRS) bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook, where
NSRS is the number of configured SRS resources in the SRS resource set associated with the higher layer
parameter usage of value 'codeBook'.
- Precoding information and number of layers – number of bits determined by the following:
- 0 bits if the higher layer parameter txConfig = nonCodeBook;
- 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;
- 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if txConfig = codebook, and according to the
values of higher layer parameters transformPrecoder, maxRank, and codebookSubset;
- 2 or 4 bits according to Table7.3.1.1.2-4 for 2 antenna ports, if txConfig = codebook, and according to the
values of higher layer parameters maxRank and codebookSubset;
- 1 or 3 bits according to Table7.3.1.1.2-5 for 2 antenna ports, if txConfig = codebookmaxRank and

codebookSubset, and according to the values of higher layer parameters .
- Antenna ports – number of bits determined by the following
- 2 bits as defined by Tables 7.3.1.1.2-6, if transformPrecoder=enabled, dmrs-Type=1, and maxLength=1;
- 3 bits as defined by Tables 7.3.1.1.2-8/9/10/11, if transformPrecoder=disabled, dmrs-Type=1, and

maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher
layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers
field if the higher layer parameter txConfig = codebook;

ETSI


field if the higher layer parameter txConfig = codebook.
where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers
to CDM groups {0}, {0,1}, and {0, 1,2} respectively.
If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-

derived according to dmrs-UplinkForPUSCH-MappingTypeA and x B is the “Antenna ports” bit width derived
according to dmrs-UplinkForPUSCH-MappingTypeB. A number of xA − xB zeros are padded in the MSB of
this field, if the mapping type of the PUSCH corresponds to the smaller value of x A and x B .
- CSI request – 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSize.
- CBG transmission information (CBGTI) – 0, 2, 4, 6, or 8 bits determined by higher layer parameter

maxCodeBlockGroupsPerTransportBlock for PUSCH.
- PTRS-DMRS association – number of bits determined as follows
- 0 bit if PTRS-UplinkConfig is not configured and transformPrecoder=disabled, or if

transformPrecoder=enabled, or if maxRank=1;
- 2 bits otherwise, where Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between
PTRS port(s) and DMRS port(s) for transmission of one PT-RS port and two PT-RS ports respectively, and
the DMRS ports are indicated by the Antenna ports field.
“PTRS-DMRS association” field is present for the indicated bandwidth part but not present for the active
bandwidth part, the UE assumes the “PTRS-DMRS association” field is not present for the indicated
bandwidth part.betaOffsets = semiStatic
- beta_offset indicator – 0 if the higher layer parameter ; otherwise 2 bits as defined by Table 9.3-3 in [5, TS
38.213].
- DMRS sequence initialization – 0 if the higher layer parameter transformPrecoder=enabled; 1 bit if the higher
layer parameter transformPrecoder=disabled and both scramblingID0 and scramblingID1 are configured in
DMRS-UplinkConfig, for nSCID selection defined in Subclause 6.4.1.1.1.1 of [4, TS 38.211].
- UL-SCH indicator – 1 bit. A value of “1” indicates UL-SCH shall be transmitted on the PUSCH and a value of
“0” indicates UL-SCH shall not be transmitted on the PUSCH.
For a UE configured with SUL in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of
the cell and if the number of information bits in format 0_1 for the SUL is not equal to the number of information bits in
format 0_1 for the non-SUL, zeros shall be appended to smaller format 0_1 until the payload size equals that of the
larger format 0_1.
ETSI
Table 7.3.1.1.2-1: Bandwidth part indicator
Value of BWP indicator field

Bandwidth part
2 bits
00 First bandwidth part configured by higher layers
01 Second bandwidth part configured by higher layers
10 Third bandwidth part configured by higher layers
11 Fourth bandwidth part configured by higher layers
Table 7.3.1.1.2-2: Precoding information and number of layers, for 4 antenna ports, if
transformPrecoder=disabled and maxRank = 2 or 3 or 4
codebookSubset codebookSubset
Bit field Bit field Bit field
= = codebookSubset=
mapped to mapped to mapped to
fullyAndPartialAn partialAndNonCo nonCoherent
index index index
dNonCoherent herent
0 1 layer: TPMI=0 0 1 layer: TPMI=0 0 1 layer: TPMI=0
… … … … … …
4 2 layers: TPMI=0 4 2 layers: TPMI=0 4 2 layers: TPMI=0
… … … … … …
12 1 layer: TPMI=4 12 1 layer: TPMI=4 12-15 reserved
… … … …
19 1 layer: TPMI=11 19 1 layer: TPMI=11
20 2 layers: TPMI=6 20 2 layers: TPMI=6
… … … …
32 1 layers: TPMI=12
… …
… …
56 3 layers: TPMI=3
… …
59 3 layers: TPMI=6
60 4 layers: TPMI=3
61 4 layers: TPMI=4
62-63 reserved
ETSI
Table 7.3.1.1.2-3: Precoding information and number of layers for 4 antenna ports, if
transformPrecoder= enabled, or if transformPrecoder=disabled and maxRank = 1
Bit field codebookSubset = Bit field codebookSubset= Bit field
codebookSubset
mapped to fullyAndPartialAnd mapped to partialAndNonCoh mapped to
= nonCoherent
index NonCoherent index erent index
… … … … … …
… … … …
12 1 layers: TPMI=12 12-15 reserved
… …
28-31 reserved
transformPrecoder=disabled and maxRank = 2
Bit field codebookSubset = Bit field
codebookSubset =
mapped fullyAndPartialAndNonCoher mapped
nonCoherent
to index ent to index
3 1 layer: TPMI=2 3 reserved
4 1 layer: TPMI=3
5 1 layer: TPMI=4
6 1 layer: TPMI=5
7 2 layers: TPMI=1
8 2 layers: TPMI=2
9-15 reserved
transformPrecoder= enabled, or if transformPrecoder= disabled and maxRank = 1
Bit field codebookSubset = Bit field

codebookSubset
mapped to fullyAndPartialAnd mapped to
= nonCoherent
index NonCoherent index
2 1 layer: TPMI=2
3 1 layer: TPMI=3
4 1 layer: TPMI=4
5 1 layer: TPMI=5
6-7 reserved
...
Table 7.3.1.1.2-33: VRB-to-PRB mapping
Bit field mapped to index VRB-to-PRB mapping

0 Non-interleaved
1 Interleaved
[TS 38.214, clause 6.1.2.1]
ETSI
j
 2 μ PUSCH 
 2 μ PDCCH 
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and

Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
Type B {0,…,13} {1,…,14} {1,…,14} {0,…,12} {1,…,12} {1,…,12}

0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
ETSI
PUSCH transmission.
[38.214 clause 6.1.2.2]
[38.214 clause 6.1.2.2.1]
In uplink resource allocation of type 0, the resource block assignment information includes a bitmap indicating the
resource blocks defined by higher layer parameter rbg-Sizeconfigured for PUSCH and the size of the carrier bandwidth

Carrier Bandwidth Part Size Configuration 1 Configuration 2
1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
size
The total number of RBGs ( N RBG ) for a uplink carrier bandwidth part i of size N BWP, i PRBs is given by
(
N RBG = N BWP
size
( )) 
,i + N BWP,i mod P / P where
start

start
,i mod P ,
- size
the size of the last RBG is RBGlast (
= N BWP
start size
) ( start
)
,i + N BWP ,i mod P if N BWP ,i + N BWP ,i mod P > 0 and P otherwise.
size
- the size of all other RBG is P.
indexed in the order of increasing frequency of the carrier bandwidth part and starting at the lowest frequency. The
order of RBG bitmap is such that RBG 0 to RBG N RBG − 1 are mapped from 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.
[38.214 clause 6.1.2.2.2]
size
ETSI
size

size
/2  then
RIV = N BWP
size
else
RIV = N BWP
size size
size
− 1 − RBstart )

size
[TS 38.214, clause 6.1.4.1]
search space,
- else
ETSI
[TS 38.214, clause 5.1.3.1]

IMCS Qm efficiency
0 2 120 0.2344
1 2 157 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 438 2.5664
18 6 466 2.7305
19 6 517 3.0293
20 6 567 3.3223
21 6 616 3.6094
22 6 666 3.9023
23 6 719 4.2129
24 6 772 4.5234
25 6 822 4.8164
26 6 873 5.1152
27 6 910 5.3320
28 6 948 5.5547
29 2 reserved
30 4 reserved
31 6 reserved
[TS 38.214, clause 6.1.4.2]
if
- 0 ≤ I MCS ≤ 27 and transform precoding is enabled, the UE shall first determine the TBS as specified below:
- '
- '
sh
− N DMRS
PRB
− N oh
PRB RB
sh
ETSI
PRB
PRB
PRB PRB
PRB

( '
)
NRE = min 156, NRE ⋅ nPRB where nPRB is the total number of allocated PRBs for the UE.
else if
else
[TS 38.214, clause 5.1.3.2]
If N inf o ≤ 3824
else
end if
  N inf o  
o = max
'
24,2 n · n 
, where
  2 
n = max(3, log2 (N inf o ) − 6) .
'
ETSI

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
- if R ≤ 1 / 4
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  3816 
else
o > 8424
'
if N inf
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
ETSI
end if

within a TTI
ETSI
(Note 1)
12129 ≤ TBS ≤24200 2 8*FLOOR((TBS – 200)/16)
24201 ≤ TBS ≤ 36272 3 8*FLOOR((TBS – 272)/24)
36273 ≤ TBS ≤48344 4 8*FLOOR((TBS – 344)/32)
48345≤ TBS ≤60416 5 8*FLOOR((TBS – 416)/40)
60417 ≤ TBS ≤ 72488 6 8*FLOOR((TBS –488)/48)
72489 ≤ TBS ≤84560 7 8*FLOOR((TBS – 560)/56)
84561 ≤ TBS ≤96632 8 8*FLOOR((TBS –632)/64)
96633< TBS ≤108704 9 8*FLOOR((TBS –704)/72)
10705 ≤ TBS ≤120776 10 8*FLOOR((TBS – 776)/80)
120777≤ TBS ≤132848 11 8*FLOOR((TBS –848)/88)
132849 ≤ TBS ≤ 144920 12 8*FLOOR((TBS – 920)/96)
144921 ≤ TBS ≤ 156992 13 8*FLOOR((TBS – 992)/104)
156993 ≤ TBS ≤ 169064 14 8*FLOOR((TBS – 1064)/112)
169065 ≤ TBS ≤ 181136 15 8*FLOOR((TBS – 1136)/120)
181137 ≤ TBS ≤ 193208 16 8*FLOOR((TBS – 1208)/128)
193209 ≤ TBS ≤ 205280 17 8*FLOOR((TBS – 1280)/136)
205281 ≤ TBS ≤ 217352 18 8*FLOOR((TBS – 1352)/144)
217353 ≤ TBS ≤ 229424 19 8*FLOOR((TBS – 1424)/152)
TBS> 229424 20 8*FLOOR((TBS – 1496)/160)
24.301 [21] clause 9.9.4.12).
This gives:
ETSI
BWP assumed as 0
DL,BWP
size
RBG
11 2 1 All 1…11
18 2 2 2,4,6,8,10,12,16,18
24 2 2 2,4,6,8,10,12,16,18,20,22,24
25 2 1 All 1…25
31 2 1 All 1…31
32 2 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32
38 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38
51 4 3 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 4 4 4,8,12,16,20,24,28,32,36,40,44,48,52
65 4 1 1,4,5,8,9,12,13,16,17,20,21,24,25,28,29,32,33,36,37,40,41,44,45,48,49,
52,53,56,57,60,61,64,65
66 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,
54,56,58,60,62,64,66
79 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79
106 8 2 2,8,10,16,18,24,26,32,34,40,42,48,50,56,58,64,66,72,74,80,82,88,90,96,
92,104,106
107 8 3 3,8,11,16,19,24,27,32,35,40,43,48,51,56,59,64,67,72,75,80,83,88,91,96,
99,104,107
132 8 4 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,104, 108,112,116,120,124,128,132
133 8 5 5,8,13,16,21,24,29,32,37,40,45,48,53,56,61,64,69,72,77,80,85,88,93,96,
101,104, 109,112,117,120,125,128,133
135 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79,80,87,88,95,96,
103,104, 111,112,119,120,127,128,135
160 16 16 16,32,48,64,80,96,112,128,144,160
216 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152,160,
168, 176,184,192,200,208,216
217 16 9 9,16,25,32,41,48,57,64,73,80,89,96,105,112,121,128,137,144,153,160,
169,176,185,192,201,208,217
264 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,160,168,
176,184,192,200,208,216,224,232,240,248,256,264
270 16 14 14,16,30,32,46,44,62,64,78,80,94,96,110,112, 126,128,142,144,158,
160,174, 176,190,192, 206,208,222,224,238,240, 254,256,270
273 16 1 1,16,17,32,33,48,49,64,65,80,81,96,97,112,113,128,129,144,145,160,
161,176,171, 192,193, 208,209, 224,225,240,241,256,257,272,273

Parameter Value Comment Condition
mcs-Table qam64
resourceAllocation dynamicSwitch pc_dynamicSwitchRA_Type0_1_PUSCH
pc_dynamicSwitchRA_Type0_1_PUSCH
AND Steps 1-5
AND pc_ra_Type0_PUSCH AND Steps 6-
10
NstartBWP 0
ETSI
ETSI
U-S Message
allowed values of N UL,BWP
1 to N RB in
3GPP TS 38.523-1 version PRB
16.9.0 Release 16 701 ETSI TS 138 523-1 V16.9.0 (2021-12)
BWP, time domain resource as per Table
7.1.1.4.2.0-1 and I MCS from 0 to 28.
nPRB.

TBS is less than or equal to UE capability
"Maximum number of UL-SCH transport
block bits received within a TTI" as specified
in Table 7.1.1.4.2.3.3.2-1 and larger than or
equal to 136 bits as specified in Table
7.1.1.4.2.3.3.2-2
Skip the execution of steps 2 to 5 for which

'
the value of N inf o satisfies the condition
'
3824 < N inf o < 3825.(Note 4)
Skip the execution of steps 1 to 5 for I MCS >
27 and N PRB < 5. (Note3)
2 SS creates one or more PDCP SDUs - - - -
depending on TBS in accordance with Table
7.1.1.4.2.3.3.2-2.
3 The SS transmits all PDCP SDUs (NSDUs) as <-- MAC PDU (NxPDCP SDUs) - -
created in step 2 in a MAC PDU.
4 After the reception of 2 Scheduling Request, <-- (UL Grant) (DCI: (DCI Format - -
SS transmits UL Grant DCI 0_1, and values 0_1, S, L, I MCS and nPRB.)
of S, L, I MCS and nPRB..
transmitted by the SS in step 3 using Time,
frequency Resources and modulation and
coding scheme as configured by the SS in
step 4?
- EXCEPTION : Steps 5Aa1 to 10 are - - - -
executed if pc_ra_Type0_PUSCH
executed if NOT
a1 message including PUSCH-Config with IE
(Note 2)
allowed values of N PRB as per table
resource length L 3 to 14-S and I MCS from 0
to 28.
nPRB.

capability "Maximum number of UL-SCH
in Table 7.1.1.4.2.3.3.2-2.

'
the value of N inf o satisfies the condition
'
3824 < N inf o < 3825. (Note 4)
Skip the execution of steps 6 to 10 for I MCS > ETSI
None.
256QAM / Transform precoding disabled
(1)
with { UE in RRC_CONNECTED state and mcs-Table is set as ‘qam256‘ }
ensure that {
}
(2)
with { UE in RRC_CONNECTED state and mcs-Table is set as ‘qam256‘ }
ensure that {
}
[TS 38.212, clause 7.3.1.1.2]
RNTI or SP-CSI-RNTI or new-RNTI:
- Carrier indicator – 0 or 3 bits, as defined in Subclause 10.1 of [5, TS38.213].
higher layers, excluding the initial UL bandwidth part. The bit width for this field is determined as
ETSI
UL,BWP
of the active UL bandwidth part:
[6, TS 38.214],
- log2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits if only resource allocation type 1 is configured, or
(
max log 2 ( N RB
UL, BWP UL, BWP
( N RB )
configured.
- If both resource allocation type 0 and 1 are configured, the MSB bit is used to indicate resource allocation type 0
or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1
indicates resource allocation type 1.
- For resource allocation type 0, the N RBG LSBs provide the resource allocation as defined in Subclause 6.1.2.2.1
of [6, TS 38.214].
- For resource allocation type 1, the log2 ( N RB

UL,BWP UL,BWP
follows:
- log2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits provides the frequency domain resource allocation according to
Subclause 6.1.2.2.2 of [6, TS 38.214]
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if both
allocation type 0 for the indicated bandwidth part if the bit width of the "Frequency domain resource
assignment" field of the active bandwidth part is smaller than the bit width of the "Frequency domain
width for this field is determined as log 2 ( I ) bits, where I the number of entries in the higher layer parameter
- 0 bit if only resource allocation type 0 is configured or if the higher layer parameter frequencyHopping is not
configured;
Subclause 6.3 of [6, TS 38.214].
- Modulation and coding scheme – 5 bits as defined in Subclause 6.1.4.1 of [6, TS 38.214]
ETSI
- 2nd downlink assignment index – 0 or 2 bits:
- 0 bit otherwise.
- TPC command for scheduled PUSCH – 2 bits as defined in Subclause 7.1.1 of [5, TS38.213]

  

  or
 log2 (NSRS) bits, where NSRS is the number of
  k =1  k  
configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value
'codeBook' or 'nonCodeBook', and LPUSCH
max
is the maximum number of supported layers for the PUSCH.
  min{Lmax , NSRS} N 
PUSCH
 SRS 
- log 

2

  
  bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter
k =1  k  
  
txConfig = nonCodebook, where NSRS is the number of configured SRS resources in the SRS resource set
associated with the higher layer parameter usage of value 'nonCodeBook';
- log2 (NSRS) bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook, where
NSRS is the number of configured SRS resources in the SRS resource set associated with the higher layer
parameter usage of value 'codeBook'.
values of higher layer parameters maxRank and codebookSubset;
values of higher layer parameters maxRank and codebookSubset.
- Antenna ports – number of bits determined by the following


ETSI


field if the higher layer parameter txConfig = codebook.
If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-

derived according to dmrs-UplinkForPUSCH-MappingTypeA and x B is the “Antenna ports” bit width derived
according to dmrs-UplinkForPUSCH-MappingTypeB. A number of xA − xB zeros are padded in the MSB of
this field, if the mapping type of the PUSCH corresponds to the smaller value of x A and x B .
- CSI request – 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSize.
- CBG transmission information (CBGTI) – 0, 2, 4, 6, or 8 bits determined by higher layer parameter

maxCodeBlockGroupsPerTransportBlock for PUSCH.
- 0 bit if PTRS-UplinkConfig is not configured and transformPrecoder=disabled, or if

transformPrecoder=enabled, or if maxRank=1;
PTRS port(s) and DMRS port(s) for transmission of one PT-RS port and two PT-RS ports respectively, and
the DMRS ports are indicated by the Antenna ports field.
“PTRS-DMRS association” field is present for the indicated bandwidth part but not present for the active
bandwidth part, the UE assumes the “PTRS-DMRS association” field is not present for the indicated
bandwidth part.
- beta_offset indicator – 0 if the higher layer parameter betaOffsets = semiStatic; otherwise 2 bits as defined by
Table 9.3-3 in [5, TS 38.213].
- DMRS sequence initialization – 0 if the higher layer parameter transformPrecoder=enabled; 1 bit if the higher
layer parameter transformPrecoder=disabled and both scramblingID0 and scramblingID1 are configured in
DMRS-UplinkConfig, for nSCID selection defined in Subclause 6.4.1.1.1.1 of [4, TS 38.211].
- UL-SCH indicator – 1 bit. A value of “1” indicates UL-SCH shall be transmitted on the PUSCH and a value of
“0” indicates UL-SCH shall not be transmitted on the PUSCH.
For a UE configured with SUL in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of
the cell and if the number of information bits in format 0_1 for the SUL is not equal to the number of information bits in
format 0_1 for the non-SUL, zeros shall be appended to smaller format 0_1 until the payload size equals that of the
larger format 0_1.
ETSI
Table 7.3.1.1.2-1: Bandwidth part indicator
Value of BWP indicator field

Bandwidth part
2 bits
00 First bandwidth part configured by higher layers
01 Second bandwidth part configured by higher layers
10 Third bandwidth part configured by higher layers
11 Fourth bandwidth part configured by higher layers
transformPrecoder=disabled and maxRank = 2 or 3 or 4
codebookSubset = codebookSubset = codebookSubset=
mapped mapped mapped
fullyAndPartialAndNonCoherent partialAndNonCoherent nonCoherent
to index to index to index
… … … … … …
… … … … … …
12 1 layer: TPMI=4 12 1 layer: TPMI=4 12-15 reserved
… … … …
… … … …
… …
… …
56 3 layers: TPMI=3
… …
59 3 layers: TPMI=6
60 4 layers: TPMI=3
61 4 layers: TPMI=4
62-63 reserved
ETSI
Table 7.3.1.1.2-3: Precoding information and number of layers for 4 antenna ports, if
transformPrecoder= enabled, or if transformPrecoder=disabled and maxRank = 1
codebookSubset = codebookSubset= codebookSubset=
mapped mapped mapped
fullyAndPartialAndNonCoherent partialAndNonCoherent nonCoherent
to index to index to index
… … … … … …
… … … …
12 1 layers: TPMI=12 12-15 reserved
… …
28-31 reserved
transformPrecoder=disabled and maxRank = 2
Bit field Bit field
codebookSubset = codebookSubset
mapped mapped
fullyAndPartialAndNonCoherent = nonCoherent
to index to index
3 1 layer: TPMI=2 3 reserved
4 1 layer: TPMI=3
5 1 layer: TPMI=4
6 1 layer: TPMI=5
7 2 layers: TPMI=1
8 2 layers: TPMI=2
9-15 reserved
transformPrecoder= enabled, or if transformPrecoder= disabled and maxRank = 1
Bit field Bit field

codebookSubset = codebookSubset
mapped mapped
fullyAndPartialAndNonCoherent = nonCoherent
to index to index
2 1 layer: TPMI=2
3 1 layer: TPMI=3
4 1 layer: TPMI=4
5 1 layer: TPMI=5
6-7 reserved
...
Table 7.3.1.1.2-33: VRB-to-PRB mapping
Bit field mapped to index VRB-to-PRB mapping

0 Non-interleaved
1 Interleaved
[TS 38.214, clause 6.1.2.1]
ETSI
block and a CSI report on PUSCH by a DCI, the Time domain resource assignment field value md of the DCI provides
a row index m + 1 to an allocated table. The determination of the used resource allocation table is defined in sub-clause
j
 2 μ PUSCH 
 2 μ PDCCH 
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and

Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
Type B {0,…,13} {1,…,14} {1,…,14} {0,…,12} {1,…,12} {1,…,12}

0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
ETSI
PUSCH transmission.
[38.214 clause 6.1.2.2]
[38.214 clause 6.1.2.2.1]
resource blocks defined by higher layer parameter rbg-Sizeconfigured for PUSCH and the size of the carrier bandwidth

Carrier Bandwidth Part Size Configuration 1 Configuration 2
1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
size
The total number of RBGs ( N RBG ) for a uplink carrier bandwidth part i of size N BWP, i PRBs is given by
(
N RBG = N BWP
size
( )) 
,i + N BWP,i mod P / P where
start

start
,i mod P ,
- size
the size of the last RBG is RBGlast (
= N BWP
start size
) ( start
)
,i + N BWP ,i mod P if N BWP ,i + N BWP ,i mod P > 0 and P otherwise.
size
- the size of all other RBG is P.
indexed in the order of increasing frequency of the carrier bandwidth part and starting at the lowest frequency. The
order of RBG bitmap is such that RBG 0 to RBG N RBG − 1 are mapped from 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.
[38.214 clause 6.1.2.2.2]
size
ETSI
size

size
/2  then
RIV = N BWP
size
else
RIV = N BWP
size size
size
− 1 − RBstart )

size
[TS 38.214, clause 6.1.4.1]
search space,
- else
ETSI
[TS 38.214, clause 5.1.3.1]

IMCS Qm efficiency
0 2 120 0.2344
1 2 193 0.3770
2 2 308 0.6016
3 2 449 0.8770
4 2 602 1.1758
5 4 378 1.4766
6 4 434 1.6953
7 4 490 1.9141
8 4 553 2.1602
9 4 616 2.4063
10 4 658 2.5703
11 6 466 2.7305
12 6 517 3.0293
13 6 567 3.3223
14 6 616 3.6094
15 6 666 3.9023
16 6 719 4.2129
17 6 772 4.5234
18 6 822 4.8164
19 6 873 5.1152
20 8 682.5 5.3320
21 8 711 5.5547
22 8 754 5.8906
23 8 797 6.2266
24 8 841 6.5703
25 8 885 6.9141
26 8 916.5 7.1602
27 8 948 7.4063
28 2 reserved
29 4 reserved
30 6 reserved
31 8 reserved
[TS 38.214, clause 6.1.4.2]
if
- '
- '
sh
− N DMRS
PRB
− N oh
PRB RB
sh
ETSI
PRB
PRB
PRB PRB
PRB

( '
)
else if
else
[TS 38.214, clause 5.1.3.2]
If N inf o ≤ 3824
else
end if
  N inf o  
o = max
'
24,2 n · n 
, where
  2 
n = max(3, log2 (N inf o ) − 6) .
'
ETSI

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
- if R ≤ 1 / 4
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  3816 
else
o > 8424
'
if N inf
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
ETSI
end if

within a TTI

(Note 1)
12129 ≤ TBS ≤24200 2 8*FLOOR((TBS – 200)/16)
24201 ≤ TBS ≤ 36272 3 8*FLOOR((TBS – 272)/24)
36273 ≤ TBS ≤48344 4 8*FLOOR((TBS – 344)/32)
48345≤ TBS ≤60416 5 8*FLOOR((TBS – 416)/40)
60417 ≤ TBS ≤ 72488 6 8*FLOOR((TBS –488)/48)
72489 ≤ TBS ≤84560 7 8*FLOOR((TBS – 560)/56)
84561 ≤ TBS ≤96632 8 8*FLOOR((TBS –632)/64)
96633< TBS ≤108704 9 8*FLOOR((TBS –704)/72)
10705 ≤ TBS ≤120776 10 8*FLOOR((TBS – 776)/80)
120777≤ TBS ≤132848 11 8*FLOOR((TBS –848)/88)
132849 ≤ TBS ≤ 144920 12 8*FLOOR((TBS – 920)/96)
TBS> 144920 13 8*FLOOR((TBS – 992)/104)
24.301 [21] clause 9.9.4.12).
This gives:
ETSI
BWP assumed as 0
DL,BWP
size
RBG
11 2 1 All 1…11
18 2 2 2,4,6,8,10,12,16,18
24 2 2 2,4,6,8,10,12,16,18,20,22,24
25 2 1 All 1…25
31 2 1 All 1…31
32 2 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32
38 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38
51 4 3 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 4 4 4,8,12,16,20,24,28,32,36,40,44,48,52
65 4 1 1,4,5,8,9,12,13,16,17,20,21,24,25,28,29,32,33,36,37,40,41,44,45,48,49,
52,53,56,57,60,61,64,65
66 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,
54,56,58,60,62,64,66
79 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79
106 8 2 2,8,10,16,18,24,26,32,34,40,42,48,50,56,58,64,66,72,74,80,82,88,90,96,
92,104,106
107 8 3 3,8,11,16,19,24,27,32,35,40,43,48,51,56,59,64,67,72,75,80,83,88,91,96,
99,104,107
132 8 4 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,104, 108,112,116,120,124,128,132
133 8 5 5,8,13,16,21,24,29,32,37,40,45,48,53,56,61,64,69,72,77,80,85,88,93,96,
101,104, 109,112,117,120,125,128,133
135 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79,80,87,88,95,96,
103,104, 111,112,119,120,127,128,135
160 16 16 16,32,48,64,80,96,112,128,144,160
216 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152,160,168,
176,184,192,200,208,216
217 16 9 9,16,25,32,41,48,57,64,73,80,89,96,105,112,121,128,137,144,153,160,169,
176,185,192,201,208,217
264 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,160,168,
176,184,192,200,208,216,224,232,240,248,256,264
270 16 14 14,16,30,32,46,44,62,64,78,80,94,96,110,112, 126,128,142,144,158,160,
174, 176,190,192, 206,208,222,224,238,240, 254,256,270
273 16 1 1,16,17,32,33,48,49,64,65,80,81,96,97,112,113,128,129,144,145,160,
161,176,171, 192,193, 208,209, 224,225,240,241,256,257,272,273

mcs-Table qam256
resourceAllocation dynamicSwitch pc_dynamicSwitchRA_Type0_1_PUSCH
AND Steps 1-5
AND pc_ra_Type0_PUSCH AND Steps
6-10
rbg-Size Not present configuration 1
applicable
NstartBWP 0
ETSI

U-S Message
DL,BWP
allowed values of N PRB 1 to N RB
in
BWP, time domain resource as per Table
7.1.1.4.2.0-1 and I MCS from 0 to 27.
nPRB.

7.1.1.4.2.4.3.2-2.
the TBS size equal to 3824 or 3840. (Note 3)
7.1.1.4.2.4.3.2-2.
3 After 300ms, the SS transmits all PDCP <-- MAC PDU (NxPDCP SDUs) - -
SDUs (NSDUs) as created in step 2 in a MAC
PDU.
4 After 60ms of step 3 SS transmits UL Grant <-- (UL Grant) (DCI: (DCI Format - -
DCI 0_1, and values of S, L, I MCS and nPRB.. 0_1, S, L, I MCS and nPRB.)
step 4?
- EXCEPTION : Steps 5Aa1 to 10 are - - - -
executed if pc_ra_Type0_PUSCH
executed if NOT
a1 message including PUSCH-Config with IE
(Note 2)
allowed values of N PRB as per Table
resource length L 3 to 14-S and I MCS from 0
to 27.
nPRB.
ETSI

7.1.1.4.2.4.3.2-2.
the TBS size equal to 3824 or 3840. (Note 3)
7.1.1.4.2.4.3.2-2.
8 After 300ms, the SS transmits all PDCP <-- MAC PDU (NxPDCP SDUs) - -
SDUs (NSDUs) as created in step 7 in a MAC
PDU.
9 After 60ms of step 8 SS transmits UL Grant <-- (UL Grant) (DCI: (DCI Format - -
DCI 0_1, and values of S, L, I MCS and nPRB.. 0_1, S, L, I MCS and nPRB.)
step 4?
[15].
[None].
7.1.1.4.2.5 UL-SCH Transport Block Size selection / DCI format 0_0 / Transform precoding and
64QAM
(1)
with { UE in RRC_CONNECTED state and transform precoding enabled}
ensure that {
assignment and modulation and coding }
}
38.214 clause 6.1.2.1, 6.1.2.2, 6.1.2.2.2, 6.1.4.1, 5.1.3.1, 6.1.4.2 and 5.1.3.2. Unless otherwise stated these are Rel-15
requirements.
[TS 38.212, clause 7.3.1.1.1]
RNTI or new-RNTI:
ETSI

UL, BWP UL, BWP
( N RB + 1) / 2)  bits where
UL,BWP
- N RB is the size of the active UL bandwidth part in case DCI format 0_0 is monitored in the UE specific
- otherwise, N RB
UL, BWP is the size of the initial UL bandwidth part.
- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2)  bits provides the frequency domain resource allocation according to
Subclause 6.1.2.2.2 of [6, TS 38.214]
- Modulation and coding scheme – 5 bits as defined in Subclause 6.1.3 of [6, TS 38.214]
- UL/SUL indicator – 1 bit for UEs configured with SUL in the cell as defined in Table 7.3.1.1.1-1 and the
number of bits for DCI format 1_0 before padding is larger than the number of bits for DCI format 0_0 before
padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0_0,
after the padding bit(s).
- If the UL/SUL indicator is present in DCI format 0_0 and the higher layer parameter pusch-Config is not
configured on both UL and SUL the UE ignores the UL/SUL indicator field in DCI format 0_0, and the
corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer
parameter pucch-Config is configured;
- If the UL/SUL indicator is not present in DCI format 0_0, the corresponding PUSCH scheduled by the DCI
format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured.
The following information is transmitted by means of the DCI format 0_0 with CRC scrambled by TC-RNTI:
ETSI

UL, BWP UL, BWP
( N RB + 1) / 2)  bits where
UL,BWP
- N RB is the size of the initial UL bandwidth part.
where N UL_hop = 1 if N RB
UL, BWP
< 50 and N UL_hop = 2 otherwise
- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2)  bits provides the frequency domain resource allocation according to
Subclause 6.1.2.2.2 of [6, TS 38.214]
- Modulation and coding scheme – 5 bits as defined in Subclause 6.1.3 of [6, TS 38.214], using Table 5.1.3.1-1
- New data indicator – 1 bit, reserved
- HARQ process number – 4 bits, reserved
- UL/SUL indicator – 1 bit if the cell has two ULs and the number of bits for DCI format 1_0 before padding is
larger than the number of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if
present, locates in the last bit position of DCI format 0_0, after the padding bit(s).
- If 1 bit, reserved, and the corresponding PUSCH is always on the same UL carrier as the previous
transmission of the same TB
prior to padding is less than the payload size of the DCI format 1_0 monitored in common search space for scheduling
the same serving cell, zeros shall be appended to the DCI format 0_0 until the payload size equals that of the DCI
format 1_0.
prior to padding is larger than the payload size of the DCI format 1_0 monitored in common search space for
scheduling the same serving cell, the bit width of the frequency domain resource allocation field in the DCI format 0_0
is reduced by truncating the first few most significant bits such that the size of DCI format 0_0 equals to the size of the
DCI format 1_0.
format 1_0 monitored in common search space for scheduling the same serving cell, zeros shall be appended to the DCI
format 0_0 until the payload size equals that of the DCI format 1_0.
ETSI
and if the number of information bits in the DCI format 0_0 prior to padding is larger than the payload size of the DCI
format 1_0 monitored in common search space for scheduling the same serving cell, the bit width of the frequency
domain resource allocation field in the DCI format 0_0 is reduced by truncating the first few most significant bits such
that the size of DCI format 0_0 equals to the size of the DCI format 1_0.
If DCI format 0_0 is monitored in UE specific search space and satisfies both of the following
format 1_0 monitored in UE specific search space for scheduling the same serving cell, zeros shall be appended to the
DCI format 0_0 until the payload size equals that of the DCI format 1_0.
[TS 38.214, clause 6.1.2.1]
Reporting Settings. The ith codepoint of K2 s determined as K 2 = max Y j where Y j (i ) is the ith codepoint of Y j .
j
 2 μ PUSCH 
μ PDCCH

 2 

if
( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤ 14 − S , and
ETSI

Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
Type B {0,…,13} {1,…,14} {1,…,14} {0,…,12} {1,…,12} {1,…,12}

0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
PUSCH transmission.
[38.214 clause 6.1.2.2]
[38.214 clause 6.1.2.2.2]
n uplink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set of
size
size
ETSI

size
/2  then
RIV = N BWP
size
else
RIV = N BWP
size size
size
− 1 − RBstart )

size
[TS 38.214, clause 6.1.4.1]
...
else
- if mcs-TableTransformPrecoder in PUSCH-Config is set to 'qam256', and the PUSCH is scheduled with C-RNTI
or SP-CSI-RNTI, and PUSCH is assigned by DCI format 0_1,
- the UE shall use IMCS and Table 5.1.3.1.-2 to determine the modulation order (Qm) and Target code rate (R)
- elseif the UE is not configured with new-RNTI, mcs-TableTransformPrecoder in PUSCH-Config is set to

'qam64LowSE', and the PUSCH is scheduled with C-RNTI, or SP-CSI-RNTI, and the PUSCH is assigned by a
PDCCH in a UE-specific search space,
- elseif mcs-TableTransformPrecoder in ConfiguredGrantConfig is set to 'qam256', and PUSCH is scheduled with

CS-RNTI,
- elseif mcs-TableTransformPrecoder in ConfiguredGrantConfig is set to 'qam64LowSE', and PUSCH is

scheduled with CS-RNTI,
- else
- the UE shall use IMCS and Table 6.1.4.1-1to determine the modulation order (Qm) and Target code rate (R)
ETSI
end
For Table 6.1.4.1-1 and Table 6.1.4.1-2, if higher layer parameter PUSCH-tp-pi2BPSK is configured, q = 1 otherwise
q=2.
Table 6.1.4.1-1: MCS index table for PUSCH with transform precoding and 64QAM
MCS Index Modulation Order Target code Rate R x 1024 Spectral
IMCS Qm efficiency
0 q 240/ q 0.2344
1 q 314/ q 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 466 2.7305
18 6 517 3.0293
19 6 567 3.3223
20 6 616 3.6094
21 6 666 3.9023
22 6 719 4.2129
23 6 772 4.5234
24 6 822 4.8164
25 6 873 5.1152
26 6 910 5.3320
27 6 948 5.5547
28 q reserved
29 2 reserved
30 4 reserved
31 6 reserved
[TS 38.214, clause 6.1.4.2]
if
- '
ETSI
- '
sh
− N DMRS
PRB
− N oh
PRB RB
sh
PRB
PRB
PRB PRB
PRB

( '
)
else if
else
[TS 38.214, clause 5.1.3.2]
If N inf o ≤ 3824
else
end if
  N inf o  
o = max
'
24,2 n · n 
, where
  2 
n = max(3, log2 (N inf o ) − 6) .
'
ETSI

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
- if R ≤ 1 / 4
N' + 24  N'
inf o + 24

TBS = 8· C·   − 24 , where C = 
inf o



8· C 
  3816 
else
o > 8424
'
if N inf
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C 
  8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
ETSI
end if

ETSI
(Note 1)
12129 ≤ TBS ≤24200 2 8*FLOOR((TBS – 200)/16)
24201 ≤ TBS ≤ 36272 3 8*FLOOR((TBS – 272)/24)
36273 ≤ TBS ≤48344 4 8*FLOOR((TBS – 344)/32)
48345≤ TBS ≤60416 5 8*FLOOR((TBS – 416)/40)
60417 ≤ TBS ≤ 72488 6 8*FLOOR((TBS –488)/48)
72489 ≤ TBS ≤84560 7 8*FLOOR((TBS – 560)/56)
84561 ≤ TBS ≤96632 8 8*FLOOR((TBS –632)/64)
96633< TBS ≤108704 9 8*FLOOR((TBS –704)/72)
10705 ≤ TBS ≤120776 10 8*FLOOR((TBS – 776)/80)
120777≤ TBS ≤132848 11 8*FLOOR((TBS –848)/88)
132849 ≤ TBS ≤ 144920 12 8*FLOOR((TBS – 920)/96)
144921 ≤ TBS ≤ 156992 13 8*FLOOR((TBS – 992)/104)
156993 ≤ TBS ≤ 169064 14 8*FLOOR((TBS – 1064)/112)
169065 ≤ TBS ≤ 181136 15 8*FLOOR((TBS – 1136)/120)
181137 ≤ TBS ≤ 193208 16 8*FLOOR((TBS – 1208)/128)
193209 ≤ TBS ≤ 205280 17 8*FLOOR((TBS – 1280)/136)
205281 ≤ TBS ≤ 217352 18 8*FLOOR((TBS – 1352)/144)
217353 ≤ TBS ≤ 229424 19 8*FLOOR((TBS – 1424)/152)
TBS> 229424 20 8*FLOOR((TBS – 1496)/160)
24.301 [21] clause 9.9.4.12).
This gives:

transformPrecoder enabled
ETSI

U-S Message
N PRB 1 to N RB
UL,BWP
in BWP, time
7.1.1.4.2.0-1 and I MCS from 0 to
27.
7.1.1.4.2.5.3.2-1 and larger than
Table 7.1.1.4.2.5.3.2-2
3824 or 3840. (Note 1)
for I MCS > 27 and N PRB < 5.
(Note2)
7.1.1.4.2.5.3.2-2.
3 The SS transmits all PDCP SDUs <-- MAC PDU (NxPDCP - -
(NSDUs) as created in step 2 in a SDUs)
MAC PDU.
4 After the reception of 2 <-- (UL Grant) (DCI Format - -
Scheduling Request , SS 0_0, S, L, I MCS and nPRB.)
transmits UL Grant DCI 0_0, and
values of S, L, I MCS and nPRB.
[15].
Note 2: For I MCS > 27 and N PRB < 5, the resulting TBS is very small leading to CRC errors in decoding UL
data.
None.
ETSI
7.1.1.4.2.6 UL-SCH Transport Block Size selection / DCI format 0_2
(1)
ensure that {
assignment and modulation and coding}
}
[TS 38.212, clause 7.3.1.1.3]
RNTI or SP-CSI-RNTI or MCS-C-RNTI:
- Carrier indicator – 0, 1, 2 or 3 bits determined by higher layer parameter carrierIndicatorSizeDCI-0-2, as defined

in Clause 10.1 of [5, TS38.213].
- UL/SUL indicator – 0 bit for UEs not configured with supplementaryUplink in ServingCellConfig in the cell or
UEs configured with supplementaryUplink in ServingCellConfig in the cell but only one carrier in the cell is
configured for PUSCH transmission; otherwise, 1 bit as defined in Table 7.3.1.1.1-1.
- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of UL BWPs configured by

higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as
bits, where
- if , in which case the bandwidth part indicator is equivalent to the

ascending order of the higher layer parameter BWP-Id;
- otherwise , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
- Frequency domain resource assignment – number of bits determined by the following:
- bits if only resource allocation type 0 is configured, where is defined in Clause 6.1.2.2.1 of [6, TS
38.214]
- bits if only resource allocation type 1 is configured, or

bits if resourceAllocationDCI-0-2-r16 is configured as
'dynamicSwitch', where is the size of the active
UL bandwidth part, is defined as in clause 4.4.4.4 of [4, TS 38.211] and is given by higher layer
parameter resourceAllocationType1GranularityDCI-0-2. If the higher layer parameter
resourceAllocationType1GranularityDCI-0-2 is not configured, is equal to 1.
- If resourceAllocationDCI-0-2-r16 is configured as 'dynamicSwitch', the MSB bit is used to indicate resource

allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0
and the bit value of 1 indicates resource allocation type 1.
ETSI
- For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 6.1.2.2.1
of [6, TS 38.214].
- For resource allocation type 1, the LSBs provide the resource allocation as
follows:
- MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214],
where if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2 contains two
offset values and if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2
contains four offset values
- bits provide the frequency domain resource allocation

according to Clause 6.1.2.2.2 of [6, TS 38.214]
- bits provide the frequency domain resource allocation according to

Clause 6.1.2.2.2 of [6, TS 38.214]
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if
resourceAllocationDCI-0-2-r16 is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE
assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain
resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain
- Time domain resource assignment – 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause 6.1.2.1 of [6, TS38.214]. The
bitwidth for this field is determined as bits, where I is the number of entries in the higher layer
parameter pusch-TimeDomainAllocationListDCI-0-2 if the higher layer parameter is configured, or I is the
number of entries in the higher layer parameter PUSCH-TimeDomainResourceAllocationList if the higher layer
parameter PUSCH-TimeDomainResourceAllocationList is configured and the higher layer parameter pusch-
TimeDomainAllocationListDCI-0-2 is not configured; otherwise I is the number of entries in the default table.
- 0 bit if the higher layer parameter frequencyHoppingDCI-0-2 is not configured;
Clause 6.3 of [6, TS 38.214].
- Modulation and coding scheme –5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]
- Redundancy version – 0, 1 or 2 bits determined by higher layer parameter numberOfBitsForRV-DCI-0-2
- If 0 bit is configured, rvid to be applied is 0;
- 1 bit according to Table 7.3.1.2.3-1;
- 2 bits according to Table 7.3.1.1.1-2.
- HARQ process number – 0, 1, 2, 3 or 4 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-

0-2
- Downlink assignment index – 0, 1, 2 or 4 bits
- 0 bit if the higher layer parameter downlinkAssignmentIndexDCI-0-2 is not configured;
- 1, 2 or 4 bits otherwise,
ETSI
- 2nd downlink assignment index – 0 or 2 bits
- 0 bit otherwise.
When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter
priorityIndicatorDCI-0-2 is configured, if the bit width of the Downlink assignment index in DCI format 0_2 for
one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 0_2 for the
other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller
Downlink assignment index until the bit width of the Downlink assignment index in DCI format 0_2 for the two
HARQ-ACK codebooks are the same.
- TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

  

k
  or

bits, where is the number of
  k =1   
configured SRS resources in the SRS resource set configured by higher layer parameter srs-
ResourceSetToAddModListDCI-0-2, and associated with the higher layer parameter usage of value 'codeBook' or
'nonCodeBook',
  min{Lmax , N SRS }  NSRS  

- log2 
  

k
  bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter


  k =1   
txConfig = nonCodebook, where is the number of configured SRS resources in the SRS resource set
configured by higher layer parameter srs-ResourceSetToAddModListDCI-0-2, and associated with the higher
layer parameter usage of value 'nonCodeBook' and
- if UE supports operation with maxMIMO-LayersDCI-0-2 and the higher layer parameter maxMIMO-
LayersDCI-0-2 of PUSCH-ServingCellConfig of the serving cell is configured, Lmax is given by that
parameter
- otherwise, Lmax is given by the maximum number of layers for PUSCH supported by the UE for the
serving cell for non-codebook based operation.
- bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook, where
is the number of configured SRS resources in the SRS resource set configured by higher layer parameter
srs-ResourceSetToAddModListDCI-0-2, and associated with the higher layer parameter usage of value
'codeBook'.
- 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and
according to whether transform precoder is enabled or disabled, and the values of higher layer parameters
maxRankDCI-0-2, and codebookSubsetDCI-0-2;
- 4 or 5 bits according to Table 7.3.1.1.2-2A for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=2,
transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;
- 4 or 6 bits according to Table 7.3.1.1.2-2B for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=3 or 4,
transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;
- 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if txConfig = codebook, ul-
ETSI
maxRankDCI-0-2 and codebookSubsetDCI-0-2;
- 3 or 4 bits according to Table 7.3.1.1.2-3A for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform
precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2;
- 2 or 4 bits according to Table7.3.1.1.2-4 for 2 antenna ports, if txConfig = codebook, ul-

- 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, transform precoder is disabled, the maxRankDCI-0-2=2, and
codebookSubsetDCI-0-2=nonCoherent;
- 1 or 3 bits according to Table7.3.1.1.2-5 for 2 antenna ports, if txConfig = codebook, ul-

- 2 bits according to Table 7.3.1.1.2-5A for 2 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform
precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2.
For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to fullpowerMode2,

the values of higher layer parameters maxRankDCI-0-2 is configured to be larger than 2, and at least one SRS
resource with 4 antenna ports is configured in an SRS resource set with usage set to 'codebook' and an SRS
resource with 2 antenna ports is indicated via SRI in the same SRS resource set, then Table 7.3.1.1.2-4 is used.
For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna
ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource
among the configured SRS resources in an SRS resource set with usage set to 'codebook'. If the number of ports for
a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the
configured SRS resources, a number of most significant bits with value set to '0' are inserted to the field.
- Antenna ports – number of bits determined by the following:
- 0 bit if higher layer parameter antennaPortsFieldPresenceDCI-0-2 is not configured;
- 2, 3, 4, or 5 bits otherwise,
- 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, dmrs-Type=1, and maxLength=1,
except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2 BPSK
modulation is used;
- 2 bits as defined by 7.3.1.1.2-6A, if transform precoder is enabled, and dmrs-UplinkTransformPrecoding

and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-Type=1, and maxLength=1,
where nSCID is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, in [4, TS38.211];
- 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, dmrs-Type=1, and maxLength=2,
except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2 BPSK
modulation is used;
- 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled, and dmrs-

UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-
Type=1, and maxLength=2, where nSCID is the scrambling identity for antenna ports defined in Clause
6.4.1.1.1.2, in [4, TS38.211];
- 3 bits as defined by Tables 7.3.1.1.2-8/9/10/11, if transform precoder is disabled, dmrs-Type=1, and

maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the
higher layer parameter txConfig = nonCodebook and according to the Precoding information and number
of layers field if the higher layer parameter txConfig = codebook;
ETSI



of layers field if the higher layer parameter txConfig = codebook.
If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 and dmrs-UplinkForPUSCH-

MappingTypeB-DCI-0-2 and is configured with antennaPortsFieldPresenceDCI-0-2, the bitwidth of this field
equals , where is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-
MappingTypeA-DCI-0-2 and is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-
MappingTypeB-DCI-0-2. A number of zeros are padded in the MSB of this field, if the mapping type
of the PUSCH corresponds to the smaller value of and .
If a UE is not configured with higher layer parameter antennaPortsFieldPresenceDCI-0-2, antenna port(s) are
defined assuming bit field index value 0 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23.
- SRS request – 0, 1, 2 or 3 bits
- 0 bit if the higher layer parameter srs-RequestDCI-0-2 is not configured;
- 1 bit as defined by Table 7.3.1.1.3-1 if higher layer parameter srs-RequestDCI-0-2 = 1 and for UEs not
configured with supplementaryUplink in ServingCellConfig in the cell;
- 2 bits if higher layer parameter srs-RequestDCI-0-2 = 1 and for UEs configured with supplementaryUplink in
ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-
1 and the second bit is defined by Table 7.3.1.1.3-1;
- 2 bits as defined by Table 7.3.1.1.2-24 if higher layer parameter srs-RequestDCI-0-2 = 2 and for UEs not
configured with supplementaryUplink in ServingCellConfig in the cell;
- 3 bits if higher layer parameter srs-RequestDCI-0-2 = 2 and for UEs configured with supplementaryUplink in
ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-
1 and the second and third bits are defined by Table 7.3.1.1.2-24;
- CSI request – 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSizeDCI-0-2.
- 0 bit if PTRS-UplinkConfig is not configured in either dmrs-UplinkForPUSCH-MappingTypeA or dmrs-

UplinkForPUSCH-MappingTypeB and transform precoder is disabled, or if transform precoder is enabled, or
if maxRankDCI-0-2=1;
PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured by
maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports
field.
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the
"PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active
bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth
part.
ETSI
- beta_offset indicator – 0 bit if the higher layer parameter betaOffsets = semiStatic; otherwise 1 bit if 2 offset
indexes are configured by higher layer parameter dynamicDCI-0-2 as defined by Table 9.3-3A in [5, TS 38.213],
and 2 bits if 4 offset indexes are configured by higher layer parameter dynamicDCI-0-2 as defined by Table 9.3-
3 in [5, TS 38.213].
When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter
priorityIndicatorDCI-0-2 is configured, if the bit width of the beta_offset indicator in DCI format 0_2 for one
HARQ-ACK codebook is not equal to that of the beta_offset indicator in DCI format 0_2 for the other HARQ-
ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller beta_offset
indicator until the bit width of the beta_offset indicator in DCI format 0_2 for the two HARQ-ACK codebooks
are the same.
- DMRS sequence initialization – 0 or 1 bit
- 0 bit if the higher layer parameter dmrs-SequenceInitializationDCI-0-2 is not configured or if transform

precoder is enabled;
- 1 bit if transform precoder is disabled and the higher layer parameter dmrs-SequenceInitializationDCI-0-2 is
configured.
- UL-SCH indicator – 1 bit. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of
"0" indicates UL-SCH shall not be transmitted on the PUSCH. Except for DCI format 0_2 with CRC scrambled
by SP-CSI-RNTI, a UE is not expected to receive a DCI format 0_2 with UL-SCH indicator of "0" and CSI
request of all zero(s).
- Open-loop power control parameter set indication – 0 or 1 or 2 bits.
- 0 bit if the higher layer parameter p0-PUSCH-SetList is not configured;
- 1 or 2 bits otherwise,
- 1 bit if SRS resource indicator is present in the DCI format 0_2;
- 1 or 2 bits as determined by higher layer parameter olpc-ParameterSetDCI-0-2 if SRS resource indicator

is not present in the DCI format 0_2;
- Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-0-2 is not configured; otherwise 1 bit as
defined in Clause 9 in [5, TS 38.213].
- Invalid symbol pattern indicator – 0 bit if higher layer parameter invalidSymbolPatternIndicatorDCI-0-2 is not
configured; otherwise 1 bit as defined in Clause 6.1.2.1 in [6, TS 38.214].
A UE does not expect that the bit width of a field in DCI format 0_2 with CRC scrambled by CS-RNTI is larger than
corresponding bit width of same field in DCI format 0_2 with CRC scrambled by C-RNTI for the same serving cell. If
the bit width of a field in the DCI format 0_2 with CRC scrambled by CS-RNTI is not equal to that of the
corresponding field in the DCI format 0_2 with CRC scrambled by C-RNTI for the same serving cell, a number of most
significant bits with value set to '0' are inserted to the field in DCI format 0_2 with CRC scrambled by CS-RNTI until
the bit width equals that of the corresponding field in the DCI format 0_2 with CRC scrambled by C-RNTI for the same
serving cell.
Table 7.3.1.1.3-1: 1 bit SRS request in DCI format 0_2 and DCI format 1_2
Value of SRS request Triggered aperiodic SRS resource

field set(s) for DCI format 0_2 and 1_2
No aperiodic SRS resource set
0
triggered
SRS resource set(s) configured with
higher layer parameter aperiodicSRS-
1 ResourceTrigger set to 1 or an entry in
aperiodicSRS-ResourceTriggerList set
to 1
[TS 38.214, clause 6.1.2.1]
ETSI
block and a CSI report(s) on PUSCH by a DCI, the 'Time domain resource assignment' field value m of the DCI
provides a row index m + 1 to an allocated table. The determination of the used resource allocation table is defined in
Clause 6.1.2.1.1. The indexed row defines the slot offset K2, the start and length indicator SLIV, or directly the start
symbol S and the allocation length L, the PUSCH mapping type, and the number of repetitions (if numberOfRepetitions
is present in the resource allocation table) to be applied in the PUSCH transmission.
When the UE is scheduled to transmit a PUSCH with no transport block and with a CSI report(s) by a 'CSI request' field
on a DCI, the 'Time domain resource assignment' field value m of the DCI provides a row index m + 1 to the allocated
table as defined in Clause 6.1.2.1.1. The indexed row defines the start and length indicator SLIV, or directly the start
symbol S and the allocation length L, and the PUSCH mapping type to be applied in the PUSCH transmission and the
K2 value is determined as K2 = max Yj ( m + 1) , where Y j , j = 0 ,..., N Rep − 1 are the corresponding list entries of the
j
higher layer parameter
- reportSlotOffsetListDCI-0-2, if PUSCH is scheduled by DCI format 0_2 and reportSlotOffsetListDCI-0-2 is

configured;
- reportSlotOffsetListDCI-0-1, if PUSCH is scheduled by DCI format 0_1 and reportSlotOffsetListDCI-0-1 is

configured;
- reportSlotOffsetList, otherwise;
in CSI-ReportConfig for the N Rep triggered CSI Reporting Settings and Y j ( m + 1 ) is the (m+1)th entry of Y j .
- The slot Ks where the UE shall transmit the PUSCH is determined by K2 as Ks

   CA CA  
2 μPUSCH N slot , offset , PDCCH N slot ,offset , PUSCH
= n ⋅  + K2 +  −  ⋅ 2 μPUSCH  , if UE is configured with ca-SlotOffset for
 2 μPDCCH   2
μoffset , PDCCH
2
μoffset ,PUSCH  
  
 2 μPUSCH 
at least one of the scheduled and scheduling cell, Ks =  n ⋅  + K2 , otherwise, and where n is the slot with
 2 μPDCCH 
the scheduling DCI, K2 is based on the numerology of PUSCH, and μPUSCH and μ PDCCH are the subcarrier
spacing configurations for PUSCH and PDCCH, respectively,
- and are the and the μ offset , respectively, which are determined by higher-
layer configured ca-SlotOffset for the cell receiving the PDCCH, and are the
and the μ offset ,respectively, which are determined by higher-layer configured ca-SlotOffset for the cell
transmitting the PUSCH, as defined in clause 4.5 of [4, TS 38.211], and
- for PUSCH scheduled by DCI format 0_1, if pusch-RepTypeIndicatorDCI-0-1 is set to 'pusch-RepTypeB', the
UE applies PUSCH repetition Type B procedure when determining the time domain resource allocation. For
PUSCH scheduled by DCI format 0_2, if pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeB', the UE
applies PUSCH repetition Type B procedure when determining the time domain resource allocation. Otherwise,
the UE applies PUSCH repetition Type A procedure when determining the time domain resource allocation for
PUSCH scheduled by PDCCH.
- For PUSCH repetition Type A, the starting symbol S relative to the start of the slot, and the number of
consecutive symbols L counting from the symbol S allocated for the PUSCH are determined from the start and
length indicator SLIV of the indexed row:
if ( L − 1) ≤ 7 then
SLIV = 14 ⋅ ( L − 1) + S
else
SLIV = 14 ⋅ (14 − L + 1) + (14 − 1 − S )
where 0 < L ≤14− S , and
ETSI
- For PUSCH repetition Type B, the starting symbol S relative to the start of the slot, and the number of
consecutive symbols L counting from the symbol S allocated for the PUSCH are provided by startSymbol and
length of the indexed row of the resource allocation table, respectively.
- For PUSCH repetition Type A, the PUSCH mapping type is set to Type A or Type B as defined in Clause
6.4.1.1.3 of [4, TS 38.211] as given by the indexed row.
- For PUSCH repetition Type B, the PUSCH mapping type is set to Type B.

Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
(repetition Type
A only)
Type B {0,…,13} {1,…,14} {1,…,14} for {0,…, 11} {1,…,12} {1,…,12} for
repetition Type A, repetition Type A,
{1,…,27} for {1,…,23} for
repetition Type B repetition Type B
For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCI format 0_1 or 0_2 in PDCCH with CRC
scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, the number of repetitions K is determined as
- if numberOfRepetitions is present in the resource allocation table, the number of repetitions K is equal to
numberOfRepetitions;
- elseif the UE is configured with pusch-AggregationFactor, the number of repetitions K is equal to pusch-
AggregationFactor;
- otherwise K=1.
If a UE is configured with higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH, the UE does not

expect to be configured with pusch-AggregationFactor.
For PUSCH repetition Type A, in case K>1, the same symbol allocation is applied across the K consecutive slots and
the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the K consecutive slots applying
the same symbol allocation in each slot. The redundancy version to be applied on the nth transmission occasion of the
TB, where n = 0, 1, … K-1, is determined according to table 6.1.2.1-2.
Table 6.1.2.1-2: Redundancy version for PUSCH transmission

rvid indicated by the DCI rvid to be applied to nth transmission occasion (repetition Type A) or nth
scheduling the PUSCH actual repetition (repetition Type B)
n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3
0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
[38.214 clause 6.1.2.2]
detected PDCCH DCI except for a PUSCH transmission scheduled by a RAR UL grant or fallbackRAR UL grant, in
which case the frequency domain resource allocation is determined according to clause 8.3 of [6, 38.213] or a MsgA
PUSCH transmission with frequency domain resource allocation determined according to clause 8.1A of [6, 38.213].
Three uplink resource allocation schemes type 0, type 1 and type 2 are supported. Uplink resource allocation scheme
ETSI
type 0 is supported for PUSCH only when transform precoding is disabled. Uplink resource allocation scheme type 1
and type 2 are supported for PUSCH for both cases when transform precoding is enabled or disabled.
If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the 'Frequency domain
resource' assignment field by setting a higher layer parameter resourceAllocation in pusch-Config to 'dynamicSwitch',
for DCI format 0_1 or setting a higher layer parameter resourceAllocationDCI-0-2 in pusch-Config to 'dynamicSwitch'
for DCI format 0_2, the UE shall use uplink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise
the UE shall use the uplink frequency resource allocation type as defined by the higher layer parameter
resourceAllocation for DCI format 0_1 or the higher layer parameter resourceAllocationDCI-0-2 for DCI format 0_2.
The UE shall assume that when the scheduling PDCCH is received with DCI format 0_1 and useInterlacePUCCH-
PUSCH in BWP-UplinkDedicated is configured, uplink type 2 resource allocation is used.
allocation type 1 is used, except when any of the higher layer parameters useInterlacePUCCH-PUSCH in BWP-
UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured in which case uplink
resource allocation type 2 is used.
The UE expects that either none or both of useInterlacePUCCH-PUSCH in BWP-UplinkCommon and

useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured.
If a bandwidth part indicator field is not configured in the scheduling DCI or the UE does not support active bandwidth
part change via DCI, the RB indexing for uplink type 0, type 1 and type 2 resource allocation is determined within the
UE's active bandwidth part. If a bandwidth part indicator field is configured in the scheduling DCI and the UE supports
active bandwidth part change via DCI, the RB indexing for uplink type 0, type 1, type 2 resource allocation is
determined within the UE's bandwidth part indicated by bandwidth part indicator field value in the DCI. The UE shall
upon detection of PDCCH intended for the UE determine first the uplink bandwidth part and then the resource
allocation within the bandwidth part. RB numbering starts from the lowest RB in the determined uplink bandwidth part.
[38.214 clause 6.1.2.2.1]
resource blocks defined by higher layer parameter rbg-Size configured in pusch-Config and the size of the bandwidth

1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
[38.214 clause 6.1.2.2.2]
size
contiguously allocated non-interleaved virtual resource blocks within the active bandwidth part of size NBWP PRBs
except for the case when DCI format 0_0 is decoded in any common search space in which case the size of the initial
size
UL bandwidth part NBW P,0 shall be used.

if ( LRBs − 1) ≤ N BWP / 2
size
 then
RIV = N BWP
size
( L RBs − 1) + RB start
else
ETSI
RIV = N BWP
size size
( N BWP − L RBs + 1) + ( N BWP
size
− 1 − RB start )
where L RBs ≥ 1 and shall not exceed NBWP− RBstart.

size
initial
When the DCI size for DCI format 0_0 in USS is derived from the initial UL BWP with size N BW P
but applied to
active
another active BWP with size of N B W P , an uplink type 1 resource block assignment field consists of a resource
K
indication value (RIV) corresponding to a starting resource block RB start = 0, K , 2 ⋅ K , , ( N BW P − 1) ⋅ K
initial
and a length in
K
terms of virtually contiguously allocated resource blocks L RBs = K , 2 ⋅ K , , N BW P ⋅ K .
initial
The resource indication value is defined by
if (L 'RBs −1) ≤  NBWP / 2 then

initial
RIV = N BWP
initial
( L ' RBs − 1) + RB ' start
else
RIV = N BWP
initial initial
( N BWP − L ' RBs + 1) + ( N BWP
initial
− 1 − RB 'start )
where L ' RBs = LRBs K , RB 'start = RBstart K and where L 'RBs shall not exceed N BWP
initial
− RB ' start .
, K is the maximum value from set {1, 2, 4, 8} which satisfies K ≤  NBWP / NBWP  ; otherwise K = 1.
active initial
W P > N BW P
If N Bactive initial
When the scheduling grant is received with DCI format 0_2, an uplink type 1 resource allocation field consists of a
resource indication value (RIV) corresponding to a starting resource block group RBGstart=0, 1, …, NRBG-1 and a length
in terms of virtually contiguously allocated resource block groups LRBGs=1, …, NRBG, where the resource block groups
are defined as in 6.1.2.2.1 with P defined by resourceAllocationType1GranularityDCI-0-2 if the UE is configured with
higher layer parameter resourceAllocationType1GranularityDCI-0-2, and P=1 otherwise. The resource indication value
is defined by
if (LRBGs −1) ≤  NRBG / 2 then
RIV = N RBG ( L RBGs − 1) + RBG start
else
RIV = N RBG ( N RBG − L RBGs + 1) + ( N RBG − 1 − RBG start )
where LRBGs ≥ 1 and shall not exceed N RBG − RBGstart .
[TS 38.214, clause 6.1.4.1]
For a PUSCH scheduled by RAR UL grant or
for a PUSCH scheduled by a fallbackRAR UL grant or
for a MsgA PUSCH transmission, or
for a PUSCH scheduled by a DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or
for a PUSCH scheduled by a DCI format 0_1 or DCI format 0_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-
RNTI, SP-CSI-RNTI, or
for a PUSCH with configured grant using CS-RNTI, and
if transform precoding is disabled for this PUSCH transmission according to Clause 6.1.3
- if mcs-TableDCI-0-2 in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format
0_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI,
ETSI
used in the physical uplink shared channel;
- elseif the UE is not configured with MCS-C-RNTI, mcs-TableDCI-0-2 in pusch-Config is set to 'qam64LowSE',
and the PUSCH is scheduled by a PDCCH by a PDCCH with DCI format 0_2 with CRC scrambled by C-RNTI
or SP-CSI-RNTI,
[TS 38.214, clause 5.1.3.1]

MCS Index Modulation Order Spectral
Target code Rate R x [1024]
IMCS Qm efficiency
0 2 30 0.0586
1 2 40 0.0781
2 2 50 0.0977
3 2 64 0.1250
4 2 78 0.1523
5 2 99 0.1934
6 2 120 0.2344
7 2 157 0.3066
8 2 193 0.3770
9 2 251 0.4902
10 2 308 0.6016
11 2 379 0.7402
12 2 449 0.8770
13 2 526 1.0273
14 2 602 1.1758
15 4 340 1.3281
16 4 378 1.4766
17 4 434 1.6953
18 4 490 1.9141
19 4 553 2.1602
20 4 616 2.4063
21 6 438 2.5664
22 6 466 2.7305
23 6 517 3.0293
24 6 567 3.3223
25 6 616 3.6094
26 6 666 3.9023
27 6 719 4.2129
28 6 772 4.5234
29 2 reserved
30 4 reserved
31 6 reserved
[TS 38.214, clause 6.1.4.2]
For a PUSCH scheduled by RAR UL grant or
for a PUSCH scheduled by fallbackRAR UL grant or
for a PUSCH scheduled by a DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or
for a PUSCH scheduled by a DCI format 0_1 or DCI format 0_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-
RNTI, or
for a PUSCH transmission with configured grant, or
for a MsgA PUSCH transmission,
if
ETSI
- A UE first determines the number of REs allocated for PUSCH within a PRB (N RE
'
) by
-
'
NRE = Nsc
RB sh
· Nsymb − NDMRS
PRB
− Noh
PRB
, where N scRB = 12 is the number of subcarriers in the frequency domain
sh
in a physical resource block, N symb is the number of symbols L of the PUSCH allocation according to
PRB
Clause 6.1.2.1 for scheduled PUSCH or Clause 6.1.2.3 for configured PUSCH, N DMRS is the number of REs
for DM-RS per PRB in the allocated duration including the overhead of the DM-RS CDM groups without
data, as described for PUSCH with a configured grant in Clause 6.1.2.3 or as indicated by DCI format 0_1 or
PRB
DCI format 0_2 or as described for DCI format 0_0 in Clause 6.2.2, and Noh is the overhead configured
PRB
by higher layer parameter xOverhead in PUSCH-ServingCellConfig. If the Noh is not configured (a value
PRB PRB
from 6, 12, or 18), the Noh is assumed to be 0. For Msg3 or MsgA PUSCH transmission the Noh is
PRB
always set to 0. In case of PUSCH repetition Type B, N DMRS is determined assuming a nominal repetition
with the duration of L symbols without segmentation.
- A UE determines the total number of REs allocated for PUSCH (N ) by

RE
NRE = min ( '
156, NRE )⋅nPRB where n PRB is the total number of allocated PRBs for the UE.
- Next, proceed with steps 2-4 as defined in Clause 5.1.3.2
- For a PUSCH scheduled by fallbackRAR UL grant, UE assumes the TB size determined by the UL grant in
the fallbackRAR shall be the same as the TB size used in the corresponding MsgA PUSCH transmission.
else if
initial PUSCH for the same transport block is transmitted with configured grant,
- the TBS shall be determined from configuredGrantConfig for a configured grant Type 1 PUSCH.
- the TBS shall be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH.
else
initial PUSCH for the same transport block is transmitted with configured grant,
- the TBS shall be determined from configuredGrantConfig for a configured grant Type 1 PUSCH.
- the TBS shall be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH.
[TS 38.214, clause 5.1.3.2]
2) Unquantized intermediate variable (Ninfo) is obtained by N inf o = N RE · R·Q m ·υ .
ETSI
If N inf o ≤ 3824
else
end if
 n  N inf o  
quantized intermediate number of information bits Ninf o = max 24,2 ·
'
- 
n  , where
  2 
n = max (3, log 2 (N inf o ) − 6 ) .
'

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
  Ninf o − 24  
  2 
n
n = log 2 (N inf o − 24 ) − 5 and ties in the round function are broken towards the next largest integer.
- if R ≤ 1/ 4
ETSI
N' + 24  N' + 24

TBS = 8· C·  inf o  − 24 , where C = 
inf o



8· C   3816 
else
'
if N inf o > 8424
N' + 24  N'
inf o + 24

 − 24 , where C =  


8· C  
8424 
else
N' + 24 
TBS = 8·  inf o
 − 24


8 

end if
end if
Test frequency NRf1 is as specified in TS 38.508-1 [4] clause 4.3.1 using the common highest UL and DL channel
bandwidth and using the default subcarrier spacing specified in TS 38.508-1 [4] clause 6.2.3.1.

ETSI
(Note 1)
12129 ≤ TBS ≤24200 2 8*FLOOR((TBS – 200)/16)
24201 ≤ TBS ≤ 36272 3 8*FLOOR((TBS – 272)/24)
36273 ≤ TBS ≤48344 4 8*FLOOR((TBS – 344)/32)
48345≤ TBS ≤60416 5 8*FLOOR((TBS – 416)/40)
60417 ≤ TBS ≤ 72488 6 8*FLOOR((TBS –488)/48)
72489 ≤ TBS ≤84560 7 8*FLOOR((TBS – 560)/56)
84561 ≤ TBS ≤96632 8 8*FLOOR((TBS –632)/64)
96633< TBS ≤108704 9 8*FLOOR((TBS –704)/72)
10705 ≤ TBS ≤120776 10 8*FLOOR((TBS – 776)/80)
120777≤ TBS ≤132848 11 8*FLOOR((TBS –848)/88)
132849 ≤ TBS ≤ 144920 12 8*FLOOR((TBS – 920)/96)
TBS> 144920 13 8*FLOOR((TBS – 992)/104)
24.301 [21] clause 9.9.4.12).
This gives:
ETSI
Table 7.1.1.4.2.6.3.2-2A: Bandwidth part Dependent Parameters for RBG’s with start of BWP assumed
as 0
DL,BWP
size
RBG
11 2 1 All 1…11
18 2 2 2,4,6,8,10,12,16,18
24 2 2 2,4,6,8,10,12,16,18,20,22,24
25 2 1 All 1…25
31 2 1 All 1…31
32 2 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32
38 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38
51 4 3 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 4 4 4,8,12,16,20,24,28,32,36,40,44,48,52
65 4 1 1,4,5,8,9,12,13,16,17,20,21,24,25,28,29,32,33,36,37,40,41,44,45,48,49,
52,53,56,57,60,61,64,65
66 4 2 2,4,6,8,10,12,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,
54,56,58,60,62,64,66
79 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79
106 8 2 2,8,10,16,18,24,26,32,34,40,42,48,50,56,58,64,66,72,74,80,82,88,90,96,
92,104,106
107 8 3 3,8,11,16,19,24,27,32,35,40,43,48,51,56,59,64,67,72,75,80,83,88,91,96,
99,104,107
132 8 4 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,104, 108,112,116,120,124,128,132
133 8 5 5,8,13,16,21,24,29,32,37,40,45,48,53,56,61,64,69,72,77,80,85,88,93,96,
101,104, 109,112,117,120,125,128,133
135 8 7 7,8,15,16,23,24,31,32,39,40,47,48,55,56,63,64,71,72,79,80,87,88,95,96,
103,104, 111,112,119,120,127,128,135
160 16 16 16,32,48,64,80,96,112,128,144,160
216 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152,160,
168, 176,184,192,200,208,216
217 16 9 9,16,25,32,41,48,57,64,73,80,89,96,105,112,121,128,137,144,153,160,
169,176,185,192,201,208,217
264 16 8 8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,160,168,
176,184,192,200,208,216,224,232,240,248,256,264
270 16 14 14,16,30,32,46,44,62,64,78,80,94,96,110,112, 126,128,142,144,158,
160,174, 176,190,192, 206,208,222,224,238,240, 254,256,270
273 16 1 1,16,17,32,33,48,49,64,65,80,81,96,97,112,113,128,129,144,145,160,
161,176,171, 192,193, 208,209, 224,225,240,241,256,257,272,273

mcs-TableDCI-0-2-r16 qam64LowSE
resourceAllocationDCI-0- resourceAllocationType1
2-r16
NstartBWP 0
ETSI

U-S Message
N PRB 1 to N RB
UL,BWP
as per table
7.1.1.4.2.6.3.2-2A in BWP, time
7.1.1.4.2.0-1 and I MCS from 0 to
28.
Skip the execution of steps for

= 28 and < 4.
(Note 1)
7.1.1.4.2.6.3.2-1 and larger than
Table 7.1.1.4.2.6.3.2-2.
3824 or 3840. (Note 2)
7.1.1.4.2.6.3.2-2.
3 After 300ms, the SS transmits all <-- MAC PDU (NxPDCP - -
PDCP SDUs (NSDUs) as created in SDUs)
step 2 in a MAC PDU.
4 After 60ms of step 3, SS transmits <-- (UL Grant) (DCI Format - -
UL Grant DCI 0_0, and values of 0_0, S, L, I MCS and nPRB.)
S, L, I MCS and nPRB..
Note 1: For = 28 and < 4, the resulting TBS is very small leading to CRC errors in decoding UL
data.
[15].
None.
ETSI
7.1.1.5 Discontinuous reception
7.1.1.5.0 DRX Common Definitions

FirstSlot is the First DL Slot in the subframe, which is 0 for both FDD and TDD as per default configuration in
38.5081-1[4] TDD-UL-DL-Config Table 4.6.3-192
LastDLSlot is the Last DL Slot in a frame; for FDD numerology =0 it is slot 9, numerology=1 it is slot 19,
numerology=2 it is slot 39. For TDD as per default configuration in 38.5081-1[4] TDD-UL-DL-Config Table 4.6.3-
192, for numerology =0, it is slot 7, numerology=1 it is slot 16, numerology=3 it is slot 77
LastULSlot is the Last UL Slot in a frame; for FDD/TDD numerology =0 it is slot 9, numerology=1 it is slot
18(Second Last as 2 Consecutive UL Slots), numerology=3 it is slot 79; the PDCCH for UL grant is sent K2= 4 Slot
earlier.
7.1.1.5.1 DRX operation / Short cycle not configured / Parameters configured by RRC
(1)
ensure that {
when { Long DRX cycle is configured and [(SFN * 10) + subframe number] modulo (drx-LongCycle) =
drx-StartOffset }
then { UE starts the OnDurationTimer and monitors the PDCCH for OnDurationTimer PDCCH-Occasions}
}
(2)
ensure that {
when { Long DRX cycle is configured and a new DL transmission is indicated on the PDCCH during
Active Time }
then { UE starts or restarts the Drx-InactivityTimer and monitors the PDCCH for Drx-
InactivityTimer PDCCH occasions starting from the next PDCCH occasion of the PDCCH occasion 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 PDCCH Occasion and the
data in the soft buffer of the corresponding HARQ process was not successfully decoded }
then { UE starts the drx-RetransmissionTimer-DL for the corresponding HARQ process and monitors
the PDCCH for drx-RetransmissionTimer consecutive PDCCH Occasion }
}
(4)
ensure that {
when { Long DRX cycle is configured and an uplink grant for a pending HARQ retransmission can
occur in this PDCCH occasion}
then { UE monitors the PDCCH in this PDCCH occasion }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.321, clause 5.7. Unless
[TS 38.321, clause 5.7]
The MAC entity may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring. .
Activity for the MAC entity's C-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-
ETSI
PUSCH-RNTI, and TPC-SRS-RNTI. When using DRX operation, the MAC entity shall also monitor PDCCH
according to requirements found in other subclauses of this specification. When in RRC_CONNECTED, if DRX is
configured, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this
subclause; otherwise the MAC entity shall monitor the PDCCH continuously.
RRC controls DRX operation by configuring the following timers:
- drx-onDurationTimer: the duration at the beginning of a DRX Cycle;
- drx-SlotOffset: the delay before starting the drx-onDurationTimer;
- drx-InactivityTimer: the duration after the PDCCH occasion in which a PDCCH indicates an new UL or DL
transmission for the MAC entity;
- drx-RetransmissionTimerDL (per DL HARQ process): the maximum duration until a DL retransmission is

received;
- drx-RetransmissionTimerUL (per UL HARQ process): the maximum duration until a grant for UL
retransmission is received;
- drx-LongCycle StartOffset: the Long DRX cycle and drx-StartOffset which defines the subframe where the Long
and Short DRX Cycle starts;
- drx-ShortCycle (optional): the Short DRX cycle;
- drx-ShortCycleTimer (optional): the duration the UE shall follow the Short DRX cycle;
- drx-HARQ-RTT-TimerDL (per DL HARQ process): the minimum duration before a DL assignment for HARQ
retransmission is expected by the MAC entity;
- drx-HARQ-RTT-TimerUL (per UL HARQ process): the minimum duration before a UL HARQ retransmission
grant is expected by the MAC entity.
When a DRX cycle is configured, the Active Time includes the time while:
- drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or

ra-ContentionResolutionTimer (as described in subclause 5.1.5) is running; or
- a Scheduling Request is sent on PUCCH and is pending (as described in subclause 5.4.4); or
- a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after
successful reception of a Random Access Response for the random access preamble not selected by the MAC
entity among the contention-based Random Access Preamble (as described in subclause 5.1.4).
When DRX is configured, the MAC entity shall:
1> if a MAC PDU is received in a configured downlink assignment:
2> start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of
the corresponding transmission carrying the DL HARQ feedback;
2> stop the drx-RetransmissionTimerDL for the corresponding HARQ process.
1> if a MAC PDU is transmitted in a configured uplink grant:
2> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of
the first repetition of the corresponding PUSCH transmission;
2> stop the drx-RetransmissionTimerUL for the corresponding HARQ process.
1> if a drx-HARQ-RTT-TimerDL expires:
2> if the data of the corresponding HARQ process was not successfully decoded:
3> start the drx-RetransmissionTimerDL for the corresponding HARQ process.
1> if an drx-HARQ-RTT-TimerUL expires:
ETSI
2> start the drx-RetransmissionTimerUL for the corresponding HARQ process.
1> if a DRX Command MAC CE or a Long DRX Command MAC CE is received:
2> stop drx-onDurationTimer;
2> stop drx-InactivityTimer.
1> if drx-InactivityTimer expires or a DRX Command MAC CE is received:
2> if the Short DRX cycle is configured:
3> start or restart drx-ShortCycleTimer in the first symbol after the expiry of drx-HARQ-RTT-TimerDL.;
3> use the Short DRX Cycle.
2> else:
3> use the Long DRX cycle.
1> if drx-ShortCycleTimer expires:
1> if a Long DRX Command MAC CE is received:
2> stop drx-ShortCycleTimer;
1> if the Short DRX Cycle is used, and [(SFN x 10) + subframe number] modulo (drx-ShortCycle) = (drx-
StartOffset) modulo (drx-ShortCycle); or
1> if the Long DRX Cycle is used, and [(SFN x 10) + subframe number] modulo (drx-LongCycle) = drx-
StartOffset:
2> if drx-SlotOffset is configured:
3> start drx-onDurationTimer after drx-SlotOffset from the beginning of the subframe.
2> else:
3> start drx-onDurationTimer.
1> if the MAC entity is in Active Time:
2> monitor the PDCCH;
2> if the PDCCH indicates a DL transmission or if a DL assignment has been configured:
3> start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process immediately after the
corresponding PUCCH transmission;
2> if the PDCCH indicates a UL transmission or if a UL grant has been configured:
3> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process immediately after the first
repetition of the corresponding PUSCH transmission;
2> if the PDCCH indicates a new transmission (DL or UL):
3> start or restart drx-InactivityTimer.
1> else (i.e. not part of the Active Time):
2> not report CQI/PMI/RI on PUCCH.
ETSI
ETSI

U-S Message
1 SS transmits RRCReconfiguration to configure <-- - - -
specific DRX parameters. (Note 6)
2 The UE transmits --> - - -
3 In the first PDCCH occasion when the Drx- <-- MAC PDU - -
onDurationTimer is running, the SS indicates
the transmission of a DL MAC PDU on the
PDCCH.
4 Check: Does the UE transmit a HARQ ACK for --> HARQ ACK 1 P
the DL MAC PDU in Step 3?
5 At least drx-InactivityTimer PDCCH occasions <-- MAC PDU - -
after the transmission of the MAC PDU in Step
3 has been indicated (This means the next
DRX cycle or later after Step 2) in the last
PDCCH occasion while the drx-
onDurationTimer is still running, the SS
indicates the transmission a DL MAC PDU on
the PDDCH. (Note 4).
7 drx-InactivityTimer PDCCH-occasions after the <-- MAC PDU - -
transmission of the MAC PDU transmitted in
step 5 was indicated on the PDCCH, the SS
indicates the transmission of a DL MAC PDU
on the PDCCH. (Note 4)
9 At least drx-InactivityTimer PDCCH occasions <-- Invalid MAC PDU - -
after the transmission of the MAC PDU in Step
7 has been indicated (This means the next
DRX cycle or later after Step 5) and in the last
PDCCH occasion before the Drx-
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)
for the DL MAC PDU in Step 9?
11 In the first PDCCH occasion when the Drx- <-- MAC PDU - -
RetransmissionTimerDL for the MAC PDU in
Step 9 is started (i.e. after expiry of drx-HARQ-
RTT-TimerDL after step 9), the SS indicates
PDCCH.
13 At least drx-InactivityTimer PDCCH occasions <-- Invalid MAC PDU - -
after the transmission of the DL MAC PDU in
Step 11 has been indicated (This means the
next DRX cycle or later after Step 11) and last
PDCCH occasion before the Drx-
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)
ETSI
15 In the last PDCCH occasion when the drx- <-- MAC PDU - -
RetransmissionTimerDL for MAC PDU in Step
13 is still running, the SS indicates the
PDCCH.
17 The SS is configured for Uplink Grant <-- UL grant on PDCCH - -
Allocation Type [0]. At least drx-InactivityTimer
PDCCH subframes after the transmission of
the DL MAC PDU in Step 15 has been
indicated in the last PDCCH occasion when
the onDuratiopnTimer is still running (This
means the next DRX cycle or later after Step
9), the SS indicates an UL grant to the UE on
the PDCCH. (Note 4)
18 Check: Does the UE transmit a Buffer Status --> Buffer Status Report MAC control 1 P
Report on the UL indicating an empty buffer? element
RetransmissionTimer-UL for MAC PDU from
Step 17 is still running, the SS indicates the
PDCCH.
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 PDCCH occasions is 0. These timers are: drx-
InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL and drx-
HARQ-RTT-TimerUL.
Note 4: The drx-InactivityTimer is started in the next PDCCH occasion of the PDCCH occasion where DL new
transmission is indicated.
Note 5: The timer values expressed in number of slots.

radioBearerConfig RadioBearerConfig NR
}
nonCriticalExtension::= SEQUENCE { NR
}
}
}
ETSI

cellGroupConfig ::= SEQUENCE {
drx-Config CHOICE {
setup SEQUENCE {
drx-onDurationTimer ms20
drx-InactivityTimer ms10
drx-HARQ-RTT-TimerDL 56 Number of slots=4 μ =0,1,2,3,
due to number of
4 ( 2 with
symbol per
normal CP)
slot=14
48 Number of slots=4 μ = 2 with
due to number of
external CP
symbol per
slot=12
drx-HARQ-RTT-TimerUL 56 Number of slots=4 μ =0,1,2,3,
due to number of
4 ( 2 with
symbol per
normal CP)
slot=14
due to number of
external CP
symbol per
slot=12
drx-RetransmissionTimerDL sl8
drx-RetransmissionTimerUL sl8
drx-LongCycleStartOffset CHOICE {
ms640 7
}
shortDRX Not present
drx-SlotOffset ms0
}
}
}
}
7.1.1.5.2 DRX operation / Short cycle not configured / Long DRX command MAC control
element reception
(1)
with { UE in CONNECTED mode }
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 {
ETSI
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 }
}
[TS 38.321, clause 5.7]
The MAC entity may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring.
Activity for the MAC entity's C-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-
RRC controls DRX operation by configuring the following timers:
- drx-InactivityTimer: the duration after the PDCCH occasion in which a PDCCH indicates a new UL or DL

received;
- drx-LongCycle StartOffset: the Long DRX cycle and drx-StartOffset which defines the subframe where the Long

successful reception of a Random Access Response for the random access preamble not selected by the MAC
ETSI
3> start the drx-RetransmissionTimerDL for the corresponding HARQ process.
1> if an drx-HARQ-RTT-TimerUL expires:
2> start the drx-RetransmissionTimerUL for the corresponding HARQ process.
3> start or restart drx-ShortCycleTimer in the first symbol after the expiry of drx-HARQ-RTT-TimerDL.;
2> else:
1> if the Short DRX Cycle is used, and [(SFN x 10) + subframe number] modulo (drx-ShortCycle) = (drx-
1> if the Long DRX Cycle is used, and [(SFN x 10) + subframe number] modulo (drx-LongCycle) = drx-
StartOffset:
2> if drx-SlotOffset is configured:
3> start drx-onDurationTimer after drx-SlotOffset from the beginning of the subframe..
2> else:
3> start drx-onDurationTimer.
2> if the PDCCH indicates a DL transmission or if a DL assignment has been configured:
3> start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process immediately after the
corresponding PUCCH transmission;
ETSI
2> if the PDCCH indicates a UL transmission or if a UL grant has been configured:
3> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process immediately after the first
repetition of the corresponding PUSCH transmission;
3> start or restart drx-InactivityTimer.
1> else (i.e. not part of the Active Time):
2> not report CQI/PMI/RI on PUCCH.
For FDD, NormalSLT(current SFN,current sub-frame, current slot,y)=y; For TDD, NormalSLT(current SFN, current
slot,y) counts the minimum number of normal slots needed to cover y number of PDCCH-occasions(slots) until next
PDCCH-occasion(slot) available, starting from current slot on current SFN.
ETSI

U-S Message
1 SS transmits RRCReconfiguration to configure <-- - - -
specific DRX parameters. (Note 5)
2 The UE transmits --> - - -
3 In a PDCCH occasion which is X PDCCH sub <-- MAC PDU - -
frames before the PDCCH occasion in which
the onDurationTimer expires, with X < drx-
onDurationTimer, the SS indicates the
PDCCH. The SS transmits an MAC PDU.
5 In a PDCCH occasion before the drx- <-- MAC PDU(DRX MAC Control - -
onDurationTimer expires, the SS indicates the element)
PDCCH. The SS transmits a DL MAC PDU
with DRX MAC Control element.
UE successfully decodes the MAC PDU and
starts the long DRX cycle.
6 Check: Does the UE transmit a HARQ ACK? --> HARQ ACK 1 P
6A In a PDCCH occasion before the Long DRX <-- MAC PDU
cycle ends, the SS indicates the transmission
of a DL MAC PDU on the PDCCH. The SS
transmits a DL MAC PDU
6B Check: Does the UE transmit a HARQ ACK? --> HARQ ACK 1 F
7 On the next or later DRX cycle than the one <-- MAC PDU - -
used for Step 3 and on a PDCCH occasion
which is X PDCCH sub frames before the
PDCCH occasion in which the
onDurationTimer expires, with X < drx-
onDurationTimer,the SS indicates the
transmission of a DL MAC PDU. The SS
transmits an invalid MAC PDU. (Note 1)
8 Check: Does the UE transmit a HARQ NACK? --> HARQ NACK - P
8A In a PDCCH occasion before the Drx-HARQ- <-- MAC PDU(DRX MAC Control - -
RTT-TimerDL for the MAC PDU indicated in element)
Step 7 expires, the SS indicates the
8B Check: Does the UE transmit a HARQ ACK? --> HARQ ACK 2,3 P
9 In a PDCCH occasion when the drx- <-- MAC PDU(DRX MAC Control - -
RetransmissionTimer for the MAC PDU element)
indicated in Step 7 is still running,, the SS
indicates the transmission of a DL MAC PDU.
The SS transmits a DL MAC PDU with DRX
MAC Control element.
10 Check: Does the UE transmit a HARQ ACK? --> HARQ ACK 2,3 P
11 In the last sub frame when the Drx- <-- MAC PDU - -
RetransmissionTimer for the DL MAC PDU
indicated on the PDCCH in Step 7 is still
running, the SS indicates the transmission of a
DL MAC PDU.
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 PDCCH occasions(slots). These timers are:
drx-InactivityTimer, drx-RetransmissionTimer, Drx-HARQ-RTT-TimerDL.
RRCConnectionReconfigurationComplete
ETSI

}
}
}
}

drx-Config CHOICE {
setup SEQUENCE {
drx-HARQ-RTT-TimerDL 56 Number of slots=4 μ =0,1,2,3,
due to number of
4 ( 2 with
symbol per
normal CP)
slot=14
due to number of
external CP
symbol per
slot=12
drx-HARQ-RTT-TimerUL 56 Number of slots=4 μ =0,1,2,3,
due to number of
4 ( 2 with
symbol per
normal CP)
slot=14
due to number of
external CP
symbol per
slot=12
ms640 7
}
drx-SlotOffset ms0
}
}
}
}
ETSI
7.1.1.5.3 DRX operation / Short cycle configured / Parameters configured by RRC
(1)
ensure that {
when { Short DRX cycle and drx-SlotOffset is configured and [(SFN * 10) + subframe number] modulo
drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle) }
then { UE starts the OnDurationTimer after drx-SlotOffset and monitors the PDCCH for
OnDurationTimer PDCCH-subframes }
}
(2)
ensure that {
when { drxShortCycleTimer is expired and [(SFN * 10) + subframe number] modulo (drx-LongCycle) =
drx-StartOffset: }
then { UE starts the OnDurationTimer after drx-SlotOffset and monitors the PDCCH for
OnDurationTimer PDCCH-subframes }
}
Editor’s Note: The conformance requirements are based on running RAN2 CR
References: The conformance requirements covered in the present test case are specified in: TS 38.321, clause 5.7.
[TS 38.321, clause 5.7]
The MAC entity may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring
activity for the MAC entity's C-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-
according to requirements found in other subclauses of this specification..When in RRC_CONNECTED, if DRX is
RRC controls DRX operation by configuring the following parameters:

received;
- drx-LongCycleStartOffset: the Long DRX cycle and drx-StartOffset which defines the subframe where the Long
ETSI

successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC
3> start or restart drx-ShortCycleTimer in the first symbol after the expiry of drx-InactivityTimer or in the
first symbol after the end of DRX Command MAC CE reception;
2> else:
1> if the Short DRX Cycle is used, and [(SFN × 10) + subframe number] modulo (drx-ShortCycle) = (drx-
1> if the Long DRX Cycle is used, and [(SFN × 10) + subframe number] modulo (drx-LongCycle) = drx-
StartOffset:
For FDD, NormalSLT (current SFN, current sub-frame, current slot, y) = y; For TDD, NormalSLT (current SFN, current
slot, y) counts the minimum number of normal slots needed to cover y number of PDCCH-occasions(slots) until next
PDCCH-occasion(slot) available, starting from current slot on current Subframe.
ETSI

U–S Message
1 SS transmits NR RRCReconfiguration <-- - - -
message to configure specific DRX
parameters for SpCell (Note1)
2 The UE transmitNR --> - - -
RRCReconfigurationComplete messages
(Note 2)
3 In the first PDCCH occasion, after the drx- <-- MAC PDU - -
SlotOffset when the drx-onDurationTimer is
running, the SS indicates the transmission of a
DL MAC PDU on the PDCCH. (Note 3)(Note 4)
4 Check: Does the UE transmit a HARQ ACK for --> HARQ ACK - -
5 At least drx-InactivityTimer after the <-- MAC PDU - -
transmission of the MAC PDU in Step 3 has
been indicated (This means the next DRX
cycle or later after Step 1) in the last PDCCH
occasion while the drx-onDurationTimer is still
running according to [(SFN * 10) + subframe
number] modulo drx-ShortCycle) = (drx-
StartOffset) modulo (drx-ShortCycle)), the SS
indicates the transmission a DL MAC PDU on
the PDDCH.
7 SS waits for drx-ShortCycleTimer to expire. - - - -
8 In the first PDCCH occasion after the drx- <-- MAC PDU - -
SlotOffset when the drx-onDurationTimer of
drx-LongCycle is running, the SS indicates the
PDCCH.
Note 3: The drx-InactivityTimer is started in the first symbol after the end of the PDCCH reception where DL new
Note 4: When the drx-InactivityTimer expires, UE starts drx-ShortCycleTimer in the first symbol after the expiry of
drx-InactivityTimer.

}
}
}
}
ETSI

drx-Config CHOICE {
setup SEQUENCE {
drx-InactivityTimer Ms10
drx-HARQ-RTT-TimerDL 56
drx-HARQ-RTT-TimerUL 56
ms640 7
}
shortDRX SEQUENCE {
drx-ShortCycle Ms80
drx-ShortCycleTimer 7
}
drx-SlotOffset ms0
}
}
}
}
7.1.1.5.4 DRX operation / Short cycle configured / DRX command MAC control element
reception
(1)
ensure that {
when { Short DRX cycle is configured and a DRX Command MAC control element is received }
}
(2)
ensure that {
when { Short 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 { Short DRX cycle is configured and the drx-RetransmissionTimer-DL is running and a DRX
Command MAC control element is received }
then { UE continues running the drx-RetransmissionTimer-DL and monitors the PDCCH }
}
[TS 38.321, clause 5.7]
ETSI
The MAC entity may be configured by RRC with a DRX functionality that controls the UE's PDCCH monitoring
configured, for all the activated Serving Cells, the MAC entity may monitor the PDCCH discontinuously using the
DRX operation specified in this subclause; otherwise the MAC entity shall monitor the PDCCH continuously.
- drx-RetransmissionTimerDL (per DL HARQ process except for the broadcast process): the maximum duration
until a DL retransmission is received;
- drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): the minimum duration
before a DL assignment for HARQ retransmission is expected by the MAC entity;

ETSI
3> start the drx-RetransmissionTimerDL for the corresponding HARQ process in the first symbol after the
expiry of drx-HARQ-RTT-TimerDL.
1> if a drx-HARQ-RTT-TimerUL expires:
2> start the drx-RetransmissionTimerUL for the corresponding HARQ process in the first symbol after the
expiry of drx-HARQ-RTT-TimerUL.
2> else:
StartOffset:
2> if the PDCCH indicates a DL transmission:
3> start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end
of the corresponding transmission carrying the DL HARQ feedback;
2> if the PDCCH indicates a UL transmission:
3> start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end
of the first repetition of the corresponding PUSCH transmission;
3> start or restart drx-InactivityTimer in the first symbol after the end of the PDCCH reception.
ETSI
1> in current symbol n, if the MAC entity would not be in Active Time considering grants/assignments/DRX
Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent 4 ms prior to
symbol n when evaluating all DRX Active Time conditions as specified in this subclause:
2> not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 [7].
1> if CSI masking (csi-Mask) is setup by upper layers:
2> in current symbol n, if onDurationTimer would not be running considering grants/assignments/DRX

Command MAC CE/Long DRX Command MAC CE received 4 ms prior to symbol n when evaluating all
DRX Active Time conditions as specified in this subclause:
3> not report CSI on PUCCH.
1> else:
Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent 4 ms prior to
symbol n when evaluating all DRX Active Time conditions as specified in this subclause:
3> not report CSI on PUCCH and semi-persistent CSI on PUSCH.
Regardless of whether the MAC entity is monitoring PDCCH or not, the MAC entity transmits HARQ feedback,
aperiodic CSI on PUSCH, and aperiodic SRS defined in TS 38.214 [7] when such is expected.
The MAC entity needs not to monitor the PDCCH if it is not a complete PDCCH occasion (e.g. the Active Time starts
or ends in the middle of a PDCCH occasion).
For FDD, NormalSLT(current SFN, current subframe, current slot, y)=y; For TDD, NormalSLT(current SFN, current
subframe, current slot, y) counts the minimum number of normal slots needed to cover y number of PDCCH-occasions
(slots) until next PDCCH-occasion (slot) available, starting from current slot on current SFN.
ETSI

U-S Message
1 SS transmits NR <-- NR RRC: RRCReconfiguration - -
specific DRX parameters for NR Cell. (Note
1)
2 The UE transmits NR --> NR RRC: - -
RRCReconfigurationComplete message. RRCReconfigurationComplete
(Note 2)
3 In a PDCCH occasion which is X subframes <-- MAC PDU - -
before the PDCCH occasion in which the
drx-onDurationTimer expires,
with X < drx-onDurationTimer-1, the SS
on the PDCCH. (Note 7)
4 Check: Does the UE transmit a HARQ ACK --> HARQ ACK 1 P
5 In a PDCCH occasion before the drx- <-- MAC PDU (DRX MAC Control - -
onDurationTimer expires, the SS indicates element)
with DRX MAC Control element. UE
successfully decodes the MAC PDU.
6 In a PDCCH occasion before the short DRX <-- MAC PDU
A cycle ends, the SS indicates the
6 Check: Does the UE transmit a HARQ ACK --> HARQ ACK 1 F
B in step 6B?
7 On the next or later DRX cycle than the one <-- MAC PDU - -
used for Step 3 and on a PDCCH occasion
which is X PDCCH sub frames before the
PDCCH occasion in which the
onDurationTimer expires, with X < drx-
onDurationTimer, the SS indicates the
transmission of a DL MAC PDU. The SS
transmits an invalid MAC PDU. (Note 3)
8 Check: Does the UE transmit a HARQ NACK --> HARQ NACK 2,3 P
8 In a PDCCH occasion before the Drx-HARQ- <-- MAC PDU(DRX MAC Control
A RTT-TimerDL for the MAC PDU indicated in element)
Step 7 expires, the SS indicates the
B
9 In a PDCCH occasion which is Z slots before <-- MAC PDU(DRX MAC Control - -
the slot in which the drx- element)
RetransmissionTimerDL for the DL MAC
PDU in Step 7 expires, with 1 <Z< drx-
RetransmissionTimerDL, the SS indicates
the transmission of a DL MAC PDU. The SS
transmits a DL MAC PDU with DRX MAC
Control element.
10 Check: Does the UE transmit a HARQ ACK --> HARQ ACK 2,3,1 P
RetransmissionTimerDL for the DL MAC
PDU indicated on the PDCCH in Step 7 is
still running, the SS indicates the
transmission of a DL MAC PDU.
12 Check: Does the UE transmit a HARQ ACK --> HARQ ACK 2,3 P
ETSI

Note 5: Timer tolerances for the MAC DRX related timers measured in PDCCH occasions (slots). These timers are:
Note 6: K is the time for given PDSCH to HARQ feedback of PUCCH and shall be shorter than drx-InactivityTimer. In
this TC, the DCI format should be configured to not include the PDSCH-to-HARQ-timing-indicator field. When
the UE schedules a PDSCH reception over a number of symbols where the last symbol is within slot n-k, the
UE shall provide corresponding HARQ-ACK information in a PUCCH transmission within slot n-k+4
according to TS 38.321 clause 9.2.3. Thus, the maximum value of K is 4 slots in this test case.
Note 7: The SS assumes that the UE starts in long DRX after configuration.
Table 7.1.1.5.4.3.3-1: RRCReconfiguration (Step 1, Table 7.1.1.5.4.3.2-1)

(CONTAINING
CellGroupConfig)
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI
Derivation Path: 38.508-1 [4], Table 4.6.3-n

drx-Config CHOICE {
setup SEQUENCE {
drx-InactivityTimer Ms10
drx-RetransmissionTimerDL Sl80
drx-RetransmissionTimerUL Sl80
ms640 7
}
shortDRX SEQUENCE {
drx-ShortCycle ms80
}
drx-SlotOffset ms0
}
}
}
}
7.1.1.5.5 DRX operation / Short cycle configured / Long DRX command MAC control
element reception
(1)
ensure that {
when { short DRX cycle is configured and a long DRX Command MAC control element is received }
}
(2)
ensure that {
when { Long DRX cycle and drx-SlotOffset is configured and [(SFN * 10) + subframe number] modulo
drx-LongCycle} = drxStartOffset }
then { UE starts the OnDurationTimer after drx-SlotOffset and monitors PDCCH for OnDurationTimer
PDCCH-subframes }
}
[TS 38.321, clause 5.7]
according to requirements found in other clauses of this specification. When in RRC_CONNECTED, if DRX is
configured, for all the activated Serving Cells, the MAC entity may monitor the PDCCH discontinuously using the
DRX operation specified in this clause; otherwise the MAC entity shall monitor the PDCCH as specified in TS 38.213
[6].
ETSI

ra-ContentionResolutionTimer (as described in clause 5.1.5) is running; or
- a Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4); or
entity among the contention-based Random Access Preamble (as described in clause 5.1.4).
ETSI
2> else:
StartOffset:
2> monitor the PDCCH as specified in TS 38.213 [6];
3> start or restart drx-InactivityTimer in the first symbol after the end of the PDCCH reception.
Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to
symbol n when evaluating all DRX Active Time conditions as specified in this clause:
2> not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 [7];
2> not report CSI on PUCCH and semi-persistent CSI configured on PUSCH.
1> if CSI masking (csi-Mask) is setup by upper layers:
ETSI
2> in current symbol n, if drx-onDurationTimer would not be running considering grants/assignments/DRX

Command MAC CE/Long DRX Command MAC CE received until 4 ms prior to symbol n when evaluating
all DRX Active Time conditions as specified in this clause:
3> not report CSI on PUCCH.
NOTE: If a UE multiplexes a CSI configured on PUCCH with other overlapping UCI(s) according to the
procedure specified in TS 38.213 [6] subclause 9.2.5 and this CSI multiplexed with other UCI(s) would
be reported on a PUCCH resource outside DRX Active Time, it is up to UE implementation whether to
report this CSI multiplexed with other UCI(s).
Regardless of whether the MAC entity is monitoring PDCCH or not, the MAC entity transmits HARQ feedback,
aperiodic CSI on PUSCH, and aperiodic SRS defined in TS 38.214 [7] when such is expected.
7.1.1.5.5.3 Test Description
For FDD, NormalSLT=(current SFN, current sub-frame, current slot, y)=y; For TDD, NormalSLT(current SFN, current
slot, y) counts the minimum number of normal slots needed to cover y number of PDCCH-occasions (slots) until next
PDCCH-occasion(slot) available, starting from current slot on current SFN.
ETSI

U-S Message
1 SS transmits NR RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
message to configure specific DRX
parameters for NR Cell. (Note 1)
2 The UE transmits NR --> NR RRC: - -
(Note 2)
3 In a PDCCH occasion when the drx- <-- MAC PDU - -
PDCCH. The SS transmits an valid MAC
PDU. (Note 3)
4 Wait for the expiry of drx-InactivityTimer to - - - -
A ensure that UE starts the Short DRX Cycle.
5 In a PDCCH occasion before the drx- <-- MAC PDU (Long DRX MAC Control - -
onDurationTimer expires, the SS indicates element)
with Long DRX MAC Control element. UE
successfully decodes the MAC PDU.
7 In the first PDCCH occasion, after the drx- <-- MAC PDU - -
SlotOffset when the drx-onDurationTimer is
running according to [(SFN * 10) + subframe
number] modulo drx-LongCycle) = (drx-
StartOffset) modulo (drx-LongCycle)), the SS
on the PDCCH.
9 At least drx-InactivityTimer PDCCH <-- MAC PDU - -
occasions after the transmission of the MAC
PDU in Step 7 has been indicated (This
means the next DRX cycle or later after Step
7) in the last PDCCH occasion while the drx-
onDurationTimer is still running, the SS
indicates the transmission a DL MAC PDU
on the PDDCH. (Note 7)
Note 3: The SS assumes that the UE starts in long DRX after configuration.
Note 5: Timer tolerances for the MAC DRX related timers measured in PDCCH occasions (slots). These timers are:
Note 6: Void
Note 7: The drx-InactivityTimer is started in the next PDCCH occasion of the PDCCH occasion where DL new
ETSI

radioBearerConfig RadioBearerConfig with NR
conditions SRB2 and
DRB1
}
masterCellGroup CellGroupConfig with NR
condition SRB2_DRB1
}
}
}

drx-Config CHOICE {
setup SEQUENCE {
ms640 7
}
shortDRX SEQUENCE {
drx-ShortCycle ms80
}
drx-SlotOffset ms0
}
}
}
}
7.1.1.6 Semi-Persistent Scheduling
7.1.1.6.1 Correct handling of DL assignment / Semi-persistent case
(1)
with { UE in 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 CS-RNTI in slot y and with NDI set as 0
and PDCCH content indicates activation }
then {UE starts receiving DL MAC PDU in slots y+n*[semiPersistSchedIntervalDL] where ‘n’ is
positive integer starting at zero }
ETSI
(2)
with { UE in RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC
PDU in slot y+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a DL assignment addressed to its CS-RNTI in slot p and with NDI set as 0, where
p!= y+n*[semiPersistSchedIntervalDL] }
then { UE starts receiving DL MAC PDU in slots p+n*[semiPersistSchedIntervalDL] and stops
receiving DL MAC PDU at slots y+n*[semiPersistSchedIntervalDL]where ‘n’ is positive integer starting
at zero }
}
(3)
PDU at slot p+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a DL assignment [for retransmission] addressed to its CS-RNTI in Slot z and
with NDI set as 1, where z!= p+n*[semiPersistSchedIntervalDL] }
then { UE receives MAC PDU as per the retransmission grant for CS-RNTI }
}
(4)
PDU at slot y+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a DL assignment addressed to its C-RNTI in Slot p, such that p=
y+n*[semiPersistSchedIntervalDL] }
then { UE receives MAC PDU as per assignment addressed to its C-RNTI }
}
(5)
with { UE in RRC_Connected state with DRB established and stored DL SPS grant to receive MAC PDU at
slot z+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives a RRC Message 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 PDU’s as
per stored SPS assignment in slot z+n*[semiPersistSchedIntervalDL] }
}
(6)
ensure that {
when { UE receives a DL assignment addressed to its stored CS-RNTI in slot p and with NDI set as 0
and PDCCH content indicates deactivation }
then {UE stops receiving DL MAC PDU’s as per stored SPS assignment }
}
References: The conformance requirements covered in the present TC are specified in TS 38.321, clause 5.3.1, 5.8.1 TS
38.300, clause 10.2 and TS 38.213 clause 102. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.3.1]
ETSI
entity.
4> if the timeAlignmentTimer, associated with the TAG containing the Serving Cell on which the HARQ
feedback is to be transmitted,is running:
HARQ entity.
HARQ Process ID = [floor (CURRENT_slot × 10 / (numberOfSlotsPerFrame ×periodicity ))] modulo nrofHARQ-

Processes
ETSI
2> indicate a downlink assignment and redundancy version for the dedicated broadcast HARQ process to the HARQ
entity.
[TS 38.321, clause 5.8.1]
Semi-Persistent Scheduling (SPS) is configured by RRC per Serving Cell and per BWP. Activation and deactivation of
the DL SPS are independent among the Serving Cells.
For the DL SPS, a DL assignment is provided by PDCCH, and stored or cleared based on L1 signalling indicating SPS
activation or deactivation.
RRC configures the following parameters when SPS is configured:
- cs-RNTI: CS-RNTI for activation, deactivation, and retransmission;
- nrofHARQ-Processes: the number of configured HARQ processes for SPS;
- periodicity: periodicity of configured downlink assignment for SPS.
When SPS is released by upper layers, all the corresponding configurations shall be released.
After a downlink assignment is configured for SPS, the MAC entity shall consider sequentially that the Nth downlink
assignment occurs in the slot for which:
(numberOfSlotsPerFrame × SFN + slot number in the frame) =

[(numberOfSlotsPerFrame × SFNstart time + slotstart time) + N × periodicity × numberOfSlotsPerFrame / 10] modulo (1024
× numberOfSlotsPerFrame)
where SFNstart time and slotstart time are the SFN and slot, respectively, of the first transmission of PDSCH where the
configured downlink assignment was (re-)initialised.
[TS 38.300, clause 10.2]
In the downlink, the gNB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s). A UE always
monitors the PDCCH(s) in order to find possible assignments when its downlink reception is enabled (activity governed
by DRX when configured). When CA is configured, the same C-RNTI applies to all serving cells.
The gNB may pre-empt an ongoing PDSCH transmission to one UE with a latency-critical transmission to another UE.
The gNB can configure UEs to monitor interrupted transmission indications using INT-RNTI on a PDCCH. If a UE
receives the interrupted transmission indication, the UE may assume that no useful information to that UE was carried
by the resource elements included in the indication, even if some of those resource elements were already scheduled to
this UE.
In addition, with Semi-Persistent Scheduling (SPS), the gNB can allocate downlink resources for the initial HARQ
transmissions to UEs: RRC defines the periodicity of the configured downlink assignments while PDCCH addressed to
CS-RNTI can either signal and activate the configured downlink assignment, or deactivate it; i.e. a PDCCH addressed
to CS-RNTI indicates that the downlink assignment can be implicitly reused according to the periodicity defined by
RRC, until deactivated.
NOTE: when required, retransmissions are explicitly scheduled on PDCCH(s).
The dynamically allocated downlink reception overrides the configured downlink assignment in the same serving cell,
if they overlap in time. Otherwise a downlink reception according to the configured downlink assignment is assumed, if
activated.
When CA is configured, at most one configured downlink assignment can be signalled per serving cell. When BA is
configured, at most one configured downlink assignment can be signalled per BWP. On each serving cell, there can be
only one configured downlink assignment active at a time, and multiple configured downlink assignment can be
simultaneously active on different serving cells only. Activation and deactivation of configured downlink assignments
are independent among the serving cells.
[TS 38.213, clause 10.2]
ETSI
A UE validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or configured UL grant
Type 2 PDCCH if
- the CRC of a corresponding DCI format is scrambled with a CS-RNTI provided by cs-RNTI, and
- the new data indicator field for the enabled transport block is set to '0'.
Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 10.2-1 or Table 10.2-
2.
If validation is achieved, the UE considers the information in the DCI format as a valid activation or valid release of DL
SPS or configured UL grant Type 2. If validation is not achieved, the UE discards all the information in the DCI format.
Table 10.2-1: Special fields for DL SPS and UL grant Type 2 scheduling activation PDCCH validation
DCI format 0_0/0_1 DCI format 1_0 DCI format 1_1
HARQ process number set to all '0's set to all '0's set to all '0's
For the enabled transport block:
Redundancy version set to '00' set to '00'
set to '00'
Table 10.2-2: Special fields for DL SPS and UL grant Type 2 scheduling release PDCCH validation
DCI format 0_0 DCI format 1_0
HARQ process number set to all '0's set to all '0's
Modulation and coding scheme set to all '1's set to all '1's
Frequency domain resource
set to all '1's set to all '1's
assignment
A UE is expected to provide HARQ-ACK information in response to a SPS PDSCH release after {} symbols from the
last symbol of a PDCCH providing the SPS PDSCH release. If processingType2Enabled of PDSCH-ServingCellConfig
is set to enable for the serving cell with the PDCCH providing the SPS PDSCH release, N = 5 for μ = 0 , N = 5.5 for
μ = 1 , and N = 11 for μ = 2 , otherwise, N =10 for μ = 0 , N =12 for μ = 1 , N = 22 for μ = 2 , and N = 25 for
μ = 3 , wherein μ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH
providing the SPS PDSCH release and the SCS configuration of a PUCCH carrying the HARQ-ACK information in
response to a SPS PDSCH release.
ETSI

U-S Message
1 The SS transmits a DL assignment using UE’s <-- (DL SPS Grant) - -
CS-RNTI in Slot ‘Y’, NDI=0.
2 The SS transmits in Slot ‘Y’, a DL MAC PDU <-- MAC PDU - -
containing a RLC PDU (DL-SQN=0) on UM
DRB.
4 The SS transmits in Slot ‘Y+X’, a DL MAC <-- MAC PDU - -
PDU containing a RLC PDU (DL-SQN=1) on
DRB. (Note 1)
CS-RNTI in Slot ‘P’, NDI=0;
(Where Y+X<P<Y+2X)
7 The SS transmits in Slot ‘P’, a DL MAC PDU <-- MAC PDU - -
DRB.
9 The SS transmits in Slot ‘Y+2X’, a DL MAC <-- MAC PDU - -
UM DRB.
Feedback?
11 The SS transmits a DL assignment using UE’s <-- (DL Grant) - -
C-RNTI in Slot ‘P+X’, NDI=0.
12 The SS transmits in Slot ‘P+X’, a DL MAC <-- MAC PDU - -
PDU containing a RLC PDU (DL-SQN=3)on
UM DRB.(Note2)
14 The SS transmits in Slot ‘P+2X’, a DL MAC <-- MAC PDU - -
UM DRB.
CS-RNTI in Slot ‘P+3X’, NDI=0.
PDU containing 1 RLC PDU’s (DL-SQN=5) on
UM DRB; CRC is calculated in such a way will
result in CRC error in UE.
18 Check: Does the UE transmit a HARQ NACK? --> HARQ NACK - -
- EXCEPTION: Step 19 and 20 shall be - - - -
repeated until HARQ retransmission count = 3
is reached for MAC PDU at step 17.(Note 3)
CS-RNTI in Slot ‘Z’, NDI=1;
Where (P+3X < Z <P+4X); The DL HARQ
process is same as in step 18.
20 The SS re-transmits in Slot ‘Z’, a DL MAC PDU <-- MAC PDU - -
DRB.
- EXCEPTION: Up to 3 HARQ NACK from the - - - -
UE should be allowed at step 21(Note 3).
22 The SS Transmits a PDCCH [for DL SPS <-- PDCCH [for DL SPS explicit - -
deactivation] using UE’s CS-RNTI in slot ‘Q’, release]
NDI=0; Where (P+3X< Q <P+4X).
PDU containing 1 RLC PDU’s (DL-SQN=6)on
UM DRB;
Feedback?
ETSI
26 The SS Transmits a DL assignment using UE’s <-- (DL SPS Grant) - -

CS-RNTI in SF-Num ‘P+6X’, NDI=0
27 The SS transmits in SF-Num ‘P+6X’, a DL <-- MAC PDU - -
MAC PDU containing a RLC PDU (DL-
SQN=6)on UM DRB
29 SS transmits NR RRCReconfiguration to <-- RRCReconfiguration - -
disable SPS-ConfigurationDL.(Note 4)
RRCReconfigurationComplete.(Note5)
PDU containing 1 RLC PDU’s (DL-SQN=7) on
UM DRB;
Feedback?
Note 1: X is equal to semiPersistSchedIntervalDL in this document.
Note 2: The DL assignment for C-RNTI and hence the size of MAC PDU is different in size than stored CS-RNTI DL
assignment in step 6. This assures UE is receiving DSCH data as per DL assignment for C-RNTI and not as
per stored grant for CS-RNTI.
Note 3: 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.
Note 6: As per TS 38.508-1[4], the default value for PDSCH slot offset (K0) is 0, hence the DL MAC PDU’s
associated with DL SPS grant in Slot X are sent in same slot X.
Table 7.1.1.6.1.3.3-1: RRCReconfiguration (Preamble)

(CONTAINING
CellGroupConfig)
Not present NR
nonCriticalExtension := SEQUENCE{} Not present EN-DC
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

servCellIndex 1
Not present NR
sps-Config CHOICE {
setup SEQUENCE {
periodicity ms40
n1PUCCH-AN SEQUENCE{
pucch-ResourceId 0
}
}
}
}
}
cs-RNTI CHOICE {
setup SEQUENCE{
}
}
}
}
Table 7.1.1.6.1.3.3-3: RRCReconfiguration (step 29 of Table 7.1.1.6.1.3.2-1)

(CONTAINING
CellGroupConfig)
Not present NR
nonCriticalExtension := SEQUENCE{} Not present EN-DC
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

servCellIndex 1
Not present NR
sps-Config CHOICE {
release Null
}
}
}
}
}
7.1.1.6.2 Correct handling of UL grant / configured grant Type 1
(1)
with { UE in RRC_Connected state with DRB established and sps-Configuration in UL is enabled with
Configured grant type 1 }
ensure that {
when { The symbol in which equation [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) +
(slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] =
(timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 ×
numberOfSlotsPerFrame × numberOfSymbolsPerSlot)is satisfied }
then { UE starts transmitting UL MAC PDU periodically in the symbol associated with the new re-
configured grant }
}
(2)
with { UE in RRC_Connected state with DRB established and configured UL grant type 1 }
ensure that {
when { UE receives a new UL grant type 1 in an RRC message }
configured grant }
}
(3)
ensure that {
when { UE receives a RRC message including sps-Configuration with rrcConfiguredUplinkGrant set as
‘release’ }
then { UE deletes the stored configured UL Grant type 1 parameters and stops transmitting UL MAC
PDU’s as per configured UL grant type 1 }
}
(4)
ensure that {
when { UE receives a UL grant addressed to its CS-RNTI with NDI set as 1 for retransmission }
then { UE re-transmits MAC PDU as per the new grant }
}
(5)
ensure that {
ETSI
when { UE receives a UL grant addressed to its C-RNTI resulting in UL transmission overlap in time
domain as configured grante type 1 }
then { UE transmits MAC PDU as per grant addressed to its C-RNTI }
}7.1.1.6.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.321 clauses 5.4.1
and 5.8.2, 3GPP TS 38.300 clause 10.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.4.1]
NDI.
3> start or restart the configuredGrantTimer for the corresponding HARQ process, if configured.
grant;
ETSI
grant received on the PDCCH or in a Random Access Response for this Serving Cell:

that takes place.
NOTE 3: If the MAC entity receives both a grant in a Random Access Response and an overlapping grant for its C-
RNTI or CS-RNTI, requiring concurrent transmissions on the SpCell, the MAC entity may choose to
continue with either the grant for its RA-RNTI or the grant for its C-RNTI or CS-RNTI.
[TS 38.321, clause 5.8.2]
There are two types of transmission without dynamic grant:
- configured grant Type 1 where an uplink grant is provided by RRC, and stored as configured uplink grant;
- configured grant Type 2 where an uplink grant is provided by PDCCH, and stored or cleared as configured
uplink grant based on L1 signalling indicating configured uplink grant activation or deactivation.
Type 1 and Type 2 are configured by RRC per Serving Cell and per BWP. Multiple configurations can be active
simultaneously only on different Serving Cells. For Type 2, activation and deactivation are independent among the
Serving Cells. For the same Serving Cell, the MAC entity is configured with either Type 1 or Type 2.
RRC configures the following parameters when the configured grant Type 1 is configured:
- cs-RNTI: CS-RNTI for retransmission;
- periodicity: periodicity of the configured grant Type 1;
- timeDomainOffset: Offset of a resource with respect to SFN=0 in time domain;
- timeDomainAllocation: Allocation of configured uplink grant in time domain which contains

startSymbolAndLength (i.e. SLIV in TS 38.214 [7]);
- nrofHARQ-Processes: the number of HARQ processes for configured grant.
Upon configuration of a configured grant Type 1 for a Serving Cell by upper layers, the MAC entity shall:
ETSI
1> store the uplink grant provided by upper layers as a configured uplink grant for the indicated Serving Cell;
1> initialise or re-initialise the configured uplink grant to start in the symbol according to timeDomainOffset and S
(derived from SLIV as specified in TS 38.214 [7]), and to reoccur with periodicity.
After an uplink grant is configured for a configured grant Type 1, the MAC entity shall consider that the uplink grant
recurs associated with each symbol for which:
[(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in the frame ×

numberOfSymbolsPerSlot) + symbol number in the slot] =
(timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 × numberOfSlotsPerFrame ×
numberOfSymbolsPerSlot), for all N >= 0.

[(SFNstart time × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slotstart time × numberOfSymbolsPerSlot +
symbolstart time) + N × periodicity] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot), for all N >=
0.
where SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, of the first transmission
opportunity of PUSCH where the configured uplink grant was (re-)initialised.
When a configured uplink grant is released by upper layers, all the corresponding configurations shall be released and
all corresponding uplink grants shall be cleared.
1> if the configured uplink grant confirmation has been triggered and not cancelled; and
1> if the MAC entity has UL resources allocated for new transmission:
2> instruct the Multiplexing and Assembly procedure to generate an Configured Grant Confirmation MAC CE
as defined in subclause 6.1.3.7;
2> cancel the triggered configured uplink grant confirmation.
For a configured grant Type 2, the MAC entity shall clear the configured uplink grant immediately after first
transmission of Configured Grant Confirmation MAC CE triggered by the configured uplink grant deactivation.
Retransmissions except for repetition of configured uplink grants use uplink grants addressed to CS-RNTI.
[TS 38.300, clause 10.3]
In the uplink, the gNB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s). A UE always
monitors the PDCCH(s) in order to find possible grants for uplink transmission when its downlink reception is enabled
(activity governed by DRX when configured). When CA is configured, the same C-RNTI applies to all serving cells.
In addition, with Configured Grants, the gNB can allocate uplink resources for the initial HARQ transmissions to UEs.
Two types of configured uplink grants are defined:
- With Type 1, RRC directly provides the configured uplink grant (including the periodicity).
- With Type 2, RRC defines the periodicity of the configured uplink grant while PDCCH addressed to CS-RNTI
can either signal and activate the configured uplink grant, or deactivate it; i.e. a PDCCH addressed to CS-RNTI
indicates that the uplink grant can be implicitly reused according to the periodicity defined by RRC, until
deactivated.
The dynamically allocated uplink transmission overrides the configured uplink grant in the same serving cell, if they
overlap in time. Otherwise an uplink transmission according to the configured uplink grant is assumed, if activated.
Retransmissions other than repetitions are explicitly allocated via PDCCH(s).
ETSI
When CA is configured, at most one configured uplink grant can be signalled per serving cell. When BA is configured,
at most one configured uplink grant can be signalled per BWP. On each serving cell, there can be only one configured
uplink grant active at a time. A configured uplink grant for one serving cell can either be of Type 1 or Type 2. For Type
2, activation and deactivation of configured uplink grants are independent among the serving cells. When SUL is
configured, a configured uplink grant can only be signalled for one of the 2 ULs of the cell.
Same Pre-test conditions as in clause 7.1.1.0 and UM DRB should be established on NR Cell 1.
ETSI

U-S Message
messageto configure UL configured grant type
1 in SFN 900, timeDomainOffset is set to 5.
(Note 1)
2)
3 SS transmits a DL MAC PDU containing 4 <-- MAC PDU (nine RLC SDUs) - -
RLC SDUs of size 96 bytes in SFN 1022 on
UM DRB. (Note 3)
4 Check: Does the UE transmit a MAC PDU --> MAC PDU (one RLC SDU) 1 P
containing first RLC SDU in Symbol ‘x0’, Slot
y0’, SFN ‘z0’ after the SFN in step 3 wraps
around?
Where
[(z0 × numberOfSlotsPerFrame ×
numberOfSymbolsPerSlot) + (y0 ×
numberOfSymbolsPerSlot) + x0] = (5 ×
numberOfSymbolsPerSlot + S + 0 ×
periodicity) modulo (1024 ×
numberOfSlotsPerFrame ×
numberOfSymbolsPerSlot). (Note 4)
containing second RLC SDU in Symbol ‘x1’,
Slot y1’, SFN ‘z1’?
Where
numberOfSymbolsPerSlot).
message to configure UL configured grant type
1 in SFN ‘z1 + 1’, timeDomainOffset is set to
35.
RRCReconfigurationComplete. message RRCReconfigurationComplete)
8 Check: Does the UE transmit a MAC PDU --> MAC PDU (one RLC SDU) 2 F
containing third RLC SDU received in step 4 in
Symbol ‘x2’, Slot y2’, SFN ‘z2’?
Where
numberOfSymbolsPerSlot + S + N ×
numberOfSymbolsPerSlot), N >= 2.
containing fourth RLC SDU in Symbol ‘x3’, Slot
around?
Where
ETSI
containing fifth RLC SDU in Symbol ‘x4’, Slot
y4’, SFN ‘z4’?
Where
11 SS transmits a UL grant addressed to UE’s <-- (UL Grant) - -
stored CS-RNTI with NDI set as 1 in Slot ‘p0’of
PDCCH (p0 = floor ((y4 +2) * (PDCCHSCS /
PUSCHSCS))), allowing the UE to retransmit
one loop back SDU.
12 Check: Does the UE retransmit the MAC PDU --> MAC PDU (one RLC SDU) 4 P
containing the same fifth RLC SDU as in step
10 in Symbol ‘S’ of Slot ‘q’ of PUSCH?
i.e., in the PUSCH slot q = floor (p0 *

(PUSCHSCS / PDCCHSCS)) + K2. (Note 5)
containing sixth RLC SDU in Symbol ‘x5’, Slot
y5’, SFN ‘z5’?
Where
14 SS transmits a UL Grant using UE’s C-RNTI in <-- (UL Grant) - -
in Slot ‘p1’ of PDCCH allowing UE to transmit
a MAC PDU containing two RLC SDU, where
p1 = floor ((z6 × numberOfSlotsPerFrame - K2)
* (PDCCHSCS / PUSCHSCS)). (Note 6)
Where
15 Check: Does the UE transmit a MAC PDU --> MAC PDU (two RLC SDU’s) 5 P
containing seventh and eight RLC SDU’s in
Symbol ‘x6’, Slot y6’, SFN ‘z6’?
containing one RLC SDU in Symbol ‘x7’, Slot
y7’, SFN ‘z7’?
Where
17 After step 16, SS transmits NR <-- (NR RRC: RRCReconfiguration - -
RRCReconfiguration message to release UL
configured grant type 1 in SFN ‘z4 + 1’.
19 SS transmits a DL MAC PDU containing one <-- MAC PDU (one RLC SDU)
RLC SDU of size 96 bytes in SFN ‘z7 + 10’.
20 Check: Does the UE transmit a MAC PDU --> MAC PDU (one RLC SDU) 3 F
ETSI
containing one RLC SDU in Symbol ‘x8’, Slot

y8’, SFN ‘z8’?
Where
Note 3: According to the setting parameters in Table 7.1.1.6.2.3.3-2, TB size for configured grant type 1 is 808 bits,
which is enough to allow the UE to transmit one PDU at a time (96 bytes RLC SDU + 1 byte UM RLC
Header + 2 bytes MAC Sub PDU header + 2 bytes for short BSR or padding).
Note 4: S is the starting symbol relative to the slot of the first PUSCH transmission for new configured grant type 1.
The value of S can be obtained from TS 38.508-1 [4], Table 4.6.3-122.
 2μPUSCH 
Note 5: q is the slot where the UE shall transmit the PUSCH and is determined by K2 as n ⋅ μ  + K2
 2 PDCCH 
where n is the slot with the scheduling DCI, K2 is based on the numerology of PUSCH. S is the starting
symbol relatived to the start of the slot q according to TS 38.214 clause 6.1.2.1.
Note 6: The UL grant addressed to C-RNTI should result in UL transmission overlap in time domain as configured
grant type 1.

(CONTAINING
CellGroupConfig)
Not Present NR
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

cs-RNTI CHOICE {
setup SEQUENCE{
}
}
}
servCellIndex Not present NR
1 EN-DC
initialUplink SEQUENCE {
setup SEQUENCE {
sl20 10
}
}
}
}
setup SEQUENCE {
38.508-1[4], Table
4.6.3-51
setup SEQUENCE {
}
}
}
1
p0-PUSCH-Alpha 1
repK n1
ETSI
timeDomainOffset 5 For Step 1

35 For Step 6
38.508-1 [4], Table
4.6.3-122
frequencyDomainAllocation BIT STRING (SIZE(18) BIT STRING FR1_FDD,
(SIZE(18), Equal to FR1_TDD
NBWPsize * (LRB-
1) + RBstart),
where
LRB = 2 PRB,
RBstart = 0,
NBWPsize is the
size [PRBs] of the
active carrier
bandwidth part and
ontained in
TS.38.508-1 [4]
clause 4.3.1.1.
frequencyDomainAllocation BIT STRING (SIZE(18) BIT STRING FR2_TDD
(SIZE(18), Equal to
NBWPsize * (LRB-
1) + RBstart),
where
LRB=9 PRB,
RBstart = 0and
NBWPsize is the
size [PRBs] of the
active carrier
bandwidth part and
ontained in
TS.38.508-1 [4]
clause 4.3.1.2.
antennaPort 0
mcsAndTBS 18 FR1_FDD,
FR1_TDD
25 FR2_TDD
}
}
}
setup SEQUENCE {
PUSCH-TimeDomainResourceAllocationList
SEQUENCE {
k2 n8 FR1 and
FR2
mappingType typeB
startSymbolAndLength 0011011 Start symbol(S)=0, FR1
Length(L)=14
startSymbolAndLength 0001110 S=0, L=2 FR2
}
}
}
}
}
}
}
}
}
ETSI

(CONTAINING
CellGroupConfig)
Not present NR
(CONTAINING
CellGroupConfig)
}
}
}
}

release Null
}
}
}
}
}
}
7.1.1.6.3 Correct handling of UL grant / configured grant Type 2
(1)
with { UE in RRC_Connected state with DRB established and sps-Configuration in UL is enabled }
ensure that {
when { UE receives an UL configured grant type 2 addressed to its stored CS-RNTI with NDI set as 0
and PDCCH content indicates SPS activation }
then { UE starts transmitting UL MAC PDU periodically in the symbol associated with the
configured grant }
}
(2)
ensure that {
when {UE receives a UL grant addressed to its CS-RNTI with NDI set as 0 }
configured grant }
}
ETSI
(3)
ensure that {
when { UE receives a UL grant addressed to its CS-RNTI with NDI set as 1 for retransmission }
then { UE re-transmits MAC PDU as per the new grant }
}
(4)
with{ UE in RRC_Connected state with DRB established and configured UL grant type 2 }
ensure that {
when { UE receives a UL grant addressed to its C-RNTI resulting in UL transmission overlap in time
domain as configured grante type 2 }
then { UE transmits MAC PDU as per grant addressed to its C-RNTI }
}
(5)
ensure that {
when {UE receives a RRC message 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 PDU’s
as per configured UL grant type 2 }
}
(6)
with{ UE in RRC_Connected state with DRB established and configured UL grant type 2 }
ensure that {
when{ If in the symbol in which UL Configured Grant type 2 is available but the HARQ buffer is
empty (no data for transmission) }
then{ UE ignores the UL configured grant type 2 and does not send any MAC PDU }
}
(7)
with { UE in RRC_Connected state with DRB established and sps-Configuration in UL is enabled }
ensure that {
when { UE receives UL configured grant type 2 addressed to its stored CS-RNTI in slot p and with
NDI set as 0 and PDCCH content indicates SPS deactivation }
then {UE stops transmitting UL MAC PDU’s as per configured UL grant type 2}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.321 clauses 5.4.1
and 5.8.2, 3GPP TS 38.300 clauses 10.3 and TS 38.213 clause 102. Unless otherwise stated these are Rel-15
requirements.
[TS 38.321, clause 5.4.1]
ETSI
NDI.
3> start or restart the configuredGrantTimer for the correponding HARQ process, if configured.
grant;
grant received on the PDCCH or in a Random Access Response for this Serving Cell:

ETSI
that takes place.
NOTE 3: If the MAC entity receives both a grant in a Random Access Response and an overlapping grant for its C-
RNTI or CS-RNTI, requiring concurrent transmissions on the SpCell, the MAC entity may choose to
continue with either the grant for its RA-RNTI or the grant for its C-RNTI or CS-RNTI.
[TS 38.321, clause 5.8.2]
There are two types of transmission without dynamic grant:
Type 1 and Type 2 are configured by RRC per Serving Cell and per BWP. Multiple configurations can be active
simultaneously only on different Serving Cells. For Type 2, activation and deactivation are independent among the
Serving Cells. For the same Serving Cell, the MAC entity is configured with either Type 1 or Type 2.
- timeDomainOffset: Offset of a resource with respect to SFN=0 in time domain;

startSymbolAndLength (i.e. SLIV in TS 38.214 [7]);
Upon configuration of a configured grant Type 1 for a Serving Cell by upper layers, the MAC entity shall:
1> store the uplink grant provided by upper layers as a configured uplink grant for the indicated Serving Cell;
1> initialise or re-initialise the configured uplink grant to start in the symbol according to timeDomainOffset and S
(derived from SLIV as specified in TS 38.214 [7]), and to reoccur with periodicity.

(timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 × numberOfSlotsPerFrame ×
numberOfSymbolsPerSlot), for all N >= 0.

symbolstart time) + N × periodicity] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot), for all N >=
0.
ETSI
When a configured uplink grant is released by upper layers, all the corresponding configurations shall be released and
1> if the configured uplink grant confirmation has been triggered and not cancelled; and
2> instruct the Multiplexing and Assembly procedure to generate an Configured Grant Confirmation MAC CE
as defined in subclause 6.1.3.7;
2> cancel the triggered configured uplink grant confirmation.
For a configured grant Type 2, the MAC entity shall clear the configured uplink grant immediately after first
transmission of Configured Grant Confirmation MAC CE triggered by the configured uplink grant deactivation.
Retransmissions except for repetition of configured uplink grants use uplink grants addressed to CS-RNTI.
[TS 38.300, clause 10.3]
In addition, with Configured Grants, the gNB can allocate uplink resources for the initial HARQ transmissions to UEs.
Two types of configured uplink grants are defined:
deactivated.
The dynamically allocated uplink transmission overrides the configured uplink grant in the same serving cell, if they
overlap in time. Otherwise an uplink transmission according to the configured uplink grant is assumed, if activated.
Retransmissions other than repetitions are explicitly allocated via PDCCH(s).
When CA is configured, at most one configured uplink grant can be signalled per serving cell. When BA is configured,
at most one configured uplink grant can be signalled per BWP. On each serving cell, there can be only one configured
uplink grant active at a time. A configured uplink grant for one serving cell can either be of Type 1 or Type 2. For Type
2, activation and deactivation of configured uplink grants are independent among the serving cells. When SUL is
configured, a configured uplink grant can only be signalled for one of the 2 ULs of the cell.
[TS 38.213, clause 10.2]
A UE validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or configured UL grant
Type 2 PDCCH if
- the new data indicator field for the enabled transport block is set to '0'.
Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 10.2-1 or Table 10.2-
2.
ETSI
Table 10.2-1: Special fields for DL SPS and UL grant Type 2 scheduling activation PDCCH validation
DCI format 0_0/0_1 DCI format 1_0 DCI format 1_1
set to '00'
Table 10.2-2: Special fields for DL SPS and UL grant Type 2 scheduling release PDCCH validation
DCI format 0_0 DCI format 1_0

Frequency domain resource
set to all '1's set to all '1's
assignment
A UE is expected to provide HARQ-ACK information in response to a SPS PDSCH release after symbols from the last
symbol of a PDCCH providing the SPS PDSCH release. If processingType2Enabled of PDSCH-ServingCellConfig is
set to enable for the serving cell with the PDCCH providing the SPS PDSCH release, N = 5 for μ = 0 , N = 5.5 for
μ = 1 , and N = 11 for μ = 2 , otherwise, N =10 for μ = 0 , N =12 for μ = 1 , N = 22 for μ = 2 , and N = 25 for
μ = 3 , wherein μ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH
Same Pre-test conditions as in clause 7.1.1.0 and UM DRB should be established on NR Cell 1.The loop back size is set
to accommodate one RLC SDU in UL of same size as one RLC SDU in DL and 1 byte MAC subheader for Configured
Grant Confirmation MAC CE.
ETSI

U-S Message
1 SS transmits NR RRCReconfiguration <-- (NR RRC: RRCReconfiguration - -
message to configure UL configured grant type
2. (Note 1)
RRCReconfigurationComplete message. (Note RRCReconfigurationComplete
2)
3 SS transmits a DL MAC PDU containing 6 <-- MAC PDU - -
RLC SDUs on UM DRB.
4 The UE transmits a Scheduling Request, --> (SR) - -
indicating that loop back SDUs are ready for
transmission in UL RLC.
5 SS transmits a UL configured grant type 2 <-- (UL configured Grant type 2) - -
addressed to UE’s stored CS-RNTI in Slot ‘n’
of PDCCH, NDI=0, allowing the UE to transmit
one loop back SDU and 1 byte MAC
subheader for Configured Grant Confirmation
MAC CE.
containing one RLC SDU and a Configured
Grant Confirmation MAC CE in Symbol ‘S’ of
Slot ‘y’ of PUSCH as per grant in step 5?
i.e., in the PUSCH slot y=floor (n * (PUSCHSCS

/ PDCCHSCS)) + K2. (Note 3)
containing one RLC SDU in Symbol ‘S’ of Slot
‘y + x’ of PUSCH as per grant in step 5? (Note
4)
addressed to UE’s stored CS-RNTI in Slot ‘p’
of PDCCH (p = floor (p0 * (PDCCHSCS /
PUSCHSCS))), NDI = 0, allowing the UE to
transmit one loop back SDU and 1 byte MAC
MAC CE,
Where p0 is the slot of PUSCH with y + x < p0
< y + 2x - K2.
containing one RLC SDU and 1 byte MAC
MAC CE in Symbol ‘S’ of Slot ‘z’ of PUSCH as
per grant in step 8?
i.e., in the PUSCH slot z = floor (p *

(PUSCHSCS/ PDCCHSCS)) + K2. (Note 3)
10 Check: Does the UE transmit a MAC PDU --> MAC PDU 2 F
‘y + 2x’ as per grant in step 5?
‘z + x’ of PUSCH as per grant in step 8?
addressed to UE’s stored CS-RNTI in Slot ‘q’
of PDCCH (q = floor (q0 * (PDCCHSCS /
PUSCHSCS))), NDI = 1; allowing the UE to
transmit one loop back SDU. The UL HARQ
process is the same as in step 11,
Where q0 is the slot of PUSCH with z + x < q0
< z + 2x - K2.
containing the same RLC SDU as in step 11 in
Symbol ‘S’ of Slot ‘w’ of PUSCH?
ETSI
i.e., in the PUSCH slot w = floor (q *

(PUSCHSCS / PDCCHSCS)) + K2. (Note 3)
‘z + 2x’ of PUSCH as per grant in step 8?
15 SS transmits a UL Grant using UE’s C-RNTI in <-- (UL Grant) - -
in Slot ‘r’ of PDCCH allowing UE to transmit a
MAC PDU containing one RLC SDU, where r =
floor ((z + 3x - K2) * (PDCCHSCS / PUSCHSCS)).
17 Check: Does the UE transmit a MAC PDU in --> MAC PDU 6 F
Slot ‘z + 4x’ as per grant in containing zero
MAC SDU? (Note 5)
18 SS transmits a DL MAC PDU containing 1 <-- MAC PDU
RLC SDU on UM DRB after step 17.
20 The SS transmits a PDCCH [for UL configured <-- PDCCH [for UL configured grant - -
grant type 2 explicit release] using UE’s CS- type 2 explicit release]
RNTI in Symbol ‘S’ of slot ‘p’ with NDI=0.
Where (z+5x< p <z+6x).
‘S’ of Slot ‘z + 6x’ of PUSCH as per grant in
step 8?
22 SS transmits a UL configured grant type 2 <-- (UL configured grant type 2) - -
addressed to UE’s stored CS-RNTI in Slot ‘j’ of
PDCCH, NDI=0, allowing the UE to transmit
one loop back SDU and 1 byte MAC
MAC CE.
containing one RLC SDU and a Configured
Grant Confirmation MAC CE in Symbol ‘S’ of
Slot ‘y’ of PUSCH as per grant in step 22?
i.e., in the PUSCH slot y=floor (n * (PUSCHSCS

/ PDCCHSCS)) + K2. (Note 3)
24 SS transmits RRCReconfiguration to disable <-- NR RRC: RRCReconfiguration - -
UL configured grant type 2.
25 The UE transmits --> NR RRC: - -
RRCReconfigurationComplete. RRCReconfigurationComplete
26 SS transmits a DL MAC PDU containing 1 <-- MAC PDU - -
RLC SDU.
Symbol ‘S’ of Slot ‘z + 6x’ of PUSCH as per
grant in step 8.
 2μPUSCH 
Note 3: y is the slot where the UE shall transmit the PUSCH and is determined by K2 as n ⋅ μ  + K2
 2 PDCCH 
symbol relatived to the start of the slot y according to TS 38.214 clause 6.1.2.1.
Note 4: x is equal to periodicity / 14 in this test case.
Note 5: If the MAC entity does not generate a MAC PDU, one of the conditions which shall be satisfied is that there
is no aperiodic CSI requested for this PUSCH transmission as specified in TS 38.321 clause 5.4.3.1.3.
ETSI

(CONTAINING
CellGroupConfig)
Not present NR
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

cs-RNTI CHOICE {
setup SEQUENCE{
}
}
}
setup SEQUENCE {
sl20 10
}
}
}
}
setup SEQUENCE {
38.508-1 [4], Table
4.6.3-51
setup SEQUENCE {
}
}
}
resourceAllocation ResourceAllocationType1
p0-PUSCH-Alpha 1
repK n1
}
}
setup SEQUENCE {
ETSI
SEQUENCE {
k2 n8 FR1 and
FR2
mappingType typeB
startSymbolAndLength 0011011 FR1
startSymbolAndLength 0001110 FR2
}
}
}
}
}
}
}

(CONTAINING
CellGroupConfig)
Not present NR
(CONTAINING
CellGroupConfig)
}
}
}
}

cellGroupId 1
release Null
}
}
}
}
}
}
ETSI
7.1.1.6.4 Correct handling of DL assignment / Multi Semi-persistent configuration
(1)
ensure that {
when { UE receives a DL assignment addressed to its stored CS-RNTI in slot y and with NDI set as 0
with sps-ConfigIndex=0}
then {UE starts receiving DL MAC PDU in slots y+n*[semiPersistSchedIntervalDL] where ‘n’ is
positive integer starting at zero }
}
(2)
PDU in slot y+n*[semiPersistSchedIntervalDL] }
ensure that {
when { UE receives another DL assignment addressed to its CS-RNTI in slot p and with NDI set as 0
associated with sps-ConfigIndex=1, where p!= y+n*[semiPersistSchedIntervalDL] }
then { UE starts receiving DL MAC PDU in slots p+n*[semiPersistSchedIntervalDL] and continue
receiving DL MAC PDU at slots y+n*[semiPersistSchedIntervalDL]where ‘n’ is positive integer starting
at zero }
}
38.300, clause 10.2, and TS 38.213, clause 10.2. Unless otherwise stated these are Rel-16 requirements.
[TS 38.321, clause 5.3.1]
entity.
ETSI
4> if the timeAlignmentTimer, associated with the TAG containing the Serving Cell on which the HARQ
feedback is to be transmitted, is running:
associated PDSCH duration and to recur according to rules in clause 5.8.1;
HARQ entity.
For configured downlink assignments without harq-ProcID-Offset, the HARQ Process ID associated with the slot
where the DL transmission starts is derived from the following equation:

Processes
NOTE 1: In case of unaligned SFN across carriers in a cell group, the SFN of the concerned Serving Cell is used to
calculate the HARQ Process ID used for configured downlink assignments.
For configured downlink assignments with harq-ProcID-Offset, the HARQ Process ID associated with the slot where
the DL transmission starts is derived from the following equation:

Processes + harq-ProcID-Offset
NOTE 2: CURRENT_slot refers to the slot index of the first transmission occasion of a bundle of configured
downlink assignment.
HARQ entity.
[TS 38.321, clause 5.8.1]
ETSI
Semi-Persistent Scheduling (SPS) is configured by RRC per Serving Cell and per BWP. Multiple assignments can be
active simultaneously in the same BWP. Activation and deactivation of the DL SPS are independent among the Serving
Cells.
For the DL SPS, a DL assignment is provided by PDCCH, and stored or cleared based on L1 signalling indicating SPS
activation or deactivation.
RRC configures the following parameters when the SPS is configured:
- nrofHARQ-Processes: the number of configured HARQ processes for SPS;
- harq-ProcID-Offset: Offset of HARQ process for SPS;
- periodicity: periodicity of configured downlink assignment for SPS.
When the SPS is released by upper layers, all the corresponding configurations shall be released.
After a downlink assignment is configured for SPS, the MAC entity shall consider sequentially that the Nth downlink
assignment occurs in the slot for which:
(numberOfSlotsPerFrame × SFN + slot number in the frame) =

[(numberOfSlotsPerFrame × SFNstart time + slotstart time) + N × periodicity × numberOfSlotsPerFrame / 10] modulo (1024
× numberOfSlotsPerFrame)
where SFNstart time and slotstart time are the SFN and slot, respectively, of the first transmission of PDSCH where the
configured downlink assignment was (re-)initialised.
NOTE: In case of unaligned SFN across carriers in a cell group, the SFN of the concerned Serving Cell is used to
calculate the occurrences of configured downlink assignments.
[TS 38.300, clause 10.2]
In the downlink, the gNB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s). A UE always
monitors the PDCCH(s) in order to find possible assignments when its downlink reception is enabled (activity governed
by DRX when configured). When CA is configured, the same C-RNTI applies to all serving cells.
The gNB may pre-empt an ongoing PDSCH transmission to one UE with a latency-critical transmission to another UE.
The gNB can configure UEs to monitor interrupted transmission indications using INT-RNTI on a PDCCH. If a UE
receives the interrupted transmission indication, the UE may assume that no useful information to that UE was carried
by the resource elements included in the indication, even if some of those resource elements were already scheduled to
this UE.
In addition, with Semi-Persistent Scheduling (SPS), the gNB can allocate downlink resources for the initial HARQ
transmissions to UEs: RRC defines the periodicity of the configured downlink assignments while PDCCH addressed to
CS-RNTI can either signal and activate the configured downlink assignment, or deactivate it; i.e. a PDCCH addressed
to CS-RNTI indicates that the downlink assignment can be implicitly reused according to the periodicity defined by
RRC, until deactivated.
NOTE: When required, retransmissions are explicitly scheduled on PDCCH(s).
The dynamically allocated downlink reception overrides the configured downlink assignment in the same serving cell,
if they overlap in time. Otherwise a downlink reception according to the configured downlink assignment is assumed, if
activated.
The UE may be configured with up to 8 active configured downlink assignments for a given BWP of a serving cell.
When more than one is configured:
- The network decides which of these configured downlink assignments are active at a time (including all of
them); and
- Each configured downlink assignment is activated separately using a DCI command and deactivation of
configured downlink assignments is done using a DCI command, which can either deactivate a single configured
downlink assignment or multiple configured downlink assignments jointly.
ETSI
[TS 38.213, clause 10.2]
A UE validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or a configured UL
grant Type 2 PDCCH if
- the new data indicator field in the DCI format for the enabled transport block is set to '0', and
- the DFI flag field, if present, in the DCI format is set to '0', and
- if validation is for scheduling activation and if the PDSCH-to-HARQ_feedback timing indicator field in the DCI
format is present, the PDSCH-to-HARQ_feedback timing indicator field does not provide an inapplicable value
from dl-DataToUL-ACK-r16.
If a UE is provided a single configuration for UL grant Type 2 PUSCH or for SPS PDSCH, validation of the DCI
format is achieved if all fields for the DCI format are set according to Table 10.2-1 or Table 10.2-2.
If a UE is provided more than one configurations for UL grant Type 2 PUSCH or for SPS PDSCH, a value of the
HARQ process number field in a DCI format indicates an activation for a corresponding UL grant Type 2 PUSCH or
for a SPS PDSCH configuration with a same value as provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex,
respectively. Validation of the DCI format is achieved if the RV field for the DCI format is set as in Table 10.2-3.
If a UE is provided more than one configuration for UL grant Type 2 PUSCH or for SPS PDSCH
- if the UE is provided ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, a

value of the HARQ process number field in a DCI format indicates a corresponding entry for scheduling release
of one or more UL grant Type 2 PUSCH or SPS PDSCH configurations
- if the UE is not provided ConfiguredGrantConfigType2DeactivationStateList or sps-

ConfigDeactivationStateList, a value of the HARQ process number field in a DCI format indicates a release for a
corresponding UL grant Type 2 PUSCH or for a SPS PDSCH configuration with a same value as provided by
ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively.
Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 10.2-4.
Table 10.2-1: Special fields for single DL SPS or single UL grant Type 2 scheduling activation PDCCH
validation when a UE is provided a single SPS PDSCH or UL grant Type 2 configuration in the active
DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_2 DCI format 1_1
Redundancy version set to all '0's set to all '0's
set to all '0's
Table 10.2-2: Special fields for single DL SPS or single UL grant Type 2 scheduling release PDCCH
validation when a UE is provided a single SPS PDSCH or UL grant Type 2 configuration in the active
DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_1/1_2
set to all '0's for FDRA set to all '0's for FDRA
Type 2 with Type 0 or for
Frequency domain resource dynamicSwitch
assignment
set to all '1's for FDRA
set to all '1's, otherwise Type 1
ETSI
Table 10.2-3: Special fields for a single DL SPS or single UL grant Type 2 scheduling activation
PDCCH validation when a UE is provided multiple DL SPS or UL grant Type 2 configurations in the
active DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_2 DCI format 1_1
set to all '0's
Table 10.2-4: Special fields for a single or multiple DL SPS and UL grant Type 2 scheduling release
PDCCH validation when a UE is provided multiple DL SPS or UL grant Type 2 configurations in the
active DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_1/1_2
set to all '0's for FDRA
Type 2 with set to all '0's for FDRA Type 0 or
for dynamicSwitch
Frequency domain resource assignment
set to all '1's for FDRA Type 1
set to all '1's, otherwise
A UE is expected to provide HARQ-ACK information in response to a SPS PDSCH release after symbols from the
last symbol of a PDCCH providing the SPS PDSCH release. If processingType2Enabled of PDSCH-ServingCellConfig
is set to enable for the serving cell with the PDCCH providing the SPS PDSCH release, for , for
, and for , otherwise, for , for , for , and for
, wherein corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH
Same Pre-test conditions as in clause 7.1.1.0 except that set to return no data in uplink and that the UM DRB is
configured according to Table 7.1.1.6.4.3.1-1.
Uplink UM RLC sn-FieldLength IF (pc_um_WithShortSN ) size6

ELSE size12
Downlink UM RLC sn-FieldLength F (pc_um_WithShortSN ) size6
ELSE size12
ETSI

U-S Message
config SPS-ConfigurationDL.(Note 2)
RRCReconfigurationComplete.(Note 3)
CS-RNTI associated with sps-ConfigIndex=0
in Slot ‘Y’, NDI=0
4 The SS transmits in Slot ‘Y’, a DL MAC PDU <-- MAC PDU - -
containing a RLC PDU on UM DRB.
5 Check: does the UE transmit a HARQ ACK? --> HARQ ACK 1 P
6 The SS transmits in Slot ‘Y+X’, a DL MAC <-- MAC PDU - -
PDU containing a RLC PDU on DRB. (Note 1)
8 SS transmits NR RRCReconfiguration to add <-- RRCReconfiguration - -
another SPS-ConfigurationDL.(Note 2)
CS-RNTI associated with sps-ConfigIndex=1
in Slot ‘P’, NDI=0;
(Where Y+X<P<Y+2X)
11 The SS transmits in Slot ‘P’, a DL MAC PDU <-- MAC PDU - -
containing a RLC PDU on UM DRB.
13 The SS transmits in Slot ‘Y+2X’, a DL MAC <-- MAC PDU - -
PDU containing a RLC PDU on UM DRB.
14 Check: Does the UE transmit a HARQ --> HARQ ACK 2 P
Feedback?
15 The SS transmits in Slot ‘P+X’, a DL MAC <-- MAC PDU - -
UM DRB.
16 Check: Does the UE transmit a HARQ --> HARQ ACK 2 P
Feedback?
disable SPS-ConfigurationDL.(Note 2)
Note 1: X is equal to semiPersistSchedIntervalDL in this document.
Note 4: As per TS 38.508-1[4], the default value for PDSCH slot offset (K0) is 0, hence the DL MAC PDU’s
associated with DL SPS grant in Slot X are sent in same slot X.
ETSI
Table 7.1.1.6.4.3.3-1: RRCReconfiguration (step 1/8, Table 7.1.1.6.4.3.2-1)

(CONTAINING
CellGroupConfig)
Not present NR
nonCriticalExtension Not present EN-DC
(CONTAINING
CellGroupConfig)
}
}
}
}
Table 7.1.1.6.4.3.3-2: CellGroupConfig (in Table 7.1.1.6.4.3.3-1)

physicalCellGroupConfig PhysicalCellGroupConfig Table
7.1.1.6.4.3.3-3
servCellIndex 1 EN-DC
Not present NR
sps-ConfigToAddModList-r16 ::= SEQUENCE
(SIZE (1..maxNrofSPS-Config-r16)) OF SPS-
Config {
SPS-Config ::= SEQUENCE [1] { The first SPS STEP 1
configuration entry
setup SEQUENCE {
periodicity ms160
sps-ConfigIndex-r16 0
harq-ProcID-Offset-r16 0
}
SPS-Config ::= SEQUENCE [2] { The second SPS STEP 8
configuration entry
setup SEQUENCE {
periodicity ms160
harq-ProcID-Offset-r16 8
}
}
}
}
}
}
}
ETSI
Table 7.1.1.6.4.3.3-3: PhysicalCellGroupConfig (Table 7.1.1.6.4.3.3-2)

PhysicalCellGroupConfig ::= SEQUENCE {
cs-RNTI ‘FFE0’H
}

(CONTAINING
CellGroupConfig)
Not present NR
nonCriticalExtension Not present EN-DC
(CONTAINING
CellGroupConfig)
}
}
}
}

servCellIndex 1
Not present NR
sps-ConfigToReleaseList-r16 SEQUENCE 2 entries Release all the
(SIZE (1..maxNrofSPS-Config-r16)) OF SPS- SPS entries
ConfigIndex-r16 { configured
previously
SPS-ConfigIndex-r16[1] 0
SPS-ConfigIndex-r16[2] 1
}
}
}
}
}
7.1.1.6.5 Correct handling of UL grant / Multi configured uplink grants
7.1.1.6.5.1 Test Purpose (TP)(1)

with { UE in RRC_Connected state with DRB established and sps-Configuration in UL is enabled with
Configured grant type 1 }
ensure that {
when { The symbol in which equation [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) +
(slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] =
(timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 ×
numberOfSlotsPerFrame × numberOfSymbolsPerSlot)is satisfied }
ETSI
configured grant }
}
(2)
ensure that {
when { UE receives another UL grant type 1 in an RRC message with timeDomainOffset 15}
then { UE starts transmitting UL MAC PDU in symbol with timeDomainOffset 15 and continue
transmitting UL MAC PDU in symbol with timeDomainOffset 5}
}
38.300, clause 10.3. Unless otherwise stated these are Rel-16 requirements.
[TS 38.321, clause 5.4.1]
Uplink grant is either received dynamically on the PDCCH, in a Random Access Response, configured semi-
persistently by RRC or determined to be associated with the PUSCH resource of MSGA as specified in clause 5.1.2a.
The MAC entity shall have an uplink grant to transmit on the UL-SCH. To perform the requested transmissions, the
MAC layer receives HARQ information from lower layers. An uplink grant addressed to CS-RNTI with NDI = 0 is
considered as a configured uplink grant. An uplink grant addressed to CS-RNTI with NDI = 1 is considered as a
dynamic uplink grant.
NDI.
3> start or restart the configuredGrantTimer for the corresponding HARQ process, if configured.
3> stop the cg-RetransmissionTimer for the corresponding HARQ process, if running.
3> stop the cg-RetransmissionTimer for the corresponding HARQ process, if running;
ETSI
grant;
PUSCH duration and to recur according to rules in clause 5.8.2;
4> stop the cg-RetransmissionTimer for the corresponding HARQ process, if running.
1> if the MAC entity is configured with lch-basedPrioritization, and the PUSCH duration of the configured uplink
grant does not overlap with the PUSCH duration of an uplink grant received in a Random Access Response or
with the PUSCH duration of an uplink grant addressed to Temporary C-RNTI or the PUSCH duration of a
MSGA payload for this Serving Cell; or
1> if the MAC entity is not configured with lch-basedPrioritization, and the PUSCH duration of the configured
uplink grant does not overlap with the PUSCH duration of an uplink grant received on the PDCCH or in a
Random Access Response or the PUSCH duration of a MSGA payload for this Serving Cell:
2> if, for the corresponding HARQ process, the configuredGrantTimer is not running and cg-
RetransmissionTimer is not configured (i.e. new transmission):
2> else if the cg-RetransmissionTimer for the corresponding HARQ process is configured and not running, then
for the corresponding HARQ process:
3> if the configuredGrantTimer is not running, and the HARQ process is not pending (i.e. new
transmission):
3> else if the previous uplink grant delivered to the HARQ entity for the same HARQ process was a
configured uplink grant (i.e. retransmission on configured grant):
For configured uplink grants neither configured with harq-ProcID-Offset2 nor with cg-RetransmissionTimer, the
HARQ Process ID associated with the first symbol of a UL transmission is derived from the following equation:
For configured uplink grants with harq-ProcID-Offset2, the HARQ Process ID associated with the first symbol of a UL
transmission is derived from the following equation:
HARQ Process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + harq-ProcID-Offset2
where CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot number in the frame

× numberOfSymbolsPerSlot + symbol number in the slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot
ETSI
[TS 38.321, clause 5.8.2]There are two types of transmission without dynamic grant:
Type 1 and Type 2 are configured by RRC for a Serving Cell per BWP. Multiple configurations can be active
simultaneously in the same BWP. For Type 2, activation and deactivation are independent among the Serving Cells. For
the same BWP, the MAC entity can be configured with both Type 1 and Type 2.
- timeDomainOffset: Offset of a resource with respect to SFN = timeReferenceSFN in time domain;

startSymbolAndLength (i.e. SLIV in TS 38.214 [7]) or startSymbol (i.e. S in TS 38.214 [7]);
- nrofHARQ-Processes: the number of HARQ processes for configured grant;
- harq-ProcID-Offset: offset of HARQ process for configured grant for operation with shared spectrum channel
access;
- harq-ProcID-Offset2: offset of HARQ process for configured grant;
- timeReferenceSFN: SFN used for determination of the offset of a resource in time domain. The UE uses the
closest SFN with the indicated number preceding the reception of the configured grant configuration.
- nrofHARQ-Processes: the number of HARQ processes for configured grant;
- harq-ProcID-Offset: offset of HARQ process for configured grant for operation with shared spectrum channel
access;
- harq-ProcID-Offset2: offset of HARQ process for configured grant.
RRC configures the following parameters when retransmissions on configured uplink grant is configured:
- cg-RetransmissionTimer: the duration after a configured grant (re)transmission of a HARQ process when the UE
shall not autonomously retransmit that HARQ process.
Upon configuration of a configured grant Type 1 for a BWP of a Serving Cell by upper layers, the MAC entity shall:
1> store the uplink grant provided by upper layers as a configured uplink grant for the indicated BWP of the Serving
Cell;
1> initialise or re-initialise the configured uplink grant to start in the symbol according to timeDomainOffset,
timeReferenceSFN, and S (derived from SLIV or provided by startSymbol as specified in TS 38.214 [7]), and to
reoccur with periodicity.
After an uplink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the
Nth (N >= 0) uplink grant occurs in the symbol for which:

(timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset ×
numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 × numberOfSlotsPerFrame ×
ETSI
After an uplink grant is configured for a configured grant Type 2, the MAC entity shall consider sequentially that the
Nth (N >= 0) uplink grant occurs in the symbol for which:

symbolstart time) + N × periodicity] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot).
If cg-nrofPUSCH-InSlot or cg-nrofSlots is configured for a configured grant Type 1 or Type 2, the MAC entity shall
consider the uplink grants occur in those additional PUSCH allocations as specified in clause 6.1.2.3 of TS 38.214 [7].
NOTE: In case of unaligned SFN across carriers in a cell group, the SFN of the concerned Serving Cell is used to
calculate the occurrences of configured uplink grants.
When the configured uplink grant is released by upper layers, all the corresponding configurations shall be released and
1> if at least one configured uplink grant confirmation has been triggered and not cancelled; and
2> if, in this MAC entity, at least one configured uplink grant is configured by
configuredGrantConfigToAddModList:
3> instruct the Multiplexing and Assembly procedure to generate a Multiple Entry Configured Grant
Confirmation MAC CE as defined in clause 6.1.3.31.
2> else:
3> instruct the Multiplexing and Assembly procedure to generate a Configured Grant Confirmation MAC CE
2> cancel all triggered configured uplink grant confirmation(s).
For a configured grant Type 2, the MAC entity shall clear the configured uplink grant(s) immediately after first
transmission of Configured Grant Confirmation MAC CE or Multiple Entry Configured Grant Confirmation MAC CE
which confirms the configured uplink grant deactivation.
Retransmissions use:
- repetition of configured uplink grants; or
- received uplink grants addressed to CS-RNTI; or
- configured uplink grants with cg-RetransmissionTimer configured.
[TS 38.300, clause 10.3]
The gNB may cancel a PUSCH transmission, or a repetition of a PUSCH transmission, or an SRS transmission of a UE
for another UE with a latency-critical transmission. The gNB can configure UEs to monitor cancelled transmission
indications using CI-RNTI on a PDCCH. If a UE receives the cancelled transmission indication, the UE shall cancel the
PUSCH transmission from the earliest symbol overlapped with the resource or the SRS transmission overlapped with
the resource indicated by cancellation (see clause 11.2A of TS 38.213 [38]).
In addition, with Configured Grants, the gNB can allocate uplink resources for the initial HARQ transmissions and
HARQ retransmissions to UEs. Two types of configured uplink grants are defined:
ETSI
deactivated.
If the UE is not configured with enhanced intra-UE overlapping resources prioritization, the dynamically allocated
uplink transmission overrides the configured uplink grant in the same serving cell, if they overlap in time. Otherwise an
uplink transmission according to the configured uplink grant is assumed, if activated.
If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant
transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant
transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest
priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in
MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a
dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes
the transmission based on the comparison between the priority of the logical channel which triggered the scheduling
request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can
be multiplexed in MAC PDU associated with the overlapping resource. In case the MAC PDU associated with a
deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a
retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission
using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is
not provided by the gNB.
Retransmissions other than repetitions are explicitly allocated via PDCCH(s) or via configuration of a retransmission
timer.
The UE may be configured with up to 12 active configured uplink grants for a given BWP of a serving cell. When more
than one is configured, the network decides which of these configured uplink grants are active at a time (including all of
them). Each configured uplink grant can either be of Type 1 or Type 2. For Type 2, activation and deactivation of
configured uplink grants are independent among the serving cells. When more than one Type 2 configured grant is
configured, each configured grant is activated separately using a DCI command and deactivation of Type 2 configured
grants is done using a DCI command, which can either deactivate a single configured grant configuration or multiple
configured grant configurations jointly.
When SUL is configured, the network should ensure that an active configured uplink grant on SUL does not overlap in
time with another active configured uplink grant on the other UL configuration.
For both dynamic grant and configured grant, for a transport block, two or more repetitions can be in one slot, or across
slot boundary in consecutive available slots with each repetition in one slot. For both dynamic grant and configured
grant Type 2, the number of repetitions can be also dynamically indicated in the L1 signalling. The dynamically
indicated number of repetitions shall override the RRC configured number of repetitions, if both are present.
Same Pre-test conditions as in clause 7.1.1.0 and UM DRB should be established on NR Cell 1.
ETSI

U-S Message
messageto configure UL configured grant type
1 in SFN 900, timeDomainOffset is set to 5.
RRCReconfigurationComplete message. RRCReconfigurationComplete)
3 SS transmits a DL MAC PDU containing 4 <-- MAC PDU (nine RLC SDUs) - -
RLC SDUs of size 96 bytes in SFN 1022 on
UM DRB. (Note 1)
containing first RLC SDU in Symbol ‘x0’, Slot
around?
Where
numberOfSymbolsPerSlot). (Note 2)
containing second RLC SDU in Symbol ‘x1’,
Slot y1’, SFN ‘z1’?
Where
message to add another configure UL
configured grant type 1 in SFN ‘z1 + 1’,
timeDomainOffset is set to 15.
RRCReconfigurationComplete message RRCReconfigurationComplete)
containing third RLC SDU in Symbol ‘x0’, Slot
around?
Where
containing fourth RLC SDU in Symbol ‘x2’, Slot
y2’, SFN ‘z2?
Where
containing fifth RLC SDU in Symbol ‘x1’, Slot
ETSI

around?
Where
containing sixth RLC SDU in Symbol ‘x3’, Slot
y3’, SFN ‘z3’?
Where
Note 1: According to the setting parameters in Table 7.1.1.6.2.3.3-2, TB size for configured grant type 1 is 808 bits,
which is enough to allow the UE to transmit one PDU at a time (96 bytes RLC SDU + 1 byte UM RLC
Header + 2 bytes MAC Sub PDU header + 2 bytes for short BSR or padding).
Note 2: S is the starting symbol relative to the slot of the first PUSCH transmission for new configured grant type 1.
The value of S can be obtained from TS 38.508-1 [4], Table 4.6.3-122.
 2μPUSCH 
Note 3: q is the slot where the UE shall transmit the PUSCH and is determined by K2 as n ⋅ μ  + K2
 2 PDCCH 
symbol relative to the start of the slot q according to TS 38.214 clause 6.1.2.1.
Note 4: The UL grant addressed to C-RNTI should result in UL transmission overlap in time domain as configured
grant type 1.

secondaryCellGroup Not Present
nonCriticalExtension := SEQUENCE{
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

cs-RNTI CHOICE {
setup SEQUENCE{
}
}
}
servCellIndex Not present
setup SEQUENCE {
sl20 10
}
}
}
}
configuredGrantConfigToAddModList-r16 2 entries
SEQUENCE (SIZE
(1..maxNrofConfiguredGrantConfig-r16)) OF
ConfiguredGrantConfig {
configuredGrantConfig[1] SEQUENCE { The first UL Grant Step1
configuration entry
38.508-1[4], Table
4.6.3-51
setup SEQUENCE {
}
}
}
1
p0-PUSCH-Alpha 1
repK n1
timeDomainOffset 5
ETSI
38.508-1 [4], Table

4.6.3-122
NBWPsize * (LRB-
1) + RBstart),
where
LRB = 2 PRB,
RBstart = 0,
NBWPsize is the
size [PRBs] of the
active carrier
bandwidth part and
contained in
TS.38.508-1 [4]
clause 4.3.1.1.
(SIZE(18), Equal to
NBWPsize * (LRB-
1) + RBstart),
where
LRB=9 PRB,
RBstart = 0and
NBWPsize is the
size [PRBs] of the
active carrier
bandwidth part and
contained in
TS.38.508-1 [4]
clause 4.3.1.2.
antennaPort 0
FR1_TDD
25 FR2_TDD
}
}
configuredGrantConfig[2] SEQUENCE { The second UL Step6
Grant configuration
entry
38.508-1[4], Table
4.6.3-51
setup SEQUENCE {
}
}
}
1
p0-PUSCH-Alpha 1
repK n1
ETSI

timeDomainOffset 15
38.508-1 [4], Table
4.6.3-122
NBWPsize * (LRB-
1) + RBstart),
where
LRB = 2 PRB,
RBstart = 0,
NBWPsize is the
size [PRBs] of the
active carrier
bandwidth part and
contained in
TS.38.508-1 [4]
clause 4.3.1.1.
(SIZE(18), Equal to
NBWPsize * (LRB-
1) + RBstart),
where
LRB=9 PRB,
RBstart = 0and
NBWPsize is the
size [PRBs] of the
active carrier
bandwidth part and
contained in
TS.38.508-1 [4]
clause 4.3.1.2.
antennaPort 0
FR1_TDD
25 FR2_TDD
}
}
}
setup SEQUENCE {
SEQUENCE {
k2 n8 FR1 and
FR2
mappingType typeB
startSymbolAndLength 0011011 Start symbol(S)=0, FR1
Length(L)=14
startSymbolAndLength 0001110 S=0, L=2 FR2
}
}
}
}
}
}
}
}
ETSI
7.1.1.7 Activation/Deactivation of SCells
7.1.1.7.1 Activation/Deactivation of SCells / Activation/Deactivation MAC control element

reception / sCellDeactivationTimer

reception / sCellDeactivationTimer / Intra-band Contiguous CA
(1)
with { UE in RRC_CONNECTED state with SCell configured }
ensure that {
when { UE receives an SCell Activation/Deactivation MAC CE activating the Scell }
then { UE starts monitoring PDCCH on activated SCell }
}
(2)
with(UE in RRC_CONNECTED state with SCell activated )
ensure that {
when{ UE receives a DL assignment on SCell PDCCH }
then { UE restarts the sCellDeactivationTimer }
}
(3)
with ( UE in RRC_CONNECTED state with SCell activated )
ensure that {
when{ UE sCellDeactivationTimer expires }
then { UE deactivates the SCell and stops monitoring PDCCH on SCell }
}
(4)
with (UE in RRC_CONNECTED state with SCell activated )
ensure that {
when{ UE receives a SCell Activation/Deactivation MAC CE deactivating the SCell }
then { UE deactivates the SCell and stops monitoring PDCCH on SCell }
}
(5)
with( UE in RRC_CONNECTED state with SCell activated and UL CA is supported)
ensure that {
when{ UE receives a UL assignment on SCell and has data available for transmission }
then { UE transmits the UL MAC PDU }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.321, clauses 5.9 and TS
38.331 clause 5.3.5.5.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.9]
If the MAC entity is configured with one or more SCells, the network may activate and deactivate the configured
SCells. Upon configuration of an SCell, the SCell is deactivated.
The configured SCell(s) is activated and deactivated by:
- receiving the SCell Activation/Deactivation MAC CE described in subclause 6.1.3.10;
- configuring sCellDeactivationTimer timer per configured SCell (except the SCell configured with PUCCH, if
any): the associated SCell is deactivated upon its expiry.
ETSI
The MAC entity shall for each configured SCell:
1> if an SCell Activation/Deactivation MAC CE is received activating the SCell:
2> activate the SCell according to the timing defined in TS 38.213 [6]; i.e. apply normal SCell operation
including:
3> SRS transmissions on the SCell;
3> CSI reporting for the SCell;
3> PDCCH monitoring on the SCell;
3> PDCCH monitoring for the SCell;
3> PUCCH transmissions on the SCell, if configured.
2> start or restart the sCellDeactivationTimer associated with the SCell in the slot when the SCell
Activation/Deactivation MAC CE was received;
2> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell
according to the stored configuration, if any, and to start in the symbol according to rules in subclause 5.8.2;
2> trigger PHR according to subclause 5.4.6.
1> else if an SCell Activation/Deactivation MAC CE is received deactivating the SCell; or
1> if the sCellDeactivationTimer associated with the activated SCell expires:
2> deactivate the SCell according to the timing defined in TS 38.213 [6];
2> stop the sCellDeactivationTimer associated with the SCell;
2> stop the bwp-InactivityTimer associated with the SCell;
2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell
respectively;
2> suspend any configured uplink grant Type 1 associated with the SCell;
2> flush all HARQ buffers associated with the SCell.
1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or
1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment
for the activated SCell; or
1> if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment:
2> restart the sCellDeactivationTimer associated with the SCell.
1> if the SCell is deactivated:
2> not transmit SRS on the SCell;
2> not report CSI for the SCell;
2> not transmit on UL-SCH on the SCell;
2> not transmit on RACH on the SCell;
2> not monitor the PDCCH on the SCell;
2> not monitor the PDCCH for the SCell;
2> not transmit PUCCH on the SCell.
ETSI
HARQ feedback for the MAC PDU containing SCell Activation/Deactivation MAC CE shall not be impacted by PCell,
PSCell and PUCCH SCell interruptions due to SCell activation/deactivation in TS 38.133 [11].
When SCell is deactivated, the ongoing Random Access procedure on the SCell, if any, is aborted.
[TS 38.321, clause 6.1.3.10]
The SCell Activation/Deactivation MAC CE of one octet is identified by a MAC PDU subheader with LCID as
specified in Table 6.2.1-1. It has a fixed size and consists of a single octet containing seven C-fields and one R-field.
The SCell Activation/Deactivation MAC CE with one octet is defined as follows (Figure 6.1.3.10-1).
The SCell Activation/Deactivation MAC CE of four octets is identified by a MAC PDU subheader with LCID as
specified in Table 6.2.1-1. It has a fixed size and consists of four octets containing 31 C-fields and one R-field. The
SCell Activation/Deactivation MAC CE of four octets is defined as follows (Figure 6.1.3.10-2).
For the case with no Serving Cell with a ServCellIndex as specified in TS 38.331 [8] larger than 7, SCell
Activation/Deactivation MAC CE of one octet is applied, otherwise SCell Activation/Deactivation MAC CE of four
octets is applied.
- Ci: If there is an SCell configured for the MAC entity with SCellIndex i as specified in TS 38.331 [8], this field
indicates the activation/deactivation status of the SCell with SCellIndex i, else the MAC entity shall ignore the Ci
field. The Ci field is set to "1" to indicate that the SCell with SCellIndex i shall be activated. The Ci field is set to
"0" to indicate that the SCell with SCellIndex i shall be deactivated;
- R: Reserved bit, set to "0".
C7 C6 C5 C4 C3 C2 C1 R Oct 1
Figure 6.1.3.10-1: SCell Activation/Deactivation MAC CE of one octet
C7 C6 C5 C4 C3 C2 C1 R Oct 1
C15 C14 C13 C12 C11 C10 C9 C8 Oct 2
C23 C22 C21 C20 C19 C18 C17 C16 Oct 3
C31 C30 C29 C28 C27 C26 C25 C24 Oct 4
Figure 6.1.3.10-2: SCell Activation/Deactivation MAC CE of four octets
Same Pre-test conditions as in clause 7.1.1.0 except that DRB is configured in RLC AM mode according to Table 7.1.1.
7.1.1.3.1-1 and in additionNR Cell 3 is configured as NR Active SCell.
Table 7.1.1. 7.1.1.3.1-1: RLC parameters
ETSI
Table 7.1.1.7.1.1.3.2-1: Time instances of cell power level and parameter changes
Parameter Unit NR Cell 1 NR Cell 3

SS/PBCH dBm/SC
T0 -85 -85
SSS EPRE S
ETSI

U-S Message
1 SS transmits an RRCReconfiguration <-- (RRCReconfiguration) - -
message to configure NR SCell(NR Cell 3).
Note 1
2 The UE transmits --> (RRCReconfigurationComplete) - -
2
3 The SS transmits Activation MAC control <-- MAC PDU (SCell - -
element to activate NR SCell on NR SpCell. Activation/Deactivation MAC CE
4 200 ms after step 3, the SS indicates a new <-- MAC PDU - -
transmission on PDCCH of SCell and
transmits a MAC PDU (containing an RLC
PDU)
5 Check: Does the UE transmit a Scheduling --> (SR) 1 P
Request on PUCCH?
6 The SS sends an UL grant suitable for <-- (UL Grant) - -
transmitting loop back PDU on NR SpCell.
7 The UE transmits a MAC PDU containing the --> MAC PDU - -
loop back PDU corresponding to step 4.
8 The SS transmits a MAC PDU containing RLC <-- MAC PDU - -
status PDU acknowledging reception of RLC
PDU in step 7 on NR SpCell
9 400 ms(sCellDeactivationTimer = 320 ms) <-- MAC PDU - -
after step 4, the SS indicates a new
transmission on PDCCH of NR SCell and
PDU)
10 Check: Does the UE transmit a Scheduling --> (SR) 2 F
Request on PUCCH in next 1 second?
11 The SS transmits Activation MAC control <-- MAC PDU ((SCell - -
element to activate SCell on NR SpCell. Activation/Deactivation MAC CE
12 200 ms after step 11 The SS indicates a new <-- MAC PDU - -
transmits a MAC PDU (containing just padding
or RLC status PDU, but no RLC data PDU)
13 400 ms after step 11 the SS indicates a new <-- MAC PDU - -
PDU)
14 Check: Does the UE transmit a Scheduling --> (SR) 1,3 P
Request on PUCCH?
15 The SS sends an UL grant suitable for <-- (UL Grant) - -
transmitting loop back PDU IF
pc_UL_NR_CA_2CC on NR SCell ELSE on
NR SpCell.
16 The UE transmits a MAC PDU containing the --> MAC PDU 5 P
loop back PDU corresponding to step 14
17 The SS transmits a MAC PDU containing RLC <-- MAC PDU - -
status PDU acknowledging reception of RLC
PDU in step 16
18 The SS transmits Deactivation MAC control <-- MAC PDU (SCell - -
element to de-activate SCell on NR SpCell. Activation/Deactivation MAC CE
19 The SS indicates a new transmission on <-- MAC PDU - -
PDCCH of NR SCell and transmits a MAC
PDU (containing an RLC PDU)
20 Check: Does the UE transmit a Scheduling --> (SR) 4 F
Request on PUCCH in the next 1 second?
ETSI

c1 CHOICE {
(CONTAINING
CellGroupConfig)
}
}
}
}
}

38.508-1 [4] table 4.6.3-
154
on
}
}
}

NR Cell 3
uplinkConfigCommon Not present Not
pc_UL_NR_
CA_2CC
}
ETSI

uplinkConfig Not present Not
pc_UL_NR_
CA_2CC
uplinkConfig SEQUENCE { pc_UL_NR_
CA_2CC
}
sCellDeactivationTimer ms320
}
Table 7.1.1.7.1.1.3.3-5: BWP-UplinkDedicated (Table 7.1.1.7.1.1.3.3-4)

pucch-Config Not present
}

reception / sCellDeactivationTimer / Inter-Band CA

reception / sCellDeactivationTimer / Intra-band non-Contiguous CA
- CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA
7.1.1.8 Bandwidth Part (BWP) operation
7.1.1.8.1 Bandwidth Part (BWP) operation UL/DL
(1)
ensure that {
when { UE receives BandwidthPart-Config IE included in RRC Message received on SpCell (i.e. PSCell
in case of EN-DC or PCell in case of SA) }
then { UE starts normal MAC operation in the FirstActive UL and DL Bandwidth part }
}
(2)
ensure that {
when { UE receives a DL DCI format 1_1 assigning a BWP different than the previously configured
BWP }
then { UE starts normal MAC operation in the received new BWP }
}
ETSI
(3)
with { UE in RRC_CONNECTED }
ensure that {
when { UE receives a UL DCI format 0_1 assigning a BWP different than the previously configured
BWP }
then { UE starts normal MAC operation in the received new BWP }
}
(4)
ensure that {
when { UE determines that a RACH Procedure is triggered in SpCell (i.e. PSCell in case of EN-DC or
PCell in case of SA) and PRACH occasions are not configured }
then { UE initiates the PRACH procedure in the initial BWP }
}
(5)
with { UE in RRC_Connected State with defaultDownlinkBWP configured }
ensure that {
when { UE bwp-InactivityTimer expires }
then { UE performs BWP switching to a BWP indicated by the defaultDownlinkBWP }
}
(6)
with { UE in RRC_Connected State with defaultDownlinkBWP configured and Active BWP is different than
defaultDownlinkBWP and bwp-InactivityTimer is running }
ensure that {
when { UE receives UL assignment or DL grant addressed to its C-RNTI }
then { UE restarts the bwp-InactivityTimer }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.211 clause 4.4.5, TS
38.212 clause 7.3.1.1.2 and 7.3.1.2.2, TS 38.321 clause 5.15 and TS 38.331 clause 5.3.5.3. Unless otherwise stated
[TS 38.211, clause 4.4.5]
A bandwidth part is a subset of contiguous common resource blocks defined in subclause 4.4.4.3 for a given
start,μ
numerology μ i in bandwidth part i on a given carrier. The starting position NBWP,i and the number of resource blocks
size,μ start,μ size,μ start,μ start,μ size,μ
x < NBWP,i + NBWP,i ≤ Ngrid,x + Ngrid,x ,
start,μ start,μ start,μ size,μ
x ≤ N BWP,i < N grid,x + N grid,x and
NBWP,i in a bandwidth part shall fulfil N grid, Ngrid,
respectively. Configuration of a bandwidth part is described in clause 12 of [5, TS 38.213].
A UE can be configured with up to four bandwidth parts in the downlink with a single downlink bandwidth part being
active at a given time. The UE is not expected to receive PDSCH, PDCCH, or CSI-RS (except for RRM) outside an
active bandwidth part.
A UE can be configured with up to four bandwidth parts in the uplink with a single uplink bandwidth part being active
at a given time. If a UE is configured with a supplementary uplink, the UE can in addition be configured with up to four
bandwidth parts in the supplementary uplink with a single supplementary uplink bandwidth part being active at a given
time. The UE shall not transmit PUSCH or PUCCH outside an active bandwidth part. For an active cell, the UE shall
not transmit SRS outside an active bandwidth part.
Unless otherwise noted, the description in this specification applies to each of the bandwidth parts. When there is no
risk of confusion, the index may be dropped from , , , and .
[TS 38.212, clause 7.3.1.1.2]
ETSI
RNTI or SP-CSI-RNTI or MCS-C-RNTI:
- Carrier indicator – 0 or 3 bits, as defined in Subclause 10.1 of [5, TS 38.213].
higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as
- nBWP = nBWP,RRC + 1 if nBWP,RRC ≤ 3 , in which case the bandwidth part indicator is equivalent to the ascending
order of the higher layer parameter BWP-Id;
[TS 38.212, clause 7.3.1.2.2]
RNTI or MCS-C-RNTI:
- Carrier indicator – 0 or 3 bits as defined in Subclause 10.1 of [5, TS 38.213].
higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as
- nBWP = nBWP, RRC + 1 if nBWP,RRC ≤ 3 , in which case the bandwidth part indicator is equivalent to the higher
[TS 38.321, clause 5.15]
In addition to clause 12 of TS 38.213 [6], this subclause specifies requirements on BWP operation.
A Serving Cell may be configured with one or multiple BWPs, and the maximum number of BWP per Serving Cell is
The BWP switching for a Serving Cell is used to activate an inactive BWP and deactivate an active BWP at a time. The
BWP switching is controlled by the PDCCH indicating a downlink assignment or an uplink grant, by the bwp-
InactivityTimer, by RRC signalling, or by the MAC entity itself upon initiation of Random Access procedure. Upon
RRC (re-)configuration of firstActiveDownlinkBWP-Id and/or firstActiveUplinkBWP-Id for SpCell or activation of an
SCell, the DL BWP and/or UL BWP indicated by firstActiveDownlinkBWP-Id and/or firstActiveUplinkBWP-Id
respectively (as specified in TS 38.331 [5]) is active without receiving PDCCH indicating a downlink assignment or an
uplink grant. The active BWP for a Serving Cell is indicated by either RRC or PDCCH (as specified in TS 38.213 [6]).
For unpaired spectrum, a DL BWP is paired with a UL BWP, and BWP switching is common for both UL and DL.
ETSI
For each activated Serving Cell configured with a BWP, the MAC entity shall:
1> if a BWP is activated:
2> transmit on UL-SCH on the BWP;
2> transmit on RACH on the BWP, if PRACH occasions are configured;
2> monitor the PDCCH on the BWP;
2> transmit PUCCH on the BWP, if configured;
2> report CSI for the BWP;
2> transmit SRS on the BWP, if configured;
2> receive DL-SCH on the BWP;
2> (re-)initialize any suspended configured uplink grants of configured grant Type 1 on the active BWP
according to the stored configuration, if any, and to start in the symbol according to rules in subclause 5.8.2.
1> if a BWP is deactivated:
2> not transmit on UL-SCH on the BWP;
2> not transmit on RACH on the BWP;
2> not monitor the PDCCH on the BWP;
2> not transmit PUCCH on the BWP;
2> not report CSI for the BWP;
2> not transmit SRS on the BWP;
2> not receive DL-SCH on the BWP;
2> clear any configured downlink assignment and configured uplink grant of configured grant Type 2 on the
BWP;
2> suspend any configured uplink grant of configured grant Type 1 on the inactive BWP.
Upon initiation of the Random Access procedure on a Serving Cell, after the selection of carrier for performing Random
Access procedure as specified in subclause 5.1.1, the MAC entity shall for the selected carrier of this Serving Cell:
1> if PRACH occasions are not configured for the active UL BWP:
2> switch the active UL BWP to BWP indicated by initialUplinkBWP;
2> if the Serving Cell is a SpCell:
3> switch the active DL BWP to BWP indicated by initialDownlinkBWP.
1> else:
2> if the Serving Cell is a SpCell:
3> if the active DL BWP does not have the same bwp-Id as the active UL BWP:
4> switch the active DL BWP to the DL BWP with the same bwp-Id as the active UL BWP.
1> stop the bwp-InactivityTimer associated with the active DL BWP of this Serving Cell, if running.
1> if the Serving Cell is SCell:
2> stop the bwp-InactivityTimer associated with the active DL BWP of SpCell, if running.
1> perform the Random Access procedure on the active DL BWP of SpCell and active UL BWP of this Serving
Cell.
ETSI
If the MAC entity receives a PDCCH for BWP switching of a Serving Cell, the MAC entity shall:
1> if there is no ongoing Random Access procedure associated with this Serving Cell; or
1> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon
reception of this PDCCH addressed to C-RNTI (as specified in subclauses 5.1.4 and 5.1.5):
2> perform BWP switching to a BWP indicated by the PDCCH.
If the MAC entity receives a PDCCH for BWP switching for a Serving Cell while a Random Access procedure
associated with that Serving Cell is ongoing in the MAC entity, it is up to UE implementation whether to switch BWP
or ignore the PDCCH for BWP switching, except for the PDCCH reception for BWP switching addressed to the C-
RNTI for successful Random Access procedure completion (as specified in subclauses 5.1.4 and 5.1.5) in which case
the UE shall perform BWP switching to a BWP indicated by the PDCCH. Upon reception of the PDCCH for BWP
switching other than successful contention resolution, if the MAC entity decides to perform BWP switching, the MAC
entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure after performing the
BWP switching; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue with the
ongoing Random Access procedure on the Serving Cell.
Upon reception of RRC (re-)configuration for BWP switching for a Serving Cell while a Random Access procedure
associated with that Serving Cell is ongoing in the MAC entity, the MAC entity shall stop the ongoing Random Access
procedure and initiate a Random Access procedure after performing the BWP switching.
The MAC entity shall for each activated Serving Cell configured with bwp-InactivityTimer:
1> if the defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by the
defaultDownlinkBWP-Id; or
1> if the defaultDownlinkBWP-Id is not configured, and the active DL BWP is not the initialDownlinkBWP:
2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received
on the active BWP; or
2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received
for the active BWP; or
2> if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment:
3> if there is no ongoing random access procedure associated with this Serving Cell; or
3> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed
upon reception of this PDCCH addressed to C-RNTI (as specified in subclauses 5.1.4 and 5.1.5):
4> start or restart the bwp-InactivityTimer associated with the active DL BWP.
2> if the bwp-InactivityTimer associated with the active DL BWP expires:
3> if the defaultDownlinkBWP-Id is configured:
4> perform BWP switching to a BWP indicated by the defaultDownlinkBWP-Id.
3> else:
4> perform BWP switching to the initialDownlinkBWP.
NOTE: If a Random Access procedure is initiated on an SCell, both this SCell and the SpCell are associated with
this Random Access procedure.
1> if a PDCCH for BWP switching is received, and the MAC entity switches the active DL BWP:
2> if the defaultDownlinkBWP-Id is configured, and the MAC entity switches to the DL BWP which is not
indicated by the defaultDownlinkBWP-Id; or
2> if the defaultDownlinkBWP-Id is not configured, and the MAC entity switches to the DL BWP which is not
the initialDownlinkBWP:
ETSI
[TS 38.331, clause 5.2.1]
System Information (SI) is divided into the MIB and a number of SIBs where:
- ...
- For a UE in RRC_CONNECTED, the network can provide system information through dedicated signalling
using the RRCReconfiguration message, e.g. if the UE has an active BWP with no common search space
configured to monitor system information or paging.
- For PSCell and SCells, the network provides the required SI by dedicated signalling, i.e. within an
RRCReconfiguration message. Nevertheless, the UE shall acquire MIB of the PSCell to get SFN timing of the
SCG (which may be different from MCG). Upon change of relevant SI for SCell, RAN releases and adds the
concerned SCell. For PSCell, SI can only be changed with Reconfiguration with Sync.
NOTE: The physical layer imposes a limit to the maximum size a SIB can take. The maximum SIB1 or SI
message size is 2976 bits.
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration:
...
1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCReconfiguration was received via SRB1:
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E-UTRA RRC message
RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG:
4> initiate the random access procedure on the SpCell, as specified in TS 38.321 [3];
...
NOTE: For EN-DC, in the case RRCReconfiguration is received via SRB1, the random access is triggered by
RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is
received via SRB3, the random access is triggered by the MAC layer due to arrival of
RRCReconfigurationComplete.
ETSI

U-S Message
0 The SS transmits <-- (RRCReconfiguration) - -
RRCReconfiguration to configure
the dedicated BWPs incl. the
FirstActive BWP. (Note 1) (Note
4).
- EXCEPTION: Steps 0Aa1 to 0Ab2 - - - -
describe behaviour which
depends on procedure
parameters; the "lower case letter"
identifies a step sequence that
take place if a procedure
0A IF Connectivity is EN-DC or --> (RRCReconfigurationComp - -
a1 NGEN-DC, the UE sends lete)
(Note 2).
0A IF Connectivity is NR, the SS <-- UL Grant - -
b1 allocates (transmitted in
FirstActiveDownlinkBWP) an UL
Grant with DCI format 0_1
indicating FirstActiveUplinkBWP
(BWP#1).
0A Check: Does the UE send --> (RRCReconfigurationComp 1 P
b2 RRCReconfigurationComplete in lete)
the FirstActive BWP configured?
(Note 2) (Note 3) (Note 5)
1 The SS transmits a valid MAC <-- MAC PDU - -
PDU containing RLC PDU in the
configured FirstActive Downlink
BWP configured.
2 After 100ms from step 1, the SS <-- UL Grant - -
allocates (transmitted in
FirstActiveDownlinkBWP) an UL
Grant.
SDU in the FirstActive BWP
configured? (Note 5)
4 Void - - - -
5 The SS indicates on PDCCH <-- MAC PDU - -
(transmitted in Downlink BWP#1)
DL DCI format 1_1 with new BWP
Id (= BWP #2) and transmits a
MAC PDU containing RLC PDU
on the newly configured BWP (i.e.
Downlink BWP#2).
6 After 100ms from step5, the SS <-- UL Grant - -
allocates (transmitted in Downlink
BWP#2) an UL Grant (with DCI
indicating BWP#2), sufficient for
loopback of the RLC SDU from
step 5 in a Slot. (Note 3)
SDU in the configured BWP (i.e.
Uplink BWP#2)? (Note 5)
8 Void - - - -
PDU containing RLC PDU in the
configured BWP (i.e. Downlink
BWP#2).
ETSI
10 After 100ms from step 9 the SS <-- UL Grant - -

indicates on PDCCH (transmitted
in Downlink BWP#2) UL DCI
format 0_1 with new BWP Id (=IF
pc_bwp_sameNumerology_upto4,
THEN BWP #3 ELSE BWP #1)
and allocates an UL Grant,
sufficient for loopback of the RLC
SDU from step 9 in a Slot.
SDU in the configured BWP (i.e.
(IF
THEN BWP #3 ELSE BWP #1, for
FDD and for TDD)? (Note 5)
A PDU containing RLC PDU in the
BWP#2 for FDD) or (IF
THEN BWP #3 ELSE BWP #1 for
TDD).
12 After 100ms from step 11A the SS <-- PDCCH Order - -
indicates PDCCH order on CSS (ra-PreambleIndex =
for contention-based random '000000'B)
access (transmitted in Downlink
BWP#2 for FDD OR (IF
THEN BWP #3 ELSE BWP #1 for
TDD).
13 Check: Does the UE send PRACH --> PRACH Preamble 4 P
Preamble in the initial BWP (UL
BWP#0)?
13 The SS transmits (in Downlink <-- Random Access Response - -
A BWP #0) a MAC PDU addressed
to UE RA-RNTI, containing RAR
with matching RAPID in MAC sub
header.
13 The UE sends (in UL BWP#0) a --> msg3 (C-RNTI MAC - -
B msg3 in the grant associated to CONTROL ELEMENT)
the received Random Access
Response.
13 SS schedules (in Downlink <-- Contention Resolution - -
C BWP#0) PDCCH transmission for
UE C-RNTI and allocates UL
grant sufficient for the UE to loop
back the data received at step
11a.
D MAC PDU including one RLC
SDU in the initial BWP (i.e. Uplink
BWP#0)? (Note 5)
14- Void - - - -
15
16 The SS indicates on PDCCH <-- MAC PDU - -
(transmitted in Downlink BWP#0)
DL DCI format 1_1 with BWP Id (=
BWP #1) and transmits a MAC
PDU containing RLC PDU on the
BWP#1).
17 After 400 ms from step 16, the SS <-- MAC PDU - -
transmits another valid MAC PDU
containing RLC PDU in the active
BWP (i.e. Downlink BWP#1).
ETSI
18 After 400 ms from step 17, the SS <-- UL Grant - -

allocates (transmitted in Downlink
BWP#1) an UL Grant (with DCI
indicating BWP#1), sufficient for
loopback of a MAC PDU
containing both RLC SDUs from
steps 16 and 17 in a Slot. (Note 3)
MAC PDU containing both RLC
SDUsin the active BWP (i.e.
Uplink BWP#1)? (Note 5)
20 The SS waits 1000 ms from step <-- MAC PDU - -
18 to ensure that the bwp-
InactivityTimer expired and then
transmits a valid MAC PDU
containing RLC PDU in the BWP
with defaultDownlinkBWP-Id (=
Downlink BWP#2).
21 The SS allocates (transmitted in <-- UL Grant - -
the defaultDownlinkBWP, i.e.
Downlink BWP#2) an UL Grant
(with DCI indicating BWP#2),
sufficient for loopback of the RLC
SDU from step 20 in a Slot. (Note
3)
MAC PDU in Uplink BWP#2 (=
BWP Id of the
defaultDownlinkBWP)? (Note 5)
Note 3: In paired spectrum (= FDD), the switching of Downlink BWP and Uplink BWP can happen
independently. Whereas in TDD, the switching of BWP for Downlink and Uplink is always at the same
time instance. Currently, the scope of the Test Purposes (TP) is considered to not cover checking of a
BWP deviation which results from non-synchronized Downlink and Uplink BWP switching in FDD.
Note 4: After the preamble the UE is in RRC_CONNECTED, therefore SRBs and DRBs are already
established. The RRCReconfiguration message in step 1 and step 14 shall not contain any elements
like e.g. "rlc-BearerToAddModList" whose value(s) remain unchanged since the preamble. The sole
purpose of the RRCReconfiguration message in step 1 and 14 is to configure BWPs and related fields
for switching of BWPs.
Note 5: When the UE does not use the expected BWP for the UL transmission the SS shall not receive the
data what implicitly fails the test case.
Table 7.1.1.8.1.3.3-0: Conditions for specific message contents
BWP#1 Bandwidth part 1
ETSI
Table 7.1.1.8.1.3.3-1: RRCReconfiguration (step 0)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 (see also Note 4 in Table 7.1.1.8.1.3.2-1)
}
}
}
}
Table 7.1.1.8.1.3.3-1A: CellGroupConfig (Table 7.1.1.8.1.3.3-1)

physicalCellGroupConfig Not present
servCellIndex Not present
ServCellIndex EN-DC
spCellConfigCommon Not present
rlf-TimersAndConstants Not present
spCellConfigDedicated ServingCellConfig- Table
Dedicated 7.1.1.8.1.3.3-2
}
reportUplinkTxDirectCurrent-v1530 true
}
ETSI
Table 7.1.1.8.1.3.3-2: ServingCellConfig-Dedicated (Table 7.1.1.8.1.3.3-1A)

tdd-UL-DL-ConfigurationDedicated Not present
TDD-UL-DL- TDD
ConfigDedicated
..initialDownlinkBWP ::= SEQUENCE {
pdcch-Config CHOICE {
release NULL
}
release NULL
}
}
downlinkBWP-ToAddModList SEQUENCE (SIZE 3 entries
(1..maxNrofBWPs)) BWP-Downlink {
BWP-Downlink[1] BWP-Downlink-BWP-N entry 1
with condition BWP#1
BWP-Downlink[2] BWP-Downlink-BWP-N entry 2
with condition BWP#2
BWP-Downlink[3] BWP-Downlink-BWP-N entry 3 pc_bwp_sa
with condition BWP#3 meNumerol
ogy_upto4
}
firstActiveDownlinkBWP-Id 1
bwp-InactivityTimer ms750
defaultDownlinkBWP-Id 2
initialUplinkBWP ::= SEQUENCE {
release NULL
}
release NULL
}
srs-Config CHOICE {
release NULL
}
}
uplinkBWP-ToReleaseList Not present
uplinkBWP-ToAddModList SEQUENCE (SIZE 3 entries
(1..maxNrofBWPs)) OF BWP-Uplink {
BWP-Uplink[1] BWP-Uplink-BWP-N with entry 1
condition BWP#1
BWP-Uplink[2] BWP-Uplink-BWP-N with entry 2
condition BWP#2
BWP-Uplink[3] BWP-Uplink-BWP-N with entry 3 pc_bwp_sa
condition BWP#3 meNumerol
ogy_upto4
}
firstActiveUplinkBWP-Id 1
pusch-ServingCellConfig Not present
}
pdcch-ServingCellConfig Not present
pdsch-ServingCellConfig Not present
csi-MeasConfig CSI-MeasConfig for TRS pc_bwp-
WithoutRest
riction =
True
}
ETSI
Table 7.1.1.8.1.3.3-2A: BWP-Downlink-BWP-N (Table 7.1.1.8.1.3.3-2 and Table 7.1.1.8.1.3.3-4)

BWP-Downlink ::= SEQUENCE {
bwp-Id 1 BWP#1
2 BWP#2
3 BWP#3
bwp-Common SEQUENCE {
genericParameters SEQUENCE {
locationAndBandwidth 1381 Note 1 BWP#1 and
pc_bwp-
WithoutRest
riction =
True
1387 Note 1 BWP#2 and
pc_bwp-
WithoutRest
riction =
True
pc_bwp-
WithoutRest
riction =
True
6600 Note 2 BWP#1,2,3
and
pc_bwp-
WithoutRest
riction =
False and
5MHz
pc_bwp-
WithoutRest
riction =
False
pc_bwp-
WithoutRest
riction =
False
pc_bwp-
WithoutRest
riction =
False
12925 Note 4 BWP#1and
pc_bwp-
WithoutRest
riction =
False and
100MHz
pc_bwp-
WithoutRest
riction =
False and
100MHz
pc_bwp-
WithoutRest
riction =
False and
100MHz
}
pdcch-ConfigCommon Not present no cell specific
configuration for
ETSI
dedicated BWP
pdsch-ConfigCommon Not present no cell specific
configuration for
dedicated BWP
}
bwp-Dedicated SEQUENCE {
setup PDCCH-Config-BWP-N
}
setup PDSCH-Config-BWP-N
}
}
}
size
Note 1: According to TS 38.214 [21] clause 5.1.2.2.2 with NBWP =275, LRBs=6 and RBStart=6,12,18 for BWP#1,2,3
size
Note 2: According to TS 38.214 [21] clause 5.1.2.2.2 with NBWP =275, LRBs=25 and RBStart=0 for BWP#1,2,3
size
Note 3: According to TS 38.214 [21] clause 5.1.2.2.2 with NBWP =275, LRBs=30,36,42 and RBStart=0 for BWP#1,2,3
size
Note 4: According to TS 38.214 [21] clause 5.1.2.2.2 with NBWP =275, LRBs=48,54,60 and RBStart=0 for BWP#1,2,3
Table 7.1.1.8.1.3.3-2B: PDCCH-Config-BWP-N (Table 7.1.1.8.1.3.3-2A)

controlResourceSetToAddModList SEQUENCE 2 entries
(SIZE (1..3)) OF ControlResourceSet {
ControlResourceSet[1] ControlResourceSet- entry 1
BWP-N with condition
BWP#N
}
searchSpacesToAddModList SEQUENCE (SIZE 1 entry
SearchSpace[1] SearchSpace-BWP-N entry 1
with condition BWP#N
SearchSpace[2] SearchSpace-CSS-BWP- entry 2
N with condition BWP#N
}
}
ETSI
Table 7.1.1.8.1.3.3-2C: PDSCH-Config (Table 7.1.1.8.1.3.3-2A)

tci-StatesToAddModList SEQUENCE(SIZE (1.. 2 entries pc_bwp-
maxNrofTCI-States)) OF TCI-State { WithoutRest
riction =
True
tci-StateId 0
cell ServCellIndex As per 38.508-1
Table 4.6.3-166
bwp-id Not present
ssb 1
}
qcl-Type type C
}
Table 4.6.3-166
bwp-id Not present BWP ID
ssb 1
}
qcl-Type type D
}
}
tci-StateId 1
Table 4.6.3-166
bwp-id 1 BWP#1
2 BWP#2
3 BWP#3
csi-rs 1
}
qcl-Type type A
}
Table 4.6.3-166
bwp-id 1 BWP#1
2 BWP#2
3 BWP#3
csi-rs 1
}
qcl-Type type D
}
}
}
PDSCH-TimeDomainAllocationList::= SEQUENCE { PDSCH-
TimeDomainResourceAll
ocationList
}
Table 7.1.1.8.1.3.3-2CA: PDSCH-TimeDomainResourceAllocationList (Table 7.1.1.8.1.3.3-2C)
ETSI
Derivation Path: TS 38.331 [6], clause 6.3.2

PDSCH-TimeDomainAllocationList::= SEQUENCE {
SEQUENCE {
k0 1 pc_bwp-
SwitchingDe
lay_Type1
AND
SCS_15KHz
3 pc_bwp_Swi
tchingDelay
_Type2
AND
SCS_15KHz
2 pc_bwp-
SwitchingDe
lay_Type1
AND
SCS_30KHz
5 pc_bwp_Swi
tchingDelay
_Type2
AND
SCS_30KHz
3 pc_bwp-
SwitchingDe
lay_Type1
AND
SCS_60KHz
9 pc_bwp_Swi
tchingDelay
_Type2
AND
SCS_60KHz
6 pc_bwp-
SwitchingDe
lay_Type1
AND
SCS_120KH
z
18 pc_bwp_Swi
tchingDelay
_Type2
AND
SCS_120KH
z
mappingType typeA
symbol(S)=2,
Length(L)=12
}
}
ETSI
Table 7.1.1.8.1.3.3-2D: ControlResourceSet-BWP-N (Table 7.1.1.8.1.3.3-2B)

controlResourceSetId 9 BWP#1
10 BWP#2
11 BWP#3
frequencyDomainResources 10000000 00000000 CORESET to use
00000000 00000000 the least
00000000 00000 significant 6 RBs
of each BWP
duration 2 SearchSpace
duration of 2
symbols
tci-StatesPDCCH-ToAddList SEQUENCE(SIZE 1 entry pc_bwp-
(1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId { WithoutRest
riction =
True
TCI-StateId[1] 1 TRS
}
}
Table 7.1.1.8.1.3.3-2E: SearchSpace-BWP-N (Table 7.1.1.8.1.3.3-2B)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-162 with condition USS

searchSpaceId 37 BWP#1
38 BWP#2
39 BWP#3
10 BWP#2
11 BWP#3
nrofCandidates SEQUENCE {
aggregationLevel1 n0
}
}
ETSI
Table 7.1.1.8.1.3.3-2F: BWP-Uplink-BWP-N (Table 7.1.1.8.1.3.3-2 and Table 7.1.1.8.1.3.3-4)
ETSI
BWP-Uplink ::= SEQUENCE {
bwp-Id 1 BWP#1
3GPP TS 38.523-1 version 16.9.0 Release 16 2 842 ETSI TS 138 523-1 V16.9.0
BWP#2(2021-12)
3 BWP#3
bwp-Common SEQUENCE {
genericParameters SEQUENCE {
locationAndBandwidth 1381 Note 1 BWP#1 and
pc_bwp-
WithoutRest
riction =
True
pc_bwp-
WithoutRest
riction =
True
pc_bwp-
WithoutRest
riction =
True
6600 Note 2 BWP#1,2,3
and
pc_bwp-
WithoutRest
riction =
False and
5MHz
pc_bwp-
WithoutRest
riction =
False
pc_bwp-
WithoutRest
riction =
False
pc_bwp-
WithoutRest
riction =
False
pc_bwp-
WithoutRest
riction =
False and
100MHz
pc_bwp-
WithoutRest
riction =
False and
100MHz
pc_bwp-
WithoutRest
riction =
False and
100MHz
}
rach-ConfigCommon Not present No cell specific
configuration for
dedicated BWP
pusch-ConfigCommon Not present no cell specific
configuration for
dedicated BWP
pucch-ConfigCommon PUCCH-ConfigCommon-
BWP-N
}
setup PUCCH-Config-BWP-N
}
pusch-Config CHOICE { ETSI
setup PUSCH-Config-BWP-N
5MHz According to TS 38.508-1 [4] clause 6.2.3.1 with CBW=5Mhz
100MHz According to TS 38.508-1 [4] clause 6.2.3.1 with CBW=100Mhz
Table 7.1.1.8.1.3.3-2G: PUCCH-Config-BWP-N (Table 7.1.1.8.1.3.3-2F)

PUCCH-Config::= SEQUENCE {
resourceSetToAddModList SEQUENCE (SIZE 1 entry
(1..4)) OF PUCCH-ResourceSet {
PUCCH-ResourceSet[1] SEQUENCE { entry 1
pucch-ResourceSetId 0
resourceList SEQUENCE (SIZE (1..32)) OF 1 entry
PUCCH-ResourceId {
PUCCH-ResourceId[1] 0 entry 1
}
maxPayloadSize 256
}
}
resourceToAddModList SEQUENCE (SIZE (1..128)) 1 entry
OF PUCCH-Resource {
PUCCH-Resource[1] SEQUENCE { entry 1
pucch-RessourceId 0
startingPRB 0 BWP#1
0 BWP#2
0 BWP#3
intraSlotFrequencyHopping disabled
secondHopPRB Not Present
format CHOICE {
format0 SEQUENCE {
initialCyclicShift 0
nrofSymbols 2
startingSymbolIndex 0
}
}
}
}
}
Table 7.1.1.8.1.3.3-2H: PUSCH-Config-BWP-N (Table 7.1.1.8.1.3.3-2F)

pusch-TimeDomainAllocationList PUSCH- TS 38.508-1 [4]
TimeDomainResourceAll Table 4.6.3-122
ocationList
}
ETSI
Table 7.1.1.8.1.3.3-3: PUCCH-ConfigCommon-BWP-N (Table 7.1.1.8.1.3.3-2F)

PUCCH-ConfigCommon ::= SEQUENCE {
pucch-ResourceCommon Not Present
pucch-GroupHopping enable
hoppingId Not present
p0-nominal Not Present
}
Table 7.1.1.8.1.3.3-4: SearchSpace-CSS-BWP-N (Table 7.1.1.8.1.3.3-2B)
Derivation Path: TS 38.508-1[4], Table 4.6.3-162 with condition CSS

searchSpaceId 30 BWP#1
31 BWP#2
32 BWP#3
10 BWP#2
11 BWP#3
nrofCandidates SEQUENCE {
}
}
}
ETSI
Table 7.1.1.8.1.3.3-5: CSI-MeasConfig for TRS (Table 7.1.1.8.1.3.3-2)
Derivation Path: TS 38.508-1[4] Table 4.6.3-38

CSI-MeasConfig::= SEQUENCE {
nzp-CSI-RS-ResourceToAddModList SEQUENCE 2 entries in case of FR2 2 entries in case
(SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP- 4 entries in case of FR1 of FR2
CSI-RS-Resource { 4 entries in case
of FR1
NZP-CSI-RS-Resource[1] NZP-CSI-RS-Resource entry 1
for TRS (1) CSI-RS resource
1
NZP-CSI-RS-Resource[2] NZP-CSI-RS-Resource entry 2
2
NZP-CSI-RS-Resource[3] NZP-CSI-RS-Resource entry 3 FR1
3
NZP-CSI-RS-Resource[4] NZP-CSI-RS-Resource entry 4 FR1
4
}
nzp-CSI-RS-ResourceSetToAddModList 1 entry
SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-
ResourceSets)) OF NZP-CSI-RS-ResourceSet {
NZP-CSI-RS-ResourceSet[1] NZP-CSI-RS- entry 1
ResourceSet for TRS
}
csi-IM-ResourceToAddModList Not present
csi-IM-ResourceSetToAddModList Not present
csi-SSB-ResourceSetToAddModList Not present
csi-ResourceConfigToAddModList SEQUENCE 1 entry
(SIZE (1..maxNrofCSI-ResourceConfigurations)) OF
CSI-ResourceConfig {
CSI-ResourceConfig[1] CSI-ResourceConfig for entry 1
TRS
}
reportTriggerSize Not present
aperiodicTriggerStateList SetupRelease Not present
}
Table 7.1.1.8.1.3.3-6: NZP-CSI-RS-ResourceSet for TRS (Table 7.1.1.8.1.3.3-5)

NZP-CSI-RS-ResourceSet ::= SEQUENCE {
nzp_CSI_ResourceSetId 0
nzp-CSI-RS-Resources SEQUENCE (SIZE 2 entries in case of FR2
(1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF 4 entries in case of FR1
NZP-CSI-RS-ResourceId {
CSI-RS resource 1
CSI-RS resource 2
NZP-CSI-RS-ResourceId[3] 2 entry 3 FR1
CSI-RS resource 3
NZP-CSI-RS-ResourceId[4] 3 entry 4 FR1
CSI-RS resource 4
}
repetition off
aperiodicTriggeringOffset Not present
trs_Info true
}
ETSI
Table 7.1.1.8.1.3.3-7: CSI-ResourceConfig for TRS (Table 7.1.1.8.1.3.3-5)

CSI-ResourceConfig ::= SEQUENCE {
csi-ResourceConfigId 0
csi-RS-ResourceSetList CHOICE {
nzp-CSI-RS-SSB SEQUENCE {
nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE 1 entry
(1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig))
OF NZP-CSI-RS-ResourceSetId {
NZP-CSI-RS-ResourceSetId[1] 0 entry 1
}
csi-SSB-ResourceSetList Not present
}
}
bwp-Id BWP-Id
resourceType periodic
}
Table 7.1.1.8.1.3.3-8: NZP-CSI-RS-Resource for TRS (Table 7.1.1.8.1.3.3-5)

nzp-CSI-RS-ResourceId 0 CSI-RS resource 1
1 CSI-RS resource 2
2 CSI-RS resource 3
3 CSI-RS resource 4
resourceMapping CSI-RS-
ResourceMapping for
TRS
powerControlOffset 0
periodicityAndOffset CSI-
ResourcePeriodicityAnd
Offset for TRS
qcl-InfoPeriodicCSI-RS TCI-StateId 0
7.1.1.9 MAC Reconfiguration and Reset
7.1.1.9.1 MAC Reset
(1)
Void
(2)
with { UE in RRC_CONNECTED state )
ensure that {
when{ UE MAC is reset, due to reconfiguration with sync on same cell }
then { UE considers the next transmission for each DL HARQ process as very first }
}
(3)
Void
(4)
with ( UE in RRC_CONNECTED state )
ETSI
ensure that {
then { UE flushes UL HARQ buffer }
}
(5)
with (UE in 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 present TC are specified in: TS 38.321, clauses 5.12 and TS
38.331 clause 5.3.5.5.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.12]
If a reset of the MAC entity is requested by upper layers, the MAC entity shall:
1> initialize Bj for each logical channel to zero;
1> stop (if running) all timers;
1> consider all timeAlignmentTimers as expired and perform the corresponding actions in subclause 5.2;
1> set the NDIs for all uplink HARQ processes to the value 0;
1> stop, if any, ongoing RACH procedure;
1> discard explicitly signalled contention-free Random Access Resources, if any;
1> flush Msg3 buffer;
1> cancel, if any, triggered Scheduling Request procedure;
1> cancel, if any, triggered Buffer Status Reporting procedure;
1> cancel, if any, triggered Power Headroom Reporting procedure;
1> flush the soft buffers for all DL HARQ processes;
1> for each DL HARQ process, consider the next received transmission for a TB as the very first transmission;
1> release, if any, Temporary C-RNTI;
1> reset BFI_COUNTER.
[TS 38.331, clause 5.3.5.5.2]
The UE shall perform the following actions to execute a reconfiguration with sync.
1> stop timer T310 for the corresponding SpCell, if running;
1> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the
reconfigurationWithSync;
1> if the frequencyInfoDL is included:
2> consider the target SpCell to be one on the frequency indicated by the frequencyInfoDL with a physical cell
identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the frequency of the source SpCell with a physical cell identity
indicated by the physCellId;
ETSI
1> start synchronising to the DL of the target SpCell;
1> apply the specified BCCH configuration defined in 9.1.1.1;
1> acquire the MIB, which is scheduled as specified in TS 38.213 [13];
1> perform the actions specified in clause 5.2.2.4.1
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the
RRC message triggering the reconfiguration with sync, which could be before confirming successful
reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing
information is not needed for random access.
1> reset the MAC entity of this cell group;
1> consider the SCell(s) of this cell group, if configured, to be in deactivated state;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group;
Editor's Note: Verify that this does not configure some common parameters which are later discarded due to e.g.
SCell release or due to LCH release.
1> configure lower layers in accordance with the received spCellConfigCommon;
1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the
received reconfigurationWithSync.
Table 7.1.1.9.1.3.1-1: Void
ETSI

U-S Message
0 The SS stops the default downlink - - - -
retransmission. (Note 4)
SS ignores scheduling requests and does not
allocate any uplink grant until after step 3
1 The SS transmits a MAC PDU containing one <-- MAC PDU (1 RLC SDU of 40 - -
RLC SDU with P field set 0 on DRB bytes on DRB)
2 Void - - - -
3 The SS transmits NR RRCReconfiguration <-- RRCReconfiguration - -
message with reconfigurationWithSync with
the same SpCell. (Note 1)
- EXCEPTION: Steps 4 and 4a can happen in - - - -
any order
4 The UE transmits an NR --> RRCReconfigurationComplete - -
2)
- EXCEPTION: UE may loop back the MAC - - - -
PDU sent at step 1 depending upon UE
implementation
4a The UE transmit a MAC PDU including one --> MAC PDU - -
RLC SDU
5 Void - - - -
5A The SS ignores scheduling requests and does
6 The SS transmits a MAC PDU containing RLC <-- MAC PDU (1 RLC SDU of 40 - -
SDU with P field set 0 on DRB. The HARQ bytes on DRB)
Process and NDI on PDCCH is same as in
step 1. The SS shall ensure that the HARQ
process used at step 1 will not be used in
between steps 3 and 5.
request?
- Exception: The SS ignores following - - - -
scheduling requests before step 9.
8 The SS allocates 1 UL Grant with size 384 bits <-- Uplink Grant - -
and NDI indicates new transmission. (Note 5)
9 The UE transmits a MAC PDU including one --> MAC PDU - -
RLC SDU with P field set 1.
9A The SS transmits a STATUS PDU. <-- STATUS PDU - -
10- Void - - - -
16
A not allocate any uplink grant.
SDU with P field set 0 on DRB. bytes on DRB)
18 The UE transmits a scheduling request --> (SR) - -
Exception: The SS ignores following - - - -
19 The SS allocates an UL Grant with size 384 <-- Uplink Grant - -
bits for one HARQ process X, and NDI
indicates new transmission. (Note 5)
20 The UE transmit a MAC PDU including one --> MAC PDU - -
RLC SDU with P field set 1.
20 The SS transmits a STATUS PDU. <-- STATUS PDU - -
A
21 Void
message with reconfigurationWithSync with
the same SpCelll. Note 1
ETSI
23 The UE transmits an NR RRCReconfigurationComplete - -

2
24 Void
A not allocate any uplink grant.
SDU with P field set 0 on DRB. The HARQ bytes on DRB)
Process and NDI on PDCCH is same as in
step 17. The SS shall ensure that the HARQ
process used at step 17 will not be used in
between steps 22 and 23.
26 The UE transmits a scheduling request --> (SR) - -
Exception: The SS ignores following - - - -
27 The SS allocates an UL Grant with with size <-- Uplink Grant - -
384 bits corresponding to HARQ process X,
with NDI not toggled compared to step 19, and
NDI indicates new transmission. (Note 5)
28 Check: Does UE transmit a MAC PDU --> MAC PDU 4,5 P
including one RLC SDU of 40 bytes on DRB
and P field is set 1?
Note 3: RLC re-establishment on DRB is used to make sure UE discard RLC PDU.
Note 4: The SS stops the default downlink retransmission to avoid HARQ ACK for the retransmission of DRB data
at step 1.
Note 5: The UL grant of 384 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit one
PDU at a time (40 bytes RLC SDU + 3 bytes RLC Header + 2 bytes MAC Sub PDU header + 2 bytes for
short BSR or padding).

sr-TransMax n64
Table 7.1.1.9.1.3.3-1: RRCReconfiguration for NR (steps 3 and 22 of Table 7.1.1.9.1.3.2-1)

radioBearerConfig RadioBearerConfig n set to the default NR
according to TS 38.508-1 DRB of the first
[4], table 4.6.3-132 with PDU session
with condition DRBn
according to TS 38.508-1
[4], table 4.6.3-19 with
condition PCell_change
}
}
}
}
ETSI
Table 7.1.1.9.1.3.3-2: RRCConnectionReconfiguration for EN-DC (step 3 and 22 of Table 7.1.1.9.1.3.2-

1)
Derivation Path: 36.508 Table 4.6.1-8

RRCConnectionReconfiguration ::= SEQUENCE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 ::= SEQUENCE
{
nonCriticalExtension ::= SEQUENCE {
nr-Config-r15 CHOICE {
nr-SecondaryCellGroupConfig-r15 OCTET STRING
including the
RRCReconfiguration
message and the IE
secondaryCellGroup
according TS 38.508-1
[67], table 4.6.1-13 with
condition EN-DC_HO
}
}
nr-RadioBearerConfig1-r15 OCTET STRING
including
RadioBearerConfig
[67], table 4.6.3-132 with
conditions EN-DC_DRB
}
}
}
}
}
}
7.1.1.10 Other Procedures
7.1.1.10.1 DataInactivityTimer expiry
(1)
with { UE in NR RRC_CONNECTED state and dataInactivityTimer configured and running }
ensure that {
when { UE receives or transmits MAC SDU from DRB }
then { UE restarts the dataInactivityTimer }
}
(2)
with { UE in NR RRC_CONNECTED state and dataInactivityTimer configured and running }
ensure that {
when { UE detecting data inactivity on expiry of DataInactivityTimer }
then { UE enters RRC_IDLE state }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.321 clause 5.19 and
TS 38.331 clause 5.3.8.5.
ETSI
[TS 38.321, clause 5.19]
The UE may be configured by RRC with a Data inactivity monitoring functionality, when in RRC_CONNECTED.
RRC controls Data inactivity operation by configuring the timer dataInactivityTimer.
When dataInactivityTimer is configured, the UE shall:
1> if any MAC entity receives a MAC SDU for DTCH logical channel, DCCH logical channel, or CCCH logical
channel; or
1> if any MAC entity transmits a MAC SDU for DTCH logical channel, or DCCH logical channel:
2> start or restart dataInactivityTimer.
1> if the dataInactivityTimer expires:
2> indicate the expiry of the dataInactivityTimer to upper layers.
[TS 38.331 clause 5.3.8.5]
Upon receiving the expiry of DataInactivityTimer from lower layers while in RRC_CONNECTED, the UE shall:
1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection
failure'.
System Simulator:
- NR Cell 1.
UE:
- None.
Preamble:
- The UE is in state 3N-A and Test Mode Activated according to 38.508-1 [4] Table 4.4A.2-1 with UE test loop
mode B is established IP PDU delay set to 6 seconds.
ETSI

U-S Message
1 The SS waits (dataInactivityTimer/2 + 1) - - - -
seconds
2 SS transmits a downlink assignment including <-- (PDCCH (C-RNTI)) - -
the C-RNTI assigned to the UE
assignment a RLC PDU in a MAC PDU.
4 Void - - - -
5 Void - - - -
6 Check: Does the UE transmits a MAC PDU --> MAC PDU (containing 1 MAC sub 1 P
containing Loop backed PDU on expiry of IP PDU containing RLC SDU)
PDU delay?
7- Repeat steps 1-6 - - - -
12
13 SS waits dataInactivityTimer seconds for the - - -
UE to enter RRC_IDLE.
indicate that the UE is in RRC_IDLE?
7.1.1.10.1.3.3 Specific Message Contents
Derivation path: 38.508-1[4], table 4.6.3-68

dataInactivityTimer s10
}
Table 7.1.1.10.1.3.3-2: CLOSE UE TEST LOOP (Preamble)
Derivation path: 36.508-1 [7] table 4.7A-3 condition UE test loop mode B
UE test loop mode B LB setup
IP PDU delay '0000 0110'B 6 seconds
7.1.1.10.2 Recommended Bit Rate
(1)
with { UE in RRC Connected state and MMTEL call established}
ensure that {
when { IF upper Layers requested to query the gNB for the recommended bit rate for a logical
channel and for a direction and bitRateQueryProhibitTimer is not running }
then { UE transmits a Recommended Bit Rate Query MAC Control Element}
}
(2)
with(UE in RRC Connected state and MMTEL call established)
ensure that {
when{ IF upper Layers requested to query the gNB for the recommended bit rate for a logical
channel and for a direction and bitRateQueryProhibitTimer is running}
then { UE does not transmits a Recommended Bit Rate Query MAC Control Element}
ETSI
(3)
with ( UE in RRC Connected state and MMTEL call established)
ensure that {
when{ UE receives MAC PDU from the gNB for the recommended bit rate for a logical channel and for
a direction }
then { UE sends an HARQ ACK }
}
[TS 38.321, clause 5.18.10]
The recommended bit rate procedure is used to provide the MAC entity with information about the bit rate which the
gNB recommends. The bit rate is the recommended bit rate of the physical layer. Averaging window of default value
2000 ms will apply as specified in TS 26.114 [13].
The gNB may transmit the Recommended bit rate MAC CE to the MAC entity to indicate the recommended bit rate for
the UE for a specific logical channel and a specific direction (either uplink or downlink). Upon reception of a
Recommended bit rate MAC CE the MAC entity shall:
- indicate to upper layers the recommended bit rate for the indicated logical channel and direction.
The MAC entity may request the gNB to indicate the recommended bit rate for a specific logical channel and a specific
direction. If the MAC entity is requested by upper layers to query the gNB for the recommended bit rate for a logical
channel and for a direction (i.e. for uplink or downlink), the MAC entity shall:
1> if a Recommended bit rate query for this logical channel and this direction has not been triggered:
2> trigger a Recommended bit rate query for this logical channel, direction, and desired bit rate.
If the MAC entity has UL resources allocated for new transmission the MAC entity shall:
1> for each Recommended bit rate query that the Recommended Bit Rate procedure determines has been triggered
and not cancelled:
2> if bitRateQueryProhibitTimer for the logical channel and the direction of this Recommended bit rate query is
configured, and it is not running; and
2> if the MAC entity has UL resources allocated for new transmission and the allocated UL resources can
accommodate a Recommended bit rate MAC CE plus its subheader as a result of LCP as defined in clause
5.4.3.1:
3> instruct the Multiplexing and Assembly procedure to generate the Recommended bit rate MAC CE for the
logical channel and the direction of this Recommended bit rate query;
3> start the bitRateQueryProhibitTimer for the logical channel and the direction of this Recommended bit
rate query;
3> cancel this Recommended bit rate query.
[TS 38.321, clause 6.1.20]
The Recommended bit rate MAC CE is identified by a MAC subheader with LCID as specified in Tables 6.2.1-1 and
6.2.1-2 for bit rate recommendation message from the gNB to the UE and bit rate recommendation query message from
the UE to the gNB, respectively. It has a fixed size and consists of two octets defined as follows (Figure 6.1.3.20-1):
- LCID: This field indicates the identity of the logical channel for which the recommended bit rate or the
recommended bit rate query is applicable. The length of the field is 6 bits;
ETSI
- Uplink/Downlink (UL/DL): This field indicates whether the recommended bit rate or the recommended bit rate
query applies to uplink or downlink. The length of the field is 1 bit. The UL/DL field set to 0 indicates downlink.
The UL/DL field set to 1 indicates uplink;
- Bit Rate: This field indicates an index to Table 6.1.3.20-1. The length of the field is 6 bits. For bit rate
recommendation the value indicates the recommended bit rate. For bit rate recommendation query the value
indicates the desired bit rate;
- R: reserved bit, set to 0.
UL/ Bit
LCID Oct 1
DL Rate
Bit Rate R R R Oct 2
Figure 6.1.3.20-1: Recommended bit rate MAC CE
Table 6.1.3.20-1: Values (kbit/s) for Bit Rate field
Index NR Index NR
Recommended Recommended
Bit Rate value Bit Rate value
[kbit/s] [kbit/s]
0 Note 1 32 700
1 0 33 800
2 9 34 900
3 11 35 1000
4 13 36 1100
5 17 37 1200
6 21 38 1300
7 25 39 1400
8 29 40 1500
9 32 41 1750
10 36 42 2000
11 40 43 2250
12 48 44 2500
13 56 45 2750
14 72 46 3000
15 88 47 3500
16 104 48 4000
17 120 49 4500
18 140 50 5000
19 160 51 5500
20 180 52 6000
21 200 53 6500
22 220 54 7000
23 240 55 7500
24 260 56 8000
25 280 57 Reserved
26 300 58 Reserved
27 350 59 Reserved
28 400 60 Reserved
29 450 61 Reserved
30 500 62 Reserved
31 600 63 Reserved
Note 1: For bit rate recommendation message this
index is used for indicating that no new
recommendation on bit rate is given.
ETSI
System Simulator:
- NR Cell 1
UE:
- None.
Preamble:
- The UE is in 5GS state 1N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
ETSI

U-S Message
1 The procedure in table 4.9.15.2.2-1 in TS - - - -
38.508-1 [4] is performed. The
bitRateQueryProhibitTimer for the Logical
channel of MMTEL QoS Flow is configured as
s3 (3 seconds).
2 Trigger the UE to perform Recommended Bit - - - -
Rate query for direction Downlink via AT
(+CGBRRREQ) or MMI command.
3 Check: Does the UE transmit a MAC PDU -> MAC PDU 1 P
containing Recommended bit rate MAC CE
with Uplink/Downlink (UL/DL) set as 0?
Rate query for direction Uplink via AT
6 SS transmits a MAC PDU containing <- MAC PDU - -
Recommended bit rate MAC CE with
Uplink/Downlink (UL/DL) set as 0 and Bit Rate
same as value received in step 5.
Rate query for direction Up Link via AT
containing Recommended bit rate MAC CE ?
9 While bitRateQueryProhibitTimer is running (3 - - - -
seconds) in UE, trigger the UE to perform
Recommended Bit Rate query for direction Up
Link via AT (+CGBRRREQ) or MMI command.
10 Check: While bitRateQueryProhibitTimer is -> MAC PDU 2 F
running, does the UE transmit a MAC PDU
containing Recommended bit rate MAC CE ?
11 Check: After bitRateQueryProhibitTimer -> MAC PDU 2 P
expires, does the UE transmit a MAC PDU
12 SS transmits a MAC PDU containing <- MAC PDU - -
Recommended bit rate MAC CE with
Uplink/Downlink (UL/DL) set as 1 and Bit Rate
same as value received in step 11.
Note: The bitRateQueryProhibitTimer is configured only for UL direction as per asn.1 definition.
None
ETSI
7.1.1.11 NR Dual Connectivity
7.1.1.11.1 DC power headroom reporting / PSCell activation and DL pathloss change

reporting
(1)
with { UE in RRC_CONNECTED state on Pcell }
ensure that {
when { PSCell is added }
then { UE transmits a Power Headroom Report for the PCell and PSCell }
}
(2)
with { UE in RRC_CONNECTED state with PSCell and with Power headroom reporting for phr-Tx-
PowerFactorChange }
ensure that {
when { the DL Pathloss has changed more than phr-Tx-PowerFactorChange dB and phr-ProhibitTimer is
running }
then { UE does not transmit a MAC PDU containing Power Headroom MAC Control Element }
}
(3)
with { UE in RRC_CONNECTED state with PSCell and with Power headroom reporting for phr-Tx-
PowerFactorChange }
ensure that {
when { the phr-ProhibitTimer expires and power headroom report is triggered due to DL Pathloss
change }
then { UE transmits a MAC PDU containing Power Headroom MAC Control Element for the Pcell and
PSCell }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.321 clause 5.4.6
[TS 38.321, clause 5.4.6]
changed in between.
ETSI
cancelled; and
transmit, plus its subheader, as a result of LCP as defined in clause 5.4.3.1:
2> if multiplePHR with value true is configured:
specified in clause 7.7 of TS 38.213 [6] for NR Serving Cell and clause 5.1.1.2 of TS 36.213 [17] for
E-UTRA Serving Cell;
3> if phr-Type2OtherCell with value true is configured:
UTRA MAC entity);
6> obtain the value for the corresponding PCMAX,f,c field for the SpCell of the other MAC entity
(i.e. E-UTRA MAC entity) from the physical layer.
ETSI
System Simulator:
- NR Cell 1 is the PCell and NR Cell 10 is the PSCell.
- System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in all cells.
UE:
- None.
Preamble:
- The UE is in state NR RRC_CONNECTED using generic procedure parameter Connectivity (NR-DC), Test
Mode (On) associated with UE test loop mode A configured on NR Cell 1 according to TS 38.508-1 [4], clause
4.5.4.
Table 7.1.1.11.1.3.2-0: Cell configuration power level changes over time for FR1
T0 Cell- dBm/SC -82 off
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
Table 7.1.1.11.1.3.2-0A: Cell configuration power level changes over time for FR2

T0 Cell- dBm/SC -82 off
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
specific RS S
EPRE
ETSI

U-S Message
1 The SS transmits UL grant to the UE at every <-- - - -
10ms in PDCCH occasion.
2 SS transmits NR RRCReconfiguration <-- RRCReconfiguration - -
message to configure to specific Power
Headroom parameters for NR Cell
containing Multiple-Entry PHR MAC CE?
(Note 1)
RRCReconfigurationComplete message
including nr-SCG-Response (Note 1)
5 Wait for T= 10% of prohibitPHR-Timer from - - - -
step 3
6 Reduce SS power level for NR PCell so as to - - - -
cause a DL_Pathloss change at UE by 5dB,
row T1 of Table 7.1.1.11.1.3.2-0/0A.
Multiple-Entry PHR MAC CE?
9 Increase SS power level for NR PCell so as to - - - -
row T2 of Table 7.1.1.11.1.3.2-0/0A.
Element?
12 Wait for T= 10% of prohibitPHR-Timer from - - - -
step 11
13 Reduce SS power level for NR PSCell so as to - - - -
row T3 of Table 7.1.1.11.1.3.2-0/0A.
Multiple-Entry PHR MAC CE?
16 Increase SS power level for NR PSCell so as - - - -
to cause a DL_Pathloss change at UE by 5dB,
row T4 of Table 7.1.1.11.1.3.2-0/0A.
Element?
19 The SS transmits an NR RRCReconfiguration <-- RRCReconfiguration - -
reporting
parameters
Note 2: Void.
ETSI
7.1.1.11.1.3.3 Specific Message Contents
Table 7.1.1.11.1.3.3-2: CellGroupConfig (step 2, Table 7.1.1.11.1.3.2-1)

phr-Config CHOICE {
setup SEQUENCE {
phr-Tx-PowerFactorChange dB3
multiplePHR true
dummy false
}
}
}
}
7.1.1.12 UE power saving
7.1.1.12.1 Void
7.1.1.12.2 Void
7.1.1.12.3 DRX adaptation / UE wakeup indication
(1)
with { UE in RRC_CONNECTED state and long DRX is configured and [(SFN * 10) + subframe number]
modulo (drx-LongCycle) = drx-StartOffset and DCP is configured }
ensure that {
when { UE receives a DCP indication with the value of wake-up indication is 1 }
then { UE starts the drx-onDurationTimer after drx-SlotOffset from the beginning of the subframe
and monitors the PDCCH }
}
(2)
with { UE in RRC_CONNECTED state and long DRX is configured and [(SFN * 10) + subframe number]
modulo (drx-LongCycle) = drx-StartOffset and DCP is configured }
ensure that {
when { UE receives ps-wakeup with the value configured true }
and monitors the PDCCH for OnDurationTimer PDCCH-Occasions }
}
(3)
with { UE in RRC_CONNECTED state long DRX is configured and [(SFN * 10) + subframe number] modulo
(drx-LongCycle) = drx-StartOffset and DCP is configured }
ensure that {
when { all DCP occasions in time domain occurred in DRX active time }
}
(4)
with { UE in RRC_CONNECTED state long DRX is configured and DCP is configured}
ETSI
ensure that {
when { all DCP occasions in time domain occurred during measurement gap }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.321, clause 5.7, TS
38.213, clause 10.3 and 7.3.1.3.7. Unless otherwise stated these are Rel-15 requirements.
[TS 38.321, clause 5.7]
activity for the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI,
TPC-PUSCH-RNTI, TPC-SRS-RNTI, and AI-RNTI. When using DRX operation, the MAC entity shall also monitor
PDCCH according to requirements found in other clauses of this specification. When in RRC_CONNECTED, if DRX
is configured, for all the activated Serving Cells, the MAC entity may monitor the PDCCH discontinuously using the
DRX operation specified in this clause; otherwise the MAC entity shall monitor the PDCCH as specified in TS 38.213
[6].
NOTE 1: If Sidelink resource allocation mode 1 is configured by RRC, a DRX functionality is not configured.
grant is expected by the MAC entity;
- ps-Wakeup (optional): the configuration to start associated drx-onDurationTimer in case DCP is monitored but
not detected;
- ps-TransmitOtherPeriodicCSI (optional): the configuration to report periodic CSI that is not L1-RSRP on
PUCCH during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated
drx-onDurationTimer is not started;
- ps-TransmitPeriodicL1-RSRP (optional): the configuration to transmit periodic CSI that is L1-RSRP on PUCCH
during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated drx-
onDurationTimer is not started.
Serving Cells may be configured by RRC in two groups. When RRC does not configure a secondary DRX group, there
is only one DRX group. When two DRX groups are configured each group of Serving Cells, which is called a DRX
group, is configured by RRC with its own set of parameters: drx-onDurationTimer, drx-InactivityTimer. When two
DRX groups are configured, the two groups share the following parameter values: drx-SlotOffset, drx-
ETSI
RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-

ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.
When a DRX cycle is configured, the Active Time for Serving Cells in a DRX group includes the time while:
- drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or
- drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any Serving Cell in the DRX group;

or
- ra-ContentionResolutionTimer (as described in clause 5.1.5) or msgB-ResponseWindow (as described in clause

5.1.4a) is running; or
- a Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4); or
entity among the contention-based Random Access Preamble (as described in clauses 5.1.4 and 5.1.4a).
1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower
layers:
For each DRX group, the MAC entity shall:
1> if drx-InactivityTimer for this DRX Group expires:
3> start or restart drx-ShortCycleTimer for this DRX Group in the first symbol after the expiry of drx-
InactivityTimer;
3> use the Short DRX Cycle for this DRX group.
2> else:
3> use the Long DRX cycle for this DRX group.
ETSI
1> if a DRX Command MAC CE is received:
3> start or restart drx-ShortCycleTimer for this DRX Group in the first symbol after the end of DRX
Command MAC CE reception;
3> use the Short DRX Cycle for both DRX groups.
2> else:
3> use the Long DRX cycle for both DRX groups.
1> if drx-ShortCycleTimer for this DRX Group expires:
2> use the Long DRX for this DRX Group cycle.
2> stop drx-ShortCycleTimer for both DRX groups;
2> use the Long DRX cycle for both DRX groups.
StartOffset) modulo (drx-ShortCycle):
StartOffset:
2> if DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6], clause 10.3:
3> if DCP indication associated with the current DRX Cycle received from lower layer indicated to start drx-
onDurationTimer, as specified in TS 38.213 [6]; or
3> if all DCP occasion(s) in time domain, as specified in TS 38.213 [6], associated with the current DRX
Cycle occurred in Active Time considering grants/assignments/DRX Command MAC CE/Long DRX
Command MAC CE received and Scheduling Request sent until 4 ms prior to start of the last DCP
occasion, or within BWP switching interruption length, or during a measurement gap; or
3> if ps-Wakeup is configured with value true and DCP indication associated with the current DRX Cycle
has not been received from lower layers:
2> else:
NOTE 2: In case of unaligned SFN across carriers in a cell group, the SFN of the SpCell is used to calculate the
DRX duration.
1> if the DRX group is in Active Time:
2> monitor the PDCCH on the Serving Cells in this DRX group as specified in TS 38.213 [6];
NOTE 3: When HARQ feedback is postponed by PDSCH-to-HARQ_feedback timing indicating a non-numerical

k1 value, as specified in TS 38.213 [6], the corresponding transmission opportunity to send the DL
HARQ feedback is indicated in a later PDCCH requesting the HARQ-ACK feedback.
ETSI
3> if the PDSCH-to-HARQ_feedback timing indicate a non-numerical k1 value as specified in TS 38.213

[6]:
4> start the drx-RetransmissionTimerDL in the first symbol after the PDSCH transmission for the
corresponding HARQ process.
2> if the PDCCH indicates a new transmission (DL or UL) on a Serving Cell in this DRX group:
3> start or restart drx-InactivityTimer for this DRX group in the first symbol after the end of the PDCCH
reception.
1> if DCP monitoring is configured for the active DL BWP as specified in TS 38.213 [6], clause 10.3; and
1> if the current symbol n occurs within drx-onDurationTimer duration; and
1> if drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause:
2> if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC
CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n when
evaluating all DRX Active Time conditions as specified in this clause:
3> not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 [7];
3> not report semi-persistent CSI configured on PUSCH;
3> if ps-TransmitPeriodicL1-RSRP is not configured with value true:
4> not report periodic CSI that is L1-RSRP on PUCCH.
3> if ps-TransmitOtherPeriodicCSI is not configured with value true:
4> not report periodic CSI that is not L1-RSRP on PUCCH.
1> else:
2> in current symbol n, if the DRX group would not be in Active Time considering grants/assignments
scheduled on Serving Cell(s) in this DRX Group and DRX Command MAC CE/Long DRX Command MAC
CE received and Scheduling Request sent until 4 ms prior to symbol n when evaluating all DRX Active Time
conditions as specified in this clause:
3> not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 [7] in this DRX group;
3> not report CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group.
Regardless of whether the MAC entity is monitoring PDCCH or not on the Serving Cells in this DRX group, the MAC
entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS defined in TS 38.214 [7] on the Serving
Cells in this DRX group when such is expected.
[TS 38.213, clause 10.3]
A UE configured with DRX mode operation [11, TS 38.321] on the PCell or on the SpCell [12, TS 38.331]
- a PS-RNTI for DCI format 2_6 by ps-RNTI
ETSI
- a number of search space sets, by dci-Format2-6, to monitor PDCCH for detection of DCI format 2_6 on the
active DL BWP of the PCell or of the SpCell according to a common search space as described in Clause 10.1
- a payload size for DCI format 2_6 by SizeDCI_2-6
- a location in DCI format 2_6 of a Wake-up indication bit by PSPositionDCI2-6, where
- the UE may not start the drx-onDurationTimer for the next long DRX cycle when a value of the Wake-up
indication bit is '0', and
- the UE starts the drx-onDurationTimer for the next long DRX cycle when a value of the Wake-up indication
bit is '1'
- a bitmap, when the UE is provided a number of groups of configured SCells by Scell-groups-for-dormancy-

outside-active-time, where
- the bitmap location is immediately after the Wake-up indication bit location
- the bitmap size is equal to the number of groups of configured SCells where each bit of the bitmap
corresponds to a group of configured SCells from the number of groups of configured SCells
- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by dormant-BWP, for the UE [11,
TS38.321] for each activated SCell in the corresponding group of configured SCells
- a '1' value for a bit of the bitmap indicates
- an active DL BWP, provided by first-non-dormant-BWP-ID-for-DCI-outside-active-time, for the UE for

each activated SCell in the corresponding group of configured SCells, if a current active DL BWP is the
dormant DL BWP
- a current active DL BWP, for the UE for each activated SCell in the corresponding group of configured
SCells, if the current active DL BWP is not the dormant DL BWP
- an offset by ps-Offset indicating a time, where the UE starts monitoring PDCCH for detection of DCI format 2_6
according to the number of search space sets, prior to a slot where the drx-onDuarationTimer would start on the
PCell or on the SpCell [11, TS 38.321]
- for each search space set, the PDCCH monitoring occasions are the ones in the first slots indicated by
duration, or slot if duration is not provided, starting from the first slot of the first slots and ending
prior to the start of drx-onDurationTimer.
The UE does not monitor PDCCH for detecting DCI format 2_6 during Active Time [11, TS 38.321].
If a UE reports for an active DL BWP a requirement of X slots prior to the beginning of a slot where the UE would start
the drx-onDurationTimer, the UE is not required to monitor PDCCH for detection of DCI format 2_6 during the X
slots, where X corresponds to the requirement of the SCS of the active DL BWP.
If a UE is provided search space sets to monitor PDCCH for detection of DCI format 2_6 in the active DL BWP of the
PCell or of the SpCell and the UE does not detect DCI format 2_6
- if the UE is provided ps-WakeupOrNot, the UE is indicated by ps-WakeupOrNot whether the UE may not start or
whether the UE shall start the drx-onDurationTimer for the next DRX cycle
- if the UE is not provided ps-WakeupOrNot, the UE may not start Active Time indicated by drx-onDurationTimer
for the next DRX cycle
PCell or of the SpCell and the UE
- is not required to monitor PDCCH for detection of DCI format 2_6, as described in Clauses 10, 11.1, 12, and in
Clause 5.7 of [14, TS 38.321] for all corresponding PDCCH monitoring occasions outside Active Time prior to a
next DRX cycle, or
- does not have any PDCCH monitoring occasions for detection of DCI format 2_6 outside Active Time of a next
DRX cycle
ETSI
the UE shall start the drx-onDurationTimer for the next DRX cycle.
If a UE is provided search space sets to monitor PDCCH for detection of DCI format 0_1 and DCI format 1_1 and if
one or both of DCI format 0_1 and DCI format 1_1 include a SCell dormancy indication field,
- the SCell dormancy indication field is a bitmap with size equal to a number of groups of configured SCells,
provided by Scell-groups-for-dormancy-within-active-time,
- each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured
Scells
- if the UE detects a DCI format 0_1 or a DCI format 1_1 that does not include a carrier indicator field, or detects
a DCI format 0_1 or DCI format 1_1 that includes a carrier indicator field with value equal to 0
- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by dormant-BWP, for the UE for each
activated SCell in the corresponding group of configured SCells
- an active DL BWP, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time, for the UE for each

activated SCell in the corresponding group of configured SCells, if a current active DL BWP is the dormant
DL BWP
- the UE sets the active DL BWP to the indicated active DL BWP
If a UE is provided search space sets to monitor PDCCH for detection of DCI format 1_1, and if
- the CRC of DCI format 1_1 is scrambled by a C-RNTI or a MCS-C-RNTI, and if
- resourceAllocation = resourceAllocationType0 and all bits of the frequency domain resource assignment field in
DCI format 1_1 are equal to 0, or
- resourceAllocation = resourceAllocationType1 and all bits of the frequency domain resource assignment field in
DCI format 1_1 are equal to 1
- resourceAllocation = dynamicSwitch and all bits of the frequency domain resource assignment field in DCI
format 1_1 are equal to 0 or 1
the UE considers the DCI format 1_1 as indicating SCell dormancy, not scheduling a PDSCH reception or indicating a
SPS PDSCH release, and for transport block 1 interprets the sequence of fields of
- modulation and coding scheme
- new data indicator
- redundancy version
and of
- HARQ process number
- antenna port(s)
- DMRS sequence initialization
as providing a bitmap to each configured SCell, in an ascending order of the SCell index, where
- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by dormant-BWP, for the UE for a
corresponding activated SCell
- an active DL BWP, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time, for the UE for a

corresponding activated SCell, if a current active DL BWP is the dormant DL BWP
ETSI
- a current active DL BWP, for the UE for a corresponding activated SCell, if the current active DL BWP is
not the dormant DL BWP
- the UE sets the active DL BWP to the indicated active DL BWP
If an active DL BWP provided by dormant-BWP for a UE on an activated SCell is not a default DL BWP for the UE on
the activated SCell, as described in Clause 12, the BWP inactivity timer is not used for transitioning from the active DL
BWP provided by dormant-BWP to the default DL BWP on the activated SCell.
A UE is expected to provide HARQ-ACK information in response to a detection of a DCI format 1_1 indicating SCell
dormancy after symbols from the last symbol of a PDCCH providing the DCI format 1_1. If
processingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell with the PDCCH providing
the DCI format 1_1, for , for , and for ; otherwise, for ,
for , for , and for , where is the smallest SCS configuration between the SCS
configuration of the PDCCH providing the DCI format 1_1 and the SCS configuration of a PUCCH with the HARQ-
ACK information in response to the detection of the DCI format 1_1.
[TS 38.213, clause 7.3.1.3.7]
DCI format 2_6 is used for notifying the power saving information outside DRX Active Time for one or more UEs.
The following information is transmitted by means of the DCI format 2_6 with CRC scrambled by PS-RNTI:
- block number 1, block number 2,…, block number N
where the starting position of a block is determined by the parameter PSPositionDCI2-6 provided by higher
layers for the UE configured with the block.
If the UE is configured with higher layer parameter PS-RNTI and dci-Format2-6, one block is configured for the UE by
higher layers, with the following fields defined for the block:
- Wake-up indication - 1 bit
- SCell dormancy indication – 0 bit if higher layer parameter Scell-groups-for-dormancy-outside-active-time is not

configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to higher layer parameter Scell-groups-
for-dormancy-outside-active-time, where each bit corresponds to one of the SCell group(s) configured by higher
layers parameter Scell-groups-for-dormancy-outside-active-time, with MSB to LSB of the bitmap corresponding
to the first to last configured SCell group.
The size of DCI format 2_6 is indicated by the higher layer parameter SizeDCI_2-6, according to Clause 10.3 of [5, TS
38.213].
ETSI

U-S Message
1 SS transmits RRCReconfiguration to configure <--
specific DCP parameters. (Note 1)
2 The UE transmits -->
3 Wait 1280ms to ensure UE is out DRX active
time.
4 The SS transmits DCI 2-6 on the PDCCH <-- (PDCCH (DCI 2-6))
within the PS-offset time before the start of
next long DRX drx-onDurationTimer and the
DCI 2-6 indicates to start the next Drx-
onDurationTimer.
5 In the first PDCCH occasion when the Drx- <-- MAC PDU
PDCCH.
ps-wakeup with value true. (Note 1)
time.
PDCCH.
specific DCP parameters. (Note 1)
time.
15 The SS transmits DCI 2-6 on the PDCCH <-- (PDCCH (DCI 2-6))
within the PS-offset time before the start of
next long DRX drx-onDurationTimer and the
DCI 2-6 indicates to start the next Drx-
onDurationTimer.
16 In the last PDCCH occasion when the Drx- <-- Invalid MAC PDU
the transmission of an invalid DL MAC PDU on
the PDCCH.
17 The UE transmit a HARQ NACK for the DL --> HARQ NACK
MAC PDU in Step 16.
18 In the PDCCH occasion when the next Drx- <-- MAC PDU
PDCCH.
specific measonfig parameters. (Note 1)
time.
ETSI
PDCCH.
Table 7.1.1.12.3.3.3-1: RRCReconfiguration (step 1, 7 and 12)
Derivation Path: TS 38.508-1 [6]

}
}
}
}

cellGroupId CellGroupId TS 38.508-1
default value
mac-CellGroupConfig ::= SEQUENCE {
drx-Config CHOICE {
setup DRX-Config TS 38.508-1
default value
}
}
physicalCellGroupConfig::= SEQUENCE {
dcp-Config-r16 CHOICE {
setup DCP-Config-r16 TS 38.508-1
default value
}
}
}
}
ETSI

initialDownlinkBWP ::= SEQUENCE {
pdcch-Config CHOICE { Step 1, Step
7, Step 12,
Step 20
setup PDCCH-Config
}
}
}
Table 7.1.1.12.3.3.3-4: PDCCH-Config (Table 7.1.1.12.3.3.3-3: BWP-DownlinkDedicated)

controlResourceSetToAddModList
}
searchSpacesToAddModList SEQUENCE(SIZE
searchSpace ::= SEQUENCE {
searchSpaceExt-r16 ::= SEQUENCE {
controlResourceSetId-r16 1
searchSpaceType-r16 SEQUENCE {
common SEQUENCE {
dci-Format2-6-r16 SEQUENCE {
}
}
}
}
}
}
}
Table 7.1.1.12.3.3.3-5: CellGroupConfig (Table 7.1.1.13.3.3.3-1: RRCReconfiguration step 7)

default value
drx-Config CHOICE {
default value
}
}
setup SEQUENCE {
ps-WakeUp-r16 true
}
}
}
}
ETSI

default value
drx-Config CHOICE {
setup SEQUENCE {
ms20 0
}
drx-SlotOffset ms0
}
setup SEQUENCE {
ps-Offset-r16 40
}
}
}
Table 7.1.1.12.3.3.3-7: RRCReconfiguration (step 20)

measConfig ::= SEQUENCE {
measGapConfig ::= SEQUENCE {
gapUE CHOICE {
setup SEQUENCE {
gapOffset 34
mgl ms6
mgrp ms40
mgta ms0
}
}
}
}
}
}
}
}
ETSI

default value
drx-Config CHOICE {
setup SEQUENCE {
ms40 39
}
drx-SlotOffset ms0
}
}
}
setup SEQUENCE {
ps-Offset-r16 40
}
}
}
}
7.1.1.12.4 DRX adaptation / SCell dormancy indication
7.1.1.12.4.1 DRX adaptation / SCell dormancy indication / Intra-band Contiguous CA
(1)
with { UE in RRC_CONNECTED state with Scell configured and long DRX is configured and DCP is
configured }
ensure that {
when { UE is outside DRX active time and receives the PDCCH indicating entering dormant BWP for
SCell }
then { UE activates the BWP indicated by dormantBWP-Id and stops monitoring the PDCCH}
}
(2)
with { UE in RRC_CONNECTED state with Scell configured and long DRX is configured and DCP is
configured }
ensure that {
when { UE is outside DRX active time and the active DL BWP is dormant BWP and receives the PDCCH
indicating leaving dormant BWP from SCell }
then { UE activates the BWP indicated by firstOutsideActiveTimeBWP-Id and starts normal MAC
operation on the new BWP }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.212, clause 7.3.1.3.7, TS
38.213, clause 10.3, TS 38.321, clause 5.15.1 and 5.9. Unless otherwise stated these are Rel-15 requirements.
[TS 38.212, clause 7.3.1.3.7]
DCI format 2_6 is used for notifying the power saving information outside DRX Active Time for one or more UEs.
ETSI
The following information is transmitted by means of the DCI format 2_6 with CRC scrambled by PS-RNTI:
- block number 1, block number 2,…, block number N
where the starting position of a block is determined by the parameter ps-PositionDCI-2-6 provided by higher
layers for the UE configured with the block.
If the UE is configured with higher layer parameter ps-RNTI and dci-Format2-6, one block is configured for the UE by
higher layers, with the following fields defined for the block:
- Wake-up indication - 1 bit
- SCell dormancy indication – 0 bit if higher layer parameter dormancyGroupOutsideActiveTime is not

configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to higher layer parameter
dormancyGroupOutsideActiveTime, where each bit corresponds to one of the SCell group(s) configured by
higher layers parameter dormancyGroupOutsideActiveTime, with MSB to LSB of the bitmap corresponding to
the first to last configured SCell group.
The size of DCI format 2_6 is indicated by the higher layer parameter sizeDCI-2-6, according to Clause 10.3 of [5, TS
38.213].
[TS 38.213, clause 10.3]
A UE configured with DRX mode operation [11, TS 38.321] can be provided the following for detection of a DCI
format 2_6 in a PDCCH reception on the PCell or on the SpCell [12, TS 38.331]
- a PS-RNTI for DCI format 2_6 by ps-RNTI
- a number of search space sets, by dci-Format2-6, to monitor PDCCH for detection of DCI format 2_6 on the
active DL BWP of the PCell or of the SpCell according to a common search space as described in Clause 10.1
- a payload size for DCI format 2_6 by sizeDCI_2-6
- a location in DCI format 2_6 of a Wake-up indication bit by psPositionDCI-2-6
- a '0' value for the Wake-up indication bit, when reported to higher layers, indicates to not start the drx-
onDurationTimer for the next long DRX cycle [11, TS 38.321]
- a '1' value for the Wake-up indication bit, when reported to higher layers, indicates to start the drx-
onDurationTimer for the next long DRX cycle [11, TS 38.321]
- a bitmap, when the UE is provided a number of groups of configured SCells by

dormancyGroupOutsideActiveTime, where
- the bitmap location is immediately after the Wake-up indication bit location
- the bitmap size is equal to the number of groups of configured SCells where each bit of the bitmap
corresponds to a group of configured SCells from the number of groups of configured SCells
- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by dormantBWP-Id, for the UE [11,
TS38.321] for each activated SCell in the corresponding group of configured SCells
- an active DL BWP, provided by firstOutsideActiveTimeBWP-Id, for the UE for each activated SCell in
the corresponding group of configured SCells, if a current active DL BWP is the dormant DL BWP
- an offset by ps-Offset indicating a time, where the UE starts monitoring PDCCH for detection of DCI format 2_6
according to the number of search space sets, prior to a slot where the drx-onDuarationTimer would start on the
PCell or on the SpCell [11, TS 38.321]
- for each search space set, the PDCCH monitoring occasions are the ones in the first slots indicated by
duration, or slot if duration is not provided, starting from the first slot of the first slots and ending
prior to the start of drx-onDurationTimer.
ETSI
On PDCCH monitoring occasions associated with a same long DRX Cycle, a UE does not expect to detect more than
one DCI format 2_6 with different values of the Wake-up indication bit for the UE or with different values of the
bitmap for the UE.
The UE does not monitor PDCCH for detecting DCI format 2_6 during Active Time [11, TS 38.321].
If a UE reports for an active DL BWP a requirement of X slots prior to the beginning of a slot where the UE would start
the drx-onDurationTimer, the UE is not required to monitor PDCCH for detection of DCI format 2_6 during the X
slots, where X corresponds to the requirement of the SCS of the active DL BWP in Table 10.3-1.
Table 10.3-1: Minimum time gap value X

Minimum Time Gap X (slots)
SCS (kHz)
Value 1 Value 2
15 1 3
30 1 6
60 1 12
120 2 24
PCell or of the SpCell and the UE detects DCI format 2_6, the physical layer of a UE reports the value of the Wake-up
indication bit for the UE to higher layers [11, TS 38.321] for the next long DRX cycle.
PCell or of the SpCell and the UE does not detect DCI format 2_6, the physical layer of the UE does not report a value
of the Wake-up indication bit to higher layers for the next long DRX cycle.
PCell or of the SpCell and the UE
- is not required to monitor PDCCH for detection of DCI format 2_6, as described in Clauses 10, 11.1, 12, and in
Clause 5.7 of [11, TS 38.321] for all corresponding PDCCH monitoring occasions outside Active Time prior to a
next long DRX cycle, or
- does not have any PDCCH monitoring occasions for detection of DCI format 2_6 outside Active Time of a next
long DRX cycle
the physical layer of the UE reports a value of 1 for the Wake-up indication bit to higher layers for the next long DRX
cycle.
If an active DL BWP provided by dormantBWP-Id for a UE on an activated SCell is not a default DL BWP for the UE
on the activated SCell, as described in Clause 12, the BWP inactivity timer is not used for transitioning from the active
DL BWP provided by dormantBWP-Id to the default DL BWP on the activated SCell.
[TS 38.321, clause 5.15.1]
In addition to clause 12 of TS 38.213 [6], this clause specifies requirements on BWP operation.
A Serving Cell may be configured with one or multiple BWPs, and the maximum number of BWP per Serving Cell is
The BWP switching for a Serving Cell is used to activate an inactive BWP and deactivate an active BWP at a time. The
BWP switching is controlled by the PDCCH indicating a downlink assignment or an uplink grant, by the bwp-
InactivityTimer, by RRC signalling, or by the MAC entity itself upon initiation of Random Access procedure or upon
detection of consistent LBT failure on SpCell. Upon RRC (re-)configuration of firstActiveDownlinkBWP-Id and/or
firstActiveUplinkBWP-Id for SpCell or activation of an SCell, the DL BWP and/or UL BWP indicated by
firstActiveDownlinkBWP-Id and/or firstActiveUplinkBWP-Id respectively (as specified in TS 38.331 [5]) is active
without receiving PDCCH indicating a downlink assignment or an uplink grant. The active BWP for a Serving Cell is
indicated by either RRC or PDCCH (as specified in TS 38.213 [6]). For unpaired spectrum, a DL BWP is paired with a
UL BWP, and BWP switching is common for both UL and DL.
ETSI
For each SCell a dormant BWP may be configured with dormantBWP-Id by RRC signalling as described in TS 38.331
[5]. Entering or leaving dormant BWP for SCells is done by BWP switching per SCell or per dormancy SCell group
based on instruction from PDCCH (as specified in TS 38.213 [6]). The dormancy SCell group configurations are
configured by RRC signalling as described in TS 38.331 [5]. Upon reception of the PDCCH indicating leaving dormant
BWP, the DL BWP indicated by firstOutsideActiveTimeBWP-Id or by firstWithinActiveTimeBWP-Id (as specified in
TS 38.331 [5] and TS 38.213 [6]) is activated. Upon reception of the PDCCH indicating entering dormant BWP, the DL
BWP indicated by dormantBWP-Id (as specified in TS 38.331 [5]) is activated. The dormant BWP configuration for
SpCell or PUCCH SCell is not supported.
For each activated Serving Cell configured with a BWP, the MAC entity shall:
1> if a BWP is activated and the active DL BWP for the Serving Cell is not the dormant BWP:
2> transmit on UL-SCH on the BWP;
2> transmit on RACH on the BWP, if PRACH occasions are configured;
2> monitor the PDCCH on the BWP;
2> transmit PUCCH on the BWP, if configured;
2> report CSI for the BWP;
2> transmit SRS on the BWP, if configured;
2> receive DL-SCH on the BWP;
2> (re-)initialize any suspended configured uplink grants of configured grant Type 1 on the active BWP
according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2;
2> if lbt-FailureRecoveryConfig is configured:
3> stop the lbt-FailureDetectionTimer, if running;
3> set LBT_COUNTER to 0;
3> monitor LBT failure indications from lower layers as specified in clause 5.21.2.
1> if a BWP is activated and the active DL BWP for the Serving Cell is dormant BWP:
2> stop the bwp-InactivityTimer of this Serving Cell, if running.
2> not monitor the PDCCH for the BWP;
2> not report CSI on the BWP, report CSI except aperiodic CSI for the BWP;
2> not transmit PUCCH on the BWP.
respectively;
2> if configured, perform beam failure detection and beam failure recovery for the SCell if beam failure is
detected.
1> if a BWP is deactivated:
ETSI
2> not transmit PUCCH on the BWP;
2> not report CSI for the BWP;
2> clear any configured downlink assignment and configured uplink grant of configured grant Type 2 on the
BWP;
2> suspend any configured uplink grant of configured grant Type 1 on the inactive BWP.
Upon initiation of the Random Access procedure on a Serving Cell, after the selection of carrier for performing Random
Access procedure as specified in clause 5.1.1, the MAC entity shall for the selected carrier of this Serving Cell:
1> if PRACH occasions are not configured for the active UL BWP:
2> switch the active UL BWP to BWP indicated by initialUplinkBWP;
2> if the Serving Cell is an SpCell:
3> switch the active DL BWP to BWP indicated by initialDownlinkBWP.
1> else:
2> if the Serving Cell is an SpCell:
3> if the active DL BWP does not have the same bwp-Id as the active UL BWP:
4> switch the active DL BWP to the DL BWP with the same bwp-Id as the active UL BWP.
1> stop the bwp-InactivityTimer associated with the active DL BWP of this Serving Cell, if running.
1> if the Serving Cell is SCell:
2> stop the bwp-InactivityTimer associated with the active DL BWP of SpCell, if running.
1> perform the Random Access procedure on the active DL BWP of SpCell and active UL BWP of this Serving
Cell.
If the MAC entity receives a PDCCH for BWP switching of a Serving Cell, the MAC entity shall:
1> if there is no ongoing Random Access procedure associated with this Serving Cell; or
1> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon
reception of this PDCCH addressed to C-RNTI (as specified in clauses 5.1.4, 5.1.4a, and 5.1.5):
2> cancel, if any, triggered consistent LBT failure for this Serving Cell;
2> perform BWP switching to a BWP indicated by the PDCCH.
If the MAC entity receives a PDCCH for BWP switching for a Serving Cell(s) or a dormancy SCell group(s) while a
Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, it is up to UE
implementation whether to switch BWP or ignore the PDCCH for BWP switching, except for the PDCCH reception for
BWP switching addressed to the C-RNTI for successful Random Access procedure completion (as specified in clauses
5.1.4, 5.1.4a, and 5.1.5) in which case the UE shall perform BWP switching to a BWP indicated by the PDCCH. Upon
reception of the PDCCH for BWP switching other than successful contention resolution, if the MAC entity decides to
perform BWP switching, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random
Access procedure after performing the BWP switching; if the MAC decides to ignore the PDCCH for BWP switching,
the MAC entity shall continue with the ongoing Random Access procedure on the Serving Cell.
ETSI
1> if a PDCCH for BWP switching is received, and the MAC entity switches the active DL BWP:
2> if the defaultDownlinkBWP-Id is configured, and the MAC entity switches to the DL BWP which is not
indicated by the defaultDownlinkBWP-Id and is not indicated by the dormantBWP-Id if configured; or
2> if the defaultDownlinkBWP-Id is not configured, and the MAC entity switches to the DL BWP which is not
the initialDownlinkBWP and is not indicated by the dormantBWP-Id if configured:
[TS 38.321, clause 5.9]
If the MAC entity is configured with one or more SCells, the network may activate and deactivate the configured
SCells. Upon configuration of an SCell, the SCell is deactivated unless the parameter sCellState is set to activated for
the SCell by upper layers.
The configured SCell(s) is activated and deactivated by:
- receiving the SCell Activation/Deactivation MAC CE described in clause 6.1.3.10;
- configuring sCellDeactivationTimer timer per configured SCell (except the SCell configured with PUCCH, if
any): the associated SCell is deactivated upon its expiry;
- configuring sCellState per configured SCell: if configured, the associated SCell is activated upon SCell
configuration.
The MAC entity shall for each configured SCell:
1> if an SCell is configured with sCellState set to activated upon SCell configuration, or an SCell
Activation/Deactivation MAC CE is received activating the SCell:
2> if the SCell was deactivated prior to receiving this SCell Activation/Deactivation MAC CE; or
2> if the SCell is configured with sCellState set to activated upon SCell configuration:
3> if firstActiveDownlinkBWP-Id is not set to dormant BWP:
4> activate the SCell according to the timing defined in TS 38.213 [6]; i.e. apply normal SCell operation
including:
5> SRS transmissions on the SCell;
5> CSI reporting for the SCell;
5> PDCCH monitoring on the SCell;
5> PDCCH monitoring for the SCell;
5> PUCCH transmissions on the SCell, if configured.
3> else (i.e. firstActiveDownlinkBWP-Id is set to dormant BWP):
4> stop the bwp-InactivityTimer of this Serving Cell, if running.
3> activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-
Id respectively.
2> start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS
38.213 [6];
2> if the active DL BWP is not the dormant BWP:
3> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this
SCell according to the stored configuration, if any, and to start in the symbol according to rules in clause
5.8.2.2;
ETSI
3> trigger PHR according to clause 5.4.6.
1> else if an SCell Activation/Deactivation MAC CE is received deactivating the SCell; or
1> if the sCellDeactivationTimer associated with the activated SCell expires:
2> deactivate the SCell according to the timing defined in TS 38.213 [6];
2> stop the sCellDeactivationTimer associated with the SCell;
2> stop the bwp-InactivityTimer associated with the SCell;
2> deactivate any active BWP associated with the SCell;
respectively;
2> clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell;
2> flush all HARQ buffers associated with the SCell;
2> cancel, if any, triggered consistent LBT failure for the SCell.
1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or
1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment
for the activated SCell; or
1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower
layers; or
2> restart the sCellDeactivationTimer associated with the SCell.
1> if the SCell is deactivated:
2> not transmit SRS on the SCell;
2> not report CSI for the SCell;
2> not transmit on UL-SCH on the SCell;
2> not transmit on RACH on the SCell;
2> not monitor the PDCCH on the SCell;
2> not monitor the PDCCH for the SCell;
2> not transmit PUCCH on the SCell.
HARQ feedback for the MAC PDU containing SCell Activation/Deactivation MAC CE shall not be impacted by PCell,
PSCell and PUCCH SCell interruptions due to SCell activation/deactivation in TS 38.133 [11].
When SCell is deactivated, the ongoing Random Access procedure on the SCell, if any, is aborted.
Same Pre-test conditions as in clause 7.1.1.0 except that Test loop function(Off) System information combination NR-4
and in addition NR Cell 3 is configured as NR Active Scell.
ETSI

T0 Cell- dBm/SC -88 off NR cell 1 is available and
specific RS S NR cell 3 is not available
EPRE
T1 Cell- dBm/SC -88 -88 NR cell 1 and NR cell 3
specific RS S are available
EPRE
T0 Cell- dBm/SC -82 off NR cell 1 is available and
specific RS S NR cell 3 is not available
EPRE
T1 Cell- dBm/SC -82 -82 NR cell 1 and NR cell 3
specific RS S are available
EPRE

U-S Message
0 Set the power levels according to “T1” as per
Table 7.1.1.12.4.1.3.2-1/2.
1 SS transmits an RRCReconfiguration <--
message. (Note 1)
2)
3 The SS transmits a SCell Activation MAC-CE <-- MAC PDU (SCell
to activate SCell (NR Cell 3). Activation/Deactivation MAC CE
4 The SS transmits DCI 2-6 within ps-Offset time <-- (PDCCH (DCI 2-6))
before the start of next long DRX drx-
onDurationTimer on NR Cell 1. (Note 3)
5 The SS indicates a new transmission on <-- MAC PDU
PDCCH of SCell and transmits a MAC PDU on
the dormant BWP (BWP#1) when the Drx-
onDurationTimer is running.
6 Check: Does the UE transmit a HARQ ACK for --> 1 F
7 The SS transmits DCI 2-6 within the ps-offset <-- (PDCCH (DCI 2-6))
time before the start of next long DRX drx-
onDurationTimer on NR Cell 1. (Note 4)
8 The SS indicates a new transmission on <-- MAC PDU
PDCCH of SCell and transmits a MAC PDU on
the active BWP (BWP#0) when the Drx-
onDurationTimer is running.
Note 3: The Wake-up indication is value 1 and the SCell dormancy indication is value 0 in the DCI 2-6.
Note 4: The Wake-up indication is value 1 and the SCell dormancy indication is value 1 in the DCI 2-6.
ETSI
Table 7.1.1.12.4.1.3.3-1: RRCReconfiguration (step 1)
Derivation Path: TS 38.508-1 [6]

}
}
}
}
Table 7.1.1.12.4.1.3.3-2: CellGroupConfig (Table 7.1.1.12.4.3.3-1: RRCReconfiguration)

default value
drx-Config CHOICE {
default value
}
}
setup DCP-Config-r16 TS 38.508-1
default value
}
}
servingCellConfig SEQUENCE {
setup PDCCH-Config
}
}
}
}
}
38.508-1 [4] table 4.6.3-
154
on
}
}
}
ETSI
Table 7.1.1.12.4.1.3.3-3: PDCCH-Config (Table 7.1.1.12.4.3.3-2: CellGroupConfig)

controlResourceSetToAddModList 1 entry
ControlResourceSet[1] ControlResourceSet TS 38.508-1
default value
}
searchSpacesToAddModListExt-r16
SEQUENCE(SIZE (1..10)) OF SearchSpace {
searchSpaceExt-r16 ::= SEQUENCE {
controlResourceSetId-r16 1
searchSpaceType-r16 SEQUENCE {
common SEQUENCE {
dci-Format2-6-r16 SEQUENCE {
}
}
}
}
}
}
Table 7.1.1.12.4.1.3.3-4: ServingCellConfigCommon (Table 7.1.1.12.4.3.3-2: CellGroupConfig)

NR Cell 3
}
Table 7.1.1.12.4.1.3.3-5: ServingCellConfig (Table 7.1.1.12.4.3.3-2: CellGroupConfig)

downlinkBWP-ToAddModList SEQUENCE (SIZE
(1..maxNrofBWPs)) BWP-Downlink {
BWP-Downlink BWP-Downlink
}
firstActiveDownlinkBWP-Id 0
dormancyGroupID-r16 0
dormantBWP-Config-r16 ::= SEQUENCE {
dormantBWP-Id-r16 1
outsideActiveTimeConfig-r16 CHOICE {
setup SEQUENCE {
firstOutsideActiveTimeBWP-Id-r16 0
dormancyGroupOutsideActiveTime-r16 0
}
}
}
}
ETSI
Table 7.1.1.12.4.1.3.3-6: BWP-Downlink (Table 7.1.1.12.4.3.3-5: ServingCellConfig)

BWP-Downlink ::= SEQUENCE {
bwp-Id 1 BWP#1
bwp-Common Not present
setup SEQUENCE {
controlResourceSetToAddModList 1 entry
SEQUENCE(SIZE (1..3)) OF ControlResourceSet {
ControlResourceSet[1] ControlResourceSet TS 38.508-1
default value
}
controlResourceSetToReleaseList Not present
}
}
}
}
7.1.1.12.4.2 DRX adaptation / SCell dormancy indication / Intra-band non Contiguous CA
7.1.1.12.4.3 DRX adaptation / SCell dormancy indication / Inter-band CA
7.1.2 RLC
Editor’s note: Intended to capture tests of RLC Layer behaviour defined in TS 38.322
7.1.2.1 Default Pre-Test Conditions for all RLC test cases

The following pre-test conditions shall be applied in all RLC test cases until the test case explicitly over writes these
conditions.
7.1.2.1.1 Default Pre-Test Conditions for AM RLC test cases
System Simulator:
- The SS configures the test environment in accordance to the execution conditions in Table 7.1.2.1.1-1.
UE:
- None
Preamble:
execution conditions in Table 7.1.2.1.1-2 and the message condition UE TEST LOOP MODE A to return one
UL PDCP SDU per DL PDCP SDU.
ETSI
Table 7.1.2.1.1-1: Test environment

Combination
IF pc_NG_RAN_NR NR Cell 1 NR: System information
Combination NR-1

NR: N/A
NR: N/A
Table 7.1.2.1.1-2: Preamble parameters

Execution Condition Multi-PDN / Multi- Generic Procedure Parameters Primary DRB used for
Condition
One DRB
TRUE Connectivity(NR),
N DRBs (N ≥ 2)
bearer),
bearer),
bearer),
bearer),
Table 7.1.2.1.1-3: Message conditions

Condition
IF Message with condition AM is used for step 7 in
pc_NG_RAN_NR 4.5.4.2 according to [4]
ELSE IF Message condition MCG_and_SCG with condition
pc_EN_DC SCG-DRB(1,0) is used for step 7 in 4.5.4.2 according
to [4]
pc_NGEN_DC SCG-DRB(1,0) is used for step 7 in 4.5.4.2 according
to [4]
7.1.2.1.2 Default Pre-Test Conditions for UM RLC test cases

Same Pre-test conditions as in clause 7.1.2.1.1 with the exceptions in Table 7.1.2.1.2-1.
ETSI
Table 7.1.2.1.2-1: Message conditions

Condition
IF Message with condition UM is used for step 7 in
pc_NG_RAN_NR 4.5.4.2 according to [4]
pc_EN_DC SCG-DRB(0,1) is used for step 7 in 4.5.4.2 according
to [4]
pc_NGEN_DC SCG-DRB(0,1) is used for step 7 in 4.5.4.2 according
to [4]
7.1.2.2 RLC Unacknowledged mode
7.1.2.2.1 UM RLC / Segmentation and reassembly / 6-bit SN / Segmentation Info (SI) field
(1)
with { UE in RRC_CONNECTED state configured for 6 bit SN in RLC UM }
ensure that {
when { UE receives UMD PDU containing a SI field set to 00 }
then { UE correctly decodes the received UMD PDU }
}
(2)
ensure that {
when { UE receives a 6 bit SN configured UMD PDU containing a SI field set to 01 }
}
(3)
ensure that {
when { UE receives a 6 bit SN configured UMD PDU containing a SI field set to 11 and SO field }
}
(4)
ensure that {
}
(5)
ensure that {
when { UE has UL SDU to send and UL grant available is sufficient to send whole SDU in one PDU }
then { UE transmits RLC SDU containing a SI field set to 00 }
}
(6)
ensure that {
when { UE has UL SDU to send and UL grant available is not sufficient to send whole SDU in one PDU
}
ETSI
then { UE transmits first RLC SDU segment containing a SI field set to 01 and including 6 bit SN
}
}
(7)
ensure that {
}
then { UE transmits middle RLC SDU segment containing a SI field set to 11, including SO field
and including 6 bit SN }
}
(8)
ensure that {
}
then { UE transmits last RLC SDU segment containing a SI field set to 10, including SO field and
including 6 bit SN }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.322, clauses 5.2.2.2.1,
5.2.2.2.2, 6.2.3.4 and 6.2.2.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.2.2.2.1]
The receiving UM RLC entity shall maintain a reassembly window according to state variable RX_Next_Highest as
follows:
- a SN falls within the reassembly window if (RX_Next_Highest – UM_Window_Size) <= SN

<RX_Next_Highest;
- a SN falls outside of the reassembly window otherwise.
When receiving an UMD PDU from lower layer, the receiving UM RLC entity shall:
- either deliver the UMD PDU after removing the RLC header, discard the received UMD PDU, or place it in the
reception buffer (see sub clause 5.2.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-Reassembly as
needed (see sub clause 5.2.2.2.3).
When t-Reassembly expires, the receiving UM RLC entity shall:
- update state variables, discard RLC SDU segments and start t-Reassembly as needed (see sub clause 5.2.2.2.4).
[TS 38.322, clause 5.2.2.2.2]
When an UMD PDU is received from lower layer, the receiving UM RLC entity shall:
- if the UMD PDU header does not contain an SN:
- remove the RLC header and deliver the RLC SDU to upper layer.
- else if (RX_Next_Highest – UM_Window_Size) <= SN < RX_Next_Reassembly:
- discard the received UMD PDU.
- else:
- place the received UMD PDU in the reception buffer.
ETSI
[TS 38.322, clause 6.2.2.3]
UMD PDU consists of a Data field and an UMD PDU header. The UMD PDU header is byte aligned
When an UMD PDU contains a complete RLC SDU, the UMD PDU header only contains the SI and R fields.
An UM RLC entity is configured by RRC to use either a 6 bit SN or a 12 bit SN. An UMD PDU header contains the SN
field only when the corresponding RLC SDU is segmented. An UMD PDU carrying the first segment of an RLC SDU
does not carry the SO field in its header. The length of the SO field is 16 bits.
SI R R R R R R Oct 1
Data Oct 2
...
Oct N
Figure 6.2.2.3-1: UMD PDU containing a complete RLC SDU
SI SN Oct 1
Data Oct 2
...
Oct N
Figure 6.2.2.3-2: UMD PDU with 6 bit SN (No SO)
SI R R SN Oct 1
SN Oct 2
Data Oct 3
...
Oct N
Figure 6.2.2.3-3: UMD PDU with 12 bit SN (No SO)
SI SN Oct 1
SO Oct 2
SO Oct 3
Data Oct 4
...
Oct N
Figure 6.2.2.3-4: UMD PDU with 6 bit SN and with SO
ETSI
SI R R SN Oct 1
SN Oct 2
SO Oct 3
SO Oct 4
Data Oct 5
...
Oct N
Figure 6.2.2.3-5: UMD PDU with 12 bit SN and with SO
[TS 38.322, clause 6.2.3.4]
Length: 2 bits.
The SI field indicates whether a RLC PDU contains a complete RLC SDU or the first, middle, last segment of a RLC
SDU.
Table 6.2.2.6-1: SI field interpretation
Value Description
00 Data field contains all bytes of a RLC SDU
01 Data field contains the first segment of a RLC SDU
10 Data field contains the last segment of a RLC SDU
11 Data field contains neither the first nor last segment of a RLC SDU
Same Pre-test conditions as in clause 7.1.2.1.2 with the exception for the UM DRB is configured according to Table
7.1.2.2.1.3.1-1.
Uplink UM RLC sn-FieldLength size6

Downlink UM RLC sn-FieldLength size6
ETSI

U-S Message
0 The SS stops allocating any UL grant. - - - -
1 The SS transmits UMD PDU#1 containing a <-- UMD PDU#1 - -
complete RLC SDU#1 (SI field = 00).
2 SS allocates an UL grant sufficient to loop <-- UL Grant - -
back RLC SDU#1 in one RLC/MAC PDU
3 Check: Does the UE transmit RLC SDU#1? --> (RLC SDU#1) 1,5 P
4 The SS transmits UMD PDU#2 containing the <-- UMD PDU#2 - -
first segment of RLC SDU#2 (SI field = 01).
Note 3
second segment of RLC SDU#2 (SI field = 11)
and including SO field. Note 3
last segment of RLC SDU#2 (SI field = 10) and
including SO field. Note 3
7 SS allocates 3 UL grants at an interval of 20 <-- UL Grants - -
ms so as to loop back RLC SDU#2 in 3
RLC/MAC PDUs. Note 1 & 2
8 Check: Does the UE transmit UMD PDU#2 --> (RLC SDU#2, first segment) 2,3, P
containing the first segment of RLC SDU#2 (SI 4,6
field = 01)?
9 Check: Does the UE transmit UMD PDU#3 --> (RLC SDU#2, second segment) 2,3, P
containing the second segment of RLC SDU#2 4,7
(SI field = 11) and including SO field?
10 Check: Does the UE transmit UMD PDU#4 --> (RLC SDU#2, last segment) 2,3, P
containing the last segment of RLC SDU#2 (SI 4,8
field = 10) and including SO field?
Note 1: The UL grants for step 8,9,10 are sufficiently small (240 bits, LRBs & IMCS as per 38.523-3[3] annex B) that UE
transmits RLC SDU#2 in 3 UL RLC PDUs by segmenting.
Note 2: The RLC PDU containing a segment shall be of size 208 bits resp. 224 bits and a MAC sub PDU header of
16 bits and a 16-bit MAC BSR CE included in step 8 resulting in a MAC PDU of size 240 bits.
Note 3: The data part in step 4 first segment not including SO is 200 bits (25 bytes). Step 5, second segment SO=25
and data is 200 bits (25 bytes). Step 6, third segment SO=25+25=50 and data is 200 bits (25 bytes).
None.
7.1.2.2.2 UM RLC / Segmentation and reassembly / 12-bit SN / Segmentation Info (SI)

field
(1)
ensure that {
when { UE receives UMD PDU containing a SI field set to 00 }
}
(2)
ensure that {
when { UE receives a 12 bit SN configured UMD PDU containing a SI field set to 01 }
}
ETSI
(3)
ensure that {
}
(4)
ensure that {
}
(5)
ensure that {
when { UE has UL SDU to send and UL grant available is sufficient to send whole SDU in one PDU }
then { UE transmits RLC SDU containing a SI field set to 00 }
}
(6)
ensure that {
}
then { UE transmits first RLC SDU segment containing a SI field set to 01 and including 12 bit
SN}
}
(7)
ensure that {
}
then { UE transmits middle RLC SDU segment containing a SI field set to 11, including SO field
and including 12 bit SN }
}
(8)
ensure that {
}
then { UE transmits last RLC SDU segment containing a SI field set to 10, including SO field and
including 12 bit SN }
}
Same conformance requirements as clause 7.1.2.2.1.2
7.1.2.2.2.3.1-1.
ETSI

Same test procedure sequence as 7.1.2.2.1.3.2 except that RLC UM SN is 12 bit and the data part in step 4 first segment
not including SO is 192 bits (24 Bytes). Step 5, second segment SO=24 and data is 192 bits (24 bytes). Step 6, third
segment SO=24+24=48 and data is 192 bits (24 bytes).
None.
7.1.2.2.3 UM RLC / 6-bit SN / Correct use of sequence numbering
(1)
with { UE in RRC_CONNECTED state with UM RLC 6 bit SN }
ensure that {
when { UE transmits the first PDU which is segmented }
then { UE includes the SN field equal to 0 in each RLC segment }
}
(2)
ensure that {
when { UE transmit subsequent segmented PDUs }
then { UE includes the SN field incremented by 1 for each segmented PDU of one RLC SDU }
}
(3)
ensure that {
when { UE transmit segments belonging to more than 64 SDUs }
then { UE wraps the SN after transmitting the segments of 64 SDUs }
}
(4)
ensure that {
when { segments of more than 64 SDUs are sent to UE }
then { UE accepts PDUs with SNs that wrap around every 64 segmented SDUs }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.322, clause
5.2.2.1.1, 5.2.2.2, 6.2.2.3, 6.2.3.3 and 7.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.2.2.1.1]
When submitting a UMD PDU to lower layer, the transmitting UM RLC entity shall:
- if the UMD PDU contains a segment of an RLC SDU, set the SN of the UMD PDU to TX_Next;
- if the UMD PDU contains a segment that maps to the last byte of an RLC SDU, then increment TX_Next by
one.
ETSI
[TS 38.322, clause 5.2.2.2]
follows:

<RX_Next_Highest;
- else:
When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall:
- if all byte segments with SN = x are received:
- reassemble the RLC SDU from all byte segments with SN = x, remove RLC headers and deliver the
reassembled RLC SDU to upper layer;
- if x = RX_Next_Reassembly:
- update RX_Next_Reassembly to the SN of the first SN > current RX_Next_Reassembly that has not been
reassembled and delivered to upper layer.
- else if x falls outside of the reassembly window:
- update RX_Next_Highest to x + 1;
- discard any UMD PDUs with SN that falls outside of the reassembly window;
- if RX_Next_Reassembly falls outside of the reassembly window:
- set RX_Next_Reassembly to the SN of the first SN >= (RX_Next_Highest – UM_Window_Size) that has
not been reassembled and delivered to upper layer.
[TS 38.322, clause 6.2.2.3]
field only when the corresponding RLC SDU is segmented.
[TS 38.322, clause 6.2.3.3]
ETSI
The SN field indicates the sequence number of the corresponding RLC SDU. …. For RLC UM, the sequence number is
incremented by one for every segmented RLC SDU..
[TS 38.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 63 for 6 bit SN or from 0 to 4095 for 12 bit SN.
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 64 for 6 bit SN and 4096 for 12 bit
SN).
Each transmitting UM RLC entity shall maintain the following state variables:
a) TX_Next
This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU with segment. It is
initially set to 0, and is updated after the UM RLC entity submits a UMD PDU including the last segment of an RLC
SDU to lower layers.
Each receiving UM RLC entity shall maintain the following state variables and constant:
b) RX_Next_Reassembly – UM receive state variable
This state variable holds the value of the earliest SN that is still considered for reassembly. It is initially set to 0.
c) RX_Timer_Trigger – UM t-Reassembly state variable
This state variable holds the value of the SN following the SN which triggered t-Reassembly.
d) RX_Next_Highest– UM receive 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. It serves as the higher edge of the reassembly window. It is initially set to 0.
7.1.2.2.3.3.1-1.

ETSI

U-S Message
1 The SS transmits UMD PDU#1 with 6 bit SN = <-- UMD PDU#1 - -
0 containing the first segment of RLC SDU#1
(SI field = 01).
2 The SS transmits UMD PDU#2 with 6 bit SN=0 <-- UMD PDU#2 - -
containing the last segment of RLC SDU#1 (SI
field = 10) and including SO field.
RLC/MAC PDUs. (Note 1)
4 Check: Does the UE transmit UMD PDU#1 --> (RLC SDU#1, first segment) 1 P
with 6 bit SN = 0 containing the first segment
of RLC SDU#1 (SI field = 01)?
5 Check: Does the UE transmit UMD PDU#2 --> (RLC SDU#1, last segment) 1 P
with 6 bit SN = 0 containing the last segment
- EXCEPTION: Steps 6 to 10 are executed 63 - - - -
times, the initial value of k = 1, it is
incremented by one for each iteration.
6 The SS transmits UMD PDU#(2*k+1) with 6 bit <-- UMD PDU#(2*k+1) - -
SN = k containing the first segment of RLC
SDU#(k+1) (SI field = 01).
7 The SS transmits UMD PDU#(2*(k+1)) with 6 <-- UMD PDU#(2*(k+1)) - -
bit SN=k containing the last segment of RLC
SDU#(k+1) (SI field = 10)
ms so as to loop back RLC SDU#(k+1) in 2
9 Check: Does the UE transmit UMD --> (RLC SDU#(k+1), first segment) 2 P
PDU#(2*k+1) with 6 bit SN = k containing the
first segment of RLC SDU#(k+1) (SI field =
01)? (Note 2)
10 Check: Does the UE transmit UMD --> (RLC SDU#(k+1), last segment) 2 P
PDU#(2*(k+1)) with 6 bit SN = k containing the
last segment of RLC SDU#(k+1) (SI field = 10)
and including SO field? (Note 2)
11 The SS transmits UMD PDU#129 with 6 bit SN <-- UMD PDU#129 - -
= 0 containing the first segment of RLC
SDU#65 (SI field = 01).
12 The SS transmits UMD PDU#130 with 6 bit <-- UMD PDU#130 - -
SN= 0 containing the last segment of RLC
SDU#65 (SI field = 10) and including SO field
14 Check: Does the UE transmit UMD PDU#129 --> (RLC SDU#65, first segment) 3.4 P
15 Check: Does the UE transmit UMD PDU#130 --> (RLC SDU#65, last segment) 3,4 P
of RLC SDU#65 (SI field = 10) and including
SO field?
Note 1: The RLC SDU size shall be 12 octets which are segmented into 6 and 6 octets. With 2 octets of MAC
header, 2 octets of Short BSR and 1 octet of RLC header (without SO) the first segment consists of 88 bits
and a TBS of this size shall be allocated. With 2 octets of MAC header and 3 octets of RLC header (with SO)
the second segment consists of 88 bits and a TBS of this size shall be allocated. (LRBs & IMCS as per 38.523-
3[3] annex B)
Note 2: The verdict shall be provided each time (SN+1) mod 16 = 0.
ETSI
None.
7.1.2.2.4 UM RLC / 12-bit SN / Correct use of sequence numbering
(1)
ensure that {
when { UE transmits the first PDU which is segmented }
then { UE includes the SN field equal to 0 in each RLC segment }
}
(2)
ensure that {
when { UE transmit subsequent segmented PDUs }
then { UE includes the SN field incremented by 1 for each segmented PDU of one RLC SDU}
}
(3)
ensure that {
when { UE transmit segments belonging to more than 4096 SDUs }
then { UE wraps the SN after transmitting the segments of 4096 SDUs }
}
(4)
ensure that {
when { segments of more than 4096 SDUs are sent to UE }
then { UE accepts PDUs with SNs that wrap around every 4096 segmented SDUs }
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.322, clause
5.2.2.1.1, 5.2.2.2, 6.2.2.3, 6.2.3.3 and 7.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.2.2.1.1]
When submitting a UMD PDU to lower layer, the transmitting UM RLC entity shall:
- if the UMD PDU contains a segment of an RLC SDU, set the SN of the UMD PDU to TX_Next;
- if the UMD PDU contains a segment that maps to the last byte of an RLC SDU, then increment TX_Next by
one.
[TS 38.322, clause 5.2.2.2]
follows:

<RX_Next_Highest;
ETSI
- else:
[TS 38.322, clause 6.2.2.3]
field only when the corresponding RLC SDU is segmented.
[TS 38.322, clause 6.2.3.3]
The SN field indicates the sequence number of the corresponding RLC SDU. … For RLC UM, the sequence number is
incremented by one for every segmented RLC SDU.
[TS 38.322, clause 7.1]
ETSI
SN).
a) TX_Next
7.1.2.2.4.3.1-1.
Uplink RLC sn-FieldLength size12

Downlink RLC sn-FieldLength size12
ETSI

U-S Message
1 The SS transmits UMD PDU#1 with 12 bit SN <-- UMD PDU#1 - -
= 0 containing the first segment of RLC SDU#1
(SI field = 01).
SN=0 containing the last segment of RLC
SDU#1 (SI field = 10) and including SO field
4 Check: Does the UE transmit UMD PDU#1 --> (RLC SDU#1, first segment) 1 P
5 Check: Does the UE transmit UMD PDU#2 --> (RLC SDU#1, last segment) 1 P
- EXCEPTION: Steps 6 to 10 are executed 4095 - - - -
times, the initial value of k = 1, it is
incremented by one for each iteration.
6 The SS transmits UMD PDU#(2*k+1) with 12 <-- UMD PDU#(2*k+1) - -
bit SN = k containing the first segment of RLC
SDU#(k+1) (SI field = 01).
7 The SS transmits UMD PDU#(2*(k+1)) with 12 <-- UMD PDU#(2*(k+1)) - -
bit SN=k containing the last segment of RLC
SDU#(k+1) (SI field = 10)
ms so as to loop back RLC SDU#(k+1) in 2
9 Check: Does the UE transmit UMD --> (RLC SDU#(k+1), first segment) 2 P
PDU#(2*k+1) with 12 bit SN = k containing the
first segment of RLC SDU#(k+1) (SI field =
01)? (Note 2)
10 Check: Does the UE transmit UMD --> (RLC SDU#(k+1), last segment) 2 P
PDU#(2*(k+1)) with 12 bit SN = k containing
the last segment of RLC SDU#(k+1) (SI field =
10) and including SO field? (Note 2)
SN = 0 containing the first segment of RLC
SDU#4097 (SI field = 01).
SN= 0 containing the last segment of RLC
SDU#4097 (SI field = 10) and including SO
field
14 Check: Does the UE transmit UMD PDU#8193 --> (RLC SDU#4097, first segment) 3.4 P
15 Check: Does the UE transmit UMD PDU#8194 --> (RLC SDU#4097, last segment) 3,4 P
of RLC SDU#4097 (SI field = 10) and including
SO field?
Note 1: The RLC SDU size shall be 10 octets which are segmented into 5 and 5 octets. With 2 octets of MAC
header, 2 octets of Short BSR and 2 octets of RLC header (without SO) the first segment consists of 88 bits
and a TBS of this size shall be allocated. With 2 octets of MAC header and 4 octets of RLC header (with SO)
the second segment consists of 88 bits and a TBS of this size shall be allocated. (LRBs & IMCS as per 38.523-
3[3] annex B)
Note 2: The verdict shall be provided each time (SN+1) mod 256 = 0.
ETSI
None.
7.1.2.2.5 UM RLC / Receive Window operation and t-Reassembly expiry
(1)
with { UE in RRC_CONNECTED state and using UM RLC }
ensure that {
when { UE receives a RLC PDU including SN and '(RX_Next_Highest – UM_Window_Size) <= SN <
RX_Next_Highest }
then { UE discards any UMD PDUs with SN that falls outside of the reassembly window }
}
(2)
ensure that {
when { UE receives a RLC PDU including SN and '(RX_Next_Highest – UM_Window_Size) > SN or SN >=
RX_Next_Reassembly' }
then { UE stores the PDU in receive buffer }
}
(3)
ensure that {
when { UE places a RLC PDU including SN into the reception buffer and all byte segments with that
SN are received }
then { UE delivers the reassembled SDU to upper layers}
}
(4)
ensure that {
when { t-Reassembly expires }
then { UE updates RX_Next_Reassembly and discards all segments with SN < updated
RX_Next_Reassembly }
}
5.2.2.2.2, 5.2.2.2.3, 5.2.2.2.4 and 7.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.2.2.2.1]
follows:

<RX_Next_Highest;
- either deliver the UMD PDU to upper layer after removing the RLC header, discard the received UMD PDU, or
place it in the reception buffer (see sub clause 5.2.2.2.2);
ETSI
- update state variables, discard RLC SDU segments and start t-Reassembly as needed (see sub clause 5.2.2.2.4).
[TS 38.322, clause 5.2.2.2.2]
- else:
[TS 38.322, clause 5.2.2.2.3]
- if t-Reassembly is running:
- if RX_Timer_Trigger <= RX_Next_Reassembly; or
- if RX_Timer_Trigger falls outside of the reassembly window and RX_Timer_Trigger is not equal to
RX_Next_Highest; or
- if RX_Next_Highest = RX_Next_Reassembly + 1 and there is no missing byte segment of the RLC SDU
associated with SN = RX_Next_Reassembly before the last byte of all received segments of this RLC SDU:
- stop and reset t-Reassembly.
- if t-Reassembly is not running (includes the case when t-Reassembly is stopped due to actions above):
- if RX_Next_Highest > RX_Next_Reassembly + 1; or
- if RX_Next_Highest = RX_Next_Reassembly + 1 and there is at least one missing byte segment of the RLC
SDU associated with SN = RX_Next_Reassembly before the last byte of all received segments of this RLC
SDU:
- start t-Reassembly;
- set RX_Timer_Trigger to RX_Next_Highest.
ETSI
[TS 38.322, clause 5.2.2.2.4]
- update RX_Next_Reassembly to the SN of the first SN >= RX_Timer_Trigger that has not been reassembled;
- discard all segments with SN < updated RX_Next_Reassembly;
- if RX_Next_Highest > RX_Next_Reassembly + 1; or
- if RX_Next_Highest = RX_Next_Reassembly + 1 and there is at least one missing byte segment of the RLC
SDU associated with SN = RX_Next_Reassembly before the last byte of all received segments of this RLC
SDU:
- set RX_Timer_Trigger to RX_Next_Highest.
[TS 38.322, clause 5.2.2.2.4]
This sub clause describes the state variables used in AM and UM entities in order to specify the RLC protocol. The state
variables defined in this subclause are normative.
...
SN).
When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.
...
RX_Next_Highest– 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.
(RX_Next_Highest– UM_Window_Size) <= SN < RX_Next_Highest is evaluated as [(RX_Next_Highest–
UM_Window_Size) – (RX_Next_Highest– UM_Window_Size)] modulo 2[sn-FieldLength] <= [SN – (RX_Next_Highest–
UM_Window_Size)] modulo 2[sn-FieldLength] < [RX_Next_Highest– (RX_Next_Highest– UM_Window_Size)] modulo
2[sn-FieldLength]), where sn-FieldLength is 6 or 12 for 6 bit SN and 12 bit SN, respectively.
...
a) TX_Next
ETSI
Same Pre-test conditions as in clause 7.1.2.1.2 with the exception that the UM DRB is configured according to Table
7.1.2.2.5.3.1-1.
t-Reassembly ms200
ELSE size12
Downlink UM RLC sn-FieldLength F (pc_um_WithShortSN ) size6
ELSE size12

Parameter Value
t-Reordering ms30
ETSI

U-S Message
1 The SS transmits UMD PDU#1 containing first <-- UMD PDU#1 - -
segment of RLC SDU#1, SN=0.
2 20 ms after step 1 the SS transmits UMD <-- UMD PDU#3 - -
PDU#3 containing first segment of RLC
SDU#2, SN=1.
PDU#4 containing last segment of RLC
SDU#2, SN=1.
3A 60 ms after step 1 the SS transmits UMD <-- UMD PDU#9 - -
PDU#9 containing first segment of RLC
SDU#5, SN=w
3B 80 ms after step 1 the SS transmits UMD <-- UMD PDU#10 - -
PDU#10 containing last segment of RLC
SDU#5, SN=w
3C 100 ms after step 1 the SS assigns 2 UL - - - -
grants (UL grant allocation type 2) with a time
spacing of 20 ms so as to loop back RLC
SDU#2.
(Note 3)
4A Check: Does the UE transmit RLC SDU#5? --> (RLC SDU#5) 2,3 P
(Note 4)
PDU#2 last segment of RLC SDU#1, SN=0.
5A The SS starts the UL default grant - - - -
transmissions.
6 Check: For 1 sec after step 5, does the UE --> (RLC SDU#1) 1 F
transmit RLC SDU#1, SN=0? (Note 6)
6A - - - -
8 Wait for 200 ms to ensure that t- Reassembly - - - -
for the UMD PDU#5 expires.
9 The SS transmits UMD PDU#6 containing last <-- UMD PDU#6 - -
segment of RLC SDU#3, SN=5 (Note 7).
10 Check: For 1 sec after step 9, does the UE --> (RLC SDU#3) 4 F
transmit RLC SDU#3? (Note 7)
12 The SS transmits UMD PDU#8 containing last <-- UMD PDU#8 - -
(Note 5)
Note 1: The RLC SDU size shall be 12 octets which are segmented into 7 and 5 octets.
Note 2: UL grant of 144 bits(LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit one PDU
at a time( 12 bytes RLC SDU + 1 or 2 bytes RLC Header + 2 bytes MAC Sub PDU header + 2 or 3 bytes for
short BSR and/or padding).
Note 3: The UE transmits the looped back PDCP data of RLC SDU#2 in a PDCP PDU with PDCP SN=0.
None
ETSI
7.1.2.2.6 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 {
then { The UE resets variables TX_Next, RX_Next_Reassembly, and RX_Next_Highest to their initial
value of 0 }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.322, clauses 5.1.2 and 7.1,
TS 38.331 clause 5.3.5.5.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.1.2]
When upper layers request an RLC entity re-establishment, the UE shall:
- discard all RLC SDUs, RLC SDU segments, and RLC PDUs, if any;
- stop and reset all timers;
- reset all state variables to their initial values.
[TS 38.322, clause 7.1]
d) RX_Next_Highest – Highest received state variable
This state variable holds the value of the SN following the SN of the RLC SDU with the highest SN among received
RLC SDUs. It is initially set to 0.
a) TX_Next
[TS 38.331, clause 5.3.5.5.4]
ETSI
For each RLC-Bearer-Config received in the rlc-BearerToAddModList IE the UE shall:
1> if the UE’s current configuration contains a RLC bearer with the received logicalChannelIdentity:
2> if reestablishRLC is received:
3> re-establish the RLC entity as specified in TS 38.322 [4];
2> reconfigure the RLC entity or entities in accordance with the received rlc-Config;
2> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig;
NOTE: The network does not re-associate an already configured logical channel with another radio bearer. Hence
servedRadioBearer is not present in this case.
Same Pre-test conditions as in clause 7.1.2.1.2 with the exception that the UM DRB is configured according to Table
7.1.2.2.6.3.1-1.
t-Reassembly ms200
ELSE size12
Downlink UM RLC sn-FieldLength IF (pc_um_WithShortSN ) size6
ELSE size12
ETSI

U-S Message
1 The SS transmits UMD PDU#1. Header of <-- UMD PDU#1 - -
UMD PDU#1 does not contain an SN. This
PDU carries RLC SDU#1.
2 The UE transmits RLC SDU#1. --> (RLC SDU#1) - -
3 The SS transmits UMD PDU#2. Header of <-- UMD PDU#2 - -
UMD PDU#2 contains SN=0. This PDU carries
the first segment of SDU#2.
message to trigger RLC re-establishment on
DRB using Reconfig with sync procedure.
(Note 3)(Note 5)
4A The UE transmits a NR --> RRCReconfigurationComplete - -
RRCReconfigurationcomplete message.
(Note 4)
5 100 ms after step 4A the SS transmits UMD <-- UMD PDU#3 - -
PDU#3. Header of UMD PDU#3 contains
SN=0. This PDU carries the last segment of
RLC SDU#2. The UE starts t-Reassembly.
6 Check: For 250 ms after step 5 does the UE --> (RLC SDU#2) 1 F
transmit RLC SDU#2?
6A The SS stops allocating any UL grant.
7 300 ms (1.5 * t- Reassembly) after step 5 the <-- UMD PDU#4 - -
SS transmits UMD PDU#4. This PDU carries
the first segment of RLC SDU#3.SN=1.
PDU#5. This PDU carries the second and last
segment of RLC SDU#3.SN=1.
8A 20 ms after step 8 the SS allocates 2 UL - - - -
grants at an interval of 20 ms so as to loop
back RLC SDU#3 in 2 RLC/MAC PDUs. Note
1&2
9 Check: Does the UE transmit first segment of --> (RLC SDU#3 first segment) 2 P
RLC SDU#3? Header of UMD PDU contains
SN=0.
10 Check: Does the UE transmit second and last --> (RLC SDU#3 last segment) 2 P
segment of RLC SDU#3? Header of UMD
PDU contains SN=0.
10A The SS starts the UL default grant
transmissions
(Note 3)
(Note 4)
11B The SS stops allocating any UL grant.
12 After 100 ms the SS transmits UMD PDU#6. <-- UMD PDU#6 - -
Header of UMD PDU#6 contains SN=0. This
PDU carries the first segment of SDU#4.
PDU#7. Header of UMD PDU#6 contains
SN=0. This PDU carries the second segment
of SDU#4.
13A 20 ms after step 13 the SS allocates 2 UL - - - -
grants at an interval of 20 ms so as to loop
back RLC SDU#4 in 2 RLC/MAC PDUs. Note
1&2
14 Check: Does the UE transmit first segment of --> (RLC SDU#4 first segment) 2 P
RLC SDU#4? Header of UMD PDU contains
SN=0.
ETSI
15 Check: Does the UE transmit second and last --> (RLC SDU#4 last segment) 2 P
segment of RLC SDU#4? Header of UMD
PDU contains SN=0.
Note 1: For SN size = size6 the RLC SDU size shall be 12 octets which are segmented into 6 and 6 octets. With 2
octets of MAC BSR and 2 octets of MAC header and 1 octet of RLC header (without SO) the first segment
consists of 88 bits and a TBS of this size shall be allocated. With 2 octets of MAC header and 3 octets of
RLC header (with SO) the second segment consists of 88 bits and a TBS of this size shall be allocated. (LRBs
& IMCS as per 38.523-3[3] annex B)
Note 2: For SN size = size12 the RLC SDU size shall be 10 octets which are segmented into 5 and 5 octets. With 2
octets of MAC BSR and 2 octets of MAC header and 2 octets of RLC header (without SO) the first segment
consists of 88 bits and a TBS of this size shall be allocated. With 2 octets of MAC header and 4 octets of
RLC header (with SO) the second segment consists of 88 bits and a TBS of this size shall be allocated. (LRBs
& IMCS as per 38.523-3[3] annex B)
Note 3: For EN-DC, the NR RRCReconfiguration message is contained in RRCConnectionReconfiguration as
defined in Table 7.1.2.2.6.3.3-2
Note 4: For EN-DC, the NR RRCReconfigurationComplete message is contained in
Table 7.1.2.2.6.3.3-1: RRCReconfiguration for NR (steps 4, 11, Table 7.1.2.2.6.3.2-1)

radioBearerConfig RadioBearerConfig n set to the default
according to TS 38.508-1 DRB of the first
[4], table 4.6.3-132 with PDU session
with conditions SRB1
and SRB2 and DRBn
}
nonCriticalExtension::= SEQUENCE {
according to TS 38.508-1
[4], table 4.6.3-19 with
condition PCell_change
}
}
}
ETSI
Table 7.1.2.2.6.3.3-2: RRCConnectionReconfiguration for EN-DC (steps 4, 11 Table 7.1.2.2.6.3.2-1)
Derivation Path: 36.508 Table 4.6.1-8

c1 CHOICE{
{
including the
RRCReconfiguration
message and the IE
secondaryCellGroup
[67], table 4.6.1-13 with
condition EN-DC_HO
}
}
including
RadioBearerConfig
[67], table 4.6.3-132 with
}
}
}
}
}
}
7.1.2.3 RLC Acknowledged Mode
7.1.2.3.1 AM RLC / 12-bit SN / Segmentation and reassembly / Segmentation Info (SI) field
(1)
ensure that {
when { UE receives a 12 bit SN configured AMD PDU containing a SI field set to 00 }
then { UE correctly decodes the received AMD PDU }
}
(2)
ensure that {
}
(3)
ensure that {
when { UE receives a 12 bit SN configured AMD PDU containing a SI field set to 11 and SO field }
}
ETSI
(4)
ensure that {
}
(5)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send complete PDU }
then { UE transmits AMD PDU containing a complete AMD SDU and SI field set to 00 }
}
(6)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send first segment only }
then { UE transmits AMD PDU containing first segment of AMD SDU and SI field set to 01 }
}
(7)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send middle segment only }
then { UE transmits AMD PDU containing middle segment of AMD SDU and SI field set to 11,
including SO field }
}
(8)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send last segment only }
then { UE transmits AMD PDU containing last segment of AMD SDU and SI field set to 10, including
SO field }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.322, clauses 6.2.2.4 and
[TS 38.322, clause 6.2.2.4]
AMD PDU consists of a Data field and an AMD PDU header. The AMD PDU header is byte aligned.
An AM RLC entity is configured by RRC to use either a 12 bit SN or a 18 bit SN. The length of the AMD PDU header
is two and three bytes respectively.
An AMD PDU header contains a D/C, a P, a SI, and a SN. An AMD PDU header contains the SO field only when the
Data field consists of an RLC SDU segment which is not the first segment, in which case a 16 bit SO is present.
ETSI
D/C P SI SN Oct 1
SN Oct 2
Data Oct 3
...
Oct N
Figure 6.2.2.4-1: AMD PDU with 12 bit SN (No SO)
D/C P SI R R SN Oct 1
SN Oct 2
SN Oct 3
Data Oct 4
...
Oct N
D/C P SI SN Oct 1
SN Oct 2
SO Oct 3
SO Oct 4
Data Oct 5
...
Oct N
Figure 6.2.2.4-3: AMD PDU with 12 bit SN with SO
SN Oct 2
SN Oct 3
SO Oct 4
SO Oct 5
Data Oct 6
...
Oct N
[TS 38.322, clause 6.2.3.4]
Length: 2 bits.
The SI field indicates whether an RLC PDU contains a complete RLC SDU or the first, middle, last segment of an RLC
SDU.
ETSI

Value Description
00 Data field contains all bytes of an RLC SDU
01 Data field contains the first segment of an RLC SDU
10 Data field contains the last segment of an RLC SDU
11 Data field contains neither the first nor last segment of an RLC SDU
Same Pre-test conditions as in clause 7.1.2.1.1 with the exception that the AM DRB is configured according to Table
7.1.2.3.1.3.1-1.
Uplink SN-FieldLength-AM size12

Downlink SN-FieldLength-AM size12
ETSI

U-S Message
1 The SS transmits AMD PDU#1 containing a <-- AMD PDU#1 - -
complete RLC SDU#1 (SI field = 00).
1A 60 ms after Step1, SS allocates an UL grant <-- UL Grant - -
sufficient to loop back RLC SDU#1 in one
RLC/MAC PDU
2 Check: Does the UE transmit AMD PDU#1 --> (RLC SDU#1) 1,5 P
containing a complete RLC SDU#1 (SI field =
00)?
3 The SS transmits a STATUS PDU. <-- STATUS PDU (ACK SN=1) - -
4 The SS transmits AMD PDU#2 containing the <-- AMD PDU#2 - -
first segment of RLC SDU#2 (SI field = 01).
Note 3
second segment of RLC SDU#2 (SI field = 11)
and including SO field. Note 3
last segment of RLC SDU#2 (SI field = 10) and
including SO field. Note 3
6A SS allocates 3 UL grants at an interval of 20 <-- UL Grants - -
RLC/MAC PDUs. (Note 1 and Note 2)
7 Check: Does the UE transmit AMD PDU#2 --> (RLC SDU#2) 2,3, P
containing the first segment of RLC SDU#2 (SI 4,6
field = 01)?
containing the middle segment of RLC SDU#2 4,7
(SI field = 11) and including SO field?
containing the last segment of RLC SDU#2 (SI 4,8
field = 10) and including SO field?
10 The SS transmits a STATUS PDU. <-- STATUS PDU (ACK SN=2) - -
Note 1: The UL grants for step 7,8,9 are sufficiently small (240 bits, LRBs & IMCS as per 38.523-3[3] annex B) that UE
transmits RLC SDU#2 in 3 UL RLC PDUs by segmenting.
Note 2: The RLC PDU containing a segment shall be of size 208 bits resp. 224 bits and a MAC sub PDU header of
16 bits and a 16-bit MAC BSR CE included in step 8 resulting in a MAC PDU of size 240 bits.
Note 3: The data part in step 4 first segment not including SO is 192 bits (24 bytes). Step 5, second segment
SO=24 and data is 192 bits (24 bytes). Step 6, third segment SO=24+24=48 and data is 192 bits (24
bytes).
None
7.1.2.3.2 AM RLC / 18-bit SN / Segmentation and reassembly / Segmentation Info (SI) field
(1)
ensure that {
then { UE correctly decodes the received AMD PDU or AMD PDU segment }
}
ETSI
(2)
ensure that {
}
(3)
ensure that {
}
(4)
ensure that {
}
(5)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send complete PDU }
then { UE transmits AMD PDU containing a complete AMD SDU and SI field set to 00 }
}
(6)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send first segment only }
then { UE transmits AMD PDU containing first segment of AMD SDU and SI field set to 01 }
}
(7)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send middle segment only }
then { UE transmits AMD PDU containing middle segment of AMD SDU and SI field set to 11,
including SO field }
}
(8)
ensure that {
when { UE has UL RLC SDU to send and the UL Grant is sufficient to send last segment only }
then { UE transmits AMD PDU containing last segment of AMD SDU and SI field set to 10, including
SO field }
}
Same conformance requirements as in clause 7.1.2.3.1.2
7.1.2.3.2.3.1-1.
ETSI

Same test procedure as in clause 7.1.2.3.1.3.2 except that SN is 18 bit and the data part in step 4 first segment not
including SO is 184 bits (23 Bytes). Step 5, second segment SO=23 and data is 184 bits (23 bytes). Step 6, third
segment SO=23+23=46 and data is 184 bits (23 bytes).
None
7.1.2.3.3 AM RLC / 12-bit SN / Correct use of sequence numbering
(1)
with { UE in RRC_CONNECTED state with AM RLC 12 bit SN }
ensure that {
when { UE transmits the PDU corresponding to first SDU }
then { UE includes the SN field equal to 0 in PDU }
}
(2)
ensure that {
when{ UE transmits subsequent SDUs }
then { UE includes the SN field incremented by 1 per SDU of each PDU transmitted }
}
(3)
ensure that {
with { UE transmits more than 4096 SDUs}
then { UE wraps the SN after transmitting the 4096 SDUs}
}
(4)
with { UE in RRC_CONNECTED state with AM RLC 12 bit SN
ensure that {
with { more than 4096 SDUs are sent to UE }
then { UE accepts PDUs with SNs that wrap around every 4096 SDUs }
}
5.2.3.2.1, 5.2.3.2.2, 6.2.2.4 and 7.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.2.3.2.1]
The receiving side of an AM RLC entity shall maintain a receiving window according to the state variable RX_Next as
follows:
- a SN falls within the receiving window if RX_Next <= SN < RX_Next + AM_Window_Size;
- a SN falls outside of the receiving window otherwise.
When receiving an AMD PDU from lower layer, the receiving side of an AM RLC entity shall:
ETSI
- either discard the received AMD PDU or place it in the reception buffer (see sub clause 5.2.3.2.2);
- if the received AMD PDU was placed in the reception buffer:
When t-Reassembly expires, the receiving side of an AM RLC entity shall:
- update state variables and start t-Reassembly as needed (see sub clause 5.2.3.2.4).
[TS 38.322, clause 5.2.3.2.2]
When an AMD PDU is received from lower layer, where the AMD PDU contains byte segment numbers y to z of an
RLC SDU 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 RLC SDU with SN = x have been received before:
- discard the received AMD PDU.
- else:
- place the received AMD PDU in the reception buffer;
- if some byte segments of the RLC SDU contained in the AMD PDU have been received before:
- discard the duplicate byte segments.
[TS 38.322, clause 6.2.2.4]
D/C P SI SN Oct 1
SN Oct 2
Data Oct 3
...
Oct N
SN Oct 2
SN Oct 3
Data Oct 4
...
Oct N
ETSI
D/C P SI SN Oct 1
SN Oct 2
SO Oct 3
SO Oct 4
Data Oct 5
...
Oct N
SN Oct 2
SN Oct 3
SO Oct 4
SO Oct 5
Data Oct 6
...
Oct N
[TS 38.322, clause 7.1]
c) RETX_COUNT – Counter
This counter counts the number of retransmissions of an RLC SDU or RLC SDU segment (see subclause 5.3.2). There
is one RETX_COUNT counter maintained per RLC SDU.
The receiving side of each AM RLC entity shall maintain the following state variables:
a) RX_Next – Receive state variable
This state variable holds the value of the SN following the last in-sequence completely received RLC SDU, and it
serves as the lower edge of the receiving window. It is initially set to 0, and is updated whenever the AM RLC entity
receives an RLC SDU with SN = RX_Next.
b) RX_Next_Status_Trigger – t-Reassembly state variable
This state variable holds the value of the SN following the SN of the RLC SDU which triggered t-Reassembly.
c) RX_Highest_Status – Maximum STATUS transmit state variable
This state variable holds the highest possible value of the SN which can be indicated by "ACK_SN" when a STATUS
PDU needs to be constructed. It is initially set to 0.
a) TX_Next
ETSI
7.1.2.3.3.3.1-1.

pollPDU p2048
pollByte kB25
ETSI

U-S Message
- EXCEPTION: Steps 1 – 3a1 shall be repeated - - - -
from j=0 to j=
FLOOR(Maximum_RLC_SN/iteration_size).
(Note 1, 4, 6)
1 SS transmits in one slot, several RLC PDUs in <-- RLC PDUs - -
a RLC PDU List, the number of RLC PDUs
sent is defined by the iteration_size. (Note 4,
5).
Each RLC PDU contains one RLC SDU.
- EXCEPTION: In Step 2, SS may receive a - - - -
RLC PDU or several RLC PDUs, then step 2
may be repeated multiple times until all RLC
PDUs with SN=j*iteration_size to
SN=(((j+1)*iteration_size)-1) for each iteration
are received.
2 CHECK: Does UE transmit RLC PDUs with --> RLC PDUs 1,2 P
SN=0 for the first iteration and all RLC PDUs
for each iteration?
(Note 2) (Note 7)
- 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 <-- STATUS PDU - -
transmitted at Step 2 THEN the SS transmits a
Status Report.
4 SS transmits a RLC PDU containing one RLC <-- RLC PDU - -
SDU.
5 CHECK: Does UE transmit a RLC PDU with --> RLC PDU 3,4 P
SN=0?
6 The SS transmits a STATUS PDU with <-- STATUS PDU - -
ACK_SN = 1.
Note 1: Maximum_RLC_SN = 2[RLC-SN-SizeUL] -1.
Note 2: The verdict shall be provided each time [(SN+1) mod 256 = 0] for 12 bit SN and [(SN+1) mod 4096 = 0] for
18 bit SN respectively.
Note 3: Void
Note 4: Iteration will be incremented by iteration_size of 1 for 12 bit SN and iteration_size of 25 for 18 bit SN. Small
RLC SDU size will be used.
Note 5: SS shall transmit a RLC PDU list with size equal to iteration_size and incrementing SN by 1 till SN = ((j + 1) *
iteration_size)-1.
Note 6: The RLC SDU size shall be 4 octets(3 octets of PDCP header + 1 octet PDCP SDU).
Note 7: All RLC PDUs may be received by the SS in the same slot or in multiple slots (max one MAC PDU in a slot).
None.
7.1.2.3.4 AM RLC / 18-bit SN / Correct use of sequence numbering
(1)
ensure that {
when { UE transmits the PDU corresponding to first SDU }
then { UE includes the SN field equal to 0 in PDU }
}
ETSI
(2)
ensure that {
when{ UE transmits subsequent SDUs }
then { UE includes the SN field incremented by 1 per SDU of each PDU transmitted }
}
(3)
ensure that {
with { UE transmits more than 262144 SDUs }
then { UE wraps the SN after transmitting the 262144 SDUs }
}
(4)
with { UE in RRC_CONNECTED state with AM RLC 18 bit SN
ensure that {
with { more than 262144 SDUs are sent to UE }
then { UE accepts PDUs with SNs that wrap around every 262144 SDUs }
}
Same as conformance requirements in clause 7.1.2.3.3.2
7.1.2.3.4.3.1-1.

pollPDU p2048
pollByte kB25
Same as test procedure in clause 7.1.2.3.3.3.2
None.
7.1.2.3.5 AM RLC / 12-bit SN / Control of transmit window / Control of receive window
(1)
with { UE in RRC_CONNECTED state with AM RLC 12 bit SN and pending uplink data for transmission }
ensure that {
when { AMD PDUs in transmission buffer fall outside TX_Next_Ack <= SN < TX_Next_Ack +
AM_Window_Size }
then { UE does not transmit these AMD PDUs }
}
ETSI
(2)
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 }
}
(3)
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 }
}
(4)
ensure that {
when { the receive window has been moved }
then { UE continues accepting AMD PDUs within updated window range }
}
5.2.3.2.2, 5.2.3.2.3 and 7.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.2.3.2.2]
- else:
[TS 38.322, clause 5.2.3.2.3]
When an AMD PDU with SN = x is placed in the reception buffer, the receiving side of an AM RLC entity shall:
- if x >= RX_Next_Highest
- update RX_Next_Highest to x+ 1.
- if all bytes of the RLC SDU with SN = x are received:
- reassemble the RLC SDU from AMD PDU(s) with SN = x, remove RLC headers when doing so and deliver
the reassembled RLC SDU to upper layer;
- if x = RX_Highest_Status,
- update RX_Highest_Status to the SN of the first RLC SDU with SN > current RX_Highest_Status for
which not all bytes have been received.
- if x = RX_Next:
ETSI
- update RX_Next to the SN of the first RLC SDU with SN > current RX_Next for which not all bytes
have been received.
- if RX_Next_Status_Trigger = RX_Next; or
- if RX_Next_Status_Trigger = RX_Next + 1 and there is no missing byte segment of the SDU associated with
SN = RX_Next before the last byte of all received segments of this SDU; or
- if RX_Next_Status_Trigger falls outside of the receiving window and RX_Next_Status_Trigger is not equal
to RX_Next + AM_Window_Size:
- if t-Reassembly is not running (includes the case t-Reassembly is stopped due to actions above):
- if RX_Next_Highest> RX_Next +1; or
- if RX_Next_Highest = RX_Next + 1 and there is at least one missing byte segment of the SDU associated
with SN = RX_Next before the last byte of all received segments of this SDU:
- set RX_Next_Status_Trigger to RX_Next_Highest.
[TS 38.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. AM_Window_Size =
2048 when a 12 bit SN is used, AM_Window_Size = 131072 when an 18 bit SN is used.
7.1.2.3.5.3.1-1.
pollPDU infinity
pollByte infinity
sn-FieldLength(UL-AM-RLC) size12
sn-FieldLength(DL-AM-RLC) size12
ETSI

U-S Message
0 The SS does not allocate any uplink grant. - - - -
- EXCEPTION: The SS is configured for step 1 - - - -
500 ms in advance. The transmissions are
performed every second radio frame. Step 2 is
started 100 ms after the first DL AMD PDU has
been transmitted in step 1.
- EXCEPTION: Step 1 a1 shall be repeated - - - -
from j=0 to j=
FLOOR((Maximum_RLC_SN/iteration size) -1,
and the last repetition shall execute Step 1b1.
(Note 1) (Note 3) (Note 4) (Note 6)
1a1 The SS transmits several RLC PDUs in a RLC <-- RLC Data PDU (SN = j*iteration_ - -
PDU List, the number of RLC PDUs sent is size, SN=(((j+1)*iteration_size)-1)
defined by the iteration_size.
Each RLC Data PDU contains one RLC SDU.
(Note 8) (Note 9) (Note 5)
1b1 The SS transmits several RLC PDUs in a RLC <-- RLC Data PDU (SN = j*iteration_ - -
PDU List, the number of RLC PDUs sent is size, SN=(((j+1)*iteration_size))
defined by the iteration_size+1.
Each RLC Data PDU contains one RLC SDU.
The SS transmits AMD PDU(SN=W+1) as last
packet (Note 8) (Note 9) (Note 5)
1A Void - - - -
2 In the following steps the SS transmits 1 UL <-- (UL grants) - -
grant in every second radio frame to enable
the UE to return each received AMD PDU in
one looped back AMD PDU. (Note 2)
- EXCEPTION: Step 2A shall be repeated from - - - -
j=0 to j=FLOOR((Maximum_RLC_SN/iteration
size). (Note 1) (Note 3) (Note 4) (Note 6)
- EXCEPTION: In Step 2A, SS shall receive a - - - -
RLC PDU and step 2A is repeated from
SN=j*iteration_size to SN=(((j+1)*iteration_
size)-1). (Note 1) (Note 3) (Note 4) (Note 6)
(Note 8) (Note 9)
2A Check: Does UE transmit a RLC Data PDU --> RLC Data PDU (SN = j*iteration_ 1 P
with the Poll bit not set and with SN=0 for the size, SN=(((j+1)*iteration_size)-1)
first RLC Data PDU and then incremented by 1
at each RLC Data PDU? (Note 7)(Note 10)
3 Check: Does the UE transmit the (W)st AMD --> AMD PDU(SN=W-1), Poll 1 P
PDU with the Poll bit set and with the contents
of the SDU?
4 The SS starts the UL default grant - - - -
transmission.
5 Check: Does the UE transmit an AMD PDU --> AMD PDU 1 F
within t-PollRetransmit/2?
6 The SS transmits a STATUS PDU to <-- STATUS PDU - -
acknowledge the W uplink AMD PDUs with
SN=0 to SN=W-1. ACK_SN = W.
7 Check: Does the UE transmit an AMD PDU --> AMD PDU(SN=W), Poll 2 P
with the Poll bit set and with the contents of the
SDU?
ACK_SN = W+1.
9 The SS transmits the (W+2)nd AMD PDU <-- AMD PDU - -
containing a SDU to the UE with the Sequence
Number field set to ((2W+1 mod AM_Modulus)
= 1) and the Polling bit set. (Note 3) (Note 5)
10 Check: Does the UE transmit a STATUS PDU --> STATUS PDU 3 P
acknowledging W+1 SDUs? (ACK_SN =
W+1). (Note 1)
ETSI
11 The SS transmits the (W+2)nd AMD PDU to <-- AMD PDU - -

the UE with the Sequence Number field set to
W+1 and the Polling bit set. (Note 5)
- EXCEPTION: Steps 12 and 13 can happen in - - - -
any order
12 Check: Does the UE transmit a STATUS PDU --> STATUS PDU 4 P
acknowledging W+1 PDUs? (ACK_SN field =
W+2). (Note 11)
13 Check: Does the UE transmit an AMD PDU --> AMD PDU 4 P
with the same data as received in the
corresponding DL AMD PDU in step 11? (Note
11)
ACK_SN = W+2.
Note 1: PDUs are numbered 1,2, …, W+2.
Note 2: 20 ms gap between transmissions both in DL and UL respectively allows TTCN to tolerate one HARQ
retransmission (FDD/TDD) per transport block.
Note 3: AM_Modulus is 4096 resp 262144 for SN size is size12 or size18.
Note 4: The RLC SDU size shall be 4 octets(3 octets of PDCP header + 1 octet PDCP SDU).
If SN size is size18 is used the RLC SDU size shall be 7 octets. With 2 octets of BSR or padding, 2 octets
of MAC header and 3 octets of RLC header (without SO) the RLC PDU consists of 56 bits and a TBS of
112 bits shall be allocated
Note 5: PDCP SN=W+1
Note 6: Maximum_RLC_SN = W-1.
Note 7: The verdict shall be provided each time (SN+1) mod 256 = 0 resp. (SN+1) mod 4096 = 0, if SN size is
size12 or size18.
Note 8: Iteration will be 211 in case of len12bits. Small RLC SDU size will be used and no repetition will be needed.
Note 9: Iteration will be incremented by iteration_size of 211 for SN len18bits. Small RLC SDU size will be used and
it shall be repeated FLOOR(Maximum_RLC_SN/iteration_size).
Note 10: -2 for the last iteration, as the last reception will be handled by step 3.
Note 11: STATUS PDU at step 12 and AMD PDU at step 13 may be received by SS in the same slot or in multiple
slots
None
7.1.2.3.5a AM RLC / 18-bit SN / Control of transmit window / Control of receive window
(1)
ensure that {
when { AMD PDUs in transmission buffer fall outside TX_Next_Ack <= SN < TX_Next_Ack +
AM_Window_Size }
then { UE does not transmit these AMD PDUs }
}
(2)
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 }
}
(3)
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 }
}
ETSI
(4)
ensure that {
when { the receive window has been moved }
then { UE continues accepting AMD PDUs within updated window range }
}
Same as conformance requirements in clause 7.1.2.3.5.2.
7.1.2.3.5a.3 Test description
7.1.2.3.5a.3.1-1.
Table 7.1.2.3.5a.3.1-1: RLC parameters
pollPDU infinity
pollByte infinity
sn-FieldLength(UL-AM-RLC) size18
sn-FieldLength(DL-AM-RLC) size18
None.
7.1.2.3.6 AM RLC / Polling for status
(1)
with { UE in RRC_CONNECTED state and using AM RLC }
ensure that {
when { last data in the UL buffer is being transmitted }
then { UE transmits a Poll }
}
(2)
ensure that {
when { the t-PollRetransmit timer expires }
}
(3)
ensure that {
when { PDU_WITHOUT_POLL >= pollPDU }
}
ETSI
(4)
ensure that {
when { BYTE_WITHOUT_POLL >= pollByte }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.322, clauses 5.3.3.2, 7.3
and 7.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.3.3.2]
Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission such
that the AMD PDU contains either a not previously transmitted RLC SDU or an RLC SDU segment containing not
previously transmitted byte segment, 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 AMD PDU;
- if PDU_WITHOUT_POLL >= pollPDU; or
- if BYTE_WITHOUT_POLL >= pollByte:
- include a poll in the AMD PDU as described below.
Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission, the
transmitting side of an AM RLC entity shall:
- if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC SDUs
or RLC SDU segments awaiting acknowledgements) after the transmission of the AMD PDU; or
- if no new RLC SDU can be transmitted after the transmission of the AMD PDU (e.g. due to window stalling);
NOTE: Empty RLC buffer (excluding transmitted RLC SDUs or RLC SDU segments awaiting
acknowledgements) should not lead to unnecessary polling when data awaits in the upper layer. Details
are left up to UE implementation.
To include a poll in an AMD PDU, the transmitting side of an AM RLC entity shall:
- set the P field of the AMD PDU to "1";
- set PDU_WITHOUT_POLL to 0;
- set BYTE_WITHOUT_POLL to 0.
After submitting an AMD PDU including a poll to lower layer and after incrementing of TX_Next if necessary, the
- set POLL_SN to TX_Next – 1;
- if t-PollRetransmit is not running:
- start t-PollRetransmit.
- else:
- restart t-PollRetransmit.
[TS 38.322, clause 5.3.3.4]
Upon expiry of t-PollRetransmit, the transmitting side of an AM RLC entity shall:
ETSI
- if both the transmission buffer and the retransmission buffer are empty (excluding transmitted RLC SDU or RLC
SDU segment awaiting acknowledgements); or
- if no new RLC SDU or RLC SDU segment can be transmitted (e.g. due to window stalling):
- consider the RLC SDU with SN = TX_Next – 1 for retransmission; or
- consider any RLC SDU which has not been positively acknowledged for retransmission.
- include a poll in an AMD PDU as described in section 5.3.3.2.
[TS 38.322, clause 7.3]
a) t-PollRetransmit
This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll (see sub clause 5.3.3).
[TS 38.322, clause 7.4]
b) pollPDU
This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollPDU PDUs (see
subclause 5.3.3).
c) pollByte
This parameter is used by the transmitting side of each AM RLC entity to trigger a poll for every pollByte bytes (see
subclause 5.3.3).
7.1.2.3.6.3.1-1.
pollPDU p256
pollByte kB25
ETSI

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 4 AMD PDUs such that 1 <-- AMD PDU (SN=0) - -
AMD PDU is sent every two radio frame, each AMD PDU (SN=1)
containing an RLC SDU of 976 bits. (Note 2) AMD PDU (SN=2)
AMD PDU (SN=3)
- EXCEPTION: In parallel to the events - - - -
described in step 3, the step specified in Table
7.1.2.3.6.3.2-2 should take place.
3 The SS waits for 100 ms after the first DL AMD - - - -
PDU has been transmitted in step 2, then
starts assigning UL grants in every second
radio frame of size 1032 bits. (Note 1) (Note 2)
4 Check 1: Does the UE transmit an AMD PDU --> AMD PDU 2 P
with a SN in range 0 to 3 and P=1?
Record time TB.
Check 2: Is (TB – TA) = t-PollRetransmit?
transmission on reception of SR.
6 The SS transmits an RLC Status Report <-- STATUS PDU - -
ACKing reception of PDU’s 0-3.
7 Check: Does the UE retransmit an AMD PDU --> AMD PDU 2 F
within 1 sec?
message changing pollPDU to p4.
(Note 3)
(Note 4)
10 The SS transmits 8 AMD PDUs such that 1 <-- AMD PDU (SN=4) - -
AMD PDU is sent every second radio frame, AMD PDU (SN=5)
each containing an RLC SDU of 976 bits. ...
(Note 2) AMD PDU (SN=11)
described in step 11, the step specified in
Table 7.1.2.3.6.3.2-3 should take place.
starts assigning UL grants (UL grant allocation
type 2) in every second radio frame of size
1032 bits. (Note 1) (Note 2)
12 The SS transmits a Status Report with <-- STATUS PDU - -
ACK_SN=12, NACK_SN=4, NACK_SN=5,
NACK_SN=6 (constructed by NACK_SN
Range), NACK_SN=8 and NACK_SN=9
(constructed by NACK_SN Range).
12 Void. - - - -
A
13 Check: Does the UE transmit AMD PDUs with --> AMD PDU (SN=4, P=0) 2 P
the following SN and P values? AMD PDU (SN=5, P=0)
AMD PDU, SN=4, P=0 AMD PDU (SN=6, P=0)
AMD PDU, SN=8, P=0
AMD PDU, SN=9, P=1
transmission on reception of SR.
15 The SS transmits a Status Report with <-- STATUS PDU - -
ACK_SN=12 and no NACK_SN.
ETSI

message changing pollPDU to p256.
(Note 3)
16 The UE transmits a NR --> RRCReconfigurationComplete - -
A RRCReconfigurationcomplete message.
(Note 4)
17 The SS does not allocate any UL grant. - - - -
18 After 500 ms the SS transmits 412 AMD PDUs <-- AMD PDU (SN=12) - -
such that 1 AMD PDU is sent every second AMD PDU (SN=13)
radio frame, each containing an RLC SDU of ...
size 976 bits. (Note 2) AMD PDU (SN=423)
described in step 19, the steps specified in
Table 7.1.2.3.6.3.2-4 should take place.
starts assigning UL grants (UL grant allocation
type 2) in every second radio frame of size
1032 bits. (Note 1) (Note 2)
transmission
Note 1: UL grant of 1032 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to loop back one
SDU of size 976 bits and one short BSR (16 bits) into each MAC PDU sent in the uplink (1032 bits - 24 bit
AMD PDU header - 16 bit MAC BSR CE- 16 bit MAC PDU subheader). The UE will include an SDU of size
976 bits and one short BSR in the looped back MAC PDU.
Note 2: 20ms gap between transmissions both in DL and UL respectively allows TTCN to tolerate one HARQ
retransmission (FDD/TDD) per transport block, if such happen (TS 38.523-3 [3]).
[7] Table 4.6.1-8 using condition EN-DC_EmbedNR_RRCRecon.

U-S Message
1 Check: Does the UE transmit 4 AMD PDUs, --> AMD PDUs 1 P
with only the last one having the poll bit set?
Record time TA when the PDU with the poll bit
set is received at the SS.

U-S Message
with the poll bit set only in the 4th and the 8th
PDUs?
ETSI

U-S Message
with the poll bit set only in the last (205th) one?
(Note 1)
2 The SS transmits an RLC Status Report. <-- STATUS PDU - -
with the poll bit set only in the last (410th) one?
(Note 1)
with the poll bit set only in the last (412th )
one?
Note 1: (976 bits x 205PDUs) / 8 = 25010 > 25 KB, with 1 kB = 1000 bytes (TS 38.331 [12], clause 3.2)
Table 7.1.2.3.6.3.3-1: RRCReconfiguration (steps 8 and 16, Table 7.1.2.3.6.3.2-1)

}
}
}
}

rlc-BearerToAddModList SEQUENCE 1 entry
(SIZE(1..maxLCH)) OF RLC-BearerConfig {
RLC-BearerConfig[1] RLC-BearerConfig entry 1
}
spCellConfig Not present
}
Table 7.1.2.3.6.3.3-3: RLC-BearerConfig (Table 7.1.2.3.6.3.3-2)
Derivation Path: 38.508-1 [4], Table 4.6.3-148 with condition AM

RLC-BearerConfig ::= SEQUENCE {
logicalChannelIdentity Set to LCID of the DRB
under test
rlc-Config RLC-Config
}
ETSI
Table 7.1.2.3.6.3.3-4: RLC-Config (Table 7.1.2.3.6.3.3-3)

RLC-Config ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
sn-FieldLength Not present
pollPDU p4 step 8
p256 step 16
pollByte kB25
}
dl-AM-RLC SEQUENCE {
}
7.1.2.3.7 AM RLC / Receiver status triggers
(1)
ensure that {
when { Reception failure of an RLC data PDU is detected and t-Reassembly expires }
then { UE initiates Status Reporting }
}
(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 ‘x’ of the PDU that
carries the Poll satisfies x < RX_Highest_Status or x >= RX_Next + AM_Window_Size }
then { UE initiates Status Reporting }
}
(4)
ensure that {
when { Polling from peer AM RLC entity is detected and the sequence number ‘x’ of the PDU that
carries the Poll does not satisfies x < RX_Highest_Status or x >= RX_Next + AM_Window_Size }
then { UE waits until ‘x < RX_Highest_Status or x >= RX_Next + AM_Window_Size’ 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 }
}
ETSI
(6)
ensure that {
when { the UE needs to send a Status Report and continuous sequence of RLC SDUs that have not been
received yet }
then { UE includes NACK_SN with NACK range }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.322, clause 5.3.4. Unless
[TS 38.322, clause 5.3.4]
An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative
acknowledgements of RLC SDUs (or portions of them).
Triggers to initiate STATUS reporting include:
- Polling from its peer AM RLC entity:
- When an AMD 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 AMD PDU is to be discarded as specified in subclause 5.2.3.2.2; or
- if x < RX_Highest_Status or x >= RX_Next + AM_Window_Size:
- trigger a STATUS report.
- else:
- delay triggering the STATUS report until x < RX_Highest_Status or x >= RX_Next +
AM_Window_Size.
NOTE 1: This ensures that the RLC Status report is transmitted after HARQ reordering.
- Detection of reception failure of an AMD PDU
- The receiving side of an AM RLC entity shall trigger a STATUS report when t-Reassembly expires.
NOTE 2: The expiry of t-Reassembly triggers both RX_Highest_Status to be updated and a STATUS report to be
triggered, but the STATUS report shall be triggered after RX_Highest_Status 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 submit 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
submit it to lower layer.
When a STATUS PDU has been submitted 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 RLC SDUs with SN such that RX_Next <= SN < RX_Highest_Status that has not been completely
received yet, in increasing SN order of RLC SDUs and increasing byte segment order within RLC SDUs,
ETSI
starting with SN = RX_Next 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 RLC SDU 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 RLC SDU.
- for a continuous sequence of byte segments of a partly received RLC SDU that have not been received yet:
- include in the STATUS PDU a set of NACK_SN, SOstart and SOend.
- for a continuous sequence of RLC SDUs that have not been received yet:
- include in the STATUS PDU a set of NACK_SN and NACK range;
- include in the STATUS PDU, if required, a pair of SOstart and SOend.
- set the ACK_SN to the SN of the next not received RLC SDU which is not indicated as missing in the resulting
STATUS PDU.
7.1.2.3.7.3.1-1.
t-Reassembly ms150
t-StatusProhibit ms300
ETSI

U-S Message
- The SS ignores scheduling requests and does - - - -
1 The SS transmits 4 AMD PDUs with SN=0, 1, <-- AMD PDU (SN=0, P=0) - -
2, and 4. The SS sets the P field of all the AMD PDU (SN=1, P=0)
AMD PDUs to 0. A time spacing of 20 ms is AMD PDU (SN=2, P=0)
applied. AMD PDU (SN=4, P=0)
Record time TA when the AMD PDU with SN=4
is sent.
2 The SS waits for 70 ms after the transmission <-- (UL grants, 848 bits) - -
of the first AMD PDU to ensure UE RLC has all
the required SDUs available and then assigns
3 UL grants (UL grant allocation type 2) with a
time spacing of 20 ms of size 848 bits (UL
Grant Allocation type 2). (Note 1)
6 60 ms after step 5, the SS transmits a <-- STATUS PDU - -
STATUS PDU
7 80 ms after step 5, the SS starts the UL default - - - -
grant transmission.
8 Check 1: Does the UE transmit a Status --> STATUS PDU 1 P
Report with NACK_SN=3 and ACK_SN=5?
Record time TB (Note 5)
Check 2: (TB – TA) = t-Reassembly?
9 100 ms after the Status Report is received at <-- AMD PDU (SN=5, P=0) - -
Step 8, the SS transmits 4 AMD PDUs with AMD PDU (SN=6, P=0)
SN=5, 6, 8 and 9. The SS sets the P field of all AMD PDU (SN=8, P=0)
the AMD PDUs to 0. A time spacing of 20 ms AMD PDU (SN=9, P=0)
is applied.
Report with NACK_SN=3 and ACK_SN=7?
Record time TC
Check 2: (TC – TB) = t-StatusProhibit?
11 The SS ignores scheduling requests unless - - - -
otherwise specified and does not allocate any
uplink grant.
12 After 200 ms the SS transmits 2 AMD PDUs <-- AMD PDU (SN=3, P=0) - -
with SN=3, SN=7. The SS sets the P field of all AMD PDU (SN=7, P=1)
the AMD PDUs to 0 except for that of the AMD
PDU with SN=7. A time spacing of 20 ms is
applied.
13 The SS waits for 100 ms after the transmission <-- (UL grant, 88 bits) - -
of the last AMD PDU to ensure UE RLC has all
1 UL grant (UL grant allocation type 3) of size
88 bits. (Note 2)
14 Check: Does the UE transmit a Status Report --> STATUS PDU 3 P
with no NACK_SN and ACK_SN = 10?
15 In the second frame following the one <-- (UL grant, 848 bits) - -
scheduled in step 13 the SS assigns 7 UL
grants (UL grant allocation type 2) with a time
spacing of 20 ms of size 848 bits. (Note 1)
23 The SS transmits a STATUS PDU <-- STATUS PDU - -
ETSI
24 After 300 ms the SS transmits an AMD PDU <-- AMD PDU (SN=11, P=0) - -
with SN=11 and P=0, and an AMD PDU with AMD PDU (SN=12, P=1)
SN=12 and P=1.A time spacing of 20 ms is
applied.
25 Check: Does the UE transmit a scheduling --> (SR) 4 F
request within t-Reassembly/ 2 ms after the
transmission of the first AMD PDU of Step 24?
26 At t-Reassembly/ 2 ms after the transmission <-- AMD PDU (SN=10, P=0) - -
of the second AMD PDU of Step 24, the SS
transmits an AMD PDU with SN=10 and P=0.
27 The SS waits for 60 ms to ensure UE RLC has <-- (UL grant, 88 bits) - -
all the required SDUs available and then
assigns 1 UL grant (UL grant allocation type 3)
of size 88 bits. (Note 2)
28 Check: Does the UE transmit a Status Report --> STATUS PDU 4 P
with no NACK_SN and ACK_SN=13?
29 The SS assigns 3 UL grants (UL grant <-- (UL grant, 848 bits) - -
allocation type 2) with a time spacing of 20 ms
with SN=17 and P=0, and an AMD PDU with AMD PDU (SN=19, P=1)
SN=19 and P=1. A time spacing of 20 ms is
applied.
35 The SS waits for t-Reassembly ms to ensure - - - -
expiry.
36 60 ms after step 35 the SS assigns an UL <-- (UL Grant, 88 bits) - -
grant (UL grant allocation type 3) of size 88
bits. (Note 3)
37 Check: Does the UE transmit a Status Report --> STATUS PDU 5,6 P
with ACK_SN=18 and NACK_SN: 13
including NACK Range 4 (SN 13, 14, 15, 16)?
with SN=16 and P=1.
39 30 ms after step 38 the SS assigns an UL <-- (UL Grant, size 112) - -
grant (UL grant allocation type 3) of size 112
bits. (Note 4)
40 Check: Does the UE transmit a Status Report --> STATUS PDU 5,6 P
with ACK_SN=20 and NACK_SN: 13 including
NACK Range 3 (SN 13, 14, 15) and
NACK_SN=18 without NACK Range?
41 60 ms after step 38 the SS transmits 4 AMD <-- AMD PDU (SN=13, P=0) - -
PDUs with SN=13, 14, 15 and 18. A time AMD PDU (SN=14, P=0)
spacing of 20 ms is applied. AMD PDU (SN=15, P=0)
AMD PDU (SN=18, P=0)
42 130 ms after the transmission of the first AMD <-- (UL grant, 848 bits) - -
PDU the SS assigns 7 UL grant (UL grant
allocation type 3 with a time spacing of 20 ms
43 The UE loopbacks the complete RLC SDU. --> (RLC SDU#14) - -
ETSI
Note 1: UL grant of 848 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit one
PDU at a time ( 99 bytes RLC SDU + 3 bytes RLC Header + 2 bytes MAC Sub PDU header + 2 bytes for
short BSR or padding).
Note 2: UL grant of 88 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit a Status
Report with ACK_SN(3 byte) + 2 byte MAC PDU subheader and (2 byte short BSR). 4 Bytes additional
space provided to confirm UE does not include NACK_SN and conformant UE instead will include MAC
Padding.
Note 3: UL grant of 88 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit (a Status
Report with ACK_SN (3 Bytes)and 1 NACK_SNs with NACK Range(4 Bytes) + MAC PDU subheader (2
Bytes) + Short BSR (2 Byte).
Note 4: UL grant of 112 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit (a
Status Report with ACK_SN (3 Bytes)and 1 NACK_SNs with NACK Range(4 Bytes) +NACK SN (3 Bytes)
+ MAC PDU subheader (2 Bytes) + Short BSR (2 Byte).
Note 5: Time TB should be recorded by factoring in the SR-Periodicity as configured in the
SchedulingRequestResourceConfig->periodicityAndOffset
None
7.1.2.3.8 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-Reassembly value is changed during reconfiguration of RLC parameters by upper layers }
then { UE starts using new t-Reassembly 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: TS 38.322, clauses 5.3.3.1,
5.3.3.2, 5.3.3.3, 5.3.4 and 7.3. TS 38.331 clause 5.3.5.5.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.3.3.1]
An AM RLC entity can poll its peer AM RLC entity in order to trigger STATUS reporting at the peer AM RLC entity.
[TS 38.322, clause 5.3.3.2]
Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission such
that the AMD PDU contains either a not previously transmitted RLC SDU or an RLC SDU segment containing not
previously transmitted byte segment, the transmitting side of an AM RLC entity shall:
- increment PDU_WITHOUT_POLL by one;
ETSI
- increment BYTE_WITHOUT_POLL by every new byte of Data field element that it maps to the Data field of
the AMD PDU;
- if PDU_WITHOUT_POLL >= pollPDU; or
- if BYTE_WITHOUT_POLL >= pollByte:
Upon notification of a transmission opportunity by lower layer, for each AMD PDU submitted for transmission, the
- if both the transmission buffer and the retransmission buffer becomes empty (excluding transmitted RLC SDUs
or RLC SDU segments awaiting acknowledgements) after the transmission of the AMD PDU; or
- if no new RLC SDU can be transmitted after the transmission of the AMD PDU (e.g. due to window stalling);
NOTE: Empty RLC buffer (excluding transmitted RLC SDUs or RLC SDU segments awaiting
acknowledgements) should not lead to unnecessary polling when data awaits in the upper layer. Details
are left up to UE implementation.
To include a poll in an AMD PDU, the transmitting side of an AM RLC entity shall:
- set the P field of the AMD PDU to "1";
- set PDU_WITHOUT_POLL to 0;
- set BYTE_WITHOUT_POLL to 0.
After submitting an AMD PDU including a poll to lower layer and after incrementing of TX_Next if necessary, the
- set POLL_SN to TX_Next – 1;
- if t-PollRetransmit is not running:
- start t-PollRetransmit.
- else:
- restart t-PollRetransmit.
[TS 38.322, clause 5.3.3.3]
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 SDU with sequence
number equal to POLL_SN:
- if t-PollRetransmit is running:
- stop and reset t-PollRetransmit.
[TS 38.322, clause 5.3.4]
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 SDU or RLC
SDU segment awaiting acknowledgements); or
- if no new RLC SDU or RLC SDU segment can be transmitted (e.g. due to window stalling):
- consider the RLC SDU with SN = TX_Next – 1 for retransmission; or
- consider any RLC SDU which has not been positively acknowledged for retransmission.
ETSI
- include a poll in an AMD PDU as described in section 5.3.3.2.
[TS 38.322, clause 7.3]
The following timers are configured by 3GPP TS 38.331 [5]:
a) t-PollRetransmit
This timer is used by the transmitting side of an AM RLC entity in order to retransmit a poll (see sub clause 5.3.3).
b) t-Reassembly
This timer is used by the receiving side of an AM RLC entity and receiving UM RLC entity in order to detect loss of
RLC PDUs at lower layer (see sub clauses 5.2.2.2 and 5.2.3.2). If t-Reassembly is running, t-Reassembly shall not be
started additionally, i.e. only one t-Reassembly per RLC entity is running at a given time.
c) t-StatusProhibit
This timer is used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU (see
sub clause 5.3.4).
[TS 38.331, clause 5.3.5.5.4]
For each RLC-Bearer-Config received in the rlc-BearerToAddModList IE the UE shall:
1> if the UE’s current configuration contains a RLC bearer with the received logicalChannelIdentity:
2> if reestablishRLC is received:
3> re-establish the RLC entity as specified in TS 38.322 [4];
2> reconfigure the RLC entity or entities in accordance with the received rlc-Config;
2> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig;
NOTE: The network does not re-associate an already configured logical channel with another radio bearer. Hence
servedRadioBearer is not present in this case.
7.1.2.3.8.3.1-1.
Parameter Value
t-Reassembly ms150
pollPDU infinity
pollByte infinity
ETSI

U-S Message/PDU/SDU
1- Same expected sequence as in Table - - 1,2, -
29 7.1.2.3.8.3.2-2 with (X=0, t-Reassembly = 3
ms150, t-StatusProhibit = ms300, t-
PollRetransmit=ms400) Note 1.
30 The SS transmits NR RRCReconfiguratioin <-- RRCReconfiguration - -
message to reconfigure RLC in the UE and
set:
- t-Reassembly to ms200,
- t-StatusProhibit to ms400,
- t-PollRetransmit to ms500.
(Note 1)
A RRCReconfigurationcomplete message.
(Note 2)
31- Same expected sequence as in Table - - 1,2, -
59 7.1.2.3.8.3.2-2 with (X=11, t-Reassembly = 3
ms200, t-StatusProhibit = ms400, t-
PollRetransmit=ms500).
ETSI
Table 7.1.2.3.8.3.2-2: Behaviour Sequence (X, t-Reassembly, t-StatusProhibit,t-PollRetransmit)

U-S Message/PDU/SDU
2 The SS transmits 4 AMD PDUs with P=0 and <-- AMD PDU#1 (SN=X, P=0) - -
SN=X, X+1, X+2 and X+4. AMD PDU#2 (SN=X+1, P=0)
The SS record time TA when AMD PDU#5 AMD PDU#3 (SN=X+2, P=0)
(with SN=X+4) is sent. A time spacing of 20 AMD PDU#5 (SN=X+4, P=0)
ms is applied.
3 The SS waits for 70 ms after the transmission <-- (UL grants, 848 bits) - -
of the first AMD PDU to ensure UE RLC has all
3 UL grants of size 848 bits with a time
spacing of 20 ms. (Note 1)
4 The UE transmits RLC SDU#1+X. --> (RLC SDU#1+X) - -
7 60 ms after step 3 the SS transmits a STATUS <-- STATUS PDU - -
PDU.
transmission.
9 Check 1: Does the UE transmit a STATUS --> STATUS PDU 2 P
PDU with NACK_SN=X+3 and ACK_SN=X+5?
Record time TB (Note 5).
Check 2: Is (TB – TA ) = t-Reassembly?
10 100 ms after the Status Report received at <-- AMD PDU#6 (SN=X+5, P=0) - -
Step 9, the SS sends 4 AMD PDUs with P=0 AMD PDU#7 (SN=X+6, P=0)
and SN=X+5, X+6, X+8 and X+9. A time AMD PDU#9 (SN=X+8, P=0)
spacing of 20 ms is applied. AMD PDU#10 (SN=X+9, P=0)
Report with NACK_SN=X+3 and
ACK_SN=X+7?
Record time TC
Check 2: (TC – TB) = t-StatusProhibit?
13 After 250 ms the SS transmits 3 AMD PDUs <-- AMD PDU#4 (SN=X+3, P=0) - -
with SN=X+3, X+7 and X+9. The SS sets the AMD PDU#8 (SN=X+7, P=0)
P field of all the AMD PDUs to 0 except for that AMD PDU#10 (SN=X+9, P=1)
of the AMD PDU with SN=X+9. A time spacing
of 20 ms is applied.
14 The SS waits for 150 ms after AMD PDU#4 <-- (UL grant, 88 bits) - -
transmission to ensure UE RLC has all the
required SDUs available and then assigns 1
UL grant of size 88 bits (UL Grant Allocation
type 3). (Note 2)(Note 4)
15 The UE transmits a Status Report with no --> STATUS PDU - -
NACK_SN and ACK_SN=X+10.
16 In the subframe following the one scheduled in <-- (UL grants, 848 bits) - -
step 14 the SS assigns 7 UL grants of size 848
bits (UL Grant Allocation type 2) with a time
spacing of 20 ms. (Note 1)
25 The SS transmits an AMD PDU to the UE. <-- AMD PDU#11 (SN=X+10, P=0) - -
transmission.
ETSI
27 The UE transmits an AMD PDU with the same --> AMD PDU#11 (SN=X+10, P=1) - -
data as received in the corresponding DL AMD
PDU. Record time TD.
28 Check 1: Does the UE set the poll bit as both --> AMD PDU#11 (SN=X+10, P=1) 1 P
the transmission and retransmission buffers
become empty? Record time TE.
Check 2: Is (TE – TD ) = t-PollRetransmit?
29 The SS transmits a STATUS PDU <-- STATUS PDU - -
Note 1: UL grant of 848 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit one
PDU at a time.
Note 2: UL grant of 88 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit a Status
Report with ACK_SN(3 byte) + 2 byte MAC PDU subheader and (2 byte short BSR). 4 Bytes additional
space provided to confirm UE does not include NACK_SN and conformant UE instead will include MAC
Padding.
Note 3: Every DL AMD PDU contains 1 RLC SDU size of 99 bytes.
Note 4: Timing difference between step 11 to step 15 is equal to t-statusProhibit timer. UE starts SR from step 13
with AMD-PDU#4. 150 ms is chosen so that UE does not reach sr-transMax(n16) otherwise UE RACHes.
Note 5: Time TB should be recorded by factoring in the SR-Periodicity as configured in the
SchedulingRequestResourceConfig->periodicityAndOffset.

}
}
}
}

RLC-BearerConfig[1] RLC-BearerConfig entry 1
}
spCellConfig Not present
}
Table 7.1.2.2.8.3.3-3: RLC-BearerConfig (Table 7.1.2.3.8.3.3-2)

RLC-BearerConfig ::= SEQUENCE {
logicalChannelIdentity Set to LCID of the DRB
under test
rlc-Config RLC-Config
}
ETSI
Table 7.1.2.2.8.3.3-4: RLC-Config (Table 7.1.2.3.8.3.3-3)

RLC-Config ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
}
dl-AM-RLC SEQUENCE {
t-Reassembly ms200
}
}
}
7.1.2.3.9 AM RLC / Reassembling of AMD PDUs
(1)
ensure that {
，
when { UE receives AMD PDUs and all bytes of the RLC SDU(s) with SN = x are received }
then { UE reassembles the RLC SDU(s) from AMD PDU(s) with SN = x }
}
(2)
ensure that {
when { t-Reassembly expires }
then { update RX_Highest_Status to the SN of the first RLC SDU with SN >= RX_Next_Status_Trigger
for which not all bytes have been received }
}
(3)
ensure that {
when { UE receives AM PDU segments }
then { UE delivers reassembled RLC SDU to upper layer }
}
(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 AMD PDU segments with segments lost }
then { UE transmits STATUS PDU to request retransmission of missing segments }
}
(6)
ETSI
ensure that {
when { UE receives overlapping RLC AMD PDU segments }
then { UE discards duplicate RLC AMD PDU byte segments }
}
(7)
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}
}
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 38.322 clauses
4.2.1.3.3, 5.2.3.2.1, 5.2.3.2.2, 5.2.3.2.3, 5.2.3.2.4 and 5.3.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 4.2.1.3.3]
When the receiving side of an AM RLC entity receives AMD PDUs, it shall:
- detect whether or not the AMD PDUs have been received in duplication, and discard duplicated AMD PDUs;
- detect the loss of AMD PDUs at lower layers and request retransmissions to its peer AM RLC entity;
- reassemble RLC SDUs from the received AMD PDUs and deliver the RLC SDUs to upper layer as soon as they
are available.
[TS 38.322, clause 5.2.3.2.1]
The receiving side of an AM RLC entity shall maintain a receiving window according to the state variable RX_Next as
follows:
- a SN falls within the receiving window if RX_Next <= SN < RX_Next + AM_Window_Size;
- a SN falls outside of the receiving window otherwise.
When receiving an AMD PDU from lower layer, the receiving side of an AM RLC entity shall:
- either discard the received AMD PDU or place it in the reception buffer (see sub clause 5.2.3.2.2);
- if the received AMD PDU was placed in the reception buffer:
- update state variables and start t-Reassembly as needed (see sub clause 5.2.3.2.4).
[TS 38.322, clause 5.2.3.2.2]
- else:
ETSI
[TS 38.322, clause 5.2.3.2.3]
When an AMD PDU with SN = x is placed in the reception buffer, the receiving side of an AM RLC entity shall:
- if x >= RX_Next_Highest
- update RX_Next_Highest to x+ 1.
- if all bytes of the RLC SDU with SN = x are received:
- reassemble the RLC SDU from AMD PDU(s) with SN = x, remove RLC headers when doing so and deliver
the reassembled RLC SDU to upper layer;
- if x = RX_Highest_Status,
- update RX_Highest_Status to the SN of the first RLC SDU with SN > current RX_Highest_Status for
which not all bytes have been received.
- if x = RX_Next:
- update RX_Next to the SN of the first RLC SDU with SN > current RX_Next for which not all bytes
have been received.
- if RX_Next_Status_Trigger = RX_Next; or
- if RX_Next_Status_Trigger = RX_Next + 1 and there is no missing byte segment of the SDU associated with
SN = RX_Next before the last byte of all received segments of this SDU; or
- if RX_Next_Status_Trigger falls outside of the receiving window and RX_Next_Status_Trigger is not equal
to RX_Next + AM_Window_Size:
- if t-Reassembly is not running (includes the case t-Reassembly is stopped due to actions above):
- if RX_Next_Highest> RX_Next +1; or
- if RX_Next_Highest = RX_Next + 1 and there is at least one missing byte segment of the SDU associated
with SN = RX_Next before the last byte of all received segments of this SDU:
[TS 38.322, clause 5.2.3.2.4]
- update RX_Highest_Status to the SN of the first RLC SDU with SN >= RX_Next_Status_Trigger for which not
all bytes have been received;
- if RX_Next_Highest> RX_Highest_Status +1: or
- if RX_Next_Highest = RX_Highest_Status + 1 and there is at least one missing byte segment of the SDU
associated with SN = RX_Highest_Status before the last byte of all received segments of this SDU:
[TS 38.322, clause 5.3.4]
An AM RLC entity sends STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative
acknowledgements of RLC SDUs (or portions of them).
Triggers to initiate STATUS reporting include:
ETSI
- Polling from its peer AM RLC entity:
- When an AMD 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 AMD PDU is to be discarded as specified in subclause 5.2.3.2.2; or
- if x < RX_Highest_Status or x >= RX_Next + AM_Window_Size:
- trigger a STATUS report.
- else:
- delay triggering the STATUS report until x < RX_Highest_Status or x >= RX_Next +
AM_Window_Size.
NOTE 1: This ensures that the RLC Status report is transmitted after HARQ reordering.
- Detection of reception failure of an AMD PDU
- The receiving side of an AM RLC entity shall trigger a STATUS report when t-Reassembly expires.
NOTE 2: The expiry of t-Reassembly triggers both RX_Highest_Status to be updated and a STATUS report to be
triggered, but the STATUS report shall be triggered after RX_Highest_Status is updated.
lower layer.
- else:
- set the ACK_SN to the SN of the next not received RLC SDU which is not indicated as missing in the resulting
STATUS PDU.
ETSI
lower layer.
- else:
- set the ACK_SN to the SN of the next not received RLC SDU which is not indicated as missing in the
resulting STATUS PDU.
7.1.2.3.9.3.1-1.

Parameter Value
t-Reassembly ms150
ETSI

U-S Message/PDU/SDU
0 The SS stops the UL grant - - - -
transmission.
1 The SS transmits AMD PDU#1 <-- AMD PDU#1 (SN=3) - -
containing a complete RLC
SDU#4 (89 bytes and SI
field=00). (Note 4)
containing the last segment (44 segment 2
bytes) of RLC SDU#1 (SI
field=10, SO=45).
field=10, SO=45).
containing the first segment (45 segment 1
field=01).
containing the first segment (45 segment 1
bytes) of RLC SDU#1 (SI field
=01).
6 The SS waits for 20 ms then SS <-- UL Grants - -
transmits 2 uplink grants with a
time spacing of 20 ms. (Note 1)
7 Check: Does the UE transmit an --> AMD PDU (RLC SDU#1) 1,3 P
AMD PDU containing RLC
SDU#1 in its data field?
8 Check: Does the UE transmit an --> AMD PDU (RLC SDU#2) 1,3 P
SDU#2 in its data field?
9 Void
9A 110 ms after step 5 the SS starts <-- UL Grant - -
the UL default grant transmission.
10 Wait for t-reassembly of UE side --> STATUS PDU (ACK_SN=4, 2,7 P
to expire. NACK_SN=2)
Check: Does the UE transmit an
RLC STATUS PDU with
NACK_SN=2 and ACK_SN=4 to
correctly to inform SS of missing
RLC SDU#3?
10A The SS stops the UL grant - - - -
transmission.
11 120 ms after step 10 the SS <-- AMD PDU#6 (SN=2) - -
transmits AMD PDU#6 containing segment 1
the first 45 bytes of SDU#3 in its
data field. SO=0 and LSF=0. No
header extension part is
provided.(Note 5)
11A 20 ms after step 11 the SS <-- AMD PDU#6 (SN=2) - -
the first 45 bytes of SDU#3 in its
data field. SO=0 and LSF=0. No
header extension part is provided.
12 40 ms after step 11 the SS <-- AMD PDU#12 (SN=2, P=1) - -
transmits AMD PDU#12 segment 2
containing the last 44 bytes of
SDU#3 in its data field, with the
P-bit set. SO=45 and LSF=1. No
header extension part is provided.
ETSI
13 After the expiry of t-StatusProhibit <-- UL Grant - -

timer started at step 10, the SS
assigns 1 UL grant (UL grant
allocation type 3) of size 88 bits.
(Note 2)
14 Check: Does the UE transmit a --> STATUS PDU 1,3,4 P
STATUS PDU with ACK_SN=4,
thus acknowledging the reception
of PDUs with SN=0 to SN=3, and
no NACK_SN provided?
14A The SS waits for 40 ms to ensure <-- UL Grant - -
UE has all the required SDUs
available and then assigns 2 UL
grants of 768 bits (Note 1).
15 Check: Does the UE transmit --> (RLC SDU#3) 1,3,4 P
RLC SDU#3?
15A Check: Does the UE transmit --> (RLC SDU#4) 1,3,4 P
RLC SDU#4 with the P-bit set?
16 The SS transmits a STATUS <-- STATUS PDU (ACK SN=4) - -
PDU.
field=10, SO=45).
17A The SS starts the UL default <-- UL Grant - -
grant transmission.
to expire. NACK_SN=4 with SOStart=0
Check: Does the UE transmit an /SOEnd=44)
RLC STATUS PDU with
ACK_SN=5, NACK_SN=4 with
SOStart=0 and SOEnd=44?
transmission.
19 160 ms after step 18 The SS <-- AMD PDU#8 (SN=4, P=1) - -
the first segment (45 bytes) of
RLC SDU#5 (SI field=01). (Note
6)
20 Void
21 Void
21A After the expiry of t-StatusProhibit <-- UL Grant - -
(Note 2)
22 Check: Does the UE transmit an --> STATUS PDU (ACK_SN=5) 1,3,5 P
RLC STATUS PDU with
ACK_SN=5?
22A The SS waits for 100 ms then SS <-- UL Grant - -
transmits one uplink grant. (Note
1)
22B Check: Does the UE transmit an --> AMD PDU (RLC SDU#5) 1,3,5 P
SDU#5 in its data field with the P-
bit set?
22C The SS transmits a STATUS <-- STATUS PDU (ACK SN=5)
PDU
containing the last 29 bytes of segment 3
RLC SDU#6 (SI field=10,
SO=60).
23A The SS starts the UL default <-- UL Grant - -
grant transmission.
ETSI
24 Wait for t-reassembly of UE side --> STATUS PDU 2,5 P

to expire. (ACK_SN=6, NACK_SN=5 with
Check: Does the UE transmit an SOStart=0 / SOEnd=59)
RLC STATUS PDU with
containing the last 49 byte of RLC segment 2
SDU#6 (SI field=10, SO=40).
25A Void.
to expire. NACK_SN=5 with SOStart=0 /
Check: Does the UE transmit an SOEnd=39)
RLC STATUS PDU with
transmission.
27 160 ms after step 26 The SS <-- AMD PDU#11 (SN=5, P=1) - -
transmits AMD PDU#11 segment 1
containing the first 40 bytes of
RLC SDU#6 (SI field =01).
28 Void
29 Void
29A After the expiry of t-StatusProhibit <-- UL Grant - -
(Note 2, Note 7)
30 Check: Does the UE transmit an --> STATUS PDU (ACK_SN=6) 1,3,6 P
RLC STATUS PDU with
ACK_SN=6, thus acknowledging
the reception of RLC SDUs with
SN=0 to SN=5, and no NACK_SN
provided?
30A The SS transmits one uplink <-- UL Grant - -
grant. (Note 1)
30B Check: Does the UE transmit an --> AMD PDU (RLC SDU#6) 1,3,6 P
SDU#6 in its data field with the P-
bit set?
31 The SS transmits a STATUS <-- STATUS PDU (ACK SN=6) - -
PDU.
Note 1: UL grant of 768 bits(LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to transmit
one PDU at a time( 89 bytes RLC SDU + 3 bytes RLC Header + 2 bytes MAC Sub PDU header +
2 bytes for short BSR or padding).
Note 2: UL grant of 88 bits (LRBs & IMCS as per 38.523-3 [3] annex B) is chosen to allow the UE to transmit
a Status Report with ACK_SN(3 byte) + 2 Bytes MAC PDU subheader and (2 Bytes short BSR). 4
Bytes additional space provided to confirm UE does include resp. does not include NACK_SN
and conformant UE instead will include MAC Padding.
Note 3: Void
Note 4: The PDUs in steps 1-5 are scheduled with a 20 ms time spacing. The UL grant provision in step 6
is scheduled 20 ms later That way this step sequence takes less than t-Reassembly.
Note 5: Timing difference between step 10 to step 14 is equal to t-statusProhibit timer. UE starts SR from
step 12. 120 ms is chosen so that UE does not reach sr-transMax(n16) otherwise UE RACHes.
None.
ETSI
7.1.2.3.10 AM RLC / Re-transmission of RLC PDU with and 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
be transmitted as 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 { AMD PDU to be retransmitted does not fit in new allocated TBS }
then { UE segments AMD PDU }
}
(4)
ensure that {
when { AMD PDU segment to be retransmitted does not fit in new allocated TBS }
then { UE re-segments AMD PDU segment to fit TBS }
}
6.2.2.5, 6.2.3.3, 6.2.3.4, 6.2.3.5, 6.2.3.7, 6.2.3.10, 6.2.3.12, 6.2.3.14 and 6.2.3.15. Unless otherwise stated these are Rel-
15 requirements.
[TS 38.322, clause 5.3.2]
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 RLC SDU or an RLC SDU segment by the following:
- STATUS PDU from its peer AM RLC entity.
When receiving a negative acknowledgement for an RLC SDU or an RLC SDU segment 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 RLC SDU falls within the range TX_Next_Ack <= SN < = the highest SN of the
AMD PDU among the AMD PDUs submitted to lower layer:
- consider the RLC SDU or the RLC SDU segment for which a negative acknowledgement was received for
retransmission.
When an RLC SDU or an RLC SDU segment is considered for retransmission, the transmitting side of the AM RLC
entity shall:
- if the RLC SDU or RLC SDU segment is considered for retransmission for the first time:
- set the RETX_COUNT associated with the RLC SDU to zero.
ETSI
- else, if it (the RLC SDU or the RLC SDU segment that is considered for retransmission) is not pending for
retransmission already and the RETX_COUNT associated with the RLC SDU has not been incremented due to
another negative acknowledgment in the same STATUS PDU:
- increment the RETX_COUNT.
- if RETX_COUNT = maxRetxThreshold:
- indicate to upper layers that max retransmission has been reached.
When retransmitting an RLC SDU or an RLC SDU segment, the transmitting side of an AM RLC entity shall:
- if needed, segment the RLC SDU or the RLC SDU segment;
- form a new AMD PDU which will fit within the total size of AMD PDU(s) indicated by lower layer at the
particular transmission opportunity;
- submit the new AMD PDU to lower layer.
When forming a new AMD PDU, the transmitting side of an AM RLC entity shall:
- only map the original RLC SDU or RLC SDU segment to the Data field of the new AMD PDU;
- modify the header of the new AMD PDU in accordance with the description in sub clause 6.2.2.4;
- set the P field according to sub clause 5.3.3.
[TS 38.322, clause 6.2.2.4]
D/C P SI SN Oct 1
SN Oct 2
Data Oct 3
...
Oct N
SN Oct 2
SN Oct 3
Data Oct 4
...
Oct N
ETSI
D/C P SI SN Oct 1
SN Oct 2
SO Oct 3
SO Oct 4
Data Oct 5
...
Oct N
SN Oct 2
SN Oct 3
SO Oct 4
SO Oct 5
Data Oct 6
...
Oct N
[TS 38.322, clause 6.2.2.5]
STATUS PDU consists of a STATUS PDU payload and an RLC control PDU header.
RLC control PDU header consists of a D/C and a CPT field.
The STATUS PDU payload starts from the first bit following the RLC control PDU header, and it consists of one
ACK_SN and one E1, zero or more sets of a NACK_SN, an E1, an E2 and an E3, and possibly a pair of a SOstart and a
SOend or a NACK range field for each NACK_SN.
ETSI
D/C CPT ACK_SN Oct 1

ACK_SN Oct 2
E1 R R R R R R R Oct 3
NACK_SN Oct 4
NACK_SN E1 E2 E3 R Oct 5
NACK_SN Oct 6
SOstart Oct 8
SOstart Oct 9
SOend Oct 10
SOend Oct 11
NACK range Oct 12
NACK_SN Oct 13
...
Figure 6.2.2.5-1: STATUS PDU with 12 bit SN
D/C CPT ACK_SN Oct 1

ACK_SN Oct 2
ACK_SN E1 R Oct 3
NACK_SN Oct 4
NACK_SN Oct 5
NACK_SN E1 E2 E3 R R R Oct 6
NACK_SN Oct 7
NACK_SN Oct 8
SOstart Oct 10
SOstart Oct 11
SOend Oct 12
SOend Oct 13
NACK range Oct 14
NACK_SN Oct 15
NACK_SN Oct 16
... Oct 18
Figure 6.2.2.5-2: STATUS PDU with 18 bit SN
[TS 38.322, clause 6.2.3.3]
Length: 12 bits or 18 bits (configurable) for AMD PDU. 6 bits or 12 bits (configurable) for UMD PDU.
ETSI
The SN field indicates the sequence number of the corresponding RLC SDU. For RLC AM, the sequence number is
incremented by one for every RLC SDU. For RLC UM, the sequence number is incremented by one for every
segmented RLC SDU.
[TS 38.322, clause 6.2.3.4]
Length: 2 bits.
The SI field indicates whether an RLC PDU contains a complete RLC SDU or the first, middle, last segment of an RLC
SDU.

Value Description
00 Data field contains all bytes of an RLC SDU
01 Data field contains the first segment of an RLC SDU
10 Data field contains the last segment of an RLC SDU
11 Data field contains neither the first nor last segment of an RLC SDU
[TS 38.322, clause 6.2.3.5]
Length: 16 bits
The SO field indicates the position of the RLC SDU segment in bytes within the original RLC SDU. Specifically, the
SO field indicates the position within the original RLC SDU to which the first byte of the RLC SDU segment in the
Data field corresponds. The first byte of the original RLC SDU is referred by the SO field value "0000000000000000",
i.e., numbering starts at zero.
[TS 38.322, clause 6.2.3.7]
Length: 1 bit.
The P field indicates whether or not the transmitting side of an AM RLC entity requests a STATUS report from its peer
AM RLC entity. The interpretation of the P field is provided in Table 6.2.3.7-1.
Table 6.2.3.7-1: P field interpretation

Value Description
0 Status report not requested
1 Status report is requested
[TS 38.322, clause 6.2.3.10]
Length: 12 bits or 18 bits (configurable).
The ACK_SN field indicates the SN of the next not received RLC SDU which is not reported as missing in the
STATUS PDU. When the transmitting side of an AM RLC entity receives a STATUS PDU, it interprets that all RLC
SDUs up to but not including the RLC SDU with SN = ACK_SN have been received by its peer AM RLC entity,
excluding those RLC SDUs indicated in the STATUS PDU with NACK_SN, portions of RLC SDUs indicated in the
STATUS PDU with NACK_SN, SOstart and SOend, RLC SDUs indicated in the STATUS PDU with NACK_SN and
NACK_range, and portions of RLC SDUs indicated in the STATUS PDU with NACK_SN, NACK range, SOstart and
SOend.
[TS 38.322, clause 6.2.3.12]
Length: 12 bits or 18 bits (configurable).
The NACK_SN field indicates the SN of the RLC SDU (or RLC SDU segment) that has been detected as lost at the
receiving side of the AM RLC entity.
[TS 38.322, clause 6.2.3.14]
Length: 16 bits.
ETSI
The SOstart field (together with the SOend field) indicates the portion of the RLC SDU with SN = NACK_SN (the
NACK_SN for which the SOstart is related to) that has been detected as lost at the receiving side of the AM RLC entity.
Specifically, the SOstart field indicates the position of the first byte of the portion of the RLC SDU in bytes within the
original RLC SDU. The first byte of the original RLC SDU is referred by the SOstart field value "0000000000000000",
i.e., numbering starts at zero.
[TS 38.322, clause 6.2.3.15]
Length: 16 bits.
When E3 is 0, the SOend field (together with the SOstart field) indicates the portion of the RLC SDU with SN =
NACK_SN (the NACK_SN for which the SOend is related to) that has been detected as lost at the receiving side of the
AM RLC entity. Specifically, the SOend field indicates the position of the last byte of the portion of the RLC SDU in
bytes within the original RLC SDU. The first byte of the original RLC SDU is referred by the SOend field value
"0000000000000000", i.e., numbering starts at zero. The special SOend value "1111111111111111" is used to indicate
that the missing portion of the RLC SDU includes all bytes to the last byte of the RLC SDU.
When E3 is 1, the SOend field indicates the portion of the RLC SDU with SN = NACK_SN + NACK range - 1 that has
been detected as lost at the receiving side of the AM RLC entity. Specifically, the SOend field indicates the position of
the last byte of the portion of the RLC SDU in bytes within the original RLC SDU. The first byte of the original RLC
SDU is referred by the SOend field value "0000000000000000", i.e., numbering starts at zero. The special SOend value
"1111111111111111" is used to indicate that the missing portion of the RLC SDU includes all bytes to the last byte of
the RLC SDU.
Same Pre-test conditions as in clause 7.1.2.1.1 with the exception for the AM DRB is configured according to Tables
7.1.2.3.10.3.1-1.
Table 7.1.2.3.10.3.1-1: RLC settings
Parameter Value
ETSI

U-S Message
1 The SS transmits one AMD PDU containing <-- AMD PDU#1 - -
SDU#1 (91 bytes) in its data field.
2 The UE transmits one AMD PDU containing --> AMD PDU#1 (SN=0) - -
SDU#1 in its data field.
4 The UE transmits one AMD PDU containing --> AMD PDU#2 (SN=1) - -
5 The SS transmits a RLC STATUS PDU. <-- STATUS PDU - -
ACK_SN=2, NACK_SN=0.
6 Check: Does the UE transmit the AMD PDU --> AMD PDU#1 (SN=0) 1 P
not yet acknowledged?
ACK_SN=2.
9 The UE transmits an AMD PDU containing --> AMD PDU#3 (SN=2) - -
- EXCEPTION: Steps 10 to 11 shall be - - - -
repeated until RETX_COUNT=
maxRetxThreshold-1.
ACK_SN=3 and NACK_SN=2.
11 Check: Does the UE retransmit the AMD PDU --> AMD PDU#3 (SN=2) 2 P
not yet acknowledged?
ACK_SN=3.
13 The SS stops the UL grant transmission. - - - -
14 The SS transmits one AMD PDU containing <-- AMD PDU#4 (SN=3) - -
15 The SS waits for 60 ms and allocates one UL <-- (UL grant, 808 bits) - -
grant of size 808 bits.
(Note 1)
16 The UE transmits an AMD PDU with the same --> AMD PDU#4 (SN=3) - -
data contents as received in the
corresponding part of SDU#4?
17 The SS transmits a STATUS PDU. This PDU <-- STATUS PDU - -
nacks the AMD PDU with SN=3. ACK_SN=4
and NACK_SN=3.
18 The SS waits for 100 ms and then allocates 1 <-- (UL grant, 408 bits) - -
UL grant of size 408 bits (Note 2)
18A The SS waits for 20 ms and then allocates 1 <-- (UL grant, 456 bits) - -
UL grant of size 456 bits (Note 5)
19 Check: Does the UE transmit an SDU --> SDU#4 segment 1 (SN=3) 3 P
segment with SI=01 and SOEnd=43 and the
same data contents at the received positions
as in the original SDU#4?
20 Check: Does the UE transmit an SDU --> SDU#4 segment 2 (SN=3) 3 P
segment with SI=10 and SOStart=44 and the
21 After 100 ms SS transmits a STATUS PDU. <-- STATUS PDU - -
This PDU nacks the SDU with SN=3.
NACK_SN=3, SOStart=0, SOEnd=43 and
ACK_SN=4.
22 The SS waits for 100 ms and then allocates 2 <-- (UL grant, 240 bits) - -
UL grants (UL grant allocation type 2) at an
interval of 20 ms of size 240 bits (Note 3, Note
6)
22A - -
Void
ETSI
23 Check: Does the UE transmit an AMD PDU --> SDU#4 segment 1, first part 4 P
segment with SI=01 and SOEnd=22 and the (SN=3)
24 Check: Does the UE transmit an AMD PDU --> SDU#4 segment 1, second part 4 P
segment with SI=11, SOStart=23 and the (SN=3)
25 The SS transmits a STATUS PDU. This PDU <-- STATUS PDU - -
acks the AMD PDUs with SN=3. ACK_SN=4.
Note 1: UL grant of 808 bits=101 bytes (LRBs & IMCS as per 38.523-3[3] annex B) is chosen to allow the UE to
transmit one PDU and 2 bytes short BSR + 3 bytes padding or 5 bytes padding at a time.
Note 2: UL grant of 408 bits (LRBs & IMCS as per 38.523-3[3] annex B) is chosen such that UE will segment into 2
AMD PDUs. MAC PDU of 408 bits=51 bytes fit an AMD PDU payload of 44 bytes + 3 bytes for the first
segment of the AMD PDU header + 2 bytes for MAC header + 2 bytes of MAC BSR CE.
AMD PDUs. MAC PDU of 240 bits=30 bytes fit an AMD PDU payload of = 23 bytes + 3 bytes for the first
segment of the AMD PDU header + 2 bytes for MAC header + 2 bytes for MAC BSR CE.
Note 4: Void.
segment of the AMD PDU header + 2 bytes for MAC header +2 bytes for possible short BSR or padding
segment of the AMD PDU header + 2 bytes for MAC header +2 bytes for possible short BSR or padding
None.
7.1.2.3.11 AM RLC / RLC re-establishment procedure
(1)
ensure that {
then { The UE discards all RLC SDUs, RLC SDU segments, and RLC PDUs, if any }
}
(2)
ensure that {
then { The UE resets all state variables to their initial values }
}
References:
The conformance requirements covered in the present test case are specified in: TS 38.322, clauses 5.1.2, 7.1 and TS
38.331 clause 5.3.11. Unless otherwise stated these are Rel-15 requirements.
[TS 38.322, clause 5.1.2]
When upper layers request an RLC entity re-establishment, the UE shall:
- discard all RLC SDUs, RLC SDU segments, and RLC PDUs, if any;
- stop and reset all timers;
ETSI
- reset all state variables to their initial values.
[TS 38.322, clause 7.1]
This sub clause describes the state variables used in AM and UM entities in order to specify the RLC protocol. The state
All state variables related to AM data transfer can take values from 0 to 4095 for 12 bit SN or from 0 to 262143 for 18
bit SN. 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 4096 for 12 bit SN and
262144 for 18 bit SN).
SN).
When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.
TX_Next_Ack and RX_Next shall be assumed as the modulus base at the transmitting side and receiving side of an AM
RLC entity, respectively. This modulus base is subtracted from all the values involved, and then an absolute comparison
is performed (e.g. RX_Next <= SN < RX_Next + AM_Window_Size is evaluated as [RX_Next – RX_Next] modulo
2[sn-FieldLength] <= [SN – RX_Next] modulo 2[sn-FieldLength] < [RX_Next + AM_Window_Size – RX_Next] modulo 2[sn-
FieldLength]
), where sn-FieldLength is 12 or 18 for 12 bit SN and 18 bit SN, respectively.
RX_Next_Highest– 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.
(RX_Next_Highest– UM_Window_Size) <= SN < RX_Next_Highest is evaluated as [(RX_Next_Highest–
UM_Window_Size) – (RX_Next_Highest– UM_Window_Size)] modulo 2[sn-FieldLength] <= [SN – (RX_Next_Highest–
UM_Window_Size)] modulo 2[sn-FieldLength] < [RX_Next_Highest– (RX_Next_Highest– UM_Window_Size)] modulo
2[sn-FieldLength]), where sn-FieldLength is 6 or 12 for 6 bit SN and 12 bit SN, respectively.
The transmitting side of each AM RLC entity shall maintain the following state variables:
a) TX_Next_Ack – Acknowledgement state variable
This state variable holds the value of the SN of the next RLC SDU 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 RLC SDU with SN = TX_Next_Ack.
b) TX_Next – 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 constructs an AMD PDU with SN = TX_Next and contains an RLC
SDU or the last segment of a RLC SDU.
c) POLL_SN – Poll send state variable
This state variable holds the value of the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer
when POLL_SN is set according to sub clause 5.3.3.2. It is initially set to 0.
The transmitting side of each AM RLC entity shall maintain the following counters:
a) PDU_WITHOUT_POLL – Counter
This counter is initially set to 0. It counts the number of AMD PDUs sent since the most recent poll bit was transmitted.
b) BYTE_WITHOUT_POLL – Counter
This counter is initially set to 0. It counts the number of data bytes sent since the most recent poll bit was transmitted.
c) RETX_COUNT – Counter
ETSI
This counter counts the number of retransmissions of an RLC SDU or RLC SDU segment (see subclause 5.3.2). There
is one RETX_COUNT counter maintained per RLC SDU.
The receiving side of each AM RLC entity shall maintain the following state variables:
a) RX_Next – Receive state variable
This state variable holds the value of the SN following the last in-sequence completely received RLC SDU, and it
serves as the lower edge of the receiving window. It is initially set to 0, and is updated whenever the AM RLC entity
receives an RLC SDU with SN = RX_Next.
b) RX_Next_Status_Trigger – t-Reassembly state variable
This state variable holds the value of the SN following the SN of the RLC SDU which triggered t-Reassembly.
c) RX_Highest_Status – Maximum STATUS transmit state variable
This state variable holds the highest possible value of the SN which can be indicated by "ACK_SN" when a STATUS
PDU needs to be constructed. It is initially set to 0.
a) TX_Next
[TS 38.331, clause 5.3.11]
UE shall:
1> reset MAC;
2> stop timer T302;
1> stop all timers that are running except T320 and T325;
1> discard the UE Inactive AS context;
1> set the variable pendingRnaUpdate to false, if that is set to true;
1> discard the KgNB, the KRRCenc key, the KRRCint, the KUPint key and the KUPenc key, if any;
ETSI
1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP
entity and SDAP for all established RBs;
1> indicate the release of the RRC connection to upper layers together with the release cause;
1> enter RRC_IDLE and perform cell selection as specified in TS 38.304 [20], except if going to RRC_IDLE was
triggered by selecting an inter-RAT cell while T311 was running;
1> if going to RRC_IDLE was triggered by reception of the RRCRelease message including a waitTime:
2> inform the upper layer that access barring is applicable for all access categories except categories '0' and '2'.
Same Pre-test conditions as in clause 7.1.2.1.1 with the exception for the AM DRB is configured according to Table
7.1.2.3.11.3.1-1.

Parameter Value
t-Reassembly ms200
Table 7.1.2.3.11.3.1-2: PDCP parameters

Parameter Value
t-Reordering ms160
statusReportRequired Not present
ETSI

U-S Message
- The SS ignores scheduling requests and does - - - -
1 The SS creates 2 RLC SDUs of size 40 bytes <-- AMD PDU#1 - -
segmented into two AMD PDUs each. AMD AMD PDU#2
PDU#1 and AMD PDU#2 belong to RLC AMD PDU#4
SDU#1, AMD PDU#3 and #4 belong to RLC
SDU#2. SS transmits AMD PDU#1 (SN=0),
AMD PDU#2 (SN=0) and AMD PDU#4
(SN=1).
2 60 ms after sending PDU#1 in step 1 the SS <-- (UL grant) - -
allocates 1 UL grant of default size.
3 The UE returns RLC SDU#1. --> (RLC SDU#1) - -
4 The SS does not acknowledge the reception of - - - -
RLC SDU#1.
(Note 1) (Note 4) (Note 6) (Note 7)
transmissions
- EXCEPTION: Steps 7 and 8 can occur in any - - - -
order. (Note 8)
5)
8 The UE retransmits RLC SDU #1 (SN=0). --> (RLC SDU#1) - -
(Note 2)
9 SS transmits a STATUS PDU (ACK_SN = 1). <-- STATUS PDU - -
10 SS transmits AMD PDU#3 with SN=0 and the <-- AMD PDU#3 - -
P field set to "1"
11 Void
12 Check: For 1 second, does the UE return RLC --> (RLC SDU#2) 1 F
SDU#2
(Note 3)
13 SS transmits AMD PDU#4 with SN=0 <-- AMD PDU#4 - -
13 UE transmits a STATUS PDU (ACK_SN=1) --> STATUS PDU - -
A (Note 9)
14 Check: Does the UE return RLC SDU#2 with (RLC SDU#2) 2 P
SN=1? -->
(Note 9)
15 SS transmits a STATUS PDU (ACK_SN = 2) <-- STATUS PDU - -
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 2: The UE will retransmit the PDCP SDU associated with RLC SDU#1 in accordance to TS 38.323 clause 5.5
Note 3: AMD PDU#4 is discarded by a conformant UE in step 5.
[7], Table 4.6.1-8 using condition EN-DC_EmbedNR_RRCRecon, EN-DC_PSCell_HO and
RBConfig_NoKeyChange.
Note 6: For NR, the RRCReconfiguration message is as per RRCReconfiguration-HO with condition
RBConfig_NoKeyChange according to 38.508-1 [4], Table 4.8.1-1A.
Note 7: The expiry of t-Reassembly timer started in step 1 will trigger STATUS PDU from the UE. This starts SR.
The RRC reconfiguration is scheduled 300 ms in advance. sr-transMax is therefore set to n32 so that the
UE does not reach sr-transMax and then RACHes before reconfiguring.
Note 8: Per 38.508-1 Table 4.6.3-66: LogicalChannelConfig, both SRB1 and DRB have the same logical channel
priority with prioritisedBitRate as infinity.
Note 9 RLC PDUs at steps 13A and 14 may be received by the SS in the same slot or in multiple slots (max one
MAC PDU in a slot).
ETSI

sr-TransMax n32 7.1.2.3.11.3.2-1
Note 7
Table 7.1.2.3.11.3.3-1: RRCReconfiguration-HO (step 5, Table 7.1.2.3.11.3.3-1)
Derivation Path: 38.508-1 [4], Table 4.8.1-1A with condition RBConfig_NoKeyChange
Table 7.1.2.3.11.3.3-2: Void
7.1.3 PDCP
7.1.3.0 Default Pre-Test Conditions for all PDCP test cases

The following pre-test conditions shall be applied in all PDCP test cases until the test case explicitly over writes these
conditions
System Simulator:
- The SS configures the test environment in accordance to the execution conditions in Table 7.1.3.0-1.
UE:
- None
Preamble:
execution conditions in Table 7.1.3.0-2 and using the message condition UE TEST LOOP MODE A to return
one UL PDCP SDU per DL PDCP SDU.
Table 7.1.3.0-1: Test environment

Combination
IF pc_NG_RAN_NR and NR Cell 1 is PCell NR System information
Connectivity(NR-DC) NR Cell 10 is PSCell Combination NR-1
IF pc_NG_RAN_NR NR Cell 1 NR System information
Combination NR-1
NR: N/A
NR: N/A
ETSI
Table 7.1.3.0-2: Preamble parameters

Execution ConditionMulti-PDN / Multi- Generic Procedure Parameters Primary DRB used for
Condition
One DRB
Connectivity(NR-DC), SN terminated SCG DRB
DC bearer(One MN Terminated MCG
bearer and One SN Terminated SCG
bearer),
TRUE Connectivity(NR), Default DRB of the first
N DRBs (N ≥ 2)
Connectivity(NR-DC), SN terminated SCG DRB
DC bearer(N MN Terminated MCG
bearers and One SN Terminated SCG
bearer),
N DRBs (N ≥ 2)
bearer),
bearer),
bearer),
bearer),
Table 7.1.3.0-3: Message conditions

Condition
IF Message with condition AM is used for step 7 in 4.5.4.2
pc_NG_RAN_NR according to [4]
pc_EN_DC is used for step 7 in 4.5.4.2 according to [4]
pc_NGEN_DC is used for step 7 in 4.5.4.2 according to [4]
7.1.3.1 Maintenance of PDCP sequence numbers for radio bearers
7.1.3.1.1 Maintenance of PDCP sequence numbers / User plane / 12 bit SN
(1)
with { UE in RRC_CONNECTED state with PDCP configured for 12 bit SN}
ETSI
ensure that {
when { UE transmits a PDCP Data SDU on a DRB }
then { UE increments SN with 1 for each transmitted PDU for SN=0 to Maximum_PDCP_SN (2[pdcp-SN-SizeUL]
-1) }
}
(2)
with { UE in RRC_CONNECTED state with PDCP configured for 12 bit SN }
ensure that {
when { UE transmits a PDCP Data SDU on a DRB and, after incrementation, TX_NEXT is larger than the
Maximum_PDCP_SN(2[pdcp-SN-SizeUL] -1) }
then { UE sets SN to 0 in the next transmitted PDCP SDU}
}
References: The conformance requirements covered in the present TC are specified in: TS 38.323, clauses 5.2.1, 5.2.2.1
and 6.2.2.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.323, clause 5.2.1]
At reception of a PDCP SDU from upper layers, the transmitting PDCP entity shall:
- start the discardTimer associated with this PDCP SDU (if configured).
For a PDCP SDU received from upper layers, the transmitting PDCP entity shall:
- associate the COUNT value corresponding to TX_NEXT to this PDCP SDU;
NOTE 1: Associating more than half of the PDCP SN space of contiguous PDCP SDUs with PDCP SNs, when
e.g., the PDCP SDUs are discarded or transmitted without acknowledgement, may cause HFN
desynchronization problem. How to prevent HFN desynchronization problem is left up to UE
implementation.
- perform header compression of the PDCP SDU as specified in the subclause 5.7.4;
- perform integrity protection, and ciphering using the TX_NEXT as specified in the subclause 5.9 and 5.8,
respectively;
- set the PDCP SN of the PDCP Data PDU to TX_NEXT modulo 2[pdcp-SN-Size];
- increment TX_NEXT by one;
- submit the resulting PDCP Data PDU to lower layer as specified below.
When submitting a PDCP Data PDU to lower layer, the transmitting PDCP entity shall:
- if the transmitting PDCP entity is associated with one RLC entity:
- submit the PDCP Data PDU to the associated RLC entity.
- else, if the transmitting PDCP entity is associated with two RLC entities:
- if pdcpDuplication is configured and activated:
- duplicate the PDCP Data PDU and submit the PDCP Data PDU to both associated RLC entities.
- else, if pdcpDuplication is configured but not activated:
- submit the PDCP Data PDU to the primary RLC entity.
- else:
- if the total amount of PDCP data volume and RLC data volume pending for initial transmission (as
specified in TS 36.322 [5]) in the two associated RLC entities is less than ul-DataSplitThreshold:
ETSI
- else:
- submit the PDCP Data PDU to either the primary RLC entity or the secondary RLC entity.
NOTE 2: If the transmitting PDCP entity is associated with two RLC entities, the UE should minimize the amount
of PDCP PDUs submitted to lower layers before receiving request from lower layers and minimize the
PDCP SN gap between PDCP PDUs submitted to two associated RLC entities to minimize PDCP
reordering delay in the receiving PDCP entity.
[TS 38.323, clause 5.2.2.1]
In this section, following definitions are used:
- HFN(State Variable): the HFN part (i.e. the number of most significant bits equal to HFN length) of the State
Variable;
- SN(State Variable): the SN part (i.e. the number of least significant bits equal to PDCP SN length) of the State
Variable;
- RCVD_SN: the PDCP SN of the received PDCP Data PDU, included in the PDU header;
- RCVD_HFN: the HFN of the received PDCP Data PDU, calculated by the receiving PDCP entity;
- RCVD_COUNT: the COUNT of the received PDCP Data PDU = [RCVD_HFN, RCVD_SN]
At reception of a PDCP Data PDU from lower layers, the receiving PDCP entity shall determine the COUNT value of
the received PDCP Data PDU, i.e. RCVD_COUNT, as follows:
- if RCVD_SN < SN(RX_DELIV) – Window_Size:
- RCVD_HFN = HFN(RX_DELIV) + 1.
- else if RCVD_SN >= SN(RX_DELIV) + Window_Size:
- RCVD_HFN = HFN(RX_DELIV) – 1.
- else:
- RCVD_HFN = HFN(RX_DELIV);
- RCVD_COUNT = [RCVD_HFN, RCVD_SN].
After determining the COUNT value of the received PDCP Data PDU = RCVD_COUNT, the receiving PDCP entity
shall:
- if RCVD_COUNT < RX_DELIV; or
- if the PDCP Data PDU with COUNT = RCVD_COUNT has been received before:
- perform deciphering and integrity verification of the PDCP Data PDU using COUNT = RCVD_COUNT;
- if integrity verification fails:
- indicate the integrity verification failure to upper layer;
- discard the PDCP Data PDU.
- else:
- discard the PDCP Data PDU.
ETSI
If the received PDCP Data PDU with COUNT value = RCVD_COUNT is not discarded above, the receiving PDCP
entity shall:
- store the resulting PDCP SDU in the reception buffer;
- if RCVD_COUNT >= RX_NEXT:
- update RX_NEXT to RCVD_COUNT + 1.
- if outOfOrderDelivery is configured:
- deliver the resulting PDCP SDU to upper layers.
- if RCVD_COUNT = RX_DELIV:
- deliver to upper layers in ascending order of the associated COUNT value after performing header
decompression, if not decompressed before;
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from COUNT =
RX_DELIV;
- update RX_DELIV to the COUNT value of the first PDCP SDU which has not been delivered to upper
layers, with COUNT value > RX_DELIV;
- if t-Reordering is running, and if RX_DELIV >= RX_REORD:
- stop and reset t-Reordering.
- if t-Reordering is not running (includes the case when t-Reordering is stopped due to actions above), and
RX_DELIV < RX_NEXT:
- update RX_REORD to RX_NEXT;
- start t-Reordering.
[TS 38.322, clause 6.2.2.2]
Figure 6.2.2.2-1 shows the format of the PDCP Data PDU with 12 bits PDCP SN. This format is applicable for UM
DRBs and AM DRBs.
Figure 6.2.2.2-1: PDCP Data PDU format with 12 bits PDCP SN
ETSI
Same Pre-test conditions as in clause 7.1.3.0 exception of PDCP parameters according to Table 7.1.3.1.1.3.1-1.
PDCP-Config pdcp-SN-SizeUL len12bits

PDCP-Config pdcp-SN-SizeDL len12bits

U-S Message
- EXCEPTION: Steps 1 – 2 shall be repeated - - - -
from j = 0 to j =
FLOOR(Maximum_PDCP_SN/iteration_size).
(Note 1, 4)
1 SS transmits in one slot, several PDCP PDUs <-- PDCP PDUs - -
in a PDCP PDU list without header
compression, the number of PDCP PDUs sent
in each PDCP PDU list is defined by the
iteration_size. (Note 4, 5).
- EXCEPTION: In Step 2, SS may receive a - - - -
PDCP PDU or several PDCP PDUs, then step
2 may be repeated multiple times until all
PDCP PDUs with SN=j*iteration_size to
SN=(((j+1)* iteration_size)-1) for each iteration
are received.
2 CHECK: Does UE transmit PDCP PDUs with --> PDCP PDUs 1 P
SN=0 for the first iteration and all PDCP PDUs
for each iteration?
(Note 2) (Note 6)
3 SS transmits a PDCP PDU containing one <-- PDCP PDU - -
PDCP SDU without header compression.
4 CHECK: Does UE transmit a PDCP PDU with --> PDCP PDU 2 P
SN=0?
5 SS transmits a PDCP PDU containing one <-- PDCP PDU - -
PDCP SDU without header compression.
6 CHECK: Does UE transmit a PDCP PDU with --> PDCP PDU 1 P
SN=1?
Note 1: Maximum_PDCP_SN = 2[pdcp-SN-SizeUL] -1.
Note 2: The verdict shall be provided each time [(SN+1) mod 256 = 0] for 12 bit SN and [(SN+1) mod 4096 = 0] for
18 bit SN respectively.
Note 3: Void
Note 4: Iteration will be incremented by iteration_size of 1 for 12 bit SN and iteration_size of 25.for 18 bits SN. Small
PDCP SDU size will be used.
Note 5: SS shall transmit a PDCP PDU list with size equal to iteration_size and incrementing SN by 1 till SN =
((j+1)*iteration_size)-1.
Note 6 All PDCP PDUs may be received by the SS in the same slot or in multiple slots (max one MAC PDU in a slot)
None.
ETSI
7.1.3.1.2 Maintenance of PDCP sequence numbers / User plane / 18 bit SN
(1)
with { UE in RRC_CONNECTED state with PDCP configured for 18 bit SN}
ensure that {
when { UE transmits a PDCP Data SDU on a DRB }
then { UE increments SN with 1 for each transmitted PDU for SN=0 to Maximum_PDCP_SN (2[pdcp-SN-SizeUL]
-1) }
}
(2)
with { UE in RRC_CONNECTED state with PDCP configured for 18 bit SN }
ensure that {
when { UE transmits a PDCP Data SDU on a DRB and, after incrementation, TX_Next is larger than the
Maximum_PDCP_SN (2[pdcp-SN-SizeUL] -1) }
then { UE sets SN to 0 in the next transmitted PDCP SDU}
}
Same as conformance requirements in clause 7.1.3.1.1.2
PDCP-Config pdcp-SN-SizeUL len18bits

PDCP-Config pdcp-SN-SizeDL len18bits
None.
7.1.3.2 PDCP integrity protection
7.1.3.2.1 Integrity protection / Correct functionality of integrity algorithm SNOW3G / SRB /

DRB
(1)
with { UE in RRC_CONNECTED state and SRB is configured with NR-PDCP}
ensure that {
when { Functionality of integrity algorithms with SNOW3G is taken into use on SRB }
then { UE performs correct integrity protection function in NR-PDCP entities associated with SRB
}
}
(2)
with { UE in RRC_CONNECTED state and NOT EN-DC }
ensure that {
ETSI
when { Functionality of integrity algorithms with SNOW3G is taken into use on DRB }
then { UE performs correct integrity protection function in PDCP entities associated with DRB }
}
(3)
with { UE in RRC_CONNECTED state and SRB3 is configured }
ensure that {
when { message on SRB 3 is received and fails the integrity protection check }
then { UE transmits SCGFailureInformationNR message with failure type 'srb3-IntegrityFailure' }
}
NOTE: TP2 (integrity on DRB) is not applicable to EN-DC as per 38.331 clause 6.3.2, the IE PDCP-
Config.drb.integrityProtection is‘ Cond ConnectedTo5GC‘.
References: The conformance requirements covered in the present TC are specified in: TS 38.323, clauses 5.9, 5.2.2.1,
TS 33.501 clauses 5.6.2, D.3.1 and TS 38.331 clauses5.7.3.1, 5.7.3.2, 5.7.3.3. Unless otherwise stated these are Rel-15
requirements.
[TS 38.323, clause 5.9]
The integrity protection function includes both integrity protection and integrity verification and is performed in PDCP,
if configured. The data unit that is integrity protected is the PDU header and the data part of the PDU before ciphering.
The integrity protection is always applied to PDCP Data PDUs of SRBs. The integrity protection is applied to PDCP
Data PDUs of DRBs for which integrity protection is configured. The integrity protection is not applicable to PDCP
Control PDUs.
The integrity protection algorithm and key to be used by the PDCP entity are configured by upper layers TS 38.331 [3]
and the integrity protection method shall be applied as specified in TS 33.501 [6].
The integrity protection function is activated by upper layers TS 38.331 [3]. When security is activated, the integrity
protection function shall be applied to all PDUs including and subsequent to the PDU indicated by upper layers TS
38.331 [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.
For downlink and uplink integrity protection and verification, the parameters that are required by PDCP for integrity
protection are defined in TS 33.501 [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
specified in TS 33.501 [6]). The parameters required by PDCP which are provided by upper layers TS 38.331 [3] are
listed below:
- BEARER (defined as the radio bearer identifier in TS 33.501 [6]. It will use the value RB identity –1 as in TS
38.331 [3]);
- KEY (the integrity protection keys for the control plane and for the user plane are KRRCint and KUPint,
respectively).
At transmission, the UE computes the value of the MAC-I field and at reception it verifies the integrity of the PDCP
Data 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 38.323, clause 5.2.2.1]
ETSI
- else:
shall:
- discard the PDCP Data PDU;
[TS 33.501, clause 5.6.2]
All Identifiers and names specified in the present subclause are for 5G.
Each Integrity Algorithm used for 5G will be assigned a 4-bit identifier. The following values for integrity algorithms
are defined:
"00002" NIA0 Null Integrity Protection algorithm;
"00012" 128-NIA1 128-bit SNOW 3G based algorithm;
"00102" 128-NIA2 128-bit AES based algorithm; and
"00112" 128-NIA3 128-bit ZUC based algorithm.
128-NIA1 is based on SNOW 3G (see TS35.215 [14]).
128-NIA2 is based on 128-bit AES [15] in CMAC mode [17].
128-NIA3 is based on 128-bit ZUC (see TS35.221 [18]).
Full details of the algorithms are specified in Annex D.
[TS 33.501, clause D.3.1.1]
The input parameters to the integrity algorithm are a 128-bit integrity key named KEY, a 32-bit COUNT, a 5-bit bearer
identity called BEARER, the 1-bit direction of the transmission i.e. DIRECTION, and the message itself i.e.
MESSAGE. The DIRECTION bit shall be 0 for uplink and 1 for downlink. The bit length of the MESSAGE is
LENGTH.
Figure D.3.1.1-1 illustrates the use of the integrity algorithm NIA to authenticate the integrity of messages.
ETSI
COUNT DIRECTION COUNT DIRECTION
MESSAGE BEARER MESSAGE BEARER
KEY NIA KEY NIA
Sender MAC-I/NAS-MAC XMAC-I/XNAS-MAC Receiver
Figure D.3.1.1-1: Derivation of MAC-I/NAS-MAC (or XMAC-I/XNAS-MAC)
Based on these input parameters the sender computes a 32-bit message authentication code (MAC-I/NAS-MAC) using
the integrity algorithm NIA. The message authentication code is then appended to the message when sent. For integrity
protection algorithms, the receiver computes the expected message authentication code (XMAC-I/XNAS-MAC) on the
message received in the same way as the sender computed its message authentication code on the message sent and
verifies the data integrity of the message by comparing it to the received message authentication code, i.e. MAC-I/NAS-
MAC.
[TS 38.331, clause 5.7.3.1]
UE RAN
RRC connection reconfiguration
SCGFailureInformation
Figure 5.7.3.1-1: SCG failure information
The purpose of this procedure is to inform EUTRAN or NR MN about an SCG failure the UE has experienced i.e. SCG
radio link failure, e failure of SCG reconfiguration with sync, SCG configuration failure for RRC message on SRB3,
SCG integrity check failure and exceeding the maximum uplink transmission timing difference.
[TS 38.331, clause 5.7.3.2]
A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the
following conditions is met:
1> upon detecting radio link failure for the SCG, in accordance with subclause 5.3.10.3;
1> upon reconfiguration with sync failure of the SCG, in accordance with subclause 5.3.5.9.3;
1> upon SCG configuration failure, in accordance with subclause 5.3.5.9.2;
1> upon integrity check failure indication from SCG lower layers, in accordance with subclause 5.3.5.9.1.
Upon initiating the procedure, the UE shall:
1> suspend SCG transmission for all SRBs and DRBs;
1> reset SCG-MAC;
ETSI
1> stop T304, if running;
1> if the UE is operating in EN-DC:
2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10, 5.6.13a].
[TS 38.331, clause 5.7.3.3]
The UE shall set the SCG failure type as follows:
...
1> else, if the UE initiates transmission of the SCGFailureInformationNR message due to SRB3 IP check failure:
2> set the failureType as srb3-IntegrityFailure;
- Same Pre-test conditions as in clause 7.1.3.0 with the exception that integrity protection algorithm ‘nia1
(SNOW3G)’ is configured.
- For EN_DC, same Pre-test conditions as in clause 7.1.3.0 with the exception that integrity protection algorithms
‘nia1 (SNOW3G)’ and ‘eia1 (SNOW3G)’ are configured and without message condition UE TEST LOOP
MODE A.
- For EN_DC or NGEN_DC, RRCConnectionReconfiguration message including MobilityControlInfo IE is

transmitted on E-UTRA Cell 1 to reconfigure SRB1 and SRB2 from E-UTRA PDCP to NR PDCP.
ETSI

U-S Message
- EXCEPTION: Steps 1a1 to 1b2 describe - - - -
behaviour that depends on UE configuration;
sequence that takes place depending on a
particular configuration.
1a1 IF Connectivity is EN-DC or NGEN-DC, the SS <-- RRC: UECapabilityEnquiry - -
sends EUTRA RRC UECapabilityEnquiry
message including RAT-Type eutra-nr to the
UE integrity protected.
1a2 Check: Does the UE send a EUTRA RRC --> RRC: UECapabilityInformation 1 P
UECapabilityInformation message integrity
protected?
1b1 ELSE the SS sends NR RRC <-- NR RRC: UECapabilityEnquiry - -
UECapabilityEnquiry message to the UE.
1b2 Check: Does the UE send a NR RRC --> NR RRC: UECapabilityInformation 1 P
UECapabilityInformation message?
- EXCEPTION: Steps 2a1-2a4 describe - - - -
sequence that takes place if SRB3 is
configured
2a1 IF Connectivity is EN-DC or NGEN-DC, IF <-- RRCReconfiguration - -
pc_srb3 then the SS transmits an
RRCReconfiguration message to reconfigure
NR MAC, sent on SRB3 integrity protected.
Note 1
2a2 Check: Does the UE transmit an --> RRCReconfigurationComplete 1 P
RRCReconfigurationComplete message on
SRB3 integrity protected?
2a3 The SS sends RRCReconfiguration message <-- RRCReconfiguration - -
to the UE integrity protected on SRB3. The
MAC-I is corrupted so as to result in integrity
failure at UE.
2a4 Check: Does the UE send --> SCGFailureInformationNR 3 P
SCGFailureInformationNR with failureType
‘srb3-IntegrityFailure’ on SRB1?
behaviour that depends on whether 5GC is
being emulated; the "lower case letter"
identifies a step sequence that takes place if
5GC is being emulated.
3a1 SS transmits PDCP PDU on DRB integrity <-- PDCP PDU - -
protected.
3a2 Check: Does the UE transmit looped back --> PDCP PDU 2 P
PDCP PDU integrity protected on DRB?
Note 1: For EN-DC the NR RRCReconfiguration is contained in RRCConnectionReconfiguration Table
7.1.3.2.1.3.3-1
ETSI
Table 7.1.3.2.1.3.3-1: RRCConnectionReconfiguration (Preamble for EN-DC or NGEN-DC)
Derivation Path: 36.508 [7] Table 4.6.1-8

c1 CHOICE{
{
mobilityControlInfo MobilityControlInfo-HO- As per Table
SameCell 7.1.3.2.1.3.3-1A
setup SEQUENCE {
including the
RRCReconfiguration
message according to TS
38.508-1 [4], table 4.6.1-
13 with condition EN-
DC_HO
}
}
sk-Counter-r15 Increment the value by 1
from the previous value
including
RadioBearerConfig
[4], Table 4.6.3-132 with
and Re-establish_PDCP
nr-RadioBearerConfig1-r15 OCTET STRING SRB3
including
RadioBearerConfig
[4], Table 4.6.3-132 with
and SRB3
including
RadioBearerConfig
[4], table 4.6.3-132 with
condition
SRB_NR_PDCP
}
}
}
}
}
}
}
}
}
}
}
ETSI
SRB3 Establishment of SRB3
Table 7.1.3.2.1.3.3-1A: MobilityControlInfo-HO-SameCell (Table 7.1.3.2.1.3.3-1)

MobilityControlInfo-HO ::= SEQUENCE {
targetPhysCellId PhysicalCellIdentity of E-
UTRA Cell 1
carrierFreq Not present
}
Table 7.1.3.2.1.3.3-2: MAC-CellGroupConfig (step 2a1, Table 7.1.3.2.1.3.2-1)

periodicBSR-Timer sf10 Different from
default
}
}
Table 7.1.3.2.1.3.3-3: SCGFailureInformationNR message (step 2a4, Table 7.1.3.2.1.3.2-1)
Derivation Path: 36.508 [7], Table 4.6.1-18AA

SCGFailureInformationNR-r15::= SEQUENCE {
c1 CHOICE {
scgFailureInformationNR-r15 SEQUENCE {
failureReportSCG-NR-r15 SEQUENCE {
failureType-r15 srb3-IntegrityFailure
measResultFreqListNR-r15 Not checked
measResultSCG-r15 Not checked
}
nonCriticalExtension SEQUENCE {}
}
}
}
}
Table 7.1.3.2.1.3.3-4: RRCReconfiguration (Preamble for NR/5GC)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR

radioBearerConfig RadioBearerConfig-
IntegrityOnDRB
}
}
}
ETSI
Table 7.1.3.2.1.3.3-5: RadioBearerConfig-IntegrityOnDRB (Preamble for NR/5GC)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-132 with conditions SRB2 and DRB1
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) 1 entry Primary DRB as DRB1
OF DRB-ToAddMod { per Table 7.1.3.0-
2
DRB-ToAddMod[1] SEQUENCE { entry 1
cnAssociation CHOICE {
sdap-Config SDAP-Config
}
drb-Identity DRB-Identity using
condition DRB1
reestablishPDCP Not present
recoverPDCP Not present
pdcp-Config PDCP-Config-
IntegrityOnDRB
}
}
}
Table 7.1.3.2.1.3.3-6: PDCP-Config-IntegrityOnDRB (Preamble for NR/5GC)

PDCP-Config ::= SEQUENCE {
drb SEQUENCE {
discardTimer infinity
pdcp-SN-Size-UL len18bits
pdcp-SN-Size-DL len18bits
headerCompression CHOICE {
notUsed NULL
}
integrityProtection enabled
statusReportRequired true
outOfOrderDelivery Not present
}
moreThanOneRLC Not present
t-Reordering Not present
}
7.1.3.2.2 Integrity protection / Correct functionality of integrity algorithm AES / SRB / DRB
(1)
with { UE in RRC_CONNECTED state and SRB is configured with NR-PDCP }
ensure that {
when { Functionality of integrity algorithms with AES is taken into use on SRB }
then { UE performs correct integrity protection function in NR-PDCP entity associated with SRB }
}
(2)
ensure that {
when { Functionality of integrity algorithms with AES is taken into use on DRB }
}
ETSI
(3)
ensure that {
then { UE transmits SCGFailureInformationNR message with failure type as srb3-IntegrityFailure }
}
NOTE: TP2 (integrity on DRB) is not applicable to EN-DC as per TS 38.331 [12] clause 6.3.2, the IE PDCP-
Config.drb.integrityProtection is 'Cond ConnectedTo5GC'.
Same conformance requirements as in clause 7.1.3.2.1.2
Same Pre-test conditions as in clause 7.1.3.2.1.3.1 except that integrity protection algorithm ‘nia2 (AES)’ and ‘eia2
(AES)’ is configured.
Same test procedure sequence as in clause 7.1.3.2.1.3.2.
Same specific message contents as in clause 7.1.3.2.1.3.3 except for integrity protection algorithm ‘nia2 (AES)’ and
‘eia2 (AES)’.
7.1.3.2.3 Integrity protection / Correct functionality of integrity algorithm ZUC / SRB / DRB
(1)
ensure that {
when { Functionality of integrity algorithms with ZUC is taken into use on SRB }
then { UE performs correct integrity protection function in NR-PDCP entities associated with SRB
}
}
(2)
ensure that {
when { Functionality of integrity algorithms with ZUC is taken into use on DRB }
}
(3)
ensure that {
then { UE transmits SCGFailureInformationNR message with failure type as srb3-IntegrityFailure }
}
NOTE: TP2 (integrity on DRB) is not applicable to EN-DC as per TS 38.331 [12] clause 6.3.2, the IE PDCP-
Config.drb.integrityProtection is 'Cond ConnectedTo5GC.
Same conformance requirements as in clause 7.1.3.2.1.2.
ETSI
Same Pre-test conditions as in clause 7.1.3.2.1.3.1 except that integrity protection algorithm ‘nia3 (ZUC)’ and ‘eia3
(ZUC)’ is configured.
Same test procedure sequence as in clause 7.1.3.2.1.3.2.
Same specific message contents as in clause 7.1.3.2.1.3.3 except integrity protection algorithm ‘nia3 (ZUC)’ and ‘eia3
(ZUC)’.
7.1.3.3 PDCP Ciphering and deciphering
7.1.3.3.1 Ciphering and deciphering / Correct functionality of encryption algorithm

SNOW3G / SRB / DRB
(1)
(1)
ensure that {
when { Functionality of encryption algorithms with SNOW3G is taken into use on SRB }
then { UE performs correct ciphering/deciphering function in NR-PDCP entity associated with SRB
}
}
(2)
ensure that {
when { Functionality of encryption algorithms with SNOW3G is taken into use on DRB }
then {UE performs correct ciphering/deciphering function in NR-PDCP entity associated with DRB }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.323 clause 5.8, TS 33.501
clauses 5.6.1, D.2.1.1 and TS 36.331 clause 6.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.323, clause 5.8]
The ciphering function includes both ciphering and deciphering and is performed in PDCP, if configured. The data unit
that is ciphered is the data part of the PDCP Data PDU (see subclause 6.3.3) except the SDAP header if included in the
PDCP SDU, and the MAC-I (see subclause 6.3.4). The 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 TS 38.331 [3] and the
ciphering method shall be applied as specified in TS 33.501 [6].
The ciphering function is activated by upper layers TS 38.331 [3]. When security is activated, the ciphering function
shall be applied to all PDCP Data PDUs indicated by upper layers TS 38.331 [3] for the downlink and the uplink,
respectively.
For downlink and uplink ciphering and deciphering, the parameters that are required by PDCP for ciphering are defined
in TS 33.501 [6] and are input to the ciphering algorithm. The required inputs to the ciphering function include the
ETSI
COUNT value, and DIRECTION (direction of the transmission: set as specified in TS 33.501 [6]).The parameters
required by PDCP which are provided by upper layers TS 38.331 [3] are listed below:
38.331 [3]);
- KEY (the ciphering keys for the control plane and for the user plane are KRRCenc and KUPenc, respectively).
[TS 33.501, clause 5.6.1]
All Identifiers and names specified in this subclause are for5G.
Each Encryption Algorithm used for 5G will be assigned a 4-bit identifier. The following values for ciphering
algorithms are defined:
"00002" NEA0 Null ciphering algorithm;
"00012" 128-NEA1 128-bit SNOW 3G based algorithm;
"00102" 128-NEA2 128-bit AES based algorithm; and
"00112" 128-NEA3 128-bit ZUC based algorithm.
128-NEA1 is based on SNOW 3G (see TS35.215 [14]).
128-NEA2 is based on 128-bit AES [15] in CTR mode [16].
128-NEA3 is based on 128-bit ZUC (sseTS35.221 [18]).
Full details of the algorithms are specified in Annex D.
[TS 33.501, clause D.2.1.1]
The input parameters to the ciphering algorithm are a 128-bit cipher key named KEY, a 32-bit COUNT, a 5-bit bearer
identity BEARER, the 1-bit direction of the transmission i.e. DIRECTION, and the length of the keystream required i.e.
LENGTH. The DIRECTION bit shall be 0 for uplink and 1 for downlink.
Editor’s Note: For NAS layer security, the inputs may need to change depending on the solution that is selected for
having simultaneous NAS connections for 3GPP and non-3GPP.
Figure D.2.1.1-1 illustrates the use of the ciphering algorithm NEA to encrypt plaintext by applying a keystream using a
bit per bit binary addition of the plaintext and the keystream. The plaintext may be recovered by generating the same
keystream using the same input parameters and applying a bit per bit binary addition with the ciphertext.
ETSI
COUNT DIRECTION COUNT DIRECTION
BEARER LENGTH BEARER LENGTH
KEY NEA KEY NEA
KEYSTREAM KEYSTREAM
BLOCK BLOCK
PLAINTEXT CIPHERTEXT PLAINTEXT

BLOCK BLOCK BLOCK
Sender Receiver
Figure D.2.1.1-1: Ciphering of data
Based on the input parameters the algorithm generates the output keystream block KEYSTREAM which is used to
encrypt the input plaintext block PLAINTEXT to produce the output ciphertext block CIPHERTEXT.
The input parameter LENGTH shall affect only the length of the KEYSTREAM BLOCK, not the actual bits in it.
[TS 36.331, clause 6.3.3]
The IE SecurityAlgorithmConfig is used to configure AS integrity protection algorithm (SRBs) and AS ciphering
algorithm (SRBs and DRBs).
SecurityAlgorithmConfig field descriptions

cipheringAlgorithm
Indicates the ciphering algorithm to be used for SRBs and DRBs, as specified in TS 33.501 [11]. The algorithms nea0-nea3 are
identical to the LTE algorithms eea0-3. For EN-DC, the algorithms configured for bearers using KeNB shall be the same as for all
bearers using KeNB.
integrityProtAlgorithm
For EN-DC, this IE indicates the integrity protection algorithm to be used for SRBs, as specified in TS 33.501 [11]. The algorithms
nia0-nia3 is identical to the LTE algorithms eia0-3. For EN-DC, the algorithms configured for SRBs using KeNB shall be the same
as for all SRBs using KeNB.
- Same Pre-test conditions as in clause 7.1.3.0 with the exception that ciphering algorithm ‘nea1 (SNOW3G)’ is
configured.
- For EN_DC or NGEN_DC, same Pre-test conditions as in clause 7.1.3.0 with the exception that ciphering
algorithms ‘eea1 (SNOW3G)’ and ‘nea1 (SNOW3G)’ are configured and without message condition UE TEST
LOOP MODE A, then RRCConnectionReconfiguration message including MobilityControlInfo IE is
transmitted on E-UTRA Cell 1 to reconfigure SRB1, SRB2 and MCG DRB from E-UTRA PDCP to NR PDCP
and Test Loop Function (On) with UE test loop mode A (message condition UE TEST LOOP MODE A to return
one UL PDCP SDU per DL PDCP SDU) according to TS 38.508-1 [4].
ETSI

U–S Message
- Exception steps 1a1 to 1b2 depends on UE - - - -
configuration.
1a1 IF Connectivity is EN-DC or NGEN-DC, <-- RRC:UECapabilityEnquiry - -
the SS sends EUTRA RRC
UECapabilityEnquiry including RAT-Type eutra
message to the UE.
1a2 Check: Does the UE send a EUTRA RRC --> RRC:UECapabilityInformation 1 P
1b1 ELSE the SS sends NR RRC <-- NR RRC:UECapabilityEnquiry - -
UECapabilityEnquiry message to the UE.
1b2 Check: Does the UE send a NR RRC --> NR RRC:UECapabilityInformation 1 P
- EXCEPTION: steps 2a1-2a2 depends on UE - - - -
configuration, executed if SCG DRB is
configured
2a1 IF Connectivity is EN-DC or NGEN-DC, SS <-- PDCP PDU - -
transmits PDCP PDU on SCG DRB ciphered.
2a2 Check: Does the UE transmit looped back --> PDCP PDU 2 P
PDCP PDU ciphered on SCG DRB?
3 SS transmits PDCP PDU on MCG DRB <-- PDCP PDU - -
ciphered.
4 Check: Does the UE transmit looped back --> PDCP PDU 2 P
PDCP PDU ciphered on MCG DRB?
ETSI
Table 7.1.3.3.1.3.3-1: RRCConnectionReconfiguration (Preamble for EN-DC or NGEN-DC)
Derivation Path: 36.508[47] Table 4.6.1-8

c1 CHOICE{
{
mobilityControlInfo MobilityControlInfo-HO- As per Table
SameCell 7.1.3.3.1.3.3-2
radioResourceConfigDedicated RadioResourceConfigDe As per Table
dicated-DRB-Rel-Add 7.1.3.3.1.3.3-3
setup SEQUENCE {
including the
RRCReconfiguration
message according to TS
38.508-1 [4], table 4.6.1-
13 with condition EN-
DC_HO.
}
}
sk-Counter-r15 Increment the value by 1
from the previous value
including
RadioBearerConfig
[4], table 4.6.3-132 with
condition EN-DC_DRB
including
RadioBearerConfig
[4], table 4.6.3-132 with
conditions
SRB_NR_PDCP and
MCG_NR_PDCP
}
}
}
}
}
}
}
}
}
}
}
}
ETSI
Table 7.1.3.3.1.3.3-2: MobilityControlInfo-HO-SameCell (Table 7.1.3.3.1.3.3-1)

MobilityControlInfo-HO ::= SEQUENCE {
UTRA Cell 1
carrierFreq Not present
}
Table 7.1.3.3.1.3.3-3: RadioResourceConfigDedicated-DRB-Rel-Add (Table 7.1.3.3.1.3.3-1)
Derivation Path: 36.508 [7], Table 4.6.3-19AAAAAD

RadioResourceConfigDedicated-SRB2-DRB ::=
SEQUENCE {
srb-ToAddModList Not present
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) 1 entry
OF DRB-ToAddMod {
drb-ToAddMod[1] DRB-ToAddMod- entry 1
DEFAULT (8) using See TS 36.508
condition AM except subclause 4.8.2
pdcp-Config not included
}
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) 1 entry
OF DRB-Identity {
DRB-Identity[1] 8 entry 1
Same as the DRB
Identity associated
with the default
EPS bearer
}
}
7.1.3.3.2 Ciphering and deciphering / Correct functionality of encryption algorithm AES /

SRB / DRB
(1)
ensure that {
when { Functionality of encryption algorithms with AES is taken into use on SRB }
}
}
(2)
ensure that {
when { Functionality of encryption algorithms with AES is taken into use on DRB }
then {UE performs correct ciphering/deciphering function in NR-PDCP entity associated with DRB }
}
Same conformance requirement as in clause 7.1.3.3.1.2.
ETSI
Same Pre-test conditions as in clause 7.1.3.3.1.3.1 with the exception that ciphering algorithm ‘nea2 (AES)’ and ‘eea2
(AES)’ is configured.
Same Test procedure sequence as in clause 7.1.3.3.1.3.2
None
7.1.3.3.3 Ciphering and deciphering / Correct functionality of encryption algorithm ZUC /

SRB / DRB
(1)
with { UE in RRC_CONNECTED state and SRB is configured with NR-PDCP}
ensure that {
when { Functionality of encryption algorithms with ZUC is taken into use on SRB }
}
}
(2)
with { UE in RRC_CONNECTED state and DRB is configured with NR-PDCP}
ensure that {
when { Functionality of encryption algorithms with ZUC is taken into use on DRB }
then { UE performs correct ciphering/deciphering function in NR-PDCP entity associated with DRB
}
}
Same conformance requirement as in clause 7.1.3.3.1.2.
Same Pre-test conditions as in clause 7.1.3.3.1.3.1 with the exception that ciphering algorithm ‘nea3 (ZUC)’ and ‘eea3
(ZUC)’ is configured.
Same Test procedure sequence as in clause 7.1.3.3.1.3.2.
None
ETSI
7.1.3.4 PDCP Handover
7.1.3.4.1 PDCP handover / Lossless handover / PDCP sequence number maintenance /

PDCP status report to convey the information on missing or acknowledged PDCP
SDUs at handover / In-order delivery and duplicate elimination in the downlink
(1)
with { UE in RRC_CONNECTED state with default RB using RLC-AM }
ensure that {
when { UE is requested to make a lossless handover by SS }
then { UE creates a PDCP status report to SS }
}
(2)
ensure that {
then { UE retransmits the unacknowledged data }
}
(3)
ensure that {
then { UE achieves in-order delivery and discards a PDCP PDU already received in the downlink }
}
5.2.2.1, 5.3, 5.4.1, 5.4.2 and 7.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.323, clause 5.1.2]
When upper layers request a PDCP entity re-establishment, the UE shall additionally perform once the procedures
described in this section. After performing the procedures in this section, the UE shall follow the procedures in
subclause 5.2.
When upper layers request a PDCP entity re-establishment, the transmitting PDCP entity shall:
- for UM DRBs and AM DRBs, reset the header compression protocol for uplink and start with an IR state in U-
mode (as defined in RFC 3095 [8] and RFC 4815 [9]) if drb-ContinueROHC is not configured in TS 38.331 [3];
- for UM DRBs and SRBs, set TX_NEXT to the initial value;
- for SRBs, discard all stored PDCP SDUs and PDCP PDUs;
- apply the ciphering algorithm and key provided by upper layers during the PDCP entity re-establishment
procedure;
- apply the integrity protection algorithm and key provided by upper layers during the PDCP entity re-
establishment procedure;
- for UM DRBs, 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 without restarting the discardTimer, as specified in subclause 5.2.1;
ETSI
- for AM DRBs, from the first PDCP SDU for which the successful delivery of the corresponding PDCP Data
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 entity re-establishment as specified below:
- perform integrity protection and ciphering of the PDCP SDU using the COUNT value associated with this
PDCP SDU as specified in the subclause 5.9 and 5.8;
- submit the resulting PDCP Data PDU to lower layer, as specified in subclause 5.2.1.
When upper layers request a PDCP entity re-establishment, the receiving PDCP entity shall:
- process 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;
- for SRBs and UM DRBs, if t-Reordering is running:
- stop and reset t-Reordering;
- for UM DRBs, deliver all stored PDCP SDUs to the upper layers in ascending order of associated COUNT
values after performing header decompression;
- for AM DRBs, perform header decompression for all stored PDCP SDUs if drb-ContinueROHC is not
configured in TS 38.331 [3];
- for UM DRBs and AM DRBs, reset the header compression protocol for downlink and start with NC state in U-
- for UM DRBs and SRBs, set RX_NEXT and RX_DELIV to the initial value;
procedure;
establishment procedure.
[TS 38.323, clause 5.2.2.1]
Variable;
Variable;
- RCVD_COUNT: the COUNT of the received PDCP Data PDU = [RCVD_HFN, RCVD_SN].
- else:
ETSI
shall:
entity shall:
RX_DELIV;
RX_DELIV < RX_NEXT:
[TS 38.323, clause 5.3]
When the discardTimer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP
status report, the transmitting PDCP entity shall discard the PDCP SDU along with the corresponding PDCP Data PDU.
If the corresponding PDCP Data PDU has already been submitted to lower layers, the discard is indicated to lower
layers.
For SRBs, when upper layers request a PDCP SDU discard, the PDCP entity shall discard all stored PDCP SDUs and
PDCP PDUs.
ETSI
NOTE: Discarding a PDCP SDU already associated with a PDCP SN causes a SN gap in the transmitted PDCP
Data PDUs, which increases PDCP reordering delay in the receiving PDCP entity. It is up to UE
implementation how to minimize SN gap after SDU discard.
[TS 38.323, clause 5.4.1]
For AM DRBs configured by upper layers to send a PDCP status report in the uplink (statusReportRequired in TS
38.331 [3]), the receiving PDCP entity shall trigger a PDCP status report when:
- upper layer requests a PDCP entity re-establishment;
- upper layer requests a PDCP data recovery.
If a PDCP status report is triggered, the receiving PDCP entity shall:
- compile a PDCP status report as indicated below by:
- setting the FMC field to RX_DELIV;
- if RX_DELIV < RX_NEXT:
- allocating a Bitmap field of length in bits equal to the number of COUNTs 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, or up to and including a PDCP SDU for which the resulting PDCP Control PDU size
is equal to 9000 bytes, whichever comes first;
- setting in the bitmap field as '0' for all PDCP SDUs that have not been received, and optionally PDCP
SDUs for which decompression have failed;
- setting in the bitmap field as '1' for all PDCP SDUs that have been received;
- submit the PDCP status report to lower layers as the first PDCP PDU for transmission via the transmitting PDCP
entity as specified in subclause 5.2.1..
[TS 38.323, clause 5.4.2]
For AM DRBs, when a PDCP status report is received in the downlink, the transmitting PDCP entity shall:
- consider for each PDCP SDU, if any, with the bit in the bitmap set to '1', or with the associated COUNT value
less than the value of FMC field as successfully delivered, and discard the PDCP SDU as specified in the
subclause 5.3.
[TS 38.323, clause 7.1]
This sub clause describes the state variables used in PDCP entities in order to specify the PDCP protocol. The state
All state variables are non-negative integers, and take values from 0 to [232 – 1].
PDCP Data PDUs are numbered integer sequence numbers (SN) cycling through the field: 0 to [2[pdcp-SN-Size] – 1].
The transmitting PDCP entity shall maintain the following state variables:
a) TX_NEXT
This state variable indicates the COUNT value of the next PDCP SDU to be transmitted. The initial value is 0.
The receiving PDCP entity shall maintain the following state variables:
a) RX_NEXT
This state variable indicates the COUNT value of the next PDCP SDU expected to be received. The initial value is 0.
b) RX_DELIV
This state variable indicates the COUNT value of the first PDCP SDU not delivered to the upper layers, but still waited
for. The initial value is 0.
ETSI
c) RX_REORD
This state variable indicates the COUNT value following the COUNT value associated with the PDCP Data PDU which
triggered t-Reordering.
- 2 NR cells (NR Cell 1 and NR Cell 2) are configured with DRBs in RLC AM mode.
- The cell power levels are configured as per the Table 7.1.3.4.1.3.1-1.
- DRB of NR Cell 1 is configured according to Table 7.1.3.4.1.3.1-3.
Table 7.1.3.4.1.3.1-1: Time instances of cell power level in FR1

Parameter Unit EUTRA NR Cell 1 NR Cell 2 Remark
Cell 1
T0 Cell-specific dBm/SCS -85 - -
RS EPRE
SS/PBCH - -88 Off
dBm/SCS
SSS EPRE
RS EPRE
SS/PBCH - -88 -82
dBm/SCS
SSS EPRE
T2 Cell-specific dBm/SCS -85 -
RS EPRE
SS/PBCH - -82 -88
dBm/SCS
SSS EPRE
Table 7.1.3.4.1.3.1-2: Time instances of cell power level in FR2

Parameter Unit EUTRA NR Cell 1 NR Cell 2 Remark
Cell 1
RS EPRE
SS/PBCH - -91 Off
dBm/SCS
SSS EPRE
RS EPRE
SS/PBCH - -91 -82
dBm/SCS
SSS EPRE
T2 Cell-specific dBm/SCS -96 -
RS EPRE
SS/PBCH - -82 -91
dBm/SCS
SSS EPRE
ETSI

U-S Message
1 The SS creates 5 PDCP Data PDUs and the - - - -
TX_NEXT 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 <-- PDCP PDU DATA #k - -
RLC-AM RB with the following content to the
UE:
D/C field = 1 (PDCP Data PDU) and PDCP SN
= k on NR Cell 1.
After having sent a PDU, the SS set TX_NEXT
= k+1.
3 The UE sends the PDCP Data PDU#k via --> PDCP PDU DATA #k - -
UE:
= k on NR Cell 1.
Data is previously received data from PDU #k.
(Note 1)
3A The SS changes NR Cell 2 parameters
1(FR1) / 7.1.3.4.1.3.1-2(FR2).
- EXCEPTION: Step 4 to 6 shall be repeated for - - - -
m=2 to 4 (increment=1).
4 The SS is configured on NR Cell 1 not to send - - - -
RLC acknowledgement (RLC ACK) to the next
received RLC SDU to the UE.
5 The SS sends the PDCP Data PDU #m via <-- PDCP PDU DATA #m - -
UE:
=m.
After having sent a PDU, the SS set TX_NEXT
= m+1. (Note 6)
6 The UE sends the PDCP Data PDU#m via --> PDCP PDU DATA #m - -
UE:
= m.
Data is previously received data from PDU #m.
(Note 2)
6A Configure SS not to allocate UL grant to the
UE in NR Cell 1
7 Void - - - -
message to perform SpCell change from NR
Cell1 to NR Cell2
(Note 3)
9 The SS assigns UL grant during the Random - - - -
Access procedure on NR Cell 2 to allow the
UE to send PDCP status report.(Note 5)
- EXCEPTION: Steps 10 and 11 can occur in - - - -
any order. (Note 7)
(Note 4)
11 Check: Does the UE send PDCP Control --> PDCP STATUS REPORT 1 P
PDUs via RLC-AM RB with the following
content to the SS:
D/C field = 0 (PDCP control PDU) and PDU
Type =000, FMC field = 5 on NR Cell 2?
ETSI
12 The SS generates a PDCP status report <-- PDCP STATUS REPORT - -

message and sends it to UE: D/C field = 0
(PDCP control PDU) and PDU Type =000,
FMC field = 2 on NR Cell 2.
13 Configure the SS to allocate Default UL grants - - - -
to the UE in NR Cell 2.
14 Void - - - -
- EXCEPTION: Step 15 shall be repeated for - - - -
m=2 to 4 (increment=1).
15 Check: Does the UE send the PDCP Data --> PDCP PDU DATA #m 2 P
PDU #m via RLC-AM RB with the following
content to the SS:
= m on NR Cell 2?
Note: Data is previously received data from
PDU #m.
(Note 8)
16 The SS sends the PDCP Data PDU#5 via <-- PDCP DATA PDU#5 - -
UE:
PDCP Data PDU #5 (
D/C field = 1 (PDCP Data PDU) and PDCP
SN=5) on NR Cell 2.
17 The UE transmits a PDCP Data PDU via RLC- --> PDCP DATA PDU #5 - -
AM RB with the following content back to the
SS:
SN=5 on NR Cell 2.
Note: Data is previously received packet in
PDCP Data PDU#5.
(Note 1)
18 TX_NEXT is set to "6". - - - -
The SS creates a PDCP Data PDU#6 (not
transmitted).
19 The TX_NEXT is set to "7". The SS creates a - - - -
PDCP Data PDU #7.
20 The SS sends PDCP Data PDU#7 via RLC- <-- PDCP DATA PDU #7 - -
AM RB with the following content to the UE:
PDCP Data PDU#7;
SN=7 on NR Cell 2.
21 Check: Does the UE transmit a PDCP DATA --> PDCP DATA PDU#7 3 F
PDU#7 on NR Cell 2?
21A Configure SS not to allocate UL grant to the - - - -
UE in NR Cell 1
22 The SS changes NR Cell 1 and NR Cell 2 - - - -
parameters according to row "T2" in Table
7.1.3.4.1.3.1-1(FR1) / 7.1.3.4.1.3.1-2(FR2).
23 The SS requests transmits NR <-- RRCReconfiguration - -
RRCReconfiguration message to perform
SpCell change from NR Cell2 to NR Cell1 with
key change.
(Note 3)
24 SS assigns UL grant during the Random - - - -
Access procedure on NR Cell 1 to allow the
UE to send PDCP status report.(Note 5)
any order. (Note 7)
(Note 4)
26 The UE sends PDCP Control PDUs via RLC- --> PDCP STATUS REPORT - -
AM RB with the following content to the SS:
D/C field = 0 (PDCP control PDU) and PDU
Type =000, FMC field = 6, Bitmap = 0x80 on
NR Cell 1.
ETSI
27 The SS generates a PDCP status report <-- PDCP STATUS REPORT - -

message and sends it to UE: D/C field = 0
(PDCP control PDU) and PDU Type =000,
FMC field = 6 on NR Cell 1.
28 Configure the SS to allocate Default UL grants - - - -
to the UE in NR Cell 1
28A The SS sends the PDCP Data PDU#5 via <-- PDCP DATA PDU#5 - -
UE:
PDCP Data PDU #5 (
SN=5) on NR Cell 1.
28B Check: Does the UE transmit a PDCP Data --> PDCP DATA PDU #5 3 F
PDU via RLC-AM RB with the following
content back to the SS:
SN=5 on NR Cell 1 within the next 5 seconds?
29 The SS sends the PDCP Data PDU#6 via <-- PDCP DATA PDU #6 - -
UE:
PDCP Data PDU#6 (
SN=6) on NR Cell 1.
30 Check: Does the UE transmit a PDCP Data --> PDCP DATA PDU #6 3 P
PDU via RLC-AM RB with the following
content back to the SS?
SN=6 on NR Cell 1.
PDCP Data PDU#6
(Note 9)
31 Check: Does the UE transmit PDCP Data PDU --> PDCP DATA PDU #7 3 P
via RLC-AM RB with the following content
back to the SS?
SN=7 on NR Cell 1.
PDCP Data PDU#7
(Note 9)
Note 1: The SS acknowledges the received data.
Note 2: SS doesn’t send the RLC ACK for this data.
Note 3: For EN-DC the NR RRCReconfiguration (Table 7.1.3.4.1.3.3-1 with cond EN-DC) and RadioBearerConfig
message (Table 7.1.3.4.1.3.3-2) are contained in RRCConnectionReconfiguration 36.508 [7], Table 4.6.1-8
using conditions EN-DC_EmbedNR_RRCRecon, EN-DC_PSCell_HO and RBConfig_KeyChange. IE sk-
Counter-r15 is included with a value incremented by 1 than previous value.
Note 5: The PDCP STATUS REPORT PDU size shall be 6 octets with 3 octets of RLC header, 2 octets of MAC
header and 3 octets of MAC BSR or padding, so TBS of 112 bits shall be allocated.
Note 6: PDCP PDU with m = 2 is sent at t = 0 and the subsequent PDCP PDUs are sent at t = (m-2)*75.
Note 7: Per 38.508-1 Table 4.6.3-66: LogicalChannelConfig, both SRB1 and DRB have the same logical channel
priority with prioritisedBitRate as infinity.
Note 8 PDCP PDUs at step 15 (m=2 to 4) may be received by the SS in the same slot or in multiple slots (max one
MAC PDU in a slot).
Note 9 PDCP PDUs at steps 30 and 31 may be received by the SS in the same slot or in multiple slots (max one
MAC PDU in a slot).
Derivation Path: 38.508-1 [4], Table: 4.6.3-155

sr-TransMax n64
ETSI
Table 7.1.3.4.1.3.3-1: RRCReconfiguration (steps 8, 23)

}
masterKeyUpdate ::= SEQUENCE {
keySetChangeIndicator false
nextHopChainingCount 0
nas-Container Not present Horizontal key
derivation
}
}
}
}
Table 7.1.3.4.1.3.3-2: RadioBearerConfig (Table 7.1.3.4.1.3.3-1)

OF DRB-ToAddMod {
drb-Identity 2 SCG DRB Id EN-DC
Default DRB of the first NR
PDU session
reestablishPDCP True
pdcp-Config PDCP-Config
}
}
}
Table 7.1.3.4.1.3.3-3: PDCP-Config (Table 7.1.3.4.1.3.3-2)

drb SEQUENCE {
statusReportRequired True
}
}
ETSI
Table 7.1.3.4.1.3.3-4: CellGroupConfig for EN-DC (Table 7.1.3.4.1.3.3-1)
Derivation Path: 38.508-1 [4], Table: 4.6.3-19 with condition PSCell_change

on
}
}
}
Table 7.1.3.4.1.3.3-4A: CellGroupConfig for NR/5GC (Table 7.1.3.4.1.3.3-1)
Derivation Path: 38.508-1 [4], Table: 4.6.3-19 with condition PCell_change
Table 7.1.3.4.1.3.3-5: Void
Table 7.1.3.4.1.3.3-6: Void
7.1.3.4.2 PDCP handover / Non-lossless handover / PDCP sequence number

maintenance
(1)
with { UE in RRC_CONNECTED state with default RB 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 }
}
(2)
with { UE in RRC_CONNECTED state with default RB using RLC-UM }
ensure that {
when { UE is requested to make a non-lossless handover by SS }
then { UE is able to receive next PDCP Data PDU with SN value 0 }
}
[TS 38.323, clause 5.1.2]
When upper layers request a PDCP entity re-establishment, the UE shall additionally perform once the procedures
described in this section. After performing the procedures in this section, the UE shall follow the procedures in
subclause 5.2.
When upper layers request a PDCP entity re-establishment, the transmitting PDCP entity shall:
- for UM DRBs and AM DRBs, reset the header compression protocol for uplink and start with an IR state in U-
- for UM DRBs and SRBs, set TX_NEXT to the initial value;
ETSI
procedure;
establishment procedure;
- for UM DRBs, 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 without restarting the discardTimer.
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 entity re-establishment as specified below:
PDCP SDU as specified in the subclause 5.9 and 5.8;
- submit the resulting PDCP Data PDU to lower layer.
When upper layers request a PDCP entity re-establishment, the receiving PDCP entity shall:
- process 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;
- for UM DRBs, if t-Reordering is running:
- stop and reset t-Reordering;
- deliver all stored PDCP SDUs to the upper layers in ascending order of associated COUNT values after
performing header decompression.
- for AM DRBs, perform header decompression for all stored PDCP SDUs if drb-ContinueROHC is not
configured in TS 38.331 [3];
- for UM DRBs and AM DRBs, reset the header compression protocol for downlink and start with NC state in U-
- for UM DRBs and SRBs, set RX_NEXT and RX_DELIV to the initial value;
procedure;
establishment procedure.
Same Pre-test conditions as in clause 7.1.3.0 except that the DRB under test is configured in RLC UM mode. For EN-
DC, ciphering algorithm is configured as null on E-UTRA.
ETSI

U-S Message
TX_NEXT 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 <-- PDCP PDU DATA #k - -
RLC-UM RB with the following content to the
UE:
= k.
After having sent a PDU, the SS set
TX_NEXT= k+1.
3 The UE sends the PDCP Data PDU #k via --> PDCP PDU DATA #k - -
SS:
= k.
message to trigger non-lossless handover to
the same SpCell . (Note 1, Note 3 and Note4)
2)
6 The SS sends the PDCP Data PDU #2 via <-- PDCP PDU DATA #2 - -
UE:
= 0.
After having sent a PDU, the SS set
TX_NEXT= 1.
7 Check: Does the UE send the PDCP Data --> PDCP PDU DATA #2 1, 2 P
PDU #2 via RLC-UM RB with the following
content back to the SS:
= 0?
Note 1: For EN-DC the NR RRCReconfiguration message with SCG Key change (secondary to master)is
contained in RRCConnectionReconfiguration 36.508 [7], Table 4.6.1-8 using condition EN-DC_PSCell_HO
and RBConfig_KeyChange.
Note 3: The RRCReconfiguration message triggers UE to perform the Random Access procedure, MAC reset,
RLC and PDCP re-establishment.
Note 4: For NR, the RRCReconfiguration message with master key change is as per RRCReconfiguration-HO with
condition RBConfig_KeyChange according to 38.508-1 [4], Table 4.8.1-1A.
Table 7.1.3.4.2.3-1: RRCReconfiguration for EN-DC (step 4, Table 7.1.3.4.2.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition EN-DC_HO.
ETSI
Table 7.1.3.4.2.3-1A: RRCReconfiguration for NR/5GC (step 4, Table 7.1.3.4.2.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with condition RBConfig_KeyChange

RRCReconfiguration::= SEQUENCE {
(CONTAINING
CellGroupConfig)
masterKeyUpdate SEQUENCE {
keySetChangeIndicator false K
nextHopChainingCount 0 Horizontal key
derivation
nas-Container not present
}
Table 7.1.3.4.2.3-2: RadioBearerConfig for EN-DC (step 4, Table 7.1.3.4.2.3.2-1)
Derivation Path: 38.508-1 [4], Table 4.6.3-132 with condition EN-DC_DRB AND Re-establish_PDCP
securityConfig SEQUENCE {
securityAlgorithmConfig SecurityAlgorithmConfig
keyToUse master
}
}
Table 7.1.3.4.2.3-3: SecurityAlgorithmConfig for EN-DC (Table 7.1.3.4.2.3-2)

SecurityAlgorithmConfig ::= SEQUENCE {
cipheringAlgorithm nea0
}
Table 7.1.3.4.2.3-4: CellGroupConfig for EN-DC (step 4, Table 7.1.3.4.2.3.2-1)
Derivation Path: 38.508-1 [4], Table 4.6.3-19 with condition PSCell_change

rlc-BearerToAddModList SEQUENCE 1 entry EN-DC
RLC-Bearer-Config[1] RLC-BearerConfig with entry 1
conditions UM and DRB2
and Re-establish_RLC
}
}
Table 7.1.3.4.2.3-5: CellGroupConfig for NR/5GC (step 4, Table 7.1.3.4.2.3.2-1)
Derivation Path: 38.508-1 [4], Table 4.6.3-19 with condition PCell_change
ETSI
7.1.3.4.3 PDCP handover / DAPS handover / Status reporting / Intra-frequency
(1)
with { UE in NR RRC_CONNECTED state and supporting Intra-frequency DAPS handover }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for Intra-
frequency DAPS handover }
then { PDCP entity associated with a DAPS bearer shall keep DL/UL reception/transmission with
the source gNB }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting Intra-frequency DAPS handover and receiving an
RRCReconfiguration message including a reconfigurationWithSync for Intra-frequency DAPS handover
with key change }
ensure that {
when { UE has performed random access procedure to the target cell successfully }
then { UE shall perform uplink data switching }
}
(3)
with key change }
ensure that {
when { upper layer requests a uplink data switching }
then { UE shall send a PDCP status report for the DAPS bearer }
}
(4)
with key change }
ensure that {
when { upper layer requests a PDCP entity reconfiguration and the associated RLC entity is
released for a radio bearer }
then { UE shall send a PDCP status report for the DAPS bearer }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.331 clause 5.3.5.5.2 and
TS 38323 clause 4.2.2, 5.4.1, 5.8, 5.9 and 5.13. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.3.5.5.2]
1> If any DAPS bearer is configured:
2> create a MAC entity for the target cell group with the same configuration as the MAC entity for the source
cell group;
2> for each DAPS bearer:
3> establish an RLC entity or entities for the target cell group, with the same configurations as for the source
cell group;
ETSI
3> establish the logical channel for the target cell group, with the same configurations as for the source cell
group;
NOTE 2b: In order to understand if a DAPS bearer is configured, the UE needs to check the presence of the field
daps-Config within the RadioBearerConfig IE received in radioBearerConfig or radioBearerConfig2.
2> for each SRB:
3> establish an RLC entity for the target cell group, with the same configurations as for the source cell
group;
group;
3> suspend SRBs for the source cell group;
NOTE 3: Void
2> apply the value of the newUE-Identity as the C-RNTI in the target cell group;
2> configure lower layers for the target SpCell in accordance with the received spCellConfigCommon;
2> configure lower layers for the target SpCell in accordance with any additional fields, not covered in the
previous, if included in the received reconfigurationWithSync.
[TS 38.323, clause 4.2.2]
The PDCP entities are located in the PDCP sublayer. Several PDCP entities may be defined for a UE. Each PDCP
entity is carrying the data of one radio bearer. A PDCP entity is associated either to the control plane or the user plane
depending on which radio bearer it is carrying data for.
Figure 4.2.2.1 represents the functional view of the PDCP entity for the PDCP sublayer; it should not restrict
implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2].
For split bearers and DAPS bearers, routing is performed in the transmitting PDCP entity.
A PDCP entity associated with DRB can be configured by upper layers TS 38.331 [3] to use header compression. In
this version of the specification, the robust header compression protocol (ROHC) and the Ethernet header compression
protocol (EHC) are supported. Each header compression protocol is independently configured for a DRB.
ETSI
Figure 4.2.2-1: PDCP layer, functional view
Figure 4.2.2-2 represents the functional view of the PDCP entity associated with the DAPS bearer for the PDCP
sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined
in TS 38.300 [2].
For DAPS bearers, the PDCP entity is configured with two sets of security functions and keys and two sets of header
compression protocols.
ETSI
UE UE
Transmitting PDCP entity Receiving PDCP entity
Transmission buffer: Sequence numbering

Header Decompression Header Decompression
Header Compression Header Compression

Packets associated Packets associated
Packets associated Packets associated to a PDCP SDU to a PDCP SDU
to a PDCP SDU to a PDCP SDU
associated to a
associated to a
associated to a
Packets not
Packets not
PDCP SDU
PDCP SDU
associated to a
Packets not
PDCP SDU
Packets not
PDCP SDU
Reception buffer:
Integrity Protection Integrity Protection
Reordering, duplicte discarding
Ciphering Ciphering Integrity Verification Integrity Verification
Add PDCP header Deciphering Deciphering
Routing Remove PDCP Header
Radio Interface (Uu)
Figure 4.2.2-2: PDCP layer associated with DAPS bearer, functional view
[TS 38.323, clause 5.4.1]
- upper layer requests a PDCP data recovery;
- upper layer requests a uplink data switching;
- upper layer reconfigures the PDCP entity to release DAPS and daps-SourceRelease is configured in TS 38.331
[3].
For UM DRBs configured by upper layers to send a PDCP status report in the uplink (statusReportRequired in TS
- upper layer requests a uplink data switching.
[TS 38.323, clause 5.8]
The ciphering function includes both ciphering and deciphering and is performed in PDCP, if configured. The data unit
that is ciphered is the MAC-I (see clause 6.3.4) and the data part of the PDCP Data PDU (see clause 6.3.3) except the
SDAP header and the SDAP Control PDU if included in the PDCP SDU. The ciphering is not applicable to PDCP
Control PDUs.
For downlink and uplink, the ciphering algorithm and key to be used by the PDCP entity are configured by upper layers
TS 38.331 [3] and the ciphering method shall be applied as specified in TS 33.501 [6].
The ciphering function is activated/suspended/resumed by upper layers TS 38.331 [3]. When security is activated and
not suspended, the ciphering function shall be applied to all PDCP Data PDUs indicated by upper layers TS 38.331 [3]
for the downlink and the uplink, respectively.
For DAPS bearers, the PDCP entity shall perform the ciphering or deciphering for the PDCP SDU using the ciphering
algorithm and key either configured for the source cell or configured for the target cell, based on to/from which cell the
PDCP SDU is transmitted/received.
For downlink and uplink ciphering and deciphering, the parameters that are required by PDCP for ciphering are defined
in TS 33.501 [6] and are input to the ciphering algorithm. The required inputs to the ciphering function include the
ETSI
COUNT value, and DIRECTION (direction of the transmission: set as specified in TS 33.501 [6]). The parameters
required by PDCP which are provided by upper layers TS 38.331 [3] are listed below:
38.331 [3]);
- KEY (the ciphering keys for the control plane and for the user plane are KRRCenc and KUPenc, respectively).
[TS 38.323, clause 5.9]
The integrity protection function includes both integrity protection and integrity verification and is performed in PDCP,
if configured. The data unit that is integrity protected is the PDU header and the data part of the PDU before ciphering.
The integrity protection is always applied to PDCP Data PDUs of SRBs. The integrity protection is applied to sidelink
SRB1, SRB2 and SRB3. The integrity protection is applied to PDCP Data PDUs of DRBs (including sidelink DRBs for
unicast) for which integrity protection is configured. The integrity protection is not applicable to PDCP Control PDUs.
For downlink and uplink, the integrity protection algorithm and key to be used by the PDCP entity are configured by
upper layers TS 38.331 [3] and the integrity protection method shall be applied as specified in TS 33.501 [6].
The integrity protection function is activated/suspended/resumed by upper layers TS 38.331 [3]. When security is
activated and not suspended, the integrity protection function shall be applied to all PDUs including and subsequent to
the PDU indicated by upper layers TS 38.331 [3] for the downlink and the uplink, respectively.
NOTE 1: 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.
NOTE 2: As the PC5-S message which activates the integrity protection function is itself integrity protected with
the configuration included in this PC5-S message, this message needs first be decoded by upper layer
before the integrity protection verification could be performed for the PDU in which the message was
received.
For DAPS bearers, the PDCP entity shall perform the integrity protection or verification for the PDCP SDU using the
integrity protection algorithm and key either configured for the source cell or configured for the target cell, based on
to/from which cell the PDCP SDU is transmitted/received.
For downlink and uplink integrity protection and verification, the parameters that are required by PDCP for integrity
protection are defined in TS 33.501 [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
specified in TS 33.501 [6]). The parameters required by PDCP which are provided by upper layers TS 38.331 [3] are
listed below:
38.331 [3]);
- KEY (the integrity protection keys for the control plane and for the user plane are KRRCint and KUPint,
respectively).
[TS 38.323, clause 5.13]
For DAPS bearers, when upper layers request uplink data switching, the transmitting PDCP entity shall:
PDU has not been confirmed by the RLC entity associated with the source cell, 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 uplink data switching to the RLC entity associated with the target cell as
specified below:
- perform header compression of the PDCP SDU using ROHC as specified in the clause 5.7.4;
PDCP SDU as specified in the clause 5.9 and 5.8;
- submit the resulting PDCP Data PDU to lower layer, as specified in clause 5.2.1.
ETSI
- for UM DRBs, for all PDCP SDUs which have been processed by PDCP but which have not yet been submitted
to lower layers, perform transmission of the PDCP SDUs in ascending order of the COUNT values to the RLC
entity associated with the target cell as specified below:
- perform header compression of the PDCP SDU using ROHC as specified in the clause 5.7.4;
PDCP SDU as specified in the clause 5.9 and 5.8;
- submit the resulting PDCP Data PDU to lower layer, as specified in clause 5.2.1.
System Simulator:
- NR Cell 1 is the Serving cell and the power level is configured to ''Serving Cell” defined in TS 38.508-1 [4]
Table 6.2.2.1-3.
- NR Cell 2 is the Suitable neighbour intra-frequency cell and the power level is configured to '' Suitable
neighbour intra-frequency cell” defined in TS 38.508-1 [4] Table 6.2.2.1-3.
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for both NR Cells.
- Test Loop Function (On) with UE test loop mode B activated according to TS 38.508-1 [4], table 4.5.4.2-3.
UE:
- None.
Preamble:
- The UE is in 3N-A state configured with DRB#1 in RLC AM mode according to TS 38.508-1 [4], Table 4.4A.2-
3.
ETSI

U-S Message
1 The SS transmits an RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
message containing reconfigurationWithSync
to order UE to perform DAPS handover to NR
Cell 2. DRB#n of the first PDU session is
configured as DAPS bearer.
- EXCEPTION: In parallel with step 2-3, parallel - - - -
executed repeatedly.
2 The SS sends one IP Packet to the UE via <-- PDCP PDU DATA #0 - -
DRB#n of the first PDU session in NR Cell 1
and
2A The SS stops sending RLC - - - -
acknowledgements.
3 Check: Does the UE loop back the IP packet --> PDCP PDU DATA #0 1 P
received at step 2 in NR Cell 1?
4 The SS transmits Random Access Response <- Random Access Response - -
to respond to the latest preamble in NR Cell 2.
- EXCEPTION: Steps 5-7 can occur in any - - - -
order.
5 The UE transmits an --> NR RRC: - -
RRCReconfigurationComplete message in NR RRCReconfigurationComplete
Cell 2.
6 Check: Does the UE retransmit the IP packet --> PDCP PDU DATA #0 2 P
received at step 2 in NR Cell 2?
7 Check: Does the UE send PDCP status report --> PDCP STATUS REPORT 3 P
in NR Cell 2? (Note 1)
message with condition
DAPS_HO_ReleaseSource in NR Cell 2.
- EXCEPTION: Steps 9-10 can occur in any - - - -
order.
Cell 2.
10 Check: Does the UE send PDCP status report --> PDCP STATUS REPORT 4 P
in NR Cell 2? (Note 1)
Note 1: D/C field = 0 (PDCP control PDU) and PDU Type =000 (PDCP status report), FMC field = 1.

U-S Message
1 The UE transmits preamble to NR Cell 2. -> (PRACH Preamble) - -
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with Condition RBConfig_NoKeyChange

radioBearerConfig RadioBearerConfig with
conditions
(SRB_NR_PDCP and
Re-establish_PDCP) and
DRB1 AND DAPS_PDCP
nonCriticalExtension SEQUENCE{
(CONTAINING
CellGroupConfig)
}
}
}
}

rlc-BearerToAddModList SEQUENCE 3 entries
RLC-BearerConfig[1] RLC-BearerConfig with entry 1
conditions SRB1 and Re-
establish_RLC
establish_RLC
RLC-BearerConfig[3] RLC-BearerConfig with entry3
conditions AM, DRB2 except
drb-Identity of
servedRadioBearer shall set
to DRB-Identity with
condition DRB1
}
spCellConfigCommon SEQUENCE {
physCellId Physical Cell Identity of NR
Cell 2
}
uplink RACH-ConfigDedicated OCTET
STRING
(CONTAINING
RACH-
ConfigDedicate
d)
}
}
}
}
ETSI
Table 7.1.3.4.3.3.3-3: RACH-ConfigDedicated (Table 7.1.3.4.3.3.3-2)

RACH-ConfigDedicated ::= SEQUENCE {
cfra SEQUENCE {
rach-ConfigGeneric RACH-ConfigGeneric OCTET
STRING
(CONTAINING
RACH-
ConfigGeneric)
}
}
}

}
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with Condition DAPS_HO_ReleaseSource
7.1.3.5 PDCP other
7.1.3.5.1 PDCP Discard
(1)
ensure that {
when { the Discard Timer for a PDCP SDU expires }
then { UE discards the corresponding PDCP SDU }
}
[TS 38.323, clause 5.3]
When the discardTimer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP
status report, the transmitting PDCP entity shall discard the PDCP SDU along with the corresponding PDCP Data PDU.
If the corresponding PDCP Data PDU has already been submitted to lower layers, the discard is indicated to lower
layers.
For SRBs, when upper layers request a PDCP SDU discard, the PDCP entity shall discard all stored PDCP SDUs and
PDCP PDUs.
NOTE: Discarding a PDCP SDU already associated with a PDCP SN causes a SN gap in the transmitted PDCP
Data PDUs, which increases PDCP reordering delay in the receiving PDCP entity. It is up to UE
implementation how to minimize SN gap after SDU discard.
ETSI
[TS 38.323, clause 7.1]
This sub clause describes the state variables used in PDCP entities in order to specify the PDCP protocol. The state
All state variables are non-negative integers, and take values from 0 to [232 – 1].
PDCP Data PDUs are numbered integer sequence numbers (SN) cycling through the field: 0 to [2[pdcp-SN-Size] – 1].
The transmitting PDCP entity shall maintain the following state variables:
a) TX_NEXT
This state variable indicates the COUNT value of the next PDCP SDU to be transmitted. The initial value is 0.
The receiving PDCP entity shall maintain the following state variables:
a) RX_NEXT
This state variable indicates the COUNT value of the next PDCP SDU expected to be received. The initial value is 0.
b) RX_DELIV
This state variable indicates the COUNT value of the first PDCP SDU not delivered to the upper layers, but still waited
for. The initial value is 0.
c) RX_REORD
This state variable indicates the COUNT value following the COUNT value associated with the PDCP Data PDU which
triggered t-Reordering.
[TS 38.323, clause 6.3.5]
Length: 32 bits
The COUNT value is composed of a HFN and the PDCP SN. The size of the HFN part in bits is equal to 32 minus the
length of the PDCP SN.
Figure 6.3.5-1: Format of COUNT
NOTE: COUNT does not wrap around.
Same Pre-test conditions as in clause 7.1.3.0 with exceptions listed in Table 7.1.3.5.1.3.1-1 applicable for the
configured UM DRB and Table 7.1.3.5.1.3.3-1 for SR configuration except that PDCP is configured for 18 bit SN.
Parameter Value
Discard_Timer 500 ms
ETSI

U-S Message
- EXCEPTION: The SS does not allocate UL grants - - - -
unless when explicitly stated so in the procedure.
1 The SS creates 5 PDCP Data PDUs and the PDCP - - -
SN = "0" within TX_NEXT.
2 Void
- EXCEPTION: Step 3 shall be repeated for k=0 to 2 - - - -
(increment=1) with the below specified PDU size
sent to the UE:
Data PDU#1 = 46 bytes for k=0
3 The SS sends a PDCP Data PDU via RLC-UM RB <-- PDCP DATA PDU (SN=k) - -
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 PDCP SN is
set to k+1 within TX_NEXT.
4 Wait for Discard_Timer to expire. - - - -
Note: According to TS38.508-1, timer tolerance
should be 10% of Discard_Timer.
(increment=1) with the below specified PDU size
sent to the UE:
5 The SS sends a PDCP Data PDU via RLC-UM RB <-- PDCP DATA PDU (SN=k) - -
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 PDCP SN is
set to k+1 within TX_NEXT.
6 The SS resumes normal UL grant allocation. - - - -
7 Check: Does UE transmit a PDCP Data PDU # 4 of --> PDCP Data PDU # 4 1 P
size 94 bytes? (Note1) (Note 2)
8 Check: Does UE transmit a PDCP Data PDU # 5 of --> PDCP Data PDU # 5 1 P
size 110 bytes? (Note1) (Note 2)
Note 1 PDCP Data PDU contents are checked to verify that the UL PDU is same as the DL PDU. According to the
Note in TS 38.323 [19] clause 5.3 in case of PDCP SDUs being discarded it is up to the UE implementation
which SN to be used and therefore the SN cannot be checked.
Note 2 PDCP PDUs at steps 7 and 8 may be received by the SS in the same slot or in multiple slots (max one
MAC PDU in a slot).

sr-TransMax n64
7.1.3.5.2 PDCP Uplink Routing / Split DRB
7.1.3.5.2.1 Test Purpose
(1)
with { UE in RRC_CONNECTED state with SCG activated with a Split DRB established and total amount of
PDCP data volume is less than ul-DataSplitThreshold and not yet transmitted RLC data volume in the
two associated RLC entities }
ETSI
ensure that {
when { UE has PDCP SDUs available for transmission }
then { the UE transmits the PDCP SDUs on the Primary RLC entity }
}
(2)
with { UE in RRC_CONNECTED state with SCG activated with a Split DRB established and total amount of
PDCP data volume is not less than ul-DataSplitThreshold and not yet transmitted RLC data volume in
the two associated RLC entities }
ensure that {
then { the UE transmits the PDCP SDUs on the primary or secondary RLC entity }
}
[TS 38.323, clause 5.2.1]
implementation.
respectively;
When submitting a PDCP Data PDU to lower layer, the transmitting PDCP entity shall:
- submit the PDCP Data PDU to the associated RLC entity.
- if the PDCP duplication is activated:
- if the PDCP PDU is a PDCP Data PDU:
- duplicate the PDCP Data PDU and submit the PDCP Data PDU to both associated RLC entities.
- else:
- if the two associated RLC entities belong to the different Cell Groups; and
specified in TS 36.322 [5]) in the two associated RLC entities is equal to or larger than ul-
DataSplitThreshold:
- submit the PDCP Data PDU to either the primary RLC entity or the secondary RLC entity;.
ETSI
- else:
Same Pre-test conditions as in clause 7.1.3.0 with exceptions listed in Table 7.1.3.5.2.3.1-1 and Generic procedure
parameter DC bearer(MCG and split).
For NR 5GC, NRCell 1 is the PCell and NR Cell 10 is the PSCell and same Pre-test conditions as in clause 7.1.3.0
using generic procedure parameter Connectivity (NR-DC) with DC bearer(MCG and split).
Parameter Value
Discard_Timer 500 ms
ul-DataSplitThreshold b100
ETSI

U-S Message
1 The SS sends a PDCP Data PDU on the split DRB <-- PDCP DATA PDU - -
on AM RLC entity configured for SCG on PSCell.
Data PDU = 64 bytes.
- EXCEPTION: In parallel with step 2, UE may - - - -
execute parallel behaviour defined in table
7.1.3.5.2.3.2-2.
2 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 1 P
the AM RLC entity configured for SCG on PSCell?
Data PDU = 164 bytes.
- EXCEPTION: Steps 4a1 to 4b2 describe optional - - - -
behaviour that depends on the UE uplink path
4a1 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 P
the AM RLC entity configured for MCG on PCell?
4a2 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 F
4b1 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 P
4b2 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 F
the AM RLC entity configured for MCG PCell?
5 SS transmits NR RRCReconfiguration message to <-- RRCReconfiguration - -
configure new split DRB parameters, where the ul-
DataSplitThreshold is equal to 0 bytes (Note 1).
6 UE transmits RRCReconfigurationComplete (Note --> RRCReconfigurationComple - -
2). te
7 The SS sends a PDCP Data PDU on the split DRB <-- PDCP Data PDU - -
Data PDU = 64 bytes
- EXCEPTION: Steps 8a1 to 8b2 describe optional - - - -
behaviour that depends on the UE uplink path
8a1 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 P
the AM RLC entity configured for MCG on PCell?
8a2 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 F
8b1 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 P
8b2 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 F
the AM RLC entity configured for MCG PCell?

U-S Message
1 Check: Does UE transmit a PDCP Data PDU --> PDCP DATA PDU 1 F
on the AM RLC entity configured for MCG on
PCell in next two seconds?
NOTE: Two seconds sufficient time to discard
PDCP PDU.
ETSI
Table 7.1.3.5.2.3.3-0A: RRCConnectionReconfiguration (step 5, Table 7.1.3.5.3.3.2-1)

c1 CHOICE{
{
including
RadioBearerConfig
}
}
}
}
}
}
}
}
}
}
}
}
Table 7.1.3.5.2.3.3-0B: RRCReconfiguration (step 5, Table 7.1.3.5.2.3.2-1)

radioBearerConfig2 OCTET STRING
including
RadioBearerConfig
}
}
}
}
}
}
ETSI
Table 7.1.3.5.2.3.3-1: RadioBearerConfig ( Table 7.1.3.5.2.3.3-0A and Table 7.1.3.5.2.3.3-0B)

OF DRB-ToAddMod {
pdcp-Config SEQUENCE {
moreThanOneRLC SEQUENCE {
primaryPath SEQUENCE {
cellGroup 1 EN-DC
0 NR
logicalChannel LogicalChannelIdentity
}
ul-DataSplitThreshold b0
}
}
}
}
}
7.1.3.5.3 PDCP Data Recovery
(1)
with { UE in RRC_CONNECTED state with a DRB established using RLC-AM }
ensure that {
when { network requests reconfiguration and recovery of the DRB (without handover) }
then { UE reconfigures the DRB and performs retransmission of all the PDCP PDUs previously
submitted to re-established AM RLC entity in ascending order of the associated COUNT values from the
first PDCP PDU for which the successful delivery has not been confirmed by lower layers }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.323, clauses 5.2.1, 5.4.1
and 5.5; TS 38.331, clause 5.3.5.4.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.323, clause 5.2.1]
implementation.
respectively;
ETSI
When submitting a PDCP PDU to lower layer, the transmitting PDCP entity shall:
- submit the PDCP PDU to the associated RLC entity;
- if pdcp-Duplication is configured and activated:
- duplicate the PDCP Data PDU and submit the PDCP Data PDU to both associated RLC entities;
- else, if pdcp-Duplication is configured but not activated:
- submit the PDCP Data PDU to the primary RLC entity;
- else:
specified in TS 38.322 [5]) in the two associated RLC entities is less than ul-DataSplitThreshold:
- submit the PDCP PDU to the primary RLC entity;
- else:
- submit the PDCP PDU to either the primary RLC entity or the secondary RLC entity.
[TS 38.323, clause 5.4.1]
- upper layer requests a PDCP data recovery.
If a PDCP status report is triggered, the receiving PDCP entity shall:
- compile a PDCP status report as indicated below by:
- setting the FMC field to RX_DELIV;
- allocating a Bitmap field of length in bits equal to the number of COUNTs 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, or up to and including a PDCP SDU for which the resulting PDCP Control PDU size
is equal to 9000 bytes, whichever comes first;
- setting in the bitmap field as '0' for all PDCP SDUs that have not been received, and optionally PDCP
SDUs for which decompression have failed;
- setting in the bitmap field as '1' for all PDCP SDUs that have been received;
- submit the PDCP status report to lower layers as the first PDCP PDU for transmission.
[TS 38.323, clause 5.4.2]
For AM DRBs, when a PDCP status report is received in the downlink, the transmitting PDCP entity shall:
ETSI
- consider for each PDCP SDU, if any, with the bit in the bitmap set to '1', or with the associated COUNT value
less than the value of FMC field as successfully delivered, and discard the PDCP SDU as specified in the
subclause 5.3.
[TS 38.323, clause 5.5]
For AM DRBs, when upper layers request a PDCP data recovery for a radio bearer, the transmitting PDCP entity shall:
- perform retransmission of all the PDCP Data PDUs previously submitted to re-established or released AM RLC
entity in ascending order of the associated COUNT values for which the successful delivery has not been
confirmed by lower layers.
After performing the above procedures, the transmitting PDCP entity shall follow the procedures in subclause 5.2.1.
Same Pre-test conditions as in clause 7.1.3.0 except that DRB is configured in RLC AM mode according to Table
7.1.3.5.3.3.1-1.
For NR 5GC, NRCell 1 is the PCell and NR Cell 10 is the PSCell and same Pre-test conditions as in clause 7.1.3.0
using generic procedure parameter Connectivity (NR-DC).
ETSI

U-S Message
1 Void - - - -
Next_PDCP_TX_SN is set to "0".
- EXCEPTION: Steps 2A and 4 shall be repeated for - - - -
k=0 to 2 (increment=1).
2A The SS is configured on PSCell to not send RLC - - - -
acknowledgement (RLC ACK) to the UE
3 The SS sends the PDCP Data PDU #k on SCG <-- PDCP PDU DATA #k - -
DRB on (PSCell):
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.
4 The UE sends the PDCP Data PDU #k on the AM --> PDCP PDU DATA #k - -
RLC entity configured for PSCell:
Data is previously received data from PDU #k.
4A The SS does not allocate any UL grant. - - - -
5 The SS transmits a NR RRCReconfiguration. (Note <-- RRCReconfiguration - -
1).
6 The UE transmits a NR --> RRCReconfigurationComple - -
RRCReconfigurationComplete. te
(Note 2).
7 The SS assigns 1 UL grant of sufficient size to - - - -
allow the UE to send only PDCP status report.
8 The UE sends PDCP Control PDUs on PSCell via --> PDCP STATUS REPORT - -
RLC-AM RB with the following content to the SS:
D/C field = 0 (PDCP control PDU) and PDU Type
=000, FMC field = 3.
8A After 100 ms the SS allocates 3 UL grants every - - - -
20ms of sufficient size to enable the UE to return
each received PDCP PDU in one looped back
PDCP PDU on PSCell.
(increment=1).
9 Check: Does the UE send the PDCP Data PDU #k --> PDCP DATA PDU #k 1 P
via the AM RLC entity configured for PSCell for
Connectivity ENDC and PCell for Connectivity (NR-
DC).
Data is previously received data from PDU #k ?
ETSI
Table 7.1.3.5.3.3.3-1: RRCConnectionReconfiguration (step 5, Table 7.1.3.5.3.3.2-1)
Derivation Path: 36.508 [7], Table 4.6.1-8 with condition MCG_and_SCG

c1 CHOICE{
{
setup SEQUENCE {
including the
RRCReconfiguration-
PDCP message and the
IE secondaryCellGroup
}
}
including
RadioBearerConfig-
PDCP-ENDC
}
}
}
}
}
}
}
}
}
}
}
}
ETSI
Table 7.1.3.5.3.3.3-2: RRCReconfiguration-PDCP (Step 5, Table 7.1.3.5.3.3.3-1)

radioBearerConfig Not present NR-DC
secondaryCellGroup CellGroupConfig-PDCP- EN-DC
ENDC
Not present NR-DC
nonCriticalExtension SEQUENCE { NR-DC
masterCellGroup CellGroupConfig with SCG DRBn added
condition DRBn as per in master cell
38.508-1[4] Table 4.6.3- group
19
mrdc-SecondaryCellGroupConfig CHOICE {
setup SEQUENCE {
mrdc-SecondaryCellGroup CHOICE {
nr-SCG RRCReconfiguration- OCTET STRING
SCGRLCreEst (CONTAINING
RRCReconfigurati
on)
radioBearerConfig2 RadioBearerConfig-
PDCPsplit
}
}
}
}
}
}
}
}
}
}
Table 7.1.3.5.3.3.3-2A: RRCReconfiguration-SCGRLCreEst (Table 7.1.3.5.3.3.3-2)
Derivation Path: 38.508-1 [4], Table 4.6.1-13 with condition NR-DC_SCG

secondaryCellGroup CellGroupConfig-SCG- OCTET STRING
RLC (CONTAINING
CellGroupConfig)
}
}
}
ETSI
Table 7.1.3.5.3.3.3-2B: CellGroupConfig-PDCP-ENDC(Table 7.1.3.5.3.3.3-2)

conditions AM and DRB2
}
}
Table 7.1.3.5.3.3.3-2C: CellGroupConfig-SCG-RLC (Table 7.1.3.5.3.3.3-2A)
Derivation Path: 38.508-1 [4], Table 4.6.1-19 with condition NR-DC_SCG

RLC-BearerConfig with
conditions AM and DRBn
}
}
Table 7.1.3.5.3.3.3-3: RadioBearerConfig-PDCP-ENDC (Table 4.1.3.5.3.3.3-2)

srb3-ToRelease Not present
drb-ToAddModList Not present
drb-ToAddModList SEQUENCE (SIZE 1 entry
(1..maxDRB)) OF DRB-ToAddMod {
eps-BearerIdentity 6
sdap-Config Not present
}
drb-Identity 2

recoverPDCP true
pdcp-Config PDCP-Config-Split
}
}
drb-ToReleaseList Not present
}
ETSI
Table 7.1.3.5.3.3.3-3A: RadioBearerConfig-PDCPsplit (Table 7.1.3.5.3.3.3-2)

OF {
DRB-ToAddMod[1] SEQUENCE {
cnAssociation Not present
drb-Identity DRB-Identity with SGC DRBn
condition DRBn
recoverPDCP true
}
}
}
Table 7.1.3.5.3.3.3-4: PDCP-Config-Split (Table 7.1.3.5.3.3.3-3)
Derivation Path: 38.508-1 [4], Table 4.6.3-99 condition EN-DC

cellGroup 1 EN-DC
0 MCG Path NR-DC
}
ul-DataSplitThreshold infinity
}
}
7.1.3.5.4 PDCP reordering / Maximum re-ordering delay below t-Reordering / t-Reordering

timer operations
(1)
with { UE in RRC_CONNECTED state using RLC-AM }
ensure that {
when { a PDCP PDU is received from the lower layers and the COUNT value of the received PDCP Data
PDU is out of the re-ordering window }
then { UE discards the PDCP PDU }
}
(2)
with { UE in RRC_CONNECTED state using RLC-AM }
ensure that {
when { a PDCP PDU is received from the lower layers and the COUNT value of the received PDCP Data
PDU is within the re-ordering window }
then { UE stores the resulting PDCP SDU }
}
(3)
with { UE in RRC_CONNECTED state using RLC-AM, and the RX_DELIV is not equal to the COUNT value of
the RX_NEXT (there is missing PDCP PDUs) }
ensure that {
when { a PDCP PDU is received from the lower layers and the RCVD_COUNT = RX_DELIV }
then { UE delivers the resulting PDCP SDU and all stored PDCP SDUs with consecutive COUNT value
to upper layer, in ascending order }
}
ETSI
(4)
with { UE in RRC_CONNECTED state using RLC-AM and the associated PDCP t-Reordering timer is running
}
ensure that {
when { RX_DELIV >= RX_REORD }
then { UE stops and resets t-Reordering timer }
}
(5)
}
ensure that {
when { the t-Reordering timer expires }
then { UE delivers all stored PDCP SDUs to upper layer }
}
(6)
}
ensure that {
when { the t-Reordering is reconfigured by upper layers }
then { UE stops and resets t-Reordering timer }
}
References: The conformance requirements covered in the present test case are specified in: TS 38.323, clause 5.2.2.1,
[TS 38.323, clause 5.2.2.1]
Variable;
Variable;
- RCVD_COUNT: the COUNT of the received PDCP Data PDU = [RCVD_HFN, RCVD_SN].
- else:
shall:
ETSI
entity shall:
RX_DELIV;
RX_DELIV < RX_NEXT:
[TS 38.323, clause 5.2.2.2]
When t-Reordering expires, the receiving PDCP entity shall:
decompression, if not decompressed before:
- all stored PDCP SDU(s) with associated COUNT value(s) < RX_REORD;
- all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from RX_REORD;
- update RX_DELIV to the COUNT value of the first PDCP SDU which has not been delivered to upper layers,
with COUNT value >= RX_REORD;
[TS 38.323, clause 5.2.2.3]
ETSI
When the value of the t-Reordering is reconfigured by upper layers while the t-Reordering is running, the receiving
PDCP entity shall:
- stop and restart t-Reordering.
t-Reordering ms300
ETSI

U-S Message
1 The SS sends the PDCP SDU #131072 <-- (PDCP SDU #131072) - -
D/C field = 1 (PDCP Data PDU) and PDCP SN =
131072. (Note 1)
2 Check: Does the UE transmit a PDCP SDU via the --> (PDCP SDU) 1 F
AM RLC entity in the next 1s?
D/C field = 1 (PDCP Data PDU) and PDCP SN = 1.
The UE starts t-Reordering.
D/C field = 1 (PDCP Data PDU) and PDCP SN =2.
5 Wait for 100ms (< configured t-Reordering). - - - -
7 Check: Does the UE transmit the PDCP SDU #0 --> (PDCP SDU #0) 2, 3 P
via the AM RLC entity
0?
(Note 4)
1?
(Note 4)
2?
(Note 4)
11 Wait for 100ms (< configured t-Reordering) - - - -
The UE restarts t-Reordering timer.
Note T1
14 Check: Does the UE transmit the PDCP SDU #3 --> (PDCP SDU #3) 3 P
via the AM RLC entity?
(Note 5)
15 Check: Does the UE transmit the PDCP SDU #4 --> (PDCP SDU #4) 3 P
via the AM RLC entity?
(Note 5)
16 Check 1: Does the UE transmit the PDCP SDU #7 --> (PDCP SDU #7) 4,5 P
with PDCP SN=5 via the AM RLC entity after t-
Reordering expiry?
Note T2
Check 2: Is (T2 – T1) > t-Reordering?
18 Wait for 100ms (< configured t-Reordering) - - - -
19 The SS reconfigures the t-Reordering by sending a <-- RRCReconfiguration - -
NR RRCReconfiguration message.
The UE restarts t-Reordering timer. (Note 2)
Note T3
20 The UE transmits a NR --> RRCReconfigurationComple - -
RRCReconfigurationComplete message. te
(Note 3)
21 Check 1: Does the UE transmit the PDCP SDU #9 --> (PDCP SDU #9) 6 P
ETSI
with PDCP SN=6 via the AM RLC entity after t-

Reordering expiry?
Note T4
Check 2: Is (T4 – T3) > t-Reordering?
Note 1: The Reordering Window size is 131072 when 18 bit SN length is used.
[7], Table 4.6.1-8 using condition EN-DC_Embed_RBConfig.
Note 4: PDCP SDUs at steps 7, 8 and 9 may be received by the SS in the same slot or in multiple slots (max one
MAC PDU in a slot)
Note 5: PDCP SDUs at steps 14 and 15 may be received by the SS in the same slot or in multiple slots (max one
MAC PDU in a slot).

radioBearerConfig RadioBearerConfig Not EN-DC
}
RRCReconfiguration-v1530-IEs::= SEQUENCE {
masterCellGroup CellGroupConfig Not-EN-DC
}
}

drb-ToAddModList ::= SEQUENCE (SIZE 1..2)) OF DRB-
1 entry
ToAddMod {
pdcp-Config SEQUENCE {
drb SEQUENCE {
outOfOrderDelivery False
}
t-Reordering ms750
}
}
}
}
7.1.3.5.5 PDCP Duplication
(1)
with { UE in RRC_CONNECTED state and pdcpDuplication is configured and activated}
ensure that {
when { UE has PDCP SDUs available for transmission}
then { the UE transmits the PDCP SDUs on both the associated RLC entities }
}
ETSI
(2)
with { UE in RRC_CONNECTED state and pdcpDuplication is configured and not activated }
ensure that {
when { UE receives MAC Control Element to Activate PDCP Duplication on a DRB configured with PDCP
duplication }
then { the UE activates PDCP Duplication on the PDCP associated with the DRB }
}
(3)
with { UE in RRC_CONNECTED state and pdcpDuplication is configured }
ensure that {
then { the UE transmits the PDCP SDUs on the primary RLC entity}
}
(4)
ensure that {
when { the UE had transmited the PDCP SDUs on both the associated RLC entities and successful
delivery of a PDCP Data PDU is confirmed by one of the two associated AM RLC entities}
then { the other AM RLC entity discards the duplicated PDCP Data PDU}
}
References: The conformance requirements covered in the present TC are specified in: TS 38.321:5.10, 6.1.3.10 and
TS 38.323:5.2.1, 5.11.1, 5.11.2 and TS 38.331: 5.3.5.6.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.323, clause 5.2.1]
- if the PDCP duplication is activated:
- duplicate the PDCP Data PDU and submit the PDCP Data PDU to both associated RLC entities;
- else:
- submit the PDCP Control PDU to the primary RLC entity;
- else:
- if the two associated RLC entities belong to the different Cell Groups; and
specified in TS 38.322 [5]) in the two associated RLC entities is equal to or larger than ul-
DataSplitThreshold:
- submit the PDCP PDU to either the primary RLC entity or the secondary RLC entity;
- else:
- submit the PDCP PDU to the primary RLC entity.
[TS 38.331, clause 5.3.5.6.4]
The UE shall:
ETSI
1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration; or
1> for each drb-Identity value that is to be released as the result of full configuration according to 5.3.5.11:
2> release the PDCP entity and the drb-Identity;
2> if SDAP entity associated with this DRB is configured:
3> indicate the release of the DRB to SDAP entity associated with this DRB (TS 37.324 [24], clause 5.3.3);
3> if a new bearer is not added either with NR or E-UTRA with same eps-BearerIdentity:
4> indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers.
NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity
value that is not part of the current UE configuration.
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is
determined by the CellGroupConfig.
[TS 38.323, clause 5.11.1]
For the PDCP entity configured with pdcp-Duplication, the transmitting PDCP entity shall:
- for SRBs:
- activate the PDCP duplication;
- for DRBs:
- if the activation of PDCP duplication is indicated:
- if the deactivation of PDCP duplication is indicated:
- deactivate the PDCP duplication.
[TS 38.323, clause 5.11.2]
- if the successful delivery of a PDCP Data PDU is confirmed by one of the two associated AM RLC entities:
- indicate to the other AM RLC entity to discard the duplicated PDCP Data PDU;
- if the deactivation of PDCP duplication is indicated:
- indicate to the secondary RLC entity to discard all duplicated PDCP Data PDUs.
[TS 38.321, clause 5.10]
If one or more DRBs are configured with PDCP duplication, the network may activate and deactivate the PDCP
duplication for the configured DRB(s).
The PDCP duplication for the configured DRB(s) is activated and deactivated by:
- receiving the Duplication Activation/Deactivation MAC CE described in subclause 6.1.3.11;
- indication by RRC.
The MAC entity shall for each DRB configured with PDCP duplication:
1> if a Duplication Activation/Deactivation MAC CE is received activating the PDCP duplication of the DRB:
2> indicate the activation of PDCP duplication of the DRB to upper layers.
ETSI
1> if a Duplication Activation/Deactivation MAC CE is received deactivating the PDCP duplication of the DRB:
2> indicate the deactivation of PDCP duplication of the DRB to upper layers.
System Simulator:
- For NR 5GC NR Cell 1 and NR Cell 10
UE:
- None
Preamble:
- Same Pre-test conditions as in clause 7.1.3.0 and Generic procedure parameter DC bearer (MCG and split).
- For NR 5GC, Same Pre-test conditions as in clause 7.1.3.0 using generic procedure parameter Connectivity (NR-
DC), Bearers(MCG(s) and Split),
ETSI

U-S Message
1 Void - - - -
2 SS transmits a Duplication Activation MAC CE to <-- MAC PDU (Duplication - -
activate PDCP Duplication for split DRB. Activation MAC Control
Element)
2A The SS is configured not to send RLC ACK for the - - - -
next PDU on split DRB. (Note 6)
on the AM RLC primary entity.
- EXCEPTION: Steps 4-4A below occur in any - - - -
sequence
the AM RLC primary entity?
4A Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 2 P
the AM RLC secondary entity?
4B- Void - - - -
4C
5 SS transmits a Duplication Deactivation MAC CE to <-- MAC PDU (Duplication - -
deactivate PDCP Duplication for split DRB. Deactivation MAC Control
Element)
the AM RLC entity configured on the AM RLC
primary entity?
message to activate parameters for
PdcpDuplication(Note 2)
8A UE responses NR RRCReconfigurationComplete --> RRCReconfigurationComple - -
message.(Note 3) te
8AA The SS is configured not to send RLC ACK for the - - - -
next PDU on split DRB. (Note 6)
8B The SS sends a PDCP Data PDU on the split DRB <-- PDCP DATA PDU - -
- EXCEPTION: Steps 8C-8D below occur in any - - - -
sequence
8C Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 1 P
8D Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 1 P
the AM RLC secondary entity?
8E- Void - - - -
8F
9 The SS stops allocating any UL grant for the AM - - - -
RLC secondary entity(Note 1)
11 UE transmits a PDCP Data PDU on the AM RLC --> PDCP DATA PDU - -
primary entity
12 The SS resumes normal UL grant allocation for the - - - -
AM RLC secondary entity.
13 Check: Does UE transmit a PDCP Data PDU on --> PDCP DATA PDU 4 F
the AM RLC primary or secondary entity in next
five seconds?
Note 1: Discard of RLC SDU is not possible if submitted to lower layers. Therefore, Grant is not provided so that
RLC SDU is not submitted to lower layers.
Note 2: For EN-DC the NR RRCReconfiguration is contained in RRCConnectionReconfiguration Table
7.1.3.5.5.3.3-4.
Note 4: Void
Note 5: Void
Note 6: SS is configured not to send RLC ACK for the next PDU on split DRB to ensure that UE side primary or
ETSI
secondary entities do not discard the PDU before PDSCH transmission upon receipt of RLC ACK on one of
the entities. This may cause UE side entities to retransmit the PDU but it shall be ignored by SS side RLC
entity as it has already been received though not acknowledged due to SS side RLC being configured in
test mode.
Table 7.1.3.5.5.3.3-0A: RRCConnectionReconfiguration (step 8, Table 7.1.3.5.5.3.2-1)

c1 CHOICE{
{
including
RadioBearerConfig-
PDCP
}
}
}
}
}
}
}
}
}
}
}
}
Table 7.1.3.5.5.3.3-0B: RRCReconfiguration (step 8, Table 7.1.3.5.5.3.2-1)

radioBearerConfig2 OCTET STRING
including
RadioBearerConfig-
PDCP
}
}
}
}
}
}
ETSI
Table 7.1.3.5.5.3.3-1: RadioBearerConfig-PDCP (Table 7.1.3.5.5.3.3-0A and Table 7.1.3.5.5.3.3-0B ,

Step 8)

drb-ToAddModList Not present
OF DRB-ToAddMod {
drb-Identity 2 EN-DC
SCG DRBn NR
}
}
drb-ToReleaseList Not present
}
Table 7.1.3.5.5.3.3-2: PDCP-Config-Split (Table 7.1.3.5.5.3.3-1)
Derivation Path: 38.508-1 [4], Table 4.6.3-99 condition Split

cellGroup 1 EN-DC
0 NR
}
ul-DataSplitThreshold infinity
pdcp-Duplication true
}
}
7.1.3.5.6 PDCP Duplication / 3 RLC entities
(1)
ensure that {
then { the UE transmits the PDCP SDUs on all the associated RLC entities}
}
(2)
with { UE in RRC_CONNECTED state and pdcpDuplication is configured and not activated}
ensure that {
when { UE receives MAC Control Element to Activate PDCP Duplication on a DRB configured with PDCP
duplication}
then { the UE activates PDCP Duplication on the PDCP associated with the DRB}
}
(3)
with { UE in RRC_CONNECTED state and pdcpDuplication is configured}
ensure that {
then { the UE transmits the PDCP SDUs on the primary RLC entity}
}
ETSI
(4)
ensure that {
when { the UE had transmitted the PDCP SDUs on all the associated RLC entities and successful
delivery of a PDCP Data PDU is confirmed by one of the associated AM RLC entities}
then { the other AM RLC entities discard the duplicated PDCP Data PDU}
}
(5)
ensure that {
when { UE receives MAC Control Element to deactivate PDCP Duplication on one of the associated RLC
entity configured with PDCP duplication}
then { the UE deactivate the PDCP duplication for the indicated associated RLC entity}
References: The conformance requirements covered in the present TC are specified in: TS 38.321:5.10, 6.1.3.11,
6.1.3.32, TS 38.323:5.2.1, 5.11.1, 5.11.2 and TS 38.331: 5.3.5.6.4. Unless otherwise stated these are Rel-16
requirements.
[TS 38.323, clause 5.2.1]
- else, if the transmitting PDCP entity is associated with at least two RLC entities:
- if the PDCP duplication is activated for the RB:
- duplicate the PDCP Data PDU and submit the PDCP Data PDU to the associated RLC entities
activated for PDCP duplication;
- else:
- submit the PDCP Control PDU to the primary RLC entity;
- else (i.e. the PDCP duplication is deactivated for the RB):
- if the split secondary RLC entity is configured; and
specified in TS 38.322 [5]) in the primary RLC entity and the split secondary RLC entity is equal to or
larger than ul-DataSplitThreshold:
- submit the PDCP PDU to either the primary RLC entity or the split secondary RLC entity;
- else, if the transmitting PDCP entity is associated with the DAPS bearer:
- if the uplink data switching has not been requested:
- submit the PDCP PDU to the RLC entity associated with the source cell;
- else:
- submit the PDCP Data PDU to the RLC entity associated with the target cell;
- else:
- if the PDCP Control PDU is associated with source cell:
ETSI
- submit the PDCP Control PDU to the RLC entity associated with the source cell;
- else:
- submit the PDCP Control PDU to the RLC entity associated with the target cell;
- else:
- submit the PDCP PDU to the primary RLC entity.
[TS 38.323, clause 5.11.1]
- for SRBs:
- for DRBs:
- if the activation of PDCP duplication is indicated for the DRB:
- activate the PDCP duplication for the DRB;
- if the activation of PDCP duplication is indicated for at least one associated RLC entities:
- activate the PDCP duplication for the indicated associated RLC entities;
- activate the PDCP duplication for the DRB;
- if the deactivation of PDCP duplication is indicated for the DRB:
- deactivate the PDCP duplication for the DRB;
- if the deactivation of PDCP duplication is indicated for at least one associated RLC entities:
- deactivate the PDCP duplication for the indicated associated RLC entities;
- if all associated RLC entities other than the primary RLC entity are deactivated for PDCP duplication:
- deactivate the PDCP duplication for the DRB.
[TS 38.323, clause 5.11.2]
- if the successful delivery of a PDCP Data PDU is confirmed by one of the associated AM RLC entities:
- indicate to the other AM RLC entities to discard the duplicated PDCP Data PDU;
- if the deactivation of PDCP duplication is indicated for the DRB:
- indicate to the RLC entities other than the primary RLC entity to discard all duplicated PDCP Data PDUs;
- if the deactivation of PDCP duplication is indicated for at least one associated RLC entities:
- indicate to the RLC entities deactivated for PDCP duplication to discard all duplicated PDCP Data PDUs.
[TS 38.321, clause 5.10]
If one or more DRBs are configured with PDCP duplication, the network may activate and deactivate the PDCP
duplication for all or a subset of associated RLC entities for the configured DRB(s).
The PDCP duplication for the configured DRB(s) is activated and deactivated by:
- receiving the Duplication Activation/Deactivation MAC CE described in clause 6.1.3.11;
- receiving the Duplication RLC Activation/Deactivation MAC CE described in clause 6.1.3.32;
ETSI
The PDCP duplication for all or a subset of associated RLC entities for the configured DRB(s) is activated and
deactivated by:
- receiving the Duplication RLC Activation/Deactivation MAC CE described in clause 6.1.3.32;
The MAC entity shall for each DRB configured with PDCP duplication:
1> if a Duplication Activation/Deactivation MAC CE is received activating the PDCP duplication of the DRB:
2> indicate the activation of PDCP duplication of the DRB to upper layers.
1> if a Duplication Activation/Deactivation MAC CE is received deactivating the PDCP duplication of the DRB:
2> indicate the deactivation of PDCP duplication of the DRB to upper layers.
1> if a Duplication RLC Activation/Deactivation MAC CE is received activating PDCP duplication for associated
RLC entities of a DRB configured with PDCP duplication:
2> indicate the activation of PDCP duplication for the indicated secondary RLC entity(ies) of the DRB to upper
layers.
1> if a Duplication RLC Activation/Deactivation MAC CE is received deactivating PDCP duplication for associated
RLC entities of a DRB configured with PDCP duplication:
2> indicate the deactivation of PDCP duplication for the indicated secondary RLC entity(ies) of the DRB to
upper layers.
[TS 38.331, clause 5.3.5.6.4]
The UE shall:
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset
or released is determined by the CellGroupConfig.7.1.3.5.6.3 Test description
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 and NR Cell 6 are the SCells
UE:
- None
ETSI
Preamble:
- Same Pre-test conditions as in clause 7.1.3.0 and NR Cell 3 and NR Cell 6 are configured as NR Active Scells.

U-S Message
1 SS transmits a MAC CE to activate PDCP MAC PDU (Duplication
Duplication for split DRB. RLCActivation MAC Control
Element)
- EXCEPTION: Steps 3-4 below occur in any - - - -
sequence
the associated AM RLC entities?
5 SS transmits a MAC CE to deactivate PDCP <-- MAC PDU (Duplication RLC - -
Duplication for split DRB. Deactivation MAC Control
Element)
the indicated associated RLC entity configured on
8 SS transmits a MAC CE to deactivate PDCP <-- MAC PDU (Duplication RLC - -
Duplication for split DRB. Deactivation MAC Control
Element)
message to activate parameters for
PdcpDuplication.
11 UE responses NR RRCReconfigurationComplete --> RRCReconfigurationComple - -
message. te
- EXCEPTION: Steps 13-14 below occur in any - - - -
sequence
the associated AM RLC entities?
15 The SS stops allocating any UL grant for the - - - -
associated AM RLC entities.(Note)
17 UE transmits a PDCP Data PDU on the AM RLC --> PDCP DATA PDU - -
primary entity
18 The SS resumes normal UL grant allocation for the - - - -
associated AM RLC entities.
the AM RLC primary or the associated AM RLC
entities in next five seconds?
Note: Discard of RLC SDU is not possible if submitted to lower layers. Therefore, Grant is not provided so that RLC
SDU is not submitted to lower layers.
ETSI
Table 7.1.3.5.6.3.3-1: RadioBearerConfig (step 10, Table 7.1.3.5.6.3.2-1)

OF DRB-ToAddMod {
drb-Identity DRBn
}
}
}
Table 7.1.3.5.6.3.3-2: PDCP-Config (Table 7.1.3.5.6.3.3-1)
Derivation Path: 38.508-1 [4], Table 4.6.3-99 condition Split

t-Reordering Not present
moreThanTwoRLC-DRB-r16 SEQUENCE {
duplicationState-r16 SEQUENCE (SIZE (3)) 3 entries
duplicationState-r16[1] true
}
}
7.1.3.5.7 Ethernet header compression and decompression / Correct functionality of

ethernet header compression and decompression
Editor’s note: Configuration of ethernet protocol is FFS.
(1)
ensure that {
when { Ethernet header compression functionality is taken into use on DRB }
then { UE performs correct ethernet header compression and decompression function on DRB }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.323, clause 5.12. These
are Rel-16 requirements.
[TS 38.323, clause 5.12.2]
PDCP entities associated with DRBs can be configured by upper layers TS 38.331 [3] to use EHC. Each PDCP entity
carrying user plane data may be configured to use EHC. Every PDCP entity uses at most one EHC compressor instance
and at most one EHC decompressor instance.
[TS 38.323, clause 5.12.3]
The usage and definition of the parameters shall be as specified below.
ETSI
- MAX_CID_EHC_UL: This is the maximum CID value that can be used for uplink. One CID value shall always
be reserved for uncompressed flows. The parameter MAX_CID_EHC_UL is configured by upper layers
(maxCID-EHC-UL in TS 38.331 [3]);
[TS 38.323, clause 5.12.4]
If EHC is configured, the EHC protocol generates two types of output packets:
- EHC compressed packets (i.e. EHC full header packets and EHC compressed header packets), each associated
with one PDCP SDU;
- standalone packets not associated with a PDCP SDU, i.e. EHC feedback.
An EHC compressed packet is associated with the same PDCP SN and COUNT value as the related PDCP SDU. The
header compression is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP SDU.
EHC feedback are not associated with a PDCP SDU. They are not associated with a PDCP SN and are not ciphered.
[TS 38.323, clause 5.12.5]
If EHC is configured by upper layers for PDCP entities associated with user plane data, the PDCP Data PDUs are
decompressed by the EHC protocol after performing deciphering as explained in clause 5.8. The header decompression
is not applicable to the SDAP header and the SDAP Control PDU if included in the PDCP Data PDU.
[TS 38.323, clause 5.12.6.1]
When an EHC feedback is generated by the EHC protocol, the transmitting PDCP entity shall:
- submit to lower layers the corresponding PDCP Control PDU as specified in clause 6.2.3.3 i.e. without
associating a PDCP SN, nor performing ciphering.
[TS 38.323, clause 5.12.6.2]
At reception of a PDCP Control PDU for EHC feedback from lower layers, the receiving PDCP entity shall:
- deliver the corresponding EHC feedback to the EHC protocol without performing deciphering.
Pre-test conditions as in clause 7.1.3.0 with condition pc_NG_RAN_NR, one PDN/PDU session and message with
condition UM used for step 7 in 4.5.4.2 according to [4].
ETSI

U-S Message
to configure DRB to use ethernet header
compression.
2 UE transmits RRCReconfigurationComplete --> RRCReconfigurationComplete - -
message to confirm that reconfiguration with
ethernet header compression configuration is
completed.
3 SS Transmits a ciphered PDCP Data PDU with <-- PDCP Data PDU #0 - -
unique Context ID containing full header
ethernet packet.
4 CHECK: Does UE transmit uncyphered EHC --> PDCP Control PDU #0 1 P
feedback packet with Context ID set in step 3?
5 CHECK: Does UE transmit ciphered looped --> PDCP Data PDU #0 1 P
back PDCP Data PDU with unique Context ID
containing full header ethernet packet?
6 SS Transmits uncyphered EHC feedback <-- PDCP Control PDU #0 - -
packet with Context ID set in step 5
7 SS Transmits a ciphered PDCP Data PDU with --> PDCP Data PDU #1 - -
unique Context ID set in step 3 containing
compressed header ethernet packet.
8 CHECK: Does UE transmit ciphered looped --> PDCP Data PDU #1 1 P
back PDCP Data PDU with Context ID set in
step 5 containing compressed header ethernet
packet?
Derivation Path: TS 38.508 [4], clause 4.6.1, table 4.6.1-13 RRCReconfiguration

radioBearerConfig RadioBearerConfig-EHC
}
}
}
Table 7.1.3.5.7.3.3-2: RadioBearerConfig-EHC (Table 7.1.3.5.7.3.3-1)

OF DRB-ToAddMod {
drb-Identity DRB-Identity for DRB
created in pre-test
conditions
pdcp-Config PDCP-Config-EHC
}
}
}
ETSI
Table 7.1.3.5.7.3.3-3: PDCP-Config-EHC
Derivation Path: TS38.331 [12], clause 6.3.2

ethernetHeaderCompression-r16 SEQUENCE {
ehc-Common-r16 SEQUENCE {
ehc-CID-Length-r16 bits15
}
ehc-Downlink-r16 SEQUENCE {
drb-ContinueEHC-DL-r16 true
}
ehc-Uplink-r16 SEQUENCE {
maxCID-EHC-UL-r16 32767
drb-ContinueEHC-UL-r16 true
}
}
}
7.1.4 SDAP
7.1.4.1 SDAP Data Transfer and PDU Header Handling UL/DL
(1)
with { UE in RRC_CONNECTED state with multiple DRB's established, each mapping more than one QoS
flow }
ensure that {
when { UE receives an SDAP PDU with SDAP header }
then { UE SDAP entity retrieves the SDAP SDU from the SDAP PDU and delivers it to upper layer }
}
(2)
with { UE in RRC_CONNECTED state with multiple DRB's established configured with UL SDAP header,
each mapping more than one QoS flow configured by RRC }
ensure that {
when { UE has to transmit a SDAP PDU with header to be included }
then {UE builds an SDAP PDU from the SDAP SDU including the header, and maps it to the DRB as
per stored DRB mapping rule for the QoS flow }
}
(3)
with { UE in RRC_CONNECTED state with multiple DRB's and QoS flows established }
ensure that {
when { UE receives a SDAP PDU with SDAP header and RDI fields set to 1 }
then { UE stores the QoS flow to DRB mapping of the DL SDAP PDU as the QoS flow to DRB mapping
rule for the UL and uses it for further UL SDAP PDU transmissions }
}
(4)
with { UE in RRC_CONNECTED state with multiple DRB's and QoS flows established }
ensure that {
when { UE receives a SDAP PDU with SDAP header and RDI field set to 1 and the stored QoS flow to
DRB mapping rule for the QoS flow is different from the QoS flow to DRB mapping of the DL SDAP data
PDU }
then { UE stores the QoS flow to DRB mapping of the DL SDAP PDU as the QoS flow to DRB mapping
rule for the UL, to be used for further UL SDAP PDU transmissions and transmits an end-marker
control PDU for the QoS flow on the old DRB }
}
ETSI
(5)
with { UE in RRC_CONNECTED state with multiple DRB's and QoS flows established with QoS flow to DRB
mapping }
ensure that {
when { UE receives a message which configures a new QoS flow to DRB mapping, different from the
existing mapping }
then { UE stores the QoS flow to DRB mapping to be used for further UL SDAP PDU transmissions
and transmits an end-marker control PDU for the QoS flow on the old DRB }
}
5.2.2, 5.3.1, 5.3.2, 6.2.2.1, 6.2.2.2, 6.2.2.3, 6.2.3 and 6.3.4, TS 24.501 clause 6.2.5.1.3. Unless otherwise stated these are
[TS 37.324 clause 5.2.1]
At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity shall:
- if there is no stored QoS flow to DRB mapping rule for the QoS flow as specified in the subclause 5.3:
- map the SDAP SDU to the default DRB;
- else:
- map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule;
- if the DRB to which the SDAP SDU is mapped is configured by RRC (3GPP TS 38.331 [3]) with the presence
of SDAP header,
- construct the UL SDAP data PDU as specified in the subclause 6.2.2.3;
- else:
- submit the constructed UL SDAP data PDU to the lower layers.
NOTE 1: UE behaviour is not defined if there is neither a default DRB nor a stored QoS flow to DRB mapping rule
for the QoS flow.
NOTE 2: Default DRB is always configured with UL SDAP header (3GPP TS 38.331 [3]).
[TS 37.324 clause 5.2.2]
At the reception of an SDAP data PDU from lower layers for a QoS flow, the receiving SDAP entity shall:
- if the DRB from which this SDAP data PDU is received is configured by RRC (3GPP TS 38.331 [3]) with the
presence of SDAP header:
- perform reflective QoS flow to DRB mapping as specified in the subclause 5.3.2;
- perform RQI handling as specified in the subclause 5.4;
- retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.2.
- else:
- retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.1;
- deliver the retrieved SDAP SDU to the upper layer.
[TS 37.324 clause 5.3.1]
When RRC (3GPP TS 38.331 [3]) configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity
shall:
ETSI
- if the SDAP entity has already been established and there is no stored QoS flow to DRB mapping rule for the
QoS flow and a default DRB is configured:
- construct an end-marker control PDU, as specified in the subclause 6.2.3, for the QoS flow;
- map the end-marker control PDU to the default DRB;
- submit the end-marker control PDU to the lower layers.
- if the stored UL QoS flow to DRB mapping rule is different from the configured QoS flow to DRB mapping rule
for the QoS flow and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC
(3GPP TS 38.331 [3]) with the presence of UL SDAP header:
- map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;
- store the configured UL QoS flow to DRB mapping rule for the QoS flow.
When RRC (3GPP TS 38.331 [3]) releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity
shall:
- remove the UL QoS flow to DRB mapping rule for the QoS flow.
[TS 37.324 clause 5.3.2]
For each received DL SDAP dataPDU with RDI set to 1, the SDAP entity shall:
- process the QFI field in the SDAP header and determine the QoS flow;
- if there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:
- submit the end-marker control PDU to the lower layers;
- if the stored QoS flow to DRB mapping rule for the QoS flow is different from the QoS flow to DRB mapping of
the DL SDAP data PDU and the DRB according to the stored QoS flow to DRB mapping rule is configured by
RRC (3GPP TS 38.331 [3]) with the presence of UL SDAP header:
- submit the end-marker control PDU to the lower layers;
- store the QoS flow to DRB mapping of the DL SDAP data PDU as the QoS flow to DRB mapping rule for the
UL.
[TS 37.324 clause 6.2.2.1]
An SDAP PDU consists only of a data field and does not consist of any SDAP header, as described in Figure 6.2.2.1-1.
Figure 6.2.2.1-1: SDAP Data PDU format without SDAP header
ETSI
[TS 37.324 clause 6.2.2.2]
Figure 6.2.2.2 – 1 shows the format of SDAP Data PDU of DL with SDAP header being configured.
Figure 6.2.2.2-1: DL SDAP Data PDU format with SDAP header
[TS 37.324 clause 6.2.2.3]
Figure 6.2.2.3 – 1 shows the format of SDAP Data PDU of UL with SDAP header being configured.
Figure 6.2.2.3-1: UL SDAP Data PDU format with SDAP header
[TS 37.324 clause 6.2.3]
Figure 6.2.3 – 1 shows the format of End-Marker Control PDU.
D/C R QFI Oct 1
Figure 6.2.2.3-1: UL SDAP Data PDU format with SDAP header
[TS 37.324 clause 6.3.4]
Length: 6 bits
The QFI field indicates the ID of the QoS flow (3GPP TS 23.501 [4]) to which the SDAP PDU belongs.
[TS 24.501 clause 6.2.5.1.3]
ETSI
For PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, upon receiving an UL user data packet from the
upper layers for transmission via a PDU session, the UE shall attempt to associate the UL user data packet with:
a) the QFI of a signalled QoS rule associated with the PDU session which has a set of packet filters containing a
packet filter for UL direction matching the UL user data packet or containing a packet filter for both UL and DL
directions matching the UL user data packet; or
b) the QFI of a derived QoS rule associated with the PDU session which has the packet filter for UL direction
matching the UL user data packet;
by evaluating the QoS rules in increasing order of their precedence values until the UL user data packet is associated
with a QFI or all QoS rules are evaluated.
For PDU session of unstructured PDU session type, upon receiving an UL user data packet from the upper layers for
transmission via a PDU session, the UE shall associate the UL user data packet with the QFI of the default QoS rule
associated with the PDU session.
If the UL user data packet is associated with a QFI, the UE shall pass the QFI along the UL user data packet to the
lower layers for transmission.
NOTE: Marking of the UL user data packet with the QFI is performed by the lower layers.
If all QoS rules are evaluated and the UL user data packet is not associated with a QFI, the UE shall discard the UL user
data packet.
System Simulator:
- NR Cell 1
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A with one PDU session active according to TS 38.508-1 [4], clause 4.4A.3, Table
4.4A.3-1 and using the message condition UE TEST LOOP MODE B active with IP PDU delay = 1 second, to
return one SDAP SDU per DL SDAP SDU. 2 DRBs are configured where DRB j is defined as default DRB. The
NAS QoS rules for the QoS flows with QFI=1, QFI=2, QFI=5 and QFI=6 are configured. QoS flows with QFI=5
and QFI=6 are mapped to DRB j, QoS flows with QFI=1 and QFI=2 are mapped to DRB k.
ETSI

U-S Message
1 The SS sends the SDAP Data PDU with SDAP <-- SDAP DL Data PDU - -
header on DRB k and the following content to
the UE: RDI=0. RQI=0, QFI=2.
2 Check: Does the UE re-transmit SDAP Data --> SDAP UL Data PDU 1,2 P
PDU on DRB k with SDAP header as per the
stored DRB mapping flow with QFI=2?
the UE: RDI=1, RQI=0, QFI=5.
7.1.4.1.3.2-2 shall take place.
4 Check: Does the UE re-transmit SDAP Data --> SDAP UL Data PDU 3 P
stored DRB mapping Flow with QFI=5?
5 The SS transmits an RRCReconfiguration <-- RRCReconfiguration - -
message including a PDU SESSION (PDU SESSION MODIFICATION
MODIFICATION COMMAND COMMAND)
in step 6 the events specified in Tables
7.1.4.1.3.2-3 and 7.1.4.1.3.2-4 shall take
place.
6 The UE transmits an --> RRCReconfigurationComplete - -
the UE: RDI=0. RQI=0, QFI=4.
8 Check: Does the UE re-transmit SDAP Data --> SDAP UL Data PDU 5 P
stored DRB mapping Flow with QFI=4?
Table 7.1.4.1.3.2-2: Parallel behaviour

U-S Message
1 Check: Does the UE transmit End-Marker --> SDAP UL Control PDU 4 P
Control PDU on DRB j for QFI=5?

U-S Message
Control PDU on DRB j for QFI=4?

U-S Message
1 The UE Transmits PDU SESSION --> ULInformationTransfer - -
MODIFICATION COMPLETE (PDU SESSION MODIFICATION
COMPLETE)
ETSI
Table 7.1.4.1.3.3-1: RadioBearerConfig-DRB (Preamble)
Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition NR

drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) 2 entries
OF DRB-ToAddMod {
sdap-Config SEQUENCE {
pdu-Session The same as the PDU
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
sdap-HeaderDL present
sdap-HeaderUL present
defaultDRB false
mappedQoS-FlowsToAdd SEQUENCE {
QFI 1
QFI 2
}
}
}
drb-Identity k k is allocated
according to
internal TTCN
mapping
}
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
defaultDRB true
QFI 5
QFI 6
}
}
}
}
drb-Identity j j is allocated
according to
internal TTCN
mapping
}
}
}
ETSI
Table 7.1.4.1.3.3-2: RadioBearerConfig-DRB (step 5, Table 7.1.4.1.3.2-1)

RadioBearerConfig ::= SEQUENCE { - -
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) 1 entry BID is the total
OF DRB-ToAddMod { number of
established DRBs
in the UE, before
applying the
contents of this IE
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
defaultDRB false
QFI 4
}
}
according to
internal TTCN
mapping
}
}
}
}
Table 7.1.4.1.3.3-3: PDU SESSION MODIFICATION COMMAND (step 5, Table 7.1.4.1.3.2-1)

PDU session ID The same as the PDU
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
Authorized QoS rules 1 entry
QoS rule [1] Reference QoS rule #4a QFI=4
as defined in Table
4.8.2.1-4a.
Authorized QoS flow descriptions 1 entry
QoS flow [1] Reference QoS flow #2a QFI=4
as defined in Table
4.8.2.3-2a.
ETSI
Table 7.1.4.1.3.3-4: PDU SESSION ESTABLISHMENT ACCEPT (Preamble)

session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
Authorized QoS rules 4 entries
QoS rule [1] Reference QoS rule #1 QFI=1
as defined in Table
4.8.2.1-1
as defined in Table
4.8.2.1-4
as defined in Table
4.8.2.1-5
as defined in Table
4.8.2.1-6
Mapped EPS Bearer contexts Not Present
Authorized QoS flow descriptions 4 entries
QoS flow [1] Reference QoS flow #1 QFI=1
as defined in Table
4.8.2.3-1
as defined in Table
7.1.4.1.3.3-5
as defined in Table
7.1.4.1.3.3-6
as defined in Table
4.8.2.3-4
Table 7.1.4.1.3.3-5: Reference QoS flow #1 (Preamble)
Derivation Path: TS 38.508-1 [4], table 4.8.2.3-1

QoS flow descriptions
QoS flow description 1 entry
QFI ‘00 0001’B QFI 1
Operation code ‘001’B Create new QoS
flow description
E bit ‘1’B Parameters list is
included
Number of parameters ’00 0001’B 1 parameter
5QI ‘0000 1001’B 5QI 9
ETSI

QFI ‘00 0010’B QFI 2
flow description
included
5QI ‘0000 0101’B 5QI 5
7.1.4.2 SDAP Data Transfer handling without Header UL/DL
(1)
with { UE in RRC_CONNECTED state with multiple DRB's established. SDAP configured without header and
no stored QoS flow mapping }
ensure that {
when { UE receives a SDAP SDU from upper layers }
then { UE SDAP entity transmits the SDAP PDU with header on default DRB }
}
(2)
no stored QoS flow mapping }
ensure that {
when { UE SDAP recieves from RRC new Qos Flow mapping }
then { UE SDAP entity transmits an end-marker control PDU for the QoS flow on default DRB }
}
(3)
stored QoS flow mapping configured by RRC }
ensure that {
when { UE receives a SDAP SDU from upper layers }
then { UE SDAP entity transmits the SDAP PDU without header on non default DRB as per configured
QoS flow mapping }
}
5.2.2, 5.3.1, 6.2.2.1 and 6.2.3, TS 24.501 clause 6.2.5.1.3. Unless otherwise stated these are Rel-15 requirements.
[TS 37.324 clause 5.2.1]
At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity shall:
- if there is no stored QoS flow to DRB mapping rule for the QoS flow as specified in the subclause 5.3:
- map the SDAP SDU to the default DRB;
- else:
- map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule;
- if the DRB to which the SDAP SDU is mapped is configured by RRC (3GPP TS 38.331 [3]) with the presence
of SDAP header,
ETSI
- else:
- submit the constructed UL SDAP data PDU to the lower layers.
NOTE 1: UE behaviour is not defined if there is neither a default DRB nor a stored QoS flow to DRB mapping rule
for the QoS flow.
NOTE 2: Default DRB is always configured with UL SDAP header (3GPP TS 38.331 [3]).
[TS 37.324 clause 5.2.2]
At the reception of an SDAP data PDU from lower layers for a QoS flow, the receiving SDAP entity shall:
- if the DRB from which this SDAP data PDU is received is configured by RRC (3GPP TS 38.331 [3]) with the
presence of SDAP header:
- perform reflective QoS flow to DRB mapping as specified in the subclause 5.3.2;
- perform RQI handling as specified in the subclause 5.4;
- retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.2.
- else:
- retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.1;
- deliver the retrieved SDAP SDU to the upper layer.
[TS 37.324 clause 5.3.1]
When RRC (3GPP TS 38.331 [3]) configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity
shall:
- if the SDAP entity has already been established and there is no stored QoS flow to DRB mapping rule for the
QoS flow and a default DRB is configured:
- if the stored UL QoS flow to DRB mapping rule is different from the configured QoS flow to DRB mapping rule
for the QoS flow and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC
(3GPP TS 38.331 [3]) with the presence of UL SDAP header:
- store the configured UL QoS flow to DRB mapping rule for the QoS flow.
When RRC (3GPP TS 38.331 [3]) releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity
shall:
- remove the UL QoS flow to DRB mapping rule for the QoS flow.
[TS 37.324 clause 6.2.2.1]
An SDAP PDU consists only of a data field and does not consist of any SDAP header, as described in Figure 6.2.2.1-1.
ETSI
Figure 6.2.2.1-1: SDAP Data PDU format without SDAP header
[TS 37.324 clause 6.2.3]
Figure 6.2.3 – 1 shows the format of End-Marker Control PDU.
D/C R QFI Oct 1
Figure 6.2.3-1: End-Marker Control PDU
[TS 24.501 clause 6.2.5.1.3]
For PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, upon receiving an UL user data packet from the
upper layers for transmission via a PDU session, the UE shall attempt to associate the UL user data packet with:
a) the QFI of a signalled QoS rule associated with the PDU session which has a set of packet filters containing a
packet filter for UL direction matching the UL user data packet or containing a packet filter for both UL and DL
directions matching the UL user data packet; or
b) the QFI of a derived QoS rule associated with the PDU session which has the packet filter for UL direction
matching the UL user data packet;
by evaluating the QoS rules in increasing order of their precedence values until the UL user data packet is associated
with a QFI or all QoS rules are evaluated.
For PDU session of unstructured PDU session type, upon receiving an UL user data packet from the upper layers for
transmission via a PDU session, the UE shall associate the UL user data packet with the QFI of the default QoS rule
associated with the PDU session.
If the UL user data packet is associated with a QFI, the UE shall pass the QFI along the UL user data packet to the
lower layers for transmission.
NOTE: Marking of the UL user data packet with the QFI is performed by the lower layers.
If all QoS rules are evaluated and the UL user data packet is not associated with a QFI, the UE shall discard the UL user
data packet.
System Simulator:
- NR Cell 1
UE:
- None.
ETSI
Preamble:
- The UE is in 5GS state 3N-A with one PDU session active according to TS 38.508-1 [4], clause 4.4A.3, Table
4.4A.3-1 and using the message condition UE TEST LOOP MODE B active to return one UL SDAP SDU per
DL SDAP SDU. 2 DRBs are configured where DRBj is defined as default DRB. The NAS QoS rules for QoS
flows QFI = 5 and QFI = 2 are configured. The 'mappedQoS-Flows' is empty for both DRB's for SDAP layer.

U-S Message
1 The SS sends the SDAP Data PDU without <-- SDAP DL Data PDU - -
SDAP header on DRB k for QFI =2.
2 Check: Does the UE transmit SDAP Data PDU --> SDAP UL Data PDU 1 P
on DRB j, which is default DRB, with SDAP
header including QFI=2?
SDAP header on DRB j for QFI 5.
on DRB j, which is default DRB, with SDAP
header including QFI=5?
message to configure QoS Flow rules
7.1.4.2.3.2-2 shall take place.
6 The UE transmit an NR --> (RRCReconfigurationComplete) - -
SDAP header on DRB k for QFI =2.
on DRB k?
SDAP header on DRB j for QFI 5.
on DRB j, with SDAP header including QFI=5?

U-S Message
Control PDU on DRBj for QFI=2?
Table 7.1.4.2.3.2-3: Void
ETSI
Table 7.1.4.2.3.3-1: RadioBearerConfig-DRB (Preamble)

OF SEQUENCE {
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
sdap-HeaderDL absent
sdap-HeaderUL absent
defaultDRB false
}
}
according to
internal TTCN
mapping
}
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
defaultDRB true
}
}
according to
internal TTCN
mapping
}
}
}
ETSI
Table 7.1.4.2.3.3-2: RadioBearerConfig-DRB (step 5, Table 7.1.4.2.3.2-1)

OF SEQUENCE {
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
sdap-HeaderUL absent
defaultDRB false
QFI 2
}
}
}
according to
internal TTCN
mapping
}
session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
defaultDRB true
mappedQoS-FlowsToAdd Not present The 'mappedQoS-
Flows' is empty
for the DRB.
}
}
according to
internal TTCN
mapping
}
}
}
ETSI
Table 7.1.4.2.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (Preamble)

session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
as defined in Table
4.8.2.1-1
as defined in Table
4.8.2.1-4 except DQR bit
set to ‘0’
as defined in Table
4.8.2.1-5
Mapped EPS bearer contexts Not Present
as defined in Table
7.1.4.2.3.3-4
as defined in Table
7.1.4.2.3.3-5
as defined in Table
4.8.2.3-3

QFI ‘00 0001’B QFI 1
flow description
included
5QI ‘0000 1001’B 5QI 9

QFI ‘00 0010’B QFI 2
flow description
included
5QI ‘0000 0101’B 5QI 5
ETSI
8 RRC
8.1 NR RRC
8.1.1 RRC connection management procedures
8.1.1.1 Paging
8.1.1.1.1 RRC / Paging for connection / 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 a matched identity ng-5G-S-TMSI }
then { UE successfully establishes the RRC connection }
}
(3)
ensure that {
when { UE receives a Paging message including only unmatched identities }
then { UE does not resume RRC connection }
}
(4)
ensure that {
when { UE receives a Paging message including a matched identity fullI-RNTI }
then { UE successfully resumes the RRC connection }
}
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.2.3.
[TS 38.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 the UE identity allocated by upper layers:
3> forward the ue-Identity and accessType (if present) to the upper layers;
1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message:
2> if the ue-Identity included in the PagingRecord matches the UE's stored fullI-RNTI:
ETSI
3> if the UE is configured by upper layers with Access Identity 1:
4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mps-
PriorityAccess;
3> else if the UE is configured by upper layers with Access Identity 2:
4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mcs-
PriorityAccess;
3> else if the UE is configured by upper layers with one or more Access Identities equal to 11-15:
4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to
highPriorityAccess;
3> else:
4> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set to mt-
Access;
2> else if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers:
3> forward the ue-Identity to upper layers and accessType (if present) to the upper layers;
3> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'other'.
System Simulator:
- NR Cell 1
UE:
- None.
Preamble:
- The UE is in 5GS state 1N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1.
ETSI

U-S Message
only unmatched identities (incorrect ng-5G-S-
TMSI).
RRCSetupRequest message within 10s?
two unmatched identities (incorrect ng-5G-S-
TMSI) and a matched identity (correct ng-5G-
S-TMSI).
RRCSetupRequest message?
6 The UE transmit an RRCSetupComplete --> NR RRC: RRCSetupComplete - -
message including SERVICE REQUEST to 5GMM: SERVICE REQUEST
confirm the successful completion of the
connection establishment.
7-10 Steps 5 to 8 of the NR RRC_CONNECTED - - - -
procedure in TS 38.508-1 Table 4.5.4.2-3 are
executed to successfully complete the service
request procedure.
sequence that takes place if inactiveState is
configured
11 IF pc_inactiveState THEN the SS transmits an <-- NR RRC: RRCRelease - -
a1 RRCRelease message including
suspendConfig.
11a2 The SS transmits a Paging message including <-- NR RRC: Paging - -
only unmatched identities (incorrect fullI-RNTI).
11a3 Check: Does the UE transmit an --> NR RRC: RRCResumeRequest 3 F
RRCResumeRequest message within 10s?
11a4 The SS transmits a Paging message including <-- NR RRC: Paging - -
two unmatched identities (incorrect fullI-RNTI)
and a matched identity (correct fullI-RNTI).
11a5 Check: Does the UE transmit an --> NR RRC: RRCResumeRequest 4 P
RRCResumeRequest message?
11a6 The SS transmits an RRCResume message. <-- NR RRC: RRCResume - -
11a7 The UE transmits an RRCResumeComplete --> NR RRC: RRCResumeComplete - -
message.
12- Void - - - -
17
ETSI
Table 8.1.1.1.1.3.3-1: Paging (step 1, Table 8.1.1.1.1.3.2-1)

pagingRecordList SEQUENCE 3 entries
(SIZE(1..maxNrofPageRec)) OF PagingRecord {
PagingRecord[1] SEQUENCE { entry 1
ue-Identity CHOICE {
ng-5G-S-TMSI Set to the different value
from the NG-5G-S-TMSI
of the UE
}
}
of the UE
}
}
of the UE
}
}
}
}
Derivation Path: TS 38.508-1[4], Table 4.6.1-9

of the UE
}
}
of the UE
}
}
ng-5G-S-TMSI Set to the value of the
NG-5G-S-TMSI of the UE
}
}
}
}
ETSI
Table 8.1.1.1.1.3.3-3: RRCSetupRequest (step 4, Table 8.1.1.1.1.3.2-1)

RRCSetupRequest ::= SEQUENCE {
rrcSetupRequest SEQUENCE {
establishmentCause mt-Access
}
}
Table 8.1.1.1.1.3.3-4: Paging (step 11a2, Table 8.1.1.1.1.3.2-1)

fullI-RNTI Set to the different value
from the I-RNTI-Value of
the UE
}
}
the UE
}
}
the UE
}
}
}
}
ETSI
Table 8.1.1.1.1.3.3-5: Paging (step 11a4, Table 8.1.1.1.1.3.2-1)

the UE
}
}
the UE
}
}
fullI-RNTI Set to the value of the I-
RNTI-Value of the UE
}
}
}
}
8.1.1.1.2 RRC / Paging for connection / Shared network environment
(1)
with { UE in NR RRC_IDLE state having been registered in the TA of the current cell which has
broadcasted a SIB1 message including multiple PLMN identities }
ensure that {
when { UE receives a Paging message including an IE ue-Identity set to the ng-5G-S-TMSI which was
allocated to the UE during the UE registration procedure }
then { UE initiates RRCSetupRequest with ue-Identity set to ng-5G-S-TMSI-Part1 }
}
(2)
with { UE having sent RRCSetupRequest with ue-Identity set to ng-5G-S-TMSI-Part1 }
ensure that {
when { the UE receives RRCSetup message }
then { UE will set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI-Part2 in RRCSetupComplete message }
}
(3)
with { UE in NR RRC_INACTIVE state having been registered in the TA of the current cell which has
broadcasted a SIB1 message including multiple PLMN identities }
ensure that {
when { UE receives a Paging message including an IE ue-Identity set to the ng-5G-S-TMSI which was
allocated to the UE during the UE registration procedure }
then { UE releases RRC connection with release cause ‘other’ and goes to NR RRC_IDLE state }
}
Editor’s note: conformance requirements will be updated according to latest core specification.
ETSI
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.2.3,5.3.3.3
5.3.3.4 and 5.3.11, TS 24.501, clause 5.3.1.4 and 5.6.1.1 . Unless otherwise stated these are Rel-15 requirements.
[TS 38.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 the UE identity allocated by upper layers:
3> forward the ue-Identity and accessType (if present) to the upper layers;
1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message:
2> if the ue-Identity included in the PagingRecord matches the UE's stored fullI-RNTI:
2> else if the ue-Identity included in the PagingRecord matches the UE identity allocated by upper layers:
3> forward the ue-Identity to upper layers and accessType (if present) to the upper layers;
[TS 38.331, clause 5.3.3.3]
The UE shall set the contents of RRCSetupRequest message as follows:
1> set the ue-Identity as follows:
3> set the ue-Identity to ng-5G-S-TMSI-Part1;
2> else:
3> draw a 39-bit random value in the range 0..239-1 and set the ue-Identity to this value;
NOTE 1: Upper layers provide the 5G-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 RRCSetupRequest 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.6.
[TS 38.331, clause 5.3.3.4]
3> else:
ETSI
[TS 38.331, clause 5.3.11]
UE shall:
1> reset MAC;
2> stop timer T302;
1> if going to RRC_IDLE was triggered by reception of the RRCRelease message including a waitTime:
2> inform the upper layer that access barring is applicable for all access categories except categories '0' and '2'.
[TS 24.501, clause 5.3.1.4]
Upon receiving AMF paging indication from the lower layers, the UE shall transition from 5GMM-CONNECTED
mode with RRC inactive indication to 5GMM-IDLE mode over 3GPP access and handle the AMF paging same as the
paging request received in the 5GMM-IDLE mode over 3GPP access as specified in clause 5.6.1.
[TS 24.501, clause 5.6.1.1]
The UE shall invoke the service request procedure when:
a) the UE, in 5GMM-IDLE mode over 3GPP access, receives a paging request from the network;
System Simulator:
- NR Cell 1.
UE:
- None.
Preamble:
- The UE is in state 1N-A as defined in TS 38.508-1 [4], clause 4.4A on NR Cell 1 and 5G-GUTI is allocated in
REGISTRATION ACCEPT.
ETSI

U-S Message
a matched ng-5G-S-TMSI.
RRCSetupRequest message with ue-Identity
set to ng-5G-S-TMSI-Part1?
4 Check: Does the UE transmit an --> NR RRC: RRCSetupComplete 2 P
RRCSetupComplete message including ng-
5G-S-TMSI-Part2 and a SERVICE REQUEST
message and an IE selectedPLMN-Identity
corresponding to the PLMN on which the UE
has been registered to confirm the successful
completion of the connection establishment?
5-8 Steps 5 to 8 of the generic radio bearer - - - -
establishment procedure (TS 38.508-1 [4]
Table 4.5.4.2-3) are executed to successfully
complete the service request procedure.
- EXCEPTION: Steps 9a1-9b1 describe - - - -
sequence that takes place if inactiveState is
configured
9 a1 IF pc_inactiveState THEN the SS transmits an <-- NR RRC: RRCRelease - -
RRCRelease message with suspendConfig to
suspend RRC connection and move to
RRC_INACTIVE state.
9a2 Wait 5s and the SS transmits a Paging <-- NR RRC: Paging - -
message including a matched ng-5G-S-TMSI.
9a3 Check: Does the UE transmit an --> NR RRC: RRCSetupRequest 3 P
RRCSetupRequest message on the cell
specified in the test case?
9a49 Steps 3-9 of Generic procedure for checking - - - -
a10- UE is in state 5GC RRC_IDLE on a certain cell
as specified in Table 4.9.4.2.2-1 of TS 38.508-
1 [4] are performed.
9b1 ELSE the SS transmits an RRCRelease <-- NR RRC: RRCRelease - -
message
10- Void - - - -
18
Table 8.1.1.1.2.3.3-1: SIB1 (preamble and all steps, Table 8.1.1.1.2.3.2-1)

SIB1 ::= SEQUENCE {
plmn-IdentityList PLMN-IdentityInfoList
}
}
ETSI
Table 8.1.1.1.2.3.3-2: PLMN-IdentityInfoList (Table 8.1.1.1.2.3.3-1)

PLMN-IdentityInfoList ::= SEQUENCE (SIZE 1 entry
plmn-Identity[1] SEQUENCE { entry 1
mcc See Table 8.1.1.1.2.3.3- PLMN1
2A
mnc See Table 8.1.1.1.2.3.3- PLMN1
2A
}
plmn-Identity[2] SEQUENCE { entry 2
mcc See Table 8.1.1.1.2.3.3- PLMN2
2A
mnc See Table 8.1.1.1.2.3.3- PLMN2
2A
}
}
}
}
The PLMN Identity list broadcasted on the BCCH in NR Cell 1 shall be configured as defined in the table below.
Table 8.1.1.1.2.3.3-2A: PLMN Identity List broadcasted for NR 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:
Table 8.1.1.1.2.3.3-2B: definition of each PLMN code
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 EFIMSI on the test USIM card
for PLMN 1.
NOTE 3: Set to the same Mobile Country Code stored in EFIMSI on the test USIM card for PLMN 2.
ETSI
Table 8.1.1.1.2.3.3-3: RRCSetupRequest (step 2, 9a3, Table 8.1.1.1.2.3.2-1)

ng-5G-S-TMSI-Part1 ng-5G-S-TMSI-Part1 ng-5G-S-TMSI-
Part1 is rightmost
39 bits of 5G-S-
TMSI. 5G-S-TMSI
is derived from
5G-GUTI in
REGISTRATION
ACCEPT
according to TS
23.003 [34]
}
}
}
Table 8.1.1.1.2.3.3-4: RRCSetupComplete (step 4, Table 8.1.1.1.2.3.2-1)

rrc-TransactionIdentifier RRC-
TransactionIdentifier
ng-5G-S-TMSI-Value ng-5G-S-TMSI-Part2 ng-5G-S-TMSI-
Part2 is the
leftmost 9 bits of
5G-S-TMSI. 5G-
S-TMSI is derived
from 5G-GUTI in
REGISTRATION
ACCEPT
according to TS
23.003 [34]
selectedPLMN-Identity 1 or 2 PLMN1 or PLMN2
Note1
}
}
}
Note1: If RPLMN is PLMN1, UE will select PLMN1; if RPLMN is PLMN2, UE will select PLMN2
ETSI
Table 8.1.1.1.2.3.3-5: RRCRelease (step 9a1, Table 8.1.1.1.2.3.2-1)

suspendConfig SEQUENCE {
fullI-RNTI I-RNTI-Value 38.508-1[4] Table
4.6.3-64
shortI-RNTI ShortI-RNTI-Value 38.508-1[4] Table
4.6.3-170
ran-PagingCycle rf256
ran-NotificationAreaInfo CHOICE {
cellList SEQUENCE (SIZE (1.. 2 entries
maxPLMNIdentities)) OF PLMN-RAN-AreaCell {
PLMN-RAN-AreaCellList[1] SEQUENCE { entry 1
plmn-Identity PLMN1
ran-AreaCells SEQUENCE (SIZE (1..32)) OF 1 entry
CellIdentity {
CellIdentity[1] CellIdentity of NR Cell 1 entry 1
}
}
PLMN-RAN-AreaCellList[2] SEQUENCE { entry 2
plmn-Identity PLMN2
ran-AreaCells SEQUENCE (SIZE (1..32)) OF 1 entry
CellIdentity {
CellIdentity[1] CellIdentity of NR Cell 1 entry 1
}
}
}
}
t380 Not Present
nextHopChainingCount NextHopChainingCount 38.508-1[4] Table
4.6.3-83
}
}
}
}
8.1.1.2 RRC connection establishment
8.1.1.2.1 RRC connection establishment / Return to idle state after T300 expiry /
connEstFailOffsetValidity / T300 expired
(1)
with { UE in NR RRC_IDLE state having sent an RRCSetupRequest message }
ensure that {
when { the SS does not answer to the UE during T300 }
then { UE goes to RRC_IDLE state }
}
(2)
ensure that {
when { T300 has expired a consecutive connEstFailCount times on the same cell for which
connEstFailureControl is included in SIB1 for a period as indicated by connEstFailOffsetValidity }
ETSI
then { UE uses connEstFailOffset for the parameter Qoffsettemp when performing cell
reselection }
}
(3)
ensure that {
when { connEstFailOffsetValidity has expired }
then { UE stops using the parameter Qoffsettemp when performing cell reselection }
}
(4)
ensure that {
when { UE receives a short message transmitted on PDCCH using P-RNTI indicating a
systemInfoModification }
then {UE re-acquires and applies the new system information }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.3.7.
[TS 38.331, clause 5.3.3.7]
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> if the T300 has expired a consecutive connEstFailCount times on the same cell for which
connEstFailureControl is included in SIB1:
3> for a period as indicated by connEstFailOffsetValidity:
4> use connEstFailOffset for the parameter Qoffsettemp for the concerned cell when performing cell
selection and reselection according to TS 38.304 [20] and TS 36.304 [27];
NOTE: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE
implementation whether to stop using connEstFailOffset for the parameter Qoffsettemp during
connEstFailOffsetValidity for the concerned cell.
2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends;
System Simulator:
UE:
- None.
Preamble:
- The UE is in state 1N-A as defined in TS 38.508-1 [4], clause 4.4A on NR Cell 1 and 5G-GUTI is allocated in
REGISTRATION ACCEPT.
ETSI
Table 8.1.1.2.1.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the NR
described in the texts in this clause. The configuration "T0" indicates the initial conditions. Subsequent configuration
marked "T1" is applied at the points indicated in the Main behaviour description in Table 8.1.1.2.1.3.2-3.

Cell 1 Cell 3
T0 SS/PBCH dBm/SCS -78 Off
SSS EPRE
SSS EPRE
Note: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3.

T0 SS/PBCH dBm/SCS -82 Off
SSS EPRE
Qrxlevmin dBm -91+Delta(NRf1) -
SSS EPRE
Qrxlevmin dBm -91+Delta(NRf1) -100+Delta(NRf2)
ETSI

U-S Message
message.
3 The SS waits for 2s (T300 expire). - - - -
4 Check: Does UE send RRCSetupRequest in 5 --> NR RRC: RRCSetupRequest 1 F
second?
procedure step 1-8 in TS 38.508-1 [4] Table
4.9.4.2.2-1 indicate that the UE is in
RRC_IDLE?
6 SS transmits an RRCRelease message to <-- NR RRC: RRCRelease - -
release RRC connection and move the UE to
RRC_IDLE
7 The SS remove connEstFailOffset in SIB1. - - - -
8 The SS transmits a Short message on PDCCH - PDCCH (DCI 1_0): Short - -
systemInfoModification.
8A Wait for 2.1* modification period to allow the - - - -
9 Void - - - -
message.
12 The SS waits for 2s to let T300 expire. - - - -
12 The SS re-adjusts the SS levels according to - - - -
A row "T1" in table 8.1.1.2.1.3.2-1/2 and waits for
35s to allow UE to perform cell reselection.
a matched ng-5G-S-TMSI on NR Cell 1.
14 Check: Does UE send RRCSetupRequest in 5 --> NR RRC: RRCSetupRequest 2 F
second?
15 Void - - - -
16 After expiry of connEstFailOffsetValidity, the - - - -
SS waits 35s to allow UE to perform cell
reselection.
procedure step 1-9a1 in TS 38.508-1 [4] Table
18 The SS changes NR Cell 3 to high priority in - - - -
SIB4.
18 The SS changes NR cell reselection priority of - - - -
A NR Cell 3 in the SIB2 of NR Cell 3.
procedure step 1-9a1 in TS 38.508-1 [4] Table
ETSI
Table 8.1.1.2.1.3.3-1: RRCSetupRequest (steps 2 and 11, Table 8.1.1.2.1.3.2-3)

}
}
Table 8.1.1.2.1.3.3-2: SIB1 (step 7, Table 8.1.1.2.1.3.2-3)

SIB1 ::= SEQUENCE {
connEstFailureControl ConnEstFailureControl Table
8.1.1.2.1.3.3-3
}
Table 8.1.1.2.1.3.3-3: ConnEstFailureControl (Table 8.1.1.2.1.3.3-2)

ConnEstFailureControl ::= SEQUENCE {
connEstFailOffsetValidity s60
connEstFailOffset Not present Value of infinity
shall be used for
Qoffsettemp
}
Table 8.1.1.2.1.3.3-4: SIB4 (steps 18, Table 8.1.1.2.1.3.2-3)

SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE 1 entry
The entry
corresponding to
the carrier of NR
Cell 3
cellReselectionPriority 7 Higer priority than
NR Cell 1
}
}
}
ETSI
Table 8.1.1.2.1.3.3-5: SIB2 of NR Cell 3 (steps 18A, Table 8.1.1.2.1.3.2-3)

SIB2::= SEQUENCE {
SEQUENCE{
cellReselectionPriority 7 Higer priority than NR
Cell 1
}
}
8.1.1.2.2 Void
8.1.1.2.3 RRC connection establishment / RRC Reject with wait time
(1)
with { UE in NR RRC_IDLE state and has sent an RRCSetupRequest message }
ensure that {
when { UE receives an RRCReject message including an IE waitTime }
then { UE doesn't re-send RRCSetupRequest message before the waitTime is expired }
}
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.15.2.
[TS 38.331, clause 5.3.15.2]
The UE shall:
1> reset MAC and release the default MAC Cell Group configuration;
1> if waitTime is configured in the RRCReject:
2> start timer T302, with the timer value set to the waitTime;
1> if RRCReject is received in response to a request from upper layers:
2> inform the upper layer that access barring is applicable for all access categories except categories '0' and '2';
1> if RRCReject is received in response to an RRCSetupRequest:
2> inform upper layers about the failure to setup the RRC connection, upon which the procedure ends;
1> else if RRCReject is received in response to an RRCResumeRequest or an RRCResumeRequest1:
2> if resume is triggered by upper layers:
3> inform upper layers about the failure to resume the RRC connection;
2> if resume is triggered due to an RNA update:
3> set the variable pendingRnaUpdate to true;
ETSI
2> discard the current KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key derived in
accordance with 5.3.13.3;
2> suspend SRB1, upon which the procedure ends;
The RRC_INACTIVE UE shall continue to monitor paging while the timer T302 is running.
System Simulator:
- NR Cell 1
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3 and Test Loop
Function (On) with UE test loop mode B is established.
ETSI

U-S Message
1 The SS transmits one IP packet to the UE on - - - -
the DRB associated with the default PDU
session on NR Cell 1. (Note 2)
2 Wait for 1 second after the IP packet has been - - - -
transmitted in step 1. (Note 1)
on NR Cell 1.
4- Steps 1-2 of the NR RRC_CONNECTED - - - -
4A procedure in table 4.5.4.2-3 in TS 38.508-1[4]
are performed.
5 The SS responds with RRCReject message <-- NR RRC: RRCReject - -
with IE waitTime set to 10s.
RRCSetupRequest message while timer T302
is running?
7 Check: Does UE transmit RRCSetupRequest - NR RRC: RRCSetupRequest 1 P
message for sending the IP packet received in
step 1 after timer T302 expires?
8- Steps 3 to 7 of the NR RRC_CONNECTED - - - -
12 procedure in TS 38.508-1 [4] Table 4.5.4.2-3
are executed.
any order.
RRCReconfigurationComplete message on RRCReconfigurationComplete
Cell 1.
14 The UE loop backs the IP packet received in - - - -
step 1 on the DRB associated with the default
PDU session on Cell 1. (Note 2)
Note 1: The 1 second delay is used to secure that the UE has received and forwarded the IP Packet transmitted by
the SS in step 1 to the UE test loop function before the RRCRelease message is sent by the SS in step 3.
Note 2: Default PDU session type is set in the PICS pc_APN_Default_Configuration.
Table 8.1.1.2.3.3.3-1: RRCReject (step 5, table 8.1.1.2.3.3.2-1)

RRCReject ::= SEQUENCE {
rrcReject SEQUENCE {
waitTime 10 10 seconds
}
}
}
Table 8.1.1.2.3.3.3-2: CLOSE UE TEST LOOP (Preamble, Table 8.1.1.2.3.3.2-1)
Derivation Path: TS 36.508 [7], Table 4.7A-3, condition UE TEST LOOP MODE B
ETSI
Table 8.1.1.2.3.3.3-3: SERVICE REQUEST (Step 9, Table 8.1.1.2.3.3.2-1)
Derivation Path: TS 38.508-1[4], Table 4.7.1-16

Service type '0001'B data
8.1.1.2.4 RRC connection establishment / Extended and spare fields in SI
(1)
with { UE is powered on and receives system information }
ensure that {
when { UE receives an optional spare or extended field in system information that it does not
comprehend }
then { UE treats system information as if the spare or extended field were absent and system
information is not ignored, and UE establishes an RRC connection }
}
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.2.2.3.1,
10.1 and 10.3. Unless otherwise stated, these are Rel-15 requirements.
[TS 38.331, clause 5.2.2.3.1]
The UE shall:
1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or
1> if the UE is in RRC_CONNECTED while T311 is running:
2> if the UE is unable to acquire the MIB;
3> perform the actions as specified in clause 5.2.2.5;
2> else:
3> perform the actions specified in clause 5.2.2.4.1.
1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by
searchSpaceSIB1 and pagingSearchSpace and has received an indication about change of system information; or
2> if ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213 [13]) and if SIB1 acquisition is
required for the UE:
3> acquire the SIB1, which is scheduled as specified in TS 38.213 [13];
3> if the UE is unable to acquire the SIB1:
3> else:
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2.
ETSI
2> else if SIB1 acquisition is required for the UE and ssb-SubcarrierOffset indicates that SIB1 is not scheduled
in the cell:
3> perform the actions as specified in clause 5.2.2.5.
NOTE: The UE in RRC_CONNECTED is only required to acquire broadcasted SIB1 if the UE can acquire it
without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 10.1]
The generic error handling defined in the subsequent clauses applies unless explicitly specified otherwise e.g. within the
procedure specific error handling.
The UE shall consider a value as not comprehended when it is set:
- to an extended value that is not defined in the version of the transfer syntax supported by the UE;
- to a spare or reserved value unless the specification defines specific behaviour that the UE shall apply upon
receiving the concerned spare/reserved value.
The UE shall consider a field as not comprehended when it is defined:
- as spare or reserved unless the specification defines specific behaviour that the UE shall apply upon receiving the
concerned spare/reserved field.
[TS 38.331 clause 10.3]
The UE shall, when receiving an RRC message on any logical channel:
1> if the message includes a field that has a value that the UE does not comprehend:
2> if a default value is defined for this field:
3> treat the message while using the default value defined for this field;
2> else if the concerned field is optional:
3> treat the message as if the field were absent and in accordance with the need code for absence of the
concerned field;
2> else:
3> treat the message as if the field were absent and in accordance with sub-clause 10.4.
System Simulator:
- NR Cell 1.
UE:
None.
Preamble:
- The UE is switched off
ETSI

U-S Message
1 System information that includes extended and <-- RRC: SYSTEM INFORMATION - -
spare fields that the UE does not comprehend (BCCH)
is broadcasted on BCCH.
(Note 1)
3 Does the UE transmit an RRCSetupRequest --> RRCSetupRequest 1 P
message on NR Cell 1?
4 The SS transmits an RRCSetup message on <-- RRCSetup - -
Cell 1.
5 Check: Does the UE transmit an --> RRCSetupComplete 1 P
RRCSetupComplete message to confirm the 5GMM: REGISTRATION
successful completion of the connection REQUEST
establishment and initiates the registration
procedure by including the REGISTRATION
REQUEST message?
21a described in TS 38.508 Table 4.5.2.2-2 are
1 performed on NR Cell 1.
Note 1 The NR-15 in Table 4.4.3.1.2-1 Combinations of system information blocks of TS 38.508-1 [4] is used
Table 8.1.1.2.4.3.3-1: MIB (step 1, Table 8.1.1.2.4.3.2-1)

MIB ::= SEQUENCE {
spare ‘1’B In Rel-15, the lowest bit is For Rel-15
considered a spare according
to TS 38.331 [12].
}
Table 8.1.1.2.4.3.3-2: SystemInformation (step 1, Table 8.1.1.2.4.3.2-1)
Derivation Path: TS 38.508-1, Table 4.6.1-29

systemInformation SEQUENCE {
sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB))
OF CHOICE {
SIB2
SIB11-r16 In Rel-15, SIB11
is considered an
extended field
according to TS
38.331 [12].
}
}
}
}
ETSI
Table 8.1.1.2.4.3.3-3: SIB11 (Table 8.1.1.2.4.3.3-2)

SIB11-r16 ::= SEQUENCE {
measIdleConfigSIB-r16 Not Present
lateNonCriticalExtension Not Present
}
8.1.1.3 RRC release
8.1.1.3.1 RRC connection release / Redirection to another NR frequency
(1)
with { UE in NR RRC_CONNECTED state }
ensure that {
when { UE receives an RRCRelease message including an IE redirectedCarrierInfo with nr and
carrierFreq different from the frequency UE was on in RRC_CONNECTED state }
then { UE enters RRC_IDLE state on new frequency included in IE redirectedCarrierInfo }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.8.3, TS
38.304, clause 5.2.4.1.Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> delay the following actions defined in this clause 60ms from the moment the RRCRelease message was received
or optionally when lower layers indicate that the receipt of the RRCRelease message has been successfully
acknowledged, whichever is earlier;
3> the received cnType is provided to upper layers;
1> else:
[TS 38.304, clause 5.2.4.1]
ETSI
[TS 38.304, clause 5.2.6]
On transition from RRC_CONNECTED to RRC_IDLE state or RRC_INACTIVE state, UE shall attempt to camp on a
suitable cell according to redirectedCarrierInfo if included in the RRCRelease message used for this transition. If the
UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the RRCRelease
message does not contain the redirectedCarrierInfo, UE shall attempt to select a suitable cell on an NR carrier. If no
suitable cell is found according to the above, the UE shall perform cell selection using stored information in order to
find a suitable cell to camp on.
When returning to RRC_IDLE state after UE moved to RRC_CONNECTED state from camped on any cell state, UE
shall attempt to camp on an acceptable cell according to redirectedCarrierInfo, if included in the RRCRelease message.
If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the
RRCRelease message does not contain redirectedCarrierInfo UE shall attempt to select an acceptable cell on an NR
frequency. If no acceptable cell is found according to the above, the UE shall continue to search for an acceptable cell
of any PLMN in state any cell selection.
System Simulator:
- 2 cells on different NR frequencies and different tracking areas:
- NR Cell 1 (TAI-1) serving cell
- NR Cell 23 (TAI-2) suitable neighbour inter-frequency cell
- Cell power levels are selected according to 38.508-1 [4] Table 6.2.2.1-3 for FR1 or Table 6.2.2.2-2 for FR2.
NR Cell 23 is switched on after UE has registered on NR Cell 1.
UE:
- None.
Preamble:
- If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2
Table 4.4A.2-3.
- Else, the UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1
according to 38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
ETSI

U-S Message
1 The SS transmits an RRCRelease message <-- NR RRC:RRCRelease - -
(IE redirectedCarrierInfo including NR Cell 23).
2A Check: Does the UE transmits an --> NR RRC: RRCSetupRequest 1 P
RRCSetupRequest message?
2B SS transmit an RRCSetup message on on the <-- NR RRC: RRCSetup - -
NGC Cell 23.
2C Check: Does the UE transmits an --> NR RRC: RRCSetupComplete 1 -
establishment and a REGISTRATION
REQUEST message indicating "mobility
registration updating" is sent to update the
registration of the actual tracking area?
3 The SS transmits a SecurityModeCommand <-- NR RRC: SecurityModeCommand - -
message.
4 The UE transmits a SecurityModeComplete --> NR RRC: SecurityModeComplete - -
message.
5-6 Steps 4-5 of TS 38.508-1 [4] Table 4.9.5.2.2-1 - - - -
of the generic procedure are performed.
message to establish SRB2 and DRB.
procedure in TS 38.508-1[4] subclause 4.9.1
indicate that the UE is capable of exchanging
IP data on DRB#n associated with the first
PDU session?
Table 8.1.1.3.1.3.3-1: SIB4 for NR cells 1 and 23 (preamble and all steps, Table 8.1.1.3.1.3.2-1)

SIB4 ::= SEQUENCE {
interFreqCarrierFreqList SEQUENCE (SIZE 1 entry
dl-CarrierFreq Same downlink NR NR Cell 1
Cell 23
Same downlink NR NR Cell 23
Cell 1
cellReselectionPriority Not present
}
}
}
ETSI
Table 8.1.1.3.1.3.3-2: RRCRelease message (step 1, Table 8.1.1.3.1.3.2-1)

redirectedCarrierInfo CHOICE {
nr SEQUENCE {
carrierFreq ARFCN-ValueNR for NR
Cell 23 frequency
ssbSubcarrierSpacing Subcarrier spacing of
SSB for NR Cell 23
smtc SSB-MTC 38.508-1 [4] Table
4.6.3-185
}
}
}
}
}
Table 8.1.1.3.1.3.3-3: RRCReconfiguration message (step 6, Table 8.1.1.3.1.3.2-1)

RadioBearerConfig- 38.508-1 [4] Table
SRB2-DRB (n, m) 4.8.1-4
masterCellGroup CellGroupConfig-SRB2- 38.508-1 [4] Table
DRB(n, m) 4.8.1-2B
}
}
}
}
8.1.1.3.2 RRC connection release / Redirection from NR to E-UTRA
(1)
ensure that {
when { UE receives an RRCRelease message including an IE redirectionInformation with E-UTRA
frequency }
then { UE enters RRC_IDLE state on E-UTRA frequency included in IE redirectionInformation }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.3.8.3, TS
38.304, clause 5.2.6.
[TS 38.331, clause 5.3.8.3]
The UE shall:
ETSI
1> delay the following actions defined in this clause 60ms from the moment the RRCRelease message was received
or optionally when lower layers indicate that the receipt of the RRCRelease message has been successfully
acknowledged, whichever is earlier;
[TS 38.304, clause 5.2.6]
At reception of RRCRelease message to transition the UE to RRC_IDLE or RRC_INACTIVE, UE shall attempt to

camp on a suitable cell according to redirectedCarrierInfo if included in the RRCRelease message used for this
transition. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If
the RRCRelease message does not contain the redirectedCarrierInfo, UE shall attempt to select a suitable cell on an NR
carrier. If no suitable cell is found according to the above, the UE shall perform cell selection using stored information
in order to find a suitable cell to camp on.
When returning to RRC_IDLE state after UE moved to RRC_CONNECTED state from camped on any cell state, UE
shall attempt to camp on an acceptable cell according to redirectedCarrierInfo, if included in the RRCRelease message.
If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the
RRCRelease message does not contain redirectedCarrierInfo UE shall attempt to select an acceptable cell on an NR
frequency. If no acceptable cell is found according to the above, the UE shall continue to search for an acceptable cell
of any PLMN in state any cell selection.
System Simulator:
- NR Cell 1 is the serving cell. System information combination NR-6 as defined in TS 38.508 -1 [4] clause
4.4.3.1.2 is used
- E-UTRA Cell 1 is a suitable neighbour cell. System information combination 31 as defined in TS 38.508 [7],
subclause 4.4.3.1.1
- The parameters settings and power levels for NR Cell 1, E-UTRA Cell 1 are selected to ensure that camping on
NR Cell 1 is guaranteed and no cell re-selection to E-UTRA Cell 1 can take place (E -UTRA Cell 1 priority is
lower than serving NR Cell 1).
UE:
- None
Preamble:
- With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell", the UE is brought to state 1E-A,
RRC_IDLE using generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On), in
accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2.
- With E-UTRA Cell 1 and NR Cell 1 power levels set according to T0, the UE is brought to state 3N-A as
defined in TS 38.508-1 [4], clause 4.4A.2.
ETSI
Tables 8.1.1.3.2.3.2-1/ 8.1.1.3.2.3.2-1A illustrates the downlink power levels to be applied for NR Cell 1, E-UTRA Cell
1 for the test execution.

Cell 1 Cell 1
Cell- dBm/15 “Off”
T0 specific RS kHz
EPRE
SS/PBCH dBm/S -85 -
SSS EPRE CS
T1 Cell- dBm/15 -91 The power levels are such that camping on NR
specific RS kHz Cell 1 is guaranteed.
EPRE
SS/PBCH dBm/S -85 -
SSS EPRE CS
Cell- dBm/15 -91 The power levels are such that UE performs
T2 specific RS kHz deregistration on E-UTRA cell and does not
EPRE reselect NR Cell
SS/PBCH dBm/S -110 -
SSS EPRE CS

Cell 1 Cell 1
T0 Cell- dBm/15 “Off”
specific RS kHz
EPRE
SS/PBCH dBm/S -82 -
SSS EPRE CS
T1 Cell- dBm/15 -96 The power levels are such that camping on NR
specific RS kHz Cell 1 is guaranteed.
EPRE
SS/PBCH dBm/S -82 -
SSS EPRE CS
T2 Cell- dBm/15 -96 The power levels are such that UE performs
specific RS kHz deregistration on E-UTRA cell and does not
EPRE reselect NR Cell
SS/PBCH dBm/S -139 -
SSS EPRE CS

U-S Message
0 The SS changes NR Cell 1 and E-UTRA Cell 1 - - - -
level according to the row "T1" in Table
8.1.1.3.2.3.2-1A
1 SS transmits an RRCRelease message (IE <-- NR RRC: RRCRelease - -
redirectionInformation including ARFCN-
ValueEUTRA of E-UTRA Cell 1).
procedure in TS 38.508-1 Table 4.9.7.2.2-1 is
performed and the UE is camped on E-UTRAN Cell
1, with connected without release‘’?
2A SS changes NR Cell 1 SSS levels according to the - - - -
row "T2" in Table 8.1.1.3.2.3.2-1/2.
3 At the end of this test procedure sequence, the UE - - - -
is in end state E-UTRA connected
ETSI
Table 8.1.1.3.2.3.3-1 RRCRelease (step 1, Table 8.1.1.3.2.3.2-2)
Derivation Path: TS 38.508-1 table 4.6.1-16

redirectedCarrierInfo CHOICE {
eutra SEQUENCE {
eutraFrequency EARFCN of E-UTRA Cell
1
cnType epc
}
}
}
}
}
8.1.1.3.3 RRC connection release / Success / With priority information / T320 expiry
(1)
with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListNR
with higher priority frequency }
ensure that {
}
(2)
with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListNR
with higher priority frequency and timer T320 }
ensure that {
when { T320 timer expires }
then { UE discards the cell reselection priority information provided by the
cellReselectionPriorities and apply the cell reselection priority information broadcast in the
system information to perform reselection to another NR cell }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.8.3 and
TS38.304, clause 5.2.4.1, 5.2.4.2 and 5.2.4.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if the security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the
ETSI
1> else:
1> if deprioritisationReq is included:
RRCResumeRequest1:
message;
RRCRelease message;
2> else:
3> store in the UE Inactive AS Context the received suspendConfig, all current parameters configured with
RRCReconfiguration or RRCResume, the current KgNB and KRRCint keys, the ROHC state, the C-RNTI
used in the source PCell, the cellIdentity and the physical cell identity of the source PCell;
2> suspend all SRB(s) and DRB(s), except SRB0;
2> indicate PDCP suspend to lower layers of all DRBs;
3> start timer T380, with the timer value set to t380;
ETSI
2> if the RRCRelease message is including the waitTime:
3> inform the upper layer that access barring is applicable for all access categories except categories '0' and
'2';
2> indicate the suspension of the RRC connection to upper layers;
2> enter RRC_INACTIVE and perform cell selection as specified in TS 38.304 [20];
1> else
2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with the release cause 'other'.
[TS 38.331, clause 5.3.8.4]
The UE shall:
1> if T320 expires:
[TS 38.304, clause 5.2.4.1]
NAS (TS 23.122 [9]).
information.
ETSI
[TS 38.304, clause 5.2.4.1]
NAS (TS 23.122 [9]).
information.
[TS 38.304, clause 5.2.4.2]
ETSI
[TS 38.304, clause 5.2.4.5]
- A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > Thresh X, HighQ during a time interval
TreselectionRAT
- A cell of a higher priority RAT/ frequency fulfils Srxlev > Thresh X, HighP during a time interval TreselectionRAT;
and
[TS 38.304, clause 5.2.4.6]
where:

ETSI
The cells shall be ranked according to the R criteria specified above by deriving Q meas,n and Qmeas,s and calculating the R
to clause 5.2.4.4.

System Simulator:
- NR Cell 1, NR Cell 3 and NR Cell6.
- NR Cell 1 (TAI-1) serving cell.
- System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cells.
NOTE: For Cell 3 and 6 TAI is set to TAI-2
UE:
- None.
Preamble:
Table 4.4A.2-3.
Table 8.1.1.3.3.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the cells at
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.
ETSI

SS/PBCH dBm/
T0 -88 Off Off assigned to satisfy SrxlevCell 1 >
SSS EPRE SCS
Sintrasearch. (NOTE 1)
SS/PBCH dBm/ assigned to satisfy both
T1 -88 -94 -88
SSS EPRE SCS Threshx, high < SrxlevCell 3 and
Threshx, low <SrxlevCell 6.
SS/PBCH dBm/
T2 -88 Off -88 assigned to satisfy Threshx, high
SSS EPRE SCS
< SrxlevCell 6.
NOTE 1: Power level “Off” is defined in TS38.508 Table 6.2.2.1-3.
Table 8.1.1.3.3.3.2-2 Time instances of cell power level and parameter changes for FR2

SS/PBCH dBm/
T0 -82 Off Off assigned to satisfy SrxlevCell 1 >
SSS EPRE SCS
Sintrasearch. (NOTE 1)
SS/PBCH dBm/ assigned to satisfy both
T1 -82 -91 -82
SSS EPRE SCS Threshx, high < SrxlevCell 3 and
Threshx, low <SrxlevCell 6.
SS/PBCH dBm/
T2 -82 Off -82 assigned to satisfy Threshx, high
SSS EPRE SCS
< SrxlevCell 6.
NOTE 1: Power level “Off” is defined in TS38.508 Table 6.2.2.1-3.
ETSI

U-S Message
1 The SS changes NR Cell 1, NR Cell 3 and NR - - - -
Cell 6 power level according to the row "T1" in
table 8.1.1.3.3.3.2-1/2.
including the freqPriorityListNR on NR Cell 1.
2A Check: Does the UE transmits an --> NR RRC: RRCSetupRequest 1 P
RRCSetupRequest message on NR Cell3?
2B SS transmit an RRCSetup message on NR <-- NR RRC: RRCSetup - -
Cell3.
2C Check: Does the UE transmits an --> NR RRC: RRCSetupComplete 1 P
establishment and a REGISTRATION
REQUEST message indicating "mobility
registration updating" is sent to update the
registration of the actual tracking area?
3 Void
3A The SS transmits a SecurityModeCommand <-- NR RRC: SecurityModeCommand
message.
3B The UE transmits a SecurityModeComplete --> NR RRC: SecurityModeComplete
message.
3C- Steps 4-5 of TS 38.508-1 [4] Table 4.9.5.2.2-1 - - - -
3D of the generic procedure are performed.
3E The SS transmits an RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
3F The UE transmits an --> NR RRC: - -
3G Check: Does the test result of generic test - - 1 -
IP data on DRB #n associated with the first
PDU session on NR Cell 3?
3H The SS releases RRC connection. - - - -
table 8.1.1.3.3.3.2-1/2.
5-5B Steps 1-3 in TS 38.508-1 [4] Table 4.9.5.2.2-1 - - - -
are peformed on NR Cell 1.
5C The SS transmits a SecurityModeCommand <-- NR RRC: SecurityModeCommand - -
message.
5D The UE transmits a SecurityModeComplete --> NR RRC: SecurityModeComplete - -
message.
5E- Steps 4-5 in TS 38.508-1 [4] Table 4.9.5.2.2-1 - -
5F are peformed.
containing IE freqPriorityListNR to update the
cell reselection priority of NR Cell 6 and the
timer T320.
table 8.1.1.3.3.3.2-1/2.
RRCSetupRequest message within T320
running?
9 Check: After timer T320 expiry, does the UE - - 2 -
perform the Registration procedure for mobility
registration update as described in steps 1-3 of
Table 4.9.5.2.2-1 on NR Cell 6?
10 The SS transmits a SecurityModeCommand <-- NR RRC: SecurityModeCommand - -
message.
11 The UE transmits a SecurityModeComplete --> NR RRC: SecurityModeComplete - -
message.
12- Steps 4-5 of Table 4.9.5.2.2-1 of the generic - - - -
ETSI
13 procedure are performed.

procedure in TS 38.508-1 subclause 4.9.1
PDU session on NR Cell 6?
Table 8.1.1.3.3.3.3-1: RRCRelease (step 2, Table 8.1.1.3.3.3.2-3)
Derivation Path: TS 38.508 [4] Table 4.6.1-16

cellReselectionPriorities SEQUENCE {
freqPriorityListEUTRA Not present
freqPriorityListNR SEQUENCE (SIZE 3 entries
carrierFreq Same downlink ARFCN
cellReselectionSubPriority Not present
}
}
}
}
}
}
}
}
ETSI
Table 8.1.1.3.3.3.3-2: SIB4 for Cell 1 (preamble and all steps, Table 8.1.1.3.3.3.2-3)

Cell 3
}
Cell 6
}
}
}
Table 8.1.1.3.3.3.3-3: SIB4 for Cell 6 (all steps, Table 8.1.1.3.3.3.2-3)

Cell 1
}
Cell 3
}
}
}
ETSI

freqPriorityListEUTRA Not present
freqPriorityListNR SEQUENCE (SIZE 2 entries
carrierFreq ARFCN-ValueNR of NR
Cell 1
}
carrierFreq ARFCN-ValueNR of NR
Cell 6
}
}
t320 min5
}
}
}
}
Table 8.1.1.3.3.3.3-5: RRCReconfiguration message (step 3E and step 14, Table 8.1.1.3.1.3.2-1)

RadioBearerConfig- 38.508-1 [4] Table
SRB2-DRB (n, m) 4.8.1-4
masterCellGroup CellGroupConfig-SRB2- 38.508-1 [4] Table
DRB(n, m) 4.8.1-2B
}
}
}
}
ETSI
Table 8.1.1.3.3.3.3-6: SIB4 for Cell 3 (all steps, Table 8.1.1.3.3.3.2-3)

Cell 1
t-ReselectionNR 1
}
Cell 3
}
}
}
8.1.1.3.4 RRC connection release / Success / With priority information / T320 expiry / E-
UTRA
(1)
with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListEUTRA
with higher priority frequency }
ensure that {
priority EUTRA frequency }
then { UE reselects the cell which belongs to the higher priority EUTRA frequency }
}
(2)
with { UE in NR RRC_IDLE state having received an RRCRelease message with the freqPriorityListEUTRA
with higher priority frequency and timer T320 }
ensure that {
when { T320 timer expires }
then { UE discards the cell reselection priority information provided by the
cellReselectionPriorities and apply the cell reselection priority information broadcast in the
system information to perform reselection to an E-UTRA cell }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.8.3 and T
38.304, clause 5.2.4.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.8.3]
The UE shall:
ETSI
1> else:
[TS 38.304, clause 5.2.4.1]
NAS (TS 23.122 [9]).
information.
[TS 38.331, clause 5.3.8.4]
The UE shall:
1> if T320 expires:
ETSI
[TS 38.304, clause 5.2.4.2]

[TS 38.304, clause 5.2.4.5]
- A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > Thresh X, HighQ during a time interval
TreselectionRAT
- A cell of a higher priority RAT/ frequency fulfils Srxlev > Thresh X, HighP during a time interval TreselectionRAT;
and
ETSI
[TS 38.304, clause 5.2.4.6]
where:

System Simulator:
- NR Cell 1, E-UTRA Cell 1 and E-UTRA Cell 3.
- System information combination 1 as defined in TS 36.508 [7] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
ETSI
Preamble:
- With E-UTRA Cell 1 "Serving cell",E-UTRA Cell 3 "Non-suitable "Off" cell" and NR Cell 1 "Non-suitable
"Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using
generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On), in accordance with
the procedure described in TS 38.508-1 [4], clause 4.5.2. 4G GUTI and eKSI are assigned and security context
established.
[4], Table 6.2.2.1-3, the UE is brought to state 3N-A, NR RRC_ CONNECTED, in accordance with the
established.
- The UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to
38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are
Table 8.1.1.3.4.3.2-1: Time instances of cell power level and parameter changes in FR1

Cell-specific
dBm/15kHz - "off” "off”
RS EPRE
T0
SS/PBCH
dBm/SCS -88 - -
SSS EPRE
The power level values are assigned to
Cell-specific satisfy both Threshx, low < SrxlevE-UTRACell 1
dBm/15kHz - -73 -73
RS EPRE and Threshx, high <SrxlevE-UTRACell 3 but not
T1
to satisfy SrxlevNR Cell 1 < Threshserving, low
SS/PBCH
dBm/SCS -88 - -
SSS EPRE
The power level values are assigned to
Cell-specific
dBm/15kHz - "off” "off” satisfy SrxlevNR Cell 1 > Snonintrasearch. (NOTE
RS EPRE
T2 1)
SS/PBCH
dBm/SCS -88 - -
SSS EPRE
dBm/15kHz - -73 "off”
RS EPRE satisfy Threshx, high < SrxlevE-UTRA Cell 1.
T3
SS/PBCH
dBm/SCS -88 - -
SSS EPRE
NOTE 1: Power level “Off” is defined in TS36.508 [7] Table 6.2.2.1-3.

Cell-specific
dBm/15kHz - "off” "off”
RS EPRE
T0
SS/PBCH
dBm/SCS FFS - -
SSS EPRE
The power level values are assigned
to satisfy both Threshx, low < SrxlevE-
Cell-specific
dBm/15kHz - FFS FFS UTRACell 1 and Threshx, high <SrxlevE-
RS EPRE
T1 UTRACell 3 but not to satisfy SrxlevNR Cell 1
< Threshserving, low
SS/PBCH
dBm/SCS FFS - -
SSS EPRE
ETSI

Cell-specific
dBm/15kHz - "off” "off” to satisfy SrxlevNR Cell 1 > Snonintrasearch.
RS EPRE
T2 (NOTE 1)
SS/PBCH
dBm/SCS FFS - -
SSS EPRE
Cell-specific
dBm/15kHz - FFS "off” to satisfy Threshx, high < SrxlevE-UTRA Cell
RS EPRE
T3 1.
SS/PBCH
dBm/SCS FFS - -
SSS EPRE
NOTE 1: Power level “Off” is defined in TS36.508 [7] Table 6.2.2.1-3.

U-S Message
1 The SS changes NR Cell 1, E-UTRA Cell 1 - - - -
and E-UTRA Cell 3 level according to the row
"T1" in Table 8.1.1.3.4.3.2-1/2
including the freqPriorityListEUTRA on NR Cell
1.
2A Check: Does the UE transmits an --> RRC: RRCConnectionRequest 1 P
RRCConnectionRequest message on E-UTRA
cell 3?
2B SS transmits an RRCConnectionSetup RRC: RRCConnectionSetup - -
<--
message on E-UTRA cell 3.
2C Check: Does the UE transmits an --> RRC: 1 P
RRCConnectionSetupComplete message to RRCConnectionSetupComplete
confirm the successful completion of the NAS: TRACKING AREA UPDATE
connection establishment and a TRACKING REQUEST
AREA UPDATE REQUEST message is sent to
area?
3 Void
3A The SS transmits a SecurityModeCommand <-- E-UTRA RRC: - -
message. SecurityModeCommand
3B The UE transmits a SecurityModeComplete --> E-UTRA RRC: - -
message. SecurityModeComplete
3C- Steps 5-6 of TS 38.508-1 [4] Table 4.9.7.2.2-1 - - - -
3D of the generic procedure are performed.
3E The SS transmits an <-- E-UTRA RRC: - -
RRCConnectionReconfiguration message to RRCConnectionReconfiguration
establish DRB #n
3F The UE transmits an --> E-UTRA RRC: - -
RRCReconfigurationComplete message. RRCConnectionReconfigurationC
omplete
3G Void - - 1 -
3GA The SS sends one IP Packet to the UE on the - - - -
default DRB associated with the first PDU
session.
3GB The UE loop backs the IP packet received in - - 1 P
step 3GA.
3H The SS transmits an RRConnectionRelease <-- E-UTRA RRC: - -
RRCConnectionRelease
ETSI
4 The SS changes NR Cell 1, E-UTRA Cell 1 - - - -

and E-UTRA Cell 3 level according to the row
"T2" in Table 8.1.1.3.4.3.2-1/2
5 UE perform on the NR Cell 1 the mobility and - - - -
periodic registration update procedure in TS
38.508-1[4] subclause 4.9.9.2.2
5AA The SS transmits an RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
5AB The UE transmits an --> NR RRC: - -
5A Void - - 1 -
5B The SS sends one IP Packet to the UE on the - - - -
session.
5C The UE loop backs the IP packet received in - - 1 P
step 5B.
containing IE freqPriorityListEUTRA to update
the cell reselection priority of E-UTRA Cell 1
and the timer T320.
7 The SS changes power levels of NR Cell 1, E- - - - -
UTRA Cell 1 and E-UTRA Cell 3 according to
row “T3” in Table 8.1.1.3.4.3.2-1/2.
8 Check: While timer T320 is running, does the - - 2 F
UE transmit an RRCSetupRequest message?
9 Void - - 2 -
9A Check: Does the UE transmits an --> RRC: RRCConnectionRequest 2 P
RRCConnectionRequest message on E-UTRA
cell 1?
9B SS transmits an RRCConnectionSetup RRC: RRCConnectionSetup - -
<--
message on E-UTRA cell 1.
9C Check: Does the UE transmits an --> RRC: 2 P
RRCConnectionSetupComplete message to RRCConnectionSetupComplete
confirm the successful completion of the NAS: TRACKING AREA UPDATE
connection establishment and a TRACKING REQUEST
AREA UPDATE REQUEST message is sent to
area?
10 The SS transmits a SecurityModeCommand <-- E-UTRA RRC: - -
message. SecurityModeCommand
11 The UE transmits a SecurityModeComplete --> E-UTRA RRC: - -
message. SecurityModeComplete
12- Steps 5-6 of TS 38.508-1 [4] Table 4.9.7.2.2-1 - - - -
13 of the generic procedure are performed.
14 The SS transmits an <-- E-UTRA RRC: - -
RRCConnectionReconfiguration message to RRCConnectionReconfiguration
establish DRB #n
15 The UE transmits an --> E-UTRA RRC: - -
RRCReconfigurationComplete message. RRCConnectionReconfigurationC
omplete
16 Void - - 2 -
16A The SS sends one IP Packet to the UE on the - - - -
session.
16B The UE loop backs the IP packet received in - - 2 P
step 16A.
ETSI

freqPriorityListEUTRA SEQUENCE (SIZE 2 entries
carrierFreq ARFCN-ValueEUTRA for
EUTRA Cell 1 frequency
}
}
}
Cell 1 frequency
}
}
t320 Not Present
}
}
}
}
Table 8.1.1.3.4.3.3-2: SIB5 for NR cell 1 (preamble and all steps, Table 8.1.1.3.4.3.2-3)

SIB5 ::= SEQUENCE {
carrierFreqListEUTRA SEQUENCE (SIZE 2 entries
}
}
}
}
ETSI

freqPriorityListEUTRA SEQUENCE (SIZE 1 entry
carrierFreq ARFCN-ValueEUTRA of
E-UTRA Cell 1
}
}
Cell 1 frequency
}
}
t320 min5
}
}
}
}
Table 8.1.1.3.4.3.3-4: RRCConnectionReconfiguration (steps 3E and 14 Table 8.1.1.3.4.3.2-3)
Derivation Path: TS 36.508[7] Table 4.6.1-8

c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated RadioResourceConfigDe
dicated-DRB(n, m)
}
}
}
}
Table 8.1.1.3.4.3.3-5: RRCReconfiguration-SRB2-DRB (n, m) (step 5AA, Table 8.1.1.3.4.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1B
Table 8.1.1.3.4.3.3-6: REGISTRATION REQUEST (Step 5, Table 8.1.1.3.4.3.2-3)

UPDATE REQUEST 8.1.1.3.4.3.3-7
message
ETSI
Table 8.1.1.3.4.3.3-7: TRACKING AREA UPDATE REQUEST (Table 8.1.1.3.4.3.3-6)
8.1.1.3.5 Void
8.1.1.3.6 Void
8.1.1.3.7 RRC connection release / Success / Deprioritisation / Frequency / T325 expiry
(1)
ensure that {
when { UE receives an RRCRelease message including IE deprioritisationReq with
deprioritisationType indicating ‘frequency’ and a deprioritisationTimer }
then { UE considers the current frequency to be the lowest priority frequency (i.e. lower than
any of the network configured values) while T325 is running }
}
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3 and TS
38.304 clause 5.2.4.1.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if deprioritisationReq is included and the UE supports RRC connection release with deprioritisation:
[TS 38.304, clause 5.2.4.1]
RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection or SNPN selection is performed
on request by NAS (TS 23.122 [9]).
System Simulator:
- NR Cell 1 and NR Cell 3 have different tracking areas and equal priority.
ETSI
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
Table 8.1.1.3.7.3.2-1 illustrates the downlink power levels to be applied for NR 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.

SSS EPRE SCS
T1 SS/PBCH dBm/ -85 -91 The power level values are set so that RNRCell 1
SSS EPRE SCS < R NRCell 3.

T0 SS/PBCH dBm/ FFS FFS
SSS EPRE SCS
T1 SS/PBCH dBm/ FFS FFS
SSS EPRE SCS

U-S Message
on NR Cell 1 including IE deprioritisationReq.
2 SS starts timer T325. - - - -
2A The SS adjusts the SS/PBCH EPRE levels - - - -
according to row "T1" in table 8.1.1.3.7.2-1/2
4 SS waits for T325 expiry. - - - -
ETSI

deprioritisationReq SEQUENCE {
deprioritisationType frequency
deprioritisationTimer min5
}
}
}
}
8.1.1.3.7a RRC connection release / Success / Deprioritisation / NR / T325 expiry
(1)
ensure that {
when { UE receives an RRCRelease message including IE deprioritisationReq with
deprioritisationType indicating ‘nr’ and a deprioritisationTimer }
then { UE considers all frequencies of NR to be the lowest priority frequency (i.e. lower than
any of the network configured values) while T325 is running }
}
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.3.8.3 and TS
38.304 clause 5.2.4.1.
[TS 38.331, clause 5.3.8.3]
The UE shall:
1> if deprioritisationReq is included and the UE supports RRC connection release with deprioritisation:
[TS 38.304, clause 5.2.4.1]
RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection or SNPN selection is performed
on request by NAS (TS 23.122 [9]).
ETSI
8.1.1.3.7a.3 Test Description
System Simulator:
- NR Cell 1 and NR Cell 3 have different tracking areas and equal priority.
- E-UTRA Cell 1 is a lower priority cell.
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.
Table 8.1.1.3.7a.3.2-1 illustrates the downlink power levels to be applied for NR Cell 1, NR Cell 3 and E-UTRA 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
Table 8.1.1.3.7a.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter Unit NR Cell 1 NR Cell 3 E-UTRA Cell 1 Remark
T0 SS/PBCH dBm/S -88 Off -

SSS EPRE CS
Cell-specific dBm/15 - - Off
RS EPRE kHz
T1 SS/PBCH dBm/S -85 -79 - The power level values are assigned to
SSS EPRE CS satisfy SrxlevE-UTRA Cell 1> Threshx, high
Cell-specific dBm/15 - - -75
RS EPRE kHz
Table 8.1.1.3.7a.3.2-2: Time instances of cell power level and parameter changes for FR2
Parameter Unit NR Cell 1 NR Cell 3 E-UTRA Cell 1 Remark

T0 SS/PBCH dBm/S FFS FFS -
SSS EPRE CS
Cell-specific dBm/15 - - Off
RS EPRE kHz
T1 SS/PBCH dBm/S FFS FFS - The power level values are assigned to
SSS EPRE CS satisfy SrxlevE-UTRA Cell 1> Threshx, high
Cell-specific dBm/15 - - -75
RS EPRE kHz
ETSI
Table 8.1.1.3.7a.3.2-3: Main behaviour

U-S Message
according to row "T1" in table 8.1.1.3.7a.3.2-
1/2
on NR Cell 1 including IE deprioritisationReq.
3 SS starts timer T325. - - - -
UTRAN Cell 1?
5 SS waits for T325 expiry. - - - -
6 Check: Does the test result of generic test --> NR RRC: RRCSetupRequest 1 P
Table 8.1.1.3.7a.3.3-1: RRCRelease (step 2, Table 8.1.1.3.7a.3.2-3)

deprioritisationReq SEQUENCE {
deprioritisationType nr
deprioritisationTimer min5
}
}
}
}
8.1.1.4 RRC resume
8.1.1.4.1 RRC resume / Suspend-Resume / RNA update / Success / Short message for SI
update
(1)
with { UE in NR RRC_INACTIVE state, with stored shortI-RNTI and useFullResumeID is not signalled in
SIB1 }
ensure that {
when { UE receives a Paging message to resume RRC connection }
then { UE sends RRCResumeRequest message by setting resumeIdentity to the stored shortI-RNTI
value }
}
(2)
with { UE in NR RRC_INACTIVE state, with stored fullI-RNTI and useFullResumeID is signalled in
SIB1 }
ensure that {
when { UE receives a Paging message to resume RRC connection }
then { UE sends RRCResumeRequest1 message by setting resumeIdentity to the stored fullI-RNTI
value }
ETSI
(3)
ensure that {
when { UE performs cell reselection and enters an RNA not belonging to the configured ran-
NotificationAreaInfo }
then { UE shall initiate RRC connection resume procedure with cause value set to rna-Update }
}
(4)
ensure that {
then { UE re-acquires and applies the new system information about the correct prach-
ConfigurationIndex in random access to resume RRC connection }
}
References: The conformance requirements covered in the current TC is specified in: TS 38.331 clause 5.2.2.2.2,
5.2.2.3.1, 5.2.2.4.2, 5.3.8.3, 5.3.13.2, 5.3.13.3, 5.3.13.8 and 6.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.2.2.2.2]
A modification period is used, i.e. updated SI message (other than SI message for ETWS, CMAS and positioning
assistance data) is broadcasted in the modification period following the one where SI change indication is transmitted.
The modification period boundaries are defined by SFN values for which SFN mod m = 0, where m is the number of
radio frames comprising the modification period. The modification period is configured by system information. The UE
receives indications about SI modifications and/or PWS notifications using Short Message transmitted with P-RNTI
over DCI (see clause 6.5). Repetitions of SI change indication may occur within preceding modification period. SI
change indication is not applicable for SI messages containing posSIBs.
modification period if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1
and searchSpaceOtherSystemInformation, on the active BWP to monitor paging, as specified in TS 38.213 [13], clause
13.
2> apply the SI acquisition procedure as defined in sub-clause 5.2.2.3 from the start of the next modification
period.
[TS 38.331, clause 5.2.2.3.1]
The UE shall:
2> if the UE is unable to acquire the MIB;
ETSI
2> else:
3> perform the actions specified in clause 5.2.2.4.1.
2> if ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213 [13]) and if SIB1 acquisition is
required for the UE:
3> acquire the SIB1, which is scheduled as specified in TS 38.213 [13];
3> if the UE is unable to acquire the SIB1:
3> else:
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2.
2> else if SIB1 acquisition is required for the UE and ssb-SubcarrierOffset indicates that SIB1 is not scheduled
in the cell:
3> perform the actions as specified in clause 5.2.2.5.
[TS 38.331, clause 5.2.2.4.2]
1> if the cellAccessRelatedInfo contains an entry with the PLMN-Identity of the selected PLMN:
2> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, and cellIdentity for the cell as
received in the corresponding PLMN-IdentityInfo containing the selected PLMN;
1> else:
2> if the UE supports the bandwidth of the initial uplink BWP and of the initial downlink BWPs indicated in the
locationAndBandwidth fields in uplinkConfigCommon:
3> select the first frequency band in the frequencyBandList which the UE supports and for which the UE
supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present;
3> if trackingAreaCode is not provided for the selected PLMN nor the registered PLMN nor PLMN of the
equivalent PLMN list:
4> consider the cell as barred in accordance with TS 38.304 [20];
4> if intraFreqReselection is set to notAllowed:
5> consider cell re-selection to other cells on the same frequency as the barred cell as not allowed, as
specified in TS 38.304 [20];
4> else:
ETSI
5> consider cell re-selection to other cells on the same frequency as the barred cell as allowed, as
3> else:
3> forward the PLMN identity to upper layers;
3> if in RRC_INACTIVE and the forwarded information does not trigger message transmission by upper
layers:
4> if the serving cell does not belong to the configured ran-NotificationAreaInfo:
5> initiate an RNA update as specified in 5.3.13.8;
[TS 38.331, clause 5.3.8.3]
The UE shall:
RRCResumeRequest1:
message;
RRCRelease message;
2> else:
3> store in the UE Inactive AS Context the configured suspendConfig, the current KgNB and KRRCint keys, the
ROHC state, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the
source PCell, and all other parameters configured except with ReconfigurationWithSync;
[TS 38.331, clause 5.3.13.2]
The UE initiates the procedure when upper layers or AS (when responding to RAN paging or upon triggering RNA
updates while the UE is in RRC_INACTIVE) requests the resume of a suspended RRC connection.
The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before
initiating this procedure.
Upon initiation of the procedure, the UE shall:
1> if the resumption of the RRC connection is triggered by response to NG-RAN paging:
ETSI
2> select '0' as the Access Category;
2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and
one or more Access Identities provided by upper layers;
3> if the access attempt is barred, the procedure ends;
1> else if the resumption of the RRC connection is triggered by upper layers:
2> if the upper layers provide an Access Category and one or more Access Identities:
3> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access
Identities provided by upper layers;
4> if the access attempt is barred, the procedure ends;
2> set the resumeCause in accordance with the information received from upper layers;
1> else if the resumption of the RRC connection is triggered due to an RNA update as specified in 5.3.13.8:
2> if an emergency service is ongoing:
NOTE: How the RRC layer in the UE is aware of an ongoing emergency service is up to UE implementation.
3> set the resumeCause to emergency;
2> else:
2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and
one or more Access Identities to be applied as specified in TS 24.501 [23];
3> if the access attempt is barred:
4> set the variable pendingRnaUpdate to true;
4> the procedure ends;
1> release the MCG SCell(s) from the UE Inactive AS context, if stored;
1> apply the default L1 parameter values as specified in corresponding physical layer specifications, except for the
parameters for which values are provided in SIB1;
1> apply the default SRB1 configuration as specified in 9.2.1;
1> apply the default MAC Cell Group configuration as specified in 9.2.2;
1> release delayBudgetReportingConfig from the UE Inactive AS context, if stored;
1> release overheatingAssistanceConfig from the UE Inactive AS context, if stored;
1> start timer T319;
1> set the variable pendingRnaUpdate to false;
1> initiate transmission of the RRCResumeRequest message or RRCResumeRequest1 in accordance with 5.3.13.3.
ETSI
[TS 38.331, clause 5.3.13.3]
The UE shall set the contents of RRCResumeRequest or RRCResumeRequest1 message as follows:
1> if field useFullResumeID is signalled in SIB1:
2> select RRCResumeRequest1 as the message to use;
2> set the resumeIdentity to the stored fullI-RNTI value;
1> else:
2> select RRCResumeRequest as the message to use;
2> set the resumeIdentity to the stored shortI-RNTI value;
1> submit the selected message RRCResumeRequest or RRCResumeRequest1 for transmission to lower layers.
NOTE 2: Only DRBs with previously configured UP ciphering shall resume ciphering.
[TS 38.331, clause 5.3.13.8]
In RRC_INACTIVE state, the UE shall:
1> if T380 expires; or
1> if RNA Update is triggered at reception of SIB1, as specified in 5.2.2.4.2:
2> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause set to rna-Update;
1> if barring is alleviated for Access Category '8', as specified in 5.3.14.4:
2> if upper layers do not request RRC the resumption of an RRC connection, and
2> if the variable pendingRnaUpdate is set to true:
3> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause value set to rna-Update.
If the UE in RRC_INACTIVE state fails to find a suitable cell and camps on the acceptable cell to obtain limited
service as defined in TS 38.304 [20], the UE shall:
NOTE: It is left to UE implementation how to behave when T380 expires while the UE is camped neither on a
suitable nor on an acceptable cell.
[TS 38.331, clause 6.5]
Short Messages can be transmitted on PDCCH using P-RNTI with or without associated Paging message using Short
Message field in DCI format 1_0 (see TS 38.212 [17], clause 7.3.1.2.1).
Table 6.5-1 defines Short Messages. Bit 1 is the most significant bit.
ETSI
Table 6.5-1: Short Messages
Bit Short Message

1 systemInfoModification
If set to 1: indication of a BCCH modification other than SIB6, SIB7 and SIB8.
2 etwsAndCmasIndication
If set to 1: indication of an ETWS primary notification and/or an ETWS secondary notification
and/or a CMAS notification.
3 stopPagingMonitoring
This bit can be used for only operation with shared spectrum channel access and if
nrofPDCCH-MonitoringOccasionPerSSB-InPO is present.
If set to 1: indication that the UE may stop monitoring PDCCH occasion(s) for paging in this
Paging Occasion as specified in TS 38.304 [20], clause 7.1.
4–8 Not used in this release of the specification, and shall be ignored by UE if received.
System Simulator:
- NR Cell 1 is the serving cell and NR Cell 2 is a suitable neighbour intra-frequency cell.
- Cell power levels are selected according to 38.508-1 [4] Table 6.2.2.1-3 and NR Cell 2 is switched on after UE
has registered on NR Cell 1.
UE:
- None.
Preamble:
Table 4.4A.2-3.
Table 8.1.1.4.1.3.2-1 for FR1 and table 8.1.1.4.1.3.2-2 for FR2 illustrate the downlink power levels to be applied for the
Table 8.1.1.4.1.3.2-1: Cell configuration changes over time for FR1

SSS EPRE
T1 SS/PBCH dBm/SCS "Off" -94 Power level “Off” is

SSS EPRE defined in TS
38.508-1 [4] Table
6.2.2.1-3
ETSI
Table 8.1.1.4.1.3.2-2: Cell configuration changes over time for FR2

SSS EPRE
Qrxlevmin dBm - -
110+Delta( 110+Delta(N
NRf1) Rf1)
T1 SS/PBCH dBm/SCS "Off" -91 Power level “Off” is
SSS EPRE defined in TS
38.508-1 [4] Table
Qrxlevmin dBm - -
110+Delta(N 6.2.2.2-2
Rf1)
ETSI

U-S Message
- The following messages are to be observed on - - - -
NR Cell 1 unless explicitly stated otherwise
a matched identity (correct fullI-RNTI).
RRCResumeRequest message by setting
resumeIdentity to the stored shortI-RNTI
value?
message.
IP data on DRB#n associated with default
Internet PDU session?
including both fullI-RNTI and shortI-RNTI in
suspendConfig.
7 The SS changes the SIB1 of NR Cell 1 to set - - - -
the useFullResumeID to True.
8 The SS transmits a Short message on PDCCH <-- PDCCH (DCI 1_0): Short - -
9 Wait for 2.1* modification period second for the - - - -
UE to receive new system information.
(Note 1)
11 Check: Does the UE transmit an --> NR RRC: RRCResumeRequest1 2 P
RRCResumeRequest1 message by setting
resumeIdentity to the stored fullI-RNTI value?
message.
suspendConfig.
of table 8.1.1.4.1.3.2-1 for FR1 and table
8.1.1.4.1.3.2-2 for FR2.
- The following messages are to be observed on - - - -
NR Cell 2 unless explicitly stated otherwise.
RRCResumeRequest message with
resumeCause set to rna-Update on NR Cell 2
within 60s?
18 The UE transmit an RRCResumeComplete --> NR RRC: RRCResumeComplete - -
message.
IP data on DRB#n associated with default
Internet PDU session?
suspendConfig.
21- Void - - - -
22
22A The SS changes the prach-ConfigurationIndex - - - -
in the system information.
22B The SS transmits a Short message on PDCCH - PDCCH (DCI 1_0): Short - -
ETSI

23 Wait for 2.1* modification period second for the - - - -
UE to receive new system information.
(Note 1)
24 The SS transmits a Paging message including - NR RRC: Paging - -
25 Check: Does the UE transmit a random access - - 4 P
using prach-ConfigurationIndex given in step
22?
26 The UE transmits an RRCResumeRequest --> RRCResumeRequest - -
message.
27 The SS transmits an RRCResume message. <-- RRCResume - -
28 The UE transmits an RRCResumeComplete --> RRCResumeComplete - -
message.
Note 1: The modification period, expressed in number of radio frames = modificationPeriodCoeff *
defaultPagingCycle.
Derivation Path: TS 38.508-1 [4], Table 4.6.1-9 with condition NR_RRC_RESUME
Table 8.1.1.4.1.3.3-2: RRCRelease (step 6, 13, Table 8.1.1.4.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-16 with condition NR_RRC_INACTIVE

SIB1 ::= SEQUENCE {
useFullResumeID true
}
Table 8.1.1.4.1.3.3-4: Paging (step 10 and 24, Table 8.1.1.4.1.3.2-3)
Table 8.1.1.4.1.3.3-5: RRCResumeRequest (step 16, Table 8.1.1.4.1.3.2-3)

RRCResumeRequest ::= SEQUENCE {
rrcResumeRequest SEQUENCE {
resumeCause rna-Update
}
}
Table 8.1.1.4.1.3.3-6: RRCResume (step 3, 12, Table 8.1.1.4.1.3.2-3)
Table 8.1.1.4.1.3.3-7: Void
ETSI
Table 8.1.1.4.1.3.3-8: RRCResume (step 17, Table 8.1.1.4.1.3.2-3)

masterCellGroup := SEQUENCE { CellGroupConfig Table
8.1.1.4.1.3.3-10
}
}
}
Table 8.1.1.4.1.3.3-9: Void

}

}
Table 8.1.1.4.1.3.3-12: BWP-DownlinkDedicated (Table 8.1.1.4.1.3.3-11: ServingCellConfig)

pdcch-Config Not present
setup PDSCH-Config
}
}
ETSI
Table 8.1.1.4.1.3.3-13: PDSCH-Config (Table 8.1.1.4.1.3.3-12: BWP-DownlinkDedicated)

dmrs-DownlinkForPDSCH-MappingTypeA Not present
tci-StatesToAddModList SEQUENCE(SIZE (1.. 1 entry
tci-StateId 0
ssb SSB index #n SSB index of NR
Cell 2
}
}
}
}
}
Derivation Path: TS 38.508-1 [4] table 4.6.1-28

SIB1 ::= SEQUENCE {
rach-ConfigGeneric SEQUENCE {
prach-ConfigurationIndex 157
}
}
}
}
}
}
8.1.1.4.2 RRC resume / Suspend-Resume / RRC setup / T319 expiry
(1)
with { UE in NR RRC_INACTIVE state and sends RRCResumeRequest message to resume RRC Connection }
ensure that {
when { UE receives a RRCSetup message }
then { UE shall discards any stored UE Inactive AS context, suspendConfig and send
RRCSetupComplete message with ng-5G-S-TMSI-Value set to ng-5G-S-TMSI }
}
(2)
with { UE in NR RRC_INACTIVE state and sends RRCResumeRequest message to resume RRC Connection }
ensure that {
when { T319 expires }
then { UE shall release RRC connection with release cause RRC Resume failure and go to NR
RRC_IDLE state }
}
ETSI
5.3.11, 5.3.13.5 and 5.3.13.7 and TS 24.501 clause 5.3.1.4. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.3.4]
1> if the RRCSetup is received in response to an RRCResumeRequest or RRCResumeRequest1:
2> discard any stored UE Inactive AS context and suspendConfig;
2> discard any current AS security context including the K RRCenc key, the KRRCint key, the KUPint key and the
KUPenc key;
2> release radio resources for all established RBs except SRB0, including release of the RLC entities, of the
associated PDCP entities and of SDAP;
2> release the RRC configuration except for the default MAC Cell Group configuration and CCCH
configuration;
2> indicate to upper layers fallback of the RRC connection;
1> perform the cell group configuration procedure in accordance with the received masterCellGroup and as
specified in 5.3.5.5;
1> perform the radio bearer configuration procedure in accordance with the received radioBearerConfig and as
specified in 5.3.5.6;
1> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited
from another RAT;
1> stop timer T300, T301 or T319 if running;
2> perform the actions as specified in 5.3.14.4.
1> if the RRCSetup is received in response to an RRCResumeRequest, RRCResumeRequest1 or RRCSetupRequest:
2> enter RRC_CONNECTED;
2> stop the cell re-selection procedure;
1> consider the current cell to be the PCell;
3> else:
ETSI
2> set the selectedPLMN-Identity to the PLMN selected by upper layers (TS 24.501 [23]) from the PLMN(s)
included in the plmn-IdentityList in SIB1;
2> if upper layers provide the 'Registered AMF':
3> include and set the registeredAMF as follows:
4> if the PLMN identity of the 'Registered AMF' is different from the PLMN selected by the upper
layers:
5> include the plmnIdentity in the registeredAMF and set it to the value of the PLMN identity in the
'Registered AMF' received from upper layers;
4> set the amf-Identifier to the value received from upper layers;
3> include and set the guami-Type to the value provided by the upper layers;
2> if upper layers provide one or more S-NSSAI (see TS 23.003 [21]):
3> include the s-nssai-List and set the content to the values provided by the upper layers;
2> set the dedicatedNAS-Message to include the information received from upper layers;
[TS 38.331, clause 5.3.11]
UE shall:
1> reset MAC;
2> stop timer T302;
[TS 38.331, clause 5.3.13.5]
The UE shall:
1> if timer T319 expires or upon receiving Integrity check failure indication from lower layers while T319 is
running:
2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'RRC Resume
failure'.
[TS 38.331, clause 5.3.13.7]
The UE shall:
1> perform the RRC connection setup procedure as specified in 5.3.3.4.
ETSI
[TS 24.501, clause 5.3.1.4]
If the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers
that the resumption of the RRC connection has failed, and:
a) if the lower layers indicate that access barring is applicable for all access categories except categories 0 and 2,
the UE shall:
1) stay in 5GMM-CONNECTED mode with RRC inactive indication;
b) else, the UE shall:
1) enter 5GMM-IDLE mode; and
2) initiate the registration procedure for mobility and periodic registration update used for mobility (i.e. the 5GS
registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message) for
N1 NAS signalling connection recovery as specified in subclause 5.5.1.3.2.
NOTE 2: An indication from the lower layer that the RRC connection has been released with cause "RRC resume
failure" can be considered as an indication that the resumption of the RRC connection has failed.
System Simulator:
- NR Cell 1 is the serving cell.
UE:
- None.
Preamble:
ETSI

U-S Message
2 The UE transmit an RRCResumeRequest --> NR RRC: RRCResumeRequest - -
message to resume RRC Connection by
setting resumeIdentity to the stored shortI-
RNTI value?
3 The SS transmits an RRCSetup message in <-- NR RRC: RRCSetup - -
response to RRCResumeRequest message.
4 Check: Does the UE transmits an --> NR RRC: RRCSetupComplete 1 P
RRCSetupComplete message and a 5GMM: REGISTRATION
REGISTRATION REQUEST message by REQUEST
discarding any stored UE Inactive AS context
and suspendConfig, setting the ng-5G-S-
TMSI-Value to ng-5G-S-TMSI?
4A- Steps 4-5 as defined in TS 38.508-1 [4] Table - - - -
4B 4.9.5.2.2-1.
4C- Steps 5-8 as defined in TS 38.508-1 [4] Table - - - -
4F Table 4.5.4.2-3.
suspendConfig.
a matched identities (correct fullI-RNTI).
7 The UE transmits an RRCResumeRequest --> NR RRC: RRCResumeRequest - -
RNTI value?
8 The SS waits for T319 expiry. - - - -
9 Check: Does the test result of test procedure in - - 2 -
TS 38.508-1 [4] subclause 4.9.5 indicate
that the UE has performed mobility registration
on NR cell 1 started in NR RRC_IDLE?
Table 8.1.1.4.2.3.3-1: RRCRelease (preamble and step 5 in Table 8.1.1.4.2.3.2-1)

suspendConfig SEQUENCE { NR_RRC_I
NACTIVE
fullI-RNTI I-RNTI-Value
shortI-RNTI ShortI-RNTI-Value
}
}
}
}
Table 8.1.1.4.2.3.3-1a: Void
ETSI
Table 8.1.1.4.2.3.3-2: RRCResumeRequest (step 2 and 7 Table 8.1.1.4.2.3.2-1)

resumeCause mt-Access
}
}
Table 8.1.1.4.2.3.3-3: RRCSetupComplete (step 4 in Table 8.1.1.4.2.3.2-1)

ng-5G-S-TMSI-Value ng-5G-S-TMSI
}
}
}
Table 8.1.1.4.2.3.3-4: REGISTRATION REQUEST (step 4 in Table 8.1.1.4.2.3.2-1)

5GS registration type
5GS registration type value '010'B Mobility
registration
updating
Uplink data status Present but contents not
checked
Table 8.1.1.4.2.3.3-5: RRCReconfiguration (step 4E in Table 8.1.1.4.2.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 condition NR and SRB2

dedicatedNAS-MessageList Not present
}
8.1.1.4.3 Void
8.1.1.4.4 RRC resume / Suspend-Resume / RRC reconfiguration / Active MCG SCell

addition / Intra-band Contiguous CA
FFS
FFS
ETSI
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 is the SCell.
UE:
- None.
Preamble:

U-S Message
RRCResumeRequest message by setting
resumeIdentity to the stored shortI-RNTI
value?
message.
FFS
FFS

addition / Intra-band non-Contiguous CA
Same as TC 8.1.1.4.4 but applied to Intra-band non-Contiguous CA.
ETSI
Same as TC 8.1.1.4.4 with the following differences:
- CA configuration: Intra-band non-contiguous replaces Intra-band Contiguous CA

addition / Inter-band CA
Same as TC 8.1.1.4.4 but applied to Inter-band CA case.
8.1.1.4.7 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Intra-
band Contiguous CA
FFS
FFS
ETSI
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 is the PSCell, NR Cell 12 is the SCell
UE:
- None.
Preamble:

U-S Message
2 The UE transmit an RRCResumeRequest --> NR RRC: RRCResumeRequest - -
RNTI value?
3 The SS transmits an RRCSetup message in <-- NR RRC: RRCSetup - -
response to RRCResumeRequest message.
message by discarding any stored UE Inactive REQUEST
AS context and suspendConfig, setting the ng-
5G-S-TMSI-Value to ng-5G-S-TMSI?
5-6 Steps 4-5 as defined in TS 38.508-1 [4] Table - - - -
4.9.5.2.2-1.
7-8 Steps 5-6 as defined in TS 38.508-1 [4] Table - - - -
4.5.4.2-3.
9 Step 7 as defined in TS 38.508-1 [4] Table - - - -
4.5.4.2-3 and FFS.
10 Step 8 as defined in TS 38.508-1 [4] Table - - - -
4.5.4.2-3.
FFS
FFS
8.1.1.4.8 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Intra-
band non-Contiguous CA
ETSI
8.1.1.4.9 RRC resume / Suspend-Resume / RRC setup / Active SCG SCell addition / Inter-
band CA
8.1.2 RRC reconfiguration
8.1.2.1 Radio bearer establishment / reconfiguration / release
8.1.2.1.1 RRC reconfiguration / DRB / SRB / Establishment / Modification / Release /

Success
(1)
with { UE having completed the RRC connection establishment procedure}
ensure that {
ETSI
when { SS sends in sequence a SecurityModeCommand and an RRCReconfiguration message to establish a

DRB }
then { UE establishes the initial security configuration in accordance with the received
securityConfigSMC included in SecurityModeCommand and successfully completes the reconfiguration }
}
(2)
with { UE in NR RRC_CONNECTED state without SRB2 }
ensure that {
when { SS sends an RRCReconfiguration message including SRB2 configuration }
then { UE successfully establishes the signalling radio bearer }
}
(3)
ensure that {
when { UE receives an RRCReconfiguration message to reconfigure the current UE configuration of
SRB and DRB }
then { UE reconfigures the data and signalling radio bearers and sends an
RRCReconfigurationComplete message }
}
(4)
ensure that {
when { UE receives an RRCReconfiguration message including a drb-ToReleaseList }
then { for each drb-Identity release the PDCP entity and RLC entity and logical channel and
indicate release of the DRB(s) to upper layers }
}
5.3.5.6.3, 5.3.5.6.4, and 5.3.5.6.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.4.3]
The UE shall:
1> derive the KgNB key, as specified in TS 33.501 [11];
1> derive the KRRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.501 [11];
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
KRRCint key;
1> if the SecurityModeCommand message passes the integrity protection check:
2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm indicated in the
SecurityModeCommand message, as specified in TS 33.501 [11];
2> derive the KUPint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.501 [11];
2> configure lower layers to apply SRB 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;
[TS 38.331, clause 5.3.5.6.3]
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 or reconfiguration from E-UTRA PDCP to NR PDCP):
ETSI
2> establish a PDCP entity;
2> if AS security has been activated:
3> if target RAT of handover is E-UTRA/5GC, or;
3> if the UE is only connected to E-UTRA/5GC:
4> configure the PDCP entity with the security algorithms and keys (KRRCenc and KRRCint)
configured/derived as specified in TS 36.331 [10];
3> else:
4> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys
(KRRCenc and KRRCint) associated with the master key (KeNB/ KgNB) or secondary key (S-KgNB) as
indicated in keyToUse, if applicable;
2> if the current UE configuration as configured by E-UTRA in TS 36.331 [10] includes an SRB identified with
the same srb-Identity value:
3> associate the E-UTRA RLC entity and DCCH of this SRB with the NR PDCP entity;
3> release the E-UTRA PDCP entity of this SRB;
2> if the pdcp-Config is included:
3> configure the PDCP entity in accordance with the received pdcp-Config;
2> else:
3> configure the PDCP entity in accordance with the default configuration defined in 9.2.1 for the
corresponding SRB;
1> for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration:
2> if the reestablishPDCP is set:
4> configure the PDCP entity to apply the integrity protection algorithm and K RRCint key
configured/derived as specified in TS 36.331 [10], 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;
4> configure the PDCP entity to apply the ciphering algorithm and K RRCenc key configured/derived as
specified in TS 36.331 [10], i.e. the 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;
3> else:
4> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with
the master key (KeNB/KgNB) or secondary key (S-KgNB), as indicated in keyToUse , 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;
4> configure the PDCP entity to apply the ciphering algorithm and K RRCenc key associated with the master
key (KeNB/KgNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the 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;
4> re-establish the PDCP entity of this SRB as specified in TS 38.323 [5];
2> else, if the discardOnPDCP is set:
ETSI
3> trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5];
2> if the pdcp-Config is included:
3> reconfigure the PDCP entity in accordance with the received pdcp-Config.
[TS 38.331, clause 5.3.5.6.4]
The UE shall:
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is
determined by the CellGroupConfig.
[TS 38.331, clause 5.3.5.6.5]
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 including the case when full configuration option is used):
2> establish a PDCP entity and configure it in accordance with the received pdcp-Config;
2> if the PDCP entity of this DRB is not configured with cipheringDisabled:
4> configure the PDCP entity with the ciphering algorithm and K UPenc key configured/derived as
3> else:
4> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the
KUPenc key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in
keyToUse;
2> if the PDCP entity of this DRB is configured with integrityProtection:
3> configure the PDCP entity with the integrity algorithms according to securityConfig and apply the KUPint
key associated with the master (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse;
2> if an sdap-Config is included:
3> if an SDAP entity with the received pdu-Session does not exist:
4> establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1;
4> If an SDAP entity with the received pdu-Session did not exist prior to receiving this reconfiguration:
ETSI
5> indicate the establishment of the user plane resources for the pdu-Session to upper layers;
3> configure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324 [24]
and associate the DRB with the SDAP entity;
3> if the DRB was configured with the same eps-BearerIdentity either by NR or E-UTRA prior to receiving
this reconfiguration:
4> associate the established DRB with the corresponding eps-BearerIdentity;
3> else:
4> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to
upper layers;
System Simulator:
- NR Cell 1
UE:
- None
Preamble:
- If pc_IP_Ping is set to TRUE then the UE is in 5GS state 1N-A, PDU SESSION ACTIVE according to TS
38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1
ETSI

U-S Message
1 SS transmits a Paging message to the UE on the <-- NR RRC: Paging - -
appropriate paging block, and including the UE
identity in one entry of the IE pagingRecordList.
2 UE transmits an RRCSetupRequest message. --> NR RRC: - -
RRCSetupRequest
3 SS transmits an RRCSetup message <-- NR RRC: RRCSetup - -
4 The UE transmits an RRCSetupComplete to --> NR RRC: - -
confirm the successful completion of the RRCSetupComplete
connection establishment.
5 SS transmits a SecurityModeCommand message <-- NR RRC: - -
to activate AS security. SecurityModeCommand
6 Using the same slot as the SecurityModeCommand <-- NR RRC: - -
message in step 5, the SS transmits an RRCReconfiguration
RRCReconfiguration message to establish a data
radio bearer, DRB1 and signalling radio bearer,
SRB2.
7 Check: Does the UE transmit a --> NR RRC: 1 P
SecurityModeComplete message? SecurityModeComplete
8 Check: Does the UE transmit an --> NR RRC: 1,2 P
RRCReconfigurationComplete message to confirm RRCReconfigurationComple
the establishment of data radio bearer, DRB1 and te
signalling radio bearer, SRB2?
9 Void - -
10 Void - -
11 The SS transmits an RRCReconfiguration <-- NR RRC: - -
message to modify SRB and DRB configuration. RRCReconfiguration
12 Check: Does the UE transmit an --> NR RRC: 3 P
RRCReconfigurationComplete message? RRCReconfigurationComple
te
12A Check: Does the test result of generic test - - 3 -
indicate that the UE is capable of exchanging IP
data on DRB#1 established in Step 11?
12B Cause the UE to request establishment of PDU - - - -
session.(Note 1)
12C The PDU session establishment procedure as - - - -
specified in TS 38.508-1 [4] subclause 4.5A.2 takes
place.
13 The SS transmits an RRCReconfiguration <--
NR RRC: - -
message with a drb-ToReleaseList and PDU RRCReconfiguration
SESSION RELEASE COMMAND 5GMM: DL NAS
TRANSPORT
5GSM: PDU SESSION
RELEASE COMMAND
RRCReconfigurationComplete message? RRCReconfigurationComple
te
16 The UE transmits an ULInformationTransfer --> NR RRC: - -
message and a UL NAS TRASPORT containing ULInformationTransfer
PDU SESSION RELEASE COMPLETE. 5GMM: UL NAS
TRANSPORT
5GSM: PDU SESSION
RELEASE COMPLETE
NOTE 1: The request to establish a PDU session may be performed by MMI or AT Command.
ETSI
Derivation Path: TS 38.508-1, table 4.6.1-13

conditions SRB2 and
DRB1
(CONTAINING
CellGroupConfig)
}
}
}

(SIZE(1..maxLC-ID)) OF RLC-BearerConfig {
RLC-Bearer-Config[1] SEQUENCE { entry 1
logicalChannelIdentity LogicalChannelIdentity
servedRadioBearer CHOICE {
drb-Identity DRB-Identity with
condition DRB1
}
reestablishRLC Not present
RLC-Config Not present
mac-LogicalChannelConfig Not present
}
srb-Identity SRB-Identity with
condition SRB2
}
}
}
spCellConfig SEQUENCE Not present
}
ETSI

condition SRB2
(CONTAINING
CellGroupConfig)
}
}
}

condition SRB2
}
}
}
}

(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI

condition SRB2
}
reestablishRLC true
}
condition DRB1
}
reestablishRLC true
}
}
}

radioBearerConfig RadioBearerConfig
(CONTAINING
CellGroupConfig)
}
}
}

drb-ToReleaseList 1 DRB1
}
ETSI

cellGroupId 1
rlc-BearerToAddModList Not Present
rlc-BearerToReleaseList SEQUENCE 1 entry
(SIZE(1..maxLC-ID)) OF
LogicalChannelIdentity {
logicalChannelIdentity[1] LogicalChannelIdentit entry 1
y
}
mac-CellGroupConfig Not Present
tag-Config Not Present
phr-Config Not Present
physicalCellGroupConfig Not Present
rlf-TimersAndConstants Not Present
}
8.1.2.1.2 RRC reconfiguration / RRC bearer establishment / uplinkTxDirectCurrentList
(1)
ensure that {
when { UE receives a RRCReconfiguration message containing reportUplinkTxDirectCurrent }
then { UE will include the uplinkTxDirectCurrentList in RRCReconfigurationComplete message. }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.3.
[TS 38.331, clause 5.3.5.3]
1> set the content of RRCReconfigurationComplete message as follows:
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent, or;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent:
3> include the uplinkTxDirectCurrentList;
System Simulator:
- NR Cell 1.
- System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1 is used in NR cell.
ETSI
UE:
- None.
Preamble:
- The UE is in state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.

U-S Message
1 The SS transmits a RRCReconfiguration <-- NR RRC: RRCReconfiguration - -
message containing uplinkBWP-ToAddModList
IE to add BWP#1 and including
reportUplinkTxDirectCurrent IE.
2 Check: Does the UE transmit the --> NR RRC: 1 P
RRCReconfigurationComplete message RRCReconfigurationComplete
including the uplinkTxDirectCurrentList?

}
}
}
}

}
reportUplinkTxDirectCurrent-v1530 true
}
ETSI

uplinkBWP-ToAddModList SEQUENCE (SIZE 1 entry
(1..maxNrofBWPs)) OF BWP-Uplink {
BWP-Uplink[1] BWP-Uplink entry 1
TS 38.508-1 [4],
Table 4.6.3-13 to
add BWP#1
}
}
}
Table 8.1.2.1.2.3.3-4: RRCReconfigurationComplete (step 2, Table 8.1.2.1.2.3.2-1)

RRCReconfigurationComplete ::= SEQUENCE {
rrc-TransactionIdentifier Not checked
rrcReconfigurationComplete SEQUENCE {
lateNonCriticalExtension Not checked
UplinkTxDirectCurrentList SEQUENCE (SIZE 1 entry
(1..maxNrofServingCells)) OF
UplinkTxDirectCurrentCell {
UplinkTxDirectCurrentCell[1] SEQUENCE { entry 1
servCellIndex 0
UplinkTxDirectCurrentBWP SEQUENCE 2 entries
(SIZE (1..maxNrofBWPs)) OF
UplinkTxDirectCurrentBWP {
UplinkTxDirectCurrentBWP[1] SEQUENCE { entry 1
bwp-Id 0
shift7dot5kHz Not checked
txDirectCurrentLocation Any value between 0 and
3299
}
UplinkTxDirectCurrentBWP[2] SEQUENCE { entry 2
bwp-Id 1
shift7dot5kHz Not checked
txDirectCurrentLocation Any value between 0 and
3299
}
}
}
}
nonCriticalExtension Not checked
}
}
}
}
ETSI
8.1.2.1.3 Void
8.1.2.1.4 RRC reconfiguration / Dedicated RLF timer
(1)
with { UE in NR RRC_CONNECTED state configured with timers according rlf-TimersAndConstants }
ensure that {
when { UE detecting radio link failure on expiring of timer T310 }
then { UE sends an RRCReestablishmentRequest message according rlf-TimersAndConstants }
}
(2)
with { UE in NR RRC_CONNECTED state with rlf-TimersAndConstants released}
ensure that {
when { UE detecting radio link failure on expiring of timer T310 }
then { UE sends an RRCReestablishmentRequest message according ue-TimersAndConstants }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.3,
5.3.5.5, 5.3.5.5.6 and 5.3.5.5.7.
[TS 38.331 clause 5.3.5.3]
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new
configuration;
[TS 38.331 clause 5.3.5.5]
The UE performs the following actions based on a received CellGroupConfig IE:
1> if the CellGroupConfig contains the spCellConfig:
2> configure the SpCell as specified in 5.3.5.5.7;
[TS 38.331 clause 5.3.5.5.7]
The UE shall:
1> if the SpCellConfig contains the rlf-TimersAndConstants:
2> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6;
[TS 38.331 clause 5.3.5.5.6]
The UE shall:
1> if the received rlf-TimersAndConstants is set to release:
ETSI
2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants
received in SIB1;
1> else:
2> (re-)configure the value of timers and constants in accordance with received rlf-TimersAndConstants;
System Simulator:
None.
Preamble:
- The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.
Parameter Unit NR NR
Cell 1 Cell 2
SS/PBCH
T1 dBm/SCS “Off” -88
SSS EPRE
SS/PBCH
T2 dBm/SCS “-88” “Off”
SSS EPRE
Parameter Unit NR NR
Cell 1 Cell 2
SS/PBCH
T1 dBm/SCS “Off” -82
SSS EPRE
SS/PBCH
T2 dBm/SCS “-82” “Off”
SSS EPRE
ETSI

U-S Message
parameters according to the row "T1" in table
8.1.2.1.4.3.2-1 or 8.1.2.1.4.3.2-2 in order that
the radio link quality of NR Cell 1 is degraded,
and NR Cell 2 is suitable for camping.
2 Check: Does the UE send --> NR RRC: 1 P
RRCReestablishmentRequest message on NR RRCReestablishmentRequest
Cell 2 after T310 expired (ms6000)?
3 The SS transmits an RRCReestablishment <-- NR RRC: RRCReestablishment - -
message.
RRCReestablishmentComplete message. RRCReestablishmentComplete
message containing RLF-TimersAndConstants
set to release.
RRCReconfigurationComplete message. RRCReconfigurationtComplete
8.1.2.1.4.3.2-1 or 8.1.2.1.4.3.2-2 in order that
the radio link quality of NR Cell 2 is degraded,
and NR Cell 1 is suitable for camping.
Cell 1 after T310 expired (ms1000)?
9 The SS transmits RRCReestablishment <-- NR RRC: RRCReestablishment - -
message.
RRCReestablishmentComplete message. RRCReestablishmentComplete
RRCReconfigurationtComplete message. RRCReconfigurationtComplete
Table 8.1.2.1.4.3.3-1: RLF-TimersAndConstants (preamble)

RLF-TimersAndConstants ::= SEQUENCE {
t310 ms6000
n310 n20
}
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition REEST

}
}
}
}
ETSI

rlf-TimersAndConstants CHOICE {
release NULL
}
}
}
8.1.2.1.5 NR CA / RRC reconfiguration / SCell addition / modification / release / Success

band Contiguous CA
(1)
ensure that {
when { UE receives an RRCReconfiguration message containing sCellToAddModList for SCell addition }
then { UE adds the new SCell and sends an RRCReconfigurationComplete message }
}
(2)
with { UE in NR RRC_CONNECTED state with SCell configured}
ensure that {
when { UE receives an RRCReconfiguration message containing sCellToAddModList for SCell
modification }
then { UE modifies the SCell configuration and sends an RRCReconfigurationComplete message }
}
(3)
with { UE in NR RRC_CONNECTED state with SCell configured}
ensure that {
when { UE receives an RRCReconfiguration message containing sCellToReleaseList }
then { UE sends an RRCReconfigurationComplete message }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.3,
5.3.5.5.1 and 5.3.5.5.9.
[TS 38.331 clause 5.3.5.3]
ETSI
1> else:
configuration;
[TS 38.331 clause 5.3.5.5.1]
1> if the CellGroupConfig contains the sCellToReleaseList:
2> perform SCell release as specified in 5.3.5.5.8;
1> if the CellGroupConfig contains the sCellToAddModList:
2> perform SCell addition/modification as specified in 5.3.5.5.9.
[TS 38.331 clause 5.3.5.5.9]
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration
(SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and
sCellConfigDedicated;
2> configure lower layers to consider the SCell to be in deactivated state;
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell
modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated.
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 is the SCell.
None.
Preamble:
- The UE is in state 3N-A, and with UE test loop mode B active if pc_IP_Ping is set to FALSE, as defined in TS
38.508-1 [4], subclause 4.4A on NR Cell 1.
ETSI

U-S Message
1 The SS transmits an <-- NR RRC: RRCReconfiguration - -
RRCReconfigurationmessage containing an
sCellToAddModList with SCell NR Cell 3
addition,
2 Check: Does the UE transmits an --> NR RRC: 1 P
RRCReconfigurationComplete message? RRCReconfigurationtComplete
IP data on DRB1 and Cell 3?
sCellToAddModList with SCell NR Cell 3
modification.
IP data on DRB1 and Cell 3?
sCellToReleaseList with SCell NR Cell 3.
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition SCell_add

}
}
}
}
ETSI

(1..maxNrofSCells)) OF SCellConfig {
sCellConfigCommon Not present
}
}
}

firstActiveDownlinkBWP-Id Not present
firstActiveUplinkBWP-Id Not present
}
pdsch-ServingCellConfig CHOICE {
setup PDSCH-
ServingCellConfig
}
}
Table 8.1.2.5.1.1.3.3-5: PDSCH-ServingCellConfig (Table 8.1.2.5.1.1.3.3-4)

PDSCH-ServingCellConfig ::= SEQUENCE {
nrofHARQ-ProcessesForPDSCH n16
}

}
}
}
}
ETSI

sCellToAddModList Not present
sCellToReleaseList SEQUENCE (SIZE 1 entry
(1..maxNrofSCells)) OF SCellIndex {
SCellIndex[1] 1 entry 1
}
}
8.1.2.1.5.2 NR CA / RRC reconfiguration / SCell addition / modification / release / Success / Inter-

band CA
Same as TC 8.1.2.1.5.1 but applied to Inter-band CA.
Same as TC 8.1.2.1.5.1 but applied to Inter-band CA.
Same as TC 8.1.2.1.5.1 with the following differences:

band non-contiguous CA
Same as TC 8.1.2.1.5.1 but applied to Intra-band non-contiguous CA.
Same as TC 8.1.2.1.5.1 but applied to Intra-band non-contiguous CA.
ETSI
8.1.3 Measurement configuration control and reporting
8.1.3.1 Intra NR measurements
8.1.3.1.1 Measurement configuration control and reporting / Intra NR measurements /

Event A1 / Event A2
(1)
with { UE in NR RRC_CONNECTED and measurement configured for event A1 and event A2 with event based
periodical reporting }
ensure that {
when { Serving cell becomes better than absolute threshold plus hysteresis and entering condition
for event A1 is met }
then { UE sends MeasurementReport message at regular intervals while entering condition for
event A1 is satisfied }
}
(2)
with { UE in NR RRC_CONNECTED 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 }
}
(3)
with { UE in NR RRC_CONNECTED and measurement configured for event A1 and event A2 with event based
periodical reporting }
ensure that {
when { Serving cell becomes worse than absolute threshold minus hysteresis and entering condition
for event A2 is met }
}
(4)
with { UE in NR RRC_CONNECTED state and periodical measurement reporting triggered by event A2
ongoing }
ensure that {
when { Serving cell becomes better than absolute threshold plus hysteresis }
}
(5)
with { UE in NR RRC_CONNECTED and measurements are re-configured for event A1 with event based
periodical reporting to report on leaving condition }
ensure that {
when { Serving cell becomes worse than absolute threshold minus hysteresis }
then { UE sends MeasurementReport message while leaving condition for event A1 is satisfied }
}
ETSI
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.5.3, 5.5.2,
5.5.4.1, 5.5.4.2, 5.5.4.3 and 5.5.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> else:
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
1> if the received measConfig includes the measObjectToAddModList:
2> perform the measurement object addition/modification procedure as specified in 5.5.2.5;
1> if the received measConfig includes the reportConfigToAddModList:
2> perform the reporting configuration addition/modification procedure as specified in 5.5.2.7;
1> if the received measConfig includes the quantityConfig:
2> perform the quantity configuration procedure as specified in 5.5.2.8;
1> if the received measConfig includes the measIdToRemoveList:
2> perform the measurement identity removal procedure as specified in 5.5.2.2;
1> if the received measConfig includes the measIdToAddModList:
2> perform the measurement identity addition/modification procedure as specified in 5.5.2.3;
[TS 38.331, clause 5.5.4.1]
If security has been activated successfully, the UE shall:
1> for each measId included in the measIdList within VarMeasConfig:
2> if the corresponding reportConfig includes a reportType set to eventTriggered or periodical;
3> if the corresponding measObject concerns NR;
4> if the eventA1 or eventA2 is configured in the corresponding reportConfig:
ETSI
5> consider only the serving cell to be applicable;
2> if the reportType is set to eventTriggered 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 a measurement
reporting 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;
2> else if the reportType is set to eventTriggered 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 timeToTrigger defined within the
VarMeasConfig 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:
3> initiate the measurement reporting procedure, as specified in 5.5.5.
[TS 38.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;
1> for this measurement, consider the NR serving cell corresponding to the associated measObjectNR associated
with this event.
Inequality A1-1 (Entering condition)
Ms – Hys > Thresh
Inequality A1-2 (Leaving condition)
Ms + Hys < Thresh
The variables in the formula are defined as follows:
ETSI
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 reportConfigNR for this event).
Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigNR for this event).
Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.
Hys is expressed in dB.
Thresh is expressed in the same unit as Ms.
[TS 38.331, clause 5.5.4.3]
The UE shall:
1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is
fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is
fulfilled;
1> for this measurement, consider the serving cell indicated by the measObjectNR associated to this event.
Ms + Hys < Thresh
Ms – Hys > Thresh
Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigNR for this
event).
[TS 38.331, clause 5.5.5]
UE Network
MeasurementReport
Figure 5.5.5.1-1: Measurement reporting
The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this
procedure only after successful security activation.
For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within
the MeasurementReport message as follows:
ETSI
1> set the measId to the measurement identity that triggered the measurement reporting;
1> set the measResultServingCell within measResultServingMOList to include , for each NR serving cell that is
configured with servingCellMO, RSRP, RSRQ and the available SINR derived based on the rsType if indicated
in the associated reportConfig , otherwise based on SSB if available, otherwise based on CSI-RS;
1> set the measResultServingCell within measResultServingMOList to include for each NR serving cell that is
configured with servingCellMO, if any, the servCellId;
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 reportConfig for this measId:
2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding
reportConfig for this measId;
1> else:
2> if the reportType 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 UE is configured with EN-DC:
1> else:
2> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.
System Simulator:
- NR Cell 1
UE:
- None.
Preamble:
columns marked "T1" and "T2", are to be applied subsequently. The exact instants on which these values shall be
ETSI
Parameter Unit NR Remark

Cell 1
Power level is such that entry condition
SS/PBCH
T0 dBm/SCS -98 for event A2 is satisfied Ms + Hys <
SSS EPRE
Thresh
SS/PBCH for event A1 is satisfied Ms – Hys >
T1 dBm/SCS -78
SSS EPRE Thresh and exit condition for event A2
is satisfied too.
Power level is such that exit condition
SS/PBCH
T2 dBm/SCS -98 for event A1 is satisfied Ms + Hys <
SSS EPRE
Thresh
Parameter Unit NR Remark

Cell 1
SS/PBCH
T0 dBm/SCS FFS for event A2 is satisfied Ms + Hys <
SSS EPRE
Thresh
SS/PBCH for event A1 is satisfied Ms – Hys >
T1 dBm/SCS FFS
SSS EPRE Thresh and exit condition for event A2
is satisfied too.
Power level is such that exit condition
SS/PBCH
T2 dBm/SCS FFS for event A1 is satisfied Ms + Hys <
SSS EPRE
Thresh
ETSI

U-S Message
1 SS transmits an RRCReconfiguration message <-- NR RRC: RRCReconfiguration - -
including measConfig to setup intra NR
measurement and reporting for event A1 and
event A2.
RRCReconfigrationComplete message. RRCReconfigurationComplete
3 Check: Does the UE transmit a --> NR RRC: MeasurementReport 3 P
MeasurementReport message to report event
A2 with the measured RSRP, RSRQ and SINR
value for NR Cell 1?
- EXCEPTION: Step 4 below is repeated until 3 - - - -
MeasurementReport messages are received
from the UE and Interval between two
MeasurementReport is same as the IE
reportInterval configured in measConfig.
MeasurementReport message at regular
intervals, with the measured RSRP, RSRQ
and SINR value for NR Cell 1?
5 SS re-adjusts the SS/PBCH EPRE level - - - -
according to row "T1" in Table 8.1.3.1.1.3.2-
1/2.
6 Wait and ignore MeasurementReport - - - -
messages for 15 s to allow change of power
levels for NR Cell 1 and UE measurement.
executed
- EXCEPTION: Step 8 below is repeated until 3 - - - -
MeasurementReport messages are received
from the UE and Interval between two
MeasurementReport is same as the IE
reportInterval configured in measConfig.
MeasurementReport message at regular
intervals, with the measured RSRP, RSRQ
and SINR value for NR Cell 1?
1/2.
messages for 15 s to allow change of power
levels for NR Cell 1 and UE measurement.
11 Check: Does the UE transmit a - - 2 F
value for NR Cell 1 within the next 10s?
NOTE: SS ignore MeasurementReport
message for event A2.
to re-configure for event A1 with event based
periodical reporting to report on leaving
condition and release event A2.
1/2.
15 SS receive four MeasurementReport - - - -
ETSI
messages for A1 and then wait 5s.

1/2.
18 Check: Does the UE attempt to transmit - - 5 F
MeasurementReport message within the next
10s?

U-S Message
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS
ETSI
Table 8.1.3.1.1.3.3-2: MeasConfig (Table 8.1.3.1.1.3.3-1)

measObjectToAddModList SEQUENCE (SIZE (1.. 1 entry
maxNrofObjectId)) OF MeasObjectToAddMod {
MeasObjectToAddMod[1] SEQUENCE { entry 1
measObjectId 1
measObject CHOICE {
measObjectNR MeasObjectNR(57) Thres=57(-
100dBm
≤ SS-RSRP<-
99dBm)
}
}
}
reportConfigToAddModList SEQUENCE (SIZE 2 entries
(1..maxReportConfigId)) OF ReportConfigToAddMod
{
ReportConfigToAddMod[1] SEQUENCE { entry 1
reportConfigId 1
reportConfig ReportConfigNR-
EventA1
}
reportConfigId 2
EventA2
}
}
measIdToAddModList SEQUENCE (SIZE (1.. 2 entries
maxNrofMeasId)) OF MeasIdToAddMod {
MeasIdToAddMod[1] SEQUENCE { entry 1
measId 1
measObjectId 1
reportConfigId 1
{
measId 2
measObjectId 1
reportConfigId 2
{
}
quantityConfig QuantityConfig
}
Table 8.1.3.1.1.3.3-3: MeasObjectNR (Table 8.1.3.1.1.3.3-2)

MeasObjectNR ::= SEQUENCE {
ssbFrequency Downlink ARFCN of NR
cell 1 SSB
}
ETSI
Table 8.1.3.1.1.3.3-4: ReportConfigNR-EventA1 (Table 8.1.3.1.1.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-142 with condition EVENT_A1

ReportConfigNR::= SEQUENCE {
reportType CHOICE {
eventTriggered SEQUENCE {
eventId CHOICE {
eventA1 SEQUENCE { EVENT_A1
a1-Threshold CHOICE {
rsrp 69 -88dBm FR1
≤ SS-RSRP<-
87dBm
rsrp FFS FR2
}
}
}
reportAmount Infinity
}
}
}

reportType CHOICE {
eventId CHOICE {
rsrp 69 -88dBm FR1
≤ SS-RSRP<-
87dBm
rsrp 73 -84dBm FR2
≤ SS-RSRP<-
83dBm
}
}
}
reportAmount Infinity
}
}
}
ETSI
Table 8.1.3.1.1.3.3-6: QuantityConfig (Table 8.1.3.1.1.3.3-2)

QuantityConfig ::= SEQUENCE {
quantityConfigNR-List SEQUENCE (SIZE 1 entry
(1..maxNrofQuantityConfig)) OF QuantityConfigNR {
QuantityConfigNR[1] SEQUENCE { entry 1
quantityConfigCell SEQUENCE {
ssb-FilterConfig SEQUENCE {
filterCoefficientRSRP fc4
filterCoefficientRSRQ fc4
filterCoefficientRS-SINR fc4
}
}
}
}
}
Table 8.1.3.1.1.3.3-7: MeasurementReport (steps 3, 4, 7, 8, 17, Table 8.1.3.1.1.3.2-3)

MeasurementReport ::= SEQUENCE {
measurementReport SEQUENCE {
measResults SEQUENCE {
measId 2 Step 3, 4
measId 1 Step
7,8,17
measResultServingMOList SEQUENCE { 1 entry
servCellId ServCellIndex of NR Cell 1
measResultServingCell SEQUENCE {
physCellId Physical CellID of the NR Cell 1
measResult SEQUENCE {
cellResults SEQUENCE {
resultsSSB-Cell SEQUENCE {
rsrp (0..127)
rsrq (0..127)
sinr Not present
(0..127) pc_ss_SIN
R_Meas
}
}
}
}
}
}
}
}
}
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS
ETSI

measObjectToAddModList Not Present
reportConfigToAddModList SEQUENCE (SIZE 1 entry
{
reportConfigId ReportConfigId
EventA1
}
}
measIdToAddModList Not Present
measIdToRemoveList SEQUENCE (SIZE 1 entry
(1..maxNrofMeasId)) OF MeasId {
MeasId[1] 2 ebtry 1
Release event A2
}
quantityConfig Not Present
}

reportType CHOICE {
eventId CHOICE {
eventA1 SEQUENCE {
rsrp 69 -88dBm FR1
≤ SS-RSRP<-
87dBm
rsrp FFS FR2
}
reportOnLeave true
}
}
reportAmount r4
}
}
}
8.1.3.1.2 Measurement configuration control and reporting / Event A3 / Measurement of

Neighbour NR cell / Intra-frequency measurements
(1)
with { UE in NR RRC_CONNECTED state and intra-frequency measurements configured for event A3 }
ensure that {
when { Entry condition for event A3 is not met for neighbor cell }
then { UE does not send MeasurementReport }
}
(2)
with { UE in NR RRC_CONNECTED state and intra-frequency measurements configured for event A3 }
ensure that {
ETSI
when { Neighbor cell becomes offset better than serving cell }

then { UE sends MeasurementReport with correct measId for event A3 }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.5.3, 5.5.2,
[TS 38.331, clause 5.3.5.3]
1> else:
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
[TS 38.331, clause 5.5.4.1]
2> if the corresponding reportConfigincludes a reportType set to eventTriggered or periodical;
5> if a serving cell is associated with a measObjectNR and neighbors are associated with another
measObjectNR, consider any serving cell associated with the other measObjectNR to be a
neighboring cell as well;
ETSI
measId;
[TS 38.331, clause 5.5.4.4]
The UE shall:
1> use the SpCell for Mp, Ofp and Ocp.
NOTE The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this
event which may be different from the NR SpCell measObjectNR.
Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off
Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off
Mn is the measurement result of the neighboring cell, not taking into account any offsets.
Ofn is the measurement object specific offset of the reference signal of the neighbor cell (i.e. offsetMO as defined
within measObjectNR corresponding to the neighbor cell).
Ocn is the cell specific offset of the neighbor cell (i.e. cellIndividualOffset as defined within measObjectNR
corresponding to the frequency of the neighbor cell), and set to zero if not configured for the neighbor cell.
Mp is the measurement result of the SpCell, not taking into account any offsets.
Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR
corresponding to the SpCell).
Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding
to the SpCell), and is set to zero if not configured for the SpCell.
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event).
Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.
Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.
[TS 38.331, clause 5.5.5]
ETSI
UE Network
MeasurementReport
1> set the measResultServingCell within measResultServingMOList to include, for each NR serving cell that is
configured with servingCellMO, RSRP, RSRQ and the available SINR, derived based on the rsType if indicated
in the associated reportConfig, otherwise based on SSB if available, otherwise based on CSI-RS;
1> set the servCellId within measResultServingMOList to include each NR serving cell that is configured with
servingCellMO, if any;
1> if there is at least one applicable neighboring cell to report:
2> if the reportType is set to eventTriggered or periodical:
3> set the measResultNeighCells to include the best neighboring cells up to maxReportCells in accordance
with the following:
4> if the reportType is set to eventTriggered:
5> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for
this measId;
4> for each cell that is included in the measResultNeighCells, include the physCellId;
5> for each included cell, include the layer 3 filtered measured results in accordance with the
reportConfig for this measId, ordered as follows:
6> if the measObject associated with this measId concerns NR:
7> if rsType in the associated reportConfig is set to ssb:
8> set resultsSSB-Cell within the measResult to include the SS/PBCH block based
quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in
decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best
cell is included first:
ETSI
System Simulator:
- NR Cell 1 is the serving cell.
- NR Cell 2 is the intra-frequency neighbor cell.
UE:
- None.
Preamble:
- The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A.
Table 8.1.3.1.2.3.2-1 and 8.1.3.1.2.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1 and NR Cell
2 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the
configuration marked "T1" and "T2", are applied at the point indicated in the Main behaviour description in Table
8.1.3.1.2.3.2-3.
ETSI
Table 8.1.3.1.2.3.2-1: Time instances of cell power level and parameter changes for NR Cell 1 and NR
Cell 2 in FR1

Cell 1 Cell 2
Power levels are such that entry
condition for event A3 is not
SS/PBCH dBm/
T0 -85 -91 satisfied for the neighbour NR cell:
SSS EPRE SCS
Mn + Ofn + Ocn – Hys > Mp + Ofp
+ Ocp + Off
condition for event A3 is satisfied
SS/PBCH dBm/
T1 -85 -79 for intra-frequency neighbour NR
SSS EPRE SCS
cell (measId 1): Mn + Ofn + Ocn –
Hys > Mp + Ofp + Ocp + Off
Power levels are such that leaving
SS/PBCH dBm/
T2 -85 -91 (measId 1):
SSS EPRE SCS
Mn + Ofn + Ocn + Hys < Mp + Ofp
+ Ocp + Off
Table 8.1.3.1.2.3.2-2: Time instances of cell power level and parameter changes for NR Cell 1 and NR
Cell 2 in FR2

Cell 1 Cell 2
SS/PBCH dBm/
T0 FFS FFS satisfied for the neighbour NR cell:
SSS EPRE SCS
Mn + Ofn + Ocn – Hys > Mp + Ofp
+ Ocp + Off
SS/PBCH dBm/
T1 FFS FFS for intra-frequency neighbour NR
SSS EPRE SCS
cell (measId 1): Mn + Ofn + Ocn –
Hys > Mp + Ofp + Ocp + Off
SS/PBCH dBm/
T2 FFS FFS (measId 1):
SSS EPRE SCS
Mn + Ofn + Ocn + Hys < Mp + Ofp
+ Ocp + Off
ETSI

U-S Message
message including MeasConfig to setup NR
measurement and reporting for intra-frequency
event A3 (measId 1).
3 SS re-adjusts the cell-specific reference signal - - - -
level according to row "T1" in table 8.1.3.1.2.3.2-
1/2.
A3 (measId 1) with the measured RSRP value
for NR Cell 2?
5A Wait and ignore MeasurementReport messages
for 10s to allow change of power levels for NR
Cell 2 and UE measurement
level according to row "T2" in table 8.1.3.1.2.2-
1/2.
10s?
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition NR_MEAS
ETSI

MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE 1 entry
(1..maxNrofMeasId)) OF MeasObjectToAddMod {
measObjectId 1
measObject CHOICE {
measObjectNR MeasObjectNR Table
8.1.3.1.2.3.3-3
}
}
}
reportConfigToAddModList SEQUENCE(SIZE 1 entry
(1..maxReportConfigId)) OF ReportConfigToAddMod {
reportConfigId 1
reportConfig CHOICE {
reportConfigNR ReportConfigNR- Table
EventA3 8.1.3.1.2.3.3-4
}
}
}
measIdToAddModList SEQUENCE (SIZE 1 entry
(1..maxNrofMeasId)) OF MeasIdToAddMod {
measId 1
measObjectId 1
reportConfigId 1
}
}
}

MeasObjectNR::= SEQUENCE {
ssbFrequency ARFCN-ValueNR for
SSB of NR Cell 1
absThreshSS-BlocksConsolidation Not present
nrofSS-BlocksToAverage Not present
}
ETSI
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition EVENT_A3

ReportConfigNR ::= SEQUENCE {
reportType CHOICE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset CHOICE {
rsrp 2 1 dB (2*0.5 dB) FR1
FFS FR2
}
}
}
reportAmount infinity
reportQuantityCell SEQUENCE {
rsrp true
rsrq false
sinr false
}
}
}
}
ETSI
Table 8.1.3.1.2.3.3-5: MeasurementReport (step 4, Table 8.1.3.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-5A

measId 1
measResultServingMOList SEQUENCE (SIZE 1 entry Measurement
(1..maxNrofServingCells)) OF MeasResultServMO { report for NR Cell
1
MeasResultServMO[1] SEQUENCE { entry 1
physCellId PCI of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
Not checked pc_ss_SIN
R_Meas
}
}
}
}
}
}
measResultNeighCells CHOICE {
measResultListNR SEQUENCE (SIZE (1.. 1 entry Measurement
maxCellReport)) OF MeasResultNR { report for NR Cell
2
MeasResultNR[1] SEQUENCE { entry 1
physCellId Physical layer cell identity
of NR Cell 2
rsrp (0..127)
rsrq Not present
sinr Not present
}
resultsCSI-RS-Cell Not present
}
rsIndexResults Not present
}
cgi-Info Not present
}
}
}
}
}
}
}
ETSI

Neighbour NR cell / Inter-frequency measurements
(1)
with { UE in NR RRC_CONNECTED state and inter-frequency measurements configured for event A3 }
ensure that {
when { Entry condition for event A3 is not met for neighbour cell }
}
(2)
with { UE in NR RRC_CONNECTED state and inter-frequency measurements configured for event A3 }
ensure that {
when { Neighbour cell becomes offset better than serving cell }
}
Same as test case 8.1.3.1.2 with the following difference:
[TS 38.331, clause 5.5.2.9]
The UE shall:
1> if gapUE is set to setup:
2> if a per UE measurement gap configuration is already setup, release the per UE measurement gap
configuration;
2> setup the per UE measurement gap configuration indicated by the measGapConfig in accordance with the
received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following
condition:
SFN mod T = FLOOR(gapOffset/10);
subframe = gapOffset mod 10;
with T = MGRP/10 as defined in TS 38.133 [14];
2> if mgta is configured, apply the specified timing advance to the gap occurrences calculated above (i.e. the UE
starts the measurement mgta ms before the gap subframe occurrences);
Same as test case 8.1.3.1.2 with the following differences:
- Cells configuration: NR Cell 3 replaces NR Cell 2.
- System information combination: NR-4 repleaces NR-2.
ETSI

measObjectToAddModList SEQUENCE (SIZE 2 entries
measObjectId 1
measObject CHOICE {
measObjectNR MeasObjectNR-f1 Table
8.1.3.1.3.3.3-2
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.3.3.3-3
}
}
}
reportConfigId 1
EventA3 8.1.3.1.2.3.3-4
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
measGapConfig MeasGapConfig
}
Table 8.1.3.1.3.3.3-2: MeasObjectNR-f1 (Table 8.1.3.1.3.3.3-1)

SSB of NR Cell 1
}
ETSI

SSB of NR Cell 3
}

Neighbour NR cell / Inter-band measurements
(1)
with { UE in NR RRC_CONNECTED state and inter-band measurements configured for event A3 }
ensure that {
when { Entry condition for event A3 is not met for neighbour cell }
}
(2)
with { UE in NR RRC_CONNECTED state and inter-band measurements configured for event A3 }
ensure that {
when { Neighbour cell becomes offset better than serving cell }
}
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
ETSI
Specific message contents

measObjectId 1
measObject CHOICE {
8.1.3.1.4.3.3-2
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.4.3.3-3
}
}
}
reportConfigId 1
EventA3 8.1.3.1.2.3.3-4
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
}
ETSI

SSB of NR Cell 1
}

SSB of NR Cell 10
}

(1)
with { UE in NR RRC_CONNECTED state and intra-frequency measurements configured for event A4 with
event based periodical reporting }
ensure that {
when { Neighbour cell becomes better than absolute threshold }
}
(2)
ongoing }
ensure that {
when { Neighbour cell becomes worse than absolute threshold }
}
[TS 38.331, clause 5.3.5.3]
ETSI
1> else:
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
[TS 38.331, clause 5.5.4.1]
If AS security has been activated successfully, the UE shall:
4> for measurement events other than eventA1 or eventA2:
5> else:
6> consider any neighbouring cell detected based on parameters in the associated measObjectNR
to be applicable when the concerned cell is not included in the blackCellsToAddModList
defined within the VarMeasConfig for this measId;
4> else:
5> for events involving a serving cell associated with a measObjectNR and neighbours associated
with another measObjectNR, consider any serving cell associated with the other measObjectNR to
be a neighbouring cell as well;
ETSI
measId;
2> else if the reportType is set to eventTriggered 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 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;
measId;
[TS 38.331, clause 5.5.4.5]
The UE shall:
1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled.
ETSI
Mn + Ofn + Ocn – Hys > Thresh
Mn + Ofn + Ocn + Hys < Thresh
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR
corresponding to the neighbour cell).
Ocn is the measurement object specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within
measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.
Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.
Ofn, Ocn, Hys are expressed in dB.
Thresh is expressed in the same unit as Mn.
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
Figure 5.5.5-1: Measurement reporting
procedure only after successful AS security activation.
1> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available
SINR for each configured serving cell derived based on the rsType indicated in the associated reportConfig;
1> if there is at least one applicable neighbouring cell to report:
3> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance
with the following:
this measId;
ETSI
cell is included first;
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 VarMeasReportList for this
measId;
7> set results SSB-Cell within the measResult to include the SS/PBCH block based
order of decreasing trigger quantity, i.e. the best cell is included first:
1> else:
ETSI
System Simulator:
- NR Cell 1 is the serving cell, NR Cell 2 is the intra-frequency neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
configuration marked "T1" and "T2", are applied at the point indicated in the Main behaviour description in Table
8.1.3.1.5.3.2-3.

Cell 1 Cell 2
SS/PBCH dBm/ condition for event A4 (measId 1)
T0 -85 -91
SSS EPRE SCS is not satisfied:
Mn + Ofn + Ocn - Hys ≦ Thresh
T1 -85 -79
SSS EPRE SCS is satisfied:
T2 -85 -93

Cell 1 Cell 2
T0 FFS FFS is not satisfied:
SSS EPRE SCS
Mn + Ofn + Ocn - Hys ≦ Thresh
T1 FFS FFS
T2 FFS FFS
ETSI

U-S Message
event A4 (measId 1).
1/2.
- EXCEPTION: In parallel to events described in - - - -
step 4 the steps specified in table 8.1.3.1.5.3.2-4
shall take place
4 Wait for 30 seconds to ensure that the UE - - 1 -
performs a periodical intra-frequency reporting
for NR Cell 2
1/2.
6 Wait and ignore MeasurementReport messages - - - -
7 Check: Does the UE transmit a --> NR RRC: MeasurementReport 2 F
10s?

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
for NR Cell 2?
ETSI

measObjectId 1 MeasObjectIdNR
-f1
measObject CHOICE {
measObjectNR SEQUENCE {
ssbFrequency ssbFrequency IE equals
the ARFCN for NR Cell 2
}
}
}
}
reportConfigId 1
EventA4 8.1.3.1.5.3.3-3
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
}
}

reportType CHOICE {
eventId CHOICE {
eventA4 SEQUENCE {
rsrp 70 -86dBm FR1
FFS FR2
}
hysteresis 2 1 dB
}
}
rsrp true
rsrq false
sinr false
}
}
}
}
ETSI

measId 1
measResultServingMOList SEQUENCE (SIZE 1 entry Report NR Cell 1
(1..maxNrofServingCells)) OF MeasResultServMO {
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
measResultListNR SEQUENCE (SIZE (1.. 1 entry Report NR
maxCellReport)) OF OF MeasResultNR { neighbour cell
of NR Cell 2
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}
}

Same as test case 8.1.3.1.5 but applied to inter-frequency case.
ETSI
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
ETSI

measObjectId 1
measObject CHOICE {
8.1.3.1.6.3.3-2
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.6.3.3-3
}
}
}
reportConfigId 1
EventA4 8.1.3.1.5.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
}

SSB of NR Cell 1
}
ETSI

SSB of NR Cell 3
}

Same as test case 8.1.3.1.5 but applied to inter-band case.
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
ETSI

measObjectId 1
measObject CHOICE {
8.1.3.1.7.3.3-2
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.7.3.3-3
}
}
}
reportConfigId 1
EventA4 8.1.3.1.5.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
}

SSB of NR Cell 1
}
ETSI

SSB of NR Cell 10
}

(1)
with { UE in NR RRC_CONNECTED state and intra-frequency measurements configured for event A5 with
event based periodical reporting }
ensure that {
when { Serving cell becomes worse than absolute threshold1 and neighbour cell becomes better than
absolute threshold2 }
then { UE sends MeasurementReport message at regular intervals while entering conditions for
event A5 are satisfied }
}
(2)
ongoing }
ensure that {
when { Serving cell becomes better than absolute threshold1 or neighbour cell becomes worse than
absolute threshold2 }
}
[TS 38.331, clause 5.3.5.3]
1> else:
configuration;
[TS 38.331, clause 5.5.2.1]
ETSI
The UE shall:
[TS 38.331, clause 5.5.4.1]
5> if a serving cell is associated with a measObjectNR and neighbours are associated with another
neighbouring cell as well;
4> else:
measId;
ETSI
measId;
measId;
[TS 38.331, clause 5.5.4.6]
The UE shall:
1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as
specified below, are fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least
one of the two, as specified below, is fulfilled;
1> use the SpCell for Mp.
NOTE: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the
measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell.
Inequality A5-1 (Entering condition 1)
Mp + Hys < Thresh1
Mn + Ofn + Ocn – Hys > Thresh2
Inequality A5-3 (Leaving condition 1)
ETSI
Mp – Hys > Thresh1
Mn + Ofn + Ocn + Hys < Thresh2
Mp is the measurement result of the NR SpCell, not taking into account any offsets.
Mn is the measurement result of the neighbouring cell/SCell, not taking into account any offsets.
Ofn is the measurement object specific offset of the neighbour/SCell cell (i.e. offsetMO as defined within
measObjectNR corresponding to the neighbour cell/SCell).
Ocn is the cell specific offset of the neighbour cell/SCell (i.e. cellIndividualOffset as defined within measObjectNR
corresponding to the neighbour cell/SCell), and set to zero if not configured for the neighbour cell.
Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigNR for this
event).
event).
Thresh1is expressed in the same unit as Mp.
Thresh2 is expressed in the same unit as Mn.
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
configured with servingCellMO, RSRP, RSRQ and the available SINR derived based on the rsType if indicated
in the associated reportConfig, otherwise based on SSB if available, otherwise based on CSI-RS; for each
configured serving cell derived based on the rsType indicated in the associated reportConfig;
set the servCellId within measResultServingMOList to include each NR serving cell that is configured with
ETSI
with the following:
this measId;
the following:
measId;
ETSI
1> else:
System Simulator:
- NR Cell 1 is the PCell, NR Cell 2 is the intra-frequency neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
2at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the
configuration marked "T1" and "T2"are applied at the point indicated in the Main behaviour description in Table
8.1.3.1.8.3.2-3.

Cell 1 Cell 2
condition for event A5 (measId 1) is
SS/PBCH dBm/
T0 -85 -91 not satisfied:
SSS EPRE SCS
Mp + Hys ≥ Thresh1 or Mn + Ofn +
Ocn + Hys ≤ Thresh2
SS/PBCH dBm/
T1 -85 -79 satisfied:
SSS EPRE SCS
Mp + Hys < Thresh1 and Mn + Ofn
+ Ocn - Hys > Thresh2
SS/PBCH dBm/
SSS EPRE SCS
Mp - Hys > Thresh1 or Mn + Ofn +
Ocn + Hys < Thresh2
ETSI

Cell 1 Cell 2
SS/PBCH dBm/
T0 FFS FFS not satisfied:
SSS EPRE SCS
Mp + Hys ≥ Thresh1 or Mn + Ofn +
Ocn + Hys ≤ Thresh2
SS/PBCH dBm/
T1 FFS FFS satisfied:
SSS EPRE SCS
Mp + Hys < Thresh1 and Mn + Ofn
+ Ocn – Hys > Thresh2
SS/PBCH dBm/
SSS EPRE SCS
Mp – Hys > Thresh1 or Mn + Ofn +
Ocn + Hys < Thresh2

U-S Message
event A5 (measId 1)
1/2.
- EXCEPTION: In parallel to events described in - - - -
step 4 the steps specified in table 8.1.3.1.8.3.2-4
shall take place
4 Wait for 30 seconds to ensure that the UE - - 1 -
performs a periodical intra-frequency reporting
for NR Cell 2
1/2.
10s?

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
1 Check: Does the UE transmit a --> MeasurementReport 1 P
for NR Cell 2?
ETSI

-f1
measObject CHOICE {
}
}
}
}
reportConfigId 1
EventA5 8.1.3.1.8.3.3-3
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
}
}
ETSI

reportType CHOICE {
eventId CHOICE {
eventA5 SEQUENCE {
a5-Threshold1 CHOICE {
rsrp 76 -80dBm FR1
FFS FR2
}
rsrp 70 -86dBm FR1
FFS FR2
}
}
}
rsrp true
rsrq false
sinr false
}
}
}
}
ETSI

measId 1
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
measResultListNR SEQUENCE (SIZE (1.. 1 entry Report NR
maxCellReport)) OF MeasResultNR { neighbour cell
of NR Cell 2
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}
}

Same as test case 8.1.3.1.8 but applied to inter-frequency case.
ETSI
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
ETSI

measObjectId 1
measObject CHOICE {
8.1.3.1.9.3.3-2
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.9.3.3-3
}
}
}
reportConfigId 1
EventA5 8.1.3.1.8.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
}

SSB of NR Cell 1
}
ETSI

SSB of NR Cell 3
}

Same as test case 8.1.3.1.8 but applied to inter-band case.
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
ETSI

measObjectId 1
measObject CHOICE {
8.1.3.1.10.3.3-2
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.10.3.3-3
}
}
}
reportConfigId 1
EventA5 8.1.3.1.8.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
}

SSB of NR Cell 1
}
ETSI

SSB of NR Cell 10
}

simultaneous events A3 (intra and inter-frequency measurements) / RSRQ based
measurements
(1)
with { UE in NR RRC_CONNECTED state, measurements configured for two event A3 at the same time and
triggerQuantity set to rsrq }
ensure that {
when { Entry condition for event A3 is not met }
}
(2)
triggerQuantity set to rsrq }
ensure that {
when { Neighbour becomes offset better than serving }
}
5.5.2.1, 5.5.2.9, 5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 38.331, clause 5.3.5.3]
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
1> if the received measConfig includes the measGapConfig:
2> perform the measurement gap configuration procedure as specified in 5.5.2.9;
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
- SFN mod T = FLOOR(gapOffset/10);
- subframe = gapOffset mod 10;
- with T = MGRP/10 as defined in TS 38.133 [14];
[TS 38.331, clause 5.5.4.1]
4> else:
5> if useWhiteCellList is set to TRUE:
ETSI
5> else:
6> consider any neighbouring cell detected based on parameters in the associated measObjectNRto
be applicable when the concerned cell is not included in the blackCellsToAddModList defined
within the VarMeasConfig for this measId;
measId;
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 reportType is set to eventTriggered 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;
…3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:
[TS 38.331, clause 5.5.4.4]
The UE shall:
ETSI
Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined
within measObjectNR corresponding to the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
ETSI
with the following:
this measId;
1> else:
System Simulator:
- NR Cell 1 is the serving cell, NR Cell 2 is the intra-frequency neighbour cell, and NR Cell 3 is the inter-
frequency neighbour cell.
UE:
- None.
Preamble:
ETSI
Table 8.1.3.1.11.3.2-1 and 8.1.3.1.11.3.2-2 illustrate the downlink power levels to be applied for NR Cell 1, NR Cell 2
and NR Cell 3 at various time instants of the test execution for FR1 and FR2 respectively. 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) (DL only)
T0 SS/PBCH dBm/S -88 -100 "Off" Power levels are such that entry condition for
SSS EPRE CS event A3 (measId 1 & 2) is not satisfied:Mn +
SS-RSRQ dB -11.74 -17.74 - Ofn + Ocn – Hys < Mp + Ofp + Ocp + Off
Noc dBm/S -94 -
CS
T1 SS/PBCH dBm/S -88 -88 "Off" Power levels are such that entry condition for
SSS EPRE CS event A3 (measId 1) is satisfied:
SS-RSRQ dB -11.74 -11.74 - Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp +
Off
Noc dBm/S -94 -
CS
T2 SS/PBCH dBm/S -88 "Off" -88 Power levels are such that entry condition for
SSS EPRE CS event A3 (measId 2) is satisfied:
SS-RSRQ dB -11.74 - -11.74 Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp +
Off
Noc dBm/S -94 -94
CS
NOTE 1: The total tolerance used is the sum of downlink signal level uncertainty (TS 38.508-1 Table 6.2.2.1-4) and
absolute UE measurement accuracy (TS 38.133 clause 10).

(DL only) (DL only)
T0 SS/PBCH dBm/S FFS FFS "Off" Power levels are such that entry condition
SSS EPRE CS for event A3 (measId 1 & 2) is not satisfied:
RSRQ dB FFS FFS - Mn + Ofn + Ocn – Hys < Mp + Ofp + Ocp +
Noc dBm/S FFS FFS Off
CS
T1 SS/PBCH dBm/S FFS FFS "Off" Power levels are such that entry condition
SSS EPRE CS for event A3 (measId 1) is satisfied:
RSRQ dB FFS FFS - Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp +
Off
Noc dBm/S FFS FFS
CS
T2 SS/PBCH dBm/S FFS "Off" FFS Power levels are such that entry condition
SSS EPRE CS for event A3 (measId 2) is satisfied:
RSRQ dB FFS - FFS Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp +
Off
Noc dBm/S FFS FFS
CS
NOTE 1: The total tolerance used is the sum of downlink signal level uncertainty (TS 38.508-1 Table 6.2.2.2-TBD) and
ETSI

U-S Message
message on NR Cell 1 including MeasConfig
to setup NR measurement and reporting for
two event A3 (measId 1 and measId 2) (intra
and inter frequency measurement).
NR Cell 1.
MeasurementReport message on NR Cell 1
within the next 10s?
4 The SS re-adjusts the cell-specific reference - - - -
signal level according to row "T1" in Table
8.1.3.1.11.3.2-1/2.
MeasurementReport message on NR Cell 1 to
report event A3 (measId 1) with the measured
RSRP and RSRQ values for NR Cell 2?
8.1.3.1.11.3.2-1/2.
RSRP and RSRQ values for NR Cell 3?
Derivation Path: TS 38.508-1 [4] table 4.6.1-13 with condition NR_MEAS
ETSI
Table 8.1.3.1.11.3.3-2: MeasConfig (step 1, Table 8.1.3.1.11.3.2-3)
Derivation Path: TS 38.508-1[4] table 4.6.3-69

measObjectId 1
measObject CHOICE {
8.1.3.1.11.3.3-
3
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.11.3.3-
4
}
}
}
reportConfigNR ReportConfigNR-A3 Table
8.1.3.1.11.3.3-
5
}
}
}
measIdToAddModList SEQUENCE (SIZE 2 entries
measId 1
measObjectId 1
}
measId 2
measObjectId 2
}
}
}

Cell 1 SSB
}
ETSI

Cell 3 SSB
}
Table 8.1.3.1.11.3.3-5: ReportConfigNR-A3 (Table 8.1.3.1.11.3.3-2)
Derivation Path: TS 38.508-1 [4] table 4.6.3-142 with condition EVENT_A3

reportType CHOICE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset CHOICE {
rsrq -6 Actual value = -3dB
}
hysteresis 0 Actual value = 0dB
}
}
reportAmount r1
}
}
}
Table 8.1.3.1.11.3.3-6: Void
ETSI
Table 8.1.3.1.11.3.3-7: MeasurementReport (steps 5 and 7, Table 8.1.3.1.11.3.2-3)
Derivation Path: TS 38.508-1 [4] , table 4.6.1-5A

measId 1 Step 5
2 Step 7
measResultServingMOList SEQUENCE (SIZE 1 entry Step 5
servCellId ServCellIndex of NR
Cell 1
physCellId PhysCellId of NR Cell
1
rsrp (0..127)
rsrq (0..127)
sinr (0..127) pc_ss_SINR_Meas
Not present
}
}
}
}
}
}
measResultListNR SEQUENCE (SIZE 1 entry
(1..maxCellReport)) OF MeasResultNR {
physCellId PhysCellId of NR Cell Step 5
2
PhysCellId of NR Cell Step 7
3
rsrp (0..127)
rsrq (0..127)
Not present
}
}
}
}
}
}
}
}
}
}
ETSI

simultaneous events A5 (intra and inter-frequency measurements) / SINR based
measurements
(1)
triggerQuantity set to sinr }
ensure that {
}
(2)
triggerQuantity set to sinr }
ensure that {
when { SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 }
}
5.5.2.1, 5.5.2.9, 5.5.4.1, 5.5.4.4 and 5.5.5.
[TS 38.331, clause 5.3.5.3]
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
[TS 38.331, clause 5.5.4.1]
4> else:
5> else:
ETSI
measId;
event):
measId;
measId;
[TS 38.331, clause 5.5.4.4]
The UE shall:
1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as
1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least
1> use the SpCell for Mp.
NOTE: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the
measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell.
Mp + Hys < Thresh1
ETSI
Mp is the measurement result of the NR SpCell, not taking into account any offsets.
Mn is the measurement result of the neighbouring cell/SCell, not taking into account any offsets.
Ofn is the measurement object specific offset of the neighbour/SCell cell (i.e. offsetMO as defined within
measObjectNR corresponding to the neighbour cell/SCell).
Ocn is the cell specific offset of the neighbour cell/SCell (i.e. cellIndividualOffset as defined within measObjectNR
corresponding to the neighbour cell/SCell), and set to zero if not configured for the neighbour cell.
event).
event).
Thresh1is expressed in the same unit as Mp.
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
with the following:
ETSI
this measId;
...
...
1> else:
System Simulator:
- NR Cell 1 is the serving cell, NR Cell 2 is the intra-frequency neighbour cell, and NR Cell 3 is the inter-
frequency neighbour cell.
UE:
- None.
Preamble:
Table 8.1.3.1.12.3.2-1 and Table 8.1.3.1.12.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR
Cell 2 and NR Cell 3 at various time instants of the test execution for FR1 and FR2 respectively. Row marked "T0"
ETSI
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) (DL only)
T0 SS/PBCH dBm/S -82 -94 "Off" Power levels are such that either one entry
SSS EPRE CS condition for event A5 (measId 1 & 2) is not
SINR dB 12 0 - satisfied:
Noc dBm/S -94 -94 Mp +Hys > Thresh1 or Mn + Ofn + Ocn –
CS Hys < Thresh2
T1 SS/PBCH dBm/S -88 -88 "Off" Power levels are such that both entry
SSS EPRE CS conditions for event A5 (measId 1) is
SINR dB -6 6 - satisfied:
Mp + Hys < Thresh1 and Mn + Ofn + Ocn
Noc dBm/S -94 -94 – Hys > Thresh2
CS
T2 SS/PBCH dBm/S -88 "Off" -88 Power levels are such that both entry
SINR dB 6 - 6 satisfied:
Noc dBm/S -94 -94 – Hys > Thresh2
CS
NOTE 1: The total tolerance used is the sum of downlink signal level uncertainty (TS 38.508-1 Table 6.2.2.1-4) and
Parameter Unit Cell 1 Cell 2 Cell 10 Remark

(DL only) (DL only)
T0 SS/PBCH dBm/S FFS FFS "Off" Power levels are such that either one entry
SSS EPRE CS condition for event A5 (measId 1 & 2) is not
SINR dB FFS FFS - satisfied:
Noc dBm/S FFS FFS Mp +Hys > Thresh1 or Mn + Ofn + Ocn –
CS Hys < Thresh2
T1 SS/PBCH dBm/S FFS FFS "Off" Power levels are such that both entry
SINR dB FFS FFS - satisfied:
Noc dBm/S FFS FFS – Hys > Thresh2
CS
T2 SS/PBCH dBm/S FFS "Off" FFS Power levels are such that both entry
SINR dB FFS - FFS satisfied:
Noc dBm/S FFS FFS – Hys > Thresh2
CS
NOTE 1: The total tolerance used is the sum of downlink signal level uncertainty (TS 38.508-1 Table 6.2.2.2-TBD) and
ETSI

U-S Message
to setup NR measurement and reporting for
two event A5 (measId 1 and measId 2) (intra
and inter frequency measurement).
NR Cell 1.
signal level according to row "T1" in table
8.1.3.1.12.3.2-1/2.
SINR values for NR Cell 2?
8.1.3.1.12.3.2-1/2.
SINR values for NR Cell 3?
Derivation Path: TS 38.508-1 [4] table 4.6.1-13 with condition NR_MEAS
ETSI

measObjectId 1
measObject CHOICE {
8.1.3.1.12.3.3-
3
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.12.3.3-
3A
}
}
}
8.1.3.1.12.3.3-
5
}
}
}
measId 1
measObjectId 1
}
measId 2
measObjectId 2
}
}
}

Cell 1 SSB
}
ETSI
Table 8.1.3.1.12.3.3-3A: MeasObjectNR-f2 (Table 8.1.3.1.12.3.3-2)
Derivation Path: TS 38. 508-1 [4], Table 4.6.3-76

Cell 3 SSB
}
Table 8.1.3.1.12.3.3-4: Void
Derivation Path: TS 38.508-1 [4] table 4.6.3-142 with condition EVENT_A5

reportType CHOICE {
eventId CHOICE {
eventA5 SEQUENCE {
sinr 68 11 dB
}
sinr 47 0.5 dB
}
}
}
rsrp false
rsrq false
sinr true
}
reportAmount r1
}
}
}
ETSI
Table 8.1.3.1.12.3.3-6: MeasurementReport (steps 5 and 7, Table 8.1.3.1.12.3.2-3)

measId 1 Step 5
2 Step 7
measResultServingMOList SEQUENCE (SIZE 1 entry Step 5
Cell 1
physCellId PhysCellId of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr (0..127)
}
}
}
}
}
}
physCellId PhysCellId of NR Cell 2 Step 5
PhysCellId of NR Cell 3 Step 7
rsrp Not Present
rsrq Not Present
sinr (0..127)
}
}
}
}
}
}
}
}
}
}
ETSI
8.1.3.1.13 Measurement configuration control and reporting / SS/PBCH block based / CSI-
RS based intra-frequency measurements / Measurement of Neighbour NR cell
(1)
with { UE in NR RRC_CONNECTED state and measurement configured for SS/PBCH measurement reporting of
intra-frequency on specified frequency}
ensure that {
when { SS/PBCH block sorting quantity is above absThreshSS-BlocksConsolidation for each beam of
Neighbour Cell}
then { UE sends MeasurementReport message containing rsIndexResults with resultsSSB-Indexes}
}
(2)
intra-frequency on specified frequency }
ensure that {
when { SS/PBCH block sorting quantity is below absThreshSS-BlocksConsolidation for one beam of
Neighbour Cell and another beam(s) is above absThreshSS-BlocksConsolidation}
then { UE sends MeasurementReport message containing rsIndexResults with resultsSSB-Indexes
includes RsIndex above absThreshSS-BlocksConsolidation and excludes RsIndex below absThreshSS-
BlocksConsolidation }
}
(3)
with { UE in NR RRC_CONNECTED state and measurement configured for CSI-RS measurement reporting of
intra frequency on specified frequency }
ensure that {
when { CSI-RS sorting quantity is above absThreshCSI-RS-Consolidation for each beam of Neighbour
Cell}
then { UE sends MeasurementReport message containing rsIndexResults with results CSI-RS-Indexes}
}
(4)
intra frequency on specified frequency }
ensure that {
when { CSI-RS sorting quantity is below absThreshCSI-RS-Consolidation for one beam of Neighbour
Cell and another beam(s) is above absThreshCSI-RS-Consolidation }
then { UE sends MeasurementReport message containing rsIndexResults with results CSI-RS-Indexes
includes RsIndex above absThreshCSI-RS-Consolidation and excludes RsIndex below absThreshCSI-RS-
Consolidation }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clauses 5.5.5.1 and
5.5.5.2]. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.5.5.1]
1> for each serving cell configured with servingCellMO:
2> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:
ETSI
3> if the serving cell measurements based on the rsType included in the reportConfig that triggered the
measurement report are available:
4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the
available SINR of the serving cell, derived based on the rsType included in the reportConfig that
triggered the measurement report;
2> else:
3> if SSB based serving cell measurements are available:
available SINR of the serving cell, derived based on SSB;
3> else if CSI-RS based serving cell measurements are available:
available SINR of the serving cell, derived based on CSI-RS;
1> set the ServingCellId within measResultServingMOList to include for each NR serving cell that is configured
with servingCellMO, if any;
with the following:
this measId;
8> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include

beam measurement information as described in 5.5.5.2;
7> else if rsType in the associated reportConfig is set to csi-rs:
8> set resultsCSI-RS-Cell within the measResult to include the CSI-RS based quantity(ies)
indicated in the reportQuantityCell within the concerned reportConfig, in decreasing
order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is
included first;

[TS 38.331, clause 5.5.5.1]
ETSI
1> else:
2> if SRB3 is configured:
3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the
procedure ends;
2>else:
3> submit the MeasurementReport message via the EUTRA MCG embedded in E-UTRA RRC message
ULInformationTransferMRDC as specified in TS 36.331 [10].
1> else:
2>submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.
[TS 38.331, clause 5.5.5.2]
For beam measurement information to be included in a measurement report the UE shall:
1> if reportType is set to eventTriggered:
2> consider the trigger quantity as the sorting quantity if available , otherwise RSRP as sorting quantity if
available, otherwise RSRQ as sorting quantity if available, otherwise SINR as sorting quantity;
1> if reportType is set to periodical:
2> if a single reporting quantity is set to TRUE in reportQuantityRs-Indexes;
3> consider the configured single quantity as the sorting quantity;
2> else:
3> if rsrp is set to TRUE;
4> consider RSRP as the sorting quantity;
3> else:
4> consider RSRQ as the sorting quantity;
1> set rsIndexResults to include up to maxNrofRs-IndexesToReport SS/PBCH block indexes or CSI-RS indexes in
order of decreasing sorting quantity as follows:
2> if the measurement information to be included is based on SS/PBCH block:
3> include within resultsSSB-Indexes the index associated to the best beam for that SS/PBCH block sorting
quantity and the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation
defined in the VarMeasConfig for the corresponding measObject;
3> if includeBeamMeasurements is configured, include the SS/PBCH based measurement results for the
quantities in reportQuantity-RsIndexes set to TRUE for each SS/PBCH blockindex;
ETSI
2> else if the beam measurement information to be included is based on CSI-RS:
3> include within resultsCSI-RS-Indexes the index associated to the best beam for that CSI-RS sorting
quantity and the remaining beams whose sorting quantity is above absThreshCSI-RS-Consolidation
defined in the VarMeasConfig for the corresponding measObject;
3> if includeBeamMeasurementsis configured, include the CSI-RS based measurement results for the
quantities in reportQuantity-RsIndexes set to TRUE for each CSI-RS index.
System Simulator:
- NR Cell 1 is the Serving Cell.
- NR Cell 2 is the intra-frequency neighbour cell of NR Cell 1. NR Cell2 has two beams: SSB/CSI-RS index#0
and SSB/CSI-RS index#1.
UE:
- None
Preamble:
Table 8.1.3.1.13.3.2-1 and Table 8.1.3.1.13.3.2-1A illustrates the downlink power levels to be applied for NR Cell 1 and
NR 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
ETSI

Beam Beam
0 1
(NOTE) (NOTE)
SS/PBCH dBm/SC
-94 - - -
SSS EPRE S
Reference dBm/SC
- -90 - -
Power S
T0 SS/PBCH
SSS
EPRE,
dB - - -4 -4
CSI-RS
EPRE
offset
Mn + Ofn + Ocn − Hys  Mp + Ofp + Ocp + Off
SS/PBCH dBm/SC
-106 - - -
SSS EPRE S Power level is such that SS/PBCH quality
and CSI-RS quality for both beams of NR
Reference dBm/SC Cell 2 are above absThreshSS-
- -90 - - BlocksConsolidation.
Power S
T1
SS/PBCH
SSS
EPRE,
dB - - -4 -4
CSI-RS
EPRE
offset
SS/PBCH dBm/SC Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp
-94 - - -
SSS EPRE S + Off
Reference dBm/SC
- -90 - - Power level is such that SS/PBCH quality
Power S
SS/PBCH and CSI-RS quality for both beams of NR
T2 Cell 2 are below absThreshSS-
SSS
EPRE, BlocksConsolidation
dB - - -12 -12
CSI-RS
EPRE
offset
Power level is such that SS/PBCH quality
SS/PBCH dBm/SC and CSI-RS quality for beam 0 of NR Cell
-106 - - -
SSS EPRE S 2 is above absThreshSS-
BlocksConsolidation and for beam 1 of
Reference dBm/SC NR Cell 2 is below absThreshSS-
- -90 - -
Power S BlocksConsolidation.
T3
SS/PBCH
SSS
EPRE,
dB - - -4 -12
CSI-RS
EPRE
offset
ETSI

Beam Beam
0 1
(NOTE) (NOTE)
SS/PBCH dBm/SC
-82 - - -
SSS EPRE S
Reference dBm/SC
- -90 - -
Power S
T0 SS/PBCH
SSS
EPRE,
dB - - -1 -1
CSI-RS
EPRE
offset
Mn + Ofn + Ocn − Hys  Mp + Ofp + Ocp + Off
SS/PBCH dBm/SC
-100 - - -
SSS EPRE S
and CSI-RS quality for both beams of NR
Reference dBm/SC Cell 2 are above absThreshSS-
- -90 - -
T1
SS/PBCH
SSS
EPRE,
dB - - -1 -1
CSI-RS
EPRE
offset
Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp
SS/PBCH dBm/SC
-100 - - - + Off
SSS EPRE S
Reference dBm/SC Power level is such that SS/PBCH quality
- -90 - -
Power S and CSI-RS quality for both beams of NR
T2 SS/PBCH Cell 2 are below absThreshSS-
SSS BlocksConsolidation
EPRE,
dB - - -10 -10
CSI-RS
EPRE
offset
SS/PBCH dBm/SC and CSI-RS quality for beam 0 of NR Cell
-100 - - -
SSS EPRE S 2 is above absThreshSS-
BlocksConsolidation and for beam 1 of
Reference dBm/SC NR Cell 2 is below absThreshSS-
- -90 - -
T3
SS/PBCH
SSS
EPRE,
dB - - -1 -10
CSI-RS
EPRE
offset
ETSI

U-S Message
1 The SS transmits an NR RRCReconfiguration <-- NR RRC: - -
message including measConfig to setup SS/PBCH RRCReconfiguration
block based intra- frequency NR measurement for
NR Cell 1 and reporting for event A3.
RRCReconfigurationComplete message. RRCReconfigurationComple
te
3 The SS re-adjusts the cell-specific reference signal - - - -
level according to row "T1".
MeasurementReport message to report event A3 MeasurementReport
with the measured results for NR Cell 2 with beam
information containing RsIndex[0] and RsIndex[1]?
4A The SS re-adjusts the cell-specific reference signal - - - -
level according to the row "T2".
4AA Wait and ignore MeasurementReport messages for - - - -
10s to allow change of power levels for NR Cell 2
and UE measurement.
4B Check: Does the UE transmit a - - 1 F
report the event A3 during the next 1s?
information containing RsIndex[0] and excludes
RsIndex[1]?
7-8 Void - - - -
including measConfig to setup CSI-RS based intra- RRCReconfiguration
frequency NR measurement for NR Cell 1 and
reporting for event A3.
10 The UE transmits an RRCConfigurationComplete. --> NR RRC: - -
RRCReconfigurationComple
te
information containing RsIndex[0] and RsIndex[1]?
12A The SS re-adjusts the cell-specific reference signal - - - -
level according to the row "T2".
12A Wait and ignore MeasurementReport messages for - - - -
A 10s to allow change of power levels for NR Cell 2
and UE measurement.
12B Check: Does the UE transmit a - - 1 F
report the event A3 during the next 1s?
information containing RsIndex[0] and excludes
RsIndex[1]?
including measConfig to release CSI-RS based RRCReconfiguration
intra-frequency NR measurement.
16 The UE transmits an RRCConfigurationComplete. --> NR RRC: - -
RRCReconfigurationComple
te
ETSI
Table 8.1.3.1.13.3.3-1: RRCReconfiguration (steps 1, 9 and 15, Table 8.1.3.1.13.3.2-2)

MeasConfig::= SEQUENCE {
measObjectToAddModList IdMeasObjectToAdd Step 1
Not present Step 9, Step
15
reportConfigToAddModList IdReportConfigToAdd Step 1
Not present Step 9, Step
15
measIdToRemoveList SEQUENCE (SIZE 1 entry Step 15
(1..maxNrofObjectId)) OF MeasObjectId {
MeasObjectId[1] 1
}
measIdToAddModList IdMeasIdToAdd Step 1, Step
9
Not present Step 15
}
Table 8.1.3.1.13.3.3-3: IdMeasObjectToAdd (Table 8.1.3.1.13.3.3-2)

MeasObjectToAddModList::= SEQUENCE (SIZE 1 entry
measObjectId 1
measObject CHOICE {
measObjectNR Id-MeasObjectNR
}
}
}
ETSI
Table 8.1.3.1.13.3.3-4: Id-MeasObjectNR (Table 8.1.3.1.13.3.3-3)

Cell1
refFreqCSI-RS Same as “Point A”
defined for the downlink
of NR Cell1
referenceSignalConfig SEQUENCE {
ssb-ConfigMobility SEQUENCE {
ssb-ToMeasure CHOICE {
setup CHOICE {
shortBitmap 1100 (FREQ<=3G
Hz AND
(FR1_FDD
OR NOT
CASE_C))
OR
(FREQ<=2.4
GHz AND
FR1_TDD)
mediumBitmap 11000000 (FREQ>3G
Hz AND
FR1) OR
(FREQ>2.4
GHz AND
FR1_TDD
AND
CASE_C)
longBitmap 11000000 00000000 FR2
00000000 00000000
00000000 00000000
00000000 00000000
}
}
}
csi-rs-ResourceConfigMobility CHOICE {
setup SEQUENCE {
subcarrierSpacing SubcarrierSpacing
csi-RS-CellList-Mobility SEQUENCE (SIZE 2 entries
(1..maxNrofCSI-RS-CellsRRM)) OF CSI-RS-
CellMobility {
CSI-RS-CellMobility[1] SEQUENCE { entry 1
cellId Physical CellID of the NR
Cell 1
csi-rs-MeasurementBW SEQUENCE {
nrofPRBs size24
startPRB same value as
‘offsetToCarrier’ as
defined for the DL
frequency of NR Cell 1
}
density d3
csi-rs-ResourceList-Mobility SEQUENCE 1 entry
(SIZE (1..maxNrofCSI-RS-ResourcesRRM)) OF CSI-
RS-Resource-Mobility {
RS-Resource-Mobility[1] SEQUENCE { entry 1
csi-RS-Index 0
slotConfig CHOICE {
ms20 0 To avoid collision
with CSI-RS of
NR Cell 2
}
associatedSSB Not present
associatedSSB SEQUENCE { pc_csi_RSR
ETSI
P_AndRSR
Q_MeasWit
hSSB
ssb-Index 0
isQuasiColocated false
}
frequencyDomainAllocation CHOICE {
row1 1000
}
firstOFDMSymbolInTimeDomain 4
sequenceGenerationConfig 24
}
}
}
Cell 2
nrofPRBs size24
defined for the DL
frequency of the cell
}
density d3
csi-rs-ResourceList-Mobility SEQUENCE 2 entries
csi-RS-Index 0 CSI-RS with Index
0
slotConfig CHOICE {
ms20 10 * 2µ µ is numerology
index
(SCS=15kHz: 0,
SCS=30kHz: 1,
etc.)
}
P_AndRSR
Q_MeasWit
hSSB
ssb-Index 0
}
row1 1000
}
}
1
slotConfig CHOICE {
ms20 10 * 2µ µ: numerology
index
(SCS=15kHz: 0,
SCS=30kHz: 1,
etc.)
}
P_AndRSR
Q_MeasWit
ETSI
hSSB
ssb-Index 1
}
row1 0001
}
}
}
}
}
}
}
}
absThreshSS-BlocksConsolidation SEQUENCE {
thresholdRSRP 57 corresponding to - FR1
100dBm
66 +Delta(NRf1) corresponding to - FR2
91dBm
}
}
NOTE 1: delta(NRf1) is derived based on calibration procedure defined in the TS 38.508-1 [4], clause 6.1.3.3 on NR
Cell1
Table 8.1.3.1.13.3.3-5: IdReportConfigToAdd (Table 8.1.3.1.13.3.3-2)

ReportConfigToAddModList::= SEQUENCE(SIZE 2 entries
{
reportConfigId 1
reportConfigNR IdReportConfig-A3-SSB
}
}
reportConfigId 2
reportConfigNR IdReportConfig-A3-CSI-
RS
}
}
}
ETSI
Table 8.1.3.1.13.3.3-6: IdReportConfig-A3-SSB (Table 8.1.3.1.13.3.3-5)

reportType CHOICE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset CHOICE {
rsrp 2
}
}
}
reportQuantityRS-Indexes SEQUENCE {
rsrp true
rsrq false
sinr false
}
maxNrofRS-IndexesToReport 2
includeBeamMeasurements true
}
}
}
Table 8.1.3.1.13.3.3-6A: IdReportConfig-A3-CSI-RS (Table 8.1.3.1.13.3.3-5)

reportType CHOICE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset CHOICE {
rsrp 2
}
}
}
rsType csi-rs
sinr false
}
reportQuantityRS-Indexes SEQUENCE {
rsrp true
rsrq false
sinr false
}
maxNrofRS-IndexesToReport 2
includeBeamMeasurements true
}
}
}
ETSI
Table 8.1.3.1.13.3.3-7: IdMeasIdToAdd (Table 8.1.3.1.13.3.3-2)

MeasIdToAddModList::= SEQUENCE (SIZE 1 entry
MeasIdToAddMod
measId 1
measObjectId 1
reportConfigId 1 Step 1
2 Step 9
}
}

measResults MeasResults
}
}
}
ETSI
Table 8.1.3.1.13.3.3-9: MeasResults (Table 8.1.3.1.13.3.3-8)

MeasResults ::= SEQUENCE {
measId 1
measResultServingMOList SEQUENCE (SIZE 1 entry
servCellId ServCellIndex of NR Cell
1
physCellId Physical CellID of the NR
Cell 1
cellResults SEQUENCE{
rsrp (0..127)
rsrq (0..127)
sinr (0..127) pc_ss_SINR
_Meas
Not present
}
rsIndexResults SEQUENCE {
resultsSSB-Indexes SEQUENCE (SIZE 1 entry
(1..maxNrofIndexesToReport2)) OF ResultsPerSSB-
Index {
ResultsPerSSB-Index[1] EQUENCE { entry 1
ssb-Index Not checked
ssb-Results SEQUENCE {
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
resultsCSI-RS-Indexes Not present
}
}
}
}
}
Cell 2
rsrp (0..127)
rsrq (0..127)
_Meas
Not present
}
}
resultsSSB-Indexes SEQUENCE (SIZE 2 entries that may appear
(1..maxNrofIndexesToReport2)) OF ResultsPerSSB- in an arbitrary order
Index {
ResultsPerSSB-Index [1] SEQUENCE { entry 1
ssb-Index SSB index 0
rsrp (0..127)
ETSI
rsrq Not present

sinr Not present
}
}
ResultsPerSSB-Index [2] SEQUENCE { entry 2
ssb-Index SSB index 1
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}

}
}
}
ETSI

measId 1
1
Cell 1
rsrp (0..127)
rsrq (0..127)
_Meas
Not present
}
}
Index {
ResultsPerSSB-Index[1] SEQUENCE { entry 1
ssb-Index Not checked
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
Cell2
rsrp (0..127)
rsrq (0..127)
_Meas
Not present
}
}
Index {
ssb-Index[1] SSB index 0
ETSI
ssb-Results[1] SEQUENCE {
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
Table 8.1.3.1.13.3.3-12: Void
Table 8.1.3.1.13.3.3-13: Void
Table 8.1.3.1.13.3.3-14: Void
Table 8.1.3.1.13.3.3-15: Void
Table 8.1.3.1.13.3.3-16: Void
Table 8.1.3.1.13.3.3-17: Void

}
}
}
ETSI

measId 1
measResultServingMOList SEQUENCE {(SIZE 1 entry
1
Cell 1
resultsSSB-Cell Not present
resultsCSI-RS-Cell SEQUENCE {
rsrp (0..127)
rsrq (0..127)
sinr Not present
Not checked pc_ss_SINR
_Meas
}
}
resultsSSB-Indexes Not present
resultsCSI-RS-Indexes SEQUENCE (SIZE 1 entry
Index {
csi-RS-Index Not checked
csi-RS-Results SEQUENCE {
rsrp (0..127)
rsrq (0..127)
sinr Not present
}
}
}
}
}
}
}
}
Cell 2
rsrp (0..127)
rsrq (0..127)
sinr Not present
}
}
resultsSSB-Indexes Not Present
resultsCSI-RS-Indexes SEQUENCE (SIZE 2 entries that may appear
(1..maxNrofIndexesToReport2)) OF ResultsPerCSI- in an arbitrary order
RS-Index {
ResultsPerCSI-RS-Index[1] SEQUENCE { entry 1
csi-RS-Index CSI-RS-index 0
ETSI
rsrp Not checked
rsrq Not present
sinr Not present
}
}
ResultsPerCSI-RS-Index[2] SEQUENCE { entry 2
csi-RS-Index CSI-RS-index 1
rsrp Not checked
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}

}
}
}
ETSI

measId 1
1
Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
_Meas
}
}
resultsSSB-Indexes Not present
Index {
csi-RS-Index Not checked
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}
Cell 2
rsrp (0..127)
rsrq (0..127)
sinr Not present
}
}
resultsSSB-Indexes Not Present
Index {
ETSI
csi-RS-Index CSI-RS-Index 0
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}
8.1.3.1.14 Void
8.1.3.1.14A Measurement configuration control and reporting / SS/PBCH block based / CSI-
RS based inter-frequency measurements / Measurement of Neighbour NR cell
8.1.3.1.14A.1 Test Purpose (TP)
(1)
inter-frequency on specified frequency}
ensure that {
when { SS/PBCH block sorting quantity is above absThreshSS-BlocksConsolidation for each beam of
Neighbour Cell}
then { UE sends MeasurementReport message containing rsIndexResults with resultsSSB-Indexes}
}
(2)
inter-frequency on specified frequency }
ensure that {
when { SS/PBCH block sorting quantity is below absThreshSS-BlocksConsolidation for one beam of
Neighbour Cell and another beam(s) is above absThreshSS-BlocksConsolidation}
then { UE sends MeasurementReport message containing rsIndexResults with resultsSSB-Indexes
includes RsIndex above absThreshSS-BlocksConsolidation and excludes RsIndex below absThreshSS-
BlocksConsolidation }
}
(3)
inter frequency on specified frequency }
ensure that {
when { CSI-RS sorting quantity is above absThreshCSI-RS-Consolidation for each beam of Neighbour
Cell}
then { UE sends MeasurementReport message containing rsIndexResults with resultsCSI-RS-Indexes}
}
(4)
inter frequency on specified frequency }
ensure that {
when { CSI-RS sorting quantity is below absThreshCSI-RS-Consolidation for one beam of Neighbour
Cell and another beam(s) is above absThreshCSI-RS-Consolidation }
then { UE sends MeasurementReport message containing rsIndexResults with resultsCSI-RS-Indexes
includes RsIndex above absThreshCSI-RS-Consolidation and excludes RsIndex below absThreshCSI-RS-
Consolidation }
}
ETSI
8.1.3.1.14A.2 Conformance requirements
Same as TC 8.1.3.1.13
8.1.3.1.14A.3 Test description
8.1.3.1.14A.3.1 Pre-test conditions
- System information combination NR-4 as defined in TS 38.508-1[4] clause 4.4.3.1.2 is used in NR cells.
8.1.3.1.14A.3.2 Test procedure sequence
8.1.3.1.14A.3.3 Specific message contents
Table 8.1.3.1.14A.3.3-1: IdMeasObjectToAdd (Table 8.1.3.1.13.3.3-2)

MeasObjectToAddModList ::= SEQUENCE (SIZE 2 entries
measObjectId 1
measObject CHOICE {
measObjectNR Id-MeasObjectNR-f1
}
}
measObjectId 2
measObject CHOICE {
measObjectNR Id-MeasObjectNR-f2
}
}
}
ETSI
Table 8.1.3.1.14A.3.3-1A: Id-MeasObjectNR-f1 (Table 8.1.3.1.14A.3.3-1)

Cell 1
of NR Cell1
setup SEQUENCE {
csi-RS-CellList-Mobility SEQUENCE (SIZE 1 entry
CellMobility {
Cell 1
nrofPRBs size24
defined for the DL
frequency of NR Cell 1
}
density d3
csi-rs-ResourceList-Mobility SEQUENCE 1 entry
CSI-RS-Resource-Mobility[1] SEQUENCE { entry 1
csi-RS-Index 0
slotConfig CHOICE {
ms20 0
}
P_AndRSR
Q_MeasWit
hSSB
ssb-Index 0
}
row1 1000
}
}
}
}
}
}
}
}
99dBm
66 corresponding to - FR2
90dBm
}
absThreshCSI-RS-Consolidation SEQUENCE {
99dBm
ETSI
90dBm
thresholdRSRQ Not Present
thresholdSINR Not Present
}
nrofCSI-RS-ResourcesToAverage 2
}
ETSI
Table 8.1.3.1.14A.3.3-2: Id-MeasObjectNR-f2 (Table 8.1.3.1.14A.3.3-1)

Cell3
of NR Cell3
ssb-ConfigMobility SEQUENCE {
ssb-ToMeasure CHOICE {
setup CHOICE {
shortBitmap 1100 (FREQ<=3G
Hz AND
(FR1_FDD
OR NOT
CASE_C))
OR
(FREQ<=2.4
GHz AND
FR1_TDD)
mediumBitmap 11000000 (FREQ>3G
Hz AND
FR1) OR
(FREQ>2.4
GHz AND
FR1_TDD
AND
CASE_C)
longBitmap 11000000 00000000 FR2
00000000 00000000
00000000 00000000
00000000 00000000
}
}
}
setup SEQUENCE {
csi-RS-CellList-Mobility SEQUENCE (SIZE 1 entry
CellMobility {
Cell 3
nrofPRBs size24
defined for the DL
frequency of the cell
}
density d3
csi-rs-ResourceList-Mobility SEQUENCE 2 entries
(SIZE (1.. maxNrofCSI-RS-ResourcesRRM)) OF CSI-
0
slotConfig CHOICE {
ms20 10 * 2µ µ is numerology
index
(SCS=15kHz: 0,
SCS=30kHz: 1,
etc.)
ETSI
}
P_AndRSR
Q_MeasWit
hSSB
ssb-Index 0
}
row1 1000
}
}
1
slotConfig CHOICE {
ms20 10 * 2µ µ: numerology
index
(SCS=15kHz: 0,
SCS=30kHz: 1,
etc.)
}
P_AndRSR
Q_MeasWit
hSSB
ssb-Index 1
}
row1 0001
}
}
}
}
}
}
}
}
909dBm
66 +Delta(NRf2) corresponding to - FR2
90dBm
}
absThreshCSI-RS-Consolidation SEQUENCE {
99dBm
90dBm
thresholdRSRQ Not Present
thresholdSINR Not Present
}
nrofCSI-RS-ResourcesToAverage 2
}
NOTE 1: Delta(NRf2) is derived based on calibration procedure defined in the TS 38.508-1 [4], clause 6.1.3.3 on NR
Cell3
ETSI
Table 8.1.3.1.14A.3.3-3: Void
Table 8.1.3.1.14A.3.3-4: IdMeasIdToAdd (Table 8.1.3.1.13.3.3-2)

MeasIdToAddModList::= SEQUENCE (SIZE 1 entry
measId 1
measObjectId 2
2 Step 9
}
}
Table 8.1.3.1.14A.3.3-5: Void
Table 8.1.3.1.14A.3.3-6: Void
8.1.3.1.15 Void
8.1.3.1.15A Measurement configuration control and reporting / Intra NR measurements /

Blacklisting
8.1.3.1.15A.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and measurement 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 NR RRC_CONNECTED state and measurement reporting triggered by event A3 is ongoing and
no neighbour cells are blacklisted }
ensure that {
when { Neighbour cells satisfies entry condition for event A3 }
then { Neighbour cells are considered in measurement reporting }
}
8.1.3.1.15A.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clauses 5.5.1, 5.5.4.1,
and 5.5.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.5.1]
The network may configure an RRC_CONNECTED UE to perform measurements and report them in accordance with
the measurement configuration. The measurement configuration is provided by means of dedicated signalling i.e. using
the RRCReconfiguration
...
- For intra-frequency and inter-frequency measurements a measurement object indicates the frequency/time
location and subcarrier spacing of reference signals to be measured. Associated with this measurement object,
ETSI
the network may configure a list of cell specific offsets, a list of 'blacklisted' cells and a list of 'whitelisted' cells.
Blacklisted cells are not applicable in event evaluation or measurement reporting. Whitelisted cells are the only
ones applicable in event evaluation or measurement reporting.
...
[TS 38.331, clause 5.5.4.1]
The UE shall:
3> if the corresponding measObject concerns EUTRA:
4> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be
applicable when the concerned cell is not included in the blackCellsToAddModList defined within the
VarMeasConfig for this measId;
measId;
measId;
measId;
ETSI
[TS 38.331, clause 5.5.5.1]
the following:
measId;
3> else:
8> if reportQuantityRsIndexes and maxNrofRSIndexesToReport are configured, include

ETSI
1> else:
[TS 38.331, clause 5.5.2.5]
The UE shall:
1> for each measObjectId included in the received measObjectToAddModList:
2> if an entry with the matching measObjectId exists in the measObjectList within the VarMeasConfig, for this
entry:
3> reconfigure the entry with the value received for this measObject, except for the fields
cellsToAddModList, blackCellsToAddModList, whiteCellsToAddModList, cellsToRemoveList,
blackCellsToRemoveList and whiteCellsToRemoveList;
3> if the received measObject includes the cellsToRemoveList:
4> for each physCellId included in the cellsToRemoveList:
5> remove the entry with the matching physCellId from the cellsToAddModList;
3> if the received measObject includes the cellsToAddModList:
4> for each physCellId value included in the cellsToAddModList:
5> if an entry with the matching physCellId exists in the cellsToAddModList:
6> replace the entry with the value received for this physCellId;
5> else:
6> add a new entry for the received physCellId to the cellsToAddModList;
3> if the received measObject includes the blackCellsToRemoveList:
4> for each pci-RangeIndex included in the blackCellsToRemoveList:
5> remove the entry with the matching pci-RangeIndex from the blackCellsToAddModList;
NOTE: For each pci-RangeIndex included in the blackCellsToRemoveList that concerns overlapping ranges of
cells, a cell is removed from the black list of cells only if all cell indexes containing it are removed.
3> if the received measObject includes the blackCellsToAddModList:
4> for each pci-RangeIndex included in the blackCellsToAddModList:
5> if an entry with the matching pci-RangeIndex is included in the blackCellsToAddModList:
6> replace the entry with the value received for this pci-RangeIndex;
5> else:
ETSI
6> add a new entry for the received pci-RangeIndex to the blackCellsToAddModList;
3> for each measId associated with this measObjectId in the measIdList within the VarMeasConfig, if any:
4> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;
4> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;
2> else:
3> add a new entry for the received measObject to the measObjectList within VarMeasConfig.
[TS 38.331, clause 5.5.4.4]
The UE shall:
8.1.3.1.15.3A Test description
8.1.3.1.15.3A.1 Pre-test conditions
System Simulator:
- NR Cell 1, Cell 3 and Cell 12:
ETSI
- NR Cell 1 is the serving cell
- NR Cell 3 and Cell 12 are inter-frequency neighbour cells
- System information combination NR-4 as defined in TS 38.508-1[4] clause 4.4.3.1.2 is used in NR cells.
UE:
- None
Preamble:
- The UE is in state NR RRC_CONNECTED in Established (state 3) according to [18].
8.1.3.1.15A.3.2 Test procedure sequence
Table 8.1.3.1.15A.3.2-1 illustrates the downlink power levels to be applied for NR Cell 1, Cell 3 and Cell 12 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.1.3.1.15A.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter Unit NR Cell 1 NR Cell 3 NR Cell Remark

(DL only) 12
(DL only)
T0 SS/PBCH dBm/ -85 -97 -97 Power levels are such that leaving condition
SSS EPRE SCS for event A3 is satisfied for all neighbour NR
cells:
Mn + Ofn + Ocn + Hys  Mp + Ofp + Ocp + Off
T1 SS/PBCH dBm/ -85 -79 -97 Power levels are such that entry condition for
SSS EPRE SCS event A3 is satisfied for inter-frequency
neighbour NR cell 3 [measId 1]
Mn + Ofn + Ocn − Hys  Ms + Ofs + Ocs + Off
T2 SS/PBCH dBm/ -85 -79 -79 Power levels are such that entry condition for
neighbour NR cell 3 and NR Cell 12 [measId 2]
Table 8.1.3.1.15A.3.2-1A: Time instances of cell power level and parameter changes for FR2
Parameter Unit NR Cell 1 NR Cell 3 NR Cell Remark

(DL only) 12
(DL only)
T0 SS/PBCH dBm/ FFS FFS FFS Power levels are such that leaving condition
SSS EPRE SCS for event A3 is satisfied for all neighbour NR
cells:
Mn + Ofn + Ocn + Hys  Mp + Ofp + Ocp + Off
T1 SS/PBCH dBm/ FFS FFS FFS Power levels are such that entry condition for
neighbour NR cell 3 [measId 1]
T2 SS/PBCH dBm/ FFS FFS FFS Power levels are such that entry condition for
SSS EPRE SCS event A3 is satisfeied for intr-frequency
neighbour NR cell 3 and NR Cell 12 [measId 2]
ETSI
Table 8.1.3.1.15A.3.2-2: Main behaviour

U-S Message
including measConfig to setup intra NR
measurement and reporting for event A3.
8.1.31.15A.3.2.-1/1A.
4 Check: does the UE transmit a - NR RRC: MeasurementReport 1 F
MeasurementReport messages within the next
10s?
8.1.3.1.15A.3.2.-1/1A.
6 Check: does the UE transmit a --> NR RRC: MeasurementReport 1 P
A3 with the measured RSRP values for Cell 1
and Cell 12 without Cell 3 results?
including measConfig to remove Cell 3 from
the blacklisted cell list.
RRCReconfigrationComplete message RRCReconfigurationComplete
- EXCEPTION: Steps 8Aa1 to 8Ab1 describe a - - - -
transaction that depends on the UE behaviour;
sequence that takes place if a specific
behaviour happens.
8A IF the UE detects event A3 for Cell 12 before --> NR RRC: MeasurementReport - -
a1 event A3 for Cell 3 THEN the UE may transmit
A3 with the measured RSRP values for Cell 1
and Cell .
8A IF the UE detects event A3 for Cell 3 before --> NR RRC: MeasurementReport - -
b1 event A3 for Cell 12 THEN the UE may
transmit MeasurementReport message to
report event A3 with the measured RSRP
values for Cell 1 and Cell 3.
9 Check: does the UE transmit a --> NR RRC: MeasurementReport 2 P
A3 with the measured RSRP values for Cell 1,
Cell 3 and Cell 12?
including measConfig to release intra NR
measurement and reporting for event A3.
RRCReconfigrationComplete message RRCReconfigurationComplete
8.1.3.1.15A.3.3 Specific message contents
Table 8.1.3.1.15A.3.3-1: RRCReconfiguration (step 1 and Step 7 Table 8.1.3.1.15A.3.2-2)
ETSI
Table 8.1.3.1.15A.3.3-2: MeasConfig (Table 8.1.3.1.15A.3.3-1)
Derivation Path: TS 38.508 clause 4.6.3 table 4.6.3-69 with condition EVENT_A3
measObjectToAddModList SEQUENCE (SIZE 2 entries Step 1 of
(1..maxNrofMeasId)) OF MeasObjectToAddMod { Table
8.1.3.1.15A.
3.3-1
measObjectId 1
measObject CHOICE {
8.1.3.1.15A.3.3-
2A
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.15A.3.3-3
}
}
}
measObjectToAddModList SEQUENCE (SIZE 1 entry Step 7 of
(1..maxNrofMeasId)) OF MeasObjectToAddMod { Table
8.1.3.1.15A.
3.3-1
measObjectId 2
measObject CHOICE {
8.1.3.1.15A.3.3-5
}
}
}
measObjectToAddModList Not present Step 10 of
Table
8.1.3.1.15A.
3.3-1
reportConfigToAddModList SEQUENCE(SIZE 1 entry Step 1 of
(1..maxReportConfigId)) OF ReportConfigToAddMod Table
{ 8.1.3.1.15A.
3.3-1
reportConfigNR ReportConfigNR(2) a3-Offset value
Same as TS 38.508-1 set to 1 dB (2*0.5
Table 4.6.3-142 except dB)
for reportAmount set to
‘r1’
}
}
}
reportConfigToAddModList Not present Step 7 or 10
of Table
8.1.3.1.15A.
3.3-1
measIdToRemoveList SEQUENCE (SIZE 1 entry Step 10 of
(1..maxNrofMeasId)) OF MeasId { Table
8.1.3.1.15A.
3.3-1
MeasId[1] 1 entry 1
}
measIdToAddModList SEQUENCE (SIZE 1 entry Step 1 of
ETSI
(1..maxNrofMeasId)) OF MeasIdToAddMod { Table

8.1.3.1.15A.
3.3-1
MeasIdToAddMod[1] SEQUENCE {
measId 1
measObjectId 2
}
}
measIdToAddModList Not present Step 7 or 10
of Table
8.1.3.1.15A.
3.3-1
measGapConfig MeasGapConfig with
condition INTER-
FREQ_ODD
}
Table 8.1.3.1.15A.3.3-2A: MeasObjectNR-f1 (Table 8.1.3.1.15A.3.3-2)

SSB of NR Cell 1
}
Table 8.1.3.1.15A.3.3-3: MeasObjectNR-f2 (Table 8.1.3.1.15A.3.3-2)

SSB of NR Cell 3
smtc1 SSB-MTC with condition
INTER-FREQ_ODD
blackCellsToAddModList SEQUENCE (SIZE (1.. 1 entry Add Cell 3
maxNrofPCI-Ranges)) OF PCI-RangeElement {
PCI-RangeElement[1] SEQUENCE { entry 1
PCI-RangeIndex 1
pci-Range SEQUENCE {
start physicalCellIdentity-Cell3
range Not present
}
}
}
}
ETSI
Table 8.1.3.1.15A.3.3-4: MeasurementReport (step 6, Table 8.1.3.1.15A.3.2-2)
Derivation Path: TS 38.508-1 [4] clause 4.6.1 table 4.6.1-5A

c1 CHOICE {
measId 1
servCellId ServCellIndex - Cell1
measResultServingCell SEQUENCE { Report Cell 1
physCellId physicalCellIdentity-Cell1
rsrp (0..127)
rsrq (0..127)
(0..127) pc_ss_SIN
R_Meas
sinr Not present
}
}
}
}
}
}
measResultListNR SEQUENCE (SIZE 1 entry Report Cell 12
physCellId physicalCellIdentity-Cell
12
rsrp (0..127)
rsrq (0..127)
sinr (0..127) pc_ss_SIN
R_Meas
Not present
}
}
}
}
}
}
}
}
}
}
ETSI
Table 8.1.3.1.15A.3.3-5: MeasObjectNR-f2 (Step 7 Table 8.1.3.1.15A.3.3-2)

SSB of NR Cell 3
smtc1 SSB-MTC with condition
INTER-FREQ_ODD
blackCellsToRemoveList SEQUENCE (SIZE (1.. 1 entry Remove Cell 3
PCI-RangeIndex [1] physicalCellIdentity-Cell3 entry 1
}
}
ETSI
Table 8.1.3.1.15A.3.3-6: MeasurementReport (step 8Aa1, Table 8.1.3.1.15A.3.2-2)

c1 CHOICE {
measId 1
(1.. maxNrofServingCells)) OF MeasResultServMO {
servCellId ServCellIndex – Cell1
rsrp (0..127)
rsrq (0..127)
R_Meas
Not present
}
}
}
}
}
}
12
rsrp (0..127)
rsrq (0..127)
R_Meas
Not present
}
}
}
}
}
}
}
}
}
}
}
ETSI
Table 8.1.3.1.15A.3.3-7: MeasurementReport (step 8Ab1, Table 8.1.3.1.15A.3.2-2)

c1 CHOICE {
measId 1
rsrp (0..127)
rsrq (0..127)
R_Meas
Not Present
}
}
}
}
}
}
physCellId[1] physicalCellIdentity-Cell3
measResult [1] SEQUENCE {
rsrp (0..127)
rsrq (0..127)
R_Meas
Not Present
}
}
}
}
}
}
}
}
}
}
}
ETSI
Table 8.1.3.1.15A.3.3-8: MeasurementReport (step 9, Table 8.1.3.1.15A.3.2-2)

c1 CHOICE {
measId 1
rsrp (0..127)
rsrq (0..127)
R_Meas
Not Present
}
}
}
}
}
}
measResultListNR SEQUENCE (SIZE 2 entries that may appear Report Cell 3 and
(1..maxCellReport)) OF MeasResultNR { in an arbitrary order Cell 12
rsrp (0..127)
rsrq (0..127)
R_Meas
Not Present
}
}
}
}
12
rsrp (0..127)
rsrq (0..127)
R_Meas
Not Present
}
}
}
ETSI

}
}
}
}
}
}
}
}

Whitelisting
(1)
with { UE in NR RRC_CONNECTED state and measurement configured for event A3 reporting }
ensure that {
when { Neighbour cell not listed as a white 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 NR RRC_CONNECTED state and measurement reporting triggered by event A3 is ongoing and
all of the neighbour cells are whitelisted }
ensure that {
when { Neighbour cells satisfies entry condition for event A3 }
then { Neighbour cells are considered in measurement reporting }
}
5.5.2.1, 5.5.2.9, 5.5.4.1, 5.5.4.6 and 5.5.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
1> else:
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.4.1]
2> if the corresponding reportConfig includes a reportType set to eventTriggered or periodical:
3> if the corresponding measObject concerns NR:
measId;
measId;
ETSI
measId;
[TS 38.331, clause 5.5.4.4]
The UE shall:
ETSI
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
with the following:
this measId;
ETSI
1> else:
System Simulator:
- NR Cell 1 is the PCell, NR Cell 2 and NR Cell 4 are the intra-frequency neighbour cells of NR Cell 1.
UE:
- None.
Preamble:
Table 8.1.3.1.16.3.2-1 and 8.1.3.1.16.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR Cell 2
and NR Cell 4 at various time instants of the test execution. Row marked "T0" denotes the conditions after the
preamble, while the configuration marked "T1" is applied at the point indicated in the Main behaviour description in
Table 8.1.3.1.16.3.2-3.
Table 8.1.3.1.16.3.2-1: Time instances of cell power level and parameter changes for NR Cell 1, 2, 4 in
FR1

SS/PBCH dBm/
T0 -85 -91 -91 not satisfied:
SSS EPRE SCS
Mn + Ofn + Ocn – Hys ≦ Mp +
Ofp + Ocp + Off
SS/PBCH dBm/
T1 -85 -78 -91 satisfied:
SSS EPRE SCS
Mn + Ofn + Ocn – Hys > Mp + Ofp +
Ocp + Off
SS/PBCH dBm/
T2 -85 -91 -91 not satisfied:
SSS EPRE SCS
Mn + Ofn + Ocn – Hys ≦ Mp + Ofp
+ Ocp + Off
ETSI
Table 8.1.3.1.16.3.2-2: Time instances of cell power level and parameter changes for NR Cell 1, 2, 4 in
FR2

SS/PBCH dBm/
T0 FFS FFS FFS not satisfied:
SSS EPRE SCS
+ Ocp + Off
SS/PBCH dBm/
T1 FFS FFS FFS satisfied:
SSS EPRE SCS
Mn + Ofn + Ocn – Hys > Mp + Ofp +
Ocp + Off
SS/PBCH dBm/
T2 FFS FFS FFS not satisfied:
SSS EPRE SCS
+ Ocp + Off

U-S Message
event A3 (measId 1)
level according to row "T1" in table
8.1.3.1.16.3.2-1/2.
30s?
message including both NR Cell 2 and NR Cell 4
in whiteCellsToAddModList
for 10s to allow UE measurement
for NR Cell 2?
8.1.3.1.16.3.2-1/2.
10s?
Table 8.1.3.1.16.3.3-1: RRCReconfiguration (step 1 and 5, Table 8.1.3.1.16.3.2-3)
ETSI

measObjectId 1
measObject CHOICE {
measObjectNR MeasObjectNR-f1 Step 1
MeasObjectNR-whitelist Step 5
}
}
}
reportConfigToAddModList Not present Step 5
reportConfigToAddModList SEQUENCE(SIZE 1 entry Step 1
reportConfigId 1
reportConfigNR ReportConfigNR-
EventA3
}
}
}
measIdToAddModList Not present Step 5
measIdToAddModList SEQUENCE (SIZE 1 entry Step 1
measId 1
measObjectId 1
reportConfigId 1
}
}
}

SSB of NR Cell 1
whiteCellsToAddModList SEQUENCE(SIZE (1.. 1 entry
pci-RangeIndex 1
start 900
range Not present
}
}
}
}
ETSI
Table 8.1.3.1.16.3.3-4: MeasObjectNR-whitelist (Table 8.1.3.1.16.3.3-2)

SSB of NR Cell 1
whiteCellsToAddModList SEQUENCE (SIZE 2 entries
(1..maxNrofPCI-Ranges)) OF PCI-RangeElement {
pci-RangeIndex 1
start PhyCellId of NR Cell 2
range n4
}
}
pci-RangeIndex 2
start PhyCellId of NR Cell 4
range n4
}
}
}
}

reportType CHOICE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset CHOICE {
rsrp 0 0dB FR1
FFS FR2
}
useWhiteCellList TRUE
}
}
reportInterval ms10240
rsrp true
rsrq false
sinr false
}
}
}
}
ETSI

measId 1
1
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
2
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}
}
ETSI
8.1.3.1.17 NR CA / Measurement configuration control and reporting / Intra NR

measurements / Event A6

Event A6 / Intra-band Contiguous CA
(1)
with { UE in NR RRC_CONNECTED state and measurements configured for event A6 }
ensure that {
}
(2)
ensure that {
when { Intra-frequency neighbour becomes offset better than SCell }
}
(3)
ensure that {
when { UE receives a RRCReconfiguration message containing sCellToReleaseList with a sCellIndex
equal to one of the current UE SCell configuration }
}
5.3.5.5.9, 5.5.2.1, 5.5.4.1, 5.5.4.7 and 5.5.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
1> else:
configuration;
ETSI
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
(SCell addition):
Editor's Note: FFS Check automatic measurement handling for SCells.
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this
measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this
measId;
modification):
[TS 38.331, clause 5.5.2.1]
The UE shall:
[TS 38.331, clause 5.5.4.1]
ETSI
4> else:
measId;
event):
measId;
measId;
[TS 38.331, clause 5.5.4.7]
ETSI
The UE shall:
1> for this measurement, consider the (secondary) cell corresponding to the measObjectNR associated to this event
to be the serving cell.
NOTE: The reference signal(s) of the neighbour(s) and the reference signal(s) of the SCell are both indicated in
the associated measObjectNR.
Mn + Ocn – Hys > Ms + Ocs + Off
Mn + Ocn + Hys < Ms + Ocs + Off
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within the associated
measObjectNR), and set to zero if not configured for the neighbour cell.
Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within the associated
measObjectNR), and is set to zero if not configured for the serving cell.
Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.
Ocn, Ocs, Hys, Off are expressed in dB.
[TS 38.331, clause 5.5.5]
UE Network
MeasurementReport
ETSI
the following:
measId;
1> else:
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 is the SCell to be added, and NR Cell 12 is the intra-frequency neighbour cell
of NR Cell 3.
- NR Cell 3 is an Inactive SCell according to TS 38.508-1 [4] clause 6.3.1.
ETSI
UE:
- None.
Preamble:
Table 8.1.3.1.17.1.3.2-1 and 8.1.3.1.17.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR
Cell 3 and NR Cell 12 at various time instants of the test execution. Row marked "T0" denotes the conditions after the
preamble, while the configuration marked "T1" is applied at the point indicated in the Main behaviour description in
Table 8.1.3.1.17.1.3.2-3.
Table 8.1.3.1.17.1.3.2-1: Time instances of cell power level and parameter changes in FR1

Power levels are such that entry condition
SS/PBCH
T0 dBm/SCS -82 -88 -94 for event A6 (measId 1) is not satisfied:
SSS EPRE
SS/PBCH
T1 dBm/SCS -82 -88 -78 for event A6 (measId 1) is satisfied:
SSS EPRE
Mn + Ocn - Hys > Ms + Ocs + Off

SS/PBCH
T0 dBm/SCS FFS FFS FFS for event A6 (measId 1) is not satisfied:
SSS EPRE
SS/PBCH
T1 dBm/SCS FFS FFS FFS for event A6 (measId 1) is satisfied:
SSS EPRE
Mn + Ocn – Hys > Ms + Ocs + Off
ETSI

U-S Message
message including sCellToAddModList with
NR Cell 3 as SCell addition.
message including measConfig to setup intra
NR measurement and reporting for event A6.
10s?
6 The SS re-adjusts the SS/PBCH EPRE level - - - -
according to row "T1" in table 8.1.3.1.17.1.3.2-
1/2.
A6 with the measured RSRP value for NR Cell
12?
message including sCellToReleaseList with
NR Cell 3 as SCell release.
10 Check: Does the UE attempt to transmit an - - 3 F
uplink message for the next 15s?
Table 8.1.3.1.17.1.3.3-2: Void
Table 8.1.3.1.17.1.3.3-3: Void
ETSI
Table 8.1.3.1.17.1.3.3-5: MeasConfig (Table 8.1.3.1.17.1.3.3-4)

-f1
measObject CHOICE {
}
}
-f2
measObject CHOICE {
}
}
}
reportConfigId[1] 1
reportConfig[1] CHOICE {
EventA6 8.1.3.1.17.1.3.3-
6
}
}
}
measId[1] 1
measObjectId[1] 2
reportConfigId[1] 1
}
}
}
ETSI
Table 8.1.3.1.17.1.3.3-6: ReportConfigNR-EventA6 (Table 8.1.3.1.17.1.3.3-5)

reportType CHOICE {
eventId CHOICE {
eventA6 SEQUENCE {
a6-Offset CHOICE {
rsrp 0
}
}
}
reportInterval ms10240
rsrp true
rsrq false
sinr false
}
}
}
}
Table 8.1.3.1.17.1.3.3-7: MeasurementReport (step 7, Table 8.1.3.1.17.1.3.2-3)

}
}
}
ETSI
Table 8.1.3.1.17.1.3.3-8: MeasResults (Table 8.1.3.1.17.1.3.3-7)

measId 1
measResultServingMOList SEQUENCE (SIZE 2 entries
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
_Meas
}
}
}
}
}
of NR Cell 3
rsrp (0..127)
rsrq (0..127)
sinr Not present
_Meas
}
}
}
}
}
}
measResultListNR SEQUENCE (SIZE 1 entry Report NR Cell
(1..maxCellReport)) OF MeasResultNR { 12
of NR Cell 12
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
ETSI

masterCellGroup CellGroupConfig Table
8.1.3.1.17.1.3.3-
10
SCell release for
NR Cell 3
dedicatedSIB1-Delivery Not present SCell release
}
}
}
}

SCell release for
NR Cell 3
}
}

Event A6 / Inter-band CA
Same as TC 8.1.3.1.17.1 but applied to Inter-band CA case.
Same as test case 8.1.3.1.17.1 with the following differences:
- CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
- Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12.
ETSI
Same as test case 8.1.3.1.17.1 with the following differences.
NOTE: For simplicity the steps referred below are steps in test case 8.1.3.1.17.1.

-f1
measObject CHOICE {
}
}
}
-f5
measObject CHOICE {
the ARFCN for NR Cell
10
}
}
}
}
reportConfigId 1
EventA6
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
}
ETSI

Event A6 / Intra-band non Contiguous CA
Same as TC 8.1.3.1.17.1 but applied to Intra-band non Contiguous CA case.
- CA configuration: Intra-band non Contiguous CA replaces Intra-band Contiguous CA.
Same as test case 8.1.3.1.17.1 but applied to Intra-band non Contiguous CA case..
8.1.3.1.18 NR CA / Measurement configuration control and reporting / Intra NR

measurements / Additional measurement reporting

Additional measurement reporting / Intra-band Contiguous CA
(1)
with { UE in NR RRC_CONNECTED state and measurements configured for event A2 reporting include
reportAddNeighMeas }
ensure that {
when { Entry condition for event A2 of the concerned frequency that triggered measurement
reporting is met }
then { UE sends MeasurementReport that does not include the best non-serving cell of the
concerned frequency in the measResultBestNeighCell }
}
(2)
with { UE in NR RRC_CONNECTED state and measurements configured for event A2 reporting include
reportAddNeighMeas }
ensure that {
when { Entry condition for event A2 of other than the concerned frequency that triggered
measurement reporting is met }
then { UE sends MeasurementReport that includes the best non-serving cell of the concerned
frequency in the measResultBestNeighCell }
}
ETSI
5.3.5.5.9, 5.5.2.1, 5.5.4.1, 5.5.4.7 and 5.5.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
1> else:
configuration;
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
(SCell addition):
Editor's Note: FFS Check automatic measurement handling for SCells.
measId:
measId;
modification):
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.4.1]
5> consider only the serving cell to be applicable;
measId;
event):
measId;
ETSI
measId;
[TS 38.331, clause 5.5.4.7]
The UE shall:
1> for this measurement, consider the serving cell indicated by the measObjectNR associated to this event.
Ms + Hys < Thresh
Ms – Hys > Thresh
[TS 38.331, clause 5.5.5]
UE Network
MeasurementReport
ETSI
1> if the reportConfig associated with the measId that triggered the measurement reporting includes
reportAddNeighMeas:
2> for each serving cell measObjectId referenced in the measIdList, other than the measObjectId corresponding
with the measId that triggered the measurement reporting:
3> set the measResultBestNeighCell within measResultServingMOList to include the physCellId and the
available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig
of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if
RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with
the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this
measObjectNR, otherwise with the highest measured SINR;
the following:
measId;
ETSI
1> else:
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 is the SCell to be added, NR Cell 12 (broadcast only cell) and NR Cell 23
(broadcast only cell) is the intra-frequency neighbour cell of NR Cell 3.
- Relative SS signal level uncertainty between Intra-freq cells is +/-1 dB for FR1 and FFS for FR2.
UE:
- None.
Preamble:
Table 8.1.3.1.18.1.3.2-1 and 8.1.3.1.18.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR
Cell 3, NR Cell 12 and NR Cell 23 at various time instants of the test execution. Row marked "T0" denotes the
conditions after the preamble, while the configuration marked "T1" and "T2" are applied at the point indicated in the
Main behaviour description in Table 8.1.3.1.18.1.3.2-3.

SS/PBCH dBm/ condition for event A2 is not satisfied:
T0 -82 -82 -91 Off
SSS EPRE SCS Ms + Hys > Thresh for NR Cell 1 and NR
Cell 3
SS/PBCH dBm/ condition for event A2 in NR Cell 3 is
T1 -82 -98 -91 -88
SSS EPRE SCS satisfied:
Ms + Hys < Thresh
T2 -82 -82 -78 -82
Cell 3
T3 -98 -82 -78 -82
Ms + Hys < Thresh
ETSI

T0 FFS FFS FFS Off
Cell 3
T1 FFS FFS FFS Off
Ms + Hys < Thresh
T2 FFS FFS FFS Off
Cell 3
T3 FFS FFS FFS FFS
Ms + Hys < Thresh

U-S Message
message including sCellToAddModList with NR
Cell 3 as SCell addition.
message including measConfig to setup intra
NR measurement and for event A2 reporting
configuration and include reportAddNeighMeas.
5 The SS re-adjusts the SS/PBCH EPRE level - - - -
according to row "T1" in table 8.1.3.1.18.1.3.2-
1/2.
MeasurementReport message that does not
include the RSRP value of the best non-serving
cell on the concerned serving frequency in
measResultBestNeighCell?
8.1.3.1.18.1.3.2-1/2.
7A 30 seconds after step 7, SS re-adjusts the cell- - - - -
specific reference signal level according to row
"T3" in table 8.1.3.1.18.1.3.2-1/2.
MeasurementReport message included the
RSRP value of the best non-serving cell (NR
Cell 12) on the concerned serving frequency in
measResultBestNeighCell?
message containing an sCellToReleaseList with
SCell NR Cell 3.
ETSI
Table 8.1.3.1.18.1.3.3-2: Void
Table 8.1.3.1.18.1.3.3-3: Void
ETSI

-f1
measObject CHOICE {
}
}
-f2
measObject CHOICE {
}
}
}
reportConfigId 1
EventA2 8.1.3.1.18.1.3.3-
6
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
measId 2
measObjectId 2
reportConfigId 1
}
}
}
ETSI
Table 8.1.3.1.18.1.3.3-6: ReportConfigNR-EventA2 (Table 8.1.3.1.18.1.3.3-5)

reportType CHOICE {
eventId CHOICE {
eventA2 SEQUENCE {
a2-Threshold SEQUENCE {
rsrp 67 -89dBm FR1
FFS FR2
}
}
}
reportAmount r1
rsrp true
rsrq false
sinr false
}
reportAddNeighMeas setup
}
}
}
Table 8.1.3.1.18.1.3.3-7: MeasurementReport (step 6, step 8, Table 8.1.3.1.18.1.3.2-3)

measResults MeasResults1 Table Step 6
8.1.3.1.18.1.3.3-
8
MeasResults2 Table Step 8
8.1.3.1.18.1.3.3-
9
}
}
}
ETSI
Table 8.1.3.1.18.1.3.3-8: MeasResults1 (Table 8.1.3.1.18.1.3.3-7)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-79 with Condition A2

MeasResults ::= SEQUENCE { Step 6
measId 2
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
_Meas
}
}
}
}
}
of NR Cell 3
rsrp (0..127)
rsrq (0..127)
sinr Not present
_Meas
}
}
}
}
}
}
}
ETSI
Table 8.1.3.1.18.1.3.3-9: MeasResults2 (Table 8.1.3.1.18.1.3.3-7)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-79 with Condition A2

MeasResults ::= SEQUENCE { Step 8
measId 1
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
_Meas
}
}
}
}
}
of NR Cell 3
rsrp (0..127)
rsrq (0..127)
sinr Not present
_Meas
}
}
}
}
measResultBestNeighCell SEQUENCE { Report NR Cell
12
of NR Cell 12
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
ETSI

}
}
}
}

}
}

Additional measurement reporting / Inter-band CA
- Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12 and NR Cell 31 replaces
NR Cell 23.
- CA configuration: Inter-band CA replaces Inter-band Contiguous CA
- Cells configuration: NR Cell 10 replaces NR Cell 3, NR Cell 30 replaces NR Cell 12 and NR Cell 31 replaces
NR Cell 23.
ETSI
Same as test case 8.1.3.1.18.1 with the following differences.

-f1
measObject CHOICE {
}
}
}
measObjectId[2] 2 MeasObjectIdNR
-f5
measObject[2] CHOICE {
the ARFCN for NR Cell
10
}
}
}
}
reportConfigId 1
EventA2
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
measId 2
measObjectId 2
reportConfigId 1
}
}
}
ETSI

Additional measurement reporting / Intra-band non Contiguous CA
- CA configuration: Intra-band non Contiguous CA replaces Inter-band Contiguous CA.
Same as test case 8.1.3.1.18.1 but applied to Intra-band non Contiguous CA case.
8.1.3.1.19 Measurement configuration control and reporting / Inter-frequency

measurements/ SFTD
(1)
with { UE in NR RRC_CONNECTED state with reportSFTD-NeighMeas configured }
ensure that {
when { The sfn-OffsetResult and frameBoundaryOffsetResult results become available }
then { UE transmits a MeasurementReport message including the MeasResultCellListSFTD-NR IE }
}
5.5.2.1, 5.5.3.1, 5.5.4.1, and 5.5.5.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
...
...
1> else (RRCReconfiguration was received via SRB1):
configuration;
ETSI
...
[TS 38.331, clause 5.5.2.1]
The network applies the procedure as follows:
- to ensure that, whenever the UE has a measConfig associated with a CG, it includes a measObject for the SpCell
and for each NR SCell of the CG to be measured;
,,,
- when the UE is in NE-DC, NR-DC, or NR standalone, to configure at most one measurement identity across all
CGs using a reporting configuration with the reportType set to reportSFTD;
...
The UE shall:
...
...
...
...
[TS 38.331, clause 5.5.3.1]
The UE shall:
1> whenever the UE has a measConfig, perform RSRP and RSRQ measurements for each serving cell for which
servingCellMO is configured as follows:
2> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig
contains an rsType set to ssb and ssb-ConfigMobility is configured in the measObject indicated by the
servingCellMO:
...
3> derive serving cell measurement results based on SS/PBCH block, as described in 5.5.3.3;
...
...
2> if the reportType for the associated reportConfig is set to reportSFTD and the numberOfReportsSent as
defined within the VarMeasReportList for this measId is less than one:
...
ETSI
3> else if the reportSFTD-NeighMeas is included:
4> if the measObject is associated to NR:
5> if the drx-SFTD-NeighMeas is included:
6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected
based on parameters in the associated measObject using available idle periods;
5> else:
6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected
based on parameters in the associated measObject;
5> if the reportRSRP is set to true:
6> perform RSRP measurements based on SSB for the NR neighbouring cell(s) detected based on
parameters in the associated measObject;
2> perform the evaluation of reporting criteria as specified in 5.5.4.
[TS 38.331, clause 5.5.4.1]
...
2> else if the corresponding reportConfig includes a reportType set to reportSFTD:
...
4> else if the reportSFTD-NeighMeas is included:
5> if cellsForWhichToReportSFTD is configured in the corresponding reportConfig:
6> consider any NR neighbouring cell detected on the associated measObjectNR which has a
physical cell identity that is included in the cellsForWhichToReportSFTD to be applicable;
5> else:
6> consider up to 3 strongest NR neighbouring cells detected based on parameters in the

associated measObjectNR to be applicable when the concerned cells are not included in the
blackCellsToAddModList defined within the VarMeasConfig for this measId;
...
2> if the corresponding reportConfig includes a reportType is set to reportSFTD:
...
4> else
5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity
to be reported becomes available for each requested pair of PCell and NR cell or the maximal
measurement reporting delay as specified in TS 38.133 [14];
...
[TS 38.331, clause 5.5.5.1]
ETSI
UE Network
MeasurementReport
...
...
2> else if the reportSFTD-NeighMeas is included within the corresponding reportConfigNR for this measId:
3> for each applicable cell which measurement results are available, include an entry in the
measResultCellListSFTD-NR and set the contents as follows:
4> set physCellId to the physical cell identity of the concerned NR neighbour cell.
4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower
layers;
4> if the reportRSRP is set to true:
5> set rsrp-Result to the RSRP of the concerned cell derived based on SSB;
...
...
1> else:
System Simulator:
- NR Cell 1 is the PCell, NR Cell 10 is the inter-frequency neighbour cell.
- System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR PCell.
UE:
- None.
Preamble:
- The UE is in state RRC_CONNECTED using generic procedure parameter Connectivity (NR) established
according to TS 38.508-1 [4], clause 4.5.4.
ETSI

U-S Message
message including MeasConfig to setup inter-
frequency SFTD measurement on NR neighbour
cell (NR Cell 10)
MeasurementReport message including
measResultCellListSFTD-NR within the next 5s?
NOTE 1
NOTE 1: Time limit is chosen based on the inter-frequency SFTD measurement reporting delay requirements
specified in TS 38.133 [30] clause 9.3.8.
ETSI

measObjectId 1
measObject CHOICE {
measObjectNR MeasObjectNR-1 for NR Cell 1
}
}
measObjectId 2
measObject CHOICE {
measObjectNR MeasObjectNR-2 for NR Cell 10
}
}
reportConfigToAddModList SEQUENCE (SIZE 1 entry
reportConfigId 1
reportConfigNR ReportConfigNR Table
8.1.3.1.19.3.3-5
}
}
}
(1..maxMeasId)) OF MeasIdToAddMod {
measId 1
measObjectId 2
reportConfigId 1
}
}
measGapConfig MeasGapConfig specified
in 38.508-1 [4] Table
4.6.3-70
}
Table 8.1.3.1.19.3.3-3: MeasObjectNR-1 (Table 8.1.3.1.19.3.3-2)

ssbFrequency ARFCN-ValueNR of NR
Cell 1
}
Table 8.1.3.1.19.3.3-4: MeasObjectNR-2 (Table 8.1.3.1.19.3.3-2)

ssbFrequency ARFCN-ValueNR of NR
Cell 10
}
ETSI
Table 8.1.3.1.19.3.3-5: ReportConfigNR (Table 8.1.3.1.19.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-142 with condition SFTD_NEIGHBOUR

reportType CHOICE {
reportSFTD SEQUENCE {
reportRSRP true
reportSFTD-NeighMeas true
}
}
}
Table 8.1.3.1.19.3.3-6: MeasResults (step 3, Table 8.1.3.1.19.3.2-1)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-79 with condition SFTD_NEIGHBOUR

measId 1
measResultCellListSFTD-NR SEQUENCE (SIZE 1 entry
(1..maxCellSFTD)) OF MeasResultCellSFTD-NR {
MeasResultCellSFTD-NR[1] SEQUENCE { entry 1
sfn-OffsetResult (0..1023)
frameBoundaryOffsetResult (-30720..30719)
rsrp-Result (0..127)
}
}
}
8.1.3.1.20 Measurement configuration control and reporting / Measurement Gaps / gapFR1
(1)
ensure that {
when { UE receives RRCReconfiguration message containing MeasConfig to setup gapFR1 and report
periodical measurements for neighbour cell on FR1 frequency }
then { UE applies gapFR1 and sends periodical measurements for neighbour cell on FR1 frequency }
}
5.5.2.1, 5.5.2.9, 5.5.4.1, 5.5.4.5 and 5.5.5.1. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
1> else:
ETSI
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
[TS 38.331, clause 5.5.2.9]
The UE shall:
1> if gapFR1 is set to setup:
2> if an FR1 measurement gap configuration is already setup, release the FR1 measurement gap configuration;
2> setup the FR1 measurement gap configuration indicated by the measGapConfig in accordance with the
condition:
[TS 38.331, clause 5.5.4.1]
ETSI
5> else:
2> if reportType is set to periodical and if a (first) measurement result is available:
3> if the reportAmount exceeds 1:
4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to
be reported becomes available for the NR SpCell;
3> else (i.e. the reportAmount is equal to 1):
be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells;
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
ETSI
with the following:
4> else:
5> 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;
1> else:
1> else:
System Simulator:
- NR Cell 1 is the serving cell, NR Cell 3 is the inter-frequency neighbour cell of NR Cell 1.
ETSI
UE:
- None.
Preamble:
Table 8.1.3.1.20.3.2-1/2 illustrates the downlink power levels to be applied for NR Cell 1 and NR Cell 3 at various time
instants of the test execution. Row marked "T1" are applied at the point indicated in the Main behaviour description in
Table 8.1.3.1.20.3.2-3.

Cell 1 Cell3
SS/PBCH dBm/
T1 -85 -79
SSS EPRE SCS

Cell 1 Cell3
SS/PBCH dBm/
T1 FFS FFS
SSS EPRE SCS
ETSI

U-S Message
8.1.3.1.20.3.2-1/2.
message to setup FR1 independent gap (pattern
#0) and inter-frequency measurement on NR
Cell 3.
3 Check: Does the UE transmit at least 10 --> NR RRC: MeasurementReport 1 P
MeasurementReport messages to periodically
report the measured RSRP value for NR Cell 3
within the next 30 seconds?
3A The SS waits and ignores MeasurementReport - - - -
messages for 3s to allow UE to measure NR
Cell 3.
4 The SS transmits an RRCReconfiguration to <-- NR RRC: RRCReconfiguration - -
change gap pattern to pattern #1.
RRCReconfigurationComplete message to RRCReconfigurationComplete
confirm the change of pattern.
- EXCEPTION: Steps 7 to 9 shall be repeated for
each gap pattern among #2 - #11 and supported
by UE (indicated in supportedGapPattern).
change gap pattern to the next pattern
supported by UE.
confirm the change of gap pattern.
Table 8.1.3.1.20.3.3-1: RRCReconfiguration (steps 1, 4 and 7, Table 8.1.3.1.20.3.2-3)
ETSI

measObjectToAddModList Not present Step 4 OR
Step 7
measObjectToAddModList SEQUENCE (SIZE 2 entries Step 1
measObjectId 1
measObject CHOICE {
8.1.3.1.20.3.3-3
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.20.3.3-4
}
}
}
reportConfigToAddModList Not present Step 4 OR
Step 7
reportConfigId 1
reportConfigNR ReportConfigNR with
condition PERIODICAL
}
}
}
measIdToAddModList Not present Step 4 OR
Step 7
measId 1
measObjectId 2
reportConfigId 1
}
}
measGapConfig MeasGapConfig-gapFR1 Table
8.1.3.1.20.3.3-5
}
ETSI

SSB of NR Cell 1
smtc1 SEQUENCE {
sf20 0 To make sure
SMTC for intra-
frequency
measurement is
non-overlapping
with MG
}
}
}

SSB of NR Cell 3
smtc1 SEQUENCE {
sf20 10
}
}
}
Table 8.1.3.1.20.3.3-5: MeasGapConfig-gapFR1 (Table 8.1.3.1.20.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-70 with condition GAP_FR1

MeasGapConfig ::= SEQUENCE {
gapFR1 CHOICE {
setup SEQUENCE {
gapOffset 9
mgl ms3 Pattern #2, #3, #10 or #11
ms4 Pattern #6, #7, #8 or #9
ms6 Pattern #0, #1, #4 or #5
mgrp ms20 Pattern #4, #6 or #10
ms40 Pattern #0, #2 or #7
mgta ms0
}
}
}
ETSI
Table 8.1.3.1.20.3.3-6: MeasurementReport (steps 3, 6 and 9, Table 8.1.3.1.20.3.2-3)

measId 1
1
rsrp (0..127)
rsrq (0..127)
R_Meas
Not present
}
}
}
}
}
}
3
of NR Cell 3
rsrp (0..127)
rsrq (0..127)
R_Meas
Not present
}
}
}
}
}
}
}
}
}
}
ETSI
8.1.3.1.21 Measurement configuration control and reporting / Measurement Gaps / gapFR2
(1)
ensure that {
when { UE receives RRCReconfiguration message containing MeasConfig to setup gapFR2 and report
periodical measurements for neighbor cell on FR2 frequency }
then { UE applies gapFR2 and sends periodical measurements for neighbor cell on FR2 frequency }
}
[TS 38.331, clause 5.3.5.3]
1> else:
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.2.9]
The UE shall:
condition:
[TS 38.331, clause 5.5.4.1]
5> else:
ETSI
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
with the following:
4> else:
ETSI
1> else:
1> else:
System Simulator:
- NR Cell 1 is the serving cell, NR Cell 3 is the inter-frequency neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
ETSI

U-S Message
message to setup FR2 independent gap (pattern
#13) and inter-frequency measurement on NR
Cell 3.
change gap pattern to pattern #14.
confirm the change of pattern.
- EXCEPTION: Steps 7 to 9 shall be repeated for
each gap pattern among #12 and #15 - #23 and
supported by UE (indicated in
supportedGapPattern).
change gap pattern to the next pattern
supported by UE.
confirm the change of gap pattern.
Table 8.1.3.1.21.3.3-1: RRCReconfiguration (step 1, 4 and 7, Table 8.1.3.1.21.3.2-2)
ETSI

measObjectToAddModList Not present Step 4 OR
Step 7
measObjectToAddModList SEQUENCE (SIZE 2 entries Step 1
measObjectId 1
measObject CHOICE {
8.1.3.1.21.3.3-3
}
}
measObjectId 2
measObject CHOICE {
8.1.3.1.21.3.3-4
}
}
}
reportConfigToAddModList Not present Step 4 OR
Step 7
reportConfigId 1
}
}
}
measIdToAddModList SEQUENCE (SIZE Not present Step 4 OR
Step 7
measId 1
measObjectId 2
reportConfigId 1
}
}
measGapConfig MeasGapConfig-gapFR2 Table
8.1.3.1.21.3.3-5
}
ETSI

SSB of NR Cell 1
smtc1 SEQUENCE {
sf20 10 To make sure
SMTC for intra-
frequency
measurement is
non-overlapping
with MG
}
}
}

SSB of NR Cell 3
smtc1 SEQUENCE {
sf20 0
}
}
}
Table 8.1.3.1.21.3.3-5: MeasGapConfig-gapFR2 (Table 8.1.3.1.21.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-70 with Condition GAP_FR2

gapFR2 CHOICE {
setup SEQUENCE {
gapOffset 0
mgl ms1dot5 Pattern #20, #21, #22 or #23
ms3dot5 Pattern #16, #17, #18 or #19
ms5dot5 Pattern #12, #13, #14 or #15
mgrp ms20 Pattern #12, #16 or #20
ms40 Pattern #13, #17 or #21
ms80 Pattern #14, #18 or #22
ms160 Pattern #15, #19 or #23
mgta ms0
}
}
}
ETSI

measId 1
1
rsrp (0..127)
rsrq (0..127)
R_Meas
Not present
}
}
}
}
}
}
3
of NR Cell 3
rsrp (0..127)
rsrq (0..127)
R_Meas
Not present
}
}
}
}
}
}
}
}
}
}
ETSI
8.1.3.1.22 Void

Periodic reporting / Continuation of the measurements after RRC Resume
(1)
ensure that {
when { UE receives RRCReconfiguration including measConfig to setup periodical measurement
reporting }
then { UE sends RRCReconfigurationComplete and starts sending periodic measurement reports }
}
(2)
with { UE in NR RRC_INACTIVE state and measurement configured for periodical reporting }
ensure that {
when { UE receives RRCResume message without including measconfig }
then { UE resumes RRC connection and performs periodic measurements as per the measurement
configuration }
}
(3)
with { UE in NR RRC_INACTIVE state and measurement configured for periodical reporting }
ensure that {
when { UE receives RRCResume message including the measconfig }
then { UE resumes RRC connection and performs periodic measurements as per the received
measconfig in RRCResume message }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.3.13.4, 5.5.2
and 5.5.4.1.
[TS 38.331, clause 5.3.13.4]
The UE shall:
1> release the suspendConfig except the ran-NotificationAreaInfo;
1> resume SRB2 and all DRBs;
1> if the RRCResume message includes the measConfig:
1> resume measurements if suspended;
1> enter RRC_CONNECTED;
1> indicate to upper layers that the suspended RRC connection has been resumed;
ETSI
1> submit the RRCResumeComplete message to lower layers for transmission;
1> the procedure ends.
[TS 38.331, clause 5.3.13.4]
The UE shall:
[TS 38.331, clause 5.5.4.1]
4> if corresponding reportConfig includes reportType set to periodical; or
5> if useWhiteCellList is set to true:
to be applicable when the concerned cell is included in the whiteCellsToAddModList defined
5> else:
ETSI
System Simulator:
- NR Cell 1 is the serving cell, NR Cell 2 is the intra-frequency neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
- The UE is in state 3N-A in NR Cell 1 as defined in TS 38.508-1 [4], subclause 4.4A.
Tables 8.1.3.1.23.3.2-1 and 8.1.3.1.23.3.2-2 illustrate the downlink power levels to be applied for NR Cell 1 and NR
Cell 2 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble.
Table 8.1.3.1.23.3.2-1: Power levels in FR1

Cell 1 Cell 2
SS/PBCH dBm/
T0 -85 -91
SSS EPRE SCS

Cell 1 Cell 2
SS/PBCH dBm/
T0 FFS FFS
SSS EPRE SCS
ETSI

U-S Message
message including MeasConfig to setup intra
NR periodic measurement reporting.
2A The SS waits and ignores MeasurementReport --> NR RRC: MeasurementReport - -
Cell 2.
30 seconds?
behaviour that depends on UE configuration; the
"lower case letter" identifies a step sequence
that takes place if inactiveState is configured
4a1 IF pc_inactiveState THEN the SS transmits an <-- NR RRC: RRCRelease - -
RRCRelease message with suspendConfig.
4a2 The SS waits for 5 sec and transmits a Paging - NR RRC: Paging - -
message including a matched identity (correct
fullI-RNTI).
4a3 UE transmits RRCResumeRequest message --> NR RRC: RRCResumeRequest - -
4a4 The SS transmits an RRCResume message <-- NR RRC: RRCResume - -
without including MeasConfig.
4a5 The UE transmits an RRCResumeComplete --> NR RRC: - -
message. RRCResumeComplete
4a6 The SS waits and ignores MeasurementReport --> NR RRC: MeasurementReport - -
Cell 2.
4a7 Check: Does the UE transmit at least 10 --> NR RRC: MeasurementReport 2 P
30 seconds?
4a8 The SS transmits an RRCRelease message with <-- NR RRC: RRCRelease - -
suspendConfig.
4a9 The SS waits for 5 sec and transmits a Paging - NR RRC: Paging - -
message including a matched identity (correct
fullI-RNTI).
4a1 UE transmits RRCResumeRequest message --> NR RRC: RRCResumeRequest - -
0
4a1 The SS transmits an RRCResume message <-- NR RRC: RRCResume - -
1 including MeasConfig.
4a1 The UE transmits an RRCResumeComplete --> NR RRC: - -
2 message. RRCResumeComplete
4a1 The SS waits and ignores MeasurementReport --> NR RRC: MeasurementReport - -
3 messages for 3s to allow UE to measure NR
Cell 2.
4a1 Check: Does the UE transmit at least 10 --> NR RRC: MeasurementReport 3 P
4 MeasurementReport messages within the next
30 seconds?
5- Void - - - -
16
ETSI

-f1
measObject CHOICE {
}
}
}
}
reportConfigId 1
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
}
}
ETSI
Table 8.1.3.1.23.3.3-3: MeasurementReport (step 3 and step 4a7, Table 8.1.3.1.23.3.2-3)

measId 1
servCellId Cell index corresponding to
NR Cell 1
of NR Cell 1
}
}
}
measResultListNR SEQUENCE (SIZE (1.. 1 entry
maxCellReport)) OF MeasResultNR {
of NR Cell 2
measResult Not Checked
}
}
}
}
}
}
}
Table 8.1.3.1.23.3.3-4: RRCRelease (step 4a1 and step 4a8, Table 8.1.3.1.23.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-16 with condition NR_RRC_INACTIVE
Table 8.1.3.1.23.3.3-5: Paging (step 4a2 and step 4a9, Table 8.1.3.1.23.3.2-3)
Derivation Path: TS 38.508-1 [4] Table 4.6.1-9 with condition NR_RRC_RESUME
Table 8.1.3.1.23.3.3-6: RRCResumeRequest (step 4a3 and step 4a10, Table 8.1.3.1.23.3.2-3)

resumeCause mt-Access
}
}
ETSI
Table 8.1.3.1.23.3.3-7: RRCResume (step 4a11, Table 8.1.3.1.23.3.2-3)

measConfig MeasConfigResume
}
}
}
Table 8.1.3.1.23.3.3-8: MeasConfigResume (Table 8.1.3.1.23.3.3-7)

-f1
measObject CHOICE {
}
}
}
}
reportConfigId 1
}
}
}
measId[1] 1
}
measId 2
measObjectId 1
reportConfigId 1
}
}
}
ETSI
Table 8.1.3.1.23.3.3-9: MeasurementReport (step 4a14, Table 8.1.3.1.23.3.2-3)

measId 2
NR Cell 1
of NR Cell 1
}
}
}
of NR Cell 2
measResult Not Checked
}
}
}
}
}
}
}
8.1.3.2 Inter-RAT measurements
8.1.3.2.1 Measurement configuration control and reporting / Inter-RAT measurements /

Event B1 / Measurement of E-UTRA cells
(1)
with { UE is NR RRC_CONNECTED state and inter-RAT measurement event B1 to measure neighbour E-UTRA
cell is configured }
ensure that {
when { Entering condition for the event B1 is not met }
then { UE does not transmit any MeasurementReport }
}
(2)
with { UE is NR RRC_CONNECTED state and inter-RAT measurement event B1 to measure neighbour E-UTRA
ensure that {
when { Entering condition for the event B1 is met }
then { UE transmits a MeasurementReport }
}
ETSI
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clauses 5.3.5.3, 5.5.2,
[TS 38.331, clause 5.3.5.3]
3> else:
NOTE: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random
Access procedure towards the SCG is left to UE implementation.
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the
new configuration;
1> else:
configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment
procedure;
3> resume SRB1 and DRBs that are suspended;
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.2.9]
The UE shall:
1> else if gapUE is set to release:
2> release the per UE measurement gap configuration.
NOTE 1: For gapFR2 configuration, the SFN and subframe of a serving cell on FR2 frequency is used in the gap
calculation
NOTE 2: For gapFR1 or gapUE configuration, the SFN and subframe of the PCell is used in the gap calculation.
[TS 38.331, clause 5.5.4.1]
be applicable when the concerned cell is included in the whiteCellsToAddModList defined
5> else:
3> else if the corresponding measObject concerns E-UTRA;
4> consider any neighbouring cell detected on the associated frequency to be applicable when the
concerned cell is not included in the blackCellsToAddModListEUTRAN defined within the
ETSI
measId;
measId;
measId;
2> upon the expiry of T321 for this measId:
[TS 38.331, clause 5.5.4.8]
The UE shall:
1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled;
Inequality B1-1 (Entering condition)
ETSI
Inequality B1-2 (Leaving condition)
Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.
Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-
OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the neighbour inter-
RAT cell).
Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the
measObjectEUTRA corresponding to the neighbour inter-RAT cell), and set to zero if not configured for the
neighbour cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).
Thresh is the threshold parameter for this event (i.e. b1-ThresholdEUTRA as defined within reportConfigInterRAT
for this event).
Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.
[TS 38.331, clause 5.5.5]
UE Network
MeasurementReport
reportQuantityRsIndexes and maxNrofRSIndexesToReport:
2> for each serving cell configured with servingCellMO, include beam measurement information according to
the associated reportConfig as described in 5.5.5.2;
ETSI
with the following:
this measId;
9> if reportQuantityRsIndexesand maxNrofRSIndexesToReport are configured, include

6> if the measObject associated with this measId concerns E-UTRA:
7> set the measResult to include the quantity(ies) indicated in the reportQuantity within the
concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as
specified in 5.5.5.3, i.e. the best cell is included first;
procedure ends;
2> else:
1> else:
ETSI
System Simulator:
- NR Cell 1 is the PCell, E-UTRA Cell 1 is the inter-RAT neighbour cell of NR Cell 1.
- System information combination NR-6 as defined in TS 38.508-1 [4] clause 4.4.3.1.2.
UE:
- None.
Preamble:
Table 8.1.3.2.1.3.2-1 and 8.1.3.2.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, and E-UTRA
Cell 1 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while
the configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.1.3.2.1.3.2-
3.

Cell 1 Cell 1
SS/PBCH dBm/ Power levels are such that entry
-85 -
SSS EPRE SCS condition for event B1 is not
T0
Cell-specific dBm/15 satisfied:
-93
RS EPRE kHz Mn + Ofn + Ocn + Hys < Thresh
SS/PBCH dBm/
-85 - Power levels are such that entry
SSS EPRE SCS
T1 condition for event B1 is satisfied:
Cell-specific dBm/15
-73 Mn + Ofn + Ocn – Hys > Thresh
RS EPRE kHz

Cell 1 Cell 1
FFS -
T0
Cell-specific dBm/15 satisfied:
FFS
RS EPRE kHz Mn + Ofn + Ocn + Hys < Thresh
SS/PBCH dBm/
FFS - Power levels are such that entry
SSS EPRE SCS
FFS Mn + Ofn + Ocn – Hys > Thresh
RS EPRE kHz
ETSI

U-S Message
RAT measurement and reporting for event B1.
10s?
1/2.
B1 with the measured RSRP value for NR Cell
1?
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13with condition NR_MEAS
ETSI

-f1
measObject CHOICE {
}
}
}
measObjectId 2 MeasObjectIdE-
UTRA-f1
measObject CHOICE {
measObjectEUTRA SEQUENCE {
E-UTRA Cell 1
}
}
}
}
reportConfigId 1
reportConfigInterRAT ReportConfigInterRAT- Table
EventB1 8.1.3.2.1.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
quantityConfig QuantityConfig with
condition INTER-RAT
}
ETSI
Table 8.1.3.2.1.3.3-3: ReportConfigInterRAT-EventB1 (Table 8.1.3.2.1.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-141 with condition EVENT_B1

reportType CHOICE {
eventId CHOICE {
eventB1 SEQUENCE {
b1-ThresholdEUTRA SEQUENCE {
rsrp 61 -80dBm FR1
FFS FFS FR2
}
}
}
reportAmount r1
}
}
}
ETSI

measId 1 Step 5
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
measResultListEUTRA SEQUENCE (SIZE (1.. 1 entry Report E-UTRA
maxCellReport)) OF MeasResultEUTRA { neighbour cell
MeasResultEUTRA[1] SEQUENCE { entry 1
eutra-PhysCellId Physical layer cell identity Step 5
of E-UTRA Cell 1
rsrp (0..97)
rsrq (0..34)
sinr Not present
}
}
}
}
}
}
}

Event B2 / Measurement of E-UTRA cells
(1)
with { UE is NR RRC_CONNECTED state and inter-RAT measurement event B2 to measure neighbor E-UTRA
ensure that {
when { Entering condition 1 for event B2 is not met but Entering condition 2 is met }
}
ETSI
(2)
ensure that {
when { Entering condition 1 and 2 for event B2 is met }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clauses 5.3.5.3, 5.5.2,
[TS 38.331, clause 5.3.5.3]
3> else:
NOTE: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random
Access procedure towards the SCG is left to UE implementation.
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the
new configuration;
1> else:
configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment
procedure;
3> resume SRB2 and DRBs that are suspended;
[TS 38.331, clause 5.5.2.1]
ETSI
The UE shall:
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
[TS 38.331, clause 5.5.4.1]
ETSI
be applicable when the concerned cell is included in the whiteCellsToAddModList defined
5> else:
measId;
measId;
measId;
ETSI
[TS 38.331, clause 5.5.4.9]
The UE shall:
1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as
1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least
Inequality B2-1 (Entering condition 1)
Mp + Hys < Thresh1
Inequality B2-3 (Leaving condition 1)
Mp is the measurement result of the PCell, not taking into account any offsets.
OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the inter-RAT
neighbour cell).
neighbour cell.
Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRAT for
this event).
Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2EUTRA as defined within
reportConfigInterRAT for this event).
Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR.
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.
Thresh1 is expressed in the same unit as Mp.
[TS 38.331, clause 5.5.5]
ETSI
UE Network
MeasurementReport
reportQuantityRsIndexes and maxNrofRSIndexesToReport:
with the following:
this measId;
9> if reportQuantityRsIndexesand maxNrofRSIndexesToReport are configured, include

ETSI
procedure ends;
2> else:
1> else:
System Simulator:
UE:
- None.
Preamble:
Table 8.1.3.2.2.3.2-1 and 8.1.3.2.2.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, and E-UTRA
3.
ETSI

Cell 1 Cell 1
SS/PBCH dBm/ condition 1 for event B2 is not
-78 -
SSS EPRE SCS satisfied and entry condition 2 is
T0
satisfied:
Cell-specific dBm/15 Mp + Hys > Thresh1 and
-73
RS EPRE kHz Mn + Ofn + Ocn - Hys > Thresh2
-90 -
SSS EPRE SCS condition for event B2 is satisfied:
T1
Cell-specific dBm/15 Mp + Hys < Tresh1 and
-73

Cell 1 Cell 1
FFS -
T0
satisfied:
Cell-specific dBm/15 Mp + Hys > Thresh1 and
FFS
FFS -
T1
Cell-specific dBm/15 Mp + Hys < Tresh1 and
FFS

U-S Message
10s?
1/2.
1?
ETSI

-f1
measObject CHOICE {
}
}
}
measObjectId 2 MeasObjectIdE-
UTRA-f1
measObject CHOICE {
measObjectEUTRA SEQUENCE {
E-UTRA Cell 1
}
}
}
}
reportConfigId 1
EventB2 8.1.3.2.2.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
Condition INTER-RAT
}
ETSI

reportType CHOICE {
eventId CHOICE {
eventB2 SEQUENCE {
b2-Threshold1 SEQUENCE {
rsrp 73 -83dBm FR1
FFS FFS FR2
}
b2-Threshold2EUTRA SEQUENCE {
rsrp 58 -83dBm FR1
FFS FFS FR2
}
}
}
reportAmount r1
}
}
}
ETSI

measId 1
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
measResultListEUTRA SEQUENCE (SIZE (1.. 1 entry Report E-UTRA
maxCellReport)) OF MeasResultEUTRA { neighbour cell
eutra-PhysCellId Physical layer cell identity
of E-UTRA Cell 1
rsrp (0..97)
rsrq (0..34)
sinr Not present
}
}
}
}
}
}
}

Event B2 / Measurement of E-UTRA cells / RSRQ based measurements
(1)
cell is configured and triggerQuantity set to rsrq }
ensure that {
when { Entering condition 1 and 2 for event B2 is not met }
}
ETSI
(2)
cell is configured and triggerQuantity set to rsrq }
ensure that {
}
5.5.2.1, 5.5.4.1, 5.5.4.9 and 5.5.5.
[TS 38.331, clause 5.3.5.3]
[TS 38.331, clause 5.5.2.1]
The UE shall:
1> if the received measConfig includes the measObjectToRemoveList:
2> perform the measurement object removal procedure as specified in 5.5.2.4;
1> if the received measConfig includes the reportConfigToRemoveList:
2> perform the reporting configuration removal procedure as specified in 5.5.2.6;
1> if the received measConfig includes the measGapSharingConfig:
2> perform the measurement gap sharing configuration procedure as specified in 5.5.2.11;
1> if the received measConfig includes the s-MeasureConfig:
ETSI
2> if s-MeasureConfig is set to ssb-RSRP, set parameter ssb-RSRP of s-MeasureConfig within VarMeasConfig
to the lowest value of the RSRP ranges indicated by the received value of s-MeasureConfig;
2> else, set parameter csi-RSRP of s-MeasureConfig within VarMeasConfig to the lowest value of the RSRP
ranges indicated by the received value of s-MeasureConfig.
[TS 38.331, clause 5.5.4.1]
measId;
measId;
measId;
ETSI
[TS 38.331, clause 5.5.4.9]
The UE shall:
Mp + Hys < Thresh1
neighbour cell).
neighbour cell.
this event).
ETSI
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:
with the following:
this measId;
ETSI
1> else:
System Simulator:
- Cell 1 is the NR serving cell, E-UTRA Cell 1 is the inter-RAT neighbour cell.
UE:
- None.
Preamble:
Table 8.1.3.2.3.3.2-1 and 8.1.3.2.3.3.2-2 illustrate the downlink power levels to be applied for NR Cell 1 and E-UTRA
Cell 1 at various time instants of the test execution for FR1 and FR2 respectively. 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.
Parameter Unit NR Cell 1 E-UTRA Cell Remark

T0 SS/PBCH dBm/SCS -88 - Power levels are such that entry condition for event
SSS B2 is not satisfied:
EPRE Mp + Hys ≥ Thresh1 or Mn + Ofn + Ocn – Hys ≤
SS-RSRQ dB -11.74 - Thresh2
Cell- dBm/15kHz - -94
specific
RS EPRE
RSRQ dB - -11.46
Noc dBm/SCS -94 -
Noc dBm/15kHz - -94
T1 SS/PBCH dBm/SCS -88 - Power levels are such that entry condition for event
SSS B2 is satisfied:
EPRE Mp + Hys < Thresh1 and Mn + Ofn + Ocn – Hys >
SS-RSRQ dB -11.74 - Thresh2
Cell- dBm/15kHz - -80
specific
RS EPRE
RSRQ dB - -3.94
ETSI
Parameter Unit NR Cell 1 E-UTRA Cell 2 Remark

T0 SS/PBCH dBm/SCS FFS - Power levels are such that entry condition for event
SSS B2 is not satisfied:
EPRE Mp + Hys ≥ Thresh1 or Mn + Ofn + Ocn – Hys ≤
SS-RSRQ dB FFS - Thresh2
Cell- dBm/15kHz - FFS
specific
RS EPRE
RSRQ dB - FFS
Noc dBm/SCS FFS -
Noc dBm/15kHz - FFS
T1 SS/PBCH dBm/SCS FFS - Power levels are such that entry condition for event
SSS B2 is satisfied:
EPRE Mp + Hys < Thresh1 and Mn + Ofn + Ocn – Hys >
SS-RSRQ dB FFS - Thresh2
Cell- dBm/15kHz - FFS
specific
RS EPRE
RSRQ dB - FFS

U-S Message
to setup inter-RAT measurement and reporting
for event B2
NR Cell 1.
8.1.3.2.3.3.2-1/2.
MeasurementReport message on Cell 1 to
report event B2 with the measured RSRP and
RSRQ values for E-UTRA Cell 1?
Derivation Path: TS 38.508-1 [4] table 4.6.1-13 with condion NR_MEAS
ETSI

measObjectId 1
measObject CHOICE {
8.1.3.2.3.3.3-
3
}
}
measObjectId 2
measObject CHOICE {
measObjectEUTRA MeasObjectEUTRA-f2 Table
8.1.3.2.3.3.3-
4
}
}
}
reportConfigInterRAT ReportConfigInterRAT-B2 Table
8.1.3.2.3.3.3-
5
}
}
}
measId 1
measObjectId 2
}
}
condition INTER-RAT
measGapConfig MeasGapConfig Table
8.1.3.2.3.3.3-
6
}

cell 1 SSB
}
ETSI
Table 8.1.3.2.3.3.3-4: MeasObjectEUTRA-f2 (Table 8.1.3.2.3.3.3-2)

MeasObjectEUTRA::= SEQUENCE {
carrierFreq Downlink ARFCN of E-
UTRA Cell 1
}
Table 8.1.3.2.3.3.3-5: ReportConfigInterRAT-B2 (Table 8.1.3.2.3.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-141 with condition EVENT_B2

ReportConfigInterRAT::= SEQUENCE {
reportType CHOICE {
eventId CHOICE {
eventB2 SEQUENCE {
b2-Threshold1 CHOICE {
rsrq 79 Actual value = -4dB
}
b2-Threshold2EUTRA CHOICE {
rsrq 23 Actual value = -8dB
}
hysteresis Hysteresis
timeToTrigger ms0
}
}
reportInterval ReportInterval
}
}
}
Table 8.1.3.2.3.3.3-6: MeasGapConfig (Table 8.1.3.2.3.3.3-2)

gapUE CHOICE {
setup SEQUENCE {
gapOffset 0
mgl ms6
mgrp ms40
mgta ms0
}
}
}
ETSI
Table 8.1.3.2.3.3.3-7: MeasurementReport (steps 5, Table 8.1.3.2.3.3.3-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-5A

measId 1 Step 5
measResultServingMOList SEQUENCE (SIZE
MeasResultServMO[1] SEQUENCE { 1 entry entry 1
serving cell
physCellId PhysCellId of NR
serving cell
rsrp (0..127)
rsrq (0..127)
sinr Not present
Not checked pc_ss_SINR_Meas
}
}
}
}
}
}
MeasResultListEUTRA SEQUENCE (SIZE 1 entry
(1..maxCellReport)) OF MeasResultEUTRA {
eutra-PhysCellId PhysCellId of E- Step 5
UTRA Cell 1
rsrp (0..97)
rsrq (0..34)
sinr Not present
}
}
}
}
}
}
}

Event B2 / Measurement of E-UTRA cells / SINR based measurements
(1)
cell is configured and triggerQuantity set to sinr }
ensure that {
when { Entering condition 1 and 2 for event B2 is not met }
}
ETSI
(2)
cell is configured and triggerQuantity set to sinr }
ensure that {
}
[TS 38.331, clause 5.3.5.3]
1> else:
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
[TS 38.331, clause 5.5.4.1]
3> else if the corresponding measObject concerns E-UTRA:
measId;
ETSI
measId;
measId;
3> if reportOnLeave is set to true for the corresponding reporting configuration:
[TS 38.331, clause 5.5.4.9]
The UE shall:
Mp + Hys < Thresh1
neighbour cell).
ETSI
neighbour cell.
this event).
[TS 38.331, clause 5.5.5.1]
UE Network
MeasurementReport
with the following:
this measId;
ETSI
1> else:
System Simulator:
- NR Cell 1 is the serving cell, EUTRA Cell 1 is the inter-RAT neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
Table 8.1.3.2.4.3.2-1 and 8.1.3.2.4.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1 and EUTRA
the configuration marked "T1", is applied at the point indicated in the Main behaviour description in Table
8.1.3.2.4.3.2-3.
ETSI
Table 8.1.3.2.4.3.2-1: Time instances of cell power level and parameter changes for NR Cell 1 and E-
UTRA Cell 1 in FR1

Cell 1 Cell 1
SS/PBCH dBm/
-79 -
SSS EPRE SCS
Cell-specific dBm/15 conditions for event B2 are not
- -91
RS EPRE kHz satisfied:
T0 dBm/15 1) Mp + Hys ≥ Thresh1 and
Noc - -82
kHz
2) Mn + Ofn + Ocn – Hys ≤
dBm/
Noc -94 - Thresh2
SCS
SINR - 15 -9
SS/PBCH dBm/
-91 -
SSS EPRE SCS
Cell-specific dBm/15 Power levels are such that entry
- -73
RS EPRE kHz condition for event B2 are
T1 dBm/15 satisfied:
Noc - -82
kHz 1) Mp + Hys < Thresh1 and
dBm/ Mn + Ofn + Ocn – Hys > Thresh2
Noc -94 -
SCS
SINR - 3 9
Table 8.1.3.2.4.3.2-2: Time instances of cell power level and parameter changes for NR Cell 1 and E-
UTRA Cell 1 in FR2

Cell 1 Cell 1
SS/PBCH dBm/
FFS -
SSS EPRE SCS
Cell-specific dBm/15 conditions for event B2 are not
- FFS
RS EPRE kHz satisfied:
T0 dBm/15 1) Mp + Hys ≥ Thresh1 and
Noc - FFS
kHz
2) Mn + Ofn + Ocn – Hys ≤
dBm/
Noc FFS - Thresh2
SCS
SINR - FFS FFS
SS/PBCH dBm/
FFS -
SSS EPRE SCS
Cell-specific dBm/15 Power levels are such that entry
- FFS
RS EPRE kHz condition for event B2 are
T1 dBm/15 satisfied:
Noc - FFS
kHz Mp + Hys < Thresh1 and
dBm/ Mn + Ofn + Ocn – Hys > Thresh2
Noc FFS -
SCS
SINR - FFS FFS
ETSI

U-S Message
message including MeasConfig to setup EUTRA
measurement and reporting for inter-RAT event
B2.
MeasurementReport message with event B2 for
EUTRA Cell 1 within the next 10s?
1/2.
MeasurementReport message with event B2 for
EUTRA Cell 1 within the next 10s?
ETSI

measObjectId 1
measObject CHOICE {
8.1.3.2.4.3.3-3
}
}
measObjectId 2
measObject CHOICE {
measObjectEUTRA MeasObjectEUTRA-f2 Table
8.1.3.2.4.3.3-4
}
}
}
reportConfigId 1
EventB2 8.1.3.2.4.3.3-5
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
condition INTER-RAT
}

SSB of NR Cell 1
}
ETSI
Table 8.1.3.2.4.3.3-4: MeasObjectEUTRA-f2 (Table 8.1.3.2.4.3.3-2)

MeasObjectEUTRA::= SEQUENCE {
CRS of E-UTRA Cell 1
}

ReportConfigInterRAT ::= SEQUENCE {
reportType CHOICE {
eventId CHOICE {
eventB2 SEQUENCE {
sinr 64 Actual value = FR1
9dB
FFS FR2
}
sinr 46 0 dB
}
hysteresis 4 2 dB
}
}
reportAmount r1
reportQuantity SEQUENCE {
rsrp true
rsrq true
sinr true
}
}
}
}
ETSI

measId 1
1
rsrp (0..127)
rsrq (0..127)
sinr (0..127)
}
}
}
}
}
}
measResultListEUTRA SEQUENCE (SIZE (1.. 1 entry Measurement
maxCellReport)) OF MeasResultEUTRA { report for EUTRA
Cell 1
eutra-PhysCellId PhysCellId of EUTRA Cell
1
rsrp (0..97)
rsrq (0..34)
sinr (0..127)
}
}
}
}
}
}
}
8.1.3.2.5 Void

Event B1 / NR to UMTS
(1)
with { UE is NR RRC_CONNECTED state and inter-RAT measurement event B1 to measure neighbour UTRA
ensure that {
when { Entering condition for the event B1 is not met }
}
ETSI
(2)
ensure that {
when { Entering condition for the event B1 is met }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.331 [12], clause 5.5.4.1,
5.5.4.8 and 5.5.5.1.
[TS 38.331, clause 5.5.4.1]
3> else if the corresponding measObject concerns UTRA-FDD:
4> if eventB1-UTRA-FDD or eventB2-UTRA-FDD is configured in the corresponding reportConfig; or
4> if corresponding reportConfig includes reportType set to periodical:
5> 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;
measId;
3> if useT312 is set to true in reportConfig for this event:
4> if T310 for the corresponding SpCell is running; and
4> if T312 is not running for corresponding SpCell:
5> start timer T312 for the corresponding SpCell with the value of T312 configured in the
corresponding measObjectNR;
[TS 38.331, clause 5.5.4.8]
The UE shall:
1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled.
Inequality B1-1 (Entering condition)
ETSI
Inequality B1-2 (Leaving condition)
OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the neighbour inter-
RAT cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the
frequency of the neighbour inter-RAT cell).
neighbour cell.
Thresh is the threshold parameter for this event (i.e. b1-ThresholdEUTRA as defined within reportConfigInterRAT
for this event, b1-ThresholdUTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event).
Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.
[TS 38.331, clause 5.5.5.1]
with the following:
this measId;
4> else:

ETSI
7> else if rsType in the associated reportConfig is set to csi-rs:
8> set resultsCSI-RS-Cell within the measResult to include the CSI-RS based quantity(ies)
indicated in the reportQuantityCell within the concerned reportConfig, in decreasing
order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is
included first;

6> if the measObject associated with this measId concerns UTRA-FDD and if
ReportConfigInterRAT includes the reportQuantityUTRA-FDD:
7> set the measResult to include the quantity(ies) indicated in the reportQuantityUTRA-FDD
within the concerned reportConfigInterRAT in decreasing order of the sorting quantity,
determined as specified in 5.5.5.3, i.e. the best cell is included first;
System Simulator:
- NR Cell 1 is the PCell, UTRA Cell 1 is the inter-RAT neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
Table 8.1.3.2.6.3.2-1 and 8.1.3.2.6.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, and UTRA
3.
Parameter Unit NR UTRA Remark

Cell 1 Cell 1
-85 -
T0
Cell-specific dBm/3.84 satisfied:
-93
CPICH_Ec MHz Mn + Ofn + Ocn + Hys < Thresh
SS/PBCH dBm/
-85 - Power levels are such that entry
SSS EPRE SCS
Cell-specific dBm/3.84
-73 Mn + Ofn + Ocn – Hys > Thresh
CPICH_Ec MHz
ETSI

Cell 1 Cell 1
FFS -
T0
Cell-specific dBm/3.84 satisfied:
FFS
CPICH_Ec MHz Mn + Ofn + Ocn + Hys < Thresh
SS/PBCH dBm/
FFS - Power levels are such that entry
SSS EPRE SCS
FFS Mn + Ofn + Ocn – Hys > Thresh
CPICH_Ec MHz

U-S Message
10s?
8.1.3.2.6.3.2-1/2.
1?
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13, condition NR_MEAS


-f1
measObject CHOICE {
}
}
}
measObjectId 2 MeasObjectIdUT
RA-FDD-r16
measObject CHOICE {
measObjectUTRA-FDD-r16 SEQUENCE {
carrierFreq-r16 ARFCN-ValueUTRA-
FDD-r16 for UTRA Cell 1
utra-FDD-Q-OffsetRange-r16 Not present
cellsToRemoveList-r16 Not present
cellsToAddModList-r16 Not present
}
}
}
}
reportConfigId 1
EventB1 8.1.3.2.6.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
condition INTER-RAT
}
ETSI

reportType CHOICE {
eventId CHOICE {
eventB1-UTRA-FDD-r16 SEQUENCE {
b1-ThresholdUTRA-FDD-r16 CHOICE {
utra-FDD-RSCP-r16 61 -80dBm FR1
FFS FFS FR2
}
}
}
reportAmount r1
}
}
}
ETSI

measId 1 Step 5
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
}
}
}
}
}
}
measResultListUTRA-FDD-r16 SEQUENCE 1 entry Report UTRA
(SIZE (1.. maxCellReport)) OF MeasResultListUTRA- neighbour cell
FDD-r16 {
MeasResultUTRA-FDD-r16[1] SEQUENCE { entry 1
physCellId-r16 Physical layer cell identity Step 5
of UTRA Cell 1
measResult-r16 SEQUENCE {
utra-FDD-RSCP-r16 (-5..91)
utra-FDD-EcN0-r16 Not present
}
}
}
}
}
}
}

Event B2 / NR to UMTS
(1)
ensure that {
when { Entering condition 1 for event B2 is not met but Entering condition 2 is met }
}
(2)
ETSI
ensure that {
}
[TS 38.331, clause 5.3.5.3]
The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the
conditional reconfiguration (CHO or CPC):
[TS 38.331, clause 5.5.2.1]
The UE shall:
[TS 38.331, clause 5.5.2.9]
condition:
2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the
measurement mgta ms before the gap subframe occurrences);
1> else if gapFR1 is set to release:
ETSI
2> release the FR1 measurement gap configuration;
condition:
configuration;
condition:
[TS 38.331, clause 5.5.4.1]
ETSI
measId;
measId;
measId;
3> if reportOnLeave is set to true for the corresponding reporting configuration:
for one or more applicable transmission resource pools for all measurements taken during timeToTrigger
defined for this event within the VarMeasConfig, while the VarMeasReportList does not include an
measurement reporting entry for this measId (a first transmission resource pool triggers the event):
3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the
VarMeasReportList for this measId;
ETSI
for one or more applicable transmission resource pools not included in the poolsTriggeredList for all
measurements taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent
transmission resource pool triggers the event):
3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the
for one or more applicable transmission resource pools included in the poolsTriggeredList defined within the
VarMeasReportList for this measId for all measurements taken during timeToTrigger defined within the
3> remove the concerned transmission resource pool(s) in the poolsTriggeredList defined within the
3> if the poolsTriggeredList defined within the VarMeasReportList for this measId is empty:
4> stop the periodical reporting timer for this measId, if running
[TS 38.331, clause 5.5.4.9]
The UE shall:
Mp + Hys < Thresh1
neighbour cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the
frequency of the neighbour inter-RAT cell).
ETSI
neighbour cell.
this event).
reportConfigInterRAT for this event, b2-Threshold2UTRA-FDD as defined for UTRA-FDD within
[TS 38.331, clause 5.5.5.1]
with the following:
System Simulator:
UE:
- None.
Preamble:
ETSI
3.

Cell 1 Cell 1
-78 -
T0
satisfied:
Cell-specific dBm/3.84 Mp + Hys > Thresh1 and
-73
CPICH_Ec MHz Mn + Ofn + Ocn - Hys > Thresh2
-85 -
T1
Cell-specific dBm/3.84 Mp + Hys < Tresh1 and
-73

Cell 1 Cell 1
FFS -
T0
satisfied:
Cell-specific dBm/3.84 Mp + Hys > Thresh1 and
FFS
FFS -
T1
Cell-specific dBm/3.84 Mp + Hys < Tresh1 and
FFS

U-S Message
10s?
8.1.3.2.7.3.2-1/2.
1?
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13, condition NR_MEAS


-f1
measObject CHOICE {
}
}
}
RA-FDD-r16
measObject CHOICE {
}
}
}
}
reportConfigId 1
EventB2 8.1.3.2.7.3.3-3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
condition INTER-RAT
}
ETSI

reportType CHOICE {
eventId CHOICE {
eventB2-UTRA-FDD-r16 SEQUENCE {
b2-Threshold1-r16 SEQUENCE {
rsrp 73 -83dBm FR1
FFS FFS FR2
}
b2-Threshold2UTRA-FDD-r16 SEQUENCE {
rsrp 58 -83dBm FR1
FFS FFS FR2
}
}
}
reportAmount r1
}
}
}
ETSI

measId 1
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
}
}
}
}
}
}
FDD-r16 {
MeasResultListUTRA-FDD-r16[1] SEQUENCE { entry 1
physCellId-r16 Physical layer cell identity
of UTRA Cell 1
}
}
}
}
}
}
}

Periodic reporting / NR to UTRA
(1)
with { UE is NR RRC_CONNECTED state and periodic inter-RAT measurement reporting of neighbour UTRA
cells is configured }
ensure that {
when { The UE receives reference signal power of UTRA cell where measurements are configured }
then { UE sends MeasurementReport message at regular intervals }
}
(2)
with { UE is NR RRC_CONNECTED state with periodic measurement reporting of UTRA cells ongoing }
ensure that {
ETSI
when { The UE receives a RRCConnectionReconfiguration message removing the measId of periodic

reporting of NR cells }
then { UE stops sending MeasurementReport message for UTRA cells }
}
5.5.2.1, 5.5.4.1 and 5.5.5.1. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.3.5.3]
[TS 38.331, clause 5.5.2.1]
The UE shall:
[TS 38.331, clause 5.5.2.9]
condition:
ETSI
condition:
configuration;
condition:
[TS 38.331, clause 5.5.4.1]
2> else if the purpose is included and set to reportStrongestCells, reportStrongestCellsForSON, reportLocation
or sidelink and if a (first) measurement result is available:
3> if the purpose is set to reportStrongestCells and reportStrongestCSI-RSs is not included:
ETSI
4> if the triggerType is set to periodical and the corresponding reportConfig includes the ul-
DelayConfig:
5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first
measurement result is provided by lower layers;
4> else if the reportAmount exceeds 1:
to be reported becomes available for the PCell;
to be reported becomes available for the PCell and for the strongest cell among the applicable
cells, or becomes available for the pair of PCell and the PSCell in case of SSTD measurements, or
becomes available for each requested pair of PCell and NR cell or the maximal measurement
reporting delay as specified in TS 38.133 [X, 8.17.2.3] in case of SFTD measurements;
3> else:
4> initiate the measurement reporting procedure, as specified in 5.5.5, when it has determined the
strongest cells on the associated frequency;
2> upon expiry of the T321 for this measId:
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 PCell RSRP being equal to or better than s-
Measure or due to the measurement gap not being setup.
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 38.331, clause 5.5.5.1]
with the following:
ETSI
System Simulator:
UE:
- None.
Preamble:
3.

Cell 1 Cell 1
SS/PBCH dBm/
-78 -
SSS EPRE SCS
T0
- Off
CPICH_Ec MkHz
SS/PBCH dBm/
-78 -
SSS EPRE SCS
T1
- -85
CPICH_Ec MkHz

Cell 1 Cell 1
SS/PBCH dBm/
-82 -
SSS EPRE SCS
T0
- Off
CPICH_Ec MkHz
SS/PBCH dBm/
-82 -
SSS EPRE SCS
T1
- -85
CPICH_Ec MkHz
ETSI

U-S Message
message including measConfig to setup inter
RAT measurements and reporting for UTRA
cells.
3 The SS changes UTRA Cell 1 parameters - - - -
messages for 8 s to allow for the switching of
cells and UE measurement.
perform periodical reporting for UTRA Cell 1?
RRCConnectionReconfiguration message
including measConfig to remove inter RAT
measurements of UTRA cells from periodic
reporting.
8 Check: Does the UE transmit a --> 2 F
MeasurementReport message in the next 10s?
Derivation path: 38.508-1 [4], Table 4.6.1-13, condition NR_MEAS
ETSI

-f1
measObject CHOICE {
}
}
}
RA-FDD-r16
measObject CHOICE {
}
}
}
}
reportConfigId 1
reportConfig ReportConfigInterRAT-
PERIODICAL-UTRA
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
quantityConfig QuantityConfig-UTRA
}
ETSI
Table 8.1.3.2.8.3.3-3: ReportConfigInterRAT-PERIODICAL-UTRA (Table 8.1.3.2.8.3.3-2)
Derivation Path: 38.508-1 [4] Table 4.6.3-141 with condition PERIODICAL

reportType CHOICE {
periodical SEQUENCE {
reportQuantityUTRA-FDD-r16 SEQUENCE {
cpich-RSCP TRUE
cpich-EcN0 FALSE
}
}
}
}
Table 8.2.3.3.1.3.3-4: QuantityConfig-UTRA (Table 8.1.3.2.8.3.3-2)

QuantityConfig ::= SEQUENCE {
QuantityConfigUTRA-FDD-r16 SEQUENCE {
filterCoefficientRSCP-r16 FilterCoefficient
filterCoefficientRSCP-r16 FilterCoefficient
}
}
ETSI
Derivation Path: 38.508-1 [4] Table 4.6.1-5A

measId 1
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
}
}
}
}
}
}
FDD-r16 {
MeasResultListUTRA-FDD-r16[1] SEQUENCE { entry 1
physCellId-r16 Physical layer cell identity
of UTRA Cell 1
}
}
}
}
}
}
}

(1..maxMeasId)) OF MeasId {
measId[1] 1 entry 1
}
}
ETSI
8.1.3.3 Measurement for self-optimized networks
8.1.3.3.1 Measurement configuration control and reporting / CGI reporting of NR cell
(1)
ensure that {
when { Neighbour NR cell becomes offset better than serving }
then { UE sends MeasurementReport for event A3 }
}
(2)
ensure that {
when { UE is commanded to report the global cell identity of the neighbour NR 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 }
}
[TS 38.331, clause 5.3.5.3]
1> else (MCG RRCReconfiguration):
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.2.3]
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 reportType is set to reportCGI in the reportConfig associated with this measId:
4> if the measObject associated with this measId concerns FR1:
5> start timer T321 with the timer value set to 2 seconds for this measId;
4> if the measObject associated with this measId concerns FR2:
5> start timer T321 with the timer value set to 16 seconds for this measId.
[TS 38.331, clause 5.5.3.1]
The UE shall:
servingCellMO:
2> if the reportType for the associated reportConfig is set to reportCGI and timer T321 is running:
3> perform the corresponding measurements on the frequency and RAT indicated in the associated
measObject using available idle periods;
3> if the cell indicated by reportCGI field for the associated measObject is an NR cell and that indicated cell
is broadcasting SIB1 (see TS 38.213 [13], clause 13):
ETSI
4> try to acquire SIB1 in the concerned cell;
2> if the reportType for the associated reportConfig is periodical or eventTriggered:
3> if the UE does not require measurement gaps to perform the concerned measurements:
4> if s-MeasureConfig is not configured
5> if the measObject is associated to NR and the rsType is set to ssb:
6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig

are configured:
7> derive layer 3 beam measurements only based on SS/PBCH block for each measurement
quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;
6> derive cell measurement results based on SS/PBCH block for the trigger quantity and each
measurement quantity indicated in reportQuantityCell using parameters from the associated
measObject, as described in 5.5.3.3;
[TS 38.331, clause 5.5.4.1]
4> if corresponding reportConfig includes reportType set to periodical; or
5> else:
2> else if the corresponding reportConfig includes a reportType set to reportCGI:
3> consider the cell detected on the associated measObject which has a physical cell identity matching the
value of the cellForWhichToReportCGI included in the corresponding reportConfig within the
VarMeasConfig to be applicable;
ETSI
measId;
2> if reportType is set to reportCGI:
3> if the UE acquired the SIB1 or SystemInformationBlockType1 for the requested cell; or
3> if the UE detects that the requested NR cell is not transmitting SIB1 (see TS 38.213 [13], clause 13):
4> stop timer T321;
[TS 38.331, clause 5.5.4.4]
The UE shall:
ETSI
[TS 38.331, clause 5.5.5]
UE Network
MeasurementReport
2> else:
3> if SSB based serving cell measurements are available:
available SINR of the serving cell, derived based on SSB;
3> else if CSI-RS based serving cell measurements are available:
ETSI
available SINR of the serving cell, derived based on CSI-RS;
with the following:
this measId;
2> else:
3> if the cell indicated by cellForWhichToReportCGI is an NR cell:
4> if plmn-IdentityInfoList of the cgi-Info for the concerned cell has been obtained:
5> include the plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if available),

ranac (if available) and cellIdentity for each entry of the plmn-IdentityInfoList;
5> include frequencyBandList if available;
4> else if MIB indicates the SIB1 is not broadcast:
5> include the noSIB1 including the ssb-SubcarrierOffset and pdcch-ConfigSIB1 obtained from MIB
of the concerned cell;
ETSI
1> else:
System Simulator:
- NR Cell 1 is the PCell, NR Cell 2 is the intra-frequency neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
Table 8.1.3.3.1.3.2-1 and 8.1.3.3.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, and NR Cell
configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.1.3.3.1.3.2-3.

SS/PBCH dBm/
SSS EPRE SCS
Mn + Ofn + Ocn – Hys < Mp + Ofp +
Ocp + Off
SS/PBCH dBm/ condition for event A3 is satisfied:
T1 -85 -79
SSS EPRE SCS Mn + Ofn + Ocn – Hys > Mp + Ofp +
Ocp + Off

SS/PBCH dBm/
SSS EPRE SCS
Mn + Ofn + Ocn – Hys < Mp + Ofp +
Ocp + Off
SS/PBCH dBm/ condition for event A3 is satisfied:
T1 FFS FFS
SSS EPRE SCS Mn + Ofn + Ocn – Hys > Mp + Ofp +
Ocp + Off
ETSI

U-S Message
message including MeasConfig to setup intra-
frequency measurement and reporting for event
A3.
1/2.
2?
message including measConfig including
reportCGI for Cell 2 and sufficient idle periods
for UE to acquire the relevant system
information from Cell 2
MeasurementReport message with CGI of Cell 2
within 2 sec if Cell 2 is in FR1 (or within 16 sec if
Cell 2 is in FR2)?
Table 8.1.3.3.1.3.3-2: CellGroupConfig-DRX (Table 8.1.3.3.1.3.3-1)
Derivation Path: TS 508-1 [4], Table 4.6.3-19 with condition MEAS

8.1.3.3.1.3.3-9
}
ETSI
Table 8.1.3.3.1.3.3-3: MeasConfig-A3 (Table 8.1.3.3.1.3.3-1)

measObjectId 1
measObject CHOICE {
}
}
}
}
reportConfigToAddModList SEQUENCE(SIZE 2 entries
reportConfigId 1
8.1.3.3.1.3.3-4
}
}
reportConfigId 2
reportConfigNR ReportConfigNR-CGI Table
8.1.3.3.1.3.3-5
}
}
}
measId 1
measObjectId 1
reportConfigId 1 reportConfigId
for event A3
}
}
}
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with Condition EVENT_A3

reportType CHOICE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset CHOICE {
rsrp 2 1 dB (2*0.5 dB)
}
}
}
reportAmount r1
}
}
}
ETSI
Table 8.1.3.3.1.3.3-5: ReportConfigNR-CGI (Table 8.1.3.3.1.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with Condition CGI

reportType CHOICE {
reportCGI SEQUENCE {
cellForWhichToReportCGI PhysCellId of NR Cell 2
}
}
}

measConfig MeasConfig-CGI Table
8.1.3.3.1.3.3-7
masterCellGroup CellGroupConfig-DRX Table
8.1.3.3.1.3.3-2
}
}
}
}
Table 8.1.3.3.1.3.3-7: MeasConfig-CGI (Table 8.1.3.3.1.3.3-6)

measObjectToAddModList Not present
reportConfigToAddModList Not present
measId 1
measObjectId 1
for CGI
measurement
}
}
}
ETSI
Table 8.1.3.3.1.3.3-8: MeasurementReport (step 4 and step 7, Table 8.1.3.3.1.3.2-3)

measId 1
of NR Cell 1
resultsSSB-Cell Not Checked Step 7
resultsSSB-Cell SEQUENCE { Step 4
rsrp (0..127)
rsrq (0..127)
R_Meas
Not present
}
}
}
}
}
}
of NR Cell 2
resultsSSB-Cell Not present Step 7
rsrp (0..127)
rsrq (0..127)
R_Meas
}
}
}
cgi-Info Not present Step 4
cgi-Info SEQUENCE { Step 7
plmn-IdentityInfoList Set according to specific
message content
frequencyBandList Set according to specific
message content
noSIB1 Not present
}
}
}
}
}
}
}
}
ETSI
Table 8.1.3.3.1.3.3-9: MAC-CellGroupConfig
Derivation Path: TS 38.508-1 [4], Table 4.6.3-68 with Condition DRX

drx-Config CHOICE {
setup SEQUENCE {
ms640 0
}
}
}
}
8.1.3.3.2 Measurement configuration control and reporting / CGI reporting of E-UTRA cell
(1)
ensure that {
when { UE detects that entering condition 1 and 2 for event B2 is met }
then { UE transmits a MeasurementReport for event B2 }
}
(2)
ensure that {
when { UE is commanded to report the global cell identity of the neighbour E-UTRA 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 }
}
[TS 38.331, clause 5.3.5.3]
1> else (MCG RRCReconfiguration):
configuration;
[TS 38.331, clause 5.5.2.1]
The UE shall:
ETSI
[TS 38.331, clause 5.5.2.3]
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 reportType is set to reportCGI in the reportConfig associated with this measId:
4> start timer T321 with the timer value set to 1 second for this measId;
[TS 38.331, clause 5.5.2.9]
The UE shall:
configuration;
condition:
ETSI
[TS 38.331, clause 5.5.3.1]
The UE shall:
servingCellMO:
2> if the reportType for the associated reportConfig is set to reportCGI and timer T321 is running:
3> perform the corresponding measurements on the frequency and RAT indicated in the associated
measObject using available idle periods;
3> if the cell indicated by reportCGI field is an E-UTRA cell:
4> try to acquire SystemInformationBlockType1 in the concerned cell;
2> if the reportType for the associated reportConfig is periodical or eventTriggered:
3> if a measurement gap configuration is setup
4> if s-MeasureConfig is not configured
5> if the measObject is associated to E-UTRA:
6> perform the corresponding measurements associated to neighbouring cells on the frequencies
indicated in the concerned measObject, as described in 5.5.3.2;
[TS 38.331, clause 5.5.4.1]
ETSI
3> else if the corresponding measObject concerns E-UTRA:
4> if eventB1 or eventB2 is configured in the corresponding reportConfig:
5> consider a serving cell, if any, on the associated E-UTRA frequency as neighbour cell;
4> else:
2> else if the corresponding reportConfig includes a reportType set to reportCGI:
3> consider the cell detected on the associated measObject which has a physical cell identity matching the
value of the cellForWhichToReportCGI included in the corresponding reportConfig within the
VarMeasConfig to be applicable;
measId;
2> if reportType is set to reportCGI:
3> if the UE acquired the SIB1 or SystemInformationBlockType1 for the requested cell
4> stop timer T321;
ETSI
[TS 38.331, clause 5.5.4.9]
The UE shall:
Mp + Hys < Thresh1
neighbour cell).
neighbour cell.
this event).
[TS 38.331, clause 5.5.5]
ETSI
UE Network
MeasurementReport
with the following:
this measId;
ETSI
2> else:
3> if the cell indicated by cellForWhichToReportCGI is an E-UTRA cell:
4> if all mandatory fields of the cgi-Info-EPC for the concerned cell have been obtained:
5> include in the cgi-Info-EPC the fields broadcasted in E-UTRA SystemInformationBlockType1

associated to EPC;
4> if the UE is E-UTRA/5GC capable and all mandatory fields of the cgi-Info-5GC for the concerned cell
have been obtained:
5> include in the cgi-Info-5GC the fields broadcasted in E-UTRA SystemInformationBlockType1

associated to 5GC;
4> if the mandatory present fields of the cgi-Info for the cell indicated by the cellForWhichToReportCGI
in the associated measObject have been obtained:
5> include the freqBandIndicator;
5> if the cell broadcasts the multiBandInfoList, include the multiBandInfoList;
5> if the cell broadcasts the freqBandIndicatorPriority, include the freqBandIndicatorPriority;
1> else:
System Simulator:
UE:
- None.
Preamble:
Table 8.1.3.3.2.3.2-1 and 8.1.3.3.2.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, and NR Cell
configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 8.1.3.3.2.3.2-3.
ETSI
Parameter Unit NR Cell 1 E-UTRA Remark

Cell 1
(DL only)
SS/PBCH dBm/S Power levels are such that entry
-85 -
SSS EPRE CS condition for event B2 is not
T0 satisfied:
- -91 Mp + Hys < Thresh1 and
RS EPRE kHz
Mn + Ofn + Ocn - Hys < Thresh2
-85 -
SSS EPRE CS condition for event B2 is satisfied:
T1
Cell-specific dBm/15 Mp + Hys < Thresh1 and
- -79
Parameter Unit NR Cell 1 E-UTRA Remark

Cell 1
(DL only)
FFS -
SSS EPRE CS condition for event B2 is not
T0 satisfied:
- FFS Mp + Hys < Thresh1 and
RS EPRE kHz
Mn + Ofn + Ocn - Hys < Thresh2
FFS -
SSS EPRE CS condition for event B2 is satisfied:
T1
Cell-specific dBm/15 Mp + Hys < Thresh1 and
- FFS

U-S Message
1/2.
B2 with the measured RSRP value for E-UTRA
Cell 1?
message including measConfig including
reportCGI for E-UTRA Cell 1 and sufficient idle
periods for UE to acquire the relevant system
information from E-UTRA Cell 1
MeasurementReport message with CGI of E-
UTRA Cell 1 within 1 sec?
ETSI
Table 8.1.3.3.2.3.3-2: CellGroupConfig-DRX (Table 8.1.3.3.2.3.3-1)
Derivation Path: TS 508-1 [4], Table 4.6.3-19 with condition MEAS

8.1.3.3.2.3.3-9
}
Table 8.1.3.3.2.3.3-3: MeasConfig-B2 (Table 8.1.3.3.2.3.3-1)

measObjectId 1
measObject CHOICE {
}
}
}
measObjectId 2
measObject CHOICE {
measObjectEUTRA MeasObjectEUTRA MO for E-UTRA
Cell 1
}
}
}
reportConfigId 1
B2 8.1.3.3.2.3.3-4
}
}
reportConfigId 2
CGI 8.1.3.3.2.3.3-5
}
}
measId 1
measObjectId 2
for event B2
}
}
Condition INTER-RAT
}
ETSI
Table 8.1.3.3.2.3.3-4: ReportConfigInterRAT-B2 (Table 8.1.3.3.2.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-141 with Condition EVENT_B2

reportType CHOICE {
eventId CHOICE {
eventB2 SEQUENCE {
rsrp 77 -79 dBm FR1
FFS FR2
}
rsrp 56 -85dBm
}
}
}
reportAmount r1
}
}
}
Table 8.1.3.3.2.3.3-5: ReportConfigInterRAT-CGI (Table 8.1.3.3.2.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-141 with Condition CGI

reportType CHOICE {
reportCGI SEQUENCE {
cellForWhichToReportCGI EUTRA-PhysCellId of E-
UTRA Cell 1
}
}
}

measConfig MeasConfig-CGI Table
8.1.3.3.2.3.3-7
masterCellGroup CellGroupConfig-DRX Table
8.1.3.3.2.3.3-2
}
}
}
}
ETSI
Table 8.1.3.3.2.3.3-7: MeasConfig-CGI (Table 8.1.3.3.2.3.3-6)

measObjectToAddModList Not present
reportConfigToAddModList Not present
measId 1
measObjectId 2
for CGI
measurement
}
}
}
ETSI
Table 8.1.3.3.2.3.3-8: MeasurementReport (step 4 and step 7, Table 8.1.3.3.2.3.2-3)

measId 1
of NR Cell 1
resultsSSB-Cell Not Checked Step 7
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
measResultListEUTRA SEQUENCE (SIZE (1..
maxCellReport)) OF MeasResultEUTRA {
eutra-PhysCellId[1] PhysCellId of E-UTRA Cell
1
measResult[1] SEQUENCE {
rsrp (0..97) Step 4
Not present Step 7
rsrq (0..34) Step 4
Not present Step 7
sinr Not present
}
cgi-Info Not present Step 4
cgi-Info SEQUENCE { Step 7
cgi-info-EPC SEQUENCE {
cgi-info-EPC-legacy Set according to specific
message content
cgi-info-EPC-list Set according to specific
message content
}
cgi-info-5GC Not check
freqBandIndicator Set according to specific
message content
multiBandInfoList Set according to specific
message content
freqBandIndicatorPriority Set according to specific
message content
}
}
}
}
}
}
}
ETSI
Table 8.1.3.3.2.3.3-9: MAC-CellGroupConfig
Derivation Path: TS 38.508-1 [4], Table 4.6.3-68 with Condition DRX

drx-Config CHOICE {
setup SEQUENCE {
ms640 0
}
}
}
}
8.1.4 Handover
8.1.4.1 Intra NR handover
8.1.4.1.1 Void
8.1.4.1.2 Intra NR handover / Success / Inter-frequency
(1)
with { UE in NR RRC_CONNECTED state and having performed the inter-frequency measurements for the
neighbour cell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync with rach-
ConfigDedicated }
then { UE performs handover to the target cell and transmits an RRCReconfigurationComplete
message }
}
(2)
with { UE in NR RRC_CONNECTED state and having performed the inter-frequency measurements for the
neighbour cell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync without rach-
ConfigDedicated }
then { UE performs handover to the target cell and transmits an RRCReconfigurationComplete
message }
}
(3)
with { UE in NR RRC_CONNECTED state}
ensure that {
when { UE receives an RRCReconfiguration message including dedicatedSIB1-Delivery containing SIB1
information with a change of trackingAreaCode }
then { UE reads the updated SIB1 information and sends an RRCReconfigurationComplete message
followed by registration on the new tracking area }
}
(4)
ensure that {
ETSI
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync and

keySetChangeIndicator set to 'true' in MasterKeyUpdate for handover to the target cell }
then { UE performs handover to the target cell with security key update and transmits an
RRCReconfigurationComplete message }
}
5.3.5.5.1, 5.3.5.5.2, 5.5.4.4, 5.2.2.4.2 and 5.3.5.7. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
1> if the RRCReconfiguration includes the masterKeyUpdate:
2> perform security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery:
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
…1> if the RRCReconfiguration message includes the measConfig:
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell
group successfully completes a random access procedure triggered above;
2> stop timer T304 for that cell group;
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 respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN
of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request
configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell
of the MCG, has a common search space configured by searchSpaceSIB1:
ETSI
4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2;
NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast
data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 5.3.5.5.1]
The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In
(NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE-DC, the SCG is configured as
specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig
IE.
1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync:
2> perform Reconfiguration with sync according to 5.3.5.5.2;
2> resume all suspended radio bearers and resume SCG transmission for all radio bearers, if suspended;
1> if the CellGroupConfig contains the mac-CellGroupConfig:
2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;
1> if the CellGroupConfig contains the spCellConfig:
2> configure the SpCell as specified in 5.3.5.5.7;
[TS 38.331, clause 5.3.5.5.2]
2> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical
cell identity indicated by the physCellId;
1> else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity
ETSI
[TS 38.331, clause 5.5.4.4]
The UE shall:
[TS 38.331, clause 5.2.2.4.2]
1> if the cellAccessRelatedInfo contains an entry with the PLMN-Identity of the selected PLMN:
ETSI
2> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, and cellIdentity for the cell as
received in the corresponding PLMN-IdentityInfo containing the selected PLMN;
1> if in RRC_CONNECTED while T311 is not running:
2> disregard the frequencyBandList, if received, while in RRC_CONNECTED;
2> apply the configuration included in the servingCellConfigCommonSIB;
[TS 38.331, clause 5.3.5.7]
The UE shall:
1> if UE is connected to E-UTRA/EPC:
2> upon reception of sk-Counter as specified in TS 36.331 [10]:
3> update the S-KgNB key based on the KeNB key and using the received sk-Counter value, as specified in TS
33.401 [30];
3> derive the KRRCenc and KUPenc keys as specified in TS 33.401 [30];
3> derive the KRRCint and KUPint keys as specified in TS 33.401 [30].
1> else:
2> if the nas-Container is included in the received masterKeyUpdate:
3> forward the nas-Container to the upper layers;
2> if the keySetChangeIndicator is set to true:
3> derive or update the KgNB key based on the KAMF key, as specified in TS 33.501 [11];
2> else:
3> derive or update the KgNB key based on the current KgNB key or the NH, using the nextHopChainingCount
value indicated in the received masterKeyUpdate, as specified in TS 33.501 [11];
2> store the nextHopChainingCount value;
2> derive the keys associated with the KgNB key as follows:
3> if the securityAlgorithmConfig is included in SecurityConfig:
4> derive the KRRCenc and KUPenc keys associated with the cipheringAlgorithm indicated in the
securityAlgorithmConfig, as specified in TS 33.501 [11];
4> derive the KRRCint and KUPint keys associated with the integrityProtAlgorithm indicated in the
3> else:
4> derive the KRRCenc and KUPenc keys associated with the current cipheringAlgorithm, as specified in TS
33.501 [11];
4> derive the KRRCint and KUPint keys associated with the current integrityProtAlgorithm, as specified in
TS 33.501 [11].
NOTE: Ciphering and integrity protection are optional to configure for the DRBs.
ETSI
System Simulator:
- NR Cell 1 is the serving cell and NR Cell 3 is the inter-frequency neighbour cell of NR Cell 1.
UE:
- None.
Preamble:
Table 4.4A.2-3.
Tables 8.1.4.1.2.3.2-1 and 8.1.4.1.2.3.2-2 illustrate the downlink power levels to be applied for NR Cell 1 and NR Cell
configuration marked "T1", T2 and "T3", are applied at the point indicated in the Main behaviour description in Table
8.1.4.1.2.3.2-3.

Cell 1 Cell 3
SS/PBCH dBm/
T0 -85 -91 condition for event A3 is not
SSS EPRE SCS
satisfied
SS/PBCH dBm/
T1 -85 -79 condition for event A3 is satisfied
SSS EPRE SCS
for NR Cell 3
SS/PBCH dBm/
T2 -79 -85 condition for event A3 is satisfied
SSS EPRE SCS
for NR Cell 1
SS/PBCH dBm/
T3 -88 -78
SSS EPRE SCS

Cell 1 Cell 3
SS/PBCH dBm/
T0 FFS FFS condition for event A3 is not
SSS EPRE SCS
satisfied
SS/PBCH dBm/
T1 FFS FFS condition for event A3 is satisfied
SSS EPRE SCS
for NR Cell 3
SS/PBCH dBm/
T2 FFS FFS condition for event A3 is satisfied
SSS EPRE SCS
for NR Cell 1
SS/PBCH dBm/
T3 FFS FFS
SSS EPRE SCS
ETSI

U-S Message
NR measurement and reporting for inter-
frequency event A3.
3 SS adjusts the cell-specific reference signal level - - - -
according to row "T1".
4 Check: Does the UE transmit a --> NR RRC: MeasurementReport - -
3?
message including reconfigurationWithSync with
rach-ConfigDedicated,keySetChangeIndicator
set to true and including nas-Container IE to
order the UE to perform inter-frequency
handover to NR Cell 3
6 Check: Does the UE transmit --> NR RRC: 1, 4 P
Cell 3?
6A Check: Does the test result of generic test - - 1,4 -
data on DRB #n associated with the first PDU
session on NR Cell 3?
NR measurement and reporting for inter-
frequency event A3.
10 Check: Does the UE transmit a --> NR RRC: MeasurementReport - -
1?
message including reconfigurationWithSync
without rach-ConfigDedicated,
keySetChangeIndicator set to true and including
nas-Container IE to order the UE to perform
inter-frequency handover to NR Cell 1
12 Check: Does the UE transmit --> NR RRC: 2, 4 P
Cell 1?
12 Check: Does the test result of generic test - - 2,4 -
A procedure in TS 38.508-1 subclause 4.9.1
including dedicatedSIB1-Delivery containing
SIB1 of NR Cell 3 to order the UE to perform
handover to NR Cell 3.
RRCReconfigurationComplete message on NR RRCReconfigurationComplete
Cell 3?
16 Check: Does UE transmit a REGISTRATION --> NR RRC: ULInformationTransfer 3 P
REQUEST message to update the registration of 5GMM: REGISTRATION
the actual tracking area? REQUEST
ETSI
17 SS responds with REGISTRATION ACCEPT <-- NR RRC: DLInformationTransfer - -

message. 5GMM: REGISTRATION
ACCEPT
18 The UE send a REGISTRATION COMPLETE --> NR RRC: ULInformationTransfer - -
message. 5GMM: REGISTRATION
COMPLETE
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition MEAS
ETSI

measObjectId 1
measObject CHOICE {
}
}
measObjectId 2
measObject CHOICE {
}
}
}
}
reportConfigId 1
EventA3
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
}
}
ETSI
Table 8.1.4.1.2.3.3-3: ReportConfigNR-EventA3 (Table 8.1.4.1.2.3.3-2 and Table 8.1.4.1.2.3.3-8)

reportType CHOICE {
eventId CHOICE {
a3-Offset CHOICE {
rsrp 6 3dB FR1
FFS FR2
}
hysteresis 0 0 dB
timeToTrigger ms640
}
}
reportAmount r1
rsrp true
rsrq false
sinr false
}
}
}
}
ETSI

measId 1
NR Cell 1
of NR Cell 1
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
of NR Cell 3
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}
}
ETSI
Derivation Path: TS 38.508-1 [4] Table 4.8.1-1A with condition RBConfig_KeyChange

measConfig SEQUENCE {
measObjectToRemoveList SEQUENCE (SIZE 2 entries
measObjectId[1] 1 entry 1
}
measId[1] 1 entry 1
}
}
masterCellGroup OCTET STRING
(CONTAINING
CellGroupConfig)
keySetChangeIndicator True
nas-Container NASContainer Intra N1 mode
NAS transparent
container
}
}
}
}
}
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change and CFRA
spCellConfigCommon SEQUENCE { Same as default
ServingCellConfigComm
on
physCellId Physical cell Id of NR
Cell 3
}
Uplink RACH-ConfigDedicated
}
}
}
}
ETSI
Table 8.1.4.1.2.3.3-6A: NASContainer (Table 8.1.4.1.2.3.3-5, Table 8.1.4.1.2.3.3-10)
Derivation Path: TS 24.501, table 9.11.2.6

Message authentication code The calculated value of The value of
MAC-I for this message. MAC-I is
calculated by SS
using COUNT =
0xFFFFFFFF( as
per TS
33.501[20],
6.9.2.3.3)
Type of ciphering algorithm Set according to PIXIT
px_NAS_5GC_Ciphering
Algorithm for default
ciphering algorithm
Type of integrity protection algorithm Set according to PIXIT This value should
px_NAS_5GC_IntegrityAl not be equal to
gorithm for default the null integrity
integrity protection algorithm.
algorithm
KACF ‘1’B a new KAMF has
been calculated
by the network
TSC '0'B native security
context (for
KSIAMF)
Key set identifier in 5G KSIAMF that was created
when the UE last
registered to 5GCN
Sequence number The internal counter of eight least
the SS significant bits of
the downlink NAS
COUNT
Derivation Path: TS 38.508-1 [4] Table 4.6.1-13 with condition MEAS
ETSI

measObjectId 1
measObject CHOICE {
}
}
}
measObjectId 2
measObject CHOICE {
}
}
}
}
reportConfigId 1
EventA3
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
}
}
ETSI

measId 1
NR Cell 3
of NR Cell 3
rsrp (0..127)
rsrq (0..127)
sinr Not present
R_Meas
}
}
}
}
}
}
of NR Cell 1
rsrp (0..127)
rsrq Not present
sinr Not present
}
}
}
}
}
}
}
}
}
}
ETSI

measConfig SEQUENCE {
measObjectToRemoveList SEQUENCE (SIZE 2 entries
}
measId[1] 1 entry 1
}
}
masterCellGroup OCTET STRING
(CONTAINING
CellGroupConfig)
nas-Container NASContainer Intra N1 mode
NAS transparent
container
}
}
}
}
}
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change

spCellConfigCommon SEQUENCE { Same as default
ServingCellConfigComm
on
physCellId Physical cell Id of NR
Cell 1
}
}
}
}
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with condition RBConfig_NoKeyChange

dedicatedSIB1-Delivery SIB1 OCTET STRING
(CONTAINING
SIB1)
}
}
}
}
Table 8.1.4.1.2.3.3-13: SIB1 (Table 8.1.4.1.2.3.3-12)

SIB1 ::= SEQUENCE {
plmn-IdentityList SEQUENCE (SIZE 1 entry
plmn-Identity[1] entry 1
trackingAreaCode 2
}
}
}
}
8.1.4.1.3 Void
8.1.4.1.4 Void
8.1.4.1.5 Intra NR handover / Failure / Re-establishment successful
(1)
with { UE in NR RRC_CONNECTED state and having received an RRCReconfiguration message including a
reconfigurationWithSync for handover to the target cell }
ensure that {
when { UE detects handover failure and the initial cell is selectable }
then { UE performs an RRCReestablishment procedure on the source cell }
}
(2)
with { UE detects handover failure and having transmitted an RRCReestablishmentRequest message }
ensure that {
when { UE receives an RRCReestablishment message with a nextHopChainingCount which is different
from the NCC associated with the currently active KgNB }
then { UE derives new KgNB from the nextHopChainingCount and completes RRCReestablishment
procedure on the source cell }
}
(3)
with { UE detects handover failure and having transmitted an RRCReestablishmentRequest message }
ensure that {
ETSI
when { UE receives an RRCReestablishment message with a nextHopChainingCount which is same as the

NCC associated with the currently active KgNB }
then { UE derives new KgNB from the currently active KgNB and completes RRCReestablishment
procedure on the source cell }
}
5.3.5.5.2, 5.3.5.7, 5.3.5.8.3 and 5.3.7.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
1> else:
[TS 38.331, clause 5.3.5.7]
The UE shall:
1> else:
2> if the nas-Container is included in the received masterKeyUpdate:
3> forward the nas-Container to the upper layers;
ETSI
2> if the keySetChangeIndicator is set to true:
3> derive or update the KgNB key based on the KAMF key, as specified in TS 33.501 [11];
2> else:
3> derive or update the KgNB key based on the current KgNB key or the NH, using the nextHopChainingCount
value indicated in the received masterKeyUpdate, as specified in TS 33.501 [11];
2> store the nextHopChainingCount value;
2> derive the keys associated with the KgNB key as follows:
3> if the securityAlgorithmConfig is included in SecurityConfig:
4> derive the KRRCenc and KUPenc keys associated with the cipheringAlgorithm indicated in the
4> derive the KRRCint and KUPint keys associated with the integrityProtAlgorithm indicated in the
3> else:
4> derive the KRRCenc and KUPenc keys associated with the current cipheringAlgorithm, as specified in TS
33.501 [11];
4> derive the KRRCint and KUPint keys associated with the current integrityProtAlgorithm, as specified in
TS 33.501 [11].
NOTE: Ciphering and integrity protection are optional to configure for the DRBs.
[TS 38.331, clause 5.3.5.8.3]
The UE shall:
1> if T304 of the MCG expires:
2> release dedicated preambles provided in rach-ConfigDedicated if configured;
2> revert back to the UE configuration used in the source PCell;
2> initiate the connection re-establishment procedure as specified in subclause 5.3.7.
NOTE 1: In the context above, "the UE configuration" includes state variables and parameters of each radio bearer.
1> else if T304 of a secondary cell group expires:
2> release dedicated preambles provided in rach-ConfigDedicated, if configured;
2> initiate the SCG failure information procedure as specified in subclause 5.7.3 to report SCG reconfiguration
with sync failure, upon which the RRC reconfiguration procedure ends;
1> else if T304 expires when RRCReconfiguration is received via other RAT (HO to NR failure):
2> reset MAC;
2> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT.
[TS 38.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
1> store the nextHopChainingCount value indicated in the RRCReestablishment message;
ETSI
1> update the KgNB key based on the current KgNB key or the NH, using the stored nextHopChainingCount value, as
1> derive the KRRCenc and KUPenc keys associated with the previously configured cipheringAlgorithm, as specified in
TS 33.501 [11];
1> derive the KRRCint and KUPint keys associated with the previously configured integrityProtAlgorithm, as specified
in TS 33.501 [11].
1> request lower layers to verify the integrity protection of the RRCReestablishment message, using the previously
configured algorithm and the KRRCint key;
1> if the integrity protection check of the RRCReestablishment message fails:
failure', upon which the procedure ends;
1> configure lower layers to resume integrity protection for SRB1 using the previously configured algorithm and
the KRRCint 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 resume ciphering for SRB1 using the previously configured algorithm and, the KRRCenc
key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE,
1> release the measurement gap configuration indicated by the measGapConfig, if configured;
1> submit the RRCReestablishmentComplete message to lower layers for transmission;
System Simulator:
- NR Cell 1 is the Serving cell.
- NR Cell 2 is the Suitable neighbour intra-frequency cell.
UE:
- None.
Preamble:
Table 8.1.4.1.5.3.2-1 and Table 8.1.4.1.5.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. The exact instants on which these values shall be
ETSI

1 2
SS/PBCH dBm/SC
T1 -88 -88
SSS EPRE S
SS/PBCH dBm/SC
T2 -88 “Off”
SSS EPRE S

1 2
SS/PBCH dBm/SC
T1 FFS FFS
SSS EPRE S
SS/PBCH dBm/SC
T2 FFS “Off”
SSS EPRE S
ETSI

U-S Message
-
message on NR Cell 1 to order the UE to
perform handover to NR Cell 2.
described in step 3 the steps specified in Table
RRCReestablishmentRequest RRCReestablishmentRequest
message to resume SRB1 operation and re-
activate security on NR Cell 1.
6 Does the UE transmit an --> NR RRC: 2 P
RRCReestablishmentComplete message RRCReestablishmentComplete
using the security key derived from the
nextHopChainingCount on NR Cell 1?
message to resume existing radio bearers on
NR Cell 1.
NR Cell 1.
10 Check: Does the UE transmit an --> NR RRC: - -
12 Does the UE transmit an --> NR RRC: 3 P
using the security key derived from the
nextHopChainingCount on NR Cell 1?
A message to resume existing radio bearers on
NR Cell 1.
B RRCReconfigurationComplete message on RRCReconfigurationComplete
NR Cell 1.
on NR Cell 1.
ETSI

U-S Message
- EXCEPTION: The steps 1 and 2 below are - - - -
repeated for the duration of T304.
1 The UE attempts to perform the handover - - - -
using MAC Random Access Preamble on NR
Cell 2.
2 The SS does not respond. - - - -
Table 8.1.4.1.5.3.3-1: SIB1 for NR Cell 1 and NR Cell 2 (preamble and all steps, Table 8.1.4.1.5.3.2-3)

}
Table 8.1.4.1.5.3.3-2: RRCReconfiguration-HO (steps 2, 8, Table 8.1.4.1.5.3.2-3)
Table 8.1.4.1.5.3.3-3: RRCReestablishmentRequest (step 4, 10, Table 8.1.4.1.5.3.2-3)

RRCReestablishmentRequest ::= SEQUENCE {
ue-Identity SEQUENCE {
c-RNTI the value of the C-RNTI
of the UE
physCellId PhysicalCellIdentity of
NR Cell 1
shortMAC-I The same value as the
16 least significant bits of
the MAC-I value
calculated by SS.
}
reestablishmentCause handoverFailure
}
Table 8.1.4.1.5.3.3-4: RRCReestablishment (step 5, 11, Table 8.1.4.1.5.3.2-3)

RRCReestablishment ::= SEQUENCE {
rrcReestablishment SEQUENCE {
}
}
}
Table 8.1.4.1.5.3.3-5: Void
ETSI
Table 8.1.4.1.5.3.3-6: Void
Table 8.1.4.1.5.3.3-7: RRCReconfiguration (step 6A and 12A, Table 8.1.4.1.5.3.2-3)
Derivation Path: TS 38.508-1[4], table 4.6.1-13 with condition REEST
8.1.4.1.6 Intra NR handover / Failure / Re-establishment failure
(1)
reconfigurationWithSync for handover to the target cell }
ensure that {
when { UE detects handover failure and fails an RRCReestablishment procedure }
then { UE enters NR RRC_IDLE state }
}
5.3.5.5.2, 5.3.5.8.3 and 5.3.7.5 and TS 24.501, clause 5.5.1.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
1> else:
ETSI
[TS 38.331, clause 5.3.5.8.3]
The UE shall:
2> revert back to the UE configuration used in the source PCell;
2> initiate the connection re-establishment procedure as specified in subclause 5.3.7.
NOTE 1: In the context above, "the UE configuration" includes state variables and parameters of each radio bearer.
1> else if T304 of a secondary cell group expires:
2> release dedicated preambles provided in rach-ConfigDedicated, if configured;
2> initiate the SCG failure information procedure as specified in subclause 5.7.3 to report SCG reconfiguration
with sync failure, upon which the RRC reconfiguration procedure ends;
1> else if T304 expires when RRCReconfiguration is received via other RAT (HO to NR failure):
2> reset MAC;
2> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT.
[TS 38.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
TS 33.501 [11];
in TS 33.501 [11].
ETSI
[TS 24.501, clause 5.5.1.3.2]
The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration
update by sending a REGISTRATION REQUEST message to the AMF,
f) when the UE receives an indication of "RRC Connection failure" from the lower layers and does not have
signalling pending (i.e. when the lower layer requests NAS signalling connection recovery) except for the case
specified in subclause 5.3.1.4;
System Simulator:
- NR Cell 1 is the Serving cell.
- NR Cell 2 is the Suitable neighbour intra-frequency cell.
UE:
- None.
Preamble:
Table 8.1.4.1.6.3.2-1 and Table 8.1.4.1.6.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. The exact instants on which these values shall be

1 2
SS/PBCH dBm/SC
T1 -88 -88
SSS EPRE S
SS/PBCH dBm/SC
T2 -88 “Off”
SSS EPRE S

1 2
SS/PBCH dBm/SC
T1 FFS FFS
SSS EPRE S
SS/PBCH dBm/SC
T2 FFS “Off”
SSS EPRE S
ETSI

U-S Message
-
Note: RRCReestablishment includes a wrong
nextHopChainingCount value causing an
integrity check failure.
6 Check: Does the test result of test procedure in - - 1 -
TS 38.508-1 [4] subclause 4.9.5 indicate
that the UE has performed mobility registration
on NR cell 1 started in NR RRC_IDLE?

U-S Message
1 The UE attempts to perform the handover - - - -
using MAC Random Access Preamble on NR
Cell 2.
Table 8.1.4.1.6.3.3-1: SIB1 for NR Cell 1 and NR Cell 2 (preamble and all steps, Table 8.1.4.1.6.3.2-3)

}
Table 8.1.4.1.6.3.3-2: RRCReconfiguration-HO (step 2, Table 8.1.4.1.6.3.2-3)
ETSI
Table 8.1.4.1.6.3.3-3: RRCReestablishmentRequest (step 4, Table 8.1.4.1.6.3.2-3)

c-RNTI the value of the C-RNTI
of the UE
physCellId PhysicalCellIdentity of
NR Cell 1
shortMAC-I The same value as the
16 least significant bits of
the MAC-I value
calculated by SS.
}
}
Table 8.1.4.1.6.3.3-4: RRCReestablishment (step 5, Table 8.1.4.1.6.3.2-3)

}
}
}
8.1.4.1.7 NR CA / Intra NR handover / Success / PCell Change and SCell addition /

SCell release
8.1.4.1.7.1 NR CA / Intra NR handover / Success / PCell Change and SCell addition / SCell
release / Intra-band Contiguous CA
(1)
with { UE in NR RRC_CONNECTED state and configured an SCell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for handover
to one of the SCell and sCellToAddModList for an SCell addition }
then { UE transmits an RRCReconfigurationComplete message. }
}
(2)
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for PCell
change and including sCellToReleaseList with an sCellIndex set to the configured Scell }
then { UE sends an RRCReconfigurationComplete message. }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.5.2,
clauses 5.3.5.5.9 and clauses 5.3.5.5.8. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
ETSI
1> else:
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
(SCell addition):
measId:
measId;
ETSI
modification):
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 is the configured SCell. NR Cell 2 is the target SCell. NR Cell 23 is the target
intra-frequency Cell of NR Cell 3, and also the target PCell.
- NR Cell 1 and NR Cell 3 are Intra-band Contiguous. NR Cell 2 and NR Cell 23 are Intra-band Contiguous.
- NR Cell 23 belongs to the same PLMN and TAI with NR Cell 1.
UE:
- None.
Preamble:
Table 4.4A.2-3.
Table 8.1.4.1.7.1.3.2-1 and Table 8.1.4.1.7.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR
Cell 3, NR Cell 2 and NR Cell 23 at various time instants of the test execution. Row marked “T0” denotes the
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.
Table 8.1.4.1.7.1.3.2-1: Time instances of cell power level and parameter changes for FR1

T0 SS/PBCH dBm/ -88 -88 -88 “off” NR Cell 1, NR Cell 2 and NR Cell
SSS EPRE SCS 3 are available. NR Cell 23 are not
available.
T1 SS/PBCH dBm/ “off” -88 -88 -88 NR Cell 3, NR Cell 2 and NR Cell
available.
ETSI

T0 SS/PBCH dBm/ FFS FFS FFS “off” NR Cell 1, NR Cell 2 and NR Cell
available.
T1 SS/PBCH dBm/ “off” FFS FFS FFS NR Cell 3, NR Cell 2 and NR Cell
available.

U-S Message
1 The SS changes Cell parameters according to - - - -
the row “T0” in table 8.1.4.1.7.1.3.2-1/2.
message including a sCellToAddModList to
add NR Cell 3 as a SCell.
3 The UE transmits the --> NR RRC: - -
message including a reconfigurationWithSync
for handover to NR Cell 3 and
sCellToAddModList to add NR Cell 2 as a
SCell.
5 Check: Does UE transmit the --> NR RRC: 1 P
RRCReconfigurationComplete message? RRCReconfigurationComplete
5A Check: Does the test result of generic test - - 1 -
procedure in TS 38.508-1 Table 4.9.1-1A
PDU session on Cell 2?
the row “T1” in table 8.2.4.2.1.1.3.2-1/2.
to change PCell to NR Cell 23 and including
sCellToReleaseList with a sCellIndex of NR
Cell 2.
PDU session on Cell 23?
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition SCell_add

(CONTAINING
CellGroupConfig)
}
}
}
}
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition SCell_Add

sCellConfigCommon SEQUENCE {
Cell 3
}
}
}
}
Derivation Path: TS 38.508-1 [4] 4.8.1-1A with condition RBConfig_KeyChange

(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PCell_change and SCell_Add
Cell 3
}
}
}
Cell 2
}
}
}
SCell release
for NR Cell 3
}
}
Table 8.1.4.1.7.1.3.3-5: RRCReconfiguration-HO (step 7, Table 8.1.4.1.7.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with conditions PCell_change

Cell 23
}
}
}
SCell release
for NR Cell 2
}
}
release / Inter-band CA
ETSI
- NR Cell 30 belongs to the same PLMN and TAI with NR Cell 1.
Table 8.1.4.1.7.2.3.3-1: SIB3 of NR Cell 10 (step 6, Table 8.1.4.1.7.1.3.2-3)

SIB3 ::= SEQUENCE {
IntraFreqNeighCellInfo [1] SEQUENCE { entry 1
physCellId Physical Cell Identity
of NR Cell 30
}
}
}
release / Intra-band non-contiguous CA
Same as TC 8.1.4.1.7.1 but applied to Intra-band non-Contiguous CA.
ETSI
8.1.4.1.8 NR CA / Intra NR handover / Success / PCell Change / SCell no Change

Contiguous CA
(1)
with { UE in NR RRC_CONNECTED state and configured an SCell }
ensure that {
when { UE receives an RRCReconfiguration message including a reconfigurationWithSync for PCell
change and sCellToAddModList with an SCell same from configured Scell }
then { UE transmits an RRCReconfigurationComplete message. }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clauses 5.3.5.5.2,
clauses 5.3.5.5.9. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
1> else:
ETSI
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
(SCell addition):
measId:
measId;
modification):
System Simulator:
- NR Cell 1 is the PCell, NR Cell 3 is the configured SCell. NR Cell 2 is the target intra-frequency Cell of NR Cell
1, and also the target PCell.
- NR Cell 1 and NR Cell 3 are Intra-band Contiguous.
UE:
- None.
Preamble:
Table 4.4A.2-3.
ETSI
Table 8.1.4.1.8.1.3.2-1 and Table 8.1.4.1.8.1.3.2-2 illustrates the downlink power levels to be applied for NR Cell 1, NR
Cell 1, NR Cell 3 and NR Cell 2 at various time instants of the test execution. Row marked “T0” denotes the conditions
after the preamble, while rows marked “T1” are to be applied subsequently. The exact instants on which these values

T0 SS/PBCH dBm/ -88 -99 “off” NR Cell 1, NR Cell 3 are
SSS EPRE SCS available. NR Cell 2 are not
available.
T1 SS/PBCH dBm/ -88 -99 -88 NR Cell 1, NR Cell 3 and NR Cell
SSS EPRE SCS 2 are available.

T0 SS/PBCH dBm/ FFS FFS “off” NR Cell 1, NR Cell 3 are
SSS EPRE SCS available. NR Cell 2 are not
available.
T1 SS/PBCH dBm/ FFS FFS FFS NR Cell 1, NR Cell 3 and NR Cell
SSS EPRE SCS 2 are available.

U-S Message
the row “T0” in table 8.1.4.1.8.1.3.2-1/2.
message including a sCellToAddModList to
add NR Cell 3 as a SCell.
3 The UE transmits the --> NR RRC: - -
3A Check: Does the test result of generic test - - 1 P
IP data on DRB1 and NR Cell 3?
the row “T1” in table 8.1.4.1.8.1.3.2-1/2.
to change PCell to NR Cell 2 and
sCellToAddModList to add NR Cell 3 as the
Scell.
message containing an sCellToReleaseList
with SCell NR Cell 3.
ETSI

(CONTAINING
CellGroupConfig)
}
}
}
}

sCellIndex 1
Cell 3
}
}
}
}
Table 8.1.4.1.8.1.3.3-3: RRCReconfiguration-HO (step 5, Table 8.1.4.1.8.1.3.2-3)
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change and SCell_add
Cell 2
}
}
}
sCellIndex 1
Cell 3
}
}
}
SCell release
for NR Cell 3
}
}

}
}
}
}

}
}
ETSI
8.1.4.1.8.2 NR CA / Intra NR handover / Success / PCell Change / SCell no Change / Inter-band

CA

non-contiguous CA
ETSI
8.1.4.1.9 NR CA / Intra NR handover / Failure / Re-establishment successful
8.1.4.1.9.1 NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band

Contiguous CA
(1)
reconfigurationWithSync for PCell change and including sCellToReleaseList with an sCellIndex set to
the configured Scell }
ensure that {
when { UE detects handover failure and the source PCell is selectable}
then { UE successfully performs an RRCReestablishment procedure on source Pcell}
}
(2)
reconfigurationWithSync for PCell change and including sCellToReleaseList with an sCellIndex set to
the configured SCell }
ensure that {
when { UE detects handover failure and the initial SCell is selectable}
then { UE successfully performs an RRCReestablishment procedure on original SCell and the
original SCell becomes the PCell}
}
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clause 5.3.5.5.2,
5.3.5.5.9, 5.3.5.5.8 and 5.3.7.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.5.2]
1> else:
ETSI
[TS 38.331, clause 5.3.5.5.9]
The UE shall:
(SCell addition):
measId:
measId;
modification):
[TS 38.331, clause 5.3.5.5.8]
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
[TS 38.331, clause 5.3.7.5]
The UE shall:
1> stop timer T301;
ETSI
TS 33.501 [11];
in TS 33.501 [11].
8.1.4.1.9.1.3 Test Description
System Simulator:
- NR Cell 1 is the PCell and NR Cell 3 is the SCell
- System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in all NR cells.
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A as defined in TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3 on NR Cell 1.
Table 8.1.4.1.9.1.3.2-1 and Table 8.1.4.1.9.1.3.2-1A illustrates the downlink power levels to be applied for NR Cell 1
and NR Cell 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the
preamble, while rows marked "T1", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which
these values shall be applied are described in the texts in this clause.
ETSI

Cell 1 Cell 3

SS/PBCH dBm/SC condition for event A3 is not satisfied
T0 -85 -91
SSS EPRE S Mn + Ofn + Ocn – Hys < Mp + Ofp + Ocp
+ Off
SS/PBCH dBm/SC condition for event A3 is satisfied
T1 -85 -79
SSS EPRE S Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp
+ Off
Power levels are assigned to satisfy
SS/PBCH dBm/SC
T2 -85 “Off” SrxLevCell3 < 0 such that selecting Cell
SSS EPRE S
1 is guaranteed
T3 -85 -79
+ Off
SS/PBCH dBm/SC
T4 “Off” -79 SrxLevCell1 < 0 such that selecting Cell
SSS EPRE S
3 is guaranteed
Table 8.1.4.1.9.1.3.2-1A: Time instances of cell power level and parameter changes for FR2

Cell 1 Cell 3
SS/PBCH dBm/SC condition for event A3 is not satisfied
T0 [FFS] [FFS]
SSS EPRE S Mn + Ofn + Ocn – Hys < Mp + Ofp + Ocp
+ Off
T1 [FFS] [FFS]
+ Off
SS/PBCH dBm/SC
T2 [FFS] “Off” SrxLevCell3 < 0 such that selecting Cell
SSS EPRE S
1 is guaranteed
T3 [FFS] [FFS]
+ Off
SS/PBCH dBm/SC
T4 “Off” [FFS] SrxLevCell1 < 0 such that selecting Cell
SSS EPRE S
3 is guaranteed
ETSI

U-S Message
message on NR Cell 1 to configure NR Cell 3
as an SCell
NR Cell 1.
message on NR Cell 1 to setup event A3
reporting configuration.
NR Cell 1.
8.1.4.1.9.1.3.2-1/1A
6 The UE transmits a MeasurementReport --> NR RRC: MeasurementReport - -
message on NR Cell 1 to report event A3 with
the measured RSRP, RSRQ value for NR Cell
3.
perform inter frequency handover to NR Cell 3
and to release SCell NR Cell 3.
8.1.4.1.9.1.3.2-3 should take place.
8.1.4.1.9.1.3.2-1/1A
Cell 1?
11A The SS changes NR Cell 1 and NR Cell 3 - - - -
8.1.4.1.9.1.3.2-1/1A.
message to resume existing radio bearer on
NR Cell 1 and configure NR Cell 3 as an SCell
NR Cell 1
message on NR Cell 1 to setup event A3
reporting configuration.
NR Cell 1.
16 Void - - - -
17 The UE transmits a MeasurementReport --> NR RRC: MeasurementReport - -
message on NR Cell 1 to report event A3 with
the measured RSRP, RSRQ value for NR Cell
3.
perform handover to NR Cell 3 and to release
SCell NR Cell3.
described in step 19 the steps specified in
ETSI
Table 8.1.4.1.9.1.3.2-3 should take place.

8.1.4.1.9.1.3.2-1/1A
Cell 3?
message to resume existing radio bearer on
NR Cell 3.
NR Cell 3.

U-S Message
1 The UE attempts to perform the inter - - - -
frequency handover using MAC Random
Access Preamble on NR Cell 3.
Table 8.1.4.1.9.1.3.3-1: SIB1 for NR Cell 1 and NR Cell 3 (Preamble and all the steps in Table
8.1.4.1.9.1.3.2-2)

SIB1 ::= SEQUENCE {
}
}
}
}
}
}
ETSI
Table 8.1.4.1.9.1.3.3-2: RRCReconfiguration (step 1 and 12, Table 8.1.4.1.9.1.3.2-2)

}
}
}
Derivation path: TS 38.508-1 [4], table 4.6.3-19

sCellIndex 1
on
}
}
sCellToReleaseList Not present
}

physCellId Physical layer cell
identity of NR Cell 3
}
Table 8.1.4.1.9.1.3.3-5: RRCReconfiguration (steps 3 and 14, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 and condition NR_MEAS
ETSI
Derivation path: TS 38.508-1[4], table 4.6.3-69

measObjectId 1
measObject CHOICE {
measObjectNR MeasObjectNR-f1 NR Cell 1
}
}
measObjectId 2
measObject CHOICE {
measObjectNR MeasObjectNR-f2 NR Cell 3
}
}
}
reportConfigId[1] 1
reportConfig[1] CHOICE {
reportConfigNR ReportConfigNR-A3
}
}
}
measId 1
measObjectId 2
reportConfigId 1
}
}
Table 8.1.4.1.9.1.3.3-7: MeasObjectNR-f1 (Table 8.1.4.1.9.1.3.3-6)

Cell 1 SSB
}
Table 8.1.4.1.9.1.3.3-8: MeasObjectNR-f2 (Table 8.1.4.1.9.1.3.3-6)

Cell 3 SSB
}
ETSI
Table 8.1.4.1.9.1.3.3-9: ReportConfigNR-A3 (Table 8.1.4.1.9.1.3.3-6)
Derivation Path: TS 38.508-1 [4], table 4.6.3-142 with condition EVENT_A3

reportType CHOICE {
eventId CHOICE {
eventA3 SEQUENCE {
a3-Offset CHOICE {
rsrp 2 1 dB (2*0.5 dB) FR1
FFS FR2
}
timeToTrigger ms2560
}
}
}
}
}
ETSI
Table 8.1.4.1.9.1.3.3-10: MeasurementReport (steps 6 and 17, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1 [4], table 4.6.1-5A

Cell 1
1
rsrp (0..127)
rsrq (0..127)
Not present
}
}
}
}
}
}
measResultNeighCells CHOICE { 1 entry
measResultListNR SEQUENCE (SIZE
3
rsrp (0..127)
rsrp (0..127)
sinr (0..127)
}
}
}
}
}
}
}
}
}
}
ETSI
Table 8.1.4.1.9.1.3.3-11: RRCReconfiguration (steps 7 and 18, Table 8.1.4.1.9.1.3.2-2)
Derivation Path: TS 38.508-1[4], table 4.6.1-13 with condition NR

}
}
}
}
Derivation path: TS 38.508-1 [4] table 4.6.3-19 with condition PCell_Change

downlinkConfigCommon SEQUENCE {
frequencyInfoDL SEQUENCE {
absoluteFrequencySSB Downlink ARFCN of NR
Cell 3 SSB
}
}
}
uplink SEQUENCE {
cfra SEQUENCE {
resources CHOICE {
ssb SEQUENCE {
ssb-ResourceList SEQUENCE 1 entry
(SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-
Resource {
CFRA-SSB-Resource[1] SEQUENCE { entry 1
ra-PreambleIndex 63
}
}
}
}
}
}
}
}
}
SCellIndex of NR
Cell 3
}
}
ETSI
Table 8.1.4.1.9.1.3.3-13: RRCReestablishmentRequest (steps 9 and 20, Table 8.1.4.1.9.1.3.2-2)

}
}
Table 8.1.4.1.9.1.3.3-14: RRCReestablishment (steps 10 and 21, Table 8.1.4.1.9.1.3.2-2)

}
}
}
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 with condition REEST

masterCellGroup CellGroupConfig with
condition SCell_add and
REEST
}
}
}
}
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 with condition REEST
8.1.4.1.9.2 NR CA / Intra NR handover / Failure / Re-establishment successful / Inter-band CA
Same as TC 8.1.4.1.9.1 but applied to Inter-band CA case
ETSI
8.1.4.1.9.3 NR CA / Intra NR handover / Failure / Re-establishment successful / Intra-band non-

contiguous CA
Same as TC 8.1.4.1.9.1 but applied to Intra-band non-contiguous CA case
- CA configuration: Intra-band Contiguous CA replaces Intra-band non-contiguous CA.
8.1.4.2 Inter-RAT handover
8.1.4.2.1 Inter-RAT handover from NR
8.1.4.2.1.1 Inter-RAT handover / From NR to E-UTRA / Success
(1)
ensure that {
when { UE receives a MobilityFromNRCommand message }
ETSI
then { UE transmits an RRCConnectionReconfigurationComplete message on the E-UTRA cell }

}
References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.4.3.2, clause
5.4.3.3 and clause 5.4.3.4 and TS 36.331, clause 5.4.2.2 and clause 5.4.2.3.
[TS.38.331, clause 5.4.3.2]
The network initiates the mobility from NR procedure to a UE in RRC_CONNECTED, possibly in response to a
MeasurementReport message, by sending a MobilityFromNRCommand message. The network applies the procedure as
follows:
- the procedure is initiated only when AS-security has been activated, and SRB2 with at least one DRB are setup
and not suspended.
[TS 38.331, clause 5.4.3.3]
The UE shall:
1> if the targetRAT-Type is set to eutra:
2> consider inter-RAT mobility as initiated towards E-UTRA;
2> forward the nas-SecurityParamFromNR to the upper layers, if included;
1> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT.
[TS.38.331, clause 5.4.3.4]
Upon successfully completing the handover, at the source side the UE shall:
1> reset MAC;
1> stop all timers that are running;
1> release ran-NotificationAreaInfo, if stored;
1> release the AS security context including the KRRCenc key, the KRRCint, the KUPint key and the KUPenc key, if stored;
1> release all radio resources, including release of the RLC entity and the MAC configuration;
1> release the associated PDCP entity and SDAP entity for all established RBs;
NOTE : PDCP and SDAP configured by the source RAT prior to the handover that are reconfigured and re-used by
target RAT when delta signalling (i.e., during inter-RAT intra-system handover when fullConfig is not present) is used,
are not released as part of this procedure.
1> indicate the release of the RRC connection to upper layers together with the release cause 'other'.
[TS 36.331, clause 5.4.2.2]
The RAN using another RAT or the E-UTRA connected to a different type of CN initiates the handover to E-UTRA
procedure, in accordance with the specifications applicable for the other RAT or for the E-UTRA connected to a
different type of CN, by sending the RRCConnectionReconfiguration message via the radio access technology from
which the inter-RAT handover is performed.
E-UTRAN applies the procedure as follows:
- to activate ciphering, possibly using NULL algorithm, if not yet activated in the other RAT or in the E-UTRA
connected to a different type of CN;
- to establish SRB1, SRB2 and one or more DRBs, i.e. at least the DRB associated with the default EPS bearer is
established if the target CN is EPC and at least one DRB is established if the target CN is 5GC.
[TS 36.331, clause 5.4.2.3]
ETSI
If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE
shall:
1> if the RRCConnectionReconfiguration message includes the fullConfig and the source RAT was E-UTRA(i.e.,
intra-RAT inter-system handover):
1> apply the default physical channel configuration as specified in 9.2.4;
1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;
1> apply the default MAC main configuration as specified in 9.2.2;
1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;
1> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity
indicated by the targetPhysCellId;
1> start synchronising to the DL of the target PCell;
1> set the C-RNTI to the value of the newUE-Identity;
1> for the target PCell, apply the downlink bandwidth indicated by the dl-Bandwidth;
1> for the target PCell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;
1> configure lower layers in accordance with the received radioResourceConfigCommon;
received mobilityControlInfo;
1> perform the radio resource configuration procedure as specified in 5.3.10;
1> if the handoverType in securityConfigHO is set to fivegc-ToEPC:
2> indicate to higher layer that the CN has changed from 5GC to EPC;
2> derive the key KeNB based on the mapped KASME key as specified for interworking between EPS and 5GS
in TS 33.501 [86];
2> store the nextHopChainingCount-r15 value;
1> else if the handoverType in securityConfigHO is set to intra5GC:
1> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];
1> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401
[32];
1> if the handoverType in securityConfigHO is set to fivegc-ToEPC or if the handoverType-v1530 is not present:
2> configure lower layers to apply the indicated integrity protection algorithm and the KRRCint 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;
2> configure lower layers to apply the indicated ciphering algorithm, the KRRCenc key and the KUPenc 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;
1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:
ETSI
1> if the RRCConnectionReconfiguration message includes the measConfig:
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new
configuration;
1> if the RRCConnectionReconfiguration message does not include rlf-TimersAndConstants set to setup:
2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;
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 PCell, if any;
of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration,
sounding RS configuration), if any, upon acquiring the SFN of the target PCell;
NOTE 1: 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> enter E-UTRA RRC_CONNECTED, upon which the procedure ends;
System Simulator:
- NR Cell 1 and E-UTRA Cell 1.
- System information Combination NR-6 as defined in TS 38.508 [4] clause 4.4.3.1 is used in NR cells.
UE:
- None
Preamble:
- The UE is in 5GS state 3N-A and Test Loop Function (On) with UE test loop mode B on NR Cell 1 according to
38.508-1[4], clause 4.4A.2 Table 4.4A.2-3.
ETSI

U-S Message
1 The SS transmits a MobilityFromNRCommand <-- MobilityFromNRCommand - -
message on NR Cell 1.
2 Check: Does the UE transmit an --> RRCConnectionReconfigurationC 1 P
RRCConnectionReconfigurationComplete omplete
message on E-UTRA Cell 1 using the security
key derived from the new KeNB?
3 The UE transmits an ULInformationTransfer --> RRC: ULInformationTransfer - -
message on the cell specified in the test case. NAS: TRACKING AREA UPDATE
This message includes a TRACKING AREA REQUEST
UPDATE REQUEST message.
4 The SS transmits a DLInformationTransfer <-- RRC: DLInformationTransfer - -
This message includes a TRACKING AREA ACCEPT
UPDATE ACCEPT message.
This message includes a TRACKING AREA COMPLETE
UPDATE COMPLETE message.
6 Void - - - -
7 The SS sends one IP Packet to the UE on the - - - -
session.
8 The UE loop backs the IP packet received in - - 1 P
step 7.
Table 8.1.4.2.1.1.3.3-1: MobilityFromNRCommand (step 1, Table 8.1.4.2.1.1.3.2-1)

MobilityFromNRCommand::= SEQUENCE {
rrc-TransactionIdentifier RRC-TransactionIdentifier
mobilityFromNRCommand SEQUENCE {
targetRAT-Type eutra
targetRAT-MessageContainer DL-DCCH message
containing
RRCConnectionReconfig
uration
nas-SecurityParamFromNR 8 LSB of the downlink
NAS COUNT
}
}
}
Table 8.1.4.2.1.1.3.3-2: RRCConnectionReconfiguration (Table 8.1.4.2.1.1.3.3-1)
Derivation Path: TS 36.508, Table 4.6.1-8, condition HO-TO-EUTRA(1,0)
ETSI
Table 8.1.4.2.1.1.3.3-3: MobilityControlInfo (Table 8.1.4.2.1.1.3.3-1)
Derivation Path: TS 36.508 [7], Table 4.6.5-1, condition HO-TO-EUTRA

MobilityControlInfo ::= SEQUENCE {
UTRA Cell 1
carrierFreq SEQUENCE {
as used for E-UTRA Cell
1
}
carrierFreq Not present Band > 64
carrierBandwidth SEQUENCE {
dl-Bandwidth Downlink system
bandwidth under test.
ul-Bandwidth Uplink Bandwidth under FDD
test.
ul-Bandwidth Not present TDD
}
carrierFreq-v9e0 SEQUENCE { Band > 64
dl-CarrierFreq-v9e0 Same downlink EARFCN
1
}
}
FDD FDD cell environment
TDD TDD cell environment
Band > 64 If band > 64 is selected
Table 8.1.4.2.1.1.3.3-4: SecurityConfigHO (Table 8.1.4.2.1.1.3.3-1)
Derivation Path: TS 36.508, Table 4.6.4-1

SecurityConfigHO-v1530 ::= SEQUENCE {
handoverType-v1530 CHOICE {
fivegc-ToEPC-r15 SEQUENCE {
securityAlgorithmConfig-r15 SEQUENCE {
cipheringAlgorithm Set according to PIXIT
parameter for default
ciphering algorithm
integrityProtAlgorithm Set according to PIXIT
integrity protection
algorithm
}
nextHopChainingCount-r15 2
}
}
}
Table 8.1.4.2.1.1.3.3-5: Void
ETSI
Table 8.1.4.2.1.1.3.3-6: TRACKING AREA UPDATE REQUEST (step 3, Table 8.1.4.2.1.1.3.2-1)
Derivation Path: TS 38.508-1 table 4.9.7.2.3-1

EPS update type
EPS update type Value '000'B TA updating TA_only
‘001’B Combined TA/LA combined_T
updating A_LA_witho
ut_IMSI
'010'B Combined TA/LA combined_T
attach
NAS Key Set Identifier The value of ngKSI assigned in
preamble
Type of security context flag ‘1’B Mapped security
context
Non-current native NAS key set identifier Not present or any allowed value
Old GUTI Mapped 5G-GUTI
EPS bearer context status Not checked
TA_only The UE is configured to initiate EPS attach
combined_TA_LA The UE is configured to initiate combined EPS/IMSI attach
combined_TA_LA_without_IMSI The UE is configured to initiate combined attach
Table 8.1.4.2.1.1.3.3-7: Void
8.1.4.2.1.2 Inter-RAT handover / From NR to EN-DC / Success
(1)
ensure that {
when { UE receives a MobilityFromNRCommand message with the embedded RRCConnectionReconfiguration
message including nr-SecondaryCellGroupConfig }
then { UE transmits an RRCConnectionReconfigurationComplete message embedding an
RRCReconfigurationComplete message on the E-UTRA cell }
}
Same as TC 8.1.4.2.1.1 with the addition of: Rel-16 TS 36.331, clause 5.3.5.4 and Rel-16 TS 37.340, clause 10.16.1.
[TS 36.331, clause 5.3.5.4]
If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the
configuration included in this message, the UE shall:
1> if the RRCConnectionReconfiguration message includes the fullConfig:
1> if the received RRCConnectionReconfiguration includes the sk-Counter:
2> perform key update procedure as specified in in TS 38.331 [82], clause 5.3.5.7;
1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:
2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3.
ETSI
1> set the content of RRCConnectionReconfigurationComplete message as follows:
2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:
3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;
1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;
[TS 37.340, clause 10.16.1]
Inter-system HO from NR to E-UTRA with EN-DC configuration is supported in this version of the specification. N26
based inter-system HO will be executed between source RAN and gNB.
System Simulator:
- NR Cell 1 is the serving cell. System information combination NR-6 as defined in TS 38.508-1 [4]
clause 4.4.3.1.2 is used in NR Cell 1.
- E-UTRA Cell 1 (PCell) and NR Cell 3 (PSCell) are the target cells. System information combination 31 as
defined in TS 36.508 [7] clause 4.4.3.1 is used in the E-UTRA cell. Only NR MIB is broadcasted on NR Cell 3.
UE:
- None
Preamble:
Table 4.4A.2-3.
ETSI

U-S Message
message and a PDU SESSION 5GMM: DL NAS TRANSPORT
MODIFICATION COMMAND to add DRB#a 5GSM: PDU SESSION
associated with a new QoS Flow. MODIFICATION COMMAND
RRCReconfigurationComplete message RRCReconfigurationComplete
0C The UE transmits a ULInformationTransfer --> NR RRC: ULInformationTransfer - -
message, an UL NAS TRANSPORT message 5GMM: UL NAS TRANSPORT
and an PDU SESSION MODIFICATION 5GSM: PDU SESSION
COMPLETE message MODIFICATION COMPLETE
1 The SS transmits a MobilityFromNRCommand <-- MobilityFromNRCommand - -
message on NR Cell 1,and embedded (RRCConnectionReconfiguration)
RRCConnectionReconfiguration message
contains nr-SecondaryCellGroupConfig with
the configuration of NR Cell 3
2 Check: Does the UE transmit an --> RRCConnectionReconfigurationC 1 P
RRCConnectionReconfigurationComplete omplete
containing NR RRCReconfigurationComplete (RRCReconfigurationComplete)
message on E-UTRA Cell 1 using the security
key derived from the new KeNB and sk-
Counter?
This message includes a TRACKING AREA REQUEST
UPDATE REQUEST message.
4 The SS transmits a DLInformationTransfer <-- RRC: DLInformationTransfer - -
This message includes a TRACKING AREA ACCEPT
UPDATE ACCEPT message.
This message includes a TRACKING AREA COMPLETE
UPDATE COMPLETE message.
IP data on DRB#b associated with the default
EPS bearer in E-UTRA Cell 1
IP data on the SCG DRB#a in NR Cell 3
Table 8.1.4.2.1.2.3.3-0A: PDU SESSION MODIFICATION COMMAND (step 0A, Table 8.1.4.2.1.2.3.2-1)

session ID in PDU
SESSION
ESTABLISHMENT
REQUEST associated
with the Internet PDU
session if available or
with the first PDU session
Mapped EPS bearer contexts
Mapped EPS bearer context
ETSI
EPS bearer identity (DRB#a + 4)

Operation code ‘001’B Create new EPS
bearer
E bit '1'B Parameters list is
included
Number of EPS parameters ’0001’B 1 parameter
Mapped EPS QoS parameters EPC dedicated bearer
context of the entry in TS
38.508-1 [4] Table 4.8.4-
1 which has been
determined by the DNN
IE in the UL NAS
TRANSPORT message
which carried the
corresponding PDU
SESSION
ESTABLISHMENT
REQUEST or by
pc_APN_Default_Config
uration if the DNN IE was
not present
Authorized QoS rules One entry
as defined in TS 38.508-
1 [4] Table 4.8.2.1-1.
Authorized QoS flow descriptions One entry
QoS flow [1] Dedicated QoS Flow QFI=5
NOTE: The mapped EPS bearer will become the Dedicated EPS Bearer after handover.
Table 8.1.4.2.1.2.3.3-0B: Dedicated QoS Flow (step 0A, Table 8.1.4.2.1.2.3.2-1)
Derivation Path: TS 24.501, table 9.11.4.12

QoS flow description
QFI ‘00 0101’B QFI 5
flow description
included
Number of parameters ’00 0010’B 2 parameters
5QI 5QI 1 5QI 1
EPS bearer identity (DRB#a + 4) EBI related to NR
DRB#a
ETSI
Table 8.1.4.2.1.2.3.3-0C: RRCReconfiguration (step 0A, Table8.1.4.2.1.2.3.2-1)
Derivation Path: TS xx?? Table 4.6.1-13 with condition NR.

c1 CHOICE {
radioBearerConfig RadioBearerConfig-HO-
ENDC
}
masterCellGroup CellGroupConfig- OCTET STRING
DRB(1,0) (CONTAINING
CellGroupConfig)
}
}
}
}
Table 8.1.4.2.1.2.3.3-0D: RadioBearerConfig-HO-ENDC (Table 8.1.4.2.1.2.3.3-0C)

OF DRB-ToAddMod {
DRB-ToAddMod[1] SEQUENCE {
sdap-Config SEQUENCE { SDAP-Config
defaultDRB false
}
}
condition DRB#a
}
}
NOTE: DRB#a will become the Dedicated EPS Bearer and the SCG DRB on NR Cell 3 after Handover.
Table 8.1.4.2.1.2.3.3-1: MobilityFromNRCommand (step 1, Table 8.1.4.2.1.2.3.2-1)

MobilityFromNRCommand::= SEQUENCE {
rrc-TransactionIdentifier RRC-TransactionIdentifier
mobilityFromNRCommand SEQUENCE {
targetRAT-Type eutra
targetRAT-MessageContainer DL-DCCH message
containing
RRCConnectionReconfig
uration
nas-SecurityParamFromNR 8 LSB of the downlink
NAS COUNT
}
}
}
ETSI
Table 8.1.4.2.1.2.3.3-2: RRCConnectionReconfiguration (Table 8.1.4.2.1.2.3.3-1)
Derivation Path: TS 36.508 [7], Table 4.6.1-8, condition HO-TO-EN-DC(x,0)

mobilityControlInfo MobilityControlInfo_EN-
DC
including the
RRCReconfiguration
message and
CellGroupConfig_EN-DC
including
RadioBearerConfig_EN-
DC
NOTE: x is equal to the number of PDU sessions established on NR Cell 1. These are all included in the HO to E-
UTRA.
Table 8.1.4.2.1.2.3.3-2A: CellGroupConfig_EN-DC (Table 8.1.4.2.1.2.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition EN-DC

conditions AM and
DRB#a
}
}
NOTE: DRB#a is the SCG DRB on NR Cell 3 after Handover
Table 8.1.4.2.1.2.3.3-2B: RadioBearerConfig_EN-DC (Table 8.1.4.2.1.2.3.3-2)

OF DRB-ToAddMod {
eps-BearerIdentity (DRB#a + 4)
}
condition DRB#a
reestablishPDCP true
}
}
NOTE: DRB#a is the SCG DRB on NR Cell associated with the Dedicated EPS Bearer after handover.
ETSI
Table 8.1.4.2.1.2.3.3-3: MobilityControlInfo_EN-DC (Table 8.1.4.2.1.2.3.3-1)
Derivation Path: TS 36.508 [7], Table 4.6.5-1, condition HO-TO-EN-DC

MobilityControlInfo ::= SEQUENCE {
UTRA Cell 1
carrierFreq SEQUENCE {
1
}
carrierFreq Not present Band > 64
carrierBandwidth SEQUENCE {
dl-Bandwidth Downlink system
bandwidth under test.
ul-Bandwidth Uplink Bandwidth under FDD
test.
ul-Bandwidth Not present TDD
}
carrierFreq-v9e0 SEQUENCE { Band > 64
dl-CarrierFreq-v9e0 Same downlink EARFCN
1
}
}
FDD FDD cell environment
TDD TDD cell environment
Band > 64 If band > 64 is selected
Table 8.1.4.2.1.2.3.3-4: SecurityConfigHO (Table 8.1.4.2.1.2.3.3-1)

SecurityConfigHO-v1530 ::= SEQUENCE {
handoverType-v1530 CHOICE {
fivegc-ToEPC-r15 SEQUENCE {
securityAlgorithmConfig-r15 SEQUENCE {
cipheringAlgorithm Set according to PIXIT
ciphering algorithm
integrityProtAlgorithm Set according to PIXIT
algorithm
}
nextHopChainingCount-r15 2
}
}
}
Table 8.1.4.2.1.2.3.3-5: Void
Table 8.1.4.2.1.2.3.3-6:RRCConnectionReconfigurationComplete (step 2, Table 8.1.4.2.1.2.3.2-1)
Derivation Path: TS 36.508 [7], Table 4.6.1-9, condition HO-TO-EN-DC(1,0)
ETSI
Table 8.1.4.2.1.2.3.3-7: TRACKING AREA UPDATE REQUEST (step 3, Table 8.1.4.2.1.2.3.2-1)
Derivation Path: TS 36.508 [7] clause 4.7.2-27

EPS update type
EPS update type Value '000'B TA updating TA_only
‘001’B Combined TA/LA combined_T
updating A_LA_witho
ut_IMSI
'010'B Combined TA/LA combined_T
attach
NAS Key Set Identifier The value of ngKSI assigned in
preamble
Type of security context flag ‘1’B Mapped security
context
Non-current native NAS key set identifier Not present or any allowed value
Old GUTI Mapped 5G-GUTI
GUTI type Native
Additional GUTI Any value or not present
UE status UE is in 5GMM-REGISTERED
state
TA_only The UE is configured to initiate EPS attach
combined_TA_LA The UE is configured to initiate combined EPS/IMSI attach
combined_TA_LA_without_IMSI The UE is configured to initiate combined attach
8.1.4.2.2 Inter-RAT handover to NR
8.1.4.2.2.1 Inter-RAT handover / From E-UTRA to NR / Success
(1)
ensure that {
when { UE receives a MobilityFromEUTRACommand message }
then { UE transmits a RRCReconfigurationComplete message on the NR cell }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.4.2.2,
5.4.2.3, TS 36.331, clause 5.4.3.2, 5.4.3.3, 5.4.3.4.Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.4.2.2]
The RAN using another RAT initiates the handover to NR procedure, in accordance with the specifications applicable
for the other RAT, by sending the RRCReconfiguration message via the radio access technology from which the inter-
RAT handover is performed.
The network applies the procedure as follows:
- to activate ciphering, possibly using NULL algorithm, if not yet activated in the other RAT;
- to re-establish SRBs and one or more DRBs;
[TS 38.331, clause 5.4.2.3]
The UE shall:
ETSI
1> perform RRC reconfiguration procedure as specified in 5.3.5;
NOTE: If the UE is connected to 5GC of the source E-UTRA cell, the delta configuration for PDCP and SDAP
can be used for intra-system inter-RAT handover.
[TS 36.331, clause 5.4.3.2]
E-UTRAN initiates the mobility from E-UTRA procedure to a UE in RRC_CONNECTED, possibly in response to a
MeasurementReport message or in response to reception of CS fallback indication for the UE from MME, by sending a
MobilityFromEUTRACommand message. E-UTRAN applies the procedure as follows:
- the procedure is initiated only when AS-security has been activated, and SRB2 with at least one DRB are setup
and not suspended;
[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:

1> if the MobilityFromEUTRACommand message includes the purpose set to handover:
2> else if the targetRAT-Type is set to nr:
3> consider inter-RAT mobility as initiated towards NR;
3> access the target cell indicated in the inter-RAT message in accordance with the specifications in TS
38.331 [82];
[TS 36.331, clause 5.4.3.4]
Upon successfully completing the handover, the cell change order or enhanced 1xRTT CS fallback, the UE shall:
1> else if the UE is connected to 5GC prior to the reception of the MobilityFromEUTRACommand and the
targetRAT-Type in the received MobilityFromEUTRACommand is set to nr:
2> reset MAC;
2> stop all timers that are running;
2> release ran-NotificationAreaInfo, if stored;
2> release the AS security context including the KRRCenc key, the KRRCint, the KUPint key and the KUPenc key, if
stored;
2> release all radio resources, including release of the RLC entity and the MAC configuration and the associated
PDCP entity and SDAP entity for all established RBs;
NOTE 1: PDCP and SDAP configured by the source configurations RAT prior to the handover that are
reconfigured and re-used by target RAT when delta signalling (i.e., during inter-RAT intra-sytem
handover when fullConfig is not present) is used, are not released as part of this procedure.
1> else:
ETSI
2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other';
NOTE 2: If the UE performs enhanced 1xRTT CS fallback along with concurrent mobility to CDMA2000 HRPD
and the connection to either CDMA2000 1xRTT or CDMA2000 HRPD succeeds, then the mobility from
E-UTRA is considered successful.
System Simulator:
- E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell".
- System information combination 31 as defined in TS 36.508 [7] clause 4.4.3.1 is used in the E-UTRA cell.
- System information combination NR-6 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in the NR cell.
UE:
- None.
Preamble:
- The UE isbrought to state RRC_CONNECTED using generic procedure parameters Connectivity (E-
UTRA/EPC), Unrestricted nr PDN (On), Test Loop Function (On) with UE test loop mode B, on E-UTRA Cell 1
according to the procedure described in TS 38.508-1 [4], clause 4.5.4.
ETSI

U-S Message
0 The SS configures NR Cell 1 as the "Serving - - - -
cell" and wait 5s.
1 The SS transmits a <-- E-UTRA RRC: - -
MobilityFromEUTRACommand message on E- MobilityFromEUTRACommand
UTRA Cell 1.
NR Cell 1?
3 The UE transmits a ULInformationTransfer --> NR RRC: ULInformationTransfer - -
message indicating “mobility registration REQUEST
updating” is sent to update the registration of
the actual tracking area.
4 SS sends an DLInformationTransfer message <-- NR RRC: DLInformationTransfer - -
and a REGISTRATION ACCEPT message 5GMM: REGISTRATION
containing a 5G-GUTI. ACCEPT
message and a REGISTRATION COMPLETE 5GMM: REGISTRATION
message. COMPLETE
described in step 6 below, the steps specified
in table 8.1.4.2.2.1.3.2-2 might take place.
6 The procedure in table 4.5A.2C.2.2-1 in TS - - - -
38.508-1 [4] is performed.
7 Void - - - -
8 The SS sends one IP Packet to the UE on the - - - -
session.
9 The UE loop backs the IP packet received in - - - -
step 8.

U-S Message
- EXCEPTION: Steps 1a1 to 1a2 describes - - - -
behaviour that depends on the UE
implementation; the "lower case letter"
identifies a step sequence that take place
depending on the UE implementation
1a1 IF the DNN of the established PDU session - - - -
is IMS AND the UE initiates IMS re-
registration on NR in the next 10s THEN
perform step 1 defined in Appendix A.12 of
TS 34.229-5 [41] .
(NOTE 1)
1a2 Step 2 of Appendix A.12 of TS 34.229-5 [41]. - - - -
NOTE 1: Whether a PDU session is for IMS is determined by the DNN/APN type of the entry in TS 38.508-1[7],
Table 4.8.4-1 which itself has been determined by the DNN IE in the UL NAS TRANSPORT message
which carried the corresponding PDU SESSION ESTABLISHMENT REQUEST or by
pc_APN_Default_Configuration if the DNN IE was not present. In future versions of the present
specification other types of DNNs may also initiate IMS registration - this will be determined by the entry
IMS registration for the type of DNN specified in TS 38.508-1[7], Table 4.8.4-1.
ETSI
Table 8.1.4.2.2.1.3.3-1: MobilityFromEUTRACommand (step 1, Table 8.1.4.2.2.1.3.2-1)
Derivation Path: TS 36.508 [7] table 4.6.1-6

MobilityFromEUTRACommand ::= SEQUENCE {
c1 CHOICE {
mobilityFromEUTRACommand-r8 SEQUENCE {
purpose CHOICE {
handover SEQUENCE {
targetRAT-Type nr
targetRAT-MessageContainer RRCReconfiguration
nas-SecurityParamFromEUTRA Not present
systemInformation Not present
}
}
}
}
}
}
Table 8.1.4.2.2.1.3.3-2: RRCReconfiguration (Table 8.1.4.2.2.1.3.3-1)

radioBearerConfig RadioBearerConfig as
per table 4.6.3-132 in TS
38.508-1 [4] with
conditions SRB1,SRB2
and DRB1
masterCellGroup CellGroupConfig with OCTET STRING
conditions SRB1,SRB2 (CONTAINING
and DRB1 CellGroupConfig)
fullConfig true
masterKeyUpdate MasterKeyUpdate
}
}
}
}
Table 8.1.4.2.2.1.3.3-3: Void
ETSI

RLC-Bearer-Config[1] RLC-Bearer-Config with entry 1
condition SRB1
condition SRB2
condition DRB1
}
mac-CellGroupConfig MAC-CellGroupConfig
physicalCellGroupConfig PhysicalCellGroupConfig
on
t304 ms1000
supplementaryUplink Not present
}
}
rlf-TimersAndConstants CHOICE {
setup RLF-
TimersAndConstants
}
}
}

Cell 1
}
ETSI
Table 8.1.4.2.2.1.3.3-6: MasterKeyUpdate (Table 8.1.4.2.2.1.3.3-2)

MasterKeyUpdate ::= SEQUENCE {
nextHopChainingCount NextHopChainingCount 38.508-1 [4] Table
4.6.3-83
nas-Container Octets 1 to 4 are 24.501 [22]
Message authentication 9.11.2.9 The
code(MAC) IE using {NH, value part of S1
NCC=2} mode to N1 mode
NAS transparent
Bits 1 to 4 of octet 5 are container
set according to PIXIT
algorithm.
Bits 5 to 8 of octet 5 are

set according to PIXIT
ciphering algorithm.
Bits 1 to 3 of octet 6
contains the Key set
identifier in 5G.
Bit 4 of octet 6 contains

the type of security
context flag(TSC).
Bits 5 to 7 of octet 6
contains the 3bit Next
hop chaining counter.
Bit 8 of octet 6 is Spare.
Octets 7 and 8 are spare

and shall be coded as
zero.
}
8.1.4.3 DAPS handover
8.1.4.3.1 DAPS handover with key change / Success / Intra-frequency
(1)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover }
ensure that {
with key change and dapsConfig is configured for a DRB }
then { UE performs DAPS handover to the target cell and keeps DL/UL reception/transmission with
the source gNB for the DRB configured with dapsConfig }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover and having received an
RRCReconfiguration message including a reconfigurationWithSync for handover to the neighbour cell
and a dapsConfig configured for any DRB }
ensure that {
then { UE transmits an RRCReconfigurationComplete message to the target gNB }
ETSI
(3)
ensure that {
when { UE receives an RRCReconfiguration message including a daps-SourceRelease }
then { UE releases the radio link with the source cell }
}
(4)
ensure that {
then { UE continues the downlink user data reception from the source gNB until releasing the
source cell }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.1 and 9.2.3.2.1
and TS 38.331 clause 5.3.5.3 and 5.3.5.5.2. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.1]
Network controlled mobility applies to UEs in RRC_CONNECTED and is categorized into two types of mobility: cell
level mobility and beam level mobility.
Cell Level Mobility requires explicit RRC signalling to be triggered, i.e. handover. For inter-gNB handover, the
signalling procedures consist of at least the following elemental components illustrated in Figure 9.2.3.1-1:
UE Source gNB Target gNB
1. HANDOVER REQUEST
Admission Control
2. HANDOVER REQUEST ACKNOWLEDGE
3. RRCReconfiguration
Switch to New Cell
4. RRCReconfigurationComplete
Figure 9.2.3.1-1: Inter-gNB handover procedures
1. The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface.
2. The target gNB performs admission control and provides the new RRC configuration as part of the
HANDOVER REQUEST ACKNOWLEDGE.
3. The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message
received in the HANDOVER REQUEST ACKNOWLEDGE. The RRCReconfiguration message includes at
least cell ID and all information required to access the target cell so that the UE can access the target cell without
reading system information. For some cases, the information required for contention-based and contention-free
random access can be included in the RRCReconfiguration message. The access information to the target cell
may include beam specific information, if any.
4. The UE moves the RRC connection to the target gNB and replies with the RRCReconfigurationComplete.
ETSI
NOTE 1: User Data can also be sent in step 4 if the grant allows.
In case of DAPS handover, the UE continues the downlink user data reception from the source gNB until releasing the
source cell and continues the uplink user data transmission to the source gNB until successful random access procedure
to the target gNB.
Only source and target PCell are used during DAPS handover. CA, DC, SUL, multi-TRP, NR sidelink configurations
and V2X sidelink configurations are released by the source gNB before the handover command is sent to the UE and
are not configured by the target gNB until the DAPS handover has completed (i.e. at source cell release).
The handover mechanism triggered by RRC requires the UE at least to reset the MAC entity and re-establish RLC,
except for DAPS handover, where upon reception of the handover command, the UE:
- Creates a MAC entity for target;
- Establishes the RLC entity and an associated DTCH logical channel for target for each DRB configured with
DAPS;
- For each DRB configured with DAPS, reconfigures the PDCP entity with separate security and ROHC functions
for source and target and associates them with the RLC entities configured by source and target respectively;
- Retains the rest of the source configurations until release of the source.
NOTE 2: The handling on RLC and PDCP for DRBs not configured with DAPS is the same as in normal handover.
NOTE 3: Void.
RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM
mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure
without a key change. For DRBs using RLC UM mode and for SRBs, PDCP can either be re-established together with a
security key change or remain as it is without a key change.
Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB
uses the same DRB configuration as the source gNB.
Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for
recovering from handover failure except in certain CHO or DAPS handover scenarios:
- When DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the
source cell, and reports DAPS handover failure via the source without triggering RRC connection re-
establishment if the source link has not been released.
- When initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a
CHO candidate and if network configured the UE to try CHO after handover/CHO failure, then the UE attempts
CHO execution once, otherwise re-establishment is performed.
DAPS handover for FR2 to FR2 case is not supported in this release of the specification.
[TS 38.300, clause 9.2.3.2.1]
The intra-NR RAN handover performs the preparation and execution phase of the handover procedure performed
without involvement of the 5GC, i.e. preparation messages are directly exchanged between the gNBs. The release of the
resources at the source gNB during the handover completion phase is triggered by the target gNB. The figure below
depicts the basic handover scenario where neither the AMF nor the UPF changes:
ETSI
UE Source gNB Target gNB AMF UPF(s)
User Data User Data
0.Mobility control information provided by AMF
1.Measurement Control and Reports
2. Handover Decision
3. HANDOVER REQUEST
4. Admission Control
5. HANDOVER REQUEST
ACKNOWLEDGE
6. RAN Handover Initiation
Deliver buffered data

and new data from UPF(s)
Detach from old cell 7a. EARLY STATUS

Synchronise to new cell TRANSER
7. SN STATUS TRANSFER
User Data
Buffer User Data

from Source gNB
8. RAN Handover Completion
8a. HANDOVER SUCCESS
8b. SN STATUS TRANSFER
User Data
User Data User Data
9. PATH SWITCH REQUEST
10. Path Switch in UPF(s)
End Marker
User Data

ACKNOWLEDGE
12. UE CONTEXT RELEASE
http://msc-generator.sourceforge.net v6.3.7
Figure 9.2.3.2.1-1: Intra-AMF/UPF Handover
0. The UE context within the source gNB contains information regarding roaming and access restrictions which
were provided either at connection establishment or at the last TA update.
1. The source gNB configures the UE measurement procedures and the UE reports according to the measurement
configuration.
2. The source gNB decides to handover the UE, based on MeasurementReport and RRM information.
ETSI
3. The source gNB issues a Handover Request message to the target gNB passing a transparent RRC container with
necessary information to prepare the handover at the target side. The information includes at least the target cell
ID, KgNB*, the C-RNTI of the UE in the source gNB, RRM-configuration including UE inactive time, basic
AS-configuration including antenna Info and DL Carrier Frequency, the current QoS flow to DRB mapping
rules applied to the UE, the SIB1 from source gNB, the UE capabilities for different RATs, PDU session related
information, and can include the UE reported measurement information including beam-related information if
available. The PDU session related information includes the slice information and QoS flow level QoS profile(s).
The source gNB may also request a DAPS handover for one or more DRBs.
NOTE 1: After issuing a Handover Request, the source gNB should not reconfigure the UE, including performing
Reflective QoS flow to DRB mapping.
4. Admission Control may be performed by the target gNB. Slice-aware admission control shall be performed if the
slice information is sent to the target gNB. If the PDU sessions are associated with non-supported slices the
target gNB shall reject such PDU Sessions.
5. The target gNB prepares the handover with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE
to the source gNB, which includes a transparent container to be sent to the UE as an RRC message to perform
the handover. The target gNB also indicates if a DAPS handover is accepted.
NOTE 2: As soon as the source gNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the
transmission of the handover command is initiated in the downlink, data forwarding may be initiated.
NOTE 3: For DRBs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source
gNB, until SN assignment is handed over to the target gNB in step 8b, for which the normal data
forwarding follows as defined in 9.2.3.2.3.
6. The source gNB triggers the Uu handover by sending an RRCReconfiguration message to the UE, containing the
information required to access the target cell: at least the target cell ID, the new C-RNTI, the target gNB security
algorithm identifiers for the selected security algorithms. It can also include a set of dedicated RACH resources,
the association between RACH resources and SSB(s), the association between RACH resources and UE-specific
CSI-RS configuration(s), common RACH resources, and system information of the target cell, etc.
NOTE 4: For DRBs configured with DAPS, the source gNB does not stop transmitting downlink packets until it
receives the HANDOVER SUCCESS message from the target gNB in step 8a.
NOTE 4a: CHO cannot be configured simultaneously with DAPS handover.
7a. For DRBs configured with DAPS, the source gNB sends the EARLY STATUS TRANSFER message. The DL
COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the
first PDCP SDU that the source gNB forwards to the target gNB. The source gNB does not stop assigning SNs
to downlink PDCP SDUs until it sends the SN STATUS TRANSFER message to the target gNB in step 8b.
7. For DRBs not configured with DAPS, the source gNB sends the SN STATUS TRANSFER message to the target
gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of DRBs for
which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at
least the PDCP SN of the first missing UL PDCP SDU and may include a bit map of the receive status of the out
of sequence UL PDCP SDUs that the UE needs to retransmit in the target cell, if any. The downlink PDCP SN
transmitter status indicates the next PDCP SN that the target gNB shall assign to new PDCP SDUs, not having a
PDCP SN yet.
NOTE 5: In case of DAPS handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter
status for a DRB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS
TRANSFER message in step 8b instead of step 7.
NOTE 6: For DRBs configured with DAPS, the source gNB may additionally send the EARLY STATUS
TRANSFER message(s) between step 7 and step 8b, to inform discarding of already forwarded PDCP
SDUs. The target gNB does not transmit forwarded downlink PDCP SDUs to the UE, whose COUNT is
less than the conveyed DL COUNT value and discards them if transmission has not been attempted
already.
8. The UE synchronises to the target cell and completes the RRC handover procedure by sending
RRCReconfigurationComplete message to target gNB. In case of DAPS handover, the UE does not detach from
the source cell upon receiving the RRCReconfiguration message. The UE releases the source resources and
ETSI
configurations and stops DL/UL reception/transmission with the source upon receiving an explicit release from
the target node.
NOTE 6a: From RAN point of view, the DAPS handover is considered to only be completed after the UE has
released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover
or inter-RAT handover cannot be initiated until the source cell has been released.
8a/b In case of DAPS handover, the target gNB sends the HANDOVER SUCCESS message to the source gNB to
inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS
TRANSFER message for DRBs configured with DAPS for which the description in step 7 applies, and the
normal data forwarding follows as defined in 9.2.3.2.3.
NOTE 7: The uplink PDCP SN receiver status and the downlink PDCP SN transmitter status are also conveyed for
DRBs with RLC-UM in the SN STATUS TRANSFER message in step 8b, if configured with DAPS.
NOTE 8: For DRBs configured with DAPS, the source gNB does not stop delivering uplink QoS flows to the UPF
until it sends the SN STATUS TRANSFER message in step 8b. The target gNB does not forward QoS
flows of the uplink PDCP SDUs successfully received in-sequence to the UPF until it receives the SN
STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN
receiver status indicates the start of uplink PDCP SDUs to be delivered to the UPF. The target gNB does
not deliver any uplink PDCP SDUs which has an UL COUNT lower than the provided.
NOTE 9: Void.
9. The target gNB sends a PATH SWITCH REQUEST message to AMF to trigger 5GC to switch the DL data path
towards the target gNB and to establish an NG-C interface instance towards the target gNB.
10. 5GC switches the DL data path towards the target gNB. The UPF sends one or more "end marker" packets on the
old path to the source gNB per PDU session/tunnel and then can release any U-plane/TNL resources towards the
source gNB.
11. The AMF confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST
ACKNOWLEDGE message.
12. Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB
sends the UE CONTEXT RELEASE to inform the source gNB about the success of the handover. The source
gNB can then release radio and C-plane related resources associated to the UE context. Any ongoing data
forwarding may continue.
Upon receiving a handover command requesting DAPS handover, the UE suspends source cell SRBs, stops sending and
receiving any RRC control plane signalling toward the source cell, and establishes SRBs for the target cell. The UE
releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after
successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is
available, then the UE reverts back to the source cell configuration and resumes source cell SRBs for control plane
signalling transmission.
[TS 38.331, clause 5.3.5.3]
1> if the RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection while
timer T311 is running, as defined in 5.3.7.3:
2> remove all the entries within VarConditionalReconfig, if any;
1> if the RRCReconfiguration includes the daps-SourceRelease:
2> reset the source MAC and release the source MAC configuration;
3> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical
channel for the source SpCell;
ETSI
3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
2> for each SRB:
3> release the PDCP entity for the source SpCell;
3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for
the source SpCell;
2> release the physical channel configuration for the source SpCell;
2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and
the KUPenc key), if any;
group successfully completes a Random Access procedure triggered above:
2> stop timer T310 for source SpCell if running;
2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS
2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in
TS 38.323 [5];
NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast
NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the
configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may
include more than the concerned UE assistance information within the UEAssistanceInformation
according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message may not be similar to
the original one.
[TS 38.331, clause 5.3.5.5.2]
1> if no DAPS bearer is configured:
1> if this procedure is executed for the MCG:
2> if timer T316 is running;
3> stop timer T316;
3> clear the information included in VarRLF-Report, if any;
2> resume MCG transmission, if suspended.
ETSI
1> else:
1> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;
1> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213 [13];
NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell.
cell group;
cell group;
group;
2> for each SRB:
group;
group;
NOTE 3: Void
ETSI
System Simulator:
- NR Cell 1 is the Serving cell and the power level is configured to ''Serving Cell” defined in TS 38.508-1 [4]
Table 6.2.2.1-3.
- NR Cell 2 is the Suitable neighbour intra-frequency cell and the power level is configured to '' Suitable
neighbour intra-frequency cell” defined in TS 38.508-1 [4] Table 6.2.2.1-3
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for both NR Cells
UE:
- None.
Preamble:
Table 4.4A.2-3.
ETSI

U-S Message
- EXCEPTION: In parallel with step 2-3, parallel - - - -
2 Check: Does the test result of generic test <-- - 1 P
IP data on DRB#n of the first PDU session on
NR Cell 1?
3 Void - - - -
to respond to the latest preamble on NR Cell 2.
5 Check: Does UE transmit an --> NR RRC: 1,2 P
Cell 2?
5A The SS transmits one IP Packet to verify data - - - -
path on DRB#n of the first PDU session on NR
Cell 1
5B Check: Does the UE transmit HARQ feedback - - 4 P
after step 5A?
Cell 2?
procedure in TS 38.508-1 Table 4.9.1-1
NR Cell 2?
9 The SS transmits one IP Packet to verify data - - - -
path on DRB#n of the first PDU session on NR
Cell 1.
10 Check: Does UE send the IP Packet on - - 3 F
DRB#n of the first PDU session in the uplink
on NR Cell 1 within the next 1s?

U-S Message
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with Condition RBConfig_KeyChange

conditions
(SRB_NR_PDCP and
DRB1 AND DAPS_PDCP
(CONTAINING
CellGroupConfig)
}
}
}
}

establish_RLC
establish_RLC
drb-Identity of
condition DRBn
}
Cell 2
}
uplink RACH-ConfigDedicated Table
8.1.4.3.1.3.3-3
}
}
}
}
ETSI

cfra SEQUENCE {
rach-ConfigGeneric RACH-ConfigGeneric Table
8.1.4.3.1.3.3-4
}
}
}

}
Derivation Path: TS 38.508-1 [4], Table 4.8.1-13 with Condition DAPS_HO_ReleaseSource
8.1.4.3.2 DAPS handover / HO Failure and source link available / HO Success and RLF in
source / Intra-frequency
(1)
reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for a DRB }
ensure that {
when { T304 of the MCG expires and the source link has not been released }
then { UE falls back to source cell configuration, resumes the connection with source cell, and
reports DAPS HO failure via the source without triggering RRC connection re-establishment }
}
(2)
reconfigurationWithSync for handover to the neighbour cell and a dapsConfig configured for a DRB }
ensure that {
when { Radio link failure is detected for the source MCG }
then { UE suspends all DRBs in the source, releases the source connection and continues the
handover procedure to target }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.1 and 9.2.3.2.1
and TS 38.331 clause 5.3.5.3, 5.3.5.5.2, 5.3.5.5.6, 5.3.5.5.7, 5.3.5.8.3, 5.3.10.3 and 5.7.5.3. Unless otherwise stated
[TS 38.300, clause 9.2.3.1]
Network controlled mobility applies to UEs in RRC_CONNECTED and is categorized into two types of mobility: cell
level mobility and beam level mobility.
Cell Level Mobility requires explicit RRC signalling to be triggered, i.e. handover. For inter-gNB handover, the
signalling procedures consist of at least the following elemental components illustrated in Figure 9.2.3.1-1:
ETSI
UE Source gNB Target gNB
1. HANDOVER REQUEST
Admission Control
Switch to New Cell
Figure 9.2.3.1-1: Inter-gNB handover procedures
1. The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface.
2. The target gNB performs admission control and provides the new RRC configuration as part of the
HANDOVER REQUEST ACKNOWLEDGE.
3. The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message
received in the HANDOVER REQUEST ACKNOWLEDGE. The RRCReconfiguration message includes at
least cell ID and all information required to access the target cell so that the UE can access the target cell without
reading system information. For some cases, the information required for contention-based and contention-free
random access can be included in the RRCReconfiguration message. The access information to the target cell
may include beam specific information, if any.
4. The UE moves the RRC connection to the target gNB and replies with the RRCReconfigurationComplete.
NOTE 1: User Data can also be sent in step 4 if the grant allows.
In case of DAPS handover, the UE continues the downlink user data reception from the source gNB until releasing the
source cell and continues the uplink user data transmission to the source gNB until successful random access procedure
to the target gNB.
Only source and target PCell are used during DAPS handover. CA, DC, SUL, multi-TRP, NR sidelink configurations
and V2X sidelink configurations are released by the source gNB before the handover command is sent to the UE and
are not configured by the target gNB until the DAPS handover has completed (i.e. at source cell release).
The handover mechanism triggered by RRC requires the UE at least to reset the MAC entity and re-establish RLC,
except for DAPS handover, where upon reception of the handover command, the UE:
- Creates a MAC entity for target;
- Establishes the RLC entity and an associated DTCH logical channel for target for each DRB configured with
DAPS;
- For each DRB configured with DAPS, reconfigures the PDCP entity with separate security and ROHC functions
for source and target and associates them with the RLC entities configured by source and target respectively;
- Retains the rest of the source configurations until release of the source.
NOTE 2: The handling on RLC and PDCP for DRBs not configured with DAPS is the same as in normal handover.
NOTE 3: Void.
RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM
mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure
without a key change. For DRBs using RLC UM mode and for SRBs, PDCP can either be re-established together with a
security key change or remain as it is without a key change.
Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB
uses the same DRB configuration as the source gNB.
ETSI
Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for
recovering from handover failure except in certain CHO or DAPS handover scenarios:
- When DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the
source cell, and reports DAPS handover failure via the source without triggering RRC connection re-
establishment if the source link has not been released.
- When initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a
CHO candidate and if network configured the UE to try CHO after handover/CHO failure, then the UE attempts
CHO execution once, otherwise re-establishment is performed.
DAPS handover for FR2 to FR2 case is not supported in this release of the specification.
[TS 38.300, clause 9.2.3.2.1]
The intra-NR RAN handover performs the preparation and execution phase of the handover procedure performed
without involvement of the 5GC, i.e. preparation messages are directly exchanged between the gNBs. The release of the
resources at the source gNB during the handover completion phase is triggered by the target gNB. The figure below
depicts the basic handover scenario where neither the AMF nor the UPF changes:
ETSI
UE Source gNB Target gNB AMF UPF(s)
User Data User Data
2. Handover Decision
3. HANDOVER REQUEST
5. HANDOVER REQUEST
ACKNOWLEDGE
6. RAN Handover Initiation
Deliver buffered data

and new data from UPF(s)
Detach from old cell 7a. EARLY STATUS

Synchronise to new cell TRANSER
7. SN STATUS TRANSFER
User Data
Buffer User Data

from Source gNB
8. RAN Handover Completion
User Data
User Data User Data
10. Path Switch in UPF(s)
End Marker
User Data

ACKNOWLEDGE
12. UE CONTEXT RELEASE
Figure 9.2.3.2.1-1: Intra-AMF/UPF Handover
0. The UE context within the source gNB contains information regarding roaming and access restrictions which
were provided either at connection establishment or at the last TA update.
1. The source gNB configures the UE measurement procedures and the UE reports according to the measurement
configuration.
2. The source gNB decides to handover the UE, based on MeasurementReport and RRM information.
ETSI
3. The source gNB issues a Handover Request message to the target gNB passing a transparent RRC container with
necessary information to prepare the handover at the target side. The information includes at least the target cell
ID, KgNB*, the C-RNTI of the UE in the source gNB, RRM-configuration including UE inactive time, basic
AS-configuration including antenna Info and DL Carrier Frequency, the current QoS flow to DRB mapping
rules applied to the UE, the SIB1 from source gNB, the UE capabilities for different RATs, PDU session related
information, and can include the UE reported measurement information including beam-related information if
available. The PDU session related information includes the slice information and QoS flow level QoS profile(s).
The source gNB may also request a DAPS handover for one or more DRBs.
NOTE 1: After issuing a Handover Request, the source gNB should not reconfigure the UE, including performing
Reflective QoS flow to DRB mapping.
4. Admission Control may be performed by the target gNB. Slice-aware admission control shall be performed if the
slice information is sent to the target gNB. If the PDU sessions are associated with non-supported slices the
target gNB shall reject such PDU Sessions.
5. The target gNB prepares the handover with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE
to the source gNB, which includes a transparent container to be sent to the UE as an RRC message to perform
the handover. The target gNB also indicates if a DAPS handover is accepted.
NOTE 2: As soon as the source gNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the
transmission of the handover command is initiated in the downlink, data forwarding may be initiated.
NOTE 3: For DRBs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source
gNB, until SN assignment is handed over to the target gNB in step 8b, for which the normal data
forwarding follows as defined in 9.2.3.2.3.
6. The source gNB triggers the Uu handover by sending an RRCReconfiguration message to the UE, containing the
information required to access the target cell: at least the target cell ID, the new C-RNTI, the target gNB security
algorithm identifiers for the selected security algorithms. It can also include a set of dedicated RACH resources,
the association between RACH resources and SSB(s), the association between RACH resources and UE-specific
CSI-RS configuration(s), common RACH resources, and system information of the target cell, etc.
NOTE 4: For DRBs configured with DAPS, the source gNB does not stop transmitting downlink packets until it
receives the HANDOVER SUCCESS message from the target gNB in step 8a.
NOTE 4a: CHO cannot be configured simultaneously with DAPS handover.
7a. For DRBs configured with DAPS, the source gNB sends the EARLY STATUS TRANSFER message. The DL
COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the
first PDCP SDU that the source gNB forwards to the target gNB. The source gNB does not stop assigning SNs
to downlink PDCP SDUs until it sends the SN STATUS TRANSFER message to the target gNB in step 8b.
7. For DRBs not configured with DAPS, the source gNB sends the SN STATUS TRANSFER message to the target
gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of DRBs for
which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at
least the PDCP SN of the first missing UL PDCP SDU and may include a bit map of the receive status of the out
of sequence UL PDCP SDUs that the UE needs to retransmit in the target cell, if any. The downlink PDCP SN
transmitter status indicates the next PDCP SN that the target gNB shall assign to new PDCP SDUs, not having a
PDCP SN yet.
NOTE 5: In case of DAPS handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter
status for a DRB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS
TRANSFER message in step 8b instead of step 7.
NOTE 6: For DRBs configured with DAPS, the source gNB may additionally send the EARLY STATUS
TRANSFER message(s) between step 7 and step 8b, to inform discarding of already forwarded PDCP
SDUs. The target gNB does not transmit forwarded downlink PDCP SDUs to the UE, whose COUNT is
less than the conveyed DL COUNT value and discards them if transmission has not been attempted
already.
8. The UE synchronises to the target cell and completes the RRC handover procedure by sending
RRCReconfigurationComplete message to target gNB. In case of DAPS handover, the UE does not detach from
the source cell upon receiving the RRCReconfiguration message. The UE releases the source resources and
ETSI
configurations and stops DL/UL reception/transmission with the source upon receiving an explicit release from
the target node.
NOTE 6a: From RAN point of view, the DAPS handover is considered to only be completed after the UE has
released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover
or inter-RAT handover cannot be initiated until the source cell has been released.
8a/b In case of DAPS handover, the target gNB sends the HANDOVER SUCCESS message to the source gNB to
inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS
TRANSFER message for DRBs configured with DAPS for which the description in step 7 applies, and the
normal data forwarding follows as defined in 9.2.3.2.3.
NOTE 7: The uplink PDCP SN receiver status and the downlink PDCP SN transmitter status are also conveyed for
DRBs with RLC-UM in the SN STATUS TRANSFER message in step 8b, if configured with DAPS.
NOTE 8: For DRBs configured with DAPS, the source gNB does not stop delivering uplink QoS flows to the UPF
until it sends the SN STATUS TRANSFER message in step 8b. The target gNB does not forward QoS
flows of the uplink PDCP SDUs successfully received in-sequence to the UPF until it receives the SN
STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN
receiver status indicates the start of uplink PDCP SDUs to be delivered to the UPF. The target gNB does
not deliver any uplink PDCP SDUs which has an UL COUNT lower than the provided.
NOTE 9: Void.
9. The target gNB sends a PATH SWITCH REQUEST message to AMF to trigger 5GC to switch the DL data path
towards the target gNB and to establish an NG-C interface instance towards the target gNB.
10. 5GC switches the DL data path towards the target gNB. The UPF sends one or more "end marker" packets on the
old path to the source gNB per PDU session/tunnel and then can release any U-plane/TNL resources towards the
source gNB.
11. The AMF confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST
ACKNOWLEDGE message.
12. Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target gNB
sends the UE CONTEXT RELEASE to inform the source gNB about the success of the handover. The source
gNB can then release radio and C-plane related resources associated to the UE context. Any ongoing data
forwarding may continue.
Upon receiving a handover command requesting DAPS handover, the UE suspends source cell SRBs, stops sending and
receiving any RRC control plane signalling toward the source cell, and establishes SRBs for the target cell. The UE
releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after
successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is
available, then the UE reverts back to the source cell configuration and resumes source cell SRBs for control plane
signalling transmission.
[TS 38.331, clause 5.3.5.3]
1> if the RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection while
timer T311 is running, as defined in 5.3.7.3:
1> if the RRCReconfiguration includes the daps-SourceRelease:
2> reset the source MAC and release the source MAC configuration;
channel for the source SpCell;
ETSI
2> for each SRB:
3> release the PDCP entity for the source SpCell;
3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for
the source SpCell;
2> release the physical channel configuration for the source SpCell;
2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and
the KUPenc key), if any;
group successfully completes a Random Access procedure triggered above:
2> stop timer T310 for source SpCell if running;
2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS
2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in
TS 38.323 [5];
NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast
NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the
configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may
include more than the concerned UE assistance information within the UEAssistanceInformation
according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message may not be similar to
the original one.
[TS 38.331, clause 5.3.5.5.2]
1> if no DAPS bearer is configured:
1> if this procedure is executed for the MCG:
2> if timer T316 is running;
3> stop timer T316;
3> clear the information included in VarRLF-Report, if any;
2> resume MCG transmission, if suspended.
ETSI
1> else:
1> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;
1> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213 [13];
NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell.
cell group;
cell group;
group;
2> for each SRB:
group;
group;
NOTE 3: Void
[TS 38.331, clause 5.3.5.5.6]
The UE shall:
ETSI
1> if the received rlf-TimersAndConstants is set to release:
2> if any DAPS bearer is configured:
3> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in
ue-TimersAndConstants received in SIB1;
2> else:
3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-
TimersAndConstants received in SIB1;
1> else:
3> configure the value of timers and constants for the target cell group in accordance with received rlf-
TimersAndConstants;
2> else:
3> (re-)configure the value of timers and constants in accordance with received rlf-TimersAndConstants;
3> stop timer T310 for this cell group, if running;
3> stop timer T312 for this cell group, if running;
3> reset the counters N310 and N311.
[TS 38.331, clause 5.3.5.5.7]
The UE shall:
1> if the SpCellConfig contains the rlf-TimersAndConstants:
2> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6;
1> else if rlf-TimersAndConstants is not configured for this cell group:
3> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in
ue-TimersAndConstants received in SIB1;
2> else
3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-
TimersAndConstants received in SIB1;
[TS 38.331, clause 5.3.5.8.3]
The UE shall:
2> release dedicated msgA PUSCH resources provided in rach-ConfigDedicated if configured;
2> if any DAPS bearer is configured, and radio link failure is not detected in the source PCell, according to
subclause 5.3.10.3:
3> reset MAC for the target PCell and release the MAC configuration for the target PCell;
ETSI
channel for the target PCell;
3> for each SRB:
4> if the masterKeyUpdate was not received:
5> configure the PDCP entity for the source PCell with state variables continuation as specified in TS
38.323 [5], the state variables as the PDCP entity for the target PCell;
4> release the PDCP entity for the target PCell;
4> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel
for the target PCell;
4> trigger the PDCP entity for the source PCell to perform SDU discard as specified in TS 38.323 [5];
4> re-establish the RLC entity for the source PCell;
3> release the physical channel configuration for the target PCell;
3> revert back to the SDAP configuration used in the source PCell;
3> discard the keys used in target PCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the
KUPenc key), if any;
3> resume suspended SRBs in the source PCell;
3> for each non DAPS bearer:
4> revert back to the UE configuration used for the DRB in the source PCell, includes PDCP, RLC states
variables, the security configuration and the data stored in transmission and reception buffers in PDCP
and RLC entities ;
3> revert back to the UE measurement configuration used in the source PCell;
3> initiate the failure information procedure as specified in subclause 5.7.5 to report DAPS handover failure.
NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.
[TS 38.331, clause 5.3.10.3]
The UE shall:
1> if any DAPS bearer is configured and T304 is running:
2> upon T310 expiry in source SpCell; or
2> upon random access problem indication from source MCG MAC; or
2> upon indication from source MCG RLC that the maximum number of retransmissions has been reached; or
2> upon consistent uplink LBT failure indication from source MCG MAC:
3> consider radio link failure to be detected for the source MCG i.e. source RLF;
3> suspend the transmission and reception of all DRBs in the source MCG;
3> reset MAC for the source MCG;
3> release the source connection.
[TS 38.331, clause 5.7.5.3]
ETSI
The UE shall:
1> if initiated to provide DAPS failure information, set FailureInfoDAPS as follows:
2> set the failureType as daps-failure;
1> if used to inform the network about a failure for an MCG RLC bearer or DAPS failure information:
2> submit the FailureInformation message to lower layers for transmission via SRB1;
System Simulator:
- NR Cell 1 is the Serving cell and NR Cell 2 is the Suitable neighbour intra-frequency cell.
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for NR Cells
UE:
- None.
Preamble:
- If pc_IP_Ping is set to TRUE then, the UE is in 5GS state 3N-A on NR Cell 1 according to TS 38.508-1 [4],
clause 4.4A.2 Table 4.4A.2-3.
Table 8.1.4.3.2.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the NR
marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in Table 8.1.4.3.2.3.2-3.

1 2
SS/PBCH dBm/SC
T0 -88 -94
SSS EPRE S
SS/PBCH dBm/SC
T1 -88 off
SSS EPRE S
SS/PBCH dBm/SC
T2 -88 -88
SSS EPRE S
SS/PBCH dBm/SC
T3 off -88
SSS EPRE S
ETSI

1 2
SS/PBCH dBm/SC
T0 FFS FFS
SSS EPRE S
SS/PBCH dBm/SC
T1 FFS off
SSS EPRE S
SS/PBCH dBm/SC
T2 FFS FFS
SSS EPRE S
SS/PBCH dBm/SC
T3 off FFS
SSS EPRE S
ETSI

U-S Message
3 Check: Does the UE transmit an --> NR RRC: 1 F
Cell 1 within 5s?
4 Check: Does the UE transmit a --> NR RRC: FailureInformation 1 P
FailureInformation message with failureType-
r16 set to daps-failure on NR Cell 1 within 5s?
indicate that the UE revert back to the
configuration used in the source PCell on
DRB#n of the first PDU session on NR Cell 1?
according to the row "T3" and waits 300ms to
ensure T310 expires in NR Cell 1.
to respond to the latest preamble on NR Cell
2.
10 Check: Does UE transmit an --> NR RRC: 2 P
Cell 2?
NR Cell 2?
13 Check: Does the UE transmits an --> NR RRC: - -
Cell 2.

U-S Message
ETSI
Table 8.1.5.6.1.3.3-1: SIB1 for NR Cell 1 (all steps)

SIB1 ::= SEQUENCE {
ue-TimersAndConstants SEQUENCE {
t310 ms0 0 ms
}
}
Derivation Path: TS 38.508-1 [4], Table 4.8.1-1A with Condition RBConfig_KeyChange

conditions
(SRB_NR_PDCP and
DRB1 AND DAPS_PDCP
(CONTAINING
CellGroupConfig)
Table
8.1.4.3.2.3.3-3
}
}
}
}
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with condition PCell_change and CFRA
establish_RLC
establish_RLC
drb-Identity of
condition DRBn
}
Cell 2
}
uplink RACH-ConfigDedicated Table
8.1.4.3.2.3.3-4
}
}
}
}

cfra SEQUENCE {
rach-ConfigGeneric RACH-ConfigGeneric Table
8.1.4.3.2.3.3-5
}
}
}

}
Table 8.1.4.3.2.3.3-6: FailureInformation (step 4, Table 8.1.4.3.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-4 with Condition DAPS_HOF
ETSI
Derivation Path: TS 38.508-1 [4], Table 4.8.1-13 with Condition DAPS_HO_ReleaseSource
8.1.4.3.3
8.1.4.3.4 DAPS handover / Success / Inter-frequency
(1)
with { UE in NR RRC_CONNECTED state and supporting DAPS handover }
ensure that {
and dapsConfig is configured for a DRB }
then { UE performs DAPS handover to the target cell and keeps DL/UL reception/transmission with
the source gNB for the DRB configured with dapsConfig }
}
(2)
ensure that {
then { UE transmits an RRCReconfigurationComplete message to the target gNB }
}
(3)
ensure that {
when { UE receives an RRCReconfiguration message including a daps-SourceRelease }
then { UE releases the radio link with the source cell }
}
Same as test case 8.1.4.3.1.
- System information combination: NR-4 replaces NR-2.
ETSI
8.1.4.4 Conditional handover
8.1.4.4.1 Conditional handover / Success / A3 / A5 / A3+A5
(1)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving an
RRCReconfiguration message including ConditionalReconfiguration }
ensure that {
when { any CHO execution condition is not satisfied }
then { UE maintains connection with source gNB and starts evaluating the CHO execution
conditions for the candidate cell(s) }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting conditional handover }
ensure that {
when { UE receives an RRCReconfiguration message including ConditionalReconfiguration and only
event A3 is configured as conditional handover trigger event }
then { UE starts evaluating the CHO execution condition A3 and perform conditional handover to
the neighbour cell triggered in conditional configuration execution }
}
(3)
ensure that {
when { UE receives an RRCReconfiguration message including ConditionalReconfiguration and only
event A5 is configured as conditional handover trigger event }
then { UE starts evaluating the CHO execution condition A5 and perform conditional handover to
the neighbour cell triggered in conditional configuration execution }
}
(4)
ensure that {
when { UE receives an RRCReconfiguration message including ConditionalReconfiguration and both
event A3 and event A5 are configured as conditional handover trigger events }
then { UE starts evaluating the CHO execution condition A3 and A5 and perform conditional
handover to the neighbour cell triggered in conditional configuration execution }
}
(5)
ensure that {
when { UE perform conditional handover procedure successfully }
then { UE releases stored CHO configurations }
}
References: The conformance requirements covered in the present TC are specified in: TS 38.300 9.2.3.4.1, and
9.2.3.4.2 and TS 38.331 clause 5.3.5.1, 5.3.5.13.1, 5.3.5.13.4 and 5.3.5.13.5. Unless otherwise stated these are Rel-16
requirements.
[TS 38.300, clause 9.2.3.4.1]
A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover
execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO
ETSI
configuration, and stops evaluating the execution condition(s) once a handover is executed (legacy handover or
conditional handover execution).
The following principles apply to CHO:
- The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s)
and execution condition(s) generated by the source gNB.
- An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in [12]).
Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and
SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single
candidate cell.
- Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration),
the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO
configuration.
- While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not
monitor source cell.
CHO is not supported for NG-C based handover in this release of the specification.
[TS 38.300, clause 9.2.3.4.2]
As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional
handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged
between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is
triggered by the target gNB. The figure below depicts the basic conditional handover scenario where neither the AMF
nor the UPF changes:
ETSI
UE Source gNB Target gNB Other potential AMF UPF(s)

target gNB(s)
User Data User Data
2. CHO Decision
3. HANDOVER REQUEST
3. HANDOVER REQUEST
5. HANDOVER REQUEST
ACKNOWLEDGE
Evaluate the CHO conditions. 7a. EARLY STATUS TRANSFER
Detach from the old cell, User Data

synchronize to the new cell.
8. CHO Handover completion
User Data
8c. HANDOVER CANCEL
Figure 9.2.3.2.1-1 step 9-12
Figure 9.2.3.4.2-1: Intra-AMF/UPF Conditional Handover
0/1. Same as step 0, 1 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
2. The source gNB decides to use CHO.
3. The source gNB requests CHO for one or more candidate cells belonging to one or more candidate gNBs. A
CHO request message is sent for each candidate cell.
4. Same as step 4 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1.
5. The candidate gNB(s) sends CHO response (HO REQUEST ACKNOWLEDGE) including configuration of
CHO candidate cell(s) to the source gNB. The CHO response message is sent for each candidate cell.
ETSI
6. The source gNB sends an RRCReconfiguration message to the UE, containing the configuration of CHO
candidate cell(s) and CHO execution condition(s).
NOTE 1: CHO configuration of candidate cells can be followed by other reconfiguration from the source gNB.
NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover configuration.
7. The UE sends an RRCReconfigurationComplete message to the source gNB.
7a If early data forwarding is applied, the source gNB sends the EARLY STATUS TRANSFER message.
8. The UE maintains connection with the source gNB after receiving CHO configuration, and starts evaluating the
CHO execution conditions for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding
CHO execution condition, the UE detaches from the source gNB, applies the stored corresponding configuration
for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure
by sending RRCReconfigurationComplete message to the target gNB. The UE releases stored CHO
configurations after successful completion of RRC handover procedure.
8a/b The target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has
successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message
following the principles described in step 7 of Intra-AMF/UPF Handover in clause 9.2.3.2.1.
NOTE 2: Late data forwarding may be initiated as soon as the source gNB receives the HANDOVER SUCCESS
message.
8c. The source gNB sends the HANDOVER CANCEL message toward the other signalling connections or other
candidate target gNBs, if any, to cancel CHO for the UE.
[TS 38.331, clause 5.3.5.1]
UE Network
RRCReconfiguration
Figure 5.3.5.1-1: RRC reconfiguration, successful
UE Network
RRCReconfiguration
RRC connection re-establishment
Figure 5.3.5.1-2: RRC reconfiguration, failure
The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs, to perform
reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to
add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change configuration.
As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.
ETSI
[TS 38.331, clause 5.3.5.13.1]
The network configures the UE with one or more candidate target SpCells in the conditional reconfiguration. The UE
evaluates the condition of each configured candidate target SpCell. The UE applies the conditional reconfiguration
associated with one of the target SpCells which fulfils associated execution condition. The network provides the
configuration parameters for the target SpCell in the ConditionalReconfiguration IE.
The UE performs the following actions based on a received ConditionalReconfiguration IE:
1> if the ConditionalReconfiguration contains the condReconfigToRemoveList:
2> perform conditional reconfiguration removal procedure as specified in 5.3.5.13.2;
1> if the ConditionalReconfiguration contains the condReconfigToAddModList:
2> perform conditional reconfiguration addition/modification as specified in 5.3.5.13.3;
[TS 38.331, clause 5.3.5.13.4]
The UE shall:
1> for each condReconfigId within the VarConditionalReconfig:
2> consider the cell which has a physical cell identity matching the value indicated in the
ServingCellConfigCommon included in the reconfigurationWithSync in the received condRRCReconfig to be
applicable cell;
2> for each measId included in the measIdList within VarMeasConfig indicated in the condExecutionCond
associated to condReconfigId:
3> if the entry condition(s) applicable for this event associated with the condReconfigId, i.e. the event
corresponding with the condEventId(s) of the corresponding condTriggerConfig within
VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering
taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig:
4> consider the event associated to that measId to be fulfilled;
3> if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e. the event
corresponding with the condEventId(s) of the corresponding condTriggerConfig within
VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering
taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig:
4> consider the event associated to that measId to be not fulfilled;
2> if event(s) associated to all measId(s) within condTriggerConfig for a target candidate cell within the stored
condRRCReconfig are fulfilled:
3> consider the target candidate cell within the stored condRRCReconfig, associated to that condReconfigId,
as a triggered cell;
3> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5;
NOTE: Up to 2 MeasId can be configured for each condReconfigId. The conditional reconfiguration event of the
2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and
triggering threshold.
[TS 38.331, clause 5.3.5.13.5]
The UE shall:
1> if more than one triggered cell exists:
2> select one of the triggered cells as the selected cell for conditional reconfiguration execution;
1> for the selected cell of conditional reconfiguration execution:
2> apply the stored condRRCReconfig of the selected cell and perform the actions as specified in 5.3.5.3;
ETSI
NOTE: If multiple NR cells are triggered in conditional reconfiguration execution, it is up to UE implementation

which one to select, e.g. the UE considers beams and beam quality to select one of the triggered cells for
execution.
System Simulator:
- System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used for NR cells
UE:
- None.
Preamble:
Tables 8.1.4.4.1.3.2-1 and 8.1.4.4.1.3.2-2 illustrate the downlink power levels to be applied for NR Cells at various time
instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration
marked "T1", T2 and "T3", are applied at the point indicated in the Main behaviour description in Table 8.1.4.4.1.3.2-3.

Power levels are such that UE registered on NR
SS/PBCH dBm/
T0 -82 -91 -91 Cell 1 and entry condition for event A3 is not
SSS EPRE SCS
satisfied
SS/PBCH dBm/ Power levels are such that entry condition for
T1 -91 -79 -91
SSS EPRE SCS event A3 is satisfied for NR Cell 2
T2 -91 -91 -79
T3 -79 -91 -91
SSS EPRE SCS event A3 and event A5 are satisfied for NR Cell 1

SS/PBCH dBm/
T0 FFS FFS FFS Cell 1 and entry condition for event A3 is not
SSS EPRE SCS
satisfied
T1 FFS FFS FFS
T2 FFS FFS FFS
T3 FFS FFS FFS
SSS EPRE SCS event A3 and event A5 are satisfied for NR Cell 1
ETSI

U-S Message
message including MeasConfig and
ConditionalReconfiguration to set NR Cell 2
and NR Cell 4 as target candidate cells and
configure event A3 as trigger event in NR cell
1.
cell 1.
3 Check: Does the UE initiate a random access --> (PRACH Preamble) 1 F
procedure transmitting Preamble in NR Cell 2
or in NR cell 4 within 10s?
4 SS adjusts the cell-specific reference signal - - - -
5 Check: Does the UE initiate a random access --> (PRACH Preamble) 2 P
procedure by transmitting Preamble in NR Cell
2 within 10s?
6 The SS transmits Random Access Response. <-- Random Access Response - -
Cell 2.
and NR Cell 4 as target candidate cells and
configure event A5 as trigger event in NR cell
2.
cell 2.
4 within 10s?
Cell 4.
ConditionalReconfiguration for intra
-frequency event A3 and A5 in NR cell 4.
cell 4.
1 within 10s?
Cell 1.
ETSI

24 Check: Does the UE transmit --> NR RRC: 5 F
Cell 2 within 10s?
Table 8.1.4.4.1.3.3-1: RRCReconfiguration (Step 1, step 9 and step 16, Table 8.1.4.4.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition NR_MEAS and CHO
measConfig MeasConfig Table
8.1.4.4.1.3.3-2
conditionalReconfiguration-r16 ConditionalReconfigurati Table
on 8.1.4.4.1.3.3-6
}
}
}
}
}
}
}
ETSI

measObjectId 1
measObject CHOICE {
8.1.4.4.1.3.3-3
}
}
}
reportConfigId 1
condEventA3 8.1.4.4.1.3.3-4
}
}
reportConfigId 2
condEventA5 8.1.4.4.1.3.3-5
}
}
}
measIdToAddModList SEQUENCE (SIZE 1 entry Step 1, Step
(1..maxNrofMeasId)) OF MeasIdToAddMod { 9
measId 1
measObjectId 1
2 Step 9
}
}
measIdToAddModList SEQUENCE (SIZE 2 entries Step 16
measId 1
measObjectId 1
reportConfigId 1
}
measId 2
measObjectId 1
reportConfigId 2
}
}
}
ETSI

ssbFrequency ARFCN-ValueNR for The SSB of NR
SSB of NR Cell 1 cell 1, NR Cell 2
and NR cell 4
have the same
ARFCN value as
specified in TS
38.508-1 [4]
clause 6.2.3
}
Table 8.1.4.4.1.3.3-4: ReportConfigNR-condEventA3 (Table 8.1.4.4.1.3.3-2)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-142 with condition CHO AND EVENT_A3
reportType CHOICE {
condTriggerConfig SEQUENCE {
condEventId CHOICE {
condEventA3 SEQUENCE {
a3-Offset CHOICE {
rsrp 2 1 dB (2*0.5 dB) FR1
FFS FR2
}
}
}
}
}
}
reportType CHOICE {
rsrp 76 -80dBm FR1
FFS FR2
}
rsrp 70 -86dBm FR1
FFS FR2
}
}
}
}
}
}
ETSI
Table 8.1.4.4.1.3.3-6: ConditionalReconfiguration (Table 8.1.4.4.1.3.3-1)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25D

ConditionalReconfiguration-r16::= SEQUENCE {
condReconfigToRemoveList-r16 Not present
condReconfigToAddModList-r16 CondReconfigToAddMod Table Step 1, Step
List-r16 (Step 1 and step 8.1.4.4.1.3.3-7 9
9)
CondReconfigToAddMod Table Step 16
List-r16 (Step 16) 8.1.4.4.1.3.3-10
}
Table 8.1.4.4.1.3.3-7: CondReconfigToAddModList-r16 (Step 1 and step 9, Table 8.1.4.4.1.3.3-6)
Derivation Path: TS 38.508-1 [4] Table 4.6.3-25C

CondReconfigToAddModList-r16 ::= SEQUENCE 2 entries
(SIZE (1.. maxNrofCondCells-r16)) OF
CondReconfigToAddMod-r16 {
CondReconfigToAddMod-r16[1] ::= SEQUENCE { entry 1
condReconfigId-r16 1
condExecutionCond-r16::= SEQUENCE {
MeasId [1] 1
}
condRRCReconfig-r16 RRCReconfiguration-HO Table Step 1
with condition HO_NR 8.1.4.4.1.3.3-8
cell 2
RRCReconfiguration-HO Table Step 9
cell 1
}
MeasId [1] 1
}
condRRCReconfig-r16 RRCReconfiguration-HO Table
cell 4
}
}
Table 8.1.4.4.1.3.3-8: RRCReconfiguration-HO (Table 8.1.4.4.1.3.3-7)

masterCellGroup CellGroupConfig with Table HO_NR cell
condition PCI_NR cell 1 8.1.4.4.1.3.3-9 1
CellGroupConfig with Table HO_NR cell
CellGroupConfig with Table HO_NR cell
}
}
}
}
ETSI
8.1.4.4.1.3.3-9: CellGroupConfig (Table 8.1.4.4.1.3.3-8)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-19 with Condition PCell_change and CFRA
physCellId Physical Cell Identity of NR PCI_NR cell
Cell 1 1
Physical Cell Identity of NR PCI_NR Cell
Cell 2 2
Cell 4 4
}
}
}
}
Table 8.1.4.4.1.3.3-10: CondReconfigToAddModList-r16 (Step 16, Table 8.1.4.4.1.3.3-6)

MeasId [1] 1
MeasId [2] 2
}
cell 1
}
MeasId [1] 1
}
cell 2
}
}
8.1.4.4.2 Conditional handover / modify conditional handover configuration
(1)
RRCReconfiguration message including a ConditionalReconfiguration }
ensure that {
when { UE received another RRCReconfiguration message with adding a new entry in the
CondReconfigToAddModList before any CHO execution condition is satisfied }
then { UE add the new entry within the VarConditionalReconfig and apply the latest conditional
handover configurations}
}
ETSI
(2)
ensure that {
when { UE received another RRCReconfiguration message with modifying an existing entry in the
CondReconfigToAddModList before any CHO execution condition is satisfied }
then { UE replace the existing entry with the value received and apply the latest conditional
handover configurations }
}
(3)
ensure that {
when { UE received another RRCReconfiguration message with condConfigToRemoveList before any CHO
execution condition is satisfied }
then { UE removes the entry with the matching condConfigId included in the
condConfigToRemoveList and apply the latest conditional handover configurations }
}
9.2.3.4.2 and TS 38.331 clause 5.3.5.1, 5.3.5.13.2 and 5.3.5.13.3. Unless otherwise stated these are Rel-16
requirements.
[TS 38.300, clause 9.2.3.4.1]
candidate cell.
configuration.
[TS 38.300, clause 9.2.3.4.2]
ETSI

target gNB(s)
User Data User Data
2. CHO Decision
3. HANDOVER REQUEST
3. HANDOVER REQUEST
5. HANDOVER REQUEST
ACKNOWLEDGE

User Data
8c. HANDOVER CANCEL
Figure 9.2.3.2.1-1 step 9-12
ETSI
message.
[TS 38.331, clause 5.3.5.1]
UE Network
RRCReconfiguration
Figure 5.3.5.1-1: RRC reconfiguration, successful
UE Network
RRCReconfiguration
RRC connection re-establishment
Figure 5.3.5.1-2: RRC reconfiguration, failure
The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs, to perform
reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to
add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change configuration.
As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.
[TS 38.331, clause 5.3.5.13.2]
The UE shall:
ETSI
1> for each condReconfigId value included in the condReconfigToRemoveList that is part of the current UE
conditional reconfiguration in VarConditionalReconfig:
2> remove the entry with the matching condReconfigId from the VarConditionalReconfig;
NOTE: The UE does not consider the message as erroneous if the condReconfigToRemoveList includes any
condReconfigId value that is not part of the current UE configuration.
[TS 38.331, clause 5.3.5.13.3]
For each condReconfigId received in the condReconfigToAddModList IE the UE shall:
1> if an entry with the matching condReconfigId exists in the condReconfigToAddModList within the
VarConditionalReconfig:
2> if the entry in condReconfigToAddModList includes an condExecutionCond;
3> replace the entry with the value received for this condReconfigId;
2> if the entry in condReconfigToAddModList includes an condRRCReconfig;
2> replace the entry with the value received for this condReconfigId;
1> else:
2> add a new entry for this condReconfigId within the VarConditionalReconfig;
1> perform conditional reconfiguration evaluation as specified in 5.3.5.13.4;
System Simulator:
UE:
- None.
Preamble:
Tables 8.1.4.4.2.3.2-1 and 8.1.4.4.2.3.2-2 illustrate the downlink power levels to be applied for NR cells at various time
ETSI

SS/PBCH dBm/
T0 -82 -91 -91 Cell 1 and entry condition for event A3 is not
SSS EPRE SCS
satisfied
SS/PBCH dBm/ Power levels are such that entry condition for event
T1 -91 -79 -91
SSS EPRE SCS A3 is satisfied for NR Cell 2
T2 -91 -91 -79
T3 -79 -91 -79
SSS EPRE SCS A3 is satisfied for NR Cell 1 and NR Cell 4

SS/PBCH dBm/
T0 FFS FFS FFS Cell 1 and entry condition for event A3 is not
SSS EPRE SCS
satisfied
T1 FFS FFS FFS
T2 FFS FFS FFS
T3 FFS FFS FFS
SSS EPRE SCS A3 is satisfied for NR Cell 1 and NR Cell 4

U-S Message
ConditionalReconfiguration to set NR Cell 4 as
a target candidate cell.
Cell 1.
message including ConditionalReconfiguration
to add NR Cell 2 as another target candidate
cell.
Cell 1.
4 within 10s?
Cell 2 within 10s?
procedure in TS 38.508-1 [4] Table 4.9.1-1A
and NR Cell 4 as target candidate cells.
ETSI
Cell 2.
with condConfigToRemoveList to remove NR
Cell 4 from the target candidate cell list.
Cell 2.
15 Check: Does the UE initiate a random access --> (PRACH Preamble) 3 F
4 within 10s?
to replace NR Cell 2 with NR Cell 4 as the
target candidate cell.
4 within 10s?
Cell 4.
Table 8.1.4.4.2.3.3-1: RRCReconfiguration (Step 1, step 3, step 10, step 12 and step 16, Table
8.1.4.4.2.3.2-3)
measConfig Not present Step 3, Step
12, Step 16
MeasConfig Table Step 1, Step
8.1.4.4.2.3.3-2 10
on 8.1.4.4.2.3.3-6
}
}
}
}
}
}
}
ETSI

measObjectId 1
measObject CHOICE {
8.1.4.4.2.3.3-3
}
}
}
reportConfigId 1
condEventA3 8.1.4.4.2.3.3-4
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
}
}

SSB of NR Cell 1 Cell 1, NR Cell 2
and NR Cell 4
have the same
ARFCN value as
specified in TS
38.508-1 [4]
clause 6.2.3
}
ETSI
reportType CHOICE {
a3-Offset CHOICE {
rsrp 2 1 dB (2*0.5 dB) FR1
FFS FR2
}
}
}
}
}
}

ConditionalReconfiguration-r16 ::= SEQUENCE {
condReconfigToRemoveList-r16 Not present
condReconfigToRemoveList-r16 SEQUENCE (SIZE 1 entry Step 12
(1.. maxNrofCondCells-r16)) OF CondReconfigId-r16
{
condReconfigId-r16[1] 2 entry 1
}
condReconfigToAddModList-r16 CondReconfigToAddMod Table Step 1, Step
List-r16 (Step 1 and step 8.1.4.4.2.3.3-7 16
16)
List-r16 (Step 3) 8.1.4.4.2.3.3-10
List-r16 (Step 10) 8.1.4.4.2.3.3-11
}
Table 8.1.4.4.2.3.3-6: CondReconfigToAddModList-r16 (Step 1 and step 16, Table 8.1.4.4.2.3.3-6)

CondReconfigToAddModList-r16 ::= SEQUENCE 1 entry
MeasId [1] 1
}
condRRCReconfig-r16 RRCReconfiguration-HO Table Step 1, Step
with condition HO_NR 8.1.4.4.2.3.3-8 16
Cell 4
}
}
ETSI

masterCellGroup CellGroupConfig with Table HO_NR cell
CellGroupConfig with Table HO_NR Cell
condition PCI_NR Cell 2 8.1.4.4.2.3.3-9 2
}
}
}
}
physCellId Physical Cell Identity of NR PCI_NR Cell
Cell 1 1
Cell 2 2
Cell 4 4
}
}
}
}

CondReconfigToAddModList-r16 ::= SEQUENCE 1 entry
MeasId [1] 1
}
Cell 2
}
}
ETSI

MeasId [1] 1
}
Cell 1
}
MeasId [1] 1
}
Cell 4
}
}
8.1.4.4.3 Conditional handover / Failure
(1)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving a
ensure that {
when { UE detects conditional handover failure and finds a selectable cell which is the candidate
cell included in ConditionalReconfiguration before T311 expires }
then { UE applies the stored condRRCReconfig associated to the selected cell and perform
conditional handover to the selected cell }
}
(2)
with { UE in NR RRC_CONNECTED state and supporting conditional handover and receiving a
ensure that {
when { UE detects conditional handover failure and cannot find any selectable cell before T311
expires }
then { UE goes to RRC_IDLE and release the stored conditional handover configurations }
}
9.2.3.4.2 and TS 38.331 clause 5.3.7.3, 5.3.7.6 and 5.3.11. Unless otherwise stated these are Rel-16 requirements.
[TS 38.300, clause 9.2.3.4.1]
ETSI
candidate cell.
configuration.
[TS 38.300, clause 9.2.3.4.2]
ETSI

target gNB(s)
User Data User Data
2. CHO Decision
3. HANDOVER REQUEST
3. HANDOVER REQUEST
5. HANDOVER REQUEST
ACKNOWLEDGE

User Data
8c. HANDOVER CANCEL
Figure 9.2.3.2.1-1 step 9-12
ETSI
message.
[TS 38.331, clause 5.3.7.3]
Upon selecting a suitable NR cell, the UE shall:
1> ensure having valid and up to date essential system information as specified in clause 5.2.2.2;
1> stop timer T311;
1> if attemptCondReconfig is configured; and
1> if the selected cell is one of the candidate cells for which the reconfigurationWithSync is included in the
masterCellGroup in VarConditionalReconfig:
2> apply the stored condRRCReconfig associated to the selected cell and perform actions as specified in 5.3.5.3;
1> else:
2> if UE is configured with conditionalReconfiguration:
3> reset MAC;
3> release spCellConfig, if configured;
3> release the MCG SCell(s), if configured;
3> release delayBudgetReportingConfig, if configured and stop timer T342, if running;
3> release overheatingAssistanceConfig , if configured and stop timer T345, if running;
3> if MR-DC is configured:
4> perform MR-DC release, as specified in clause 5.3.5.10;
3> release idc-AssistanceConfig, if configured;
3> release btNameList, if configured;
3> release wlanNameList, if configured;
ETSI
3> release sensorNameList, if configured;
3> release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG,
if running;
3> release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the
MCG, if running;
3> release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the
MCG, if running;
3> release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated
with the MCG, if running;
3> release minSchedulingOffsetPreferenceConfig for the MCG, if configured and stop timer T346e
associated with the MCG, if running;
3> release releasePreferenceConfig, if configured and stop timer T346f, if running;
3> release onDemandSIB-Request if configured, and stop timer T350, if running;
3> suspend all RBs, except SRB0;
2> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig:
3> for the associated reportConfigId:
4> remove the entry with the matching reportConfigId from the reportConfigList within the
VarMeasConfig;
3> if the associated measObjectId is only associated to a reportConfig with reportType set to
condTriggerConfig:
4> remove the entry with the matching measObjectId from the measObjectList within the
VarMeasConfig;
3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
2> start timer T301;
2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for
the parameters for which values are provided in SIB1;
2> apply the default MAC Cell Group configuration as specified in 9.2.2;
2> initiate transmission of the RRCReestablishmentRequest message in accordance with 5.3.7.4;
NOTE: This procedure applies also if the UE returns to the source PCell.
Upon selecting an inter-RAT cell, the UE shall:
failure'.
[TS 38.331, clause 5.3.7.6]
Upon T311 expiry, the UE shall:
1> if the procedure was initiated due to radio link failure or handover failure:
2> set the noSuitableCellFound in the VarRLF-Report to true;
ETSI
failure'.
[TS 38.331, clause 5.3.11]
The UE shall:
1> reset MAC;
1> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig:
2> for the associated reportConfigId:
3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
2> if the associated measObjectId is only associated to a reportConfig with reportType set to
condTriggerConfig:
3> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
2> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
1> discard the KgNB key, the S-KgNB key, the S-KeNB key, the KRRCenc key, the KRRCint key, the KUPint key and the
KUPenc key, if any;
1> release all radio resources, including release of the RLC entity, the BAP entity, the MAC configuration and the
associated PDCP entity and SDAP for all established RBs;
1> except if going to RRC_IDLE was triggered by inter-RAT cell reselection while the UE is in RRC_INACTIVE
or RRC_IDLE or when selecting an inter-RAT cell while T311 was running or when selecting an E-UTRA cell
for EPS fallback for IMS voice as specified in 5.4.3.5:
2> enter RRC_IDLE and perform cell selection as specified in TS 38.304 [20];
System Simulator:
UE:
- None.
Preamble:
ETSI
Tables 8.1.4.4.3.3.2-1 and 8.1.4.4.3.3.2-2 illustrate the downlink power levels to be applied for NR cells at various time

SS/PBCH dBm/ Power levels are such that UE registered on NR
T0 -85 -113 -113
SSS EPRE SCS Cell 1
T1 -91 -79 -91
SS/PBCH dBm/
T2 -113 -113 -79 The power level is such that only SrxlevNR Cell 4 > 0
SSS EPRE SCS
T3 -79 -91 -91
SS/PBCH dBm/
T4 -113 -113 -113 Power levels are such that all Srxlev NR Cell < 0
SSS EPRE SCS
SS/PBCH dBm/
T5 -113 -79 -113 The power level is such that only SrxlevNR Cell 2 > 0
SSS EPRE SCS

SS/PBCH dBm/ Power levels are such that UE registered on NR
T0 FFS FFS FFS
SSS EPRE SCS Cell 1
T1 FFS FFS FFS
SS/PBCH dBm/
T2 FFS FFS FFS The power level is such that only SrxlevNR Cell 4 > 0
SSS EPRE SCS
T3 FFS FFS FFS
SS/PBCH dBm/
T4 FFS FFS FFS Power levels are such that all Srxlev NR Cell < 0
SSS EPRE SCS
SS/PBCH dBm/
T5 FFS FFS FFS The power level is such that only SrxlevNR Cell 2 > 0
SSS EPRE SCS

U-S Message
ConditionalReconfiguration.
Cell 1.
4 The UE attempts to perform the intra - - - -
4 within 10s?
ETSI

Cell 4.
ConditionalReconfiguration.
Cell 4.
14 The UE attempts to perform the inter - - - -
15 Wait 5s to ensure that T304 and T311 expire.
(Note 1)
2 within 10s?
18 Check: Does the generic mobility registration - - 2 P
updating procedure described in TS 38.508-1
[4] Table 4.9.5.2.2-1 is performed on NR Cell
2.
Note 1: The wait time is selected to cover T304 (1000ms) + T311 (1000ms) to ensure that UE goes to RRC_IDLE.
Table 8.1.4.4.3.3.3-1: SIB1 for NR Cell 2 (preamble and all steps, Table 8.1.4.4.3.3.2-3)

SIB1 ::= SEQUENCE {
PLMN-IdentityInfoList SEQUENCE {
trackingAreaCode 2
}
}
}
ETSI
Table 8.1.4.4.3.3.3-2: RRCReconfiguration (Step1 and step 11, Table 8.1.4.4.3.3.2-3)
measConfig MeasConfig Table
8.1.4.4.3.3.3-3
on 8.1.4.4.3.3.3-4
}
}
}
}
}
}
}

measObjectId 1
measObject CHOICE {
8.1.4.4.3.3.3-4
}
}
}
reportConfigId 1
condEventA3 8.1.4.4.3.3.3-5
}
}
}
measId 1
measObjectId 1
reportConfigId 1
}
}
}
ETSI

SSB of NR Cell 1 Cell 1, NR Cell 2
and NR Cell 4
have the same
ARFCN value as
specified in TS
38.508-1 [4]
clause 6.2.3
}
reportType CHOICE {
a3-Offset CHOICE {
rsrp 2 1 dB (2*0.5 dB) FR1
FFS FR2
}
}
}
}
}
}

ConditionalReconfiguration-r16::= SEQUENCE {
condReconfigToAddModList-r16 CondReconfigToAddMod Table
List-r16 8.1.4.4.3.3.3-7
}
ETSI
Table 8.1.4.4.3.3.3-7: CondReconfigToAddModList-r16 (Table 8.1.4.4.3.3.3-6)

MeasId [1] 1
}
Cell 2
Cell 1
}
MeasId [1] 1
}
Cell 4
Cell 2
}
}

masterCellGroup CellGroupConfig with Table HO_NR Cell
}
}
}
}
ETSI
physCellId Physical Cell Identity of NR PCI_NR Cell
Cell 1 1
Cell 2 2
Cell 4 4
}
}
}
}
8.1.5 RRC others
8.1.5.1 UE capability transfer
8.1.5.1.1 UE capability transfer / Success
(1)
ensure that {
when { UE receives an UECapabilityEnquiry message }
then { UE transmits an UECapabilityInformation message including UE radio access capability
information corresponding to the ue-CapabilityRequest variable }
}
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clauses 5.6.1.3,
5.6.1.4, 5.7.7.2 and 5.7.7.3.
[TS 38.331, clause 5.6.1.3]
The UE shall set the contents of UECapabilityInformation message as follows:
1> if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to nr:
2> include in the ue-CapabilityRAT-ContainerList a UE-CapabilityRAT-Container of the type UE-NR-

Capability and with the rat-Type set to nr;
2> include the supportedBandCombinationList, featureSets and featureSetCombinations as specified in clause

5.6.1.4;
1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends.
[TS 38.331, clause 5.6.1.4]
The UE invokes the procedures in this clause if the NR or E-UTRA network requests UE capabilities for nr, eutra-nr or
eutra. This procedure is invoked once per requested rat-Type (see clause 5.6.1.3 for capability enquiry by the NR
network; see TS 36.331 [10], clause 5.6.3.3 for capability enquiry by the E-UTRA network). The UE shall ensure that
the feature set IDs are consistent across feature sets, feature set combinations and band combinations in all three UE
ETSI
capability containers that the network queries with the same fields with the same values, i.e. UE-
CapabilityRequestFilterNR and fields in UECapabilityEnquiry message (i.e. requestedFreqBandsNR-MRDC,
requestedCapabilityNR and eutra-nr-only flag) as defined in TS 36.331, where applicable.
NOTE 1: Capability enquiry without frequencyBandListFilter is not supported.
[TS 38.331, clause 5.7.7.2]
A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following
conditions are met:
1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and
1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323
[5];
Upon initiating the procedure, the UE shall:
1> initiate transmission of the ULDedicatedMessageSegment message as specified in 5.7.7.3;
[TS 38.331, clause 5.7.7.3]
The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS
38.323 [5]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment
messages as follows:
1> F or each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the
segmentNumber for each subsequent RRC message segment;
1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the
segmentNumber;
1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:
2> set the rrc-MessageSegmentType to lastSegment;
1> else:
2> set the rrc-MessageSegmentType to notLastSegment;
1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower
layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.
System Simulator:
- NR Cell 1
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A on NR Cell 1.
ETSI

U-S Message
1 The SS transmits a UECapabilityEnquiry message <-- UECapabilityEnquiry - -
including nr and rrc-segAllowed-r16 set to enabled.
- EXCEPTION: The "lower case letter" identifies a - - - -
step sequence that takes place depending on the
size of UE capability message.
IF pc_NR_UL_Segmentation and UE’s
encoded UECapabilityInformation message >=
Max PDCP SDU size then steps 2a1 and 2a2 will
be performed else step 2b1 will be performed
- EXCEPTION: Step 2a1 is repeated a maximum of - - - -
16 times or till rrc-MessageSegmentType-16 IE
within the UlDedicatedMessageSegment message
indicates rrc-MessageSegmentType-r16 =
lastSegment.
2a1 The UE sends segments of --> ULDedicatedMessageSegm - -
UECapabilityInformation message contained within ent
the rrc-MessageSegmentContainer-r16 IE of the
ULDedicatedMessageSegment message?
2a2 Check: Is the received UE radio access capability - - 1 P
information as per the ue-CapabilityRequest
variable?
2b1 Check: Does the UE transmit a --> UECapabilityInformation 1 P
UECapabilityInformation message including UE
radio access capability information as per the ue-
CapabilityRequest variable?
Table 8.1.5.1.1.3.3-1: UECapabilityEnquiry (step 1, Table 8.1.5.1.1.3.2-1)

UECapabilityEnquiry ::= SEQUENCE {
ueCapabilityEnquiry SEQUENCE {
ue-CapabilityRAT-RequestList SEQUENCE (SIZE -
(1.. maxRAT-CapabilityContainers)) OF
CapabilityRAT-Request {
UE-CapabilityRAT-Request[1] SEQUENCE { entry 1
rat-Type nr
}
}
ue-CapabilityEnquiryExt OCTET STRING
Containing
UECapabilityEnquiry-
v1560-IEs
}
criticalExtensionsFuture
}
}
ETSI
Table 8.1.5.1.1.3.3-2: UECapabilityInformation (steps2a2 and 2b1, Table 8.1.5.1.1.3.2-1)

UECapabilityInformation ::= SEQUENCE {
ueCapabilityInformation SEQUENCE {
ue-CapabilityRAT-ContainerList SEQUENCE
(SIZE (0..maxRAT-CapabilityContainers)) OF
CapabilityRAT-Request {
UE-CapabilityRAT-Request[1] SEQUENCE { entry 1
rat-Type nr
ueCapabilityRAT-Container UE-NR-Capability Encoded as per
TS 38.331 [12]
clause 5.6.1
}
}
nonCriticalExtension Not checked
}
criticalExtensionsFuture Not checked
}
}
ETSI
Table 8.1.5.1.1.3.3-3: UE-NR-Capability (Table 8.1.5.1.1.3.3-2)

UE-NR-Capability ::= SEQUENCE {
accessStratumRelease Checked "rel-15" or higher
pdcp-Parameters SEQUENCE {
supportedROHC-Profiles SEQUENCE {
profile0x0000 Not checked
}
maxNumberROHC-ContextSessions Not checked
uplinkOnlyROHC-Profiles Not checked
continueROHC-Context Not checked
outOfOrderDelivery Checked pc_outOfOrd
erDelivery
shortSN Checked pc_shortSN
pdcp-DuplicationSRB Not checked
pdcp-DuplicationMCG-OrSCG-DRB Not checked
}
rlc-Parameters SEQUENCE {
am-WithShortSN Checked pc_am_With
ShortSN
um-WithShortSN Checked pc_um_With
ShortSN
um-WithLongSN Checked pc_um_WIth
LongSN
}
mac-Parameters SEQUENCE {
mac-ParametersCommon SEQUENCE {
lcp-Restriction Not checked
dummy Not checked
lch-ToSCellRestriction Not checked
recommendedBitRate Not checked
recommendedBitRateQuery Not checked
}
mac-ParametersXDD-Diff SEQUENCE {
skipUplinkTxDynamic Checked (NOTE 4) pc_skipUplin
kTxDynamic
logicalChannelSR-DelayTimer Checked (NOTE 5) pc_logicalCh
annelSR_De
layTimer
longDRX-Cycle Checked (NOTE 6) pc_longDRX
_Cycle
shortDRX-Cycle Checked (NOTE 7) pc_shortDR
X_Cycle
multipleSR-Configurations Not checked
multipleConfiguredGrants Not checked
}
}
phy-Parameters SEQUENCE {
phy-ParametersCommon SEQUENCE {
csi-RS-CFRA-ForHO Checked pc_csi_RS_
CFRA_ForH
O
dynamicPRB-BundlingDL Not checked
sp-CSI-ReportPUCCH Not checked
sp-CSI-ReportPUSCH Not checked
ETSI
nzp-CSI-RS-IntefMgmt Not checked

type2-SP-CSI-Feedback-LongPUCCH Not checked
precoderGranularityCORESET Not checked
dynamicHARQ-ACK-Codebook supported
semiStaticHARQ-ACK-Codebook Not checked
spatialBundlingHARQ-ACK Not checked
dynamicBetaOffsetInd-HARQ-ACK-CSI Not checked
pucch-Repetition-F1-3-4 Not checked
ra-Type0-PUSCH Checked pc_ra_Type0
_PUSCH
dynamicSwitchRA-Type0-1-PDSCH Not checked
dynamicSwitchRA-Type0-1-PUSCH Not checked
pdsch-MappingTypeA supported pc_pdsch_M
appingType
A
pdsch-MappingTypeB Checked pc_pdsch_M
appingType
B
interleavingVRB-ToPRB-PDSCH Checked pc_interleavi
ngVRB_ToP
RB_PDSCH
interSlotFreqHopping-PUSCH Not checked
type1-PUSCH-RepetitionMultiSlots Not checked
type2-PUSCH-RepetitionMultiSlots Not checked
pusch-RepetitionMultiSlots Checked pc_pusch_R
epetitionMult
iSlots
pdsch-RepetitionMultiSlots Checked pc_pdsch_R
epetitionMult
iSlots
downlinkSPS Checked pc_downlink
SPS
configuredUL-GrantType1 Checked pc_configure
dUL_GrantT
ype1
configuredUL-GrantType2 Checked pc_configure
dUL_GrantT
ype2
pre-EmptIndication-DL Not checked
cbg-TransIndication-DL Not checked
cbg-TransIndication-UL Not checked
cbg-FlushIndication-DL Not checked
dynamicHARQ-ACK-CodeB-CBG-Retx-DL Not checked
rateMatchingResrcSetSemi-Static Not checked
rateMatchingResrcSetDynamic Not checked
bwp-SwitchingDelay Not checked
dummy Not checked
maxNumberSearchSpaces n10
rateMatchingCtrlResrsSetDynamic Not checked
maxLayersMIMO-Indication Not checked
}
phy-ParametersXDD-Diff SEQUENCE {
dynamicSFI Not checked
twoPUCCH-F0-2-ConsecSymbols Not checked
twoDifferentTPC-Loop-PUSCH Not checked
twoDifferentTPC-Loop-PUCCH Not checked
dl-SchedulingOffset-PDSCH-TypeA Not checked
dl-SchedulingOffset-PDSCH-TypeB Not checked
ul-SchedulingOffset Not checked
}
phy-ParametersFRX-Diff SEQUENCE {
dummy1 Not checked
twoFL-DMRS Not checked
dummy2 Not checked
dummy3 Not checked
ETSI
supportedDMRS-TypeDL Not checked

supportedDMRS-TypeUL Not checked
semiOpenLoopCSI Not checked
csi-ReportWithoutPMI Not checked
csi-ReportWithoutCQI Not checked
onePortsPTRS Not checked
pucch-F2-WithFH supported
pucch-F3-WithFH supported
pucch-F4-WithFH Not checked
freqHoppingPUCCH-F0-2 Not checked
freqHoppingPUCCH-F1-3-4 Not checked
mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot Not checked
uci-CodeBlockSegmentation Not checked
onePUCCH-LongAndShortFormat Not checked
twoPUCCH-AnyOthersInSlot Not checked
intraSlotFreqHopping-PUSCH Not checked
pusch-LBRM Not checked
pdcch-BlindDetectionCA Not checked
tpc-PUSCH-RNTI Not checked
tpc-PUCCH-RNTI Not checked
tpc-SRS-RNTI Not checked
absoluteTPC-Command Not checked
pusch-HalfPi-BPSK Not checked
pucch-F3-4-HalfPi-BPSK Not checked
almostContiguousCP-OFDM-UL Not checked
sp-CSI-RS Not checked
sp-CSI-IM Not checked
tdd-MultiDL-UL-SwitchPerSlot Not checked
multipleCORESET Not checked
csi-RS-IM-ReceptionForFeedback Not checked CSI-RS-IM-
ReceptionForFee
dback
csi-RS-ProcFrameworkForSRS Not checked CSI-RS-
ProcFrameworkFo
rSRS
csi-ReportFramework Not checked CSI-
ReportFramework
mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot
SEQUENCE {
sameSymbol Not checked
diffSymbol Not checked
}
mux-SR-HARQ-ACK-PUCCH Not checked
mux-MultipleGroupCtrlCH-Overlap Not checked
dl-64QAM-MCS-TableAlt Not checked
ul-64QAM-MCS-TableAlt Not checked
cqi-TableAlt Not checked
oneFL-DMRS-TwoAdditionalDMRS-UL Not checked
twoFL-DMRS-TwoAdditionalDMRS-UL Not checked
oneFL-DMRS-ThreeAdditionalDMRS-UL Not checked
}
phy-ParametersFR1 SEQUENCE {
pdcchMonitoringSingleOccasion Not checked
scs-60kHz Not checked
pdsch-256QAM-FR1 Checked pc_pdsch_2
56QAM_FR1
pdsch-RE-MappingFR1-PerSymbol Not checked
pdsch-RE-MappingFR1-PerSlot Not checked
}
phy-ParametersFR2 SEQUENCE {
ETSI
dummy Not checked

pdsch-RE-MappingFR2-PerSymbol Not checked
pCell-FR2 Not checked
pdsch-RE-MappingFR2-PerSlot Not checked
}
}
rf-Parameters SEQUENCE {
supportedBandListNR SEQUENCE (SIZE
(1..maxBands)) OF BandNR {
BandNR[i] SEQUENCE {
bandNR Checked Checked for pc_nrBandx
'maxBands' ('x' being the
entries of band
FreqBandIndicator number/type
NR[i] related PICS
listed in TS
38.508-2)
modifiedMPR-Behaviour Not checked
mimo-ParametersPerBand Not checked MIMO-
ParametersPerBa
nd[i]
extendedCP Not checked
multipleTCI supported
bwp-WithoutRestriction Not checked
bwp-SameNumerology Not checked
bwp-DiffNumerology Not checked
crossCarrierScheduling-SameSCS Not checked
pdsch-256QAM-FR2 Checked pc_pdsch_2
56QAM_FR2
pusch-256QAM Checked pc_pusch_2
56QAM_FR1
ue-PowerClass Not checked
rateMatchingLTE-CRS Not checked
channelBWs-DL-v1530 CHOICE {
fr1 SEQUENCE {
}
fr2 SEQUENCE {
}
}
}
channelBWs-UL-v1530[i] CHOICE {
fr1 SEQUENCE {
}
fr2 SEQUENCE {
}
maxUplinkDutyCycle-PC2-FR1 Not checked
pucch-SpatialRelInfoMAC-CE Not checked
powerBoosting-pi2BPSK Not checked
}
}
supportedBandCombinationList SEQUENCE (SIZE
(1..maxBandComb)) OF BandCombination {
BandCombinationSEQUENCE {
bandList SEQUENCE (SIZE
(1..maxSimultaneousBands)) OF BandParameters {
BandParameters CHOICE
ETSI
eutra SEQUENCE {
bandEUTRA Not checked FreqBandIndicator
EUTRA
ca-BandwidthClassDL-EUTRA Not checked CA-
BandwidthClassE
UTRA
ca-BandwidthClassUL-EUTRA Not checked CA-
BandwidthClassE
UTRA
}
nr SEQUENCE {
bandNR Not checked FreqBandIndicator
NR
ca-BandwidthClassDL-NR Not checked CA-
BandwidthClassN
R
ca-BandwidthClassUL-NR Not checked CA-
BandwidthClassN
R
}
}
}
}
featureSetCombination Not checked FeatureSetCombi
nationId
ca-ParametersEUTRA Not checked CA-
ParametersEUTR
A
ca-ParametersNR Not checked CA-
ParametersNR
mrdc-Parameters Not checked MRDC-
Parameters
supportedBandwidthCombinationSet Not checked
powerClass-v1530 Not checked
}
appliedFreqBandListFilter Not checked FreqBandList
supportedBandCombinationList-v1540
SEQUENCE (SIZE (1..maxBandComb)) OF
BandCombination-v1540 {
BandCombination-v1540 SEQUENCE {
bandList-v1540 SEQUENCE (SIZE Not checked BandParameters-
(1..maxSimultaneousBands)) OF BandParameters- v1540
v1540 {
BandParameters-v1540 SEQUENCE {
srs-CarrierSwitch CHOICE {
nr SEQUENCE [ NR bands
srs-SwitchingTimesListNR SEQUENCE Not checked
(SIZE (1..maxSimultaneousBands)) OF SRS-
SwitchingTimeNR
}
eutra SEQUENCE { EUTRA bands
srs-SwitchingTimesListEUTRA SEQUENCE Not checked
(SIZE (1..maxSimultaneousBands)) OF SRS-
SwitchingTimeEUTRA
}
}
srs-TxSwitch-v1540 SEQUENCE {
supportedSRS-TxPortSwitch Not checked
txSwitchImpactToRx Not checked
txSwitchWithAnotherBand Not checked
}
}
}
ca-ParametersNR-v1540[i] Not checked CA-
ParametersNR-
v1540
ETSI
}
}
srs-SwitchingTimeRequested Not checked
}
measAndMobParameters SEQUENCE {
measAndMobParametersCommon SEQUENCE {
supportedGapPattern Not checked
ssb-RLM supported
ssb-AndCSI-RS-RLM Not checked
eventB-MeasAndReport Not checked
handoverFDD-TDD Not checked
eutra-CGI-Reporting Not checked
nr-CGI-Reporting Not checked
independentGapConfig Checked pc_independ
entGapConfi
g
periodicEUTRA-MeasAndReport Not checked
handoverFR1-FR2 Not checked
maxNumberCSI-RS-RRM-RS-SINR Not checked
}
measAndMobParametersXDD-Diff SEQUENCE {
intraAndInterF-MeasAndReport Checked (NOTE 1) pc_intraAndI
nterF-
MeasAndRe
port
eventA-MeasAndReport Checked (NOTE 2) pc_eventA_
MeasAndRe
port
handoverInterF Not checked
handoverLTE Not checked
handover-eLTE Not checked
}
measAndMobParametersFRX-Diff SEQUENCE {
ss-SINR-Meas Not checked
csi-RSRP-AndRSRQ-MeasWithSSB Checked (NOTE 3) pc_csi-
RSRP-
AndRSRQ-
MeasWithSS
B
csi-RSRP-AndRSRQ-MeasWithoutSSB Not checked
csi-SINR-Meas Not checked
csi-RS-RLM Not checked
maxNumberResource-CSI-RS-RLM Not checked
}
}
fdd-Add-UE-NR-Capabilities SEQUENCE {
}
kTxDynamic
annelSR_De
layTimer
_Cycle
ETSI

X_Cycle
}
nterF-
MeasAndRe
port
MeasAndRe
port
}
}
tdd-Add-UE-NR-Capabilities SEQUENCE {
}
kTxDynamic
annelSR_De
layTimer
_Cycle
X_Cycle
}
nterF-
MeasAndRe
port
MeasAndRe
port
}
fr1-Add-UE-NR-Capabilities SEQUENCE {
dummy1 Not checked
dummy2 Not checked
dummy3 Not checked
ETSI

csi-RS-IM-ReceptionForFeedback Not checked
csi-RS-ProcFrameworkForSRS Not checked
csi-ReportFramework Not checked
SEQUENCE {
}
}
RSRP-
AndRSRQ-
MeasWithSS
B
}
}
fr2-Add-UE-NR-Capabilities SEQUENCE {
phy-ParametersFRX-Diff SEQUENCE { Not checked
dummy1 Not checked
ETSI

dummy2 Not checked
dummy3 Not checked
csi-RS-IM-ReceptionForFeedback Not checked
csi-RS-ProcFrameworkForSRS Not checked
csi-ReportFramework Not checked
SEQUENCE {
}
}
RSRP-
AndRSRQ-
MeasWithSS
B
ETSI

}
}
featureSets SEQUENCE {
featureSetsDownlink SEQUENCE (SIZE
(1..maxDownlinkFeatureSets)) OF
FeatureSetDownlink {
FeatureSetDownlink SEQUENCE { Not checked
featureSetListPerDownlinkCC Not checked
intraBandFreqSeparationDL Not checked
scalingFactor Not checked
crossCarrierScheduling-OtherSCS Not checked
scellWithoutSSB Not checked
csi-RS-MeasSCellWithoutSSB Not checked
dummy1 Not checked
type1-3-CSS Not checked
pdcch-MonitoringAnyOccasions Not checked
dummy2 Not checked
ue-SpecificUL-DL-Assignment Not checked
searchSpaceSharingCA-DL Not checked
timeDurationForQCL SEQUENCE {
}
pdsch-ProcessingType1-DifferentTB-PerSlot
SEQUENCE {
}
dummy3 Not checked
dummy4 Not checked
dummy5 Not checked
dummy6 Not checked
dummy7 Not checked
}
}
featureSetsDownlinkPerCC SEQUENCE (SIZE
(1..maxPerCC-FeatureSets)) OF
FeatureSetDownlinkPerCC {
FeatureSetDownlinkPerCCSEQUENCE {
supportedSubcarreirSpacingDL Not checked SubcarrierSpacing
supportedBandwidthDL Not checked SupportedBandwi
dth
channelBW-90mhz Not checked
maxNumberMIMO-LayersPDSCH Not checked MIMO-LayersDL
supportedModulationOrderDL Not checked ModulationOrder
}
}
featureSetsUplink SEQUENCE (SIZE
(1..maxUplinkFeatureSets)) OF FeatureSetUplink {
FeatureSetUplink SEQUENCE {
featureSetListPerUplinkCC Not checked
scalingFactor Not checked
crossCarrierScheduling-OtherSCS Not checked
intraBandFreqSeparationUL Not checked
searchSpaceSharingCA-UL Not checked
dummy1 Not checked
supportedSRS-Resources Not checked SRS-Resources
twoPUCCH-Group Not checked
dynamicSwitchSUL Not checked
simultaneousTxSUL-NonSUL Not checked
pusch-ProcessingType1-DifferentTB-PerSlot
ETSI
SEQUENCE {
}
dummy2 Not checked
}
}
featureSetsUplinkPerCC SEQUENCE (SIZE
FeatureSetUplinkPerCC {
FeatureSetUplinkPerCCSEQUENCE {
supportedSubcarrierSpacingUL Not checked SubcarrierSpacing
supportedBandwidthUL Not checked SupportedBandwi
dth
channelBW-90mHz Not checked
mimo-CB-PUSCH SEQUENCE {
maxNumberMIMO-LayersCB-PUSCH Not checked
maxNumberSRS-ResourcePerSet Not checked
}
maxNumberMIMO-LayersNonCB-PUSCH Not checked
supportedModulationOrderUL Not checked ModulationOrder
}
}
featureSetsDownlink-v1540 SEQUENCE (SIZE
(1..maxDownlinkFeatureSets)) OF
FeatureSetDownlink-v1540 {
FeatureSetDownlink-v1540 SEQUENCE {
oneFL-DMRS-TwoAdditionalDMRS-DL Not checked
additionalDMRS-DL-Alt Not checked
twoFL-DMRS-TwoAdditionalDMRS-DL Not checked
oneFL-DMRS-ThreeAdditionalDMRS-DL Not checked
pdcch-MonitoringAnyOccasionsWithSpanGap
SEQUENCE {
}
pdsch-SeparationWithGap Not checked
pdsch-ProcessingType2 SEQUENCE {
}
pdsch-ProcessingType2-Limited SEQUENCE {
differentTB-PerSlot-SCS-30kHz Not checked
}
dl-MCS-TableAlt-DynamicIndication Not checked
}
}
featureSetsUplink-v1540 SEQUENCE (SIZE
(1..maxUplinkFeatureSets)) OF FeatureSetUplink-
v1540 {
FeatureSetUplink-v1540 SEQUENCE {
zeroSlotOffsetAperiodicSRS Not checked
pa-PhaseDiscontinuityImpacts Not checked
pusch-SeparationWithGap Not checked
pusch-ProcessingType2 SEQUENCE {
}
ul-MCS-TableAlt-DynamicIndication Not checked
}
ETSI
}
featureSetsUplinkPerCC-v1540 SEQUENCE (SIZE
FeatureSetUplinkPerCC-v1540 {
FeatureSetUplinkPerCC-v1540 SEQUENCE {
mimo-NonCB-PUSCH SEQUENCE {
maxNumberSRS-ResourcePerSet Not checked
maxNumberSimultaneousSRS-ResourceTx Not checked
}
}
}
}
featureSetCombinations SEQUENCE (SIZE
(1..maxFeatureSetCombinations)) OF
FeatureSetCombination {
FeatureSetCombination SEQUENCE (SIZE
(1..maxSimultaneousBands)) OF
FeatureSetsPerBand {
FeatureSetsPerBand SEQUENCE (SIZE
(1..maxFeatureSetsPerBand)) OF FeatureSet {
FeatureSetCHOICE {
eutra SEQUENCE {
downlinkSetEUTRA Not checked FeatureSetEUTR
A-DownlinkId
uplinkSetEUTRA Not checked FeatureSetEUTR
A-UplinkId
}
nr SEQUENCE {
downlinkSetNR Not checked FeatureSetDownli
nkId
uplinkSetNR Not checked FeatureSetUpinkI
d
}
}
}
}
}
fdd-Add-UE-NR-Capabilities-v1530 SEQUENCE {
eutra-ParametersXDD-Diff SEQUENCE {
rsrqMeasWidebandEUTRA Not checked
}
}
tdd-Add-UE-NR-Capabilities-v1530 SEQUENCE {
}
}
dummy Not checked
interRAT-Parameters SEQUENCE {
eutra SEQUENCE {
supportedBandListEUTRA SEQUENCE (SIZE
(1..maxBandsEUTRA)) OF FreqBandIndicatorEUTRA Not checked
eutra-ParametersCommon SEQUENCE {
mfbi-EUTRA Not checked
modifiedMRP-BehaviorEUTRA Not checked
multiNS-Pmax-EUTRA Not checked
rs-SINR-MeasEUTRA Not checked
ne-DC Not checked
nr-HO-ToEN-DC-r16 Checked pc_interRAT
_NR_ToEND
C
}
ETSI
}
}
}
inactiveState Checked pc_inactiveS
tate
delayBudgetReporting Not checked
nonCriticalExtension SEQUENCE { Not checked
sdap-Parameters SEQUENCE {
as-ReflectiveQoS Checked pc_as_Refle
ctiveQoS
}
overheatingInd Not checked
ims-Parameters SEQUENCE {
ims-ParametersCommon SEQUENCE {
voiceOverEUTRA-5GC Not checked
}
ims-ParametersFRX-Diff SEQUENCE {
voiceOverNR Not checked
}
}
fr1-Add-UE-NR-Capabilities-v1540 SEQUENCE {
}
}
fr2-Add-UE-NR-Capabilities-v1540 SEQUENCE {
}
}
fr1-fr2-Add-UE-NR-Capabilities SEQUENCE {
dummy1 Not checked
dummy2 Not checked
dummy3 Not checked
ETSI

csi-RS-IM-ReceptionForFeedback Not checked CSI-RS-IM-
ReceptionForFee
dback
csi-RS-ProcFrameworkForSRS Not checked CSI-RS-
ProcFrameworkFo
rSRS
csi-ReportFramework Not checked CSI-
ReportFramework
SEQUENCE {
}
}
RSRP-
AndRSRQ-
MeasWithSS
B
}
}
nonCriticalExtension SEQUENCE {} Not checked
}
}
Note 1: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and intraAndInterF-
MeasAndReport is supported in both modes, then support of intraAndInterF-MeasAndReport will be signaled
in measAndMobParameters/measAndMobParametersXDD-Diff.
If the UE is dual mode (FDD + TDD) and intraAndInterF-MeasAndReport is only supported in one mode, then
support of intraAndInterF-MeasAndReport will be signaled in one of fdd-Add-UE-NR-
Capabilities/measAndMobParametersXDD-Diff or tdd-Add-UE-NR-
Capabilities/measAndMobParametersXDD-Diff as appropriate.)
Note 2: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and eventA-MeasAndReport
is supported in both modes, then support of eventA-MeasAndReport will be signaled in
measAndMobParameters/measAndMobParametersXDD-Diff.
If the UE is dual mode (FDD + TDD) and eventA-MeasAndReport is only supported in one mode, then
support of eventA-MeasAndReport will be signaled in one of fdd-Add-UE-NR-
Capabilities/measAndMobParametersXDD-Diff or tdd-Add-UE-NR-
Capabilities/measAndMobParametersXDD-Diff as appropriate.
Note 3: If the UE supports single frequency range (FR1 or FR2), or the UE supports both frequency ranges (FR1 and
FR2) and csi-RSRP-AndRSRQ-MeasWithSSB is supported in both frequency ranges, then support of csi-
RSRP-AndRSRQ-MeasWithSSB will be signaled in measAndMobParameters/MeasAndMobParametersFRX-
Diff.
ETSI
If the UE supports both frequency ranges (FR1 + FR2) and csi-RSRP-AndRSRQ-MeasWithSSB is only
supported in one frequency range, then support of csi-RSRP-AndRSRQ-MeasWithSSB will be signaled in
one of fr1-Add-UE-NR-Capabilities/measAndMobParametersFRX-Diff or fr2-Add-UE-NR-
Capabilities/measAndMobParametersFRX-Diff as appropriate.)
Note 4: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and skipUplinkTxDynamic is
supported in both modes, then support of skipUplinkTxDynamic will be signaled in mac-Parameters/mac-
ParametersXDD-Diff.
If the UE is dual mode (FDD + TDD) and skipUplinkTxDynamic is only supported in one mode, then
skipUplinkTxDynamic will be signaled in one of fdd-Add-UE-NR-Capabilities/mac-ParametersXDD-Diff or tdd-
Add-UE-NR-Capabilities/mac-ParametersXDD-Diff as appropriate.
Note 5: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and logicalChannelSR-
DelayTimer is supported in both modes, then support of logicalChannelSR-DelayTimer will be signaled in
mac-Parameters/mac-ParametersXDD-Diff.
If the UE is dual mode (FDD + TDD) and logicalChannelSR-DelayTimer is only supported in one mode, then
support of logicalChannelSR-DelayTimer will be signaled in one of fdd-Add-UE-NR-Capabilities/mac-
ParametersXDD-Diff or tdd-Add-UE-NR-Capabilities/mac-ParametersXDD-Diff as appropriate.
Note 6: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and pc_longDRX_Cycle is
supported in both modes, then support of pc_longDRX_Cycle will be signaled in mac-Parameters/mac-
ParametersXDD-Diff.
If the UE is dual mode (FDD + TDD) and pc_longDRX_Cycle is only supported in one mode, then support of
pc_longDRX_Cycle will be signaled in one of fdd-Add-UE-NR-Capabilities/mac-ParametersXDD-Diff or tdd-
Note 7: If the UE is single mode (FDD or TDD), or the UE is dual mode (FDD and TDD) and pc_shortDRX_Cycle is
supported in both modes, then support of pc_shortDRX_Cycle will be signaled in mac-Parameters/mac-
ParametersXDD-Diff.
If the UE is dual mode (FDD + TDD) and pc_shortDRX_Cycle is only supported in one mode, then support of
pc_shortDRX_Cycle will be signaled in one of fdd-Add-UE-NR-Capabilities/mac-ParametersXDD-Diff or tdd-
Table 8.1.5.1.1.3.3-4: UECapabilityEnquiry-v1560-IEs (Table 8.1.5.1.1.3.3-1)

UECapabilityEnquiry-v1560-IEs ::= SEQUENCE {
capabilityRequestFilterCommon Not present
rrc-SegAllowed-r16 enabled
}
}
ETSI
Table 8.1.5.1.1.3.3-5: ULDedicatedMessageSegment (step 2a1, Table 8.1.5.1.1.3.2-1)
Derivation Path: 38.508-1 [4], Table 4.6.1-32C

ULDedicatedMessageSegment-r16 ::= SEQUENCE {
segmentNumber-r16 0 for first segment, and
incremented by 1 for
each subsequent
segment
rrc-MessageSegmentContainer-r16 Not Checked OCTET STRING
including
segmented
UECapabilityInfor
mation message
rrc-MessageSegmentType-r16 notLastSegment for all
segments except the last
segment.
lastSegment for the last

segment
}
}
8.1.5.2 SI change / On-demand SIB
8.1.5.2.1 Void
8.1.5.2.2 SI change / Notification of BCCH modification / Short message for SI update in

NR RRC_CONNECTED state
(1)
ensure that {
then { UE re-acquires the SIB1 }
}
References: The conformance requirements covered in the present test case are specified in: TS 38.331, clause 5.2.2.2.2,
5.2.2.3.1, 5.2.2.4.2 and 6.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.2.2.2.2]
A modification period is used, i.e. updated SI (other than for ETWS and CMAS) is broadcasted in the modification
period following the one where SI change indication is transmitted. The modification period boundaries are defined by
SFN values for which SFN mod m= 0, where m is the number of radio frames comprising the modification period. The
modification period is configured by system information. The UE receives indications about SI modifications and/or
PWS notifications using Short Message transmitted with P-RNTI over DCI (see clause 6.5). Repetitions of SI change
indication may occur within preceding modification period.
modification period if the UE is provided with common search space on the active BWP to monitor paging, as specified
in TS 38.213 [13], clause 13.
ETSI
2> apply the SI acquisition procedure as defined in sub-clause 5.2.2.3 from the start of the next modification.
[TS 38.331, clause 5.2.2.3.1]
The UE shall:
1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by
searchSpaceSIB1 and pagingSearchSpace and has received an indication about change of system information; or
NOTE: The UE in RRC_CONNECTED is only required to acquire broadcasted SIB1 if the UE can acquire it
without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
[TS 38.331, clause 5.2.2.4.2]
3> if the UE has a stored valid version of a SIB, in accordance with sub-clause 5.2.2.2.1, that the UE requires
to operate within the cell in accordance with sub-clause 5.2.2.1:
4> use the stored version of the required SIB;
3> if the UE has not stored a valid version of a SIB, in accordance with sub-clause 5.2.2.2.1, of one or
several required SIB(s), in accordance with sub-clause 5.2.2.1:
4> for the SI message(s) that, according to the si-SchedulingInfo, contain at least one required SIB and
for which si-BroadcastStatus is set to broadcasting:
5> acquire the SI message(s) as defined in sub-clause 5.2.2.3.2;
[TS 38.331, clause 6.5]
Short messages can be transmitted on PDCCH using P-RNTI with or without associated Paging message using Short
Message field in DCI format 1_0 (see TS 38.212 [17, 7.3.1.2.1]).
Table 6.5-1 defines Short Messages. Bit 1 is the most significant bit.
Table 6.5-1: Short messages
Bit Short message

1 systemInfoModification
If set to 1: indication of a BCCH modification other than SIB6, SIB7 and SIB8.
2 etwsAndCmasIndication
If set to 1: indication of an ETWS primary notification and/or an ETWS secondary notification and/or a
CMAS notification.
3 – [8] Not used in this release of the specification, and shall be ignored by UE if received.
ETSI
System Simulator:
- NR Cell 1
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A and Test Loop Function (ON) with UE test loop mode B established according to
TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-3.

U-S Message
1 The SS sends one IP Packet to the UE. - - - -
1A The SS waits 0.5 second and then ignores - - - -
scheduling requests and does not allocate any
uplink grant.
2 The SS changes the prach-ConfigurationIndex - - - -
in the system information.
4 Void - - - -
5 Check: Does the UE initiate a random access - - 1 P
using prach-ConfigurationIndex given in step 3
to send pending Uplink data?
6 The SS transmits Random Access Response - - - -
with RAPID corresponding to preamble in step
5. (Note 1)
7 The UE loop backs the IP packets received in - - - -
step 1
8 The SS starts the UL default grant
transmissions.
Note 1: The resource allocation for Msg3 shall be enough to accommodate all of the DRB data that UE will loop back
at step 7. To be more specific, resource allocation shall be no less than: TB size = IP packet (64 bytes) +
SDAP header (1 bytes) + PDCP header (3 bytes) + RLC header (3 bytes) + MAC header (2 bytes) + padding
or BSR (2 bytes) + C-RNTI MAC CE (2 Bytes) = 77 bytes.
Table 8.1.5.2.2.3.3-1: CLOSE UE TEST LOOP (Preamble, Table 8.1.5.2.2.3.2-1)
Derivation Path: TS 36.508-1 [7] table 4.7A-3 condition UE test loop mode B
ETSI

SIB1 ::= SEQUENCE {
prach-ConfigurationIndex 119 . FR1 FDD
94 FR1 TDD
6 FR2
}
}
}
}
}
}
8.1.5.3 PWS notification
8.1.5.3.1 PWS notification / PWS reception in NR RRC_IDLE state
(1)
ensure that {
when { an ETWS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an
etwsAndCmasIndication and the si-SchedulingInfo includes scheduling information for SIB6 }
then { the UE is able to retrieve the PWS message from SIB6 and alert the user }
}
(2)
ensure that {
then { the UE is able to retrieve all the PWS message segments from SIB7, reassemble the message
and alert the user }
}
(3)
ensure that {
when { a CMAS capable UE receives a short message transmitted on PDCCH using P-RNTI indicating an
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clause 5.2.2.2.2.
[TS 38.331 clause 5.2.2.2.2]
ETWS or CMAS capable UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for indications about PWS
notification in its own paging occasion every DRX cycle. ETWS or CMAS capable UEs in RRC_CONNECTED shall
ETSI
monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle if the UE
is provided with common search space on the active BWP to monitor paging.
For Short Message reception in a paging occasion, the UE monitors the PDCCH monitoring occasion(s) for paging as
specified in TS 38.304 [20] and TS 38.213 [13].
1> if the UE is ETWS capable or CMAS capable, the etwsAndCmasIndication bit of Short Message is set, and the
UE is provided with searchSpaceOtherSystemInformation on the active BWP:
2> immediately re-acquire the SIB1;
2> if the UE is CMAS capable and si-SchedulingInfo includes scheduling information for SIB8:
2> apply the SI acquisition procedure as defined in sub-clause 5.2.2.3 from the start of the next modification
period.
System Simulator:
- NR Cell 1.
UE:
- None.
Preamble:
- The UE is in test state 1N-A according to TS 38.508-1 [4].
ETSI

U-S Message
- If pc_ETWS_NR is true, step1-8 will be - - - -
excuted.
1 The SS indicates an etwsAndCmasIndication <-- PDCCH (DCI 1_0): Short - -
by Short Message field in DCI format 1_0 and Message
transmitted on PDCCH using P-RNTI. The SS
starts transmitting SIB1 with the si-
SchedulingInfo including scheduling
information for SIB6 on NR Cell 1.
2 The SS includes an ETWS message with new - - - -
messageIdentifier and serialNumber in SIB6.
(Note 1)
3 Check: Does the UE alert or activate alerting - - 1 P
the user (NOTE 2)?
4 The SS waits for 10s. - - - -
6 The SS includes an ETWS message with new - - - -
(NOTE 3).
7 Check: Does the UE indicate the contents of - - 2 P
the "warning message" to the user, and alert or
activate alerting the user (NOTE 2)?
8 The SS waits for 10s. - - - -
- If pc_CMAS_NR is true, step9-11 will be - - - -
excuted.
10 The SS includes a CMAS message with new - - - -
(NOTE 4).
11 Check: Does the UE indicate the contents of - - 3 P
the "warning message" to the user, and alert or
activate alerting the user (NOTE 2)?
NOTE 1: The NR-10 in Table 4.4.3.1.2-1 Combinations of system information blocks of TS 38.508-1 [4] is used.
NOTE 2: The data indication and user alerting are the UE implementation issues.
None
8.1.5.3.2 PWS notification / PWS reception in NR RRC_INACTIVE state
(1)
ensure that {
ETSI
then { the UE is able to retrieve the PWS message from SIB6 and alert the user }
}
(2)
ensure that {
}
(3)
ensure that {
}
System Simulator:
- NR Cell 1.
UE:
None.
Preamble:
- The UE is in state Registered, Inactive mode (state 2N-A) according to TS 38.508-1 [4].
Same as test case 8.1.5.3.1
8.1.5.3.3 PWS notification / PWS reception in NR RRC_CONNECTED state
(1)
ensure that {
ETSI
(2)
ensure that {
}
(3)
ensure that {
}
System Simulator:
- NR Cell 1.
UE:
None.
Preamble:
- The UE is in test state 3N-A according to TS 38.508-1 [4].
Same as test case 8.1.5.3.1 except PDCCH (DCI 1_0): Short Message is sent on active BWP.
8.1.5.3.4 PWS notification / PWS reception using dedicatedSystemInformationDelivery
(1)
ensure that {
when { UE receives an RRCReconfiguration message including dedicatedSystemInformationDelivery
containing SIB6 }
then { UE reads the SIB6 to alert the user and sends an RRCReconfigurationComplete message }
}
ETSI
(2)
ensure that {
containing SIB7 }
}
(3)
ensure that {
containing SIB8 }
}
5.2.2.4.8, 5.2.2.4.9, 5.3.5.3. Unless otherwise stated these are Rel-15 requirements.
[TS 38.331, clause 5.3.5.3]
1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery:
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery:
2> perform the action upon reception of System Information as specified in 5.2.2.4;
[TS 38.331, clause 5.2.2.4.7]
1> forward the received warningType, messageIdentifier and serialNumber to upper layers;
[TS 38.331, clause 5.2.2.4.8]
1> if there is no current value for messageIdentifier and serialNumber for SIB7; 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 SIB7:
2> use the received values of messageIdentifier and serialNumber for SIB7 as the current values of
messageIdentifier and serialNumber for SIB7;
2> discard any previously buffered warningMessageSegment;
2> if all segments of a warning message have been received:
3> assemble the warning message from the received warningMessageSegment;
3> forward the received warning message, messageIdentifier, serialNumber and dataCodingScheme to upper
layers;
3> stop reception of SIB7;
3> discard the current values of messageIdentifier and serialNumber for SIB7;
2> else:
3> store the received warningMessageSegment;
ETSI
3> continue reception of SIB7;
1> else if all segments of a warning message have been received:
2> forward the received complete warning message, messageIdentifier, serialNumber and dataCodingScheme to
upper layers;
2> stop reception of SIB7;
2> discard the current values of messageIdentifier and serialNumber for SIB7;
1> else:
The UE should discard any stored warningMessageSegment and the current value of messageIdentifier and
serialNumber for SIB7 if the complete warning message has not been assembled within a period of 3 hours.
[TS 38.331, clause 5.2.2.4.9]
1> if the SIB8 contains a complete warning message and the complete geographical area coordinates (if any):
2> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and the
geographical area coordinates (if any) to upper layers;
1> else:
2> if the received values of messageIdentifier and serialNumber are the same (each value is the same) as a pair
for which a warning message and the geographical area coordinates (if any) are currently being assembled:
3> store the received warningAreaCoordinatesSegment (if any);
3> if all segments of a warning message and geographical area coordinates (if any) have been received:
4> assemble the geographical area coordinates from the received warningAreaCoordinatesSegment (if
any);
4> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and
geographical area coordinates (if any) to upper layers;
4> stop assembling a warning message and geographical area coordinates (if any) for this
messageIdentifier and serialNumber and delete all stored information held for it;
2> else if the received values of messageIdentifier and/or serialNumber are not the same as any of the pairs for
which a warning message is currently being assembled:
3> start assembling a warning message for this messageIdentifier and serialNumber pair;
3> start assembling the geographical area coordinates (if any) for this messageIdentifier and serialNumber
pair;
3> store the received warningAreaCoordinatesSegment (if any);
ETSI
The UE should discard warningMessageSegment and warningAreaCoordinatesSegment (if any) and the associated
values of messageIdentifier and serialNumber for SIB8 if the complete warning message and the geographical area
coordinates (if any) have not been assembled within a period of 3 hours.
NOTE: The number of warning messages that a UE can re-assemble simultaneously is a function of UE
implementation.
System Simulator:
- NR Cell 1.
UE:
- None
Preamble:
- The UE is in 5GS state 3N-A according to TS 38.508-1 [4], clause 4.4A.2 Table 4.4A.2-1

U-S Message
- If pc_ETWS_NR is true, steps 1-6 will be - - - -
excuted.
message containing
dedicatedSystemInformationDelivery
containing SIB6.
the user (NOTE 1)?
message containing
containing SIB7.
6 Check: Does the UE indicate the "warning - - 2 P
message" to the user, and alert or activate
alerting the user (NOTE 1)?
- If pc_CMAS_NR is true, steps 7-9 will be - - - -
excuted.
message containing
containing SIB8.
the user (NOTE 1)?
NOTE 1: The data indication and user alerting are the UE implementation issues.
ETSI
Table 8.1.5.3.4.3.3-1: RRCReconfiguration (Steps 1, 4 and 7 Table 8.1.5.3.4.3.2-1)

masterCellGroup Not present
dedicatedNAS-MessageList Not present
dedicatedSystemInformationDelivery SystemInformation OCTET STRING
(CONTAINING
SystemInformatio
n)
}
}
}
}
Table 8.1.5.3.4.3.3-2: SystemInformation (Steps 1, 4 and 7 Table 8.1.5.3.4.3.2-1)

systemInformation-r15 SEQUENCE {
sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB)) 1 entry
OF CHOICE {
sib6 SIB6 Acc to 38.508-1 Step 1
[4] Table 4.6.2-5:
SIB6
sib7 SIB7 Step 4
sib8 SIB8 Step 7
}
nonCriticalExtension SEQUENCE {} Not present
}
}
}
ETSI
Table 8.1.5.3.4.3.3-3: SIB7 (Step 4 in Table 8.1.5.3.4.3.2-1)

SIB7 ::= SEQUENCE {
messageIdentifier '0001 0001 0000 0010'B ETWS message
identifier for
earthquake and
tsunami message
(see TS 23.041
[25])
serialNumber '0011 0000 0000 0000'B Note 1.
warningMessageSegmentType lastSegment
warningMessageSegmentNumber 0
warningMessageSegment Octetstring of N Containing the
complete ETWS
message
dataCodingScheme Bitstring (8) ID of the see TS 23.041
alphabet/coding and the [25].
applied language
}
Note 1: Geographical Scope (Octet 1 bit 7 ~ 6) set to 'Cell wide',
Emergency User Alert (Octet 1 bit 5) set to 'Activate emergency user alert',
Popup (Octet 1 bit 4) set to 'Activate popup',
Update Number (Octet 2 bits 3~0) for each update, incremented by one, See TS 23.041 [25].
Table 8.1.5.3.4.3.3-4: SIB8 (Step 7 in Table 8.1.5.3.4.3.2-1)

SIB8 ::= SEQUENCE {
messageIdentifier '0001 0001 0001 0010'B CMAS CBS
Message Identifier
for CMAS
Presidential Level
Alerts (see TS
23.041 [25])
serialNumber '0011 0000 0000 0000'B Note 1
warningMessageSegmentType lastSegment
warningMessageSegmentNumber 0
warningMessageSegment Octetstring of N
dataCodingScheme Bitstring (8) ID of the Containing the
alphabet/coding and the complete CMAS
applied language message
warningAreaCoordinatesSegment Not present

}
Note 1: Geographical Scope (Octet 1 bit 7 ~ 6) set to 'Cell wide',
Emergency User Alert (Octet 1 bit 5) set to 'Activate emergency user alert',
Popup (Octet 1 bit 4) set to 'Activate popup',
Update Number (Octet 2 bits 3~0) for each update, incremented by one, See TS 23.041 [25].
ETSI
8.1.5.4 Counter check
8.1.5.4.1 Counter check / Reception of CounterCheck message by the UE
(1)
with { UE in NR RRC_CONNECTED state with two DRBs established and having received 10 data packets on
each DRB }
ensure that {
when { UE receives CounterCheck message with drb-CountMSB-InfoList included for DRB3(not
established) and DRB1 (with the most significant bits of the count different from the actual COUNT)}
then { UE sends CounterCheckResponse message by including the drb-Identity, the count-Uplink and
the count-Downlink set to the value of TX_NEXT – 1 and RX_NEXT – 1 in drb-CountInfoList IE for each
DRB established, and by including the drb-Identity, the count-Uplink and the count-Downlink with the
most significant bits set identical to the corresponding values in the drb-CountMSB-InfoList and the
least significant bits set to zero for the DRB that is not established }
}
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.6.3.
[TS 38.331, clause 5.3.6.3]
Upon receiving the CounterCheck message, the UE shall:
1> for each DRB that is established:
2> if no COUNT exists for a given direction (uplink or downlink) because it is a uni-directional bearer
configured only for the other direction:
3> assume the COUNT value to be 0 for the unused direction;
2> if the drb-Identity is not included in the drb-CountMSB-InfoList:
3> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-
Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT – 1 and RX_NEXT – 1
(specified in TS 38.323 [5]), respectively;
2> else if, for at least one direction, the most significant bits of the COUNT are different from the value
indicated in the drb-CountMSB-InfoList:
Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT – 1 and RX_NEXT – 1
(specified in TS 38.323 [5]), respectively;
1> for each DRB that is included in the drb-CountMSB-InfoList in the CounterCheck message that is not
established:
Identity, the count-Uplink and the count-Downlink with the most significant bits set identical to the
corresponding values in the drb-CountMSB-InfoList and the least significant bits set to zero;
1> submit the CounterCheckResponse message to lower layers for transmission upon which the procedure ends.
System Simulator:
- NR Cell 1.
ETSI
- System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.3 is used in the NR cell.
UE:
- None.
Preamble:
- The UE is in 5GS state 3N-A on NR Cell 1 with atleast one PDU session active according to TS 38.508-1 [4],
clause 4.4A.3 Table 4.4A.3-1 and Test Loop Function (On) with UE test loop mode B is established. 2 DRBs are
configured where DRB1 is defined as default DRB.

U-S Message
1 The SS transmits 10 IP packets on each DRB - - - -
(using QFI2 for DRB1 and QFI5 for DRB2)
2 The UE loops back the IP packets received in - - - -
step 1 (Note 1)
3 The SS transmits CounterCheck message with <-- NR RRC: CounterCheck - -
drb-Identity not included in the drb-CountMSB-
InfoList
CounterCheckResponse message by including CounterCheckResponse
the drb-Identity, the count-Uplink and the
count-Downlink set to the value of TX_NEXT –
1 and RX_NEXT – 1 in drb-CountInfoList IE for
each DRB established?
Note 1: IP packets at step 2 may be received by the SS in the same slot or in multiple slots
Table 8.1.5.4.1.3.3-1: RRCReconfiguration (Preamble, Table 8.1.5.4.1.3.2-1)
Derivation Path: TS 38.508-1 [4], table 4.6.1-13 with condition NR

radioBearerConfig RadioBearerConfig-
2DRBs
masterCellGroup CellGroupConfig-2DRBs OCTET STRING
(CONTAINING
CellGroupConfig)
}
}
}
}
ETSI
Table 8.1.5.4.1.3.3-2: RadioBearerConfig-2DRBs (Preamble, Table 8.1.5.4.1.3.3-1)
Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition SRB2 and DRB1
OF DRB-ToAddMod {
sdap-Config::= SEQUENCE {
pdu-Session PDU session ID Same as the PDU
session ID in PDU
SESSION
ESTABLISHMEN
T REQUEST
defaultDRB true
QFI 2
}
}
}
Condition DRB1
}
}
DRB-ToAddMod[2] SEQUENCE entry 2
pdu-Session PDU session ID Same as the PDU
session ID in PDU
SESSION
ESTABLISHMEN
T REQUEST
defaultDRB false
QFI 5
}
}
}
Condition DRB2
}
}
}
}
Table 8.1.5.4.1.3.3-3: CellGroupConfig-2DRBs (Preamble, Table 8.1.5.4.1.3.3-1)
Derivation Path: TS 38.508-1 [4], table 4.6.3-19 and condition SRB2_DRB1

condition SRB2
}
}
ETSI
Table 8.1.5.4.1.3.3-4: PDU SESSION ESTABLISHMENT ACCEPT (Preamble) (Table 8.1.5.4.1.3.2-1)

session ID in PDU
SESSION
ESTABLISHMENT
REQUEST
as defined in Table
4.8.2.1-1.
as defined in Table
4.8.2.1-4 except DQR bit
set to ‘0’B.
as defined in Table
4.8.2.1-5.
Mapped EPS Bearer contexts Not Present
as defined in
Table8.1.5.4.1.3.3-7.
as defined in
Table8.1.5.4.1.3.3-8.
as defined in Table
4.8.2.3-3.
Table 8.1.5.4.1.3.3-5: CounterCheck (step 3, Table 8.1.5.4.1.3.2-1)

CounterCheck ::= SEQUENCE {
counterCheck SEQUENCE {
drb-CountMSB-InfoList SEQUENCE (SIZE 2 entries
(1..maxDRB)) OF DRB-CountMSB-Info {
DRB-CountMSB-Info[1] SEQUENCE { entry 1
drb-Identity DRB-Identity with DRB established
Condition DRB1
countMSB-Uplink 1
countMSB-Downlink 1
}
DRB-CountMSB-Info[2] SEQUENCE { entry 2
drb-Identity DRB-Identity with DRB not
Condition DRB3 established
countMSB-Uplink 3
countMSB-Downlink 3
}
}
}
}
}
ETSI
Table 8.1.5.4.1.3.3-6: CounterCheckResponse (step 4, Table 8.1.5.4.1.3.2-1)

CounterCheckResponse ::= SEQUENCE {
counterCheckResponse SEQUENCE {
drb-CountInfoList SEQUENCE (SIZE 3 entries
(0..maxDRB)) OF DRB-CountInfo {
DRB-CountInfo[1] SEQUENCE { entry 1
Condition DRB1
count-Uplink 9
count-Downlink 9
}
Condition DRB2 but not requested
count-Uplink 9
count-Downlink 9
}
drb-Identity DRB-Identity with DRB not
Condition DRB3 established
count-Uplink] 384 MSB 3 and LSB 0
count-Downlink 384 MSB 3 and LSB 0
}
}
}
}
}
Table 8.1.5.4.1.3.3-7: Reference QoS flow #1 (Preamble)
Derivation Path: TS 38.508-1, table 4.8.2.3-1

QFI ‘00 0001’B QFI 1
flow description
included
5QI ‘0000 1001’B 5QI 9
Table 8.1.5.4.1.3.3-8: Reference QoS flow #2 (Preamble)
Derivation Path: TS 38.508-1, table 4.8.2.3-2

QoS flow description
QFI ‘00 0010’B QFI 2
flow description
included
5QI ‘0000 0101’B 5QI 5
ETSI
8.1.5.5 Redirection to NR
8.1.5.5.1 Redirection to NR / From E-UTRA / Success
(1)
ensure that {
when { UE receives an RRCConnectionRelease message including a redirectedCarrierInfo for
redirection to an NR cell }
then { UE enters E-UTRA RRC_IDLE state and performs redirection to NR cell }
}
References: The conformance requirements covered in the current TC is specified in: TS 36.331 clause 5.3.8.3. Unless
[TS 36.331, clause 5.3.8.3]
The UE shall:
1> except for NB-IoT, BL UEs or UEs in CE, 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> for BL UEs or UEs in CE, delay the following actions defined in this sub-clause 1.25 seconds 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> for NB-IoT, delay the following actions defined in this sub-clause 10 seconds 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.
NOTE: For BL UEs, UEs in CE and NB-IoT, when STATUS reporting, as defined in TS 36.322 [7], has not been
triggered and the UE has sent positive HARQ feedback (ACK), as defined in TS 36.321 [6], the lower
layers can be considered to have indicated that the receipt of the RRCConnectionRelease message has
been successfully acknowledged.
1> stop T380, if running;
1> if the RRCConnectionRelease message is received in response to an RRCConnectionResumeRequest for EDT:
2> indicate to upper layers that the suspended RRC connection has been resumed;
2> discard the stored UE AS context and resumeIdentity;
2> stop timer T300;
ETSI
1> if the security is not activated and if UE is connected to 5GC:
2> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12 with the
1> if the RRCConnectionRelease message includes redirectedCarrierInfo indicating redirection to geran; or
1> if the RRCConnectionRelease message includes idleModeMobilityControlInfo including freqPriorityListGERAN:
2> if AS security has not been activated; and
2> if upper layers indicate that redirect to GERAN without AS security is not allowed:
3> ignore the content of the RRCConnectionRelease;
3> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12, with
release cause 'other', upon which the procedure ends;
1> if AS security has not been activated:
2> ignore the content of redirectedCarrierInfo, if included and indicating redirection to nr;
2> ignore the content of idleModeMobilityControlInfo, if included and including freqPriorityListNR;
2> if the UE ignores the content of redirectedCarrierInfo or of idleModeMobilityControlInfo:
3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other',
upon which the procedure ends;
1> if the RRCConnectionRelease message includes redirectedCarrierInfo indicating redirection to eutra and if UE
is connected to 5GC:
2> if cn-Type is included:
3> after the cell selection, indicate the available CN Type(s) and the received cn-Type to upper layers;
NOTE 1: Handling the case if the E-UTRA cell selected after the redirection does not support the core

Lte Parametros

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lte Parametros

Uploaded by

Copyright:

Available Formats

ETSI TS 138 523-1 V16.9.

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - APE 7112B

Notice of disclaimer & limitation of liability

Intellectual Property Rights

Modal verbs terminology

6.4.1 NG-RAN Only PLMN Selection in RRC_INACTIVE state .................................................................... 345

8.1.3.1.3 Measurement configuration control and reporting / Event A3 / Measurement of Neighbour

8.1.3.2.6 Measurement configuration control and reporting / Inter-RAT measurements / Event B1 / NR

8.1.5.3.3 PWS notification / PWS reception in NR RRC_CONNECTED state......................................... 1566

8.1.6.1.3.2 Radio Link Failure / Reporting of Inter-frequency measurements ........................................ 1754

8.2.3.8.1a Measurement configuration control and reporting / Event A5 / Measurement of Neighbour

8.2.5.1 Radio link failure / PSCell addition failure ....................................................................................... 2437

9.1.5.1.7 Void ............................................................................................................................................. 2596

9.2.4.1 Generic UE configuration update ...................................................................................................... 2731

10.3.1 PDU session authentication and authorization........................................................................................ 2852

11.4.4 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE T3346 running / Emergency

Annex A (informative): Change history ...........................................................................................3140

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.

In the present document, modal verbs have the following meanings:

shall indicates a mandatory requirement to do something

shall not indicates an interdiction (prohibition) to do something

should indicates a recommendation to do something

should not indicates a recommendation not to do something

may indicates permission to do something

need not indicates permission not to do something

can indicates that something is possible

cannot indicates that something is impossible

The constructions "is" and "is not" do not indicate requirements.

- the overall test structure;

- the test configurations;

- the conformance requirement and references to the core specifications;

- the test purposes; and

- For a specific reference, subsequent revisions do not apply.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 38.523-2: "5GS; UE conformance specification; Part 2: Implementation Conformance

[14] 3GPP TS 38.212: "NR; Multiplexing and channel coding".

[15] 3GPP TS 38.214: "NR; Physical layer procedures for data".

[28] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".

[31] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".

[34] 3GPP TS 23.003: "Numbering, addressing and identification"

[39] GSMA PRD IR.88: "LTE and EPC Roaming Guidelines".

[42] 3GPP TS 22.101: "Service aspects; Service principles".

3 Definitions, symbols and abbreviations

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.

ICS Implementation Conformance Statement

4.1 Test methodology

4.1.2 Test interfaces and facilities

4.2 Implicit testing

4.3 Repetition of tests

4.4 Handling of differences between conformance requirements

5 Reference conditions, generic and test procedures,

5.1 Reference conditions

5.2 Generic and test procedures

5.3 Test parameters

5.3.4 Messages and Information Elements (IEs)

6 Idle mode and RRC Inactive state operations

6.1 NR idle mode operations

6.1.1.1 PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN /