DLMS/COSEM通信框架详解：第七版技术报告

DLMS/COSEM

Greenbook

需积分: 7 129 浏览量更新于2024-07-21 收藏 2.9MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Greenbook 7是DLMS用户协会发布的关于DLMS/COSEM架构和协议的第七版技术报告。这份文档详细介绍了DLMS（Digital Loop Meter System）/COSEM（Companion Specification for Energy Metering）通信框架，旨在提供能源计量的通信标准。" 在DLMS/COSEM体系中，以下几个核心知识点尤为关键： 1. **DLMS/COSEM通信框架**：这是一个用于智能电网和能源管理系统的通信标准，它定义了设备间的通信方式和数据交换规范。框架包括客户端/服务器型操作、连接（关联）导向的操作模式，确保不同设备间能够有效地进行数据交互。 2. **客户端/服务器型操作**：DLMS/COSEM系统中，设备可以作为客户端发起请求，而另一设备作为服务器响应请求。这种模式允许设备之间的双向通信，如智能电表向数据收集系统发送读数或接收控制指令。 3. **通信配置文件**：通信配置文件描述了特定应用场景下的通信行为，比如不同类型的设备如何建立连接、保持会话以及断开连接等。 4. **连接导向操作**：此部分强调了连接的建立、维护和关闭，是保证数据安全传输的重要环节。连接导向操作有助于防止数据丢失和错误传输，尤其在需要实时性或数据完整性的情景下。 5. **互操作性和互联性**：COSEM设计的目标之一是实现不同制造商设备之间的互操作性。通过协议识别服务，设备可以识别并适应与之通信的其他设备的协议，从而实现互联。 6. **确保互连性**：协议识别服务是实现这一目标的关键机制，它允许设备检测并确认它们都支持相同的通信协议，以确保数据交换的正确性。 7. **应用模型**：文档描述了几种不同的应用模型，这些模型代表了DLMS/COSEM可能在实际场景中的使用方式，如智能电表、数据收集系统、控制中心等。 8. **DLMS/COSEM服务器模型**：服务器模型通常指的是提供数据和服务的设备，如智能电表，它们能够接收和响应客户端的请求。 9. **DLMS/COSEM客户端模型**：客户端模型通常是数据收集系统或者远程监控系统，它们请求服务器提供数据或执行特定操作。 10. **DLMS/COSEM数据采集系统模型**：这类模型描述了如何组织和管理多个智能电表的数据收集，包括数据聚合、存储和分析功能。 "Greenbook 7"为理解和实施基于DLMS/COSEM的智能能源管理系统提供了详尽的指南，涵盖了从基础通信协议到具体应用模型的全面信息。这份文档对于开发、集成和维护能源管理系统的工程师来说具有极高的参考价值。

资源详情

资源推荐

DLMS User Association, COSEM Architecture and Protocols, Seventh Edition

DLMS User Association 2009-12-22

DLMS UA 1000-2 Ed. 7.0

16/310

IV Initialization Vector

LAN Local Area Network

LDN Logical Device Name

LLC Logical Link Control (Sublayer)

LLS Low Level Security

L-SAP LLC sublayer Service Access Point

LPDU LLC Protocol Data Unit

LSB Least Significant Bit

LSDU LLC Service Data Unit

m mandatory, used in conjunction with attribute and method definitions

MAC Medium Access Control (sublayer)

MAC Message Authentication Code (cryptography)

master Central station – station which takes the initiative and controls the data flow

MIB Management Information Base

MSAP MAC sublayer Service Access Point (in the HDLC based profile, it is equal to the HDLC address)

MSB Most Significant Bit

MSC Message Sequence Chart

MSDU MAC Service Data Unit

NDM Normal Disconnected Mode

NIST National Institute of Standards and Technology

NRM Normal Response Mode

N(R) Receive sequence Number

N(S) Send sequence Number

o optional, used in conjunction with attribute and method definitions

OBIS Object Identification System

OSI Open System Interconnection

PAR Positive Acknowledgement with Retransmission

PDU Protocol data unit

P/F Poll/Final

PhL Physical Layer

PHPDU PH PDU

PHSDU PH SDU

PLC Power line carrier

PSDU Physical layer Service Data Unit

PSTN Public Switched Telephone Network

PPP Point-to-Point Protocol

RARP Reverse Address Resolution Protocol

.req .request service primitive

.res .response service primitive

RLRE A-Release Response – an APDU of the ACSE

RLRQ A-Release Request – an APDU of the ACSE

RNR Receive Not Ready (a HDLC frame type)

RR Receive Ready (a HDLC frame type)

SAP Service Access Point

DLMS User Association, COSEM Architecture and Protocols, Seventh Edition

DLMS User Association 2009-12-22

DLMS UA 1000-2 Ed. 7.0

18/310

4. The DLMS/COSEM communications framework

4.1 Client/server type operation, communication profiles

Data exchange between data collection systems and metering equipment using the COSEM

interface object model is based on the client/server paradigm. Metering equipment

To allow servers notifying clients about events, unsolicited services are also available.

play the role

of the server.

Concepts, names and names terminology used below relate to the Open System Interconnection

Reference Model described in ISO/IEC 7498-1. Their use is outlined in this clause and further

developed in other clauses.

The data collection application and the metering application are modelled as one or more

