DLMS用户协会蓝皮书：COSEM接口类与OBIS对象识别系统

需积分: 10 43 浏览量更新于2024-07-16 收藏 6.73MB PDF 举报

"《Blue_Book_Edition_13.pdf》是关于IEC62056标准的蓝皮书，2019年的第13版，包含了COSEM接口类和OBIS对象识别系统的内容。书中详细阐述了COSEM（Customer Ownership Semantic Model for Electricity Meters）对象模型，涉及IEC 62056-61和IEC 62056-62两个部分。这份技术报告是针对能源计量的伴侣规范，由DLMS用户协会发布。" 这篇文档的核心知识点包括： 1. **COSEM接口类**：COSEM（Customer Ownership Semantic Model for Electricity Meters）是用于电能表的数据交换标准，它定义了一套接口类，允许不同设备间的通信和数据交换。这些接口类是COSEM模型的基础，涵盖了各种功能，如数据读取、设置、控制和事件记录。 2. **OBIS对象识别系统**：OBIS（Object Identification System）是COSEM的一部分，用于唯一地标识电能表和其他智能设备中的数据对象。OBIS编码系统使得在不同制造商的设备间能够标准化数据交流，提高了互操作性。 3. **术语和定义**：文档中详细列出了与图像传输过程、S-FSK电力线通信（PLC）设置ICs、PRIMEN宽带OFDM PLC设置ICs、ZigBee®通信、支付计量ICs以及仲裁器IC相关的术语和定义，这些都是智能电网通信的关键元素。 - **S-FSK PLC**：这是一种电力线通信技术，用于在电力线上传输数据，常用于智能电网。 - **PRIMEN**：是一种基于OFDM（正交频分复用）的电力线通信协议，适用于宽频带应用。 - **ZigBee**：是一种低功耗、短距离无线通信技术，广泛应用于智能家居和物联网设备。 - **支付计量ICs**：与支付相关的计量集成电路，可能涉及到预付费电表等。 - **仲裁器IC**：在多设备通信中，用于解决冲突和管理网络访问的组件。 4. **基本原理**：文档介绍了COSEM接口类的基本原则，包括通用原则和引用方法。这些原则指导了如何设计和实现符合COSEM标准的通信接口。 5. **引用方法**：这部分描述了如何在COSEM框架内引用和定位不同的对象和服务，包括预留的基名，这些是确保系统稳定性和未来扩展的关键。 6. **标准引用**：文档提到了IEC 62056-61和IEC 62056-62，这两个标准分别可能详细规定了COSEM接口的特定方面和OBIS的实施规则。 7. **DLMS用户协会**：DLMS（Distributed Local Measurement System）用户协会是一个国际组织，负责维护和推广DLMS/COSEM标准，以促进全球智能计量系统的互操作性。《Blue_Book_Edition_13.pdf》是智能电网和能源计量领域的重要参考资料，详细介绍了COSEM标准的实现和OBIS编码体系，对于理解智能电表的通信机制和数据交换具有极高的价值。

COSEM Interface Classes and OBIS Object Identification System

DLMS User Association 2019-05-08 DLMS UA 1000-1 Ed 13 15/573

Foreword

This document is confidential. It may not be copied, nor handed over to persons outside the

standardization environment.

The copyright is enforced by national and international law. The "Berne Convention for the

Protection of Literary and Artistic Works", which is signed by 176 countries world-wide, and

other treaties apply.

Liability

DLMS User Association Publications have the form of recommendations for international use.

While all reasonable efforts are made to ensure that the technical content of DLMS User

Association Publications is accurate, the DLMS User Association cannot be held responsible

for the way in which they are used or for any misinterpretation by any end user.

No liability shall attach to DLMS User Association or its directors, employees, servants or

agents including individual experts and members of its technical committees for any personal

injury, property damage or other damage of any nature whatsoever, whether direct or indirect,

or for costs (including legal fees) and expenses arising out of the publication, use of, or reliance

upon, this DLMS User Association Publication or any other DLMS User Association

Publications.

Intellectual Property Rights

The DLMS User Association (DLMS UA) draws attention to the fact that it is claimed that

compliance with this document may involve the use of a patent concerning the Image transfer

procedure.

The DLMS UA takes no position concerning the evidence, validity and scope of this patent right.

The holder of this patent right has assured the DLMS UA that he/she is willing to negotiate

licenses either free of charge or under reasonable and non-discriminatory terms and conditions

with applicants throughout the world. In this respect, the statement of the holder of this patent

right is registered with the DLMS UA. Information may be obtained from Itron, Inc., Liberty Lake,

