ANSI CTA-709.5-2015 Control Networking Protocol Specification Part 5 Implementation Application Layer Guidelines (Formerly ANSI CEA-709.5).pdf

1、 ANSI/CEA Standard Control Networking Protocol Specification Part 5: Implementation Application Layer Guidelines ANSI/CEA-709.5 September 2015 CEA-709.5 i FOREWORD This standard was developed by the Consumer Electronics Association under the auspices of the R7 Consumer Electronics Networking Committ

2、ee. CEA-709.5 ii CONTENTS INTRODUCTION . 1 TAGS . 1 OVERVIEW . 1 1 SCOPE 2 2 REFERENCES 2 2.1 NORMATIVE REFERENCES 2 2.1.1 Normative Reference List 3 2.1.2 Normative Reference Acquisition . 3 3 TERMS AND DEFINITIONS . 3 3.1 APPLICATION SET 3 3.2 BASE TYPE . 3 3.3 CHANGEABLE-TYPE NETWORK VARIABLE 3 3

3、.4 CONFIGURATION PROPERTY (CP) DATA VALUE USED TO CONFIGURE THE APPLICATION PROGRAM IN A DEVICE . 4 3.5 CONFIGURATION-PROPERTY MEMBER . 4 3.6 CONFIGURATION-PROPERTY MEMBER NUMBER 4 3.7 CONFIGURATION-PROPERTY TYPE INDEX 4 3.8 DEVICE . 4 3.9 DEVICE CHANNEL ID 4 3.10 DEVICE CLASS 4 3.11 DEVICE INTERFAC

4、E 4 3.12 DEVICE-LOCATION FIELD 4 3.13 DEVICE SELF-DOCUMENTATION STRING DSDS 5 3.14 DEVICE SUBCLASS . 5 3.15 DYNAMIC FUNCTIONAL BLOCK . 5 3.16 DYNAMIC NETWORK VARIABLE 5 3.17 FORMAT . 5 3.18 FUNCTIONAL BLOCK 5 3.19 FUNCTIONAL-BLOCK INDEX . 5 3.20 FUNCTIONAL PROFILE FP 5 3.21 FUNCTIONAL-PROFILE KEY 6

5、3.22 FUNCTIONAL-PROFILE MEMBER . 6 3.23 FUNCTIONAL-PROFILE MEMBER NUMBER 6 3.24 FUNCTIONAL-PROFILE NUMBER . 6 3.25 FUNCTIONAL-PROFILE SELECTOR 6 3.26 FUNCTIONAL-PROFILE TEMPLATE . 7 3.27 GLOBAL INDEX . 7 3.28 INHERITING PROFILE 7 3.29 INTEROPERABILITY 7 3.30 CNP DEVICE 7 3.31 CNP NETWORK . 7 3.32 MA

6、NUFACTURER ID MID 7 3.33 NETWORK-INTERFACE SELECTION . 7 3.34 NETWORK VARIABLE NV 8 3.35 NETWORK-VARIABLE DECLARATION 8 3.36 NETWORK-VARIABLE INDEX 8 3.37 NETWORK-VARIABLE MEMBER 8 3.38 NETWORK-VARIABLE MEMBER NUMBER 8 3.39 NETWORK-VARIABLE PROGRAMMATIC NAME . 8 3.40 NETWORK-VARIABLE SELECTION 8 3.4

7、1 NETWORK-VARIABLE TYPE 8 3.42 NETWORK-VARIABLE TYPE INDEX . 9 CEA-709.5 iii 3.43 UNIQUE NODE ID . 9 3.44 NODE . 9 3.45 PASSIVE CONFIGURATION TOOL PCT 9 3.46 PRIMARY FUNCTIONAL BLOCK . 9 3.47 PRIMARY FUNCTIONAL PROFILE . 9 3.48 PROPRIETARY DATA . 9 3.49 SELF-DOCUMENTATION STRING SD STRING 9 3.50 SEL

