IEC 62056 DLMS/COSEM seminardlms.com/training/DLMS_Seminar_EUW2015_Extract__151124.pdf · IEC 62056...

device

languagemessagespecification

IEC 62056 DLMS/COSEM seminar

EUW 2015, Vienna 2nd November 2015

Győző Kmethy, DLMS UA, President Paul Fuchs, DLMS UA, General Secretary Victoria Varjú, DLMS UA, Support manager

Bas Roelofsen, DNV GL, Consultant

DLMS Seminar EUW 2015 Vienna 1

device


Agenda

• 13:00 Registration • 13:30 Introduction – the DLMS User Association and DNV GL • 13:45 The big picture • 14:15 New DLMS/COSEM functions • 15:00 Coffee break • 15:30 Improved efficiency • 15:45 Comprehensive end-to-end security • 16:15 New communication profiles • 16:30 Conformance testing: CTT 3.0 • 16:45 International standardization • 17:00 Q/A • 17:30 End of the program


device


INTRODUCTION: THE DLMS UA AND DNV GL


device


The DLMS User Association

Who we are • Community of users of the DLMS/COSEM standards

– Meter manufacturers, utilities, communication providers, system integrators, chip makers

• Non-profit Association registered in Zug, Switzerland • IEC and CENELEC technical / liaison partner

– Direct input to international standardization

• 325+ members from 50+ countries – Europe 182, Asia 115

• Close to 600 DLMS/COSEM compliant meter types, more than 100 manufacturers

• www.dlms.com


http://www.dlms.com/

device


The DLMS User Association

What do we do – services • pre-standardization for international standardization

– IEC TC13, IEC TC57, CEN TC294

• registration of standard elements – OBIS codes, COSEM interface class ids, protocol identifiers

• DLMS/COSEM compliance certification – Self-testing and third party testing

• technical support regarding the specification • training (in partnership with DNV GL) • promotion

– In standardisation organizations, in projects, with authorities


device


DLMS UA Milestones since 1997 1999: First implementations 2002: International standards published: IEC & CEN Conformance testing in place, Training seminars launched

2003 - 2005: Global spread - Solidly established in the C & I sector 2006 - 2010: IEC 62056 Ed. 2.0 2006

Specification enhanced for smart metering and gas metering Selected by M/441 and OPEN meter project as core standard for smart metering

2013 : New edition of the IEC 62056 series: ELECTRICITY METERING DATA EXCHANGE – THE DLMS/COSEM SUITE: Part 5-3 Application layer, part 6-1 OBIS, part 6-2 COSEM Communication profiles: part 7-6 HDLC, part 8-3 S-FSK PLC, part 9-7 TCP-UDP/IP

2014: Blue Book Edition 12, Green Book Edition 8 , being brought to the IEC EN/TS 52056 PRIME PLC, G3-PLC, AMC-SS PLC profiles, EN/TS 50568 B-PSK PLC profile

2015: Yellow Book Edition 5, Conformance Test Tool 3.0 IEC 62056-5-3 / 6-1 / 6-2 Edition 2, in line with GB Ed. 7 + Amd 3 and BB Ed. 11 Launching Edition 3 , in line with GB Ed. 8 and BB Ed. 12


device


DLMS UA Working groups

• WG Maintenance • development of new features to meet new market requirements • development and validation of the Conformance Test Tool (CTT) • 50+ members

• TF CEN metering • co-operation with CEN TC294: assignment of OBIS codes related to HCA,

gas, thermal energy and water metering • any other TC294 specific issues


device


DLMS UA membership

Associated members: • Organizations with mutual

interest

Regular members: • Joining fee: € 1,000 • Annual fee: € 1,000 • Mgmt. Commitee: 11 seats • Voting rights

Benefits: • Access to the specification: the „Coloured books” • Access to Conformance Test Tool and certification (Regular members) • Participation in the management and technical work • Technical support on the specification


http://dlms.com/images/knx.jpg

device


DNV GL Energy - Global service portfolio Training partner of the DLMS UA

