ETSI TS V7.1.0 ( ) Technical Specification

Transcription

1 TS V7.1.0 ( ) Technical Specification Universal Mobile Telecommunications System (UMTS); User Equipment (UE) conformance specification; Part 3: Abstract test suites (ATSs) (3GPP TS version Release 7)

2 1 TS V7.1.0 ( ) Reference RTS/TSGR v710 Keywords UMTS 650 Route des Lucioles F Sophia Antipolis Cedex - FRANCE Tel.: Fax: Siret N NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on printers of the PDF version kept on a specific network drive within Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other documents is available at If you find errors in the present document, please send your comment to one of the following services: 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. European Telecommunications Standards Institute All rights reserved. DECT TM, PLUGTESTS TM, UMTS TM, TIPHON TM, the TIPHON logo and the logo are Trade Marks of registered for the benefit of its Members. 3GPP TM is a Trade Mark of registered for the benefit of its Members and of the 3GPP Organizational Partners.

3 2 TS V7.1.0 ( ) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to. The information pertaining to these essential IPRs, if any, is publicly available for members and non-members, and can be found in SR : "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to in respect of standards", which is available from the Secretariat. Latest updates are available on the Web server ( Pursuant to the IPR Policy, no investigation, including IPR searches, has been carried out by. No guarantee can be given as to the existence of other IPRs not referenced in SR (or the updates on the Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding deliverables. The cross reference between GSM, UMTS, 3GPP and identities can be found under

4 3 TS V7.1.0 ( ) Contents Intellectual Property Rights...2 Foreword...2 Foreword...13 Introduction Scope References Definitions and abbreviations Definitions Abbreviations Requirements on the TTCN development ATS structure Modularity Module structure Contents of the modules Example of a working platform Test method and testing architecture Test method Testing architecture Lower Tester (LT) Configuration and initialization Upper Tester (UT) TTCN Model extension Multiplexing of RLC services NAS test method and architecture Test configuration Routing UL NAS massages in SS RRC and RAB test method and architecture Test configuration RAB test method Sending data on the same TTI Sending continuous data on consecutive TTIs RLC test method and architecture Testing architecture Test method Handling SUFIs in TTCN Void SMS test method and architecture SMS CS test method and architecture SMS PS test method and architecture SMS Cell broadcasting test method and architecture MAC test method and architecture Testing architecture Test method Abnormal decoding situations MAC_es/e test method (Rel-6 or later) BMC test method and architecture BMC test architecture BMC test method PDCP test PDCP test architecture...39

5 4 TS V7.1.0 ( ) PDCP test method Multi-RAT Handover Test Model Overview ASP function description Identities Cell configuration and control L1 (GERAN) configuration and control Basic physical channel configuration Multislot configuration for circuit or packet switched channels Frame in the near future L1 header L2 configuration and control Don't response to some handover access bursts No UA reply to SABM System Information sending Paging Generic procedures for GPRS signalling GPRS generic attach procedures and ciphering mode control Cell change order within a TBF Generic configuration procedure for GSM ciphering mode control L H bits convention and bit padding in DL GERAN DL RLC/MAC message bit padding GSM DL message spare padding L H convention in rest octets of GSM DL messages Spare Bits GSM System Information messages on SACCH GSM Measurement Information messages on SACCH DCH-DSCH model (R99 or Rel-4) DCH with HS-DSCH (MAC-hs) model (FDD, Rel-5 or later) a DCH with HS-DSCH model for 1.28 Mcps TDD (Rel-5 or later) b DCH with HS-DSCH (MAC-ehs) model (FDD, Rel-7 or later) c HS-DSCH (MAC-hs/ehs) model (FDD, Rel-7 or later)(no DCH Associated) E-DCH model (Rel-6 or later) MBMS model (Rel-6 or later) MBMS RLC test model RLC test model for MTCH test RLC test model for MCCH test PCO and ASP definitions NAS PCO and ASP definitions NAS PCO Definitions Primitives used at Dc PCO Ut PCO and ASP definitions Ut PCO Declarations Primitives used at Ut PCO RRC PCO and ASP definitions AM/UM/TM PCO and ASP definitions SAP and PCO for data transmission and reception Control PCO and ASP SAP and PCO for control primitives transmission and reception Control ASP CPHY_AICH_AckModeSet CPHY_Cell_Config CPHY_Cell_Release a CPHY_Cell_TimingAdjust b CPHY_Detect_TFCI CPHY_Ini CPHY_Cell_TxPower_Modify CPHY_Frame_Number a CPHY_SFN (Rel-6 or later) b CPHY_MBMS_MICH_q (Rel-6 or later) c CPHY_MBMS_NI (Rel-6 or later)...76

6 5 TS V7.1.0 ( ) CPHY_Out_of_Sync CPHY_PRACH_Measurement CPHY_RL_Modify CPHY_RL_Release CPHY_RL_Setup CPHY_Sync a CPHY_HS_DPCCH_AckNack (Rel-5 or later) b CPHY_HS_DPCCH_CQI (Rel-5 or later) c CPHY_HS_DSCH_CRC_Mode (Rel-5 or later) CPHY_TrCH_Config a CPHY_UL_PowerModify CPHY_TrCH_Release CMAC_BMC_Scheduling CMAC_Ciphering_Activate a CMAC_FACH_MeasOccas CMAC_Config a CMAC_MAChs_MACehs_TFRCconfigure (Rel-5 or later) aa CMAC _MACehs_HS_SCCH_Orders (Rel-5 or later) b CMAC_MACe_Config (Rel-6 or later) c CMAC_MACe_NodeB_CellMapping (Rel-6 or later) d CMAC_MACes_Config (Rel-6 or later) e CMAC_MACe_AG (Rel-6 or later) f CMAC_MACe_AckNack (Rel-6 or later) g CMAC_MACe_E_TFC_Restriction (Rel-6 or later) h CMAC_MACe_RG (Rel-6 or later) ha CMAC_MACe_Bind_Grant_Tx (Rel-7 or later) i CMAC_MACes_SI_IND j CMAC_MACes_SI_Config (Rel-6 or later) k CMAC_MBMS_ConfigInfo (Rel-6 or later) CMAC_PAGING_Config CMAC_Restriction CMAC_SecurityMode_Config CMAC_SequenceNumber CMAC_SYSINFO_Config a CRLC_Bind_TestData_TTI b CRLC_BindTestDataInOneMAChs_MACehs_PDU (Rel-5 or later) CRLC_Ciphering_Activate CRLC_Config CRLC_Integrity_Activate CRLC_Integrity_Failure a CRLC_MAC_I_Mode b CRLC_NotAckNxtRxSDU c CRLC_ProhibitRLC_Ack CRLC_Resume a CRLC_RRC_MessageSN CRLC_SecurityMode_Config a CRLC_SetRRC_MessageSN b CRLC_Set_Count_I CRLC_SequenceNumber a CRLC_SendContinuousData_TTI CRLC_Status CRLC_Suspend a CRLC_MTCH_Scheduling (Rel-6 or later) CBMC_Config b DEC_PERbitstring c ENC_PERbitstring RLC_TR_DATA RLC_AM_DATA a RLC_UM_ACCESSinfo (Rel-6 or later) b RLC_UM_CriticalMCCHMsg (Rel-6 or later) c RLC_TR_SeqOfRlcPdus RLC_UM_DATA...139

7 6 TS V7.1.0 ( ) a RLC_UM_MSCH_Msg (Rel-6 or later) RLC_TR_MACesDATA_IND (Rel-6 or later) Specific ASP and IE definitions for 1.28 Mcps TDD (Rel-4 or later) Specific ASP definitions Specific IE definitions TTCN primitives UTRAN TTCN primitives GERAN PCO and ASP definitions PCO Type definitions PCO type for data transmission and reception in GERAN PCO type for configuration and control in GERAN PCO definitions PCOs for data transmission and reception in GERAN PCOs for control primitives transmission and reception in GERAN GERAN ASP Definitions ASPs for data transmission and reception in GERAN ASPs for control primitive transmission and reception in GERAN A-GPS Upper tester, PCO and ASP definitions Upper tester SV PCO A-GPS Primitives Control ASP Data ASP ROHC test model and ASP ROHC test method ASP and PCO for control primitives transmission and reception PCO definition CPDCP_Config CPDCP_ComProtocolControl ASP and PCO for data transmission and reception PCO definition PDCP_DATA PDCP_DL_FeedBack Handling RLP for CS non-transparent data UTRAN cell GERAN cell ASP and PCO for control primitives ASP and PCO for data transmission and reception Design Considerations Channel mapping Channel and RB identity Physical channels Transport channels Support of Default Configurations Logical Channels Radio bearers Scrambling and channelization codes MAC-d MAC-d configuration examples Configuration of compressed mode UE Side SS Side Use of U-RNTI and C-RNTI Channels configurations Configuration of Cell_FACH Configuration of Cell_DCH_StandAloneSRB Configuration of Cell_DCH_Speech Configuration of Cell_DCH_64kCS_RAB_SRB Configuration of Cell_DCH_57_6kCS_RAB_SRB Configuration of Cell_RLC_DCH_RAB Configuration of Cell_FACH_BMC...215

8 7 TS V7.1.0 ( ) Configuration of PS Cell_DCH_64kPS_RAB_SRB and Cell_PDCP_AM_RAB Configuration of Cell_Two_DTCH Configuration of Cell_Single_DTCH (CS) Configuration of PS Cell_PDCP_UM_RAB Configuration of PS Cell_PDCP_AM_UM_RAB Configuration of Cell_2SCCPCH_BMC Configuration of Cell_Four_DTCH_CS_PS, Cell_Four_DTCH_PS_CS Configuration of Cell_Two_DTCH_CS_PS, Cell_Two_DTCH_PS_CS Configuration of Cell_Four_DTCH_CS Configuration of Cell_DCH_MAC_SRB Configuration of Cell_FACH_MAC_SRB Configuration of Cell_FACH_MAC_SRB Configuration of Cell_FACH_2SCCPCH_StandAlonePCH Configuration of PS Cell_DCH_2AM_PS Configuration of PS Cell_DCH_2_PS_Call Configuration of Cell_FACH_3_SCCPCH_4_FACH_Cnfg Configuration of Cell_FACH_3_SCCPCH_4_FACH_Cnfg Configuration of Cell_FACH_3_SCCPCH_3_FACH_CTCH Configuration of PS Cell_DCH_DSCH_PS_RAB Configuration of Cell_DCH_DSCH_CS_PS Configuration of Cell_FACH_2SCCPCH_StandAlonePCH_2a Configuration of Cell_FACH_3_SCCPCH_4_FACH_2a_Cnfg Configuration of Cell_FACH_3_SCCPCH_4_FACH_2a_Cnfg Configuration of Cell_FACH_3_SCCPCH_3_FACH_CTCH_2a Configuration of Cell_DCH_HS_DSCH (Rel-5 or later) Configuration of cell_one_dtch_hs_dsch_mac (Rel-5 or later) a Configuration of cell_three_dtch_1q_hs_dsch_mac (Rel-7 or later) b Configuration of cell_three_dtch_3q_hs_dsch_mac (Rel-7 or later) c Configuration of Cell_E_HS_SRB_MAC_TM_RAB (Rel-7 or later) Configuration of Cell_2UM_3AM_DCH_HS_DSCH (Rel-5 or later) Configuration of Cell_DCH_Speech_WAMR (Rel-5 or later) Configuration of PS Cell_Four_DTCH_HS_CS and Cell_Four_DTCH_CS_HS (Rel-5 or later) Configuration of PS Cell_Two_DTCH_HS_CS (Rel-5 or later) Configuration of PS Cell_DCH_64kPS_RAB_SRB_HS (Rel-5 or later) Configuration of PS Cell_DCH_2AM_HS_DSCH (Rel-5 or later) Configuration of Cell_Three_DTCH_5SRB (Rel-5 or later) Configuration of Cell_Five_DTCH_CS_HS (Rel-5 or later) Configuration of Cell_DCH_E_HS (Rel-6 or later) Configuration of Cell_DCH_dlSRB_E_HS (Rel-6 or later) Configuration of Cell_E_HS (Rel-6 or later) Configuration of PS Cell_Four_DTCH_E_HS_CS and Cell_Four_DTCH_CS_E_HS (Rel-6 or later) Configuration of Cell_2DCH_2AM_dlSRB_E_HS (Rel-6 or later) Configuration of Cell_E_HS_MAC_TM_RAB (Rel-6 or later) Configuration of Cell_2DCH_MAC_2TM_dlSRB_E_HS (Rel-6 or later) Configuration of Cell_2DCH_1AM_1UM_E_HS (Rel-6 or later) Configuration of Cell_3DCH_2AM_1UM_E_HS (Rel-6 or later) Configuration of Cell_Four_DTCH_CS_E_HS_5SRB (Rel-6 or later) Configuration of Cell_Four_DTCH_HS_5SRB (Rel-5 or later) Configuration of Cell_E_HS_StandAloneSRB/ Cell_E_HS_StandAloneSRB_NoConn (Rel-6 or later) MBMS channel configuration (Rel-6 or later) Configuration cell_mbms_mcch (Rel-6 or later) Configuration cell_mbms_mcch_one_mtch (Rel-6 or later) Configuration of PS Cell_DCH_64kPS_AM_RAB Configuration of PS Cell_MBMS_PTPRB Configuration of PS Cell_MBMS_PTPRB_AM Configuration of Cell_FACH_MCCH_SRB / Cell_FACH_MCCH_NoDedicated Configuration of Cell_DCH_MCCH_PS Configuration of PS Cell_DCH_1AM_2AM_HS_DSCH (Rel-6 or later) System information blocks scheduling Grouping SIBs for testing SIB configurations...261

9 8 TS V7.1.0 ( ) Test SIB default schedule Test SIB schedule for idle mode, measurement and Inter-RAT UTRAN to GERAN test cases Test SIB special schedule Test SIB schedule for two S-CCPCH or two PRACH Test SIB schedule for Inter-Rat Handover from GERAN to UTRAN Test Handling the transmission of SIB Delivery of System Information content Scheduling of system Information blocks Example of usage Security in testing Authentication Ciphering Integrity Test security scenarios Start security function Start integrity protection without start of ciphering Start both integrity protection and ciphering Void RB setup AM / UM RB TM RB RB Reconfiguration for AM RAB modification of RLC size "RB mapping info" in CELL UPDATE CONFIRM "RB mapping info" in RB RECONFIGURATION / RELEASE Security modification Integrity started, ciphering not started Integrity and ciphering started SRNS relocation Void Presence of "Integrity protection mode info" but absence of "Ciphering mode info" Presence of "Integrity protection mode info" and "Ciphering mode info" IE CELL/URA update RLC re-establish (RB2, RB3, RB4) RLC re-establish (RAB) Inter RAT handover to UTRAN ciphering has not been activated ciphering has been activated Hard handover Test USIM configurations Test USIM for Idle mode tests Downlink power setting in SS Test suite operation definitions Test suite operation definitions in the common modules Specific test suite operation for RLC defined in BasicM Pseudocode in a C like notation Specific test suite operation definitions for Multi RAT Handover testing Specific test suite operation for Multi RAB testing Specific test suite operation for InterSystem Handover testing Specific test suite operation for RAB_HS testing Specific test suite operation for Intersystem HS Testing Specific test suite operation for A-GPS testing Specific test suite operation for E-DCH Testing Specific test suite operation for E-DCH/HS-ENH and MBMS testing AT commands AT command lists in ATSs AT commands in IR_U ATS: AT commands in MAC and RLC ATS: AT commands in NAS ATS: AT commands in RAB ATS: AT commands in RRC ATS: AT commands SMS ATS: AT commands in HSDPA ATS (Rel-5 or later):...314

10 9 TS V7.1.0 ( ) AT commands for E-DCH testing (Rel-6 or later) and HS-ENH testing (Rel-7 or later) AT Command Handling in TTCN AT Command Interface AT Command Dialogues AT Response Types 'OK' Response Name String Error strings AT Command Parameters And Options Bit padding Requirements for implementation Test PDP contexts Mapping of Quality of service and AT command for HSDPA testing Mapping of Quality of service and AT command for E-DCH testing DCH-DSCH Configurations a DCH with HS-DSCH Configurations (Rel-5 or later) aa HS-DSCH Configurations without DCH associated (Rel-6 or later) b HS-DSCH Configuration Verification c HS-DSCH Configurations for enhanced Cell FACH (Rel-7 or later) [Mapping CCCH/BCCH/PCCH on HS-DSCH] Pre- and postambles for GERAN to UTRAN tests Preamble for GERAN to UTRAN tests Postamble for GERAN to UTRAN tests GERAN to UTRAN handover in CS GERAN to UTRAN cell change in PS (in PMM-CONNECTED) GERAN to UTRAN DTM test cases E-DCH configurations (Rel-6 or later) DPCH (SRB) and E-DCH (RAB) configuration Serving E-DCH cell SHO - addition of E-DCH RL in a serving RL cell (intra node B) SHO addition of E-DCH RL in a non-serving RL cell (inter node B) DPCH/HS-DSCH/E-DCH setup and release order Serving E-DCH cell with UL DTX Configured [Rel-7] Guidelines of MBMS implementations MCCH scheduling implementation MSCH scheduling and service data on MTCH Scheduled service data on MTCH without MSCH configured Cell mapping Annex A (normative): Abstract Test Suites (ATS) A.1 Version of specifications A.2 NAS ATS A.2.1 Void A.2.2 The TTCN Machine Processable form (TTCN.MP) A.3 SMS ATS A.3.1 Void A.3.2 The TTCN Machine Processable form (TTCN.MP) A.4 RRC ATS A.4.1 Void A.4.2 The TTCN Machine Processable form (TTCN.MP) A.5 RLC ATS A.5.1 Void A.5.2 The TTCN Machine Processable form (TTCN.MP) A.6 MAC ATS A.6.1 Void A.6.2 The TTCN Machine Processable form (TTCN.MP) A.7 BMC ATS...350

11 10 TS V7.1.0 ( ) A.7.1 Void A.7.2 The TTCN Machine Processable form (TTCN.MP) A.8 PDCP ATS A.8.1 Void A.8.2 The TTCN Machine Processable form (TTCN.MP) A.9 RAB ATS A.9.1 Void A.9.2 The TTCN Machine Processable form (TTCN.MP) A.10 IR_U ATS A.10.1 Void A.10.2 The TTCN Machine Processable form (TTCN.MP) A.11 AGPS ATS A.11.1 Void A.11.2 The TTCN Machine Processable form (TTCN.MP) A.12 HSD_ENH ATS A.12.1 Void A.12.2 The TTCN Machine Processable form (TTCN.MP) A.13 HSU_ENH ATS A.13.1 Void A.13.2 The TTCN Machine Processable form (TTCN.MP) A.14 MBMS ATS A.14.2 The TTCN Machine Processable form (TTCN.MP) Annex B (normative): Partial IXIT proforma B.0 Introduction B.1 Parameter values B.1.1 BasicM test suite parameter declarations B.1.2 L3M test suite parameters declarations B.1.3 NAS test suite parameters declarations B.1.4 SMS test suite parameters declarations B.1.5 RRC_M test suite parameters declarations B.1.6 PDCP test suite parameters declarations B.1.7 BMC test suite parameters declarations B.1.8 RRC test suite parameters declarations B.1.9 RAB test suite parameters declarations B.1.10 RLC and MAC test suite parameters declarations B.1.11 Multi RAT test suite parameters declarations B.1.12 MMI questions B.1.13 A-GPS test suite parameters declarations B.1.14 HSD_ENH test suite parameters declarations B.1.15 HSU_ENH test suite parameters declarations B.1.16 HS_ENH test suite parameters declarations Annex C (informative): Additional information to IXIT C.1 Identification Summary C.2 Abstract Test Suite Summary C.3 Test Laboratory C.3.1 Test Laboratory Identification C.3.2 Accreditation status of the test service C.3.3 Manager of Test Laboratory C.3.4 Contact person of Test Laboratory C.3.5 Means of Testing C.3.6 Instructions for Completion C.4 Client...384

12 11 TS V7.1.0 ( ) C.4.1 Client Identification C.4.2 Client Test Manager C.4.3 Client Contact person C.4.4 Test Facilities Required C.5 System Under Test C.5.1 SUT Information C.5.2 Limitations of the SUT C.5.3 Environmental Conditions C.6 Ancillary Protocols C.6.1 Ancillary Protocols C.6.2 Ancillary Protocols Annex D (informative): PCTR Proforma Annex E (informative): TTCN style guide for 3GPP ATS E.1 Introduction E.2 ETR 141 rules and applicability E.2.1 Multiple words are separated by upper case letters at the start of each word E.2.2 Identifiers shall be protocol standard aligned E.2.3 Identifiers shall be distinguishing (use of prefixes) E.2.4 Identifiers should not be too long (use standard abbreviations) E.2.5 Test suite operations must not use global data E.3 3GPP ATS implementation guidelines E.3.1 Test case groups shall reflect the TSS&TP document E.3.2 Test case names correspond to the clause number in the prose E.3.3 Use standard template for test case and test step header E.3.4 Do not use identical tags in nested CHOICE constructions E.3.5 Incorrect usage of enumerations E.3.6 Structured type as OCTETSTRING should not be used E.3.7 Wildcards in PDU constraints for structured types should not be used E.3.8 TSOs should be passed as many parameters as meaningful to facilitate their implementation E.3.9 Specification of Encoding rules and variation should be indicated E.3.10 Use of global data should be limited E.3.11 Limit ATS scope to a single layer / sub-layer E.3.12 Place system information in specially designed data structures E.3.13 Place channel configuration in specially designed data structures E.3.14 PICS / PIXIT parameters E.3.15 Dynamic vs. static choices E.3.16 Definition of Pre-Ambles and Post Ambles E.3.17 Use test steps to encapsulate AT and MMI commands E.3.18 Use system failure guard timers E.3.19 Mapping between prose specification and individual test cases E.3.20 Verdict assignment E General E Test cases E Test steps E Defaults E.3.21 Test suite and test case variables E.3.22 Use of macros is forbidden E.3.23 Support for future Radio Access Technologies E.3.24 Managing multiple representations of the same information E Predefined types E Simple types E Structured types E Conversion responsibility E Option 1: Calling party conversions E Advantages E Disadvantages E Option 2: Called party conversions...413

13 12 TS V7.1.0 ( ) E Advantages E Disadvantages E.3.25 Assignment using constraint E.3.26 Guidelines for use of timers when tolerances are applicable E Specific situations E Example situations E Example of situation E Example of situation E Example of situation Annex F (informative): Void Annex G (informative): Recommendation of an unique ICS/IXIT electronic exchange format G.1 Syntax G.2 Examples Annex H (informative): A-GPS ASN.1 module Annex I (Informative): Guidance on test execution I.1 Void I.2 FDD test execution on different frequency bands I.2.1 FDD Band VI, XIII, XIV I.2.2 FDD Band XII I.3 Void I.4 InterRAT test execution Annex J (informative): Change history History...468

14 13 TS V7.1.0 ( ) Foreword This Technical Specification has been produced by the 3 rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 3 of a multi-part conformance test specification for UE. The specification contains a TTCN2 design frame work and the detailed test specifications in TTCN for UE at the Uu interface. 3GPP TS [1]: "User Equipment (UE) conformance specification; Part 1: Protocol conformance specification". 3GPP TS [2]: "User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification". 3GPP TS : "Abstract Test Suite (ATS)" (the present document).

15 14 TS V7.1.0 ( ) 1 Scope The present document specifies the protocol conformance testing in TTCN for the 3GPP User Equipment (UE) at the Uu interface. The present document is the 3 rd part of a multi-part test specification, 3GPP TS The following TTCN test specification and design considerations can be found in the present document: - the overall test suite structure; - the testing architecture; - the test methods and PCO definitions; - the test configurations; - the design principles, assumptions, and used interfaces to the TTCN tester (System Simulator); - TTCN styles and conventions; - the partial PIXIT proforma; - the TTCN.MP and TTCN.GR forms for the mentioned protocols tests. The Abstract Test Suites designed in the document are based on the test cases specified in prose (3GPP TS [1]). The present document is valid for UE implemented according to 3GPP Release 1999, 3GPP Release 4, 3GPP Release 5, 3GPP Release 6 or 3GPP Release 7. 2 References The following documents contain provisions, which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. - For a Release 1999 UE, references to 3GPP documents are to version 3.x.y, when available. - For a Release 4 UE, references to 3GPP documents are to version 4.x.y, when available. - For a Release 5 UE, references to 3GPP documents are to version 5.x.y, when available. - For a Release 6 UE, references to 3GPP documents are to version 6.x.y, when available. - For a Release 7 UE, references to 3GPP documents are to version 7.x.y, when available. [1] 3GPP TS : "User Equipment (UE) conformance specification; Part 1: Protocol conformance specification". [2] 3GPP TS : "User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) proforma specification". [3] 3GPP TS : "Common test environments for User Equipment (UE) conformance testing". [4] 3GPP TS : "Terminal logical test interface; Special conformance testing functions".

16 15 TS V7.1.0 ( ) [5] 3GPP TR : "Vocabulary for 3GPP specifications". [6] 3GPP TS : "Numbering, addressing and identification". [7] 3GPP TS : "General UMTS architecture". [8] 3GPP TS : "Mobile radio interface signalling layer 3; General aspects". [9] 3GPP TS : "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". [10] 3GPP TS : "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [11] 3GPP TS : "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". [12] 3GPP TS : "Physical layer procedures (FDD)". [13] 3GPP TS : "Physical layer procedures (TDD)". [14] 3GPP TS : "Radio interface protocol architecture". [15] 3GPP TS : "Interlayer procedures in connected mode". [16] 3GPP TS : "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode". [16a] 3GPP TS : "UE Radio Access capabilities" [17] 3GPP TS : "Medium Access Control (MAC) protocol specification". [18] 3GPP TS : "Radio Link Control (RLC) protocol specification". [19] 3GPP TS : "Packet Data Convergence Protocol (PDCP) specification". [20] 3GPP TS : "Broadcast/Multicast Control (BMC)". [21] 3GPP TS : "Radio Resource Control (RRC) protocol specification". [22] 3GPP TS : "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE-DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". [23] 3GPP TS : "AT command set for 3G User Equipment (UE)". [24] 3GPP TS : "Packet domain; Mobile Station (MS) supporting Packet Switched services". [25] 3GPP TS : "3G security; Security architecture". [26] 3GPP TS : "Mobile Station (MS) conformance specification; Part 1: Conformance specification". [27] TR (V1.0.0): "Information technology; Open Systems Interconnection Conformance testing methodology and framework; The Tree and Tabular Combined Notation (TTCN) (Ed. 2++)". [28] ITU-T Recommendation X.691 (1997) "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". [29] ISO/IEC 8824 (all parts): "Information technology - Abstract Syntax Notation One (ASN.1)". [30] IETF RFC 2507: "IP Header Compression". [31] 3GPP TS : "Multiplexing and multiple access on the radio path". 3GPP TS 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path".

17 16 TS V7.1.0 ( ) [32] 3GPP TS : "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". 3GPP TS 04.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". [33] 3GPP TS : "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification". [34] 3GPP TS : "Alphabets and language-specific information". [35] 3GPP TS : "Technical realization of Short Message Service (SMS)". [36] 3GPP TS : "Technical realization of Cell Broadcast Service (CBS)". [37] ETR 141: "Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; The Tree and Tabular Combined Notation (TTCN) style guide". [38] TR : "Methods for Testing and Specification (MTS); TTCN interim version including ASN support [ISO/IEC ] (Second Edition Mock-up for JTC1/SC21 Review)". [39] ITU-T Recommendation X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". [40] 3GPP TS : "Physical channels and mapping of transport channels onto physical channels (FDD)". [41] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework". [42] 3GPP TS : "Mobile Station - Base Stations System (MS - BSS) Interface Data Link (DL) layer specification". [43] 3GPP TS : "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". 3GPP TS 04.18: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". [44] 3GPP TR : "Radio interface for Broadcast/Multicast Services". [45] ITU-T Recommendation O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate". [46] IETF RFC 1144: "Compressing TCP/IP headers for low-speed serial links". [47] ITU-T Recommendation V.42bis: "Data compression procedures for data circuit-terminating equipment (DCE) using error correction procedures". [48] ITU-T Recommendation V.44: "Data compression procedures". [49] 3GPP TS : "Mobile radio interface layer 3 specification". 3GPP TS 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [50] 3GPP TS : "Mobile radio interface layer 3 supplementary services specification; Formats and coding". [51] 3GPP TS : "Mobile Application Part (MAP) specification". [52] ITU-T Recommendation Q.773: "Signalling System No. 7 - Transaction Capabilities Formats and Encoding". [53] ITU-T Recommendation X.880: "Information Technology - Remote Operations: Concepts, Model and Notation".

18 17 TS V7.1.0 ( ) [54] IETF RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed". [55] 3GPP TS : "Radio Link Protocol (RLP) for circuit switched bearer and teleservices". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS [1] apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS [1], 3GPP TS [9], 3GPP TS [21] and TR [27] apply. 4 Requirements on the TTCN development A number of requirements are identified for the development and production of TTCN specification for 3GPP UE at Uu interface. 1. Top-down design, following 3GPP TS [1], 3GPP TS [3] and 3GPP TS [4]. 2. A unique testing architecture and test method for testing all protocol layers of UE. 3. Uniform TTCN style and naming conventions. 4. Improve TTCN readability. 5. Using TTCN-2++ (TR [27]) for R99, Release 4, Release 5 and Release-6, avoid the use of the TTCN 2 features TTCN 3 does not support. 6. TTCN specification feasible, implementable and compilable. 7. Test cases shall be designed in a way for easily adaptable, upwards compatible with the evolution of the 3GPP core specifications and the future Releases. 8. The test declarations, data structures and data values shall be largely reusable. 9. Modularity and modular working method. 10. NAS ATS should be designed being independent from the radio access technologies. 11. Minimizing the requirements of intelligence on the emulators of the lower testers. Especially the functionality of the RRC emulator in the TTCN tester should be reduced and simplified, the behaviours should be standardized as the TTCN RRC test steps in the TTCN modular library. 12. Giving enough design freedom to the test equipment manufacturers. 13. Maximizing reuse of ASN.1 definitions from the relevant core specifications. In order to fulfil these requirements and to ensure the investment of the test equipment manufacturers having a stable testing architecture for a relatively long period, a unique testing architecture and test method are applied to the 3GPP UE protocol tests.

19 18 TS V7.1.0 ( ) 5 ATS structure The total TTCN specification for the UE testing is structured in a number of separate layered ATSs. The number of ATS being produced corresponds to the number of the 3GPP core specifications referred. The separation of ATSs reduces the size of ATSs. The layer-specific test preambles and test data can be confined to one test suite and parallel development of test suites can be facilitated. The separation of ATSs enables also easily to follow the evolution of the core specifications. - NAS ATSs: 1) GSM MAP L3 ATS including MM, CC, GMM, SM test groups; 2) SMS ATS; 3) A-GPS ATS - AS ATSs: 1) RRC ATS including Singlecell and multicell test group; 2) RLC ATS; 3) MAC ATS; 4) BMC ATS; 5) PDCP ATS; 6) RAB ATS; 7) IR_U ATS; 8) HSD_ENH ATS (Rel-5 or later); 9) HSU_ENH ATS (Rel-6 or later); 10) MBMS ATS (Rel-6 or later); 11) HS-ENH ATS (Rel-7 or later). 5.1 Modularity The modular TTCN approach is used for the development of the 3GPP ATS specification work. Three modules, BasicM, RRC_M and L3M are installed.

