You are on page 1of 35

Smart metering technology

A description of the advanced features and fitment of


DLMS/COSEM to the above mentioned Smart Grid and
AMI features
Smart Grid drivers

• Asset management
• Energy efficiency
• Green energy
• Customer satisfaction
• Technology and Trade
• Social benefits
Smart Metering Requirements

Smart Metering Requirement DLMS/COSEM Support for feature


Self Healing – Anticipate, Detect Register Monitors, Thresholds, Load limiters,
and Respond Events & Alarms, Notification and Push, Controls,
Remote Firmware Upgrade

Consumer participation – ToD/ToU classes, Load Control, Import/Export


ToU/ToD, RTP/CPP, Demand Registers
Response, NetMetering

Resilience to Attack Access security (authentication), Data Transport


Security (encryption), Security/Tamper Events and
Logs, Event Notification, Remote Firmware
Upgrade

Generation options and Enabling Net Metering


Markets
Operating Efficiently Low communication overheads – Selective access
and Optimized encoding of packets
Self Description
Push function
Real time event reporting

RTC
Event Event code Push setup object
object

Event Log

PUSH to Head End System


Alarms and Events/Tamper

• Standard classes and objects to model


instantaneous(real time) alarm/event and to
log(historic) them chronologically
• Application layer service to report event/alarm
on a near real time basis
Data Push (IC:40)

• Push data to data center automatically


– At a scheduled time or periodically
– If a monitored threshold is exceeded (e.g. alarm
monitor)
– Triggered by an event (e.g. key pressed, meter
cover opened)
– On request of a client (e.g. wake-up).
Data Push
Push Setup Interface Class
Load Control and Management

• Demand response schemes require a Load


management system to interact with the
smart meters to connect/disconnect Loads
dynamically to handle peaks
• DLMS/COSEM provides a Disconnect Control
interface class to handle this requirement
Disconnect Control (IC:70)

• Disconnect control state machine has 3 states


• Disconnect and reconnect can be requested:
– Remotely, via a communication channel:
remote_disconnect, remote_reconnect;
– Manually, using e.g. a push button:
manual_disconnect, manual_reconnect;
– Locally, by a function of the meter, e.g. limiter,
prepayment: local_disconnect, local_reconnect.
Disconnect Control (IC:70)
Disconnect Control (IC:70)

• Interface Class Table


Limiter

• Similar to Monitors except that actions are


triggered only when the thresholds are
crossed for a minimum time duration
Authentication

• Lowest level authentication


• Low level authentication
• High level authentication
Authentication
authentication Mechanisms
HLS Authentication Mechanisms
Data transport security
Security policy (IC 64 version 0)

• Security is not imposed


• All messages authenticated
• All messages encrypted
• All messages authenticated and encrypted
Security policy (Version 1)
Security policy – optimal use of security

Attribute access rights Method access rights


(0) no_access, (0) no_access,
(1) read_only, (1) access,
(2) write_only, (2) authenticated_access
(3) read_and_write,
(4) authenticated_read_only,
(5) authenticated_write_only
(6)authenticated_read_and_
write
Security suite

• Security Suite Id - 0
• Authentication algorithm - AES-GCM-128
• Encryption algorithm - AES-GCM-128
• Key transport method - Key wrapping using AES-128
key
Ciphered PDU
Security Header field

Bit 3…0 - Security_Suite_Id


Bit 4 - indicates that the APDU is authenticated
Bit 5 - indicates that the APDU is encrypted
Bit 6 - 0 = Unicast, 1 = Broadcast
Bit 7 - Reserved, must be set to 0
Ciphering keys
• Dedicated key
• Global key
• Mater key
Cryptographic protection [AES-GCM]
Change key to Key Transfer
key2
Client
Cipher Action
Establish AA supporting AES Key Wrap key2 Prepare Action
request using key1
key transfer using Master key request
and AES GCM

Key transfer Action response Key transfer Action request

Server
Retry count, Locking period
Reset frame
counter
Update to key2
FAIL AES GCM
Cipher Action
response using Decipher
key1 and AES GCM Log result and FAIL
Result= AES Key
timestamp to
FAILED unwrap
Prepare Action Security log
response
FAIL Accept
Result= new key
PASS
Security setup
Remote Firmware upgrade

• Standard data model to remotely upgrade


and/or activate meter firmware
• Saves cost and time of utility by correcting
meter remotely and not visiting faulty meter
premise or replacing faulty meters
Time of Use Metering

• DLMS/COSEM provides a rich set of


standardized objects to handle multi-tariff ToU
metering.
• The primary interface classes in this regard are
– Activity Calendar
– Schedule
– Special Days table
– Single Action Schedule
– Script Table
Schedule and Calendar
Self-Description

• DLMS/COSEM devices are self-descriptive in


nature
– The object list of each association can be
downloaded by standard dlms/cosem clients
– Each association provides an application specific
virtual view of the smart meter
– The virtual views can provide different levels of
access to different applications
– DLMS/COSEM devices can advertise their
capabilities and negotiate the same with clients to
achieve the most optimum settings
Multiple communication media support

DLMS meter serial DLMS meter PLC DLMS meter IP DLMS meter
comm comm comm future comm

Data model Data model Data model Data model


IEC 62056-61,62 IEC 62056-61,62 IEC 62056-61,62 IEC 62056-61,62
Application Application Application Application
Layer Layer Layer Layer
IEC 62056-53 IEC 62056-53 IEC 62056-53 IEC 62056-53
HDLC LLC COSEM Transport
IEC 62056-46 IEC 61334-4-32 for IP
IEC 62056-47 Communication
Physical MAC+Phy Profile
IEC 62056-42 IEC 61334-5-1 TCP/UDP, IP layers

RS232/485 Power Line Carrier Ethernet Future


Optical port GPRS communication
PSTN/GSM modem PPP media
Low communication overhead

• Selective access – Ability to read/access part


of an attribute of an Interface Class – for
select classes with complex attributes
• Efficient data organization and presentation
using A-XDR encoding/ ASN.1 notation

You might also like