EN 61375-3-2:2012

SLOVENSKI STANDARD
01-oktober-2012
äHOH]QLãNHHOHNWURQVNHQDSUDYH.RPXQLNDFLMVNRRPUHåMHYODNDGHO09%
3UHVNXãDQMHXVWUH]QRVWLYHþQDPHQVNHJDSRGDWNRYQHJDYRGLODYR]LOD,(&

Electronic railway equipment - Train communication network - Part 3-2: MVB -
Multipurpose Vehicle Bus conformance testing (IEC 61375-3-2:2012)
Elektronische Betriebsmittel für Bahnen - Zug-Kommunikations-Netzwerk - Teil 3-2: MVB
(Multipurpose-Vehicle-Bus) Konformitätsprüfung (IEC 61375-3-2:2012)
Matériel électronique ferroviaire - Réseau embarqué de train (TCN) - Partie 3-2: Essais
de conformité MVB (Bus de véhicule multifonctions) (CEI 61375-3-2:2012)
Ta slovenski standard je istoveten z: EN 61375-3-2:2012
ICS:
45.020 Železniška tehnika na Railway engineering in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 61375-3-2
NORME EUROPÉENNE
August 2012
EUROPÄISCHE NORM
ICS 45.060
English version
Electronic railway equipment -
Train communication network (TCN) -
Part 3-2: MVB (Multifunction Vehicle Bus) conformance testing
(IEC 61375-3-2:2012)
Matériel électronique ferroviaire -  Elektronische Betriebsmittel für Bahnen -
Réseau embarqué de train (TCN) - Zug-Kommunikations-Netzwerk -
Partie 3-2: Essais de conformité MVB Teil 3-2: MVB (Multipurpose-Vehicle-Bus)
(Bus de Véhicule Multifonctions) Konformitätsprüfung
(CEI 61375-3-2:2012) (IEC 61375-3-2:2012)

This European Standard was approved by CENELEC on 2012-07-26. CENELEC members are bound to comply
with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard
the status of a national standard without any alteration.

Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the CEN-CENELEC Management Centre or to any CENELEC member.

This European Standard exists in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CENELEC member into its own language and notified
to the CEN-CENELEC Management Centre has the same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus,
the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany,
Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Management Centre: Avenue Marnix 17, B - 1000 Brussels

© 2012 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 61375-3-2:2012 E
Foreword
The text of document 9/1645/FDIS, future edition 1 of IEC 61375-3-2, prepared by IEC/TC 9 "Electrical
equipment and systems for railways" was submitted to the IEC-CENELEC parallel vote and approved by
CENELEC as EN 61375-3-2:2012.
The following dates are fixed:
(dop) 2013-04-26
• latest date by which the document has
to be implemented at national level by
publication of an identical national
standard or by endorsement
• latest date by which the national (dow) 2015-07-26

standards conflicting with the
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent
rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association, and supports essential requirements of EU Directive(s).

For the relationship with EU Directive(s) see informative Annex ZZ, which is an integral part of this
document.
Endorsement notice
The text of the International Standard IEC 61375-3-2:2012 was approved by CENELEC as a European
Standard without any modification.

- 3 - EN 61375-3-2:2012
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications

The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.

NOTE  When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year

IEC 60063 1963 Preferred number series for resistors and - -
+ A1 1967 capacitors
+ A2 1977
IEC 60571 - Electronic equipment used on rail vehicles - -

IEC 60807 Series Rectangular connectors for frequencies below - -
3 MHz
IEC 61375-2-1 - Electronic railway equipment - Train EN 61375-2-1 -
communication network (TCN) -
Part 2-1: Wire Train Bus (WTB)

IEC 61375-2-2 - Electronic railway equipment - Train EN 61375-2-2 -
communication network (TCN) -
Part 2-2: Wire Train Bus conformance testing

IEC 61375-3-1 - Electronic railway equipment - Train EN 61375-3-1 -
communication network (TCN) -
Part 3-1: Multifunction Vehicle Bus (MVB)

ISO/IEC 8482 1993 Information technology - Telecommunications - -
and information exchange between systems -
Twisted pair multipoint interconnections

ISO/IEC 9646-1 1994 Information technology - Open Systems - -
Interconnection - Conformance testing
methodology and framework -
Part 1: General concepts
ISO/IEC 9646-7 1995 Information technology - Open Systems - -
Interconnection - Conformance testing
methodology and framework -
Part 7: Implementation Conformance
Statements
Annex ZZ
(informative)
Coverage of Essential Requirements of EU Directives

This European Standard has been prepared under a mandate given to CENELEC by the
European Commission and the European Free Trade Association and within its scope the
standard covers all relevant essential requirements as given in Annex III of the EU Directive
2008/57/EC.
Compliance with this standard provides one means of conformity with the specified essential
requirements of the Directive concerned.

WARNING: Other requirements and other EU Directives may be applicable to the products
falling within the scope of this standard.

IEC 61375-3-2 ®
Edition 1.0 2012-06
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Electronic railway equipment – Train communication network (TCN) –

Part 3-2: MVB (Multifunction Vehicle Bus) conformance testing

Matériel électronique ferroviaire – Réseau embarqué de train (TCN) –

Partie 3-2: Essais de conformité MVB (Bus de Véhicule Multifonctions)

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XD
ICS 45.060 ISBN 978-2-88912-071-0

– 2 – 61375-3-2  IEC:2012
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
2 Normative references . 8
3 Terms and definitions . 9
4 Conformance test: approach, requirements and boundaries . 9
4.1 Approach . 9
4.1.1 Requirements . 9
4.1.2 Requirements declaration statements for an IUT . 11
4.2 Boundaries . 12
4.2.1 General . 12
4.2.2 Basic interconnection tests . 13
4.2.3 Capability tests . 13
4.2.4 Behaviour tests. 14
4.2.5 Conformance resolution tests . 14
4.2.6 Interpretation of clauses/subclauses and statements . 15
4.2.7 Relation to interoperability . 17
4.2.8 Relation to performance test . 17
4.3 Conformance assessment process outline . 18
4.3.1 General . 18
4.3.2 Analysis of results, outcomes and verdicts . 18
5 Conformance test of an MVB device . 19
5.1 PICS . 19
5.1.1 Instructions for filling the PICS pro-forma . 19
5.1.2 PICS tables . 21
5.2 Test suites . 29
5.2.1 Basic interconnection tests . 29
5.2.2 Capability tests . 30
5.2.3 Behavioural tests . 31
5.2.4 Electrical short distance medium . 31
5.2.5 Electrical middle distance medium . 35
5.2.6 Slave device status test suites . 40
5.2.7 Process data test suites . 48
5.2.8 Slave message data capability test suite . 60
5.2.9 MVB repeater conformance tests . 77
6 Conformance test of RTP . 86
6.1 General . 86
6.2 Ports and Traffic_Store . 86
6.3 Dataset consistency . 86
6.3.1 Error handling . 87
6.3.2 Freshness supervision . 87
6.3.3 Synchronisation dataset . 87
6.3.4 Dataset polling . 87
6.3.5 Dataset, port and logical address . 87
6.3.6 Traffic_Store Identifier . 87

61375-3-2  IEC:2012 – 3 –
6.4 Port_Address . 88
6.5 Link_Process_Data_Interface primitives . 88
6.6 Messages services and protocols . 88
7 Conformance test of NM . 88
Annex A (normative) Test laboratory role and client role . 89
Annex B (informative) Test instrumentation and dedicated test beds . 96
Bibliography . 98

Figure 1 – Application of the waveshaper . 29
Figure 2 – ESD test layout . 31
Figure 3 – ESD terminator connector test . 33
Figure 4 – ESD waveform measurement . 34
Figure 5 – Measurement of an EMD device . 36
Figure 6 – Measurement of insertion loss . 37
Figure 7 – EMD transmitter test circuits . 38
Figure 8 – Example of test hardware implementation . 49
Figure 9 – F_code + Address . 54
Figure 10 – Concept of message data testing . 60
Figure 11 – Model of the relation between TE and IUT for message data testing . 61
Figure 12 – Relation between TE and IUT in case of test of IUT as caller . 61
Figure 13 – Packet formats (transport layer body) . 62
Figure 14 – Test message task of IUT . 63
Figure 15 – Caller timeout identification . 66
Figure 16 – Nesting address with 0x83 . 71
Figure 17 – Block diagram of a line . 77
Figure 18 – Frames in test RP-1.2 . 78
Figure 19 – Inter-frame spacing . 79
Figure 20 – Pulse distortion . 80
Figure 21 – Frame with out-of-place transition . 80
Figure 22 – Frames in test RP-1.4 . 81
Figure B.1 – Test bed configuration MRTB1 . 96
Figure B.2 – Test bed configuration MRTB2 . 97

Table 1 – Document structure . 7
Table 2 – Continuance indication . 16
Table 3 – Weak statements . 17
Table 4 – Relation to interoperability . 17
Table 5 – Relation to performance test . 17
Table 6 – ESD basic interconnection tests . 30
Table 7 – EMD basic interconnection tests . 30
Table 8 – Measurement idle . 32
Table 9 – Measurement with load for minimum current . 32
Table 10 – Measurement with load for maximum current . 32

– 4 – 61375-3-2  IEC:2012
Table 11 – Measurement with load for overcurrent . 33
Table 12 – ESD measurements pin to pin . 33
Table 13 – Event poll strategy. 64
Table 14 – Abbreviations . 68
Table 15 – Addressing type . 68
Table 16 – Test function directory . 70
Table 17 – Test station directory . 71
Table 18 – Nesting address . 72
Table 19 – Read_Memory and Write_Memory sequence . 73
Table 20 – Configuration of periodic data in BA . 84
Table 21 – Configuration of periodic ports in CU-1 . 84
Table 22 – Configuration of periodic ports in CU-2 . 85

61375-3-2  IEC:2012 – 5 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ELECTRONIC RAILWAY EQUIPMENT –
TRAIN COMMUNICATION NETWORK (TCN) –

Part 3-2: MVB (Multifunction Vehicle Bus) conformance testing

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 61375-3-2 has been prepared by IEC Technical Committee 9:
Electrical equipment and systems for railways.
This first edition cancels the clauses of the IEC 61375-2 first edition published in 2007
relevant to the specification of MVB conformance testing and constitutes a technical revision.
It was prepared taking into account the IEC 61375-3-1 first edition.

– 6 – 61375-3-2  IEC:2012
The text of this standard is based on the following documents:
FDIS Report on voting
9/1645/FDIS 9/1669/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of IEC 61375 series, under the general title Electronic railway equipment –
Train communication network (TCN), can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
61375-3-2  IEC:2012 – 7 –
INTRODUCTION
TCN is an International Standard with the aim of defining interfaces so as to achieve plug-in
compatibility:
a) between equipment located in different vehicles, and
b) between equipment and devices located within the same vehicle.
One of the key success factors for the deployment of any technology is standardisation and
ensuring interoperability among various implementations. To facilitate interoperability a
conformance test should be implemented.
In this part of IEC 61375, the conformace testing of the MVB defined in IEC 61375-3-1 is
specified.
This standard is structured into 5 clauses and 2 annexes.
The clauses and annexes are listed and briefly described in Table 1.
Table 1 – Document structure
Clause Description
1 Scope This clause describes the scope of this standard and.
2. Normative references This clause contains a list of referred norms.
3 Terms and definitions This clause introduces basic terms and abbreviations not
reported in IEC 61375-3-1.
4 Conformance test: approach, This clause is an overview of the methods of TCN
requirements and boundaries implementation verification that are available to the
developer and regulatory personnel.
Supplies information concerning the ICS and IXITpPro-
forma(s).
5 Conformance test of an MVB This clause covers all tests on MVB devices that are
device grouped by classes, from Class 0 up to Class 4. The main
contents are:
the MVB PICS and PIXIT;
the MVB test suites;
the MVB test procedures.
6 Conformance test of RTP This clause covers the conformance tests of real time
protocols.
7 Conformance test of NM This clause covers network management services’ testing.
Annex A – Test laboratory role and This annex is normative.
client role
Annex B – Test instrumentation and This annex is informative.
dedicated test beds
– 8 – 61375-3-2  IEC:2012
ELECTRONIC RAILWAY EQUIPMENT –
TRAIN COMMUNICATION NETWORK (TCN) –

