Codeofchina.com is in charge of this English translation. In case of any doubt about the English translation, the Chinese original shall be considered authoritative.
This standard is developed in accordance with the rules given in GB/T 1.1-2009 Directives for standardization - Part 1: Structure and drafting of standards.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The issuing body of this document shall not be held responsible for identifying any or all such patent rights.
This standard was proposed by China Electricity Council.
This standard is under the jurisdiction of National Technical Committee on Smart Grid User Interface of Standardization Administration of China (SAC/TC 549).
During the process of implementing this standard, the relevant comments and recommendations, whenever necessary, can be fed back to the Standardization Center of the China Electricity Council (No.1, 2nd Lane, Baiguang Road, Beijing, 100761, China).
Specification for information exchange of power demand response
1 Scope
This standard specifies the general principles and requirements of information exchange, information model, information exchange service and information exchange mechanism of power demand response system.
This standard is applicable to the design, development and upgrade of power demand response system.
2 Normative references
The following referenced documents are indispensable for the application of this standard. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
GB/T 32672-2016 General technical specification of power demand response system
GB/T 7408-2005 Data elements and interchange formats - Information interchange - Representation of dates and times
Decree No.14 of the National Development and Reform Commission of the People's Republic of China - Regulations on security protection of power monitoring systems
3 Terms and definitions
For the purposes of this document, the terms and definitions given in GB/T 32672-2016 and the following apply. For the convenience of application, some terms and definitions specified in GB/T 32672-2016 are listed below.
3.1
information model
describing the main objects involved in demand response businesses, which are mainly composed of information class and its association relation
3.2
information exchange service
information model encapsulated via specified data encapsulation mode and transmitted between systems, system and end in the demand response system
3.3
information exchange
information flows of different systems or ends organize information according to a unified information model and exchange information through information exchange services
3.4
information class
composed of a set of properties that describe the characteristics of objects and represent specific objects in demand response businesses
3.5
association relation
representing the mutual relation between different information classes, including association, dependence, generalization, aggregation, etc.
3.6
package
composed of a set of information classes of the same type and their association relation
3.7
data type
type used to describe an property in an information class
3.8
demand response business organizer
demand response service manager who organizes and implements the demand response business relying on the demand response service system; it may also refers to the demand response aggregator that implements the demand response business for the demand response service manager or the superior demand response aggregator based on the demand response aggregation system.
3.9
demand response business participant
power users and demand response aggregators who directly participate in the demand response business organized by the demand response service manager, or power users and demand response aggregators who participate in the demand response business organized by the demand response aggregators
3.10
demand response event
describing the information such as power price, load reduction or transfer volume according to certain rules during the execution of demand response business, and the information shall be released by the implementation organization to power users
3.11
up node; UN
code used to represent the system or end participating in information exchange in the demand response system. Compared with the down node, it usually refers to the demand response service system and demand response aggregation system
3.12
down node; DN
code used to represent the system or end participating in information exchange in the demand response system. Compared with the up node, it usually refers to the demand response aggregation system and demand response end
4 General principles and requirements of information exchange
Ensure the legitimacy of users participating in information exchange during the implementation of demand response business, so as to ensure the legitimacy of information exchange.
4.3 Normalization requirements
The essential feature of information exchange is normalization, which is an important premise for information exchange to carry out and realize information resource sharing and exchange in different countries and regions, different industries and different enterprises.
4.4 Security requirements
Including confidentiality, integrity, non-repudiation and authentication of information exchange, which is in accordance with Decree No.14 of the National Development and Reform Commission of the People's Republic of China.
4.5 Authenticity requirements
Various information data shall truthfully reflect the real situation during the implementation of the demand response business.
Foreword i 1 Scope 2 Normative references 3 Terms and definitions 4 General principles and requirements of information exchange 4.1 General principles 4.2 Legality requirements 4.3 Normalization requirements 4.4 Security requirements 4.5 Authenticity requirements 4.6 Reliability requirements 4.7 Validity requirements 4.8 Timeliness requirements 5 Information model 5.1 General 5.2 Domain package 5.2.1 Overview 5.2.2 Basic type of Boolean 5.2.3 Basic type of Integer 5.2.4 Basic type of Float 5.2.5 Basic type of String 5.2.6 Basic type of DateTime 5.2.7 Basic type of Duration 5.2.8 Enumeration type of UnitMultiplier 5.2.9 Enumeration type of UnitSymbol 5.3 Registration package 5.3.1 Overview 5.3.2 Enumeration type of TransportType 5.3.3 Service specifications 5.3.4 Enumeration type of ServiceType 5.3.5 KeyValue 5.4 Event package 5.4.1 Overview 5.4.2 Demand response event (Event) 5.4.3 Enumeration type of ResponseRequired 5.4.4 EventDescriptor 5.4.5 Enumeration type of EventStatus 5.4.6 EventActivePeriod 5.4.7 EventSignals 5.4.8 EventBaseline 5.4.9 EventSignal 5.4.10 Enumeration type of SignalName 5.4.11 Enumeration type of SignalType 5.5 Report package 5.5.1 Overview 5.5.2 MetaDataReport 5.5.3 ReportDescription 5.5.4 MetricDescription 5.5.5 Enumeration type of MetricName 5.5.6 Enumeration type of ReadingType 5.5.7 Target 5.5.8 EndDeviceAsset 5.5.9 Enumeration type of EndDeviceAssetType 5.5.10 MeterAsset 5.5.11 SamplingRate 5.5.12 ReportRequest 5.5.13 ReportSpecifier 5.5.14 Enumeration type of ReportType 5.5.15 PendingReports 5.5.16 Resource 5.5.17 PointData 5.5.18 CurveData 5.5.19 PointCurveData 5.5.20 RegularCurve 5.5.21 IrregularCurve 5.5.22 Data 5.5.23 Enumeration type of DataQuality class 5.6 Participation package 5.6.1 General 5.6.2 Enumeration type of OptType 5.6.3 Enumeration type of OptReason class 5.7 Poll package 5.7.1 Overview 5.7.2 EventResponse 5.7.3 QualifiedEventID 6 Information exchange service 6.1 General 6.2 Universal services 6.2.1 Overview 6.2.2 DrRequest 6.2.3 DrResponse 6.3 Registration services 6.3.1 Overview 6.3.2 QueryRegistrationRequest 6.3.3 CreateRegistrationRequest 6.3.4 CreateRegistrationResponse 6.3.5 CancelRegistrationRequest 6.3.6 CancelRegistrationResponse 6.4 Event services 6.4.1 Overview 6.4.2 QueryEventRequest 6.4.3 QueryEventResponse 6.5 Reporting services 6.5.1 Overview 6.5.2 RegisterReportRequest 6.5.3 RegisterReportResponse 6.5.4 CreateReportRequest 6.5.5 CreateReportResponse 6.5.6 CancelReportRequest 6.5.7 CancelReportResponse 6.5.8 ResourceReportRequest 6.5.9 MomentDataReportRequest 6.5.10 IntervaIDataReportRequest 6.5.11 DataReportResponse 6.6 Participation services 6.6.1 Overview 6.6.2 CreateOptRequest 6.6.3 CreateOptResponse 6.6.4 CancelOptRequest 6.6.5 CancelOptResponse 7 Information exchange mechanism Annex A (Informative) Typical scenario of demand response information interaction Annex B (Informative) JSON syntax Annex C (Informative) Example of HTTP encapsulated JSON message Annex D (Informative) Abbreviation Bibliography
电力需求响应信息交换规范 1 范围 本标准规定了电力需求响应系统信息交换的一般原则和要求、信息模型、信息交换服务及信息交换机制。 本标准适用于电力需求响应系统的设计、研发与升级完善。 2 规范性引用文件 下列文件对于本文件的应用是必不可少的。凡是注日期的引用文件，仅注日期的版本适用于本文件。凡是不注日期的引用文件，其最新版本(包括所有的修改单)适用于本文件。 GB/T 32672-2016 电力需求响应系统通用技术规范 GB/T 7408-2005 数据和交换格式 信息交换 日期和时间表示法(Data elements and interchange formats—Information interchange—Representation of dates and times) 中华人民共和国国家发展和改革委员会令第14号 电力监控系统安全防护规定 3 术语和定义 GB/T 32672-2016 界定的以及下列术语和定义适用于本文件。为了便于使用，以下重复列出了GB/T 32672-2016中的一些术语和定义。 3.1 信息模型 information model 描述需求响应业务涉及的主要对象，主要由信息类及其关联关系构成。 3.2 信息交换服务 information exchange service 需求响应系统中，系统与系统间、系统与终端间通过规定的数据封装方式封装信息模型，并进行传输。 3.3 信息交换 information exchange 不同系统或终端的信息流按照统一的信息模型组织信息，并通过信息交换服务来交换信息。 3.4 信息类 information class 由一组描述对象特性的属性构成，对需求响应业务中特定对象进行表示。 3.5 关联关系 association relation 表示不同信息类之间的相互关系，包括关联、依赖、泛化、聚合等。 3.6 包 package 由一组相同类型的信息类及信息类的关联关系构成。 3.7 数据类型 data type 用以描述信息类中属性的类型。 3.8 需求响应业务组织方 demand response business organizer 依托需求响应服务系统组织实施需求响应业务的需求响应服务管理者；也可以指依托需求响应聚合系统，为需求响应服务管理者或上级需求响应聚合商代理实施需求响应业务的需求响应聚合商。 3.9 需求响应业务参与方 demand response business participant 直接参与需求响应服务管理者所组织需求响应业务的电力用户、需求响应聚合商，或参与需求响应聚合商所组织需求响应业务的电力用户、需求响应聚合商。 3.10 需求响应事件 demand response event 在需求响应业务执行过程中，按一定规则描述电力价格、负荷削减或转移量等信息，由实施机构向电力用户发布。 3.11 上位节点 Up Node；UN 需求响应系统中，用于表示参与信息交换的系统或终端的代号，相较于下位节点，通常代指需求响应服务系统、需求响应聚合系统。 3.12 下位节点 Down Node；DN 需求响应系统中，用于表示参与信息交换的系统或终端的代号，相较于上位节点，通常代指需求响应聚合系统、需求响应终端。 4 信息交换的一般原则和要求 4.1 一般原则 合法性、规范性、安全性、真实性、可靠性、有效性、时效性。 4.2 合法性要求 确保需求响应业务实施过程中参与信息交换用户的合法性，使信息交换的合法性得到保障。 4.3 规范性要求 信息交换的本质特征是规范化，是信息交换能在不同国家和地区、不同行业、不同企业间开展和实现信息资源共享和交换的重要前提。 4.4 安全性要求 包括信息交换的保密性、完整性、不可否认性、可认证性等，符合中华人民共和国国家发展和改革委员会第14号令。 4.5 真实性要求 各种信息数据要如实反映需求响应业务实施过程的真实情况。 4.6 可靠性要求 数据传输过程中，如果遇到网络故障或系统出现异常的情况，要保证数据安全、可靠地继续传输，确保信息交换的准确、完整和一致。 4.7 有效性要求 选择最有价值的信息和最适合的传递工具及路线，用最经济的方式传递尽可能多的信息。 4.8 时效性要求 及时反映需求响应业务实施过程的真实情况，即信息的获取、收集和交换适应信息动态变化要求，更新后的信息能及时得到获取和反馈。 5 信息模型 5.1 总则 信息模型为需求响应信息交换过程中进行实际交换的主体，含有六个包，分别为域包、注册包、事件包、报告包、参与包、询问包，六个包之间的关联关系如图1所示。
