ISO 16484-5:2007

INTERNATIONAL ISO
STANDARD 16484-5
Second edition
2007-03-15
Building automation and control
systems —
Part 5:
Data communication protocol
Systèmes d'automatisation et de gestion technique du bâtiment —
Partie 5: Protocole de communication de données

Reference number
©
ISO 2007
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 2007
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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2007 – All rights reserved

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 document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 16484-5 was prepared by the American Society of Heating, Refrigerating and Air-Conditioning Engineers
(ASHRAE) (as ANSI/ASHRAE 135-2004) and was adopted without modifications by Technical Committee
ISO/TC 205, Building environment design.
This second edition cancels and replaces the first edition (ISO 16484-5:2003), which has been technically
revised, as detailed in the enclosed ANSI/ASHRAE publication, pages 598 to 601.
ISO 16484 consists of the following parts, under the general title Building automation and control systems:
⎯ Part 1: Overview and definitions
⎯ Part 2: Hardware
⎯ Part 3: Functions
⎯ Part 5: Data communication protocol
⎯ Part 6: Data communication conformance testing
Applications and project implementation are to form the subjects of future parts 4 and 7.

INTERNATIONAL STANDARD ISO 16484-5:2007(E)

Building automation and control systems —
Part 5:
Data communication protocol
1 Scope
This part of ISO 16484 defines data communication services and protocols for computer equipment used for
monitoring and control of heating, ventilation, air-conditioning and refrigeration (HVAC&R) and other building
systems. It defines, in addition, an abstract, object-oriented representation of information communicated
between such equipment, thereby facilitating the application and use of digital control technology in buildings.
The scope and field of application are furthermore detailed in Clause 2 of the enclosed ANSI/ASHRAE
publication.
2 Requirements
Requirements are the technical recommendations made in the following publication (reproduced on the
following pages), which is adopted as an International Standard:
ANSI/ASHRAE 135-2004, A Data Communication Protocol for Building Automation and Control
Networks
The text on the back of the title page of the ANSI/ASHRAE standard and the policy statement on the last page
are not relevant for the purposes of international standardization.
The following International Standards are cited in the text:
ISO/IEC 7498 (all parts), Information technology — Open Systems Interconnection — Basic Reference Model
ISO/TR 8509, Information processing systems — Open Systems Interconnection — Service conventions
ISO/IEC 8649, Information technology — Open Systems Interconnection — Service definition for the
Association Control Service Element
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 specifications
ISO/IEC 8824 (all parts), Information technology — Abstract Syntax Notation One (ASN.1)
ISO/IEC 8825 (all parts), Information technology — ASN.1 encoding rules
ISO/IEC 8859-1, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin
alphabet No. 1
ISO/IEC 9545, Information technology — Open Systems Interconnection — Application Layer structure
ISO/IEC 10646, Information technology — Universal Multiple-Octet Coded Character Set (UCS)
3 Revision of ANSI/ASHRAE 135
It has been agreed with the American Society of Heating, Refrigerating and Air-Conditioning Engineers
(ASHRAE) that Technical Committee ISO/TC 205 will be consulted in the event of any revision or amendment
of ANSI/ASHRAE 135. To this end, ANSI will act as a liaison body between ASHRAE and ISO.

2 © ISO 2007 – All rights reserved

ANSI/ASHRAE Standard 135-2004
(Including ANSI/ASHRAE addenda listed in the History of Revisions) ®
ASHRAE
STANDARD
BACnet® —
A Data Communication
Protocol for Building
Automation and
Control Networks
Approved by the ASHRAE Standards Committee October 5,
2003; by the ASHRAE Board of Directors Jaunaru 29, 2004; and
by the American National Standards Institute February 25,
2004. See "History of Revisions" section for approval dates of
addenda.
This standard is under continuous maintenance by a Standing
Standard Project Committee (SSPC) for which the Standards
Committee has established a documented program for reqular
publication of addenda or revisions, including procdedures for
timely, documented, consensus action on requests for change
to any part of the standard. The change submittal form,
instructions and deadlines are given at the back of this
document and may be obtained in electronic form from
ASHRAE's Internet Home Page, http://www.ashrae.org, or in
paper form from the Manager of Standards. The latest edition
of an ASHRAE Standard and printed copies of a public review
draft may be purchased from ASHRAE Customer Service, 1791
Tullie Circle, NE, Atlanta, GA 30329-2305. E-mail:
orders@ashrae.org. Fax: 404-321-5478. Telephone: 404-636-
8400 (worldwide), or toll free 1-800-527-4723 (for orders in U.S.
and Canada).
© 2004 American Society of Heating, Refrigerating and Air-
Conditioning Engineers, Inc.
ISSN 1041-2336
AMERICAN SOCIETY OF HEATING,
REFRIGERATING AND
AIR-CONDITIONING ENGINEERS, INC.
1791 Tullie Circle, NE · Atlanta GA 30329-2305
(Blank page)
4 © ISO 2007 – All rights reserved

ASHRAE STANDING STANDARD PROJECT COMMITTEE 135
Cognizant TC: TC 1.4, Control Theory and Applications
SPLS Liaison: Frank E. Jakob
Steven T. Bushby, Chair* Troy D. Cowan* Mark A. Railsback
William O. Swan III, Vice-Chair Daniel P. Giorgis David W. Robin
Carl Neilson, Secretary* Thomas S. Ertsgaard* Ernest L. Senior
Barry B. Bridges* Craig P. Gemmill* Daniel A. Traill*
James F. Butler* Robert L. Johnson J. Michael Whitcomb*
A. J. Capowski* Stephen T. Karg* David F. White
Keith A. Corbett J. Damian Ljungquist* Grant N. Wichenko
Jeffery Cosiol Jerald P. Martocci
*Denotes members of voting status when this standard was approved for publication.

