ISO/TS 14907-2:2011

Electronic fee collection — Test procedures for user and fixed equipment — Part 2: Conformance test for the onboard unit application interface

ISO/TS 14907-2:2011 describes tests that verify on-board unit (OBU) conformance of implementations of functions and data structures, as defined in the implementation conformance statement based on ISO 14906:2011, for electronic fee collection (EFC) applications. After the tests of isolated data items and functions, an example is given for testing of a complete EFC transaction. ISO/TS 14907-2:2011 comprises definitions of OBU conformance assessment tests of basic dedicated short-range communication (DSRC) L7 functionality, EFC application functions, EFC attributes (i.e. EFC application information), the addressing procedures of EFC attributes and (hardware) components [e.g. integrated circuit cards (ICC) and man-machine interfaces (MMI)], the EFC transaction model, which defines the common elements and steps of any EFC transaction, and the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface level. It also defines tests that assess OBU capabilities, assess OBU behaviour, serve as a guide for OBU 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. It is outside the scope of ISO/TS 14907-2:2011 to define tests that assess performance, robustness, and reliability of an implementation.

Perception du télépéage — Modes opératoires relatifs aux équipements embarqués et aux équipements fixes — Partie 2: Essai de conformité de l'interface d'application de l'unité embarquée

General Information

• Status: Withdrawn
• Publication Date: 24-Oct-2011
• Withdrawal Date: 24-Oct-2011
• ICS: 35.240.60 - IT applications in transport
• ICS: 43.040.15 - Car informatics. On board computer systems
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 5 - Fee and toll collection
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 07-Jul-2016

Relations

• Revised: ISO/TS 14907-2:2016 - Electronic fee collection — Test procedures for user and fixed equipment — Part 2: Conformance test for the on-board unit application interface
• Effective Date: 05-Nov-2015
• Consolidates: ISO 230-7:2006 - Test code for machine tools — Part 7: Geometric accuracy of axes of rotation
• Effective Date: 06-Jun-2022
• Revises: ISO/TS 14907-2:2006 - Road transport and traffic telematics — Electronic fee collection — Test procedures for user and fixed equipment — Part 2: Conformance test for the onboard unit application interface
• Effective Date: 25-Sep-2010

Standards Content (Sample)

TECHNICAL ISO/TS
SPECIFICATION 14907-2
Second edition
2011-11-01

Electronic fee collection — Test
procedures for user and fixed
equipment —
Part 2:
Conformance test for the onboard unit
application interface
Perception du télépéage — Modes opératoires relatifs aux équipements
embarqués et aux équipements fixes —
Partie 2: Essai de conformité de l'interface d'application de l'unité
embarquée




Reference number
ISO/TS 14907-2:2011(E)
©
ISO 2011

