Iec tr 61968 900 2015

Whi e IEC 619 8-9 defines the variou data items from whic the req est an resp n e mes ages are con tru ted, it is les pres riptive a out the cor esp n in mes age flows – that is, how a c

THIS PUBLICATION IS COPYRIGHT PROT CTED

Copyright © 2 15 IEC, Ge e a, Switzerla d

Al rig ts reserv d Unles oth rwise sp cifie , n p rt of this p blc tio ma b re ro u e or uti ze in a y form

or b a y me ns,ele tro ic or me h nic l in lu in p oto o yin a d microfim, with ut p rmis io in writin from

eith r IEC or IEC's memb r Natio al Commite in th c u try of th re u ster If y u h v a y q estio s a o t IEC

c p rig t or h v a e q iry a o t o tainin a ditio al rig tsto this p blc tio , ple se c nta t th a dres b low or

y ur lo al IEC memb r Natio al Commite for furth r informatio

Th Intern tio al Ele trote h ic l Commis io (IEC) is th le din glo al org nizatio th t pre ares a d p blsh s

Intern tio al Sta d rds for al ele tric l ele tro ic a d relate te h olo ies

Ab ut IEC publ c tio s

Th te h ic l c nte t of IEC p blc tio s is k pt u d r c nsta t re iew b th IEC Ple se ma e sure th t y u h v th

latest e itio , a c rig n a or a ame dme t mig t h v b e p blsh d

IEC Catalog e - webstore.ie c / catalog e

Th sta d-alo e a plc tio for c nsultin th e tire

biblo ra hic l infor matio o IEC Inter natio al Sta d rds,

Te h ic l Sp cific tio s, Te h ic l Re orts a d oth r

d c me ts Av ia le for PC, Ma OS, An r oid Ta lets a d

iPa

IEC publc tio s s arc - w w.ie c /se rc pub

Th a v n e se rc e a les to fin IEC p blc tio s b a

v riety of crite a (r efer en e n mb r , te t, te h ic l

c mmite ,…) It also giv s informatio o pr oje ts, re la e

a d w ith r awn p blc tio s

IEC J st Publs ed - webstore.ie c / j stpubls ed

Sta u to d te o al n w IEC p blc tio s Just Pu lsh d

d tais al n w p blc tio s rele se Av ia le o ln a d

also o c a mo th b emai

Ele to edia - ww w.ele to edia.org

Th w or l 's le din o ln dictio ary of ele tro ic a d

ele tr i al ter ms c ntainin more th n 3 0 0 ter ms a d

d finitio s in En lsh a d Fre c , w ith e uiv le t ter ms in 15

a ditio al la g a es A lso known as th Inter natio al

Ele tr ote h ic l Vo a ulary (IEV) o ln

IEC Glos ary - std.ie c / glos ary

Mor e th n 6 0 0 ele trote h ic l termin lo y e tries in

En lsh a d Fr en h e tr acte fr om th Terms a d Definitio s

cla se of IEC p blc tio s is u d sin e 2 0 Some e tr i s

h v b e c le te fr om e r lier p blc tio s of IEC TC 3 ,

7 ,8 a d CIS R

IEC Cu tomer Serv ic Cente - webstore.ie c / cs

If y u w ish to giv us y our fe d a k o this p blc tio or

n e furth r as ista c ,ple se c nta t th Customer Ser vic

Ce tr e: csc@ie c

CONTENTS

FOREWORD 8

INTRODUCTION 10 1 Sco e 13 2 Normative referen es 13 3 IEC 619 8-10 b sic 13 3.1 General 13 3.2 IEC 619 8-10 mes age ex han e p tern 14 3.3 IEC 619 8-10 mes age typ s 14 3.3.1 General 14 3.3.2 Req est mes ages 15 3.3.3 Resp n e mes ages 17 3.3.4 Un ol cited event mes ages 18 3.4 IEC 619 8-10 mes age content 19 3.4.1 General 19 3.4.2 Verb an nou elements in the mes age he der 2

3.4.3 Get req ests 2

3.4.4 Other req ests 21

3.4.5 The Cor elationID element 21

3.4.6 Other elements in the mes age he der 21

3.4.7 The Mes age.x d XSD s hema definition fi e 2

4 Req est an resp n e mes ages in detai 2

4.1 General 2

4.2 Several p tential resp n e mes ages for e c req est mes age 2

4.3 Resp n e mes ages contain a statu in ication 2

4.4 Resp n e mes ages containin data an er or notification 2

4.5 Sp cific er or in ication in the resp n e mes ages 24 4.6 Implcit in ication of s c es 2

4.7 General er or in ication in the resp n e mes ages 28 4.7.1 General 2

4.7.2 Set in the <Re ly> Res lt> element 2

4.7.3 Multiple resp n e mes ages 2

4.8 Multiple <Req est>, <Re ly> an <Paylo d> elements 2

4.9 Implementation-sp cific mes ages 3

5 The namin of o jects 3

5.1 General 3

5.2 Namin meters 3

5.3 En DeviceGroups, UsagePoints an UsagePointGroups 3

5.4 Namin of other o jects 33 5.5 Provisionin an inter ogatin a s stem 3

6 Meter re d req ests an resp n es 3

6.1 General 3

6.2 Mes age ex han e p t ern 3

6.2.1 General 3

6.3.1 General 3

6.3.2 Namin of meters 3

6.3.3 The Re din Typ element 3

6.3.4 The Re din Qual ty element 41

6.3.5 The TimeSc ed le element 4

6.3.6 Sp cifyin multiple con traints in a req est mes age 43 6.3.7 Coin ident meter re d 4

6.4 On-deman meter re d 4

6.4.1 General 4

6.4.2 Pin in a meter 4

6.5 MeterRe din s resp n e 4

6.5.1 General 4

6.5.2 The <MeterRe din > Meter> element 51

6.5.3 The <MeterRe din > Re din s> element 5

6.5.4 The <MeterRe din > Re din s> Re din Qual ties> element 5

6.5.5 The <MeterRe din > Re din s> Re din Typ > element 5

6.5.6 The <MeterRe din > Re din s> IntervalBlocks> elements 5

6.5.7 The En DeviceTyp , Re din QualtyTyp an Re din Typ elements 5

6.6 Un ol cited meter re d 5

6.6.1 General 5

6.6.2 Mes age ex han e p t ern 5

6.6.3 Mis in re d 5

6.6.4 Un ol cited MeterRe d together with En DeviceEvents 5

6.7 More a out timestamps an interval data 6

6.7.1 General 6

6.7.2 Interval data 61

6.7.3 The interval block 6

6.7.4 Raw data 6

7 Meter control req ests an resp n es 6

7.1 General 6

7.2 Mes age ex han e p t ern 6

7.3 Cre te(En DeviceControls) mes age 6

7.3.1 General 6

7.3.2 En DeviceControls element 6

7.4 Re ly(En DeviceControls) mes age 7

7.5 Cre ted(En DeviceEvents) mes age 71

7.5.1 General 71

7.5.2 En DeviceEvents element 71

7.6 Un ol cited En DeviceEvents Mes ages 7

7.6.1 General 7

7.6.2 Mes age ex han e p tern 7

7.7 Premises are networks 7

7.7.1 General 7

7.7.2 Mes age ex han e p tern 7

7.7.3 Pairin the Meter an PAN device 7

8 Config ration an provisionin 76 8.1 General 7

8.2 Mes age ex han e p t ern 7

8.3 Meter config ration 7

8.3.1 General 7

8.3.2 Cre te(MeterConfig) mes age 7

8.3.3 Re ly(MeterConfig) mes age, s c es case 81

8.3.4 Re ly(MeterConfig) mes age, faiure case 81

8.4 Master data l nk ge 81

8.4.1 General 81

8.4.2 Cre te(MasterData ink ge) mes age 8

8.5 Op rationSets 8

8.5.1 General 8

8.5.2 Op rationSet req est mes age 8

8.5.3 Op rationSet Resp n e Mes age 8

9 Sc ed l n action for future exec tion 8

9.1 General 8

9.2 Sc ed l n a meter re d 8

9.2.1 General 8

9.2.2 Mes age ex han e p t ern 8

9.2.3 MeterRe dSc ed le element 8

9.3 Cre te(MeterRe dSc ed le) mes age 9

9.3.1 General 9

9.3.2 Re ly(MeterRe dSc ed le) mes age 9

9.4 Can el n a req est 9

9.4.1 General 9

9.4.2 Can el(MeterRe dSc ed le) req est 9

10 Tran p rtin IEC 619 8-9 mes ages 9

10.1 General 9

10.2 Tran p rtin over SOAP 9

