OMS-Spec-Vol1_General_v140

Volume 1

General Part

Issue 1.4.0 / 2011-01-31

Release

Document History

Version Date Comment Editor

0.1 2008-02-12 Initial version for discussion in Open Metering

Meeting 2008-02-26/26 in Laatzen P. Gabriel, IMS

0.2 2008-03-05 split into three documents

first changes after review

P. Gabriel

0.3 2008-03-06 Changes after mini review with Mr. Pahl and

Mr. Guderjahn. Further integration of Laatzen

review changes

P. Gabriel

0.4 2008-03-18 Changes after first review and review of

version 0.3

P. Gabriel

0.5 2008-03-28 Changes after comments and correction of

English texts

P. Gabriel

0.6 2008-04-02

Further

correction P.

Gabriel 0.7 2008-05-08

Start

editing

080508

div. Q on wording marked

H. Baden

0.8 2008-06-30 Changes of review by Mr. Pahl and Mr. Thor

Structure changed. List of members moved to

an annex; New lists of tables and figures.

H. Baden

0.9 2008-07-12 Changes stated by Mr. Ziegler, Mr. Ossig Mr.

Feuchtmeier and Mr. Pahl implemented.

Fig.1 changed

H. Baden

0.9.1 2008-07-14 Review with Mr. Pahl H. Baden

0.9.2 2008-07-14 Review with Mr. Feuchtmeier

Fig.2 Scen.3 changed

Last version before release of V.1.0 for

external discussion.

H. Baden

1.0.0 2008-07-21 Minor

correction proposals: Prof. Ziegler

Amendments by Mr. Feuchtmeier on 2.2, 3.3

and 3.4

H. Baden

1.0.1 2008-09-19 Term ‘Customer’ changed to ‘consumer’ H. Baden

2009-01-12 Chapter ‘Security’ extended H. Baden

1.0.2 2009-01-13 3.3

M-Bus and 3.4 DLMS/COSEM completed H. Baden

1.0.2 2009-01-13 EN13757-6 added to Appendix A H. Baden

1.0.2 2009-01-26 Review with several text corrections and

amendments

AG-2 / H. Baden

1.0.2 2009-01-26 App. C List of members completed H. Baden

1.0.3 2009-02-16 Fig.1

changed: customer -> consumer,

PSTN -> DSL, Metering Devices

H. Baden

1.0.3 2009-02-16 3.5.2 and 3.7.3 corrected AG1+2 (H. Baden)

1.0.3 2009-02-16 Fig.2 changed: customer -> consumer H. Baden

1.0.3 2009-02-16 New Fig. 3, Encryption H. Baden

1.0.3 2009-02-24 List of members: EMS Patvag changed to

Swiss Gas Metering AG / MEMS AG, CH H. Baden on request of Mr. Sabattini

1.0.4 2009-03-02 Fig.

2 corrected H. Baden 1.0.4 2009-03-02 File

name

added to footer, H. Baden 1.0.4 2009-03-02 changed Fig. 3 Encryption symmetric

New Fig. 4 Signature asymmetric

H. Baden

1.0.4 2009-03-05 AMMBO added to App. B H. Baden

1.0.4 2009-03-05 Fig.1:

Consumer Interface changed to ISO/IEC

14543 H. Baden on request of Mr. Lux, KNX

1.0.4 2009-03-05 ISO/IEC

14543

added to App. A H. Baden

1.0.4 2009-03-05 PDF traced created, distributed to AG-2 H. Baden

1.0.4 2009-03-10 Fig.3

changed (KST, KSP) H. Baden

1.0.4 2009-03-17 3.7.3

and Fig.4 edited H. Baden, as of AG1#20 1.0.4 2009-03-17 Cleaned up for AG-2#20 and Plenum#8 H. Baden

1.0.4 2009-03-18 Amendment

on 3.5.3 Breaker AG-2 #20

1.0.4 2009-03-23 App. A: Reference Codes changed:

DLM2008 Æ DLMS-UA