Power testing, inspections and certification

Renewables advisory services

Renewables certification

Electricity transmission and distribution

Smart grids and smart cities

Energy market and policy design

Energy management and operations services

Energy efficiency services

Software

Policy Production Transmission & distribution Use


device


DNV GL metering services related to DLMS/COSEM

• Training – DLMS / COSEM Fundamentals & Details – Close cooperation with DLMS UA to build the training material – DNV GL’s experience in smart meter test projects

• Consultancy – Smart Meter Specifications (tender documents / ‘companion specifications’) – Test Case development – Test Procedures & Organizational Design

• Testing – Product Acceptance Testing against DLMS Companion Specs. (Madrid/Arnhem) – Conformance Testing (DLMS/COSEM over PRIME in Madrid, DLMS, IDIS in Arnhem) – Testing on ‘Neutral Ground’ – Test Tooling


device



device


DLMS/COSEM basics

Standard for meter data exchange: multi-utility, multi-media, all

application segments

Interoperability on device level by common “language”

100+ meter manufacturers have close to 600 meter types certified

DLMS UA Books / IEC 62056 / EN 13757-1

+ Companion specifications “how to use”

DLMS User Association 325+ members worldwide

Major smart metering projects worldwide,

millions of meters installed


device


DLMS/COSEM Vocabulary

• COSEM, “Companion Specification for Energy Metering” – Semantics: (meaning) of metering applications

• object model to present metering functions through the interfaces • objects work together to realize the various functions

• OBIS, “Object Identification System” – Naming system of the objects

• DLMS, “Device Language Message Specification” – Syntax: application layer protocol specifying services to access

COSEM objects • APDUs are specified in ASN.1 • Transfer syntax (encoding) is A-XDR, a more compact from of BER

• DLMS/COSEM – comprises the object model, the application layer protocol and the

communication profiles to transport the messages


device


DLMS/COSEM scope

All metering functions / use cases

All energy types

All market segments

All communication media


Metering

Commercial

Industrial, T&D

Billing Load profiles Instantaneous PQ

Residential

Control

device


The DLMS/COSEM 3 step approach

3. Transporting

C0 01 00 03 01 01 01 08 00 FF 02

2. Messaging

Protocol Services to access attributes and methods

Communication Protocol

Messages: Service_Id( Class_Id, Instance_Id, Attribute_Id/Method_Id )

Encoding: (APDU)

1. Modeling COSEM Interface Objects

Register 0 ..n Class_id=3, Version=0 Attribute(s) Data Type Min Max Def 1. logical_name (static) octet-string 2. value ( dyn .) instance specific 3. scaler -unit (static) scal _unit_type Method(s) m/o 1. reset o

• Data model, to view the meter functionality at its interface(s) • COSEM objects • OBIS Object Identification System

• Messaging method to communicate with the model and to represent data as a series of bytes (APDUs)

• Transportation method to carry the messages over the media between the meter and remote parties

Separation of model and protocol: “orthogonality”


device


MODELLING: COSEM


device


Object modelling

Attribute 1

Attribute 2

...

Attribute n

Method 1

...

Method n

NAME

Meaning

Data type

Value range

Any real-world things can be described by some attributes

Each attribute has a meaning, a data type and a value range

Methods allow performing operations on attributes

The NAME attribute identifies the data

...to read or write the attributes

...to invoke the methods

Attributes and methods constitute an object

Using the object means:

Clock Scheduler

Media setup Profile Register

Object Library

Association

17 DLMS Seminar EUW 2015 Vienna

device


Functional meter model with COSEM objects


Function Supporting interface classes (objects)

device


Example 1: Tarification model

Clock

logical_name

time

….

Activity calendar

calendar_name_act

season_profile_act::= array

{season_profile_name, season_start, week_name}

week_profile_table_act ::=array

{week_profile_name,Monday...Sunday}

logical_name

Script table