The following persons served as consultants to the project committee:

Andrey Golovin H. Michael Newman David H. Ritter
David G. Holmberg René Quirighetti Takeji Toyoda
__________________________________________________________________________________________________________________

ASHRAE STANDARDS COMMITTEE 2003-2004
Van D. Baxter, Chair Matt R. Hargan Cyrus H. Nasseri
Davor Novosel, Vice-Chair Richard D. Hermans Gideon Shavit
Donald B. Bivens John F. Hogan David R. Tree
Dean S. Borges Frank E. Jakob Thomas H. Williams
Paul W. Cabot Stephen D. Kennedy James E. Woods
Charles W. Coward, Jr. David E. Knebel Kent W. Peterson, CO
Hugh F. Crowther Frederick H. Kohloss Ross D. Montgomery, BOD ExO
Brian P. Dougherty Merle F. McBride
Hakim Elmahdy Mark P. Modera
Claire B. Ramspeck, Manager of Standards
__________________________________________________________________________________________________________________
SPECIAL NOTE
This American National Standard (ANS) is a national voluntary consensus standard developed under the auspices of the American Society of Heating,
Refrigerating and Air-Conditioning Engineers (ASHRAE). Consensus is defined by the American National Standards Institute (ANSI), of which ASHRAE is a
member and which has approved this standard as an ANS, as "substantial agreement reached by directly and materially affected interest categories. This signifies
the concurrence of more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that an effort
be made toward their resolution." Compliance with this standard is voluntary until and unless a legal jurisdiction makes compliance mandatory through
legislation.
ASHRAE obtains consensus through participation of its national and international members, associated societies, and public review.

ASHRAE Standards are prepared by a Project Committee appointed specifically for the purpose of writing the Standard. The Project Committee Chair and Vice-
Chair must be members of ASHRAE; while other members may or may not be members of ASHRAE, all must be technically qualified in the subject area of the
standard. Every effort is made to balance the concerned interests on all Project Committees.

The Manager of Standards of ASHRAE should be contacted for:
a. interpretation of the contents of this Standard,
b. participation in the next review of the Standard,
c. offering constructive criticism for improving the Standard,
d. permission to reprint portions of the Standard.
DISCLAIMER
ASHRAE uses its best efforts to promulgate standards for the benefit of the public in light of available information and accepted industry practices. However,
ASHRAE does not guarantee, certify, or assure the safety or performance of any products, components, or systems tested, designed, installed, or operated in
accordance with ASHRAE's Standards or Guidelines or that any tests conducted under its standards will be nonhazardous or free from risk.

ASHRAE INDUSTRIAL ADVERTISING POLICY ON STANDARDS

ASHRAE Standards and Guidelines are established to assist industry and the public by offering a uniform method of testing for rating purposes, by
suggesting safe practices in designing and installing equipment, by providing proper definitions of this equipment, and by providing other information that
may serve to guide the industry. The creation of ASHRAE Standards and Guidelines is determined by the need for them, and conformance to them is
completely voluntary.
In referring to this standard and marking of equipment and in advertising, no claim shall be made, either stated or implied, that the product has been approved
by ASHRAE.
(Blank page)
6 © ISO 2007 – All rights reserved

