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-4Part 1: Test suite structure and test purposesPD CEN ISO/TS 16403-1:2012National forewordThis Pu
2、blished Document is the UK implementation of CEN ISO/TS 16403-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 71832 8ICS 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 16403-1:2012TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNI
5、SCHE SPEZIFIKATION CEN ISO/TS 16403-1 March 2012 ICS 35.240.60; 03.220.20 English Version Electronic fee collection - Evaluation of equipment for conformity to ISO/TS 17575-4 - Part 1: Test suite structure and test purposes (ISO 16403-1:2012) Perception du tlpage - valuation de conformit de lquipeme
6、nt lISO/TS 17575-4 - Partie 1: Structure de la suite dessais et objectif dessai (ISO 16403-1:2012) Elektronische Gebhrenerhebung - Konformittsevaluierung von Einrichtungen nach CEN ISO/TS 17575-4 - Teil 1: Prfreihen Struktur und Prfabsichten (ISO 16403-1:2012) This Technical Specification (CEN/TS) w
7、as 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 Europea
8、n 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 final
9、 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, Luxembou
10、rg, 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 All
11、 rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN ISO/TS 16403-1:2012: EPD CEN ISO/TS 16403-1:2012CEN ISO/TS 16403-1:2012 (E) 2 Contents Page Foreword 3PD CEN ISO/TS 16403-1:2012CEN ISO/TS 16403-1:2012 (E) 3 Foreword This document (CEN ISO
12、/TS 16403-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 element
13、s 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 Techni
14、cal 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 16403-1:2012ISO/TS 16403-1:2012(E) ISO 2012 All rights reserved iiiContents Page Introduction . v 1 Scope 1 2 Normative references 1 3 Terms and definitions . 2 4 Abbreviations . 2 5 Test Suite Structure (TSS) 3 5.1 Structure . 3 5.2 Reference to conforma
16、nce test specifications 3 5.3 Test Purposes (TP) 4 5.3.1 TP definition conventions. 4 5.3.2 TP naming conventions 5 5.4 Protocol Conformance Test Report (PCTR) . 5 Annex A (normative) Test Purposes for Front End . 6 Annex B (normative) TP for Back End 24 Annex C (normative) Data Structures . 31 Anne
17、x D (informative) PCTR Proforma for Front End . 40 Annex E (informative) PCTR Proforma for Back End 44 Bibliography 48 PD CEN ISO/TS 16403-1:2012ISO/TS 16403-1:2012(E) ISO 2012 All rights reserved vIntroduction This part of ISO/TS 16403 is part of a set of standards that supports interoperability of
18、 autonomous EFC-systems, which includes ISO/TS 17575 that defines 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 Front End and
19、 Back End that comply with the requirements in ISO/TS 17575-4. This part of ISO/TS 16403 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 conformance evaluation and type approval, achieve comparability bet
20、ween the results of the corresponding tests applied in different places at different times, and facilitate communications between parties. This part of ISO/TS 16403 is based on ISO/TS 17575-4. PD CEN ISO/TS 16403-1:2012TECHNICAL SPECIFICATION ISO/TS 16403-1:2012(E) ISO 2012 All rights reserved 1Elec
21、tronic fee collection Evaluation of equipment for conformity to ISO/TS 17575-4 Part 1: Test suite structure and test purposes 1 Scope This part of ISO/TS 16403 specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of Front End and Back End to ISO/TS 17575-4. The
22、objective of the present document is to provide a basis for conformance tests for the Front End and the Back End in Electronic Fee Collection based on autonomous on-board equipment (OBE) to enable interoperability between different equipment supplied by different manufacturers. Autonomous OBE operat
23、e without relying on dedicated road-side infrastructure by employing wide-area technologies such as Global Navigation Satellite Systems (GNSS) and Cellular Communications Networks (CN). These EFC systems are referred to by a variety of names. Besides the terms autonomous systems and GNSS/CN systems,
24、 also the terms GPS/GSM systems, and wide-area charging systems are in use. Autonomous systems use satellite positioning, often combined with additional sensor technologies such as gyroscopes, odometers, and accelerometers, to localise the vehicle and to find its position on a map containing the cha
25、rged geographic objects, such as charged roads or charged areas. From the charged objects, the vehicle characteristics, the time of day and other data that are relevant for describing road use, the tariff and ultimately the road usage fee is determined. Test Purposes applicable for the Back End focu
26、s on the output produced by the Back End, i.e. Roaming Rules data element. Test Purposes related to Front End focus on the main scenarios defined in ISO/TS 17575-4 6.2.4. To verify the Front End behaviour it is needed to observe Charge Reports which are defined in ISO/TS 17575-1. The dependencies be
27、tween Context Data (defined in ISO/TS 17575-3), Charge Report (defined in ISO/TS 17575-1) and Roaming (defined in ISO/TS 17575-4) to support a particular pricing scheme scenario are outside of the scope of this part of ISO/TS 16403. As ISO/TS 17575-4 does not specify any invalid behaviour of Front E
28、nd and Back End, BI test purposes are not applicable for any Test Purpose group. 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 edition of the r
29、eferenced document (including any amendments) applies. ISO 14906, Electronic fee collection Application interface definition for dedicated short-range communication ISO 17573, Electronic fee collection Systems architecture for vehicle-related tolling PD CEN ISO/TS 16403-1:2012ISO/TS 16403-1:2012(E)
30、2 ISO 2012 All rights reservedISO/TS 17575-1, Electronic fee collection Application interface definition for autonomous systems Part 1: Charging ISO/TS 17575-3, Electronic fee collection Application interface definition for autonomous systems Part 3: Context data ISO/TS 17575-4, Electronic fee colle
31、ction Application interface definition for autonomous systems Part 4: Roaming 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO 17573, ISO/TS 17575-1 and the following apply. 3.1 contract expression of an agreement between two or more parties concernin
32、g the use of the road infrastructure NOTE A contract specifies obligations, permissions and prohibitions for the objects involved. ISO 14906:2011, definition 3.7 3.2 service provider operator that accepts the users payment means and in return provides a road-use service to the user NOTE Taken from I
33、SO 14906:2004. 3.3 toll charger 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, unless otherwise specified. ADU Application Data Unit ASN.1 Abstract Syntax Notation One A
34、TS Abstract Test Suite BI Invalid Behaviour BV Valid Behaviour CCC Compliance Check Communication CN Cellular Network DUT Device Under Tests EFC Electronic Fee Collection GNSS Global Navigation Satellite Systems HMI Human Machine Interface PD CEN ISO/TS 16403-1:2012ISO/TS 16403-1:2012(E) ISO 2012 Al
35、l rights reserved 3ID Identifier OBE 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 Structure Table 1 Test Suite Structures shows the Test Suit
36、e Structure (TSS). Table 1 Test Suite Structures Group Type of DUT Behaviour General Front End Valid Behaviour Invalid Behaviour not applicable Back End Valid Behaviour Invalid Behaviour not applicable Combined Charge Report Front End Valid Behaviour Invalid Behaviour not applicable Relevant EFC Con
37、texts Front End Valid Behaviour Invalid Behaviour not applicable Data Elements Back End Valid Behaviour Invalid Behaviour not applicable 5.2 Reference to conformance test specifications This document takes into account already defined test purposes for conformance to the base standards by referencin
38、g them, so that: a) For test purposes that are identical to those defined in this specification or the base standards conformance test cases direct reference is reported. For readers convenience, the title or a verbal description of the referenced test purpose is given, together with the reference.
39、PD CEN ISO/TS 16403-1:2012ISO/TS 16403-1:2012(E) 4 ISO 2012 All rights reservedb) 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
40、 conformance testing. c) For test purposes that are specific to ISO/TS 17575-4, a complete description is given. d) An indication on whether a test purpose is identical, derived, or specific is given in each test purpose. 5.3 Test Purposes (TP) 5.3.1 TP definition conventions The TPs are defined fol
41、lowing 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. The data structures that shall be used are specified in Annex C and defined in ISO/TS 17575-3 and ISO/TS 17575-
42、4. Table 2 TP Definition Rules TP ID according to the TP naming conventions Title Reference TP origin Initial condition 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 de
43、scription of Test Purpose objective. Reference The reference should contain 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 defin
44、ed in another test standard, derived from a TP defined in another test standard, 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 perform
45、s, and the events that are expected from the DUT to conform to the base specification. PD CEN ISO/TS 16403-1:2012ISO/TS 16403-1:2012(E) ISO 2012 All rights reserved 55.3.2 TP naming conventions Each TP is given a unique identification. This unique identification is built up to contain the following
46、string of information: TP/- TP : to indicate that it is a Test Purpose; : which group TP belongs to; : type of DUT (i.e. FE or BE); X : type of testing (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.
47、Table 3 TP naming convention Identifier: TP/- applicable for FE and BE GEN General applicable for FE CCR Combined Charge Report applicable for FE REC Relevant EFC Contexts applicable for BE DAT Data elements = type of DUT FE Front End BE Back End x = Type of testing BV Valid Behaviour Tests BI Inval
48、id 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 a Protocol Conformance Test Report (PCTR). The supplier of the Front End and the Back End shall comple
49、te a PCTR; see Annex D and Annex E for the proformas. PD CEN ISO/TS 16403-1:2012ISO/TS 16403-1:2012(E) 6 ISO 2012 All rights reservedAnnex A (normative) Test Purposes for Front End A.1 Introduction This annex contains the Test Purposes (TP) for the conformity evaluation of Front End to ISO/TS 17575-4. 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 me
