EN ISO TS 16407-2-2012 en Electronic fee collection - Evaluation of equipment for conformity to ISO TS 17575-1 - Part 2 Abstract test suite《电子收费 符合ISO TS 17575 1的设备评估 第2部分 抽象测试集》.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationElectronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-1Part 2: Abstract test suitePD CEN ISO/TS 16407-2:2012National forewordThis Published Document is

2、 the UK implementation of CEN ISO/TS 16407-2:2012.The UK participation in its preparation was entrusted to Technical CommitteeEPL/278, Road transport informatics.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to incl

3、ude all the necessary provisions of acontract. Users are responsible for its correct application. The British Standards Institution 2012Published by BSI Standards Limited 2012ISBN 978 0 580 71834 2ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations

4、.This Published Document was published under the authority of theStandards Policy and Strategy Committee on 30 April 2012.Amendments issued since publicationAmd. No. Date Text affectedPUBLISHED DOCUMENTPD CEN ISO/TS 16407-2:2012TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION

5、CEN ISO/TS 16407-2 March 2012 ICS 35.240.60; 03.220.20 English Version Electronic fee collection - Evaluation of equipment for conformity to ISO/TS 17575-1 - Part 2: Abstract test suite (ISO 16407-2:2012) Perception de tlpage - Evaluation de conformit de lquipement lISO/TS 17575-1 - Partie 2: Suite

6、de test abstraite (ISO 16407-2:2012) Elektronische Gebhrenerhebung - Konformittsevaluierung von Einrichtungen nach CEN ISO/TS 17575-1 - Teil 2: Abstrakte Prfreihe (ISO 16407-2:2012) This Technical Specification (CEN/TS) was approved by CEN on 30 January 2012 for provisional application. The period o

7、f validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard. CEN members are required to announce the existence of this CEN/TS i

8、n the same way as for an EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached. CE

9、N members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia,

10、Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2012 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN

11、 national Members. Ref. No. CEN ISO/TS 16407-2:2012: EPD CEN ISO/TS 16407-2:2012CEN ISO/TS 16407-2:2012 (E) 2 Contents Page Foreword 3PD CEN ISO/TS 16407-2:2012CEN ISO/TS 16407-2:2012 (E) 3 Foreword This document (CEN ISO/TS 16407-2:2012) has been prepared by Technical Committee CEN/TC 278 “Road tra

12、nsport and traffic telematics“, the secretariat of which is held by NEN, in collaboration with Technical Committee ISO/TC 204 “Intelligent transport systems“. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shal

13、l not be held responsible for identifying any or all such patent rights. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic,

14、 Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. PD CEN ISO/TS 16407-2:2012ISO/TS 16407-2:2012(E)

15、 ISO 2012 All rights reserved iiiContents Page Introduction . v 1 Scope 1 2 Normative references 1 3 Terms and definitions . 1 4 Abbreviations . 2 5 Abstract Test Method (ATM) 2 5.1 Implementations Under Tests 2 5.2 Test architecture 2 5.3 Protocol Implementation Extra Information for Testing (PIXIT

16、) . 3 6 Untestable Test Purposes (TP) 3 7 ATS data structures 3 7.1 ASN.1 description 3 8 External functions . 4 8.1 Functions for communications 4 8.2 Functions for timing 4 9 Message filtering . 5 10 ATS naming conventions . 5 10.1 Definition naming conventions 5 10.2 Test Case identifier . 7 10.3

17、 TTCN-3 modules identifier 7 Annex A (normative) TTCN-3 Library modules for FE and BE . 8 Annex B (informative) PIXIT Proforma for FE and BE . 9 Bibliography 11 PD CEN ISO/TS 16407-2:2012ISO/TS 16407-2:2012(E) ISO 2012 All rights reserved vIntroduction This part of ISO/IEC 16407 is part of a set of

18、standards that supports interoperability of autonomous EFC-systems, which includes ISO/TS 17575 parts 1 to 4 that define the EFC context data, their charge reports and their use of communication infrastructure. Within the suite of EFC standards, this conformance evaluation procedure defines the proc

