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-2Part 2: Abstract test suitePD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardiz
2、ation Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-National forewordThis Published Document is the UK implementation of CEN ISO/TS 16401-2:2012.The UK participation in its preparation was entrusted to Technical CommitteeEPL/
3、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 include all the necessary provisions of acontract. Users are responsible for its correct application. The British Standards Institutio
4、n 2012Published by BSI Standards Limited 2012ISBN 978 0 580 71836 6ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under the authority of theStandards Policy and Strategy Committee on 31 March 2012.Amendmen
5、ts issued since publicationAmd. No. Date Text affectedPUBLISHED DOCUMENTPD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TECHNICAL SPECIFICATION SPCIFICA
6、TION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN ISO/TS 16401-2 March 2012 ICS 35.240.60; 03.220.20 English Version Electronic fee collection - Evaluation of equipment for conformity to ISO/TS 17575-2 - Part 2: Abstract test suite (ISO/TS 16401-2:2012) Perception du tlpage - valuation de conformit de lqu
7、ipement lISO/TS 17575-2 - Partie 2: Suite dessai abstraite (ISO 16401-2:2012) Elektronische Gebhrenerhebung - Konformittsevaluierung von Einrichtungen nach CEN ISO/TS 17575-2 - Teil 2: Abstrakte Prfreihe (ISO 16401-2:2012) This Technical Specification (CEN/TS) was approved by CEN on 30 January 2012
8、for provisional application. The period of 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 t
9、o announce the existence of this CEN/TS in 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 conversio
10、n of the CEN/TS into an EN is reached. CEN 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
11、, Portugal, Romania, Slovakia, Slovenia, 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 an
12、d by any means reserved worldwide for CEN national Members. Ref. No. CEN ISO/TS 16401-2:2012: EPD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-CEN ISO/T
13、S 16401-2:2012 (E) 2 Contents Page Foreword 3PD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-CEN ISO/TS 16401-2:2012 (E) 3 Foreword This document (CEN I
14、SO/TS 16401-2:2012) has been prepared by Technical Committee CEN/TC 278 “Road transport 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 eleme
15、nts of this document may be the subject of patent rights. CEN and/or CENELEC shall 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 Tech
16、nical Specification: 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, Spain, Sweden, Switzerland
17、, Turkey and the United Kingdom. PD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Reference numberISO/TS 16401-2:2012(E)ISO 2012TECHNICAL SPECIFICATION I
18、SO/TS16401-2First edition2012-03-01Electronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-2 Part 2: Abstract test suite Perception du tlpage valuation de conformit de lquipement lISO/TS 17575-2 Partie 2: Suite dessai abstraite PD CEN ISO/TS 16401-2:2012Copyright European Co
19、mmittee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/TS 16401-2:2012(E) ISO 2012 All rights reserved iiiContents Page Introduction . v 1 Scope 1 2 Normative references 1 3 Terms and definitions . 1 4
20、Abbreviations . 2 5 Abstract Test Method (ATM). 3 5.1 Implementations Under Tests 3 5.1.1 Front-End (FE) . 3 5.1.2 Back-End (BE) 3 5.2 Test architecture 3 5.3 Protocol Implementation Extra Information for Testing (PIXIT) . 3 6 Untestable Test Purposes (TP) 3 7 ATS data structures 4 7.1 Implementatio
21、n of proposed in annex D.2. API Definition in C 4 7.2 Common data types 4 8 External functions . 4 9 Message filtering . 4 10 ATS naming conventions . 4 10.1 Definition naming conventions 5 10.2 Test Case identifier . 6 10.3 TTCN-3 modules identifier 6 Annex A (informative) TTCN-3 Library modules fo
22、r FE and BE . 7 Annex B (informative) PIXIT Proforma for FE and BE . 8 Bibliography 10 PD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/TS 16401-2:20
23、12(E) ISO 2012 All rights reserved vIntroduction This part of ISO/TS 16401 is part of a set of 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 infrastruc
24、ture. Within the suite of EFC standards this conformance evaluation procedure defines the process and tests for conformity evaluation of Front End and Back End that comply with the requirements in ISO/TS 17575-2. This part of ISO/TS 16401 is intended to assess Front End Communications API and Front
25、End Application capabilities, assess Front End Communications API and Front End Application behaviour, serve as a guide for Front End Communications API and Front End Application conformance evaluation and type approval, achieve comparability between the results of the corresponding tests applied in
26、 different places at different times, and facilitate communications between parties. This part of ISO/TS 16401 is based on ISO/TS 17575-2, and the ISO/IEC 9646 family of standards on conformance test methodology. PD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by
27、IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TECHNICAL SPECIFICATION ISO/TS 16401-2:2012(E) ISO 2012 All rights reserved 1Electronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-2 Part 2: Abstract test suite 1 S
28、cope This part of ISO/TS 16401 specifies the Abstract Test Suite (ATS) to evaluate the conformity of Front End Communications API and Front End Application to ISO/TS 17575-2. The objective of the present document is to provide a basis for conformance tests for Front End Communications API and Front
29、End Application in Electronic Fee Collection based on autonomous on-board equipment (OBE) to enable interoperability between different equipment supplied by different manufacturers. The present abstract test suite is directly derived from ISO/TS 17575-2. 2 Normative references The following referenc
30、ed documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/TS 17575-1, Electronic fee collection Application interface definit
31、ion for autonomous systems Part 1: Charging ISO/TS 17575-2, Electronic fee collection Application interface definition for autonomous systems Part 2: Communication and connection to the lower layers ISO/TS 17575-3, Electronic fee collection Application interface definition for autonomous systems Par
32、t 3: Context data 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/TS 17575-1 and the following apply. 3.1 conformance testing testing the extent to which an IUT is a conforming implementation ISO/IEC 9646-1, definition 3.3.23 3.2 contract expression
33、of an agreement between two or more parties concerning the use of the road infrastructure ISO 14906:2011, definition 3.7 NOTE A contract specifies obligations, permissions and prohibitions for the objects involved. PD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided b
34、y IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/TS 16401-2:2012(E) 2 ISO 2012 All rights reserved3.3 Front End application part of the Front End above the API ISO/TS 16401-1:2011, definition 3.2 3.4 implementation under test IUT impl
35、ementation of one or more OS1 protocols in an adjacent user/provider relationship, being that part of a real open system which is to be studied by testing ISO/IEC 9646-1, definition 3.3.43 3.5 service provider operator that accepts the users payment means and in return provides a road-use service to
36、 the user NOTE Taken from ISO 14906:2004. 3.6 system under test SUT real open system in which the IUT resides ISO/IEC 9646-1, definition 3.3.103 3.7 test case an abstract or executable test case ISO/IEC 9646-1, definition 3.3.107 3.8 toll charger legal entity charging toll for vehicles in a toll dom
37、ain ISO/TS 17574:2009, definition 3.27 4 Abbreviations For the purposes of this document, the abbreviations given in ISO/TS 16401-1 and the following apply. EUT Equipment Under Test IUT Implementation Under Test PIXIT Protocol Implementation Extra Information for Testing SCS Semiconductor Characteri
38、zation System SUT System Under Test TC Test Case PD CEN ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/TS 16401-2:2012(E) ISO 2012 All rights reserved 35
39、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 data for an individual user are collected, processed and delivered to the Back End. The
40、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 architecture The implementation under test is either the FE or the BE. The System under test co
41、mprises 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. The figure below describes the test architecture. Communication Sub-layerTTCN-3Test exec
42、utionTESTER SYSTEM UNDER TESTIUTTS 17575-2(FE or BE)eaPort pcoFigure 1 Test system architecture 5.3 Protocol Implementation Extra Information for Testing (PIXIT) The supplier of the Front End and Back End, respectively, is responsible for providing a Protocol Implementation Extra Information for Tes
43、ting (PIXIT). The supplier of the Front End and the Back End shall complete a PIXIT; see Annex B for the proforma. 6 Untestable Test 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. PD CEN
44、 ISO/TS 16401-2:2012Copyright European Committee for Standardization Provided by IHS under license with CENNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ISO/TS 16401-2:2012(E) 4 ISO 2012 All rights reservedTable 1 Untestable TPs Test purpose Reason(empty) (empty)
45、 NOTE Currently no untestable TPs have been identified. 7 ATS data structures 7.1 Implementation of proposed in annex D.2. API Definition in C The ATS is based on an API definition as depicted in ISO/TS 17575-2, D.2: A function call is implemented as a sent message. The template message used match t
46、he C function signature and the C data structures defined in D.2 The return function call is implemented as a received message The template message used match the C function signature The call-backs are implemented by as received message The template message used match the C call-back signature 7.2
47、Common data types They are reduced to an enumerate structure of communication functions error code as depicted in ISO/TS 17575-2, Annex D. 8 External functions No external functions are used. 9 Message filtering As depicted in ISO/TS 17575-2, D.2, each call-back event is ignored by default. Thus, ea
48、ch a receive cal back event statement was added in the default behaviour, to ignore it 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_instanceStateChange_any) repeat; / Ignore state transition 10 ATS naming conventions The ATS naming conventions are intended to provide an easier reading of the ATS by using
