P2 Companion Standard - search read.pudn.comread.pudn.com/downloads145/doc/633047/DSMR v2.2...

of 36

File name: Dutch Smart Meter Requirements v2.2 final P2.doc Date: 18-04-2008

Author: KEMA Consulting Config. ID: B1042

Version: 2.2 final Project: Functional and technical specifications Smart Meters

P2 Companion Standard

Dutch Smart Meter Requirements

By order of: Enbin

Reference: B1042

Date: April 18th, 2008

Version: 2.2

Status: Final

of 36




Change Summary

Revision Created /

Modified

Date Approved Comment

Base Nuon 26-Feb-06 Original version by Nuon, sepa-

rate documents for E, G, T

2.1 H. Pille 04-Feb-08 Steering group Final version

2.2 H. Pille 04-Apr-08 Steering group Clarifications in the wireless

frame format, correction of the

wireless binding procedure and

alarm / status reporting.

Added objects for location in-

formation and function location

2.2 H. Pille 18-Apr-08 Steering group Clarifications in terminology

and binding and unbinding pro-

cedure.

of 36




Issue list

Version Activity

2.2

The start bytes of the FT3 frame used for wireless transmission are not clearly

specified in the EN 13757-4 standard. It is not certain whether or not these two

bytes must be included in the FT3 frame.

of 36




CONTENTS

1 Introduction .......................................................................................................... 5

1.1 Scope................................................................................................................... 5

1.2 System architecture ............................................................................................. 6

1.3 Normative references........................................................................................... 7

1.4 M-Bus protocol description................................................................................... 7

1.5 Physical Layer...................................................................................................... 7

1.6 Data link layer ...................................................................................................... 8

1.7 Data Encryption ................................................................................................... 9

1.8 Application Layer.................................................................................................11

1.9 M-Bus data exchange with meters ......................................................................12

1.10 M-Bus communication Variable Data Blocks .......................................................20

2 Power supply ......................................................................................................24

2.1 Maximum current ................................................................................................24

2.2 Power outage......................................................................................................24

3 Installation procedures ........................................................................................25

3.1 General installation procedures...........................................................................25

3.2 Wired configurations ...........................................................................................25

3.3 Wireless configurations .......................................................................................26

3.4 Replacing an M-Bus device.................................................................................31

4 Encryption Key Management Procedures ...........................................................32

4.1 M-Bus devices default encryption keys ...............................................................32

4.2 Encryption key exchange procedures..................................................................32

5 P2 – P3 mapping.................................................................................................34

6 Document list ......................................................................................................36

of 36




1 INTRODUCTION

1.1 Scope This document provides a companion standard for an Automatic Meter Reading (AMR) sys-

tem for electricity thermal, (heat & cold), gas, water and hot water meters. The scope of this

standard is on:

� Residential electricity meters

� Residential thermal (heat & cold) meters

� Residential gas meters and gas valve

� Residential water meters

This companion standard focuses on the P2 interface for Gas, Gas valve, Thermal (heat /

cold), and Water meters. There is no separate interface for electricity meters since these me-

ters are technically part of the metering system.

Figure 1 Meter interfaces overview.

The goal of this companion standard is to reach an open, standardized protocol implementa-

tion and functional hardware requirements related to the communication between several

types of meter and an electricity meter. Note that omission in this document of any feature

listed as “REQUIRED” in the EN 13757 documents (ref section 1.3) does not mean that this

feature need not be implemented. Features described as “OPTIONAL” in the EN 13757

documents need only be implemented if these features are referred to in this companion

standard.

This companion standard is the result of a combined effort of the major Dutch grid operators.

CAS

Independent Services Provider

Supplier

Grid company

P1

G

E

Metering

system Other

Services

Module

W/T

P3

P2

P4

P0

of 36




1.2 System architecture This standard focuses on AMR for meters connected to an electricity meter.

Figure 2 M-Bus: Wired infrastructure

The communication bus is based on the M-Bus standard. References to the M-Bus standard

are included in section 1.3. This companion standard only includes deviations, clarifications

or additions to the standard as defined in the relevant standard documents.

Two infrastructures are referred to in this standard: the wired and the wireless versions. The

wired version is shown in Figure 2. The wired version is described in EN-13757-2. In the

wired version the electricity meter functions as the communication master, the other devices

connected to the M-Bus function as communication slaves. Due to uniformity reasons and

independency of used communication medium all data exchange over the wireless and

wired connection must be encrypted. The wireless version is shown in Figure 3 and is de-

scribed in EN-13757-4.

Figure 3 M-Bus: Wireless infrastructure

The electricity meter, functioning as Bus Master in the wired architecture and as listener in

the wireless infrastructure, will gather and store information from all connected meters or de-

vices and forward this information to the Central Access Server (CAS). Furthermore it will

control (e.g.) the gas valve. The maximum number of M-Bus devices associated with a single

E-Meter is four. This includes all wired, wireless M-Bus devices. The data requirements of

the CAS are based on NTA 8130 (ref. section 1.3).

of 36




1.3 Normative references The following standards are referred to in this company standard. For undated references the

latest edition applies.

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

layer

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 me-

ter readout (Radio meter reading for operation in the 868 MHz to 870 MHz SRD band)

NTA 8130

NL:2007

Basisfuncties voor de meetinrichting voor elektriciteit, gas en thermische energie voor

kleinverbruikers

FIPS-197 ADVANCED ENCRYPTION STANDARD (AES), published by the National Institute of

Standards and Technology (NIST), USA.

Functional requirements for the metering system are defined in the NTA Requirements docu-

ment.

1.4 M-Bus protocol description The protocol can be described using the 7-layered Open System Interconnection (OSI)

model.

1.5 Physical Layer

1.5.1 Wired connection 1.5.1.1 Electrical specification M-Bus is a protocol that is described for remote reading of meters in the European standard

EN 13757. It is a 2 wire system that provides power to the devices. The requirements are

given in EN 13757-2.

Nr. Layer Type of layer Functions Standard

7 Application layer Data structures, data types,

actions EN 13757-3

6 Presentation layer Empty

5 Session layer

Application ori-

ented layers

Empty

4 Transport layer Empty

3 Network layer routing (optional) -

2 Data Link layer transmission parameters, telegram

formats, addressing, data integrity EN 13757-2