10.2.1 General 9

10.2.2 Generic WSDL 9

10.2.3 Simple acknowled ement mes ages 9

10.2.4 Example mes age flow 9

10.3 Tran p rtin over JMS 9

10.3.1 General 9

10.3.2 Expl cit acknowled ements 9

10.3.3 JMS pro erty detai s 9

10.3.4 Proces detai s 9

10.3.5 Object detai s 10

1 Summary of mes age field 10

1 1 General 10

1 2 Meter re d o eration 10

1 2.1 General 10

1 2.2 Req est mes age 10

1 2.3 Resp n e mes age 10

1 2.4 Un ol cited meter re d 10

1 3 Meter control o eration 10

1 3.5 Un ol cited meter event 1 1

1 4 Config ration an provisionin 1 1

1 4.1 General 1 1

1 4.2 Provisionin a meter 1 1

1 4.3 Cre tion of a ComMod le 1 3

1 4.4 Service ocation 1 4

1 4.5 ServiceCategoryConfig 1 6

1 4.6 Service s p ler 1 6

1 4.7 UsagePoint location 1 8

1 4.8 Usage p int 12

1 4.9 Cu tomer 12

1 4.10 Cu tomer ac ou t 12

1 4.1 Cu tomer Agre ment 12

1 4.12 Pricin Stru ture 12

1 4.13 MasterData ink ge 12

1 4.14 Op rationSet 13

1 4.15 Ad in , c an in or deletin an o ject identifier 13

Fig re 1 – Example mes age for a simple meter re d req est 16

Fig re 2 – Example resp n e mes age to a simple meter re d req est 17

Fig re 3 – Example u sol cited event mes age 18

Fig re 4 – Req estMes age definition ac ordin to Mes age.x d 19

Fig re 5 – Resp n eMes age definition ac ordin to Mes age.x d 19

Fig re 6 – EventMes age definition ac ordin to Mes age.x d 20

Fig re 7 – Sub lements al owed in ide a <He der> element 2

Fig re 8 – Example of a s c es in ication in a Re ly element 2

Fig re 9 – Example of er or in ication in a Re ly element (in omplete) 2

Fig re 10 – Sub lements al owed in ide a <Re ly> element 2

Fig re 1 – Sub lements al owed in ide a <Re ly> Er or> ID> element 2

Fig re 12 – Example of overal in ication of s c es in a Re ly element 2

Fig re 13 – Example of er or in ication in a Re ly element (cor ected) 2

Fig re 14 – En Device definition 31 Fig re 15 – Example of a Meter Re d Req est with NameTyp an NameTyp Authority 3

Fig re 16 – Mes age ex han e p tern for a meter re d req est with a sin le resp n e mes age 3

Fig re 17 – Mes age ex han e p tern for a meter re d req est with multiple resp n e mes ages 3

Fig re 18 – GetMeterRe din s definition ac ordin to GetMeterRe din s.x d 3

Fig re 19 – <GetMeterRe din > Re din Typ > definition 41

Fig re 2 – <GetMeterRe din > Re din Qualty> definition 4

Fig re 21 – <GetMeterRe din s> TimeSc ed le definition 4

Fig re 2 – Example of a req est mes age for two Re din Typ codes over two meters 4

Fig re 2 – Example of a req est mes age for two meter/Re din Typ combination 4

Fig re 2 – Mes age ex han e p tern for an on-deman meter re d 48

Fig re 2 – Example of an on-deman meter re d req est mes age 4

Fig re 2 – Example of a resp n e to a meter re d req est 5

Fig re 2 – MeterRe din s definition ac ordin to MeterRe din s.x d 51

Fig re 2 – <MeterRe din s> Meter> definition 5

Fig re 2 – <MeterRe din s> Re din > definition 5

Fig re 3 – <MeterRe din > Re din Qual ty> definition 5

Fig re 31 – <MeterRe din s> IntervalBlock definition 5

Fig re 3 – Example of a meter re d resp n e with named Re din Typ an Re din Qual ty elements 56 Fig re 3 – Mes age ex han e p tern for a set of u sol cted meter re d 5

Fig re 3 – Example of an u sol cited meter re d mes age 5

Fig re 3 – Example of a mis in re din in a publ s ed mes age 5

Fig re 3 – Example of a known mis in re din in a publ s ed mes age 59 Fig re 3 – Example of a mes age s owin b th an event an a re din 6

Fig re 3 – Re din Timestamps 61 Fig re 3 – Example u e of IntervalBlocks 6

Fig re 4 – Mes age ex han e p tern for a meter control o eration 6

Fig re 41 – Example of a cre te(En DeviceControls) mes age for one meter 6

Fig re 4 – Example of a cre te(En DeviceControls) mes age for two meters 6

Fig re 4 – En DeviceControls definition 6

Fig re 4 – En DeviceControl definition 6

Fig re 4 – En DeviceControlTyp definition 7

Fig re 4 – Example of a re ly(En DeviceControls) mes age 7

Fig re 4 – Example of a cre ted(En DeviceEvents) mes age 71 Fig re 4 – En DeviceEvents definition 71

Fig re 4 – En DeviceEvent definition 7

Fig re 5 – En DeviceEventTyp definition 7

Fig re 51 – Mes age ex han e p tern for an u sol cted En Device event 7

Fig re 5 – Mes age ex han e p tern for a cre te(MeterConfig) mes age 7

Fig re 5 – MeterConfig definition 79 Fig re 5 – Example of a cre te(MeterConfig) mes age 8

Fig re 5 – Example of a re ly(MeterConfig) mes age, s c es case 81 Fig re 5 – Example of a re ly(MeterConfig) mes age, fai ure case 81 Fig re 5 – MasterData ink geConfig Relation hips 8

Fig re 5 – Example of a cre te(MasterData ink geConfig) mes age 8

Fig re 5 – Example of an exec te(Op rationSet mes age 85 Fig re 6 – Example of a re ly(Op rationSet mes age, s c es case 8

Fig re 61 – Example of a re ly(Op rationSet mes age, fai ure case 8

Fig re 6 – Mes age ex han e p tern for s hed ln a set of meter re d 8

Fig re 6 – MeterRe dSc ed le definition 9

Fig re 6 – Example of a meter re d s hed le can el mes age 9

Fig re 6 – Example of a simple meter re d req est imb d ed in a SOAP mes age 9

Fig re 6 – Example of a simple acknowled ement mes age 97

Fig re 7 – Mes age ex han e p tern s owin the simple acknowled ement

mes ages 9

Ta le 1 – Common En DeviceControls an their cor esp n in En DeviceEvent codes 6

Ta le 2 – Common En DeviceEvent codes for u sol cited mes ages 7

Ta le 3 – Config Profi es 7

Ta le 4 – JMS pro erties 99

Ta le 5 – get MeterRe din s) field 101

Ta le 6 – re ly(MeterRe din s) field 10

Ta le 7 – cre te(En DeviceControls) field 10

Ta le 8 – re ly(En DeviceControls) field 10

Ta le 9 – cre ted(En DeviceEvents) field 10

Ta le 10 – cre te(MeterConfig) field 1 1

Ta le 1 – cre te(ComMod leConfig) field 1 3

Ta le 12 – cre te(Service ocationConfig) field 1 5

Ta le 13 – cre te(ServiceCategoryConfig) field 1 6

Ta le 14 – cre te(ServiceSup l erConfig) field 1 7

Ta le 15 – cre te(UsagePointL cationConfig) field 1 9

Ta le 16 – cre te(UsagePointConfig) field 12

Ta le 17 – cre te(Cu tomerConfig) field 12

Ta le 18 – cre te(Cu tomerAc ou tConfig) field 12

Ta le 19 – cre te(Cu tomerAgre mentConfig) field 12

Ta le 2 – cre te(Pricin Stru tureConfig) field 12

Ta le 21 – cre te(MasterData ink geConfig) field , example 1 12

Ta le 2 – cre te(MasterData ink geConfig) field , example 2 131

Ta le 2 – exec te(Op rationSet He der an Paylo d field , example 1 13

Ta le 2 – exec te(Op rationSet He der an Paylo d field , example 2 13

Ta le 2 – exec te(Op rationSet He der an Paylo d field , example 3 13

INTERNATIONAL ELECTROTECHNICAL COMMISSION

1) Th Intern tio al Ele trote h ic l Commis io (IEC) is a worldwid org nizatio for sta d rdizatio c mprisin

al n tio al ele trote h ic l c mmite s (IEC Natio al Commite s) Th o je t of IEC is to promote

intern tio al c -o eratio o al q estio s c n ernin sta d rdizatio in th ele tric l a d ele tro ic fields To

this e d a d in a ditio to oth r a tivities, IEC p blsh s Intern tio al Sta d rds, Te h ic l Sp cific tio s,

Te h ic l Re orts, Pu lcly Av ia le Sp cific tio s (PAS) a d Guid s (h re fer refere to as “IEC

Pu lc tio (s)”) Th ir pre aratio is e truste to te h ic l c mmite s; a y IEC Natio al Commite intereste

in th su je t d alt with ma p rticip te in this pre aratory work Intern tio al g v rnme tal a d n

n-g v rnme tal org nizatio s laisin with th IEC also p rticip te in this pre aratio IEC c la orates closely

with th Intern tio al Org nizatio for Sta d rdizatio (ISO) in a c rd n e with c n itio s d termin d b

a re me t b twe n th two org nizatio s

2) Th formal d cisio s or a re me ts of IEC o te h ic l maters e pres , as n arly as p s ible, a intern tio al

c nse sus of o inio o th rele a t su je ts sin e e c te h ic l c mmite h s re rese tatio from al

intereste IEC Natio al Commite s

3) IEC Pu lc tio s h v th form of re omme d tio s for intern tio al use a d are a c pte b IEC Natio al

Commite s in th t se se Whie al re so a le eforts are ma e to e sure th t th te h ic l c nte t of IEC

Pu lc tio s is a c rate, IEC c n ot b h ld resp nsible for th wa in whic th y are use or for a y

misinterpretatio b a y e d user

4) In ord r to promote intern tio al u iformity, IEC Natio al Commite s u d rta e to a ply IEC Pu lc tio s

tra sp re tly to th ma imum e te t p s ible in th ir n tio al a d re io al p blc tio s An div rg n e

b twe n a y IEC Pu lc tio a d th c r esp n in n tio al or re io al p blc tio sh l b cle rly in ic te in

th later

5) IEC itself d es n t pro id a y atestatio of c nformity In e e d nt c rtific tio b dies pro id c nformity

