36508-c41_s00-s04 - Free Download PDF Ebook

3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and V12.4.1 (2014-12) Evolved Packet Core (EPC); Technical Specification Common test environments for User Equipment (UE) conformance testing (Release 12) 3GPP TS 36.508 The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices. Release 12 2 3GPP TS 36.508 V12.4.1 (2014-12) Keywords mobile, UE, terminal, testing, LTE 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © 2014, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS™ is a Trade Mark of ETSI registered for the benefit of its members 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM Association 3GPP Release 12 3 3GPP TS 36.508 V12.4.1 (2014-12) Contents Contents............................................................................................................................................................ Foreword ........................................................................................................................ Introduction.................................................................................................................................................... 1 Scope.................................................................................................................................................... 2 References............................................................................................................................................ 3 Definitions, symbols and abbreviations................................................................................................ 3.1 3.2 3.3 4 Definitions......................................................................................................................................................... Symbols............................................................................................................................................................. Abbreviations..................................................................................................................................................... Common test environment.................................................................................................................... 4.1 Environmental conditions.................................................................................................................................. 4.1.1 Temperature................................................................................................................................................. 4.1.2 Voltage......................................................................................................................................................... 4.2 Common requirements of test equipment.......................................................................................................... 4.2.1 General functional requirements.................................................................................................................. 4.2.2 Minimum functional requirements............................................................................................................... 4.2.2.1 Supported Cell Configuration................................................................................................................ 4.2.2.1.1 Supported Channels.......................................................................................................................... 4.2.2.2 Support of Tcell timing offset................................................................................................................... 4.3 Reference test conditions................................................................................................................................... 4.3.1 Test frequencies............................................................................................................................................ 4.3.1.1 FDD Mode Test frequencies................................................................................................................... 4.3.1.1.1 FDD reference test frequencies for operating band 1....................................................................... 4.3.1.1.1A FDD reference test frequencies for CA in operating band 1............................................................ 4.3.1.1.2 FDD reference test frequencies for operating band 2....................................................................... 4.3.1.1.2A FDD reference test frequencies for CA in operating band 2............................................................ 4.3.1.1.3 FDD reference test frequencies for operating band 3....................................................................... 4.3.1.1.3A FDD reference test frequencies for CA in operating band 3............................................................ 4.3.1.1.4 FDD reference test frequencies for operating band 4....................................................................... 4.3.1.1.4A FDD reference test frequencies for CA in operating band 4............................................................ 4.3.1.1.5 FDD reference test frequencies for operating band 5....................................................................... 4.3.1.1.6 FDD reference test frequencies for operating band 6....................................................................... 4.3.1.1.7 FDD reference test frequencies for operating band 7....................................................................... 4.3.1.1.7A FDD reference test frequencies for CA in operating band 7............................................................ 4.3.1.1.8 FDD reference test frequencies for operating band 8....................................................................... 4.3.1.1.9 FDD reference test frequencies for operating band 9....................................................................... 4.3.1.1.10 FDD reference test frequencies for operating band 10..................................................................... 4.3.1.1.11 FDD reference test frequencies for operating band 11..................................................................... 4.3.1.1.12 FDD reference test frequencies for operating band 12..................................................................... 4.3.1.1.13 FDD reference test frequencies for operating band 13..................................................................... 4.3.1.1.14 FDD reference test frequencies for operating band 14..................................................................... 4.3.1.1.15 FDD reference test frequencies for operating band 15..................................................................... 4.3.1.1.16 FDD reference test frequencies for operating band 16..................................................................... 4.3.1.1.17 FDD reference test frequencies for operating band 17..................................................................... 4.3.1.1.18 FDD reference test frequencies for operating band 18..................................................................... 4.3.1.1.19 FDD reference test frequencies for operating band 19..................................................................... 4.3.1.1.20 FDD reference test frequencies for operating band 20..................................................................... 4.3.1.1.21 FDD reference test frequencies for operating band 21..................................................................... 4.3.1.1.22 FDD reference test frequencies for operating band 22..................................................................... 4.3.1.1.23 FDD reference test frequencies for operating band 23..................................................................... 4.3.1.1.23A FDD reference test frequencies for CA in operating band 23.......................................................... 4.3.1.1.24 FDD reference test frequencies for operating band 24..................................................................... 4.3.1.1.25 FDD reference test frequencies for operating band 25..................................................................... 3GPP Release 12 4.3.1.1.25A 4.3.1.1.26 4.3.1.1.27 4.3.1.1.27A 4.3.1.1.28 4.3.1.1.29 4.3.1.1.31 4.3.1.2 4.3.1.2.1 4.3.1.2.2 4.3.1.2.3 4.3.1.2.4 4.3.1.2.5 4.3.1.2.6 4.3.1.2.6A 4.3.1.2.7 4.3.1.2.7A 4.3.1.2.8 4.3.1.2.8A 4.3.1.2.9 4.3.1.2.9A 4.3.1.2.10 4.3.1.2.10A 4.3.1.2.11 4.3.1.2.12 4.3.1.3 4.3.1.3.1 4.3.1.3.2 4.3.1.3.3 4.3.1.3.4 4.3.1.3.5 4.3.1.3.6 4.3.1.3.7 4.3.1.4 4.3.1.4.1 4.3.1.4.2 4.3.1.4.3 4.3.1.4.4 4.3.1.4.5 4.3.1.4.6 4.3.1.4.7 4.3.1.5 4.3.1.5.1 4.3.1.5.2 4.3.1.5.3 4.3.1.5.4 4.3.1.5.5 4.3.1.5.6 4.3.1.5.7 4.3.1.5.8 4.3.1.5.9 4.3.1.5.10 4.3.1.5.11 4.3.1.5.12 4.3.1.5.13 4.3.1.5.14 4.3.1.5.15 4.3.1.5.16 4.3.1.5.17 4.3.1.5.18 4.3.1.5.19 4.3.1.5.20 4 3GPP TS 36.508 V12.4.1 (2014-12) FDD reference test frequencies for CA in operating band 25.......................................................... FDD reference test frequencies for operating band 26..................................................................... FDD reference test frequencies for operating band 27..................................................................... FDD reference test frequencies for CA in operating band 27.......................................................... FDD reference test frequencies for operating band 28..................................................................... FDD reference test frequencies for CA in operating band 29.......................................................... FDD reference test frequencies for operating band 31..................................................................... TDD Mode Test frequencies.................................................................................................................. TDD reference test frequencies for Operating Band 33................................................................... TDD reference test frequencies for Operating Band 34................................................................... TDD reference test frequencies for Operating Band 35................................................................... TDD reference test frequencies for Operating Band 36................................................................... TDD reference test frequencies for Operating Band 37................................................................... TDD reference test frequencies for Operating Band 38................................................................... TDD reference test frequencies for CA in operating band 38.......................................................... TDD reference test frequencies for Operating Band 39................................................................... TDD reference test frequencies for CA in Operating Band 39......................................................... TDD reference test frequencies for Operating Band 40................................................................... TDD reference test frequencies for CA in operating band 40.......................................................... TDD reference test frequencies for Operating Band 41................................................................... TDD reference test frequencies for CA in operating band 41.......................................................... TDD reference test frequencies for Operating Band 42................................................................... TDD reference test frequencies for CA in operating band 42.......................................................... TDD reference test frequencies for Operating Band 43................................................................... TDD reference test frequencies for Operating Band 44................................................................... HRPD Test frequencies.......................................................................................................................... HRPD test frequencies for Band Class 0.......................................................................................... HRPD test frequencies for Band Class 1.......................................................................................... HRPD test frequencies for Band Class 3.......................................................................................... HRPD test frequencies for Band Class 4.......................................................................................... HRPD test frequencies for Band Class 6.......................................................................................... HRPD test frequencies for Band Class 10........................................................................................ HRPD test frequencies for Band Class 15........................................................................................ 1xRTT Test frequencies.......................................................................................................................... 1xRTT test frequencies for Band Class 0......................................................................................... 1xRTT test frequencies for Band Class 1......................................................................................... 1xRTT test frequencies for Band Class 3......................................................................................... 1xRTT test frequencies for Band Class 4......................................................................................... 1xRTT test frequencies for Band Class 6......................................................................................... 1xRTT test frequencies for Band Class 10....................................................................................... 1xRTT test frequencies for Band Class 15....................................................................................... MFBI Test frequencies........................................................................................................................... MFBI Test frequencies for operation band 2 overlapping with band 25.......................................... MFBI Test frequencies for operation band 3 overlapping with band 9............................................ MFBI Test frequencies for operation band 4 overlapping with band 10.......................................... MFBI Test frequencies for operation band 5 overlapping with band 18.......................................... MFBI Test frequencies for operation band 5 overlapping with band 19.......................................... MFBI Test frequencies for operation band 5 overlapping with band 26.......................................... MFBI Test frequencies for operation band 9 overlapping with band 3............................................ MFBI Test frequencies for operation band 10 overlapping with band 4.......................................... MFBI Test frequencies for operation band 12 overlapping with band 17........................................ MFBI Test frequencies for operation band 17 overlapping with band 12........................................ MFBI Test frequencies for operation band 18 overlapping with band 5.......................................... MFBI Test frequencies for operation band 18 overlapping with band 26........................................ MFBI Test frequencies for operation band 18 overlapping with band 27........................................ MFBI Test frequencies for operation band 19 overlapping with band 5.......................................... MFBI Test frequencies for operation band 19 overlapping with band 26........................................ MFBI Test frequencies for operation band 25 overlapping with band 2.......................................... MFBI Test frequencies for operation band 26 overlapping with band 5.......................................... MFBI Test frequencies for operation band 26 overlapping with band 18........................................ MFBI Test frequencies for operation band 26 overlapping with band 19........................................ MFBI Test frequencies for operation band 26 overlapping with band 27........................................ 3GPP Release 12 5 3GPP TS 36.508 V12.4.1 (2014-12) 4.3.1.5.21 MFBI Test frequencies for operation band 27 overlapping with band 18........................................ 4.3.1.5.22 MFBI Test frequencies for operation band 27 overlapping with band 26........................................ 4.3.1.5.23 MFBI Test frequencies for operation band 33 overlapping with band 39........................................ 4.3.1.5.24 MFBI Test frequencies for operation band 38 overlapping with band 41........................................ 4.3.1.5.25 MFBI Test frequencies for operation band 39 overlapping with band 33........................................ 4.3.1.5.26 MFBI Test frequencies for operation band 41 overlapping with band 38........................................ 4.3.2 Radio conditions.......................................................................................................................................... 4.3.2.1 Normal propagation condition............................................................................................................... 4.3.3 Physical channel allocations........................................................................................................................ 4.3.3.1 Antennas................................................................................................................................................. 4.3.3.2 Downlink physical channels and physical signals................................................................................. 4.3.3.3 Mapping of downlink physical channels and signals to physical resources.......................................... 4.3.3.4 Uplink physical channels and physical signals...................................................................................... 4.3.3.5 Mapping of uplink physical channels and signals to physical resources............................................... 4.3.4 Signal levels................................................................................................................................................. 4.3.4.1 Downlink signal levels........................................................................................................................... 4.3.4.2 Uplink signal levels................................................................................................................................ 4.3.5 Standard test signals..................................................................................................................................... 4.3.5.1 Downlink test signals............................................................................................................................. 4.3.5.2 Uplink test signals.................................................................................................................................. 4.3.6 Physical layer parameters............................................................................................................................ 4.3.6.1 Downlink physical layer parameters...................................................................................................... 4.3.6.1.1 Physical layer parameters for DCI format 0..................................................................................... 4.3.6.1.2 Physical layer parameters for DCI format 1..................................................................................... 4.3.6.1.3 Physical layer parameters for DCI format 1A.................................................................................. 4.3.6.1.3A Physical layer parameters for DCI format 1B.................................................................................. 4.3.6.1.4 Physical layer parameters for DCI format 1C.................................................................................. 4.3.6.1.5 Physical layer parameters for DCI format 2..................................................................................... 4.3.6.1.6 Physical layer parameters for DCI format 2A.................................................................................. 4.4 Reference system configurations....................................................................................................................... 4.4.1 Simulated network scenarios....................................................................................................................... 4.4.1.1 Single cell network scenarios................................................................................................................. 4.4.1.2 E-UTRA single mode multi cell network scenarios............................................................................... 4.4.1.3 E-UTRA dual mode multi cell network scenarios................................................................................. 4.4.1.4 3GPP Inter-RAT network scenarios....................................................................................................... 4.4.1.5 3GPP2 Inter-RAT network scenarios..................................................................................................... 4.4.1.6 WLAN Inter-RAT network scenarios..................................................................................................... 4.4.2 Simulated cells............................................................................................................................................. 4.4.3 Common parameters for simulated E-UTRA cells...................................................................................... 4.4.3.1 Common configurations of system information blocks......................................................................... 4.4.3.1.1 Combinations of system information blocks.................................................................................... 4.4.3.1.2 Scheduling of system information blocks........................................................................................ 4.4.3.2 Common contents of system information messages.............................................................................. MasterInformationBlock........................................................................................................................ SystemInformation.................................................................................................................................. SystemInformationBlockType1............................................................................................................... 4.4.3.3 Common contents of system information blocks................................................................................... SystemInformationBlockType2............................................................................................................... SystemInformationBlockType3............................................................................................................... SystemInformationBlockType4............................................................................................................... SystemInformationBlockType5............................................................................................................... SystemInformationBlockType6............................................................................................................... SystemInformationBlockType7............................................................................................................... SystemInformationBlockType8............................................................................................................... SystemInformationBlockType9............................................................................................................... SystemInformationBlockType10............................................................................................................. SystemInformationBlockType11............................................................................................................. SystemInformationBlockType12............................................................................................................. SystemInformationBlockType13............................................................................................................. SystemInformationBlockType14............................................................................................................. SystemInformationBlockType15............................................................................................................. 4.4.3.4 Channel-bandwidth-dependent parameters in system information blocks............................................. 3GPP Release 12 6 3GPP TS 36.508 V12.4.1 (2014-12) 4.4.4 Common parameters for simulated UTRA cells.......................................................................................... 4.4.4.1 Common contents of system information blocks for UTRA cells......................................................... System Information Block type 19......................................................................................................... 4.4.4.2 UTRA SIB scheduling for inter EUTRA - UTRA test........................................................................... 4.4.4.3 UTRA SIB scheduling for inter EUTRA – UTRA - GERAN test......................................................... 4.4.5 Common parameters for simulated GERAN cells....................................................................................... 4.4.6 Common parameters for simulated CDMA2000 cells............................................................................... 4.4.7 Default parameters specific for simulated cells......................................................................................... 4.4.7.1 Common contents of HRPD Overhead messages................................................................................ 4.4.7.2 Common contents of 1XRTT Overhead messages............................................................................... 4.4.7.2.1 Configuration sequence number..................................................................................................... 4.4.7.2.2 Over Head messages....................................................................................................................... 4.5 Generic procedures.......................................................................................................................................... 4.5.1 UE test states.............................................................................................................................................. 4.5.2 UE Registration (State 2)........................................................................................................................... 4.5.2.1 Initial conditions................................................................................................................................... 4.5.2.2 Definition of system information messages......................................................................................... 4.5.2.3 Procedure.............................................................................................................................................. 4.5.2.4 Specific message contents.................................................................................................................... 4.5.2A UE Registration, UE Test Mode Activated (State 2A)............................................................................... 4.5.2A.1 Initial conditions................................................................................................................................... 4.5.2A.2 Definition of system information messages......................................................................................... 4.5.2A.3 Procedure.............................................................................................................................................. 4.5.2A.4 Specific message contents.................................................................................................................... 4.5.2B UE Registration, pre-registration on HRPD (State 2B)............................................................................. 4.5.2B.1 Initial conditions................................................................................................................................... 4.5.2B.2 Definition of system information messages......................................................................................... 4.5.2B.3 Procedure.............................................................................................................................................. 4.5.2B.4 Specific message contents.................................................................................................................... 4.5.2C UE Registration, pre-registration on 1xRTT (State 2C)............................................................................ 4.5.2C.1 Initial conditions................................................................................................................................... 4.5.2C.2 Definition of system information messages......................................................................................... 4.5.2C.3 Procedure.............................................................................................................................................. 4.5.2C.4 Specific message contents.................................................................................................................... 4.5.3 Generic Radio Bearer Establishment (State 3).......................................................................................... 4.5.3.1 Initial conditions................................................................................................................................... 4.5.3.2 Definition of system information messages......................................................................................... 4.5.3.3 Procedure.............................................................................................................................................. 4.5.3.4 Specific message contents.................................................................................................................... 4.5.3A Generic Radio Bearer Establishment, UE Test Mode Activated (State 3A).............................................. 4.5.3A.1 Initial conditions................................................................................................................................... 4.5.3A.2 Definition of system information messages......................................................................................... 4.5.3A.3 Procedure.............................................................................................................................................. 4.5.3A.4 Specific message contents.................................................................................................................... 4.5.3B Generic Radio Bearer Establishment, pre-registered on HRPD (State 3B)............................................... 4.5.3B.1 Initial conditions................................................................................................................................... 4.5.3B.2 Definition of system information messages......................................................................................... 4.5.3B.3 Procedure.............................................................................................................................................. 4.5.3B.4 Specific message contents.................................................................................................................... 4.5.3C Generic Radio Bearer Establishment, pre-registered on 1xRTT (State 3C).............................................. 4.5.3C.1 Initial conditions................................................................................................................................... 4.5.3C.2 Definition of system information messages......................................................................................... 4.5.3C.3 Procedure.............................................................................................................................................. 4.5.3C.4 Specific message contents.................................................................................................................... 4.5.4 Loopback Activation (State 4)................................................................................................................... 4.5.4.1 Initial conditions................................................................................................................................... 4.5.4.2 Definition of system information messages......................................................................................... 4.5.4.3 Procedure.............................................................................................................................................. 4.5.4.4 Specific message contents.................................................................................................................... 4.5.5 HRPD registration (State H2).................................................................................................................... 4.5.5.1 Initial conditions................................................................................................................................... 4.5.5.2 Definition of system information messages......................................................................................... 3GPP Release 12 7 3GPP TS 36.508 V12.4.1 (2014-12) 4.5.5.3 Procedure.............................................................................................................................................. 4.5.5.4 Specific message contents.................................................................................................................... 4.5.5A HRPD registration, pre-registration on E-UTRAN (State H2A)............................................................... 4.5.5A.1 Initial conditions................................................................................................................................... 4.5.5A.2 Definition of system information messages......................................................................................... 4.5.5A.3 Procedure.............................................................................................................................................. 4.5.5A.4 Specific message contents.................................................................................................................... 4.5.6 HRPD session establishment (State H3).................................................................................................... 4.5.6.1 Initial conditions................................................................................................................................... 4.5.6.2 Definition of system information messages......................................................................................... 4.5.6.3 Procedure.............................................................................................................................................. 4.5.6.4 Specific message contents.................................................................................................................... 4.5.6A HRPD session establishment, pre-registered on E-UTRAN (State H3A)................................................. 4.5.6A.1 Initial conditions................................................................................................................................... 4.5.6A.2 Definition of system information messages......................................................................................... 4.5.6A.3 Procedure.............................................................................................................................................. 4.5.6A.4 Specific message contents.................................................................................................................... 4.5A Other generic procedures................................................................................................................................. 4.5A.1 Procedure for IP address allocation in the U-plane.................................................................................... 4.5A.2 Tracking area updating procedure.............................................................................................................. 4.5A.3 Procedure for IMS signalling..................................................................................................................... 4.5A.4 Generic Test Procedure for IMS Emergency call establishment in EUTRA: Normal Service.................. 4.5A.4.1 Initial conditions................................................................................................................................... 4.5A.4.2 Definition of system information messages......................................................................................... 4.5A.4.3 Procedure.............................................................................................................................................. 4.5A.4.4 Specific message contents.................................................................................................................... 4.5A.5 Generic Test Procedure for IMS Emergency call establishment in EUTRA: Limited Service................. 4.5A.5.1 Initial conditions................................................................................................................................... 4.5A.5.2 Definition of system information messages......................................................................................... 4.5A.5.3 Procedure.............................................................................................................................................. 4.5A.5.4 Specific message contents.................................................................................................................... 4.5A.6 Generic Test Procedure for IMS MO speech call establishment in E-UTRA............................................ 4.5A.6.1 Initial conditions................................................................................................................................... 4.5A.6.2 Definition of system information messages......................................................................................... 4.5A.6.3 Procedure.............................................................................................................................................. 4.5A.6.4 Specific message contents.................................................................................................................... 4.5A.7 Generic Test Procedure for IMS MT Speech call establishment in E-UTRA........................................... 4.5A.7.1 Initial conditions................................................................................................................................... 4.5A.7.2 Definition of system information messages......................................................................................... 4.5A.7.3 Procedure.............................................................................................................................................. 4.5A.7.4 Specific message contents.................................................................................................................... 4.5A.8 Generic Test Procedure for IMS MO video call establishment in E-UTRA.............................................. 4.5A.8.1 Initial conditions................................................................................................................................... 4.5A.8.2 Definition of system information messages......................................................................................... 4.5A.8.3 Procedure.............................................................................................................................................. 4.5A.8.4 Specific message contents.................................................................................................................... 4.5A.9 Generic Test Procedure for IMS MT video call establishment in E-UTRA.............................................. 4.5A.9.1 Initial conditions................................................................................................................................... 4.5A.9.2 Definition of system information messages......................................................................................... 4.5A.9.3 Procedure.............................................................................................................................................. 4.5A.9.4 Specific message contents.................................................................................................................... 4.5A.10 Generic Test Procedure for IMS MO speech and aSRVCC in E-UTRA................................................... 4.5A.10.1 Initial conditions................................................................................................................................... 4.5A.10.2 Definition of system information messages......................................................................................... 4.5A.10.3 Procedure.............................................................................................................................................. 4.5A.10.4 Specific message contents.................................................................................................................... 4.5A.11 Generic Test Procedure for IMS MO add video establishment in E-UTRA.............................................. 4.5A.11.1 Initial conditions................................................................................................................................... 4.5A.11.2 Definition of system information messages......................................................................................... 4.5A.11.3 Procedure.............................................................................................................................................. 4.5A.11.4 Specific message contents.................................................................................................................... 4.5A.12 Generic Test Procedure for IMS MT add video establishment in E-UTRA.............................................. 3GPP ....5A..........................................................................................................................................................2 Definition of system information messages...............................................................................................................................................................14................12....................3 Procedure...................................................................................................... – CounterCheckResponse..14.................5A... 4....................................................5A............ – MBMSInterestIndication......................................................................3 Procedure..........................................................................................18.................... – RRCConnectionReestablishmentReject................................................................... – SecurityModeComplete........................... 4................................................5A................... – RRCConnectionReestablishmentComplete......................................................... – CSFBParametersResponseCDMA2000................... 4.................................5A....................................................................................16 Generic Test Procedure to establish additional PDN connectivity..........................................508 V12......................... – CounterCheck...5A............................................5A................................................................................................................................................................................................................................................................14........... 4............................. – UECapabilityEnquiry....................................................................................................................2 Definition of system information messages..................................................................... – RRCConnectionRequest..................................................5A.......... – MobilityFromEUTRACommand...................................17...................................................................................................... 4.............................................................18................................................. – RRCConnectionReject..................................................5A............................................5A........... 4...........................5A.........5A....... – SecurityModeCommand................... 4.............................................................................................. – RRCConnectionReconfiguration.....................................................................................................15.5A........................................................................................ – DLInformationTransfer.3 Procedure....................1 Initial conditions............................................12..................................................................................................14 Generic Test Procedure for IMS XCAP establishment in EUTRA........5A....................................................................... 4........................................................................................................................................................ – RRCConnectionReconfigurationComplete.................................................. – RRCConnectionSetup............. – MBMSCountingResponse................................................................................................................ 4.................................... 4...................................... 4..12........ – RRCConnectionSetupComplete..................... 4.................. – HandoverFromEUTRAPreparationRequest........................................................5A..................................................................17.....................................................................................................................17 Generic Test Procedure for user initiated release of additional PDN connectivity......3 Procedure.................................................................................15..................................................................................................................................................4 Specific message contents...................... LoggedMeasurementConfiguration...............2 Definition of system information messages........................................ 4.......5A.............................2 Definition of system information messages............... – MBMSCountingRequest..5A....................................................... – RRCConnectionReestablishment....................................................................... – CSFBParametersRequestCDMA2000.................................. 4.......5A.........................5A...4 Specific message contents................ 4............................................. 4....... 4.................................5A..........................18......................16.............................................................5A.. – RRCConnectionReestablishmentRequest......................................................1 Initial conditions.....................................................................18...3 Procedure............................................15.....15............................................................. 4.....5A.......................................................................................................................................................................................................................... 4....................................................................................................1 (2014-12) 4........................3 Procedure...........................................5A.......17....................... 4............... 4.................................................................................................1 Initial conditions...................................................................................................................................................5A...........................Release 12 8 3GPP TS 36. 4...................... – Paging...........5A.................5A..... – UECapabilityInformation.... – SecurityModeFailure......................6...............................................12........16.......................................................................................................... – MBSFNAreaConfiguration...................................................2 Definition of system information messages............................. 4..................................... 4.............................1 Contents of RRC messages.................... 4......................................................5A.........................2 Definition of system information messages.... – MeasurementReport.........................................1 Initial conditions............................................ 3GPP .................14.................................................................4 Specific message contents................................................................ 4.....4 Specific message contents.......................................4 Specific message contents............................................................................................................. 4....................................................5A.......................................................................... 4....................................................6 Default RRC message and information elements contents...............................................................4.................1 Initial conditions................ – UEInformationRequest......................................18 Generic Test Procedure for network initiated release of additional PDN connectivity..............................................5A......16............................................................... – RRCConnectionRelease.............................. 4.....................................................................................................................................................................................................4 Specific message contents............................................................................................................................1 Initial conditions..............................15 Generic Test Procedure for EPS Bearer Deactivation.......................................................... 4........................................................16.............................................17....... ..................................................................................................................... RadioResourceConfigDedicatedSCell-r10-DEFAULT.......................................................................................................................... PRACH-ConfigSIB-DEFAULT......................... RadioResourceConfigCommon-DEFAULT....................................................................................................................................................................................................................................................DRB-REL(bid)........................................................................ CQI-ReportConfig-r10-DEFAULT.................... SCellToRelease-r10-DEFAULT........................................................................ SoundingRS-UL-ConfigDedicated-DEFAULT................................................... PCCH-Config-DEFAULT.........................................................................................................1 (2014-12) UEInformationResponse................................................................................................................................................................................................................................................................................................................................ RadioResourceConfigDedicated............ SoundingRS-UL-ConfigDedicatedAperiodic-r10-DEFAULT............. UplinkPowerControlCommonSCell-r10-DEFAULT.................................................................... SchedulingRequest-Config-DEFAULT................................................................................................................ PUSCH-ConfigCommon-DEFAULT...........................................................4..................... RadioResourceConfigDedicated-UM-DRB-ADD(bid)....... RadioResourceConfigDedicated-AM-DRB-ADD(bid).............................................................................................................................................................................m).................................................................................................................. Radio resource control information elements.................................................................Release 12 – – – 4......................................... RadioResourceConfigDedicated-SRB2-DRB(n. UplinkPowerControlCommon-v1020-DEFAULT. PRACH-Config-DEFAULT.......................................... SoundingRS-UL-ConfigCommon-DEFAULT............................................................................................................................................................................. RadioResourceConfigDedicated-DRB(n..................... RadioResourceConfigDedicated-SRB1................................................................ CSI-RS-ConfigZP-r11-DEFAULT.............. PDSCH-ConfigDedicated-DEFAULT....................................................... CQI-ReportAperiodic-r10-DEFAULT.........................................................................................................................................................................3 – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – 9 3GPP TS 36................................................................................................................................................................................................ RLC-Config-DRB-AM-RECONFIG.................... SRB-ToAddModList-RECONFIG................................ PUCCH-ConfigCommon-DEFAULT..................................................................... CQI-ReportPeriodic-r10-DEFAULT.............................................................. ULInformationTransfer. RadioResourceConfigDedicated-HO.......................... Rach-ConfigDedicated-DEFAULT.......................6.............................................................................................m)...................................................................................................................................508 V12............................. EPDCCH-Config-r11-DEFAULT............ CQI-ReportConfigSCell-r10-DEFAULT.......................................................................... RadioResourceConfigDedicated-SCell_AddMod........................................................................................................................................................... PDSCH-ConfigDedicated-v1130-DEFAULT.......................... DRB-ToAddModList-RECONFIG................................................................................................................................................................................................................................................................................................................................................................................................................................................... PhysicalConfigDedicatedSCell-r10-DEFAULT.................................................................................................................................................................................................. RadioResourceConfigCommonSIB-DEFAULT................................. TDD-Config-DEFAULT........................................................................................................................................ RACH-ConfigCommon-DEFAULT.................... BCCH-Config-DEFAULT................................................................................................... TPC-PDCCH-Config-DEFAULT............................................................................................................................................................. PHICH-Config-DEFAULT................................................................................................................................................................................................................................................................................... PUCCH-ConfigDedicated-DEFAULT................................................ RLC-Config-SRB-AM-RECONFIG..................................... RadioResourceConfigDedicated-HO-TO-EUTRA(n..... SCellToAddMod-r10-DEFAULT............................................................................................................. UplinkPowerControlCommon-DEFAULT............. ULHandoverPreparationTransfer. UEAssistanceInformation.....................................................................................................................................................................................................................................................................................m).................................. CSI-RS-ConfigNZP-r11-DEFAULT................................................................................ PDSCH-ConfigCommon-DEFAULT.... PUSCH-ConfigDedicated-v1130-DEFAULT........................................................................... RLC-Config-DRB-UM-RECONFIG....................... PUCCH-ConfigDedicated-v1020-DEFAULT......................................................................................................................... PUSCH-ConfigDedicated-DEFAULT...........................................6...................................................2 4..... 3GPP ......................................................... DMRS-Config-r11-DEFAULT....................................... RadioResourceConfigCommonSCell-r10-DEFAULT. PUCCH-ConfigDedicated-v1130-DEFAULT.............................................................................................................................................................. CQI-ReportConfig-DEFAULT................................................... System information blocks..................................... ............................................................................................ ReportConfigEUTRA-A6............................................................................1 4. SecurityConfigSMC-DEFAULT................ MeasObjectUTRA-GENERIC..........................................................................................................................................................7 – – 4.................................... GUTI REALLOCATION COMPLETE.................. MeasGapConfig-GP1................................................................................................. SecurityConfigHO-DEFAULT........................................................................................................................................................................................................................................................ MeasObjectEUTRA-GENERIC.................................... EMM INFORMATION................................................................................................................... Mobility control information elements........................................................................................................................... EXTENDED SERVICE REQUEST...........4.................................................. AUTHENTICATION REQUEST................................................................................................................................................................... MeasObjectGERAN-GENERIC............................................................................................................. OtherConfig-r9...................................................................................................................................................................................... Channel-bandwidth-dependent parameters.................................................................. MeasGapConfig-GP2................................................................................................. RRC-TransactionIdentifier-DL................... Default NAS message and information element contents........ ReportConfigEUTRA-A3................................................................................................................................................................... ReportConfigInterRAT-B2-GERAN...................................................................................... ReportConfigEUTRA-PERIODICAL........................................................... MeasConfig-DEFAULT............... MeasObjectCDMA2000-GENERIC........................................ ReportConfigInterRAT-PERIODICAL.......................................................... AUTHENTICATION REJECT............. Security control information elements........................................................................................................................................................................................ DOWNLINK NAS TRANSPORT................. UplinkPowerControlDedicated-v1130-DEFAULT............................ AUTHENTICATION RESPONSE..................................................................................................................................................................................................... ReportConfigToAddModList_DEFAULT................................................ UplinkPowerControlDedicated-v1020-DEFAULT........... CS SERVICE NOTIFICATION................................. RadioResourceConfigDedicated-DRB-Mod........... QuantityConfig-DEFAULT.......................... DETACH REQUEST (UE terminated detach)...................................................................................7 4...................................................................................................508 V12..................... MobilityControlInfo-HO...........Release 12 – – – – 4......................................................................................................................................................................................................................................................................................................................................................................... ReportConfigInterRAT-B1-GERAN............................................................................................................................6.............................................1 (2014-12) UplinkPowerControlDedicated-DEFAULT............................................................................................................. DETACH REQUEST (UE originating detach)..................................................8 4...................................... ReportConfigInterRAT-B2-UTRA..................................................................................................................................................................................5 – 4........................................................................7........................................................................................................................................................................................................................................................................ EMM STATUS...................... Measurement information elements.... MeasIdToAddModList_DEFAULT......................................... ReportConfigInterRAT-B2-CDMA2000................................ ReportConfigEUTRA-A4............................................................................................. ReportConfigEUTRA-A1....................... RadioResourceConfigDedicated-PCell-PATTERN................................................................6 – – – 4.............................................................................................................. UplinkPowerControlDedicatedSCell-r10-DEFAULT.... ATTACH REJECT..........6.......... AUTHENTICATION FAILURE...................... ATTACH COMPLETE.................................................................... Security protected NAS messages..................................................................................................................................................................................................... ReportConfigInterRAT-B1-UTRA............................................................................................................ ReportConfigEUTRA-A2.......................................................................................................................................................................................................................................................................................................................................................................... ATTACH REQUEST.......................................................2 - 10 3GPP TS 36....................................... Contents of EMM messages..............................................7........................................................................................................................................................................................................................................................................................................................4 – – 4..................................... Other information elements.................. ATTACH ACCEPT........................................ DETACH ACCEPT (UE terminated detach).................................................................................................................................................................................... GUTI REALLOCATION COMMAND...........................................................................6...........6.......................................................................................................................... DETACH ACCEPT (UE originating detach)........................................................... ReportConfigEUTRA-A5................................... 3GPP ............................................................................................. RRC-TransactionIdentifier-UL..............6............................................... ............................................ BEARER RESOURCE MODIFICATION REQUEST........................................... MODIFY EPS BEARER CONTEXT REQUEST.................................. ESM INFORMATION RESPONSE.............................................................................................................................................................................3 4.... SECURITY MODE REJECT..............................................1 (2014-12) IDENTITY REQUEST................................................................................................................................................... DEACTIVATE EPS BEARER CONTEXT ACCEPT.................................................................................................................................. HANDOVER FROM UTRAN COMMAND.................................................... TRACKING AREA UPDATE REQUEST.................................... Default UTRA message and information element contents.. UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE............................. MODIFY EPS BEARER CONTEXT REJECT............... ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT...................................................................................................................................7A 4.................... SECURITY MODE COMPLETE...................................................................................................................................................................... TRACKING AREA UPDATE ACCEPT....... SERVICE REQUEST............................................................ BEARER RESOURCE MODIFICATION REJECT.......................................... UTRA RRC messages.............. UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST...............Release 12 4........................................7................................. TRACKING AREA UPDATE COMPLETE..................................................................................................................................................................................... TRACKING AREA UPDATE REJECT............................ Contents of ESM messages........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ DEACTIVATE TEST MODE COMPLETE.................................2 4... IDENTITY RESPONSE..............................................................7B................................................................................................................................................ PDN DISCONNECT REQUEST................................................................................................4............................................................................................................ BEARER RESOURCE ALLOCATION REJECT................................................................................. SECURITY MODE COMPLETE.........................................................................................1 – – – – – – – – – – – 4............................................................................................................................................................ SECURITY MODE COMMAND.. MODIFY EPS BEARER CONTEXT ACCEPT.............................................................................................................. CLOSE UE TEST LOOP COMPLETE............508 V12............................................................... OPEN UE TEST LOOP.............................................. OPEN UE TEST LOOP COMPLETE...................................................................... RRC CONNECTION REQUEST............................................. ESM STATUS.... SECURITY MODE COMMAND............................................................................................................................................................ PDN CONNECTIVITY REQUEST....................... UPLINK NAS TRANSPORT................... UTRAN MOBILITY INFORMATION CONFIRM...............................................................................................................................................................................7C 11 3GPP TS 36................................................. MEASUREMENT CONTROL............................................................................................................. BEARER RESOURCE ALLOCATION REQUEST...................... ACTIVATE TEST MODE...................................................... ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT..............................7B................................................................................................................................................................... DEACTIVATE EPS BEARER CONTEXT REQUEST............................ ACTIVATE TEST MODE COMPLETE.................................. Default DS-MIPv6 message and information element contents.. UTRAN MOBILITY INFORMATION............... ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST.............................................................................................................................................. CLOSE UE TEST LOOP............................................................................................................................... Default TC message and information element contents................................................................... 3GPP ............................................................................................................................................................................................................................................................................................................................ ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT................................................................................................................................... NOTIFICATION....... DEACTIVATE TEST MODE.......................... UTRA NAS messages....................................................... ESM INFORMATION REQUEST........................................................................................ ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST......................... HANDOVER TO UTRAN COMMAND..................................................................... PDN DISCONNECT REJECT...........7B 4................................................................................................................. PHYSICAL CHANNEL RECONFIGURATION............................................................. MEASUREMENT REPORT............................................................................................................................ SERVICE REJECT............................................................................................................ PHYSICAL CHANNEL RECONFIGURATION COMPLETE..................................................................................... ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT...................................................................................................................................... PDN CONNECTIVITY REJECT.............................................................. ............................................................8.........................2 Messages used to perform DS-MIPv6 registration and deregistration............7D Default GERAN message and information element contents................... 5....................8..............................2 Generic Default Radio Bearer Establishment... UE Test Mode Activated (State 2A-RF).......................................................................................................................... IKE_AUTH Response.....................2................................................2 SRB and DRB parameters and combinations.. 4............3 DRB RLC configurations.............8.............4 GERAN reference PDP context parameters................1 Common parameters for simulated E-UTRA cells.........2......9.........5 MAC configurations..........................................................................................8.............................1..............2.......................... 4................................9...2....... 5.........................2A......................2A Generic RF procedures.................................................................................1..........................................................................................................................................................................1 GPRS message..........1..............8........................................1 General................................2 RF Reference system configurations................................................. 4......... IKE_AUTH_Request..3 Default settings for the Elementary Files (EFs).....................................................1 Combinations on DL-SCH and UL-SCH..........508 V12.................................. 4...................................................... 4............................. CSIM and ISIM.............. Binding Revocation Acknowledgement.....................................................................................2A................................................................................................................................1 General.....................9 Common test USIM.8 Reference radio bearer configurations......................... 4...4 Specific message contents...8............2...................8.......... 3GPP ...1 SRB and DRB parameters..............................2A....................................................................................................2A........4........... 5 Test environment for RF test.........8..............................9.......................... 5.......................................1 Definitions.................2 Modified contents of the CSIM Elementary Files......................2A...1 Modified contents of the USIM Elementary Files..................................................... 5................................................................... 5... 5.................. 4............................7D.................................................................................................................... 4...........................................................................2A..........................................2 Definition of system information messages................................................................................ 4........ 5. CSIM and ISIM and SS......9....1................ 4.................Release 12 12 3GPP TS 36............ 5..............2 Definition of system information messages..................................................................................................................................... 4......... IKE_SA_INIT Response........................................ 5......................................... 4. 5......1A................................................9.................................................1................................................ 5................................1 (2014-12) 4........................................................1........................2....1A Registered..................... UE Test Mode Activated (State 3A-RF)..8....................8..........1.............................. Binding Acknowledgement................................. 4.7 DRB configurations.................................................................. 5..................................1 Requirements of test equipment....................................1 Initial conditions...........9..............2......1...................2..................................................... Idle Mode.......... 4.....................................2........6 Physical Layer configurations................2 Scheduling of system information blocks..........3......................................................8...................................................................................................... 4.........2 Generation of re-synchronization parameters in the USIM................................3 Using the authentication test algorithm for UE conformance testing........................8....................... 4.... 4..................................... IKEv2 IKE_SA_INIT Request.......................................1 SRB configurations............................................................. 4..................... CSIM and ISIM parameters.................1 Combinations of system information blocks............................................................................................................................1 Authentication and key derivation in the test USIM.. 5.......................................................8............. CSIM and ISIM.............. 5................................................... 5..................................1........................ 4...............................................1 Initial conditions............................................2A...1..............................................................1 Initial conditions........................ 4.....................................................................................................................................2.......... 4...........................1.................... 4..............1A.........................2....................2..............9........................2.................................................9...........................3 Loopback Activation without looped data (State 4A-RF)..............2A.......9..................................................................................... 5.................................... 4.......2 Definition of the test algorithm for authentication.......................................... 4.1......................................2............................................................7C.......1A......................................................... 4................4 Specific message contents...........................................................................2.........3 Procedure......................................................... 5..............2 SRB and DRB combinations....3 UTRA reference radio parameters and combinations................... Binding Revocation Indication.................................2.....3.....................................3 Procedure.............3.................................... Binding Update..................2 Default parameters for the test USIM......................2.........2.8..............................................................................................2.......................................... 5..................................2 DRB PDCP configurations....................................................................1A................................................................ 5..........2A....................................................................1 UE RF test states......................................................... 5........7C...........................................................................1...............................2A.................3 Common contents of system information messages.....2................................................................................................4 DRB Logical Channel configurations............ – PS HANDOVER COMMAND.........2A...........................................1 IKEv2 messages.........9....2.........................2A....1.................2....... Router Advertisement.....................2A....................................................................... 4................. 4..............1............................................................................. 4............................ 4. ....1................................ Test frequencies for CA signalling test.. Default parameter specific for simulated cells............3..... Measurement accuracy and side conditions......1.......................................1....................................................3.........2 6..........2......... Broadcast only cell configuration.....3...................................... 5.......................... Inter-frequency carrier frequency list in SIB5 for E-UTRA NAS cells......................................4.................................................3A 6.......2 6........4 6............. Mapping of uplink physical channels and signals to physical resources.....4 6.....................................3......... Simulated NAS cells...........................2.................2 6............................................................2A......................................3.......... CDMA2000 HRPD carrier frequency list in SIB8 for E-UTRA cells..........................................2 6..............3................................... Uplink physical channels and physical signals..............................................2 6........... Application of different cell configurations..........Release 12 13 3GPP TS 36..................................1 6.2A...........................5 6....5 6............................2 6...............2..............................................................7 6.....................................................................................3.................1 Exceptions for all CA tests........................................1 MAC configurations.................................................3..1 6...3....................................................1 6............................1................... Specific message contents........................1 6.......... 5...........2 Definition of system information messages...............................................1.....................................3..........1................1 6............. Inter-frequency carrier frequency list in SIB5 for E-UTRA cells....... Test frequencies for signalling test................3 6.............................................2......................................................................................................................2.......... Intra-frequency neighbouring cell list in SIB4 for E-UTRA NAS cells.................... 5......2...................................... Initial conditions........ Downlink signal levels.....................1 Combinations on DL-SCH and UL-SCH.......................................................................... Initial UE states and setup procedures...4.3...3........................................................................2 6..........................................................3.... 5.............................. 5...........................................3 Default RRC message and information elements contents.2A............................................................... Generic procedures..........................2...................... Virtual cell configuration.............................................2.........................................................................................................2...........................................................2.......2A.............................. GERAN carrier frequency group list in SIB7 for E-UTRA cells.............................................................................................................................................................................................................3........................................................................ 5....................3.................................................. Broadcast system information............4 6........2...........................................1...............................................................................................3 6........41................. Intra-frequency neighbouring cell list in SIB4 for E-UTRA cells................. Antennas.........2...................5..3..........1 6.......................................... Signal levels..................................2 A.......................1 Radio resource control information elements................................. E-UTRA carrier frequency list in SIB19 for UTRA cells.3 6......................................................................................... Full cell configuration.....2..... 5.......1..............4.............3..................1 Requirements of test equipment.................................4 Procedure to configure SCC.........4 Specific message contents........ 5. Specific message contents.......... Simulated network scenarios for NAS test cases..........1.........1 SRB and DRB parameters.............................. Cell configurations.............. Physical channel allocations..........................................................................................1..................................3....................................1 6...........................................................................................................................................5.................................................................................................. Initial UE states and setup procedures............................................1 Neighbour cell info for all feICIC test cases........................................................ SCell configurations........................ Dedicated Bearer Establishment (to state 5)............3....... Mapping of downlink physical channels and signals to physical resources.....................2 Physical Layer configurations...... Reference system configurations.......3 Procedure.........3.....................1.............1 6..............3 6.2A.....4..............................................................2 6........................................3 SRB and DRB combinations............................3..................3 6................. Downlink physical channels and physical signals......................................5 Exceptions for feICIC tests..................3...... 3GPP .............................................................................................. 5.....................................................................................................................................................3.....................................................5......3..........3 6............................1 6.................................................................2....5 Reference radio bearer configurations...3 6.....5...........................1........................2A...................................2A.....................................1.4.2A.....................................................2 Exceptions for UL CA tests.... 5.............................. 5..................................................................4................................ 5..5........... 5...........1 6....................................................................1................3.....4 Default NAS message and information elements contents.......3...2 6........2...........................................1............3...............6 6.......................................... UTRA carrier frequency list in SIB6 for E-UTRA cells........................................ Reference test conditions.4.3.....1..............................................................................................................................................1...........5........................508 V12...............2............................ 6....................................................2.............1 6........................................................1..............1............................3........... Default configurations for NAS test cases.1 (2014-12) 5..................... 5.......................................................................1...................3. 5......1............. Minimum uplink cell configuration..........1.................................................3........2.......... Default test frequencies............................................. CDMA2000 1xRTT carrier frequency list in SIB8 for E-UTRA cells................2A.......................... 5.............................2...................................... 5..............2 6....3............2 6.................................1 6.....5............................1..................................2.....................................4 6................ 5........... 6 Test environment for Signalling test.....3....3.4 6.................................................3... ................................................... 6............................................2 Reference end states..........3A........................ Loopback Activation (to state 6).. 6.......................................................2 6.........4.......................3............. 6...........1..................... 6.3..8.4.........3A Test case postambles................4........................................... Test procedure to check that UE is camped on E-UTRAN cell upon mobility from another RAT ........................................1 Reference default EPS bearer contexts.... Procedure......2.............................4...3...............6...2................4 CS fallback to GERAN with PS Handover / MO call (EDTM not supported).........................................................3.........3 6........................................4................................................................................4......4.......... 6.............7 CS fallback to UTRAN with Handover / emergency call... 6.........5 6........ 6..........1 Introduction...............................................3...................4.............. 6. Test procedure to check RRC_IDLE state.............................4.................................................................... Test procedure to check that UE is camped on a new E-UTRAN cell........................................................................ Specific message contents.........7................4......................... 6..................4................................................................................................6 Default NAS message and information element contents.. 6...........................................................8............. Test procedure to check RRC_CONNECTED state............1 CS fallback to GERAN with redirection or CCO / MT call (DTM not supported)......................4..................................................3....................................................................................................... 6................................... 6....4.........2............4..................3......................................2..6 6.....................3.............................................. 6.......................... Test procedure Paging (for NAS testing).....2 6................3..........................................2 Reference dedicated EPS bearer contexts........................................4.................8...............4..................4.........................4.........................4...................................3 6............3....8 Test procedure to check that UE is camped on a new UTRAN cell.....................7..............2 UE triggered establishment of a default EPS bearer context associated with an additional PDN .................................... Test procedure for no response to paging (for NAS testing).4....................... 6..............1 6.......3...........6...................6 UE triggered MO SMS over SGs...................3...........................5 UE triggered CS call....4.....8.....................................................................1...... 6.......3...........................................2....... 6..........................3...................3............... 6.....4... 3GPP ..........................................1........... 6......................4...........................................................................................4..........................6 CS fallback to UTRAN with Handover / MO call..........................................5..................................7 6.......... Procedure... Introduction.8............................4.....1................. 6.................................5 CS fallback to UTRAN with Handover / MT call............4..........................................3.7.....3.....4........ 6......................................................... Specific message contents....5 Default RRC message and information element contents... 6..7..............2.....6...........................1 Measurement information elements................................................................ 6....................................5 CS fallback to GERAN with PS Handover / MT call (EDTM supported).....................7. Definition of system information messages.......................................4 6...Release 12 14 6.....3.....2 6......4.............3......................................................3 CS fallback to GERAN with PS Handover / MT call (EDTM not supported).......................................................................3............2. 6.......................................4 UE triggered deletion of an EPS bearer context...............................................2 CS fallback to GERAN with redirection or CCO / MO call (DTM not supported)..................4....................4.... Initial conditions............1.... 6............2..4.............10 Test procedure to check that UE performs tracking area updating procedure without ISR and security reconfiguration after successful completion of handover from UTRA.....3.....................4.4......1........4 6.........4..3 6................3.....4........................................................................................1 UE triggered establishment of a dedicated EPS bearer context........... 6..... 6.............................3A............................................................................................. 6......3............... 6.......4......4................2....................1 Specific message contents. 6.....................................1 Specific message contents..7.......................4...2....... Test procedure to check that a dedicated EPS bearer context is active (for NAS testing)..................4.................8 CS fallback to GERAN procedures (LAI of GERAN cell same as the LAI received in combined Attach procedure in EUTRA cell)..........2..3 Reference test procedures for TTCN development...............2 6.......................9 SRVCC Handover to UTRA...................................................................4..4.............................. 6......9...................4...............................1.............................7A 3GPP TS 36....................................3 6.......................4 CS fallback to UTRAN with redirection / MO call (PS bearer established).......4........................7.................................................4................... 6........1.........1 CS fallback to UTRAN with redirection / MT call (PS bearers not established).................................2 CS fallback to UTRAN with redirection / MO call (PS bearers not established).... 6...4......................3 UE triggered modification of an EPS bearer context....................................................3..........................................................1 Specific message contents. MeasGapConfig-GP1......................................3................3 CS fallback to UTRAN with redirection / MT call (PS bearer established)................................................508 V12...............................3... 6..7............3...... 6........1 Specific message contents....2...7...7 CS fallback to UTRAN procedures (LAI of UTRAN cell same as the LAI received in combined Attach procedure in EUTRA cell).................9 Test procedure to check that UE is camped on a new GERAN cell.......................4...........1 6.............................................................2...................4............................................................ Test procedures....................1 (2014-12) Definition of system information messages............................... 6........................4........... MeasGapConfig-GP2.......... 6..................5......................................................................4.......3........4 6.........................................................................................................3.....................................7.......2.............4.................................... 6........ MeasConfig-DEFAULT................................7............... ................4....4 Requirements of test equipment.............................................. 7........................... Mapping of GERAN cells...................................................1 (2014-12) 6.......................................... 7....................2 Short Message Relay Layer (SM-RL) messages......Release 12 15 3GPP TS 36....................................................................................................... 7.....................................3..........1 SRB and DRB parameters....................................................................6B..................1 7....................................................................................................................................6B............. 7.......................................................................4............................................... Generic Default Radio Bearer Establishment................................3...................................2A..1..................2........... SMS-SUBMIT.... CP-ACK.........................................................................2 7........................7 Timer Tolerances........2A.3 Measurement information elements................................................................. Specific message contents..................................................................................................................................................2........................................................................................................................1 Contents of RRC messages...............................................................................2..............................................................................6A.........................4..................................... 6................ RP-DATA RPDU...................................................................................... 7...............................................................................................2A............1 Physical Layer configurations........................................2.................5.....................................................1 7................4.3 7....................................................................... 6........... Generic Default Radio Bearer Establishment...................2A........................... 6............................4............2..............3 7...................................................................................................2 7..... UE Registration..........3....................... 7 Test environment for RRM tests......1 7............................................................1 7.2 Definition of system information messages................... UE Test Mode Activated (State 2A-RF).................................................................................. 7.......................................1 Tracking area updating procedure................................... Combinations of system information blocks.......2A.........................................................................5....................2A...................................................... Common parameters for simulated GERAN cells................................................................................................................................................................................ CP-DATA............ 7.......... 7.....3 Procedure.. 7....................................................... 7..................6A Default SMS over SGs message and information element contents.................................................................. SMS-DELIVER................................ 6.......... RP-ACK RPDU...2A.............. Generic RRM procedures.................................................. Common parameters for simulated E-UTRA cells................... 6...................................................................2 Radio resource control information elements........................................1 Initial conditions...............................508 V12.................................................................1.5 Reference radio bearer configurations........ UE Test Mode Activated (State 3A-RF)...............................1............................................................................................................................................ 7..................................6A............................................ 6..............................................................................................................................................5 Procedure to configure SCC..................................6 Exceptions for feICIC tests......2A..........6B Reference radio bearer configurations..................1 SRB and DRB parameters and combinations....................................1........2A................................................................2...........................................1....................................................................2 7..........1 SRB and DRB parameters......................................................2A...6B.............................................1 MAC configurations..................................................2 7............................................................................................................................................................................................3 Default RRC message and information elements contents............................................. 7.... 3GPP .................................... 6................................................1................................................................................................................................................................................................... RRM Reference system configurations......................2..............1 7........ 7........ 7....... 7..... 7................................................ 7... Common contents of system information messages..........2B............................................................................................... Scheduling of system information blocks......................3 Short Message Transfer Layer (SM-TL) messages.....6A....2A 7...... UE Test Mode Activated..........................1........................................... Annex A (informative): Connection Diagrams..................................... UE RRM test states. pre-registration on HRPD (State 3B-RF)............... Annex B (informative): Change history.........1 CM-sublayer messages....................................................................................................................4 Specific message contents....................................4 Default NAS message and information elements contents.........................2B Other generic RRM procedures.......................................................................................... 6................................................................ y. 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.1 (2014-12) Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). updates.508 V12. etc. 3 or greater indicates TSG approved document under change control. technical enhancements. y the second digit is incremented for all changes of substance. The present document defines default values for a variety of common areas. Hence the present document defines testing conditions that are common to several tests avoiding the need to duplicate the same information for every single test. EMC and Protocol aspects of the UE. i. 3GPP . constraints and performance.e.z where: x the first digit: 1 presented to TSG for information. 2 presented to TSG for approval. If specified. Where values are not specified in test cases. the test case values will take precedence. corrections. the defaults in the present document will apply.4. Introduction The definition of the Conformance Tests for UE in E-UTRAN will be a complex task as the complete test suite covers RF. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Each test requires a Test Environment to be defined in which the UE has to operate to defined standards. z the third digit is incremented when editorial only changes have been incorporated in the document.Release 12 16 3GPP TS 36. The overall task can be simplified if there are a number of well defined and agreed Common Test Environments where every one can be used for a number of tests. Should the TSG modify the contents of the present document.  For a non-specific reference.109: "Terminal logical test interface. a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.304: "Evolved Universal Terrestrial Radio Access (E-UTRA).Release 12 1 17 3GPP TS 36.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".123-3: "User Equipment (UE) conformance specification. [14] 3GPP TS 36. addressing and identification". the latest version applies. Radio Link Control (RLC) protocol specification". 3GPP .003: "Numbering.) or non-specific.905: "Vocabulary for 3GPP Specifications". [11] 3GPP TS 36.008: "Mobile radio interface Layer 3 specification. Services provided by the physical layer". constitute provisions of the present document. default parameters. Special conformance testing functions".  References are either specific (identified by date of publication. Part 1: Protocol conformance specification". [5] 3GPP TS 34. Part 3: Abstract test suites (ATSs)". [9] 3GPP TS 34. version number. common radio bearer configurations for other test purposes. edition number. common requirements for test equipment and generic set-up procedures for use in conformance tests for the 3rd Generation E-UTRAN User Equipment (UE).322: "Evolved Universal Terrestrial Radio Access (E-UTRA). [2] 3GPP TS 23.108: "Common Test Environments for User Equipment (UE). [15] 3GPP TS 36. reference radio bearer configurations used in radio bearer interoperability testing. Core network protocols.123-1: "User Equipment (UE) conformance specification.321: "Evolved Universal Terrestrial Radio Access (E-UTRA). [10] 3GPP TS 36. [1] 3GPP TR 21.  For a specific reference. Medium Access Control (MAC) protocol specification".4. [7] 3GPP TS 34. Overall description. 2 References The following documents contain provisions which. Conformance testing".302: "Evolved Universal Terrestrial Radio Access (E-UTRA). User Equipment (UE) radio access capabilities". subsequent revisions do not apply. [3] 3GPP TS 23. User Equipment (UE) procedures in idle mode". through reference in this text.123-2: "User Equipment (UE) conformance specification. Stage 2".508 V12. Stage 3".300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN). In the case of a reference to a 3GPP document (including a GSM document). Part 2: Implementation conformance statement (ICS) specification".306: "Evolved Universal Terrestrial Radio Access (E-UTRA).1 (2014-12) Scope The present document contains definitions of reference conditions and test signals. [6] 3GPP TS 34. [8] 3GPP TS 34. [12] 3GPP TS 36. [4] 3GPP TS 24. etc. [13] 3GPP TS 36. 102: "Characteristics of the Universal Subscriber Identity Module (USIM) application". Radio transmission and reception.104: "Evolved Universal Terrestrial Radio Access (E-UTRA). Packet Data Convergence Protocol (PDCP) specification".211: "Evolved Universal Terrestrial Radio Access (E-UTRA). User Equipment (UE) conformance specification. [21] 3GPP TS 36.0: "Signalling Conformance Test Specification for cdma2000 Spread Spectrum Systems". Part 1: Protocol conformance specification".401: "General Packet Radio Service(GPRS) enhancements for Evolved Universal Terrestrial Access Network (E-UTRAN) access". [31] 3GPP TS 33.521-2: "Evolved Universal Terrestrial Radio Access (E-UTRA).0: "Signalling Conformance Specification for High Rate Packet Data Air Interface".401: "3GPP System Architecture Evolution (SAE). Part 1: conformance testing".4.523-2: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC).508 V12.521-3: "Evolved Universal Terrestrial Radio Access (E-UTRA). Part 2: Implementation Conformance Statement (ICS) proforma specification". [24] 3GPP TS 23. [17] 3GPP TS 36. Security architecture". Physical layer procedures". [37] 3GPP2 TSG-C C. User Equipment (UE) conformance specification. [29] 3GPP TS 36. [23] 3GPP TR 24. User Equipment (UE) conformance specification. [28] 3GPP TS 24. Radio Resource Control (RRC).101: "Evolved Universal Terrestrial Radio Access (E-UTRA).101: "UICC-terminal interface. Physical and logical characteristics". [34] 3GPP TS 36. Part 1: Conformance specification ". [30] 3GPP TS 36. [33] 3GPP TS 31. [22] 3GPP TS 36. [20] 3GPP TS 36. [35] 3GPP TS 36.801: "3GPP System Architecture Evolution.331: "Evolved Universal Terrestrial Radio Access (E-UTRA).Open Systems Interconnection . User Equipment (UE) conformance specification. [18] 3GPP TS 36. Base Station (BS) radio transmission and reception". 3GPP . Stage 3". [19] 3GPP TS 36. Part 3: Radio Resource Management conformance testing". [26] ISO/IEC 9646 (all parts): "Information technology .323: "Evolved Universal Terrestrial Radio Access (E-UTRA).010-1: "Mobile Station (MS) conformance specification. 523-1: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC). User Equipment (UE) conformance specification. Part 3: Abstract Test Suites (ATS)". [25] 3GPP TS 51. Part 2: Implementation Conformance Statement (ICS)".1 (2014-12) [16] 3GPP TS 36. [36] 3GPP2 TSG-C C.S0038-B v1. Physical channels and modulation". [32] 3GPP TS 31. User Equipment (UE) conformance specification.Release 12 18 3GPP TS 36.523-3: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC). User Equipment (UE) radio transmission and reception". Protocol Specification". CT WG1 aspects".521-1: "Evolved Universal Terrestrial Radio Access (E-UTRA).301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS). Radio transmission and reception. Radio transmission and reception.213: "Evolved Universal Terrestrial Radio Access (E-UTRA).Conformance testing methodology and framework".S0043-A v1. [27] 3GPP TS 36. Addendum 2".402: “Architecture enhancements for non-3GPP accesses” [42] 3GPP2 X.229-1: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).Part 1: Conformance specification ". 3 Definitions.Release 12 19 3GPP TS 36. 3.508 V12. [45] 3GPP TS 31. the terms and definitions given in TR 21. the following symbols apply: NDL NRB Downlink EARFCN Transmission bandwidth configuration. H: a value followed by "H" is a hexadecimal value.0: "cdma2000 Application on UICC for Spread Spectrum Systems".121-1: "User Equipment (UE) conformance specification.S0024-B v3. expressed in units of resource blocks 3GPP . [46] 3GPP TS 34.509: "Evolved Universal Terrestrial Radio Access (E-UTRA). [49] 3GPP2 C. [44] 3GPP2 C. Stage 3" [41] 3GPP TS 23.4.0: "cdma2000 High Rate Packet Data Air Interface Specification". [48] 3GPP2 C. unless specified below: B: a value followed by "B" is a binary value. Part 3: Abstract Test Suite (ATS)". Radio transmission and reception (TDD)".1 Definitions For the purposes of the present document.229-3: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).S0057-0-B v1.S0065-B v2. Part 1: Protocol conformance specification ". User Equipment (UE) conformance specification.92: "IMS Profile for Voice and SMS". User Equipment (UE) conformance specification. [51] 3GPP TS 34.229-1: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). symbols and abbreviations 3.eHRPD Connectivity and Interworking: Core Network Aspects” [43] 3GPP TS 34. Requirements for support of radio resource management" [40] 3GPP TS 24. [47] 3GPP TS 34.122: "Terminal conformance specification.0 “E-UTRAN .2 Symbols For the purposes of the present document. Radio transmission and reception (FDD). [50] 3GPP TS 34.133: "Evolved Universal Terrestrial Radio Access (E-UTRA). Part 1: Protocol conformance specification".905 [1] apply.1 (2014-12) [38] 3GPP TS 36.S0005-F v1. Special conformance testing functions for User Equipment (UE)" [39] 3GPP TS 36. [52] GSMA PRD IR. User Equipment (UE) conformance specification.103: "Characteristics of the IP Multimedia Services Identity Module (ISIM) application".0: "Upper Layer (Layer 3) Signalling Standard for cdma2000 Spread Spectrum Systems – Release A. +55C). These test conditions are denoted as TL (temperature low. shall not make ineffective use of the radio frequency spectrum. 4.3 Abbreviations For the purposes of the present document.1 (2014-12) Aggregated Transmission Bandwidth Configuration.101 [27] Annex E. the abbreviations specified in TR 21. 3GPP .1 Temperature The UE shall fulfil all the requirements in the full temperature range of: Table 4.1. -10C) and TH (temperature high.905 [1] apply.1 Environmental conditions The requirements in this clause apply to all types of UE(s). if powered on. Uplink EARFCN 3.4. The number of the aggregated RBs within the fully allocated Aggregated Channel bandwidth.1.Release 12 NRB_agg NUL 20 3GPP TS 36. with any additional abbreviations specified below: 1xRTT CA CC DRB EARFCN ECM EMM ENB EPRE ESM HRPD MAC OFDM RBs ROHC SS TH TL TP VH VL xCH_RA xCH_RB 4 1x Radio Transmission Technology Carrier Aggregation Component Carrier (user) Data Radio Bearer E-UTRA Absolute Radio Frequency Channel Number EPS Connection Management EPS Mobility Management Evolved Node B Energy Per Resource Element EPS Session Management High Rate Packet Data Media Access Control Orthogonal Frequency Division Multiplexing Resource Blocks Robust Header Compression System Simulator Temperature High Temperature Low Transmission Point Higher extreme Voltage Lower extreme Voltage xCH-to-RS EPRE ratio for the channel xCH in all transmitted OFDM symbols not containing RS xCH-to-RS EPRE ratio for the channel xCH in all transmitted OFDM symbols containing RS Common test environment 4. Some tests are performed also in extreme temperature conditions. In no case shall the UE exceed the transmitted levels as defined in TS 36.508 V12.101 [27] for extreme operation.1. The normative reference for this requirement is TS 36.1-1: Temperature Test Environment +15C to +35C -10C to +55C for normal conditions (with relative humidity up to 75 %) for extreme conditions (see IEC publications 68-2-1 and 68-2-2) Outside this temperature range the UE. In no case shall the UE exceed the transmitted levels as defined in TS 36.9 * nominal 0. In addition.1 General functional requirements NOTE: This clause has been written such that it does not constrain the implementation of different architectures and designs of test equipment. as specified in the minimum requirement.Release 12 21 3GPP TS 36. The manufacturer shall declare the lower and higher extreme voltages and the approximate shutdown voltage. The test equipment shall use the same number of Tx antennas for all parts of the tests.2.101 [27] Annex E.2 Voltage The UE shall fulfil all the requirements in the full voltage range.2 Common requirements of test equipment Mobile conformance testing can be categorized into 3 distinct areas:  RF Conformance Testing. 4. However. 3GPP . and these are specified in this clause.508 V12. For the equipment that can be operated from one or more of the power sources listed below. Table 4.1 * nominal 1. Initial condition and Test procedure. In particular.95 * nominal 0. these would not form a common test equipment requirement for the three test areas and are not considered in the present document.1 * Nominal Nominal Outside this voltage range the UE if powered on. All test equipment used to perform conformance testing on a UE shall provide a platform suitable for testing UE's that are either: a) FDD Mode. the lower extreme voltage shall not be higher.e.2. or b) TDD Mode.1 * Nominal Nominal 1. depending on the supplier of the test equipment.  EMC Conformance Testing.9 * nominal Higher extreme voltage 1. shall not make ineffective use of the radio frequency spectrum.1.  Signalling Conformance Testing. and the higher extreme voltage shall not be lower than that specified below.90 * nominal Nominal 1. or c) both FDD/TDD Modes. EUTRAN plus UTRAN).101 [27] for extreme operation.3 * nominal Normal conditions voltage nominal 1. the voltage range between the extreme voltages.1 * nominal 0.1 (2014-12) 4. These test conditions are denoted as VL (lower extreme voltage) and VH (higher extreme voltage).85 * nominal 0. 4. The normative reference for this requirement is TS 36.1. However. Some tests are performed also in extreme voltage conditions. The test equipment required for each category of testing may or not be different.4. the UE shall inhibit all RF transmissions when the power supply voltage is below the manufacturer declared shutdown voltage. i.2-1: Voltage Test Environment Power source AC mains Regulated lead acid battery Non regulated batteries: Leclanché Lithium Mercury/nickel & cadmium Lower extreme voltage 0. there will be requirements to test operation in multi-system configurations (e.g. there will be some generic requirements of the test equipment that are essential for all three categories of test. 4.1 Supported Cell Configuration The System Simulator shall provide the capability to simulate a minimum number of cells (of the appropriate E-UTRA Mode) whose number and capabilities are governed by the test cases that need to be performed (test cases are defined in 3GPP TS 36.1.Release 12 22 3GPP TS 36.1.1.2 Minimum number Comments 1 1 2 1 n <FFS> Depending on SS's support for RB service testing (See clause 12 of 3GPP TS 36. The type and number of channels (especially physical channels) constitute an important set of capabilities for a cell. - to set and control the uplink power levels. For this purpose test cases can be split into two different categories: Tests that require only one cell and Tests that require several cells.302 and TS 36.1. - The capability (for the specific test): - to select and support an appropriate radio bearer for the downlink.2 Minimum functional requirements 4.2. 3GPP TS 36.2.508 V12.521-1 [21] (RF) and 3GPP TS 36. the system simulator must provide a cell offering the capabilities to perform all the test cases in this category.1.321 [14]. - to set the appropriate downlink power levels.1 Logical channels Logical channel BCCH CCCH DCCH PCCH DTCH 4. The reference measurement channels (mapping between Transport channels and Physical channels for PDSCH/PDCCH) are defined in 3GPP TS 36.2.212. Similarly the mapping between Transport channels and Physical channels is as described in 3GPP TS 36. however.2. The additional cells. however. The following clauses list possible channels that may be supported by the SS.2.2. The mapping between Logical and Transport channels is as described in 3GPP TS 36.2. and the minimum number of channels needed are only mandatory if specific test cases require them.4. TS 36.211. - The capability of emulating a single E-UTRA cell with the appropriate channels to allow the UE to register on the cell.521-1[21] annex A 4.2.521-3 [34] (RRM). and to maintain the connection for the duration of the test.523-1 [?] Transport channels Transport channel BCH PCH RACH DL-SCH Minimum number 1 1 1 n <FFS> Comments 3GPP . Each channel type. additional cells must be provided by the system simulator. - The capability to allow the UE to set up an RRC connection with the system simulator. need only provide a minimum set of capabilities so as to support the first cell in carrying out the multi-cell test cases.523-1 [18](Signalling).2. - to set up and support the appropriate radio bearer for the uplink.1 (2014-12) All test equipment shall provide (for the mode(s) supported) the following minimum functionality.1 Supported Channels 4. To perform test cases requiring one cell. To perform test cases requiring several cells. 3 Physical channels Physical channel PBCH PCFICH PDCCH PDSCH PHICH PUCCH PUSCH PRACH 4.1.4 Minimum number Comments 1 Physical Broadcast Channel 1 The physical control format indicator channel carries information about the number of OFDM symbols used for transmission of PDCCHs in a subframe 1 The physical downlink control channel carries scheduling assignments and other control information.Release 12 23 UL-SCH n <FFS> 4. For non-CA Signalling testing.1. which apply to all test cases unless otherwise specified.1. if applicable NA DL NA DL NA DL NA DL Support of Tcell timing offset The timing offset in terms of frame start timing between any pair of TDD cells shall be < [3us].2. The reference test frequencies for the RF and Signalling test environment for each of the operating bands are defined in sub clause 4.2. E-UTRA frequency to be tested is mid range and E-UTRA channel bandwidth to be tested is 5MHz for all operating bands for all test cases as the default configuration unless specific channel bandwidth is specified for the operating band below: 3GPP . 4.2.1 (2014-12) Minimum number NA UL Comments NA UL TBD.3.4.2 3GPP TS 36.2.2. 1 Physical Downlink Shared Channel [1] The PHICH carries the hybrid-ARQ ACK/NAK 1 The physical uplink control channel carries uplink control information 1 Physical Uplink Shared Channel 1 Physical Random Access Channel Physical signals Physical signal Demodulation reference signal Sounding Reference signal Cell-specific Reference Signal UE-specific reference signal Primary synchronisation signal Secondary synchronisation signal 4. E-UTRA/TDD is designed to operate in unpaired bands of 3GPP TS 36. For FDD cells there is no such restriction.3 Reference test conditions This clause contains the reference test conditions.2.3.1 Test frequencies The test frequencies are based on the E-UTRA frequency bands defined in the core specifications.1.1. E-UTRA/FDD is designed to operate in paired bands of 3GPP TS 36.1.101 [27].1.3.508 V12. The raster spacing is 100 KHz.101 [27]. 4.2. The reference test frequencies for the RF and Signalling test environment for each of the operating bands are defined in sub clause 4. channel bandwidth to be tested is 20 MHz as the default configuration. In the case 5MHz bandwidth is not supported by the UE. Actual test configurations are specified case by case and stated in test case itself as the initial conditions.1-1. E-UTRA channel bandwidths to be tested are lowest bandwidth. 5MHz bandwidth and highest bandwidth are selected from the combined table which includes nominal and additional channel bandwidth. E-UTRA frequencies to be tested are low range. mid range and high range for all supported operating bands by default. For RF testing.3. This channel bandwidth combination is used for Inter-band contiguous CA configuration CA_1A-21A. 18 and 20. For Band 38.4.508 V12. This channel bandwidth combination is used for all Intra-band contiguous CA configurations using Bandwidth Class B unless specific channel bandwidth combination is specified for a CA configuration or CA Bandwidth Combination Set by specific entries in this table below.BW Combination Set) Intra-band contiguous and Bandwidth Class C Intra-band contiguous and Bandwidth Class B CA Channel Bandwidth combination carrier 1 + carrier 2 [MHz + MHz] 20+20 5+5 Inter-band CA and CA Bandwidth Class Combination A-A 10 + 10 CA_1A-19A 15 + 10 CA_1A-21A 15 + 15 CA_3A-19A 20 + 10 CA_19A-21A 10 + 15 CA_39A-41A 20+20 Comment This channel bandwidth combination is used for all Intra-band contiguous CA configurations using Bandwidth Class C unless specific channel bandwidth combination is specified for a CA configuration or CA Bandwidth Combination Set by specific entries in this table below. This channel bandwidth combination is used for all Inter-band contiguous CA configurations using Bandwidth Class Combination A-A unless specific channel bandwidth combination is specified for a CA configuration or CA Bandwidth Combination Set by specific entries in this table below. This channel bandwidth combination is used for Inter-band contiguous CA configuration CA_1A-19A.3. 13.2. This channel bandwidth combination is used for Inter-band contiguous CA configuration CA_19A-21A. 40 and 41. Table 4. 5MHz bandwidth and highest bandwidth for all supported operating bands by default. This channel bandwidth combination is used for Inter-band contiguous CA configuration CA_3A-19A. For CA Signalling testing with two component carriers.1-1: Default E-UTRA channel bandwidth combinations for CA Signalling testing with two component carriers CA configuration (Band(s).1 (2014-12) For Band 11.BW Class. This channel bandwidth combination is used for Inter-band CA configuration CA_39A-41A. E-UTRA channel bandwidth to be tested is only lowest bandwidth and highest bandwidth. E-UTRA frequencies to be tested are according to sub clause 6. The lowest bandwidth. 39.2 and the E-UTRA channel bandwidth combination is according to Table 4. 3GPP . channel bandwidth to be tested is 10 MHz as the default configuration.3.Release 12 24 3GPP TS 36. 5 1970 399 525 500 2149.1.9 1972.1A-1: Test frequencies for CA_1C Range Low Mid High Note 1: CCCombo / NRB_agg [RB] BW [RB] NUL CC1 Note1 fUL [MHz] 75+75 100+100 75+75 75 100 75 18075 18100 18225 1927. Additional test frequencies not following this rule.1. for Bands 2.8 2147.5 1925 1927.1A NUL Frequency of Uplink [MHz] 1922.1.1. 19. then the same channel bandwidth is not required to be tested twice.5 1970 18025 18050 18075 18100 18300 18575 18550 18525 18500 NDL 25 50 75 100 300 575 550 525 500 Frequency of Downlink [MHz] 2112. the E-UTRA frequency and channel bandwidth to be tested follow the same rules as for Signalling testing above. changing the existing test points to address this is being discussed in RAN5 and will be considered pending technical justification. 18. 20 and 25.Release 12 25 3GPP TS 36.2 100 75 100 18399 18525 18500 1959.521-1[21].1 2147.5 2120 2132.5 1949.5 75 100 225 2117.2 201 375 302 2130.4.1.571-1. For A-GNSS testing in TS 37. are (should be) identified by notes.5 2160 FDD reference test frequencies for CA in operating band 1 Table 4. 18.5 2139.9 2162.1. 4.5 1930 1950 1977.3. an industry requirement of testing in 10MHz channel bandwidth is requested for Bands 2.5 75 100 75 18225 18298 18375 1942.5 1950.1 (2014-12) If channel bandwidth to be tested is equal to the lowest or highest channel bandwidth. In addition to the default channel bandwidths to be tested specified above.5 2120 2140 2167.1. an industry requirement of testing in 10MHz channel bandwidth is allowed for test cases in chapters 6 and 7 in TS 36.5 2160 NDL fDL [MHz] BW [RB] Carriers in increasing frequency order.521-1 [21]. 4.1 FDD reference test frequencies for operating band 1 Table 4.508 V12.8 1957. while CC2 the High Range frequency. 19.3.5 1930 1942. For intra-band non-contiguous CA (CA_XA-XA) test frequencies have been defined following the basic assumption that CC1 uses the Low Range frequency of the band.3.5 2140. 4.1-1: Test frequencies for E-UTRA channel bandwidth for operating band 1 Test Frequency ID Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 Low Range Mid Range High Range 4.5 225 298 375 2132.1.1 FDD Mode Test frequencies 4.1 1957. 20 and 25 for test cases in chapters 6 and 7 in TS 36.5 2165 2162.5 100+100 75+75 100+100 100 75 100 18201 18375 18302 1940.3.1.5 2115 2117. 3GPP NUL CC2 Note1 fUL [MHz] NDL fDL [MHz] . Editor’s note: For RF testing.3.5 1975 1972. 4.5 1185 1988.5 675 20 [1] 18700 1860 700 Mid Range 1.5 625 Low Range 10 18650 1855 650 15 [1] 18675 1857.2A-1: Test frequencies for CA_2A-2A Range N/A Note 1: CCCombo / NRB_agg [RB] BW [RB] 25 25 50 50 25 50 75 100 NUL 18625 18625 18650 18650 18625 18650 18675 18700 CC1 Note1 fUL [MHz] 1852.5 1940 3GPP 50 45 40 35 35 30 25 20 BW [RB] 25 50 50 75 100 100 100 100 NUL 19175 19150 19150 19125 19100 19100 19100 19100 CC2 Note1 fUL [MHz] 1907.3 3 19185 1908.2-1: Test frequencies for E-UTRA channel bandwidth for operating band 2 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 1930.5 5 19175 1907.5 1935 1937.1.5 1125 1982.3.1.5 1175 1987.3.7 1931.1. 4. Wgap [MHz] NDL 625 625 650 650 625 650 675 700 fDL [MHz] 1932.3.5 1932.Release 12 4.5 1940 1.5 1905 1905 1902.1 (2014-12) FDD reference test frequencies for operating band 2 Table 4.4/3/5/10 18900 1880 900 1960 15 [1]/20 [1] 1.4 18607 1850.1.1.5 1985 1985 1982.5 615 5 18625 1852.2 26 3GPP TS 36.4 19193 1909.508 V12.5 1855 1857.3.2A FDD reference test frequencies for CA in operating band 2 Table 4.5 1935 1935 1932.5 1935 1937.101 [27] Clause 7.5 1900 1900 1900 1900 NDL 1175 1150 1150 1125 1100 1100 1100 1100 fDL [MHz] 1987.5 1855 1855 1852.5 1852.5 1980 1980 1980 1980 .1.5 1860 25+25 25+50 50+50 50+75 25+100 50+100 75+100 100+10 0 Carriers in increasing frequency order.3) is allowed.5 20 [1] 19100 1900 1100 1980 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 High Range 10 19150 1905 1150 1985 15 [1] 19125 1902.1.3 1193 1989.7 607 3 18615 1851.1.5 1932. 1 1742.8 1740.5 High Range 10 19900 1780 1900 1875 15 [1] 19875 1777.1 (2014-12) FDD reference test frequencies for operating band 3 Table 4.7 1729.0 1754.1.5 1775 1777.3 1943 1879.5 1935 1878. 4.3.4 1829.1 1837.6 1832.1 1737.3 1770 1760.7 1775 1779.8 1815 1815 1833.1 1852.5 1875 1872.1.3 1815 1810.3 1745 1738.8 1750.6 1737.3A-1: Test frequencies for CA_3C Range Low CC-Combo / NRB_agg [RB] 25+100 50+100 75+100 Mid 100+100 25+100 50+100 75+100 High 100+100 25+100 50+100 75+100 100+100 Note 1: BW [RB] NUL CC1 Note1 fUL [MHz] 25 100 50 100 75 100 100 25 100 50 100 75 100 100 25 100 50 100 75 100 100 19233 19300 19255 19300 19278 19300 19300 19483 19550 19481 19526 19478 19501 19476 19733 19800 19706 19751 19679 19701 19652 1713.2 1852.2 1870 .4 19207 1710.9 1757.2 1757.4 1870 1876.9 1832.Release 12 27 4.5 Low Range 10 19250 1715 1250 1810 15 [1] 19275 1717.3 1720 1715.4 1734.5 1925 1877.1 1739.9 1852.1.4/3/5/10 19575 1747.7 1847.5 1852.4 19943 1784.9 1829.2 100 25 100 50 100 75 100 100 25 100 50 100 75 100 100 25 100 50 100 75 100 Carriers in increasing frequency order.1 1755.9 1855.6 1763.1.3) is allowed.5 1870 1872.1.2 NDL fDL [MHz] BW [RB] 1233 1300 1255 1300 1278 1300 1300 1483 1550 1481 1526 1478 1501 1476 1733 1800 1706 1751 1679 1701 1652 1808.1 1850.1.7 1752.4.4 1775 1781.3 3GPP TS 36.6 1858.5 1215 1806.0 1851.0 1849.5 5 19225 1712.6 1860.5 20 [1] 19850 1775 1850 1870 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.1 1832.7 1870 1874.5 15 [1]/20 [1] 1.5 1720 1717.7 1824.9 1737.1 1757.508 V12.3.3-1: Test frequencies for E-UTRA channel bandwidth for operating band 3 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 1.3 1840 1833.5 1575 1842.1.3A FDD reference test frequencies for CA in operating band 3 Table 4.5 5 19925 1782.101 [27] Clause 7.3 3 19935 1783.3.5 1757.5 1815 1812.2 1775 1350 1417 1399 1444 1449 1471 1498 1600 1667 1625 1670 1649 1672 1674 1850 1917 1850 1895 1850 1872 1850 1820 1826.0 1756. 3GPP NUL CC2 Note1 fUL [MHz] NDL fDL [MHz] 19350 19417 19399 19444 19449 19471 19498 19600 19667 19625 19670 19649 19672 19674 19850 19917 19850 19895 19850 19872 19850 1725 1731.1.5 20 [1] 19300 1720 1300 1815 Mid Range 1.5 1275 1812.7 1207 1805.6 1765.9 1734.3 1865 1855.9 1760.7 3 19215 1711.8 1720 1720 1738.1 1834.5 1225 1807.3.8 1835.8 1845. 1.4.4 3 5 10 15 20 19957 19965 19975 20000 20025 20050 20175 20393 20385 20375 20350 20325 20300 1710.7 2111.5 1752.5 2120 2132.5 2152.Release 12 28 3GPP TS 36.4 3 5 10 15 20 1.5 2154.5 1275 1812.5 1775 1775 100 100 100 19850 19850 19850 1775 1775 1775 NDL 1925 1900 1900 1875 1850 1850 fDL [MHz] 1877.5 1712.3A-2: Test frequencies for CA_3A-3A Range N/A Note 1: Note 2: CCCombo / NRB_agg [RB] 25+25 25+50 50+50 50+75 25+100 BW [RB] 25 25 50 50 25 25 NUL 19225 19225 19250 19250 19225 19575 CC1 Note1 fUL [MHz] 1712.1.5 1754.3 2153. 4.4 65 60 55 50 50 15 (Note 2) 45 40 35 BW [RB] 25 50 50 75 100 100 NUL 19925 19900 19900 19875 19850 19850 CC2 Note1 fUL [MHz] 1782.1 (2014-12) Table 4.1.5 2150 2147.5 75+100 100+10 100 19300 1720 1300 1815 0 Carriers in increasing frequency order.5 2145 .3.5 2115 2117.5 Wgap [MHz] fDL [MHz] 1807.3.4/3/5/10/15/20 1.5 1870 1870 1850 1850 1850 1870 1870 1870 FDD reference test frequencies for operating band 4 Table 4.3.5 1715 1715 1712.1.5 1810 1810 1807.5 1875 1875 1872.7 1711. Test point derived with regard to REFSENS requirements.5 1745 1957 1965 1975 2000 2025 2050 2175 2393 2385 2375 2350 2325 2300 3GPP Frequency of Downlink [MHz] 2110.5 1712.5 1747.4-1: Test frequencies for E-UTRA channel bandwidth for operating band 4 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL 1.1.5 2112.5 1715 1717.3 1753.5 1842.5 1807.5 1720 1732.5 NDL 1225 1225 1250 1250 1225 1575 50 19250 1715 1250 1810 50+100 75 19275 1717.5 1780 1780 1777.5 1750 1747.1.508 V12. 3.1.5 2725 882.5 10 [1] 20700 835 2700 880 5 Mid Range 20700 835 2700 880 10 [1] High Range 5 20725 837.101 [27] Clause 7.1.5 10 [1] 1. 3GPP fDL [MHz] 2152.6 FDD reference test frequencies for operating band 6 Table 4.5-1: Test frequencies for E-UTRA channel bandwidth for operating band 5 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 869. the Mobile Country Code shall be set to (MCC = '442/443').1.3.1. NOTE: For Band VI testing.5 871.5 2115 2117.5 2635 892.1. 4.4A 3GPP TS 36.3.3.1 (2014-12) FDD reference test frequencies for CA in operating band 4 Table 4.3) is allowed.5 2150 2150 2147.101 [27] Clause 7.1.1.5 10 [1] 20700 835 2700 880 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 2415 Low Range 5 20425 826.5 75+100 100 20050 1720 100+100 Carriers in increasing frequency order.5 10 [1] 20600 844 2600 889 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.Release 12 29 4.1.508 V12.5 2112.5 1750 1750 1747.5 2425 10 [1] 20450 829 2450 1.1.5 High Range 5 20625 846.5 2675 877.1.3 3 20635 847.4 20643 848.5 25+100 25 50 20000 1715 50+100 75 20025 1717.4A-1: Test frequencies for CA_4A-4A Range N/A Note 1: CCCombo / NRB_agg [RB] CC1 Note1 BW fUL [RB] NUL [MHz] 25 19975 1712.1.4/3/5 Mid Range 20525 836.7 870.5 Wgap [MHz] fDL [MHz] 2112.1.6-1: Test frequencies for E-UTRA channel bandwidth for operating band 6 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Low Range Frequency of Downlink [MHz] 5 20675 832.5 25+25 25 19975 1712.7 2407 3 20415 825.4.5 2525 881.5 2115 2115 2112.3) is allowed.3 2643 893.4 20407 824.5 2145 2145 2145 2145 .5 874 1.5 25+50 50 20000 1715 50+50 50 20000 1715 50+75 19975 1712.5 2625 891.3. 4.5 1745 1745 1745 1745 NDL 2375 2350 2350 2325 2300 2300 2300 2300 FDD reference test frequencies for operating band 5 Table 4.5 2120 NDL 1975 1975 2000 2000 1975 2000 2025 2050 35 30 25 20 20 15 10 5 BW [RB] 25 50 50 75 100 100 100 100 NUL 20375 20350 20350 20325 20300 20300 20300 20300 CC2 Note1 fUL [MHz] 1752.3. 4.3.5 100+100 75+75 100+100 100 75 100 21001 21225 21152 2525.1.5 2649.Release 12 30 4.7A-2: Test frequencies for CA_7A-7A Range N/A CCCombo / NRB_agg [RB] 50+50 50+75 75+100 100+10 0 Note 1: Note 2: BW [RB] 50 50 75 75 NUL 20800 20800 20825 21025 CC1 Note1 fUL [MHz] 2505 2505 2507.101 [27] Clause 7.5 3375 2682.3.5 Carriers in increasing frequency order.1 (2014-12) FDD reference test frequencies for operating band 7 Table 4. 3GPP 50 45 35 15 (Note 2) 30 15 (Note 2) BW [RB] 50 75 100 100 NUL 21400 21375 21350 21350 CC2 Note1 fUL [MHz] 2565 2562.5 2560 3199 3375 3350 2664.1A-1: Test frequencies for CA_7C Range Low Mid High Note 1: CC-Combo / NRB_agg [RB] BW [RB] NUL CC1 Note1 fUL [MHz] 75+75 100+100 75+75 75 100 75 20825 20850 21025 2507.1.1.5 2660.9 2682.8 2662.2 100 75 100 21199 21375 21350 2544.5 2527.7-1: Test frequencies for E-UTRA channel bandwidth for operating band 7 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 2622.1.5 2529.1.5 3425 2687.1.8 2542. Test point derived with regard to REFSENS requirements.1 2667.1 2547.5 2680 2680 .2 3001 3225 3152 2645.5 2825 20 [1] 20850 2510 2850 5/10/15 Mid Range 21100 2535 3100 2655 20 [1] 5 21425 2567.5 2630 2647.1.5 2630 5 20775 2502.7 3GPP TS 36.3.5 2775 10 20800 2505 2800 Low Range 15 20825 2507.5 2825 2850 3025 2627.5 2625 2627.3) is allowed.508 V12.1.9 2562.5 75 100 75 20975 21048 21175 2522.5 2510 2527.5 2680 NDL fDL [MHz] BW [RB] NUL CC2 Note1 fUL [MHz] NDL fDL [MHz] Carriers in increasing frequency order.5 20 [1] 21350 2560 3350 2680 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.4.3.3.5 2975 3048 3175 2642.5 2647. Table 4.1.7A FDD reference test frequencies for CA in operating band 7 Table 4.5 10 21400 2565 3400 2685 High Range 15 21375 2562.5 Wgap [MHz] 100 20850 2510 2850 2630 100 21000 2525 3000 2645 NDL 2800 2800 2825 3025 fDL [MHz] 2625 2625 2627.5 2540.1.5 2560 2560 100 21350 2560 3350 2680 100 21350 2560 3350 2680 NDL 3400 3375 3350 3350 fDL [MHz] 2685 2682. 9 4100 1874.3) is allowed.4 4125 1877.3.4.1.9 Low Range 15 [1] 21875 1757. 4.Release 12 4.5 1715 1717.9 3850 1849.5 927.1.5 1720 1740 1767.3.5 2115 2117.1.9 5/10 Mid Range 21975 1767.4 10 22100 1779.9 4050 1869.5 High Range 5 21775 912.9 FDD reference test frequencies for operating band 9 Table 4.4 20 [1] 21900 1759.1.1.7 3457 3 21465 881.4 4075 1872.3) is allowed.5 3475 10 [1] 21500 885 3500 1.1.5 2165 2162.4 21457 880.3 3 21785 913.9 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.3.4 21793 914.10-1: Test frequencies for E-UTRA channel bandwidth for operating band 10 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 NUL Frequency of Uplink [MHz] 1712.9 3900 1854.3.3 3793 959.5 930 1.4 3825 1847.10 FDD reference test frequencies for operating band 10 Table 4.4 15 [1]/20 [1] 5 22125 1782.5 2120 2140 2167.5 10 [1] 21750 910 3750 955 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.7 926.1.5 3465 Low Range 5 21475 882.3.5 3625 942.4 10 21850 1754.9-1: Test frequencies for E-UTRA channel bandwidth for operating band 9 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 21825 1752.101 [27] Clause 7.5 3775 957.508 V12.1.1.8 31 3GPP TS 36.4 3875 1852.1 (2014-12) FDD reference test frequencies for operating band 8 Table 4.101 [27] Clause 7.5 1760 22175 22200 22225 22250 22450 22725 22700 22675 22650 3GPP NDL 4175 4200 4225 4250 4450 4725 4700 4675 4650 Frequency of Downlink [MHz] 2112.5 1765 1762.1.4/3/5 Mid Range 21625 897. 4.1.5 2160 .5 10 [1] 1.5 3785 958.9 High Range 15 [1] 22075 1777.1.4 3975 1862.8-1: Test frequencies for E-UTRA channel bandwidth for operating band 8 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 925.4 20 [1] 22050 1774.3. 5 High Range 10 [1] 23230 782 5230 751 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 5035 731.Release 12 4.4 10 [1] 22800 1432.5 5095 737.5 5355 765.9 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.3) is allowed.1.4.3.4 23173 715.1.1.1.3) is allowed.1. 3GPP .1 (2014-12) FDD reference test frequencies for operating band 11 Table 4.5 10 [1] 23130 711 5130 741 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.3.3 3 23165 714.1.101 [27] Clause 7.1.11-1: Test frequencies for E-UTRA channel bandwidth for operating band 11 Test Frequency ID Low Range Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 22775 1430.3.3 5173 745.3. 4.1.1.101 [27] Clause 7.4 4775 1478.4 23017 699.5 5155 743.3) is allowed.14-1: Test frequencies for E-UTRA channel bandwidth for operating band 14 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 [1] 23305 790.14 FDD reference test frequencies for operating band 14 Table 4.4/3 23095 707.4 4925 1493.5 High Range 5 [1] 23155 713.5 5205 748.11 32 3GPP TS 36.3.1.508 V12.1.1.9 4800 1480.7 3 23025 700.3.5 10 [1] 23060 704 5060 734 Mid Range 1.13-1: Test frequencies for E-UTRA channel bandwidth for operating band 13 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 [1] 23205 779.101 [27] Clause 7.5 5165 744.1.5 High Range 10 [1] 23330 793 5330 763 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.7 5017 729.5 5305 760.1.9 Mid Range 5 / 10 [1] 22850 1437.1.5 5 [1]/10 [1] 1.5 Low Range 10 [1] 23230 782 5230 751 Mid Range 5 [1]/10 [1] 23230 782 5230 751 5 [1] 23255 784.4 10 [1] 22900 1442.5 Low Range 5 [1] 23035 701.12-1: Test frequencies for E-UTRA channel bandwidth for operating band 12 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 1.3.3) is allowed.9 High Range 5 22925 1445.13 FDD reference test frequencies for operating band 13 Table 4.12 FDD reference test frequencies for operating band 12 Table 4. 4.9 4850 1485.1.5 5255 753.9 4900 1490.3.5 5025 730.5 Low Range 10 [1] 23330 793 5330 763 Mid Range 5 [1]/10 [1] 23330 793 5330 763 5 [1] 23355 795. 4.101 [27] Clause 7. 1.1 (2014-12) FDD reference test frequencies for operating band 15 [FFS.5 5925 867.19 FDD reference test frequencies for operating band 19 Table 4.5 5875 862.1.5 High Range 10 [1] 23800 711 5800 741 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.101 [27] Clause 7.101] 4.1.1.5 5 23975 827.3.1.5 High range 10 [1] 24100 840 6100 885 15 [1] 24075 837.5 5 24125 842.5 Low Range 10 [1] 24050 835 6050 880 15 [1] 24075 837. not yet specified in TS 36.1.18-1: Test frequencies for E-UTRA channel bandwidth for operating band 18 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 23875 817.1.5 High range 10 [1] 23950 825 5950 870 15 [1] 23925 822.5 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 5975 872.17-1: Test frequencies for E-UTRA channel bandwidth for operating band 17 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 [1] 23755 706.1.4.5 Mid Range 5/10 [1]/15 [1] 24075 837.3.3.3.1.5 6075 882.Release 12 4. 3GPP .5 6075 882.101 [27] Clause 7.5 5925 867.3) is allowed.3) is allowed.5 6075 882.18 FDD reference test frequencies for operating band 18 Table 4.5 Mid Range 5/10 [1]/15 [1] 23925 822.1.508 V12.3.1.16 FDD reference test frequencies for operating band 16 [FFS.17 FDD reference test frequencies for operating band 17 Table 4.19-1: Test frequencies for E-UTRA channel bandwidth for operating band 19 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 24025 832.1.5 6125 887.5 5925 867. not yet specified in TS 36.3.1.101] 4.15 33 3GPP TS 36.1.1.5 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.1.5 Low Range 10 [1] 23900 820 5900 865 15 [1] 23925 822.3) is allowed.3.5 5755 736. 4.5 6025 877.5 5825 743.5 Low Range 10 [1] 23780 709 5780 739 Mid Range 5 [1]/10 [1] 23790 710 5790 740 5 [1] 23825 713.101 [27] Clause 7.3. 4. 3) is allowed.23 Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 NUL 24625 24650 24675 24700 25000 25375 25350 25325 25300 Frequency of Uplink [MHz] 3412.1. 4. 4.5 3520 3550 3587.1.9 6550 1505.22-1: Test frequencies for E-UTRA channel bandwidth for operating band 22 Test Frequency ID Low Range Mid Range High Range 4.3.1.4 Mid Range 5/10 [1]/15 [1] 24525 1455.7 2181.5 6425 818.21-1: Test frequencies for E-UTRA channel bandwidth for operating band 21 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 24475 1450.4 6525 1503.4 6525 1503.21 FDD reference test frequencies for operating band 21 Table 4.4 Low Range 10 [1] 24500 1452.1.3.3.Release 12 34 4.5 .20 3GPP TS 36.4 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 6225 798.5 3415 3417.101 [27] Clause 7.5 10[1] 24400 857 6400 816 High range 15[1] 24375 854.1.3.3.4 6575 1508.5 6175 793.9 15 [1] 24525 1455.5 2182.9 6500 1500.1.4 3 5 25507 25515 25525 2000.3) is allowed.7 2001.4 High range 10 [1] 24550 1457.1.23-1: Test frequencies for E-UTRA channel bandwidth for operating band 23 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Low Range 1.1.1.5 2002.5 7507 7515 7525 3GPP Frequency of Downlink [MHz] 2180.3.5 3485 3482.5 20[1] 24250 842 6250 801 Mid Range 5/10[1]/15[1]/20[1] 24300 847 6300 806 5 24425 859.5 3515 3517.1.1.3.4.5 3580 FDD reference test frequencies for operating band 23 Table 4.4 6475 1498.5 3480 NDL 6625 6650 6675 6700 7000 7375 7350 7325 7300 Frequency of Downlink [MHz] 3512.508 V12.4 5 24575 1460.5 6375 813.3.5 10[1] 24200 837 6200 796 Low Range 15[1] 24225 839.9 15 [1] 24525 1455.4 6525 1503.101 [27] Clause 7.5 20[1] 24350 852 6350 811 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.1.19-1: Test frequencies for E-UTRA channel bandwidth for operating band 20 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 5 24175 834.5 3585 3582.1.1.1.5 3420 3450 3487.22 FDD reference test frequencies for operating band 22 Table 4.1.1 (2014-12) FDD reference test frequencies for operating band 20 Table 4. 5 7525 25+50 25 Carriers in increasing frequency order.3. 4.5 5 BW [RB] 50 NUL 25650 CC2 Note1 fUL [MHz] 2015 NDL 7650 FDD reference test frequencies for operating band 24 Table 4.5 1658 1655.3.3 2018.5 2190 25600 2010 7600 2190 25693 25685 25675 25650 25625 25600 2019.25-1: Test frequencies for E-UTRA channel bandwidth for operating band 25 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL 1.1.1 (2014-12) 25550 25575 25600 2005 2007.1.4/3/5/10 15 [1]/20 [1] 1.5 2190 FDD reference test frequencies for CA in operating band 23 Table 4.5 2015 2012.4 3 5 10 15 20 Mid Range High Range 4.1.1.3 1913.4 3 5 10 15 [1] 20 [1] 26047 26055 26065 26090 26115 26140 1850.5 26683 26675 26665 26640 26615 26590 1914.5 1990 1987.4/3 5 /10 / 15 / 20 1.25 Bandwidth [MHz] 5 10 5/10 5 10 NUL Frequency of Uplink [MHz] 1629 1631.3 2198.7 1851.1.5 2197.7 1931.5 1554 FDD reference test frequencies for operating band 25 Table 4.3.3.5 1912.23A-1: Test frequencies for CA_23A-23A Range N/A Note 1: CCCombo / NRB_agg [RB] CC1 Note1 BW fUL [RB] NUL [MHz] NDL 25525 2002.1.1.Release 12 35 10 15 20 1.5 2010 7693 7685 7675 7650 7625 7600 2199.5 25725 25750 25870 26015 25990 NDL 7725 7750 7870 8015 7990 Frequency of Downlink [MHz] 1527.1.1.24 Wgap [MHz] fDL [MHz] 2182.4 3 5 10 15 [1] 20 [1] 1.3.5 1860 8047 8055 8065 8090 8115 8140 Frequency of Downlink [MHz] 1930.5 1992.5 1643.5 1905 8683 8675 8665 8640 8615 8590 1994.1.1.5 1855 1857.5 1530 1542 1556.5 1852.23A 3GPP TS 36.3.5 8365 1962.5 1910 1907.5 2017.5 1935 1937.5 1985 3GPP fDL [MHz] 2195 .5 2010 7550 7575 7600 2185 2187.4.5 1940 26365 1882.1.24-1: Test frequencies for E-UTRA channel bandwidth for operating band 24 Test Frequency ID Low Range Mid Range High Range 4.5 1932.508 V12.3 1993.5 2195 2192. Release 12 36 3GPP TS 36. 3GPP .26-1: Test frequencies for E-UTRA channel bandwidth for operating band 26 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 859.1.5 1932.5 865 867.3 9033 893.3.5 8090 8440 1935 1970 55 50 15 (Note 2) 45 10 (Note 2) BW [RB] 25 50 50 NUL 26665 26640 26640 CC2 Note1 fUL [MHz] 1912.508 V12.5 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.4 26697 814.101 [27] Clause 7.1.5 1.1 (2014-12) NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36. 4.3.1.3.26 FDD reference test frequencies for operating band 26 Table 4.5 8775 Mid Range 1.5 1852.5 10[1] 26990 844 8990 889 15 [1] 26965 841.1.5 1887.25A FDD reference test frequencies for CA in operating band 25 Table 4.101 [27] Clause 7. Test point derived with regard to REFSENS requirements.1.1.5 1990 1990 8640 8640 1990 1990 Carriers in increasing frequency order. 4.5 1967.4/3/5/10[1] 26865 831.5 1910 1910 50 50 26640 26640 1910 1910 NDL 8665 8640 8640 fDL [MHz] 1992.7 860.1.25A-1: Test frequencies for CA_25A-25A Range N/A CCCombo / NRB_agg [RB] 25+25 25+50 50+50 Note 1: Note 2: BW [RB] 25 25 25 NUL 26065 26065 26415 CC1 Note1 fUL [MHz] 1852.5 8705 Low Range 5 26715 816.4.1.5 15 [1] 1.5 9015 891.4 27033 848.5 861.3 3 27025 847.5 8715 10[1] 26750 820 8750 15 [1] 26775 822.7 8697 3 26705 815.5 8965 886.5 9025 892.3) is allowed.3.3) is allowed.5 High Range 5 27015 846.5 50 50 26090 26440 1855 1890 Wgap [MHz] NDL 8065 8065 8415 fDL [MHz] 1932.5 8865 876. Release 12 4.3.1.1.27 37 3GPP TS 36.508 V12.4.1 (2014-12) FDD reference test frequencies for operating band 27 Table 4.3.1.1.27-1: Test frequencies for E-UTRA channel bandwidth for operating band 27 Test Frequency ID Frequency of Downlink [MHz] 1.4 27047 807.7 9047 852.7 3 27055 808.5 9055 853.5 Low Range 5 27065 809.5 9065 854.5 10 [1] 27090 812 9090 857 Mid Range 1.4/3/5/10 [1] 27125 815.5 9125 860.5 1.4 27203 823.3 9203 868.3 3 27195 822.5 9195 867.5 High Range 5 27185 821.5 9185 866.5 10 [1] 27160 819 9160 864 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.101 [27] Clause 7.3) is allowed. 4.3.1.1.27A Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL FDD reference test frequencies for CA in operating band 27 Table 4.3.1.1.27A-1: Test frequencies for CA_27B Range Low Mid High Note 1: CC-Combo / NRB_agg [RB] CC1 Note1 BW NUL fUL [RB] [MHz] 6 27048 807.8 6+25 15 27056 808.6 15+25 25 27065 809.5 25+25 6 27051 808.1 6+50 15 27059 808.9 15+50 6 27101 813.1 6+25 15 27101 813.1 15+25 25 27101 813.1 25+25 6 27080 811.0 6+50 15 27079 810.9 15+50 6 27155 818.5 6+25 15 27146 817.6 15+25 25 27137 816.7 25+25 6 27109 813.9 6+50 15 27100 813.0 15+50 Carriers in increasing frequency order. NDL 9048 9056 9065 9051 9059 9101 9101 9101 9080 9079 9155 9146 9137 9109 9100 3GPP fDL [MHz] 852.8 853.6 854.5 853.1 853.9 858.1 858.1 858.1 856.0 855.9 863.5 862.6 861.7 858.9 858.0 BW [RB] 25 25 25 50 50 25 25 25 50 50 25 25 25 50 50 NUL 27078 27095 27113 27102 27119 27131 27140 27149 27131 27139 27185 27185 27185 27160 27160 CC2 Note 1 fUL [MHz] 810.8 812.5 814.3 813.2 814.9 816.1 817.0 817.9 816.1 816.9 821.5 821.5 821.5 819.0 819.0 NDL 9078 9095 9113 9102 9119 9131 9140 9149 9131 9139 9185 9185 9185 9160 9160 fDL [MHz] 855.8 857.5 859.3 858.2 859.9 861.1 862.0 862.9 861.1 861.9 866.5 866.5 866.5 864.0 864.0 Release 12 38 4.3.1.1.28 3GPP TS 36.508 V12.4.1 (2014-12) FDD reference test frequencies for operating band 28 Table 4.3.1.1.28-1: Test frequencies for E-UTRA channel bandwidth for operating band 28 Test Frequency ID Frequency of Downlink [MHz] 3 27225 704.5 9225 759.5 5 27235 705.5 9235 760.5 Low Range 10[1] 27260 708 9260 763 15[1] 27285 710.5 9285 765.5 20[1] 27310 713 9310 768 3 27375 719.5 9375 774.5 5 27385 720.5 9385 775.5 Mid Range 10[1] 27410 723 9410 778 15[1] 27435 725.5 9435 780.5 20[1,2] 27460 728 9460 783 3 27645 746.5 9645 801.5 5 27635 745.5 9635 800.5 High Range 10[1] 27610 743 9610 798 15[1] 27585 740.5 9585 795.5 20[1] 27560 738 9560 793 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.101 [27] Clause 7.3) is allowed. NOTE 2: Mid Range for 20 MHz moved due to note 2 in Table 5.6.1-1 of TS 36.101 [27]. 4.3.1.1.29 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL FDD reference test frequencies for CA in operating band 29 Table 4.3.1.1.29-1: Test frequencies for E-UTRA channel bandwidth for operating band 29 Test Frequency ID Low Range Bandwidth [MHz] 3 5 10 NUL NA[1] NA[1] NA[1] Frequency of Uplink [MHz] NA NA NA NDL 9675 9685 9710 Frequency of Downlink [MHz] 718.5 719.5 722 3 NA[1] NA 9715 722.5 5 /10 3 NA[1] NA 9755 726.5 High Range 5 NA[1] NA 9745 725.5 10 NA[1] NA 9720 723 NOTE 1: Restricted to E-UTRA operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell. Mid Range 4.3.1.1.30 FDD reference test frequencies for operating band 30 Table 4.3.1.1.30-1: Test frequencies for E-UTRA channel bandwidth for operating band 30 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 5/10 5 10 NUL 27685 27710 27710 27735 27710 Frequency of Uplink [MHz] 2307.5 2310 2310 2312.5 2310 3GPP NDL 9795 9820 9820 9845 9820 Frequency of Downlink [MHz] 2352.5 2355 2355 2357.5 2355 Release 12 4.3.1.1.31 39 3GPP TS 36.508 V12.4.1 (2014-12) FDD reference test frequencies for operating band 31 Table 4.3.1.1.31-1: Test frequencies for E-UTRA channel bandwidth for operating band 31 Test Frequency ID Frequency of Downlink [MHz] 1.4 27767 453.2 9877 463.2 Low Range 3[1] 27775 454 9885 464 5[1] 27785 455 9895 465 Mid Range 1.4/3[1]/ 5[1] 27785 455 9895 465 1.4 27803 456.8 9913 466.8 High Range 3[1] 27795 456 9905 466 5[1] 27785 455 9895 465 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.101 [27] Clause 7.3) is allowed. 4.3.1.2 4.3.1.2.1 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL TDD Mode Test frequencies TDD reference test frequencies for Operating Band 33 Table 4.3.1.2.1-1: Test frequencies for E-UTRA channel bandwidth for operating band 33 Test Frequency ID Low Range Mid Range High Range 4.3.1.2.2 Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 36025 36050 36075 36100 36100 36175 36150 36125 36100 Frequency (UL and DL) [MHz] 1902.5 1905 1907.5 1910 1910 1917.5 1915 1912.5 1910 TDD reference test frequencies for Operating Band 34 Table 4.3.1.2.2-1: Test frequencies for E-UTRA channel bandwidth for operating band 34 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 15 5/10/15 5 10 15 EARFCN 3GPP 36225 36250 36275 36275 36325 36300 36275 Frequency (UL and DL) [MHz] 2012.5 2015 2017.5 2017.5 2022.5 2020 2017.5 Release 12 4.3.1.2.3 40 3GPP TS 36.508 V12.4.1 (2014-12) TDD reference test frequencies for Operating Band 35 Table 4.3.1.2.3-1: Test frequencies for E-UTRA channel bandwidth for operating band 35 Test Frequency ID Low Range Mid Range High Range 4.3.1.2.4 Bandwidth [MHz] 1.4 3 5 10 15 20 1.4/3/5/10/15/20 1.4 3 5 10 15 20 EARFCN [MHz] 36357 36365 36375 36400 36425 36450 36650 36943 36935 36925 36900 36875 36850 Frequency (UL and DL) [MHz] 1850.7 1851.5 1852.5 1855 1857.5 1860 1880 1909.3 1908.5 1907.5 1905 1902.5 1900 TDD reference test frequencies for Operating Band 36 Table 4.3.1.2.4-1: Test frequencies for E-UTRA channel bandwidth for operating band 36 Test Frequency ID Low Range Mid Range High Range 4.3.1.2.5 Bandwidth [MHz] 1.4 3 5 10 15 20 1.4/3/5/10/15/20 1.4 3 5 10 15 20 EARFCN [MHz] 36957 36965 36975 37000 37025 37050 37250 37543 37535 37525 37500 37475 37450 Frequency (UL and DL) [MHz] 1930.7 1931.5 1932.5 1935 1937.5 1940 1960 1989.3 1988.5 1987.5 1985 1982.5 1980 TDD reference test frequencies for Operating Band 37 Table 4.3.1.2.5-1: Test frequencies for E-UTRA channel bandwidth for operating band 37 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN [MHz] 37575 37600 37625 37650 37650 37725 37700 37675 37650 3GPP Frequency (UL and DL) [MHz] 1912.5 1915 1917.5 1920 1920 1927.5 1925 1922.5 1920 Release 12 41 4.3.1.2.6 3GPP TS 36.508 V12.4.1 (2014-12) TDD reference test frequencies for Operating Band 38 Table 4.3.1.2.6-1: Test frequencies for E-UTRA channel bandwidth for operating band 38 Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 Test Frequency ID Low Range Mid Range High Range 4.3.1.2.6A EARFCN 37775 37800 37825 37850 38000 38225 38200 38175 38150 Frequency (UL and DL) [MHz] 2572.5 2575 2577.5 2580 2595 2617.5 2615 2612.5 2610 TDD reference test frequencies for CA in operating band 38 Table 4.3.1.2.6A-1: Test frequencies for CA_38C Range Low High Note 1: CC1 Note1 BW [RB] 75 100 75 CC2 Note1 fUL/DL [MHz] 2577.5 2580 2587.5 BW [RB] 75 100 75 NUL/DL 37975 38048 38075 fUL/DL [MHz] 2592.5 2599.8 2602.5 100+100 100 37901 2585.1 75+75 75 38025 2597.5 100+100 100 37952 2590.2 Carriers in increasing frequency order. 100 75 100 38099 38175 38150 2604.9 2612.5 2610 75+75 100+100 75+75 Mid 4.3.1.2.7 CCCombo / NRB_agg [RB] NUL/DL 37825 37850 37925 TDD reference test frequencies for Operating Band 39 Table 4.3.1.2.7-1: Test frequencies for E-UTRA channel bandwidth for operating band 39 Test Frequency ID Low Range Mid Range High Range 4.3.1.2.7A Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 38275 38300 38325 38350 38450 38625 38600 38575 38550 Frequency (UL and DL) [MHz] 1882.5 1885 1887.5 1890 1900 1917.5 1915 1912.5 1910 TDD reference test frequencies for CA in Operating Band 39 Table 4.3.1.2.7A-1: Test frequencies for CA_39C 3GPP Release 12 Range Low Mid High Note 1: 4.3.1.2.8 42 CCCombo / NRB_agg [RB] 3GPP TS 36.508 V12.4.1 (2014-12) CC1 Note1 CC2 Note1 BW [RB] NUL/DL 25+100 25 38283 38350 100 50+100 50 38305 38350 100 75+100 75 38328 38350 100 25+100 25 38358 100 38425 50+100 50 38356 100 38401 75+100 75 38353 100 38376 38433 25+100 25 100 38500 38406 50+100 50 100 38451 38379 75+100 75 100 38401 Carriers in increasing frequency order. fUL/DL [MHz] 1883.3 1890 1885.5 1890 1887.8 1890 1890.8 1897.5 1890.6 1895.1 1890.3 1892.6 1898.3 1905.0 1895.6 1900.1 1892.9 1895.1 BW [RB] 100 25 100 50 100 75 100 25 100 50 100 75 100 25 100 50 100 75 NUL/DL 38400 38467 38449 38494 38499 38521 38475 38542 38500 38545 38524 38547 38550 38617 38550 38595 38550 38572 fUL/DL [MHz] 1895.0 1901.7 1899.9 1904.4 1904.9 1907.1 1902.5 1909.2 1905.0 1909.5 1907.4 1909.7 1910 1916.7 1910 1914.5 1910 1912.2 TDD reference test frequencies for Operating Band 40 Table 4.3.1.2.8-1: Test frequencies for E-UTRA channel bandwidth for operating band 40 Test Frequency ID Low Range Mid Range High Range 4.3.1.2.8A Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 38675 38700 38725 38750 39150 39625 39600 39575 39550 Frequency (UL and DL) [MHz] 2302.5 2305 2307.5 2310 2350 2397.5 2395 2392.5 2390 TDD reference test frequencies for CA in operating band 40 Table 4.3.1.2.8A-1: Test frequencies for CA_40C 3GPP Release 12 Range Low Mid High Note 1: 4.3.1.2.9 43 CCCombo / NRB_agg [RB] 3GPP TS 36.508 V12.4.1 (2014-12) CC1 Note1 CC2 Note1 BW [RB] NUL/DL 50+100 50 38705 38750 100 38725 75+75 75 38750 100+100 100 50+100 50 39056 100 39101 39075 75+75 75 100+100 100 39051 39406 50+100 50 100 39451 39425 75+75 75 39352 100+100 100 Carriers in increasing frequency order. fUL/DL [MHz] 2305.5 2310 2307.5 2310 2340.6 2345.1 2342.5 2340.1 2375.6 2380.1 2377.5 2370.2 BW [RB] 100 50 75 100 100 50 75 100 100 50 75 100 NUL/DL 38849 38894 38875 38948 39200 39245 39225 39249 39550 39595 39575 39550 fUL/DL [MHz] 2319.9 2324.4 2322.5 2329.8 2355.0 2359.5 2357.5 2359.9 2390 2394.5 2392.5 2390 TDD reference test frequencies for Operating Band 41 Table 4.3.1.2.9-1: Test frequencies for E-UTRA channel bandwidth for operating band 41 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 39675 39700 39725 39750 40620 41565 41540 41515 41490 Frequency (UL and DL) [MHz] 2498.5 2501 2503.5 2506 2593 2687.5 2685 2682.5 2680 4.3.1.2.9A TDD reference test frequencies for CA in operating band 41 Table 4.3.1.2.9A-1: Test frequencies for CA_41C 3GPP 5 2583.6 2583.6 2670.9 2520.5 2506 NUL/DL 39675 39675 39700 39700 39700 39725 39750 25+25 25+50 50+50 50+75 50+100 75+100 100+10 0 Carriers in increasing frequency order.9 2523.9 2665.1 2667.5 2600.1 2525.7 2602.1.5 2680 2682.9 2680 2684.5 2680 2680 2680 4.4 2602.5 3590 .2.5 3410 3500 3597. fUL/DL [MHz] 2501.8 2598.10-1: Test frequencies for E-UTRA channel bandwidth for operating band 42 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 3GPP 41615 41640 41665 41690 42590 43565 43540 43515 43490 Frequency (UL and DL) [MHz] 3402.1.5 2685 2685 2682.508 V12.4 2518.1.2 2680 NUL/DL 39849 39894 39875 39899 39921 39948 40670 40715 40695 40694 40717 40719 41490 41535 41515 41490 41512 41490 Table 4.2.5 2506 2503.3.5 3405 3407.3.10 TDD reference test frequencies for Operating Band 42 Table 4.1 2585.2 BW [RB] 100 50 75 100 75 100 100 50 75 100 75 100 100 50 75 100 75 100 fUL/DL [MHz] 2515.8 2506 2506 2583.5 2501 2501 2501 2503.1 2660.3.5 2662.6 2588.5 2503.4.5 2600.1 (2014-12) CC1 Note1 CC2 Note1 BW [RB] NUL/DL 50+100 50 39705 100 39750 75+75 75 39725 75+100 75 39728 100 39750 100+100 100 39750 50+100 50 40526 100 40571 75+75 75 40545 75+100 75 40523 100 40546 100+100 100 40521 50+100 50 41346 100 41391 75+75 75 41365 75+100 75 41319 100 41341 100+100 100 41292 Carriers in increasing frequency order.3 2585.0 2602.5 2520.1 2665.Release 12 Range Low Mid High Note 1: 44 CCCombo / NRB_agg [RB] 3GPP TS 36.9A-2: Test frequencies for CA_41A-41A Range N/A Note 1: CCCombo / NRB_agg [RB] CC1 Note1 BW [RB] 25 25 50 50 50 75 100 Wgap [MHz] fUL/DL [MHz] 2498.5 2498.5 2682.5 3595 3592. 184 179 174 169 164 159 154 CC2 Note1 BW [RB] 25 50 50 75 100 100 100 NUL/DL 41565 41540 41540 41515 41490 41490 41490 fUL/DL [MHz] 2687.2. 7 3419.3 3410 3405.1.2. CC2 Note1 fUL/DL [MHz] 3403.5 3595 3595 3592.4 3424.3 3585 3575.6 3490.8 3410 3410 3490.1.3.5 3490.3 3492.7 3590 3594.9 3427.5 3402.1 3578.8 3497.6 3495.4.10ATDD reference test frequencies for CA in operating band 42 Table 4.2.7 3509.4 3509.9 3575.9 3590 3596.5 3410 25+25 25+50 50+50 50+75 50+100 75+100 100+10 0 Carriers in increasing frequency order.8 3502. 3GPP 190 185 180 175 170 165 160 CC2 Note1 BW [RB] 25 50 50 75 100 100 100 NUL/DL 43565 43540 43540 43515 43490 43490 43490 fUL/DL [MHz] 3597.10A-2: Test frequencies for CA_42A-42A Range N/A Note 1: CCCombo / NRB_agg [RB] CC1 Note1 BW [RB] 25 25 50 50 50 75 100 NUL/DL 41615 41615 41640 41640 41640 41665 41690 Wgap [MHz] fUL/DL [MHz] 3402.5 3590 3592.5 3590 3590 3590 .2.2 BW [RB] 100 25 100 50 100 75 100 100 25 100 50 100 75 100 100 25 100 50 100 75 100 NUL/DL 41740 41807 41789 41834 41839 41861 41888 42615 42682 42640 42685 42664 42687 42689 43490 43557 43490 43535 43490 43512 43490 fUL/DL [MHz] 3415 3421.1.2 3590 Table 4.1 3429.6 3580.3.3.Release 12 45 3GPP TS 36.9 3424.1 (2014-12) 4.1 3570.5 3507.1 3490.2 3505 3509.5 3509.508 V12.1 3572.5 3410 3407.10A-1: Test frequencies for CA_42C CC-Combo / NRB_agg [RB] Range Low Mid High Note 1: CC1 Note1 BW [RB] NUL/DL 25+100 25 41623 100 41690 50+100 50 41645 100 41690 75+100 75 41668 100 41690 100+100 100 41690 25+100 25 42498 100 42565 50+100 50 42496 100 42541 75+100 75 42493 100 42516 100+100 100 42491 25+100 25 43373 100 43440 50+100 50 43346 100 43391 75+100 75 43319 100 43341 100+100 100 43292 Carriers in increasing frequency order.5 3405 3405 3405 3407. 23 Channel Number 1013 356 779 Frequency of Uplink [MHz] 824.3.1.00 1908.00 1988.23 1.2.2 Bandwidth [MHz] 1.25 Channel Number 25 600 1175 3GPP Frequency of Uplink [MHz] 1851.70 835.3 4.2.1.508 V12.5 798 795.5 3610 3700 3797.3.23 1.3.3.1.11 46 3GPP TS 36.2.2-1: Test frequencies for HRPD in Band Class 1 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 1.5 3795 3792.3.3.5 3790 TDD reference test frequencies for Operating Band 44 Table 4.2.4.25 1.68 893.25 1880.1-1: Test frequencies for HRPD in Band Class 0 Test Frequency ID Low Range Mid Range High Range 4.11-1: Test frequencies for E-UTRA channel bandwidth for operating band 43 Test Frequency ID Low Range Mid Range High Range 4.3.5 793 HRPD Test frequencies HRPD test frequencies for Band Class 0 Table 4.1.37 Frequency of Downlink [MHz] 869.1.12 Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 43615 43640 43665 43690 44590 45565 45540 45515 45490 Frequency (UL and DL) [MHz] 3602.68 848.75 Frequency of Downlink [MHz] 1931.37 HRPD test frequencies for Band Class 1 Table 4.70 880.1.3.5 705.1.25 1960.3.3.5 713 753 801.3.1 (2014-12) TDD reference test frequencies for Operating Band 43 Table 4.3.1 Bandwidth [MHz] 3 5 10 15 20 3/5/10/15/20 3 5 10 15 20 EARFCN 45605 45615 45640 45665 45690 46090 46575 46565 46540 46515 46490 Frequency (UL and DL) [MHz] 704.25 1.75 .5 3605 3607.12-1: Test frequencies for E-UTRA channel bandwidth for operating band 44 Test Frequency ID Low Range Mid Range High Range 4.5 800.5 708 710.1.Release 12 4.1.3. 25 1.1.3.1.1.25 1930.3 47 3GPP TS 36.25 HRPD test frequencies for Band Class 6 Table 4.5-1: Test frequencies for HRPD in Band Class 6 Test Frequency ID Low Range Mid Range High Range 4.3.50 Frequency of Downlink [MHz] 2116.25 1.7 Bandwidth [MHz] 1.25 Frequency of Downlink [MHz] 1845.25 1.3.3.1.90 915.25 1.00 1765.3.4.25 1.1 (2014-12) HRPD test frequencies for Band Class 3 Table 4.3.50 Frequency of Downlink [MHz] 853.25 1.3.00 2127.00 843.3.Release 12 4.3.25 Channel Number 100 300 525 Frequency of Uplink [MHz] 1755.50 1750.7-1: Test frequencies for HRPD in Band Class 15 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 1.1.4 Bandwidth [MHz] 1.3.25 Channel Number 75 450 800 3GPP Frequency of Uplink [MHz] 1713.6-1: Test frequencies for HRPD in Band Class 10 Test Frequency ID Low Range Mid Range High Range 4.75 2132.90 860.1.508 V12.00 1866.25 1.50 821.50 HRPD test frequencies for Band Class 15 Table 4.25 Channel Number 1120 872 76 Frequency of Uplink [MHz] 888.3.1.3.75 1732.3.00 1937.3.1.00 898.3.25 1.00 1855.95 Frequency of Downlink [MHz] 833.50 866.3-1: Test frequencies for HRPD in Band Class 3 Test Frequency ID Low Range Mid Range High Range 4.95 HRPD test frequencies for Band Class 4 Table 4.1.3.00 937.50 HRPD test frequencies for Band Class 10 Table 4.50 2150.25 Channel Number 125 200 350 Frequency of Uplink [MHz] 1926.00 .4-1: Test frequencies for HRPD in Band Class 4 Test Frequency ID Low Range Mid Range High Range 4.3.5 Bandwidth [MHz] 1.00 898.3.25 2120.00 Frequency of Downlink [MHz] 2113.25 1.1.25 Channel Number 100 500 820 Frequency of Uplink [MHz] 808.25 1.6 Bandwidth [MHz] 1.00 1776.3.3. 68 893.25 Channel Number 25 600 1175 Frequency of Uplink [MHz] 1851.00 1765.23 1.00 1866.25 1xRTT test frequencies for Band Class 6 Table 4.3.4.00 898.90 860.1 48 3GPP TS 36.1.3.1.3.1.25 1960.5-1: Test frequencies for 1xRTT in Band Class 6 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 1.23 1.1.3.508 V12.1.3-1: Test frequencies for 1xRTT in Band Class 3 Test Frequency ID Low Range Mid Range High Range 4.3.4.1.25 1.75 .1.25 Channel Number 225 275 375 3GPP Frequency of Uplink [MHz] 1931.95 1xRTT test frequencies for Band Class 4 Table 4.3.25 2123.3.00 1988.5 Bandwidth [MHz] 1.00 1908.25 1.75 Frequency of Downlink [MHz] 2121.1.25 1.4 Bandwidth [MHz] 1.00 1776.25 1.25 1.25 1.37 Frequency of Downlink [MHz] 869.4 4.25 Channel Number 100 300 525 Frequency of Uplink [MHz] 1755.3.3.37 1xRTT test frequencies for Band Class 1 Table 4.3.4.75 1xRTT test frequencies for Band Class 3 Table 4.4.4.1.1.Release 12 4.4.25 Channel Number 1120 872 76 Frequency of Uplink [MHz] 888.2-1: Test frequencies for 1xRTT in Band Class 1 Test Frequency ID Low Range Mid Range High Range 4.4.00 1855.2 Bandwidth [MHz] 1.25 1880.75 1938.4-1: Test frequencies for 1xRTT in Band Class 4 Test Frequency ID Low Range Mid Range High Range 4.25 1.1.68 848.1-1: Test frequencies for 1xRTT in Band Class 0 Test Frequency ID Low Range Mid Range High Range 4.4.25 Frequency of Downlink [MHz] 1845.25 1933.1 (2014-12) 1xRTT Test frequencies 1xRTT test frequencies for Band Class 0 Table 4.4.75 Frequency of Downlink [MHz] 1931.70 835.70 880.4.95 Frequency of Downlink [MHz] 833.23 Channel Number 1013 356 779 Frequency of Uplink [MHz] 824.75 2128.3.90 915.25 1.00 843.3 Bandwidth [MHz] 1.4. 7 Bandwidth [MHz] 1.50 1xRTT test frequencies for Band Class 15 Table 4.521-1.3.same as per Table 4.6 1846. TS 36.521-3 and TS 37.75 1732.5.9 1872.4/3/5/10 15 [1]/20 [1] 1.50 Frequency of Downlink [MHz] 853.3.4 3 5 10 15 [1] 20 [1] 1.4 1847.1.3.2-1: Test frequencies for E-UTRA channel bandwidth for operating band 3 overlapping with band 9 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 1.00 MFBI Test frequencies Editor’s Note: MFBI test frequencies are not used for TS 36.1.4.50 1750.1.1.1.25 1.1.9 NDL 1606 1614 1624 1649 1674 1699 Frequency of Downlink [MHz] 1845.00 898.5.1.1 MFBI Test frequencies for operation band 2 overlapping with band 25 .same as per Table 4.25 1.4-1 3GPP .4.25 1.5 Bandwidth [MHz] 1.9 1852.2 1878.50 2150.4.1.3.25 Channel Number 100 500 820 Frequency of Uplink [MHz] 808.2-1 4.4 1774 1862.3 MFBI Test frequencies for operation band 4 overlapping with band 10 .4 1752.4 1854.101 [27] Clause 7.6 49 3GPP TS 36.9 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.9 1757.3.50 821.3.4 1874.50 866.Release 12 4.4 1754.25 1.3.571-1.3.9 1849 1869.1. 4.1.3) is allowed.7-1: Test frequencies for 1xRTT in Band Class 15 Test Frequency ID Low Range Mid Range High Range 4.4 1942 1934 1924 1899 1874 1879.2 MFBI Test frequencies for operation band 3 overlapping with band 9 Table 4.4 1849.6 1751.00 Frequency of Downlink [MHz] 2113.9 19774 1767.75 2132.4 3 5 10 15 [1] 20 [1] NUL 19606 19614 19624 19649 19674 19699 Frequency of Uplink [MHz] 1750.4 1759.25 Channel Number 75 450 800 Frequency of Uplink [MHz] 1713.4 1877. 4.00 937.1.9 1777.4 1779.2 1783.3.6-1: Test frequencies for 1xRTT in Band Class 10 Test Frequency ID Low Range Mid Range High Range 4.4.1 (2014-12) 1xRTT test frequencies for Band Class 10 Table 4.4 19942 19934 19924 19899 19874 1784.5.3.3.5.4.508 V12.1.4 1782.1.4 19849 1774. 1 (2014-12) MFBI Test frequencies for operation band 5 overlapping with band 18 Table 4.5 Frequency of Downlink [MHz] 869.3.4.5 872.5 2535 Mid Range 10 [1] 1.4 3 5 20407 20415 20425 20430 20453 20445 20435 824.5 2150 2147.5.5 2595 888.3.8-1: Test frequencies for E-UTRA channel bandwidth for operating band 10 overlapping with band 4 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 NUL Frequency of Uplink [MHz] 1712.5 827 829.4 20603 844.9-1 4.5 1752.4 3 5 1.7 825.6 MFBI Test frequencies for operation band 5 overlapping with band 26 .same as per Table 4.5 1.5 .5 2120 2132.5.3.3.5 880 882.1.5 1750 1747.3.5 10 [1] 20560 840 2560 885 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5-1: Test frequencies for E-UTRA channel bandwidth for operating band 5 overlapping with band 19 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 875.5 High Range 5 20585 842.5.5 2407 2415 2425 2430 2453 2445 2435 Low Range Mid Range High Range 4.4 20467 830.5 2115 2117.5 2585 887.5-1 4.5 2152.5 2485 10 [1] 20510 835 2510 1.3.5 826.1.1.5 MFBI Test frequencies for operation band 5 overlapping with band 19 Table 4.5 1720 1732.1.same as per Table 4.4/3/5 20535 837.4-1: Test frequencies for E-UTRA channel bandwidth for operating band 5 overlapping with band 18 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL 1.1.5 2475 Low Range 5 20485 832.Release 12 4.3 2603 889.1.7 2467 3 20475 831.1.7 MFBI Test frequencies for operation band 9 overlapping with band 3 .4 50 3GPP TS 36.5.7 876.1.3.5 22175 22200 22225 22250 22375 22575 22550 22525 3GPP NDL 4175 4200 4225 4250 4375 4575 4550 4525 Frequency of Downlink [MHz] 2112.5.3.5.508 V12.101 [27] Clause 7. 4.1.3 3 20595 843.3) is allowed.3.1.8 MFBI Test frequencies for operation band 10 overlapping with band 4 Table 4.1.3.5 1715 1717.7 870.3 873.1.4/3/5 1.5.5.5 877.3 828.5 827.5 871.5 872 874. 5.18-1 3GPP .3) is allowed.101 [27] Clause 7.7 825.7 5067 734.5 5155 743.10 MFBI Test frequencies for operation band 17 overlapping with band 12 .Release 12 51 20 4.1.3.17-1 4.5 827.4 3 5 1.3.3.7 3 23075 705.1.same as per Table 4.4/3 23120 710 5120 740 5 [1]/10 [1] 1.1.1.5 872.5 5075 735.5 High Range 5 [1] 23155 713. 4.5 5165 744.5 MFBI Test frequencies for operation band 18 overlapping with band 26 .1 (2014-12) 1745 4500 2145 MFBI Test frequencies for operation band 12 overlapping with band 17 Table 4.4 23173 715.5 10 [1] 23110 709 5110 739 Mid Range 1.508 V12.7 870.9 22500 3GPP TS 36.5 5947 5955 5965 5970 5993 5985 5975 Frequency of Downlink [MHz] 869.5.5 826.11-1: Test frequencies for E-UTRA channel bandwidth for operating band 18 overlapping with band 5 Test Frequency ID Low Range Mid Range High Range 4.1.1.3.same as per Table 4.3 873.5 872 874.5.5 Low Range 5 [1] 23085 706.3.3 3 23165 714.3 5173 745.3.4 3 5 23947 23955 23965 23970 23993 23985 23975 824.4/3/5 1.4 23067 704.1.5.3.3.5.9-1: Test frequencies for E-UTRA channel bandwidth for operating band 12 overlapping with band 17 Test Frequency ID Bandwidth NUL Frequency of NDL Frequency of [MHz] Uplink [MHz] Downlink [MHz] 1.11 MFBI Test frequencies for operation band 18 overlapping with band 5 Table 4.1.4.5 827 829.5 871.5.5 10 [1] 23130 711 5130 741 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.12 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL 1.5 5085 736.1.3 828.1. 5 High Range 10 26590 1905 8590 1985 15 [1] 26565 1902.5 5 26615 1907.3.7 1931.7 8047 3 26055 1851.7 870.7 825.1.15 MFBI Test frequencies for operation band 19 overlapping with band 26 .1.19-1 4.3 822.3.17 MFBI Test frequencies for operation band 26 overlapping with band 5 Table 4.5 866.7 861.5 8065 Low Range 10 26090 1855 8090 15 [1] 26115 1857.5 8615 1987.5.5.5 8115 20 [1] 26140 1860 8140 Mid Range 1.1.16-1: Test frequencies for E-UTRA channel bandwidth for operating band 25 overlapping with band 2 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 1930.same as per Table 4.1.4/3/5/10 26340 1880 8340 15 [1]/20 [1] 1.5.5 817.7 816.3.5.1.4.16 MFBI Test frequencies for operation band 25 overlapping with band 2 Table 4.4 3 5 1.1.4 3 5 23857 23865 23875 23895 23933 23925 23915 815.4 26633 1909.5 8625 1988.5 868.3.1.1.5 1940 1960 1.5.5.3) is allowed.3 8633 1989.19-1 4.3 867.5 8565 1982.1 (2014-12) MFBI Test frequencies for operation band 18 overlapping with band 27 Table 4.3.508 V12.1.5 826.14 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL 1.5 819.3.same as per Table 4.101 [27] Clause 7.3 3 26625 1908.5 821.1.5.5 8055 5 26065 1852.3.5 823.Release 12 52 4.5.5 .1.5 5857 5865 5875 5895 5933 5925 5915 Frequency of Downlink [MHz] 860.4 3 5 26797 26805 26815 824.13 3GPP TS 36.5 MFBI Test frequencies for operation band 19 overlapping with band 5 .1.4 26047 1850.5 1932. 4.4/3/5 1.5 20 [1] 26540 1900 8540 1980 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 864.5 1935 1937.5 8797 8805 8815 3GPP Frequency of Downlink [MHz] 869.3.13-1: Test frequencies for E-UTRA channel bandwidth for operating band 18 overlapping with band 27 Test Frequency ID Low Range Mid Range High Range 4.3.3.5 862.17-1: Test frequencies for E-UTRA channel bandwidth for operating band 26 overlapping with band 5 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Low Range 1.5 871. 19-1: Test frequencies for E-UTRA channel bandwidth for operating band 26 overlapping with band 19 Test Frequency ID Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL Frequency of Downlink [MHz] 875.5 8865 876.5 8875 10[1] 26900 835 8900 Mid Range 1.5 9015 891. 3GPP .4 27033 848.5 8915 881.101 [27] Clause 7.3 3 26835 828.3.5 8825 872.19 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL MFBI Test frequencies for operation band 26 overlapping with band 19 Table 4.3 8843 874.3) is allowed.Release 12 53 3GPP TS 36.4 26993 844.4/3/5/10[1] 26915 836.5 10[1] 26800 825 8800 870 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.3 9033 893.5 8965 886.3.18 MFBI Test frequencies for operation band 26 overlapping with band 18 Table 4.4.5 15 [1] 1.5 High Range 5 26975 842.3 8993 889.1.5 8835 873.101 [27] Clause 7.5 8925 15 [1] 1.1 (2014-12) 10[1] 26840 829 8840 874 15 [1] 26865 831.3) is allowed.1.5 877.7 876.4 26843 829.5.5.5 8725 862.5 9025 892.1.3) is allowed.5 10[1] 26990 844 8990 889 15 [1] 26965 841.5 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.4/3/5/10[1] 26925 837.3.3.5 8975 887.4 26857 830.7 8707 860.5 8865 Low Range 5 26875 832.7 8857 3 26865 831. 4.5 Mid Range 1.5 1.5 8775 867.5 10[1] 26750 820 8750 865 Mid Range 1.5 10[1] 26950 840 8950 885 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 8985 888.4/3/5/10[1] 26775 822.5 High Range 5 27015 846.508 V12.5 Low Range 5 26725 817.1.5 High Range 5 26825 827.101 [27] Clause 7.5 8715 861. 4.5 880 882.18-1: Test frequencies for E-UTRA channel bandwidth for operating band 26 overlapping with band 18 Test Frequency ID Frequency of Downlink [MHz] 1.3 3 27025 847.5.7 3 26715 816.5.3 3 26985 843.5 1.4 26707 815. 21-1: Test frequencies for E-UTRA channel bandwidth for operating band 27 overlapping with band 18 Test Frequency ID Low Range Mid Range High Range 4.101 [27] Clause 7.4 27203 823.21 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL MFBI Test frequencies for operation band 27 overlapping with band 18 Table 4.2.5 9127 9135 9145 9165 9203 9195 9185 Frequency of Downlink [MHz] 860.5 821.5 8705 860.1.1-1 4.5 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 817.4 3 5 1.4/3/5 27160 819 9160 864 1.5 9135 861.1.5 Mid Range 1. 4.5.23 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL MFBI Test frequencies for operation band 33 overlapping with band 39 .3 9203 868.5 819.4 3 5 27127 27135 27145 27165 27203 27195 27185 815.3.same as per Table 4.5.1.same as per Table 4.3.3.3.3.7 8697 859.4/3/5 26740 819 8740 864 1.7 861.22-1: Test frequencies for E-UTRA channel bandwidth for operating band 27 overlapping with band 26 Test Frequency ID Frequency of Downlink [MHz] 1.5.1.3.4/3/5 1.5 9185 866.7 9117 859.5 5 26715 816.5.5 5 26765 821.5 Mid Range 1.5 9125 860.20 3GPP TS 36.5.5 MFBI Test frequencies for operation band 27 overlapping with band 26 Table 4.1 (2014-12) MFBI Test frequencies for operation band 26 overlapping with band 27 Table 4.3 867.4 26783 823.7 816.5.Release 12 54 4.4 27117 814.7 Low Range 3 26705 815.4 26697 814.5 868.3 8783 868.5 8775 867.3.24 MFBI Test frequencies for operation band 38 overlapping with band 41 .3) is allowed.3 High Range 3 26775 822.5 9195 867.5 8765 866.5 862.5 NOTE 1: Bandwidth for which a relaxation of the specified UE receiver sensitivity requirement (TS 36.5 8715 861.2.3) is allowed.1.3.6-1 3GPP .5 864.1.22 Bandwidth [MHz] NUL Frequency of Uplink [MHz] NDL 1.1.508 V12.5 823.3.5 5 27185 821.101 [27] Clause 7.5.3 822. 4.5.3.7 Low Range 3 27125 815.1.4.5 866.1.5 5 27135 816.3 High Range 3 27195 822.1.20-1: Test frequencies for E-UTRA channel bandwidth for operating band 26 overlapping with band 27 Test Frequency ID Frequency of Downlink [MHz] 1. 25-1: Test frequencies for E-UTRA channel bandwidth for operating band 39 overlapping with band 33 Test Frequency ID Low Range Mid Range High Range 4.3.5 1915 1912.1 Antennas If the UE has two Rx antennas.25 55 3GPP TS 36.5 1905 1907.2-1 and for two SS Tx antennas in table 4. The uplink connection between the UE and System Simulator is without Additive White Gaussian Noise.508 V12.3.3.3.3.1.3. and has no fading or multipath effects.5 1910 MFBI Test frequencies for operation band 41 overlapping with band 38 Table 4.26-1: Test frequencies for E-UTRA channel bandwidth for operating band 41 overlapping with band 38 Test Frequency ID Low Range Mid Range High Range Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 40415 40440 40465 40490 40640 40865 40840 40815 40790 Frequency (UL and DL) [MHz] 2572.2 Radio conditions 4. the downlink signal is applied to it.213 [29] clause 5.3.5 2575 2577.5 2615 2612.1. 3GPP .2 Downlink physical channels and physical signals The Downlink Physical channels and Physical signals used and their relative powers are specified for single SS Tx antenna in table 4. 4.5. The details of downlink power allocation for PDSCH channel are described in TS 36. the same downlink signal is applied to each one.3.3.1 Normal propagation condition The downlink connection between the System Simulator and the UE is without Additive White Gaussian Noise.5.5 2580 2595 2617.3. Both UE Rx antennas shall be connected unless otherwise stated in the test case.2. If the UE has one Rx antenna.5 1910 1910 1917.1.3.4.1.3.1 (2014-12) MFBI Test frequencies for operation band 39 overlapping with band 33 Table 4.2.5.3.3.26 Bandwidth [MHz] 5 10 15 20 5/10/15/20 5 10 15 20 EARFCN 38475 38500 38525 38550 38550 38625 38600 38575 38550 Frequency (UL and DL) [MHz] 1902.Release 12 4.3. 4. and has no fading or multipath effects.2-2.5.5 2610 4.3 Physical channel allocations 4. 211 [35].4. The mapping of downlink physical channels to physical resources for Single Tx Antenna is described in table 4. Physical layer cell identity = 0 is used as the default physical layer cell identity N ID CFI = 3 for 1.2-2: Power allocation for OFDM symbols and reference signals.Release 12 56 3GPP TS 36.1.3. 3 and 5 MHz system bandwidths = 2 for 10. Mapping of downlink physical channels and signals to physical resources Parameters for mapping of downlink physical channels and signals are specified as follows. For RF testing. 3GPP . 15 and 20 MHz system bandwidths = 2 if PMCH is configured (‘mbsfn-SubframeConfiguration’ is present in SIB2) Ng =1 PHICH duration = Normal For Signalling testing.508 V12.4. two SS Tx antennas Physical Channel PBCH PSS SSS PCFICH PDCCH PDSCH PHICH PMCH MBSFN RS NOTE: 4.3.3.3.521-1 [21] Annex C.1 (2014-12) Table 4. single SS Tx antenna Physical Channel PBCH PSS SSS PCFICH PDCCH PDSCH PHICH PMCH MBSFN RS EPRE Ratio PBCH_RA = 0 dB PBCH_RB = 0 dB PSS_RA = 0 dB SSS_RA = 0 dB PCFICH_RB = 0 dB PDCCH_RA = 0 dB PDCCH_RB = 0 dB PDSCH_RA = 0 dB PDSCH_RB = 0 dB PHICH_RB = 0 dB PMCH_RA = 0 dB MBSFN RS_RA = 0dB Table 4.3.3-2 for 5/20MHz system bandwidth TDD.3.2-1: Power allocation for OFDM symbols and reference signals.3. Normal Cyclic Prefix cell .3-1 for 5/10MHz system bandwidth FDD and table 4.3. the mapping of DL physical channels to resource element is defined TS 36.3 EPRE Ratio PBCH_RA = 0 dB PBCH_RB = 0 dB PSS_RA = 0 dB SSS_RA = 0 dB PCFICH_RB = 0 dB PDCCH_RA = 0 dB PDCCH_RB = 0 dB PDSCH_RA = -3 dB PDSCH_RB = -3 dB PHICH_RB = 0 dB PMCH_RA = 0 dB MBSFN RS_RA = 0dB MBSFN RS is not defined downlink physical channels in TS 36.3.3. the default system bandwidth is 5/10/20 MHz and single SS Tx antenna is used unless specified otherwise in the test case. 1 of each subframe (BW=10MHz) Symbols 0. 1 of each MBSFN subframe PDSCH All remaining OFDM symbols of each subframe not allocated to PDCCH Note Mapping rule is specified in TS36.8.3-1: Mapping of DL Physical Channels to Resource Elements for Single SS Tx Antenna and 5/10 MHz System Bandwidth (FDD) Physical channel PBCH Time Domain Location Frequency Domain Location Symbols 0 to 3 of slot 1 of subframe 0 of each radio frame Occupies 72 subcarriers centred on the DC subcarrier PSS Symbol 6 of slot 0 and 10 of each radio frame SSS Symbol 5 of slots 0 and 10 of each radio frame PCFICH Symbol 0 of each subframe PHICH Symbol 0 of each subframe Occupies 62 subcarriers centred on the DC subcarrier.4 . 1. Each PHICH group maps into 3 REGs in the frequency domain on the REGs not assigned to PCFICH over the whole system bandwidth.2 Mapping rule is specified in TS36.211 [35] sub clause 6.8.1 (2014-12) Table 4.4 Mapping rule is specified in TS36. Maps into 4 REGs uniformly spread in the frequency domain over the whole system bandwidth.2.3 . 3GPP . REs not allocated to RS is allocated to PDSCH REs not allocated to MBSFN RS is allocated to PMCH In case a single cell-specific RS is configured. REs not allocated to RS. 2 of each subframe (BW=5MHz) The remaining REGs not allocated to both PCFICH and PHICH are used for PDCCH Symbols 0.CFI = 3 (BW=5MHz) Mapping rule is specified in TS36.6.4.211 [35] sub clause 6.211 [35] sub clause 6. Occupies 62 subcarriers centred on the DC subcarrier.7.CFI = 2(BW=10MHz) Mapping rule is specified in TS36. (See TS 36.211 [35] sub clause 6. Additional 10 subcarriers (5 on each side) adjacent to the centred 62 subcarriers are reserved.Number of PHICH groups = 4(BW=5 MHz)/7(BW=10MHz) Mapping rule is specified in TS36. PSS.CELL_ID = 0 .2 Mapping rule is specified in TS36.11.3.211 [35] sub clause 6.2. PSS and SSS is allocated to PDSCH PMCH NOTE: MBSFN region of MBSFN subframes For other subframes.CELL_ID = 0 Mapping rule is specified in TS36.9.1.5 . SSS and PBCH is allocated to PDSCH For Subframe 5.Release 12 57 3GPP TS 36.508 V12.3.211 [35] sub clause 6.CFI = 2 For Subframe 0.5 . REs not allocated to RS. cell-specific RS shall be assume to be present on antenna ports 0 and 1 for the purpose of mapping a symbol-quadruplet to a REG (resource element group).4).211 [35] sub clause 6. PDCCH Symbols 0.211 [35] sub clause 6.11.5 .8.211 [35] sub clause 6. Additional 10 subcarriers (5 on each side) adjacent to the centred 62 subcarriers are reserved. 5 . 1.2. GP and UpPTS is allocated to PDSCH PMCH MBSFN region of MBSFN subframes For other downlink subframes.211 [35] subclause 6.1 (2014-12) Table 4.211 [35] subclause 6.508 V12. 2 of other downlink subframes (BW=5MHz) Symbols 0. cell-specific RS shall be assume to be present on antenna ports 0 and 1 for the purpose of mapping a symbol-quadruplet to a REG (resource element group).4.211 [35] subclause 6.211 [35] subclause 6.4 .211 [35] subclause 6. 1 of each MBSFN subframe PDSCH All remaining OFDM symbols of each downlink subframe and DwPTS not allocated to PDCCH Frequency Domain Location Occupies 72 subcarriers centred on the DC subcarrier Occupies 62 subcarriers centred on the DC subcarrier. 1 of other downlink subframes (BW=20MHz) Symbols 0.Number of PHICH groups = 4(BW=5MHz)/13(BW=20MHz) Mapping rule is specified in TS36.CFI = 2 (BW=20MHz) Mapping rule is specified in TS36. PSS. Additional 10 subcarriers (5 on each side) adjacent to the centred 62 subcarriers are reserved.2 Mapping rule is specified in TS36.3 . Maps into 4 REGs uniformly spread in the frequency domain over the whole system bandwidth. REs not allocated to RS. Additional 10 subcarriers (5 on each side) adjacent to the centred 62 subcarriers are reserved.4 Mapping rule is specified in TS36.9.3. REs not allocated to RS is allocated to PDSCH REs not allocated to MBSFN RS is allocated to PMCH NOTE 1: In case a single cell-specific RS is configured. 1 of subframe 1.Release 12 58 3GPP TS 36.3.11.1.2.2 Mapping rule is specified in TS36.3-2: Mapping of DL Physical Channels to Resource Elements for Single SS Tx Antenna and 5/20 MHz System Bandwidth (TDD) Physical channel PBCH PSS Time Domain Location Symbols 0 to 3 of slot 1 of subframe 0 of each radio frame Symbol 2 of slot 2 and 12 of each radio frame SSS Symbol 6 of slots 1 and 11 of each radio frame PCFICH Symbol 0 of each downlink subframe and Special subframe PHICH Symbol 0 of each downlink subframe and Special subframe PDCCH Symbols 0.211 [35] sub clause 6.8.CELL_ID = 0 Mapping rule is specified in TS36. REs not allocated to RS. SSS and PBCH is allocated to PDSCH For Subframe 5. 6 and Symbols 0.4) 3GPP . Each PHICH group maps into 3 REGs in the frequency domain on the REGs not assigned to PCFICH over the whole system bandwidth.211 [35] subclause 6. Occupies 62 subcarriers centred on the DC subcarrier.8.CFI = 3 (BW=5MHz) Mapping rule is specified in TS36.211 [35] subclause 6. (See TS 36.CFI = 2 For Subframe 0.7.5 . 6 and Symbols 0.CELL_ID = 0 .211 [35] subclause 6.11. 1 of subframe 1. The remaining REGs not allocated to both PCFICH and PHICH are used for PDCCH Note Mapping rule is specified in TS36. REs not allocated to RS and SSS is allocated to PDSCH For Subframe 1 and 6.6.8.5 . 6.4 Signal levels 4.4.5.2 Uplink signal levels [FFS] 4. 4.4.5 Mapping of uplink physical channels and signals to physical resources [FFS].4.3. Note 2: The power level is specified at each UE Rx antenna.3.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz Number of RBs 6 15 25 50 75 100 Channel BW Power dBm -66 -62 -60 -57 -55 -54 RS EPRE dBm/15kHz -85 -85 -85 -85 -85 -85 Note 1: The channel bandwidth powers are informative. If the uncertainty value is critical for the test purpose a tighter uncertainty is specified for the related test case in TS 36. based on -85dBm/15kHz RS_EPRE.1 Downlink test signals [FFS] 4.521-3 [34] Annex F 4.1-1 are used unless otherwise specified in a test case.3. for any level specified. The default signal level uncertainty is +/-3dB at each test port.4. then scaled according to the number of RBs and rounded to the nearest integer dBm value. and if so how unallocated Resource elements should be treated.2 Uplink test signals [FFS] 3GPP .3.521-1 [21] Annex F or in TS 36.1 Downlink signal levels The downlink power settings in table 4. 4.3.508 V12.1-1: Default Downlink power levels Unit Channel bandwidth 1. Table 4.1 (2014-12) NOTE 2: In case the default TDD configuration for subframe assignment and special subframe patterns (see subclause 4.3.3. Full RE allocation with no boost or deboost is assumed.Release 12 59 3GPP TS 36. It is [FFS] whether there is a requirement to specify constant power throughout all OFDM symbols.3.4.3.5.5 Standard test signals 4.3.4 Uplink physical channels and physical signals [FFS].3.3.3) 4. 508 V12.2-1.1 Physical layer parameters for DCI format 0 Default physical layer parameters for DCI format 0 are specified in table 4.1 Downlink physical layer parameters 4.6. This is present for all the uplinkdownlink configurations and only applies to uplink -downlink configuration 1-6 HARQ process number New data indicator Redundancy version TPC command for PUCCH Downlink Assignment Index (TDD only) 3GPP Value in binary "0" "00" "01" - . Table 4.3.1.6.321 Depending on test parameters 0 dB (accumulated TPC) 2 bits as defined in Table 7. Set for every data transmission/retransmission according to the rules specified in TS 36.2 Value format 0 w/o Hopping Depending on test parameters Depending on test parameters Set for every data transmission/retransmission according to the rules specified in TS 36.1. This field is present only for TDD configuration 0 2 bits as defined in Table 7.4.213.321 0 dB (accumulated TPC) 0 2 bits as defined in sections 5. This field is present only for TDD configuration 1-6 w/o aperiodic CQI Value in binary "0" "0" "01" "000" - - "0" Physical layer parameters for DCI format 1 Default physical layer parameters for DCI format 1 are specified in table 4.213.3.1-1: Physical layer parameters for DCI format 0 Parameter Flag for format 0/format 1A differentiation Hopping flag Resource block assignment and hopping resource allocation Modulation and coding scheme and redundancy version New data indicator TPC command for scheduled PUSCH Cyclic shift for DM RS UL index (TDD only) Downlink Assignment Index (TDD only) CQI request 4.3.1 (2014-12) 4.213. It represents the total number of PDSCH subframes with and without PDCCH and PDCCH indicating downlink SPS release in the window.1.3-X in TS 36.1-1.3.3.6.1.6.1.6 Physical layer parameters 4.1. 3bits for FDD.3-X in TS 36.3.1 and 8 of TS 36.1.1.6.Release 12 60 3GPP TS 36.3.6. It represents the number of PDSCH with PDCCH and PDCCH indicating downlink SPS release in the window up to the present subframe.6.2-1: Physical layer parameters for DCI format 1 Parameter Resource allocation header Resource block assignment Modulation and coding scheme Value Resource allocation type 0 Depending on test parameters Depending on test parameters Depending on test parameters.3. 4 bits for TDD. Table 4. 508 V12.321 Depending on test parameters 0 dB (accumulated TPC) 2 bits as defined in Table 7.3.4.1.3-X in TS 36.3 61 3GPP TS 36.1 (2014-12) Physical layer parameters for DCI format 1A Default physical layer parameters for DCI format 1A are specified in table 4.6.213.3-1: Physical layer parameters for DCI format 1A Parameter Flag for format 0/format 1A differentiation Localized/Distributed VRB assignment flag Resource block assignment Modulation and coding scheme Value format 1A Localized VRB assignment Depending on test parameters Depending on test parameters Depending on test parameters.3.1.3. This is present for all the uplinkdownlink configurations and only applies to uplink -downlink configuration 1-6 HARQ process number New data indicator Redundancy version TPC command for PUCCH Downlink Assignment Index (TDD only) 3GPP Value in binary "1" "0" "00" "01" - .6. Set for every data transmission/retransmission according to the rules specified in TS 36. Table 4. 4 bits for TDD.1. 3bits for FDD. It represents the number of PDSCH with PDCCH and PDCCH indicating downlink SPS release in the window up to the present subframe.Release 12 4.6.3-1. 2.6. 4 bits for TDD.3A-1: Physical layer parameters for DCI format 1B Parameter Localized/Distributed VRB assignment flag Resource block assignment Modulation and coding scheme Value Localized VRB assignment Depending on test parameters Depending on test parameters Depending on test parameters.213.4.4-1.0 for precoding according to the indicated TPMI in the TPMI information field HARQ process number New data indicator Redundancy version TPC command for PUCCH Downlink Assignment Index (TDD only) TPMI information for precoding PMI confirmation for precoding 4.6.1.Release 12 4.3A 62 3GPP TS 36.508 V12.3-1 for 2 Tx antenna ports and Table 6.4-1: Physical layer parameters for DCI format 1C Parameter gap value (N_RB >= 50) Resource block assignment Transport block size index Value gap1 depending on test parameters depending on test parameters 3GPP Value in binary "0" - .3-2 for 4 Tx antenna ports corresponding to the single layer transmission Set for every transmission.6.3.3.1.211 Table 6. Set for every data transmission/retransmission according to the rules specified in TS 36.1.6.3.1. 3bits for FDD.3. It represents the number of PDSCH with PDCCH and PDCCH indicating downlink SPS release in the window up to the present subframe.6.4 Value in binary "0" "00" "01" - - - Physical layer parameters for DCI format 1C Default physical layer parameters for DCI format 1C are specified in table 4.4. Table 4.3-X in TS 36.1 (2014-12) Physical layer parameters for DCI format 1B Default physical layer parameters for DCI format 1B are specified in table 4.6.3.1.4.3. This is present for all the uplinkdownlink configurations and only applies to uplink -downlink configuration 1-6 Set for codebook index according to TS 36.1.3. 1 for precoding according to the latest reported PMI on PUSCH. Table 4.321 Depending on test parameters 0 dB (accumulated TPC) 2 bits as defined in Table 7.3.2.3A-1. 3.5-5 for 4 Tx antenna ports Downlink Assignment Index (TDD only) HARQ process number Transport block to codeword swap flag Modulation and coding scheme (transport block 1) New data indicator (transport block 1) Redundancy version (transport block 1) Modulation and coding scheme (transport block 2) New data indicator (transport block 2) Redundancy version (transport block 2) Precoding information 3GPP Value in binary "0" "01" - "0" - . It represents the number of PDSCH with PDCCH and PDCCH indicating downlink SPS release in the window up to the present subframe. Table 4.3-X in TS 36.4.6.1. This is present for all the uplinkdownlink configurations and only applies to uplink -downlink configuration 1-6 Depending on test parameters. 3bits for FDD.213.3.5 63 3GPP TS 36.1 (2014-12) Physical layer parameters for DCI format 2 Default physical layer parameters for DCI format 2 are specified in table 4.1.5-1: Physical layer parameters for DCI format 2 Parameter Resource allocation header Resource block assignment TPC command for PUCCH Value Resource allocation type 0 Depending on test parameters 0 dB (accumulated TPC) 2 bits as defined in Table 7. 4 bits for TDD.212 Table 5.321 Depending on test parameters Set for every transmission according to 36.3.508 V12.3.6.1.5-1.321 Depending on test parameters Depending on test parameters Set for every data transmission/retransmission according to the rules specified in TS 36.5-4 for 2 Tx antenna ports and Table 5.3.6.1.3. No swap Depending on test parameters Set for every data transmission/retransmission according to the rules specified in TS 36.3.1.Release 12 4. 3bits for FDD. It represents the number of PDSCH with PDCCH and PDCCH indicating downlink SPS release in the window up to the present subframe.6.5A-2 Downlink Assignment Index (TDD only) HARQ process number Transport block to codeword swap flag Modulation and coding scheme (transport block 1) New data indicator (transport block 1) Redundancy version (transport block 1) Modulation and coding scheme (transport block 2) New data indicator (transport block 2) Redundancy version (transport block 2) Precoding information Value in binary "0" "01" - "0" - 4.6-1. 4.321 depending on test parameters N/A for 2 Tx antenna ports.1.3-X in TS 36. GSM. This is present for all the uplinkdownlink configurations and only applies to uplink -downlink configuration 1-6 depending on test parameters. HRPD or 1xRTT)).3.3.212 Table 5.1.6-1: Physical layer parameters for DCI format 2A Parameter Resource allocation header Resource block assignment TPC command for PUCCH Value Resource allocation type 0 depending on test parameters 0 dB (accumulated TPC) 2 bits as defined in Table 7.4.Release 12 4. For 4 Tx antenna ports.4 Reference system configurations The reference system configurations specified in this sub clause apply to all test cases unless otherwise specified.1-1 for such information.1.321 depending on test parameters depending on test parameters Set for every data transmission/retransmission according to the rules specified in TS 36.1 Single cell network scenarios For FDD and TDD basic single cell environment.4. set for every transmission according to 36.1.1 Simulated network scenarios The UE will eventually have to operate in either single mode networks (FDD or TDD). Cell 1 is used.3. 4.2.6. Please refer to Table 6. or inter-RAT networks ((FDD or TDD) + (UTRA FDD. 3GPP .3.213. NOTE 1: The number of cells specified does not necessarily correspond to the maximum number of resources to be configured simultaneously in test equipment.1.6 64 3GPP TS 36.4. and 4 bits for TDD. Table 4.6. No swap depending on test parameters Set for every data transmission/retransmission according to the rules specified in TS 36. UTRA TDD.3.3. NOTE 2: For NAS test cases see sub clause 6.1 (2014-12) Physical layer parameters for DCI format 2A Default physical layer parameters for DCI format 2A are specified in table 4. Simulated network scenarios to be tested are listed in this sub clause.508 V12. dual mode networks (FDD+TDD). 1. NOTE: Test frequency and range defined in table 4. Cell 1 and Cell 27 are used.4. f20 is the default test frequency. Cell 1 and Cell 24 are used.2-2. f1 is the default test frequency.4.2-1. For FDD and TDD inter-RAT cell environment with multi HRPD cells.1.4. f17 is the default test frequency. f8 is the default test frequency.1.4. For FDD and TDD inter-RAT cell environment with (UTRA FDD or UTRA TDD) and GERAN. For FDD and TDD inter-RAT cell environment with multi UTRA FDD or UTRA TDD cells. Cell 12. f11 is the default test frequency.6 WLAN Inter-RAT network scenarios For FDD and TDD inter-RAT cell environment with WLAN.4 3GPP Inter-RAT network scenarios For FDD and TDD basic inter-RAT cell environment with UTRA FDD or UTRA TDD. 4. E-UTRA single mode multi cell network scenarios defined in clause 4. For FDD and TDD inter-RAT cell environment with GERAN. Cell 1. Default parameters for simulated cells are specified in table 4. Cell 1. 4.521-1 test cases.2. Cell 10 and Cell 31 are used. Cell 20 and Cell 21 are used.4. For CDMA2000 HRPD cells.4.2-1A and table 4.4.2 are combined with the dual mode scenarios defined in this clause when additional intra or inter-frequency cells are used.508 V12. For FDD or TDD basic inter-band cell environment. 4. For FDD and TDD inter-RAT cell environment with 1xRTT.1 (2014-12) E-UTRA single mode multi cell network scenarios For FDD or TDD basic intra-frequency multi cell environment.4.2-1 do not apply to 36. Cell 16 and Cell 17 are used. Cell 1 and Cell 7.4. For FDD or TDD multi tracking area inter-frequency multi cell environment. Test frequencies and simulated cells are defined in table 4. Cell 1. Cell 1. Cell 3 and Cell 6 are used. Cell 1. For FDD and TDD inter-RAT cell environment with multi 1xRTT cells. Cell 1.4. For UTRA cells. For WLAN cells. For GERAN cells. Cell 1 and Cell 15. Cell 1 and Cell 25. Cell 5 and Cell 24 are used.1. Cell 1 and Cell 19.Release 12 4. Cell 28. Cell 2 and Cell 4 are used.2 Simulated cells NOTE: For NAS test cases see subclause 6. Cell 1 and Cell 15 are used. For FDD or TDD basic inter-frequency multi cell environment.1.4. Cell 29 and Cell 30 are used.3 E-UTRA dual mode multi cell network scenarios For FDD and TDD basic multi cell environment. Cell 26 are used. f14 is the default test frequency. 3GPP . In addition.2 65 3GPP TS 36. For FDD and TDD multi PLMN multi cell environment. Cell 1 and Cell 11 are used. For FDD and TDD inter-RAT cell environment with multi GERAN cells.3.5 3GPP2 Inter-RAT network scenarios For FDD and TDD inter-RAT cell environment with HRPD. For FDD or TDD multi tracking area intra-frequency multi cell environment. Cell 1 and Cell 10 are used. For E-UTRA cells. For FDD or TDD multi PLMN inter-frequency multi cell environment. Cell 13 and Cell 14 are used. 4. Cell 1 and Cell 5 are used. Cell 8 and Cell 9 is used. For CDMA 2000 1xRTT cells. 4. Cell 1 and Cell 19 are used. Cell 1 and Cell 23 are used.4.1. 3 to 4. simultaneous co-existence of Cell 2 with Cell 11 is not allowed. For signalling test. For RRM test with intra-band contiguous CA. with the test frequencies specified in clauses 4. Note 8) Low (Note 1.3.xA for FDD and 4.1 (2014-12) Common parameters for simulated cells are specified in subclauses 4. see clause 7. both PCC and SCC are “Low”.xA for TDD For RRM test with intra-band contiguous CA. Cell 11 (Note 4) Cell 3. with the test frequencies specified in clauses 4. Cell 31 Cell 28.508 V12.1.1. Cell 7 Cell 8 Cell 9 Cell 24 Cell 25 Cell 26 CDMA2000 Operating band for CDMA2000 Cell 15.6A. Cell 29 Cell 5.1.xA for TDD without any regard to range. Cell 12. Note 5.2.4. Note 8) (Note 1) Mid (Note 1) High (Note 1) Low (Note 1) Mid (Note 2) High (Note 2) Low (Note 2) Mid (Note 3) High (Note 3) Low (Note 3) Mid f14 f15 f16 f17 f18 f19 f20 Note 1: Note 2: Note 3: Note 4: Note 5: Note 6: Note 7: Note 8: RAT Simulated cells Cell 1.4.1.2. Cell 30.1. see clause 6.1. Cell 20 1xRTT 1xRTT cells CDMA2000 Operating band for CDMA2000 High Cell 21 1xRTT 1xRTT cells CDMA2000 Operating band for CDMA2000 Low Cell 22 1xRTT 1xRTT cells WLAN Operating band for WLAN cells FFS Cell 27 For signalling test.1. Unless otherwise stated. Thus “Low”. Cell 4.1.4.2. Table 4.2-1: Definition of test frequencies and simulated cells Test frequency f1 Operating band Range E-UTRA Operating band under test f2 E-UTRA Operating band under test f3 E-UTRA Operating band under test f4 f5 E-UTRA E-UTRA Operating band under test Operating band for inter-band cells f6 E-UTRA Operating band for inter-band cells f7 E-UTRA Operating band for inter-band cells f8 UTRA Operating band for UTRA cells f9 UTRA Operating band for UTRA cells f10 UTRA Operating band for UTRA cells f11 GERAN Operating band for GERAN cells f12 GERAN Operating band for GERAN cells f13 GERAN Operating band for GERAN cells Mid (Note 1. both PCC and SCC are “Mid”.xA for FDD and 4.1. Cell 23 Cell 6.3. 3GPP . For RRM test with intra-band non-contiguous CA.xA for TDD For RRM test with intra-band contiguous CA. test point with maximum Wgap is chosen. Cell 16 HRPD HRPD cells CDMA2000 Operating band for CDMA2000 High Cell 17 HRPD HRPD cells CDMA2000 Operating band for CDMA2000 Low Cell 18 HRPD HRPD cells CDMA2000 Operating band for CDMA2000 Mid Cell 19.xA for TDD.3.2. For signalling test.2.2.3.1.108 [5] clause 5. Note 6.3.4.3.1.3. Cell 2. with the test frequencies specified in clauses 4. See TS 34.1. the test frequencies are specified in clauses 4.xA for FDD and 4. Cell 13 Cell 14 Cell 10. Note 8) High (Note 1.1.4.4.1. Other cell specific parameters are specified in subclause 4.xA for FDD and 4.3. “Mid” and “High” information in this table does not apply.Release 12 66 3GPP TS 36. both PCC and SCC are “High”.3.1. see clause 6.2. For RRM test.7. Note 7.3. 3). TAI-3 1 TAI-3 Cell 28 Cell 13. Note 3: Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card (subclause 4.Release 12 67 3GPP TS 36. TAI-5 004 31 1 TAI-5 32769 1 Cell 30 Cell 31 TAI-2 (Note 3) 2 TAI-2 32769 1 Note 1: The value(s) in the column TA# list indicates TAI(s) included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell.4.003 Cell 4 TAI-1 1 TAI-1 subclause 2.2-1A: Default E-UTRA parameters for 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 Cell 31 E-UTRAN Cell Identifier eNB Identifier '0000 0000 0000 0000 0001'B '0000 0000 0000 0000 0001'B '0000 0000 0000 0000 0010'B '0000 0000 0000 0000 0011'B '0000 0000 0000 0000 0100'B '0000 0000 0000 0000 0101'B '0000 0000 0000 0000 0110'B '0000 0000 0000 0000 0010'B '0000 0000 0000 0000 0100'B '0000 0000 0000 0000 0111'B '0000 0000 0000 0000 0110'B '0000 0000 0000 0000 0010'B '0000 0000 0000 0000 0100'B '0000 0000 0000 0000 0111'B '0000 0000 0000 0000 0110'B Physical layer cell identity rootSequenceIndex FDD rootSequenceIndex TDD Cell Identity '0000 0000'B 0 22 0 '0000 0010'B 2 86 8 '0000 0011'B 3 22 0 '0000 0100'B 4 150 16 '0000 0110'B 6 22 0 '0000 1010'B 10 22 0 '0000 1011'B 11 214 24 '0000 1100'B 12 86 8 '0000 1101'B 13 86 8 '0000 1110'B 14 22 0 '0001 0111'B 23 150 16 '0001 1100'B 28 86 8 '0001 1101'B 29 86 8 '0001 1110'B 30 22 0 '0001 1111'B 31 214 24 Table 4. Cell 10 TAI-1 1 TAI-1 Cell 11 TAI-2 2 TAI-2 Cell 23 TAI-2 2 TAI-2 Cell 12.2-2: Default NAS parameters for simulated cells cell ID TA# Tracking Area PLMN MCC MNC (Note 3) (Note 3) (Note 3) (Note 3) (Note 3) (Note 3) (Note 3) (Note 3) 002 11 TAC TA# list (Note 1) GUTI (Note 2) MME Identifier MME Group ID MME Code 32769 1 32769 1 32769 1 32769 1 32769 1 32769 1 32769 1 32769 1 32769 1 M-TMSI Cell 1 TAI-1 1 TAI-1 Arbitrarily selected Cell 2 TAI-1 1 TAI-1 according to Cell 3 TAI-1 1 TAI-1 TS 23.9. TAI-4 003 21 1 TAI-4 32769 1 Cell 29 Cell 14.4.508 V12. Note 2: The value in the column GUTI indicates GUTI included in the response messages of the registration procedure (ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT) when the UE performs the registration procedure on a corresponding cell.4.8 Cell 6 TAI-1 1 TAI-1 [2].1 (2014-12) Table 4. 3GPP . 4. 4.E-UTRA TDD single cell scenario 3GPP . Table 4. In this clause.3). Combination 1 is the default combination which applies to the following test case scenarios: .2-4: Default 1XRTT parameters for simulated cells Cell ID Cell 19 Cell 20 Cell 21 Cell 22 Note 1: Note 2: SID NID BASE_ID Pilot PN Offset REG_ZONE MCC IMSI_11_12 Set Set according 50 1 Note Note 2 according to PIXIT 1 to PIXIT parameter parameter 200 Set Set according 100 1 Note Note 2 according to PIXIT 1 to PIXIT parameter parameter 200 Set Set according 150 2 Note Note 2 according to PIXIT 1 to PIXIT parameter parameter 200 Set Set according 200 3 Note Note 2 according to PIXIT 1 to PIXIT parameter parameter Set to the same Mobile Country Code stored in EFIMSI on the test USIM card (subclause 4.3).3 Common parameters for simulated E-UTRA cells The parameters specified in this sub clause apply to all simulated E-UTRA cells unless otherwise specified.9.4.4. 200 Table 4.2-3: Default HRPD parameters for simulated cells Cell ID Cell 15 Cell 16 Cell 17 Cell 18 Note 1: SectorID ColorCode Pilot PN Offset CountryCode Set according to PIXIT Set according to PIXIT 50 (Note 1) parameter parameter Set according to PIXIT Set according to PIXIT 100 (Note 1) parameter parameter Set according to PIXIT Set according to PIXIT 150 (Note 1) parameter parameter Set according to PIXIT Set according to PIXIT 200 (Note 1) parameter parameter Set to the same Mobile Country Code stored in EFIMSI on the test USIM card (subclause 4.3.E-UTRA FDD single cell scenario .1 (2014-12) Table 4.4.9.4.2-5: Neighbouring cell list for 1XRTT cells Cell ID Cell 19 Cell 20 Cell 21 Cell 22 Intra Frequency cell 20 cell 19 X X Inter Frequency Cells cell 22 cell 22 cell 20 cell 20 Cell 21 Cell 21 cell 19 cell 19 X X cell 22 cell 21 4.1 Common configurations of system information blocks Combinations of system information blocks The combination of system information blocks required by a test case depends on the test case scenario.3. the following combinations of system information blocks are defined.508 V12.4.1 4.1.Release 12 68 3GPP TS 36. Set to the same Mobile Network Code stored in EFIMSI on the test USIM card (subclause 4.3).9.4. 3GPP2 inter-RAT E-UTRA TDD + HRPD multi cell scenario .3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD multi cell scenario .3GPP inter-RAT E-UTRA TDD + GERAN multi cell scenario Combination 6 applies to the following test case scenarios: .E-UTRA TDD intra-band carrier aggregation component carriers cell scenario Combination 4 applies to the following test case scenarios: .Release 12 69 3GPP TS 36.E-UTRA TDD inter-frequency multi cell scenario .E-UTRA TDD + home eNB multi cell scenario Combination 8 applies to the following test case scenarios: .3GPP2 inter-RAT E-UTRA FDD + 1xRTT multi cell scenario .E-UTRA FDD ETWS single cell scenario .1 (2014-12) .E-UTRA FDD inter-band carrier aggregation component carriers cell scenario .E-UTRA FDD inter-band multi cell scenario .E-UTRA FDD inter-frequency multi cell scenario .3GPP inter-RAT E-UTRA FDD + GERAN multi cell scenario .4. Combination 7 applies to the following test case scenarios: .3GPP2 inter-RAT E-UTRA TDD + 1xRTT multi cell scenario Editor’s note: 3GPP2 Inter-RAT multi cell scenarios with E-UTRA + HRPD + 1xRTT are FFS.E-UTRA TDD ETWS single cell scenario Combination 9 applies to the following test case scenarios: 3GPP .E-UTRA TDD intra-frequency multi cell scenario with neighbouring cell related information Combination 3 applies to the following test case scenarios: .E-UTRA TDD intra-frequency multi cell scenario .E-UTRA FDD intra-band carrier aggregation component carriers cell scenario .3GPP inter-RAT E-UTRA TDD + UTRA FDD multi cell scenario Combination 5 applies to the following test case scenarios: .E-UTRA TDD inter-band multi cell scenario .E-UTRA FDD intra-frequency multi cell scenario .E-UTRA FDD and E-UTRA TDD dual mode multi cell non-roaming scenario .3GPP2 inter-RAT E-UTRA FDD + HRPD multi cell scenario .E-UTRA FDD + home eNB multi cell scenario .E-UTRA FDD and E-UTRA TDD dual mode multi cell roaming scenario Combination 2 applies to the following test case scenarios: .508 V12.E-UTRA FDD intra-frequency multi cell scenario with neighbouring cell related information .3GPP inter-RAT E-UTRA FDD + UTRA FDD multi cell scenario . E-UTRA TDD inter-frequency + 3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD + GERAN multi cell scenario Combination 11 applies to the following test case scenarios: .3GPP E-UTRA TDD + CMAS single cell scenario Combination 18 applies to the following test case scenarios: .E-UTRA TDD inter-frequency + 3GPP inter-RAT UTRA multi-cell scenario Combination 10 applies to the following test case scenarios: .3GPP E-UTRA TDD + MBMS inter-frequency multi cell scenario (non-MBMS cell broadcasting SIB15) 3GPP .3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD + home eNB multi cell scenario Combination 12 applies to the following test case scenarios: .3GPP inter-RAT E-UTRA FDD + UTRA FDD + home eNB multi cell scenario .3GPP E-UTRA FDD inter-frequency multi cell scenario + MBMS .4.E-UTRA FDD inter-frequency + GERAN cell scenario .3GPP E-UTRA FDD single cell scenario + MBMS .3GPP inter-RAT E-UTRA TDD + UTRA LCR TDD + GERAN multi cell scenario.3GPP E-UTRA FDD + MBMS inter-frequency multi cell scenario (non-MBMS cell broadcasting SIB15) .3GPP E-UTRA TDD single cell scenario + MBMS .3GPP inter-RAT E-UTRA FDD + GERAN + home eNB multi cell scenario .1 (2014-12) .3GPP E-UTRA FDD + CMAS single cell scenario . Combination 10a applies to the following test case scenarios: .3GPP E-UTRA FDD intra-frequency multi cell scenario + MBMS .3GPP E-UTRA TDD intra-frequency multi cell scenario + MBMS Combination 16 applies to the following test case scenarios: .E-UTRA FDD inter-frequency + 3GPP inter-RAT UTRA multi-cell scenario .Release 12 70 3GPP TS 36.508 V12.E-UTRA FDD inter-frequency + 3GPP inter-RAT E-UTRA FDD + UTRA FDD + GERAN multi cell scenario .E-UTRA TDD inter-frequency + GERAN cell scenario Combination 13 applies to the following test case scenarios: .3GPP E-UTRA TDD inter-frequency multi cell scenario + MBMS Combination 17 applies to the following test case scenarios: .E-UTRA TDD inter-frequency + home eNB Combination 14 applies to the following test case scenarios: .3GPP inter-RAT E-UTRA TDD + GERAN + home eNB multi cell scenario Combination 15 applies to the following test case scenarios: .E-UTRA FDD inter-frequency + home eNB .3GPP inter-RAT E-UTRA FDD + UTRA FDD + GERAN multi cell scenario . 1-1: Combinations of system information blocks Combination No.3GPP E-UTRA TDD + MBMS intra-frequency multi cell scenario (MBMS cell broadcasting SIB15) Combination 20 applies to the following test case scenarios: . Table 4.1 (2014-12) Combination 19 applies to the following test case scenarios: .4.3GPP E-UTRA TDD + MBMS inter-band multi cell scenario (MBMS cell broadcasting SIB15) Combination 21 applies to the following test case scenarios: .4.3.3GPP E-UTRA FDD + MBMS intra-frequency multi cell scenario (MBMS cell broadcasting SIB15) . 1 2 3 4 5 6 7 8 9 10 10a 11 12 13 14 15 16 17 18 19 20 21 4.1.2-1: Scheduling for combination 1 Scheduling Information No.2 SIB 2 X X X X X X X X X X X X X X X X X X X X X X SIB 3 X X X X X X X X X X X X X X X X X X X X X X SIB 4 SIB 5 System information block type SIB SIB SIB SIB SIB SIB 6 7 8 9 10 11 SIB 12 SIB 13 SIB 14 SIB 15 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Scheduling of system information blocks The scheduling configurations for combinations of system information blocks are defined in the following tables. 1 2 Periodicity [radio frames] 16 See sub clause 4.E-UTRA TDD SIMTC single cell scenario Table 4.508 V12.4.3GPP E-UTRA TDD + MBMS inter-frequency multi cell scenario (MBMS cell broadcasting SIB15) .3.4.1.4 3GPP Mapping of system information blocks SIB2 SIB3 .3GPP E-UTRA FDD + MBMS inter-band multi cell scenario (MBMS cell broadcasting SIB15) .Release 12 71 3GPP TS 36.1.E-UTRA FDD SIMTC single cell scenario .3.3.4.3GPP E-UTRA FDD + MBMS inter-frequency multi cell scenario (MBMS cell broadcasting SIB15) . 3.4.3.4.3.4.4.1.1 (2014-12) Table 4.4.4.2-6: Scheduling for combination 6 Scheduling Information No.4.4.4.3.3.4.4 Mapping of system information blocks SIB2 SIB3 SIB8 Table 4.4 See sub clause 4.2-4: Scheduling for combination 4 Scheduling Information No. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.4 Mapping of system information blocks SIB2 SIB3 SIB7 Table 4.4 Mapping of system information blocks SIB2 SIB3 SIB5 Table 4.4.4.3. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.2-2: Scheduling for combination 2 Scheduling Information No.4.3.4 Mapping of system information blocks SIB2 SIB3 SIB4 SIB9 Table 4.3.3.4.4 See sub clause 4. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.4. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.3.4 See sub clause 4.3.3.4.3.1.4 See sub clause 4.1.3.4 Mapping of system information blocks SIB2 SIB3 SIB6 Table 4.2-3: Scheduling for combination 3 Scheduling Information No.3.3.3.4 See sub clause 4.4 See sub clause 4.4. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.1.4 Mapping of system information blocks SIB2 SIB3 SIB4 Table 4.Release 12 72 3GPP TS 36.4 See sub clause 4.4.4.2-8: Scheduling for combination 8 Scheduling Information No.1.3.4.4. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.2-7: Scheduling for combination 7 Scheduling Information No.3.1.4 See sub clause 4.508 V12.4.4.1.3.3.4 See sub clause 4.4.3.4 3GPP Mapping of system information blocks SIB2 SIB3 SIB11 SIB10 . 1 2 3 Periodicity [radio frames] 16 See sub clause 4.3.2-5: Scheduling for combination 5 Scheduling Information No. 4.508 V12.4.4.4 See sub clause 4.4 Mapping of system information blocks SIB2 SIB3 SIB5 SIB7 Table 4.3.4. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.4.4 See sub clause 4.3.3.4.4.4 See sub clause 4.4.4.2-13: Scheduling for combination 13 Scheduling Information No.2-9: Scheduling for combination 9 Scheduling Information No.3. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.2-10a: Scheduling for combination 10a Scheduling Information No.4 3GPP Mapping of system information blocks SIB2 SIB3 SIB4 SIB5 .4 Mapping of system information blocks SIB2 SIB3 SIB5.4 See sub clause 4.3.4 See sub clause 4.3.4.3.2-11: Scheduling for combination 11 Scheduling Information No.3. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.4.3.4. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.4 See sub clause 4.4.4.3.4 Mapping of system information blocks SIB2 SIB3 SIB4 SIB6 SIB9 Table 4.4.1.4.3.3.1.1.3. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.4.4 Mapping of system information blocks SIB2 SIB3 SIB5.1.Release 12 73 3GPP TS 36.3.4.4.4.4.3.4 See sub clause 4. 1 2 3 4 5 Periodicity [radio frames] 16 See sub clause 4.3.4 See sub clause 4.4 See sub clause 4.1.3.1.4. SIB6 SIB7 Table 4.3.2-10: Scheduling for combination 10 Scheduling Information No.3.3.3.4 See sub clause 4.4.4 Mapping of system information blocks SIB2 SIB3 SIB6 SIB7 Table 4.1 (2014-12) Table 4.4.4 See sub clause 4.3. SIB6 Table 4.3.2-12: Scheduling for combination 12 Scheduling Information No.3.4.4 See sub clause 4. 4 See sub clause 4.3.3.4 See sub clause 4.1.4 Mapping of system information blocks SIB2 SIB3 SIB5 SIB15 Table 4.4 See sub clause 4.4 See sub clause 4.4.3.4.4.3.2-16: Scheduling for combination 16 Scheduling Information No.1.2-14: Scheduling for combination 14 Scheduling Information No.4 Mapping of system information blocks SIB2 SIB3 SIB5 SIB13 Table 4.4.4.3.4.1.3.1.2-19: Scheduling for combination 19 Scheduling Information No.3.3.Release 12 74 3GPP TS 36.3. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.4 Mapping of system information blocks SIB2 SIB3 SIB12 Table 4.3.4.4.4.4 See sub clause 4.3.4 See sub clause 4.4 See sub clause 4.4.3.1.3.2-17: Scheduling for combination 17 Scheduling Information No.4 See sub clause 4.4.4.3. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.4.3.4 Mapping of system information blocks SIB2 SIB3 SIB13 Table 4.4.3. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.3.4.4 See sub clause 4.3.3.3.4.4.1 (2014-12) Table 4.4.4. 1 2 3 4 5 Periodicity [radio frames] 16 See sub clause 4.4.3.4.4.508 V12.2-18: Scheduling for combination 18 Scheduling Information No.1.3.4. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.4. 1 2 3 4 Periodicity [radio frames] 16 See sub clause 4.4 See sub clause 4.4 See sub clause 4.3.4 3GPP Mapping of system information blocks SIB2 SIB3 SIB13 SIB15 .4 Mapping of system information blocks SIB2 SIB3 SIB4 SIB7 SIB9 Table 4.2-15: Scheduling for combination 15 Scheduling Information No. 1 Not present 3GPP Comment Condition .4 See sub clause 4.4.2.3.3.3.3. PHICH-Config-DEFAULT Comment Condition See subclause 4.4.2 Common contents of system information messages - MasterInformationBlock The MasterInformationBlock includes the system information transmitted on BCH. 1 2 3 Periodicity [radio frames] 16 See sub clause 4.331 clause 6.3.4.6.3 A valid value as defined in TS 36.4 See sub clause 4.4. Table 4. 1 2 3 4 5 Periodicity [radio frames] 16 See sub clause 4.Release 12 75 3GPP TS 36.3.4.4.1.2-21: Scheduling for combination 21 Scheduling Information No.4 See sub clause 4.4.4.4.4.2 Information Element MasterInformationBlock ::= SEQUENCE { dl-Bandwidth phich-Config SEQUENCE {} systemFrameNumber Value/remark Downlink system bandwidth under test.4 See sub clause 4.1.2-20: Scheduling for combination 20 Scheduling Information No.331 [17] '0000 0000 00'B spare } - SystemInformation The SystemInformation message is used to convey one or more System Information Blocks.2-2: SystemInformation Derivation Path: 36. Table 4.3.2.4..4 Mapping of system information blocks SIB2 SIB3 SIB5 SIB13 SIB15 Table 4.3.3.3.331 clause 6.4 Mapping of system information blocks SIB2 SIB3 SIB14 4.4.2 Information Element SystemInformation ::= SEQUENCE { criticalExtensions CHOICE { systemInformation-r8 SEQUENCE { sib-TypeAndInfo SEQUENCE (SIZE (1. All the SIBs included are transmitted with the same periodicity.3.maxSIB)) OF CHOICE {} criticalExtensionsFuture SEQUENCE {} } } } Value/remark See subclause 4.2-1: MasterInformationBlock Derivation Path: 36.508 V12.4.3.1 (2014-12) Table 4. Not present QBASED -20 (-20dB) Not present Not present } } } Condition Explanation 3GPP .2-2 For NAS test cases.Release 12 - 76 3GPP TS 36.4.3 FDD TDD To allow sufficient number of retransmissions.6)) OF SEQUENCE { plmn-Identity[1] SEQUENCE { mcc SEQUENCE (SIZE (3)) OF MCCNMC-Digit mnc SEQUENCE (SIZE (2.3.2.. 0 Not present True Support IMS emergency call in limited service mode.2..2. notReserved See table 4.2.6.2-1.maxSI-Message)) OF SEQUENCE {} tdd-Config SEQUENCE {} tdd-Config SEQUENCE {} si-WindowLength systemInfoValueTag nonCriticalExtension SEQUENCE { lateNonCriticalExtension nonCriticalExtension SEQUENCE { ims-EmergencySupport-r9 cellSelectionInfo-v920 SEQUENCE {} cellSelectionInfo-v920 SEQUENCE { q-QualMin-r9 q-QualMinOffset-r9 } nonCriticalExtension Value/remark Comment Condition 1 entry See table 4.3. see table 6.1 (2014-12) SystemInformationBlockType1 SystemInformationBlockType1 contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information.4.2-2 See table 4. Cell ID for the simulated cell notBarred notAllowed FALSE Not present -70 (-140 dBm) -106 dBm Not present Not present Operating band under test.1 Not present TDD-ConfigDEFAULT ms20 For RF/RRM test cases For signalling test cases See subclause 4. see table 6.3.4. For NAS test cases.508 V12.3.3..4.2-2 For NAS test cases. Table 4. See subclause 4.2-3: SystemInformationBlockType1 Derivation Path: 36.3)) OF MCCNMC-Digit } cellReservedForOperatorUse[1] } trackingAreaCode cellIdentity cellBarred intraFreqReselection csg-Indication csg-Identity } cellSelectionInfo SEQUENCE { q-RxLevMin q-RxLevMinOffset } p-Max freqBandIndicator schedulingInfoList SEQUENCE (SIZE (1.4. see table 6.331 clause 6.2-1.2-1.4.2 Information Element SystemInformationBlockType1 ::= SEQUENCE { cellAccessRelatedInfo SEQUENCE { plmn-IdentityList SEQUENCE (SIZE (1. 3 Common contents of system information blocks - SystemInformationBlockType2 The IE SystemInformationBlockType2 contains radio resource configuration information that is common for all UEs.4.maxMBSFN-Allocations)) OF SEQUENCE { radioframeAllocationPeriod radioframeAllocationOffset subframeAllocation CHOICE{ oneFrame } } timeAlignmentTimerCommon Value/remark Not present RadioResourceCo nfigCommonSIBDEFAULT Comment See subclause 4. Table 4.4.3-1: SystemInformationBlockType2 Derivation Path: 36.1 (2014-12) FDD cell environment TDD cell environment This condition applies to Quality based cell (re)selection signalling test cases. } Condition MBMS FDD TDD Condition Explanation MBMS cell environment FDD cell environment TDD cell environment 3GPP .3.6.3 ms1000 ms1000 ms1000 n1 ms10000 n1 Typical value in real network Typical value in real network Typical value in real network Not present Not Present 1 (NS_01) Default UL EARFCN applies Typical value in real network A-MPR doesn’t apply by default.2.101 table 6.331 clause 6. Not present MBMS n4 1 0 FDD TDD ‘100000’ B ‘000010’ B FDD TDD sf750 ‘sf750’ is applicable to the widest range of mobility (up to about 360km/h).4.Release 12 77 FDD TDD QBASED 3GPP TS 36.1 Information Element SystemInformationBlockType2 ::= SEQUENCE { ac-BarringInfo SEQUENCE {} radioResourceConfigCommon SEQUENCE {} ue-TimersAndConstants SEQUENCE { t300 t301 t310 n310 t311 n311 } freqInfo SEQUENCE { ul-CarrierFreq ul-Bandwidth additionalSpectrumEmission } mbsfn-SubframeConfigList mbsfn-SubframeConfigList SEQUENCE (SIZE (1.4-1.3.. See TS 36. 4.3.508 V12. 3-2: SystemInformationBlockType3 Derivation Path: 36.3. At least two cellspecific antenna ports are used in all neighbouring cells.331 clause 6. All neighCells with port1 Typical value in real network Not present Not present Not present Not present -20 (-20dB) Not present 3 (3dB) } } Condition Explanation 3GPP QBASED QBASED . interfrequency and/or inter-RAT cell re-selection (i.1 (2014-12) SystemInformationBlockType3 The IE SystemInformationBlockType3 contains cell re-selection information common for intra-frequency. For RF/RRM test cases For signalling test cases The downlink bandwidth of the serving cell applies.1 Information Element SystemInformationBlockType3 ::= SEQUENCE { cellReselectionInfoCommon SEQUENCE { q-Hyst speedStateReselectionPars SEQUENCE {} } cellReselectionServingFreqInfo SEQUENCE { s-NonIntraSearch threshServingLow cellReselectionPriority } intraFreqCellReselectionInfo SEQUENCE { q-RxLevMin Value/remark dB0 Not present Not present 0 (0 dB) 4 -70 (-140 dBm) p-Max s-IntraSearch allowedMeasBandwidth Not present Not present Not present presenceAntennaPort1 FALSE TRUE t-ReselectionEUTRA t-ReselectionEUTRA-SF } lateNonCriticalExtension { s-IntraSearch-v920 SEQUENCE {} s-NonIntraSearch-v920 SEQUENCE {} q-QualMin-r9 threshServingLowQ-r9 Condition To reduce interference between intrafrequency multiple cells -106 dBm neighCellConfig Comment '01'B (No MBSFN subframes are present in all neighbour cells) 0 Typical value in real network A middle value in the range has been selected.4.4.508 V12. applicable for more than one type of cell re-selection but not necessarily all) as well as intra-frequency cell re-selection information other than neighbouring cell related. Table 4.3.e. MBSFN doesn’t apply by default.Release 12 - 78 3GPP TS 36. 3. } Condition NonCSG CSG - Explanation SIB4 transmitted on a non-CSG cell SIB4 transmitted on a CSG cell SystemInformationBlockType5 The IE SystemInformationBlockType5 contains information relevant only for inter-frequency cell re-selection i.3.e. see table 6. see table 6.1.508 V12.maxCellIntra)) OF SEQUENCE {} intraFreqBlackCellList SEQUENCE (SIZE (1. The IE includes cells with specific re-selection parameters as well as blacklisted cells.1.3. Not required unless Blacklisted cell list configuration is tested..2-3.1 Information Element SystemInformationBlockType4 ::= SEQUENCE { intraFreqNeighCellList SEQUENCE (SIZE (1. When Qoffset configuration is tested. The IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters.Release 12 79 QBASED All neighCells with port1 - 3GPP TS 36.331 clause 6. 3GPP .maxCellBlack)) OF SEQUENCE {} csg-PhysCellIdRange SEQUENCE {} csg-PhysCellIdRange SEQUENCE { start range Value/remark Not present Not present Comment Not required unless Qoffset configuration is tested.4. Not present Physical Cell ID of the cell on which this SIB is transmitted Not present } Condition NonCSG CSG The UE shall apply value 1 in case the field is absent.4. in which case only the physical cell identity value indicated by start applies. When Blacklisted cell list configuration is tested.4.3-3: SystemInformationBlockType4 Derivation Path: 36.1-1. information about other E-UTRA frequencies and inter-frequency neighbouring cells relevant for cell re-selection.3.. Table 4.3.1-1.1 (2014-12) See the definition below table 4. Used for all neighbouring cells with at least two cell-specific antenna ports SystemInformationBlockType4 The IE SystemInformationBlockType4 contains neighbouring cell related information relevant only for intra-frequency cell re-selection. 508 V12.3.Release 12 80 3GPP TS 36.3-4: SystemInformationBlockType5 3GPP .4.4.1 (2014-12) Table 4. maxFreq)) OF SEQUENCE { dl-CarrierFreq[n] q-RxLevMin[n] 81 3GPP TS 36.3.2-1. Not required unless Qoffset configuration is tested.331 clause 6.4. MBSFN doesn’t apply by default. For NAS test cases when cells are on same PLMN. see table 6..1.2-1.1.1 Information Element SystemInformationBlockType5 ::= SEQUENCE { interFreqCarrierFreqList SEQUENCE (SIZE (1.Release 12 Derivation Path: 36.3. For NAS test cases when cells are on same PLMN. All neighCells with port1 .4.maxCellBlack)) OF SEQUENCE {} Not present 3GPP Condition For RF/RRM test cases For signalling test cases Typical value in real network Not required unless speeddependent cell reselection is tested. This value should be higher than threshServingLow of the serving cell to avoid ping-pong with lower priority cells. For Signalling test cases except NAS. Not required unless Blacklisted cell list configuration is tested.3.2.3.. Channelbandwidthdependent parameter At least two cellspecific antenna ports are used in all neighbouring cells.508 V12.3.4 presenceAntennaPort1[n] FALSE TRUE cellReselectionPriority[n] 4 neighCellConfig[n] '01'B (No MBSFN subframes are present in all neighbour cells) dB0 q-OffsetFreq[n] interFreqNeighCellList[n] SEQUENCE (SIZE (1.1 (2014-12) Value/remark Comment The same number of entries as the configured inter-freq carriers.2.3. see table 6. -65 (-130 dBm) n denotes the index of the entry -106 dBm p-Max[n] t-ReselectionEUTRA[n] Not present 0 t-ReselectionEUTRA-SF[n] Not present threshX-High[n] 2 (4 dB) threshX-Low[n] allowedMeasBandwidth[n] 1 (2 dB) See subclause 4. The same priority as the one used for serving cell in SIB 3.2-1.3.maxCellInter)) OF SEQUENCE {} Not present interFreqBlackCellList[n] SEQUENCE (SIZE (1. see table 6. Downlink EARFCN under test For Signalling test cases except NAS.. Qoffset doesn’t apply by default. see table 6.3.2-1. Release 12 82 q-QualMin-r9[n] threshX-Q-r9[n] SEQUENCE {} threshX-Q-r9[n] SEQUENCE { threshX-HighQ-r9 threshX-LowQ-r9 } 3GPP TS 36.1 (2014-12) Not present -20 (-20dB) Not present QBASED 5 (5dB) 5 (5dB) } } Condition QBASED All neighCells with port1 QBASED Explanation See the definition below table 4.2-3.3. Used for all neighbouring cells with at least two cell-specific antenna ports 3GPP .508 V12.4.4. 4.1 (2014-12) SystemInformationBlockType6 The IE SystemInformationBlockType6 contains information relevant only for inter-RAT cell re-selection i.4.3.Release 12 - 83 3GPP TS 36.3-5: SystemInformationBlockType6 3GPP .e. Table 4. The IE includes cell re-selection parameters common for a frequency.508 V12. information about UTRA frequencies and UTRA neighbouring cells relevant for cell re-selection. 1.508 V12..3-1 3 2 (4 dB) 1 (2 dB) -40 (-79 dBm) p-MaxUTRA[n] 21 (21 dBm) q-QualMin[n] -24 (-24 dB) threshX-Q-r9[n] SEQUENCE {} threshX-Q-r9[n] SEQUENCE { Not present carrierFreq[n] threshX-HighQ-r9 threshX-LowQ-r9 } } carrierFreqListUTRA-TDD SEQUENCE (SIZE (1.3. table 6.3.1. QBASED 9 (9dB) 9 (9dB) Not present cellReselectionPriority[n] threshX-High[n] threshX-Low[n] q-RxLevMin[n] The same number of entries as the configured UTRA TDD carriers For Signalling test cases.1 Information Element SystemInformationBlockType6 ::= SEQUENCE { carrierFreqListUTRA-FDD SEQUENCE (SIZE (1. table 6.3-1 Downlink UARFCN under test For Signalling test cases. The same value as defined in TS 34.1.6a Typical value in real network } Condition UTRA-FDD UTRA-TDD .1.maxUTRA-TDD-Carrier)) OF SEQUENCE {} carrierFreqListUTRA-TDD SEQUENCE (SIZE (1.108 [5]. see table 6.1..1 (2014-12) Value/remark Not present cellReselectionPriority[n] threshX-High[n] threshX-Low[n] q-RxLevMin[n] The same number of entries as the configured UTRA FDD carriers For Signalling test cases.1.1.maxUTRA-TDD-Carrier)) OF SEQUENCE { Condition UTRA-TDD n denotes the index of the entry UTRA-FDD The same value as defined in TS 34.maxUTRA-FDD-Carrier)) OF SEQUENCE { 84 3GPP TS 36.3.3-1 3 2 (4 dB) 1 (2 dB) -41 (-81 dBm) p-MaxUTRA[n] 21 (21 dBm) carrierFreq[n] Comment } t-ReselectionUTRA 0 t-ReselectionUTRA-SF Not present Explanation 3GPP n denotes the index of the entry The same value as defined in TS 34.1. table 6. table 6.1. see table 6.108 [5].1.. table 6.108 [5].6a The same value as defined in TS 34. see table 6.331 clause 6.3-1 Downlink UARFCN under test For Signalling test cases.1.108 [5]..maxUTRA-FDD-Carrier)) OF SEQUENCE {} carrierFreqListUTRA-FDD SEQUENCE (SIZE (1. see table 6. The same value as defined in TS 34.108 [5].3.3.1.Release 12 Derivation Path: 36.4. 3.e.1 Information Element SystemInformationBlockType7 ::= SEQUENCE { t-ReselectionGERAN t-ReselectionGERAN-SF carrierFreqsInfoListSEQUENCE (SIZE (1.1.3-6: SystemInformationBlockType7 Derivation Path: 36. For RRM test cases.2.1.4-1 2 ‘01000000'B 2 0 2 2 } } 3GPP NCC=1 permitted Condition .1-1 For Signalling test cases.2. The IE includes cell re-selection parameters for each frequency.3.4.3.2.2.508 V12. see table 6.1 (2014-12) UTRA FDD cell environment UTRA TDD cell environment See the definition below table 4.4-1 Comment n denotes the index of the entry Set the corresponding starting ARFCN of the GERAN cells under test. Table 4. Editor’s note: Need for condition ‘UTRA-FDD-TDD’ where both UTRA FDD cell and UTRA TDD cell exist simultaneously is FFS. see table 7.1-1 For Signalling test cases.4-1 Set according to the band used for GERAN cells under test Set the corresponding ARFCN of GERAN cells under test For RRM test cases. see table 6.4.3.331 clause 6. - SystemInformationBlockType7 The IE SystemInformationBlockType7 contains information relevant only for inter-RAT cell re-selection i.1-1 For Signalling test cases.maxGNFG)) OF SEQUENCE { carrierFreqs [n] SEQUENCE { startingARFCN[n] bandIndicator[n] followingARFCNs[n] CHOICE { explicitListOfARFCNs[n] } } commonInfo[n] SEQUENCE { cellReselectionPriority[n] ncc-Permitted[n] q-RxLevMin[n] p-MaxGERAN[n] threshX-High[n] threshX-Low[n] } Value/remark 0 Not present The same number of entries as the configured GERAN carriers For RRM test cases. see table 7.2..2.2-3.Release 12 85 UTRA-FDD UTRA-TDD QBASED 3GPP TS 36. information about GERAN frequencies relevant for cell re-selection. see table 6.3.1. see table 7.4.3. SystemInformationBlockType8 The IE SystemInformationBlockType8 contains information relevant only for inter-RAT cell re-selection i.3.3-7: SystemInformationBlockType8 3GPP .508 V12.Release 12 86 3GPP TS 36. Table 4.4.e.1 (2014-12) . The IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters.4. information about CDMA2000 frequencies and CDMA2000 neighbouring cells relevant for cell re-selection. 63) 1 entry Operating band class under test The same number of entries as the configured CDMA2000 HRPD frequencies For Signalling test cases.3. spare5. spare1.331 and calculated by the SS 5 Not present 1XRTT HRPD FALSE Not present Not present 1 entry Operating band class under test. spare11.331 clause 6. bc15.maxCDMA -BandClass)) OF SEQUENCE { bandClass cellReselectionPriority threshX-High threshX-Low } neighCellList SEQUENCE (SIZE (1. spare7. spare4. spare6. see table 6. spare10. spare9. bc11. bc1.} INTEGER (0. bc10. spare10. spare1.1 Information Element SystemInformationBlockType8 ::= SEQUENCE { systemTimeInfo SEQUENCE { cdma-EUTRA-Synchronisation cdma-SystemTime CHOICE { synchronousSystemTime } } searchWindowSize parametersHRPD SEQUENCE {} parametersHRPD SEQUENCE { preRegistrationInfoHRPD SEQUENCE { preRegistrationAllowed preRegistrationZoneId secondaryPreRegistrationZoneIdList } cellReselectionParametersHRPD SEQUENCE { bandClassList SEQUENCE (SIZE (1... spare14.16)) OF SEQUENCE { arfcn[n] 87 3GPP TS 36. spare13.5-1 ARFCN of the CDMA2000 HRPD frequency 3GPP ENUMERATED {bc0. bc14. spare7. bc13.. spare14.... 1 30(-30) 32(-32) ENUMERATED {bc0. bc2. spare12. bc10. bc5. spare3. bc12. spare4.3. bc15. spare3. bc8. bc11. bc14. bc6. bc16.2047) . bc8. bc6. bc1. spare12.1 (2014-12) Value/remark Comment Condition TRUE A valid value as per TS 36. bc13.. spare11. spare9.} n denotes the index of the entry INTEGER (0. spare8.4. bc17..508 V12. . spare2. bc4.63) INTEGER (0. . bc16. bc9. bc3. bc7. spare6. bc17.Release 12 Derivation Path: 36. bc9. spare13.. spare2. bc2. spare5. bc12. bc5. bc4.1.16)) OF SEQUENCE { bandClass neighCellsPerFreqList SEQUENCE (SIZE (1. spare8.. bc3. bc7. 1. see table 6.Release 12 88 For Signalling test cases.508 V12.1 (2014-12) .4.3.5-1 3GPP 3GPP TS 36. spare14... spare4. bc9. bc2. spare9. spare3. spare6. bc16. spare11. spare13. spare2.Release 12 physCellIdList[n] SEQUENCE (SIZE (1. bc12. bc17. bc11.. spare13. bc4. bc7. spare5.1 (2014-12) Physical Cell ID List of the CDMA2000 HRPD frequency For Signalling test cases.63) 1 entry Operating band class under test The same number of entries as the configured CDMA2000 1xRTT frequencies For Signalling test cases. spare2.. see table 6. . bc2... bc4.3. spare9. bc17.7) Not present A valid value.16)) OF SEQUENCE { arfcn[n] 89 3GPP TS 36.16)) OF SEQUENCE { bandClass neighCellsPerFreqList SEQUENCE (SIZE (1.1. spare4.6-1 3GPP ENUMERATED {bc0.. bc11.508 V12. bc6. spare1. bc12.1.16)) OF {INTEGER (0. bc1. bc3. spare10..maxPNOffset) 0 Not Present INTEGER (0.. spare11. see table 6. spare14. bc8. . spare8. spare10. bc7. bc1.4. spare6. spare12.. bc6. bc16. spare8. bc5. bc10. bc15.5-1 INTEGER (0. bc5. bc13. bc15. bc9. spare5. spare1.maxCDMA -BandClass)) OF SEQUENCE { bandClass cellReselectionPriority threshX-High threshX-Low } neighCellList SEQUENCE (SIZE (1.3. spare3.} INTEGER (0. spare7. bc14. bc3.6-1 ARFCN of the CDMA2000 1xRTT frequency For Signalling test cases.. bc10.1. see table 6. spare12.maxPNOffset) } } } t-ReselectionCDMA2000 t-ReselectionCDMA2000-SF } } parameters1XRTT SEQUENCE {} parameters1XRTT SEQUENCE { csfb-RegistrationParam1XRTT SEQUENCE { longCodeState1XRTT cellReselectionParameters1XRTT SEQUENCE { bandClassList SEQUENCE (SIZE (1. bc13. calculated and updated by the SS HRPD 1XRTT BIT STRING (SIZE (42)) OPTIONAL 1 entry Operating band class under test 0 30(-30) 32(-32) ENUMERATED {bc0.3.} n denotes the index of the entry INTEGER (0.... bc8. spare7. bc14.2047) .63) INTEGER (0. 7) } } } Condition HRPD 1XRTT Explanation CDMA2000 HRPD cell environment CDMA2000 1XRTT cell environment Editor’s note: Need for condition ‘HRPD-1XRTT’ where both CDMA2000 HRPD cell and CDMA2000 1xRTT cell exist simultaneously is FFS.maxPNOffset) } } } t-ReselectionCDMA2000 t-ReselectionCDMA2000-SF 3GPP TS 36. - SystemInformationBlockType9 The IE SystemInformationBlockType9 contains a home eNB name (HNB Name)..508 V12.Release 12 90 physCellIdList[n] SEQUENCE (SIZE (1.3..4..1 Information Element SystemInformationBlockType9 ::= SEQUENCE { hnb-Name } - Value/remark “3gppTest” SystemInformationBlockType10 The IE SystemInformationBlockType10 contains an ETWS primary notification.3-8: SystemInformationBlockType9 Derivation Path: 36.1 (2014-12) Physical Cell ID List of the CDMA2000 1xRTT frequency For Signalling test cases. 3GPP Comment Condition .6-1 INTEGER (0.1.maxPNOffset) 0 Not Present INTEGER (0.3. see table 6..3. Table 4.16)) OF {INTEGER (0.331 clause 6.4. For each update. '11 0000 0000'B Activate emergency user alert. incremented by one.Popup (1 bit) Octet 1 bit 4 Value/remark . Activate Popup.Emergency User Alert (1 bit) Octet 1 bit 5 ~ Octet 2 bit 4 Octet 1 bit 5 .1 Information Element SystemInformationBlockType10 ::= SEQUENCE { messageIdentifier '0001 0001 0000 0010'B serialNumber .Update Number (4 bit) Octet 2 bit 3 ~ 0 warningType .Padding (7 bit) warningSecurityInfo } Octet 2 bit 6 ~ bit 0 Not present 3GPP Comment ETWS message identifier for earthquake and tsunami message [see TS 23.3-9: SystemInformationBlockType10 Derivation Path: 36. Activate emergency user alert.4.331 clause 6.1 (2014-12) Table 4.Geographical Scope (2 bit) '0011 0000 0000 0000'B Octet 1 bit 7 ~ 6 .Emergency User Alert (1 bit) Octet 1 bit 0 . Activate popup. [see TS 23.3.Release 12 91 3GPP TS 36.Popup (1 bit) Octet 2 bit 7 . [see TS 23.Message Code (10 bit) .Warning Type Value (7 bit) '0000 0101 1000 0000'B Octet 1 bit 7 ~ 1 .041] Cell wide.3.4.508 V12.041] '000 0000'B Condition .041] Earthquake and Tsunami. Table 4.Update Number (4 bit) Octet 2 bit 3 ~ 0 warningMessageSegmentType warningMessageSegmentNumber warningMessageSegment notLastSegment 0 Octetstring of N dataCodingScheme Bitstring (8) ID of the alphabet/coding and the applied language [see TS 23. [see TS 23.Popup (1 bit) Octet 1 bit 4 .3.041] serialNumber .1 (2014-12) SystemInformationBlockType11 The IE SystemInformationBlockType11 contains an ETWS secondary notification.Release 12 - 92 3GPP TS 36.041] where N ≥ 1 and less than 1246. For each update.041] Condition .508 V12. '11 0000 0000'B Activate emergency user alert.4.Geographical Scope (2 bit) '0011 0000 0000 0000'B Octet 1 bit 7 ~ 6 .4. Activate popup. incremented by one.3. [see TS 23.Emergency User Alert (1 bit) Octet 1 bit 5 ~ Octet 2 bit 4 Octet 1 bit 5 .041] } 3GPP Cell wide.Message Code (10 bit) .3-10: SystemInformationBlockType11 (1st Segment) Derivation Path: 36.1 Information Element SystemInformationBlockType11 ::= SEQUENCE { messageIdentifier Value/remark Comment '0001 0001 0000 0010'B ETWS message identifier for earthquake and tsunami message [see TS 23.331 clause 6. incremented by one. [see TS 23.508 V12.Message Code (10 bit) .Update Number (4 bit) Octet 2 bit 3 ~ 0 warningMessageSegmentType warningMessageSegmentNumber warningMessageSegment notLastSegment 1 Octetstring of N dataCodingScheme Not present Condition Cell wide.Popup (1 bit) Octet 1 bit 4 .1 (2014-12) Table 4.331 clause 6.3.3-12: SystemInformationBlockType11 (3rd Segment) Derivation Path: 36.Update Number (4 bit) Octet 2 bit 3 ~ 0 warningMessageSegmentType warningMessageSegmentNumber warningMessageSegment lastSegment 2 Octetstring of N dataCodingScheme Not present } 3GPP Cell wide.3.041] where N ≥ 1 and less than 1246.4.Geographical Scope (2 bit) '0011 0000 0000 0000'B Octet 1 bit 7 ~ 6 .1 Information Element SystemInformationBlockType11 ::= SEQUENCE { messageIdentifier Value/remark Comment '0001 0001 0000 0010'B ETWS message identifier for earthquake and tsunami message [see TS 23. [see TS 23.331 clause 6. For each update.4. [see TS 23.Geographical Scope (2 bit) '0011 0000 0000 0000'B Octet 1 bit 7 ~ 6 . incremented by one.041] Condition .3-11: SystemInformationBlockType11 (2nd Segment) Derivation Path: 36.Popup (1 bit) Octet 1 bit 4 .041] } Table 4. [see TS 23.3.Release 12 93 3GPP TS 36.1 Information Element SystemInformationBlockType11 ::= SEQUENCE { messageIdentifier Value/remark Comment '0001 0001 0000 0010'B ETWS message identifier for earthquake and tsunami message [see TS 23. Activate popup.3. '11 0000 0000'B Activate emergency user alert.Emergency User Alert (1 bit) Octet 1 bit 5 ~ Octet 2 bit 4 Octet 1 bit 5 .041] where N ≥ 1 and less than 1246.Message Code (10 bit) . '11 0000 0000'B Activate emergency user alert. Activate popup.Emergency User Alert (1 bit) Octet 1 bit 5 ~ Octet 2 bit 4 Octet 1 bit 5 .041] serialNumber .041] serialNumber .4. For each update. 1 (2014-12) SystemInformationBlockType12 The IE SystemInformationBlockType12contains an CMAS notification.1 Information Element SystemInformationBlockType11 ::= SEQUENCE { messageIdentifier-r9 Value/remark Comment '0001 0001 0001 0010'B CMAS CBS Message Identifier for CMAS Presidential Level Alerts (see TS 23.331 clause 6. (see TS 23. 9] } Table 4.041) Condition .3.3.508 V12.4.041) serialNumber-r9 warningMessageSegmentType warningMessageSegmentNumber warningMessageSegment '0011 0000 0000 0000'B notLastSegment 1 Octetstring of N dataCodingScheme lateNonCriticalExtension Not present Not present } 3GPP where N ≥ 1 and less than 1246.4.523-3 [20] cl.4.3.041]) serialNumber-r9 warningMessageSegmentType warningMessageSegmentNumber warningMessageSegment '0011 0000 0000 0000'B notLastSegment 0 Octetstring of N dataCodingScheme -Bitstring (8) ID of the alphabet/coding and the applied language [see TS 23.331 clause 6.3. Table 4.1 Information Element SystemInformationBlockType11 ::= SEQUENCE { messageIdentifier-r9 Value/remark Comment '0001 0001 0001 0010'B CMAS CBS Message Identifier for CMAS Presidential Level Alerts (see TS 23.041) Provided as PIXITs [see TS 36.041] Not present lateNonCriticalExtension Condition where N ≥ 1 and less than 1246.3-12b: SystemInformationBlockType12 (2nd Segment) Derivation Path: 36.Release 12 - 94 3GPP TS 36. (see TS 23.3-12a: SystemInformationBlockType12 (1st Segment) Derivation Path: 36. 1 Information Element SystemInformationBlockType11 ::= SEQUENCE { messageIdentifier-r9 Value/remark Comment '0001 0001 0001 0010'B CMAS CBS Message Identifier for CMAS Presidential Level Alerts (see TS 23.maxMBSFN-Area)) OF SEQUENCE { mbsfn-AreaId-r9 non-MBSFNregionLength notificationIndicator-r9 mcch-Config-r9 SEQUENCE { mcch-RepetitionPeriod-r9 mcch-Offset-r9 mcch-ModificationPeriod-r9 sf-AllocInfo-r9 signallingMCS-r9 Value/remark Comment Condition 0 2 0 rf32 1 0 rf512 ‘100000’B ‘000010’B n2 FDD TDD FDD TDD } } notificationConfig-r9 SEQUENCE { notificationRepetitionCoeff-r9 notificationOffset-r9 notificationSF-Index-r9 n4 1 0 1 5 Subframe #1 Subframe #9 } } Condition FDD TDD Explanation FDD cell environment TDD cell environment 3GPP FDD TDD FDD TDD ..3-12c: SystemInformationBlockType12 (3rd Segment) Derivation Path: 36.4.4. (see TS 23.3.3.331 clause 6. Table 4.3.508 V12.041) } - SystemInformationBlockType13 The IE SystemInformationBlockType13 contains the information required to acquire the MBMS control information associated with one or more MBSFN areas.331 clause 6.4.1 (2014-12) Table 4.041) serialNumber-r9 warningMessageSegmentType warningMessageSegmentNumber warningMessageSegment '0011 0000 0000 0000'B lastSegment 2 Octetstring of N dataCodingScheme lateNonCriticalExtension Not present Not present Condition where N ≥ 1 and less than 1246.Release 12 95 3GPP TS 36.1 Information Element SystemInformationBlockType13 ::= SEQUENCE { mbsfn-AreaInfoList-r9 SEQUENCE (SIZE(1.3-13: SystemInformationBlockType13 Derivation Path: 36.3. .maxFreq)) OF SEQUENCE { dl-CarrierFreq-r11 mbms-SAI-List-r11[n] SEQUENCE (SIZE (1.3.3. see table 6.maxSAI-MBMS-r11)) OF { INTEGER (0. . Table 4. MBMS_inter Freq.Release 12 - 96 3GPP TS 36.. The same number of entries as the configured MBMS SAIs providing the MBMS service in the test case for the specific frequency Not present } Condition Explanation 3GPP Condition n denotes the index of the entry MBMS_intra Freq MBMS_inter Freq..3.1.331 clause 6.65535) Not present The same number of entries as the configured inter-freq carriers providing the MBMS service in the test case (including additional bands. if any) Downlink EARFCN under test.3-14: SystemInformationBlockType15 Derivation Path: 36.maxSAI-MBMS-r11)) OF { INTEGER (0.1 (2014-12) SystemInformationBlockType14 The IE SystemInformationBlockType14 contains the EAB parameters.508 V12.4. b..4.65535) MBMS_intra Freq.331 clause 6.2-1.65535) } lateNonCriticalExtension Value/remark 1 Comment 1 entry INTEGER (0..3. n denotes the index of the entry INTEGER (0..65535) } mbms-SAI-InterFreqList-r11 mbms-SAI-InterFreqList-r11[n] SEQUENCE (SIZE (1.3.3-13A: SystemInformationBlockType14 Derivation Path: 36..1 Information Element SystemInformationBlockType14-r11 ::= SEQUENCE { eab-Param-r11 CHOICE { EAB-Config-r11 ::= SEQUENCE { eab-Category-r11 eab-BarringBitmap-r11 Value/remark a '1111111111'B } } lateNonCriticalExtension Comment Condition EAB applies to all UEs in the PLMN ENUMERATED {a. c} All UE classes 0-9 BIT STRING (SIZE (10)) Not Present } - SystemInformationBlockType15 The IE SystemInformationBlockType15 contains the MBMS Service Area Identities (SAI) of the current and/ or neighbouring carrier frequencies.1 Information Element SystemInformationBlockType15 ::= SEQUENCE { mbms-SAI-IntraFreq-r11[1] SEQUENCE (SIZE (1. Table 4.4. Release 12 97 MBMS_intraFreq SIB15 transmitted for a MBMS intra-band cell environment (MBMS service only provided for intra-frequency cells). SIB15 transmitted for a MBMS inter-frequency cell environment (MBMS service provided on multiple frequencies within a band). MBMS_interFreq 4.4.3.4 3GPP TS 36.508 V12.4.1 (2014-12) Channel-bandwidth-dependent parameters in system information blocks The default values of parameters in system information blocks which depend on the channel bandwidth are defined in table 4.4.3.4-1. Table 4.4.3.4-1: Channel-bandwidth-dependent parameters Information Element SIB3 periodicity SIB4 periodicity SIB5 periodicity SIB6 periodicity SIB7 periodicity SIB8 periodicity measurement Bandwidth in SIB5 SIB9 periodicity SIB10 periodicity SIB11 periodicity SIB12 periodicity SIB13 periodicity SIB15 periodicity Channel bandwidth 5 MHz 10 MHz 32 32 1.4 MHz 64 3 MHz 64 128 128 64 128 128 128 Comment 15 MHz 32 20MHz 32 64 64 64 64 64 64 64 128 64 64 64 64 128 128 64 64 64 64 128 128 64 64 64 64 mbw6 mbw15 mbw25 mbw50 mbw75 mbw100 128 128 64 64 64 64 64 64 32 32 32 32 64 64 32 32 32 32 64 64 32 32 32 32 64 64 32 32 32 32 64 64 32 32 32 32 4.4.4 Common parameters for simulated UTRA cells The parameters specified in this subclause apply to all simulated UTRA cells unless otherwise specified. Default UTRA parameters for simulated cells are specified in table 4.4.4-1 and table 4.4.4-2. Other parameters are specified in TS 34.108 [5]. Table 4.4.4-1: Default parameters for simulated UTRA cells cell ID Cell 5 Cell 7 Cell 8 Cell 9 Primary scrambling code for FDD 100 150 200 250 3GPP Cell parameters ID for TDD 0 4 8 12 Release 12 98 3GPP TS 36.508 V12.4.1 (2014-12) Table 4.4.4-2: Default NAS parameters for simulated UTRA cells PLMN Cell 5 Cell 7 Cell 8 Cell 9 Note 1: Location Area Routing Area TMSI P-TMSI signature Identification Identification MCC MNC LA# LAC RA# RAC (Note 1) LAI-1 1 RAI-1 1 Arbitrarily selected Arbitrarily selected according to according to (Note 1) LAI-1 1 RAI-1 1 TS 23.003 TS 23.003 (Note 1) LAI-1 1 RAI-1 1 subclause 2.4 [2]. subclause 2.7 [2]. (Note 1) LAI-1 1 RAI-1 1 Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card (subclause 4.9.3). 4.4.4.1 Common contents of system information blocks for UTRA cells - System Information Block type 19 The system information block type 19 contains Inter-RAT frequency and priority information to be used in the cell. 3GPP Release 12 99 3GPP TS 36.508 V12.4.1 (2014-12) Table 4.4.4.1-1: System Information Block type 19 Derivation Path: 25.331 clause 11.3 Information Element SysInfoType19 ::= SEQUENCE { utra-PriorityInfoList SEQUENCE { utra-ServingCell SEQUENCE { priority s-PrioritySearch1 s-PrioritySearch2 threshServingLow } utran-FDD-FrequencyList SEQUENCE (SIZE(1..maxNumFDDFreqs)) OF SEQUENCE {} utran-TDD-FrequencyList SEQUENCE (SIZE(1..maxNumTDDFreqs)) OF SEQUENCE {} gsm-PriorityInfoList SEQUENCE (SIZE (1..maxNumGSMCellGroup)) OF SEQUENCE {} eutra-FrequencyAndPriorityInfoList SEQUENCE (SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE earfcn[n] measurementBandwidth[n] priority[n] qRxLevMinEUTRA[n] Value/remark 3 0 (0dB) Not present 0 (0dB) } v920NonCriticalExtensions SEQUENCE {} v920NonCriticalExtensions SEQUENCE { sysInfoType19-v920ext SEQUENCE { utra-PriorityInfoList-v920ext SEQUENCE { threshServingLow2 } eutra-FrequencyAndPriorityInfoList-v920ext (SIZE (1..maxNumEUTRAFreqs)) OF SEQUENCE { qQualMinEUTRA[n] threshXhigh2[n] threshXlow2[n] } } nonCriticalExtensions SEQUENCE {} } } Condition QBASED Condition default value is 0 Not present Not present Not present The same number of entries as the configured eutra carriers For Signalling test cases, see table 6.3.1.7-1 Downlink EARFCN under test For Signalling test cases, see table 6.3.1.7-1 Set according to EUTRA band ChBw in Table 5.6-1 of TS36.104. 4 -53 (-106 dBm) -70 (-140 dBm) threshXhigh[n] threshXlow[n] eutra-blackListedCellList[n] eutraDetection[n] Comment n denotes the index of the entry For signalling test cases For RF/RRM test cases 2 (4 dB) 1 (2 dB) Not present TRUE Not present QBASED 7 (7dB) -20 (-20dB) 5 (5dB) 5 (5dB) Not present Explanation See the definition below table 4.4.3.2-3. 3GPP default value is 0 Release 12 100 3GPP TS 36.508 V12.4.1 (2014-12) 4.4.4.2 UTRA SIB scheduling for inter EUTRA - UTRA test Table 4.4.4.2-1: UTRA SIB schedule Block MIB Type SIB_REP 8 SEG_ 1 COUNT SB1 SIB1 SIB2 SIB3 16 1 64 1 64 1 64 1 SIB4 SIB5/SIB5bis SIB6 64 1 64 4 SIB7 SIB11 SIB12 SIB18 SIB19 16 1 64 3 64 1 64 1 64 2 64 4 Table 4.4.4.2-2: UTRA SIB-repeat period Frame No / SIB_POS Block Type 0 MIB 2 SB1 4 SIB7 6 SIB6 8 MIB 10 SIB6 12 SIB6 14 SIB6 Frame No / SIB_POS Block Type 16 MIB 18 SB1 20 SIB7/SIB3 22 SIB1/SIB2 24 MIB 26 SIB12 28 SIB19 30 SIB19 Frame No / SIB_POS Block Type 32 MIB 34 SB1 36 SIB7/SIB18 38 SIB5/ SIB5bis 40 MIB 42 SIB5/ SIB5bis 44 SIB5/ SIB5bis 46 SIB5/ SIB5bis Frame No / SIB_POS Block Type 48 MIB 50 SB1 52 SIB7/SIB4 54 56 MIB 58 SIB11 60 SIB11 62 SIB11 4.4.4.3 - UTRA SIB scheduling for inter EUTRA – UTRA - GERAN test Table 4.4.4.3-1: UTRA SIB schedule Block Type SIB Rep Max. No of seg. MIB SB1 SIB1 SIB2 SIB3 SIB4 8 16 128 128 64 64 SIB5/ SIB5bis 128 1 2 1 1 1 1 4 3GPP SIB7 SIB11 SIB16 SIB18 SIB19 32 128 128 128 128 1 3 8 1 3 Release 12 101 3GPP TS 36.508 V12.4.1 (2014-12) Table 4.4.4.3-2: UTRA SIB-repeat period Frame No / SIB_POS Block Type Frame No / SIB_POS Block Type Frame No / SIB_POS Block Type Frame No / SIB_POS Block Type Frame No / SIB_POS Block Type Frame No / SIB_POS Block Type Frame No / SIB_POS Block Type Frame No / SIB_POS Block Type 0 2 4 6 8 10 12 14 MIB SB1 SB1 - MIB SIB1 SIB18 SIB2 16 18 20 22 24 26 28 30 MIB SB1 SB1 SIB7 MIB SIB3 - SIB4 32 34 36 38 40 42 44 46 MIB SB1 SB1 SIB5/ SIB5bis MIB SIB5/ SIB5bis SIB5/ SIB5bis SIB5/ SIB5bis 48 50 52 54 56 58 60 62 MIB SB1 SB1 SIB7 MIB SIB11 SIB11 SIB11 64 66 68 70 72 74 76 78 MIB SB1 SB1 SIB16 MIB SIB16 SIB16 SIB16 80 82 84 86 88 90 92 94 MIB SB1 SB1 SIB7 MIB SIB3 SIB19 SIB4 96 98 100 102 104 106 108 110 MIB SB1 SB1 SIB16 MIB SIB16 SIB16 SIB16 112 114 116 118 120 122 124 126 MIB SB1 SB1 SIB7 MIB SIB19 SIB19 - 4.4.5 Common parameters for simulated GERAN cells The parameters specified in this subclause apply to all simulated GERAN cells unless otherwise specified. See TS 51.010 [25]. The contents of SYSTEM INFORMATION TYPE 2 Quarter message specified below are identical for all GERAN cells. 3GPP Release 12 102 3GPP TS 36.508 V12.4.1 (2014-12) Table 4.4.5-1: System Information 2 Quater 3GPP Release 12 103 Derivation Path: 44.018 Table 10.5.2.33b.1 Information Element System information 2Quater L2 pseudo length PROTOCOL DISCRIMINATOR SKIP INDICATOR MESSAGE TYPE SI 2QUATER REST OCTETS BA Indicator 3G BA Indicator MP Change Mark SI2Q Index SI2Q Count Measurement_Parameters Description GPRS_Real Time Difference Description GPRS_BSIC Description GPRS_REPORT PRIORITY Description GPRS_MEASUREMENT_Parameters Description NC Measurement Parameters extension length 3G Neighbour Cell Description 3G Measurement Parameters Description GPRS_3G_MEASUREMENT Parameters Description Additions in release 5 3G Additional Measurement Parameters Description 3G ADDITIONAL MEASUREMENT Parameters Description 2 Additions in release 6 3G_CCN_ACTIVE Additions in release 7 700_REPORTING_OFFSET 810_REPORTING_OFFSET Additions in release 8 Priority and E-UTRAN Parameters Description Serving Cell Priority Parameters Description 3GPP TS 36.508 V12.4.1 (2014-12) Value/remark 1 ‘0110’B Comment RR management Protocol ‘0000’B ‘00000111’B 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present H 0 Not Present 0 Not Present H 0 H 0 0 H 1 1 Not Present Not Present Present Present Note : Values as defined from TS 45.008, section 10.4 Table 3 GERAN_PRIORITY THRESH_Priority_Search THRESH_GSM_low H_PRIO T_Reselection 3G Priority Parameters Description E-UTRAN Parameters Description E-UTRAN_CCN_ACTIVE E-UTRAN_Start E-UTRAN_Stop E-UTRAN Measurement Parameters Description GPRS E-UTRAN Measurement Parameters Description Repeated E-UTRAN Neighbour Cells { EARFCN 2 15 (always) 0 0 0 0 1 0 1 1 0 0 Not Present Present CCN not supported Not Present Not Present 1 Present Same as cell 1 This field specifies the E-UTRA Absolute Radio Frequency Channel Number as defined in 3GPP TS 36.104. 3GPP Condit ion 4. this structure needs to be specified for each cell. See C.104. EARFCN and EUTRAN_PRIORITY will then need to be configured to the corresponding EUTRAN cell Not Present Not Present 4.S0038-B [36] for HRPD cells and C. 4.508 V12. 3GPP .7 Default parameters specific for simulated cells Default parameters specific for simulated cells are specified in this subclause.Release 12 104 Measurement Bandwidth E-UTRAN_PRIORITY Set according to EUTRA band under test ‘100’B THRESH_E-UTRAN_high THRESH_E-UTRAN_low E-UTRAN_QRXLEVMIN ‘00010’B ‘00010’B 17 (-106 dBm) 0 (-140 dBm) } ** 0 Repeated E-UTRAN Not Allowed Cells Repeated E-UTRAN PCID to TA mapping 3G CSG Description E-UTRAN CSG Description Additions in release 9 spare padding 0 0 0 0 L spare padding 3GPP TS 36.4.1 - Common contents of HRPD Overhead messages QuickConfig The QuickConfig message is used to indicate a change in the overhead messages’ contents and to provide frequently changing information.S0043-A [37] for 1xRTT cells. 4.4.6 Common parameters for simulated CDMA2000 cells The parameters specified in this subclause apply to all simulated HRPD or 1xRTT cells unless otherwise specified.7.4. Actual value =4 dB Actual value =4 dB For signalling test cases For RF/RRM test cases End of Repeated EUTRAN Neighbour cells structure Note: When this message is used in Tics where more than one E-UTRA cells are active.1 (2014-12) Same as cell 1 as defined in 3GPP TS 36. 4.S0024-B clause 7.1 (2014-12) Table 4.6.2-3 Least significant 24 bits of Sector ID given in table 4.508 V12.7.4. 3GPP Condition .1-1: QuickConfig Derivation Path: C. 0 – 255 24 bits 16 bits 16 bits 0-1 0-63 0-1.11. RPCCount63To0 occurrences 0 or 1 bits 0 or 6 bits 0 or 1 bits.2-3 A valid value and same as used for SectorParameters A valid value and same as used for AccessParameter s 0X0 A valid value corresponding to the value of px_MACIndex A valid value corresponding to the value of px_MACIndex A valid value corresponding to the value of px_MACIndex A valid value corresponding to the value of px_MACIndex A valid value corresponding to the value of px_MACIndex Not Present or a valid value corresponding to the value of px_MACIndex Not Present or a valid value corresponding to the value of px_MACIndex Not Present or a valid value corresponding to the value of px_MACIndex 0X0 Comment 0-255.4.RPCCount127To64 occurrences 0 or 1 bits 0 or 8 bits 0 or 1 bits 0 – 7 bits as needed all set to zero SectorParameters The SectorParameters message is used to convey sector specific information to the access terminals.Release 12 105 3GPP TS 36.4.2.1 Information Element MessageID ColorCode SectorID24 SectorSignature AccessSignature Redirect RPCCount63To0 ForwardTrafficValid63To0 RPCCount127To64Included RPCCount127To64 ForwardTrafficValid127To64 RPCCount130To383Included RPCCount130To383 ForwardTrafficValid130To383 Reserved - Value/remark 0x0 See table 4. 508 V12.Release 12 106 Table 4.4.1-2: SectorParameters 3GPP 3GPP TS 36.7.4.1 (2014-12) . 2-3 See table 4. Note 1. Depends on test case 11 bits. NeighbourCount occurrences Not Present NeighborChannel Not Present NeighborSearchWindowSizeIncluded NeighborSearchWindowSize 0x0 NeighborSearchWindowOffsetIncluded NeighborSearchWindowOffset 0x0 Not Present ExtendedChannelIncluded 0x0 or Not Present ExtendedChannelCount ExtendedChannel Not Present Not Present AccessHashingChannelMaskIncluded 0x0 or Not Present AccessHashingMaskLength Not Present Not Present 3GPP Condition No_NeighPN Inc NeighPNInc No_NeighPN Inc NeighPNInc NeighPNInc No_NeighPN Inc 0 or 24 bits. 0 or ExtendedChannelCount occurrences 0 or 1 bits.0 8 bits 5 bits.11.4. AccessHashingChannelMaskL ength occurrences of this field and AccessHashingChannelMask if set as AccessHashingChannelMask.S0024-B v3. calculated and updated by the SS' Any valid value 0x1 or 0x0 0x1 or 0x0 0x1 or 0x0 0x00 Set according to PIXIT parameter Set according to PIXIT parameter 0x0 NeighborPilotPN 16 Not Present NeighborChannelIncluded Pilots PN's of configured cells [FFS] 0x0 3GPP TS 36.6.2.S0024-B clause 7. The number of cdma2000 high rate packet data extended channels available to the access terminal on this sector. 0 or 5 bits 24 bits.Release 12 Derivation Path: C. ChannelCount occurrences.1 in 3GPP2 C. Sub-clause 13.4.2 Information Element MessageID CountryCode SectorID SubnetMask SectorSignature Latitude Longitude RouteUpdateRadiusOverhead LeapSeconds LocalTimeOffset ReverseLinkSilenceDuration ReverseLinkSilencePeriod ChannelCount Channel SystemType BandClass ChannelNumber NeighborCount 107 Value/remark 0x01 See table 4. NeighbourCount occurrences 1 bit 0 or 4 bits.Depends on test case 128 bit value 8 bits 16 bits 22 bits 23 bits 11 bits 8 bits 11 bits 2 bits 2 bits 5 bits 24 bits. Note 1.2-3 0x40 Any valid value Any valid value Any valid value 0x0 'A valid value.4. 0 or 4 bits.1 (2014-12) Comment 0-255 0 – 999. NeighbourCount occurrences 1 bit 0 or 3 bits. Depends on BandClass 5 bits 1 bit.508 V12. 0<=AccessHashingChannelMa . NeighbourCount occurrences 0 or 1 bits. Note 1.Release 12 108 AccessHashingChannelMaskSameAsPrevious Not Present AccessHashingChannelMask Not Present RouteUpdateTriggerCodeIncluded 0x0 or Not Present Not Present Not Present 0x0 or Not Present 0x0 or Not Present Not Present 0x0 or Not Present Not Present Not Present 0x0 or Not Present Not Present Not Present 0x0 or Not Present Not Present Not Present 0X0 RouteUpdateTriggerCode RouteUpdateTriggerMaxAge PriorSessionGAUP FPDCHSupportedInclude FPDCHSupported SecondaryColorCodeIncluded SecondaryColorCodeCount SecondaryColorCode PilotGroupIDLoopIncluded PilotGroupIDIncluded PilotGroupID IsSectorMultiCarrierCapable ReverseBandClass ReverseChannelNumber Reserved Note 1: skLength<=(ChannelCount + ExtendedChannelCount). it can be Not Present. Note 1. AT assumes as 0x0. Note 1. 0 or 1 bits 0 or 1 bits.1 (2014-12) Explanation No neighbour Pilot PN included Neighbor Pilot PN's included AccessParameters The AccessParameters message is used to convey Access Channel information to the access terminals.508 V12. Note 1. AccessHashingChannelMaskL ength occurrences of this field and AccessHashingChannelMask if set as AccessHashingChannelMask 0 or AccessHashingMaskLength+1 0 or 1 bits. Note 1. 3GPP . 0 or 12 bits 0 or 4 bits 0 or 1 bits. Condition No_NeighPNInc NeighPNInc - 3GPP TS 36.4. Note 1. If not present. 0 or 3 bits 8 bits 0 or 1 bits. 1 bit. 0 or 5 bits 0 or 11 bits 0 – 7 bits as needed all set to zero As no Non reserved fields following this are included. 0 or 1 bits 0 or 3 bits 0 or 1 bits. 0 or 1 bits. Clause 1.2-3 A valid value.S0024-B clause 9.6.1-3: AccessParameters Derivation Path: C.7.Release 12 109 3GPP TS 36.2 4. 4.1 Information Element MessageID MaximumRevision Value/remark 0x0 0x1 MinimumRevision 0x1 Pilot PN Offset CDMA System Time See table 4.4.12.0 0 – 511 37 bits Condition Editor's Note: This section is reserved for cell specific default parameters. 8bits(-84 – 115 dB).S0024-B v3. - Sync The access network broadcasts the Sync message to convey basic network and timing information Table 4.5 dB) 3bits(1 – 7) 4 bits 6 bits.1-4: Sync Derivation Path: C.508 V12.6 Information Element MessageID Access Cycle Duration Access Signature OpenLoopAdjust Value/remark 0x1 16 slots or 64 slots Any valid value Set according to PIXIT parameter for default open loop adjust 0x0(0 dB) 0x5 0x8(4 dB) 0x2 0x2 or 0x4 0x0 or 0x1 ProbeInitialAdjust ProbeNumStep PowerStep PreambleLength CapsuleLengthMax APersistence Comment 0-255 16.4.S0024-B clause 7. Actual value is -1 times 5 bits(-16 – 15 db) 4bits(1 – 15) 4 bits(0 – 7.6.7.2. calculated and updated by the SS Comment 0-255 8 bits .7.4.4.4.7. 'NACMPAPersist = 4' occurrences APersistence 0x0 or 0x1 6 bits APersistence 0x0 or 0x1 6 bits APersistence 0x0 or 0x1 6 bits Reserved 0X0 0 – 7 bits as needed all set to zero Note 1: The value specified is the value to be used when the AccessParameters is being sent first time.4.S0024-B v3.128 slots Condition 16 bits Note1.0 8 bits. At every change of content of AccessParameters message it is incremented by 1.1 (2014-12) Table 4.64. Clause 1.4.2. a base station maintains a configuration sequence number CONFIG_SEQ for configuration messages transmitted on the Paging channel and increments by 1 modulo 64 whenever any of the following messages being transmitted are modified: System Parameters Message Neighbor List Message (Band Class 0 only) CDMA Channel List Message Extended System Parameters Message 3GPP .2.3.15 of 3GPP2 C.15 of 3GPP2 C.1 Common contents of 1XRTT Overhead messages Configuration sequence number In general. 7.2.Release 12 110 3GPP TS 36.7.1 (2014-12) Extended Neighbor List Message (band classes other than Band Class 0).2 - Over Head messages CDMA Channel List Message Table 4.4. 6 bits. 4.4 3GPP Comment 9 bits. For simplicity resaons the System Simulator may use any value for this configuration sequence number CONFIG_SEQ.2-1: CDMA Channel List Message Derivation Path: C.4.1 Set according to PIXIT parameter or as per clause 4.3. 11 bits Condition .4.2-4 Set to ' CONFIG_SEQ' of base station as per clause 4.508 V12.2.4.4 Information Element PILOT_PN CONFIG_MSG_SEQ CDMA_FREQ Value/remark See table 4.S0005 clause 3.7.4.3.2.2.7.1.2. 508 V12.7.4.2-2: System Parameters Message 3GPP .1 (2014-12) System Parameters Message Table 4.4.2.Release 12 - 111 3GPP TS 36. 60 PN Chips 4 bits.1 (2014-12) Comment 15 bits 16 bits 12 bits 3 bits 3 bits.2. 5 or 28 frames 1 bits. NID roamer registration enabled 1 bits.2-4 1 0 or 1 0 or 1 MULT_NIDS 0 or 1 BASE_ID BASE_CLASS See table 4.4. periodic report mode disabled BandClass1 _4 Not BandClass1 _4 .Release 12 Derivation Path: C.4.7. Base Station Latitude 23 bits. Distance based registration disabled 4 bits. Power control reporting threshold 4 bits. parameter change registration disabled or enabled 7 bits. Maximum Slot Cycle index 1 bits.7.1 Information Element PILOT_PN CONFIG_MSG_SEQ 112 SID NID REG_ZONE TOTAL_ZONES ZONE_TIMER MULT_SIDS Value/remark See table 4. Search window size for the remaining set.4. power-down registration enabled as per PIXIT 1 bits. 60 PN Chips 4 bits.4. threshold report mode disabled 1 bits. Mobile shall not or shall store SID_NID_List containing different NID's 16 bits 4 bits 0 PAGE_CHAN 1 MAX_SLOT_CYCLE_INDEX 1 or 0 HOME_REG 1 FOR_SID_REG 1 FOR_NID_REG 1 POWER_UP_REG 1 POWER_DOWN_REG PARAMETER_REG Set according to PIXIT parameter 0 or 1 REG_PRD 0 BASE_LAT BASE_LONG Any valid value REG_DIST 0 SRCH_WIN_A 8 SRCH_WIN_N 8 SRCH_WIN_R 8 NGHBR_MAX_AGE 0 PWR_REP_THRESH PWR_REP_FRAMES PWR_THRESH_ENABLE PWR_PERIOD_ENABLE Any valid value 0. 1 or 5 0. power-up registration enabled 1 bits.4. registration period. Mobile shall not or shall store SID_NID_List containing different SID's 1 bits.S0005 clause 3. Search Window Size for the neighbor set.4. SID roamer registration enabled 1 bits.2.1 See table 4. 4 or 7 0 0 3GPP Condition 9 bits 6 bits 3 bits.2-4 Set to ' CONFIG_SEQ' of base station as per clause 4.4.2. Minimum Neighbour set age 5 bits. Base Station Longitude 11 bits.508 V12.2-4 1 3GPP TS 36. Number of Paging Channels 3 bits. Search Window size for Active Set. 1 or 2 minutes 1 bits.2-4 See table 4. Home registration enabled 1 bits. 60 PN Chips 4 bits.3.2-4 See table 4. power control reporting frame count. No timer Based Registration 22 bits. 4.5 dB) 4 bits. User zone Identification not transmitted 1 bit. Extended channel list not sent Explanation If Band Class is 1 or 4 If Band Class is 1 or 3 or 4 3GPP BandClass1 _3_4 Not BandClass1 _3_4 . Extended System Parameters message present 1 bit. Pilot drop threshold (-16 dB Ec/Io) 4. Drop timer value (4 sec) 1 bit. Pilot detection threshold (-14 dB Ec/Io) 6 bits. Extended neighbor list not present 0 GEN_NGHBR_LST 0 GLOBAL_REDIRECT 0 PRI_NGHBR_LST 0 USER_ZONE_ID 0 EXT_GLOBAL_REDIRECT 0 EXT_CHAN_LST 0 Condition BandClass1_4 BandClass1_3_4 1 bit.Release 12 113 PWR_REP_DELAY RESCAN 3GPP TS 36. Extended global redirection not transmitted 1 bit. Global service redirection message not transmitted 1 bit. General neighbor list not sent 1 bit. Active set versus candidate set comparison threshold (2.508 V12.1 (2014-12) 0 or 14 0 T_ADD 28 (-14 dB Ec/Io) T_DROP 32 T_COMP T_TDROP EXT_SYS_PARAMETER EXT_NGHBR_LST 5 3 1 1 5 bits. Private neighbor list message not transmitted 1 bit. 0 or 56 frames 1 bit. re-initialize and reacquire the system 6bits. 4.2-3: Access Parameters message 3GPP .Release 12 - 114 3GPP TS 36.508 V12.2.4.7.1 (2014-12) Access Parameters Message Table 4. 5 access probes/ sequence 3 bits.2. Persistence modifier for Access Channel attempts for registrations 4 bits.Release 12 Derivation Path: C. Persistence modifier for access channel attempts for message transmissions 3 bits. Persistence value for access overload classes 15 3 bits. Max number of access probe sequences for an access channel request 4 bits. Power increment 4 bits. No authentication data in access channel messages 0 or 32 bits 1 bits. 0 is used in initial transmission and incremented by 1 modulo 64 every time Access Parameters message is modified. Extended nominal transmit power Condition . Initial power offset in dB 3 bits. for simplicity reasons any value may be used 5 bits. Access channel probe sequence backoff range =no back off 4 bits. Max number of access probe sequences for an access channel response 2 bits. Access Channel preamble length = 2+1 frames 6 bits.4.2. Access Channel probe back off = no back off 4 bits..7.63 ACC_CHAN 0 NOM_PWR INIT_PWR PWR_STEP NUM_STEP 0 0 1 or 3 MAX_CAP_SZ Any valid value 2 or 7 PAM_SZ Any valid value PSIST(0-9) 0 PSIST(10) 0 PSIST(11) 0 PSIST(12) 0 PSIST(13) 0 PSIST(14) 0 PSIST(15) 0 MSG_PSIST 0 REG_PSIST 0 PROBE_PN_RAN 4 or 0 ACC_TMO 3. Persistence value for access overload classes 13 3 bits. Persistence value for access overload classes 12 3 bits.2 Information Element PILOT_PN ACC_MSG_SEQ 115 Value/remark See table 4.1. Persistence value for access overload classes 11 (emergency) 3 bits. Maximum Access channel message capsule size =2 or 7 +3 frames 4 bits. Time Randomization for Access Channel probes= 0 to 15 PN chips 4 bits. Number of access channels -1 4 bits. Acknowledgement timeout = (value +2) * 80 ms 4 bits. Nominal transmit power offset in dB 5 bits.4. 4 or 5 PROBE_BKOFF 1 or 0 BKOFF 1 or 0 MAX_REQ_SEQ Any valid value MAX_RSP_SEQ Any valid value AUTH 0 RAND NOM_PWR_EXT Not present 0 3GPP 3GPP TS 36. Persistence value for access overload classes 14 3 bits.508 V12.2-4 0.2.3.S0005 clause 3. Persistence value for access overload classes 0-9 3 bits. Access Message Sequence. Persistence value for access overload classes 10 3 bits.1 (2014-12) Comment 9 bits. 6 bits. 2.2-4: Extended System Parameters Message 3GPP .Release 12 - 116 3GPP TS 36.4.508 V12.4.1 (2014-12) Extended System Parameters Message Table 4.7. Quick PCH not supported 0 or 2 bits 0 or 1 bits 0 or 3 bits 0 or 1 bits 0 or 3 bits 1 bits.2-4 See table 4. Pilot Report indicator.1 (2014-12) Comment 9 bits 6 bits 1 bits.2. Use TMSI indicator 2 bits.7. 0 dB Gain adjustment of Reverse traffic channel 1 bits 0 or 2 bits Condition .7. 0 dB 6 bits. Access Entry Handoff not permitted 1 bits 1 bits.S0005 clause 3. the MS reports or does not report additional pilots which have strengths exceeding T_ADD 1 bits 0 or 1 bits 1 bits 0 or 1 bits 0 or 1 bits 0 or 1 bits 0 or 1 bits 0 or 1 bits 0 or 3 bits 0 or 6 bits 1 bits.4.2. Delete foreign TMSI 1 bits. Broad cast GPS not supported 1 bits. 0 dB 8 bits. Preferred Access Channel MSID Type 10 bits 7 bits. 11th and 12th digits of the IMSI 4 bits 8 bits if present 3 bits 1 bits 8 bits 8 bits 6 bits 6 bits.2-4 TMSI_ZONE_LEN TMSI_ZONE BCAST_INDEX IMSI_T_SUPPORTED P_REV MIN_P_REV SOFT_SLOPE ADD_INTERCEPT DROP_INTERCEPT PACKET_ZONE_ID 1 or 0 1 or Not present 0 0 6 6 0 0 0 0 MAX_NUM_ALT_SO RESELECT_INCLUDED 0 0 EC_THRESH EC_I0_THRESH PILOT_REPORT Not present Not present 1 or 0 NGHBR_SET_ENTRY_INFO ACC_ENT_HO_ORDER NGHBR_SET_ACCESS_INFO ACCESS_HO ACCESS_HO_MSG_RSP ACCESS_PROBE_HO ACC_HO_LIST_UPD ACC_PROBE_HO_OTHER_MSG MAX_NUM_PROBE_HO NGHBR_SET_SIZE ACCESS_ENTRY_HO 0 Not present 0 Not present Not present Not present Not present Not present Not present Not present ACCESS_HO_ALLOWED BROADCAST_GPS_ASST Not present Not present 0 QPCH_SUPPORTED NUM_QPCH QPCH_RATE QPCH_POWER_LEVEL_PAGE QPCH_CCI_SUPPORTED QPCH_POWER_LEVEL_CONFIG SDB_SUPPORTED 0 Not present Not present Not present Not present Not present 0 RLGAIN_TRAFFIC_PILOT 0 REV_PWR_CNTL_DELAY_INCL REV_PWR_CNTL_DELAY 0 Not present 3GPP 3GPP TS 36.2. System reselection parameters not included 0 or 5 bits 0 or 5 bits 1 bits.4.13 Information Element PILOT_PN CONFIG_MSG_SEQ DELETE_FOR_TMSI USE_TMSI PREF_MSID_TYPE 117 Value/remark See table 4.4.1 0 0 or 1 3 MCC IMSI_11_12 See table 4. Short Data burst not supported 6 bits.2-4 Set to ' CONFIG_SEQ' of base station as per clause 4.Release 12 Derivation Path: C.4.508 V12.3. Packet data service zone not supported 3 bits 1 bits.4. 4.2.S0005 clause 3.2-4 Set to ' CONFIG_SEQ' of base station as per clause 4.2-4.4.4.4.7.2. the band class is not 0.7. the band class is 0.7.1 (2014-12) Neighbor List Message Table 4.3.2.3.1 10 or 1 NGHBR_CONFIG(n) NGHBR_PN(n) 0 or Not present See table 4.e.Release 12 - 118 3GPP TS 36.S0005 clause 3.4.4.2-4 or Not present SEARCH_PRIORITY(n) 1. Pilot PN Sequence offset index increment = n * 50 3 bits if present.2-4 Set to ' CONFIG_SEQ' of base station as per clause 4.1 10 or 1 NGHBR_CONFIG(n) 0 or Not present NGHBR_PN(n) Comment Condition 9 bits 6 bits 4 bits.508 V12. Condition InterFreqCell Explanation If the configured neighbour cell is on a different frequency compared to the cell in which Extended Neighbour list message is being transmitted 3GPP .4.2-5.2-5 - Comment Condition 9 bits 6 bits 4 bits.14 Information Element PILOT_PN CONFIG_MSG_SEQ PILOT_INC Value/remark See table 4.2.4.4.2. 9 bits if present See table 4.2. The parameters for the first cell should be set as per table 4.2-4 or Not Present Note 1: the elements with index n are repeated as per table 4. Derivation Path: C.7. Medium present search priority FREQ_INCL(n) 1 1 bit InterFreqCell 0 or Not present NGHBR_BAND(n) Set according to 0 or 5 bits InterFreqCell PIXIT parameter Not present NGHBR_FREQ(n) Set according to 0 or 11 bits InterFreqCell PIXIT parameter Not Present Note 1: The elements with index n are repeated as per table 4.2-6: Neighbor List Message This message is sent when EXT_NGHBR_LST in Systems parameter message is set as '0'B i.3 Information Element PILOT_PN CONFIG_MSG_SEQ PILOT_INC Value/remark See table 4. Neighbor configuration where neighbor base station has same number of frequencies having paging channels as the current base station. 2 or Not 2 bits if present.e.7.2-7: Extended Neighbor List Message This message is sent when EXT_NGHBR_LST in Systems parameter message is set as '1'B i. The SS can transmit up to 7 neighbour intra frequency cell information.4.2.2. Derivation Path: C.4.4. Pilot PN Sequence offset index increment = n * 50 9 bits if present Extended Neighbor List Message Table 4.7. S0005 clause 3. 4.2-4 See table 4. Paging Channel Data rate=9600 bps 11 bits.2-4 See table 4.7.26 Information Element P_REV MIN_P_REV SID NID PILOT_PN LC_STATE Value/remark 6 6 See table 4.523-1 [18] and TS 36. Long code State Condition 36 bits.2. calculated and updated by the SS A valid value.7.4. calculated and updated by the SS A valid value.2. Extended frequency assignment 4. calculated and updated by the SS A valid value.1. calculated and updated by the SS 0 SYS_TIME LP_SEC LTM_OFF DAYLT PRAT CDMA_FREQ EXT_CDMA_FREQ Set according to PIXIT parameter or as per clause 4.4 Comment 8 bits. calculated and updated by the SS A valid value. Frequency assignment 11 bits.5.508 V12. Offset of local time from System time 1 bits. This section also defines a set of procedures to bring the UE into these states.4.1 UE test states NOTE: The need to have a procedure for the transition from State 4/State 3 to State 2 is for further study and it can added if the technical motivation for this procedure can be justified.3.4. 3GPP . System time 8 bits.4 Set according to PIXIT parameter or as per clause 4.4. Minimum protocol revision level 15 bits 16 bits 9 bits 42 bits.523-3 [34] or other procedures defined in this specification.2.3. TS 36.1. Daylight savings indicator 2 bits.Release 12 119 - 3GPP TS 36.2-8: Sync Channel Message Derivation Path: C.1 (2014-12) Sync channel Messages Table 4.2-4 A valid value.5 Generic procedures This clause describes UE test states which can be used in the initial condition of many test cases defined in TS 36.3.4.521-1 [21]. The number of leap seconds 6 bits. Protocol revision level 8 bits. 508 V12.5.1 (2014-12) Figure 4.5. 3GPP .Release 12 120 3GPP TS 36.1-1 and the status of the relevant protocols in the UE in the different states are given in table 4.1-1: E-UTRAN UE Test States for Basic Generic Procedures In order that the UE can set up a call or session in E-UTRAN.4. The sequences are shown in figure 4.5.1-1. there are a number of procedures to be undertaken in a hierachical sequence to move between known states. pre-registered on 1xRTT State 3 Generic RB Established RRC_IDLE ECM-IDLE EMM-REGISTERED RRC_IDLE ECM-IDLE EMM-REGISTERED 1 default EPS bearer context active. 1 default EPS bearer context active.1. pre-registered on 1xRTT RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases ECM-CONNECTED EMM-REGISTERED RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases ECM-CONNECTED EMM-REGISTERED 1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases 1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases 1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases 1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases 1 default EPS bearer context active and N (0 ≤ N ≤ 7) dedicated EPS bearers active as specified in the test cases State 4 Loopback Activated NOTE: Refer to TS 24.509 [38] for details regarding UE test mode and UE Loopback. 3GPP Active Active Active Active Active . pre-registered on HRPD RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases ECM-CONNECTED EMM-REGISTERED State 3C Generic RB Established. pre-registered on HRPD State Registered.Release 12 121 3GPP TS 36. Active RRC_IDLE ECM-IDLE EMM-REGISTERED 1 default EPS bearer context active.1-1: The E-UTRAN UE states RRC ECM EMM State 1 Switched OFF ----State 2 Registered.301 [28] subclause 5.1 (2014-12) Table 4.5. UE Test Mode ----Not active Registered. Idle Mode.1 for more details on the ESM state.4. Active RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases ECM-CONNECTED EMM-REGISTERED Not active State 3A Generic RB Established. UE Test Mode Activated State Registered. UE Test Mode Activated RRC_CONNECTED 1 + N (0 ≤ N ≤ 7) data radio bearers configured as specified in the test cases ECM-CONNECTED EMM-REGISTERED State 3B Generic RB Established.5.508 V12. 2C Idle Mode. 2B Idle Mode. NOTE: Refer to TS 36. RRC_IDLE Idle Mode ----ECM-IDLE ----EMM-REGISTERED State 2A ESM ----1 default EPS bearer context active. there is a number of procedures that need to be performed in a certain sequence to move between known UE states.1 (2014-12) Figure 4.508 V12. but has no active connection to the network. 4. but the UE is also pre-registered in E-UTRAN. and has an active network connection. The UE should be ready to perform a nonoptimised cell reselection to E-UTRAN (as per [41] cl.1-2. 9.5.2 UE Registration (State 2) Editor’s Note: The UE Registration assumptions below are still in progress .5. - one of the PDN connectivities is for IMS. HRPD UE states are described in table 4.92 [52]. 14.Release 12 122 3GPP TS 36. - During initial UE registration the UE requests for one or two PDN connectivities. but the UE is also pre-registered in E-UTRAN. UE Registration depends on the specific configuration of a UE. Same state as State H2. The UE should be ready to perform an optimised handover to E-UTRAN (as per [41] cl. 9.1). - As for any 2nd PDN connectivity request security protection is already established the UE provides a valid APN in the PDN CONNECTIVITY REQUEST. In order to reduce complexity and to achieve testability several assumptions and definitions are made: - An IMS capable UE is compliant to GSMA PRD IR. 3GPP .523-2 [19]. connectivity to this PDN is not established during the initial UE registration.they represent the assumptions on which the test specification is based in the present version of TS 36. - When the UE requests for two PDN connectivities: - it re-uses the existing RRC connection for signalling regarding the 2nd PDN connectivity. The InterRAT Idle State Protocol (IR-ISP) is in Monitor State. The UE should be ready to perform an optimised cell reselection to E-UTRAN (as per [41] cl.1-2.4.5. These states and sequences are shown in figure 4.1-2: HRPD UE Test States for Basic Generic Procedures In order for the UE to set up a session in an HRPD RAN. The UE should be ready to perform a non-optimised handover to E-UTRAN (as per [41] cl. Same state as State H3.5. which is expressed by PICS according to TS 36. 8 and [42] cl. Table 4. 8). - If the UE is configured with an APN for XCAP only usage (pc_XCAP_only_APN==true).5.1-2: Description of HRPD UE states State H2 H3 H2A H3A Description The UE is registered on the HRPD network.6). The UE is registered on the HRPD network.508.5). 3GPP .e.2.4.508 V12. - The procedure shall be performed under ideal radio conditions as defined in clause 5 User Equipment: - The Test UICC shall be inserted. 4.Release 12 123 3GPP TS 36.1 (2014-12) In detail the following UE configurations are supported: Configuration IMS_Only Condition Explanation pc_IMS AND NOT UE is configured to request for IMS PDN connectivity only pc_Provide_Internet_as_second_APN AND NOT pc_Provide_IMS_as_second_APN Internet_Only NOT pc_IMS UE does not support IMS IMS_Internet pc_IMS AND UE is configured to request for IMS PDN connectivity first pc_Provide_Internet_as_second_APN and then to request for an internet PDN connectivity Internet_IMS pc_IMS AND UE is configured to request for an internet PDN connectivity pc_Provide_IMS_as_second_APN first and then to request for the IMS PDN connectivity NOTE: pc_Provide_Internet_as_second_APN and pc_Provide_IMS_as_second_APN are mutually exclusive i.5. Further auxiliary definitions: Configuration PDN1_IMS PDN2_IMS MULTI_PDN XCAP_SIGNALLING 4.1 Condition IMS_Only OR IMS_Internet Internet_IMS IMS_Internet OR Internet_IMS test case requires XCAP signalling Initial conditions System Simulator: - 1 cell. default parameters. This shall contain either ISIM and USIM applications or only a USIM application on UICC.2 Definition of system information messages The default system information messages are used.2.5. shall not be true at the same time. 508 V12.2.Release 12 4.5.3-1: UE registration procedure (state 1 to state 2) 3GPP .4.2.5.1 (2014-12) Procedure Table 4.3 124 3GPP TS 36. EXCEPTION: Steps 9a1 to 9a2 describe behaviour that depends on UE configuration. The SS transmits a SecurityModeCommand message to activate AS security. The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN. The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST The SS transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure.508 V12. EXCEPTION: In parallel to the event described in step 16 below.2. IF the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the SS transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN. if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS U-S <---> <---> <---> <---> - 3GPP TS 36. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer. The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration.1 (2014-12) Message Sequence Message RRC: SYSTEM INFORMATION (BCCH) RRC: RRCConnectionRequest RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: ATTACH REQUEST NAS: PDN CONNECTIVITY REQUEST RRC: DLInformationTransfer NAS: AUTHENTICATION REQUEST RRC: ULInformationTransfer NAS: AUTHENTICATION RESPONSE RRC: DLInformationTransfer NAS: SECURITY MODE COMMAND RRC: ULInformationTransfer NAS: SECURITY MODE COMPLETE - <-- RRC: DLInformationTransfer NAS: ESM INFORMATION REQUEST --> RRC: ULInformationTransfer NAS: ESM INFORMATION RESPONSE <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: UECapabilityEnquiry --> RRC: UECapabilityInformation <-- RRC: RRCConnectionReconfiguration NAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST --> RRC: RRCConnectionReconfigurationComplete 3GPP .4.8. 0) according to 4. This message includes the ATTACH ACCEPT message. The UE transmits a UECapabilityInformation message to transfer UE radio access capability.1.2. The UE transmits a SecurityModeComplete message and establishes the initial security configuration. The SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure. The SS transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1. The UE transmits an AUTHENTICATION RESPONSE message and establishes mutual authentication. SS transmits an RRCConnectionSetup message. the "lower case letter" identifies a step sequence that take place if the UE has ESM information which needs to be transferred. The SS transmits a NAS SECURITY MODE COMMAND message to activate NAS security. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT.Release 12 Step 1 2 3 4 5 6 7 8 - 9a1 9a2 10 11 12 13 14 15 - 125 Procedure UE transmits an RRCConnectionRequest message. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message.1. 1 takes place performing IP address allocation in the Uplane.508 V12.Release 12 126 36.508 subclause 4.1 (2014-12) .4. 3GPP 3GPP TS 36.5A. 508 V12.5A.Release 12 - 16 - 16a1 16a2 EXCEPTION: IF PDN1_IMS THEN in parallel to the event described in step 16 below the generic procedure for IMS signalling in the Uplane specified in TS 36. EXCEPTION: Steps18a1 to 18b1 describe behaviour that depends on UE capabilities/configuration and test requirements. The UE transmits an RRCConnectionRequest message. <-- RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE RRC: RRCConnectionRelease --> RRC: RRCConnectionRequest <-- RRC: RRCConnectionSetup --> RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST <-- 16b6 The UE transmits a TRACKING AREA UPDATE COMPLETE message.508 subclause 4. The SS transmits a TRACKING AREA UPDATE ACCEPT message. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE. pc_attach and pc_TAU_idle _in_IMS are set to TRUE (Note 2) THEN The SS transmits an RRCConnectionRelease message to release the RRC connection. EXCEPTION: Steps 16a1 to 16c1 describe behaviour that depends on UE configuration. IF MULTI_PDN AND (pc_XCAP_only_APN OR NOT XCAP_SIGNALLING) AND pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36. --> 16c1 ELSE IF MULTI_PDN = TRUE THEN The generic procedure for UE establishing additional PDN connectivity as specified in TS 36.1 (2014-12) RRC: ULInformationTransfer NAS: ATTACH COMPLETE NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT - --> RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE REQUEST <-- 16a3 The UE transmits a TRACKING AREA UPDATE COMPLETE message. pc_attach and pc_TAU_connected _in_IMS are set to TRUE (Note 1) THEN The UE transmits a TRACKING AREA UPDATE REQUEST message.508 subclause 4. 127 --> - 3GPP TS 36.508 subclause 4.17 IF MULTI_PDN AND (pc_XCAP_only_APN RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE - 16b2 16b3 16b4 16b5 17 - 18a1 18a2 - <-- RRC: RRCConnectionRelease - - - - 3GPP .5A. The UE transmits an RRCConnectionSetupComplete message including a TRACKING AREA UPDATE REQUEST message. IF IMS voice not supported and pc_voice_PS_1_CS_2. The SS transmit an RRCConnectionSetup message. the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured.4.16 takes place The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2). --> 16b1 ELSE IF IMS voice not supported and pc_voice_PS_1_CS_2. the "lower case letter" identifies a step sequence that takes place when the UE is configured in a certain way. The SS transmits a TRACKING AREA UPDATE ACCEPT message.5A.3 takes place if requested by the UE This message includes the ATTACH COMPLETE message. The UE implementation supports TAU in idle mode. NOTE 2: The procedure is used with specific message withno IMS voice network support.1 (2014-12) OR NOT XCAP_SIGNALLING) AND NOT pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36.7 with the exceptions below.2.6.5.508 V12. CS Voice as secondary and to initiate EPS attach. Table 4.4 Specific message contents All specific message contents shall be referred to clause 4.1-16 Information Element RRCConnectionRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionRequest-r8 SEQUENCE { ue-Identity } } } Value/remark Comment Condition Any allowed value Table 4.5. The UE implementation supports TAU in connected mode. CS Voice as secondary and to initiate EPS attach.5A.4-1: RRCConnectionRequest (Step 2) Derivation Path: Table 4.508 subclause 4.6.1-23 Information Element UECapabilityInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ ueCapabilityInformation-r8 } } } Value/remark Any allowed value 3GPP Comment Condition .18 NOTE 1: The procedure is used with specific message with no IMS voice network support.Release 12 128 3GPP TS 36. The UE is configured for voice domain preference IMS PS voice preferred.5.6 and 4. The UE is configured for voice domain preference IMS PS voice preferred.4-2: UECapabilityInformation (Step 13) Derivation Path: Table 4.4.2. 4.2. 4-5: TRACKING AREA UPDATE ACCEPT (Steps 16a2 and 16b5) Derivation Path: 36.5. are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used.5.Release 12 129 3GPP TS 36.4.2-24 with condition combined_TA_LA 4.3-6 apply unless the condition IPv4_address_only in table 4. length of contents = 0).7.1 (2014-12) Table 4. the IE Protocol configuration options contains a configuration protocol option = '000B00H' ("IPv4 address allocation via DHCPv4".7. Condition IPv4_address_only IPv4-DHCP Explanation This condition applies if the test case preamble description indicates that the UE is allocated an IPv4 address. 3GPP .0 DHCPv4 is to be IPv4-DHCP used to allocate the IPv4 address ESM cause IF "PDN type" IE in step "PDN type IPv4 4 is 'IPv4v6' THEN only allowed" '00110010'B ELSE Not present NOTE: The default message contents specified in table 4.2.2A UE Registration.3-6 with condition IMS_PDN_ConnEstab for PDN1_IMS and NOT IMS_PDN_ConnEstab else Information Element Value/remark Comment Condition EPS bearer identity '0101'B arbitrary value PDN1_IMS used for PDN OR NOT connectivity being MULTI_PDN maintained during the test case EPS bearer identity '1100'B arbitrary value MULTI_PDN used for additional AND NOT PDN connectivity PDN1_IMS which may be released before entering the test procedure of the test case PDN address IPv4_addres s_only Length of PDN address contents 5 octets PDN type value ‘001’B IPv4 PDN address information IPv4 address The SS provides a NOT IPv4valid IPv4 address DHCP 0.2.508 Table 4. Note 2: If both messages. If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message.4-3: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Step 14) Derivation Path: Table 4.2-27 with condition combined_TA_LA Table 4. UE Test Mode Activated (State 2A) The same assumptions and definitions apply as in clause 4.508 Table 4.2.7.2. PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE. Note 1: This condition is used in conjunction with IPv4 or IPv4v6 as indicated in the "PDN address row" just above.5.0.5.5.4-3 is true.2.4-4: TRACKING AREA UPDATE REQUEST (Steps 16a1 and 16b4) Derivation Path: 36.508 V12.0.5.7. Table 4. default parameters.Release 12 4.2A.508 V12. 3GPP .1 130 3GPP TS 36. - The procedure shall be performed under ideal radio conditions as defined in clause 5 User Equipment: - The Test USIM shall be inserted.5.4. 4.1 (2014-12) Initial conditions System Simulator: - 1 cell.5.2A.2 Definition of system information messages The default system information messages are used. 4.2A.5.5.3 131 3GPP TS 36.Release 12 4.508 V12.1 (2014-12) Procedure Table 4.2A.3-1: UE registration with test mode activation procedure (state 1 to state 2A) 3GPP . 3 The SS transmits an ACTIVATE TEST MODE message to activate UE radio bearer test mode procedure.8. The UE transmits a UECapabilityInformation message to transfer UE radio access capability. 0) according to 4. The SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure.5A.508 subclause 4.5A. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT. U-S - Message Sequence Message - <-- RRC: DLInformationTransfer TC: ACTIVATE TEST MODE --> <-- RRC: ULInformationTransfer TC: ACTIVATE TEST MODE COMPLETE RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: UECapabilityEnquiry --> RRC: UECapabilityInformation <-- RRC: RRCConnectionReconfiguration NAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST --> RRC: RRCConnectionReconfigurationComplete --> RRC: ULInformationTransfer NAS: ATTACH COMPLETE NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT - - --> RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE REQUEST <-- RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE RRC: RRCConnectionRelease 18a3 The UE transmits a TRACKING AREA UPDATE COMPLETE message. The SS transmits a SecurityModeCommand message to activate AS security.4. The UE transmits an ACTIVATE TEST MODE COMPLETE message.508 V12.Release 12 Step 1 to 9a2 10 11 12 13 14 15 16 17 - - 18 - 18a1 18a2 132 3GPP TS 36. --> 18b1 ELSE IF IMS voice not supported and pc_voice_PS_1_CS_2. The UE transmits a SecurityModeComplete message and establishes the initial security configuration. pc_attach and pc_TAU_connected _in_IMS are set to TRUE (Note 1) THEN The UE transmits a TRACKING AREA UPDATE REQUEST message. The SS transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1.1 takes place performing IP address allocation in the U-plane if requested by the UE. the "lower case letter" identifies a step sequence that takes place when the UE is configured in a certain way. EXCEPTION: IF PDN1_IMS THEN in parallel to the event described in step 18 below the generic procedure for IMS signalling in the Uplane specified in TS 36.1. EXCEPTION: Steps18a1 to 18c1 describe behaviour that depends on UE configuration. EXCEPTION: In parallel to the event described in step 18 below the generic procedure for IP address allocation in the Uplane specified in TS 36. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE.2.2.5.3 takes place if requested by the UE This message includes the ATTACH COMPLETE message.1 (2014-12) Procedure Same procedure for steps 1 to 9a2 as specified in the procedure in clause 4.2.508 subclause 4. This message includes the ATTACH ACCEPT message.1. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer. IF IMS voice not supported and pc_voice_PS_1_CS_2. The SS transmits a TRACKING AREA UPDATE ACCEPT message. pc_attach and <-- 3GPP . 16 takes place 19 The SS transmits an RRCConnectionRelease <-RRC: RRCConnectionRelease message to release RRC connection and move to RRC_IDLE (State 2A). The UE implementation supports TAU in idle mode.4-1: RRCConnectionRequest (Step 2) Derivation Path: Table 4. The UE transmits an RRCConnectionSetupComplete message including a TRACKING AREA UPDATE REQUEST message. 20a1 IF MULTI_PDN AND pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36. The SS transmit an RRCConnectionSetup message.17 20b1 IF MULTI_PDN AND NOT pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36.5. NOTE 2: The procedure is used with specific message with no IMS voice network support.2A.5A.4.508 subclause 4. CS Voice as secondary and to initiate EPS attach.2A.7 and 4.5. 4.5A. The UE is configured for voice domain preference IMS PS voice preferred.508 V12. The SS transmits a TRACKING AREA UPDATE ACCEPT message. 4. The UE transmits a TRACKING AREA UPDATE COMPLETE message. The UE transmits an RRCConnectionRequest message. Table 4.Release 12 18b2 18b3 18b4 18b5 18b6 133 pc_TAU_idle _in_IMS are set to TRUE (Note 2) THEN The SS transmits an RRCConnectionRelease message to release the RRC connection. 3GPP TS 36.508 subclause 4. CS Voice as secondary and to initiate EPS attach.7A with the exceptions below.18 NOTE 1: The procedure is used with specific message with no IMS voice network support.4 Specific message contents All specific message contents shall be referred to clause 4.1-16 Information Element RRCConnectionRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionRequest-r8 SEQUENCE { ue-Identity } } } Value/remark Any allowed value 3GPP Comment Condition .508 subclause 4. EXCEPTION: Steps 20a1 to 20b1 describe behaviour that depends on UE capabilities/configuration. The UE implementation supports TAU in connected mode.6. the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured. The UE is configured for voice domain preference IMS PS voice preferred.1 (2014-12) --> RRC: RRCConnectionRequest <-- RRC: RRCConnectionSetup --> RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST <-- RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE --> 18c1 ELSE IF MULTI_PDN = TRUE THEN The generic procedure for UE establishing additional PDN connectivity as specified in TS 36.6.5A. 7.2A..4-4: TRACKING AREA UPDATE ACCEPT (Steps 18a2 and 18b5) Derivation Path: 36.508 Table 4.2.5.Release 12 134 3GPP TS 36.508 Table 4.2B UE Registration.5.2B.5.5.2-3 Information Element SystemInformationBlockType1 ::= SEQUENCE { schedulingInformation ::= SEQUENCE (SIZE (1. SIB3 and SIB 8 are transmitted Condition .3-2) Derivation Path: 36.1 (2014-12) Table 4.2B.1 } 3GPP Comment SIB2. pre-registration on HRPD (State 2B) The same assumptions and definitions apply as in clause 4.508 section 4.5.2-24 with condition combined_TA_LA 4.2 Definition of system information messages Table 4. 4.4-3: TRACKING AREA UPDATE REQUEST (Steps 18a1 and 18b4) Derivation Path: 36.3.7.5.5. 4.2A.maxSI-Message)) OF SEQUENCE {} Value/remark Combination 6 in TS 36.4.1-23 Information Element UECapabilityInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ ueCapabilityInformation-r8 } } } Value/remark Comment Condition Any allowed value Table 4.2B.2A.5.508 Table 4.4.2-1: SystemInformationBlockType1 for cell 1 (Steps 1-41.4-2: UECapabilityInformation (Step 15) Derivation Path: Table 4.6.508 V12. Table 4.1 Initial conditions System Simulator: - Cell 1 - Cell 1 is transmitting SystemInformationBlockType8 User Equipment: - The Test USIM shall be inserted.4.3.5.2-27 with condition combined_TA_LA Table 4.2B. 4. spare13. bc3.7) } } } 4..2B.63) 1 entry Band Class of frequency under test ENUMERATED {bc0. bc14.maxCDMA 1 entry -BandClass)) OF SEQUENCE { bandClass Band Class of frequency under test cellReselectionPriority threshX-High threshX-Low } neighCellList SEQUENCE (SIZE (1... spare8. bc10. bc16.2-2: SystemInformationBlockType8 for cell 1 (Steps 1-41. bc4. bc1.63) INTEGER (0. spare12.5. bc4. bc8.. spare5. spare6.16)) OF SEQUENCE { bandClass } } t-ReselectionCDMA2000 3 30(-30) 32(-32) ENUMERATED {bc0. bc10. bc12. bc5. bc9. spare9. spare7. bc6. condition HRPD Information Element Value/remark SystemInformationBlockType8 ::= SEQUENCE { parametersHRPD SEQUENCE { preRegistrationInfoHRPD SEQUENCE { preRegistrationAllowed TRUE preRegistrationZoneId ColorCode secondaryPreRegistrationZoneIdList Not present SEQUENCE (SIZE (1. spare11. bc15. bc6. bc7. spare8.508 V12.5.3-1 shows the cell power levels during the procedure. bc2.3. spare3. bc13.. bc14.2B. spare3. bc2. bc7. spare11.2B. spare1.2B. spare4.. spare14. Table 4.3-7. bc3.Release 12 135 3GPP TS 36.} 3 INTEGER (0..3-2) Derivation Path: 36. spare12. bc13.3 Comment Procedure Table 4. bc16..508 Table 4. bc1.. spare5. bc9. spare2.5. 3GPP Condition . spare10. spare2. . bc17. bc12. spare13.1 (2014-12) Table 4. bc15. spare4. spare7. spare14. spare10. . spare1. bc5.5.4.2)) OF SEQUENCE { PreRegistrationZoneIdHRPD Not present } } cellReselectionParametersHRPD SEQUENCE { bandClassList SEQUENCE (SIZE (1. spare6.. bc11. spare9. bc11. bc17.} INTEGER (0. bc8. 3-1: Time instances of cell power level and parameter changes T0 Parameter Cell-specific RS EPRE Unit dBm/15kHz Cell 1 -75 3GPP Remark - .Release 12 136 3GPP TS 36.5.508 V12.4.2B.1 (2014-12) Table 4. 5.2B.1 (2014-12) Table 4.4.Release 12 137 3GPP TS 36.3-2: UE registration with HRPD pre-registration procedure (state 1 to state 2B) 3GPP .508 V12. The UE transmits an ULInformationTransfer containing a tunneled ConfigurationComplete message on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled ConfigurationRequest message for Stream protocol on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenCompleteon Cell 1. Optionally tunneled device level authentication may take place on Cell 1. The SS transmits a DLInformationTransfer containing a tunneled ConfigurationResponse message for Stream protocol accepting EMPA bound to service network on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled EMPA ConfigurationResponse message or MMPA ConfigurationResponse message on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkCloseReq message on Cell 1.2.5. Optionally tunneled Location Update U-S - Message Sequence Message - --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer <-- DLInformationTransfer <--> - <--> - 3GPP . The SS transmits a DLInformationTransfer containing a tunneled ConfigurationResponse message for SCP configuration on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled EMPA ConfigurationRequest message or MMPA ConfigurationRequest message on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled UATIComplete message on Cell 1. The SS transmits a DLInformationTransfer containing a tunneled EMPA ConfigurationResponse message or MMPA ConfigurationResponse message on Cell 1.4. The SS transmits an DLInformationTransfer containing a tunneled SoftConfigurationComplete message on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenReqmessage on Cell 1. The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkOpenConfmessage on Cell 1.508 V12. The SS transmits a DLInformationTransfer containing a tunneled UATIAssignment message on Cell 1.Release 12 Step 1 to 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 30A 30B 30C 30D 31 32 138 3GPP TS 36. The SS transmits a DLInformationTransfer containing a tunneled EMPA ConfigurationRequest message or MMPA ConfigurationRequest message on Cell 1. The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkCloseConf message on Cell 1.1 (2014-12) Procedure Same procedure for steps 1 to 16 as specified in the procedure in clause 4.3 The UE transmits an ULInformationTransfer containing a tunneled UATIRequest message Cell 1. The UE transmits an ULInformationTransfer containing a tunneled ConfigurationRequest message for SCP configuration on Cell 1. 3GPP 3GPP TS 36.508 V12.4.1 (2014-12) .Release 12 139 procedure may take place if the SS is configured to support it. 5A.17 IF MULTI_PDN AND NOT 140 3GPP TS 36. and Attach Type = “handover”.Release 12 32A 32B 32C 33 33A 34 35 36 37 38 39 39A 39B 40 41 - 42a1 42b1 The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenReq message on Cell 1. Void. EXCEPTION: Steps 42a1 to 42b1 describe behaviour that depends on UE capabilities/configuration. PDN Address.4.508 subclause 4. The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkCloseConf message on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled VSNCP Configure-Ack message. PDN Type. The SS transmits a DLInformationTransfer containing a tunneled AlternateLinkOpenConf message on Cell 1. IPv6 or IPv4/v6) The SS transmits a DLInformationTransfer containing a tunneled VSNCP Configure-Ack message. APN. Tunneled PPP LCP negotiation is performed between the UE and the SS. Protocol Configuration Options. optionally tunneled PPP Version Capability Indicaiton and/or Max PPP Inactivity Timer negotiation may take place. After entering PPP LCP Open State. including a PDN-ID. The UE transmits an ULInformationTransfer containing a tunneled VSNCP ConfigureRequest message.508 V12. EAP-AKA’ is selected as the authentication protocol. 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 IP address allocation. PDN Type indicates the UE’s IP capability (IPv4. IF MULTI_PDN AND pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36. The SS transmits a DLInformationTransfer containing a tunneled VSNCP ConfigureRequest message including the PDN-ID configuration option. the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured. Tunneled EAP-AKA’ is performed between the UE and the SS.1 (2014-12) --> ULInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer <--> - <-> - <--> - --> ULInformationTransfer <-- DLInformationTransfer <-- DLInformationTransfer --> ULInformationTransfer <--> --> ULInformationTransfer <-- DLInformationTransfer <-- RRCConnectionRelease - - - - - - 3GPP . The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkOpenComplete message on Cell 1. The UE transmits an ULInformationTransfer containing a tunneled AlternateLinkCloseReq message on Cell 1. The SS transmits an RRCConnectionRelease message on Cell 1. Optionally deferred IP address allocation using tunnelled IETF messages can take place depending on the Address Allocation Preference indicated by the UE at Step 35. 2B.5. an alternative link establishement procedure is also performed.4-2: UECapabilityInformation (Step13. Table 4. Table 4.5A. Note 2: Message contents of tunnelled CDMA2000 messages (steps 17-40) are not checked in terms of conformance testing. NOTE: If step 31 is performed.4-3: UATI Request message (Step 17. Set by UE 1 bit.3-2) Derivation Path: Table 4. RATI set by UE ‘0000’B ‘00000000’B 8 bits.2B.5.5.6.Release 12 141 3GPP TS 36.6. 4.1-16 Information Element RRCConnectionRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionRequest-r8 SEQUENCE { ue-Identity } } } Value/remark Comment Condition Any allowed value Table 4.5. Set by UE 3GPP Comment SAP Header UATI Request Condition .1 (2014-12) pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36.7 and 4.5.3-2) Derivation Path: Table 4.508 subclause 4.18 Note 1: The sequence in steps 17-40 lists important eHRPD procedures.6.1-23 Information Element UECapabilityInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ ueCapabilityInformation-r8 } } } Value/remark Comment Condition Any allowed value Table 4.7A with the exceptions below.2B.5. 4.4 Specific message contents All specific message contents shall be referred to clause 4.4.2B. Table 4.2B.508 V12.3-2) Field SAPState SessionConfigurationToken ConnectionLayerFormat ATI Record Reserved MessageID TransactionID Value/remark ‘0’B 16 bits.5.2B.4-1: RRCConnectionRequest (Step 2. Set by UE 34 bits. More protocol negotiations can happen based on UE capability and SS emulation.2B. Table 4. 4.2B.2-1: SystemInformationBlockType1 for cell 1 (Steps 1-19.508 Table 4.Release 12 142 3GPP TS 36.508 V12. RATI set in UATI Request ‘0000’B ‘00000001’B 8 bits. 4. SIB3 and SIB 8 are transmitted Condition . pre-registration on 1xRTT (State 2C) The same assumptions and definitions apply as in clause 4.5. Set by SS 8 bits.4.2B.5.3-2) Derivation Path: 36.508 section 4. Set by SS ‘0000000’B ‘1’B ‘1101000’B 104 bits.4.3-2) Field SAPState SessionConfigurationToken ConnectionLayerFormat ATI Record Reserved MessageID MessageSequence Reserved1 SubnetIncluded UATISubnetMask UATI104 UATIColorCode UATI024 UpperOldUATILength Reserved2 Value/remark ‘1’B ‘0’ 1 bit..4-4: UATI Assignment message (Step 18.1 (2014-12) Table 4.1 } 3GPP Comment SIB2.maxSI-Message)) OF SEQUENCE {} Value/remark Combination 6 in TS 36. Set by SS 34 bits. Table 4.5.2C.2.2C.5. Set by SS ‘0000’B ‘0000’B Comment SAP Header Condition UATI Assignment 4.2C.5.2C UE Registration. Table 4.5.2-3 Information Element SystemInformationBlockType1 ::= SEQUENCE { schedulingInformation ::= SEQUENCE (SIZE (1.3. Set to ColorCode 24 bits.2C.2 Definition of system information messages Table 4.5.3.5. 4.1 Initial conditions System Simulator: - Cell 1 - Cell 1 is transmitting SystemInformationBlockType8 User Equipment: - The Test USIM shall be inserted. - The UE is switched OFF. 4.508 V12.. spare2. bc10.3.Release 12 143 3GPP TS 36.2-4 '001'B zoneTimer '000'B or '001'B } longCodeState1XRTT cellReselectionParameters1XRTT SEQUENCE { bandClassList SEQUENCE (SIZE (1.. spare6. bc8.} INTEGER (0. bc16. spare9.63) INTEGER (0.5. bc1. bc11. calculated and updated by the SS Comment BIT STRING (SIZE (15)) BIT STRING (SIZE (16)) BOOLEAN BOOLEAN BOOLEAN BOOLEAN BOOLEAN BOOLEAN BOOLEAN BIT STRING (SIZE (7)) BIT STRING (SIZE (12)) BIT STRING (SIZE (3)) BIT STRING (SIZE (3)) BIT STRING (SIZE (42)) OPTIONAL 1 entry Band Class of frequency under test 3 30(-30) 32(-32) TRUE } 3GPP ENUMERATED {bc0. spare12.508 Table 4.4.2-4 Nid NID under test For Signalling test cases.3-7. bc15. bc5. see table 4. spare4. bc17. spare5. see table 4. bc7.2C. condition 1XRTT Information Element Value/remark SystemInformationBlockType8 ::= SEQUENCE { parameters1XRTT SEQUENCE { csfb-RegistrationParam1XRTT SEQUENCE { Sid SID under test For Signalling test cases.4. . bc2. see table 4. Table 4. bc12.1 (2014-12) Table 4. bc6. spare13.5.4. bc9.3-2) Derivation Path: 36. spare3.63) Condition . spare1... bc14. spare8. spare10..2-2: SystemInformationBlockType8 for cell 1 (Steps 1-19. bc3. spare14.maxCDMA -BandClass)) OF SEQUENCE { bandClass cellReselectionPriority threshX-High threshX-Low } } csfb-RegistrationParam1XRTT-v920{ powerDownReg-r9 } } A valid value. bc4. spare7. bc13.2C. spare11.2-4 multipleSID TRUE multipleNID TRUE homeReg TRUE foreignSIDReg TRUE foreignNIDReg TRUE parameterReg TRUE powerUpReg TRUE registrationPeriod ’0000000’ registrationZone totalZone Registration zone under test For Signalling test cases.4. 1 (2014-12) Procedure Table 4.Release 12 4.4.2C.2C.5.3-2: UE registration with 1xRTT pre-registration procedure (state 1 to state 2C) Step Procedure U-S - 1 to 16 16A Message Sequence Message Same procedure for steps 1 to 16 as specified in the procedure in clause 4. 18 The SS transmits a DLInformationTransfer <-DLInformationTransfer containing a 1x RTT GCSNA Encapsulated Registration Accept Order on Cell 1. the "lower case letter" identifies a step sequence that takes place if one of those is supported/configured.4 Specific message contents All specific message contents shall be referred to clause 4.5A.5A.508 subclause 4. 19 The SS transmits an RRCConnectionRelease <-RRCConnectionRelease message on Cell 1. Table 4.17 20b1 IF MULTI_PDN AND NOT pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36.5. 17 The UE transmits an ULInformationTransfer --> ULInformationTransfer containing a 1xRTT GCSNA Encapsulated Registration message on Cell 1.5.5.2.3-3: Void 4.7A with the exceptions below.18 Note: Message contents of tunnelled CDMA2000 messages (steps 17-18) are not checked in terms of conformance testing.5.508 V12. 4.2C.6. 17A The SS transmits a DLInformationTransfer <-DLInformationTransfer containing a GCSNA Ack message on Cell 1.2C.7 and 4.3-1 shows the cell power levels after the preamble.2C.508 subclause 4.2C.3 144 3GPP TS 36. 3GPP .3-1: Time instances of cell power level and parameter changes Parameter Cell-specific RS EPRE T0 Unit dBm/15kHz Cell 1 -60 Remark - Table 4. EXCEPTION: Steps 20a1 to 20b1 describe behaviour that depends on UE capabilities/configuration. 20a1 IF MULTI_PDN AND pc_UE_supports_user_initiated_PDN_discon nect THEN the non-IMS PDN shall be released as specified in TS 36. Table 4.3 The UE transmits a --> CSFBParametersRequestCDMA2000 CSFBParametersRequestCDMA2000 on Cell 1? 16B The SS transmits a <-CSFBParametersResponseCDMA2000 CSFBParametersResponseCDMA2000 on Cell 1.5.5. 1-2 Information Element CSFBParametersResponseCDMA2000 ::= SEQUENCE { criticalExtensions CHOICE { csfbParametersResponseCDMA2000-r8 SEQUENCE { Rand mobilityParameters Value/remark Random Challenge Data set by SS Set according to Table 4.5.5.5.5.4.3-2) Derivation Path: 36.Release 12 145 3GPP TS 36.3-2) Derivation Path: Table 4.1-16 Information Element RRCConnectionRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionRequest-r8 SEQUENCE { ue-Identity } } } Value/remark Comment Condition Any allowed value Table 4.2C. Table 4.2C.1 (2014-12) Table 4.5.1-23 Information Element UECapabilityInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ ueCapabilityInformation-r8 } } } Value/remark Comment Condition Any allowed value Table 4.4-3: Void Table 4. Table 4.5.5.2C.4-2: UECapabilityInformation (Step 13.4-5: CSFBParametersResponseCDMA2000 (Step 16B.4-4: Void Table 4.5.508 V12.2C.6.5.4-1: RRCConnectionRequest (Step 2.2C.2C. Table 4.3-2) Derivation Path: Table 4.4-6 } } } 3GPP Comment Condition .6.2C.2C.6.508 Table 4.2C. 2C.3-2) 3GPP .5.4. Table 4.Release 12 146 3GPP TS 36.5.508 V12.4-6: mobilityParameters (CDMA2000Parameters) (Step 16B.1 (2014-12) Table 4.2C. Release 12 Information Element RecordType SIDIncluded SID NIDIncluded NID REG_ZONEIncluded REG_ZONE TOTAL_ZONESIncluded TOTAL_ZONES ZONE_TIMERIncluded ZONE_TIMER PACKET_ZONE_IDIncluded PACKET_ZONE_ID PZIDHystParametersIncluded PZ_HYST_ENABLED PZ_HYST_INFO_INCL PZ_HYST_LIST_LEN PZ_HYST_ACT_TIMER PZ_HYST_TIMER_MUL PZ_HYST_TIMER_EXP P_REVIncluded P_REV MIN_P_REVIncluded MIN_P_REV ‘0’B NEG_SLOT_CYCLE_INDEX_SUPIncluded NEG_SLOT_CYCLE_INDEX_SUP ENCRYPT_MODEIncluded ENCRYPT_MODE ENC_SUPPORTEDIncluded ENC_SUPPORTED SIG_ENCRYPT_SUPIncluded SIG_ENCRYPT_SUP MSG_INTEGRITY_SUPIncluded MSG_INTEGRITY_SUP SIG_INTEGRITY_SUP_INCLIncluded SIG_INTEGRITY_SUP_INCL SIG_INTEGRITY_SUPIncluded SIG_INTEGRITY_SUP AUTHIncluded AUTH MAX_NUM_ALT_SOIncluded MAX_NUM_ALT_SO USE_SYNC_IDIncluded USE_SYNC_ID MS_INIT_POS_LOC_SUP_INDIncluded MS_INIT_POS_LOC_SUP_IND MOB_QOSIncluded MOB_QOS BAND_CLASS_INFO_REQIncluded BAND_CLASS_INFO_REQ BAND_CLASSIncluded BAND_CLASS BYPASS_REG_INDIncluded BYPASS_REG_IND ‘0’B ALT_BAND_CLASSIncluded ALT_BAND_CLASS MAX_ADD_SERV_INSTANCEIncluded MAX_ADD_SERV_INSTANCE HOME_REGIncluded HOME_REG FOR_SID_REGIncluded FOR_SID_REG FOR_NID_REGIncluded FOR_NID_REG 147 Value/remark ‘00000000’B ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘0’B Not present ‘0’B Not present Not present Not present Not present Not present Not present ‘1’B ’00000110’B ‘1’B ’00000110’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘1’B ‘00’B ‘1’B ‘000’B ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘1’B ‘00000’B ‘0’B Not present Not present ‘0’B Not present ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘1’B The same as SIB8 3GPP 3GPP TS 36.508 V12.4.1 (2014-12) Comment Condition . 4.Release 12 POWER_UP_REGIncluded POWER_UP_REG POWER_DOWN_REGIncluded POWER_DOWN_REG PARAMETER_REGIncluded PARAMETER_REG REG_PRDIncluded REG_PRD REG_DISTIncluded REG_DIST PREF_MSID_TYPEIncluded PREF_MSID_TYPE EXT_PREF_MSID_TYPEIncluded EXT_PREF_MSID_TYPE MEID_REQDIncluded MEID_REQD MCCIncluded MCC IMSI_11_12Included IMSI_11_12 IMSI_T_SUPPORTEDIncluded IMSI_T_SUPPORTED RECONNECT_MSG_INDIncluded RECONNECT_MSG_IND RER_MODE_SUPPORTEDIncluded RER_MODE_SUPPORTED TKZ_MODE_SUPPORTEDIncluded TKZ_MODE_SUPPORTED TKZ_IDIncluded TKZ_ID PILOT_REPORTIncluded PILOT_REPORT PILOT_REPORT SDB_SUPPORTEDIncluded SDB_SUPPORTED AUTO_FCSO_ALLOWEDIncluded AUTO_FCSO_ALLOWED SDB_IN_RCNM_INDIncluded SDB_IN_RCNM_IND FPC_FCH_Included FPC_FCH_INIT_SETPT_RC3 FPC_FCH_INIT_SETPT_RC4 FPC_FCH_INIT_SETPT_RC5 FPC_FCH_INIT_SETPT_RC11 FPC_FCH_INIT_SETPT_RC12 T_ADD_Included T_ADD PILOT_INC_Included PILOT_INC RAND_Included RAND LP_SEC_Included LP_SEC LTM_OFF_Included LTM_OFF DAYLT_Included DAYLT GCSNAL2AckTimer_Included GCSNAL2AckTimer GCSNASequenceContextTimer_Incl uded GCSNASequenceContextTimer 148 ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘1’B The same as SIB8 ‘0’B Not present ‘1’B ’11’B ‘0’B Not present ‘0’B Not present ‘1’B See the Table 4.508 V12.2-4 Note 1. Note 2 ‘1’B See the Table 4.4.2-4 Note 1.1 (2014-12) .4. Note 2 ‘1’B ’0’B ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘0’B Not present ‘1’B ’00011000’B ’00011000’B ’00011000’B ’00000000’B ’00000000’B ‘0’B Not present ‘1’B ’0010’B ‘0’B Not present ‘1’B ‘00000000’B ‘1’B ‘000000’B ‘1’B ‘0’B ‘1’B ‘00000001’B ‘1’B ‘00000101’B 3GPP 3GPP TS 36. 4. Table 4.3-2) Derivation Path: 36. Set by UE ‘0000000’B 16 bits.5.1 (2014-12) Table 4.2C.5.4-8 } } } } } Table 4.6.5. Set by UE 8 bits.508 V12.5.1-25 Information Element ULInformationTransfer ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransfer-r8 SEQUENCE { dedicatedInformationType CHOICE { dedicatedInfoCDMA2000-1XRTT Value/remark Comment Condition Set according to Table 4. Table 4.2C.2C. Set by UE Variable.3-2) MessageID Information Element Value/remark ‘00000001’B GCSNAOption AlternativeGCSNAOption_INCL IWSIDIncl AckRequired StopDupDetect MessageSequence NumTLACEncapsulated1xL3PDU Reserved 1xLogicalChannel 1xProtocolRevision MsgType ‘00000001’B ‘0’B ‘0’B ‘1’B ‘0’B Set by UE ‘00’B ‘0000’B ‘0’B ’00000110’B ‘00000001’B NumTLACHeaderRecords TLACHeaderRecordType TLACHeaderRecordLength MSID_TYPE MSID_LEN MSID Reserved 1xL3PDULength REG_TYPE ‘0001’B ‘0000’B 8 bits.4-7: ULInformationTransfer (Step 17.4-8: 1xRTT GCSNA Encapsulated Registration message (Step 17. Set by UE ‘0001’B SLOT_CYCLE_INDEX MOB_P_REV SCM MOB_TERM RETURN_CAUSE QPCH_SUPPORTED ENHANCED_RC UZID_INCL ‘010’B 8 bits.5.2C. Set by UE ‘1’B ‘1’B ‘1’B ‘1’B ‘0’B 3GPP Comment GCSNA1xCircuitS ervice message Registration message Power up registration Condition .2C.Release 12 149 3GPP TS 36. Set by UE ‘011’B 4 bits.508 Table 4. 4. Table 4.7. 3GPP .4.2C. Table 4. as defined in subclause 4.Release 12 150 3GPP TS 36. User Equipment: - The UE shall be in Registered.4.5. Idle Mode state (State 2).2C.4.2 Information Element EPS attach result EMM cause Value/remark '0001'B '0001 0010'B Comment EPS only #18 “CS domain not available” Condition combined_E PS_IMSI 4.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.1 (2014-12) Table 4. 4. Set by SS ‘00’B ‘0000’B ‘0’B ’00000110’B ‘00000111’B ‘0000’B ‘000’B 16 bits.508 clause 4.2C.4-10: ATTACH ACCEPT (Step 14.5. unless otherwise specified in the test case. once it is finalised RAN5 can refer to them accordingly.2C.5.3 Generic Radio Bearer Establishment (State 3) Editor note: The default parameter and system information will depend on progress in Clause 4.508 V12.5. Set by SS ‘011011’B ADD_RECORD_LEN ORDQ ‘001’B ‘00000000’B Comment Condition Order message Registration Accept Order Table 4.5.4-9: 1xRTT CS Registration Accept Order (Step 18.5.3.3-2) Derivation Path: 36.3-2) Information Element MessageID GCSNAOption AlternativeGCSNAOption_INCL IWSIDIncl AckRequired StopDupDetect MessageSequence NumTLACEncapsulated1xL3PDU Reserved 1xLogicalChannel 1xProtocolRevision MsgType NumTLACHeaderRecords Reserved 1xL3PDULength ORDER Value/remark ‘00000001’B ‘00000001’B ‘0’B ‘0’B ‘0’B ‘0’B 6 bits.5.2 Definition of system information messages The default system information messages are used.3. 5.4.3.3 151 3GPP TS 36.3.3-1: Generic Radio Bearer establishment procedure (state 2 to state 3) 3GPP .Release 12 4.1 (2014-12) Procedure The establishment of generic radio bearer connection is assumed to always be mobile terminated.5.508 V12. Table 4. IF N  1 (see step 8). EXCEPTION: the steps 9 and 10a1 to 10a3 (if present) happen in any order.Release 12 Step 1 2 3 4 5 6 7 8 9 10a1 10a2 10a3 10a4 152 Procedure SS sends a Paging message to the UE on the appropriate paging block. UE transmits an RRCConnectionRequest message. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message. IF N  2 (see step 8). the RRCConnectionReconfiguration message contains the configuration of these additional data radio bearers in the drb-ToAddModify IE and one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer. The UE transmits a SecurityModeComplete message and establishes the initial security configuration. the UE transmits an ACTIVATE DEDICATED EPS BEARER U-S <-<-- --> <-- 3GPP TS 36. associated with the default EPS bearer context..508 V12.1 (2014-12) Message Sequence Message RRC: SYSTEM INFORMATION (BCCH) RRC: Paging (PCCH) RRC: RRCConnectionRequest RRC: RRCConnectionSetup --> RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST . the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 3rd ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8. IF the test case using state 3 as an initial state is using N additional data radio bearers (0 ≤ N ≤ 7). m) where n and m are the number of DRBs associated with dedicated EPS bearer contexts and configured respectively with RLC-AM and RLC-UM (n+m = N). The SS configures a new data radio bearer. ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST - - --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT --> RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT --> RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT --> RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS 3GPP . SS transmit an RRCConnectionSetup message. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer..4. the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 2nd ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8. (State3) The SS transmits a SecurityModeCommand message to activate AS security. IF N  4 (see step 8). and including the UE identity in one entry of the IE pagingRecordLists. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1+n. the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 1st ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8. IF N  3 (see step 8). associated with the default EPS bearer context. the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 6th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.7. 4.Release 12 10a5 10a6 10a7 153 CONTEXT ACCEPT message matching with the 4th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8. IF N  5 (see step 8). the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 5th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8. 4. 4.7A. Idle Mode state. 4.4.5. UE Test Mode Activated (State 3A) Editor's note: The default parameter and system information will depend on progress in Clause 4. Idle Mode state.5. IF N = 7 (see step 8).3A.5.7 and 4. unless otherwise specified in the test case.1 (2014-12) BEARER CONTEXT ACCEPT --> RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT --> RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT --> RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT Specific message contents All specific message contents shall be referred to clause 4. 4. UE Test Mode Activated (State 2A-RF for RF and RRM testing).6.4.5.3A Generic Radio Bearer Establishment.5.3A.3A.5.4. the UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message matching with the 7th ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message included in step 8.3 Procedure Same procedure as specified in the procedure in clause 4. IF N  6 (see step 8). 4. 4. once it is finalised RAN5 can refer to them accordingly.6 and 4.508 V12.3A. as defined in subclause 4.3. - The UE shall be in Registered.2 Definition of system information messages The default system information messages are used.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. UE Test Mode Activated (State 2A for Signalling testing).5. 3GPP .4 Specific message contents All specific message contents shall be referred to clause 4.3. User Equipment: - The UE shall be in Registered.3.4 3GPP TS 36. 4. User Equipment: - The UE shall be in Registered.5. 4.3 Procedure Same procedure as specified in the procedure in clause 4. 4.3.6. as defined in subclause 4.3 Procedure Same procedure as specified in the procedure in clause 4.3C Generic Radio Bearer Establishment. pre-registered on 1xRTT (State 3C) Editor note: The default parameter and system information will depend on progress in Clause 4. 4. 4.3B Generic Radio Bearer Establishment.2 Definition of system information messages The default system information messages are used.3C.Release 12 154 3GPP TS 36. once it is finalised RAN5 can refer to them accordingly.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. Idle Mode state.5. unless otherwise specified in the test case.3B. pre-registered on HRPD (State 2B). 4.3. 4.4. pre-registered on HRPD (State 3B) Editor note: The default parameter and system information will depend on progress in Clause 4. unless otherwise specified in the test case. 4.5.3C.6. once it is finalised RAN5 can refer to them accordingly.4.4 Specific message contents All specific message contents shall be referred to clause 4.3B.7A.3C.4.7 and 4.5.2 Definition of system information messages The default system information messages are used.3B.3.7 and 4.5.5. 4.4 Specific message contents All specific message contents shall be referred to clause 4.5.5. 4.5.4. 3GPP . User Equipment: - The UE shall be in Registered.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.3B. 4.7A.5. pre-registered on 1xRTT (State 2C).5. as defined in subclause 4.1 (2014-12) 4. 4.5.3. Idle Mode state.508 V12.3C. 4 Direction UE .5.5. - Cell 1 has a lower reselection priority than Cell 15.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.5.7A. 4.508 V12. 4.4.5.5. User Equipment: - The UE shall be in Generic RB Establishment state.2 Definition of system information messages The default overhead messages as specified in clause 4.3 Procedure Table 4.4.4 Loopback Activation (State 4) 4.3-1: Loopback activation procedure (state 3A to state 4) Step Procedure 1 The SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. 3GPP .5.4.5. 4.4.SS <---> Message Sequence Message RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE Specific message contents All specific message contents shall be referred to clause 4.5 HRPD registration (State H2) Editor's note: The default parameter and system information will depend on progress in Clause 4.4.3 Procedure Editor note: procedure needs to be specified.5.1 (2014-12) 4.Release 12 155 3GPP TS 36. as defined in subclause 4.5. - Cell 15 is transmitting default overhead messages. User Equipment: - The Test USIM shall be inserted (State 1). The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated (State 4).6 and 4.5: 4. 2 4.4.5. 4. 4.4 are used.5. UE Test Mode Activated (State 3A). 4.4.5. once it is finalised RAN5 can refer to them accordingly. unless otherwise specified in the test case.2 Definition of system information messages The default system information messages are used.1 Initial conditions System Simulator: - Cell 1 and Cell 15. 6. 4.5A HRPD registration.5A.4.4.4 Specific message contents Editor's note: message contents need to be specified where necessary.5A.5.1 (2014-12) Specific message contents Editor's note: message contents need to be specified where necessary. 4.5. 3GPP .4.2 Definition of system information messages The default overhead messages as specified in clause 4. unless otherwise specified in the test case.2 Definition of system information messages The default overhead messages as specified in clause 4. 4.6.1 Initial conditions System Simulator: - Cell 1 and Cell 15. pre-registration on E-UTRAN (State H2A) Editor's note: The default parameter and system information will depend on progress in Clause 4. - Cell 1 has a lower reselection priority than Cell 15. Dormant Mode state (State H2). 4.4 156 3GPP TS 36.6 HRPD session establishment (State H3) Editor's note: The default parameter and system information will depend on progress in Clause 4.5A.5.5. 4. - Cell 15 is transmitting default overhead messages.4 are used.3 Procedure Editor's note: procedure needs to be specified.5. once it is finalised RAN5 can refer to them accordingly.3 Procedure Editor's note: procedure needs to be specified. User Equipment: - The Test USIM shall be inserted (State 1).5.5.5.4 are used.5.5.Release 12 4. 4. once it is finalised RAN5 can refer to them accordingly.508 V12.5A. 4. 4. 4.5. as defined in subclause 4.4.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. User Equipment: - The UE shall be in HRPD Registered.6. 4. pre-registered on E-UTRAN state (State H2A).4.5.1 (2014-12) Specific message contents Editor's note: message contents need to be specified where necessary.508 V12.6.5. shall advance to the next specified step. as defined in subclause 4.1 Procedure for IP address allocation in the U-plane The purpose of this procedure is to allow the successful completion of IP address allocation if it is initiated by the UE therefore the result from the execution of the Procedure for IP address allocation in the U-plane shall not lead to assignment of a verdict.3 4.6.5.6A. pre-registered on E-UTRAN (State H3A) Editor's note: The default parameter and system information will depend on progress in Clause 4.4. 3GPP .5A Other generic procedures 4.6A. Dormant Mode.5.6A HRPD session establishment.5. 4. unless otherwise specified in the test case.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. from which the Procedure for IP address allocation in the U-plane is called.6A. once it is finalised RAN5 can refer to them accordingly.4 157 3GPP TS 36.3 Procedure Same procedure as specified in the procedure in clause 4. User Equipment: - The UE shall be in HRPD Registered.5A.5.2 sec is suggested within which the procedure is expected to start.4 are used.6A.Release 12 4.2 Definition of system information messages The default overhead messages as specified in clause 4. If the timer expires then the test procedure. Depending on the UE configuration there may be unpredictable delay in the start of the procedure. 4. A guarding time of 1. 4.4 Specific message contents Editor's note: message contents need to be specified where necessary. 4.4.5. 2.5A. EXCEPTION: In parallel to the event described in step 1 below the step specified in Table 4.5A. <-- 3GPP .Release 12 158 3GPP TS 36.1 (2014-12) Table 4.2.1-1: Tracking area updating procedure Step 1 2 3 4 5 Procedure The SS transmits system information on the cell specified in the test case.508 V12.4. SS transmits an RRCConnectionSetup message.2 Tracking area updating procedure The procedure is defined in table 4. U-S <---> <-- Message Sequence Message RRC: SYSTEM INFORMATION (BCCH) RRC: RRCConnectionRequest RRC: RRCConnectionSetup --> RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST <-- RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE RRC: RRCConnectionRelease 6 The UE transmits a TRACKING AREA UPDATE COMPLETE --> 7 The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE. The UE transmits an RRCConnectionRequest message on the cell specified in the test case.1-2: Procedure for IP address allocation in the U-plane.1-1: Procedure for IP address allocation in the U-plane Step - 1 Procedure EXCEPTION: Step 1 below and Step 1 in Table 4. U-S - Message Sequence Message - 4. SS responds with TRACKING AREA UPDATE ACCEPT message. If the "PDN type" in the latest PDN CONNECTIVITY REQUEST message prior to this procedure was 'IPv4' or 'IPv4v6' then.5A. Table 4.1-2 may take place.5A.5A. parallel behaviour Step 1 Procedure If the "PDN type" in the latest PDN CONNECTIVITY REQUEST message prior to this procedure was 'IPv6' or 'IPv4v6' then stateless address auto configuration occurs on the user plane bearer established for the default EPS bearer context activated with the latest ACTIVATE DEFAULT EPS BEARER CONTEXT message prior to this procedure.1-1.5A.1-2 describe behaviour that depends on the contents of the latest PDN CONNECTIVITY REQUEST message sent by the UE prior to this procedure.5A. Message Sequence Message U-S - - - - - - Table 4. IPv4 address allocation by DHCPv4 may occur on the user plane bearer established for the default EPS bearer context activated with the latest ACTIVATE DEFAULT EPS BEARER CONTEXT message prior to this procedure. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area. 229 [40] clause 5.1 (2014-12) NOTE 1: The periodic tracking area updating timer T3412 is deactivated by default during the attach procedure (TS 36. Table 4. User Equipment: - The UE shall be in Registered.Release 12 159 3GPP TS 36.1. NOTE 2: The SS does not initiate authentication and NAS SECURITY MODE COMMAND are not performed (reuse of keys allocated during the attach procedure). unless otherwise specified in the test case. The SS waits for Timer_1 expiry Message Sequence Message U-S - - - - - - - - - - Depending on the UE configuration there may be unpredictable delay in the start of the procedure.4. 4.4 Generic Test Procedure for IMS Emergency call establishment in EUTRA: Normal Service 4. The procedure is applicable for UEs with IMS support (TS 36. Idle Mode state (State 2). The UE may initiate IMS registration according TS 24. 3GPP .3 Procedure The establishment of IMS emergency call is assumed to always be mobile originated. from which the Procedure for IMS signalling Uplane is called. A guarding time of [10] sec is suggested within which the procedure is expected to start.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. as defined in subclause 4. 4.5A. If the timer expires then the test procedure.5A. 4.4.2 Definition of system information messages The default system information messages are used.3 Procedure for IMS signalling The purpose of this procedure is to allow the successful completion of IMS signalling if it is initiated by the UE.2).2291 [43] subclause C.4-1/25).4.508 clause 4.5A.523-2 A.5A. shall advance to the next specified step 4.4.508 V12.3-1: Procedure for IMS signalling in the U-plane Step Procedure 1-9 10a1 10a2 a110a2 a9 10a2 b1 Note 1: Void EXCEPTION: Steps 10a1 to 10a2b1 describe a transaction that depends on the UE capability IF pc_IMS then the SS starts timer Timer_1 = 10 s (Note 1) EXCEPTION: Steps 10a2a1 to 10a2b1 describe a transaction that depends on the UE implementation Registration procedure according TS 34.5A.5A.4.4.2 (steps 3-11) Note: SS cancels timer Timer_1 at step 10a2a1.7. 4.5A.Release 12 160 3GPP TS 36.1 (2014-12) Table 4.508 V12.3-1: EUTRA/EPS signalling for IMS Emergency Call 3GPP .4. The DRB associated with default EPS bearer context obtained during the attach procedure is established The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. associated with the dedicated EPS bearer context. Note: The APN is set to the test APN defined for emergency bearer services.Release 12 St 1 2 3 4 5 6 7 8 9 10 - 11 12 13 14 161 3GPP TS 36.508 V12. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message. RRCConnectionReconfiguration message contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.4. The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN. SS transmit an RRCConnectionSetup message. the behaviour in table 4.5A.1 (2014-12) Procedure Make the UE attempt an IMS emergency call The UE transmits an RRCConnectionRequest message with ' establishmentCause' set to 'emergency'.6. The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message. EXCEPTION: In parallel to the events described in steps 11 to 15 below. Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 10 The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. associated with the default EPS bearer context. associated with the default EPS bearer context. The SS configures a new data radio bearer. EPS bearer context #4 (QCI 1) according to table 6. 3GPP U-S --> Message Sequence Message RRCConnectionRequest <---> RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> RRC: RRCConnectionReconfigurationComplet e --> PDN CONNECTIVITY REQUEST <-- RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST - - --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST <-- --> RRC: RRCConnectionReconfigurationComplet e .6. associated with the default EPS bearer context. The SS transmits a SecurityModeCommand message to activate AS security. associated with the default EPS bearer for emergency IMS signalling. The SS configures a new data radio bearer.1-1: Reference default EPS bearer context is used.4. 0). EPS bearer context #2 (QCI 5) according to table 6. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. (Optional IP address allocation followed by IMS emergency registration and IMS emergency speech call establishment) The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. The SS configures a new RLC-UM data radio bearer.2-1: Reference dedicated EPS bearer contexts is used.3-2 occurs. associated with the default EPS bearer for emergency call. The UE transmits a SecurityModeComplete message and establishes the initial security configuration. with 'Request type' set to 'emergency ('0100'B )'. 3-6 and table 4.6. Steps 1-4 expected sequence defined in annex C.6.1 takes place performing IP address allocation in the Uplane.4.1-8 with condition AM-DRB-ADD(2) Information Element Value/Remark Access point name APN-1 EPS QoS According to reference default EPS bearer context #2 – in table 6.4-3: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 13.3-3 and table 4.4.5A.3-2: Parallel behaviour St 1 2-5 610 Procedure EXCEPTION: Step 1 describes behaviour that depends on the UE behaviour. Emergency registration procedure is performed.22 of TS 34. 4.in table 6.6.7.4.508 V12.7. IMS Emergency call for EPS is established.3-1) Derivation path: Table 4.3-1) Derivation path: Table 4.5A.229-1 [35].2-1 3GPP Comment SS defines an additional dedicated EPS QoS Condition .5A.Release 12 15 162 3GPP TS 36.7 with the exceptions below. Table 4.6 and 4.6.1-1 Comment SS uses the test APN defined for emergency bearer services SS defines an additional dedicated EPS QoS Condition Table 4.4.5A.4.1-8 with condition UM-DRB-ADD(3) Information Element Value/Remark Linked EPS bearer identity Default EBId-2 (same value like in table 4.4 Message Sequence Message U-S - - - - - - - - Specific message contents All specific message contents shall be referred to clause 4.4-1: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 10.6.2291 [35].508 subclause 4.4.1 (2014-12) The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.4-1) EPS QoS According to reference dedicated EPS bearer context #1 .20 of TS 34.5A. Table 4.2-1 TFT According to reference dedicated EPS bearer context #1 . If initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.5A.4. Steps 1-5 defined in annex C.in table 6.4. Table 4.5A.5A. --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT Table 4. 3GPP .508 V12. as defined in subclause 4.5. User Equipment: - The UE is switched on and camped on the cell in EMM-DEREGISTERED.2 Definition of system information messages The default system information messages are used.5A.Release 12 163 3GPP TS 36.5 Generic Test Procedure for IMS Emergency call establishment in EUTRA: Limited Service 4.4.LIMITED-SERVICE state.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. unless otherwise specified in the test case. 4.5A.1 (2014-12) 4.5A.5.4. Table 4.3-1: EUTRA/EPS signalling for IMS Emergency Call in limited service 3GPP .Release 12 4.1 (2014-12) Procedure The establishment of IMS emergency call is assumed to always be mobile originated.508 V12.4.5A.5.5A.3 164 3GPP TS 36.5. and EEA0 (NULL ciphering) algorithms are used. the "lower case letter" identifies a step sequence that takes place if the UE is in a particular state. The SS transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure. EXCEPTION: Steps 5a2a1 to 5a2b1 describe behaviour that depends on the UE state. The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. the "lower case letter" identifies a step sequence that take place if the UE has ESM information which needs to be transferred. UE transmits an AUTHENTICATION FAILURE message with EMM cause #20 "MAC failure" or EMM cause #21 "synch failure". SS transmits an RRCConnectionSetup message. EPS attach type set to “EPS emergency attach" ('0110'B). IF the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the SS transmits an ESM INFORMATION REQUEST message to initiate exchange of protocol configuration options and/or APN. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message. UE transmits an AUTHENTICATION RESPONSE message and establishes mutual authentication. The UE transmits an ESM INFORMATION RESPONSE message to transfer protocol configuration options and/or APN.1 (2014-12) Procedure Make the UE attempt an IMS emergency call The UE transmits an RRCConnectionRequest message with 'establishmentCause' set to 'emergency'. The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration. KSI value is set to "000" and EIA0 (NULL integrity). EXCEPTION: Steps 5a1 to 5a2b1 describe behaviour that depends on the UE ID sent in the ATTACH REQUEST message in step 4 and take place only if the UE does not send IMEI. Note: If UE has sent Authentication Failure in U-S --> <---> - <-- Message Sequence Message RRCConnectionRequest RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: ATTACH REQUEST NAS: PDN CONNECTIVITY REQUEST - RRC: DLInformationTransfer NAS: AUTHENTICATION REQUEST - --> RRC: ULInformationTransfer NAS: AUTHENTICATION RESPONSE --> RRC: ULInformationTransfer NAS: AUTHENTICATION FAILURE - RRC: DLInformationTransfer NAS: SECURITY MODE COMMAND <-- --> - RRC: ULInformationTransfer NAS: SECURITY MODE COMPLETE - <-- RRC: DLInformationTransfer NAS: ESM INFORMATION REQUEST --> RRC: ULInformationTransfer NAS: ESM INFORMATION RESPONSE <-- RRC: SecurityModeCommand 3GPP . with 'Request type' set to 'emergency ('0100'B)'.508 V12. Note: If UE has sent Authentication Failure in step 5a2b16b1 or the behaviour described in steps 5a1 to 5a2b1 does not take place. The SS transmits a SecurityModeCommand message to activate AS security.Release 12 St 1 2 3 4 - 5a1 - 5a2 a1 5a2 b1 6a1 6b1 7 8 - 9a1 9a2 10 165 3GPP TS 36. EXCEPTION: Steps 9a1 to 9a2 describe behaviour that depends on UE configuration.4. (Note 2) Void Void The SS transmits a NAS SECURITY MODE COMMAND message to activate NAS security selecting. 6. The SS transmits a UECapabilityEnquiry message to initiate the UE radio access capability transfer procedure. (Optional IP address allocation followed by IMS emergency speech call establishment) The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of default bearer. The UE transmits a SecurityModeComplete message and establishes the initial security configuration. The SS transmits an RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1. then. is established. associated with the dedicated EPS bearer context.Release 12 11 12 13 14 - 15 16 17 step 5a2b1. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT. eia0 (NULL integrity). RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. associated with the default EPS bearer for emergency IMS signalling. or the behaviour described in steps 5a1 to 5a2b1 does not take place. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE. The DRB associated with default EPS bearer context #2 (QCI 5) according to table 6. The UE transmits a UECapabilityInformation message to transfer UE radio access capability. 0).4. This message includes the ATTACH COMPLETE message.3-2 occurs. 18 19 Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 10 The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. the behaviour in table 4.1 (2014-12) --> RRC: SecurityModeComplete <-- RRC: UECapabilityEnquiry --> RRC: UECapabilityInformation <-- RRC: RRCConnectionReconfiguration NAS: ATTACH ACCEPT NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST - - --> RRC: RRCConnectionReconfigurationComplete --> RRC: ULInformationTransfer NAS: ATTACH COMPLETE NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT <-- RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST --> RRC: RRCConnectionReconfigurationComplete --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT EPS bearer context #4 (QCI 1) according to table 6. Note: The APN is set to the test APN defined for emergency bearer services EXCEPTION: In parallel to the events described in steps 15 to 19 below. and eea0 (NULL ciphering) algorithms are used. The SS configures a new RLC-UM data radio bearer. 166 3GPP TS 36.6.508 V12. Note 1: Note 2: Void EMM cause #26 "non-EPS authentication unacceptable" is not expected to happen as SS will not set the "separation bit" in the AMF field of AUTN as 0 3GPP .2-1: Reference dedicated EPS bearer contexts is used. This message includes the ATTACH ACCEPT message with EPS attach result set to “EPS only" ('001'B).1-1: Reference default EPS bearer contexts.5. The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. obtained during the attach procedure.5A. 5.3-1).3-1).5A.22 of TS 34.4 Message Sequence Message U-S - - - - - - Specific message contents All specific message contents shall be referred to clause 4. Table 4.5A.5. Table 4. 1 2-6 4.5A. 3GPP . If initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.4.3-2: Parallel behaviour St Procedure - EXCEPTION: Step 1 describes behaviour that depends on the UE behaviour.Release 12 167 3GPP TS 36.1 (2014-12) Table 4.5.2-19 Information Element Type of integrity protection algorithm Type of ciphering algorithm NAS key set identifier NAS key set identifier Value/remark Set according to PIXIT parameter for default integrity protection algorithm EIA0 Comment NullAlgorith mUsed NOT NullAlgorith mUsed NullAlgorith mUsed Set according to PIXIT parameter for default ciphering algorithm EEA0 The valid NAS key set identifier.5A.6 and 4.5A.3-1) Derivation Path: Table 4.7.7 with the exceptions below. or the behaviour described in steps 5a1 to 5a2b1 does not take place (Table 4.5. Steps 1-5 defined in annex C.4-1: SECURITY MODE COMMAND (step 7.1 takes place performing IP address allocation in the Uplane.2291 [35].5.508 V12.5. IMS Emergency call for EPS is established. NOT NullAlgorith mUsed NullAlgorith mUsed '000'B TSC Spare half octet Condition NullAlgorithmUsed '0'B Condition NOT NullAlgorith mUsed native security context (for KSIASME) '0000'B Explanation UE has sent Authentication Failure in step 5ab1 (Table 4.5A.508 subclause 4.5A. 5A.3-1).5A.4-3: SecurityConfigSMC-LimitedService (Table 4.5A.5. or the behaviour described in steps 5a1 to 5a2b1 (Table 4.5A.6.2-1 TFT See Reference dedicated EPS bearer context #4 in table 6.1 (2014-12) Table 4.4-4) EPS QoS See Reference dedicated EPS bearer context #4 in table 6.3-1) Derivation Path: Table 4.3-1) does not take place.5A.4-2 Information Element SecurityConfigSMC.5A.6.5.5A.5A.5. Table 4.5.5.5.4-2) Derivation Path: Table 4.5A.5.1-8 with condition UM-DRB-ADD(3) Information Element Value/Remark Linked EPS bearer identity Default EBId-2 (same value as in table 4.4-3 } } } } Table 4.LimitedService ::= SEQUENCE { securityAlgorithmConfig SEQUENCE { Value/remark cipheringAlgorithm Set according to PIXIT parameter for default ciphering algorithm eea0 integrityProtAlgorithm Set according to PIXIT parameter for default integrity protection algorithm eia0 Comment Condition NOT NullAlgorith mUsed NullAlgorith mUsed NOT NullAlgorith mUsed NullAlgorith mUsed } Condition NullAlgorithmUsed Explanation UE has sent Authentication Failure in step 5a2b1 (Table 4.6.4-4: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 17.4.5A. Table 4.3-3 and table 4.Release 12 168 3GPP TS 36.6.6.1-19 Information Element SecurityModeCommand ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE{ securityModeCommand-r8 SEQUENCE { securityConfigSMC nonCriticalExtension SEQUENCE {} Value/remark Comment Condition RRCTransactionIdentifier-DL SecurityConfigSMCLimitedService Not present Table 4. Table 4.5.5.3-1) Derivation path: Table 4.508 V12.5.4-2: SecurityModeCommand (step 10.7.2-1 3GPP Comment Condition . Release 12 169 3GPP TS 36.5A. 4.7.6. User Equipment: - The UE shall be in Registered.4.1 (2014-12) Table 4.6. Table 4.5.508 V12.5A. unless otherwise specified in the test case.6.5.3-6 and table 4.5A.2 Definition of system information messages The default system information messages are used.3-1) Derivation path: Table 4.6 Generic Test Procedure for IMS MO speech call establishment in EUTRA 4.5A.5A. Idle Mode state (State 2).1-1 Comment SS uses the test APN defined for emergency bearer services SS defines an additional dedicated EPS bearer Condition 4.4.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. 3GPP .4-5: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 14.6.1-8 with condition AM-DRB-ADD(2) Information Element Value/Remark Access point name APN-1 EPS QoS According to reference default EPS bearer context #2 – in table 6. as defined in subclause 4. 5A. the behaviour in table 4.6.6.6.6. The UE transmits a SecurityModeComplete message and establishes the initial security configuration. UE sends INVITE. associated with the dedicated EPS bearer context.6.5A. U-S - 3GPP Message Sequence Message - . The SS transmits a SecurityModeCommand message to activate AS security. The DRB associated with default EPS bearer context obtained during the attach procedure is established EXCEPTION: In parallel to the events described in steps 8 below.1 (2014-12) Procedure Table 4.3-1: EUTRA/EPS signalling for IMS MO speech call St 1 2 3 4 5 6 7 8 9-11 12 - Procedure U-S --> Make the UE attempt an IMS speech call The UE transmits an RRCConnectionRequest message with ' establishmentCause' set to ' mo-Data '. SS transmit an RRCConnectionSetup message. (IMS MTSI MO speech call establishment) Message Sequence Message RRCConnectionRequest <---> RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> <-- - RRC: RRCConnectionReconfigurationComplet e RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST - 13 The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message. EXCEPTION: In parallel to the events described in steps 13-14 below.3 170 3GPP TS 36.3-2 occurs. associated with the default EPS bearer context.2-1: Reference dedicated EPS bearer contexts. MTSI MO speech call for EPS. 0). --> RRC: RRCConnectionReconfigurationComplet e 14 The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. EPS bearer context #4 (QCI 1) according to table 6. associated with the default EPS bearer context.1).3-3 occurs. (IMS MTSI MO speech call establishment) The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer.229-1 [35].21 of TS 34. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1. The SS configures a new data radio bearer.229-1 [35]. --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT Table 4.508 V12.Release 12 4. Steps 3-4 expected sequence defined in annex C. associated with the dedicated EPS bearer. The SS configures a new RLC-UM data radio bearer with condition DRB (0.5A.6. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.5A. the behaviour in table 4.3-2: Parallel behaviour St 1 Procedure Step 2 expected sequence defined in annex C.5A.4.21 of TS 34. MTSI MO speech call for EPS.7 Generic Test Procedure for IMS MT Speech call establishment in EUTRA 4.7.6.508 V12. as defined in subclause 4. 4. User Equipment: - The UE shall be in Registered.4 U-S - Message Sequence Message - Specific message contents All specific message contents shall be referred to clause 4.7.Release 12 171 3GPP TS 36. 4.229-1 [35].21 of TS 34.1 (2014-12) Table 4. unless otherwise specified in the test case.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.2 Definition of system information messages The default system information messages are used.5A. Idle Mode state (State 2). 3GPP .5A.7.5A. 4.5A.6.5A.4.4.3-3: Parallel behaviour St Procedure 1-8 Steps 5-13 expected sequence defined in annex C.6 and 4. 229-1 [35].11 of TS 34.229-1 [35]. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.5A. MTSI MT speech call. MTSI MT speech.5A. 1622 Steps 5-11 expected sequence defined in annex C.11 of TS 34. associated with the default EPS bearer context.Release 12 4. - RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT - 23A Step 11A expected sequence defined in annex C. associated with the dedicated EPS bearer. The SS transmits a SecurityModeCommand message to activate AS security.11 of TS 34.6 and 4.4. The UE transmits an RRCConnectionRequest message with ' establishmentCause' set to 'mt-Access'. and including the UE identity in one entry of the IE pagingRecordLists.3 172 3GPP TS 36. The DRB associated with default EPS bearer context obtained during the attach procedure is established The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. The UE transmits a SecurityModeComplete message and establishes the initial security configuration.508 V12. 0).1). The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. - - 4. associated with the default EPS bearer context.11 of TS 34.1 (2014-12) Procedure Table 4. U-S <-- Message Sequence Message RRC: Paging (PCCH) --> RRCConnectionRequest <---> RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> RRC: RRCConnectionReconfigurationComplet e - - <-- RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST --> RRC: RRCConnectionReconfigurationComplet e --> 15 The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. - - 2526 Steps 14-15 expected sequence defined in annex C.3-1: EUTRA/EPS signalling for IMS MT speech call St 1 2 3 4 5 6 7 8 9-12 13 14 Procedure SS sends a Paging message to the UE on the appropriate paging block. Steps 1-4 expected sequence defined in annex C. associated with the dedicated EPS bearer context.229-1 [35]. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1.7.7.229-1 [35]. MTSI MT speech.7. 3GPP . MTSI MT speech.229-1 [35]. The SS configures a new data radio bearer. MTSI MT speech. The SS configures a new RLC-UM data radio bearer with condition DRB (0.4 Specific message contents All specific message contents shall be referred to clause 4. - - 2324 Steps 12-13 expected sequence defined in annex C.5A.7. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.11 of TS 34. SS transmit an RRCConnectionSetup message. 8.Release 12 173 3GPP TS 36. as defined in subclause 4. 3GPP .5A.4.1 (2014-12) 4.5A.8. Idle Mode state (State 2).508 V12.4.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. unless otherwise specified in the test case.5A. User Equipment: - The UE shall be in Registered. 4.2 Definition of system information messages The default system information messages are used.8 Generic Test Procedure for IMS MO video call establishment in EUTRA 4. Message Sequence Message RRCConnectionRequest <---> RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> <-- - RRC: RRCConnectionReconfigurationComplet e RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST - --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT --> Table 4.6.3-2: Parallel behaviour St 1 Procedure Step 2 expected sequence defined in annex C.3-3 occurs. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1. The SS configures two new RLC-UM data radio bearers with condition DRB (0.5A. the behaviour in table 4. associated with the dedicated EPS bearer context.5A.508 V12. The SS configures a new data radio bearer. UE sends INVITE.5A.8. One EPS bearer context #4 (QCI 1) and one EPS bearer context #3 (QCI 2) according table 6.8.8.2-1: Reference dedicated EPS bearer contexts. The DRB associated with default EPS bearer context obtained during the attach procedure is established EXCEPTION: In parallel to the events described in steps 8 below.25 of TS 34.2). (IMS MTSI MO video call establishment) The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer.3-2 occurs. the behaviour in table 4. RRCConnectionReconfiguration message contains one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer. associated with the default EPS bearer context. The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the second bearer. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message. associated with the default EPS bearer context. SS transmit an RRCConnectionSetup message.2-1: Reference dedicated EPS bearer contexts.Release 12 4.5A.8.3 174 3GPP TS 36. (IMS MTSI MO video call establishment). The SS transmits a SecurityModeCommand message to activate AS security.3-1: EUTRA/EPS signalling for IMS MO video call St 1 2 3 4 5 6 7 8 9-11 12 13 14 15 Procedure U-S --> Make the UE attempt an IMS video call The UE transmits an RRCConnectionRequest message with ' establishmentCause' set to ' mo-Data '. associated with the dedicated EPS bearer. EXCEPTION: In parallel to the events described in steps 13-14 below.1 (2014-12) Procedure Table 4. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer.25 of TS 34.6.5A.229-1 [35]. 0). U-S - 3GPP Message Sequence Message - .8. The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer.4. The UE transmits a SecurityModeComplete message and establishes the initial security configuration. Steps 3-4 expected sequence defined in annex C. EPS bearer context #4 (QCI 1) according table to 6.229-1 [35]. MTSI MO video call for EPS. 6 and 4.8. Idle Mode state (State 2). User Equipment: - The UE shall be in Registered.508 V12.229-1 [35].3-3: Parallel behaviour St Procedure 1-8 Steps 5-13 expected sequence defined in annex C.5A.4.5A.4 U-S - Message Sequence Message - Specific message contents All specific message contents shall be referred to clause 4.9.8.9 Generic Test Procedure for IMS MT video call establishment in EUTRA 4.Release 12 175 3GPP TS 36. 4.1 (2014-12) Table 4.5A. as defined in subclause 4.5A.25 of TS 34. 4.5A. 3GPP .1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.9. MTSI MO video call for EPS.2 Definition of system information messages The default system information messages are used.4. 4. unless otherwise specified in the test case.7. MTSI MT video call. One EPS bearer context #4 (QCI 1) and one EPS bearer context #3 (QCI 2) according table 6. Steps 5-15 expected sequence defined in annex C. The DRB associated with default EPS bearer context obtained during the attach procedure is established The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer.229-1 [35]. 3GPP - - <-- RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT - --> - .5A. MTSI MT video call for EPS. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.2).7.6 and 4. SS transmit an RRCConnectionSetup message.9.5A. associated with the dedicated EPS bearer.9.508 V12. The SS configures a new RLC-UM data radio bearer with condition DRB (0. The UE transmits an RRCConnectionRequest message with ' establishmentCause' set to 'mt-Access'.26 of TS 34. The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the second bearer.229-1 [35]. associated with the dedicated EPS bearer context. The SS configures a new data radio bearer.26 of TS 34. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1.3-1: EUTRA/EPS signalling for IMS MT video call St 1 2 3 4 5 6 7 8 9-12 13 14 15 16 1727 Procedure SS sends a Paging message to the UE on the appropriate paging block.9.4 U-S <-- Message Sequence Message RRC: Paging (PCCH) --> RRCConnectionRequest <---> RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> RRC: RRCConnectionReconfigurationComplet e Specific message contents All specific message contents shall be referred to clause 4.2-1: Reference dedicated EPS bearer contexts.5A. The SS transmits a SecurityModeCommand message to activate AS security. associated with the default EPS bearer context.3 176 3GPP TS 36. RRCConnectionReconfiguration message contains one ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message per additional data radio bearer. 0). The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer. associated with the default EPS bearer context.4.1 (2014-12) Procedure Table 4. and including the UE identity in one entry of the IE pagingRecordLists. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. 4.6. The UE transmits a SecurityModeComplete message and establishes the initial security configuration.Release 12 4. Steps 1-4 expected sequence defined in annex C. 10 Generic Test Procedure for IMS MO speech and aSRVCC in EUTRA 4.2 Definition of system information messages The default system information messages are used. unless otherwise specified in the test case.508 V12.5A. User Equipment: - The UE shall be in Registered. 4. as defined in subclause 4.4.1 (2014-12) 4.10. 3GPP . Idle Mode state (State 2).10.Release 12 177 3GPP TS 36.5A.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.4.5A. 5A. The SS transmits a SecurityModeCommand message to activate AS security. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message. Initiate MTSI MO speech.508 V12. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1.6.3-2: Parallel behaviour St 1 Procedure Step 2 expected sequence defined in annex C. Message Sequence Message RRC: RRCConnectionReconfigurationComplet e RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST - --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT Table 4. associated with the dedicated EPS bearer context. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.3-3 occurs. MTSI MO speech call to alerting state.1 (2014-12) Procedure Table 4. the behaviour in table 4. the behaviour in table 4.3-1: EUTRA/EPS signalling for IMS MO speech to alerting state St 1 2 3 4 5 6 7 8 9-11 12 13 14 Procedure U-S --> Make the UE attempt an IMS speech call The UE transmits an RRCConnectionRequest message with ' establishmentCause' set to ' mo-Data '.1).3-2 occurs.10. The DRB associated with default EPS bearer context obtained during the attach procedure is established EXCEPTION: In parallel to the events described in steps 8 below.10.Release 12 4. 0). U-S - 3GPP Message Sequence Message - . The UE transmits a SecurityModeComplete message and establishes the initial security configuration. EXCEPTION: In parallel to the events described in steps 13-14 below. MTSI MO speech call for EPS.5A.229-1 [35].5A.5A.2-1: Reference dedicated EPS bearer contexts.21 of TS 34. The SS configures a new RLC-UM data radio bearer with condition DRB (0. UE sends INVITE.4. associated with the dedicated EPS bearer.10.229-1 [35]. RRCConnectionRequest <---> RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> <-- - The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.10. Steps 3-4 expected sequence defined in annex C.10.3 178 3GPP TS 36. EPS bearer context #4 (QCI 1) according to table 6. The SS configures a new data radio bearer. associated with the default EPS bearer context. SS transmit an RRCConnectionSetup message.21 of TS 34. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer.5A. associated with the default EPS bearer context. add video remove video.1. Steps 2-4 expected sequence defined in expected sequence test case 17.4 of TS 34.5A. The SS configures a new RLC-UM data radio bearer with condition DRB (0.4. 4.11.229-1 [35].3-1: EUTRA/EPS signalling for IMS MO add video St 1 2-4 5 6 7 Procedure Make the UE attempt add IMS video to the voice call.11.5A. 4.2 Definition of system information messages The default system information messages are used. 3GPP U-S <-- - Message Sequence Message RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST - --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT .11.6.6.11 Generic Test Procedure for IMS MO add video establishment in EUTRA 4. The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer.6. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. as defined in subclause 4. EPS bearer context #3 (QCI 2) according table to 6.10. the behaviour in table 4. 4.21 of TS 34.11.2-1: Reference dedicated EPS bearer contexts.229-1 [35].5A. EXCEPTION: In parallel to the events described in steps 6-7 below.4 U-S - Message Sequence Message - Specific message contents All specific message contents shall be referred to clause 4.3 Procedure Table 4.5A.5A.3-3: Parallel behaviour St Procedure 1-7 Steps 5-11 expected sequence defined in annex C.508 V12.5A.5A.10. 4.7.1). User Equipment: - The UE shall execute 4. (IMS MTSI MO video call establishment). associated with the dedicated EPS bearer.5A.5A. MTSI MO speech call to alerting state for EPS.3-2 occurs.6 and 4.11.1 (2014-12) Table 4.4. associated with the dedicated EPS bearer context.Release 12 179 3GPP TS 36. MO Speech. EPS bearer context #3 (QCI 2) according to table 6.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment. unless otherwise specified in the test case.2-1: Reference dedicated EPS bearer contexts. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer. 4. add video remove video.6.3-1: EUTRA/EPS signalling for IMS MT add video St 1-3 4 5 6 7-12 Procedure Steps 1-3 expected sequence defined in expected sequence test case 17.6 and 4. 4.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.1.229-1 [35].1). The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the first bearer. 3GPP U-S - Message Sequence Message - <-- RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT .5A.4. add video remove video. The SS configures a new RLC-UM data radio bearer with condition DRB (0.2-1: Reference dedicated EPS bearer contexts.2-1: Reference dedicated EPS bearer contexts.4 of TS 34. MT Speech.12. associated with the dedicated EPS bearer context.5A. associated with the dedicated EPS bearer.11.3 Procedure Table 4.12 Generic Test Procedure for IMS MT add video establishment in EUTRA 4. EPS bearer context #3 (QCI 2) according to table 6.3-2: Parallel behaviour St Procedure 1-6 Steps 5-10 expected sequence defined in test case 17. Steps 4-9 expected sequence defined in test case 17.5A.2. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #3 (QCI 2) according table to 6.12.508 V12.6. add video remove video.4 U-S - Message Sequence Message - Specific message contents All specific message contents shall be referred to clause 4.12.4. MT Speech.4 of TS 34. as defined in subclause 4.Release 12 180 3GPP TS 36.4 of TS 34. 4.7.229-1 [35].5A.229-1 [35].12.1.2 Definition of system information messages The default system information messages are used. User Equipment: - The UE shall execute 4.5A.5A.5A. unless otherwise specified in the test case.7.11. MO Speech.1 (2014-12) Table 4.5A. 4. 14.4.1 (2014-12) Specific message contents All specific message contents shall be referred to clause 4.13 Void 4. Idle Mode state (State 2).7.1 Initial conditions System Simulator: - Parameters are set to the default parameters for the basic single cell environment.4 181 3GPP TS 36. 4. - If pc_XCAP_only_APN==true then the UE is connected to the IMS PDN only - else the UE is connected to the IMS PDN and the Internet PDN which is used for XCAP signalling. as defined in subclause 4.4. 3GPP .14 Generic Test Procedure for IMS XCAP establishment in EUTRA 4.Release 12 4. 4.5A.6 and 4.5A. User Equipment: - The UE shall be in Registered.5A.5A.2 Definition of system information messages The default system information messages are used. unless otherwise specified in the test case.508 V12.14.12.5A. 4 U-S --> Message Sequence Message RRCConnectionRequest <---> RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> RRC: RRCConnectionReconfigurationComplet e Specific message contents All specific message contents shall be referred to clause 4.7. associated with the default EPS bearer context.16 (condition: NOT ADD_IMS) 4. The SS transmits a SecurityModeCommand message to activate AS security. The DRBs associated with the respective default EPS bearer context obtained during the attach procedure are established The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer.15.2 Definition of system information messages The system information messages applicable in the test case are used.15.5A. SS transmit an RRCConnectionSetup message. The EPS bearer has to be specified.5A. The SS configures a new data radio bearer. The UE transmits a SecurityModeComplete message and establishes the initial security configuration.Release 12 4. 0) in case of pc_XCAP_over_Internet_APN==true.15 Generic Test Procedure for EPS Bearer Deactivation 4.4.5A. 4.508 V12.6 and 4. The RRCConnectionReconfiguration message is using condition SRB2-DRB(1.1 (2014-12) Procedure Table 4.508 subclause 4. associated with the default EPS bearer context. The UE transmits an RRCConnectionRequest message with ' establishmentCause' set to 'mo-Data '.1 Initial conditions The EPS bearer to be deactivated has been established before.5A.3 182 3GPP TS 36. 4.5A.3-1: EUTRA/EPS signalling for XCAP St 1 2 3 4 5 6 7 8 Procedure Make the UE attempt XCAP signalling. EXCEPTION: IF pc_XCAP_only_APN THEN additional PDN connectivity shall be established as specified in TS 36.14. 0) in case of pc_XCAP_only_APN==true or using condition SRB2DRB(2.5A. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.14.5A.14. 3GPP . EXCEPTION: In parallel to the event described in step2 the step specified in Table 4.15.15.4-1: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 1.5A.4 U-S --> Message Sequence Message RRC: ULInformationTransfer NAS: DEACTIVATE EPS BEARER CONTEXT ACCEPT Specific message contents Table 4.3-1: Procedure for EPS Bearer Deactivation Step 1 2 3 Procedure The SS transmits an RRCConnectionReconfiguration message to deactivate an EPS bearer.15.3 183 3GPP TS 36.1 (2014-12) Procedure Table 4.3-12 and table 4.16 Generic Test Procedure to establish additional PDN connectivity The same assumptions and definitions apply as in clause 4.15.5A.5A.15.7.31) Derivation path: Table 4.5A.5.508 V12.3-2 should take place. Void U-S <---> - Message Sequence Message RRC: RRCConnectionReconfiguration NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST RRC: RRCConnectionReconfigurationComplete - Table 4. 4.5A.15.2and in addition: 3GPP .7.1-8 with condition and condition NETWORK-INITIATED Information Element Value/Remark Comment EPS bearer identity EPS bearer identity Same value as in the activation message. ESM cause 00100100 regular deactivation Condition Table 4.5A.4-2: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 2.6. Table 4.Release 12 4.3-11 Information Element EPS bearer identity Value/remark EPS bearer identity Procedure transaction identity 0 Comment The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.5A.3-2: Procedure for EPS Bearer Deactivation (parallel behaviour) Step 1 Procedure The UE transmits an ULInformationTransfer message to accept deactivation of the EPS bearer.3-1) Derivation Path:Table 4.5A.15. No procedure transaction identity assigned Condition 4. Table 4.15.5A.4. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the deactivation of EPS bearer.5A.15. 5A.5A.5. - The procedure shall be performed under ideal radio conditions as defined in clause 5 User Equipment: - The UE is in Registered.16. RRC_CONNECTED state (State 2). 4.5A.2.3 Procedure Table 4.16. if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.Release 12 184 Condition ADD_IMS 4.3-1 AND PDN2_IMS==true. The SS configures a new data radio bearer. default parameters. RRCConnectionReconfiguration message contains the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.3-20 Information Element Access point name Value/remark Any allowed value 3GPP Comment The UE includes a new APN.4 U-S --> <-- Message Sequence Message RRC: ULInformationTransfer NAS: PDN CONNECTIVITY REQUEST RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer NAS:ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT Specific message contents All specific message contents shall be referred to clause 4.7.5A. Table 4.5A.4.2 Definition of system information messages The default system information messages are used. associated with the additional default EPS bearer context.508 subclause 4.1 3GPP TS 36.16. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of additional default bearer. 4.1 takes place performing IP address allocation in the U-plane.1 (2014-12) Explanation true if this procedure is part of the intitial registration (step 16c1 in table 4.4-1: PDN CONNECTIVITY REQUEST (step 1) Derivation Path: Table 4.16.3 takes place if requested by the UE The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message.508 subclause 4.3-1: Establishment of additional PDN connectivity St 1 2 3 - - 4 Procedure The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN. false for all other cases Initial conditions System Simulator: - 1 cell.5A.508 V12.16.5A. EXCEPTION: In parallel to the event described in step 4 below.6 and 4. EXCEPTION: IF ADD_IMS THEN in parallel to the event described in step 4 below the generic procedure for IMS signalling in the U-plane specified in TS 36.7 with the exceptions below. Condition .16.5A. 4. 7.4.5A. Idle Mode state (State 2) with connectivity at least to two PDNs 4.3-4 Information Element EPS bearer identity Procedure transaction identity Value/Remark (same value as used in step 2) 0 Comment Condition No procedure transaction identity assigned 4.5A.1 (2014-12) Table 4. default parameters.Release 12 185 3GPP TS 36.17.1 Initial conditions System Simulator: - 1 cell.4-3: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 4) Derivation path: Table 4.5A.1-8 with condition AM-DRB-ADD(1) for ADD_IMS or with condition AM-DRB-ADD(8) else Information Element Value/Remark Comment Condition EPS bearer identity '0101'B arbitrary value ADD_IMS used for PDN connectivity being maintained during the test case EPS bearer identity '1100'B arbitrary value NOT used for additional ADD_IMS non-IMS PDN connectivity Procedure transaction identity PTI-1 SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure Table 4.5A.4-2: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 2) Derivation path: Table 4.16.16.3-6 with condition IMS_PDN_ConnEstab for ADD_IMS and NOT IMS_PDN_ConnEstab else and table 4.5A.17 Generic Test Procedure for user initiated release of additional PDN connectivity 4.2 Definition of system information messages The default system information messages are used.508 V12.17.6. 3GPP . - The procedure shall be performed under ideal radio conditions as defined in clause 5 User Equipment: - The UE shall be in Registered.7. 7 with the exceptions below. Table 4. The SS transmits a RRCConnectionReconfiguration message to establish SRB2 and DRBs associated with all default EPS bearer contexts The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of SRB2 and DRBs associated with all default EPS bearer contexts.17. The UE transmits a PDN DISCONNECT REQUEST The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message included in an RRCConnectionReconfiguration message.3 186 3GPP TS 36.4-1: RRCConnectionReconfiguration (step 7) Derivation path: 36.508 V12.17.3-1: Release of additional PDN connectivity St Procedure Message Sequence Message U-S 1 2 3 4 5 6 7 8 9 10 11 12 Cause the UE to request disconnection from the additional PDN (see Note 1) The UE transmits an RRCConnectionRequest SS transmit an RRCConnectionSetup message.17.4. The UE transmits a SecurityModeComplete message and establishes the initial security configuration.7.4-2: PDN DISCONNECT REQUEST (step 9) Derivation Path: TS 36.508 table 4.5A. The UE transmits an RRCConnectionReconfigurationComplete message to confirm the release of the bearer.1-8 using condition SRB2-DRB(2.4 Specific message contents All specific message contents shall be referred to clause 4. 0) NOTE: The bid for the AM DRBs shall be 1 and 8 instead of 1 and 2.Release 12 4.17.5A. The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.1 (2014-12) Procedure Table 4.5A.508 Table 4. in any case the EPS bearer identity of the Default EPS Bearer of the PDN to be released needs to be handed over to the UE 4.17.3-22 Information Element EPS bearer identity Value/remark ‘0000’ Procedure transaction identity PTI-1 Linked EPS bearer identity (bearer identity as handed over at step 1) 3GPP Comment "no EPS bearer identity assigned" UE assigns a particular PTI not yet used between 1 and 254 Condition . Table 4.5A. --> <---> RRCConnectionRequest RRC: RRCConnectionSetup RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST <-- RRC: SecurityModeCommand --> RRC: SecurityModeComplete <-- RRC: RRCConnectionReconfiguration --> RRC: RRCConnectionReconfigurationComplet e --> RRC: ULInformationTransfer PDN DISCONNECT REQUEST RRC: RRCConnectionReconfiguration NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST RRC: RRCConnectionReconfigurationComplet e RRC: ULInformationTransfer DEACTIVATE EPS BEARER CONTEXT ACCEPT RRC: RRCConnectionRelease <---> --> 13 The SS transmits an RRCConnectionRelease message <-to release RRC connection NOTE 1: The request to disconnect from a PDN may be performed by MMI or AT command. The SS transmits a SecurityModeCommand message to activate AS security.6.5A. The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.6 and 4. 7. regular deactivation UEINITIATED Table 4. - The procedure shall be performed under ideal radio conditions as defined in clause 5 User Equipment: - The UE shall be in Registered. 3GPP . default parameters.3-12 Information Element EPS bearer identity Procedure transaction identity Value/remark (same as in Linked EPS bearer identity of step 9) PTI-1 ESM cause 00100100 Comment Condition SS re-uses the particular PTI defined by UE for this present PDN disconnection procedure. Idle Mode state (State 2) with connectivity at least to two PDNs 4.1 (2014-12) Table 4.5A.508 Table 4.6.18.5A.4-3: RRCConnectionReconfiguration (step 10) Derivation path: 36.3-11 Information Element EPS bearer identity Procedure transaction identity Value/remark (same as in DEACTIVATE EPS BEARER CONTEXT REQUEST of step 10) 0 Comment The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.18 Generic Test Procedure for network initiated release of additional PDN connectivity 4.2 Definition of system information messages The default system information messages are used.5A.5A. No procedure transaction identity assigned Condition 4.7.Release 12 187 3GPP TS 36.1 Initial conditions System Simulator: - 1 cell.17.4-4: DEACTIVATE EPS BEARER CONTEXT REQUEST (step 10) Derivation Path: TS 36.508 table 4.18.17.508 V12.1-8 using condition DRB-REL(8) Table 4.5A.17.4-5: DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 12) Derivation Path: TS 36.508 Table 4.4.5A. 4.1-8 using condition DRB-REL(8) Table 4.1-8 using condition SRB2-DRB(2.18.5A.18.7 with the exceptions below.4-1: RRCConnectionReconfiguration (step 8) Derivation path: 36.4 <-- RRC: RRCConnectionReconfiguration --> RRC: RRCConnectionReconfigurationComplet e <-- RRC: RRCConnectionReconfiguration NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST RRC: RRCConnectionReconfigurationComplet e DEACTIVATE EPS BEARER CONTEXT ACCEPT RRC: RRCConnectionRelease --> --> <-- Specific message contents All specific message contents shall be referred to clause 4.6.3.4-3: DEACTIVATE EPS BEARER CONTEXT REQUEST (step 10) Derivation Path: TS 36.18.7.5A.5A. SS releases the PDN connectivity by transmitting a RRCConnectionReconfiguration containing a DEACTIVATE EPS BEARER CONTEXT REQUEST The UE transmits an RRCConnectionReconfigurationComplete message to confirm the release of the bearer.5. The SS transmits an RRCConnectionRelease message to release RRC connection 4. The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.18.508 Table 4.3 188 3GPP TS 36.1 (2014-12) Procedure Table 4.508 4. Table 4.18.18.Release 12 4.5A. Table 4.3-1: Release of additional PDN connectivity St Procedure Message Sequence Message U-S 1-7 8 9 10 11 12 13 Steps 1 to 7 of the generic radio bearer establishment procedure (TS 36.508 table 4.4-2: RRCConnectionReconfiguration (step 10) Derivation path: 36.5A.6 and 4. 0) NOTE: The bid for the AM DRBs shall be 1 and 8 instead of 1 and 2.508 table 4.3-1) The SS transmits a RRCConnectionReconfiguration message to establish SRB2 and DRBs associated with all default EPS bearer contexts The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of SRB2 and DRBs associated with all default EPS bearer contexts.6.5A.508 V12.3-12 Information Element EPS bearer identity ESM cause Value/remark (identity of default EPS bearer associated with the PDN to be released) 00011010 T3396 Deactivated 3GPP Comment Condition Insufficient resources Rel-10 . 6.1 (2014-12) Table 4.6. TS 36.3-11 Information Element EPS bearer identity Value/remark (same as in DEACTIVATE EPS BEARER CONTEXT REQUEST of step 10) Procedure transaction identity 0 Comment The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.1 Contents of RRC messages – CounterCheck Table 4. No procedure transaction identity assigned Condition 4.1-0a: CounterCheck Derivation Path: 36.18.331 clause 6.5A.508 V12.523-1 [18] and other clauses in this specification. TS 36.4-4: DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 12) Derivation Path: TS 36.2.4.331 clause 6.2.7.2 Information Element CounterCheck ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { counterCheck-r8 SEQUENCE { drb-CountMSB-InfoList nonCriticalExtension SEQUENCE {} Value/remark Comment Condition Comment Condition RRCTransactionIdentifier-DL Set according to specific message content Not present } } } } – CounterCheckResponse Table 4.508 Table 4.6 Default RRC message and information elements contents This clause contains the default values of common RRC messages and information elements.521-3 [34].1-0b: CounterCheckResponse Derivation Path: 36.Release 12 189 3GPP TS 36.2 Information Element CounterCheckResponse ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { counterCheckResponse-r8 SEQUENCE { drb-CountInfoList nonCriticalExtension SEQUENCE {} Value/remark RRCTransactionIdentifier-UL Set according to specific message content Not checked } } } 3GPP . All the messages and information elements are listed in alphabetical order. 4.6.521-1 [21]. which unless indicated otherwise in specific clauses of TS 36. 2.508 V12.6.1-2: CSFBParametersResponseCDMA2000 Derivation Path: 36.331 clause 6.2 Information Element CSFBParametersResponseCDMA2000 ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { csfbParametersResponseCDMA2000-r8 SEQUENCE { rand mobilityParameters nonCriticalExtension SEQUENCE {} Value/remark Comment Condition RRCTransactionIdentifier-DL Set according to specific message content Set according to specific message content Not present } } } – DLInformationTransfer Table 4.1-1: CSFBParametersRequestCDMA2000 Derivation Path: 36.2.2.2 Information Element CSFBParametersRequestCDMA2000 ::= SEQUENCE { criticalExtensions CHOICE { csfbParametersRequestCDMA2000-r8 SEQUENCE { nonCriticalExtension SEQUENCE {} } } } – Value/remark Comment Condition Not checked CSFBParametersResponseCDMA2000 Table 4.Release 12 – 190 3GPP TS 36.4.1-3: DLInformationTransfer Derivation Path: 36.331 clause 6.6.1 (2014-12) CSFBParametersRequestCDMA2000 Table 4.331 clause 6.6.2 Information Element DLInformationTransfer ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { dlInformationTransfer-r8 SEQUENCE { dedicatedInfoType CHOICE { dedicatedInfoNAS } nonCriticalExtension SEQUENCE {} Value/remark RRCTransactionIdentifier-DL Set according to specific message content Not present } } } } 3GPP Comment Condition . 1-4: HandoverFromEUTRAPreparationRequest Derivation Path: 36.6.331 clause 6. generated by the SS Set according to specific message content Not present } } } } 3GPP Comment Condition .508 V12.Release 12 – 191 3GPP TS 36.1 (2014-12) HandoverFromEUTRAPreparationRequest Table 4.4.2 Information Element HandoverFromEUTRAPreparationRequest ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { handoverFromEUTRAPreparationRequest-r8 SEQUENCE { cdma2000-Type rand mobilityParameters nonCriticalExtension SEQUENCE {} Value/remark RRCTransactionIdentifier-DL type1XRTT A random value.2. . ms2560. spare1} ENUMERATED { ms1280.0A: LoggedMeasurementConfiguration Derivation Path: 36. ms20480. min90.2.3. min120.3)) OF MCCNMC-Digit } traceId-r10 Value/remark Comment See table 4. ms5120. ms30720.4. loggingInterval-r10 ms10240 nonCriticalExtension SEQUENCE {} Not present } } } } 3GPP ENUMERATED { min10.2-2 See table 4. min20.331 clause 6.2 Information Element LoggedMeasurementConfiguration-r10 ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { loggedMeasurementConfiguration-r10 SEQUENCE { traceReference-r10 SEQUENCE { plmn-Identity-r10 SEQUENCE { mcc SEQUENCE (SIZE (3)) OF MCCNMC-Digit mnc SEQUENCE (SIZE (2.2-2 ‘0EF’H OCTET STRING (SIZE (3)) } traceRecordingSessionRef-r10 ‘1A’H tce-Id-r10 ‘5’H absoluteTimeInfo-r10 areaConfiguration-r10 loggingDuration-r10 Set to value corresponding to the absolute time when the message is sent Not present min120 OCTET STRING (SIZE (2)) OCTET STRING (SIZE (1)) BIT STRING (SIZE (48)).508 V12. spare2. see TS 36. ms10240.1 (2014-12) LoggedMeasurementConfiguration Table 4. min60.6.4. ms40960. ms61440} Condition . min40.1-4.Release 12 - 192 3GPP TS 36.4.331 clause 6.6 for format. 2.6.008 clause 10.331 clause 6.13)..1 (2014-12) MBMSCountingRequest Table 4.508 V12.6.1-4AB: MBMSCountingResponse Derivation Path: 36..2. OCTET STRING (SIZE (3)) Not present Not present } – MBMSCountingResponse Table 4.6..2 Information Element MBMSCountingResponse-r10 ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ countingResponse-r10 OF SEQUENCE { mbsfn-AreaIndex-r10 countingResponseList-r10 SEQUENCE (SIZE (1. maxServiceCount)) OF SEQUENCE { tmgi-r10 SEQUENCE { plmn-Id-r9 CHOICE{ plmn-Index-r9 } serviceId-r9 } } lateNonCriticalExtension nonCriticalExtension SEQUENCE {} Value/remark Comment Condition 1 ‘000000’O MBMS service ID (TS 24.Release 12 – 193 3GPP TS 36.5.4.1-4AA: MBMSCountingRequest Derivation Path: 36.2 Information Element MBMSCountingRequest-r10 ::= SEQUENCE { countingRequestList-r10 SEQUENCE (SIZE (1.331 clause 6. maxServiceCount)) OF SEQUENCE { countingResponseService-r10 } lateNonCriticalExtension nonCriticalExtension SEQUENCE {} } } } } Value/remark Not present 0 Not present Not present 3GPP Comment Condition . .2 Information Element criticalExtensions CHOICE { c1 CHOICE{ interestIndication-r11 OF SEQUENCE { mbms-FreqList-r11[n] SEQUENCE (SIZE (1.1-4AC: MBMSInterestIndication Derivation Path: 36.2.Release 12 – 194 3GPP TS 36.1-4A: MBSFNAreaConfiguration Derivation Path: 36.4.1 (2014-12) MBMSInterestIndication Table 4.maxEARFCN2) } mbms-Priority-r11 lateNonCriticalExtension nonCriticalExtension SEQUENCE {} Value/remark Comment The number of entries is set according to specific message content.2 Information Element MBSFNAreaConfiguration-r9 ::= SEQUENCE { commonSF-Alloc-r9 SEQUENCE (SIZE (1.maxMBSFN-Allocations)) OF SEQUENCE { radioframeAllocationPeriod radioframeAllocationOffset subframeAllocation CHOICE { oneFrame } } commonSF-AllocPeriod-r9 pmch-InfoList-r9 SEQUENCE (SIZE (0.331 clause 6..2...maxSessionPerPMCH)) OF SEQUENCE { MBMS-SessionInfo-r9 SEQUENCE { tmgi-r9 SEQUENCE { plmn-Id-r9 CHOICE{ plmn-Index-r9 } serviceId-r9 } sessionId-r9 logicalChannelIdentity-r9 Value/remark Comment Condition n4 1 0 FDD TDD ‘100000’B ‘000010’B FDD TDD rf8 1 0 rf8 1 ‘000000’O Not present 1 } } } 3GPP OCTET STRING (SIZE (3)) ..6. Not checked INTEGER (0.maxFreqMBMS-r11)) OF { INTEGER (0..maxEARFCN2 ) ENUMERATED {true} Condition Not present Not present } } } – MBSFNAreaConfiguration Table 4.6.508 V12.331 clause 6.maxPMCHPerMBSFN)) OF SEQUENCE { pmch-Config-r9 SEQUENCE { sf-AllocEnd-r9 dataMCS-r9 mch-SchedulingPeriod-r9 } mbms-SessionInfoList-r9 SEQUENCE (SIZE (0. 1-5: MeasurementReport Derivation Path: 36.6.1-7: Paging Derivation Path: 36.331 clause 6.331 clause 6.331 clause 6.6.maxPageRec)) OF SEQUENCE { ue-Identity[1] CHOICE { s-TMSI } cn-Domain[1] } systemInfoModification etws-Indication nonCriticalExtension SEQUENCE {} Value/remark 1 entry Set to the value of the STMSI of the UE ps Not present Not present Not present } 3GPP .2.2 Information Element MobilityFromEUTRACommand ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { mobilityFromEUTRACommand-r8 SEQUENCE { csFallbackIndicator purpose CHOICE { Value/remark RRCTransactionIdentifier-DL Set according to specific message content Set according to specific message content handover cellChangeOrder } nonCriticalExtension SEQUENCE {} Not present } } } } – Paging Table 4.6.1 (2014-12) MeasurementReport Table 4.2.2 Information Element Paging ::= SEQUENCE { pagingRecordList SEQUENCE (SIZE (1.1-6: MobilityFromEUTRACommand Derivation Path: 36.2.4.508 V12..Release 12 – 195 3GPP TS 36.2 Information Element MeasurementReport ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { measurementReport-r8 SEQUENCE { measResults Value/remark Comment Condition Comment Condition Comment Condition Set according to specific message content Not checked nonCriticalExtension SEQUENCE {} } } } } – MobilityFromEUTRACommand Table 4. 4.508 V12.Release 12 196 3GPP 3GPP TS 36.1 (2014-12) . 508 V12.1-8: RRCConnectionReconfiguration 3GPP .1 (2014-12) RRCConnectionReconfiguration Table 4.4.Release 12 – 197 3GPP TS 36.6. 2. m) AM-DRBADD(bid) UM-DRBADD(bid) DRBREL(bid) HO HO-TOEUTRA(n.. m) DRB(n.331 clause 6. m) SRB1SRB2DRB(n.4. HO-TOEUTRA SRB2DRB(n. m) RadioResourceConfigDe dicated-DRB(n.2 Information Element RRCConnectionReconfiguration ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE{ rrcConnectionReconfiguration-r8 SEQUENCE { measConfig mobilityControlInfo dedicatedInfoNASList radioResourceConfigDedicated securityConfigHO nonCriticalExtension SEQUENCE { lateNonCriticalExtension nonCriticalExtension SEQUENCE { otherConfig-r9 otherConfig-r9 fullConfig-r9 nonCriticalExtension SEQUENCE { sCellToReleaseList-r10 sCellToAddModList-r10 sCellToAddModList-r10 SEQUENCE (SIZE (1.m) AM-DRBADD(bid) UM-DRBADD(bid) DRBREL(bid) DRB-Mod SRB2DRB(n.508 V12. m) RadioResourceConfigDe dicated-DRB-Mod RadioResourceConfigDe dicated-SCell_AddMod RadioResourceConfigDe dicated-PCell-PATTERN Not present SecurityConfigHODEFAULT MEAS HO.1 (2014-12) Value/remark Comment Condition RRCTransactionIdentifier-DL Not present MeasConfig-DEFAULT Not present MobilityControlInfo-HO Not present Set according to specific message content Not present RadioResourceConfigDe dicated-SRB2-DRB(n.maxSCell-r10)) OF SEQUENCE { sCellToAddMod[1] 198 3GPP TS 36. m) DRB(n. HO-TOEUTRA Not present Not present OtherConfig-r9 Not present Not present Not present 1 entry SCellToAddMod-r10DEFAULT 3GPP OtherConfig SCell_AddM od . m) RadioResourceConfigDe dicated-AM-DRBADD(bid) RadioResourceConfigDe dicated-UM-DRBADD(bid) RadioResourceConfigDe dicated-DRB-REL(bid) RadioResourceConfigDe dicated-HO RadioResourceConfigDe dicated-HO-TOEUTRA(n.Release 12 Derivation Path: 36.m) DRB-Mod SCell_AddM od PCellPATTERN HO. m) DRB-Mod SCell_AddMod PCell-PATTERN OtherConfig – Explanation Establishment of a SRB and DRB combination with n x AM DRB and m x UM DRB (including establishment of SRB2) Establishment of additional n x AM DRB:s and m x UM DRB:s (SRB2 should already be established) Establishment of a single additional AM DRB with bearer identity bid (SRB2 should already be established) Establishment of a single additional UM DRB with bearer identity bid (SRB2 should already be established) Release of the DRB with bearer identity bid Intra LTE handover A measurement is configured Inter-RAT handover to E-UTRA including the establishment of a SRB1.2.1 (2014-12) Not present } } } } } } } Condition SRB2-DRB(n.m) AM-DRB-ADD(bid) UM-DRB-ADD(bid) DRB-REL(bid) HO MEAS HO-TO-EUTRA(n.m) DRB(n. SRB2 and n x AM DRB plus m x UM DRB Modification of already established DRB ID 2 and is used for sending Modify EPS Bearer Context Request message (SRB2 should already be established) Addition or modification of SCell eICIC Serving Cell Pattern Other Configuration is configured RRCConnectionReconfigurationComplete Table 4.508 V12.Release 12 199 } nonCriticalExtension 3GPP TS 36.4.331 clause 6.2 Information Element RRCConnectionReconfigurationComplete ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { rrcConnectionReconfigurationComplete-r8 SEQUENCE { nonCriticalExtension SEQUENCE {} } } } Value/remark RRCTransactionIdentifier-UL Not checked 3GPP Comment Condition .6.1-9: RRCConnectionReconfigurationComplete Derivation Path: 36. 2 Information Element RRCConnectionReestablishment ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE{ rrcConnectionReestablishment-r8 SEQUENCE { radioResourceConfigDedicated nextHopChainingCount nonCriticalExtension SEQUENCE {} Value/remark Comment Condition RRCTransactionIdentifier-DL RadioResourceConfigDe dicated-SRB1 0 Not present } } } } – RRCConnectionReestablishmentComplete Table 4.4.2.1 (2014-12) RRCConnectionReestablishment Table 4.6.331 clause 6.508 V12.2.2 Information Element RRCConnectionReestablishmentReject ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionReestablishmentReject-r8 SEQUENCE { nonCriticalExtension SEQUENCE {} } } } Value/remark Not present 3GPP Comment Condition .6.1-11: RRCConnectionReestablishmentComplete Derivation Path: 36.2 Information Element RRCConnectionReestablishmentComplete ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { rrcConnectionReestablishmentComplete-r8 SEQUENCE { nonCriticalExtension SEQUENCE {} } } } – Value/remark Comment Condition RRCTransactionIdentifier-UL Not checked RRCConnectionReestablishmentReject Table 4.1-12: RRCConnectionReestablishmentReject Derivation Path: 36.6.331 clause 6.331 clause 6.Release 12 – 200 3GPP TS 36.1-10: RRCConnectionReestablishment Derivation Path: 36.2. 2 Information Element RRCConnectionRelease ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { rrcConnectionRelease-r8 SEQUENCE { releaseCause redirectedCarrierInfo idleModeMobilityControlInfo nonCriticalExtension SEQUENCE {} } } } Value/remark RRCTransactionIdentifier-DL other Not present Not present Not present } 3GPP .331 clause 6.2 Information Element RRCConnectionReestablishmentRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionReestablishmentRequest-r8 SEQUENCE { ue-Identity reestablishmentCause spare Value/remark Comment Condition Comment Condition Comment Condition Set according to specific message content Set according to specific message content Present but contents not checked } } } – RRCConnectionReject Table 4.6.2.1 (2014-12) RRCConnectionReestablishmentRequest Table 4.508 V12.2 Information Element RRCConnectionReject ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { rrcConnectionReject-r8 SEQUENCE { waitTime nonCriticalExtension SEQUENCE {} } } } } – Value/remark 3(seconds) Not present RRCConnectionRelease Table 4.331 clause 6.2.2.4.6.1-13: RRCConnectionReestablishmentRequest Derivation Path: 36.6.331 clause 6.1-14: RRCConnectionReject Derivation Path: 36.Release 12 – 201 3GPP TS 36.1-15: RRCConnectionRelease Derivation Path: 36. 508 V12.6.1-18: RRCConnectionSetupComplete Derivation Path: 36.6.2.331 clause 6.2 Information Element RRCConnectionSetupComplete ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { rrcConnectionSetupComplete-r8 SEQUENCE { selectedPLMN-Identity registeredMME dedicatedInfoNAS nonCriticalExtension SEQUENCE {} Value/remark RRCTransactionIdentifier-UL 1 Not checked Present but contents not checked Not checked } } } } 3GPP .331 clause 6.2 Information Element RRCConnectionRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcConnectionRequest-r8 SEQUENCE { ue-Identity CHOICE { s-TMSI } establishmentCause spare Value/remark Comment Condition Comment Condition Comment Condition Any allowed value Present but contents not checked Present but contents not checked } } } – RRCConnectionSetup Table 4.6.2.1 (2014-12) RRCConnectionRequest Table 4.331 clause 6.4.Release 12 – 202 3GPP TS 36.1-17: RRCConnectionSetup Derivation Path: 36.1-16: RRCConnectionRequest Derivation Path: 36.2.2 Information Element RRCConnectionSetup ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { rrcConnectionSetup-r8 SEQUENCE { radioResourceConfigDedicated nonCriticalExtension SEQUENCE {} Value/remark RRCTransactionIdentifier-DL RadioResourceConfigDe dicated-SRB1 Not present } } } } – RRCConnectionSetupComplete Table 4. 1-19: SecurityModeCommand Derivation Path: 36.2 Information Element SecurityModeComplete ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { securityModeComplete-r8 SEQUENCE { nonCriticalExtension SEQUENCE {} } } Value/remark RRCTransactionIdentifier-UL Not checked } – SecurityModeFailure Table 4.1 (2014-12) SecurityModeCommand Table 4.331 clause 6.2 Information Element SecurityModeFailure ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { securityModeFailure-r8 SEQUENCE { nonCriticalExtension SEQUENCE {} } } Value/remark RRCTransactionIdentifier-UL Not checked } 3GPP .1-20: SecurityModeComplete Derivation Path: 36.2.2 Information Element SecurityModeCommand ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE{ securityModeCommand-r8 SEQUENCE { securityConfigSMC nonCriticalExtension SEQUENCE {} Value/remark Comment Condition Comment Condition Comment Condition RRCTransactionIdentifier-DL SecurityConfigSMCDEFAULT Not present } } } } – SecurityModeComplete Table 4.6.1-21: SecurityModeFailure Derivation Path: 36.2.Release 12 – 203 3GPP TS 36.331 clause 6.508 V12.331 clause 6.2.4.6.6. 4.2.Release 12 – 204 3GPP TS 36.508 V12.2 Information Element UECapabilityEnquiry ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE { ueCapabilityEnquiry-r8 SEQUENCE { ue-CapabilityRequest nonCriticalExtension SEQUENCE {} } } } Value/remark RRCTransactionIdentifier-DL eutra Not present } 3GPP Comment Condition .6.1-22: UECapabilityEnquiry Derivation Path: 36.1 (2014-12) UECapabilityEnquiry Table 4.331 clause 6. Release 12 – 205 UECapabilityInformation Table 4.1-23: UECapabilityInformation 3GPP 3GPP TS 36.1 (2014-12) .4.6.508 V12. FGI 8 -.FGI 23 -.331 clause 6.FGI 25 -.508 V12.FGI 5 -.FGI 11 -.FGI 10 -.FGI 13 -.FGI 22 -.1 (2014-12) Value/remark Comment Condition RRCTransactionIdentifier-UL 1 entry Set according to specific message content Same as indicated in TC applicability of 36.FGI 24 -.FGI 12 -.FGI 1 -.FGI 9 -.FGI 18 -.FGI 26 -.Release 12 Derivation Path: 36.4.FGI 14 -.maxRAT-Capabilities)) OF SEQUENCE { rat-Type ueCapabilityRAT-Container ue-EUTRA-Capability SEQUENCE { accessStratumRelease ue-Category pdcp-Parameters SEQUENCE { supportedROHC-Profiles SEQUENCE { profile0x0001 profile0x0001 profile0x0002 profile0x0002 profile0x0003 profile0x0004 profile0x0006 profile0x0101 profile0x0102 profile0x0103 profile0x0104 } maxNumberROHC-ContextSessions } phyLayerParameters rf-Parameters measParameters featureGroupIndicators -.FGI 6 -.FGI 28 206 3GPP TS 36.2 Information Element UECapabilityInformation ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE{ ueCapabilityInformation-r8 SEQUENCE { ue-CapabilityRAT-ContainerList SEQUENCE (SIZE (1.FGI 4 -.FGI 15 -.523-2 Not checked Not checked true Not checked true Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked 3GPP ROHC ROHC .FGI 7 -.FGI 27 -.FGI 16 -.FGI 20 -.FGI 19 -.2.FGI 3 -.FGI 17 -..FGI 21 -.FGI 2 -. FGI 11F -.FGI 41 -.FGI 7F -.FGI 5F -.508 V12.FGI 21F -.FGI 4F -.FGI 19F -.FGI 3F -.FGI 1F -.FGI 10F -.FGI 8F -.4.FGI 6F -.FGI 31 -.FGI 36 -.1 (2014-12) Not checked Not checked Not checked ‘0’B (Undefined) Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked ‘0’B (Undefined) Not checked BITSTRING 32 Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked 3GPP FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD .FGI 34 -.Release 12 -.FGI 25F 207 3GPP TS 36.FGI 14F -.FGI 32 interRAT-Parameters SEQUENCE { utraFDD utraTDD128 utraTDD384 utraTDD768 geran cdma2000-HRPD cdma2000-1xRTT cdma2000-1xRTT } nonCriticalExtension SEQUENCE { phyLayerParameters-v920 interRAT-ParametersGERAN-v920 interRAT-ParametersUTRA-v920 interRAT-ParametersCDMA2000-v920 deviceType-r9 csg-ProximityIndicationParameters-r9 neighCellSI-AcquisitionParameters-r9 son-Parameters-r9 nonCriticalExtension SEQUENCE { lateNonCriticalExtension SEQUENCE { featureGroupIndRel9Add-r9 -.FGI 2F -.FGI 16F -.FGI 15F -.FGI 20F -.FGI 33 -.FGI 22F -.FGI 13F -.FGI 42-64 fdd-Add-UE-EUTRA-Capabilities-r9 SEQUENCE { phyLayerParameters-r9 featureGroupIndicators-r9 -.FGI 12F -.FGI 9F -.FGI 29 -.FGI 37 -.FGI 35 -.FGI 38 -.FGI 40 -.FGI 30 -.FGI 23F -.FGI 39 -.FGI 18F -.FGI 24F -.FGI 17F -. FGI 27T -.FGI 41F -.FGI 3T -.FGI 22T -.FGI 4T -.FGI 1T -.FGI 29F -.FGI 37F -.FGI 5T -.FGI 36F -.FGI 29T -.FGI 11T -.FGI 18T -.FGI 10T -.FGI 33F -.508 V12.FGI 24T -.FGI 32T featureGroupIndRel9Add-r9 -.FGI 8T -.FGI 21T -.FGI 32F featureGroupIndRel9Add-r9 -.Release 12 208 -.FGI 26F -.FGI 26T -.FGI 17T -.FGI 19T -.FGI 20T -.FGI 13T -.FGI 28T -.FGI 23T -.FGI 27F -.FGI 35F -.FGI 14T -.FGI 31T -.FGI 16T -.FGI 12T -.FGI 34F -.FGI 9T -.FGI 42F-64F interRAT-ParametersGERAN-r9 interRAT-ParametersUTRA-r9 interRAT-ParametersGERAN-r9 interRAT-ParametersCDMA2000-r9 neighCellSI-AcquisitionParameters-r9 } tdd-Add-UE-EUTRA-Capabilities-r9 SEQUENCE { phyLayerParameters-r9 featureGroupIndicators-r9 -.FGI 15T -.FGI 31F -.4.FGI 39F -.FGI 30T -.FGI 28F -.1 (2014-12) Not checked Not checked Not checked Not checked Not checked Not checked ‘0’B (Undefined) if present FDD = TDD FDD = TDD BITSTRING 32 Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked ‘0’B (Undefined) if present Not checked Not checked Not checked Not checked Not checked Not checked BITSTRING 32 Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked ‘0’B (Undefined) if present FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD FDD = TDD BITSTRING 32 Not checked 3GPP .FGI 33T 3GPP TS 36.FGI 25T -.FGI 6T -.FGI 40F -.FGI 30F -.FGI 38F -.FGI 2T -.FGI 7T -. FGI 34T -.FGI 108 -.FGI 37T -.FGI 42T-64T interRAT-ParametersGERAN-r9 interRAT-ParametersUTRA-r9 interRAT-ParametersGERAN-r9 interRAT-ParametersCDMA2000-r9 neighCellSI-AcquisitionParameters-r9 } nonCriticalExtension SEQUENCE { interRAT-ParametersUTRA-v9c0 nonCriticalExtension SEQUENCE { phyLayerParameters-v9d0 nonCriticalExtension SEQUENCE { rf-Parameters-v9e0 nonCriticalExtension SEQUENCE {} } } } 3GPP TS 36.FGI 111 -.FGI 35T -.FGI 113 -.FGI 105 -.FGI 38T -.FGI 40T -.FGI 116 -.FGI 117-132 interRAT-ParametersCDMA2000-v1020 ue-BasedNetwPerfMeasParameters-r10 interRAT-ParametersUTRA-TDD-v1020 nonCriticalExtension SEQUENCE { fdd-Add-UE-EUTRA-Capabilities-v1060 tdd-Add-UE-EUTRA-Capabilities-v1060 rf-Parameters-v1060 nonCriticalExtension SEQUENCE { rf-Parameters-v1090 nonCriticalExtension SEQUENCE { BITSTRING 32 Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked ‘0’B (Undefined) if present Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked 3GPP .FGI 112 -.FGI 115 -.FGI 39T -.FGI 102 -.FGI 103 -.4.FGI 106 -.FGI 114 -.FGI 110 -.FGI 36T -.1 (2014-12) Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked ‘0’B (Undefined) if present Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked } nonCriticalExtension SEQUENCE { ue-Category-v1020 Not checked phyLayerParameters-v1020 Not checked rf-Parameters-v1020 Not checked measParameters-v1020 Not checked featureGroupIndRel10-r10 -.FGI 101 -.508 V12.FGI 109 -.FGI 41T -.FGI 107 -.FGI 104 -.Release 12 209 -. 4.4-1/41).Release 12 210 pdcp-Parameters-v1130 phyLayerParameters-v1130 rf-Parameters-v1130 measParameters-v1130 interRAT-ParametersCDMA2000- Not checked Not checked Not checked Not checked Not checked otherParameters-r11 fdd-Add-UE-EUTRA-Capabilities- Not checked Not checked tdd-Add-UE-EUTRA-Capabilities- Not checked nonCriticalExtension SEQUENCE {} Not checked 3GPP TS 36.1 (2014-12) v1130 v1130 v1130 } } } } } } } } nonCriticalExtension SEQUENCE {} Not checked } } } } Condition ROHC FDD = TDD Explanation Support of ROHC profile0x0001 and ROHC profile0x0002 (TS 36.523-2 table A.41/40 and A. is not checked per default 3GPP .508 V12.4.4. UE is not allowed to signal different values for FDD and TDD. 2.1-23A: UEInformationRequest Derivation Path: 36.Release 12 – 211 3GPP TS 36.508 V12.4.331 clause 6. ConEstFail Logged MDT Not present Not present true Not present Not present } } } } } } } Condition Logged MDT ConEstFail RLF report Condition Explanation Used for Logged MDT test cases Used for RRC connection establishment failure report related test cases Used for Radio Link Failure Logging test cases 3GPP ConEstFail .2 Information Element UEInformationRequest-r9 ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE{ ueInformationRequest-r9 SEQUENCE { rach-ReportReq-r9 rlf-ReportReq-r9 nonCriticalExtension SEQUENCE { lateNonCriticalExtension nonCriticalExtension SEQUENCE {} nonCriticalExtension SEQUENCE { logMeasReportReq-r10 nonCriticalExtension SEQUENCE {} nonCriticalExtension SEQUENCE { connEstFailReportReq-r11 nonCriticalExtension SEQUENCE {} Value/remark Comment RRCTransactionIdentifier-DL FALSE FALSE TRUE RLF report Not present Not present true Logged MDT.6.1 (2014-12) UEInformationRequest Table 4. Release 12 – 212 3GPP TS 36.6.2.6.508 V12.4.2 Information Element UEInformationResponse-r9 ::= SEQUENCE { rrc-TransactionIdentifier criticalExtensions CHOICE { c1 CHOICE{ ueInformationResponse-r9 SEQUENCE { rach-Report-r9 SEQUENCE {} rlf-Report-r9 SEQUENCE {} nonCriticalExtension SEQUENCE { lateNonCriticalExtension nonCriticalExtension SEQUENCE { logMeasReport-r10 SEQUENCE {} nonCriticalExtension SEQUENCE { } } } } } Value/remark Comment Condition Comment Condition RRCTransactionIdentifier-UL Not checked Not checked Not checked Not checked Not checked } - ULHandoverPreparationTransfer Table 4.1-23B: UEInformationResponse Derivation Path: 36.331 clause 6.1-24: ULHandoverPreparationTransfer Derivation Path: 36.2.2 Information Element ULHandoverPreparationTransfer ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulHandoverPreparationTransfer-r8 SEQUENCE { cdma2000-Type meid dedicatedInfo nonCriticalExtension SEQUENCE {} Value/remark type1XRTT Set to the 56 bit CDMA2000 mobile identification number of the UE Set according to specific message content Not checked } } } } 3GPP .331 clause 6.1 (2014-12) UEInformationResponse Table 4. 1 (2014-12) ULInformationTransfer Table 4.2.2 Information Element ULInformationTransfer ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransfer-r8 SEQUENCE { dedicatedInfoType CHOICE { dedicatedInfoNAS } nonCriticalExtension SEQUENCE {} Value/remark Comment Condition Comment Condition Present but contents not checked Not checked } } } } – UEAssistanceInformation Table 4.6.4.1-25: ULInformationTransfer Derivation Path: 36.331 clause 6.1-26: UEAssistanceInformation Derivation Path: 36.4.2 System information blocks See subclause 4.6.2.2 Information Element UEAssistanceInformation-r11 ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ UEAssistanceInformation-r11-IEs SEQUENCE { powerPreferenceIndication-r11 powerPreferenceIndication-r11 laterNonCriticalExtension nonCriticalExtension SEQUENCE {} } } } } Condition Low_Power Normal Value/remark lowPowerConsumption normal Not Present Not Present Low_Power Normal Explanation The UE indicates that it prefers a configuration primarily optimised for power saving The UE indicates that it does not prefer a configuration primarily optimised for power saving 4. 3GPP .3.Release 12 – 213 3GPP TS 36.3 in this document.331. Clause 6.508 V12.6. 3.2 Information Element BCCH-Config-DEFAULT::= SEQUENCE { modificationPeriodCoeff Value/remark n4 Comment Condition To provide reliable delivery of SI change notifications.6. } – CQI-ReportAperiodic-r10-DEFAULT Table 4.3-1A: CQI-ReportAperiodic-r10-DEFAULT Derivation Path: 36.6.6.508 V12.1 (2014-12) 4.331 clause 6.3-1: BCCH-Config-DEFAULT Derivation Path: 36.331 clause 6.3-0B: Void – BCCH-Config-DEFAULT Table 4.6.3-0A: Void Table 4.Release 12 214 3GPP TS 36.4.3 Radio resource control information elements Table 4.2 Information Element CQI-ReportAperiodic-r10 ::=CHOICE { setup SEQUENCE { cqi-ReportModeAperiodic-r10 aperiodicCSI-Trigger-r10 } } Value/remark rm30 Not present 3GPP Comment Condition .3.6. 6.508 V12.331 clause 6.21C in TS 36.213) (see Table 7.2.21B in TS 36.2 Information Element CQI-ReportConfig-r10 ::= SEQUENCE { cqi-ReportAperiodic-r10 nomPDSCH-RS-EPRE-Offset cqi-ReportPeriodic-r10 pmi-RI-Report-r9 csi-SubframePatternConfig-r10 Value/remark CQI-ReportAperiodic-r10DEFAULT 0 Not present CQI-ReportPeriodic-r10DEFAULT Not present Not present } Condition Explanation 3GPP Comment Condition CQI_PERI ODIC .3-2AA: CQI-ReportConfig-r10-DEFAULT Derivation Path: 36.4.2.2.2.331 clause 6.213) 24 cqi-FormatIndicatorPeriodic CHOICE { widebandCQI } ri-ConfigIndex TDD NULL 483 FDD (see Table 7.1 (2014-12) CQI-ReportConfig-DEFAULT Table 4.3-2: CQI-ReportConfig-DEFAULT Derivation Path: 36.213) (see Table 7. 484 simultaneousAckNackAndCQI Condition TDD FALSE } } } Condition CQI_PERIODIC FDD TDD – Explanation When periodic CQI reporting should be enabled FDD cell environment TDD cell environment CQI-ReportConfig-r10-DEFAULT Table 4.21B in TS 36.21A in TS 36.213) This value for TDD is selected together with cqipmi-ConfigIndex based on TDD configuration 1.Release 12 – 215 3GPP TS 36.3.2 Information Element CQI-ReportConfig-DEFAULT ::= SEQUENCE { cqi-ReportModeAperiodic nomPDSCH-RS-EPRE-Offset cqi-ReportPeriodic cqi-ReportPeriodic CHOICE { setup SEQUENCE { cqi-PUCCH-ResourceIndex cqi-pmi-ConfigIndex Value/remark Comment rm30 0 Not present CQI_PERIO DIC 0 25 FDD (see Table 7.3.6. 508 V12.4.1 (2014-12) .Release 12 CQI_PERIODIC 216 When periodic CQI reporting should be enabled 3GPP 3GPP TS 36. 6.508 V12.3-2ABA: CQI-ReportConfig-v1130-DEFAULT 3GPP .Release 12 – 217 3GPP TS 36.4.1 (2014-12) CQI-ReportConfig-v1130-DEFAULT Table 4. 2 Information Element CQI-ReportConfig-v1130 ::= SEQUENCE { cqi-ReportPeriodic-v1130 SEQUENCE { simultaneousAckNackAndCQI-Format3-r11 cqi-ReportPeriodicProcExtToReleaseList-r11 cqi-ReportPeriodicProcExtToAddModList-r11 SEQUENCE (SIZE (1.maxCQI-ProcExt-r11)) OF SEQUENCE { cqi-ReportPeriodicProcExtId-r11[1] SEQUENCE { cqi-ReportPeriodicProcExtId-r11 cqi-pmi-ConfigIndex-r11 cqi-FormatIndicatorPeriodic-r11 CHOICE { widebandCQI-r11 SEQUENCE { csi-ReportMode-r11 } subbandCQI-r11 SEQUENCE { k periodicityFactor-r11 } } ri-ConfigIndex-r11 csi-ConfigIndex-r11 CHOICE { release setup SEQUENCE { cqi-pmi-ConfigIndex2-r11 ri-ConfigIndex2-r11 } } 218 3GPP TS 36.Release 12 Derivation Path: 36.maxCSI-IM-r11)) OF SEQUENCE { csi-IM-ConfigId-r11[1] resourceConfig-r11[1] subframeConfig-r11[1] } csi-ProcessToReleaseList-r11 csi-ProcessToAddModList-r11SEQUENCE (SIZE (1.331 clause 6...maxCSI-Proc-r11)) OF SEQUENCE { csi-ProcessId-r11[1] csi-RS-ConfigNZPId-r11[1] csi-IM-ConfigId-r11[1] p-C-AndCBSRList-r11[1] SEQUENCE (SIZE (1.3...2)) OF SEQUENCE { p-C-r11[1] codebookSubsetRestriction-r11[1] } cqi-ReportBothProc-r11[1] SEQUENCE { ri-Ref-CSI-ProcessId-r11 pmi-RI-Report-r11 } cqi-ReportPeriodicProcId-r11[1] cqi-ReportAperiodicProc-r11[1] SEQUENCE { cqi-ReportModeAperiodic-r11 trigger01-r11 trigger10-r11 Not present 1 entry 1 2 2 1 3 Not present 1 entry 1 1 1 1 entry -6 1111111 1 Not present 1 Not present Not present Not present 3GPP FDD TDD FDD TDD .1 (2014-12) Value/remark Comment Condition Not present Not present 1 entry 1 Not present Not present Not present Not present Not present NULL Not present Not present } } } cqi-ReportBoth-r11 SEQUENCE { csi-IM-ConfigToReleaseList-r11 csi-IM-ConfigToAddModList-r11 SEQUENCE (SIZE (1.4.508 V12. 6.2 Information Element CQI-ReportPeriodic-r10 ::= CHOICE { setup SEQUENCE { cqi-PUCCH-ResourceIndex-r10 cqi-PUCCH-ResourceIndexP1-r10 cqi-pmi-ConfigIndex cqi-FormatIndicatorPeriodic-r10 CHOICE { widebandCQI-r10 SEQUENCE { csi-ReportMode-r10 } } ri-ConfigIndex Value/remark 0 Not present 25 24 Condition FDD TDD Not present Not present 483 484 simultaneousAckNackAndCQI cqi-Mask-r9 csi-ConfigIndex-r10 Comment FALSE Not present Not present } } 3GPP SCell_Conf ig FDD and NOT SCell_Conf ig TDD and NOT SCell_Conf ig .3-2AC: CQI-ReportPeriodic-r10-DEFAULT Derivation Path: 36.6.3-2AB: CQI-ReportConfigSCell-r10-DEFAULT Derivation Path: 36.508 V12.3.3.331 clause 6.1 (2014-12) Not present } } } } Condition FDD TDD – Explanation FDD cell environment TDD cell environment CQI-ReportConfigSCell-r10-DEFAULT Table 4.4.Release 12 219 trigger11-r11 3GPP TS 36.331 clause 6.2 Information Element CQI-ReportConfigSCell-r10 ::= SEQUENCE { cqi-ReportModeAperiodic-r10 nomPDSCH-RS-EPRE-Offset-r10 cqi-ReportPeriodicSCell-r10 pmi-RI-Report-r10 Value/remark Comment rm30 0 Not present CQI-ReportPeriodic-r10DEFAULT Not present Condition CQI_PERI ODIC } Condition CQI_PERIODIC – Explanation When periodic CQI reporting should be enabled CQI-ReportPeriodic-r10-DEFAULT Table 4. Table 4.4.331 clause 6.6.6.3.1 (2014-12) Explanation FDD cell environment TDD cell environment CQI-ReportPeriodic configuration for SCell.Release 12 220 Condition FDD TDD SCell_Config 3GPP TS 36.3-2AE: Void – CSI-RS-ConfigNZP-r11-DEFAULT Table 4.508 V12.6.3-2AD: Void Table 4.3.6.3-2AF: CSI-RS-ConfigNZP-r11-DEFAULT Derivation Path: 36.2 Information Element CSI-RS-ConfigNZP-r11 ::= SEQUENCE { csi-RS-ConfigNZPId-r11 antennaPortsCount-r11 resourceConfig-r11 subframeConfig-r11 scramblingIdentity-r11 qcl-CRS-Info-r11 SEQUENCE { qcl-ScramblingIdentity-r11 crs-PortsCount-r11 mbsfn-SubframeConfigList-r11 CHOICE { release setup SEQUENCE { subframeConfigList } } } Value/remark Comment 1 an2 0 0 1 3 0 Condition FDD TDD FDD TDD 0 n2 NULL Not present } Condition FDD TDD – Explanation FDD cell environment TDD cell environment CSI-RS-ConfigZP-r11-DEFAULT Table 4.2 Information Element CSI-RS-ConfigZP-r11 ::= SEQUENCE { csi-RS-ConfigZPId-r11 resourceConfigList-r11 subframeConfig-r11 Value/remark 1 0010000000000000 1 3 } Condition FDD TDD Explanation FDD cell environment TDD cell environment 3GPP Comment Condition FDD TDD .3-2AG: CSI-RS-ConfigZP-r11-DEFAULT Derivation Path: 36.331 clause 6. .331 clause 6.508 V12.6.Release 12 – 221 3GPP TS 36.maxDRB)) OF SEQUENCE { eps-BearerIdentity[1] drb-Identity[1] pdcp-Config[1] rlc-Config[1] logicalChannelIdentity[1] logicalChannelConfig[1] eps-BearerIdentity[2] drb-Identity[2] pdcp-Config[2] rlc-Config[2] logicalChannelIdentity[2] logicalChannelConfig[2] Value/remark 2 Entries Not present 1 Not present RLC-Config-DRB-AMRECONFIG Not present Not present Not present 2 Not present RLC-Config-DRB-AMRECONFIG Not present Not present } 3GPP .3-2A: DRB-ToAddModList-RECONFIG Derivation Path: 36.3.4.6.331 clause 6.3.2 Information Element DMRS-Config-r11 ::= CHOICE { release setup SEQUENCE { scramblingIdentity-r11 scramblingIdentity2-r11 } } – Value/remark Comment Condition Comment Condition NULL 0 1 DRB-ToAddModList-RECONFIG Table 4.2 Information Element DRB-ToAddModList ::= SEQUENCE (SIZE (1.1 (2014-12) DMRS-Config-r11-DEFAULT Table 4.3-2AH: DMRS-Config-r11-DEFAULT Derivation Path: 36. 2 Information Element EPDCCH-Config-r11 ::= SEQUENCE{ config-r11{ setup SEQUENCE { subframePatternConfig-r11{ setup SEQUENCE { subframePattern-r11 CHOICE { subframePatternFDD-r10 subframePatternTDD-r10{ subframeConfig1-5-r10 Value/remark 00000000000000000000 00000000000000000000 1111111110 1111111101 1111111011 1111110111 Comment Condition FDD FDD.6.3-2B: EPDCCH-Config-r11-DEFAULT Derivation Path: 36.508 V12.3.1 (2014-12) EPDCCH-Config-r11-DEFAULT Table 4.4.Release 12 – 222 3GPP TS 36. TM9 TDD 0000000000 0000000000 1100111001 1100111001 TM9 } } } } startSymbol-r11 setConfigToReleaseList-r11 setConfigToAddModList-r11 SEQUENCE { setConfigId-r11[1] transmissionType-r11[1] resourceBlockAssignment-r11[1] SEQUENCE{ numberPRB-Pairs-r11 resourceBlockAssignment-r11 } dmrs-ScramblingSequenceInt-r11[1] pucch-ResourceStartOffset-r11[1] re-MappingQCL-ConfigListId-r11[1] setConfigId-r11[2] transmissionType-r11[2] resourceBlockAssignment-r11[2] SEQUENCE{ numberPRB-Pairs-r11 resourceBlockAssignment-r11 } dmrs-ScramblingSequenceInt-r11[2] pucch-ResourceStartOffset-r11[2] re-MappingQCL-ConfigListId-r11[2] Not present 2 Not present 2 entry 0 distributed localized n4 n2 n8 101001000101101110 10010011000 111001001011101100110 01101100 0 0 Not present 0 1 distributed localized TM9 TM10 TM9 TM10 TM9 TM10 TM10 TM9.331 clause 6. TM10 n8 111001001011101100110 01101100 0 0 Not present 0 } } } } Condition Explanation 3GPP TM10 . 6.2 Information Element PCCH-Config-DEFAULT::= SEQUENCE { defaultPagingCycle nB Value/remark rf128 Comment Condition Typical value in real network.3.331 clause 6.3. } – PDSCH-ConfigCommon-DEFAULT Table 4.2 Information Element PDSCH-ConfigCommon-DEFAULT ::= SEQUENCE { referenceSignalPower p-b Value/remark Condition 18 (dBm) 0 ( B / A 1 ( B /  A = 1) 1TX = 1) 2TX.331 clause 6. 4TX } Condition 1TX 2TX 4TX Comment Explanation 1 SS Tx antenna environment 2 SS Tx antenna environment 4 SS Tx antenna environment 3GPP .6.508 V12.4.3-4: PHICH-Config-DEFAULT Derivation Path: 36.2 Information Element PHICH-Config-DEFAULT ::= SEQUENCE { phich-Duration phich-Resource Value/remark normal one Comment Condition Ng=1 has been selected to ensure enough PHICH resources from the real network point of view.3.331 clause 6.6.3-3: PCCH-Config-DEFAULT Derivation Path: 36.1 (2014-12) FDD cell environment TDD cell environment Transmission mode 9 Transmission mode 10 PCCH-Config-DEFAULT Table 4.Release 12 223 FDD TDD TM9 TM10 – 3GPP TS 36. oneT } – PHICH-Config-DEFAULT Table 4.3-5: PDSCH-ConfigCommon-DEFAULT Derivation Path: 36. dB0 for others Comment dB-3 for signalling test cases to reduce interference from PDSCH of intrafrequency neighbour cells dB-3 Condition 1TX 2TX.2 Information Element PDSCH-ConfigDedicated-v1130 ::= SEQUENCE { dmrs-ConfigPDSCH-r11 qcl-Operation re-MappingQCLConfigToReleaseList-r11 re-MappingQCLConfigToAddModList-r11 SEQUENCE (SIZE (1..maxRE-MapQCL-r11)) OF SEQUENCE { pdsch-RE-MappingQCL-ConfigId-r11[1] optionalSetOfFields-r11[1] SEQUENCE { crs-PortsCount-r11 crs-FreqShift-r11 mbsfn-SubframeConfigList-r11{ setup SEQUENCE { subframeConfigList } } pdsch-Start-r11 } csi-RS-ConfigZPId-r11[1] qcl-CSI-RS-ConfigNZPId-r11[1] Value/remark Condition DMRS-Config-r11DEFAULT typeB Not present 1 entry 1 0 TM10 Not present Not present Not present Not present 2 1 1 } } Condition TM10 Comment Explanation Transmission mode 10 3GPP [TM10 .331 clause 6.331 clause 6.3-6AA: PDSCH-ConfigDedicated-v1130-DEFAULT Derivation Path: 36.1 (2014-12) PDSCH-ConfigDedicated-DEFAULT Table 4.6.2 Information Element PDSCH-ConfigDedicated-DEFAULT ::= SEQUENCE { p-a Value/remark dB-3 for signalling test cases.4.3-6: PDSCH-ConfigDedicated-DEFAULT Derivation Path: 36.3. 4TX } – PDSCH-ConfigDedicated-v1130-DEFAULT Table 4.6.Release 12 – 224 3GPP TS 36.3.508 V12. 4.6.3.Release 12 – 225 3GPP TS 36.1 (2014-12) PhysicalConfigDedicatedSCell-r10-DEFAULT Table 4.3-6A: PhysicalConfigDedicatedSCell-r10-DEFAULT Derivation Path: 36.2 Information Element PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE { nonUL-Configuration-r10 SEQUENCE { antennaInfo-r10 SEQUENCE { transmissionMode-r10 codebookSubsetRestriction-r10 ue-TransmitAntennaSelection Value/remark tm1 tm2 Not present release Comment Condition 1TX 2TX } crossCarrierSchedulingConfig-r10 csi-RS-Config-r10 pdsch-ConfigDedicated-r10 } ul-Configuration-r10 ul-Configuration-r10 SEQUENCE { antennaInfoUL-r10 pusch-ConfigDedicatedSCell-r10 uplinkPowerControlDedicatedSCell-r10 cqi-ReportConfigSCell-r10 soundingRS-UL-ConfigDedicated-r10 soundingRS-UL-ConfigDedicated-v1020 soundingRS-UL-ConfigDedicatedAperiodic-r10 Not present Not present PDSCHConfigDedicatedDEFAULT Not present UL CA Not present Not present UplinkPowerControlDedic atedSCell-r10-DEFAULT CQI-ReportConfigSCellr10-DEFAULT Not present Not present Not present } } Condition UL CA 1TX 2TX Explanation When UL Carrier Aggregation is used.331 clause 6.508 V12. 1 SS Tx antenna environment 2 SS Tx antenna environment 3GPP . 7.7.6.3.2.3-7: PRACH-Config-DEFAULT Derivation Path: 36.8 Comment Condition See table 5.2-5 in TS 36.6.2.2-1A and clause 6.2 Table 6.2.1-3 and 5.3.3-7 PRACH-Config-DEFAULT 3GPP .Release 12 – 226 3GPP TS 36. Channelbandwidthdependent parameter FDD TDD TDD FDD TDD } } Note: Although PRACH format 0-3 is applicable for both FDD and TDD. Table 4.2 Information Element PRACH-Config-DEFAULT ::= SEQUENCE { rootSequenceIndex Value/remark See clause 4.4.211 for PRACH format 4 FDD Typical value in real network for FDD (see table 5. Condition FDD TDD – Explanation FDD cell environment TDD cell environment PRACH-ConfigSIB-DEFAULT Table 4.331 clause 6.211) Typical value in real network for TDD (see table 5. Assuming cell radius is up to approximately 1 km.6.508 clause 4.6.7.4.2-2 See clause 4.1 (2014-12) PRACH-Config-DEFAULT Table 4.2-1A and clause 6.6.14 in TS 36.2.2. Table 4.3.2-4 in TS 36.2-2 prach-ConfigInfo SEQUENCE { prach-ConfigIndex 3 51 highSpeedFlag FALSE (Unrestricted set) zeroCorrelationZoneConfig 5 (Ncs configuration = 5) 4 (Ncs configuration = 4) prach-FreqOffset See subclause 4.508 V12.4.7.7. Assuming cell radius is up to approximately 3 km.2.2 Table 6.7.4.3-7a: PRACH-ConfigSIB-DEFAULT Derivation Path: 36.1-1 and 5.4.12 in TS 36. the PRACH format 4 is used as default for testing for TDD.3.3 Table 4.211) High speed train configuration doesn’t apply by default.3.211for PRACH format 03 See table 5. 3-9: PUCCH-ConfigDedicated-DEFAULT Derivation Path: 36.508 V12.2 Information Element PUCCH-ConfigDedicated-DEFAULT ::= SEQUENCE { ackNackRepetition CHOICE { release } tddAckNackFeedbackMode Value/remark Condition NULL Not present multiplexing } Condition FDD TDD Comment Explanation FDD cell environment TDD cell environment 3GPP Multiplexing is selected as default to align with RAN4’s assumptions in RF tests.Release 12 – 227 3GPP TS 36.8 nCS-AN n1PUCCH-AN 6 0 Comment Condition Assuming typical values of the maximum delay spread Channelbandwidthdependent parameter } – PUCCH-ConfigDedicated-DEFAULT Table 4.331 clause 6.6.6. FDD TDD .1 (2014-12) PUCCH-ConfigCommon-DEFAULT Table 4.331 clause 6.3-8: PUCCH-ConfigCommon-DEFAULT Derivation Path: 36.4.3.6.3.2 Information Element PUCCH-ConfigCommon-DEFAULT ::= SEQUENCE { deltaPUCCH-Shift Value/remark ds2 nRB-CQI See subclause 4. Release 12 – 228 3GPP TS 36.3-9A: PUCCH-ConfigDedicated-v1020-DEFAULT Derivation Path: 36.508 V12.1 (2014-12) PUCCH-ConfigDedicated-v1020-DEFAULT Table 4.3.4. TDD 4 101 102 103 104 4 105 106 107 108 } } } } } twoAntennaPortActivatedPUCCH-Format1a1b-r10 simultaneousPUCCH-PUSCH-r10 n1PUCCH-AN-RepP1-r10 Comment Not present Not present Not present } 3GPP .6.331 clause 6.2 Information Element PUCCH-ConfigDedicated-v1020 ::= SEQUENCE { pucch-Format-r10 CHOICE { channelSelection-r10 SEQUENCE { n1PUCCH-AN-CS-r10 CHOICE { setup SEQUENCE { n1PUCCH-AN-CS-List-r10 SEQUENCE{ N1PUCCH-AN-CS-r10 } n1PUCCH-AN-CS-List-r10 SEQUENCE{ N1PUCCH-AN-CS-r10 N1PUCCH-AN-CS-r10 Value/remark Condition 1 4 101 102 103 104 FDD 2 2TX AND FDD. 8 enable64QAM } ul-ReferenceSignalsPUSCH SEQUENCE { groupHoppingEnabled Comment Typical configuration in real network Typical configuration in real network Channelbandwidthdependent parameter FALSE TRUE groupAssignmentPUSCH 0 sequenceHoppingEnabled FALSE cyclicShift 0 } } 3GPP In accordance with “the RAN5 LTE UE Feature list”.331 clause 6. Typical value in real network In accordance with “the RAN5 LTE UE Feature list”.6.3.2 Information Element PUSCH-ConfigCommon-DEFAULT ::= SEQUENCE { pusch-ConfigBasic SEQUENCE { n-SB Value/remark 1 hoppingMode interSubFrame pusch-HoppingOffset See subclause 4.331 clause 6.6.6.1 (2014-12) PUCCH-ConfigDedicated-v1130-DEFAULT Table 4.508 V12.Release 12 – 229 3GPP TS 36.3-9AA: PUCCH-ConfigDedicated-v1130-DEFAULT Derivation Path: 36.4.3-10: PUSCH-ConfigCommon-DEFAULT Derivation Path: 36. Condition .3.2 Information Element PUCCH-ConfigDedicated-v1130-DEFAULT ::= SEQUENCE { n1PUCCH-AN-CS-v1130 CHOICE { release setup SEQUENCE { n1PUCCH-AN-CS-ListP1-r11[1] n1PUCCH-AN-CS-ListP1-r11[2] } } nPUCCH-Param-r11 CHOICE { release setup SEQUENCE { nPUCCH-Identity-r11 n1PUCCH-AN-r11 } } } – Value/remark Comment Condition NULL 2 entries FFS FFS NULL FFS FFS PUSCH-ConfigCommon-DEFAULT Table 4. 1 (2014-12) PUSCH-ConfigDedicated-DEFAULT Table 4.3-11A: Void – PUSCH-ConfigDedicated-v1130-DEFAULT Table 4.6.6.3.331 clause 6.2 Information Element PUSCH-ConfigDedicated-DEFAULT ::= SEQUENCE { betaOffset-ACK-Index betaOffset-RI-Index betaOffset-CQI-Index } Value/remark Comment Condition 9 6 6 Table 4.Release 12 – 230 3GPP TS 36.3-11AA: PUSCH-ConfigDedicated-v1130-DEFAULT Derivation Path: 36.4.3.6.331 clause 6.3-11: PUSCH-ConfigDedicated-DEFAULT Derivation Path: 36.2 Information Element PUSCH-ConfigDedicated-v1130-DEFAULT ::= SEQUENCE { pusch-DMRS-r11 CHOICE { release setup SEQUENCE { nPUSCH-Identity-r11 nDMRS-CSH-Identity-r11 } } } Value/remark NULL FFS FFS 3GPP Comment Condition .508 V12. 3-12: RACH-ConfigCommon-DEFAULT Derivation Path: 36. the probability of 2 transmissions is less than 1%. an UE with pathloss of CDF = 90% reaches the maximum transmit power in 4 successive retransmissions. Condition . Under the condition of Target SIR = 2 dB.331 clause 6. Not present dB2 dBm-104 (default) n6 ra-ResponseWindowSize sf10 mac-ContentionResolutionTimer sf48 } maxHARQ-Msg3Tx Comment 4 } 3GPP Thermal noise = -113 dBm NF = 5 dB IoT = 6 dB Required SNR = -8 dB (See table 8. 6 has been selected considering the margin of 2.1 (2014-12) RACH-ConfigCommon-DEFAULT Table 4.6.2-1 in TS 36.3. 4 has been selected considering the margin of 2.104 [30]) -> -110 dB (default value is acceptable) Under the condition of Case 1 in RAN1 simulation assumptions.4.Release 12 – 231 3GPP TS 36. The maximum value is preferable.4. Allows for a sufficient number of msg3 retransmissions.508 V12.2 Information Element RACH-ConfigCommon-DEFAULT ::= SEQUENCE { preambleInfo SEQUENCE { numberOfRA-Preambles preamblesGroupAConfig SEQUENCE {} } powerRampingParameters SEQUENCE { powerRampingStep preambleInitialReceivedTargetPower } ra-SupervisionInfo SEQUENCE { preambleTransMax Value/remark n52 Assuming the number of dedicated preambles is 12. 3-12A: Rach-ConfigDedicated-DEFAULT Derivation Path: 36. HO-toEUTRA SAME-BW DIFF-BW.3-13: RadioResourceConfigCommon-DEFAULT Derivation Path: 36.3.6.508 V12.4. HO-toEUTRA FullConfig.2 Information Element RadioResourceConfigCommon-DEFAULT ::= SEQUENCE { rach-ConfigCommon prach-Config pdsch-ConfigCommon pusch-ConfigCommon phich-Config Value/remark RACH-ConfigCommonDEFAULT PRACH-Config-DEFAULT Not present PDSCH-ConfigCommonDEFAULT PUSCH-ConfigCommonDEFAULT Not present PHICH-Config-DEFAULT pucch-ConfigCommon Not present PUCCH-ConfigCommonDEFAULT soundingRSUL-ConfigCommon SoundingRS-ULConfigCommonDEFAULT Not present UplinkPowerControlCom mon-DEFAULT uplinkPowerControlCommon antennaInfoCommon antennaInfoCommon SEQUENCE { antennaPortsCount } antennaInfoCommon SEQUENCE { Not present antennaPortsCount } p-Max tdd-Config an1 ul-CyclicPrefixLength uplinkPowerControlCommon-v1020 Comment Condition FullConfig.1 (2014-12) Rach-ConfigDedicated-DEFAULT Table 4.Release 12 – 232 3GPP TS 36.331 clause 6.2 Information Element Rach-ConfigDedicated-DEFAULT ::= SEQUENCE { ra-PreambleIndex ra-PRACH-MaskIndex } – Value/remark Comment Condition 52 0 RadioResourceConfigCommon-DEFAULT Table 4.6. FullConfig.331 clause 6. HO-toEUTRA FullConfig.3. HO-toEUTRA Not present Not present TDD-Config-DEFAULT len1 UplinkPowerControlCom mon-v1020-DEFAULT Not present } Condition Explanation 3GPP FDD TDD CA . HO-toEUTRA 2TX an2 FullConfig. Used for SCell with one antenna port Used for SCell with two antenna ports Used for SCell with four antenna ports 3GPP FDD TDD . Handover with full configuration option (Rel-9 or later) Inter-RAT handover to E-UTRA For Carrier Aggregation Test cases RadioResourceConfigCommonSCell-r10-DEFAULT Table 4.4.331 clause 6.508 V12.3-13A: RadioResourceConfigCommonSCell-r10-DEFAULT Derivation Path: 36.1 (2014-12) FDD cell environment TDD cell environment Used for cells with two antenna ports Source and target cell are configured with same bandwidth Source and target cell are configured with different bandwidth When UL Carrier Aggregation is used.6.3.2 Information Element RadioResourceConfigCommonSCell-r10DEFAULT ::= SEQUENCE { nonUL-Configuration-r10 SEQUENCE { dl-Bandwidth-r10 antennaInfoCommon-r10 SEQUENCE { antennaPortsCount antennaPortsCount antennaPortsCount Value/remark Comment Condition Same downlink bandwidth as used for target SCell an1 an2 an4 1TX 2TX 4TX Not present PHICH-Config-DEFAULT PDSCH-ConfigCommonDEFAULT Not present TDD-Config-DEFAULT FDD TDD } mbsfn-SubframeConfigList-r10 phich-Config-r10 pdsch-ConfigCommon-r10 tdd-Config-r10 } ul-Configuration-r10 ul-Configuration-r10 SEQUENCE { ul-FreqInfo-r10 SEQUENCE { ul-CarrierFreq-r10 ul-Bandwidth-r10 additionalSpectrumEmissionSCell-r10 } p-Max-r10 uplinkPowerControlCommonSCell-r10 soundingRS-UL-ConfigCommon-r10 ul-CyclicPrefixLength-r10 prach-ConfigSCell-r10 pusch-ConfigCommon-r10 Not present UL CA Not present Not present 1 (CA_NS_01) Not present UplinkPowerControlCom monSCell-r10-DEFAULT SoundingRS-ULConfigCommonDEFAULT len1 Not present FFS PUSCH-ConfigCommonDEFAULT } } Condition FDD TDD UL CA 1TX 2TX 4TX Explanation FDD cell environment TDD cell environment When UL Carrier Aggregation is used.Release 12 233 FDD TDD 2TX SAME-BW DIFF-BW UL CA FullConfig HO-to-EUTRA CA – 3GPP TS 36. Release 12 – 234 3GPP TS 36.6. with value SRBToAddMod-DEFAULT using condition SRB1 Not present Not present MAC-MainConfig-SRB Not present PhysicalConfigDedicated -DEFAULT using condition SRB1 } 3GPP See subclause 4.4.2 Information Element RadioResourceConfigCommonSIB-DEFAULT ::= SEQUENCE { rach-ConfigCommon bcch-Config pcch-Config prach-Config pdsch-ConfigCommon pusch-ConfigCommon pucch-ConfigCommon soundingRS-UL-ConfigCommon uplinkPowerControlCommon ul-CyclicPrefixLength uplinkPowerControlCommon-v1020 Value/remark Comment RACH-ConfigCommonDEFAULT BCCH-Config-DEFAULT PCCH-Config-DEFAULT PRACH-ConfigSIBDEFAULT PDSCH-ConfigCommonDEFAULT PUSCH-ConfigCommonDEFAULT PUCCH-ConfigCommonDEFAULT SoundingRS-ULConfigCommonDEFAULT UplinkPowerControlCom mon-DEFAULT len1 Not present UplinkPowerControlCom mon-v1020-DEFAULT Condition CA } Condition CA – Explanation For Carrier Aggregation Test cases RadioResourceConfigDedicated-SRB1 Table 4.2)) OF SEQUENCE {} drb-ToAddModList drb-ToReleaseList mac-MainConfig CHOICE { explicitValue } sps-Config physicalConfigDedicated Value/remark Comment 1 entry.8.2 See subclause 4.6.8.2 Information Element RadioResourceConfigDedicated-SRB1 ::= SEQUENCE { srb-ToAddModList SEQUENCE (SIZE (1.3-15: RadioResourceConfigDedicated-SRB1 Derivation Path: 36.3-14: RadioResourceConfigCommonSIB-DEFAULT Derivation Path: 36.3.1 (2014-12) RadioResourceConfigCommonSIB-DEFAULT Table 4.2 Condition .331 clause 6.3.508 V12..331 clause 6. 2 } NOTE: In cases where no RLC-UM bearer is configured.4.2)) OF SEQUENCE { srb-ToAddMod[1] } drb-ToAddModList SEQUENCE (SIZE (1.2 n+m entries DRB-ToAddModDEFAULT (k) using condition AM DRB-ToAddModDEFAULT (k) using condition UM n AM RLC DRBs See subclause 4.8.508 V12. Condition m=0 m>0 Explanation m is equal to zero m is greater than zero 3GPP .1 (2014-12) RadioResourceConfigDedicated-SRB2-DRB(n.2 m=0 See subclause 4..N) m is the number of UM RLC DRBs (0.8. large DRX Cycle length is used.DEFAULT using condition RBC See subclause 4.n+m] } drb-ToReleaseList mac-MainConfig CHOICE { explicitValue } sps-Config physicalConfigDedicated Value/remark Comment n is the number of AM RLC DRBs (1. k=n+1. k=1.8.m) Derivation Path: 36..6.8..331 clause 6..2 m>0 See subclause 4. m) ::= SEQUENCE { srb-ToAddModList SEQUENCE (SIZE (1.8.3.3-16: RadioResourceConfigDedicated-SRB2-DRB(n.. small DRX Cycle length is used.Release 12 – 235 3GPP TS 36.maxDRB)) OF SEQUENCE { drb-ToAddMod[k.8.m) Table 4. In cases where at least one RLC-UM bearer is configured.M) Condition 1 entry SRB-ToAddModDEFAULT using condition SRB2 See subclause 4.2 Information Element RadioResourceConfigDedicated-SRB2-DRB(n.2 m UM RLC DRBs See subclause 4.n] drb-ToAddMod[k.2 m>0 Not present MAC-MainConfig-RBC using condition DRX_L (note) MAC-MainConfig-RBC using condition DRX_S (note) Not present PhysicalConfigDedicated .. 2 Not present Not present (note) MAC-MainConfig-RBC using condition DRX_S (note) Condition n>0 m>0 m=0 m>0 See subclause 4.N) m is the number of UM RLC DRBs (0.508 V12. In cases where at least one RLC-UM bearer is added. k= BID+1+n.m) Derivation Path: 36.331 clause 6.BID+n] drb-ToAddMod[k.8. before applying the contents of this IE n AM RLC DRBs See subclause 4.1 (2014-12) RadioResourceConfigDedicated-DRB(n. k=BID+1.2 Not present Not present In cases where no RLC-UM bearer is added.2 m UM RLC DRBs See subclause 4.. m) ::= SEQUENCE { srb-ToAddModList drb-ToAddModList SEQUENCE (SIZE (1. BID+n+m] } drb-ToReleaseList mac-MainConfig mac-MainConfig CHOICE { explicitValue } sps-Config physicalConfigDedicated } NOTE: Value/remark Not present n+m entries DRB-ToAddModDEFAULT (k) using condition AM DRB-ToAddModDEFAULT (k) using condition UM BID is the total number of established DRBs in the UE. Condition n>0 m=0 m>0 Comment n is the number of AM RLC DRBs (0.8.4..3.8.m) Table 4... small DRX Cycle length is used..6.Release 12 – 236 3GPP TS 36.maxDRB)) OF SEQUENCE { drb-ToAddMod[k.3-17: RadioResourceConfigDedicated-DRB(n.2 Information Element RadioResourceConfigDedicated-DRB(n. existing DRX configuration is used without modification.M) Explanation n is greater than zero m is equal to zero m is greater than zero 3GPP . n+m] } drb-ToReleaseList mac-MainConfig CHOICE { explicitValue } sps-Config physicalConfigDedicated Value/remark Comment n is the number of AM RLC DRBs (1.N) m is the number of UM RLC DRBs (0.3-18: RadioResourceConfigDedicated-HO-TO-EUTRA(n. k=n+1.. small DRX Cycle length is used.1 (2014-12) RadioResourceConfigDedicated-HO-TO-EUTRA(n..2 m>0 Not present MAC-MainConfig-RBC using condition DRX_L (note) MAC-MainConfig-RBC using condition DRX_S (note) Not present PhysicalConfigDedicated .M) Condition 2 entries SRB-ToAddModDEFAULT using condition SRB1 SRB-ToAddModDEFAULT using condition SRB2 See subclause 4.331 clause 6.8.8.2 m UM RLC DRBs See subclause 4.DEFAULT using condition RBC See subclause 4.n] drb-ToAddMod[k. Condition m=0 m>0 Explanation m is equal to zero m is greater than zero 3GPP .4.2 m>0 See subclause 4.2 Information Element RadioResourceConfigDedicated-HO-TO-EUTRA(n. m) ::= SEQUENCE { srb-ToAddModList SEQUENCE (SIZE (1. In cases where at least one RLC-UM bearer is configured. large DRX Cycle length is used.m) Derivation Path: 36.3.m) Table 4.8.6...2 n+m entries DRB-ToAddModDEFAULT (k) using condition AM DRB-ToAddModDEFAULT (k) using condition UM n AM RLC DRBs See subclause 4. k=1.2 See subclause 4.8.508 V12.Release 12 – 237 3GPP TS 36.2 } NOTE: In cases where no RLC-UM bearer is configured.8.2)) OF SEQUENCE { srb-ToAddMod[1] srb-ToAddMod[2] } drb-ToAddModList SEQUENCE (SIZE (1.8...2 m=0 See subclause 4.8.maxDRB)) OF SEQUENCE { drb-ToAddMod[k. 8.8.maxDRB)) OF SEQUENCE { drb-ToAddMod[1] } drb-ToReleaseList mac-MainConfig CHOICE { explicitValue } sps-Config physicalConfigDedicated Value/remark Comment bid is the bearer identity Not present one entry DRB-ToAddModDEFAULT (bid) using condition UM See subclause 4.maxDRB)) OF SEQUENCE { drb-ToAddMod[1] } drb-ToReleaseList mac-MainConfig sps-Config physicalConfigDedicated Value/remark Comment bid is the bearer identity Condition Not present one entry DRB-ToAddModDEFAULT (bid) using condition AM See subclause 4. 3GPP See subclause 4.2 Information Element RadioResourceConfigDedicated-UM-DRBADD(bid) ::= SEQUENCE { srb-ToAddModList drb-ToAddModList SEQUENCE (SIZE (1. small DRX Cycle length is used.3-18A: RadioResourceConfigDedicated-AM-DRB-ADD(bid) Derivation Path: 36.Release 12 - 238 3GPP TS 36.8.4.331 clause 6..331 clause 6.3.3..2 Information Element RadioResourceConfigDedicated-AM-DRBADD(bid) ::= SEQUENCE { srb-ToAddModList drb-ToAddModList SEQUENCE (SIZE (1.1 (2014-12) RadioResourceConfigDedicated-AM-DRB-ADD(bid) Table 4.2 Not present MAC-MainConfig-RBC using condition DRX_S (note) Not present Not present } NOTE: Since one RLC-UM bearer is added.3-18B: RadioResourceConfigDedicated-UM-DRB-ADD(bid) Derivation Path: 36.508 V12.2 Not present Not present Not present Not present } - RadioResourceConfigDedicated-UM-DRB-ADD(bid) Table 4.6.6.2 Condition . 1 (2014-12) RadioResourceConfigDedicated.3..2 See subclause 4.2 Information Element RadioResourceConfigDedicated-DRB-REL(bid) ::= SEQUENCE { srb-ToAddModList drb-ToAddModList drb-ToReleaseList SEQUENCE (SIZE (1.3-19AAA: RadioResourceConfigDedicated-SCell_AddMod Derivation Path: 36.3-19: RadioResourceConfigDedicated-HO Derivation Path: 36.331 clause 6.331 clause 6.2 Condition .2 Information Element RadioResourceConfigDedicated-HO ::= SEQUENCE { srb-ToAddModList drb-ToAddModList drb-ToReleaseList mac-MainConfig sps-Config physicalConfigDedicated Value/remark Not present Not present Not present Not present Not present PhysicalConfigDedicatedDEFAULT using condition RBC-HO } 3GPP Comment See subclause 4.DRB-REL(bid) Table 4.Release 12 - 239 3GPP TS 36.6.331 clause 6.4.8.3.maxDRB)) OF drb-Identity[1] mac-MainConfig sps-Config physicalConfigDedicated } – Value/remark Comment bid is the bearer identity Condition Not present Not present one entry bid Not present Not present Not present RadioResourceConfigDedicated-SCell_AddMod Table 4.6.6.8.508 V12.3.3-18C: RadioResourceConfigDedicated-DRB-REL(bid) Derivation Path: 36.2 } – RadioResourceConfigDedicated-HO Table 4.8.2 Information Element RadioResourceConfigDedicated-SCell_AddMod ::= SEQUENCE { srb-ToAddModList drb-ToAddModList drb-ToReleaseList mac-MainConfig sps-Config physicalConfigDedicated Value/remark Not present Not present Not present MAC-MainConfig-RBC using condition SCell_AddMod Not present PhysicalConfigDedicatedDEFAULT using condition SCell_AddMod Comment Condition See subclause 4. 2-1: RLC-Config-DRB-AM Information Element Value/remark RLC-Config-DRB-AM-RECONFIG ::= CHOICE { am SEQUENCE { ul-AM-RLC SEQUENCE { t-PollRetransmit ms855 pollPDU p64 pollByte kB250 maxRetxThreshold t8 } dl-AM-RLC SEQUENCE { t-Reordering ms85 t-StatusProhibit ms50 } } } – Comment Condition RLC-Config-DRB-UM-RECONFIG Table 4.3.2 Information Element RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE { physicalConfigDedicatedSCell-r10 Value/remark Comment Condition PhysicalConfigDedicated SCell-r10-DEFAULT } – RLC-Config-DRB-AM-RECONFIG Table 4.6.6.331 clause 6.2.508 table 4.3-19AA: RadioResourceConfigDedicatedSCell-r10-DEFAULT Derivation Path: 36.1-1: RLC-Config-DRB-UM Information Element Value/remark RLC-Config-DRB-UM-RECONFIG ::= CHOICE { um-Bi-Directional SEQUENCE { ul-UM-RLC SEQUENCE { sn-FieldLength Size10 } dl-UM-RLC SEQUENCE { sn-FieldLength Size10 t-Reordering ms55 } } } 3GPP Comment Condition .3.6.8.508 table 4.1.508 V12.3-19A: RLC-Config-DRB-AM-RECONFIG Derivation Path: 36.1 (2014-12) RadioResourceConfigDedicatedSCell-r10-DEFAULT Table 4.4.3-19B: RLC-Config-DRB-UM-RECONFIG Derivation Path: 36.2.Release 12 – 240 3GPP TS 36.3.1.8. 2 Information Element sCellToReleaseList-r10 SEQUENCE (SIZE (1.6..2.508 V12. } – SCellToRelease-r10-DEFAULT Table 4.2.3.6.4.3-19C: RLC-Config-SRB-AM-RECONFIG Derivation Path: 36. 9.6.1 Information Element RLC-Config-SRB-AM-RECONFIG ::= CHOICE { am SEQUENCE { ul-AM-RLC SEQUENCE { t-PollRetransmit pollPDU pollByte maxRetxThreshold } dl-AM-RLC SEQUENCE { t-Reordering t –StatusProhibit } } } – Value/remark ms50 pInfinity kBinfinity t6 ms40 ms0 Comment Condition Default Default Default SCellToAddMod-r10-DEFAULT Table 4.331 clause 6.331 clause 6.2.1 (2014-12) RLC-Config-SRB-AM-RECONFIG Table 4.2..331 clause 6.maxSCell-r10) OF SEQUENCE { sCellIndex-r10[1] } Value/remark 1 3GPP .3-19E: SCellToRelease-r10-DEFAULT Derivation Path: 36.Release 12 – 241 3GPP TS 36..2 Information Element SCellToAddMod-r10 ::= SEQUENCE { sCellIndex-r10 cellIdentification-r10 SEQUENCE { physCellId-r10 dl-CarrierFreq-r10 } radioResourceConfigCommonSCell-r10 radioResourceConfigDedicatedSCell-r10 Value/remark Comment Condition Comment Condition Set according to specific message content Set according to specific message content Set according to specific message content RadioResourceConfigCo mmonSCell-r10DEFAULT RadioResourceConfigDe dicatedSCell-r10DEFAULT .3-19D: SCellToAddMod-r10-DEFAULT Derivation Path: 36. 6.3-1 in TS 36.1 (2014-12) SchedulingRequest-Config-DEFAULT Table 4.6.211) Assuming SRS density is high (see Table 5.6.3.3-20: SchedulingRequest-Config-DEFAULT Derivation Path: 36.6.8 sc0 sc4 ackNackSRS-SimultaneousTransmission srs-MaxUpPts } TRUE Not Present } Condition FDD TDD Explanation FDD cell environment TDD cell environment 3GPP Comment Channelbandwidthdependent parameter Assuming SRS density is high (see Table 5.2 Information Element SoundingRS-UL-ConfigCommon-DEFAULT ::= SEQUENCE { setup SEQUENCE { -srs-BandwidthConfig srs-SubframeConfig Value/remark See subclause 4.508 V12.5.331 clause 6.3-20A: Void – SoundingRS-UL-ConfigCommon-DEFAULT Table 4.6.4.331 clause 6.2 Information Element SchedulingRequest-Config-DEFAULT ::= CHOICE { setup SEQUENCE { sr-PUCCH-ResourceIndex sr-ConfigIndex Value/remark See subclause 4.5.Release 12 – 242 3GPP TS 36.8 Comment Channelbandwidthdependent parameter 30 27 n4 dsr-TransMax Condition FDD TDD } } Condition FDD TDD Explanation FDD cell environment TDD cell environment Table 4.3.3.3-21: SoundingRS-UL-ConfigCommon-DEFAULT Derivation Path: 36.211) Typical value in real network Condition FDD TDD .3.3-2 in TS 36. Release 12 – 243 3GPP TS 36.2 Information Element SoundingRS-UL-ConfigDedicated-DEFAULT ::= CHOICE { setup SEQUENCE { srs-Bandwidth srs-HoppingBandwidth freqDomainPosition duration srs-ConfigIndex Value/remark bw0 Condition bw0 used with no frequency hopping.2-1 in TS 36.2-2 in TS 36.2 Information Element SoundingRS-UL-ConfigDedicatedAperiodic-r10 ::= CHOICE { setup SEQUENCE { srs-ConfigIndexAp-r10 srs-ConfigApDCI-Format4-r10 srs-ActivateAp-r10 } } Value/remark 10 Not present Not present 3GPP Comment Condition ..1023) See Table 8.3.1 (2014-12) SoundingRS-UL-ConfigDedicated-DEFAULT Table 4.508 V12.213 31 transmissionComb cyclicShift Comment FDD TDD 0 cs0 } } Condition FDD TDD Explanation FDD cell environment TDD cell environment Table 4.6.213 INTEGER (0.3. bw3 used with frequency hopping hbw0 0 TRUE 20 See Table 8.6.3-22: SoundingRS-UL-ConfigDedicated-DEFAULT Derivation Path: 36.3-22AB: SoundingRS-UL-ConfigDedicatedAperiodic-r10-DEFAULT Derivation Path: 36.331 clause 6.3-22AA: Void – SoundingRS-UL-ConfigDedicatedAperiodic-r10-DEFAULT Table 4.4.6.331 clause 6. 4.3-22A: SRB-ToAddModList-RECONFIG Derivation Path: 36.2 Information Element TPC-PDCCH-Config-DEFAULT ::= CHOICE { setup SEQUENCE { tpc-RNTI tpc-Index CHOICE { indexOfFormat3 } Value/remark ‘03FF’H ‘01FA’H 1 } } Condition PUCCH PUSCH Explanation For PUCCH For PUSCH 3GPP PUCCH PUSCH .3-23: TDD-Config-DEFAULT Derivation Path: 36.3-24: TPC-PDCCH-Config-DEFAULT Derivation Path: 36.Release 12 – 244 3GPP TS 36..331 clause 6.2 Information Element TDD-Config-DEFAULT ::= SEQUENCE { subframeAssignment specialSubframePatterns } – Value/remark Comment Condition Comment Condition sa1 Ssp6 TPC-PDCCH-Config-DEFAULT Table 4.508 V12.6.6.331 clause 6.2)) OF SEQUENCE { srb-Identity[1] rlc-Config[1] CHOICE { explicitValue logicalChannelConfig[1] CHOICE { defaultValue } srb-Identity[2] rlc-Config[2] CHOICE { explicitValue Value/remark 2 Entries Comment Condition 1 RLC-Config-SRB-AMRECONFIG NULL 2 RLC-Config-SRB-AMRECONFIG } logicalChannelConfig[2] CHOICE { defaultValue } NULL } – TDD-Config-DEFAULT Table 4.3.6.3.3.2 Information Element SRB-ToAddModList ::= SEQUENCE (SIZE (1.331 clause 6.1 (2014-12) SRB-ToAddModList-RECONFIG Table 4. 4.331 clause 6.6.6.8) p0-NominalPUCCH -117 (-117 dBm) deltaFList-PUCCH SEQUENCE { deltaF-PUCCH-Format1 deltaF0 deltaF-PUCCH-Format1b deltaF3 deltaF-PUCCH-Format2 deltaF0 deltaF-PUCCH-Format2a deltaF0 deltaF-PUCCH-Format2b deltaF0 } deltaPreambleMsg3 Comment Condition Typical value in real network Typical value in real network Thermal noise = -121 dBm NF = 5 dB IoT = 6 dB Required SNR = -7.331 clause 6.3.8) 3GPP Comment Condition .3.Release 12 – 245 3GPP TS 36.3-25: UplinkPowerControlCommon-DEFAULT Derivation Path: 36.3-25A: UplinkPowerControlCommonSCell-r10-DEFAULT Derivation Path: 36.2 Information Element UplinkPowerControlCommon-DEFAULT ::= SEQUENCE { p0-NominalPUSCH Value/remark -85 (-85 dBm) alpha al08 (0.2 Information Element UplinkPowerControlCommonSCell-r10 ::= SEQUENCE { p0-NominalPUSCH-r10 alpha-r10 } Value/remark -85 (-85 dBm) al08 (0.5 dB (1-bit A/N) -> -117 dB In accordance with RAN1 simulation results In accordance with RAN1 simulation results In accordance with RAN1 simulation results In accordance with RAN1 simulation results In accordance with RAN1 simulation results 4 } – UplinkPowerControlCommonSCell-r10-DEFAULT Table 4.1 (2014-12) UplinkPowerControlCommon-DEFAULT Table 4.508 V12. 2 Information Element UplinkPowerControlCommon-v1020-DEFAULT ::= SEQUENCE { deltaF-PUCCH-Format3-r10 deltaF-PUCCH-Format1bCS-r10 Value/remark Comment deltaF0 deltaF4 Condition RM coding Dual RM coding deltaF1 } Condition RM coding Dual RM coding – Explanation Used for Reed-Muller coding Used for Dual Reed-Muller coding UplinkPowerControlDedicated-DEFAULT Table 4.6.3-26: UplinkPowerControlDedicated-DEFAULT Derivation Path: 36.6.6.3.331 clause 6.1 (2014-12) UplinkPowerControlCommon-v1020-DEFAULT Table 4.508 V12.3.331 clause 6.331 clause 6.3-26A: UplinkPowerControlDedicated-v1020-DEFAULT Derivation Path: 36.2 Information Element UplinkPowerControlDedicated-v1020 ::= SEQUENCE { deltaTxD-OffsetListPUCCH-r10 deltaTxD-OffsetListPUCCH-r10 SEQUENCE { deltaTxD-OffsetPUCCH-Format1-r10 deltaTxD-OffsetPUCCH-Format1a1b-r10 deltaTxD-OffsetPUCCH-Format22a2b-r10 deltaTxD-OffsetPUCCH-Format3-r10 } pSRS-OffsetAp-r10 Value/remark Condition Not Present TxD dB0 dB0 dB0 dB0 0 } Condition TxD SRSAp Comment Explanation When PUCCH Transmission Diversity is performed.4.3-25AA: UplinkPowerControlCommon-v1020-DEFAULT Derivation Path: 36.Release 12 – 246 3GPP TS 36. Aperiodic SRS configured 3GPP SRSAp Not present .2 Information Element UplinkPowerControlDedicated-DEFAULT ::= SEQUENCE { p0-UE-PUSCH deltaMCS-Enabled accumulationEnabled p0-UE-PUCCH pSRS-Offset filterCoefficient } – Value/remark Comment Condition 0 en0 TRUE 0 3 (-6 dB) fc4 UplinkPowerControlDedicated-v1020-DEFAULT Table 4.3. 508 V12.3-26BA: UplinkPowerControlDedicated-v1130-DEFAULT Derivation Path: 36.Release 12 – 247 3GPP TS 36.3-26B: UplinkPowerControlDedicatedSCell-r10-DEFAULT Derivation Path: 36.2 Information Element RadioResourceConfigDedicated-DRB ::= SEQUENCE { srb-ToAddModList drb-ToAddModList } drb-ToReleaseList mac-MainConfig sps-Config physicalConfigDedicated Value/remark Not present DRB-ToAddModListRECONFIG Not present Not present Not present Not present } 3GPP Comment Condition .1 (2014-12) UplinkPowerControlDedicated-v1130-DEFAULT Table 4.6.3.2 Information Element UplinkPowerControlDedicated-v1130 -DEFAULT ::= SEQUENCE { pSRS-Offset-v1130 pSRS-OffsetAp-v1130 deltaTxD-OffsetListPUCCH-v1130 = SEQUENCE { deltaTxD-OffsetPUCCH-Format1bCS-r11 } } – Value/remark Comment Condition FFS FFS FFS UplinkPowerControlDedicatedSCell-r10-DEFAULT Table 4.3.6.2 Information Element UplinkPowerControlDedicatedSCell-r10 ::= SEQUENCE { p0-UE-PUSCH-r10 deltaMCS-Enabled-r10 accumulationEnabled-r10 pSRS-Offset-r10 pSRS-OffsetAp-r10 filterCoefficient-r10 pathlossReferenceLinking-r10 } - Value/remark Comment Condition 0 en0 TRUE 7 7 fc4 sCell RadioResourceConfigDedicated-DRB-Mod Table 4.331 clause 6.331 clause 6.3.6.3-27: RadioResourceConfigDedicated-DRB-Mod Derivation Path: 36.331 clause 6.4. 508 V12.331 clause 6.3-28: RadioResourceConfigDedicated-PCell-PATTERN Derivation Path: 36.3-29: OtherConfig-r9 Derivation Path: 36.1 (2014-12) RadioResourceConfigDedicated-PCell-PATTERN Table 4.6.Release 12 - 248 3GPP TS 36.2 Information Element measSubframePatternPCell ::= CHOICE { MeasSubframePattern-r10 ::= CHOICE { subframePatternFDD-r10 Value/remark Comment Condition Comment Condition ‘00110011001100110011 00110011001100110011’ B FFS subframePatternTDD-r10 } } - OtherConfig-r9 Table 4.3.331 clause 6.3.6. The UE is not allowed to send power preference indications 3GPP Release Setup .6 Information Element OtherConfig-r9 ::= SEQUENCE { reportProximityConfig-r9 ::= SEQUENCE { proximityIndicationEUTRA-r9 proximityIndicationUTRA-r9 } IDC-Config-r11 SEQUENCE { idc-Indication-r11 autonomouseDenialParameters-r11 ::= SEQUENCE { autonomousDenialSubframes-r11 autonomousDenialValidity-r11 } } PowerPrefIndicationConfig-r11 CHOICE { Release setup SEQUENCE { powerPrefIndicationTimer-r11 } } ObtainLocationConfig-r11 ::= SEQUENCE { obtainLocation-r11 } } Condition Setup Release Value/remark Not Present Not Present Not Present Not Present Not Present NULL s30 Not present Explanation The UE is allowed to send power preference indications.4. 2.331 clause 6.508 V12.4 Security control information elements – SecurityConfigHO-DEFAULT Table 4.3.2.3.6.1 (2014-12) 4.Release 12 249 3GPP TS 36. 6.331 clause 6.6. 6.2. For RF .6.3 Information Element SecurityConfigSMC-DEFAULT ::= SEQUENCE { securityAlgorithmConfig SEQUENCE { cipheringAlgorithm integrityProtAlgorithm Value/remark Set according to PIXIT parameter for default ciphering algorithm eea0 Set according to PIXIT parameter for default integrity protection algorithm spare1 or eia0-v920 eia1 eia2 } } Condition For SIG For RF Explanation Used for signalling test cases Used for RF/RRM test cases 3GPP For SIG For RF For SIG This IE is set to one of the algorithms supported by the UE as indicated in the IE "UE network capability" in the ATTACH REQUEST message.4.3 Information Element SecurityConfigHO-DEFAULT ::= SEQUENCE { handoverType CHOICE { intraLTE SEQUENCE { securityAlgorithmConfig keyChangeIndicator nextHopChainingCount } } } – Value/remark Comment Condition Comment Condition Not present FALSE 0 SecurityConfigSMC-DEFAULT Table 4.4-2: SecurityConfigSMC-DEFAULT Derivation Path: 36.2.4-1: SecurityConfigHO-DEFAULT Derivation Path: 36. 508 V12.6. RadioResourceConfigCo mmon-DEFAULT Not present Rach-ConfigDedicatedDEFAULT } Condition SAME-BW DIFF-BW Explanation Source and target cell are configured with same bandwidth Source and target cell are configured with different bandwidth 3GPP HO-toEUTRA FullConfig.5 Mobility control information elements – MobilityControlInfo-HO Table 4.3.1 (2014-12) 4.5-1: MobilityControlInfo-HO Derivation Path: 36.Release 12 250 3GPP TS 36. HO-toEUTRA .4.6.4 Information Element MobilityControlInfo-HO ::= SEQUENCE { targetPhysCellId carrierFreq carrierBandwidth carrierBandwidth SEQUENCE { dl-Bandwidth ul-Bandwidth Value/remark Set according to specific message content Set according to specific message content Not present Comment Condition SAME-BW DIFF-BW Same downlink bandwidth as used for target cell Not present } additionalSpectrumEmission t304 newUE-Identity radioResourceConfigCommon rach-ConfigDedicated Not present 1 ms1000 SS arbitrarily selects a value between ‘003C’H and ‘FFF2’H.331 clause 6. 6-1A: MeasGapConfig-GP1 Derivation Path: 36.4.331. UTRAN GERAN.5.3. table 6. Condition INTER-FREQ INTER-RAT eICIC - Condition Explanation For E-UTRA inter-freq measurements For inter-RAT measurements with UTRAN and GERAN For eICIC measurements MeasGapConfig-GP1 Table 4.1-1 is applied.331. clause 6. clause 6.Release 12 251 3GPP TS 36.3.6 Measurement information elements - MeasConfig-DEFAULT Table 4. INTERRAT MeasGapConfig-GP2 s-Measure preRegistrationInfoHRPD speedStatePars } Note: Not present Not present Not present For signalling test.508 V12.5 Information Element MeasConfig-DEFAULT ::= SEQUENCE { measObjectToRemoveList measObjectToAddModList reportConfigToRemoveList reportConfigToAddModList measIdToRemoveList measIdToAddModList quantityConfig measGapConfig Value/remark Comment Not present Not present MeasObjectEUTRAGENERIC Not present Not present ReportConfigToAddModLi st_DEFAULT Not present Not present MeasIdToAddModList_D EFAULT QuantityConfig-DEFAULT Not present MeasGapConfig-GP1 eICIC eICIC eICIC INTERFREQ.6-1: MeasConfig-DEFAULT Derivation Path: 36.6.6.6.5 Information Element MeasGapConfig-GP1 ::= CHOICE { setup SEQUENCE { gapOffset CHOICE { gp0 } } } Value/remark 0 3GPP Comment TGRP = 40 ms Condition .1 (2014-12) 4. .Release 12 - 252 3GPP TS 36.3.331.1 (2014-12) MeasGapConfig-GP2 Table 4. bc3.6-1C: MeasObjectCDMA2000-GENERIC Derivation Path: 36.spare9. spare7.6-1D: ReportConfigToAddModList_DEFAULT Derivation Path: 36.6.3. spare12.331 clause 6. bc7.. spare3. bc9. bc15. bc12. clause 6. spare13. spare6.5 Information Element ReportConfigToAddModList_DEFAULT ::= SEQUENCE { reportConfigId[1] reportConfig[1] Value/remark 1 entry IdReportConfig-A3 ReportConfigEUTRA-A3 } 3GPP Comment Condition . bc13. bc17.331. INTEGER (0 to 2047) Downlink channel number } searchWindowSize As per specific message content 0 (0 dB) Not present [Not present] Not present offsetFreq cellsToRemoveList cellsToAddModList cellForWhichToReportCGI Comment Condition INTEGER (0.6-1B: MeasGapConfig-GP2 Derivation Path: 36.6. bc5. bc8. spare8. bc2. typeHRPD] As per specific message content Should be one of the following: bc0. spare11. bc14. bc6. spare5.6. bc11. bc10.. spare14. clause 6. bc4.15) } – ReportConfigToAddModList_DEFAULT Table 4. bc1.3. bc16.4. spare4. spare1. spare10. spare2.508 V12.5 Information Element MeasObjectCDMA2000-GENERIC ::= SEQUENCE { cdma2000-Type carrierFreq SEQUENCE { bandClass arfcn Value/remark As per specific message content [type1XRTT..5 Information Element MeasGapConfig-GP2 ::= CHOICE { setup SEQUENCE { gapOffset CHOICE { gp1 } } } – Value/remark 0 Comment Condition TGRP = 80 ms MeasObjectCDMA2000-GENERIC Table 4. 331 clause 6.6.5 Information Element MeasIdToAddModList_DEFAULT ::= SEQUENCE { measId[1] measObjectId[1] reportConfigId[1] } - Value/remark 1 entry 1 IdMeasObject-f1 IdReportConfig-A3 Comment Condition MeasObjectEUTRA-GENERIC Table 4.Release 12 – 253 3GPP TS 36. clause 6.3.331.5 Information Element MeasObjectEUTRA-GENERIC(Freq) ::= SEQUENCE { carrierFreq allowedmeasBandwidth presenceAntennaPort1 neighbourCellConfig Value/remark Downlink EARFCN for Freq The number of the resource blocks for Freq FALSE TRUE offsetFreq cellsToRemoveList cellsToAddModList blackCellsToRemoveList blackCellsToAddModList cellForWhichToReportCGI measCycleSCell-r10 '01'B (No MBSFN subframes are present in all neighbour cells) 0 (dB 0) Not present Not present Not present Not present Not present sf512 measSubframePatternConfigNeigh-r10 Not present Comment At least two cellspecific antenna ports are used in all neighbouring cells.6-2: MeasObjectEUTRA-GENERIC(Freq) Derivation Path: 36.1 (2014-12) MeasIdToAddModList_DEFAULT Table 4.6-1E: MeasIdToAddModList_DEFAULT Derivation Path: 36.4.6.3. } Condition SCell_EXIST All neighCells with port1 Explanation When SCell exists on the carrier frequency indicated by carrierFreq Used for all neighbouring cells with at least two cell-specific antenna ports 3GPP Condition All neighCells with port1 SCell_EXI ST .508 V12. MBSFN doesn’t apply by default. 3.1 (2014-12) MeasObjectGERAN-GENERIC Table 4.4. the neighbouring cell list needs to be provided in specific test cases.6-2A: MeasObjectGERAN-GENERIC(Freq) Derivation Path: 36.331 clause 6.6.6.Release 12 - 254 3GPP TS 36.331 clause 6.5 Information Element MeasObjectGERAN-GENERIC(Freq) ::= SEQUENCE { carrierFreqs SEQUENCE { startingARFCN bandIndicator followingARFCNs CHOICE { explicitListOfARFCNs Value/remark Comment Condition Downlink GERAN ARFCN of Freq Set according to the band used for GERAN cells under test Set the corresponding ARFCN of GERAN cells under test } } offsetFreq ncc-Permitted cellForWhichToReportCGI 0 (dB 0) ‘01000000'B Not present NCC=1 permitted } - MeasObjectUTRA-GENERIC Table 4.6-3: MeasObjectUTRA-GENERIC(Freq) Derivation Path: 36.5 Information Element MeasObjectUTRA-GENERIC(Freq) ::= SEQUENCE { carrierFreq Value/remark offsetFreq cellsToRemoveList cellsToAddModList Downlink UARFCN of Freq 0 (dB 0) Not present Not present cellForWhichToReportCGI Not present } 3GPP Comment For UTRA.508 V12. Condition .3. Release 12 - 255 3GPP TS 36. clause 6.1 (2014-12) QuantityConfig-DEFAULT Table 4.6.6-4: ReportConfigEUTRA-A1(Thres) Derivation Path: 36.6.331.3.5 Information Element ReportConfigEUTRA-A1(Thres) ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventA1 SEQUENCE { a1-Threshold CHOICE { threshold-RSRP Value/remark Thres+140 } } } hysteresis timeToTrigger 0 (0 dB) ms256 } } triggerQuantity reportQuantity maxReportCells reportInterval reportAmount rsrp both 1 ms1024 r1 } 3GPP Comment Thres is actual threshold value in dBm Condition .508 V12.6-3A: QuantityConfig-DEFAULT Derivation Path: 36.331 clause 6.3.4.5 Information Element QuantityConfig-DEFAULT ::= SEQUENCE { quantityConfigEUTRA SEQUENCE { filterCoefficientRSRP filterCoefficientRSRQ } quantityConfigUTRA SEQUENCE {} quantityConfigUTRA SEQUENCE { measQuantityUTRA-FDD measQuantityUTRA-FDD measQuantityUTRA-TDD filterCoefficient Value/remark Not present Not present Condition DEFAULT fc4 DEFAULT fc4 Not present UTRAN cpich-EcN0 cpich-RSCP pccpch-RSCP Not present } quantityConfigGERAN SEQUENCE {} quantityConfigGERAN SEQUENCE { measQuantityGERAN filterCoefficient } quantityConfigCDMA2000 SEQUENCE {} quantityConfigCDMA2000 SEQUENCE { measQuantityCDMA2000 } Comment For signalling test cases DEFAULT fc4 Not present GERAN rssi Not present DEFAULT fc2 Not present CDMA2000 [FFS] } Condition UTRAN GERAN CDMA2000 - Explanation For inter-RAT measurements with UTRAN For inter-RAT measurements with GERAN For inter-RAT measurements with CDMA2000 ReportConfigEUTRA-A1 Table 4. 4.Release 12 - 256 3GPP TS 36.1 (2014-12) ReportConfigEUTRA-A2 Table 4.6.331 clause 6.6.3.3.5 Information Element ReportConfigEUTRA-A2(Thres) ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventA2 SEQUENCE { a2-Threshold CHOICE { threshold-RSRP Value/remark Thres+140 Comment Condition Thres is actual threshold value in dBm } } } hysteresis timeToTrigger 0 (0 dB) ms320 } } triggerQuantity reportQuantity maxReportCells reportInterval reportAmount rsrp both 1 ms1024 r1 } - ReportConfigEUTRA-A3 Table 4.331 clause 6.6-5: ReportConfigEUTRA-A2(Thres) Derivation Path: 36.5 Information Element ReportConfigEUTRA-A3 ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventA3 SEQUENCE { a3-Offset reportOnLeave Value/remark 0 (0 dB) FALSE } } hysteresis timeToTrigger 0 (0 dB) ms640 } } triggerQuantity reportQuantity maxReportCells reportInterval reportAmount rsrp both 1 ms1024 r1 } 3GPP Comment To reduce interference between intrafrequency multiple cells Condition .6-6: ReportConfigEUTRA-A3 Derivation Path: 36.508 V12. 5 Information Element ReportConfigEUTRA-A4 ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventA4 SEQUENCE { a4-Threshold CHOICE{ threshold-RSRP threshold-RSRQ Value/remark Thres + 140 Thres * 2 + 40 Comment Condition Thres is actual threshold value in dBm Thres is actual threshold value in dB Not RSRQ RSRQ } } } hysteresis timeToTrigger 0 (0 dB) ms0 } } triggerQuantity reportQuantity maxReportCells reportInterval reportAmount si-RequestForHO-r9 ue-RxTxTimeDiffPeriodical-r9 rsrp rsrq both 1 ms1024 r1 Not Present Not Present } Condition RSRQ Explanation When RSRQ based measurement is applied 3GPP Not RSRQ RSRQ .1 (2014-12) ReportConfigEUTRA-A4 Table 4.3.331 clause 6.4.6-6AA: ReportConfigEUTRA-A4(Thres) Derivation Path: 36.6.508 V12.Release 12 - 257 3GPP TS 36. Thres2) Derivation Path: 36.5 Information Element ReportConfigEUTRA-A5 ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventA5 SEQUENCE { a5-Threshold1 CHOICE{ threshold-RSRP threshold-RSRQ Value/remark Thres1 + 140 Thres1 * 2 + 40 } a5-Threshold2 CHOICE{ threshold-RSRP threshold-RSRQ Thres2 + 140 Thres2 * 2 + 40 Comment Condition Thres1 is actual threshold value in dBm Thres1 is actual threshold value in dB Not RSRQ Thres2 is actual threshold value in dBm Thres2 is actual threshold value in dB Not RSRQ RSRQ RSRQ } } } hysteresis timeToTrigger 0 (0 dB) ms0 } } triggerQuantity reportQuantity maxReportCells reportInterval reportAmount si-RequestForHO-r9 ue-RxTxTimeDiffPeriodical-r9 rsrp rsrq both 1 ms1024 r1 Not Present Not Present } Condition RSRQ Explanation See the definition below table 4.6.6.4.6-6AB: ReportConfigEUTRA-A5(Thres1.Release 12 - 258 3GPP TS 36.6-6AA.331 clause 6.1 (2014-12) ReportConfigEUTRA-A5 Table 4.3.508 V12. 3GPP Not RSRQ RSRQ . 6.3.508 V12.6.Release 12 - 259 3GPP TS 36.5 Information Element ReportConfigEUTRA-PERIODICAL ::= SEQUENCE { triggerType CHOICE { periodical SEQUENCE { purpose } } triggerQuantity reportQuantity maxReportCells reportInterval reportAmount } Value/remark reportStrongestCells rsrp both 1 ms1024 infinity 3GPP .5 Information Element ReportConfigEUTRA-A6 ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventA6-r10 SEQUENCE { a6-Offset-r10 a6-ReportOnLeave-r10 } } hysteresis timeToTrigger } } triggerQuantity reportQuantity maxReportCells reportInterval reportAmount si-RequestForHO-r9 ue-RxTxTimeDiffPeriodical-r9 includeLocationInfo-r10 reportAddNeighMeas-r10 } - Value/remark Comment Condition Comment Condition 0 (0 dB) FALSE 0 (0 dB) ms640 rsrp both 1 ms1024 r1 Not Present Not Present Not Present Not Present ReportConfigEUTRA-PERIODICAL Table 4.6-6A: ReportConfigEUTRA-A6 Derivation Path: 36.6-7: ReportConfigEUTRA-PERIODICAL Derivation Path: 36.331 clause 6.4.1 (2014-12) ReportConfigEUTRA-A6 Table 4.331 clause 6.3. 30) } } maxReportCells 6 In line with RAN4 requirement reportInterval reportAmount ms1024 r1 } } } hysteresis timeToTrigger } 3GPP Condition .331 clause 6.508 V12.6.Release 12 - 260 3GPP TS 36.1 (2014-12) ReportConfigInterRAT-B1-GERAN Table 4.3.6-7A: ReportConfigInterRAT-B1-GERAN(GERAN-Thres) Derivation Path: 36.5 Information Element ReportConfigInterRAT-B1-GERAN(GERAN-Thres) ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventB1 SEQUENCE { b1-Threshold CHOICE { b1-ThresholdGERAN Value/remark Comment (GERAN-Thres + 110) GERAN-Thres is actual value in dBm 0 ms0 INTEGER(0..4. 508 V12.6-7B: ReportConfigInterRAT-B1-UTRA(UTRA-Thres) Derivation Path: 36.6.4.331 clause 6.5 Information Element ReportConfigInterRAT-B1-UTRA(UTRA-Thres) ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventB1 SEQUENCE { b1-Threshold CHOICE { b1-ThresholdUTRA CHOICE { utra-EcN0 utra-RSCP Value/remark (UTRA-Thres * 2 + 49) UTRA-Thres + 115 utra-RSCP UTRA-Thres + 115 Comment Condition UTRA-Thres is actual Ec/NO value in dB For signalling test cases UTRA-FDD UTRA-Thres is actual RSCP value in dBm UTRA-Thres is actual RSCP value in dBm } } } } hysteresis timeToTrigger 3 (1.5 dB) ms0 } } maxReportCells 6 reportInterval reportAmount ms1024 r1 In line with RAN4 requirement } Condition UTRA-FDD UTRA-TDD Explanation UTRA FDD cell environment UTRA TDD cell environment 3GPP UTRA-FDD UTRA-TDD .1 (2014-12) ReportConfigInterRAT-B1-UTRA Table 4.Release 12 - 261 3GPP TS 36.3. 331 clause 6. ms1024. r32. ms5120..1 (2014-12) ReportConfigInterRAT-B2-CDMA2000 Table 4.Release 12 - 262 3GPP TS 36. ms480. ms2048. spare3. CDMA2000-Thres) Derivation Path: 36.6-7C: ReportConfigInterRAT-B2-CDMA2000(EUTRA-Thres. min1. r4. r2. spare2. infinity Condition . min12. r8. min60. CDMA2000-Thres) ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventB2 SEQUENCE { b2-Threshold1 CHOICE { threshold-RSRP Value/remark Comment EUTRA-Thres+140 EUTRA-Thres is actual threshold value in dBm [30 (-15 dB)] Integer (0.3.30) } } maxReportCells reportInterval [8] [ms2048] reportAmount [r1] } b2-Threshold2 CHOICE { b2-Threshold2CDMA2000 } } 3GPP Range: ms120.5 Information Element ReportConfigInterRAT-B2-CDMA2000(EUTRA-Thres.508 V12. ms640.. ms10240. r64. spare1 Range: r1. min6. min30.6.4. ms240.63) } } hysteresis timeToTrigger [2 (1 dB)] ms0 INTEGER(0. r16. 5 Information Element ReportConfigInterRAT-B2-GERAN(EUTRA-Thres..6.Release 12 263 3GPP TS 36.3.30) } } maxReportCells 6 In line with RAN4 requirement reportInterval reportAmount ms1024 r1 } b2-Threshold2 CHOICE { b2-Threshold2GERAN } } } hysteresis timeToTrigger } 3GPP Condition . GERAN-Thres) Derivation Path: 36.6.508 V12.4.6-7D: void - ReportConfigInterRAT-B2-GERAN Table 4. GERAN-Thres) ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventB2 SEQUENCE { b2-Threshold1 CHOICE { threshold-RSRP Value/remark Comment EUTRA-Thres+140 EUTRA-Thres is actual threshold value in dBm GERAN-Thres + 110 GERAN-Thres is actual value in dBm 0 ms0 INTEGER(0.1 (2014-12) Table 4.331 clause 6.6-7E: ReportConfigInterRAT-B2-GERAN(EUTRA-Thres. UTRA-Thres) Derivation Path: 36.508 V12.6.4.3.331 clause 6. UTRA-Thres) ::= SEQUENCE { triggerType CHOICE { event SEQUENCE { eventId CHOICE { eventB2 SEQUENCE { b2-Threshold1 CHOICE { threshold-RSRP } b2-Threshold2 CHOICE { b2-Threshold2UTRA CHOICE { utra-EcN0 utra-RSCP Value/remark EUTRA-Thres+140 EUTRA-Thres is actual threshold value in dBm UTRA-Thres * 2 + 49 UTRA-Thres is actual Ec/NO value in dB For signalling test cases UTRA-Thres + 115 utra-RSCP Comment UTRA-Thres + 115 UTRA-Thres is actual RSCP value in dBm UTRA-Thres is actual RSCP value in dBm } } } } hysteresis timeToTrigger 3 (1.6-8: ReportConfigInterRAT-B2-UTRA(EUTRA-Thres.Release 12 264 - 3GPP TS 36.5 dB) ms0 } } maxReportCells 6 reportInterval reportAmount ms1024 r1 In line with RAN4 requirement } Condition UTRA-FDD UTRA-TDD Explanation UTRA FDD cell environment UTRA TDD cell environment 3GPP Condition UTRA-FDD UTRA-FDD UTRA-TDD .5 Information Element ReportConfigInterRAT-B2-UTRA(EUTRA-Thres.1 (2014-12) ReportConfigInterRAT-B2-UTRA Table 4. Release 12 - 265 3GPP TS 36.331 clause 6.6.6 Information Element RRC-TransactionIdentifier-UL ::= Value/remark 0.6.331 clause 6.8 Channel-bandwidth-dependent parameters The default values of parameters which depend on the channel bandwidth are defined in table 4.3 4.7-1: RRC-TransactionIdentifier-DL Derivation Path: 36.6.6-9: ReportConfigInterRAT-PERIODICAL Derivation Path: 36.8-1.7 Other information elements – RRC-TransactionIdentifier-DL Table 4.508 V12.331 clause 6.6 Information Element RRC-TransactionIdentifier-DL ::= – Value/remark Comment Condition Comment The same value as the value of RRCTransactionIdentifi er-DL in the downlink message initiating the procedure Condition 0.3.4.3.5 Information Element ReportConfigInterRAT-PERIODICAL ::= SEQUENCE { triggerType CHOICE { periodical SEQUENCE { purpose } } maxReportCells reportInterval reportAmount } Value/remark Comment Condition reportStrongestCells 1 ms1024 infinity 4.6.6.1 (2014-12) ReportConfigInterRAT-PERIODICAL Table 4. 3GPP .6...3.7-2: RRC-TransactionIdentifier-UL Derivation Path: 36.3 RRC-TransactionIdentifier-UL Table 4. 1 Security protected NAS messages In subclauses 4. 1) bw2 (mSRS. 5). 5). 4. (4. All the messages and information elements are listed in alphabetical order. which apply to all test cases unless otherwise specified. (4.7. Nb) = (40. Nb) = (20. (20. 5) Typical value in real network Selected based on typical maximum number of UEs.b.b.Release 12 266 3GPP TS 36. 3). 3GPP . 1).1 (2014-12) Table 4. the message shall be contained by SECURITY PROTECTED NAS MESSAGE unless contained by another NAS message.7. (40. Nb) = (60.7.4.6.2 and 4. 4. (4.8-1: Channel-bandwidth-dependent parameters Information Element PrachFrequencyOff set nRB-CQI PuschHoppingOffset sr-PUCCHResourceInde x srsBandwidthCo nfig Channel bandwidth 5 MHz 10 MHz 2 4 1. 1) bw2 (mSRS. 2). Nb) = (80. (4. all the NAS messages are described in the plain NAS message format.7 Default NAS message and information element contents This clause contains the default values of common NAS messages and information elements. The default contents of SECURITY PROTECTED NAS MESSAGE message are defined in table 4. (4. 2). (4. 1). 1) bw2 (mSRS.b.3 in this document.7. (20. 2). 5). When a NAS message is security protected. Typical value in real network Selected in accordance with pucchResourceSize. 1). (4.508 V12. (4. 1).1-1. 1).b.4 MHz 0 3 MHz 1 0 0 2 0 2 FFS FFS Comment 15 MHz 6 20MHz 8 4 6 8 4 8 12 16 FFS 20 41 62 84 FFS bw3 (mSRS. (20. Release 12 267 3GPP TS 36.508 V12.4. unless specified otherwise in other clauses of the present specification or in a test case. 3GPP .301 clause 8.2. the condition CIPHERED applies.23 Information Element Protocol discriminator Security header type Value/remark EMM '0001'B '0010'B '0011'B '0100'B Message authentication code Sequence number NAS message Condition UNCIPHERED CIPHERED UNCIPHERED-NEW CIPHERED-NEW SENT-BY-SS SENT-BY-UE The calculated value of MAC-I for this message.1 (2014-12) Table 4. for every DL NAS message sent within SECURITY PROTECTED NAS MESSAGE message. The internal counter of the SS Any allowed value Comment Condition Integrity protected UNCIPHER ED CIPHERED Integrity protected and ciphered Integrity protected with new EPS security context Integrity protected and ciphered with new EPS security context The value of MAC-I is calculated by SS using Sequence number sent by UE.1-1: SECURITY PROTECTED NAS MESSAGE Derivation Path: 24.7. UNCIPHER ED-NEW CIPHEREDNEW SENT-BYSS SENT-BYUE SENT-BYSS SENT-BYUE Set according to specific message content Explanation This condition applies to unciphered NAS message exchange This condition applies to ciphered NAS message exchange This condition applies to unciphered NAS message exchange with new EPS security context This condition applies to ciphered NAS message exchange with new EPS security context Use for the message sent from SS to UE Use for the message sent from UE to SS When a valid NAS security context exists. The same value as the XMAC-I value calculated by SS. 1 (2014-12) .Release 12 268 4.7.7.2-1: ATTACH ACCEPT 3GPP 3GPP TS 36.2 Contents of EMM messages - ATTACH ACCEPT This message is sent by the SS to the UE. Table 4.4.508 V12. For NAS test cases.2.2-1.4.2-1.2-2 in this document M-TMSI See table 4.508 V12.2.1 Information Element Protocol discriminator Security header type 269 Value/remark EMM '0000'B Attach accept message identity EPS attach result '0100 0010'B '0001'B '0010'B Spare half octet T3412 value Timer value Unit '0000'B TAI list Length of tracking area identity list contents Partial tracking area identity list 1 Number of elements Type of list '0 0000'B '111'B EPS_only combined_E PS_IMSI value indicates that the timer is deactivated.2-2 in this document MME Code See table 4. see table 6. For NAS test cases. see table 6.3. not security protected Attach accept EPS only combined EPS/IMSI attach '0 0000'B '00'B MNC Location area identification Location area identification MCC Condition 6 octets See table 4.3.3.3. EPS_only combined_E PS_IMSI .2-1.2-1.2.2-2 in this document MNC See table 4.2.2-2 in this document TAC 1 See table 4.2-2 in this document GUTI Length of EPS mobile identity contents Type of identity Odd/even indication Comment '0000 0110'B MCC ESM message container 3GPP TS 36. For NAS test cases. with nonconsecutive TAC values For NAS test cases.4.2-2 in this document MME Group ID See table 4.301 clause 8.3.2-1.2.4. 1 element list of TACs belonging to one PLMN.4. see table 6. See table 4.2. see table 6.2-2 in this document MNC Plain NAS message. For NAS test cases.4.2.2-1.3.3.2-2 in this document ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to activate the default bearer '0000 1011'B '110'B '0'B MCC See table 4.4.2.2.1 (2014-12) Not present MCC of the EUTRA cell from which this message is sent MCC of the EUTRA cell 3GPP 11 octets GUTI even number of identity digits and also when the GUTI is used For NAS test cases. For NAS test cases. see table 6. see table 6. see table 6.Release 12 Derivation Path: 24.4.3. For NAS test cases.4.4. see table 6.2-1.2-1. 4.Release 12 270 from which this message is sent 1 Not present LAC MS identity MS identity Length of mobile identity contents Type of identity '0000 0101'B '100'B Odd/even indication '0'B TMSI EMM cause T3402 value T3423 value Equivalent PLMNs Emergency number list EPS network feature support TMSI-1 Not present Not present Not present Not present Not present '0000 0001'B EPS network feature support '0000 0011'B Additional update result Additional update result Not present ‘10’ B T3412 extended value Not present Condition combined_EPS_IMSI additional_update_result_SMS - 5 octets TMSI/P-TMSI/MTMSI even number of identity digits and also when the TMSI/P-TMSI or TMGI and optional MBMS Session Identity is used IMS voice over PS session in S1 mode supported IMS voice over PS session in S1 mode supported.301 clause 8. This condition applies if the UE is configured to initiate combined EPS/IMSI attach or if explicitly specified. If the UE requested "SMS only" in the Additional update type IE and combined_EPS_IMSI condition applies EPS_only NOTE: 3GPP TS 36.7.2. Table 4.2-2: ATTACH COMPLETE Derivation Path: 24. ATTACH COMPLETE This message is sent by the UE to the SS.508 V12.2 Information Element Protocol discriminator Security header type Attach complete message identity ESM message container Value/remark EMM '0000'B '0100 0011'B ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message 3GPP Comment Plain NAS message. not security protected Attach complete Condition .1 (2014-12) This message is always sent within SECURITY PROTECTED NAS MESSAGE message. emergency bearer services in S1 mode supported “SMS only” EPS_only combined_E PS_IMSI Rel-9 additional_u pdate_result _SMS Rel-10 Explanation This condition applies if the UE is configured to initiate EPS attach or if explicitly specified. 7.3 Information Element Protocol discriminator Security header type Attach reject message identity EMM cause ESM message container NOTE: Value/remark EMM '0000'B '0100 0100'B Set according to specific message content.2. it is sent within SECURITY PROTECTED NAS MESSAGE message.508 V12.1 (2014-12) This message is always sent within SECURITY PROTECTED NAS MESSAGE message.2-3: ATTACH REJECT Derivation Path: 24.Release 12 NOTE: - 271 3GPP TS 36. Otherwise this message is sent without integrity protection. Set according to specific message content.301 clause 8. 3GPP .4. Table 4. not security protected Attach reject If this message includes the EMM cause set to #25. Comment Condition Plain NAS message. ATTACH REJECT This message is sent by the SS to the UE. 1 (2014-12) ATTACH REQUEST This message is sent by the UE to the SS.7.508 V12.2.301 clause 8. 3GPP .2-4: ATTACH REQUEST Derivation Path: 24. This message is sent integrity protected when a valid security context exists and without integrity protection otherwise. Table 4. not security protected Attach request EPS attach combined EPS/IMSI attach EPS_only combined_E PS_IMSI EPS_only combined_E PS_IMSI Explanation See the definition below table 4.2-1.4 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Attach request message identity EPS attach type '0100 0001'B '0001'B '0010'B NAS key set identifier Old GUTI or IMSI UE network capability ESM message container Any allowed value Any allowed value Any allowed value PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present Not present or any allowed value Not present or any allowed value Old P-TMSI signature Additional GUTI Last visited registered TAI DRX parameter MS network capability Old location area identification TMSI status Mobile station classmark 2 Mobile station classmark 3 Supported Codecs Additional update type Additional update type Old GUTI type Condition EPS_only combined_EPS_IMSI NOTE: Comment Condition Plain NAS message. See the definition below table 4.7.4.2-1.7.Release 12 272 - 3GPP TS 36. 6 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Authentication reject message type '0101 0100'B NOTE: This message is sent without integrity protection. Table 4.1 (2014-12) AUTHENTICATION FAILURE This message is sent by the UE to the SS.7.5. 3GPP Comment Plain NAS message. not security protected Authentication reject Condition . AUTHENTICATION REJECT This message is sent by the SS to the UE.2-5: AUTHENTICATION FAILURE Derivation Path: 24.5 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Authentication failure message type '0101 1100'B EMM cause Authentication failure parameter '0001 0100'B Not present NOTE: - Comment Condition Plain NAS message.2 The security protection of this message is the same as the previous AUTHENTICATION REQUEST message.2.301 [28] subclause 8.2-6: AUTHENTICATION REJECT Derivation Path: 24. not security protected Authentication failure Mac failure See TS 24.2.Release 12 - 273 3GPP TS 36.301 clause 8.2. Table 4.7.4.301 clause 8.508 V12. 508 V12.301 [28] subclause 9.2-7: AUTHENTICATION REQUEST Derivation Path: 24.7 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Authentication request message type '0101 0010'B NAS key set identifierASME NAS key set identifier An arbitrarily selected value between '000'B and '110'B.7.Release 12 - 274 3GPP TS 36.9.4 NOTE: Comment Condition Plain NAS message.2-8: AUTHENTICATION RESPONSE Derivation Path: 24.2 Within a test execution this message is sent without integrity protection before NAS security mode control procedure has been successfully completed. Table 4. and sent integrity protected and ciphered within SECURITY PROTECTED NAS MESSAGE message after NAS security mode control procedure has been successfully completed.301 [28] subclause 9.9. different from the valid NAS key set identifier of the UE if such a value exists.2. AUTHENTICATION RESPONSE This message is sent by the UE to the SS.1 (2014-12) AUTHENTICATION REQUEST This message is sent by the SS to the UE. Table 4. SS does not maintain information for NAS security mode control procedure after a TC is completed.3. not security protected Authentication request native security context (for KSIASME) '0000'B An arbitrarily selected 128 bits value See TS 24. the AUTHENTICATION RESPONSE message may be sent integrity protected when a valid security context exists and without integrity protection otherwise. not security protected Authentication response When sent in response to an AUTHENTICATION REQUEST message which is not integrity protected and not ciphered. '0'B TSC Spare half octet Authentication parameter RAND (EPS challenge) Authentication parameter AUTN (EPS challenge) NOTE: - Comment Condition Plain NAS message. 3GPP .301 clause 8.301 clause 8.4.7.3.8 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Authentication response message type '0101 0011'B Authentication response parameter See TS 24.2. 301 clause 8.9 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B CS service notification message identity '01100100'B Paging identity CLI SS Code LCS indicator LCS client identity ‘1’B Not present Not present Not present Not present NOTE: - Comment Condition Plain NAS message.2-10: DETACH ACCEPT Derivation Path: 24.301 clause 8.1 (2014-12) CS SERVICE NOTIFICATION This message is sent by the SS to the UE. not security protected CS Service notification TMSI This message is always sent within SECURITY PROTECTED NAS MESSAGE message. DETACH ACCEPT (UE originating detach) This message is sent by the SS to the UE.2 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Detach accept message identity '0100 0110'B NOTE: Comment Condition Plain NAS message.2-9: DETACH ACCEPT Derivation Path: 24.4.301 clause 8. Table 4. Table 4.2-8A: CS SERVICE NOTIFICATION Derivation Path: 24. Table 4.2.7. DETACH ACCEPT (UE terminated detach) This message is sent by the UE to the SS. 3GPP .10.1 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Detach accept message identity '0100 0110'B NOTE: - Comment Condition Plain NAS message.7.2.10.7.2. not security protected Detach accept This message is sent using the same security protection as in the previous DETACH REQUEST message received from the UE. not security protected Detach accept This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MESSAGE message after NAS security mode control procedure has been successfully completed.508 V12.Release 12 - 275 3GPP TS 36. Comment Plain NAS message.2-12: DETACH REQUEST Derivation Path: 24.2-11: DETACH REQUEST Derivation Path: 24. otherwise set to the IMSI of the UE.301 clause 8.7.1 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Detach request message identity Detach type Type of detach '0100 0101'B Switch off NAS key set identifier NAS key set identifier '1'B '001'B ‘011’B Condition Plain NAS message. Table 4.2-1. This message is sent with integrity protection before SS has started the ciphering and integrity and ciphered protected after SS has started the ciphering.7.2.Release 12 276 - 3GPP TS 36.2 Information Element Protocol discriminator Security header type Detach request message identity Detach type Spare half octet EMM cause NOTE: Value/remark EMM '0000'B '0100 0101'B Set according to specific message content.1 (2014-12) DETACH REQUEST (UE originating detach) This message is sent by the UE to the SS. See the definition below table 4.4. not security protected Detach request This message is always sent within SECURITY PROTECTED NAS MESSAGE message.11.11.7.2-1.508 V12. Table 4. set to the GUTI. TSC GUTI or IMSI Condition EPS_only Combined_EPS_IMSI NOTE: Comment Explanation See the definition below table 4. 3GPP Condition .2. not security protected Detach request EPS detach combined EPS/IMSI detach switch off EPS_only Combined_ EPS_IMSI The valid NAS key set identifier.301 clause 8. Any Value If the UE has a valid GUTI.7. '0000'B Set according to specific message content. - DETACH REQUEST (UE terminated detach) This message is sent by the SS to the UE. 7.7.12 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Downlink NAS transport message identity '0110 0010'B NAS message container Set according to specific message content NOTE: Comment Condition Plain NAS message. not security protected EMM status This message is always sent within SECURITY PROTECTED NAS MESSAGE message.4.2-13: EMM INFORMATION Derivation Path: 24. Set according to specific message content. - EMM INFORMATION This message is sent by the SS to the UE.2. not security protected EMM information This message is always sent within SECURITY PROTECTED NAS MESSAGE message.1 (2014-12) DOWNLINK NAS TRANSPORT This message is sent by the SS to the UE.301 clause 8. Set according to specific message content.Release 12 277 - 3GPP TS 36.2-12A: DOWNLINK NAS TRANSPORT Derivation Path: 24.508 V12.2.13 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B EMM information message identity Full name for network '0110 0001'B Set according to specific message content.14 Information Element Protocol discriminator Security header type EMM status message identity EMM cause NOTE: Value/remark EMM '0000'B '0110 0000'B Set according to specific message content. Comment Plain NAS message.2-14: EMM STATUS Derivation Path: 24. Set according to specific message content. Table 4. Table 4. not security protected Downlink NAS transport This message is always sent within SECURITY PROTECTED NAS MESSAGE message.2. EMM STATUS This message is sent by the UE or by the SS.301 clause 8. 3GPP Condition . Table 4.7.301 clause 8. Short name for network Local time zone Universal time and local time zone Network daylight saving time NOTE: - Comment Condition Plain NAS message. Set according to specific message content. set to the M-TMSI.508 V12. '0'B TSC M-TMSI If the UE has a valid MTMSI.301 clause 8. not security protected Extended service request mobile terminating CS fallback or 1xCS fallback native security context (for KSIASME) CS fallback accepted by the UE This message is always sent within SECURITY PROTECTED NAS MESSAGE message.Release 12 278 - 3GPP TS 36.2. TAI list NOTE: Comment Plain NAS message.2-14A: EXTENDED SERVICE REQUEST Derivation Path: 24.2-15: GUTI REALLOCATION COMMAND Derivation Path: 24.2. 3GPP Condition . Table 4. otherwise set to the IMSI of the UE.7. Table 4. Set according to specific message content. ’001’B CSFB response NOTE: - Comment Condition Plain NAS message.1 (2014-12) EXTENDED SERVICE REQUEST This message is sent by the UE to the SS.16 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B GUTI reallocation command message identity '0101 0000'B GUTI Set according to specific message content.7.301 clause 8. GUTI REALLOCATION COMMAND This message is sent by the SS to the UE.4. not security protected GUTI reallocation command This message is always sent within SECURITY PROTECTED NAS MESSAGE message.15 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Extended service request message identity '0100 1100'B Service type '0001'B NAS key set identifier NAS key set identifier The valid NAS key set identifier. Release 12 - 279 3GPP TS 36.2.7.1 (2014-12) GUTI REALLOCATION COMPLETE This message is sent by the UE to the SS.2-16: GUTI REALLOCATION COMPLETE Derivation Path: 24. not security protected Identity request IMSI This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MESSAGE message after NAS security mode control procedure has been successfully completed.18 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Identity request message identity Identity type Spare half octet '0101 0101'B '0001'B '0000'B NOTE: - Comment Condition Plain NAS message.7.2-17: IDENTITY REQUEST Derivation Path: 24. Table 4. not security protected GUTI reallocation complete This message is always sent within SECURITY PROTECTED NAS MESSAGE message. IDENTITY REQUEST This message is sent by the SS to the UE.508 V12.17 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B GUTI reallocation complete message identity '0101 0001'B NOTE: - Comment Condition Plain NAS message.301 clause 8. Table 4.2.2-18: IDENTITY RESPONSE Derivation Path: 24. IDENTITY RESPONSE This message is sent by the UE to the SS.301 clause 8. Table 4. 3GPP .7.2.4.19 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Identity response message Mobile identity '0101 0110'B IMSI of the UE NOTE: Comment Condition Plain NAS message.301 clause 8. not security protected Identity response This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MESSAGE message after NAS security mode control procedure has been successfully completed. 4.2-19: SECURITY MODE COMMAND Derivation Path: 24. Table 4.1 (2014-12) SECURITY MODE COMMAND This message is sent by the SS to the UE. not security protected Security mode command Set according to PIXIT parameter for default ciphering algorithm eea0 NAS key set identifier NAS key set identifier IMEISV request Replayed nonceUE NonceMME Comment . 3GPP For RF For SIG '0000'B Set according to the received UE security capabilities Not present Not present Not present Condition For SIG For RF Condition Plain NAS message.508 V12.20 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Security mode command message identity '0101 1101'B Selected NAS security algorithms Type of integrity protection algorithm Set according to PIXIT parameter for default integrity protection algorithm 0(reserved or eia0) eia1 eia2 Type of ciphering algorithm The valid NAS key set identifier.2. '0'B TSC Spare half octet Replayed UE security capabilities NOTE: For SIG This IE is set to one of the algorithms supported by the UE as indicated in the IE "UE network capability" in the ATTACH REQUEST message.301 clause 8.7.Release 12 - 280 3GPP TS 36. For RF native security context (for KSIASME) Explanation Used for signalling test cases Used for RF/RRM test cases This message is always sent integrity protected with new EPS security context. 2.2-20: SECURITY MODE COMPLETE Derivation Path: 24.2. SERVICE REJECT This message is sent by the SS to the UE. SECURITY MODE REJECT This message is sent by the UE to the SS.22 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Security mode reject message identity '0101 1111'B EMM cause The value is set according to specific message content.7. Not present Comment Condition Plain NAS message. Table 4.21 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Security mode complete message identity '0101 1110'B IMEISV Not present NOTE: - Comment Condition Plain NAS message.508 V12. Otherwise this message is sent without integrity protection.301 clause 8. not security protected Security mode reject This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MESSAGE message after NAS security mode control procedure has been successfully completed. not security protected Security mode complete This message is always sent within SECURITY PROTECTED NAS MESSAGE message with new EPS security context. not security protected Service reject If this message includes the EMM cause set to #25.4.7.Release 12 - 281 3GPP TS 36. it is sent within SECURITY PROTECTED NAS MESSAGE message. Table 4.24 Information Element Protocol discriminator Security header type Service reject message identity EMM cause T3442 value NOTE: Value/remark EMM '0000'B '0100 1110'B Set according to specific message content.301 clause 8.2. NOTE: - Comment Condition Plain NAS message.7.301 clause 8.1 (2014-12) SECURITY MODE COMPLETE This message is sent by the UE to the SS.2-22: SERVICE REJECT Derivation Path: 24. Table 4.2-21: SECURITY MODE REJECT Derivation Path: 24. 3GPP . Table 4.25 Information Element Protocol discriminator Security header type KSI and sequence number Sequence number (short) KSI Message authentication code (short) Value/remark EMM '1100'B The 5 least significant bits of the NAS COUNT value applicable when this message is sent for sequence number.301 clause 8.508 V12.Release 12 - 282 3GPP TS 36. The effective KSI value.7.2.2-23: SERVICE REQUEST Derivation Path: 24.1 (2014-12) SERVICE REQUEST This message is sent by the UE to the SS.4. The 2 least significant octets of the resulting message authentication code 3GPP Comment Security header for the SERVICE REQUEST message Condition . 4.2-24: TRACKING AREA UPDATE ACCEPT 3GPP .1 (2014-12) TRACKING AREA UPDATE ACCEPT This message is sent by the SS to the UE.Release 12 - 283 3GPP TS 36.7.508 V12. Table 4. see table 6.2-2 in this document MNC See table 4.2.3. see table 6. see table 6.2.2.4. For NAS test cases.3.301 clause 8. For NAS test cases.3. see table 6. not security protected Tracking area update accept TA updated combined TA/LA updated TA_only combined_T A_LA Periodic value indicates that the timer is deactivated.2-2 in this document MME Group ID See table 4.2.2-2 in this document TAI list Length of tracking area identity list contents Partial tracking area identity list 1 Number of elements Type of list Condition Plain NAS message.3.4.2-1. For NAS test cases.2.508 V12.26 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Tracking area update accept message identity '0100 1001'B EPS update result '0000'B '0001'B Spare half octet T3412 value T3412 value Timer value Unit '0000'B Not present GUTI Length of EPS mobile identity contents Type of identity Odd/even indication '0 0000'B '111'B '0000 1011'B '110'B '0'B MCC See table 4.2.2-2 in this document Location area identification Location area identification MCC Comment '0000 0110'B MCC EPS bearer context status 3GPP TS 36. See table 4.2-2 in this document M-TMSI See table 4.2-1. see table 6.1 (2014-12) The same value as the value set in TRACKING AREA UPDATE REQUEST message Not present MCC of the EUTRA cell from which this message is sent 3GPP TA_only combined_T A_LA . with nonconsecutive TAC values For NAS test cases.3.4. 11 octets GUTI even number of identity digits and also when the GUTI is used For NAS test cases.2-1. For NAS test cases.2.2-1. For NAS test cases. see table 6. 6 octets '0 0000'B '00'B 1 element list of TACs belonging to one PLMN.2-2 in this document TAC 1 See table 4. see table 6.2-2 in this document MME Code See table 4.4.2-1.Release 12 284 Derivation Path: 24.2-1.3.3.2.2.2-2 in this document MNC See table 4.2-1.4. see table 6.4.2-1.4.4. For NAS test cases.3.4. If the UE requested "SMS only" in the Additional update type IE and combined_TA_LA.301 clause 8.2-25: TRACKING AREA UPDATE COMPLETE Derivation Path: 24. This condition applies if in the last TRACKING AREA UPDATE REQUEST sent prior to this message.4. This message is always sent within SECURITY PROTECTED NAS MESSAGE message. TRACKING AREA UPDATE COMPLETE This message is sent by the UE to the SS. Table 4.Release 12 285 MNC MCC of the EUTRA cell from which this message is sent 1 Not present LAC MS identity MS identity Length of mobile identity contents Type of identity '0000 0101'B '100'B Odd/even indication '0'B TMSI EMM cause T3402 value T3423 value Equivalent PLMNs Emergency number list EPS network feature support TMSI-1 Not present Not present Not present Not present Not present 0000 0001'B Additional update result Additional update result Not present ‘10’ B T3412 extended value Not present Condition TA_only combined_TA_LA Periodic TAU_additional_update_result_SMS NOTE: - 3GPP TS 36. not security protected Tracking area update complete This message is always sent within SECURITY PROTECTED NAS MESSAGE message. This condition applies if the UE is configured to initiate combined EPS/IMSI attach or if explicitly specified.508 V12.27 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Tracking area update complete message identity '0100 1010'B NOTE: Comment Plain NAS message.2.1 (2014-12) 5 octets TMSI/P-TMSI/MTMSI even number of identity digits and also when the TMSI/P-TMSI or TMGI and optional MBMS Session Identity is used TA_only combined_T A_LA IMS voice over PS session in S1 mode supported “SMS only” TAU_additio nal_update_ result_SMS Rel-10 Explanation This condition applies if the UE is configured to initiate EPS attach or if explicitly specified.7. 3GPP Condition . the EPS update type Value = '011'B (periodic updating). NOTE: Comment Condition Plain NAS message.Release 12 - 286 3GPP TS 36.2. it is sent within SECURITY PROTECTED NAS MESSAGE message.4. not security protected Tracking area update reject If this message includes the EMM cause set to #25.2-26: TRACKING AREA UPDATE REJECT Derivation Path: 24. Otherwise this message is sent without integrity protection.508 V12. Table 4.28 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Tracking area update reject message identity '0100 1011'B EMM cause Set according to specific message content.7.1 (2014-12) TRACKING AREA UPDATE REJECT This message is sent by the SS to the UE. 3GPP .301 clause 8. 4. not security protected Tracking area update request TA updating Combined TA/LA updating No bearer establishment requested '0'B NAS key set identifier NAS key set identifier Comment TA_only combined_T A_LA .7.29 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Tracking area update request message identity '0100 1000'B EPS update type EPS update type Value "Active" flag '000'B '001'B TSC Old GUTI Non-current native NAS key set identifier GPRS ciphering key sequence number Old P-TMSI signature Additional GUTI NonceUE UE network capability Last visited registered TAI DRX parameter UE radio capability information update needed EPS bearer context status MS network capability Old location area identification TMSI status Mobile station classmark 2 Mobile station classmark 3 Supported Codecs Additional update type Additional update type Old GUTI type The valid NAS key set identifier of the UE '0'B Explanation 3GPP TA_only combined_T A_LA native security context (for KSIASME) Any allowed value Not present Not present Not present Not present Not present Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or (octet 3 = '00100000'B and octet 4 = '00000000'B) Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present Not present or any allowed value Not present or any allowed value Condition Condition Plain NAS message.301 clause 8.2-27: TRACKING AREA UPDATE REQUEST Derivation Path: 24.508 V12.2.Release 12 - 287 3GPP TS 36.1 (2014-12) TRACKING AREA UPDATE REQUEST This message is sent by the UE to the SS. Table 4. 508 V12. Table 4.7.3-1: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT Derivation Path: 24.Release 12 288 TA_only combined_TA_LA NOTE: - 3GPP TS 36.301 clause 8.7.3.3 Contents of ESM messages - ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT This message is sent by the UE to the SS. Table 4. not security protected Uplink NAS transport This message is always sent within SECURITY PROTECTED NAS MESSAGE message.301 clause 8.1 (2014-12) See the definition below table 4. UPLINK NAS TRANSPORT This message is sent by the UE to the SS. This message is always sent within SECURITY PROTECTED NAS MESSAGE message.2-24.4.1 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM The same value as the value set in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message '0000 0000'B Activate dedicated EPS bearer context accept message identity '1100 0110'B Protocol configuration options Not present or any allowed value NOTE: Comment No procedure transaction identity assigned Activate dedicated EPS bearer context accept This message is always sent within SECURITY PROTECTED NAS MESSAGE message.2.2-27A: UPLINK NAS TRANSPORT Derivation Path: 24.2-24.7. 3GPP Condition .30 Information Element Protocol discriminator Security header type Value/remark EMM '0000'B Uplink NAS transport message identity '0100 0011'B NAS message container Set according to specific message content NOTE: Comment Condition Plain NAS message.7. 4.7. See the definition below table 4. 7.4.3.508 V12.3-2: ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT Derivation Path: 24.Release 12 - 289 3GPP TS 36.301 clause 8. Table 4.2 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM The same value as the value set in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. 3GPP Condition . Not present Protocol configuration options NOTE: Comment No procedure transaction identity assigned Activate dedicated EPS bearer context reject This message is always sent within SECURITY PROTECTED NAS MESSAGE message.1 (2014-12) ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT This message is sent by UE to the SS. '0000 0000'B Activate dedicated EPS bearer context reject message identity '1100 0111'B ESM cause The value is set according to specific message content. 6.7.6.2-1 See Reference dedicated EPS bearer context #1 in table 6.2-1 Not present '0000 0000'B See Reference dedicated EPS bearer context #1 in table 6.508 V12.4. Table 4.3 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Activate dedicated EPS bearer context request message identity Linked EPS bearer identity Spare half octet EPS QoS TFT Transaction identifier Negotiated QoS Negotiated LLC SAPI Radio priority Packet flow Identifier Protocol configuration options Condition NETWORK-INITIATED UE-INITIATED NOTE: Value/remark ESM Arbitrarily selected value between '0101'B and '1111'B.2-1 See Reference dedicated EPS bearer context #1 in table 6.6. 3GPP Condition pc_GERAN . '0000 0000'B The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST message or BEARER RESOURCE ALLOCATION REQUEST message '1100 0101'B The EPS bearer identity of the associated default bearer '0000'B See Reference dedicated EPS bearer context #1 in table 6.3-3: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST Derivation Path: 24.1 (2014-12) ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST This message is sent by the SS to the UE.2-1 Not present Distinct value between 0 and 127 calculated on basis of the EPS bearer identity.3. See Reference dedicated EPS bearer context #1 in table 6.6.Release 12 290 - 3GPP TS 36.301 clause 8.2-1 See Reference dedicated EPS bearer context #1 in table 6.6.2-1 Comment No procedure transaction identity assigned NETWORKINITIATED UEINITIATED Activate dedicated EPS bearer context request pc_UTRAN AND/OR pc_GERAN Best Effort Explanation Network initiated ESM procedures UE initiated ESM procedures This message is always sent within SECURITY PROTECTED NAS MESSAGE message.6. 7. Table 4.301 clause 8. Table 4.3. 3GPP Condition .7.3-5: ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT Derivation Path: 24.4.3-4: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT Derivation Path: 24. ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT This message is sent by UE to the SS.508 V12.3.5 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.4 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message '0000 0000'B Activate default EPS bearer context accept message identity '1100 0010'B Protocol configuration options Not present or any allowed value NOTE: - Comment Condition No procedure transaction identity assigned Activate default EPS bearer context accept This message is always sent within SECURITY PROTECTED NAS MESSAGE message.301 clause 8. '0000 0000'B Activate default EPS bearer context reject message identity '1100 0011'B ESM cause The value is set according to specific message content. Not present Protocol configuration options NOTE: Comment No procedure transaction identity assigned Activate default EPS bearer context reject This message is always sent within SECURITY PROTECTED NAS MESSAGE message.Release 12 - 291 3GPP TS 36.1 (2014-12) ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT This message is sent by the UE to the SS. 3-6: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST 3GPP . Table 4.508 V12.1 (2014-12) ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST This message is sent by the SS to the UE.4.Release 12 - 292 3GPP TS 36.7. 3gppnetwork.1 (2014-12) NOT IMS_PDN_C onnEstab IMS_PDN_C onnEstab NOT IMS_PDN_C onnEstab AND NOT APN_Provid ed NOT IMS_PDN_C onnEstab AND APN_Provid ed IMS_PDN_C onnEstab AND NOT APN_Provid ed IMS_PDN_C onnEstab AND APN_Provid ed IPv4 5 octets ‘001’B IPv4 address 0.508 V12. '1100 0001'B APN as provided in ESM INFORMATION RESPONSE or PDN CONNECTIVITY REQUEST Access point name IMS.mcc<MCC>.6. apn.3gppnetwork.org.Release 12 Derivation Path: 24. Use APN Network Identifier provided in ESM INFORMATION RESPONSE or PDN CONNECTIVITY REQUEST message and the APN Operator Identifier mnc<MNC>.3.mcc <MCC>.0.1-1 See Reference default EPS bearer context #2 in table 6.epc. The same value as the value set in the latest PDN CONNECTIVITY REQUEST message sent prior to this message. The <MNC> and <MCC> are set to the same values as in IMSI.6.0 PDN address Length of PDN address contents PDN type value PDN address information 9 octets ‘010’B IPv6 interface identifier PDN address Length of PDN address contents 13 octets IPv4 The SS provides a valid IPv4 address DHCPv4 is to be used to allocate the IPv4 address NOT IPv4DHCP IPv4-DHCP IPv6 IPv6 The SS provides a valid IPv6 interface identifier IPv4v6 3GPP . PDN address Length of PDN address contents PDN type value PDN address information Comment Condition Activate default EPS bearer context request See Reference default EPS bearer context #1 in table 6.4.6 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Activate default EPS bearer context request message identity EPS QoS EPS QoS Access point name 293 Value/remark ESM An arbitrarily selected value between '0101'B and '1111'B.0.1-1 The SS defines a Default APN Access point name Access point name 3GPP TS 36.301 clause 8.mnc<MNC>.org The <MNC> and <MCC> are set to the same values as in IMSI. 1-1 Not present Container ID 2 IPv6 address Container ID n IPv4 address ‘0003’H Length of container ID n contents Container ID n contents Container ID n+1 IPv6 address ‘000D’H Length of container ID n+1 contents Container ID n+1 contents IPv4 address 3GPP NOT IPv4DHCP IPv4-DHCP pc_UTRAN AND/OR pc_GERAN Best Effort pc_GERAN P-CSCF IPv6 Length value determined by the TTCN implementation P-CSCF IPv6 Address ‘000C’H Length of container ID 2 contents Container ID 2 contents IPv4v6 The SS provides a valid IPv6 interface identifier The SS provides a valid IPv4 address DHCPv4 is to be used to allocate the IPv4 address See Reference default EPS bearer context #1 in table 6.6.508 V12.0.1-1 Not present '0000 0000'B See Reference default EPS bearer context #1 in table 6.4.0 Transaction identifier Negotiated QoS Negotiated LLC SAPI Radio priority Packet flow Identifier APN-AMBR ESM cause Protocol configuration options Configuration protocol Container ID 1 Not present Distinct value between 0 and 127 calculated on basis of the EPS bearer identity.1-1 ‘0001’H Length of container ID 1 contents Container ID 1 contents 3GPP TS 36.6.1 (2014-12) P-CSCF IPv4 Length value determined by the TTCN implementation P-CSCF IPv4 Address n assigned to next available number Length value determined by the TTCN implementation DNS IPv6 Address n assigned to next available number Length value determined by the TTCN implementation DNS IPv4 Address DNS IPv6 DNS IPv4 .6.6.6.0.1-1 See Reference default EPS bearer context #1 in table 6.1-1 See Reference default EPS bearer context #1 in table 6.Release 12 294 PDN type value PDN address information (Octets 4 to 11) ‘011’B IPv6 interface identifier PDN address information (Octets 12 to 15) IPv4 address 0. See Reference default EPS bearer context #1 in table 6. are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used. PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE.3-14) If this message refers to establishment of connectivity to the IMS PDN (only applicable if the UE supports IMS according to TS 36. Note 2: If both messages.523-2 A.508 V12. DNS IPv4 APN_Provided IMS_PDN_ConnEstab NOTE: Note: If both messages.4. are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used.4. the Protocol configuration options and the additional parameter list was included with a “DNS IPv6 Address Request”.523-2 A.Release 12 295 Condition IPv4 IPv6 IPv4v6 IPv4-DHCP 3GPP TS 36. If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message. the PDN type = '001'B If in the last PDN CONNECTIVITY REQUEST sent prior to this message. 3GPP . Note 2: If both messages. are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used. length of contents = 0). are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used. the Protocol configuration options and the additional parameter list was included with a “DNS IPv4 Address Request”.4. Note 2: If both messages. If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message. the PDN type = '011'B If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message.4-1/25). the IE Protocol configuration options contains a configuration protocol option = '000B00H' ("IPv4 address allocation via DHCPv4".7. the PDN type = '010'B If in the last PDN CONNECTIVITY REQUEST sent prior to this message. the Protocol configuration options and the additional parameter list was included with a “P-CSCF IPv6 Address Request” P-CSCF IPv6 Note 1: This condition is only applicable for UEs with IMS support (TS 36.4-1/25). PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE. PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE. This message is always sent within SECURITY PROTECTED NAS MESSAGE message. DNS IPv6 Note: If both messages. Note 1: This condition is used in conjunction with IPv4 or IPv4v6 as indicated in the "PDN address row" just above. are received and contain a Protocol configuration options IE then the IE from the message which is received later shall be used. If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message. PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE.523-2 A. PDN CONNECTIVITY REQUEST and ESM INFORMATION RESPONSE. If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message.4.1 (2014-12) Explanation If in the last PDN CONNECTIVITY REQUEST sent prior to this message. If in the last PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE sent prior to this message an Access Point Name was included NOTE: APN_Provided is equivalent to pc_Provide_IMS_APN for establishment of the first PDN connectivity during initial registration and if the first PDN is IMS (see table 4.4-1/25). the Protocol configuration options and the additional parameter list was included with a “P-CSCF IPv4 Address Request” P-CSCF IPv4 Note 1: This condition is only applicable for UEs with IMS support (TS 36. 7.301 clause 8.3. '0000'B Spare half octet Traffic flow aggregate Number of packet filters E bit TFT operation code Packet filter list Parameters list Required traffic flow QoS Protocol configuration options NOTE: Greater than 0 and less than or equal to 16 Any allowed value '001'B Any allowed value Not present or any allowed value Any allowed value Not present or any allowed value Comment No EPS bearer identity assigned Bearer resource allocation request Create new TFT This message is always sent within SECURITY PROTECTED NAS MESSAGE message.508 V12.Release 12 - 296 3GPP TS 36. '1101 0101'B Comment Condition No EPS bearer identity assigned Bearer resource allocation reject Set according to specific message content.3.7. BEARER RESOURCE ALLOCATION REQUEST This message is sent by the UE to the SS.8 Information Element Protocol discriminator EPS bearer identity Value/remark ESM '0000'B Procedure transaction identity Bearer resource allocation request message identity Any value from 1 to 254 '1101 0100'B Linked EPS bearer identity The EPS bearer identity of the associated default bearer.3-6A: BEARER RESOURCE ALLOCATION REJECT Derivation Path: 24.7 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Bearer resource allocation reject message identity ESM cause Protocol configuration options NOTE: - Value/remark ESM '0000'B The value indicated in BEARER RESOURCE ALLOCATION REQUEST message. 3GPP Condition .1 (2014-12) BEARER RESOURCE ALLOCATION REJECT This message is sent by the SS to the UE.301 clause 8.4.3-6B: BEARER RESOURCE ALLOCATION REQUEST Derivation Path: 24. Table 4. Table 4. Not present This message is always sent within SECURITY PROTECTED NAS MESSAGE message. '1101 0111'B Comment Condition No EPS bearer identity assigned Bearer resource modification reject Set according to specific message content. Not present This message is always sent within SECURITY PROTECTED NAS MESSAGE message.1 (2014-12) BEARER RESOURCE MODIFICATION REJECT This message is sent by the SS to the UE.Release 12 297 - 3GPP TS 36.508 V12. '0000'B Any allowed value Spare half octet Traffic flow aggregate Traffic flow aggregate Number of packet filters E bit TFT operation code Packet filter list Parameters list Required traffic flow QoS ESM cause Protocol configuration options Greater than 0 and less than or equal to 16 Any allowed value '101'B Any allowed value Not present or any allowed value Not present or any allowed value Not present '0010 0100'B Not present or any allowed value Condition Explanation 3GPP Comment Condition No EPS bearer identity assigned Bearer resource modification request RELEASEREQUESTE D Delete packet filters from existing TFT Regular deactivation RELEASEREQUESTE D .7. Table 4.3-8: BEARER RESOURCE MODIFICATION REQUEST Derivation Path: 24. Table 4.9 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Bearer resource modification reject message identity ESM cause Protocol configuration options NOTE: Value/remark ESM '0000'B The value indicated in BEARER RESOURCE MODIFICATION REQUEST message. - BEARER RESOURCE MODIFICATION REQUEST This message is sent by the UE to the SS.301 clause 8.3.301 clause 8.3.4.3-7: BEARER RESOURCE MODIFICATION REJECT Derivation Path: 24.7.10 Information Element Protocol discriminator EPS bearer identity Value/remark ESM '0000'B Procedure transaction identity Bearer resource modification request message identity Any value from 1 to 254 '1101 0110'B EPS bearer identity for packet filter The EPS bearer identity of the associated dedicated EPS bearer related with packet filter. Table 4. Table 4.301 clause 8.Release 12 298 RELEASE-REQUESTED NOTE: 3GPP TS 36. '0000 0000'B Deactivate EPS bearer context accept message identity '1100 1110'B Protocol configuration options Not present or any allowed value NOTE: - Comment Condition No procedure transaction identity assigned Deactivate EPS bearer context accept This message is always sent within SECURITY PROTECTED NAS MESSAGE message.7.9 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.3-12: DEACTIVATE EPS BEARER CONTEXT REQUEST Derivation Path: 24.1 (2014-12) UE requests the release of bearer resources. '0000 0000'B The same value as the value set in PDN DISCONNECT REQUEST message or BEARER RESOURCE MODIFICATION REQUEST message.3-9: (Void) Table 4. This message is always sent within SECURITY PROTECTED NAS MESSAGE message.3.301 clause 8.3-11: DEACTIVATE EPS BEARER CONTEXT ACCEPT Derivation Path: 24.7.508 V12.3-10: (Void) - DEACTIVATE EPS BEARER CONTEXT ACCEPT This message is sent by the UE to the SS. DEACTIVATE EPS BEARER CONTEXT REQUEST This message is sent by the SS to the UE.7.7. Table 4.3.10 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Deactivate EPS bearer context request message identity ESM cause Protocol configuration options Value/remark ESM Set according to specific message content. Not present 3GPP Comment No procedure transaction identity assigned Condition NETWORKINITIATED UEINITIATED Deactivate EPS bearer context request .4. '1100 1101'B Set according to specific message content. 7.12 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity ESM information response message identity Access point name Value/remark ESM '0000'B Access point name Access point name Any allowed value Protocol configuration options Not present or any allowed value IMS_APN_Default Internet_APN Expression pc_IMS AND NOT pc_Provide_IMS_as_second_APN AND pc_Provide_IMS_APN pc_IMS AND NOT pc_Provide_IMS_as_second_APN AND NOT pc_Provide_IMS_APN NOT pc_IMS OR pc_Provide_Internet_as_second_APN 3GPP Condition No EPS bearer identity assigned The same value as the value set in ESM INFORMATION REQUEST message.1 (2014-12) Explanation Network initiated ESM procedures UE initiated ESM procedures This message is always sent within SECURITY PROTECTED NAS MESSAGE message. - ESM INFORMATION RESPONSE This message is sent by the UE to the SS.3-13: ESM INFORMATION REQUEST Derivation Path: 24.301 clause 8.Release 12 299 Condition NETWORK-INITIATED UE-INITIATED NOTE: 3GPP TS 36. - ESM INFORMATION REQUEST This message is sent by the SS to the UE.508 V12.3.11 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity ESM information request message identity NOTE: Value/remark ESM '0000'B Comment Condition No EPS bearer identity assigned The value indicated in PDN CONNECTIVITY REQUEST message.7.4. Table 4. '1101 1001'B ESM information request This message is always sent within SECURITY PROTECTED NAS MESSAGE message.3.3-14: ESM INFORMATION RESPONSE Derivation Path: 24.301 clause 8. Table 4. '1101 1010'B Not present or any allowed value Not present Condition IMS_APN_Provided Comment ESM information response Internet_AP N IMS_APN_D efault IMS_APN_P rovided Explanation IMS APN shall be provided by the UE: No IMS APN shall be provided by the UE. IMS APN is default APN . 4. Table 4. Table 4.301 clause 8.3-16: MODIFY EPS BEARER CONTEXT ACCEPT Derivation Path: 24.3-15: ESM STATUS Derivation Path: 24. Comment Condition No procedure transaction identity assigned ESM status This message is always sent within SECURITY PROTECTED NAS MESSAGE message.3. '0000 0000'B Modify EPS bearer context accept message identity '1100 1010'B Protocol configuration options Not present or any allowed value NOTE: Comment No procedure transaction identity assigned Modify EPS bearer context accept This message is always sent within SECURITY PROTECTED NAS MESSAGE message. MODIFY EPS BEARER CONTEXT ACCEPT This message is sent by the UE to the SS. '0000 0000'B '1110 1000'B Set according to specific message content.Release 12 NOTE: - 300 3GPP TS 36. 3GPP Condition .7.3.301 clause 8. ESM STATUS This message is sent by the UE or by the SS.508 V12.1 (2014-12) This message is always sent within SECURITY PROTECTED NAS MESSAGE message.14 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM The same value as the value set in MODIFY EPS BEARER CONTEXT REQUEST message.13 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity ESM status message identity ESM cause NOTE: - Value/remark ESM Set according to specific message content.7. 4.301 clause 8.3-17: MODIFY EPS BEARER CONTEXT REJECT Derivation Path: 24. Table 4. '0000 0000'B Modify EPS bearer context reject message identity '1100 1011'B ESM cause The value is set according to specific message content.1 (2014-12) MODIFY EPS BEARER CONTEXT REJECT This message is sent by the UE to the SS.7. Not present Protocol configuration options NOTE: Comment No procedure transaction identity assigned Modify EPS bearer context reject This message is always sent within SECURITY PROTECTED NAS MESSAGE message.508 V12. 3GPP Condition .Release 12 - 301 3GPP TS 36.3.15 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM The same value as the value set in MODIFY EPS BEARER CONTEXT REQUEST message. Not Present.7..508 V12. Not Present. Not present Comment No procedure transaction identity assigned NETWORKINITIATED UEINITIATED Modify EPS bearer context request Best Effort Explanation Network initiated ESM procedures UE initiated ESM procedures This message is always sent within SECURITY PROTECTED NAS MESSAGE message.Release 12 302 - 3GPP TS 36.3. '1100 1001'B New EPS QoS TFT New QoS Negotiated LLC SAPI Radio priority Packet flow Identifier APN-AMBR Protocol configuration options Condition NETWORK-INITIATED UE-INITIATED NOTE: Use the same value as used in Activate EPS Bearer Context Request message According to reference dedicated EPS bearer context #2 except for TFT operation code which is set to ‘100’B and TFT identifier is set to ‘00110000’B.1 (2014-12) MODIFY EPS BEARER CONTEXT REQUEST This message is sent by the SS to the UE. '0000 0000'B Modify EPS bearer context request message identity The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST message or BEARER RESOURCE ALLOCATION REQUEST message. Not Present.301 clause 8.16 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity Value/remark ESM Set according to specific message content.3-18: MODIFY EPS BEARER CONTEXT REQUEST Derivation Path: 24. Not Present. 3GPP Condition pc_GERAN . '0000 0000'B Not Present. Table 4.4. Release 12 - 303 3GPP TS 36.508 V12.4.1 (2014-12) NOTIFICATION This message is sent by the SS to the UE. Table 4.7.3-18A: NOTIFICATION Derivation Path: 24.301 clause 8.3.18A Information Element Protocol discriminator EPS bearer identity Value/remark ESM '0000'B Procedure transaction identity The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message for IMS signalling. '0000 0000'B Notification message identity Notification indicator '1101 1011'B '0000 0001'B Condition SRVCC-HO-CANCELLED NOTE: - Comment Condition No EPS bearer identity assigned SRVCC-HOCANCELLE D No procedure transaction identity assigned Notification SRVCC handover cancelled, IMS session reestablishment required SRVCC-HOCANCELLE D Explanation Used if SRVCC handover is cancelled. This message is always sent within SECURITY PROTECTED NAS MESSAGE message. PDN CONNECTIVITY REJECT This message is sent by the SS to the UE. Table 4.7.3-19: PDN CONNECTIVITY REJECT Derivation Path: 24.301 clause 8.3.17 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity PDN connectivity reject message identity ESM cause Protocol configuration options NOTE: Value/remark ESM '0000'B The same value as the value set in PDN CONNECTIVITY REQUEST message. '1101 0001'B Comment Condition No EPS bearer identity assigned PDN connectivity reject The value is set according to specific message content. Not present This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MESSAGE message after NAS security mode control procedure has been successfully completed. 3GPP Release 12 - 304 3GPP TS 36.508 V12.4.1 (2014-12) PDN CONNECTIVITY REQUEST This message is sent by the UE to the SS. Table 4.7.3-20: PDN CONNECTIVITY REQUEST Derivation Path: 24.301 clause 8.3.18 Information Element Protocol discriminator EPS bearer identity Value/remark ESM '0000'B Procedure transaction identity PDN connectivity request message identity Any value from 1 to 254 '1101 0000'B Request type PDN type '0001'B Any value between '001'B, '010'B, '011'B and '100'B ESM information transfer flag Not present or any allowed value Not present Access point name Protocol configuration options NOTE: Not present or any allowed value Comment Condition No EPS bearer identity assigned PDN connectivity request initial request The allowed values are respectively IPv4, IPv6, IPv4v6 and "unused but interpreted as IPv6 by the network" The value is mandatory when the PDN CONNECTIVITY REQUEST message is sent together with an ATTACH REQUEST message. The value received from the UE does not affect the possible verdict associated with the message when received by the SS. The SS shall remember if this IE is present and its contents because this affects subsequent SS behaviour, e.g. coding of ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST. This message is sent without integrity protection before NAS security mode control procedure has been successfully completed and sent within SECURITY PROTECTED NAS MESSAGE message after NAS security mode control procedure has been successfully completed. 3GPP Release 12 - 305 3GPP TS 36.508 V12.4.1 (2014-12) PDN DISCONNECT REJECT This message is sent by the SS to the UE. Table 4.7.3-21: PDN DISCONNECT REJECT Derivation Path: 24.301 clause 8.3.19 Information Element Protocol discriminator EPS bearer identity Procedure transaction identity PDN disconnect reject message identity ESM cause - The value indicated in PDN DISCONNECT REQUEST message. '1101 0011'B Comment Condition No EPS bearer identity assigned PDN disconnect reject Set according to specific message content. Not present Protocol configuration options NOTE: Value/remark ESM '0000'B This message is always sent within SECURITY PROTECTED NAS MESSAGE message. PDN DISCONNECT REQUEST This message is sent by the UE to the SS. Table 4.7.3-22: PDN DISCONNECT REQUEST Derivation Path: 24.301 clause 8.3.20 Information Element Protocol discriminator EPS bearer identity Value/remark ESM '0000'B Procedure transaction identity PDN disconnect request message identity Any value from 1 to 254 '1101 0010'B Linked EPS bearer identity The EPS bearer identity of the associated default bearer. '0000'B Not present or any allowed value Spare half octet Protocol configuration options NOTE: Comment Condition No EPS bearer identity assigned PDN disconnect request This message is always sent within SECURITY PROTECTED NAS MESSAGE message. 4.7A Default TC message and information element contents This clause contains the default values of common TC (Test Control, see [38]) messages and information elements, which apply to all test cases unless otherwise specified. All the messages and information elements are listed in alphabetical order. 3GPP Release 12 - 306 3GPP TS 36.508 V12.4.1 (2014-12) ACTIVATE TEST MODE This message is sent by the SS to the UE embedded in a RRC DLInformationTransfer message. Table 4.7A-1: ACTIVATE TEST MODE Derivation Path: 36.509 clause 6.5 Information Element Value/remark Comment Protocol discriminator Skip indicator Message type UE test loop mode 1111 0000 10000100 00000000 UE test loop mode A UE test loop mode 00000001 UE test loop mode B UE test loop mode 00000010 UE test loop mode C Condition UE TEST LOOP MODE A UE TEST LOOP MODE B UE TEST LOOP MODE C - Condition UE TEST LOOP MODE A (default) UE TEST LOOP MODE B UE TEST LOOP MODE C Explanation UE test loop function configured for UE test loop mode A operation. UE test loop function configured for UE test loop mode B operation. UE test loop function configured for UE test loop mode C operation. ACTIVATE TEST MODE COMPLETE This message is sent by the UE to the SS embedded in a RRC ULInformationTransfer message. Table 4.7A-2: ACTIVATE TEST MODE COMPLETE Derivation Path: 36.509 clause 6.6 Information Element Protocol discriminator Skip indicator Message type Value/remark 1111 0000 10000101 3GPP Comment Condition Release 12 - 307 3GPP TS 36.508 V12.4.1 (2014-12) CLOSE UE TEST LOOP This message is sent by the SS to the UE embedded in a RRC DLInformationTransfer message. Table 4.7A-3: CLOSE UE TEST LOOP Derivation Path: 36.509 clause 6.1 Information Element Value/remark Protocol discriminator Skip indicator Message type UE test loop mode UE test loop mode A LB setup Length of UE test loop mode A LB setup list in bytes 1111 0000 10000000 00000000 UE test loop mode B LB setup UE test loop mode C LB setup UE test loop mode UE test loop mode A LB setup UE test loop mode B LB setup IP PDU delay UE test loop mode C LB setup UE test loop mode UE test loop mode A LB setup UE test loop mode B LB setup UE test loop mode C LB setup MBSFN area identity Not present Not present 00000001 Not present UE test loop mode A No LB setup list. No scaling (UL RLC SDU size will be equal to the received DL SDU size) 00000000 Not present 00000010 Not present Not present 00000000 MCH identity 00000000 Logical channel identity 00000001 Condition UE TEST LOOP MODE A UE TEST LOOP MODE B UE TEST LOOP MODE C - 0 Comment UE test loop mode B Condition UE TEST LOOP MODE A (default) UE TEST LOOP MODE B No delay UE test loop mode C UE TEST LOOP MODE C MTCH ID 0, same value as broadcasted in the default SystemInformationBloc kType13 message 0, same value as indicated in the default MBSFNAreaConfigurati on message 1, same value as indicated in the default MBSFNAreaConfigurati on message Explanation UE test loop function configured for UE test loop mode A operation. UE test loop function configured for UE test loop mode B operation. UE test loop function configured for UE test loop mode C operation. CLOSE UE TEST LOOP COMPLETE This message is sent by the UE to the SS embedded in a RRC ULInformationTransfer message. Table 4.7A-4: CLOSE UE TEST LOOP Derivation Path: 36.509 clause 6.2 Information Element Protocol discriminator Skip indicator Message type Value/remark 1111 0000 10000001 3GPP Comment Condition Release 12 - 308 3GPP TS 36.508 V12.4.1 (2014-12) DEACTIVATE TEST MODE This message is sent by the SS to the UE embedded in a RRC DLInformationTransfer message. Table 4.7A-5: DEACTIVATE TEST MODE Derivation Path: 36.509 clause 6.7 Information Element Value/remark Protocol discriminator Skip indicator Message type - Comment Condition 1111 0000 10000110 DEACTIVATE TEST MODE COMPLETE This message is sent by the UE to the SS embedded in a RRC ULInformationTransfer message. Table 4.7A-6: DEACTIVATE TEST MODE COMPLETE Derivation Path: 36.509 clause 6.8 Information Element Value/remark Protocol discriminator Skip indicator Message type - Comment Condition 1111 0000 10000111 OPEN UE TEST LOOP This message is sent by the SS to the UE embedded in a RRC DLInformationTransfer message. Table 4.7A-7: OPEN UE TEST LOOP Derivation Path: 36.509 clause 6.3 Information Element Protocol discriminator Skip indicator Message type - Value/remark Comment Condition 1111 0000 10000010 OPEN UE TEST LOOP COMPLETE This message is sent by the UE to the SS embedded in a RRC ULInformationTransfer message. Table 4.7A-8: OPEN UE TEST LOOP COMPLETE Derivation Path: 36.509 clause 6.4 Information Element Protocol discriminator Skip indicator Message type Value/remark 1111 0000 10000011 3GPP Comment Condition Release 12 - 309 3GPP TS 36.508 V12.4.1 (2014-12) UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST This message is sent by the SS to the UE embedded in a RRC DLInformationTransfer message. Table 4.7A-9: UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST Derivation Path: 36.509 clause 6.10 Information Element Protocol discriminator Skip indicator Message type - Value/remark Comment Condition 1111 0000 10001001 UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE This message is sent by the UE to the SS embedded in a RRC ULInformationTransfer message. Table 4.7A-10: UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE Derivation Path: 36.509 clause 6.11 Information Element Protocol discriminator Skip indicator Message type MBMS Packet Counter Value Value/remark 1111 0000 1000101 1 3GPP Comment Condition 4.1-1: HANDOVER TO UTRAN COMMAND 3GPP .508 V12.1 (2014-12) 4.7B.1 UTRA RRC messages – HANDOVER TO UTRAN COMMAND Table 4.Release 12 310 3GPP TS 36.7B Default UTRA message and information element contents 4.7B. S-RNTI-2 Ciphering algorithm RNC support for change of UE capability New H-RNTI 311 Value/remark U-RNTI-Short 0000 0000 0001B 00 0000 0001B UEA0 or UEA1.UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA HSUPA/HS DPA RB UTRA FDD PS RB. UTRA PS RB + Speech.1 (2014-12) Comment Condition UTRA FDD PS RB. UTRA HSUPA/HS DPA RB UTRA FDD PS RB. UTRA TDD PS RB. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA HSDPA RB. UTRA PS RB + Speech.2.SRNC identity . FALSE Not present '1010 1010 1010 1010' New Primary E-RNTI Not present '1010 1010 1010 1010' New Secondary E-RNTI Default configuration for CELL_FACH CHOICE specification mode . UTRA Speech. UTRA HSDPA RB. The indicated algorithm must be one of the algorithms supported by the UE. clause 10.4.508 V12. .16a Information Element New U-RNTI .Signalling RB information to setup List Not present Not present Complete specification Same as the corresponding IE in the RRC CONNECTION SETUP message (Transition to CELL_DCH or HS-PDSCH in CELL_FACH) using 3GPP 3GPP TS 36. UTRA Speech.Release 12 Derivation Path: 25.331. UTRA TDD PS RB. UTRA PS . UTRA Speech. UTRA HSDPA RB. 108 clause 9.UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H .508 V12.1.1 (2014-12) RB + Speech.108 clause 9. .4.2 for UTRA-TDD. 3GPP 3GPP TS 36.Release 12 312 condition A1 in TS 34.1 for UTRAFDD. Same as the corresponding IE in the RRC CONNECTION SETUP message in TS 34.1. 508 V12.1.28 Mcps TDD) using condition A2 in TS 34.1 for UTRA-FDD. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA FDD PS RB.28 Mcps TDD) using condition A3 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message (1. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1.1 for UTRA-FDD.1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.28 Mcps TDD option) message in TS 34.108 clause 9.1.108 clause 9.108 clause 9. UTRA PS RB + Speech.2 for UTRA-TDD.1 for UTRAFDD.108 clause 9.108 clause 9.1 (2014-12) UTRA TDD PS RB UTRA HSUPA/HS DPA RB UTRA Speech.28 Mcps TDD) using condition A11 in TS 34.1.108 clause 9.Release 12 .108 clause 9.2 for UTRA-TDD. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A11 in TS 34.28 Mcps 3GPP 3GPP TS 36.RAB information to setup list 313 Same as the corresponding IE in the RRC CONNECTION SETUP message in TS 34.2. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A3 in TS 34. Same as the corresponding IE in the RRC CONNECTION SETUP (Transition to CELL_DCH) (1.1.1 for UTRA-FDD.2 Same as the corresponding IE in the RRC CONNECTION SETUP message (Transition to CELL_DCH or HS-PDSCH in CELL_FACH) using condition A3 in TS 34.2 for UTRA-TDD. Same as the corresponding IE in the RADIO BEARER SETUP message (1. UTRA PS RB + Speech UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA TDD PS RB .1.1.2 for UTRA-TDD. Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9.4.108 clause 9. 508 V12.Release 12 314 TDD) using condition A3 in TS 34.2 for UTRA-TDD.1 (2014-12) .2.4. 3GPP 3GPP TS 36.108 clause 9. 108 clause 9.1.108 clause 9. UTRA PS RB + Speech.28 Mcps TDD) using condition A10 in TS 34.2 for UTRA-TDD.1 for UTRA-FDD Same as the corresponding IE in the RADIO BEARER SETUP message (1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.1.108 clause 9.1.28 Mcps TDD) using condition A3 in TS 34.1 for UTRA-FDD. UTRA TDD PS RB UTRA HSDPA RB UTRA .28 Mcps TDD) using condition A13 in TS 34.2 UTRA-TDD.1. Same as the corresponding IE in the RADIO BEARER SETUP message (1. Same as the corresponding IE in the RADIO BEARER SETUP message (1.2 for UTRA-TDD Same as the corresponding IE in the RADIO BEARER SETUP message using condition A3 in TS 34.4.108 clause 9.108 clause 9.108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.508 V12.108 clause 9.1. Same as the corresponding IE in the RADIO BEARER SETUP message (1.2 for UTRA-TDD.1.2.108 clause 9.2 for UTRA-TDD. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA FDD PS RB.28 Mcps TDD) using condition A10 in TS 34.1.28 Mcps TDD) using condition A2 in TS 34. Same content as the 3GPP 3GPP TS 36.UL Transport channel information common for all transport channels 315 Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34.108 clause 9.1.Release 12 .1 (2014-12) UTRA HSDPA RB UTRA HSUPA/HS DPA RB UTRA Speech. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1 for UTRA-FDD.1 for UTRA-FDD.108 clause 9.1 UTRA-FDD.1. 1.1 for UTRA-FDD.2 for UTRA-TDD.28 Mcps TDD) using condition A13 in TS 34.108 clause 9. Same content as the corresponding IE in the RADIO BEARER SETUP message (1.4.Release 12 316 corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.1 (2014-12) HSUPA/HS DPA RB .1.508 V12. 3GPP 3GPP TS 36.108 clause 9. 1.Added or Reconfigured UL TrCH information .2.108 clause 9.Added or Reconfigured UL TrCH information[1] 317 Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.1 (2014-12) UTRA Speech.Added or Reconfigured UL TrCH information .108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message (1.2.28 Mcps TDD) using condition A13 in TS 34.1. Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9. 3GPP 3GPP TS 36.1 Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34.1 for UTRA-FDD.1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A11 in TS 34.1 for UTRA-FDD.108 clause 9.1 for UTRA-FDD.1.28 Mcps TDD) in TS 34.28 Mcps TDD) using condition A11 in TS 34.508 V12.Release 12 .108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9.1. Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9.1 for UTRA-FDD. UTRA PS RB + Speech.1.2 for UTRA-TDD.28 Mcps TDD) using condition A2 in TS 34.2 for UTRA-TDD Same as the corresponding IE in the RADIO BEARER SETUP message using condition A3 in TS 34.1.1.2 for UTRA-TDD.108 clause 9.108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.4.1.28 Mcps TDD) using condition A10 in TS 34.2 for UTRA-TDD. 2 Entries Same as the corresponding IE in the RRC CONNECTION SETUP message (1.108 clause 9. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA FDD PS RB UTRA HSDPA RB UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA HSUPA/HS DPA RB UTRA TDD PS RB UTRA TDD PS RB . 2 for UTRAT-TDD.28 Mcps TDD) using condition A13 in TS 34.108 clause 9.28 Mcps TDD) using condition A2 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1.4.2.108 clause 9.108 clause 9.1 (2014-12) UTRA TDD PS RB UTRA Speech.1. Same as the corresponding IE in the RADIO BEARER SETUP message (1.28 Mcps TDD) using condition A10 in TS 34.108 clause 9.108 clause 9.2 for UTRA-TDD. Same as the 3GPP 3GPP TS 36.28 Mcps TDD) using condition A3 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A3 in TS 34. UTRA PS RB + Speech.108 clause 9.1 for UTRA-FDD. UTRA Speech + .Release 12 .1 Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9.108 clause 9.2 for UTRA-TDD.1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34. Same content as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message (1.2.Added or Reconfigured UL TrCH information[2] .2.Added or Reconfigured DL TrCH information 318 Same as the corresponding IE in the RADIO BEARER SETUP message (1.1. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA FDD PS RB UTRA TDD PS RB UTRA HSDPA RB UTRA HSUPA/HS DPA RB UTRA Speech.508 V12.1.1.2. UTRA PS RB + Speech.1 for UTRA-FDD.108 clause 9.DL Transport channel information common for all transport channels .1 for UTRA-FDD.1.108 clause 9.1 for UTRA-FDD.28 Mcps TDD) using condition A3 in TS 34. 1 (2014-12) Packet RAB Setup after Speech RAB Setup in CELL_DC H . 3GPP 3GPP TS 36.108 clause 9.508 V12.28 Mcps TDD) using condition A2 in TS 34.1.Release 12 319 corresponding IE in the RADIO BEARER SETUP message (1.2 for UTRA-TDD.4. Added or Reconfigured DL TrCH information .2.2 for UTRA-TDD.28 Mcps TDD) in TS 34.4. Same as the corresponding IE in the 3GPP 3GPP TS 36. UTRA PS RB + Speech.108 clause 9. UTRA Speech + Packet .1.1 for UTRA-FDD.1.1.1.28 Mcps TDD) using condition A3 in TS 34.Added or Reconfigured DL TrCH information[1] .108 clause 9.1 (2014-12) UTRA FDD PS RB UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA HSDPA RB UTRA HSUPA/HS DPA RB UTRA TDD PS RB UTRA TDD PS RB UTRA TDD PS RB UTRA Speech.1 for UTRA-FDD.108 clause 9.28 Mcps TDD) using condition A13 in TS 34. 2 Entries Same as the corresponding IE in the RRC CONNECTION SETUP message (1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.28 Mcps TDD) using condition A11 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34.1 Same as the corresponding IE in the RADIO BEARER SETUP message using condition A11 in TS 34.108 clause 9.Release 12 . Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1.28 Mcps TDD) using condition A10 in TS 34.1 for UTRA-FDD.Uplink DPCH info 320 Same as the corresponding IE in the RADIO BEARER SETUP message using condition A3 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1.108 clause 9.1.2.1 for UTRA-FDD.108 clause 9.108 clause 9.Added or Reconfigured DL TrCH information[2] .108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9.2 for UTRA-TDD.2. Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9.508 V12.2.1.2 for UTRA-TDD. 3GPP 3GPP TS 36.1 (2014-12) RAB Setup after Speech RAB Setup in CELL_DC H .1.2 for UTRA-TDD.108 clause 9.4.Release 12 321 RADIO BEARER SETUP message (1.28 Mcps TDD) using condition A13 in TS 34.508 V12. 28 Mcps TDD) using condition A3 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34. UTRA Speech.1.108 clause 9.1.108 clause 9.508 V12.1 for UTRA-FDD.1. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA HSUPA/HS DPA RB .2 for UTRA-TDD.1 Same as the corresponding IE in the RADIO BEARER SETUP message (1.28 Mcps TDD) using condition A13 in TS 34. UTRA PS RB + Speech.2.1.1.1. UTRA HSDPA RB. Not present Same as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.2.1 for UTRA-FDD.E-DCH Info 322 Same as the corresponding IE in the RADIO BEARER SETUP message using condition A3 in TS 34. UTRA TDD PS RB.1 (2014-12) UTRA FDD PS RB UTRA TDD PS RB UTRA HSDPA RB UTRA HSUPA/HS DPA RB UTRA FDD PS RB. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1 for UTRA-FDD.28 Mcps TDD) using condition A10 in TS 34.108 clause 9.108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message (1.Release 12 .108 clause 9.4. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.2 for UTRA-TDD. Same as the corresponding IE in the 3GPP 3GPP TS 36.108 clause 9.108 clause 9. Release 12 323 RADIO BEARER SETUP message (1.1 (2014-12) .508 V12.108 clause 9.28 Mcps TDD) using condition A13 in TS 34.2 for UTRA-TDD.4. 3GPP 3GPP TS 36.1. 108 clause 9.108 clause 9.108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.Release 12 .1.108 clause 9.Downlink HS-PDSCH Information .1 (2014-12) UTRA FDD PS RB. UTRA PS RB + Speech.108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1 Same as the corresponding IE in the 3GPP 3GPP TS 36.1 for UTRA-FDD.1. UTRA TDD PS RB.28 Mcps TDD) using condition A10 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message (1. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA HSDPA RB UTRA HSUPA/HS DPA RB UTRA Speech.1. UTRA PS RB + Speech.Downlink information common for all radio links 324 Not present Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34.1 for UTRA-FDD. Same as the corresponding IE in the RADIO BEARER SETUP message (1.508 V12.2 for UTRA-TDD.1.1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A4 in TS 34.4. UTRA Speech.1.28 Mcps TDD) using condition A13 in TS 34.108 clause 9.2 for UTRA-TDD. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.28 Mcps TDD) using condition A2 in TS 34.108 clause 9. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA FDD PS RB UTRA TDD PS RB .1.2 for UTRA-TDD.1 for UTRA-FDD. 108 clause 9.4. 3GPP 3GPP TS 36.1 (2014-12) .508 V12.2.2.Release 12 325 RADIO BEARER SETUP message (1.28 Mcps TDD) using condition A3 in TS 34. 1. Same as the corresponding IE in the RADIO BEARER SETUP message (1.108 clause 9.508 V12.28 Mcps TDD) using condition A2 in TS 34.Downlink information for each radio link list 326 Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A2 in TS 34.1 for UTRA-FDD.2 for UTRA-TDD.1.108 clause 9.2.108 clause 9.Release 12 . Same as the corresponding IE in the RADIO BEARER SETUP message (1.4.1.108 clause 9. Same as the corresponding IE in the RADIO BEARER SETUP message (1.1.1.28 Mcps TDD) using condition A10 in TS 34.28 Mcps TDD) using condition A10 in TS 34.108 clause 9.2 for UTRA-TDD.2 for UTRA-TDD.108 clause 9.1 (2014-12) UTRA HSDPA RB UTRA HSUPA/HS DPA RB UTRA Speech. Same as the 3GPP 3GPP TS 36.1. UTRA PS RB + Speech.108 clause 9.28 Mcps TDD) using condition A13 in TS 34. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34.2 for UTRA-TDD.2.1 Same as the corresponding IE in the RADIO BEARER SETUP message (1.28 Mcps TDD) using condition A3 in TS 34.108 clause 9.108 clause 9.1 for UTRA-FDD. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A10 in TS 34. UTRA Speech + Packet RAB Setup after Speech RAB Setup in CELL_DC H UTRA FDD PS RB UTRA TDD PS RB UTRA HSDPA RB UTRA . Same as the corresponding IE in the RADIO BEARER SETUP message (1.1.108 clause 9.1 for UTRA-FDD.1. Same as the corresponding IE in the RADIO BEARER SETUP message using condition A3 in TS 34.1 for UTRA-FDD.1. UTRA Establishment of the UTRA reference configuration as specified in Table 4.8.3-1 using the condition “UTRA HSDPA RB”.1. UTRA FDD PS RB Establishment of the UTRA FDD reference configuration as specified in Table 4.4.8.1 for UTRA-FDD.8.8. UTRA TDD PS RB Establishment of the UTRA TDD reference configuration as specified in Table 4.8. UTRA HSDPA RB Establishment of the UTRA reference configuration as specified in Table 4.3-1 using Speech the condition “UTRA PS RB + Speech”.2 for UTRA-TDD.Release 12 Frequency info Multi-frequency Info Maximum allowed UL TX power 327 corresponding IE in the RADIO BEARER SETUP message using condition A14 in TS 34. Set according to the frequency of the target UTRA cell.1 (2014-12) HSUPA/HS DPA RB Explanation Establishment of the UTRA reference configuration as specified in Table 4.3-1 using the condition “UTRA FDD PS RB”.8.3-1 using Packet RAB Setup the condition “UTRA Speech + Packet RAB Setup after Speech RAB Setup in Cell DCH”.8. UTRA Speech + Establishment of the UTRA reference configuration as specified in Table 4.1. UTRA PS RB + Establishment of the UTRA reference configuration as specified in Table 4.3-1 using HSUPA/HSDPA RB the condition “UTRA HSUPA/HSDPA RB”.108 clause 9.108 clause 9.3-1 using the condition “UTRA Speech”. after Speech RAB Setup in CELL_DCH 3GPP .28 Mcps TDD) using condition A13 in TS 34.3-1 using the condition “UTRA TDD PS RB”. Same as the corresponding IE in the RADIO BEARER SETUP message (1.508 V12. Not present 21dBm Condition UTRA Speech 3GPP TS 36. E-UTRA message – Comment E-UTRA RRCConnectionReconfig uration using condition HO-TO-EUTRA(1.RRC Message sequence number SR-VCC Info Activation time RAB Info . Not present Now .1-3: MEASUREMENT CONTROL Derivation Path: 25. SS provides the value of this IE.Measurement Report Transfer Mode .Periodical Reporting/Event Trigger Reporting Mode Additional measurement list Value/remark Arbitrarily selects an unused integer between 0 to 3 SS calculates the value of MAC-I for this message and writes to this IE.Release 12 – 328 3GPP TS 36.2.331.RRC message sequence number Measurement Identity Measurement Command Measurement Reporting Mode .CN domain identity . clause 10.331.1-8 MEASUREMENT CONTROL Table 4.Re-establishment timer Inter-system message .RAB identity 0000 0101B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity.CHOICE System type .1-2: HANDOVER FROM UTRAN COMMAND Derivation Path: 25.1 (2014-12) HANDOVER FROM UTRAN COMMAND Table 4.Message authentication code Value/remark Condition SS calculates the value of MAC-I for this message and writes to this IE.6. 3 Setup Acknowledged mode RLC Event trigger Not present 3GPP Comment Condition .2. from its internal counter. clause 10.NAS Synchronization Indicator . The first/ leftmost bit of the bit string contains the most significant bit of the MACI. SS provides the value of this IE. from its internal counter.0) See Table 4.7B.17 Information Element Message Type RRC transaction identifier Integrity check info .7B. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.Message authentication code . PS domain Not present Use T315 .508 V12.15 Information Element Message Type Integrity check info .4. CHOICE system .Measurement quantity .CHOICE reported cell 0 10 ms cellDCHMeasOccasionSequence .CHOICE system .CHOICE mode .Inter-RAT reporting quantity .Time to trigger .Hysteresis .Idle Interval Information CELL_DCH measurement occasion info LCR 3GPP TS 36.4.CHOICE Inter-RAT measurement objects .Reporting cell status .Measurement quantity .Measurement bandwidth .Measurement quantity for UTRAN quality estimate .-19).Measurement quantity .Timeslot Bitmap DPCH Compressed mode status info FDD_UTRA TDD Primary CCPCH RSCP E-UTRA RSRP 0 .Release 12 CHOICE Measurement type .Measurement occasion pattern sequence parameters -k .UTRAN estimated quality .Status Flag .Maximum number of reported cells .Measurement purpose .Parameters required for each event .Filter coefficient . -66 dB 0 -55 (-80 dBm) .Filter coefficient .. range should be (115.E-UTRA carrier frequency .1 (2014-12) When measurement quantity is RSRP.Inter-RAT event identity 329 Inter-RAT measurement E-UTRA frequency list Remove no frequencies Downlink EARFCN of EUTRA Cell Same downlink system bandwidth as used for EUTRA Cell Not present 0 FDD CPICH Ec/N0 CPICH RSCP For signalling tests cases. TDD_UTRA FALSE E-UTRA both Not present Inter-RAT measurement reporting criteria 1 entry Set according to specific test.Reporting cell status .CHOICE report criteria .Measurement quantity .25 [dBm] Report cells within active set or within virtual active set or of the other RAT 2 Not present LCR_TDD_U TRA 1 entry 0 activate '00001' 3 0 1 Not Present Not Present 3GPP FDD_UTRA AND NOT Compressed_ .Offset .M_Length .508 V12.Reporting quantity .Threshold other system . the actual value = Threshold other system .Inter-RAT measurement quantity .Pattern sequence identifier .Blacklisted cells list .CHOICE mode .Threshold own system -W .CHOICE E-UTRA frequency removal .New frequencies . 4.TGCFN DPCH Compressed mode status info Condition FDD_UTRA TDD_UTRA LCR_TDD_UTRA Compressed_mode – (Current CFN + (250 – TTI/10msec)) mod 256 1 entry 1 activate (Current CFN + (252 – TTI/10msec)) mod 256 Not present TDD_UTRA Explanation FDD UTRA cell environment TDD UTRA cell environment LCR TDD UTRA cell environment The UE Support of Compressed mode (TS 36.RSRP Set according to specific test.RSRQ Set according to specific test.1 (2014-12) mode FDD_UTRA AND Compressed_ mode DPCH Compressed mode status info .Measured E-UTRA cells .TGPS Status Flag . (256+CFN-(CFN MOD 8 + 8)) MOD 256 3 Not present Not present Not present Not present Not present 1 entry 1 entry PhysicalCellIdentity of EUTRA Cell .TGPS reconfiguration CFN .Transmission gap pattern sequence .E-UTRA Carrier Frequency . . The value is compared against the XMAC-I value computed by SS. E-UTRA Event Results .E-UTRA measured results list .1-4: MEASUREMENT REPORT Derivation Path: 25.4-1/28).508 V12.Inter-RAT event identity Set according to 3GPP Comment Condition .Release 12 330 3GPP TS 36.TGPSI .Physical Cell Identity Value/remark This IE is checked to see if it is present.4. MEASUREMENT REPORT Table 4.331. The value is used by SS to compute the XMAC-I value. clause 10.19 Information Element Message Type Integrity check info . This IE is checked to see if it is present.Message authentication code .523-2 table A. The first/ leftmost bit of the bit string contains the most significant bit of the MACI.2.RRC Message sequence number Activation time Measurement identity Measured Results Measured results on RACH Additional measured results Event results Inter-RAT cell info indication E-UTRA Measured Results .7B. The first/ leftmost bit of the bit string contains the most significant bit of the MACI.Downlink DPCH info common for all RL .2. from its internal counter.DPCH compressed mode info .E-UTRA events results list .331.4.DPCH compressed mode info .508 V12. clause 10.TGPS Status Flag .1-5: PHYSICAL CHANNEL RECONFIGURATION Derivation Path: 25. SS provides the value of this IE. Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present CELL_DCH Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present 1 Deactivate Not Present 3GPP TDD FDD .7B.Reported cells .1 (2014-12) specific test.Message authentication code .TGPSI .Release 12 331 3GPP TS 36.RRC message sequence number Integrity protection mode info Ciphering mode info Activation time Delay restriction flag New U-RNTI New C-RNTI New H-RNTI New Primary E-RNTI New Secondary E-RNTI RRC State indicator UE Mobility State Indicator UTRAN DRX cycle length coefficient CN information info URA identity RNC support for change of UE capability Reconfiguration in response to requested change of UE capability Downlink counter synchronization info Frequency info DTX-DRX timing information DTX-DRX Information HS-SCCH less Information MIMO parameters HARQ Info Maximum allowed UL TX power CHOICE channel requirement E-DCH Info Downlink HS-PDSCH Information Downlink information common for all radio links .E-UTRA Carrier Frequency .TGCFN Value/remark Comment Condition Arbitrarily selects an unused integer between 0 to 3 SS calculates the value of MAC-I for this message and writes to this IE.22 Information Element Message Type RRC transaction identifier Integrity check info .Physical Cell Identity – 1 entry Downlink EARFCN of EUTRA Cell 1 entry PhysicalCellIdentity of EUTRA Cell PHYSICAL CHANNEL RECONFIGURATION Table 4. . Uplink compressed mode method .Downlink frame type .Default DPCH Offset Value Downlink information for each radio link MBMS PL Service Restriction Information – 3GPP TS 36.ITP .TX Diversity mode . The value is compared against the XMAC-I value computed by SS.TGL1 .331.T Reconfirm abort .DeltaSIRAfter1 .TGPL1 .TGSN . This IE is checked to see if it is present.N identify abort .TGPRC .DeltaSIR2 .TGMP .DeltaSIR1 .RRC Message sequence number Uplink integrity protection activation info COUNT-C activation time Uplink counter synchronization info Value/remark This IE is checked to see if it is present.1 (2014-12) E-UTRA measurement Infinity 8 10 Not Present undefined 12 Not Present Mode 0 Mode 0 UL and DL.SSDT information .4.Release 12 332 .2. The first/ leftmost bit of the bit string contains the most significant bit of the MACI. The value is used by SS to compute the XMAC-I value.CHOICE UL/DL Mode . UL only or DL only (depending on the UE capability) HLS(or not sent.DeltaSIRAfter2 .TGL2 .Transmission gap pattern sequence configuration parameters . Not checked Not checked Not checked 3GPP Comment Condition .TGD .508 V12.1-6: PHYSICAL CHANNEL RECONFIGURATION COMPLETE Derivation Path: 25.RPP .Downlink compressed mode method . depending on the UE capability) HLS(or not sent.0) Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present Not Present PHYSICAL CHANNEL RECONFIGURATION COMPLETE Table 4. depending on the UE capability) B 20 (2.TGPL2 . clause 10.Message authentication code .7B.0) 10 (1.23 Information Element Message Type Integrity check info . CHOICE UE id type .331.7B. clause 10. clause 10.331.1-n: SECURITY MODE COMPLETE Derivation Path: 25.7B.Release 12 – 333 3GPP TS 36.1-7: RRC CONNECTION REQUEST Derivation Path: 25.1 (2014-12) RRC CONNECTION REQUEST Table 4. clause 10.2.2.4.2. Not checked Not checked Not checked Not checked Not checked Not Present Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked Not checked REL-8 REL-8 REL-8 REL-8 REL-8 REL-8 REL-9 REL-9 SECURITY MODE COMMAND Table 4.7B.43 Information Element FFS – Value/remark Comment Condition Comment Condition SECURITY MODE COMPLETE Table 4. To be checked against requirement if specified FALSE This IE will not be checked by default behaviour. but in specific test case.508 V12.331.1-n: SECURITY MODE COMMAND Derivation Path: 25.39 Information Element Message Type Predefined configuration status information Initial UE identity .TMSI and LAI (GSM-MAP) Establishment cause Protocol error indicator UE Specific Behaviour Information 1 idle Domain indicator Call type UE capability indication MBMS Selected Services Support for F-DPCH UE Mobility State Indicator Support for Enhanced F-DPCH HS-PDSCH in CELL_FACH MAC-ehs support DPCCH Discontinuous Transmission support Support of common E-DCH Multi cell support Pre-redirection info Support of MAC-i/is Support of SPS operation Support for CS Voice over HSPA Dual cell MIMO support System Information Container Stored Indicator Measured results on RACH Access stratum release indicator – Value/remark Comment Condition To be checked against requirement if specified Set to the UE's TMSI and LAI.44 Information Element FFS Value/remark 3GPP . 1-n: UTRAN MOBILITY INFORMATION Derivation Path: 34.508 V12.Release 12 – 334 3GPP TS 36.CN common GSM-MAP NAS system information .523-1 [18]: - UTRA NAS messages are defined as exceptions.CN domain related information .CN domain specific NAS system information .108 clause 9.CN domain specific DRX cycle length coefficient 7 – Comment UTRAN MOBILITY INFORMATION CONFIRM Table 4. to the messages defined in this section.108 clause 9.CN domain identity CS . In 3GPP TS 36.CN domain specific NAS system information .GSM-MAP NAS system information 1E 01H . IE by IE.4.GSM-MAP NAS system information 00 01H .1 (UTRAN MOBILITY INFORMATION CONFIRM message) 4.CN domain identity PS .2 UTRA NAS messages This section contains default message contents for UTRA NAS messages.GSM-MAP NAS system information 01 00H .7B.1.PLMN identity Not present .7B.1-n: UTRAN MOBILITY INFORMATION CONFIRM Derivation Path: 34. The following messages are not specified in this section: - AUTHENTICATION REQUEST (CS) - AUTHENTICATION RESPONSE (CS) - DETACH REQUEST (CS & PS) - DETACH ACCEPT (CS & PS) - IDENTITY REQUEST (CS & PS) - IDENTITY RESPONSE (CS & PS) - P-TMSI REALLOCATION COMMAND (PS) - P-TMSI REALLOCATION COMPLETE (PS) - SERVICE REQUEST (PS) 3GPP Condition . - UTRA NAS messages not defined in this section are specified completely.1 (UTRAN MOBILITY INFORMATION message) Information Element Value/remark UTRAN MOBILITY INFORMATION CN information info .1.CN domain specific DRX cycle length coefficient 7 .7B.1 (2014-12) UTRAN MOBILITY INFORMATION Table 4. Release 12 335 3GPP TS 36.4.2-1: ROUTING AREA UPDATE REQUEST 3GPP .1 (2014-12) Table 4.508 V12.7B. For test cases where no "UE" statement indicates that a PTMSI signature was previously registered.4. The checking of this IE is expected to be covered in UMTS test cases.508 V12. The checking of this IE is expected to be covered in UMTS test cases. The checking of this IE is expected to be covered in UMTS test cases. The checking of this IE is expected to be covered in UMTS test cases. whether or not the UE includes this IE depends on previous USIM contents. the UE may initiate either PS only or CS/PS registration procedures.Release 12 Derivation path: 24.4.14 Information Element Update type 336 Value/Remark 000 'RA updating' or 001 'combined RA/LA updating' 010 ‘combined RA/LA updating with IMSI attach’ GPRS ciphering key sequence number Old routing area identification MS Radio Access capability Any allowed value Any allowed value Any allowed value Old P-TMSI signature Not present or any allowed value Requested READY timer value Not present or any allowed value DRX parameter Not present or any allowed value TMSI status MS network capability 0 'no valid TMSI available' or not present Not present or any allowed value Any allowed value PDP context status Any allowed value PS LCS Capability Not present or any allowed value MBMS context status UE network capability Not present Any allowed value (must be present) Additional mobile identity Not present or any allowed value Not present or any allowed value Not present or any allowed value P-TMSI Additional old routing area identification Mobile station classmark 2 3GPP 3GPP TS 36. depending on capability and domain preference for voice and SMS.1 (2014-12) Comment In NMO I. No detailed checking by default but should be aligned with PICS This IE shall be included if the MS supports SRVCC Condition . The checking of this IE is expected to be covered in UMTS test cases.008 table 9. The checking of this IE is expected to be covered in UMTS test cases. Supported Codecs Not present or any allowed value Not present or any allowed value Any allowed value Rel-9 Voice domain preference and UE's usage setting P-TMSI type 3GPP Rel-10 .Release 12 337 3GPP TS 36.4.1 (2014-12) Mobile station classmark 3 Not present or any allowed value to GERAN or UTRAN.508 V12. This IE shall be included if the MS supports SRVCC to GERAN. 15 Information Element Force to standby Update result Value/Remark 0 'Force to standby not indicated' 000 'RA updated' Comment IF the UE indicated 000 'RA updating' in the previous RAU request message IF the UE indicated 001 'combined RA/LA updating' in the previous RAU request message 001 'combined RA/LA updated' Periodic RA update timer Routing area identification 1 ‘No follow-on proceed’ 111 (deactivated) 1 P-TMSI signature Allocated P-TMSI Arbitrary value Arbitrary value MS identity Not present List of Receive N PDU Numbers Not present Negotiated READY timer value GMM cause T3302 value Cell Notification Not present Not present Not present Not present Equivalent PLMNs PDP context status Not present Same value as the one received in the RAU request message Not present Not present Not present Not present Not present Not present Network feature support Emergency Number List MBMS context status Requested MS Information T3319 value T3323 value 3GPP Condition Value in table 4.Release 12 338 3GPP TS 36.4.4.4-2 for simulated UTRA cells.4.1 (2014-12) Table 4. .7B. and RA/LA procedures do not necessarily change TMSI Realistic network value This IE is for A/Gb mode only.008 table 9. 2 most significant bits = 11 to indicate SGSN Is never present in case of RA only procedure.508 V12.2-2: ROUTING AREA UPDATE ACCEPT Derivation path: 24. 2-5: LOCATION UPDATING ACCEPT Derivation path: 24.15 Information Element Location area identification Mobile identity TMSI 1 Follow on proceed Present CTS permission Equivalent PLMNs Emergency Number List Absent Absent Absent Value/Remark Arbitrary value 3GPP 2 most significant bits = 00 to indicate VLR This IE is unncessary in non-CS fallback test cases.17 Information Element Location updating type Ciphering key sequence number Location area identification Mobile station classmark Mobile identity Mobile station classmark for UMTS Additional update parameters Value/Remark Any allowed value Any allowed value Any allowed value Any allowed value Any allowed value Any allowed value Not present or any allowed value Table 4.2-4: LOCATION UPDATING REQUEST Derivation path: 24.7B.1 (2014-12) Table 4.7B.Release 12 339 3GPP TS 36.16 Information Element List of Receive N PDU Numbers Inter RAT handover information E-UTRAN inter RAT handover information Value/Remark Not present Not present Not present Comment Condition Comment Condition Comment Condition Table 4.4.2.508 V12.4.008 table 9.7B.008 table 9.2-3: ROUTING AREA UPDATE COMPLETE Derivation path: 24.008 table 9.2. . 4.7B.008 table 9.1 Information Element MS network capability Attach type GPRS ciphering key sequence number DRX parameter P-TMSI or IMSI Old routing area identification MS Radio Access capability Old P-TMSI signature Requested READY timer value TMSI status PS LCS Capability Mobile station classmark 2 Mobile station classmark 3 Supported Codecs UE network capability Additional mobile identity Additional old routing area identification Voice domain preference and UE's usage setting P-TMSI type Value/Remark Any allowed value 001 'GPRS attach' or 011 'Combiner GPRS/IMS attach' Any allowed value Any allowed value Any allowed value Any allowed value Any allowed value Not present or any allowed value Not present or any allowed value 0 'no valid TMSI available' or not present Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value Any allowed value (must be present) Not present or any allowed value Not present or any allowed value Not present or any allowed value Not present or any allowed value 3GPP Comment Rel-9 Rel-10 Condition .2-6: ATTACH REQUEST Derivation path: 24.4.508 V12.1 (2014-12) Table 4.Release 12 340 3GPP TS 36. 2 Information Element Attach result Value/Remark 001 'GPRS only attached' Comment 011 'combined GPRS/IMSI attached' Force to standby Routing area identification P-TMSI signature Negotiated READY timer value Allocated P-TMSI 000 'Force to standby not indicated' 111 (deactivated) 100 'priority level 4 (lowest)' 100 'priority level 4 (lowest)' 1 Arbitrary value Not present Arbitrary value MS identity Not present Periodic RA update timer Radio priority for SMS Radio priority for TOM8 Arbitrary value GMM cause T3302 value Cell Notification Equivalent PLMNs Network feature support Emergency Number List Requested MS Information T3319 value T3323 value Not present Not present Not present Not present Not present Not present Not present Not present Not present 3GPP Condition IF the UE indicated 001 'GPRS attach' in the previous attach request message IF the UE indicated 011 'Combined GPRS/IMS I attach' in the previous attach request message 2 most significant bits = 11 to indicate SGSN 2 most significant bits = 00 to indicate VLR IF the UE indicated 001 'GPRS attach' in the previous attach request message IF the UE indicated 011 'Combined GPRS/IMS I attach' in the previous attach request message .1 (2014-12) Table 4.Release 12 341 3GPP TS 36.4.508 V12.2-7: ATTACH ACCEPT Derivation path: 24.008 table 9.4.7B. 008 table 9.008 table 9.7B.4.7B.4.2-10: AUTHENTICATION AND CIPHERING RESPONSE Derivation path: 24.20 Information Element Location area identification Mobile identity Value/Remark Any allowed value Any allowed value Comment Condition Table 4.3 Information Element Inter RAT handover information E-UTRAN inter RAT handover information Value/Remark Not present Not present Comment Condition Table 4.2-8: ATTACH COMPLETE Derivation path: 24.Release 12 342 3GPP TS 36.2.7B.2.2-13: CM SERVICE REQUEST Derivation path: 24.7B.4.9 Information Element Ciphering algorithm IMEISV request Force to standby A&C reference number Value/Remark Any allowed value 000 ‘IMEISV not requested’ 000 'Force to standby not indicated' Any allowed value Comment Condition Table 4.008 table 9.508 V12.2-11: TMSI REALLOCATION COMMAND Derivation path: 24.11 Information Element CM service type Ciphering key sequence number Mobile station classmark Mobile identity Priority Additional update parameters Value/Remark Any allowed value Any allowed value Any allowed value Any allowed value Not present or any allowed value Not present or any allowed value 3GPP Comment Condition .4.1 (2014-12) Table 4.2-12: TMSI REALLOCATION COMPLETE Derivation path: 24.21 Table 4.2-9: AUTHENTICATION AND CIPHERING REQUEST Derivation path: 24.10 Information Element A&C reference number Spare half octet Value/Remark Arbitrary value 0000 Comment Condition Table 4.7B.008 table 9.008 table 9.2.008 table 9.7B. 7C Default DS-MIPv6 message and information element contents 4.Release 12 343 3GPP TS 36.1 (2014-12) 4.7C.1-1: Message IKE_SA_INIT Request 3GPP .7C.508 V12.1 IKEv2 messages - IKEv2 IKE_SA_INIT Request This message is sent by the UE to the SS.4. Table 4. 5 of TS 33.5 of TS 33.508 V12.1 (2014-12) Value/remark Set by the UE 0 ‘00100001’B ‘00100010’B ’00100010’B ‘00000010’B ‘00000001’B ‘00000001’B ‘00000000’B ‘00000010’B ‘00000011’B Transform type Transform ID ‘00000001’B ‘00000011’B More transform ‘00000011’B Transform type Transform ID ‘00000010’B ‘00000010’B More transform ‘00000011’B Transform type Transform ID ‘00000011’B ‘00000010’B Last transform ‘00000000’B Transform type Transform ID ‘00000100’B ‘00000010’B Last proposal Proposal # Protocol ID SPI size Number of transforms More transform ‘00000000’B ‘00000010’B ‘00000001’B ‘00000000’B ‘00000010’B ‘00000011’B Transform type Transform ID ‘00000001’B ‘00001011’B More transform ‘00000011’B Transform type Transform ID ‘00000010’B ‘00000100’B More transform ‘00000011’B 3GPP Comment First message jn IKE_SA_INIT exchange SA IKE_SA_INIT KE First cryptographic suite (section 6.234) IKE This is the transform for confidentiality Encryption AES with 128-bit keys in CBC mode (ENCR_AES_CB C) This is the transform for prf PRF PRF_AES128_XC BC_ AES-XCBCPRF-128 This is the Condition .234) IKE This is the transform for confidentiality Encryption 3DES in CBC mode (ENCR_3DES) This is the transform for prf PRF PRF_HMAC_SHA 1 (HMAC-SHA1) This is the transform for integrity Integrity HMAC-SHA1-96 (AUTH_HMAC_S HA1_96) This is the transform for DH DH Diffie-Hellman group 2 (1024-bit MODP) Second cryptographic suite (section 6.Release 12 344 Field IKE Header Initiator’s IKE_SA SPI Responder’s IKE_SA SPI Next Payload Exchange Type Security Association Payload Next Payload More proposal Proposal # Protocol ID SPI size Number of transforms More transform 3GPP TS 36.4. 508 V12.4.1 (2014-12) transform for integrity Integrity AES-XCBC-MAC96 (AUTH_ AESXCBC -96) This is the transform for DH DH Diffie-Hellman group 2 (1024-bit MODP) ‘00101000’B ‘0000000000000010’B Set by the UE Nonce DH group 2 ‘00101001’B Notify Random number set by the UE REDIRECT_SUPPORTED Notify Payload Next Payload ‘00000000’B No Next Payload Protocol ID ‘00000000’B SPI size ‘00000000’B Notify Message Type '0100000000010110'B Notification is not specific to a particular security association SPI field not present REDIRECT_SUP PORTED REDIRECT_FROM Notify Payload Next Payload ‘00000000’B No next payload Protocol ID ‘00000000’B SPI size ‘00000000’B Notification is not specific to a particular security association SPI field not present Notify Message Type '0100000000010110'B REDIRECT_FRO M GW Ident Type Any allowed value (IPv6 or IPv4 or HA FQDN) Set depending on how the UE has discovered the HA in the preamble New Responder GW Identity Depends on GW Ident type Condition UE IKE INIT HA UE IKE INIT HA Redirected UE IKE INIT HA UE IKE INIT HA UE IKE INIT HA UE IKE INIT HA UE IKE INIT HA UE IKE INIT HA UE IKE INIT HA Redirected UE IKE INIT HA Redirected UE IKE INIT HA Redirected UE IKE INIT HA Redirected UE IKE INIT HA Redirected UE IKE INIT HA Redirected UE IKE INIT HA Redirected Explanation Part of IKE_INIT_SA request message sent to HA only Part of IKE_INIT_SA request message sent to HA only after a REDIRECT payload was received in a previous IKEV2 messages exchange 3GPP .Release 12 345 Transform type Transform ID ‘00000011’B ‘00000101’B Last transform ‘00000000’B Transform type Transform ID ‘00000100’B ‘00000010’B Key Exchange Payload Next Payload DH Group # Key Exchange data Nonce Payload Next Payload Nonce data 3GPP TS 36. 1 (2014-12) IKE_SA_INIT Response This message is sent by the SS to the UE.1-2: Message IKE_SA_INIT Response Field IKE Header Initiator’s IKE_SA SPI Responder’s IKE_SA SPI Next Payload Exchange Type Security Association Payload Next Payload Proposal Key Exchange Payload Next payload DH Group # Key Exchange data Nonce Payload Next t payload Nonce data Value/remark Same as that set by the UE in IKE_SA_INIT request Set by the SS ‘00100001’B ‘00100010’B Comment SA IKE_SA_INIT ’00100010’B One of the 2 proposals included in IKE_SA_INIT at Step 1 KE ‘00 101000’B ‘0000000000000010’B Set by the SS Nonce DH group 2 ‘00000000’B Set by the SS No Next Payload 3GPP Condition . Table 4.508 V12.7C.4.Release 12 - 346 3GPP TS 36. 1 (2014-12) IKE_AUTH_Request This message is sent by the UE to the SS.7C.4.1-3: Message IKE_AUTH Request 3GPP .Release 12 - 347 3GPP TS 36. Table 4.508 V12. 1 (2014-12) Value/remark Comment Same as that set by the UE in IKE_INIT_SA Request Same as that set by the SS in IKE_INIT_SA Response ‘00101110’B ‘00100011’B E IKE_AUTH ‘00100011’B IDi Random value set by the UE Encrypted IKE Payloads Identification – Initiator Payload Next Payload ‘00101111’B ID Type 00000010B ID Set to MN-NAI CP Configuration Payload Next Payload ‘00100001’B SA CFG Type ‘00000001’B Request Configuration Attribute ‘00010000’B MIP6_HOME_PR EFIX attribute Length ‘0000000000000000’B Security Association Payload Next Payload ‘00101100’B Proposals Any set of allowed values TSi Traffic Selector – Initiator Payload Next Payload ‘00101100’B Traffic selector data Any allowed set of values TSr Traffic Selector – Responder Payload Next Payload ‘00100100’B Traffic selector data Any allowed set of values IDr Identification – Responder Payload Next Payload ‘00000000’B ID Type ‘00000010’B ID APN Next Payload ‘00110000’B Initialization Vector Random value set by the UE Encrypted IKE Payloads 3GPP No Next Payload EAP Condition UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 HA UE IKE AUTH1 HA UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH1 UE IKE AUTH2 UE IKE AUTH2 UE IKE AUTH2 .508 V12.4.Release 12 348 Field IKE Header Initiator’s IKE_SA SPI Responder’s IKE_SA SPI Next Payload Exchange Type Encrypted Payload Next Payload Initialization Vector 3GPP TS 36. 15) Fields from Encrypted payload Fields from Encrypted payload Fields from Encrypted payload Padding Set by the UE Pad Length Set by the UE Integrity checksum data Set by the UE Condition UE IKE AUTH1 UE IKE AUTH1 HA UE IKE AUTH2 UE IKE AUTH3 UE IKE AUTH2 UE IKE AUTH2 UE IKE AUTH2 UE IKE AUTH2 UE IKE AUTH2 UE IKE AUTH2 UE IKE AUTH2 UE IKE AUTH3 UE IKE AUTH3 UE IKE AUTH3 UE IKE AUTH3 UE IKE AUTH3 UE IKE AUTH3 UE IKE AUTH3 Explanation Part of IKE_AUTH request message sent to HA or ePDG after the reception of IKE_INIT_SA response Part of IKE_AUTH request message sent to HA after the reception of IKE_INIT_SA response Part of IKE_AUTH request message sent to HA or ePDG after the reception of IKE_ SA response message containing the certificate payload CERT Part of IKE_AUTH request message sent to HA or ePDG after the reception of IKE_SA response containing EAP and encryption payloads only 3GPP .4.4 ‘00100111’B AUTH Next Payload Initialization Vector Random value set by the UE Encrypted IKE Payloads Authentication Payload Next Payload ‘00000000’B No Next Payload Auth Method ’00000010’B Auth Data derived from the MSK obtained from AKA exchange Shared Key Integrity code RFC 4306 defines the function to derive this key (section 2.301 [28] subclause 9.3.9.1 (2014-12) Extensible Authentication Payload Next Payload ‘00000000’B No Next Payload Code ‘00000010’B Response Type ‘00010111’B AKA Subtype AKA-Challenge Attribute type ’00000011’B AT_RES AT_RES See TS 24.508 V12.Release 12 349 3GPP TS 36. 1-4: Message IKE_AUTH Response 3GPP .7C.Release 12 - 350 3GPP TS 36.508 V12.4.1 (2014-12) IKE_AUTH Response This message is sent by the SS to the UE. Table 4. Release 12 351 Field IKE Header Initiator’s IKE_SA SPI Responder’s IKE_SA SPI Next Payload Exchange Type Encrypted Payload Next Payload Initialization Vector 3GPP TS 36.508 V12.4.1 (2014-12) Value/remark Comment Same as that set by the UE in IKE_SA_INIT request Same as that set by the SS in IKE_SA_INIT response ‘00101110’B ‘00100011’B E IKE_AUTH ‘00100100’B IDr Set by the SS Encrypted IKE Payloads Identification – Responder Payload Next Payload ‘00100101’B ID Type ‘00000010’B ID APN CERT Certificate Payload Next Payload ‘00110000’B EAP Cert encoding ’00000100’B Certificate data Set by the SS X.509 certificate signature DER encoded X.509 certificate Extensible Authentication Payload Next Payload ‘00000000’B No Next Payload Code ‘00000001’B Request Type ‘00010111’B AKA Subtype AKA-Challenge Attribute type ’00000001’B AT_RAND AT_RAND An arbitrarily selected 128 bits value ‘00000010’B AT_AUTN Next Payload See TS 24.301 [28] subclause 9.9.3.2 ‘00110000’B EAP Initialization Vector Set by the SS Attribute Type AT_AUTN Encrypted IKE Payloads Extensible Authentication Payload Next Payload ‘00000000’B No Next Payload Code ‘00000011’B Success Next Payload ‘00101111’B CP Auth Method ’00000010’B Shared Key Integrity code 3GPP Condition SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH1 SS IKE AUTH2 SS IKE AUTH2 SS IKE AUTH2 SS IKE AUTH2 SS IKE AUTH2 SS IKE AUTH2 SS IKE AUTH3 SS IKE AUTH3 Release 12 Auth Data 352 derived from the MSK obtained from AKA exchange 3GPP TS 36.508 V12.4.1 (2014-12) RFC 4306 defines the function to derive this key (section 2.15) Configuration Payload Next Payload ‘00100001’B SA CFG Type ‘00000010’B Reply Configuration Attribute ‘00010000’B MIP6_HOME_PR EFIX attribute Length ‘0000000000010101’B Prefix lifetime Any allowed value Home Prefix IPv6 prefix – 16 bytes Prefix length ‘10000000’B Prefix length must be 64 Next Payload ‘00100001’B SA Protocol ID ‘00000000’B SPI Size ‘00000000’B Notification is not specific to a particular security association SPI field not present Notify Message Type Length ‘0100000000010111’B GW Ident Type ‘00000101’B New Responder GW Identity IPv6 address of the HA to relocate GW Ident Type ‘00000001’B New Responder GW Identity IPv4 address of the HA to relocate Optional Next Payload ‘00101101’ TSi Proposal One of the 2 proposals included in IKE_AUTH Request at Step 3 Notify Payload REDIRECT Security Association Payload Traffic Selector – Initiator Payload Next Payload ‘00101100’B Traffic Selector data Any allowed set of values TSr Traffic Selector – Responder Payload Next Payload Padding ‘00000000’B No Next Payload Set by the SS Fields from Encryption 3GPP SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 HA SS IKE AUTH3 HA SS IKE AUTH3 HA SS IKE AUTH3 HA SS IKE AUTH3 HA SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 HA redirect SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 SS IKE AUTH3 Release 12 353 Pad Length Set by the SS Integrity checksum data Set by the SS Condition SS IKE AUTH1 SS IKE AUTH2 SS IKE AUTH3 SS IKE AUTH3 HA SS IKE AUTH3 HA_redirect 3GPP TS 36.508 V12.4.1 (2014-12) payload Fields from Encryption payload Fields from Encryption payload Explanation Part of IKE_AUTH request message sent to the UE as part of the first IKE_AUTH Response message Part of IKE_AUTH request message sent to the UE as part of the second IKE_AUTH Response message Part of IKE_AUTH request message sent to the UE as part of the third IKE_AUTH Response message Part of IKE_AUTH request message sent to the UE as part of the third IKE_AUTH Response message when the UE interacts with HA Part of IKE_AUTH request message sent to the UE as part of the third IKE_AUTH Response message when the UE interacts with HA and the UE gets redirected 4.7C.2 Messages used to perform DS-MIPv6 registration and deregistration - Router Advertisement This message is sent by the SS to the UE. Table 4.7C.2-1: Message Router Advertisement Field Type Code Checksum Cur Hop Limit M O Value/remark ‘10000110’B ‘00000000’B Set by SS ‘00000000’B Set by the SS Set by the SS H Prf ‘0’B Set by the SS Prf Set by the SS P Set by the SS Reserved Router Lifetime Reachable Time Retrans Timer type ‘00000’B Set by the SS Set by the SS Set by the SS ‘00000011’B Length Prefix length L A Valid Lifetime Preferred Lifetime Prefix ‘00000100’B Set by the SS ‘1’B Set by the SS Set by the SS Set by the SS Set as per specific message content 3GPP Comment ICMP checksum Unspecified Depends on access network specific settings Depends on access network specific settings Depends on access network specific settings Depends on access network specific settings Prefix Information Option Condition Release 12 - 354 3GPP TS 36.508 V12.4.1 (2014-12) Binding Update This message is sent by the UE to the SS. Table 4.7C.2-2: Message Binding Update Information Element IPv4 Source Address IPv4 Destination Address UDP header Source Port Destination port IPv6 Source Address IPv6 Destination Address Destination Header Payload Proto MH Type Sequence Number Lifetime A H L K M R P F IPv4 Home Address option Alternate Care-of Address option Value/remark UE IPv4 CoA (IPv4 address acquired by UE during network attachment) IPv4 of Home Agent discovered during preamble Set by UE ‘0001000001011111’B UE IPv6 CoA (IPv6 address acquired by the UE during network attachment) IPv6 Home Address configured by the UE from Home Network Prefix assigned to UE during preamble IPv6 of Home Agent discovered during preamble IPv6 Home Address configured by the UE from Home Network Prefix assigned to the UE during preamble ‘00111011’B ‘00000101’B Comment UE IPv4 UE IPv4 UE IPv4 UE IPv4 IPv6 visited UE IPv6home, UE IPv4 IPv6 visited Binding Update message Any allowed value Any allowed non-zero value ‘0000000000000000’B ‘1’B ‘1’B Not checked ‘1’B ’0’B ’1’B ‘0’B ’0’B Set to the value "0.0.0.0" to request allocation for the UE. The "P" flag is set to '0'B. The Prefix Length is set to the requested prefix length of '32'. Same IPv6 address as that inserted in the IP Source Address field Condition Explanation 3GPP Condition UE IPv4 IPv6 visited UE IPv6home Optional UE IPv6visited Release 12 355 UE IPv4 UE IPv6-home UE IPv6-visited - 3GPP TS 36.508 V12.4.1 (2014-12) UE is in an IPv4 visited network (see RFC 5555) UE is in an IPv6 home network (see RFC 5555) UE is in an IPv6 visited network (see RFC 5555) Binding Acknowledgement This message is sent by the SS to the UE. Table 4.7C.2-3: Message Binding Acknowledgement Information Element IPv4 Source Address IPv4 Destination Address UDP header Source Port Destination port Value/remark IPv4 Home Agent address Same value as UE IPv4 CoA in IP Source Address from Binding Update Comment UE IPv4 UE IPv4 UE IPv4 UE IPv4 ‘0001000001011111’B Same as Source port in Binding Update IPv6 Home Agent address Same value as UE IPv6 CoA in IP Source Address from Binding Update IPv6 Home Address IPv6 Source Address IPv6 Destination Address Routing Header Payload Proto MH Type Same value as UE IPv6 Home Address in Destination Header from Binding Update ‘00111011’B ‘00000110’B Status ‘00000000’B K R P Sequence Number Set by the SS ‘1’B ‘0’B Same value as that sent by the UE in the Binding Update ‘0000000010010110’B Lifetime UE IPv6visited UE IPv6home, UE IPv4 UE IPv6visited Binding Acknowledgement message Binding Update accepted 10 min ‘0000000000000000’B IPv4 Address Acknowledgement option IPv4 Home Address allocated to the UE Binding Refresh Advice option ‘0000000010010110’B Condition UE IPv4 UE IPv6-home UE IPv6-visited Present if IPv4 Home Address option was included by the UE in Binding Update 10 min Explanation UE is in an IPv4 visited network (see RFC 5555) UE is in an IPv6 home network (see RFC 5555) UE is in an IPv6 visited network (see RFC 5555) 3GPP Condition UE IPv4 UE IPv6visited, UE IPv4 UE IPv6home Release 12 - 356 3GPP TS 36.508 V12.4.1 (2014-12) Binding Revocation Indication This message is sent by the SS to the UE. Table 4.7C.2-4: Binding Revocation Indication Field IPv4 Header IPv4 Source Address UDP header Source Port Destination port IPv6 Header IPv6 Source Address IPv6 Destination Address Routing Header B.R. Type Sequence Number Revocation Trigger P G V Condition UE IPv4 UE IPv6-visited Value/remark Comment UE IPv4 Home Agent address UE IPv4 UE IPv4 UE IPv4 Set by SS ‘0001000001011111’B IPv6 Home Agent address IPv6 Home Address configured by UE from Home Network Prefix assigned to UE during preamble IPv6 CoA IPv6 Home Address configured by the UE from Home Network Prefix assigned to the UE during preamble ‘00000001’B Set by the SS ‘00000001’B ‘0’B ‘0’B ‘0’B UE IPv4 UE IPv6visited UE IPv6visited B.R.I Explanation UE is in an IPv4 visited network (see RFC 5555) UE is in an IPv6 visited network (see RFC 5555) 3GPP Condition UE IPv4 UE IPv4 Release 12 - 357 3GPP TS 36.508 V12.4.1 (2014-12) Binding Revocation Acknowledgement This message is sent by the UE to the SS. Table 4.7C.2-5: Binding Revocation Acknowledgement Information Element IPv4 Header IPv4 Source Address IPv4 Destination Address UDP header Source Port Destination port IPv6 Header IPv6 Source Address IPv6 Destination Address Destination Header B.R. Type Sequence Number Status P G V Condition UE IPv4 UE IPv6-visited Value/remark Comment IPv4 CoA UE IPv4 Home Agent Address ‘0001000001011111’B Same as Source port in Binding Revocation UDP header Source Port Destination port IPv6 Home Address configured by UE IPv6 CoA IPv6 of Home Agent address IPv6 Home Address configured by the UE ‘00000010’B Same value as Sequence Number sent by the SS in Binding Revocation ‘00000000’B '0’B '0’B '0’B UE IPv4 UE IPv4 UE IPv4 UE IPv4 UE IPv6visited IPv6 Destination Address UE IPv6visited B.R.A Success Explanation UE is in an IPv4 visited network (see RFC 5555) UE is in an IPv6 visited network (see RFC 5555) 3GPP Condition UE IPv4 UE IPv4 UE IPv4 7D.2.7D.508 V12.Release 12 358 3GPP TS 36.7D Default GERAN message and information element contents 4.1 Information Element PAGE_MODE Global TFI CONTAINER_ID PS Handover to A/Gb Mode Payload PS Handover RR Info flag PS Handover Radio Resources IE Handover Reference ARFCN SI NCI BSIC 0 <CCN_ACTIVE> 0 <3G_CCN_ACTIVE> 0 <CCN Support Description> Frequency Parameters NETWORK_CONTROL_ORDER 0 <Global Packet Timing Advance> EXTENDED_DYNAMIC_ALLOCATION RLC_RESET 0 <PO> 0 <Uplink Control Timeslot> 0 GPRS mode 0 <NAS Container for PS Handover IE> Value/remark Default TFI of mobile station uplink TBF 00 00 00 Present 0 default ARFCN for BCCH of GERAN cell 00 0 BSIC of GERAN cell not present not present not present default PDTCH of GERAN cell 2 not present 0 1 not present not present Uplink TBF assignment for default PDTCH of GERAN cell not present 3GPP Comment PS Handover RR Info Non-synchronized RLC is reset Condition .1 GPRS message – PS HANDOVER COMMAND Table 4.060 clause 11.1-1: PS HANDOVER COMMAND Derivation Path: 44.1 (2014-12) 4.4.43. 8.2.2 4.3.1 (2014-12) 4.2.8.2 Information Element SRB-ToAddMod-DEFAULT ::= SEQUENCE { srb-Identity Value/remark Comment 1 2 Condition SRB1 SRB2 rlc-Config CHOICE { defaultValue } logicalChannelConfig CHOICE { defaultValue } } 4.8.1.8.508 V12.2.Release 12 359 3GPP TS 36.2.1-1: PDCP-Config-DRB-UM Derivation Path: 36.8.2 SRB and DRB parameters and combinations 4.2.2.331 clause 6.1.1.2.3.1 4.1.4.331 clause 6.1 SRB and DRB parameters SRB configurations Table 4.1-1: SRB-ToAddMod-DEFAULT Derivation Path: 36.8.1.2.1 General 4.2 Information Element PDCP-Config-DRB-UM ::= SEQUENCE { discardTimer rlc-AM SEQUENCE {} rlc-UM SEQUENCE { pdcp-SN-Size } headerCompression CHOICE { notUsed } Value/remark ms100 Not present Len12bits NULL } 3GPP Comment Suitable for real time services Condition .8.8 Reference radio bearer configurations 4.1 DRB PDCP configurations DRB PDCP configurations for UM RLC Table 4.8. 3.331 clause 6.1 Value/remark Comment Condition Comment Condition Infinity TRUE Not present NULL DRB RLC configurations DRB UM RLC configurations Table 4.331 clause 6.3.1-1: RLC-Config-DRB-UM Derivation Path: 36.1.8.3.2-1: RLC-Config-DRB-AM Derivation Path: 36.8.331 clause 6.8.3 4.3.2.1 (2014-12) DRB PDCP configurations for AM RLC Table 4.2.3.8.2.2 Information Element PDCP-Config-DRB-AM ::= SEQUENCE { discardTimer rlc-AM SEQUENCE { statusReportRequired } rlc-UM SEQUENCE {} headerCompression CHOICE { notUsed } } 4.2. Condition .1.1.1.2-1: PDCP-Config-DRB-AM Derivation Path: 36.1.1.3.8.508 V12.3.4.2 Information Element RLC-Config-DRB-UM ::= CHOICE { um-Bi-Directional SEQUENCE { ul-UM-RLC SEQUENCE { sn-FieldLength } dl-UM-RLC SEQUENCE { sn-FieldLength t-Reordering Value/remark Size10 Size10 ms50 ms50 provides sufficient margin } } } 4.2.1.2 Information Element RLC-Config-DRB-AM ::= CHOICE { am SEQUENCE { ul-AM-RLC SEQUENCE { t-PollRetransmit pollPDU pollByte maxRetxThreshold } dl-AM-RLC SEQUENCE { t-Reordering t-StatusProhibit Value/remark Comment ms80 p128 kB125 t4 ms80 Ms60 } } } 3GPP Is sufficient for 5 HARQ transmissions Should be equal to or smaller than t-PollRetransmit.Release 12 4.8.2 360 3GPP TS 36.2.2.2 DRB AM RLC configurations Table 4.2.2.8. 1.3.8.4 361 3GPP TS 36.2 Information Element LogicalChannelConfig-DRB ::= SEQUENCE { ul-SpecificParameters SEQUENCE { priority prioritisedBitRate bucketSizeDuration logicalChannelGroup Value/remark 6 13 kBps0 ms100 1 2 } } Condition HI LO Explanation Used for DRBs with high logical channel priority Used for DRBs with low logical channel priority 3GPP Comment Condition HI LO PBR is disabled.331 clause 6.4.Release 12 4. HI LO .2.1 (2014-12) DRB Logical Channel configurations Table 4.1.8.4-1: LogicalChannelConfig-DRB Derivation Path: 36.2.508 V12. Release 12 4.4.2.1.508 V12.1.2.8.1 (2014-12) .5-1: MAC-MainConfig-RBC 3GPP 3GPP TS 36.8.5 362 MAC configurations Table 4. 1 (2014-12) Value/remark Comment Not present SCell_AddM od n5 sf20 Infinity no_periodic _BSR_or_ PHR sf320 sf10240 no_periodic _BSR_or_ PHR FALSE Not present NOT pc_FeatrGrp _5 or SCell_AddM od pc_FeatrGrp _5 AND DRX_S drx-Config CHOICE { setup SEQUENCE { onDurationTimer drx-InactivityTimer drx-RetransmissionTimer longDRX-CycleStartOffset CHOICE { sf40 } shortDRX Condition psf2 psf100 psf16 sf40 typical value in real network for real-time services. 4 0 For SIG For RF Not present } } timeAlignmentTimerDedicated phr-Config CHOICE { release } phr-Config sf750 no_periodic _BSR_or_ PHR NULL Not present phr-Config CHOICE { setup SEQUENCE { 3GPP SCell_AddM od and RF .3.2 Information Element MAC-MainConfig-RBC ::= SEQUENCE { ul-SCH-Config ul-SCH-Config SEQUENCE { maxHARQ-Tx periodicBSR-Timer retxBSR-Timer ttiBundling } drx-Config 363 3GPP TS 36. 4 0 For SIG For RF Not present } } drx-Config CHOICE { setup SEQUENCE { onDurationTimer drx-InactivityTimer drx-RetransmissionTimer longDRX-CycleStartOffset CHOICE { sf1280 } shortDRX pc_FeatrGrp _5 AND DRX_L psf6 psf1920 psf16 sf1280 typical value in real network for besteffort services.4.508 V12.Release 12 Derivation Path: 36.331 clause 6. 331 clause 6.2.2 Information Element MAC-MainConfig-SRB ::= SEQUENCE { ul-SCH-Config SEQUENCE { maxHARQ-Tx periodicBSR-Timer retxBSR-Timer ttiBundling } drx-Config CHOICE { release } timeAlignmentTimerDedicated phr-Config CHOICE { setup SEQUENCE { periodicPHR-Timer prohibitPHR-Timer dl-PathlossChange } } } Value/remark n5 sf20 sf320 FALSE NULL sf750 sf500 sf200 dB3 3GPP Comment Condition .3.4.Release 12 364 periodicPHR-Timer prohibitPHR-Timer dl-PathlossChange 3GPP TS 36.8.1 (2014-12) sf500 sf200 dB3 } } sr-ProhibitTimer-r9 mac-MainConfig-v1020 mac-MainConfig-v1020SEQUENCE { sCellDeactivationTimer-r10 extendedBSR-Sizes-r10 extendedPHR-r10 Not present Not present SCell_AddM od rf32 setup setup } } Condition DRX_S DRX_L no_periodic_BSR_or_PHR For SIG For RF SCell_AddMod Explanation Used for DRX configuration with small DRX cycle length Used for DRX configuration with large DRX cycle length Used to disable BSR and PHR Used for DRX configuration in Protocol testing Used for DRX configuration in RRM testing Addition or modification of SCell Table 4.508 V12.1.5-2: MAC-MainConfig-SRB Derivation Path: 36. 2.6 365 3GPP TS 36.Release 12 4.2.1 (2014-12) Physical Layer configurations Table 4.1.1.4.8.8.6-1: PhysicalConfigDedicated-DEFAULT 3GPP .508 V12. 2 Information Element PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { pdsch-ConfigDedicated pucch-ConfigDedicated 366 3GPP TS 36.6.3 CA SRB1 or HO-TOEUTRA SCell_AddM od RBC or RBC-HO Not present pusch-ConfigDedicated PUSCHConfigDedicatedDEFAULT Not present See subclause 4.Release 12 Derivation Path: 36.6.3 CQI-ReportConfigDEFAULT using condition CQI_PERIODIC Not present Not present See subclause 4.3 PUCCHConfigDedicatedDEFAULT See subclause 4.3 CQI-ReportConfigDEFAULT See subclause 4.3.3 TPC-PDCCH-ConfigDEFAULT using condition PUSCH See subclause 4.6.6.6.508 V12.6.3 SRB1 or HO-TOEUTRA RBC or RBC-HO SCell_AddM od SRB1 or RBC-HO or HO-TOEUTRA RBC SCell_AddM od SRB1 or HO-TOEUTRA RBC or RBC-HO SCell_AddM od SRB1 or HO-TOEUTRA RBC or RBC-HO SCell_AddM od SRB1 SCell_AddM od RBC or RBC-HO or HO-TOEUTRA SRB1 SCell_AddM od RBC or RBC-HO or HO-TOEUTRA SRB1 or HO-TOEUTRA RBC or RBC-HO SoundingRS-UlConfigDedicatedDEFAULT See subclause 4.6.4.3 uplinkPowerControlDedicated UplinkPowerControlDedi cated-DEFAULT See subclause 4.6.331 clause 6.3 Not present 2TX tm3 '11' } 3GPP BIT STRING (SIZE (2)) .6.1 (2014-12) Value/remark Comment PDSCHConfigDedicatedDEFAULT Not present See subclause 4.3 Not present tpc-PDCCH-ConfigPUCCH Not present TPC-PDCCH-ConfigDEFAULT using condition PUCCH tpc-PDCCH-ConfigPUSCH cqi-ReportConfig soundingRS-UL-ConfigDedicated antennaInfo CHOICE { explicitValue SEQUENCE { transmissionMode codebookSubsetRestriction CHOICE { n2TxAntenna-tm3 Condition See subclause 4. 1 (2014-12) Not present Not present Not present Not present FALSE Not present CQI-ReportConfig-r10DEFAULT Not present Not present PUCCHConfigDedicated-v1020DEFAULT Not present 3GPP See subclause 4.6.508 V12.Release 12 ue-TransmitAntennaSelection CHOICE { Release } } defaultValue } schedulingRequestConfig 367 NULL NULL SchedulingRequestConfig-DEFAULT Not present cqi-ReportConfig-v920 antennaInfo-v920 antennaInfo-r10 antennaInfoUL-r10 cif-Presence-r10 cqi-ReportConfig-r10 csi-RS-Config-r10 pucch-ConfigDedicated-v1020 pusch-ConfigDedicated-v1020 3GPP TS 36.3 SRB1 or RBC-H or HO-TOEUTRA RBC SCell_AddM od SCell_AddM od SCell_AddM od SCell_AddM od .4. Release 12 schedulingRequestConfig-v1020 soundingRS-UL-ConfigDedicated-v1020 soundingRS-UL-ConfigDedicatedAperiodic-r10 uplinkPowerControlDedicated-v1020 additionalSpectrumEmissionCA-r10 additionalSpectrumEmissionCA-r10 368 3GPP TS 36..4.maxCSI-RS-ZP-r11)) OF { CSI-RS-ConfigZP-r11[1] } pdsch-ConfigDedicated-v1130 cqi-ReportConfig-v1130 pucch-ConfigDedicated-v1130 pusch-ConfigDedicated-v1130 uplinkPowerControlDedicated-v1130 } Note: SCell_AddM od and (TxD or SRSAp) SCell_AddM od and IntraBC CA SCell_AddM od and InterB CA and UL CA 1 (CA_NS_01) EPDCCH-Config-r11DEFAULT Not present Not present Not present 1 entry ePDCCH DL_CoMP CSI-RS-ConfigNZP-r11DEFAULT Not present Not present 1 entry DL_CoMP CSI-RS-ConfigZP-r11DEFAULT PDSCHConfigDedicated-v1130DEFAULT Not present CQI-ReportConfig-v1130DEFAULT Not present PUCCHConfigDedicated-v1130DEFAULT Not present PUSCHConfigDedicated-v1130DEFAULT Not present UplinkPowerControlDedic ated-v1130-DEFAULT Not present For signalling test.1. Condition Explanation 3GPP DL_CoMP DL_CoMP UL_CoMP UL_CoMP UL_CoMP .1-1 is applied..6B.1.maxCSI-RS-NZP-r11)) OF { CSI-RS-ConfigNZP-r11[1] } csi-RS-ConfigZPToReleaseList-r11 csi-RS-ConfigZPToAddModList-r11 csi-RS-ConfigZPToAddModList-r11 SEQUENCE (SIZE (1. table 6.1 (2014-12) Not present Not present Not present UplinkPowerControlDedic ated-v1020-DEFAULT Not present Not present Not present additionalSpectrumEmissionCA-r10 CHOICE { setup SEQUENCE { additionalSpectrumEmissionPCell-r10 } } epdcch-Config-r11 csi-RS-ConfigNZPToReleaseList-r11 csi-RS-ConfigNZPToAddModList-r11 csi-RS-ConfigNZPToAddModList-r11 SEQUENCE (SIZE (1.508 V12. where n=1.M This SRB and DRB combination is setup with UE Registration procedure and the Generic Radio Bearer Establishment or Generic Radio Bearer Establishment. UE Test Mode Activated procedure using specific message content .Release 12 369 SRB1 RBC 2TX RBC-HO SCell_AddMod HO-TO-EUTRA ePDCCH DL_CoMP UL_CoMP CA TxD SRSAp Intra-BC CA Inter-B CA UL CA 4.1.1 Explanation Used for AM DRB Used for UM DRB SRB and DRB combinations Combinations on DL-SCH and UL-SCH SRB1 and SRB2 for DCCH + n x AM DRB + m x UM DRB.the default RRCConnectionReconfiguration message with condition SRB2-DRB(n.1 4..2.2..8.1.3-1 defines UTRA reference radio parameters and combinations to be used in E-UTRA and UTRA inter-RAT test cases.2.8. DRB configurations Table 4.8.2.2 Information Element DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE { eps-BearerIdentity drb-Identity pdcp-Config Value/remark Comment bid is the bearer identity (1.331 clause 6.8.8. 3GPP .3.8. Aperiodic SRS configured Intra-band contiguous Carrier Aggregation Inter-band Carrier Aggregation When UL Carrier Aggregation is used. m).1.7-1: DRB-ToAddMod-DEFAULT(bid) Derivation Path: 36..2 4.7 3GPP TS 36.4.2.8) bid+4 bid PDCP-Config-DRB-AM PDCP-Config-DRB-UM RLC-Config-DRB-AM RLC-Config-DRB-UM bid+2 LogicalChannelConfigDRB using condition HI LogicalChannelConfigDRB using condition LO rlc-Config logicalChannelIdentity logicalChannelConfig Condition AM UM AM UM UM AM } Condition AM UM 4. 4.N and m=0.508 V12.8.2.2.1 (2014-12) Used at configuration of SRB1 during RRC connection (re-)establishment Used at configuration of a radio bearer combination during SRB2+DRB establishment Used for cells with two antenna ports Used during Handover Addition or modification of SCell Inter-RAT handover to E-UTRA Used at configuration of ePDCCH Used for DL CoMP Used for UL CoMP For Carrier Aggregation Test cases When PUCCH Transmission Diversity is performed.3 UTRA reference radio parameters and combinations Table 4. 108 subclause 6.2.108[5].2 kbps / CS RAB + Interactive or background / UL:64 DL:64 kbps / PS RAB+ UL:3.108 subclause 6.2 Definition of the test algorithm for authentication Same as clause 8.9.2. using Key derivation function HMACSHA-256 algorithm.10.2 DL:12.1 in 3GPP TS 34.26 UTRA HSUPA/HSDPA RB TS 34. 4.1 General See clause 8.4-1 defines GERAN reference PDP context parameters to be used in E-UTRA and GERAN inter-RAT test cases.4 kbps SRBs for DCCH Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH Conversational / speech / UL:12. Test PDP context3.2.1 Comment Conversational / speech / UL:12.4 kbps SRBs for DCCH 4. 4. RES[XRES] as in clause 8.2 DL:12. CSIM and ISIM parameters This clause defines default parameters for programming the elementary files of the test UICC when running conformance test cases defined in 3GPP TS 36.4 DL: 3.4 DL:3.9 Common test USIM.4 GERAN reference PDP context parameters Table 4.2 kbps / CS RAB + UL:3.2.9. CSIM and ISIM and SS UE and SS calculate Ck.4 UTRA FDD PS RB UTRA HSDPA RB TS 34.1.4 kbps SRBs for DCCH Interactive or background / UL:64 DL: 64 kbps / PS RAB + UL:3.8.8.10.108 subclause 6.9. AUTN.508 V12.2.1.10.1.1.1 in 3GPP TS 34.8.108 [5].6.4.4 DL:3.3-1: UTRA reference radio parameters and combinations Condition UTRA Speech Reference configuration TS 34. Table 4.4.4.1 Definitions See clause 8.8.108 subclause 6.2 in 3GPP TS 34.5. 4.1.4.523-1[18].4 DL:3.5.1 in 3GPP TS 34.1.2.4.2.108 [5].3 UTRA PS RB + Speech TS 34.4 kbps SRBs for DCCH Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB + UL:3.108 subclause 6.4.4-1: GERAN reference PDP context parameters Condition GPRS Reference configuration TS 51.10.1.401 [31]. Derivation of KASME and other E-UTRA Keys shall be as defined in Annex A of 3GPP TS 33. 4. 3GPP .1 Authentication and key derivation in the test USIM.1. 4.108 [5]. Ik. Compression is always turned off if nothing else is stated explicitly in the test case.010-1 subclause 40. Comment Test PDP context3 is the default Test PDP context which is used in the GERAN Inter-RAT GPRS test cases where no particular Test PDP contexts are specified.Release 12 370 3GPP TS 36.40 TS 34.10.9.1 (2014-12) Table 4.1. 102 [33] .4.Release 12 371 4. 4.103 [45].101 [32] and 3GPP TS 31.9. annex E. The settings of the elementary files at the MF and USIM ADF (Application DF) level resp.2.2 in 3GPP TS 34.g. GUTI in bytes 1 to 12) may be updated as a result of a tracking area update attempt by the UE. the ISIM ADF (Application DF) level are the same as section 8.229-1 Annex E [46] and 3GPP TS 34.2 Default parameters for the test USIM.2.1.108 [5].3. EFUST (USIM Service Table): Services Service n°15: Service n°16: Service n°85 Service n°87 Cell Broadcast Message Identifier Cell Broadcast Message Identifier Ranges EPS Mobility Management Information Call control on EPS PDN connection by USIM 3GPP Activated Optional Optional Yes No Version .108[5].9.3 Default settings for the Elementary Files (EFs) The format and coding of elementary files of the USIM are defined in 3GPP TS 31.3 Using the authentication test algorithm for UE conformance testing See clause 8.S0065-B [48]. section 4. in conjunction with byte 18 setting of "01".1.102 [23]. The TAC (bytes 16 to 17) is set to "FF FE" since this.229-3 Annex B.2. CSIM and ISIM Same as clause 8.1 (2014-12) Generation of re-synchronization parameters in the USIM.1 Modified contents of the USIM Elementary Files EFEPSLOCI (EPS location information) File size: 18 Bytes Default values: Bytes 1 to 12 (HEX): FF FF FF FF FF FF FF FF FF FF FF FF(GUTI) Bytes 13 to 17 (HEX): 42 F6 18 FF FE (Last visited registered TAI) Byte 18 (BIN): 00000001 (EPS update status = "not updated") Bytes 13 to 17: TAI-MCC = 246 (bytes 13 to 14) and TAI-MNC = 81 (byte 15) are frequently used.2.9.2 3GPP TS 36. EFEPSNSC (EPS NAS Security Context) The programming of this EF follows default parameter written in 3GPP TS 31. is used to ensure that the UE performs Attach at the beginning of a test. Bytes in this file (e.9. The settings of the elementary files at the CSIM ADF (Application DF) level as specified below.2 in 3GPP TS 34. Those of the CSIM are defined in 3GPP2 C.508 V12.3 in 3GPP TS 34.523-1 [18]. Those of the ISIM are defined in 3GPP TS 31.1.108 [5].1 [47] with the exceptions listed below. Note that some files may be updated by the UE based on information received from the SS.108 [5] resp. EFNASCONFIG (Non Access Stratum Configuration) File size: 28 Bytes Default values: Bytes 1 to 28 (HEX): FF FF … FF The programming of this EF follows the specific USIM requirements given in 3GPP TS 36. 4. 4. 4. CSIM and ISIM Same as clause 8.1 in 3GPP TS 34.101 [32] and 3GPP TS 31.3 in 3GPP TS 34.9.1. 9. Annex E. EFAH (Analog Home SID) The programming of this EF follows default parameter written in 3GPP2 C.1 (2014-12) Activated Optional EFCOUNT (Call Count) The programming of this EF follows default parameter written in 3GPP2 C.0 GHz PCS band)) 01 Record 3: Default values: Bytes 1 to 2 (HEX): E8 03 (CDMA Home SID (SIDp): 1000) Bytes 3 to 4 (HEX): AE 08 (CDMA Home NID (NIDp): 2222) Bytes 5 (HEX): (Band Class: 3 (832 to 925 MHz JTACS band)) 03 3GPP Version .S0065-B [48].4. EFIMSI_M (IMSI_M) The programming of this EF follows default parameter written in 3GPP2 C.Release 12 372 Services Service n°96 Non Access Stratum Configuration 4. Annex E. EFIMSI_T (IMSI_T) The programming of this EF follows default parameter written in 3GPP2 C. Annex E.508 V12. EFALOC (Analog Location and Registration Indicators) The programming of this EF is a test house option.S0065-B [48].2 Modified contents of the CSIM Elementary Files 3GPP TS 36. EFTMSI (TMSI) The programming of this EF follows default parameter written in 3GPP2 C.S0065-B [48]. Annex E.S0065-B [48]. NID) Record size: 5 Bytes Record count:6 Record 1: Default values: Bytes 1 to 2 (HEX): E8 03 (CDMA Home SID (SIDp): 1000) Bytes 3 to 4 (HEX): AE 08 (CDMA Home NID (NIDp): 2222) Bytes 5 (HEX): (Band Class: 0 (800 MHz cellular band)) 00 Record 2: Default values: Bytes 1 to 2 (HEX): E8 03 (CDMA Home SID (SIDp): 1000) Bytes 3 to 4 (HEX): AE 08 (CDMA Home NID (NIDp): 2222) Bytes 5 (HEX): (Band Class: 1 (1.3. EFCDMAHOME (CDMA Home SID. Annex E.S0065-B [48]. EFAOP (Analog Operational Parameters) The programming of this EF is a test house option.8 to 2. Annex E. Annex E.4. EFACCOLC (Access Overload Class ACCOLCp) The 4 LSB of this 1 byte file are der-bit access overload class indicator is derived from the last digit of the associated decimal representation of the IMSI_M vis decimal to binary conversion.S0065-B [48]. Bits 0 to 3 are derived from the last digit of the associated decimal representation of the IMSI_M via decimal to binary conversion. EFSNREGI (CDMA System-Network Registration Indicators) The programming of this EF is a test house option.87 GHz Korean PCS band)) 04 Record 5: Default values: Bytes 1 to 2 (HEX): E8 03 (CDMA Home SID (SIDp): 1000) Bytes 3 to 4 (HEX): AE 08 (CDMA Home NID (NIDp): 2222) Bytes 5 (HEX): (Band Class: 5 (450 MHz NMT band)) 05 Record 6: Default values: Bytes 1 to 2 (HEX): E8 03 (CDMA Home SID (SIDp): 1000) Bytes 3 to 4 (HEX): AE 08 (CDMA Home NID (NIDp): 2222) Bytes 5 (HEX): (Band Class: 6 (2 GHz IMT-2000 band)) 06 EFZNREGI (CDMA Zone-Based Registration Indicators) The programming of this EF follows default parameter written in 3GPP2 C. EFSSCI (Suggested Slot Cycle Index) The programming of this EF is a test house option. File size: 1 byte Default value: Bits 4 to 7 are reserved and set to ‘0000’.1 (2014-12) Record 4: Default values: Bytes 1 to 2 (HEX): E8 03 (CDMA Home SID (SIDp): 1000) Bytes 3 to 4 (HEX): AE 08 (CDMA Home NID (NIDp): 2222) Bytes 5 (HEX): (Band Class: 4 (1.Release 12 373 3GPP TS 36.75 to 1. EFPRL (Preferred Roaming List) File size: 18 Bytes Default values: Bytes 1 to 18 (HEX): 00 12 00 00 00 00 40 01 21 00 02 80 00 50 00 00 6E DB 3GPP . EFTERM (Call Termination Mode Preferences) The programming of this EF is a test house option.S0065-B [48]. EFDISTREGI (CDMA Distance-Based Registration Indicators) The programming of this EF follows default parameter written in 3GPP2 C.508 V12. EFACP (Analog Channel Preferences) The programming of this EF is a test house option. 1 (2014-12) The interpretation of the default values read as follows: PRL ID – 0 Preferred only – 0 Default roaming indication – 0 Number of Acquisition Records – 1 Number of system records – 1 EFRUIMID (Removable UIMID) This EF stores a 32-bit electronic identification number (ID) unique to the CSIM or a 32-bit pseudo-UIMID of the CSIM. Services Service n°1 : Service n°2 : Service n°3 : Service n°4 : Service n°5 : Service n°6: Service n°7: Service n°8: Service n°9: Service n°10: Service n°11: Service n°12: Service n°13: Service n°14: Service n°15: Service n°16: Service n°17: Service n°18: Service n°19: Service n°20: Service n°21: Service n°22: Service n°23: Service n°24: Service n°25: Service n°26: Service n°27: Service n°28: Service n°29: Service n°30: Service n°31: Service n°32: Service n°33: Service n°34: Service n°35: Service n°36: Service n°37: Service n°38: Service n°39: Service n°40: Service n°41: Service n°42: Local Phone Book Fixed Dialling Numbers (FDN) Extension 2 Service Dialling Numbers (SDN) Extension3 Short Message Storage Short Message Parameters (SMP) HRPD Service Category Program for BC-SMS CDMA Home Service Provider Name Data Download via SMS Broadcast (for CCAT) Data Download via SMS-PP (for CCAT) Call Control (for CCAT) 3GPD-SIP 3GPD-MIP AKA IP-based Location Services (LCS) BCMCS Multimedia Messaging Service (MMS) Extension 8 MMS User Connectivity Parameters Application Authentication Group Identifier Level 1 Group Identifier Level 2 De-Personalization Control Keys Cooperative Network List Outgoing Call Information (OCI) Incoming Call Information (ICI) Extension 5 Multimedia Storage Image (EFIMG) Enabled Services Table Capability Configuration Parameters (CCP) SF_EUIMID-based EUIMID Messaging and 3GPD Extensions Root Certificates WAP Browser Java Reserved for CDG Reserved for CDG IPv6 Proactive CSIM (for CCAT) 3GPP Activated Option Option Option Option Option Yes Yes Yes Option Yes Option Option Option Option Option Yes Option Option Option Option Option Option Option Option Option Option Option Option Option Option Option Yes Option Option Option Option Option Option No No Option Option Version . EFCSIM_ST (CSIM Service Table) Services will be allocated and activated as follows. It is specified by the CSIM manufacturer.4.Release 12 374 3GPP TS 36.508 V12. EFFDN (Fixed Dialling Numbers) The programming of this EF is a test house option.S0065-B [48].508 V12. Annex E.S0065-B [48]. EFSMSP (Short Message Service Parameters) Record size: 12 Bytes Record count: 1 Record 1: Default values: Bytes 1 to 23 (HEX): 00 02 10 02 5D FE FF FF 02 F5 FF FF FF FF FF FF FF FF 08 03 08 01 C0 The interpretation of the default values in this record read as follows: Teleservice Identifier: CDMA Cellular Messaging Teleservice [CMT-95] Parameter Indicators: MSG_ENCODING.Release 12 375 3GPP TS 36. Annex E. EFOTAPASPC (OTAPA/SPC_Enabled) The programming of this EF follows default parameter written in 3GPP2 C. EFOTA (OTASP/OTAPA Features) The programming of this EF is a test house option. EFNAMLOCK (NAM_LOCK) The programming of this EF is a test house option.S0065-B [48]. Annex E. EFLI (Language Indication) The programming of this EF is a test house option. EFESN_MEID_ME (ESN_ME or MEID_ME) The programming of this EF follows default parameter written in 3GPP2 C. EFSMS (Short Messages) The programming of this EF follows default parameter written in 3GPP2 C. Annex E. Validity Period.S0065-B [48].1 (2014-12) EFSPC (Service Programming Code) The programming of this EF follows default parameter written in 3GPP2 C. EFSP (Service Preferences) The programming of this EF is a test house option.4. Bearer Data Message Encoding: 7-bit ASCII Validity Period: Indefinite Bearer Data: Priority Indicator: Emergency 3GPP . 3GPP . EFME3GPDOPC (ME 3GPD Operation Capability) The programming of this EF follows default parameter written in 3GPP2 C. EFMAXPRL (Maximum PRL) The programming of this EF is a test house option.S0065-B [48]. EFSPCS (SPC Status) If EFSPC is set to default value of ’00 00 00’. Annex E. Annex E. Annex E.4.508 V12. otherwise it shall be set to ‘01’.S0065-B [48].S0065-B [48]. EFAD (Administrative Data) The programming of this EF follows default parameter written in 3GPP2 C.S0065-B [48]. Annex E. EFMDN (Mobile Directory Number) The programming of this EF is a test house option. then EFSPCS shall be set to ‘00’.1 (2014-12) EFSMSS (SMS Status) The programming of this EF follows default parameter written in 3GPP2 C. EFECC (Emergency Call Codes) The programming of this EF follows default parameter written in 3GPP2 C. EF3GPDOPM (3GPD Operation Mode) The programming of this EF is a test house option. EFSIPCAP (SimpleIP Capability Parameters) The programming of this EF is a test house option. EFSPN (CDMA Home Service Provider Name) File size: 35 Bytes Default values: Bytes 1 to 35 (HEX): 01 02 01 44 65 66 61 75 6C 74 20 53 65 72 76 69 63 65 20 50 72 6F 76 69 64 65 72 20 4E 61 6D 65 FF FF FF The interpretation of the default values read as follows: Display Condition: Display of registered system is required Character Encoding: 7-bit ASCII Language Indicator: 1 (English) Service Provider Name: “Default Service Provider Name” EFUSGIND (UIMID/SF_EUIMID Usage Indicator) The programming of this EF is a test house option. EFSSFC (Supplementary Services Feature Code Table) The programming of this EF is a test house option.Release 12 376 3GPP TS 36. EFMECRP (ME-specific Configuration Request Parameters) The programming of this EF follows default parameter written in 3GPP2 C. EFMIPSP (MobileIP Status Parameters) The programming of this EF is a test house option. EFHRPDCAP (HRPD Access Authentication Capability Parameters) File size: 3 Bytes Default values: Bytes 1 to 3 (HEX): 20 F8 80 The interpretation of the default values read as follows: Maximum NAI Length: 32 Maximum Length of Shared Secret: 31 Authentication Algorithms: PPP CHAP EFHRPDUPP (HRPD Access Authentication User Profile Parameters) File size: 14 Bytes Default values: Bytes 1 to 14 (HEX): 0D 0B 61 62 63 40 78 79 7A 2E 63 6F 6D 10 The interpretation of the default values read as follows: HRPD Profile NAI: “[email protected] [48]. EFSIPSP (SimpleIP Status Parameters) The programming of this EF is a test house option.Release 12 377 3GPP TS 36.508 V12. EFPUZL (Preferred User Zone List) The programming of this EF is a test house option. Annex E. EFSIPPAPSS (SimpleIP PAP SS Parameters) The programming of this EF is a test house option.1 (2014-12) EFMIPCAP (MobileIP Capability Parameters) The programming of this EF is a test house option.4. EFSIPUPP (SimpleIP User Profile Parameters) The programming of this EF is a test house option. EFMAXPUZL (Maximum PUZL) The programming of this EF is a test house option.com” HRPD Profile Authentication Algorithm: CHAP 3GPP . EFMIPUPP (MobileIP User Profile Parameters) The programming of this EF is a test house option. Band: 1. Type: MCC-MNC-based. Type: CDMA Generic.1 (2014-12) EFCSSPR (CUR_SSPR_P_REV) The programming of this EF follows default parameter written in 3GPP2 C. Roam Indicator: 0. Band: 6. Type: IS-856. EFEPRL (Extended Preferred Roaming List) File size: 129 Bytes Default values: Bytes 1 to 16 (HEX): 00 81 00 00 03 00 01 80 00 04 00 0A 04 01 64 03 Bytes 17 to 32 (HEX): 0B 0B 04 01 64 03 F5 0A 04 0A 58 08 19 0B 04 0A Bytes 33 to 48 (HEX): 58 0C 97 0A 02 31 13 0B 02 30 C8 71 C0 02 00 10 Bytes 49 to 64 (HEX): 1F 01 00 C8 FF FF 00 80 00 38 E0 08 00 00 80 00 Bytes 65 to 80 (HEX): 71 E0 12 00 10 1F 01 00 C8 FF FF 00 80 00 38 E0 Bytes 81 to 96 (HEX): 18 00 00 80 00 71 C0 22 00 10 1F 01 00 C8 FF FF Bytes 97 to 112 (HEX): 00 80 80 38 E0 28 00 00 80 80 71 E0 02 00 10 1F Bytes 113 to 128 (HEX):01 00 C8 FF FF 00 80 80 38 E0 08 00 00 80 80 2B Byte 129 (HEX): 6B The interpretation of the default values read as follows: PRL ID – 0 List Type: IS-683D Preferred only – 0 Default roaming indication – 0 Number of acquisition records – 6 - Index: 0. Subnet ID: /0. Subnet ID: MCC-MNC SID/NID. Association Tag: 0 - Acquisition Index: 5. Band: 6. Annex E. Type: HDR Generic Band: 0.4. Association Tag: 0 - Acquisition Index: 3. Type: IS-856. Association Tag: 1 - Acquisition Index: 1. Type: CDMA Generic. Roam Indicator: 0. Type: IS-856. SID: 200. Subnet ID: /0. NID: 65535100. EFATC (Access Terminal Class) The programming of this EF is a test house option. Subnet ID: /0. Band: 0. Type: HDR Generic. Channel: 275 - Index: 5. Association Tag: 1 - Acquisition Index: 0. Band: 1. Channel: 356 and 779 - Index: 1.Release 12 378 3GPP TS 36. Channel: 600 and 1175 - Index: 4. MNC: 01. Channel: 356 and 1013 - Index: 2. Roam Indicator: 0. Type: HDR Generic. Subnet ID: /0. MCC: 001. Association Tag: 0 3GPP .S0065-B [48]. Type: IS-856. Channel: 600 and 25 - Index: 3. Type: CDMA Generic.508 V12. Channel: 200 Number of records in the Common Subnet Table – 0 Number of system records – 8 - Acquisition Index: 1. Roam Indicator: 0. Roam Indicator: 0. MCC: 001. Higher Priority Search Time: 64 minutes.Release 12 379 3GPP TS 36. Roam Indicator: 0. Association Tag: 0 - Acquisition Index: 4. 3GPP . Subnet ID: MCC-MNC SID/NID.4. MNC: 01. Association Tag: 1 - Acquisition Index: 0. Roam Indicator: 0. Higher Priority Search Time: 64 minutes.S0065-B [48]. NID: 65535100. Subnet ID: MCC-MNC SID/NID. Roam Indicator: 0. Annex E. SID: 200. MNC: 01. System Priority: 1. Subnet ID: MCC-MNC SID/NID. Priority Class: Home + Preferred. Higher Priority Search Time: 64 minutes. MNC: 01. Type: MCC-MNC-based. MSPL Index: 1 EFMLPL (Multimode system selection Location associated Priority List) File size: 18 Bytes Default values: Bytes 1 to 18 (HEX): 00 09 01 00 01 01 01 00 01 FF FF FF FF FF FF FF FF FF The interpretation of the default values read as follows: Current MMSS_P_REV – 1 MSPL Version ID – 1 MSPL Block 1: MSPL Identification – 1. Network Capability Indicator: no Network CAP used - Index 2: System Type: cdma2000 HRPD. Location Parameter Type Value: default. System Priority: 1.508 V12. MCC: 001. Priority Class: Home Only. NID: 65535100. SID: 200. EFBCSMStable (Broadcast Short Message Table) The programming of this EF follows default parameter written in 3GPP2 C. Annex E. MCC: 001. Type: MCC-MNC-based. NID: 65535. Number of MSPL ID1 records – 3 - Index 1: System Type: EUTRA. Network Capability Indicator: no Network CAP used EFBCSMScfg (Broadcast Short Message Configuration) The programming of this EF is a test house option. EFBCSMSpref (Broadcast Short Message Preference) The programming of this EF follows default parameter written in 3GPP2 C. Type: MCC-MNC-based.1 (2014-12) - Acquisition Index: 2. SID: 200.S0065-B [48]. Priority Class: Any. System Priority: 1. Network Capability Indicator: no Network CAP used - Index 3: System Type: cdma2000 AI. Association Tag: 1 EFMSPL (Multimode system selection System Priority List) File size: 18 Bytes Default values: Bytes 1 to 18 (HEX): 00 0F 01 00 01 01 01 03 07 08 02 0C 00 3E 00 FF FF FF The interpretation of the default values read as follows: Current MMSS_P_REV – 1 MLPL Version ID – 1 MLPL Identification – 1 Number of MLPL Records – 1 - Index: 1. 4. EFMMSICP (MMS Issuer Connectivity Parameters) The programming of this EF follows default parameter written in 3GPP2 C.1 (2014-12) EFBCSMSP (Broadcast Short Message Parameter) The programming of this EF follows default parameter written in 3GPP2 C.S0065-B [48].S0065-B [48]. EFCDMACNL (CDMA Co-operative Network List) The programming of this EF is a test house option.508 V12. Annex E. 3GPP .S0065-B [48]. Annex E.S0065-B [48]. EFEXT8 (Extension 8) The programming of this EF follows default parameter written in 3GPP2 C.S0065-B [48]. Annex E.S0065-B [48]. EFMMSUP (MMS User Preferences) The programming of this EF follows default parameter written in 3GPP2 C. EFBAKPARA (Currently used BAK Parameters) The programming of this EF is a test house option. EFMMSN (MMS Notification) The programming of this EF follows default parameter written in 3GPP2 C.S0065-B [48]. Annex E. EFHOME_TAG (Home System Tag) The programming of this EF is a test house option. Annex E. EFAuthCapability (Authentication Capability) The programming of this EF follows default parameter written in 3GPP2 C. EFMMSUCP (MMS User Connectivity Parameters) The programming of this EF follows default parameter written in 3GPP2 C. EFGID1 (Group Identifier Level 1) The programming of this EF is a test house option. Annex E. EFUpBAKPARA (Updated BAK Parameters) The programming of this EF is a test house option. EFDCK (De-Personalization Control Keys) The programming of this EF is a test house option. EF3GCIK (3G Cipher and Integrity Keys) The programming of this EF is a test house option.Release 12 380 3GPP TS 36. Annex E. EFGID2 (Group Identifier Level 2) The programming of this EF is a test house option. 508 V12.Release 12 381 EFGROUP_TAG (Group Tag List) The programming of this EF is a test house option.1 (2014-12) . EFSF_EUIMID (Short FormEUIMID) Specified by CSIM Manufacturer. EFEXT3(Extension3) The programming of this EF is a test house option. EFLCSCP (LCS Connectivity Parameter) The programming of this EF is a test house option. 3GPP 3GPP TS 36. EFHiddenKey (Key for hidden phone book entries) The programming of this EF is a test house option. EFOCI (Outgoing Call Information) The programming of this EF is a test house option. EFEXT5 (Extension 5) The programming of this EF is a test house option. EFSDN (Service Dialling Numbers) The programming of this EF is a test house option. EFSPECIFIC_TAG (Specific Tag List) The programming of this EF is a test house option. EFCALL_PROMPT (Call Prompt List) The programming of this EF is a test house option. EFEXT2(Extension2) The programming of this EF is a test house option. EFEST (Enabled Service Table) The programming of this EF is a test house option.4. EFCCP2 (Capability Configuration Parameters 2) The programming of this EF is a test house option. EFICI (Incoming Call Information) The programming of this EF is a test house option. EFLCSVER (LCS Protocol Version) The programming of this EF is a test house option. Annex E.S0065-B [48]. EFSMSCAP (SMS Capabilities) File size: 4 Bytes Default values: Bytes 1 to 4 (HEX): 3C 08 07 01 The interpretation of the default values read as follows: SMS Retry Period: 60 seconds SMS Retry Interval: 8 seconds SMS Flags: Send On Access: True Send on Traffic: True Send as Standard EMS: True SMS Preferred Service Option: SO 6 EFMIPFlags (MobileIP Flags) The programming of this EF is a test house option. EFWAPBrowserCP (WAP Browser Connectivity Parameters) The programming of this EF is a test house option. EFRC (Root Certificates) The programming of this EF is a test house option. EFTCPConfig (TCp Configurations) The programming of this EF is a test house option. EFDGC (Data Generic Configurations) The programming of this EF is a test house option.4. EFWAPBrowserBM (WAP Browser Bookmarks) The programming of this EF follows default parameter written in 3GPP2 C. Annex E. EFIPV6CAP (IPv6 Capabilities) The programming of this EF is a test house option. 3GPP .508 V12.Release 12 382 3GPP TS 36.S0065-B [48].1 (2014-12) EFAppLabels (Application Labels) The programming of this EF is a test house option. EFModel (Device Model Information) The programming of this EF follows default parameter written in 3GPP2 C. EF3GPDUPPExt (3GPD User Profile Parameters Extension) The programming of this EF is a test house option. 4.508 V12. 3GPP 3GPP TS 36.Release 12 383 EFMMSConfig (MMS Configuration) The programming of this EF is a test house option.1 (2014-12) . EFJDL (Java Download URL) The programming of this EF is a test house option.