ISO 16484-6:2005

Building automation and control systems (BACS) — Part 6: Data communication conformance testing

ISO 16484-6:2005 defines a standard method for verifying that an implementation of the BACnet protocol provides each capability claimed in its Protocol Implementation Conformance Statement (PICS) in conformance with the BACnet standard (ISO 16484-5). ISO 16484-6:2005 provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS, including the following: support of each claimed BACnet service, either as an initiator, executor, or both; support of each claimed BACnet object-type, including both required properties and each claimed optional property; support of the BACnet network layer protocol; support of each claimed data link option; support of all claimed special functionality.

Systèmes d'automatisation et de gestion technique du bâtiment — Partie 6: Essais de conformité de la communication de données

General Information

• Status: Withdrawn
• Publication Date: 06-Dec-2005
• Withdrawal Date: 06-Dec-2005
• ICS: 35.240.67 - IT applications in building and construction industry
• ICS: 91.040.01 - Buildings in general
• Technical Committee: ISO/TC 205 - Building environment design
• Drafting Committee: ISO/TC 205/WG 3 - Building Automation and Control System (BACS) Design
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 09-Feb-2009

Relations

• Consolidates: ISO 5495:1983 - Sensory analysis — Methodology — Paired comparison test
• Effective Date: 06-Jun-2022
• Revised: ISO 16484-6:2009 - Building automation and control systems (BACS) — Part 6: Data communication conformance testing
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 16484-6
First edition
2005-12-15


Building automation and control systems
(BACS) —
Part 6:
Data communication conformance testing
Systèmes d'automatisation et de gestion technique du bâtiment —
Partie 6: Essais de conformité de la communication de données




Reference number
ISO 16484-6:2005(E)
©
 ISO 2005