as es me t servic s a d, in some are s, a c s to IEC marks of c nformity IEC is n t resp nsible for a y

servic s c rie o t b in e e d nt c rtific tio b dies

6) Al users sh uld e sure th t th y h v th latest e itio of this p blc tio

7) No la i ty sh l ata h to IEC or its dire tors, emplo e s, serv nts or a e ts in lu in in ivid al e p rts a d

memb rs of its te h ic l c mmite s a d IEC Natio al Commite s for a y p rso al injury, pro erty d ma e or

oth r d ma e of a y n ture wh tso v r, wh th r dire t or in ire t, or for c sts (in lu in le al fe s) a d

e p nses arisin o t of th p blc tio , use of, or rela c u o , this IEC Pu lc tio or a y oth r IEC

Pu lc tio s

8) Ate tio is drawn to th Normativ refere c s cite in this p blc tio Use of th refere c d p blc tio s is

in isp nsa le for th c re t a plc tio of this p blc tio

9) Ate tio is drawn to th p s ibi ty th t some of th eleme ts of this IEC Pu lc tio ma b th su je t of

p te t rig ts IEC sh l n t b h ld resp nsible for id ntifyin a y or al su h p te t rig ts

The main task of IEC tec nical commit e s is to pre are International Stan ard However, a

tec nical commite may pro ose the publ cation of a tec nical re ort when it has col ected

data of a diferent kin from that whic is normal y publ s ed as an International Stan ard, for

example "state of the art"

IEC TR 619 8-9 0, whic is a tec nical re ort, has b en pre ared by IEC tec nical

commit e 5 : Power s stems management an as ociated information ex han e

The text of this tec nical re ort is b sed on the fol owin doc ments:

This publcation has b en drafed in ac ordan e with the ISO/IEC Directives, Part 2.

A l st of al p rts in the IEC 619 8 series, publ s ed u der the general title Ap p licato

integrato at electric uti tes – Syste m inte rface s for distrib u tio ma age me t, can b fou d

on the IEC we site

The present tec nical re ort refers to some ambig ities oc ur in es ential y in IEC 619 8-9

an IEC 619 8-10 (la eled here as “Warnin s”) These is ues are b in ad res ed in

Workin Group 14 of IEC tec nical commite 5 an wi b resolved in the forth omin new

edition of IEC 619 8-9 an IEC 619 8-10

The commit e has decided that the contents of this publcation wi remain u c an ed u ti

the sta i ty date in icated on the IEC we site u der "htp:/we store.iec.c " in the data

related to the sp cific publ cation At this date, the publ cation wi b

• reconfirmed,

• with rawn,

• re laced by a revised edition, or

• amen ed

A bi n ual version of this publ cation may b is ued at a later date

IMPORTANT – The 'colour in ide' logo on the cov r pa e of this publ c tion indic te

understa ding of its conte ts Us rs s ould therefore print this doc me t using a

colour printer

Ge eral

This tec nical re ort is inten ed to help u ers to interpret IEC 619 8-9:2 13

IEC 619 8-9 provides a u iform me n for p rformin meter re d an control o eration over

a distributed network

The most recent version of IEC 619 8-9 was publs ed in 2 13 an is the secon edition

This tec nical re ort therefore con entrates on this edition

Althou h this tec nical re ort con entrates on IEC 619 8-9, a p rtion of this de en s on

another stan ard, IEC 619 8-10 :2 13

The purp se of IEC 619 8-9 is to al ow heterogene u comp nents, p s ibly prod ced by

dif erent ven ors, to intero erate with one another Su h comp nents typical y in lu e a

c stomer information s stem (CIS), an outage management s stem (OMS), a meter data

management s stem (MDMS) an a he d-en s stem (HES)

The mes ages that are ex han ed b twe n the variou comp nents are XML doc ments

IEC 619 8-9 defines how these mes ages are expres ed ac ordin to the semantic of the

o eration s p orted by this stan ard

For example, a MDMS mig t in tru t a HES to re d the forward bulk energ u age from a set

of meters an return the cor esp n in values b ck to the MDMS Alternatively, the HES

mig t b in tru ted to p rform some control o eration on a meter – for in tan e, dis on ect

the p wer, reset the re din s of that meter an then re sta l s the p wer again In b th

cases, IEC 619 8-9 defines the precise way in whic the a pro riate req est an resp n e

mes ages are formulated

Whi e IEC 619 8-9 defines the variou data items from whic the req est an resp n e

mes ages are con tru ted, it is les pres riptive a out the cor esp n in mes age flows –

that is, how a complete mes age ex han e lo ks This doc ment provides examples of typical

mes age ex han e p t ern

In other word , IEC 619 8-9 is informative rather than normative (man atory) when it comes

to des ribin u e cases an mes age p tern

IEC 619 8-9 do s not pres rib the me n by whic s c mes ages are tran mited from

comp nent to comp nent However, it may b as umed that comp nents commu icate with

one another either by me n of we services (SOAP mes ages) or over a mes age bu s c

as JMS or eq ivalent

IEC 619 8-9 XML s h ma definition fi e

IEC 619 8-9 defines man dif erent typ s of XML mes age ac ordin to the kin of data that

are to b tran mited These mes age typ s are refer ed to as profies For example, one

s c profi e cor esp n s to a meter re d req est mes age an another to the cor esp n in

resp n e mes age

An exes H an I of IEC 619 8-9:2 13 contain l stin s of variou XML s hema definition

(XSD) fi es, one for e c profie s p orted by the stan ard These con train the formats of the

A p p r or PDF l stin is not a p rtic larly practical way of ac es in these XSD doc ments.

However, they are also avaiable in electronic form from the UCAIUG we site

1

Su h XSD fies may b con eniently examined u in a gra hical editor s c as XML Spy

whic is a commercial prod ct from Altov GmbH

Con e tions u e in this te hnic l report

The examples u ed in this tec nical re ort general y refer to MDMS an HES s stems These

names are u ed for i u trative purp ses only Other s stem names s c as CIS an MDMS or

clent an server could ju t as eq al y wel have b en c osen

XML fragments an examples, the names of fi es an other l teral text are s own in a fixe

for explanation of the other s mb ls u ed

A sig l k this denotes a warnin There are a few are s where sp cial care

ne d to b ta en with IEC 619 8-9

How this te hnic l report is orga ize

• Clau e 3 of this tec nical re ort des rib s the b sic of IEC 619 8-10 as they relate to

IEC 619 8-9

• Clau e 4 des rib s more detai s con ernin IEC 619 8-10 , esp cialy as to what these

have to do with formulatin req est an resp n e mes ages an how notification of

er ors are commu icated This clau e also des rib s how the stan ard IEC 619 8-9 set of