CONTENTS
FOREWORD ………………………………………………………………………………………………………………….vii
1 PURPOSE. 1
2 SCOPE. 1
3 DEFINITIONS. 1
3.1 Terms Adopted from International Standards. 1
3.2 Terms Defined for this Standard. 2
3.3 Abbreviations and Acronyms Used in this Standard. 5
4 BACnet PROTOCOL ARCHITECTURE . 8
4.1 The BACnet Collapsed Architecture. 9
4.2 BACnet Network Topology . 11
4.3 Security. 13
5 THE APPLICATION LAYER. 14
5.1 The Application Layer Model . 14
5.2 Segmentation of BACnet Messages. 18
5.3 Transmission of BACnet APDUs . 19
5.4 Application Protocol State Machines. 23
5.5 Application Protocol Time Sequence Diagrams. 37
5.6 Application Layer Service Conventions. 45
6 THE NETWORK LAYER. 47
6.1 Network Layer Service Specification . 47
6.2 Network Layer PDU Structure . 48
6.3 Messages for Multiple Recipients. 53
6.4 Network Layer Protocol Messages . 54
6.5 Network Layer Procedures. 56
6.6 BACnet Routers. 58
6.7 Point-To-Point Half-Routers . 63
7 DATA LINK/PHYSICAL LAYERS: ISO 8802-3 ("Ethernet") LAN. 68
7.1 The Use of ISO 8802-2 Logical Link Control (LLC) . 68
7.2 Parameters Required by the LLC Primitives . 68
7.3 Parameters Required by the MAC Primitives. 68
7.4 Physical Media . 68
8 DATA LINK/PHYSICAL LAYERS: ARCNET LAN. 70
8.1 The Use of ISO 8802-2 Logical Link Control (LLC) . 70
8.2 Parameters Required by the LLC Primitives . 70
8.3 Mapping the LLC Services to the ARCNET MAC Layer. 70
8.4 Parameters Required by the MAC Primitives. 70
8.5 Physical Media . 70
9 DATA LINK/PHYSICAL LAYERS: MASTER-SLAVE/TOKEN PASSING (MS/TP) LAN. 72
9.1 Service Specification . 72
9.2 Physical Layer . 74
9.3 MS/TP Frame Format . 76
9.4 Overview of the MS/TP Network. 77
9.5 MS/TP Medium Access Control. 78
9.6 Cyclic Redundancy Check (CRC) . 94
9.7 Interfacing MS/TP LANs with Other BACnet LANs . 95
9.8 Responding BACnet User Processing of Messages from MS/TP. 95
9.9 Repeaters. 95
10 DATA LINK/PHYSICAL LAYERS: POINT-TO-POINT (PTP). 97
10.1 Overview. 97
10.2 Service Specification . 97
10.3 Point-to-Point Frame Format. 102
10.4 PTP Medium Access Control Protocol . 104
11 DATA LINK/PHYSICAL LAYERS: EIA/CEA-709.1 ("LonTalk") LAN. 125
11.1 The Use of ISO 8802-2 Logical Link Control (LLC) . 125
11.2 Parameters Required by the LLC Primitives . 125
ASHRAE 135-2004 i
11.3 Mapping the LLC Services to the LonTalk Application Layer. 125
11.4 Parameters Required by the Application Layer Primitives. 125
11.5 Physical Media . 126
12 MODELING CONTROL DEVICES AS A COLLECTION OF OBJECTS. 127
12.1 Accumulator Object Type . 130
12.2 Analog Input Object Type. 138
12.3 Analog Output Object Type . 143
12.4 Analog Value Object Type. 148
12.5 Averaging Object Type. 153
12.6 Binary Input Object Type. 156
12.7 Binary Output Object Type . 161
12.8 Binary Value Object Type. 167
12.9 Calendar Object Type . 172
12.10 Command Object Type . 174
12.11 Device Object Type . 178
12.12 Event Enrollment Object Type . 185
12.13 File Object Type . 190
12.14 Group Object Type . 192
12.15 Life Safety Point Object Type . 194
12.16 Life Safety Zone Object Type . 200
12.17 Loop Object Type. 206
12.18 Multi-state Input Object Type . 213
12.19 Multi-state Output Object Type. 217
12.20 Multi-state Value Object Type . 221
12.21 Notification Class Object Type. 226
12.22 Program Object Type. 229
12.23 Pulse Converter Object Type. 234
12.24 Schedule Object Type . 241
12.25 Trend Log Object Type. 246
13 ALARM AND EVENT SERVICES. 252
13.1 Change of Value Reporting. 253
13.2 Intrinsic Reporting. 255
13.3 Algorithmic Change Reporting. 258
13.4 Alarm and Event Occurrence and Notification. 266
13.5 AcknowledgeAlarm Service. 269
13.6 ConfirmedCOVNotification Service. 271
13.7 UnconfirmedCOVNotification Service. 273
13.8 ConfirmedEventNotification Service. 274
13.9 UnconfirmedEventNotification Service . 277
13.10 GetAlarmSummary Service. 279
13.11 GetEnrollmentSummary Service . 281
13.12 GetEventInformation Service . 284
13.13 LifeSafetyOperation Service . 286
13.14 SubscribeCOV Service . 288
13.15 SubscribeCOVProperty Service . 290
14 FILE ACCESS SERVICES . 293
14.1 AtomicReadFile Service . 294
14.2 AtomicWriteFile Service. 297
15 OBJECT ACCESS SERVICES. 299
15.1 AddListElement Service . 299
15.2 RemoveListElement Service . 301
15.3 CreateObject Service . 303
15.4 DeleteObject Service . 305
15.5 ReadProperty Service. 306
15.6 ReadPropertyConditional Service. 308
15.7 ReadPropertyMultiple Service. 313
15.8 ReadRange Service. 316
ii ASHRAE 135-2004
8 © ISO 2007 – All rights reserved

15.9 WriteProperty Service. 320
15.10 WritePropertyMultiple Service. 322
16 REMOTE DEVICE MANAGEMENT SERVICES. 325
16.1 DeviceCommunicationControl Service. 325
16.2 ConfirmedPrivateTransfer Service . 327
16.3 UnconfirmedPrivateTransfer Service. 329
16.4 ReinitializeDevice Service . 330
16.5 ConfirmedTextMessage Service. 332
16.6 UnconfirmedTextMessage Service . 334
16.7 TimeSynchronization Service. 335
16.8 UTCTimeSynchronization Service . 336
16.9 Who-Has and I-Have Services. 337
16.10 Who-Is and I-Am Services . 339
17 VIRTUAL TERMINAL SERVICES. 341
17.1 Virtual Terminal Model . 341
17.2 VT-Open Service. 345
17.3 VT-Close Service . 347
17.4 VT-Data Service. 348
17.5 Default-terminal Characteristics. 350
18 ERROR, REJECT, and ABORT CODES. 354
18.1 Error Class - DEVICE. 354
18.2 Error Class - OBJECT. 354
18.3 Error Class - PROPERTY. 354
18.4 Error Class - RESOURCES. 355
18.5 Error Class - SECURITY. 355
18.6 Error Class - SERVICES. 356
18.7 Error Class - VT . 357
18.8 Reject Reason . 357
18.9 Abort Reason. 358
19 BACnet PROCEDURES. 359
19.1 Backup and Restore . 359
19.2 Command Prioritization . 362
20 ENCODING BACnet PROTOCOL DATA UNITS. 366
20.1 Encoding the Fixed Part of BACnet APDUs. 366
20.2 Encoding the Variable Part of BACnet APDUs . 376
21 FORMAL DESCRIPTION OF APPLICATION PROTOCOL DATA UNITS. 390
22 CONFORMANCE AND INTEROPERABILITY . 434
22.1 Conformance to BACnet. 434
22.2 BACnet Interoperability. 435
23 EXTENDING BACnet TO ACCOMMODATE VENDOR PROPRIETARY INFORMATION . 437
23.1 Extending Enumeration Values . 437
23.2 Using the PrivateTransfer Services to Invoke Non-Standardized Services . 437
23.3 Adding Proprietary Properties to a Standardized Object. 438
23.4 Adding Proprietary Object Types to BACnet. 438
23.5 Restrictions on Extending BACnet. 439
24 NETWORK SECURITY . 440
24.1 Security Architecture. 440
24.2 Authentication Mechanisms . 441
24.3 Data Confidentiality Mechanism . 443
24.4 RequestKey Service. 444
24.5 Authenticate Service . 445
25 REFERENCES. 448
ANNEX A - PROTOCOL IMPLEMENTATION CONFORMANCE STATEMENT (NORMATIVE) . 450
ANNEX B - GUIDE TO SPECIFYING BACnet DEVICES (INFORMATIVE). 452
ANNEX C - FORMAL DESCRIPTION OF OBJECT TYPE STRUCTURES (INFORMATIVE). 453
ANNEX D - EXAMPLES OF STANDARD OBJECT TYPES (INFORMATIVE). 465
D.1 Example of an Accumulator Object. 465
ASHRAE 135-2004 iii
D.2 Example of an Analog Input Object. 465
D.3 Example of an Analog Output Object . 466
D.4 Example of an Analog Value Object. 466
D.5 Example of an Averaging Object. 467
D.6 Example of a Binary Input Object . 467
D.7 Example of a Binary Output Object. 468
D.8 Example of a Binary Value Object . 469
D.9 Example of a Calendar Object. 470
D.10 Example of a Command Object. 470
D.11 Example of a Device Object. 471
D.12 Example of an Event Enrollment Object. 473
D.13 Example of a File Object. 475
D.14 Example of a Group Object. 475
D.15 Example of a Life Safety Point Object. 475
D.16 Example of a Life Safety Zone Object. 476
D.17 Example of a Loop Object. 477
D.18 Example of a Multi-state Input Object . 478
D.19 Example of a Multi-state Output Object . 479
D.20 Example of a Multi-state Value Object . 480
D.21 Example of a Notification Class Object . 480
D.22 Example of a Program Object. 480
D.23 Example of a Pulse Converter Object . 482
D.24 Example of a Schedule Object. 482
D.25 Example of a Trend Log Object . 483
ANNEX E - EXAMPLES OF BACnet APPLICATION SERVICES (INFORMATIVE). 485
E.1 Alarm and Event Services . 485
E.2 File Access Services . 489
E.3 Object Access Services . 491
E.4 Remote Device Management Services. 498
E.5 Virtual Terminal Services .
...