1 Physical layer

Transport ori-

ented layers cable, bit representation, bus ex-

tensions, topology, electrical speci-

fications.

EN 13757-2

EN 13757-4

of 36




1.5.1.2 Hardware connections and cable No physical access for P2 port is possible by customer. The connections to the P2 port must

be located behind a (sealable) lid. The bus interfaces of the slaves are polarity independent:

that is, the two bus lines can be interchanged without affecting the operation of the M-Bus

devices. Besides protection aspects, this also results in simplified installation of the bus sys-

tem. Electrical requirements including bus voltage and max current are given in EN 13757-2

section 4. Connections and wiring are according to 13757-2.

1.5.2 Wireless connection Wireless meter data will be exchanged according to the EN 13757-4 standard. Devices con-

nected through the wireless (RF) M-Bus connection will connect according to the T1 / T2

mode in EN 13757-4. See section 1.9.3 and EN 13757-4 for difference in use of T1 and T2.

The choice for T1 / T2 mode is made after consulting suppliers of M-Bus devices. Reason to

select T2 is power consumption. The T2 mode allows the M-Bus device receiver to be turned

off most of the time. Other modes (S2 or R) are expected to be less secure or are expected

to have higher power consumption due to continuously enabled receiver.

Data encoding according to EN 13757-4 section 5.4 will be used. Data sent by the M-Bus

device to the listener device shall be encoded by the “3 out of 6” code. Data sent by the lis-

tener device to the M-Bus device shall be encoded by the Manchester code (according to EN

13757-4).

1.6 Data link layer

1.6.1 Wired Connections For the wired M-Bus link layer the format class FT1.2 of EN 60870-5-1 and a telegram struc-

ture according to EN 60870-5-2 shall be used. Refer to EN-13757-2 for field definitions in

the respective protocol headers.

1.6.1.1 Master/slave The electricity meter is the master device, meaning that all communication is initiated from it.

If there is an alarm in a connected device then this will only be indicated during the next

reading of the device. It will not generate an immediate alarm. In this companion standard,

the maximum number of slaves in a wired configuration is four.

Master

Slave 2 Slave 3 Slave 1

M-Bus

Slave 4

Figure 4 M-Bus: master slave configuration

of 36




1.6.1.2 Baud rate The baud rate for wired configurations is, at all times and in any situation, fixed to 2400,E,8,1

to ensure error free communication independent of the number of meters on the bus or the

lengths of the cables.

1.6.2 Wireless Connections According to EN 13757-4 the link layer of EN 60870-5-2 with the format class FT 3 shall be

used. Refer to EN 13757-4 for field definitions in the respective protocol headers.

The maximum number of ‘slaves’ in a wireless configuration is identical to the wired solution

and is also four.

1.6.3 Alternative solutions

wireless

wireless

Figure 5 Dongle interface

As alternative solution for data exchange meter suppliers may install a combination of hard-

ware or software paired meter-dongle combinations according to the following rules:

� The dongle-master interface must be conforming to the wired M-Bus specifications in this

document.

� The wireless communication between the dongle and the meter may be vendor specific,

non-standard, with the following restrictions:

− Supplier should clearly show that the wireless communication is encrypted with

same security level as for wireless communication is required;

− Dongle and meter may be a hard coded pair, individual dongles and meters need not

be interchangeable.

Note that in this document the “Dongle Connected” M-Bus devices are regarded as wired M-

Bus devices.

1.7 Data Encryption Encryption is mandatory. EN-13757-3 section 5.10 defines DES encryption. The preferred

encryption however is AES (Federal Information Processing Standard (FIPS) 197, Advanced

Encryption Standard (AES)). The following shows the encryption mechanisms and the status.

of 36




Encryption Method Code

(header signature field)

Algorithm Key size Status

00xxh None (no encryption) - Mandatory, support required

02xxh DES 64 Optional1

03xxh DES 64 Optional1

04xxh AES-128 128 Mandatory, support required

Due to the mathematical nature of the AES-algorithm the encrypted length contained in the

low byte of the signature word shall be an integer multiple of 16 if the high byte signals AES-

Encryption. Unused bytes in the last 16-byte block shall be filled with appropriately structured

dummy data records to achieve the required record boundary at the end of the encrypted

data. One or several bytes containing the filler DIF = 2Fh are suggested to fill such gaps.

Filler bytes will be added after the last byte of the data block including any CRC bytes.

1.7.1 Signature Fields Two new CI field codes are defined (ref to table 1 in EN 13757-3):

CI Application

5Ah Master to Slave: 4 byte header followed by Variable data format response

5Bh Master to Slave: 12 byte header followed by Variable data format response

These CI field codes were defined in EN 13757-3 as “reserved”.

Structure of Data Header (CI=5Ah)

CI Access No. Status Signature

5Ah 01h 00h 02h 20h

Structure of Data Header (CI=5Bh)

CI Ident.nr Manufr. Version Device Type Access No. Status Signature

5Bh 12345678 3456 01h 0Eh 01h 00h 02h 20h

These CI field codes allow data from E-meter to M-Bus device to be encrypted.

1.7.2 Key Management Procedures Every M-Bus device is configured by the supplier with a default key. The supplier guarantees

that every meter has a unique key. This default key is exclusively used to decrypt any new

key that is received over the M-Bus.

The key is set by the CAS. The key is transferred to the Electricity meter over P3 and the

same key is, encrypted with the M-Bus devices default key, transferred to the Electricity me-

ter and from there it is transferred to the M-Bus device. The M-Bus device will decrypt this

1 No support required or guaranteed, maintained for compatibility with the standard.

of 36




new key using its default key and from then on will use the new received key. Until this new

key is received and decoded, all messages are sent unencrypted, and all commands, includ-

ing and not limited to synchronisation and valve commands, are ignored.

1.7.3 Block Chaining The CBC (Cipher Block Chaining) method is used. The Initialisation vector is either zero or is

defined as follows:

Encryption

Method Code

Block Chaining (ref EN13757-

3 section 5.10.5)

Initialisation Vector

00xxh - -

02xxh CBC, 00 00 00 00h

03xxh CBC,

Identification number from the fixed

data header (ref 1.10)

Manufacturing ID from the fixed data

header (ref 1.10)

Current Date in Type G (CP16) format.