Part 3-2: MVB (Multifunction Vehicle Bus) conformance testing

1 Scope
This part of IEC 61375 applies to all equipment and devices implemented according to
IEC 61375-3-1, i.e. it covers the procedures to be applied to such equipment and devices
when the conformance should be proven.
The applicability of this standard to a TCN implementation allows for individual conformance
checking of the implementation itself and is a pre-requisite for further interoperability checking
between different TCN implementations.
NOTE 1 An example of TCN implementation is given in UIC 556.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 60063: 1963, Preferred number series for resistors and capacitors
Amendment 1:1967
Amendment 2:1977
IEC 60571: Electronic equipment used on rail vehicles
IEC 60807 (all parts), Rectangular connectors for frequencies below 3 MHz
IEC 61375-2-1: Electronic railway equipment – Train Communication Network (TCN) –
Part 2-1: Wire Train Bus (WTB)
IEC 61375-2-2: Electronic railway equipment – Train Communication Network (TCN) –
Part 2-2: Wire Train Bus conformance testing
IEC 61375-3-1: Electronic railway equipment – Train Communication Network (TCN) –
Part 3-1: Multifunction Vehicle Bus (MVB)
ISO/IEC 8482: 1993, Information technology – Telecommunications and information exchange
between systems – Twisted pair multipoint interconnections
ISO/IEC 9646-1:1994, Information technology – Open Systems Interconnection –
Conformance testing methodology and framework – Part 1: General concepts (Also available
as ITU-T Recommendation X.290 (1995))
ISO/IEC 9646-7:1995, Information technology – Open Systems Interconnection –Conformance
testing methodology and framework – Part 7: Implementation Conformance Statements (Also
available as ITU-T Recommendation X.296 (1995))