mes ages may b au mented by implementation-sp cific mes ages

• Clau e 5 des rib s how meters an other o jects are named in the IEC 619 8-9 world

• Clau es 6 an 7 resp ctively des rib how meter re d o eration an meter control

o eration are car ied out

• Clau e 8 s ows how a MDMS or HES may b config red with provisionin information

• Clau e 9 dis u ses some of the les freq ently u ed mes age ex han e p tern ,

sp cifical y how to s hed le action for exec tion at some future time an how to can el

them s ould the ne d arise

_ _ _ _ _ _ _

1

ht p:/ iectc5 ucaiug.org WG14/P rt9/Sh re %2 Docume ts P rt%2 9%2 2 d/IEC-P rt

9-Profi es-2 d-E itio %2 FDIS.zip

2

ht p:/ www.alto a.com – XML Sp is th tra e n me of a pro u t su ple b Alto a GmbH This

informatio is giv n for th c n e ie c of users of this d c me t a d d es n t c nstitute a e d rseme t b

th IEC of th pro u t n me Eq iv le t pro u ts ma b use if th y c n b sh wn to le d to th same

results

3

ht p:/ www.ecl pse.org – Eclpse is th tra e n me of a pro u t su ple b th Eclpse Fo n atio This

informatio is giv n for th c n e ie c of users of this d c me t a d d es n t c nstitute a e d rseme t b

th IEC of th pro u t n me Eq iv le t pro u ts ma b use if th y c n b sh wn to le d to th same

results

• Clau e 10 provides some detai s con ernin tran mit in IEC 619 8-9 mes ages over

SOAP (we services) or JMS tran p rts

• Clau e 1 is a detai ed referen e of the variou field that are u ed within IEC 619 8-9

mes ages

APPLICATION INTEGRATION AT ELECTRIC UTILITIES –

Part 900: Guidance for implementation of IEC 61968-9

This p rt of IEC 619 8-9, whic is a tec nical re ort, is a referen e doc ment an , as s c , is

not alway s ita le for some ne new to the world of meter re din an control In p rtic lar, it

as umes sig ificant domain knowled e

This tec nical re ort is a comp nion doc ment to the of icial stan ard It is writ en from the

viewp int of a sofware develo er or s stems integrator who is task d with implementin

IEC 619 8-9 It is not inten ed as a complete des ription of this stan ard For ful detai s,

ple se refer to IEC 619 8-9

To get the most from this tec nical re ort, the u er s ould have a go d u derstan in of XML

tec nologies, in p rtic lar of XML s hema definition an of we services

This tec nical re ort contain informative recommen ation whic may b u ed to g ide

implementation of IEC 619 8-9 an IEC 619 8-10 It do s not atempt to b ex au tive In

p rtic lar, it foc ses on the most common IEC 619 8-9 interfaces an as umes the u er is

u in we services or JMS as the u derlyin tran p rt mec anism If the u er is u in other

s stems or the tran p rt services are somethin other than we services or JMS, the

recommen ation in this tec nical re ort may b les relevant but p rha s sti u eful

The folowin doc ments, in whole or in p rt, are normatively referen ed in this doc ment an

are in isp n a le for its a pl cation For dated referen es, only the edition cited a pl es For

u dated referen es, the latest edition of the referen ed doc ment (in lu in an

amen ments) a pl es

IEC 619 8-9:2 13, Ap plcato integrato at electric u ti te s – System interfaces for

distrib utio ma a eme nt – Part 9: Inte rface s for meter re adin a d co trol

IEC 619 8-10 :2 13, App licato inte rato at electric uti tes – System interfaces for

distrib utio ma a eme nt – Part 100 : Impleme ntato p rofie s

3 IEC 61968-100 ba ic

The IEC 619 8-10 stan ard is s ared acros the other IEC 619 8 stan ard , not ju t

IEC 619 8-9 In bro d terms, where s IEC 619 8-9 is con erned with the co te nts of the

variou mes ages, IEC 619 8-10 is more con erned with the co structo of the mes ages

an the tra sp rt of mes ages b twe n s stems

An imp rtant p rt of IEC 619 8-10 is the Me s ge.xs s hema definition fie

5

This

des rib s a mes age he der whic forms p rt of every IEC 619 8-9 mes age This is

_ _ _ _ _ _ _

Before contin in , it s ould b emphasized that this tec nical re ort des rib s IEC 619 8-10

as it sp cifical y relates to IEC 619 8-9 In general, however, the prin iples des rib d here

are also a pl ca le to other p rts of the IEC 619 8 series, esp cial y Parts 3 to 8

3.2 IEC 619 8-10 me s ge e c a ge pat erns

IEC 619 8-9 do s not completely sp cify the mes age ex han e p tern – that is, how a set

of mes ages together form a con ersation in whic one s stem req ests data from another

an these are then returned Su h mes age ex han e p t ern in te d fal u der the remit of

IEC 619 8-10

A detaied dis u sion of al the p s ible mes age ex han e p tern is b yon the s o e of

this tec nical re ort However, with regard to implementation of IEC 619 8-9, there are two

bro d kin s of mes age ex han e into whic al u e cases fal

• Re ue t an re pon e me s ge This is the clas ic req est resp n e p radigm

For example, a MDMS s stem may ma e an on-deman meter re d req est to a HES

When the HES has o tained the neces ary data, it return these b ck to the MDMS

alon with some in ication of s c es or otherwise of the overal req est Other

examples mig t b for a req est to b made to the HES to dis on ect the p wer to a

c stomer or for the meter to b reset to an initial state (if the c stomer has ju t moved

into a new a artment, say) In these lat er examples, the resp n e reflects the s c es

or fai ure of the req est

The IEC 619 8 series of stan ard are flexible in definin how a complete

con ersation may b car ied out For in tan e, a sin le req est for some meter data

may res lt in several cor esp n in resp n e mes ages b in generated This may

ha p n, say, if the meter re d req ests are for future data It may also oc ur if the

amou t of data b in req ested is to large to fit into a sin le resp n e, in whic case

a series of resp n e mes ages would b returned that re resent the complete meter

data del vered in c u ks

• Un ol cite e e t me s ge These are made when one entity sen s data to another

without an initial req est havin b en made For example, a HES mig t notify a MDMS

when a meter is dis on ected Alternatively, the HES may b config red to re d a set

of meters at certain times an to re ort their values without an expl cit req est

mes age b in sent

In another example, a typical con ersation may b gin with a req est for an action to

ta e place fol owed by the cor esp n in resp n e whic in es en e say nothin

more than “ his req est a p ars to b ac e ta le” Final y, only when the a pl cation

car ies out the action at some later time is an u sol cited event mes age sent to the

original req estor to confirm whether the action has s c e ded or not

3.3 IEC 619 8-10 me s ge type

IEC 619 8-10 defines four kin s of mes age: request mes ages, resp n e mes ages, event

mes ages an fault mes ages In IEC p rlan e these mes age kin s are termed stere typ s

• Re ue t me s ge are u ed for sen in q eries or comman s For example, a

req est mes age mig t b sent from a MDMS to a HES to in tru t the later to o tain a

set of meter re din s ac ordin to meter identification an other criteria

information On e it has ac uired the req ired data, for example, the HES sen s these

b ck to the MDMS in one or more resp n e mes ages

Resp n e mes ages are also u ed to in icate whether a given req est s c e ded or

whether there were an fai ures in car yin it out

Resp n e mes ages may also b u ed for sen in simple acknowled ements in the

context of we services as des rib d in Subclau e 10.2.2

• Ev nt me s g s are u ed for sen in u sol cited data – that is, as n hronou data or

statu information For in tan e, s c mes ages may b sent to notify a MDMS or

other entity of an as n hronou event s c as a p wer outage to a meter

As noted a ove, event mes ages may also b u ed to sen meter re din s ac ordin

to a pre-config red s hed le For example, a HES mig t maintain its own s hed le of

meter inter ogation an pu h these data to a MDMS at reg lar intervals throu hout

the day

An event mes age that res lts from a previou req est is termed a co se uental

e ve t mes age

• Fa lt me s g s are u ed for sen in notification of er ors that are so severe that the

receivin s stem can p rform no me nin ful proces in These typical y oc ur within

the context of req ests made over we services – for in tan e, as a res lt of detection

of a SOAP fault More general er or notification – req ests that are in omplete or

referen e non-existent meters an s c lk – are in te d made in a resp n e

mes age This doc ment do s not ad res fault mes ages an further

An IEC 619 8-9 mes age, whether it is a req est mes age, resp n e mes age or event

mes age, is comp sed as an XML doc ment These diferent mes age typ s are