04xxh CBC, 00 00 00 00 00 00 00 00h

1.7.4 Encrypted Data Deviating from EN13757-3 section 5.10.5 bullet d: The first data block of the encrypted part

of any telegram will be the 6 byte current meter clock time, format I, DIF 06h, VIF 6Dh, to en-

sure that the first block contains a changing element.

DIF 06H 6 Bytes integer

VIF 6DH Extended Date and time compound

data type I

xxH

xxH

xxH

xxH

xxH

Meter Clock Time

xxH

e.g. 02-09-2004 13:10:00,

Day of the week = 0

Week = 0

Time = valid

Daylight Saving, Leap Year as re-

quired.

Note that this field is not always included in the examples in this document!

1.8 Application Layer The application layer includes the data that is transmitted. For the M-Bus protocol the data

structures and data types of the application layer are described in EN 13757-3.

The equipment identifier shall be held at least in the bus slave meters and should be used in

every communication with the meter. The alarm status shall include all information necessary

to determine if meter intervention is required or whether the index reading is no longer valid.

An alarm indicating that a battery needs changing is required where applicable. The 8 bit

alarm frame may be divided into urgent alarms needing immediate action and alarm mes-

sages where the time span until action is less important. The position and meaning of the bits

of 36




may be meter specific. Therefore, it shall be necessary that the meaning of the bits is known

in the host system. It shall be possible that the meter specific mask, distinguishing between

urgent alarms and alarm messages, can be programmed by the host system into the electric-

ity meter.

Information about the meter or module is useful for auditing the system. Such data includes

manufacturer identifier, metered medium (gas, water, heat) and generation information for

the data stream. The access number in the data header will be maintained by the M-Bus de-

vice as specified in EN-13757-3 section 5.8.

Application layer data structures will be the same for wired and wireless systems, although

not all exchanges are implemented in the wireless systems (refer to 1.9.2 for exchanges in

wired systems and 1.9.3 for the exchanges in wireless systems).

1.9 M-Bus data exchange with meters

1.9.1 General This part of document describes the required M-Bus communication protocol between the

residential electricity meter, functioning as M-bus master, and M-Bus slave devices.

The installation part, such as the installation process of an external M-Bus device, removing

an external M-Bus device, exchanging a external M-Bus device, is described for both wired

and wireless devices in section 3.

1.9.2 Meter Value Transfer M-Bus devices can transfer either current, “real-time”, values or hourly values. Real Time

values are sent on request only. The hourly values are stored by the M-Bus device every

whole hour. Minimally one hourly value is stored.

The M-Bus transfer will use the Storage Number bit in the DIF block to signify the hourly

value.

1.9.3 Wired M-Bus communication

1.9.3.1 Send/Confirm Procedure The M-Bus master initiates communication by sending a short frame: SND_NKE

Field Hex Remark

Start Character 10H Short format

C-Field 40H SND_NKE

A-Field xxH Primary Address of M-Bus slave

Checksum xxH Sum of A and C fields, two least sig-

nificant Hex digits

Stop Character 16H Always 16H

The response of an M-Bus slave:

of 36




Field Hex Remark

Single character E5H The slave returns SCC (single control

character )

This message, SND_NKE can be used for detecting new devices on address zero (ref

3.2.1.1).

1.9.3.2 Information from M-Bus device If a reply is given in the format of E5H the M-Bus master can verify the type of device by re-

questing the device with a REQ_UD2. The slave shall answer with a RSP_UD (see 1.9.3.6

and 1.9.3.7).

1.9.3.3 Set Date and Time If the M-Bus device has an internal clock it should be synchronised by the master system.

Synchronisation is done:

� At every time change of the Bus Master (including daylight savings time related changes)

� At every restart of the communication (after communication breakdown, after M-bus

master breakdown, after M-bus device breakdown).

� Every day to ensure a maximum deviation below 60 seconds.

The maximum allowed clock deviation between E-meter and M-Bus device is 60 seconds. If

the M-Bus device receives a new system time through the Set Date and Time mechanism

then it verifies the difference between the new time and the old M-Bus Device system time. If

the difference is more than 60 seconds then a “time synch error” is set (ref 1.10.2). The M-

Bus device will always set its system time to the time received in the synchronisation mes-

sage. Note that this transaction is encrypted (ref 1.7.4).

SND_UD :

Field Hex Remark

Start Character 68H Start byte long telegram

L 09H Length

L 09H Length


C 53H (FCB=0)

A xxH Address base address

CI 5AH Data send (master to slave)



data type I

xxH

xxH

xxH

xxH

xxH

New time stamp

xxH

e.g. 02-09-2004 13:10:00,

Day of the week = 0

Week = 0

Time = valid


quired.

CS xxH Checksum

of 36




Field Hex Remark


1.9.3.4 Valve Control Command If the M-Bus device has a controllable valve then the Master (E-Meter) can send valve con-

trol commands.

SND_UD :

Field Hex Remark


L XxH Length

L xxH Length


C 53H (FCB=0)

A xxH Address base address

CI 5AH Data send (master to slave)

Access Nr xxH

Status 00H

04H Signature

xxH



data type I

00H

0AH

0DH

2DH

82H

09H

e.g. 02-09-2004 13:10:00,

Day of the week = 0

Week = 0

Time = valid


quired.

DIF 01H 1 digit binary

VIF FDH Extension

VIFE 1FH Remote control

Valve Command xxH 02: valve released, not open

01: valve opened,

00: valve closed

Note that this transaction is encrypted (ref 1.7.4).

Output to the valve will be according to the command. If the valve status is not equal to the

last received valve command, then the valve error bit (1.10.2) is set.

1.9.3.5 M-Bus procedure for data transmission During standard operation the M-Bus Master shall collect the consumption data by polling the

M-Bus by the available device addresses. Polling should be on an hourly basis or faster as

required. Data acquired from M-Bus devices includes:

� Billing reads, registered every hour at the full hour;

� On demand reads;

of 36




� Availability in the M-Bus Master and transfer from the M-Bus Master to other systems is

outside the scope of this companion standard.

1.9.3.6 Procedure for data request The M-Bus master initiates a request for data by sending a short frame: REQ_UD2

Field Hex Remark

Start Character 10H Short format

C-Field 5BH REQ_UD2