MBUS2008 Æ MBUS-UG

OBK2008 Æ OBIS-ConvTab

SML2008 Æ SML-spec

H. Baden

1.0.4 2009-04-08 Version closed to be released as v.1.1.0 H. Baden

Version Date Comment Editor

1.1.0 2009-04-26 Release H.

Baden

1.1.1 2009-05-07 New issue draft opened for editing H. Baden

1.1.1 2009-05-07 Reactivated:

Sophisticated Meter H. Baden as of AG-2#21 1.1.1 2009-05-07 Structure of ‘3 Definitions and Terms’

enhanced and amendments added.

H. Baden

1.1.1 2009-05-07 Radiocrafts added to App. C H. Baden

1.1.1 2009-05-13 Review / changes at AG-1 meeting AG-1#22

1.1.1 2009-05-15 Definitions

without

numeration H. Baden as of AG-1#22 1.1.1 2009-05-15 Definition

of repeater added H. Baden

1.1.1 2009-05-19 Fig.2

correction: connection of one meter to

more than one MUC to be marked as

alternatively but not at same time

H. Baden

1.1.2 2009-06-12 New draft issue opened H. Baden

1.1.2 2009-06-12 Fig.2 Legend completed; lines shaped more

clear

Abbreviation MUC definition completed

H. Baden as of AG-2#22

1.1.2 2009-06-12 Issue

distributed to AG-1 and AG-2 members

for meeting review and release

H. Baden

1.1.3 2009-07-04 Editorial corrections H. Baden

1.1.3 2009-07-05 Reference ETSI2006 changed to ETSI-ERM H. Baden as submitted

by Mr. Evjen

1.1.3 2009-07-05 Definition

‘Breaker’ changed to ‘Actuator’ in

accordance to Vol.2 / AG1 H. Baden as submitted by Mr. Evjen

1.1.3 2009-07-05 Reference REC7003 corrected to ERC7003

New references added:

EN 60870-5-2 and NTPv4 H. Baden in adaption to OMSS Vol.2 V.1.0.8

1.1.3 2009-07-06 Version closed for release as V.1.

2.0 H. Baden

1.1.3 2009-07-17 Final corrections (only formal) H. Baden

1.2.0 2009-07-17 Release

for publication H. Baden

1.2.1 2009-10-07 Checked for register value, no changes

necessary

H. Baden

1.2.2 2009-12-18 Definition of the OMS-MUC added to 3.2 H. Baden as of AG-2, Action 21-09 1.2.2 2010-03-24 3.1 changed to table-structure H. Baden

1.2.2 2010-03-14 E-DIN

43863-5

added to App. A H. Baden

1.2.2 2010-03-24 App. C Member list updated H. Baden

1.3.0 2010-03-24 Editorial

fix up and release H. Baden

1.3.1 2010-03-29 Page 6 Line 12: KNX added H. Baden as of Mr. Lux

1.3.2 2010-11-08 Footer

changed from Open Metering

to OMS GROUP

H. Baden

1.3.2 2010-11-09 OMS Logo added to front page and Headline H. Baden

1.3.2 2010-11-10 App. C Member list updated H. Baden

1.3.3 2010-11-18 Abbreviations

MUCC and OMSS added to App.

B; Definition MUC rendered more precisely;

editorial corrections H. Baden as of Mr. Peters, Mr Sabbattini and Mr. Lorenzen

1.3.4 2010-12-01 Changes on ‘3.5 Offline Tariffing’ and ‘3.6

Security’ to clarify the difference between basic

and sophisticated meter.

H. Baden as of OMS plenary #11.

1.3.4 2010-12-13 Headline / Logo edited

Ammendment to the definition MUCC

H. Baden as of Mr. Pahl

1.3.4 2011-01-27 Secondary

Communication

added to 2.1 H. Baden as of AG1#31

1.4.0 2011-01-31 Final

editorial fix up and release H. Baden

Table of contents

1Introduction (6)

1.1Text mark up (7)

2General Definitions and System Description (8)