19、ess and tests for conformity evaluation of Front End and Back End that comply with the requirements in ISO/TS 17575-1. This part of ISO/IEC 16407 is intended to assess Front End and Back End capabilities, assess Front End and Back End behaviour, serve as a guide for Front End and Back End conformanc

20、e evaluation and type approval, achieve comparability between the results of the corresponding tests applied in different places at different times, and facilitate communications between parties. This part of ISO/IEC 16407 is based on ISO/TS 17575-1, and the ISO/IEC 9646 family of standards on confo

21、rmance test methodology. PD CEN ISO/TS 16407-2:2012TECHNICAL SPECIFICATION ISO/TS 16407-2:2012(E) ISO 2012 All rights reserved 1Electronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-1 Part 2: Abstract test suite 1 Scope This part of ISO/IEC 16407 specifies the Abstract Tes

22、t Suite (ATS) to evaluate the conformity of Front End and Back End to ISO/TS 17575-1. The objective of this part of ISO/IEC 16407 is to provide a basis for conformance tests for the Front End and the Back End in Electronic Fee Collection to enable interoperability between different equipment supplie

23、d by different manufacturers. The present abstract test suite is directly derived from ISO/TS 17575-1. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the l

24、atest edition of the referenced document (including any amendments) applies. ISO/TS 17575-1, Electronic fee collection Application interface definition for autonomous systems Part 1: Charging 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 co

25、nformance testing testing the extent to which an IUT is a conforming implementation ISO/IEC 9646-1:1994, definition 3.3.23 3.2 implementation under test an implementation of one or more OS1 protocols in an adjacent user/provider relationship, being that part of a real open system which is to be stud

26、ied by testing ISO/IEC 9646-1:1994, definition 3.3.43 3.3 system under test the real open system in which the IUT resides ISO/IEC 9646-1:1994, definition 3.3.103 PD CEN ISO/TS 16407-2:2012ISO/TS 16407-2:2012(E) 2 ISO 2012 All rights reserved3.4 test case an abstract or executable test case ISO/IEC 9

27、646-1:1994, definition 3.3.107 4 Abbreviations For the purposes of this document, the following abbreviations apply, unless otherwise specified. BE Back End DUT Device Under Test EUT Equipment Under Test FE Front End IUT Implementation under test PIXIT Protocol Implementation Extra Information for T

28、esting SCS Semiconductor Characterization System SUT System under test TC Test case 5 Abstract Test Method (ATM) This clause describes the ATM used to test the layers at the FE side and at the BE side. 5.1 Implementations Under Tests 5.1.1 Front-End (FE) The part(s) of the toll system where usage da

29、ta for an individual user are collected, processed and delivered to the Back End. The Front End comprises the on-board equipment and optionally a proxy. 5.1.2 Back-End (BE) Generic name for the computing and communication facilities of the Service Provider and/or the Toll Charger. 5.2 Test architect

30、ure The implementation under test is either the FE or the BE. The System under test comprises also the communication sub-layer, which is necessary to perform the IUT tests. The tester executes the TTCN-3 test cases of the present Test Specification, running on an emulated communication sub-layer. PD

31、 CEN ISO/TS 16407-2:2012ISO/TS 16407-2:2012(E) ISO 2012 All rights reserved 3The figure below describes the test architecture. Upper Tester Communication Sub-layer TTCN-3 Test execution TESTER SYSTEM UNDER TEST IUT (FE/BE) eaPort pco Figure 1 Test system architecture 5.3 Protocol Implementation Extr

32、a Information for Testing (PIXIT) The supplier of the Front End and Back End, respectively, is responsible for providing a Protocol Implementation Extra Information for Testing (PIXIT). The supplier of the Front End and the Back End shall complete a PIXIT; see Annex B for a proforma. 6 Untestable Te

33、st Purposes (TP) This clause gives a list of TPs which are not implemented in the Abstract Test Suite due to the chosen Abstract Test Method or other restrictions. Table 1 Untestable TPs Test purpose Reason (empty) (empty) NOTE Currently no untestable TPs have been identified. 7 ATS data structures

34、7.1 ASN.1 description The ATS is based on the following ASN.1 description: ContextDataModule: it provides the ASN.1 description for ContextData, including Iso17575-3 ADU descriptions ChargingModule: it provides the ASN.1 description for charging support, including ChargeReport and ChargeReportRespon