A-Field xxH Primary Address of M-Bus slave

Checksum xxH Sum of A and C fields, two least sig-

nificant Hex digits


1.9.3.7 Respond from the M-bus slave The slave shall respond with a long format frame: RSP_UD

Field Hex Remark

Start 68H Start byte Long Telegram

L 65H Length 101 Bytes

L 65H Length 101 Bytes

Start 68H Start byte

C 08H Sending of the required data

A XxH Primary address or 253 for secondary address

CI 72H Answer of variable length

78H

56H

34H

Ident.

Nr.

4

Byte

12H

Ident Number, e.g. 12345678 in BCD

XxH Manf. ID

XxH

e.g. Manufacturer ID

Version 33H SW-Version, e.g. 51

Medium 0CH Medium, e.g. Heat

Access Nr 01H Access Counter

Status 00H No Error (Any Application Error = 02)

00H Default 0

Fix

ed D

ata

Hea

der

12 B

yte

. R

efe

r to

1.1

0.1

Signature

00H Default 0

RS

P-U

D2

Data

Reco

rd (

with E

quip

m.

iden

tifier

an

d r

ea

din

g)

Variable Data Blocks (Records) (ref section 1.10)

CS XxH Checksum

Stop 16H Stop

Remarks

� Secondary addresses (A=253) need not be implemented

� 12 byte headers are mandatory in variable length data blocks (refer to 1.10.1)

1.9.3.8 Readout List Wired meters Meter specific data blocks are defined in section 1.10. The order in which data blocks are

inserted in an RSP-UD frame is not specified.

of 36




The following holds:

� Data Information Fields (DIF) and Value Information Fields (VIF) are mandatory and are

coded as in EN 13757-3.

� Extended Data Information Fields (DIFE) and Extended Value Information Fields (VIFE)

may be used to distinguish tariff based values or special units.

All types slave meter will send the following data if not specifically polled for a specific data

item:

� 1.10.1 Fixed Data Header

� 1.10.3 Equipment Identifier

� 1.10.7 Meter Configuration Data

Wired M-Bus devices transfer hourly values (Storage Number bit in DIF field is set), unless

specifically requested by the master to send actual readings.

� 1.10.4 Gas Meter specific data blocks:

o Corrected volume if this is in the meter configuration data

o Uncorrected volume if this is in the meter configuration data

o Valve status (1.10.5) if this is in the configuration data.

Valve devices (device type =x21) will sent gas valve specific data only (1.10.5).

Thermal meters (device type =x0D) will send the following data items if not specifically polled

for a specific data item:

• 1.10.6 Thermal (heat / cold) Meter specific data blocks:

o Actual meter reading heat if this is in the meter configuration data

o Actual meter reading cold if this is in the meter configuration data

o Actual meter reading volume if this is in the meter configuration data

Water meters (device type =x07) will send the following data items if not specifically polled


• 1.10.7 Water Meter specific data blocks: actual meter reading volume.

1.9.4 Wireless M-Bus communication

1.9.4.1 General notes with the Wireless M-Bus Communication The link layer of EN 60870-5-1 with the format class FT3 shall be used.

Note the following issues:

• The EN 13757-4 notes that the first octet of the first block is the L field. However the start

octets specified in the EN 60870-5 standard are included in this document. Please note

that this issue is still being discussed!

• The frame definitions outlined in IEC 870-5-2 are followed with the note that the Address

field is 8 octets in length and specifies the destination station address. There is no source

address included.

• The first block of the frame, referred to as block 0 in IEC 60870-5) will consist of:

o The Length field (ref IEC 6087-5-1)

o The C field (ref IEC 60870-5-2)

o The M-Bus device address (always), consisting of:

of 36




� Two octet manufacturer code (EN 13757-3)

� Four octet identification number (EN 13757-3)

� One octet version (EN 13757-3)

� One octet device type (EN 13757-3).

• Every block following the first will be 16 octets long, followed by a two octet CRC. The

very last block in the frame contains 1 to 16 octets of data as needed.

1.9.4.2 M-Bus procedure for data transmission The M-Bus device will send data according to the EN 13757-4 specifications with the follow-

ing fields defined:

� If the M-Bus device does not accept commands (valve or time synch) then every hour

device data will be transferred using T1 mode, C=44H (ref 1.9.3.2).

� If the M-Bus device can process commands (e.g. synchronisation commands or valve

commands), then every hour device data will be transferred using T2 “access demand”

message, C=48H The M-Bus device will then wait for an acknowledge (C=00H ) on this

request. If the acknowledge is received then a link is established and all C-fields values

of EN 60870-5-2 may be used.

� CI – Control Information: In all data exchanges CI=72H will be used (EN 13757-3 Appli-

cation Layer with full header) for compatibility with the wired M-Bus. 12 byte data header

is mandatory.

� The M-Bus device will initiate transfer every hour. The time is random to lower the

chance of two M-Bus devices transmitting at the same time.

1.9.4.3 Device Data Transfer Gas meters will transfer hourly Gas Meter Specific Data Blocks (1.10.4), every hour. These

values are time stamped. Following the access demand procedure the E-Meter may respond

with:

� A Valve control command

� A time synchronisation command.

Valve devices will transfer hourly Valve Status Blocks (1.10.4). These values are not time

stamped, the values are registered at the full hour. Following the access demand procedure

the E-Meter may respond with:

� A Valve control command


Thermal meters will transfer hourly Thermal Meter Specific Data Blocks (1.10.6). These val-

ues are not time stamped, the values are registered at the full hour. Following the access

demand procedure the E-Meter may respond with:


Water meters will transfer hourly water Meter Specific Data Blocks (1.10.7). These values

are not time stamped, these values are registered at the full hour. Following the access de-

mand procedure the E-Meter may respond with:


of 36




1.9.4.4 Set Date and Time Note that RF devices can only be synchronised after the M-Bus device initiates an access

demand procedure. RF communication does not support the master-slave mechanism.

If the M-Bus device has an internal clock it should be synchronised by the E-meter. Synchro-

nisation is done:

� At every time change of the Bus Master (including daylight savings time related changes)

� At every restart of the communication (after communication breakdown, after M-bus host

breakdown, after M-bus device breakdown).

� Every day to ensure a maximum deviation below 60 seconds.