2.1Total System Overview (8)

2.2System Topology (9)

3Definitions and Terms (10)

3.1Market Roles (10)

3.2Functional Units (10)

3.3Interfaces and Protocols (11)

3.4Metering Devices (12)

3.5Offline Tariffing (13)

3.6Security (14)

4References to Standards (16)

Appendix A:Referenced Documents (17)

Appendix B:Abbreviation Index (19)

Appendix C:Members (21)

List of figures

Figure 1: System Environment (8)

Figure 2: Different System Topologies (9)

Figure 3: Encryption - Decryption (14)

Figure 4: Signature and Validation (15)

1 Introduction

This specification focuses on an automatic meter readout system, called Open Metering System (OMS). Part of this system is the Multi Utility Communication.

A Multi Utility Communication Controller (MUC Controller; MUC) is a hardware system which

is used to readout different metering devices and to transfer subsets of this data to ‘AMM 5

back office systems’ for billing, servicing or other purposes.

Metering devices are sensors and actuators which are defined in “Chapter 3 Definitions and Terms”. Metering devices and AMM Systems have to follow certain protocols which are described within this document for Open Metering conformity.

Working groups have been established consisting of members from different companies who 10

are working in the energy supply and metering areas to work out this specification. The Open Metering Working Groups specifies communication interfaces for the MUC and different communication endpoints. The vendor associations Figawa1, ZVEI2 and KNX3 are chairs in this specification creation process.

Communication with the MUC splits up into primary, secondary and tertiary communication:

15

•The primary communication handles multi-discipline metering devices for electricity and gas as well as heat and water meter reading. Its goals are the definition of the transmission media, of the transmission techniques and of the protocols between the metering devices on the one hand and the MUC on the other hand.

•The secondary communication focuses on an extension of the covered range (wired, 20

PLC or wireless) using networking and multi hopping based on a routing protocol. A unified secondary communication is not defined yet. If necessary proprietary solutions for secondary communication may be used to transport data via a meshed network. In this case it has to be ensured that data send out by an open metering meter are provided as

defined in the Open Metering System Specification.

25

A simple manufacturer independent extension of the radio range, based on repeater

technologies, is described in the part primary communication (OMSPC).

•The tertiary communication is the interface between a MUC and the back office systems for automated meter management (AMM). It specifies the data flow for defined pull and

push procedures between the MUC and the AMM back office system. The main topics in 30

tertiary communication are data acquisition and data providing for presentation, event handling, configuration, control and clock synchronization.

The relating documents are:

Open Metering System Specification …

Volume 1, General Part (OMSGP) – this document.

35

Volume 2, Primary Communication (OMSPC).

Volume 3, Tertiary Communication and MUC (OMSTC).

They define minimal requirements on communication and functionality between given endpoints. Manufacturers and suppliers should be encouraged to develop their hardware and

software in a common direction. The transport of data is specified only up to the TCP/IP layer 40

of the Ethernet interface.

1 Bundesvereinigung der Firmen im Gas- und Wasserfach e.V., Cologne

2 Zentralverband Elektrotechnik- und Elektronikindustrie e.V., Frankfurt am Main

3 KNX Association, Brussels

1.1 Text mark up

Text mark up is defined throughout all Open Metering System documents as follows: •Italic text is used if new terms are invented.

•References to documents are given in square brackets: [ ]

•Parentheses mark up abbreviations or options, defined at

5

Appendix B: Abbreviation Index

•Work items are marked up by the word [WORKITEM] in square brackets with a yellow background.

2 General Definitions and System Description

This chapter presents a total system overview including all term definitions and references to

used standards.

2.1 Total System Overview

5

Figure 1: System Environment

Figure 1 illustrates the total system overview. The upper half shows the user’s view: the system which has been installed at the consumer locations connects to a Distribution System Operator (DSO) or other market participants via internet communication technologies 10

provided by GSM, Telephone Systems (PSTN), Power Line Communication or broad-band networks. The interface for this communication is standardized on a TCP/IP basis.