Washington, USA.

Attention is drawn to the possibility that some of the elements of this document may be the

subject of patent rights other than those identified above. The DLMS UA shall not be held

responsible for identifying any or all such patent rights.

The DLMS UA maintains on-line databases of patents relevant to their standards. Users are

encouraged to consult the databases for the most up to date information concerning patents.

Acknowledgement

The actual document has been established by the WG Maintenance of the DLMS UA.

Clauses 4.4.7 and 4.4.9 are based on parts of NIST documents. Reprinted courtesy of the

National Institute of Standards and Technology, Technology Administration, U.S. Department

of Commerce. Not copyrightable in the United States.

COSEM Interface Classes and OBIS Object Identification System

16/573 2019-05-08 DLMS UA 1000-1 Ed. 13 DLMS User Association

Status of standardization

The contents of this edition is the basis of a planned revision to:

• IEC 62056-6-1 Ed. 3:2017, Electricity Metering Data Exchange – The DLMS/COSEM suite

– Part 6-1: Object identification system (OBIS); and

• IEC 62056-6-2 Ed. 3:2017, Electricity Metering Data Exchange – The DLMS/COSEM suite

– Part 6-2: COSEM interface classes.

Revision history

Version Date Author Comment

Release 1 01 April 1998 DLMS UA Initial version

First Edition 12 Nov. 1998 DLMS UA Considering comments received after R1

Second Edition 03 May 1999 DLMS UA Major rework, classes and associations added

Third Edition 29 Feb. 2000 DLMS UA Major rework, adapted to CDVs of IEC TC13, OBIS added

Fourth Edition 25 March 2001 DLMS UA Considering comments to CDVs by IEC National Committees

Fifth Edition 05 March 2002 DLMS UA Content adapted to IEC International Standards

Sixth Edition 16th August 2004 DLMS UA Content adapted to draft IEC 62056-61 Edition 2

draft IEC 62056-62

(CD versions) and EN 13757-1:2002

Seventh Edition 12

September 2005

DLMS UA Content adapted to 13/1341/CDV, draft IEC 62056-61 Edition 2,

13/1342/CDV, draft IEC 62056-62 Edition 2 and comments received

on these drafts, as well as on EN 13757-1:2002

Eighth Edition 14

September 2007

DLMS UA Document restructured, editorial errors in Ed. 7.0 corrected.

Ninth Edition 9

February 2009 DLMS UA New elements for smart metering and advanced gas volume and

energy conversion added.

Tenth Edition 26

August 2010 DLMS UA Brought in line with Green Book.

New interface classes and new versions of interface classes added.

New OBIS codes added.

Eleventh Edition 26th August 2013 DLMS UA

New interface classes and new versions of existing interface classes

added. New OBIS codes added.

Twelfth Edition 10

September 2014

DLMS UA New interface classes and new versions of existing interface classes

added in support of Security management, Payment Metering,

Arbitrator, Compact data, Data protection, Push setup, G3-PLC, M-

Bus,New OBIS codes added.

Twelfth Edition

Corrigendum 1

December 2015 DLMS UA Technical and editorial corrections

Edition 12.1 21

December 2015 DLMS UA Consolidated edition including the Corrigendum 1.

Edition 12.2 21

December 2016 DLMS UA

New or updated interface classes for Function Control, Array

Manager, NTP setup, Compact data,GSM-related and HS-PLC

networks added. New OBIS codes added

Edition 13 8

May 2019 DLMS UA See below

COSEM Interface Classes and OBIS Object Identification System

18/573 2019-05-08 DLMS UA 1000-1 Ed. 13 DLMS User Association

Introduction

Object modelling and data identification

Driven by the business needs of the energy market participants – generally in a liberalized,

competitive environment – and by the desire to manage natural resources efficiently and to

involve the consumers, the utility meter became part of an integrated metering, control and

billing system. The meter is not any more a simple data recording device but it relies critically

on communication capabilities. Ease of system integration, interoperability and data security

are important requirements.

COSEM, the Companion Specification for Energy Metering, addresses these challenges by

looking at the utility meter as part of a complex measurement and control system. The meter

has to be able to convey measurement results from the metering points to the business

processes which use them. It also has to be able to provide information to the consumer and

manage consumption and eventually local generation.

COSEM achieves this by using object modelling techniques to model all functions of the meter,

without making any assumptions about which functions need to be supported, how those

functions are implemented and how the data are transported. The formal specification of

COSEM interface classes forms a major part of COSEM.

To process and manage the information it is necessary to uniquely identify all data items in a

