TS 136 523-3 - V13.2.0

TS 136 523-3 - V13.2.0
ETSI TS 136 523-3 V13.2.0 (2017-03)
TECHNICAL SPECIFICATION
LTE;
Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC);
User Equipment (UE) conformance specification;
Part 3: Test suites
(3GPP TS 36.523-3 version 13.2.0 Release 13)
3GPP TS 36.523-3 version 13.2.0 Release 13
1
ETSI TS 136 523-3 V13.2.0 (2017-03)
Reference
RTS/TSGR-0536523-3vd20
Keywords
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 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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
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.
© European Telecommunications Standards Institute 2017.
All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
2
ETSI TS 136 523-3 V13.2.0 (2017-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 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
3GPP TS 36.523-3 version 13.2.0 Release 13
3
ETSI TS 136 523-3 V13.2.0 (2017-03)
Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Modal verbs terminology....................................................................................................................................2
Foreword...........................................................................................................................................................14
Introduction ......................................................................................................................................................14
1
Scope ......................................................................................................................................................15
2
References ..............................................................................................................................................15
3
Definitions and abbreviations .................................................................................................................18
3.1
3.2
4
Definitions ........................................................................................................................................................ 18
Abbreviations ................................................................................................................................................... 18
E-UTRAN/SAE system architecture and test models ............................................................................18
4.1
Test system architecture ................................................................................................................................... 18
4.1.1
General system architecture ........................................................................................................................ 18
4.1.2
Component architecture .............................................................................................................................. 19
4.2
E-UTRAN test models ..................................................................................................................................... 21
4.2.1
Layer 2 test models ..................................................................................................................................... 21
4.2.1.1
MAC test model .................................................................................................................................... 21
4.2.1.2
RLC test model ..................................................................................................................................... 23
4.2.1.3
PDCP test model ................................................................................................................................... 24
4.2.1.3.1
PDCP ROHC test model ................................................................................................................. 24
4.2.1.3.2
PDCP test model (Non ROHC) ....................................................................................................... 25
4.2.2
RRC test model ........................................................................................................................................... 26
4.2.3
DRB test model........................................................................................................................................... 27
4.2.4
IP Test Model ............................................................................................................................................. 27
4.2.4.1
IP user data ............................................................................................................................................ 28
4.2.4.2
Configuration of Sockets....................................................................................................................... 29
4.2.4.2.1
Socket Establishment....................................................................................................................... 29
4.2.4.2.2
Socket Release ................................................................................................................................. 30
4.2.4.3
Handling of IP data ............................................................................................................................... 30
4.2.4.4
Routing of IP Data ................................................................................................................................ 31
4.2.4.5
Multiple PDNs ...................................................................................................................................... 31
4.2.4.6
IP Addresses Guidelines ....................................................................................................................... 32
4.2.4.6.1
Common Structure of IP Addresses ................................................................................................ 32
4.2.4.6.2
Common Requirements regarding IP Addresses ............................................................................. 33
4.2.4.6.3
Network Entities and their IP addresses .......................................................................................... 33
4.2.4.7
User Plane Signalling for Address Allocation....................................................................................... 34
4.2.4.7.1
DHCP .............................................................................................................................................. 34
4.2.4.7.2
DHCPv6 .......................................................................................................................................... 37
4.2.4.7.3
ICMPv6 ........................................................................................................................................... 37
4.2.4.7.4
DNS ................................................................................................................................................. 38
4.2.4A
LTE-Carrier Aggregation test Models ........................................................................................................ 41
4.2.4A.1
CA-MAC test model ............................................................................................................................. 41
4.2.4A.2
CA-RRC test model .............................................................................................................................. 43
4.2.4A.3
LAA-MAC test model........................................................................................................................... 44
4.2.4A.4
LAA-RRC test model ............................................................................................................................ 45
4.2.4B
Dual Connectivity test models .................................................................................................................... 46
4.2.4B.1
DC MAC test model.............................................................................................................................. 46
4.2.4B.2
DC PDCP test model ............................................................................................................................. 47
4.2.4B.3
DC RRC test model ............................................................................................................................... 48
4.2.5
IP model extension for IMS ........................................................................................................................ 49
4.2.5.1
IPsec ...................................................................................................................................................... 50
4.2.5.1.1
Security Association ........................................................................................................................ 50
4.2.5.1.2
SAD and SPD .................................................................................................................................. 51
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4
ETSI TS 136 523-3 V13.2.0 (2017-03)
4.2.5.2
Signalling Compression (SigComp) ................................................................................................ 52
4.2.5.3
SIP TTCN-3 Codec ......................................................................................................................... 52
4.2.6
Support of DSMIPv6 .................................................................................................................................. 52
4.2.7
MBMS test model ....................................................................................................................................... 53
4.2.8
OCNG test model ....................................................................................................................................... 53
4.2.9
Device-to-Device Proximity Services test model ....................................................................................... 55
4.2.9.1
ProSe Function test model .................................................................................................................... 56
4.2.9.2
Direct Discovery test model .................................................................................................................. 56
4.2.9.3
Direct Communication test model......................................................................................................... 57
4.2.10
SC-PTM test model .................................................................................................................................... 58
4.3
SAE Test Model ............................................................................................................................................... 59
4.3.1
NAS Test Model ......................................................................................................................................... 59
4.4
Inter RAT Test Model ...................................................................................................................................... 60
4.4.1
E-UTRAN-UTRAN Inter RAT Test Model ............................................................................................... 60
4.4.1.1
User data over UTRAN ......................................................................................................................... 60
4.4.1.1.1
Raw user data over UTRAN ............................................................................................................ 61
4.4.1.1.2
IP data over UTRAN ....................................................................................................................... 61
4.4.1.1.3
Routing IP data ................................................................................................................................ 62
4.4.2
E-UTRAN-GERAN Inter RAT Test Model ............................................................................................... 63
4.4.2.1
User data over GERAN ......................................................................................................................... 63
4.4.2.1.1
Raw user data over GERAN ............................................................................................................ 64
4.4.2.1.2
IP data over GERAN ....................................................................................................................... 64
4.4.2.1.3
Routing IP data ................................................................................................................................ 65
4.4.3
E-UTRAN-CDMA2000 Inter RAT Test Model ......................................................................................... 66
4.4.3.1
E-UTRAN-CDMA2000 HRPD Inter RAT Test Model ........................................................................ 66
4.4.3.2
E-UTRAN-CDMA2000 1xRTT Inter RAT test model......................................................................... 68
4.4.4
E-UTRAN FDD-TDD Inter RAT Test Model ............................................................................................ 71
4.4.5
E-UTRAN-UTRAN-GERAN Inter RAT Test Model ................................................................................ 72
4.4.6
3GPP-WLAN Inter working Test Model .................................................................................................... 73
4.4.6.1
E-UTRAN-WLAN Inter working Test Model ...................................................................................... 73
4.4.6.2
UTRAN-WLAN Inter working Test Model .......................................................................................... 75
4.5
Generic WLAN Test Model ............................................................................................................................. 76
4.5.1
WLAN Access Point ................................................................................................................................... 76
4.5.2
ePDG/AAA-Server Emulation.................................................................................................................... 76
4A
NB-IoT system architecture and test models..........................................................................................79
4A.1
Test system architecture ................................................................................................................................... 79
4A.2
NB-IoT test models .......................................................................................................................................... 79
4A.2.1
Layer 2 test models ..................................................................................................................................... 79
4A.2.1.1
Layer 2 loopback mode for CP mode.................................................................................................... 79
4A.2.1.2
MAC test model (CP mode) .................................................................................................................. 81
4A.2.1.3
RLC test model (CP mode) ................................................................................................................... 82
4A.2.1.4
PDCP test model ................................................................................................................................... 83
4A.2.2
RRC / NAS test model ................................................................................................................................ 84
5
5.1
5.2
6
6.1
6.1.1
6.1.2
6.2
6.2.1
6.2.2
6.2.3
6.3
6.3.1
6.3.2
6.4
6.4.1
6.4.2
Upper Tester Interface ............................................................................................................................85
Definitions ........................................................................................................................................................ 85
Upper Tester ASPs ........................................................................................................................................... 85
ASP specifications..................................................................................................................................91
General Requirements and Assumptions .......................................................................................................... 91
IP ASP requirements ................................................................................................................................... 91
Enhancement of IP ASP for handling IMS signalling ................................................................................ 91
E-UTRAN ASP Definitions ............................................................................................................................. 92
Configuration Primitives............................................................................................................................. 92
Signalling Primitives................................................................................................................................... 92
Co-ordination Messages between NAS Emulation PTC and EUTRA PTC ............................................... 93
UTRAN ASP Definitions ................................................................................................................................. 94
Void ............................................................................................................................................................ 95
ASPs for Data Transmission and Reception ............................................................................................... 95
GERAN ASP Definitions ................................................................................................................................. 96
ASPs for Control Primitive Transmission .................................................................................................. 96
ASPs for Data Transmission and Reception ............................................................................................... 98
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
6.5
6.5.1
6.5.2
6.5.3
7
5
ETSI TS 136 523-3 V13.2.0 (2017-03)
NB-IoT ASP Definitions ................................................................................................................................ 101
Configuration Primitives........................................................................................................................... 101
Signalling Primitives................................................................................................................................. 101
Co-ordination Messages between NAS Emulation PTC and NBIOT PTC .............................................. 102
E-UTRAN/SAE Test Methods and Design Considerations .................................................................104
7.1
7.1.1
7.1.1.1
7.1.1.2
7.1.1.2.1
7.1.2
7.1.2.1
7.1.2.2
7.1.3
7.2
7.2.1
7.3
7.3.1
7.3.1.1
7.3.2
7.3.2.1
7.3.3
7.3.3.1
7.3.3.1.1
7.3.3.1.2
7.3.3.2
7.3.3.2.1
7.3.3.2.2
7.3.3.3
7.3.3.3.1
7.3.3.3.2
7.3.3.4
7.3.3.5
7.3.3.5.1
7.3.3.5.2
7.3.3.6
7.3.3.6.1
7.3.3.7
7.3.3.8
7.3.3.8.1
7.3.3.8.2
7.3.3.8.3
7.3.3.8.4
7.3.3.9
7.3.3.9.1
7.4
7.4.1
7.4.2
7.4.3
7.4.3.1
7.4.4
7.4.5
7.5
7.5.1
7.5.2
7.6
7.6.1
7.6.2
7.7
7.7.1
7.7.2
Channel Mapping ........................................................................................................................................... 104
PDCCH Candidate Selection .................................................................................................................... 104
FDD candidates selection .................................................................................................................... 105
TDD candidates selection ................................................................................................................... 109
TDD candidates selection in special subframes .................................................................................. 112
ePDCCH Candidate Selection .................................................................................................................. 112
FDD candidates selection .................................................................................................................... 112
TDD candidates selection ................................................................................................................... 113
MPDCCH Candidate Selection................................................................................................................. 113
Uplink Grant ................................................................................................................................................... 114
Exception TC list ...................................................................................................................................... 117
Downlink Resource Allocation ...................................................................................................................... 117
PDCCH DCI default formats .................................................................................................................... 118
Default DCI Format to be used in test cases configuring MIMO........................................................ 118
Radio parameters configured .................................................................................................................... 118
HARQ Retransmission when MIMO is configured .................................................................................. 119
General DL scheduling scheme ................................................................................................................ 119
Additional rules for BCCH scheduling scheme .................................................................................. 119
BCCH with DCI combination 1 .................................................................................................... 120
BCCH with DCI combination 2 .................................................................................................... 120
Additional rules for PCCH specific scheduling scheme ..................................................................... 120
PCCH with DCI combination 1 ..................................................................................................... 120
PCCH with DCI combination 2 ..................................................................................................... 120
Additional rules for RAR specific scheduling scheme ........................................................................ 121
RAR with DCI combination 1 ....................................................................................................... 121
RAR with DCI combination 2 ....................................................................................................... 121
Additional rules for UE-dedicated scheduling scheme in normal mode ............................................. 121
DL Resource allocation bitmaps ......................................................................................................... 123
DCI combination 1 ........................................................................................................................ 123
DCI combination 2 ........................................................................................................................ 125
UE-dedicated scheduling scheme in explicit mode ............................................................................. 128
DL Scheduling in Transport Block Size Selection Test Cases ...................................................... 129
Resource allocation sheets .................................................................................................................. 129
MPDCCH DL DCI formats ................................................................................................................ 130
BCCH ............................................................................................................................................ 130
PCCH ............................................................................................................................................ 131
RAR ............................................................................................................................................... 131
UE-dedicated scheduling ............................................................................................................... 131
DL Resource allocation bitmaps for BL/CE UE ................................................................................. 132
DCI combination 1 ........................................................................................................................ 132
Cell Configurations ........................................................................................................................................ 134
Cell Configuration Types.......................................................................................................................... 134
Cell Power Change ................................................................................................................................... 134
E-UTRAN cell identity ............................................................................................................................. 134
Timing parameters of cells .................................................................................................................. 134
Cell configurations for NAS test cases ..................................................................................................... 136
Configuration of Multi-Cell Environment ................................................................................................ 137
TDD Considerations ....................................................................................................................................... 137
FDD vs. TDD implementation.................................................................................................................. 137
Guideline for FDD vs. TDD verification .................................................................................................. 137
Special RLC Modes........................................................................................................................................ 138
Suppression of RLC Acknowledgements ................................................................................................. 138
Modification of VT(S) .............................................................................................................................. 138
System information ........................................................................................................................................ 138
System information broadcasting ............................................................................................................. 138
Scheduling information............................................................................................................................. 139
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.7.2a
7.7.3
7.7.3.1
7.7.3.1.1
7.7.3.1.2
7.7.3.2
7.8
7.8.1
7.8.2
7.8.3
7.8.4
7.9
7.10
7.11
7.12
7.12.1
7.12.2
7.13
7.14
7.14.1
7.14.2
7.15
7.16
7.16.1
7.16.1a
7.16.2
7.16.3
7.17
7.17.1
7.17.2
7.18
7.19
7.20
7.21
7.21.1
7.21.2
7.21.3
7.22
7.22.1
7.22.2
7.22.3
7.23
7.24
7.24.1
7.24.2
7.24.3
7.25
7.25.1
7.25.2
7.25.3
7.26
7.27
7.27.1
7.27.2
7.27.2.1
7.27.2.2
7.28
7.28.1
7.28.2
7.28.3
6
ETSI TS 136 523-3 V13.2.0 (2017-03)
Scheduling information for BR System information ................................................................................ 142
System information modification ............................................................................................................. 150
Non-PWS System Information modification ...................................................................................... 150
UE in Idle_mode............................................................................................................................ 150
UE in connected mode................................................................................................................... 151
PWS System Information modification .............................................................................................. 152
Timers and Timing Restrictions ..................................................................................................................... 152
Auxiliary timers ........................................................................................................................................ 153
RRC timers reconfiguration ...................................................................................................................... 153
MAC TA timer reconfiguration ................................................................................................................ 153
Non-protocol timers .................................................................................................................................. 153
Error Indication .............................................................................................................................................. 153
Race Conditions ............................................................................................................................................. 154
Radio Link Failure.......................................................................................................................................... 154
Test method for RRC signalling latency ........................................................................................................ 154
Procedure delays in PUCCH synchronized state ...................................................................................... 154
Procedure delays when RACH procedure required .................................................................................. 156
RLC test method for scheduled data............................................................................................................... 156
IP packets for Loopback Mode....................................................................................................................... 157
IP packets used for Loopback Mode A ..................................................................................................... 157
IP packets used for Loopback Mode B ..................................................................................................... 157
Connected Mode DRX ................................................................................................................................... 158
Handover Sequences ...................................................................................................................................... 159
Sequence of inter-cell handover................................................................................................................ 159
Sequence of inter-cell CA handover (more than one CC before and after handover)............................... 160
Sequence of intra-cell handover................................................................................................................ 161
UL Grants used in RA procedure during handover .................................................................................. 162
Simulation of PDCP MAC-I Failure in UE .................................................................................................... 162
Integrity and ciphering not yet activated................................................................................................... 162
Integrity and/or ciphering already activated ............................................................................................. 163
RRC Connection Release Sequence ............................................................................................................... 163
DL CCCH Message and Contention Resolution MAC Control Element transmission in one MAC PDU
or in separate MAC PDUs .............................................................................................................................. 163
RRC Connection Reconfiguration Sequence (Measurement Control) ........................................................... 164
Inter-RAT - GERAN special issues................................................................................................................ 164
Timeslot assigned for GERAN CS traffic................................................................................................. 164
Subchannel used in GERAN L2 access message ...................................................................................... 164
Paging in GERAN .................................................................................................................................... 164
EUTRAN RSRQ Calculations ....................................................................................................................... 165
Assumptions ............................................................................................................................................. 165
The Ideal Calculation ................................................................................................................................ 165
Additional RSRQ Calculations For Fixing Boundary Values .................................................................. 165
Test method for eICIC and feICIC ................................................................................................................. 166
Carrier Aggregation Signalling Sequences ..................................................................................................... 166
Initial configuration of Pcell ..................................................................................................................... 166
Initial configuration of SCell .................................................................................................................... 167
Scell Addition and/or release .................................................................................................................... 168
Test method for MBMS ................................................................................................................................. 168
Schedule transmission of MCCH messages .............................................................................................. 168
MCCH change notification ....................................................................................................................... 169
MTCH data scheduling ............................................................................................................................. 169
Type B FDD Half-Duplex Considerations ..................................................................................................... 169
Test method for Device-to-Device Proximity Services .................................................................................. 170
Direct Discovery test method.................................................................................................................... 170
Direct Communication test method .......................................................................................................... 170
Synchronisation and SBCCH transmission ......................................................................................... 170
Sidelink data transmission/reception ................................................................................................... 171
Test method for SC-PTM ............................................................................................................................... 171
Schedule transmission of SC-MCCH messages ....................................................................................... 171
SC-MCCH information change ................................................................................................................ 172
SC-MTCH data scheduling ....................................................................................................................... 172
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7A
7
ETSI TS 136 523-3 V13.2.0 (2017-03)
NB-IoT Test Methods and Design Considerations ..............................................................................172
7A.1
Physical signals and channels ......................................................................................................................... 172
7A.2
System information ........................................................................................................................................ 172
7A.2.1
System information broadcasting in general ............................................................................................. 172
7A.2.2
System information scheduling and synchronisation signals .................................................................... 173
7A.2.2.1
MIB-NB, NPSS, NSSS ....................................................................................................................... 173
7A.2.2.2
SIB1-NB ............................................................................................................................................. 173
7A.2.2.3
SI-messages containing SIB3-NB, SIB4-NB, SIB5-NB, SIB14-NB, SIB16-NB ............................... 174
7A.2.2.3.1
SI combination 1 scheduling ......................................................................................................... 174
7A.2.2.3.2
SI combination 2/3/4 scheduling ................................................................................................... 175
7A.2.3
System information modification ............................................................................................................. 176
7A.3
Search space configurations ........................................................................................................................... 176
7A.3.1
Type1CSS - Paging................................................................................................................................... 177
7A.3.2
Type2CSS – Random access .................................................................................................................... 177
7A.3.3
UESS ........................................................................................................................................................ 177
7A.4
Timing considerations .................................................................................................................................... 178
7A.4.1
Random access procedure ......................................................................................................................... 178
7A.4.2
Uplink transmissions................................................................................................................................. 179
7A.4.3
Downlink transmissions ............................................................................................................................ 180
7A.4.4
Half-duplex mode ..................................................................................................................................... 180
7A.4.5
Conclusions............................................................................................................................................... 181
7A.5
Scheduling requests and scheduling of UL grants .......................................................................................... 181
7A.5.1
RACH procedure mode ............................................................................................................................ 181
7A.5.2
Polling mode ............................................................................................................................................. 181
7A.6
Scheduling requirements ................................................................................................................................ 181
7A.6.1
Random access procedure ......................................................................................................................... 182
7A.6.2
Downlink transmissions ............................................................................................................................ 182
7A.6.3
Periodic uplink grants ............................................................................................................................... 183
7A.6.4
HARQ re-transmissions ............................................................................................................................ 184
7A.6.4.1
Uplink ................................................................................................................................................. 184
7A.6.4.2
Downlink ............................................................................................................................................. 184
7A.6.5
Timing info for UL messages ................................................................................................................... 185
7A.6.6
Uplink time alignment .............................................................................................................................. 185
7A.7
RRC Connection Release Sequence ............................................................................................................... 185
7A.8
DL CCCH Message and Contention Resolution MAC Control Element transmission in one MAC PDU
or in separate MAC PDUs .............................................................................................................................. 186
7A.9
Cell Configuration .......................................................................................................................................... 186
7A.9.1
Cell Power Change ................................................................................................................................... 186
7A.9.2
Timing Parameters of Cells ...................................................................................................................... 186
7A.9.3
Configuration of Multi-Cell Environment ................................................................................................ 187
7A.10
Timers and Timing Restrictions ..................................................................................................................... 187
7A.11
Error Indication .............................................................................................................................................. 187
8
External Function Definitions ..............................................................................................................187
9
IXIT Proforma ......................................................................................................................................190
9.1
9.2
9.3
E-UTRAN PIXIT ........................................................................................................................................... 190
MultiRAT PIXIT ............................................................................................................................................ 194
NB-IoT PIXIT ................................................................................................................................................ 198
10
Postambles............................................................................................................................................198
10.1
10.1.1
10.1.2
10.1.2.1
10.1.3
10.1.3.1
10.1.4
10.1.4.1
10.1.5
10.1.5.1
10.2
10.2.1
Postambles for E-UTRA to UTRA tests......................................................................................................... 198
UE postamble states and procedures for E-UTRA to UTRA.................................................................... 198
Switch/Power off procedure ..................................................................................................................... 200
Procedure ............................................................................................................................................ 200
CC disconnect procedure .......................................................................................................................... 202
Procedure ............................................................................................................................................ 202
PS Routing Area Update procedure .......................................................................................................... 203
Procedure ............................................................................................................................................ 203
CS fallback procedure ............................................................................................................................... 204
Procedure ............................................................................................................................................ 204
Postambles for E-UTRAN to GERAN tests ................................................................................................... 206
UE postamble states and procedures for E-UTRA to GERAN test cases ................................................. 206
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
10.2.2
10.2.2.1
10.2.3
10.2.3.1
10.2.4
10.2.4.1
10.2.5
10.2.5.1
10.3
10.3.1
10.3.2
10.3.2.1
10.3.3
10.3.3.1
10.3.3.2
10.3.4
10.3.4.1
10.3.5
10.3.5.1
10.4
10.4.1
10.4.1.1
10.4.1.2
10.5
10.5.1
10.5.2
10.5.2.1
10.5.3
10.5.3.1
10.5.4
10.5.4.1
10.5.5
10.5.5.1
11
8
ETSI TS 136 523-3 V13.2.0 (2017-03)
Switch/Power off procedure ..................................................................................................................... 208
Procedure ............................................................................................................................................ 208
PS Handover procedure ............................................................................................................................ 209
Procedure ............................................................................................................................................ 209
CC disconnect procedure .......................................................................................................................... 210
Procedure ............................................................................................................................................ 210
CS fallback procedure ............................................................................................................................... 210
Procedure ............................................................................................................................................ 210
Postambles for E-UTRA test cases ................................................................................................................. 211
UE postamble states and procedures for E-UTRA test cases.................................................................... 211
Switch/Power off procedure in State E1 ................................................................................................... 212
Procedure ............................................................................................................................................ 212
Switch/Power off procedure in State E2 and E3 ....................................................................................... 213
Procedure for E2 and E3 ..................................................................................................................... 213
Procedure for E2_T3440 ..................................................................................................................... 214
Switch/Power off procedure in State E4 ................................................................................................... 215
Procedure ............................................................................................................................................ 215
Automatic selection mode procedure in State E5 (current cell, neighbour cell) ....................................... 215
Procedure ............................................................................................................................................ 215
Postambles for E-UTRA to HRPD test cases ................................................................................................. 215
UE postamble procedures for E-UTRA to HRPD (No Pre-Registration) ................................................. 215
Registration on HRPD Cell ................................................................................................................. 215
Detach on HRPD Cell ......................................................................................................................... 217
Postambles for NB-IoT test cases................................................................................................................... 217
UE postamble states and procedures for NB-IoT test cases...................................................................... 217
Switch/Power off procedure in State N1................................................................................................... 218
Procedure ............................................................................................................................................ 218
Switch/Power off procedure in State N2 and N3 ...................................................................................... 218
Procedure for N2 and N3 .................................................................................................................... 218
Switch/Power off procedure in State N4................................................................................................... 218
Procedure ............................................................................................................................................ 218
Automatic selection mode procedure in State N5 (current cell, neighbour cell) ...................................... 219
Procedure ............................................................................................................................................ 219
Guidelines on test execution.................................................................................................................219
11.1
11.1.1
11.2
11.2.1
11.2.1.1
11.2.1.2
11.2.2
11.2.3
11.2.4
11.2.4.1
11.2.4.2
11.2.5
11.3
11.3.1
11.3.2
11.3.3
11.4
11.4.1
11.4.2
11.4.3
11.5
11.6
EUTRA single technology ............................................................................................................................. 219
Replacement of test case execution .......................................................................................................... 220
EUTRA - UTRA - GERAN ........................................................................................................................... 221
UTRA configured – GERAN not configured ........................................................................................... 221
EUTRA band overlapping UTRA band .............................................................................................. 221
EUTRA band not overlapping UTRA band ........................................................................................ 222
GERAN configured - UTRA not configured ............................................................................................ 223
Neither UTRA nor GERAN configured ................................................................................................... 224
Both UTRA and GERAN configured ....................................................................................................... 224
EUTRA band overlapping UTRA band .............................................................................................. 224
EUTRA band not overlapping UTRA band ........................................................................................ 225
Replacement of test case execution .......................................................................................................... 225
EUTRA inter-band ......................................................................................................................................... 225
Primary operating band ............................................................................................................................. 226
Secondary operating band for inter-band cells.......................................................................................... 226
Replacement of test case execution .......................................................................................................... 226
EUTRA CA .................................................................................................................................................... 226
CA contiguous Intra-band operation ......................................................................................................... 226
CA Inter-band operation ........................................................................................................................... 227
CA non-contiguous Intra-band operation ................................................................................................. 229
EUTRA MFBI ................................................................................................................................................ 229
EUTRA DC .................................................................................................................................................... 231
Annex A (normative):
Test Suites .....................................................................................................232
A.1
Baseline of specifications .....................................................................................................................232
A.2
E-UTRA Test Suites.............................................................................................................................232
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Annex B (informative):
9
ETSI TS 136 523-3 V13.2.0 (2017-03)
Style Guides ..................................................................................................251
B.1
Introduction ..........................................................................................................................................251
B.2
General Requirements for TTCN-3 Implementations ..........................................................................251
B.3
Naming Conventions ............................................................................................................................252
B.3.1
B.3.2
B.3.3
B.3.4
B.4
Prefixes and Restrictions for TTCN-3 Objects............................................................................................... 252
Void ................................................................................................................................................................ 253
Void ................................................................................................................................................................ 253
Identifiers consisting of more than one Name ................................................................................................ 253
Implementation Issues ..........................................................................................................................253
B.4.1
B.4.2
B.4.3
B.4.4
B.4.5
B.4.5.1
B.4.5.2
B.4.5.3
B.4.6
B.4.7
B.4.8
B.4.8.1
B.4.9
B.4.10
B.5
Control part .................................................................................................................................................... 253
Top Level Test Case Definitions .................................................................................................................... 253
Inter Component Communication .................................................................................................................. 254
Encoding Information..................................................................................................................................... 254
Verdict Assignment ........................................................................................................................................ 254
PASS verdict assignment .......................................................................................................................... 255
FAIL or INCONC verdict assignment ...................................................................................................... 255
Verdict assignment in default behaviour .................................................................................................. 256
Default Behaviour .......................................................................................................................................... 256
Templates for Sending and Receiving ............................................................................................................ 257
Logging .......................................................................................................................................................... 257
Prose Step Numbers .................................................................................................................................. 257
Top level comments ....................................................................................................................................... 258
Mapping of DRBs .......................................................................................................................................... 258
Modularisation .....................................................................................................................................258
Annex C (informative):
Design Principles ..........................................................................................260
C.1
ASP Design ..........................................................................................................................................260
C.2
SS State Model .....................................................................................................................................261
Annex D (informative):
D.1
TTCN-3 Definitions .....................................................................................264
EUTRA_ASP_TypeDefs......................................................................................................................264
D.1.1
D.1.2
D.1.3
D.1.3.1
D.1.3.2
D.1.3.2.1
D.1.3.2.2
D.1.3.2.3
D.1.3.3
D.1.3.4
D.1.3.5
D.1.3.6
D.1.3.7
D.1.3.8
D.1.3.8.1
D.1.3.8.2
D.1.3.9
D.1.3.10
D.1.3.11
D.1.4
D.1.5
D.1.5.1
D.1.5.2
D.1.5.3
D.1.6
D.1.7
ASN1_Container ............................................................................................................................................ 264
System_Configuration .................................................................................................................................... 273
Cell_Configuration ......................................................................................................................................... 276
Cell_Configuration_Common................................................................................................................... 277
Downlink_Physical_Layer_Configuration ............................................................................................... 281
Antenna_Configuration ....................................................................................................................... 282
Physical_Channels .............................................................................................................................. 283
Physical_Signals ................................................................................................................................. 285
Uplink_Physical_Layer_Configuration .................................................................................................... 286
Common_MAC_Configuration ................................................................................................................ 287
Random_Access_Procedure ..................................................................................................................... 294
System_Information_Control ................................................................................................................... 299
Paging_Control ......................................................................................................................................... 304
UE_Specific_Channel_Configuration ...................................................................................................... 304
UE_Specific_Channel_Configuration_DL ......................................................................................... 304
UE_Specific_Channel_Configuration_UL ......................................................................................... 305
Carrier_Aggregation ................................................................................................................................. 308
OCNG_Config .......................................................................................................................................... 310
EIMTA_Config......................................................................................................................................... 311
Cell_Power_Attenuation ................................................................................................................................ 311
Radio_Bearer_Configuration ......................................................................................................................... 312
PDCP_Configuration ................................................................................................................................ 312
RLC_Configuration .................................................................................................................................. 313
MAC_Configuration ................................................................................................................................. 315
AS_Security ................................................................................................................................................... 318
Semi_Persistent_Scheduling .......................................................................................................................... 320
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.1.8
D.1.9
D.1.10
D.1.11
D.1.12
D.1.13
D.1.14
D.1.15
D.1.16
D.1.17
D.1.18
D.1.19
D.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
Paging_Trigger ............................................................................................................................................... 322
L1_MAC_Indication_Control ........................................................................................................................ 322
Rlc_Indication_Control .................................................................................................................................. 323
PDCP_Count .................................................................................................................................................. 324
PDCP_Handover ............................................................................................................................................ 325
L1_MAC_Test_Mode .................................................................................................................................... 325
PDCCH_Order ............................................................................................................................................... 326
System_Indications ........................................................................................................................................ 326
System_Interface ............................................................................................................................................ 329
MBMS_Configuration.................................................................................................................................... 330
SCPTM_Configuration .................................................................................................................................. 333
DirectIndicationInfo_Trigger ......................................................................................................................... 335
EUTRA_ASP_DrbDefs........................................................................................................................335
D.2.1
D.2.2
D.3
10
MBMS_MRB_Primitive_Definitions ............................................................................................................ 335
System_Interface ............................................................................................................................................ 336
EUTRA_NB_ASP_L2DataDefs ..........................................................................................................337
D.3.1
PDU_TypeDefs .............................................................................................................................................. 337
D.3.1.1
MAC_PDU ............................................................................................................................................... 337
D.3.1.2
RLC_PDU................................................................................................................................................. 340
D.3.1.2.1
Common .............................................................................................................................................. 340
D.3.1.2.2
TM_Data ............................................................................................................................................. 341
D.3.1.2.3
UM_Data............................................................................................................................................. 341
D.3.1.2.4
AM_Data ............................................................................................................................................. 343
D.3.1.2.5
AM_Status .......................................................................................................................................... 345
D.3.1.3
PDCP ........................................................................................................................................................ 348
D.3.2
DRB_Primitive_Definitions ........................................................................................................................... 354
D.3.2.1
DRB_Common ......................................................................................................................................... 354
D.3.2.2
Downlink .................................................................................................................................................. 355
D.3.2.3
Uplink ....................................................................................................................................................... 356
D.4
EUTRA_ASP_SrbDefs ........................................................................................................................357
D.4.1
D.4.2
D.5
SRB_DATA_ASPs ........................................................................................................................................ 357
Port_Definitions ............................................................................................................................................. 359
IP_ASP_TypeDefs ...............................................................................................................................359
D.5.1
D.5.2
D.5.3
D.5.4
D.5.4.1
D.5.4.2
D.5.4.3
D.5.4.4
D.5.4.5
D.5.4.6
D.5.5
D.6
NasEmu_AspTypes_EUTRA ...............................................................................................................378
D.6.1
D.7
IP_Common ................................................................................................................................................... 359
IP_Config ....................................................................................................................................................... 361
IPsec_Config .................................................................................................................................................. 362
IP_SocketHandling......................................................................................................................................... 364
Socket_Common....................................................................................................................................... 364
Socket_Datagram ...................................................................................................................................... 365
TCP_Socket .............................................................................................................................................. 366
UDP_Socket ............................................................................................................................................. 371
ICMP_Socket ............................................................................................................................................ 373
Socket_Primitives ..................................................................................................................................... 375
System_Interface ............................................................................................................................................ 376
System_Interface ............................................................................................................................................ 379
EUTRA_CommonDefs ........................................................................................................................380
D.7.1
D.7.2
D.7.3
D.7.4
D.7.4.1
D.7.4.1.1
D.7.4.2
D.7.4.3
D.7.4.4
D.7.5
Common_Types ............................................................................................................................................. 380
Common_Constants ....................................................................................................................................... 380
RRC_Nested_Types ....................................................................................................................................... 381
ASP_CommonPart ......................................................................................................................................... 382
ASP_CommonPart_Definitions ................................................................................................................ 382
Routing_Info ....................................................................................................................................... 382
REQ_ASP_CommonPart .......................................................................................................................... 383
CNF_ASP_CommonPart .......................................................................................................................... 383
IND_ASP_CommonPart ........................................................................................................................... 383
MBMS_CommonDefs.................................................................................................................................... 383
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.8
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_ASP_TypeDefs ...............................................................................................................384
D.8.1
D.8.1.1
D.8.1.2
D.8.1.3
D.8.1.4
D.8.1.5
D.8.1.6
D.8.2
D.8.3
D.8.4
D.8.5
D.8.5.1
D.8.5.2
D.8.5.3
D.8.5.4
D.8.6
D.8.6.1
D.8.6.2
D.8.7
D.9
11
CDMA2000_Common ................................................................................................................................... 384
CDMA2000_SystemContants................................................................................................................... 384
CDMA2000_Routing................................................................................................................................ 384
CDMA2000_TimingInfo .......................................................................................................................... 385
CDMA2000_ReqAspCommonPart .......................................................................................................... 386
CDMA2000_IndAspCommonPart ........................................................................................................... 387
CDMA2000_CnfAspCommonPart ........................................................................................................... 387
CDMA2000_PowerLevel ............................................................................................................................... 388
CDMA2000_Data .......................................................................................................................................... 389
CDMA2000_CellConfiguration ..................................................................................................................... 391
CDMA2000_HRPD ....................................................................................................................................... 393
CDMA2000_PDN_Defs ........................................................................................................................... 393
CDMA2000_SubProtocols ....................................................................................................................... 394
HRPD_Indications .................................................................................................................................... 396
HRPD_Commands ................................................................................................................................... 399
CDMA2000_RTT1X...................................................................................................................................... 402
RTT1X_Indications .................................................................................................................................. 402
RTT1X_Commands .................................................................................................................................. 405
System_Interface ............................................................................................................................................ 407
CDMA2000_CommonDefs..................................................................................................................410
D.10 EUTRA_ASP_CDMA2000TunnellingDefs ........................................................................................414
D.11 EUTRA_ASP_VirtualNoiseDefs .........................................................................................................415
D.12 UTRAN_ASP_VirtualNoiseDefs .........................................................................................................416
D.13 WLAN_ASP_TypeDefs .......................................................................................................................417
D.14 SideLinkUE_ASP_TypeDefs ...............................................................................................................429
D.14.1
SideLinkUE_Data .......................................................................................................................................... 429
D.14.2
SideLinkUE_Configuration............................................................................................................................ 431
D.14.2.1
SL_Routing_Timing ................................................................................................................................. 431
D.14.2.2
SL_SystemRequestAsp ............................................................................................................................. 433
D.14.2.2.1
SL_RequestAspCommon_Part............................................................................................................ 433
D.14.2.2.2
Discovery_Specific ............................................................................................................................. 436
D.14.2.2.3
Communication_Specific .................................................................................................................... 438
D.14.2.2.4
SL_Security......................................................................................................................................... 444
D.14.2.3
SL_SystemConfirmAsp ............................................................................................................................ 445
D.14.2.4
SL_SystemIndicationAsp ......................................................................................................................... 445
D.14.2.5
SL_System_Interface ................................................................................................................................ 447
D.15 CommonDefs .......................................................................................................................................448
D.16 EUTRA_NB_ASP_TypeDefs ..............................................................................................................451
D.16.1
Cell_Configuration ......................................................................................................................................... 451
D.16.1.1
Cell_Configuration_Common................................................................................................................... 451
D.16.1.2
Uplink_Physical_Layer_Configuration .................................................................................................... 452
D.16.1.3
Common_MAC_Configuration ................................................................................................................ 452
D.16.1.4
Random_Access_Procedure ..................................................................................................................... 454
D.16.2
System_Indications ........................................................................................................................................ 456
D.17 EUTRA_NB_CommonDefs .................................................................................................................456
D.17.1
Common_Types ............................................................................................................................................. 456
D.17.2
RRC_Nested_Types ....................................................................................................................................... 457
D.17.3
ASP_CommonPart ......................................................................................................................................... 457
D.17.3.1
ASP_CommonPart_Definitions ................................................................................................................ 457
D.17.3.1.1
Routing_Info ....................................................................................................................................... 457
D.17.3.1.2
Timing_Info ........................................................................................................................................ 457
D.17.3.2
REQ_ASP_CommonPart .......................................................................................................................... 458
D.17.3.3
CNF_ASP_CommonPart .......................................................................................................................... 458
D.17.3.4
IND_ASP_CommonPart ........................................................................................................................... 459
D.17.4
L2Data_CommonDefs.................................................................................................................................... 459
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
12
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.18 References to TTCN-3 .........................................................................................................................461
Annex E (informative):
Upper Tester Scenarios ...............................................................................462
E.1
No confirmation ...................................................................................................................................462
E.2
Immediate confirmation .......................................................................................................................462
E.3
Late response ........................................................................................................................................464
E.4
Multiple responses................................................................................................................................465
Annex F (informative):
F.1
NBIOT_ASP_TypeDefs.......................................................................................................................468
F.1.1
F.1.2
F.1.3
F.1.3.1
F.1.3.2
F.1.3.2.1
F.1.3.2.2
F.1.3.3
F.1.3.4
F.1.3.5
F.1.3.6
F.1.3.7
F.1.3.8
F.1.3.8.1
F.1.3.8.2
F.1.4
F.1.5
F.1.5.1
F.1.5.2
F.1.6
F.1.7
F.1.8
F.1.9
F.1.10
F.1.11
F.2
F.2.1
F.2.2
F.3
F.3.1
F.4
TTCN-3 Definitions .....................................................................................468
ASN1_Container ............................................................................................................................................ 468
System_Configuration .................................................................................................................................... 469
Cell_Configuration ......................................................................................................................................... 472
Cell_Configuration_Common................................................................................................................... 472
Downlink_Physical_Layer_Configuration ............................................................................................... 474
Physical_Channels .............................................................................................................................. 474
Physical_Signals ................................................................................................................................. 477
Uplink_Physical_Layer_Configuration .................................................................................................... 478
Common_MAC_Configuration ................................................................................................................ 479
Random_Access_Procedure ..................................................................................................................... 482
System_Information_Control ................................................................................................................... 485
Paging_Control ......................................................................................................................................... 487
UE_Specific_Channel_Configuration ...................................................................................................... 487
UE_Specific_Channel_Configuration_DL ......................................................................................... 487
UE_Specific_Channel_Configuration_UL ......................................................................................... 488
Cell_Power_Attenuation ................................................................................................................................ 489
Radio_Bearer_Configuration ......................................................................................................................... 489
RLC_Configuration .................................................................................................................................. 489
MAC_Configuration ................................................................................................................................. 490
AS_Security ................................................................................................................................................... 493
Paging_Trigger ............................................................................................................................................... 494
RLC_Counts ................................................................................................................................................... 495
PDCP_Count .................................................................................................................................................. 495
L1_MAC_Test_Mode .................................................................................................................................... 497
System_Interface ............................................................................................................................................ 497
NBIOT_ASP_SrbDefs .........................................................................................................................498
SRB_DATA_ASPs ........................................................................................................................................ 498
Port_Definitions ............................................................................................................................................. 500
NBIOT_ASP_L2DataDefs ...................................................................................................................500
System_Interface ............................................................................................................................................ 500
EUTRA_NB_ASP_L2DataDefs ..........................................................................................................501
F.4.1
PDU_TypeDefs .............................................................................................................................................. 501
F.4.1.1
MAC_PDU ............................................................................................................................................... 501
F.4.1.2
RLC_PDU................................................................................................................................................. 504
F.4.1.2.1
Common .............................................................................................................................................. 504
F.4.1.2.2
TM_Data ............................................................................................................................................. 505
F.4.1.2.3
UM_Data............................................................................................................................................. 505
F.4.1.2.4
AM_Data ............................................................................................................................................. 507
F.4.1.2.5
AM_Status .......................................................................................................................................... 509
F.4.1.3
PDCP ........................................................................................................................................................ 512
F.4.2
DRB_Primitive_Definitions ........................................................................................................................... 518
F.4.2.1
DRB_Common ......................................................................................................................................... 518
F.4.2.2
Downlink .................................................................................................................................................. 519
F.4.2.3
Uplink ....................................................................................................................................................... 520
F.5
F.5.1
NasEmu_AspTypes_NBIOT ................................................................................................................521
System_Interface ............................................................................................................................................ 521
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
F.6
13
ETSI TS 136 523-3 V13.2.0 (2017-03)
NBIOT_CommonDefs .........................................................................................................................523
F.6.1
NBIOT_Common_Types ............................................................................................................................... 523
F.6.2
NBIOT_RRC_Nested_Types ......................................................................................................................... 524
F.6.3
NBIOT_ASP_CommonPart ........................................................................................................................... 524
F.6.3.1
NBIOT_ASP_CommonPart_Definitions .................................................................................................. 524
F.6.3.1.1
NBIOT_Routing_Info ......................................................................................................................... 524
F.6.3.2
REQ_ASP_CommonPart .......................................................................................................................... 525
F.6.3.3
NBIOT_CNF_ASP_CommonPart ............................................................................................................ 525
F.6.3.4
NBIOT_IND_ASP_CommonPart............................................................................................................. 526
F.7
NBIOT_Imported_EUTRA_ASN1_Types ..........................................................................................526
F.8
CommonDefs .......................................................................................................................................526
F.9
EUTRA_NB_ASP_TypeDefs ..............................................................................................................527
F.9.1
F.9.1.1
F.9.1.2
F.9.1.3
F.9.1.4
F.9.2
Cell_Configuration ......................................................................................................................................... 527
Cell_Configuration_Common................................................................................................................... 527
Uplink_Physical_Layer_Configuration .................................................................................................... 528
Common_MAC_Configuration ................................................................................................................ 528
Random_Access_Procedure ..................................................................................................................... 529
System_Indications ........................................................................................................................................ 531
F.10 EUTRA_NB_CommonDefs .................................................................................................................532
F.10.1
Common_Types ............................................................................................................................................. 532
F.10.2
RRC_Nested_Types ....................................................................................................................................... 532
F.10.3
ASP_CommonPart ......................................................................................................................................... 532
F.10.3.1
ASP_CommonPart_Definitions ................................................................................................................ 532
F.10.3.1.1
Routing_Info ....................................................................................................................................... 532
F.10.3.1.2
Timing_Info ........................................................................................................................................ 532
F.10.3.2
REQ_ASP_CommonPart .......................................................................................................................... 534
F.10.3.3
CNF_ASP_CommonPart .......................................................................................................................... 534
F.10.3.4
IND_ASP_CommonPart ........................................................................................................................... 534
F.10.4
L2Data_CommonDefs.................................................................................................................................... 535
F.11 References to TTCN-3 .........................................................................................................................537
Annex G (informative):
Change history .............................................................................................538
History ............................................................................................................................................................634
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
14
ETSI TS 136 523-3 V13.2.0 (2017-03)
Foreword
This Technical Specification (TS) has been produced by ETSI 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.
Introduction
The present document is part 3 of a multi-part conformance test specification for the 3GPP evolved User Equipment
(UE). The specification contains a TTCN-3 design frame work and the detailed test specifications in TTCN-3 for
evolved UE at the UE-E-UTRAN radio interface.
-
3GPP TS 36.523-1 [1]: "User Equipment (UE) conformance specification; Part 1: Protocol conformance
specification".
-
3GPP TS 36.523-2 [2]: "User Equipment (UE) conformance specification; Part 2: Implementation Conformance
Statement (ICS) proforma specification".
-
3GPP TS 36.523-3: "Test Suites" (the present document).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
1
15
ETSI TS 136 523-3 V13.2.0 (2017-03)
Scope
The present document specifies the protocol and signalling conformance testing in TTCN-3 for the 3GPP UE at the
UE-E-UTRAN radio interface.
The following TTCN test specification and design considerations can be found in the present document:
-
the test system architecture;
-
the overall test suite structure;
-
the test models and ASP definitions;
-
the test methods and usage of communication ports definitions;
-
the test configurations;
-
the design principles and assumptions;
-
TTCN styles and conventions;
-
the partial PIXIT proforma;
-
the test suites.
The Abstract Test Suites designed in the document are based on the test cases specified in prose
(3GPP TS 36.523-1 [1]). The applicability of the individual test cases is specified in the test ICS proforma specification
(3GPP TS 36.523-2 [1]).
The present document is valid for TTCN development for LTE, LTE-Advanced and LTE-Advanced Pro (including NBIoT) UE conformance test according to 3GPP Releases starting from Release 8 up to the Release indicated on the cover
page of the present document.
In the remainder of the present document, unless explicitly stated otherwise, the term E-UTRA(N) implicitly refers to
the Wideband part of E-UTRA(N) known as WB-E-UTRA(N). The Narrowband part of E-UTRA(N) is always
explicitly referred to as NB-IoT.
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 unless the context in which the reference is made suggests a different Release is
relevant (information on the applicable release in a particular context can be found in e.g. test case title,
description or applicability, message description or content).
[1]
3GPP TS 36.523-1: "User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification".
[2]
3GPP TS 36.523-2: "User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
[3]
3GPP TS 36.508: "Common test environments for User Equipment (UE) conformance testing".
[4]
3GPP TS 36.509: "Terminal logical test interface; Special conformance testing functions".
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
16
ETSI TS 136 523-3 V13.2.0 (2017-03)
[5]
3GPP TS 34.123-1: "User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification".
[6]
3GPP TS 34.123-2: "User Equipment (UE) conformance specification; Part 2: Implementation
Conformance Statement (ICS) proforma specification".
[7]
3GPP TS 34.123-3: "User Equipment (UE) conformance specification; Part 3: Abstract Test Suite
(ATS)".
[8]
3GPP TS 34.108: "Common test environments for User Equipment (UE) conformance testing".
[9]
3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions".
[10]
3GPP TS 51.010-1: "Mobile Station (MS) conformance specification; Part 1: Conformance
Specification".
[11]
3GPP TS 51.010-2: "Mobile Station (MS) conformance specification; Part 2: Protocol
Implementation Conformance Statement (PICS) proforma specification".
[12]
3GPP TS 51.010-5: "Mobile Station (MS) conformance specification; Part 5: Inter-RAT (GERAN
to UTRAN) Abstract Test Suite (ATS)".
[13]
ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Tree and Tabular
Combined Notation version 3; Part 1: TTCN-3 Core Language".
[14]
3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); "UE Procedures in Idle
Mode".
[15]
3GPP TS 36.306 "Evolved Universal Terrestrial Radio Access (E-UTRA); "UE Radio Access
Capabilities".
[16]
3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); "Medium Access
Control (MAC) protocol specification".
[17]
3GPP TS 36.322:"Evolved Universal Terrestrial Radio Access (E-UTRA); "Radio Link Control
(RLC) protocol specification".
[18]
3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); "Packet Data
Convergence Protocol (PDCP) Specification".
[19]
3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource
Control (RRC); Protocol Specification".
[20]
3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols;
Stage 3".
[21]
3GPP TS 24.301: "Non-Access-Stratum (NAS) Protocol for Evolved Packet System (EPS);
Stage 3".
[22]
3GPP TS 24.303: "Mobility Management based on DSMIPv6; User Equipment (UE) to network
protocols; Stage 3".
[23]
3GPP TS 24.304: "Mobility management based on Mobile IPv4; User Equipment (UE) – foreign
agent interface; Stage 3".
[24]
3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[25]
3GPP TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP
accesses".
[26]
3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[27]
ETSI ES 201 873-4: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 4: TTCN-3 Operational Semantics".
[28]
ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)".
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
17
ETSI TS 136 523-3 V13.2.0 (2017-03)
[29]
ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[30]
3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures".
[31]
3GPP TS 27.005: "Use of Data Terminal Equipment – Data Circuit terminating Equipment
(DTE-DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
[32]
3GPP TS 27.007: "AT command set for 3G User Equipment (UE)".
[33]
3GPP TS 27.060: "Packet domain; Mobile Station (MS) supporting Packet Switched services".
[34]
3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception".
[35]
3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
modulation".
[36]
3GPP TS 25.331: "RRC Protocol Specification".
[37]
3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".
[38]
3GPP2 TSG-C C.S0024_C v2.0: "cdma2000 High Rate Packet Data Air Interface Specification".
[39]
3GPP2 TSG-C C.S0057-E v1.0: "Band Class Specification for cdma2000 Spread Spectrum
Systems".
[40]
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".
[41]
3GPP TS 33.203: "3G security; Access security for IP-based services".
[42]
3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP); Stage 3".
[43]
IETF RFC 3320: "Signalling Compression (SigComp)".
[44]
IETF RFC 3485: "The Session Initiation Protocol (SIP) and Session Description Protocol (SDP)
Static Dictionary for Signalling Compression (SigComp)".
[45]
IETF RFC 3486: "Compressing the Session Initiation Protocol (SIP)".
[46]
IETF RFC 4896: "Signalling Compression (SigComp) Corrections and Clarifications".
[47]
IETF RFC 5049: "Applying Signalling Compression (SigComp) to the Session Initiation Protocol
(SIP)".
[48]
3GPP TS 23.003: "Numbering, addressing and identification".
[49]
3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".
[50]
3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN)".
[51]
3GPP TS 34.229-3: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE)
conformance specification; Part 3: Abstract Test Suite ".
[52]
3GPP TS 37.571-4: “User Equipment (UE) conformance specification for UE positioning; Part 4:
Test Suites”
[53]
3GPP TS 36.214: " Evolved Universal Terrestrial Radio Access (E-UTRA);Physical layer;
Measurements".
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
18
ETSI TS 136 523-3 V13.2.0 (2017-03)
[54]
IETF RFC 1144: "Compressing TCP/IP headers for low-speed serial links".
[55]
IETF RFC 2507: "IP Header Compression".
[56]
ITU-T Recommendation V.42bis: "Data compression procedures for data circuit-terminating
equipment (DCE) using error correction procedures".
[57]
ITU-T Recommendation V.44: "Data compression procedures".
[58]
IETF RFC 1035: "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION"
[59]
IETF RFC 3596: "DNS Extensions to Support IP Version 6"
[60]
ITU-T Recommendation V.250: " Serial asynchronous automatic dialling and control"
[61]
3GPP TS 24.334: "Proximity-service (ProSe) User Equipment (UE) to ProSe function protocol
aspects; Stage 3"
[62]
3GPP TS 25.307: "Requirements on User Equipments (UEs) supporting a release-independent
frequency band"
[63]
3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses"
[64]
IETF RFC 5996: "Internet Key Exchange Protocol Version 2 (IKEv2)".
[65]
IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets".
[66]
IETF RFC 4187 (January 2006): "Extensible Authentication Protocol Method for 3rd Generation
Authentication and Key Agreement (EAP-AKA)".
[67]
3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access
networks"
3
Definitions and abbreviations
3.1
Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [26] apply.
3.2
Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [26] apply.
4
E-UTRAN/SAE system architecture and test models
4.1
Test system architecture
4.1.1
General system architecture
The general system architecture is shown in figure 4.1.1-1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
19
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test control, Logging
TTCN-3
generated code
Codec
System Simulator HW
System Adaptor (SA)
Platform Adaptor (PA)
Protocol layers
internal interface
System
dependent
Host-PC
layers
System
dependent
layers
internal interface
UE
air interface
Figure 4.1.1-1: Architecture of system simulator
The scope of the present document is the TTCN-3 implementation of conformance tests. Specifications and definitions
of the present document affect the codec and the system adaptor (SA). Test control and logging are out of scope as well
as the interface between the TTCN-3 generated code and the system adaptor which can be either standardised TRI or
proprietary.
The main assumptions regarding the system architecture are:
-
TTCN-3 code runs on the host system only:
-
No TTCN-3 components are downloaded to system simulator HW.
-
Layer 2 tests (MAC, RLC) are controlled by appropriate configuration primitives in TTCN-3 but neither
layer 2 nor parts of it are implemented in TTCN-3; the system simulator performs low layer procedure
autonomously but all system simulator implementations shall result in the same test pattern at the air
interface.
-
Proprietary interfaces e.g. instead of the TRI are not considered in the test model.
-
The timing considerations of the conformance tests shall be supported by appropriate timing information
(e.g. system frame number) provided from/to the system simulator rather than by timing measurements in
TTCN-3.
4.1.2
Component architecture
For E-UTRAN conformance tests each access technology (RAT) is hosted by a separate TTCN-3 parallel component
(PTC):
-
E-UTRAN.
-
UTRAN.
-
GERAN.
-
Other technologies like 3GPP2 UTRAN.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
20
ETSI TS 136 523-3 V13.2.0 (2017-03)
The PTCs are controlled by the TTCN-3 master test component (MTC) which:
-
is independent from the RAT;
-
may host the upper tester for MMI and AT commands;
-
creates, synchronises and terminates the PTCs;
-
starts and terminates test cases.
Figure 4.1.2-1 shows this component architecture for a E-UTRAN and UTRAN scenario.
MTC:
Synchronisation
Upper Tester
at/mmi commands
PTC: E-UTRAN
at/mmi
commands
Config data,
status info
system interface
PTC: UTRAN
Coordination
messages
...
Config data,
status info
...
Adaptation Layer
Data PDUs
Config and
Control
UE
Protocol
Stack
System
Simulator
Figure 4.1.2-1:E-UTRAN-UTRAN component model
According to this model there are different interfaces to be considered:
MTC - PTC:
-
common synchronisation of PTCs;
-
upper tester primitives.
MTC - System Interface:
-
upper tester primitives.
PTC - PTC:
-
primitives containing information for IRAT handover.
PTC - System Interface:
-
primitives containing peer-to-peer message;
-
configuration primitives.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2
E-UTRAN test models
4.2.1
Layer 2 test models
21
ETSI TS 136 523-3 V13.2.0 (2017-03)
When test loop mode is used for the Layer 2 tests the DRB ports at the SS side is referred to the raw DRB ones. At the
SS side, DRBs are initially configured with default modes and parameters. For the purpose of L2-testing the DRBs may
be reconfigured later on as indicated in the subsequent test models (see below).
4.2.1.1
MAC test model
TTCN CODE
SRB0-SRB2
DRB
DRB
TM
TM
Config/Contro
l
RLC
DTCH
DTCH
MAC
PHY
Loopback above PDCP in UE
Figure 4.2.1.1-1: Test model for MAC testing
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. On UE side Ciphering
is enabled (since Mandatory) but with dummy ciphering algorithm, which is equivalent to not using ciphering. ROHC is
not configured on UE Side.
On the SS Side, Layer 1 is configured in the normal way. MAC is configured in a special mode, where it does not add
any MAC headers in DL and /or not remove any MAC headers in UL directions respectively at DRB port. In this case,
the TTCN shall provide the final PDU, including padding. Except for this, the MAC layer shall perform all of its other
functions.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
22
ETSI TS 136 523-3 V13.2.0 (2017-03)
On DRBs the RLC is configured in transparent mode. Hence with this configuration PDU's out of SS RLC are same as
the SDU's in it. There is no PDCP configured on SS Side. The ports are directly above RLC.
There are two different test modes in which MAC header addition/removal can be configured:
DL/UL header-transparent mode: no header addition in DL and no header removal in UL.
DL only header-transparent mode: no header addition in DL; UL MAC is configured in normal mode to remove
MAC header and dispatch the MAC SDUs according to the logical channel Ids.
If SS MAC is configured in DL/UL header-transparent mode, the PDU's exchanged at the DRB port between TTCN
and SS, shall be the final MAC PDU's consisting of MAC, RLC and PDCP headers. TTCN code shall take care in DL
of building MAC header, RLC headers and PDCP headers and in UL handle MAC, RLC and PDCP headers. TTCN
code shall take care of maintaining sequence numbers and state variables for RLC and PDCP layers. During testing of
multiple DRBs at the UE side, it shall still be possible to configure only one DRB on SS side with configuration in the
figure 4.2.1.1-1. Other DRBs will not be configured, to facilitate routing UL TBSs. Multiplexing/de-multiplexing of
PDUs meant/from different DRBs shall be performed in TTCN. Since the MAC layer does not evaluate the MAC
headers in UL it cannot distinguish between SRB and DRB data in UL. Therefore there shall be no SRB traffic while
MAC is configured in this test mode. The SS MAC shall take care of automatic repetitions in UL and DL, based on
normal MAC HARQ behaviour.
If SS MAC is configured in DL only header-transparent mode, the UL PDUs exchanged at the DRB port between
TTCN and SS, shall be final RLC PDUs consisting of RLC and PDCP headers. SS shall route these PDUs based on
logical channel IDs. In DL, TTCN sends fully encoded MAC PDUs at the DRB port (consisting of MAC, RLC and
PDCP headers). In this case TTCN needs to take care of maintaining sequence numbers and state variables for RLC and
PDCP layers. Furthermore in UL and DL the SS MAC layer shall be capable of dealing with SRB data (i.e. it shall
handle DL RLC PDUs coming from SRBs RLC layer or dispatch UL RLC PDUs to SRBs) as in normal mode. The SS
MAC shall take care of automatic repetitions in UL and DL, based on normal MAC HARQ behaviour.
NOTE:
TTCN shall ensure that no DL MAC SDUs in normal mode and DL MAC PDUs in test mode are mixed
for the same TTI.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception over system indication port, if configured. In a similar way the
reception of RACH preambles is reported by SS over the same port.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.1.2
23
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC test model
TTCN CODE
SRB0-SRB2
DRB
DRB
TM
TM
Config/Contro
l
RLC
DTCH
DTCH
MAC
PHY
Loopback above PDCP in UE
Figure 4.2.1.2.3-1: Test model for RLC AM/UM testing
This model is suitable for testing both UM/AM mode of operation of DRBs on UE side.
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. On UE side Ciphering
is enabled (since mandatory) but with dummy ciphering algorithm, which is equivalent to not using ciphering. ROHC is
not configured on UE Side.
On the SS Side, L1 and MAC are configured in the normal way. The RLC is configured in transparent mode. Hence
with this configuration PDUs out of SS RLC are same as the SDUs in it. There is no PDCP configured on SS Side. The
ports are directly above RLC.
The PDUs exchanged between TTCN and SS, shall be the final RLC PDUs consisting of RLC and PDCP headers.
TTCN code shall take care in DL of building RLC headers and PDCP headers and in UL handle RLC and PDCP
headers. TTCN code shall take care of maintaining sequence numbers and state variables for RLC and PDCP layers. If
RLC on UE side is in AM mode, TTCN shall take care of generating polls in DL and responding with RLC control
PDUs on reception of UL Poll.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.1.3
4.2.1.3.1
24
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP test model
PDCP ROHC test model
TTCN CODE
PDCP PDU
SRB0-SRB2
DRB
DRB
Config/Contro
l
UL Feedback
injected by CASP
ROHC
PDCP
Ciphering
Ciphering
RLC
AM/UM
AM/UM
DTCH
DTCH
MAC
PHY
Loopback above PDCP in UE
Figure 4.2.1.3.1-1: Test model for PDCP ROHC testing
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. On UE side Ciphering
is enabled and ROHC is configured.
On the SS Side L1, MAC and RLC are configured in normal way. They shall perform all of their functions. The ports
are above PDCP.
The PDCP is configured in special mode, with no header manipulation. Ciphering is configured in both directions.
ROHC is configured in DL direction only. UL ROHC feedback can be injected by control ASP. It shall be possible to
configure 'no header manipulation' mode independently in UL and DL directions. When configured in special mode, SS
shall not add PDCP header (DL) and remove PDCP Header (UL). PDCP state variables shall be maintained by SS
PDCP layer. It shall be possible for SS PDCP to update state variables based on the PDU's in both directions, even
though headers are not added/removed. Also, it shall be possible to read or set the PDCP internal state variables, by
control primitives.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception over system indication port, if configured.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.1.3.2
25
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP test model (Non ROHC)
TTCN CODE
PDCP PDU
SRB0-SRB2
Ciphering
Ciphering
DRB
DRB
PDCP
PDCP
AM/UM
AM/UM
Config/Contro
l
PDCP
RLC
DTCH
DTCH
MAC
PHY
Loopback above PDCP in UE
Figure 4.2.1.3.2-1: Test model for PDCP (Non ROHC) testing
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. On UE side Ciphering
is enabled and ROHC is not configured.
On the SS Side L1, MAC and RLC are configured in normal way. They shall perform all of their functions. The ports
are above PDCP.
The PDCP is configured in a special mode, named transparent mode. In this mode, SS shall not add PDCP header (DL)
and remove PDCP Header (UL). The TTCN maintains sequence numbers and state variables for the PDCP layer. The
TTCN makes use of the AS ciphering functionality in both directions, employing the dummy ciphering algorithm.
Ciphering/deciphering are performed using TTCN external functions. ROHC is not configured.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception over system indication port, if configured.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.2
26
ETSI TS 136 523-3 V13.2.0 (2017-03)
RRC test model
TTCN CODE
Control
SRB0
SRB1
NAS Integrity &
Ciphering
SRB2
DRB
RRC/NAS Emulator
Integrity
Integrity
Ciphering
Ciphering
Ciphering
AM
AM
AM/UM
PDCP
RLC
TM
CCCH
DCCH
DCCH
DTCH
MAC
PHY
UE Operation in Normal Mode
Figure 4.2.2-1: Test model for RRC testing
The UE is configured in normal mode. On UE side Ciphering/Integrity (PDCP and NAS) is enabled and ROHC is not
configured.
On the SS Side L1, MAC, RLC and PDCP are configured in normal way. They shall perform all of their functions. For
SRB0 the DL and UL port is above RLC. For SRB1 and SRB2 the port is above/below the RRC and NAS emulator,
which may be implemented as a parallel test component. For DRB, the port is above PDCP. PDCP Ciphering/Integrity
is enabled. NAS integrity/Ciphering is enabled.
The RRC/NAS emulator for SRB1 and SRB2 shall provide the Ciphering and integrity functionality for the NAS
messages. In UL direction, SS shall report RRC messages, still containing (where appropriate) the secure and encoded
NAS message, to the RRC port. In DL, RRC and NAS messages with same timing information shall be embedded in
one PDU after integrity and ciphering for NAS messages.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception over system indication port, if configured.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.3
27
ETSI TS 136 523-3 V13.2.0 (2017-03)
DRB test model
TTCN CODE
SRB0-SRB2
DRB
DRB
Ciphering
Ciphering
PDCP
RLC
AM/UM
AM/UM
DTCH
DTCH
MAC
PHY
Loopback above PDCP in UE
Figure 4.2.3-1: Test model for DRB testing
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. Ciphering is optionally
configured on UE side. In TTCN the DRB data is considered as raw data and there is no IP handling while the UE is in
loopback mode.
On the SS Side L1, MAC, RLC and PDCP are configured in normal way. They shall perform all of their functions. The
ports are above PDCP. When test loop mode is used for the DRB, the ports at the SS side refer to the raw DRB ones.
Ciphering is enabled and ROHC is not configured on SS Side.
SS shall send in DL all PDU's received from different RB's but with same timing control information in one MAC PDU
and in one TTI.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception over system indication port, if configured.
4.2.4
IP Test Model
Depending on different test scenarios user plane data can be distinguished in:
-
Raw user data upon EUTRA PDCP (Raw mode);
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
28
ETSI TS 136 523-3 V13.2.0 (2017-03)
IP user data (IP mode).
The raw user data are applied for L2 or DRB tests, no IP protocols are involved. The UL user data is directly routed to
the EUTRA_PTC.
The IP user data are applied when IP packets data are discarded, looped back or handled in TTCN. A DRB can have
one or more Transport and Internet protocols configured.
Whether a DRB is in IP or in raw mode depends on the configuration of the routing table in the DBR-Mux. This is
controlled by the IP_CTRL port and independent from the configuration of the IP connections (IP_SOCKET).
4.2.4.1
IP user data
To allow the usage of common protocol implementations at the system adaptor the related interfaces in TTCN-3 are
based on the Sockets API.
There can be one or several sockets (server or client) for each DRB: TCP, UDP and ICMP.
Each socket can be clearly identified by the IP address, port number and the protocol (tcp|udp\icmp). It implies that a
TCP socket can be either server or client.
It is assumed that:
-
Different DRBs are not using the same sockets.
-
The UE behaviour of a single IP-based protocol on a specific socket like DHCP can be included in conformance
tests.
-
Other protocols like ESP are not considered but can easily be introduced later, if necessary, by using the same
socket approach.
The routing of IP packets from the IP stack to the DRBs in DL, and from the DRBs either to the DRB port (E_DRB in
case of EUTRA) or to the IP stack or discard/loopback in UL is done by the DRB-Mux. This behaviour is controlled by
the DRB-Mux's routing table.
The general architecture of the IP test model is shown in figure 4.2.4.1-1 (with a DHCP server as example for IP
handling).
NOTE:
In figure 4.2.4.1-1 DHCP is one example for a protocol above the IP stack; other protocols like DNS can
also be implemented but this a pure TTCN implementation issue and independent from the system
interface.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
29
ETSI TS 136 523-3 V13.2.0 (2017-03)
EUTRA_PTC
IP_PTC
IP Data
DATA
IP_DATA
DHCP Server
test case relevant
IP Data
CTRL
CTRL
IP_CTRL
DHCP
Data
CTRL
Socket
Control
Routing
Control
MUX/Filter
Socket
Ctrl
IP-Data
IP_SOCK
DRB
L2 Data
IP_CTRL
IP Data,
Socket Ctrl
System Interface
E_DRB
IP_SOCK
IP-Data
IP_CTRL
Socket
Ctrl
Routing
Ctrl
IP stack
raw mode
IP mode
DRB-MUX
EUTRA:
Cellx, DRBy
UTRAN:
Cellx, RBy
Routing
Table
GERAN
System Adaptor
Figure 4.2.4.1-1: Example of EUTRA IP test model with a DHCP server
4.2.4.2
Configuration of Sockets
The following configurations are controlled by the IP_PTC (IP_SOCKET_REQ). The socket configuration and the
sending/receiving of data are done with the same ASP on the system port IP_SOCK.
4.2.4.2.1
Socket Establishment
TCP server
TCP socket configured as server: the socket 'listens' to a 'connect' from the UE. The socket can be configured by using
the following system calls of the Berkeley Sockets API:
-
socket (AF_INET | AF_INET6, SOCK_STREAM, 0);
-
setsockopt;
-
bind (local IP address Port);
-
listen.
NOTE:
Currently the only socket option being defined is SO_BROADCAST
When the UE connects to the server the connection is accepted with the 'accept' system call.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
30
ETSI TS 136 523-3 V13.2.0 (2017-03)
TCP client
A TCP connection is established to an existing TCP server at the UE side. This can be done with the following system
calls:
-
socket (AF_INET|AF_INET6, SOCK_STREAM, 0);
-
setsockopt;
-
connect (remote Server Addr of the UE = IP-Addr + Port).
UDP socket
A UDP socket can be established with the system calls
-
socket (AF_INET|AF_INET6, SOCK_DGRAM, 0);
-
setsockopt;
-
bind (local IP address, Port);
-
connect.
NOTE 1: 'setsockopt' can be used to set the option SO_BROADCAST to allow broadcast messages (e.g. for
DHCP).
NOTE 2: Usage of 'connect' depends on implementation of the system adaptor.
4.2.4.2.2
Socket Release
A socket is released:
-
in case of TCP when the remote entity closes the connection;
-
when it is closed explicitly by the IP_PTC (system call 'close').
NOTE 1: In general the sockets are independent from the configuration of the DRBs. Especially in case of UDP or
ICMP the sockets can exist even without any DRB being configured.
NOTE 2: For IMS, TCP close happens for unprotected ports after initial registration and for protected ports after
deregistration or re-registration: Any protected TCP connections are kept as long as the UE is registered
independent of whether the RRC connection is released in between. In general TCP close is expected to
be done from the client’s end.
In detail
- after initial registration TTCN waits ΔT seconds for the UE to close any TCP connection on the
unprotected port
- after de-registration TTCN waits ΔT seconds for the UE to close its client TCP connection; after this is
done the TTCN closes any remaining TCP connection (independently of the server/client role)
- after re-registration when there is a new security context TTCN waits ΔT seconds for the UE to close its
client TCP connection of the old security context.
- as special case after an emergency call the same procedure is applied as for de-registration
ΔT is 3s.
4.2.4.3
Handling of IP data
Sending and receiving of IP data is done by the same ASPs as the socket establishment on IP_SOCK. In TTCN the IP
data are handled by a separate TTCN component: IP_PTC. This PTC can deal with the data according to the respective
protocol, e.g. DHCP. In general, this is out of scope for the (signalling conformance) test case in terms of pass/fail
assignment.
The IP_PTC will receive data from sockets being configured for the corresponding IP protocols. Any unrecognised IP
packets are discarded by the IP stack in the system adaptor.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
31
ETSI TS 136 523-3 V13.2.0 (2017-03)
When the IP data is relevant for the test purpose, e.g. the test purpose is to test DHCP, the IP data are routed to the
EUTRA_PTC. This allows generic protocol implementations for the common case, i.e. IP_PTC and DHCP server are
independent from test case specific implementations.
The interface between EUTRA_PTC and IP_PTC is a pure TTCN implementation issue and independent of the system
interface. Furthermore it is irrelevant for the system interface whether e.g. the DHCP server is part of the IP_PTC or
implemented as a separate PTC.
-
For TCP, the primitives to send and receive data correspond to the 'send' and 'recv' system calls.
-
For UDP and ICMP, the primitives correspond to the 'sendto' and 'recvfrom' system calls.
-
For both UDP and TCP the system adaptor may send ("in-band") error indications in case of system errors. That
results in an assignment of inconc by the IP_PTC.
4.2.4.4
Routing of IP Data
The routing of IP data is done in the DRB-Mux which gets a routing table configured. This table associates the address
and protocol information of IP packets (protocol, local IP address, local port, remote IP address, remote port) with the
radio bearer (RAT, cell, DRB id).
In UL a DRB is considered being in raw mode when there is no entry found in the routing table. It is considered being
in IP mode when there is any entry regardless of the protocol and address information being stored, i.e. in UL, the SS
does not need to evaluate the IP header to route the data (in raw mode this would cause problems in the case of
loopback data). In addition for the IP mode, specific entries of the routing table can be flagged to discard or loopback IP
packets matching this entry.
The discard mode can be used e.g. for rSRVCC to suppress RTP/RTCP data on the default AM DRB during HO. The
major purpose is to discard the data silently (i.e. to suppress any error reporting like ICMP error messages).
NOTE:
It is up to system implementation how packets are discarded (explicitly or implicitly by the IP stack) as
long as it done silently.
The loopback mode can be configured for RTP and/or RTCP, and depending on the protocol the SS shall manipulate
the packets as follows :
-
swapping of source and destination address and port .
NOTE:
Further manipulation of the RTP header and/or RTCP header is not considered in the present document.
Beyond the aforementioned requirements, it is up to system implementation how packets are looped back.
In DL the IP packets of the IP stack are routed to the DRBs acc. to the routing information in the routing table (see
annex D for details).
NOTE:
4.2.4.5
Only the IP PTC can re-configure the Routing Table; if that needs to be triggered by a RAT specific PTC,
this is done by appropriate coordination messages but the RAT specific PTCs don't have a direct access to
the routing tables.
Multiple PDNs
In case multiple PDNs broadcast, or multicast datagrams sent by the UE, need to assigned to the respective PDN:
IPv4
When the UE does not get a valid IPv4 address assigned via NAS signalling it will request the IP address via
DHCP. In this case there are DHCP broadcast messages in UL.
In the case of multiple PDNs, it cannot be distinguished by evaluating the IP address to which PDN the message
belongs but additional information is necessary:
The network side needs to know which interface (i.e. network) the broadcast comes from; in case of LTE this is
associated with the default bearer of the particular PDN.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
NOTE:
32
ETSI TS 136 523-3 V13.2.0 (2017-03)
In principle the 'chaddr' field or the 'client identifier' option of the DHCP messages may be used to
distinguish different interfaces (e.g. for Ethernet this would be the MAC address) but it is not specified
how these fields are to be used by the UE (or how to configure them at the UE); RFCs (e.g. RFC 2131)
only require the client identifier to be unique in a given subnet.
IPv6
The UE gets an interface identifier assigned via NAS signalling (TS 24.301 [21] clause 6.2.2) which is used as
link-local address during stateless address auto configuration (TS 23.060 [43] clause 9.2.1.1 and TS 29.061
[44] clause 11.2):
The UE may send a ROUTER SOLICITATION message (multicast) to which the network responds with a
ROUTER ADVERTISEMENT.
Since the ROUTER SOLICITATION message contains the interface identifier as assigned via NAS signalling,
even in the case of multiple PDNs it can distinguished which PDN is concerned, as long as the interface
identifiers are different for different PDNs (for UE side as well as for network side).
NOTE:
According to TS 23.060 [43] clause 9.2.1.1 and RFC 3314 a real network (PDN-GW) itself shall send an
(unsolicited) ROUTER ADVERTISEMENT after it has assigned the interface identifier.
Conclusions and Requirements:
In the case of broadcast or multicast messages TTCN needs additional information about the PDN being addressed.
When a socket connection is configured to allow broadcasts and there is a broadcast or multicast message in UL the SS
shall provide information about on which bearer the datagram has been sent (RAT, cell, DRB id).
NOTE:
From the socket programming point of view multiple PDNs for the SS are like a multi-homed host:
Servers for different interfaces are bound to different interfaces (e.g. using the ‘bind’ system call with a
specific IP address instead of IPADDR_ANY) or a server may retrieve the interface id for a received
datagram from the IP stack with an appropriate system call.
Even though the details are implementation dependent, the SS shall be capable of:
determining RAT, cell, DRB id for any broadcast or multicast datagram in UL
avoiding any duplication of messages in UL even when multiple servers are listening to broadcast/multicast
messages (what is a possible SS implementation)
4.2.4.6
IP Addresses Guidelines
4.2.4.6.1
Common Structure of IP Addresses
IPv4:
Network prefix (subnet address)
n bits
Host part
32-n bits
with ‘n’ e.g. depending on the network class
IPv6:
Network prefix
Global routing prefix
64 – n bits
Subnet ID
n bits
Interface ID
64 bits
Addresses within one network (PDN) have all the same subnet address (IPv4) or global routing prefix (IPv6)
NOTE: As a consequence at the system simulator, routing can be done based on appropriate network masks, but that
is dependent on SS implementation and therefore is out of scope for this document.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.4.6.2
33
ETSI TS 136 523-3 V13.2.0 (2017-03)
Common Requirements regarding IP Addresses
IP addresses are configured via PIXIT parameters as defined in clause 9.1.
These PIXIT parameters shall fulfil the following requirements:
Network and UE addresses shall be different from each other
Network entities (DHCP server, DNS server, P-CSCF etc.) of a given PDN shall all have the same global routing
prefix (IPv6) or subnet address (IPv4).
The IP address assigned to the UE shall have the same global routing prefix (IPv6) or subnet address (IPv4) as the
corresponding network.
Requirements for IPv6: according to TS 23.401, cl. 5.3.1.2.2
The 64 bit network prefix of a UE’s IPv6 address is unique
The UE may change its interface id during auto configuration
The UE must use the given interface id in the link local address for router solicitation but may use any other
interface id in the global address
NOTE: As a consequence, the SS implementation needs to cope with the changing of the UE address and cannot
rely on static IP address assignment to the UE.
Global routing prefix (IPv6) and subnet address (IPv4) shall be different for different PDNs
Home agent address:
The home agent is located in the UE’s home network (which shall be considered to find an appropriate network
prefix for the home agent’s IP address)
In order to simplify implementations, the following rules shall be applied:
The IPv6 interface identifier as assigned to the UE via NAS signalling shall be unique, i.e.
It shall be different for different PDNs
It shall differ from the interface ids of the other entities on the link (in general the interface id of the PDN-GW)
Multiple PDNs shall have different IPv6 interface identifier for the PDN-GW
NOTE: Consistency checks for addresses of different PDNs can be done based on an appropriate network mask
(IPv4, e.g. 255.255.255.0) and global routing prefix (IPv6, e.g. 2001:db8:1234::/48).
4.2.4.6.3
Network Entities and their IP addresses
In general and in accordance of IMS test cases in TS 36.523-1 [1] and TS 34.229-1 [40] the simulated network
architecture can be illustrated as in Figure 4.2.4.6.3-1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
DHCP
ICMPv6
Server
DNSServer
Server
P-CSCF 1
Signalling
34
ETSI TS 136 523-3 V13.2.0 (2017-03)
SS
S-CSCF 1
S-CSCF 2
P-CSCF 2
(IP(IP
address:
NW)
address:
NW)
address:
(IP(IP
address:
NWNW)
–
IPv4, IPv6)
UE
User Data
Remote
User
(IP address:
(IP address:
UE – IPv4,
remote UE –
IPv6)
IPv4, IPv6)
Figure 4.2.4.6.3-1: Simulated Network Architecture
For simplification and to keep the number of PIXITs small , several network entities share the same PIXIT:
px_IPv4_AddressXX_NW:
P-CSCF 1 (IPv4 address), DNS Server (IPv4 address), DHCP Server
px_IPv6_AddressXX_NW:
P-CSCF 1 (IPv6 address), DNS Server (IPv6 address), ICMPv6 Server
(“XX” refers to the respective PDN)
In general , in test cases according to TS 36.523-1 [1] and TS 34.229-1 [40] no IP addresses are needed for
S-CSCF 1, S-CSCF 2 or P-CSCF 2.
4.2.4.7
User Plane Signalling for Address Allocation
For IPv4, the UE gets assigned the IP address via NAS signalling unless it explicitly requests to use DHCP.
For IPv6, the UE gets assigned a unique interface identifier to be used until it has successfully performed the autoconfiguration procedure (Ref. to RFC 2462).
NOTE: This clause specifies behaviour of the SS (TTCN) to achieve successful IP signalling; but in general, IP
signalling is out of scope for conformance tests as defined in TS 36.523-1 [1].
4.2.4.7.1
DHCP
When the UE supports IPv4 and does not get an IPv4 address via NAS signalling it will request the address via DHCP
(Ref. to RFC2131).
The UE may send a DHCPDISCOVER with or without Rapid Commit Option (Ref. to RFC 4039):
UE sends DHCPDISCOVER according to table 4.2.4.7.1-1 with Rapid Commit Option.
TTCN sends DHCPACK according to table 4.2.4.7.1-4
UE sends DHCPDISCOVER according to table 4.2.4.7.1-1 without Rapid Commit Option.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
35
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN sends DHCPOFFER according to table 4.2.4.7.1-2
When the Rapid Commit option is not used the UE sends a DHCPREQUEST as response to the DHCPOFFER:
UE sends DHCPREQUEST according to table 4.2.4.7.1-3
TTCN sends DHCPACK according to table 4.2.4.7.1-4
Any other DHCP messages shall be ignored by TTCN.
Table 4.2.4.7.1-1: DHCPDISCOVER
SRC ADDR
SRC Port
DEST ADDR
DEST Port
op
htype
hlen
hops
xid
secs
flags
ciaddr
yiaddr
siaddr
giaddr
chaddr
sname
file
options
magic cookie
message type
rapid commit
UDP
0.0.0.0
68
255.255.255.255
67
DHCP
‘01’O
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
‘63825363’O
‘01’O
present
any address
not checked
broadcast
BOOTREQUEST
0 according to RFC 2131 Table 5
0 according to RFC 2131 Table 5
0 according to RFC 2131 Table 5
0 according to RFC 2131 Table 5
client’s hardware address
(may be overloaded with further options)
(may be overloaded with further options)
NOTE
DHCPDISCOVER
shortened address assignment by 2message exchange acc. to RFC 4039
address assignment by 4-message
exchange
not present
NOTE: Any further options are not evaluated and ignored by TTCN
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
36
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 4.2.4.7.1-2: DHCPOFFER
UDP
SRC ADDR
SRC Port
DEST ADDR
DEST Port
valid server address
67
255.255.255.255
68
address as configured by PIXIT
op
htype
hlen
hops
xid
secs
flags
ciaddr
yiaddr
DHCP
‘02’O
as in corresponding DHCPDISCOVER
as in corresponding DHCPDISCOVER
‘00’O
as in corresponding DHCPDISCOVER
‘0000’O
as in corresponding DHCPDISCOVER
‘00000000’O
valid UE address
siaddr
0
giaddr
chaddr
sname
file
options
magic cookie
message type
lease time
server identifier
as in corresponding DHCPDISCOVER
as in corresponding DHCPDISCOVER
‘0000000000000000’O
‘00000000000000000000000000000000’O
broadcast
‘63825363’O
‘02’O
86400
server address
BOOTREPLY
NOTE 1
NOTE 1
NOTE 2
NOTE 2
NOTE 2
NOTE 2
NOTE 2
address to be assigned to the UE
(as configured by PIXIT)
the UE does not need to retrieve
any operating system executable
image
NOTE 2
NOTE 2
DHCPOFFER
one day; mandatory (NOTE 2)
server address as used in the UDP
header
NOTE 1: To get any valid value
NOTE 2: According to table 3 in RFC 2131
Table 4.2.4.7.1-3: DHCPREQUEST
SRC ADDR
SRC Port
DEST ADDR
DEST Port
UDP
0.0.0.0
68
255.255.255.255
67
DHCP
‘01’O
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
any value
op
htype
hlen
hops
xid
secs
flags
ciaddr
yiaddr
siaddr
giaddr
chaddr
sname
file
options
magic cookie
‘63825363’O
message type
‘02’O
NOTE: Any further options are not evaluated and ignored by TTCN
ETSI
any address
not checked
broadcast
BOOTREQUEST
0 according to RFC 2131 Table 5
0 according to RFC 2131 Table 5
0 according to RFC 2131 Table 5
0 according to RFC 2131 Table 5
client’s hardware address
(may be overloaded with further options)
(may be overloaded with further options)
NOTE
DHCPREQUEST
3GPP TS 36.523-3 version 13.2.0 Release 13
37
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 4.2.4.7.1-4: DHCPACK
UDP
SRC ADDR
SRC Port
DEST ADDR
DEST Port
valid server address
67
255.255.255.255
68
address as configured by PIXIT
not checked
broadcast
ciaddr
yiaddr
DHCP
‘02’O
‘01’O
as in corresponding DHCPREQUEST or
DHCPDISCOVER
‘00’O
as in corresponding DHCPREQUEST or
DHCPDISCOVER
‘0000’O
as in corresponding DHCPREQUEST or
DHCPDISCOVER
‘00000000’O
valid UE address
siaddr
0
giaddr
as in corresponding DHCPREQUEST or
DHCPDISCOVER
as in corresponding DHCPREQUEST or
DHCPDISCOVER
‘0000000000000000’O
‘00000000000000000000000000000000’O
op
htype
hlen
hops
xid
secs
flags
chaddr
sname
file
options
magic cookie
message type
lease time
server identifier
‘63825363’O
‘05’O
86400
server address
BOOTREPLY
NOTE
NOTE
NOTE
NOTE
NOTE
NOTE
address to be assigned to the UE
(as configured by PIXIT)
the UE does not need to retrieve
any operating system executable
image
NOTE
NOTE
DHCPACK
one day; mandatory (NOTE)
server address as used in the UDP
header
NOTE: According to table 3 in RFC 2131
4.2.4.7.2
DHCPv6
DHCPv6 is not needed for E-UTRA conformance tests as defined in 36.523-1[1]
4.2.4.7.3
ICMPv6
When the UE supports IPv6 it will perform IPv6 Stateless Address Auto configuration according to RFC 4862. The UE
sends an ICMPv6 Router Solicitation message according to table 4.2.4.7.3-1; as response the TTCN sends an
ICMPv6 Router Advertisement message according to table 4.2.4.7.3-2.
NOTE: The TTCN does not send any (periodic) unsolicited Router Advertisement, i.e. the UE is expected to ask for
an immediate advertisement whenever it is needed.
Any other ICMPv6 messages are ignored by the TTCN (especially in accordance to TS 23.060, clause 9.2.1.1, the
TTCN silently discards Neighbour Solicitation).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
38
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 4.2.4.7.3-1: ICMPv6 Router Solicitation
IPv6
link local address
multicast address
ICMPv6 (Ref. to RFC 4861)
133
0
not checked
ignored
SRC ADDR
DEST ADDR
NOTE 1
NOTE 2
type
Router Solicitation
code
checksum
reserved
options
source link-layer address
ignored if present
other options
ignored
NOTE 1: The UE shall use the interface identifier as assigned via NAS signalling (but this is not checked in
TTCN).
NOTE 2: TTCN detects the multicast address by checking it to start with FF02 but accepts any of these
addresses.
Table 4.2.4.7.3-2: ICMPv6 Router Advertisement
IPv6
SRC ADDR
DEST ADDR
link local address (NW)
link local address (UE)
ICMPv6 (Ref. to RFC 4861)
134
0
calculated by TTCN
64
‘0’B
type
code
checksum
current hop limit
m-flag
o-flag
reserved
router lifetime
reachable time
retrains timer
options
source link-layer address
mtu
prefix information
type
length
prefix length
on-link flag
‘0’B
'000000'B
65535
0
0
4.2.4.7.4
Router Advertisement
arbitrarily selected
no “Managed address
configuration”; NOTE 3
no “Other configuration”
max. value
unspecified
unspecified
not present
not present
‘03’O
4
64
‘0’B
autonomous address configuration flag
reserved1
valid lifetime
preferred lifetime
reserved2
prefix
NOTE 1:
NOTE 2:
NOTE 3:
NOTE 4:
NOTE 1
NOTE 2
/64 IPv6 prefix acc. to
TS 23.401
no “On-link detection”;
NOTE 3
‘0’B
‘000000’B
'FFFFFFFF'O
infinity; NOTE 3
'FFFFFFFF'O
infinity; NOTE 3
‘00000000’B
globally unique /64 IPv6
NOTE 4, 5
prefix to be assigned to
the UE
The server’s link local address is derived from the server’s global IPV6 address (PIXIT parameter)
As received as SRC address of the corresponding Router Solicitation
Acc. to TS 29.062 clause 11.2.1.3.2
The routing prefix of the UE’s global IPv6 address is derived from the respective PIXIT parameter
NOTE 5: Since the UE may change its interface identifier after successful auto configuration to any
value in general the IPv6 address used by the UE differs from the PIXIT
DNS
In general DNS is not needed for E-UTRA conformance tests as defined in 36.523-1[1].
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
39
ETSI TS 136 523-3 V13.2.0 (2017-03)
Nevertheless as the IP test model is also applicable for test suites other than 36.523-1[1] handling of certain DNS
queries (according to RFC 1035 [58]) is supported over UDP:
Table 4.2.4.7.4-1: Supported DNS Queries
DNS Header
id
qr
opcode
aa
tc
rd
ra
z
rcode
qdcount
ancount
nscount
any value
'0'B
'0000'B
'?'B
'0'B
'?'B
'?'B
'000'B
'????'B
1
0
0
arcount
0
2 octets; id to be used in response
query
standard query
Authoritative Answer: any value in query
no truncation
Recursion Desired: any value
Recursion Available: any value in query
must be '000'B according to RFC 1035 [58]
Response code: na for query
unsigned 16 bit integer: number of questions
unsigned 16 bit integer: number of answers
unsigned 16 bit integer: number of authority
records
unsigned 16 bit integer: number of additional
records
Questions
DNS Question: only one question per query is supported
qname
any value
octetstring with encoded domain name according
to RFC 1035 clause 4.1.2 [58]
qtype
'0001'O or
Type A (IPv4 Address according to RFC 1035
'001C'O
clause 3.2.2 [58]) or Type AAAA (IPv6 Address
according to RFC 3596 clause 2.1 [59])
qclass
'0001'O
IN (internet)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
40
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 4.2.4.7.4-2: Corresponding DNS Responses
id
qr
opcode
aa
tc
rd
ra
z
rcode
qdcount
ancount
nscount
arcount
DNS Question
DNS Answer
qname
qtype
qclass
ttl
rdlength
rdata
DNS Header
same value as in
corresponding query
'1'B
response
same value as in
corresponding query
'1'B
Authoritative Answer
'0'B
no truncation
'0'B
no recursion
'0'B
no recursion
'000'B
'0000'B
no error
1
unsigned 16 bit integer: number of questions
1
unsigned 16 bit integer: number of answers
0
unsigned 16 bit integer: number of authority
records
0
unsigned 16 bit integer: number of additional
records
Questions
same value as in
corresponding query
Answers
same value as in
corresponding query/question
same value as in
corresponding query/question
'0001'O
86400
4 for IPv4
16 for IPv6
octetstring containing IPv4 or
IPv6 address
ETSI
IN (internet)
one day
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.4A
41
ETSI TS 136 523-3 V13.2.0 (2017-03)
LTE-Carrier Aggregation test Models
4.2.4A.1
CA-MAC test model
TT CN CO DE
C o n f ig /
S R B 0 -S R B 2
C o n t ro l
DRB
TM
TM
DTCH
RLC
MAC
M AC
PHY
PHY
S C ell
P C el l
S C el l
L o o p b a ck a b o v e P D C P in U E
Figure 4.2.4A.1-1: Test model for CA-MAC testing
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. On UE side Ciphering
is enabled (since Mandatory) but with dummy ciphering algorithm, which is equivalent to not using ciphering. ROHC is
not configured on UE Side.
On the SS Side,
Pcell only: On DRBs the RLC is configured in transparent mode. Hence with this configuration PDU's out of SS RLC
are same as the SDU's in it. There is no PDCP configured on SS Side. The ports are directly above RLC.
Pcell/Scell: Layer 1 is configured in the normal way. MAC is configured in a special mode, where it does not add any
MAC headers in DL and /or not remove any MAC headers in UL directions respectively at DRB port. In this case, the
TTCN shall provide the final PDU, including padding. Except for this, the MAC layer shall perform all of its other
functions. For SRB’s/BCCH/PCCH the configuration is same as in CA-RRC test model.
There are two different test modes in which MAC header addition/removal can be configured:
DL/UL header-transparent mode: no header addition in DL and no header removal in UL.
DL only header-transparent mode: no header addition in DL; UL MAC is configured in normal mode to remove
MAC header and dispatch the MAC SDUs according to the logical channel Ids.
If SS MAC is configured in DL/UL header-transparent mode, the PDU's exchanged at the DRB port between TTCN
and SS, shall be the final MAC PDU's consisting of MAC, RLC and PDCP headers. TTCN code shall take care in DL
of building MAC header, RLC headers and PDCP headers and in UL handle MAC, RLC and PDCP headers. TTCN
code shall take care of maintaining sequence numbers and state variables for RLC and PDCP layers. During testing of
multiple DRBs at the UE side, it shall still be possible to configure only one DRB on SS side with configuration in the
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
42
ETSI TS 136 523-3 V13.2.0 (2017-03)
figure 4.2.4A.1-1. Other DRBs will not be configured, to facilitate routing UL TBs. Multiplexing/de-multiplexing of
PDUs meant/from different DRBs shall be performed in TTCN. Since the MAC layer does not evaluate the MAC
headers in UL it cannot distinguish between SRB and DRB data in UL. Therefore there shall be no SRB traffic while
MAC is configured in this test mode.
If SS MAC is configured in DL only header-transparent mode, the UL PDUs exchanged at the DRB port between
TTCN and SS, shall be final RLC PDUs consisting of RLC and PDCP headers. SS shall route these PDUs based on
logical channel IDs. In DL, TTCN sends fully encoded MAC PDUs at the DRB port (consisting of MAC, RLC and
PDCP headers). In this case TTCN needs to take care of maintaining sequence numbers and state variables for RLC and
PDCP layers. Furthermore in UL and DL the SS MAC layer shall be capable of dealing with SRB data (i.e. it shall
handle DL RLC PDUs coming from SRBs RLC layer or dispatch UL RLC PDUs to SRBs) as in normal mode.
NOTE:
TTCN shall ensure that no DL MAC SDUs in normal mode and DL MAC PDUs in test mode are mixed
for the same TTI.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception in Pcell over system indication port, if configured. In a similar way
the reception of RACH preambles in Pcell/Scell is reported by SS over the same port, if configured.
The RACH Procedure configured in active Scell controls the RACH procedure in Scell. The PDCCH order is sent on
PDCCH controlling the Scell. PRACH preamble is received in the Scell. RAR is transmitted in the associated Pcell as
per RACH procedure in active Scell.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.4A.2
43
ETSI TS 136 523-3 V13.2.0 (2017-03)
CA-RRC test model
TTCN CODE
Control
SRB0
NAS Integrity &
Ciphering
SRB1
DRB
SRB2
SRB0
RRC/NAS Emulator
Integrity
Integrity
Ciphering
Ciphering
PDCP
RLC
TM
CCCH
AM
AM
DCCH
Ciphering
TM
AM/UM
DTCH
DCCH
MAC
MAC
PHY
PHY
PCell
DTCH
CCCH
SCell
UE Operation in Normal Mode
Figure 4.2.4A.2-1: Test model for CA-RRC testing
The UE is configured in normal mode. On UE side Ciphering/Integrity (PDCP and NAS) is enabled and ROHC is not
configured.
On the SS Side L1 (Pcell/Scell), MAC (Pcell/Scell), RLC (Pcell) and PDCP (Pcell) are configured in normal way. They
shall perform all of their functions. For SRB0 the DL and UL port is above RLC. For SRB1 and SRB2 the port is
above/below the RRC and NAS emulator, which may be implemented as a parallel test component. For DRB, the port
is above PDCP. PDCP Ciphering/Integrity is enabled. NAS integrity/Ciphering is enabled.
Note: RLC for BCCH/ PCCH/CCH are configured per serving cell; RLC and PDCP for DCCH/DTCH are configured
only in Pcell and are additionally multiplexed on MAC of associated Scells.
The RRC/NAS emulator for SRB1 and SRB2 shall provide the Ciphering and integrity functionality for the NAS
messages. In UL direction, SS shall report RRC messages, still containing (where appropriate) the secure and encoded
NAS message, to the RRC port. In DL, RRC and NAS messages with same timing information shall be embedded in
one PDU after integrity and ciphering for NAS messages.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception in Pcell over system indication port, if configured. In a similar way
the reception of RACH preambles in Pcell/Scell is reported by SS over the same port, if configured.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
44
ETSI TS 136 523-3 V13.2.0 (2017-03)
The RACH Procedure configured in active Scell controls the RACH procedure in Scell. The PDCCH order is sent on
PDCCH controlling the Scell. PRACH preamble is received in the Scell. RAR is transmitted in the associated Pcell as
per RACH procedure in active Scell.
4.2.4A.3
LAA-MAC test model
TTCN CO DE
C o n fig /
S R B 0 -S R B 2
C o n tro l
DRB
TM
TM
DTCH
RLC
M AC
M AC
PHY
PHY
S C e ll
P C e ll
L A A S C e ll
L o o p b a c k a b o v e P D C P in U E
Figure 4.2.4A.3-1: Test model for LAA-MAC testing
The test model is similar to CA-MAC test model in clause 4.2.4A.1, except for the following differences in SCell when
configured in unlicensed band:
-
The BCCH/PBCH is not configured (BcchConfig_Type is not present),
-
The PCCH is not configured (PcchConfig_Type is not present),
-
UL physical Channels are not configured (PhysicalLayerConfigUL_Type is not present) with RAT type set as
TDD,
-
SRB0 is not configured,
-
RACH procedure is not configured (RachProcedureConfig_Type is not present).
Based on band of operation the SS shall use frame structure type 3 in the SCell in unlicensed band.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.4A.4
45
ETSI TS 136 523-3 V13.2.0 (2017-03)
LAA-RRC test model
TTCN CODE
Control
NAS Integrity &
Ciphering
SRB1
SRB0
DRB
SRB2
RRC/NAS Emulator
Integrity
Integrity
Ciphering
Ciphering
PDCP
RLC
TM
AM
AM
CCCH
DCCH
Ciphering
AM/UM
DTCH
DTCH
DCCH
MAC
MAC
PHY
PHY
PCell
LAA SCell
UE Operation in Normal Mode
Figure 4.2.4A.4-1: Test model for LAA-RRC testing
The test model is similar to LAA-RRC test model in clause 4.2.4A.2, except for the following differences in SCell
configuration in unlicensed band:
-
The BCCH/PBCH is not configured (BcchConfig_Type is not present),
-
The PCCH is not configured (PcchConfig_Type is not present),
-
UL physical Channels are not configured (PhysicalLayerConfigUL_Type is not present) with RAT type set as
TDD,
-
SRB0 is not configured,
-
RACH procedure is not configured (RachProcedureConfig_Type is not present).
Based on band of operation the SS shall use frame structure type 3 in the SCell in unlicensed band.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.4B
4.2.4B.1
46
ETSI TS 136 523-3 V13.2.0 (2017-03)
Dual Connectivity test models
DC MAC test model
TTC N CO DE
C o n f ig /
S R B 0 -S R B 2
C o n t ro l
DRB
TM
RLC
TM
TM
D TC H
M AC
PHY
P C el l
TM
D T CH
M AC
MAC
PHY
PHY
S C e ll
S C el l
M AC
PHY
PS C el l
L o o p b a ck a b o v e P D C P in U E
Figure 4.2.4B.1-1: Test model for DC MAC testing
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. On UE side Ciphering
is enabled (since mandatory) with dummy ciphering algorithm, which is equivalent to not using ciphering. ROHC is not
configured on UE Side.
On the SS Side, zero or more SCell’s associated with PCell/PSCell may be configured.
PCell/PSCell only: On DRBs the RLC is configured in transparent mode. Hence with this configuration PDU's out of
SS RLC are same as the SDU's in it. There is no PDCP configured on SS Side. The ports are directly above RLC.
PCell/PSCell/SCell: Layer 1 is configured in the normal way. MAC is configured in a special mode, where it does not
add any MAC headers in DL and /or not remove any MAC headers in UL directions respectively at DRB port. In this
case, the TTCN shall provide the final PDU, including padding. Except for this, the MAC layer shall perform all of its
other functions. For SRB’s/BCCH/PCCH the configuration is same as in Dual connectivity-RRC test model.
For Split DRB’s the TM DRB from the CG will be used to send/receive PDU’s in that CG.
There are two different test modes in which MAC header addition/removal can be configured:
-
DL/UL header-transparent mode: no header addition in DL and no header removal in UL.
-
DL only header-transparent mode: no header addition in DL; UL MAC is configured in normal mode to remove
MAC header and dispatch the MAC SDUs according to the logical channel Ids.
If SS MAC is configured in DL/UL header-transparent mode, the PDU's exchanged at the DRB port between TTCN
and SS, shall be the final MAC PDU's consisting of MAC, RLC and PDCP headers. TTCN code shall take care in DL
of building MAC header, RLC headers and PDCP headers and in UL handle MAC, RLC and PDCP headers. TTCN
code shall take care of maintaining sequence numbers and state variables for RLC and PDCP layers. During testing of
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
47
ETSI TS 136 523-3 V13.2.0 (2017-03)
multiple DRBs at the UE side, it shall still be possible to configure only one DRB on SS side per CG with configuration
in the figure 4.2.4B.1-1. Other DRBs will not be configured, to facilitate routing UL TBs. Multiplexing/de-multiplexing
of PDUs meant/from different DRBs shall be performed in TTCN. Since the MAC layer does not evaluate the MAC
headers in UL it cannot distinguish between SRB and DRB data in UL. Therefore there shall be no SRB traffic while
MAC is configured in this test mode.
If SS MAC is configured in DL only header-transparent mode, the UL PDUs exchanged at the DRB port between
TTCN and SS shall be final RLC PDUs consisting of RLC and PDCP headers. SS shall route these PDUs based on
logical channel IDs. In DL, TTCN sends fully encoded MAC PDUs at the DRB port (consisting of MAC, RLC and
PDCP headers). In this case TTCN needs to take care of maintaining sequence numbers and state variables for RLC and
PDCP layers. Furthermore in UL and DL the SS MAC layer shall be capable of dealing with SRB data (i.e. it shall
handle DL RLC PDUs coming from SRBs RLC layer or dispatch UL RLC PDUs to SRBs) as in normal mode.
NOTE:
TTCN ensures that no DL MAC SDUs in normal mode and DL MAC PDUs in test mode are mixed for
the same TTI.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception in PCell over system indication port, if configured. In a similar way
the reception of RACH preambles in PCell/SCell is reported by SS over the same port, if configured.
The RACH Procedure configured in active SCell controls the RACH procedure in SCell. The PDCCH order is sent on
PDCCH controlling the SCell. PRACH preamble is received in the SCell. RAR is transmitted in the associated PCell as
per RACH procedure in active SCell.
4.2.4B.2
DC PDCP test model
The PDCP test model is based on DC RRC test model except for the following.
The UE is configured in Test Loop Mode, to loop back the user domain data above PDCP layer. On UE side Ciphering
is enabled and ROHC is not configured.
The PDCP is configured in a special mode, named transparent mode. In this mode, SS shall not add PDCP header (DL)
and remove PDCP Header (UL). The TTCN maintains sequence numbers and state variables for the PDCP layer. The
TTCN makes use of the AS ciphering functionality in both directions, employing the dummy ciphering algorithm.
Ciphering/deciphering are performed using TTCN external functions. ROHC is not configured.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.4B.3
48
ETSI TS 136 523-3 V13.2.0 (2017-03)
DC RRC test model
TTCN CODE
Control
SRB’s/
MCG DRB’s
Split
DRB’s
SCG
DRB
SRB0
SRB0
PDCP
Ciphering
Ciphering
RLC
AM
TM
TM
AM/UM
AM
CCCH
MCG (except Split
DRB) Same as CA
RRC test model
DTCH
PCell/SCell
CCCH
DTCH
MAC
MAC
PHY
PHY
PSCell
SCell
UE Operation in Normal Mode
Figure 4.2.4B.3-1: Test model for DC RRC testing
The UE is configured in normal mode. On UE side Ciphering/Integrity (PDCP and NAS) is enabled and ROHC is not
configured. Zero or more SCell’s associated with PCell/PSCell may be configured.
On the SS Side L1 (PCell/PSCell/SCell), MAC (PCell/PSCell/SCell), RLC (PCell/PSCell) and PDCP (PCell/PSCell)
are configured in normal way. They shall perform all of their functions. SRB’s are configured only in PCell. For SRB0
the DL and UL port is above RLC. For SRB1 and SRB2 the port is above/below the RRC and NAS emulator, which
may be implemented as a parallel test component. For DRB, the port is above PDCP. PDCP Ciphering/Integrity is
enabled. NAS integrity/Ciphering is enabled.
NOTE:
RLC for BCCH/PCCH/CCCH are configured per serving cell; RLC and PDCP for DCCH/DTCH are
configured only in PCell/PSCell and are additionally multiplexed on MAC of associated SCells in the CG
(carrier group).
For Split DRB’s PDCP is not configured in PSCell. If UL traffic on split DRB will be steered through SCG (i.e. ulDataSplitDRB-ViaSCG is true), the IE ul-DataSplitDRB-ViaSCG will only be provided in PDCP-Info in PSCell.
The PCell and SCell (associated with either PCell or PSCell) are same as in CA RRC test model in clause 4.2.4A.2.
The RRC/NAS emulator for SRB1 and SRB2 shall provide the Ciphering and Integrity functionality for the NAS
messages. In UL direction, SS shall report RRC messages, still containing (where appropriate) the secure and encoded
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
49
ETSI TS 136 523-3 V13.2.0 (2017-03)
NAS message, to the RRC port. In DL, RRC and NAS messages with same timing information shall be embedded in
one PDU after integrity and ciphering for NAS messages.
The UL Scheduling Grant and DL Scheduling assignments are configured from TTCN over system control port. SS
reports PUCCH scheduling information reception in PCell/PSCell over system indication port, if configured. In a
similar way the reception of RACH preambles in PCell/PSCell/SCell is reported by SS over the same port, if
configured.
4.2.5
IP model extension for IMS
The IMS test model is based on the IP Test Model with extensions to support IPsec. Support of Signalling Compression
(SigComp) may be added in the future if needed.
IMS in general may use TCP, UDP or alternated TCP/UDP as transport layer for signalling messages.
At TTCN-3 system interface level there are no IMS specific ports or ASPs, i.e. IMS specific issues are purely handled
in TTCN and therefore out of scope for this document.
NOTE:
Even though the main intention to introduce the IMS test model is to support the initial IMS registration
procedure, the IMS test model is independent of any specific IMS procedures.
IMS_PTC
EUTRA_PTC
L
R
T
C
_
P
I
CTRL
SIP client
(sec)
SIP server
(sec)
IMS IP CTRL
SIP client
(sec)
SIP server
(sec)
IMS IP CTRL
IP_PTC
Control
L
R
T
C
IP-Data
Routing
Control
Socket
Control
MUX/Filter
Socket Ctrl
IP_SOCK
IPsec_CTRL
IP_CTRL
IPsec_CTRL
IP_CTRL
IP Data ,
Socket Ctrl
System Interface
IP_
SOCK
IP-Da ta
Socket
Ctrl
IPsec: SAD, SPD
IP stack
ra w mode
EUTRA:
Cellx, DRBy
DRB-MUX
UTRAN:
Cellx, RBy
Security
Ctrl
Routing
Ctrl
IP mode
Routing Table
GERAN
System Adaptor
Figure 4.2.5-1: Example for IP model supporting IMS
NOTE 1: At the system interface IPsec is the only difference compared to the IP model of clause 4.2.4
NOTE 2: It is a working assumption to have a separate PTC for IMS as shown in figure 4.2.5-1
NOTE 3: Ports between the IP_PTC and the IMS_PTC are for illustration only
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.5.1
50
ETSI TS 136 523-3 V13.2.0 (2017-03)
IPsec
IPsec involves security policy database (SPD) and security association database (SAD) (Ref. RFC4301). The entries in
the databases are configured with security parameters by ASPs at the IPsec_CTRL port.
NOTE:
IPsec is not directly associated to a given socket but IPsec is applied to IP packets matching a configured
security association. configuration of IPsec in general is independent of the existence of sockets but
typically the IPsec configuration is done just before establishment of a corresponding socket.
⇒
The SS shall cleanup all IPsec database entries which has been setup by TTCN during a test case at the end of the test
case independent of how the test case terminates (normal termination, run-time error etc.)
4.2.5.1.1
NOTE:
Security Association
Within this clause SA is used as abbreviation of ‘Security Association’ (i.e. not as abbreviation for
‘System Adaptor’ as usual)
During the IMS signalling handling two pairs of SAs consisting of four unidirectional SAs will be used, one pair of SAs
(SA2 and SA4) is between the server port of UE and the client port of the SS, another pair of SAs (SA1 and SA3) is
between the client port of UE and the server port of the SS, see figure 4.2.5.2.3.1-1.
UE
port_uc
SS
port_ps
SA1, spi_ps
port_pc
port_us
SA2, spi_us
port_uc
port_ps
SA3, spi_uc
port_us
port_pc
SA4, spi_pc
Figure 4.2.5.2.3.1-1 Two pairs of SAs
SA1 used for data flow from port_uc to port_ps is an inbound SA for protected server port of P-CSCF, its Security
Parameter Index spi_ps is selected by P-CSCF (IMS Registration/Authentication function in IP_PTC) and presented in
401 Unauthorised; SA2 used for data flow from port_pc to port_us is an inbound SA for protected server port of UE, its
Security Parameter Index spi_us is selected by UE and presented in initial REGISTER message; SA3 used for data flow
from port_ps to port_uc is an inbound SA for protected client port of UE, its Security Parameter Index spi_uc is selected
by UE and presented in initial REGISTER message; SA4 used for data flow from port_us to port_pc via an inbound SA
for client port of P-CSCF, its Security Parameter Index spi_pc is selected by P-CSCF (IMS Registration/Authentication
function in IP_PTC) and presented in 401 Unauthorised message. The pair of SA1 and SA3 is for bidirectional traffic
between port_uc and port_ps. The pair of SA2 and SA4 is for bidirectional traffic between port_pc and port_us. Those
four spi_xx and other security parameters are negotiated during security association set up procedure and shall be
passed to IPsec protocol layer in the SS. See "SAD and SPD" and clause 7.2 of TS 33.203 [41].
These four unidirectional SA and relevant ports are shared by TCP and UDP. TCP transport will use all four SAs, UDP
transport uses only two SAs, because there is no traffic from port_ps to port_uc, nor from port_us to port_pc.
Figure 4.2.5.2.3.1-2 shows the usage of ports and SAs under UDP and TCP transport in a generic registration procedure
(see clause C.2 of TS 34.229-1 [40]).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
51
ETSI TS 136 523-3 V13.2.0 (2017-03)
TCP transport
UDP transport
Unprotected
client port
REGISTER
401 Unauthorised
Unprotected
server port
RANDIIAUTN
REGISTER RES
port_uc
SA1, spi_ps
200 OK
SA2, spi_us
port_us
Unprotected
server port
Unprotected
client port
Unprotected
client port
Unprotected
client port
port_ps
port_uc
port_uc
port_pc
SUBSCRIBE
port_uc
200 OK
port_us
SA1, spi_ps
NOTIFY
port_us
port_uc
port_ps
port_uc
port_pc
port_us
SA2, spi_us
401 Unauthorised
RANDIIAUTN
REGISTER RES
Unprotected
server port
Unprotected
server port
port_ps
SA1, spi_ps
200 OK
SA3, spi_uc
SUBSCRIBE
SA1, spi_ps
port_ps
port_ps
port_ps
SA3, spi_uc
NOTIFY
port_pc
SA2, spi_us
200 OK
port_uc
REGISTER
200 OK
port_pc
SA2, spi_us
SS
UE
SS
UE
port_us
port_ps
200 OK
port_pc
SA4, spi_pc
SA4, spi_ps
Figure 4.2.5.2.3.1-2: Usage of ports and SAs in UDP and TCP transport
4.2.5.1.2
SAD and SPD
SAD and SPD are used by IPsec to store various security parameters (per Security Association). During IMS AKA, the
UE and the IMS Registration/Authentication function in IP_PTC negotiates the negotiable parameters for security
association setup, this negotiation is carried out at the SIP level in TTCN-3, and the resulting security association
parameters are maintained in TTCN-3. The involved parameters are:
spi_uc; spi_us; spi_pc; spi_ps
encryption algorithm
integrity algorithm
The IMS AKA will generate key IKIM, the security parameters IKESP and CKESP are derived from IKIM and CKIM in
TTCN-3 (Ref. Annex I of TS 33.203[41]). ASPs are used to pass these parameters (per security association and with its
selectors) from TTCN-3 to SAD and SPD of IPsec layer in the SS.
The same IKESP and CKESP will be used for the four unidirectional SAs. All of the four unidirectional SAs will use the
same negotiated encryption algorithm and integrity algorithm.
In addition to those negotiable security parameters, other security parameters are fixed in IMS environment (see
clause 7.1 of TS 33.203 [41]):
Life type:
second
SA duration:
232-1
Mode:
transport
IPsec protocol:
ESP, ESP integrity applied
Key length:
192 bits for DES-EDES_CBC, 128 bits for AES-CBC and HMAC-MD5-96; 160 bits
for HMAC-SHA-1-96
These parameters are hard coded with IPsec implementation in the SS, not passed from TTCN-3.
An SA have to be bound to selectors (specific parameters) of the data flows between UE and P-CSCF (IMS
Registration/Authentication function in IP_PTC), the selectors are:
source IP address
destination IP address
source port
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
52
ETSI TS 136 523-3 V13.2.0 (2017-03)
destination port
transport protocols that share the SA
IP addresses bound to the two pairs of SAs are:
For inbound SAs at the P-CSCF (the SS side):
-
The source and destination IP addresses associated with the SA are identical to those in the header of the IP
packet in which the initial SIP REGISTER message was received by the P-CSCF.
For outbound SAs at the P-CSCF (the SS side):
-
The source IP address bound to the outbound SA equals the destination IP address bound to the inbound SA;
the destination IP address bound to the outbound SA equals the source IP address bound to the inbound SA.
Ports bound to the two pairs of SAs are depictured in figure 4.2.5.2.3.1-1, port_ps and port_pc shall be different from
the default SIP ports 5060 and 5061. The number of the ports port_ps and port_pc are communicated to the UE during
the security association setup procedure.
The transport protocol selector shall allow UDP and TCP.
The selectors are passed to the SS IPsec layer together with the security parameters related to an SA bound to the
selectors.
4.2.5.2
Signalling Compression (SigComp)
Signalling compression is mandatory (see clause 8 of TS 24.229 [42]) and Signalling compression (RFC 3320 [43],
RFC 3485 [44], RFC 3486 [45], RFC 4896 [46], RFC 5049 [47]) protocol is used for SIP compression. SigComp entity
in the model is used to carry out the compression/decompression functions. In receiving direction of the SS the
SigComp entity will detect whether the incoming SIP message is compressed, and decompress the message if it is
compressed. In the SS transmitting direction, the TTCN, via ASP, controls when the compression of outgoing SIP
message is started. Stateless compression is not used in the SIP environment. For state full operation of SigComp the
ASP passing compartment ID to SigComp is applied. The SS shall clean all states related to a connection in SigComp
when an ASP for closing the connection is received. The SS shall also clean all states in the SigComp when abortion of
a test case is detected or after the system reboots. If decompression failure occurs while decompressing a message, the
message shall be discarded. The SigComp entity in the SS shall automatically find if a secure port or un-secure port is
being used for transmission or reception of messages. If an un-secure port is used for transmission, it shall not include
state creation instructions. If the state creation command is received in a compressed message on an un-secured port, a
decompression failure shall be generated.
4.2.5.3
SIP TTCN-3 Codec
SIP is a text-based protocol, the messages exchanged between the UE and the SS are character strings. In TTCN-3 the
messages are structured to take the advantages of TTCN-3 functionalities, and to make the debugging and maintenance
easier.
Even though there is no encoding/decoding of SIP messages at the TTCN-3 system interface, the IMS_PTC uses the
SIP codec by means of the TTCN-3 build-in functions encvalue and decvalue.
The SIP codec is specified in TS 34.229-3 [45] clause 7.
4.2.6
Support of DSMIPv6
For testing of DSMIPv6 IP packets being relevant for the test cases may be routed by the IP_PTC to the PTCs with
specific test case implementation. There are not specific requirements for the system interface.
The functions of HA and ePDG are FFS.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.7
53
ETSI TS 136 523-3 V13.2.0 (2017-03)
MBMS test model
TTCN CODE
SRB0-SRB2
DRB
MRB
PDCP
Cipher ing
RLC
AM/UM
UM
DTCH
MTCH
MAC
MCH
SCH
PHY
Counting - Test loop mode C active in UE
Figure 4.2.7-1: Test model for MBMS testing
The UE is configured in Test Loop Mode C to count the successfully received MBMS Packets. On the UE side,
Ciphering/Integrity (PDCP and NAS) are enabled on SRBs/DRB. No security is configured on MCCH/MTCH.
On the SS side, the cell is configured as a normal cell, the MBMS parameters are configured by using an additional call
of SYSTEM_CTRL_REQ. L1, MAC and RLC are configured for MCCH/MTCH in normal mode; they shall perform
all of their functions. The MRB ports are above RLC. For MTCH data transmission, the SS shall set the MCH
Scheduling Information (MSI) in the MAC PDU in the first subframe allocated to the MCH within the MCH scheduling
period to indicate the position of each MTCH and unused subframes on the MCH according to TS 36.321[16] clause
6.1.3.7 The SS will be explicitly configured by the TTCN for MSI MAC control element. SS shall repeat the same
configured MSI in the first subframe allocated to the MCH within each new MCH scheduling period.
The MRB data is considered as raw data and is scheduled with explicit timing control information from TTCN on
MTCH.
4.2.8
OCNG test model
The OCNG generator is a logical block in the SS MAC layer, activated/deactivated by TTCN. There is one OCNG
generator per cell, and OCNG may be activated by TTCN in any cell (i.e. serving or neighbour).
When OCNG is activated in a cell, the SS shall automatically transmit uncorrelated pseudo random data in an arbitrary
number of DL MAC TB’s on PDSCH’s, in each non-ABS (Almost Blank Subframe) identified by
MeasSubFramePattern, identified by an arbitrary number of virtual (non existing) UE’s with C-RNTI’s set different
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
54
ETSI TS 136 523-3 V13.2.0 (2017-03)
from the C-RNTI of the UE under test. The SS shall treat these MAC TB’s in a special way, i.e. shall not expect any
HARQ feedback and shall not make any HARQ retransmissions. The SS shall select the number of virtual UE’s to
achieve the following conditions in each non-ABS subframe:
-
Load all CCE’s unused by any scheduled RNTI (SI-RNTI, C-RNTI , P-RNTI, RA-RNTI, Temp C-RNTI, SPS
C-RNTI, M-RNTI) transmissions.
-
Utilize all PRB’s un-assigned by any scheduled RNTI.
-
The modulation is restricted to QPSK.
The DCI combination 1 defined in clause 7.3.3.5.1 is used to facilitate maximum utilization of un-assigned PRB’s.
While activating OCNG on a non-PCell, TTCN shall take care of timing information for the cell such that the SFN and
subframe number should result in the corresponding PCell SFN mod x = 0, where x is the size of the subframePattern
bit string divided by 10 and the corresponding subframe number of Pcell =0.
TTCN CODE
Control
SRB0
SRB1
NAS Integrity &
Ciphering
SRB2
DRB
RRC/NAS Emulator
Integrity
Integrity
Ciphering
Ciphering
Ciphering
AM
AM
AM/UM
PDCP
RLC
TM
CCCH
DCCH
DCCH
OCNG Generator
MAC
PHY
UE Operation in Normal Mode
Figure 4.2.8-1: Test model for testing with OCNG
ETSI
DTCH
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.9
55
ETSI TS 136 523-3 V13.2.0 (2017-03)
Device-to-Device Proximity Services test model
Figure 4.2.9-1: D2D ProSe test model
For testing of Device-to-Device Proximity Services (D2D ProSe), the system simulator (SS) shall implement, in
addition to one or several simulated E-UTRA cells (L1/L2), one or several simulated UEs (L1/L2), called hereafter SSUE. An SS-UE is used to send/receive data with the UE under test over the PC5 interface. This is depicted in the D2D
ProSe test model of Figure 4.2.9-1.
From a TTCN architecture point of view Figure 4.2.9-2 depicts the TTCN component model used for D2D ProSe.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
56
ETSI TS 136 523-3 V13.2.0 (2017-03)
Figure 4.2.9-2: D2D ProSe component model
An SS-UE is controlled by TTCN in the SideLink PTC and is configured for Direct Discovery or Direct
Communication by TTCN over sidelink system control SL_SYS port.
The ProSe Function is simulated in the ProSe_PTC. The HTTP_ProSe_PTC takes care about extracting and embedding
PC3 messages from/into HTTP requests and responses and to generate the trigger for network-initiated procedures
(OMA PUSH). There are no PC3 interface specific system ports, i.e. PC3 messages are IP user data in terms of clause
4.2.4.
4.2.9.1
ProSe Function test model
The PC3 Control Protocol procedures between the UE and the ProSe Function can be tested by TTCN at the
ProSe_PTC. The ProSe_PTC handles ProSe discovery messages and procedures as defined in TS 24.334 [61].
The purpose of the HTTP_ProSe_PTC is to emulate the transport protocol for PC3 Control Protocol messages. It is
responsible to receive HTTP requests addressing the ProSe function in UL, for encoding and decoding of the ProSe
discovery messages and to provide the HTTP responses with all relevant headers in DL.
In addition the HTTP_ProSe_PTC provides means to trigger network-initiated procedures (e.g. OMA PUSH) and is
used for HTTP based authentication (e.g. GBA).
4.2.9.2
Direct Discovery test model
The UE under test is configured in normal mode.
The SS-UE is configured in coverage. L1 and MAC are configured in normal way, they shall perform all of their
functions. The SL_DATA port for transmission and reception of SL-DCH message, i.e. PC5_DISCOVERY messages,
is above MAC.
On UE side integrity in SL-DCH message is applied. TTCN in SL_UE PTC provides the integrity functionality for the
SL-DCH messages:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
57
ETSI TS 136 523-3 V13.2.0 (2017-03)
-
In reception, SS-UE shall report to TTCN the SL-DCH message, containing the Message Code Integrity (MIC),
with the SFN/Subframe at which the message was received. TTCN shall check the MIC field.
-
In transmission, TTCN computes the MIC before sending the SL-DCH messages to SS-UE.
The SS-UE is configured by TTCN over sidelink system control port to receive/transmit SLSS. The SS-UE shall report
SLSS reception over the sidelink system indication port.
4.2.9.3
Direct Communication test model
The UE under test is configured in normal mode or in Test loop mode E, ciphering (PDCP on STCH) is not enabled
unless specified otherwise in the test case and ROHC is not configured.
The SS-UE is configured in coverage or out of coverage. L1, MAC and RLC are configured in normal way, they shall
perform all of their functions. PDCP is configured in normal mode or in 'no header manipulation' special mode in STCH
security test cases:
-
When configured in normal mode, PDCP shall perform all of its functions. PDCP ciphering is not enabled unless
specified otherwise in the test case and ROHC is not configured.
-
When configured in 'no header manipulation' mode, no header manipulation shall be performed in PDCP layer in
both directions: the SS-UE shall not add PDCP header (in transmission) and remove PDCP Header (in
reception). PDCP state variables shall be maintained by SS-UE PDCP layer. PDCP ciphering is enabled when
specified in the test and ROHC is not configured.
The SL_DATA port for transmission and reception of STCH data is above PDCP. The STCH data is considered as raw
data.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.2.10
58
ETSI TS 136 523-3 V13.2.0 (2017-03)
SC-PTM test model
Figure 4.2.10-1: Test model for SC-PTM testing
The UE is configured in Test Loop Mode F to count the successfully received MBMS Packets. On the UE side,
Ciphering/Integrity (PDCP and NAS) are enabled on SRBs/DRB. No security is configured on SC-MCCH/SC-MTCH.
On the SS side, the cell is configured as a normal cell, the SC-PTM parameters are configured by using an additional
call of SYSTEM_CTRL_REQ. L1, MAC and RLC are configured for SC-MCCH/SC-MTCH in normal mode; they
shall perform all of their functions. Existing MRB port will be reused for routing SC-MRB data.
The SC-MRB data is considered as raw data that shall not be multiplexed with the data from other RBs and shall be sent
in one MAC PDU and in one TTI. DL Scheduling assignments are configured from TTCN over system control port.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.3
SAE Test Model
4.3.1
NAS Test Model
59
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN
Data co-ord ports
NASIntegrityAlgorithm
If a NAS message is included:
Downlink: Encode the NAS
message, perform security
protection and add to the outgoing
RRC message
In the TTCN3 code the NAS
messages are coded
according to the TTCN3
defined types. The
encoding/decoding and the
security protection is handled
by the NAS emulator, not the
Test case
Uplink: Extract the NASDedicatedInformation, decipher
and check the integrity on the
received message, then decode
into the TTCN3 defined type
NAS Emulator PTC
Test Case
NASCiphering
NASDeciphering
External functions for
NAS Security
Config co-ord ports
Port for SRB
TTCN3 codec
Protocol stack of lower layers (PDCP, RLC, MAC, PHY…)
Figure 4.3.1-1: NAS Test Model
The NAS emulator is a parallel test component which handles NAS security, with the help of external functions to
perform the integrity and (de)ciphering.
The interface between the emulator and the TTCN (co-ordination messages) handle data as TTCN-3 values. The
interface between the emulator and the SS handles the RRC messages as TTCN-3 values, containing (where applicable)
secure, encoded NAS messages.
The NAS emulator is not part of the test case in terms of verdict assignment (i.e. it does not check the correctness of any
protocol message). Nevertheless, in case of fatal errors such as encode/decode errors, the NAS emulator sets the verdict
to inconclusive and terminates immediately - which causes the test case to terminate. I.e. the NAS emulator does not
resolve error situations.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
60
ETSI TS 136 523-3 V13.2.0 (2017-03)
4.4
Inter RAT Test Model
4.4.1
E-UTRAN-UTRAN Inter RAT Test Model
TTCN CODE
E-UTRAN PTC
DRB
SRB2-SRB0
UTRAN PTC
Config/Contro
l
RAB
SRB0-SRB4
RRC/NAS
Emulator
Integrity
PDCP
PDCP
RRC [Int]
Emulator&
Dir. Tx
Ciphering
RLC
RLC
Ciphering
[AM/UM/TM]
Ciphering
MAC
[AM/UM/TM]
MAC
PHY
PHY
UE in Normal Mode
Figure 4.4.1-1: Test model for Inter RAT E-UTRAN-UTRAN testing
The model consists of dual protocol stack one for E-UTRAN and one for UTRAN. The TTCN implementation for
E-UTRAN and UTRAN functionalities will be in separate Parallel Test Components. The SS E-UTRAN part is same as
the model defined in clause 4.2.2 for RRC testing.
The SS UTRAN part consisting of PHY, MAC, RLC and PDCP (optionally) (IF PS user RB established only), are
configured in normal mode. They shall perform all of their functions normally. Ciphering is enabled and shall be
performed in RLC (AM/UM) and MAC (TM RLC). Integrity is enabled, and SS shall provide RRC emulator for
integrity protection calculation and checking and 'Direct transfer' adaptation. Ports are above RLC (CS RAB and
SRB0), PDCP (PS RAB) and RRC Emulator (SRB1 to SRB4).
The UE is configured in normal mode. Ciphering/Integrity (PDCP and NAS) are enabled and ROHC is not configured
in E-UTRAN. Ciphering is enabled in UTRAN.
4.4.1.1
User data over UTRAN
User data transferred over UTRAN is distinguished between:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
61
ETSI TS 136 523-3 V13.2.0 (2017-03)
Raw user data (raw mode),
IP data (IP mode).
Depending upon whether the user data is relevant for the purpose of test, several scenarios are listed:
Raw user data relevant for the purpose of test,
IP data relevant for the purpose of test,
IP data, considered as IP signalling, not directly relevant for the purpose of test.
4.4.1.1.1
Raw user data over UTRAN
The raw user data can be as RLC SDUs and PDCP SDUs. The DL and UL user data are routed to UTRAN_PTC (Fig.
4.4.1.1.2-1). The IP stack in SS is not involved for all raw user data applications.
RLC SDUs is applied if the test loop mode 1 with loopback of RLC SDUs in TS 34.109 [9] is activated. PDCP in SS is
not configured in this case; the DL and UL user data are routed to UTRAN_PTC via the RLC port.
The raw user data as PDCP SDUs is applied in the following cases:
the test loop mode 4 (TS 34.109 [9]) is activated,
the test loop mode 1 is activated with loopback of PDCP SDUs (TS 34.109 [9]),
the test loop mode B (TS 36.509 [4]) is activated and raw data is looped back on UTRAN,
IP raw data is another type of raw user data. The test loop mode is not activated. This case is applied when sending
uplink data is triggered by the upper tester.
PDCP and optional RoHC are configured in SS, the DL and UL user data are routed to UTRAN_PTC via the PDCP
port.
Feeding raw user data is largely used in the pure UTRAN test in TS 34.123-3 [7].
4.4.1.1.2
IP data over UTRAN
The IP data over UTRAN is applied to E-UTRA-UTRAN I-RAT and UTRAN test cases. The IP stack in SS is
involved. IP data is considered as:
IP packets data (IP mode) relevant for the purpose of test,
IP signalling (IP mode), to be handled in TTCN at IP Layer
One of the IP signalling handling is the stateless address auto configuration for IPv6, illustrated in Fig. 4.4.1.1.2-1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
62
ETSI TS 136 523-3 V13.2.0 (2017-03)
UTRA_PTC
IP_PTC
IP Data
DAT A
IP _DATA
ICMPv6 Server
test case re levant
IP Data
CTRL
CTRL
IP_CTRL
DHC P
Data
CTRL
Socket
Control
Routing
C ontrol
MUX/Filter
Socke t
Ctr l
IP-Dat a
IP_S OCK
PDCP
L2 Data
IP _CTRL
IP Data,
Socke t C trl
S ystem I nterface
IP_SOCK
PDC P
IP-Data
IP _CTRL
Socket
Ctrl
Routi ng
Ctrl
IP stack
raw mode
IP mode
DRB-MUX
EUTRA:
Cellx, DRBy
Cellx
PDCP
Routing
Table
GERAN
System Adaptor
UTRAN:
Cellx RBy
Figure 4.4.1.1.2-1: UTRAN IP test model with an ICMPv6 server
4.4.1.1.3
Routing IP data
The routing of user data is the function of DRB-Mux and controlled by a routing table.
If there is no entry in the routing table for a given RB, it is considered being in raw mode, raw user data is routed to
or from the UTRAN PDCP port.
If there is an entry in the routing table for a given RB, it is considered being in IP mode, IP data is routed to or from
the IP stack.
For EUTRA-UTRAN or UTRAN test, the routing entry parameters in the DRB-Mux's routing table are specified as
(RAT=Utran, cell-id=-1, RB id). SS PDCP entity does not belong to a particular cell; the cellId shall be assigned to the
value -1. Consequently, the UTRAN cell id provided in DRB-Mux is set to cell-id=-1.
IP protocol information of IP data (protocol, local IP address, local port, remote IP address, and remote port) is also
provided in the routing table. More information can be found in 4.2.4.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.4.2
63
ETSI TS 136 523-3 V13.2.0 (2017-03)
E-UTRAN-GERAN Inter RAT Test Model
TTCN CODE
E-UTRAN PTC
DRB
SRB2-SRB0
GERAN PTC
Config/Contro
l
SAPI0
SAPI1, 3
RRC/NAS
Emulator
Integrity
PDCP
SNDCP
Ciphering
LLC
RLC
[AM/UM/TM]
Ciphering
RLC/MAC
MAC
L2
L1
PHY
Ciphering
UE in Normal Mode
Figure 4.4.2-1: Test model for Inter RAT E-UTRAN-GERAN testing
The model consists of dual protocol stack one for E-UTRAN and one for GERAN. The TTCN implementation for
E-UTRAN and GERAN functionalities will be in separate Parallel Test Components. The SS E-UTRAN part is the
same as the model defined in clause 4.2.2 for RRC testing.
The SS GERAN model for GPRS consists of L1, MAC/ RLC and LLC, configured in normal mode. SNDCP may also
be configured. If SNDCP is configured, this shall reference the LL Entity by the LLMEId. They shall perform all of
their functions normally. Ciphering is enabled and shall be performed in LLC. XIDs shall be sent/received by the TTCN
and the TTCN will then send the XID information to the SS using the G_CLLC_XID_Config_REQ ASP. Ports are
above RLC (GRR messages), LLC (NAS and Data) and SNDCP (User Data).
The SS GERAN model for GSM consists of L1, L2 (MAC/ RLC), configured in normal mode. They shall perform all
of their functions normally. Ciphering is enabled and shall be performed in L1. Ports are above L2.
The UE is configured in normal mode. Ciphering/Integrity (PDCP and NAS) are enabled and ROHC is not configured
in E-UTRAN. Ciphering is enabled in GERAN.
4.4.2.1
User data over GERAN
User data transferred over GERAN is distinguished between:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
64
ETSI TS 136 523-3 V13.2.0 (2017-03)
Raw user data (raw mode),
IP data (IP mode).
Depending upon whether the user data is relevant for the purpose of test, several scenarios are listed:
Raw user data relevant for the purpose of test,
IP data relevant for the purpose of test,
IP data, considered as IP signalling, not directly relevant for the purpose of test.
4.4.2.1.1
Raw user data over GERAN
The raw user data can be as RLC blocks and SNDCP SDUs. The DL and UL user data are routed to GERAN PTC (Fig.
4.4.2.1.2-1). The IP stack in the SS is not involved for all raw user data applications.
RLC blocks are applied if testloop mode B (TS 36.509 [4]) is activated and raw data is looped back on GERAN.
IP raw data is another type of raw data. The testloop mode is not activated. This case is applied when sending uplink
data is triggered by the upper tester.
SNDCP and optionally RoHC are configured in the SS, DL and UL user data are routed to GERAN_PTC via the
SNDCP port.
4.4.2.1.2
IP data over GERAN
The IP data over GERAN is applied to EUTRA – GERAN I-RAT test cases. The IP stack in the SS is involved. IP data
is considered as:
-
IP packets data (IP mode) relevant for the purpose of the test,
-
IP signalling (IP mode), to be handled in the TTCN at IP layer.
One of the IP signalling handling is the stateless address auto configuration for IPv6, illustrated in Figure 4.4.2.1.2-1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
65
ETSI TS 136 523-3 V13.2.0 (2017-03)
Figure 4.4.2.1.2-1: GERAN IP test model with an ICMPv6 server
4.4.2.1.3
Routing IP data
The routing of user data is the function of the DRB-Mux and is controlled by a routing table.
If there is no entry in the routing table for a given NSAPI, it is considered to be in raw mode, raw user data is routed to
or from the GERAN SNDCP port.
If there is an entry in the routing table for a given NSAPI, it is considered to be in IP mode, IP data is routed to or from
the IP stack.
For EUTRA-GERAN, the routing entry parameters in the DRB-Mux's routing table are specified as (RAT = GERAN,
cell-id, NSAPI). IP protocol information of IP data (protocol, local IP address, local port, remote IP address, and remote
port) is also provided in the routing table. More information can be found in clause 4.2.4.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.4.3
66
ETSI TS 136 523-3 V13.2.0 (2017-03)
E-UTRAN-CDMA2000 Inter RAT Test Model
4.4.3.1
E-UTRAN-CDMA2000 HRPD Inter RAT Test Model
TTCN CODE
E-UTRAN PTC
DRB
SRB2-SRB0
HRPD PTC
Config/Control
Commands/
Indications
RLP-Flow
C2KTUNNEL
RRC/NAS
Emulator
ABOVE
HRPD
IPv4
PPP: VSNP
IPv6
PPP: VSNCP
SNP
RSP
APPLICATION
Integrity
PPP:LCP
PPP:EAP-AKA
RLP
FCP
SLP
PDCP
Ciphering
RLC
LUP
STREAM
SP
SESSION
SMP
AMP
SCP
[AM/UM/TM]
CONNECTION
MAC
SECURITY
PHY
MAC
ALMP
IR Init
SP
PCP
IR RUP
Security
E-CCH
Key Exchg
E-FTCH
IR Idle
SP
CSP
IR SAP
IR OMP
Autn
Encryp
E-ACH
PHY
UE in Normal Mode
Figure 4.4.3-1: Test model for InterRAT E-UTRAN-CDMA2000 HRPD testing
ETSI
R-TCH
3GPP TS 36.523-3 version 13.2.0 Release 13
67
ETSI TS 136 523-3 V13.2.0 (2017-03)
The model consists of a dual protocol stack, one for E-UTRAN and one for eHRPD. The TTCN implementation for
E-UTRAN and eHRPD functionalities will be in separate Parallel Test Components. The SS E-UTRAN part is same as
the model defined in clause 4.2.2 for RRC testing.
The eHRPD part emulation in SS is considered as a black box. The commands/Indications port is used for commanding
the SS to bring the UE into the desired state and monitoring the progress. The System commands and indications are
designed with principle of having minimum command/indication per eHRPD procedure hence avoid racing conditions
and timing issues. By default, the execution order of sub procedures (e.g. protocol negotiations) cannot be monitored by
TTCN. The SS emulations shall be compliant with respective 3GPP/3GPP2 core specifications and guarantee execution
order of respective eHRPD procedures as per relevant 3GPP/3GPP2 test/core specifications.
The C2KTUNNEL port is used for routing encapsulated
1. pre-registration messages (i.e. messages encapsulated in ULInformationTransfer and DLInformationTransfer) in
the EUTRAN cell to the eHRPD and
2. handover related eHRPD messages (i.e. messages encapsulated in HandoverFromEUTRAPreparationRequest/
ULHandoverPreparationTransfer/ MobilityFromEUTRACommand).
The SS eHRPD part consists of Physical, MAC, Security, Connection, Session, Stream, Application and Layers for PPP
and IP configured in normal mode. They shall perform all of their functions normally. Encryption may be enabled and
performed in security layer.
The CDMA2000 eHRPD emulation in the SS supports the following layers and protocols:
-
Physical layer (Subtype 2).
-
MAC layer:
-
-
Enhanced (Subtype 0, Subtype 1) Control Channel MAC Protocol (ECH).
-
Enhanced (Subtype 1) Forward Traffic Channel MAC Protocol (E-F-TCH).
-
Enhanced (Subtype 1) Access Channel MAC Protocol (E-ACH).
-
Subtype 3 Reverse Traffic Channel MAC Protocol (R-TCH).
Security Layer:
-
-
-
-
Default Security Protocol (Security).
Connection Layer:
-
Default Air Link Management Protocol (ALMP).
-
Default Connected State Protocol (CSP).
-
Default Packet Consolidation Protocol (PCP).
-
Inter-RAT Signalling Adaptation Protocol (IR-SAP) (required only for optimized handover).
-
Inter-RAT Initialization State Protocol (IR-Init SP) (required only for optimized handover).
-
Inter-RAT Idle State Protocol (IR-Idle SP) (required only for optimized handover).
-
Inter-RAT Route Update Protocol (IR-RUP) (required only for optimized handover).
-
Inter-RAT Overhead Messages Protocol (IR-OMP) (required only for optimized handover).
Session Layer:
-
Default Session Management Protocol (SMP).
-
Default Address Management Protocol (AMP).
-
Default Session Configuration Protocol (SCP).
Stream Layer:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
ETSI TS 136 523-3 V13.2.0 (2017-03)
Default Stream Protocol (DSP).
Application Layer:
-
-
-
68
Default Signalling Application:
-
Signalling Network Protocol (SNP).
-
Signalling Link Protocol (SLP).
Enhanced Multi-Flow Packet Application:
-
Route Selection Protocol (RSP).
-
Radio Link Protocol (RLP).
-
Location Update Protocol (LUP).
-
Flow Control Protocol (FCP).
Alternate Enhanced Multi-Flow Packet Application (to be listed along with EMPA during SCP negotiation)
Above eHRPD:
-
PPP: Vendor Specific Network Control Protocol (PPP:VSNCP).
-
PPP: Vendor Specific Network Protocol (PPP:VSNP).
-
PPP: Link Control Protocol (PPP:LCP).
-
PPP: Extensible Authentication protocol-Authentication and Key Agreement’ (PPP:EAP-AKA’).
-
IPv4.
-
IPv6.
During pre-registration phase, one cell per preRegistrationZoneID (ColorCode) to be simulated will be configured by
TTCN with power level as ‘off’, or as specified by the test case. The SS will be issued System commands for preregistration and expect the appropriate system indications.
The UE is configured in normal mode. Ciphering/Integrity (PDCP and NAS) are enabled and ROHC is not configured
in E-UTRAN. Encryption is enabled in HRPD.
4.4.3.2
E-UTRAN-CDMA2000 1xRTT Inter RAT test model
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
69
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN CODE
E-UTRAN PTC
DRB
1xRTT PTC
Config/Control
SRB2-SRB0
Commands/
Indications
RLP-Flow
C2KTUNNEL
RRC/NAS
Emulator
Integrity
PDCP
Ciphering
Supervisioning
& Config Mgmt
RLC
[AM/UM/TM]
LAC
Auth
Msg Int
Signalling
ARQ
SAR
ARQ
Utility
MAC
MAC
RLP
SRBP
Mux and
Qos
F/RPDCH
PHY
PHY
UE in Normal/Loop back
Mode
Figure 4.4.3.2-1: Test model for InterRAT E-UTRAN-CDMA2000 1xRTT testing
The 1xRTT test model consists of a dual protocol stack, one for E-UTRAN and one for 1xRTT. The TTCN
implementation for E-UTRAN and 1xRTT functionalities are in separate Parallel Test Components. The SS E-UTRAN
part is same as the model defined in clause 4.2.2 for RRC testing.
The 1xRTT part emulation in SS is considered as a black box. The commands/Indications port is used for commanding
the SS to bring the UE into the desired state and monitoring the progress. The System commands and indications are
designed with principle of having minimum command/indication per 1xRTT procedures hence avoid racing conditions
and timing issues. By default, the execution order of sub procedures(e.g. protocol negotiations) cannot be monitored by
TTCN. The SS emulations shall be compliant with respective 3GPP/3GPP2 core specifications and guarantee execution
order of respective 1xRTT procedures as per relevant 3GPP/3GPP2 test/core specifications.
The C2KTUNNEL port is used for routing encapsulated
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
70
ETSI TS 136 523-3 V13.2.0 (2017-03)
1. pre-registration messages (i.e. messages encapsulated in CSFBParametersResponseCDMA2000,
ULInformationTransfer and DLInformationTransfer) in the EUTRAN cell to the 1xRTT and
2. handover, e-CSFB related 1xRTT messages (i.e. messages encapsulated in
HandoverFromEUTRAPreparationRequest/ ULHandoverPreparationTransfer/
MobilityFromEUTRACommand).
The SS 1xRTT part consists of Physical, MAC, LAC, Session, Stream, Application and Layers for PPP and IP
configured in normal mode. They shall perform all of their functions normally. Encryption may be enabled and
performed in security layer.
The CDMA2000 1xRTT emulation in the SS supports the following layers and protocols:
-
Physical layer.
-
MAC layer:
-
-
-
Signalling Radio Burst protocol.
-
Radio Link Protocol for Data services.
-
Forward and Reverse Packet Data Channel functions.
-
Multiplexing and QoS Delivery.
Link Access Control:
-
Authentication and Message Integrity sublayer [optional].
-
ARQ sublayer.
-
Addressing.
-
Utility.
-
Segmentation and Reassembly.
Layer 3:
-
Super visioning and Configuration Management.
-
Signalling Protocol.
During pre-registration phase, one cell per preRegistrationZoneID (ColourCode) to be simulated will be configured by
TTCN with power level as ‘off’, or as specified by the test case. The SS will be issued System commands for preregistration and expect the appropriate system indications.
The UE is configured in normal mode or loop back mode. Ciphering/Integrity (PDCP and NAS) are enabled and ROHC
is not configured in E-UTRAN. Encryption may be enabled in 1xRTT.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.4.4
71
ETSI TS 136 523-3 V13.2.0 (2017-03)
E-UTRAN FDD-TDD Inter RAT Test Model
TTCN CODE
E-UTRAN [FDD/TDD] PTC
DRB
SRB2-SRB0
Config/Control
RRC/NAS
Emulator
Integrity
RRC/NAS
Emulator
PDCP
Integrity
PDCP
Ciphering
Ciphering
RLC
RLC
[AM/UM/TM]
[AM/UM/TM]
MAC
MAC
PHY [FDD]
PHY [TDD]
UE in Normal Mode
Figure 4.4.4-1: Test model for Inter RAT E-UTRANFDD-TDD testing
The model consists of dual protocol stack one for E-UTRANFDD and one for E-UTRANTDD. The TTCN
implementation for E-UTRANFDD and TDD functionalities will be in the same Parallel Test Component. The SS
E-UTRAN (both FDD and TDD) part is the same as the model defined in clause 4.2.2 for RRC testing. SS
E-UTRANFDD and TDD shall be configured as separate cells.
The UE is configured in normal mode. Ciphering/Integrity (PDCP and NAS) are enabled and ROHC is not configured
for both FDD and TDD.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.4.5
72
ETSI TS 136 523-3 V13.2.0 (2017-03)
E-UTRAN-UTRAN-GERAN Inter RAT Test Model
TTCN CODE
E-UTRAN PTC
DRB
SRB2-SRB0
UTRAN PTC
Config/Control
GERAN PTC
SAPI0
SRB0-SRB4 Config/Control SAPI1, 3
RAB
RRC/NAS
Emulator
Integrity
PDCP
PDCP
RRC [Int]
Emulator&
Dir. Tx
Ciphering
RLC
[AM/UM/TM]
RLC
Ciphering
[AM/UM/TM]
Ciphering
MAC
MAC
SNDCP
LLC
Ciphering
RLC/MAC
L2
L1
PHY
PHY
Ciphering
UE in Normal Mode
Figure 4.4.5-1: Test model for Inter RAT E-UTRANFDD-TDD testing
The model consists of integrated protocol stack supporting E-UTRAN, UTRAN and GERAN. The TTCN
implementation for E-UTRAN, UTRAN and GERAN functionalities will be in separate Parallel Test Components. The
SS E-UTRAN part is the same as the model defined in clause 4.2.2 for RRC testing. The SS UTRAN part is the same as
the model defined in clause 4.4.1. The SS GERAN part is same as the model defined in clause 4.4.2.
The UE is configured in normal mode. Ciphering/Integrity (PDCP and NAS) are enabled and ROHC is not configured
in E-UTRAN. Ciphering/Integrity are enabled in UTRAN. Ciphering is enabled in GERAN.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.4.6
73
ETSI TS 136 523-3 V13.2.0 (2017-03)
3GPP-WLAN Inter working Test Model
4.4.6.1
E-UTRAN-WLAN Inter working Test Model
TTCN CODE
E-UTRAN PTC
DRB
SRB2-SRB0
WLAN PTC
Commands/
Indications
Config/Control
RRC/NAS
Emulator
EAPAKA
IKEv2
DNS
IPSec
IPv4/v6
Integrity
PDCP
Ciphering
ANQP/HS 2.0 ANQP Element
RLC
[AM/UM/TM]
WLAN
Station
Management
Entity
MAC
MAC
Mangmnt
Entity
WLAN
MAC
Phy
Mangmnt
Entity
WLAN
PHY
MAC
Sublayer
PHY
UE in Normal Mode
Figure 4.4.6.1-1: Test model for E-UTRAN-WLAN interworking testing
ETSI
PLCP
PMD
3GPP TS 36.523-3 version 13.2.0 Release 13
74
ETSI TS 136 523-3 V13.2.0 (2017-03)
The model consists of a dual protocol stack, one for E-UTRAN and one for WLAN. E-UTRAN and WLAN
functionalities are implemented in separate Parallel Test Components in the TTCN. The SS E-UTRAN part is the same
as the model defined in clause 4.2.2 for RRC testing. The WLAN part is specified in clause 4.5.
The UE is configured in normal mode. Ciphering/Integrity (PDCP and NAS) are enabled and ROHC is not configured
in E-UTRAN.
NOTE:
The working assumption is that the UE supports IP address preservation. Therefore the UE includes
INTERNAL_IP4_ADDRESS or the INTERNAL_IP6_ADDRESS attribute or both in the
CFG_REQUEST Configuration Payload within the IKE_AUTH request message. The ePDG then relays
in the IKEv2 Configuration Payload (CFG_REPLY) of the final IKE_AUTH response message the
remote IP address information to the UE. Reference 24.302 [67] clause 7.2.2(UE) and 7.3.1(ePDG).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.4.6.2
75
ETSI TS 136 523-3 V13.2.0 (2017-03)
UTRAN-WLAN Inter working Test Model
TTCN CODE
UTRAN PTC
RAB
SRB0-SRB4
PDCP
Ciphering
RRC [Int]
Emulator&
Dir. Tx
WLAN PTC
Commands/
Indications
Config/Control
EAPAKA
IKEv2
DNS
IPSec
IPv4/v6
RLC
[AM/UM/TM]
ANQP/HS 2.0 ANQP Element
Ciphering
MAC
WLAN
Station
Management
Entity
PHY
MAC
Mangmnt
Entity
WLAN
MAC
Phy
Mangmnt
Entity
WLAN
PHY
MAC
Sublayer
PLCP
PMD
UE in Normal Mode
Figure 4.4.6.2-1: Test model for UTRAN-WLAN interworking testing
The model consists of a dual protocol stack, one for UTRAN and one for WLAN. UTRAN and WLAN functionalities
are implemented in separate Parallel Test Components in the TTCN. The SS UTRAN part is the same as the model
defined in clause 4.4.1. The SS WLAN part is defined in clause 4.5.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4.5
76
ETSI TS 136 523-3 V13.2.0 (2017-03)
Generic WLAN Test Model
The generic WLAN test model is applicable for IMS over WLAN testing, as well as for E-UTRAN/UTRAN-WLAN
interworking testing. The TTCN and SS implementations emulate an untrusted Non-3GPP IP Access as specified in
TS 23.402 [63]: There is the WLAN access point (WLAN AP) and the emulation of ePDG and AAA-server.
4.5.1
WLAN Access Point
The WLAN access point emulation is done at the SS with a few configuration parameters provided by TTCN. The
following layers need to be supported:
-
Station Management Entity
-
Physical layer:
-
-
-
Physical Sublayer Management Entity
-
Physical layer Convergence procedure
-
Physical Medium Dependent
MAC layer:
-
MAC Management Entity
-
MAC sublayer
-
Also contains security services
ANQP element and HS 2.0 ANQP Network elements
WLAN security protocol using WPA/WPA2 algorithms shall be supported.
4.5.2
ePDG/AAA-Server Emulation
An IPsec tunnel is established between the UE being in the untrusted network and the ePDG: Establishment,
maintenance and release of the IPsec tunnel requires IP signalling between the tunnel end-points (UE, ePDG) according
to RFC 5996 [64] and TS 33.402 [25]. IP data between the UE and the emulated 3GPP network is transferred through
the IPsec tunnel by using UDP Encapsulation of IPsec ESP Packets according to RFC 3948 [65].
Figure 4.5.2-1 shows the principle of the IPsec tunnel. Note that the IP addresses of 3GPP and non-3GPP network shall
be different.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
77
ETSI TS 136 523-3 V13.2.0 (2017-03)
Figure 4.5.2-1: IPsec tunnel for untrusted Non-3GPP IP Access to 3GPP network
During establishment of the IPsec tunnel, parameters for authentication and authorization (EAP AKA) are exchanged
between the ePDG and the AAA-server (see TS 33.402 [25] clause 8).
The means for establishment, maintenance and release of the IPsec tunnel shall be provided by the SS. The TTCN does
not deal with IKE messages as such. In addition to the IP test model of clause 4.2.4 there are the following requirements
for SS implementation:
-
IPsec tunnelling according to RFC 5996 [64] (IKEv2) and RFC 3948 [65]
-
Emulation of EAP AKA according to RFC 4187 [66] i.e. interworking between IPsec (ePDG) and emulated
AAA-server
The enhancement of the common IP test model of clause 4.2.4 is shown in figure 4.5.2-2.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
78
ETSI TS 136 523-3 V13.2.0 (2017-03)
Figure 4.5.2-2: Generic WLAN Test Model
Further implementation requirements:
IPsec tunnel handling is controlled by the TTCN with static parameters
-
DNS for dynamic selection of the ePDG is handled in the TTCN according to the common IP test model
-
DHCP and ICMPv6 can be handled in the TTCN when needed (as for E-UTRA or UTRAN)
-
IMS SIP/SDP signalling is handled in the TTCN as for E-UTRA or UTRAN
-
RTP/RTCP loopback model can be configured in the same way as for E-UTRA
-
Routing of IP packets from and to WLAN is controlled by the DRB-Mux in the same way as for E-UTRA or
UTRAN
In the context of the IPsec tunnel, logically two instances of the DRB-Mux can be considered:
-
Uplink
-
lower DRB-Mux to distinguish whether a UDP packet is IKE or ESP data
-
-
an IKE or ESP packet needs to be routed to the IPsec tunnel
upper DRB-Mux to handle IP packets coming out of the IPsec tunnel
Downlink
-
upper DRB-Mux to distinguish whether an IP packet shall be sent into the IPsec tunnel
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
79
ETSI TS 136 523-3 V13.2.0 (2017-03)
lower DRB-Mux to determine routing of IKE/ESP packets (i.e. the packets inside the tunnel)
4A
NB-IoT system architecture and test models
4A.1
Test system architecture
The principles outlined in clause 4.1 apply also to the case of NB-IoT.
For NB-IoT conformance tests, NB-IoT is considered as a separate radio access technology (RAT) and is hosted by a
separate TTCN-3 parallel component (PTC).
4A.2
NB-IoT test models
4A.2.1
Layer 2 test models
4A.2.1.1
Layer 2 loopback mode for CP mode
Layer 2 test cases for control plane mode (CP mode) are using UE test loop mode G or H according to TS 36.509 [4]
with GH_RLC_SDU_loopback set to true. In this mode the UE is still able to receive RRC and NAS messages but in
case of ESM DATA TRANSPORT (UE test loop mode G) or CP DATA (UE test loop mode H) the UE takes the user
data of the DL NAS message and uses it as RLC SDU in UL.
At the SS, depending on the requirements of the particular test case, RLC layer and MAC layer may be configured in
transparent mode to allow TTCN the control over RLC and MAC layers. This requires that the RRC message
DLInformationTransfer-NB and the contained ESM DATA TRANSPORT or CP DATA are fully encoded (including
NAS security protection). To avoid inconsistencies of the NAS COUNTs, TTCN still uses the NAS emulator. But in the
DL instead of sending the messages to the SS, the NAS emulator encodes and ciphers a message and gives the encoded
octetstring back to the test case implementation at the NBIOT PTC. The exchange of the respective L2 PDUs happens
at the L2DATA port instead of the SRB port. Therefore the SS gets configured for an L2TestMode in which the L2 UL
and DL messages shall be routed to/from L2DATA port and there is no signalling via the SRB port anymore as long as
the L2TestMode is activated.
In contrast to L2 tests on DRBs the RLC counts VTS and VRR need to be:
-
retrieved from the SS before configuring the RLC into transparent mode,
-
maintained in TTCN while the test mode is active,
-
restored at the SS after the RLC layer gets re-configured back to normal operation.
NOTE:
For NB-IoT in CP mode there is no PDCP.
Figure 4A.2.1.1-1 illustrates the layer 2 loopback mode.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
80
ETSI TS 136 523-3 V13.2.0 (2017-03)
NBIOT L2 CP test case (TTCN-3)
NB_L2_DATA_REQ
NB_L2_DATA_IND
L1/2 configuration for
L2 CP test cases
NB_L2_SDU_MSG
NB_SYSTEM port
NB_L2_DATA port
NB_L2_SRB port
NB_SRB_COMMON_IND
NAS_CTRL_REQ
NB_SRB_COMMON_REQ
NAS_CTRL_CNF
NB_SRB port
NASCTRL port
SRB1/SRB1bis:
RRC only
RRC+ NAS,
NAS only
NASCount
Security
L2 SDU (bitstring)
RRC
codec
NAS
Security
(per UE)
NAS
codec
Test mode / normal mode
routing
RRC PDU
NAS Emulation (TTCN-3)
SRB0:
RRC
only
NB_RRC_PDU_REQ/ NB_RRC_PDU_I ND
SRB port
System Interface
NB_SYSTEM port
NB_L2_DATA port
L2TestMode (disabled | enabled)
SRB port
normal mode
L2TestMode
RLC Counts Get/Set
RLC
NB_RLC_RbConfig (AM | TM)
NB_MAC_TestModeConfig (None | Transparent)
MAC
Figure 4A.2.1.1-1: Layer 2 loopback mode
ETSI
System Adaptor
3GPP TS 36.523-3 version 13.2.0 Release 13
4A.2.1.2
81
ETSI TS 136 523-3 V13.2.0 (2017-03)
MAC test model (CP mode)
TTCN CODE
Config/Control
RLC
SRB1bis
SRB1bis
TM
TM
DCCH
DCCH
MAC
(transparent mode)
PHY
Loopback above RLC in UE
Figure 4A.2.1.2-1: Test model for MAC testing in NB-IoT CP mode
In general NB-IoT MAC test cases are implemented for control plane mode using loopback mode as described in clause
4A.2.1.1. At the SS RLC and MAC layer are configured in transparent mode with L2TestMode enabled. Transparent
mode means that the TTCN fully controls processing of the RLC and MAC PDUs including padding and the SS is
responsible for encoding and decoding of the MAC PDUs only.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4A.2.1.3
82
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC test model (CP mode)
TTCN CODE
Config/Control
RLC
SRB1bis
SRB1bis
TM
TM
DCCH
DCCH
MAC
PHY
Loopback above RLC in UE
Figure 4A.2.1.3-1: Test model for RLC testing in NB-IoT CP mode
In general NB-IoT RLC test cases are implemented for control plane mode using loopback mode as described in clause
4A.2.1.1. At the SS RLC layer is configured in transparent mode with L2TestMode enabled. Transparent mode means
that the TTCN fully controls processing of the RLC PDUs and the SS is responsible for encoding and decoding of the
RLC PDUs only.
Only RLC AM mode of operation is used. On the SS Side, L1 and MAC are configured in the normal way. The UL
Scheduling Grant and DL Scheduling assignments are configured from TTCN over the SRB1bis port.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4A.2.1.4
83
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP test model
TTCN CODE
SRB1
DRB
DRB
Ciphering
Ciphering
PDCP
RLC
AM
AM
DTCH
DTCH
MAC
PHY
Loopback above PDCP in UE
Figure 4A.2.1.4-1: Test model for PDCP testing
In general the UE is configured in Test Loop Mode A, to loop back the user domain data above PDCP layer. Ciphering
is optionally configured on UE side. PDCP test cases require the UE to support NB-IoT user plane mode.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
4A.2.2
84
ETSI TS 136 523-3 V13.2.0 (2017-03)
RRC / NAS test model
TTCN CODE
UP
CP
SRB1bis
SRB0
SRB1
DRB
Control
RRC/NAS Emulator
with NAS Integrity & Ciphering
Integrity
PDCP
Ciphering
AM
DCCH
TM
CCCH
AM
DCCH
Ciphering
AM
RLC
DTCH
MAC
PHY
UE Operation in Normal Mode
Figure 4A.2.2-1: Test model for NB-IoT RRC/NAS testing
The UE is configured in normal mode. On UE side NAS security (ciphering/integrity) is enabled and ROHC is not
configured. For UP, PDCP and AS security (ciphering/integrity) are enabled.
On the SS Side L1, MAC and RLC are configured in normal mode. They shall perform all of their functions. For SRB0
the DL and UL port is above RLC. For SRB1/SRB1bis the port is above/below the RRC and NAS emulator, which is
implemented as a parallel test component. NAS security (integrity/ciphering) is enabled. For UP, PDCP is configured
in normal mode and the DRB port is above PDCP. AS security (ciphering/integrity) is enabled.
The NAS emulator for SRB1/SRB1bis shall provide the ciphering and integrity functionality for the NAS messages. In
the UL direction, the SS shall report RRC messages, still containing (where appropriate) the secure and encoded NAS
message, to the RRC port. In DL, RRC and NAS messages with same timing information shall be embedded in one
PDU after integrity and ciphering for NAS messages.
The UL Scheduling Grant and DL Scheduling Assignments are configured from TTCN over the system control port.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
5
85
ETSI TS 136 523-3 V13.2.0 (2017-03)
Upper Tester Interface
This clause describes the handling of Upper Tester Commands at the system interface. The internal handling of those
commands in TTCN is out of scope.
In the TTCN, the Upper Tester is located at the MTC; therefore there is one interface to the system adaptor common for
all RATs.
5.1
Definitions
Upper test (UT) commands are commands at the UT interface and can be distinguished as:
-
AT commands:
Well-defined commands specified in 3GPP core specifications like TS 27.007 [32].
At the UT interface AT commands shall be used as defined in the core specifications. It is out of scope of the
TTCN implementation whether or not an AT command is supported by the UE and whether automatic operation
or manual intervention is used.
All AT commands are sent as AT command strings as defined in clause 5.2. If an AT command is not
implemented in the UE, the system adaptor needs to parse the AT command and map it to an appropriate
proprietary command (which is out of scope for this document). If required, the system adaptor then also needs
to provide a response appropriately formatted as an AT string, as expected by the TTCN.
-
MMI commands:
In context of this specification MMI commands are commands for which there is no AT command defined in
any core specification. This is independent from the operation (manual or automatic).
For each UT command the interactions between the system adaptor and the UE can be distinguished as either an
automatic operation or requiring manual intervention.
-
Automatic operation:
There is no interaction needed by the test operator i.e. the UT command is performed automatically (e.g. by
using the UE's AT command interface). It is up to the system adaptor implementation to use the given UT
command or map it to proprietary UE command(s) depending on each UE implementation (see clause 5.2).
-
Manual intervention:
The UT command is performed by a test operator (e.g. by manual handling of the UE). The interaction between
the SS and the operator, and the operator and the UE is up to the system adaptor implementation and out of
scope for TTCN.
The TTCN implementation shall be the same for both modes. There shall be no difference between automatic operation
and manual intervention.
NOTE:
5.2
Annex E shows message flows for manual intervention and automatic operation in different scenarios.
This illustrates the behaviour at the system adapter and shows that the behaviour is the same in TTCN for
both modes.
Upper Tester ASPs
There is one primitive defined carrying either an MMI or an AT command to be sent to the system adaptor and one
common confirmation primitive to be sent by the system adaptor.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Type Name
TTCN-3 Type
Cmd
AT
MMI
CnfRequired
86
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 ASP Definition
UT_SYSTEM_REQ
Record
TTCN-3 Type
union
charstring carrying the AT command as defined in TS 27.007 [32],
TS 27.005 [31] and TS 27.060 [33]
- Cmd (charstring)
- List of parameters:
- Name (charstring)
- Value (charstring)
TTCN-3 Type
Ut_CnfReq_Type
CNF_REQUIRED: SS shall reply with one confirmation (NOTE)
NO_CNF_REQUIRED: SS shall swallow any confirmation generated
NOTE:
LOCAL_CNF_REQUIRED: SS shall immediately send one
confirmation when the command is submitted to the UE i.e.
in case of operator interaction when the operator has
confirmed the command, but SS shall not wait for the UE
responding(NOTE)
In the TTCN, a confirmation shall only be requested in cases when there is no signalling from the UE
being triggered by the MMI/AT command
Type Name
TTCN-3 Type
Result
ResultString
TTCN-3 ASP Definition
UT_COMMON_CNF
Record
TTCN-3 Type
boolean
true: success
false: failure
NOTE:
In case of AT commands, the SS shall return false if and
only if the UE comes back with "ERROR" as result code according to
ITU-T Rec V.250 clause 5.7 [60]. In case of e.g. "+CME ERROR" the
SS shall return true and put the UE's response into the ResultString
TTCN-3 Type
charstring
response by the UE for commands which request the UE to return a
result, optional
In case of AT commands, ResultString shall contain the complete line
according to the specification of the AT command.
The following MMI commands are defined.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
87
Table 5.1: MMI commands
ETSI
ETSI TS 136 523-3 V13.2.0 (2017-03)
3GPP TS 36.523-3 version 13.2.0 Release 13
88
Command
ETSI TS 136 523-3 V13.2.0 (2017-03)
Parameters
Value
(none)
(none)
(none)
(none)
"USIM"
<USIM>
(none)
"PLMN"
<PLMN ID>
“WARNING1”
<WARNING1>
“WARNING2”
<WARNING2>
(none)
(none)
“WARNING1”
<WARNING1>
“WARNING2”
<WARNING2>
(none)
(none)
(none)
"Length"
<Length>
"Msg"
<Msg>
"Length"
<Length>
"Msg"
<Msg>
(none)
(none)
(none)
(none)
Name
"SWITCH_ON"
"SWITCH_OFF"
"POWER_ON"
"POWER_OFF"
"INSERT USIM"
"REMOVE_USIM"
"CHECK_PLMN"
"CHECK_ETWS_INDICATION"
“CHECK_ETWS_ALERT”
“CHECK_ETWS_NO_ALERT”
"CHECK_CMAS_INDICATION"
“CHECK_CMAS_ALERT”
“CHECK_CMAS_NO_ALERT”
"HRPD_PDN_CONNECTION”
“CHECK_MESSAGE_DISPLAYED”
“CHECK_SMS_LENGTH_CONTENT
S"
"CONFIGURE_SMS_ONLY"
"DISABLE EPS CAPABILITY"
"DETACH_NON_EPS"
"CLEAR_STORED_ASSISTANCE_D
ATA"
"CHECK_DTCH_THROUGHCONNEC
TED"
"GERAN_UPLINK_DATA"
"SELECT_CSG"
“TRIGGER_USER_RESELECTION”
"REQUEST_NON_CALL_RELATED_
SS"
"MBMS_SERVICE_INTEREST"
“MBMS_SERVICE_ACTIVE”
“MBMS_PRIORITY_OVER_UNICAST
”
"CHECK_ETWS_NO_INDICATION"
"CHECK_CMAS_NO_INDICATION"
"CHECK_CALL_DISPLAY"
"CHECK_CSG"
"CHECK_NITZ_DST"
"CHECK_RESPONSE_DISPLAY"
"CHECK_SS_USER_IND"
“CHECK_SS_USER_IND_FAILURE”
ETSI
(none)
"PLMN"
"CSG"
"PLMN"
"Service"
(none)
<PLMN ID>
<CSG ID>
(none)
(none)
<PLMN ID>
<MBMS Service
ID>
"Interest"
"ON" / "OFF"
"SAI"
<MBMS SAI>
"Service"
<MBMS Service
ID>
"SAI"
<MBMS SAI>
“Active”
"ON" / "OFF"
"Priority Over
"FALSE" /
Unicast"
"TRUE"
“WARNING1”
<WARNING1>
“WARNING2”
<WARNING2>
“WARNING1”
<WARNING1>
“WARNING2”
<WARNING2>
"ToDisplay"
<NAME>/<NUM
BER>
"CSG"
< CSG ID >
"Included"
"FALSE" /
"TRUE"
"DaylightSaving
DST
Time:"
"ToDisplay"
<STRING>
"Supplementary <SUPPLEMEN
Service"
TARY
SERVICE>
"ToDisplay"
<STRING>
(none)
3GPP TS 36.523-3 version 13.2.0 Release 13
89
"CONFIGURE_OPERATIONMODE"
“CONFIGURE_ANDSF_RULE”
“WLAN_ANDSF_CONFIGURED”
“WLAN_ANDSF_NOT_CONFIGURED
”
"CMTLR_DUMMY" (see Note)
ETSI TS 136 523-3 V13.2.0 (2017-03)
"OPERATION
MODE"
“ANDSF Rule”
<OPERATION
MODE>
<ANDSF
RULE>
(none)
(none)
”Notification
<NOTIFICATIO
Type”
N TYPE>
"CCFC_DUMMY" (see Note)
”Status”
<STATUS>
"CNAP_DUMMY" (see Note)
”Testname”
<TESTNAME>
"CTZE_DUMMY" (see Note)
"Year
<YEAR>
"Month"
<MONTH>
"Day"
<DAY>
"Hour"
<HOUR>
"Minutes"
<MINUTES>
"Seconds"
<SECONDS>
“Daylight
<DAYLIGHT
SavingTime”
SAVING TIME>
"TimeZone"
<TIMEZONE>
"CMWN_DUMMY" (see Note)
(none)
“D2D_DISCOVERY_CLEAR”
(none)
“D2D_DISCOVERY_CONFIGURATIO “ProSeApplicati
<charstring>
N”
onID”
"PLMN_List"
<PLMN
ID_List>
T4005
<T4005>
“D2D_DISCOVERY”
“ProSeApplicati
<charstring>
onID”
“Announce”
"ON" / "OFF"
“Monitor”
"ON" / "OFF"
“D2D_COMMUNICATION”
“ProSe Layer-2
<charstring>
Group ID”
“Transmit”
"ON" / "OFF"
“Receive”
"ON" / "OFF"
“Max size of UE
<bytes>
transmitted
Direct
Communication
data”
“D2D_COMMUNICATION_CONFIGU “ProSe Layer-2
<charstring>
RATION”
Group ID”
"PLMN_List"
<PLMN
ID_List>
T4005_Minutes
<T4005>
“Security Life
<SecurityTimer
time timer in
>
minutes”
(Default: 0)
"CONFIGURE_EDRX"
"EDRX"
"ON" / "OFF"
"CONFIGURE_PSM"
"PSM"
"ON" / "OFF"
"TRIGGER_MO_EXCEPTIONDATA”
(none)
Note:
These MMI commands are used to indicate to the SS that a UT
response is expected by the TTCN in the case when the AT
command is not supported. They can be ignored if the UE
supports the AT command. The prefix of these commands
matches the start of the AT response expected by the TTCN
The following AT commands are applied in TTCN.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
90
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 5.2: AT Commands
Command
ATD
ATA
ATH
AT+CGEQOS
AT+CGTFT
AT+CGDSCONT
AT+CGACT
AT+CGCMOD
AT+CGDCONT
AT+CMGD
AT+CSMS
AT+CPMS
AT+CMGF
AT+CSCS
AT+CSCA
AT+CMGW
AT+CMSS
AT+CMMS
AT+CSMP
AT+CGEQREQ
AT+CCLK
AT+COPS
AT+CGATT
AT+CEMODE
AT+CEN
AT+CLIP
AT+CLIR
AT+COLP
AT+CCFC
AT+CHLD
AT+CEPPI
AT+CDU
AT+CHCCS
AT+COLR
AT+CCWA
AT+CNAP
AT+CLCK
AT+CPWD
AT+CTZR
AT+CTZU
AT+CUSD
AT+CMWI
AT+CPSMS
Reference
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.005 [31]
TS 27.005 [31]
TS 27.005 [31]
TS 27.005 [31]
TS 27.007 [32]
TS 27.005 [31]
TS 27.005 [31]
TS 27.005 [31]
TS 27.005 [31]
TS 27.005 [31]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
TS 27.007 [32]
AT commands are referred to TS 27.005 [31], TS 27.007 [32] and TS 27.060 [33].
The setting in TTCN of the AT command elements listed in Table 5-3 may require adaptation to the UE dependent
interpretation of the element. It shall be handled by the system adaptor.
Table 5-3: AT commands elements
Element
<cid>
Reference
TS 27.007 [32]
TTCN Setting
EPS Bearer Identity or PDP Context Identity
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
91
ETSI TS 136 523-3 V13.2.0 (2017-03)
6
ASP specifications
6.1
General Requirements and Assumptions
The following common requirements affect ASP definitions:
-
The definition of ASPs shall have no impact on the common system architecture or on the performance.
-
The codec implementation is out of scope of the present document.
-
For peer-to-peer PDUs contained in an ASP encoding rules need to be considered acc. to the respective protocol:
-
ASN.1 BER and PER.
-
Tabular notation for NAS PDUs or layer 2 data PDUs.
There are no encoding rules being defined for top level ASP definitions and information exchanged between the test
executable and the System Adaptor (SA) only. Instead encoding depends on implementation of the codec and the SA.
There are no encoding rules being defined for ASPs between TTCN-3 components. This is implementation dependent.
Info elements defined in the protocol specifications (e.g. RRC) shall be re-used in configuration ASPs as far as possible.
For optional fields within the configuration ASPs, the following rules will be applied:
-
For ASN.1 fields - these will follow the same rules as defined in the RRC specification [19].
-
For TTCN-3 fields - when the current configuration of an optional field is to be 'kept as it is' then the field will
be set to omit.
-
For TTCN-3 fields - when the current configuration of an optional field is to be released/deleted then a separate
option is provided in a union.
6.1.1
IP ASP requirements
6.1.2
Enhancement of IP ASP for handling IMS signalling
The IMS test model handling registration signalling introduces IPsec and SigComp layers into the IP test model in
Figure 4.2.5.2-1. The ASP on system port IP_SOCK needs to be enhanced to provide additional configuration/control
functions for IPsec and SigComp. The enhanced IP ASP should contain:
1. Function to clean all IPsec and SigComp configurations and to put the IPsec and SigComp in the initial state.
2. Function to return SigComp layer a Compartment Id instructing SigComp layer to save the state of a received
message which was compressed.
3. Function to start or stop signalling compression in sending direction (the SS to the UE) of SigComp.
4. Function to set security parameters (per security association) in IPsec layer.
5. A flag indicating whether SigComp layer shall be included in the data path when establishing a connection.
6. A flag indicating whether the received message was compressed by SigComp.
7. A parameter to point to a compartment used by SigComp to send a message.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
6.2
92
ETSI TS 136 523-3 V13.2.0 (2017-03)
E-UTRAN ASP Definitions
Test case (TTCN-3)
SYSTEM_CTRL_REQ
SYSTEM_CTRL_CNF
SYSTEM_IND
SYSIND port
NAS_CTRL_REQ
SYS port
SRB_COMMON_IND
DRB_COMMON_IND
SRB_COMMON_REQ
NAS_CTRL_CNF
DRB_COMMON_REQ
DRB port
SRB port
NASCTRL port
NAS Emulation
(TTCN-3)
SRB2:
NAS
only
SRB1:
RRC only
RRC+ NAS,
NAS only
NAsCount
NAS
Security
(per UE)
Security
RRC/NAS
codec
SRB0:
RRC
only
RRC_PDU_REQ/RRC_PDU_IND
SRB port
User Plane
RRC
(below RRC)
Control Plane
SRB1
SRB2
SRB0
PDCP
PDCP
Ciphering/ROHC
RRC Security (per RB)
PDCP Conf ig
RLC
AM
RLC Config
DRB
TM
DCCH
DCCH
CCCH
LCID=2
LCID=1
LCID=0
RLC
AM/UM/TM
L1MacIndCtrl
MAC Conf ig
RB-Mapping
SpsConfig
SystemIndication
Logical Channels
MAC
C-RNTI
CcchDcchDtchConf ig
RachProcedureConf ig
CellConfigRequest
BcchConfig
PagingTrigger
PCCH
CTRL
PcchConfig
BCCH
CTRL
RACH
CTRL
StaticCellInf o
PhysicalLayerConf igDL
PhysicalLayerConf igUL
PHY
Ref erencePower
L1_TestMode
PdcchOrder
SystemIndication
PBCH/PCFICH/PHICH/PDCCH/PDSCH
PRACH/PUCCH/PUSCH
EnquireTiming
CellAttenuation
Figure 6.2-1: E-UTRAN ASP Test Model
6.2.1
Configuration Primitives
Annex D contains the ASP definitions for configurations.
6.2.2
Signalling Primitives
Annex D contains the ASP definitions for configurations.
ETSI
CCCH/DCCH/DTCH
CTRL
DTCH
3GPP TS 36.523-3 version 13.2.0 Release 13
6.2.3
93
ETSI TS 136 523-3 V13.2.0 (2017-03)
Co-ordination Messages between NAS Emulation PTC and EUTRA
PTC
TTCN-3 ASP Definition
SRB_COMMON_REQ
Record
TTCN-3 Type
record
cell id
SRB0, SRB1, SRB2
system frame number and sub-frame number or "Now"
CnfFlag: (normally false)
FollowOnFlag:
true: Indicates that the message(s) to be sent on the same TTI will
follow
NOTE 1: If the same TimingInfo is not used in the messages to be
sent on the same TTI, the SS shall produce an error.
false: Indicates that no more message(s) will follow.
Signalling Part
TTCN-3 Type
record
Rrc
TTCN-3 Type
union
omit:
NAS message shall be present; NAS message shall be sent in
DLInformationTransfer
present, NAS message present:
(piggybacked) NAS PDU shall be security protected (if necessary) and
inserted in RRC PDU's NAS_DedicatedInformation
present, NAS message omit:
(RRC message does not contain NAS information)
Ccch
DL_CCCH_Message as define in TS 36.331 [19], clause 6.2.1
Dcch
DL_DCCH_Message as define in TS 36.331 [19], clause 6.2.1
Nas
TTCN-3 Type
record
omit:
RRC message shall be present; RRC message does not contain
(piggybacked) NAS PDU
present, RRC message omit:
NAS message shall be sent embedded in DLInformationTransfer
present, RRC message present:
NAS message is piggybacked in RRC message
NOTE 2: In case of RRC message being sent on CCCH or does not
have IE NAS_DedicatedInformation NAS message shall be
omitted.
SecurityProtectionInfo
security status (if protected with integrity and/or ciphering, if at all)
NAS message
union of all NAS messages define for DL except SECURITY
PROTECTED NAS MESSAGE
Type Name
TTCN-3 Type
Common Part
CellId
RoutingInfo
TimingInfo
ControlInfo
Type Name
TTCN-3 Type
Common Part
CellId
RoutingInfo
TimingInfo
Signalling Part
Rrc
Ccch
Dcch
TTCN-3 ASP Definition
SRB_COMMON_IND
Record
TTCN-3 Type
record
cell id
SRB0, SRB1, SRB2
system frame number; sub-frame number when PDU has been received
TTCN-3 Type
record
TTCN-3 Type
union
omit:
NAS message shall be present; NAS message is received in
ULInformationTransfer
present, NAS message present:
NAS_DedicatedInformation contains unstructured and security
protected NAS PDU and the NAS message contains the deciphered
message in structured format
present, NAS message omit:
(RRC message does not contain NAS information)
UL_CCCH_Message as define in TS 36.331 [19], clause 6.2.1
UL_DCCH_Message as define in TS 36.331 [19], clause 6.2.1
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Nas
SecurityProtectionInfo
NAS message
94
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 ASP Definition
TTCN-3 Type
record
omit
RRC message shall be present; RRC message does not contain
(piggybacked) NAS PDU
present, RRC message omit
NAS message has been received in ULInformationTransfer
present, RRC message present
NAS message is piggybacked in RRC message
security status (if protected with integrity and/or ciphering, if at all),
nas count
union of all NAS messages define for UL except SECURITY
PROTECTED NAS MESSAGE
TTCN-3 ASP Definition
NAS_CTRL_REQ
Record
TTCN-3 Type
record
cell id
(not used for configuration)
current system frame number; sub-frame number
(always provided by the SS)
Result
Success or error
(in case of error an SS specific error code shall be provided; this will not
be evaluated by TTCN but may be useful for validation)
Primitive specific Part
TTCN-3 Type
union
Security
Start/Restart
Integrity
Ciphering
NasCountReset
Release
NAS Count
get
set
Type Name
TTCN-3 Type
Common Part
CellId
RoutingInfo
TimingInfo
TTCN-3 ASP Definition
NAS_CTRL_CNF
Record
TTCN-3 Type
record
cell id
(not used for configuration)
current system frame number; sub-frame number
(always provided by the SS)
Result
Success or error
(in case of error an SS specific error code shall be provided; this will not be
evaluated by TTCN but may be useful for validation)
Primitive specific Part
TTCN-3 Type
union
Security
(contains no further information)
NAS Count
get
set
Type Name
TTCN-3 Type
Common Part
CellId
RoutingInfo
TimingInfo
6.3
UTRAN ASP Definitions
The UTRAN ASP definitions are specified according to 3GPP TS 34.123 [7], clause 6A.3.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
95
ETSI TS 136 523-3 V13.2.0 (2017-03)
6.3.1
Void
6.3.2
ASPs for Data Transmission and Reception
TTCN-3 ASP Definition
Type Name
U_RLC_AM_REQ
TTCN-3 Type
union
Port
UTRAN_AM
RLC_AM_DATA_REQ
RLC_AM_TestDataReq
TS 34.123-3, clause 7.3.2.2.34
TS 34.123-3, clause 7.3.3.1
TTCN-3 ASP Definition
Type Name
U_RLC_AM_IND
TTCN-3 Type
union
Port
UTRAN_AM
RLC_AM_DATA_CNF
RLC_AM_DATA_IND
RLC_AM_TestDataInd
TTCN-3 ASP Definition
UTRAN_RLC_AM_REQ
UTRAN_RLC_AM_IND
UTRAN_RLC_TR_REQ
UTRAN_RLC_TR_IND
UTRAN_RLC_UM_REQ
UTRAN_RLC_UM_IND
RRC_DataReq
RRC_DataReqInd
TS 34.123-3, clause 7.3.2.2.34
TS 34.123-3, clause 7.3.2.2.34
TS 34.123-3, clause 7.3.3.1
Port
UTRAN_AM
UTRAN_AM
UTRAN_TM
UTRAN_TM
UTRAN_UM
UTRAN_UM
UTRAN_Dc
UTRAN_Dc
The Invalid_DL_DCCH_Message type is replaced with:
Type Name
TTCN-3 Type
Invalid_DL_DCCH_Message
NULL
ETSI
Defined in
TS 34.123-3, clause 7.3.2.2.34
TS 34.123-3, clause 7.3.2.2.34
TS 34.123-3, clause 7.3.2.2.33
TS 34.123-3, clause 7.3.2.2.33
TS 34.123-3, clause 7.3.2.2.35
TS 34.123-3, clause 7.3.2.2.35
TS 34.123-3, clause 7.1.2
TS 34.123-3, clause 7.1.2
3GPP TS 36.523-3 version 13.2.0 Release 13
96
6.4
GERAN ASP Definitions
6.4.1
ASPs for Control Primitive Transmission
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 ASP Definition
Type Name
G_CPHY_CONFIG_REQ
TTCN-3 Type
Union
Port
GERAN_CL1
G_CL1_CreateCell_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_DeleteCell_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_CreateBasicPhyCh_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_CreateMultiSlotConfig_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_DeleteChannel_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_ChangePowerLevel_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_CipheringControl_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_CipherModeModify_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_ChModeModify_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL1_ComingFN_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL2_HoldPhyInfo_REQ
TS 34.123-3, clause 7.3.4.3.2.2
G_CL1_L1Header_REQ
TS 34.123-3, clause 7.3.4.3.2.1
G_CL2_MeasRptControl_REQ
TS 34.123-3, clause 7.3.4.3.2.2
G_CL2_NoUAforSABM_REQ
TS 34.123-3, clause 7.3.4.3.2.2
G_CL2_ResumeUAforSABM_REQ
TS 34.123-3, clause 7.3.4.3.2.2
G_CL2_Release_REQ
TS 34.123-3, clause 7.3.4.3.2.2
G_CL1_SetNewKey_REQ
TS 34.123-3, clause 7.3.4.3.2.1
TTCN-3 ASP Definition
Type Name
TTCN-3 Type
Port
ComingFN
L1Header
None
G_CPHY_CONFIG_CNF
Union
GERAN_CL1
RFN
L1Header
This choice used when neither of the other choices are
selected
TTCN-3 ASP Definition
Type Name
G_CRLC_CONFIG_REQ
TTCN-3 Type
Union
Port
GERAN_CRLC
G_CRLC_CreateRLC_MAC_REQ
TS 34.123-3, clause 7.3.4.3.2.3
G_CRLC_DeleteRLC_MAC_REQ
TS 34.123-3, clause 7.3.4.3.2.3
G_CRLC_DL_TBF_Config_REQ
TS 34.123-3, clause 7.3.4.3.2.3
G_CRLC_UL_TBF_Config_REQ
TS 34.123-3, clause 7.3.4.3.2.3
TTCN-3 ASP Definition
Type Name
TTCN-3 Type
Port
G_CRLC_CONFIG CNF
empty record
GERAN_CRLC
TTCN-3 ASP Definition
Type Name
G_LLC_CONFIG_REQ
TTCN-3 Type
Union
Port
GERAN_CLLC
G_CLLC_Assign_REQ
TS 34.123-3, clause 7.3.4.3.2.4
G_CLLC_ReassignLLE_REQ
See below
G_CLLC_CreateLLE_REQ
TS 34.123-3, clause 7.3.4.3.2.4
G_CLLC_DeleteLLE_REQ
TS 34.123-3, clause 7.3.4.3.2.4
G_CLLC_XID_Config_REQ
See below
G_CLLC_DoNotCheckSequenceNumber_REQ
See below
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
97
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 ASP Definition
Type Name
TTCN-3 Type
Port
G_CLLC_CONFIG_CNF
empty record
GERAN_CLLC
ASP Name
G_CSNDCP_Activate_REQ
PCO Type
G_CSAP
Comments
The ASP is used to activate the SNDCP entity
Parameter Name
Parameter Type
Comments
sNDCPId
SNDCPId
The SNDCP entity identifier of the cell
lLMEId
LLMEId
Logical link management entity Id
nSAPI
integer
The Network Service Access Point Identifier
sAPI
SAPI
LLC SAPI
0 - RFC 1144 [54] compress;
PCI_Compression
INTEGER
1 - RFC 2507 [55] compression;
32 - no compression
0 - ITU-T Recommendation V.42bis [56] compression;
dataCompression
INTEGER
1 - ITU-T Recommendation V.44 [57] compression;
32 - no compression
0 - Asynchronous
nPDUNumberSync
INTEGER
1 - Synchronous
Detailed Comments
ASP Name
G_CSNDCP_Activate_CNF
PCO Type
G_CSAP
Comments
The ASP is used to get the confirmation of a G_CSNDCP_Activate_REQ
Parameter Name
Parameter Type
Comments
sNDCPId
SNDCPId
SNDCPentity identifier
nSAPI
NSAPI
The Network Service Access Point Identifier
Detailed Comments
ASP Name
PCO Type
G_CSNDCP_Release_REQ
G_CSAP
This ASP is used to inform that the NSAPI is in use and the acknowledge mode peer to peer LLC
Comments
operation for the requested SAPI is established.
Parameter Name
Parameter Type
Comments
sNDCPId
SNDCPId
The SNDCP entity identifier
nSAPI
integer
The Network Service Access Point Identifier
Detailed Comments
Type Name
TTCN-3 Type
Port
TTCN-3 ASP Definition
G_SNDCP_CONFIG_CNF
Record
GERAN_CSNDCP
TTCN-3 ASP Definition
Type Name
G_SNDCP_CONFIG_REQ
TTCN-3 Type
Union
Port
GERAN_CSNDCP
G_CSNDCP_Activate_REQ
G_CSNDCP_Release_REQ
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
98
ETSI TS 136 523-3 V13.2.0 (2017-03)
ASP Name
PCO Type
G_CLLC_ReassignLLE_REQ
G_CSAP
The ASP is used to reassign RLC/MAC entity to the specified LLME identity.
Comments
This ASP allows simulation of Intra-SGSN operations in tests.
Parameter Name
Parameter Type
Comments
lLMEId
LLMEId
Logical Layer Management Entity Id
This parameter indicates the RLC/MAC emulation module in the cell,
rLC_MAC_MappingInfo
integer
not the cell itself
tLLI
TLLI
ASP Name G_CLLC_XID_Config_REQ
PCO Type G_CSAP
Comments The ASP is used to inform the SS of the XID information responded to the UE by TTCN
Parameter Name
Parameter Type
Comments
lLMEId
LLMEId
tLLI
TLLI
sAPI
SAPI
xID_Info
XID_Info
the XID parameters responded to the UE/MS
Detailed Comments
ASP Name
PCO Type
G_CLLC_DoNotCheckSequenceNumber_REQ
G_CSAP
The ASP commands the SS to not check the N(U) sequence number of the next LLC message to be
Comments
received on the connection specified by the ASP parameters. The SS should however use this value
to update its value of N(U).
Parameter Name
Parameter Type
Comments
lLMEId
LLMEId
The identifier of the cell Logical Layer Management Entity Id
tLLI
TLLI
sAPI
SAPI
Detailed Comments
6.4.2
ASPs for Data Transmission and Reception
TTCN-3 ASP Definition
Type Name
G__L2_DATAMESSAGE_REQ
TTCN-3 Type
Union
Port
GERAN_L2
G_L2_UNITDATA_REQ
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_Release_REQ
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_SYSINFO_REQ
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_Paging_REQ
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_PagingGPRS_REQ
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_DATA_REQ
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_GTTP_REQ
TS 34.123-3, clause 7.3.4.3.1.1
The SysInfoType is replaced with:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Type Name
TTCN-3 Type
99
ETSI TS 136 523-3 V13.2.0 (2017-03)
SysInfoMsg
Union
SYSTEMINFORMATIONTYPE1
SYSTEMINFORMATIONTYPE2
SYSTEMINFORMATIONTYPE3
SYSTEMINFORMATIONTYPE4
SYSTEMINFORMATIONTYPE5
SYSTEMINFORMATIONTYPE6
SYSTEMINFORMATIONTYPE13
SYSTEMINFORMATIONTYPE15
SYSTEMINFORMATIONTYPE2bis
SYSTEMINFORMATIONTYPE2ter
SYSTEMINFORMATIONTYPE2quater
SYSTEMINFORMATIONTYPE5bis
TTCN-3 ASP Definition
Type Name
G__L2_DATAMESSAGE_IND
TTCN-3 Type
Union
Port
GERAN_L2
G_L2_UNITDATA_IND
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_Release_CNF
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_Release_IND
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_Estab_IND
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_GTTP_IND
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_DATA_IND
TS 34.123-3, clause 7.3.4.3.1.1
G_L2_ACCESS_IND
TS 34.123-3, clause 7.3.4.3.1.1
TTCN-3 ASP Definition
Type Name
G__RLC_DATAMESSAGE_REQ
TTCN-3 Type
Union
Port
GERAN_RLC
G__RLC_ControlMsg_REQ
TS 34.123-3, clause 7.3.4.3.1.2
TTCN-3 ASP Definition
Type Name
G__RLC_DATAMESSAGE_IND
TTCN-3 Type
Union
Port
GERAN_RLC
G__RLC_ControlMsg_IND
TS 34.123-3, clause 7.3.4.3.1.2
TTCN-3 ASP Definition
Type Name
G__LLC_DATAMESSAGE_REQ
TTCN-3 Type
Union
Port
GERAN_LLC
G_LLC_UNITDATA_REQ
TS 34.123-3, clause 7.3.4.3.1.3
G_LLC_XID_RES
TS 34.123-3, clause 7.3.4.3.1.3
ASP Name G_LLC_NULL_IND
PCO Type G_DSAP
Comments The ASP is used to receive the LLC NULL frame, sent by the UE for Cell Update.
Parameter Name
Parameter Type
Comments
lLMEId
LLMEId
tLLI
TLLI
sAPI
SAPI
Detailed Comments
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
100
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 ASP Definition
Type Name
G__LLC_DATAMESSAGE_IND
TTCN-3 Type
Union
Port
GERAN_LLC
G_LLC_UNITDATA_IND
TS 34.123-3, clause 7.3.4.3.1.3
G_LLC_XID_IND
TS 34.123-3, clause 7.3.4.3.1.3
G_LLC_NULL_IND
ASP Name
PCO Type
G_SN_UNIDATA_REQ
G_DSAP
The ASP is used to send a valid IP datagram on the specified NSAPI to the UE/MS by
Comments
unacknowledged transmission.
Parameter Name
Parameter Type
Comments
sNDCPId
SNDCPId
nSAPI
integer
5 to 15
n_PDU
N_PDU
Valid IPv4 or IPv6 datagram
Detailed Comments
Unacknowledged transmission mode
ASP Name
PCO Type
G_SN_UNITDATA_IND
G_DSAP
The ASP is used to receive an IP datagram on the specified NASPI from the UE/MS in unacknowledged
Comments
transmission mode.
Parameter Name
Parameter Type
Comments
sNDCPId
SNDCPId
nSAPI
integer
5 to 15
n_PDU
N_PDU
IPv4 or IPv6 datagram
Detailed Comments
Unacknowledged transmission mode
Type Name
Type Definition
Type Encoding
Comments
SNDCPId
INTEGER
The identifier of the SNDCP entity in SGSN
TTCN-3 ASP Definition
Type Name
G__SN_DATAMESSAGE_REQ
TTCN-3 Type
Union
Port
GERAN_SNDCP
G_SN_UNITDATA_REQ
TTCN-3 ASP Definition
Type Name
G__SN_DATAMESSAGE_IND
TTCN-3 Type
Union
Port
GERAN_SNDCP
G_SN_UNITDATA_IND
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
6.5
101
ETSI TS 136 523-3 V13.2.0 (2017-03)
NB-IoT ASP Definitions
Test case (TTCN-3)
NB_SYSTEM_CTRL_REQ
NB_SYSTEM_CTRL_CNF
NB_SYSTEM_IND
NB_SYSIND port
NAS_CTRL_REQ
NB_L2_SDU_MSG
NB_SYSTEM port
NB_SRB_COMMON_IND
NAS_CTRL_CNF
NASCTRL port
NB_L2_SRB port
NAS Emulation
(TTCN-3, see figure 4A.2.1-1)
NB_DRB_COMMON_REQ
DRB port
NB_SRB port
NAS
Security
(per UE)
RRC codec
NB_DRB_COMM ON_IND
NB_SRB_COMMON_REQ
NAS
codec
Test mode/ normal mode routing
SRB port
User Plane
RRC
(below RRC)
Control Plane
SRB1
SRB1bis
SRB0
PDCP
PDCP
Ciphering/ROHC
RRC Security (per RB)
PDCP Config
RlcIndCtrl
DRB
RLC
RLC
TM
AM
RLC Conf ig
DCCH
DCCH
AM/TM
CCCH
L1MacIndCtrl
MAC Conf ig
RB-Mapping
SystemIndication
Logical Channels
LCID=1
LCID=3
LCID=0
MAC
C-RNTI
CcchDcchDtchConf ig
RachProcedureConf ig
CellConfigRequest
BcchConf ig
PagingTrigger
PCCH
CTRL
PcchConf ig
Non Anchor Conf ig
RACH
CTRL
StaticCellInf o
PhysicalLayerConf igDL
PHY
PhysicalLayerConf igUL
DL Bitmap Conf ig
InitialCellPower
L1_TestMode
NPBCH/NPDCCH/NPDSCH
NPRACH/NPUSCH
NPDCCH Order
SystemIndication
BCCH
CTRL
EnquireTiming
CellAttenuation
Figure 6.5-1: NB-IoT ASP Test Model
6.5.1
Configuration Primitives
Annex F contains the ASP definitions for configurations.
6.5.2
Signalling Primitives
Annex F contains the ASP definitions for configurations.
ETSI
CCCH/DCCH/DTCH
CTRL
DTCH
3GPP TS 36.523-3 version 13.2.0 Release 13
6.5.3
102
ETSI TS 136 523-3 V13.2.0 (2017-03)
Co-ordination Messages between NAS Emulation PTC and NBIOT
PTC
TTCN-3 ASP Definition
NB_SRB_COMMON_REQ
Record
TTCN-3 Type
record
cell id
SRB0, SRB1, SRB1bis
H-SFN, system frame number and sub-frame number or "Now"
CnfFlag: (normally false)
FollowOnFlag:
true: Indicates that the message(s) to be sent on the same TTI will
follow
NOTE 1: If the same TimingInfo is not used in the messages to be
sent on the same TTI, the SS shall produce an error.
false: Indicates that no more message(s) will follow.
Signalling Part
TTCN-3 Type
record
Rrc
TTCN-3 Type
union
omit:
NAS message shall be present; NAS message shall be sent in
DLInformationTransfer_NB
present, NAS message present:
(piggybacked) NAS PDU shall be security protected (if necessary) and
inserted in RRC PDU's NAS_DedicatedInformation
present, NAS message omit:
(RRC message does not contain NAS information)
Ccch
DL_CCCH_Message_NB as define in TS 36.331 [19], clause 6.7.1
Dcch
DL_DCCH_Message_NB as define in TS 36.331 [19], clause 6.7.1
Nas
TTCN-3 Type
record
omit:
RRC message shall be present; RRC message does not contain
(piggybacked) NAS PDU
present, RRC message omit:
NAS message shall be sent embedded in DLInformationTransfer_NB
present, RRC message present:
NAS message is piggybacked in RRC message
NOTE 2: In case of RRC message being sent on CCCH or does not
have IE NAS_DedicatedInformation NAS message shall be
omitted.
SecurityProtectionInfo
security status (if protected with integrity and/or ciphering, if at all)
NAS message
union of all NAS messages define for DL except SECURITY
PROTECTED NAS MESSAGE
Type Name
TTCN-3 Type
Common Part
CellId
RoutingInfo
TimingInfo
ControlInfo
Type Name
TTCN-3 Type
Common Part
CellId
RoutingInfo
TimingInfo
Signalling Part
Rrc
Ccch
Dcch
TTCN-3 ASP Definition
NB_SRB_COMMON_IND
Record
TTCN-3 Type
record
cell id
SRB0, SRB1, SRB1bis
H-SFN, system frame number; sub-frame number when PDU has been
received
TTCN-3 Type
record
TTCN-3 Type
union
omit:
NAS message shall be present; NAS message is received in
ULInformationTransfer_NB
present, NAS message present:
NAS_DedicatedInformation contains unstructured and security
protected NAS PDU and the NAS message contains the deciphered
message in structured format
present, NAS message omit:
(RRC message does not contain NAS information)
UL_CCCH_Message_NB as define in TS 36.331 [19], clause 6.7.1
UL_DCCH_Message_NB as define in TS 36.331 [19], clause 6.7.1
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Nas
SecurityProtectionInfo
NAS message
103
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 ASP Definition
TTCN-3 Type
record
omit
RRC message shall be present; RRC message does not contain
(piggybacked) NAS PDU
present, RRC message omit
NAS message has been received in ULInformationTransfer_NB
present, RRC message present
NAS message is piggybacked in RRC message
security status (if protected with integrity and/or ciphering, if at all),
nas count
union of all NAS messages define for UL except SECURITY
PROTECTED NAS MESSAGE
For other ASPs, please refer to 6.2.3
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
104
7
E-UTRAN/SAE Test Methods and Design
Considerations
7.1
Channel Mapping
Figure 7.1 shows the channel type mapping that is used for the configuration of the SS. In layer 2 test cases non default
channel mapping can be applied on SS, as explained in clause 4.2.1.
TM
RACH
PRACH
UM
RLC
AM
PCCH
BCCH
CCCH
DCCH
PCH
BCH
DL-SCH
UL-SCH
PBCH
PDSCH
PUSCH
Logical
chs
DTCH
Transport
chs
PCFICH
PHICH
PDCCH
PUCCH
Physical
chs
Figure 7.1-1: Channel type mapping for the default configuration of the SS
7.1.1
PDCCH Candidate Selection
In this clause following abbreviations are used:
-
Common search Space Aggregation: CS_Agr.
-
UE-Specific Search Space Aggregation: UE_Agr.
-
Total number of CCEs available in a subframe: Max_CCE.
SS shall apply defined rules below in a DL subframe for PDCCH candidates selection.
-
Scheduled transmissions on SI-RNTI, P-RNTI, RA-RNTI, M-RNTI, G-RNTI, SC-RNTI, SC-N-RNTI and
eIMTA-RNTI, use Common Search Space. UL and DL Scheduled transmissions on C-RNTI / SPS C-RNTI, DL
Scheduled transmissions on Temp. C-RNTI and UL Scheduled transmission on SL-RNTI, use UE-Specific
Search Space. Transmissions on TPC-PUCCH-RNTI / TPC-PUSCH-RNTI and UL Scheduled transmissions on
Temp. C-RNTI is not considered for default CCE management.
-
If a transmission on SI-RNTI is scheduled, PDCCH candidate corresponding to CCEs between 0 and (CS_Agr1) is used. For FDD, this PDCCH candidate is reserved for SI-RNTI, and left vacant if no SI-RNTI transmission
is scheduled. For TDD the default UL/DL configuration type 1, this PDCCH candidate is reserved for SI-RNTI
in subframes 0 & 5 (i.e. subframes where PDCCH for UL grant for C-RNTI / SPS C-RNTI is not scheduled).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
105
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCCH candidates corresponding to CCEs between CS_Agr and (2*CS_Agr-1) can be used for the transmission
on P-RNTI, RA-RNTI, M-RNTI, G-RNTI, SC-RNTI, SC-N-RNTI or eIMTA-RNTI. In conformance test cases
with single UE, there is no requirement for transmissions scheduled for more than one of P-RNTI, RA-RNTI, MRNTI, G-RNTI, SC-RNTI, SC-N-RNTI or eIMTA-RNTI in one DL subframe. As per TS 36.331 [19] clause
5.8.1.3, the MCCH change notification indicator shall be transmitted on MBSFN subframes only.
For FDD:
-
For DL transmission for C-RNTI / SPS C-RNTI / Temp C-RNTI the lowest value of m =m' which has a PDCCH
available from CCEs between 2*CS_Agr and (Max_CCE-1) shall be used. 'm' is defined in TS 36.213 [30],
clause 9.1.1.
-
For UL transmission for C-RNTI / SPS C-RNTI /SL-RNTI the lowest value of m =m">m' which has a PDCCH
available from CCEs between 2*CS_Agr and (Max_CCE-1) shall be used, irrespective of PDCCH candidate
corresponding to m' is used or not. In conformance test cases with single UE, there is no requirement for
transmissions scheduled for more than one of C-RNTI / SPS C-RNTI or SL-RNTI in one DL subframe.
For TDD:
-
For DL transmission, for C-RNTI / SPS C-RNTI / Temp C-RNTI the lowest value of m =m' which has a
PDCCH available from CCEs between 1*CS_Agr and (Max_CCE-1) shall be used. 'm' is defined in TS 36.213
[30] clause 9.1.1. In conformance test cases with single UE, there is no requirement for transmissions scheduled
for more than one of C-RNTI / SPS C-RNTI / Temp C-RNTI, P-RNTI, RA-RNTI or eIMTA-RNTI in one DL
sub frame.
-
For UL transmission, for C-RNTI / SPS C-RNTI / SL-RNTI the lowest value of m =m"and if in the sub frame m'
is also used, m"!=m' has a PDCCH available from CCEs between 0 and (Max_CCE-1) shall be used. In
conformance test cases with single UE, there is no requirement for transmissions scheduled for more than one of
C-RNTI / SPS C-RNTI, SL-RNTI or eIMTA-RNTI in one DL subframe.
NOTE:
7.1.1.1
If m' or m'' cannot be allocated in any TTI, it is a TTCN error due to X-RNTI not properly allocated. The
error shall be reported to TTCN. The TTCN will exit the test case assigning an inconclusive verdict.
FDD candidates selection
Table 7.1.1.1-1 gives the CCE resources utilized for m' and m'' for default values of common search space aggregation
level =4, UE-specific search space aggregation L=2 resulting in 6 PDCCH candidates m=0..5 and channel Bandwidth of
5 MHz. This give Max_CCE =20 for FDD. The table also gives the corresponding CCE start indices of PDCCH
candidates for m' and m''.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
106
Table 7.1.1.1-1: CCE Start indices(m' & m'') to be used for various C-RNTIs (5 MHz)
C-RNTI
tsc_C_RNTI_Def
Value
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
tsc_C_RNTI_Def3
'1111'H
4369
tsc_C_RNTI_Def4
'1FF1'H
8177
tsc_C_RNTI_Def5
'04D2'H
1234
tsc_C_RNTI_Def6
'0929'H
2345
tsc_C_RNTI_Def7
'0D80'H
3456
tsc_C_RNTI_Def8
'11D7'H
4567
tsc_C_RNTI_Def9
'162E'H
5678
tsc_C_RNTI_Def10
'1A85'H
6789
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
0
12
1
14
0
12
1
14
0
16
1
18
0
12
1
14
0
10
1
12
4
8
5
10
2
8
3
10
0
8
1
10
0
12
1
14
0
16
1
18
SF1
1
8
2
10
0
16
1
18
0
10
1
12
0
12
1
14
2
8
3
10
0
10
1
12
0
16
1
18
0
16
1
18
3
8
4
10
0
8
1
10
SF2
0
14
1
16
2
8
3
10
0
14
1
16
0
18
5
8
0
10
1
12
4
8
5
10
2
8
3
10
0
8
1
10
0
12
1
14
0
16
1
18
SF3
0
8
1
10
0
14
1
16
2
8
3
10
0
16
1
18
4
8
5
10
0
12
1
14
0
18
5
8
2
8
3
10
0
16
1
18
3
8
4
10
SF4
0
12
1
14
0
10
1
12
3
8
4
10
3
8
4
10
0
14
1
16
0
14
1
16
0
14
1
16
0
14
1
16
0
8
1
10
0
8
1
10
SF5
3
8
4
10
4
8
5
10
0
10
1
12
0
18
5
8
2
8
3
10
1
8
2
10
0
14
1
16
0
16
1
18
2
8
3
10
1
8
2
10
SF6
4
8
5
10
4
8
5
10
0
14
1
16
0
18
5
8
3
8
4
10
3
8
4
10
3
8
4
10
3
8
4
10
0
16
1
18
0
16
1
18
SF7
0
8
1
10
1
8
2
10
0
8
1
10
0
18
5
8
0
14
1
16
3
8
4
10
0
16
1
18
2
8
3
10
0
18
5
8
1
8
2
10
SF8
0
14
1
16
0
18
5
8
0
18
5
8
2
8
3
10
1
8
2
10
4
8
5
10
0
14
1
16
0
8
1
10
3
8
4
10
3
8
4
10
SF9
0
10
1
12
0
16
1
18
4
8
5
10
4
8
5
10
0
10
1
12
2
8
3
10
2
8
3
10
2
8
3
10
2
8
3
10
2
8
3
10
Table 7.1.1.1-1a gives the CCE resources utilized for m' and m'' for default values of common search space aggregation
level =4, UE-specific search space aggregation L=2 resulting in 6 PDCCH candidates m=0..5 and channel Bandwidth of
5 MHz and CFI=2, suitable for eMBMS test cases. This give Max_CCE =12 for FDD. The table also gives the
corresponding CCE start indices of PDCCH candidates for m' and m''.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
107
Table 7.1.1.1-1a: CCE Start indices(m' & m'') to be used for various C-RNTIs with CFI=2 (5 MHz)
C-RNTI
tsc_C_RNTI_Def
Value
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
tsc_C_RNTI_Def3
'1111'H
4369
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
4
8
5
10
0
8
1
10
2
8
3
10
SF1
3
8
4
10
4
8
5
10
0
10
5
8
SF2
3
8
4
10
0
8
1
10
0
10
5
8
SF3
0
8
1
10
0
10
5
8
4
8
5
10
SF4
2
8
3
10
3
8
4
10
0
10
5
8
SF5
1
8
2
10
4
8
5
10
0
10
5
8
SF6
2
8
3
10
0
8
1
10
0
10
5
8
SF7
0
8
1
10
0
10
5
8
2
8
3
10
SF8
3
8
4
10
1
8
2
10
0
10
5
8
SF9
1
8
2
10
0
8
1
10
2
8
3
10
Tables 7.1.1.1-2, 7.1.1.1-3 and 7.1.1.1-4 give the CCE resources utilized for m' and m'' for default values of common
search space aggregation level =4, UE-specific search space aggregation L=2 resulting in 6 PDCCH candidates m=0..5
and bandwidths of 10/15/20 MHz respectively. This gives Max_CCE =25(10 MHz)/37(15 MHz)/50(20 MHz) for FDD.
The tables also give the corresponding CCE start indices of PDCCH candidates for m' and m''. These are in general to
be applied in MAC Transport block size test cases defined in clause 7.1.7 of TS 36.523-1 [1].
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
108
Table 7.1.1.1-2: CCE Start indices (m' & m'') to be used for default C-RNTI (10 MHz)
C-RNTI
tsc_C_RNTI_Def
Value
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
tsc_C_RNTI_Def3
'1111'H
4369
tsc_C_RNTI_Def4
'1FF1'H
8177
tsc_C_RNTI_Def5
'04D2'H
1234
tsc_C_RNTI_Def6
'0929'H
2345
tsc_C_RNTI_Def7
'0D80'H
3456
tsc_C_RNTI_Def8
'11D7'H
4567
tsc_C_RNTI_Def9
'162E'H
5678
tsc_C_RNTI_Def10
'1A85'H
6789
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
0
12
1
14
0
8
1
10
0
16
1
18
2
8
3
10
3
8
4
10
0
20
1
22
4
8
5
10
2
8
3
10
0
8
1
10
0
12
1
14
SF1
3
8
4
10
4
8
5
10
0
10
1
12
0
20
1
22
0
16
1
18
0
18
1
20
0
20
1
22
0
8
1
10
0
10
1
12
0
12
1
14
SF2
3
8
4
10
0
20
1
22
0
10
1
12
0
14
1
16
0
22
5
8
2
8
3
10
0
20
1
22
0
12
1
14
2
8
3
10
0
20
1
22
SF3
0
20
1
22
0
10
1
12
4
8
5
10
4
8
5
10
0
12
1
14
2
8
3
10
1
8
2
10
0
8
1
10
4
8
5
10
3
8
4
10
SF4
0
16
1
18
0
14
1
16
0
22
5
8
0
10
1
12
0
22
5
8
0
18
1
20
0
14
1
16
0
10
1
12
0
16
1
18
0
12
1
14
SF5
0
18
1
20
4
8
5
10
0
22
5
8
0
18
1
20
2
8
3
10
1
8
2
10
0
22
5
8
4
8
5
10
0
16
1
18
0
18
1
20
SF6
0
16
1
18
0
20
1
22
0
22
5
8
3
8
4
10
3
8
4
10
0
18
1
20
0
10
1
12
3
8
4
10
2
8
3
10
0
20
1
22
SF7
0
8
1
10
0
22
5
8
2
8
3
10
0
22
5
8
3
8
4
10
0
22
5
8
0
8
1
10
2
8
3
10
0
14
1
16
0
10
1
12
SF8
0
14
1
16
0
18
1
20
0
10
1
12
2
8
3
10
1
8
2
10
0
12
1
14
0
18
1
20
4
8
5
10
1
8
2
10
3
8
4
10
SF9
0
18
1
20
0
8
1
10
0
16
1
18
0
12
1
14
0
22
5
8
2
8
3
10
4
8
5
10
0
20
1
22
0
16
1
18
0
12
1
14
Table 7.1.1.1-3: CCE Start indices (m' & m'') to be used for default C-RNTI (15 MHz)
C-RNTI
tsc_C_RNTI_Def
Value
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
tsc_C_RNTI_Def3
'1111'H
4369
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
4
8
5
10
0
32
1
34
0
16
1
18
SF1
0
14
1
16
0
12
1
14
0
22
1
24
ETSI
SF2
0
14
1
16
0
20
1
22
0
22
1
24
SF3
0
20
1
22
0
34
5
8
4
8
5
10
SF4
0
16
1
18
0
14
1
16
0
10
1
12
SF5
0
18
1
20
4
8
5
10
0
22
1
24
SF6
0
28
1
30
0
8
1
10
0
34
5
8
SF7
0
20
1
22
0
10
1
12
0
28
1
30
SF8
0
26
1
28
0
30
1
32
0
34
5
8
SF9
0
30
1
32
0
32
1
34
0
28
1
30
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
109
Table 7.1.1.1-4: CCE Start indices (m' & m'') to be used for default C-RNTI (20 MHz)
C-RNTI
tsc_C_RNTI_Def
Value
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
tsc_C_RNTI_Def3
'1111'H
4369
7.1.1.2
SF0
3
8
4
10
0
12
1
14
1
8
2
10
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF1
0
36
1
38
0
46
1
48
0
20
1
22
SF2
0
34
1
36
2
8
3
10
0
24
1
26
SF3
0
38
1
40
0
34
1
36
0
34
1
36
SF4
0
42
1
44
0
20
1
22
3
8
4
10
SF5
0
22
1
24
0
10
1
12
0
10
1
12
SF6
0
10
1
12
0
10
1
12
2
8
3
10
SF7
0
8
1
10
0
26
1
28
0
38
1
40
SF8
2
8
3
10
0
28
1
30
0
48
5
8
SF9
0
20
1
22
1
8
2
10
0
20
1
22
TDD candidates selection
The default TDD subframe configuration 1 is applied to this clause. By default no DL data is scheduled in special
subframes 1 and 6.
Considering that each TDD subframe having different PHICH group number, and only two symbols being present for
PDCCH in the special subframes 1 and 6 for bandwidth of 5 MHz, two symbols for PDCCH in all subframes for
bandwidth of 10/15/20 MHz (TS 36.508 [3]), each subframe has, therefore, different number of MAX_CCE.
Table 7.1.1.2-1 gives the PDCCH candidates of m' and m'' for default values of common search space aggregation level
=8, UE-specific search space aggregation L=8 resulting in 2 PDCCH candidates m=0,1 and the corresponding CCE
start indices for channel bandwidth of 5MHz. SF0 and SF5 cannot be used for UL grant. SF1 and SF6 are not used for
DL assignment. SF2, SF3, SF7 and SF8 are not applicable to PDCCH CCE allocation since they are uplink subframes.
Table 7.1.1.2-1: CCE Start indices (m' & m'') to be used for various C-RNTIs (5 MHz)
C-RNTI
Value
tsc_C_RNTI_Def
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
tsc_C_RNTI_Def3
'1111'H
4369
tsc_C_RNTI_Def4
'1FF1'H
8177
tsc_C_RNTI_Def5
'04D2'H
1234
tsc_C_RNTI_Def6
'0929'H
2345
tsc_C_RNTI_Def7
'0D80'H
3456
tsc_C_RNTI_Def8
'11D7'H
4567
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
SF0
21
1
8
1
8
1
8
1
8
0
8
1
8
1
8
1
8
SF1
12
0
0
0
0
0
0
0
0
0
0
0
0
0
0
-
ETSI
SF2
-
SF3
-
SF4
20
1
8
0
0
0
8
1
0
0
8
1
0
0
8
1
0
0
8
1
0
0
8
1
0
0
8
1
0
0
8
SF5
21
0
8
1
8
0
8
0
8
1
8
0
8
0
8
0
8
SF6
12
0
0
0
0
0
0
0
0
0
0
0
10
0
0
-
SF7
-
SF8
-
SF9
20
0
8
1
0
1
8
0
0
1
8
0
0
1
8
0
0
0
8
1
0
1
8
0
0
1
8
0
0
1
8
3GPP TS 36.523-3 version 13.2.0 Release 13
C-RNTI
Value
tsc_C_RNTI_Def9
'162E'H
5678
tsc_C_RNTI_Def1
0
'1A85'H
6789
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
ETSI TS 136 523-3 V13.2.0 (2017-03)
110
SF0
1
8
1
8
-
SF1
0
0
0
0
0
0
SF2
-
SF3
-
SF4
1
0
0
8
1
0
0
8
1
0
SF5
0
8
0
8
-
SF6
0
0
0
0
0
0
SF7
-
SF8
-
SF9
0
0
1
8
0
0
1
8
0
0
Table 7.1.1.2-1a gives the PDCCH candidates of m' and m'' for default values of common search space aggregation
level =4, UE-specific search space aggregation L=4 resulting in 2 PDCCH candidates m=0,1 and the corresponding
CCE start indices for channel bandwidth of 5MHz and CFI=2, suitable for eMBMS test cases. SF0 and SF5 cannot be
used for UL grant. SF1 and SF6 are not used for DL assignment. SF2, SF3, SF7 and SF8 are not applicable to PDCCH
CCE allocation since they are uplink subframes.
Note: With Max-CCE=13 or 12, aggregation level of 8 results in only 1 PDCCH candidate. Hence aggregation level of
4 is used.
Table 7.1.1.2-1a: CCE Start indices (m' & m'') to be used for various C-RNTIs with CFI=2 (5 MHz)
C-RNTI
Value
tsc_C_RNTI_Def
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
tsc_C_RNTI_Def3
'1111'H
4369
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
13
1
4
0
4
0
8
-
SF1
12
0
4
0
0
0
8
SF2
-
SF3
-
SF4
12
0
8
1
0
0
4
1
8
0
8
1
0
SF5
13
1
4
1
4
0
8
-
SF6
12
0
8
0
4
0
8
SF7
-
SF8
-
SF9
12
1
4
0
0
0
4
1
8
0
8
1
0
Tables 7.1.1.2-2, 7.1.1.2-3 and 7.1.1.2-4 give the PDCCH candidates of m' and m'' for default values of common search
space aggregation level =8, UE-specific search space aggregation L=8 resulting in 2 PDCCH candidates m=0,1 and the
corresponding CCE start indices for bandwidths of 10/15/20 MHz respectively, with the different Max_CCE number
for each subframe.
Table 7.1.1.2-2: CCE Start indices (m' & m'') to be used for default C-RNTI (10 MHz)
C-RNTI
Value
tsc_C_RNTI_Def '1001'H
4097
tsc_C_RNTI_Def '1034'H
2
4148
tsc_C_RNTI_Def '1111'H
3
4369
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
27
1
8
0
8
0
16
-
SF1
25
0
8
0
0
0
16
ETSI
SF2
-
SF3
-
SF4
25
0
16
1
0
0
8
1
16
0
16
1
0
SF5
27
1
8
1
8
0
16
-
SF6
25
0
16
0
8
0
16
SF7
-
SF8
-
SF9
25
1
8
0
0
0
8
1
16
0
16
1
0
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
111
Table 7.1.1.2-3: CCE Start indices (m' & m'') to be used for default C-RNTI (15 MHz)
C-RNTI
Value
tsc_C_RNTI_Def '1001'H
4097
tsc_C_RNTI_Def '1034'H
2
4148
tsc_C_RNTI_Def '1111'H
3
4369
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
41
0
8
0
8
0
24
-
SF1
37
0
8
0
0
0
8
SF2
-
SF3
-
SF4
37
1
8
0
0
0
24
1
0
0
24
1
0
SF5
41
0
8
1
8
1
8
-
SF6
37
0
0
0
16
0
24
SF7
-
SF8
-
SF9
37
0
8
1
16
1
8
0
0
1
8
0
0
Table 7.1.1.2-4: CCE Start indices (m' & m'') to be used for default C-RNTI (20 MHz)
C-RNTI
Value
tsc_C_RNTI_Def '1001'H
4097
tsc_C_RNTI_Def ‘1034'H
2
4148
tsc_C_RNTI_Def ‘1111'H
3
4369
tsc_C_RNTI_Def ‘1FF1'H
4
8177
tsc_C_RNTI_Def ‘04D2'H
5
1234
tsc_C_RNTI_Def ‘0929'H
6
2345
tsc_C_RNTI_Def ‘0D80'H
7
3456
tsc_C_RNTI_Def ‘11D7'H
8
4567
tsc_C_RNTI_Def ‘162E'H
9
5678
tsc_C_RNTI_Def ‘1A85'H
10
6789
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
55
1
8
0
32
0
16
0
16
0
8
0
32
1
8
0
16
0
32
1
8
-
SF1
50
0
8
0
0
0
40
0
32
0
16
0
24
0
32
0
32
0
40
0
0
ETSI
SF2
-
SF3
-
SF4
50
0
16
1
24
0
8
1
16
0
40
1
0
0
40
1
0
0
40
1
0
0
24
1
32
0
8
1
16
0
40
1
0
0
16
1
24
1
8
0
0
SF5
55
0
24
1
8
0
40
0
24
0
16
0
24
0
40
1
8
0
16
0
24
-
SF6
50
0
16
0
32
0
40
0
8
0
8
0
24
0
40
0
8
0
16
0
32
SF7
-
SF8
-
SF9
50
0
24
1
32
0
32
1
40
0
16
1
24
1
8
0
0
0
40
1
0
0
16
1
24
1
8
0
0
0
32
1
40
0
16
1
24
1
8
0
0
3GPP TS 36.523-3 version 13.2.0 Release 13
7.1.1.2.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
112
TDD candidates selection in special subframes
In test cases (7.1.3.12/13) testing DL data transmission in special subframes following CCE tables will be used
Table 7.1.1.2.1-1: CCE Start indices (m' & m'') to be used for various default C-RNTI (5 MHz)
C-RNTI
Value
tsc_C_RNTI_Def
'1001'H
4097
tsc_C_RNTI_Def2
‘1034'H
4148
NOTE:
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
SF0
21
1
8
1
SF1
12
1
0
0
0
1
SF2
-
SF3
-
SF4
20
1
8
0
0
0
SF5
21
0
8
1
SF6
12
1
0
0
0
1
SF7
-
SF8
-
SF9
20
0
8
1
0
1
CCE_St_Ind'
8
0
-
-
8
8
0
-
-
8
m''
-
0
-
-
1
-
0
-
-
0
CCE_St_Ind''
-
0
-
-
0
-
0
-
-
0
Special subframes with Max CCE =12 and aggregation of 8 result in only 1 PDCCH. Hence either only
UL grant or DL allocation is possible.
Table 7.1.1.2.1-2: CCE Start indices (m' & m'') to be used for default C-RNTI (20 MHz)
C-RNTI
Value
tsc_C_RNTI_Def '1001'H
4097
tsc_C_RNTI_Def ‘1034'H
2
4148
7.1.2
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
55
1
8
0
32
-
SF1
50
0
8
1
16
1
8
0
0
SF2
-
SF3
-
SF4
50
0
16
1
24
0
8
1
16
SF5
55
0
24
1
8
-
SF6
50
0
16
1
24
0
32
1
40
SF7
-
SF8
-
SF9
50
0
24
1
32
0
32
1
40
ePDCCH Candidate Selection
Total number of eREGs available in a subframe: Max_eREG.
Total number of eCCEs available in a subframe: Max_eCCE.
The value of numberPRB-Pairs=8 to be used in ePDCCH signalling test cases result in MAX_eREG=128 as per TS
36.211 [35] clause 6.2.4A. As per TS 36.211 [35] clause 6.8A.1 results in MAX_eCCE=32.
7.1.2.1
FDD candidates selection
The UE specific search space aggregation L=2 same as in clause 7.1.1.1 is used. For DL transmission for C-RNTI / SPS
C-RNTI value of m=0 (m’) in set config ID 0 shall be used. 'm' is defined in TS 36.213 [30], clause 9.1.4. For UL
transmission for C-RNTI / SPS C-RNTI the lowest value of m=1 (m”) shall be used.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
113
Table 7.1.2.1-1: eCCE Start indices (m' & m'') to be used for various C-RNTIs
C-RNTI
tsc_C_RNTI_Def
Value
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
NOTE:
SF0
0
20
1
4
0
8
1
24
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF1
0
2
1
18
0
24
1
8
SF2
0
10
1
26
0
4
1
20
SF3
0
28
1
12
0
26
1
10
SF4
0
0
1
16
0
14
1
30
SF5
0
26
1
10
0
0
1
16
SF6
0
16
1
0
0
4
1
20
SF7
0
8
1
24
0
22
1
6
SF8
0
22
1
6
0
26
1
10
SF9
0
2
1
18
0
8
1
24
eCCE start indices are independent of bandwidth.
7.1.2.2
TDD candidates selection
The search space aggregation L=8 same as in clause 7.1.1.2 is used. For DL transmission for C-RNTI / SPS C-RNTI
value of m=0 (m’) in set config ID 0 shall be used. 'm' is defined in TS 36.213 [30], clause 9.1.4. For UL transmission
for C-RNTI / SPS C-RNTI the lowest value of m=1(m”) shall be used.
Table 7.1.2.2-1: CCE Start indices (m' & m'') to be used for various C-RNTIs
C-RNTI
Value
tsc_C_RNTI_Def
'1001'H
4097
tsc_C_RNTI_Def2
'1034'H
4148
7.1.3
Max_CCE
m'
CCE_St_Ind'
m''
CCE_St_Ind''
m'
CCE_St_Ind'
m''
CCE_St_Ind''
SF0
21
0
16
0
0
-
SF1
12
0
8
0
0
SF2
-
SF3
-
SF4
20
0
0
1
16
0
24
1
8
SF5
21
0
8
0
0
-
SF6
12
0
0
0
0
SF7
-
SF8
-
SF9
20
0
8
1
24
0
0
1
16
MPDCCH Candidate Selection
The value of numberPRB-Pairs=2+4 (numberPRB-Pairs-v1310= n6) is to be used for MPDCCH in signalling test cases.
The DCI format 6-2 used for P-RNTI will be sent in Type1-common search space. The DCI format 6-1A and 6-1B
scrambled with RA-RNTI will be sent in Type2-common search space. The DCI format 6-1A and 1B scrambled by CRNTI and DCI format 6-0A and 6-0B can be sent either in Type0-common (CEModeA only) or UE Specific by CRNTI search space. For simplicity and to be applicable for both CE Modes, they will always be sent on UE Specific by
C-RNTI search space.
It is assumed that transmissions based on P-RNTI, C-RNTI and RA-RNTI are mutually exclusive in a one UE test
environment. In a subframe any one of following will happen:
-
1 DCI for P-RNTI- 1 DCI for RA-RNTI-
1 or 2 DCI for C-RNTI
For TDD with default ‘specialSubframePatterns’ = ssp6, as per 36.213[30] clause 9.1.5, UE is not required to monitor
MPDCCH in special subframes for both CE Mode’s A and B.
For Type1-common search space for P-RNTI, as per 36.213[30] clause 9.1.5 only one MPDCCH with Aggregation L’ =
24 is defined. This requires all 6 PRB’s to be used. For this eCCE’s with 0 to 23 (i.e. all eCCE’s) are used.
For Type2-common search space for RA-RNTI, Aggregation L’ of 24 results in only one MPDCCH utilising all 6
PRB’s. For this eCCE’s with 0 to 23 (i.e. all eCCE’s) are used.
For UE Specific by C-RNTI search space, if only one of DCI 6-1x and 6-0x is to be sent, then Aggregation L’ of 24
results in only one MPDCCH utilising all 6 PRB’s. For this eCCE’s with 0 to 23 (i.e. all eCCE’s) are used.
For UE Specific by C-RNTI search space, if both UL and DL DCI (6-1x and 6-0x) are to be sent then:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
114
ETSI TS 136 523-3 V13.2.0 (2017-03)
-
For CE Mode B with R=r1, aggregation level L’=8 on 2 PRB’s (the lowest 2 PRB’s in Narrow band), resulting
in only one MPDCCH utilising all 8 eCCE’s with 0 to 7 are used. This is used for DCI 6-1x (36.213[30] table
9.1.5-2b).
-
For CE Mode B with R=r1, aggregation level L’=16 on 4 PRB’s (the highest 4 PRB’s in Narrow band), resulting
in only one MPDCCH utilising all 16 eCCE’s with 0 to 15 are used. This is used for DCI 6-0x(36.213[30] table
9.1.5-2b).
-
For CE Mode A with R=r1, level L’=8 on 4 PRB’s (the highest 4 PRB’s in Narrow band), resulting in two
MPDCCH, MPDCCH 1 with CCE’s 0-7are used for DCI 6- 1x and MPDCCH 2 with CCE’s 8-15are used for
DCI 6- 0x(36.213[30] table 9.1.5-2a).
MPDCCH is repeated based on semi-statically configured higher layer parameter mpdcch-NumRepetition and
dynamically selected by network. Each value of mpdcch-NumRepetition = rmax maps into max 4 allowed values of
repetitions R = r1, r2, r3, r4. UE is required to monitor all r1, r2, r3 & r4 as per 36.213[30] table 9.1.5-2a for CE Mode
A and table 9.1.5-2b for CE mode B.
Following values shall be used for DCI subframe repetition number R based on rmax= mpdcch-NumRepetition default
values:
-
Type1-common search space for P-RNTI, mpdcch-NumRepetition-Paging-r13 =r16, R=r1=1 for both CE-Modes
A & B.
-
Type2-common search space for RA-RNTI, mpdcch-NumRepetition-RA-r13 =r1, R=r1=1, resulting in no
retransmissions is used for both CE-Modes A & B.
-
-
Type2-common search space for RA-RNTI, mpdcch-NumRepetition-RA-r13 =r4, R=r1=1, resulting in no
retransmissions is used for both CE-Modes A & B.
-
Type2-common search space for RA-RNTI, mpdcch-NumRepetition-RA-r13 =r16, R=r1=2, resulting in 2
transmissions is used for both CE-Modes A & B.
-
Type2-common search space for RA-RNTI, mpdcch-NumRepetition-RA-r13 =r64, R=r1=2, resulting in 8
transmissions is used for both CE-Modes A & B.
UE Specific by C-RNTI search space, mpdcch-NumRepetition-r13 =r16, R=r1=2 resulting in 2 transmissions.
-
7.2
UE Specific by C-RNTI search space, mpdcch-NumRepetition-r13 =r1, R=r1=1 resulting in 1 transmission.
Uplink Grant
The Network/SS informs the UE if it is allowed to make Uplink Data transmission by transmitting 'DCI format 0' on
PDCCH. The UE shall transmit (4 TTI later for FDD or variable for TDD) a Transport block of exactly the same size as
specified in DCI format 0. The UE has no control of its own on TB size, and has to merely follow the network, even if
that means lots of MAC padding or resource starving.
The UE has the following means to communicate if it has UL data ready for transmission and subsequently the estimate
of quantity of data to be transmitted.
RACH procedure: UE in idle mode, handed over to a new cell or connected mode but PUCCH is unsynchronized
(sometimes referred to as PUCCH is not configured) will trigger RACH procedure on data ready for transmission in
UL.
Scheduling Request: UE in connected mode, no grant configured, PUCCH is synchronized and has data ready for
transmission in UL, will transmit a scheduling request on PUCCH.
Buffer Status Reports: UE in connected mode, PUCCH synchronized, has a configured grant for current TTI, but grant
is not sufficient to transmit all the data will include MAC control element BSR in the UL MAC PDU.
RACH and SR indicate on data availability and BSR provides an estimate of data available for transmission.
CQI/PMI/RI feedback from the UE which indicates the channel conditions and recommended number of layers.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
115
ETSI TS 136 523-3 V13.2.0 (2017-03)
Hence to determine the exact need of the grant requirement of the UE a network/SS needs to act on all four of the
above. This eventually complicates the SS implementation and hence the grant allocation procedure is simplified such
that SS needs only to react on reception of SR and grant allocation configured from the TTCN.
The SS disables aperiodic CQI/PMI/RI feedback from the UE by setting the ‘CQI request field’ to 0 in DCI format
0/RAR grant.
When request for periodic CQI/PMI/RI feedback is requested due to TTCN configuration, the SS does not react on
periodic CQI/PMI/RI feedback received and still allocates grants as configured from TTCN.
The SS, if configured for maintaining PUCCH synchronization at UE, shall periodically transmit automatically MAC
PDUs containing the MAC control element 'Timing Advance'. The period as configured by the TTCN is set to 80 % of
the 'Time Alignment Timer' default value (750 ms) configured at UE.
Additionally the SS can be configured to automatically transmit a 'configured' UL grant at every reception of a
Scheduling Request. This grant should be selected under the following restrictions:
-
All UE categories can handle this i.e. (for UEs Cat 1 and above TBS <= 5160, for Cat 0/M1 TBS <= 1000).
-
It is sufficiently large that most of uplink signalling messages can be transmitted. In case the grant is not
sufficient to fit the whole UL data, the UE will have to wait for the expiry of RETX_BSR_TIMER and
retransmit a SR. And hence the procedure is repeated.
The following 5 types of grant allocation configurations are possible. Grant allocation Types 1 to 3 are applicable, when
the UE is in connected state. Grant allocation Type 4 is applicable when UE is establishing /re-establishing the RRC
Connection, or during handover or in connected state but PUCCH is not synchronised. Grant allocation type 5 is
applicable when the UE is in connected state and is used for lower category UEs when the UL grants greater than Max
TBS supported by the UE is needed.
Grant Allocation Type 1:
-
SS is configured to maintain PUCCH Synch.
-
SS is configured to send an automatically 'configured Grant' (in terms of IMCS and NPRB) to the UE on every
reception of a Scheduling Request, within 10 subframes. The default configured grant is IMCS = 9 and NPRB = 25
for test cases without IMS signalling within the test body and IMCS = 20 and NPRB = 25for test cases with IMS
signalling within the test body, unless explicitly specified in test cases.
-
By default this type of grant allocation is applied. The majority of Idle mode, RRC and NAS test cases, the
preambles of all tests and the postambles of those tests for which UE is still PUCCH synchronised at the end of
test body. A few Layer 2 tests also use this type of grant.
Grant Allocation Type 2:
-
Configure SS to maintain PUCCH Synch.
-
Configure SS to periodically transmit a grant (IMCS and NPRB). Number of grants (1 or more) and period (in ms)
configured by TTCN.
-
The first grant transmitted is as specified in the explicit timing information. If timing information is "now" the
SS selects the first suitable subframe for UL transmission.
-
The grant allocation period for TDD shall be assigned without conflict with the allowed UL subframes in the
TDD subframe configurations. As example of allocation period, the TDD UL Grant allocation can be assigned as
in multiples of 5 ms.
-
This type of grant allocation is applicable to the majority of RLC, PDCP and a few MAC test cases.
-
No additional grant is allocated on reception of any SRs.
Grant Allocation Type 3:
-
SS may or may not be configured to maintain PUCCH Synch.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
116
ETSI TS 136 523-3 V13.2.0 (2017-03)
-
Configure SS to transmit a one time grant (IMCS and NPRB) in the time requested by TTCN. The one time
transmission is achieved by setting Number of grants=1 and period =Only once
-
This type of grant allocation is suitable for MAC and DRB tests when UE is in UL Synchronised state
Grant Allocation Type 4 (RACH configuration):
-
In addition to the 3 types of UL grant allocations, a fourth type of grant allocation during the RACH procedure is
also possible, where the SS behaves as per the RACH procedure configured and allocates the configured grant
during the RACH procedure. This UL Grant type is used in the configuration for the preamble in many
situations, basically in MAC test cases. This type of grant is further used when UE is establishing/re-establishing
the RRC connection or during handover, or when the UE is not PUCCH synchronised;
Grant Allocation Type 5:
-
SS is configured to maintain PUCCH Synch.
-
Configure SS to periodically transmit a grant (IMCS and NPRB) on reception of SR. Number of grants (1 or
more) and period (in ms) configured by TTCN. The first grant is sent within 10 subframes of SR. Reception of
SR starts/restarts periodic grant transmission. The default configured grant is IMCS = 12 and NPRB = 25 for UE
Cat 1 and IMCS = 14 and NPRB =4 for UE Cat 0/CAT M1 (CE Mode A), unless explicitly specified in test cases.
-
This type of grant allocation is suitable when the UE category is lower than 2. The majority of Idle mode, RRC
and NAS test cases, the preambles of all tests and the postambles of those tests which UE is still PUCCH
synchronised at the end of the test body. A few Layer 2 tests also use this type of grant.
All the UL grant allocation methods define grant allocation in terms of IMCS and NPRB to be used. The SS shall allocate
RBs corresponding to PRB indices 0..(NPRB-1).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.2.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
117
Exception TC list
This clause contains the exception test case list where the explicit uplink grant types other than UL grant type 1 are
specified.
Table 7.2.1-1: Exception test case list with explicit uplink grant types other than UL grant type 1
Group
RLC
MAC
PDCP
RRC
NAS
DRB
7.3
Test Case
7.2.2.6
7.2.2.7
7.2.3.1
7.2.3.2
7.2.3.4
7.2.3.5
7.2.3.6
7.2.3.7
7.2.3.9
7.2.3.10
7.2.3.13
7.2.3.15
7.2.3.17
7.2.3.18
7.2.3.21
7.1.4.1
7.1.4.2
7.1.4.3
7.1.4.4
7.1.4.7
7.1.4.8
7.1.4.10
7.1.4.11
7.1.4.14
7.1.4.15
7.1.4.16
7.1.5.1
7.1.5.2
7.1.5.3
7.1.5.4
7.1.5.5
7.1.6.1
7.3.5.4
8.2.1.5
9.2.1.1.24
12.1.1
12.1.2
Uplink Grant Type 2
X
X
Uplink Grant Type 3
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Downlink Resource Allocation
The DL resource allocation is an SS emulation function. In order to ensure similar DL behaviours (within defined
tolerances) on the different SS platforms in the timing stringent requirements, all downlink resource allocation schemes
specified in the present clause shall be supported by the SS.
When the DL data is to be sent with a specific scheduling requirement, for instance, in a TTI in advance rather than
“now”, the TTCN shall ensure that the data is scheduled at least 100 ms in advance. The 100 ms time in general covers
all time delays, from the time DL data is sent by the TTCN at the EUTRA PTC to the completion of the transmission at
the SS (TTCN delays, codec delays, adaptor delays and SS processing delays at various protocol Layers). In the case of
more than one NAS PDU is piggy-backed in a scheduled RRC PDU, 20ms shall be added per additional NAS PDU:
100ms + ((NoOfNASPDUs – 1) * 20ms; this calculation is based on the assumption that there are not more than 7
piggy-backed NAS messages; this is valid for LTE.
NOTE:
The DL data means DL signalling and/or data in the present clause.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.3.1
118
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCCH DCI default formats
Two types of DCI combinations are identified as default formats for the signalling and protocol test.
DCI combination 1 uses:
-
DCI format 1A, resource allocation type 2 localised, for all DL scheduling types.
DCI combination 2 uses:
-
DCI format 1C, resource allocation type 2 distributed, for scheduling of PCCH/BCCH/RAR; and
-
DCI format 1 resource allocation type 0, for UE dedicated scheduling.
7.3.1.1
Default DCI Format to be used in test cases configuring MIMO
Transmission mode 3 will be used in MIMO test cases configuring 2 Transmit antenna SS environment. As per 36.213
Table 7.1-5, in Transmission mode 3, UE is expected to decode only DCI formats 2A and 1A. Similarly for
Transmission mode 4, UE is expected to decode only DCI formats 2 and 1A. Hence for all test cases configuring 2TX
(2 antenna ports) at SS, DCI combination 1 is the default DCI combination to be applied. This allows DCI format 1A to
be used as default DL scheduling scheme for test sequences not explicitly specified to use DCI formats 2A or 2(i.e.
preamble, postamble etc.)
7.3.2
Radio parameters configured
The SS shall support DL QPSK, 16QAM and 64QAM modulation schemes. The configured radio parameters, including
DCI format, resource allocation types, maximum allowed modulation scheme, first virtual / physical resource block to
be used, maximum available resource blocks and redundancy version, are provided to the SS.
In the normal signalling test condition, DL RLC and HARQ retransmissions are rare. The redundancy version is
provided to allow the occasional HARQ retransmissions. For those MAC, RLC tests contained in table 7.3.2-1 where
timing requirements are involved the DL or UL HARQ retransmissions are not tolerable. Table 7.3.2-2 lists the RLC
tests where timing requirements are involved, only one DL or UL HARQ retransmission per transport block is tolerable.
Unless otherwise specified, if HARQ retransmissions occur in the test cases contained in table 7.3.2-1 or more than one
HARQ retransmission occurs in the test cases of table 7.3.2-2, the test cases will be terminated with verdict
inconclusive.
NOTE:
If the test is expecting the reporting of UL ACK/NACK for the DL MAC PDUs, or is configuring the
PHICH in a certain mode, HARQ retransmissions other than those that are already specified in the prose
will have an impact on the test sequence. If test cases perform scheduling of data transmissions and/or
receptions, or the testing timers in the test cases are less than 900 ms (i.e. the tolerance for 90 ms), HARQ
retransmissions will make it difficult to continue testing.
Table 7.3.2-1: TC list intolerable of HARQ retransmissions
Test case
Comment
MAC
7.1.3.1, 7.1.3.2, 7.1.3.4, 7.1.3.5, 7.1.3.6, 7.1.3.9, 7.1.6.1,
HARQ feedback reporting enabled or DL CRC errors
7.1.6.2
introduced; DL HARQ un specified (re)transmissions will
result in ‘Fail' in test body, UL HARQ retransmissions are
allowed;
7.1.4.8
Strict relationship between grant and UL data
7.1.4.3
Up to 104 PDUs to be sent in DL every TTI;
7.1.4.2, 7.1.4.11, 7.1.4.12, 7.1.4.14, 7.1.5.4
HARQ feedback transmission specified or PHICH errors
introduced
7.1.4.15, 7.1.4.16
Periodic UL grants
RLC
7.2.2.6, 7.2.2.7, 7.2.2.8, 7.2.2.10, 7.2.3.1, 7.2.3.2, 7.2.3.4, Tolerating HARQ retransmissions is not feasible due to rigid
7.2.3.5, 7.2.3.10, 7.2.3.13, 7.2.3.14, 7.2.3.15, 7.2.3.18
timing and scheduling conditions. Testing timer < 900 ms
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
119
Table 7.3.2-2: TC list intolerable of more than one HARQ retransmission per transport block
Test case
Comment
RLC
7.2.3.6, 7.2.3.7, 7.2.3.8, 7.2.3.9, 7.2.3.17
Tolerating more than one HARQ
retransmission is not feasible due to rigid
timing and scheduling conditions. Testing
timer < 900 ms
7.3.2.1 HARQ Retransmission when MIMO is configured
For test cases configuring MIMO, if in a TTI more than one transport blocks are scheduled (DCI format 2/ 2A/2B), the
HARQ retransmission is handled independently for each transport block by SS. In case UE ACKs one Transport block
and NACKs the other and there is no fresh data scheduled for transmission, SS only schedules the NACKed transport
block for retransmission, using same Imcs as used in initial transmission, mapped to codeword 0. Acked Transport block
(and hence codeword 1) is disabled by setting corresponding I MCS = 0 and rvidx = 1. Resource allocation (Nprb) used in
retransmission is same as in initial transmission.
It is assumed that retransmission and fresh data scheduled in one TTI will not happen.
7.3.3
General DL scheduling scheme
The rules in the present clause, unless particularly specified, are applied to both default DCI combinations.
The bandwidth of 5/10/15/20 MHz makes 25/50/75/100 available physical resource blocks respectively. The
25/50/75/100 resource blocks are divided into three distinct sets. Exact set sizes and the elements contained in the
individual sets depend upon the DCI combination to be applied.
-
The first set is reserved for BCCH mapped to DL-SCH (SI-RNTI).
-
The second set is reserved for PCCH mapped to DL-SCH (P-RNTI).
-
The third set is used for one of mutually exclusive transmissions of:
-
'Random Access Response' mapped to DL-SCH (RA-RNTI); or
-
UE-dedicated scheduling mapped to DL-SCH (C-RNTI/ SPS C-RNTI/ Temp C-RNTI).
For each subframe for which data of one or more types is scheduled, the SS shall select a Transport Block Size (TBS),
independently for each type of data scheduled, such that:
-
All the scheduled data is transmitted respecting the timing information. More details on the timing information
can be found in clause 7.8.
-
Not more than MaxRbCnt resource blocks are used, for DCI format 1C, NPRB = MaxRbCnt.
-
Minimum MAC Padding is performed.
-
If all scheduled Data cannot be transmitted in the indicated subframe, for example due to TDD and half duplex
configuration, it shall be transmitted in the next available subframe.
7.3.3.1
Additional rules for BCCH scheduling scheme
This scheme is applicable for Data transmission on logical channel BCCH mapped to DL-SCH, PDCCH scrambled by
SI-RNTI. For both DCI combinations 4 physical resource blocks are reserved for BCCH transmission. The maximum
modulation scheme is restricted to QPSK.
Following additional rules are applied for TBS selection:
-
The Max TBS, the maximum TBS allowed for the scheduling scheme, is restricted to 600. (nearest value
achievable for ITBS = 9 and NPRB = 4, as per table 7.1.7.2.1-1 of TS 36.213 [30]).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
120
ETSI TS 136 523-3 V13.2.0 (2017-03)
-
If the scheduled Data cannot fit into a TBS smaller or equal to Max TBS, SS generates an error (it's a TTCN
error). TTCN should gracefully exit the test case as a fatal error, assigning inconclusive verdict.
-
Rules in clause 7.3.3.1.1 for DCI combination 1 and in clause 7.3.3.1.2 for DCI combination 2 shall be applied.
7.3.3.1.1
BCCH with DCI combination 1
TS 36.213 [30], table 7.1.7.2.1-1, rows with ITBS =0..26 and columns with NPRB =2 (corresponding to TPC LSB =0)
and NPRB =3 (corresponding to TPC LSB =1), TBS <=Max TBS are applicable.
Distinct TBSs and all (TPC LSB, ITBS) combinations for each distinct TBS are listed in the sheet.
If a TBS can have two (TPC LSB, ITBS) combinations, the combination with TPC LSB =0 is selected.
RIV indicates 4 PRBs with index 0..3 allocated.
7.3.3.1.2
BCCH with DCI combination 2
TS 36.213 [30], table 7.1.7.2.3-1, ITBS =0..17 with TBS ≤Max TBS are applicable.
RIV indicates 4 virtual RBs with index 0..3 allocated. These virtual RBs correspond to the physical RBs
-
with index 0, 6, 12, 18 in even slots and 12, 18, 0, 6 in odd slots for 5 MHz bandwidth;
-
with index 0, 12, 27, 39 in even slots and 27, 39, 0, 12 in odd slots for 10 MHz bandwidth;
-
with index 0, 16, 48, 64 in even slots and 48, 64, 0, 16 in odd slots for 15 MHz bandwidth;
-
with index 0, 24, 48, 72 in even slots and 48, 72, 0, 24 in odd slots for 20 MHz bandwidth.
7.3.3.2
Additional rules for PCCH specific scheduling scheme
This scheme is applicable for Data transmission on logical channel PCCH mapped to DL-SCH, PDCCH scrambled by
P-RNTI. For DCI combination 1, one physical resource block is reserved. For DCI combination 2, two physical
resource blocks are reserved for 5 MHz bandwidth, and four physical resource blocks are reserved for 10 MHz, 15 MHz
or 20 MHz bandwidth. The maximum modulation scheme is restricted to QPSK.
Following additional rules are applied for TBS selection:
-
If the scheduled Data cannot fit into Max TBS, SS generates an error (it's a TTCN error). TTCN should
gracefully exit the test case as a fatal error, assigning inconclusive verdict.
-
Rules in clause 7.3.3.2.1 for DCI combination 1 and clause 7.3.3.2.2 for DCI combination 2 shall be applied.
7.3.3.2.1
PCCH with DCI combination 1
TS 36.213 [30], table 7.1.7.2.1-1, rows with ITBS =0..26 and columns with NPRB =2 (corresponding to TPC LSB =0)
and NPRB =3 (corresponding to TPC LSB =1) TBS < =Max TBS are applicable.
The Max TBS is restricted to 120 (nearest value achievable for ITBS = 9 and NPRB =1, as per table 7.1.7.2.1-1 of
TS 36.213 [30]).
Distinct TBSs and all (TPC LSB, ITBS) combinations for each distinct TBS are listed in the sheet.
If a TBS can have two (TPC LSB, ITBS) combinations, the combination with TPC LSB =0 is selected.
RIV indicates 1 PRBs with index 4 allocated.
7.3.3.2.2
PCCH with DCI combination 2
TS 36.213 [30], table 7.1.7.2.3-1, ITBS =0..11 for 5 MHz/ ITBS =0..17 for 10, 15 or 20 MHz with TBS ≤ Max TBS are
applicable.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
121
ETSI TS 136 523-3 V13.2.0 (2017-03)
The Max TBS is restricted to
296 bits (nearest value achievable for ITBS = 9 and NPRB =2) for 5 MHz bandwidth,
600 bits (nearest value achievable for ITBS = 9 and NPRB = 4) for 10, 15 or 20 MHz bandwidth.
RIV indicates either two virtual RBs with index 4 and 5 allocated, or four virtual RBs with index 4 to 7 allocated. These
virtual RBs correspond to physical RBs:
with index 1 and 7 in even slots and 13 and 19 in odd slots for 5 MHz bandwidth;
with index 1, 13, 28, 40 in even slots and 28, 40, 1, 13in odd slots for 10 MHz bandwidth;
with index 1, 17, 49, 65 in even slots and 49, 65, 1, 17 in odd slots for 15 MHz bandwidth;
with index 1, 25, 49, 73 in even slots and 49, 73, 1, 25 in odd slots for 20 MHz bandwidth.
7.3.3.3
Additional rules for RAR specific scheduling scheme
This scheme is applicable for transmission of Random Access Response mapped to DL-SCH, PDCCH scrambled by
RA-RNTI. For both DCI combinations four physical resource blocks are reserved. The maximum modulation scheme is
restricted to QPSK.
Following additional rules are applied for TBS selection:
-
The Max TBS is restricted to 600 bits (nearest value achievable for ITBS = 9 and NPRB =4, as per table 7.1.7.2.1-1
of TS 36.213 [30]).
-
If the scheduled Data cannot fit into Max TBS, SS generates an error (it's a TTCN error). TTCN should
gracefully exit the test case as a fatal error, assigning inconclusive verdict.
-
Rules in clause 7.3.3.3.1 for DCI combination 1 and clause 7.3.3.3.2 for DCI combination 2 shall be applied.
7.3.3.3.1
RAR with DCI combination 1
TS 36.213 [30], table 7.1.7.2.1-1, rows with ITBS = 0..26 and columns with NPRB = 2 (corresponding to TPC LSB = 0)
and 3 (corresponding to TPC LSB = 1) TBS ≤ Max TBS are applicable
Distinct TBSs and all (TPC LSB, ITBS ) combinations for each distinct TBS are listed in the sheet.
If a TBS can have two (TPC LSB, ITBS ) combinations, the combination with TPC LSB = 0 is selected.
RIV indicates 4 PRBs with index 5..8 allocated.
7.3.3.3.2
RAR with DCI combination 2
TS 36.213 [30], table 7.1.7.2.3-1, ITBS = 0..17 with TBS <= Max TBS are applicable.
RIV indicates 4 virtual RBs are allocated. These corresponds to physical RB
with index 13, 19, 2, 8 in even slots and 1, 7, 14, 20 in odd slots for 5 MHz bandwidth;
with index 2, 14, 29, 41 in even slots and 29, 41, 2, 14 in odd slots for 10 MHz bandwidth;
with index 2, 18, 50, 66 in even slots and 50, 66, 2, 18 in odd slots for 15 MHz bandwidth;
with index 2, 26, 50, 74 in even slots and 50, 74, 2, 26 in odd slots for 20 MHz bandwidth.
7.3.3.4
Additional rules for UE-dedicated scheduling scheme in normal mode
The UE-dedicated DL scheduling can work in the normal mode or in the explicit mode. The two resource allocation
schemes shall be reconfigurable from each other when the UE and SS are not sending and receiving data, for instance,
at end of the test preamble and before the beginning of the test body.
The present clause is specified for the use of the normal mode. The explicit mode is referred to clause 7.3.3.6.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
122
ETSI TS 136 523-3 V13.2.0 (2017-03)
The scheme specified in the present clause is applicable for transmission of data dedicated to a UE in a DL subframe,
mapped to DL-SCH, PDCCH scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI when spatial multiplexing MIMO
mode is not configured. The maximum modulation scheme is restricted to 64QAM. For the DCI combination 1, 20
physical resource blocks (5 to 24), and for the DCI combination 2, 17 physical resource blocks are reserved. In the case
when three intra frequency cells are applied to the test in the DCI combination 1, for the purpose of interference
reduction, only 9 PRBs (16 to 24) are reserved.
In TDD normal TBS selection mode, no data is transmitted in DwPTS of the special subframe. For FDD, data can be
transmitted in any subframe, except for half-duplex Type B UEs for which scheduling restrictions are specified in
clause 7.26.
The following additional rules are applied for TBS selection:
-
Multiple ASPs can also carry same explicit timing information; indicating different ASP payloads, eventually
needs to be transmitted in 1 TTI.
-
For UE Category ≠ 0 the Max TBS is restricted to 10296 bits (Max supported by UE category type 1).
-
For UE Category = 0 and M1, the Max TBS is restricted to 1000 bits. Hence in all TBS sheets only TB
combinations with TBSize ≤ 1000 are used.
For 5 MHz bandwidth and the DCI combination 1 with 20 PRBs or DCI combination 2, the TBS 8248, 8760, and 9528
are blocked as they result in coding rates higher than 0.93.
For 5 MHz bandwidth and special DCI combination 1 with 9 PRBs, the TBS 2216, 5992 and 6712 are blocked as they
result in coding rates higher than 0.93.
For 10 MHz, 15 MHz and 20 MHz bandwidths none of TBSs are blocked due to coding rates higher than 0.93.
TBS 280 is blocked for all bandwidths as it can be achieved by only Nprb =1 and Itbs=15, requiring 64 QAM
modulation scheme. This TBS would normally be used for “RACH procedure MSG4+RRCconnectionSetup”.
The blocked TBS are considered to be not available for selection.
-
Data pending for transmission in a given sub-frame consists of (listed in transmission priority order):
-
MAC Control Elements that the SS needs to send.
-
AMD STATUS PDU(s) that the SS needs to send.
-
Data not sent in previous subframe(s).
-
Fresh Data scheduled for transmission in this subframe for all logical channels.
-
Distinct TBSs and all (NPRB, ITBS) combinations for each distinct TBS are listed in the sheet.
-
If a TBS size can be achieved with more than one combination of IMCS (ITBS) and NPRB:
-
Select combination with lowest delta between NPRB and IMCS.
-
If still more than one combination remain, select combination with highest NPRB.
-
Not more than one RLC Data PDU shall be placed in a MAC PDU per logical channel (i.e. minimize RLC
segmentation).
-
In a subframe, in case there is data pending for transmission from more than one logical channel, for each type of
data pending for transmission as defined above, priority shall be given to the logical channel with the lowest
logical channel priority value. In case of more than one logical channel with the same logical channel priority
value, these logical channels should be served equally. Data pending for transmission from more than one logical
channel will rarely happen for the signalling and protocol test.
-
Data not transmitted within a subframe is scheduled as pending for transmission in the next available subframe
according to the priorities given above. Pending data for transmission will rarely happen for the signalling and
protocol test.
-
TBS selected in a context by various platforms shall be within an allowed deterministic tolerance of:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
-
123
ETSI TS 136 523-3 V13.2.0 (2017-03)
-
2 bytes for potential Timing Advance Command MAC Control Element (1 byte data + 1 byte MAC sub
header).
-
4 bytes each for AMD STATUS PDU (2 bytes data + 2 bytes MAC subheader).
-
Therefore in the worst case the SS may add up to (2 + 4 x NAMRB ) bytes to the data scheduled for
transmission in a certain subframe, where NAMRB is the number of AM radio bearers (SRB or DRB) actively
sending DL data in the test, in any subframe.
For DCI combination 1 RIV is calculated based on physical resource blocks corresponding to NPRB of the
selected TBS and (NPRB, ITBS) combination. The physical resource blocks that can be allocated are the first NPRB
resources of index range
-
5..24 for 5 MHz bandwidth,
-
28..49 for 10 MHz bandwidth,
-
9..30 for 15 & 20 MHz bandwidth.
For DCI combination 2, RBG assignment is calculated based on physical resource blocks corresponding to NPRB
of the selected TBS and (NPRB, ITBS) combination. The size of RBG is 2 for 5 MHz, 3 for 10 MHz and 4 for 15 &
20 MHz. The available physical resource blocks for allocation are:
-
For 5 MHz bandwidth, RBG1(2,3), RBG2(4,5), RBG4(8,9), RBG5(10,11), RBG7(14,15), RBG8(16,17),
RBG10(20,21), RBG11(22,23) and RBG12(24). If NPRB is even, the first NPRB /2 available RBGs are
allocated. If NPRB is odd, then first (NPRB -1)/2 RBGs and RBG 12 are allocated.
-
For 10 MHz bandwidth, RBG1(3,4,5), RBG2(6,7,8), RBG3(9,10,11), RBG5(15,16,17), RBG6(18,19,20),
RBG10(30,31,32), RBG11(33,34,35), RBG12(36,37,38) and RBG16(48,49). If NPRB mod 3 is 0, the first
NPRB /3 RBGs are allocated. If NPRB mod 3 is 2, then first (NPRB -2)/3 available RBGs and RBG 16 are
allocated.
-
For 15 MHz bandwidth, RBG1(4,5,6,7), RBG2(8,9,10,11), RBG3(12,13,14,15), RBG5(20,21,22,23),
RBG6(24,25,26,27), RBG7(28,29,30,31), RBG11(44,45,46,47), RBG13(52,53,54,55), RBG14(56,57,58,59),
RBG15(60,61,62,63), RBG17(68,69,70,71), RBG18(72.73.74). If NPRB mod 4 is 0, the first NPRB /4 RBGs are
allocated. If NPRB mod 4 is 3, then first (NPRB -3)/4 available RBGs and RBG 18 are allocated.
-
For 20 MHz bandwidth, RBG1(4,5,6,7), RBG2(8,9,10,11), RBG3(12,13,14,15), RBG4(16,17,18,19),
RBG5(20,21,22,23), RBG7(28,29,30,31), RBG8(32,33,34,35), RBG9(36,37,38,39), RBG10(40,41,42,43),
RBG14(56,57,58,59), RBG15(60,61,62,63), RBG16(64,65,66,67), RBG17(68,69,70,71),
RBG19(76.77.78.79) and RBG20(80,81,82,83). The first NPRB /4 RBGs are allocated.
7.3.3.5
DL Resource allocation bitmaps
7.3.3.5.1
DCI combination 1
Table 7.3.3.5.1-1: Physical resource allocation bitmap
for DCI combination 1 (5 MHz) with 20 PRBs
NPRB
BCCH
PCCH
RAR
UE-Dedicated
0
1
2
3
4
5
6
7
8
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
124
Table 7.3.3.5.1-2: Physical resource allocation bitmap
for DCI combination 1 (5 MHz) with 9 PRBs
NPRB
BCCH
PCCH
RAR
UE-Dedicated
0
1
2
3
4
5
6
7
8
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Table 7.3.3.5.1-3 (columns 0–34): Physical resource allocation bitmap
for DCI combination 1 (10 MHz)
NPRB
0 1 2 3 4 5 6 7 8
BCCH
PCCH
RAR
UE-Specific
9..22
23..27
Not
Used
Used for PBCH and other common
signals
28 29 30 31 32 33 34
Table 7.3.3.5.1-3 (columns 35–49): Physical resource allocation bitmap
for DCI combination 1 (10 MHz)
NPRB
BCCH
PCCH
RAR
UE-Specific
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Table 7.3.3.5.1-3A (columns 0–20): Physical resource allocation bitmap
for DCI combination 1 (15 MHz)
NPRB
BCCH
PCCH
RAR
UE-Specific
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Table 7.3.3.5.1-3B (columns 21-74): Physical resource allocation bitmap
for DCI combination 1 (15 MHz)
NPRB
BCCH
PCCH
RAR
UE-Specific
21
22
23
24
25
26
27
28
29
30
31..33
34..41
42..74
Not Used
Used for PBCH and
other common
signals
Not Used
Table 7.3.3.5.1-4 (columns 0–20): Physical resource allocation bitmap
for DCI combination 1 (20 MHz)
NPRB
BCCH
PCCH
RAR
UE-Specific
0
1
2
3
4
5
6
7
8
9
10
ETSI
11
12
13
14
15
16
17
18
19
20
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
125
Table 7.3.3.5.1-5 (columns 21-99): Physical resource allocation bitmap
for DCI combination 1 (20 MHz)
NPRB
BCCH
PCCH
RAR
UE-Specific
21
22
7.3.3.5.2
23
24
25
26
27
28
29
30
31..46
47..52
53..99
Not Used
Used for PBCH and
other common
signals
Not Used
DCI combination 2
Table 7.3.3.5.2-1: Physical resource allocation bitmap
for DCI combination 2 (5 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Dedicated
0
0
2
1
2
3
4
5
6
1
3
4
7
8
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
2
3
0
1
5
8
4
6
9
6
7
5
7
8
9
Table 7.3.3.5.2-2 (columns 0-20): Physical resource allocation bitmap
for DCI combination 2 (10 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBGs
0
0
2
1
2
3
4
5
6
7
8
4
6
8
10
x
x
0
1
2
9 10 11 12 13 14 15 16 17 18 19 20
1
3
5
7
9
11
x x
3
4
5
6
Table 7.3.3.5.2-2 (columns 21-41): Physical resource allocation bitmap
for DCI combination 2 (10 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBGs
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
2
3
0
1
6
7
4
5
10
11
8
9
x x x x x x x
x x
7
8
9
10
11
12
13
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
126
Table 7.3.3.5.2-2 (columns 42-49): Physical resource allocation bitmap
for DCI combination 2 (10 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBG's
42 43 44 45 46 47 48 49
Not Used
14
15
16
Table 7.3.3.5.2-2a (columns 0-19): Physical resource allocation bitmap
for DCI combination 2 (15 MHz)
nprb
BCCHEven
BCCH-Odd
PCCHEven
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBG's
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0
2
16
17
18
1
3
4
6
5
7
8
10
x
19
9
11
x
x
0
1
2
x
3
4
Table 7.3.3.5.2-2a (columns 20-39): Physical resource allocation bitmap
for DCI combination 2 (15 MHz)
nprb
BCCHEven
BCCH-Odd
PCCHEven
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBG's
20
21
22
23
24
25
26
5
27
28
29
30
6
31
32
33
34
7
35
36
37
38
8
39
9
Table 7.3.3.5.2-2a (columns 40-59): Physical resource allocation bitmap
for DCI combination 2 (15 MHz)
nprb
BCCHEven
BCCH-Odd
PCCHEven
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
40
41
42
43
44
45
46
47
48
49
50
2
0
6
4
10
8
x
ETSI
x
51
52
53
54
55
56
57
58
59
3GPP TS 36.523-3 version 13.2.0 Release 13
RBG's
ETSI TS 136 523-3 V13.2.0 (2017-03)
127
10
11
12
13
Table 7.3.3.5.2-2a (columns 60-74): Physical resource allocation bitmap
for DCI combination 2 (15 MHz)
nprb
BCCHEven
BCCH-Odd
PCCHEven
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBG's
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
3
1
7
5
11
9
x
x
15
16
17
18
Table 7.3.3.5.2-3 (columns 0-19): Physical resource allocation bitmap
for DCI combination 2 (20 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBGs
0
0
2
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
4
6
8
10
x
x
0
1
2
3
4
Table 7.3.3.5.2-3 (columns 20-39): Physical resource allocation bitmap
for DCI combination 2 (20 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBGs
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
1
3
5
7
9
11
x x
5
6
7
8
9
Table 7.3.3.5.2-3 (columns 40-59): Physical resource allocation bitmap
for DCI combination 2 (20 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBG's
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59
2
0
6
4
10
8
x x x
10
11
12
13
14
ETSI
14
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
128
Table 7.3.3.5.2-3 (columns 60-79): Physical resource allocation bitmap
for DCI combination 2 (20 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBGs
60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
3
1
7
5
11
9
x x
15
16
17
18
19
Table 7.3.3.5.2-3 (columns 80-99): Physical resource allocation bitmap
for DCI combination 2 (20 MHz)
NPRB
BCCH-Even
BCCH-Odd
PCCH-Even
PCCH-Odd
RAR-Even
RAR-Odd
UE-Specific
RBGs
NOTE:
7.3.3.6
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
Not Used
20
21
22
23
24
Odd and even refer to slots.
UE-dedicated scheduling scheme in explicit mode
This scheme applies to:
1. spatial multiplexing MIMO configurations or
2. transmit diversity MIMO configurations and non-MIMO configuration where the normal mode scheduling
scheme is inappropriate.
SS is configured with an exact TBS (modulation and coding scheme, Imcs, and number of resource blocks, Nprb) to use.
Other parameters, such as the HARQ process number and redundancy version to use for each transmission, are also
configured by the TTCN. SS shall use TBS sheets with matching DCI format and Resource allocation Type. If the
parameter 'FirstRbIndex' is configured different than specified in respective TBS sheet, the resource block bit maps in
TBS sheet s are shifted by ' FirstRbIndex' and applied, with an exception for Resource allocation type 0 where only the
full size 'Resource block groups' are shifted by ' FirstRbIndex'; if the last Resource block group is not full size, and is
part of resource block bitmap, it is applied without any shift.
All data scheduled for a certain subframe shall be transmitted in the single indicated subframe, using configured
parameters. The TTCN shall ensure that the configured parameters are consistent, in particular that the scheduled data
size and the configured TBS match each other. Data scheduled by the prose, and hence also by the TTCN, provides
possible space for the Timing Advance MAC control element and the RLC Status PDU. The SS shall include one of
these if so triggered, else the bits reserved for these are filled by MAC padding.
Additionally, in the case of MIMO data scheduled for transmission in a given sub-frame, this consists of (listed in
transmission priority order):
-
MAC Control Elements that the SS needs to send (if triggered).
-
AMD STATUS PDU(s) that the SS needs to send (if triggered).
-
Fresh data scheduled for transmission in this subframe for one or more logical channels, as per logical channel
priority [lower value = higher priority]; if data is available for more than one logical channel with the same
priority, then the logical channel corresponding to the DRB-ID with the lower value has the higher priority.
-
MAC padding.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
129
The following additional rules need to be applied on data scheduled for transmission to be mapped on two transport
blocks corresponding to two code words:
-
Higher priority data (as stated above) maps on to Transport Block 1 and lower priority data maps on Transport
Block 2 (if Transport Block 1 gets full); and
-
Minimum MAC padding is performed in Transport Block 1; and
-
If data from one logical channel needs to be mapped on to two transport blocks, the PDCP PDUs with lower
PDCP sequence numbers get mapped on to Transport Block 1.
By default no data is scheduled in TDD special subframes (i.e. subframes 1 and 6 for default TDD subframe
configuration). For testing DL data reception in TDD special subframe, explicit mode TBS selection shall be used. The
TTCN shall ensure that the configured parameters are consistent, in particular that the scheduled data size and the
configured TBS match each other. As per TS36.213 [30] clause 7.1.7, for special subframe configuration 9 with normal
cyclic prefix or special subframe configuration 7 with extended cyclic prefix, the actual Nprb used for TB size
calculation will be a max( floor{ Nprb in DCI command *0.375},1). Tables 7.3.3.6-1/2 give the mapping for Nprb in
DCI command and Nprb used for TB size determination.
Table 7.3.3.6-1: Nprb DCI to Nprb TBS mapping for 20 Mhz
Nprb in DCI command
(configured by TTCN)
4
8
12
16
20
24
28
32
36
40
44
48
54
60
Nprb used for TBS determination
1
3
4
6
7
9
10
12
13
15
16
18
20
22
Table 7.3.3.6-2: Nprb DCI to Nprb TBS mapping for 5 Mhz
Nprb in DCI command
(configured by TTCN)
Nprb used for TBS determination
7.3.3.6.1
4
6
8
12
14
16
1
2
3
4
5
6
DL Scheduling in Transport Block Size Selection Test Cases
The MAC transport block size selection test cases defined in clause 7.1.7 of TS 36.523-1 [1], use bandwidths of
5/10/15/20MHz. For the preamble and post amble in these tests, the default scheduling rules defined in clauses 7.3.3.1
to 7.3.3.4 for 5/10/15/20 MHz and DCI combination 1A are applied respectively. During the test body, when the actual
TB sizes with appropriate DCI and resource allocation formats needed are to be tested, the SS is configured in explicit
mode for UE-dedicated scheduling.
7.3.3.7
Resource allocation sheets
Attached with this Technical Specification, the DL resource allocation tables can be found, providing physical resource
allocations for various transport block sizes, developed as per rules specified in clause 7.3.3, in Microsoft Excel format.
Each individual sheet in the workbook represents various scheduling schemes as per table 7.3.3.7-1.
Table 7.3.3.7-1: DL resource allocation sheets
S. No
1
Sheet Name
DCI-1A-PCCH
2
DCI-1A-BCCH
3
DCI-1A-RAR
4
DCI-1A-UE-Specific
5
DCI-1A-3-IntraFreqUE-Specific
Description
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by P-RNTI (5 MHz, 10 MHz, 15 MHz and 20 MHz)
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by SI-RNTI (5 MHz, 10 MHz, 15 MHz and 20 MHz)
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by RA-RNTI (5 MHz, 10 MHz, 15 MHz and 20 MHz)
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI (5 MHz)
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI and three Intra
Freq cells are configured (5 MHz)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
S. No
6
Sheet Name
DCI-1A-UE-Specific-10MHz
6A
DCI-1A-UE-Specific-15MHz
7
DCI-1A-UE-Specific-20MHz
8
DCI-1C-PCCH
9
DCI-1C-BCCH
10
DCI-1C-RAR
11
DCI-1-UE-Specific
12
DCI-1C-PCCH-10MHz-Gap1
13
DCI-1C-BCCH-10MHz-Gap1
14
DCI-1C-RAR-10MHz-Gap1
15
DCI-1-UE-Specific10MHz-Gap1
15A
DCI-1C-PCCH-15MHz-Gap1
15B
DCI-1C-BCCH-15MHz-Gap1
15C
DCI-1C-RAR-15MHz-Gap1
15D
DCI-1-UE-Specific15MHz-Gap1
16
DCI-1C-PCCH-20MHz-Gap1
17
DCI-1C-BCCH-20MHz-Gap1
18
DCI-1C-RAR-20MHz-Gap1
19
DCI-1-UE-Specific-20MHzGap1
20
DCI-1-RA0-ExplicitConfig
21
DCI-1-RA1-ExplicitConfig
22
DCI1A-ExplicitConfig
23
DCI-2A-RA0-ExplicitConfig
24
DCI-2A-RA1-ExplicitConfig
7.3.3.8
130
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI (10 MHz)
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI (15 MHz)
DL Resource scheduling for DCI format 1A and PDCCH is
scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI (20 MHz)
Also in preamble/postamble phase of MAC TBS test cases with 15
MHz bandwidth configured
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by P-RNTI (5 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by SI-RNTI (5 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by RA-RNTI (5 MHz)
DL Resource scheduling for DCI format 1, Resource allocation 0
and PDCCH is scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI
(5 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by P-RNTI (10 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by SI-RNTI (10 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by RA-RNTI (10 MHz)
DL Resource scheduling for DCI format 1, Resource allocation 0
and PDCCH is scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI
(10 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by P-RNTI (15 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by SI-RNTI (15 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by RA-RNTI (15 MHz)
DL Resource scheduling for DCI format 1, Resource allocation 0
and PDCCH is scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI
(15 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by P-RNTI (20 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by SI-RNTI (20 MHz)
DL Resource scheduling for DCI format 1C and PDCCH is
scrambled by RA-RNTI (20 MHz)
DL Resource scheduling for DCI format 1, Resource allocation 0
and PDCCH is scrambled by C-RNTI/ SPS C-RNTI/ Temp C-RNTI
(20 MHz)
DL Resource scheduling for DCI format 1, Resource allocation 0
and PDCCH is scrambled by C-RNTI
DL Resource scheduling for DCI format 1, Resource allocation 1
and PDCCH is scrambled by C-RNTI
DL Resource scheduling for DCI format 1A, Resource allocation
2(localised & distributed) and PDCCH is scrambled by C-RNTI
DL Resource scheduling for DCI format 2A, Resource allocation 0
and PDCCH is scrambled by C-RNTI
DL Resource scheduling for DCI format 2A, Resource allocation 1
and PDCCH is scrambled by C-RNTI
MPDCCH DL DCI formats
The PRB scheduling is for the PRB’s within a selected Narrow Band consisting of 6 resources. Hence all PRB selection
is restricted to these 6 PRB’s in the ‘X’ selected narrow band.
7.3.3.8.1
BCCH
There is no MPDCCH transmitted for BCCH hence no DCI format. All six contiguously allocated localized virtual
resource blocks within a narrowband are used. The Itbs is configured by RRC.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.3.3.8.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
131
PCCH
DCI format 6-2 is used for PCCH scheduling. All six contiguously allocated localized virtual resource blocks within a
narrowband are used. The Itbs to TB size mapping is in table 7.3.3.8.2-1 derived from TS 36.213 [30] table 7.1.7.2.3-1.
The Itbs = Imcs in the DCI 6-2. The Imcs = Itbs shall be less than or equal to 7.
Table 7.3.3.8.2-1: Transport Block Size (TBS) table for PCCCH, DCI 6-2
7.3.3.8.3
I TBS
0
1
2
3
4
5
TBS
40
56
72 120 136
144
6
7
176 208
RAR
7.3.3.8.3.1
RAR with DCI format 6-1A for CE ModeA UE
TS 36.213 [30], table 7.1.7.2.1-1, rows with ITBS = 0..15 and columns with NPRB = 2 (corresponding to TPC LSB = 0)
and 3 (corresponding to TPC LSB = 1) TBS ≤ Max TBS are applicable
Distinct TBSs and all (TPC LSB, ITBS ) combinations for each distinct TBS are listed in the sheet.
If a TBS can have two (TPC LSB, ITBS ) combinations, the combination with TPC LSB = 0 is selected.
RIV =18, indicates 4 localised virtual RBs (0,1,2,3) are allocated. These correspond to physical RB (0,1,2,3) in the
indicated narrow band. Resource allocation sheet ‘DCI-6-1A-RAR’ gives the transport block sizes.
RAR length is 7 bytes,1 byte header and 6 bytes Payload. Needing 1 byte for Back off indicator if included.
Tbsize of 600, allows max upto 10 RAR messages to be sent in one MAC PDU [8*7*10=560 bits]
7.3.3.8.3.2
RAR with DCI format 6-1B for CE ModeB UE
TS 36.213 [30], clause 7.1.7.2.6 Imcs=ITBS = 0..9.
Resource allocation bit is set to 0 in the indicated narrowband, indicates RBs with PRB index {0, 1, 2, 3} are allocated.
The TB sizes are given by table 7.3.3.8.3.2-1.
Table 7.3.3.8.3.2-1: Transport Block Size (TBS) table for RAR, DCI 6-1B
I TBS
0
1
2
3
4
5
6
7
8
9
TBS
88
144
176
208
256
328
392
472
536
616
RAR length is 6 bytes,1 byte header and 5 bytes Payload. Needing 1 byte for Back off indicator if included.
Max Tbsize of 616, allows max up to 11RAR messages to be sent in one MAC PDU (8*7*11=616 bits).
7.3.3.8.4
7.3.3.8.4.1
UE-dedicated scheduling
UE-dedicated scheduling with DCI format 6-1A for CE ModeA UE
TS 36.213 [30], table 7.1.7.2.3-1, ITBS = 0..15 with TBS <= Max TBS=1000 are applicable. The rules applied are same
as clause 7.3.3.4. Resource allocation sheet ‘UE-Specific-DCI-6-1A’ gives the transport block sizes.
7.3.3.8.4.2
UE-dedicated scheduling with DCI format 6-1B for CE ModeB UE
TS 36.213 [30], clause 7.1.7.2.6 Imcs=ITBS = 0..9, Modulation is always QPSK.
Resource allocation bit is set to 0 in the indicated narrowband, indicates RBs with PRB index {0, 1, 2, 3} are allocated
and 1 indicates all 6 PRB’s are allocated. If a TB size can be achieved by both nPRB=4 and 6, then the rules to select
TBS combination are same as clause 7.3.3.4. Resource allocation sheet ‘UE-Specific-DCI-6-1A’ gives the transport
block sizes.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.3.3.9
ETSI TS 136 523-3 V13.2.0 (2017-03)
132
DL Resource allocation bitmaps for BL/CE UE
7.3.3.9.1
DCI combination 1
For simplicity of scheduling, it is proposed to restrict DCI combination 1 for WB-EUTRA operation in test cases also
applicable for BL/CE UE and executed against BL/CE UE.
UE-specific below includes all other transmission C-RNTI/T-CRNTI/P-RNTI/RA-RNTI on PDSCH.
Table 7.3.3.9.1-1: Physical resource allocation bitmap
for DCI combination 1 (5 MHz)
NPRB
BCCH
SIB1-BR
SIx-BR
UE-Specific
MPDCCH/P-RNTI
MPDCCH
NOTE:
0
1
2
3
4
5
6
7
8
NB 0
NB 0
9-15
16
17
18
19-24
NB 3
Used for PBCH and
other common signals
NB 3
NB 3
NB 0
NB 1
The allocation assumes that SIB1-BR, SIx-BR and SIx are not transmitted in same subframe.
It is unavoidable to use NB 3 for both SIB1-BR and UE-specific. This means that UE-specific transmission cannot be
used in (frame number mod 2=0 in even physical layer cell Id and frame number mod 2 =1 in odd physical layer cell 1d,
subframe =4). NB 1 and 2 need to be avoided so as to avoid central 72 carriers carrying MIB and reduce interference
between intra frequency cells.
Table 7.3.3.9.1-2: Narrow band allocation per cell (5 MHz)
Physical cell ID
mod 2
SIB1-BR set
SIx-BR
UE-specific
MPDCCH
0
1
NB 0,NB 3
NB 3,NB 0
NB 0
NB 0
NB 3
NB 3
NB 1
NB 1
MPDCCH
associated
with the PRNTI
NB 0
NB 3
Table 7.3.3.9.1-3 (columns 0–30): Physical resource allocation bitmap
for DCI combination 1 (10 MHz)
NPRB
BCCH
SIB1-BR
SIx-BR
UE-Specific
MPDCCH/P-RNTI
MPDCCH
0
1
2
3
4
5
6
7-12
13-18
NB 0
NB 0
NB 1
NB 2
NB 0
NB 1
NB1
19..21
22..27
28-30
Not Used
Used for PBCH
and other
common
signals
Not Used
NB 2
NB2
Table 7.3.3.9.1-3 (columns 31–49): Physical resource allocation bitmap
for DCI combination 1 (10 MHz)
NPRB
BCCH
SIB1-BR
SIx-BR
UE-Specific
MPDCCH/P-RNTI
MPDCCH
31-36
37-42
43-48
NB 5
NB 6
NB 7
NB 5
NB 6
NB 6
NB 7
NB 7
49
Not Used
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
133
Table 7.3.3.9.1-4: Narrow band allocation per cell (10 MHz)
Physical cell ID
mod 6
0
1
2
3
4
5
NOTE:
SIB1-BR set
SIx-BR
UE-specific
MPDCCH
NB 0,NB 5
NB 1,NB 6
NB 2,NB 7
NB 5,NB 0
NB 6,NB 1
NB 7,NB 2
NB 0
NB 0
NB 0
NB 0
NB 0
NB 0
NB 6
NB 7
NB 6
NB 6
NB 7
NB 6
NB 1
NB 2
NB 1
NB 1
NB 2
NB 1
MPDCCH associated
with the P-RNTI
NB 0
NB 1
NB 2
NB 5
NB 6
NB 7
The allocation assumes SIB1-BR, SIx-BR and SIx are not transmitted in same subframe.
Table 7.3.3.9.1-5 (columns 0–43): Physical resource allocation bitmap
for DCI combination 1 (20 MHz)
NPRB
BCCH
SIB1-BR
SIx-BR
UE-Specific
MPDCCH/P-RNTI
0 1 2 3 4 5 6 7
8-13
NB 0
14-19
20-25
26-31
32-37
38-43
NB 2
NB 3
NB 4
NB 5
NB 6
NB 2
NB 3
NB 4
NB 5
NB 6
NB 1
NB 0
NB 1
Table 7.3.3.9.1-5 (columns 44-99): Physical resource allocation bitmap
for DCI combination 1 (20 MHz)
53-54
44-46
NPRB
BCCH
SIB1-BR
SIx-BR
UE-Specific
MPDCCH/P-RNTI
MPDCCH
56-61
47..52
Not
Used
Used for
PBCH and
other
common
signals
Not
Used
NB 9
NB 9
62-67
6873
64-79
NB 10 NB11 NB 12
NB 10 NB11 NB 12
80-85
86-91
92-97
98..99
NB 13
NB 13
NB 15
NB 14
NB 14
Not
Used
NB 15
NB 7
Table 7.3.3.9.1-6: Narrow band allocation per cell (20 MHz)
Physical
cell ID mod
14
0
1
2
3
4
5
6
7
8
9
10
11
12
13
SIB1-BR set
SIx-BR
UE-specific
MPDCCH
NB 0, NB 3, NB 6, NB 11
NB 1, NB 4, NB 9, NB 12
NB 2, NB 5, NB 10, NB 13
NB 3, NB 6, NB 11, NB 14
NB 4,NB 9, NB 12, NB 15
NB 5, NB 10, NB 13, NB 0
NB 6, NB 11, NB 14, NB 1
NB 9, NB 12, NB 15, NB 2
NB 10, NB13, NB 0, NB 3
NB 11, NB 14, NB 1, NB 4
NB 12, NB 15, NB 2, NB 5
NB 13, NB 0, NB 3, NB 6
NB 14, NB 1, NB 4, NB 9
NB 15, NB 2, NB 5, NB 10
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 1
NB 14
NB 14
NB 14
NB 15
NB 14
NB 14
NB 15
NB 14
NB 14
NB 15
NB 14
NB 14
NB 15
NB 14
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
NB 7
ETSI
MPDCCH
associated with
the P-RNTI
NB 0
NB 1
NB 2
NB 3
NB 4
NB 5
NB 6
NB 9
NB 10
NB 11
NB 12
NB 13
NB 14
NB 15
3GPP TS 36.523-3 version 13.2.0 Release 13
7.4
Cell Configurations
7.4.1
Cell Configuration Types
134
ETSI TS 136 523-3 V13.2.0 (2017-03)
Three cell configurations are defined in TS 36.508 [3] clause 6.3.3: Full Cell, Minimum Uplink Cell and Broadcast
Only Cell; however the TTCN always considers all cells as Full Cells, and thus always provides the complete cell
configuration parameters.
The SS may:
-
always configure a cell as a 'Full Cell' based on the complete information; or
-
configure the cell based on the 'CellConfig_Type' flag taking only the required configuration parameters and
ignoring the others.
For a given value of the 'CellConfig_Type' flag, the TTCN shall:
-
For Full Cell Configuration:
-
-
-
expect normal SS behaviour.
For Minimum Uplink Cell Configuration:
-
Configure the SS to report Preamble detection.
-
Assign verdicts based on the PRACH Preamble Indications.
-
Consume any uplink SRB0 messages (if the SS is configured as a Full Cell).
For Broadcast Only Cell Configuration:
-
Not configure the SS to report Preamble detection.
-
Consume any uplink SRB0 messages (if the SS is configured as a Full Cell).
7.4.2
Cell Power Change
To set and adjust the cell power at the two test ports, Reference Power and Attenuation, are provided in the record
Reference Power.
The field Reference Power is only set when the cell is created and is not updated during the test case execution. The SS
applies the Reference Power when the cell is fully configured.
To adjust the power level in the test case, the field Attenuation is used. After initial configuration of a cell the
attenuation corresponds to the value "off". When the power is changed for more than one cell, the power changes must
happen at the same time for all the cells according to the time instances for power level changes specified in
TS 36.523-1 [1]. The time it takes to complete the power change for all the cells shall be done:
-
within a maximum of 700 ms when changing the power of a cell from "off" to a certain value; or
-
within a maximum of 100 ms (10 frames) otherwise.
The SS shall ensure the power level at the test ports conform to the required downlink signal levels specified in
clause 6.2.2.1 of TS 36.508 [3].
7.4.3
7.4.3.1
E-UTRAN cell identity
Timing parameters of cells
For RRC and Idle mode test, the timing parameters in table 7.4.3.1-1 are applied. The specification of Cell 1 - Cell 30
can be found in TS 36.508 [3].
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
135
Table 7.4.3.1-1: Timing parameters of simulated cells
cell ID
Cell 1
Cell 2
Cell 3
Cell 4
Cell 6
Cell 10
Cell 11
Cell 12
Cell 13
Cell 14
Cell 23
Cell 28
Cell 29
Cell 30
NOTE:
SFN offset
FDD Tcell
TDD Tcell (Ts)
(Ts)
Synchronous
Non synchronous
0
0
0
0
124
30720
154
30720
257
150897
77
150897
1000
61440
307
61440
657
524
77
524
129
43658
77
43658
957
92160
154
92160
1015
181617
154
181617
890
31244
154
31244
680
300501
77
300501
383
212337
154
212337
890
31244
154
31244
680
300501
77
300501
1015
181617
154
181617
For TDD, synchronous Tcell values are applied unless specified otherwise in the
test cases.
Table 7.4.3.1-2 is applied to the NAS test when more than one PLMN exists in a test case. Further cell parameters can
be found in TS 36.508 [3], table 6.3.2.2-3.
Table 7.4.3.1-2: Timing parameters of simulated cells for NAS TCs in different PLMNs
cell ID
Cell A
Cell B
Cell C
Cell D
Cell E
Cell F
Cell G
Cell H
Cell I
Cell J
Cell K
Cell L
Cell M
NOTE:
SFN
FDD Tcell
TDD Tcell (Ts)
offset
(Ts)
Synchronous
Non synchronous
0
0
0
0
124
30720
154
30720
257
61440
307
61440
1000
92160
154
92160
752
32047
77
32047
NA
NA
NA
NA
957
631
77
631
1015
31351
154
31351
890
127200
77
127200
680
1327
77
1327
383
157920
154
157920
562
188640
307
188640
471
122880
307
122880
For TDD, synchronous Tcell values are applied unless specified otherwise in
the test cases.
Figure 7.4.3.1-3 illustrates shifting DL transmission timing offset by Tcell = 1 subframe, between multiple NAS FDD
cells on the same frequency (table 7.4.3.1-4) in the same PLMN.
1 subframe
time
Cell A
Cell B
Cell C
P-SS
Cell D
S-SS
PBCH
Cell M
Figure 7.4.3.1-3: Timing offset between FDD cells on the same frequency
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
136
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 7.4.3.1-4 is applied to the NAS test when all NAS cells in a test case belong to the same PLMN. Further cell
parameters can be found in TS 36.508 [3], table 6.3.2.2-2.
Table 7.4.3.1-4: Timing parameters of simulated cells for NAS TCs in same PLMN
cell ID
Cell A
Cell B
Cell C
Cell D
Cell E
Cell F
Cell G
Cell H
Cell I
Cell J
Cell K
Cell L
Cell M
NOTE:
SFN offset
FDD Tcell (Ts)
TDD Tcell (Ts)
Synchronous
Non synchronous
0
0
0
0
124
30720
154
30720
257
150897
77
150897
1000
61440
307
61440
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
471
31244
154
31244
For TDD, synchronous Tcell values are applied unless specified otherwise in the test
cases.
Shifting radio frame transmission timing can eliminate the following interference between intra frequency cells:
-
P-SS/S-SS to P-SS/S-SS, RS, PBCH, PCFICH, PDCCH and PHICH.
-
PBCH to PBCH.
-
PBCH to PCFICH, PDCCH and PHICH.
-
PDSCH to PCFICH, PDCCH, PHICH.
As TDD UL and DL are on same frequency, to avoid interference between DL and UL, the Random Access Response
Timing Advance (RAR TA) is related to the Tcell:
For TDD cells:
RAR TA = [FLOOR ((Tcell) mod 30720 / 16) ] mod 1282
For FDD, the Random Access Response Timing Advance is set to 0.
In MBMS test cases, cells belonging to the same MBSFN Area have a synchronized radio frame timing: the SFN offset
and Tcell values are set to the values of the cell having the lower cellId value.
In Carrier Aggregation signalling test cases, the SFN offset and Tcell of configured cells has to be same.
Editor's note: More clarification in terms of tables representing configured cells may be needed. Cell 1, Cell 2, Cell3,
Cell12 & Cell 6 are configured in CA test cases.
The HFSN Offset shall be set to 0 for all cells.
7.4.4
Cell configurations for NAS test cases
The default cell identifiers for NAS cells are defined in 36.508 [3] clause 6.3.2.2.
The allocation of Physical layer cell identifiers to the individual cells is according to (PCI mode 6) being differential for
the cells working on the same radio frequency. The way of PCI allocation can reduce the interference between the intrafrequency cells for reference signal to reference signal, PCFICH to PCFICH and PHICH to PHICH. The definition of
Cell A - Cell M can be found in TS 36.508 [3].
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.4.5
137
ETSI TS 136 523-3 V13.2.0 (2017-03)
Configuration of Multi-Cell Environment
When there is more than one EUTRA cell in a test case the following rules are applied in TTCN:
-
At the beginning of the preamble, before initial attachment of the UE, all EUTRA cells are configured but
switched off.
-
In the preamble only the serving cell is switched on; all other cells remain switched off.
-
At the end of the preamble the cells are configured according to the initial power level settings (T0) of the test
case.
The mapping of cells to physical resources and management of the physical resources are out of TTCN scope. The
following principles can be applied to the system simulator:
-
Cells being switched off need not to be mapped to physical resources.
-
When a cell is switched off mapping to a physical resource may be kept and reused when the cell is switched on
again.
-
When a cell is switched on it can either already been mapped to a physical resource or it needs to be mapped to a
free resource.
-
When there are less physical resources than cells it is up to SS implementation to find strategies to dynamically
map the cells to the resources.
Independent from the strategies being used the system simulator shall obey timing restrictions for changing powerlevels of one or several cells as stated in clause 7.4.2.
7.5
TDD Considerations
LTE options of FDD and TDD will be contained in the same common FDD and TDD test cases, similar to the prose in
TS 36.523-1 [1].
The TDD Uplink-downlink configuration 1 in 3GPP TS 36.211 [35], table 4.2-2 is applied.
7.5.1
FDD vs. TDD implementation
FDD/TDD differences are introduced in the common FDD and TDD test cases using branches at a low level in the test
case. The branches are used either:
-
to assign a variable;
-
to implement a different behaviour;
-
to change an FDD or TDD parameter in a template sent to the UE or SS.
The mode under test (FDD or TDD) is based on the value of the bands under test.
7.5.2
Guideline for FDD vs. TDD verification
With respect to EUTRA FDD vs. TDD technologies, it is recommended that separate verifications for FDD and TDD
are required for the TCs in TS 36.523-1 [1]:
-
clause 6, 7, 8, 12, 13;
-
with MultiRAT involved.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
138
7.6
Special RLC Modes
7.6.1
Suppression of RLC Acknowledgements
ETSI TS 136 523-3 V13.2.0 (2017-03)
Two different modes, both applicable per radio bearer, are defined as:
-
General suppression:
-
-
If this mode is activated, no RLC acknowledgements will be generated by the SS. This mode can be switched
on and will persist until it is switched off. Afterwards the SS will continue handling the RLC
acknowledgements as normal.
One time suppression:
-
If this mode is activated, no RLC acknowledgement will be generated by SS for the next RLC message data
PDU received. Once this has been done, the SS continues handling RLC acknowledgements as normal.
In case of a handover the modes continue to be active.
7.6.2
Modification of VT(S)
This mode allows to manipulate the RLC state variable VT(S) so that the SS can generate an RLC sequence number as
needed during a test. The input to the special test mode is an integer (0..1023) as value of ModifyVTS, The SS shall set
variable VT(S) as follows:
VT(S):= ModifyVTS.
The purpose of this special test mode is to force an incorrect RLC sequence number to be used by the SS. Once VT(S)
has been modified in the RLC entity at the SS side, this RLC entity will be inconsistent. One possibility to bring the
RLC entity back to normal is to re-establish the RLC peer connection. This is done in the only use case of this special
RLC test mode by performing an RRC Connection reconfiguration immediately after the test mode has been applied.
Users of this test mode should ensure that the RLC AM PDU carrying the incorrect sequence number will reach the
peer RLC entity. It is therefore recommended to activate the RRC Connection reconfiguration only after some delay.
This delay shall be short enough to ensure that the UE will not yet request the retransmission of the RLC PDU
corresponding to the skipped sequence numbers.
7.7
System information
7.7.1
System information broadcasting
The rules for the transmission of BCCH messages are specified in TS 36.331 [19], clause 5.2. The current clause
provides the implementation guidelines.
The ASPs SYSTEM_CTRL_REQ and SYSTEM_CTRL_CNF are used as interface to SS; the following rules apply:
-
The complete system information is provided to SS by using a single ASP.
-
SS starts scheduling all system information from the same SFN.
-
The scheduling information sent to SS is the same as the scheduling information sent to the UE. For each SI
message, the subframeOffset in SYSTEM_CTRL_REQ indicates the exact point in time in the SI window at
which SS shall start the transmission of the related SI.
-
SS shall set the systemFrameNumber in the MIB to the 8 most significant bits of the SFN. A dummy value is
provided by TTCN.
-
If the HFSN value is included in SIB1 sent from the TTCN, the SS shall set the hyperSFN in this message to the
current HSFN. In this case, a dummy value is provided by TTCN.
-
If the HFSN is not included in the SIB1 sent from the TTCN, it shall not be added by the SS.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
139
-
The system information is sent to SS using the asn.1 types, SS shall encode in unaligned PER and add the
necessary padding bits as specified in TS 36.331 [19], clause 9.1.1.1.
-
In the E-UTRAN-CDMA2000 Inter RAT configuration, SS shall set the CDMA2000 synchronousSystemTime
in SystemInformationBlockType8 to the SFN boundary at or after the ending boundary of the SI-window in
which SystemInformationBlockType8 is transmitted (see TS 36.331 [19], clause 6.3.4). The changes of
synchronousSystemTime will not result in system information change notification, nor in a modification of
systemInfoValueTag in SIB1 in TTCN as specified in TS 36.331 [19], clause 6.3.1. If 1xRTT is being tested,
then SS shall overwrite the longCodeState1XRTT in SystemInformationBlockType8 to the state of long code
generation registers in CDMA2000 1xRTT system as defined in C.S0002-A [12, Section 1.3] at
⎡t / 10⎤ × 10 + 320 ms, where t equals to the cdma-SystemTime. The changes of longCodeState1XRTT will not
result in system information change notification, nor in a modification of systemInfoValueTag in SIB1 in TTCN
as specified in TS 36.331 [19], clause 6.3.1.
7.7.2
Scheduling information
The maximum number of resource blocks as defined in table 7.7.2-1 are used to broadcast the system information.
Table 7.7.2-1: Maximum number of resource blocks
Maximum number of resource blocks assigned
4
4
SIB1
for all SIs
The subframe offset values used for SI messages are according to table 7.7.2-2.
Table 7.7.2-2: SubframeOffset values
Scheduling Information No.
Acc to TS 36.508 [3], clause 4.4.3.1.2
SI1
SI2
SI3
SI4
SI5
subframeOffset (FDD)
subframeOffset (TDD)
1
1
3
7
7
0
0
15
15
15
All System Information messages are sent only once within the SI-window.
Table 7.7.2-3 (FDD) and 7.7.2-4(TDD) give the SFN's and subframe numbers in which the MIB, SI1, SI2, SI3, SI4 &
SI5 are actually scheduled as per default parameters for si-WindowLength(20sf), periodicity for SI1(16), SI2(32),
SI3(64) , SI4(64) and SI5(64) for bandwidths 5/10/15/20 MHz defined in TS 36.508 [3]:
Table 7.7.2-3: System Information Scheduling (FDD)
SFN\SUBFrame
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
SI1
2
3
4
SI2
5
SIB1
6
7
SIB1
SI3
SIB1
SIB1
SI4
SIB1
SI5
SIB1
SIB1
SIB1
ETSI
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
SFN\SUBFrame
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
0
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
SI1
2
ETSI TS 136 523-3 V13.2.0 (2017-03)
140
3
4
5
SIB1
6
7
8
9
8
9
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SI1
SIB1
SI2
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SI1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SI1
SIB1
SI2
SIB1
SI3
SIB1
SIB1
SI4
SIB1
SI5
Table 7.7.2-4: System Information Scheduling (TDD)
SFN\SUBFrame
0
1
0
MIB, SI1
MIB
1
2
3
4
ETSI
5
SIB1
6
7
3GPP TS 36.523-3 version 13.2.0 Release 13
SFN\SUBFrame
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
0
MIB, SI2
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB, SI1
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB, SI1
MIB
MIB, SI2
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB, SI1
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB, SI1
MIB
1
2
ETSI TS 136 523-3 V13.2.0 (2017-03)
141
3
4
5
SIB1
SIB1
SI3
SIB1
SI4
SIB1
SI5
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
ETSI
6
7
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
SFN\SUBFrame
66
67
68
69
70
71
72
73
0
MIB, SI2
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
2
ETSI TS 136 523-3 V13.2.0 (2017-03)
142
3
4
5
SIB1
6
7
8
9
SIB1
SI3
SIB1
SI4
SIB1
SI5
NOTE: Subframes 4 and 9 are avoided so as to facilitate availability of PDCCHs in the UE specific search space for
transmission of PDCCH for both UL C-RNTI/SPS-RNTI and DL C-RNTI/SPS-RNTI/Temp C-RNTI.
7.7.2a
Scheduling information for BR System information
The scheduling of BR System Information is based upon the following conditions (Ref: 36.211 [44] clause 6.4.1):
-
SIB1- BR
N PDSCH
=4 i.e. the schedulingInfoSIB1-BR-r13 values are selected from {1,4,7,10,13,16} which as per
36.213[30] table 7.1.6-1 would result in 4 repetitions.
-
si-WindowLength-BR-r13 =20 ms (same value as si-WindowLength)
-
si-RepetitionPattern-r13 = every2ndRF (hence results eventually in only transmission in first frame of window)
-
Except for SIB1-BR (mandated for SIB1-BR by 36.211) hopping is assumed to be not enabled for anything else.
-
The current test plan excludes inter frequency and inter rat test cases due to limitations in RAN4. Inter
frequency, inter RAT system information combinations are not considered.
-
The typical size of SIB1/2/3/4 is less than 700 bits, the Max TB size for SIx-BR is 936 bits, 36.213 [30] table
7.1.7.2.7-1, hence no segmentation is assumed. For SIB1-BR schedulingInfoSIB1-BR-r13 =10, and for SIB 2,3,4
the si-TBS-r13 is set as b712.
-
If MIB needs to be repeated as per 36.331[19] clause 5.2.1.2 in subframe#9 of the previous radio frame for FDD
and sub frame #5 of the same radio frame for TDD, the same can be achieved in the below schedule.
The sub frame offset values used for SI messages are according to table 7.7.2a-1.
Table 7.7.2a-1: SubframeOffset values
Scheduling Information No.
subframeOffset (FDD)
subframeOffset (TDD)
Acc to TS 36.508 [3], clause 4.4.3.1.2
SI1
1
0
SI2
1
0
SI3
3
0
SI4
3
0
SI1-BR
2
4
SI2-BR
2
4
SI3-BR
2
4
SI4-BR
2
4
NOTE:
The subframe offsets for SIx-BR of 4 is suitable only for default TDD uplink-downlink
configuration =1 and additionally for 2, 4 & 6.
The following tables give the SFN and subframe numbers in which MIB, SIs and SI-BRs are actually scheduled as per
default parameters defined in TS 36.508 [3] for:
Table 7.7.2a-3 for FDD with even physical layer cell IDs
Table 7.7.2a.5 for FDD with odd physical layer cell IDs
Table 7.7.2-4 for TDD for DL bandwidth <=5Mhz
Table 7.7.2a.6 for TDD for DL bandwidth > 5Mhz and odd physical layer cell Id.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
143
Table 7.7.2a-2: BR System Information Scheduling (FDD) for even physical layer cell
N cell mod 2
=0]
IDs[ ID
SFN\SUBFrame
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
0
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
SI1
2
SI1-BR
SI2
SI2-BR
SI1
3
4
SIB1-BR
5
SIB1
SIB1-BR
SIB1
SI3-BR
SI3
SIB1-BR
SIB1
SI4-BR
SI4
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SI1-BR
SI1
SI1-BR
SIB1-BR
SIB1
SI2
SI2-BR
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SI1
SI1-BR
ETSI
6
7
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
SFN\SUBFrame
61
62
63
64
65
66
67
68
69
70
71
72
0
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
2
ETSI TS 136 523-3 V13.2.0 (2017-03)
144
3
4
5
SIB1-BR
SIB1
SI1
SI1-BR
SIB1-BR
SIB1
SI2
SI2-BR
SIB1-BR
SIB1
SI3-BR
SI3
SIB1-BR
SIB1
SI4-BR
SI4
SIB1-BR
SIB1
SIB1-BR
SIB1
ETSI
6
7
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
145
DL
Table 7.7.2a-3: BR System Information Scheduling (TDD) for DL bandwidth<=5Mhz [ N RB
≤ 15 ]and for
DL
> 15 ] and even physical layer cell Id [
DL bandwidth > 5Mhz [ N RB
SFN\SUBFrame
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
0
MIB, SI1
MIB
MIB, SI2
MIB
MIB/SI3
MIB
MIB, SI4
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB, SI1
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB, SI1
MIB
MIB, SI2
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB, SI1
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
2
3
4
SI1-BR
SI2-BR
SI3-BR
SI4-BR
SI1-BR
SI1-BR
SI2-BR
SI1-BR
ETSI
5
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
6
cell
N ID
mod 2
7
=0]
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
SFN\SUBFrame
60
61
62
63
64
65
66
67
68
69
70
71
72
73
0
MIB
MIB
MIB
MIB
MIB, SI1
MIB
MIB, SI2
MIB
MIB, SI3
MIB
MIB, SI4
MIB
MIB
MIB
1
2
ETSI TS 136 523-3 V13.2.0 (2017-03)
146
3
4
SI1-BR
SI2-BR
SI3-BR
SI4-BR
ETSI
5
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
6
7
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
147
Table 7.7.2a-4: BR System Information Scheduling (FDD) for odd physical layer cell IDs[
SFN\SUBFrame
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
0
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
SI1
2
SI1-BR
SI2
SI2-BR
3
4
5
SIB1
SIB1-BR
SIB1
SIB1-BR
SI3-BR
SI3
SIB1
SIB1-BR
SI4-BR
SI4
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SI1
SI1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SI1
SI1-BR
SIB1
SIB1-BR
SI2
SI2-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SI1
SI1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
SIB1
SIB1-BR
ETSI
6
7
8
cell
N ID
mod 2
9
=1]
3GPP TS 36.523-3 version 13.2.0 Release 13
SFN\SUBFrame
62
63
64
65
66
67
68
69
70
71
72
0
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
MIB
1
2
SI1
SI1-BR
ETSI TS 136 523-3 V13.2.0 (2017-03)
148
3
4
5
SIB1
SIB1-BR
SIB1
SIB1-BR
SI2
SI2-BR
SIB1
SIB1-BR
SI3-BR
SI3
SIB1
SIB1-BR
SI4-BR
SI4
SIB1
SIB1-BR
SIB1
ETSI
6
7
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
149
DL
Table 7.7.2a-5: BR System Information Scheduling (TDD) for DL bandwidth > 5Mhz [ N RB
> 15 ] and
odd physical layer cell Id [
SFN\SUBFrame
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
0
MIB, SI1
MIB, SIB1-BR
MIB, SI2
MIB, SIB1-BR
MIB/SI3
MIB, SIB1-BR
MIB, SI4
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB, SI1
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB, SI1
MIB, SIB1-BR
MIB, SI2
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB, SI1
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
1
2
3
cell
N ID
mod 2
4
SI1-BR
5
SIB1
SI2-BR
SIB1
SI3-BR
SIB1
SI4-BR
SIB1
SIB1
SIB1
SIB1
SIB1
SI1-BR
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SI1-BR
SIB1
SI2-BR
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
SI1-BR
SIB1
SIB1
SIB1
SIB1
SIB1
SIB1
ETSI
=1]
6
7
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
SFN\SUBFrame
60
61
62
63
64
65
66
67
68
69
70
71
72
73
7.7.3
0
MIB
MIB, SIB1-BR
MIB
MIB, SIB1-BR
MIB, SI1
MIB, SIB1-BR
MIB, SI2
MIB, SIB1-BR
MIB, SI3
MIB, SIB1-BR
MIB, SI4
MIB, SIB1-BR
MIB
MIB, SIB1-BR
1
ETSI TS 136 523-3 V13.2.0 (2017-03)
150
2
3
4
5
SIB1
6
7
8
9
SIB1
SI1-BR
SIB1
SI2-BR
SIB1
SI3-BR
SIB1
SI4-BR
SIB1
SIB1
System information modification
For system information modification, the same rules as defined in clause 7.7.1 are applied.
The SFN and the HSFN for the start of modification period are calculated by TTCN. The modified system information
and the calculated SFN, HSFN are provided in the ASP SYSTEM_CTRL_REQ.
7.7.3.1
Non-PWS System Information modification
The modification of system information is notified by paging messages containing the systemInfoModification (normal
DRX) or systemInfoModification-eDRX (extended DRX). The paging messages are sent during one modification period
before broadcasting the modified system information for normal DRX, and within a Paging Time Window (PTW) for
extended DRX. The paging messages are sent on paging occasions (PO) within the paging frames (PF). With the default
paging and sysinfo parameters provided in TS 36.508 [3] PO is set to 9 for FDD and 0 for TDD.
In case the UE is configured by the SS with an extended DRX cycle and the cell indicates support for eDRX in System
Information, eDRX is performed. See to TS 36.304 [14], clause 7.3
7.7.3.1.1
7.7.3.1.1.1
UE in Idle_mode
Paging in DRX when P-RNTI transmitted on PDCCH
In the case of normal DRX, the paging frames calculation is based on the UE identity (see to TS 36.304 [14], clause 7).
With:
defaultPagingCycle=128
nB=oneT
modificationPeriodCoeff=n4
it results in 4 paging messages to be sent on the paging occasions during the modification period in the frames of:
SFN mod 128 = (UE_ID) mod 128.
7.7.3.1.1.2
Paging in extended DRX
In the case of eDRX, the DRX cycle is longer than the modification period and the parameter is the Paging Hyperframe
(PH) and refers to the hyper SFN (H-SFN) in which the UE starts monitoring POs during a Paging Time Window
(PTW). The H-SFN is broadcasted by the cell and increments by one when the SFN wraps around. When a change
notification is received, the UE acquires the updated system information at the next H-SFN boundary defined by:
H-SFN mod 256 = 0
If the UE is configured with a TeDRX cycle of 512 radio frames, it monitors POs as defined on normal DRX with
parameter T = 512, otherwise it will monitor POs calculated as normal DRX only (as per clause 7.7.3.1.1.1 or
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
151
ETSI TS 136 523-3 V13.2.0 (2017-03)
7.7.3.1.1.3) within the periodic PTW configured for the UE. The calculation of the bounds for the PTW are UE-specific
and described on TS 36.304 [14] clause 7.3.
Figure 7.7.3.1.1-1: Paging cycles in eDRX idle mode
7.7.3.1.1.3
Paging in DRX when P-RNTI transmitted on MPDCCH
BL/CE UEs can be notified using Direct Indication information or paging message.
For BL/CE UEs, the paging frames calculation is based on the UE identity (see to TS 36.304 [14], clause 7.1). With:
defaultPagingCycle=128
nB=oneT
modificationPeriodCoeff=n4
number of paging narrowbands=1
SystemInformationBlockType1-BR modification period = 512 frames
SIs-BR modification period = 512 frames
The paging occasion calculation is resulting in the frames of: SFN mod 128 = (UE_ID) mod 128. The Paging
Narrowband (PNB) is resulting in PNB=0 and then resulting in the Narrow Band used for MPDCCH defined in clause
7.3.3.9.1.
One paging message is sent on the calculated paging occasion before the start of SystemInformationBlockType1-BR
modification period. When both SystemInformationBlockType1-BR and SIs-BR are modified, their respective
modification period starts may not match:
-
When they match, SS is configured with the modified SystemInformationBlockType1-BR and SIs-BR in one
ASP
-
When they do not match, SS is configured with the modified SystemInformationBlockType1-BR and SIs-BR in
two different ASPs with activation time set to the start of the respective modification periods.
7.7.3.1.2
UE in connected mode
When the UE is in connected mode, paging messages are sent on the paging occasions of each frame within the paging
cycle throughout a modification period. This results in 128*4 consecutive paging messages to be sent during the
modification period.
BCCH modification period (n+1)
BCCH modification period (n)
Updated information
Paging cycle
Paging notification
Figure 7.7.3.1.2-1: Paging notification UE in connected mode
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
152
For ETWS and/or CMAS capable UEs in connected mode, paging messages are sent on the paging occasions of each
frame within the last paging cycle of the modification period. This results in 128 consecutive paging messages to be
sent during the modification period.
BCCH modification period (n+1)
BCCH modification period (n)
Updated information
Paging cycle
Paging notification
Figure 7.7.3.1.2-2: Paging notification for ETWS and/or CMAS capable UE in connected mode
7.7.3.2
PWS System Information modification
The modification of system information for ETWS and CMAS notification is notified by paging messages. The
transmission of system information notification is not necessarily at the beginning of a modification period.
When the UE is in idle mode, the paging frames calculation is the same as defined in clause 7.7.3.1.1.
When the UE is in connected mode, paging messages are sent on the paging occasions of each frame during a paging
cycle. This results in 128 consecutive paging messages to be sent. The transmission of the first paging message and the
first system information notification are simultaneous and are sent at the beginning of a paging cycle.
7.8
Timers and Timing Restrictions
A timer is set at the beginning of each test case to guard against system failure. Behaviour on expiry of this guard timer
shall be consistent for all test cases.
A watchdog timer can be specified for receive statements in order to reduce blocking time when a test case has already
failed. Watchdog timers are a kind of TTCN auxiliary timer. When a watchdog timer is used to control a receive event,
its expiry does not need to be handled explicitly in the test case, but will lead to a fail or inconclusive verdict due to
handling in the default behaviour.
In idle mode operations, an idle mode generic timer is specified for receive statements if the test case specification does
not explicitly specify a wait time for the specific test step or test purpose. The expiry of this idle mode generic timer is
at least 6 minutes to safely cover most test scenarios.
The watchdog timer and the idle mode generic timer are only to be used inside the test case test body; if the timer
expires a fail verdict is applied.
It is the TTCN responsibility to ensure that appropriate timer values are being used.
Tolerances (as described in TS 36.508 [3]) are not applicable to guard timers, idle mode generic timers and watchdog
timers.
In general timers of less than 500 ms shall not be implemented by TTCN timers but controlled by usage of the timing
information provided by the SS (This is based on an estimate of the system delay). To achieve this, there will be cases
when a DL message is scheduled at a specific point in time. This shall be done by adding at least 100 ms to the current
time.
If Timing is ‘now' the SS shall schedule the data transmission or the (re)configuration in the next available sub-frame,
but will ensure that this period is less than 80 ms.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.8.1
153
ETSI TS 136 523-3 V13.2.0 (2017-03)
Auxiliary timers
For practical reasons, the TTCN can include timers that are not specified as part of the expected sequence. These timers
are documented below.
RLC and PDCP watchdog timer.
7.8.2
RRC timers reconfiguration
Considering the allowed UE accuracy for the RRC timer T3xx being between 100 ms and 2.5 % of T3xx (see
TS 36.133 [37]), the TTCN applies the RRC net timers tolerance as MAX (10% of T3xx, (100 ms + 5 RTT)), whereby:
FDD: 10 % of T3xx or 140 ms whichever is higher.
TDD: 10 % of T3xx or 155 ms whichever is higher.
7.8.3
MAC TA timer reconfiguration
Considering that the UE applies new values for MAC timers not before restart of the timer (see TS 36.321 [16],
clause 5.8), when the TA timer is changed at the UE, a delay in TTCN will be added so as to allow SS to transmit
Timing advance MCE (based on current periodic Timing advance configuration) and hence resulting in restart of TA
timer at UE with new value.
7.8.4
Non-protocol timers
Time durations or periods in the test specification without corresponding references in the core specifications are
considered as non-protocol timers for which no timer tolerances are applied in the TTCN.
7.9
Error Indication
There are several situations on lower layer in which SS shall raise an error rather than trying to resolve the problem.
This is done by sending a SystemIndicationError to the test case. SS shall raise an error in the following cases:
-
HARQ retransmissions (applicable when SS is configured to indicate HARQ retransmissions as errors):
-
HARQ CRC error for UL data;
-
HARQ NACK from the UE unless SS is configured to report HARQ ACK/NACK.
-
Paging, System information exceeds max. number of resource blocks.
-
Configuration: max. number of resource blocks specified for a channel exceeds system bandwidth.
-
When in User-Plane a DL PDCP PDU or SDU not fitting into one TTI is sent with Harq Process being explicitly
specified.
-
SS gets invalid TimingInfo for TDD from the test case.
-
SS detects contradiction of UL grant(s) and TDD configuration.
-
Data scheduled for the same TTI does not fit into an available transport block.
Further error conditions are specified in annex D.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.10
154
ETSI TS 136 523-3 V13.2.0 (2017-03)
Race Conditions
When two uplink messages are sent from the UE within a very small amount of time, they may be received in either
order in the TTCN if they are received on different ports. This may cause a race condition which is due to the snapshot
mechanism in TTCN. In these cases, the TTCN will accept the messages in either order and then compare the
timestamps of both messages to ensure they were sent in the correct order.
For UL messages received at a single port, there are normally no race conditions, with the exception of the SRB port
where the following rules shall be fulfilled, in order to achieve an ordered UL message queue:
-
UL messages are queued according to the timing information.
-
UL messages with the same timing information are queued according to the logical channel priority with the
"higher-first-in" principle.
7.11
Radio Link Failure
A radio link failure shall be triggered by switching the downlink power level of the source cell to the value for
non-suitable "Off" for the time period of least T310 + time it takes to receive N310 consecutive out-of-sync indications
from lower layers (non-suitable "Off" is defined in TS 36.508 [3], whereas T310 and N310 are defined in
TS 36.331 [19]).
If the RRC re-establishment procedure is used in a radio link failure context, it shall be realised by using two cells.
7.12
Test method for RRC signalling latency
Test cases testing RRC signalling latency will need special test method. The PUCCH synchronisation state of UE
influences the test method. Following 2 different ways in which the UE's completeness of procedure can be probed are
considered:
1. UE is still PUCCH synchronized and can respond to uplink grants.
2. UE needs a RACH procedure and hence RACH procedural delays add upon the actual procedure delay.
7.12.1
Procedure delays in PUCCH synchronized state
For latency tests there may be up to 4 HARQ retransmissions in DL (corresponding to the default configuration of the
SS) but HARQ retransmissions in UL cannot be compensated , i.e. any HARQ error in UL shall result in an
inconclusive verdict for the test case (otherwise a UE may get fail due to a HARQ error).
Figure 7.12.1-1 demonstrates the latency check procedure that will be applied when UE is in PUCCH synchronized
state and can respond to uplink grants.
SS is configured to report ACK/NACK received from UE, to TTCN.
NOTE:
Due to L2 signalling (e.g. RLC STATUS PDUs) it is necessary to limit the reporting of UL HARQ
ACK/NACK to the time between sending of the RRC message and receiving the ACK.
By default SS is configured to retransmit any DL MAC PDU max 4 times.
To avoid unexpected side effects the Time Alignment timer needs to be set to infinity and the SS shall be configured
to not send any Timing Advance MAC control elements during the latency tests (since this may result in additional
ACK/NACK)
The SS shall be configured to report HARQ errors and in the case of an UL HARQ error, an inconclusive verdict is
assigned.
In the case of HARQ retransmissions in DL the HARQ RTT Timer according to TS 36.321 clause 7.7 [16] is
-
8 for FDD
-
10 for TDD configuration 1 in case the DL PDU is sent in subframe 4 (as per default; see Table 7.12.1-1).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
155
The SS shall schedule DL retransmission at 4th TTI for FDD and TDD since reception of the NACK.
Let N be the max allowed delay for procedure.
TTCN schedules at time T1 a DL message to the UE.
TTCN schedules UL grants at
T2(k) = T1 + N + 1 + ∆1 + k * RTT;
with
k = 0..4; number of HARQ retransmission in DL
RTT = 8 (FDD)
RTT = 10 (TDD)
∆1 = 0 (FDD)
∆1 = 0..3 (TDD; possible UL subframe uncertainty since not all subframes can be used for UL)
Example:
given TDD; DL PDU sent at subframe 4; N=10
∆1 = 1 since UL grant cannot be scheduled for subframe 5 but needs subframe 6 (36.213 [30] cl.8.0)
⇒
The UL data is sent by the UE at
T3(K) = T2(K) + 4 + ∆2 with ∆2 = 0 for FDD and ∆2 = 0..3 for TDD and K is the value of k corresponding to
which a HARQ Ack is received
The latency requirements are fulfilled when
T3(K) - T1 = N + 5 + ∆1 + ∆2 + K * RTT
Looking at TDD configuration 1 in detail it can be shown that ∆ = ∆1 + ∆2 = 0 .. 3
⇒ T (K) - T
3
1
= N + 5 + ∆ + k * RTT; with ∆ = 0 .. 3
NOTE:
as long as N is a multiple of 5ms, given T1 is at 4th TTI for TDD configuration 1 we get ∆ = 3 (∆1 = 1 and ∆2
= 2, 36.213 [30] cl.8.0)
Delay Requirement
Y-X<= N+?
Time = T1
DL Msg Tx
DL Msg
Re-Tx
UL GRANTS
UL MAC Padding
PDU’s
NACK
Time =Y
UL Msg Rx
Time =X
ACK
Figure 7.12.1-1: Delays in PUCCH synchronized state
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
156
Table 7.12.1-1: TDD configuration 1
Subframe
Configuration 1
Delay from DL to Ack/Nack [TTIs]
Delay from NCK to re tx [TTIs]
RTT
7.12.2
0
D
1
S
11
10
2
U
6,7
4
3
U
4
6
4
D
5
D
6
S
10
11
10
7
U
6,7
4
8
U
4
6
9
D
10
Procedure delays when RACH procedure required
Figure 7.12.2-1 demonstrates the latency check procedure that will be applied when UE is not PUCCH synchronized
state needs RACH procedure.
PRACH configuration index is set as 14 for FDD, 12 for TDD which allows UE to send Preamble in any frame at
any subframe.
SS is configured to report ACK/NACK, PRACH preambles received from UE.
By default SS is configured to retransmit any DL MAC PDU max 4 times [1 Transmission and 4 Retransmission].
Let N be the max allowed delay for procedure.
TTCN schedules at time T1, DL message to the UE. This is achieved using Time stamps in send ASP's.
The time difference between the ACK and the reception of PRACH preamble will be checked against N plus any
Interruption time (TS 36.133 [37]) and verdict is assigned, when (Y-X) <= N + Tinterrupt + ∆:
∆ = 0 for FDD;
∆ = 3TTI for TDD, where 3TTI is UL subframe uncertainty.
If cell change occurs, cell timing differences, Frame number offsets need to be included for procedural delay
evaluations.
Delay Requirement
Y-X<= N + Tinterrupt+ ?
Time = T1
DL Msg Tx
DL Msg
Re-Tx
NACK
RAR
Time =Y
PRACH Preamble
Time =X
ACK
Cont. Resolution
UL MSG Rx
Figure 7.12.2-1: Delays when RACH procedure needed
7.13
RLC test method for scheduled data
The test loop mode is applied to the RLC tests. The allowed SS delay for sending data (< 80 ms) is comparable to the
default values of the RLC timers. In order to ensure a unique TTCN implementation of the RLC test cases and the
deterministic test result, independent from the SS platforms and UEs, scheduled data method can be applied to the test.
The scheduled data method is suitable to the RLC test if:
Receiving multiple UL RLC SDUs is expected in the test; the UE may send a STATUS PDU in addition.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
157
Time measurement is required for the looped back RLC SDUs.
DL RLC PDUs are sent on consecutive TTIs; the subframe numbers to be applied are relevant in TDD.
Table 7.13-1 illustrates the data scheduling in the RLC test.
Table 7.13-1: Scheduled RLC test events
Scheduled timing
Test event
Multiple SDUs
descriptions
Time measurement
DL data in TDD
t0 (see note 1)
Obtain the
reference time
t1 (see note 1)
Send DL data
Send DL data
Send 1st DL data
t2
Provide UL grant (see note 2)
Receive UL data
Send subsequent data
(see note 3)
NOTE 1: (t1-t0) 100 ms which is greater than the allowed SS max. delay time, 80 ms.
NOTE 2: (t2-t1) = 60 ms, this duration will allow the UE transmitting max. 3 scheduling requests (every 20 ms
once) after the UL data to be looped back being available at the UE without going onto PRACH.
NOTE 3: The applied TDD subframe numbers 4, 5, 9, 10, 14, 15, 19, 20, 24, 25,...
≥
If the test case prose does not indicate timely restrictions for the scheduling, sequential sending events are scheduled in
consecutive TTIs.
NOTE 1: For TDD configuration 1, the subframes 0, 4, 5 and 9 are considered as consecutive.
NOTE 2: Scheduling may imply to execute the test steps in the TTCN in an order different from the order given in
the test case prose. However, the sequence of the events over the air follows the prose description.
7.14
IP packets for Loopback Mode
7.14.1
IP packets used for Loopback Mode A
It is irrelevant which kind of data is used in loopback mode A. Some PDCP test cases however specify to use IP
packets. In these cases, an ICMPv4 ECHO REPLY shall be used with a valid IP header checksum and valid ICMP
checksum.
7.14.2
IP packets used for Loopback Mode B
According to TS 36.509 [4], the UE performs loopback mode B above the UL TFT entity. Therefore IP packets need to
match the packet filters signalled to the UE according to TS 36.508 [3], clause 6.6.2:
When the UE gets configured via NAS signalling with packet filter #1 and #2 according to TS 36.508 clause 6.6.2 the
IP packets shall fulfil the following requirements:
Protocol:
UDP referred to packet filter #1 and #2
IP addresses:
Referred to TS 36.508 [3], table 6.6.2-3, note 1 source and destination IP address are the same.
Ports:
⇒ IP packet's source port shall match remote port of packet filter #1.
packet filter #2 specifies UL filter ⇒ IP packet's destination port shall match remote port of packet filter #2.
packet filter #1 specifies DL filter
To summarize, on dedicated bearers for loopback mode B, UDP packets used shall match the packet filters configured
at the UE side. The UDP packets, having no specific content, shall have the correct header checksum and UDP
checksum. On the default bearer, any other packets can be used, as an example, ICMPv4 ECHO REPLY similar as for
loopback mode A.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.15
158
ETSI TS 136 523-3 V13.2.0 (2017-03)
Connected Mode DRX
The SS shall support connected mode DRX according to TS 36.321 [16], i.e. the SS shall not send any data to the UE
while the UE is not monitoring the PDCCH. To achieve this, the SS needs to estimate the UE's Active Time by
considering the on-duration as well as the drx-inactivity timer:
on-duration:
The on-duration can be derived from the SS' DRX configuration.
drx-inactivity timer:
According to TS 36.321 [16], clause 5.7 at the UE the drx-inactivity timer is started or restarted during the
Active Time whenever PDCCH indicates a new transmission (DL or UL).
There is no activation time for the configuration of DRX at the UE and it is not acceptable just to consider the
on-duration after re-configuration of the UE (for DRX_L according to TS 36.508 [3] the DRX cycle is 1.28 s); instead
the drx-inactivity timer needs to be taken in account after DRX reconfiguration as well.
The following rules shall be applied to achieve synchronisation of SS and UE:
1. SS shall consider drx-inactivity timer as restarted at the UE whenever the UE is addressed on the PDCCH (DL
data or UL grant).
2. When there is a scheduling request sent by the UE, SS assigns a grant independent of DRX;
when sending out that grant on PDCCH SS considers drx-inactivity timer as (re-)started (as per 1. above).
3. For all DL messages scheduled with specific timing information SS shall send the data at the given time
irrespective of current DRX configuration.
4. DRX (re-)configuration:
a) when DRX has not been configured at the UE yet:
a1) TTCN will configure the SS just before the sending out the RRCConnectionReconfiguration message
configuring DRX at the UE; no other send-events between the reconfiguration of the SS and sending the
RRC message shall be scheduled in TTCN.
a2) TTCN will schedule sending of the RRCConnectionReconfiguration message configuring DRX with
specific timing information.
b) Reconfiguration of DRX at the UE: Same as a) but:
b1) TTCN shall schedule sending of the RRCConnectionReconfiguration according to the old DRX
configuration (i.e. the SS does not need to cache the new configuration).
c) RRC connection release:
c1) TTCN will release DRX at the SS just after the RRC connection release procedure.
5. There shall be no parallel data on any DRBs during DRX reconfiguration.
NOTE:
Timing requirements in the DRX test cases:
a) The drx-Inactivity Timer shall be long compared to the duration between sending
RRCConnectionReconfiguration and receiving RRCConnectionReconfigurationComplete (> 50 ms).
It ensures the SS in-time sending of the RLC STATUS PDU.
or
b) The drx-cycle shall be short compared to the RLC timers applied for SRB1.
Figure 7.15-1 illustrates DRX (re)configuration at the SS and the UE.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
159
ETSI TS 136 523-3 V13.2.0 (2017-03)
Figure 7.15-1: DRX (Re)configuration
NOTE 1: Between RRCConnectionReconfiguration and RRCConnectionReconfigurationComplete the UE may
send a separate RLC STATUS PDU to acknowledge the RRCConnectionReconfiguration, but that does
not affect the principle as long as SS applies rule 2.
NOTE 2: During the "greyzone" SS does not know about DRX configuration at the UE; during that period
according to rule 4a1 and rule 5 there is no data to be sent by SS.
The TTCN (re)configures the connected mode DRX in SS for the test cases if DRX_S is applied (Ref. TS 36.508 [3].
The (re)configuration of DRX_L in SS is FFS.
Together with DRX, the SS shall implement eDRX for which an extended longDRX-Cycle can be configured. The
values of eDRX cycle can be of 5.12 and 10.24s for connected mode. When TTCN configures the eDRX cycle on the
SS alongside the DRX configuration, the SS shall apply it.
For test case 7.1.6.1 and 7.1.6.2, DRX will not be activated at the SS. Periodic UL grants every 5ms (suitable for both
FDD and TDD and less than drx-InactivityTimer 6ms) will be allocated to the UE during the steps configuring test case
specific DRX parameters of the test case to prevent UE from activating DRX; These grants may result in padding MAC
PDU's transmitted by UE, which will be received by SS MAC and discarded.
7.16
Handover Sequences
7.16.1
Sequence of inter-cell handover
In general, the Inter-Cell handover is done without activation time, i.e. the timing information for configuration of the
SS and sending of the RRCConnectionReconfiguration is ‘Now'.
The sequence may be interrupted if other events need to be handled. E.g. when a TAU procedure is performed in the
target cell and there are procedures left to be executed on the source cell.
1. Transfer of the PDCP Count for AM DRBs from source to target cell:
a) Source Cell: Get PDCP COUNT.
b) Target Cell: Set PDCP COUNT.
NOTE 1: There shall be no further sending/receiving of AM DRB data before the HO has been done.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
160
ETSI TS 136 523-3 V13.2.0 (2017-03)
2. Target Cell:
Inform the SS about the HO and about the source cell id.
3. Target Cell:
Configure RACH procedure either dedicated or C-RNTI based.
4. Target Cell:
Activate security.
NOTE 2: For AM DRBs the PDCP count is maintained (for SRBs and UM DRBs the PDCP count is reset).
5. Target Cell:
configure DRX (if necessary).
NOTE 3: As long as the DRX configuration is not modified by the RRCConnectionReconfiguration the target cell
gets the same DRX configuration as the source cell.
NOTE 3A: According to TS 36.331 clause 5.5.6.1 the measurement gap configuration is released at the UE due to
the handover, therefore nothing needs to be configured at the target cell regarding measurement gaps.
6. Source Cell:
Stop periodic TA.
NOTE 4: Unless explicitly specified UL grant configuration keeps configured as per default at the source cell.
7. Target Cell:
Configure UL grant configuration ("OnSR", periodic TA is not started).
8. Source Cell:
Send RRCConnectionReconfiguration.
9. Target Cell:
Receive RRCConnectionReconfigurationComplete.
10. Target Cell:
Start periodic TA.
11. Target Cell:
Inform the SS about completion of the HO (e.g. to trigger PDCP STATUS PDU).
12. Target Cell:
Re-configure RACH procedure as for initial access.
12a.
Target Cell: Configure measurement gap configuration (if necessary).
13. Source Cell:
Reset SRBs and release DRBs.
14. Source Cell:
Release DRX and MeasGapConfig configuration.
7.16.1a Sequence of inter-cell CA handover (more than one CC before and
after handover)
The Inter-Cell handover is done with activation time, i.e. the timing information for configuration of the SS and sending
of the RRCConnectionReconfiguration is explicit. Time ‘T’ is set to 700 ms in advance of the handover, time T1 = T +
10 ms and time T2 = T +20 ms.
At Time T , steps 1-3:
1. Source Pcell: Configure source primary cell for stop of automatic Time alignment MCE transmission by SS
2. Target Pcell: Configure target pcell for no RACH response transmission
3. Source Pcell: Schedule the transmission of RRC Connection Reconfiguration message to UE requesting
Handover to target Pcell and Scell
At time T2, steps 4-5:
4. Target Pcell: If target Pcell is same as source Scell, configure SS for target Pcell to be converted from a Scell to
Pcell
4a. Configuration of DRBs at the target PCell
5. Transfer of the PDCP Count for AM DRBs from source to target Pcell:
a) Source PCell: Get PDCP COUNT.
b) Target PCell: Set PDCP COUNT.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
161
ETSI TS 136 523-3 V13.2.0 (2017-03)
NOTE 1: There shall be no further sending/receiving of AM DRB data before the HO has been done.
At time T1, steps 6-12:
6. Target PCell: Inform the SS about the HO and about the source Pcell id.
7. Target PCell: Configure RACH procedure either dedicated or C-RNTI based.
8. Target PCell: Activate security.
NOTE 2: For AM DRBs the PDCP count is maintained (for SRBs and UM DRBs the PDCP count is reset).
9. Target PCell & Target Scell:
configure DRX.
NOTE 3: As long as the DRX configuration is not modified by the RRCConnectionReconfiguration the target cell
gets the same DRX configuration as the source cell.
NOTE 4: According to TS 36.331 clause 5.5.6.1 the measurement gap configuration is released at the UE due to the
handover, therefore nothing needs to be configured at the target cell regarding measurement gaps.
10. Target PCell: Configure UL grant configuration ("OnSR", periodic TA is not started).
11. Target PCell: Configure Target Pcell as Pcell.
12. Target SCell: Configure Target Scell for
12.1
Configure RACH procedure C-RNTI based.
12.2
Configure UL grant configuration ("OnSR", periodic TA is not started).
12.3
Configure target SCell as Scell with new Pcell association.
After time T2 (without activation time):
13. Target PCell: Receive RRCConnectionReconfigurationComplete.
14.Target PCell: Start periodic TA.
15. Target PCell: Inform the SS about completion of the HO (e.g. to trigger PDCP STATUS PDU).
16. Target PCell: Re-configure RACH procedure as for initial access.
16a.
Target Pcell & TargetSCell: Configure measurement gap configuration (if necessary).
17. Source PCell: If source Pcell is not target Scell, reset SRBs and release DRBs.
18. Source Pcell: If source Pcell is not target Scell, configure from Pcell to normal cell.
19. Source Pcell: If source Pcell is not target Scell, Release DRX and MeasGap configuration
20. Source SCell: If source Scell is neither target Pcell or Scell, Release DRX and MeasGapConfig configuration.
21. Source Scell: If source Scell is neither target Pcell or Scell, configure from Scell to normal cell.
22. Source Scell: If source Scell is neither target Pcell or Scell, Configure UL grant configuration ("OnSR", periodic
TA is not started).
7.16.2
Sequence of intra-cell handover
For Intra-Cell handover dedicated timing information is used: the sequence starts at time T with sending of the
RRCConnectionReconfiguration. T is set to 300 ms in advance of the handover.
0. Before T:
Get PDCP count for AM DRBs.
1. At T:
Send RRCConnectionReconfiguration.
2. At T + 5ms:
Release SRBs and DRBs.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
3. At T + 5ms:
162
ETSI TS 136 523-3 V13.2.0 (2017-03)
Configure RACH procedure either dedicated or C-RNTI based.
NOTE 1: Since the RACH procedure may require a new C-RNTI to be used it cannot be configured before sending
out the RRCConnectionReconfiguration.
3A At T + 5ms:
Release MeasGapConfig configuration.
NOTE 2: According to TS 36.331, clause 5.5.6.1 the measurement gap configuration is released at the UE due to
the handover, therefore MeasGapConfig is released unless a new measurement gap configuration is
explicitly given in the RRCConnectionReconfiguration.
4. At T + 10ms:
(Re-) configure SRBs and DRBs.
5. At T + 10ms:
Reestablish security, disable TA transmission.
NOTE 3: For AM DRBs the PDCP count is maintained while for SRBs and UM DRBs the PDCP count is reset.
6. (after step 5)
Receive RRCConnectionReconfigurationComplete.
7. (after step 6)
Re-configure RACH procedure as for initial access, enable TA transmissions.
8. (after step 7)
Restore the PDCP count for AM DRBs.
7.16.3
UL Grants used in RA procedure during handover
In the Random Access Procedure a grant is assigned to the UE by the Random Access Response and another grant, as
initial grant, is assigned for contention resolution.
When UL data is pending, the UE will try to put as much data into given grants as possible, i.e. it will segment the user
data and send it e.g. with the initial grant if possible. To avoid this segmentation of user data, the grants assigned during
handover will be set in TTCN to:
Grant assigned by Random Access Response:
56 bits.
Initial grant:
104 bits.
NOTE 1: According to TS 36.321 [16], clause 5.1.4, 56 bits are the minimum grant which can be assigned by the
Random Access Response. That is sufficient to convey C-RNTI (3 bytes) and short BSR (2 bytes) or long
BSR (4 bytes) but even with short BSR the remaining 2 bytes are not sufficient to convey any segment of
the RRCConnectionReconfigurationComplete (at least 4 bytes).
NOTE 2: The RRCConnectionReconfigurationComplete (9 bits) shall completely be conveyed in the initial grant of
RA procedure. This requires a minimum of 10 bytes (1 byte MAC header + 2 bytes RLC header + 5 bytes
PDCP header + 2 bytes payload). Additionally an optional PHR MAC element (2 bytes) needs to be
considered since the PHR has higher priority than the MAC SDU. Any further user data would require a
minimum of 5 additional bytes (2 bytes MAC header + 2 bytes RLC header + 1 byte payload).
7.17
Simulation of PDCP MAC-I Failure in UE
PDCP integrity protection test cases 7.3.4.x have the requirement to trigger MAC-I failures in UE for downlink
messages; to achieve the MAC-I failure in UE two methods are specified in the subsequent sub clauses.
7.17.1
Integrity and ciphering not yet activated
UE has not yet started Integrity protection and it is required to trigger MAC-I failure for the PDCP PDU carrying RRC
SecurityModeCommand starting integrity with one of integrity protection algorithms. Further a conformant UE will
respond with SecurityModeFailure without any integrity protection.
This is achieved by:
Not configuring SS PDCP to start integrity and ciphering with selected algorithm.
RRC SecurityModeCommand is sent indicating Integrity protection through the desired algorithm.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
163
ETSI TS 136 523-3 V13.2.0 (2017-03)
Normal behaviour of PDCP layer in SS will include all zeros in MAC-I.
This results in MAC-I failure as UE will calculate the XMAC-I with indicated algorithm.
7.17.2
Integrity and/or ciphering already activated
UE has started Integrity protection (ciphering configured with possibly non null algorithm) and it is required to trigger
MAC-I failure for the PDCP PDU carrying an RRC UECapabilityEnquiry message. A conformant UE will trigger an
RRCConnectionReestablishment procedure.
This is achieved by:
Configuring SS PDCP to use a different Integrity algorithm other than used by UE (i.e. if UE is configured to use
AES, SS is configured to use SNOW3G and vice versa).
Ciphering is configured at SS side same as in UE side.
The MAC-I included by SS PDCP will be as per new algorithm.
UE will calculate XMAC-I based on its own algorithm which is different from the algorithm SS has used and will
result in MAC-I failure.
7.18
RRC Connection Release Sequence
According to TS 36.331 [19], clause 5.3.8.3, after reception of the RRCConnectionRelease the UE may either wait
60 ms or for indication of acknowledgement from lower layer. After the RRC connection release there are cases where
the UE may immediately come up with an RRC connection request. This requires scheduled release of resources at the
SS:
1. At T:
Send RRCConnectionRelease, stop UL grants.
2. At T + 5ms:
Release security.
3. At T + 10ms:
Release DRX configuration at the SS.
3A At T + 15ms:
Release measurement gap configuration at the SS.
4. At T + 50ms:
no action.
5. At T + 55ms:
Release SRBs and DRBs.
6. At T + 60ms:
(Re-) configure SRBs.
7. Delay of 840ms (NOTE)
T is set to 300ms in advance of RRC connection release.
NOTE: The delay ensures that the UE is camping on the serving cell again to avoid side effects e.g. due to
subsequent power level changes. It does not affect any sending of messages by the UE. The delay 840ms
is chosen to ensure the UE is re-camping on the cell and has read relevant system information, MIB,
SIB1, SIB2 and all other SIs.
7.19
DL CCCH Message and Contention Resolution MAC
Control Element transmission in one MAC PDU or in
separate MAC PDUs
When the contention based RACH procedure is being executed (RRC Connection Establishment or RRC Connection
Reconfiguration), in general the contention resolution MAC control element and the DL RRC PDU (RRC Connection
Setup/RRC Connection Reject/RRC Connection Re-establishment/RRC Connection Re-establishment Reject) are sent
in one MAC PDU. This is achieved by pre-configuring the SS (before the start of the RRC procedure) to send the
encoded DL message and contention resolution MCE in one MAC PDU.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
164
ETSI TS 136 523-3 V13.2.0 (2017-03)
Nevertheless, due to specific test purposes there are still many cases where it is necessary to send the DL CCCH
message separately:
RRC connection establishment
When RRC connection establishment is part of the test purpose
Special cases: , e.g. when no contention resolution shall be sent according to the test purpose
RRC Connection Reestablishment is part of the test purpose
RRC Connection Reject is part of the test purpose
RRC Connection Reestablishment Reject is part of the test purpose
NOTE:
7.20
The way contention resolution is applied has impact on the DCI format being used in a test case: when the
DL CCCH message is sent separately DCI combination 1 according to clause 7.3.1 shall be used.
RRC Connection Reconfiguration Sequence (Measurement
Control)
When an RRC Connection Reconfiguration message contains information to configure measurement gaps at the UE
according to TS 36.331 [19] clause 5.5.2.9, the SS needs to be configured accordingly:
IF MeasConfig contains measGapConfig:
1. At T:
Send RRC Connection Reconfiguration.
2. At T + 5ms:
Configure measurement gaps at the SS.
3. (after step 2)
Receive RRC Connection Reconfiguration Complete
ELSE
1. Send RRC Connection Reconfiguration (without scheduling)
2. Receive RRC Connection Reconfiguration Complete.
T in general is set to 100ms in advance of the RRC connection reconfiguration.
7.21
Inter-RAT - GERAN special issues
7.21.1
Timeslot assigned for GERAN CS traffic
Timeslot 3 shall be used as the timeslot assigned for GERAN CS traffic, in order to avoid conflicts with timeslots
reserved for other purposes (e.g. the GPRS channel which is assigned to timeslot 4).
7.21.2
Subchannel used in GERAN L2 access message
The subchannel is valid only for the following logical channel types: FACCH/H, SDCCH/8, SDCCH/4. For other
logical channel types this field is not applicable and shall be coded as 15 for compatibility with TTCN2 test cases. The
SS shall ignore it if this field is coded as 15.
7.21.3
Paging in GERAN
The system paging parameter BS_PA_MFRMS is set to a value of 2 multi frames, in order to ensure the next paging
occasion is as soon as possible.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
165
7.22
EUTRAN RSRQ Calculations
7.22.1
Assumptions
ETSI TS 136 523-3 V13.2.0 (2017-03)
-
As per 36.214 [53] clause 5.1.1 and 5.12, the RSRP and RSSI shall be averaged over the same set of resource
blocks. It is assumed that the power calculations made over one symbol are good enough for RSRQ calculations.
This is based on the assumption that the power levels remain the same across the symbols on which the UE is
calculating the average. The contribution of Nprb and the OFDM symbols carrying cell specific reference
symbols per PRB contribute equally in numerator and denominator, hence RSRQ calculations in dB with
aggregation over cell DL bandwidth and without aggregation result in the same output.
-
As per table 7.4.3.1.1-1, for FDD the timing offset between the intra frequency cells is always a multiple of sub
frame duration i.e. 3072 Ts, hence in the symbols carrying cell-specific reference signals in one cell, the other
cell (interference) is also carrying a cell-specific reference signal, even though in a different subframe. Hence
from an interference calculation perspective, we can safely assume that the cells contributing an interference
shall also transmit the same cell specific reference signal in the symbol/
-
The noise source is treated as a dummy cell transmitting on all resource elements with equal EPRE. Hence to
switch off the noise source, a value of non-suitable "Off" cell, as per 36.508 [3] table 6.2.2.1-1 shall be used (<145), and the signal level uncertainties similar to configured cells in 36.508 [3] clause 6.2.2.1 will also be
applied to the noise source.
-
When the Noc value remains 'off' during the test case execution, the Virtual Noise Generator is not configured in
the SS.
7.22.2
The Ideal Calculation
The test case specifies the RS-EPRE (dBm/15kHz) which is the cell absolute power-cell attenuation in dBm per carrier
of 15 kHz; the linear average over few measurements will give the RRP value.
It is assumed that the power levels of all contributors is fluctuating hence in the typical test environment RS-EPRE will
be the RSRP over a single carrier frequency.
The RS-EPREmW(mW/15kHz) = 10 power (RSRP/10).
The energy in noise source [Noc] for the frequency is also specified in the same units of dBm/15kHz.
The RSSImW calculation(mW over a resource block frequency of 180 kHz) = 2 (the sum over all intra frequency
configured cells RS-EPREmW) + 10 power ((Noc/10)*12.
The cell inference is multiplied by 2 as in a RB, cell specific reference is transmitted in only 2 carriers. But the AWGN
transmits on all 12 carriers in the resource block.
The RSRQ in dB will be the 10*log (RS-EPREmW/RSSImW).
7.22.3
Additional RSRQ Calculations For Fixing Boundary Values
In addition to the ideal calculation, various RSRQ calculations take into consideration the combinations of the SS signal
uncertainties and possibly all 12 carriers being used for DL transmission.
The 12 carriers being used can happen when the UE makes the measurement in a subframe when a DL PDSCH is
scheduled or measurement is in subframe zero and the UE measures in OFDM symbol carrying PBCH i.e. slot 1,
symbol 0.
The Min and Max RSRQ values are identified from 6 different RSRQ calculations:
RSRQ Ideal: RSRQ calculated in ideal conditions as given above
RSRQ Min: RSRQ calculation applying –ve signal uncertainty to all configured cells and noise source
RSRQ Max: RSRQ calculation applying +ve signal uncertainty to all configured cells and noise source
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
166
ETSI TS 136 523-3 V13.2.0 (2017-03)
RSRQ Max Worst Case: RSRQ calculation applying +ve signal uncertainty for measured cell and –ve signal
uncertainty to all remaining configured cells and noise source. This shall be the Max RSRQ possible
RSRQ Max And 12 Carriers: RSRQ calculation applying +ve signal uncertainty to all configured cells and noise source
and cell interference considered over all 12 carriers
RSRQ Min Worst Case And 12 Carriers: RSRQ calculation applying -ve signal uncertainty for measured cell and +ve
signal uncertainty to all others; and cell interference considered over all 12 carriers. This shall be the Min RSRQ
possible
Applying UE measurement accuracy 36.133 [37], Table 9.1.6.2-1, +/-4dB normal conditions and side conditions of
RSRQ when RSRP Ês/Iot ≥ -6 dB & RSRP ≥ -124 dBm the final boundary value for RSRQ is
Min RSRQ With UE Meas Acc := Min RSRQ -4 dB
Max RSRQ With UE Meas Acc := Max RSRQ + 4 dB
For conditions to fulfil desired cell selection or reselection, the respective conditions shall be satisfied for both the
boundary values Min RSRQ RSRQ With UE Measurement Accuracy and Max RSRQ With UE Measurement
Accuracy.
As the Boundary conditions also consider the worst scenario of all 12 carriers being transmitted, the requirement for
OCNG is removed. There is no need to restrict measurement bandwidth and will be applicable for both DCI formats.
7.23
Test method for eICIC and feICIC
When periodic CQI feedback is requested due to TTCN configuration, the SS reports the periodic CQI to the TTCN. SS
does not react on periodic CQI received and still allocates grants as configured from TTCN.
In the selected ABS no DL/UL user data (SRB/DRB) is scheduled, nor paging is transmitted; this is controlled by
TTCN.
For feICIC testing, the SS may be configured to temporarily stop the transmission of SIB1 and its associated DCI.
7.24
Carrier Aggregation Signalling Sequences
7.24.1
Initial configuration of Pcell
Cell is configured as a normal cell by using function f_EUTRA_CellConfig_Def. The missing CA default parameters
(e.g. UL power control Common) are configured by using additional ASP call(s).
EUTRA_PTC
PCELL
f_EUTRA_CellConfig_Def
UL power control Common
Figure 7.24.1-1: CA sequence of an initial cell configuration for a cell to be used as Pcell
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.24.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
167
Initial configuration of SCell
Cell is configured as a normal cell except for SRB/DRB configuration by function f_EUTRA_SS_ConfigureActiveCell.
SRB0 not yet configured in step 1 is then configured.
The missing CA default parameters (e.g. UL power control (Common + Dedicated), PUSCH config Dedicated, SRS UL
Dedicated) are configured by using additional ASP call(s).
EUTRA_PTC
SCell
f_EUTRA_SS_ConfigureActiveCell
New Function for SRB0 Config
UL power control (Common + Dedicated), PUSCH config Dedicated, SRS UL Dedicated
Figure 7.24.2-1: CA sequence of an initial cell configuration for a cell to be used as Scell
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.24.3
ETSI TS 136 523-3 V13.2.0 (2017-03)
168
Scell Addition and/or release
EUTRA_PTC
Repeated
for each
Scell to be
added
PCELL
UE
SCELL
[If ScellAdd>0]ServingCellConfig.PCell
[If ScellAdd>0]C-RNTI Cont Based RachPr ocedure
[If ScellAdd>0]C-RNTI
[If ScellAdd>0 AND PCell DRX Config] DRX Config
[If ScellAdd>0 AND PCell Meas Gap Config] Meas Gap Config
[If ScellAdd>0]Servi ngCellConfig.SCell
[If ScellAdd>0] UL Grant Config (no Grant, no PUCCH Synch)
RRCConnectionReconfiguration
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
RRCConnectionReconfigurationComplete
[IF ScellAdd=0 AND ScellDel>0]ServingCellConfig.Release
Repeated
for each
Scell to be
deleated
[IF ScellScellDel>0 AND DRX config Scell]DRX Release
[IF ScellScellDel>0 AND Meas Gapconfig] ScellMeas Gap Rel
[IF ScellDel>0] UL Grant Config(Default grant, no PUCCH Sync)
[IF ScellD el>0]ServingCellConfig.Rel ease
Figure 7.24.3-1: CA sequence of Scell Addition and/or release
7.25
Test method for MBMS
7.25.1
Schedule transmission of MCCH messages
The rules for the transmission of MCCH messages are specified in TS 36.331 [19], clause 5.8.1.2. The ASPs
SYSTEM_CTRL_REQ and SYSTEM_CTRL_CNF are used as interface to SS; the following rules apply:
The complete MCCH information is provided to SS by using a single ASP. The MCCH carries the
MBSFNAreaConfiguration and may also carry the MBMSCountingRequest message.
The scheduling information sent to SS is the same as the scheduling information sent to the UE.
The MCCH information is sent to SS using the asn.1 types, SS shall encode in unaligned PER and add the necessary
padding bits as specified in TS 36.331 [19], clause 9.1.1.1.
Segmentation occurs when the MCCH message size is larger than the TBS of the MCH. SS starts scheduling all
MCCH information blocks from the same SFN.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
169
ETSI TS 136 523-3 V13.2.0 (2017-03)
NOTE: With the default values NPRB=NRBDL=25 for 5 MHz and default signalling Imcs =2; then Itbs=2 and
the TB size will be 1096 bits, hence segmentation may never happen.
7.25.2
MCCH change notification
A change notification is used to indicate the modification of MCCH information. The notification is transmitted on
PDCCH, it includes the notification indicator provided in the ASP and is transmitted using the M-RNTI (defined in
3GPP TS 36.321 [16] Table 7.1-1).
The notification messages are sent during one modification period before transmitting the modified MCCH information.
The SFN for the start of modification period is calculated by TTCN. The modified MCCH information and the
calculated SFN are provided in the ASP SYSTEM_CTRL_REQ. The notification messages are sent on SFN/subframes
calculated by TTCN according to 36.331 [19] clause 6.3.7.
7.25.3
MTCH data scheduling
The SS is configured with configuration parameters for CSA, PMCH, MRBs, MSI and scheduling information for
MTCH data transmission.
The TTCN shall ensure that:
-
For each configured MCH, the routing & timing information of the scheduled MRB data is consistent with the
configured MSI.
-
The size of all MRB data scheduled in the same subframe shall fit within the resource allocation of that
subframe.
The SS shall ensure that:
-
In subframes belonging to the CSA and for which no MCCH/MTCH/MSI data is scheduled by the TTCN, no
MCH data shall be sent in MBMS subframes not used as per MSI.
If an MTCH packet is scheduled from TTCN in a subframe in which MCCH will be automatically transmitted by SS
and/or MSI is configured and needs to be included, the MTCH packet and MCCH data along with possible MSI are
included in one MAC PDU and signallingMCS is used.
When data is sent on MTCH the SS shall set the MSI in the MAC header according to TS 36.321 [16] clause 6.1.3.7.
The periodicity of the MSI is defined by the MCH scheduling period i.e. the MSI is not necessarily included in the
subframe where the RLC SDU is transmitted.
7.26
Type B FDD Half-Duplex Considerations
Type B FDD half-duplex UE has limitations in receiving a DL subframe preceding or following a UL subframe for the
same UE hence a blank subframe is needed. In [non TTI bundling considerations] max 3 contiguous subframes UL or
DL can be scheduled. And after and before any contiguous DL/UL subframes block a blank subframe is needed.
If the UE under test is a Type B FDD half-duplex UE:
-
SS will be configured per cell by providing UE category info and FDD half-duplex operation.
-
When explicit timing info is provided in any DL transmission, the SS shall ignore the UE capability and shall
follow the explicit scheduling. It will be TTCN responsibility to schedule UL/DL transmissions based on UE
capability. Paging is always explicitly scheduled and hence SS follows explicit scheduling for paging.
-
For UE Category 0, SI scheduling will be configured as per TDD SI scheduling (Table 7.7.2-4) restricting
system info transmissions in sub frames 0 and 5. For UE Category M1, SI scheduling is specified in clause
7.7.2a.
-
For non-explicitly scheduled new DL transmissions/ new UL grant allocations, the SS shall restrict UL/DL
operations as per table below:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
170
Table 7.26-1: Scheduling pattern for type B half-duplex FDD UE (non-explicitly scheduled)
-
SFN\
SubFrame
0
1
X (any)
SI
Blank
2
3
New UL
Data/ Blank
HARQ
4
5
6
7
Blank
SI
DL
HARQ
Blank
8
New DL
Data/ UL
Grant
9
Blank
If HARQ retransmissions are required:
-
DL retransmissions being asynchronous in nature shall be scheduled by the SS as per above schedule (i.e.
subframe 8).
-
UL retransmissions being synchronous will not be limited to subframe 2. i.e. the first UL retransmission will
be in frame X+1, subframe 0, second retransmission in frame X+1, subframe 8 and so on.
-
HARQ retransmissions shall be prioritised over new transmissions.
7.27
Test method for Device-to-Device Proximity Services
7.27.1
Direct Discovery test method
SS-UE is configured in coverage, i.e. it is associated with a EUTRA-cell (as specified in clause 7.27.2.1).
SS-UE can be configured for sidelink data transmission and/or reception:
-
When UE under test is configured in sidelink discovery type 1 (i.e. ue-Selected), the SS-UE is configured in
reception with the same pool(s) of resource.
-
When UE under test is configured in sidelink discovery type 2B (i.e. scheduled), the SS-UE is configured in
reception with the same pool of resource and same indexes.
-
For transmission, TTCN configures the SS-UE with a pool of resources and provides the SL_DATA_REQ ASP
including:
-
the SL-DCH message to be transmitted,
-
the timing info indicating the SFN/Subframe of the first discovery period,
-
the number of discovery periods in which the message shall be transmitted,
-
the selected PSDCH resource value (n_PSDCH), this value is incremented by TTCN after each transmission
cycle. To avoid clashes when multiple PC5_DISCOVERY messages are transmitted within the same
discovery period, TTCN will provide different n_PSDCH values.
7.27.2
7.27.2.1
Direct Communication test method
Synchronisation and SBCCH transmission
When configured in coverage, the SS-UE is associated with a EUTRA-cell, it is configured with the same configuration
parameters i.e. Band, Bandwidth, UL frequency, Cell timing, TDD Frame structure of the associated EUTRA cell.
When out of coverage, SS-UE is configured explicitly by TTCN, e.g. Band, Bandwidth, TDD Frame structure. For
timing synchronisation SS-UE can be configured either:
-
To synchronise from UE under test transmitted SLSS/MIB-SL: UE under test is the synchronisation source. The
SS-UE shall use the received SLSS and MIB-SL including the DirectFrameNumber/DirectSubframeNumber as
synchronisation source as specified in TS 36.331 [19], clause 5.10.9.2
-
To be the synchronisation source: SS-UE shall initiate autonomously the
DirectFrameNumber/DirectSubframeNumber and transmit SLSS/MIB-SL.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
171
ETSI TS 136 523-3 V13.2.0 (2017-03)
When the SS-UE is configured by TTCN over sidelink system control port to receive/transmit SLSS and MIB-SL, the
following rules apply:
-
For transmission, the complete MIB-SL message is provided to SS-UE. SS-UE shall set the DirectFrameNumber
and DirectSubframeNumber in the MIB-SL, a dummy value is provided by TTCN.
-
The MIB-SL is sent to SS-UE using asn.1 types. The rules for encoding and transmission of SBCCH messages
(MIB-SL) are specified in TS 36.331 [19].
-
For reception, SS-UE shall report SLSS or MIB-SL over the sidelink system indication port.
7.27.2.2
Sidelink data transmission/reception
When UE is in coverage and configured in transmission mode 1 (i.e. scheduled), the sidelink Scheduling Grant is
configured in SS by TTCN over system control port. On PDCCH, the SS informs the UE under test if it is allowed to
make sidelink data transmission by transmitting 'DCI format 5' including ‘SCI format 0’ with the CRC scrambled by
SL-RNTI (acc. to TS 36.213 [30] clause 14.2). The UE under test will transmit on PSCCH/PSSCH as specified in the
received DCI format 5 and ‘SCI format 0’. SS shall only react on reception of SR and grant allocation configured from
the TTCN. The following sidelink grant allocation is configured:
-
SS is configured to maintain PUCCH Synch.
-
SS is configured to send automatically a 'configured Grant' (in terms of NPSCCH, ITRP and NPRB) to the UE on
every reception of a Scheduling Request, within 10 subframes.
-
-
The default resource for PSCCH is NPSCCH = 11,
The default configured grant for PSSCH in SCI format 0 is ITRP = 36 and NPRB = 25. The SS shall allocate
resource allocation RBs corresponding to PRB indices 0..(NPRB-1).- SS-UE is configured with the same pool(s)
of resources as UE under test.
When UE is out of coverage or configured in transmission mode 2 (i.e. ue-Selected), UE selects autonomously the
resources on PSCCH/PSSCH. SS-UE is configured with the same pool(s) of resources as UE under test.
The SS-UE, when triggered to transmit data, is configured with IMCS=0 and the same NPSCCH , ITRP and NPRB as
specified above.
7.28
Test method for SC-PTM
7.28.1
Schedule transmission of SC-MCCH messages
The rules for the transmission of SC-MCCH messages are specified in TS 36.331 [19], clause 5.8a.1.2. The ASPs
SYSTEM_CTRL_REQ and SYSTEM_CTRL_CNF are used as interface to SS; the following rules apply:
-
The complete SC-MCCH information is provided to SS by using a single ASP. The SC-MCCH carries the
SPCTMConfiguration message.
-
The scheduling information sent to SS is the same as the scheduling information sent to the UE.
-
The SC-MCCH information is sent to SS using the asn.1 types, SS shall encode in unaligned PER and add the
necessary padding bits as specified in TS 36.331 [19], clause 9.1.1.7.
-
Segmentation occurs when the SC-MCCH message size is larger than the TBS of the DL-SCH. SS starts
scheduling all SC-MCCH information blocks from the same SFN.
NOTE:
With the default values NPRB=NRBDL=25 for 5 MHz and default signalling Imcs =2; then Itbs=2 and
the TB size will be 1096 bits, hence segmentation may never happen.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7.28.2
172
ETSI TS 136 523-3 V13.2.0 (2017-03)
SC-MCCH information change
There are two possibilities to update SC-MCCH information. One is to transmit modified SC-MCCH information at the
beginning of the modification period. Alternatively, notification mechanism can be used. The notification is transmitted
using the DCI format 1C with SC-N-RNTI (defined in 3GPP TS 36.321 [16] Table 7.1-1) and one bit within the 8-bit
bitmap. The notification is sent in the first subframe, which can be used for SC-MCCH transmission in a repetition
period. Modified SC-MCCH message is to be transmitted starting from the same subframe, as defined in TS 36.300
clause 15.3.5a.
The SFN for the start of modification to SC-MCCH is calculated by TTCN according to TS 36.331 [19] clause 6.3.1 as
defined for SystemInformationBlockType20. The modified SC-MCCH information, the calculated SFN and a flag,
pointing on if a notification mechanism has to be used, are provided in the ASP SYSTEM_CTRL_REQ.
7.28.3
SC-MTCH data scheduling
The SS may be configured with scheduling information for SC-MTCH data transmission. The TTCN shall ensure that
SC-MTCH packets will be scheduled for the transmission only during the Active Time for a PDCCH subframe as
defined in TS 36.321 [16] clause 5.7a.
7A
NB-IoT Test Methods and Design Considerations
NOTE:
7A.1
Unless explicitly stated otherwise, the present clause and its subclauses apply to the NB-IoT anchor
carrier.
Physical signals and channels
For Signalling testing, single Tx antenna shall be used by the SS, unless specified otherwise in a test case.
The SS shall transmit all NB-IoT physical signals and channels according to TS 36.211 [35], with the following
additional requirements, unless specified otherwise in a test case:
-
The NRS shall be transmitted on one antenna port.
-
The NPSS and NSSS shall be transmitted on one and the same antenna port.
No (WB-E-UTRA) LTE signals and channels shall be transmitted by the SS, except for the case of ‘in-band same PCI’
operation mode where the SS shall transmit the LTE CRS. For the in-band operation modes, TTCN will provide the
necessary LTE CRS configuration to the SS ; for the case of ‘in-band different PCI’ operation mode, the SS shall use
this information to skip the resource elements, which should be occupied by the LTE CRS, when transmitting NB-IoT
downlink physical channels.
7A.2
System information
7A.2.1
System information broadcasting in general
TTCN provides separately the BCCH (MIB-NB, SIB-NB’s) messages to transmit, and the scheduling of how and when
to transmit them. However the complete information is provided to the SS by using a single ASP.
The SS shall transmit all BCCH messages according to TS 36.331 [19], with the following additional requirements:
-
SS shall start scheduling all BCCH messages from the same timing (H-SFN, SFN).
-
SS shall set and maintain the SFN-MSB and the HSFN-LSB in the MIB-NB message provided by TTCN,
according to its internal timing. A dummy value is provided by TTCN.
-
SS shall set and maintain the HSFN-MSB in the SIB1-NB message provided by TTCN, according to its internal
timing. A dummy value is provided by TTCN.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
ETSI TS 136 523-3 V13.2.0 (2017-03)
173
TTCN provides the BCCH messages to the SS using the ASN.1 types. The SS shall encode them in unaligned
PER and add the necessary padding bits as specified in TS 36.331 [19], clause 8.5.
7A.2.2
System information scheduling and synchronisation signals
For NB-IoT the scheduling of UL and DL data strongly depends on the scheduling of system information and
synchronisation signals: The SS can schedule DL assignments and UL grants only in subframes which are not used by
system information or synchronisation signals.
This clause shows the allocation of system information and synchronisation signals according to core specifications and
for cases of common system information scheduling according to TS 36.508 [3] clause 8.1.4.3.
NOTE:
Unless explicitly stated otherwise, the present clause and its subclauses apply to downlinkBitmap-r13 not
being specified in SIB1-NB.
7A.2.2.1
MIB-NB, NPSS, NSSS
NPSS is transmitted in subframe 5 of every radio frame (TS 36.211 [35] clause 10.2.7.1.2).
NSSS is transmitted in subframe 9 of every radio frame with even frame number (TS 36.211 [35] clause 10.2.7.2.2).
MIB-NB is sent on NPBCH: It is split into 8 blocks, each of which is repeated 8 times in the first subframe of a frame
(TS 36.331 [19] clause 5.2.1.2a)
MIB uses first subframe of every frame, periodicity is 640ms.
⇒
Table 7A.2.2.1-1: MIB-NB, NPSS, NSSS scheduling
SFN mod 2 = 0
...
...
...
0
N
P
B
C
H
7A.2.2.2
1
2
3
4
5
N
P
S
S
SFN mod 2 = 1
6
7
8
9
N
S
S
S
0
N
P
B
C
H
1
2
3
4
5
N
P
S
S
6
7
8
9
SIB1-NB
SIB1-NB scheduling depends on
-
schedulingInfoSIB1-r13 contained in MasterInformationBlock-NB:
TBS of 208, 328, 440 or 680 and 4, 8 or 16 repetitions (TS 36.213 [30] Tables 16.4.1.3-3 & 16.4.1.5.2-1)
-
Physical Cell ID (PCID) derived by the UE from the NSSS:
Starting radio frame number for NB-SIB1 repetitions depends on the PCID and the number of repetitions (TS
36.213 [30] Table 16.4.1.3-4)
According to TS 36.331 [19] clause 5.2.1.2a independent from the TBS a single SIB1-NB transmission takes every
second of 16 sub-sequent frames and the parts of the SIB1-NB are sent at subframe #4.
Table 7A.2.2.2-1shows SIB1-NB scheduling for the 16 repetitions for the case that the radio frame of the first
Ncell
transmission is 0 ( N ID
mod 4 = 0 in Table 16.4.1.3-4 of TS 36.213 [30]); frames with SIB1-NB are shown in green.
ETSI
...
...
...
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
174
Table 7A.2.2.2-1: SIB1-NB scheduling with 16 repetitions
frame 0
frame 0
frame 16
frame 32
frame 48
frame 64
frame 80
frame 96
frame 112
frame 128
frame 144
frame 160
frame 176
frame 192
frame 208
frame 224
frame 240
frame 1
frame 1
frame 17
frame 33
frame 49
frame 65
frame 81
frame 97
frame 113
frame 129
frame 145
frame 161
frame 177
frame 193
frame 209
frame 225
frame 241
7A.2.2.3
frame 2
frame 2
frame 18
frame 34
frame 50
frame 66
frame 82
frame 98
frame 114
frame 130
frame 146
frame 162
frame 178
frame 194
frame 210
frame 226
frame 242
frame 3
frame 3
frame 19
frame 35
frame 51
frame 67
frame 83
frame 99
frame 115
frame 131
frame 147
frame 163
frame 179
frame 195
frame 211
frame 227
frame 243
frame 4
frame 4
frame 20
frame 36
frame 52
frame 68
frame 84
frame 100
frame 116
frame 132
frame 148
frame 164
frame 180
frame 196
frame 212
frame 228
frame 244
frame 5
frame 5
frame 21
frame 37
frame 53
frame 69
frame 85
frame 101
frame 117
frame 133
frame 149
frame 165
frame 181
frame 197
frame 213
frame 229
frame 245
frame 6
frame 6
frame 22
frame 38
frame 54
frame 70
frame 86
frame 102
frame 118
frame 134
frame 150
frame 166
frame 182
frame 198
frame 214
frame 230
frame 246
frame 7
frame 7
frame 23
frame 39
frame 55
frame 71
frame 87
frame 103
frame 119
frame 135
frame 151
frame 167
frame 183
frame 199
frame 215
frame 231
frame 247
frame 8
frame 8
frame 24
frame 40
frame 56
frame 72
frame 88
frame 104
frame 120
frame 136
frame 152
frame 168
frame 184
frame 200
frame 216
frame 232
frame 248
frame 9
frame 9
frame 25
frame 41
frame 57
frame 73
frame 89
frame 105
frame 121
frame 137
frame 153
frame 169
frame 185
frame 201
frame 217
frame 233
frame 249
frame 10
frame 10
frame 26
frame 42
frame 58
frame 74
frame 90
frame 106
frame 122
frame 138
frame 154
frame 170
frame 186
frame 202
frame 218
frame 234
frame 250
frame 11
frame 11
frame 27
frame 43
frame 59
frame 75
frame 91
frame 107
frame 123
frame 139
frame 155
frame 171
frame 187
frame 203
frame 219
frame 235
frame 251
frame 12
frame 12
frame 28
frame 44
frame 60
frame 76
frame 92
frame 108
frame 124
frame 140
frame 156
frame 172
frame 188
frame 204
frame 220
frame 236
frame 252
frame 13
frame 13
frame 29
frame 45
frame 61
frame 77
frame 93
frame 109
frame 125
frame 141
frame 157
frame 173
frame 189
frame 205
frame 221
frame 237
frame 253
frame 14
frame 14
frame 30
frame 46
frame 62
frame 78
frame 94
frame 110
frame 126
frame 142
frame 158
frame 174
frame 190
frame 206
frame 222
frame 238
frame 254
frame 15
frame 15
frame 31
frame 47
frame 63
frame 79
frame 95
frame 111
frame 127
frame 143
frame 159
frame 175
frame 191
frame 207
frame 223
frame 239
frame 255
SI-messages containing SIB3-NB, SIB4-NB, SIB5-NB, SIB14-NB, SIB16-NB
Scheduling of SI messages is specified in TS 36.331 [19] clauses 5.2.1.2a and 5.2.3a.
As SI messages are sent on NPDSCH, only "NB-IoT DL subframes" can be used according to TS 36.213 [30] clause
16.4: In case of SIB1-NB not specifying downlinkBitmap-r13 NB-IoT DL subframes are subframes not containing
NPSS/NSSS/NPBCH/NB-SIB1 transmissions.
The parameters for SI scheduling are contained in SystemInformationBlockType1-NB:
Configuration common for all SI messages:
-
Window size
-
Frame offset for scheduling
Configuration per SI message:
-
SI window:
According to TS 36.331 [19] clause 5.2.3a the position of an SI-window depends on the order of the
corresponding SI-message in the list, the window size and the periodicity.
-
Repetitions of the SI-message:
Within an SI-window repetitions are specified by the repetition-pattern.
-
SIBs mapped to the SI-message
-
Transport block size (TBS) and number of subframes (NSF) used for transmission:
According to clause 6.7.2 of TS 36.331 [19] NSF is either 2 (for TBS = 56, 120) or NSF is 8 (for TBS = 208, 256,
328, 440, 552, 680).
7A.2.2.3.1
SI combination 1 scheduling
TS 36.508 [3] clause 8.1.4.3 specifies configuration of SI combination 1 scheduling as shown in table 7A.2.1.3.1-1 with
⇒ SIB1-NB in every second frame at subframe 4
-
16 Repetitions of SIB1-NB
-
si-WindowLength-r13:
ms160
-
si-RadioFrameOffset-r13:
0 (not present in SystemInformationBlockType1-NB)
-
1 SI-message:
- SI-Window 1
si-Periodicity-r13
si-RepetitionPattern-r13
si-TB-r13
rf64
every8thRF
NSF = 8
552
-
⇒
According to TS 36.331 [19] clause 5.2.3a the SI-windows start at subframe 0 of frame SI1:
with TSI1 = 64
(H-SFN * 1024 + SFN) mod TSI1 = 0;
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
175
Table 7A.2.2.3-1: SI combination 1 scheduling (SIB2-NB only)
SI
Wind
ow
K
SFN = K
SFN = K + 1
SFN = K + 2
SFN = K + 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
...
SI-1
SI-1
0
4
8
12
16
20
24
28
32
36
40
44
48
52
56
60
64
68
72
76
80
84
88
92
...
With
NPBCH
7A.2.2.3.2
NPSS
NSSS
SIB1-NB
SI-1
SI combination 2/3/4 scheduling
TS 36.508 [3] clause 8.1.4.3 specifies configuration of SI combination 2/3/4 scheduling as shown in table 7A.2.1.3.1-2
with
⇒ SIB1-NB in every second frame at subframe 4
-
16 Repetitions of SIB1-NB
-
si-WindowLength-r13:
ms160
-
si-RadioFrameOffset-r13:
0 (not present in SystemInformationBlockType1-NB)
-
3 SI-messages:
- SI-Window 1
si-Periodicity-r13
si-RepetitionPattern-r13
si-TB-r13
- SI-Window 2
si-Periodicity-r13
si-RepetitionPattern-r13
si-TB-r13
- SI-Window 3
si-Periodicity-r13
si-RepetitionPattern-r13
si-TB-r13
-
rf64
every8thRF
NSF = 8
552
⇒
rf64
every16thRF
256 NSF = 8
⇒
rf64
every16thRF
256 NSF = 8
⇒
According to TS 36.331 [19] clause 5.2.3a the SI-windows start at subframe 0 of frame
with TSI1 = 64
(H-SFN * 1024 + SFN) mod TSI1 = 0;
with TSI2 = 64
(H-SFN * 1024 + SFN) mod TSI2 = 16;
with TSI3 = 64
(H-SFN * 1024 + SFN) mod TSI3 = 32;
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
176
Table 7A.2.2.3-2: SI combination 2/3/4 scheduling (SIB2-NB + SIB3-NB + SIB4/5/14-NB)
SI
Window
K
0
1
2
3
SFN = K
4 5 6
7
8
9
0
1
2
SFN = K + 1
3 4 5 6
7
8
9
0
1
2
SFN = K + 2
3 4 5 6
7
8
9
0
1
2
SFN = K + 3
3 4 5 6
...
0
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
136
140
SI-1
SI-2
SI-3
SI-1
SI-2
SI-3
SI-1
...
With
NPBCH
7A.2.3
NPSS
NSSS
SIB1-NB
SI-1
SI-2
SI-3
System information modification
According to TS 36.331 [19] for normal DRX the modification period for change of system information is
ModificationPeriod = modificationPeriodCoeff * defaultPagingCycle
(modificationPeriodCoeff, defaultPagingCycle are given by SIB signalling).
Editor's note: eDRX is FFS
TTCN implementation is responsible to wait long enough to ensure that the UE has acquired the new system
information. With modificationPeriodCoeff=n32 and defaultPagingCycle=rf128 this means that TTCN needs to wait
more than 40s to be sure that the UE has got the change.
As working assumption it is sufficient to schedule just one paging message or one direct indication in a modification
period to indicate change of system information in the next modification period.
7A.3
Search space configurations
There are 3 kinds of search spaces in NB-IoT (TS 36.213 [30] clause 16.6):
-
Type1-NPDCCH common search space (Type1CSS): Paging
-
Type2-NPDCCH common search space (Type2CSS): Random access
-
NPDCCH UE-specific search space (UESS): UL grants and DL assignments for UE in connected mode
The search spaces define in which time windows the network may schedule DL assignments and UL grants.
ETSI
7
8
9
3GPP TS 36.523-3 version 13.2.0 Release 13
177
ETSI TS 136 523-3 V13.2.0 (2017-03)
Scheduling of DL assignments and UL grants is not possible in subframes occupied by system information or
synchronisation signals or in subframes outside the respective search space.
-
Timing of NB-IoT conformance test cases strongly depends on the system information scheduling (see clause
7A.2.2) and the search space configurations described in this clause.
In addition it is the responsibility of the SS to determine the exact timing for scheduling of DL assignments and UL
grants.
Table 7A.3-1 shows the relevant parameters for search space calculations.
Table 7A.3-1: Parameters for search space calculations
Rmax
Type1CSS
Type2CSS
UESS
Type1CSS
Type2CSS
UESS
Type1CSS
Type2CSS
UESS
Type1CSS
Type2CSS
UESS
Type1CSS
G
αoffset
T
R
Type2CSS
UESS
7A.3.1
configured in SIB2-NB (PCCH-Config-NB-r13)
configured in SIB2-NB (NPRACH-Parameters-NB-r13)
configured in RadioResourceConfigDedicated-NB-r13 (NPDCCH-ConfigDedicated-NB-r13)
(not applicable)
configured in SIB2-NB (NPRACH-Parameters-NB-r13)
configured in RadioResourceConfigDedicated-NB-r13 (NPDCCH-ConfigDedicated-NB-r13)
(not applicable)
configured in SIB2-NB (NPRACH-Parameters-NB-r13)
configured in RadioResourceConfigDedicated-NB-r13 (NPDCCH-ConfigDedicated-NB-r13)
DRX cycle according to PCCH-Config-NB-r13.defaultPagingCycle-r13
search space cycle: Rmax * G
search space cycle: Rmax * G
depends on Rmax and the "DCI subframe repetition number" in the DCI format N2 as shown in
TS 36.213 [30] table 16.6-2
depends on Rmax and the "DCI subframe repetition number" in the DCI format N1 as shown in
TS 36.213 [30] table 16.6-3
depends on Rmax and the "DCI subframe repetition number" in the DCI format N0/N1 as shown
in TS 36.213 [30] table 16.6-1
Type1CSS - Paging
For NB-IoT the same calculations for paging are applied as for WB-E-UTRA (TS 36.304 [14] clause 7), but in contrast
to WB-E-UTRA the paging does not happen at the paging occasion itself, but the Type1-NPDCCH common search
space starts at the paging occasion according to TS 36.213 [30] clause 16.6: DCI with format N2 is sent out on
NPDCCH from the next suitable subframe onward (starting at the paging occasion).
As for WB-E-UTRA the paging occasion is calculated by TTCN and provided to SS as timing information of the
system request. The SS shall schedule the DCI and the corresponding paging message (if any) according to the given
configuration of the Type1CSS, PCCH configuration and according to the rules provided by core specifications (mainly
TS 36.213 [30] clause 16).
7A.3.2
Type2CSS – Random access
In principle the same considerations can be applied as for the UESS (see below).
7A.3.3
UESS
Taking into account the SIB scheduling as described in clause 7A.2 and applying parameters for the UESS as per TS
36.508 [3] UESS configuration results in
Table 7A.3.3-1: Parameters for UESS
Rmax
G
αoffset
T
R
16
4
0
64
2
according to TS 36.508 [3] table 8.1.6.3-3
according to TS 36.508 [3] table 8.1.6.3-3
according to TS 36.508 [3] table 8.1.6.3-3
Rmax * G
according to DCI subframe repetition number in TS 36.508
[3] Table 8.1.3.6.1.2-2 and parameters as above
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
ETSI TS 136 523-3 V13.2.0 (2017-03)
178
according to TS 36.213 [30] clause 16.6
the search spaces start at k0 = 0, 64, 128, 192, 256, ...
the candidates within a search space start at b = R * u = 0, 2, 4, 6, 8, 10, 12, 14.
Table 7A.3.3-2: Scheduling of UESS
K
SFN = K
SFN = K + 1
SFN = K + 2
SFN = K + 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
...
...
0
4
8
12
16
20
24
28
32
36
40
44
48
52
56
60
64
68
72
76
...
With
NPBCH
NPSS
NSSS
SIB1-NB
search space candidate 0
SI-1
SI-2
SI-3
search space candidates 1..7
NOTE 1: Depending on SS configuration in general the first search space candidate can be used for the
transmission of the DCI. Therefore the first search space candidate is highlighted in table 7A.3.3-2.
7A.4
Timing considerations
Based on SIB scheduling and search space configuration as described in the previous clauses timing considerations are
made as below.
7A.4.1
Random access procedure
Details regarding random access procedure in NB-IoT are specified in clause 16.3 of TS 36.213 [30] and clause 5.1 of
TS 36.321 [16]. The timing of a random access procedure in NB-IoT is illustrated in table 7A.4.1-1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
179
Table 7A.4.1-1: Timing of random access procedure
...
...
...
...
RACH
pream
ble
← tdelay1 →
...
RAR
with
UL
grant
DCI
format
N1
...
...
Type2 CSS
←tDCI→
← tdelay2 →
step
1
←tRAR→
← tdelay3 →
step 2
...
Type2 CSS
Msg3
...
DCI
format
N0/1
←tMsg3
→
← tdelay4 →
←tDCI→
step
3
← tdelay5 →
step 4
with
steps 1-4
tdelay1
tDCI
tdelay2
tRAR
tdelay3
tMsg3
tdelay4
tdelay5
Random access procedure according to TS 36.300 [69] clause 10.1.5.1:
step 2: RAR is addressed to RA-RNTI
step 3: Msg3 contains either a CCCH SDU (a) or the C-RNTI (b)
step 4: a) temporary C-RNTI based contention resolution (DL assignment for Msg4)
b) C-RTNI based contention resolution (UL grant)
NOTE:
According to TS 36.213 [30] clause 16.5.1, Table 16.5.1-4 and clause 16.4.1, Table 16.4.1-5 the DCI for step 4 is
sent on NPDCCH in the Type2 common search space
depends on Type1-CSS configuration, start of RA response window according to TS
≥ 3ms (but up to ≥ 50ms)
36.321 [16] clause 5.1.4 and when the RACH preamble happens
for Rmax = 16 and DCI subframe repetition number = 0 (TS 36.213 [30] clause 16.6)
≥ 2ms
scheduling delay according to DCI (TS 36.213 [30] clause 16.4.1 and table 16.4.1-1)
≥ 4ms
depending on TBS and number of repetitions (TS 36.213 [30] clause 16.4.1)
≥ 1ms
scheduling delay according to RAR grant (TS 36.213 [30] clause 16.3.3)
≥ 12ms
depending on MSC index and number of repetitions according to RAR grant; the TBS
≥ 1ms
is 88 bits in all cases (TS 36.213 [30] clause 16.3.3)
delay before the UE monitors NPDCCH again (TS 36.213 [30] clause 16.6)
≥ 3ms
depending on whether UL or DL transmission follows, see clause 7A.4.2 and 7A.4.3
≥ 13ms
NOTE 1: In addition to the delay in table 7A.4.1-1 there is further delay caused by PBCH, NPSS, NSSS, SI
transmissions.
NOTE 2: Assuming a search space configuration as per clause 7A.3 in general a random access procedure needs
more than two search space cycles.
7A.4.2
Uplink transmissions
Table 7A.4.2-1: Timing of uplink transmissions
...
...
...
DCI
format
N0
←tDCI1→
ULSCH
← tdelay1 →
←tData→
ACK/
NACK
← tdelay2 →
...
←tDCI2→
with
tDCI1
tdelay1
tData
≥ 2ms
≥ 8ms
≥ 1ms
tdelay2
tDCI2
≥ 3ms
≥ 2ms
for Rmax = 16 and DCI subframe repetition number = 0 (TS 36.213 [30] clause 16.6)
according to TS 36.213 [30] table 16.5.1-1
depending on TBS and number of repetitions (TS 36.213 [30] clause 16.5.1 and TS
36.211 Table 10.1.2.3-1) (NOTE 4)
according to TS 36.213 [30] clause 16.5.2
(same as tDCI1)
NOTE 1: In addition to the delay in table 7A.4.2-1 there is further delay caused by PBCH, NPSS, NSSS, SI
transmissions.
ETSI
..
.
..
.
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
180
NOTE 2: Assuming a search space configuration as per clause 7A.3 in general an uplink transmission takes one
search space cycle.
NOTE 3: Even when in case of necessary UL re-transmission the grant for the re-transmission is sent immediately
using adaptive HARQ NACK it is hardly predictable how many search space cycles the complete
successful transmission takes. Nevertheless one re-transmission may still be finished in the same search
space cycle in which the initial UL has been scheduled.
NOTE 4: For single tone ( N scRU = 1 ) according to TS 36.213 [30] Table 16.5.1.2-1 the maximum value of ITBS is 10.
Therefore according to table 16.5.1.2-2 the maximum grant of 1000 bits requires at least IRU = 5 i.e. tData ≥
6ms for maximum grant.
7A.4.3
Downlink transmissions
Table 7A.4.3-1: Timing of downlink transmissions
...
...
...
DCI
format
N1
←tDCI→
DLSCH
← tdelay1 →
←tData→
ACK/NACK
← tdelay2 →
...
← tACK/NACK →
with
tDCI
tdelay1
tData
tdelay2
tACK/NACK
≥ 2ms
≥ 4ms
≥ 1ms
≥ 12ms
≥ 2ms
for Rmax = 16 and DCI subframe repetition number = 0 (TS 36.213 [30] clause 16.6)
scheduling delay according to DCI (TS 36.213 [30] clause 16.4.1 and table 16.4.1-1)
depending on TBS and number of repetitions (TS 36.213 [30] clause 16.4.1)
depending HARQ-ACK resource allocation according to TS 36.213 [30] clause 16.4.2
multiples of 2ms according to TS 36.211 [35] Table 10.1.2.3-1; depending on number of
repetitions configured by RRC signalling (NPUSCH-ConfigCommon-NB-r13, NPUSCHConfigDedicated-NB-r13; NRep ≥ 1)
NOTE 1: In addition to the delay in table 7A.4.3-1 there is further delay caused by PBCH, NPSS, NSSS, SI
transmissions.
NOTE 2: Assuming a search space configuration as per clause 7A.3 in general a downlink transmission takes one
search space cycle.
NOTE 3: Assuming a search space configuration as per clause 7A.3 in case of a HARQ NACK from the UE a retransmission needs to be scheduled in the next search space cycle (as even when the DL transmission has
been scheduled using the first search space candidate, at the point in time the SS detects the NACK there
is no search space candidate in the current search space cycle anymore).
7A.4.4
Half-duplex mode
According to TS 36.211 [35] for NB-IoT only type-B half-duplex FDD operation is supported (clause 10.2.2.3) in
which according to clause 4.1 the UE cannot transmit and receive at the same time.
In addition in clause 16.6 of TS 36.213 [30] there are further rules further restricting the timing of UL/DL transmissions
summarised in table 7A.4.4-1and table 7A.4.4-2.
Table 7A.4.4-1: Uplink transmissions
n
DCI
Format
N0
n+1
...
n+k-1
n+k
n1
n1+1
NPUSCH
transmission
UL-SCH transmission: NPDCCH not monitored by the UE
ETSI
n1+2
n1+3
ACK/NA
CK
(NPDCC
H)
3GPP TS 36.523-3 version 13.2.0 Release 13
181
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 7A.4.4-2: Downlink transmissions
n
n+1
n+k-1
DCI
Format
N1
NPDSCH
transmission
n+k
n1
n1+1
n1+2
NPUSCH Format 2:
ACK/NACK
DL-SCH transmission: NPDCCH not monitored by the UE
7A.4.5
Conclusions
Based on the system information scheduling as in clause 7A.2 and search space configuration as in clause 7A.3 the
following conclusions are made:
-
Random access procedure:
After detection of the random access preamble steps 2-4 of the random access procedure take at least two search
space cycles.
-
Uplink and downlink transmissions:
In general an UL or DL transmission takes one search space cycle and UL/DL transmission are mutually
exclusive, i.e. a search space cycle can be either for UL or for DL.
7A.5
Scheduling requests and scheduling of UL grants
As there is no NPUCCH in NB-IoT the UE cannot directly indicate scheduling requests to the network. Instead
according to TS 36.321 [16] clause 5.4.4 the UE starts with a RACH procedure, unless an SR-ProhitTimer is configured
by RRC signalling.
NOTE 1: It seems not to be reliable that, when no SR-ProhitTimer is configured, the UE will use an UL grant being
scheduled in advance.
NOTE 2: It seems not to be reliable that a UE uses an UL grant addressed with C-RNTI when it has already started
a RACH procedure and is waiting for the RA response being addressed by the RA-RNTI. Furthermore
there is no core spec reference about the UE to abort the RACH procedure in this case.
-
7A.5.1
In terms of UL scheduling there are two modes for the UE in RRC connected mode: RACH
procedure mode and polling mode.
RACH procedure mode
UL grant scheduling is triggered by a RACH procedure and the subsequent evaluation of BSRs. There is no explicit
scheduling of UL grants in advance.
The SS assigns UL grants according to RACH procedure configuration and common MAC configuration (DCI format
N0 configuration of UL grants).
NOTE:
7A.5.2
In case of uncorrelated UL and DL transmissions there may be race conditions resulting in the UE having
started a random access procedure already when the SS schedules the DL transmission. In this case the
UE may not read the DL assignment anymore and therefore not receive the DL data.
Polling mode
SR-ProhibitTimer (logicalChannelSR-Prohibit-r13 according to release 13 ASN.1, TS 36.331 [19]) is configured at the
UE (for each logical channel) and the SS polls the UE with UL grants: When the UE has UL data pending it will use a
given grant; the UE in connected mode will not start any RACH procedure while SR-ProhibitTimer is running.
The SS gets configured with periodic UL grants to be assigned to the UE: grant size, periodicity, total number of grants.
7A.6
Scheduling requirements
As conclusion of the above timing and scheduling considerations this clause defines SS requirements about how to
schedule UL grants and DL assignments.
ETSI
n1+3
3GPP TS 36.523-3 version 13.2.0 Release 13
7A.6.1
182
ETSI TS 136 523-3 V13.2.0 (2017-03)
Random access procedure
The SS gets configured with:
-
configuration of the Type2 common search space (Rmax, G, αoffset)
-
Type 2 common search space candidate to schedule RAR
-
Type 2 common search space candidate to schedule DL assignment or UL grant at step 4 of the random access
procedure
-
UL grant to be provided in RAR
-
DCI for DL assignment of Msg4 in case of temporary C-RNTI based contention resolution
-
For C-RNTI based contention resolution (RACH procedure mode):
DCI for UL grants to be used at step 4 of the random access procedure and for any subsequent UL transmissions
(if any)
The SS shall:
-
when it has detected a RACH preamble, wait until start of the next Type2 common search space within the RA
response window and schedule the Random Access Response containing the UL grant for Msg3 by using the
Type2 common search space candidate as configured
-
after it has received Msg3, schedule a DL assignment or UL grant in the next Type2 common search space by
using the search space candidate as configured
-
in case of RACH procedure with C-RNTI based contention resolution (i.e. UE in connected mode), check
whether the UL MAC PDU sent at step 4 of the random access procedure contains a BSR element indicating that
the UE needs more UL grant. If so, the SS shall use the ACK/NACK response corresponding to step 4's UL
transmission as specified in clause 16.5.2 of TS 36.213 [30] to schedule another UL grant as configured at the SS
( the SS shall not do any dynamic calculation for the UL grant based on the details of the BSR);
this shall be repeated until the UE does not indicate need for further UL grant anymore.
Pending DL transmissions shall be postponed until after all UL data has been received.
NOTE: This rule applies for RACH procedure mode according to clause 7A.5.1.
⇒
-
in case of RACH procedure with C-RNTI based contention resolution (i.e. UE in connected mode), not use any
adaptive HARQ ACK to schedule a DL transmission.
7A.6.2
Downlink transmissions
The SS gets configured with:
-
configuration of the UE specific search space (Rmax, G, αoffset)
-
search space candidate to be used for DL assignments within the search space
-
DCI to be used for DL assignments:
normal mode:
transport block size, ITBS and ISF to be automatically determined by the SS
explicit mode: DCI with ITBS, ISF provided by TTCN
When the SS gets a message from TTCN to be sent in DL it shall:
-
when the timing info is now, schedule the DL assignment in the next search space not being used for HARQ retransmissions.
-
when a specific timing info is given, schedule the DL assignment by using the configured search space candidate
in the next NPDCCH period starting at or after the given point in time. If for any reason there is an ongoing UL
or DL transmission so that the UE may not monitor the NPDCCH, the SS shall raise an error.
NOTE: The search space candidate is given as index (0..7) in the configuration of the UE specific search space
corresponding to u in the calculations of clause 16.6 in TS 36.213 [30].
-
when timing info is "now" and a previous DL transmission is still pending, schedule the DL assignment of the
2nd message in the search space starting after the HARQ ACK of the 1st message.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
183
-
when e.g. an RRC message containing user data needs to be segmented by the RLC layer transmission of the
resulting transport blocks shall be scheduled in consecutive search space cycles and the given timing info is
applied for the first transmission.
-
when TBS, ITBS and ISF shall be determined by the SS, use the mapping according to table 7A.6.2-1, otherwise
use ITBS and ISF as provided by TTCN.
Table 7A.6.2-1: DL Resource allocation in normal mode
amount of pending
DL data (bits): NData
ITBS
(NOTE)
ISF
(NOTE)
NData ≤ 16
16 < NData ≤ 24
24 < NData ≤ 32
32 < NData ≤ 40
40 < NData ≤ 56
56 < NData ≤ 72
72 < NData ≤ 88
88 < NData ≤ 104
104 < NData ≤ 120
120 < NData ≤ 136
136 < NData ≤ 144
144 < NData ≤ 176
176 < NData ≤ 208
208 < NData ≤ 224
224 < NData ≤ 256
256 < NData ≤ 296
296 < NData ≤ 328
328 < NData ≤ 392
TBS to be
chosen by the
SS
16
24
32
40
56
72
88
104
120
136
144
176
208
224
256
296
328
392
0
1
2
3
4
5
6
7
8
9
10
6
4
4
8
9
10
8
0
0
0
0
0
0
0
0
0
0
0
1
2
2
1
1
1
2
392 < NData ≤ 456
456 < NData ≤ 472
472 < NData ≤ 504
504 < NData ≤ 536
456
472
504
536
9
7
10
8
2
3
2
3
536 < NData ≤ 616
616
9
3
Comment
TBS=152 skipped as it would require ISF=5 (NOTE 1)
NOTE 2
NOTE 2
NOTE 2
TBS=344 skipped as it would require ISF=7 (NOTE 1)
TBS=376 skipped as it would require ITBS=11 (NOTE
2)
TBS=408 skipped as it would require ISF=5 (NOTE 1)
TBS=424 skipped as it would require ISF=4 (NOTE 1)
TBS=440 skipped as it would require either ITBS=12
(NOTE 2) or ISF=6 (NOTE 1)
)
TBS=552 skipped as it would require ISF=6 (NOTE 1)
TBS=568 skipped as it would require ISF=7 (NOTE 1)
TBS=584 skipped as it would require either ITBS=11
(NOTE 2) or ISF=4 (NOTE 1)
TBS=600 skipped as it would require ISF=5 (NOTE 1)
NOTE 2
616 < NData
680
10
3
NOTE 1: According to TS 36.213 [30] Table 16.4.1.5.1-1
NOTE 2: According to TS 36.213 [30] clause 16.4.1.5.1 for operationModeInfo set to ‘00’ or ‘01’ (Inband Operation Mode)
ITBS is 0 ≤ ITBS ≤ 10
-
ISF ≤ 3 for all DL transmission (i.e. a DL transmission needs not more than 4 NB-IoT DL subframes, which is
needed for maximum TBS of 680)
7A.6.3
Periodic uplink grants
Periodic scheduling of UL grants applies for polling mode according to clause 7A.5.2, i.e. in general the UE is
configured with SR-ProhibitTimer(s) to be prevented from triggering RACH procedures in connected mode.
The SS gets configured with:
-
configuration of the UE specific search space (Rmax, G, αoffset)
-
search space candidate to be used for UL grants within the search space
-
configuration of grant scheduling:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
184
-
DCI of the UL grants
-
number of UL grants to be scheduled: one grant only, several, continuous
-
periodicity: every search space, every 2nd search space, ...
When the SS gets configured for periodic scheduling of uplink grants, the SS shall:
-
start UL grant scheduling with the next available search space candidate as configured for the UE specific search
space after the given timing information (which can be "now" or a specific point in time).
-
not give any additional grants base on buffer status reporting by the UE.
-
not use the adaptive HARQ ACK to schedule another transmission.
-
when DL transmission is scheduled, postpone any UL grant which would be scheduled for the same search space
by one search space cycle.
NOTE: the periodicity is related to beginning of the UL grant scheduling i.e. independent from whether or not a
single grant is postponed.
Table 7A.6.3-1 gives an example for periodic UL grant scheduling for a periodicity of every 3rd search space cycle: at
UESS cycle 7 the UL grant is postponed to cycle 8 due to DL transmission.
Table 7A.6.3-1: Periodic UL grant scheduling – Example for UL and DL transmissions
...
UESS
cycle
1
UL grant
configuration
UL
7A.6.4
NOTE:
UESS
cycle
2
UESS
cycle
3
UESS
cycle
4
DL
UL
UESS
cycle
5
UESS
cycle
6
UESS
cycle
7
UESS
cycle
8
DL
UL
UESS
cycle
9
UESS
cycle
10
...
UL
HARQ re-transmissions
HARQ re-transmission are considered being rare in a RF cabled test environment. Nevertheless
depending on test requirements HARQ re-transmissions may be tolerated at least for some test cases.
The SS shall report HARQ errors to TTCN if HARQ error reporting is configured by TTCN.
7A.6.4.1
Uplink
When the SS needs to request a re-transmission in uplink, it shall use adaptive HARQ ACK/NACK to indicate the
NACK to the UE. The re-transmission shall be scheduled immediately by using the ACK/NACK response
corresponding to the UL transmission as specified in clause 16.5.2 of TS 36.213 [30] independent from any UL grant
scheduling.
⇒
If the re-transmission is not successfully finished within the search cycle in which the transmission has been started, i.e.
a second search space cycle is needed to complete the UL transmission, the SS shall:
-
if a DL transmission is pending with timing info "now":
postpone the DL transmission
-
if DL transmission is scheduled explicitly for the second search space cycle:
raise an error
-
if an UL grant is scheduled for the second search space cycle:
postpone this UL grant for one cycle.
7A.6.4.2
Downlink
When the UE indicates a HARQ NACK to the SS for a DL transmission in search space cycle N, the SS shall reschedule the DL assignment in search space cycle N+1.
The SS shall:
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
185
ETSI TS 136 523-3 V13.2.0 (2017-03)
-
if a another DL transmission is pending with timing info "now":
postpone the DL transmission
-
if DL transmission is scheduled explicitly for the second search space cycle:
raise an error
-
if an UL grant is scheduled for the second search space cycle:
postpone this UL grant for one cycle.
Depending on test requirements, the SS may get configured to generate a CRC error for a DL transmission
corresponding to a configured DCI. In this case the DCI may be reconfigured before the retransmission happens.
Therefore the SS shall not re-use the DCI of the initial transmission but shall consider a possible reconfiguration of the
DCI.
7A.6.5
Timing info for UL messages
The SS shall provide the H-SFN, SFN and subframe number of the subframe corresponding to the first RU of the
NPUSCH transmission. It is up to TTCN implementation to derive other timing information if needed (e.g. the start of
the corresponding search space).
NOTE:
7A.6.6
E.g. in case of IP data a layer 3 message carrying the user data on the control plane may be segmented by
the RLC layer. In this case the timing info shall be related to the first segment.
Uplink time alignment
As for legacy LTE the SS can be configured to periodically send Timing Advance Commands to the UE to prevent the
UE from starting a RACH procedure due to expiry of the Time Alignment Timer. When the Time Alignment Timer at
the UE is set to infinity, the SS is configured not to do any automatic transmission of Timing Advance Commands.
7A.7
RRC Connection Release Sequence
As for legacy LTE according to TS 36.331 [19], clause 5.3.8.3, after reception of the RRCConnectionRelease the UE
may either wait 60ms or for indication of acknowledgement from lower layer. Furthermore according to TS 36.331
[19], clause 5.3.12, upon leaving RRC_CONNECTED the UE resets layer 2.
-
As the UE resets layer 2 anyway after 60ms there is no need to provide the UE with UL grants for
layer 2 signalling (e.g. RLC ACK).
Assuming search space cycles of 64ms as described in clause 7A.3 and with a given search space cycle N starting at
time T being at least 100ms in advance, TTCN scheduled schedules the RRC Connection Release Sequence as
1. At T:
Start of search space cycle N:
Send RRCConnectionRelease, stop UL grants.
2. At T + 64ms:
Start of search space cycle N+1:
Release security (optional; only when security has been configured).
3. At T + 80ms:
Release SRBs and DRBs (if configured).
4. At T + 96ms:
(Re-) configure SRBs.
5. Delay of 840ms (NOTE)
NOTE:
The delay 840ms is chosen to ensure the UE is re-camping on the cell and has read relevant system
information, MIB, SIB1, SIB2 and all other SIs.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
7A.8
186
ETSI TS 136 523-3 V13.2.0 (2017-03)
DL CCCH Message and Contention Resolution MAC
Control Element transmission in one MAC PDU or in
separate MAC PDUs
Regarding DL RRC PDU (e.g. RRC Connection Setup) being contained in Msg4 of the random access procedure or
being sent in a separate DL message the same principles apply as described in clause 7.19 for legacy LTE.
7A.9
Cell Configuration
7A.9.1
Cell Power Change
Please refer to clause 7.4.2
7A.9.2
Timing Parameters of Cells
To reduce interference for cells with same frequency the timing for these cells is shifted to avoid that NPSS and NSSS
are transmitted at the same time. This is done by TS values in multiples of 30720 (one subframe).
Table 7A.9.2-1 shows timing parameters for cells with frequencies according to Table 8.1.4.2-1 in TS 36.508 [3], Table
7A.9.2-2 shows timing parameters for cells with frequencies according to Table 8.1.4.2-4 in TS 36.508 [3], Table
7A.9.2-3 shows timing parameters for cells with frequencies according to Table 8.1.4.2-5 in TS 36.508 [3];
cells with same frequency are marked with the same colour.
Table 7A.9.2-1: Timing parameters of simulated NB-IoT cells – Batch1
Cell ID
SFN offset
Tcell (Ts)
Frequency
(Table 8.1.4.2-1 in TS 36.508 [3])
Ncell 1
Ncell 2
Ncell 3
Ncell 4
Ncell 6
Ncell 10
Ncell 11
Ncell 12
Ncell 13
Ncell 14
Ncell 23
0
124
257
1000
657
129
957
1015
890
680
383
0
184320
150897
61440
524
43658
92160
181617
31244
300501
212337
f1
f1
f2
f1
f3
f5
f1
f2
f3
f4
f2
Table 7A.9.2-2: Timing parameters of simulated NB-IoT cells – Batch2 in same PLMN
Cell ID
SFN offset
Tcell (Ts)
Frequency
(Table 8.1.4.2-4 in TS 36.508 [3])
Ncell 50
Ncell 51
Ncell 52
Ncell 53
Ncell 61
0
124
257
1000
471
0
30720
150897
61440
31244
f1
f1
f2
f1
f2
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
187
Table 7A.9.2-2: Timing parameters of simulated NB-IoT cells –Batch2 in different PLMNs
Cell ID
SFN offset
Tcell (Ts)
Frequency
(Table 8.1.4.2-5 in TS 36.508 [3])
Ncell 50
Ncell 51
Ncell 52
Ncell 53
Ncell 54
Ncell 55
Ncell 56
Ncell 57
Ncell 58
Ncell 59
Ncell 60
Ncell 61
Ncell 62
Ncell 63
0
124
257
1000
752
957
1015
890
680
383
562
471
595
728
0
30720
61440
92160
32047
631
31351
127200
1327
157920
188640
122880
153600
184320
f1
f1
f1
f1
f2
f2
f2
f3/f1
f4/f2
f3/f1
f3/f1
f1
f1
f1
The Random Access Response Timing Advance is set to 0.
7A.9.3
Configuration of Multi-Cell Environment
Please refer to clause 7.4.5
7A.10 Timers and Timing Restrictions
Please refer to clause 7.8
7A.11 Error Indication
The SS shall raise an error indication in all cases of system errors or other unforeseen events at lower layers.
In addition the SS may get configured for HARQ error reporting, e.g. in cases when HARQ retransmissions would have
unacceptable impact on the test behaviour.
Any error indication results in an "inconc" verdict in TTCN.
8
External Function Definitions
The following external functions are required to be implemented by the SS.
Name
Description
Parameters
Return Value
TTCN-3 External Function
fx_KeyDerivationFunction
Hashing function for Hashing algorithms as defined in TS 33.401 [24]
SHA-256 encoding algorithm is used as KEY Description Function
KDF
KDF_HMAC_SHA_256 (no other KDF defined yet)
Key
bit key
String
string being constructed acc. to TS 33.401 [24], annex A
256 bit derived key
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Name
Description
Parameters
Return Value
Name
Description
Parameters
Return Value
Name
Description
Parameters
Return Value
Name
Description
Parameters
Return Value
Name
Description
Parameters
Return Value
188
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 External Function
fx_NasIntegrityAlgorithm
Apply integrity protection algorithm on a given octetstring
NAS PDU
octetstring according to TS 24.301 [21], clause 4.4.3.3 this
shall include octet 6 to n of the security protected NAS
message, i.e. the sequence number IE and the NAS message
IE
Integrity Algorithm
3 bits as defined in TS 24.301 [21], clause 9.9.3.23
KNASint
Integrity key
NAS COUNT
as documented in TS 24.301
BEARER Id
fix value ('00000'B) acc. TS 33.401 [24], clause 8.1
Direction
UL: 0
DL: 1
(acc. to TS 33.401 [24], clause B.1)
Message Authentication Code (4 octets)
TTCN-3 External Function
fx_NasCiphering
Apply ciphering on a given octetstring
NAS PDU
octetstring
Ciphering Algorithm
3 bits as defined in TS 24.301 [21], clause 9.9.3.23
KNASenc
Ciphering Key
NAS COUNT
as documented in TS 24.301
BEARER Id
fixed value ('00000'B) acc. TS 33.401 [24], clause 8.1
ciphered octet string
TTCN-3 External Function
fx_NasDeciphering
Apply deciphering on a given octetstring
ciphered NAS PDU
octetstring
Ciphering Algorithm
3 bits as defined in TS 24.301 [21], clause 9.9.3.23
KNASenc
Ciphering Key
NAS COUNT
as documented in TS 24.301 [21]
BEARER Id
fixed value ('00000'B) acc. TS 33.401 [24], clause 8.1
deciphered octet string
TTCN-3 External Function
fx_AsIntegrityAlgorithm
Apply integrity protection algorithm on a given octetstring
PDCP PDU
octetstring
Integrity Algorithm
3 bits as defined in TS 33.401 [24]
KRRCint
Integrity key
PDCP COUNT
octetstring, length 4
BEARER Id
the value of the DRB identity minus one
Direction
UL: 0
DL: 1
(acc. to TS 33.401 [24], clause B.2)
Message Authentication Code (4 octets)
TTCN-3 External Function
fx_AsCiphering
Apply ciphering on a given octetstring
SDU
octetstring
Ciphering Algorithm
3 bits as defined in TS 33.401 [24]
KRRCenc
Ciphering Key
PDCP COUNT
octetstring, length 4
BEARER Id
the value of the DRB identity minus one
ciphered octet string
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Name
Description
Parameters
Return Value
Name
Description
Parameters
189
ETSI TS 136 523-3 V13.2.0 (2017-03)
TTCN-3 External Function
fx_AsDeciphering
Apply deciphering on a given octetstring
ciphered SDU
octetstring
Ciphering Algorithm
3 bits as defined in TS 33.401 [24]
KRRCenc
Ciphering Key
PDCP COUNT
octetstring, length 4
BEARER Id
the value of the DRB identity minus one
deciphered octet string
TTCN-3 External Function
fx_GetSystemTime
Function to get the system time: Implementation is based on C standard library (time.h)
p_Struct_tm (out)
p_Struct_tm returns local system time equivalent to "struct tm"
as defined for C standard library (time.h or ctime):
type record Struct_tm_Type {
integer tm_sec, // seconds after the minute
// (0..61; see NOTE)
integer tm_min, // minutes after the hour (0..59)
integer tm_hour, // hours since midnight (0..23)
integer tm_mday, // day of the month (1..31)
integer tm_mon, // months since January (0..11)
integer tm_year, // years since 1900
integer tm_wday, // days since Sunday (0..6)
integer tm_yday, // days since January 1 (0..365)
integer tm_isdst // Daylight Saving Time flag
};
NOTE: tm_sec is generally 0-59. Extra range to accommodate
for leap seconds in certain systems
C implementation:
time_t v_Now = time(NULL);
struct tm *v_Tm = localtime(&v_Now);
p_TimezoneInfo (out)
p_TimezoneInfo returns the difference (in seconds) between
the UTC time (GMT) and the local time (integer value);
C implementation:
int timezone =
(int)difftime(mktime(gmtime(&v_Now)), v_Now);
NOTE:
p_TimezoneInfo does not consider daylight saving e.g. it is
always 3600 for CET independent of summer/winter
Return Value
None
Name
Description
Parameters
Return Value
TTCN-3 External Function
fx_MD5_Hex
external function to calculate the MD5 Message-Digest Algorithm according to RFC 1321
Data
octetstring
octetstring
Name
Description
Parameters
Return Value
TTCN-3 External Function
fx_CalculateCRC32
Cyclic Redundancy Check calculation according to ITU-T Recommendation V.42 of CRC32 algorithm.
p_Input
bitstring
bitstring, length 32
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
9
ETSI TS 136 523-3 V13.2.0 (2017-03)
190
IXIT Proforma
This partial IXIT proforma contained in the present document is provided for completion, when the related Abstract
Test Suite is to be used against the Implementation Under Test (IUT).
Text in italics is a comment for guidance for the production of an IXIT, and is not to be included in the actual IXIT.
The completed partial IXIT will normally be used in conjunction with the completed ICS, as it adds precision to the
information provided by the ICS.
9.1
E-UTRAN PIXIT
Table 9.1-1: Common PIXIT
Parameter Name
px_AccessPointName
px_AttachTypeTested
px_eAuthRAND
px_EllipsoidPointWithAltitude
px_HorizontalVelocity
px_eJapanMCC_Band6
px_PWS_CB_DataPage1
px_PWS_CB_DataPage2
px_PWS_CB_DataPage3
px_PWS_CB_DataPage4
px_PWS_CB_DataCodingSche
me
px_ETWS_DigitalSignature
px_IPv4_Address1_UE
px_IPv4_Address2_UE
px_IPv4_Address2a_UE
px_IPv4_Address1_NW
px_Ipv4_Address2_NW
px_IPv4_Address1_RemoteUE
px_IPv4_Address2_RemoteUE
px_Ipv4_Address_HomeAgent
px_IPv6_Address1_UE
px_IPv6_Address2_UE
Parameter Type
Default Value
Supported
Values
Description
Access Point Name, as defined
in TS 23.003 [48] and used in
TS 24.008 [20], clause 10.5.6.1
octetstring
EPS_ATTA
EUTRA_ATTAC
Attach Type to be tested, if UE
EPS_ATTACH_ON CH_ONLY,
H_TESTED_Typ
supports both pc_Attach and
LY
COMBINED
e
pc_Combined_Attach
_ATTACH
oct2bit(‘A3DE0C6
B128_Type
D363E30C364A40
Random Challenge
78F1BF8D577’O)
Ellipsoid Point With Altitude value
to be provided in Update UE
O8_Type
location information (see 36.509
cl. 6.12)
Horizontal Velocity value to be
O3_Type
provided in Update UE location
information (see 36.509 cl. 6.12)
Japan MCC code to be used for
Band 6. The same value will be
NAS_Mcc
‘442’H
used for E-UTRA and Inter-RAT
cells. Type is different to that
defined in TS 34.123-3 [7]
ETWS or CMAS Page 1 warning
charstring
data message
ETWS or CMAS Page 2 warning
charstring
data message
ETWS or CMAS Page 3 warning
charstring
data message
ETWS or CMAS Page 4 warning
charstring
data message
ETWS or CMAS data coding
scheme of the alphabet/coding
bitstring
and the applied language [see
TS 23.041]
O43_Type
ETWS Digital Signature
charstring
IPv4 Address connected to PDN1
charstring
IPv4 Address connected to PDN2
IPv4 Address connected to
charstring
PDN2a
charstring
IPv4 Gateway Address in PDN1
charstring
Ipv4 Gateway Address in PDN2
IPv4 Address of remote UE
charstring
connected to PDN1
IPv4 Address of remote UE
charstring
connected to PDN2
charstring
Ipv4 Home Agent Address
charstring
IPv6 Address connected to PDN1
charstring
IPv6 Address connected to PDN2
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Parameter Name
Parameter Type
191
Default Value
px_IPv6_Address2a_UE
charstring
px_IPv6_Address1_NW
px_Ipv6_Address2_NW
charstring
charstring
px_IPv6_Address1_RemoteUE
charstring
px_IPv6_Address2_RemoteUE
charstring
px_Ipv6_Address_HomeAgent
charstring
px_SMS_ChkMsgReceived
boolean
true
px_SMS_MsgFrmt
charstring
"1"
px_RATComb_Tested
px_SinglePLMN_Tested
RATComb_Test
ed_Type
SinglePLMN_Te
sted_Type
Supported
Values
Description
IPv6 Address connected to
PDN2a
IPv6 Gateway Address in PDN1
Ipv6 Gateway Address in PDN2
IPv6 Address of remote UE
connected to PDN1
IPv6 Address of remote UE
connected to PDN2
Ipv6 Home Agent Address
Whether the operator can check
an MT Short Message received
SMS message format <mode>
(see TS 27.005 [31] cl. 3.2.3).
NOTE: Default value is for text
mode. Change value to “0” to
execute tests with PDU mode.
EUTRA_UTRA
EUTRA_UT
RA,
EUTRA_GE
RAN,
EUTRA_Onl
y
This parameter represents the
network RAT capability /
preference and indicates which, if
any is supported, RAT
combination is to be tested.
MultiPLMN
SinglePLM
N,
MultiPLMN,
MultiPLMNi
nPrimaryBa
nd,
MultiPLMNi
nSecondary
Band
This parameter represents the
network capability/preference to
support multi PLMNs on the
same test Band and indicates the
preference of multi PLMNs or
single PLMN test environment.
This PIXIT shall be set to
SinglePLMN when only one
frequency is defined for the test
band.
px_UE_CS_PS_UsageSetting_
Tested
CS_PS_MODE
VOICE_CENTRIC
px_UE_PS_UsageSetting_Test
ed
PS_MODE
VOICE_CENTRIC
px_UTRAN_ModeUnderTest
UTRAN_FDD_T
DD
UTRAN_FDD
px_TestLoopModeB_Delay
O1_Type
‘5A’
px_IP_MTU_Size
integer
65535
px_UTRAN_OverlappingNotSup
integer
portedFrequencyBandMFBI
px_MFBI_UTRAN_FrequencyB
and
ETSI TS 136 523-3 V13.2.0 (2017-03)
integer
ETSI
VOICE_CE
NTRIC,
DATA_CEN
TRIC
VOICE_CE
NTRIC,
DATA_CEN
TRIC
UTRAN_FD
D,
UTRAN_TD
D
Specifies which CS/PS mode is
under test
Specifies which PS mode is
under test
Specifies which radio access
technology is being tested in
UTRAN
This parameter represents the
IP_PDU_delay to be used for UE
test loop mode B in test cases,
where long delay may be needed
e.g. because of user interaction.
MTU Size. This value is specific
to the SS.
A not supported UTRAN
frequency band that is
overlapping with a supported
band
(px_MFBI_UTRAN_FrequencyBa
nd). This PIXIT shall be set also
in accordance with the values of
the 3 PIXIT items:
px_UARFCN_D_High,
px_UARFCN_D_Mid,px_UARFC
N_L_Mid. Applied to MFBI test
case scenario.
A supported UTRAN frequency
band overlapping with
3GPP TS 36.523-3 version 13.2.0 Release 13
Parameter Name
Parameter Type
192
Default Value
ETSI TS 136 523-3 V13.2.0 (2017-03)
Supported
Values
Description
px_UTRAN_OverlappingNotSupp
ortedFrequencyBandMFBI.
Applied to MFBI test case
scenario.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
193
Table 9.1-2: E-UTRAN PIXIT
Parameter Name
Parameter Type
Default Value
px_EllipsoidPointWithAltitude_P
O8_Type
roSe_Area1
px_EllipsoidPointWithAltitude_P
O8_Type
roSe_Area2
px_EllipsoidPointWithAltitude_N
O8_Type
otProSe
px_ePrimaryBandChannelBand
width
px_ePrimaryFrequencyBand
TDD_SubframeA
1
ssignment_Type
Dl_Bandwidth_T
n25
ype
integer
1
px_eSecondaryFrequencyBand
integer
px_eSecondaryBandChannelBa
ndwidth
px_EUTRA_CA_BandCombinati
on
px_EUTRA_DC_BandCombinati
on
Dl_Bandwidth_T
ype
CA_BandCombi
nation_Type
DC_BandCombi
nation_Type
px_NAS_CipheringAlgorithm
B3_Type
001’B
px_NAS_IntegrityProtAlgorithm
B3_Type
001’B
px_eTDDsubframeConfig
2
n25
CA_1C
DC_1A-3A
CipheringAlgorit
eea1
hm_r12
IntegrityProtAlgo
px_RRC_IntegrityProtAlgorithm
eia1
rithm
MaxNumberRO
px_eMaxNumberROHC_Contex
HC_ContextSes Cs16
tSessions
sions_Type
px_RRC_CipheringAlgorithm
px_MFBI_FrequencyBand
integer
26
px_MFBI_BandChannelBandwi
dth
Dl_Bandwidth_T
ype
n25
px_OverlappingNotSupportedFr
equencyBand_MFBI
integer
27
px_OverlappingSupportedFrequ
integer
encyBand_MFBI
26
ETSI
Supported
Values
Description
Ellipsoid Point With Altitude value
corresponding to geographical
area 1 provided in
EFPROSE_RADIO_COM to be provided
in Update UE location information
(see 36.509 cl. 6.12)
Ellipsoid Point With Altitude value
corresponding to geographical
area 2 provided in
EFPROSE_RADIO_COM to be provided
in Update UE location information
(see 36.509 cl. 6.12)
Ellipsoid Point With Altitude value
not corresponding to
geographical area provided in
EFPROSE_RADIO_COM to be provided
in Update UE location information
(see 36.509 cl. 6.12)
TDD uplink-downlink subframe
configuration
Channel bandwidth used on
px_ePrimaryFrequencyBand
E-UTRA primary frequency band
E-UTRA secondary frequency
band
Channel bandwidth used on
px_eSecondaryFrequencyBand
Band combination for CA test
cases
Band combination for DC test
cases
NAS Ciphering Algorithm (eea1,
see NOTE)
NAS Integrity Algorithm (eia1,
see NOTE)
Ciphering Algorithm (see NOTE)
Integrity Algorithm (see NOTE)
Maximum number of ROHC
context sessions
A supported E-UTRA frequency
band overlapping with
px_OverlappingNotSupportedFre
quencyBand_MFBI. Applied to
MFBI test case scenario.
E-UTRAN channel bandwidth
used on
px_MFBI_FrequencyBand.
Applied to MFBI test case
scenario.
A not supported E-UTRA
frequency band that is
overlapping with a supported
band
(px_MFBI_FrequencyBand).
Applied to MFBI test case
scenario.
A supported E-UTRA frequency
band overlapping with
px_OverlappingNotSupportedFre
quencyBand_MFBI. Applied to
MFBI enhancement test case
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
194
px_ProSeAnnApplicationIdentity
charstring
1
mcc345.mnc012.Pr
oSeApp.Food.Rest
aurants.Italian
px_ProSeMonApplicationIdentit
y1
charstring
mcc300.mnc165.Pr
oSeApp.*.Sports.S
urfing
px_ProSeMonApplicationIdentit
yNot1
charstring
mcc208.mnc*.ProS
eApp.Shops.Food.
Wine
px_ProSe_TLS_CipherSuite
TLS_CIPHER_T
ype
TLS_PSK_WITH_3
DES_EDE_CBC_S
HA
scenario.
A ProSe Application ID with
which data structure the UE is
preconfigured and for which the
UE can request and perform
Direct Discovery Announcing. TS
23.003, section 24.2.
A ProSe Application ID with
which data structure the UE is
preconfigured and for which the
UE can request and perform
Direct Discovery Monitoring. TS
23.003, section 24.2
A ProSe Application ID with
which data structure the UE is
NOT preconfigured to request
and perform Direct Discovery
Monitoring. TS 23.003, section
24.2
TLS cipher suite to be used
for ProSe communication
Supported sidelink bandwidth
different from
n25
px_ePrimaryBandChannelBandw
idth
Unless specified otherwise in the test case prose, the null algorithm shall not be used for verification.
px_SL_AdditionalSupportedBan Ul_Bandwidth_T
dwidth
ype
NOTE:
9.2
MultiRAT PIXIT
Table 9.2-1: GERAN PIXIT
Parameter Name
px_GERAN_BandUnderTest
Parameter Type
GERAN_BandU
nderTestType
Default Value
GSM_P900
ETSI
Supported
Values
Description
Indicates which band is under
test
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
195
Table 9.2-2: UTRAN PIXIT
Parameter Name
Parameter Type
Default
Value
Supported Values
px_UTRAN_CipheringAlgorithm
CipheringAlgorit
hm_r7
uea2
uea0, uea1, uea2
px_UARFCN_Low_TDD
integer
px_UARFCN_Mid_TDD
integer
px_UARFCN_High_TDD
integer
px_TDD_OperationBandCharstr
ing
px_NoTDD_LCR_onLTE
Description
UTRAN Ciphering algorithm
Low Range downlink UARFCN
value for LCR TDD
Mid Range downlink UARFCN
value for LCR TDD
High Range downlink UARFCN
value for LCR TDD
charstring
a
boolean
false
ETSI
px_UARFCN_Mid_TD
D,
px_UARFCN_Low_TD
D and
Applicable for TDD
px_UARFCN_High_T
The operation band under test as
DD shall take the
defined in 34.108 clause 5.1.2
values according to
the value of
px_TDD_OperationBa
ndCharstring
Only applicable to UE supporting
(at least) LTE and LCR TDD.
If set to true, the UE is configured
not to report support of LCR TDD
(IE utraTDD128 in
UECapabilityInformation) when
being camped on an LTE cell
with no detectable LCR TDD cell
in the environment
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
196
Table 9.2-3: CDMA2000 HRPD PIXIT
Parameter Name
Parameter Type
Default Value
px_HRPD_BandClass
BandclassCDMA
1
2000_Type
px_HRPD_SectorID_Cell15
SectorID_HRPD
_Type
px_HRPD_SectorID_Cell16
SectorID_HRPD
_Type
px_HRPD_SectorID_Cell17
SectorID_HRPD
_Type
px_HRPD_SectorID_Cell18
SectorID_HRPD
_Type
px_ColorCode
ColorCode_Type 64
px_ColorCodeDiff
B32_Type
px_OpenLoopAdjust
OpenLoopAdjust
10
_Type
px_UATI24
O3_Type
'123456'O
px_MACIndex
integer
15
oct2bit('FEA00000
000000000000000
000000001'O)
oct2bit('FEA00000
000000000000000
000000002'O)
oct2bit('FEA00000
000000000000000
000000003'O)
oct2bit('FEA00000
000000000000000
000000004'O)
128
ETSI
Supported
Values
Description
Band Class;
Table 1.5-1 of C.S0057-E v1.0
Default value corresponds to 1.8
to 2.0 GHz PCS band
Sector ID of Cell 15;
Clause 13.9 of C.S0024-C v2.0
Sector ID of Cell 16;
Clause 13.9 of C.S0024-C v2.0
Sector ID of Cell 17;
Clause 13.9 of C.S0024-C v2.0
Sector ID of Cell 18;
Clause 13.9 of C.S0024-C v2.0
Colour code of the subnet to
which the sectors belong;
Same for all HRPD cells
Colour code of the subnet to
which the sectors belong;
Adifferent colour code than
default
The value of open loop adjust to
be used by access terminals in
the open loop power estimate,
expressed as an unsigned value
in units of 1 dB. The value used
by the access terminal is -1 times
the value of this field
UATI to be allocated to the UE,
clause 6.3.7.2.2 of C.S0024-C
v2.0
ReverseLinkMACIndex to be
used. Allowed values 0...383
C.S0024-C v2.0 clause
12.4.1.3.2.2
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
197
Table 9.2-4: CDMA2000 1xRTT PIXIT
Parameter Name
Parameter Type
Default Value
px_1XRTT_BaseId_Cell19
px_1XRTT_BaseId_Cell20
px_1XRTT_BaseId_Cell21
px_1XRTT_BaseId_Cell22
B16_Type
B16_Type
B16_Type
B16_Type
int2bit (39,16)
int2bit (40,16)
int2bit (41,16)
int2bit (42,16)
px_1XRTT_NID
B16_Type
int2bit (100,16)
px_1XRTT_SID
px_1XRTT_TMSI_Def
B15_Type
O4_Type
int2bit (200,15)
'1234ABCD'O
px_1XRTT_MinProtRev
ProtRev_Type
0
px_1XRTT_UserInfo_EncMode
px_1XRTT_Sig_EncMode
EncryptionMode
_Type
EncryptionMode
_Type
Supported
Values
2
2
px_1XRTT_BandClass
BandclassCDMA
1
2000_Type
px_PowerDownRegEnabled
boolean
true
px_1XRTT_Zone_Timer
B3_Type
‘000’B
px_RAND
B32_Type
'000011110000111
100001111000011
11'B
px_RAND2
B32_Type
'000011110000111
100001111000011
11'B
Description
Base ID of Cell 19
Base ID of Cell 20
Base ID of Cell 21
Base ID of Cell 22
default Network ID of 1xRTT
Cells
default SystemID of 1xRTT Cells
TMSI to be used in 1XRTT
Minimum Protocol revision
supported by Base Station
Encryption Mode
Rijndael algorithm
Encryption Mode
Rijndael algorithm
Band Class; Table 1.5-1 of
C.S0057 E v1.0. Default value
corresponds to 1.8 GHz to
2.0 GHz PCS band
Parameter for power down reg in
1xRTT
Zone timer sent in ‘System
Parameters Message’ overhead
message
Random Challenge Data to be
included along with mobility
parameters in
CSFBParametersResponseCDM
A2000 or
HandoverFromEUTRAPreparatio
nRequest
Random Challenge Data to be
included along with mobility
parameters in
CSFBParametersResponseCDM
A2000 or
HandoverFromEUTRAPreparatio
nRequest
Table 9.2-5: WLAN PIXIT
Parameter Name
px_ePDG_Ipsec_CipheringAlgo
rithm
Parameter Type
Default
Value
IPsec_Ciphering
Algorithm_Type
des_ede3_cbc,
des_ede
aes_cbc,
3_cbc
nociph
Supported Values
px_ePDG_Ipsec_IntegrityAlgorit
IPsec_IntegrityAl hmac_s hmac_md5_96,
hm
gorithm_Type
ha_1_96 hmac_sha_1_96
Description
Ipsec Ciphering Algorithm used
in ePDG
Ipsec Integrity Algorithm used in
ePDG
px_WLANBand
WLAN_Band_Ty Band2_
pe
4Ghz
px_WLAN_RulesToBeTested
WLAN_RulesTo
BeTested
Band2_4Ghz,
Band5Ghz,
Band3_6Ghz
"ANDSF "ANDSF_Rules",
_Rules" "RAN_Rules"
px_WLAN_PDN1_ToOffload
boolean
true
px_WLAN_UE_AddrIPv4
charstring
IPv4 WLAN UE Address
charstring
IPv6 WLAN UE Address
charstring
IPv4 WLAN Network Address
px_WLAN_UE_AddrIPv6
px_WLAN_NetworkAddrIPv4
ETSI
WLAN ISM Band
Rules to be tested in WLAN test
cases
If set to true, the first PDN
connection is offloaded to WLAN.
If set to false, the second PDN
connection is offloaded to WLAN.
3GPP TS 36.523-3 version 13.2.0 Release 13
px_WLAN_NetworkAddrIPv6
9.3
ETSI TS 136 523-3 V13.2.0 (2017-03)
198
charstring
IPv6 WLAN Network Address
NB-IoT PIXIT
Table 9.3-1: NB-IoT PIXIT
Parameter Name
px_NB_OperationMode
Parameter Type
Default
Value
NB_OperationM
ode_Type
inband_samePCI,
standalo inband_differentPCI,
ne
guardband,
standalone
px_DoAttachWithoutPDN
boolean
false
px_SMSTransport_CP_CIoT
boolean
false
px_nonSMSTransport_CP_CIoT boolean
false
px_ModifyBearerResources
false
10
boolean
Supported Values
Description
NB-IoT Operation Mode
UE is configured to do Attach
without PDN; if the value is
FALSE it is assumed that the UE
is configured to do Attach with
PDN
NB-IoT UE configured to utilise
the SMS service as transport
mechanism for user data for
Control Plane CIoT Optimisation
NB-IoT UE configured to utilise
non-SMS services as transport
mechanism for user data for
Control Plane CIoT Optimisation
NB-IoT UE configured to handle
modification of bearer resources
including dedicated bearers
(PDN of type "IP")
Postambles
The purpose of this clause is to specify postambles to bring the UE to a well defined state regardless of the UE state at
the termination of main test body or of the SS conditions and values of the system information inherited from the test.
10.1
Postambles for E-UTRA to UTRA tests
This clause describes UE postamble procedures which are used at the end of inter-RAT test cases specified in
TS 36.508 [3] so as to switch off the UE.
UE LTE and UTRAN postamble conditions are specified in table 10.1-1.
Table 10.1-1: UE postamble conditions
LTE UE attach type
attach
combined_attach
10.1.1
UE UTRA CS/PS domain
pc_CS AND pc_PS
pc_PS AND NOT (pc_CS)
pc_CS AND pc_PS
pc_CS AND NOT (pc_PS)
Postamble condition
C1
C2
C3
C4
UE postamble states and procedures for E-UTRA to UTRA
In order to bring the UE to the switched/powered off state, a number of procedures need to be executed in a hierarchical
sequence, according to the reference end state specified in each test procedure sequence. The sequences and the
identified procedures are shown in figure 10.1.1-1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
199
UTRA
handover (U3)
P10.1.4
UTRA CS
fallback (U4)
P10.1.5
UTRA CS call
(U5)
P10.1.3
UTRA
connected
(U2)
UTRA idle (U1)
P10.1.2
P10.1.2
Off
Figure 10.1.1-1: UE postamble procedures for E-UTRA / UTRA test cases
NOTE 1: Depending on the test case specifications the termination of a test case can be in any state of figure
10.1.1-1.
UE in UTRA state U2, U3, U4 and U5 may send data on the established radio bearer and shall be accepted and handled.
NOTE 2: NAS and AS security procedures during routing area update and handover are performed according to TS
33.401 [24], clauses 9.1.1 and 9.2.1 and TS 25.331 [36], clause 8.3.6.3.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
10.1.2
10.1.2.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
200
Switch/Power off procedure
Procedure
Table 10.1.2.1-1: Switch/Power off procedure
Step
Procedure
1
The UE is powered off or switched off, (see
ICS)
EXCEPTION: Steps 2 to 7 specify the
behaviour if UE supports pc_SwitchOnOff.
EXCEPTION: Steps 2 to 4 are used only
when the UE is in UTRA idle end state (U1).
2
The UE transmits RRC CONNECTION
REQUEST
3
The SS transmit a RRC CONNECTION
SETUP
4
The UE transmits an RRC CONNECTION
SETUP COMPLETE message
EXCEPTION: Step 4Aa1 to 4Aa6 specifies
optional behaviour if the UE is registered to
IMS services. UE may perform IMSderegistration procedure.
4Aa1 The UE transmits UPLINK DIRECT
TRANSFER message or INITIAL DIRECT
TRANSFER message when the UE is in
UTRA idle end state (U1).
This message includes a GMM SERVICE
REQUEST message with service type=Data.
4Aa2 The SS transmits a SECURITY MODE
COMMAND message for the ps domain.
4Aa3 The UE transmits a SECURITY MODE
COMPLETE message.
4Aa4 The SS transmits a RADIO BEARER SETUP
message using the UTRA reference radio
bearer parameters and combination “UTRA
PS RB” according to TS 36.508 subclause
4.8.3 and Table 4.8.3-1.
4Aa5 The UE transmits a RADIO BEARER SETUP
COMPLETE
4Aa6 IMS de-registration is performed using the
generic procedure defined in 34.229-1 [40]
Annex C.30.
EXCEPTION: Step 4Aa7a1 to 4Aa7a2
specifies optional behaviour depending on the
UE implementation. The UE may perform
PDP context deactivation procedure before
Detach.
4Aa7a The UE transmits DEACTIVATE PDP
1
CONTEXT REQUEST
4Aa7a The SS transmits DEACTIVATE PDP
2
CONTEXT ACCEPT
EXCEPTION: Step 5a1 specifies behaviour
when the current UTRA cell is in NMO I and
the UE is in condition:
- C1 or
- C3
5a1
The UE transmits an UPLINK DIRECT
TRANSFER message or INITIAL DIRECT
TRANSFER message when the UE is in
UTRA idle end state (U1).
This message includes a DETACH
REQUEST message with the detach
type=‘power switched off, GPRS/IMSI
combined detach'
ETSI
Message Sequence
Message
U-S
-
-
-
-
-->
RRC CONNECTION REQUEST
<--
RRC CONNECTION SETUP
-->
RRC CONNECTION SETUP COMPLETE
-->
GMM SERVICE REQUEST
SECURITY MODE COMMAND
SECURITY MODE COMPLETE
RADIO BEARER SETUP
RADIO BEARER SETUP COMPLETE
-->
DEACTIVATE PDP CONTEXT REQUEST
<--
DEACTIVATE PDP CONTEXT ACCEPT
-
-->
-
DETACH REQUEST
3GPP TS 36.523-3 version 13.2.0 Release 13
Step
Procedure
-
EXCEPTION: Step 5b1 specifies behaviour
when the current UTRA cell is in (NMO I or
NMO II) and the UE is in condition C4
The UE transmits an UPLINK DIRECT
TRANSFER message or INITIAL DIRECT
TRANSFER message when the UE is in
UTRA idle end state (U1).
This message includes an IMSI DETACH
INDICATION message
EXCEPTION: Step 5c1 specifies behaviour
when the current UTRA cell is in (NMO I or
NMO II) and the UE is in condition C2
The UE transmits an UPLINK DIRECT
TRANSFER message or INITIAL DIRECT
TRANSFER message when the UE is in
UTRA idle end state (U1).
This message includes a DETACH
REQUEST message with detach type=‘power
switched off, PS detach''
EXCEPTION: Steps 5d1 and 5d2 specify
behaviour when the current UTRA cell is in
NMO II and the UE is in condition:
- C1 or
- C3.
Both detach messages (in steps 5d1 and 5d2)
can be sent by UE in any order.
The UE transmits an UPLINK DIRECT
TRANSFER message or INITIAL DIRECT
TRANSFER message when the UE is in
UTRA idle end state (U1) and this is the first
message received.
This message includes a DETACH
REQUEST message with the detach
type=‘power switched off, PS detach''
The UE transmits an UPLINK DIRECT
TRANSFER message or INITIAL DIRECT
TRANSFER message when the UE is in
UTRA idle end state (U1) and this is the first
message received.
This message includes an IMSI DETACH
INDICATION message
The SS transmits an RRC CONNECTION
RELEASE message
The UE transmits a RRC CONNECTION
RELEASE COMPLETE message
5b1
-
5c1
-
5d1
5d2
6
7
ETSI TS 136 523-3 V13.2.0 (2017-03)
201
ETSI
U-S
-
-->
-
-->
-
Message Sequence
Message
-
IMSI DETACH INDICATION
-
DETACH REQUEST
-
-->
DETACH REQUEST
-->
IMSI DETACH INDICATION
<--
RRC CONNECTION RELEASE
-->
RRC CONNECTION RELEASE
COMPLETE
3GPP TS 36.523-3 version 13.2.0 Release 13
10.1.3
10.1.3.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
202
CC disconnect procedure
Procedure
Table 10.1.3.1-1: CC disconnect procedure
Step
1
2
3
4
5a
5b
5c
5d
5e
6
7
8
Procedure
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a DISCONNECT
message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a RELEASE
message.
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a RELEASE
COMPLETE message.
Void
The SS transmits an RRC CONNECTION
RELEASE message
The UE transmits a RRC CONNECTION
RELEASE COMPLETE message
The UE transmits RRC CONNECTION
REQUEST
The SS transmit a RRC CONNECTION
SETUP
The UE transmits an RRC CONNECTION
SETUP COMPLETE message
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE REQUEST message with Update
type ='Combined RA/LA Updated'
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE ACCEPT message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE COMPLETE message.
ETSI
Message Sequence
U-S
Message
<-DISCONNECT
-->
RELEASE
RELEASE COMPLETE
<--
<--
RRC CONNECTION RELEASE
-->
-->
RRC CONNECTION RELEASE
COMPLETE
RRC CONNECTION REQUEST
<--
RRC CONNECTION SETUP
-->
RRC CONNECTION SETUP COMPLETE
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE COMPLETE
-->
3GPP TS 36.523-3 version 13.2.0 Release 13
10.1.4
10.1.4.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
203
PS Routing Area Update procedure
Procedure
Table 10.1.4.1-1: PS Routing Area Update procedure
Step
Procedure
-
EXCEPTION: steps 1a1 to 1a5 specify the UE
behaviour when the current UTRA cell is in
NMO I and the UE is in condition:
- C1 or
- C3 and the UE is not registered to the LAC
of the current UTRA cell
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE REQUEST message with Update
type ='Combined RA/LA Updated'
Void
Void
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE ACCEPT message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE COMPLETE message.
EXCEPTION: steps 1b1 to 1b5 specify the UE
behaviour when the current UTRA cell is in
(NMO I or NMO II) and the UE is in condition:
- C2 or
- C3 and the UE is registered to the LAC of
the current UTRA cell
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE REQUEST message with Update
type ='RA Update'
Void
Void
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE ACCEPT message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE COMPLETE message.
EXCEPTION: steps 1c1 to 1c9 specify the UE
behaviour when the current UTRA cell is in
NMO II and the UE is in condition:
- C1 or
- C3 and the UE is not registered to the LAC
of the current UTRA cell.
1a1
1a2
1a3
1a4
1a5
-
1b1
1b2
1b3
1b4
1b5
-
1c1
The LOCATION UPDATE REQUEST
message (step 1c6) can be received during
the routing area updating procedure (steps
1c1 to 1c4).
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE REQUEST message with Update
type ='RA Update'.
ETSI
U-S
-
Message Sequence
Message
-
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE COMPLETE
-->
-
-
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE COMPLETE
-->
-
-->
-
ROUTING AREA UPDATE REQUEST
3GPP TS 36.523-3 version 13.2.0 Release 13
Step
1c2
1c3
1c4
1c5
1c6
1c7
1c8
1c9
1c10
10.1.5
10.1.5.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
204
Procedure
Void
Void
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE ACCEPT message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE COMPLETE message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a LOCATION
UPDATING REQUEST message.
The SS transmits a SECURITY MODE
COMMAND message.
The UE transmits a SECURITY MODE
COMPLETE message.
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a LOCATION
UPDATING ACCEPT
The EU transmits a UPLINK DIRECT
TRANSFER message.
This message includes a TMSI
REALLOCATION COMPLETE
Message Sequence
U-S
Message
<-ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE COMPLETE
-->
-->
LOCATION UPDATING REQUEST
<--
SECURITY MODE COMMAND
-->
SECURITY MODE COMPLETE
<--
LOCATION UPDATING ACCEPT
-->
TMSI REALLOCATION COMPLETE
CS fallback procedure
Procedure
Table 10.1.5.1-1: CS fallback procedure
Step
Procedure
-
EXCEPTION: In parallel to the events
described in step 1a1 to 2a5 the steps
specified in table 10.1.5.1-2 takes place.
EXCEPTION: Steps 1a1 and 1a2 specify the
MO call procedure and step 1b1 specifies the
MT call procedure.
The UE transmits an INITIAL DIRECT
TRANSFER message including a CM
SERVICE REQUEST message.
The SS transmits an UPLINK DIRECT
TRNASFER message including a CM
SERVICE REJECT with the reject cause #32
(Service option not supported)
EXCEPTION: Step 1b1 specifies the MT call
procedure.
The UE transmits an INITIAL DIRECT
TRANSFER message including a PAGING
RESPONSE message.
EXCEPTION: Steps 2a1 and 2a5 specify the
location area update procedure when the
current UTRA cell is in NMO II and the UE is
in condition C3 and the UE is not registered to
the LAC of the current UTRA cell.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a LOCATION
UPDATING REQUEST message.
-
1a1
1a2
1b1
-
2a1
ETSI
Message Sequence
Message
U-S
-
-
-
-
-->
CM SERVICE REQUEST
<--
CM SERVICE REJECT
-->
-
-->
PAGING RESPONSE
-
LOCATION UPDATING REQUEST
3GPP TS 36.523-3 version 13.2.0 Release 13
Step
Procedure
2a2
The SS transmits a SECURITY MODE
COMMAND message.
The UE transmits a SECURITY MODE
COMPLETE message.
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a LOCATION
UPDATING ACCEPT
The EU transmits a UPLINK DIRECT
TRANSFER message.
This message includes a TMSI
REALLOCATION COMPLETE
The SS transmits a SECURITY MODE
COMMAND message.
The UE transmits a SECURITY MODE
COMPLETE message.
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE ACCEPT message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE COMPLETE message.
EXCEPTION: Steps 7a1 and 7a5 specify the
combined routing updating procedure when
the initial RAU procedure was for RA Only.
This may occur either before, or after, steps 8
and 9
The UE transmits a ROUTING AREA
UPDATE REQUEST message.
The SS transmits a SECURITY MODE
COMMAND message.
The UE transmits a SECURITY MODE
COMPLETE message.
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE ACCEPT message.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a ROUTING AREA
UPDATE COMPLETE message.
EXCEPTION: Steps 7b1 and 7b4 specify the
location updating procedure when the current
UTRA cell is in network mode (NMO I or NMO
II) and the UE is in condition C4 and the UE is
not registered to the LAC of the current UTRA
cell.
The UE transmits an UPLINK DIRECT
TRANSFER message.
This message includes a LOCATION
UPDATING REQUEST message.
The SS transmits a SECURITY MODE
COMMAND message.
The UE transmits a SECURITY MODE
COMPLETE message.
The SS transmits a DOWNLINK DIRECT
TRANSFER message.
This message includes a LOCATION
UPDATING ACCEPT
The EU transmits a UPLINK DIRECT
TRANSFER message.
This message includes a TMSI
REALLOCATION COMPLETE
2a3
2a4
2a5
3
4
5
6
-
7a1
7a2
7a3
7a4
7a5
-
7b1
7b2
7b3
7b4
7b5
ETSI TS 136 523-3 V13.2.0 (2017-03)
205
ETSI
Message Sequence
U-S
Message
<-SECURITY MODE COMMAND
-->
SECURITY MODE COMPLETE
<--
LOCATION UPDATING ACCEPT
-->
TMSI REALLOCATION COMPLETE
<--
SECURITY MODE COMMAND
-->
<--
SECURITY MODE COMPLETE
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE COMPLETE
-->
-
-
-->
ROUTING AREA UPDATE REQUEST
<--
SECURITY MODE COMMAND
-->
<--
SECURITY MODE COMPLETE
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE COMPLETE
-->
-
-
-->
LOCATION UPDATING REQUEST
<--
SECURITY MODE COMMAND
-->
SECURITY MODE COMPLETE
<--
LOCATION UPDATING ACCEPT
-->
TMSI REALLOCATION COMPLETE
3GPP TS 36.523-3 version 13.2.0 Release 13
Step
8
9
ETSI TS 136 523-3 V13.2.0 (2017-03)
206
Message Sequence
U-S
Message
<-RRC CONNECTION RELEASE
Procedure
The SS transmits an RRC CONNECTION
RELEASE message.
The UE transmits an RRC CONNECTION
RELEASE COMPLETE message.
-->
RRC CONNECTION RELEASE
COMPLETE
Table 10.1.5.1-2: Parallel behaviour
St
1
Procedure
The UE transmits a ROUTING AREA UPDATE
REQUEST message.
10.2
U-S
-->
Message Sequence
Message
ROUTING AREA UPDATE
REQUEST
TP
Verdict
-
-
Postambles for E-UTRAN to GERAN tests
This clause describes UE postamble procedures which are used at the end of inter-RAT test cases defined in
TS 36.508 [3] so as to switch off the UE. UE LTE and GERAN postamble transitions are specified in table 10.2-1.
Table 10.2-1: UE postamble conditions
LTE UE attach type
attach
combined attach
10.2.1
UE GERAN CS/PS domain
pc_GPRS
pc_GPRS
NOT pc_GPRS
Postamble condition
C1
C2
C3
UE postamble states and procedures for E-UTRA to GERAN test
cases
In order to bring the UE to the switched/powered off state there are a number of procedures that need to be executed in
a hierarchical sequence, according to the reference end state specified in each test procedure sequence. The sequences
and the identified procedures are shown in figure 10.2.1-1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
207
ETSI TS 136 523-3 V13.2.0 (2017-03)
GERAN PS
Handover (G2)
GERAN CS
Call (G4)
GERAN
CS fallback (G3)
P10.2.4
P10.2.5
P10.2.3
GERAN Idle
(G1)
P10.2.2
Off
Figure 10.2.1-1: UE postamble procedures for E-UTRA / GERAN test cases
NOTE 1: Depending on the test case specifications the termination of a test case can be in any state of
figure 10.2.1-1.
NOTE 2: The security procedures for interworking to GERAN are according to TS 33.401 [24] clauses 10.2.1 and
10.3.1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
10.2.2
10.2.2.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
208
Switch/Power off procedure
Procedure
Table 10.2.2.1-1: Switch/Power off procedure
Step
Procedure
1
The UE is powered off or switched off, (see
ICS)
EXCEPTION: Steps 2a1 to 2c2 specify the
behaviour if UE supports pc_SwitchOnOff.
EXCEPTION: Step 2a1 specifies behaviour
when the GERAN cell is in (NMO I or NMO II)
and UE is in condition C1
2a1
The UE transmits a DETACH REQUEST
message
EXCEPTION: Step 2b1 specifies behaviour
when the GERAN cell is in (NMO I or NMO II)
and UE is in condition C3
2b1
The UE transmits an IMSI DETACH
INDICATION message
EXCEPTION: Steps 2c1 – 2c1A3 and step
2c2 specify behaviour when the GERAN cell
is in NMO II and UE is in condition C2. The
messages can be sent in any order
2c1
The UE transmits an IMSI DETACH
INDICATION message
2c1A1 The UE transmits a Classmark Change
message
EXCEPTION: Steps 2c1A2 and 2cA3 can
occur in any order
2c1A2 IF pc_UTRA THEN the UE transmits a Utran
Classmark Change message.
2c1A3 IF UE is still attached for GPRS (step 2c2 has
not yet occurred) THEN the UE transmits a
GPRS Suspension Request message
2c2
The UE transmits a DETACH REQUEST
message
ETSI
Message Sequence
Message
U-S
-
-
-
-
-
-
-->
-
-->
-
DETACH REQUEST
-
IMSI DETACH INDICATION
-
-->
IMSI DETACH INDICATION
-->
CLASSMARK CHANGE
-
-
-->
UTRAN CLASSMARK CHANGE.
-->
GPRS SUSPENSION REQUEST
-->
DETACH REQUEST
3GPP TS 36.523-3 version 13.2.0 Release 13
10.2.3
10.2.3.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
209
PS Handover procedure
Procedure
Table 10.2.3.1-1: PS handover procedure
Step
Procedure
-
EXCEPTION: Steps 1a1 and 1a3 specify the
UE behaviour when GERAN cell is in NMO I
and the UE is in condition C2 and the UE is
not registered to the LAC of this cell.
1a1
The UE transmits a ROUTING AREA
UPDATE REQUEST message with update
type='Combined RA/LA Update'.
1a2
The SS transmits a ROUTING AREA
UPDATE ACCEPT message.
1a3
The UE transmits a ROUTING AREA
UPDATE COMPLETE message.
EXCEPTION: Steps 1b1 and 1b3 specify the
location updating procedure when GERAN
cell is in (NMO I or NMO II) and the UE is in
condition C2 and the UE is registered to the
LAC of this cell.
1b1
The UE transmits a ROUTING AREA
UPDATE REQUEST message with update
type='RA Update'.
1b2
The SS transmits a ROUTING AREA
UPDATE ACCEPT message.
1b3
The UE transmits a ROUTING AREA
UPDATE COMPLETE message.
EXCEPTION: Steps 1c1 and 1c6 specify the
location updating procedure when GERAN
cell is in NMO II and the UE is in condition C2
and the UE is not registered to the LAC of this
cell.
1c1
The UE transmits a ROUTING AREA
UPDATE REQUEST message with update
type='RA Update'.
1c2
The SS transmits a ROUTING AREA
UPDATE ACCEPT message.
1c3
The UE transmits a ROUTING AREA
UPDATE COMPLETE message.
1c4
The UE transmits a LOCATION UPDATING
REQUEST message.
1c4A1 The UE transmits a Classmark Change
message
EXCEPTION: The next step describes
behaviour that depends on UE capability.
1c4A2 IF pc_UTRA THEN the UE transmits a Utran
Classmark Change message.
1c5
The SS transmits a LOCATION UPDATING
ACCEPT
1c6
The UE transmits a TMSI REALLOCATION
COMPLETE
ETSI
U-S
-
Message Sequence
Message
-
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
-->
-
ROUTING AREA UPDATE COMPLETE
-
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
-->
-
ROUTING AREA UPDATE COMPLETE
-
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
-->
ROUTING AREA UPDATE COMPLETE
-->
LOCATION UPDATING REQUEST
-->
CLASSMARK CHANGE
-
-
-->
UTRAN CLASSMARK CHANGE.
<--
LOCATION UPDATING ACCEPT
TMSI REALLOCATION COMPLETE
3GPP TS 36.523-3 version 13.2.0 Release 13
10.2.4
10.2.4.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
210
CC disconnect procedure
Procedure
Table 10.2.4.1-1: CC disconnect procedure
Step
Procedure
1
2
3
The SS transmits a DISCONNECT message.
The UE transmits a RELEASE message.
The SS transmits a RELEASE COMPLETE
message.
The SS transmits a CHANNEL RELEASE
message.
4
10.2.5
10.2.5.1
Message Sequence
U-S
Message
<-DISCONNECT
-->
RELEASE
RELEASE COMPLETE
<-<--
CHANNEL RELEASE
CS fallback procedure
Procedure
Table 10.2.5.1-1: CS fallback procedure MO call
Step
Procedure
-
EXCEPTION: Steps 1a1 and 1a2 specify the
MO call procedure.
1a1
The UE transmits a CM SERVICE REQUEST
message.
1a2
The SS transmits a CM SERVICE REJECT
with the reject cause #32 (Service option not
supported)
EXCEPTION: Step 1b1 specifies the MT call
procedure.
1b1
The UE transmits a PAGING RESPONSE
message.
EXCEPTION: Steps 2a1 to 2a6 specify the
procedure when GERAN cell is in NMO II and
if the UE is in condition C2 and the UE is
registered to the LAC of the current GERAN
cell.
2a1
The UE transmits a LOCATION UPDATING
REQUEST message.
2a1A1 The UE transmits a Classmark Change
message
EXCEPTION: The next step describes
behaviour that depends on UE capability.
2a1A2 IF pc_UTRA THEN the UE transmits a Utran
Classmark Change message.
2a2
The SS transmits a LOCATION UPDATING
ACCEPT
2a3
The UE transmits a TMSI REALLOCATION
COMPLETE
2a4
The UE transmits a ROUTING AREA
UPDATE REQUEST message.
2a5
The SS transmits a ROUTING AREA
UPDATE ACCEPT message.
2a6
The UE transmits a ROUTING AREA
UPDATE COMPLETE message.
EXCEPTION: Steps 2b1 to 2b3 specify the
location updating procedure when GERAN
cell is in (NMO I or NMO II) and if the UE is in
condition C3 and the UE is not registered to
the LAC of the current GERAN cell
2b1
The UE transmits a LOCATION UPDATING
ETSI
U-S
-
Message Sequence
Message
-
-->
CM SERVICE REQUEST
<--
CM SERVICE REJECT
-->
-
PAGING RESPONSE
-
-->
LOCATION UPDATING REQUEST
-->
CLASSMARK CHANGE
-
-
-->
UTRAN CLASSMARK CHANGE.
<--
LOCATION UPDATING ACCEPT
TMSI REALLOCATION COMPLETE
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
-->
-
-->
ROUTING AREA UPDATE COMPLETE
-
LOCATION UPDATING REQUEST
3GPP TS 36.523-3 version 13.2.0 Release 13
Step
Procedure
Message Sequence
Message
U-S
REQUEST message.
2b1A1 The UE transmits a Classmark Change
message
EXCEPTION: The next step describes
behaviour that depends on UE capability.
2b1A2 IF pc_UTRA THEN the UE transmits a Utran
Classmark Change message.
2b2
The SS transmits a LOCATION UPDATING
ACCEPT
2b3
The UE transmits a TMSI REALLOCATION
COMPLETE
EXCEPTION: Steps 2c1 to 2c3 specify the
routing area updating procedure when the
GERAN cell is in NMO I and the UE is in
condition C2and the UE is not registered to
the LAC of the current GERAN cell
2c1
The UE transmits a ROUTING AREA
UPDATE REQUEST message with update
type = ‘Combined RA/LA update'.
2c2
The SS transmits a ROUTING AREA
UPDATE ACCEPT message.
2c3
The UE transmits a ROUTING AREA
UPDATE COMPLETE message.
10.3
ETSI TS 136 523-3 V13.2.0 (2017-03)
211
-->
-
CLASSMARK CHANGE
-
-->
UTRAN CLASSMARK CHANGE.
<--
LOCATION UPDATING ACCEPT
TMSI REALLOCATION COMPLETE
-
-
-->
ROUTING AREA UPDATE REQUEST
<--
ROUTING AREA UPDATE ACCEPT
-->
ROUTING AREA UPDATE COMPLETE
Postambles for E-UTRA test cases
This clause describes UE postamble states which can be used in the post condition of E-UTRA test cases defined in TS
36.523-1 [1]. The clause also specifies a set of procedures to bring the UE into these states.
10.3.1
UE postamble states and procedures for E-UTRA test cases
In order to bring the UE to switched/powered off state there are some procedures that need to be executed. The
identified procedures are shown in figure 10.3.1-1.
E-UTRA
manual
selection (E5)
E-UTRA
connec ted (E2)
E-UTRA
connected T3440
(E2_T3440)
E-UTRA test
mode (E3)
E-UTRA
deregistered
(E4)
P10.3.5
P10.3.3
P10.3.3
E-UTRA idle
(E1)
P10.3.3
P10.3. 4
P10.3.2
Off
Figure 10.3.1-1: UE postamble states and procedures for E-UTRA
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
10.3.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
212
Switch/Power off procedure in State E1
10.3.2.1
Procedure
Table 10.3.2.1-1: Switch/Power off procedure
Step
Procedure
1
The UE is powered off or switched off, (see
ICS)
EXCEPTION: Steps 2a1 to 2a4 specify
behaviour if the UE supports pc_SwitchOnOff
UE transmits an RRCConnectionRequest
message.
SS transmit an RRCConnectionSetup
message.
EXCEPTION: Steps 2a3Aa1 to 2a3Aa6
specify optional behaviour if the UE has
previously performed IMS registration
The UE transmits an
RRCConnectionSetupComplete message to
confirm the successful completion of the
connection establishment and to initiate the
IMS signalling procedure by including the
SERVICE REQUEST message.
The SS transmits a SecurityModeCommand
message to activate AS security.
The UE transmits a SecurityModeComplete
message and establishes the initial security
configuration.
The SS configures a new data radio bearer,
associated with the default EPS bearer
context.
The RRCConnectionReconfiguration
message is using condition SRB2-DRB(1, 0).
The DRB associated with default EPS bearer
context obtained during the attach procedure
is established
EXCEPTION: In parallel to the event
described in step 2a3Aa5 below, the
behaviour in TS 34.229-1 [40] Annex C.30
may occur. (IMS de-registration)
The UE transmits an
RRCConnectionReconfigurationComplete
message to confirm the establishment of the
new data radio bearer, associated with the
default EPS bearer context.
The UE initiates the Detach procedure by
sending DETACH REQUEST
EXCEPTION : Step 2a3Ba1 below specifies
the behaviour if the UE has not previously
performed IMS registration
The UE transmits an
RRCConnectionSetupComplete message to
confirm the successful completion of the
connection establishment and to initiate the
Detach procedure by including the DETACH
REQUEST message.
The SS transmits an RRC CONNECTION
RELEASE message
2a1
2a2
-
2a3Aa
1
2a3Aa
2
2a3Aa
3
2a3Aa
4
2a3Aa
5
2a3Aa
6
2a3
Ba1
2a4
ETSI
Message Sequence
Message
U-S
-
-
-
-
-->
<--
RRC: RRCConnectionRequest
RRC: RRCConnectionSetup
-
-->
RRC: RRCConnectionSetupComplete
NAS: SERVICE REQUEST
<--
RRC: SecurityModeCommand
-->
RRC: SecurityModeComplete
<--
RRC: RRCConnectionReconfiguration
-
-
-->
RRC:
RRCConnectionReconfigurationComplet
e
-->
NAS: DETACH REQUEST
-->
RRC: RRCConnectionSetupComplete
NAS: DETACH REQUEST
<--
RRC CONNECTION RELEASE
3GPP TS 36.523-3 version 13.2.0 Release 13
10.3.3
ETSI TS 136 523-3 V13.2.0 (2017-03)
213
Switch/Power off procedure in State E2 and E3
10.3.3.1
Procedure for E2 and E3
Table 10.3.3.1-1: Switch/Power off procedure
Step
Procedure
Message Sequence
Message
U-S
-
EXCEPTION: In parallel to the events
described in steps 1 to 2a2, the steps
described:
- in Table 10.3.3.1-2 may take place if UE
supports pc_eMBMS_SC and SIB15 is
broadcasted in the cell,
- in Table 10.3.3.1-3 may take place if UE
supports pc_discSupportedBands and SIB19
is broadcasted in the cell or if UE supports
pc_commSupportedBands and SIB18 is
broadcasted in the cell.
1
The UE is powered off or switched off (see
ICS)
EXCEPTION: Steps 2a1 to 2a2 specify
behaviour if the UE supports pc_SwitchOnOff
EXCEPTION : Step 2a1Aa1 to 2a1Aa2 below
specifies optional behaviour if the UE has
previously performed IMS registration
2a1Aa The UE may perform the procedure described
1–
in TS 34.229-1 [40] Annex C.30 (IMS de2a1Aa registration)
2
2a1 The UE transmits DETACH REQUEST
2a2 The SS transmits an RRC CONNECTION
RELEASE message
-
-
-
-
-
-
-
-
-->
<--
DETACH REQUEST
RRC CONNECTION RELEASE
Table 10.3.3.1-2: Parallel behaviour
St
1
Procedure
UE transmits a MBMSInterestIndication
message.
U-S
-->
Message Sequence
Message
MBMSInterestIndication
Table 10.3.3.1-3: Parallel behaviour
St
1
Procedure
U-S
-->
UE transmits a SidelinkUEInformation
message.
ETSI
Message Sequence
Message
SidelinkUEInformation
3GPP TS 36.523-3 version 13.2.0 Release 13
10.3.3.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
214
Procedure for E2_T3440
Table 10.3.3.2-1: RRC release and switch/power off procedure
Step
Procedure
1
The SS transmits an RRC CONNECTION
RELEASE message
The SS waits for 5s to ensure that the UE
goes to RRC_IDLE state.
The UE is powered off or switched off (see
ICS)
EXCEPTION: Steps 4a1 to 4a4 specify
behaviour if the UE supports pc_SwitchOnOff
UE transmits an RRCConnectionRequest
message.
SS transmit an RRCConnectionSetup
message.
EXCEPTION: Steps 4a3Aa1 to 4a3Aa6
specify optional behaviour is the UE has
previously performed IMS registration
The UE transmits an
RRCConnectionSetupComplete message to
confirm the successful completion of the
connection establishment and to initiate the
IMS signalling procedure by including the
SERVICE REQUEST message.
The SS transmits a SecurityModeCommand
message to activate AS security.
The UE transmits a SecurityModeComplete
message and establishes the initial security
configuration.
The SS configures a new data radio bearer,
associated with the default EPS bearer
context.
The RRCConnectionReconfiguration
message is using condition SRB2-DRB(1, 0).
The DRB associated with default EPS bearer
context obtained during the attach procedure
is established
EXCEPTION: In parallel to the event
described in step 4a3Aa5 below, the
behaviour in TS 34.229-1 [40] Annex C.30
may occur. (IMS de-registration)
The UE transmits an
RRCConnectionReconfigurationComplete
message to confirm the establishment of the
new data radio bearer, associated with the
default EPS bearer context.
The UE initiates the Detach procedure by
sending DETACH REQUEST
EXCEPTION : Step 4a3Ba1 below specifies
the behaviour if the UE has not previously
performed IMS registration
The UE transmits an
RRCConnectionSetupComplete message to
confirm the successful completion of the
connection establishment and to initiate the
Detach procedure by including the DETACH
REQUEST message.
The SS transmits an RRC CONNECTION
RELEASE message
2
3
4a1
4a2
-
4a3Aa
1
4a3Aa
2
4a3Aa
3
4a3Aa
4
-
4a3Aa
5
4a3Aa
6
-
4a3
Ba1
4a4
ETSI
U-S
<--
Message Sequence
Message
RRC CONNECTION RELEASE
-
-
-
-
-->
<--
RRC: RRCConnectionRequest
RRC: RRCConnectionSetup
-
-->
RRC: RRCConnectionSetupComplete
NAS: SERVICE REQUEST
<--
RRC: SecurityModeCommand
-->
RRC: SecurityModeComplete
<--
RRC: RRCConnectionReconfiguration
-
-
-->
RRC:
RRCConnectionReconfigurationComplet
e
-->
NAS: DETACH REQUEST
-
-->
RRC: RRCConnectionSetupComplete
NAS: DETACH REQUEST
<--
RRC CONNECTION RELEASE
3GPP TS 36.523-3 version 13.2.0 Release 13
10.3.4
ETSI TS 136 523-3 V13.2.0 (2017-03)
215
Switch/Power off procedure in State E4
10.3.4.1
Procedure
Table 10.3.4.1-1: Switch/Power off procedure
Step
Procedure
1
The UE is powered off or switched off (see
ICS)
10.3.5
U-S
-
Message Sequence
Message
-
Automatic selection mode procedure in State E5 (current cell,
neighbour cell)
10.3.5.1
Procedure
Table 10.3.5.1-1: Automatic selection mode procedure
Step
Procedure
1
Set UE to Automatic PLMN selection
mode.
The SS configures:
- the current cell as a “Non-Suitable Off
cell”
- the neighbour cell as a “Serving cell”
Generic test procedure in TS 36.508
subclause 6.4.2.7-1 is performed on the
neighbour cell
At the end of this test procedure sequence,
the UE is in end state E-UTRA idle (E1)
2
3
-
10.4
Message Sequence
Message
U-S
-
-
-
-
-
-
-
-
Postambles for E-UTRA to HRPD test cases
This clause describes UE postamble states which can be used in the post condition of E-UTRA test cases defined in
TS 36.523-1 [1]. The clause also specifies a set of procedures to bring the UE into these states.
10.4.1
10.4.1.1
UE postamble procedures for E-UTRA to HRPD (No PreRegistration)
Registration on HRPD Cell
Table 10.4.1.1: Registration on HRPD Cell procedure
Step
Procedure
1
2
3
4
The UE transmits a UATIRequest message.
The SS transmits UATIAssignment message
The UE transmits UATIComplete message
The UE transmits ConnectionRequest
message.
The SS transmits a TrafficChannelAssignment
message.
The UE transmits TrafficChannelcomplete.
The UE transmits ConfigurationRequest
message for SCP configuration.
The SS transmits a ConfigurationResponse
5
6
7
8
ETSI
U-S
-->
<--->
-->
Message Sequence
Message
UATIRequest
UATIAssignment
UATIComplete
ConnectionRequest
<--
TrafficChannelAssignment
-->
-->
TrafficChannelcomplete
SCP:ConfigurationRequest
<--
SCP:ConfigurationResponse
3GPP TS 36.523-3 version 13.2.0 Release 13
Step
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
ETSI TS 136 523-3 V13.2.0 (2017-03)
216
Procedure
Message Sequence
Message
U-S
message for SCP configuration.
The UE transmits ConfigurationRequest
message for Stream protocol.
The SS transmits a ConfigurationResponse
message for Stream protocol accepting EMPA
bound to service network.
The UE transmits EMPA ConfigurationRequest
message.
The SS transmits an EMPA
ConfigurationResponse message.
The UE transmits ConfigurationComplete
message.
Optionally session negotiation initiated by the
SS might take place
Optionally device level authentication may take
place.
Optionally Location Update procedure may
take place if the SS is configured to support it.
PPP LCP negotiation is performed between
the UE and the SS. EAP-AKA is selected as
the authentication protocol.
Tunnelled EAP-AKA is performed between the
UE and the SS.
The UE transmits VSNCP Configure-Request
message, including a PDN-ID, PDN Type,
APN, PDN Address with empty content,
Protocol Configuration Options, and Attach
Type = "handover".
The Address Allocation Preference option
contained in the Protocol Configuration
Options indicates whether the UE wants to
perform the IP address allocation during the
attach procedure or deferred IPv4 address
allocation. PDN Type indicates the UE's IP
capability (IPv4, IPv6 or IPv4/v6)
The SS transmits a VSNCP Configure-Ack
message.
The SS transmits a VSNCP Configure-Request
message including the PDN-ID configuration
option.
The UE transmits VSNCP Configure-Ack
message.
Optionally IPv4 address allocation by DHCPv4
may occur (depending on the Address
Allocation Preference indicated by the UE at
Step 19).
Optionally Link global IPv6 address
configuration by ICMPv6 may occur
(depending on the Address Allocation
Preference indicated by the UE at Step
19).solicitation message.
ETSI
-->
Stream:ConfigurationRequest
<--
Stream: ConfigurationResponse
-->
EMPA:ConfigurationRequest
<--
EMPA: ConfigurationResponse
-->
ConfigurationComplete
<-->
-
<-->
-
<-->
-
<-->
-
<-->
-
-->
VSNCP: Configure-Request
<--
VSNCP: Configure-Ack
<--
VSNCP: Configure-Request
-->
VSNCP :Configure-Ack
<-->
-
<-->
-
3GPP TS 36.523-3 version 13.2.0 Release 13
10.4.1.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
217
Detach on HRPD Cell
Table 10.4.1.2: Detach on HRPD Cell procedure
Step
1
2
3
10.5
Procedure
The UE transmits PPP:LCP TerminateRequest
The SS transmits PPP: LCP Terminate-Ack
the UE and SS perform Session update to
release the reservations
U-S
-->
Message Sequence
Message
LCP:Terminate-Request
<-<-->
LCP:Terminate-Ack
-
Postambles for NB-IoT test cases
This clause describes UE postamble states which can be used in the post condition of NB-IoT test cases defined in TS
36.523-1 [1]. The clause also specifies a set of procedures to bring the UE into these states.
10.5.1
UE postamble states and procedures for NB-IoT test cases
In order to bring the UE to switched/powered off state there are some procedures that need to be executed. The
identified procedures are shown in figure 10.5.1-1.
NB-IoT manual
selection (N5)
NB-IoT test
mode (N3)
NB-IoT
connected
(N2)
NB-IoT
deregistered
(N4)
P10.5.5
P10.5.3
P10.5.3
NB-IoT idle
(N1)
P10.5. 4
P10.5.2
Off
Figure 10.5.1-1: UE postamble states and procedures for NB-IoT
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
10.5.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
218
Switch/Power off procedure in State N1
10.5.2.1
Procedure
Table 10.5.2.1-1: Switch/Power off procedure
Step
Procedure
1
The UE is powered off or switched off, (see
ICS)
EXCEPTION: Steps 2a1 to 2a4 specify
behaviour if the UE supports pc_SwitchOnOff
UE transmits an RRCConnectionRequest-NB
message.
SS transmit an RRCConnectionSetup-NB
message.
The UE transmits an
RRCConnectionSetupComplete-NB message
to confirm the successful completion of the
connection establishment and to initiate the
Detach procedure by including the DETACH
REQUEST message.
The SS transmits an
RRCConnectionRelease-NB message
2a1
2a2
2a3
2a4
10.5.3
10.5.3.1
Message Sequence
Message
U-S
-
-
-
RRC: RRCConnectionRequest-NB
-->
RRC: RRCConnectionSetup-NB
<--->
RRC: RRCConnectionSetupCompleteNB
NAS: DETACH REQUEST
<--
RRCConnectionRelease-NB
Switch/Power off procedure in State N2 and N3
Procedure for N2 and N3
Table 10.5.3.1-1: Switch/Power off procedure
Step
1
2
3
10.5.4
10.5.4.1
Procedure
The UE is powered off or switched off (see
ICS)
The UE transmits DETACH REQUEST
The SS transmits an
RRCConnectionRelease-NB message
U-S
-->
<--
Message Sequence
Message
DETACH REQUEST
RRCConnectionRelease-NB
Switch/Power off procedure in State N4
Procedure
Table 10.5.4.1-1: Switch/Power off procedure
Step
Procedure
1
The UE is powered off or switched off (see
ICS)
ETSI
U-S
-
Message Sequence
Message
-
3GPP TS 36.523-3 version 13.2.0 Release 13
10.5.5
ETSI TS 136 523-3 V13.2.0 (2017-03)
219
Automatic selection mode procedure in State N5 (current cell,
neighbour cell)
10.5.5.1
Procedure
Table 10.5.5.1-1: Automatic selection mode procedure
Step
Procedure
1
Set UE to Automatic PLMN selection
mode.
The SS configures:
- the current cell as a “Non-Suitable Off
cell”
- the neighbour cell as a “Serving cell”
Generic test procedure in TS 36.508
subclause 8.1.5A.X is performed on the
neighbour cell
At the end of this test procedure sequence,
the UE is in end state NB-IoT idle (N1)
2
3
-
Message Sequence
Message
U-S
-
-
-
-
-
-
-
-
Editors Note: Subclause of generic test procedure introduced in R5-167185.
11
Guidelines on test execution
This clause provides the guidelines on test executions.
The restriction on test case execution as listed in this clause is due to the restriction of bandwidth to accommodate the
necessary number of radio frequencies for the specific operating Band as used by the test cases.
11.1
EUTRA single technology
This clause provides the guidelines for the test cases to be executed on the pure EUTRA test configuration.
A test case using more than one radio frequency, i.e. using the radio frequencies f2 or f3 or f4 specified in
TS 36.508 [3], shall avoid to be executed on operating:
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31.
The list containing such test cases is given below:
6.1.1.1, 6.1.1.2, 6.1.1.3, 6.1.1.6, 6.1.1.7, 6.1.1.8, 6.1.2.7, 6.1.2.8, 6.1.2.9, 6.1.2.11, 6.1.2.13, 6.1.2.15, 6.1.2.17,
6.1.2.18, 6.3.1, 6.3.5, 6.3.6, 6.3.9, 6.4.1, 6.4.2,
8.1.3.4, 8.1.3.5, 8.2.4.6, 8.2.4.26, 8.3.1.3, 8.3.1.3a, 8.3.1.4, 8.3.1.6, 8.3.1.9, 8.3.1.10, 8.3.1.11, 8.3.1.26, 8.3.1.27,
8.3.1.31, 8.3.4.2, 8.3.4.3, 8.3.4.5, 8.6.2.2, 8.6.2.3a, 8.6.2.8, 8.6.2.10, 8.6.2.11, 8.6.2.12, 8.6.4.2, 8.6.4.3, 8.6.4.4,
8.6.4.8, 8.6.4.9, 8.6.4.10, 8.6.6.2, 8.6.6.5, 8.6.6.6, 8.6.6.7, 8.6.8.2, 8.6.8.6,
9.2.1.1.1a, 9.2.1.1.7, 9.2.1.1.13, 9.2.1.1.15, 9.2.1.1.16, 9.2.1.2.1, 9.2.1.2.10, 9.2.1.2.12, 9.2.1.2.14, 9.2.3.2.1,
9.2.3.2.12, 9.2.3.2.15, 9.2.3.2.16,
11.2.6, 11.2.7,
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
220
ETSI TS 136 523-3 V13.2.0 (2017-03)
13.4.1.2,
17.4.1, 17.4.2, 17.4.3,
21.3.1, 21.3.2, 21.3.3, 21.3.7, 21.3.10, 21.3.11, 21.3.12.
A test case using more than two radio frequencies, i.e. using the radio frequencies f3 or f4 specified in TS 36.508 [3],
shall avoid to be executed on operating:
Band 6,
Band 11,
Band 14,
Band 17 with 5MHz bandwidth,
Band 23 with 10MHz bandwidth,
Band 30,
Band 38,
Band 39
The list containing such test cases is given below:
6.1.1.1, 6.1.1.2, 6.1.1.3, 6.1.1.6, 6.1.1.7, 6.1.1.8, 6.1.2.7, 6.1.2.8, 6.1.2.9, 6.1.2.15, 6.3.5
8.1.3.5, 8.3.1.4, 8.6.4.3,
9.2.1.1.1a, 9.2.1.1.7, 9.2.1.1.15,
11.2.7.
A test case using more than three radio frequencies, i.e. using the radio frequency f4 specified in TS 36.508 [3], shall
avoid to be executed on operating:
Band 12 with 5MHz bandwidth,
Band 19,
Band 20,
Band 21,
Band 27,
Band 34,
Band 70.
The list containing such test cases is given below:
6.1.1.1, 6.1.1.2, 6.1.1.6, 6.1.1.8,
9.2.1.1.7.
11.1.1
Replacement of test case execution
In case of bandwidth limitation for accommodation of more frequencies, a number of test cases can be replaced with the
corresponding mirror test cases without affecting the test coverage. The table 11.1.1-1 shows the possible replacements.
Only one of the paired test cases is required for execution.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
221
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 11.1.1-1: Replacement of test cases
Original test case
6.1.1.1
6.1.1.2
6.1.1.3
6.1.1.6
6.1.2.7
6.1.2.8
6.1.2.9
8.3.1.9
8.3.1.11
9.2.1.1.1a
9.2.1.1.7
9.2.1.1.13
9.2.1.1.15
9.2.1.1.16
Replacing test case
6.1.1.1b
6.1.1.2a
6.1.1.3b
6.1.1.6a
6.1.2.7a
6.1.2.8a
6.1.2.9a
8.3.1.9a
8.3.1.11a
9.2.1.1.1b
9.2.1.1.7a
9.2.1.1.13a
9.2.1.1.15a
9.2.1.1.16a
11.2 EUTRA - UTRA - GERAN
This clause contains the guidelines for the EUTRA interRAT test cases to be executed on the different test
configurations: with only UTRA configured, with only GERAN configured or with UTRA-GERAN both configured.
Whether or not an EUTRA frequency band overlaps the UTRA band, the dependency will affect the restrictions of the
test execution on this band.
NOTE:
11.2.1
The case where an EUTRA band overlaps a GSM band is not considered.
UTRA configured – GERAN not configured
This clause provides the guidelines for the EUTRA interRAT test cases where UTRA is configured, while GERAN is
either not needed or not configured.
11.2.1.1
EUTRA band overlapping UTRA band
The restriction on test case execution as listed in this clause is due to the bandwidth of an EUTRA Band
accommodating the necessary number of EUTRA or EUTRA, UTRA radio frequencies if an E-UTRA band overlaps
the UTRA Band. A test case using more than one radio frequency, on the same EUTRA and UTRA band, shall avoid to
be executed on operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31.
The list containing such test cases is given below:
6.2.1.2, 6.2.1.3, 6.2.2.1, 6.2.2.5, 6.2.2.8, 6.2.3.3, 6.2.3.3a, 6.2.3.4, 6.2.3.4a, 6.2.3.5, 6.2.3.5a, 6.2.3.6, 6.2.3.13,
6.2.3.31, 6.2.3.32, 6.2.3.33, 6.2.4.1, 6.2.4.2, 6.2.4.3, 6.2.4.4, 6.2.4.5, 6.2.4.6, 6.2.4.7, 6.3.3, 6.3.4, 6.3.7, 6.4.3,
6.4.4, 6.4.5, 6.4.6,
8.1.3.6, 8.1.3.6a, 8.1.3.7, 8.3.2.3, 8.3.2.3a, 8.3.2.4, 8.3.3.2, 8.3.4.4, 8.4.1.2, 8.4.1.4, 8.4.1.5, 8.4.2.2, 8.4.2.4, 8.5.2.1,
8.6.3.1, 8.6.3.4, 8.6.5.1, 8.6.5.1a, 8.6.5.4, 8.6.7.1, 8.6.7.4, 8.6.9.1, 8.6.9.2, 8.6.10.1, 8.7.1,
9.2.1.1.11, 9.2.1.1.12, 9.2.1.2.1b, 9.2.1.2.1c, 9.2.1.2.1d, 9.2.1.2.5, 9.2.1.2.8, 9.2.1.2.9, 9.2.1.2.11, 9.2.1.2.13,
9.2.1.2.15, 9.2.2.1.3, 9.2.2.1.10, 9.2.3.1.6, 9.2.3.1.10, 9.2.3.1.11, 9.2.3.1.12, 9.2.3.1.15, 9.2.3.1.15a, 9.2.3.1.17,
9.2.3.1.18, 9.2.3.1.18a, 9.2.3.2.1a, 9.2.3.2.1b, 9.2.3.2.1c, 9.2.3.2.3, 9.2.3.2.5, 9.2.3.2.6, 9.2.3.2.7, 9.2.3.2.8,
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
222
ETSI TS 136 523-3 V13.2.0 (2017-03)
9.2.3.2.9, 9.2.3.2.11, 9.2.3.2.13, 9.2.3.2.14, 9.2.3.3.1, 9.2.3.3.2, 9.2.3.3.3, 9.2.3.3.4, 9.2.3.3.5, 9.2.3.3.5a, 9.3.1.4,
9.3.1.5, 9.3.1.6,
11.2.10, 11.2.11,
13.1.2, 13.1.2a, 13.1.3, 13.1.4, 13.1.5, 13.1.15, 13.1.16, 13.3.2.1, 13.4.2.1, 13.4.2.4, 13.4.3.1, 13.4.3.2, 13.4.3.4,
13.4.3.6, 13.4.3.7, 13.4.3.8, 13.4.3.9, 13.4.3.10, 13.4.3.11, 13.4.3.13, 13.4.3.14, 13.4.3.15, 13.4.3.16, 13.4.3.18,
13.4.3.19, 13.4.3.20.
A test case using more than two radio frequencies on the same EUTRA and UTRA band shall avoid to be executed on
operating:
Band 6,
Band 11,
Band 14,
Band 17 with 5MHz bandwidth,
Band 23 with 10MHz bandwidth,
Band 38,
Band 39.
The list containing such test cases is given below:
6.2.1.2, 6.2.1.3,
8.6.3.4, 8.6.5.1a, 8.6.7.4,
9.2.1.2.9, 9.2.1.2.11, 9.2.1.2.13, 9.2.3.1.15, 9.2.3.1.18, 9.2.3.2.5, 9.2.3.2.6, 9.2.3.2.7, 9.2.3.2.8, 9.2.3.2.11, 9.2.3.2.13,
9.2.3.2.14.
A test case using more than three radio frequencies, on the same EUTRA and UTRA band shall avoid to be executed on
operating
Band 12 with 5MHz bandwidth,
Band 19,
Band 20,
Band 21,
Band 27,
Band 34,
Band 70.
The list containing such test cases is given below:
9.2.1.2.13, 9.2.3.2.13.
11.2.1.2
EUTRA band not overlapping UTRA band
The restriction on test case execution as listed in this clause is due to the bandwidth of an EUTRA Band
accommodating the necessary number of EUTRA radio frequencies. A test case using more than one radio frequency
shall avoid to be executed on E-UTRA operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
223
ETSI TS 136 523-3 V13.2.0 (2017-03)
Band 18,
Band 31.
The list containing such test cases is given below:
6.2.1.2, 6.2.1.3,
8.6.3.4, 8.6.5.1a, 8.6.7.4,
9.2.1.2.9, 9.2.1.2.11, 9.2.1.2.13, 9.2.3.1.15, 9.2.3.1.18, 9.2.3.2.5, 9.2.3.2.6, 9.2.3.2.7, 9.2.3.2.8, 9.2.3.2.11, 9.2.3.2.13,
9.2.3.2.14,
A test case using more than two radio frequencies shall avoid to be executed on E-UTRA operating
Band 6,
Band 11,
Band 14,
Band 17 with 5MHz bandwidth,
Band 23 with 10MHz bandwidth,
Band 30,
Band 38,
Band 39.
The list containing such test cases is given below:
9.2.1.2.13, 9.2.3.2.13.
11.2.2
GERAN configured - UTRA not configured
This clause provides the guidelines for the EUTRA/GERAN test cases where UTRA is either not needed or not
configured. The restriction on test case execution as listed in this clause is due to the restriction of bandwidth of an
EUTRA Band accommodating the necessary number of EUTRA radio frequencies.
A test case using more than one radio frequency shall avoid to be executed on E-UTRA operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31
The list containing such test cases is given below:
6.2.1.4, 6.2.3.17, 6.2.3.18,
8.3.2.2,
9.2.1.2.9, 9.2.1.2.11, 9.2.1.2.13, 9.2.3.1.15, 9.2.3.1.18, 9.2.3.2.5, 9.2.3.2.6, 9.2.3.2.7, 9.2.3.2.8, 9.2.3.2.11, 9.2.3.2.13,
9.2.3.2.14.
A test case using more than two radio frequencies, i.e. using the radio frequencies f3 or f4 specified in TS 36.508 [3],
shall avoid to be executed on operating:
Band 6,
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
224
ETSI TS 136 523-3 V13.2.0 (2017-03)
Band 11,
Band 14,
Band 17 with 5MHz bandwidth,
Band 23 with 10MHz bandwidth,
Band 30,
Band 38,
Band 39
The list containing such test cases is given below:
9.2.1.2.13, 9.2.3.2.13.
11.2.3
Neither UTRA nor GERAN configured
Certain EMM test cases can be executed as EUTRA_Only configuration despite of UTRA or GERAN test branches
included in the test cases. The restriction on test case execution as listed in this clause is due to the bandwidth of an
EUTRA Band accommodating the necessary number of EUTRA radio frequencies.
A test case using more than one radio frequency shall avoid to be executed on E-UTRA operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31.
The list containing such test cases is given below:
9.2.3.1.15, 9.2.3.1.18.
11.2.4
Both UTRA and GERAN configured
This clause provides the guidelines for the EUTRA - UTRA - GERAN test cases where three RAT technologies are
simultaneously configured.
11.2.4.1
EUTRA band overlapping UTRA band
The restriction on test case execution as listed in this clause is due to the bandwidth of an EUTRA Band
accommodating the necessary number of EUTRA or EUTRA, UTRA radio frequencies if an E-UTRA band overlaps
the UTRA Band.
A test case using more than one radio frequency shall avoid to be executed on E-UTRA operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31.
The list containing such test cases is given below:
6.2.1.1, 8.3.2.5, 8.3.2.6,
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
225
ETSI TS 136 523-3 V13.2.0 (2017-03)
9.2.1.2.6, 9.2.1.2.7,
11.2.8
A test case using more than two radio frequencies, i.e. using the radio frequencies f3 or f4 specified in TS 36.508 [3],
shall avoid to be executed on operating:
Band 6,
Band 11,
Band 14,
Band 17 with 5MHz bandwidth,
Band 23 with 10MHz bandwidth,
Band 38
Band 39
The list containing such test cases is given below:
6.2.1.1.
11.2.4.2
EUTRA band not overlapping UTRA band
The restriction on test case execution as listed in this clause is due to the restriction of bandwidth of an EUTRA Band
accommodating the necessary number of EUTRA radio frequencies.
A test case using more than one radio frequency shall avoid to be executed on E-UTRA operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31.
The list containing such test cases is given below:
6.2.1.1
11.2.5
Replacement of test case execution
In case of bandwidth limitation for accommodation of more frequencies, a number of test cases can be replaced with the
corresponding mirror test cases without affecting the test coverage. The table 11.2.1.5-1 shows the possible
replacements. Only one of the paired test cases is required for execution.
Table 11.2.5-1: Replacement of interRAT test cases
Original test case
9.2.3.1.15
Replacing test case
9.2.3.1.15a
9.2.3.1.18a
9.2.3.1.18
11.3
EUTRA inter-band
The restriction on test case execution as listed in this clause is due to the restriction of bandwidth of an EUTRA band
accommodating the necessary number of EUTRA radio frequencies. The inter-band test includes also EUTRA FDDTDD and inter-band carrier aggregation tests.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
11.3.1
226
ETSI TS 136 523-3 V13.2.0 (2017-03)
Primary operating band
A test case using more than one radio frequency on the first operating band, shall avoid to be executed on operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31.
The list containing such test cases is given below:
6.1.2.15a, 8.1.3.12.
11.3.2
Secondary operating band for inter-band cells
Test case using more than one radio frequency, on the second operating band, shall avoid to be executed on operating
Band 12 with 10MHz bandwidth,
Band 13,
Band 17 with 10MHz bandwidth,
Band 18,
Band 31.
The list containing such test cases is given below:
6.1.1.1a, 6.1.1.3a, 6.1.1.4a, 6.1.2.16, 8.1.3.11a, 8.1.3.12b, 8.2.4.13a, 8.2.4.14a, 8.3.1.12a, 8.3.1.14a
11.3.3
Replacement of test case execution
In case of bandwidth limitation for accommodation of more frequencies, a number of test cases can be replaced with the
corresponding mirror test cases without affecting the test coverage. The table 11.3.3-1 shows the possible replacements.
Only one of the paired test cases is required for execution.
Table 11.3.3-1: Replacement of test cases
Original test case
8.1.3.12
11.4
Replacing test case
8.1.3.12b
EUTRA CA
The restriction on CA test case execution as listed in this clause is due to the restriction of bandwidth of an EUTRA CA
band accommodating the necessary number of EUTRA radio frequencies.
11.4.1
CA contiguous Intra-band operation
Test case using more than two radio frequencies, i.e. using the radio frequencies f3 or f4 specified in TS 36.508 [3],
shall avoid to be executed on E-UTRA CA Configuration:
CA_5B,
CA_23B,
CA_38C,
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
227
ETSI TS 136 523-3 V13.2.0 (2017-03)
CA_39C,
CA_70C.
The list containing such test cases is given below:
8.2.4.19.1, 8.2.4.21.1
The following test cases using SCell on f2 are not applicable to be run when executed in the band combinations
CA_70C:
7.1.2.10.1,
7.1.2.11.1,
7.1.4.20.1,
8.2.2.7.1,
8.2.4.17.1,
8.2.4.20.1,
8.2.4.23.1,
8.3.1.17.1,
8.3.1.18.1
11.4.2
CA Inter-band operation
Test case using more than one radio frequency on the primary band, i.e. using the radio frequency f2 specified in TS
36.508 [3], shall avoid to be executed on E-UTRA CA Configuration:
CA_8A-11A,
CA_12A-25A,
CA_12A-30A,
CA_18A-28A,
CA_19A-21A,
CA_19A-28A,
CA_19A-42A,
CA_19A-42C,
CA_21A-42C,
and on E-UTRA CA switched configuration
CA_1A-18A,
CA_1A-19A,
CA_1A-21A,
CA_2A-12A,
CA_2A-13A,
CA_2A-17A,
CA_2A-29A,
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
228
ETSI TS 136 523-3 V13.2.0 (2017-03)
CA_2A-30A,
CA_3A-19A,
CA_4A-12A,
CA_4A-13A,
CA_4A-17A,
CA_4A-29A,
CA_4A-30A,
CA_5A-12A,
CA_5A-13A,
CA_5A-17A,
CA_5A-29A,
CA_5A-30A,
CA_7A-12A,
CA_8A-11A,
CA_11A-18A,
CA_12A-30A,
CA_19A-21A,
CA_20A-31A,
CA_29A-30A
The list containing such test cases is given below:
8.2.4.19.2
Test case using more than one radio frequency on the primary band, i.e. using the radio frequency f2 or f6 (depending
upon the Cell being used) specified in TS 36.508 [3], shall avoid to be executed on E-UTRA CA Configuration:
CA_8A-11A,
CA_19A-21A,
CA_12A_30A
and on E-UTRA CA switched configuration
CA_8A-11A,
CA_19A-21A,
CA_12A_30A,
CA_29A-30A
The list containing such test cases is given below:
8.2.4.21.2
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
229
ETSI TS 136 523-3 V13.2.0 (2017-03)
These test cases can be run with switched allocation of PCell and SCell as specified in TS 36.508 [3] clause 6.2.3.2
(NOTE 3 and 4).
The following test cases are not applicable to be run when executed in the band combinations CA_2A-29A and
CA_4A-29A, CA_5A-29A, CA_20A-32A, CA_23A-29A, CA_20A-67A and on E-UTRA CA switched configuration
CA_29A-30A:
7.1.2.10.2,
7.1.2.11.2,
7.1.4.20.2,
8.2.2.7.2,
8.2.4.17.2,
8.2.4.20.2,
8.2.4.23.2,
8.3.1.17.2,
8.3.1.18.2
The 3DL CA test cases can be run on 3CCs FDD-TDD band combinations, they are using more than one radio
frequency on the primary band, i.e. using the radio frequency f2 specified in TS 36.508 [3], shall avoid to be executed
on E-UTRA CA Configuration:
CA_19A-42C,
CA_21A-42C
The list containing such test cases is given below:
7.1.2.11.4
11.4.3
CA non-contiguous Intra-band operation
Test case using more than two radio frequencies, i.e. using the radio frequencies f3 specified in TS 36.508 [3], shall
avoid to be executed on E-UTRA CA Configuration:
CA_5A-5A,
CA_23A-23A
The list containing such test cases is given below:
8.2.4.19.3
8.2.4.21.3
11.5
EUTRA MFBI
The following EUTRA MFBI test cases shall be executed using the combinations specified in Table 11.5-1 for
px_OverlappingNotSupportedFrequencyBand_MFBI and px_MFBI_FrequencyBand:
6.1.2.19, 6.1.2.20, 6.1.2.21, 6.1.2.22, 6.2.3.34, 6.2.3.35
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
230
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table 11.5-1: Operating and MFBI EUTRA bands combinations
px_OverlappingNotS
px_MFBI_FrequencyBand (Note)
upportedFrequencyB
and_MFBI
2
25
3
9
4
10
5
18, 19, 26
9
3
10
4
12
17
17
12
18
5, 26, 27
19
5, 26
25
2
26
5, 18, 19, 27
27
18, 26
33
39
38
41
39
33
41
38
Note: The UE supports one or more of the listed MFBI bands and does not
support at least one overlapping band. If the UE supports all
overlapping bands, these test cases are not applicable.
Test case 6.1.2.20 is not applicable to be run when executed in the band combination 5 & 18.
For test case 6.2.3.34 additionally the UTRA band combinations specified in Table 11.5-2 for
px_UTRAN_OverlappingNotSupportedFrequencyBandMFBI and px_MFBI_UTRAN_FrequencyBand shall also be
applicable
Table 11.5-2: Operating and MFBI UTRA bands combinations
px_UTRAN_Overlapp
px_MFBI_UTRAN_FrequencyBand (Note)
ingNotSupportedFre
quencyBandMFBI
2
25
3
9
4
10
5
18, 19, 26
9
3
10
4
18
5, 26
19
5, 26
25
2
26
5, 18, 19
Note: The UE supports one or more of the listed MFBI bands and does not
support at least one overlapping band. If the UE supports all
overlapping bands, these test cases are not applicable.
The MFBI test case 6.1.2.23 shall be executed using the combinations specified in Table 11.5-3 for
px_ePrimaryFrequencyBand, px_MFBI_FrequencyBand and px_OverlappingNotSupportedFrequencyBandMFBI
Table 11.5-3: Operating and MFBI EUTRA bands combinations
px_ePrimaryFrequencyBand
px_MFBI_FrequencyBand
39
38
ETSI
px_OverlappingNotSupportedFreq
uencyBandMFBI
41
3GPP TS 36.523-3 version 13.2.0 Release 13
11.6
231
ETSI TS 136 523-3 V13.2.0 (2017-03)
EUTRA DC
The restriction on DC test case execution as listed in this clause is due to the restriction of bandwidth of an EUTRA DC
band accommodating the necessary number of EUTRA radio frequencies.
Test case using more than one radio frequency on the primary band, i.e. using the radio frequency f2 specified in TS
36.508 [3], shall avoid to be executed on E-UTRA DC inter-band configuration:
DC_19A-21A,
and on E-UTRA DC switched configuration
DC_1A-19A,
DC_1A-21A,
DC_2A-13A,
DC_3A-19A,
DC_4A-12A,
DC_4A-13A,
DC_4A-17A,
DC_5A-12A,
DC_19A-21A
The list containing such test cases is given below:
8.2.4.25.1, 8.2.4.25.2, 8.2.4.25.3, 8.2.4.25.4, 8.2.4.25.5, 8.2.4.25.6, 8.2.4.25.7
Test cases using more than one radio frequency on the secondary band, i.e. using the radio refuency f6 specified in TS
36.508 [3], shall avoid to be executed on E-UTRA DC inter-band configurations:
DC_1A-19A,
DC_1A-21A,
DC_2A-13A,
DC_3A-19A,
DC_4A-12A,
DC_4A-13A,
DC_4A-17A,
DC_5A-12A,
DC_19A-21A
and on E-UTRA DC switched configuration
DC_19A-21A
The list containing such test cases is given below:
8.5.1.8.1, 8.5.1.8.2
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
232
ETSI TS 136 523-3 V13.2.0 (2017-03)
Annex A (normative):
Test Suites
This annex contains the approved TTCN Test Suites. The test suites have been produced using the Testing and Test
Control Notation version 3 (TTCN3) according to ES 201 873-1 [13].
A.1
Baseline of specifications
Table A.1 shows the baseline of the relevant cores specifications and the test specifications which the delivered TTCN
test suites are referred to.
Table A.1: References of the test and Core specifications
Core specifications
baseline
Test specifications
A.2
TS 36.331 [19]
TS 24.301 [21]
TS 36.508 [3]
TS 36.509 [4]
TS 36.523-1 [1]
TS 36.523-2 [2]
E-UTRA Test Suites
Table A.2 lists all approved test cases.
For a given test case, the following variants are distinguished (if applicable):
- FDD: E-UTRA FDD mode; and UTRA FDD mode in case the test case is Inter-RAT with UTRA cell(s).
- TDD: E-UTRA TDD mode; and UTRA TDD mode in case the test case is Inter-RAT with UTRA cell(s).
- T/F: E-UTRA TDD mode and UTRA FDD mode; only applicable to Inter-RAT test cases with UTRA cell(s).
An "X" in columns FDD, TDD or T/F indicates the test case is approved for the respective variant.
An "-" in columns FDD, TDD or T/F indicates the test case is not applicable to the respective variant.
Table A.2: E-UTRA/EPS TTCN test cases
Test case
Description
6.1.1.1
PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN/Automatic mode
6.1.1.1a
PLMN selection / Automatic mode / between FDD and TDD
6.1.1.1b
PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
Single Frequency operation
6.1.1.2
PLMN selection of “Other PLMN/access technology combinations” / Automatic mode
6.1.1.2a
PLMN selection of “Other PLMN/access technology combinations” / Automatic mode /
Single Frequency operation
6.1.1.3
Cell reselection of ePLMN in manual mode
6.1.1.3a
Cell reselection of ePLMN in manual mode / between FDD and TDD
6.1.1.3b
Cell reselection of ePLMN in manual mode / Single Frequency operation
6.1.1.4
PLMN selection in shared network environment / Automatic mode
6.1.1.4a
PLMN selection in shared network environment / Automatic mode / between FDD and TDD
6.1.1.6
PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
User reselection
6.1.1.6a
PLMN selection of RPLMN, HPLMN/EHPLMN, UPLMN and OPLMN / Automatic mode /
User reselection / Single Frequency operation
6.1.1.7
PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer
6.1.1.7a
PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer / Single Frequency
ETSI
FDD
X
X
X
TDD
X
X
X
T/F
-
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
X
X
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
233
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
FDD
TDD
T/F
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
-
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
-
X
X
-
X
X
-
X
X
X
X
X
-
X
X
-
X
X
X
X
X
X
X
-
operation
6.1.1.8
6.1.1.9
6.1.2.2
6.1.2.2a
6.1.2.2b
6.1.2.3
6.1.2.3a
6.1.2.4
6.1.2.5
6.1.2.6
6.1.2.7
6.1.2.7a
6.1.2.8
6.1.2.8a
6.1.2.9
6.1.2.9a
6.1.2.10
6.1.2.11
6.1.2.12
6.1.2.13
6.1.2.14
6.1.2.15
6.1.2.15a
6.1.2.15b
6.1.2.16
6.1.2.17
6.1.2.18
6.1.2.19
6.1.2.20
6.1.2.21
6.1.2.22
6.1.2.23
6.2.1.1
6.2.1.2
6.2.1.3
6.2.1.4
6.2.1.6
6.2.2.1
6.2.2.2
6.2.2.3
6.2.2.4
6.2.2.5
6.2.2.6
6.2.2.7
6.2.2.8
6.2.3.1
6.2.3.1a
PLMN selection of RPLMN or (E)HPLMN / Automatic mode
PLMN selection of RPLMN or (E)HPLMN; Manual mode
Cell selection, Qrxlevmin
Cell selection / Qqualmin
Cell selection / UE Cat 0 not allowed
Cell selection/Intra E-UTRAN/Serving cell becomes non-suitable (S<0 or barred)
Cell selection / Intra E-UTRAN / Serving cell becomes non-suitable (Srxlev > 0 and Squal
<0)
Cell reselection
Cell reselection for inter-band operation
Cell reselection using Qhyst, Qoffset and Treselection
Cell reselection/Equivalent PLMN
Cell reselection / Equivalent PLMN / Single Frequency operation
Cell reselection using cell status and cell reservations/Access control class 0 to 9
Cell reselection using cell status and cell reservations / Access control class 0 to 9 / Single
Frequency operation
Cell reselection using cell status and cell reservations/Access control class 11 to15
Cell reselection using cell status and cell reservations / Access control class 11 to 15 /
Single Frequency operation
Cell reselection in shared network environment
Inter-frequency cell reselection
Cell reselection / Cell-specific reselection parameters provided by the network in a
neighbouring cell list
Cell re-selection, Sintrasearch, Snonintrasearch
Speed-dependent cell reselection
Inter-frequency cell reselection according to cell reselection priority provided by SIBs
Inter-frequency cell reselection according to cell reselection priority provided by SIBs /
Between FDD and TDD
Inter-band cell reselection according to cell reselection priority provided by SIBs
Cell reselection / interband operation / Between FDD and TDD
Cell reselection for Squal to check against SIntraSearchQ and SnonIntraSearchQ
Inter-frequency cell reselection based on common priority information with parameters
ThreshX, HighQ, ThreshX, LowQ and ThreshServing, LowQ
Intra-frequency cell reselection / MFBI
Inter-frequency cell reselection / MFBI
Inter-band cell reselection / MFBI
Cell reselection / MFBI / UE does not support multiBandInfoList
Inter-Band cell reselection / MFBI frequency band priority adjustment/inter-band CA
Inter-RAT PLMN selection / Selection of correct RAT for OPLMN / Automatic mode
Inter-RAT PLMN selection / Selection of correct RAT for UPLMN / Automatic mode
Inter-RAT PLMN selection / Selection of correct PLMN and RAT in shared network
environment / Automatic mode
Inter-RAT PLMN selection / Selection of correct RAT from the OPLMN list / Manual mode
Inter-RAT background HPLMN search / Search for correct RAT for HPLMN / Automatic
mode
Inter-RAT cell selection/From E-UTRA RRC_IDLE to UTRA_Idle/Serving cell becomes nonsuitable
Inter-RAT cell selection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_idle /
Serving cell becomes non-suitable
Inter-RAT cell selection / From E-UTRA RRC_IDLE to HRPD Idle / Serving cell becomes
non-suitable
Inter-RAT cell selection / From E-UTRA RRC_IDLE to 1xRTT Dormant / Serving cell
becomes non-suitable
Cell selection / No USIM
Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-UTRA RRC_IDLE /
Serving cell becomes non-suitable
Inter-RAT Cell selection / From GSM_Idle/GPRS Packet_idle to E-UTRA RRC_IDLE /
Serving cell is barred
Inter-RAT cell selection / From UTRA_Idle to E-UTRA RRC_IDLE / Serving cell becomes
non-suitable
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_Idle
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to GSM_Idle/GPRS Packet_Idle
(Squal < ThreshServing, LowQ, Srxlev > ThreshX, LowP and Srxlev > ThreshX, HighP)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
234
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
6.2.3.3
Inter-RAT cell reselection/From UTRA_Idle to E-UTRA RRC_IDLE
6.2.3.3a
Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE (QqualminEUTRA,
SqualServingCell < Threshserving,low2, SqualnonServingCell,x > Threshx, low2 and
SqualnonServingCell,x > Threshx, high2)
6.2.3.4
Inter-RAT cell reselection / From UTRA CELL_PCH state to E-UTRA RRC_IDLE
6.2.3.4a
Inter-RAT cell reselection / From UTRA_CELL_PCH state to E-UTRA RRC_IDLE based on
RSRQ+RSRP evaluation
6.2.3.5
Inter-RAT cell reselection/From E-UTRA RRC_IDLE to UTRA_Idle
6.2.3.5a
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle (Squal > ThreshX,
HighQ, Squal < ThreshServing, LowQ, Squal > ThreshX, LowQ and SnonIntraSearchQ)
6.2.3.6
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle according to RAT
priority provided by dedicated signalling
6.2.3.7
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is higher
reselection priority than E-UTRA
6.2.3.7a
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is higher
reselection priority than E-UTRA (Srxlev > ThreshX, HighP)
6.2.3.8
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is lower
reselection priority than E-UTRA
6.2.3.8a
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to HRPD Idle / HRPD cell is lower
reselection priority than E-UTRA (Squal < ThreshServing, LowQ and Srxlev > ThreshX,
LowP)
6.2.3.9
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant / 1xRTT cell is
higher reselection priority than E-UTRA
6.2.3.9a
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant / 1xRTT cell is
higher reselection priority than E-UTRA (Srxlev > ThreshX, HighP)
6.2.3.10
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant / 1xRTT cell is
lower reselection priority than E-UTRA
6.2.3.10a Inter-RAT cell reselection / From E-UTRA RRC_IDLE to 1xRTT Dormant / 1xRTT cell is
lower reselection priority than E-UTRA (Squal < ThreshServing, LowQ and Srxlev >
ThreshX, LowP)
6.2.3.13
Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE according to RAT
priority provided by dedicated signalling
6.2.3.14
Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA / Priority of EUTRA cells are higher than the serving cell
6.2.3.15
Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA / Priority of EUTRA cells are lower than the serving cell
6.2.3.16
Inter-RAT cell reselection / From GSM_Idle to E-UTRAN /based on H_PRIO criteria
6.2.3.17
Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA / Priority EUTRA cells
6.2.3.18
Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA / Blacklisted EUTRA cells
6.2.3.19
Inter-RAT cell redirection to E-UTRA cell from GSM TCH mode
6.2.3.21
Inter-RAT autonomous cell reselection GPRS Packet_transfer NC0 mode to E-UTRA
6.2.3.23
Inter-RAT cell reselection from GPRS Packet_transfer to E-UTRA in CCN mode / PACKET
CELL CHANGE CONTINUE
6.2.3.24
Inter-RAT cell reselection from GPRS Packet_transfer to E-UTRA in CCN mode / PACKET
CELL CHANGE ORDER
6.2.3.26
Inter-RAT autonomous cell reselection GPRS Packet_transfer NC1 mode to E-UTRA Cell
6.2.3.27
Inter-RAT cell selection from GPRS Packet_transfer to E-UTRA (NC2 mode)
6.2.3.28
Inter-RAT cell reselection from GPRS Packet_transfer to E-UTRA
6.2.3.29
Inter-RAT Cell Reselection from GPRS Packet_transfer NC1 mode to E-UTRA in CCN
mode (PACKET MEASUREMENT ORDER)
6.2.3.31
Inter-RAT cell reselection / From UTRA_Idle (low priority) to E-UTRA RRC_IDLE (high
priority) according to RAT priority provided by dedicated signalling
6.2.3.32
Inter-RAT cell re-selection / From E-UTRA RRC_IDLE to UTRA_Idle, Snonintrasearch
6.2.3.33
Inter-RAT cell reselection / From E-UTRA RRC_IDLE to UTRA_Idle / Squal based cell
reselection parameters are broadcasted in E-UTRAN / UE does not support Squal based
cell reselection in UTRAN
6.2.3.35
Inter-RAT cell reselection from UTRA to E-UTRA / MFBI
Inter-RAT absolute priority based reselection in UTRA CELL_FACH to E-UTRA RRC_IDLE (Higher
6.2.4.1
6.2.4.2
6.2.4.3
Priority Layers, Srxlev,x > Threshx,high and Srxlev,serv > Sprioritysearch1 and SqualServ >
Sprioritysearch2)
Inter-RAT absolute priority based reselection in UTRA CELL_FACH (Higher Priority Layers, no cell
reselection to E-UTRA RRC_IDLE when Srxlev,serv < Sprioritysearch1)
Inter-RAT absolute priority based reselection in UTRA CELL_FACH to E-UTRA RRC_IDLE (Higher
Priority Layers, Squal,x > Threshx,high2 and Srxlev,serv > Sprioritysearch1 and SqualServ >
ETSI
FDD
X
X
TDD
X
-
T/F
X
-
X
X
X
X
X
X
X
X
X
-
X
-
X
X
X
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
X
X
X
-
X
X
-
X
X
X
X
-
X
X
-
X
X
X
X
X
X
-
X
X
-
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
X
-
X
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
6.2.4.4
6.2.4.5
6.2.4.6
6.2.4.7
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.3.6
6.3.7
6.3.9
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5
6.4.6
6.4.7
7.1.1.1
7.1.1.1a
7.1.1.2
7.1.2.1
7.1.2.2
7.1.2.3
7.1.2.4
7.1.2.5
7.1.2.6
7.1.2.7
7.1.2.8
7.1.2.9
7.1.2.10.1
7.1.2.10.2
7.1.2.10.3
7.1.2.11.2
7.1.3.1
7.1.3.2
7.1.3.3
7.1.3.3a
7.1.3.4
7.1.3.5
7.1.3.6
7.1.3.7
7.1.3.9
7.1.3.11.1
235
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
Sprioritysearch2)
Inter-RAT absolute priority based reselection in UTRA CELL_FACH (lower priority) to E-UTRA
RRC_IDLE (higher priority) (All Layers, Srxlev,x > Threshx,high)
Inter-RAT absolute priority based reselection in UTRA CELL_FACH (lower priority) to E-UTRA
RRC_IDLE (higher priority) (All Layers, Squal,x >ThreshX,high2)
Inter-RAT absolute priority based reselection in UTRA CELL_FACH (higher priority) to E-UTRA
RRC_IDLE (lower priority) (All Layers, Srxlev,serv < Sprioritysearch1 , Srxlev,serv <Thresh serv,low
and Srxlev,x > ThreshX,low)
Inter-RAT absolute priority based reselection in UTRA CELL_FACH (higher priority) to E-UTRA
RRC_IDLE (lower priority) (All Layers, Srxlev,serv < Sprioritysearch1 , Squal,serv <Thresh serv,low2
&& Squal,x > ThreshX,low2)
Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-CSG cell to E-UTRA
RRC_IDLE CSG cell
Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA idle CSG cell
Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE CSG cell
Inter-RAT cell reselection / From UTRA CELL_PCH state to E-UTRA RRC_IDLE CSG cell
Manual support for CSG ID selection
Ignoring CSG cells in cell selection/reselection when allowed CSG list is empty or not
supported
Inter-RAT Cell reselection from E-UTRA idle non-CSG cell to a UTRA CSG cell
Manual CSG ID selection across PLMNs
Manual CSG ID selection / Hybrid cell whose CSG ID is not in the Allowed CSG list nor
Operator’s list
Inter-frequency cell reselection / From E-UTRA RRC_IDLE non-CSG cell to E-UTRA
RRC_IDLE member hybrid cell
Inter-RAT cell reselection / From E-UTRA RRC_IDLE non-CSG cell to UTRA_Idle member
hybrid cell
Inter-RAT cell reselection / From E-UTRA RRC_IDLE non-member hybrid cell to UTRA_Idle
member hybrid cell
Inter-RAT cell reselection / From UTRA_Idle to E-UTRA RRC_IDLE member hybrid cell
Inter-RAT cell reselection / From UTRA CELL_PCH to E-UTRA RRC_IDLE member hybrid
cell
Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA RRC_IDLE
member hybrid cell
CCCH mapped to UL SCH/ DL-SCH/Reserved LCID (Logical Channel ID)
CCCH mapped to UL SCH/ DL-SCH / UE Cat 0
DTCH or DCCH mapped to UL SCH/ DL-SCH/Reserved Logical Channel ID
Correct selection of RACH parameters/Random access preamble and PRACH resource
explicitly signalled to the UE by RRC/Non-contention based random access procedure
Correct selection of RACH parameters/Random access preamble and PRACH resource
explicitly signalled to the UE in PDCCH Order/Non-contention based random access
procedure
Correct selection of RACH parameters/Preamble selected by MAC itself/Contention based
random access procedure
Random access procedure/Successful
Random access procedure/MAC PDU containing multiple RARs
Maintenance of uplink time alignment
MAC contention resolution/Temporary C-RNTI
MAC contention resolution/C-RNTI
MAC backoff indicator
CA / Random access procedure / SCell / Intra-band Contiguous CA
CA / Random access procedure / SCell / Inter-band CA
CA / Random access procedure / SCell / Intra-band non-contiguous CA
CA / Maintenance of uplink time alignment / Multiple TA / Inter-band CA
Correct handling of DL assignment/Dynamic case
Correct handling of DL assignment / Semi-persistent case
MAC PDU header handling
MAC PDU header handling / UE with limited TB size
Correct HARQ process handling/DCCH and DTCH
Correct HARQ process handling/CCCH
Correct HARQ process handling/BCCH
MAC padding
MAC reset DL
CA / Correct HARQ process handling / DCCH and DTCH / P cell and Scell / Intra-band
Contiguous CA
ETSI
FDD
TDD
T/F
X
-
X
X
-
X
X
-
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
-
X
X
-
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
-
X
X
-
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
3GPP TS 36.523-3 version 13.2.0 Release 13
236
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
FDD
7.1.3.11.2 CA / Correct HARQ process handling / DCCH and DTCH / P cell and Scell / Inter-band CA
X
7.1.3.11.3 CA / Correct HARQ process handling / DCCH and DTCH / P cell and Scell / Intra-band non-Contiguous X
7.1.3.11.4
7.1.3.11.5
7.1.3.12
CA
FDD-TDD CA / Correct HARQ process handling / DCCH and DTCH / FDD PCell and TDD SCell
FDD-TDD CA / Correct HARQ process handling / DCCH and DTCH / TDD PCell and FDD SCell
TDD additional special subframe configuration / Special subframe pattern 9 with Normal
Cyclic Prefix / CRS based transmission scheme
TDD
X
T/F
-
X
X
-
X
-
7.1.3.12a
TDD additional special subframe configuration / Special subframe pattern 7 with Extended Cyclic Prefix
/ CRS based transmission scheme
-
X
-
7.1.3.13
TDD additional special subframe configuration / Special subframe pattern 9 with Normal
Cyclic Prefix / UE-specific reference signals based transmission scheme
-
X
-
7.1.3.13a
TDD additional special subframe configuration / Special subframe pattern 7 with Extended Cyclic Prefix
/ UE-specific reference signals based transmission scheme
-
X
-
7.1.4.1
7.1.4.2
7.1.4.3
7.1.4.4
7.1.4.5
Correct handling of UL assignment/Dynamic case
Correct handling of UL assignment / Semi-persistent case
Logical channel prioritization handling
Correct handling of MAC control information/Scheduling requests and PUCCH
Correct handling of MAC control information/Scheduling requests and random access
procedure
Correct handling of MAC control information/Buffer status/UL data arrive in the UE Tx buffer
and retransmission of BSR/Regular BSR
Correct handling of MAC control information/Buffer Status/UL resources are
allocated/Padding BSR
Correct handling of MAC control information / Buffer Status / UL resources are allocated /
Cancellation of Padding BSR
Correct handling of MAC control information/Buffer status/Periodic BSR timer expires
MAC padding
Correct HARQ process handling
MAC reset UL
MAC PDU header handling
Correct HARQ process handling / TTI bundling
UE power headroom reporting/Periodic reporting
UE power headroom Reporting/DL pathloss change reporting
CA / Correct handling of MAC control information / Buffer Status / UL data arrive in the UE
Tx buffer / Extended buffer size
CA / UE power headroom reporting / SCell activation and DL pathloss change reporting /
Extended PHR / Intra-band Contiguous
CA / UE power headroom reporting / SCell activation and DL pathloss change reporting /
Extended PHR / Inter-band CA
CA / Correct handling of MAC control information / Buffer status / Intra-band Contiguous CA
CA / Correct handling of MAC control information / Buffer status / Inter-band CA
CA / Correct handling of MAC control information / Buffer status / Intra-band nonContiguous CA
CA / UE power headroom reporting / Extended PHR
Correct HARQ process handling / TTI bundling with enhanced HARQ pattern
Correct HARQ process handling / TTI bundling without resource allocation restriction
Inter-TTI PUSCH hopping by uplink grant
Predefined intra-TTI PUSCH hopping (N_sb=1)
Predefined intra-TTI PUSCH hopping (N_sb=2/3/4)
Predefined inter-TTI PUSCH hopping (N_sb=1)
Predefined inter-TTI PUSCH hopping (N_sb=2/3/4)
DRX operation/Short cycle not configured/Parameters configured by RRC
DRX operation/Short cycle not configured/DRX command MAC control element reception
DRX operation / Short cycle configured / Parameters configured by RRC
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
X
-
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
X
-
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
X
-
7.1.4.6
7.1.4.7
7.1.4.7a
7.1.4.8
7.1.4.10
7.1.4.11
7.1.4.12
7.1.4.13
7.1.4.14
7.1.4.15
7.1.4.16
7.1.4.18
7.1.4.19.1
7.1.4.19.2
7.1.4.20.1
7.1.4.20.2
7.1.4.20.3
7.1.4.21
7.1.4.23
7.1.4.24
7.1.5.1
7.1.5.2
7.1.5.3
7.1.5.4
7.1.5.5
7.1.6.1
7.1.6.2
7.1.6.3
7.1.6.4
7.1.7.1.1
7.1.7.1.2
7.1.7.1.3
7.1.7.1.4
7.1.7.1.5
7.1.7.1.6
7.1.7.1.7
DRX Operation / Short cycle configured / DRX command MAC control element reception
DL-SCH transport block size selection/DCI format 1/RA type 0
DL-SCH transport block size selection/DCI format 1/RA type 1
DL-SCH transport block size selection/DCI format 1A/RA type 2/Localised VRB
DL-SCH transport block size selection/DCI format 1A/RA type 2/Distributed VRB
DL-SCH transport block size selection / DCI format 2A / RA type 0 / Two transport blocks
enabled / Transport block to codeword swap flag value set to 0
DL-SCH transport block size selection / DCI format 2A / RA type 1/ Two transport blocks
enabled / Transport block to codeword swap flag value set to 1
DL-SCH transport block size selection / DCI format 1 / RA type 0 / 256QAM
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
237
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
7.1.7.1.8
DL-SCH transport block size selection / DCI format 1 / RA type 1 / 256QAM
7.1.7.1.11 DL-SCH transport block size selection / DCI format 2A / RA type 0 / Two transport blocks enabled /
FDD
X
X
TDD
X
T/F
-
X
X
-
UL-SCH transport block size selection/DCI format 0
Periodic RI reporting using PUCCH / Category 1 UE / Transmission mode 3/4
CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element
reception / sCellDeactivationTimer/ Intra-band Contiguous CA
CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element
reception / sCellDeactivationTimer/ Inter-band CA
CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element
reception / sCellDeactivationTimer / Intra-band non-Contiguous CA
X
X
X
X
X
X
-
X
X
-
X
X
-
7.1.10.1
7.1.10.2
Sending SR on PUCCH with DMRS generated by using virtual cell identity / nPUCCH-Identity
7.1.10.2 Transmitting data on PUSCH with DMRS generated by using virtual cell identity / nPUSCHIdentity
X
X
X
X
-
7.2.2.1
7.2.2.2
7.2.2.3
7.2.2.4
7.2.2.5.1
7.2.2.5.2
7.2.2.6
7.2.2.7
UM RLC/Segmentation and reassembly/5-bit SN/Framing info field
UM RLC/Segmentation and reassembly/10-bit SN/Framing info field
UM RLC/Reassembly/5-bit SN/LI value > PDU size
UM RLC/Reassembly/10-bit SN/LI value > PDU size
UM RLC/5-bit SN/Correct use of sequence numbering
UM RLC/5-bit SN/Correct use of sequence numbering
UM RLC/Concatenation, segmentation and reassembly
UM RLC/In sequence delivery of upper layer PDUs without residual loss of RLC
PDUs/Maximum re-ordering delay below t-Reordering
UM RLC/In sequence delivery of upper layer PDUs without residual loss of RLC
PDUs/Maximum re-ordering delay exceeds t-Reordering
UM RLC/In sequence delivery of upper layer PDUs with residual loss of RLC
PDUs/Maximum re-ordering delay exceeds t-Reordering
UM RLC/Duplicate detection of RLC PDUs
UM RLC/RLC re-establishment procedure
AM RLC/Concatenation and reassembly
AM RLC/Segmentation and reassembly/No PDU segmentation
AM RLC/Segmentation and reassembly/Framing info field
AM RLC/Segmentation and reassembly/Different numbers of length indicators
AM RLC/Reassembly/LI value > PDU size
AM RLC/Correct use of sequence numbering
AM RLC/Control of transmit window
AM RLC/Control of receive window
AM RLC/Polling for status
AM RLC/Receiver status triggers
AM RLC/Reconfiguration of RLC parameters by upper layers
AM RLC/In sequence delivery of upper layers PDUs
AM RLC/Re-ordering of RLC PDU segments
AM RLC/Re-transmission of RLC PDU without re-segmentation
AM RLC/Re-segmentation RLC PDU/SO, FI, LSF
AM RLC/Reassembly/AMD PDU reassembly from AMD PDU segments, Segmentation
Offset and Last Segment Flag fields
AM RLC/Duplicate detection of RLC PDUs
AM RLC/RLC re-establishment at RRC connection reconfiguration including
mobilityControlInfo IE
Maintenance of PDCP sequence numbers/User plane/RLC AM
Maintenance of PDCP sequence numbers/User plane/RLC UM/Short PDCP SN (7 bits)
Maintenance of PDCP sequence numbers/User plane/RLC UM/Long PDCP SN (12 bits)
Ciphering and deciphering/Correct functionality of EPS AS encryption algorithms/SNOW 3G
Ciphering and deciphering/Correct functionality of EPS UP encryption algorithms/SNOW 3G
Ciphering and deciphering/Correct functionality of EPS AS encryption algorithms/AES
Ciphering and deciphering/Correct functionality of EPS UP encryption algorithms/AES
Ciphering and deciphering / Correct functionality of EPS AS encryption algorithms / ZUC
Ciphering and deciphering / Correct functionality of EPS AS encryption algorithms / ZUC
Integrity protection/Correct functionality of EPS AS integrity algorithms/SNOW 3G
Integrity protection/Correct functionality of EPS AS integrity algorithms/AES
Integrity protection / Correct functionality of EPS AS integrity algorithms / ZUC
PDCP handover/Lossless handover/PDCP sequence number maintenance
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
7.1.7.1.12
7.1.7.2.1
7.1.8.1
7.1.9.1.1
7.1.9.1.2
7.1.9.1.3
7.2.2.8
7.2.2.9
7.2.2.10
7.2.2.11
7.2.3.1
7.2.3.2
7.2.3.3
7.2.3.4
7.2.3.5
7.2.3.6
7.2.3.7
7.2.3.8
7.2.3.9
7.2.3.10
7.2.3.13
7.2.3.14
7.2.3.15
7.2.3.16
7.2.3.17
7.2.3.18
7.2.3.20
7.2.3.21
7.3.1.1
7.3.1.2
7.3.1.3
7.3.3.1
7.3.3.2
7.3.3.3
7.3.3.4
7.3.3.5
7.3.3.6
7.3.4.1
7.3.4.2
7.3.4.3
7.3.5.2
Transport block to codeword swap flag value set to ’0’ / 256QAM
DL-SCH Transport Block Size selection / DCI format 2A / RA type 1 / Two transport blocks enabled /
Transport block to codeword swap flag value set to ’1’ / 256QAM
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
238
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
FDD
7.3.5.3
PDCP handover/Non-lossless handover/PDCP sequence number maintenance
X
7.3.5.4
PDCP handover/Lossless handover/PDCP status report to convey the information on
X
missing or acknowledged PDCP SDUs at handover
7.3.5.5
PDCP handover/In-order delivery and duplicate elimination in the downlink
X
7.3.6.1
PDCP discard
X
8.1.1.1
RRC/Paging for connection in idle mode
X
8.1.1.2
RRC/Paging for notification of BCCH modification in idle mode
X
8.1.1.3
RRC / Paging for connection in idle mode / Multiple paging records
X
8.1.1.4
RRC / Paging for connection in idle mode / Shared network environment
X
8.1.1.6
RRC/BCCH modification in connected mode
X
8.1.1.7
RRC / Paging / EAB active
X
8.1.2.2
RRC connection establishment/Reject with wait time
X
8.1.2.3
RRC connection establishment/Return to idle state after T300 timeout
X
8.1.2.5
RRC connection establishment/0% access probability for MO calls, no restriction for MO
X
signalling
8.1.2.6
RRC connection establishment / Non-zero percent access probability for MO calls, no
X
restriction for MO signalling
8.1.2.7
RRC connection establishment/0% access probability for AC 0 to 9, AC 10 is barred, AC 11
X
to 15 are not barred, access for UE with access class in the range 11 to 15 is allowed
8.1.2.8
RRC connection establishment / Range of access baring time
X
8.1.2.9
RRC Connection Establishment / 0% access probability for MO calls, non-zero percent
X
access probability for MO signalling
8.1.2.11
RRC connection establishment of emergency call
X
8.1.2.12
RRC connection establishment of emergency call / Limited Service
X
8.1.2.13
RRC connection establishment / 0% access probability for MO calls, 0% access probability
X
for MO signalling
8.1.2.14
RRC connection establishment / High speed flag
X
8.1.3.1
RRC connection release/Success
X
8.1.3.4
RRC connection release/Redirection to another E-UTRAN frequency
X
8.1.3.5
RRC connection release/Success/With priority information
X
8.1.3.6
RRC connection release/Redirection from E-UTRAN to UTRAN
X
8.1.3.6a
RRC connection release / Redirection from E-UTRAN to UTRAN / Pre-redirection info
X
8.1.3.7
RRC connection release / Redirection from UTRAN to E-UTRAN
X
8.1.3.8
RRC connection release / Redirection from E-UTRAN to GERAN
X
8.1.3.9
RRC connection release / Redirection from E-UTRAN to HRPD
X
8.1.3.10
RRC connection release / Redirection from E-UTRAN to 1xRTT
X
8.1.3.11
RRC connection release / Redirection to another E-UTRAN band
X
8.1.3.11a RRC connection release / Redirection to another E-UTRAN band / Between FDD and TDD
X
8.1.3.12
RRC connection release / Success / With priority information / Inter-band
X
8.1.3.12a RRC connection release / Success / With priority information / Inter-band / Between FDD
X
and TDD
8.1.3.12b RRC connection release / Success / With priority information / Inter-band(Single frequency
X
operation in source band)
8.2.1.1
RRC connection reconfiguration/Radio bearer establishment for transition from RRC_IDLE
X
to RRC_CONNECTED/Success/Default bearer/Early bearer establishment
8.2.1.3
RRC connection reconfiguration/Radio bearer establishment/Success/Dedicated bearer
X
X
8.2.1.5
RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE
to RRC CONNECTED / Success / Latency check
8.2.1.6
RRC connection reconfiguration / Radio bearer establishment for transition from RRC_IDLE
X
to RRC CONNECTED / Success / Latency check / SecurityModeCommand and
RRCConnectionReconfiguration transmitted in the same TTI
8.2.1.7
RRC connection reconfiguration/Radio bearer establishment/Success/SRB2
X
8.2.1.8
RRC connection reconfiguration / Radio bearer establishment / Success / Dedicated bearer
X
/ ROHC configured
8.2.2.1
RRC connection reconfiguration/Radio resource reconfiguration/Success
X
8.2.2.2
RRC connection reconfiguration/SRB/DRB reconfiguration/Success
X
8.2.2.3.1
CA / RRC connection reconfiguration / SCell addition/ modification/release / Success / Intra- X
band contiguous CA
8.2.2.3.2
CA / RRC connection reconfiguration / SCell addition/ modification/release / Success / Inter- X
band CA
8.2.2.3.3
CA / RRC connection reconfiguration / SCell addition/ modification/release / Success / Intra- X
band non-contiguous CA
8.2.2.4.1
CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band Contiguous
X
CA
ETSI
TDD
X
X
T/F
-
X
X
X
X
X
X
X
X
X
X
X
-
X
-
X
-
X
X
-
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
-
X
-
X
X
-
X
-
X
X
-
X
X
X
-
X
-
X
-
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
239
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
FDD
8.2.2.4.2
CA / RRC connection reconfiguration / SCell SI change / Success / Inter-band CA
X
8.2.2.4.3
CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band nonX
contiguous CA
8.2.2.5.1
CA / RRC connection reconfiguration / SCell addition without UL / Success / Intra-band
X
contiguous CA
8.2.2.5.2
CA / RRC connection reconfiguration / SCell addition without UL / Success / Inter-band CA
X
8.2.2.5.3
CA / RRC connection reconfiguration / SCell addition without UL / Success / Intra-band
X
non-contiguous CA
8.2.2.6.1
RRC connection reconfiguration/ UE Assistance Information/power preference indication
X
setup and release
8.2.2.6.2
RRC connection reconfiguration/ UE Assistance Information/power preference indication
X
release on connection re-establishment
8.2.2.6.3
RRC connection reconfiguration/ UE Assistance Information/T340 running
X
8.2.2.7.1
CA / RRC connection reconfiguration / sTAG addition/ modification/release / Success /
X
Intra-band Contiguous CA
8.2.2.7.2
CA / RRC connection reconfiguration / sTAG addition/ modification/release / Success /
X
Inter-band CA
8.2.2.7.3
CA / RRC connection reconfiguration / sTAG addition/ modification/release / Success /
Intra-band non-contiguous CA
8.2.2.8
RRC connection reconfiguration / SIB1 information / Success
X
8.2.3.1
RRC connection reconfiguration/Radio bearer release/Success
X
8.2.4.1
RRC connection reconfiguration/Handover/Success/Dedicated preamble
X
8.2.4.2
RRC connection reconfiguration/Handover/Success/Common preamble
X
8.2.4.3
RRC connection reconfiguration/Handover/Success/Intra-cell/Security reconfiguration
X
8.2.4.4
RRC connection reconfiguration/Handover/Failure/Intra-cell/Security reconfiguration
X
8.2.4.5
RRC connection reconfiguration/Handover/All parameters included
X
8.2.4.6
RRC connection reconfiguration/Handover/Success/Inter-frequency
X
8.2.4.7
RRC connection reconfiguration/Handover/Failure/Re-establishment successful
X
8.2.4.8
RRC connection reconfiguration / Handover / Failure / Re-establishment failure
X
8.2.4.9
RRC connection reconfiguration/Handover/Inter-band blind handover/Success
X
8.2.4.10
RRC connection reconfiguration / Handover / Between FDD and TDD
X
8.2.4.12
RRC connection reconfiguration / Handover / Setup and release of MIMO
X
8.2.4.13
RRC connection reconfiguration / Handover / Success (with measurement) / Inter-band
X
8.2.4.13a RRC connection reconfiguration / Handover / Success (with measurement) / Inter-band /
X
between FDD and TDD
8.2.4.14
RRC connection reconfiguration / Handover / Failure / Re-establishment successful / InterX
band
8.2.4.14a RRC connection reconfiguration / Handover / Failure / Re-establishment successful / InterX
band / between FDD and TDD
8.2.4.15
RRC connection reconfiguration / Handover / Failure / Re-establishment failure / Inter-band
X
8.2.4.15a RRC connection reconfiguration / Handover / Failure / Re-establishment failure / Inter-band
X
/ Between FDD and TDD
8.2.4.16.1 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band Contiguous
X
CA
8.2.4.16.2 CA / RRC connection reconfiguration / Setup and Change of MIMO / Inter-band CA
X
8.2.4.16.3 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band nonX
contiguous CA
8.2.4.17.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell
X
addition / Intra-band contiguous CA
8.2.4.17.2 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell
X
addition / Inter-band CA
8.2.4.17.3 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell
X
addition / Intra-band non-contiguous CA
8.2.4.18.1 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra‑ band
X
contiguous CA
8.2.4.18.2 CA / RRC connection reconfiguration / Handover / Success / SCell release / Inter‑ band
X
CA
8.2.4.18.3 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra‑ band
X
non-contiguous CA
8.2.4.19.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change/ Scell no
X
Change / Intra-band contiguous CA
8.2.4.19.2 CA / RRC connection reconfiguration / Handover / Success / PCell Change/ Scell no
X
Change / Inter-band CA
8.2.4.19.3 CA / RRC connection reconfiguration / Handover / Success / PCell Change/ Scell no Change / IntraX
ETSI
TDD
X
X
T/F
-
X
-
X
X
-
X
-
X
-
X
X
X
X
-
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
-
X
-
X
X
-
X
-
X
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
240
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
FDD
TDD
T/F
CA / RRC connection reconfiguration / Handover / Success / Scell Change / Intra-band
Contiguous CA
CA / RRC connection reconfiguration / Handover / Success / Scell Change / Inter-band CA
CA / RRC connection reconfiguration / Handover / Success / SCell Change / Intra-band
non-Contiguous CAChange / Intra-band non-contiguous CA
CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band
Contiguous CA
CA / RRC connection reconfiguration / Handover / Success / SCell release / Inter-band CA
CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band noncontiguous CA
RRC connection reconfiguration / Handover / MFBI / Target cell broadcasting information
disregarded by the UE
CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful /
Intra-band Contiguous CA
CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful /
Inter-band CA
CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful /
Intra-band non-Contiguous CA
Measurement configuration control and reporting/Intra E-UTRAN measurements/Event A1
Measurement configuration control and reporting/Intra E-UTRAN measurements/Event A2
Measurement configuration control and reporting/Intra E-UTRAN measurements/Two
simultaneous events A3 (intra and inter-frequency measurements)
Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A3 (intra and inter-frequency measurements) / RSRQ based
measurements
Measurement configuration control and reporting/Intra E-UTRAN measurements/Periodic
reporting (intra and inter-frequency measurements)
Measurement configuration control and reporting/Intra E-UTRAN measurements/Two
simultaneous event A3 (intra-frequency measurements)
Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A2 and A3 (inter-frequency measurements)
Measurement configuration control and reporting/Intra E-UTRAN
measurements/Blacklisting
Measurement configuration control and reporting/Intra E-UTRAN
measurements/Handover/IE measurement configuration present
Measurement configuration control and reporting/Intra E-UTRAN measurements/Intrafrequency handover/IE measurement configuration not present
Measurement configuration control and reporting / Intra E-UTRAN measurements / Intrafrequency handover / IE measurement configuration not present / Single Frequency
operation
Measurement configuration control and reporting/Intra E-UTRAN measurements/Interfrequency handover/IE measurement configuration not present
Measurement configuration control and reporting/Intra E-UTRAN
measurements/Continuation of the measurements after RRC connection re-establishment
Measurement configuration control and reporting / Intra Frequency measurements /
Continuation of the measurements after RRC connection re-establishment / Single
Frequency operation
Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A3 (Inter-band measurements)
Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A3 (inter-band measurements) / Between FDD and TDD
Measurement configuration control and reporting / Intra E-UTRAN measurements / Periodic
reporting (intra-frequency and inter-band measurements)
Measurement configuration control and reporting / Intra E-UTRAN measurements / Periodic
reporting (intra-frequency and inter-band measurements) / Between FDD and TDD
Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A2 and A3 (Inter-band measurements)
Measurement configuration control and reporting / Intra E-UTRAN measurements / Two
simultaneous events A2 and A3 (inter-band measurements) / Between FDD and TDD
Measurement configuration control and reporting / Intra E-UTRAN measurements / Interband handover / IE measurement configuration not present
Measurement configuration control and reporting / Intra E-UTRAN measurements / Interband handover / IE measurement configuration not present / Between FDD and TDD
Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
X
-
X
X
X
X
-
X
X
-
X
X
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
X
X
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
-
band non-contiguous CA
8.2.4.20.1
8.2.4.20.2
8.2.4.20.3
8.2.4.21.1
8.2.4.21.2
8.2.4.21.3
8.2.4.22
8.2.4.23.1
8.2.4.23.2
8.2.4.23.3
8.3.1.1
8.3.1.2
8.3.1.3
8.3.1.3a
8.3.1.4
8.3.1.5
8.3.1.6
8.3.1.7
8.3.1.8
8.3.1.9
8.3.1.9a
8.3.1.10
8.3.1.11
8.3.1.11a
8.3.1.12
8.3.1.12a
8.3.1.13
8.3.1.13a
8.3.1.14
8.3.1.14a
8.3.1.15
8.3.1.15a
8.3.1.16
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
8.3.1.16a
8.3.1.17.1
8.3.1.17.2
8.3.1.17.3
8.3.1.18.1
8.3.1.18.2
8.3.1.18.3
8.3.1.19
8.3.1.21
8.3.1.22.1
8.3.1.22.2
8.3.1.22.3
8.3.1.23
8.3.1.24
8.3.1.25
8.3.1.26
8.3.1.27
8.3.1.28
8.3.2.1
8.3.2.2
8.3.2.3
8.3.2.3a
8.3.2.4
8.3.2.5
8.3.2.6
8.3.2.7
8.3.2.8
8.3.2.9
8.3.2.10
8.3.2.11
8.3.3.1
8.3.3.2
8.3.3.3
241
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
FDD
Continuation of the measurements after RRC connection re-establishment / Inter-band
Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Continuation of the measurements after RRC connection re-establishment / Inter-band /
Between FDD and TDD
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Event A6 / Intra-band contiguous CA
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Event A6 / Inter-band CA
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Event A6 / Intra-band non-contiguous CA
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Additional measurement reporting / Intra-band contiguous CA
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Additional measurement reporting / Inter-band CA
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Additional measurement reporting / Intra-band non-contiguous CA
eICIC / Measurement configuration control and reporting / CSI change
X
eICIC / Measurement configuration control and reporting/Event A3 Handover / Neighbor
X
RSRP measurement configuration change
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Event A1 / Event A2 / Intra-band Contiguous CA
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Event A1 / Event A2 / Inter-band CA
CA / Measurement configuration control and reporting / Intra E-UTRAN measurements /
X
Event A1/Event A2 / Intra-band non-contiguous CA
Measurement configuration control and reporting / Intra E-UTRAN measurements / Event
X
A4
Measurement configuration control and reporting / Intra E-UTRAN measurements / Event
X
A5
Measurement configuration control and reporting / Intra E-UTRAN measurements / Event
X
A5 / RSRQ based measurements
Measurement configuration control and reporting / Intra E-UTRAN measurements / Event
X
A5 (Inter-frequency measurements)
Measurement configuration control and reporting / Intra E-UTRAN measurements / Event
X
A5 (Inter-frequency measurements) / RSRQ based measurements
eICIC / Measurement configuration control and reporting/Event A1 / RSRP and RSRQ
X
measurement / Serving ABS
Measurement configuration control and reporting / Inter-RAT measurements / Event B2 /
X
Measurement of GERAN cells
Measurement configuration control and reporting / Inter-RAT measurements / Periodic
X
reporting / Measurement of GERAN cells
Measurement configuration control and reporting/Inter-RAT measurements/Event
X
B2/Measurement of UTRAN cells
Measurement configuration control and reporting / Inter-RAT measurements / Event B2 /
X
Measurement of UTRAN cells / RSRQ based measurements
Measurement configuration control and reporting / Inter-RAT measurements / Periodic
X
reporting / Measurement of UTRAN cells
Measurement configuration control and reporting / Inter-RAT measurements / Periodic
X
reporting / Measurements of E-UTRAN, UTRAN and GERAN cells
Measurement configuration control and reporting / Inter-RAT measurements / Simultaneous X
A2 and two B2 / Measurements of E-UTRAN, UTRAN and GERAN cells
Measurement configuration control and reporting/Inter-RAT measurements/Event
X
B2/Measurement of HRPD cells
Measurement configuration control and reporting / Inter-RAT measurements / Periodic
X
reporting / Measurement of HRPD cells
Measurement configuration control and reporting / Inter-RAT measurements / Event B2 /
X
Measurement of 1xRTT cells
Measurement configuration control and reporting / Inter-RAT measurements / Periodic
X
reporting / Measurement of 1xRTT cells
Measurement configuration control and reporting / Inter-RAT Measurements / Event B1 /
X
Measurement of UTRAN cells
Measurement configuration control and reporting/SON/ANR/CGI reporting of E-UTRAN cell
X
Measurement configuration control and reporting / SON / ANR / CGI reporting of UTRAN
X
cell
Measurement configuration control and reporting / SON / ANR / CGI reporting of GERAN
X
ETSI
TDD
T/F
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
X
X
X
X
X
X
X
X
X
X
-
X
-
X
-
X
-
X
X
X
X
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
8.3.3.4
8.3.4.1
8.3.4.2
8.3.4.3
8.3.4.4
8.3.4.5
8.4.1.2
8.4.1.4
8.4.1.5
8.4.2.2
8.4.2.4
8.4.2.7.1
8.4.2.7.2
8.4.2.7.3
8.4.3.2
8.4.3.3
8.4.7.3
8.4.7.4
8.4.7.5
8.4.7.6
8.4.7.7
8.4.7.8
8.4.7.9
8.4.7.10
8.5.1.1
8.5.1.2
8.5.1.3
8.5.1.4
8.5.1.5
8.5.1.6
8.5.1.7.1
8.5.1.7.2
8.5.1.7.3
8.5.2.1
8.5.4.1
8.5.4.2
8.5.4.3
8.5.4.4
8.6.1.1
8.6.1.2
8.6.2.1
8.6.2.2
8.6.2.3
8.6.2.3a
8.6.2.4
8.6.2.5
242
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
FDD
cell
Measurement configuration control and reporting / SON / ANR / CGI reporting of HRPD cell
X
Intra-frequencySI acquisition / CSG cell and non-CSG cell
X
Inter-freq SI acquisition / Non-member hybrid cell
X
Inter-freq SI acquisition / Member hybrid cell
X
Inter-RAT SI acquisition / RRC_CONNECTED / UMTS member CSG cell
X
Inter-frequency E-UTRAN FDD – FDD / CSG Proximity Indication
X
Inter-RAT handover / From E-UTRA to UTRA PS / Data
X
Inter-RAT handover / From E-UTRA to UTRA HSPA / Data
X
Inter-RAT handover / from E-UTRA to UTRA HSUPA/HSDPA / Data
X
Inter-RAT handover / From UTRA PS to E-UTRA / Data
X
Inter-RAT handover / From UTRA HSPA to E-UTRA / Data
X
CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell
X
addition / Intra-band Contiguous CA
CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell
X
addition / Inter-band CA
CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell
X
addition / Intra-band non-contiguous CA
Inter-RAT cell change order / From E-UTRA data RRC_CONNECTED to GPRS / Without
X
NACC
Inter-RAT cell change order / From E-UTRA data to GPRS / With NACC
X
Pre-registration at 1xRTT and inter-RAT handover / CS fallback from E-UTRA RRC_IDLE
X
to 1xRTT
Pre-Registration at 1xRTT and inter-RAT handover / CS fallback caused by addition of CS
X
service / From E-UTRA Data to 1xRTT
Pre-registration at 1xRTT and inter-RAT handover / Enhanced CS fallback from E-UTRA
X
RRC_IDLE to 1xRTT / MT call
Pre-registration at 1xRTT and inter-RAT handover / Enhanced CS fallback from E-UTRA
X
RRC_CONNECTED to 1xRTT / MO call
Pre-registration at 1xRTT and inter-RAT handover / Enhanced CS fallback from E-UTRA
X
RRC_CONNECTED to e1XCSFB ECAM-based 1xRTT / MO call
Pre-registration at 1xRTT and inter-RAT Handover / Enhanced CS fallback from E-UTRA
X
RRC_CONNECTED to 1xRTT / ECAM-based MT call
Pre-registration at 1xRTT and inter-RAT Handover / Enhanced CS fallback from E-UTRA
X
RRC_CONNECTED to 1xRTT / Extended Service Reject / MO call
Pre-registration at 1xRTT and inter-RAT Handover / Enhanced CS fallback from E-UTRA
X
call failure – GCSNA with Reorder Order
Radio link failure/RRC connection re-establishment Success
X
Radio link failure/T301 expiry
X
Radio link failure/T311 expiry
X
Radio link failure / RRC connection re-establishment reject
X
Radio link failure/Radio link recovery while T310 is running
X
Radio link failure / T311 expiry / Dedicated RLF timer
X
CA / No Radio link failure on Scell/ RRC Connection Continues on PCell / Intra-band
X
Contiguous CA
CA / No Radio link failure on Scell/ RRC Connection Continues on PCell / Inter-band CA
X
CA / No Radio link failure on Scell/ RRC Connection Continues on PCell / Intra-band nonX
contiguous CA
Redirection to E-UTRAN / From UTRAN upon reception of RRC CONNECTION REJECT
X
UE capability transfer/Success
X
Network-requested CA Band Combination Capability Signalling / Number of UE supported
X
CA band combinations less than or equal to 128
Network-requested CA Band Combination Capability Signalling / Number of UE supported
X
CA band combinations exceeds 128
UE Capability Transfer/ Success/ UE Cat 0/ UE Paging Info
X
Immediate MDT / Reporting / Location information
X
Immediate MDT / Reporting / Location information / Request from eNB / Event A2
X
Logged MDT / Intra-frequency measurement, logging and reporting
X
Logged MDT / Inter-frequency measurement, logging and reporting
X
Logged MDT / Logging and reporting / Limiting area scope
X
Logged MDT / Logging and reporting / Limiting area scope / TAC list with PLMN identity
X
Logged MDT / Logging and reporting / Indication of logged measurements at E-UTRA
X
handover
Logged MDT / Logging and reporting / Indication of logged measurements at E-UTRA reX
ETSI
TDD
T/F
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
-
X
-
X
-
X
-
X
-
X
-
X
X
X
X
X
X
X
-
X
X
-
X
X
X
X
-
X
-
X
X
X
X
X
X
X
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
8.6.2.6
8.6.2.7
8.6.2.8
8.6.2.9
8.6.2.10
8.6.2.11
8.6.2.12
8.6.3.1
8.6.3.4
8.6.4.1
8.6.4.2
8.6.4.3
8.6.4.4
8.6.4.5
8.6.4.7
8.6.4.8
8.6.4.9
8.6.4.10
8.6.5.1
8.6.5.1a
8.6.5.4
8.6.6.1
8.6.6.2
8.6.6.4
8.6.6.5
8.6.6.6
8.6.6.7
8.6.7.1
8.6.7.2
8.6.7.3
8.6.7.4
8.6.8.1
8.6.8.2
8.6.8.3
8.6.8.4
8.6.8.5
8.6.8.6
8.6.9.1
8.6.9.2
243
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
FDD
establishment
Logged MDT / Release of logged MDT measurement configuration / Expire of duration
X
timer
Logged MDT / Release of logged MDT measurement configuration / Reception of new
X
logged measurement configuration, Detach or UE power off
Logged MDT / Maintaining logged measurement configuration / UE state transitions and
X
mobility
Logged MDT / Location information
X
Logged MDT / Logging and reporting / Reporting at RRC connection establishment / PLMN
X
list
Logged MDT / Logging and reporting / Reporting at intra LTE handover / PLMN list
X
Logged MDT / Logging and reporting / Reporting at RRC connection re-establishment /
X
PLMN list
Logged MDT / UTRAN Inter-RAT measurement, logging and reporting
X
Logged MDT / Logging and reporting / Reporting at UTRAN Inter-RAT handover / PLMN list
X
Radio Link Failure logging / Reporting of Intra-frequency measurements
X
Radio Link Failure logging / Reporting of Inter-frequency measurements
X
Radio Link Failure logging / Reporting at RRC connection establishment and
X
reestablishment
Radio Link Failure logging / Reporting at E-UTRA handover
X
Radio Link Failure logging / Reporting of ECGI of the PCell
X
Radio Link Failure logging / Location information
X
Radio Link Failure logging / Logging and reporting / Reporting at RRC connection
X
establishment / PLMN list
Radio Link Failure logging / Logging and reporting / Reporting at intra LTE handover /
X
PLMN list
Radio Link Failure logging / Logging and reporting / Reporting at RRC connection reX
establishment / PLMN list
Radio Link Failure logging / Reporting at UTRAN Inter-RAT handover
X
Radio Link Failure logging / Reporting at UTRAN Inter-RAT handover / PLMN list
X
Radio Link Failure logging / Reporting of selected UTRA cell
X
Handover Failure logging / Reporting of Intra-frequency measurements
X
Handover Failure logging / Reporting of Inter-frequency measurements
X
Handover Failure logging / Location information
X
Handover Failure logging / Logging and reporting / Reporting at RRC connection
X
establishment / PLMN list
Handover Failure logging / Logging and reporting / Reporting at intra LTE handover / PLMN
X
list
Handover Failure logging / Logging and reporting / Reporting at RRC connection reX
establishment / PLMN list
Handover Failure logging / Reporting of UTRAN Inter-RAT measurements
X
Handover Failure logging / Reporting of GERAN Inter-RAT measurements
X
Handover Failure logging / Reporting of CDMA2000 Inter-RAT measurements
X
Handover Failure logging / Reporting at UTRAN Inter-RAT handover / PLMN list
X
Connection Establishment Failure logging / Logging and reporting / T300 expiry
X
Connection Establishment Failure logging / Logging and reporting / Reporting at intra-LTE
X
handover
Connection Establishment Failure logging / Logging and reporting / Reporting at RRC
X
connection re-establishment
Connection Establishment Failure logging / Logging and reporting / Location Information
X
Connection Establishment Failure logging / Logging and reporting / Reporting of IntraX
frequency measurements
Connection Establishment Failure logging / Logging and reporting / Reporting of InterX
frequency measurements
Connection Establishment Failure logging / Logging and reporting / Reporting at UTRAN
X
Inter-RAT handover
Connection Establishment Failure logging / Logging and reporting / Reporting of UTRAN Inter-RAT
X
TDD
T/F
X
-
X
-
X
-
X
X
-
X
X
-
X
X
X
X
X
-
X
X
X
X
-
X
-
X
-
X
X
X
X
X
X
X
X
X
-
X
-
X
-
X
X
X
-
X
X
X
-
X
-
X
X
-
X
-
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
-
X
X
-
measurements
8.6.9.3
8.6.10.1
8.6.11.1
8.7.1
9.1.2.1
9.1.2.3
Connection Establishment Failure logging / Logging and reporting / Reporting of GERAN
Inter-RAT measurements
Inter-RAT Immediate MDT / Reporting / Location information / Event B2
RACH Optimisation
Inter-RAT / ANR measurement, logging and reporting / E-UTRAN cell
Authentication accepted
Authentication not accepted by the network, GUTI used, authentication reject and re-
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
9.1.2.4
9.1.2.5
9.1.2.6
9.1.2.7
9.1.3.1
9.1.3.2
9.1.3.3
9.1.4.2
9.1.5.1
9.2.1.1.1
9.2.1.1.1a
9.2.1.1.1b
9.2.1.1.2
9.2.1.1.2a
9.2.1.1.7
9.2.1.1.7a
9.2.1.1.7b
9.2.1.1.7c
9.2.1.1.9
9.2.1.1.10
9.2.1.1.11
9.2.1.1.12
9.2.1.1.13
9.2.1.1.13a
9.2.1.1.14
9.2.1.1.15
9.2.1.1.15a
9.2.1.1.16
9.2.1.1.16a
9.2.1.1.17
9.2.1.1.18
9.2.1.1.19
9.2.1.1.20
9.2.1.1.21
9.2.1.1.22
9.2.1.1.23
9.2.1.1.24
9.2.1.1.25
9.2.1.1.26
9.2.1.1.27
9.2.1.1.27a
9.2.1.1.28
9.2.1.1.28a
9.2.1.1.29
9.2.1.1.30
9.2.1.2.1
9.2.1.2.1b
9.2.1.2.1c
9.2.1.2.1d
9.2.1.2.2
9.2.1.2.3
9.2.1.2.4
9.2.1.2.4a
9.2.1.2.5
9.2.1.2.6
9.2.1.2.7
244
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
FDD
authentication
Authentication not accepted by the UE/MAC code failure
X
Authentication not accepted by the UE/SQN failure
X
Abnormal cases/Network failing the authentication check
X
Authentication not accepted by the UE/ non-EPS authentication unacceptable
X
NAS security mode command accepted by the UE
X
NAS security mode command not accepted by the UE
X
No emergency bearer service / NAS security mode command with EIA0 not accepted by
X
the UE
Identification procedure/IMEI requested
X
EMM information procedure
X
Attach Procedure/Success/Valid GUTI
X
Attach/Success/Last visited TAI, TAI list and equivalent PLMN list handling
X
Attach Procedure / Success / Last visited TAI, TAI list and equivalent PLMN list handling /
X
Single Frequency operation
Attach Procedure/Success/With IMSI/GUTI reallocation
X
AttachWithIMSI configured / Selected PLMN is neither the registered PLMN nor in the list of
X
equivalent PLMNs / Success
Attach/Success/List of equivalent PLMNs in the ATTACH ACCEPT message
X
Attach Procedure / Success / List of equivalent PLMNs in the ATTACH ACCEPT message /
X
Single Frequency operation
Attach / Success / native GUMMEI
X
Attach / Success / PSM
X
Attach/Rejected/IMSI invalid
X
Attach/Rejected/Illegal ME
X
Attach / Rejected / EPS services and non-EPS services not allowed
X
Attach / Rejected / EPS services not allowed
X
Attach/Rejected/PLMN not allowed
X
Attach / Rejected / PLMN not allowed / Single Frequency operation
X
Attach/Rejected/Tracking area not allowed
X
Attach/Rejected/Roaming not allowed in this tracking area
X
Attach / Rejected / Roaming not allowed in this tracking area / Single Frequency operation
X
Attach/Rejected/EPS services not allowed in this PLMN
X
Attach / Rejected / EPS services not allowed in this PLMN / Single Frequency operation
X
Attach/Rejected/No suitable cells in tracking area
X
Attach / Rejected / Not authorized for this CSG
X
Attach/Abnormal case/Failure due to non integrity protection
X
Attach/Abnormal case/Access barred because of access class barring or NAS signalling
X
connection establishment rejected by the network
Attach/Abnormal case/Success after several attempts due to no network response
X
Attach/Abnormal case/Unsuccessful attach after 5 attempts
X
Attach/Abnormal case/Repeated rejects for network failures
X
Attach/Abnormal case/Change of cell into a new tracking area
X
Attach/Abnormal case/Mobile originated detach required
X
Attach/Abnormal case/Detach procedure collision
X
Attach / Abnormal case / Network reject with Extended Wait Timer
X
Attach Procedure / EAB broadcast handling / ExtendedAccessBarring configured in the UE
X
Attach / Success / IMS
X
Attach / Success / IMS / Second PDN
X
Attach / Rejected / IMEI not accepted
X
Attach / Abnormal case / ESM failure
X
Combined attach/Success/EPS and non-EPS services
X
Combined attach / Success / SMS only
X
Combined attach procedure / Success / CS Fallback not preferred
X
Combined attach procedure / Success / EPS and CS Fallback not preferred / data centric
X
UE
Combined attach / Success / EPS services only / IMSI unknown in HSS
X
Combined attach / Success / EPS services only / MSC temporarily not reachable
X
Combined attach/Success/EPS services only/CS domain not available
X
Successful combined attach procedure / EPS service only / congestion
X
Combined attach / Rejected / IMSI invalid
X
Combined attach / Rejected / Illegal ME
X
Combined attach / Rejected / EPS services and non-EPS services not allowed
X
ETSI
TDD
T/F
X
X
X
X
X
X
X
-
X
X
X
X
X
-
X
X
-
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
--
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
3GPP TS 36.523-3 version 13.2.0 Release 13
245
Test case
9.2.1.2.8
9.2.1.2.9
9.2.1.2.10
9.2.1.2.11
9.2.1.2.12
9.2.1.2.13
9.2.1.2.14
9.2.1.2.15
9.2.2.1.1
9.2.2.1.2
9.2.2.1.3
9.2.2.1.4
9.2.2.1.6
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
Combined attach / Rejected / EPS services not allowed
Combined attach / Rejected / PLMN not allowed
Combined attach / Rejected / Tracking area not allowed
Combined attach / Rejected / Roaming not allowed in this tracking area
Combined attach / Rejected / EPS services not allowed in this PLMN
Combined attach / Rejected / No suitable cells in tracking area
Combined attach / Rejected / Not authorized for this CSG
Combined attach / Abnormal case / Handling of the EPS attach attempt counter
UE initiated detach/UE switched off
UE initiated detach/USIM removed from the UE
UE initiated detach/EPS capability of the UE is disabled
UE initiated detach / detach for non-EPS services
UE initiated detach/Abnormal case/Local detach after 5 attempts due to no network
response
9.2.2.1.7
UE initiated detach/Abnormal case/Detach procedure collision
9.2.2.1.8
UE initiated detach/Abnormal case/Detach and EMM common procedure collision
9.2.2.1.9
UE initiated detach/Abnormal case/Change of cell into a new tracking area
9.2.2.1.10 UE initiated detach / Mapped security context
9.2.2.2.1
NW initiated detach/Re-attach required
9.2.2.2.2
NW initiated detach/IMSI detach
9.2.2.2.14 NW initiated detach/Abnormal case/EMM cause not included
9.2.3.1.1
Normal tracking area update/Accepted
9.2.3.1.1a Normal tracking area update / Accepted / PSM
9.2.3.1.4
Normal tracking area update/List of equivalent PLMNs in the TRACKING AREA UPDATE
ACCEPT message
9.2.3.1.5
Periodic tracking area update/Accepted
9.2.3.1.5a Periodic tracking area update / Accepted / Per-device timer
9.2.3.1.5b Periodic tracking area update / Accepted / PSM / T3312 Extended Value
9.2.3.1.6
Normal tracking area update / UE with ISR active moves to E-UTRAN
9.2.3.1.8
UE receives an indication that the RRC connection was released with cause “load
balancing TAU required”
9.2.3.1.8a Normal tracking area update / low priority override
9.2.3.1.8b Normal tracking area update / EAB active
9.2.3.1.9
Normal tracking area update / Correct handling of CSG list
9.2.3.1.9a Normal tracking area update/NAS signalling connection recovery
9.2.3.1.10 Normal tracking area update / Rejected / IMSI invalid
9.2.3.1.11 Normal tracking area update / Rejected / Illegal ME
9.2.3.1.12 Normal tracking area update / Rejected / EPS service not allowed
9.2.3.1.13 Normal tracking area update/Rejected/UE identity cannot be derived by the network
9.2.3.1.14 Normal tracking area update/Rejected/UE implicitly detached
9.2.3.1.15 Normal tracking area update / Rejected / PLMN not allowed
9.2.3.1.15a Normal tracking area update / Rejected / PLMN not allowed / Single Frequency operation
9.2.3.1.16 Normal tracking area update/Rejected/Tracking area not allowed
9.2.3.1.17 Normal tracking area update / Rejected / Roaming not allowed in this tracking area
9.2.3.1.18 Normal tracking area update / Rejected / EPS services not allowed in this PLMN
9.2.3.1.18a Normal tracking area update / Rejected / EPS services not allowed in this PLMN / Single
Frequency operation
9.2.3.1.19 Normal tracking area update/Rejected/No suitable cells in tracking area
9.2.3.1.20 Normal tracking area update / Rejected / Not authorized for this CSG
9.2.3.1.20a Normal tracking area update / Rejected / Congestion
9.2.3.1.22 Normal tracking area update / Abnormal case / access barred due to access class control
or NAS signalling connection establishment rejected by the network
9.2.3.1.23 Normal tracking area update/Abnormal case/Success after several attempts due to no
network response/TA belongs to TAI list and status is UPDATED
9.2.3.1.25 Normal tracking area update/Abnormal case/Failure after 5 attempts due to no network
response
9.2.3.1.26 Normal tracking area update/Abnormal case/TRACKING AREA UPDATE REJECT
9.2.3.1.27 Normal tracking area update/Abnormal case/Change of cell into a new tracking area
9.2.3.1.28 Normal tracking area update/Abnormal case/Tracking area updating and detach procedure
collision
9.2.3.2.1
Combined tracking area update/Successful
9.2.3.2.1a Combined tracking area update / Successful / Check of last visited TAI and handling of TAI
list, LAI and TMSI
ETSI
FDD
X
X
X
X
X
X
X
X
X
X
X
X
X
TDD
X
X
X
X
X
X
X
X
X
X
X
X
X
T/F
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
-
X
X
-
X
X
X
X
X
X
-
X
X
X
X
X
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
9.2.3.2.1b
9.2.3.2.1c
9.2.3.2.2
9.2.3.2.3
9.2.3.2.4
9.2.3.2.4a
9.2.3.2.5
9.2.3.2.6
9.2.3.2.7
9.2.3.2.8
9.2.3.2.9
9.2.3.2.10
9.2.3.2.11
9.2.3.2.12
9.2.3.2.13
9.2.3.2.14
9.2.3.2.15
9.2.3.2.16
9.2.3.2.17
9.2.3.3.1
9.2.3.3.2
9.2.3.3.3
9.2.3.3.4
9.2.3.3.5
9.2.3.3.5a
9.2.3.4.1
9.3.1.1
9.3.1.3
9.3.1.4
9.3.1.5
9.3.1.6
9.3.1.7
9.3.1.7a
9.3.1.12a
9.3.1.16
9.3.1.17
9.3.1.18
9.3.2.1
9.3.2.2
9.3.2.2a
9.4.1
9.4.2
9.4.3
9.4.4
9.4.5
9.4.6
10.2.1
10.3.1
10.4.1
10.4.2
10.5.1
10.5.1a
10.5.1b
10.5.3
10.5.4
10.6.1
10.7.1
246
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
FDD
Combined tracking area update / Success / SMS only
X
Combined tracking area update / Success / CS Fallback not preferred
X
Combined tracking area update / Successful for EPS services only / IMSI unknown in HSS
X
Combined tracking area update / Successful for EPS services only / MSC temporarily not
X
reachable
Combined tracking area update / Successful for EPS services only / CS domain not
X
available
Combined tracking area update / Successful for EPS services only / congestion
X
Combined tracking area update / Rejected / IMSI invalid
X
Combined tracking area update / Rejected / Illegal ME
X
Combined tracking area update / Rejected / EPS services and non-EPS services not
X
allowed
Combined tracking area update / Rejected / EPS services not allowed
X
Combined tracking area update / Rejected / UE identity cannot be derived by the network
X
Combined tracking area update / Rejected / UE implicitly detached
X
Combined tracking area update / Rejected / PLMN not allowed
X
Combined tracking area update / Rejected / Tracking area not allowed
X
Combined tracking area update / Rejected / Roaming not allowed in this tracking area
X
Combined tracking area update / Rejected / EPS services not allowed in this PLMN
X
Combined tracking area update / Rejected / No suitable cells in tracking area
X
Combined tracking area update / Rejected / Not authorized for this CSG
X
Combined tracking area update / Abnormal case / handling of the EPS tracking area
X
updating attempt counter
First Iu mode to S1 mode inter-system change after attach
X
Iu mode to S1 mode intersystem change / ISR is active / Expiry of T3312 in E-UTRAN or
X
T3412 in UTRAN and further intersystem change
Iu mode to S1 mode intersystem change / Periodic TAU and RAU / ISR activated, T34xx
X
expired
First S1 mode to Iu mode inter-system change after attach
X
Periodic routing area update
X
Periodic location update
X
TAU/RAU procedure for inter-system cell reselection between A/Gb and S1 modes
X
Service request initiated by UE for user data
X
Service request / Mobile originating CS fallback
X
Service request / Rejected / IMSI invalid
X
Service request / Rejected / Illegal ME
X
Service request / Rejected / EPS services not allowed
X
Service request/Rejected/UE identity cannot be derived by the network
X
Service request/Rejected/UE implicitly detached
X
Extended service request / Rejected / CS domain temporarily not available
X
Service request/Abnormal case/Switch off
X
Service request/Abnormal case/Procedure collision
X
Service request / Rejected / Not authorized for this CSG
X
Paging procedure
X
Paging for CS fallback/Idle mode
X
Paging for CS fallback/Connected mode
X
Integrity protection/Correct functionality of EPS NAS integrity algorithm/SNOW3G
X
Integrity protection/Correct functionality of EPS NAS integrity algorithm/AES
X
Ciphering and deciphering/Correct functionality of EPS NAS encryption algorithm/SNOW3G
X
Ciphering and deciphering/Correct functionality of EPS NAS encryption algorithm/AES
X
Integrity protection / Correct functionality of EPS NAS integrity algorithm / ZUC
X
Ciphering and deciphering / Correct functionality of EPS NAS encryption algorithm / ZUC
X
Dedicated EPS bearer context activation/Success
X
EPS bearer context modification/Success
X
EPS bearer context deactivation/Success
X
EPS bearer context deactivation / Re-establishment
X
UE requested PDN connectivity procedure accepted by the network
X
UE requested PDN connectivity accepted / Dual priority / T3396 override
X
UE requested PDN connectivity accepted / Dual priority / T3346 override
X
UE requested PDN connectivity procedure not accepted
X
UE requested PDN connectivity not accepted / Network reject with Extended Wait Timer
X
UE requested PDN disconnect procedure accepted by the network
X
UE requested bearer resource allocation, accepted by the network/New EPS bearer context X
ETSI
TDD
X
X
X
X
T/F
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
247
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
FDD
10.7.2
UE requested bearer resource allocation accepted by the network/Existing EPS bearer
X
context
10.7.3
UE requested bearer resource allocation not accepted by the network
X
10.7.4
UE requested bearer resource allocation/Expiry of timer T3480
X
10.7.5
UE requested bearer resource allocation / BEARER RESOURCE ALLOCATION REJECT
X
message including cause #43 “unknown EPS bearer context”
10.8.1
UE requested bearer resource modification accepted by the network/New EPS bearer
X
context
10.8.2
UE requested bearer resource modification accepted by the network/Existing EPS bearer
X
context
10.8.3
UE requested bearer resource modification not accepted by the network
X
10.8.4
UE requested bearer resource modification / Cause #36 “regular deactivation”
X
10.8.5
UE requested bearer resource modification / BEARER RESOURCE MODIFICATION
X
REJECT message including cause #43 “unknown EPS bearer context”
10.8.6
UE requested bearer resource modification / Collision of a UE requested bearer resource
X
modification procedure and EPS bearer context deactivation procedure
10.8.7
UE requested bearer resource modification / Expiry of timer T3481
X
10.9.1
UE routing of uplinks packets
X
11.1.1
MT-SMS over SGs/Idle mode
X
11.1.2
MT-SMS over SGs/Active mode
X
11.1.3
MO-SMS over SGs/Idle mode
X
11.1.4
MO-SMS over SGs/Active mode
X
11.1.5
Multiple MO-SMS over SGs / Idle mode
X
11.1.6
Multiple MO-SMS over SGs / Active mode
X
11.2.1
Emergency bearer services / Normal cell / NORMAL-SERVICE / Local Emergency
X
Numbers List sent in the Attach / PDN connect new emergency EPS bearer context /
Service request / Emergency PDN disconnect
11.2.2
Emergency bearer services / Normal cell / LIMITED-SERVICE / Attach / PDN connect /
X
Service request / PDN disconnect / Detach / Temporary storage of EMM information
11.2.3
Emergency bearer services / CSG cell / LIMITED-SERVICE / Attach / Security mode control X
procedure without prior authentication / PDN connect / Service request / PDN disconnect /
Detach upon UE switched off / Temporary storage of EMM information
11.2.4
Emergency bearer services / Normal cell / NO-IMSI / Attach / No EPS security context /
X
PDN connect / Service request / Timer T3412 expires
11.2.5
Emergency bearer services / Normal cell / NORMAL-SERVICE / Local Emergency
X
Numbers List NOT sent in the Attach / PDN connect new emergency EPS bearer context /
Authentication SQN code failure – MME aborts authentication continues using current
security context / Service request / Emergency PDN disconnect
Handling of Local Emergency Numbers List provided during Attach and Normal tracking area update
11.2.6
X
TDD
X
T/F
-
X
X
X
-
X
-
X
-
X
X
X
-
X
-
X
X
X
X
X
X
X
X
X
-
X
-
X
-
X
-
X
-
X
-
X
X
-
Attach for emergency bearer services / Rejected / No suitable cells in tracking area /
Emergency call using the CS domain / UTRA or GERAN
LIMITED-SERVICE / EPS does not support IMS Emergency / Emergency call using the CS
domain
LIMITED-SERVICE / Inter-system mobility / E-UTRA to UTRA CS / SRVCC Emergency
Call Handover to UTRAN
X
X
X
X
X
X
X
X
X
11.2.12
LIMITED-SERVICE / Inter-system mobility / E-UTRA to GSM CS / SRVCC Emergency Call Handover
to GERAN
X
X
-
12.2.1
12.2.2
12.2.3
12.2.4
12.3.1
12.3.2
12.3.3
12.3.4
13.1.1
13.1.2
13.1.2a
Data transfer of E-UTRA radio bearer combinations 1, 3, 6 and 9
Data transfer of E-UTRA radio bearer combinations 2, 4, 7 and 10
Data transfer of E-UTRA radio bearer combinations 5, 6, 8, 11 and 12
Data transfer of E-UTRA radio bearer combination 13
Data transfer of E-UTRA radio bearer combinations 1, 3, 6 and 9 / MIMO
Data transfer of E-UTRA radio bearer combinations 2, 4, 7 and 10 / MIMO
Data transfer of E-UTRA radio bearer combinations 5, 6, 8, 11 and 12 / MIMO
Data transfer of E-UTRA radio bearer combination 13 / MIMO
Activation and deactivation of additional data radio bearer in E-UTRA
Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection / MO call
Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection including
System Information / MO call
Call setup from E-UTRAN RRC_CONNECTED / CS fallback to UTRAN with redirection /
MT call
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
11.2.7
11.2.8
11.2.10
11.2.11
13.1.3
procedures
UE has PDN connection only for emergency bearer services / Normal tracking area update / Accepted /
Local Emergency Numbers List is not sent by the network / Handling of the lists of forbidden tracking
areas
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
248
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
FDD
13.1.4
Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with handover / MT call
X
13.1.5
Call setup from E-UTRAN RRC_CONNECTED / CS fallback to UTRAN with handover / MO
X
call
13.1.7
Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with redirection / MT call
X
13.1.8
Call setup from E-UTRA RRC_CONNECTED / CS fallback to GSM with redirection / MO
X
call
13.1.9
Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with CCO without NACC / MO
X
call
13.1.10
Call setup from E-UTRA RRC_CONNECTED / CS fallback to GSM with CCO without
X
NACC / MT call
13.1.15
Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection / MT call /
X
UTRAN cell is barred
13.1.16
Emergency call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with handover
X
13.1.17
Call setup from E-UTRAN RRC_IDLE / mobile originating 1xCS fallback emergency call to
X
1xRTT
13.1.18
Call setup from E-UTRAN RRC_IDLE / mobile originating enhanced 1xCS fallback
X
emergency call to 1xRTT
13.1.19
Emergency call setup from E-UTRAN RRC_IDLE / IMS VoPS supported / EMC BS not
X
supported / CS fallback to UTRAN or GERAN with redirection
13.1.20
Emergency call setup from E-UTRAN RRC_IDLE / IMS VoPS not supported / EMC BS
X
supported / CS fallback to UTRAN or GERAN with redirection
13.2.1
RRC connection reconfiguration/E-UTRA to E-UTRA
X
13.3.1.1
Intra-system connection re-establishment/Radio link recovery while T310 is running
X
13.3.1.2
Intra-system connection re-establishment/Re-establishment of a new connection when
X
further data is to be transferred
13.3.1.3
RRC connection reconfiguration / Full configuration / DRB establishment
X
13.3.2.1
Inter-system connection re-establishment / E-UTRAN to UTRAN / Further data are to be
X
transferred
13.3.2.2
Inter-system connection re-establishment / E-UTRAN to GPRS / Further data are to be
X
transferred
13.4.1.2
Inter-frequency mobility/E-UTRA to E-UTRA packet
X
13.4.1.3
Intra-system mobility / E-UTRA FDD to E-UTRA TDD to E-UTRA FDD packet
X
13.4.1.4
Inter-band mobility / E-UTRA to E-UTRA packet
X
13.4.1.5
RRC connection reconfiguration / Handover / Full configuration / DRB establishment
X
13.4.2.1
Inter-system mobility / E-UTRA to UTRA packet
X
13.4.2.4
Inter-system mobility / Service based redirection from UTRA to E-UTRA
X
13.4.2.5
Inter-system mobility / Service based redirection from GSM/GPRS to E-UTRA
X
13.4.3.1
Inter-system mobility / E-UTRA voice to UTRA CS voice / SRVCC
X
ETSI
TDD
X
X
T/F
X
X
X
X
-
X
-
X
-
X
X
X
X
X
-
X
-
X
X
X
X
X
X
X
-
X
X
X
X
-
X
X
X
X
X
X
X
X
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
249
ETSI TS 136 523-3 V13.2.0 (2017-03)
Test case
Description
FDD
13.4.3.2
Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / SRVCC
X
13.4.3.3
Inter-system mobility / E-UTRA voice to GSM CS voice / SRVCC
X
13.4.3.4
Inter-system mobility / E-UTRA voice to UTRA CS voice / Unsuccessful case / Retry on old
X
cell / SRVCC
13.4.3.5
Inter-system mobility / E-UTRA voice to GSM CS voice / Unsuccessful case / Retry on old
X
cell / SRVCC
13.4.3.6
Inter-system mobility / E-UTRA PS voice + PS Data / HO cancelled / Notification procedure
X
/ SRVCC
13.4.3.7
Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call
X
13.4.3.8
Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call / Forked
X
responses
13.4.3.9
Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MO call / SRVCC HO
X
failure
13.4.3.10 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MT call
X
13.4.3.11 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MT call / SRVCC HO
X
failure
13.4.3.13 Inter-system mobility / E-UTRA voice to UTRA CS voice / aSRVCC / MT call / User answers X
in PS domain / SRVCC HO cancelled
13.4.3.14 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / aSRVCC X
/ MO call
13.4.3.15 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / aSRVCC X
/ MO call / SRVCC HO cancelled
13.4.3.16 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / aSRVCC X
/ MT call
13.4.3.18 Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data / bSRVCC X
/ MO call
13.4.3.19
Inter-system mobility / E-UTRA PS voice + PS data to UTRA CS voice + PS data /
X
bSRVCC / MO call / SRVCC HO cancelled
13.4.3.20 Inter-system mobility / E-UTRA voice to UTRA CS voice / bSRVCC / MO call / SRVCC HO
X
failure
13.4.3.21 Inter-system mobility / E-UTRA PS voice to GSM CS voice / bSRVCC / MO call
X
13.4.3.22 Inter-system mobility / E-UTRA PS voice to GSM CS voice / bSRVCC / MO call / SRVCC
X
HO cancelled
13.4.3.23 Inter-system mobility / E-UTRA voice to GSM CS voice / bSRVCC / MO call / SRVCC HO
X
failure
13.4.3.24 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MO call
X
13.4.3.25 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MO call / Forked
X
responses
13.4.3.26 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MO call / SRVCC HO
X
failure
13.4.3.27 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MT call
X
13.4.3.28 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MT call / SRVCC HO
X
failure
13.4.3.30 Inter-system mobility / E-UTRA voice to GSM CS voice / aSRVCC / MT call / User answers
X
in PS domain/ SRVCC HO cancelled
13.4.3.32 Inter-system mobility / UTRA CS voice to E-UTRA voice / rSRVCC
X
13.4.3.34 Inter-system mobility / UTRA CS voice to E-UTRA voice / alerting / rSRVCC / MO call
X
13.4.3.41 Inter-system mobility / E-UTRA PS voice to GSM CS voice / HO cancelled / Notification procedure /
X
TDD
T/F
X
-
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
-
X
X
-
X
-
X
X
-
X
-
X
-
SRVCC
13.4.4.1
13.4.4.2
13.4.4.5
13.5.1
13.5.1a
13.5.2
13.5.2a
13.5.3
13.5.3a
13.5.4
13.5.5
13.5.6
14.1
Pre-registration at 1xRTT and Cell reselection / 1x Zone Registration
Pre-registration at 1xRTT and Cell reselection / 1x Ordered Registration
Pre-Registration at 1xRTT / Power Down Registration
MTSI MO speech call / SSAC / 0% access probability for MTSI MO speech call
MTSI MO speech call / SSAC in Connected mode / 0% access probability for MTSI MO
speech call
MTSI MO video call / SSAC / 0% access probability for MTSI MO video call
MTSI MO video call / SSAC in connected mode / 0% access probability for MTSI MO video
call
Emergency call / Success / SSAC / 0% access probability for MTSI MO speech call
Emergency call / Success / SSAC in connected mode / 0% access probability for MTSI MO
speech call
MTSI MO speech call / SCM / 0% access probability skip for MTSI MO speech call
MTSI MO video call / SCM / 0% access probability skip for MTSI MO video call
MTSI MO SMS / SCM / 0% access probability skip for MTSI MO SMS over IP
ETWS reception in RRC_IDLE state / Duplicate detection
ETSI
X
X
X
X
X
X
-
X
X
X
-
X
X
X
X
-
X
X
X
X
-
X
X
X
X
X
X
X
-
3GPP TS 36.523-3 version 13.2.0 Release 13
Test case
14.2
17.1.1
17.1.2
17.1.3
17.1.4
17.1.5
17.2.1
17.2.2
17.2.3
17.2.4
17.3.1
17.3.2
17.4.1
17.4.1a
17.4.2
17.4.2a
17.4.3
17.4.3a
17.4.4
17.4.5
17.4.6
17.4.7
17.4.8
17.4.9.1
17.4.9.2
17.4.10.1
17.4.10.2
17.4.11.1
17.4.11.2
18.1.1
18.1.2
18.1.3
22.4.2
22.4.6
22.4.11
22.4.13
22.5.10
22.5.11
22.5.12
250
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description
ETWS reception in RRC_CONNECTED state / Duplicate detection
MCCH information acquisition/ UE is switched on
MCCH information acquisition/UE cell reselection to a cell in a new MBSFN area
MCCH information acquisition/UE handover to a cell in a new MBSFN area
MCCH information acquisition/ UE is receiving an MBMS service
MCCH information acquisition/UE is not receiving MBMS data
UE acquire the MBMS data based on the SIB13 and MCCH message / MCCH and MTCH
are on the same MCH
UE acquire the MBMS data based on the SIB13 and MCCH message / MCCH and MTCH
are on different MCHs
UE receives the MBMS data when this data is in the beginning of the MSAP
Reception of PDCCH DCI format 0 and PHICH in MBSFN subframes.
MBMS Counting / UE not receiving MBMS service
MBMS Counting / UE receiving MBMS service
Cell reselection to intra-frequency cell to start MBMS service
Cell reselection to intra-frequency cell to continue MBMS service reception / Single
Frequency operation (inter-band neighbouring cell)
Cell reselection to inter- frequency cell to start MBMS service
Cell reselection to inter- band cell to start MBMS service reception
Handover to inter-frequency cell to start MBMS service reception
Handover to inter-band cell to start MBMS service reception
MBMS service continuity / Handover to inter-frequency cell / MBMS Interest Indication on
cell not broadcasting SIB15
Conditional retransmission of MBMS Interest Indication after handover
MBMS service continuity / E-UTRAN release of unicast bearer
MBMS Interest Indication after Radio Link Failure
Continue MBMS service reception after E-UTRAN release of unicast bearer
FDD
X
X
X
X
X
X
X
TDD
X
X
X
X
X
X
T/F
-
X
X
-
X
X
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
X
-
X
X
X
X
X
X
X
X
X
-
CA / Start MBMS reception on Non-Serving Cell / Continue MBMS reception on SCell after SCell
addition / Intra-band Contiguous CA
CA / Start MBMS reception on Non-Serving Cell / Continue MBMS reception on SCell after SCell
addition / Inter-band CA
CA / Start MBMS reception on SCell / Continue MBMS reception on Non-Serving after SCell release /
Intra-band Contiguous CA
CA / Start MBMS reception on SCell / Continue MBMS reception on Non-Serving after SCell release /
Inter-band CA
CA / Start MBMS reception on PCell / Continue MBMS reception after swap of SCell and PCell / Intraband Contiguous CA
CA / Start MBMS reception on PCell / Continue MBMS reception after swap of SCell and PCell / Interband CA
PWS reception in RRC_IDLE state / Duplicate detection
PWS reception in RRC_CONNECTED state / Duplicate detection
PWS reception in RRC_CONNECTED State/Power On
NB-IoT / Paging for connection in idle mode / Multiple paging records
NB-IoT / Paging for notification of BCCH modification in idle mode / Direct indication for SI
update
NB-IoT / RRC connection release / Redirection to another NB-IoT frequency
NB-IoT / UE capability transfer / Success
NB-IoT / EPS NAS integrity and encryption / SNOW 3G
NB-IoT / EPS NAS integrity and encryption / AES
NB-IoT / EPS NAS integrity and encryption / ZUC
The Test Suite in TTCN3 is contained in multiple ASCII files which accompany the present document.
ETSI
X
-
X
X
-
X
X
-
X
X
-
X
X
-
X
X
X
X
X
-
-
X
X
X
X
X
-
-
3GPP TS 36.523-3 version 13.2.0 Release 13
251
ETSI TS 136 523-3 V13.2.0 (2017-03)
Annex B (informative):
Style Guides
B.1
Introduction
This annex is based on the style guide given in TS 34.123-3 [7], annex E but the language for UE conformance tests is
TTCN-3.
B.2
General Requirements for TTCN-3 Implementations
The TTCN-3 implementation for UE conformance tests shall be based on the following general design considerations:
-
Even though it is not reflected in TTCN-3 anymore in UE conformance tests ASPs and PDUs will still be
distinguished. This has impact on type definitions and naming conventions.
-
In general, templates for UE conformance tests shall be separated for sending and receiving.
-
Modified templates shall not be modified again.
-
All local variables shall be declared at the beginning of a function;
the order of declarations is:
-
local constants
-
local variables
-
local timers
-
The purpose of the test case implementation is conformance testing.
-
The common RAN5 approval process needs to be considered.
The TTCN-3 implementation for UE conformance tests shall fulfil the following requirements.
The implementation shall:
-
follow ES 201 873-1 [13] (TTCN-3 Core Language) and ES 201 873-4 [27] (TTCN-3 Operational Semantics);
-
be independent from interface specifications like TRI (ES 201 873-5 [28]) and TCI (ES 201 873-6 [29]) as well
as from proprietary approaches;
-
not use or rely on tool dependent features;
-
support maintainability and extendibility;
-
follow the naming conventions as defined below.
Further requirements:
-
Usage of external functions should be avoided.
-
Type definitions:
-
Existing ASN.1 type definitions contained in protocol specifications are imported from the respective
standards. All other type definitions shall be done within TTCN-3.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
B.3
252
ETSI TS 136 523-3 V13.2.0 (2017-03)
Naming Conventions
Even though these are being used for TTCN-3 the naming conventions provided in the present document are mainly
backward compatible to TTCN-2 as defined in TS 34.123-3 [7].
B.3.1
Prefixes and Restrictions for TTCN-3 Objects
Table B.3.1: Prefixes used for TTCN-3 objects
TTCN object
upper case
upper case
upper case
upper case
upper case
Prefix/
Postfix
(none)
(none)
p_
f_
fl_
upper case
upper case
fx_
a_
upper case
upper case
tsc_
const_
(none)
type definition
local variable
global (component) variable
port type
port name
local timer
ASP template
upper case
upper case
upper case
upper case
upper case
upper case
upper case
_Type
v_
vc_
PDU template
upper case
CM template
upper case
Template
(neither ASP nor PDU nor CM)
upper case
test suite parameter (PICS)
test suite parameter (PIXIT)
test case
upper case
upper case
TTCN module
TTCN group
function parameter
function running on a component
local function (tree) not to be used by
other modules
external function
altstep
test case selection expression
global constant
local constant
Enumerated
Initial Letter
t_
cas_
cads_
car_
cadr_
cs_
cds_
cr_
cdr_
cms_
cmr_
cs_
cds_
cr_
cdr_
crs_
pc_
px_
TC_
ETSI
Comment
local function not to be used by other modules
(including defaults)
name as specified in TS 36.523-2 [2] shall be used
(see note 1)
local constant being defined in a function
there are no restrictions regarding enumerated
types
(see note 7)
(see note 6)
(see note 2)
send ASP
modified (derived) send ASP
receive ASP
modified (derived) receive ASP
send PDU
modified (derived) send PDU
receive PDU
modified (derived) receive PDU
(see note 3)
send coordination message
receive coordination message
send template
modified (derived) send template
receive template
modified (derived) receive template
templates for IEs used in both directions
(see note 5)
(see note 8)
(see note 8)
(see note 4)
3GPP TS 36.523-3 version 13.2.0 Release 13
253
ETSI TS 136 523-3 V13.2.0 (2017-03)
NOTE 1: Global constants may be defined differently in imported modules (e.g. without any prefix and with lower case
initial letter).
NOTE 2: Global variables or timers are those defined within the TTCN-3 components. They are visible to all the
functions run in the component.
NOTE 3: Base template may have a second prefix:
- 508: PDU as defined in TS 36.508 [3];
- 108: PDU as defined in TS 34.108 [8].
NOTE 4: Test case names will correspond to the clause in the prose that specifies the test purpose. E.g. TC_8_1.
NOTE 5: Applicable only in case of "quasi-constant" definitions, e.g. to define a (constant) random pattern to be used
for sending and receiving when the UE is configured in loopback mode.
NOTE 6: Counter variables do not need to have a prefix.
NOTE 7: Exceptions for type definitions:
- ASP names are fully upper case letters and typically have postfix "_REQ", "_CNF" or "_IND".
- RRC protocol type definitions are extracted and imported from TS 36.331 [19]/TS 25.331 [36] and are
therefore out of scope.
- NAS protocol type definitions follow the names provided in the tabular notion of the standards and
therefore do not have a "_Type" postfix.
NOTE 8: For clarification an additional postfix _FDD/_TDD can be added.
B.3.2
Void
B.3.3
Void
B.3.4
Identifiers consisting of more than one Name
When identifiers are a concatenation of several words the words shall start with capital letters:
e.g.:. "px" + "Cell" + "A" + "Cell" + "Id" -> px_CellACellId.
Further details are described in TS 34.123-3 [7], clause E.2.1.
B.4
Implementation Issues
B.4.1
Control part
Even though the control part may not be used in a test campaign but be overruled by the test management system it is
used to provide the following information:
-
All test cases contained in the test suite.
-
For each test case:
-
Test case selection expression.
For maintenance reasons it shall be possible to generate the control part automatically by an appropriate tool.
B.4.2
Top Level Test Case Definitions
The top level test case definitions run on the MTC exclusively. The tasks of these test case definitions are generally the
same for each test case:
-
Start guard timer.
-
Create PTCs.
-
Connect PTCs.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
Start PTCs.
-
Wait for PTCs having finished.
254
ETSI TS 136 523-3 V13.2.0 (2017-03)
Additionally the MTC may host the upper tester but this is left open to implementation.
For maintenance reasons it shall be possible to generate the top level test case definitions defined for the MTC
automatically by an appropriate tool. To achieve this, the name of a function to be started on particular PTC need
derived from the test case name:
e.g. the function for PTC_A in test case TC_XX_YY_ZZ shall be f_TC_XX_YY_ZZ_A.
Cells are created in an off-state in the preambles of the corresponding PTCs while UE is in the switched off-state.
B.4.3
Inter Component Communication
Communication between PTCs or PTCs and the MTC can be done by messages or by build-in mechanisms as done and
kill. For maintenance reasons and extendibility the inter component communication shall be encapsulated by TTCN-3
implementation.
B.4.4
Encoding Information
For UE conformance tests several encoding rules need to be applied by the TTCN-3 codec. Even though the codec is
out of scope of the present document there are aspects with impact on TTCN-3 implementation depending on different
type definitions.
Table B.4.4-1
Type definitions
Encoding
ASN.1 types used for RRC signalling
ASN.1 PER
ASN.1 types used by NAS protocols
ASN.1 BER
NAS types
Tabular notated (see note)
SMS Types
Tabular notated (see note)
DRB types
Tabular notated (see note)
DHCPv4 types
Tabular notated (see note)
ICMPv6 types
Tabular notated (see note)
DNS types
Tabular notated (see note)
GERAN types
Tabular notated (see note)
GPRS Padding
see TS 34.123-3 [7], clause 6.10.2.9.1
GSM Spare Padding
see TS 34.123-3 [7], clause 6.10.2.9.2
LowHigh Rule
see TS 34.123-3 [7], clause 6.10.2.9.3
SACCHSysInfo Spare Padding
see TS 34.123-3 [7], clause 6.10.2.9.5
TTCN-3 types not used at the air interface:
- Configuration of system simulator
(no specific encoding required)
- Coordination between components
- Types used internally in TTCN-3
NOTE:
Tabular notated is performed by concatenation of all the present fields in the TTCN-3 template.
Encoding information may be provided and supported in TTCN-3 by grouping of type definitions and using the encode
attribute.
B.4.5
Verdict Assignment
In general the following rules shall be applied.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
255
ETSI TS 136 523-3 V13.2.0 (2017-03)
Table B.4.5-1: Rules for verdict assignment
Verdict
Pass
Fail
Inconc
Error
Rule
shall be assigned for each step defined in the prose of the test case
shall be assigned when there is a non-conformant signalling by the UE within the test body
shall be assigned outside the test body and when it is not unequivocal whether a misbehaviour is
caused by non-conformity of the UE signalling
In case of obvious programming or parameterisation errors (e.g. missing case in a select statement)
B.4.5.1 PASS verdict assignment
The PASS verdicts are assigned by test cases or test case specific functions.
For generic test procedures as specified in 36.508 cl. 6.4.2, the preliminary pass is assigned directly after the procedure
if all described in the procedure UL messages have been successfully received; this allows re-usage of these procedures
for other purposes.
B.4.5.2 FAIL or INCONC verdict assignment
The verdict FAIL or INCONC can be assigned in test cases, in the test case-specific function, in the common functions
and in the default behaviour.
Test case or test case-specific function:
In normal cases the common function f_EUTRA_SetVerdictFailOrInconc or f_UTRAN_SetVerdictFailOrInconc
shall be used to assign FAIL or INCONC depending on whether it is in the test body or outside of the body.
An exception is made in the NITZ test cases: TC 9.1.5.1 in 3GPP TS 36.523-1 [1], TC 9.4.10, TC 12.2.1.13, TC
12.2.1.14, TC 12.2.1.15 in 3GPP TS 34.123-1 [2], in the UE capability test cases: TC 8.4.5.1 in 3GPP TS
36.523-1 [1] and TC 8.1.5.7 in 3GPP TS 34.123-1 [2]: the function f_SetVerdict is used in the test body to
assign a FAIL verdict without stopping the execution of the test case.
If in test cases a verdict FAIL shall be assigned for watchdog timer timeouts this needs to be done explicitly.
Common Functions:
The majority of the common functions have no verdict assignment. If a verdicts assignment is required in some
common functions, the common function f_EUTRA_SetVerdictFailOrInconc or
f_UTRAN_SetVerdictFailOrInconc shall be used to assign FAIL or INCONC.
As an exception in the altstep a_EUTRA_RacingCond_AwaitRrcMessage an INCONC is assigned when the
RRC message and the L1/MAC indication are in the wrong order.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
256
ETSI TS 136 523-3 V13.2.0 (2017-03)
B.4.5.3 Verdict assignment in default behaviour
The default behaviour handles all events not being handled in test cases or functions. Whether the verdict FAIL or
INCONC to be assigned in the default behaviour it depends very much on the port where the event occurs.
Table B.4.5.3-1: Verdict assignment in default behaviour upon test ports
Test port
SYS
SYSIND
Message
SYSTEM_CTRL_CNF
SYSTEM_IND:
Error indication
SYSTEM_IND:
MAC indication
SYSTEM_IND:
L1 indication
Comment
unexpected confirmation
unspecific error at SS
(see note 1)
Verdict
INCONC
INCONC
FAIL in the test body INCONC
outside the test body
INCONC
RachPreamble, SchedReq, UL_HARQ may
be repeated by the UE in case of transmission
errors
(see note 1)
SRB
SRB_COMMON_IND
Any unexpected L3 signalling (see note 3)
FAIL in the test body INCONC
outside the test body
NASCTRL
NAS_CTRL_CNF
unexpected confirmation
INCONC
DRB
DRB_COMMON_IND
L2 and combined tests (see note 2)
FAIL in the test body INCONC
outside the test body
pure signalling tests (see note 2)
INCONC
UT
UT_COMMON_CNF
unexpected confirmation
INCONC
NOTE 1: L1/MAC indications need to be enabled by the test case therefore they occur only when being relevant for the
test case.
NOTE 2: L2 and combined tests can be distinguished from pure signalling tests by additional global information
controlled by f_EUTRA_TestBody_Set.
NOTE 3: Layer 3 signalling by definition covers NAS and RRC signalling i.e. in general unexpected RRC messages will
cause a FAIL in the body of any NAS test case as well as unexpected NAS messages will cause a FAIL in the
body of any RRC test case.
Table B.4.5.3-2: Verdict assignment in default behaviour when time-out
Timeout
Comment
Verdict
any timer
unspecific timeout (see note)
INCONC
NOTE:
Local timers of test cases or functions cannot be distinguished in the default behaviour.
B.4.6
Default Behaviour
As experience from UMTS conformance tests there shall be one standard default behaviour for each component.
The following rules shall be applied:
-
The standard default behaviour is activated during initialisation of the respective component.
In normal cases a TTCN writer does not need to care about the default.
-
In general there is only one default behaviour activated (i.e. the standard default behaviour).
-
The standard default behaviour shall cover all ports and timers of the component.
-
Whenever possible deviations from the standard default behaviour shall be implemented locally rather than by
introducing a new default behaviour.
If for exceptional cases the standard default behaviour needs to be replaced by another default behaviour or another
default behaviour needs to be activated on top, the TTCN writer is responsible:
-
to avoid side effects;
-
to restore the standard behaviour.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
B.4.7
257
ETSI TS 136 523-3 V13.2.0 (2017-03)
Templates for Sending and Receiving
Templates used for sending and receiving shall be separated in general:
-
A template shall be either for sending or for receiving; this shall be reflected in the prefix of the identifier.
-
Send templates shall use no receive templates and vice versa.
-
All parameters of a send template shall be restricted to:
-
-
values;
-
template (value);
-
template (omit).
Parameters of receive templates may allow wildcards. They can be:
-
values;
-
unrestricted template parameters;
-
template parameters restricted to be present.
-
The only exception to the above rule is for "quasi-constant" definitions, as described in note 5 of table B.3.1.
Otherwise, even when the same data is expected for sending and receiving templates, there shall be different
templates and the following rule shall be applied.
-
The receive template is assigned the send template e.g.:
-
-
template My_Type cr_Template := cs_Template
This results in separate definitions for sending and receiving and improves maintainability.
NOTE 1: For maintenance reasons, a send template shall never be derived from a receive template; and also a
receive template shall never be assigned to a send template.
NOTE 2: When a send template is assigned to a receive template, the formal parameters of the receive template
must follow the rules of send templates (i.e. it shall only contain 'template (value)', 'template (omit)' or
values only).
B.4.8
Logging
In general no explicit log statements shall be used. As an exception log may be used to report unexpected situations in
TTCN-3 like fatal programming error.
B.4.8.1 Prose Step Numbers
Informative comments containing the prose steps defined in 36.523-1 should be implemented according to the
following guidelines:
- They relate to the Expected Sequence steps in the prose
- They should not be placed in common functions
- They should only be placed in functions containing the test case body
- They should always start with //@siclog
- They should always finish with siclog@
- For single steps they should be in the form //@siclog "Step 1" siclog@
- For multiple steps (where several steps are completed in a common function), they should be in the form
//@siclog "Steps 1 - 3" siclog@ - i.e. Steps, space, first number, space, dash, space, second number
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
258
ETSI TS 136 523-3 V13.2.0 (2017-03)
- They should be placed as close as possible, but always BEFORE, the line send/receive/function call
- The step number should also be included in any pass/fail verdict specified in the test case body
- If the step is listed as Void (or a group of steps) in the expected sequence, include the word Void in the
comment.
Therefore the format of the comment should be:
//@siclog "Step[s] X [- Y] [Void]" siclog@
B.4.9
Top level comments
No restriction is specified for the top level comments.
B.4.10 Mapping of DRBs
LTE DRBs are mapped in TTCN according to the following rules:
-
DRB1 is exclusively reserved for the default DRB and hence is always AM
-
additional DRBs (AM or UM) may be assigned from DRB2 onward in any order
-
there shall be no reconfiguration of a DRB from AM to UM or vice versa (unless a test case explicitly requires
this); this especially means that DRB1 is never reconfigured to UM
-
in general at the SS all DRBs needed by a test case may be configured at the beginning of the test case.
B.5
Modularisation
Even though there are no specific rules how to apply modularisation in general some principles can be defined:
-
Maintainability and extendibility:
-
-
Maintainability and extendibility are essential for definition of the modular structure.
Granularity of modules:
-
Cyclic imports are forbidden in TTCN-3; this has impact on the extendibility:
-
-
Too big modules are hard to handle and may cause increase of compilation time:
-
NOTE:
-
The granularity of modules shall not be too small.
The granularity of modules shall not be too rough.
These are only vague principles since there is no way to define what small or huge modules are.
General module structure:
-
The following modularisation can be applied independent from the internal structure:
-
Type definitions: TTCN-3, ASN.1.
-
Component definitions.
-
Common Templates: component dependent, component independent.
-
Common behaviour: MTC, PTCs.
-
Test case specific templates.
-
Test case specific behaviour.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
-
259
ETSI TS 136 523-3 V13.2.0 (2017-03)
Whether or how these module groups can further be sub-divided is implementation dependent and therefore out
of scope of the present document.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
260
ETSI TS 136 523-3 V13.2.0 (2017-03)
Annex C (informative):
Design Principles
C.1
ASP Design
All ASPs consist of a common part (defined as a TTCN-3 type) and a specific part.
All ASPs sent by the SS include timing information (SFN, subframe number) in the common part.
Only one ASP is defined per direction per port, but this ASP may contain a union of several sub-ASPs in the specific
part.
In general a small number of common ASPs cover all functionality, although other ASPs may be introduced to simplify
TTCN-3 implementation and improve readability. Recurrent SS changes, such as power level changes, security
activation and MAC scheduling are handled in dedicated ASPs. In addition, special purpose ASPs are used to control
special behaviour, for example in L2 tests.
Configuration ASPs re-use ASN.1 definitions defined in the core specs.
No encoding rules are specified for the configuration ASPs; how they are encoded is left up to the SS implementation.
Configuration ASPs are 'procedure-based', rather than 'protocol layer-based' and reflect the state transitions of the SS.
The same ASPs are used for reconfiguration and for initial configuration. In the case of reconfiguration the semantics of
omit is to keep the configuration as it is; therefore when an IE in a configuration may be left out this is done e.g. by
setting the respective field to a special value "None".
Data ASPs for sending/receiving peer-to-peer PDUs and user data all have different ASPs for the different SAPs.
The common part includes (at least):
-
-
Timing Info:
-
SFN.
-
Subframe number (optional).
-
Which timing to use will depend on the test procedure and ASP purpose.
Control Info:
-
Confirmation Flag.
The RRC ASN.1 IEs used in the specific part of the configuration ASPs:
-
are imported using the granularity at the channel structure level or below;
-
allow the ASP to be organised according to SS requirements;
-
have a name that relates to SS configuration.
The SS specific IEs used in the specific part of the configuration ASPs (i.e. those elements not imported from the RRC
ASN.1):
-
use a naming convention such that they are easily distinguishable from the RRC ASN.1 IEs;
-
are defined in TTCN-3 (i.e. not in ASN.1).
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
C.2
261
ETSI TS 136 523-3 V13.2.0 (2017-03)
SS State Model
Figure C.2 shows the basic SS state model. It is basic in the sense that internally the SS may have more states; however,
(re)configuration actions (state transitions in the model) should cause the SS to transit between the states defined below.
The following assumptions have been made about this state model:
-
It presents a model of states in scope of a single cell. Hence, all configuration activities shall be performed in
scope of a single cell.
-
It depicts only SS states and SS (re)configuration actions between these states:
-
-
It does not show events which may trigger state transitions, e.g. L3 messages or procedures - i.e. it is test case
and L3 procedure agnostic.
-
It does not show any peer-to-peer (i.e. between SS and UE) messages.
Triggers for state transitions are always SS configuration messages (ASPs) coming from the test suite:
-
-
L2 messages coming from the UE can only trigger internal SS sub-state transitions and semi-autonomous
procedures.
L1 and L2 procedures (e.g. random access procedure, scheduling, security activation steps) are
semi-autonomously handled by the SS and after being pre-configured do not require interaction with the test
case:
-
The majority of test cases do not need to worry about e.g. RA procedure and letting the SS handle it would
greatly simplify test case definition and implementation.
-
There may be stringent time requirements in case of some procedures that can be hard to meet in a generic
way in the test suite.
-
Semi-autonomous procedures should be flexibly configurable and should have a "manual" mode in which
they are handled by the test suite in order to enable testing them. What is the desired level and way of control
is FFS.
Most states are stationary states, i.e. the SS can stay in them for a long time or, after performing some procedures,
returns to these states. However, there is one state (indicated by dashed lines) which is part of the AS security activation
procedure and is transitional, i.e. the SS can only stay in it for a short time until a transition the next stationary state is
triggered.
To make the diagram more readable, a separate state called ANY_STATE has been introduced, together with some
transitions. It shows which transitions are allowed at any point of time in any state.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
262
NOT_CONFIGURED
Add broadcasting cell
Add cell
Page UE
CELL_
BROADCASTING
Configure
NAS security
Post connection
setup configuration
CELL_ACTIVE
Configure RA
parameters
Activate
AS security
Release all RBs
Fail AS security
activation
AS_SECURITY_
ACTIVE
Configure RA
parameters
Reconfigure
physical layer
Configure
special mode
Add RBs
Reconfigure
AS security
Configure
special mode
RBS_ACTIVE
Configure
scheduling
Reconfigure
NAS security
Send MAC CE Configure
SPS
Reconfigure
RBs
NOT_CONFIGURED
Remove cell
ANY_STATE
Modify Power
Modify System Information
Figure C.2-1: Basic SS state model
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
263
ETSI TS 136 523-3 V13.2.0 (2017-03)
Description of states.
Table C.2-1: Description of states
State
NOT_CONFIGURED
CELL_BROADCASTING
CELL_ACTIVE
AS_SECURITY_ACTIVE
RBS_ACTIVE
ANY_STATE
Description
The cell does not exist (is not configured) in the SS
Physical DL channels and signals configured
Initial cell configuration done: freq, BW, antennas, MIMO mode, power, etc.
Transport and logical channels configured for SI broadcast
Cell is broadcasting SI and downlink signals
NOTE 1: This type of cell is needed only to serve as a neighbouring cell for
measurement purposes, where full cell configuration does not need to be
specified. There is no need to be able to promote a broadcasting cell to a
full cell.
NOTE 2: It is currently open whether a separate cell type with limited
PRACH/RACH Rx capability is needed - this depends on whether a
justified use case is defined for such a cell type.
Cell configured to send and receive data from UE (fully functional)
SRB0 defined (default configuration specified in TS 36.508 [3])
SRB1 defined (default configuration specified in TS 36.508 [3])
The SS has AS security (integrity protection and ciphering) active
NOTE 3: The SS needs to autonomously take care of a temporary state in which
integrity protection is applied to an outgoing SMC message, but ciphering
is not.
SRB2 and/or DRBs are configured for the UE (in addition to SRB0 and SRB1)
Represents any of the above states (except NOT_CONFIGURED)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
264
ETSI TS 136 523-3 V13.2.0 (2017-03)
Annex D (informative)
TTCN-3 Definitions
D.1
EUTRA_ASP_TypeDefs
Type definitions for configuration of the system simulator;
Common design principles:
Semantics of OMIT: for all TTCN-3 type definitions used in ASPs omit means "keep as it is" =>
- on initial configuration in general all fields shall be provided
- no default values for fields are foreseen
- if necessary non-existence of information shall be explicitly configured
(e.g. with a union of "no configuration" and "configuration parameters"
- fields within structures imported from the core spec are excepted from this rule
D.1.1
ASN1_Container
Definitions containing ASN.1 types for backward compatibility;
NOTE 1: PCCH_Message and BCCH_DL_SCH_Message already have a critical extension mechanism by RRC type
definition
NOTE 2: BCCH_BCH_Message contains the MIB and therefore is considered to be not extendable
NOTE 3: "simple types" are not considered: C_RNTI, PhysCellId, CellIdentity, ARFCN_ValueEUTRA
AntennaInfoDedicated_R8andLater_Type
TTCN-3 Record Type
Name
AntennaInfoDedicated_R8andLater_Type
Comment
antennaInfo
AntennaInfoDedicated
antennaInfo_v9 AntennaInfoDedicated_v92
opt
20
0
AntennaInfoDedicated_R10andLater_Type
TTCN-3 Record Type
Name
AntennaInfoDedicated_R10andLater_Type
Comment
antennaInfo
AntennaInfoDedicated_r10
antennaInfoUL
AntennaInfoUL_r10
opt
antennaInfoDe
AntennaInfoDedicated_v12
opt
dicated_v1250
50
CQI_ReportConfig_R8andLater_Type
TTCN-3 Record Type
Name
CQI_ReportConfig_R8andLater_Type
Comment
cqi_ReportConf CQI_ReportConfig
ig
cqi_ReportConf CQI_ReportConfig_v920
opt
ig_v920
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
265
ETSI TS 136 523-3 V13.2.0 (2017-03)
CQI_ReportConfig_R10andLater_Type
TTCN-3 Record Type
Name
CQI_ReportConfig_R10andLater_Type
Comment
cqi_ReportConf CQI_ReportConfig_r10
NOTE: field 'csi-SubframePatternConfig-r10' is not relevant as
ig_r10
long as a cell is configured as SCell
cqi_ReportConf CQI_ReportConfig_v1130
opt
ig_v1130
cqi_ReportConf CQI_ReportConfig_v1250
opt
ig_v1250
PUCCH_ConfigDedicated_R8andLater_Type
TTCN-3 Record Type
Name
PUCCH_ConfigDedicated_R8andLater_Type
Comment
pucch_ConfigD PUCCH_ConfigDedicated
edicated
pucch_ConfigD PUCCH_ConfigDedicated_
opt
edicated_v102
v1020
0
pucch_ConfigD PUCCH_ConfigDedicated_
opt
edicated_v113
v1130
0
pucch_ConfigD PUCCH_ConfigDedicated_
opt
edicated_v125
v1250
0
PUSCH_ConfigDedicated_R8andLater_Type
TTCN-3 Record Type
Name
PUSCH_ConfigDedicated_R8andLater_Type
Comment
pusch_ConfigD PUSCH_ConfigDedicated
in case of CA beta offset shall be the same for the PCell and the
edicated
associated SCells
pusch_ConfigD PUSCH_ConfigDedicated_
opt optionally present for Rel 10 cells (normal or CA); in case of CA
edicated_v102
v1020
beta offset shall be the same for the PCell and the associated
0
SCells
pusch_ConfigD PUSCH_ConfigDedicated_
opt
edicated_v113
v1130
0
pusch_ConfigD PUSCH_ConfigDedicated_
opt
edicated_v125
v1250
0
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
266
ETSI TS 136 523-3 V13.2.0 (2017-03)
UplinkPowerControlCommon_R8andLater_Type
TTCN-3 Record Type
Name
UplinkPowerControlCommon_R8andLater_Type
Comment
uplinkPowerCo UplinkPowerControlCommo
ntrolCommon
n
uplinkPowerCo UplinkPowerControlCommo opt optionally present for Rel 10 cells (normal or CA);
ntrolCommon_
n_v1020
NOTE: 'p0-NominalPUCCH', 'deltaFList-PUCCH',
v1020
'deltaPreambleMsg3' and 'UplinkPowerControlCommon-v1020'
are not relevant as long as a cell is configured as SCell
uplinkPowerCo UplinkPowerControlCommo opt only present when cell is configured as Rel 11 or later Scell
ntrolCommonS
nSCell_v1130
Cell_v1130
uplinkPowerCo UplinkPowerControlCommo opt
ntrolCommonP
nPSCell_r12
SCell_r12
UplinkPowerControlDedicated_R8andLater_Type
TTCN-3 Record Type
Name
UplinkPowerControlDedicated_R8andLater_Type
Comment
uplinkPowerCo UplinkPowerControlDedicat
ntrolDedicated
ed
uplinkPowerCo UplinkPowerControlDedicat opt optionally present for Rel 10 cells (normal or CA);
ntrolDedicated_ ed_v1020
NOTE: field 'p0-UE-PUCCH' is not relevant as long as a cell is
v1020
configured as SCell
pathlossRefere SCellPathlossReferenceLin
opt NOTE: relevant only as long as a cell is configured as SCell
king_Type
nceLinking
uplinkPowerCo UplinkPowerControlDedicat opt
ntrolDedicated_ ed_v1130
v1130
uplinkPowerCo UplinkPowerControlDedicat opt
ntrolDedicated_ ed_v1250
v1250
SoundingRS_UL_ConfigDedicated_R8andLater_Type
TTCN-3 Record Type
Name
SoundingRS_UL_ConfigDedicated_R8andLater_Type
Comment
soundingRS_U SoundingRS_UL_ConfigDe
opt
L_ConfigDedic
dicated
ated
soundingRS_U SoundingRS_UL_ConfigDe
opt
L_ConfigDedic
dicated_v1020
ated_v1020
soundingRS_U SoundingRS_UL_ConfigDe
opt
L_ConfigDedic
dicatedAperiodic_r10
atedAperiodic_r
10
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
267
ETSI TS 136 523-3 V13.2.0 (2017-03)
SchedulingRequestConfig_R8andLater_Type
TTCN-3 Record Type
Name
SchedulingRequestConfig_R8andLater_Type
Comment
schedulingReq
SchedulingRequestConfig
uestConfig
schedulingReq
SchedulingRequestConfig_
opt
uestConfig_v10 v1020
20
TDD_Config_R8andLater_Type
TTCN-3 Record Type
Name
TDD_Config_R8andLater_Type
Comment
R8
TDD_Config
tdd_Config_v11 TDD_Config_v1130
opt
30
RACH_ConfigCommon_R8andLater_Type
TTCN-3 Record Type
Name
RACH_ConfigCommon_R8andLater_Type
Comment
rach_ConfigCo
RACH_ConfigCommon
All parameters in RACH_ConfigCommonScell_r11 are covered
mmon
by RACH_ConfigCommon;
RACH_ConfigCommon will be used in Scell also for a complete
set of RACH parameters both when configured as a Scell or
normal RACH procedure when it seazes to exist as Scell;
when cell is configured as Scell, additional parameters shall be
ignored by SS
rach_ConfigCo
RACH_ConfigCommon_v1
opt
mmon_v1250
250
TDD_Config_Type
TTCN-3 Union Type
Name
TDD_Config_Type
Comment
R8andLater
TDD_Config_R8andLater_Type
AntennaInfoCommon_Type
TTCN-3 Union Type
Name
AntennaInfoCommon_Type
Comment
R8
AntennaInfoCommon
AntennaInfoDedicated_Type
TTCN-3 Union Type
Name
AntennaInfoDedicated_Type
Comment
NOTE: acc. to Cond AI-r8/AI-r10 of PhysicalConfigDedicated 'antennaInfo'/'antennaInfo-v920' and
'antennaInfo-r10' are mutual exclusive
R8andLater
AntennaInfoDedicated_R8andLat
er_Type
R10andLater
AntennaInfoDedicated_R10andLa
ter_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
268
ETSI TS 136 523-3 V13.2.0 (2017-03)
PHICH_Config_Type
TTCN-3 Union Type
Name
PHICH_Config_Type
Comment
R8
PHICH_Config
PRACH_Config_Type
TTCN-3 Union Type
Name
PRACH_Config_Type
Comment
R8
PRACH_Config
R8andLater
PRACH_Config_R8andLater_Typ
e
To be removed after grace period
PRACH_Config_R8andLater_Type
TTCN-3 Record Type
Name
PRACH_Config_R8andLater_Type
Comment
prach_Config
PRACH_Config
prach_Config_v PRACH_Config_v1310
opt
1310
PUCCH_ConfigCommon_Type
TTCN-3 Union Type
Name
PUCCH_ConfigCommon_Type
Comment
R8
PUCCH_ConfigCommon
R8andLater
PUCCH_ConfigCommon_R8andL
ater_Type
To be removed after grace period
PUCCH_ConfigCommon_R8andLater_Type
TTCN-3 Record Type
Name
PUCCH_ConfigCommon_R8andLater_Type
Comment
pucch_ConfigC PUCCH_ConfigCommon
ommon
pucch_ConfigC PUCCH_ConfigCommon_v
opt
ommon_v1310
1310
PUCCH_ConfigDedicated_Type
TTCN-3 Union Type
Name
PUCCH_ConfigDedicated_Type
Comment
R8andLater
PUCCH_ConfigDedicated_R8and
Later_Type
R13andLater
PUCCH_ConfigDedicated_R13an
dLater_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
269
ETSI TS 136 523-3 V13.2.0 (2017-03)
PUCCH_ConfigDedicated_R13andLater_Type
TTCN-3 Record Type
Name
PUCCH_ConfigDedicated_R13andLater_Type
Comment
pucch_ConfigD PUCCH_ConfigDedicated_r
E-UTRAN configures pucch-ConfigDedicated-r13 only if pucchedicated_r13
13
ConfigDedicated is not configured
PUSCH_ConfigCommon_Type
TTCN-3 Union Type
Name
PUSCH_ConfigCommon_Type
Comment
R8
PUSCH_ConfigCommon
R8andLater
PUSCH_ConfigCommon_R8andL
ater_Type
To be removed after grace period
PUSCH_ConfigCommon_R8andLater_Type
TTCN-3 Record Type
Name
PUSCH_ConfigCommon_R8andLater_Type
Comment
pusch_ConfigC PUSCH_ConfigCommon
ommon
pusch_ConfigC PUSCH_ConfigCommon_v
opt
ommon_v1270
1270
pusch_ConfigC PUSCH_ConfigCommon_v
opt
ommon_v1310
1310
PUSCH_ConfigDedicated_Type
TTCN-3 Union Type
Name
PUSCH_ConfigDedicated_Type
Comment
R8andLater
PUSCH_ConfigDedicated_R8and
Later_Type
R13andLater
PUSCH_ConfigDedicated_R13an
dLater_Type
PUSCH_ConfigDedicated_R13andLater_Type
TTCN-3 Record Type
Name
PUSCH_ConfigDedicated_R13andLater_Type
Comment
pusch_ConfigD PUSCH_ConfigDedicated_r
E-UTRAN configures pusch-ConfigDedicated-r13 only if puschedicated_r13
13
ConfigDedicated is not configured
SoundingRS_UL_ConfigCommon_Type
TTCN-3 Union Type
Name
SoundingRS_UL_ConfigCommon_Type
Comment
R8
SoundingRS_UL_ConfigCommon
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
270
ETSI TS 136 523-3 V13.2.0 (2017-03)
SoundingRS_UL_ConfigDedicated_Type
TTCN-3 Union Type
Name
SoundingRS_UL_ConfigDedicated_Type
Comment
R8andLater
SoundingRS_UL_ConfigDedicate
d_R8andLater_Type
SchedulingRequestConfig_Type
TTCN-3 Union Type
Name
SchedulingRequestConfig_Type
Comment
R8andLater
SchedulingRequestConfig_R8and
Later_Type
CQI_ReportConfig_Type
TTCN-3 Union Type
Name
CQI_ReportConfig_Type
Comment
NOTE: acc. to Cond CQI-r8/CQI-r10 of PhysicalConfigDedicated 'cqi-ReportConfig'/'cqi-ReportConfigv920' and 'cqi-ReportConfig-r10' are mutual exclusive
R8andLater
CQI_ReportConfig_R8andLater_T
ype
R10andLater
CQI_ReportConfig_R10andLater_
Type
RACH_ConfigCommon_Type
TTCN-3 Union Type
Name
RACH_ConfigCommon_Type
Comment
R8
RACH_ConfigCommon
R8andLater
In an active Scell, the SS uses the necessary parameters defined
in RACH-ConfigCommonSCell-r11 and ignores additional
parameters;
The additional parameters will be applicable when the cell seizes
to exist as scell
RACH_ConfigCommon_R8andLa
ter_Type
RACH_ConfigDedicated_Type
TTCN-3 Union Type
Name
RACH_ConfigDedicated_Type
Comment
R8
RACH_ConfigDedicated
MeasGapConfig_Type
TTCN-3 Union Type
Name
MeasGapConfig_Type
Comment
R8
MeasGapConfig
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
271
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_Config_Type
TTCN-3 Union Type
Name
PDCP_Config_Type
Comment
R8
PDCP_Config
UL_AM_RLC_Type
TTCN-3 Union Type
Name
UL_AM_RLC_Type
Comment
R8
UL_AM_RLC
DL_AM_RLC_Type
TTCN-3 Union Type
Name
DL_AM_RLC_Type
Comment
R8
DL_AM_RLC
UL_UM_RLC_Type
TTCN-3 Union Type
Name
UL_UM_RLC_Type
Comment
R8
UL_UM_RLC
DL_UM_RLC_Type
TTCN-3 Union Type
Name
DL_UM_RLC_Type
Comment
R8
DL_UM_RLC
TTI_BundlingConfig_R8andLater_Type
TTCN-3 Record Type
Name
TTI_BundlingConfig_R8andLater_Type
Comment
TTI_BundlingE
TTI_Bundling_Type
nabled
E_HARQ_Patte E_HARQ_Pattern_r12_Typ
opt
e
rn
TTI_BundlingConfig_Type
TTCN-3 Union Type
Name
TTI_BundlingConfig_Type
Comment
R8
boolean
R8andLater
TTI_BundlingConfig_R8andLater_
Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
272
DRX_Config_R8andLater_Type
TTCN-3 Record Type
Name
DRX_Config_R8andLater_Type
Comment
R8
DRX_Config
opt
R13
DRX_Config_r13_Type
opt
EDRX_CycleSt EDRX_CycleStartOffset_r1
opt
artOffset_r13
3_Type
DRX_Config_Type
TTCN-3 Union Type
Name
DRX_Config_Type
Comment
R8
DRX_Config
R8andLater
DRX_Config_R8andLater_Type
SpsConfigurationDL_Type
TTCN-3 Union Type
Name
SpsConfigurationDL_Type
Comment
R8
SPS_ConfigDL.setup
SpsConfigurationUL_Type
TTCN-3 Union Type
Name
SpsConfigurationUL_Type
Comment
R8
SPS_ConfigUL.setup
UplinkPowerControlCommon_Type
TTCN-3 Union Type
Name
UplinkPowerControlCommon_Type
Comment
R8andLater
UplinkPowerControlCommon_R8
andLater_Type
UplinkPowerControlDedicated_Type
TTCN-3 Union Type
Name
UplinkPowerControlDedicated_Type
Comment
R8andLater
UplinkPowerControlDedicated_R8
andLater_Type
ETSI
ETSI TS 136 523-3 V13.2.0 (2017-03)
3GPP TS 36.523-3 version 13.2.0 Release 13
273
ETSI TS 136 523-3 V13.2.0 (2017-03)
CSI_RS_Config_Type
TTCN-3 Record Type
Name
CSI_RS_Config_Type
Comment
CSI_RS_Confi
CSI_RS_Config_r10
g
CSI_RS_Confi
CSI_RS_ConfigNZPToAdd
gNZPToAddMo ModList_r11
dList
CSI_RS_Confi
CSI_RS_ConfigNZPToRele
gNZPToReleas aseList_r11
eModList
CSI_RS_Confi
CSI_RS_ConfigZPToAddM
gZPToAddMod odList_r11
List
CSI_RS_Confi
CSI_RS_ConfigZPToRelea
gZPToRelease
seList_r11
ModList
D.1.2
opt
The IE is used for TM1-9
opt
The IE is to configure the non-zero power CSI-RS resource
configuration
opt
The IE is to release the non-zero power CSI-RS resource
configuration
opt
The IE is to configure the zero power CSI-RS resource
configuration
opt
The IE is to release the zero power CSI-RS resource
configuration
System_Configuration
Formal ASP Definitions for system configuration
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
274
ETSI TS 136 523-3 V13.2.0 (2017-03)
SystemRequest_Type
TTCN-3 Union Type
Name
SystemRequest_Type
Comment
Cell
CellConfigRequest_Type
CellAttenuation CellAttenuationList_Type
List
RadioBearerLis
t
EnquireTiming
AS_Security
Sps
Paging
RadioBearerList_Type
L1MacIndCtrl
RlcIndCtrl
PdcpCount
PdcpHandover
Control
L1_TestMode
PdcchOrder
L1Mac_IndicationControl_Type
Rlc_IndicationControl_Type
PDCP_CountReq_Type
PDCP_HandoverControlReq_Typ
e
L1_TestMode_Type
RA_PDCCH_Order_Type
ActivateScell
ActivateScell_Type
MbmsConfig
PDCCH_MCC
H_ChangeNotif
ication
MSI_Config
MBMS_Config_Type
PDCCH_MCCH_ChangeNotificati
on_Type
UE_Cat_Info
UE_CategoryInfo_Type
OCNG_Config
OCNG_Config_Type
PdcchTddConfi
gOrder
PDCCH_TDD_ConfigOrder_Type
DirectIndication
Info
DirectIndicationInfoTrigger_Type
Null_Type
AS_Security_Type
SpsConfig_Type
PagingTrigger_Type
MSI_Config_Type
configure/release a cell
power attenuation for one or several cells;
all cells included in the list shall be changed at the same time;
all cells in the list shall reach the new cell power within a
maximum of 100ms (10 frames)
acc. to the tolerances given in TS 36.508
NOTE: In the common ASP part the CellId shall be set
- to the cell the timing information refers to if activation time shall
be applied
- to eutra_Cell_NonSpecific when there is no activation time
configure/release one or several SRBs and/or DRBs
NOTE: RBs are not configured in an SCell
get SFN and sub-frame number for this cell
StartRestart/Release of AS security
to configure/activate or release semi-persistent scheduling
to trigger SS to send paging at the given paging occasion (as
calculated in TTCN)
to configure SS to generate indications for L1/MAC events
to configure SS to generate indications for RLC events
to set or enquire PDCP COUNT for one ore more RBs
to inform the target cell about the handover
To Set L1/MAC in special Test modes e.g. DL CRC, PHICH etc
to configure SS to transmit a PDCCH order with configured CRNTI to the UE
to trigger RA procedure;
result in DCI Format 1A transmission as in TS 36.212, clause
5.3.3.1.3
to configure SS to transmit a MAC control Element to activate an
Scell
Configuration of PMCH/MCCH/MTCH for eMBMS
To trigger SS to send MCCH change notification at the given
SFN/subframe (as calculated in TTCN)
Configuration of MSI in MBMS normal mode to be included by
the SS in the first subframe allocated to the MCH within the MCH
scheduling period;
uses MRB_ID option in routing info and logical channel ID is
omitted
provides UE category info to SS; to be used e.g. for
determination of Nsoft bits for rate matching
To be configured in SS after preamble in MAC TBS test cases
Provides SS Mode for Activating/Releasing OCNG configuration
in the cell
To trigger SS to send DCI 1C message(s) from a given
SFN/subframe (as calculated in TTCN) over PDCCH with CRC
scrambled by the eIMTA-RNTI,
to indicate the eIMTA-UL/DL-configuration.
The SS shall set the DCI 1C content according to
eimta_UL_DL_ConfigIndex_r12 provided in EIMTA_Config
To Trigger SS to transmit a Direct Indication information using
DCI command 6_2 and including the 8 bits in the DCI command
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
275
ETSI TS 136 523-3 V13.2.0 (2017-03)
SystemConfirm_Type
TTCN-3 Union Type
Name
SystemConfirm_Type
Comment
confirmations for system configuration;
in general to be sent after the configuration has been done
Cell
Null_Type
(no further parameters from SS)
CellAttenuation Null_Type
(no further parameters from SS)
List
NOTE 1:
the confirmation shall be sent when all cells have changed power
levels
NOTE 2:
for the CellId in the common ASP part the same rules are applied
as for the SYSTEM REQ
RadioBearerLis Null_Type
(no further parameters from SS)
t
EnquireTiming
Null_Type
SFN and sub-frame number are included in the TimingInfo
AS_Security
Null_Type
(no further parameters from SS)
Sps
Null_Type
(no further parameters from SS)
Paging
Null_Type
normally not needed but defined for completeness
L1MacIndCtrl
Null_Type
(no further parameters from SS)
RlcIndCtrl
Null_Type
(no further parameters from SS)
PdcpCount
PDCP_CountCnf_Type
as response to 'Get' a list is returned containing COUNT
information for the requested RBs
PdcpHandover
Null_Type
confirmation for PDCP handover control
Control
L1_TestMode
Null_Type
confirmation for L1 test mode
PdcchOrder
Null_Type
confirmation for PDCCH Order
ActivateScell
Null_Type
confirmation for ActivateScell
MbmsConfig
Null_Type
confirmation for MbmsConfig
PDCCH_MCC
Null_Type
normally not needed but defined for completeness
H_ChangeNotif
ication
MSI_Config
Null_Type
confirmation for explicit MSI Configuration
UE_Cat_Info
Null_Type
confirmation for UE CAT info
OCNG_Config
Null_Type
Confirmation of OCNG configuration
DirectIndication Null_Type
Confirmation of DirectIndicationInfo
Info
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
276
ETSI TS 136 523-3 V13.2.0 (2017-03)
SystemIndication_Type
TTCN-3 Union Type
Name
SystemIndication_Type
Comment
Error
charstring
RachPreamble
RachPreamble_Type
SchedReq
BSR
UL_HARQ
Null_Type
BSR_Type
HARQ_Type
C_RNTI
PHR
HarqError
C_RNTI
PHR_Type
HarqError_Type
RlcDiscardInd
PeriodicRI
RlcDiscardInd_Type
RI_Type
EPHR
CqiInd
MAC_CTRL_ExtPowerHeadRoo
m_Type
Null_Type
SrsInd
SRSInd_Type
DC_PHR
MAC_CTRL_DC_PowerHeadRoo
m_Type
D.1.3
indicates an error situation in SS;
is not explicitly handled in TTCN but causes an INCONC due to
default behaviour;
an additional error code can be signalled in the common part of
the ASP;
SS shall raise an error in case of
- Invalid TimingInfo for TDD
- Contradiction of periodic UL grants and TDD configuration
- Data scheduled for the same TTI does not fit into an available
transport block
(NOTE: additional cases may occur)
RACH preamble being sent by the UE
In case of Preamble repetition (BL/CE UE under test) the SS
sends one indication after reception of all preamble repetitions of
a preamble attempt based on the CE level of UE.
indication for scheduling request sent by the UE
to report the Buffer/Extended Buffer status report being received
to report the UL HARQ as received on PUCCH[TTI] for
corresponding DL transmission in TTI-x,
where x is normally 4
indicates C-RNTI being contained in a MAC PDU sent by the UE
to report the Power headroom report received
indicates detection of HARQ error:
1. HARQ CRC error for UL data
2. HARQ NACK from the UE unless SS is configured to report
HARQ ACK/NACK
indicates e.g. discarded PDUs
indicates periodic Rank Indicator (RI) reported by the UE on
PUCCH or PUSCH;
periodic CQI/PMI/RI Reporting is semi-statically configured at the
UE by higher layers (see TS 36.213 clause 7.2.2);
aperiodic reporting acc. to TS 36.213 clause 7.2.1 shall not be
indicated
NOTE:
Acc. to TS 36.213 clause 7.2 aperiodic reporting has higher
precedence than periodic reporting;
=> as working assumption the CQI request field in DCI format 0
is expected to be 0 for UL grants assigned by the SS i.e.
aperiodic reporting acc. to TS 213 clause 7.2.1 does not happen
indicates Extended Power headroom report reported by the UE
indicates periodic CQI reported by the UE - NOTE: Report CQI
value is currently not required
Indicates start or stop of Type 0 SRS reception on configured
periodic SRS resources
indicates Dual Connectivity Power headroom report reported by
the UE
Cell_Configuration
Specific Info for Cell Configuration Primitive
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
277
D.1.3.1 Cell_Configuration_Common
Cell_Configuration_Common: Basic Type Definitions
TTCN-3 Basic Types
EUTRA_FDD_Info_Type
CfiValue_Type
Null_Type
integer (1..3)
no further parameters defined for FDD
CellConfigRequest_Type
TTCN-3 Union Type
Name
CellConfigRequest_Type
Comment
AddOrReconfig CellConfigInfo_Type
ure
Release
Null_Type
for cell configuration:
CellId : identifier of the cell to be configured
RoutingInfo : None
TimingInfo : Now (for initial configuration and for reconfiguration
in general)
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
to remove a cell completely CellId : identifier of the cell to be released;
eutra_Cell_NonSpecific, in case all cells shall be released
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
CellConfigInfo_Type
TTCN-3 Record Type
Name
CellConfigInfo_Type
Comment
common information for initial cell configuration or reconfiguration;
in case of reconfiguration OMIT means 'keep configuration as it is'
Basic
BasicCellConfig_Type
opt basic information for a cell (e.g. broadcasting)
Active
ActiveCellConfig_Type
opt add. configuration for active cell (i.e. cell being capable to receive
RACH preamble)
CellConfigCapability_Type
TTCN-3 Enumerated Type
Name
CellConfigCapability_Type
Comment
capabilities af a cell acc. to the initial condition of a test case
broadcastOnlyCell
no detection of RACH preables required; cell is only broadcasting
minimumUplinkCell
detection of RACH preables required but not any further RX capability
fullCell
full TX and RX capabilities
CA_CellInitialConfig_Type
TTCN-3 Enumerated Type
Name
CA_CellInitialConfig_Type
Comment
PCell
The cell when added as a CC in CA scenario for first time will be configured as an PCell
Scell_Active
The cell when added as a CC in CA scenario for first time will be configured as an SCell, and
when configured as Scell, it may be activated, 36.508 clause 6.3.4
Scell_Inactive
The cell when added as a CC in CA scenario for first time will be configured as an SCell, and
when configured as Scell, it will never be activated, 36.508 clause 6.3.4
PScell
The cell when added as a CC in CA-Dual connectivity scenario for first time will be configured
as a PSCell. PSCell is always active like PCell
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
278
ETSI TS 136 523-3 V13.2.0 (2017-03)
BasicCellConfig_Type
TTCN-3 Record Type
Name
BasicCellConfig_Type
Comment
ConfigCapabilit CellConfigCapability_Type
y
StaticCellInfo
StaticCellInfo_Type
PhysicalLayerC PhysicalLayerConfigDL_Ty
pe
onfigDL
InitialCellPower InitialCellPower_Type
opt
mandatory for the initial configuration; to be omitted afterwards
opt
opt
Common information which does not change during a test
default settings regarding physical control channels: PCFICH,
PHICH, PDCCH
reference cell power for the RS of each antenna in DL
NOTE 1:
the power of the RS of an antenna may be reduced by antenna
specific configuration
NOTE 2:
in general the power may be adjusted on a per resource element
basis
=> all physical channel/signal power settings shall be ajusted
relatively to the RS;
if there are more than one TX antennas each one may have its
own attenuation;
independently from those relative power settings the cell power
can easily be adjusted by just changing the reference power
configuration of BCCH/BCH; SS is triggered to configure
RLC/MAC regardingly;
BCCH data on the PDSCH is distinguished by the SI-RNTI
PBCH: MIB;
PDSCH: scheduling and resource allocation; SIBs
configuration of PCCH/PCH; SS is triggered to configure
RLC/MAC regardingly;
PCCH data on the PDSCH is distinguished by the P-RNTI
(needed even to modify SI => shall be configured for
CELL_BROADCASTING)
capability of a cell when added as a CC in CA scenario.
1. Provided at the initial configuration of a cell in CA test cases;
to be omitted afterwards;
2. Always omit for a cell which remains normal non CA cell
configuration of BCCH_BR/BCH; SS is triggered to configure
RLC/MAC regardingly;
BCCH_BR data on the PDSCH is follows fixed schedule hence
no SI-RNTI DCI sent
PBCH: MIB;
PDSCH: scheduling and resource allocation; SIBs
LAA specific information provided if the cell is being configured
as Scell with frame structure 3 i.e. in Unlicensed band
opt
BcchConfig
BcchConfig_Type
opt
PcchConfig
PcchConfig_Type
opt
CA_CellInitialC
onfig
CA_CellInitialConfig_Type
opt
BRBcchConfig
Bcch_BRConfig_Type
opt
LAA_SCellConf
iguration
LAA_SCellConfiguration_r1
3
opt
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
279
ETSI TS 136 523-3 V13.2.0 (2017-03)
ActiveCellConfig_Type
TTCN-3 Record Type
Name
ActiveCellConfig_Type
Comment
C_RNTI
C_RNTI
opt
PhysicalLayerC
onfigUL
RachProcedure
Config
CcchDcchDtch
Config
ServingCellCon
fig
PhysicalLayerConfigUL_Ty
pe
RachProcedureConfig_Typ
e
CcchDcchDtchConfig_Type
opt
ServingCellConfig_Type
opt
SciScheduling
Config
EIMTA_Config
CE_Mode
SciSchedulingConfig_Type
opt
EIMTA_Config_Type
CE_Mode_r13_Type
opt
opt
opt
opt
(pre-)configured C-RNTI;
affects scrambling of PDSCH/PUSCH and CRC of PDCCH(s);
shall be used implicitly in RACH procedure (i.e. as CE in RAR)
parameters for PRACH, PUCCH, PUSCH
Omitted when no UL frequency is applied to the band
to configure the SS's behaviour for the RACH procedure
Omitted when no UL frequency is applied to the band
Parameters related to CCCH/DCCH/DTCH in UL and DL
not present as long as the cell is 'normal' cell (i.e. does not act as
a carrier component in CA);
present to configure cell for CA (Pcell or SCell);
in general at initial configuration 'ServingCellInfo' is omit;
after sending/scheduling the RRCConnectionReconfiguration
adding 1 or more cells for CA 'ServingCellInfo' is provided for the
cell which gets Pcell and for the cell which gets SCell
Parameters related to SideLink scheduling SCI format 0
Parameters related to eIMTA in UL and DL
Indicates the CE mode as specified in TS 36.213 It is FFS if this
can be ignored by SS
StaticCellInfo_Type
TTCN-3 Record Type
Name
StaticCellInfo_Type
Comment
Common information which (normally) does not change during a test;
therefore all fields are mandatory
Common
CommonStaticCellInfo_Typ
e
Downlink
DownlinkStaticCellInfo_Typ
e
Uplink
UplinkStaticCellInfo_Type
opt NOTE: for TDD UL and DL are using the same parameters
Omitted when no UL frequency is applied to the band
CommonStaticCellInfo_Type
TTCN-3 Record Type
Name
CommonStaticCellInfo_Type
Comment
information common for UL and DL; all fields are mandatory
RAT
EUTRA_RAT_Type
FDD or TDD; FDD/TDD specific parameters
PhysicalCellId
PhysCellId
N(cell, ID): imported from core spec;
-> cell specific reference signals (non-MBSFN)
-> scrambling of all DL physical channels:
PBCH, PCFICH, PDCCH, PHICH and PDSCH (together with
nRNTI)
eNB_CellId
CellIdentity
opt Placeholder for Cell identity (28 bits): eNB (20bits) and cell
identity (8bits).
The use of that field is for future usage and omit for the time
being
EutraBand
integer
NOTE:
in 3G there are overlapping bands therefore the band needs to
be provided;
in EUTRA it is provided as well to be extendable in the future
CellTimingInfo
CellTimingInfo_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
280
ETSI TS 136 523-3 V13.2.0 (2017-03)
EUTRA_TDD_Info_Type
TTCN-3 Record Type
Name
EUTRA_TDD_Info_Type
Comment
Configuration
TDD_Config_Type
TDD_Config acc. to RRC ASN.1 (acc. TS 36.331, clause 6.3.2 )
EUTRA_HalfDuplexFDD_Info_Type
TTCN-3 Record Type
Name
EUTRA_HalfDuplexFDD_Info_Type
Comment
NOTE: No specific elements required
When UE is FDD Type B Half-Duplex (i.e. Cat 0 and Half Duplex)
SS restricts non-explicitly scheduled UL data transmission in sub frame 2 and DL transmission in sub
frame 8. This results in
UL HARQ feedback in 8, DL HARQ feedback in sub frame 6, UL specific grant allocation in sub frame
8.
SS obeys explicit scheduling.
EUTRA_RAT_Type
TTCN-3 Union Type
Name
EUTRA_RAT_Type
Comment
specifies RAT type and frame structure (TS 36.211, clause 4)
FDD
EUTRA_FDD_Info_Type
TDD
EUTRA_TDD_Info_Type
HalfDuplexFDD EUTRA_HalfDuplexFDD_Info_Ty
pe
DownlinkStaticCellInfo_Type
TTCN-3 Record Type
Name
DownlinkStaticCellInfo_Type
Comment
DL Static Info
Earfcn
integer
Bandwidth
Dl_Bandwidth_Type
RBSize
EUTRA_RBSize_Type
CyclicPrefix
DL-EARFCN as defined in TS 36.101
N(DL, RB) = 6..110 (6, 15, 25, 50, 75, 100)
may be skipped assuming normal sub-carrier spacing => N(RB,
SC) = 12
EUTRA_CyclicPrefix_Type
UplinkStaticCellInfo_Type
TTCN-3 Record Type
Name
UplinkStaticCellInfo_Type
Comment
UL Static Info
Earfcn
integer
Bandwidth
Ul_Bandwidth_Type
CyclicPrefix
EUTRA_CyclicPrefix_Type
UL-EARFCN as defined in TS 36.101
N(DL, RB) = 6..110 (6, 15, 25, 50, 75, 100)
EUTRA_RBSize_Type
TTCN-3 Enumerated Type
Name
EUTRA_RBSize_Type
Comment
Resource Block Size in freq domain;
N(RB,SC) is 12 for normal sub-carrier spacing
n_RB_SC_12
n_RB_SC_24
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
281
ETSI TS 136 523-3 V13.2.0 (2017-03)
EUTRA_CyclicPrefix_Type
TTCN-3 Enumerated Type
Name
EUTRA_CyclicPrefix_Type
Comment
NOTE: in DL extended cyclic prefix depends on sub-carrier spacing
normal
extended
Modulation_Type
TTCN-3 Enumerated Type
Name
Modulation_Type
Comment
'unused' e.g. for 2nd codeword when there is no spatial multiplexing
unused
qpsk
qam16
qam64
ToRS_EPRE_Ratios_Type
TTCN-3 Record Type
Name
ToRS_EPRE_Ratios_Type
Comment
RA and RB ratios according to see TS 36.213, clause 5.2
RA
ToRS_EPRE_Ratio_Type
opt
RB
ToRS_EPRE_Ratio_Type
opt
UE_CategoryInfo_Type
TTCN-3 Record Type
Name
UE_CategoryInfo_Type
Comment
ue_Category
UE_Category_Type
ue_Category_V UE_Category_v1020_Type
1020
ue_Category_v UE_Category_v1170_Type
1170
ue_Category_v UE_Category_v11a0_Type
11a0
ue_Category_v UE_Category_v1250_Type
1250
ue_CategoryUL
_v1310
ue_CategoryDL
_v1310
UE_CategoryUL_v1310_Ty
pe
UE_CategoryDL_v1310_Ty
pe
opt
opt
opt
opt
If UE category is 0 then
1. SS shall forward UL CCCH SDU only when indicated with
LCHID '01011'B.
2. SS shall restrict DL UE-dedicated MAC TBS to 1000.
opt
opt
D.1.3.2 Downlink_Physical_Layer_Configuration
Downlink physical layer configuration:
- DL antenna configuration
- control region (PCFICH, PHICH, PDCCH)
- primary/secondary sync signals
- power control for physical channels and signals
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.1.3.2.1
ETSI TS 136 523-3 V13.2.0 (2017-03)
282
Antenna_Configuration
Antenna_Configuration: Basic Type Definitions
TTCN-3 Basic Types
AntennaPortId_Type
integer (0, 1, 2, 3, 4, 5, 6, 7, 8)
Antenna port 0..3: Cell specific reference
signals
Antenna port 4: MBSFN reference signals
Antenna port 5: UE specific reference
signals
Antenna port 6: Positioning reference
signals
Antenna port 7: UE specific reference
signals for dual layer beamforming
Antenna port 8: UE specific reference
signals for dual layer beamforming
(Antenna ports in DL acc. to 36.211 cl. 6.2.1)
AntennaPortInfo_Type
TTCN-3 Record Type
Name
AntennaPortInfo_Type
Comment
NOTE:
for conformance tests it may not be necessary to consider propagation pathes for different antennas;
=> fields of AntennaPortInfo_Type are used as place holders for future usage and are of
'Dummy_Type' for the time being
PowerAttenuati Dummy_Type
even though eNb shall send with the same power on all antennas
on
at the UE there may be different signal strength
=> RS will have reduced power
NOTE: the EPRE ratios (e.g. PDSCH-to-RS ratio) are assumed
to be equal for all antennas
PropagationDel Dummy_Type
signal from different antennas may have different propagation
ay
delay
AntennaPortConfig_Type
TTCN-3 Union Type
Name
AntennaPortConfig_Type
Comment
AddOrReconfig AntennaPortInfo_Type
ure
Release
Null_Type
add / re-configure antenna port
release antenna port
AntennaPort_Type
TTCN-3 Record Type
Name
AntennaPort_Type
Comment
Id
AntennaPortId_Type
Config
AntennaPortConfig_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
283
ETSI TS 136 523-3 V13.2.0 (2017-03)
DownlinkAntennaGroupConfig_Type
TTCN-3 Record Type
Name
DownlinkAntennaGroupConfig_Type
Comment
AntennaInfoCo
AntennaInfoCommon_Type
acc. to TS 36.331, clause 6.3.2; contains antennaPortsCount =
mmon
an1, an2, an4;
static parameter; will (normally) not be modified whilst a test;
NOTE:
information is redundant since number of antenna ports may
implicitly be determined by the number of ports being configured
AntennaPort
record length (1..4) of
1, 2 or 4 antennas;
AntennaPort_Type
from the UE's point of view each antenna may have a different
power level and a different propagation delay
D.1.3.2.2
Physical_Channels
PbchConfig_Type
TTCN-3 Record Type
Name
PbchConfig_Type
Comment
RelativeTxPow
ToRS_EPRE_Ratios_Type
er
opt
power ratio for PBCH's resource elements relative to the RS
PcfichConfig_Type
TTCN-3 Record Type
Name
PcfichConfig_Type
Comment
CfiValue
CfiValue_Type
RelativeTxPow
ToRS_EPRE_Ratios_Type
er
opt
opt
control format indicator signalled on PCFICH
power ratio for PFCICH's resource elements relative to the RS
PhichConfig_Type
TTCN-3 Record Type
Name
PhichConfig_Type
Comment
PhichConfig
PHICH_Config_Type
RelativeTxPow
er
opt
ToRS_EPRE_Ratios_Type
opt
parameters acc. TS 36.331, clause 6.3.2:
phich-Duration, phich-Resource;
may have impact on Cfi
power ratio for PHICH's resource elements relative to the RS
CCE_StartIndex_DL_UL_Type
TTCN-3 Record Type
Name
CCE_StartIndex_DL_UL_Type
Comment
CCE_St_Ind' or CCE_St_Ind'' acc. to table 7.1.1-1 in TS 36.523-3
CCE_StartInde integer
x_DL
CCE_StartInde integer
x_UL
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
284
ETSI TS 136 523-3 V13.2.0 (2017-03)
CCE_StartIndexList_Type
TTCN-3 Record of Type
Name
CCE_StartIndexList_Type
Comment
describes PDCCH candidates for all sub-frames
record length(10) of CCE_StartIndex_DL_UL_Type
PdcchCandidate_Type
TTCN-3 Record Type
Name
PdcchCandidate_Type
Comment
CCE start indeces for a given RNTI value acc. to table 7.1.1-1 in TS 36.523-3
RNTI
C_RNTI
RNTI value as per table 7.1.1-1
CCE_StartInde CCE_StartIndexList_Type
CCE Start Indices corresponding to the RNTI
xList
PdcchCandidateList_Type
TTCN-3 Record of Type
Name
PdcchCandidateList_Type
Comment
list of RNTIs and their corresponding CCE Start Indices
record of PdcchCandidate_Type
PdcchConfig_Type
TTCN-3 Record Type
Name
PdcchConfig_Type
Comment
UE performs blind detection for common and UE specific search spaces for different aggregation
levels (PDCCH formats acc. TS 36.211, clause 6.8.1)
content of the PDCCHs (DCI formats acc. TS 36.212, clause 5.3.3) shall be controlled together with
scheduling and resource allocation
CommonSearc
integer (2, 3)
opt PDCCH format for common search space;
hSpaceFormat
acc. to TS 36.213, clause 9.1.1 only aggregation level 4 and 8
are allowed (i.e. PDCCH format 2 and 3
UeSpecificSear integer (0, 1, 2, 3)
opt UE specific search space: corresponding aggregation levels 1, 2,
chSpaceForma
4, 8
t
PdcchCandidat PdcchCandidateList_Type
opt PDCCH candidate list acc. to table 7.1.1-1 in TS 36.523-3
eList
RelativeTxPow
ToRS_EPRE_Ratios_Type
opt power ratio for PDCCH's resource elements relative to the RS
er
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
285
ETSI TS 136 523-3 V13.2.0 (2017-03)
PdschRelativeTxPower_Type
TTCN-3 Record Type
Name
PdschRelativeTxPower_Type
Comment
NOTE 1:
the power control for the PDSCH is assumed to be (semi-)static for signalling conformance tests acc.
to TS 36.323;
nevertheless for different channels and purposes with the PDSCH there may be different power
settings;
NOTE 2:
acc. to TS 36.213, clause 5.2 the EPRE ratio is different in time domain for OFDM symbols containing
or not containing reference signals;
this needs to be considered by SS
RachResponse ToRS_EPRE_Ratios_Type
opt
BcchOnPdsch
ToRS_EPRE_Ratios_Type
opt
PcchOnPdsch
ToRS_EPRE_Ratios_Type
opt
CcchOnPdsch
ToRS_EPRE_Ratios_Type
opt
DcchDtchOnPd ToRS_EPRE_Ratios_Type
opt
sch
OcngOnPdsch
ToRS_EPRE_Ratios_Type
opt the power offset used for modeling allocations to virtual UE's
(different from the UE under test)
PdschConfig_Type
TTCN-3 Record Type
Name
PdschConfig_Type
Comment
RelativeTxPow
PdschRelativeTxPower_Ty
pe
er
PDSCH_Config PDSCH_ConfigCommon_v
Common
1310
opt
opt
EpdcchConfig_Type
TTCN-3 Record Type
Name
EpdcchConfig_Type
Comment
RelativeTxPow
ToRS_EPRE_Ratios_Type
er
ePdcchCandid
PdcchCandidateList_Type
ateList
EPDCCH_Conf EPDCCH_Config_r11
ig
D.1.3.2.3
opt
opt
opt
power ratio for ePDCCH's/MPDCCH(if configured) resource
elements relative to the RS
ePDCCH candidate list acc. to tables in TS 36.523-3 clause 7.1.2
If present with choice 'setup' SS starts using ePDCCH in
subframes reserved for ePDCCH for UL/DL grant transmission
on C-RNTI/SPS-RNTI and PDCCH in non reserved sub framesor
MPDCCH (if present) in all sub frames when using DCI formats
6-xx
If present with choice 'release' SS releases ePDCCH/MPDCCH
configuration and uses PDCCH for UL/DL grant transmission in
all sub frames
'omit' is no change from previous configuration
Physical_Signals
PrimarySyncSignal_Type
TTCN-3 Record Type
Name
PrimarySyncSignal_Type
Comment
RelativeTxPow
ToRS_EPRE_Ratios_Type
er
opt
power ratio for PSS's resource elements relative to the RS
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
286
ETSI TS 136 523-3 V13.2.0 (2017-03)
SecondarySyncSignal_Type
TTCN-3 Record Type
Name
SecondarySyncSignal_Type
Comment
RelativeTxPow
ToRS_EPRE_Ratios_Type
opt
er
power ratio for SSS's resource elements relative to the RS
SRS_UL_Config_Type
TTCN-3 Record Type
Name
SRS_UL_Config_Type
Comment
Common
SoundingRS_UL_ConfigCo
mmon_Type
Dedicated
SoundingRS_UL_ConfigDe
dicated_Type
PhysicalLayerConfigDL_Type
TTCN-3 Record Type
Name
PhysicalLayerConfigDL_Type
Comment
all fields are declared as optional to allow single reconfigurations; in this case omit means "keep as it
is"
AntennaGroup
DownlinkAntennaGroupCon opt
fig_Type
Pbch
PbchConfig_Type
opt
Pcfich
PcfichConfig_Type
opt
Phich
PhichConfig_Type
opt
Pdcch
PdcchConfig_Type
opt
Pdsch
PdschConfig_Type
opt
Pss
PrimarySyncSignal_Type
opt
Sss
SecondarySyncSignal_Typ
opt
e
CSI_RS_Confi
CSI_RS_Config_Type
opt Mandatory to be configured in CA PCell; in other cells if present
g
SS shall ignore it but shall apply the configuration if the cell is
promoted as PCell later on.
Pmch
PmchConfig_Type
opt Same power offset for all PMCH carrying MCCH or MTCH
Epdcch
EpdcchConfig_Type
opt
D.1.3.3 Uplink_Physical_Layer_Configuration
Uplink physical channel configuration: PRACH, PUCCH, PUSCH and UL RS
PUCCH_Configuration_Type
TTCN-3 Record Type
Name
PUCCH_Configuration_Type
Comment
Common
PUCCH_ConfigCommon_T opt
ype
Dedicated
PUCCH_ConfigDedicated_
opt
Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
287
PUSCH_Configuration_Type
TTCN-3 Record Type
Name
PUSCH_Configuration_Type
Comment
Common
PUSCH_ConfigCommon_T
opt
ype
Dedicated
PUSCH_ConfigDedicated_
opt
Type
PhysicalLayerConfigUL_Type
TTCN-3 Record Type
Name
PhysicalLayerConfigUL_Type
Comment
NOTE:
For the time being there is no requirement to configure the SS with TPC-PDCCH-Config;
In general SS is required to keep the UE's UL power constant
Prach
PRACH_Config_Type
opt parameters acc. TS 36.331, clause 6.3.2;
in general depending on FDD/TDD (see TS 36.211, clause 5.7)
Pucch
PUCCH_Configuration_Typ opt parameters acc. TS 36.331, clause 6.3.2
e
Pusch
PUSCH_Configuration_Typ opt parameters acc. TS 36.331, clause 6.3.2
e
(including configuration of RS)
TimingAdvance SS_TimingAdvanceConfig_ opt to adjust timing advance;
Type
normally timing advance is configured as 0 at the beginning and
never changed during the test case;
in some MAC test cases timing advance may be configured to a
non-zero (11 bit value) at the beginning and modified by (6 bit)
timing advance commands during the test
SRS_UL_Confi SRS_UL_Config_Type
opt sounding reference symbol (SRS); -> TS 36.213, clause 8.2, TS
g
36.211, clause 5.5.3
SR_Config
SchedulingRequestConfig_
opt PUCCH resources for scheduling requests acc. to TS 36.213
Type
table 10.15;
as signalled to the UE acc. to TS 36.331, clause 6.3.2
CQI_ReportCo
CQI_ReportConfig_Type
opt
nfig
UplinkPowerCo UplinkPowerControlCommo opt
ntrolCommon
n_Type
UplinkPowerCo UplinkPowerControlDedicat opt
ed_Type
ntrolDedicated
D.1.3.4 Common_MAC_Configuration
Transport channel and MAC related procedures and configuration
Common_MAC_Configuration: Basic Type Definitions
TTCN-3 Basic Types
ImcsValue_Type
RepetitionNumber_Type
DCISubframeRepetitionN
umber_Type
integer (0..31)
integer (0..7)
Modulation and coding scheme index coding
DCI Format 6-0A, value 0..3 as per 36.213
table 8.2b
DCI Format 6-0B, value 0..7 as per 36.213
table 8.2c
DCI Format 6-1A, value 0..3 as per 36.213
table 7.1.11-1
DCI Format 6-1B, 6_2, value 0..7 as per
36.213 table 7.1.11-2
36.213 clause as defined in section 9.1.5
integer (0..3)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
288
ETSI TS 136 523-3 V13.2.0 (2017-03)
RedundancyVersionListDL_Type
TTCN-3 Record of Type
Name
RedundancyVersionListDL_Type
Comment
NOTE:
in general the list shall contain maxHARQ-Tx elements;
if there are not enough elements specified SS shall raise an error;
per default the list is configured to 0,2,3,1,0 (TS 36.321, clause 5.4.2.2)
record length (1..28) of RedundancyVersion_Type
UL_TransRetransmission_Type
TTCN-3 Union Type
Name
UL_TransRetransmission_Type
Comment
NewTransmissi Null_Type
on
ReTransmissio
RedundancyVersion_Type
nAdaptive
ReTransmissio
Null_Type
nNonAdaptive
Retransmission RetransmissionAsynchronous_Ty
pe
Asynchronous
new transmission of data with redundancy version RV=0 (acc. to
TS 36.321 clause 5.4.2.2); NDI is toggled
SS assigns grant to requests retransmission of data with given
redundancy version; NDI is not toggled
place holder for non-adaptive retransmissions; SS does not send
any grant
Used to schedule time controlled asynchronous UL grant for
BL/CE UEs
RetransmissionAsynchronous_Type
TTCN-3 Record Type
Name
RetransmissionAsynchronous_Type
Comment
RedundencyVe RedundancyVersion_Type
SS assigns grant to requests retransmission of data with given
r
redundancy version; NDI is not toggled
SubframeOffset integer
the subframe offset since previous grant in the list, shall include
all repetitions
RepetitionNum
RepetitionNumber_Type
ber
DCISubframeR DCISubframeRepetitionNu
epetitionNumbe mber_Type
r
UL_TransRetransmissionList_Type
TTCN-3 Record of Type
Name
UL_TransRetransmissionList_Type
Comment
list of transmission and subsequent retransmissions:
in UL retransmissions are synchronous (every 8 TTIs for FDD);
independent from the HARQ_ModeList SS shall send grants for every adaptive retransmissions;
in case of non-adaptive retransmissions SS simply does not sent a grant (i.e.
ReTransmissionNonAdaptive elements are used to adjust timing of the adaptive
restransmissions only)
record length (1..28) of UL_TransRetransmission_Type
Imcs_Type
TTCN-3 Union Type
Name
Imcs_Type
Comment
Value
ImcsValue_Type
NotUsed
Null_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
289
ETSI TS 136 523-3 V13.2.0 (2017-03)
ULGrant_Period_Type
TTCN-3 Union Type
Name
ULGrant_Period_Type
Comment
OnlyOnce
Null_Type
Duration
integer (1..infinity)
grant is sent out only once; no period
duration of the grant period (TTI=1ms);
for TDD the starting time and periodicity need to be chosen in
TTCN so that the grants are assigned at valid subframes only;
otherwise SS shall raise an error
FreqDomainSchedulCommon_Type
TTCN-3 Record Type
Name
FreqDomainSchedulCommon_Type
Comment
common type to specify restrictions for frequency domain scheduling by a start index and a maximum
range of RBs;
in general the resource allocation refers to virtual resource blocks:
- format 1A (localised):
FirstRbIndex refers to the first physical RB; the RBs are subsequent (upto MaxRbCnt RBs);
may be applied for all kind of channels
- format 1C (distributed):
FirstRbIndex refers to the first virtual RB; the virtual RBs are subsequent (upto MaxRbCnt RBs)
but mapped (distributed) to physical resource; typically applied on BCCH, PCCH and RAR
- format 1 (localised):
FirstRbIndex refers to the first physical RB; RBs are not consecutive;
SS needs to provided bitmap of RBs (see TS 36.523-3) to cope with mapping of virtual resource
allocation (format 1C) applied on other channels;
typically there are either
- all channels having format 1A (localised)
- BCCH, PCCH and RAR having format 1C (distributed) + DTCH/DCCH having format 1
FirstRbIndex
integer
index of the first (vitual) resource block in frequency domain;
0 .. N(UL/DL, RB) - 1;
NOTE:
DCI format 1C refers to a virtual RB allocation i.e. the resource
block index;
differs from the physical resource allocation
where the RBs are distributed over the whole frequency
bandwidth (TS 36.213, clause 7.1.6.3)
MaxRbCnt
integer
max. number of resource blocks to be assigned;
FirstRbIndex + MaxRbCnt <= N(UL/DL, RB);
SS shall not assigned more than the given resource blocks to the
respective channel
(i.e. MaxRbCnt is the upper bound);
if the the configuration for a channel exceeds the total bandwidth
this is a TTCN error
(=> SS shall raise an error)
FreqDomainSchedulExplicit_Type
TTCN-3 Record Type
Name
FreqDomainSchedulExplicit_Type
Comment
type used for explicit DL scheduling; Nprb is the exact number of RBs whereas in
FreqDomainSchedulCommon_Type MaxRbCnt is the upper bound
FirstRbIndex
integer
index of the first resource block in frequency domain;
0 .. N(UL/DL, RB) - 1
Nprb
integer
number of resource blocks to be assigned;
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
290
ETSI TS 136 523-3 V13.2.0 (2017-03)
PdcchDciFormat_Type
TTCN-3 Enumerated Type
Name
PdcchDciFormat_Type
Comment
DCI format acc. to TS 36.212, clause 5.3.3.1;
SS shall apply physical parameters accordingly as specified in TS 36.508, clause 4.3.6
dci_0
physical layer parameters acc. TS 36.508 Table 4.3.6.1.1-1
dci_1
physical layer parameters acc. TS 36.508 Table 4.3.6.1.2-1
dci_1A
physical layer parameters acc. TS 36.508 Table 4.3.6.1.3-1
dci_1B
dci_1C
physical layer parameters acc. TS 36.508 Table 4.3.6.1.4-1
dci_1D
dci_2
physical layer parameters acc. TS 36.508 Table 4.3.6.1.5-1
dci_2A
physical layer parameters acc. TS 36.508 Table 4.3.6.1.6-1
dci_2B
dci_2C
dci_2D
dci_3
dci_3A
dci_4
dci_6_0A
DCI format 6-0A is used for the scheduling of PUSCH in one UL cell
dci_6_0B
DCI format 6-0B is used for the scheduling of PUSCH in one UL cell
dci_6_1A
DCI format 6-1A is used for the compact scheduling of one PDSCH codeword in one cell and
random access procedure initiated by a PDCCH order. The DCI corresponding to a PDCCH
order can be carried by MPDCCH
dci_6_1B
DCI format 6-1B is used for the scheduling of one PDSCH codeword in one cell
dci_6_2
DCI format 6-2 is used for for paging and direct indication
PdcchResourceAllocation_Type
TTCN-3 Enumerated Type
Name
PdcchResourceAllocation_Type
Comment
Resource allocation acc. TS 36.213, clause 7.1.6
ra_0
ra_1
ra_2_Localised
=> physical and virtual RB index are identical
ra_2_Distributed
=> virtual resource allocation
ra_Unspecified
=> None of above resource allocations and as specified by DCI format in 36.211. For example
used f0r DCI 6_1B
MIMO_PrecodingBits_Type
TTCN-3 Union Type
Name
MIMO_PrecodingBits_Type
Comment
Number of bits for precoding information acc. TS 36.212, table 5.3.3.1.5-3 and 5.3.3.1.5A-1
None
Null_Type
DCI 2A: 2 antenna ports at eNodeB (table 5.3.3.1.5A-1)
Bit2
B2_Type
DCI 2A: 4 antenna ports at eNodeB (table 5.3.3.1.5A-1)
Bit3
B3_Type
DCI 2: 2 antenna ports at eNodeB (table 5.3.3.1.5-3)
Bit6
B6_Type
DCI 2: 4 antenna ports at eNodeB (table 5.3.3.1.5-3)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
291
ETSI TS 136 523-3 V13.2.0 (2017-03)
MIMO_DciDlInfo_Type
TTCN-3 Record Type
Name
MIMO_DciDlInfo_Type
Comment
additional information for DL DCI in case of MIMO (i.e. when a 2nd CW is specified)
RedundancyVe RedundancyVersionListDL_ opt list of Redundancy version for 2nd code word;
Type
rsionList_2ndC
shall have the same length as RedundancyVersionList_1stCW;
W
if omit, for the 2nd CW the same RedundancyVersionList shall be
applied as for the 1st CW
CodeWordSwa B1_Type
transport block to codeword mapping acc. to TS 36.212 Table
pFlag
5.3.3.1.5-1
PrecodingBits
MIMO_PrecodingBits_Type
precoding information acc. TS 36.212, table 5.3.3.1.5-3 and
5.3.3.1.5A-1
DciDlInfoCommon_Type
TTCN-3 Record Type
Name
DciDlInfoCommon_Type
Comment
used for normal DL scheduling acc. to TS 36.523-3, clause 7.3
Format
PdcchDciFormat_Type
BCCH, PCCH and RACH Response: 1A or 1C (TS 36.213,
clause 7.1)
CCCH: 1A since transmission mode is not (may not be)
configured at the UE yet (TS 36.213, clause 7.1)
DTCH/DCCH: depending on transmission mode
ResourceAlloc
PdcchResourceAllocation_
depends on DCI format, e.g. ra_2_Localised or
Type
Type
ra_2_Distributed for DCI format 1A
Modulation_1st Modulation_Type
max. modulation scheme for the 1st code word;
CW
depending on the amount of data a lower modulation scheme
may be by SS but not a higher one;
BCCH, PCCH and RACH Response: QPSK only
Modulation_2n
Modulation_Type
modulation scheme for 2nd code word in case of spatial
dCW
multiplexing;
can be different than 1st code word (see TS 36.211, clause
6.3.2; TS 36.212, clause 5.3.3.1.5);
'unused' when there is no spatial multiplexing;
NOTE:
Acc. to 36.523-3 cl. 7.3.3.4 in normal mode MIMO shall not be
used
=> for the time being Modulation_2ndCW is always "unused"
FreqDomainSc
FreqDomainSchedulComm
index of 1st RB; max. number of RBs per TTI;
on_Type
hedul
NOTE:
in case of DCI format 1C the first RB index has no meaning since
distributed virtual resource blocks assigned in this case (TS
36.213, clause 7.1.6.3)
NOTE: For DCI formats used for BL/CE UEs i.e DCIs 6_X, this IE
identifies the Narrow band of 6 PRBs
RedundancyVe RedundancyVersionListDL_
list of Redundancy version to be used in case of retransmission;
Type
rsionList
the number of elements in the list provides the maxHARQ-Tx
RepetitionNum
RepetitionNumber_Type
opt used only for DCI format 6_X for BL/CE UEs
ber
DCISubframeR DCISubframeRepetitionNu
opt used only for DCI format 6_X for BL/CE UEs
epetitionNumbe mber_Type
r
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
292
ETSI TS 136 523-3 V13.2.0 (2017-03)
DciDlInfoExplicit_Type
TTCN-3 Record Type
Name
DciDlInfoExplicit_Type
Comment
used for explicit DL scheduling acc. to TS 36.523-3, clause 7.3
Imcs_1stCW
Imcs_Type
MCS index of table 7.1.7.1-1 of TS 36.213
Imcs_2ndCW
Imcs_Type
MCS index for the 2nd code word in case of MIMO;
'NotUsed' when MIMO is not used
Format
PdcchDciFormat_Type
ResourceAlloc
PdcchResourceAllocation_
Type
Type
FreqDomainSc
FreqDomainSchedulExplicit
For DCI formats used for BL/CE UEs i.e DCIs 6_X, this IE
_Type
hedul
identifies the resources in Narrow band of 6 PRBs
RedundancyVe RedundancyVersionListDL_
list of Redundancy version to be used in case of retransmission
Type
rsionList
the number of elements in the list provides the maxHARQ-Tx
MimoInfo
MIMO_DciDlInfo_Type
opt shall be present when Imcs_2ndCW specifies a 2nd CW to be
used;
shall be omit when Imcs_2ndCW is 'NotUsed'
RepetitionNum
RepetitionNumber_Type
opt used only for DCI format 6_X for BL/CE UEs
ber
DCISubframeR DCISubframeRepetitionNu
opt used only for DCI format 6_X for BL/CE UEs
epetitionNumbe mber_Type
r
DciDlInfo_Type
TTCN-3 Union Type
Name
DciDlInfo_Type
Comment
Auto
DciDlInfoCommon_Type
Explicit
DciDlInfoExplicit_Type
SS shall chose the appropriate TBS up to the maximim number
of resource blocks
used in MAC or RAB tests where exact TBS needs to be
specified
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
293
ETSI TS 136 523-3 V13.2.0 (2017-03)
DciUlInfo_Type
TTCN-3 Record Type
Name
DciUlInfo_Type
Comment
Imcs
Imcs_Type
TransRetransm UL_TransRetransmissionLi
st_Type
issionList
FreqDomainSc
hedul
Format
FreqDomainSchedulExplicit
_Type
PdcchDciFormat_Type
opt
HarqProcessId
integer
opt
RepetitionNum
ber
DCISubframeR
epetitionNumbe
r
RepetitionNumber_Type
opt
MCS index of table 8.6.1-1 of TS 36.213
list of possible retransmissions and their redundancy versions
(depending on being adapive or non-adaptive);
the list shall
- start with
- "New Transmission" (normal case) or
- "Adaptive Retransmission" (e.g. to request a retransmission
even when the data has been acknowledged with a HARQ ACK)
- end with "Adaptive Retransmission" (if there are
retransmissions)
NOTE1: TTCN implementation shall ensure that a
reconfiguration is done not before the previous list has been fully
processed
NOTE2: for normal operation the list contains only one
NewTransmission element (i.e. possible retransmissions are
non-adaptive)
For DCI formats used for BL/CE UEs i.e DCIs 6_0X, this IE
identifies the resources in Narrow band of 6 PRBs
If omit, default DCI format 0 will be applied; for BL/CE UEs 6_0X
shall be specified
Can be present in DCI format is not 6_0X; If present SS Uses the
specified HARQ process for all UL
transmissions/retransmissions;
used only for DCI format 6_X for BL/CE UEs
DCISubframeRepetitionNu
mber_Type
opt
used only for DCI format 6_X for BL/CE UEs
PeriodicGrant_Type
TTCN-3 Record Type
Name
PeriodicGrant_Type
Comment
Period
ULGrant_Period_Type
NoOfRepetition
s
TransmissionRepetition_Ty
pe
time period after which UL Grant need to be automatically
transmitted or 'OnlyOnce'
number of UL Grant repetitions to be automatically transmitted or
continuous repetition
UL_GrantConfig_Type
TTCN-3 Union Type
Name
UL_GrantConfig_Type
Comment
OnSR_Recepti
Null_Type
on
Periodic
PeriodicGrant_Type
PeriodicOnSR_
Reception
PeriodicGrant_Type
None
Null_Type
SS tranmits UL Grant as configured by CommonDciInfoUL_Type
at every reception of SR;
to be used in non L2 Test
SS tranmits UL Grant as configured by CommonDciInfoUL_Type
periodically;
to be used in L2 tests;
MAC tests testing Grants might set the period as infinite and num
grant as 1
SS tranmits UL Grant as configured by CommonDciInfoUL_Type
periodically; the periodic grant transmission
is started/restarted on reception of a SR from UE
to be used in non L2 Test to enable large UL data transmission
for lower category UEs (Cat<=1)
disable any grant transmission
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
294
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.1.3.5 Random_Access_Procedure
UplinkGrant_Type
TTCN-3 Record Type
Name
UplinkGrant_Type
Comment
TS 36.213, clause 6.2
HoppingFlag
B1_Type
RB_Allocation
B10_Type
ModAndCodSc B4_Type
heme
TPC_Comman
B3_Type
d
UL_Delay
B1_Type
CQI_Req
B1_Type
Hopping flag
Fixed size resource block assignment
Truncated modulation and coding scheme
TPC command for scheduled PUSCH
UL delay
CQI request
CRNTI_ContentionResolutionCtrl_Type
TTCN-3 Union Type
Name
CRNTI_ContentionResolutionCtrl_Type
Comment
configuration for Random Access Procedure in RRC_CONNECTED (see TS 36.300, clause 10.1.5.1);
when SS receives C-RNTI MAC element sent by the UE after Random Access Response,
SS shall deal with the C-RNTI as specified in this structure
AutomaticGrant DciUlInfo_Type
before expiry of the contention resolution timer SS shall
automatically address PDCCH
using C-RNTI as sent by the UE; the UL grant is specified acc. to
DciUlInfo_Type
None
Null_Type
Used in case of dedicated preamble transmission or to simulate
failure cases;
SS shall not address PDCCH using C-RNTI
=> expiry of contention resolution timer on UE side
ContentionResolutionCtrl_Type
TTCN-3 Union Type
Name
ContentionResolutionCtrl_Type
Comment
NOTE: SS only needs to consider one kind of contention resolution at one time;
in the initial configuration of a cell TCRNTI_Based shall be configured and
the common assuption is that in RRC_CONNECTED normally there are no RACH procedures
(i.e. no CRNTI_Based configuration needed)
whereas e.g. in case of handover scenarios CRNTI_Based shall be configured
TCRNTI_Base
TCRNTI_ContentionResolutionCtr TCRNTI based contention resolution (e.g. initial access),
l_Type
d
hence involves inclusion contention resolution identity in DL
message 4 of RACH procedure
CRNTI_Based
CRNTI_ContentionResolutionCtrl
CRNTI based contention resolution (e.g. in case UE is being in
_Type
RRC_CONNECTED):
hence uplink message in step 3 (of RACH procedure) is followed
by PDCCH transmission with UE C-RNTI to end procedure
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
295
ETSI TS 136 523-3 V13.2.0 (2017-03)
RandomAccessResponseParameters_Type
TTCN-3 Record Type
Name
RandomAccessResponseParameters_Type
Comment
paramenters to control content of RAR sent to the UE
RapId
RapIdCtrl_Type
to control Random Access Preamble Id to be sent back to the
UE; used in RAR MAC sub-header
InitialGrant
UplinkGrant_Type
initial UL grantgrant ; May be ignored if
UplinkGrantCE_Mode_Type is configured
TimingAdvance RACH_TimingAdvance_Ty
timing advance: granularity of 0.52 micro sec (16*Ts);
pe
see TS 36.300, clause 5.2.7.3, TS 36.321, clause 6.1.3.5;
NOTE:
timing advance has impact not only on the RA procedure;
SS in general needs to adjust its timing accordingly
TempC_RNTI
TempC_RNTI_Type
NOTE:
For initial Random Access Procedure at network (SS) side there
is no temporary C-RNTI:
network assigns the C-RNTI which is used by any UE as being
temporary;
the UE which 'wins' the contention resolution keeps the
(temporary) C-RNTI;
other UEs need to repeat the RACH procedure;
=> at the SS the TempC_RNTI shall be 'SameAsC_RNTI'
For Random Access Procedure in RRC_CONNECTED state the
NW assigns a temporary C-RNTI which is replaced by the one
stored at the UE;
=> TempC_RNTI may be 'SameAsC_RNTI' (in this case temp.
C-RNTI and C-RNTI are equal what is not likely in a real
network),
or there is an explicit temp. C-RNTI what is used during RA
procedure only (as in a real network)
InitialGrantCE_ UplinkGrantCE_Mode_Typ
opt used by SS based on PRACH coverage enhancement levels
e
Mode
RarList_Type
TTCN-3 Record of Type
Name
RarList_Type
Comment
in general MAC PDU may contain one or several RARs;
normally only one RAR is contained
record of RandomAccessResponseParameters_Type
UplinkGrantCE_ModeA_Type
TTCN-3 Record Type
Name
UplinkGrantCE_ModeA_Type
Comment
TS 36.213, clause 6.2 table 6-2
Msg3_PUSCH
B4_Type
_NB_Index
Msg3_PUSCH
B4_Type
_ResAllocation
Msg3_PUSCH
B2_Type
_Repetitions
MCS
B3_Type
TPC_Comman
B3_Type
d
CSI_Req
B1_Type
UL_Delay
B1_Type
Msg3_4_MPD
B2_Type
CCH_NB_Inde
x
Msg3 PUSCH narrowband index
Msg3 PUSCH Resource allocation
Number of Repetitions for Msg3 PUSCH
TPC command for scheduled PUSCH
CSI request
UL delay
Msg3/4 MPDCCH narrowband index
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
296
ETSI TS 136 523-3 V13.2.0 (2017-03)
UplinkGrantCE_ModeB_Type
TTCN-3 Record Type
Name
UplinkGrantCE_ModeB_Type
Comment
TS 36.213, clause 6.2 table 6-2
Msg3_PUSCH
B2_Type
_NB_Index
Msg3_PUSCH
B3_Type
_ResAllocation
Msg3_PUSCH
B3_Type
_Repetitions
TBS
B2_Type
Msg3_4_MPD
B2_Type
CCH_NB_Inde
x
Msg3 PUSCH narrowband index
Msg3 PUSCH Resource allocation
Number of Repetitions for Msg3 PUSCH
TBS
Msg3/4 MPDCCH narrowband index
UplinkGrantCE_Mode_Type
TTCN-3 Record Type
Name
UplinkGrantCE_Mode_Type
Comment
CE_ModeA
UplinkGrantCE_ModeA_Ty
pe
CE_ModeB
UplinkGrantCE_ModeB_Ty
pe
If the most recent PRACH coverage enhancement level for the
UE is 0 or 1, the contents of the Random Access Response
Grant are interpreted according to CEModeA.
If the most recent PRACH coverage enhancement level for the
UE is 2 or 3, the contents of the Random Access Response
Grant are interpreted according to CEModeB
RandomAccessResponse_Type
TTCN-3 Union Type
Name
RandomAccessResponse_Type
Comment
None
Null_Type
List
RarList_Type
used for unsuccessful RA procedure
normally one RAR to be sent to the UE; in general there can be
more than one RAR
RandomAccessResponseCtrl_Type
TTCN-3 Record Type
Name
RandomAccessResponseCtrl_Type
Comment
configuration for Random Access Response mapped to DL-SCH mapped to PDSCH
TransmissionMode: single antenna mode when there is only one antenna configured, transmit
diversity else;
RNTI: RA-RNTI (TS 36.321, clause 7.1);
if both RAR msg and backoff indicator are 'None' SS shall not respond on random access preamble
DciInfo
DciDlInfoCommon_Type
DCI format: 1A or 1C (TS 36.213, clause 7.1)
ResourceAllocType: 2 (acc. to DCI format)
Modulation: QPSK
Frequency domain schedule: index of 1st RB; max. number of
RBs per TTI
Rar
RandomAccessResponse_
RAR to be sent to the UE
Type
BackoffInd
RandomAccessBackoffIndic
possible backoff indicator; 'None' for normal cases
ator_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
297
ETSI TS 136 523-3 V13.2.0 (2017-03)
RandomAccessResponseConfig_Type
TTCN-3 Union Type
Name
RandomAccessResponseConfig_Type
Comment
Ctrl
RandomAccessResponseCtrl_Ty
contains information to control sending of RAR
pe
Ctrl_CRC_Erro RandomAccessResponseCtrl_Ty
same as Ctrl (see above), but MAC PDU transmitted will contain
pe
r
CRC bits (0-3) being toggled;
no retransmissions shall be made as UE shall not send a NACK
None
Null_Type
to be used when there is no RAR to be sent at all
RachProcedure_Type
TTCN-3 Record Type
Name
RachProcedure_Type
Comment
RAResponse
RandomAccessResponseC
onfig_Type
ContentionRes
olutionCtrl
control of how the SS shall react on RA preamble;
this may be
- the RAP id as expected by the UE
- a RAP id not matching to the UE's RAP
- a backoff indicator
- nothing at all
ContentionResolutionCtrl_T
ype
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
298
ETSI TS 136 523-3 V13.2.0 (2017-03)
RachProcedureList_Type
TTCN-3 Record of Type
Name
RachProcedureList_Type
Comment
to simulate RACH procedure with one or more than one attempt by the UE:
There is one RachProcedure_Type in the list per PRACH Preamble attempt. When PRACH
preamble is repeated within a Preamble attempt (BL/CE UE), the SS shall wait for all PRACH
preamble repetitions before acting as per configured RAR.
The discrete set of RAPIDS to be used by UE in each CE level is provided in
RACH_ConfigCommon->RACH_CE_LevelInfoList_r13 and the repetitions of preamble based
on CE level is provided in PRACH_Config_v1310-> prach_ParametersListCE_r13. If UE is not
repeating preambles as per its detected CE level the SS shall raises an error.
The same applies to contention resolution, one per RACH procedure Msg 3 transmission plus
its repetitions.
1. Normal cases:
one single RandomAccessResponse is sent to the UE matching the UE's RACH preamble;
contention resolution is successful immediately
=> list contains only one element which is used for any RA procedure
(Even if a RACH procedure is repeated by the UE for any reason this element shall be used;
e.g. it needs not to be handled as error when the UE sends another RACH preamble instead
of the RRC connection request message)
2. Special cases:
there are upto tsc_RandomAccessResponseListSize preambles sent by the UE
=> there are upto tsc_RandomAccessResponseListSize responses to be configured as
elements of the list;
SS shall start with the first element in the list and use the RAR as specified in this element;
if the RAR matches at the UE side the UE will send UL data and contention resolution is
performed as configured for this element;
if the RAR does not match the UE sends another RAP and SS continues with the next element
in the list;
in this case the contention resolution of the respective element is not used;
if the end of the list is reached and further RACH preambles are sent by the UE SS shall
repeatively apply the last element of the list
(this is necessary because there might be not enough time to reconfigure SS after the end of the
list has been reached and there shall be well-defined behaviour after the list has been
processed);
to change from a special mode to normal mode the RachProcedureList is reconfigured by TTCN
to achieve transparency and readability of the code;
NOTE:
when there are RACH_ConfigDedicated configured (see below) and the RA preamble matches
with one the configured ones the contention resolution ctrl is obsolete (non contention based
random access procedure)
record length(1..tsc_RandomAccessResponseListSize) of RachProcedure_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
299
RachProcedureConfig_Type
TTCN-3 Record Type
Name
RachProcedureConfig_Type
Comment
parameters to control the random access procedure; TS 36.321, clause 5.1
RACH_ConfigC RACH_ConfigCommon_Ty
opt acc. TS 36.331, clause 6.3.2; may not be necessary for SS;
pe
ommon
omit: "keep as it is"
RACH_ConfigD RACH_ConfigDedicated_Ty opt acc. TS 36.331, clause 6.3.2;
pe
edicated
when random access preamble sent by the UE matches with the
configured one,
SS shall assume the random access procedure being noncontention based;
initial configuration: no RACH_ConfigDedicated are configured;
omit means "keep as it is"
RachProcedure RachProcedureList_Type
opt in normal cases there is one element which is used for any RA
List
procedure;
special cases are used in MAC test cases;
omit means "keep as it is"
If the cell is an Active Scell, the RACH procedure configuration in
the Active Scell controls
the RAR transmission in the associated Pcell, for received
PRACH preamble in Scell
D.1.3.6 System_Information_Control
Primitive to configuration BCCH/BCH
System_Information_Control: Basic Type Definitions
TTCN-3 Basic Types
BcchToPbchConfig_Type
Null_Type
place holder for BCCH mapped to BCH
mapped to PBCH:
MIB using fixed scheduling (periodicity: 40ms);
transmission mode:
single antenna port configuration (layer
mapping acc. TS 36.211, clause 6.3.3.1)
or transmit diversity (layer mapping acc. TS
36.211, clause 6.3.3.3) depending on antenna
configuration
Sib1Schedul_Type
TTCN-3 Record Type
Name
Sib1Schedul_Type
Comment
SIB1: fixed scheduling in time domain acc. TS 36.331, clause 5.2.1.2 (periodicity: 80ms; repetitions
every 20ms)
DciInfo
DciDlInfoCommon_Type
opt DCI format: 1A or 1C (TS 36.213, clause 7.1)
ResourceAllocType: 2 (acc. to DCI format)
Modulation: QPSK
Frequency domain schedule: index of 1st RB; max. number of
RBs per TTI
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
300
ETSI TS 136 523-3 V13.2.0 (2017-03)
SingleSiSchedul_Type
TTCN-3 Record Type
Name
SingleSiSchedul_Type
Comment
specifies scheduling for a single SI in freq and time domain
DciInfo
DciDlInfoCommon_Type
opt DCI format: 1A or 1C (TS 36.213, clause 7.1)
ResourceAllocType: 2 (acc. to DCI format)
Modulation: QPSK
Frequency domain schedule: index of 1st RB; max. number of
RBs per TTI
SubframeOffset integer
opt offset within the SI-window;
NOTE: SI-window may span more than one frame
SiSchedul_Type
TTCN-3 Record Type
Name
SiSchedul_Type
Comment
specifies for a specific SI scheduling and repetitions within as SI window
Periodicity
SiPeriodicity_Type
opt
Window
record of
opt NOTE:
SingleSiSchedul_Type
acc. to TS 36.331, clause 5.2.1.2 the same SI may occur more
than once in an SI-window;
to allow this there is a "record of" even though acc. to TS 36.508,
clause 4.4.3.3 all SIs are sent only once within the window
SiSchedulList_Type
TTCN-3 Record of Type
Name
SiSchedulList_Type
Comment
record length(1..maxSI_Message) of SiSchedul_Type
AllSiSchedul_Type
TTCN-3 Record Type
Name
AllSiSchedul_Type
Comment
WindowLength
SiWindowLength_Type
SiList
SiSchedulList_Type
SegmentedSiLi SiSchedulList_Type
st
opt
opt
opt
to calculate start of each SI window acc. TS 36.331, clause 5.2.3
list of scheduling info for the SIs containing one ore more SIBs
list of scheduling info for segmented SIs (e.g. SI containing
SIB11);
corresponds to SegmentedSIs in BcchInfo_Type: SS shall
subsequently schedule the elements of the corresponding
SegmentedSIs (BcchInfo_Type);
e.g. SegmentedSiList[i] provided scheduling info for
BcchInfo_Type's SegmentedSIs[i] and the kth element of
SegmentedSIs[i] is sent at
T0 + ((K * N) + k) * periodicity
with
K: number for segments
k = 0 .. K-1
N = 0, 1, 2, ...
T0, periodicity: scheduling info as given by SegmentedSiList[i]
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
301
ETSI TS 136 523-3 V13.2.0 (2017-03)
BcchToPdschConfig_Type
TTCN-3 Record Type
Name
BcchToPdschConfig_Type
Comment
configuration for BCCH mapped to DL-SCH mapped to PDSCH
TransmissionMode: single antenna mode when there is only one antenna configured, transmit
diversity else;
RNTI: SI-RNTI (TS 36.321, clause 7.1)
Sib1Schedul
Sib1Schedul_Type
opt scheduling of SIB1 in frequency domain
SiSchedul
AllSiSchedul_Type
opt scheduling of SIs in frequency and time domain
SI_List_Type
TTCN-3 Record of Type
Name
SI_List_Type
Comment
TS 36.331, clause 6.2.1 BCCH-DL-SCH-Message and clause 6.2.2 SystemInformation
record of BCCH_DL_SCH_Message
SegmentedSI_List_Type
TTCN-3 Record of Type
Name
SegmentedSI_List_Type
Comment
Each element is a list of segments;
used for SIB11/12 segmentation
record of SI_List_Type
BcchInfo_Type
TTCN-3 Record Type
Name
BcchInfo_Type
Comment
all fields are declared as optional to allow modification of single field;
acc. to TS 36.331, clause 9.1.1.1 "RRC will perform padding, if required due to the granularity of the
TF signalling, as defined in 8.5.";
therefore this needs to be done by the system simulator
MIB
BCCH_BCH_Message
opt TS 36.331, clause 6.2.1 BCCH-BCH-Message and clause 6.2.2
MasterInformationBlock;
NOTE:
the sequence number included in MIB needs to be handled and
maintained by the system simulator;
that means that the sequence number being setup by TTCN will
be overwritten by SS
SIB1
BCCH_DL_SCH_Message
opt TS 36.331, clause 6.2.1 BCCH-DL-SCH-Message and clause
6.2.2 SystemInformationBlockType1
SIs
SI_List_Type
opt list of SIs corresponding to SiList of AllSiSchedul_Type
(i.e. element i of AllSiSchedul_Type's SiList specifies the
scheduling for SIs[i])
SegmentedSIs
SegmentedSI_List_Type
opt list of SIs containing segmented SIBs;
corresponds to SegmentedSiList in AllSiSchedul_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
302
ETSI TS 136 523-3 V13.2.0 (2017-03)
BcchConfig_Type
TTCN-3 Record Type
Name
BcchConfig_Type
Comment
all fields are optional to allow single modifications;
activation time may be applied in the common part of the ASP;
NOTE 1:
acc. to TS 36.331, clause 9.1.1.1 there is no PDCP and RLC/MAC are in TM
NOTE 2:
mapping/scheduling and contents of the System Information in general is done in one go
(i.e. there are no separate ports for SIB data and configuration)
Pbch
BcchToPbchConfig_Type
opt
Pdsch
BcchToPdschConfig_Type
opt
BcchInfo
BcchInfo_Type
opt
StopSib1Trans
Null_Type
opt if omitted:
mission
SS transmits SIB1 last provided in BcchInfo and associated
DCI.
if set:
SS shall stop transmission of SIB1 and associated DCI.
To resume SIB1 transmission, this flag shall be omitted and SIB1
shall be provided in BcchInfo.
Bcch_BRConfig_Type
TTCN-3 Record Type
Name
Bcch_BRConfig_Type
Comment
all fields are optional to allow single modifications;
activation time may be applied in the common part of the ASP;
NOTE 1:
acc. to TS 36.331, clause 9.1.1.8 there is no PDCP and RLC/MAC are in TM
NOTE 2:
mapping/scheduling and contents of the System Information in general is done in one go
(i.e. there are no separate ports for SIB data and configuration)
Pbch
Bcch_BRToPbchConfig_Ty
opt
pe
Pdsch
Bcch_BRToPdschConfig_T
opt
ype
BcchInfo
Bcch_BRInfo_Type
opt
StopSib1Trans
Null_Type
opt if omitted:
mission
SS transmits SIB1 last provided in BcchInfo and associated
DCI.
if set:
SS shall stop transmission of SIB1 and associated DCI.
To resume SIB1 transmission, this flag shall be omitted and SIB1
shall be provided in BcchInfo.
Bcch_BRToPbchConfig_Type
TTCN-3 Record Type
Name
Bcch_BRToPbchConfig_Type
Comment
BCCH_BL mapped to BCH mapped to PBCH:
MIB using fixed scheduling (periodicity: 40ms);
transmission mode:
single antenna port configuration (layer mapping acc. TS 36.211, clause 6.3.3.1)
or transmit diversity (layer mapping acc. TS 36.211, clause 6.3.3.3) depending on antenna
configuration
EnableMIB_Re boolean
If true MIB transmission shall be repeated in subframe#9 of the
petition
previous radio frame for FDD and subframe #5 of the same radio
frame for TDD
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
303
ETSI TS 136 523-3 V13.2.0 (2017-03)
SI_SubframeOffsetList_Type
TTCN-3 Record of Type
Name
SI_SubframeOffsetList_Type
Comment
record of integer
Bcch_BRToPdschConfig_Type
TTCN-3 Record Type
Name
Bcch_BRToPdschConfig_Type
Comment
Configuration for BCCH_BR mapped to DL-SCH mapped to PDSCH
TransmissionMode: single antenna mode when there is only one antenna configured, transmit
diversity else;
RNTI: No RNTI as BR SIs are sent without DCI info and scheduling for SIB-1 is provided in MIB and
for other SIBs in SIB 1
Sib1_BRSched Sib1_BRSchedul_Type
opt scheduling of SIB1 in frequency & time domain
ul
SiSchedul
BandwidthReducedAccess
opt scheduling of SIs in frequency and time domain. SS shall ignore
RelatedInfo_Type
si-ValidityTime-r13 and systemInfoValueTagList-r13 and TTCN
shall omit them
SubframeOffset SI_SubframeOffsetList_Typ opt offset within the SI-window;
e
List
NOTE: SI-window may span more than one frame. There shall
be 1 to 1 mapping with
BandwidthReducedAccessRelatedInfo_Type.schedulingInfoList_
BR_r13 elements
Sib1_BRSchedul_Type
TTCN-3 Record Type
Name
Sib1_BRSchedul_Type
Comment
SIB1: fixed scheduling in time domain acc. TS 36.331, clause 5.2.1.2 (periodicity: 80ms)
For a BL/CE UE, the resource allocation for PDSCH carrying SystemInformationBlockType1-BR and
SI messages is a set of six contiguously allocated localized virtual resource blocks within a
narrowband . the Narrow band index used for a transmission is as per 36.211 clause 6.4.1
SchedulingInfo
SchedulingInfoSIB1_BR_r1
TBS for SystemInformationBlockType1-BR and the repetitions
SIB1_BR_r13
3_Type
made within 80ms as indicated in MIB
BR_SI_List_Type
TTCN-3 Record of Type
Name
BR_SI_List_Type
Comment
TS 36.331, clause 6.2.1 BCCH-DL-SCH-Message-BR and clause 6.2.2 SystemInformation
record of BCCH_DL_SCH_Message_BR
BR_SegmentedSI_List_Type
TTCN-3 Record of Type
Name
BR_SegmentedSI_List_Type
Comment
Each element is a list of segments;
used for SIB11/12 segmentation
record of BR_SI_List_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
304
ETSI TS 136 523-3 V13.2.0 (2017-03)
Bcch_BRInfo_Type
TTCN-3 Record Type
Name
Bcch_BRInfo_Type
Comment
all fields are declared as optional to allow modification of single field;
acc. to TS 36.331, clause 9.1.1.1 "RRC will perform padding, if required due to the granularity of the
TF signalling, as defined in 8.5.";
therefore this needs to be done by the system simulator
MIB
BCCH_BCH_Message
opt The MIB shall not be present if transmission of MIB is configured
by BcchInfo_Type.
TS 36.331, clause 6.2.1 BCCH-BCH-Message and clause 6.2.2
MasterInformationBlock;
NOTE:
the sequence number included in MIB needs to be handled and
maintained by the system simulator;
that means that the sequence number being setup by TTCN will
be overwritten by SS
SIB1
BCCH_DL_SCH_Message
opt TS 36.331, clause 6.2.1 BCCH-DL-SCH-Message-BR and
_BR
clause 6.2.2 SystemInformationBlockType1
SIs
BR_SI_List_Type
opt list of SIs corresponding to SiList of AllSiSchedul_Type
(i.e. element i of AllSiSchedul_Type's SiList specifies the
scheduling for SIs[i])
SegmentedSIs
BR_SegmentedSI_List_Typ opt list of SIs containing segmented SIBs;
e
corresponds to SegmentedSiList in AllSiSchedul_Type
D.1.3.7 Paging_Control
Primitive to configuration PCCH/PCH
PcchConfig_Type
TTCN-3 Record Type
Name
PcchConfig_Type
Comment
configuration for PCCH mapped to PCH mapped to PDSCH
TransmissionMode: single antenna mode when there is only one antenna configured, transmit
diversity else;
RNTI: P-RNTI (TS 36.321, clause 7.1)
NOTE: acc. to TS 36.331, clause 9.1.1.3 there is no PDCP and RLC/MAC are in TM
DciInfo
DciDlInfoCommon_Type
opt DCI format: 1A or 1C (TS 36.213, clause 7.1)
ResourceAllocType: 2 (acc. to DCI format)
Modulation: QPSK
Frequency domain schedule: index of 1st RB; max. number of
RBs per TTI
PCCH_Config_ PCCH_Config_v1310
opt provides MPDCCH repetition for PCCH etc
v13
D.1.3.8 UE_Specific_Channel_Configuration
D.1.3.8.1
UE_Specific_Channel_Configuration_DL
Scheduling and other information for CCCH/DCCH/DTCH mapped to DL-SCH mapped to PDSCH
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
305
ETSI TS 136 523-3 V13.2.0 (2017-03)
HarqProcessConfigDL_Type
TTCN-3 Union Type
Name
HarqProcessConfigDL_Type
Comment
HARQ processes to be used automatically for DL assignments
AllProcesses
Null_Type
all HARQ processes shall be used for automatic assignmnet; this
is the normal case
SpecificSubset
HarqProcessList_Type
only the HARQ processes of this list shall be used automatically,
other processes are excluded from automatic assignments;
nevertheless all HARQ processes may be addressed explicitly by
DRB_DataPerSubframe_DL_Type.HarqProcess
CcchDcchDtchConfigDL_Type
TTCN-3 Record Type
Name
CcchDcchDtchConfigDL_Type
Comment
configuration for CCCH/DCCH/DTCH mapped to DL-SCH mapped to PDSCH
TransmissionMode: as signalled to the UE (AntennaInfoDedicated in RRCConnectionSetup);
RNTI: C-RNTI (TS 36.321, clause 7.1);
all fields optional (omit = "keep as it is") since DCI format and modulation may be changed during a
test;
for initial configuration all fields are mandatory
DciInfo
DciDlInfo_Type
opt DCI format: 1A per default since for CCCH mimo cannot be
applied in general
ResourceAllocType: (depending on DCI format)
Modulation: QPSK for signalling
Frequency domain schedule: index of 1st RB; max. number of
RBs per TTI;
in case of spatial multiplexing if there are 2 code words
FreqDomainSchedul shall be applied to both
AntennaInfo
AntennaInfoDedicated_Typ
opt as signalled to the UE (TS 36.331, clause 6.3.2):
e
transmissionMode, codebookSubsetRestriction
HarqProcessC
HarqProcessConfigDL_Typ
opt HARQ processes automatically used by the SS in DL
e
onfig
D.1.3.8.2
UE_Specific_Channel_Configuration_UL
Scheduling information for CCCH/DCCH/DTCH mapped to UL-SCH mapped to PUSCH
PucchHoppingBits_Type
TTCN-3 Union Type
Name
PucchHoppingBits_Type
Comment
Number of hopping bits acc. to TS 36.213 table 8.4-2
OneBit
B1_Type
N(UL, RB) = 6..49 i.e. default system bandwid this less than 10
MHz (does not include 10 MHz)
TwoBits
B2_Type
N(UL, RB) = 50..110 i.e. default system bandwidth is 10 MHz or
above
UplinkHoppingResourceParameters_Type
TTCN-3 Record Type
Name
UplinkHoppingResourceParameters_Type
Comment
PucchHopping
PucchHoppingBits_Type
to control hopping resource allocation as signalled in DCI format
0 (TS 36.212, clause 5.3.3.1.1)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
306
ETSI TS 136 523-3 V13.2.0 (2017-03)
UplinkHoppingControl_Type
TTCN-3 Union Type
Name
UplinkHoppingControl_Type
Comment
shall be considered by SS to fill in the information needed for DCI format 0 (TS 36.213, clause 7.1)
Deactivated
Null_Type
Activated
UplinkHoppingResourceParamete
rs_Type
CcchDcchDtchConfigUL_Type
TTCN-3 Record Type
Name
CcchDcchDtchConfigUL_Type
Comment
scheduling for CCCH/DCCH/DTCH mapped to UL-SCH mapped to PUSCH
NOTE 1:
for definition of the possible UL grants the location of the PUCCH (TS 36.211, clause 5.4.3)
and the PRACH (TS 36.211, clause 5.7.3) need to be taken into account;
NOTE 2:
In contrast to the DL where the scheduling can be done (with consideration of some restrictions) by
SS on a per need basis in the UL the scheduling depends on information provided by the UE: e.g.
BSR (buffer status report), SR (scheduling request)
see TS 36.523-3 clause 7.2 for further information.
DciInfo
DciUlInfo_Type
opt DCI format: 0 (TS 36.213, clause 7.1)
ResourceAllocType: 2 (acc. to DCI format)
Modulation: QPSK per default
Frequency domain schedule: index of 1st RB; max. number of
RBs per TTI
(upper bound up to which SS may assign grants to the UE)
Hopping
UplinkHoppingControl_Typ
opt when Hopping = 'Activated' SS shall set hopping flag in DCI
e
format 0
PUCCH_Synch UplinkTimeAlignment_Sync opt parameters to control automatic control of timing advance
h_Type
UL_GrantConfi
UL_GrantConfig_Type
opt UL grant allocation to be applied
g
UE_Specific_Channel_Configuration: Basic Type Definitions
TTCN-3 Basic Types
N_PSCCH_Type
Itrp_Type
B6_Type
integer (0..127)
DrxCtrl_Type
TTCN-3 Union Type
Name
DrxCtrl_Type
Comment
DRX configuration for connected mode (TS 36.321, clause 5.7)
None
Null_Type
DRX not configured
Config
DRX_Config_Type
DRX is configured as signalled to the UE;
NOTE: the release branch of DRX-Config in general is not used
for configuration of the SS
MeasGapCtrl_Type
TTCN-3 Union Type
Name
MeasGapCtrl_Type
Comment
support of measurement gap configuration
None
Null_Type
no measurement gap configuration
Config
MeasGapConfig_Type
measurement gap configuration acc. to TS 36.331, clause 6.3.5
and gap pattern acc. TS 36.133 Table 8.1.2.1-1;
NOTE: the release branch of MeasGapConfig in general is not
used for configuration of the SS
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
307
ETSI TS 136 523-3 V13.2.0 (2017-03)
CcchDcchDtchConfig_Type
TTCN-3 Record Type
Name
CcchDcchDtchConfig_Type
Comment
MeasGapCtrl
MeasGapCtrl_Type
opt
DL
opt
DrxCtrl
CcchDcchDtchConfigDL_Ty
pe
CcchDcchDtchConfigUL_Ty
pe
DrxCtrl_Type
TtiBundling
CifPresence
TTI_BundlingConfig_Type
boolean
opt
opt
UL
opt
opt
to tell the SS when no assignments/grants shall be assigned to
the UE
Scheduling, parameters related to CCCH, DCCH and DTCH in
DL
Scheduling, parameters related to CCCH, DCCH and DTCH in
UL
DRX configuration as sent to the UE (or 'None' when the UE
does not support connected mode DRX)
TTI bundling as configured at the UE
corresponds to PhysicalConfigDedicated.cif_Presence_r10:
The CIF field is applied for dedicated search space scheduling
i.e. DCCH/DTCH.
Not present for common search space scheduling.
CIF indicator as true may be configured even in non CA cell, to
facilitate the future
false: no serving cell is cross scheduled by this cell
true: carrier indicator field is present when the PDCCH CRC is
scrambled by C-RNTI or SPS C-RNTI
omit means "keep as it is"
SciSchedulingConfig_Type
TTCN-3 Record Type
Name
SciSchedulingConfig_Type
Comment
Scheduling for STCH mapped to SL-SCH mapped to PSSCH
DPCCH DCI format 5 (TS 36.213, clause 14.2)
UL grant allocation to be applied: On SL-BSR Reception
For the time being there is no requirement to configure the SS with TPC-PDCCH-Config;
In general SS is required to keep the UE's UL power constant
SL_RNTI_r12
C_RNTI
opt
N_PSCCH
N_PSCCH_Type
opt Resource for PSCCH - 6 bits
SL_Sheduling
SL_SciConfig_Type
opt SCI format 0 configuration
SL_SciConfig_Type
TTCN-3 Record Type
Name
SL_SciConfig_Type
Comment
SCI format 0 (TS 36.213 clause 14.2 TS 36.212 clause 5.3.3.1.9)
ResourceAllocType: 0 (36.213 cl 14.1.1.2.1 and 8.1.1)
Frequency domain schedule: index of 1st RB; max. number of RBs per TTI
(upper bound up to which SS may assign grants to the UE)
Hopping
UplinkHoppingControl_Typ
Frequency hopping flag - bit
e
FreqDomainSc
FreqDomainSchedulExplicit
Resource block assignment
_Type
hedul
Itrp
Itrp_Type
Time resource pattern of 14.1.1.1.1 of TS 36.213
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
308
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.1.3.9 Carrier_Aggregation
ActivateScell_Type
TTCN-3 Record Type
Name
ActivateScell_Type
Comment
ScellActivation
ScellBitMap_Type
SendMCE
36.321 clause 6.1.3.8; B0=C7, B1=C6 .. B6=C1, B7 is reserved.
B0 to B6, 1 means Activate associated Scell
If true the SS sends a MAC Control Element to the UE
boolean
Scell_Capability_Type
TTCN-3 Enumerated Type
Name
Scell_Capability_Type
Comment
DlOnly
the CC is configured in DL only, no aggregation in this cell in UL
UL_DL
the aggregation is configured in both UL and DL
ScellDeactivationTimer_Type
TTCN-3 Union Type
Name
ScellDeactivationTimer_Type
Comment
NOTE: this type is a union to allow semantic of "keep as it is" for optional fields of this type
NumberOfRadi
MAC_MainConfig_ScellDeactivati SCell deactivation timer acc. to TS 36.321
oFrames
onTimer_Type
Infinity
Null_Type
infinity as when 'sCellDeactivationTimer' is omitted in 'MACMainConfig' sent to the UE
SCellIndexList_List
TTCN-3 Record of Type
Name
SCellIndexList_List
Comment
record length (1..7) of SCellIndex_r10
CrossCarrierScheduledCellsList_Type
TTCN-3 Union Type
Name
CrossCarrierScheduledCellsList_Type
Comment
None
Null_Type
No Cells Cross Scheduled by this Cell; CIF can still be true.
CrossSchedule SCellIndexList_List
List of Scells Scheduled by this Scell; CIF field shall be true;
dCells
Pcell cannot be cross scheduled
SchedulingCarrierConfig_Type
TTCN-3 Union Type
Name
SchedulingCarrierConfig_Type
Comment
Own
CrossCarrierScheduledCellsList_
Type
CrossSchedule CrossSchedulingCarrierInfo_Type
d
Cell is scheduled by itself and possible cross schedules other
Scells
Cell is cross Scheduled by other carrier; the CIF field shall be
configured in the serving cell scheduling this scell
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
309
ETSI TS 136 523-3 V13.2.0 (2017-03)
CrossCarrierSchedulingConfig_Type
TTCN-3 Union Type
Name
CrossCarrierSchedulingConfig_Type
Comment
Config
SchedulingCarrierConfig_Type
When cross carrier scheduling is enabled then the CIF field shall
be configured in the serving cell scheduling this scell
None
Null_Type
PrimaryCellInfo_Type
TTCN-3 Record Type
Name
PrimaryCellInfo_Type
Comment
AssociatedScel EUTRA_CellIdList_Type
lList
MeasSubframe MeasSubframePatternPCell
PatternPCell
_r10
CrossCarrierSc CrossCarrierScheduledCell
heduledCellsLi
sList_Type
st
List of Scells associated with the Pcell/PScells (needs to be
consistent with AssociatedPcellId in Scell/PScell )
opt
opt
Information of possible Cells Cross Scheduled by this cell
Pcell_Mode_Type
TTCN-3 Union Type
Name
Pcell_Mode_Type
Comment
FDD
Null_Type
TDD
TDD_SubframeAssignment_Type
SecondaryCellInfo_Type
TTCN-3 Record Type
Name
SecondaryCellInfo_Type
Comment
AssociatedPcel EUTRA_CellId_Type
lId
SCellIndex
SCellIndex_r10
Scell_Capabilit
Scell_Capability_Type
y
ScellDeactivati
ScellDeactivationTimer_Typ
onTimer
e
cell ID of associated Pcell/PSCell (eutra_Cell_NonSpecific is not
allowed)
opt
if DL only or both UL and DL (omit means "keep as it is")
opt
SCell deactivation timer; omit means "keep as it is";
when there is more than one SCell associated to the same PCell
this field shall be set to the same value for each SCell
omit means "keep as it is"
CrossCarrierSc
hedulingConfig
STAG_Id
CrossCarrierSchedulingCon
fig_Type
STAG_Id_r11
opt
Pcell_Mode
Pcell_Mode_Type
opt
opt
if IE is never configured then scell is part of PTAG.
Uses the STAG_ID or PTAG in Auto PUCCH synchronization
when transmitting periodically Timing Advance MCE
omit means Pcell/PScell and Scell mode are same. To be
provide for FDD-TDD mixed mode CA/Dual connectivity
configurations
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
310
ETSI TS 136 523-3 V13.2.0 (2017-03)
ServingCellConfig_Type
TTCN-3 Union Type
Name
ServingCellConfig_Type
Comment
PCell
PrimaryCellInfo_Type
SCell
SecondaryCellInfo_Type
PSCell
PSCellInfo_Type
Release
Null_Type
cell shall become PCell
cell shall become SCell
cell shall become PSCell
cell is changed back to normal non CA cell
PSCellInfo_Type
TTCN-3 Record Type
Name
PSCellInfo_Type
Comment
AssociatedPcel EUTRA_CellId_Type
lId
SCellIndex
SCellIndex_r10
AssociatedScel EUTRA_CellIdList_Type
lList
CrossCarrierSc CrossCarrierSchedulingCon
fig_Type
hedulingConfig
Pcell_Mode
Pcell_Mode_Type
cell ID of associated Pcell (eutra_Cell_NonSpecific is not
allowed)
opt
opt
List of Scells associated with the PScell (needs to be consistent
with AssociatedPcellId in Scell)
omit means "keep as it is"
omit means PCell and PSCell mode are same. To be provide for
FDD-TDD mixed mode Dual connectivity configurations
D.1.3.10 OCNG_Config
OCNG_Config_Type
TTCN-3 Union Type
Name
OCNG_Config_Type
Comment
Activate
OCNG_ActivateInfo_Type
Deactivate
Null_Type
CellId : identifier of the cell where the OCNG needs to be
activated
RoutingInfo : None
TimingInfo : activation time from when the SS starts transmission
of uncorrelated pseudo random MAC TB's addressed to Virtual
UE's in non ABS subframes.
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
CellId : identifier of the cell where the OCNG needs to be
deactivated
RoutingInfo : None
TimingInfo : activation time from when the SS stops transmission
of MAC TB's addressed to Virtual UE's in non ABS subframes.
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
OCNG_ActivateInfo_Type
TTCN-3 Record Type
Name
OCNG_ActivateInfo_Type
Comment
OFDMA Channel Noise Generator (OCNG):
SS for transmitting uncorrelated pseudo random data in MAC TB's addressed to Virtual UE's, will not
do any retransmissions due to no HARQ ACK/NACK reception being considered as NACK.
MeasSubFram
MeasSubframePattern_r10
provides the bit string for x (size of bit string divided by 10 )
ePattern
frames to be repeated continuously from provided timing info;
1 represents ABS subframe hence no pseudo random MAC TB
is scheduled
0 represent non-ABS subframe and SS automatically transmits
MAC TB's consisting of pseudo random data in each non-ABS
subframe
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
311
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.1.3.11 EIMTA_Config
EIMTA_Config_Type
TTCN-3 Record Type
Name
EIMTA_Config_Type
Comment
EIMTA_MainC
EIMTA_MainConfig_r12
onfig_r12
EIMTA_MainC
onfigServCell_r
12
EIMTA_MainConfigServCell
_r12
The IE EIMTA-MainConfig is used to specify the eIMTA-RNTI
used for eIMTA and the subframes used for PDCCH monitoring
by the UE with eIMTA-RNTI
The IE EIMTA-MainConfigServCell is used to specify the eIMTA
related parameters applicable for the cell
PeriodicTransmission_Type
TTCN-3 Record Type
Name
PeriodicTransmission_Type
Comment
Period
integer (1..infinity)
NumRepetition
s
TransmissionRepetition_Ty
pe
DCI 1C transmission period (TTI=1ms);
the starting time, Period and NumRepetitions need to
be chosen in TTCN so that the DCI 1C transmissions are
assigned at valid subframes according to
EIMTA_MainConfig_r12 settings; otherwise SS shall
raise an error
number of DCI 1C repetitions to be automatically transmitted or
'Continuous'
PDCCH_TDD_ConfigOrder_Type
TTCN-3 Union Type
Name
PDCCH_TDD_ConfigOrder_Type
Comment
OnlyOnce
Null_Type
DCI 1C is sent out on PDCCH with CRC scrambled by eIMTARNTI only once; no period
Periodic
PeriodicTransmission_Type
SS transmits DCI 1C periodically as configured by
EIMTA_MainConfig_Type
None
Null_Type
stop DCI 1C transmission
D.1.4
Cell_Power_Attenuation
CellAttenuationConfig_Type
TTCN-3 Record Type
Name
CellAttenuationConfig_Type
Comment
CellId
EUTRA_CellId_Type
Attenuation
Attenuation_Type
TimingInfo
TimingInfo_Type
opt
CellAttenuationList_Type
TTCN-3 Record of Type
Name
CellAttenuationList_Type
Comment
record length(1..tsc_EUTRA_MaxNumberOfCells) of CellAttenuationConfig_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.1.5
312
ETSI TS 136 523-3 V13.2.0 (2017-03)
Radio_Bearer_Configuration
Radio Bearer Configuration: SRBs/DRBs
D.1.5.1 PDCP_Configuration
PDCP_SNLength_Type
TTCN-3 Enumerated Type
Name
PDCP_SNLength_Type
Comment
PDCP Sequence Number
PDCP_SNLength5
TS 36.323 clause 6.2.2
PDCP_SNLength7
TS 36.323 clause 6.2.3
PDCP_SNLength12
TS 36.323 clause 6.2.4
PDCP_SNLength16
TS 36.323 clause 6.2.10
PDCP_ROHC_Mode_Type
TTCN-3 Record Type
Name
PDCP_ROHC_Mode_Type
Comment
SN_Size
PDCP_SNLength_Type
PDCP_NonROHC_Mode_Type
TTCN-3 Record Type
Name
PDCP_NonROHC_Mode_Type
Comment
SN_Size
PDCP_SNLength_Type
PDCP_TestModeInfo_Type
TTCN-3 Union Type
Name
PDCP_TestModeInfo_Type
Comment
PDCP_ROHC_ PDCP_ROHC_Mode_Type
Mode
PDCP_NonRO
HC_Mode
PDCP_NonROHC_Mode_Type
ROHC test mode acc. to TS 36.523-3, clause 4.2.1.3.1;
requires PDCP to be configured for this RB =>
- SS applies ciphering in UL and DL
- SS maintains PDCP sequence numbers and state variables
Furthermore in this mode
- SS does not add/remove PDCP headers
(in UL the PDCP PDUs are decoded depending on SN_Size)
- SS applies ROHC in DL only
PDCP test mode acc. to TS 36.523-3, clause 4.2.1.3.2 (nonROCH test mode);
requires PDCP to be configured as transparent =>
- SS does not apply ciphering in UL and DL
- SS does not interpret, insert or remove PDCP headers
(in UL PDCP PDUs are decoded depending on SN_Size)
- SS does not maintain PDCP sequence numbers and state
variables
PDCP_TestModeConfig_Type
TTCN-3 Union Type
Name
PDCP_TestModeConfig_Type
Comment
None
Null_Type
Info
PDCP_TestModeInfo_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
313
PDCP_RbConfig_Type
TTCN-3 Union Type
Name
PDCP_RbConfig_Type
Comment
Srb
Null_Type
Drb
PDCP_Config_Type
Transparent
Null_Type
for SRB1/2 there are no PDCP_Parameters;
SN is always 5 bits
PDCP-Configuration acc. to TS 36.331, clause 6.3.2;
among others for UM here pdcp-SN-Size is configured to be
either len7bits or len12bits;
for AM it always is 12bit
used for PDCP tests (TS 36.523-3, clause 4.2.1.3.2):
the SS does not apply ciphering and does not maintain
PDCP sequence numbers and state variables;
in UL the PDCP PDUs are decoded acc. to the TestMode;
Note: a reconfiguration of a RB from transparent mode to
'normal' mode is not foreseen
(i.e. there is no mechanism to restore Ciphering,
PDCP sequence numbers and state variables at the SS)
PDCP_ConfigInfo_Type
TTCN-3 Record Type
Name
PDCP_ConfigInfo_Type
Comment
Rb
PDCP_RbConfig_Type
TestMode
PDCP_TestModeConfig_Ty
pe
opt
opt
mandatory for initial configuration; omit means "keep as it is"
mandatory for initial configuration; omit means "keep as it is"
PDCP_Configuration_Type
TTCN-3 Union Type
Name
PDCP_Configuration_Type
Comment
None
Null_Type
Config
for SRB0 no PDCP is configured; furthermore the PDCP may not
be configured e.g. for DRBs tested in MAC test cases
PDCP_ConfigInfo_Type
D.1.5.2 RLC_Configuration
RLC configuration: radio bearer specific
RLC_Configuration: Basic Type Definitions
TTCN-3 Basic Types
RLC_AM_SequenceNumb
er_Type
SS_RLC_TM_Type
integer (0..1023)
RLC AM sequence number
Null_Type
TM to configure SRB0; no parameters to be
defined
RLC_ACK_Prohibit_Type
TTCN-3 Enumerated Type
Name
RLC_ACK_Prohibit_Type
Comment
Prohibit
cause SS RLC layer to stop any ACK transmission for UL PDU's received from UE
Continue
bring back the SS RLC in normal mode, where ACK/NACK are transmitted at polling
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
314
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC_NotACK_NextRLC_PDU_Type
TTCN-3 Enumerated Type
Name
RLC_NotACK_NextRLC_PDU_Type
Comment
Start
cause SS RLC layer not to ACK the next received RLC PDU;
this is done regardless of whether the poll bit is set or not;
Example [from UMTS]:
when the UE gets new security information in a SECURITY MODE COMMAND
the response (SECURITY MODE COMPLETE) sent by the UE is not acknowledged at the RLC
level;
this causes the UE to continue using the "old" security information
RLC_TestModeInfo_Type
TTCN-3 Union Type
Name
RLC_TestModeInfo_Type
Comment
AckProhibit
RLC_ACK_Prohibit_Type
NotACK_NextR RLC_NotACK_NextRLC_PDU_Ty
pe
LC_PDU
ModifyVTS
RLC_AM_SequenceNumber_Typ
e
TransparentMo
de_UMDwith5B
itSN
TransparentMo
de_UMDwith10
BitSN
TransparentMo
de_AMD
Null_Type
Null_Type
Null_Type
valid only when the RLC is configured in AM
valid only when the RLC is configured in AM
to modify the VT(S) at SS: VT(S) at the SS side is set to this
(absolute) value;
valid only when the RLC is configured in AM
shall be set when TTCN expects RLC PDUs as UMD in UL with
an SN of 5 bits;
valid only when the RLC is configured in TM
shall be set when TTCN expects RLC PDUs as UMD in UL with
an SN of 10 bits;
valid only when the RLC is configured in TM
shall be set when TTCN expects RLC PDUs as AMD in UL;
valid only when the RLC is configured in TM
RLC_TestModeConfig_Type
TTCN-3 Union Type
Name
RLC_TestModeConfig_Type
Comment
None
Null_Type
Info
RLC_TestModeInfo_Type
SS_RLC_AM_Type
TTCN-3 Record Type
Name
SS_RLC_AM_Type
Comment
Tx
UL_AM_RLC_Type
Rx
DL_AM_RLC_Type
ExtendedLI
RLC_Config_v1250
opt
opt
opt
the UE's UL setting to be used in SS's tx direction
the UE's DL setting to be used in SS's rx direction
Indicates the RLC LI field size. Value TRUE means that 15 bit LI
length shall be used,
otherwise 11 bit LI length shall be used
SS_RLC_UM_Bi_Directional_Type
TTCN-3 Record Type
Name
SS_RLC_UM_Bi_Directional_Type
Comment
Tx
UL_UM_RLC_Type
opt the UE's UL setting to be used in SS's tx direction
Rx
DL_UM_RLC_Type
opt the UE's DL setting to be used in SS's rx direction
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
315
ETSI TS 136 523-3 V13.2.0 (2017-03)
SS_RLC_UM_Uni_Directional_UL_Type
TTCN-3 Record Type
Name
SS_RLC_UM_Uni_Directional_UL_Type
Comment
Rx
DL_UM_RLC_Type
opt the UE's DL setting to be used in SS's rx direction
SS_RLC_UM_Uni_Directional_DL_Type
TTCN-3 Record Type
Name
SS_RLC_UM_Uni_Directional_DL_Type
Comment
Tx
UL_UM_RLC_Type
opt the UE's UL setting to be used in SS's tx direction
RLC_RbConfig_Type
TTCN-3 Union Type
Name
RLC_RbConfig_Type
Comment
AM
SS_RLC_AM_Type
UM
SS_RLC_UM_Bi_Directional_Typ
e
UM_OnlyUL
SS_RLC_UM_Uni_Directional_UL
_Type
UM_OnlyDL
SS_RLC_UM_Uni_Directional_DL
_Type
TM
SS_RLC_TM_Type
normally SRB0 only; may be used for test purposes also
RLC_Configuration_Type
TTCN-3 Record Type
Name
RLC_Configuration_Type
Comment
Rb
RLC_RbConfig_Type
TestMode
RLC_TestModeConfig_Typ
e
opt
opt
mandatory for initial configuration; omit means "keep as it is"
mandatory for initial configuration; omit means "keep as it is"
D.1.5.3 MAC_Configuration
MAC configuration: radio bearer specific configuration
EUTRA_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_MaxHarqRetran
smission
integer
28
maximum value for maxHARQMsg3Tx as being signalled to the
UE
MAC_Test_DLLogChID_Type
TTCN-3 Union Type
Name
MAC_Test_DLLogChID_Type
Comment
LogChId
TestLogicalChannelId_Type
ConfigLchId
Null_Type
Specifies to over write the logical channel ID in MAC header in all
the DL messages sent on the configured logical channel
Specifies that the normal mode of correct logical channel ID to be
used in DL MAc header.
This will be the default mode, when SS is initially configured.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
316
ETSI TS 136 523-3 V13.2.0 (2017-03)
MAC_Test_DL_SCH_CRC_Mode_Type
TTCN-3 Enumerated Type
Name
MAC_Test_DL_SCH_CRC_Mode_Type
Comment
Normal
default mode, the CRC generation is correct
Erroneous
SS shall generate CRC error by toggling CRC bits;
the CRC error shall be applied for all PDUs of the given RNTI and their retransmission until SS
is configured back to 'normal' operation
Error1AndNormal
the SS generates wrong CRC for first transmission and correct CRC on first retransmission.
Later SS operates in normal mode. The retransmission is automatically triggered by reception of
HARQ NACK
MAC_Test_SCH_NoHeaderManipulation_Type
TTCN-3 Enumerated Type
Name
MAC_Test_SCH_NoHeaderManipulation_Type
Comment
NormalMode
MAC header is fully controlled by the SS
DL_SCH_Only
TTCN can submit a final MAC PDU including header and payloads;
SS does not do anything with this MAC PDU i.e. no header is added for the DL SCH transport
channel.
It is possible that data belonging to multiple DRBs is sent in one MAC PDU and from one
special RB configured.
NOTE: SRBs shall work as in normal mode and data can be sent/received on SRBs but sending
on SRBs shall be in different TTIs than sending data PDUs.
DL_UL_SCH
In UL and DL the SS' MAC layer is transparent i.e. SS does not add or remove any MAC header
HARQ_ModeList_Type
TTCN-3 Record of Type
Name
HARQ_ModeList_Type
Comment
record length (1..tsc_MaxHarqRetransmission) of HARQ_Type
PhichTestMode_Type
TTCN-3 Union Type
Name
PhichTestMode_Type
Comment
NormalMode
Null_Type
ExplicitMode
HARQ_ModeList_Type
PHICH is configured to operate in normal mode
the number of elements in explicit list shall match the number of
retransmissions being expected
MAC_TestModeInfo_Type
TTCN-3 Record Type
Name
MAC_TestModeInfo_Type
Comment
Parameters/Configuration for MAC tests
DiffLogChId
MAC_Test_DLLogChID_Ty
to be used in test cases 7.1.1.1 and 7.1.1.2 for using a different
pe
logical channel ID in MAC-header on DL-SCH channel
No_HeaderMa
MAC_Test_SCH_NoHeade
to configure mode for no header manipulation in SS MAC layer
rManipulation_Type
nipulation
for DL/UL SCH
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
317
MAC_TestModeConfig_Type
TTCN-3 Union Type
Name
MAC_TestModeConfig_Type
Comment
None
Null_Type
Info
MAC_TestModeInfo_Type
MAC_LogicalChannelConfig_Type
TTCN-3 Record Type
Name
MAC_LogicalChannelConfig_Type
Comment
Priority
integer
logical channel priority for the DL as described in TS 36.321,
clause 5.4.3.1 for the UL
PrioritizedBitRa PrioritizedBitRate_Type
PBR as described for the UL; probably not needed at SS
te
MAC_Configuration_Type
TTCN-3 Record Type
Name
MAC_Configuration_Type
Comment
LogicalChannel MAC_LogicalChannelConfi
g_Type
TestMode
MAC_TestModeConfig_Typ
e
opt
mandatory for initial configuration; omit means "keep as it is"
opt
mandatory for initial configuration; omit means "keep as it is";
for none MAC tests "TestMode.None:=true"
Radio_Bearer_Configuration: Basic Type Definitions
TTCN-3 Basic Types
TestLogicalChannelId_Ty
pe
integer (0..31)
To be used in MAC test mode for reserved
values of Logical channels;
RadioBearerConfigInfo_Type
TTCN-3 Record Type
Name
RadioBearerConfigInfo_Type
Comment
semantics of omit: "keep as it is"
Pdcp
PDCP_Configuration_Type
opt
Rlc
LogicalChannel
Id
RLC_Configuration_Type
LogicalChannelId_Type
opt
opt
Mac
DiscardULData
MAC_Configuration_Type
boolean
opt
opt
for SRB0: "Pdcp.None:=true"
mandatory for initial configuration; omit means "keep as it is"
mandatory for initial configuration; omit means "keep as it is"
DRBs: DTCH-LogicalChannelIdentity as for rb-MappingInfo in
DRB-ToAddModifyList;
SRBs: for SRBs specified configurations acc. to TS 36.331,
clause 9.1.2 shall be applied:
SRB1: ul-LogicalChannel-Identity = dl-LogicalChannel-Identity =
1
SRB2: ul-LogicalChannel-Identity = dl-LogicalChannel-Identity =
2
for SRB0 being mapped to CCCH the LCID is '00000'B acc. to
TS 36.321, clause 6.2.1;
mandatory for initial configuration; omit means "keep as it is"
if omitted:
initial configuration: data is handed over to TTCN as usual
re-configuration:
"keep as it is"
if set:
true - SS shall discard any data in UL for this radio bearer
false - (re)configuration back to normal mode
NOTE: typically applicable for UM DRBs only
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
318
ETSI TS 136 523-3 V13.2.0 (2017-03)
RadioBearerConfig_Type
TTCN-3 Union Type
Name
RadioBearerConfig_Type
Comment
AddOrReconfig RadioBearerConfigInfo_Type
ure
Release
Null_Type
add / re-configure RB CellId : identifier of the cell being configured
RoutingInfo : None
TimingInfo : 'Now' in common cases
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
release RB CellId : identifier of the cell being configured
RoutingInfo : None
TimingInfo : 'Now' in common cases
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
RadioBearer_Type
TTCN-3 Record Type
Name
RadioBearer_Type
Comment
Id
RadioBearerId_Type
Config
RadioBearerConfig_Type
either for SRB or DRB
RadioBearerList_Type
TTCN-3 Record of Type
Name
RadioBearerList_Type
Comment
array of SRBs and/or DRBs (DRBs + 3 SRBs)
record length (1..tsc_MaxRB) of RadioBearer_Type
D.1.6
AS_Security
Primitive for control of AS security
PdcpSQN_Type
TTCN-3 Record Type
Name
PdcpSQN_Type
Comment
Format
PdcpCountFormat_Type
Value
integer
5 bit, 7 bit or 12 bit SQN
SQN value (5 bit, 7 bit or 12 bit SQN)
NOTE:
in TTCN the test case writer is responsible to deal with potential
overflows
(e.g. there shall be a "mod 32", "mod 128" or "mod 4096"
according to the format)
PDCP_ActTime_Type
TTCN-3 Union Type
Name
PDCP_ActTime_Type
Comment
The sequence number in UL and DL for SRB1 should be one more than the present SQN, as
Ciphering starts in UL and DL soon after SMC and SMComp;
For other SRB/DRB it should be the present SQN.
None
Null_Type
No Activation time; to be used if Ciphering is not applied
SQN
PdcpSQN_Type
PDCP sequence number
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
319
ETSI TS 136 523-3 V13.2.0 (2017-03)
SecurityActTime_Type
TTCN-3 Record Type
Name
SecurityActTime_Type
Comment
RadioBearerId
RadioBearerId_Type
UL
PDCP_ActTime_Type
DL
PDCP_ActTime_Type
SecurityActTimeList_Type
TTCN-3 Record of Type
Name
SecurityActTimeList_Type
Comment
record length (1..tsc_MaxRB) of SecurityActTime_Type
AS_IntegrityInfo_Type
TTCN-3 Record Type
Name
AS_IntegrityInfo_Type
Comment
for initial configuration activation time is not needed for integrity protection as all messages in DL after
security activation are integrity protected;
this means this ASP is invoked before transmission of Security mode command;
if there is a integrity violation in UL SS shall set the IndicationStatus in the common ASP part to flag
the integrity error
(IndicationStatus.Error.Integrity.Pdcp := true);
integrity to be provided for each SRB as per core spec
Algorithm
IntegrityProtAlgorithm_Type
IntegrityProtAlgorithm_Type being defined in RRC ASN.1
KRRCint
B128_Key_Type
ActTimeList
SecurityActTimeList_Type
opt omit for initial configuration (i.e. all SRBs to be integrity protected
immediately);
in HO scenarios activation time may be needed e.g. for SRB1
AS_CipheringInfo_Type
TTCN-3 Record Type
Name
AS_CipheringInfo_Type
Comment
Algorithm
CipheringAlgorithm_r12
KRRCenc
B128_Key_Type
KUPenc
B128_Key_Type
ActTimeList
SecurityActTimeList_Type
CipheringAlgorithm_Type being defined in RRC ASN.1
KUPenc is mandatory; and SS uses it when DRB are configured
AS_SecStartRestart_Type
TTCN-3 Record Type
Name
AS_SecStartRestart_Type
Comment
Integrity
AS_IntegrityInfo_Type
opt
Ciphering
opt
AS_CipheringInfo_Type
optional to allow separated activation of integrity and ciphering;
omit: keep as it is
optional to allow separated activation of integrity and ciphering;
omit: keep as it is
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
320
ETSI TS 136 523-3 V13.2.0 (2017-03)
AS_Security_Type
TTCN-3 Union Type
Name
AS_Security_Type
Comment
Security mode command procedure (TS 36.331, clause 5.3.4):
both SMC and SMComp are integrity protected
(nevertheless SS shall be able to cope with unprotected SM reject);
ciphering is started just after SMComp (acc. to TS 36.331, clause 5.3.4.3 and 5.3.1.1)
StartRestart
AS_SecStartRestart_Type
information to start/restart AS security protection in the PDCP
Release
Null_Type
to release AS security protection in the PDCP
D.1.7
Semi_Persistent_Scheduling
Semi-persistent scheduling (SPS)
NOTE 1:
configuration of SPS cannot be done completely in advance but needs to be activated by PDCCH signalling
=> SPS is configured/activated in an own primitive which may be sent to SS during RBs are being configured
NOTE 2:
semi-persistent (configured) scheduling is per UE (as well as 'normal' scheduling; see e.g. TS 36.300, clause 11.1)
SpsAssignmentUL_Type
TTCN-3 Record Type
Name
SpsAssignmentUL_Type
Comment
information to assign semi-persistent scheduls in UL
DciInfo
DciUlInfo_Type
opt to apply a grant
SchedulInterval SpsConfigurationUL_Type
opt as in TS 36.331, clause 6.3.2 SPS-ConfigUL
SetNDI_1
Null_Type
opt if present then NDI is set as 1 indicating a retransmission; If
absent then NDI is set as 0 indicating a new transmission
SpsAssignmentDL_Type
TTCN-3 Record Type
Name
SpsAssignmentDL_Type
Comment
information to assign semi-persistent scheduls in DL
DciInfo
DciDlInfo_Type
opt to apply a assignment
SchedulInterval SpsConfigurationDL_Type
opt as in TS 36.331, clause 6.3.2 SPS-ConfigDL
SetNDI_1
Null_Type
opt if present then NDI is set as 1 indicating a retransmission; If
absent then NDI is set as 0 indicating a new transmission
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
321
ETSI TS 136 523-3 V13.2.0 (2017-03)
SpsActivateInfo_Type
TTCN-3 Record Type
Name
SpsActivateInfo_Type
Comment
Semi-persistent scheduling (SPS):
Even though SPS is pre-configured at the UE (e.g. RRCConnectionSetup>RadioResourceConfiguration->MAC_MainConfig) it needs to be activated by L1 signalling
=> SS shall 'activate' SPS by sending appropriate assignments/grants to the UE; this shall be done
with an activation time.
If SPS is already configured and new Activate command is received, at the activation time SS locally
deactivates old SPS configuration, sends UE an PDCCH assignment for new SPS assignment and
locally activates new SPS configuration.
In DL, in addition to SS SPS assignment configuration with activation time 'T', TTCN writer shall also
schedule a DL MAC PDU with same activation time 'T' and at every SPS ScheduleInterval (NOTE: in
general it is an error when TTCN does not provide data for a SchedulInterval; SS shall send no data in
this case).
Special fields of PDCCH assignment are filled as per table 9.2-1 of 36.213
SPS_C_RNTI
C_RNTI
SPS C-RNTI as signalled to UE
UplinkGrant
SpsAssignmentUL_Type
opt
DownlinkAssig
SpsAssignmentDL_Type
opt
nment
SpsPdcchRelease_Type
TTCN-3 Record Type
Name
SpsPdcchRelease_Type
Comment
On reception of this information SS shall send an SPS release indicated by PDCCH transmission with
indicated DCI format (0 or 1A) at the activation time.
Special fields of PDCCH assignment are filled as per table 9.2-1A of 36.213
SPS_C_RNTI
C_RNTI
DCI_Format
PdcchDciFormat_Type
only formats 0 (UL release) and 1A (DL release) are applicable. It
is a TTCN error if any other formats are used.
SpsDeactivateInfo_Type
TTCN-3 Union Type
Name
SpsDeactivateInfo_Type
Comment
LocalRelease
Null_Type
PdcchExplicitR
elease
SpsPdcchRelease_Type
SPS configuration shall be released at the SS, that means as
well that the SS shall not address SPS_C_RNTI anymore from
the given TimingInfo onward;
NOTE: there is no SPS release to be signalled on PDCCH (this
is done with PdcchExplicitRelease - see below)
SS transmits PDCCH content indicating SPS release but holds
the local SPS configuration until it is locally released
SpsConfig_Type
TTCN-3 Union Type
Name
SpsConfig_Type
Comment
Activate
SpsActivateInfo_Type
Deactivate
SpsDeactivateInfo_Type
CellId : identifier of the cell where the UE is active
RoutingInfo : None
TimingInfo : activation time for SPS assignment/grant
transmission; NOTE: the first SPS DL data packet shall be sent
with the same timing information
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
CellId : identifier of the cell where the UE is active
RoutingInfo : None
TimingInfo : activation time for SPS release indicated by PDCCH
transmission or SS local deactivation
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.1.8
322
ETSI TS 136 523-3 V13.2.0 (2017-03)
Paging_Trigger
SubframeOffsetList_Type
TTCN-3 Record of Type
Name
SubframeOffsetList_Type
Comment
record length (1..infinity) of integer
PagingTrigger_Type
TTCN-3 Record Type
Name
PagingTrigger_Type
Comment
CellId : identifier of the cell where the UE is active
RoutingInfo : None
TimingInfo : Calculated paging occasion
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
primitive to trigger transmission of a paging on the PCCH at a calculated paging occasion (TS 36.304,
clause 7);
the paging occasion is calculated by TTCN and activation time is applied;
as for BCCH Infor acc. to TS 36.331, clause 9.1.1.3 "RRC will perform padding, if required due to the
granularity of the TF signalling, as defined in 8.5.";
therefore this needs to be done by the system simulator
Paging
PCCH_Message
paging to be send out at paging occasion and being announced
on PDCCH using P-RNTI
SubframeOffset SubframeOffsetList_Type
opt list of subframe offsets relative to the absolute timing information
List
given in the common part of the ASP;
if present, multiple pagings are sent out at all occasions given by
the list;
if omitted only a single paging is sent at the occasion given
timing information given in the common part of the ASP
D.1.9
L1_MAC_Indication_Control
Primitive for control of L1/MAC indication for special purposes
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
323
ETSI TS 136 523-3 V13.2.0 (2017-03)
L1Mac_IndicationControl_Type
TTCN-3 Record Type
Name
L1Mac_IndicationControl_Type
Comment
NOTE:
Initially all indications are disabled in SS (i.e. it shall not be necessary in 'normal' test cases to use this
primitive but only if a specific indication is needed); omit means indication mode is not changed
RachPreamble
IndicationAndControlMode_ opt To enable/disable reporting of PRACH preamble received.
Type
SchedReq
IndicationAndControlMode_ opt To enable/disable reporting of reception of Scheduling Request
Type
on PUCCH.
BSR
IndicationAndControlMode_ opt To enable/disable reporting of Buffer/Extended Buffer Status
Type
Report.
NOTE:
this is applicable only when MAC is configured in normal mode in
UL;
MAC configured in test mode, results in over writing the report.
UL_HARQ
IndicationAndControlMode_ opt To enable/disable reporting of reception of HARQ ACK/NACK.
Type
C_RNTI
IndicationAndControlMode_ opt To enable/disable reporting of C-RNTI sent by the UE within
Type
MAC PDU
PHR
IndicationAndControlMode_ opt To enable/disable reporting of Power Headroom Report.
Type
NOTE:
this is applicable only when MAC is configured in normal mode in
UL;
MAC configured in test mode, results in over writing the report.
HarqError
IndicationAndControlMode_ opt To enable/disable reporting of HARQ errors
Type
PeriodicRI
IndicationAndControlMode_ opt To enable/disable reporting of reception of periodic Rank
Type
Indicators
EPHR
IndicationAndControlMode_ opt To enable/disable reporting of Extended Power Headroom
Type
Report.
NOTE:
this is applicable only when MAC is configured in normal mode
for UL;
MAC configured in test mode, results in overwriting the report.
PeriodicCQI
IndicationAndControlMode_ opt To enable/disable reporting of reception of periodic CQI
Type
SRS
IndicationAndControlMode_ opt To enable/disable reporting of start and stop of reception of Type
Type
0 (Configured by Higher Layer) SRS in frames meant for periodic
SRS transmission by UE.
SS reports an indication every time when SRS reception from UE
has toggled in the frames configured for periodic SRS reception
i.e.
'No periodic SRS' reception -> 'periodic SRS' reception or
'periodic SRS' reception -> 'No periodic' SRS reception.
DC_PHR
IndicationAndControlMode_ opt To enable/disable reporting of Dual Connectivity Power
Type
Headroom Report.
NOTE: this is applicable only when MAC is configured in normal
mode for UL;
MAC configured in test mode, results in overwriting the report.
D.1.10 Rlc_Indication_Control
Primitive for control of RLC indication for special purposes
Rlc_IndicationMode_Type
TTCN-3 Enumerated Type
Name
Rlc_IndicationMode_Type
Comment
enable
disable
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
324
ETSI TS 136 523-3 V13.2.0 (2017-03)
Rlc_IndicationControl_Type
TTCN-3 Record Type
Name
Rlc_IndicationControl_Type
Comment
Discard
Rlc_IndicationMode_Type
opt
To enable/disable reporting of discarded RLC PDUs
D.1.11 PDCP_Count
Primitives to enquire PDCP COUNT
PdcpCountFormat_Type
TTCN-3 Enumerated Type
Name
PdcpCountFormat_Type
Comment
PdcpCount_Srb
27 bit HFN; 5 bit SQF
PdcpCount_DrbLong
20 bit HFN; 12 bit SQF
SQN
PdcpCount_DrbShort 25 bit HFN; 7 bit SQF
SQN
PdcpCount_Type
TTCN-3 Record Type
Name
PdcpCount_Type
Comment
Format
PdcpCountFormat_Type
Value
PdcpCountValue_Type
PdcpCountInfo_Type
TTCN-3 Record Type
Name
PdcpCountInfo_Type
Comment
RadioBearerId
RadioBearerId_Type
UL
PdcpCount_Type
DL
PdcpCount_Type
opt
opt
omit: keep as it is
omit: keep as it is
PdcpCountInfoList_Type
TTCN-3 Record of Type
Name
PdcpCountInfoList_Type
Comment
record length (1..tsc_MaxRB) of PdcpCountInfo_Type
PdcpCountGetReq_Type
TTCN-3 Union Type
Name
PdcpCountGetReq_Type
Comment
AllRBs
Null_Type
SingleRB
RadioBearerId_Type
return COUNT values for all RBs being configured
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
325
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_CountReq_Type
TTCN-3 Union Type
Name
PDCP_CountReq_Type
Comment
Get
PdcpCountGetReq_Type
Set
Request PDCP count for one or all RBs being configured at the
PDCP
Set PDCP count for one or all RBs being configured at the
PDCP;
list for RBs which's COUNT shall be manipulated
PdcpCountInfoList_Type
PDCP_CountCnf_Type
TTCN-3 Union Type
Name
PDCP_CountCnf_Type
Comment
Get
PdcpCountInfoList_Type
Set
Null_Type
RBs in ascending order; SRBs first
D.1.12 PDCP_Handover
Primitives to control PDCP regarding handover
PDCP_HandoverInit_Type
TTCN-3 Record Type
Name
PDCP_HandoverInit_Type
Comment
SourceCellId
EUTRA_CellId_Type
PDCP_HandoverControlReq_Type
TTCN-3 Union Type
Name
PDCP_HandoverControlReq_Type
Comment
HandoverInit
PDCP_HandoverInit_Type
to inform SS that a handover will follow:
in the common ASP part the CellId shall be set to the id of the
target cell
HandoverComp Null_Type
to inform SS that the handover has successfully been performed
lete
by the UE;
this shall trigger the SS to sent a PDCP Status Report to the UE;
in the common ASP part the CellId shall be set to the id of the
target cell
D.1.13 L1_MAC_Test_Mode
Primitive for control of L1/MAC Test Modes
L1_TestMode_Type
TTCN-3 Record Type
Name
L1_TestMode_Type
Comment
L1 test mode; in general RACH is handled separately
DL_SCH_CRC
DL_SCH_CRC_Type
Manipulation of CRC bit generation for DL-SCH
Phich
PhichTestMode_Type
HARQ feedback mode on the PHICH
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
326
DL_SCH_CRC_Type
TTCN-3 Union Type
Name
DL_SCH_CRC_Type
Comment
NOTE:
CRC error mode for RA_RNTI is not addressed as it will be configured in RACHProcedureConfig
C_RNTI
MAC_Test_DL_SCH_CRC_Mode to configure mode for CRC bit for all MAC PDU's for which C_Type
RNTI is used in PDCCH transmission
SI_RNTI
MAC_Test_DL_SCH_CRC_Mode to configure mode for CRC bit for all MAC PDU's for which SI_Type
RNTI is used in PDCCH transmission
SPS_RNTI
MAC_Test_DL_SCH_CRC_Mode to configure mode for CRC bit for all MAC PDU's for which SPS_Type
RNTI is used in PDCCH transmission
D.1.14 PDCCH_Order
Primitive to trigger SS to send PDCCH order to initiate RA procedure (TS 36.321, clause 5.1.1)
PDCCH_Order: Basic Type Definitions
TTCN-3 Basic Types
PrachPreambleIndex_Typ
e
PrachMaskIndex_Type
Ra_PreambleIndex_Type
integer (0..15)
TS 36.321, clause 7.3
RA_PDCCH_Order_Type
TTCN-3 Record Type
Name
RA_PDCCH_Order_Type
Comment
see also TS 36.212, clause 5.3.3.1.3
PreambleIndex PrachPreambleIndex_Type
naming acc. TS 36.212, clause 5.3.3.1.3
PrachMaskInde PrachMaskIndex_Type
naming acc. TS 36.212, clause 5.3.3.1.3
x
D.1.15 System_Indications
Primitives for System indications
System_Indications: Basic Type Definitions
TTCN-3 Basic Types
PRTPower_Type
LogicalChannelGroup_Ty
pe
BSR_Value_Type
PHR_Type
RI_Type
Dummy_Type
needs to define appropriately the power level
report of
PREAMBLE_RECEIVED_TARGET_POWER;
NOTE: for the time being this is just a place
holder for enhancements in the future.
integer (0..3)
integer (0..63)
integer (0..63)
integer (1..4)
Rank indicator reported acc. to TS 36.212
Table 5.2.2.6-6
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
327
ETSI TS 136 523-3 V13.2.0 (2017-03)
HarqProcessInfo_Type
TTCN-3 Record Type
Name
HarqProcessInfo_Type
Comment
Id
HarqProcessId_Type
CURRENT_TX integer
_NB
acc. to TS 36.321 clause 5.4.2.2
HarqError_Type
TTCN-3 Union Type
Name
HarqError_Type
Comment
UL
HarqProcessInfo_Type
DL
indicates HARQ error detected at the SS side (error at UL
transmission)
indicates HARQ NACK sent by the UE (error at DL transmission)
HarqProcessInfo_Type
RachPreamble_Type
TTCN-3 Record Type
Name
RachPreamble_Type
Comment
RAPID
PrachPreambleIndex_Type
PRTPower
PRTPower_Type
RepetitionsPer
integer
PreambleAttem
pt
opt
indicates the RAPID of the preamble used (integer (0..63))
represents the PREAMBLE_RECEIVED_TARGET_POWER
Applicable when numRepetitionPerPreambleAttempt-r13 is
configured
Short_BSR_Type
TTCN-3 Record Type
Name
Short_BSR_Type
Comment
LCG
LogicalChannelGroup_Type
Value
BSR_Value_Type
Logical channel Group
BSR or Extended BSR value
Long_BSR_Type
TTCN-3 Record Type
Name
Long_BSR_Type
Comment
Value_LCG1
BSR_Value_Type
Value_LCG2
BSR_Value_Type
Value_LCG3
BSR_Value_Type
Value_LCG4
BSR_Value_Type
BSR or Extended BSR value for LCG 1
BSR or Extended BSR value for LCG 2
BSR or Extended BSR value for LCG 3
BSR or Extended BSR value for LCG 4
BSR_Type
TTCN-3 Union Type
Name
BSR_Type
Comment
Short
Short_BSR_Type
Truncated
Short_BSR_Type
Long
Long_BSR_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
328
ETSI TS 136 523-3 V13.2.0 (2017-03)
RlcDiscardInd_Type
TTCN-3 Record Type
Name
RlcDiscardInd_Type
Comment
SS shall send this indication if it discards a received RLC AMD PDU as specified in TS 36.322 cl.
5.1.3.2.2.
SequenceNum
integer
sequence number of the PDU being discarded
ber
SRSInd_Type
TTCN-3 Enumerated Type
Name
SRSInd_Type
Comment
SRS_Start
SS was not receiving SRS in the frames configured for periodic SRS, and SS has started
reception of higher layer configured SRS in frame meant for periodic SRS transmission
SRS_Stop
SS was receiving SRS in the frames configured for periodic SRS, and SS has stopped reception
of higher layer configured SRS in frame meant for periodic SRS transmission
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
329
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.1.16 System_Interface
SYSTEM_CTRL_REQ
TTCN-3 Record Type
Name
SYSTEM_CTRL_REQ
Comment
Common
ReqAspCommonPart_Type
Request
SystemRequest_Type
TimingInfo depends on respective primitive:
- Cell
TimingInfo: 'now' (in general)
- CellAttenuationList
TimingInfo: 'now' (in general, but activation time may be used
also)
- RadioBearerList
TimingInfo: 'now' in general;
activation time may be used in special case for release and/or
reconfiguration of one or several RBs;
the following rules shall be considered:
- release/Reconfiguration of an RB shall not be scheduled
ealier than 5ms after a previous data transmission on this RB
- subsequent release and reconfiguration(s) shall be
scheduled with an interval of at least 5ms
- a subsequent data transmission on an RB shall not be
scheduled ealier than 5ms after the last reconfiguration of the RB
the configuration shall be performed exactly at the given time
- EnquireTiming
TimingInfo: 'now'
- AS_Security
TimingInfo: 'now';
NOTE: "activation time" may be specified in the primitive based
on PDCP SQN
- Sps
TimingInfo: activation time for SPS assignment transmission
- Paging
TimingInfo: Calculated paging occasion
- L1MacIndCtrl
TimingInfo: 'now' (in general)
- PdcpCount
TimingInfo: 'now' (in general)
activation time may be used in case of CA inter cell handover to
set the PdcpCount
- L1_TestMode
TimingInfo: depends on the test mode;
activation time is used e.g. for manipulation of the CRC
- PdcchOrder
TimingInfo: 'now' (in general)
SYSTEM_CTRL_CNF
TTCN-3 Record Type
Name
SYSTEM_CTRL_CNF
Comment
Common
CnfAspCommonPart_Type
Confirm
TimingInfo is ignored by TTCN (apart from EnquireTiming)
=> SS may set TimingInfo to "None"
SystemConfirm_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
330
ETSI TS 136 523-3 V13.2.0 (2017-03)
SYSTEM_IND
TTCN-3 Record Type
Name
SYSTEM_IND
Comment
Common
IndAspCommonPart_Type
Indication
The SS shall provide TimingInfo (SFN + subframe number)
depending on the respective indication:
- Error/HarqError
TimingInfo: related to the error (if available)
- RachPreamble
TimingInfo: shall indicate start of the RACH preamble. In case
of Preamble repetition (BL/CE UE under test), indicates the
timing of the first Preamble transmission.
- SchedReq
TimingInfo: subframe containing the SR
- BSR
TimingInfo: subframe in which the MAC PDU contains the BSR
- UL_HARQ
TimingInfo: subframe containing the UL HARQ
- C_RNTI
TimingInfo: subframe in which the MAC PDU contains the
C_RNTI
- PHR
TimingInfo: subframe in which the MAC PDU contains the PHR
SystemIndication_Type
EUTRA_SYSTEM_PORT
TTCN-3 Port Type
Name
EUTRA_SYSTEM_PORT
Comment
EUTRA PTC: Port for system configuration
out
SYSTEM_CTRL_REQ
in
SYSTEM_CTRL_CNF
EUTRA_SYSIND_PORT
TTCN-3 Port Type
Name
EUTRA_SYSIND_PORT
Comment
EUTRA PTC: Port for system indications
in
SYSTEM_IND
D.1.17 MBMS_Configuration
EUTRA_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_MaxMRB
integer
32
ETSI
maximum MRB used in test cases
- Value arbitrarily set to 32 (5bits)
Theorically the maximum value is
maxPMCH-PerMBSFN *
maxSessionPerPMCH i.e. 15*29
3GPP TS 36.523-3 version 13.2.0 Release 13
331
ETSI TS 136 523-3 V13.2.0 (2017-03)
MBMS_Config_Type
TTCN-3 Record Type
Name
MBMS_Config_Type
Comment
all fields are optional to allow single modifications;
activation time is applied in the common part of the ASP
Mbsfn_Subfra
MBSFN_SubframeConfigLi
opt Configure subframes reserved for MBSFN
meConfigList
st
MbsfnAreaList
MbsfnAreaList_Type
opt Configure all MBSFN areas
ScptmConfig
SCPTM_Config_Type
opt If this IE is present, MBMS services are provided via SC-PTM
MbsfnAreaList_Type
TTCN-3 Record of Type
Name
MbsfnAreaList_Type
Comment
record length(1..maxMBSFN_Area) of MbsfnArea_Type
MbsfnArea_Type
TTCN-3 Record Type
Name
MbsfnArea_Type
Comment
Mbsfn_AreaInf
MBSFN_AreaInfo_r9
o
McchData
MbsfnAreaConf
iguration
MRB_List
opt
MCCH_Data_Type
MBSFNAreaConfiguration_r
9
MRB_List_Type
opt
opt
Configure MCCH scheduling
acc. to TS 36. 331 cl 9.1.1.4 there is no PDCP and MCCH use
the RLC-UM mode
configuration/scheduling and contents of the MCCH Information
is done in one go
(i.e. there are no separate ports for MCCH data and
configuration)
MCCH information to be broadcasted
Configuration parameters for CommonCSA/PMCH/MTCH
opt
Configure/release MTCH MRBs
MCCH_Data_Type
TTCN-3 Record Type
Name
MCCH_Data_Type
Comment
Mbsfn_AreaId
MBSFN_AreaId_r12
MsgList
opt
Used only for modification of MCCH info.
Omitted if Mbsfn_AreaInfo is present and mandatory present
otherwise
MCCH_MessageList_Type
MCCH_MessageList_Type
TTCN-3 Record of Type
Name
MCCH_MessageList_Type
Comment
Includes mbsfnAreaConfiguration-r9 and optionally mbmsCountingRequest-r10.
record length(1..2) of MCCH_Message
MRB_List_Type
TTCN-3 Record of Type
Name
MRB_List_Type
Comment
record length(1.. tsc_MaxMRB) of MRB_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
332
ETSI TS 136 523-3 V13.2.0 (2017-03)
MRB_Type
TTCN-3 Record Type
Name
MRB_Type
Comment
PmchLogicalCh PmchLogicalChannel_Type
annel
Config
MTCH_Config_Type
opt
present for MRB_COMMON_REQ for MTCH data scheduling;
not present for SystemRequest_Type MSI_Conf
MSI_Config_Type
TTCN-3 Union Type
Name
MSI_Config_Type
Comment
None
Null_Type
Auto
MSI_MCE_Type
no MSI MCE included
SS automatically includes configured MSI in the first subframes
allocated to the MCH within the MCH scheduling period
MSI_Type
TTCN-3 Record Type
Name
MSI_Type
Comment
36.321 clause 6.1.3.7
LchID
integer (0..31)
StopMTCH
integer (0..2047)
MRB Logical Channel ID
Stop MTCH
MSI_MCE_Type
TTCN-3 Record of Type
Name
MSI_MCE_Type
Comment
record of MSI_Type
MTCH_Config_Type
TTCN-3 Union Type
Name
MTCH_Config_Type
Comment
AddOrReconfig MTCH_ConfigInfo_Type
ure
Release
Null_Type
Add/re-configure RB CellId : identifier of the cell being configured
RoutingInfo : none
TimingInfo : 'Now' in common cases
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
release RB CellId : identifier of the cell being configured
RoutingInfo : none
TimingInfo : 'Now' in common cases
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
MTCH_ConfigInfo_Type
TTCN-3 Record Type
Name
MTCH_ConfigInfo_Type
Comment
Acc. to TS 36. 331 cl 9.1.1.4 there is no PDCP and MTCH use the RLC-UM mode
Rlc
RLC_Configuration_Type
opt Mandatory for initial configuration; omit means "keep as it is"
Note RLC DL only UM mode with SN 5 bits is only valid
Mac
MAC_MCH_TestModeConfi opt
g_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
333
ETSI TS 136 523-3 V13.2.0 (2017-03)
MAC_MCH_TestModeConfig_Type
TTCN-3 Union Type
Name
MAC_MCH_TestModeConfig_Type
Comment
None
Null_Type
MAC operation in normal mode for MCH
Config
Null_Type
MAC is configured in no header manipulation in DL [MTCH is DL
only channel]
PDCCH_MCCH_ChangeNotification_Type
TTCN-3 Record Type
Name
PDCCH_MCCH_ChangeNotification_Type
Comment
NotificationIndi
NotificationIndicator_r9_Typ opt MCCH change notification: shall be present, PDCCH shall be
e
cator_r9
scrambled with M-RNTI
SC-MCCH change notification: shall be omitted. PDCCH shall be
scrambled with SC-N-RTNI
SubframeOffset SubframeOffsetList_Type
opt list of subframe offsets relative to the absolute timing information
List
given in the
common part of the ASP, this IE is MCCH-relevant and may be
present only if NotificationIndicator_r9 is present;
if present, multiple MCCH Change Notifications are sent out at all
occasions given by the list;
if omitted only a single MCCH Change Notifications is sent at the
occasion given timing information given in
the common part of the ASP
PmchConfig_Type
TTCN-3 Record Type
Name
PmchConfig_Type
Comment
RelativeTxPow
ToRS_EPRE_Ratios_Type
er
opt
power ratio for MBSFN-RS and PMCH's resource elements
relative to the CRS
D.1.18 SCPTM_Configuration
EUTRA_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_MaxSC_MRB
integer
1023
ETSI
maximum SC-MRBs used in test
cases arbitrarly set to 32 (5bits),
but can set to max number of SCMTCHs in one cell that is
1023(10bits)
3GPP TS 36.523-3 version 13.2.0 Release 13
334
ETSI TS 136 523-3 V13.2.0 (2017-03)
SCPTM_Config_Type
TTCN-3 Record Type
Name
SCPTM_Config_Type
Comment
all fields are optional to allow single modifications;
if IE is set to "omit" - no change from previous configuration
activation time is applied in the common part of the ASP
ScMcchSchedu SC_MCCH_Scheduling_Ty
opt SC-MCCH scheduling configuration on PDCCH as per
pe
ling
SystemInformationBlockType20
acc. to TS 36. 331 cl 9.1.1.4 there is no PDCP and SC-MCCH
uses the RLC-UM mode
configuration/scheduling and contents of the SC-MCCH
Information is done in one go
(i.e. there are no separate ports for SC-MCCH data and
configuration)
ScptmConfigur
SCPTMConfiguration_r13
opt Message containing SC-MTCH configuration to be broadcasted
ation
on SC-MCCH
ScMrbList
SC_MRB_List_Type
opt Configure/release SC-MTCH SC-MRB
SC_MCCH_Scheduling_Type
TTCN-3 Record Type
Name
SC_MCCH_Scheduling_Type
Comment
ScMcchRepetiti SC_MCCH_RepetitionPerio
d_Type
onPeriod
ScMcchOffset
SC_MCCH_Offset_Type
ScMcchFirstSu SC_MCCH_FirstSubframe_
Type
bframe
ScMcchDuratio SC_MCCH_Duration_Type
opt
n
ScMcchModific SC_MCCH_ModificationPer
iod_Type
ationPeriod
SC_MRB_List_Type
TTCN-3 Record of Type
Name
SC_MRB_List_Type
Comment
record length(1.. tsc_MaxSC_MRB) of SC_MRB_Type
SC_MRB_Type
TTCN-3 Record Type
Name
SC_MRB_Type
Comment
ScMrbId
SC_MRB_Identity_Type
Config
SC_MTCH_Config_Type
SC_MTCH_Config_Type
TTCN-3 Record Type
Name
SC_MTCH_Config_Type
Comment
GRnti
B16_Type
ScMtchConfig
MTCH_Config_Type
ScMtchSchedul SC_MTCH_SchedulingInfo
ingInfo
_r13
opt
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
335
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.1.19 DirectIndicationInfo_Trigger
DirectIndicationInfoTrigger_Type
TTCN-3 Record Type
Name
DirectIndicationInfoTrigger_Type
Comment
CellId : identifier of the cell where the UE is active
RoutingInfo : None
TimingInfo : Calculated paging occasion
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
primitive to trigger transmission of a Direct Indication Information on MPDCCH at a calculated paging
occasion (TS 36.304, clause 7)
using DCI command 6_2 with Flag=0 and including the 8 bits in the DCI command (TS 36.212 clause
5.3.3.1.14);
the paging occasion is calculated by TTCN and activation time is applied;
DirectIndication B8_Type
Direct Indication Information
Info
SubframeOffset SubframeOffsetList_Type
opt list of subframe offsets relative to the absolute timing information
List
given in the common part of the ASP;
if present, multiple direct indications are sent out at all occasions
given by the list;
if omitted only a single direct indication is sent at the occasion
given timing information given in the common part of the ASP
D.2
EUTRA_ASP_DrbDefs
ASP interface for DRBs
D.2.1
MBMS_MRB_Primitive_Definitions
EUTRA_MRB_PORT
TTCN-3 Port Type
Name
EUTRA_MRB_PORT
Comment
out
MRB_COMMON_REQ
MRB_COMMON_REQ
TTCN-3 Record Type
Name
MRB_COMMON_REQ
Comment
common ASP to send PDUs to MRBs
Common
ReqAspCommonPart_Type
CellId : identifier of the cell
RoutingInfo : set to Mrb
TimingInfo : starting point when to start sending sequence of
data PDUs
e.g.
SFN = X, subframe number = x;
U_Plane.SubframeDataList[i].SubframeOffset := offset_i;
=> U_Plane.SubframeDataList[i].PduSduList shall be sent out
at
SFN = X + ((x + offset_i) / 10);
subframe number = (x + offset_i) % 10
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
U_Plane
L2Data_Request_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.2.2
336
ETSI TS 136 523-3 V13.2.0 (2017-03)
System_Interface
DRB_COMMON_REQ
TTCN-3 Record Type
Name
DRB_COMMON_REQ
Comment
common ASP to send PDUs to DRBs
Common
ReqAspCommonPart_Type
CellId : identifier of the cell
RoutingInfo : DRB id
TimingInfo : starting point when to start sending sequence of
data PDUs
e.g.
SFN = X, subframe number = x;
U_Plane.SubframeDataList[i].SubframeOffset := offset_i;
=> U_Plane.SubframeDataList[i].PduSduList shall be sent out
at
SFN = X + ((x + offset_i) / 10);
subframe number = (x + offset_i) % 10
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
U_Plane
L2Data_Request_Type
SuppressPdcch Null_Type
opt By default all DRB_COMMON_REQ scheduled DL PDU's are
ForC_RNTI
associated with an appropriate explicit configured or SS selected
DL assignment allocation on PDCCH.
For SuppressPdcch:=true in the sub frame in which DL PDU's
are transmitted, there is no associated DL assignment allocation
for configured C-RNTI. This will be used for SPS assignment
based transmission or in any error scenarios;
NOTE: this flag has no impact on PDCCH messages required for
SPS activation
DRB_COMMON_IND
TTCN-3 Record Type
Name
DRB_COMMON_IND
Comment
common ASP to receive PDUs from DRBs
Common
IndAspCommonPart_Type
CellId : identifier of the cell
RoutingInfo : DRB id
TimingInfo : time when message has been received
NOTE 1:
For MAC and RCL PDUs per definition L2Data_Indication_Type
corresponse to exactly one subframe
=> TimingInfo refers to this subframe
NOTE 2:
For PDCP a single PDU or SDU may take more than one TTI
=> TimingInfo refers to the end of the PDU/SDU and the length is
given by NoOfTTIs in L2Data_Indication_Type
(the end of the PDU/SDU is the last RLC PDU being received; in
case of retransmissins this is not necessarily the RLC PDU with
the last SN)
U_Plane
L2Data_Indication_Type
EUTRA_DRB_PORT
TTCN-3 Port Type
Name
EUTRA_DRB_PORT
Comment
out
DRB_COMMON_REQ
in
DRB_COMMON_IND
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.3
ETSI TS 136 523-3 V13.2.0 (2017-03)
337
EUTRA_NB_ASP_L2DataDefs
ASP interface for DRBs
D.3.1
PDU_TypeDefs
D.3.1.1 MAC_PDU
MAC_PDU: Basic Type Definitions
TTCN-3 Basic Types
MAC_CTRL_C_RNTI_Typ
e
MAC_CTRL_ContentionR
esolutionId_Type
C_RNTI
TS 36.321, clause 6.1.3.2
ContentionResolutionId_Type
TS 36.321, clause 6.1.3.4
fix 48-bit size;
consists of a single field defined UE
Contention Resolution Identity
(first 48 bits of the uplink CCCH SDU
transmitted by MAC)
TS 36.321, clause 6.1.3.5
indicates the amount of timing adjustment in
0.5 ms that the UE has to apply;
the length of the field is 8 bits
MAC_CTRL_TimingAdvan
ce_Type
B8_Type
MAC_SDU_Type
octetstring
MAC_PDU_Length_Type
TTCN-3 Record Type
Name
MAC_PDU_Length_Type
Comment
NOTE:
since F and L field are either both present or both omitted they are put into this record;
to allow homogeneous (direct) encoding the PDU length is not defined as union;
TTCN-3 does allow length restrictions to one lenght or a range of length but not to two specific
lengthes;
further restriction may be achieved by appropriate templates (parameter either 7 or 15 bit)
Format
B1_Type
F:
The Format field indicates the size of the Length field as
indicated in table 6.2.1-3.
There is one F field per MAC PDU subheader except for the last
subheader and sub-headers corresponding to fixed-sized MAC
control elements. The size of the F field is 1 bit.
If the size of the MAC SDU or MAC control element is less than
128 bytes, the UE shall set the value of the F field to 0, otherwise
the UE shall set it to 1
Value
B7_15_Type
L:
The Length field indicates the length of the corresponding MAC
SDU or MAC control element in bytes.
There is one L field per MAC PDU subheader except for the last
subheader and sub-headers corresponding to fixed-sized MAC
control elements.
The size of the L field is indicated by the F field
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
338
ETSI TS 136 523-3 V13.2.0 (2017-03)
MAC_PDU_SubHeader_Type
TTCN-3 Record Type
Name
MAC_PDU_SubHeader_Type
Comment
Reserved
B2_Type
Extension
B1_Type
LCID
B5_Type
Length
MAC_PDU_Length_Type
Reserved bits
E:
The Extension field is a flag indicating if more fields are present
in the MAC header or not.
The E field is set to "1" to indicate another set of at least
R/R/E/LCID fields.
The E field is set to "0" to indicate that either a MAC SDU, a
MAC control element or padding starts at the next byte
LCID:
The Logical Channel ID field identifies the logical channel
instance of the corresponding MAC SDU or the type of the
corresponding MAC control element or padding as described in
tables 6.2.1-1 and 6.2.1-2 for the DL and UL-SCH respectively.
There is one LCID field for each MAC SDU, MAC control element
or padding included in the MAC PDU. The LCID field size is 5
bits;
NOTE: In case of DRX command the sub-header corresponds to
a control element of length zero (i.e. there is no control element)
opt
MAC_Header_Type
TTCN-3 Record of Type
Name
MAC_Header_Type
Comment
record of MAC_PDU_SubHeader_Type
MAC_CTRL_ShortBSR_Type
TTCN-3 Record Type
Name
MAC_CTRL_ShortBSR_Type
Comment
TS 36.321, clause 6.1.3.1
LCG
B2_Type
Value
B6_Type
MAC_CTRL_LongBSR_Type
TTCN-3 Record Type
Name
MAC_CTRL_LongBSR_Type
Comment
TS 36.321, clause 6.1.3.1
Value_LCG1
B6_Type
Value_LCG2
B6_Type
Value_LCG3
B6_Type
Value_LCG4
B6_Type
MAC_CTRL_PowerHeadRoom_Type
TTCN-3 Record Type
Name
MAC_CTRL_PowerHeadRoom_Type
Comment
TS 36.321, clause 6.1.3.6
Reserved
B2_Type
Value
B6_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
339
ETSI TS 136 523-3 V13.2.0 (2017-03)
MAC_CTRL_ElementList_Type
TTCN-3 Set Type
Name
MAC_CTRL_ElementList_Type
Comment
NOTE 1:
for simplicication UL and DL are not distinguished even though the control elements are either UL or
DL
NOTE 2:
type is defined as set: the ordering is not signifficant;
nevertheless the ordering is well-defined by the sub-headers;
for codec implementations it is in any case necessary to evaluate the sub-header information in order
to encode/decode the payload
ShortBSR
MAC_CTRL_ShortBSR_Ty
opt UL only
pe
LongBSR
MAC_CTRL_LongBSR_Typ opt UL only
e
C_RNTI
MAC_CTRL_C_RNTI_Type opt UL only
ContentionRes
MAC_CTRL_ContentionRe
opt DL only
solutionId_Type
olutionID
TimingAdvance MAC_CTRL_TimingAdvanc opt DL only
e_Type
PowerHeadRo
MAC_CTRL_PowerHeadRo opt UL only
om_Type
om
ScellActDeact
MAC_CTRL_ScellActDeact
opt DL only
_Type
ExtPowerHead
MAC_CTRL_ExtPowerHea
opt UL only. Only one among PowerHeadroom, ExtPowerHeadroom
dRoom_Type
Room
and DC_PowerHeadRoom may be present
DC_PowerHea
MAC_CTRL_DC_PowerHe
opt UL only. Only one among PowerHeadroom, ExtPowerHeadroom
adRoom_Type
dRoom
and DC_PowerHeadRoom may be present
MAC_SDUList_Type
TTCN-3 Record of Type
Name
MAC_SDUList_Type
Comment
record of MAC_SDU_Type
MAC_PDU_Type
TTCN-3 Record Type
Name
MAC_PDU_Type
Comment
Header
MAC_Header_Type
CtrlElementList
MAC_CTRL_ElementList_T
ype
opt
SduList
Padding
MAC_SDUList_Type
octetstring
opt
opt
list of MAC PDU SubHeaders corresponding to MAC control
elements and MAC SDUs
Mac control elements;
acc. to TS 36.321, clause 6.1.2 "MAC control elements, are
always placed before any MAC SDU."
MAC SDUs, which can typically be RLC PDUs
Octet aligned Padding if more than or equal to 2 bytes
MAC_PDUList_Type
TTCN-3 Record of Type
Name
MAC_PDUList_Type
Comment
record of MAC_PDU_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
340
D.3.1.2 RLC_PDU
D.3.1.2.1
Common
RLC PDU definition: common AM/UM field definitions
Common: Basic Type Definitions
TTCN-3 Basic Types
RLC_FramingInfo_Type
B2_Type
00 First byte of the Data field corresponds to the
first byte of a RLC SDU.
Last byte of the Data field corresponds to the
last byte of a RLC SDU.
01 First byte of the Data field corresponds to the
first byte of a RLC SDU.
Last byte of the Data field does not
correspond to the last byte of a RLC SDU.
10 First byte of the Data field does not
correspond to the first byte of a RLC SDU.
Last byte of the Data field corresponds to the
last byte of a RLC SDU.
11 First byte of the Data field does not
correspond to the first byte of a RLC SDU.
Last byte of the Data field does not
correspond to the last byte of a RLC SDU.
RLC_LengthIndicator_LI11_Type
TTCN-3 Record Type
Name
RLC_LengthIndicator_LI11_Type
Comment
Extension
B1_Type
0 - Data field follows from the octet following the LI field following
this E field
1 - A set of E field and LI field follows from the bit following the LI
field following this E field
LengthIndicator B11_Type
Length Indicator
RLC_LengthIndicator_LI15_Type
TTCN-3 Record Type
Name
RLC_LengthIndicator_LI15_Type
Comment
Extension
B1_Type
0 - Data field follows from the octet following the LI field following
this E field
1 - A set of E field and LI field follows from the bit following the LI
field following this E field
LengthIndicator B15_Type
15 bit Length Indicator
RLC_LI11_List_Type
TTCN-3 Record of Type
Name
RLC_LI11_List_Type
Comment
record of RLC_LengthIndicator_LI11_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
341
RLC_LI15_List_Type
TTCN-3 Record of Type
Name
RLC_LI15_List_Type
Comment
record of RLC_LengthIndicator_LI15_Type
RLC_LI_List_Type
TTCN-3 Union Type
Name
RLC_LI_List_Type
Comment
LI11
RLC_LI11_List_Type
LI15
RLC_LI15_List_Type
RLC_PDU_Header_FlexPart_Type
TTCN-3 Record Type
Name
RLC_PDU_Header_FlexPart_Type
Comment
Flexible part of the header with a number of K LIs
LengthIndicator RLC_LI_List_Type
List of E, LI fields
Padding
B4_Type
opt optional 4 bit padding present in case of odd number of LI's
D.3.1.2.2
TM_Data
RLC PDU definition: UM (TS 36.322, clause 6.2.1.2)
TM_Data: Basic Type Definitions
TTCN-3 Basic Types
RLC_TMD_PDU_Type
D.3.1.2.3
octetstring
TS 36.322, clause 6.2.1.2
UM_Data
RLC PDU definition: UM (TS 36.322, clause 6.2.1.3)
NOTE:
To allow direct encoding the definition for RLC UM Data PDU is split into data PDU with 5/10 bit sequence number
UM_Data: Basic Type Definitions
TTCN-3 Basic Types
RLC_DataField_Type
octetstring
restrictions imposed from LI size of 11 bits is
not applicable when the LI's are not present
RLC_UMD_Header_FixPartShortSN_Type
TTCN-3 Record Type
Name
RLC_UMD_Header_FixPartShortSN_Type
Comment
TS 36.322, clause 6.2.1.3 Figure 6.2.1.3-1, 6.2.1.3-3 and 6.2.1.3-4);
one octet
FramingInfo
RLC_FramingInfo_Type
2 bits FI
Extension
B1_Type
1 bit E
SequenceNum
B5_Type
5 bits SN
ber
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
342
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC_UMD_Header_FixPartLongSN_Type
TTCN-3 Record Type
Name
RLC_UMD_Header_FixPartLongSN_Type
Comment
TS 36.322, clause 6.2.1.3 Figure 6.2.1.3-2, 6.2.1.3-5 and 6.2.1.3-6);
two octets
Reserved
B3_Type
3 bits reserved
FramingInfo
RLC_FramingInfo_Type
2 bits FI
Extension
B1_Type
1 bit E
SequenceNum
B10_Type
10 bits SN
ber
RLC_UMD_HeaderShortSN_Type
TTCN-3 Record Type
Name
RLC_UMD_HeaderShortSN_Type
Comment
FixPart
RLC_UMD_Header_FixPart
ShortSN_Type
FlexPart
RLC_PDU_Header_FlexPa
opt
rt_Type
RLC_UMD_HeaderLongSN_Type
TTCN-3 Record Type
Name
RLC_UMD_HeaderLongSN_Type
Comment
FixPart
RLC_UMD_Header_FixPart
LongSN_Type
FlexPart
RLC_PDU_Header_FlexPa
opt
rt_Type
RLC_DataFieldList_Type
TTCN-3 Record of Type
Name
RLC_DataFieldList_Type
Comment
One to one correspondence with sub headers (LengthIndicatorList_Type)
record of RLC_DataField_Type
RLC_UMD_PDU_ShortSN_Type
TTCN-3 Record Type
Name
RLC_UMD_PDU_ShortSN_Type
Comment
Header
RLC_UMD_HeaderShortSN
_Type
Data
RLC_DataFieldList_Type
RLC_UMD_PDU_LongSN_Type
TTCN-3 Record Type
Name
RLC_UMD_PDU_LongSN_Type
Comment
Header
RLC_UMD_HeaderLongSN
_Type
Data
RLC_DataFieldList_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
343
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC_UMD_PDU_Type
TTCN-3 Union Type
Name
RLC_UMD_PDU_Type
Comment
ShortSN
RLC_UMD_PDU_ShortSN_Type
LongSN
RLC_UMD_PDU_LongSN_Type
D.3.1.2.4
AM_Data
RLC PDU definition: AM (TS 36.322, clause 6.2.1.4 and 6.2.1.5)
RLC_AMD_Header_FixPart_Type
TTCN-3 Record Type
Name
RLC_AMD_Header_FixPart_Type
Comment
TS 36.322, clause 6.2.1.4 Figure 6.2.1.4-1, 6.2.1.4-2 and 6.2.1.4-3);
2 or 4 octets (AMD PDU or AMD PDU segment)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
ReSeg
B1_Type
0 - AMD PDU
1 - AMD PDU segment
Poll
B1_Type
0 - Status report not requested
1 - Status report is requested
FramingInfo
RLC_FramingInfo_Type
2 bit FI
Extension
B1_Type
1 bit E
SN
B10_Type
Sequence number
RLC_AMD_Header_FixPartExt_Type
TTCN-3 Record Type
Name
RLC_AMD_Header_FixPartExt_Type
Comment
TS 36.322, clause 6.2.1.4 Figure 6.2.1.4-1a, 6.2.1.4-2a and 6.2.1.4-3a);
3 octets
D_C
B1_Type
0 - Control PDU
1 - Data PDU
ReSeg
B1_Type
0 - AMD PDU
1 - AMD PDU segment
Poll
B1_Type
0 - Status report not requested
1 - Status report is requested
FramingInfo
RLC_FramingInfo_Type
2 bit FI
Extension
B1_Type
1 bit E
Reserved
B2_Type
2 reserved bits
SN_Ext
B16_Type
Sequence number
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
344
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC_AMD_Header_FixPartSegExt_Type
TTCN-3 Record Type
Name
RLC_AMD_Header_FixPartSegExt_Type
Comment
TS 36.322, clause 6.2.1.5 Figure 6.2.1.5-1a);
5 octets
D_C
B1_Type
0 - Control PDU
1 - Data PDU
ReSeg
B1_Type
0 - AMD PDU
1 - AMD PDU segment
Poll
B1_Type
0 - Status report not requested
1 - Status report is requested
FramingInfo
RLC_FramingInfo_Type
2 bit FI
Extension
B1_Type
1 bit E
LastSegmentFl B1_Type
0 - Last byte of the AMD PDU segment does not correspond to
ag
the last byte of an AMD PDU
1 - Last byte of the AMD PDU segment corresponds to the last
byte of an AMD PDU
Reserved
B1_Type
1 reserved bit
SN_Ext
B16_Type
Sequence number
RLC_AMD_Header_SegmentPart_Type
TTCN-3 Record Type
Name
RLC_AMD_Header_SegmentPart_Type
Comment
AMD PDU segment related info in PDU header acc. TS 36.322, clause 6.2.1.5
LastSegmentFl B1_Type
0 - Last byte of the AMD PDU segment does not correspond to
ag
the last byte of an AMD PDU
1 - Last byte of the AMD PDU segment corresponds to the last
byte of an AMD PDU
SegOffset
B15_Type
The SO field indicates the position of the AMD PDU segment in
bytes within the original AMD PDU.
Specifically, the SO field indicates the position within the Data
field of the original AMD PDU
to which the first byte of the Data field of the AMD PDU segment
corresponds to.
RLC_AMD_Header_SegmentPartExt_Type
TTCN-3 Record Type
Name
RLC_AMD_Header_SegmentPartExt_Type
Comment
AMD PDU segment related info in PDU header acc. TS 36.322, clause 6.2.1.5
SegOffset
B16_Type
The SO field indicates the position of the AMD PDU segment in
bytes within the original AMD PDU.
Specifically, the SO field indicates the position within the Data
field of the original AMD PDU
to which the first byte of the Data field of the AMD PDU segment
corresponds to.
RLC_AMD_Header_Type
TTCN-3 Record Type
Name
RLC_AMD_Header_Type
Comment
FixPart
RLC_AMD_Header_FixPart
_Type
SegmentPart
RLC_AMD_Header_Segme
ntPart_Type
FlexPart
RLC_PDU_Header_FlexPa
rt_Type
opt
present in case of AMD Seg PDU only
opt
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
345
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC_AMD_HeaderExt_Type
TTCN-3 Record Type
Name
RLC_AMD_HeaderExt_Type
Comment
FixPartExt
RLC_AMD_Header_FixPart
Ext_Type
FlexPart
RLC_PDU_Header_FlexPa
opt
rt_Type
RLC_AMD_HeaderSegExt_Type
TTCN-3 Record Type
Name
RLC_AMD_HeaderSegExt_Type
Comment
FixPartSegExt
RLC_AMD_Header_FixPart
SegExt_Type
SegmentPart
RLC_AMD_Header_Segme opt
ntPartExt_Type
FlexPart
RLC_PDU_Header_FlexPa
opt
rt_Type
present in case of AMD Seg PDU only
RLC_AMD_PDU_Type
TTCN-3 Record Type
Name
RLC_AMD_PDU_Type
Comment
Header
RLC_AMD_Header_Type
Data
RLC_DataFieldList_Type
RLC_AMD_PDU_Ext_Type
TTCN-3 Record Type
Name
RLC_AMD_PDU_Ext_Type
Comment
HeaderExt
RLC_AMD_HeaderExt_Typ
e
Data
RLC_DataFieldList_Type
RLC_AMD_PDU_SegExt_Type
TTCN-3 Record Type
Name
RLC_AMD_PDU_SegExt_Type
Comment
HeaderSegExt
RLC_AMD_HeaderSegExt_
Type
Data
RLC_DataFieldList_Type
D.3.1.2.5
AM_Status
AM Status PDU (TS 36.322, clause 6.2.1.6)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
346
AM_Status: Basic Type Definitions
TTCN-3 Basic Types
RLC_Status_Padding_Ty
pe
bitstring length (1..7)
NOTE:
in TTCN-3 length restriction cannot be done
inline in record definition
=> explicit type definition necessary
RLC_Status_ACK_Type
TTCN-3 Record Type
Name
RLC_Status_ACK_Type
Comment
ACK_SN
B10_Type
Extn1
B1_Type
Acknowledgement SN (TS 36.322, clause 6.2.2.14)
0 - a set of NACK_SN, E1 and E2 does not follow.
1 - a set of NACK_SN, E1 and E2 follows.
RLC_Status_ACK_Ext_Type
TTCN-3 Record Type
Name
RLC_Status_ACK_Ext_Type
Comment
ACK_SN_Ext
B16_Type
Extn1
B1_Type
Acknowledgement SN (TS 36.322, clause 6.2.2.14)
0 - a set of NACK_SN, E1 and E2 does not follow.
1 - a set of NACK_SN, E1 and E2 follows.
RLC_Status_SegOffset_Type
TTCN-3 Record Type
Name
RLC_Status_SegOffset_Type
Comment
Start
B15_Type
End
B15_Type
SOstart field indicates the position of the first byte of the portion
of the AMD PDU in bytes within the Data field of the AMD PDU
SOend field indicates the position of the last byte of the portion of
the AMD PDU in bytes
within the Data field of the AMD PDU. The special SOend value
'111111111111111'B is used to
indicate that the missing portion of the AMD PDU includes all
bytes to the last byte of the AMD PDU
RLC_Status_SegOffset_Ext_Type
TTCN-3 Record Type
Name
RLC_Status_SegOffset_Ext_Type
Comment
Start
B16_Type
SOstart field indicates the position of the first byte of the portion
of the AMD PDU in bytes within the Data field of the AMD PDU
End
B16_Type
SOend field indicates the position of the last byte of the portion of
the AMD PDU in bytes
within the Data field of the AMD PDU. The special SOend value
'111111111111111'B is used to
indicate that the missing portion of the AMD PDU includes all
bytes to the last byte of the AMD PDU
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
347
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC_Status_NACK_Type
TTCN-3 Record Type
Name
RLC_Status_NACK_Type
Comment
NACK_SN
B10_Type
Extn1
B1_Type
Extn2
B1_Type
SO
RLC_Status_SegOffset_Ty
pe
0 - A set of NACK_SN, E1 and E2 does not follow.
1 - A set of NACK_SN, E1 and E2 follows.
0 - A set of SOstart and SOend does not follow for this
NACK_SN.
1 - A set of SOstart and SOend follows for this NACK_SN.
opt
RLC_Status_NACK_List_Type
TTCN-3 Record of Type
Name
RLC_Status_NACK_List_Type
Comment
record of RLC_Status_NACK_Type
RLC_Status_NACK_Ext_Type
TTCN-3 Record Type
Name
RLC_Status_NACK_Ext_Type
Comment
NACK_SN_Ext B16_Type
Extn1
B1_Type
Extn2
B1_Type
SO
RLC_Status_SegOffset_Ext
_Type
0 - A set of NACK_SN, E1 and E2 does not follow.
1 - A set of NACK_SN, E1 and E2 follows.
0 - A set of SOstart and SOend does not follow for this
NACK_SN.
1 - A set of SOstart and SOend follows for this NACK_SN.
opt
RLC_Status_NACK_Ext_List_Type
TTCN-3 Record of Type
Name
RLC_Status_NACK_Ext_List_Type
Comment
record of RLC_Status_NACK_Ext_Type
RLC_AM_StatusPDU_Type
TTCN-3 Record Type
Name
RLC_AM_StatusPDU_Type
Comment
RLC STATUS PDU (TS 36.322, clause 6.2.1.6)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
CP_Type
B3_Type
000 - STATUS PDU
001..111 - Reserved (=> PDU to be discarded by the receiving
entity for this release of the protocol)
Ack
RLC_Status_ACK_Type
ACK_SN and E1 bit
NackList
RLC_Status_NACK_List_T
opt presence depends on Extn1 bit of Ack filed
ype
(RLC_Status_ACK_Type)
Padding
RLC_Status_Padding_Type opt 1..7 bit padding if needed for octet alignment
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
348
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLC_AM_StatusPDU_Ext_Type
TTCN-3 Record Type
Name
RLC_AM_StatusPDU_Ext_Type
Comment
RLC STATUS PDU (TS 36.322, clause 6.2.1.6)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
CP_Type
B3_Type
000 - STATUS PDU
001..111 - Reserved (=> PDU to be discarded by the receiving
entity for this release of the protocol)
Ack_Ext
RLC_Status_ACK_Ext_Typ
ACK_SN and E1 bit
e
Nack_Ext_List
RLC_Status_NACK_Ext_Li
opt presence depends on Extn1 bit of Ack field
st_Type
(RLC_Status_ACK_Type)
Padding
RLC_Status_Padding_Type opt 1..7 bit padding if needed for octet alignment
RLC_PDU: Basic Type Definitions
TTCN-3 Basic Types
RLC_SDU_Type
octetstring
RLC_PDU_Type
TTCN-3 Union Type
Name
RLC_PDU_Type
Comment
TMD
RLC_TMD_PDU_Type
UMD
RLC_UMD_PDU_Type
AMD
RLC_AMD_PDU_Type
AMD_Ext
RLC_AMD_PDU_Ext_Type
AMD_SegExt
RLC_AMD_PDU_SegExt_Type
Status
RLC_AM_StatusPDU_Type
Status_Ext
RLC_AM_StatusPDU_Ext_Type
RLC_PDUList_Type
TTCN-3 Record of Type
Name
RLC_PDUList_Type
Comment
record of RLC_PDU_Type
RLC_SDUList_Type
TTCN-3 Record of Type
Name
RLC_SDUList_Type
Comment
record of RLC_SDU_Type
D.3.1.3 PDCP
PDCP user plane SDU and PDU definitions
NOTE:
To allow direct encoding the definition for PDCP Data PDU is split into data PDU with long/short sequence number
PDCP: Basic Type Definitions
TTCN-3 Basic Types
PDCP_SDU_Type
octetstring
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
349
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_SDUList_Type
TTCN-3 Record of Type
Name
PDCP_SDUList_Type
Comment
record of PDCP_SDU_Type
PDCP_DataPdu_LongSN_Type
TTCN-3 Record Type
Name
PDCP_DataPdu_LongSN_Type
Comment
User plane PDCP Data PDU with long sequence number (TS 36.323, clause 6.2.3)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
Reserved
B3_Type
3 reserved bits
SequenceNum
B12_Type
12 bit sequence number
ber
SDU
PDCP_SDU_Type
content (octetstring)
PDCP_DataPdu_ShortSN_Type
TTCN-3 Record Type
Name
PDCP_DataPdu_ShortSN_Type
Comment
User plane PDCP Data PDU with short sequence number (TS 36.323, clause 6.2.4)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
SequenceNum
B7_Type
7 bit sequence number
ber
SDU
PDCP_SDU_Type
content (octetstring)
PDCP_DataPdu_ExtSN_Type
TTCN-3 Record Type
Name
PDCP_DataPdu_ExtSN_Type
Comment
User plane PDCP Data PDU with extended sequence number (TS 36.323, clause 6.2.9)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
SequenceNum
B15_Type
15 bit sequence number
ber
SDU
PDCP_SDU_Type
content (octetstring)
PDCP_DataPdu_18bitSN_Type
TTCN-3 Record Type
Name
PDCP_DataPdu_18bitSN_Type
Comment
User plane PDCP Data PDU with 18 bit sequence number (TS 36.323, clause 6.2.11)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PollingBit
B1_Type
1 - when eNB triggers a PDCP status report or LWA status report
Reserved
B4_Type
4 reserved bits
SequenceNum
B18_Type
18 bit sequence number
ber
SDU
PDCP_SDU_Type
content (octetstring)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
350
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_DataPdu_SLRB_Type
TTCN-3 Record Type
Name
PDCP_DataPdu_SLRB_Type
Comment
User plane PDCP Data PDU for SLRB (TS 36.323, clause 6.2.10.1)
SDU_Type
B3_Type
000 - IP
001 - ARP
010 - PC5 Signaling
011 - 111 reserved
PGK_Index
B5_Type
5 LSBs of PGK Identity (TS 33.303, clause 6.2.3)
PTK_Identity
B16_Type
PTK Identity (TS 33.303, clause 6.2.3)
SequenceNum
B16_Type
16 bit sequence number
ber
SDU
PDCP_SDU_Type
content (octetstring)
PDCP_DataPdu_SLRB_1to1_Type
TTCN-3 Record Type
Name
PDCP_DataPdu_SLRB_1to1_Type
Comment
User plane PDCP Data PDU for SLRB (TS 36.323, clause 6.2.10.2)
SDU_Type
B3_Type
000 - IP
001 - ARP
010 - PC5 Signaling
011 - 111 reserved
Reserved
B5_Type
5 reserved bits
KD_sess_ID
B16_Type
KD_sess Identity (TS 33.303, clause 6.5.3.1)
SequenceNum
B16_Type
16 bit sequence number
ber
SDU
PDCP_SDU_Type
content (octetstring)
MAC_I
O4_Type
MAC-I
PDCP_Ctrl_ROHC_FB_PDU_Type
TTCN-3 Record Type
Name
PDCP_Ctrl_ROHC_FB_PDU_Type
Comment
PDCP Control PDU for interspersed ROHC feedback packet (TS 36.323, clause 6.2.5)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PDU_Type
B3_Type
000 - PDCP status report
001 - Header Compression Feedback Information
010 - LWA status report
011..111 - reserved
Reserved
B4_Type
ROHC_FB
octetstring
Contains one ROHC packet with only feedback, i.e. a ROHC
packet that is not associated with a PDCP
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
351
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_Ctrl_StatusReport_Type
TTCN-3 Record Type
Name
PDCP_Ctrl_StatusReport_Type
Comment
PDCP Control PDU for PDCP status report (TS 36.323, clause 6.2.6)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PDU_Type
B3_Type
000 - PDCP status report
001 - Header Compression Feedback Information
010 - LWA status report
011..111 - reserved
FMS
B12_Type
PDCP SN of the first missing PDCP SDU.
Bitmap
octetstring
opt The MSB of the first octet of the type "Bitmap" indicates whether
or not the PDCP SDU with the SN (FMS + 1) modulo 4096 has
been received and, optionally decompressed correctly.
0PDCP SDU with PDCP SN = (FMS + bit position) modulo 4096 is
missing in the receiver.
The bit position of Nth bit in the Bitmap is N, i.e. the bit position of
the first bit in the Bitmap is 1.
1PDCP SDU with PDCP SN = (FMS + bit position) modulo 4096
does not need to be retransmitted.
The bit position of Nth bit in the Bitmap is N, i.e. the bit position of
the first bit in the Bitmap is 1.
PDCP_Ctrl_StatusReportExt_Type
TTCN-3 Record Type
Name
PDCP_Ctrl_StatusReportExt_Type
Comment
PDCP Control PDU for PDCP status report using a 15 bit SN (TS 36.323, clause 6.2.6)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PDU_Type
B3_Type
000 - PDCP status report
001 - Header Compression Feedback Information
010 - LWA status report
011..111 - reserved
Reserved
B5_Type
5 reserved bits
FMS_Ext
B15_Type
PDCP SN of the first missing PDCP SDU.
Bitmap
octetstring
opt The MSB of the first octet of the type "Bitmap" indicates whether
or not the PDCP SDU with the SN (FMS + 1) modulo
(Maximum_PDCP_SN + 1) has been received and,
optionally decompressed correctly.
0PDCP SDU with PDCP SN = (FMS + bit position) modulo
(Maximum_PDCP_SN + 1) is missing in the receiver.
The bit position of Nth bit in the Bitmap is N, i.e. the bit position of
the first bit in the Bitmap is 1.
1PDCP SDU with PDCP SN = (FMS + bit position) modulo
(Maximum_PDCP_SN + 1) does not need to be retransmitted.
The bit position of Nth bit in the Bitmap is N, i.e. the bit position of
the first bit in the Bitmap is 1.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
352
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_Ctrl_StatusReport_18bitSN_Type
TTCN-3 Record Type
Name
PDCP_Ctrl_StatusReport_18bitSN_Type
Comment
PDCP Control PDU for PDCP status report using a 18 bit SN (TS 36.323, clause 6.2.6)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PDU_Type
B3_Type
000 - PDCP status report
001 - Header Compression Feedback Information
010 - LWA status report
011..111 - reserved
Reserved
B2_Type
2 reserved bits
FMS_18bitSN
B18_Type
PDCP SN of the first missing PDCP SDU.
Bitmap
octetstring
opt The MSB of the first octet of the type "Bitmap" indicates whether
or not the PDCP SDU with the SN (FMS + 1) modulo
(Maximum_PDCP_SN + 1) has been received and,
optionally decompressed correctly.
0PDCP SDU with PDCP SN = (FMS + bit position) modulo
(Maximum_PDCP_SN + 1) is missing in the receiver.
The bit position of Nth bit in the Bitmap is N, i.e. the bit position of
the first bit in the Bitmap is 1.
1PDCP SDU with PDCP SN = (FMS + bit position) modulo
(Maximum_PDCP_SN + 1) does not need to be retransmitted.
The bit position of Nth bit in the Bitmap is N, i.e. the bit position of
the first bit in the Bitmap is 1.
PDCP_Ctrl_LWA_StatusReport_Type
TTCN-3 Record Type
Name
PDCP_Ctrl_LWA_StatusReport_Type
Comment
PDCP Control PDU for LWA status report (TS 36.323, clause 6.2.12)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PDU_Type
B3_Type
000 - PDCP status report
001 - Header Compression Feedback Information
010 - LWA status report
011..111 - reserved
FMS
B12_Type
PDCP SN of the first missing PDCP SDU.
HRW
B12_Type
PDCP SN of the PDCP SDU received on WLAN with highest
associated PDCP COUNT value.
NMP
B12_Type
Number of Missing PDCP PDUs with PDCP SNs below HRW
starting from and including FMS.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
353
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_Ctrl_LWA_StatusReportExt_Type
TTCN-3 Record Type
Name
PDCP_Ctrl_LWA_StatusReportExt_Type
Comment
PDCP Control PDU for LWA status report (TS 36.323, clause 6.2.12)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PDU_Type
B3_Type
000 - PDCP status report
001 - Header Compression Feedback Information
010 - LWA status report
011..111 - reserved
Reserved
B5_Type
5 reserved bits
FMS_Ext
B15_Type
PDCP SN of the first missing PDCP SDU.
Reserved2
B1_Type
1 reserved bit
HRW_Ext
B15_Type
PDCP SN of the PDCP SDU received on WLAN with highest
associated PDCP COUNT value.
Reserved3
B1_Type
1 reserved bit
NMP_Ext
B15_Type
Number of Missing PDCP PDUs with PDCP SNs below HRW
starting from and including FMS.
PDCP_Ctrl_LWA_StatusReport_18bitSN_Type
TTCN-3 Record Type
Name
PDCP_Ctrl_LWA_StatusReport_18bitSN_Type
Comment
PDCP Control PDU for LWA status report (TS 36.323, clause 6.2.12)
D_C
B1_Type
0 - Control PDU
1 - Data PDU
PDU_Type
B3_Type
000 - PDCP status report
001 - Header Compression Feedback Information
010 - LWA status report
011..111 - reserved
Reserved
B2_Type
2 reserved bits
FMS_18bitSN
B18_Type
PDCP SN of the first missing PDCP SDU.
HRW_18bitSN
B18_Type
PDCP SN of the PDCP SDU received on WLAN with highest
associated PDCP COUNT value.
Reserved2
B4_Type
4 reserved bits
NMP_18bitSN
B18_Type
Number of Missing PDCP PDUs with PDCP SNs below HRW
starting from and including FMS.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
354
ETSI TS 136 523-3 V13.2.0 (2017-03)
PDCP_PDU_Type
TTCN-3 Union Type
Name
PDCP_PDU_Type
Comment
DataLongSN
PDCP_DataPdu_LongSN_Type
DataShortSN
PDCP_DataPdu_ShortSN_Type
DataExtSN
PDCP_DataPdu_ExtSN_Type
Data_18bitSN
PDCP_DataPdu_18bitSN_Type
RohcFeedback PDCP_Ctrl_ROHC_FB_PDU_Typ
e
StatusReport
PDCP_Ctrl_StatusReport_Type
StatusReportEx PDCP_Ctrl_StatusReportExt_Typ
e
t
StatusReport_1 PDCP_Ctrl_StatusReport_18bitS
N_Type
8bitSN
LWA_StatusRe PDCP_Ctrl_LWA_StatusReport_T
ype
port
LWA_StatusRe PDCP_Ctrl_LWA_StatusReportEx
t_Type
portExt
LWA_StatusRe PDCP_Ctrl_LWA_StatusReport_1
8bitSN_Type
port_18bitSN
DataSLRB
PDCP_DataPdu_SLRB_Type
DataSLRB_1to
PDCP_DataPdu_SLRB_1to1_Typ
e
1
user plane PDCP data PDU with 12 Bit Seq Number
user plane PDCP data PDU with 7 Bit Seq Number
user plane PDCP data PDU with 15 Bit Seq Number
user plane PDCP data PDU with 18 Bit Seq Number
PDCP Control PDU for interspersed ROHC feedback packet
PDCP Control PDU for PDCP status report
PDCP Control PDU for PDCP status report using a 15 bit SN
PDCP Control PDU for PDCP status report using a 18 bit SN
PDCP Control PDU for LWA status report
PDCP Control PDU for LWA status report using a 15 bit SN
PDCP Control PDU for LWA status report using a 18 bit SN
user plane PDCP Data PDU for SLRB
user plane PDCP Data PDU for SLRB one to one communication
PDCP_PDUList_Type
TTCN-3 Record of Type
Name
PDCP_PDUList_Type
Comment
record of PDCP_PDU_Type
D.3.2
DRB_Primitive_Definitions
Primitive definitions to send/receive data PDUs over DRB's
D.3.2.1 DRB_Common
L2DataList_Type
TTCN-3 Union Type
Name
L2DataList_Type
Comment
MAC:
acc. to rel-8 protocols there is not more than one MAC PDU per TTI;
any MAC PDU is completely included in one subframe
RLC:
one or more RLC PDUs per TTI
(e.g. RLC Data + Status PDU on a logical channel;
more than one RLC Data PDU in one MAC PDU is valid too)
any RLC PDU is completely included in one subframe
PDCP:
one or more PDUs per TTI; one PDCP PDU may be included in more than one subframe
MacPdu
MAC_PDUList_Type
SS configuration: RLC TM mode, MAC no header removal
(PDCP is not configured)
RlcPdu
RLC_PDUList_Type
SS configuration: RLC TM mode, MAC header removal (PDCP is
not configured)
PdcpPdu
PDCP_PDUList_Type
SS configuration: RLC AM/UM mode, PDCP no header removal
PdcpSdu
PDCP_SDUList_Type
SS configuration: RLC AM/UM mode, PDCP header removal
RlcSdu
RLC_SDUList_Type
SS configuration: RLC UM mode with no PDCP, for example
MRB
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
355
ETSI TS 136 523-3 V13.2.0 (2017-03)
HarqProcessAssignment_Type
TTCN-3 Union Type
Name
HarqProcessAssignment_Type
Comment
in DL the HARQ process id may be specified by the test case or automatically assigned by SS
Id
HarqProcessId_Type
HARQ process as specified by the test case
NOTE1:
the scope of this type is only for data being sent in one TTI;
if data needs more than one TTI the HarqProcessId is undefined
for the 2nd TTI onward what shall be handled as an error at the
SS; SS may send a SYSTEM_IND indicating an error in this
case;
NOTE2:
The initial value of the NDI shall be the same for all HARQ
processes and cells
Automatic
Null_Type
HARQ process id automatically assigned by SS
D.3.2.2 Downlink
DRB_DataPerSubframe_DL_Type
TTCN-3 Record Type
Name
DRB_DataPerSubframe_DL_Type
Comment
common definition for one or several PDUs/SDUs;
in EUTRA the DL data is sent in the subframe given by the subframe offset;
in NBIOT the DL transmission is scheduled in the search space candidate given by "SubframeOffset"
for NBIOT it specifies the
NOTE 1:
For MAC and RLC PDUs a single PDU is always sent in one subframe;
SS shall raise an error indication (using SYSTEM_IND) when that is not possible
NOTE 2:
For PDCP the data may be spread over more than one subframe (segmented by the RLC);
the TTCN implemetation is responsible to calculate appropriate offsets accordingly;
the exact timing depends on (and is exactly specified by) configuration of the DL scheduling;
SS shall raise an error when there is any conflict
SubframeOffset integer
EUTRA:
Subframe offset relative to the absolute timing information given
in the common part of the ASP;
NBIOT:
Offset of the search space candidate relative to the (default)
search space candidate as configured for the NPDCCH UE
specific search space;
the search space candidate is in the next search space starting
at or after the point in time given by the timing information of the
common part of the ASP
NOTE 1:
Notes:
Acc. to TS 36.523-3, clause 7.3.3 in case of TDD or half-duplex
configuration only subframes available for DL are taken into
consideration
NOTE 2:
if a PDCP PDU or SDU takes more than one subframe,
SubframeOffset specifies the first TTI
HarqProcess
HarqProcessAssignment_T
opt HARQ process to be used: specific value (0..7) or automatically
ype
assigned by SS;
in automatic mode SS chooses HARQ process out of the set
configured by CcchDcchDtchConfigDL_Type.HarqProcessConfig
NOTE 1:
for PDCP SDUs or PDUs automatic mode shall be used;
otherwise SS shall raise an error
NOTE 2:
for NB-IoT the HarqProcess shall be omitted by TTCN and
ignored by the SS
PduSduList
L2DataList_Type
list of PDUs/SDUs to be sent in one TTI
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
356
ETSI TS 136 523-3 V13.2.0 (2017-03)
DRB_DataPerSubframeList_DL_Type
TTCN-3 Record of Type
Name
DRB_DataPerSubframeList_DL_Type
Comment
list of user plane data to be sent in sub-frames given by the SubframeOffset in the single
elements of the list;
Timing:
the start time for the whole sequence is given by the timing info of the ASP (common
information);
the timing for the respective data pdus is given by the SubframeOffset relative to the common
timing info;
design consideration:
repetitions of this sequence are not foreseen
(in which case the subframe offset could not be related to the timing info of the ASP)
record of DRB_DataPerSubframe_DL_Type
L2Data_Request_Type
TTCN-3 Record Type
Name
L2Data_Request_Type
Comment
NOTE: formal type definition to allow later enhancements;
L2Data_Request_Type defines a sequence of subframes in which data shall be sent
SubframeDataL DRB_DataPerSubframeList
_DL_Type
ist
D.3.2.3 Uplink
DRB_DataPerSubframe_UL_Type
TTCN-3 Record Type
Name
DRB_DataPerSubframe_UL_Type
Comment
common definition for one or several PDUs/SDUs being received in one subframe
or to receive one PDCP PDU or SDU being spread over more than one TTI;
NOTE:
There is a fix relation between HARQ process id and subframe in UL
=> it is not necessary to include HARQ process id for UL data
PduSduList
L2DataList_Type
list of PDUs/SDUs being received in one TTI;
elements of the list appear in the same order as the PDUs/SDUs
in the MAC PDU;
for PDCP when a PDU or SDU takes more than one TTI the list
only contains this PDU or SDU
NoOfTTIs
integer
in case of PDCP:
number of TTIs the SDU or PDU has taken
NOTE 1: for the time being the NoOfTTIs is not checked by
TTCN-3 and may be set to 1 by SS;
NOTE 2: the timing info in common part of the ASP refers to the
last TTI
NOTE 3: when NoOfTTIs > 1 => PduSduList shall only contain
one PDCP PDU or SDU
in case of MAC or RLC PDUs:
NoOfTTIs shall always be 1
(acc. to TS 36.321 MAC is not doing segmentation of RLC PDUs
and acc. to TS 36.322, clause 6.2.2.2 the maximum RLC data is
calculated to fit into a MAC PDU and RLC does segmentation
accordingly)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
357
ETSI TS 136 523-3 V13.2.0 (2017-03)
L2Data_Indication_Type
TTCN-3 Record Type
Name
L2Data_Indication_Type
Comment
NOTE: formal type definition to allow later enhancements;
L2Data_Indication_Type defines data being received in a single subframe
i.e. PDUs of subsequent TTIs are indicated in separated ASPs
SubframeData
DRB_DataPerSubframe_U
L_Type
D.4
EUTRA_ASP_SrbDefs
D.4.1
SRB_DATA_ASPs
ASP Definitions to send/receive peer-to-peer messages on SRBs
C_Plane_Request_Type
TTCN-3 Record Type
Name
C_Plane_Request_Type
Comment
RRC and/or NAS PDU to be send to the UE;
Note: it may be necessary to allow more than one NAS PDU (-> "record of")
Rrc
RRC_MSG_Request_Type
opt omit: NAS message shall be present; NAS message shall be
sent in DLInformationTransfer
present: if NAS message is present also, (piggybacked) NAS
PDU shall be security protected
(if necessary) and inserted in RRC PDU's
DedicatedInfoNAS
Nas
NAS_MSG_RequestList_Ty opt omit: RRC message shall be present; RRC message does not
pe
contain (piggybacked) NAS PDU
present: if RRC message is omitted => NAS message shall be
sent embedded in DLInformationTransfer
if RRC message is present => NAS message is
piggybacked in RRC message
in case of RRC message is sent on CCCH, NAS message shall
be omitted
NOTE:
acc. DEC 08 ASN.1 RRCConnectionReconfiguration may
contain DedicatedInfoNAS several times
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
358
ETSI TS 136 523-3 V13.2.0 (2017-03)
C_Plane_Indication_Type
TTCN-3 Record Type
Name
C_Plane_Indication_Type
Comment
RRC and/or NAS PDU to be received from the UE;
Note: it may be necessary to allow more than one NAS PDU (-> "record of")
Rrc
RRC_MSG_Indication_Typ
opt omit: NAS message shall be present; NAS message is
e
received in ULInformationTransfer
present: if NAS message is present also, DedicatedInfoNAS
contains unstructured and
ciphered NAS message and the NAS message is the
deciphered message in structured format
Nas
NAS_MSG_IndicationList_T opt omit: RRC message shall be present; RRC message does not
ype
contain (piggybacked) NAS PDU
present: if RRC message is omitted => NAS message has been
received in ULInformationTransfer
if RRC message is present => NAS message has been
piggybacked in RRC message
NOTE:
even though currently (DEC 08 ASN.1) there is no RRC PDU in
UL containing more than one
DedicatedInfoNAS we provide a list to allow extendability
SRB_COMMON_REQ
TTCN-3 Record Type
Name
SRB_COMMON_REQ
Comment
common ASP to send PDUs to SRB0, SRB1 or SRB2
Common
ReqAspCommonPart_Type
CellId
identifier of the cell
RoutingInfo
SRB0, SRB1, SRB2
TimingInfo
Now in normal cases;
For latency tests TimingInfo can be set to the
SFN/subframe
in which the RRC messages shall be sent out (in this
case and
if the RRC PDU is too long to be sent in one TTI
the TimingInfo corresponds to the first TTI)
ControlInfo
CnfFlag:=false;
FollowOnFlag
true: Indicates that the message(s) to be sent on the same TTI
will follow
NOTE 1: When FollowOnFlag is true, TimingInfo shall
always be "Now". Otherwise SS shall produce an error
NOTE 2: the follow on flag applies only for messages of
the same SRB
false: Indicates that no more message(s) will follow
Signalling
C_Plane_Request_Type
SRB_COMMON_IND
TTCN-3 Record Type
Name
SRB_COMMON_IND
Comment
common ASP to receive PDUs from SRB0, SRB1 or SRB2
Common
IndAspCommonPart_Type
CellId
identifier of the cell
RoutingInfo
SRB0, SRB1, SRB2
TimingInfo
time when message has been received
(as received from the SS by the NAS emulator)
Signalling
C_Plane_Indication_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.4.2
359
ETSI TS 136 523-3 V13.2.0 (2017-03)
Port_Definitions
EUTRA_SRB_PORT
TTCN-3 Port Type
Name
EUTRA_SRB_PORT
Comment
EUTRA PTC: Port for Sending/Receiving data on SRBs
out
SRB_COMMON_REQ
in
SRB_COMMON_IND
NASEMU_EUTRA_SRB_PORT
TTCN-3 Port Type
Name
NASEMU_EUTRA_SRB_PORT
Comment
NASEMU PTC: Port for Sending/Receiving data on SRBs (interface to EUTRA PTC)
out
SRB_COMMON_IND
in
SRB_COMMON_REQ
D.5
IP_ASP_TypeDefs
General Notes:
NOTE 1:
In general the handling of IP data shall be independent from the RAT being used on lower layers.
NOTE 2:
It shall be possible for SS implementation to reuse existing IP stack implementations in the system adaptor;
therefore the well-known concept of socket programming shall be supported
(regardless of whether those are used in the system adaptor implementation or not)
NOTE 3:
Since in general at the network side there are several different IP addresses the SS needs to simulate more than one IP
address;
that can be based on a concept of multiple virtual network adaptors
NOTE 4:
There is no easy way to control the routing of IP data for an IP connection from above the IP stack
i.e. there are no parameters at the socket interface to determine e.g. cell id and DRB id
=> another independent logical entity (DRB-MUX) is needed below the IP stack which is responsible to control the
routing of IP packets from/to DRBs in different cells of different RATs
Reference:
An introduction to socket programming can be found in
UNIX Network Programming Volume 1, Third Edition: The Sockets Networking API
by W. Richard Stevens, Bill Fenner, Andrew M. Rudoff
D.5.1
IP_Common
IP_Common: Basic Type Definitions
TTCN-3 Basic Types
PortNumber_Type
UInt16_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
360
ETSI TS 136 523-3 V13.2.0 (2017-03)
IPv4_AddrInfo_Type
TTCN-3 Record Type
Name
IPv4_AddrInfo_Type
Comment
IPv4 specific info of the socket addr (AF_INET)
Addr
charstring
IP Address as string (IP v4 dot notation) to be converted to 32-bit
unsigned integer
IPv6_AddrInfo_Type
TTCN-3 Record Type
Name
IPv6_AddrInfo_Type
Comment
IPv6 specific info of the socket addr (AF_INET6);
NOTE: sin6_flowinfo can be ignored and set to 0
Addr
charstring
to be converted to sin6_addr
ScopeId
UInt32_Type
opt sin6_scope_id
in general an IPv6 address is like "fe80::1%eth0" with eth0 being
the network adaptor mapped to a scope id (Unix)
assumption:
for UE conformance testing it is not necessary to distinguish
different scopes and the scope id in general can be determined
by the system adaptor => omit
IP_AddrInfo_Type
TTCN-3 Union Type
Name
IP_AddrInfo_Type
Comment
V4
IPv4_AddrInfo_Type
V6
IPv6_AddrInfo_Type
IP_Socket_Type
TTCN-3 Record Type
Name
IP_Socket_Type
Comment
Socket
IpAddr
IP_AddrInfo_Type
Port
PortNumber_Type
opt
opt
IP address
port number
InternetProtocol_Type
TTCN-3 Enumerated Type
Name
InternetProtocol_Type
Comment
udp
tcp
icmp
icmpv6
IP_Connection_Type
TTCN-3 Record Type
Name
IP_Connection_Type
Comment
A connection between peer-to-peer entities is unambiguously defined by the protocol
(udp/tcp/icmp/icmpv4), the local socket and the remote socket
Protocol
InternetProtocol_Type
Local
IP_Socket_Type
opt
Remote
IP_Socket_Type
opt
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.5.2
361
ETSI TS 136 523-3 V13.2.0 (2017-03)
IP_Config
Configuration of the routing table managed be the system adaptor's DRB-MUX:
foreach IP connection it is specified which
- RAT
- Cell
- DRB
to be used.
The IP connection does not need to be fully specified depending on the role SS plays (e.g. in case of a server role the
port number of the remote side is not known in advance).
The configurations of DRBs within the same cell shall be mutual exclusive.
With the configuration of the IP routing the DRB is configured either in IP or in raw mode:
either there are entries for the DRB in the routing table (IP mode) or not (raw mode)
=> It is not necessary to reconfigure this for the respective RAT.
Behaviour of the DRB-MUX in UL:
- SS gets data packet from the lower layers (e.g. PDCP SDU)
- SS checks whether there is any IP connection configured for this DRB (identified by {RAT, CellId, DrbId})
if YES => packet is routed to the IP stack (IP mode)
if NO => packet is handed over to the DRB port (raw mode)
NOTE 1:
If there is any entry for a DRB in the routing table this DRB is considered as being in IP mode and all UL IP packets are
sent to the IP stack regardless of whether their addresses match the DRB's routing entries or not (in general 'unknown'
packets are discarded by the IP stack)
=> a DRB can be either in IP or in raw mode
NOTE 2:
=> The SS does not need to evaluate any IP headers to decide whether data shall be routed to the DRB port or to the IP
stack (i.e. there is no conflict with unstructured loopback data)
Behaviour of the DRB-MUX in DL:
- SS gets IP packets from the IP stack for an IP connection
- SS compares the IP connection (protocol, local/remote IP Addr) against the IP routing table and
checks whether the corresponding protocol stack is configured at the lower layers =>
1. no match:
no entry in the routing table fits to the address in the IP packet
or the corresponding RB is not configured
=> SS shall raise an error (DRBMUX_COMMON_IND_CNF.Error)
2. one match:
There is exactly one possibility to route the IP packet
=> SS shall send the packet to this RB
3. several matches:
There are more than one DRBs, cells or RATs to which the packet may be routed
=> SS shall raise an error if there is more than one DRB in one cell matching;
if the DRBs belong to different cells or RATs SS shall send the data to all of them
(whether this may occur in test cases is FFS)
General notes:
NOTE 1:
SS may use the information of the routing table to determine which network adaptors it needs to simulate
(implementation dependent);
in general there will be more than one IP address at the network side.
NOTE 2:
In general the routing table is a simplified DL TFT implementation
NOTE 3:
When the routing table is empty all DRBs are in raw mode; this shall be the initial condition at the DRB-MUX;
=> for L2 testing in general (and apart from the preamble) there is no need to use/configure the IP_PTC; the
configuration of the RAT specific U-plane stacks is not affected
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
362
ETSI TS 136 523-3 V13.2.0 (2017-03)
IP_DataMode_Type
TTCN-3 Enumerated Type
Name
IP_DataMode_Type
Comment
discard
loopbackRTP
loopbackRTCP
IPsecTunnel
IP_RoutingInfo_Type
TTCN-3 Record Type
Name
IP_RoutingInfo_Type
Comment
IpInfo
IP_Connection_Type
IP connection tuple: protocol, local socket, remote socket
depending on the role the SS plays the following information may
be provided
(informative; even less information can be sufficient):
1. TCP/UDP server
- local IP addr -- provided
- local port
-- provided
- remote IP addr -- omit
- remote port -- omit
2. TCP/UDP client
- local IP addr -- provided
(to inform SS about the local IP addr for this service)
- local port
-- omit;
for UDP a well-defined port may be defined
(protocol dependent, e.g. DHCP)
- remote IP addr -- provided
- remote port -- provided
3. ICMP (in general ICMP may be mapped only to a single DRB)
- local IP addr -- provided
(to inform SS about the local IP addr for this service)
- local port
-- n/a (shall be set to omit)
- remote IP addr -- omit
- remote port -- n/a (shall be set to omit)
NOTE:
In case of broadcasts in UL the broadcast address shall match
any local IP address;
in DL for broadcast services typically no remote IP address is
specified in the routing table
DRB
DataMode
IP_DrbInfo_Type
IP_DataMode_Type
opt
present when IP packets matching this entry shall be discarded
or be looped back to the UE as defined for RTP or RTCP
IP_RoutingTable_Type
TTCN-3 Record of Type
Name
IP_RoutingTable_Type
Comment
NOTE: configurations of DRBs within the same cell shall be mutual exclusive
record of IP_RoutingInfo_Type
D.5.3
IPsec_Config
IP_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_IPsec_SPI_Max
integer
4294967295
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
363
IPsec_Config: Basic Type Definitions
TTCN-3 Basic Types
IPsec_SPI_Type
integer (0..tsc_IPsec_SPI_Max)
security parameter index for IPsec;
According to RFC 2406, SPI values from 0 to
255 are reserved
IPsec_IntegrityAlgorithm_Type
TTCN-3 Enumerated Type
Name
IPsec_IntegrityAlgorithm_Type
Comment
hmac_md5_96
hmac_sha_1_96
IPsec_CipheringAlgorithm_Type
TTCN-3 Enumerated Type
Name
IPsec_CipheringAlgorithm_Type
Comment
des_ede3_cbc
aes_cbc
nociph
no ciphering
IPsec_SecurityKeys_Type
TTCN-3 Record Type
Name
IPsec_SecurityKeys_Type
Comment
to install the security keys
MD5_96Key
bitstring length (128)
SHA_1_96Key
bitstring length (160)
DES_EDE3_C
bitstring length (192)
BCKey
AES_CBCKey
bitstring length (128)
IPsec_SecurityAssociation_Type
TTCN-3 Record Type
Name
IPsec_SecurityAssociation_Type
Comment
single security association (SA);
for configuration of an SA at the SS all fields are mandatory;
to release an SA the optional information is omitted
SPI
IPsec_SPI_Type
SrcAddress
charstring
DestAddress
charstring
SrcPort
UInt16_Type
DestPort
UInt16_Type
IntegrityAlgorith IPsec_IntegrityAlgorithm_T
opt mandatory to set-up an SA
ype
m
CipheringAlgori IPsec_CipheringAlgorithm_
opt mandatory to set-up an SA
Type
thm
IPsec_SecurityAssociationList_Type
TTCN-3 Record of Type
Name
IPsec_SecurityAssociationList_Type
Comment
record of IPsec_SecurityAssociation_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
364
ETSI TS 136 523-3 V13.2.0 (2017-03)
IPsec_Configure_Type
TTCN-3 Record Type
Name
IPsec_Configure_Type
Comment
add new security associations; existing SAs are not affected
SA_List
IPsec_SecurityAssociationL
ist_Type
SecurityKeys
IPsec_SecurityKeys_Type
IPsec_Release_Type
TTCN-3 Record Type
Name
IPsec_Release_Type
Comment
release security associations;
NOTE:
in context with multiple PDNs it cannot be ensured that all SPIs are unique;
e.g. the UE may use the same SPI values in different PDNs in which case uniqueness cannot be
achieved
furthermore it depends on the system implementation how entries in the IPsec SAD and SPD are
administrated
=> to release SAs the SS gets the same information as for configuration but without the security
algorithms
SA_List
IPsec_SecurityAssociationL
ist_Type
D.5.4
IP_SocketHandling
Handling of IP data and IP connections
NOTE 1:
In general IP connections are distinguished by the tuple {protocol, local socket, remote socket};
this information is used at the interface between TTCN and the system adaptor.
It is up the system adaptor implementation to associate the IP connection with the internal socket (file descriptor;
implementation dependent)
NOTE 2:
In general the association of the IP connections to (internal) sockets and the routing table for the DRB mapping (as
configured with IP_RoutingTable_Type) are independent from each other
D.5.4.1 Socket_Common
IP_SockOpt_Type
TTCN-3 Union Type
Name
IP_SockOpt_Type
Comment
socket options acc. to the setsockopt system call (i.e. for level=SOL_SOCKET in case of Berkeley
socket API);
NOTE:
only options being relevant for a specific applications (upon a socket) are configured by TTCN
other options (e.g. SO_REUSEADDR) are out of TTCN and therefore a matter of system adaptor
implementation
SO_BROADCA boolean
set to true when IP broadcast messages shall be allowed for a
ST
port;
this is required e.g. in case of DHCP
IP_MTU_SIZE
integer
MTU size to be used for IP data;
NOTEs:
- Even though the MTU size is defined as socket option it shall
be the same for all sockets of a given interface (i.e. at least within
one PDN the MTU size shall be the same)
- in general a PIXIT is used as constant value for all sockets
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
365
IP_SockOptList_Type
TTCN-3 Record of Type
Name
IP_SockOptList_Type
Comment
record of IP_SockOpt_Type
IP_SocketError_Type
TTCN-3 Union Type
Name
IP_SocketError_Type
Comment
used to indicate errors related to sockets;
the IP_Connection shall contain as much address information as available at the system adaptor
InvalidAddress
Null_Type
TTCN error: e.g. invalid or incomplete address information
System
integer
system error caused by system call;
the integer value may be used for validation but shall not be
evaluated by TTCN
D.5.4.2 Socket_Datagram
Socket_Datagram: Basic Type Definitions
TTCN-3 Basic Types
Datagram_Content_Type
octetstring
data as sent/received with sendto()/recvfrom()
on UDP or ICMP socket;
NOTE:
For ICMP the data may depend on the socket
options;
in general it does not include the IP header
and
the checksum of the ICMP packet needs to be
calculated/checked in TTCN
Datagram_DL_Type
TTCN-3 Record Type
Name
Datagram_DL_Type
Comment
datagram to be sent at a UDP or ICMP socket
Buffer
Datagram_Content_Type
content of the IP packet
Datagram_UL_Type
TTCN-3 Record Type
Name
Datagram_UL_Type
Comment
datagram as received on a UDP or ICMP socket
Buffer
Datagram_Content_Type
content of the IP packet
DrbInfo
IP_DrbInfo_Type
opt "interface id" where the data comes from in case of broadcast or
multicast packets:
for the LTE test model this is the DRB on which the IP packet
has been received;
the information is necessary when the SS cannot resolve an IP
address being assigned to that DRB.
=> when the SS provides a broadcast or multicast address as
local address in the ConnectionId of the ASP, the SS shall
provide the DRB information in this field
When the ConnectionId of the ASP is fully specified and unique
(unicast address at least for local address) the DrbId is ignored
by TTCN
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
366
D.5.4.3 TCP_Socket
TCP primitives used on the IP port
TCP_Socket: Basic Type Definitions
TTCN-3 Basic Types
TCP_Data_Type
octetstring
data as sent/received with send()/recv() on a
TCP socket
InternetApplication_Type
TTCN-3 Enumerated Type
Name
InternetApplication_Type
Comment
as TCP is stream oriented SS may need information about which criteria to be applied to get
start/end of an application message
ims
http
TLS_CIPHER_Type
TTCN-3 Enumerated Type
Name
TLS_CIPHER_Type
Comment
Cipher suite to be used for TLS
TLS_PSK_WITH_RC RFC 4279
4_128_SHA
TLS_PSK_WITH_3D
RFC 4279
ES_EDE_CBC_SHA
TLS_PSK_WITH_AE
RFC 4279
S_128_CBC_SHA
TLS_PSK_WITH_AE
RFC 4279
S_256_CBC_SHA
TLS_PSK_WITH_AE
RFC 5487
S_128_CBC_SHA25
6
PSK_BootstrappingInfo_Type
TTCN-3 Record Type
Name
PSK_BootstrappingInfo_Type
Comment
bootstrapping information as defined in 24.109
BTid
charstring
Ks_NAF
bitstring
TLS_PSK_Info_Type
TTCN-3 Record Type
Name
TLS_PSK_Info_Type
Comment
configuration information for PSK TLS
IdentityHint
charstring
BootstrappingIn PSK_BootstrappingInfo_Ty
pe
fo
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
367
ETSI TS 136 523-3 V13.2.0 (2017-03)
TLS_CipherSuiteInfo_Type
TTCN-3 Union Type
Name
TLS_CipherSuiteInfo_Type
Comment
psk
TLS_PSK_Info_Type
TLSInfo_Type
TTCN-3 Record Type
Name
TLSInfo_Type
Comment
cipherSuite
TLS_CIPHER_Type
cipherSuiteInfo
TLS_CipherSuiteInfo_Type
Cipher suite to be used
parameters for the respective cipher suite
TCP_ConnectRequest_Type
TTCN-3 Record Type
Name
TCP_ConnectRequest_Type
Comment
TCP client: -> 'connect' system call
SockOptList
IP_SockOptList_Type
when there are no options to configure the list is empty
Application
InternetApplication_Type
to specify start/end criteria for application messages
TCP_Listen_Type
TTCN-3 Record Type
Name
TCP_Listen_Type
Comment
TCP server: -> 'listen' system call
SockOptList
IP_SockOptList_Type
Application
InternetApplication_Type
TLSInfo
TLSInfo_Type
opt
when there are no options to configure the list is empty
to specify start/end criteria for application messages
to support TLS for HTTP server implementation
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
368
ETSI TS 136 523-3 V13.2.0 (2017-03)
TCP_CtrlRequest_Type
TTCN-3 Union Type
Name
TCP_CtrlRequest_Type
Comment
ConnectReq
TCP_ConnectRequest_Type
request a 'connect' to a remote server
system calls (informative)
socket
-- get file descriptor
(setsockopt) -- normally not needed
bind
-- assign local IP addr (to cope with multiple IP
addresses) and dedicated port number (if local port is given)
connect
-- connect to the client
Listen
TCP_Listen_Type
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory to distinguish different network
adaptors
local port -- omit (ephemeral port will be assigned by the
system) or specific port to be used for this connection (e.g. to
bind a given port number to the IMS client)
remote IP addr -- mandatory
remote port -- mandatory
establish a server at the local (SS) side
system calls (informative)
socket
-- get file descriptor
(setsockopt) -- if needed
bind
-- assign local IP addr and port
listen
-- await incoming connection
Close
Null_Type
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory to distinguish different network
adaptors
local port -- mandatory
remote IP add -- omit
remote port -- omit
close a connection
system calls (informative):
close
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory
local port -- mandatory
remote IP addr -- mandatory for TCP connections, omit for TCP
server
remote port -- mandatory for TCP connections, omit for TCP
server
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
369
ETSI TS 136 523-3 V13.2.0 (2017-03)
TCP_DataRequest_Type
TTCN-3 Union Type
Name
TCP_DataRequest_Type
Comment
Send
TCP_Data_Type
send data
system calls (informative):
send or write
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory
local port -- mandatory
remote IP addr -- mandatory
remote port -- mandatory
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
370
ETSI TS 136 523-3 V13.2.0 (2017-03)
TCP_CtrlIndication_Type
TTCN-3 Union Type
Name
TCP_CtrlIndication_Type
Comment
ConnectCnf
Null_Type
confirm a 'connect' to a remote server
system calls (informative):
getsockname -- get local port (ephemeral port assigned by the
system)
Accept
Null_Type
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory (as in corresponding
TCP_ConnectRequest)
local port -- mandatory (if there is more than one connection
to the same server the local port is necessary to distinguish the
connections)
remote IP addr -- mandatory (as in corresponding
TCP_ConnectRequest)
remote port -- mandatory (as in corresponding
TCP_ConnectRequest)
sent by the SS when it 'accepts' an incoming connection
system calls (informative):
accept
Close
Null_Type
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory (as in corresponding
TCP_ListenRequest)
local port -- mandatory (as in corresponding
TCP_ListenRequest)
remote IP addr -- mandatory (as gotten from 'accept')
remote port -- mandatory (as gotten from 'accept')
indicate 'close' by the remote side
system calls (informative):
indicated by recv or read
CloseCnf
Null_Type
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory
local port
-- mandatory
remote IP addr -- mandatory
remote port -- mandatory
Confirmation for 'close' request; necessary since for TCP there
are IP packets to release the connection
system calls (informative):
close
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory
local port
-- mandatory
remote IP addr -- mandatory for TCP connections, omit for TCP
server
remote port -- mandatory for TCP connections, omit for TCP
server
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
371
ETSI TS 136 523-3 V13.2.0 (2017-03)
TCP_DataIndication_Type
TTCN-3 Union Type
Name
TCP_DataIndication_Type
Comment
Recv
TCP_Data_Type
receive data
system calls (informative):
recv or read
IP_Connection:
protocol
-- tcp
local IP addr -- mandatory
local port -- mandatory
remote IP addr -- mandatory
remote port -- mandatory
D.5.4.4 UDP_Socket
UDP primitives used on the IP port
NOTE:
In principle a UDP socket may communicate with different remote entities;
therefore the system adaptor may associate the socket handle with the local socket only
(local IP address and local port)
UDP_SocketReq_Type
TTCN-3 Record Type
Name
UDP_SocketReq_Type
Comment
to establish a UDP server or to bind local port number
SockOptList
IP_SockOptList_Type
e.g. to allow broadcast messages;
when there are no options to configure the list is empty
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
372
ETSI TS 136 523-3 V13.2.0 (2017-03)
UDP_CtrlRequest_Type
TTCN-3 Union Type
Name
UDP_CtrlRequest_Type
Comment
SocketReq
UDP_SocketReq_Type
request the system adaptor to bind a socket to a local address;
this is needed in general when the system adaptor acts as
1. UDP server
2. UDP client when it uses a well-known port rather than an
ephemeral port (this is e.g. for DHCP)
3. UDP client when a local address needs to be bond (e.g. when
there are several local addresses)
system calls (informative):
socket
-- get file descriptor
(setsockopt) -- needed e.g. to allow broad cast message
bind
-- assign local IP address (to cope with multiple IP
addresses) and local port (in case of well-known local port)
Close
Null_Type
IP_Connection:
protocol
-- udp
local IP addr -- mandatory (to distinguish multiple IP
addresses)
local port
-- optional (mandatory in case of a UDP server)
remote IP addr -- omit
remote port -- omit
release local socket
system calls (informative):
close
IP_Connection:
protocol
-- udp
local IP addr -- mandatory (to identify local socket)
local port -- mandatory (to identify local socket)
remote IP addr -- omit
remote port -- omit
UDP_DataRequest_Type
TTCN-3 Union Type
Name
UDP_DataRequest_Type
Comment
SendTo
Datagram_DL_Type
send data to (any) remote socket;
NOTE:
To simplify implementation of the system adaptor the local socket
shall be bond in any case (using 'SocketReq') to specify the local
IP address before sending data;
(in general the sendto system call can be used without explicitly
binding the socket before;
in this case the port gets implicitly bond to an ephemeral port and
the default IP address is used)
system calls (informative):
sendto
IP_Connection:
protocol
-- udp
local IP addr -- mandatory (to identify local socket)
local port -- mandatory (to identify local socket)
remote IP addr -- mandatory (to address remote socket)
remote port -- mandatory (to address remote socket)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
373
ETSI TS 136 523-3 V13.2.0 (2017-03)
UDP_CtrlIndication_Type
TTCN-3 Union Type
Name
UDP_CtrlIndication_Type
Comment
SocketCnf
Null_Type
confirm 'SocketReq' and tell TTCN about assignment of
ephemeral port;
system calls (informative):
getsockname -- get local port (ephemeral port assigned by the
system; not needed if local port is well-known)
IP_Connection:
protocol
-- udp
local IP addr -- mandatory
local port -- mandatory (well-known or ephemeral port
assigned by the system)
remote IP addr -- omit
remote port -- omit
UDP_DataIndication_Type
TTCN-3 Union Type
Name
UDP_DataIndication_Type
Comment
RecvFrom
Datagram_UL_Type
receive data;
system calls (informative):
recvfrom
-- get data and src addr
IP_Connection:
protocol
-- udp
local IP addr -- mandatory (see note)
local port -- mandatory
remote IP addr -- mandatory (as gotten from recvfrom)
remote port -- mandatory (as gotten from recvfrom)
NOTE:
The UE may send a UDP packet as broadcast (IP Addr
255.255.255.255 - e.g. in case of DHCP) or multicast (e.g.
ICMPv6)
SS shall consider a broadcast address as matching every IP for
UL and DL;
the SS shall not replace the broadcast/multicast address by the
local unicast address, but shall provide DRB information in
RecvFrom;
example:
- SS gets DHCPDISCOVER with
DEST_Addr=255.255.255.255 DEST_Port=67,
SRC_Addr=0.0.0.0 SRC_Port=68
- TTCN gets DHCPDISCOVER with local
Addr=(255.255.255.255 Port=67), remote Addr=(0.0.0.0
Port=68), DrbId=(LTE, cell1, DRB1)
- TTCN sends DHCPOFFER with local Addr=(local IP Addr
Port=67), remote Addr=(255.255.255.255 Port=68)
D.5.4.5 ICMP_Socket
ICMP primitives used on the IP port
NOTE:
the local side is identified by the protocol and in general by the local IP address
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
374
ETSI TS 136 523-3 V13.2.0 (2017-03)
ICMP_SocketReq_Type
TTCN-3 Record Type
Name
ICMP_SocketReq_Type
Comment
to establish a raw socket to send/receive ICMP packets
SockOptList
IP_SockOptList_Type
e.g. to set the IP_HDRINCL socket option (to include the IP
header in the data buffer)
when there are no options to configure the list is empty
ICMP_CtrlRequest_Type
TTCN-3 Union Type
Name
ICMP_CtrlRequest_Type
Comment
SocketReq
ICMP_SocketReq_Type
request the system adaptor to open a raw socket (IPv4 or IPv6)
system calls (informative):
socket
-- get file descriptor (IPPROTO_ICMP or
IPPROTO_IPV6);
(setsockopt) -- optional; to set socket options
bind
-- assign local IP address (to cope with multiple IP
addresses)
Close
IP_Connection:
protocol
-- icmp or icmpv6
local IP addr -- mandatory (to distinguish multiple IP addresses)
local port -- omit (not applicable for ICMP)
remote IP addr -- omit
remote port -- omit (not applicable for ICMP)
release local socket
Null_Type
system calls (informative):
close
IP_Connection:
protocol
-- icmp or icmpv6
local IP addr -- mandatory (to identify local socket)
local port -- omit
remote IP addr -- omit
remote port -- omit
ICMP_DataRequest_Type
TTCN-3 Union Type
Name
ICMP_DataRequest_Type
Comment
SendTo
Datagram_DL_Type
send datagram
system calls (informative):
sendto
IP_Connection:
protocol
-- icmp or icmpv6
local IP addr -- mandatory (to identify local socket)
local port -- omit
remote IP addr -- mandatory
remote port -- omit
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
375
ETSI TS 136 523-3 V13.2.0 (2017-03)
ICMP_CtrlIndication_Type
TTCN-3 Union Type
Name
ICMP_CtrlIndication_Type
Comment
SocketCnf
Null_Type
confirm 'SocketReq'
system calls (informative):
(SocketCnf is sent when all system calls for SocketReq have
been successful)
IP_Connection:
protocol
-- icmp or icmpv6
local IP addr -- mandatory
local port -- omit
remote IP addr -- omit
remote port -- omit
ICMP_DataIndication_Type
TTCN-3 Union Type
Name
ICMP_DataIndication_Type
Comment
RecvFrom
Datagram_UL_Type
receive datagram
system calls (informative):
recvfrom
-- get data and src addr
IP_Connection:
protocol
-- icmp or icmpv6
local IP addr -- mandatory (see note)
local port -- omit
remote IP addr -- mandatory (as gotten from recvfrom)
remote port -- omit
NOTE:
As for UDP there may be multicast/broadcast packets.
In this case - as for UDP - the SS shall provide the DRB
information in RecvFrom.
D.5.4.6 Socket_Primitives
IP_CtrlRequest_Type
TTCN-3 Union Type
Name
IP_CtrlRequest_Type
Comment
TCP
TCP_CtrlRequest_Type
UDP
UDP_CtrlRequest_Type
ICMP
ICMP_CtrlRequest_Type
IP_DataRequest_Type
TTCN-3 Union Type
Name
IP_DataRequest_Type
Comment
TCP
TCP_DataRequest_Type
UDP
UDP_DataRequest_Type
ICMP
ICMP_DataRequest_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
376
ETSI TS 136 523-3 V13.2.0 (2017-03)
IP_CtrlIndication_Type
TTCN-3 Union Type
Name
IP_CtrlIndication_Type
Comment
TCP
TCP_CtrlIndication_Type
UDP
UDP_CtrlIndication_Type
ICMP
ICMP_CtrlIndication_Type
Error
IP_SocketError_Type
IP_DataIndication_Type
TTCN-3 Union Type
Name
IP_DataIndication_Type
Comment
TCP
TCP_DataIndication_Type
UDP
UDP_DataIndication_Type
ICMP
ICMP_DataIndication_Type
D.5.5
System_Interface
DRBMUX_CONFIG_REQ
TTCN-3 Union Type
Name
DRBMUX_CONFIG_REQ
Comment
NOTE 1:
There is just one primitive to configure the whole routing table.
It is not foreseen to add, remove or manipulate single entries but the table is managed in TTCN and
completely configured on any change; (otherwise it might get complicated to identify single entries)
NOTE 2:
the SS's routing table shall be empty at the beginning and can be cleared by an empty record
(DRBMUX_CONFIG_REQ.RoutingInfo = {})
NOTE 3:
In general a reconfiguration of the routing table during a test case would be necessary only if an
ephemeral port is needed to distinguish different routing
(e.g. when there are several TCP connections of the same service routed to different DRBs)
RoutingInfo
IP_RoutingTable_Type
DRBMUX_COMMON_IND_CNF
TTCN-3 Union Type
Name
DRBMUX_COMMON_IND_CNF
Comment
Confirm
Null_Type
Error
Null_Type
confirm DRBMUX_CONFIG_REQ
indication of errors at the DRB-MUX:
An Error shall be raised by the DRB-MUX e.g. in the following
cases:
- in DL when there are IP packets which cannot be routed to any
DRB
i.e. the IP packet does not match to any entry in the routing
table or the corresponding RB is not configured
- in DL when there are several DRBs possible for routing in the
same cell
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
377
ETSI TS 136 523-3 V13.2.0 (2017-03)
IPSEC_CONFIG_REQ
TTCN-3 Union Type
Name
IPSEC_CONFIG_REQ
Comment
Configure
IPsec_Configure_Type
Release
IPsec_Release_Type
IPSEC_CONFIG_CNF
TTCN-3 Union Type
Name
IPSEC_CONFIG_CNF
Comment
Confirm
Null_Type
Error
Null_Type
confirm IPSEC_CONFIG_REQ
to indicate invalid configuration of IPsec
IP_SOCKET_CTRL_REQ
TTCN-3 Record Type
Name
IP_SOCKET_CTRL_REQ
Comment
ConnectionId
IP_Connection_Type
Req
IP_CtrlRequest_Type
IP_SOCKET_DATA_REQ
TTCN-3 Record Type
Name
IP_SOCKET_DATA_REQ
Comment
ConnectionId
IP_Connection_Type
Req
IP_DataRequest_Type
IP_SOCKET_CTRL_IND
TTCN-3 Record Type
Name
IP_SOCKET_CTRL_IND
Comment
ConnectionId
IP_Connection_Type
Ind
IP_CtrlIndication_Type
IP_SOCKET_DATA_IND
TTCN-3 Record Type
Name
IP_SOCKET_DATA_IND
Comment
ConnectionId
IP_Connection_Type
Ind
IP_DataIndication_Type
IP_SOCKET_REQ
TTCN-3 Union Type
Name
IP_SOCKET_REQ
Comment
CTRL
IP_SOCKET_CTRL_REQ
DATA
IP_SOCKET_DATA_REQ
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
378
IP_SOCKET_IND
TTCN-3 Union Type
Name
IP_SOCKET_IND
Comment
CTRL
IP_SOCKET_CTRL_IND
DATA
IP_SOCKET_DATA_IND
IP_CONTROL_PORT
TTCN-3 Port Type
Name
IP_CONTROL_PORT
Comment
out
DRBMUX_CONFIG_REQ
in
DRBMUX_COMMON_IND_CNF
IPSEC_CONTROL_PORT
TTCN-3 Port Type
Name
IPSEC_CONTROL_PORT
Comment
out
IPSEC_CONFIG_REQ
in
IPSEC_CONFIG_CNF
IP_SOCKET_PORT
TTCN-3 Port Type
Name
IP_SOCKET_PORT
Comment
out
IP_SOCKET_REQ
in
IP_SOCKET_IND
D.6
NasEmu_AspTypes_EUTRA
System interface between NAS emulation and system adaptor
ETSI
ETSI TS 136 523-3 V13.2.0 (2017-03)
3GPP TS 36.523-3 version 13.2.0 Release 13
D.6.1
379
ETSI TS 136 523-3 V13.2.0 (2017-03)
System_Interface
EUTRA_RRC_PDU_REQ
TTCN-3 Record Type
Name
EUTRA_RRC_PDU_REQ
Comment
Common
ReqAspCommonPart_Type
RrcPdu
CellId : identifier of the cell
RoutingInfo : SRB0, SRB1, SRB2
TimingInfo : Now in normal cases;
For latency tests TimingInfo can be set to the SFN/subframe in
which the RRC messages shall be sent out
NOTE 1: if the RRC PDU is too long to be sent in one TTI the
TimingInfo corresponds to the first TTI
NOTE 2: the TimingInfo is not changed by the NAS Emu (i.e.
the timing info as coming from the test case
(SRB_COMMON_REQ) is handed through by the NAS Emu)
ControlInfo
CnfFlag:=false;
FollowOnFlag
true: Indicates that the message(s) to be sent on the same TTI
will follow
NOTE 1: If the TimingInfo is not the same for messages to
be sent on the same TTI, the SS shall produce an error
NOTE 2: the follow on flag applies only for messages of
the same SRB
false: Indicates that no more message(s) will follow
RRC_MSG_Request_Type
EUTRA_RRC_PDU_IND
TTCN-3 Record Type
Name
EUTRA_RRC_PDU_IND
Comment
common ASP to receive PDUs from SRB0, SRB1 or SRB2
Common
IndAspCommonPart_Type
CellId : identifier of the cell
RoutingInfo : SRB0, SRB1, SRB2
TimingInfo : time when message has been received (frame and
sub-frame number); this is handed through to the test case by
the NAS emulation
NOTE: normally an RRC PDU is expected in one TTI;
nevertheless if it is spread over more than one TTIs TimingInfo
shall refer to the end of the PDU i.e. to the last RLC PDU being
received;
Status : OK or RRC integrity error
RrcPdu
RRC_MSG_Indication_Typ
e
NASEMU_EUTRA_SYSTEM_PORT
TTCN-3 Port Type
Name
NASEMU_EUTRA_SYSTEM_PORT
Comment
NASEMU PTC: Port for Sending/Receiving data to/from the SYSTEM Interface
out
EUTRA_RRC_PDU_REQ
in
EUTRA_RRC_PDU_IND
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
380
D.7
EUTRA_CommonDefs
D.7.1
Common_Types
Common_Types: Basic Type Definitions
TTCN-3 Basic Types
RedundancyVersion_Typ
e
integer (0..3)
used in EUTRA_ASP_DrbDefs and
EUTRA_ASP_Typedefs
HarqProcessList_Type
TTCN-3 Record of Type
Name
HarqProcessList_Type
Comment
list of HARQ processes: each element shall be unique
record length(0..14) of HarqProcessId_Type
RRC_MSG_Request_Type
TTCN-3 Union Type
Name
RRC_MSG_Request_Type
Comment
DL RRC PDU on CCCH or DCCH
Ccch
DL_CCCH_Message
Dcch
DL_DCCH_Message
RRC_MSG_Indication_Type
TTCN-3 Union Type
Name
RRC_MSG_Indication_Type
Comment
UL RRC PDU on CCCH or DCCH
Ccch
UL_CCCH_Message
Dcch
UL_DCCH_Message
D.7.2
Common_Constants
EUTRA_CommonDefs: Constant Definitions
TTCN-3 Basic Types
tsc_EUTRA_MaxNu
mberOfCells
integer
20
ETSI
Maximum number of cells;
in TS 36.508 in, clause 4.4.2 and
6.3.2.2 there are tables for cells
being used in non-NAS and NAS
test cases;
in both cases less than 20 cells
are listed
3GPP TS 36.523-3 version 13.2.0 Release 13
D.7.3
381
ETSI TS 136 523-3 V13.2.0 (2017-03)
RRC_Nested_Types
RRC_Nested_Types: Basic Type Definitions
TTCN-3 Basic Types
SchedulingInfoSIB1_BR_r
13_Type
SiWindowLength_Type
BandwidthReducedAcces
sRelatedInfo_Type
SiPeriodicity_Type
PrioritizedBitRate_Type
Dl_Bandwidth_Type
Ul_Bandwidth_Type
Ra_PreambleIndex_Type
EDRX_CycleStartOffset_r
13_Type
UE_Category_Type
DRX_Config_r13_Type
TDD_SubframeAssignme
nt_Type
SCellPathlossReferenceLi
nking_Type
MAC_MainConfig_ScellDe
activationTimer_Type
CrossSchedulingCarrierIn
fo_Type
NotificationIndicator_r9_T
ype
LogicalChannelIdentity_r
9_Type
UE_Category_v1020_Typ
e
UE_Category_v1170_Typ
e
UE_Category_v11a0_Typ
e
UE_CategoryDL_v1310_T
ype
UE_CategoryUL_v1310_T
ype
UE_Category_v1250_Typ
e
E_HARQ_Pattern_r12_Ty
pe
TTI_Bundling_Type
CE_Mode_r13_Type
SC_MCCH_Duration_Typ
e
SC_MCCH_FirstSubframe
_Type
SC_MCCH_ModificationP
eriod_Type
SC_MCCH_Offset_Type
SC_MCCH_RepetitionPeri
od_Type
MasterInformationBlock.schedulingInfoS
IB1_BR_r13
SystemInformationBlockType1.si_Windo
wLength
SystemInformationBlockType1_v1310_I
Es.bandwidthReducedAccessRelatedInf
o_r13
SchedulingInfoList[0].si_Periodicity
LogicalChannelConfig.ul_SpecificParam
eters.prioritisedBitRate
CarrierBandwidthEUTRA.dl_Bandwidth
CarrierBandwidthEUTRA.ul_Bandwidth
RACH_ConfigDedicated.ra_PreambleIn
dex
MAC_MainConfig.eDRX_Config_CycleS
tartOffset_r13
UE_EUTRA_Capability.ue_Category
MAC_MainConfig.drx_Config_r13
TDD_Config.subframeAssignment
UplinkPowerControlDedicatedSCell_r10
.pathlossReferenceLinking_r10
MAC_MainConfig.mac_MainConfig_v10
20.sCellDeactivationTimer_r10
CrossCarrierSchedulingConfig_r10.sche
dulingCellInfo_r10.other_r10
MBSFN_AreaInfo_r9.notificationIndicato
r_r9
MBMS_SessionInfo_r9.logicalChannelId
entity_r9
UE_EUTRA_Capability_v1020_IEs.ue_
Category_v1020
UE_EUTRA_Capability_v1170_IEs.ue_
Category_v1170
UE_EUTRA_Capability_v11a0_IEs.ue_
Category_v11a0
UE_EUTRA_Capability_v1310_IEs.ue_
CategoryDL_v1310
UE_EUTRA_Capability_v1310_IEs.ue_
CategoryUL_v1310
UE_RadioPagingInfo_r12.ue_Category_
v1250
MAC_MainConfig.e_HARQ_Pattern_r12
MAC_MainConfig.ul_SCH_Config.ttiBun
dling
PhysicalConfigDedicated.ce_Mode_r13
SystemInformationBlockType20_r13.sc_
mcch_duration_r13
SystemInformationBlockType20_r13.sc_
mcch_FirstSubframe_r13
SystemInformationBlockType20_r13.sc_
mcch_ModificationPeriod_r13
SystemInformationBlockType20_r13.sc_
mcch_Offset_r13
SystemInformationBlockType20_r13.sc_
mcch_RepetionPeriod_r13
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.7.4
ETSI TS 136 523-3 V13.2.0 (2017-03)
382
ASP_CommonPart
Definition of ASP common parts for REQ-, CNF- and IND-ASPs
D.7.4.1 ASP_CommonPart_Definitions
D.7.4.1.1
Routing_Info
EUTRA_CommonDefs: Constant Definitions
TTCN-3 Basic Types
tsc_MaxRB
tsc_SRB2
integer
integer
maxDRB + 3
2
DRBs + 3 SRBs
Routing_Info: Basic Type Definitions
TTCN-3 Basic Types
SRB_Identity_Type
CarrierAggregationInfo_T
ype
integer (tsc_SRB0, tsc_SRB1,
tsc_SRB2)
Null_Type
SRB0 to be covered as well
place holder for additional routing information
for carrier aggregation
SC_MRB_Identity_Type
TTCN-3 Record Type
Name
SC_MRB_Identity_Type
Comment
MbmsSessionI
MBMSSessionInfo_r13
nfo
RadioBearerId_Type
TTCN-3 Union Type
Name
RadioBearerId_Type
Comment
Srb
SRB_Identity_Type
Drb
DRB_Identity
Mrb
MRB_Identity_Type
ScMrb
SC_MRB_Identity_Type
RoutingInfo_Type
TTCN-3 Union Type
Name
RoutingInfo_Type
Comment
None
Null_Type
RadioBearerId
RadioBearerId_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
383
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.7.4.2 REQ_ASP_CommonPart
ReqAspCommonPart_Type
TTCN-3 Record Type
Name
ReqAspCommonPart_Type
Comment
CellId
EUTRA_CellId_Type
RoutingInfo
RoutingInfo_Type
TimingInfo
TimingInfo_Type
ControlInfo
ReqAspControlInfo_Type
CA_Info
CarrierAggregationInfo_Typ opt
e
place holder for additional routing information for carrier
aggregation
D.7.4.3 CNF_ASP_CommonPart
CnfAspCommonPart_Type
TTCN-3 Record Type
Name
CnfAspCommonPart_Type
Comment
CellId
EUTRA_CellId_Type
RoutingInfo
RoutingInfo_Type
TimingInfo
TimingInfo_Type
Result
ConfirmationResult_Type
D.7.4.4 IND_ASP_CommonPart
IndAspCommonPart_Type
TTCN-3 Record Type
Name
IndAspCommonPart_Type
Comment
CellId
EUTRA_CellId_Type
RoutingInfo
RoutingInfo_Type
TimingInfo
TimingInfo_Type
Status
IndicationStatus_Type
CA_Info
CarrierAggregationInfo_Typ
e
D.7.5
opt
place holder for additional routing information for carrier
aggregation
MBMS_CommonDefs
Common definitions for MBMS needed for configuration of the SS
MBMS_CommonDefs: Basic Type Definitions
TTCN-3 Basic Types
Pmch_InfoIndex_Type
integer (0..maxPMCH_PerMBSFN)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
384
MRB_Identity_Type
TTCN-3 Record Type
Name
MRB_Identity_Type
Comment
MTCH is uniquely identified by:
- the logicalChannelIdentity in the mbms-SessionInfoList-r9
- the MBSFN area identity,
- the MCH index in the pmch-InfoList-r9
Mbsfn_AreaId
MBSFN_AreaId_r12
PmchLogicalCh PmchLogicalChannel_Type
annel
PmchLogicalChannel_Type
TTCN-3 Record Type
Name
PmchLogicalChannel_Type
Comment
Pmch_InfoInde Pmch_InfoIndex_Type
x
LogicalChannel LogicalChannelIdentity_r9_
Type
Identity
D.8
CDMA2000_ASP_TypeDefs
D.8.1
CDMA2000_Common
Common definitions for CDMA2000 and CDMA2000 ASPs
D.8.1.1 CDMA2000_SystemContants
CDMA2000_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_CDMA2000_Max
NumberOfCells
integer
8
Maximum number of CDMA2000
cells;
in TS 36.508 in, clause 6.3.1.5
and 6.3.1.6 define 4 cells each for
HRPD and 1XRTT;
hence total is 8
D.8.1.2 CDMA2000_Routing
CDMA2000_Routing: Basic Type Definitions
TTCN-3 Basic Types
RLP_FlowId_Type
integer (0..30)
As per S.0024, clause 4.8.2.10 both
MaxNumRLPFlowsFwd and
MaxNumRLPFlowsRvs need to be in the
range of 0x06(6) to 0x1F(31)
As per x.s007 clause 10, the PDN ID and Flow
ID identify a flow
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
385
RLP_FlowIdList_Type
TTCN-3 Record of Type
Name
RLP_FlowIdList_Type
Comment
record of RLP_FlowId_Type
CDMA2000_RoutingInfo_Type
TTCN-3 Union Type
Name
CDMA2000_RoutingInfo_Type
Comment
None
Null_Type
RLP_FlowId
RLP_FlowId_Type
D.8.1.3 CDMA2000_TimingInfo
CDMA2000_TimingInfo: Basic Type Definitions
TTCN-3 Basic Types
HRPD_FrameNumber_Ty
pe
SubFrameNumber_Type
RTT1X_FrameNumber_Ty
pe
integer
CDMA system time specified in units of 16
slots i.e. 26.66 ms.
A sub-frame is a group of four contiguous
slots.
The start of a sub-frame is specified by (T FrameOffset) mod 4 = 0, where T is the CDMA
System Time in slots
CDMA System Time, in integer multiples of 20
ms
integer (0..3)
integer
HRPD_SubFrameInfo_Type
TTCN-3 Union Type
Name
HRPD_SubFrameInfo_Type
Comment
Number
SubFrameNumber_Type
Any
Null_Type
no specific sub-frame (valid for REQ ASPs only)
HRPD_Frame_Type
TTCN-3 Union Type
Name
HRPD_Frame_Type
Comment
Number
HRPD_FrameNumber_Type
Any
Null_Type
no specific TimeStamp (valid for REQ ASPs only)
RTT1X_Frame_Type
TTCN-3 Union Type
Name
RTT1X_Frame_Type
Comment
Number
RTT1X_FrameNumber_Type
Any
Null_Type
no specific TimeStamp (valid for REQ ASPs only)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
386
ETSI TS 136 523-3 V13.2.0 (2017-03)
HRPD_SubFrameTiming_Type
TTCN-3 Record Type
Name
HRPD_SubFrameTiming_Type
Comment
Frame
HRPD_Frame_Type
Subframe
HRPD_SubFrameInfo_Typ
e
CDMA2000_SubFrameTiming_Type
TTCN-3 Union Type
Name
CDMA2000_SubFrameTiming_Type
Comment
HRPD
HRPD_SubFrameTiming_Type
HRPD Timing
RTT1X
RTT1X_Frame_Type
RTT1X Timing specified in terms of Frames only
CDMA2000_TimingInfo_Type
TTCN-3 Union Type
Name
CDMA2000_TimingInfo_Type
Comment
SubFrame
CDMA2000_SubFrameTiming_Ty
pe
Now
Null_Type
None
Null_Type
to be used in REQ ASPs when there is no 'activation time'
only to be used in SYSTEM_CTRL_CNF but not for
EnquireTiming
D.8.1.4 CDMA2000_ReqAspCommonPart
CDMA2000_ReqAspControlInfo_Type
TTCN-3 Record Type
Name
CDMA2000_ReqAspControlInfo_Type
Comment
CnfFlag
boolean
true => SS shall send CNF:
when the REQ is with no timing information (no activation time),
SS shall send the confirmation when the configuration is done,
i.e. when the test case may continue.
Example:
when there is a configuration follow by a send event it shall not
be necessary to have a wait timer in between but the CNF
triggers the send event or system Command.
If there are other triggers e.g. like the UE sending a message,
CnfFlag shall be set to false by the test case to avoid racing
conditions with the CNF and the signalling message.
When there is an activation time SS shall send the CNF after the
configuration has been scheduled;
that means SS shall not wait until the activation time has been
expired.
FollowOnFlag
boolean
false => no further (related) information
true: further related information will be sent to SS ; Currently this
value is not foreseen to be used.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
387
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_ReqAspCommonPart_Type
TTCN-3 Record Type
Name
CDMA2000_ReqAspCommonPart_Type
Comment
CellId
CDMA2000_CellId_Type
RoutingInfo
CDMA2000_RoutingInfo_T
ype
TimingInfo
CDMA2000_TimingInfo_Ty
pe
ControlInfo
CDMA2000_ReqAspContro
lInfo_Type
D.8.1.5 CDMA2000_IndAspCommonPart
CDMA2000_ErrorIndication_Type
TTCN-3 Record Type
Name
CDMA2000_ErrorIndication_Type
Comment
System
integer
any other error: may be SS specific error code; this will not be
evaluated by TTCN;
e.g. an error shall be raised when the UE requests
retransmission of an RLC PDU
CDMA2000_IndicationStatus_Type
TTCN-3 Union Type
Name
CDMA2000_IndicationStatus_Type
Comment
Ok
Null_Type
Error
CDMA2000_ErrorIndication_Type
CDMA2000_IndAspCommonPart_Type
TTCN-3 Record Type
Name
CDMA2000_IndAspCommonPart_Type
Comment
CellId
CDMA2000_CellId_Type
RoutingInfo
CDMA2000_RoutingInfo_T
ype
TimingInfo
CDMA2000_TimingInfo_Ty
pe
Status
CDMA2000_IndicationStatu
s_Type
D.8.1.6 CDMA2000_CnfAspCommonPart
CDMA2000_ConfirmationResult_Type
TTCN-3 Union Type
Name
CDMA2000_ConfirmationResult_Type
Comment
Success
Null_Type
Error
integer
may contain SS specific error code; this will not be evaluated by
TTCN
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
388
CDMA2000_CnfAspCommonPart_Type
TTCN-3 Record Type
Name
CDMA2000_CnfAspCommonPart_Type
Comment
CellId
CDMA2000_CellId_Type
RoutingInfo
CDMA2000_RoutingInfo_T
ype
TimingInfo
CDMA2000_TimingInfo_Ty
pe
Result
CDMA2000_ConfirmationR
Similar definition as EUTRA
esult_Type
D.8.2
CDMA2000_PowerLevel
CDMA2000_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_CDMA2000_Atte
nuation_Off
CDMA2000_Attenuation_Type
{Off:=true}
CDMA2000_PowerLevel: Basic Type Definitions
TTCN-3 Basic Types
CDMA2000_InitialAttenuat
ion_Type
CDMA2000_Attenuation_Type
(tsc_CDMA2000_Attenuation_Off)
Attenuation restricted to 'Off'
CDMA2000_Attenuation_Type
TTCN-3 Union Type
Name
CDMA2000_Attenuation_Type
Comment
attenuation of the reference power
Value
Attenuation_Type
Off
Null_Type
cell power reference power reduced by the given attenuation
(value is in dB)
for non suitable off cell we specify an explicit "Off" value here
CDMA2000_CellAttenuation_Type
TTCN-3 Record Type
Name
CDMA2000_CellAttenuation_Type
Comment
CellId
CDMA2000_CellId_Type
Attenuation
CDMA2000_Attenuation_Ty
pe
CDMA2000_CellAttenuationList_Type
TTCN-3 Record of Type
Name
CDMA2000_CellAttenuationList_Type
Comment
record length(1..tsc_CDMA2000_MaxNumberOfCells) of CDMA2000_CellAttenuation_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
389
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_AbsoluteCellPower_Type
TTCN-3 Record Type
Name
CDMA2000_AbsoluteCellPower_Type
Comment
PowerIoc
PowerIoc_Type
TTCN writer Shall set same vale in all cells; SS shall have only
one AWGN channel for all configured cells per frequency
SS shall create a AWGN channel in first cell per frequency and
ignore this in later cell creations on the same frequency;
i.e. this channel is created along once for Cell 15 or 16 and one
each per 17 and 19
similary for RTT1X once for 19 or 20 and one each per 21 and 22
PowerIor
PowerIor_Type
Total Transmit power in cell before attenuation
PilotOffset
PilotOffset_Type
Default -7
CDMA2000_InitialCellPower_Type
TTCN-3 Record Type
Name
CDMA2000_InitialCellPower_Type
Comment
MaxReference
CDMA2000_AbsoluteCellP
maximum value of cell reference power corresponding to Max
ower_Type
Power
Ior/Ioc in power level table;
a cell is initialised with this reference power;
its value is the upper bound of the cell power during the test case
Attenuation
CDMA2000_InitialAttenuati
initial attenuation Cell is off
on_Type
D.8.3
CDMA2000_Data
Data primitives sent/received at CDMA2000_RLP_FLOW_PORT
CDMA2000_Data: Basic Type Definitions
TTCN-3 Basic Types
RLP_SDU_Type
octetstring
RLP_SDUList_Type
TTCN-3 Record of Type
Name
RLP_SDUList_Type
Comment
record of RLP_SDU_Type
CDMA2000_U_PlaneData_Type
TTCN-3 Union Type
Name
CDMA2000_U_PlaneData_Type
Comment
Union structure is provided for future possible enhancements
RLP_Sdu
RLP_SDUList_Type
RLP SDU's
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
390
ETSI TS 136 523-3 V13.2.0 (2017-03)
RLPFlow_DataPerSubframe_DL_Type
TTCN-3 Record Type
Name
RLPFlow_DataPerSubframe_DL_Type
Comment
common definition for one or several SDUs to be sent in the subframe given by the subframe offset;
SS shall raise an error indication (using SYSTEM_IND) when that is not possible
NOTE 1:
For RLP the data may be spread over more than one subframe ;
the TTCN implemetation is responsible to calculate appropriate offsets accordingly
SubframeOffset integer
subframe offset relative to the absolute timing information given
in the common part of the ASP;
NOTE :
if a RLP SDU takes more than one subframe, SubframeOffset
specifies the first TTI
SduList
CDMA2000_U_PlaneData_
list of PDUs/SDUs to be sent in one subframe
Type
RLPFlow_DataPerSubframeList_DL_Type
TTCN-3 Record of Type
Name
RLPFlow_DataPerSubframeList_DL_Type
Comment
list of user plane data to be sent in sub-frames given by the SubframeOffset in the single
elements of the list;
Timing:
the start time for the whole sequence is given by the timing info of the ASP (common
information);
the timing for the respective data pdus is given by the SubframeOffset relative to the common
timing info;
design consideration:
repetitions of this sequence are not foreseen
(in which case the subframe offset could not be related to the timing info of the ASP)
record of RLPFlow_DataPerSubframe_DL_Type
CDMA2000_U_Plane_Request_Type
TTCN-3 Record Type
Name
CDMA2000_U_Plane_Request_Type
Comment
NOTE: formal type definition to allow later enhancements;
CDMA2000_U_Plane_Request_Type defines a sequence of subframes in which data shall be sent
SubframeDataL RLPFlow_DataPerSubfram
eList_DL_Type
ist
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.8.4
391
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_CellConfiguration
HRPD_CellParameters_Type
TTCN-3 Record Type
Name
HRPD_CellParameters_Type
Comment
Parameters specific to HRPD
SystemType
SystemType_Type
SubNetMask
B8_Type
ColorCode
ColorCode_Type
CountryCode
MCC_Type
OpenLoopAdju
st
OpenLoopAdjust_Type
ReverseRateLi
mit
ReverseRateLimit_Type
MACIndex
ReverseLinkMACIndex_Typ
e
PacketApp
PacketApplication_Type
ControlChannel
Rate
PDN_Id
PDN_Address
UATI
ControlChannelRate_Type
Specifies the sytem type of Channel
As per Table 13.1-1 of C.S0024 0, 1, 2 are defined values and 3
to 255 are reserved
7.11.6.2.2 of C.S0024
Sector Subnet identifier
set this field to the number of consecutive 1s in the subnet mask
of the subnet to which this sector belongs
7.11.6.2.1 of C.S0024
set to the color code corresponding to this sector part of
QuickConfig Over head message
7.11.6.2.2 of C.S0024
three-digit BCD (binary coded decimal) encoded representation
of the Mobile Country Code associated with this sector
9.4.6.2.6 of C.S0024;
The negative of the nominal power to be used by access
terminals in the open loop power estimate, expressed as an
unsigned value in units of 1 dB.
The value used by the access terminal is -1 times the value of
this field
Table 9.9.6.3-2 of C.S0024;
set to the highest data rate that the access terminal is allowed to
use on the Reverse Traffic Channel
C.S0024 clause 12.4.1.3.2.2
Forward channel MAC is derivered from this based on table
12.4.1.3.2.2-1
Multi Flow Packet Application to be used
Enhanced Multi-Flow Packet Application subtype(0x0009)
defined in C.S0087 or
as per C.S0087, clause 2.3 the UE Shalll not propose AEMPA
during stream protocol negotiation (0xFFFE) in C.R1001
MAC index to be used for the Control Channel
PDN_Id_Type
PDN_Address_Type
UATI_Type
PDN_ID of the bearer
the PDN Address to be provided to the UE in VSNCP ConfigAck
UATI to be Assigned to the UE
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
392
ETSI TS 136 523-3 V13.2.0 (2017-03)
RTT1X_CellParameters_Type
TTCN-3 Record Type
Name
RTT1X_CellParameters_Type
Comment
Parameters specific to 1XRTT
Reg_Zone
B12_Type
Base_Class
B4_Type
MCC
B10_Type
IMSI_11_12
B7_Type
TMSI
ProtRev
Min_ProtRev
Sig_Encryption
Mode
USerInfo_Encr
yptionMode
TMSI_Type
ProtRev_Type
ProtRev_Type
EncryptionMode_Type
C.S005 clause 3.7.2.3.2.1 and 2.6.5.1.5
Registration Zone of the base station
Reg_Zone, SID and NID shall be unique for each base station
C.S0005 clause 3.7.2.3.2.1
Base station class.
The base station shall set this field as follows:
For Band Class 1 and 4, the base station shall set this field to
'0001'; otherwise, the base station shall set this field to '0000'
3.7.2.3.2.13 and 2.3.1.1 of C.S0005
encoding is int2bit (100*D1+10*D2+D3 -111,10) with digit 0 being
maped to 10
binary representation of the Mobile Country Code associated
with this sector
3.7.2.3.2.13 and 2.3.1.2 of C.S0005
encoding is int2bit (10*D2+D3 -11,7) with digit 0 being maped to
10
binary representation of the Mobile Network Code associated
with this sector
the TMSI to be assigned to the MS
Protocol Revision
the minimum protocol revision supported by Base station
Encryption mode for Common and dedicated signalling
EncryptionMode_Type
User information Encryption mode
ModeSpecificCellParams_Type
TTCN-3 Union Type
Name
ModeSpecificCellParams_Type
Comment
RTT1X
RTT1X_CellParameters_Type
HRPD
HRPD_CellParameters_Type
CDMA2000_CellParameters_Type
TTCN-3 Record Type
Name
CDMA2000_CellParameters_Type
Comment
Type
CDMA2K_Type
CarrierFreq
CarrierFreqCDMA2000_Ty
pe
PhysCellId
PhysCellIdCDMA2000_Typ
e
CellGlobalId
CellGlobalIdCDMA2000_Ty
pe
SearchWindow SearchWindowSizeRecord_
Type
Gives if cell is EHRPD or RTT1X
Contains bandclass (5 bit) and arfcn i.e. 11 bit channel number
PN offset of pilot 0..511
Contains the 128 bit cell ID for HRPD and 47 bit cell ID for
1XRTT
contains the SearchWindow for Active, Neighbor & Remaining
cells
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
393
CDMA2000_CellConfigInfo_Type
TTCN-3 Record Type
Name
CDMA2000_CellConfigInfo_Type
Comment
CellParameters CDMA2000_CellParameter
Parameters common to HRPD and RTT1X
s_Type
InitialCellPower CDMA2000_InitialCellPowe
Power level parameters
r_Type
ModeSpecificC ModeSpecificCellParams_T
Parameters specific to RTT1X or HRPD
ype
ellParams
CDMA2000_CellConfigRequest_Type
TTCN-3 Union Type
Name
CDMA2000_CellConfigRequest_Type
Comment
AddOrReconfig CDMA2000_CellConfigInfo_Type
for cell configuration:
ure
CellId : identifier of the cell to be configured
RoutingInfo : None
TimingInfo : Now (for initial configuration and for reconfiguration
in general)
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
Release
Null_Type
to remove a cell completely CellId : identifier of the cell to be released;
eutra_Cell_NonSpecific, in case all cells shall be released
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
D.8.5
CDMA2000_HRPD
D.8.5.1 CDMA2000_PDN_Defs
CDMA2000_PDN_Defs: Basic Type Definitions
TTCN-3 Basic Types
CDMA2000_AttachType
O3_Type
IPv4_Address_Type
O4_Type
IPv6_Address_Type
O8_Type
PDN_Id_Type
B4_Type
Flow_Id_Type
B4_Type
Defined values:
1: Initial Attach to a PDN,
3: Handover attach to a PDN.
Rest undefined and not used
represents the IPv4 address as per 24.301
clause 9.9.4.9
represents the IPv6 interface identifier as per
24.301 clause 9.9.4.9
indicates the PDN Id associated with the
bearer PDN Identifier of the PDN for which the
user data is sent.
it is the low order 4 bits of, containing the
PDN-ID identifies the PDN (i.e. one per default
bearer)
Reference x.s0057 clause 10.1.5; gives only
low order 4 bits, and high order 4 bits are
added as all zero's
the lower 4 bits of the Flow Identifier, as
defined in Table 15 of x.s0057
identify each reservation that is requested to
be added or deleted
the complete 8 bit flow Identifier is formed by
PDN-ID and Flow-Id
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
394
ETSI TS 136 523-3 V13.2.0 (2017-03)
IPv4v6_Address_Type
TTCN-3 Record Type
Name
IPv4v6_Address_Type
Comment
IPv4
IPv4_Address_Type
IPv6
IPv6_Address_Type
IP v4 address to be allocated
IP v6 interface identifier to be allocated
PDN_Address_Type
TTCN-3 Union Type
Name
PDN_Address_Type
Comment
based on 24.301 cl. 9.9.4.9
IPv4
IPv4_Address_Type
IPv6
IPv6_Address_Type
IPv4v6
IPv4v6_Address_Type
only IP v4 address to be allocated
only IP v6 interface identifier to be allocated
both IP v4 address and IP v6 interface identifier to be allocated
Flow_IdList_Type
TTCN-3 Record of Type
Name
Flow_IdList_Type
Comment
record of Flow_Id_Type
D.8.5.2 CDMA2000_SubProtocols
LCP_DetachInit_Type
TTCN-3 Enumerated Type
Name
LCP_DetachInit_Type
Comment
networkInitiated
x.s0057 clause 11.2
UEInitiated
x.s0057 clause 11.1.2
DHCP_Ind_Type
TTCN-3 Record Type
Name
DHCP_Ind_Type
Comment
RapidCommit
boolean
indicates if Rapid Comit option of DHCP is used
UATI104_Type
TTCN-3 Union Type
Name
UATI104_Type
Comment
Value
O13_Type
None
Null_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
395
ETSI TS 136 523-3 V13.2.0 (2017-03)
UATI_Type
TTCN-3 Record Type
Name
UATI_Type
Comment
UATI24
O3_Type
UATI104
UATI104_Type
Represents UATI (0:23), as per clause 6.3.7.2.2 of C.S0024
Represents UATI (127:24), as per clause 6.3.7.2.2 of C.S0024 if
has to be assigned
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
396
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.8.5.3 HRPD_Indications
RegAndDefBearerEstInd_Type
TTCN-3 Record Type
Name
RegAndDefBearerEstInd_Type
Comment
UATI_Assignm
Null_Type
entCmpl
InitialChAssign
Null_Type
Cmpl
SCP_ConfigC
mpl
Null_Type
Stream_Config
Cmpl
Null_Type
EMPA_MMPA_
ConfigCmpl
Null_Type
SessionNegotia
tionCmpl
DeviceAuthCm
pl
LocationUpdate
Cmpl
EAP_AKA_Cm
pl
Null_Type
opt
Null_Type
opt
Null_Type
opt
VSNCP_Config
Cmpl
Null_Type
DHCP_ConfigC
mpl
DHCP_Ind_Type
opt
ICMPv6_Config
Cmpl
Null_Type
opt
Null_Type
UATIAssignment is received
UATIComplete is received
Initial Traffic/Extended Channel/AlternateLink(Pre-registration)
Assignment procedure started UE has sent
ConnectionRequest/AlternateLinkOpen message
Traffic/Extended Channel /AlternateLink(Pre-registration)
assignment is completedUE has sent TrafficChannelComplete(
Route update protocol)/ AlternateLinkOpenComplete.
In the registration and Default bearer establishment procedure,
UE initiated Channel/Alternate Link can be released and
configured, only first assignment is reported.
SCP (Session Configuration Protocol )ConfigurationRequest
mesage is received
SCP (Session Configuration Protocol )ConfigurationResponse
mesage is transmitted
Stream Protocol Configuration ConfigurationRequest mesage is
received
Stream Protocol Configuration ConfigurationResponse mesage
is transmitted
Enhanced Multi flow/Multi flow Packet application
ConfigurationRequest mesage is received
Enhanced Multi flow/Multi flow Packet application
ConfigurationComplete mesage is received
EMPA ConfigurationResponse message or MMPA
ConfigurationResponse is received corresponding to steps 30A
TO 30C of table 4.5.2B.3-2
SS initiated Session Negotiation has started; Session Negotiation
has completed
Device level authentication has started; Device level
authentication has completed
Location Update started; Location Update completed
Improved Extensible Authentication protocol for Authentication
and Key agreement started RFC 5448
* Message flow in x.s0057 clause 5.2.5.1 Authentication and Key
agreement Completed
optionally After entering PPP LCP Open State, PPP Version
Capability Indicaiton and/or Max PPP Inactivity Timer negotiation
are completed
PDN connection establishment started and UE has sent
PPP Vendor Specific Network Control Protocol Configuration
Request PDN Connection and default bearer establishment is
completed
with possible IPV4 address (optional) and or IPv6 interface ID
(Mandatory) provided
Attach type shall be Handover Attach
UE and SS decided for IPv4 address allocation by DHCP IPv4
address allocation completed by UE and SS
Completion of IP Address through DHCP
UE optionally sent IPv6 stateless autoconfiguration Router
solitation message and SS has responded with IPv6 Router
Advertisement message
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
397
ETSI TS 136 523-3 V13.2.0 (2017-03)
HRPD_ZoneRegistrationInd_Type
TTCN-3 Record Type
Name
HRPD_ZoneRegistrationInd_Type
Comment
UATI_Assignm
Null_Type
entCmpl
EAP_AKA_Cm
Null_Type
pl
VSNCP_Config
Cmpl
Null_Type
DHCP_ConfigC
mpl
DHCP_Ind_Type
opt
ICMPv6_Config
Cmpl
Null_Type
opt
UATIAssignment is received
UATIComplete is received
Improved Extensible Authentication protocol for Authentication
and Key agreement started RFC 5448
Message flow in x.s0057 clause 5.2.5.1 Authentication and Key
agreement Completed
optionally After entering PPP LCP Open State, PPP Version
Capability Indicaiton and/or Max PPP Inactivity Timer negotiation
are completed
PDN connection establishment started and UE has sent
PPP Vendor Specific Network Control Protocol Configuration
Request PDN Connection and default bearer establishment is
completed
with possible IPV4 address (optional) and or IPv6 interface ID
(Mandatory) provided
Attach type shall be Handover Attach
UE and SS decided for IPv4 address allocation by DHCP IPv4
address allocation completed by UE and SS
Completion of IP Address through DHCP
UE optionally sent ICMPv6 Router solitation message and SS
has responded with IPv6 Router Advertisement message
DedicatedBearerRelInd_Type
TTCN-3 Record Type
Name
DedicatedBearerRelInd_Type
Comment
VSNP_Termina Null_Type
teCmpl
SCP_ReleaseC Null_Type
opt
mpl
Dedicated bearers are deactivated/ released
Session Configuration Protocol to relase the reservations
exclusively associated with the deleated bearer
Reservation deletion completed
DefaultBearerRelDetachInd_Type
TTCN-3 Record Type
Name
DefaultBearerRelDetachInd_Type
Comment
VSNCP_Termi
Null_Type
opt To Released configured default bearer and hense associated
nateCmpl
Dedicated bearer x.s0057 clause 11.3 and 11.1.1
To indicate the default bearer is released
LCP_Terminate Null_Type
To detach the UE x.s0057 clause 11.2 Detach completed
Cmpl
MobilityFromEUTRACmpl_Type
TTCN-3 Record Type
Name
MobilityFromEUTRACmpl_Type
Comment
ConnectionReq Null_Type
Rcvd
RouteUpdateIn Null_Type
d
TrafficChCmpl
Null_Type
Rcvd
Received Tunneled HRPD Connection Request Message
Received Tunneled HRPD Route Update Message
Received HRPD Traffic Channel Complete in HRPD RAT, after
transmission of tunneled Traffic Channel Assignment,
HRPD Silence Parameters and HRPD Open Loop Parameters
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
398
ETSI TS 136 523-3 V13.2.0 (2017-03)
AdditionalDefBearerEstInd_Type
TTCN-3 Record Type
Name
AdditionalDefBearerEstInd_Type
Comment
VSNCP_Config Null_Type
PDN connection establishment started and UE has sent
Cmpl
PPP Vendor Specific Network Control Protocol Configuration
Request PDN Connection and default bearer establishment is
completed
with possible IPV4 address (optional) and or IPv6 interface ID
(Mandatory) provided
Attach type shall be Handover Attach(pre-registration) or Initial
Attach (if normal registration in HRPD cell)
DHCP_ConfigC DHCP_Ind_Type
opt UE and SS decided for IPv4 address allocation by DHCP IPv4
mpl
address allocation completed by UE and SS
Completion of IP Address through DHCP
ICMPv6_Config Null_Type
opt UE optionally sent ICMPv6 Router solitation message and SS
Cmpl
has responded with IPv6 Router Advertisement message
HRPD_SystemIndication_Type
TTCN-3 Union Type
Name
HRPD_SystemIndication_Type
Comment
Error
Null_Type
InitialAccessPr
obeRcvd
RegAndDefBea
rerEstInd
DedicatedBear
erEstInd
Null_Type
DedicatedBear
erRelInd
DefaultBearerR
elDetachInd
DedicatedBearerRelInd_Type
MovedToDorm
antMode
MobilityFromE
UTRACmpl
Null_Type
AdditionalDefB
earerEstInd
HRPD_ZoneRe
gistrationInd
AdditionalDefBearerEstInd_Type
RegAndDefBearerEstInd_Type
Null_Type
DefaultBearerRelDetachInd_Type
MobilityFromEUTRACmpl_Type
HRPD_ZoneRegistrationInd_Type
Used by SS to indicate any error;
the Actual Error types reported in ASP common part in
CDMA2000_IndicationStatus_Type
Initial Access probe is received;
UE has succesfully performed registration and default bearer
esablishment
Vendor specific network protocol (RFC 3772) procedures to reestablish Dedicated bearer as defined in S.0057 clause 5.5.3.1
(BCM is MS/NW)
or clause 5.5.4.1.1 (BCM = MS-Only) Bearer Configuration
Mode
Dedicated bearers are (re) established
To indicate the Dedicated bearer is released
To Release configured default bearer and hense associated
Dedicated bearer x.s0057 clause 11.3 and 11.1.1
Dedicated bearers are deactivated/released
To detach the UE x.s0057 clause 11.2 Detach completed
The channels are released and UE is moved to PPP dormant
mode/Air interface Idle.
To confirm that Handover from EUTRAN is completed by
receiving Traffic Channel Complete
and the MessageSequence is same as in Traffic Channel
Assignment
UE has successfully performed additional default bearer
establishment (additional PDN)
Initially pre-registered UE detects change in HRPD Zone ID in
SIB and hence updates registration
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
399
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.8.5.4 HRPD_Commands
HRPD_UE_InitStateType
TTCN-3 Enumerated Type
Name
HRPD_UE_InitStateType
Comment
HRPD UE states as defined in C.S0057 clause 3.1
idle_Null
In the Inactive/Null State,
1. there is no physical traffic channel between the UE and the eAN, and no connection exists
between the eAN and the ePCF
2. no PPP link between the UE and the HSGW .
3. The UE may have a Universal Access Terminal Identifier (UATI) that has been assigned by
an eHRPD eAN
dormant
In the Dormant State,
1. no physical traffic channel exists between the UE and the eAN and no connection exists
between the eAN and the ePCF.
2. PPP link between the UE and the HSGW
3. eHRPD DORMANT state equates to the "idle" state referred to in TS 23.402
active_Connected
In the Active/Connected State,
1. a physical traffic channel exists between the UE and the eAN over which data may be sent.
A connection exists between the eAN and the ePCF, and between the ePCF and the HSGW,
2. there is a PPP link between the UE and the HSGW
preregister
The UE is performing pre-register though a different Access network
RegAndDefBearerEst_Type
TTCN-3 Record Type
Name
RegAndDefBearerEst_Type
Comment
InitState
HRPD_UE_InitStateType
RLP_FlowId
RLP_FlowId_Type
AttachType
CDMA2000_AttachType
Associated RLP Flow ID
The Attach Type to be expected in VSNCP procedure
DefaultBearerRelDetach_Type
TTCN-3 Record Type
Name
DefaultBearerRelDetach_Type
Comment
InitState
HRPD_UE_InitStateType
PDN_Id
PDN_Id_Type
RLP_FlowId
RLP_FlowId_Type
UE_NW_Initiat
LCP_DetachInit_Type
ed
PDN_ID of the bearer
Associated RLP Folw ID
If initiated by UE or Network
DedicatedBearerEstRel_Type
TTCN-3 Record Type
Name
DedicatedBearerEstRel_Type
Comment
InitState
HRPD_UE_InitStateType
AssociatedDefa
ultBearer
PDN_Id_Type
Flow_Ids
Flow_IdList_Type
RLP_FlowIds
RLP_FlowIdList_Type
PPP and Air Interface state of UE when the procedure is being
executed
the PDN ID of the associated default bearer;
Gives the APN with which addititonal Dedicated Bearer needs to
be established
Flow_ID's of the multiple dedicated bearers to be
Activated/Deactivated
Associated RLP Folw ID; There is one to one association
between elements
in Flow_IdList_Type and RLP_FlowIdList_Type; ITs a TTCN
programing error otherwise
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
400
AdditionalDefBearerEst_Type
TTCN-3 Record Type
Name
AdditionalDefBearerEst_Type
Comment
used for multiple PDN connections
InitState
HRPD_UE_InitStateType
RLP_FlowId
RLP_FlowId_Type
Associated RLP Flow ID
ETSI
ETSI TS 136 523-3 V13.2.0 (2017-03)
3GPP TS 36.523-3 version 13.2.0 Release 13
401
ETSI TS 136 523-3 V13.2.0 (2017-03)
HRPD_SystemCommand_Type
TTCN-3 Union Type
Name
HRPD_SystemCommand_Type
Comment
ReportInitialAcc Null_Type
esProbe
RegAndDefBea
rerEst
RegAndDefBearerEst_Type
DedicatedBear
erEst
DedicatedBearerEstRel_Type
MoveToDorma
ntState
MoveToActiveS
tate
Null_Type
DedicatedBear
erRel
DedicatedBearerEstRel_Type
DefaultBearerR
elDetach
DefaultBearerRelDetach_Type
MobilityFromE
UTRA
Null_Type
RLP_FlowIdList_Type
SS is expected to report any possible Access probes received on
HRPD Cell;
will be used in situations where UE is not expected to camp on a
HRPD Cell
To complete registeration and establish Default bearer;
Initial UE State is Idle_Null State
Indications upto VSNCP protocol and possible IP signalling over
DHCPv4 and/or ICMPv6 is performed
At the end of procedure, UE is still in Active/Connected state (not
pre-registration);
SS is expected to send InitialAccessProbeRcvd(only if initial
state is not Active and not pre-registration) and
RegAndDefBearerEstInd as an indication for succesful
completion of procedure
Dedicated bearers are established/Activated by VSNP/EMPA
protocol;
PDN ID and RLP flow ID pairs are provided for each Dedicated
bearer
At the end of procedure, UE is still in Active/Connected state
SS is expected to send InitialAccessProbeRcvd (only if initial
state is not Active) and DedicatedBearerEstInd as an indication
for succesful completion of procedure
UE is Active_Connected state and is moved to Dormant state
SS is expected to send MovedToDormantMode
UE is initially Dormant state;
UE is made to Move to Active_Connected State
List of RLP flow Id's (associated with default + dedicated bearer),
need to be established are provided
SS is expected to send InitialAccessProbeRcvd
Dedicated bearers are released/De-Activated by VSNP
terminate and SCP release protocol;
At the end of procedure, UE is still in Active/Connected state (not
pre-registration)
SS is expected to send InitialAccessProbeRcvd (only if initial
state is not Active and not pre-registration) and
DedicatedBearerRelInd as an indication for succesful completion
of procedure
Default bearer is released by VSNCP terminate and SCP release
protocol
UE is made to detach by LCP protocol and Possible Channels
are released
At the end of procedure, UE is in Idle_Null state
Notes:
When Detach is network initiated the sequence is
1. Default bearer (and hence all associated Dedicated bearers)
released by VSNCP termintate
2. UE is detached by LCP terminate procedure
When Detach is UE initiatated, UE may only perform LCP
terminate procedure
SS is expected to send InitialAccessProbeRcvd (only if initial
state is not Active) and DefaultBearerRelDetachInd as an
indication for succesful completion of procedure
Prepare CDMA SS for receiving tunneled HRPD Connection
Request and Route Update tunneled in
ULHandoverPreparationTransfer
Respond with GCSNA encapsulated HRPD Silence Parameters
and HRPD Open Loop Parameters, HRPD Traffic Channel
Assignment to be sent tunneled in
MobilityFromEUTRACommand
Receive Traffic Channel Complete in the HRPD Cell;
After Receiving Traffic Channel Assignment , HRPD Silence
Parameters and HRPD Open Loop Parameters embedded in
EUTRA message MobilityFromEUTRACommand, UE has
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
402
AdditionalDefB
earerEst
AdditionalDefBearerEst_Type
HRPDZoneReg
ister
RegAndDefBearerEst_Type
D.8.6
ETSI TS 136 523-3 V13.2.0 (2017-03)
Tuned to HRPD Radio and transmitted Traffic Channel Complete
in the HRPD Cell
SS is expected to send MobilityFromEUTRACmpl as an
indication for succesful completion of procedure
To establish an additional PDN connection
Initial UE State is Idle_Null State or procedure performed through
pre-registration
Indications upto VSNCP protocol and possible IP signaling over
DHCPv4 and/or ICMPv6 is performed
At the end of procedure, UE is still in Active/Connected state(not
pre-registration);
SS is expected to send InitialAccessProbeRcvd (only if initial
state is not Active and not pre-registration) and
AdditionalDefBearerEstInd as an indication for successful
completion of procedure
To update registeration by a UE already registered and
established Default bearer;
Initial UE State is Idle_Null State
Indications upto VSNCP protocol and possible IP signalling over
DHCPv4 and/or ICMPv6 is performed
At the end of procedure, UE is still in Active/Connected state (not
pre-registration);
SS is expected to send InitialAccessProbeRcvd(only if initial
state is not Active and not pre-registration) and
RegAndDefBearerEstInd as an indication for succesful
completion of procedure
CDMA2000_RTT1X
D.8.6.1 RTT1X_Indications
RTT1X call flows in RTT1x cell
Expected Sequence for Attach (Power Up Attach)
1. Initial AccessProbeRcvd
2. CS_RegistrationStart (Powerup)
3. CS_RegistrationCmpl
Expected Sequence for Detach (Power Down Attach)
1. Initial AccessProbeRcvd
2. CS_RegistrationStart (PowerDown)
3. CS_RegistrationCmpl
Expected Sequence for CSFB Call Establishment
1. Initial AccessProbeRcvd
2. CS_CallEstStart (Origination/ PageResponse)
3. ChAssignCmpl (Extended Channel Assignment is sent)
4. CS_CallEstCompleted (Acknowledgement Order Sent, Service Connect sent, Service Connect Completion received,
Alert Sent/Received and ConnectOrder is received)
Expected Sequence for SRVCC call handover
1. HandoffCmpl
RTT1X_CS_CallType
TTCN-3 Enumerated Type
Name
RTT1X_CS_CallType
Comment
mo
Call is UE oringinated
mt
Call is UE Terminated
mo_Emergency
UE originated Emergency Call
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
403
ETSI TS 136 523-3 V13.2.0 (2017-03)
RTT1XAttachType
TTCN-3 Enumerated Type
Name
RTT1XAttachType
Comment
Ref C.S005 Table 2.7.1.3.2.1-1
powerUpAttach
UE is doing Power up attach REG_Type = '0001'B; it was not previously attached
powerDownAttach
UE is doing power down attach REG_Type = '0011'B; it was previously attached
zoneBasedAttach
UE is doing Zone based attach REG_Type = '0010'B
orderedAttach
UE is doing Ordered attach REG_Type = '0101'B
OtherAttach
Any other Attach REG_Type does not equal above values
CS_RegCmplInd_Type
TTCN-3 Record Type
Name
CS_RegCmplInd_Type
Comment
CS_Registratio RTT1XAttachType
nCmpl
CS power up/down registration is completed
UE Sent Registration message and received an L2
Acknowledgement
Optionally SS can perform Authentication and and has sent
Registration Accepted order
CS_Reg_CallCmplInd_Type
TTCN-3 Record Type
Name
CS_Reg_CallCmplInd_Type
Comment
CS_Registratio RTT1XAttachType
opt
nCmpl
CS_CallEstStar
ted
ChAssignCmpl
RTT1X_CS_CallType
CS_CallEstCo
mpleted
Null_Type
Null_Type
CS power up/down registration is completed; This is omit if
implicit registration is done
UE Sent Registration message and received an L2
Acknowledgement
Optionally SS can perform Authentication and and has sent
Registration Accepted order
UE can also do a implicit registration; i.e. reception of
Origination/reconnect/CallRecovery/Page message
by Base station is treated as implicit registration
Received Origination message for MO and Page Response for
MT
(Extended) Channel Assignment procedure started UE has sent
ConnectionRequestTraffic
Extended Channel assignment is completedUE has sent
TrafficChannelComplete
SS received Service Connect Completion (Mo) or
ConnectOrder(MT) (i.e User Accepted call)
CS_CallCmplInd_Type
TTCN-3 Record Type
Name
CS_CallCmplInd_Type
Comment
CS_CallEstStar RTT1X_CS_CallType
ted
ChAssignCmpl
Null_Type
CS_CallEstCo
Null_Type
mpleted
IsEmergencyC
boolean
all
Received Origination message for MO and Page Response for
MT
(Extended) Channel Assignment procedure started completed
SS received Service Connect Completion (MO) or ConnectOrder
(MT) (i.e User Accepted call)
True indicates the established call is emergency call, false
indicates a normal voice has been established
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
404
ETSI TS 136 523-3 V13.2.0 (2017-03)
ECSFB_CallCmplInd_Type
TTCN-3 Record Type
Name
ECSFB_CallCmplInd_Type
Comment
CS_CallEstStar RTT1X_CS_CallType
ted
HandoffCmpl
Null_Type
CS_CallEstCo
mpleted
IsEmergencyC
all
Null_Type
boolean
Received Tunneled GCSNA encapsulated Origination message
for MO and Page Response for MT call
indicates SS has received HandoffComplete message and the
call is established
SS received Service Connect Completion (MO) or ConnectOrder
(MT) (i.e User Accepted call)
True indicates the established call is emergency call, false
indicates a normal voice has been established
ECAM_CS_CallCmplInd_Type
TTCN-3 Record Type
Name
ECAM_CS_CallCmplInd_Type
Comment
CS_TunneledC RTT1X_CS_CallType
allEstStarted
CS_CallEstStar RTT1X_CS_CallType
ted
ChAssignCmpl
Null_Type
CS_CallEstCo
Null_Type
mpleted
IsEmergencyC
boolean
all
Received Tunneled GCSNA encapsulated Origination message
for MO and Page Response for MT call
Received Origination message for MO and Page Response for
MT
Extended Channel Assignment procedure started completed
SS received Service Connect[MO] or ConnectOrder[MT] (i.e
User Accepted call)
True indicates the established call is emergency call, false
indicates a normal voice has been established
ECSFB_CallRejInd_Type
TTCN-3 Record Type
Name
ECSFB_CallRejInd_Type
Comment
CS_CallEstRej
RTT1X_CS_CallType
ected
IsEmergencyC
all
boolean
SS Received tunneled 1xRTT Origination (M0)/Page Response
(MT) message
Respond with 1xRTT Release Order message
True indicates the established call is emergency call, false
indicates a normal voice has been established
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
405
ETSI TS 136 523-3 V13.2.0 (2017-03)
RTT1X_SystemIndication_Type
TTCN-3 Union Type
Name
RTT1X_SystemIndication_Type
Comment
Error
Null_Type
InitialAccessPr
obeRcvd
CS_Registratio
nCmpl
Null_Type
CS_Reg_CallC
mplInd
CS_Reg_CallCmplInd_Type
CS_CallCmplIn
d
HandoffCmpl
CS_CallCmplInd_Type
MovedToIdleSt
ate
Null_Type
ECSFB_CallC
mplInd
ECSFB_ECAM
_CallCmplInd
ECSFB_CallRe
jInd
ECSFB_CallCmplInd_Type
CS_RegCmplInd_Type
Used by SS to indicate any error; the Actual Error types reported
in ASP common part in CDMA2000_IndicationStatus_Type
Initial Access probe is received
CS power up/down registration is completed
As registration message, and possible Authentication
Registration accepted order are all
sent received on f/r-csch UE at end is in Idle state
CS Registration /implicit registration and Call Indication MO or
MT
UE is in connected state with f/r dtch configured
CS Call Indication MO or MT
UE is in connected state with f/r dtch configured
needed for SRVCC handover of an IMS voice call on LTE to
1XRTT
indicates SS has received HandoffComplete message and the
call is established
The channels are released and UE is moved to Idle state.
CS Call is released by exchange of Release order in both
directions C.S0005 figure B3 and B4
eCSFB Call Indication MO or MT
UE is in connected state with f/r dtch configured
eCSFB ECAM based Call Indication MO or MT
UE is in connected state with f/r dtch configured
eCSFB Call Rejected MO or MT
UE is not camping in 1xRTT
Null_Type
ECAM_CS_CallCmplInd_Type
ECSFB_CallRejInd_Type
D.8.6.2 RTT1X_Commands
CS_Registration_Type
TTCN-3 Record Type
Name
CS_Registration_Type
Comment
AttachType
RTT1XAttachType
IsPreRegistrati
boolean
on
RAND
B32_Type
opt
Indicates if it is done as pre registration
Value is ignored if Attach Type is Power down
(Assumption detach happens only in 1XRTT cell)
RAND [From eNB] to be included in
CSFBParametersResponseCDMA2000,
HandoverFromEUTRAPreparationRequest
Value not present for power down registration
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
406
ETSI TS 136 523-3 V13.2.0 (2017-03)
RTT1X_SystemCommand_Type
TTCN-3 Union Type
Name
RTT1X_SystemCommand_Type
Comment
ReportInitialAcc Null_Type
esProbe
CS_Registratio
n
CS_Registration_Type
CSFB_Call
RTT1X_CS_CallType
CS_Reg_CSFB
_Call
RTT1X_CS_CallType
MobilityFromE
UTRA_1XRTT
Null_Type
CS_OrderedRe
gistration
CS_Registration_Type
E_CSFB_Call
RTT1X_CS_CallType
SS is expected to report any possible Access probes received on
1XRTT Cell;
will be used in situations where UE is not expected to camp on a
1XRTT Cell
Power up attach/ power down attach in 1xRTT cell or Pre
registration (Power up attach)
tunelled through a different RAT
in case of pre-registration attach, the CDMA SS starts by sending
mobilityParameters to be tunneled in
CSFBParametersRequestCDMA2000
SS is expected to send InitialAccessProbeRcvd (only if initial
state is not pre-registration) and CS_RegistrationCmpl as an
indication for succesful completion of procedure
CSFB by a (pre-)registered UE
If the call Type is mt, CDMA SS sends 1x RTT GCSNA
encapsulated General Page to be tunneled in DLInformation
Transfer
SS is expected to send InitialAccessProbeRcvd and
CS_CallCmplInd as an indication for succesful completion of
procedure
UE not previously pre-registered hence performs registration
(Power up attach) and CSFB call
Registration can be implicit registration
SS is expected to send InitialAccessProbeRcvd and
CS_Reg_CallCmplInd as an indication for succesful completion
of procedure
Prepare SS for Mobility from Eutra
CDMA SS sends mobilityParameters to be tunneled in
HandoverFromEUTRAPreparationRequest
Receive tunneled 1xRTT GCSNA Encapsulated Origination
message and MEID in ULHandoverPreparationTransfer
Respond with GCSNA encapsulated 1xRTT Handoff Direction
message to be sent tunneled in MobilityFromEUTRACommand
Receive HandoffCmpl in the 1xRTT Cell;
SS is expected to send HandoffCmpl as an indication for
succesful completion of procedure
ordered registration on (already registered) 1xRTT cell or Pre
registration
Power up attach) through a different RAT. SS triggers the
procedure by sending
Registration Request order (GCSNA encapsulated in case of
pre-registration)
and sends mobilityParameters to be tunneled in
CSFBParametersRequestCDMA2000
SS is expected to send InitialAccessProbeRcvd (only if initial
state is not pre-registration) and CS_RegistrationCmpl as an
indication for succesful completion of procedure
Prepare SS for Enhanced CSFB call
If the call Type is mt, CDMA SS sends 1x RTT GCSNA
encapsulated General Page to be tunneled in DLInformation
Transfer
CDMA SS sends mobilityParameters to be tunneled in
HandoverFromEUTRAPreparationRequest
Receive tunneled 1xRTT GCSNA Encapsulated Origination
(M0)/Page Response (MT) message and MEID in
ULHandoverPreparationTransfer
Respond with GCSNA encapsulated 1xRTT Handoff Direction
message to be sent tunneled in MobilityFromEUTRACommand
Receive HandoffCmpl in the 1xRTT Cell;
SS responds with Alert With Information (MT)/Sevice connect
(MO) in the 1xRTT cell.
SS receives Connect order (MT)/Service Connect Completion
(MO)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
E_CSFB_Call_
ECAM
RTT1X_CS_CallType
E_CSFB_Call_
Reject
RTT1X_CS_CallType
D.8.7
407
ETSI TS 136 523-3 V13.2.0 (2017-03)
SS is expected to send ECSFB_CallCmplInd as an indication
for succesful completion of procedure
Prepare SS for Enhanced CSFB call with Extended channel
assignment
If the call Type is mt, CDMA SS sends 1x RTT GCSNA
encapsulated General Page to be tunneled in DLInformation
Transfer
CDMA SS sends mobilityParameters to be tunneled in
HandoverFromEUTRAPreparationRequest
Receive tunneled 1xRTT GCSNA Encapsulated Origination
(M0)/Page Response (MT) message and MEID in
ULHandoverPreparationTransfer
Respond with GCSNA Encapsulated ECAM message to be
sent tunneled in MobilityFromEUTRACommand
Receive Origination in the 1xRTT Cell;
After extended channel assignment, SS receives Connect order
(MT)/Service Connect Completion (MO)
SS is expected to send ECSFB_ECAM_CallCmplInd as an
indication for succesful completion of procedure
Prepare SS for Enhanced CSFB call, which needs to be rejected
If the call Type is mt, CDMA SS sends 1x RTT GCSNA
encapsulated General Page to be tunneled in DLInformation
Transfer
CDMA SS sends mobilityParameters to be tunneled in
HandoverFromEUTRAPreparationRequest
Receive tunneled 1xRTT GCSNA Encapsulated Origination
(M0)/Page Response (MT) message and MEID in
ULHandoverPreparationTransfer
Respond with GCSNA encapsulated 1xRTT Release Order
message to be sent tunneled in DLInformation Transfer
SS is expected to send ECSFB_CallRejInd as an indication for
succesful completion of procedure
System_Interface
CDMA2000_SystemRequest_Type
TTCN-3 Union Type
Name
CDMA2000_SystemRequest_Type
Comment
Cell
CDMA2000_CellConfigRequest_
configure/release a cell
Type
CellAttenuation CDMA2000_CellAttenuationList_
Type
List
CDMA2000_SystemConfirm_Type
TTCN-3 Union Type
Name
CDMA2000_SystemConfirm_Type
Comment
confirmations for system configuration; in general to be sent after the configuration has been done
Cell
Null_Type
(no further parameters from SS)
CellAttenuation Null_Type
(no further parameters from SS)
List
NOTE 1: the confirmation shall be sent when all cells have
changed power levels
NOTE 2: for the CellId in the common ASP part the same rules
are applied as for the CDMA2000 SYSTEM REQ
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
408
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_SYSTEM_CTRL_REQ
TTCN-3 Record Type
Name
CDMA2000_SYSTEM_CTRL_REQ
Comment
Common
CDMA2000_ReqAspComm
TimingInfo depends on respective primitive:
onPart_Type
Request
CDMA2000_SystemReque
- Cell
st_Type
TimingInfo: 'now' (in general)
- CellAttenuationList
TimingInfo: 'now' (in general, but activation time may be used
also)
CDMA2000_SYSTEM_CTRL_CNF
TTCN-3 Record Type
Name
CDMA2000_SYSTEM_CTRL_CNF
Comment
Common
CDMA2000_CnfAspComm
TimingInfo is ignored by TTCN
onPart_Type
=> SS may set TimingInfo to "None"
Confirm
CDMA2000_SystemConfir
m_Type
CDMA2000_SystemCommand_Type
TTCN-3 Union Type
Name
CDMA2000_SystemCommand_Type
Comment
HRPD
HRPD_SystemCommand_Type
HRPD Specific System commands
RTT1X
RTT1X_SystemCommand_Type
1XRTT specific System commands
CDMA2000_SYSTEM_CMD
TTCN-3 Record Type
Name
CDMA2000_SYSTEM_CMD
Comment
Common
CDMA2000_ReqAspComm
onPart_Type
Command
CDMA2000_SystemComm
and_Type
Routing info will be none generally;
TimingInfo is generally now but activation time may be used also
for all System commands
Cnf and Follow on flags are both false
HRPD or 1XRTT System commands
CDMA2000_SystemIndication_Type
TTCN-3 Union Type
Name
CDMA2000_SystemIndication_Type
Comment
HRPD
HRPD_SystemIndication_Type
RTT1X
RTT1X_SystemIndication_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
409
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_SYSTEM_IND
TTCN-3 Record Type
Name
CDMA2000_SYSTEM_IND
Comment
Common
CDMA2000_IndAspCommo
nPart_Type
Indication
CDMA2000_SystemIndicati
on_Type
The SS shall provide TimingInfo depending on the respective
indication:
- Error
TimingInfo: related to the error (if available)
- HRPD/RTT1X Procedure completion
The timing info corresponding to logical completion of the
complete procedure
includes completion of all sub protocols
CDMA2000_RLP_FLOW_COMMON_IND
TTCN-3 Record Type
Name
CDMA2000_RLP_FLOW_COMMON_IND
Comment
ASP to receive PDUs from RLP Packet Flows
Common
CDMA2000_IndAspCommo
CellId : identifier of the cell
nPart_Type
RoutingInfo : RLP Flow id
TimingInfo : time when RLP SDU's has been completely received
Data
CDMA2000_U_PlaneData_
Type
CDMA2000_RLP_FLOW_COMMON_REQ
TTCN-3 Record Type
Name
CDMA2000_RLP_FLOW_COMMON_REQ
Comment
ASP to send PDUs to RLP Packet flows
Common
CDMA2000_ReqAspComm
CellId : identifier of the cell
onPart_Type
RoutingInfo : RLP Flow id
TimingInfo : starting point when to start sending sequence of
data PDUs
e.g.
TimeStampLong_Type = X, subframe number = x;
U_Plane.SubframeDataList (i).SubframeOffset := offset_i;
=> U_Plane.SubframeDataList(i).PduSduList shall be sent out
at
TimeStampLong_Type = X + ((x + offset_i) / 4);
subframe number = (x + offset_i) mod 4
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
U_Plane
CDMA2000_U_Plane_Req
uest_Type
CDMA2000_SYSTEM_PORT
TTCN-3 Port Type
Name
CDMA2000_SYSTEM_PORT
Comment
CDMA2000 PTC: Port for system configuration
out
CDMA2000_SYSTEM_CTRL_RE
Q
in
CDMA2000_SYSTEM_CTRL_CN
F
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
410
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_SYSCMD_IND_PORT
TTCN-3 Port Type
Name
CDMA2000_SYSCMD_IND_PORT
Comment
CDMA2000 PTC: Port for system indications/Commands
out
CDMA2000_SYSTEM_CMD
in
CDMA2000_SYSTEM_IND
CDMA2000_RLP_FLOW_PORT
TTCN-3 Port Type
Name
CDMA2000_RLP_FLOW_PORT
Comment
CDMA2000 PTC: Port for RLP SDU's to be sent on RLP packet data streams
out
CDMA2000_RLP_FLOW_COMM
ON_REQ
in
CDMA2000_RLP_FLOW_COMM
ON_IND
D.9
CDMA2000_CommonDefs
type definitions used by CDMA2000 and EUTRA
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
411
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_CommonDefs: Basic Type Definitions
TTCN-3 Basic Types
SearchWindowSize_Type
integer (0..15)
BandclassCDMA2000_Ty
pe
ARFCN_ValueCDMA2000
_Type
PhysCellIdCDMA2000_Ty
pe
ProtRev_Type
OpenLoopAdjust_Type
BCD_Digit_Type
TMSI_Code_Type
EncryptionMode_Type
integer (0..31)
TMSI_ZoneLen_Type
integer (1..8)
SectorID_HRPD_Type
B128_Type
PilotOffset_Type
integer (-31..0)
PowerIor_Type
integer (-127..0)
PowerIoc_Type
integer (-127..0)
Attenuation_Type
SystemType_Type
integer (0..127)
integer (0..255)
ColorCode_Type
ReverseLinkMACIndex_T
ype
integer (0..255)
integer (0..383)
Search Window as in 36.331 ASN.1 definition
for
SystemInformationBlockType8.searchWindow
Size
Band class defined as in 36.331 ASN.1
definition for BandclassCDMA2000
ARFCN for CDMA2000 cell as in 36.331
ASN.1 definition for ARFCN_ValueCDMA2000
PN offset for CDMA2000 cell as in 36.331
ASN.1 definition for PhysCellIdCDMA2000
protocol revision
9.4.6.2.6 of C.S0024
To represent BCD digit of MCC
integer (0..2047)
integer (0..511)
integer (0..255)
integer (0..255)
integer (0..9)
O4_Type
integer (0..7)
C.S0005 table 3.7.4.5-1 & 3.7.5.7-3
0 ... Encryption disabled
1 ... Encryption with ORYX algorithm for User
Info and
Enhanced Cellular Msg Encryption
Algorithm for Signalling
2 ... Encryption with Rijndael algorithm
3-7 ... reserved
TMSI Zone Lenght; On encoding this is
encoded to B4_Type
Sector ID for HRPD as in 36.331 ASN.1
definition for
CellGlobalIdCDMA2000.cellGlobalIdHRPD
Represents the offset i.e. Pilot Channel power
to total cell power(dB);
By default shall be set to -7
127 selected Max value by 7 bits
Represets the cell total Tx power Ior
(dBm/1.23 MHz)
Represets the cell total AWGN power Ioc
(dBm/1.23 MHz) which is independent of cell
0 to 2 are allowed and 3 to 255 are reserved
13.1 of C.S0024
7.11.6.2.1 of C.S0024
C.S0024 clause 12.4.1.3.2.2
MCC_Type
TTCN-3 Record of Type
Name
MCC_Type
Comment
Represents Mobile Country Code
record length (3) of BCD_Digit_Type
TMSI_Zone_Type
TTCN-3 Record of Type
Name
TMSI_Zone_Type
Comment
TMSI Zone 1 to 8 octets
record length (1..8) of B8_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
412
ETSI TS 136 523-3 V13.2.0 (2017-03)
TMSI_Type
TTCN-3 Record Type
Name
TMSI_Type
Comment
Globally unique TMSI as defined in C.s0005 clause 3.7.2.3.2.19
TMSI_ZoneLen TMSI_ZoneLen_Type
Length of TMSI_Zone 1..8
TMSI_Zone
TMSI_Zone_Type
TMSI_ZoneLen octets of TMSI_Zone
TMSI_Code
TMSI_Code_Type
TMSI code
SectorID_RTT1X_Type
TTCN-3 Record Type
Name
SectorID_RTT1X_Type
Comment
Sector ID for 1XRTT acc. to C.S0005 clause 3.7.2.3.2.1 and as in 36.331 ASN.1 clause 6.3.4,
definition of CellGlobalIdCDMA2000.cellGlobalId1XRTT
BaseId
B16_Type
Base station identification.
The base station shall set this field to its identification number
NID
B16_Type
Network identification
This field serves as a sub-identifier of a system as defined by the
owner of the SID.
The base station shall set this field to the network identification
number for this network
SID
B15_Type
System identification. set to the system identification number for
this system
CarrierFreqCDMA2000_Type
TTCN-3 Record Type
Name
CarrierFreqCDMA2000_Type
Comment
Carrier Frequency for CDMA2000 cell as in 36.331 ASN.1 definition for CarrierFreqCDMA2000;
contains Band class 5 bit and Channel number 11 bit part of Sector Channel over head message
contained in 24 bit Channel IE
BandClass
BandclassCDMA2000_Typ
e
ARFCN
ARFCN_ValueCDMA2000_
Type
CDMA2K_Type
TTCN-3 Enumerated Type
Name
CDMA2K_Type
Comment
CDMA 2000 Type for CDMA2000 cell as in 36.331 ASN.1 definition for CDMA2000-Type
type1XRTT
typeHRPD
CellGlobalIdCDMA2000_Type
TTCN-3 Union Type
Name
CellGlobalIdCDMA2000_Type
Comment
CDMA 2000 Type Sector ID of the Cell as in 36.331 ASN.1 definition CellGlobalIdCDMA2000
RTT1X
SectorID_RTT1X_Type
HRPD
SectorID_HRPD_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
413
ETSI TS 136 523-3 V13.2.0 (2017-03)
ReverseRateLimit_Type
TTCN-3 Enumerated Type
Name
ReverseRateLimit_Type
Comment
Table 9.9.6.3-2 of C.S0024;
set to the highest data rate that the access terminal is allowed to use on the Reverse Traffic
Channel;
10 Reserved values
kbps0
kbps9_6
kbps19_2
kbps38_4
kbps76_8
kbps153_6
resrv1
resrv2
resrv3
resrv4
resrv5
resrv6
resrv7
resrv8
resrv9
resrv10
PacketApplication_Type
TTCN-3 Enumerated Type
Name
PacketApplication_Type
Comment
Type of Packet Application to be used in Stream protocol
enhMultiFlowPacketA
pp
ControlChannelRate_Type
TTCN-3 Enumerated Type
Name
ControlChannelRate_Type
Comment
Determines the MAC configuration for Control Channel
macIndex2
macIndex3
CDMA2000_CellId_Type
TTCN-3 Enumerated Type
Name
CDMA2000_CellId_Type
Comment
cdma2000_Cell_Non
Specific
cdma2000_Cell15
HRDP Cell
cdma2000_Cell16
HRDP Cell
cdma2000_Cell17
HRDP Cell
cdma2000_Cell18
HRDP Cell
cdma2000_Cell19
RTT1X Cell
cdma2000_Cell20
RTT1X Cell
cdma2000_Cell21
RTT1X Cell
cdma2000_Cell22
RTT1X Cell
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
414
ETSI TS 136 523-3 V13.2.0 (2017-03)
SearchWindowSizeRecord_Type
TTCN-3 Record Type
Name
SearchWindowSizeRecord_Type
Comment
SearchWindow SearchWindowSize_Type
Search Window for Active Cells
_Active
SearchWindow SearchWindowSize_Type
Search Window for Neighbor Cells
_Neighbor
SearchWindow SearchWindowSize_Type
Search Window for Rest Cells
_Remaining
D.10
EUTRA_ASP_CDMA2000TunnellingDefs
ASP definitions for tunnelling of CDMA2000 messages e.g. during CDMA2000 pre-registration
EUTRA_ASP_CDMA2000TunnellingDefs: Basic Type Definitions
TTCN-3 Basic Types
TunneledInfoCDMA2000
MEID_Type
CDMA2000_MSG_REQ
CDMA2000_MSG_IND
octetstring
ULHandoverPreparationTransfer_r8_IEs
.meid
CDMA2000_UL_Container_Type
CDMA2000_DL_Container_Type
UL_TunneledInfoCDMA2000
TTCN-3 Record Type
Name
UL_TunneledInfoCDMA2000
Comment
Msg
TunneledInfoCDMA2000
Meid
MEID_Type
opt
OCTET STRING
ASN.1 type: BIT STRING (SIZE (56))
used to tunnel meid received from UE in
ULHandoverPreparationTransfer for 1xRTT,
not present other wise
CDMA2000_UL_Container_Type
TTCN-3 Record Type
Name
CDMA2000_UL_Container_Type
Comment
CDMA2000Typ CDMA2000_Type
e
UL_Msg
UL_TunneledInfoCDMA200
0
ASN.1 type: type1XRTT, typeHRPD
DL_TunneledInfoCDMA2000
TTCN-3 Record Type
Name
DL_TunneledInfoCDMA2000
Comment
Msg
TunneledInfoCDMA2000
OCTET STRING
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
415
ETSI TS 136 523-3 V13.2.0 (2017-03)
CDMA2000_DL_Container_Type
TTCN-3 Record Type
Name
CDMA2000_DL_Container_Type
Comment
CDMA2000Typ CDMA2000_Type
e
DL_Msg
DL_TunneledInfoCDMA200
0
ASN.1 type: type1XRTT, typeHRPD
OCTET STRING
CDMA2000_TUNNELLING_PORT
TTCN-3 Port Type
Name
CDMA2000_TUNNELLING_PORT
Comment
EUTRA PTC: Port to deal with tunnelling of CDMA2000 messages
out
CDMA2000_MSG_REQ
in
CDMA2000_MSG_IND
D.11
EUTRA_ASP_VirtualNoiseDefs
ASP definitions for virtual noise generation in EUTRA cells.
The noise is configured for an already existing EUTRA cell.
For UEs with 2 antenna connectors the AWGN (Additive white Gaussian noise) signals applied to each receiver
antenna connector shall be uncorrelated.
EUTRA_ASP_VirtualNoiseDefs: Basic Type Definitions
TTCN-3 Basic Types
EUTRA_VngConfigConfir
m_Type
Null_Type
EUTRA_VngConfigInfo_Type
TTCN-3 Record Type
Name
EUTRA_VngConfigInfo_Type
Comment
Bandwidth
Dl_Bandwidth_Type
NocLevel
integer
Bandwidth to be used for the noise
(in general the same bandwidth as for the associated EUTRA
cell)
Noc level; calculation is according to 36.523-3 cl 7.22
EUTRA_VngConfigRequest_Type
TTCN-3 Union Type
Name
EUTRA_VngConfigRequest_Type
Comment
configure/activate noise for a given cell;
NOTE: it is assumed the the associated EUTRA cell has been created beforehand
Configure
EUTRA_VngConfigInfo_Type
configuration of the virtual noise generator;
regardless of the power level the noise generator is off before it
gets activated for this cell;
in case the configuration needs to be changed during a test, the
noise generator shall be deactivated for this cell
Activate
Null_Type
noise is activated (switched on) for the given cell acc. to the
previous configuration;
while being active the configuration shall not be modified
Deactivate
Null_Type
deactivate noise for given cell
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
416
ETSI TS 136 523-3 V13.2.0 (2017-03)
EUTRA_VNG_CTRL_REQ
TTCN-3 Record Type
Name
EUTRA_VNG_CTRL_REQ
Comment
Common
ReqAspCommonPart_Type
Request
CellId : as for the associated EUTRA cell
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=true; FollowOnFlag:=false
EUTRA_VngConfigRequest
_Type
EUTRA_VNG_CTRL_CNF
TTCN-3 Record Type
Name
EUTRA_VNG_CTRL_CNF
Comment
Common
CnfAspCommonPart_Type
Confirm
TimingInfo is ignored by TTCN (apart from EnquireTiming)
=> SS may set TimingInfo to "None"
EUTRA_VngConfigConfirm
_Type
EUTRA_VNG_PORT
TTCN-3 Port Type
Name
EUTRA_VNG_PORT
Comment
EUTRA PTC: Port for virtual noise generator
out
EUTRA_VNG_CTRL_REQ
in
EUTRA_VNG_CTRL_CNF
D.12
UTRAN_ASP_VirtualNoiseDefs
ASP definitions for virtual noise generation in UTRAN cells.
The noise is configurated for an already existing UTRAN cell.
NOTE: For the time being VNG is applicable for UTRAN FDD only as acc. to TS 36.304 clause 5.2.4.5 there is no
quality based measurement for UTRAN TDD, GERAN or CDMA2000
UTRAN_ASP_VirtualNoiseDefs: Basic Type Definitions
TTCN-3 Basic Types
UTRAN_VngConfigConfir
m_Type
Null_Type
UTRAN_VngConfigInfo_Type
TTCN-3 Record Type
Name
UTRAN_VngConfigInfo_Type
Comment
IocLevel
integer
Ioc level; calculation is testcase specific
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
417
ETSI TS 136 523-3 V13.2.0 (2017-03)
UTRAN_VngConfigRequest_Type
TTCN-3 Union Type
Name
UTRAN_VngConfigRequest_Type
Comment
configure/activate noise for a given cell;
NOTE: it is assumed the the associated UTRAN cell has been created beforehand
Configure
UTRAN_VngConfigInfo_Type
configuration of the virtual noise generator;
regardless of the power level the noise generator is off before it
gets activated for this cell;
in case the configuration needs to be changed during a test, the
noise generator shall be deactivated for this cell
Activate
Null_Type
noise is activated (switched on) for the given cell acc. to the
previous configuration;
while being active the configuration shall not be modified
Deactivate
Null_Type
deactivate noise for given cell
UTRAN_VNG_CTRL_REQ
TTCN-3 Record Type
Name
UTRAN_VNG_CTRL_REQ
Comment
CellId
integer
Request
UTRAN_VngConfigRequest
_Type
id of associated UTRAN cell
UTRAN_VNG_CTRL_CNF
TTCN-3 Record Type
Name
UTRAN_VNG_CTRL_CNF
Comment
CellId
integer
Confirm
UTRAN_VngConfigConfirm
_Type
id of associated UTRAN cell
UTRAN_VNG_PORT
TTCN-3 Port Type
Name
UTRAN_VNG_PORT
Comment
UTRAN PTC: Port for virtual noise generator
out
UTRAN_VNG_CTRL_REQ
in
UTRAN_VNG_CTRL_CNF
D.13
WLAN_ASP_TypeDefs
WLAN_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_WLAN_MaxNum
berOfCells
integer
3
ETSI
Only one cell is foreseen to be
used. defined 3 just for
completeness.
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
418
WLAN_ASP_TypeDefs: Basic Type Definitions
TTCN-3 Basic Types
WLAN_ChannelNumber_T
ype
integer (1..2047)
WLAN_BeaconRSSI_Type
integer (0..255)
WLAN_ChannelUtilization
Type
WLAN_AttenuationValue_
Type
WLAN_TimeStamp_Type
integer (0..255)
Channel Number of WLAN Channel
1 to 14 belong to 2.4 Ghz ISM band
131-138 belong to 3.6 Ghz ISM band
36,40,44,48,52,56,60,64,100,104,108,112,116
,120,124,128,132,136,140,149,153,157,161&1
65 belong to 5Ghz ISM band
Other channel numbers may be defined in
future for other bands and are reserved until
defined
Channel number uniquely identifies the
frequency
WLAN Beacon RSSI is defined in IEEE
802.11-2012, Part 11 table 6.7 as integer 100..40 but defined in 36.331/25.331 as
integer(0..255) so actual beacon RSSI = value
-100, and values 141..255 are not used or
spares
As defined in in IEEE 802.11-2012, Part 11
clause 8.4.2.20 used in BSS load element
integer (0..127)
O8_Type
TimeStamp field (TSF) timer in microseconds
as defined in IEEE 802.11-2012 clause
8.4.1.10
WLAN_Band_Type
TTCN-3 Enumerated Type
Name
WLAN_Band_Type
Comment
Band2_4Ghz
Band2_4Ghz = 2.4 Ghz ISM band
Band5Ghz
Band5Ghz = 5Ghz ISM band
Band3_6Ghz
Band3_6Ghz = 3.6 Ghz ISM band
WLAN_CellId_Type
TTCN-3 Enumerated Type
Name
WLAN_CellId_Type
Comment
wlan_Cell_NonSpecifi
c
wlan_Cell27
WLAN AP in EUTRA environment
wlan_Cell39
WLAN AP in UTRA environment
WLAN_RoutingInfo_Type
TTCN-3 Union Type
Name
WLAN_RoutingInfo_Type
Comment
None
Null_Type
place holder for any possible extensions, currently only none
defined
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
419
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_TimingInfo_Type
TTCN-3 Union Type
Name
WLAN_TimingInfo_Type
Comment
TimeStamp
WLAN_TimeStamp_Type
Now
Null_Type
None
Null_Type
to be used in REQ ASPs when there is no 'activation time'
only to be used in WLAN_AP_SYSTEM_CTRL_CNF
WLAN_ReqAspControlInfo_Type
TTCN-3 Record Type
Name
WLAN_ReqAspControlInfo_Type
Comment
CnfFlag
boolean
true => SS shall send CNF:
when the REQ is with no timing information (no activation time),
SS shall send the confirmation when the configuration is done,
i.e. when the test case may continue.
Example:
when there is a configuration follow by a send event it shall not
be necessary to have a wait timer in between but the CNF
triggers the send event or system Command.
If there are other triggers e.g. like the UE sending a message,
CnfFlag shall be set to false by the test case to avoid racing
conditions with the CNF and the signalling message.
When there is an activation time SS shall send the CNF after the
configuration has been scheduled;
that means SS shall not wait until the activation time has been
expired.
FollowOnFlag
boolean
false => no further (related) information
true: further related information will be sent to SS; currently this
value is not foreseen to be used.
WLAN_ReqAspCommonPart_Type
TTCN-3 Record Type
Name
WLAN_ReqAspCommonPart_Type
Comment
CellId
WLAN_CellId_Type
RoutingInfo
WLAN_RoutingInfo_Type
TimingInfo
WLAN_TimingInfo_Type
ControlInfo
WLAN_ReqAspControlInfo_
Type
WLAN_ErrorIndication_Type
TTCN-3 Record Type
Name
WLAN_ErrorIndication_Type
Comment
System
integer
any other error: may be SS specific error code; this will not be
evaluated by TTCN;
e.g. an error shall be raised when the UE performs an out of
sequence signalling
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
420
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_IndicationStatus_Type
TTCN-3 Union Type
Name
WLAN_IndicationStatus_Type
Comment
Ok
Null_Type
Error
WLAN_ErrorIndication_Type
WLAN_IndAspCommonPart_Type
TTCN-3 Record Type
Name
WLAN_IndAspCommonPart_Type
Comment
CellId
WLAN_CellId_Type
RoutingInfo
WLAN_RoutingInfo_Type
TimingInfo
WLAN_TimingInfo_Type
Status
WLAN_IndicationStatus_Ty
pe
WLAN_ConfirmationResult_Type
TTCN-3 Union Type
Name
WLAN_ConfirmationResult_Type
Comment
Success
Null_Type
Error
integer
may contain SS specific error code; this will not be evaluated by
TTCN
WLAN_CnfAspCommonPart_Type
TTCN-3 Record Type
Name
WLAN_CnfAspCommonPart_Type
Comment
CellId
WLAN_CellId_Type
RoutingInfo
WLAN_RoutingInfo_Type
TimingInfo
WLAN_TimingInfo_Type
Result
WLAN_ConfirmationResult
Similar definition as EUTRA
_Type
WLAN_Attenuation_Type
TTCN-3 Union Type
Name
WLAN_Attenuation_Type
Comment
attenuation of the reference power
Value
WLAN_AttenuationValue_Type
Off
Null_Type
cell power reference power reduced by the given attenuation
(value is in dB)
for non suitable off cell we specify an explicit "Off" value here
WLAN_CellAttenuation_Type
TTCN-3 Record Type
Name
WLAN_CellAttenuation_Type
Comment
CellId
WLAN_CellId_Type
Attenuation
WLAN_Attenuation_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
421
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_CellAttenuationList_Type
TTCN-3 Record of Type
Name
WLAN_CellAttenuationList_Type
Comment
record length(1..tsc_WLAN_MaxNumberOfCells) of WLAN_CellAttenuation_Type
WLAN_InitialCellPower_Type
TTCN-3 Record Type
Name
WLAN_InitialCellPower_Type
Comment
BeaconRSSI
WLAN_BeaconRSSI_Type
Attenuation
WLAN_Attenuation_Type
maximum value of beacon RSSI
a cell is initialised with this Beacon RSSI;
its value is the upper bound of the Beacon RSSI during the test
case
initial attenuation Cell is off
WLAN_Revision_Type
TTCN-3 Enumerated Type
Name
WLAN_Revision_Type
Comment
Rev_2012
802.11-2012, specified to be used in corespecs
Rev_n
802.11n
WLAN_ChannelBandwidth_Type
TTCN-3 Enumerated Type
Name
WLAN_ChannelBandwidth_Type
Comment
bw5
5 Mhz
bw10
10 Mhz
bw20
20 Mhz
bw40
40 Mhz
bw80
80 Mhz
WLAN_Identifiers_Type
TTCN-3 Record Type
Name
WLAN_Identifiers_Type
Comment
SSID
octetstring length (1..32)
BSSID
O6_Type
HESSID
O6_Type
opt
opt
opt
WLAN_Hotspot_Version_Type
TTCN-3 Enumerated Type
Name
WLAN_Hotspot_Version_Type
Comment
None
no hotspot certification
Rev_2
Refered in core spec; Hotspot Revision 2.0 release 2
Rev_1
Hotspot Revision 1.0
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
422
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_AP_Parameters_Type
TTCN-3 Record Type
Name
WLAN_AP_Parameters_Type
Comment
Parameters specific to WLAN AP
WLAN_Band
WLAN_Band_Type
ChannelNumbe WLAN_ChannelNumber_Ty
pe
r
ChannelBandwi WLAN_ChannelBandwidth_
Type
dth
WLAN_Identifie WLAN_Identifiers_Type
rs
WLAN_Revisio WLAN_Revision_Type
n
WLAN_Hotspot WLAN_Hotspot_Version_T
ype
_Version
WLAN band and channel number identify the frequency
Channel Bandwidth of 802.11
defined in 36.331, need to figure out how to import or define an
equivalent
Version of WLAN AP, core specs specify it to be 802.11-2012
Hotspot certification version, Core spec specify it is Hotspot 2.0
WLAN_PDN_AddressInfo_Type
TTCN-3 Record Type
Name
WLAN_PDN_AddressInfo_Type
Comment
UE_IPAddressI charstring
Pv4
UE_IPAddressI charstring
Pv6
ePDG_IPAddre charstring
ssIPv4
ePDG_IPAddre charstring
ssIPv6
PCSCF_IPAddr charstring
essIPv4
PCSCF_IPAddr charstring
essIPv6
PDN IP Address of the UE in the 3GPP network
PDN IP Address of the UE in the 3GPP network
IP address of the ePDG in the non-3GPP network
IP address of the ePDG in the non-3GPP network
IP address of the P-CSCF (3GPP network)
IP address of the P-CSCF (3GPP network)
WLAN_EAP_AKA_Cntrl_Type
TTCN-3 Record Type
Name
WLAN_EAP_AKA_Cntrl_Type
Comment
configurable parameters for EAP AKA
IMSI
hexstring
IMSI/USIM of UE
RAND
B128_Type
RAND to be used in initial key derivation
AuthK
B128_Type
Authentication secret key shared between AAA-server and USIM
IPsec_ePDG_Cntrl_Type
TTCN-3 Record Type
Name
IPsec_ePDG_Cntrl_Type
Comment
Parameters to be used for all IPsec security associations between UE and ePDG
IntegrityAlgorith IPsec_IntegrityAlgorithm_T
m
ype
CipheringAlgori IPsec_CipheringAlgorithm_
Type
thm
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
423
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_AP_CellConfigInfo_Type
TTCN-3 Record Type
Name
WLAN_AP_CellConfigInfo_Type
Comment
WLAN_AP_Par WLAN_AP_Parameters_Ty
pe
ameters
InitialCellPower WLAN_InitialCellPower_Ty
pe
Parameters for WLAN AP
Power level parameters
WLAN_ePDG_ConfigInfo_Type
TTCN-3 Record Type
Name
WLAN_ePDG_ConfigInfo_Type
Comment
PDN_AddressI
WLAN_PDN_AddressInfo_
Type
nfo
IPsec_SA
IPsec_ePDG_Cntrl_Type
EAP_AKA_Cntr WLAN_EAP_AKA_Cntrl_Ty
l
pe
Various IP Addresses to be used
Parameters for ePDG secure tunnels
Parameters for EAP AKA control
WLAN_AP_CellConfigRequest_Type
TTCN-3 Union Type
Name
WLAN_AP_CellConfigRequest_Type
Comment
AddOrReconfig WLAN_AP_CellConfigInfo_Type
for cell configuration:
ure
CellId : identifier of the cell to be configured
RoutingInfo : None
TimingInfo : Now (for initial configuration and for reconfiguration
in general)
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
Release
Null_Type
to remove a cell completely CellId : identifier of the cell to be released; Cell_NonSpecific, in
case all cells shall be released
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
WLAN_ePDG_ConfigRequest_Type
TTCN-3 Union Type
Name
WLAN_ePDG_ConfigRequest_Type
Comment
Configuration of ePDG and AAA-server emulation
AddOrReconfig WLAN_ePDG_ConfigInfo_Type
to setup configuration of ePDG and AAA-server emulation
ure
Release
Null_Type
to release the ePDG/AAA-server emulation
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
424
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_OffloadSpecificParams_Type
TTCN-3 Record Type
Name
WLAN_OffloadSpecificParams_Type
Comment
parameters that are used for offload to/from WLAN and controlled by Hotspot 2.0 version 2
ChannelUtilisati WLAN_ChannelUtilizationT
opt omit means unchanged,
ype
on
if present AP transmits this parameter in BSS Load element
IEEE 802.11-2012 clause 8.4.2.30
BackHaulDLBa O4_Type
opt Omit means unchanged, DL WAN bandwidth in kbps
ndwidth
If present AP hotspot uses this value in WAN Metrics element
Hotspot 2.0 release 2 clause 4.4
BackHaulULBa O4_Type
opt Omit means unchanged, UL WAN bandwidth in kbps
ndwidth
If present AP hotspot uses this value in WAN Metrics element
Hotspot 2.0 release 2 clause 4.4
WLAN_AP_SystemRequest_Type
TTCN-3 Union Type
Name
WLAN_AP_SystemRequest_Type
Comment
Cell
WLAN_AP_CellConfigRequest_T
configure/release a cell
ype
CellAttenuation WLAN_CellAttenuationList_Type
power attenuation for one or several cells, WLAN AP;
List
all cells included in the list shall be changed at the same time;
all cells in the list shall reach the new cell power within a
maximum of 100ms (10 frames)
OffloadSpecific WLAN_OffloadSpecificParams_T
parameter used in offload decisions
ype
Params
WLAN_AP_SystemConfirm_Type
TTCN-3 Union Type
Name
WLAN_AP_SystemConfirm_Type
Comment
confirmations for system configuration; in general to be sent after the configuration has been done
Cell
Null_Type
(no further parameters from SS)
CellAttenuation Null_Type
(no further parameters from SS)
List
NOTE 1: the confirmation shall be sent when all cells have
changed power levels
NOTE 2: for the CellId in the common ASP part the same rules
are applied as for theWLAN SYSTEM REQ
OffloadSpecific Null_Type
(no further parameters from SS)
Params
WLAN_ePDG_SystemRequest_Type
TTCN-3 Union Type
Name
WLAN_ePDG_SystemRequest_Type
Comment
ePDG
WLAN_ePDG_ConfigRequest_Ty setup/release configuration of ePDG and AAA-server emulation
pe
WLAN_ePDG_SystemConfirm_Type
TTCN-3 Union Type
Name
WLAN_ePDG_SystemConfirm_Type
Comment
confirmations for system configuration; in general to be sent after the configuration has been done
ePDG
Null_Type
(no further parameters from SS)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
425
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_AP_SYSTEM_CTRL_REQ
TTCN-3 Record Type
Name
WLAN_AP_SYSTEM_CTRL_REQ
Comment
Common
WLAN_ReqAspCommonPa
TimingInfo depends on respective primitive:
rt_Type
Request
WLAN_AP_SystemRequest
- Cell
_Type
TimingInfo: 'now' (in general)
- CellAttenuationList
TimingInfo: 'now' (in general, but activation time may be used
also)
WLAN_ePDG_SYSTEM_CTRL_CNF
TTCN-3 Record Type
Name
WLAN_ePDG_SYSTEM_CTRL_CNF
Comment
Common
WLAN_CnfAspCommonPar
CellId, RoutingInfo and TimingInfo are ignored by TTCN
t_Type
Confirm
WLAN_ePDG_SystemConfi
rm_Type
WLAN_ePDG_SYSTEM_CTRL_REQ
TTCN-3 Record Type
Name
WLAN_ePDG_SYSTEM_CTRL_REQ
Comment
Common
WLAN_ReqAspCommonPa
CellId : wlan_Cell_NonSpecific
rt_Type
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
Request
WLAN_ePDG_SystemRequ
est_Type
WLAN_AP_SYSTEM_CTRL_CNF
TTCN-3 Record Type
Name
WLAN_AP_SYSTEM_CTRL_CNF
Comment
Common
WLAN_CnfAspCommonPar
TimingInfo is ignored by TTCN
t_Type
=> SS may set TimingInfo to "None"
Confirm
WLAN_AP_SystemConfirm
_Type
WLAN_ePDG_SystemCommand_Type
TTCN-3 Union Type
Name
WLAN_ePDG_SystemCommand_Type
Comment
IpsecTunnelDis Null_Type
To trigger SS for ePDG initiated tunnel disconnection procedure
cCmd
acc. to 24.234 clause 8.3.1.2 and 8.3.2.1 (e.g. step 11 of Table
6.4.3.11-1 in 36.508)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
426
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_AP_SystemCommand_Type
TTCN-3 Union Type
Name
WLAN_AP_SystemCommand_Type
Comment
AssociateWLA
Null_Type
To prepare SS to expect WLAN association by the UE:
NAP
SS shall indicate when the UE has already associated or if not
already associated, indicate when the UE associates
DisassociateW
Null_Type
To prepare SS to expect WLAN disassociation by the UE:
LANAP
SS shall indicate when the UE has already disassociated or if not
already disassociated, indicate when the UE disassociates
WLAN_AP_SYSTEM_CMD
TTCN-3 Record Type
Name
WLAN_AP_SYSTEM_CMD
Comment
Common
WLAN_ReqAspCommonPa
rt_Type
Command
WLAN_AP_SystemComma
nd_Type
Routing info will be none generally;
TimingInfo is generally now but activation time may be used also
for all System commands
Cnf and Follow on flags are both false
WLAN AP System commands
WLAN_ePDG_SYSTEM_CMD
TTCN-3 Record Type
Name
WLAN_ePDG_SYSTEM_CMD
Comment
Common
WLAN_ReqAspCommonPa
rt_Type
Command
WLAN_ePDG_SystemCom
mand_Type
CellId : wlan_Cell_NonSpecific
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=false; FollowOnFlag:=false
WLAN ePDG System commands
WLAN_AP_SystemIndication_Type
TTCN-3 Union Type
Name
WLAN_AP_SystemIndication_Type
Comment
Error
Null_Type
Used by SS to indicate any error;
the Actual Error types reported in ASP common part in
WLAN_IndicationStatus_Type
AssociateWLA
Null_Type
UE has associated to WLAN as per IEEE 802.11-2012 clause
NAP_Ind
4.5.3.3
DisassociateW
Null_Type
UE has disassociated from WLAN as per IEEE 802.11-2012
LANAP_Ind
clause 4.5.3.5
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
427
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_ePDG_SystemIndication_Type
TTCN-3 Union Type
Name
WLAN_ePDG_SystemIndication_Type
Comment
Error
Null_Type
Used by SS to indicate any error;
the Actual Error types reported in ASP common part in
WLAN_IndicationStatus_Type
IPsecTunnelEst IPsecTunnelEstabInd_Type
To indicate progress for IPsec tunnel establishment
abInd
IPsecTunnelDis IPsecTunnelDiscInd_Type
To indicate progress for release of the IPsec tunnel
cInd
IPsecTunnelDiscInd_Type
TTCN-3 Union Type
Name
IPsecTunnelDiscInd_Type
Comment
IPSecTunnelRe Null_Type
lCmpl
Indication raised by the SS when the UE has sent
INFORMATIONAL response according to 24.234 clause 8.3.1.2
(ePDG initiated tunnel disconnection as specified for step 11 of
Table 6.4.3.11-1 in 36.508) or
SS has sent INFORMATIONAL response according to 24.234
clause 8.3.2.2 (WLAN UE initiated tunnel disconnection)
EAP_AKA_Cmpl_Status_Type
TTCN-3 Enumerated Type
Name
EAP_AKA_Cmpl_Status_Type
Comment
success
failure
EAP_AKA_Cmpl_Type
TTCN-3 Record Type
Name
EAP_AKA_Cmpl_Type
Comment
EAP_AKA_Stat EAP_AKA_Cmpl_Status_T
us
ype
XRES_Length
integer
opt
provide XRES_Length for success status
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
428
ETSI TS 136 523-3 V13.2.0 (2017-03)
IPsecTunnelEstabInd_Type
TTCN-3 Union Type
Name
IPsecTunnelEstabInd_Type
Comment
IKE_SA_INIT_I Null_Type
nd
EAP_AKA_Cm
pl
EAP_AKA_Cmpl_Type
IPSecTunnelEs
tabCmpl
Null_Type
indication by the SS that the UE has started the attempt to
establish an IPsec tunnel to the ePDG by sending an initial IKEv2
IKE_SA_INIT (step 1 of Figure 8.2.2-1 in 33.402)
NOTE: the major purpose of this primitive is to get an early
indication when the UE shall not attempt to establish the IPsec
tunnel
indication by the SS that the UE has provided all necessary
parameters for EAP-AKA and the SS has sent an EAP
Success/Failure message to UE according to step 11 of Figure
8.2.2-1 in 33.402
indication by the SS that IPsec tunnel is established: SS shall
indicate this immediately after it has sent out the final IKE_AUTH
response (containing the CFG_REPLY) at step 15 of Figure
8.2.2-1 in 33.402
NOTE: Typically the UE gets all relevant IP addresses of the
3GPP network in the configuration payload (CFG_REPLY)
WLAN_AP_SYSTEM_IND
TTCN-3 Record Type
Name
WLAN_AP_SYSTEM_IND
Comment
Common
WLAN_IndAspCommonPart
_Type
Indication
WLAN_AP_SystemIndicatio
n_Type
The SS shall provide TimingInfo depending on the respective
indication:
- Error
TimingInfo: related to the error (if available)
- WLAN offload Procedure completion
The timing info corresponding to logical completion of the
complete procedure
includes completion of all sub protocols
WLAN_ePDG_SYSTEM_IND
TTCN-3 Record Type
Name
WLAN_ePDG_SYSTEM_IND
Comment
Common
WLAN_IndAspCommonPart
_Type
Indication
WLAN_ePDG_SystemIndic
ation_Type
CellId, RoutingInfo and TimingInfo are ignored by TTCN
WLAN_AP_SYSTEM_PORT
TTCN-3 Port Type
Name
WLAN_AP_SYSTEM_PORT
Comment
WLAN PTC: Port for WLAN AP system configuration
out
WLAN_AP_SYSTEM_CTRL_RE
Q
in
WLAN_AP_SYSTEM_CTRL_CNF
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
429
ETSI TS 136 523-3 V13.2.0 (2017-03)
WLAN_AP_SYSCMD_IND_PORT
TTCN-3 Port Type
Name
WLAN_AP_SYSCMD_IND_PORT
Comment
WLAN PTC: Port for WLAN AP system indications/Commands
out
WLAN_AP_SYSTEM_CMD
in
WLAN_AP_SYSTEM_IND
WLAN_ePDG_SYSTEM_PORT
TTCN-3 Port Type
Name
WLAN_ePDG_SYSTEM_PORT
Comment
WLAN PTC: Port for WLAN ePDG/AAA-Server system configuration
out
WLAN_ePDG_SYSTEM_CTRL_
REQ
in
WLAN_ePDG_SYSTEM_CTRL_
CNF
WLAN_ePDG_SYSCMD_IND_PORT
TTCN-3 Port Type
Name
WLAN_ePDG_SYSCMD_IND_PORT
Comment
WLAN PTC: Port for WLAN ePDG/AAA-Server emulation system indications/Commands
out
WLAN_ePDG_SYSTEM_CMD
in
WLAN_ePDG_SYSTEM_IND
D.14
SideLinkUE_ASP_TypeDefs
D.14.1 SideLinkUE_Data
SL_DATA_REQ
TTCN-3 Record Type
Name
SL_DATA_REQ
Comment
Common ASP to send PDUs on PC5 channels SL-DCH or SLRB
Common
SL_ReqAspCommonPart_T
SS_UE_Id : identifier of the SL UE
ype
* RoutingInfo : SL-DCH or SLRB identity
* TimingInfo : For Direct Discovery see description in
DiscPeriodResourceList_Type;
For communication: SFN/Subframe or DFN/DirectSubframe to
use to start sending data PDUs.
* ControlInfo : CnfFlag:=false; FollowOnFlag:=false
U_Plane
SL_U_PlaneTx_Type
SL_DATA_IND
TTCN-3 Record Type
Name
SL_DATA_IND
Comment
Common ASP to receive PDUs from PC5 channels SL-DCH or SLRB
Common
SL_IndAspCommonPart_Ty
SS_UE_Id : identifier of the SL UE
pe
RoutingInfo : SL-DCH or SLRB identity
TimingInfo : SFN/Subframe or DFN/DirectSubframe when
message has been received
U_Plane
SL_U_PlaneRx_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
430
ETSI TS 136 523-3 V13.2.0 (2017-03)
SL_U_PlaneTx_Type
TTCN-3 Record Type
Name
SL_U_PlaneTx_Type
Comment
U_Plane
SL_U_Plane_Type
SL_DataSched SL_DataScheduling_Type
uling
opt
Applied on SL-DCH and PSCCH/PSSCH
SL_U_PlaneRx_Type
TTCN-3 Record Type
Name
SL_U_PlaneRx_Type
Comment
U_Plane
SL_U_Plane_Type
FreqDomainSc
FreqDomainSchedulExplicit
_Type
hedul
opt
Applied on SL-RB and SL-DCH
SL_U_Plane_Type
TTCN-3 Union Type
Name
SL_U_Plane_Type
Comment
Discovery
SL_DCH_Message_Type
PdcpPdu
PDCP_PDUList_Type
PdcpSdu
SL-DCH message
SS configuration: PDCP no header removal - In Rx only one
PDCP PDU is expected
SS configuration: PDCP header removal - In Rx only one PDCP
SDU is expected
PDCP_SDUList_Type
SL_DCH_Message_Type
TTCN-3 Union Type
Name
SL_DCH_Message_Type
Comment
SL-DCH message
pC5_DISCOVE PC5_DISCOVERY
RY
SL_DataScheduling_Type
TTCN-3 Union Type
Name
SL_DataScheduling_Type
Comment
DiscPeriodRes
DiscPeriodResourceList_Type
ource
CommPeriodR
CommPeriodResourceList_Type
esource
Applied for SS-UE transmission on SL-DCH/PSDCH
Applied for SS-UE transmission on PSCCH
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
431
ETSI TS 136 523-3 V13.2.0 (2017-03)
DiscPeriodResourceList_Type
TTCN-3 Record Type
Name
DiscPeriodResourceList_Type
Comment
Parameters for transmission of the PC5_DISCOVERY message during NumberOfTransmissionPeriod
discovery Periods
TimingInfo in Common indicates the SFN/subframe of the first discovery period
NumberOfTran
integer
Number of consecutive discovery period
smissionPeriod
N_PDSCH
integer
Resource number in the range 0..(Nt*Nf-1) (see TS 36.213 cl
14.3.1)
Multiple PC5_DISCOVERY messages can be transmitted within
a discovery period, different SL_DATA_REQ and N_PDSCH
values will be provided
CommPeriodResourceList_Type
TTCN-3 Record of Type
Name
CommPeriodResourceList_Type
Comment
One entry in the list per STCH packets provided in the U_Plane field
One entry per communication period
record of CommPeriodResource_Type
CommPeriodResource_Type
TTCN-3 Record Type
Name
CommPeriodResource_Type
Comment
Parameters for transmission of the STCH packets
TimingInfo in Common indicates the SFN/subframe of the first communication period
N_PSCCH
integer
PSCCH Resource number (see TS 36.213 cl 14.2.1.1)
Multiple STCH packets can be transmitted within a
communication period, different SL_DATA_REQ and N_PSCCH
values will be provided
SL_DATA_PORT
TTCN-3 Port Type
Name
SL_DATA_PORT
Comment
out
SL_DATA_REQ
in
SL_DATA_IND
D.14.2 SideLinkUE_Configuration
D.14.2.1 SL_Routing_Timing
SL_Routing_Timing: Basic Type Definitions
TTCN-3 Basic Types
DirectFrameNumber_Typ
e
DirectSubframeNumber_T
ype
SLRB_Identity_Type
MasterInformationBlock_SL.directFrame
Number_r12
MasterInformationBlock_SL.directSubfra
meNumber_r12
integer
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
432
ETSI TS 136 523-3 V13.2.0 (2017-03)
SS_UE_Id_Type
TTCN-3 Enumerated Type
Name
SS_UE_Id_Type
Comment
Simulated UE-ID
ss_UE_NonSpecific
Represents all Simulated UEs
ss_UE_Id1
ss_UE_Id2
ss_UE_Id3
SL_RoutingInfo_Type
TTCN-3 Union Type
Name
SL_RoutingInfo_Type
Comment
None
Null_Type
ChannelRadioB SL_ChannelRadioBearerId_Type
earerId
SL_ChannelRadioBearerId_Type
TTCN-3 Union Type
Name
SL_ChannelRadioBearerId_Type
Comment
SLDCH
Null_Type
Discovery SL-DCH
SLRB
SLRB_Identity_Type
Communication SL-RB
SL_TimingInfo_Type
TTCN-3 Union Type
Name
SL_TimingInfo_Type
Comment
InCoverageTim TimingInfo_Type
ing
OutOfCoverage SL_OoC_TimingInfo_Type
Timing
SFN/subframe
DFN/DirectSubframe
SL_OoC_TimingInfo_Type
TTCN-3 Union Type
Name
SL_OoC_TimingInfo_Type
Comment
Out of coverage timing info
DirectSubFram DirectSubFrameTiming_Type
e
Now
Null_Type
None
Null_Type
to be used in REQ ASPs when there is no 'activation time'
to be used in CNF ASPs but not for EnquireTiming
DirectSubFrameTiming_Type
TTCN-3 Record Type
Name
DirectSubFrameTiming_Type
Comment
DFN
DirectFrameNumber_Type
DSubframe
DirectSubframeNumber_Ty
pe
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
433
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.14.2.2 SL_SystemRequestAsp
D.14.2.2.1
SL_RequestAspCommon_Part
SL_RequestAspCommon_Part: Basic Type Definitions
TTCN-3 Basic Types
SL_Bandwidth_Type
MasterInformationBlock_SL.sl_Bandwidt
h_r12
SL_ReqAspCommonPart_Type
TTCN-3 Record Type
Name
SL_ReqAspCommonPart_Type
Comment
SS_UE_Id
SS_UE_Id_Type
RoutingInfo
SL_RoutingInfo_Type
TimingInfo
SL_TimingInfo_Type
ControlInfo
ReqAspControlInfo_Type
SS-UE ID
Channel or RB Id
In coverage or Out of coverage timing
SL_SystemRequest_Type
TTCN-3 Union Type
Name
SL_SystemRequest_Type
Comment
SS_UE_Config SS_UE_ConfigRequest_Type
EnquireTiming
Null_Type
L1MacIndCtrl
SL_Security
SL_L1Mac_IndicationControl_Typ
e
SL_Security_Type
Configure/release a SS-UE
Get SFN/subframe number or DFN/Direct subframe time for this
SS-UE
To configure SS_UE to generate indications for L1/MAC events
StartRestart/Release of SLRB security
SL_L1Mac_IndicationControl_Type
TTCN-3 Record Type
Name
SL_L1Mac_IndicationControl_Type
Comment
NOTE:
Initially all indications are disabled in SS (i.e. it shall not be necessary in 'normal' test cases to use this
primitive but only if a specific indication is needed); omit means indication mode is not changed
DiscSync
IndicationAndControlMode_ opt To enable/disable reporting of start and stop of reception of
Type
Discovery SLSS as configured.
NOTE:
this is applicable when SS_UE is configured with RxDiscSyncRef
SS reports an indication every time when SLSS reception from
UE has toggled in the subframes configured for SLSS reception
CommSLSS_M IndicationAndControlMode_ opt To enable/disable reporting of start and stop of reception of
Type
IBSL
communication SLSS and MIB-SL as configured.
NOTE:
this is applicable when SS_UE is configured with
CommRxSyncRef
SS reports an indication every time when SLSS/MIB-SL
reception from UE has toggled in the subframes configured for
SLSS/MIB-SL reception
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
434
ETSI TS 136 523-3 V13.2.0 (2017-03)
SS_UE_ConfigRequest_Type
TTCN-3 Union Type
Name
SS_UE_ConfigRequest_Type
Comment
AddOrReconfig SS_UE_ConfigInfo_Type
ure
Release
Null_Type
For one SS-UE configuration:
SS_UE_Id : identifier of the SS-UE to be configured
RoutingInfo : None
TimingInfo : Now (for initial configuration)
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
To remove all SS-UEs completely
SS_UE_Id : ss_UE_NonSpecific
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
SS_UE_ConfigInfo_Type
TTCN-3 Record Type
Name
SS_UE_ConfigInfo_Type
Comment
SS_UE_ProSe
SS_UE_ProSeCoverage_T
ype
Coverage
Power
SS_UE_Power_Type
DiscConfig
CommConfig
DiscConfig_Type
CommConfig_Type
opt
opt
Mandatory in the first configuration - omit means no change
InCoverage for discovery
Reference power for the RS of each antenna in Tx
Initially configured as switched ON
opt
opt
SS_UE_Power_Type
TTCN-3 Record Type
Name
SS_UE_Power_Type
Comment
MaxReference
AbsoluteCellPower_Type
Power
Attenuation
opt
Attenuation_Type
Maximum value of SS-UE reference power (in dBm/15kHz as per
TS 36.508, clause 4.3.4.1);
SS-UE is initialised with this reference power;
its value can't be reconfigured during test execution, attenuation
is used to change SS-UE power level
its value is the upper bound of the SS-UE power during the test
case
Initial attenuation: ON
InCoverageConfig_Type
TTCN-3 Record Type
Name
InCoverageConfig_Type
Comment
UL_CarrierFreq ARFCN_ValueEUTRA_r9
UL_bandwidth
Ul_Bandwidth_Type
TDD_Config
TDD_Config
CellTimingInfo
CellTimingInfo_Type
opt
omitted for FDD
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
435
ETSI TS 136 523-3 V13.2.0 (2017-03)
OutOfCoverageConfig_Type
TTCN-3 Record Type
Name
OutOfCoverageConfig_Type
Comment
CarrierFreq_r1
ARFCN_ValueEUTRA_r9
2
SL_bandwidth_ SL_Bandwidth_Type
r12
TDD_ConfigSL TDD_ConfigSL_r12
_r12
SS_UE_Timing SS_UE_TimingInfo_Type
Info
SS_UE_TimingInfo_Type
TTCN-3 Record Type
Name
SS_UE_TimingInfo_Type
Comment
SS_UE Timing
DSubframeOffs integer (0..307199)
et
DfnOffset
integer (0..1023)
frame duration Tf = 307200 * Ts = 10ms; System Time Unit Ts =
1/(15000 * 2048)
(assuming 10 bit DFN)
SS_UE_ProSeCoverage_Type
TTCN-3 Union Type
Name
SS_UE_ProSeCoverage_Type
Comment
For Discovery only InCoverage is applied
InCoverage
InCoverageConfig_Type
In coverage SS-UE shall use Band/Bandwidth/UL frequency/Cell
timing/TDD Frame structure/CP of the associated EUTRA cell
OutOfCoverage OutOfCoverageConfig_Type
PrimarySideLinkSyncSignal_Type
TTCN-3 Record Type
Name
PrimarySideLinkSyncSignal_Type
Comment
RelativeTxPow
SideLinkChannelPower_Ty
opt Power for PSSS relative to the SS-UE power level - value in dB
er
pe
SecondarySideLinkSyncSignal_Type
TTCN-3 Record Type
Name
SecondarySideLinkSyncSignal_Type
Comment
RelativeTxPow
SideLinkChannelPower_Ty
opt Power for SSSS relative to the SS-UE power level - value in dB
er
pe
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.14.2.2.2
ETSI TS 136 523-3 V13.2.0 (2017-03)
436
Discovery_Specific
Discovery_Specific: Basic Type Definitions
TTCN-3 Basic Types
DiscPeriod_r12_Type
DiscNumRetx_r12_Type
DiscNumRepetition_r12_T
ype
SideLinkChannelPower_T
ype
SL_DiscResourcePool_r12.discPeriod_r
12
SL_DiscResourcePool_r12.numRetx_r1
2
SL_DiscResourcePool_r12.numRepetiti
on_r12
integer
see TS 36.213, clause 14
DiscConfig_Type
TTCN-3 Record Type
Name
DiscConfig_Type
Comment
Acc. to 36.321: HARQ configured with fixed TBS=232 - MAC configured in TM
PC5_DISCOVERY msg = 232 bits, transmitted in one MAC TM PDU.
The PSDCH is transmitted on two contiguous physical resource blocks per slot.
The SideLink process is configured with a maximum number of HARQ retransmissions by RRC:
numRetx.
SL_DCH_Tx
SL_DCH_TxConfig_Type
opt Corresponding to UE Rx resource pool
SL_DCH_Rx
SL_DCH_RxConfig_Type
opt Corresponding to UE Tx resource allocation
SL_DCH_TxConfig_Type
TTCN-3 Union Type
Name
SL_DCH_TxConfig_Type
Comment
AddOrReconfig SL_DCH_TxConfigInfo_Type
ure
Release
Null_Type
SL_DCH_TxConfigInfo_Type
TTCN-3 Record Type
Name
SL_DCH_TxConfigInfo_Type
Comment
SS_UE_Tx
DiscResourcePool_Type
opt
DiscTxSyncRef DiscTxSyncRefConfig_Typ
opt
e
Psdch
PsdchConfig_Type
Configure SS_UE to transmit Sync SLSS with PC5_DISCOVERY
Tx
No prose yet - See 36.331 clause 5.10.5 Note 4
opt
SL_DCH_RxConfig_Type
TTCN-3 Union Type
Name
SL_DCH_RxConfig_Type
Comment
AddOrReconfig SL_DCH_RxConfigInfo_Type
ure
Release
Null_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
437
ETSI TS 136 523-3 V13.2.0 (2017-03)
SL_DCH_RxConfigInfo_Type
TTCN-3 Record Type
Name
SL_DCH_RxConfigInfo_Type
Comment
SS_UE_Rx
DiscResourcePoolList_Typ
opt
e
DiscRxSyncRef DiscRxSyncRefConfig_Typ
opt
e
For SS_UE to detect SLSS transmitted by UE under test
It is assumed that only a single Rx resource pool will be specified
for the receipt of SLSS by SS-UE
DiscResourcePool_Type
TTCN-3 Record Type
Name
DiscResourcePool_Type
Comment
All fields are mandatory for initial configuration; omit means "keep as it is"
cp_Len_r12
SL_CP_Len_r12
opt
discPeriod_r12
DiscPeriod_r12_Type
opt
numRetx_r12
DiscNumRetx_r12_Type
opt
numRepetition_ DiscNumRepetition_r12_Ty opt
pe
r12
tf_ResourceCo
SL_TF_ResourceConfig_r1
opt
nfig_r12
2
discTF_IndexLi SL_TF_IndexPairList_r12b
opt Applied in SL-DCH Rx when UE is configured in transmission
st_r12b
mode 2B
To ensure SS-UE and UE are timing aligned, the indexes are
provided to SS-UE using the same activation as the one used to
send the signalling reconfiguration message to UE
DiscResourcePoolList_Type
TTCN-3 Record of Type
Name
DiscResourcePoolList_Type
Comment
record length(1..maxSL_TxPool_r12) of DiscResourcePool_Type
DiscTxSyncRefConfig_Type
TTCN-3 Union Type
Name
DiscTxSyncRefConfig_Type
Comment
To start/reconfigure or stop transmitting SLSS (irrespective of any measurement)
AddOrReconfig DiscTxSyncRefConfigInfo_Type
ure
Release
Null_Type
DiscRxSyncRefConfig_Type
TTCN-3 Union Type
Name
DiscRxSyncRefConfig_Type
Comment
AddOrReconfig DiscSyncConfigParam_Type
ure
Release
Null_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
438
DiscTxSyncRefConfigInfo_Type
TTCN-3 Record Type
Name
DiscTxSyncRefConfigInfo_Type
Comment
All fields are mandatory for initial configuration; omit means "keep as it is"
SyncConfig
DiscSyncConfigParam_Typ opt
e
Psss
PrimarySideLinkSyncSignal opt
_Type
Ssss
SecondarySideLinkSyncSig opt
nal_Type
DiscSyncConfigParam_Type
TTCN-3 Record Type
Name
DiscSyncConfigParam_Type
Comment
All fields are mandatory for initial configuration; omit means "keep as it is"
syncCP_Len_r
SL_CP_Len_r12
opt
12
syncOffsetIndic SL_OffsetIndicatorSync_r1
opt
ator_r12
2
slssid_r12
SLSSID_r12
opt
PsdchConfig_Type
TTCN-3 Record Type
Name
PsdchConfig_Type
Comment
RelativeTxPow
SideLinkChannelPower_Ty
pe
er
D.14.2.2.3
opt
Power for PSDCH relative to the SS-UE power level - value in dB
Communication_Specific
SideLinkUE_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_MaxNumberSL_
STCH
integer
1
Acc to 36.508 cl 4.2.2.3.1.1
Communication_Specific: Basic Type Definitions
TTCN-3 Basic Types
SLSSID_Type
Mcs_Type
SL_Rohc_Profiles_Type
integer (0..335)
SL_CommConfig_r12.commTxResourc
es_r12.setup.scheduled_r12.mcs_r12
SL_PreconfigGeneral_r12.rohc_Profiles
_r12
CommConfig_Type
TTCN-3 Record Type
Name
CommConfig_Type
Comment
CommSyncRef CommSyncConfig_Type
CommRxConfi
CommRxConfig_Type
g
CommTxConfig CommTxConfig_Type
opt
opt
opt
ETSI
Covering values for In and Out of coverage
3GPP TS 36.523-3 version 13.2.0 Release 13
439
ETSI TS 136 523-3 V13.2.0 (2017-03)
CommSyncConfig_Type
TTCN-3 Record Type
Name
CommSyncConfig_Type
Comment
CommTxSyncR CommTxSyncRefConfig_Ty
pe
ef
CommRxSync
CommRxSyncRefConfig_T
ype
Ref
Synchronisatio
SL_SyncRef_Type
nSource
opt
opt
opt
Applied when OoC - When In coverage: omit
ueSyncRef
UE under test is SyncRef UE
SS_UE shall synchronise from received SLSS/MIB-SL
configured in CommRxSyncRef
UE shall be transmitting SL-SS when SS_UE is switched on
sS_UE_SyncRef
SS_UE is SyncRef UE
SS_UE shall initiate DFN/DirectSubrame and transmit
SLSS/MIB-SL acc to CommTxSyncRef
CommTxSyncRefConfig_Type
TTCN-3 Union Type
Name
CommTxSyncRefConfig_Type
Comment
To start/reconfigure or stop transmitting SLSS/MIB-SL (irrespective of any measurement)
AddOrReconfig CommTxSyncRef_Type
Add/re-configure SLSS or SBCCH
ure
Release
Null_Type
Stop SLSS and SBCCH transmission
CommRxSyncRefConfig_Type
TTCN-3 Union Type
Name
CommRxSyncRefConfig_Type
Comment
AddOrReconfig CommRxSyncRef_Type
ure
Release
Null_Type
Add/re-configure reception of SLSS or SBCCH
Release/stop reception of SLSS and SBCCH transmission
CommRxSyncRef_Type
TTCN-3 Record Type
Name
CommRxSyncRef_Type
Comment
SyncCP_Len_r SL_CP_Len_r12
12
Slssid_r12
SLSSID_Type
SyncOffsetIndic SL_OffsetIndicatorSync_r1
ator1_r12
2
SyncOffsetIndic SL_OffsetIndicatorSync_r1
ator2_r12
2
opt
Omit means any value is expected
opt
When present both SyncOffsetIndicator1_r12 and
SyncOffsetIndicator2_r12 shall ne monitored
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
440
ETSI TS 136 523-3 V13.2.0 (2017-03)
CommTxSyncRef_Type
TTCN-3 Record Type
Name
CommTxSyncRef_Type
Comment
SBCCH - RLC TM - MAC TM
SS will perform padding, if required due to the granularity of the TF signalling, as defined in 36.331 cl
8.5.
TxSyncConfig
CommTxSyncRefParam_Ty opt
pe
MIB_SL
MasterInformationBlock_SL opt DFN and Direct subframe set to a dummy value - to be set by
SS-UE
Psss
PrimarySideLinkSyncSignal opt
_Type
Ssss
SecondarySideLinkSyncSig opt
nal_Type
Psbch
PsbchConfig_Type
opt The transmit power of PSBCH is same as the transmit power of
primary sidelink synchronisation signal
CommTxSyncRefParam_Type
TTCN-3 Record Type
Name
CommTxSyncRefParam_Type
Comment
SyncCP_Len_r SL_CP_Len_r12
12
Slssid_r12
SLSSID_Type
opt
SyncOffsetIndic SL_OffsetIndicatorSync_r1
ator1_r12
2
SL_SyncRef_Type
TTCN-3 Enumerated Type
Name
SL_SyncRef_Type
Comment
sS_UE_SyncRef
ueSyncRef
CommRxConfig_Type
TTCN-3 Union Type
Name
CommRxConfig_Type
Comment
SS-UE ID : identifier of the simulated UE being configured
RoutingInfo : none
TimingInfo : 'Now' in common cases
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
AddOrReconfig CommRx_ConfigInfo_Type
Add/re-configure SideLink PSCCH/PSSCH/SLure
SCH/STCH/RLC/PDCP
Release
Null_Type
Release SideLink PSCCH/PSSCH/SL-SCH/STCH/RLC/PDCP
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
441
ETSI TS 136 523-3 V13.2.0 (2017-03)
CommTxConfig_Type
TTCN-3 Union Type
Name
CommTxConfig_Type
Comment
SS-UE ID : identifier of the simulated UE being configured
RoutingInfo : none
TimingInfo : 'Now' in common cases
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
AddOrReconfig CommTx_ConfigInfo_Type
Add/re-configure SideLink PSCCH/PSSCH/SLure
SCH/STCH/RLC/PDCP
Release
Null_Type
Release SideLink PSCCH/PSSCH/SL-SCH/STCH/RLC/PDCP
CommRx_ConfigInfo_Type
TTCN-3 Record Type
Name
CommRx_ConfigInfo_Type
Comment
It is assume that one SSUE layer 2 ID/one SLRB needs to be handled
ResourcePoolL CommResourcePoolList_Ty opt Configure subframes reserved for PSSCH and PSCCH
pe
ist
Present for first configuration
omit means no change
SL_SCH_Confi SL_SCH_Config_Type
opt SL-SCH/MAC configuration
g
Present for first configuration
omit means no change
STCH_ConfigLi STCH_ConfigList_Type
opt
st
CommResourcePoolList_Type
TTCN-3 Record of Type
Name
CommResourcePoolList_Type
Comment
record length(1..maxSL_TxPool_r12) of CommResourcePool_Type
CommResourcePool_Type
TTCN-3 Record Type
Name
CommResourcePool_Type
Comment
sc_CP_Len_r1
SL_CP_Len_r12
2
sc_Period_r12
SL_PeriodComm_r12
sc_TF_Resour
SL_TF_ResourceConfig_r1
ceConfig_r12
2
data_CP_Len_r SL_CP_Len_r12
12
dataHoppingCo SL_HoppingConfigComm_r
nfig_r12
12
data_TF_Reso
SL_TF_ResourceConfig_r1
urceConfig_r12 2
trpt_Subset_r1
SL_TRPT_Subset_r12
2
opt
opt
opt
opt
opt
opt
opt
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
442
ETSI TS 136 523-3 V13.2.0 (2017-03)
CommTx_ConfigInfo_Type
TTCN-3 Record Type
Name
CommTx_ConfigInfo_Type
Comment
All fields are optional: present for first configuration omit means no change
ResourcePoolL CommResourcePoolList_Ty opt Configure pool of resources for PSSCH and PSCCH
pe
ist
Mcs_r12
Mcs_Type
opt Indicates the Modulation and Coding Scheme as defined in TS
36.212 [23, 14.2.1]
SL_SCH_Confi SL_SCH_Config_Type
opt SL-SCH/MAC configuration
g
STCH_ConfigLi STCH_ConfigList_Type
opt RLC PDCP
st
SL_Sheduling
SSUE_SciConfig_Type
opt SCI fixed grant used
PscchConfig
PscchConfig_Type
opt
PsschConfig
PsschConfig_Type
opt
SSUE_SciConfig_Type
TTCN-3 Record Type
Name
SSUE_SciConfig_Type
Comment
Imcs
ImcsValue_Type
SL_Sheduling
SL_SciConfig_Type
Modulation and coding scheme - 5 bits as defined in section
14.1.1 of [3]
SCI fixed grant used
SL_SCH_Config_Type
TTCN-3 Record Type
Name
SL_SCH_Config_Type
Comment
All fields are mandatory for initial configuration; omit means "keep as it is"
Mac
MAC_SLDCH_TestModeCo opt
nfig_Type
SS_UE_Layer2 B24_Type
opt
Id
MAC_SLDCH_TestModeConfig_Type
TTCN-3 Union Type
Name
MAC_SLDCH_TestModeConfig_Type
Comment
None
Null_Type
MAC operation in normal mode for SL-DCH
Config
Null_Type
STCH_ConfigList_Type
TTCN-3 Record of Type
Name
STCH_ConfigList_Type
Comment
record length(1..tsc_MaxNumberSL_STCH) of STCH_Config_Type
STCH_Config_Type
TTCN-3 Record Type
Name
STCH_Config_Type
Comment
All fields are mandatory for initial configuration; omit means "keep as it is"
SLRB
SLRB_Identity_Type
opt
SL_RBIDConfi
SLRB_Config_Type
opt
g
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
443
ETSI TS 136 523-3 V13.2.0 (2017-03)
SLRB_Config_Type
TTCN-3 Union Type
Name
SLRB_Config_Type
Comment
AddOrReconfig SLRB_ConfigInfo_Type
ure
Release
Null_Type
Add/re-configure SideLink RB
Release SideLink RB
SLRB_ConfigInfo_Type
TTCN-3 Record Type
Name
SLRB_ConfigInfo_Type
Comment
All fields are mandatory for initial configuration; omit means "keep as it is"
Rlc
STCH_RLC_Type
opt
Pdcp
SL_PDCP_Configuration_T opt
ype
STCH_RLC_Type
TTCN-3 Record Type
Name
STCH_RLC_Type
Comment
One RLC entity per Tx peer UE
Uni-directional UM RLC
sn-fieldLength = 5
LCG = 3
SN is set to the first received UMD PDU in Rx
UM_Window size = 0
Layer2Id
B24_Type
opt Layer-2 Id of RLC entity: SourceLayer2-Id in Rx DestinationLayer2Id in Tx
LCID
B5_Type
opt Applied in Tx, in Rx SS shall use the value received in the first
STCH data PDU
SL_PDCP_Configuration_Type
TTCN-3 Union Type
Name
SL_PDCP_Configuration_Type
Comment
None
Null_Type
Config
SL_PDCP_ConfigInfo_Type
no PDCP is configured; e.g. for SLRBs tested in MAC test cases
SL_PDCP_ConfigInfo_Type
TTCN-3 Record Type
Name
SL_PDCP_ConfigInfo_Type
Comment
SlRb
PDCP_SLRB_Type
opt
TestMode
PDCP_TestModeConfig_Ty opt
pe
mandatory for initial configuration; omit means "keep as it is"
mandatory for initial configuration; omit means "keep as it is"
PDCP_SLRB_Type
TTCN-3 Record Type
Name
PDCP_SLRB_Type
Comment
PDCP SN length = 16b
discard timer = undefined
maxCID=15
headerCompre
SL_Rohc_Profiles_Type
ssion
opt
mandatory for initial configuration; omit means "keep as it is"
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
444
ETSI TS 136 523-3 V13.2.0 (2017-03)
PsbchConfig_Type
TTCN-3 Record Type
Name
PsbchConfig_Type
Comment
RelativeTxPow
SideLinkChannelPower_Ty
pe
er
opt
Power for PSBCH relative to the SS-UE power level - value in dB
PsschConfig_Type
TTCN-3 Record Type
Name
PsschConfig_Type
Comment
RelativeTxPow
SideLinkChannelPower_Ty
pe
er
opt
Power for PSSCH relative to the SS-UE power level - value in dB
PscchConfig_Type
TTCN-3 Record Type
Name
PscchConfig_Type
Comment
RelativeTxPow
SideLinkChannelPower_Ty
pe
er
D.14.2.2.4
opt
Power for PSCCH relative to the SS-UE power level - value in dB
SL_Security
SL_Security_Type
TTCN-3 Union Type
Name
SL_Security_Type
Comment
When not configured ciphering is considered as off
StartRestart
SL_CipheringStartRestart_Type
Information to start/restart SL security protection in the PDCP
SLRB
Release
Null_Type
To release SL security protection in the PDCP
SL_CipheringStartRestart_Type
TTCN-3 Record Type
Name
SL_CipheringStartRestart_Type
Comment
Acc to 33.303
NOTE: Group Member Id (i.e. the Layer 2 source address of the sending UE) and Group Id (i.e. the
destination Layer 2 identity of the group) are configured in MAC and RLC (SL_SCH_Config_Type
and STCH_RLC_Type).
Expiry time to be handled by TTCN
GroupId
B24_Type
ProSe Layer-2 Group Id
AlgorithmInfo
B3_Type
Security algorithm acc to 33.303 Table E.5.2.2.7-1
PGK
B256_Type
PGK_Id
B64_Type
PGK identity
PTK_Id
B16_Type
For SS_UE Tx - For PTK derivation at SS-UE side.
The value may be different from UE PTK-Id
Counter
B16_Type
For SS_UE Tx - For PTK derivation
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
445
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.14.2.3 SL_SystemConfirmAsp
SL_CnfAspCommonPart_Type
TTCN-3 Record Type
Name
SL_CnfAspCommonPart_Type
Comment
SS_UE_Id
SS_UE_Id_Type
RoutingInfo
SL_RoutingInfo_Type
TimingInfo
SL_TimingInfo_Type
Result
ConfirmationResult_Type
SL_SystemConfirm_Type
TTCN-3 Union Type
Name
SL_SystemConfirm_Type
Comment
Confirmations for SL system configuration;
in general to be sent after the configuration has been done
SS_UE_Config Null_Type
Confirmation for SS-UE configuration
EnquireTiming
Null_Type
Confirmation for EnquireTiming
L1MacIndCtrl
Null_Type
Confirmation for L1MacIndCtrl
SL_Security
Null_Type
(no further parameters from SS)
D.14.2.4 SL_SystemIndicationAsp
SL_IndAspCommonPart_Type
TTCN-3 Record Type
Name
SL_IndAspCommonPart_Type
Comment
SS_UE_Id
SS_UE_Id_Type
RoutingInfo
SL_RoutingInfo_Type
TimingInfo
SL_TimingInfo_Type
Status
IndicationStatus_Type
Simulated SS-UE ID
Channel ID or RB Id for STCH
In coverage or Out of coverage timing
SL_SystemIndication_Type
TTCN-3 Union Type
Name
SL_SystemIndication_Type
Comment
Error
charstring
DiscSync
CommSLSS_M
IBSL
DiscSLSS_Ind_Type
CommSLSS_MIBSL_Ind_Type
Indicates an error situation in SS-UE;
is not explicitly handled in TTCN but causes an INCONC due to
default behaviour;
an additional error code can be signalled in the common part of
the ASP;
SS shall raise an error in case of
- Invalid TimingInfo
- Data scheduled does not fit into an available resource in a
resource pool
(NOTE: additional cases may occur)
Indication for Discovery SLSS sent by UE
Indication for Communication SLSSID and MIB-SL sent by UE
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
446
ETSI TS 136 523-3 V13.2.0 (2017-03)
DiscSLSS_Ind_Type
TTCN-3 Enumerated Type
Name
DiscSLSS_Ind_Type
Comment
When transmitted SLSS is associated with a PC5_DISCOVERY message according to
RxDiscSyncRef.
Start is triggered in SS_UE when
- the first SLSS associated with a PC5_Discovery message is received by SS-UE since enabling
of SLSS reporting
- the previous SLSS indication was 'stop' or 'spurious' and an SLSS associated with a
PC5_Discovery message is received by SS-UE
Stop is triggered in SS_UE when
- the first PC5_DISCOVERY message is received without SLSS
- the previous SLSS indication was 'start' or 'spurious' and PC5_DISCOVERY message is
received without SLSS
Spurious is triggered in SS_UE when
- the first SLSS is received without PC5_DISCOVERY message since enabling of SLSS
reporting
- the previous SLSS indication was 'start' or 'stop' and SLSS is received without associated
PC5_DISCOVERY message
DiscSLSS_Start
DiscSLSS_Stop
DiscSLSS_Spurious
CommSLSS_MIBSL_Ind_Type
TTCN-3 Union Type
Name
CommSLSS_MIBSL_Ind_Type
Comment
Start is triggered in SS_UE when
- the first SLSS associated with a MIB-SL is received in the same subframe by SS-UE since enabling
of reporting
- the previous indication was 'stop' or 'spurious' and an SLSS associated with a MIB-SL is received by
SS-UE
Stop is triggered in SS_UE when
- no SLSS/MIB-SL is transmitted in the period
- the previous indication was 'start' or 'spurious' and no SLSS/MIB-SL is transmitted in the period
CommSLSS_St
art
CommSLSS_St
op
CommSLSS_S
purious
Spurious is triggered in SS_UE when
- the first SLSS is received without MIB-SL or MIB-SL is received without SLSS since enabling of
SLSS reporting
- the previous indication was 'start' or 'stop' and SLSS is received without MIB-SL or MIB-SL is
received without SLSS
CommSyncParamInd_Type
Null_Type
Null_Type
CommSyncParamInd_Type
TTCN-3 Record Type
Name
CommSyncParamInd_Type
Comment
SLSSID
SLSSID_Type
MIB_SL
MasterInformationBlock_SL
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
447
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.14.2.5 SL_System_Interface
SL_SYSTEM_CTRL_REQ
TTCN-3 Record Type
Name
SL_SYSTEM_CTRL_REQ
Comment
ASP to request/control SideLink system configuration
Common
SL_ReqAspCommonPart_T
TimingInfo depends on respective primitive:
ype
Request
SL_SystemRequest_Type
- SS_UE_Config
TimingInfo: depends on the request
- EnquireTiming
TimingInfo: 'now'
- L1MacIndCtrl
TimingInfo: 'now'
- SL_Security
RoutingInfo: SLRB
TimingInfo: 'now'
SL_SYSTEM_CTRL_CNF
TTCN-3 Record Type
Name
SL_SYSTEM_CTRL_CNF
Comment
ASP to confirm a SideLink system configuration request
Common
SL_CnfAspCommonPart_T
TimingInfo is ignored by TTCN (apart from EnquireTiming): SS
ype
may set TimingInfo to "None"
-EnquireTiming
TimingInfo InCoverage: SFN/Subframe
Confirm
SL_SystemConfirm_Type
SL_SYSTEM_IND
TTCN-3 Record Type
Name
SL_SYSTEM_IND
Comment
ASP to report errors or system indications
Common
SL_IndAspCommonPart_Ty
The SS shall provide TimingInfo (SFN + subframe number)
pe
depending on the respective indication:
Indication
SL_SystemIndication_Type
- Error
TimingInfo: related to the error (if available)
- DiscSync
TimingInfo: SFN/Subframe related to the SLSS
- CommSLSS
TimingInfo: SFN/Subframe or DFN/DirectSubframe related to
the SLSS
- CommMIB_SL
TimingInfo: SFN/Subframe or DFN/DirectSubframe related to
the MIB-SL
SL_SYSTEM_PORT
TTCN-3 Port Type
Name
SL_SYSTEM_PORT
Comment
SideLink UE PTC: Port for system configuration
out
SL_SYSTEM_CTRL_REQ
in
SL_SYSTEM_CTRL_CNF
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
448
SL_SYSIND_PORT
TTCN-3 Port Type
Name
SL_SYSIND_PORT
Comment
SideLink UE PTC: Port for system indications
in
SL_SYSTEM_IND
D.15
CommonDefs
CommonDefs: Constant Definitions
TTCN-3 Basic Types
tsc_UInt16Max
tsc_UInt32Max
integer
integer
65535
4294967295
ETSI
ETSI TS 136 523-3 V13.2.0 (2017-03)
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
449
CommonDefs: Basic Type Definitions
TTCN-3 Basic Types
B1_Type
B2_Type
B3_Type
B4_Type
B5_Type
B6_Type
B7_Type
B7_15_Type
bitstring length(1)
bitstring length(2)
bitstring length(3)
bitstring length(4)
bitstring length(5)
bitstring length(6)
bitstring length(7)
bitstring length(7..15)
B8_Type
B10_Type
B11_Type
B12_Type
B15_Type
B16_Type
B18_Type
B24_Type
B32_Type
B64_Type
B128_Type
B256_Type
B128_Key_Type
O3_Type
O4_Type
O6_Type
O8_Type
O13_Type
Null_Type
Dummy_Type
UInt16_Type
UInt32_Type
IP_DrbId_Type
bitstring length(8)
bitstring length(10)
bitstring length(11)
bitstring length(12)
bitstring length(15)
bitstring length(16)
bitstring length(18)
bitstring length(24)
bitstring length(32)
bitstring length(64)
bitstring length(128)
bitstring length(256)
B128_Type
octetstring length(3)
octetstring length(4)
octetstring length(6)
octetstring length(8)
octetstring length(13)
boolean (true)
boolean (true)
integer (0 .. tsc_UInt16Max)
integer (0 .. tsc_UInt32Max)
integer
PdcpCountValue_Type
B32_Type
NOTE: length restriction can only be a range
but not two destinct lengths
128 bit security key
dummy type for 'typeless' fields in unions
dummy type for temporary purposes only
DRB identity type common for all RATs:
- for EUTRA it corresponds to the ASN.1 type
DRB-Identity
- for UTRAN it corresponds to the ASN.1 type
RB-Identity and values are as defined in TS
34.123-3 Table 8.2.4.1
- for GERAN the NSAPI value (type record
NSAPI) may be used
NOTE: this is introduced to simplify the
dependencies (i.e. to keep IP_ASP_TypeDefs
independent from any RAT specific type
definitions)
IndicationAndControlMode_Type
TTCN-3 Enumerated Type
Name
IndicationAndControlMode_Type
Comment
enable
disable
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
450
ETSI TS 136 523-3 V13.2.0 (2017-03)
EUTRA_CellId_Type
TTCN-3 Enumerated Type
Name
EUTRA_CellId_Type
Comment
eutra_Cell_NonSpecif
ic
eutra_Cell1
eutra_Cell2
eutra_Cell3
eutra_Cell4
eutra_Cell6
eutra_Cell10
eutra_Cell11
eutra_Cell12
eutra_Cell13
eutra_Cell14
eutra_Cell23
eutra_Cell28
eutra_Cell29
eutra_Cell30
eutra_Cell31
eutra_CellA
eutra_CellB
eutra_CellC
eutra_CellD
eutra_CellE
eutra_CellG
eutra_CellH
eutra_CellI
eutra_CellJ
eutra_CellK
eutra_CellL
eutra_CellM
EUTRA_CellIdList_Type
TTCN-3 Record of Type
Name
EUTRA_CellIdList_Type
Comment
record length (0..9) of EUTRA_CellId_Type
IP_EUTRA_DrbInfo_Type
TTCN-3 Record Type
Name
IP_EUTRA_DrbInfo_Type
Comment
CellId
EUTRA_CellId_Type
DrbId
IP_DrbId_Type
opt
data is routed to a specific cell regardless of whether the same
DRB is configured in any other cell
mandatory at the system interface
IP_UTRAN_GERAN_DrbInfo_Type
TTCN-3 Record Type
Name
IP_UTRAN_GERAN_DrbInfo_Type
Comment
CellId
integer
DrbId
IP_DrbId_Type
opt mandatory at the system interface
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
451
IP_WLAN_DrbInfo_Type
TTCN-3 Record Type
Name
IP_WLAN_DrbInfo_Type
Comment
CellId
integer
IP_DrbInfo_Type
TTCN-3 Union Type
Name
IP_DrbInfo_Type
Comment
Eutra
IP_EUTRA_DrbInfo_Type
Utran
IP_UTRAN_GERAN_DrbInfo_Typ
e
Geran
IP_UTRAN_GERAN_DrbInfo_Typ
e
Wlan
IP_WLAN_DrbInfo_Type
IPsecTunnel
Null_Type
FBBA
Null_Type
D.16
EUTRA_NB_ASP_TypeDefs
Type definitions for configuration of the system simulator;
Common design principles:
Semantics of OMIT: for all TTCN-3 type definitions used in ASPs omit means "keep as it is" =>
- on initial configuration in general all fields shall be provided
- no default values for fields are foreseen
- if necessary non-existence of information shall be explicitly configured
(e.g. with a union of "no configuration" and "configuration parameters"
- fields within structures imported from the core spec are excepted from this rule
D.16.1 Cell_Configuration
Specific Info for Cell Configuration Primitive
D.16.1.1 Cell_Configuration_Common
EUTRA_NB_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_CellAttenuation
_Off
Attenuation_Type
{Off:=true}
Cell_Configuration_Common: Basic Type Definitions
TTCN-3 Basic Types
InitialAttenuation_Type
ToRS_EPRE_Ratio_Type
Attenuation_Type
(tsc_CellAttenuation_Off)
integer (-35..0)
Attenuation restricted to 'Off'
any-resource-element to RS ratio in dB (e.g.
PDSCH-to-RS ratio; see TS 36.213, clause
5.2)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
452
ETSI TS 136 523-3 V13.2.0 (2017-03)
CellTimingInfo_Type
TTCN-3 Record Type
Name
CellTimingInfo_Type
Comment
Cell Timing
Tcell
integer (0..307199)
SfnOffset
HsfnOffset
frame duration Tf = 307200 * Ts = 10ms; System Time Unit Ts =
1/(15000 * 2048)
integer (0..1023)
integer (0..1023)
Attenuation_Type
TTCN-3 Union Type
Name
Attenuation_Type
Comment
attenuation of the reference power
Value
integer (0..149)
Off
Null_Type
cell power reference power reduced by the given attenuation
(value is in dB)
even though in TS 36.508 -145dBm for LTE and -150dBm for
NB-IoT is given for a non suitable cell we specify an explicit "Off"
value here
InitialCellPower_Type
TTCN-3 Record Type
Name
InitialCellPower_Type
Comment
MaxReference
AbsoluteCellPower_Type
Power
Attenuation
InitialAttenuation_Type
maximum value of cell reference power (RS EPRE in dBm/15kHz
as per TS 36.508, clause 4.3.4.1);
a cell is initialised with this reference power;
its value is the upper bound of the cell power during the test case
initial attenuation
D.16.1.2 Uplink_Physical_Layer_Configuration
SS_TimingAdvanceConfig_Type
TTCN-3 Union Type
Name
SS_TimingAdvanceConfig_Type
Comment
InitialValue
RACH_TimingAdvance_Type
Relative
TimingAdvanceIndex_Type
initial value corresponding to what is sent to the UE in RACH
response
(range acc. 11 bit value; 0 in normal cases)
timing advance command to adjust changes of timing advance
acc. to TS 36.213, clause 4.2.3;
(range acc. 6 bit value: -31..32)
D.16.1.3 Common_MAC_Configuration
Transport channel and MAC related procedures and configuration
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
453
Common_MAC_Configuration: Basic Type Definitions
TTCN-3 Basic Types
TimingAdvanceIndex_Typ
e
integer (0..63)
TimingAdvance_Period_T
ype
integer (400, 600, 1020, 1530, 2040,
4090, 8190)
acc. to TS 36.321, clause 6.1.3.5 "Timing
Advance Command MAC Control Element"
and TS 36.213, clause 4.2.3 "Transmission
timing adjustments"
the values correspond to 80 % of
TimeAlignmentTimer (acc. to TS 36.523-3,
clause 7.2)
(TS 36.331, clause 6.3.2: sf500, sf750,
sf1280, sf1920, sf2560, sf5120, sf10240)
rounded to nearest multiple of 10
UplinkTimeAlignment_AutoSynch_Type
TTCN-3 Record Type
Name
UplinkTimeAlignment_AutoSynch_Type
Comment
TimingAdvance TimingAdvanceIndex_Type
TA_Period
TimingAdvance_Period_Ty
time period after which TA MAC control elements need to be
pe
automatically transmitted
TA_Repetition
TransmissionRepetition_Ty
number of TA MAC control element repetitions to be
pe
automatically transmitted or 'Continuous'
UplinkTimeAlignment_Synch_Type
TTCN-3 Union Type
Name
UplinkTimeAlignment_Synch_Type
Comment
None
Null_Type
no PUCCH Synchronisation applied
Auto
UplinkTimeAlignment_AutoSynch
SS automatically maintains PUCCH synchronization at UE
_Type
If the cell is a
- Rel 10 or earlier cell
- or Rel 11 or later Pcell
- or the Rel-11 or later scell with no STAG-ID configured,
the TAG-ID is set to '00' i.e. P-TAG in Timing advance MCE
If the cell is Rel 11 scell with STAG-ID configured, the configured
stag-ID is used as TAG-ID in Timing advance MCE
TransmissionRepetition_Type
TTCN-3 Union Type
Name
TransmissionRepetition_Type
Comment
Continuous
Null_Type
NumOfCycles
integer (1..infinity)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
454
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.16.1.4 Random_Access_Procedure
EUTRA_NB_ASP_TypeDefs: Constant Definitions
TTCN-3 Basic Types
tsc_RandomAccess
ResponseListSize
integer
10
arbitrary value (needs to be
extended, if necessary);
in case of RACH in idle, UE will
keep on making RACH attempts
until t300 expires
=> number of PRACH preambles
maybe even greater than
maximum value of
PREAMBLE_TRANS_MAX
Random_Access_Procedure: Basic Type Definitions
TTCN-3 Basic Types
RACH_TimingAdvance_T
ype
integer (0..2047)
11 bit timing advance as used in RACH
response (absolute value)
ContentionResolution_ContainedRlcPdu_Type
TTCN-3 Union Type
Name
ContentionResolution_ContainedRlcPdu_Type
Comment
RlcPdu
octetstring
octetstring of an RLC PDU containing e.g. the RRC Connection
Setup;
to be sent in the same MAC PDU as the MAC Contention
Resolution Control Element
None
Null_Type
MAC PDU containing the MAC Contention Resolution Control
Element does not contain an RLC PDU
(i.e. RRC Connection Setup is sent in another PDU)
ContentionResolution_ContainedId_Type
TTCN-3 Union Type
Name
ContentionResolution_ContainedId_Type
Comment
XorMask
ContentionResolutionId_Type
When SS receives Contention Resolution ID from the UE,
SS shall XOR it with the given mask and use this as Contention
Resolution ID;
this allows to get an unmatching Contention Resolution ID;
in normal cases mask shall be set to
tsc_ContentionResolutionId_Unchanged
(i.e. the Contention Resolution ID remains unchanged)
None
Null_Type
MAC Contention Resolution Control Element is not contained in
the MAC PDU sent out as response on Msg3
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
455
ETSI TS 136 523-3 V13.2.0 (2017-03)
TCRNTI_ContentionResolutionMacPdu_Type
TTCN-3 Record Type
Name
TCRNTI_ContentionResolutionMacPdu_Type
Comment
NOTE:
Either ContainedId or ContainedRlcPdu (or both) shall not be 'none';
(if no Contention Resolution Mac Pdu shall be sent,
TCRNTI_ContentionResolutionCtrl_Type.NoContResolID shall be used instead)
ContainedId
ContentionResolution_Cont
Either the Contention Resolution ID as received from the UE
ainedId_Type
or a modified Contention Resolution ID (XorMask !=
tsc_ContentionResolutionId_Unchanged)
or no Contention Resolution ID at all
ContainedRlcP
ContentionResolution_Cont
the MAC PDU containing the MAC Contention Resolution Control
ainedRlcPdu_Type
du
Element may contain the RRC Connection Setup;
in this case the RRC PDU shall be completely encoded been
contained in an RLC PDU
TCRNTI_ContentionResolutionCtrl_Type
TTCN-3 Union Type
Name
TCRNTI_ContentionResolutionCtrl_Type
Comment
when the UE responds on a Random Access Response with a RRC Connection Request on CCCH
and not with a C-RNTI SS shall assume initial Random Access Procedure (TS 36.300, clause
10.1.5.1),
i.e. sends a ContentionResolutionId back to the UE
MacPdu
TCRNTI_ContentionResolutionMa MAC PDU containing the Contention Resolution ID and
cPdu_Type
optionally an RRC PDU (RRC Connection Setup)
MacPdu_CRC_ TCRNTI_ContentionResolutionMa same as MacPdu (see above),
Error
cPdu_Type
but SS shall generate CRC error by toggling CRC bits;
no retransmissions shall be made as UE shall not send a NACK
NoContResolID Null_Type
SS shall not include contention resolution ID (i.e. no MAC PDU
shall be sent);
used for contention resolution fail case
RapIdCtrl_Type
TTCN-3 Union Type
Name
RapIdCtrl_Type
Comment
Automatic
Null_Type
Unmatched
Null_Type
SS shall automatically use same RAPID as received from the UE
SS shall use RAPID being different from preamble sent by the
UE;
SS shall calculate this RAPID acc. to RAPID := (RAPID + 3..63)
mod 64
if single RAR is transmitted in a MAC PDU then only 3 is added
if multiple RAR's are transmitted in MAC PDU, then for first
unmatched RAR 3 is added, second unmatched 4 is added, third
unmatched 5 is added and so on
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
456
ETSI TS 136 523-3 V13.2.0 (2017-03)
TempC_RNTI_Type
TTCN-3 Union Type
Name
TempC_RNTI_Type
Comment
SameAsC_RN
Null_Type
TI
Explicit
C_RNTI
in the RA response SS shall use the same C-RNTI as configured
in ActiveCellConfig_Type;
this is useful for initial random access
in the RA response SS shall use different value as configured in
ActiveCellConfig_Type;
this can be used when the UE already is in RRC_CONNECTED
to have a temporary C-RNTI different from the one used by the
UE;
NOTE: when the UE is not in RRC_CONNECTED there shall be
no explicit temp. C-RNTI since then the UE would assume this
value as C-RNTI
RandomAccessBackoffIndicator_Type
TTCN-3 Union Type
Name
RandomAccessBackoffIndicator_Type
Comment
None
Null_Type
normal case, no back off indicator included
Index
integer (0..15)
Backoff Parameter values acc. TS 36.321, clause 7.2;
values 0..12 are defined, 13..15 may be used in error case
D.16.2 System_Indications
HARQ_Type
TTCN-3 Enumerated Type
Name
HARQ_Type
Comment
ack represents HARQ ACK; nack represents HARQ NACK
ack
nack
D.17
EUTRA_NB_CommonDefs
D.17.1 Common_Types
Common_Types: Basic Type Definitions
TTCN-3 Basic Types
LogicalChannelId_Type
integer (0..10)
HarqProcessId_Type
integer (0..14)
ContentionResolutionId_
Type
AbsoluteCellPower_Type
bitstring length(48)
acc. TS 36.331, clause 6.3.2 and clause
6.7.3.2 for DRBs DTCHLogicalChannelIdentity is INTEGER (3..10);
additionally we have 0..2 for the SRBs
The values 0..7 represent the ID of HARQ
process ID; value range 0..14 is for TDD
used in EUTRA_ASP_DrbDefs and
EUTRA_ASP_Typedefs
absolute cell power (dBm)
integer (-150..0)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
457
ETSI TS 136 523-3 V13.2.0 (2017-03)
D.17.2 RRC_Nested_Types
RRC_Nested_Types: Basic Type Definitions
TTCN-3 Basic Types
IntegrityProtAlgorithm_Ty
pe
SecurityAlgorithmConfig.integrityProtAlg
orithm
D.17.3 ASP_CommonPart
Definition of ASP common parts for REQ-, CNF- and IND-ASPs
D.17.3.1 ASP_CommonPart_Definitions
D.17.3.1.1
Routing_Info
EUTRA_NB_CommonDefs: Constant Definitions
TTCN-3 Basic Types
tsc_SRB0
tsc_SRB1
D.17.3.1.2
integer
integer
0
1
Timing_Info
Timing_Info: Basic Type Definitions
TTCN-3 Basic Types
SystemFrameNumber_Ty
pe
SubFrameNumber_Type
HyperSystemFrameNumb
erInfo_Type
integer (0..1023)
integer (0..9)
SystemFrameNumberInfo_Type
SubFrameInfo_Type
TTCN-3 Union Type
Name
SubFrameInfo_Type
Comment
Number
SubFrameNumber_Type
Any
Null_Type
no specific sub-frame (valid for REQ ASPs only)
SystemFrameNumberInfo_Type
TTCN-3 Union Type
Name
SystemFrameNumberInfo_Type
Comment
Number
SystemFrameNumber_Type
Any
Null_Type
no specific frame number (valid for REQ ASPs only)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
458
ETSI TS 136 523-3 V13.2.0 (2017-03)
SubFrameTiming_Type
TTCN-3 Record Type
Name
SubFrameTiming_Type
Comment
SFN
SystemFrameNumberInfo_
Type
Subframe
SubFrameInfo_Type
HSFN
HyperSystemFrameNumber
Info_Type
TimingInfo_Type
TTCN-3 Union Type
Name
TimingInfo_Type
Comment
SubFrame
SubFrameTiming_Type
Now
Null_Type
None
Null_Type
to be used in REQ ASPs when there is no 'activation time'
only to be used in SYSTEM_CTRL_CNF but not for
EnquireTiming
D.17.3.2 REQ_ASP_CommonPart
ReqAspControlInfo_Type
TTCN-3 Record Type
Name
ReqAspControlInfo_Type
Comment
CnfFlag
boolean
FollowOnFlag
boolean
true => SS shall send CNF:
when the REQ is with no timing information (no activation time),
SS shall send the confirmation when the configuration is done,
i.e. when the test case may continue.
Example:
when there is a configuration follow by a send event it shall not
be necessary to have a wait timer in between but the CNF
triggers the send event.
If there are other triggers e.g. like the UE sending a message,
CnfFlag shall be set to false by the test case to avoid racing
conditions with the CNF and the signalling message.
When there is an activation time SS shall send the CNF after the
configuration has been scheduled;
that means SS shall not wait until the activation time has been
expired.
false => no further (related) information
true: further related information will be sent to SS (semantics
depending on respective ASP)
D.17.3.3 CNF_ASP_CommonPart
ConfirmationResult_Type
TTCN-3 Union Type
Name
ConfirmationResult_Type
Comment
Success
Null_Type
Error
integer
may contain SS specific error code; this will not be evaluated by
TTCN
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
459
D.17.3.4 IND_ASP_CommonPart
IntegrityErrorIndication_Type
TTCN-3 Record Type
Name
IntegrityErrorIndication_Type
Comment
Nas
boolean
Pdcp
boolean
NAS Integrity: set to true when received MAC does not match
calculated MAC
PDCP Integrity: set to true when received MAC does not match
calculated MAC
ErrorIndication_Type
TTCN-3 Record Type
Name
ErrorIndication_Type
Comment
Integrity
IntegrityErrorIndication_Typ
e
System
integer
Integrity error: received MAC does not match calculated MAC
any other error: may be SS specific error code; this will not be
evaluated by TTCN;
e.g. an error shall be raised when the UE requests
retransmission of an RLC PDU
IndicationStatus_Type
TTCN-3 Union Type
Name
IndicationStatus_Type
Comment
Ok
Null_Type
Error
ErrorIndication_Type
D.17.4 L2Data_CommonDefs
Common definitions of L2 control elements used in L2 messages (EUTRA_NB_ASP_L2DataDefs) as well as for SS
configuration (EUTRA_ASP_TypeDefs)
L2Data_CommonDefs: Basic Type Definitions
TTCN-3 Basic Types
MAC_CTRL_ScellActDeac
t_Type
ScellBitMap_Type
36.321 clause 6.1.3.8
ScellBitMap_Type
TTCN-3 Record Type
Name
ScellBitMap_Type
Comment
Value
B7_Type
Reserved
B1_Type
7 MSB bits the C Fields C7 to C1. 1 => the corresponding Scell
is Active 0 => Inactive
LSBit Reserved. Shall be set to 0
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
460
ETSI TS 136 523-3 V13.2.0 (2017-03)
PH_Record_Type
TTCN-3 Record Type
Name
PH_Record_Type
Comment
36.321 clause 6.1.3.6a
P_Bit
B1_Type
V_Bit
B1_Type
Valve
B6_Type
Reserved
PCMaxc
B2_Type
B6_Type
opt
opt
P bit: 1 indicates the UE applies power backoff due to power
management
V bit: Indicates if the PH value is based on a real transmission or
a reference format.
For Type 1 PH, V=0 indicates real transmission on PUSCH and
V=1 indicates that a PUSCH reference format is used
The power headroom level. Ph Type 2 (if configured) for Pcell
and Type 1 for Pcell and Scell
2 reservid bits. Present if V=1
Present if V=1
PH_RecordList_Type
TTCN-3 Record of Type
Name
PH_RecordList_Type
Comment
If simultaneousPUCCH-PUSCH is not configured at least oneType 1 PH record for Pcell is
present.
Additional one record per Scell for which respective 'C' bit is set as 1.
If simultaneousPUCCH-PUSCH is configured then one PH Type 2 record for P cell followed by
PH Type 1 record for P cell is present.
Additional one record per Scell for which respective 'C' bit is set as 1
record length(1..9) of PH_Record_Type
MAC_CTRL_ExtPowerHeadRoom_Type
TTCN-3 Record Type
Name
MAC_CTRL_ExtPowerHeadRoom_Type
Comment
EPH_Octet1
ScellBitMap_Type
PH_RecordList PH_RecordList_Type
At least one record for Pcell is present.
Additional one record per Scell for which respective 'C' bit is set
as 1
DC_PH_RecordList_Type
TTCN-3 Record of Type
Name
DC_PH_RecordList_Type
Comment
If simultaneousPUCCH-PUSCH is not configured at least oneType 1 PH record for Pcell is
present.
Additional one record per PScell/Scell for which respective 'C' bit is set as 1.
If simultaneousPUCCH-PUSCH is configured then one PH Type 2 record for Pcell followed one
PH Type 2 record for PScell followed by PH Type 1 record for Pcell is present.
Additional one record per PSCell/Scell for which respective 'C' bit is set as 1
record length(1..10) of PH_Record_Type
MAC_CTRL_DC_PowerHeadRoom_Type
TTCN-3 Record Type
Name
MAC_CTRL_DC_PowerHeadRoom_Type
Comment
DC_PH_Octet1 ScellBitMap_Type
DC_PH_Recor
DC_PH_RecordList_Type
At least one record for Pcell is present.
dList
Additional one record per PScell/Scell for which respective 'C' bit
is set as 1
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
D.18
461
ETSI TS 136 523-3 V13.2.0 (2017-03)
References to TTCN-3
References to TTCN-3
EUTRA_ASP_TypeD
efs
EUTRA_ASP_DrbDe
fs
EUTRA_NB_ASP_L
2DataDefs
EUTRA_ASP_SrbDe
fs
IP_ASP_TypeDefs
NasEmu_AspTypes
_EUTRA
EUTRA_CommonDe
fs
CDMA2000_ASP_Ty
peDefs
CDMA2000_Commo
nDefs
EUTRA_ASP_CDMA
2000TunnellingDefs
EUTRA_ASP_Virtual
NoiseDefs
UTRAN_ASP_Virtua
lNoiseDefs
WLAN_ASP_TypeD
efs
SideLinkUE_ASP_T
ypeDefs
CommonDefs
EUTRA_NB_ASP_T
ypeDefs
EUTRA_NB_Commo
nDefs
EUTRA_Defs/EUTRA_ASP_TypeDefs.ttcn
Rev 18016
EUTRA_Defs/EUTRA_ASP_DrbDefs.ttcn
Rev 17253
Common_EUTRA_NB/EUTRA_NB_ASP_L2DataDefs.ttcn
Rev 17857
EUTRA_Defs/EUTRA_ASP_SrbDefs.ttcn
Rev 17118
IP_PTC/IP_ASP_TypeDefs.ttcn
NasEmulation/NasEmu_AspTypes_EUTRA.ttcn
Rev 16676
Rev 17118
EUTRA_Defs/EUTRA_CommonDefs.ttcn
Rev 17965
C2K/CDMA2000_ASP_TypeDefs.ttcn
Rev 12722
C2K/CDMA2000_CommonDefs.ttcn
Rev 9022
EUTRA_Defs/EUTRA_ASP_CDMA2000TunnellingDefs.ttcn
Rev 8820
EUTRA_Defs/EUTRA_ASP_VirtualNoiseDefs.ttcn
Rev 17199
UTRAN/UTRAN_ASP_VirtualNoiseDefs.ttcn
Rev 15724
WLAN/WLAN_ASP_TypeDefs.ttcn
Rev 17351
D2D_SideLink/SideLinkUE_ASP_TypeDefs.ttcn
Rev 17253
Common/CommonDefs.ttcn
Common_EUTRA_NB/EUTRA_NB_ASP_TypeDefs.ttcn
Rev 17993
Rev 17662
Common_EUTRA_NB/EUTRA_NB_CommonDefs.ttcn
Rev 17936
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
462
ETSI TS 136 523-3 V13.2.0 (2017-03)
Annex E (informative):
Upper Tester Scenarios
Depending on whether automatic operation is used, or is replaced by the SS by manual intervention, the following
scenarios may occur.
E.1
No confirmation
There is no confirmation required in TTCN e.g. because the UE starts signalling triggered by the UT command.
Figure E.1-1: No confirmation (automatic operation)
NOTE:
The SS discards any response from the UE.
Figure E.1-2: No confirmation (manual intervention)
E.2
Immediate confirmation
TTCN needs an immediate response as a trigger to continue e.g. with DL signalling or starting a timer. In general there
is no signalling in between UT_COMMON_CMD and UT_COMMON_CNF.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
463
ETSI TS 136 523-3 V13.2.0 (2017-03)
Figure E.2-1: Immediate confirmation (automatic operation, normal case)
Figure E.2-2: Immediate confirmation (manual intervention, normal case)
Figure E.2-3: Immediate confirmation (automatic operation, local confirmation)
NOTE:
When local confirmation is required in automatic operation mode the SS discards any late response from
the UE.
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
464
Figure E.2-4: Immediate confirmation (manual intervention, local confirmation)
E.3
Late response
TTCN needs to get the response which is provided by the UE after some signalling related to the UT command. To
achieve a common implementation for automatic operation and manual intervention, the TTCN provides a DUMMY
command to trigger a 2nd interaction between the operator and the UE. Whether or not this DUMMY is used for
automatic operation is up to SS implementation. Nevertheless the DUMMY is sent just before the final DL message
which triggers the UE to generate the response, i.e. the SS may use the DUMMY to trigger reception of the response
(NOTE: in this case it is up to SS implementation to be fast enough). When replacing the AT command with manual
intervention, the SS is responsible to ensure that 2nd interaction does not happen before the final DL message has been
received and processed by the UE.
PTC
MTC
UT_COMMON_CMD
(NO_CNF_REQUIRED)
SA
UT_SYSTEM_REQ
(NO_CNF_REQUIRED)
UE
AT or
proprietary cmd
Signalling
UT_COMMON_CMD
(DUMMY, CNF_REQUIRED)
UT_SYSTEM_REQ
(DUMMY, CNF_REQUIRED)
Signalling: DL message triggering the (AT) response
Response
UT_COMMON_CNF
UT_COMMON_CNF
system interface
Figure E.3-1: Late response (automatic operation)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
PTC
MTC
UT_COMMON_CMD
SA
UT_SYSTEM_REQ
(NO_CNF_REQUIRED)
ETSI TS 136 523-3 V13.2.0 (2017-03)
465
Operator
UE
OPERATOR_CMD
(NO_CNF_REQUIRED)
1st interaction
OPERATOR_RSP
Signalling
UT_COMMON_CMD
(DUMMY, CNF_REQUIRED)
UT_SYSTEM_REQ
(DUMMY, CNF_REQUIRED)
Signalling: DL message triggering the (AT) response
OPERATOR_CMD
2 nd interaction
OPERATOR_RSP
UT_COMMON_CNF
UT_COMMON_CNF
system interface
Figure E.3-2: Late response (manual intervention)
E.4
Multiple responses
In principle the message flow for multiple responses is the same as for a single late response but for more than one
response ( The same requirements as for late response are applicable).
⇒
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
PTC
MTC
UT_COMMON_CMD
(CNF_REQUIRED)
UT_COMMON_CNF
ETSI TS 136 523-3 V13.2.0 (2017-03)
466
SA
UT_SYSTEM_REQ
(CNF_REQUIRED)
UT_COMMON_CNF
UE
AT_CMD or
proprietary cmd
Response 1
Signalling
UT_COMMON_CMD
(DUMMY, CNF_REQUIRED)
UT_SYSTEM_REQ
(DUMMY, CNF_REQUIRED)
Signalling: DL message triggering the (AT) response
Response 1
UT_COMMON_CNF
UT_COMMON_CNF
Signalling
UT_COMMON_CMD
(DUMMY, CNF_REQUIRED)
UT_SYSTEM_REQ
(DUMMY, CNF_REQUIRED)
Signalling: DL message triggering the (AT) response
Response N
UT_COMMON_CNF
UT_COMMON_CNF
system interface
Figure E.4-1: Multiple responses (automatic operation)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
PTC
MTC
UT_COMMON_CMD
(CNF_REQUIRED)
SA
UT_SYSTEM_REQ
UT_COMMON_CMD
(DUMMY, CNF_REQUIRED)
Operator
OPERATOR_CMD
(CNF_REQUIRED)
UT_COMMON_CNF
ETSI TS 136 523-3 V13.2.0 (2017-03)
467
UE
1st interaction
OPERATOR_RSP
UT_COMMON_CNF
Signalling
UT_SYSTEM_REQ
(DUMMY, CNF_REQUIRED)
Signalling: DL message triggering the (AT) response
OPERATOR_CMD
UT_COMMON_CNF
2nd interaction:
Response 1
OPERATOR_RSP
UT_COMMON_CNF
Signalling
UT_COMMON_CMD
(DUMMY, CNF_REQUIRED)
UT_SYSTEM_REQ
(DUMMY, CNF_REQUIRED)
Signalling: DL message triggering the (AT) response
OPERATOR_CMD
UT_COMMON_CNF
UT_COMMON_CNF
OPERATOR_RSP
(N+1)th interaction:
Response N
system interface
Figure E.4-2: Multiple responses (manual intervention)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
468
ETSI TS 136 523-3 V13.2.0 (2017-03)
Annex F (informative)
TTCN-3 Definitions
F.1
NBIOT_ASP_TypeDefs
Type definitions for configuration of the system simulator;
Common design principles:
Semantics of OMIT: for all TTCN-3 type definitions used in ASPs omit means "keep as it is" =>
- on initial configuration in general all fields shall be provided
- no default values for fields are foreseen
- if necessary non-existence of information shall be explicitly configured
(e.g. with a union of "no configuration" and "configuration parameters"
- fields within structures imported from the core spec are excepted from this rule
F.1.1
ASN1_Container
Definitions containing ASN.1 types for backward compatibility;
NOTE 1: PCCH_Message and BCCH_DL_SCH_Message already have a critical extension mechanism by RRC type
definition
NOTE 2: BCCH_BCH_Message contains the MIB and therefore is considered to be not extendable
NOTE 3: "simple types" are not considered: C_RNTI, PhysCellId, CellIdentity, ARFCN_ValueEUTRA
NPUSCH_ConfigDedicated_Type
TTCN-3 Record Type
Name
NPUSCH_ConfigDedicated_Type
Comment
R13
NPUSCH_ConfigDedicated
_NB_r13
NPRACH_Config_Type
TTCN-3 Record Type
Name
NPRACH_Config_Type
Comment
R13
NPRACH_ConfigSIB_NB_r
13
NB_RACH_ConfigCommon_Type
TTCN-3 Record Type
Name
NB_RACH_ConfigCommon_Type
Comment
R13
RACH_ConfigCommon_NB
_r13
NB_PDCP_Config_Type
TTCN-3 Union Type
Name
NB_PDCP_Config_Type
Comment
R13
PDCP_Config_NB_r13
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
469
NB_UL_AM_RLC_Type
TTCN-3 Record Type
Name
NB_UL_AM_RLC_Type
Comment
R13
UL_AM_RLC_NB_r13
NB_DL_AM_RLC_Type
TTCN-3 Record Type
Name
NB_DL_AM_RLC_Type
Comment
R13
DL_AM_RLC_NB_r13
NPUSCH_ConfigCommon_Type
TTCN-3 Record Type
Name
NPUSCH_ConfigCommon_Type
Comment
R13
NPUSCH_ConfigCommon_
NB_r13
NB_DRX_Config_Type
TTCN-3 Record Type
Name
NB_DRX_Config_Type
Comment
R13
DRX_Config_NB_r13
CarrierConfigDedicated_Type
TTCN-3 Record Type
Name
CarrierConfigDedicated_Type
Comment
R13
CarrierConfigDedicated_NB
_r13
DL_GapConfig_Type
TTCN-3 Record Type
Name
DL_GapConfig_Type
Comment
R13
DL_GapConfig_NB_r13
DL_Bitmap_Type
TTCN-3 Record Type
Name
DL_Bitmap_Type
Comment
R13
DL_Bitmap_NB_r13
F.1.2
System_Configuration
Formal ASP Definitions for system configuration
ETSI
ETSI TS 136 523-3 V13.2.0 (2017-03)
3GPP TS 36.523-3 version 13.2.0 Release 13
470
ETSI TS 136 523-3 V13.2.0 (2017-03)
System_Configuration: Basic Type Definitions
TTCN-3 Basic Types
NB_DPR_DataVolumnInd
ex_Type
NB_DPR_PowerHeadroo
mLevel_Type
integer (0..15)
integer (0..3)
NB_SystemRequest_Type
TTCN-3 Union Type
Name
NB_SystemRequest_Type
Comment
Cell
NB_CellConfigRequest_Type
CellAttenuation NB_CellAttenuationList_Type
List
RadioBearerLis
t
EnquireTiming
AS_Security
Paging
NB_RadioBearerList_Type
L1MacIndCtrl
NB_L1Mac_IndicationControl_Ty
pe
NB_PDCP_CountReq_Type
NB_RLC_CountsReq_Type
NB_RA_NPDCCH_Order_Type
PdcpCount
RlcCounts
NpdcchOrder
Null_Type
NB_AS_Security_Type
NB_PagingTrigger_Type
configure/release a cell
power attenuation for one or several cells;
all cells included in the list shall be changed at the same time;
all cells in the list shall reach the new cell power within a
maximum of 100ms (10 frames)
acc. to the tolerances given in TS 36.508
NOTE: In the common ASP part the CellId shall be set
- to the cell the timing information refers to if activation time shall
be applied
- to nbiot_Cell_NonSpecific when there is no activation time
configure/release one or several SRBs and/or DRBs
get HSFN, SFN and sub-frame number for this cell
StartRestart/Release of AS security
to trigger SS to send paging at the given paging occasion (as
calculated in TTCN) or a Direct Indication
to configure SS to generate indications for L1/MAC events
to set or enquire PDCP COUNT for one or more RBs
to set or enquire RLC Counts VTS and VRR
to configure SS to transmit a NPDCCH order with configured CRNTI to the UE to trigger RA procedure;
result in DCI Format N1 transmission as in TS 36.212, clause
6.4.3.2;
the SS shall schedule the NPDCCH order in the same way as
DCI for DL transmissions
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
471
ETSI TS 136 523-3 V13.2.0 (2017-03)
NB_SystemConfirm_Type
TTCN-3 Union Type
Name
NB_SystemConfirm_Type
Comment
confirmations for system configuration;
in general to be sent after the configuration has been done
Cell
Null_Type
(no further parameters from SS)
CellAttenuation Null_Type
(no further parameters from SS)
List
NOTE 1:
the confirmation shall be sent when all cells have changed power
levels
NOTE 2:
for the CellId in the common ASP part the same rules are applied
as for the SYSTEM REQ
RadioBearerLis Null_Type
(no further parameters from SS)
t
EnquireTiming
Null_Type
SFN and sub-frame number are included in the TimingInfo
AS_Security
Null_Type
(no further parameters from SS)
Paging
Null_Type
normally not needed but defined for completeness
L1MacIndCtrl
Null_Type
(no further parameters from SS)
PdcpCount
NB_PDCP_CountCnf_Type
as response to 'Get' a list is returned containing COUNT
information for the requested RBs
RlcCounts
NB_RLC_CountsCnf_Type
as response to 'Get' a list is returned containing RLC Counts
VTS and VRR
NpdcchOrder
Null_Type
confirmation for NPDCCH Order
NB_HarqError_Type
TTCN-3 Union Type
Name
NB_HarqError_Type
Comment
UL
Null_Type
DL
there is just one HARQ process for NB-IoT and uplink HARQ
operation is asynchronous (see TS 36.321 clause 5.4.2)
Null_Type
NB_RachPreamble_Type
TTCN-3 Record Type
Name
NB_RachPreamble_Type
Comment
RAPID
integer
RepetitionsPer
PreambleAttem
pt
integer
indicates the RAPID of the preamble used (integer (0..63));
according to 36.321 clause 6.2.2 "For NB-IoT, the Random
Access Preamble IDentifier field corresponds to the start
subcarrier index"
number of preambles the SS has detected for the preamble
attempt
NB_DPR_Type
TTCN-3 Record Type
Name
NB_DPR_Type
Comment
DataVolumnInd NB_DPR_DataVolumnInde
ex
x_Type
PowerHeadroo
NB_DPR_PowerHeadroom
Level_Type
mLevel
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
472
NB_SystemIndication_Type
TTCN-3 Union Type
Name
NB_SystemIndication_Type
Comment
Error
charstring
RachPreamble
NB_RachPreamble_Type
DPR
NB_DPR_Type
HarqError
NB_HarqError_Type
UL_HARQ
HARQ_Type
F.1.3
indicates an error situation in SS;
is not explicitly handled in TTCN but causes an INCONC due to
default behaviour;
an additional error code can be signalled in the common part of
the ASP;
RACH preamble being sent by the UE
NOTE 1: for NB-IoT there can be more than one repetition per
preamble attempt (numRepetitionsPerPreambleAttempt-r13 in
NPRACH-ConfigSIB-NB-DEFAULT in
SystemInformationBlockType2-NB); nevertheless the SS shall
raise only one indication per preamble attempt and indicate the
number of attempts in the ' RepetitionsPerPreambleAttempt' field
of the indication
NOTE 2: The SS shall provide start of the attampt's first
preamble as timing information of the primitive (in a lab
environment in general this is the start time of the NPRACH
preamble transmission according to clause 10.1.6.1 of TS 36.211
- depending on nprach-Periodicity and nprach-StartTime)
indicates MAC DPR control element (TS 36.321 clause 6.1.3.10)
being contained in MAC PDU
indicates detection of HARQ error:
1. HARQ CRC error for UL data
2. HARQ NACK from the UE unless SS is configured to report
HARQ ACK/NACK
to report the UL HARQ ACK/NACK
Cell_Configuration
Specific Info for Cell Configuration Primitive
F.1.3.1 Cell_Configuration_Common
Cell_Configuration_Common: Basic Type Definitions
TTCN-3 Basic Types
NB_ToRS_EPRE_Ratio_T
ype
integer (-35..0)
any-resource-element to NRS ratio in dB (e.g.
NPDSCH-to-NRS ratio; see TS 36.213, clause
16.2.2)
NB_CellConfigRequest_Type
TTCN-3 Union Type
Name
NB_CellConfigRequest_Type
Comment
AddOrReconfig NB_CellConfigInfo_Type
ure
Release
Null_Type
for cell configuration:
CellId : identifier of the cell to be configured
RoutingInfo : None
TimingInfo : Now (for initial configuration and for reconfiguration
in general)
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
to remove a cell completely CellId : identifier of the cell to be released;
nbiot_Cell_NonSpecific, in case all cells shall be released
RoutingInfo : None
TimingInfo : Now
ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
473
ETSI TS 136 523-3 V13.2.0 (2017-03)
NB_CellConfigInfo_Type
TTCN-3 Record Type
Name
NB_CellConfigInfo_Type
Comment
common information for initial cell configuration or reconfiguration;
in case of reconfiguration OMIT means 'keep configuration as it is'
Basic
NB_BasicCellConfig_Type
opt basic information for a cell (e.g. broadcasting)
Active
NB_ActiveCellConfig_Type
opt add. configuration for active cell (i.e. cell being capable to receive
RACH preamble)
NB_BasicCellConfig_Type
TTCN-3 Record Type
Name
NB_BasicCellConfig_Type
Comment
StaticCellInfo
NB_StaticCellInfo_Type
PhysicalLayerC NB_PhysicalLayerConfigDL
_Type
onfigDL
InitialCellPower InitialCellPower_Type
opt
opt
Common information which does not change during a test
default settings regarding DL physical control channels
opt
reference cell power for the NRS of each antenna in DL
NOTE 1:
the power of the RS of an antenna may be reduced by antenna
specific configuration
NOTE 2:
in general the power may be adjusted on a per resource element
basis
=> all physical channel/signal power settings shall be adjusted
relatively to the NRS;
if there are more than one TX antennas each one may have its
own attenuation;
independently from those relative power settings the cell power
can easily be adjusted by just changing the reference power
Usage of bitmap or no bitmap to define valid NB-IoT DL
subframes; omit means "keep as it is"
configuration of BCCH/BCH; SS is triggered to configure
RLC/MAC regardingly;
BCCH data on the NPDSCH
NPBCH: MIB;
NPDSCH: scheduling and resource allocation; SIBs
configuration of PCCH/PCH; SS is triggered to configure
RLC/MAC regardingly;
PCCH data on the NPDSCH is distinguished by the P-RNTI
(needed even to modify SI => shall be configured for
CELL_BROADCASTING)
DownlinkBitma
pConfig
BcchConfig
NB_DownlinkBitmapConfig
_Type
NB_BcchConfig_Type
opt
PcchConfig
NB_PcchConfig_Type
opt
opt
NB_ActiveCellConfig_Type
TTCN-3 Record Type
Name
NB_ActiveCellConfig_Type
Comment
C_RNTI
EUTRA_ASN1_C_RNTI_Ty opt
pe
PhysicalLayerC
onfigUL
RachProcedure
Config
CcchDcchDtch
Config
NonAnchorCarr
ier
NB_PhysicalLayerConfigUL
_Type
NB_RachProcedureConfig_
Type
NB_CcchDcchDtchConfig_
Type
NB_NonAnchorCarrier_Typ
e
opt
opt
opt
opt
(pre-)configured C-RNTI;
affects scrambling of NPDSCH/NPUSCH and CRC of
NPDCCH(s);
shall be used implicitly in RACH procedure (i.e. as CE in RAR)
parameters for NPRACH, NPUSCH
Omitted when no UL frequency is applied to the band
to configure the SS's behaviour for the RACH procedure
Omitted when no UL frequency is applied to the band
Parameters related to CCCH/DCCH/DTCH in UL and DL
configuration for non-Anchor Carrier ("None" if there is no nonAnchor Carrier)
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
474
NB_StaticCellInfo_Type
TTCN-3 Record Type
Name
NB_StaticCellInfo_Type
Comment
Common information which (normally) does not change during a test;
therefore all fields are mandatory
Common
NB_CommonStaticCellInfo_
information common for UL and DL
Type
Earfcn
NB_CarrierFreq_Type
DL or UL EARFCN as defined in TS 36.101
NB_CommonStaticCellInfo_Type
TTCN-3 Record Type
Name
NB_CommonStaticCellInfo_Type
Comment
information common for UL and DL; all fields are mandatory
PhysicalCellId
EUTRA_ASN1_PhysCellId_
N(Ncell, ID): imported from core spec;
Type
-> narrowband reference signals
-> scrambling of all DL physical channels:
NPBCH, NPDCCH, and NPDSCH (together with nRNTI)
NB_Band
integer
CellTimingInfo
CellTimingInfo_Type
OperationMode NB_OperationModeInfo_Ty
pe
Info
eutraControlRe NB_EutraControlRegionSiz
opt Only used for the in-band operation mode, omitted otherwise.
e_Type
gionSize
Indicates the control region size of the E-UTRA cell.
F.1.3.2 Downlink_Physical_Layer_Configuration
Downlink physical layer configuration:
- DL antenna configuration
- control region (NPDCCH)
- primary/secondary sync signals
- power control for physical channels and signals
F.1.3.2.1
Physical_Channels
Physical_Channels: Basic Type Definitions
TTCN-3 Basic Types
NPdcchSearchSpaceCan
didateIndex_Type
integer (0..7)
Index of the search space candidate to be
used for UL grant or DL assignment
(corresponds to "u" in the calculations of
clause 16.6 in TS 36.213)
NPbchConfig_Type
TTCN-3 Record Type
Name
NPbchConfig_Type
Comment
RelativeTxPow
NB_ToRS_EPRE_Ratio_Ty
pe
er
opt
power ratio for NPBCH's resource elements relative to the NRS
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
475
ETSI TS 136 523-3 V13.2.0 (2017-03)
NPdcchFormat_Type
TTCN-3 Enumerated Type
Name
NPdcchFormat_Type
Comment
NPDCCH format according to 36.211 claues 10.2.5.1 => aggregation level according to 36.213
clause 16.6
npdcchFormat0
npdcchFormat1
NPdcchUESpecificSearchSpace_Type
TTCN-3 Record Type
Name
NPdcchUESpecificSearchSpace_Type
Comment
parameters for UE specific search space (UESS, TS 36.213 clause 16.6);
In addition the SS needs to consider the "DCISubFrameRepetitionNumber" in the DCI UL/DL
configuration
to determine the value of R (actual number of NPDCCH repetitions for the DCI)
NPdcchFormat
NPdcchFormat_Type
Aggregation level: According to tables 16.6-1, 16.6-2, 16.6-3 in
TS 36.213 for typical search space configuration as per TS
36.508 NPDCCH format 1 is used i.e. there is just one search
space candidate per NPDCCH transmission. Use cases for
NPDCCH format 0 are FFS
NumRepetition
NPDCCH_NumRepetitions
Rmax for UE specific search space; TS 36.213 clause 16.6
_UESS_Type
s
StartSF
NPDCCH_StartSF_UESS_
G for UE specific search space; TS 36.213 clause 16.6
Type
Offset
NPDCCH_Offset_UESS_Ty
offset for UE specific search space; TS 36.213 clause 16.6
pe
SearchSpaceC NPdcchSearchSpaceCandi
index of the search space candidate to be used for DL
dateIndex_Type
andidateForDL
assignment
SearchSpaceC NPdcchSearchSpaceCandi
index of the search space candidate to be used for UL grant
dateIndex_Type
andidateForUL
NPdcchType1CommonSearchSpace_Type
TTCN-3 Record Type
Name
NPdcchType1CommonSearchSpace_Type
Comment
parameters for Type1 common search space for paging (Type1CSS, TS 36.213 clause 16.6);
In addition the SS needs to consider the "DCISubFrameRepetitionNumber" in the DCI DL
configuration
to determine the value of R (actual number of NPDCCH repetitions for the DCI)
NumRepetition
NPDCCH_NumRepetitions
Rmax for Type1 common search space; TS 36.213 clause 16.6
s
_Type1CSS_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
476
ETSI TS 136 523-3 V13.2.0 (2017-03)
NPdcchType2CommonSearchSpace_Type
TTCN-3 Record Type
Name
NPdcchType2CommonSearchSpace_Type
Comment
parameters for Type2 common search space for RACH procedure (Type2CSS, TS 36.213 clause
16.6);
In addition the SS needs to consider the "DCISubFrameRepetitionNumber" in the DCI DL
configuration
to determine the value of R (actual number of NPDCCH repetitions for the DCI);
NOTE:
NumRepetitions, StartSF and Offset are also included in each entry of the nprach-ParametersList of
NPRACH_Config_Type (NB_PhysicalLayerConfigUL_Type);
nevertheless NPRACH_Config_Type contains a list of NPRACH resources whereas the SS needs to
consider only one search space corresponding to the NPRACH resource the UE shall select
NumRepetition
NPDCCH_NumRepetitions
Rmax for Type2 common search space; TS 36.213 clause 16.6
_Type2CSS_Type
s
StartSF
NPDCCH_StartSF_Type2C
G for Type2 common search space; TS 36.213 clause 16.6
SS_Type
Offset
NPDCCH_Offset_Type2CS
offset for Type2 common search space; TS 36.213 clause 16.6
S_Type
SearchSpaceC NPdcchSearchSpaceCandi
index of the search space candidate to be used for random
andidateForRA dateIndex_Type
access response
R
SearchSpaceC NPdcchSearchSpaceCandi
index of the search space candidate to be used for Msg4
dateIndex_Type
andidateForMs
scheduling;
g4
this can be an DL transmission (contention resolution id based)
or an UL transmission (C-RNTI based)
NPdcchConfig_Type
TTCN-3 Record Type
Name
NPdcchConfig_Type
Comment
UESS
NPdcchUESpecificSearchS
pace_Type
Type1CSS
NPdcchType1CommonSear
chSpace_Type
Type2CSS
NPdcchType2CommonSear
chSpace_Type
RelativeTxPow
NB_ToRS_EPRE_Ratio_Ty
pe
er
opt
parameters for UE specific search space
opt
parameters for Type1 common search space
opt
parameters for Type2 common search space
opt
power ratio for NPDCCH's resource elements relative to the NRS
NPdschRelativeTxPower_Type
TTCN-3 Record Type
Name
NPdschRelativeTxPower_Type
Comment
FFS
RachResponse NB_ToRS_EPRE_Ratio_Ty opt
pe
BcchOnNPdsc
NB_ToRS_EPRE_Ratio_Ty opt
pe
h
PcchOnNPdsc
NB_ToRS_EPRE_Ratio_Ty opt
h
pe
CcchOnNPdsc
NB_ToRS_EPRE_Ratio_Ty opt
pe
h
DcchDtchOnN
NB_ToRS_EPRE_Ratio_Ty opt
pe
Pdsch
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
477
ETSI TS 136 523-3 V13.2.0 (2017-03)
NPdschConfig_Type
TTCN-3 Record Type
Name
NPdschConfig_Type
Comment
RelativeTxPow
NPdschRelativeTxPower_T
ype
er
F.1.3.2.2
opt
Physical_Signals
NB_PrimarySyncSignal_Type
TTCN-3 Record Type
Name
NB_PrimarySyncSignal_Type
Comment
RelativeTxPow
NB_ToRS_EPRE_Ratio_Ty opt
pe
er
power ratio for NPSS's resource elements relative to the NRS
(NOTE: applicable even though NRS is not in the same
subframe)
NB_SecondarySyncSignal_Type
TTCN-3 Record Type
Name
NB_SecondarySyncSignal_Type
Comment
RelativeTxPow
NB_ToRS_EPRE_Ratio_Ty opt
pe
er
power ratio for NPSS's resource elements relative to the NRS
(NOTE: applicable even though NRS is not in the same
subframe)
NB_LTE_CellSpecificReferenceSignal_Type
TTCN-3 Record Type
Name
NB_LTE_CellSpecificReferenceSignal_Type
Comment
RelativeTxPow
NB_ToRS_EPRE_Ratio_Ty opt power ratio for the LTE CRS in case of In-band transmission with
pe
er
same PCI
AntennaConfig_Type
TTCN-3 Enumerated Type
Name
AntennaConfig_Type
Comment
This type specifies how many Tx antennas shall be used by the SS
AN1
single Tx antenna shall be used by the SS
AN2
two Tx antennas shall be used by the SS
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
478
ETSI TS 136 523-3 V13.2.0 (2017-03)
NB_PhysicalLayerConfigDL_Type
TTCN-3 Record Type
Name
NB_PhysicalLayerConfigDL_Type
Comment
all fields are declared as optional to allow single reconfigurations; in this case omit means "keep as it
is"
Antenna
AntennaConfig_Type
opt
NPbch
NPbchConfig_Type
opt
NPdcch
NPdcchConfig_Type
opt
NPdsch
NPdschConfig_Type
opt
NPss
NB_PrimarySyncSignal_Ty
opt
pe
NSss
NB_SecondarySyncSignal_ opt
Type
LteCrs
NB_LTE_CellSpecificRefer
opt if omitted in initial configuration the CRS shall be considered as
enceSignal_Type
being not present, i.e. shall not be transmitted by the SS
NB_DownlinkBitmapConfig_Type
TTCN-3 Union Type
Name
NB_DownlinkBitmapConfig_Type
Comment
to specify valid NB-IoT DL subframes according to TS 36.213 clause 16.4
Bitmap
DL_Bitmap_Type
valid NB-IoT DL subframe specified by bitmap and does not
contain NPSS/NSSS/NPBCH/NB-SIB1 transmission
None
Null_Type
valid NB-IoT DL subframe does not contain
NPSS/NSSS/NPBCH/NB-SIB1 transmission
NB_NonAnchorCarrier_Type
TTCN-3 Union Type
Name
NB_NonAnchorCarrier_Type
Comment
Config
CarrierConfigDedicated_Type
None
Null_Type
F.1.3.3 Uplink_Physical_Layer_Configuration
Uplink physical channel configuration: NPRACH, NPUSCH and UL RS
NB_SubCarrierSpacingUL_Type
TTCN-3 Enumerated Type
Name
NB_SubCarrierSpacingUL_Type
Comment
subCarrierSpacing_1
5kHz
subCarrierSpacing_3
_75kHz
NPUSCH_Configuration_Type
TTCN-3 Record Type
Name
NPUSCH_Configuration_Type
Comment
Common
NPUSCH_ConfigCommon_ opt
Type
Dedicated
NPUSCH_ConfigDedicated
opt
_Type
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
ETSI TS 136 523-3 V13.2.0 (2017-03)
479
NB_PhysicalLayerConfigUL_Type
TTCN-3 Record Type
Name
NB_PhysicalLayerConfigUL_Type
Comment
NOTE:
In general SS is required to keep the UE's UL power constant
NPrach
NPRACH_Config_Type
opt parameters acc. TS 36.331, clause 6.7.3.2
NPusch
NPUSCH_Configuration_Ty opt parameters acc. TS 36.331, clause 6.7.3.2
pe
(including configuration of RS)
TimingAdvance SS_TimingAdvanceConfig_ opt to adjust timing advance;
Type
at cell initialization absolute timing advance is configured as 0;
absolute timing advance may be modified as part of the Random
Access procedure configuration;
in some MAC test cases timing advance may be configured to a
non-zero (11 bit value) at the beginning and modified by (6 bit)
timing advance commands during the test
SubCarrierSpa
NB_SubCarrierSpacingUL_ opt 15kHz or 3.75kHz UL carrier spacing; cyclic prefix as per 36.211
Type
cingUL
Table 10.1.5-1 accordingly
F.1.3.4 Common_MAC_Configuration
Transport channel and MAC related procedures and configuration
Common_MAC_Configuration: Basic Type Definitions
TTCN-3 Basic Types
NPDSCH_ImcsValue_Typ
e
NPUSCH_ImcsValue_Typ
e
integer (0..12)
Modulation and coding scheme index coding;
TS 36.213 Table 16.4.1.5.1-1
Modulation and coding scheme index coding;
TS 36.213 Table 16.5.1.2-2
integer (0..12)
NB_PdcchDciFormat_Type
TTCN-3 Enumerated Type
Name
NB_PdcchDciFormat_Type
Comment
dci_N0
physical layer parameters acc. TS 36.508 Table 8.1.3.6.1.1-1 (for NPUSCH)
dci_N1
physical layer parameters acc. TS 36.508 Table 8.1.3.6.1.1-3 (for NPDSCH)
dci_N2
physical layer parameters acc. TS 36.508 Table 8.1.3.6.1.1-3 (for Paging)
NB_CRC_ErrorMode_Type
TTCN-3 Enumerated Type
Name
NB_CRC_ErrorMode_Type
Comment
noError
SS shall not generate any CRC error
crcErrorWithRetrans
SS shall generate CRC error for DL transmissions and schedule retransmissions for each
mission
HARQ NACK
crcErrorWithoutRetra
SS shall generate CRC error for DL transmissions but not do any retransmissions
nsmission
ETSI
3GPP TS 36.523-3 version 13.2.0 Release 13
480
ETSI TS 136 523-3 V13.2.0 (2017-03)
NB_DciDlInfoCommon_Type
TTCN-3 Record Type
Name
NB_DciDlInfoCommon_Type
Comment
Downlink control information according to 36.212 clause 6.4.3
Format
NB_PdcchDciFormat_Type
NPDSCH: N1; Paging: N2
RepetitionNum
integer
Defined in TS 36.213, clause 16.4.1.3
ber
DCISubFrame
integer
Defined in TS 36.213, clause 16.6
RepetitionNum
ber
SchedulingDela integer
opt Defined in TS 36.213, clause 16.4.1
y
Present for N1; not present for N2 (Paging)
HARQ_ACKRe integer
opt Defined in TS 36.213, clause 16.4.2
source
present for N1;
not present for N2 (Paging)
CRC_ErrorMod NB_CRC_ErrorMode_Type
no CRC error, CRC error with or without subsequent
e
retransmission by the SS
NB_DciDlInfoExplicit_Type
TTCN-3 Record Type
Name
NB_DciDlInfoExplicit_Type
Comment
Downlink control information according to 36.212 clause 6.4.3
Format
NB_PdcchDciFormat_Type
NPDSCH: N1; Paging: N2
Imcs
NPDSCH_ImcsValue_Type
MCS index of TS 36.213 Table 16.4.1.5.1-1
ResourceAssig integer
Defined in TS 36.213, clause 16.4.1.3: to determine the number
nment
of subframes
RepetitionNum
integer
Defined in TS 36.213, clause 16.4.1.3
ber
DCISubFr