The lower half (technical view) shows the MUC which is installed at the consumer’s location.

Primary communication is used for close-up range communication with meters; tertiary

communication is mainly used by the MUC to communicate with Metering service providers 15

(MSP) which may be but does not have to be the MSO4 or the DSO5.

4 MSO – Meter Site Operator

5 DSO – Distribution Service Provider (distribution network operator)

2.2 System Topology

Figure 2 shows different scenarios of the system topologies. The AMM back office system maintains a connection to several MUCs. The MUCs themselves keep the connection to several meters.

In practice all shown scenario options may appear as a hybrid topology if supported by

5

the particular product.

Scenario 1 will be used if each

apartment has its own MUC

Controller. Each metering device of

an apartment is assigned to its one

10

specific MUC.

Each consumer may have his own

display unit (dedicated display, web

browser application, PDA …)

connected to his specific MUC, to

15

receive energy consumption

information and e.g. tariff data.

Habitations or facilities are

independent.

20

In Scenario 2 displays are getting

data from the AMM back office,

provided by an internet portal

system or read meter data directly

from the meter.

25

Meters can be shared among

MUCs to avoid out of range

problems.

Scenario 2 topology may also be

used at installation phase to set up

30

installations of scenario 1.

Scenario 3 shows clustering6 of

some MUCs and primary

communication with additional

35

repeaters.

Figure 2: Different System Topologies

6 This is not subject of the OMS specification but may be realized as a proprietary solution as long as

defined requirements of this specification are fulfilled.

3 Definitions and Terms

This chapter contains the major definitions and terms used in this specification.

More detailed definitions will be given at a separate glossary document.

3.1 Market Roles

According to the European legislation for the internal energy markets a set of market roles 5

were established to fulfil the requirements on legal and functional unbundling of consolidated companies.

Meter Site Operator (MSO) The MSO is owner of metering devices. He is reliable on legal and operational functionality of the meter site.

Metering Service Provider (MSP) A MSP is an organizational entity that is authorized by the connected party (consumer) to read the data and/or status of metering devices. Operator of an AMM back office and distributor of meter data to authorized parties.

Distribution System Operator (DSO) This is a Company that is assigned to operate and manage one or more distribution networks, also known as grid operator.

Energy Supplier (ESU) Company that delivers (sells) energy like electricity, gas, heat

etc. to consumers.

Consumer (CSR) This is the end user of energy, also known as customer.

3.2 Functional Units

A functional unit is an entity of hardware, software or both, capable of accomplishing a

10

specified purpose separated by task or impact. At OMS the MUC is defined as a functional unit to leave open the position or physical outline. The MUC may be a unique device or a distributed system as well as an integrated functional unit of e.g. an electricity meter.

MUC Controller

The Multi Utility Communication (MUC) is in focus of the OMS specification. The short form 15

MUC is also used for the MUC-Controller. As plural form MUCs is used.

The MUC is a meter data communication system which collects data from metering devices for electricity and gas as well as heat and water consumption. Metering values will be transferred to the MUC Controller (MUC) and will be processed there to transmit them to

AMM back office systems as well as to offer energy usage information to the consumer.

20

OMS-MUC is the functional unit MUC described by the Open Metering System Specification (OMSS) doing data processing to provide data transfer of meter readings, commands and status information.

AMM Back Office

In this specification the endpoint where all MUCs connect to is referred to as AMM back 25

office (AMMBO). AMM stands for Automated Meter Management and refers to systems

which collect data. AMM back office systems can be found at Metering Service Providers (MSP) who may be identical with Meter Site Operators (MSO) or Distribution System Operators (DSO).

In literature the term “management” is sometimes replaced by “infrastructure”, which results in Automated Metering Infrastructure (AMI).

5

AMM back office systems themselves are processing metering data to be transferred as billing and balancing information to ERP systems of resource providers or other suppliers.

3.3 Interfaces and Protocols

M-Bus

M-Bus is defined as standard for primary communication particularly with regard to battery 10

