IEC TR 61850-80-5:2024 电力设施自动化用通信网络和系统.第80-5部分:IEC 61850和IEC 61158-15之间映射信息指南

标准编号：IEC TR 61850-80-5:2024

中文名称：电力设施自动化用通信网络和系统.第80-5部分:IEC 61850和IEC 61158-15之间映射信息指南

英文名称：Communication networks and systems for power utility automation - Part 80-5: Guideline for mapping information between IEC 61850 and IEC 61158-15

发布日期：2024-02-09

标准范围

技术报告IEC TR 61850-80-5:20 24规定了通过利用IEC 61850和IEC 61158-6 IED/子系统之间的网关来构建和配置使用IEC 61850和IEC 61158-6（工业通信网络-现场总线规范，CPF类型15，Modbus）协议的系统的映射规则。目标是在这些IED/子系统之间实现可操作的运行时数据交换，并尽可能自动化网关的配置。请注意，就本文档而言，“Modbus”用于表示串行Modbus（Modbus RTU）和IEC 61158-6（Modbus TCP）。在每个协议的能力内，除了操作真实属性之外，还映射了一些配置属性（IEC 61850-7-3:20 0+AMD1:2020具有功能约束CF的属性）。时间数据。本文件中规定的规则基于已发布的标准，不对IEC 61850或61158-6进行任何拟议变更。本标准没有规定IEC 61850 IED与Modbus IED直接通信的任何规则，反之亦然，除非通过网关。本文件没有规定特定IED应支持哪些数据项，无论实施是使用Modbus还是IEC 61850。相反，该文档提供了指定网关如何将任何给定数据项从一个协议映射到另一个协议的规则，假设数据项已经可用并且使用其中一个协议进行传输。类似地，本文档没有规定给定网关应支持哪些映射规则。当本文件作为技术规范重新发布时，将确定符合性要求。本文档认识到，将存在用户将要求网关执行非标准协议映射的情况。非标准映射超出了本文档的范围。本文档还认识到，网关通常以各种方式操纵通过它们的数据。其中一些功能包括报警触发分组、数据抑制、联锁和命令阻塞。遵守本文件并不排除网关执行此类功能，即使本文件主要规定了Modbus数据到IEC 61850-7-3:20 0+AMD1:2020数据的“直通”映射。本文档的子条款7.4描述了如何通过使用XML中的等式符号的映射工具将这些函数中的一些指定给网关。然而，这些功能中的一些对于映射工具来说可能太复杂而无法以自动方式指定。用于交换运行时信息的映射架构由四个部分组成:1)网关的概念架构和相关用例2）信息模型的映射（为Modbus数据分配语义）3）数据的映射（实际上是信息模型的一部分）4)服务的映射（超出本文档的范围）

IEC TR 61850-80-5:2024, which is a Technical Report, specifies the mapping rules for building and configuring a system using both IEC 61850 and IEC 61158-6 (Industrial communication networks - Fieldbus specification, CPF Type 15, Modbus) protocols by utilizing gateways between IEC 61850 and IEC 61158-6 IEDs / subsystems. The objective is to enable operational run-time data exchange among these IEDs / subsystems, and to automate the configuration of a gateway as much as possible.
Please note that for the purposes of this document, "Modbus" is used to represent both serial Modbus (Modbus RTU) and IEC 61158-6 (Modbus TCP).
Within the capability of each protocol, some configuration attributes (IEC 61850-7-3:2010+AMD1:2020 attributes with functional constraint CF) are also mapped in addition to the operational real-time data.
The rules specified in this document are based on the published standards and do not make any proposed changes to IEC 61850 or 61158-6. This standard does not specify any rules for an IEC 61850 IED to directly communicate with a Modbus IED and vice versa, except through a gateway.
This document does not mandate which data items that a particular IED shall support, regardless of whether the implementation uses Modbus or IEC 61850. Instead this document provides rules specifying how a gateway maps any given data item from one protocol to the other, given that the data item is already available and is transmitted using one of the protocols.
Similarly, this document does not mandate which mapping rules a given gateway shall support. When this document is republished as a Technical Specification, conformance requirements will be identified.
This document recognizes that there will be situations in which a user will require that a gateway perform non-standard protocol mappings. Non-standard mappings are outside the scope of this document.
This document also recognizes that gateways typically manipulate the data passing through them in a variety of ways. Some of these functions include alarm trigger grouping, data suppression, interlocking and command blocking. Conformance to this document does not preclude a gateway from performing such functions, even though this document primarily specifies "straight through" mapping of Modbus data to IEC 61850-7-3:2010+AMD1:2020 data. Subclause 7.4 of this document describes how some of these functions may be specified to a gateway by a mapping tool using equation notation in XML. However, some of these functions may be too complex for a mapping tool to specify in an automated manner.
The mapping architecture for the exchange of the run-time information consists of four parts:
1) Conceptual architecture of a gateway and associated use case
2) Mapping of the information model (Assign semantic to the Modbus data)
3) Mapping of the data (which is in fact part of the information model)
4) Mapping of the services (out of scope for this document)

标准预览图