NORME ISO
INTERNATIONALE 16484-5
Deuxième édition
2007-03-15
Systèmes d'automatisation et de gestion
technique du bâtiment —
Partie 5:
Protocole de communication de données
Building automation and control systems —
Part 5: Data communication protocol

Numéro de référence
©
ISO 2007
PDF – Exonération de responsabilité
Les fichiers PDF peuvent contenir des polices de caractères intégrées. Conformément aux conditions de licence d'Adobe, ils peuvent
être imprimés ou visualisés, mais ne doivent pas être modifiés à moins que l'ordinateur employé à cet effet ne bénéficie d'une licence
autorisant l'utilisation de ces polices et que celles-ci y soient installées. Lors du téléchargement de fichiers PDF, les parties
concernées acceptent de fait la responsabilité de ne pas enfreindre les conditions de licence d'Adobe. Le Secrétariat central de l'ISO
décline toute responsabilité en la matière.
Adobe est une marque déposée d'Adobe Systems Incorporated.
Les détails relatifs aux produits logiciels utilisés pour la création du ou des fichiers PDF qui constituent cette publication sont
disponibles dans la rubrique General Info des fichiers; les paramètres de création PDF ont été optimisés pour l'impression. Toutes les
mesures ont été prises pour garantir l'exploitation de ces fichiers par les comités membres de l'ISO. Dans le cas peu probable où
surviendrait un problème d'utilisation, veuillez en informer le Secrétariat central à l'adresse donnée ci-dessous.

Le présent CD-ROM contient la publication ISO 16484-5:2007 au format PDF (portable document format), qui
peut être visualisée en utilisant Adobe® Acrobat® Reader.
Adobe et Acrobat sont des marques déposées de Adobe Systems Incorporated.

Cette deuxième édition annule et remplace la première édition (ISO 16484-5:2003), qui a fait l'objet d'une
révision technique.
DOCUMENT PROTÉGÉ PAR COPYRIGHT

©  ISO 2007
Tous droits réservés. Sauf exigence particulière d'installation et sauf stipulation contraire, aucune partie de ce CD-ROM ne peut être
reproduite, enregistrée dans un système d'extraction ou transmise, sous quelque forme que ce soit et par aucun procédé, sans l'accord
préalable de l'ISO. Les demandes d'autorisation de reproduction de ce produit doivent être envoyées à l'adresse ci-après.
...

NORME ISO
INTERNATIONALE 16484-5
Deuxième édition
2007-03-15
Systèmes d'automatisation et de gestion
technique du bâtiment —
Partie 5:
Protocole de communication de données
Building automation and control systems —
Part 5: Data communication protocol

Numéro de référence
©
ISO 2007
PDF – Exonération de responsabilité
Le présent fichier PDF peut contenir des polices de caractères intégrées. Conformément aux conditions de licence d'Adobe, ce fichier
peut être imprimé ou visualisé, mais ne doit pas être modifié à moins que l'ordinateur employé à cet effet ne bénéficie d'une licence
autorisant l'utilisation de ces polices et que celles-ci y soient installées. Lors du téléchargement de ce fichier, les parties concernées
acceptent de fait la responsabilité de ne pas enfreindre les conditions de licence d'Adobe. Le Secrétariat central de l'ISO décline toute
responsabilité en la matière.
Adobe est une marque déposée d'Adobe Systems Incorporated.
Les détails relatifs aux produits logiciels utilisés pour la création du présent fichier PDF sont disponibles dans la rubrique General Info
du fichier; les paramètres de création PDF ont été optimisés pour l'impression. Toutes les mesures ont été prises pour garantir
l'exploitation de ce fichier par les comités membres de l'ISO. Dans le cas peu probable où surviendrait un problème d'utilisation,
veuillez en informer le Secrétariat central à l'adresse donnée ci-dessous.