driven metering devices. Different physical media can be used here.

In order to distinguish between different M-Bus transport mechanism and application protocols, the following terms are introduced:

•Wired M-Bus (M-Bus)

is the term for communicating via two-wire M-Bus lines [EN13757-2].

15

•Wireless M-Bus (wM-Bus) is used for M-Bus RF [EN13757-4].

The M-Bus modes S1, S2, T1 and T27 may be used as meter interfaces for the

MUC Controller. Modes S1 and T1 are defined for unidirectional communication

from meter to MUC. Modes S2 and T2 provide a back channel for bidirectional

communication. Modes S and T are operating at different frequency ranges in the 20

frequency band 868 to 870 MHz. They have different data rates:

o S-Modes (Stationary mode) provide a data rate of 16,384 baud at a longer communication distance than T-Mode. Modes S1 and S2 are compatible with

the wireless KNX-system of ISO/IEC enabling combined systems for home

automation and open metering.

25

o T-Mode (Transmit frequently) provides a data rate of 66,667 baud. This is approximately four times higher than the S-modes and allows for a given

battery size more frequent transmissions without decreasing battery lifetime or

increasing collision rate. This enables a faster user feedback on his

consumption.

30

Due to this higher transmission frequency, drive-by or walk-in meter readout is

also feasible.

The back channel of T2 uses the same frequency and data rate as S2 to allow

economic receiver design.

o R-mode (Receive frequently) is not in the scope of open metering.

35

•If the application protocol is referenced, this is done by the term M-Bus protocol [EN13757-3].

•Usage of M-Bus as a generic system is referenced as M-Bus system.

•M-Bus communication via power line (M-Bus-PLC) is considered as a future

option and is not focus of this document.

40

7 Refer to [EN13757-4] and [OMSPC]

•According to energy efficiency of battery driven metering devices the standard M-Bus-Application transports shorter DIF/VIF coded data more efficient than by

OBIS based application protocol.

DLMS/COSEM, SML

DLMS/COSEM and SML are additional application protocols which will be applied in both 5

Primary and Tertiary communication as alternative software solutions. These protocols transport the related OBIS-number together with each data point.

OBIS coded COSEM or SML data may also be carried via M-Bus.

3.4 Metering Devices

In this specification different device types are defined, which are commonly referred to as 10

metering devices. These devices can communicate to or with a MUC via one of the primary communication interfaces. Metering devices in this specification are sensors and actuators.

Sensors are metering devices which at least provide meter index data (current metering counter value).

Actuators are breakers or load delimiters.

15

An authentication procedure is required for controlling devices by commands.

Unidirectional wireless M-Bus metering devices will always operate in push mode.

Pull mode may be possible with bidirectional data flow, if the metering device is supplied with external power or after communication was established in push mode.

Wired M-Bus metering devices will always communicate in pull mode. Even alarm messages 20

are pulled via frequent polling.

With other wired meter interfaces like RS232, RS485 or PLC push and pull may be possible.

Basic Meter

Basic meter are meters with minimal functionality. Current metering data are given by

request or sent in regular intervals. Note that regular intervals are not precisely regular. A 25

small deviation should be applied to minimize collisions on the air interface.

Communication data flow can be unidirectional or bidirectional. Sent Metering data are identical with data displayed on an integrated display. Authentication is not needed to access the meter index.

Sophisticated Meter

30

Sophisticated meters are basic metering devices with additional features such as data logging. The metering data given by these devices could include timestamps and metering profiles of the recorded consumption data.

Sophisticated metering devices have an internal clock to enable data logging of load profiles

at regular metering periods (e.g. 60 Min.) and other time related functions.

35

Communication data flow is always bidirectional. For functions beyond meter readout authentication using a signature is needed. Metering data are always signed. ECC is used as technology for the creation of an authentication signature.

A feature to limit or cut-off the feed in8 might be used in sophisticated metering devices.

Actuator

