ANSI CTA-2045-2013 Modular Communications Interface for Energy Management (Formerly ANSI CEA-2045).pdf

《ANSI CTA-2045-2013 Modular Communications Interface for Energy Management (Formerly ANSI CEA-2045).pdf》由会员分享，可在线阅读，更多相关《ANSI CTA-2045-2013 Modular Communications Interface for Energy Management (Formerly ANSI CEA-2045).pdf（98页珍藏版）》请在麦多课文档分享上搜索。

1、 ANSI/CTA Standard Modular Communications Interface for Energy Management ANSI/CTA-2045 (Formerly ANSI/CEA-2045) February 2013 NOTICE Consumer Technology Association (CTA) Standards, Bulletins and other technical publications are designed to serve the public interest through eliminating misunderstan

2、dings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards, Bulletins and other technical publications shall

3、 not in any respect preclude any member or nonmember of the Consumer Technology Association from manufacturing or selling products not conforming to such Standards, Bulletins or other technical publications, nor shall the existence of such Standards, Bulletins and other technical publications preclu

4、de their voluntary use by those other than Consumer Technology Association members, whether the standard is to be used either domestically or internationally. Standards, Bulletins and other technical publications are adopted by the Consumer Technology Association in accordance with the American Nati

5、onal Standards Institute (ANSI) patent policy. By such action, the Consumer Technology Association does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard, Bulletin or other technical publication. Note: The users attention is cal

6、led to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or of any patent rights in connection therewith. The patent holder has, however, filed

7、a statement of willingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. Details may be obtained from the publisher. This document does not purport to address all safety problems associated with its use

8、 or all applicable regulatory requirements. It is the responsibility of the user of this document to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. This document is copyrighted by the Consumer Technology Association and

9、may not be reproduced, in whole or part, without written permission. Federal copyright law prohibits unauthorized reproduction of this document by any means. Organizations may obtain permission to reproduce a limited number of copies by entering into a license agreement. Requests to reproduce text,

10、data, charts, figures or other material should be made to the Consumer Technology Association. (Formulated under the cognizance of the CTA R7.8 Modular Communication Interface for Energy Management Subcommittee.) Published by CONSUMER TECHNOLOGY ASSOCIATION 2015 Technology encourage manufacturers to

11、 build an MCI interface into their products that can accept a simple communications module. Consumers and program managers are then free to select whatever communication solution works best for their particular environment. The concept is relatively straightforward. Utilizing the RS-485 and Serial P

12、eripheral Interface (SPI)1 supported by most silicon chips today, the MCI protocol is capable of simply passing through standard protocols including Internet Protocol (IP), OpenADR, and SEP from the communications module to the end-device. Network security is supported through the selected transport

13、 protocol, such as Wi-Fi, ZigBee, HomePlug, Z-Wave, LonWorks, etc., in addition to network or application layer security. Communications messaging supported by this MCI standard supports direct load control, TOU, CPP, RTP, peak time rebates, all kinds of block rates, and a range of ancillary service

14、s. The functionality of the removable modules can be tailored by utilities or other load managing entities to provide support for the unique needs in a given region or service territory, without impacting the end-devices. The CEA-2045 Modular Communications Interface for Energy Management standard w

15、ill enable a new generation of “smart grid ready” products that limit risks and constraints of proprietary communications technologies and evolving standards. This approach simplifies Home Area Network (HAN) device and network interoperability, fosters program and product innovation, and opens DR pr

16、ograms to a broader range of consumer products while respecting customer choice and a competitive market landscape. 1 See http:/ and http:/en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus 2 2 Scope This standard specifies a modular communications interface (MCI) to facilitate communications wit

17、h residential devices for applications such as energy management. The MCI provides a standard interface for energy management signals and messages to reach devices. Such devices may include an energy management hub, an energy management controller, an energy management agent, a residential gateway,

18、an energy services interface, a sensor, a thermostat, an appliance, or other consumer products. The specific residential devices to use an MCI are not specified. For energy management the choice depends on the system and the network topology. If a hub topology is chosen, the MCI may be located on th

19、e hub. The connection between the hub and end devices such as appliances is not specified. The MCI specifies a physical connection from a communication module to residential Smart Grid Devices and a communications protocol with OSI (Open System Interconnection) layer specifications including applica