20 19 TS V7.1.0 ( ) Module structure The module structure is shown in figure 1. PDCP TS MAC TS RLC TS BMC TS NAS TS A-GPS TS MBMS HSD_ENH/ HSU_ENH/ HS-ENH IR_U/G RRC TS SMS TS RAB TS TS PDCP MAC RLC BMC MM CC SM GMM A-GPS RRC NAS RAB MAC RLC RRC RAB NAS MAC IR_U / G Meas8.3.4 & 8.4 Idle mode RRC_81 RRC_82_83 SMS RAB MBMS_M HSDPA_M/ HSUPA_M/ R7_M NAS_M M_RAT_HO_GERAN_M RRC_M L3M BasicM Figure 1: Module structure

21 20 TS V7.1.0 ( ) The BasicM (Basic Module) is a minimum module commonly for the layer 2 and layer 3 testing. The L3M (Layer 3 Module) contains all the items to be shared by the RRC, NAS, SMS, RAB, IR_U/G, A-GPS, HSD_ENH, HSU_ENH and MBMS ATSs. NAS is applied to the NAS, A-GPS, HSD_ENH, HSU_ENH, MBMS ATSs and HS_ENH. The RRC_M is a module containing common object for RRC, RAB, IR_U/G, SMS, A-GPS, HSD_ENH, HSU_ENH, MBMS ATSs and HS_ENH.