Throughout this specification the term ‘actuator’ is used to describe appliances which can limit consumption or cut-off the supply9. Terms which are included in the term ‘actuator’ are breaker, limiter, shut-off-valve, gas valve or switch. Bidirectional communication is mandatory 5

for these devices.

The functional unit MUC as described by Open Metering (OMS-MUC) does not contain the switching or delimiting functionality. Only data transfer of commands and status information is done by the MUC.

Repeater

10

To extend the range of wireless primary communication (e.g. on the wM-Bus) repeaters may be used.

On unidirectional metering devices a “unidirectional” repeater is defined which must not repeat any telegrams from a MUC assigned to a unidirectional meter.

The bidirectional repeater is repeating telegrams in both directions from a metering device as 15

well as from a MUC.

3.5 Offline Tariffing

In normal Tariffing, a tariff has a fixed period. Resource consumption costs a fixed rate per

period. In offline Tariffing this is different: sophisticated metering devices have to record the 20

consumption per time unit (period) in a table as a metering profile and should be able to show the values on an internal display.

A lternatively the index values are sent to the AMM back office system immediately. In this

case the index values should be encrypted for confidential transmission and a meter

signature has to be added to the telegrams to ensure integrity and to meet the issues of legal 25

metrology.

Tariffing can be dynamic, depending on the consumption volumes or is based on supply and demand principles. Other models are imaginable. The current tariff could be displayed on the consumer display or the consumer could choose a tariff which is most suitable for a period.

An alternative term for offline Tariffing is downstream Tariffing.

30

8 Compare: Breaker

9 Of electricity or gas

3.6 Security

Security items were recognized as essential to achieve legal and social acceptance of an innovative residential metering.

There are three occurrences to be handled by security procedures:

•Loss of availability

5

•Loss of confidentiality (to prevent unauthorized reading of data) – to be achieved by o encryption of the data telegrams,

especially on wireless and power line communication

o change of telegram content even if no index feed happened

o a sophisticated user and access rights management

10

•Loss of integrity and authenticity – to be protected by signature of data records

Security techniques are used in different contexts regarding authentication or secure transmission using different encryption techniques.

Encryption

To provide confidentiality of meter data these should be encrypted. Encryption should be 15

done at primary communication as well as on tertiary communication.

Encryption is mandatory for wireless and PLC communication.

Figure 3: Encryption - Decryption

20

Specification of encryption and decryption methods and procedures in detail are described in [OMSPC] and [OMSTC].

Meter Signatures

Meter signature is not required at the current specification focused on basic meters..

As a future option – if requested – the meter can sign the metered values to enable validation of the data source.

Command Signatures

5

[WORKITEM: to decide symmetric or asymmetric signature]

On AMM back office to meter (via MUC) communication authentication by signature of command data records is mandatory if meter setting commands were sent

•with influence to the metering behaviour (e.g. tariff register, due date)

as well as

10

•delimiting or switching commands were sent to affect feed in of the metered media.

The MUC itself does not sign pass-through data or commands anyway.

Specifications of signature in detail are given in OMSPC and OMSTC10.

Figure 4: Signature and Validation

15

10 Not done yet, planned for further versions.

4 References to Standards

M-Bus (Meter-Bus) is an European standard for remote reading of all types of consumption

meters as well as for various sensors and actuators [MBUS2008]. References in detail:

EN 13757-2 Communication systems for and remote reading of meters – Part 2: Physical and link layer

5

EN 13757-3 Communication systems for and remote reading of meters – Part 3: Dedicated application layer

EN 13757-4 Communication systems for meters and remote reading of meters - Part 4: Wireless meter readout (Radio meter reading for operation in the 868 MHz to 870 MHz SRD

band)

10

OBIS (Object Identification System) is specified in DIN EN 62056-61:2002 and EN 13757-1.

It uses classification numbers to identify data types. These numbers are specified both for measuring equipment and data transmission.

SML (Smart Message Language) is a communication basis for applications in the

parameterisation and data acquisition environment of metering devices. Data acquisition and 15