scripts ::= array {script_identifier,

actions {service_id, attribute /

method_id,param }

execute

logical_name

Register activation

register_assignment ::= array object_def

{class_id, log_name}

mask_list ::= array{mask_name,

index_list}

active_mask

logical_name

Register

logical_name

value

scaler_unit

Register

logical_name

value

scaler_unit

….

day_profile_table_act::= array {day_id, day_schedule

{start_time, script_logName, script_selector}

calendar_name_pass

season_profile_pass

week_profile_table_pass

day_profile_table_pass

activate_pass_clndr_time

activate_pass-calendar

add_register

add_mask

delete_mask

0-b:13.0.e.255 Tariffication Script table0-b:10.0.100.255

0-b:14.0.e.2550-b:1.0.e.255

Copies passive set to active setAuto activation

Remote or local invocation

Invokes the script that writes active_mask

attribute to make one of the masks active

The Registers listed in the active_mask

are activated

List of Registers that are managed by the Register

activation instance

COSEM model of remote tariff parametrization and

management (example)

WHEN WHAT TARGET

Special days table

logical_name

entries

….

….

0-b:11.0.e.255

device


Example 3: Object model of a simple meter

Σ Li Active power, C = 1

Measurement valuesElectricity, A = 1

Time integral 1, energy, D = 8

Data exchange control objectsAssociation objects, 0.0.40.0.x.255

Error object, 0.0.97.97.0.255

Number of power failures in all three phases, 0.0.96.7.0.255

Meter constants, 1.0.0.3.x.255Configuration program version number, 1.0.0.2.0.255Logical device name, 0.0.42.0.0.255

Σ Li A+, energy, current value, 1.0.1.8.0.255

Channel, B = 0

Communication channel setup objects

Parameters


device


MESSAGING: DLMS


device


ACCESS (unified service)

Messaging: The xDLMS services

• Common service set: – all objects can be accessed using

the same xDLMS services • SN referencing: named variables

– Read, write, Unconfirmed write • LN referencing via class-id and logical

name: – GET- SET- ACTION – Unified service: ACCESS

• Unsolicited: EventNotification, DataNotification, InfoReport

• LN referencing is more popular, as it is more powerful

• Requests identify the attribute / method and may carry data

• Responses supply the result and may carry data

• Requests and responses are paired by the client (invoke-id)

Name

Attribute 1

Object

...

Attribute n

Method(s)

Read

Write

UnconfWrite

G E T

S E T

A C T I O N

Interoperable and future proof 22 DLMS Seminar EUW 2015 Vienna

DataNotify

EventNotify

device


Building the messages

• services to access the objects

• and protocols to transport the information

Name

Attribute 1

Object

...

Attribute n

Method(s)

GET

SET

ACTION

Notification

... Data link layer

Physical layer

COMM. MEDIA

... Data link layer

Physical layer

COSEM Application layer

... Data link layer

Physical layer

Value Type / Length

Result (success)

Service

xDLMS APDU (GET-response)


C4010009060101480700FF

Block transfer

device


Application layer key features

• Two application service elements (ASEs) – Association Control: establish and release

client – server logical connections – xDLMS: messaging services to access the COSEM objects

• xDLMS features: – logical name and short name referencing – request / response and unsolicited services – selective access to part of complex attributes – multiple references: access multiple attributes with single request – invocation id and priority – transferring long APDUs: Block transfer (AL level segmentation) – Composable messages

• General protection • General block transfer


device


DLMS/COSEM standardization framework


Your project

device


The DLMS UA „Books”

Specifies the functional DATA MODEL comprising the COSEM interface classes and the OBIS codes for the various energy types. Internationally standardized by the IEC and CEN.

Specifies CONFORMANCE TEST plans for the COSEM object model and the protocol layers.

Describes the testing and certification process.

GLOSSARY OF TERMS helps to understand the specification. Internationally standardized by the IEC.

Specifies the higher layer PROTOCOLS and the DLMS/COSEM media-specific communication profiles, based on open ISO/IEC, Internet, NIST and FIPS standards. Internationally standardized by the IEC and CEN.


device


SOME KEY ATTRIBUTES OF DLMS/COSEM


device


DLMS/COSEM is OPEN

Specification is – freely available for DLMS UA members – internationally standardised: IEC, CENELEC, CEN – free of IP rights on any parts of the standards – the basis of several project-specific companion specifications

DLMS UA membership is open to anybody at nominal fee – participation in technical work – training and technical support – conformance test tool is available at equal and fair terms – forum for exchanging best practices

Used and supported worldwide


device


DLMS/COSEM is MANAGEABLE (ITU-T X.700 FCAPS classification)

Performance • selective access to large data • with-list requests for multiple data • compact encoding, templates (compact

data), compression • pull and push operation • negotiation of comm. parameters

Configuration • active / passive parameter sets • parameter monitoring and logs • image transfer and activation • negotiation of contexts and capabilities

Security • peer authentication, access rights • end-to-end, multi-layer protection of messages and data • security suites, security policies, key management • security logs

Fault management • alarms and alarm monitors • diagnostic information • error logs • event notification

Accounting • client user white listing and log • event logs • parameter logs


Management framework for Open Systems Interconnection (OSI) for CCITT (>>ITU-T) applications

device


DLMS/COSEM is INTEROPERABLE

• Interconnectivity: all, what has to be connected, can be connected (physical and abstract i.e. logical level)

• Interoperability: ability of diverse systems to work together – syntactic: ability to exchange data - protocols, formats – semantic: data exchange produces (agreed) useful results

• Interchangeability: elements providing the same function: functional IO • Reaching true interoperability

– open international standards – partnership and co-operation – discipline in following the standard – conformance testing – companion specifications make the choice between options, and specify

project specific elements that cannot be specified internationally – project specific interoperability testing


device


DLMS/COSEM: The standard of first choice

…in metering, we speak the same language

Data model, messaging method and protocols with advanced security for meter data exchange

Multi-utility and multi-media Self-descriptive, negotiable features Efficient data organization and access Meters of any complexity, from standard building blocks Covers smart metering use cases Open, international standard, widely supported Supports innovation and competition Future proof Testable interoperability


device


DLMS/COSEM IS EVOLVING - IT IS DESIGNED FOR THAT!


device


DLMS/COSEM evolutions • New functions to cover new use cases

– new COSEM interface classes, new DLMS services

• New mechanisms to boost efficiency – reduced encoding overhead – optimized messaging – use in constrained, battery operated devices, over low throughput

networks

• New, advanced security mechanisms – multi-stage protection – end-to-end protection – advanced key management

• New communication profiles – Web services, PLC, wireless


device


Main areas

Efficiency

Sending pre-defined data sets to templates: Compact data interface class Compact array encoding Compression

Security

End-to-end protection: Third party- client- server Multi-stage protection: peer authentication, message protection, COSEM data protection, Security policies and access modes Security suites, Cryptographic algorithms Symmetric and private/public keys, Public Key Certificates


Functionality

Accounting and payment function Composable services: encoding – protection – block transfer Push operation and DataNotification service ACCESS service: unified GET-SET-ACTION General Block Transfer with streaming and block recovery Messaging between the HES and the client: Web services and XML (IEC TC13 WG14) Gateway

New comm. profiles

DLMS/COSEM over PRIME PLC, G3-PLC, B-PSK PLC, AMC-SS PLC, B-PLC DLMS/COSEM over wired and wireless M-Bus

device


FUNCTIONAL EVOLUTION: ACCOUNTING AND PAYMENT


device


FUNCTIONAL EVOLUTION: ARBITRATOR


device


FUNCTIONAL EVOLUTION: COMPOSABLE MESSAGES


device


Composable messages • Earlier situation: APDUs have service specific ciphering and block

transfer mechanisms – not scalable (service specific variants would have to be added for all new services) – not available for new ACCESS, DataNotification APDUs – does not support E2E security with public key cryptography (ECDSA, ECD)

• Use case • decouple the steps of encoding, ciphering and block transfer • allow multiple protection layers by multiple parties

• Solution: • General-ciphering mechanism (symmetric key) • General-signing mechanism (private / public key) • General block transfer mechanism

• Can co-exist with service-specific ciphering and block transfer mechanisms


device


FUNCTIONAL EVOLUTION: PUSH OPERATION


device


Push operation

• Use case: alternative to pull operation – saves sending the requests

• Features – data set can be pre-defined, with selective access – triggered by pre-defined time, by events or by broadcast request – Push schedule, destination and sending method (the comm. media)

can be specified

• Object level tool: Push setup object • Messaging level tool: DataNotification xDLMS service


device


FUNCTIONAL EVOLUTION: ACCESS SERVICE


device



New xDLMS service: Access

• Use cases: – reduce number of exchanges: „One stop shopping”: all requests sent at once

• example: identify meter – read registers – read profiles – close billing period – synchronize clock

– allow many outstanding requests (important in mesh networks)

• responses may be delayed

– self-descriptive responses

• answer contains the question so that it can be stored as one entity

– improved efficiency: use service variants to eliminate unnecessary options

• E.g. Optional selective access parameters when not available

– time stamp in the APDUs (also makes the APDU unpredictable – good for security)

• Solution: – unified GET - SET - ACTION service with list

– processing the list of requests can be controlled: continue or break on error

– long-invoke-id-and-priority

device


FUNCTIONAL EVOLUTION: GENERAL BLOCK TRANSFER


device



General Block Transfer (GBT)

„Classical”, service specific block transfer: • different with each APDU • unidirectional: blocks are sent or

received • no streaming is available: reception of

each block has to be confirmed • does not support lost block recovery • ciphering is applied on the blocks

General Block Transfer: • can be applied to any APDU • bidirectional (useful with ACTION, ACCESS

transferring data in both directions) • streaming (several blocks without

confirmation) • supports lost block recovery • ciphering is applied to complete

unciphered APDU (less computation, less overhead)

(Application layer level segmentation; can be used together with lower layer segmentation)

Use case:

• lost block recovery (not supported with service-specific APDUs)

• bi-directional block transfer: can start sending a part of the response why parts of the request are still being received

• decrease number of turnarounds by streaming

• simplify implementation

• optimize for cryptograhic protection

device


FUNCTIONAL EVOLUTION: XML SCHEMA


device



COSEM APDU XML Schema

Use cases:

• using DLMS with Web services and SOAP interface

• (Simple Object Access Protocol)

• IEC/TS 62056-9-1, based on IEC 61968-1 and 61968-100 (TC57)

• Push COSEM messages in XML format

• encapsulate xDLMS messages in other messages e.g. emails

Base standards:

• ITU-T X.693: Information technology - ASN.1 encoding rules: XML Encoding Rules (XER)

• ITU-T X.694 Information technology – ASN.1 encoding rules: Mapping W3C XML schema definitions into ASN.1

device


FUNCTIONAL EVOLUTION: GATEWAY PROTOCOL


Gateway • Use case: access meters through a gateway connected to

two different networks


device


FUNCTIONAL EVOLUTION: SYSTEM BOUNDARIES


device


Smart metering, grids, homes

Smart homes

Local data transmission interface

IEC 62056-7-5

Substations (SCDADA)

IEC 61850 – COSEM mapping

IEC/TS 61850-80-4

Smart grids

ERP systems:

CIM – COSEM mapping

IEC 62056-6-9

Smart metering IEC 62056 DLMS/COSEM


device


DLMS/COSEM IS EVOLVING: HIGH EFFICIENCY


device


High efficiency

• Use case: – Implement DLMS/COSEM in constrained / battery operated devices – Use DLMS/COSEM over Low Throughput Networks – Lower communication costs


device


Concerns and methods

What How Efficient encoding A-XDR (more compact BER) Be focused Selective access to complex attributes Decrease /eliminate encoding overhead

Compact array, Compact data

Minimize number of turn-arounds With-list services, Access service Block transfer streaming Push operation

Optimize message length for medium

PDU length negotiation, block transfer, segmentation

Shorten messages Compression


device


DLMS/COSEM IS EVOLVING: COMPREHENSIVE SECURITY


device



Comprehensive end-to-end security

• End-to-End security: from the market participant to the meter

• Multi-stage: access control – message protection – data protection

• Security policies and access rights

• Cryptographic algorithms, security suites

• Key management

device


Comprehensive E2E security


device


Multi-stage protection

Application Association

+ + +

Identification

& Authenti-

cation

Message protection:

Security policy

Message protection:

Access rights

COSEM Data protection

DLMS Seminar EUW 2015 Vienna

• identification: system titles, client_user

• password authentica-tion (LLS) of client by server

• challenge – response authentication (HLS) of client and server

• protection requirements applicable to all messages

• authentication, encryption, digital signature

• may be different on request and responses

• local (attribute / method level) message protection requirements: may be different on requests and responses

• protection requirements of attribute values, method invocation and return parameters

• may be different on request and responses

57

The stonger has to be met

device



DLMS / COSEM security suites

• DLMS/COSEM uses security algorithms selected by NSA (National Security Agency) Suite B, using approved FIPS / NIST standards

58

device


DLMS/COSEM IS EVOLVING: NEW COMMUNICATION PROFILES


device


The IEC 62056 standardization framework

Comm. Profiles for Wide Area Networks

IEC 62056-9 series

Comm. Profiles for Neighbourhood

NetworksIEC 62056-8

series

Comm. Profiles for Local Networks

IEC 62056-3 / 6-7series

COSEM object-oriented data model

IEC 62056-6-2 COSEM interface classesIEC 62056-6-1 / EN 13757-1 OBIS Object Identification System

Services for connection establishment and for accessing COSEM objects

IEC 62056-5-3 DLMS/COSEM Application layer

Lower layer standards

IEC 62056 – IEC 61334 – EN – ITU-T – RFC


60

device


Smart metering system reference architecture


HDLC profile

TCP-IP profile LDTI profile

Euridis profile

M-Bus profile

S-FSK PLC profile

PRIME PLC profile

G-3 PLC profile

BPLC profile

AMC-SS PLC profile

B-PSK PLC profile Web services profile

device


DLMS/COSEM IS EVOLVING: NEW CONFORMANCE TEST TOOL


device


Why a new CTT

• To allow testing new features in the Books • New platform to support cryptographic security • More transparent presentation of the test cases

– Procedures invoked form the test cases • More transparency on the features tested: summary


• CTT 1 released in 2002, CTT 2.0 in 2007, CTT 2.5 in 2011, CTT 2.6 in 2014

• CTT3.0: in line with DLMS UA GB 7.3 and BB 11

• Released July 2015

• CTT3.1: in line with DLMS UA GB 8 and BB 12

• Beta testing of Package 1 planned in November 2015

device


Test report Test report No. 1600

Association objects

1.8.1.3 12345.67 CTI IUT info

COSEM compliant

Data link layer Application layer

COSEM

SECURITY

DLMS/COSEM specification

Abstract Test Suites

Executable Test Suites

Implementation Under Test

(IUT) DLMS Seminar EUW 2015 Vienna

64

CTT concept

device


HDLC data link layer test suite


Test suiteData link layer

using HDLC protocol

Test groupHDLC_FRAME

Test groupHDLC_ADDRESS

Test groupHDLC_NDM2NRM

Test groupHDLC_INFO

Test groupHDLC_NDMOP

Test groupHDLC_

FRAME_P

Test groupHDLC_

FRAME_N

Test groupHDLC_

ADDRESS_P

Test groupHDLC_

ADDRESS_N

Test groupHDLC_

NDM2NRM_P

Test groupHDLC_INFO_P

Test groupHDLC_INFO_N

Test groupHDLC_

NDMOP_N

Test cases Test cases Test cases Test cases Test cases Test cases Test cases Test cases

device


Application layer test suite


Test suiteDLMS/COSEM Application layer

Test groupAPPL_IDLE

Test groupAPPL_OPEN

Test groupAPPL_DATA_LN

Test groupAPPL_DATA_SN

Test groupAPPL_REL

Test groupAPPL_IDLE_N

Test groupAPPL_

DATA_SN_N

Test groupAPPL_REL_P

Test cases Test cases Test cases

Test groupAPPL_

DATA_LN_N

Test casesTest cases

device


COSEM object test algorithm


Test suiteCOSEM interface objects

COSEM_X_Y

Multiple references

Mandatory objects

What is tested:

- OBIS codes

- access rights

- attribute data structures

- some attribute values

device


Symmetric key security test suite


Test suiteDLMS/COSEM security Suite 0

(SYMSEC)

Test groupBasic capability

Test groupFrameCounter

Test groupKey transfer

Test groupSecure data exchange

Test groupSecure AA release

Test groupKey_Tx_P

Test cases Test cases Test casesTest cases

Test groupKey_Tx_N

Test groupDataX_P

Test cases Test cases

Test groupDataX_N

Test groupSecurity policy

Test cases Test cases

device


Certification form


69

• Certificates listed at www.dlms.com

• Meter type + LDN

• Manufacturer

• Test house

•Test information

•Test report is available from the manufacturer

device


CTT3.0 test report summary info: more transparency on what has been tested


70

device


INTERNATIONAL STANDARDIZATION


device


DLMS User Association

TC13, Electricity metering - WG14 – Meter data exchange,

IEC 62056 DLMS/COSEM suite - JWG 16: IEC 62056 COSEM – IEC

61968 CIM mapping

TC294, Non-electricity metering Communication systems for meters: EN 13757-1

TC13, Electricity metering WG02, Smart metering

TC 57, Power systems mgmt. - WG09: IEC 61334 PLC lower layer - WG10: IEC 62056 COSEM - IEC

61850 model mapping

DLMS UA in international standardization

M / 441 European Commission Smart Metering Standardization Mandate


device


COSEM object model - new developments

Blue Book Ed. 10:2010

COSEM-OBIS


COSEM-OBIS


COSEM-OBIS

IEC 62056- 6-2/6-1

Ed. 1:2013

COSEM - OBIS

IEC 62056- 6-2/6-1

Ed. 2:2015

COSEM - OBIS

IEC 62056- 6-2/6-1

Ed. 3:201X

COSEM - OBIS

• Image transfer, Sensor manager • Disconnect control, Limiter • Security setup V0 • M-Bus setup, S-FSK PLC setup

• Push setup • Parameter monitor • IPv6, Prime PLC and G3-PLC setup V0 • ZigBee® setup (to tunnel DLMS)

• Compact data • Association SN / LN new versions • Security setup V1 • Data protection (crypto) • Arbitrator • Payment metering • M-Bus server setup, Diagnostics • G3-PLC setup V1


device


DLMS/COSEM Application layer - new developments

Green Book Ed. 7:2009

COSEM-OBIS

Green Book Ed. 7.3:2013

COSEM-OBIS

Green Book Ed. 8:2014

COSEM-OBIS

IEC 62056- 5-3

Ed. 1:2013

DLMS/COSEM Application

layer

IEC 62056-5-3 Ed. 2: 2015


layer

IEC 62056- 5-3

Ed. 3:201X


layer

• Symmetric key cryptography

• S-FSK PLC profile

• DataNotification service (Push operation)

• General Block Transfer mechanism

• General protection APDUs

• Composable services: encoding – general protection – general block transfer

• ACCESS service (unified GET-SET-ACTION) • Public key cryptography • End-to-end security third party to meter • XML schema


device


IEC TC13 WG14 DLMS/COSEM standards Published standard Title / Status

IEC/TR 62056-1 Terms related to data exchange with metering equipment using DLMS/COSEM

IEC 62056-1-0: Ed.1: 2014 Smart metering standardization framework

IEC/TS 62056-1-1: 2015 Template for DLMS/COSEM communication profile standards 13/1643/DTS approved

IEC 62056-21 Ed.1: 2002 Direct local data exchange “FLAG protocol”

IEC 62056-3-1: Ed.1: 2013 Use of local area networks on TP with carrier signalling (non-DLMS, DLMS and DLMS/COSEM profile)

IEC 62056-42 Ed.1: 2002 Physical layer services and procedures for CO asynchronous data exchange

IEC 62056-46 Ed.1 :2002 Data link layer using HDLC protocol

IEC 62056-4-7 Ed.1 :2015 DLMS/COSEM transport layer

IEC 62056-5-3 Ed.2: 2015 DLMS/COSEM application layer (In line with DLMS UA GB Ed. 7 + Amd. 3) 13/1648/FDIS

IEC 62056-6-1 Ed.2: 2015 OBIS object identification system (In line with DLMS UA BB Ed. 11) 13/1649/FDIS

IEC 62056-6-2 Ed.2: 2015 COSEM interface classes (In line with DLMS UA BB Ed. 11) 13/1651/FDIS

IEC 62056-7-5 Ed.1: 2015 Comm. Profiles for local data exchange (13/1605/CDV approved)

IEC 62056-7-6 Ed.1 2013 The 3-layer, connection-oriented HDLC based communication profile

IEC 62056-8-3 Ed.1 :2013 Communication profile for PLC S-FSK neighbourhood networks

IEC/ 62056-9-1 Ed. 1 2015 Communication Profile using web-services to access a DLMS/COSEM Server via a COSEM Access Service (CAS) 13/1641/DTS

IEC 62056-9-7 Ed.1 :2013 Communication profile for TCP-UDP/IP networks

75 Appoved but not yet printed

device


IEC TC13 WG14 DLMS/COSEM projects

Future standard Title / Status Document

IEC 62056-3-1 Use of local area networks on TP with carrier signalling – Amendment to support Local Data Transmission IF

13/1589/RR

IEC 62056-5-3 Ed.3 DLMS/COSEM application layer (In line with GB 8) (CDV will be circulated in November)

IEC 62056-6-1 Ed. 3 OBIS object identification system (In line with BB12) (CDV will be circulated in November)

IEC 62056-6-2 Ed.3 COSEM interface classes (In line with BB12) (CDV will be circulated in November)

IECTS 62056-6-9 IEC 61869 CIM / IEC 62056 COSEM mapping 13/1647A/DTS

IEC 62056-7-3 Ed.1 DLMS/COSEM M-Bus wired & wireless profile 13/1644/NP approved

IEC 62056-8-6 Ed.1 IEC/ISO 12139-1 High speed PLC profile (Korea) draft CDV in Geneva

13/1557/CD

IEC 62056-8-20 Ed.1 RF mesh profile (USA) (IEEE 802.15.4, IPv6) 13/1607/CD


76

device


CLC TC13 WG02 Technical specifications (M/441)

TS number Title / Status Data of Availability

CLC/TS 52056-8-4 NB OFDM PRIME PLC communication profile 2015-04-24

CLC/TS 52056-8-5 NB OFDM G3 PLC communication profile 2015-04-24

CLC/TS 50568-4 SMITP lower layers 2015-04-24

CLC/TS 50568-8 SMITP B-PSK PLC communication profile incl. the original SMITP B-PSK PLC profile

2015-04-24

CLC/TS 50590 AMC-SS PLC lower layer s 2015-04-24

CLC/TC 52056-8-7 AMC_SS PLC communication profile 2015-04-24

Work completed! CLC/TS 50568 OSGP has to be re-launched


77

• Will be published as IEC TC13 standard

• Will be standardized by WG14 once the lower layers will have been standardized

• No technical agreement yet

device


[email protected] [email protected] [email protected]

Many thanks for your attention! Questions?

Forum at: http://www.dlms.com/faqanswers/index.html


mailto:[email protected]



IEC 62056 DLMS/COSEM seminardlms.com/training/DLMS_Seminar_EUW2015_Extract__151124.pdf · IEC 62056...

Documents

Transcript of IEC 62056 DLMS/COSEM seminardlms.com/training/DLMS_Seminar_EUW2015_Extract__151124.pdf · IEC 62056...