22 21 TS V7.1.0 ( ) Contents of the modules The BasicM module includes objects related to the RRC, the layer 2 and the physical layer. It includes also all test steps needed by the layer 2 and layer 3 test cases for configurations and all objects related to the definition of the steps: - Common test steps and default test steps defined as generic procedures in 3GPP TS [3]; - RRC declarations related to the steps: types, timers, PDU types, ASP type, PCOs, TSOs, constants; - Related ICS and IXIT parameters needed for testing and respectively defined in 3GPP TS [2] and the present document; - Defaults constraints based on the default message contents defined in 3GPP TS [3]; - MMI PCO and ASPs; - All TTCN objects related to the SS configuration, e.g. PCOs, declaration of the components. The L3M module includes the NAS configuration steps and all related TTCN objects: - Common test steps and default test steps defined as generic procedures in 3GPP TS [3]; - NAS declarations related to these steps: types, PDU, ASP, PCOs, TSOs, constants; - Related ICS and IXIT parameters needed for testing and respectively defined in 3GPP TS [2] and the present document; - Default constraints based on the default message contents defined in 3GPP TS [3]. The RRC_M module includes the RRC steps common to RRC and RAB test cases and all related TTCN objects Example of a working platform Figure 2 shows the working platform for the user that is writing the SMS test cases. SMS RRC_M Legend Dependency Import L3M Module BasicM Modular test suite ASN.1 file declarations Figure 2: An example of working platform for SMS

