1、BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Electronic fee collection - Evaluation of equipment for conformity to ISO 17575-2Part 2: Abstract test suitePD CEN ISO/TR 164012:2018National forewordThis Published Document is the UK implementation of CEN ISO/TR 164012
2、:2018. It is identical to ISO/TR 164012:2018. It supersedes PD CEN ISO/TS 164012:2012, which is withdrawn.The UK participation in its preparation was entrusted to Technical Committee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained on reque
3、st to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2018 Published by BSI Standards Limited 2018ISBN 978 0 580 99007 6ICS 35.240.60; 03.220.20Compliance with
4、a British Standard cannot confer immunity from legal obligations. This Published Document was published under the authority of the Standards Policy and Strategy Committee on 28 February 2018.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN ISO/TR 164012:2018TE
5、CHNICAL REPORTRAPPORT TECHNIQUETECHNISCHER BERICHTCEN ISO/TR 16401-2February 2018ICS 35.240.60; 03.220.20 Supersedes CEN ISO/TS 164012:2012EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGCEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussel
6、s 2018 CEN Ref. No. Fpr CEN ISO/TR 164012:2018: EAll rights of exploitation in any form and by any means reserved worldwide for CEN national MembersElectronic fee collection Evaluation of equipment for conformity to ISO/TS 175752 Part 2: Abstract test suite (ISO/TR 164012:2018)Perception du tlpage v
7、aluation de conformit de lquipement lISO/TS 175752 Partie 2: Suite dessai abstraite (ISO/TR 164012:2018)Elektronische Gebhrenerhebung Konformittsevaluierung von Einrichtungen nach ISO/TS 175752 Teil 2: Zusammengefasstes Prfprogramm (ISO/TR 164012:2018)This Technical Report was approved by CEN on 14
8、January 2018. It has been drawn up by the Technical Committee CEN/TC 278.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland,
9、 Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.English Version2PD CEN ISO/TR 164012:2018CEN ISO/TR 16401-2:2018 (E)European forewordThis document (CEN ISO/TR 164012:2018)
10、has been prepared by Technical Committee ISO/TC 204 “ Intelligent transport systems “ in collaboration with Technical Committee CEN/TC 278 “Intelligent transport systems” the secretariat of which is held by NEN.Attention is drawn to the possibility that some of the elements of this document may be t
11、he subject of patent rights. CEN shall not be held responsible for identifying any or all such patent rights.This document supersedes CEN ISO/TR 164012:2012.This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association.Endorsement not
12、iceThe text of ISO/TR 164012:2018 has been approved by CEN as CEN ISO/TR 164012:2018 without any modification.ISO/TR 16401-2:2018Foreword ivIntroduction v1 Scope . 12 Normative references 13 Terms and definitions . 14 Abbreviated terms 25 Abstract test method (ATM) 35.1 Implementations under tests .
13、 35.1.1 Front End (FE) . 35.1.2 Back End (BE) . 35.2 Test architecture 35.3 Protocol Implementation Extra Information for Testing (PIXIT) 36 Untestable test purposes (TP) 47 ATS data structures 47.1 General . 47.2 Common data types 48 External functions . 49 Message filtering 410 ATS naming conventi
14、ons. 410.1 Definition naming conventions . 410.2 Test case identifier . 610.3 TTCN-3 modules identifier . 6Annex A (informative) TTCN-3 library modules for FE and BE . 7Annex B (informative) PIXIT proforma for Front End Communications API and Front End application 8Bibliography .10 ISO 2018 All righ
15、ts reserved iiiContents PagePD CEN ISO/TR 164012:2018ISO/TR 16401-2:2018ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO techn
16、ical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and nongovernmental, in liaison with ISO, also take part in the work. ISO collaborates closely w
17、ith the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed
18、 for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rig
19、hts. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).Any trade name used in thi
20、s document is information given for the convenience of users and does not constitute an endorsement.For an explanation on the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the World Tr
21、ade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.This first edition of ISO/TR 16401-2 cancels and replaces ISO/TS 16401-2:2012, w
22、hich has been technically revised.The main changes compared to the previous edition are as follows: conversion from a Technical Specification to Technical Report has been made; the terms and definitions have been revised; editorial and formal corrections as well as changes to improve readability hav
23、e been made.A list of all parts in the ISO 16401 series can be found on the ISO website.iv ISO 2018 All rights reservedPD CEN ISO/TR 164012:2018ISO/TR 16401-2:2018IntroductionThis document is part of a set of standards that supports interoperability of autonomous electronic fee collection (EFC) syst
24、ems. Autonomous systems use satellite positioning, often combined with additional sensor technologies such as gyroscopes, odometers, and accelerometers, to localize the vehicle and to find its position on a map containing the charged geographic objects, such as charged roads or charged areas. From t
25、he 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 are determined.The ISO/TR 16401 series provides tests to assess the Front End Communications API and Front End application behaviour
26、s compliancy towards the requirements listed in ISO 175752. ISO/TR 164011 contains the definition of such tests in the form of test purposes, listing the initial conditions, references and individual steps in a structured textual manner. This document contains the identical tests written in Testing
27、and Test Control Notation version 3 (TTCN3).Autonomous onboard equipment (OBE) operates without relying on dedicated roadside infrastructure by employing widearea technologies such as Global Navigation Satellite Systems (GNSS) and Cellular Communications Networks (CN). Therefore, autonomous systems
28、may also be referred to as GNSS/CN systems.Within the suite of EFC standards, this document defines tests for conformity evaluation of Front End and Back End that comply with the requirements towards the context data specified in ISO 17575-2.This document is intended to assess Front End Communicatio
29、ns API 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
30、 tests applied in different places at different times, and facilitate communications between parties. ISO 2018 All rights reserved vPD CEN ISO/TR 164012:2018This page deliberately left blankElectronic fee collection - Evaluation of equipment for conformity to ISO 17575-2 Part 2: Abstract test suite1
31、 ScopeThis document contains the definition of test cases, reflecting the individual steps listed in specific test purposes defined in ISO/TR 16401-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN3).2 Normative referencesThe following documents are referred to in th
32、e text in such a way that some or all of their content constitutes requirements 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 175751, Electronic fee collection Appli
33、cation interface definition for autonomous systems Part 1: Charging3 Terms and definitionsFor the purposes of this document, the terms and definitions given in ISO 17575-1 and the following apply.ISO and IEC maintain terminological databases for use in standardization at the following addresses: IEC
34、 Electropedia: available at http:/www.electropedia.org/ ISO Online browsing platform: available at http:/www.iso.org/obp3.1conformance testingtesting the extent to which an IUT is a conforming implementationSOURCE: ISO/IEC 96461:1994, 3.3.233.2Front End applicationpart of the Front End above the API
35、SOURCE: ISO/TR 164011:2017, 3.123.3implementation under testIUTimplementation of one or more OSI protocols in an adjacent user/provider relationship, being that part of a real open system which is to be studied by testingSOURCE: ISO/IEC 96461:1994, 3.3.43TECHNICAL REPORT ISO/TR 16401-2:2018 ISO 2018
36、 All rights reserved 1PD CEN ISO/TR 164012:2018ISO/TR 16401-2:20183.4system under testSUTreal open system in which the IUT residesSOURCE: ISO/IEC 96461:1994, 3.3.1033.5test caseabstract or executable test caseSOURCE: ISO/IEC 96461:1994, 3.3.1073.6toll service providerentity providing toll services i
37、n one or more toll domainsSOURCE: ISO 17573:2010, 3.23, modified the definition has been revised.4 Abbreviated termsADU application data unitAPI application programming interfaceASN.1 Abstract Syntax Notation OneATM abstract test methodATS abstract test suiteBE Back EndBI behaviour invalidBV behavio
38、ur validCN cellular networkDUT device under testEFC electronic fee collectionFE Front EndGNSS Global Navigation Satellite SystemsID identifierIUT implementation under testOBE onboard equipmentPICS Protocol Implementation Conformance StatementsPIXIT Protocol Implementation Extra Information for Testi
39、ngSCS semiconductor characterization systemSUT system under test2 ISO 2018 All rights reservedPD CEN ISO/TR 164012:2018ISO/TR 16401-2:2018TC test caseTP test purposesTSS test suite structureTTCN Testing and Test Control Notation5 Abstract test method (ATM)This clause describes the ATM used to test t
40、he layers at the FE side and at the BE side.5.1 Implementations under tests5.1.1 Front End (FE)FE refers to the part(s) of the toll system where usage data for an individual user are collected, processed and delivered to the Back End. The Front End comprises the onboard equipment and optionally a pr
41、oxy.5.1.2 Back End (BE)BE is the generic name for the computing and communication facilities of the service provider and/or the toll charger.5.2 Test architectureThe implementation under test is either the FE or the BE. The system under test comprises also the communication sublayer, which is necess
42、ary to perform the IUT tests.The tester executes the TTCN3 test cases of this document, running on an emulated communication sublayer.Figure 1 describes the test architecture.Figure 1 Test system architecture5.3 Protocol Implementation Extra Information for Testing (PIXIT)The supplier of the Front E
43、nd and Back End, respectively, should provide a Protocol Implementation Extra Information for Testing (PIXIT); see Annex B for the proforma. ISO 2018 All rights reserved 3PD CEN ISO/TR 164012:2018ISO/TR 16401-2:20186 Untestable test purposes (TP)Table 1 gives a list of TPs which are not implemented
44、in the abstract test suite due to the chosen abstract test method or other restrictions.Table 1 Untestable TPsTest purpose Reason(empty) (empty)NOTE Currently, no untestable TPs have been identified.7 ATS data structures7.1 GeneralThe data structures are defined in the base standards using ASN.1. Th
45、e ATS is using the data definition of ASN.1 except for the data structures using advanced parametrization, where all the data structures are manually re-defined using the TTCN-38.7.2 Common data typesCommon data types are reduced to an enumerate structure of error codes for communication functions a
46、s described in ISO 175752:2016, Annex D.8 External functionsNo external functions are used.9 Message filteringAs depicted in ISO 175752:2016, D.2, each callback event is ignored by default.Thus, each receive call back event statement was added in the default behaviour to ignore it on the “pco” port,
47、 which has a valid ADU structure and was not handled in the test case behaviour.The corresponding TTCN3 code is as follows: pco.receive(mw_instanceStateChange_any) repeat; / Ignore state transition 10 ATS naming conventionsThe ATS naming conventions are intended to provide an easier reading of the A
48、TS by using rules for naming objects.10.1 Definition naming conventionsTo define the ATS naming conventions, the following principles are taken into consideration. Prefixes are short alphabetic string indicating the type of TTCN-3 element it represents (see Table 2). Suffixes should not be used exce
49、pt in those specific cases identified in Table 2. Prefixes and suffixes should be separated from the body of the identifier with an underscore (“_“).4 ISO 2018 All rights reservedPD CEN ISO/TR 164012:2018ISO/TR 16401-2:2018EXAMPLE 1 c_sixteen, t_wait_max. Only module names, data type names and module parameters should begin with an uppercase letter. All other names (i.e. the part of the identifier following the prefix) should begin with a l
