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 1: Test suite structure and test purposesPD CEN ISO/TS 16401-1:2012National forewordThis Pu
2、blished Document is the UK implementation of CEN ISO/TS 16401-1: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
3、not purport to include 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 71831 1ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity fr
4、omlegal obligations.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 16401-1:2012TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNI
5、SCHE SPEZIFIKATION CEN ISO/TS 16401-1 March 2012 ICS 03.220.20; 35.240.60 English Version Electronic fee collection - Evaluation of equipment for conformity to ISO/TS 17575-2 - Part 1: Test suite structure and test purposes (ISO 16401-1:2012) Perception du tlpage - valuation de conformit de lquipeme
6、nt lISO/TS 17575-2 - Partie 1: Structure de la suite dessais et objectifs dessai (ISO 16401-1:2012) Elektronische Gebhrenerhebung - Konformittsevaluierung von Einrichtungen nach CEN ISO/TS 17575-2 - Teil 1: Prfreihen Struktur und Prfabsichten (ISO 16401-1:2012) This Technical Specification (CEN/TS)
7、was approved by CEN on 30 January 2012 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 Europe
8、an Standard. CEN members are required to 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 fina
9、l decision about the possible conversion 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, Luxembo
10、urg, Malta, Netherlands, Norway, Poland, 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 Al
11、l rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN ISO/TS 16401-1:2012: EPD CEN ISO/TS 16401-1:2012CEN ISO/TS 16401-1:2012 (E) 2 Contents Page Foreword 3PD CEN ISO/TS 16401-1:2012CEN ISO/TS 16401-1:2012 (E) 3 Foreword This document (CEN IS
12、O/TS 16401-1: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 elemen
13、ts 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 Techn
14、ical 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,
15、 Turkey and the United Kingdom. PD CEN ISO/TS 16401-1:2012ISO/TS 16401-1:2012(E) ISO 2012 All rights reserved iiiContents Page Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions .1 4 Abbreviations.2 5 Test Suite Structure (TSS)3 5.1 Structure.3 5.2 Reference to conformance test
16、specifications 3 5.3 Test Purposes (TP)4 5.3.1 TP definition conventions.4 5.3.2 TP naming conventions4 5.4 Protocol Conformance Test Report (PCTR) .5 Annex A (normative) TP for Front End Communications API6 Annex B (normative) Annex ATP for Front End Application139 Annex C (informative) PCTR Profor
17、ma for Front End Communications API143 Annex D (informative) PCTR Proforma for Front End Application 150 Bibliography154 PD CEN ISO/TS 16401-1:2012ISO/TS 16401-1:2012(E) ISO 2012 All rights reserved vIntroduction This part of ISO/TS 16401 is part of a set of standards that supports interoperability
18、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 process and tests for conformity evaluation of
19、 Front End Communications API and Front End application 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 End application capabilities, assess Front End Communications API and Front End application behaviour, s
20、erve 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 different places at different times, and facilitate communications between parties. This part of ISO/TS
21、 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-1:2012TECHNICAL SPECIFICATION ISO/TS 16401-1:2012(E) ISO 2012 All rights reserved 1Electronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-2 Part
22、1: Test suite structure and test purposes 1 Scope This part of ISO/TS 16401 specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of Front End Communications API and Front End application to ISO/TS 17575-2. The objective of this part of ISO/TS 16401 is to provide
23、 a basis for conformance tests for Front Ent 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 different manufacturers. This part of ISO/TS 16401 covers the test pu
24、rposes for Front End Communications API covering functionalities related to instance handling, session handling, communication service primitives (i.e. sending/receiving of ADUs) and visible state transitions. It fully covers EFC communication services claimed in ISO/TS 17575-2 clause 7 and PICS pro
25、forma Clause B.2 ISO/TS 17575-2. Claims related to Front End Storage capacity are outside of the scope of this part of ISO/TS 16401. This part of ISO/TS 16401 covers the test purposes for Front End application related to session establishment on Back End request and related to session re-establishme
26、nt when session requested by Back End failed. There are no other claims with respect to Front End application claimed in ISO/TS 17575-2. The underlying communication technology requirements for layer 1-4 specified in Clause 8 ISO/TS 17575-2 is outside of the scope of this part of ISO/TS 16401. Simil
27、arly Back End communications API is outside of the scope of this part of ISO/TS 16401. According to ISO/TS 17575-2 it is expected that these Front End Communications API will be reflected in the BE, however BE Communications API is outside of the scope of ISO/TS 17575-2. 2 Normative references The f
28、ollowing referenced 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
29、interface definition for autonomous systems Part 2: Charging ISO/TS 17575-2, Electronic fee collection Application interface definition for autonomous systems Part 2: Communication and connection to the lower layers 3 Terms and definitions For the purposes of this document, the terms and definitions
30、 given in ISO/TS 17575-1 and the following apply. PD CEN ISO/TS 16401-1:2012ISO/TS 16401-1:2012(E) 2 ISO 2012 All rights reserved3.1 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
31、obligations, permissions and prohibitions for the objects involved. 3.2 Front End application part of the Front End above the API 3.3 service provider operator that accepts the users payment means and in return provides a road-use service to the user NOTE Taken from ISO 14906:2004. 3.4 toll charger
32、legal entity charging toll for vehicles in a toll domain ISO/TS 17574:2009, definition 3.27 4 Abbreviations For the purposes of this document, the following abbreviations apply throughout the document unless otherwise specified. ADU Application Data Unit API Application Programming Interface ASN.1 A
33、bstract Syntax Notation One ATS Abstract Test Suite BE Back End BI Invalid Behaviour BV Valid Behaviour CCC Compliance Check Communication CN Cellular Network DUT Device Under Tests EFC Electronic Fee Collection FE Front End GNSS Global Navigation Satellite Systems HMI Human Machine Interface ID Ide
34、ntifier PD CEN ISO/TS 16401-1:2012ISO/TS 16401-1:2012(E) ISO 2012 All rights reserved 3OBE On-Board Equipment PCTR Protocol Conformance Test Report PICS Protocol Implementation Conformance Statements TP Test Purposes TSS Test Suite Structure VAT Value Added Tax 5 Test Suite Structure (TSS) 5.1 Struc
35、ture Table 1 Test Suite Structures shows the Test Suite Structure (TSS). Table 1 Test Suite Structures Group Type of DUT Behaviour Valid Behaviour Instance Handling Front End Communications API Invalid Behaviour Valid Behaviour Front End Communications API Invalid Behaviour Session Handling Front En
36、d application Valid Behaviour Valid Behaviour Communication Service Primitives Front End Communications API Invalid Behaviour State Transitions Front End Communications API Valid Behaviour 5.2 Reference to conformance test specifications This part of ISO/TS 16401 takes into account already defined t
37、est purposes for conformance to the base standards by referencing them, so that: a) For test purposes that are identical to those defined in the base standards conformance test cases direct reference is reported. For readers convenience, the title or a verbal description of the referenced test purpo
38、se is given, together with the reference. b) For test purposes that are derived from those defined in the base standards conformance test cases, a direct reference is reported, plus an indication on how the referred test purpose has to be modified for the profile conformance testing. c) For test pur
39、poses that are specific to ISO/TS 17575-2, a complete description is given. d) An indication on whether a test purpose is identical, derived, or specific is given in each test purpose. PD CEN ISO/TS 16401-1:2012ISO/TS 16401-1:2012(E) 4 ISO 2012 All rights reserved5.3 Test Purposes (TP) 5.3.1 TP defi
40、nition conventions The TPs are defined following the rules shown in Table 2 TP Definition Rules below. All Test Purposes are defined in Annex A and Annex B, including the special notation and symbol conventions that shall be used. Table 2 TP Definition Rules Title Reference TP origin Initial conditi
41、on TP ID according to the TP naming conventions Stimulus and expected behaviour TP ID The TP ID is a unique identifier. It shall be specified according to the TP naming conventions defined in the sub-clause below. Title Short description of Test Purpose objective. Reference The reference should cont
42、ain the references of the subject to be validated by the actual TP (specification reference, clause, paragraph), or the reference to the standard document defining the TP. TP origin Indicates if the TP is identical to a TP defined in another test standard, derived from a TP defined in another test s
43、tandard, or specific for this standard profile. Initial condition The condition defines in which initial state the DUT has to be to apply the actual TP. Stimulus and expected behaviour Definition of the events the tester performs, and the events that are expected from the DUT to conform to the base
44、specification. 5.3.2 TP naming conventions Each TP is given a unique identification. This unique identification is built up to contain the following string of information: TP/- TP : to indicate that it is a Test Purpose; : which group TP belongs to; : type of DUT (i.e. API or APPL); X : type of test
45、ing (i.e. Valid Behaviour tests BV, or Invalid Behaviour tests BI); : sequential TP number (01-99). The naming conventions are as described in Table 3. PD CEN ISO/TS 16401-1:2012ISO/TS 16401-1:2012(E) ISO 2012 All rights reserved 5Table 3 TP naming convention Identifier: TP/- applicable for FE Commu
46、nications API IH Instance Handling applicable for FE Communications API SH Session Handling applicable for FE Application SH Session Handling applicable for FE Communications API CSP Communications Service Primitives applicable for FE Communications API ST State Transitions = type of DUT API Front E
47、nd Communications API APPL Front End application x = Type of testing BV Valid Behaviour Tests BI Invalid Behaviour Tests = sequential number (01-99) Test Purpose Number 5.4 Protocol Conformance Test Report (PCTR) The supplier of the Front End and Back End, respectively, is responsible for providing
48、a Protocol Conformance Test Report (PCTR). The supplier of the Front End and the Back End shall complete a PCTR; see Annex C and Annex D for the proformas. PD CEN ISO/TS 16401-1:2012ISO/TS 16401-1:2012(E) 6 ISO 2012 All rights reservedAnnex A (normative) TP for Front End Communications API A.1 Intro
49、duction This annex contains the Test Purposes (TP) for the conformity evaluation of Front End Communications API to ISO/TS 17575-2. A.1.1 TP symbols conventions A special notation and symbol convention is used, as defined in what follows. Symbols are used in the description of the TPs, with meanings according to Table A.1 below. Table A.1 Description of TP Symbols SYMBOL DESCRIPTION XXX(Type1=value1) The Tester executes an XXX method of Front End Communications