61375-3-2  IEC:2012 – 9 –
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 9646-1 and
IEC 61375-3-1 apply.
4 Conformance test: approach, requirements and boundaries
4.1 Approach
This standard specifies a general methodology for testing the conformance to the TCN
protocol standard of products in which the standard is claimed to be implemented.
This standard is organised into clauses structured into different phases of the conformance
testing process, these phases being characterised by the following roles:
a) the specification of abstract test suites for particular TCN protocols according to ISO/IEC
9646-1;
b) the derivation of executable test suites and associated testing tools according to ISO/IEC
9646-7;
Annex A specifies the rules on clients and laboratory specifying:
c) the role of a client of a test laboratory, having an implementation of TCN protocols to be
tested;
d) the operation of conformance testing, culminating in the production of a conformance test
report which gives the results in terms of the test suite(s) used and the relevant
documentation produced.
In all clauses of this standard, the scope is limited in order to meet the following objectives:
e) to achieve an adequate level of confidence in the tests as a guide to conformance;
f) to achieve comparability between the results of the corresponding tests applied in different
places at different times;
g) to facilitate communication between the parties responsible for the roles described above.
Each objective involves the framework for development of TCN test suites, as listed
hereinafter:
h) how they should relate to the various types of conformance requirement;
i) the types of test to be standardised and the types not needing standardisation;
j) the criteria for selecting tests for inclusion in a conformance test suite;
k) the notation to be used for defining tests;
l) the structure of a test suite.
Certification, an administrative procedure which may follow conformance testing, is outside
the scope of this standard.
Requirements for procurement and contracts are outside the scope of this standard.
4.1.1 Requirements
4.1.1.1 General
In the context of TCN, a real system is said to exhibit conformance if it complies with the
requirements of applicable TCN standard clauses in its communication with a reference
system, i.e. the tester.
– 10 – 61375-3-2  IEC:2012
A TCN standard is a set of interrelated clauses which, together, define behaviour of TCN
systems in their communication. Conformance of an IUT will, therefore, be expressed at two
levels, conformance to each individual clause, and conformance to the set of clauses.
The following clauses define the conformance requirements and classify them according to
attributes and into feasible groups. Attributes and grouping are defined from the general point
of view with reference to a TCN specification itself and from the IUT point of view. In the
second case, the requirement shall be declared in the appropriate PICS and PIXIT.
4.1.1.2 Conformance requirements
The conformance requirements can be:
a) mandatory requirements: these are to be observed in all cases;
b) conditional requirements: these are to be observed if the conditions, set out in the clause,
apply;
c) options: these can be selected to suit the implementation, provided that any requirements
applicable to the option are observed.
TCN essential functionality are mandatory requirements; additional functionality can be either
conditional or optional requirements.
Furthermore, conformance requirements in a Part can be stated:
d) positively: they state what shall be done;
e) negatively (prohibitions): they state what shall not be done.
Finally, conformance requirements fall into two groups:
f) static conformance requirements;
g) dynamic conformance requirements;
these are discussed in 4.1.1.3 and 4.1.1.4, respectively.
4.1.1.3 Static conformance requirements
To facilitate interoperability static conformance requirements define the allowed minimum
capabilities of an implementation. These requirements may be at a broad level, such as the
grouping of functional units and options into protocol classes, or at a detailed level, such as a
range of values that have to be supported for specific parameters of timers.
Static conformance requirements and options in TCN parts can be of two varieties:
a) those which determine the capabilities to be included in the implementation of the
particular protocol;
b) those which determine multi-layer dependencies, for example those which place
constraints on the capabilities of the underlying layers of the system in which the protocol
implementation resides. These are likely to be found in upper layer parts (e.g. network
management vs real time protocols).
All capabilities not explicitly stated as static conformance requirements are to be regarded as
optional.
4.1.1.4 Dynamic conformance requirements
Dynamic conformance requirements are all those requirements (and options) which determine
what observable behaviour is permitted by the relevant TCN part in instances of
communication. They form the bulk of each TCN protocol document. They define the set of
allowable behaviours of an implementation or real system. This set defines the maximum