The maximum allowed clock deviation between E-meter and M-Bus device is 60 seconds. If

the M-Bus device receives a new system time through the Set Date and Time mechanism

then it verifies the difference between the new time and the old M-Bus Device system time. If

the difference is more than 60 seconds then a “time synch error” is set (ref 1.10.1). The me-

ter will always set its system time to the time received in the synchronisation message.

SND_UD :

Field Hex Remark

Start Character 05H Start byte 1


L 13H Length

C 53H Control Field

AxH M : Manufacturer ID

xxH

01H Device specific

23H

45H

Identification number

67H

Version Number XXH Manufacturers version nr

A : Address Field

(ref EN13757-4 sec-

tion 5.5.3.1)

Device Type 03H Gas meter (EXAMPLE)

CRC

XXH CRC Checksum Header

CI 51H Data send (master to slave)



data type I

New Time Stamp xxH

xxH

xxH

xxH

xxH

xxH

e.g. 02-09-2004 13:10:00,

Day of the week = 0

Week = 0

Time = valid


quired.

XXH CS

XXH

Checksum

of 36




1.9.4.5 Valve Control Command If the M-Bus device has a controllable valve then following the access demand procedure the

E-Meter can send valve control commands. Note that separate valve devices have device

type 21H (valve device), not 03H (gas device).

SND_UD :

Field Hex Remark



L xxH Length

C 53H Control Field

AxH M

xxH

M : Manufacturer ID

01H

23H

45H


67H

Device specific



XXH CRC

CRC Checksum Header



VIF 6DH Extended Date and time compound data type I

xxH

xxH

xxH

xxH

xxH

xxH

e.g. 02-09-2004 13:10:00,

Day of the week = 0

Week = 0

Time = valid

Daylight Saving, Leap Year as required.


VIF FDH Extension

VIFE 1FH Remote control

xxH xxH 02: valve released, not open

01: valve opened,

00: valve closed

CRC

XXH CRC Checksum

Output to the valve will be according to the command. The M-Bus device will report a status

change at the next data transfer on the whole hour: if the valve status is not equal to the last

received valve command, then the valve error bit (1.10.1) is set.

1.9.4.6 Readout List Wireless meters Meter specific data blocks are defined in section 1.10. The order in which data blocks are

inserted in an RSP-UD frame is not specified.

of 36




The following holds:

� Data Information Fields (DIF) and Value Information Fields (VIF) are mandatory and are

coded as in EN 13757-3.

� Extended Data Information Fields (DIFE) and Extended Value Information Fields (VIFE)

may be used to distinguish tariff based values or special units.

All types meter will send the following data if not specifically polled for a specific data item:

� 1.10.1 Fixed Data Header

� 1.10.3 Equipment Identifier

� 1.10.8 Meter Configuration Data

Wireless M-Bus devices only transfer hourly values (Storage Number bit in DIF field is set).

In encrypted transmissions, the first item in the user data block must be the time stamp. This

time stamp will then hold the time of recording the stored hourly value. Note that no more

than one stored value is required.

Gas meters (device type = x03) will send the following data items if not specifically polled for

a specific data item:

� 1.10.4 Gas Meter specific data blocks:

o Corrected volume if this is in the meter configuration data

o Uncorrected volume if this is in the meter configuration data

o Valve status (1.10.5) if this is in the configuration data.

Valve devices (device type =x21) will sent gas valve specific data only (1.10.5).

Thermal meters (device type =x0D) will send the following data items if not specifically polled


• 1.10.6 Thermal (heat / cold) Meter specific data blocks:

o Actual meter reading heat if this is in the meter configuration data

o Actual meter reading cold if this is in the meter configuration data

o Actual meter reading volume if this is in the meter configuration data

Water meters (device type =x07) will send the following data items if not specifically polled


• 1.10.7 Water Meter specific data blocks: actual meter reading volume.

1.10 M-Bus communication Variable Data Blocks

1.10.1 Fixed Data Header 78H

56H

34H

Ident.

Nr.

4

Byte

12H

Ident Number, e.g. 12345678 in BCD

XxH Manf. ID

XxH

e.g. Manufacturer ID

Version 33H SW-Version, e.g. 51

Medium 0CH Device type, refer to EN 13757 for codes

Access Nr 01H Access Counter

Status 00H Error status, refer to 1.10.2

Fix

ed D

ata

Heed

er

12 B

yte

Signature 00H Default 0

of 36




00H Default 0

Refer to EN 13757-3 for the definitions of fields.

1.10.2 Error Status codes The Status code holds error information.

Bit Meaning with Bit set Significance with Bit not set

0,1 Application errors, see EN 13757-3 Application errors, see EN 13757-3

2 Power low (Battery replacement expected) Not power low

3 Permanent error No permanent error

4 Temporary error No temporary error

5 Clock Synchronisation more than 60 sec-

onds deviation No significant clock deviation.

6 Fraud attempt registered No fraud attempt registered

7 Valve alarm No valve alarm

Error bits 6, 7 are medium specific bits.

1.10.3 Equipment Identifier DIF 0DH Variable length ASCII

VIF 78H Equipment identifier

LVAR 11H Length 17

34H, 33H, 32H, 31H

39H, 38H, 37H

36H, 35H, 34H

33H, 32H, 31H

44H, 43H, 42H, 41H

Equipment identifier 17 ASCII, e.g.

ABCD1234567891234

All meters are uniquely identified by a 17 ASCII character Equipment identifier, which is de-

fined in the Tender document.

1.10.4 Gas Meter specific data blocks Actual Meter Reading temperature corrected Volume (“real time” values shown).

DIF 0CH 8 digit BCD

VIF 13H Multiplier 0,001; unit m³

43H

27H

41H

Volu

me

31H

Actual temperature corrected reading, e.g.

31412.743 m³

Actual Meter Reading raw, uncorrected, Volume

DIF 0CH 8 digit BCD


Vol-

um

e

VIFE 3AH VIF contains uncorrected units instead of corrected.

of 36




43H

27H

41H

31H

Actual raw reading, e.g. 31412.743 m³

Note Either the temperature corrected value or the raw, uncorrected value is transferred.

If a gas valve is present and if the status of this valve is monitored by the gas meter then the

gas valve specific data blocks (1.10.5) are sent as well.