distin uis ed by the to -level element in the XML doc ment This mu t alway b one of

< e u s Me s ge>, < e pon eMe s ge> or <Eve tMe s ge> ac ordin ly

3.3.2 Re ue t me s ge

Req est mes ages are stru tured as i u trated in Fig re 1 This is an example of a simple

mes age that is sent from a MDMS to a HES to req est a meter re d

Figure 1 – Ex mple me s g for a simple meter re d re ue t

At the outermost level there is a < e u s Me s ge> element whic , in this example, b lon s

Of p rtic lar imp rtan e are the <H a er < erb> an <H a er <Nou > s b lements The

combination of verb an nou identify the purp se of the mes age Here they have values

ge an Me er e d ngs resp ctively an th s identify this mes age as b in a meter re d

req est This is des rib d further in Subclau e 3.4 (The other s b lements in ide the

<H a er – < ime t mp>, < e s ge D , <Co re a ion D an <Co me t> – are explained

in 3.4.5 an 3.4.6)

The < e u s Me s ge> element also contain a < e u s > element This contain the

information as ociated with the req est – in this example, a <G tMe er e d ngs>

s b lement Other kin s of req est – a meter control o eration, for example – would contain

dif erent information (profi es) within the < e u s > element

The <G tMe er e d ngs> element contain the q al fyin criteria neces ary for ma in the

meter re d req est In this case, it sp cifies a sin le meter identifier an a time ran e In

practice, s c meter re d req ests are ofen mu h more compl cated an contain man more

p rameters to q al fy the precise data b in req ested – for example, the sp cific kin of

data, a set of time ran es, data that me t certain q alty con traints or other criteria

3.3.3 Respons me s ge

A resp n e mes age is generated as a res lt of a previou req est mes age Resp n e

mes ages are stru tured as i u trated by the example in Figure 2

Figure 2 – Ex mple re pons me s ge to a simple meter re d re ue t

As s own in this example, a resp n e mes age contain a < e pon eMe s ge> element at

the to level

Ju t l k the req est mes age of Fig re 1, a resp n e mes age also contain a <H a er

element (3.4) In turn this contain <H a er < erb> an <H a er <Nou > s b lements

The <H a er < erb> element is alway re ly for a resp n e mes age (3.4.2)

The <H a er <Nou > s b lement in the resp n e mes age alway matc es that of the

original req est an denotes the kin of mes age b in sent In this example, the value of

Me er e d ngs denotes that this is a re ly to a previou meter re din s req est

A resp n e mes age contain an in ication of whether a p rtic lar req est s c e ded or

fai ed an this is in lu ed in the < e ly element It may b the case that the returned data

are spre d over several mes ages in whic case this is also in icated This is des rib d in

Subclau es 4.3 to 4.7

Besides the <H a er an < e ly elements, the resp n e mes age also contain a

<P yloa > element It is this <P yloa > element that contain the actual data b in returned

as a res lt of the req est – that is, as umin that the req est s c e ded at le st p rtial y

Becau e the data in the <P yloa > element de en on the nature of the re ly, the

Me s ge.xs s hema definition alows a <P yloa > element to hold an kin of data – meter

data or whatever is a pro riate for the re ly

The <H a er <Nou > element sp cifies the format of the data b in sent an this matc es

the XML s hema definition for the <P yloa > data In the example a ove, the

<H a er <Nou > is Me er e d ngs an this cor esp n s to the namesp ce of the data within

