286 - P3Dutch Smart Meter v2.1 Final P3

P3 Companion Standard
Dutch Smart Meter specification and tender dossier
By order of: Reference: Date: Version: Status:
EnergieNed B101 February 4th, 2008 2.1 final After consultation / technical dialogue
File name: Author: Version:
Dutch Smart Meter Requirements v2.1 final P3.doc Date: 04-02-2008 KEMA Config. ID: B101 2.1 final Project: Functional and technical specifications Smart Meters
Page 2 of 68
Change Summary
Revision Created / Modified H. Spelt H. Spelt H.Spelt Date Approved Date June 2007 Comment
1.00 1.20 2.0 first draft 2.0 second draft
28-June-07 12-Sep-07 27-Nov-07
WG04 WG04 WG04
Original release NTA first draft Table of Contents modified + security and protocol stacks added; introduction prepared Excel file integrated, new classes added in appendix, review comments DLMS meeting 4 December added, integrated Event and error handling document Update of Disconnector class (Appendix A3); New OBIS codes added and Class ids. (excel 13/12/07); Review comments WG04 members added; Security part added; update event and error handling v0.3 (table event codes and error codes updated); Latest excel file object mapping dated 20/12/07 consistency check with CS P3 done Page 46 highlight reference added OBIS codes changed for Limiter, Disconnect control and control log Setup objects appended with attributes and OBIS codes Selection of security suite 7 mentioned References added/modified Yellow markings updated/removed/added Push/pull clarification added Footnote 3 and 4 added Rate 1 and 2 mapped on Low and Normal Tariff added as extra information PLC objects added in Appendix B
H.Spelt S. Ermens
13-Dec-07
WG04
2.0 final draft
H. Spelt S. Ermens
21-Dec-07
WG04
2.1 final H. Spelt 4-Feb-07 WG04 -
Page 3 of 68
Distribution information
Version 1.0 1.20 2.0 first draft 2.0 second draft 2.0 final draft 2.1 final Addressees Members WG4 Members WG4 Members WG4 Manufacturers Members WG4 Manufacturers Members WG4 Manufacturers Members WG4 Manufacturers Grid Companies Remarks For Review For Review For Review For Review For Review For Review
Issue list
Version 2.0 first draft 2.0 draft second Activity Almost all chapters, except introduction, needs to be filled in with information from object mapping Excel file and some extra information - missing OBIS codes and Class ID to be added when standardized; - update event & error handling part with new information - security part to be added - Final version of Event & error handling is not yet received - still some comments and questions of WG04 not yet answered and integrated - some questions/issues added in document (highlighted in yellow, red) - Update event and alarm handling chapter (including Alarm codes and filters) - some comments and questions of WG04 are not yet answered and integrated - still some questions highlighted in yellow colour. - description about the use of the associations needs to be added for the Data Concentrator - GPRS way of connection handling/setup (like push mechanism) not yet added - P2 to P3 mapping related to identifiers Gas/M-bus device (P2) and E-meter (P3) is missing
2.0 final
2.1 final
Page 4 of 68
CONTENTS
1 1.1 1.2 1.3 1.4 2 3 3.1 3.2 4 4.1 4.2 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 6 6.1 6.2 6.3 6.4 6.5 7 7.1 7.2 7.3 7.4 7.5 7.6 Introduction ............................................................................................................................ 6 Scope..................................................................................................................................... 6 System architecture............................................................................................................... 7 Normative references ............................................................................................................ 7 Document list......................................................................................................................... 9 Logical devices and associations, M-Bus modelling (general concept) .............................. 10 Communication profiles and services, security ................................................................... 11 Communication profiles ....................................................................................................... 13 COSEM Security ................................................................................................................. 16 Overview of Object Model.................................................................................................... 19 Profile structure Dutch smart meter..................................................................................... 19 Event and error handling ..................................................................................................... 20 Abstract objects ................................................................................................................... 28 SAP assignment, Association LN,COSEM logical device name......................................... 28 Identification numbers ......................................................................................................... 28 Clock.................................................................................................................................... 29 Activity Calendar and Special Days Table .......................................................................... 30 Billing periods and profiles .................................................................................................. 30 Error and Alarm Handling (error register, alarm register).................................................... 31 Event Handling (events and logs) ....................................................................................... 32 Fraud detection (event log) ................................................................................................. 32 Power Failure Event Log (counters and thresholds) ........................................................... 32 Disconnector (Control and Log, scheduler)......................................................................... 33 Limiter .................................................................................................................................. 35 P1 objects (messages, readout list) .................................................................................... 35 Electricity related objects ..................................................................................................... 36 Identification numbers (i.e. firmware version) ..................................................................... 36 E registers (+A, -A, all rate registers) .................................................................................. 36 E profiles (15', daily) ............................................................................................................ 37 Instantaneous Values (voltage, current, power).................................................................. 38 Power Quality (Voltage sags and swells) ............................................................................ 40 M-bus related objects .......................................................................................................... 42 M Bus Master Setup ............................................................................................................ 42 Identification numbers ......................................................................................................... 42 Registers ............................................................................................................................. 43 Profiles (hourly) ................................................................................................................... 43 Event Log (Class id = 7) ...................................................................................................... 44 Disconnector (Control and Log) .......................................................................................... 44 Specification of new DLMS classes ................................................................... 46
Appendix A: A.1 A.2 A.3
M-Bus Master Setup Interface Class (class_id:72) ............................................................. 46 Limiter Interface Class (class_id:71) ................................................................................... 49 Disconnect control (class_id:70) ......................................................................................... 51 PLC setup classes ............................................................................................. 55
Appendix B: B.1 B.2 B.3 B.4 B.5
S-FSK Phy&MAC setup (class_id: 50) ................................................................................ 55 S-FSK Active initiator (class_id: 51) .................................................................................... 58 S-FSK MAC synchronisation timeouts (class_id: 52).......................................................... 59 S-FSK MAC counters (class_id: 53).................................................................................... 61 S-FSK IEC 61334-4-32 LLC setup (class_id: 55) ............................................................... 63
Page 5 of 68 B.6 B.7 B.8 B.9 S-FSK Reporting system list (class_id: 56) ......................................................................... 64 ISO/IEC 8802-2 LLC Type 1 setup (class_id: 57) ............................................................... 65 ISO/IEC 8802-2 LLC Type 2 setup (class_id: 58) ............................................................... 66 ISO/IEC 8802-2 LLC Type 3 setup (class_id: 59) ............................................................... 67
Page 6 of 68
1 1.1
INTRODUCTION Scope
This document provides a companion standard for an Automatic Meter Reading (AMR) system for electricity thermal, (heat & cold), gas and 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 P3 interface for Electricity meters.
Independent Services Provider
P0 P1
Other Services Module
Metering system
P3 CAS
P4
Supplier
P2
Grid company
W/T
Figure 1.1: Meter interfaces overview The goal of this companion standard is to reach an open, standardized protocol implementation based on DLMS/COSEM. This companion standard is the result of a combined effort of the major Dutch grid operators and different manufactures who defined the necessary DLMS/COSEM object mapping.
Page 7 of 68
1.2
System architecture
The communication interface P3 and P3.1 (see figure 1.2) is based on the DLMS/COSEM standard. References to the DLMS/COSEM standard are included in section 1.3. This companion standard P3 only includes deviations, clarifications or additions to the standard as defined in the relevant standard documents. P3.2 and P0 interface (see also figure 1.2) are not part of this companion standard. The P1 and P2 interfaces are described in separate companion standards.
OSM
P1 P3.2 CAS DC
P3.1 PLC P3 GPRS, Ethernet
Electricity meter
P2
Gas meter
P0
PDA Laptop
Figure 1.2: DLMS/COSEM infrastructure P3
1.3
Normative references
The following standards are referred to in this companion standard. For undated references the latest edition applies.
Ref No 1 2 3 4 Document DLMS UA 1000-1 ed.8, 20071 DLMS UA 1000-2 ed.6, 20072 DLMS UA 1001-1 ed.3, 2007 DLMS UA 1002: ed.1, 2003 Description Blue book, COSEM Identification System and Interface Classes Green book, DLMS/COSEM Architecture and Protocols Yellow book, DLMS/COSEM Conformance Testing Process White book, COSEM Glossary of Terms
1 A new version (edition 9) of the Blue book is in development. The new version of the blue book will describe the new Classes and OBIS codes mentioned in this Companion standard and gives also the description of the new encryption and authentication mechanism. 2
A newer version (edition 7) of the Green book will have the definition of PLC Communication Profile and also the description of the new encryption and authentication mechanism.
Page 8 of 68 Ref No 5 Document IEC 61334-4-32 Description Distribution automation using distribution line carrier systems Part 4: Data communication protocols Section 32: Data link layer Logical link control (LLC) Distribution automation using distribution line carrier systems Part 4-511: Data communication protocols System management : CIASE protocol Distribution automation using distribution line carrier systems Part 4-512: Data communication protocols System management using profile 61334-5-1 Management Information Bases (MIB) Distribution automation using distribution line carrier systems Part 5-1: Lower layer profiles The spread frequency shift keying (S-FSK) profile Electricity metering Data exchange for meter reading, tariff and load control Part 21: Direct local data exchange
IEC 61334-4-511
IEC 61334-4-512
IEC 61334-5-1
IEC 62056-21 Ed 1.0:2002
10
Electricity metering Data exchange for meter reading, tariff and IEC 62056-42 Ed.1.0:2002 load control Part 42: Physical layer services and procedures for connection-oriented asynchronous data exchange IEC 62056-46 Ed.1.1:2007 IEC 62056-47 Ed 1.0:2006 IEC 62056-53 Ed 2.0:2006 IEC 62056-61 Ed 2.0:2006 IEC 62056-62 Ed 2.0:2006 NTA 8130 NL:2007 Electricity metering Data exchange for meter reading, tariff and load control Part 46: Data link layer using HDLC protocol Electricity metering Data exchange for meter reading, tariff and load control Part 47: COSEM transport layer for IP networks Electricity metering Data exchange for meter reading, tariff and load control Part 53: COSEM Application layer Electricity metering Data exchange for meter reading, tariff and load control Part 61: OBIS Object identification system Electricity metering Data exchange for meter reading, tariff and load control Part 62: Interface classes Basisfuncties voor de meetinrichting voor elektriciteit, gas en thermische energie voor kleinverbruikers Information technologyTelecommunications and information exchange between systemsLocal and metropolitan area networksSpecific requirementsPart 2: Logical Link Control Description Information technology -- Telecommunications and information exchange between systems -- High-level data link control (HDLC) procedures Communication systems for and remote reading of meters Part 2: Physical and link layer Communication systems for and remote reading of meters Part 3: Dedicated application layer Extended Dutch Smart Meter specification WG04 interoperability & Communications (Milan Kozole); December 2007 COSEM interface classes for setting up and managing communication profiles using power line carrier (latest update of Gyozo Kmethy dated 30 January 2008)
11 12 13 14 15 16
17
ISO/IEC 8802.2
18
ISO/IEC 13239
19 20 21 22 23
EN 13757-2 EN 13757-3 B101: Smart Meter Requirements Cosem security Project: COSEM_over_PLC
Page 9 of 68
Remark: The existing IEC 62056-series do not describe and cover yet all functionality of DLMS/COSEM required by this companion standard P3. The standardization process of this new functionality will start when the new Green book (edition 7) and Blue book (edition 9) are approved/published by the DLMS User Association.
1.4
Document list
Following table shows the complete set of documents that build up the Dutch Smart Meter Requirements, of which this tender document is a part of.
# [1] Document name postfix Main description The main document of the Dutch Smart Meter Requirements, containing all definitions and most of the use cases and requirements Tender document, containing additional general requirements, use cases and performance requirements Companion standard P1 Companion standard P2 Companion standard P3
[2]
Tender
[3] [4] [5]
P1 P2 P3
Page 10 of 68
LOGICAL DEVICES AND ASSOCIATIONS, M-BUS MODELLING (GENERAL CONCEPT)
In DLMS/COSEM, metering equipment is modelled in physical and logical devices. The actual device is the physical device. The physical device can contain multiple logical devices. For this companion standard it is decided that there will be only 1 logical device (the management logical device).
Physical device Management Logical device

Logical device name Association object
Other object
Other object
The logical device has at least 3 associations: Public client (client id 16), management client (client id 1) and pre-established client (client id 102). For each association, all LN services (GET, SET, ACTION, Event Notification) are supported. The pre-established client has the following settings: [.] [Description about the use of the associations needs to be added for the Data Concentrator.] There will be no direct connection to the M-bus device (used by P2) via the P3 interface. Access to the M-bus device has to be done with the objects offered by the logical device.
Page 11 of 68
COMMUNICATION PROFILES AND SERVICES, SECURITY
This chapter gives the required and selected communication profiles and the security requirements to be implement for the P3 interface. There are three communication profiles selected for the Dutch Smart meter. These are: GPRS Ethernet PLC DLMS/COSEM will use only the pull mechanism for the application layer3. The description how the E-meter will establish a GPRS connection has been added to the profiles part (see chapter 3.1.1). The profile for GPRS meters and Ethernet uses standard COSEM TCP/IP profile as defined in IEC 6205647 or in DLMS UA Green Book edition 6. The TCP/UDP based profile is given in figure 3.1. The DLMS/COSEM TCP based profile uses the standardized port number 4059.
Log_Dev_1 (management)
COSEM Application layer

ACSE xDLMS ASE
COSEM Transport layer

# 01
COSEM wrapper
DLMS/COSEM Transport layer TCP or UDP Port 4059
Network layer IP
Data link layer

e.g. Ethernet
Physical layer
e.g. Ethernet
Figure 3.1: TCP/UDP based profile
3 The operation principle used in this document is based on client / server model. Except for the Event notification which is based on unsolicited message sending for alarm management, for all the other services the client always asks for a request and the server send back the response of the concerned request. Following this, it can be noticed that push will be used anyway if we want that GPRS meters have ability to send alarms to the central station.
Page 12 of 68
The required setup objects for TCP/UDP, IPv4 and PPP will be described below. For the detailed attribute descriptions and methods see chapter 4.2 for the relevant paragraph of the Blue book [1].
TCP-UDP setup (Class ID: 41) To set up the TCP or UDP sub-layer of the COSEM TCP or UDP based transport layer 1 2 3 4 5 6 Logical name TCP-UDP_port IP_reference MSS nb_of_sim_conn inactivity_time_out Octet-string long-unsigned octet-string long-unsigned unsigned long-unsigned Min=40, max=65535, default=576 Value=1 Default=180 0-b:25.0.0.255
An instance of the TCP-UDP setup class contains all data necessary to set up the TCP or UDP sub-layer of the COSEM TCP or UDP based transport layer of a TCP-UDP/IP based communication profile. In TCP-UDP/IP based communication profiles, all AAs between a physical device hosting one or more COSEM client application processes and a physical device hosting one or more COSEM server application processes rely on a single TCP or UDP connection. The TCP or UDP entity is wrapped in the COSEM TCP-UDP based transport layer. Within a physical device, each application process client application process or server logical device - is bound to a Wrapper Port (WPort). The binding is done with the help of the SAP Assignment object. On the other hand, a COSEM TCP or UDP based transport layer may be capable to support more than one TCP or UDP connections, between a physical device and several peer physical devices hosting COSEM application processes.
NOTE When a COSEM physical device supports various data link layers (for example Ethernet and PPP), then an instance of the TCP-UDP setup object is necessary for each of them.
IPv4 setup (Class ID: 42) Handles all information that is related to the IP Address settings associated to a given device and to a lower layer connection on which these settings are used. 1 2 3 4 5 6 7 8 9 1 0 Logical name DL_reference port IP_address multicast_IP_address IP-options Subnet_mask gateway_IP_address use_DHCP_flag octet-string octet-string double-long-unsigned array array Min=40, max=65535, drf=576 Value=1 0-b:25.1.0.255
double-long-unsigned Def=180 double-long-unsigned
boolean primary_DNS_address double-long-unsigned secondary_DNS_addre double-long-unsigned ss
An instance of the IPv4 setup class handles all information that is related to the IP Address settings associated to a given device and to a lower layer connection on which these settings are used.
File name: Author: Version: Dutch Smart Meter Requirements v2.1 final P3.doc Date: 04-02-2008 KEMA Config. ID: B101 2.1 final Project: Functional and technical specifications Smart Meters
Page 13 of 68
There shall be an instance of this class in a device for each different network interfaces implemented.
PPP setup (Class ID: 44) Handles all information that is related to PPP settings associated to a given physical device and to a lower layer connection on which these settings are used. 1 2 3 4 5 logical_name PHY_reference LCP_options IPCP_options Octet-string long-unsigned octet-string long-unsigned 0-b:25.3.0.255
PPP_authentication unsigned
There shall be an instance of this class for each network interface of a physical device, using the PPP protocol.
3.1
Communication profiles
The three specific communication profiles are given in the following paragraphs 3.1.1 GPRS communication profile
GPRS
Application Process COSEM Interface Objects IEC 62056-61,62056-62
Application Layer
COSEM Application Layer IEC 62056-53
COSEM IP Transport Layers IEC 62056-47 COSEM Wrapper TCP or UDP IP
Media Dependant Lower Layers
Data Link Layer Physical Layer
SNDCP LLC RLC MAC GSM Radio
Figure 3.2: GPRS communication profile A GPRS modem setup object stores all the necessary data for a GPRS modem management. For the detailed attribute descriptions and methods see chapter 4.2 for the relevant paragraph of the Blue book [1].
Page 14 of 68 GPRS modem setup (Class ID: 45) A GPRS modem setup object stores all the necessary data for a GPRS modem management. 1 logical_name 0-b:25.4.0.255 octet-string 2 APN octet-string 3 PIN_code long-unsigned 4 quality_of_service structure
The connection setup mechanisme used by the grid operators will be described in this chapter!!
3.1.2
Ethernet communication profile
Ethernet
Application Process COSEM Interface Objects IEC 62056-61,62056-62
Application Layer
COSEM Application Layer IEC 62056-53
COSEM IP Transport Layers IEC 62056-47 COSEM Wrapper TCP or UDP IP
Media Dependant Lower Layers
Data Link Layer Physical Layer
Ethernet
Figure 3.3: Ethernet communication profile

Ethernet setup (Class ID: 43) Handles all information that is related to Ethernet settings associated to a given physical device and to a lower layer connection on which these settings are used 1 2 logical_name MAC_address Octet-string Octet-string 0-b:25.3.0.255 Default=180
Page 15 of 68
An instance of the Ethernet setup class handles all information that is related to Ethernet settings associated to a given physical device and to a lower layer connection on which these settings are used. There shall be an instance of this class for each network interface of a physical device, using the Ethernet protocol. 3.1.3 PLC
The profile for meters using the PLC medium as defined in IEC 62056-47 (has to be updated) or in DLMS UA Green Book edition 7 (in development) is pointed out below.
COSEM Application model IEC 62056-61 / 6-62 COSEM Client AP COSEM Client AP Application process COSEM Application model IEC 62056-61 / 6-62 COSEM Server AP (Log. device) COSEM Server AP ... (Log. device)
COSEM Application layer IEC 62056-53
Application layer
COSEM Application layer IEC 62056-53
SAP
SAP
CIASE IEC 61334-5-511
PLC network management
SAP
SAP
CIASE IEC 61334-5-511
SAP
SAP To/From LLC
SAP
SAP To/From LLC
COSEM transport layer Transport IEC 62056-47 layer Wrapper layer
COSEM transport layer IEC 62056-47 Transport layer Wrapper layer
TCP
TCP
IP network layer
Network layer
IP network layer
SAP
SAP
SAP
SAP
SAP
SAP Subnetwork Dependent Convergence Protocol: Protocol selection and segmentation
SAP
SAP
SAP
SAP
SAP
SAP
SNDCP
SNDCP
To/From CIASE
To/From CIASE
To/From CIASE
To/From CIASE
To/From CIASE
To/From CIASE
LLC ISO/IEC 8802.2
LLC IEC 61334-4-32
IEC 62056-46 Data link layer ISO/IEC 8802.2 CO-less LLC ISO/IEC 13239 HDLC based MAC
LLC layer
LLC ISO/IEC 8802.2
LLC IEC 61334-4-32
IEC 62056-46 Data link layer ISO/IEC 8802.2 CO-less LLC ISO/IEC 13239 HDLC based MAC
PLC S-FSK lower layer profile IEC 61334-5-1
MAC + Phy layer
PLC S-FSK lower layer profile IEC 61334-5-1
The ISO/IEC 8802.2 LLC layer may co-exist with IEC 61334-4-32 LLC layer and IEC 62056-46 data link layer used in existing implementations. On the server side, only one of them may be implemented. On the Client side, one or more of them may be implemented.The Client (concentrator) finds out the kind of LLC layer used by the server during the Discovery / Registration process and maps the LLC type to the System title.
The PLC solution requires support of ISO/IEC 8802.2, allowing to plug in TCP/IP later. This can co-exist with the IEC 61334-4-32 LLC layer and the IEC 62056-46 data link layer used in existing implementations. The selected LLC layer is ISO/IEC 8802-2 LLC layer. The other two are only allowed for backwards compatibility reasons.
Page 16 of 68
The nine PLC setup objects are given below with their OBIS codes. For the detailed attribute descriptions and methods see appendix B and [23].
S-FSK Phy&MAC setup (Class ID: 50)4 1 Logical name Octet-string 0-0:26.0.0.255
S-FSK Active Initiator (Class ID: 51) 1 Logical name Octet-string 0-0:26.1.0.255
S-FSK MAC synchronisation timeouts (Class ID: 52) 1 Logical name Octet-string 0-0:26.2.0.255
S-FSK MAC counters (Class ID: 53) 1 Logical name Octet-string 0-0:26.3.0.255
S-FSK IEC 61334-4-32 LLC Setup (Class ID: 55) 1 Logical name Octet-string 0-0:26.5.0.255
S-FSK Reporting system list (Class ID: 56) 1 Logical name Octet-string 0-0:26.6.0.255
ISO/IEC 8802-2 LLC Type 1 setup (Class ID: 57) 1 Logical name Octet-string 0-0:27.0.0.255
3.2
COSEM Security
The purpose of COSEM Security is to address the requirement for confidentiality and authentication in DLMS/COSEM communication protocol. COSEM Security should be implemented as described in DLMS UA Green Book edition 7 and DLMS UA Blue Book edition 9. Because these documents are not yet published the COSEM security requirements and way to implement are given in reference [22].
The choice of the modulation band (attribute 6 frequency) (see appendix B.1) must be mutual agreed between the vendors to reach operability. A selection of which modulation band to use, shall be tuned after practical experiences in the field . The selection depends of the architecture of the Dutch Grid in general.
Page 17 of 68
COSEM Security [22] describes how security mechanisms are used with DLMS/COSEM communication protocol. Both access and message security are required to address requirements for integrity and confidentiality in DLMS/COSEM communication protocol. Access Security DLMS/COSEM access security provides Low Level Security (LLS) and High Level Security (HLS) authentication mechanisms. LLS enable client only authentication with password and HLS enable client/server authentication with challenge mechanism. Authentication is used for association establishing. Associations offer specific view to COSEM objects with associated access rights to individual objects. During the setup of the connection (the application association) HLS should be used. The Management Logical device should be accessible without security. Message Security DLMS/COSEM message security provides encryption and authentication of the COSEM APDU with standard symmetric key algorithms. It provides confidentiality using CBC cipher mode of operation, authentication using HMAC and CBC-MAC algorithms and combined confidentiality and authentication using CCM or GCM cipher mode of operation. Encryption is used to provide confidentiality for data. The data to be protected is called plaintext. Encryption transforms the data into ciphertext. Ciphertext can be transformed back into plaintext using decryption. The Approved algorithms for encryption and decryption algorithms are: the Advanced Encryption Standard (AES) and the Triple Data Encryption Algorithm (TDEA). TDEA is based on the Data Encryption Standard (DES), which is no longer approved for Federal Government use except as a component of TDEA. Message authentication and encryption should be used in all situations and the Advanced Encryption Standard (AES) is the selected algorithm for ciphering.
Page 18 of 68
Proposed Authentication Algorithms:

Authentication Algorithm NULL HMAC-MD5-96 HMAC-SHA1-96 AES-XCBC-MAC-96 HMAC HMAC AES 128 128 128 MD5 SHA-1 CBC-MAC Algorithm Key Size [Bits] Hash Function/ Mode of Operation
Proposed Encryption Algorithms:

Encryption Algorithm NULL TDES-CBC AES-CBC-128 AES-CCM-128 AES-GCM-128 TDES AES AES AES 192 128 128 128 CBC CBC CCM GCM Algorithm Key Size [Bits] Mode of Operation
Proposed Security Suites:

Security Suite Id 0 1 2 3 4 5 6 7 Authentication Algorithm Encryption Algorithm NULL HMAC-MD5-96 HMAC-SHA1-96 HMAC-MD5-96 HMAC-SHA1-96 AES-XCBC-MAC-96 AES-CCM-128 AES-GCM-128 NULL TDES-CBC TDES-CBC AES-CBC-128 AES-CBC-128 AES-CBC-128 AES-CCM-128 AES-GCM-128
Note: Security Suites 6 and 7 use Combined Mode of operation with Authentication and Encryption. The selected security suite ID is 7. This choice covers extensive security at authentication and encryption level and realise full interoperability.
Page 19 of 68
OVERVIEW OF OBJECT MODEL
The object model of the Dutch smart meter is divided in three parts: a. Abstract objects (chapter 5) b. Electricity related objects (chapter 6) c. M-bus related objects (chapter 7) Before all the required objects for the Dutch smart meter are described in more detail in the mentioned chapters an overview will be given of all required profiles. Further an explanation of the event and error handling is described in paragraph 4.2 of this chapter for better understanding how the required objects for covering that functionality are related to each other.
4.1
Profile structure Dutch smart meter
In figure 4.1 the profiles are summarized which will be required in relation to the Dutch smart meter requirements. The Monthly billing values (combined) object is described in more detail in paragraph 5.5 (Abstract objects). The Daily load profile values (E only) and 15 min load profile values are described in more detail in paragraph 6.3 (Electricity related objects). The Hourly load profile values (per channel) are part of paragraph 7.4 (M-bus related objects).
0-0:98.1.0.255 monthly billing values (combined) captured object list = clock;+A rate 1;+A rate 2; A rate 1; A rate 2;M-bus register channel 1 to 4 capture period = triggered from a single action scheduler at the end of every month profile entries = 13 (13 month)
Note: Just for storage in case of problems, not read by CAS regularly
P3 0-4:24.3.0.255 0-3:24.3.0.255 0-2:24.3.0.255 1-0:99.2.0.255 Daily load profile values (E only)

captured object list = clock; E-status; +A rate 1, 2; A rate 1, 2; capture period = 86400 s (daily) profile entries = 10 (10 days)
1-0:99.1.0.255 15 min load profile values (E only)

captured object list = clock; E-status; +A; A
0-1:24.3.0.255 Hourly load profile values (per channel)

captured object list = clock; status; M-Bus register
capture period = 900 s (15 min) profile entries = 960 (10 days)
capture period = 3600 s (60 min) profile entries = 240 (10 days)
Note: Either captured every hour or once a day
Note: All load profiles contain exactly one entry per capture period (no gaps, no additional entries). This also applies in case of time shifts and/or power outages
P3
P3
P3 (P1)
Figure 4.1: Structure of profiles of Dutch Smart meter
Page 20 of 68
4.2
Event and error handling
This paragraph gives an overview of the event and error handling based on DLMS objects for the Dutch smart meter to fulfil the requirements stated in [21].
Standard Event Log
All general events, e.g changes of the clock, changes of the configuration, clearing of profiles, all kind of self check errors, activation of new parameters, activation of new time of use, etc.
100 entries
Filter
Events
Control Log
Events related to the disconnector, e.g connect, disconnect, changing of the disconnector threshold.
10 entries Filter Filter
Power Failure Log Error Register

Duration of long power outages
10 entries
Fraud Detection Log

Events related to fraud attemps, e.g removal of terminal cover, removal of meter cover, strong DC field detection, access with wrong password
30 entries Filter
Alarm Register
Filter
>0
M-Bus Event Log

All events concerning the M-bus devices, e.g changes of the clock, communication erros, etc.
30 entries Filter
Alarm
M-Bus Control Logs

Changes of the states related to a MBus disconnector, e.g. a gas valve, (connect, disconnect). 1 instance per M-Bus device
10 entries Filter
A lot of events are generated by the meter itself or by its environment. All these events are logged in several event logs.The objects are described in chapters 5, 6 and 7 in more detail. Additionally they are also used to set and clear errors as well as to trigger alarms. The diagram above gives an overview about the handling, the details of the objects are described in the chapters 5, 6 and 7.
Page 21 of 68
4.2.1
Events
Every event has a unique code to identify the action which has triggered it. Every event is assigned to one event log (event filter) and it is only stored there. This assignment is fixed and can't be changed dynamically. Therefore the event filter is not visible from outside. Event codes
Disconnector Control Log Fraud Detection Log M-Bus Control Log 1 M-Bus Control Log 2 M-Bus Control Log 3 M-Bus Control Log 4 Standard Event log M-Bus Event Log
Number
Name
Description
Standard event log cleared Fraud detection log cleared Disconnector control log cleared M-Bus event log cleared
Indicates that the standard event log was cleared. This is always the first entry in the event log. Indicates that the fraud detection log was cleared. This is always the first entry in the event log. Indicates that the disconnector control log was cleared. This is always the first entry in the event log. Indicates that the M-Bus event log was cleared. This is always the first entry in the event log.
x x x x x x x x x
M-Bus control log cleared Indicates that M-Bus control log was cleared. This is always (channel 1) the first entry in the event log. M-Bus control log cleared Indicates that M-Bus control log was cleared. This is always (channel 2) the first entry in the event log. M-Bus control log cleared Indicates that M-Bus control log was cleared. This is always (channel 3) the first entry in the event log. M-Bus control log cleared Indicates that M-Bus control log was cleared. This is always (channel 4) the first entry in the event log. Daylight saving time enabled or disabled Indicates the regular change from and to daylight saving time. The time stamp shows the time before the change. This event is not set in case of manual clock changes and in case of power failures. Indicates that the clock has been adjusted. The date/time that is stored in the event log is the old date/time before adjusting the clock. Indicates that the clock has been adjusted. The date/time that is stored in the event log is the new date/time after adjusting the clock. Indicates that clock may be invalid, i.e. if the power reserve of the clock has exhausted. It is set at power up. Indicates that the battery must be exchanged due to the expected end of life time. Indicates that the passive TOU has been activated. Indicates that the error register was cleared. Indicates that the alarm register was cleared. Indicates a physical or a logical error in the program memory. Indicates a physical or a logical error error in the RAM. Indicates a physical or a logical error in the non volatile memory
Clock adjusted (old date/time) Clock adjusted (new date/time) Clock invalid Replace Battery TOU activated Error register cleared Alarm register cleared Program memory error RAM error NV memory error
x x x x x x x x x x
Page 22 of 68
Disconnector Control Log
Fraud Detection Log
M-Bus Control Log 1
M-Bus Control Log 2
M-Bus Control Log 3
Name
Description
Watchdog error Measurement system error
Indicates a watch dog reset or a hardware reset of the microcontroller. Indicates a logcial or phsysical error in the measurement system
x x
Terminal cover removed Terminal cover closed Strong DC field detected No strong DC field anymore Meter cover removed Meter cover closed n times wrong password
Indicates that the terminal cover has been removed. Indicates that the terminal cover has been closed. Indicates that a strong magnetic DC field has been detected. Indicates that the strong magnetic DC field has disappeared. Indicates that the meterl cover has been removed. Indicates that the meter cover has been closed. Indicates that a user tried to gain access with a wrong password (intrusion detection)
x x x x x x x
Manual disconnection Manual connection Remote disconnection Remote connection Local disconnection Limiter threshold exceeded Limiter threshold ok
Indicates that the disconnector has been manually disconnected. Indicates that the disconnector has been manually connected. Indicates that the disconnector has been remotely disconnected. Indicates that the disconnector has been remotely connected. Indicates that the disconnector has been locally disconnected. Indicates that the limiter threshold has been exceeded. Indicates that the monitored value of the limiter dropped below the threshold.
x x x x ? x x x
Limiter threshold changed Indicates that the limiter threshold has been changed
Communication error Mbus channel 1 Communication ok M-bus channel 1 Replace Battery M-Bus channel 1 Fraud attempt M-Bus channel 1 Manual disconnection MBus channel 1
Indicates a communication problem when reading the meter connected to channel 1 of the M-Bus Indicates that the communication with the M-Bus meter connected to channel 1 of the M-Bus is ok again. Indicates that the battery must be exchanged due to the expected end of life time. Indicates that a fraud attempt has been registered. Indicates that the disconnector has been manually disconnected.
x x x x x x x
Manual connection M-Bus Indicates that the disconnector has been manually connected. channel 1 Remote disconnection MBus channel 1 Indicates that the disconnector has been remotely disconnected.
M-Bus Control Log 4
Standard Event log
M-Bus Event Log
Number
Page 23 of 68
Fraud Detection Log
M-Bus Control Log 1
M-Bus Control Log 2
M-Bus Control Log 3
Name
Description
Remote disconnection MBus channel 1 Valve alarm M-Bus channel 1 Communication error Mbus channel 2 Communication ok M-bus channel 2 Replace Battery M-Bus channel 2 Fraud attempt M-Bus channel 2 Manual disconnection MBus channel 2
Indicates that the disconnector has been remotely connected. Indicates that a valve alarm has been registered. Indicates a communication problem when reading the meter connected to channel 2 of the M-Bus Indicates that the communication with the M-Bus meter connected to channel 2 of the M-Bus is ok again. Indicates that the battery must be exchanged due to the expected end of life time. Indicates that a fraud attempt has been registered in the MBus device. Indicates that the disconnector has been manually disconnected.
x x x x x x x x x x x x x x x x x x x x x x x
Manual connection M-Bus Indicates that the disconnector has been manually connected. channel 2 Remote disconnection MBus channel 2 Remote disconnection MBus channel 2 Valve alarm M-Bus channel 2 Communication error Mbus channel 3 Communication ok M-bus channel 3 Replace Battery M-Bus channel 3 Fraud attempt M-Bus channel 3 Manual disconnection MBus channel 3 Indicates that the disconnector has been remotely disconnected. Indicates that the disconnector has been remotely connected. Indicates that a valve alarm has been registered. Indicates a communication problem when reading the meter connected to channel 3 of the M-Bus Indicates that the communication with the M-Bus meter connected to channel 3 of the M-Bus is ok again. Indicates that the battery must be exchanged due to the expected end of life time. Indicates that a fraud attempt has been registered. Indicates that the disconnector has been manually disconnected.
Manual connection M-Bus Indicates that the disconnector has been manually connected. channel 3 Remote disconnection MBus channel 3 Remote disconnection MBus channel 3 Valve alarm M-Bus channel 3 Communication error Mbus channel 4 Communication ok M-bus channel 4 Replace Battery M-Bus channel 4 Indicates that the disconnector has been remotely disconnected. Indicates that the disconnector has been remotely connected. Indicates that a valve alarm has been registered. Indicates a communication problem when reading the meter connected to channel 4 of the M-Bus Indicates that the communication with the M-Bus meter connected to channel 4 of the M-Bus is ok again. Indicates that the battery must be exchanged due to the expected end of life time.
M-Bus Control Log 4
Standard Event log
M-Bus Event Log
Number
Page 24 of 68
Fraud Detection Log
M-Bus Control Log 1
M-Bus Control Log 2
M-Bus Control Log 3
Name
Description
Fraud attempt M-Bus channel 4 Manual disconnection MBus channel 4
Indicates that a fraud attempt has been registered. Indicates that the disconnector has been manually disconnected.
x x x x x x
Manual connection M-Bus Indicates that the disconnector has been manually connected. channel 4 Remote disconnection MBus channel 4 Remote disconnection MBus channel 4 Valve alarm M-Bus channel 4 Indicates that the disconnector has been remotely disconnected. Indicates that the disconnector has been remotely connected. Indicates that a valve alarm has been registered.
4.2.2
Event Logs
The E-meter features 4 different event logs as described below. Additionally there is one event log for all M-Bus devices as well as one control log per M-Bus channel available. All logs except the power failure log have the same basic structure (timestamp and event code). The structure per event log is fixed, i.e. it is not possible to store different parameters per event. Standard Event Log [0-0:99.98.0.255] (paragraph 5.7)
Contains all events not recorded in a special event log, e.g. changes of the clock, changes of the configuration, clearing of profiles, all kind of self check errors, activation of new parameters, activation of new time of use, etc. Structure: Timestamp Event Code Minimum size: 100 entries Control Log [2-0:99.98.3.255] (paragraph 6.6) Contains all events related to the disconnector, e.g. connect, disconnect, changing of the disconnector threshold. Structure: Timestamp Event Code Currently active disconnector threshold Minimum size: 10 entries Power Failure Log [1-0:99.97.0.255]) (paragraph 5.9) Contains all events related to long power outages, i.e. start and end of a long power outage.
File name: Author: Version: Dutch Smart Meter Requirements v2.1 final P3.doc Date: 04-02-2008 KEMA Config. ID: B101 2.1 final Project: Functional and technical specifications Smart Meters
M-Bus Control Log 4
Standard Event log
M-Bus Event Log
Number
Page 25 of 68
Structure: Timestamp Event Code Minimum size: 10 entries Fraud Detection Log [0-0:99.98.1.255] (paragraph 5.8)
Contains all events related to the detection of fraud attempts, e.g. removal of terminal cover, removal of meter cover, strong DC field detection, access with wrong password, etc. Structure: Timestamp Event Code Minimum size: 30 entries M-Bus Standard Event Log [0-0:99.98.4.255] (paragraph 7.5)
Contains all events related to the M-Bus devices, e.g. changes of the clock, communication erros, etc. Structure: Timestamp Event Code Minimum size: 30 entries M-Bus Control Logs (0-x:24.5.0.255) ( paragraph 7.6) Contains all events related to an M-Bus disconnector, e.g. a gas valve (open valve, close valve). Structure: Timestamp Event Code Minimum size: 10 entries
4.2.3
Error Handling
A predefined selection of events set and clear flags in the error register. The error register can be read and displayed at anytime to see, if there is a malfunction in the device. Depending on the type of error, some errors clear themselves if the reason for the error has disappeared. Other must be cleared via CAS. Nevertheless the events are stored in one of the event logs. Error Codes The table below gives an overview of all errors and their assignment.
reserved
Byte 4 8 4 2 1 8 4 2 1 8 4 2
Com Errors
Byte 3 1 8 4 2 1 8
Critical Errors
Byte 2 4 2 1 8 4 2 1 8
Other Errors
Byte 1 4 2 1 8 4 2 1
Page 26 of 68
not used
not used
not used
not used
not used
not used
not used
not used
not used
not used
not used
not used
Communcation errro M-Bus channel 4
not used
not used
not used
Watchdog error
Measruement System Error
NV memory Erroror
RAM Error
Program memory error
not used
not used
not used
not used
not used
not used
Replace battery
Clock invalid
4.2.4
Alarm Handling
A selection of events can be made which are treated as alarms (alarm filter). If one of these events occurs, the corresponding flag in the alarm register is set and an alarm is then raised via PLC or via GSM/GPRS. All alarm flags in the alarm register remain active until the alarm register is cleared via CAS (acknowledgment). Typically fraud attempts are selected as alarm triggers. Power outages normally can't be selected since the communication network is also down in case of a power outage. Alarm Codes To be defined. Alarm Filters 4.2.5 AMR Profile status Code
In all load profiles a new simplified status code is used for every entry. It is derived from the existing VDN status word but can only be used for profiles containing cumulative values. The AMR Profile status code has a size of 1 byte and it is shown in hexadecimal form. The following table describes the state and the function of all bits:
Page 27 of 68
Flag Bit 7
Description Power down: This bit is set to indicate that an all-phase power failure occurred. not used Clock adjusted: The bit is set when clock has been adjusted more than the synchronisation limit. A the same time the DNV flag is set because the capture period deviates from its nominal lengths and may not be used for billing. not used. Daylight saving: Indicates whether or not the daylight saving time is currently active. The bit is set if the daylight saving time is active (summer) and cleared in winter. Data not valid: Indicates that the current entry may not be used for billing e.g. due to time shift or if no values have been recorded during the capture period. Clock invalid: The power reserve of the calendar clock has been exhausted. The time is declared as invalid. A the same time the DNV bit is set. Critical error: A serious error such as a hardware failure or a checksum error has occurred. A the same time, the DNV bit is set.
PDN
Bit 6 Bit 5
CAD
Bit 4 Bit 3
DST
Bit 2 DNV Bit 1
CIV
Bit 0 ERR
Page 28 of 68
5 5.1
ABSTRACT OBJECTS SAP assignment, Association LN,COSEM logical device name
SAP Assignment (Class ID: 17) Information about the logical devices in the physical device 1 2 Logical name Value Octet-string asslist_type 0-0:41.0.0.255 Only 1 logical device: The management logical device
Association LN (Class ID: 15) 1 2 3 4 logical_name object_list octet-string objlist_type 0-0:40.0.0.255
associated_partners_ associated_partners_type id application_context_ name application_context_name
5 6
xDLMS_context_info authentication_ mechanism_name
xDLMS_context_type mechanism_name
7 8 1
LLC_secret association_status reply_to_HLS_ authentication
octet-string enum
COSEM Logical Device Name (Class ID: 1) 1 2 Logical name Value Octet-string Octet-string 0-0:42.0.0.255 Unique identification of the logical device
5.2
1 2
Identification numbers
Octet-string Octet-string[16] 0-0:96.1.0.255 E-meter serial number (Serial number of the device, handled by the manufacturer)
Device ID 1 (Class ID: 1) Logical name Value
Device ID 2 (Class ID: 1) 1 2 Logical name Value Octet-string Octet-string[48] 0-0:96.1.1.255 E-meter equipment identifier (Owned and handled by the utility, has no meaning to the device.)
Page 29 of 68 Device ID 3 (Class ID: 1) 1 2 Logical name Value Octet-string Octet-string[48] 0-0:96.1.2.255 Function location (Owned and handled by the utility, has no meaning to the device.)
Device ID 4 (Class ID: 1) 1 2 Logical name Value Octet-string Octet-string[48] 0-0:96.1.3.255 Location information (Owned and handled by the utility, has no meaning to the device.)
Device ID 5 (Class ID: 1) 1 2 Logical name Value Octet-string Octet-string[48] 0-0:96.1.4.255 No special meaning defined (General purpose ID for any identification purposes. Owned and handled by the utility, has no meaning to the device.)
5.3
1 2 3 4 5 6 7 8 9
Clock
Octet-string octet-string long status octet-string octet-string integer boolean enum Value = 1. Internal crystal 0-0:1.0.0.255 current local date and time
Clock (Class ID: 8) Logical name time time_zone status daylights_savings_be gin daylights_savings_en d daylights_savings_ deviation daylights_savings_ enabled clock_base
last sunday in march at 02:00 last sunday in october at 03:00 Value = 60
Clock Time Shift Limit (Class ID: 3) 1 2 3 Logical name value Scaler_unit Octet-string unsigned scal_unit_type 1-0:0.9.11.255 Value = 60. Maximum allowed time shift without registration of a time shift event Value = {0,7}. Scaler=0, unit=seconds
Page 30 of 68
5.4
Activity Calendar and Special Days Table
Activity Calendar (Class ID: 20) Time of use for tariff control 1 2 3 4 5 Logical name calendar_name_activ e season_profile_active week_profile_table_ active day_profile_table_act ive Octet-string octet-string array[4] array[4] array[4] 0-0:13.0.0.255
minimum of 4 seasons minimum of 4 week profiles (= 1 week profile per season) minimum of 4 day profiles (= weekday, Saturday, Sunday, special day). Every day profile can contain at least 4 entries (switching points)
6 7 8 9 1 0
calendar_name_pass ive season_profile_passi ve week_profile_table_ passive day_profile_table_ passive activate_passive_ calendar_time
octet-string array[4] array[4] array[4] octet-string see above see above see above immediate activation can be done by setting the activation date to the current date
Special Days Table (Class ID: 11) 1 2 Logical name Entries Octet-string array[30] 0-0:11.0.0.255 At least 30 special days
Currently active tariff (Class ID: 1) 1 2 Logical name Value Octet-string Octet-string 0-0:96.14.0.255 currently active tariff = active_mask of register activation object
5.5
Billing periods and profiles
End of billing period 1 (Class ID: 22) End of every month 1 2 3 4 Logical name executed_script type execution_time Octet-string script enum array 0-0:15.0.0.255 billing period reset Value = 1, fixed time, wildcard in date Value = "00000000"; "FFFFFF01FF", at midnight (or any other time) of the first day of every month
Page 31 of 68 Data of billing period 1 (Class ID: 7) Monthly billing values 1 2 3 Logical name buffer capture_objects Octet-string array array 0-0:98.1.0.255 {8,0-0:1.0.0.255,2,0}; {3,1-0:1.8.1.255,2,0}; {3,1-0:1.8.2.255,2,0}; {3,1-0:2.8.1.255,2,0}; {3,1-0:2.8.2.255,2,0}; {4,0-x:24.2.y.255,2,0}; ... ( = clock;+A rate 1;+A rate 2;A rate 1;A rate 2; up to 4 M-Bus register values) Can be extended with up to 4 M-Bus register values or additional tariff registers 0, triggered from single action scheduler with billing period 1 1, unsorted (FIFO) None, unsorted 13 months
4 5 6 7 8
capture_period sort_method sort_object entries_in_use profile_entries
double-long-unsigned enum object definition double-long-unsigned double-long-unsigned
5.6
Error and Alarm Handling (error register, alarm register)
Error Object (Class ID: 1) Error register 1 2 Logical name Value Octet-string double-long-unsigned 0-0:97.97.0.255 Error code (See definition of error codes in paragraph 4.2.3)
Alarm Object (Class ID: 1) Alarm register 1 2 Logical name Value Octet-string double-long-unsigned 0-0:97.98.0.255 Alarm code (See definition of alarm codes in paragraph 4.2.4)
Alarm filter (Class ID: 1) 1 2 Logical name Value Octet-string double-long-unsigned 0-0:97.98.10.255 This filter defines, if an event is handled as an alarm when it appears. Bit mask with the same structure as the current value of the alarm object code (See definition of alarm filters in paragraph 4.2.4)
Page 32 of 68
5.7
Event Handling (events and logs)
Event Log (Class ID: 7) Standard event log containing errors and alarms 1 2 3 Logical name buffer capture_objects Octet-string array Array 0-0:99.98.0.255 {8,0-0:1.0.0.255,2,0}; {0-0:96.11.e.255,2,0} ( = clock;event code) (See definition of event codes in paragraph 4.2.1) 0, asynchronously 1, unsorted (FIFO) None, unsorted 100
4 5 6 7 8
5.8
Fraud detection (event log)
Fraud Detection Log (Class ID: 7) Event log containing all fraud detection events 1 2 3 Logical name buffer capture_objects Octet-string array Array 0-0:99.98.1.255 {8,0-0:1.0.0.255,2,0}; {1,0-0:96.11.e.255,2,0} ( = clock;tamper event code) (See definition of event codes in paragraph 4.2.1) 0, asynchronously 1, unsorted (FIFO) None, unsorted 30
4 5 6 7 8
5.9
Power Failure Event Log (counters and thresholds)
Number of power failures in any phases (Class ID: 1) (single and polyphase meters) 1 2 Logical name Value Octet-string long-unsigned 0-0:96.7.21.255
Number of long power failures in any phases (Class ID: 1) (single and polyphase meters) 1 2 Logical name Value Octet-string long-unsigned 0-0:96.7.9.255
Page 33 of 68 Time threshold for long power failure (Class ID: 3) 1 2 3 Logical name Value scaler_unit Octet-string long-unsigned scal_unit_type 0-0:96.7.20.255 Value = 180 Value = {0,7}, scaler=0, unit=seconds
Duration of long power failures in any phase (Class ID: 3) 1 2 3 Logical name Value scaler_unit Octet-string long-unsigned scal_unit_type 0-0:96.7.19.255 Is reset at the end of the power failure, i.e. after capturing in the event log Value = {0,7}, scaler=0, unit=seconds
Power Failure Event Log (Class ID: 7) 1 2 3 Logical name buffer capture_objects Octet-string array Array [2] 1-0:99.97.0.255 {8,0-0:1.0.0,2,0}; {1,0-0:96.7.19.255,2,0} ( = clock;duration of long power failures in any phase) Timestamp = end of power failure 0, asynchronously 1, unsorted (FIFO) None, unsorted 10
4 5 6 7 8
5.10
Disconnector (Control and Log, scheduler)
Disconnect control (Class ID: 70) Controls the connection and disconnection of the premises of the consumer 1 2 3 4 1 2 Logical name output_state control_state control_mode remote_disconnect remote_connect Octet-string boolean enum enum 0-0:96.3.10.255
The Disconnect Control class is a new class that is not specified in the current version of the Blue Book [1], but it will be defined in the next version. The specification of this class can be found in 0.3
Page 34 of 68 Control log (Class ID:7) Changes of the states related to the disconnect control are recorded (changing threshold, connect, disconnect) 1 2 3 logical_name buffer capture_objects octet-string array array {8, 0-0:1.0.0, 2, 0}, clock; 0-0:99.98.2.255
{1, 0-0:96.11.e, 255,2, 0}, control event code {71, 1-0:17.0.0, 3, 0}, limiter threshold Event codes must be defined in chapter 4.2.1 4 5 6 7 8 1 2 capture_period sort_method sort_object entries_in_use profile_entries reset capture optional, has no meaning double-long-unsigned enum object definition double-long-unsigned double-long-unsigned 10 Value = 0, asynchronously Value = 1, unsorted (FIFO) None, unsorted
Disconnect Control Scheduler (Class ID: 22) 1 2 3 4 Logical name executed_script type execution_time Octet-string script enum array 0-0:15.0.1.255 connect or disconnect script of disconnector script table Value = 1, fixed time Time; date. Dedicated timepoint for connection or disconnection. No wildcards in date allowed
Disconnector Script Table (Class ID: 9) 1 2 Logical name Scripts Octet-string Array[2] 0-0:10.0.106.255 connect and disconnect service of the disconnector object
Page 35 of 68
5.11
Limiter
Limiter (Class ID: 71) Handles the normal current monitoring as well as the emergency settings (code red) 1 2 3 4 5 6 7 8 9 1 0 1 1 1 Logical name monitored_value threshold_active threshold_normal treshold_emergency min_over_threshold_duration min_under_threshold_duration emergency_profile emergency_profile_group_id emergency_profile_active actions emergency_profile_update Octet-string value_definition threshold threshold threshold double_long_unsigned double_long_unsigned emergency_profile_type long-unsigned boolean action_set 0-0:17.0.0.255 instantaneous current
The Limiter class is a new class that is not specified in the current version of the Blue Book [1], but it will be defined in the next version. The specification of this class can be found in 0.2.
5.12
P1 objects (messages, readout list)
Consumer Message Text (Class ID: 1) Consumer message text sent to port P1 1 2 Logical name Value Octet-string Octet-string[1024] 0-0:96.13.0.255 Message text sent to port P1 without any further interpretation
Consumer Message Code (Class ID: 1) Consumer message code shown on display and P1 1 2 Logical name Value Octet-string Octet-string[64] 0-0:96.13.1.255 Message code must be shown on numeric display (including scroll feature), message codes are defined by GC.
General local port readout (Class ID: 7) P1 port readout list 1 2 3 4 5 6 7 8 Logical name buffer capture_objects capture_period sort_method sort_object entries_in_use profile_entries Octet-string array Array [16] double-long-unsigned enum object definition double-long-unsigned double-long-unsigned 0-0:21.0.0.255 last readout readout objects, a maximum of 16 entries is possible 10, update period of P1 [s] 1, unsorted (FIFO) None, unsorted 1
Page 36 of 68
ELECTRICITY RELATED OBJECTS
This section holds a complete overview of all electricity related objects and their attributes.
6.1
1 2
Identification numbers (i.e. firmware version)