61375-3-2  IEC:2012 – 11 –
capability that a conforming implementation or real system can have within the terms of the
TCN protocol document.
A system exhibits dynamic conformance in an instance of communication if its behaviour is a
member of the set of all behaviours permitted by the relevant TCN protocol part in a way
which is consistent with the PICS.
4.1.1.4.1 A conforming system
A conforming system or implementation is one which is shown to satisfy both static and
dynamic conformance requirements, consistent with the capabilities stated in the PICS, for
each protocol declared in the system conformance statement.
4.1.1.4.2 Interoperability and conformance
The primary purpose of conformance testing is to increase the probability that different
implementations are able to inter-operate.
Successful interoperability of two or more real open systems is more likely to be achieved if
they all conform to the same subset of a TCN part, or to the same selection of TCN parts,
than if they do not.
To prepare two or more systems to successfully inter-operate, it is recommended that a
comparison is made of the system conformance statements and PICSs of these systems.
If there is more than one version of a relevant TCN part indicated in the PICSs, the
differences between the versions need to be identified and their implications for
consideration, including their use in combination with other parts.
While conformance is a necessary condition, it is not on its own a sufficient condition to
guarantee interoperability capability. Even if two implementations conform to the same TCN
protocol part, they may fail to interoperate because of factors outside the scope of this
standard.
Trial interoperability is recommended to detect these factors. Further information to assist
interoperability between two systems can be obtained by extending the PICS comparison to
other relevant information, including test reports and PIXIT. The comparison can focus on:
a) additional mechanisms claimed to work around known ambiguities or deficiencies not yet
corrected in the TCN standard or in peer real systems, for example solution of multi-layer
problems;
b) selection of free options which are not taken into account in the static conformance
requirements of the TCN parts;
c) the existence of timers not specified in the TCN parts and their associated values.
NOTE The comparison can be made between two individual systems, between two or more types of product, or,
for the PICS comparison only, between two or more specifications for procurement, permissions to connect, etc.
4.1.2 Requirements declaration statements for an IUT
4.1.2.1 Protocol implementation conformance statement (PICS)
To evaluate the conformance of a particular implementation, it is necessary to have a
statement of the capabilities and options which have been implemented, and any features
which have been omitted, so that the implementation can be tested for conformance against
relevant requirements, and against those requirements only. Such a statement is called a
Protocol Implementation Conformance Statement (PICS).