20、tion layer messaging. An optional translation function is specified for connection to another communications medium. Examples include power line carrier or radio (RF), depending on the home area network installed or the connection to an energy management system access-network supplied by a service p

21、rovider. This second medium is outside the scope of this standard. The MCI also specifies a pass-through mechanism through to allow for an alternate architecture in which the Smart Grid Device terminates the passed-through protocol (e.g., SEP, OpenADR, etc.). CEA-2045 details the mechanical, electri

22、cal, and logical characteristics of a socket interface that allows communication devices (hereafter referred-to as UCMs universal communication modules) to be separated from end devices (hereafter referred-to as SGDs Smart Grid Devices). Although the potential applications of this technology are wid

23、e-ranging, it is intended at a minimum to provide a means by which residential products may be able to work with any load management system through user installable plug-in communication modules. Figure 1-1 illustrates the general concept. Figure 2-1 Illustrations of the Modular Communications Conce

24、pt on a controlled device (left) or Energy Management Console (right) 3 CEA-2045 identifies the physical and data-link characteristics of the interface, along with certain higher-layer and application layer elements as needed to assure interoperability over a broad range of device capabilities. In a

25、ddition, it defines a mechanism through which network, transport and application layer messages (pass-through; defined in other standards) may be passed across the interface. The scope of this standard is limited to the socket interface between the UCM and the SGD. It does not address the technology

26、 or protocol associated with the communications system of which the UCM is part. The scope of this specification does not include safety related construction, performance, marking or instruction requirements. UCM products should additionally comply with applicable product safety standard(s). Example

27、s of such standards are noted in Informative Annex E. 2.1 References 2.1.1 Normative References The following specifications and documents contain provisions that, through reference in this text, constitute normative provisions of this standard. At the time of publication, the editions indicated wer

28、e valid. All specifications and documents are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the specifications and documents listed here. 2.1.2 Normative References List RS-485 also TIA/EIA

29、485 - Electrical Characteristics of Generators and Receivers for Use in Balanced Digital Multipoint Systems 2.1.3 Normative References Acquisition RS-485 also TIA/EIA 485 - http:/www.tiaonline.org/standards/buy-tia-standards 2.1.4 Informative References The following documents contain provisions tha

30、t, through reference in this text, constitute informative provisions of this document. At the time of publication, the editions indicated were valid. All documents are subject to revision, and parties to agreements based on this document are encouraged to investigate the possibility of applying the

31、most recent editions of the documents listed here. 2.1.5 Informative References List 1. ClimateTalk Specification, various revisions 4 2. OpenADR 2.0a,b,c, various revisions 3. Smart Energy Protocol 2.0, various revisions 4. SAE J1772 - http:/standards.sae.org/j1772_201001/ 5. USNAP Specification 1.

32、0 & 2.0, various revisions 6. ZigBee Alliance Smart Energy Protocol 1.x, various revisions 7. Z-Wave Alliance Specification, various revisions 8. Currency Codes - ISO 4217 Maintenance agency, SNV - SIX Interbank Clearing (http:/www.currency-iso.org/iso_index/iso_tables/iso_tables_a1.htm) 9. ISO/IEC

33、24739 - AT Attachment with Packet Interface 2.1.6 Informative References Acquisition 1. ClimateTalk Specification ClimateTalk Alliance, www.climatetalk.org 2. OpenADR 2.0a,b,c, - OpenADR Alliance, www.openadr.org 3. Smart Energy Protocol 2.0 ZigBee Alliance, www.zigbee.org 4. SAE J1772 - http:/stand