DOCUMENT PROTÉGÉ PAR COPYRIGHT

©  ISO 2007
Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publication ne peut être reproduite ni utilisée sous
quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les microfilms, sans l'accord écrit
de l'ISO à l'adresse ci-après ou du comité membre de l'ISO dans le pays du demandeur.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Version française parue en 2009
Publié en Suisse
ii © ISO 2007 – Tous droits réservés

Avant-propos
L'ISO (Organisation internationale de normalisation) est une fédération mondiale d'organismes nationaux de
normalisation (comités membres de l'ISO). L'élaboration des Normes internationales est en général confiée
aux comités techniques de l'ISO. Chaque comité membre intéressé par une étude a le droit de faire partie du
comité technique créé à cet effet. Les organisations internationales, gouvernementales et non
gouvernementales, en liaison avec l'ISO participent également aux travaux. L'ISO collabore étroitement avec
la Commission électrotechnique internationale (CEI) en ce qui concerne la normalisation électrotechnique.
Les Normes internationales sont rédigées conformément aux règles données dans les Directives ISO/CEI,
Partie 2.
La tâche principale des comités techniques est d'élaborer les Normes internationales. Les projets de Normes
internationales adoptés par les comités techniques sont soumis aux comités membres pour vote. Leur
publication comme Normes internationales requiert l'approbation de 75 % au moins des comités membres
votants.
L'attention est appelée sur le fait que certains des éléments du présent document peuvent faire l'objet de
droits de propriété intellectuelle ou de droits analogues. L'ISO ne saurait être tenue pour responsable de ne
pas avoir identifié de tels droits de propriété et averti de leur existence.
L’ISO 16484-5 a été préparée par l’American Society of Heating, Refrigerating and Air-Conditioning Engineers
(ASHRAE) (comme l’ANSI/ASHRAE 135-2004) et a été adoptée sans modifications par le comité technique
ISO/TC 205, Conception de l’environnement intérieur des bâtiments.
Cette deuxième édition annule et remplace la première édition (ISO 16484-5:2003), qui a fait l’objet d’une
révision technique comme indiqué dans la publication ANSI/ASHRAE jointe, pages 598 à 601.
L'ISO 16484 comprend les parties suivantes, présentées sous le titre général Systèmes d'automatisation et
de gestion technique du bâtiment :
⎯ Partie 1: Vue d’ensemble et définitions
⎯ Partie 2: Équipement
⎯ Partie 3: Fonctions
⎯ Partie 5: Protocole de communication de données
⎯ Partie 6: Essais de conformité de la communication de données
Les applications et la mise en œuvre de projets seront abordées dans les futures parties 4 et 7.
NORME INTERNATIONALE ISO 16484-5:2007(F)

Systèmes d'automatisation et de gestion technique du
bâtiment —
Partie 5:
Protocole de communication de données
1 Domaine d'application
La présente partie de l’ISO 16484 définit les protocoles et les services de communication de données de
l’équipement de traitement de données, dans le cadre des fonctions de surveillance et de contrôle des
systèmes de chauffage, de ventilation, de conditionnement d’air et de réfrigération (CVCR) et d’autres
systèmes du bâtiment. Elle définit, en outre, une représentation abstraite, orientée objets, des informations
communiquées entre ces équipements, en facilitant l’application et l’utilisation de la technologie du contrôle
numérique dans les bâtiments. Le domaine et le champ d’application sont détaillés plus précisément à
l'Article 2 de la publication ANSI/ASHRAE jointe.
2 Exigences
Les exigences correspondent aux recommandations techniques indiquées dans la publication suivante
(reproduite aux pages suivantes), adoptée en tant que Norme internationale:
ANSI/ASHRAE 135-2004, A Data Communication Protocol for Building Automation and Control Networks
Le texte figurant au verso de la page de titre de la norme ANSI/ASHRAE et les instructions générales de la
dernière page ne sont pas applicables pour les besoins de normalisation internationale.
Les Normes internationales suivantes sont citées dans le texte:
ISO/CEI 7498 (toutes les parties), Technologies de l'information — Interconnexion de systèmes ouverts
(OSI) — Modèle de référence de base
ISO/TR 8509, Systèmes de traitement de l'information — Interconnexion de systèmes ouverts — Conventions
de service
ISO/CEI 8649, Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Définition de
service applicable à l'élément de service de contrôle d'association
ISO/CEI 8802-2, Technologies de l'information — Télécommunications et échange d'information entre
systèmes — Réseaux locaux et métropolitains — Exigences spécifiques — Partie 2:: Contrôle de liaison
logique
ISO/CEI 8802-3, Technologies de l'information — Télécommunications et échange d'information entre
systèmes — Réseaux locaux et métropolitains — Prescriptions spécifiques — Partie 3: Accès multiples par
surveillance du signal et détection de collision (CSMA/CD) et spécifications pour la couche physique
ISO/CEI 8824 (toutes les parties), Technologies de l'information — Notation de syntaxe abstraite numéro un
(ASN.1)
ISO/CEI 8825 (toutes les parties), Technologies de l'information — Règles de codage ASN.1
ISO/CEI 8859-1, Technologies de l'information — Jeux de caractères graphiques codés sur un seul octet —
Partie 1: Alphabet latin n° 1
ISO/CEI 9545, Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Structure de la
couche application
ISO/CEI 10646, Technologies de l'information — Jeu universel de caractères codés sur plusieurs octets
(JUC)
3 Révision de l’ANSI/ASHRAE 135
Il a été convenu avec l’American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE)
que le comité technique ISO/TC 205 serait consulté en cas de révision ou d’amendement de l’ANSI/ASHRAE
135. À ces fins, l’ANSI agira en tant qu’organisme de liaison entre l’ASHRAE et l’ISO.
2 © ISO 2007 – Tous droits réservés