8、F-DOCUMENTATION TEXT 10 3.51 SHARED-MEDIA CHANNEL . 10 3.52 STANDARD CONFIGURATION-PROPERTY TYPE SCPT . 10 3.53 STANDARD NETWORK-VARIABLE TYPE SNVT 10 3.54 STANDARD PROGRAM ID SPID . 10 3.55 STATIC FUNCTIONAL BLOCK . 10 3.56 STATIC NETWORK VARIABLE 10 3.57 SUBSYSTEM . 10 3.58 SUCCESSFUL COMMISSIONIN

9、G . 11 3.59 SYSTEM 11 3.60 UNCONFIGURED DEVICE . 11 3.61 USAGE . 11 3.62 USAGE ID . 11 3.63 USER DATA 11 3.64 WINK FUNCTION . 11 4 DEVICE INTERFACES . 11 4.1 GENERAL 11 4.2 UNIQUE NODE ID 12 4.3 STANDARD PROGRAM ID . 13 4.3.1 GENERAL 13 4.4 GUIDELINE 4.3: A DEVICE SHALL IMPLEMENT A STANDARD PROGRAM

10、ID AS DEFINED IN 4.3, STANDARD PROGRAM ID 13 4.4.1 Format Field 13 4.4.2 Manufacturer Field . 13 4.4.3 Device Class Field 13 4.4.4 Usage Field . 14 4.4.4.1 General . 14 4.4.5 Channel Type Field 15 4.4.6 Model Number Field . 15 4.5 DEVICE CHANNEL ID . 15 4.6 DEVICE LOCATION FIELD 15 4.7 DEVICE SELF-D

11、OCUMENTATION STRING (DSDS) 16 4.8 FUNCTIONAL BLOCKS 17 4.8.1 General . 17 4.8.2 Implementing a Functional Block 19 4.8.3 Network Variables 20 4.8.4 Configuration Properties . 27 4.9 DEVICE AND FUNCTIONAL BLOCK VERSIONING . 38 4.10 DEVICE INTERFACE (XIF) FILE . 39 5 RESOURCE FILES . 40 5.1 RESOURCE F

12、ILE DEFINITIONS 40 5.1.2 Type Definitions 41 5.1.3 Functional Profiles 44 5.1.4 Language Strings 47 5.1.5 Formats . 48 5.2 IDENTIFYING APPROPRIATE RESOURCES 51 CEA-709.5 iv 5.2.1 Standard and User Resources . 51 5.2.2 Using Standard Resources 52 5.2.3 Using User Resources 52 6 NETWORK INSTALLATION .

13、 53 6.1 GENERAL 53 6.2 NETWORK ADDRESSING 54 6.2.1 Network Addressing Scheme 54 6.2.2 Address-Table Entries . 55 6.2.3 Network Variable Aliases 55 6.2.4 Domain-Table Entries . 56 6.2.5 Self-Installed Devices 57 6.2.6 Field-Installed Devices 57 6.3 PASSIVE CONFIGURATION TOOLS 58 6.4 SERVICE PIN 58 6.

14、5 GATEWAYS TO COMMAND-BASED SYSTEMS 59 6.6 SHARED-MEDIA CONSIDERATIONS 60 ANNEX A - DEVICE RESOURCE FILES (INFORMATIVE) . 61 CEA-709.5 1 Introduction This standard is prepared based upon work provided to the Consumer Electronics Association (CEA) R7 Consumer Electronics Networking Committee by LonMa

15、rk International, a non-profit standards development association. This work has been modified from its original creation to update it to the latest revision. Similar documents have been used in other international standards bodies. This standard is part of a series of standards for open data transmi

16、ssion in building automation, home automation and control, and in building management systems. The content of this standard covers the data communications used for management, automation/control and field functions. The CEA-709.5 is part of a series of ANSI/CEA-709 Standards under the general title

17、Control Network Protocol (CNP), which comprises the following parts: Part 1: Protocol Stack Specification Part 2: Power Line Channel Specification Part 3: Twisted-Pair Communication Part 4: Fiber-Optic Specification Part 5: Implementation Part 6: Application Elements At present this document exists