23 22 TS V7.1.0 ( ) 6 Test method and testing architecture 6.1 Test method The distributed single party test method is used for the UE testing. The lower tester configures the emulator and communicates with the UE under test via the emulator. An upper tester interfaces UE as (E)MMI. All common parts in 3GPP TS [3], 3GPP TS [4] and 3GPP TS [2] are developed in a TTCN library including the declarations, default constraints, preambles and postambles. They have the following characteristics: - Very complex; - Worked in different layers; - Including data representing the radio parameters for SS setting and the data representing the UE capabilities (PICS parameters); - Including the generic procedures to bring the UE into certain test states or a test mode (C-plane); - Setting RABs at U-plane and SRBs in C-plane; - Being used by every test cases no matter which layer the test case belongs to; - No affect on the test verdict of PASS or FAIL. The layer-specific test cases have the characteristics: - relatively simple and straight forward; - having narrow test scope and test purposes; - test scenarios in a single layer (one PCO); - assigning the test verdict.

24 23 TS V7.1.0 ( ) 6.2 Testing architecture A unique testing architecture is shown in figure 3. CC, MM, SM, GMM SMS RRC RLC MAC BMC PDCP RAB IR_U/G A-GPS HSD_ENH HSU_ENH MBMS TTCN test cases PCO UT UT EMMI, AT coms PHY Dc PCO RRC Direct Transfer RLC MAC AM/UM/TM PCOs LT PCO CRLC PCO CMAC PCO CPHY UE (SUT) Figure 3: A unique testing architecture Lower Tester (LT) The Lower Tester (LT) provides the test means for the execution of the test cases for CC, SM, MM, GMM, SMS, RRC, RLC, MAC, PDCP, BMC, RAB, IR_U/G, A-GPS, HSD_ENH, HSU_ENH, MBMS and HS_ENH. The LT provides also the RLC, MAC and PHY emulators to communicate with the UE. The configuration and initialization of the emulators are control by the TTCN via ASPs Configuration and initialization A number of TTCN test steps are designed for the generic setting. 1) Configuration of L1 of the tester, such as the cells, Physical channels and common transport channels via CPHY- PCO, configuration of MAC via CMAC-PCO and configuration of RLC layer via CRLC-PCO. 2) Sending system information via TR-PCO. 3) Establishment RRC connection via AM or UM-PCO. 4) Assigning a radio bearer via AM-PCO. 5) MM /GMM registration via Dc-PCO. 6) Establishment of a CS call or a PDP context via Dc-PCO. 7) Setting security parameters and control of integrity via CRLC- and ciphering via CRLC- and CMAC-PCO.