ANSI/ASHRAE Standard 135-2004
(Including ANSI/ASHRAE addenda listed in the History of
Revisions)
ASHRAE®
STANDARD
BACnet® —
A Data Communication
Protocol for Building
Automation and
Control Networks
Approved by the ASHRAE Standards Committee October 5,
2003; by the ASHRAE Board of Directors Jaunaru 29, 2004; and
by the American National Standards Institute February 25,
2004. See "History of Revisions" section for approval dates of
addenda.
This standard is under continuous maintenance by a Standing
Standard Project Committee (SSPC) for which the Standards
Committee has established a documented program for reqular
publication of addenda or revisions, including procdedures for
timely, documented, consensus action on requests for change
to any part of the standard. The change submittal form,
instructions and deadlines are given at the back of this
document and may be obtained in electronic form from
ASHRAE's Internet Home Page, http://www.ashrae.org, or in
paper form from the Manager of Standards. The latest edition
of an ASHRAE Standard and printed copies of a public review
draft may be purchased from ASHRAE Customer Service, 1791
Tullie Circle, NE, Atlanta, GA 30329-2305. E-mail:
orders@ashrae.org. Fax: 404-321-5478. Telephone: 404-636-
8400 (worldwide), or toll free 1-800-527-4723 (for orders in U.S.
and Canada).
© 2004 American Society of Heating, Refrigerating and Air-
Conditioning Engineers, Inc.
ISSN 1041-2336
AMERICAN SOCIETY OF HEATING,
REFRIGERATING AND
AIR-CONDITIONING ENGINEERS, INC.
1791 Tullie Circle, NE · Atlanta GA 30329-2305

ASHRAE STANDING STANDARD PROJECT COMMITTEE 135
Cognizant TC: TC 1.4, Control Theory and Applications
SPLS Liaison: Frank E. Jakob
Steven T. Bushby, Chair* Troy D. Cowan* Mark A. Railsback
William O. Swan III, Vice-Chair Daniel P. Giorgis David W. Robin
Carl Neilson, Secretary* Thomas S. Ertsgaard* Ernest L. Senior
Barry B. Bridges* Craig P. Gemmill* Daniel A. Traill*
James F. Butler* Robert L. Johnson J. Michael Whitcomb*
A. J. Capowski* Stephen T. Karg* David F. White
Keith A. Corbett J. Damian Ljungquist* Grant N. Wichenko
Jeffery Cosiol Jerald P. Martocci
*Denotes members of voting status when this standard was approved for publication.
The following persons served as consultants to the project committee:
Andrey Golovin H. Michael Newman David H. Ritter
David G. Holmberg René Quirighetti Takeji Toyoda
ASHRAE STANDARDS COMMITTEE 2003-2004
Van D. Baxter, Chair Matt R. Hargan Cyrus H. Nasseri
Davor Novosel, Vice-Chair Richard D. Hermans Gideon Shavit
Donald B. Bivens John F. Hogan David R. Tree
Dean S. Borges Frank E. Jakob Thomas H. Williams
Paul W. Cabot Stephen D. Kennedy James E. Woods
Charles W. Coward, Jr David E. Knebel Kent W. Peterson, CO
Hugh F. Crowther Frederick H. Kohloss Ross D. Montgomery, BOD ExO
Brian P. Dougherty Merle F. McBride
Hakim Elmahdy Mark P. Modera
Claire B. Ramspeck, Manager of Standards
SPECIAL NOTE
This American National Standard (ANS) is a national voluntary consensus standard developed under the auspices of the American Society of Heating,
Refrigerating and Air-Conditioning Engineers (ASHRAE). Consensus is defined by the American National Standards Institute (ANSI), of which ASHRAE is a
member and which has approved this standard as an ANS, as "substantial agreement reached by directly and materially affected interest categories. This
signifies the concurrence of more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and
that an effort be made toward their resolution." Compliance with this standard is voluntary until and unless a legal jurisdiction makes compliance mandatory
through legislation.
ASHRAE obtains consensus through participation of its national and international members, associated societies, and public review.
ASHRAE Standards are prepared by a Project Committee appointed specifically for the purpose of writing the Standard. The Project Committee Chair and
Vice-Chair must be members of ASHRAE; while other members may or may not be members of ASHRAE, all must be technically qualified in the subject area
of the standard. Every effort is made to balance the concerned interests on all Project Committees.
The Manager of Standards of ASHRAE should be contacted for:
a. interpretation of the contents of this Standard,
b. participation in the next review of the Standard,
c. offering constructive criticism for improving the Standard,
d. permission to reprint portions of the Standard.
DISCLAIMER
ASHRAE uses its best efforts to promulgate standards for the benefit of the public in light of available information and accepted industry practices. However,

ASHRAE does not guarantee, certify, or assure the safety or performance of any products, components, or systems tested, designed, installed, or operated
in accordance with ASHRAE's Standards or Guidelines or that any tests conducted under its standards will be nonhazardous or free from risk.

ASHRAE INDUSTRIAL ADVERTISING POLICY ON STANDARDS
ASHRAE Standards and Guidelines are established to assist industry and the public by offering a uniform method of testing for rating purposes, by

suggesting safe practices in designing and installing equipment, by providing proper definitions of this equipment, and by providing other information that may
serve to guide the industry. The creation of ASHRAE Standards and Guidelines is determined by the need for them, and conformance to them is completely

voluntary.
In referring to this standard and marking of equipment and in advertising, no claim shall be made, either stated or implied, that the product has been

approved by ASHRAE.
4 © ISO 2007 – Tous droits réservés