1.10.5 Gas valve specific data blocks Valve status

DIF 89H 2 digit BCD

DIFE 40H Valve (new definition)

VIF FDH Valve (new definition)

VIFE 1A Digital status

Valv

e S

tatu

s

xxH 02: valve released, not open

01: valve opened,

00: valve closed

The valve status may be sent as control command from the e-meter / reader device to the

gas meter with CI=51H.

1.10.6 Thermal (heat / cold) Meter specific data blocks Actual meter reading energy Heat (“real time” values shown).

DIF 0CH 8 digit BCD

VIF 0DH Multiplier 0,01 ; unit GJ

27H Actual reading, e.g. 03141,27 GJ

41H

31H

En

erg

y H

EA

T

00H

Actual meter reading energy Cold

DIF 4CH 8 digit BCD

VIF 0DH Multiplier 0,01 ; unit GJ

27H Actual reading, e.g. 03141,27 GJ

41H

31H

Energ

y C

OLD

00H

Actual Meter Reading Volume

DIF 0CH 8 digit BCD


74H Actual reading, e.g. 02440,474m³

04H

44H

Volu

me

02H

of 36




1.10.7 Water Meter specific data blocks Actual Meter Reading Volume(“real time” values shown).

DIF 0CH 8 digit BCD


74H

12H

14H

Vo

lum

e

03H

Actual reading, e.g. 031412.74 m³

1.10.8 Meter Configuration Data This data item holds a single block showing which measurements are implemented. Note

that the meter type is defined in the data header (ref Device Type in 1.10.1)


VIF FDH Extension

VIFE 67H Note this was marked as “Special

Supplier Information” in EN 13757-3

xxH xxH Mask:

01H : Clock device implemented

02H : Switching device implemented

04H : Meter type Gas only: corrected

volume

1.10.9 Location Information This is the location of the connection. This value can be set and read through the P2 inter-

face. It is a 10 character ASCII string.

DIF 0DH Variable length ASCII

VIF FDH

VIFE 10H Customer Location

LVAR 0AH Length 10

34H, 33H, 32H, 31H

39H, 38H, 37H

36H, 35H, 34H

Location

1.10.10 Function Location This is the EAN code for the connection. This value can be set and read through the P2 inter-

face. It is an 18 character ASCII string.


VIF FDH

VIFE 11H Customer Location

LVAR 12H Length 18

34H, 33H, 32H, 31H

39H, 38H, 37H

36H, 35H, 34H

34H, 33H, 32H, 31H

34H, 33H, 32H, 31H

Location

of 36




2 POWER SUPPLY

2.1 Maximum current The bus interface - that is, the wired interface between the slave and the bus system – can

take the power it requires from the bus system. The interface of the slave shall be fed from

the bus. The M-Bus standard defines M-Bus loads of up to 1,5 mA whereby any external

device can use up to 4 M-Bus loads. The M-Bus master shall be capable of supplying at

least 16 M-Bus loads (4 devices of up to 4 M-Bus loads each). Note also the physical layer

specifications in EN 13757-2 section 4.

Wireless devices have their own power source.

2.2 Power outage During the expected lifetime a power outage could occur. M-Bus devices should always

measure and register the usage during a power outage. The status of a valve may not be

changed caused by the power outage. All configuration data (including M-Bus device ad-

dresses and encryption keys) and all process data (including any valve commands) are to be

stored during long power outages. Wireless devices need not necessarily detect power fail-

ures of the electricity meter and the connected communication device. The meter reading

that is registered, the meter reading that is sent to the electricity meter and the meter reading

on the meter’s display should be consistent at all times. Any registered interval data may be

lost during power outage.

of 36




3 INSTALLATION PROCEDURES

3.1 General installation procedures During installation the M-Bus addresses will of M-Bus devices will be registered in the M-Bus

master. Note that device addresses must be set to zero before installation.

There must be a facility to set M-Bus devices (wired or wireless meters) to installation mode.

This action must reset the device address as well. The resetting of the device address is dif-

ferent for wired and wireless meters. Resetting the device address is equivalent to unbinding

the M-Bus device.

There must be a facility to set electricity meters to installation mode. When in installation

mode, the wired e-meter scans for physically connected M-Bus devices, the wireless e-meter

accepts and processes installation mode requests from M-Bus devices.

After the M-Bus devices are registered in the Electricity Meter (in wired configurations the M-

Bus Master, and in wireless configurations the M-Bus slave), regular communications will

begin as discussed in sections 1.9.3 and 1.9.4

3.1.1 Wired M-Bus device reset of the device address When set to installation mode, the device address is set to zero. The encryption key is

erased and any received encrypted message is decrypted using the device’s default encryp-

tion key.

3.1.2 Wireless M-Bus device reset of the device address When set to installation mode, the most significant bit of the manufacturer ID (M) is set to

zero. The encryption key is erased and any received encrypted message is decrypted using

the device’s default encryption key.

3.2 Wired configurations

3.2.1 Scan for new M-Bus devices The E-Meter will maintain a list of device addresses, in the range 1 to 250, of all devices it is

connected to, through a wired connection. Note that according to 2.1 only four M-Bus de-

vices can be connected, either wired or wireless. While in installation mode, the E-meter will

continuously scan for devices on the wired M-Bus. All responding devices will be registered

in the list. This scan will be suspended for any other data transfer. The scan and the installa-

tion mode will be terminated if four devices are registered or after one hour. The E-meter will

support two methods to discover newly installed M-Bus devices.

3.2.1.1 Poll for devices with address 0 Address 0 is reserved for unconfigured M-Bus devices. Each unconfigured M-Bus device

shall accept and answer all communication to this address (ref EN 13757-2 section 5.7.5 and

this companion standard section 1.9.3.1).

of 36




The E-meter will select an unused device address and set the new M-Bus device’s address

to that using the procedure in 3.2.2.

Following this procedure the e-meter will poll for the device specific data and send the follow-

ing:

� A synchronisation command as in 1.9.3.3;

� (optionally) a valve command to set the valve in the latest known status as in 1.9.2.4.

3.2.1.2 Poll for devices with unregistered address The e-meter will scan once per minute all unused addresses following the procedure outlined

in EN 13757-3 section 11.5. Note that there is only one baud rate allowed and that secon-