25 24 TS V7.1.0 ( ) Upper Tester (UT) An Upper Tester (UT) exists in the test system. The UT interfaces toward UE with any optional EMMI (3GPP TS [4], clause 7). TTCN communicates with the UT by passing coordination primitives via a Ut PCO. The primitives can either contain AT commands aiming at the automatic tests, or some informal commands as MMI, in order to request the UE for certain actions and to provide simple means for observations of UE TTCN TTCN is used as specification language based on TR [27] (TTCN 2++). The importation of ASN.1 modules and modular TTCN are two of the most important features used in the design of the ATSs. The TTCN test suites have been designed to maximize the portability from the language TTCN 2 to TTCN Model extension If a test case needs to handle a concurrent situation two or more LTs can be configured at the same time. The following test scenarios identified may require multiple testers in the test configuration Multiplexing of RLC services For the RRC and NAS testing, the TTCN RRC test steps (on RB1 and RB2) and the RRC emulator (on RB3 and RB4 for the NAS messages) share the same service access point (AM SAP). The RLC emulator shall provide separate message queues (buffers) for the TTCN RRC test steps and the RRC emulator for the TTCN NAS test cases, according to the signalling radio bearer identities. 6.3 NAS test method and architecture Test configuration The NAS test method is shown in figure 4. Upper Tester e.g. MMI, EMMI commands Actions UE UT PCO NAS TTCN RRC Direct Transfer RLC MAC Physical A/I Dc PCO AM UM TM PCOs CRLC PCO CMAC PCO CPHY PCO NAS (IUT) RRC RLC MAC Figure 4: NAS testing architecture The single layer distributed test method is used.

