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:2012National forewordThis Published Document is
2、 the UK implementation of CEN ISO/TS 16401-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 71836 6ICS 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 31 March 2012.Amendments issued since publicationAmd. No. Date Text affectedPUBLISHED DOCUMENTPD CEN ISO/TS 16401-2:2012TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION
5、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 lquipement lISO/TS 17575-2 - Partie 2: Suit
6、e 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 for provisional application. The period
7、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 to announce the existence of this CEN/TS
8、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 conversion of the CEN/TS into an EN is reached. C
9、EN 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 CE
11、N national Members. Ref. No. CEN ISO/TS 16401-2:2012: EPD CEN ISO/TS 16401-2:2012CEN ISO/TS 16401-2:2012 (E) 2 Contents Page Foreword 3PD CEN ISO/TS 16401-2:2012CEN ISO/TS 16401-2:2012 (E) 3 Foreword This document (CEN ISO/TS 16401-2:2012) has been prepared by Technical Committee CEN/TC 278 “Road tr
12、ansport 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 sha
13、ll 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 16401-2:2012Reference numberISO/T
15、S 16401-2:2012(E)ISO 2012TECHNICAL SPECIFICATION ISO/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 abstrai
16、te PD CEN ISO/TS 16401-2:2012ISO/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 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-
17、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 Implementation of proposed in annex D.2. API Definition in C 4 7.2 Common data types 4 8 External functions . 4 9 Message filtering .
18、 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 for FE and BE . 7 Annex B (informative) PIXIT Proforma for FE and BE . 8 Bibliography 10 PD CEN ISO/TS 16401-2:2012ISO/TS
19、16401-2:2012(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
20、infrastructure. 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
21、and Front 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
22、applied in 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:2012TECHNICAL SPECIFICATION ISO/TS 16401-2:2012(E) ISO
23、2012 All rights reserved 1Electronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-2 Part 2: Abstract test suite 1 Scope 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 I
24、SO/TS 17575-2. The objective of the present document is to provide a basis for conformance tests for Front End Communications API and Front End Application in Electronic Fee Collection based on autonomous on-board equipment (OBE) to enable interoperability between different equipment supplied by dif
25、ferent manufacturers. The present abstract test suite is directly derived from ISO/TS 17575-2. 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 latest ed
26、ition of the referenced document (including any amendments) applies. ISO/TS 17575-1, Electronic fee collection Application interface definition for autonomous systems Part 1: Charging ISO/TS 17575-2, Electronic fee collection Application interface definition for autonomous systems Part 2: Communicat
27、ion and connection to the lower layers ISO/TS 17575-3, Electronic fee collection Application interface definition for autonomous systems Part 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 conf
28、ormance testing testing the extent to which an IUT is a conforming implementation ISO/IEC 9646-1, definition 3.3.23 3.2 contract expression 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,
29、permissions and prohibitions for the objects involved. PD CEN ISO/TS 16401-2:2012ISO/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 implementation of one or more OS1
30、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 the user NOTE Taken from ISO
31、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 domain ISO/TS 17574:2009, definit
32、ion 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 Characterization System SUT System Under
33、 Test TC Test Case PD CEN ISO/TS 16401-2:2012ISO/TS 16401-2:2012(E) ISO 2012 All rights reserved 35 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
34、where usage data 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
35、Test architecture 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
36、 sub-layer. The figure below describes the test architecture. Communication Sub-layerTTCN-3Test executionTESTER 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
37、 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 the proforma. 6 Untestable Test Purposes (TP) This clause gives a list of TPs which are not impleme
38、nted in the Abstract Test Suite due to the chosen Abstract Test Method or other restrictions. PD CEN ISO/TS 16401-2:2012ISO/TS 16401-2:2012(E) 4 ISO 2012 All rights reservedTable 1 Untestable TPs Test purpose Reason(empty) (empty) NOTE Currently no untestable TPs have been identified. 7 ATS data str
39、uctures 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 the C function signature and the C data structures defined in D.2 The r
40、eturn 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 Common data types They are reduced to an enumerate structure of commun
41、ication 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, each a receive cal back event statement was added in the default behavio
42、ur, 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 inte
43、nded to provide an easier reading of the ATS by using rules for naming objects. PD CEN ISO/TS 16401-2:2012ISO/TS 16401-2:2012(E) ISO 2012 All rights reserved 510.1 Definition naming conventions To define the ATS naming conventions, the following principle are taken into consideration: Prefixes are s
44、hort alphabetic string indicating the type of TTCN-3 element it represents (see table 2 below). Suffixes should not be used except in those specific cases identified in Table 2 below. Prefixes and suffixes should be separated from the body of the identifier with an underscore (“_“): EXAMPLE 1 c_sixt
45、een, 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 should be indicate
46、d by capitalizing the first character. Underscores should not be used for this purpose. EXAMPLE 2 f_compareDateAndTime. The Table 2 below specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix, suffixes (if any) and capitalization. Table 2 TTCN-3 na
47、ming convention Language element Naming convention Prefix Suffix Example NotesModule 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_Behaviour Data type Use u
48、pper-case initial letter none none ChargeReportList type identifiers Use upper-case initial letter none none TimeClassesGroups Message template Use lower-case initial letter m_ none m_Iso17575_3Adu Message template with wildcard or matching expression Use lower-case initial letters mw_ none mw_Iso17
49、575_3Adu_default Port instance Use lower-case initial letter none none pcoExternal function Use lower-case initial letter fx_ none fx_getCurrentTime() Constant Use lower-case initial letter c_ none c_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