(page blanche)
Sommaire Page
Avant-propos. 14
1 Objectif. 17
2 Domaine d’application . 17
3 Définitions . 17
3.1 Termes adoptés par les Normes internationales . 17
3.2 Termes définis pour la présente norme . 19
3.3    Abréviations et Acronymes utilisés dans la présente norme . 22
4 Architecture du protocole BACnet. 25
4.1 L’architecture réduite BACnet. 27
4.2 Topologie du réseau BACnet . 29
4.3 Sécurité. 30
5 La couche application . 31
5.1 Le modèle de couche application . 31
5.2 Segmentation des messages BACnet . 35
5.3 Transmission des APDU BACnet. 37
5.4 Machines à états de protocole d'application . 42
5.5 Diagrammes de séquence temporelle de protocole d'application . 58
5.6 Conventions de service de couche application . 66
6 La couche réseau. 67
6.1 Spécification de service de couche réseau . 68
6.2 Structure de PDU de la couche réseau .69
6.3 Messages pour destinataires multiples .74
6.4 Messages de protocole de couche réseau . 75
6.5 Procédures de la couche réseau. 78
6.6 Routeurs BACnet. 80
6.7 Demi-routeurs point à point. 86
7 Couches liaison de données/physique : ISO 8802-3 (Ethernet) LAN. 91
7.1 Utilisation de la procédure LLC ISO 8802-2 . 91
7.2 Paramètres requis par les primitives LLC.91
7.3 Paramètres requis par les primitives MAC . 91
7.4 Supports physiques . 91
8 Couches liaison de données/physique : LAN ARCNET. 92
8.1 Utilisation de la procédure LLC ISO 8802-2 . 92
8.2 Paramètres requis par les primitives LLC.93
8.3 Mappage des services LLC sur la couche MAC ARCNET. 93
8.4 Paramètres requis par les primitives MAC . 93
8.5 Supports physiques . 93
9 Couches liaison de données/physique : LAN Maître-esclave/passage de jeton (MS/TP). 94
9.1 Spécification de service. 95
9.2 Couche physique. 97
9.3 Format de trame MS/TP. 99
9.4 Vue d'ensemble du réseau MS/TP . 101
9.5 MAC MS/TP. 102
9.6 Contrôle de redondance cyclique (CRC). 120
6 © ISO 2007 – Tous droits réservés

9.7 Interfaçage des LAN MS/TP avec d'autres LAN BACnet.121
9.8 Réponse au traitement de messages utilisateur BACnet de MS/TP .121
9.9 Répéteurs .121
10 Couches liaison de données/Physique : Point à point (PTP) .123
10.1 Vue d'ensemble .123
10.2 Spécification de service.124
10.3 Format de trame point à point.129
10.4 Protocole MAC PTP.132
11 COUCHES LIAISON DE DONNÉES/PHYSIQUE : LAN EIA/CEA-709.1 (« LonTalk ») .155
11.1 Utilisation de la procédure LLC ISO 8802-2.155
11.2 Paramètres requis par les primitives LLC .155
11.3 Mappage des services LLC sur la couche application LonTalk.155
11.4 Paramètres requis par les primitives de la couche application .155
11.5 Supports physiques.156
12 MODÉLISATION DES DISPOSITIFS DE COMMANDE COMME UNE COLLECTION
D’OBJETS.157
12.1 Type d’objet Accumulator .160
12.2 Type d’objet Analog Input .170
12.3 Type d’objet Analog Output .176
12.4 Type d’objet Analog Value .182
12.5 Type d’objet Averaging.188
12.6 Type d’objet Binary Input .192
12.7 Type d’objet Binary Output .198
12.8 Type d’objet Binary Value .205
12.9 Type d’objet Calendar.211
12.10 Type d’objet Command.213
12.11 Type d’objet Device.217
12.12 Type d’objet Event Enrollment.225
12.13 Type d’objet File .230
12.14 Type d’objet Group.233
12.15 Type d’objet Life Safety Point .235
12.16 Type d’objet Life Safety Zone .243
12.17 Type d’objet Loop.251
12.18 Type d’objet Multi-state Input .258
12.19 Type d’objet Multi-state Output .263
12.20 Type d’objet Multi-state Value.268
12.21 Type d’objet Notification Class.274
12.22 Type d’objet Program.277
12.23 Type d’objet Pulse Converter.282
12.24 Type d’objet Schedule .290
12.25 Type d’objet Trend Log.296
13 SERVICES D’ALARME ET D’ÉVÉNEMENT.303
13.1 Rapport de changement de valeur .304
13.2 Rapport intrinsèque .306
13.3 Rapport de changement algorithmique .311
13.4 Occurrence et notification d’alarme et d’événement.320
13.5 Service AcknowledgeAlarm .323
13.6 Service ConfirmedCOVNotification.325
13.7 Service UnconfirmedCOVNotification.327
13.8 Service ConfirmedEventNotification.329
13.9 Service UnconfirmedEventNotification.332
13.10 Service GetAlarmSummary .335
13.11 Service GetEnrollmentSummary .337
13.12 Service GetEventInformation .340
13.13 Service LifeSafetyOperation .343
13.14 Service SubscribeCOV.345
13.15 Service SubscribeCOVProperty.347
14 SERVICES D’ACCÈS AUX FICHIERS. 350
14.1 Service AtomicReadFile. 351
14.2 Service AtomicWriteFile. 354
15 SERVICES D'ACCÈS AUX OBJETS . 357
15.1 Service AddListElement. 357
15.2 Service RemoveListElement. 359
15.3 Service CreateObject. 361
15.4 Service DeleteObject . 364
15.5 Service ReadProperty . 366
15.6 Service ReadPropertyConditional. 368
15.7 Service ReadPropertyMultiple. 374
15.8 Service ReadRange . 378
15.9 Service WriteProperty . 383
15.10 Service WritePropertyMultiple. 386
16 SERVICES DE GESTION DES DISPOSITIFS DISTANTS . 390
16.1 Service DeviceCommunicationControl . 390
16.2 Service ConfirmedPrivateTransfer. 392
16.3 Service UnconfirmedPrivateTransfer . 394
16.4 Service ReinitializeDevice. 395
16.5 Service ConfirmedTextMessage . 397
16.6 Service UnconfirmedTextMessage . 399
16.7 Service TimeSynchronization. 401
16.8 Service UTCTimeSynchronization . 402
16.9 Services Who-Has et I-Have . 403
16.10 Services Who-Is et I-Am. 406
17 SERVICES DE TERMINAL VIRTUEL. 409
17.1 Modèle de terminal virtuel . 409
17.2 Service VT-Open . 413
17.3 Service VT-Close. 415
17.4 Service VT-Data. 417
17.5 Caractéristiques du terminal par défaut. 419
18 CODES ERREUR, REJET et ABANDON . 423
18.1 Error Class - DEVICE. 423
18.2 Error Class - OBJECT. 423
18.3 Error Class - PROPERTY . 424
18.4 Error Class - RESOURCES . 425
18.5 Error Class - SECURITY . 426
18.6 Error Class - SERVICES . 427
18.7 Error Class - VT. 428
18.8 Raison du rejet. 429
18.9 Raison de l’abandon. 430
19 PROCÉDURES BACnet . 431
19.1 Sauvegarde et restauration . 431
19.2 Hiérarchisation des commandes . 435
20 CODAGE DES UNITÉS DE DONNÉES DU PROTOCOLE BACnet . 440
20.1 Codage de la partie fixe des APDU BACnet. 440
20.2 Codage de la partie variable des APDU BACnet . 453
21 DESCRIPTION FORMELLE DES UNITÉS DE DONNÉES DE PROTOCOLE D’APPLICATION. 468
22 CONFORMITÉ ET INTEROPÉRABILITÉ. 512
22.1 Conformité à BACnet . 512
22.2 Interopérabilité BACnet. 513
23 EXTENSION DE BACnet POUR LA PRISE EN CHARGE D’INFORMATIONS
PROPRIÉTAIRES DU FOURNISSEUR. 516
23.1 Extension des valeurs d’énumération. 516
23.2 Utilisation des services PrivateTransfer pour invoquer des services non normalisés . 517
8 © ISO 2007 – Tous droits réservés