the <P yloa > (h t :/ i c.c /TC 7 201 /Me er e d ngs#) In this example, the data is

contained within a < e er e d ngs> s b lement within the <P yloa > There is a sin le

meter re din containin a time-stamp, value an re din typ The later des rib s the

precise kin of data me s red by the value

An u sol cited event mes age is simi ar to a resp n e mes age in that it is u ed to sen data

from one s stem to another However, u l k a resp n e mes age, an event mes age is sent

autonomou ly an not neces ari y as the res lt of some previou req est mes age

Another diferen e to resp n e mes ages is that the nou in the mes age he der ne d not

matc that of the original req est, if an

The verb in the mes age he der mu t b in the p st ten e an b lon to one of the set

p wer los an so notifies the MDMS ac ordin ly The later case is des rib d more ful y in

As noted previou ly, IEC 619 8-10 in lu es the Me s ge.xs XML s hema definition fi e

This fi e sp cifies the overal stru ture of an IEC 619 8 mes age ac ordin to whether the

to -level element is a < e u s Me s ge>, < e ly e s ge> or <Eve tMe s ge> For

in tan e, Fig re 4 s ows that a < e u s Me s ge> mu t contain a <H a er s b lement an

may o tional y also contain < e u s > or <P yloa > s b lements Strictly sp a in ,

althou h b th are tec nical y o tional, in practice at le st one of the < e u s > or <P yloa >

s b lements are present

Figure 4 – Re ue tMe s ge definition a cordin to Me s ge.x d

Simi arly a resp n e mes age has the stru ture de icted in Fig re 5 In this case the < e ly

element contain statu or er or information an the <P yloa > element contain the data

b in returned as the res lt of a previou req est mes age

Fig re 5 – Re pons Me s ge d finition a cording to Me s g x d

In the case of an event mes age, only the p ylo d an he der are sent as s own in Fig re 6

IEC

IEC

Figure 6 – Ev ntMe s g definition a cording to Me s ge.x d

3.4.2 Verb a d noun eleme ts in the me s ge he der

An IEC 619 8-9 mes age mu t alway contain at le st a mes age he der with element

<H a er

The <H a er mu t contain at le st b th < erb> an <Nou > s b lements As noted a ove,

the definition of this mes age he der is covered by IEC 619 8-10 rather than by

IEC 619 8-9

The verb contained in the mes age he der mu t b lon to one of the set c n e , c a ge,

c os , cre t , d l t , exe u e, ge for req est mes ages, re ly for resp n e mes ages

an c n e e , c os d, c a ge , cre t d, d l t d or exe u e for event mes ages These

verbs are alway in lower-case

For meter re din an control o eration , the nou b lon s to one of the set Me er e d ngs,

E dDevi e on r l or E dDevi e ve t Nou s for o eration other than meter re din

an control are also p s ible – for in tan e, for HES provisionin or config ration In the case

of resp n e mes ages, the nou is the same as that in the original req est

The combination of verb an nou determines how the mes age is to b interpreted For

in tan e, a mes age with a <H a er < erb> of ge an a <H a er <Nou > of

Me er e d ngs is interpreted by a MDMS or HES as a req est for o tainin meter re d

values (either by ad res in the en devices directly or p s ibly from a data ase of stored

re din s)

3.4.3 Get re u sts

A ge verb in the mes age he der denotes a q ery req est The as ociated information for

sp cifyin the q ery is in lu ed in the mes age < e u s > element

For example, the as ociated data for a meter re d req est – the meter identifiers, the times of

interest for the meter data, the kin of meter data b in req ested an so on – are al

contained in a < e u s > G tMe er e d ngs> element as i u trated in Fig re 1

For req ests made with a < erb> of ge , the name of the s b lement within the < e u s >

section of the mes age is the name as that of the nou pre en ed with G t For example, a

< erb> of ge an a <Nou > of Me er e d ngs imply that the name of the s b lement is

<G tMe er e d ngs>

IEC

IEC 619 8-9 an IEC 619 8-10 are ambig ou an o en to interpretation

as to whether the G t prefix is req ired – in this case, whether a ge

req est s ould u e a <G tMe er e d ngs> s b lement (alon with the

G tMe er e d ngs.xs s hema definition fi e) or whether it s f ices to u e

a < e er e d ngs> s b lement in te d ( ogether with the

Me er e d ngs.xs s hema definition fi e) However, the con entional

u derstan in is that the former is cor ect and not the lat er Simi ar

con ideration a ply to other req ests made with a ge verb

The GetXx XSD s hema definition fi es may disa p ar in future edition of

IEC 619 8-9 an IEC 619 8-10

3.4.4 Other re ue ts

Verbs other than ge denote that an action is b in req ested or that information is b in

returned as the res lt of some previou mes age For in tan e, a control mes age may b

sent to cau e a switc to b set or a config ration item to b updated For s c req ests, the

as ociated information is car ied in the <P yloa > section of the mes age

For req ests made with a < erb> other than ge , the name of the s b lement within the

<P yloa > section is the same as that of the <Nou > For example, if the < erb> is re ly

This is u eful when a req estresp n e mes age p t ern is b in u ed When one s stem

sen s a req est or comman to another an sets this element to some value, the exp ctation

is that the resp n in s stem wi set this element to the same value as that in the original

req est mes age In this way, the req estin s stem can matc received resp n es to the

original req ests

A simi ar con ideration a ples for con eq ential event mes ages The <Co re a ion D

element in s c a mes age cor esp n s to that in the req est that cau es the con eq ential

event mes age to b generated

The <Co re a ion D element s ould b u iq e acros mes ages b in ex han ed b twe n

s stems One way of en urin this is to define this as a 12 -bit u iversal y u iq e identifier

(UUID)

3.4.6 Other eleme ts in the me s g he d r

Other o tional elements that may b set in the mes age he der in lu e the fol owin :

• < e i ion> The profie-sp cific section of a mes age within the < e u s > an

<P yloa > elements are q alfied by namesp ces These namesp ces sp cify the

version of the relevant XSD s hema definition For those cases where non-stan ard

c an es are req ired, the < evi ion> element is to b interpreted as a minor version

level refer in to the p ylo d or req est data The values as ig ed to this field are

non-normative an have me nin only within the local organization

• < im s am > This element in icates when the mes age was prod ced.

• < e ly d r s > If present, this forces an resp n e mes ages to b sent to the

sp cified ad res

• < ck eq ir d> If this has the value tru , an expl cit acknowled ement mes age is

sent by the recipient s stem as so n as it receives a req est This element is ig ored

acknowled ement mes age is sent regardles This is des rib d further in 10.2.2

• < es ag ID This is a strin whic can b u ed to identify the mes age This together

with the < ime t mp> are u eful for tracin or log in mes ages as they are

proces ed throu h the MDMS, HES or other s stems It has no normative me nin

• <Co m n > This element may contain an fre text – for example, “Th s i examp e

1”

• < r p rty This is a set of name/value p irs that may b u ed to c stomize the

s stem b haviour in way goin b yon that defined by the IEC This is general y u ed

to provide some implementation-sp cific fu ctional ty that go s b yon the stan ard

Usin the <Pr p rty element may imp ir intero erabi ty See, for example,

the warnin in 4.7.3

3.4.7 The Me s ge.x d XSD s hema definition fi e

The Me s ge.xs fie sp cifies the s b lements p rmited in ide a <H a er element as

de icted in Fig re 7 L o at the XML fragments in Fig re 1 an Fig re 2 to se some sample

values for these elements

Figure 7 – Subeleme ts al owe inside a <He d r> eleme t

There are a few items of note that p rtain to IEC 619 8-10 req est an resp n e mes ages

in general

A sin le req est mes age may cau e several resp n e mes ages to b generated That is,

u l k most mes agin p radigms s c as a remote proced re cal mec anism where there is

a strict one to one cor elation b twe n req ests an resp n es, IEC 619 8-10 alows itself

more flexibi ty

IEC

Althou h IEC 619 8-10 al ows for an in ication of when the last of several resp n e

mes ages is sent (se 4.7.2), in practice this may not alway b p s ible Hen e it may b

dif ic lt for an implementin s stem to know when it can cle r up relevant state information In

general an implementation mu t rely on generou time uts b fore it can safely remove state

information

As noted in 3.4.5, a resp n e mes age may contain a <Co re a ion D element in the

mes age he der, th s al owin for the req estin s stem to matc resp n e mes ages with

the original req est

It is exp cted that a resp n e mes age contain an in ication of the overal s c es or

otherwise of the req est This is contained in the < e ly element

If no er ors are en ou tered in at emptin to evaluate the req est, this < e ly element is as

The req est may also fai p rtial y or completely in whic case the < e ly element contain

the cor esp n in detai s An example of a p rtial fai ure is if the req est refers to some non

-existent meters An example of a complete fai ure is if the req est can ot b p rsed, is

mis in cru ial information or if none of the sp cified meters exist This is explained further in

4.5

If the resp n e data exten over more than one mes age, the < e ly element also s ows

this

4.4 Re pons me s ge containing data a d er or notific tions

Ac ordin to the Me s ge.xs s hema s own in Fig re 5, a resp n e mes age may contain

data, informational con ition an er or in ication or an ar an ement of these

The data, if present, are placed in the <P yloa > element The informational con ition an

er or in ication , if an , are in the < e ly element IEC 619 8-10 al ows the informational

con ition an er or in ication an resp n e data to b sent in one or over several

mes ages in whatever combination s its the resp n er b st

In the case of a re ly to a meter re din s req est, therefore, the <P yloa > contain the

meter re d values The < e ly element contain er or notification s c as the fact that the

req est may have mentioned a non-existent meter or that the req ested data could not b

returned for some other re son

4.5 Spe ific er or in ic tions in the re pon e me s ge

Er or in ication are denoted by the in lu ion of a < e ly element where the

The field of the XML s hema cor esp n in to the < e ly <Er o > element are s own in

Fig re 10

The < e ly <Er o > cod > s b lement is in te d exp cted to have one of the values

defined in An ex B of IEC 619 8-9:2 13 Ta le B.10 of IEC 619 8-9:2 13 contain a lst of

common values

The < e ly <Er o > l ve > s b lement is o tional but, if present, mu t b one of I FO M,

W RN N , FA AL or CA AST OP I A value of FA AL do s not neces ari y me n that the

whole req est has fai ed or even that some ir evoca le pro lem p rtainin to the entire

req est has oc ur ed It me n only that that p rt of the req est – for in tan e p rtainin to a

sin le meter – can ot b an wered For in tan e, a p rtic lar meter mentioned in the req est

may not exist

(A p rtic lar er or code may cor esp n to an I FO M level in some cases an to a FA AL

level in others.)

The < e ly <Er o > ID element in icates to whic en p int or other o ject the er or

notification p rtain , p s ibly also in lu in the name typ an name typ authority elements

of the req est These are placed in i T p = an i Au ho i y= at ributes resp ctively

The < e ly <Er o > ID element may also in lu e a ki d at ribute whic is exp cted to

have one of the values n me, tra s c ion or u i It also in lu es an obje tT p =

at ribute For the case of a meter that can ot b re d, the ki d atribute is n me an the

obje tT p = at ribute is Me er or U age oi t ac ordin to how the req est was formulated

(6.3.2) These atributes are s own diagrammatical y in Fig re 1

An example of s c an er or in ication is as s own in Fig re 9:

Figure 9 – Ex mple of er or indic tions in a Reply eleme t (incomplete)

This example is, however, in omplete The re son for this an the me nin of the

< e ly < e u t> element are explained in Subclau e 4.6

Figure 10 – Subeleme ts al owe in ide a <Reply eleme t

IEC

Fig re 1 – Subeleme ts al owe inside a <Reply <Er or> ID> eleme t

4.6 Impl cit indic tion of s c e s

By con ention, < e ly <Er o > elements are returned in a resp n e mes age only for those

cases where er ors are de med to have oc ur ed The s c es ful cases are u ual y not

expl citly l sted althou h the stan ard do s not pros rib this

This impl es that, in the case of a multi-mes age resp n e b in sent, a cl ent (receivin )

s stem can determine the s c es ful cases only when al the resp n e mes ages have b en

received

IEC

4.7 Ge eral er or indic tions in the re pons me s g s

As previou ly noted, b sides the data b in returned alon with an p s ible er or

notification , every resp n e mes age is exp cted to contain an in ication of the overal

s c es or otherwise of the req est The resp n e mes age may also in icate whether this is

the only mes age b in sent or if it is one of several resp n e mes ages cau ed by a sin le

req est In the lat er case it may also in icate whether it is the last the series of resp n es or

whether further mes ages are to b exp cted

The in ication of overal s c es or fai ure an the in ication of whether further mes ages are

to b exp cted are placed in the < e ly < e u t> element, of whic there mu t b exactly

one oc ur en e, together with one or more se arate < e ly <Er o > elements For example,

in Fig re 12 the < e ly element sig ifies the s c es of the req est

Figure 12 – Ex mple of ov ral indic tion of s c e s in a Reply eleme t

Becau e of the neces ity of in lu in these ad itional < e ly < e u t> an

< e ly <Er o > elements, the XML fragment s own in Fig re 9 s ould actual y re d as

Fig re 13 – Ex mple of er or indic tions in a Reply eleme t (cor e te )

In the a ove example the < e ly < e u t> element ta es the value FAI ED rather than O

This is b cau e of the fatal er or notification as explained b low

4.7.2 Set in the <Reply <Re ult> eleme t

The rules for set in the < e ly < e u t> element are as fol ows:

value 0.0 as s own in Fig re 12 This code is defined by An ex B of IEC 619

8-9:2 13 as me nin “er or fre s c es ”

Su h a mes age may also contain informational (non- atal) con ition For e c

informational con ition b in re orted, in lu e a < e ly <Er o > element an set the

< e ly <Er o > cod >, < e ly <Er o > ID an other as ociated

< e ly <Er o > stru ture at ributes a pro riately as des rib d a ove

• Otherwise, if the entire resp n e to the req est mes age is b in returned in a sin le

mes age an the resp n e mes age contain at le st one fatal er or then set

< e ly < e u t> to FAI ED

Su h a mes age may contain a mixture of data items an er or notification For e c

fatal er or or informational con ition b in re orted, in lu e a < e ly <Er o >

element an set the < e ly <Er o > cod >, < e ly <Er o > ID an other

as ociated < e ly <Er o > stru ture atributes as des rib d a ove

• Otherwise set the < e ly < e u t> element to PA TIAL This in icates that the

resp n in s stem is sen in multiple resp n e mes ages to the req est mes age

Su h mes ages may contain a mixture of data items an er or notification

There mu t b at le st one < e ly <Er o > cod > element of 0.1 or 0.2 These are

defined in An ex B of IEC 619 8-9:2 13 as the codes for “p rtial s c es (ad itional

res lts con eyed in se arate mes ages)” an “p rtial s c es (no further res lts to

fol ow)” resp ctively

If the resp n in s stem can ot determine whic is the last mes age in a set of

< e ly <Er o > cod > of 0.1

Also in lu e a < e ly <Er o > element an set the < e ly <Er o > cod >,

< e ly <Er o > ID an other as ociated < e ly <Er o > stru ture at ributes (as

des rib d a ove) for e c fatal er or or informational con ition b in re orted

4.7.3 Multiple re p ns me sa e

As noted previou ly, it is p s ible for a sin le req est to cau e multiple resp n e mes ages

to b generated As des rib d in 4.7.2, a resp n in s stem sets the < e ly < e u t> to

PA TIAL an the < e ly <Er o > cod > element to either 0.2 or 0.1, de en in on

whether this is the last mes age in the seq en e or not

It mig t a p ar that the < e ly < e u t> an < e ly <Er o > cod >

elements s ould s fice for a cl ent (receivin ) s stem to detect when it has

o tained al mes ages b lon in to a multiple mes age resp n e However,

this is true only if the u derlyin tran p rt mec anism g arante s that

mes ages are received in the same order in whic they are tran mit ed an

this may not alway b the case Unfortu ately IEC 619 8-9 an IEC 619

8-10 provide no normative me n for a cl ent to detect when it has received al

mes ages b lon in to a multiple mes age resp n e It is lef to the

implementer to devise his own s heme One p s ible way is to u e the

<H a er <Pr p rt e > element to in lu e a seq en e n mb r an a “last

mes age” flag

4.8 Multiple <Re ue t>, <Reply a d <Pa loa > eleme ts

The Me s ge.xs s hema definition fi e al ows a sin le mes age to contain more than one

s b lement within e c < e u s >, < e ly or <P yloa > element

In the case of a req est mes age, multiple s b lements within the < e u s > element are

tre ted as in e en ent req ests That is, it is tre ted as thou h the variou req ests had

b en sent in se arate mes ages Simi arly, a re ly mes age or event mes age containin

multiple s b lements in ide the < e ly or <P yloa > elements is con idered as several

Bu dl n several resp n e p ylo d into one mes age may give rise to

ambig ity when tryin to matc these to the a pl ca le < e u s > element

4.9 Impleme tation-spe ific me s ge

An IEC 619 8-9 mes age may b formulated in way that go b yon the stan ard Su h a

mes age is val d ac ordin to the XML s hema definition but its semantic are u defined

This may ha p n as folows

• First, as noted a ove, a mes age may contain several < e u s > or <P yloa >

elements within the same mes age In s c a case, only those elements that matc

the verb an nou combination in the mes age he der have an me nin ac ordin to

IEC 619 8-9 (Subclau e 3.4.2)

Elements that do not matc the given verb an nou combination may also b in lu ed

in the same mes age but their semantic are then u defined

• Secon , a <Nou > element in the mes age he der may also ta e on a value not

recog ized by the IEC Su h a mes age is legal ac ordin to the XSD s hema

val dation but its semantic are not defined (It is not p s ible for the < erb> element

to b simiarly u con trained b cau e the set of verbs is defined as a XSD

en meration typ rather than as a simple strin )

In b th cases, the me nin as rib d to s c mes ages is implementation sp cific Unles

there are overwhelmin ly go d re son , their u age is not recommen ed

Implementation sp cific p ylo d s ould in an case u e an organization-sp cific XML

namesp ce in order to en ure there is no confu ion an to emphasize that a non-stan ard

exten ion is b in u ed

5 The naming of objects

IEC 619 8-9 enforces a con istent s heme for namin o jects s c as meters an other

hardware devices

5.2 Naming meters

Cle rly a meter re d req est mu t b a le to sp cify the meters to whic the req est p rtain

The cor esp n in resp n e to s c a req est mu t simiarly b a le to identify the meters

This impl es the neces ity of an agre d an u ambig ou namin s heme b twe n sen in

an receivin s stems

For example, as noted in Subclau es 6.3 an 6.5, a meter re d req est an re d resp n e

sp cifies the meters of interest in the <E dDevi e>, <E dDevi e r u >, <U age oi t> an

<U age oi t r u > elements Eac one of these elements has a simi ar s hema definition

as de icted in Fig re 14

Fig re 14 – EndDe ic definition

Ac ordin to this s hema definition, an En Device, for in tan e, may b sp cified either as a

< RID (master resource identifier) element or as a <N me > n me> element IEC 619 8-9

states that a mRID mu t b provided as a 12 -bit u iversal y u iq e identifier or UUID In

other word , a mRID may not b ju t a simple meter identifier or serial n mb r (This

IEC

however b an as et management s stem or some other s stem whic ef ectively own the

meters an can as ig these mRIDs)

Alternatively, the meter identifier mu t b sp cified in an <E dDevi e> N me > n me>

element If this name is not u iq e, an o tional <E dDevi e> N me > N meT p > n me>

element may also b sp cified to resolve an p s ible ambig ity If this sti res lts in a

p tential confl ct, a <E dDevi e> N me > N meT p > N meT p Au ho i y <n me> element

may also b sp cified

In general, a given En Device or other o ject may b known by several names

Whic ever way the names are sp cified in a req est mes age, the sen in an receivin

s stems mu t cle rly agre on a common and u eq ivocal s heme for identifyin meters

NameTyp Authority is s own in Fig re 15 In this example the given meter is known by two

Figure 15 – Ex mple of a Meter Re d Re u st with NameType a d NameTypeAuthority

5.3 EndDe ic Groups, Us gePoints a d Us gePointGroups

• An <E dD vi e cor esp n s to an actual piece of hardware s c as a meter.

• An <E dD vi e r up is a me n for a GetMeterRe din s req est to refer to a

predefined – that is, named – set of en devices A meter re din req est in whic an

<E dDevi e r u > is sp cified refers to al the en devices in that group

• A < s g P i t> me n the location where one or more en devices exist

• A < s g P i tG oup denotes a set of u age p ints

5.4 Naming of other obje ts

Names may also b u ed for other kin s of o jects within IEC 619 8-9 For example,

Re din Typ values, Re din Qual ties, En DeviceEvents an En DeviceControls are amon

the kin s of o ject that can b as ociated with a mnemonic name This is des rib d further in

Subclau e 6.5.7

5.5 Provisionin a d inter ogating a s stem

Clau e 8 des rib s how a HES or MDMS s stem may b config red with ad itional

En DeviceConfig an UsagePointConfig resp ctively Simi arly, a s stem may b inter ogated

a out the En Devices an UsagePoints it knows a out u in GetEn DeviceConfig an

GetUsagePointConfig mes ages

For En DeviceGroups an UsagePointGroups, the cor esp n in mes age typ s are

En DeviceGroups, GetEn DeviceGroups, UsagePointGroups an GetUsagePointGroups

The IEC 619 8-9 sp cification al ows for several kin s of meter re d req ests to a HES or

MDMS These variou , overla pin u e cases are as fol ows:

• For a historic l meter re d re ue t, the HES return whatever data it may have in its

data ase of stored meter values

• An interv l re d is a set of me s rements at reg lar intervals over some defined

me s rements every ten min tes for the p riod of mid ay to mid ig t of the previou

day

• A loa profi e re d req est is an interval re d where the u its of me s rement are

related to energ con umption

• A coin ide t re d req est is a req est for data not at an explcit time but rather when

some other re din was made or when a certain event oc ur ed

• An on-dema d meter re d in tru ts the HES to return the req ested values avai a le

for a given meter by directly askin the meter This forces the meter data to b

o tained from the meter rather than from its internal data ase of stored meter values

• An un ol cite meter re d is made without an explcit req est havin b en made

In te d the meterin s stem initiates the re d by itself

This clau e des rib s how the diferent mes age ex han e p tern lo k (6.2) It then

des rib s how the contents of the variou req est (6.3) an re ly mes ages (6.4) are

formulated On-deman meter re d req ests are a sp cial case (6.4) Un ol cited meter re d

mes ages are also dis u sed (6.6)

6.2 Me s ge e c a g pat erns

There are thre common mes age ex han e p t ern relatin to how a req est for meter data

an the cor esp n in resp n e are made These are as fol ows:

• Re ue t me s g with a sin le re pon e me s ge This is the simplest case It is

des rib d in 6.2.2

• Re ue t me s ge with multiple re pon e me s ge Se 6.2.3

The first two of these mes age ex han e p t ern are simi ar to one another In b th cases,

the MDMS sen s a meter re d req est to a HES The HES then val dates this req est

As umin that the req est mes age s p l es s ficient information to proces the req est

alon with val d meter identifiers, the HES then go s to the AMI network to re d the

cor espon in values for the meters in q estion As these data are received, the HES sen s

one or more re ly(MeterRe din s) resp n e mes ages b ck to the MDMS

(The con ention re ly (MeterRe din s) is u ed to clas ify the mes age ac ordin to the verb

an nou in the he der.)

These two cases may b further s bdivided ac ordin to whether an on-deman meter re d is

b in made or not The main dif eren e b twe n an on-deman an other kin s of meter re d

req ests l es in the way the req ests are formulated That is, the mes age ex han e p tern

are the same but the detai s of the req est mes ages are dif erent This is explained in

Subclau e 6.4

6.2.2 Re ue t me s ge with a single re pons me s ge

The relevant seq en e diagram is s own in Fig re 16

The cor esp n in ste s are as fol ows:

1) The MDMS sen s a get MeterRe din s) req est to the HES The detai s of how this