application processes, APs; see 4.5. Therefore, in this environment communication takes place

always between a client and a server AP: the client AP requests services and the server AP

provides them.

A client AP may be able to exchange data with a single or with multiple server APs at the same

time. A server AP may be able to exchange data with one or more client APs at the same time.

NOTE Data exchange between server APs – the logical devices within a physical device – may be possible. Similarly,

data exchange between client APs hosted by a single or multiple physical devices may be possible. Such exchanges are

out of the scope of this specification.

Data exchange takes place via exchanging messages (SERVICE.requests / .responses) between

the peer APs. In general, the client and the server APs are located in separate devices; exchanging

messages therefore is done via a protocol stack, or communication profile, as shown in

Figure 2.

Physical channel

Client AP Server AP

SERVICE.request

SERVICE.response

Application layer

Intermediate layers

Physical layer

.request

.response

Communication profile

Figure 2 – Client/server relationship and protocols

Communication profiles comprise a number of protocol layers. Each layer has a distinct task and

provides services to its upper layer and uses services of its supporting layer(s). The client and

server COSEM APs use the services of the highest protocol layer, that of the AL. This is the only

protocol layer containing COSEM specific element(s): the xDLMS_ASE, providing COSEM interface

object related services. It may in principle be supported by any layer capable of providing the

The term "metering equipment" is an abstraction; consequently the equipment playing the role of a server may be any type of

equipment for which this abstraction is suitable.

DLMS User Association, COSEM Architecture and Protocols, Seventh Edition

DLMS User Association 2009-12-22

DLMS UA 1000-2 Ed. 7.0

20/310

data exchange via a local – optical or electrical – port according to IEC 62056-21, leased lines and the

PSTN or the GSM telephone network. See 8 and 10.2;

• the TCP-UDP/IP based communication profiles. These profiles support data exchange via the Internet

over various physical media, like Ethernet, ISDN, GPRS, PSTN or GSM using PPP etc. In these profiles,

the COSEM AL is supported by the COSEM transport layer(s), comprising a wrapper and the Internet

TCP or UDP protocol. Lower layers can be selected according to the media to be used, as the TCP-UDP

layers hide their particularities. See 7 and 10.3;

• the S-FSK PLC based communication profiles. These profiles support data exchange via power lines

using S-FSK modulation. In these profiles, the COSEM AL is supported by the connectionless LLC

sublayer as specified in IEC 61334-4-32, or the LLC sublayer using the data link layer based on the

HDLC protocol as specified in IEC 62056-46 / clause 8 The MAC and the Physical layers are as

specified in IEC 61334-5-1, with the extensions specified in this document. See 10.4.

Further communication profiles to support other media can be easily developed. The elements to be

specified in each profile are given in 10.1.

4.2 Connection (association) oriented operation

The xDLMS application protocol is a connection-oriented (CO) protocol. It means, that the client

and server APs can use the services of the xDLMS ASE only when they are “associated”

Figure 4

. In this

environment a communication session consists of three phases, as it is shown in :

• to be able to exchange application data, an application level connection, called Application Association,

has to be established between a client and a server AP. This is the task of the connection-oriented

ACSE of the AL. Before initiating the establishment of an AA, the peer PhLs of the client and server side

protocol stacks have to be connected. The intermediate layers may have to be connected or not. Each

layer, which needs to be connected, may support one or more connections simultaneously;

• once the necessary AA is established, application data exchange can take place using the services

provided by the xDLMS service element;

• at the end of the data exchange, the AA has to be released.

Client AP Server AP

Phase 1:

Connection establishment

Phase 2:

Data transfer

Phase 1:

Connection release

Figure 4 – A complete communication session in the CO environment

For the purposes of very simple devices, one-way communicating devices, and for multicasting and

broadcasting pre-established AAs are also allowed; see 9.4.4.4. For such AAs, the full

communication session may include only the data transfer phase: it can be considered that the

connection establishment phase has been already done somewhere in the past. Pre-established

AAs cannot be released.

4.3 Interoperability and interconnectivity in COSEM

In the DLMS/COSEM environment, interoperability and interconnectivity is defined between client

and server APs. A client and a server AP must be interoperable and interconnectable to ensure

data exchange between the two systems.

Application associations can be considered as application level connections.

剩余309页未读，继续阅读

qq_24626199

粉丝: 0
资源: 1

DLMS/COSEM通信框架详解：第七版技术报告

全部ios,迅雷下载

DLMS绿皮书完整版

迅雷下载地址

Write a review on the film Green Book or one of the other movies that your classmates have shared with us : The Godfather, The Truman Show.

movielens数据集平均评分前十

用python编写图书馆管理系统

c++图书管理求平均价格代码

html编写图书具体介绍，用外界样式表

c++libxl库修改表格颜色

pandas to_excel 添加颜色

用turn.js写一本书可以翻动的书，书共9页，封面为绿色，并获取首页翻页时的实时角度变化

QMap中如何存放三个变量，名词，名词对应的图片，名词的含义解释

python制作英文字典

写一个HTML页面，css实现样式，一个模块展示图书名称，作者，价格，还有一个可以进入图书详情页面的超链接，另一个模块展示名次，图书名称，点击量，名次变动

word.json文件示例

利用python制作英语字典

python excel 填充颜色_pandas to_excel 添加颜色操作

最新资源