Octet-string Octet-string 1-0:0.2.0.255 Version identifier of the currently active firmware in the E-meter
Active firmware version (Class ID: 1) Logical name Value
6.2
1 2 3
E registers (+A, -A, all rate registers)

Octet-string double-long-unsigned scal_unit_type 1-0:1.8.0.255 Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (+A) (Class ID: 3) Logical name Value Scaler_unit
Active energy import (-A) (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:2.8.0.255 Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (+A) rate 1 (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:1.8.1.255 Rate 1 = Low tariff Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (+A) rate 2 (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:1.8.2.255 Rate 2 = normal/high tariff Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (+A) rate 3 (Class ID: 3) (for future use) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:1.8.3.255 Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (+A) rate 4 (Class ID: 3) (for future use) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:1.8.4.255 Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Page 37 of 68 Active energy import (-A) rate 1 (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:2.8.1.255 Rate 1 = Low Tariff Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (-A) rate 2 (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:2.8.2.255 Rate 2 = Normal/high tariff Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (-A) rate 3 (Class ID: 3) (for future use) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:2.8.3.255 Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
Active energy import (-A) rate 4 (Class ID: 3) (for future use) 1 2 3 Logical name Value Scaler_unit Octet-string double-long-unsigned scal_unit_type 1-0:2.8.4.255 Value = {0,30}, scaler=0, unit=Wh, resolution: 0.000 kWh
6.3
E profiles (15', daily)
Load profile with period 1 (Class ID: 7) E interval readings every 15 minutes 1 2 Logical name buffer Octet-string array 1-0:99.1.0.255 The buffer must be filled monotonously, i.e. no irregular entries are allowed = exactly one entry per capture period {8,0-0:1.0.0.255,2,0}; {1,0-0:96.10.20.255,2,0} {3,0-0:1.8.0.255,2,0}; {3,0-0:2.8.0.255,2,0} ( = clock;AMR profile status; +A;A) Profile status see paragraph 4.2.5 900 (15 minutes) 1 or 3 (unsorted (FIFO) or sorted (largest)) none or {8,0-0:1.0.0.255,2,0} (unsorted or sorted by clock) 960 (10 days)
capture_objects
Array
4 5 6 7 8
Page 38 of 68 Load profile with period 2 (Class ID: 7) Daily E billing values 1 2 Logical name buffer Octet-string array 1-0:99.2.0.255 The buffer must be filled monotonously, i.e. no irregular entries are allowed = exactly one entry per capture period {8,0-0:1.0.0.255,2,0}; {1,0-0:96.10.20.255,2,0} {3,0-0:1.8.1.255,2,0}; {3,0-0:1.8.2.255,2,0} {3,0-0:2.8.1.255,2,0}; {3,0-0:2.8.2.255,2,0} ( = clock;AMR profile status; +A rate 1;+A rate 2; A rate 1;A rate 2) Profile status see paragraph 4.2.5 86400 (daily) 1 or 3 (unsorted (FIFO) or sorted (largest)) none or {8,0-0:1.0.0.255,2,0} (unsorted or sorted by clock) 10 (10 days)
capture_objects
Array
4 5 6 7 8
6.4
1 2 3
Instantaneous Values (voltage, current, power)

Octet-string long-unsigned scal_unit_type 1-0:32.7.0.255 Value = {0,35}, scaler=0, unit=V, resolution: 0 V
Instantaneous voltage L1 (Class ID: 3) Logical name Value Scaler_unit
Average voltage L1 (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:32.24.0.255 10 minutes average voltage. Averaging scheme 3 is used for instantaneous values Value = {0,35}, scaler=0, unit=V, resolution: 0 V
Instantaneous current L1 (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:31.7.0.255 Value = {0,33}, scaler=0, unit=A, resolution: 0 A
Instantaneous voltage L2 (Class ID: 3) (polyphase meters only) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:52.7.0.255 Value = {0,35}, scaler=0, unit=V, resolution: 0 V
Page 39 of 68 Average voltage L2 (Class ID: 3) (polyphase meters only) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:52.24.0.255 10 minutes average voltage. Averaging scheme 3 is used for instantaneous values Value = {0,35}, scaler=0, unit=V, resolution: 0 V
Instantaneous current L2 (Class ID: 3) (polyphase meters only) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:51.7.0.255 Value = {0,33}, scaler=0, unit=A, resolution: 0 A
Instantaneous voltage L3 (Class ID: 3) (polyphase meters only) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:72.7.0.255 Value = {0,35}, scaler=0, unit=V, resolution: 0 V
Average voltage L3 (Class ID: 3) (polyphase meters only) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:72.24.0.255 10 minutes average voltage. Averaging scheme 3 is used for instantaneous values Value = {0,35}, scaler=0, unit=V, resolution: 0 V
Instantaneous current L3 (Class ID: 3) (polyphase meters only) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:71.7.0.255 Value = {0,33}, scaler=0, unit=A, resolution: 0 A
Instantaneous active power (+P) (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:15.7.0.255 Value = {0,27}, scaler=1, unit=W, resolution: 0.00 kW
Instantaneous current (Class ID: 3) 1 2 3 Logical name Value Scaler_unit Octet-string long-unsigned scal_unit_type 1-0:90.7.0.255 Total current (sum of all phases) Value = {0,33}, scaler=0, unit=A, resolution: 0 A
Page 40 of 68
6.5
1 2
Power Quality (Voltage sags and swells)

Octet-string long-unsigned 1-0:12.31.0.255 Value = 207, threshold for the detection of power sags, programmable according to requirements of the GC Value = {0,35}, scaler=0, unit=V
Threshold for voltage sag (Class ID: 3) Logical name Value
Scaler_unit
scal_unit_type
Time threshold for voltage sag (Class ID: 3) 1 2 Logical name Value Octet-string long-unsigned 1-0:12.43.0.255 Value = 30, duration of the voltage sag until it is detected, programmable according to requirements of the GC Value = {0,7}, scaler=0, unit=seconds
Scaler_unit
scal_unit_type
Number of voltage sags in phase L1 (Class ID: 1) 1 2 Logical name Value Octet-string long-unsigned 1-0:32.32.0.255 Value = 30, duration of the voltage sag until it is detected, programmable according to requirements of the GC
Number of voltage sags in phase L2 (Class ID: 1) (polyphase meters only) 1 2 Logical name Value Octet-string long-unsigned 1-0:52.32.0.255 Value = 30, duration of the voltage sag until it is detected, programmable according to requirements of the GC
Number of voltage sags in phase L3 (Class ID: 1) (polyphase meters only) 1 2 Logical name Value Octet-string long-unsigned 1-0:72.32.0.255 Value = 30, duration of the voltage sag until it is detected, programmable according to requirements of the GC
Threshold for voltage swell (Class ID: 3) 1 2 Logical name Value Octet-string long-unsigned 1-0:12.35.0.255 Value = 253, threshold for the detection of power swells, programmable according to requirements of the GC Value = {0,35}, scaler=0, unit=V
Scaler_unit
scal_unit_type
Time threshold for voltage swell (Class ID: 3) 1 2 Logical name Value Octet-string long-unsigned 1-0:12.44.0.255 Value = 30, duration of the voltage swell until it is detected, programmable according to requirements of the GC Value = {0,7}, scaler=0, unit=seconds
Scaler_unit
scal_unit_type
Page 41 of 68 Number of voltage swells in phase L1 (Class ID: 1) 1 2 Logical name Value Octet-string long-unsigned 1-0:32.36.0.255 Value = 30, duration of the voltage swell until it is detected, programmable according to requirements of the GC
Number of voltage swells in phase L2 (Class ID: 1) (polyphase meters only) 1 2 Logical name Value Octet-string long-unsigned 1-0:52.36.0.255 Value = 30, duration of the voltage swell until it is detected, programmable according to requirements of the GC
Number of voltage swells in phase L3 (Class ID: 1) (polyphase meters only) 1 2 Logical name Value Octet-string long-unsigned 1-0:72.36.0.255 Value = 30, duration of the voltage swell until it is detected, programmable according to requirements of the GC
Page 42 of 68
7 7.1
M-BUS RELATED OBJECTS M Bus Master Setup
M-Bus Master Setup (Class ID: 72) Setup of M-bus master for every M-bus client (4 instances, one per channel, see additional info) 1 Logical name Octet-string 0-x:24.1.0.255
The M-Bus Master Setup class is a new class that is not specified in the current version of the Blue Book [1], but it will be defined in the next version. The specification of this class can be found in Appendix A1.
M-Bus port Setup (Class ID: 25) 1 2 3 4 5 logical_name default_baud avail_baud addr_state bus_address octet-string enum enum enum unsigned 0-0:24.0.0.255 Value = 3; 2400 baud Value = 3; 2400 baud; communication is fixed to 2400 baud Value = 1 only relevant if the port also can act as slave
7.2
Identification numbers
Device ID 1 (Class ID: 1) Serial number (4 instances, one per channel) 1 2 Logical name Value Octet-string Octet-string[16] 0-x:96.1.0.255 (x=channel number (1..4)) Mapping to use cases and/or M-Bus unclear
Device ID 1 (Class ID: 1) Equipment identifier (4 instances, one per channel) 1 2 Logical name Value Octet-string Octet-string[48] 0-x:96.1.1.255 (x=channel number (1..4)) Mapping to use cases and/or M-Bus unclear
Page 43 of 68
7.3
Registers
M-Bus Master Value (Class ID: 4) Instance specific (4 instances, one per channel) 1 Logical name Octet-string 0-x:24.2.e.255 (x=channel number (1..4), e=instance number (1..4), 16 instances in total: 4 channels with 4 instances per channel) set at installation time in the E-meter status of M-Bus device (Mapping to M-Bus command ?) time of last successful readout
2 3 4 5
Value scaler_unit status capture_time
double-long-unsigned scal_unit_type octet-string octet-string
7.4
Profiles (hourly)
M-Bus Master Load profile with period 1 (Class ID: 7) Hourly interval readings of M-Bus devices (4 instances, one per channel) 1 2 3 Logical name buffer capture_objects Octet-string array Array 0-x:24.3.0.255 (x=channel number (1..4)) The buffer must be filled monotonously, i.e. no irregular entries are allowed {8,0-0:1.0.0.255,2,0}; {1,0-0:96.10.20.255,2,0} {4, 0-b:24.2.e.255,2,0} ( =clock;AMR profile status;M-Bus master value object) AMR profile status see paragraph 4.2.5 3600, every hour 1 or 3 (unsorted (FIFO) or sorted (largest)) none or {8,0-0:1.0.0.255,2,0}(unsorted or sorted by clock) 240 (10 days)
4 5 6 7 8
Page 44 of 68
7.5
Event Log (Class id = 7)
M-Bus Event Log (Class ID: 7) M-bus event log containing errors and alarms 1 2 Logical name buffer Octet-string array 0-0:99.98.3.255 The buffer must be filled monotonously, i.e. no irregular entries are allowed = exactly one entry per capture period {8,0-0:1.0.0.255,2,0}; {1,0-096.11.e.255,2,0} ( = clock;event code) M-bus event codes must be defined, see 4.2.1 0, asynchronously 1, unsorted (FIFO) None, unsorted 10 Optional, has no meaning
capture_objects
Array
4 5 6 7 8 1 2
capture_period sort_method sort_object entries_in_use profile_entries Reset Capture
7.6
Disconnector (Control and Log)
M-Bus Master Disconnect Control (Class ID: 70) Controls the opening and closing of an M-Bus disconnector (e.g. gas valve) (4 instances, one per channel) 1 2 3 4 1 2 Logical name output_state control_state control_mode remote_disconnect remote_connect Octet-string boolean enum enum 0-x:24.4.0.255 (x=channel number (1..4))
The Disconnect Control class is a new class that is not specified in the current version of the Blue Book [1], but it will be defined in the next version. The specification of this class can be found in 0.3.
Page 45 of 68
M-Bus Master Control log (Class ID: 7) Changes of the states related to the disconnect control are recorded (open, close) (4 instances, one per channel) 1 2 3 Logical name buffer capture_objects Octet-string array Array 0-x:24.5.0.255 (x=channel number (1..4)) {8,0-0:1.0.0.255,2,0}; {1, 0-0:96.11.e.255, 2, 0} ( =clock;control event code) Event codes must be defined (paragraph 4.2.1) 0, asynchronously 1, unsorted (FIFO) None, unsorted 10
4 5 6 7 8
Page 46 of 68
APPENDIX A: A.1
SPECIFICATION OF NEW DLMS CLASSES
M-Bus Master Setup Interface Class (class_id:72)
This interface class allows using M-Bus interface which is configured with M-Bus Port Setup Interface class (class_id:25) for the purpose of M-Bus Master for one M-Bus Slave Device. In this case M-Bus Slave Device can be installed, deinstalled and values from Slave Device can be captured periodically into M-Bus Master Value objects. M-Bus Slave is identified with Primary Address, Identification Number, Manufacturer Id. etc. Capturing M-Bus values from the M-Bus Slave Device is configured with capture_definition and contains list of data identifications (DIB, VIB) for M-Bus Slave device. For more details about M-Bus Application Layer see EN 13757-3.
M-Bus Master Setup Attribute(s) 1. 2. 3. 4. 5. 6. 7. 8. 9. logical_name mbus_port_reference capture_definition capture_period primary_address identification_number manufacturer_id version device_type (static) (static) (static) (static) (dynamic) (dynamic) (dynamic) (dynamic) (dynamic) (dynamic) (dynamic) (dynamic)
0..n Data type octet-string octet-string array double-longunsigned unsigned double-longunsigned long-unsigned unsigned unsigned unsigned unsigned unsigned m/o O O O O O O O
class_id = 72, version = 0 Min. Max. Def. Short name x x + 0x10 x + 0x18 x + 0x20 x + 0x28 x + 0x30 x + 0x38 x + 0x40 x + 0x48 x + 0x50 x + 0x58 x + 0x60
10. access_number 11. status 12. alarm Specific methods (if required) 1. 2. 3. 4. 5. 6. 7. slave_install slave_deinstall capture reset_alarm synchronize_clock data_send set_encryption_key
x + 0x68 x + 0x70 x + 0x78 x + 0x80 x + 0x88 x + 0x90 x + 0x98
Page 47 of 68
Attribute description
logical_name Mbus_port_reference Capture_definition Identifies the M-Bus Master object instance. For logical name(s), see chapter 7.1 Provides reference to M-Bus Port Setup object which is used to communicate with Slave Device. Provides the capture_definition for slave devices. Array capture_definition_element
capture_definition_element ::= structure { data_information_block octet-string, value_information_block octet-string } Note: data_information_block and value_information_block corresponds to Data Information Block and Value Information Block described in EN 13757-3 in Clause 6. >= 1: Automatic capturing assumed. Specify the capture period in seconds 0: No automatic capturing; capturing is triggered externally or capture events occur asynchronously. primary_address Note: Elements are taken from Data Header of Variable Data Respond (See EN 137573 Clause 5) The Identification Number is either a fixed fabrication number or a number changeable by the customer, coded with 8 BCD packed digits (4 Byte), and which thus runs from 00000000 to 99999999. It can be preset at fabrication time with a unique number, but could be changeable afterwards, especially if in addition an unique and not changeable fabrication number (DIF = Och, VIF = 78h, see 7.2) is provided. Note: Element taken from Data Header of Variable Data Respond (See EN 13757-3 Clause 5.4) The field manufacturer is coded unsigned binary with 2 bytes. This manufacturer ID is calculated from the ASCII code of EN 62056-21 manufacturer ID (three uppercase letters) Note: Element is taken from Data Header of Variable Data Respond (See EN 13757-3 Clause 5.5) The field version specifies the generation or version of the meter and depends on the manufacturer. It can be used to make sure, that within each version number the identification # is unique. Note: Element is taken from Data Header of Variable Data Respond (See EN 13757-3 Clause 5.6) The device byte is coded according to Table 3 of EN 13757-3 Clause 5.7. Note: Element is taken from Data Header of Variable Data Respond (See EN 13757-3 Clause 5.7) The Access Number has unsigned binary coding, and is incremented (modulo 256) by one before or after each RSP-UD from the slave. Since it can also be used to enable private end users to detect an unwanted overfrequently readout of its consumption meters, it should not be resettable by any bus communication. Note: Element is taken from Data Header of Variable Data Respond (See EN 13757-3 Clause 5.8) The status byte is coded according to Table 4 and Table 5 of EN 13757-3 Clause 5.9. Note: Element is taken from Data Header of Variable Data Respond (See EN 13757-3 Clause 5.9) The alarm state is coded with data type D ( oolean, in this case 8 bit). Set bits signal alarm bits or alarm codes. The meaning of these bits is manufacturer specific. Note: Element is taken from alarm respond (See EN 13757-3 Annex D)
Capture_period
identification_number
manufacturer_id
version
device_type_identification
access_number
status
alarm
Page 48 of 68
Method description
slave_install(data) Installs Slave Device data long-unsigned (0)
slave_deinstall(data)
Deinstalls Slave Device data long-unsigned (0)
capture
Capture values from Slave Device data long-unsigned (0)
reset_alarm
Reset alarm state of the Slave Device data long-unsigned (0)
synchronize_clock
Synchronize clock of the Slave Device with Server Clock. Data long-unsigned (0)
data_send
Send Data to the Slave Device data array data_definition_element
data_definition_element ::= structure { data_information_block octet-string, value_information_block octet-string CHOICE { --simple data types null-data [0], bit-string [4], double-long [5], double-long-unsigned [6], octet-string [9], visible-string [10], integer [15], long [16], unsigned [17], long-unsigned [18], long64 [20] long64-unsigned [21], float32 [23], float64 [24] } } set_encryption_key Set Encryption Key to be used with Slave Device. Data octet-string (encryption_key)
Page 49 of 68
M-Bus Related OBIS Codes:

OBIS code MBUS related objects A MBUS Setup objects MBUS Master Setup objects MBUS Master Value objects
c
B Xa Xa X
a
C 24 24 24 24 24 24
D 0 1 2 3 4 5
E 0 0 Yb 0 0 0
0 0 0 0 0 0
MBUS Master Profile Generic objects MBUS Master Disconnect Control objects MBUS Master Control Log objects
a b
X X 0
x is equal to any value within the range. If only one object of each kind is instantiated, the value shall be 0.
y is equal to index of the captured value in accordance to index of capture_definition_element in capture_definition of MBUS Master Setup object
b
MBUS Master Value objects are instances of Extended Register class.
A.2
Limiter Interface Class (class_id:71)
This interface class allows defining a set of actions that are executed when the value of an attribute of monitored object Data, Register, Extended Register, Demand Register, etc. crosses the threshold value for at least minimal duration time. Threshold value can be normal or emergency threshold. Emergency threshold is activated with emergency profile defining activation start time, duration and emergency profile id. Emergency profile id is mathed to emergency profile group id and enable emergency activation only for specific emergency group.
Limiter Attribute(s) 1. logical_name 2. 3. 4. 5. 6. 7. 8. 9. monitored_value threshold_active threshold_normal threshold_emergency min_over_threshold_duration min_under_threshold_duration emergency_profile emergency_profile_group_id
(static) (static) (dyna mic) (static) (static) (static) (static) (static) (static) (dyna mic) (static)
0..n Data type octet-string value_definition threshold threshold threshold double-longunsigned double-longunsigned emergency_profile_t ype long-unsigned boolean
class_id = 71, version = 0 Min. Max. Def.
Short name x x + 0x08 x + 0x10 x + 0x18 x + 0x20 x + 0x28 x + 0x30 x + 0x38 x + 0x40 x + 0x48 x + 0x50
10. emergency_profile_active 11. actions Specific methods (if required) 1. 2. 3.
m/o
Page 50 of 68
logical_name monitored_value Identifies the Limiter object instance. For logical name(s), see chapter 6.7 Defines which attribute of an object is to be monitored. Only values with simple data types are allowed. value_definition ::= structure { class_id: long-unsigned, logical_name: octet-string, attribute_index: integer } Provides the active threshold value to which the attribute of the referenced register is compared. data threshold
threshold_active
threshold_normal
threshold: The threshold is of the same type as the monitored attribute of the referenced object. Provides the threshold value to which the attribute of the referenced register is compared when normal operation. data threshold
threshold_emergency
threshold: The threshold is of the same type as the monitored attribute of the referenced object. Provides the threshold value to which the attribute of the referenced register is compared when emergency profile is active. data threshold
min_over_threshold_duration
threshold: The threshold is of the same type as the monitored attribute of the referenced object. Defines minimal over threshold duration in seconds required to execute the over threshold action.
min_under_threshold_duration Defines minimal under threshold duration in seconds required to execute the under threshold action.
emergency_profile
Contains emergency profile id, emergency activation time and emergency duration to define emergency profile. Emergency profile is activated when emergency profile id is matched with emergency_profile_group_id attribute and time matches emergency activation time and emergency duration fields. Active emergency profile is indicated in emergency_profile_active attribute. emergency_profile ::= emergency_profile_type emergency_profile_type ::= structure { emergency_profile_id: long-unsigned, emergency_activation_time: octet-string, emergency_duration: double-long-unsigned }
emergency_profile_group_id
Defines group id of emergency profile. When emergency profile is set it is compared with emergency profile id. Emergency profile can activate only if they match. Indicates active emergency profile. Defines the scripts to be executed when the monitored value crosses the threshold for minimal duration time. action_set ::= structure {
emergency_profile_active actions
Page 51 of 68
action_over_threshold: action_item, action_under_threshold: action_item } where: - action_over_threshold defines the action when the attribute value of the monitored value crosses the threshold in upwards direction and remains over threshold for minimal over threshold duration time. - action_under_threshold defines the action when the attribute value of the monitored value crosses the threshold in the downwards direction and remains under threshold for minimal under threshold duration time. action_item ::= structure { script_logical_name: octet-string, script_selector: long-unsigned }
A.3
Disconnect control (class_id:70)
The disconnect control class manages an internal or external disconnect unit (e.g. electricity breaker, gas valve) in order to connect or disconnect the premises of the consumer. To define the behaviour of the disconnect unit under different operating conditions, the control mode can be set. Disconnect and reconnect can be requested from the following sources: Remotely : Remote commands via communication remote_reconnect remote_disconnect manual_reconnect manual_disconnect local_disconnect local reconnection is not possible without manual intervention of the user
Manually : Push button(s)
Locally: Local control functions, e.g. limiter, prepayment, etc.
The disconnect control doesn't feature a memory, i.e. any consecutive trigger is executed immediately.
Disconnect Control Attribute(s) 1. 2. 3. 4. logical_name output_state control_state control_mode (static) (dyn.) (dyn.) (static) 0..n Data type octet-string boolean enum enum class_id = 70, version = 0 Min. Max. Def. Short name x x + 0x08 x + 0x10 x + 0x18
Specific method(s) 1. 2. remote_disconnect() remote_reconnect() m m x + 0x20 x + 0x28
Page 52 of 68
logical_name output_state
Identifies the disconnect control object instance. For logical name(s), see chapter 6.6 and 7.6
Shows the actual state of the disconnect unit output, i.e. if a relay or a valve is open or closed.
boolean control_state
TRUE = connected FALSE = disconnected
Shows the internal state of the disconnect control object. (0) = disconnected enum
The output_state is set to FALSE and the consumer is disconnected. (1) = (2) = connected The output_state is set to TRUE and the consumer is connected. ready_for_reconnection The output_state is set to FALSE and the consumer is disconnected. A reconnection is only possible via manual operation, i.e. pressing a push button. No remote reconnection is possible from this state.
Page 53 of 68
The state diagram below shows the 3 control states and the possible changes among each other.
disconnected (0)
remote_reconnect (if control_mode = 2,4) remote_disconnect (if control_mode <> 0)
remote_reconnect (if control_mode = 1,3) manual_reconnect
ready_for_ reconnection (2)
manual_disconnect (if control mode = 1,2)
local_disconnect
connected (1)
control_mode
Configures the behaviour of the disconnect control object for all triggers
enum
(0) = (1) =
The disconnect control object is always in 'connected' state, no disconnection is possible at all. Remote disconnection is possible and forces the disconnect control object into 'disconnected' state. Remote reconnection forces the disconnect control object into 'ready_for_reconnection' state and a manual reconnection must be performed. Manual disconnection and reconnection are both possible. Manual disconnection forces the disconnect control object into 'ready_for_reconnection' state. From there a manual reconnection is possible, i.e. by pressing a push button. Local disconnection is possible and forces the disconnect control object directly into 'ready_for_reconnection' state. From there a manual reconnection must be performed.
(2) =
Remote disconnection is possible and forces the disconnect control object into 'disconnected' state. Remote reconnection directly reconnects the disconnect control object without manual intervention. Manual disconnection and reconnection are both possible. Manual disconnection forces the disconnect control object into 'ready_for_reconnection' state. From there a manual reconnection is possible, i.e. by pressing a push button. Local disconnection is possible and forces the disconnect control object directly into 'ready_for_reconnection' state. From there a manual reconnection must be performed.
(3) =
Remote disconnection is possible and forces the disconnect control object into 'disconnected' state. Remote reconnection forces the disconnect control object into 'ready_for_reconnection' state and a manual reconnection must be performed. Manual disconnection is not possible. A manual reconnection after a
Page 54 of 68
remote or local disconnection can be performed. Local disconnection is possible and forces the disconnect control object directly into 'ready_for_reconnection' state. From there a manual reconnection must be performed. (4) = Remote disconnection is possible and forces the disconnect control object into 'disconnected' state. Remote reconnection directly reconnects the disconnect control object without manual intervention. Manual disconnection is not possible. A manual reconnection after a local disconnection can be performed. Local disconnection is possible and forces the disconnect control object directly into 'ready_for_reconnection' state. From there a manual reconnection must be performed. Local disconnection is always possible, To suppress local disconnection, the corresponding trigger must be inhibited.
Method description
The methods can be used via any communication channel to change the actual control state of the disconnect control object. The command is executed immediately. The control state after execution of a method depends on the control_mode attribute. The methods can be protected individually to restrict the access to the disconnect control object to authorised users only or to inhibit the access at all. If a method can't be executed an access error (read/write denied) is returned. This also happens if the control_mode is set to 0 and no connection or disconnection is possible at all.
remote_disconnect () remote_reconnect () Forces the disconnect control object into 'disconnected' state if remote disconnection is enabled (control mode <> 0). Forces the disconnect control object into the 'ready_for_reconnection' state if a direct remote reconnection is disabled (control mode = 1,3). Forces the disconnect control object into the 'connected' state if remote reconnection is enabled (control mode = 2,4).
Page 55 of 68
APPENDIX B: B.1
PLC SETUP CLASSES
S-FSK Phy&MAC setup (class_id: 50)
An instance of the S-FSK Phy&MAC setup class stores the data necessary to set up and manage the physical and the MAC layer of the PLC S-FSK lower layer profile.
S-FSK Phy&MAC setup Attribute(s) 1. 2. 3. 4. 5. 6. 7. 8. 9. logical_name initiator_electrical_phase delta_electrical_phase max_receiving_gain max_transmitting_gain frequencies mac_address mac_group_addresses repeater (static) (static) (dyn.) (static) (static) (static) (dyn.) (static) (static) (dyn.) (dyn.) (dyn.) (dyn.) (dyn.) 0n Data type octet-string unsigned enum unsigned unsigned frequencies_type long-unsigned array enum boolean unsigned unsigned long-unsigned boolean m/o 1 FFE 0 0 2 6 class_id = 50, version = 0 Min. Max. Def. Short name x x + 0x08 x + 0x10 x + 0x18 x + 0x20 x + 0x28 x + 0x30 x + 0x38 x + 0x40 x + 0x48 x + 0x50 x + 0x58 x + 0x60 x + 0x68
10. repeater_status 11. credit_fields 12. min_delta_credit 13. initiator_mac_address 14. synchronization_locked Specific methods
logical_name initiator_electrical_phase Identifies the S-FSK Phy&MAC setup object instance. Holds the MIB variable initiator-electrical-phase (variable 18) specified in IEC 61334-4-512 sub-clause 5.8. It is written by the client system to indicate the phase to which it is connected. The default value is 0. It can only take three values: 0, 1 and 2. delta_electrical_phase Holds the MIB variable delta-electrical-phase (variable 1) specified in IEC 61334-4-512 subclause 5.2 and IEC 61334-5-1 sub-clause 3.5.5.3. It indicates the phase difference between the client's connecting phase and the server's connecting phase. The following values are predefined: 0: Not defined: the server is temporarily not able to determine the phase difference; 1: the server system is connected to the same phase as the client system; 2: the phase difference between the server's connecting phase and the client's connecting phase is equal to 60 degrees; 3: the phase difference between the server's connecting phase and the client's connecting phase is equal to 120 degrees; 4: the phase difference between the server's connecting phase and the client's connecting phase is equal to 180 degrees; 5: the phase difference between the server's connecting phase and the client's connecting phase is equal to -120 degrees; 6: the phase difference between the server's connecting phase and the client's connecting phase is equal to 60 degrees.
Page 56 of 68
max_receiving_gain
Holds the MIB variable max-receiving-gain (variable 2) specified in IEC 61334-4-512 subclause 5.2 and IEC 61334-5-1 sub-clause 3.5.5.3. Corresponds to the maximum allowed gain bound to be used by the server system in the receiving mode. The default unit is dB.
max_transmitting_gain
Holds the value of the max-transmitting-gain. Corresponds to the maximum attenuation bound to be used by the server system in the transmitting mode. The default unit is dB.
frequencies
Contains frequencies required for S-FSK modulation. frequencies_type structure
{ mark_frequency space_frequency }
The default unit is Hz. mac_address Holds the MIB variable mac-address (variable 3) specified in IEC 61334-4-512 sub-clause 5.3 and IEC 61334-5-1 sub-clause 4.3.7.6. NOTE MAC addresses are expressed on 12 bits.
double-long-unsigned, double-long-unsigned
Contains the value of the physical attachment (MAC address) associated to the local system. In the unconfigured state, the MAC address is NEW-address. This attribute is locally written by the CIASE when the system is registered (with a Register service). The value is used in each outgoing or incoming frame. The default value is "NEWaddress". This attribute is set to NEW: by the MAC sub-layer, once the time-out-not-addressed delay is exceeded; when a client system resets the server system. See the S-FSK Active initiator IC in Clause 0.
When this attribute is set to NEW: the system loses its synchronisation (function of the MAC-sublayer); the mac_group_address attribute is reset (array of 0 elements); the system automatically releases all AAs which can be released.
The predefined MAC addresses are shown in

Table 1. mac_group_address Holds the MIB variable mac-group-address (variable 4) specified in in IEC 61334-4-512 subclause 5.3 and IEC 61334-5-1 sub-clause 4.3.7.6. Contains a set of MAC group addresses used for broadcast purposes. array mac-address mac-address long-unsigned
The ALL-configured-address, ALL-physical-address and NO-BODY addresses are not included in this list. These ones are internal predefined values. This attribute shall be written by the initiator using DLMS services to declare specific MAC group addresses on a server system. This attribute is locally read by the MAC sublayer when checking the destination address field of a MAC frame not recognized as an individual address or as one of the three predefined values (ALL-configured-address, ALL-physical-address and NO-BODY). repeater Holds the MIB variable repeater (variable 5) specified in in IEC 61334-4-512 sub-clause 5.3 and IEC 61334-5-1 sub-clause 4.3.7.6. Holds the information whether the server system effectively repeats all frames or not.
enum
(0) never repeater (1) always repeater
Page 57 of 68
(2) dynamic repeater If the repeater variable is equal to 0, the server system should never repeat the frames. If it is set to 1, the server system is a repeater: it has to repeat all frames received without error and with a current credit greater than zero. If it is set to 2, then the repeater status can be dynamically changed by the server itself. NOTE The value 2 value is not specified in IEC 61334-4-512.
This attribute is internally read by the MAC sub-layer each time a frame is received. The default value is 1. repeater_status Holds the current repeater status of the device. boolean FALSE = no repeater
TRUE = repeater
credit_fields Holds a copy of the credit fields of the last MAC frame received by the meter. NOTE min_delta_credit See IEC 61334-5-1 Figure 10.
Holds the MIB variable min-delta-credit (variable 9) specified in in IEC 61334-4-512 subclause 5.3 and IEC 61334-5-1 sub-clause 4.3.7.6. NOTE Only the three least significant bits are used.
The Delta Credit (DC) is the subtraction of the Initial Credit (IC) and Current Credit (CC) fields of a correct received MAC frame. The delta-credit minimum value of a correct received MAC frame, directed to a server system, is stored in this attribute. The default value is set to the maximal initial credit (see IEC 61334-5-1 4.2.3.1 [6] for further explanations on the credit and the value of MAX_INITIAL_CREDIT). A client system can reinitialize this variable by setting its value to the maximal initial credit. initiator_mac_address Holds the MIB variable initiator-mac-address specified in IEC 61334-5-1 4.3.7.6. Its value is either the MAC address of the active-initiator or the NO-BODY address, depending on the value of the synchronisation_locked attribute (see below). See also IEC 61334-5-1 3.5.3, 4.1.6.3 and 4.1.7.2. NOTE If the value NO-BODY is written then the server mac_address (see the mac_address attribute) has to be set to NEW. synchronisation_locked Holds the MIB variable synchronization-locked (variable 10) specified in IEC 61334-4-512 sub-clause 5.3. Controls the synchronisation locked / unlocked state. See in IEC 61334-5-1 for more details. If the value of this attribute is equal to TRUE, the system is in the synchronisation-locked state. In this state, the initiator-mac-address is always equal to the MAC address field of the active-initiator MIB object. See attribute 2 of the S-FSK Active initiator IC. If the value of this attribute is equal to FALSE, the system is in the synchronisation-unlocked state. In this state, the initiator_mac_address attribute is always set to the NO-BODY value: a value change in the MAC address field of the active-initiator MIB object does not affect the content of the initiator_mac_address attribute which remains at the NO-BODY value. The default value of this variable shall be specified in the implementation specifications. NOTE In the synchronisation-unlocked state, the server synchronises on any valid frame. In the synchronisation locked state, the server only synchronises on frames issued or directed to the client system the MAC address of which is equal to the value of the initiator_mac_address attribute.
Page 58 of 68
Table 1 MAC addresses in the S-FSK profile

Address NO-BODY Local MAC Initiator Value 000 001FIMA-1 FIMALIMA
MAC group address All-configured NEW All Physical
LIMA + 1FFB FFC FFE FFF
NOTE MAC addresses are expressed on 12 bits. These addresses are specified in IEC 61334-5-1 sub-clauses 4.2.3.2, 4.3.7.5.1, 4.3.7.5.2 and 4.3.7.5.3. FIMA = First Initiator MAC address; C00 LIMA = Last Initiator MAC address; DFF
B.2
S-FSK Active initiator (class_id: 51)
An instance of the S-FSK Active initiator class stores the data of the active initiator. The active initiator is the client system, which has last registered the server system with a CIASE Register request. See IEC 61334-5-511 7.2.
S-FSK Active initiator Attribute(s) 1. 2. logical_name active_initiator (static) (dyn.) 0n Data type octet-string initiator_descriptor m/o x + 0x10 class_id = 51, version = 0 Min. Max. Def. Short name x x + 0x08
Specific methods 1. reset_NEW_not_synchronised
logical_name active_initiator Identifies the S-FSK Active initiator object instance Holds the MIB variable active-initiator (variable 15) specified in IEC 61334-4-512 sub-clause 5.6. Contains the identifiers of the active initiator which has last registered the system with a Register request. See IEC 61334-4-511 7.2. The Initiator system is identified with its System Title, MAC address and L-SAP selector: initiator-descriptor ::=structure
{ system_title MAC_address L-SAP_selector }

Unless otherwise specified in a system specification: File name: Author: Version: When the IEC 61334-4-32 LLC layer is used, SYSTEM-TITLE-SIZE = 6;
octet-string (SIZE(SYSTEM-TITLE-SIZE)), long-unsigned, unsigned
Page 59 of 68
When the HDLC based data link layer is used (IEC 62056-46, Green Book Clause 8), SYSTEM-TITLE-SIZE = 8; When the ISO/IEC 8802-2 LLC layer is used, SYSTEM-TITLE-SIZE = 16.
NOTE The system title of the initiator should have the same structure as the COSEM logical device name specified in DLMS UA 1000-1 sub-clause 4.1.8.2. If the System-Title field of this object is set to an octet string of 0s, it means that the system is not registered. The MAC-address element is used to update the initiator-mac-address MAC management variable when the system is configured in the synchronisation-locked state. See the specification of the initiator_mac_address and the synchronisation_locked attributes of the S-FSK Phy&MAC setup IC, sub-clause 0. As long as the server is not registered by an active initiator, the LSAP_selector field is set to 0 and the system_title field is equal to an octet string of 0s. The default value of the initiator-descriptor is: MAC_address = NO-BODY and L-SAP_selector = 0. system_title = octet-string of of 0s, the
The value of this attribute can be updated by the invocation reset_NEW_not_synchronised method or by the CIASE Register service.
Method description
reset_NEW_not_ synchronised (data) Holds the MIB variable reset-NEW-not-synchronised (variable 17) specified in IEC 613344-512 sub-clause 5.8. Allows a client system to reset the server system. The submitted value corresponds to a client MAC address. The writing is refused if the value does not correspond to a valid client MAC address or the predefined NO-BODY address. When this method is invoked, the following actions are performed: the system returns to the unconfigured state (UNC: MAC-address equals NEWaddress). This transition automatically causes the synchronisation lost (function of the MAC sub layer); the system changes the value of the active_initiator attribute: the MAC address is set to the submitted value, the LSAP selector is set to the value 0 and the System-Title is set to an octet-string of 0s. all AAs that can be released are released.
B.3
S-FSK MAC synchronisation timeouts (class_id: 52)
An instance of the S-FSK synchronisation timeouts class stores the timeouts related to the synchronization process.
S-FSK MAC synchronisation timeouts Attribute(s) 1. 2. 3. 4. 5. logical_name search_initiator_timeout synchronisation_confirmation_ timeout timeout_not_addressed timeout_frame_not_OK (static) (static) (static) (static) (static) 0n Data type octet-string long-unsigned long-unsigned long-unsigned long-unsigned m/o class_id = 52, version = 0 Min. Max. Def. Short name x x + 0x08 x + 0x10 x + 0x18 x + 0x20
Specific methods
logical_name Identifies the S-FSK synchronisation timeouts object instance.
Page 60 of 68
search_initiator_ timeout
This timeout supports the intelligent search initiator function described in Clause XXX. The timeout starts when the server receives the first frame with a valid initiator MAC address. Defines the value of the time, expressed in seconds, during which the server system is searching for the initiator with the strongest signal. During this timeout, all initiators, which may be heard by the servers, are expected to talk. After the expiry of this timeout, the server will accept a Register request from the initiator having provided the strongest signal and it will be locked to that initiator. If the value of the timeout is equal to 0, this means that the feature is not used.
synchronisation_ confirmation_timeout
Holds the MIB variable synchronisation-confirmation-timeout (variable 6) specified in IEC 61334-4-512 sub-clause 5.3 and IEC 61334-5-1 4.3.7.6. Defines the value of the time, expressed in seconds, after which a server system which just gets frame synchronised (detection of a data path equal to AAAA54C7 hex) will automatically lose its frame synchronisation if the MAC sublayer does not identify a valid MAC frame. The timeout starts after the reception of the first four bytes of a physical frame. The value of this variable can be modified by a client system. This time-out ensures a fast desynchronisation of a system, which has synchronised on a wrong physical frame. See IEC 61334-5-1 3.5.3 for more details. NOTE The default value of this variable should be specified in the implementation specifications. A value equal to 0 is equivalent to synchronisation_confirmation_timeout counter. cancel the use of the related
timeout_not_addressed
Holds the MIB variable timeout-not-addressed (variable 7) specified in IEC 61334-4-512 sub-clause 5.3 and IEC 61334-5-1 4.3.7.6. Defines the time, in minutes, after which a server system that has not been individually addressed: returns to the non configured state (UNC: MAC-address equals NEW-address): this transition automatically involves the loss of the synchronisation (function of the MAC sub layer) and releasing all AAs that can be released; loses its active initiator: the MAC address of the active-initiator is set to NO-BODY, the LSAP selector is set to the value 00 and the System Title is set to an octet-string of 0s.
Because broadcast addresses are not individual system addresses, the timer associated with the time-out-not-addressed delay ensures that a forgotten system will sooner or later return to the unconfigured state. It will be then discovered again. A forgotten system is a system, which has not been individually addressed for more than the "time-out-notaddressed" amount of time. NOTE The default value of this variable should be specified in the implementation specifications. A value equal to 0 is equivalent to cancel the use of the related time-out-not-addressed counter. timeout_frame_not_OK Holds the MIB variable time-out-frame-not-OK (variable 8), specified in IEC 61334-4-512 sub-clause 5.3 and IEC 61334-5-1 4.3.7.6. Defines the time, in seconds, after which a server system that has not received a properly formed MAC frame (incorrect NS field, inconsistent number of received sub frames, false Cyclic Redundancy Code checking) loses its frame synchronisation. The default value of this variable shall be specified in the implementation specifications. A value equal to 0 is equivalent to cancel the use of the related time-out-frame-not-OK counter.
Page 61 of 68
B.4
S-FSK MAC counters (class_id: 53)
An instance of the S-FSK counters class stores counters related to the frame exchange, transmission and repetition phases.
S-FSK MAC counters Attribute(s) 1. 2. 3. 4. 5. 6. 7. 8. logical_name synchronisation_register desynchronisation_listing broadcast_frames_counter repetitions_counter transmissions_counter CRC_OK_frames_counter CRC_NOK_frames_counter (static) (dyn.) (dyn.) (dyn.) (dyn.) (dyn.) (dyn.) (dyn.) 0n Data type octet-string array structure double-long-unsigned double-long-unsigned double-long-unsigned double-long-unsigned double-long-unsigned m/o 0 0 0 class_id = 53, version = 0 Min. Max. Def. Short name X x + 0x08 x + 0x10 x + 0x18 x + 0x20 x + 0x28 x + 0x30 x + 0x38
Specific methods
synchronisation_ register Holds the MIB variable synchronisation-register (variable 23), specified in IEC 61334-4512 sub-clause 5.8. array synchronization-couples ::= synchronization-couples structure
{
mac-address long-unsigned,
synchronisations-counter unsigned }
double-long-
This variable counts the number of synchronisation processes performed by the system. Processes that lead to a synchronisation loss due to the detection of a wrong initiator are registered. The other processes that lead to a synchronisation loss (time-out, Management Writing) are not registered. This variable provides a balance sheet of the different systems on which the server system is "potentially" able to synchronise. A synchronisation process is initialized when the Management Application Entity receives a MA_Sync.indication (Synchronisation State = SYNCHRO_FOUND) primitive from the MAC Sublayer Entity. This process is registered in the synchronisation-register variable only if the MA_Sync.indication (Synchronisation State = SYNCHRO_FOUND) primitive is followed by one of the three primitives: 1) 2) 3) MA_Data.indication(DA, SA, M_sdu) primitive; MA_Sync.indication (Synchronisation State = SYNCHRO_CONF, SA, DA) ; MA_Sync.indication(Synchronisation State = SYNCHRO_LOSS, Synchro Loss Cause = wrong_initiator, SA, DA).
NOTE The third primitive is only generated if the server system is configured in a synchronisation-locked state. See 0. Processes which lead to the generation of MA_Sync.indication (Synchronisation State = SYNCHRO_LOSS) primitives indicating synchronisation loss due to: the physical layer; the time-out-not-addressed counter; setting the mac_address attribute of the S-FSK Phy&MAC setup object to NEW; see 0; or invoking the reset_NEW_not_synchronized attribute of the S-FSK Active initiator object; see 0 (this is known as Management Writing)
Page 62 of 68
are not taken into account in this variable. For details on the MA_Sync.indication service primitive see IEC 61334-5-1 sub-clause 4.1.7.1. If the synchronisation process ends with one of the three primitives listed above, the synchronisation-register variable is updated by taking into account the SA and DA fields of the primitive. The updating of the synchronisation-register variable is carried out as follows: synchronisation_ register (continued) First, the Management Entity checks the SA and DA fields. If one of these fields corresponds to a client MAC address (CMA) the Entity: o checks if the client MAC address (CMA) appears in one of the couples contained in the synchronisation-register variable; If it appears, incremented; the related synchronizations-counter subfield is
If it does not appear, a new (mac-address, synchronizations-counter) couple is added. This couple is initialized to the (CMA, 1) value.
If none of the SA and DA fields correspond to a client MAC address, it is supposed that the system found its synchronisation reference on a DiscoverReport type frame. In that case, the mac-address which should be registered in the synchronizationregister variable is the predefined NEW value (0FFF). The updating of the synchronisation-register variable is carried out in the same way as it is done for a normal client MAC address (CMA).
When a synchronisations-counter field reaches the maximum value, it automatically returns to 0 on the next increment. The maximum number of synchronisation couples {mac-address, synchronisationscounter} contained in this variable should be specified in the implementation specifications. When this maximum is reached, the updating of the variable follows a First-In-First-Out (FIFO) mechanism: only the newest source MAC addresses are memorized. The default value of this variable is an empty array. desynchronisationlisting Holds the MIB variable desynchronisation-listing (variable 24), specified in IEC 61334-4512 sub-clause 5.8. desynchronisation_listing ::= structure
{
nb_physical_layer_desynchronisation double_long_unsigned; nb_time_out_not_addressed_desynchronisation double_long_unsigned;
nb_timeout_frame_not_OK double_long_unsigned; nb_write_request_desynchronisation double_long_unsigned; nb_wrong_initiator_desynchronisation double_long_unsigned; }
desynchronisation
This variable counts the number of desynchronisations that occurred depending on their cause. On reception of synchronisation loss notification, the Management Entity updates this attribute by incrementing the counter related to the cause of the desynchronisation. When one of the counters reaches the maximum value, it automatically returns to 0 on the next increment. The default value of this variable contains elements which are all equal to 0.
Page 63 of 68
broadcast_frames_ counter
Holds the MIB variable broadcast-frames-counter (variable 19) specified in IEC 61334-4512 sub-clause 5.8. array broadcast-couples
broadcast-couples
{
structure
source-mac-address long-unsigned, frames-counter }

It counts the broadcast frames received by the server system and issued from a client system (source-mac-address = any valid client-mac-address, destination-mac address = ALL-physical). The number of frames is classified according to the origin of the transmitter. The counter is incremented even if the LLC-destination-address is not valid on the server system. When the frames-counter field reaches its maximum value, it automatically returns to 0 on the next increment. The maximum number of broadcastcouples {source-mac-address, frames-counter} contained in this variable should be specified in the implementation specifications. When this maximum is reached, the updating of the variable follows a First-In- First-Out (FIFO) mechanism: only the newest source MAC addresses are memorized. repetitions_counter Holds the MIB variable repetitions-counter (variable 20) specified in IEC 61334-4-512 sub-clause 5.8. Counts the number of repetition phases. The repetition phases following a transmission are not counted. If the MAC sub-layer is configured in the no-repeater mode, this variable is not updated. The repetitions-counter measures the activity of the system as a repeater. A received frame repeated five times (from CC=4 to CC=0) is counted only once in the repetitions-counter since it corresponds to one repetition phase. The counter is incremented at the beginning of each repetition phase. When the repetitions-counter reaches the maximum value, it automatically returns to 0 on the next increment. The default value is 0. transmissions_counter Holds the MIB variable transmissions-counter (variable 21) specified in IEC 61334-4-512 sub-clause 5.8 Counts the number of transmission phases. A transmission phase is characterized by the transmission and the repetition of a frame. A repetition phase, which follows the reception of a frame is not counted. The transmission counter is incremented at the beginning of each transmission phase. A client system can write this variable to update the counter. When the transmissions-counter reaches the maximum value, it automatically returns to 0 on the next increment. The default value is 0. CRC_OK_frames_ counter Holds the MIB variable CRC-OK-frames-counter (variable 22) specified in IEC 61334-4512 sub-clause 5.8 Counts the number of frames received with a correct Frame Check Sequence Field. When the CRC-OK-frames counter field reaches the maximum value, it automatically returns to 0 on the next increment. The default value is 0. CRC_NOK_frames_ counter Counts the number of frames received with an incorrect Frame Check Sequence Field. When the CRC-NOK-frames counter field reaches the maximum value, it automatically returns to 0 on the next increment. The default value is 0.
double-long-unsigned
B.5
S-FSK IEC 61334-4-32 LLC setup (class_id: 55)
An instance of the S-FSK IEC 61334-4-32 LLC setup class holds parameters necessary to set up and manage the LLC layer as specified in IEC 61334-4-32.
S-FSK IEC 61334-4-32 LLC setup Attribute(s) 1. 2. 3. logical_name max_frame_length reply_status_list (static) (static) (dyn.) 0n Data type octet-string unsigned array 3 242 128 class_id = 55, version = 0 Min. Max. Def. Short name x x + 0x08 x + 0x10
Page 64 of 68
Specific methods
m/o
logical_name max_frame_length Identifies the S-FSK IEC 61334-4-32 LLC setup object instance. Holds the length of the LLC frame in bytes. See IEC 61334-4-32 sub-clause 5.1.4. In the case of the S-FSK profile, as specified in 61334-5-1 sub-clause 4.2.2, the maximum value is 242, but lower values may be chosen due to performance considerations. reply_status_list Holds the MIB variable reply-status-list (variable 11) specified in 61334-4-512 subclause 5.4. Lists the L-SAPs that have a not empty RDR (Reply Data on Request) buffer, which has not already been read. The length of a waiting L-SDU is specified in number of sub frames (different from zero). The variable is locally generated by the LLC sub layer. reply_status_list ::= array of reply_status reply_status ::= structure
{
L-SAP-selector length-of-waiting-L-SDU unsigned, unsigned
}
length-of-waiting-LSDU in the case of the S-FSK profile is in number of sub-frames; valid values are 1 to 7.
B.6
S-FSK Reporting system list (class_id: 56)
An instance of the S-FSK Reporting system list class holds the list of reporting systems.
S-FSK Reporting system list Attribute(s) 1. 2. logical_name reporting_system_list (static) (dyn.) 0n Data type octet-string array m/o class_id = 56, version = 0 Min. Max. Def. Short name x x + 0x08
Specific methods
logical_name Identifies the S-FSK Reporting system list object instance.
Page 65 of 68
reporting_system_list
Holds the MIB variable reporting-system-list (variable 16) specified in 61334-4-512 sub-clause 5.7. array system-title system-title octet-string
Contains the system-titles of the server systems which have made a DiscoverReport request and which have not already been registered. The list has a finite size and it is sorted upon the arrival. The first element is the newest one. Once full, the oldest ones are replaced by the new ones. The reporting-system-list is updated: when a DiscoverReport CI_PDU is received by the server system (whatever its state: non configured or configured): the CIASE adds the reporting system-title at the beginning of the list, and verifies that it does not exist anywhere else in the list, if so it destroys the old one. A system-title can only be present once in the list; when a Register CI_PDU is received by the server system (whatever its state: non configured or configured): the CIASE checks the reporting-system list. If a system-title is present in the reporting-system-list and in the Register CI-PDU, the CIASE deletes the system-title in the reporting-system-list: this system is no more considered as a reporting system.
The number of elements in the array is limited to one.
B.7
ISO/IEC 8802-2 LLC Type 1 setup (class_id: 57)
An instance of the ISO/IEC 8802-2 LLC Type 1 setup class holds the parameters necessary to set up the ISO/IEC 8802-2 LLC layer in Type 1 operation.
ISO/IEC 8802-2 LLC Type 1 setup Attribute(s) 1. 2. logical_name max_octets_ui_pdu (static) (static) 0n Data type octet-string long unsigned m/o class_id = 57, version = 0 Min. Max. Def. Short name X x + 0x08
Specific methods
logical_name max_octets_ui_pdu Identifies the ISO/IEC 8802-2 LLC Type 1 setup object instance. Refer to the appropriate MAC protocol specification for any limitation on the maximum number of octets in a UI PDU. No restrictions are imposed by the LLC sublayer. However, in the interest of having a value that all users of Type 1 LLC may depend upon, all MACs must at least be capable of accommodating UI PDUs with information fields up to and including 128 octets in length. See ISO/IEC 8802-2 sub-clause 6.8.1 Maximum number of octets in a UI PDU.
Page 66 of 68
B.8
ISO/IEC 8802-2 LLC Type 2 setup Attribute(s) 1. 2. 3. 4. 5. 6. 7. 8. 9. logical_name transmit_window_size_k receive_window_size_rw max_octets_i_pdu_n1 max_number_transmissions_n2 acknowledgement_timer p_bit_timer reject_timer busy_state_timer (static) (static) (static) (static) (static) (static) (static) (static) (static) 0n Data type octet-string unsigned unsigned long unsigned unsigned long unsigned long unsigned long unsigned long unsigned m/o 1 1 127 127 1 1 class_id = 58, version = 0 Min. Max. Def. Short name x x + 0x08 x + 0x10 x + 0x18 x + 0x20 x + 0x28 x + 0x30 x + 0x38 x + 0x40
Specific methods
logical_name transmit_window_size_k Identifies the ISO/IEC 8802-2 LLC Type 2 setup object instance. The transmit window size (k) shall be a data link connection parameter that can never exceed 127. It shall denote the maximum number of sequentially numbered I PDUs that the sending LLC may have outstanding (i.e., unacknowledged). The value of k is the maximum number by which the sending LLC send state variable V(S) can exceed the N(R) of the last received I PDU. See sub-clause 7.8.4 Transmit window size, k. receive_window_size_rw The receive window size (RW) shall be a data link connection parameter that can never exceed 127. It shall denote the maximum number of unacknowledged sequentially numbered I PDUs that the local LLC allows the remote LLC to have understanding. It is transmitted in the information field of XID (see ISO/IEC 8802-2 5.4.1.1.2) and applies to the XID sender. The XID receiver shall set its transmit window (k) to a value less than or equal to the receive window of the XID sender to avoid overrunning the XID sender. See ISO/IEC 8802-2 sub-clause 7.8.6 Receive window size, RW. max_octets_i_pdu_n1 N1 is a data link connection parameter that denotes the maximum number of octets in an I PDU. Refer to the various MAC descriptions to determine the precise value of N1 for a given medium access method. LLC itself places no restrictions on the value of N1. However, in the interest of having a value of N1 that all users of Type 2 LLC may depend upon, all MACs must at least be capable of accommodating I PDUs with information fields up to an including 128 octets in length. See ISO/IEC 8802-2 sub-clause 7.8.3 Maximum number of octets in an I PDU, N1. max_number_transmissions_n2 N2 is a data link connection parameter that indicates the maximum number of times that a PDU is sent following the running out of the acknowledgment timer, the P-bit timer, the reject timer, or the busy-state timer. See ISO/IEC 8802-2 sub-clause 7.8.2 Maximum number of transmissions, N2. acknowledgement_timer The acknowledgment timer is a data link connection parameter that shall define the time interval during which the LLC shall expect to receive an acknowledgment to one or more outstanding I PDUs or an expected response PDU to a sent unnumbered command PDU. See ISO/IEC 8802-2 sub-clause 7.8.1.1 Acknowledgement timer.
Page 67 of 68
p_bit_timer
The P-bit timer is a data link connection parameter that shall define the time interval during which the LLC shall expect to receive a PDU with the F bit set to 1 in response to a sent Type 2 command with the P bit set to 1. See ISO/IEC 8802-2 sub-clause 7.8.1.2 P-bit timer.
reject_timer
The reject timer is a data link connection parameter that shall define the time interval during which the LLC shall expect to receive a reply to a sent REJ PDU. See ISO/IEC 8802-2 sub-clause 7.8.1.3 Reject timer.
busy_state_timer
The busy-state timer is a data link connection parameter that shall define the timer interval during which the LLC shall wait for an indication of the clearance of a busy condition at the other LLC. See ISO/IEC 8802-2 sub-clause Busy-state timer.
B.9
ISO/IEC 8802-2 LLC Type 3 Setup Attribute(s) 1. 2. 3. 4. 5. 6. logical_name max_octets_acn_pdu_n3 max_number_transmissions_n4 acknowledgement_time_t1 receive_lifetime_var_t2 transmit_lifetime_var_t3 (static) (static) (static) (static) (static) (static) 0n Data type octet-string Long unsigned unsigned Long unsigned Long unsigned Long unsigned m/o class_id = 59, version = 0 Min. Max. Def. Short name X x + 0x08 x + 0x10 x + 0x18 x + 0x20 x + 0x28
Specific methods
logical_name max_octets_acn_pdu_n3 Identifies the ISO/IEC 8802-2 LLC Type 3 setup object instance N3 is a logical link parameter that denotes the maximum number of octets in an ACn command PDU. Refer to the various MAC descriptions to determine the precise value of N3 for a given medium access method. LLC places no restrictions on the value of N3. See ISO/IEC 8802-2 sub-clause 8.6.2 Maximum number of octets in an ACn command PDU, N3. max_number_transmissions_n4 N4 is a logical link parameter that indicates the maximum number of times that an ACn command PDU is sent by LLC trying to accomplish a successful information exchange. Normally, N4 is set large enough to overcome the loss of a PDU due to link error conditions. If the medium access control sublayer has its own retransmission capability, the value of N4 may be set to one so that LLC does not itself requeue a PDU to the medium access control sublayer. See ISO/IEC 8802-2 sub-clause 8.6.1 Maximum number of transmissions, N4. acknowledgement_time_t1 The acknowledgment time is a logical link parameter that determines the period of the acknowledgment timers, and as such shall define the time interval during which the LLC shall expect to receive an ACn response PDU from a specific LLC from which the LLC is awaiting a response PDU. The acknowledgment time shall take into account any delay introduced by the MAC sublayer and whether the timer is started at the beginning or at the end of the sending of the ACn command PDU by the LLC. The proper operation of the procedure shall require that the acknowledgment time be greater than the normal time between the sending of an ACn command PDU and the reception of the corresponding ACn response PDU. If the medium access control sublayer performs its own retransmissions and if the logical link parameter N4 is set to one to prevent LLC from re-queuing a PDU, then the acknowledgment time T1 may be set to infinity, making the acknowledgment timers unnecessary.
Page 68 of 68
See ISO/IEC 8802-2 sub-clause 8.6.4 Acknowledgement time, T1.
receive_lifetime_var_t2
This time value is a logical link parameter that determines the period of all of the receive variable lifetime timers. T2 shall be longer by a margin of safety than the longest possible period during which the first transmission and all retries of a single PDU may occur. The margin of safety shall take into account anything affecting LLCs perception of the arrival time of PDUs, such as LLC response time, timer resolution, and variations in the time required for the medium access control sublayer to pass received PDUs to LLC. If the destruction of the received state variables is not desired, the value of time T2 may be set to infinity. In this case the receive variable lifetime timer need not be implemented. See ISO/IEC 8802-2 sub-clause 8.6.5 Receive lifetime variable, T2.
transmit_lifetime_var_t3
This time value is a logical link parameter that determines the minimum lifetime of the transmit sequence state variables. T3 must be longer by a margin of safety than 1) 2) the logical link variable T2 at stations to which ACn commands are sent; and the longest possible lifetime of an ACn command-response pair. The lifetime of an ACn command-response pair must take into account the sum of processing time, queuing delays, and transmission time for the command and response PDUs at the local and remote stations.
If the destruction of the transmit state variables is not desired, the value of time T3 may be set to infinity. Note, if the receive variable lifetime parameter, T2 is set to infinity at remote stations to which ACn commands are sent, then the T3 parameter must be set to infinity at the local station. See ISO/IEC 8802-2 sub-clause 8.6.6 Transmit lifetime variable, T3.

286 - P3Dutch Smart Meter v2.1 Final P3

Uploaded by

Copyright:

Available Formats

286 - P3Dutch Smart Meter v2.1 Final P3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

286 - P3Dutch Smart Meter v2.1 Final P3

Uploaded by

Copyright:

Available Formats

P3 Companion Standard

Dutch Smart Meter specification and tender dossier

By order of: Reference: Date: Version: Status:

File name: Author: Version:

1.00 1.20 2.0 first draft 2.0 second draft

28-June-07 12-Sep-07 27-Nov-07

WG04 WG04 WG04

2.0 final draft

2.1 final H. Spelt 4-Feb-07 WG04 -

File name: Author: Version:

File name: Author: Version:

Appendix A: A.1 A.2 A.3

Appendix B: B.1 B.2 B.3 B.4 B.5

File name: Author: Version:

File name: Author: Version:

This companion standard focuses on the P3 interface for Electricity meters.

Independent Services Provider

File name: Author: Version:

Figure 1.2: DLMS/COSEM infrastructure P3

File name: Author: Version:

IEC 62056-21 Ed 1.0:2002

File name: Author: Version:

[3] [4] [5]

File name: Author: Version:

LOGICAL DEVICES AND ASSOCIATIONS, M-BUS MODELLING (GENERAL CONCEPT)

Physical device Management Logical device

File name: Author: Version:

COMMUNICATION PROFILES AND SERVICES, SECURITY

COSEM Application layer

COSEM Transport layer

DLMS/COSEM Transport layer TCP or UDP Port 4059

Data link layer

Figure 3.1: TCP/UDP based profile

File name: Author: Version:

double-long-unsigned Def=180 double-long-unsigned

boolean primary_DNS_address double-long-unsigned secondary_DNS_addre double-long-unsigned ss

COSEM Application Layer IEC 62056-53

COSEM IP Transport Layers IEC 62056-47 COSEM Wrapper TCP or UDP IP

Media Dependant Lower Layers

Data Link Layer Physical Layer

SNDCP LLC RLC MAC GSM Radio

File name: Author: Version:

Ethernet communication profile

COSEM Application Layer IEC 62056-53

COSEM IP Transport Layers IEC 62056-47 COSEM Wrapper TCP or UDP IP

Media Dependant Lower Layers

Data Link Layer Physical Layer

Figure 3.3: Ethernet communication profile

File name: Author: Version:

COSEM Application layer IEC 62056-53

COSEM Application layer IEC 62056-53

CIASE IEC 61334-5-511

PLC network management

CIASE IEC 61334-5-511

SAP To/From LLC

SAP To/From LLC

COSEM transport layer Transport IEC 62056-47 layer Wrapper layer

COSEM transport layer IEC 62056-47 Transport layer Wrapper layer

SAP Subnetwork Dependent Convergence Protocol: Protocol selection and segmentation