---------------------- Page: 1 ----------------------
ISO/TS 14907-2:2011(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO 2011 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/TS 14907-2:2011(E)
Contents Page
Foreword . iv
Introduction . v
1  Scope . 1
2  Normative references . 5
3  Terms and definitions . 5
4  Abbreviated terms . 8
5  OBU and supporting information . 11
5.1  ICS . 12
5.2  IXIT . 12
6  Testing requirements . 12
6.1  Conceptual test architecture . 12
6.2  Conformance test system. 13
6.3  Test documentation . 14
Annex A (normative) Implementation conformance statement pro forma . 16
Annex B (normative) Implementation of extra information for testing . 29
Annex C (informative) OBU test cases . 33
Annex D (informative) OBE conformance test procedures conducted in Japan . 74
Bibliography . 79

© ISO 2011 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/TS 14907-2:2011(E)
Foreword
ISO (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
technical 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
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of document:
 an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
 an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting
a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a
further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is
confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an
International Standard or be withdrawn.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TS 14907-2 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
This second edition cancels and replaces the first edition (ISO/TS 14907-2:2006), which has been technically
revised.
ISO/TS 14907 consists of the following parts, under the general title Electronic fee collection — Test
procedures for user and fixed equipment:
 Part 1: Description of test procedures
 Part 2: Conformance test for the onboard unit application interface

iv © ISO 2011 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/TS 14907-2:2011(E)
Introduction
This part of ISO/TS 14907 describes tests that verify OBU conformance of implementations of functions and
data structures for EFC applications.


© ISO 2011 – All rights reserved v

---------------------- Page: 5 ----------------------
TECHNICAL SPECIFICATION ISO/TS 14907-2:2011(E)

Electronic fee collection — Test procedures for user and fixed
equipment —
Part 2:
Conformance test for the onboard unit application interface
1 Scope
This part of ISO/TS 14907 describes tests that verify on-board unit (OBU) conformance of implementations of
functions and data structures, as defined in the implementation conformance statement based on
ISO 14906:2011, for electronic fee collection (EFC) applications. After the tests of isolated data items and
functions (C.1-C.2), an example is given for testing of a complete EFC transaction (C.3).
The scope of this part of ISO/TS 14907 comprises definitions of OBU conformance assessment tests of
 basic dedicated short-range communication (DSRC) L7 functionality,
 EFC application functions,
 EFC attributes (i.e. EFC application information),
 the addressing procedures of EFC attributes and (hardware) components [e.g. integrated circuit cards
(ICC) and man-machine interfaces (MMI)],
 the EFC transaction model, which defines the common elements and steps of any EFC transaction, and
 the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface
level, see Figure 1.
© ISO 2011 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO/TS 14907-2:2011(E)

Figure 1 — The EFC application interface
The purpose of this part of ISO/TS 14907 is to define tests that
 assess OBU capabilities,
 assess OBU behaviour,
 serve as a guide for OBU 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.
Whereas this part of ISO/TS 14907 defines examples of test cases for DSRC and EFC functionality in
Annex C, it does not intend to specify a complete test suite for a certain implementation. To compose a test
suite for a specific EFC implementation, the test cases may have to be modified and new test cases may have
to be defined and added in order for the conformance test to be complete. It can be useful to take into account
the following considerations when defining a complete test suite
 small range: “exhaustive testing” of critical interoperability/compatibility features,
 large range: testing of boundaries and random values, and
 composite types: testing of individual items in sequence or parallel.
Figure 2 shows the overall procedure of conformance testing.
2 © ISO 2011 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/TS 14907-2:2011(E)

Figure 2 — Conformance testing process
© ISO 2011 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO/TS 14907-2:2011(E)
Figure 3 gives a more detailed picture of the interface between the entity performing the conformance test and
the supplier of the Device Under Test (DUT). By the EFC application specification, the implementation
conformance statement pro forma and the implementation extra information for testing pro forma the supplier
is requested to provide the DUT (OBU), containing the Implementation Under Test (IUT), as well as the
documentation needed to perform the tests. More details on the content of the different documents are given
in Clause 5 on OBU and supporting information.
NOTE 1 The Device Under Test contains the Implementation Under Test.

Figure 3 — Documentation DUT supplier
It is outside the scope of this part of ISO/TS 14907 to define tests that assess
 performance,
 robustness, and
 reliability of an implementation.
NOTE 2 ISO/TS 14907-1 defines test procedures that are aimed at assessing performance, robustness and reliability
of EFC equipment and systems.
NOTE 3 The ISO/IEC 10373 family of International Standards defines test methods for proximity, vicinity, integrated
circuits(s) cards and related devices that may be relevant for OBUs that support such cards.
Annex D provides an informative overview of Japanese OBE conformance tests that are based on
ISO/TS 14907 suite of standards, in order to illustrate how these can be applied in practice.
4 © ISO 2011 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/TS 14907-2:2011(E)
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 referenced
document (including any amendments) applies.
ISO 14906:2011, Electronic fee collection — Application interface definition for dedicated short-range
communication
EN 12834, Road transport and traffic telematics — Dedicated short-range communication (DSRC) — DSRC
application layer
3 Terms and definitions
For the purposes of this document, the following definitions apply.
3.1
access credentials
data that is transferred to on-board equipment (OBE) in order to establish the claimed identity of a roadside
equipment (RSE) application process entity
[ISO 14906:2011, definition 3.1]
NOTE The access credentials carry information needed to fulfil access conditions in order to perform the operation
on the addressed element in the OBE. The access credentials can carry passwords as well as cryptographic based
information such as authenticators.
3.2
action
function that an application process resident at the roadside equipment (RSE) can invoke in order to make the
on-board equipment (OBE) execute a specific operation during the transaction
[ISO 14906:2011, definition 3.2]
3.3
attribute
application information formed by one or by a sequence of data elements, and that is managed by different
actions used for implementation of a transaction
[ISO 14906:2011, definition 3.3]
3.4
authenticator
data appended to, or a cryptographic transformation of, a data unit that allows a recipient of the data unit to
prove the source and/or the integrity of the data unit and protect against forgery
[ISO 14906:2011, definition 3.4]
3.5
channel
information transfer path
[ISO/IEC 7498-2:1989, definition 3.3.13 and ISO 14906:2011, definition 3.5]
3.6
component
logical and physical entity composing an on-board equipment (OBE), supporting a specific functionality
[ISO 14906:2011, definition 3.6]
© ISO 2011 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO/TS 14907-2:2011(E)
3.7
contract
expression of an agreement between two or more parties concerning the use of the road infrastructure
[ISO 14906:2011, definition 3.7]
3.8
data integrity
property that data has not been altered or destroyed in an unauthorised manner
[ISO/IEC 7498-2:1989, definition 3.3.21 and ISO 14906:2011, definition 3.10]
3.9
element
DSRC directory containing application information in the form of attributes
[ISO 14906:2011, definition 3.11]
3.10
implementation conformance statement
statement made by the supplier of an implementation or system claimed to conform to a given specification,
stating which capabilities have been implemented
3.11
implementation conformance statement pro forma
document, in the form of a questionnaire, which when completed for an implementation or system becomes
an implementation conformance statement
3.12
implementation extra information for testing
statement made by the supplier or an implementer of an IUT which contains or references all of the
information (in addition to that given in the implementation conformance statement) related to the IUT and its
testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT
3.13
implementation extra information for testing pro forma
document, in the form of a questionnaire, which when completed for an IUT becomes an implementation extra
information for testing
3.14
on-board equipment
equipment located within the vehicle and supporting the information exchange with the RSE, it is composed of
the OBU and other sub-units whose presence are considered optional for the execution of a transaction
NOTE Adapted from ISO 14906:2011, definition 3.13.
3.15
on-board unit
minimum component of an on-board equipment (OBE), whose functionality always includes at least the
support of the DSRC interface
[ISO 14906:2011, definition 3.14]
3.16
roadside equipment
equipment located at a fixed position along the road transport network, for the purpose of communication and
data exchanges with the on-board equipment (OBE) of passing vehicles
NOTE Adapted from ISO 14906:2011, definition 3.16.
6 © ISO 2011 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/TS 14907-2:2011(E)
3.17
service
EFC road transport related facility provided by a service provider, normally a type of infrastructure, the use of
which is offered to the user, for which the user may be requested to pay
[ISO 14906:2011, definition 3.17]
3.18
service primitive
communication elementary communication service provided by the application layer protocol to the
application processes
[ISO 14906:2011, definition 3.18]
NOTE The invocation of a service primitive by an application process implicitly calls upon and uses services offered
by the lower protocol layers.
3.19
toll service provider
EFC legal entity providing to his customers toll services on one or more toll domains for one or more classes
of vehicle
[ISO 14906:2011, definition 3.23]
NOTE 1 In other documents the terms issuer or contract issuer may be used.
NOTE 2 The toll service provider may provide the OBE or may provide only a magnetic card or a smart card to be used
with OBE provided by a third party (like a mobile telephone and a SIM card can be obtained from different parties).
NOTE 3 The toll service provider is responsible for the operation (functioning) of the OBE.
3.20
transaction
whole of the exchange of information between the roadside equipment (RSE) and the on-board equipment
(OBE) necessary for the completion of an electronic fee collection (EFC) operation over the DSRC
[ISO 14906:2011, definition 3.24]
3.21
transaction model
functional model describing the general structure of electronic fee collection (EFC) transactions
[ISO 14906:2011, definition 3.25]
3.22
tester
combination of equipment and processes which is able to perform conformance tests according to this part of
ISO/TS 14907
3.23
user
entity that uses transport services provided by the service provider according to the terms of a contract
NOTE Adapted from ISO 14906:2011, definition 3.26.
© ISO 2011 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO/TS 14907-2:2011(E)
4 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply throughout the document unless
otherwise specified.
4.1
ADU
Application Data Unit
4.2
APDU
Application Protocol Data Unit
4.3
AP
Application Process
4.4
ARIB
Association of Radio Industries and Businesses
NOTE ARIB (www.arib.or.jp) is based in Japan.
4.5
ASCII
American Standard Code for Information Interchange
4.6
AVI
Automatic Vehicle Identification
4.7
BST
Beacon Service Table
4.8
cf
confirm
4.9
DSRC
Dedicated Short-Range Communication
4.10
DUT
Device Under Test
4.11
EID
Element Identifier
4.12
EFC
Electronic Fee Collection
4.13
FTP
File Transfer Protocol
8 © ISO 2011 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/TS 14907-2:2011(E)
4.14
ICS
Implementation Conformance Statement
4.15
I-Kernel
Initialization Kernel
4.16
IID
Invoker Identifier
4.17
ind
indication
4.18
IUT
Implementation Under Test
[ISO 9646-1]
4.19
IXIT
Implementation eXtra Information for Testing
4.20
L1
Layer 1 of DSRC (physical layer)
4.21
L2
Layer 2 of DSRC (data link layer)
4.22
L7
Application Layer Core of DSRC
4.23
LID
Logical Link Control Identifier
4.24
LLC
Logical Link Control
4.25
LPDU
LLC Protocol Data Unit
4.26
M
a
ManufacturerID
[EN 12834]
4.27
MAC
Medium Access Control
© ISO 2011 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO/TS 14907-2:2011(E)
4.28
MMI
Man-Machine Interface
4.29
n.a.
not applicable
4.30
OBE
On-Board Equipment
4.31
OBU
On-Board Unit
4.32
ORSE
Organization for Road System Enhancement
4.33
P
a,b,c,d
Profile
[EN 13372, EN 12834]
EXAMPLE P denotes Profile 0.
0
4.34
PDU
Protocol Data Unit
4.35
PoC
Point of Control
4.36
PoO
Point of Observation
4.37
PPDU
Physical Layer Protocol Data Unit
4.38
PrWA
Private Window Allocation
[EN 12795]
4.39
PrWRq
Private Window Request
[EN 12795]
4.40
req
request
10 © ISO 2011 – All rights reserved

---------------------- Page: 15 ----------------------
ISO/TS 14907-2:2011(E)
4.41
rs
response
4.42
RSE
Roadside Equipment
4.43
SAM
Secure Application Module
4.44
T-APDU
Transfer-Application Protocol Data Unit
4.45
T-ASDU
Transfer-Application Service Data Unit
4.46
T-Kernel
Transfer Kernel
4.47
TTI
Traffic and Traveller Information
4.48
VST
Vehicle Service Table
5 OBU and supporting information
The supplier shall provide the OBU, i.e. the DUT, and the associated information including:
 OBUs personalized to be able to perform tests according to the ICS and IXIT as defined in 5.1 and 5.2,
respectively. At least five samples shall be submitted for test. More samples may be needed if several
different data structures and data contents are required in the tests;
 user's manual for the OBU, which shall include instructions how to handle the equipment, and may
include further detailed information about the protocol functions;
 implementation conformance statement according to 5.1. The ICS shall include statements regarding the
following:
 layer 7 services that are implemented in the OBU;
 EFC functions (action types) that are implemented in the OBU;
 whether or not data elements are used;
 implementation extra information for testing according to 5.2. The IXIT shall, if applicable, include:
 a statement regarding which layer 2 services shall be used to transfer the L7 services (and EFC
services);
 a description of security calculations in the OBU including a specification of the encryption algorithm
used;
© ISO 2011 – All rights reserved 11

---------------------- Page: 16 ----------------------
ISO/TS 14907-2:2011(E)
 values of the test Master Keys for calculation and verification of OBU security data such as
authenticators and access credentials.
The supplier should also provide configuration/personalization equipment for the OBU if that ensures effective
testing.
5.1 ICS
The ICS is a statement made by the supplier that claims conformance to a certain specification. The ICS
states which capabilities have been implemented in the specifications. It also states possible limitations in the
implementation of the specification.
This Technical Specification describes testing of implementations according to the following standards:
 EN 12834;
 ISO 14906:2011.
Annex A contains the ICS pro forma that shall be used for the ICS.
5.2 IXIT
The IXIT is a statement made by the supplier or an implementer of an IUT which contains or references all of
the information, in addition to that given in the implementation conformance statement, related to the DUT and
its testing environment. The IXIT enables the test laboratory to run an appropriate test suite against the DUT.
In this Technical Specification, the IXIT specifies the services in the lower communication layers that shall be
used to perform the services to be tested. These services are described e.g. in EN 12795, EN 12253 and
EN 13372.
The IXIT shall also contain further information and describe algorithms and procedures that are not specified
in the above standards but are prerequisites to perform the testing. Example of such information is:
 content of the ApplicationContextMark in the VST;
 calculation of access credentials in DSRC services;
 use of ReturnCode in DSRC L7 services and EFC functions; and
 calculation of authenticators in EFC functions.
Annex B contains the IXIT pro forma that shall be used for the declaration of the IXIT.
6 Testing requirements
6.1 Conceptual test architecture
A remote test method shall be used for the conformance test of OBUs (DUT). Figure 4 shows the conceptual
testing architecture of tester and DUT. The conformance test is only related to the implementation of the DUT.
The PoC, which is the point where the test events are controlled, shall be implemented inside the tester on the
interface between the application layer and the application process.
The PoO, which is the point where the occurrence of test events is to be observed, shall be implemented
inside the tester on the interface between the application layer and the application process. The PoO must
also interface the data link layer since some tests require observation of the behaviour on this layer.
12 © ISO 2011 – All rights reserved

---------------------- Page: 17 ----------------------
ISO/TS 14907-2:2011(E)
The PoC and PoO are characterized by a set of ASPs, according to the specifications of the tests. The test
events observed at the PoO may be supplemented by information provided by other sub-units, e.g. MMI or an
IC card if available with the DUT.

Figure 4 — Conceptual architecture of the conformance test
6.2 Conformance test system
The conformance tests shall be performed under controlled conditions by using a test system according to
Figure 5.

Figure 5 — Test facilities
6.2.1 Functionality of tester
6.2.1.1 Reference beacon
The beacon shall be a transparent physical layer interface for DSRC according to European or International
Standards, which means it shall be able to operate standardized data profiles of DSRC links. A simple beacon
may be used which will only send and receive frames to or from the DUT. The communication is controlled by
the application and data link process of the tester.
© ISO 2011 – All rights reserved 13

---------------------- Page: 18 ----------------------
ISO/TS 14907-2:2011(E)
Beacon parameters, e.g. the transmitting power, shall be adjustable by the tester.
6.2.1.2 Application and data link process
The tester shall be able to operate the communication link in real time according to data link layer functionality
of European or International Standards. The process shall provide the connection to the test control and
observation process and shall control the sending and reception of frames to and from the beacon.
6.2.1.3 Test control and observation processes
The test control and observation processes shall be implemented on an appropriately equipped computer
system. The processes shall comply with the definitions of the application and data link layers defined by
European or International standards and shall be able to generate test suites in reference to ISO 14906. The
control process shall provide functionality to configure the test-bed, to generate test suites and to perform test
suites.
EXAMPLE Test suites may be generated in plain ASCII format and may be retrieved by the real-time control process
via FTP.
While the tests are being performed, all events shall be observed by the PoO process. All results shall be
documented, visualized and be made available for detailed analysis.
6.2.2 Conformance testing
The tests performed by the tester shall be able to concentrate on EFC-communication protocol aspects, which
are:
 initialization phase (BST-VST exchange);
 application layer services according to EN 12834;
 EFC functions and services according to ISO 14906:2011;
 EFC data and parameters used according to ISO 14906:2011; and
 transaction phase (logical sequence).
The DUT shall be operated in a controlled environment according to the manufacturer's instructions.
All test suites shall be generated corresponding to the specification of the manufacturer, which shall describe
the behaviour of the DUT in terms of expected messages from the beacon and intended answers from the
DUT. The communication sequence shall be unambiguously defined. The test generation tool shall be able to
check the messages against the European or International DSRC standards. All events of a DUT are stored
by the tester.
The test suites generated shall strictly correspond to the European or International DSRC standards and to
ISO 14906:2011.
The results of the tests shall only be related to the IUT of the DUT. Only the correctness of the implementation
shall be tested, and any assessment of performance, robustness or reliability is excluded. The results of the
tests shall be able to provide confidence that the DUT works according to ICS, the underlying DSRC
standards and to ISO 14906:2011, within the scope of the performed tests.
6.3 Test documentation
The test documentation shall provide comprehensive information of the used tester, the DUT, the tests carried
out, and the gathered test results.
14 © ISO 2011 – All rights reserved

---------------------- Page: 19 ----------------------
ISO/TS 14907-2:2011(E)
6.3.1 Tester
All relevant information and specifications of the used tester shall be documented in the test report.
The ICS and the IXIT shall be provided by the manufacturer or supplier of the DUT. The ICS and IXIT shall
describe all the capabilities and limitations of the DUT according to Annex A and Annex B, respectively.
6.3.2 Test methods and test cases
A test suite is required which covers all implemented and specified functions of the DUT to be tested based on
the provided ICS and IXIT. Completeness and correctness of the test suite is required to verify conformity
between IUT and specification, including the referenced standards.
The test suite is separated in test groups; each test group consists of a number of test cases. The tester shall
provide a tool which enables the user to specify the test suite and which provides documentation of the test
suite.
The user-defined test suite should be automatically translated in a computer form which is executable by the
tester.
6.3.3 Test results
Each test case carried out shall be documented by the test generation equipment. For each test case, a
verdict shall be given: passed, inconclusive or failed. The results of all test cases shall form the conformance
test report.

© ISO 2011 – All rights reserved 15

---------------------- Page: 20 ----------------------
ISO/TS 14907-2:2011(E)
Annex A
(normative)

Implementation conformance statement pro forma
The forms in this
...