23.3 Ajout de propriétés propriétaires à un objet normalisé .517
23.4 Ajout de types d’objets propriétaires à BACnet .518
23.5 Restrictions relatives à l’extension de BACnet.518
24 SÉCURITÉ DU RÉSEAU .519
24.1 Architecture de sécurité .519
24.2 Mécanismes d’authentification .520
24.3 Mécanisme de confidentialité des données .523
24.4 Service RequestKey.524
24.5 Service Authenticate.525
25 RÉFÉRENCES .529
ANNEXE A - CERTIFICAT DE CONFORMITÉ DE MISE EN ŒUVRE DU PROTOCOLE .531
ANNEXE B – GUIDE TO SPECIFYING BACnet DEVICES (INFORMATIVE) .533
ANNEXE C – FORMAL DESCRIPTION OF OBJECT TYPE STRUCTURES (INFORMATIVE) .534
ANNEXE D – EXAMPLES OF STANDARD OBJECT TYPES (INFORMATIVE).546
D.1 Example of an Accumulator object .546
D.2 Example of an Analog Input Object.546
D.3 Example of an Analog Output Object.547
D.4 Example of an Analog Value Object.547
D.5 Example of an Averaging Object .548
D.6 Examples of a Binary Input Object.548
D.7 Examples of a Binary Output Object.549
D.8 Example of a Binary Value Object .550
D.9 Example of a Calendar Object.551
D.10 Examples of a Command Object .551
D.11 Examples of a Device Object .552
D.12 Examples of an Event Enrollment Object .554
D.13 Example of a File Object.556
D.14 Example of a Group Object .556
D.15 Example of a Life Safety Point Object.556
D.16 Example of a Life Safety Zone Object .557
D.17 Example of a Loop Object .558
D.18 Examples of a Multi-state Input Object .559
D.19 Examples of a Multi-state Output Object .560
D.20 Example of a Multi-state Value Object .561
D.21 Example of a Notification Class Object.561
D.22 Examples of a Program Object .561
D.23 Example of a Pulse Converter Object .563
D.24 Example of a Schedule Object .563
D.25 Example of a Trend Log Object .564
ANNEXE E – EXAMPLES OF BACnet APPLICATION SERVICES (INFORMATIVE).566
E.1 Alarm and Event Services .566
E.1.1 Examples of the AcknowledgeAlarm Service .566
E.1.2 Example of the ConfirmedCOVNotification Service .566
E.1.3 Example of the UnconfirmedCOVNotification Service .566
E.1.4 Example of the ConfirmedEventNotification Service .566
E.1.5 Example of the UnconfirmedEventNotification Service.567
E.1.6 Example of the GetAlarmSummary Service .568
E.1.7 Examples of the GetEnrollmentSummary Service.568
E.1.8 Example of the GetEventInformation Service .569
E.1.9 Example of the LifeSafetyOperation Service.569
E.1.10 Example of the SubscribeCOV Service.570
E.1.11 Example of the SubscribeCOVProperty Service.570
E.2 File Access Services.570
E.2.1 Examples of the AtomicReadFile Service.570
E.2.2 Examples of the AtomicWriteFile Service.571
E.3 Object Access Services.572
E.3.1 Example of the AddListElement Service.572
E.3.2 Example of the RemoveListElement Service .573
E.3.3 Example of the CreateObject Service.574
E.3.4 Example of the DeleteObject Service . 575
E.3.5 Examples of the ReadProperty Service.
...