manufacturer-independent way. The definition of OBIS, the Object Identification System is

another essential part of COSEM. It is based on DIN 43863-3:1997, Electricity meters – Part

3: Tariff metering device as additional equipment for electricity meters – EDIS – Energy Data

Identification System. The set of OBIS codes has been considerably extended over the years

to meet new needs.

COSEM models the utility meter as a server application – see 4.1.7 – used by client applications

that retrieve data from, provide control information to, and instigate known actions within the

meter via controlled access to the COSEM objects. The clients act as agents for third parties

i.e. the business processes of energy market participants.

The standardized COSEM interface classes form an extensible library. Manufacturers use

elements of this library to design their products that meet a wide variety of requirements.

The server offers means to retrieve the functions supported, i.e. the COSEM objects

instantiated. The objects can be organized to logical devices and application associations and

to provide specific access rights to various clients.

The concept of the standardized interface class library provides different users and

manufacturers with a maximum of diversity while ensuring interoperability.

COSEM Interface Classes and OBIS Object Identification System

DLMS User Association 2019-05-08 DLMS UA 1000-1 Ed 13 19/573

1 Scope

The DLMS/COSEM specification specifies

a data model and communication protocols

for data exchange with metering

equipment. It follows a three-step approach

as illustrated in

Figure 1.

Step 1, Modelling

: This covers the data

model of metering equipment a

s well as

rules for data identification. The data model

provides

a view of the functionality of the

meter, as it is available at its interface(s). It

uses generic building blocks to model this

functionality. The model does not cover

internal, implementation-specific issues.

Step 2, Messaging

: This covers the

communication services and protocols for

mapping the elements of the data model to

application protocol data units (APDU).

Step 3, Transporting

: This covers the

rvices and protocols for the

transportation of the messages through the

communication channel.

Figure 1 – The three steps approach of DLMS/COSEM: Modelling – Messaging –

Transporting

Step 1 is specified in this document. It specifies the COSEM interface classes (ICs), the OBIS

object identification system, and the use of interface objects for modelling the various functions

of the metering equipment.

Step 2 and 3 are specified in the Green Book,DLMS UA 1000-2 Ed. 9. It specifies

communication profiles for various communication media and the protocol layers of these

communication profiles. The top layer in any profile is the DLMS/COSEM application layer. It

provides services to establish a logical connection between the client and the server(s). It also

provides the xDLMS messaging services to access attributes and methods of the COSEM

interface objects. The lower, communication profile specific protocol layers transport the

information.

Rules for conformance testing are specified in the “Yellow Book”, DLMS UA 1001-1

"DLMS/COSEM Conformance Test Process".

Terms are explained in the “White book” DLMS UA 1002, "COSEM Glossary of Terms".

3. Transporting

C0 01 00 03 01 01 01 08 00 FF 02

2. Messaging

Protocol Services to access

attributes and methods

ISO, IEC,...

Communication Protocol

Messages :

Service_Id( Class_Id, Instance_Id, Attribute_Id/Method_Id )

Encoding: ( APDU )

1. Modelling

COSEM Interface Objects

Attribute(s) Data Type Min Max Def

1. logical_name

(static)

octet-string

2. value

(dyn.)

instance specific

3. scaler-unit

(static)

scal_unit_type

Method(s) m/o

1. reset

DLMS User Association

剩余573页未读，继续阅读

zxk_hz

粉丝: 1
资源: 3

DLMS用户协会蓝皮书：COSEM接口类与OBIS对象识别系统

DLMS Blue book and Green book.7z

Blue_Book_11th_edition

Blue_Book_12th_edition.pdf

kernel = cv2.getStructuringElement(cv2.MORPH_ELLIPSE, (5, 5)) red_mask = cv2.morphologyEx(red_mask, cv2.MORPH_OPEN, kernel) blue_mask = cv2.morphologyEx(blue_mask, cv2.MORPH_OPEN, kernel)

# Model print(colored('Retrieve model', 'blue')) model = get_model(p) print('Model is {}'.format(model.__class__.__name__)) print('Model parameters: {:.2f}M'.format(sum(p.numel() for p in model.parameters()) / 1e6)) print(model) model = model.cuda()，这句话是什么意思

blue_book_edition_12-2中文版

最新资源

# Model print(colored('Retrieve model', 'blue')) model = get_model(p) print('Model is {}'.format(model.class.name)) print('Model parameters: {:.2f}M'.format(sum(p.numel() for p in model.parameters()) / 1e6)) print(model) model = model.cuda()，这句话是什么意思