34、ards.sae.org/j1772_201001/ 5. USNAP Specification 1.0 & 2.0 USNAP Alliance, www.usnap.org 6. ZigBee Alliance Smart Energy Protocol 1.x, ZigBee Alliance, www.zigbee.org 7. Z-Wave Alliance http:/www.z-wavealliance.org/ 8. Currency Codes - ISO 4217 Maintenance agency, SNV - SIX Interbank Clearing (http

35、:/www.currency-iso.org/iso_index/iso_tables/iso_tables_a1.htm 9. ISO/IEC 24739 - AT Attachment with Packet Interface - http:/www.iso.org/iso/home/store/catalogue_ics.htm 2.2 Compliance As used in this document “shall” and “must” denote mandatory provisions of the standard. “Should” denotes a provisi

36、on that is recommended but not mandatory. “May” denotes a feature whose presence does not preclude compliance, and implementation of which is optional. “Optional” denotes items that may or may not be present in a compliant device. 5 2.3 Acronyms & Abbreviations SGD Smart Grid Device the end device t

37、hat is being informed of grid conditions UCM Universal Communications Module the communications device that provides communication connectivity to an SGD SPI Serial Peripheral Interface data transfer standard originally defined by Motorola (Freescale) 0x00 0xFF Two digit (8 bit) hexadecimal numbers

38、ranging from 0 to 255 decimal b0, b1 b15 Bit values within a hexadecimal number. b0 is lsb. MS Abbreviation for Most Significant LS Abbreviation for Least Significant AMI Advanced Metering Infrastructure SEP Smart Energy Protocol OpenADR 2.0 Automated Demand Response standard from the OpenADR Allian

39、ce IP Internet Protocol 3 Physical/Electrical Interface Two physical form factors are presently defined. End device manufacturers may choose either, and communications module providers who wish to cover all products may offer two module versions. For both form factors, the communications protocol ac

40、ross the socket interface is the same, as described herein. Also in both cases, the power for the UCM is provided by the SGD. One form factor provides a low voltage DC supply and an SPI serial data interface. This form factor is described in detail in Appendix A of this document. This option might b

41、e attractive in cases where the end device has no AC power source or when smaller socket size is required. The second form factor provides AC service voltage (120/240V) and an RS-485 based serial interface. This form factor is described in detail in Appendix B of this document. This option might be

42、attractive in cases where the end device does not provide a DC power supply, where compatibility with PLC communications modules is desired, or where communications module access to line frequency is needed. 3.1 Removal and Exchange of a UCM It has to be assumed that UCMs will be removed or exchange

43、d without turning off the SGD. Therefore the UCM shall be hot-swappable. 6 3.2 Block Diagram Figure 3-1 Modular Interface - Block Diagram 4 Serial Protocol CEA-2045 defines an extensible serial protocol data unit that is manageable by the simplest of devices and also capable of being extended to acc

44、ommodate the more complex. The general message format is as follows: Message Type Reserved Must be 0x0 Payload Length Payload Checksum 2 Bytes 3 Bits 13 Bits Variable 2 Bytes Table 4-1 Protocol Data Unit Format Conceptually the “payload” portion of the message can transport a range of protocols, wit

45、h the “Message Type” field indicating which protocol and the checksum included so as to assure link layer data integrity. There are 3 bits at the top of the 3 byte that are reserved for future work. These must be held at 0 to keep compatibility with future revisions. This scheme provides a high leve

46、l of flexibility and extensibility. A simple means is provided for SGDs and UCMs to discover which protocols one another support. 7 4.1.1 Message Type Field The “Message Type” bytes indicate the type of message, essentially indicating which communications protocol is represented in the payload. The

47、following “Message Type” values are specified: Message Type MS Byte Message Type LS Byte Description 0x00 to 0x05 0x00 to 0xFF Reserved for vendor proprietary use 0x06 0x00 to 0xFF Reserved to avoid confusion with link layer ACK 0x07 0x00 to 0xFF For Future Assignment 0x08 0x01 Basic DR Application

48、(at least partially supported by all devices) 0x08 0x02 Intermediate DR Application 0x08 0x03 Data-Link Messages 0x08 0x04 Commissioning and Network Support Messages 0x08 0x05 to 0xFF For Future Assignment 0x09 0x01 USNAP 1.0, Pass-Through 0x09 0x02 ClimateTalk, Pass-Through 0x09 0x03 Smart Energy P

49、rofile 1.0, Pass-Through 0x09 0x04 Smart Energy Profile 2.0 over IP, Pass-Through 0x09 0x05 OpenADR1.0 over IP, Pass-Through 0x09 0x06 OpenADR2.0 over IP, Pass-Through 0x09 0x07 Generic IP Pass-Through (IP packets self-identify version so both IPV4 and IPV6 are covered) 0x09 0x08 to 0xFF For Future Assignment 0x0A to 0x14 0x00 to 0xFF For Future Assignment 0x15 0x00 to 0xFF Reserved to avoid confusion with link layer NAK 0x16 to 0xEF 0x00 to 0xFF For Future Assignment 0xF0 to 0xFF 0x00 to 0xFF Reserved fo