26 25 TS V7.1.0 ( ) The Point of Control and Observation (PCO) are defined as the Dc (Dedicated control) SAP. The NAS test verdicts are assigned depending on the behaviours observed at the PCO. The TTCN tester provides the NAS TTCN test cases and steps with a simple RRC direct transfer function which buffers the NAS PDU data, converts the data from the NAS TTCN table format into ASN.1, or in reverse way, and delivers all lower layer services of AM-SAP for RB3 and RB4. The NAS TTCN test cases make also intensively use of the RRC TTCN test steps, in order to: - Configure, initialize and control the L2 emulator; - Initialize the UE for testing. The RRC test steps, which are called by the NAS test cases or steps, interface with the RLC PCOs (UM, AM and TR), the control PCOs CRLC, CMAC and CPHY. The General control (Gc) SAP and the Notification (Nt) SAP are not applied. Messages exchanged via these SAPs will be replaced with the corresponding RRC TTCN test steps. The Ut PCO (so called logical interface [4]) is served as the interface to the UE EMMI to allow a remote control of operations, which have to be performed during execution of a test case such as to switch the UE on/off, initiate a call, etc Routing UL NAS massages in SS The UL NAS messages are embedded in RRC messages INITIAL / UL DIRECT TRANSFER. In the UE test, the received UL NAS messages can either be routed to the Dc PCO and verified at the NAS message level, or routed to AM PCO and verified at the RRC message level. 1) RBid =3 at the SS side indicates that the UL NAS high priority messages to be routed to Dc PCO. RB3 applies to RRC_DataInd/Req. 2) RBid= -16 at the SS side indicates the received messages to be routed to RLC AM PCO. RB-16 applies to RLC_DataInd/Req. The RB3 and RB-16 do not coexist. The TTCN writer uses the MAC and RLC reconfigurations to re-map the RB and the corresponding logical channels. If RB3 has been configured, but a test case needs to re-map the logical channel from RB3 to RB-16 the following way is to replace RB3 with RB CMAC_CONFIG_REQ (reconfiguration, RB-16). Re-mapping on RB-16 which appears in the transport channel and logical channel mapping list. - CRLC_CONFIG_REQ (reconfiguration, RB-16). RB-16 appears in the routing info, in order to replace the original mapping on RB3. Mapping from RB-16 to RB3 is done in the reverse way.