– 12 – 61375-3-2  IEC:2012
In a PICS there should be a distinction between the following categories of information which
it may contain:
a) information related to the mandatory, optional and conditional static conformance
requirements of the protocol itself;
b) information related to the mandatory, optional and conditional static conformance
requirements for multi-layer dependencies.
If a set of interrelated TCN protocol has been implemented in a system, a PICS is needed for
each protocol. A system conformance statement will also be necessary, summarising all
protocols in the system for each of which a distinct PICS is provided.
4.1.2.2 Protocol implementation extra information for testing (PIXIT)
In order to test a protocol implementation, the test laboratory will require information relating
to the IUT and its testing environment in addition to that provided by the PICS. This "Protocol
Implementation eXtra Information for Testing" (PIXIT) will be provided by the client submitting
the implementation for testing, as a result of consultation with the test laboratory.
The PIXIT may contain the following information:
a) information needed by the test laboratory in order to be able to run the appropriate test
suite on the specific system (e.g. information related to the test method to be used to run
the test cases, addressing information);
b) information already mentioned in the PICS and which needs to be made precise (e.g. a
timer value range which is declared as a parameter in the PICS should be specified in the
PIXIT);
c) information to help determine which capabilities stated in the PICS as being supported are
testable and which are untestable;
d) other administrative matters (e.g. the IUT identifier, reference to the related PICS).
The PIXIT should not conflict with the appropriate PICS.
The abstract test suite specifier, test implementor and test laboratory will all contribute to the
development of the PIXIT pro-forma.
4.2 Boundaries
4.2.1 General
Conformance testing as discussed in this standard is focused on testing for conformance to
TCN clauses as they are specified in IEC 61375-3-1.
In principle, the objective of conformance testing is to establish whether the implementation
being tested conforms to the specification in the relevant clause. Practical limitations make it
impossible to be exhaustive, and economic considerations may restrict testing still further.
Therefore, this standard distinguishes four types of testing, according to the extent to which
they provide an indication of conformance:
a) basic interconnection tests, which provide prima facie evidence that an IUT conforms;
b) capability tests, which check that the observable capabilities of the IUT are in accordance
with the static conformance requirements and the capabilities claimed in the PICS;
c) behaviour tests, which endeavour to provide testing which is as comprehensive as
possible over the full range of dynamic conformance requirements within the capabilities
of the IUT;
61375-3-2  IEC:2012 – 13 –
d) conformance resolution tests, which probe in depth the conformance of an IUT to
particular requirements, to provide a definite yes/no answer and diagnostic information in
relation to specific conformance issues; such tests are not covered by this standard.
Tests a), b), c) and d) are described in detail in the following subclauses.
Relations to interoperability and performance are hereinafter considered and defined to clarify
their boundaries.
4.2.2 Basic interconnection tests
Basic interconnection tests provide limited testing of an IUT to establish that there is sufficient
conformance for interconnection to be possible, without trying to perform thorough testing.
4.2.2.1 Applicability of basic interconnection tests
Basic interconnection tests are appropriate:
a) for detecting severe cases of non-conformance;
b) as a preliminary filter before undertaking more costly tests;
c) to give a prima facie indication that an implementation which has passed full conformance
tests in one environment still conforms in a new environment (e.g. before testing an (N)-
implementation, to check that a tested (N – 1)-implementation has not undergone any
severe change due to being linked to the (N)-implementation);
d) for use by users of implementations, to determine whether the implementations appear to
be usable for communication with other conforming implementations, for example as a
preliminary to data interchange.
Basic interconnection tests are inappropriate:
e) as a basis for claims of conformance by the supplier of an implementation;
f) as a means of arbitration to determine causes for communications failure.
Basic interconnection tests are standardised a subset of a conformance test suite (including
capability and behaviour tests). They can be used on their own or together with a
conformance test suite. The existence and execution of basic interconnection tests are
optional.
4.2.3 Capability tests
Capability tests provide limited testing of each of the static conformance requirements in a
Part, to ascertain what capabilities of the IUT can be observed and to check that those
observable capabilities are valid with respect to the static conformance requirements and the
PICS.
4.2.3.1 Applicability of capability tests
Capability tests are appropriate:
a) to check as far as possible the consistency of the PICS with the IUT;
b) as a preliminary filter before undertaking more in-depth and costly testing;
c) to check that the capabilities of the IUT are consistent with the static conformance
requirements;
d) to enable efficient selection of behaviour tests to be made for a particular IUT;
e) when taken together with behaviour tests, as a basis for claims of conformance.
Capability tests are inappropriate:

– 14 – 61375-3-2  IEC:2012
f) on their own, as a basis for claims of conformance by the supplier of an implementation;
g) for testing in detail the behaviour associated with each capability which has been
implemented or not implemented;
h) for resolution of
...