18、only in English. Tags Descriptors: system management, open systems interconnection, interoperability, device communications, network interconnection, buildings, heating, ventilation, air conditioning, data bus, data transmission, protocols, device profiles, building automation, controls, building ma

19、nagement Overview This standard specifies the Layered Implementation Guidelines (LIG) for the Control Network Protocol (CNP) Specification: ANSI/CEA-709.1-D. The CNP specification model is based on the ISO Open Systems Interconnection Reference Model. There are also important extensions to the 7-lay

20、er OSI Reference Model. Figure 1 shows the scope of this specification in reference to the CNP and companion specifications for handling various data-transport media at the lower ISO protocol layers. A dashed line is used to show that the scope of this standard is not as redundancy to the other spec

21、ifications covering their respective layers but as a complement to those specifications in implementing them in an interoperable fashion. In this standard, the guidelines for implementing a device based on CNP are specified to increase the ability for devices to interoperateregardless of installer o

22、r manufacturer of the devices. Anything outside this boundary is covered in other parts of the standard. Similar specifications exist for CNP data-transport media. Draft CEA-709.5 2 This standard has been prepared to provide mechanisms through which various vendors of building automation, control, a

23、nd of building-management systems, may exchange information in a standardised way. It defines communication and internal-documentation requirements. This standard is contributing to the general US policy for energy savings for building automation, monitoring, and control of energy consuming systems

24、in typical buildings. C E A - 709. 5 I m p le m e n t a t ion Gu ide li n e A N S I / C E A - 709. 1 P r o t o c o l S t a c k A N S I / C E A - 7 0 9 . 2 P o w e r L ine C h a n n e l A N S I / C E A - 709 . 3 Tw is t e d - P a ir C o mm u n ic a t ion A N S I / C E A - 7 0 9 . 4 Fibe r - Op t ic C

25、 h a n n e l A N S I / C E A - 852 .1 E n h a n c e d I P Tun n e li n g P r o t o c o l ANSI/CEA-709Control NetworkProtocol C E A - 709. 6 A p p li c a t ion E le m e n t s Figure 1 Scope of the ANSI/CEA-709 suite of standards 1 Scope This standard contains all the information necessary to facilita

26、te the exchange of data and control information in an interoperable fashion using ANSI/CEA-709.1-D and its associated data-transport media specifications. This standard establishes a minimal set of rules for compliance. It does not rule-out extended services to be provided, given that the rules are

27、adhered-to within the system. It is the intention of the standard to permit extended services to coexist and defines the bounds in which those services function, including the format for internal device-documentation of those services. Services outside purvey of this specificationso long as they are

28、 adherents of the systemare permitted but will not necessarily be interoperable with any other devices and shall not be essential for the functioning of the device. Certain aspects of this standard are defined in other documents. These documents are referenced where relevant. In the case where a ref

29、erenced document conflicts with this standard, this standard will prevail. 2 References 2.1 Normative References The following referenced standards are indispensable for the application of this standard. These standards contain provisions that, through reference in this text, constitute normative pr

30、ovisions of this standard. At the time of publication, the editions indicated were valid. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. Draft CEA-709.5 3 2.1.1 Normative Reference List A

31、NSI/CEA-709.1-D - CONTROL NETWORK PROTOCOL SPECIFICATION ANSI/CEA-709.2 - CONTROL NETWORK POWER LINE (PL) CHANNEL SPECIFICATION ANSI/CEA-709.3 - FREE-TOPOLOGY TWISTED-PAIR CHANNEL SPECIFICATION ANSI/CEA-709.4 - FIBER-OPTIC CHANNEL SPECIFICATION ANSI/CEA-852.1-A - ENHANCED PROTOCOL FOR TUNNELLING COM

32、PONENT NETWORK PROTOCOLS OVER INTERNET PROTOCOL CHANNELS CEA-709.6 CONTROL NETWORKING PROTOCOL SPECIFICATION: PART 6: APPLICATION ELEMENTS 2.1.2 Normative Reference Acquisition 1. Consumer Electronics Association (CEA); 1919 South Eads Street, Arlington, VA 22202; Tel: +1 703 907 7500; http:/ 3 Term