dary addresses are not used. Following this procedure the e-meter will poll for the device

specific data and send the following:

� A synchronisation command as in 1.9.3.3;

� (optionally) a valve command to set the valve in the latest known status as in 1.9.3.4.

3.2.2 Set new address To change the primary address from zero to an open address the E-meter (Master) has to

write address data to the M-Bus device.

SND_UD :

Field Hex Remark


L 06H Length

L 06H Length


C 53H Control Field

A 00H Address base address (00)


DIF 01H Data identifier

VIF 7AH Address data

A xxH Address field new

CS 25H Checksum


The M-Bus device will respond to communications to that address.

This command will not be encrypted.

At any stage after setting the new M-Bus device address, the Bus Master may send Location

Information (ref 1.10.9) and / or Function Location parameters (ref 1.10.10).

3.3 Wireless configurations

3.3.1 Wireless device address Wireless M-Bus devices must have a unique device address in the range of the M-Bus

transmission. Note the address definition in EN 13757-4 section 5.5.3.5. After power up the

M-Bus device will start the first transmission with this address as sending device.

of 36




If the most significant bit of the manufacturer ID (M) is 0 (zero) then the E-meter may re-

spond with an access demand ack, followed by, in this order:

� A set new address procedure, to an unused address, as in 3.3.2.3

� A synchronisation command as in 1.9.4.4(with the new address)

� (optionally) a valve command to set the valve in the latest known status as in 1.9.4.5

If the most significant bit of the manufacturer ID (M) is non-zero then the E-meter will add the

device address to the list of configured devices and send the following commands:

� A synchronisation command as in 1.9.4.4

� (optionally) a valve command to set the valve in the latest known status as in 1.9.4.5

Note that according to 2.1 only four M-Bus devices can be connected, either wired or wire-

less.

3.3.2 M-Bus Device Binding Unlike the metered configuration, the wireless M-Bus devices must select a partner device at

installation time. The following procedure should be followed.

3.3.2.1 M-Bus Device State M-Bus devices can be in one of three states:

• Long term storage: the wireless m-bus is inactive

• Installation mode: User intervention can set a M-Bus device from storage mode to instal-

lation mode. In installation mode an M-Bus device will try to install itself for a defined pe-

riod and if it fails, it will fall back to storage mode. In installation mode an M-Bus device

will transmit requests to an M-Bus system that will connect to it and provide an M-Bus

address and an Encryption Key.

• Installed mode: after an M-Bus device receives an M-Bus Address and an encryption key

it will function as described in this document.

3.3.2.2 M-Bus Binding Procedure The binding procedure is shown in Figure 6 Wireless Binding Procedure

of 36




Secondary Station M-Bus Device

T2_access_demand_install_mode (LA1,ProdNr)

T2_access_demand_ack (LA1)


Visual Feedback

Input PulseInstaller

Requests Key from BO (ProdNr)

T2_access Demand

T2_access_demand_ack (LA)

T2_set_AES_Key (LA)

T2_ack (LA)

T2_set_soft_address(LA)

T2_ack (LA)

BO Returns Encrypted Key

BO Returns Key


Back Office (CAS)

Set to Install Mode

M-Bus device accepts

commands from here on

M-Bus device sends data

from here on

Figure 6 Wireless Binding Procedure

The various steps are in detail:

1. The installer instructs the M-Bus device to go into install mode

2. The M-Bus device sends a T2_access_demand_install_mode containing its address

and its equipment identifier (ref 1.10.3).

3. The Electricity Meter (referred to as Secondary Station), displays the equipment iden-

tifier of all M-Bus devices that send out a T2_access_demand_install_mode. The

Electricity meter must be in installation mode.

4. The M-Bus Device sends out T2_access_demand_Install_mode messages every

minute for a period of 60 minutes. If after 60 minutes no secondary device responded

yet then the M-Bus Device will continue sending T2_access_demand_Install_mode

messages every hour.

5. The installer selects the correct Equipment identifier on the Secondary Station device

and confirms binding with the M-Bus device. This selection process is done on the

Secondary Station and can as required be done in one of the following ways:

of 36




a. Selecting the appropriate equipment identifier from a list of equipment identifi-

ers from meters that are sending out T2_access_demand_install_mode mes-

sages on the display on the Secondary Station

b. Entering the appropriate equipment identifier on a PDA and transferring this

number from the PDA into the Secondary Station (entering the number can be

done by scanning a label on the meter that is being installed)

c. Selecting the appropriate equipment identifier on the PDA after receiving a list

of meters that are sending out T2_access_demand_install_mode messages

from the Secondary Station into the PDA and feeding the selected number

back into the Secondary Station

d. The Secondary Station receives the appropriate equipment identifier from the

CAS at any one time before or after the installation. There is no time limit on

this action.

There is no preferred way to introduce the appropriate equipment identifier into the

secondary device. This depends on the possibilities and capabilities of the installation

staff.

6. Following a T2_access_demand_Install_mode message, the Secondary Station De-

vice replies with a T2_access_demand_ack. From this moment on the M-Bus device

will send regular hourly data (ref 1.9.4.2), by sending Access Demand (C=48H) mes-

sages including meter reading data and/or valve status data. These meter readings

are not encrypted yet, since there is no encryption key defined yet. The M-Bus device

must send T2 messages until the encryption key exchange is completed (step 8

below).

7. The Secondary Station device may set a new address as in 3.3.2.3. Note that this is

optional and only permitted if the most significant bit of the address is zero.

8. Upon receiving a set of keys from the CAS, the Secondary Station Device may send

the encrypted key to the M-Bus device as in section 1.7.2 and 4. There is no timing

restriction on the exchange of encryption keys.

At any stage after the binding the Secondary Station Device may send Location Information

(ref 1.10.9) and / or Function Location parameters (ref 1.10.10).

T2_access_demand_install_mode block:

Field Hex Remark



L xxH Length

C 06H Control Field (ref EN13757-4 s 5.5.3.3)

0xH M

xxH

M : Manufacturer ID

01H

23H

45H


67H

Device specific


Devic

e A

ddre

ss


CRC XXH CRC Checksum Header

of 36




Field Hex Remark

XXH

CI 78H Data send


VIF 78H Equipment identifier

LVAR 11h 17 bytes