---------------------- Page: 1 ----------------------
ISO 16484-6:2005(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO 2005
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

© ISO 2005 – All rights reserved
ii

---------------------- Page: 2 ----------------------
ISO 16484-6:2005(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.
Attention is drawn to the possibility that some of the elements of this Technical Report may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 16484-6 was prepared by the American Society of Heating, Refrigerating and Air-Conditioning
Engineers (ASHRAE) as ANSI/ASHRAE 135.1-2003, and was adopted (without modifications except those
stated in Clause 2 of this International Standard) by Technical Committee ISO/TC 205, Building environment
design.
ISO 16484 consists of the following parts, under the general title Building automation and control
systems (BACS):
Part 2: Hardware
Part 3: Functions
Part 5: Data communication protocol
Part 6: Data communication conformance testing
The task of updating this part of ISO 16484 has been delegated to an ISO Maintenance Agency. Details are
given in the "Maintenance" clause overleaf.


© ISO 2005 – All rights reserved iii

---------------------- Page: 3 ----------------------
INTERNATIONAL STANDARD ISO 16484-6:2005(E)

Building automation and control systems (BACS) —
Part 6:
Data communication conformance testing
Scope
This part of ISO 16484 defines a standard method for verifying that an implementation of the BACnet protocol
provides each capability claimed in its Protocol Implementation Conformance Statement (PICS) in conformance
with the BACnet standard (ISO 16484-5).
The scope is further detailed in Clause 2 of the enclosed ANSI/ASHRAE publication.
Recommendations
The technical recommendations are those made in the following publication (reproduced on the following pages),
which is adopted as an International Standard:
ANSI/ASHRAE 135.1-2003, Method for Test for Conformance to BACnet
International Standards cited in the text are the following:
ISO 16484-5, Building automation and control systems — Part 5: Data communication protocol
ISO 10646, Information technology — Universal Multiple-Octet Coded Character Set (UCS)
ISO/IEC 8802-2, Information technology — Telecommunications and information exchange between
systems — Local and metropolitan area networks — Specific requirements — Part 2: Logical link control
ISO/IEC 8802-3, Information technology — Telecommunications and information exchange between
systems — Local and metropolitan area networks — Specific requirements — Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method and physical layer
ISO/IEC 8859-1, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin
alphabet No. 1
Maintenance
The ISO Maintenance Agency for ISO 16484-5 and ISO 16484-6, as designated by the ISO Council, is
American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc.,
1791 Tullie Circle NE,
Atlanta,
GA 30329,
USA.
E-mail: [e-mail]
The procedures for the maintenance of ISO 16484-5 and ISO 16484-6 are available at
http://www.iso.org/tc205
or from the Maintenance Agency Secretariat at the above address.
© ISO 2005 – All rights reserved
1

---------------------- Page: 4 ----------------------
ISO 16484-6:2005(E)

© ISO 2005 – All rights reserved
2

---------------------- Page: 5 ----------------------
ISO 16484-6:2005(E)
Contents
CLAUSE PAGE
1. PURPOSE.7
2. SCOPE.7
3. DEFINITIONS .7
4. ELECTRONIC PICS FILE FORMAT .7
4.1 Character Encoding.7
4.2 Structure of EPICS Files.8
4.3 Character Strings.9
4.4 Notational Rules for Parameter Values.9
4.5 Sections of the EPICS File.10
5. EPICS CONSISTENCY TESTS .27
6. CONVENTIONS FOR SPECIFYING BACnet CONFORMANCE TESTS .28
6.1 TCSL Components.28
6.2 TCSL Statements .29
6.3 Time Dependencies.34
6.4 BACnet References.34
7. OBJECT SUPPORT TESTS.35
7.1 Read Support for Properties in the Test Database.35
7.2 Write Support for Properties in the Test Database.35
7.3 Object Functionality Tests .36
8. APPLICATION SERVICE INITIATION TESTS .106
8.1 AcknowledgeAlarm Service Initiation Tests .106
8.2 ConfirmedCOVNotification Service Initiation Tests.107
8.3 UnconfirmedCOVNotification Service Initiation Tests.116
8.4 ConfirmedEventNotification Service Initiation Tests.118
8.5 UnconfirmedEventNotification Service Initiation Tests.151
8.6 GetAlarmSummary Service Initiation Tests .158
8.7 GetEnrollmentSummary Service Initiation Tests .158
8.8 GetEventInformation Service Initiation Tests.160
8.9 LifeSafetyOperation Service Initiation Tests.160
8.10 SubscribeCOV Service Initiation Tests .161
8.11 SubscribeCOVProperty Service Initiation Tests.162
8.12 AtomicReadFile Service Initiation Tests .163
8.13 AtomicWriteFile Service Initiation Tests .163
8.14 AddListElement Service Initiation Tests .164
8.15 RemoveListElement Service Initiation Tests.165
8.16 CreateObject Service Initiation Tests.165
8.17 DeleteObject Service Initiation Tests.166
8.18 ReadProperty Service Initiation Tests.167
8.19 ReadPropertyConditional Service Initiation Tests.167
8.20 ReadPropertyMultiple Service Initiation Tests.168
8.21 ReadRange Service Initiation Tests .169
8.22 WriteProperty Service Initiation Tests.170
8.23 WritePropertyMultiple Service Initiation Tests .171
8.24 DeviceCommunicationControl Service Initiation Tests.173
8.25 ConfirmedPrivateTransfer Service Initiation Test .174
8.26 UnconfirmedPrivateTransfer Service Initiation Test .174
© ISO 2005 – All rights reserved
3

---------------------- Page: 6 ----------------------
ISO 16484-6:2005(E)
8.27 ReinitializeDevice Service Initiation Tests .175
8.28 ConfirmedTextMessage Service Initiation Tests .176
8.29 UnconfirmedTextMessage Service Initiation Tests .177
8.30 TimeSynchronization Service Initiation Tests .178
8.31 UTCTimeSynchronization Service Initiation Tests .178
8.32 Who-Has Service Initiation Tests.178
8.33 I-Have Service Initiation Tests.179
8.34 Who-Is Service Initiation Tests.179
8.35 I-Am Service Initiation Tests .180
8.36 VT-Open Service Initiation Tests.180
8.37 VT-Close Service Initiation Tests .181
8.38 VT-Data Service Initiation Tests.183
8.39 RequestKey Service Initiation Tests .184
8.40 Authenticate Service Initiation Tests .185
9. APPLICATION SERVICE EXECUTION TESTS.190
9.1 AcknowledgeAlarm Service Execution Tests.190
9.2 ConfirmedCOVNotification Service Execution Tests .203
9.3 UnconfirmedCOVNotification Service Execution Tests .207
9.4 ConfirmedEventNotification Service Execution Tests.207
9.5 UnconfirmedEventNotification Service Execution Tests.209
9.6 GetAlarmSummary Service Execution Tests.209
9.7 GetEnrollmentSummary Service Execution Tests .210
9.8 GetEventInformation Service Execution Tests .214
9.9 LifeSafetyOperation Service Execution Test .216
9.10 SubscribeCOV Service Execution Tests .218
9.11 SubscribeCOVProperty Service Execution Tests.223
9.12 AtomicReadFile Service Execution Tests.230
9.13 AtomicWriteFile Service Execution Tests .237
9.14 AddListElement Service Execution Tests.248
9.15 RemoveListElement Service Execution Tests.250
9.16 CreateObject Service Execution Tests .252
9.17 DeleteObject Service Execution Tests .255
9.18 ReadProperty Service Execution Tests .256
9.19 ReadPropertyConditional Service Execution Tests.258
9.20 ReadPropertyMultiple Service Execution Tests.259
9.21 ReadRange Service Execution Tests.264
9.22 WriteProperty Service Execution Tests .267
9.23 WritePropertyMultiple Service Execution Tests.270
9.24 DeviceCommunicationControl Service Execution Test.274
9.25 ConfirmedPrivateTransfer Service Execution Tests .278
9.26 UnconfirmedPrivateTransfer Service Execution Tests .278
9.27 ReinitializeDevice Service Execution Tests.278
9.28 ConfirmedTextMessage Service Execution Tests.281
9.29 UnconfirmedTextMessage Service Execution Tests.282
9.30 TimeSynchronization Service Execution Tests.282
9.31 UTCTimeSynchronization Service Execution Tests.284
9.32 Who-Has Service Execution Tests.284
9.33 Who-Is Service Execution Tests .290
9.34 VT-Open Service Execution Tests.293
9.35 VT-Close Service Execution Tests.295
9.36 VT-Data Service Execution Tests .296
9.37 RequestKey Service Execution Test .296
9.38 Authenticate Service Execution Tests.298
© ISO 2005 – All rights reserved
4

---------------------- Page: 7 ----------------------
ISO 16484-6:2005(E)
10. NETWORK LAYER PROTOCOL TESTS.304
10.1 Processing Application Layer Messages Originating from Remote Networks.304
10.2 Router Functionality Tests.304
10.3 Half-Router Functionality Tests.328
10.4 B/IP PAD Tests.336
10.5 Initiating Network Layer Messages .338
11. LOGICAL LINK LAYER PROTOCOL TESTS.340
11.1 UI Command and Response.340
11.2 XID Command and Response.340
11.3 TEST Command and Response .341
12. DATA LINK LAYER PROTOCOLS TESTS.342
12.1 MS/TP State Machine Tests.342
12.2 PTP State Machine Tests .399
13. SPECIAL FUNCTIONALITY TESTS.440
13.1 Segmentation .440
13.2 Time Master.449
13.3 Character Sets .450
13.4 Malformed PDUs.450
14. BACnet/IP Functionality Tests .453
14.1 Non-BBMD B/IP Device.453
14.2 Non-BBMD B/IP device Device with a Server Application.455
14.3 Broadcast Distribution Table Operations.456
14.4 Foreign Device Table Operations (Negative Tests).459
14.5 BACnet Broadcast Management (No Foreign Device Table, No Applications).460
14.6 Foreign Device Management.460
14.7 Broadcast Management (BBMD, Foreign Devices, Local Application).463
15. Reporting Test Results.467
ANNEX A - Example EPICS (INFORMATIVE) .468

























© ISO 2005 – All rights reserved
5

---------------------- Page: 8 ----------------------
ISO 16484-6:2005(E)

© ISO 2005 – All rights reserved
6

---------------------- Page: 9 ----------------------
ISO 16484-6:2005(E)
1. PURPOSE
To define a standard method for verifying that an implementation of the BACnet protocol provides each capability claimed in
its Protocol Implementation Conformance Statement (PICS) in conformance with the BACnet standard.

2. SCOPE
This standard provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed
on a BACnet PICS including:

(a) support of each claimed BACnet service, either as an initiator, executor, or both,
(b) support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(c) support of the BACnet network layer protocol,
(d) support of each claimed data link option, and
(e) support of all claimed special functionality.

3. DEFINITIONS
All definitions from ISO 16484-5 also apply to this standard.

3.1 local network: the network to which a BACnet device is directly connected.

3.2 remote network: a network that is accessible from a BACnet device only by passing through one or more routers.

3.3 test database: a database of BACnet functionality and objects created by reading the contents of an EPICS.

3.4 Abbreviations and Acronyms Used in the Standard

BNF Backus-Naur Form syntax
EPICS electronic protocol implementation conformance statement
IUT implementation under test
TCSL testing and conformance scripting language
TD testing device
TPI text protocol information

4. ELECTRONIC PICS FILE FORMAT
An electronic protocol implementation conformance statement (EPICS) file contains a BACnet protocol implementation
conformance statement expressed in a standardized text form. EPICS files are machine and human readable representations
of the implementation of BACnet objects and services within a given device. EPICS files shall use the extension ".TPI" (text
protocol information) and contain normal editable text lines consisting of text character codes ending in carriage
return/linefeed pairs (X'0D', X'0A').

EPICS files are used by software testing tools to conduct and interpret the results of tests defined in this standard. An EPICS
file shall accompany any device tested according to the procedures of this standard.
4.1 Character Encoding
BACnet provides for a variety of possible character encodings. The character encodings in BACnet fall into three groups:
octet streams, double octet streams and quad octet streams. Octet streams represent characters as single octet values. In some
cases, such as Microsoft DBCS and JIS C 6226, certain octet values signal that the second octet which follows should be
viewed along with the leading octet as a single value, thus
...