33、s and Definitions For the purpose of this standard, the terms and definitions given in ANSI/CEA-709.1-D and the following apply. 3.1 application set function block or function blocks to which a configuration property applies EXAMPLE A network variable, a series or compilation of network variables, a

34、 functional block, a series or compilation of functional blocks, or the entire device. 3.2 base type fundamental type that can be used as the basis of a network-variable type or configuration-property type. NOTE The available base types are defined in section 5.1.2.2. 3.3 changeable-type network var

35、iable network variable whose type can be changed during installation NOTE See 4.8.3.3. Draft CEA-709.5 4 3.4 configuration property (CP) data value used to configure the application program in a device NOTE Configuration properties are used to set parameters such as maximum, minimum, default, and ov

36、erride values. CPs are implemented using configuration network variables or as data items within configuration files. Configuration-property data are kept in a devices non-volatile memory. 3.5 configuration-property member part of a functional profile NOTE See 3.22. 3.6 configuration-property member

37、 number Part of a functional profile NOTE See 3.23. 3.7 configuration-property type index 16-bit number that uniquely identifies a configuration-property type within the scope defined by the scope number and program-ID template of the resource file that contains the configuration-property type defin

38、ition 3.8 device logical and physical entity of the network containing an application that is designed to communicate with other logical and physical entities 3.9 device channel ID number that optionally specifies the channel to which a device is attached 3.10 device class two-byte field identifying

39、 the primary function of a device and part of the SPID of the device 3.11 device interface network-visible interface to a device consisting of the unique node ID, program ID, channel ID, location field, device self-documentation string, device configuration properties, and functional blocks 3.12 dev

40、ice-location field string or number that optionally specifies the location of a device Draft CEA-709.5 5 3.13 device self-documentation string DSDS string that specifies the structure of the contents of the self-documentation strings, the functional blocks, and optionally describes the function of a

41、 device 3.14 device subclass two-byte field specifying the usage in the first byte and the channel type in the second byte and is part of the SPID of a device NOTE See the usage and channel-type definitions. 3.15 dynamic functional block functional block that is added to a device by a network tool a

42、fter the device is installed 3.16 dynamic network variable network variable that is added to a device by a network tool after the device is installed 3.17 format four-bit value defining the structure of the program ID as being a Standard Program Identifier (SPID) and device self-documentation string

43、 (DSDS) in the device string that provides formatting instructions for a network-variable or configuration-property type 3.18 functional block portion of a devices application that performs a task by receiving configuration and operational data inputs, processing the data, and sending operational da

44、ta outputs NOTE A functional block may receive inputs from the network, from hardware attached to the device, and/or from other functional blocks on a device. A functional block may send outputs to the network, to hardware attached to the device, and/or to other functional blocks on the device. A fu

45、nctional block is an implementation of a functional profile. A “standard” functional block is one based on a standard functional profile template (SFPT). 3.19 functional-block index sequentially assigned number identifying a functional-block implementation on a device 3.20 functional profile FP temp

46、late that describes common units of functional behaviour, also known as profiles, or FPs; which can be represented with a machine-readable functional-profile template (FPT) NOTE Each functional profile consists of a profile description and a specified set of network variables and configuration prope

47、rties designed to perform a single function on Draft CEA-709.5 6 a device. The network variables and configuration properties specified by the functional profile are called the functional-profile members. A functional profile specifies whether the implementation of each functional-profile member is

48、mandatory or optional. A profile is uniquely identified by a program-ID template, scope, and functional-profile number. 3.21 functional-profile key functional-profile number NOTE See 3.24. 3.22 functional-profile member network-variable or configuration-property member of a functional profile NOTE E

49、ach functional-profile member is identified as mandatory or optional by the functional profile. Each member also includes a text description of the member for the functional profile. 3.23 functional-profile member number two-byte number that uniquely identifies a network-variable or configuration-property member of a functional profile NOTE This member number is used to associate a network variable or configuration property on a device with the corresponding network-variable or configuration-property member of the functional profile. Member numbers