Equipment identifier 34H, 33H, 32H, 31H

39H, 38H, 37H, 36H

Data

Blo

ck

35H, 34H, 33H, 32H

17 ASCII, e.g.

ABCD1234567891234

CRC first user data block XXH, XXH

31H, 44H, 43H, 42H

Data

Blo

ck

41H

Remainder of the 17 ASCII

CRC second user data block XXH CRC Checksum

Note this block is not encrypted.

3.3.2.3 Set new address To change the primary address from zero to an open address the E-meter (Master) has to

write address data to the M-Bus device.

SND_UD :

Field Hex Remark



L 15H Length

C 53H Control Field

0xH M

xxH

M : Manufacturer ID

01H

23H

45H


67H

Device specific


Old

De

vic

e A

d-

dre

ss


XXH

CRC

XXH

CRC Checksum Header


DIF 07H Data identifier (8 byte device address)

VIF 7AH Address data

AxH

xxH

Manufacturer ID

23H

45H

67H

89H

XXH

Da

ta B

lock

new device address (8

bytes, including manufac-

turer ID to reset the most

significant bit)

03H

New device address: ID number, ver-

sion number and device type

of 36




Field Hex Remark

XXH CRC

CRC Checksum

The M-Bus device will respond to communications to that address.

3.4 Replacing an M-Bus device Procedures for removing meters are presented in the DSMR Main document. Before remov-

ing an M-Bus device, its operational parameters must be read and stored.

Before installing a replacement M-Bus device, the organisation installing it must ensure that

the metering system writes all operational parameters to the new installed meter.

of 36




4 ENCRYPTION KEY MANAGEMENT PROCEDURES

4.1 M-Bus devices default encryption keys

The supplier ensures that every M-Bus device has an unique default encryption key. This

default encryption key is registered with the device’s Equipment Identifier (ref 1.10.3) but is

not logically related to it.

This default key is exclusively used to decrypt a new key sent through the P2 interface. This

new key will not replace the default key. The new key is used to encrypt / decrypt all mes-

sages received over the P2 interface.

Until a new key is received, all communication over the P2 interface will be unencrypted, and

the M-Bus device will accept no commands (e.g. synchronisation or valve commands).

4.2 Encryption key exchange procedures

After installation the M-Bus device sends meter data as defined in 1.9.3.5 and 1.9.4.2. These

transmissions will be unencrypted and will contain the M-Bus device’s Equipment Identifier

(ref 1.10.3). The electricity meter will transfer this Equipment identifier to the CAS requesting

an encryption key for the device.

The CAS will transfer a new key for the M-Bus device through the (encrypted) P3 channel to

the Electricity meter.

This new key is transferred through P3 as plain octet string, for use in the electricity meter,

and as octet string encrypted by the M-Bus device’s default key.

The encrypted string is transferred over the P2 interface, unencrypted, signature=00 00h, to

the M-Bus device as a series of 64 bit integers, least significant byte first, VIF= FDh,

VIFE=19h (formerly reserved VIFE).

of 36




The M-Bus device will concatenate the 64 bit integers, and decrypt the octet string using its

default key and will use the resulting 128 bit key in encryption / decryption of further commu-

nications.

of 36




5 P2 – P3 MAPPING

DIF DIFE VIF VIFE Value Section P3 reference

Firmware Version in fixed

header block of RSP_UD

1.10.1 0-1:96.1.1.255 - Device ID 2 Set by manufacturer, read-

only

01h 01h 1Fh Valve Control Command 1.9.3.4

1.9.4.5

0-x:24.4.0.255 Output state

0Dh 78h Equipment identifier 1.10.3 P3 section 7.2

0-x:96.1.0.255 (x=channel number (1..4))

Set by manufacturer, read-

only . This is a 17 byte field.

Location Information 1.10.9 0-x:96.1.1.255 (x=channel number (1..4)) Set during installation

Function Location 1.10.10 0-x:96.1.2.255 (x=channel number (1..4)) Set during installation

Disconnectable flag Set during operation at any

time

0Ch 13h Gas meter reading 1.10.4 0-x:24.3.0.255 (x=channel number (1..4)) Capture_Objects

0Ch 93h 3Ah Gas meter reading, uncor-

rected

1.10.4 0-x:24.3.0.255 (x=channel number (1..4)) Capture_Objects

Note that there should be

clear distinction between

corrected and uncorrected

volume

89h 40h FDh 1Ah Digital status valve 1.10.4

0Ch 0Dh Heat Meter Reading 1.10.6 0-x:24.3.0.255 (x=channel number (1..4)) Capture_Objects

4Ch 0Dh Cold meter reading 0-x:24.3.0.255 (x=channel number (1..4)) Capture_Objects

0Ch 13h Heat meter reading Vol-

ume

0Ch 14h Water meter reading 1.10.7 0-x:24.3.0.255 (x=channel number (1..4)) Capture_Objects

01h FDh 67h Meter Configuration Mask 1.10.8 0-x:24.3.0.255 (x=channel number (1..4)) Capture_Objects

01h 7Ah M-Bus Device Address 3.2.2

3.3.1

0-x:24.1.0.255 primary_address

FDh 19h Encrypted encryption key 4

of 36




Header Data (ref 1.10.1)

M-Bus Field name P3 reference

Ident Number 0-x:24.1.0.255 - identification_number

Manufacturing ID 0-x:24.1.0.255 – manufacturer_id

Version 0-x:24.1.0.255 – version

Medium 0-x:24.1.0.255 – device_type

Access Number 0-x:24.1.0.255 – access_number

Status – alarm flags 0-x:24.1.0.255 – status

Signature – Encryption method None

of 36




6 DOCUMENT LIST

Following table shows the complete set of documents that build up the Dutch Smart Meter

Requirements, of which this Companion standard P2 document is a part of.

Document name postfix Description

main

The main document of the Dutch Smart Meter Requirements,

containing all definitions and most of the use cases and re-

quirements

tender

Tender document, containing additional general requirements,

use cases and performance requirements

P1 Companion standard P1



P2 Companion Standard - search read.pudn.comread.pudn.com/downloads145/doc/633047/DSMR v2.2...

Documents

Transcript of P2 Companion Standard - search read.pudn.comread.pudn.com/downloads145/doc/633047/DSMR v2.2...