ERA PAPER ON

SMIP INTERFACES

& HIGH LEVEL

ARCHITECTURE

SIMON HARRISON

PROJECT ARCHITECT – SRSM PROJECT. SG1 & SG3 MEMBER.

STEG 09.12.10

BACKGROUND TO

PAPER

Requested from SMDG and DCG representatives

To provide clarity on the potential E2E architecture – with a

focus on the interfaces it could include

Also attempts to do some mythbusting on interoperability

Security is specifically out of scope(!)

Only a few comments received, none stating that content is

off base or fundamentally incorrect – generally very well

received

Baseline version now presented for Ofgem to publish

Companion paper – ‘DLMS Demystified’ also available

HIGH LEVEL

ARCHITECTURE

The fundamental interoperability requirement is,

subject to authorisation, for any User to interact with

any SMS component and vice versa, regardless of the

manufacturers or providers of individual systems and

components.

IHD

Gas Elec

WAN

User

User

User

DCCHE

Sec

HEDCC Functions

WANSMS

BASIC INTERFACES

Some are the same, some need to

be the same, some are potentially

out of scope

IHD

Gas Elec

WAN

User

User

User

DCCHE

Sec

HEDCC Functions

WANSMS

123

4

5

SIMPLIFIED

INTEROPERABILITY

Paper is for a non-technical audience

Uses examples to provide context

Describes intra-layer support

Physical Carrier

Transport/Protocol

Application

802.15.4 2.4GHz Radio

ZigBee

ZigBee Smart Energy

GPRS

TCP/IP

DLMS/COSEM

HAN ARCHITECTURE

Doesn’t specify an owner/controller

Doesn’t go beyond SMS components

Only addresses the requirements we know about

SMS

IHD

Gas Elec

WAN

HAN HAN

HAN HAN

Radio

Protocol

Data Format

Wire

SMS

IHD

Gas Elec

WANSmart

Device

Smart

Device

HAN HAN

HAN HAN

INTERFACE TO DCC

Focus is on the application layer, this is what matters most to

Users

DCC

User

User

User

WANSMS InternetTCP/IP

XML

Inte

rfa

ce

DTN

Proprietary

DTC/UKLink +

DCC FUNCTION

Attempts to illustrate that the DCC may

need to provide translation/bridging

between user and WAN interfaces (should

be transparent to users and components)

DCCUser

User

User

WAN

SMS InternetTCP/IP

XML

GPRSTCP/IP

DLMS COSEM

BoxWA

N

Inte

rfa

ce

DC

C I

nte

rfa

ce

Head

End

WAN/HAN/WAN

To move data between SMS components and the WAN

Application layer could tunnel from HAN to WAN and vice versa

802.15.4 2.4GHz Radio

ZigBee

ZigBee Smart Energy

GPRS

TCP/IP

DLMS/COSEM

WA

N I

nte

rfa

ce

HA

N I

nte

rfa

ce

802.15.4 2.4GHz Radio

ZigBee

DLMS over ZigBee

GPRS

TCP/IP

DLMS/COSEM

WA

N I

nte

rfa

ce

HA

N I

nte

rfa

ce

802.15.4 2.4GHz Radio

ZigBee

ZigBee Smart Energy

GPRS

TCP/IP

ZigBee SE over DLMSW

AN

In

terf

ac

e

HA

N I

nte

rfa

ce

OVERALL

ARCHITECTURE

Paper does not prescribe owners or solutions – illustrates

some known solution options for different interfaces

SMS

IHD

Gas Elec

WAN

HAN HAN

HAN HAN

DCCUser

User

User

WAN

Box

WA

N

Inte

rfa

ce

DC

C I

nte

rfa

ce

Head

End

HA

N

Inte

rfa

ce

WAN Interface

Physical Carrier(s) Transport(s) Application

GPRS, PSTN, PLC etc. Any supported DLMS COSEM

HAN Interface

Physical Carrier(s) Transport(s) Application

802.15.4 RF Homeplug 1.0

ZigBee Homeplug

ZigBee Smart Energy 1.x

DCC Interface

Physical Carrier(s) Transport(s) Application

DCC defined As supported GB Smart Meter XML Schema