exchange is the primary goal of the underlying protocol language, firmware upgrades of embedded systems should also be possible via SML. Communication is encoded using XML (SML XML) or in a binary form (SML Binary Encoding). Both encodings are equivalent to each other. The specification is given in [SML2008].

DLMS/COSEM(Device Language Message Specification / Companion Specification for 20

Energy) is specified in IEC 62056 / EN13737-1. Main focus of this language specification is the interoperability of utility meter data exchange [DLM2008]. An introduction to this language is given in [Wis1999].

NTP (Network Time Protocol) is a protocol for synchronizing the clocks of computer systems

over packet-switched, variable-latency data networks. NTPv4 is the minimal requirement for 25

the Open Metering System. It is specified in [RFC1305-1992].

Appendix A: Referenced Documents

DLMS-UA DLMS User Association, in internet: http://www.dlms.com .

(defined before as DLM2008)

ETSI-ERM EN 300220-1 V.2.1.1 Electromagnetic compatibility and Radio spectrum

Matters (ERM); Short Range Devices (SRD); Radio equipment to be

5

used in the 25 MHz to 1000 MHz frequency range with power levels

ranging up to 500 mW; Part 1: Technical characteristics and test

methods; 2006.

E-DIN 43863-5 Identification number for measuring devices applying for all

manufacturers (please refer to the latest issue of this emerging

10

standard).

EN13757-1 Communication system for meters and remote reading of meters -

Part 1: Data Exchange.

EN13757-2 Communication system for meters and remote reading of meters -

Part 2: Physical and Link Layer.

15

EN13757-3 Communication system for meters and remote reading of meters -

Part 3: Dedicated Application Layer.

EN13757-4 Communication system for meters and remote reading of meters -

Part 4: Wireless Meter Readout.

EN13757-5 Communication system for meters and remote reading of meters - 20

Part 5: Repeater Functionality.

EN13757-6 Communication systems for meters and remote reading of meters -

Part 6: Local Bus

EN60870-5-2 Telecontrol equipment and systems - Part 5: Transmission protocols -

Section 2: Link transmission procedures.

25

EN62056-61:2002 Object Identification System

ERC7003 ERC RECOMMENDATION 70-03 (Tromsø 1997 and subsequent

amendments) relating to the use of short range devices (srd)

Recommendation adopted by the Frequency Management, Regulatory

Affairs and Spectrum Engineering Working (July 2008)

30

http://www.erodocdb.dk/Docs/doc98/official/pdf/REC7003E.PDF FIPS197 Specification for the ADVANCED ENCRYPTION STANDARD (AES)

http://www.csrc.nist.gov/publications/fips/fips197/fips-197.pdf

Nov 2001

ISO/IEC 14543-x-x Architecture for Home Electronic Systems

35

MBUS-UG Homepage of the M-BUS user group, in internet: http://www.m-bus.com,

(defined before as MBUS2008).

NTPv4 no released public specification available, you may refer to

http://tools.ietf.org/html/draft-ietf-ntp-ntpv4-proto-11

OBIS-ConvTab Conversion table for metering media, OBIS Basiszähler.xls by Open

40

Metering Group, always check for the latest issue please. (Defined

before as OBK2008.) This reference changed to [OMSPC] Annex A.

SML-spec Smart Message Language Specification (defined before as SML2008),

please check for the latest issue: http://www.m-u-c.org/download.htm or

http://www.vde.de/de/fnn/arbeitsgebiete/messwesen/seiten/messwesen.

aspx

PTB50-2002 Software-Anforderungen an Messgeräte und Zusatzeinrichtungen

gemäß PTB-A 50.7 (in German) (in internet April 2002)

http://www.ptb.de/de/org/2/23/234/download_info-center/ptb-a50_7-2.pdf 5

RFC1305-1992 Request for comments 1305, in internet http://www.ietf.org/rfc/rfc1305.txt RFC2553 IPv6

WELM2004 WELMEC-European cooperation in legal metrology – Software Guide

(Measuring Instruments Directive 2004/22/EC) , 7.2, Issue 2, In Internet