req est is put together are explained in Subclau e 6.3

2) The HES val dates the req est If the req est can ot b proces ed at al – either

b cau e es ential information is mis in or the req est sp cifies only in al d or non

-existent meter identifiers – then it sen s a re ly(MeterRe din s) resp n e mes age to

the MDMS with the < e ly < e u t> element set to FAI ED alon with the

a pro riate detai s (4.7) At this p int proces in of this req est then sto s

3) Otherwise, for those meters that it do s know a out, the HES sen s the a pro riate

comman s over the AMI network to in tru t the meters to provide the req ested

information De en in on the exact req est, this may ha p n straig t away or at

some time in the future

4) The meters car y out these req ests an return information b ck to the HES

5) The HES con ol dates al the meter resp n es into a sin le re ly(MeterRe din s)

mes age whic it then sen s b ck to the MDMS If the lat er contain no fatal er ors,

the < e ly < e u t> element is set to O (4.3) Otherwise this element is set to

FAI ED (4.5)

The es en e of this mes age ex han e p t ern is that one req est generates a sin le

resp n e mes age The later may contain meter data, er or notification or a combination of

b th (4.4)

Figure 16 – Me s ge e c a ge pat ern for a meter re d re ue t

with a single re p ns me s ge

6.2.3 Req e t me s ge with multiple re pons me s g s

