ISO 16407-1:2017 pdf free.Electronic fee collection—Evaluation of equipment for conformity to ISO 17575-1—Test suite structure and test purposes.
This document takes into account already defined test purposes for conformance to the base standards by referencing them, so that
a) for test purposes that are identical to those defined in this document or the base standards conformance test cases direct reference is reported; for reader’s convenience, the title or a verbal description of the referenced test purpose 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 shall be modified for the profile conformance testing,
c) for test purposes that are specific to Iso 17575-1, a complete description is given, and
d) an indication on whether a test purpose is identical, derived, or specific is given in each test purpose.The TPs are defined following the rules shown in Table 2. 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 17575-1. The supplier of the Front End and Back End, respectively, is responsible for providing a conformance test report.
The supplier of the Front End shall complete the proforma conformance test report (PCTR) for Front
End as defined in Annex D. The supplier of the Back End shall complete the proforma conformance test report (PCTR) for Back End as defined in Annex E.In addition, the sequence of ADUs issued by the Front End is not constrained by ISO 17575-1. This means that ADU cannot in general be forced to be generated by the IUT. To execute the test purposes it may be needed to filter out some ADUs, as they might not be applicable for TP, e.g. some ADUs are applicable for different toll context. This is illustrated in Figure A.1.Front End received already Context Data with correctly set timeZone attribute and requesting presence of timeOfReport. Front End is initialized and has a toll context activated. Authentication is not used.Verify the structure of sent ChargeReport, taking presence and absence of data elements into account and verify allowed values of present data elements according to Table C.1.Front End received already Context Data requesting presence of chargeReportCounter.
Front End is initialized and has a toll context activated. Next charge Report Counter value is a maximum value (i.e. 4294967295) Authentication is not used. Verify the structure of sent ChargeReport, taking presence and absence of data elements into account and verify allowed values of present data elements according to Table C.1. IF verify NOT “OK” THEN TP failed.Verify the structure of sent ChargeReport, taking presence and absence of data elements into account
and verify allowed values of present data elements according to Table C.1.Front End received already Context Data requesting presence of mileage. Front End is initialized and has a toll context activated.
Authentication is not used.ISO 16407-1 pdf download.