http://www.welmec.org/publications/7-2.asp, visited Feb 2008.

10

Wis1999 The migration process to DLMS-COSEM: a short discussion beside the

German way to interoperability [in automatic meter reading] Wisy M.,

Metering and Tariffs for Energy Supply, 1999. Ninth International

Conference on (Conf. Publ. No. 462), Aug 1999 Page(s):119 – 123

Appendix B: Abbreviation Index

AES Advanced Encryption Standard

AMI Automated Metering Infrastructure

AMM Automated Metering Management

AMMBO AMM Back Office – a meter reading and meter management system

5

APL Application

Layer

COSEM Companion Specification for Energy

DES DES and Triple DES (3DES) are outdated Data Encryption Standards

DIF Data information field (Control field in variable data point of M-Bus-Protocol)

DLMS Device Language Message Specification

10

DSO Distribution System Operator

ECC Elliptic Curve Cryptography

ERP Enterprise Resource Planning

GSM Global System for Mobile Communication

Lo-Bus Local Bus, an M-Bus extension as defined in EN13757-6

15

M-Bus physical 2-wire M-Bus as defined in EN13757-2

M-Bus-AL M-Bus application layer or M-Bus application protocol as defined in EN13757-3 MSO Meter Site Operator

MSP Metering Service Provider

Communication;

Multi Utility Communication Controller

Utility

MUC Multi

20

(in other documents outside OMS also MUC-C is known for the MUC Controller) NTP Network

Protocol

Time

System

OBIS Object

Identification

ODC Operating Data Channel (in tertiary communication)

System

Metering

OMS Open

25

OMSS Open Metering System Specification

OMSGP OMSS Vol. 1 – General Part

OMSPC OMSS Vol. 2 – Primary Communication

OMSTC OMSS Vol. 3 –Tertiary Communication

PTB Physikalisch-Technische

Bundesanstalt

30

(the German legal metrology institute, providing scientific and technical services) RTC Real Time Clock

SDC Service Data Channel (in tertiary communication)

Language

SML Smart

Message

Communication

line

PLC Power

35

PSTN Public Switched Telephone Network

RFC Request for Comments

VIF Value information field (Control field in variable data point of M-Bus-Protocol)

wM-Bus wireless M-Bus as defined in EN13757-4

Appendix C: Members

Thanks are to be given to the companies11 and their employees for all their efforts of time, work and financial support being involved in the consortium to develop this specification: •Amber Wireless GmbH

• Apator GmbH

5

• Aquametro AG, CH

•Bär Industrie-Elektronik GmbH

•Brunata GmbH & Co. KG

• DIEHL Metering

• Elster GmbH

10

•ELSTER Messtechnik GmbH

•EMH metering GmbH & Co. KG

•GOK GmbH & Co. KG

•GWF MessSysteme AG

•Hager Elektro GmbH

15

• iAd GmbH

• ISKRAEMECO d.d.

•Itron Allmess GmbH

• Itron GmbH

• Kamstrup A/S

20

•Lackmann Zähler Gesellschaft mbH & Co. KG

•Landis + Gyr GmbH

•NZR GmbH & Co. KG

• QUNDIS GmbH

• Radiocrafts AS, Norway

25

•Robert Bosch GmbH

•Sensus Metering Systems GmbH

•SSV Software Systeme GmbH

•Swiss Gas Metering AG / MEMS AG

•Techem Energy Services GmbH

30

•Tixi.Com Telecommunication Systems GmbH

• WIKON Kommunikationstechnik GmbH

11 listed in alphabetical order

Institutional Members are:

•EMSYCON, for FNN

• Figawa, Cologne

•Fraunhofer ISE, Freiburg

• Fraunhofer IMS, Duisburg

5

•HBM management services, Hartmut Baden, Consultant

• KNX Association, Brussels

•Prof. Dr. Horst Ziegler

•Steinbeis-Innovationszentrum Embedded Design und Networking (sizedn), Lörrach

•ZVEI, Frankfurt am Main

10