The diferen e b twe n this mes age ex han e p t ern an that outl ned in 6.2.2 is that, for

this case, a req est may cau e several resp n e mes ages to b generated

The relevant seq en e diagram is s own in Fig re 17

[Re u st is in ld or s cifie al in ld ( no -eistet meters]

[Re u st is vld a d s cifie at le st sme vld ( existe tmeters]

al

[sme meter re d faie ]

[al meter re d s c d d]

R eply mesa co tains mixture of meter dta a ls

of in ld meteror meterfor which th re s faie

R eply mesa co tains meter dta o ly

g t( MeterRe din s)

re ly( MeterRe din s, <Rely Re lt> OK)

re ly( MeterRe din s, <Rely Re lt> F ILE )

re ly( MeterRe din , <Re ly Re lt> F ILE )

The ste s are as fol ows:

1) The MDMS sen s a get MeterRe din s) req est to the HES The detai s of this

req est are explained in Subclau e 6.3

2) The HES val dates the req est As in the previou case, it may b that no proces in

can b p rformed at al in whic case it sen s a re ly(MeterRe din s) resp n e

mes age with the < e ly < e u t> element set to FAI ED alon with the a pro riate

detai s (4.7) At this p int proces in of this req est sto s

3) Otherwise, the HES then sen s a re ly(MeterRe din s) b ck to the MDMS This may

contain a l st of meter-id for whic the HES is u a le to provide information, if an

(4.7) Becau e the HES exp cts to sen further re ly(MeterRe din s) resp n e

mes ages it sets < e ly < e u t> element set to PA TIAL (4.7.3)

4) For those meters that it do s know a out, the HES sen s the a pro riate comman s

over the AMI network to in tru t the meters to provide the req ested information

De en in on the exact req est, this may ha p n straig t away or at some time in the

future

5) The meters car y out these req ests an return information b ck to the HES

6) The HES sen s one or more re ly(MeterRe din s) resp n e mes ages b ck to the

MDMS Again, these have their < e ly < e u t> elements set to PA TIAL The

< e ly <Er o > cod > element has the value 0.1 for al mes ages ex e t the last

for whic this element is given a value of 0.2 (4.7.3)

Althou h this is a sl g tly more complcated mes age ex han e p tern than that outl ned in

Subclau e 6.2.2, it p s ibly al ows for a simpler implementation in ide the HES The later

can return data b ck to the MDMS as so n as they are received from the meters

Alternatively, the HES can con ol date data an er or notification into larger mes ages if it

so prefers

Figure 17 – Me s ge e c a ge pat ern for a meter re d re ue t

with multiple re pon e me s ge

A get MeterRe din s) req est mes age is sent to a HES to in tru t the HES to resp n with

the req ested meter re d data

IEC

s Meter re re e t (multiple repn me a s)

H S

HE valdates re est

HE se s rely mes g with lst of n n-eistet meter( if aplcble)

R eply mes g co tains lst of n -eistet meter, if an

HE isus com an a os AMI ntwork

to read o or more meter

R ead meter

R eply mes gs co tain mixture of meter data

an lst of meterwhich fie to read corectly

lo

[o r meters]

al

[re u t is in ld or s cifie al in ld ( no-eiste tmeters]

[re u t is vld a s cifie at le t sme vld ( existin) meters]

rely( MeterRe din s, <Re lt> Re ly P R IAL)

re ly( MeterRe in , <Re lt>Re ly FILE )

g t( MeterRe in s)

re ly( MeterRe in s, <Re ly Re lt>P R IAL)

The verb an the nou in the mes age he der are ge an Me er e d ngs resp ctively The

data in the < e u s > element des rib s what data are to b returned to the req estin

s stem

The < e u s > element is exp cted to contain one or more <G tMe er e d ngs>

s b lements In gra hical terms e c <G tMe er e d ngs> element has a s hema definition

as s own in Fig re 18

The fol owin s b lements sp cify the meters to whic the req est p rtain :

• <E dD vi e This sp cifies the in ivid al logical identities of the meters for whic

data are b in req ested

• <E dD vi e r up This sp cifies the identities of the meters by their group

identifiers

• < s g P i t> This sp cifies the u age p ints of the meters

• < s g P i tG oup This sp cifies the u age p ints by their group identifiers

These s b lements al s are the same kin of namin stru ture, as explained in Clau e 5

The fol owin s b lements sp cify fi terin criteria again t whic the returned data are

matc ed:

• < ea i g y e This sp cifies the kin of meter data b in req ested Se Subclau e

6.3.3

• < ea i g u l ty This sp cifies that only meter re din values that matc certain

q al ty con traints s ould b returned (6.3.4)

• < im S hed le This sp cifies the p riod of interest for whic data are b in

req ested (6.3.5)

• < ete R a i gs> This is u ed for ma in a coin ident meter re d req est As noted

a ove, a coin ident meter readin is one whose time is sp cified when another re din

was made or event has ta en place

• < ra sf r e Ta k This sp cifies a meter/ ran former relation hip, if an It u ual y

refers to the meter’s upstre m service tran former secon ary win in This

relation hip is u eful for outage an l ne-los ( hef ) analy is

The remain er of this clau e dis u ses the variou s b lements that may a p ar in a

<G tMe er e d ngs> req est These are covered in more detai in 1 2.2

<G tMe er e d ngs> element rather than < e er e d ngs> to hold the

req est data