35、se PD CEN ISO/TS 16407-2:2012ISO/TS 16407-2:2012(E) 4 ISO 2012 All rights reserved EfcModule: it provides the ASN.1 description for dedicated short-range communication CccModule: it provides the ASN.1 description for Radio Communication between Road-side Equipment and Onboard Equipment DSRCModule: i

36、t provides the ASN.1 description for dedicated short-range communication AVIAEINumberingAndDataStructures: it provides the ASN.1 description for Automatic vehicle and equipment identification 8 External functions All external functions are part of the common TTCN-3 source code. 8.1 Functions for com

37、munications The two following external functions are defined to initialize the communication stack as described in ISO/TS 17575-2. These functions are called during preamble (initialization) and postamble (termination) processing. Table 2 Communication initialization functions Nbr Computation Role 1

38、 fx_com_Initialize() These function initializes the communication stack 2 fx_com_DeInitialize() These function de-initializes the communication stack 8.2 Functions for timing The two following external functions are defined to support time functionality. Table 3 Communication initialization function

39、s Nbr Computation Role 1 fx_getCurrentTime() This function provides the current local time when this function is called 2 fx_addCurrentTimeOffset() This function add the offset to the current local time when this function is called PD CEN ISO/TS 16407-2:2012ISO/TS 16407-2:2012(E) ISO 2012 All rights

40、 reserved 59 Message filtering As indicated in the relevant TSS and TP document, Electronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-1 Part 1: Test suite structure and test purpose clause A.1.1, the ADUs exchanged between the IUT and the tester, which are not part of the

41、 test purpose, shall be ignored. Thus, a receive event statement was added in the default behaviour, to ignore messages received on the “pco” port, which have a valid ADU structure and were not handled in the test case behaviour. The corresponding TTCN-3 code is as following: pco.receive(mw_Iso17575

42、_3Adu_default) repeat; / Ignore ADU 10 ATS naming conventions The ATS naming conventions are intended to provide an easier reading of the ATS by using rules for naming objects. 10.1 Definition naming conventions To define the ATS naming conventions, the following principle are taken into considerati

43、on: Prefixes are short alphabetic string indicating the type of TTCN-3 element it represents (see table 4 below). Suffixes should not be used except in those specific cases identified in table 4 below. Prefixes and suffixes should be separated from the body of the identifier with an underscore (“_“)

44、. EXAMPLE 1 c_sixteen, t_wait_max. Only module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. The start of second and subsequent words in an identifier

45、should be indicated by capitalizing the first character. Underscores should not be used for this purpose. EXAMPLE 2 f_compareDateAndTime. The table 4 below specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix, suffixes (if any) and capitalization.

46、 Table 4 TTCN-3 naming convention Language element Naming convention Prefix Suffix Example Notes Module Use upper-case initial letter none none ContextData_TE TSS grouping Use all upper-case letters none none TP_RT_PS_TR Item group within a module Use upper-case initial letter none none Valid_Behavi

47、our PD CEN ISO/TS 16407-2:2012ISO/TS 16407-2:2012(E) 6 ISO 2012 All rights reservedData type Use upper-case initial letter none none ChargeReport List type identifiers Use upper-case initial letter none none TimeClassesGroups Message template Use lower-case initial letter m_ none m_Iso17575_3Adu Mes

48、sage template with wildcard or matching expression Use lower-case initial letters mw_ none mw_Iso17575_3Adu_default Port instance Use lower-case initial letter none none pco External function Use lower-case initial letter fx_ none fx_getCurrentTime() Constant Use lower-case initial letter c_ none c_

49、attr_11 Function Use lower-case initial letter f_ none f_authentication() Altstep Use lower-case initial letter a_ none a_receiveContextData() Altstep (Default) Use lower-case initial letter d_ none d_ADU_filter () Variable Use lower-case initial letter v_ none v_idx Timer Use lower-case initial letter t_ _min _maxt_wait Note 1Module parameters PICS values PIXIT values Use all upper case letters none none PIC_time PX_ORGINATOR_RECIPIENT Note 2Par