IS DLMS/COSEM SUITABLE FOR SIMPLE METERS?

While DLMS/COSEM is able to support a very rich feature set, it is also suitable for simple metering equipment !his is possible because there are only a fe" man#atory elements So very simple #evices can be mo#elle# $ or "hen ta%ing more options, very comple& ones as "ell On the mo#el level, the only man#atory element is the management logical #evice, "hich may be the only one !his must contain a S'( assignment ob)ect hol#ing the S'(*s of all logical #evices Each logical #evice must have an ob)ect hol#ing the logical #evice name, an# a current association ob)ect, so that the list of ob)ects available can be retrieve# +or simple #evices "ith small memory resources, pre*establishe# associations can be #efine# !he management logical #evice must support an association "ith a public client, allo"ing the retrieval of the structure of an un%no"n meter Everything else is left to the choice of the implementer SHORT NAME OR LOGICAL NAME REFERENCING? 'ny piece of information mo#elle# by COSEM can be accesse# as an attribute or metho# of a certain COSEM interface ob)ect !o access an attribute or metho#, it has to be referenced. ,n the metering equipment -server. the COSEM application layer provi#es t"o mechanisms to access the attributes One is calle# short name -S/. referencing an# the other is calle# logical name -L/. referencing !he #ata collection system -client. application layer al"ays uses L/ referencing When S/ referencing is use#, the attributes an# metho#s of each interface ob)ect are mappe# to DLMS named variables !his is #one #uring the #esign of the meter Each name# variable is i#entifie# "ith a short name, "hich is a 01 bit unsigne# integer 'ttribute 0, the logical name of the ob)ect is mappe# to a DLMS name# variable i#entifie# by a base name E&cept in the case of a fe" special ob)ects, there are no general rules #efine# for assigning base names 'll other attributes an# metho#s of the ob)ect are then also mappe# to DLMS name# variables !he offsets bet"een the base name an# the short name i#entifying the other attributes an# metho#s are #efine# in the #efinition of each interface class !he actual values of the short names thus #epen# on the number an# %in# of ob)ects instantiate# an# the mapping strategy use# !he base names allocate# in the metering equipment can be retrieve# by rea#ing the ob)ect2list attribute of the S/ 'ssociation ob)ect When S/ referencing is use#, the DLMS name# variables are accesse# by the stan#ar# DLMS 3E'D an# W3,!E services When L/ referencing is use#, attributes an# metho#s are accesse# via the logical name of the ob)ect, specifying the in#e&-es. of the attribute-s. an#/or the metho#-s. Logical names are #efine# by O4,S When L/ referencing is use#, the attributes an# metho#s are accesse# by the &DLMS 5E!/SE! an# 'C!,O/ services 's the #ata collection system -client. application layer al"ays uses L/ referencing, the L/ service requests are mappe# to S/ service requests by the Short /ame Mapper service element of the application layer S/ referencing has been inherite# from the original DLMS stan#ar# L/ referencing is the result of the evolution of the specification Which is the better6 !he ans"er is none of them Simply put, S/ referencing is more suitable for simple #evices an# L/ referencing for comple& #evices !he use of short names limits the possible number of ob)ects "ithin a logical #evice Depen#ing

on the comple&ity, an interface ob)ect occupies a range of 7 -Data. to 081 -Cloc%. short names, starting "ith the base name !he "hole range available is 709: !herefore, the ma&imum number of ob)ects #epen#s on the type -comple&ity. of ob)ects use# an# the strategy of allocating base names On the other han#, '(D;*s for S/ referencing are shorter than '(D;*s for L/ referencing With L/ referencing, the limit is only set by the possible O4,S names -in principle :<1==1. !here are a fe" a#vance# features available only "ith L/ referencing >o"ever, this "ill ma%e the soft"are of the meter slightly more comple& +inally, it is important to note, that the referencing style an# the correspon#ing service set is negotiate# at application association establishment an# thus interoperability is fully preserve# !here are %no"n both comple& an# simple metering equipment using either S/ or L/ referencing, en# even meters using both referencing styles WHAT IS THE PURPOSE OF THE UPPER HDLC ADDRESS? DLMS/COSEM is base# on the Client/Server para#igm, "here the #ata collection system acts as the Client an# the metering equipment acts the Server, provi#ing services to the Client !he Server is mo#elle# as a physical #evice containing one or more logical #evices, each logical #evice supporting one or more application associations "ith the Client-s. an# t"o or more COSEM ob)ects ,n the three*layer, connection oriente#, >DLC base# communication protocol, a##ressing is performe# by the M'C layer !he lo"er >DLC a##ress is use# for a##ressing the physical #evice an# the upper >DLC a##ress is use# for a##ressing the various logical #evices "ithin the same physical #evice 'pplication associations are establishe# bet"een a Client an# a Logical Device in the Server !he associations are i#entifie# by the pair of >DLC a##resses -Client >DLC a##ress $ Server lo"er >DLC/upper >DLC a##ress. !he >DLC base# #ata lin% layer supports the lo"er >DLC/upper >DLC a##ress structure by using the e&ten#e# a##ressing mechanism provi#e# by the >DLC stan#ar# ,SO/,EC 08:89 ,t is to be note#, that for the purposes of DLMS/COSEM a ne" frame format type 8, containing both the source an# the #estination a##resses have been a##e# to ,SO/,EC 08:89 ,n a full OS, protocol stac% the ?!ransport Services 'ccess (oint@ has the same role as the upper >DLC a##ress in the three*layer, connection oriente#, >DLC base# protocol stac% use# "ith COSEM !S'( is a point in the transport layer of an OS, base# pro#uct that can be accesse# for a##ressing purposes !his a##ress can be use# in a##ition to the main net"or% a##ressing ;sing a non*OS, e&ample, the role of the upper >DLC a##ress is similar to the ?port number@ ' computer, a single physical #evice is running various applications li%e "eb, mail, ftp !he computer can be accesse# using its ,( a##ress, an# the various applications $ "hich are similar to DLMS/COSEM logical #evices * can be accesse# using their port numbers Many people %no" that the assigne# port number for Worl# Wi#e Web >!!( is 7A an# the stan#ar# port for Simple Mail !ransfer (rotocol is :< What is the purp se ! the "a#a$e"e#t % $i&a% 'e(i&e? Simply spea%ing, the management logical #evice is the logical #evice, "hich must al"ays be present in the physical #evice, an# for "hich the upper >DLC a##ress A&A0 is reserve# !o#ay it is very common that a single physical metering equipment han#les multiple metering tas%s ' simple e&ample is a heat meter "ith a pulse input for a "ater*metering

#evice ' more comple& e&ample "oul# be a concentrator han#ling #ata for a number of meters 'ccor#ing to the DLMS/COSEM meter mo#el, each set of metering #ata is han#le# by a logical #evice implemente# in a physical #evice !he question is no" ho" to %no" ho" many logical #evices are insi#e the physical #evice6 We nee# a BporterC or BconciergeC to as% !his is the tas% of the management logical #evice !he management logical #evice must have a S'( assignment ob)ect, "hich contains the list of all logical #evices an# their S'( a##resses "ithin the physical #evice !he management logical #evice must support an application association to a public client, "ith the lo"est security level !he client a##ress A&0A is reserve# for the public client ,n case of L/ referencing, the S'( assignment ob)ect has a pre#efine# logical name ,n case of S/ referencing, the base2name of the S'( assignment is pre*#efine# as A&+CAA 's the only man#atory logical #evice is the management logical #evice, it is possible that this is the only logical #evice in the meter an# it contains the metering #ata as "ell >o"ever, this "oul# be a hac% violating the spirit of COSEM ' much better approach "oul# be to @mirror@ the management logical #evice on another upper >DLC a##ress as the metering logical #evice !he overhea# of such a solution is very small WHAT IS THE PURPOSE OF THE PUBLIC CLIENT? !he purpose of the public client is to support the retrieval of the structure of an un%no"n meter !he Client a##ress A&0A is reserve# for the public client !he management logical #evice, having a reserve# upper >DLC a##ress A&A0 must support an application association to this public client "ith lo"est security !he S'( a##resses of all logical #evices can be foun# by rea#ing the S'( assignment ob)ect !he list of ob)ects available -in case of S/ referencing, "ith their base names. an# the access rights to their attributes an# metho#s can be retrieve# by rea#ing the ob)ect2list attribute of the application association THE ASSOCIATION OB)ECTS* WHAT ARE THE+? ,n DLMS/COSEM, the association ob)ects play a role of a Bgate%eeperC, controlling access to the information in the meter an# provi#ing information on "hat is available 's there are t"o referencing metho#s, there are also t"o types of association ob)ects, one for Short /ame an# one for Logical /ame referencing 'lthough they perform the same tas%, the 'ssociation S/ an# the 'ssociation L/ ob)ects are slightly #ifferent !he logical name of the current association ob)ect is A A DA A A :<< ,n case of S/ referencing, the base2name of the current association ob)ect is A&+'AA Several instances of association ob)ects are possible +or their i#entification, the value group E is use# 't a time, there is only one association in a logical #evice, "hich is current !his is to avoi# the comple&ity of safe Bmulti*userC #ata han#ling in a meter On the other han#, nothing forbi#s having access at the same time to multiple logical #evices, if this is supporte# by the lo"er layers

4oth the 'ssociation L/ an# S/ ob)ects have an ob)ect2list attribute, provi#ing the list of interface ob)ects BvisibleC in the given association ,n case of L/ referencing, the ob)ect2list provi#es the class2i#, the version, the logical2name an# the access rights to the attributes an# metho#s for each ob)ect ,n case of S/ referencing, the ob)ect2list provi#es the base2name, the class*i#, the version an# the logical2name of each ob)ect !o retrieve the access rights, the get2attributesEmetho#s metho# can be use# Default access right may be use# -e g rea# only to attributes, no access to metho#s. !he 'ssociation L/ ob)ect also hol#s the information about the associate# partners -client* logical #evice., the application conte&t, the &DLMS conte&t, the authentication mechanism, the LLS secret -"hen this mechanism is use#. an# the association status !he metho#s of the 'ssociation L/ ob)ect support >igh Level Security 'uthentication an# allo" a##ing ob)ects to the ob)ect2list or to remove them !he metho#s of the 'ssociation S/ ob)ect support rea#ing ob)ects by their logical name, to retrieve access rights an# they also support the >igh Level Security 'uthentication process HOW TO CONNECT A LOGICAL DE,ICE? !here are t"o #ifferent situationsF the first being, that the #ata collection system -client. %no"s the structure of the metering #evice -server. an# the secon# that the #evice is un%no"n to the client !he client must %no" in a#vance the physical #evice a##ress, "hich is the lo"er M'C a##ress of the #evice if it is connecte# to a L'/, e g "hen multi*#rop is use# ,n case of mo#em connection, the telephone number an# the mo#em connection parameters nee# to be %no"n ,f security mechanisms are use#, the pass"or# or the BsecretC nee#s to be %no"n as "ell When the structure of the metering #evice is %no"n, the process is the follo"ing 0 Connect the physical layer Optionally, negotiate the protocol stac% : Connect the #ata lin% layer using the %no"n lo"er >DLC a##ress an# the %no"n upper >DLC a##ress of the selecte# logical #evice "ithin the physical #evice Optionally, negotiate #ata lin% layer parameters 8 Establish the application association, negotiate the application conte&t -S/ or L/ referencing., the &DLMS conte&t an# perform authentication, using the %no"n pass"or# or >LS secret D 'ccess the selecte# attributes an# metho#s, using the appropriate service set !his is 5E!/SE!/'C!,O/ "hen using L/ referencing an# 3E'D/W3,!E "hen using S/ referencing < !erminate the #ata lin% layer connection $ this "ill release the application association as "ell $ an# establish another association or terminate the physical connection !he actions to perform "hen the structure of the metering #evice is not %no"n are more complicate# !hey "ill be as follo"sG 0 Connect the physical layer Optionally, negotiate the protocol stac% : Connect the #ata lin% layer using the reserve# a##ress of the public client -A&0A., the lo"er >DLC a##ress of the physical #evice an# the upper >DLC a##ress of the management logical

#evice -A&A0. Optionally, negotiate #ata lin% layer parameters 8 Establish the application association, negotiate the application conte&t -S/ or L/ referencing. an# the &DLMS conte&t /o authentication is require# D 'ccess the S'( assignment ob)ect -in case of L/ referencing, logical name A A D0 A A :<<., in case of S/ referencing A&+CAA. to retrieve the list of logical #evices an# their S'(*s !he S'(2assignment2list attribute #elivers the S'( of each logical #evice "ith its logical2#evice2name When short name referencing is use#, the base2name of the COSEM logical #evice name ob)ect is A&+DAA < Disconnect the #ata lin% layer an# connect again using the a##ress of the appropriate client a##ress an# the upper >DLC a##ress of the logical #evice selecte# 1 Establish the application association, negotiate the application conte&t -S/ or L/ referencing., the &DLMS conte&t an# perform authentication -pass"or# must or >LS secret must be %no"n. H 3etrieve the ob)ect*list from the association ob)ect "ith access rights to attributes an# metho#s 7 4ro"se through the list an# fin# the ob)ects of interest in the logical #evice 9 'ccess the selecte# attributes an# metho#s using the appropriate service set !his is 5E!/SE!/'C!,O/ "hen using L/ referencing an# 3E'D/W3,!E "hen using S/ referencing 0A !erminate the #ata lin% layer connection $ this "ill release the application association as "ell $ an# establish another association or terminate the physical connection !he physical #evice may support installation of the metering #evice by calling in to the #ata collection system "hen it is installe# WHAT IS THE LOGICAL DE,ICE NAME? !he logical2#evice2name is use# for a "orl#*"i#e unique i#entification of each logical #evice ,t is an octet*string up to 01 octets !he first three octets uniquely i#entify the manufacturer of the #evice ,t is assigne# by the DLMS ;' in co*operation "ith the +L'5 'ssociation !he manufacturer is responsible for guaranteeing the uniqueness of the octets that follo" -up to 08 octets. !he logical #evice name is hel# by the S'( assignment ob)ect or a COSEM logical #evice name ob)ect * a #ata or register ob)ect "ith the logical name A A D: A A :<< When short name referencing is use#, the base2name of the COSEM logical #evice name ob)ect is A&+DAA SECURIT+ FEATURES* WHAT IS SUPPORTED B+ COSEM? DLMS/COSEM brings enhance# security features by provi#ing a controlle# access to the #ata store# in the meter using #ifferent levels of authentication On monopoly mar%ets, only the utility ha# to have access to the #ata in the meter an# it "as entitle# to see all #ata On #eregulate# mar%ets, various parties nee# access to the information an# normally they have rights to access a subset of #ata only !his mar%et nee# is supporte# by controlling the access "ith the association objects !he association ob)ect provi#es #ifferent vie"s of the information to the #ifferent clients, un#er the appropriate authentication mechanism

!he association may be establishe# "ith lo"est level security, lo" level security or high level security Lo"est level security is mainly use# to support the retrieval of the structure of a meter un%no"n for the #ata collection system Lo" level security -LLS. provi#e a pass"or# base# authentication of the client ,t is typically use# "hen the communication channel offers a#equate security to avoi# eaves#ropping an# message -pass"or#. replay >igh level security ->LS. is a four*pass authentication, using cryptographic algorithm an# secret cryptographic %eys With >LS, both the Client an# the Server authenticates itself !his authentication mechanism is use# in the case "hen the communication channel #oes not offer a#equate security to avoi# eaves#ropping an# message -pass"or#. replay !he DLMS/COSEM specification #oes not specify #etails of the >LS mechanism ,n a##ition, encryption can be use# !his is provi#e# by the &DLMS service element of the application layer OBIS NAMES* WHAT ARE THE+? O4,S stan#s for Ob)ect ,#entification System O4,S provi#es stan#ar# i#entifiers for all #ata "ithin the metering equipment, both measurement values an# abstract values O4,S names are use# for the i#entification of COSEM ob)ects an# also for i#entification of the #ata #isplaye# on the meter an# transmitte# through the communication line to the #ata collection system !he nee# for stan#ar# i#entification systems has been i#entifie# "ith the a#vent of comple& multifunctional meters, "hen a great number of #ata ha# to be rea# an# transmitte# Some countries have create# their o"n stan#ar#s, but most manufacturers use# proprietary systems One of the "i#ely recognise# systems "as the Energy Data ,#entification System -ED,S. #efine# in 5ermany !his system has been pic%e# as the basis of O4,S O4,S uses si& value groups in a hierarchical structure Ialue group ' i#entifies the energy type measure# 'JA i#entifies abstract co#es Ialue group ' has reserve# space for future e&tensions Ialue group 4 i#entifies the measuring channels Ialue group C i#entifies the physical quantity measure#, "hile value group D i#entifies the processing metho#s an# country specific co#es Ialue group E is use# for i#entifying rates or can be use# for further classification Ialue group + is use# for i#entifying historical values or can be use# for further classification 5roups 4 to D have co#e space for manufacturer specific i#entifiers Stan#ar# co#es for electricity, col# "ater, hot "ater, gas, heating an# cooling are #efine# in the DLMS ;' 4lue boo% ' list of full stan#ar# O4,S co#es, vali# combinations of stan#ar# values in each group, is maintaine# by the DLMS ;' !he list is available on the DLMS ;' "eb*site an# it is regularly maintaine# !he DLMS/COSEM conformance tool chec%s the logical name of each ob)ect foun# in the meter un#er test base# on this table MANUFACTURER SPECIFIC OB)ECTS* ARE THE+ POSSIBLE? DLMS/COSEM provi#es a rich set of stan#ar# ob)ects to support a "i#e functionality of metering equipment >o"ever, in or#er to support innovation, manufacturer specific ob)ects can be #efine# an# use# !hese "ill be i#entifie# by manufacturer specific O4,S co#es 'n O4,S co#e is manufacturer specific, if any of the value groups 4 to D has a value bet"een 0:7 an# :<D ,n or#er to maintain interoperability, manufacturer specific ob)ects shoul# not be use# for a purpose for "hich a stan#ar#ise# ob)ect is #efine# ,n or#er to allo" interpretation of manufacturer specific ob)ects by the #ata collection system, e&tra information is nee#e#

,t is to be note# that manufacturer specific ob)ects shall be still instances of stan#ar# interface classes an# the type of the attributes is teste# by the C!! On the other han#, manufacturer specific attributes an# metho#s are allo"e# What e%e"e#ts ! the spe&i!i&ati # #ee' t -e re$istere'? !here are a number of elements in the specification, "hich nee# to be registere#

!hese are the follo"ingG Direct local #ata e&change -,EC 1:A<1*:0. * ManufacturerKs i#entification Direct local #ata e&change -,EC 1:A<1*:0. * Enhance# i#entification character (hysical layer -5reen boo% / ,EC 1:A<1*D:. * ,#entifiers for protocol i#entification service Data lin% layer -5reen boo% / ,EC 1:A<1*D1 * LLC parameters 'pplication layer -5reen boo% / ,EC 1:A<1*<8. * COSEM 'pplication conte&t name 'pplication layer -5reen boo% / ,EC 1:A<1*<8 * COSEM 'uthentication mechanism name O4,S co#es -4lue boo% / ,EC 1:A<1*10. * Stan#ar# O4,S co#es ,nterface classes -4lue boo% / ,EC 1:A<1*1:. * COSEM Logical #evice name ,nterface classes -4lue boo% / ,EC 1:A<1*1:. * Stan#ar# interface classes an# versions

!he registration services are provi#e# by the DLMS ;' !he lists of registere# elements are available on the "eb*site of the DLMS ;', un#er ?Documentation@ HOW CAN A METER REPORT AN E,ENT? Events in the server may occur any time an# they have to be reporte# to the client !his is al"ays #one by the server management logical #evice -a##ress A&A0. to the client management application process -a##ress A&A0. ,n case of using the three*layer, connection*oriente#, >DLC base# protocol stac%, the process is the follo"ing !he lo"er layers may not be able to sen# the message out, e g the physical connection may not e&ist, or if the #ata lin% layer #oes not have the to%en ,f the physical connection #oes not e&ist, it is initiate# by the server Once the physical connection * inclu#ing the i#entification service * is #one, the Event/otification request '(D; is sent to the #ata lin% layer, "here it is pen#ing, "aiting for a sen# opportunity !he server, #etecting the event may be in a multi*#rop configuration When the client receives a call, it has to fin# out, "hich server on the multi*#rop "as calling !herefore, it buil#s a DL connection, using a special lo"er >DLC a##ress, the C'LL,/5 (hysical a##ress -A&HE resp A&8++E. an# as upper >DLC a##ress, the management logical #evice a##ress Only the physical #evice calling in "ill respon# an# buil# the #ata lin% layer connection ,f the server has no right to tal%, the client has to trigger sen#ing out the pen#ing (D; !his is #one by sen#ing an empty ;, frame to the server "ith the (/+ bit set to 0, giving the permission to the server to sen# !he pen#ing (D; is sent in a ;, frame, an# upon its reception, it is passe# on to the Client management application process !he Client '(, #epen#ing on the content of the Event/otification, may #eci#e "hat to #o ne&t

With lo"er layers other than >DLC, the authorisation to sen# out the pen#ing Event/otification (D; may be #ifferent ARE E.AMPLES FOR INFORMATION E.CHANGE A,AILABLE? E/a"p%es ! r DLMS/COSEM i#! r"ati # e/&ha#$e prepare# by 5yoLo Mmethy SNRM/UA !ra"e e/&ha#$e 0ith HDLC para"eter #e$ tiati # Sent frameG HE'AA'AAA:AA:8:09807H0HE CommentsG HE// >DLC frame opening flag 'AA'// frame type an# length AAA:// #estination a##ress -server. upper >DLC a##ress A&AAA0 AA:8// #estination a##ress -server. lo"er >DLC a##ress A&AA00 :0// source a##ress -client. A&A0 98// frame type S/3M -Set /ormal 3esponse Mo#e. // information fiel# "ith >DLC parameters not present, #efaults are propose# 07H0// +rame chec% sequence HE// >DLC frame closing flag 3eceive# frameG HE'A:8:0AAA:AA:8H8+1C<707A0DA<A:AA7AA1A:AA7AAHADAAAAAAA0A7ADAAAAAAA0CE1'HE CommentsG HE// >DLC frame opening flag 'A:8// frame type an# length :0// #estination a##ress -client. A&A0 AAA:// source a##ress -server. upper >DLC a##ress A&AAA0 AA:8// source a##ress -server. lo"er >DLC a##ress A&AA00 H8// frame type ;' -;nnumbere# ac%no"le#ge. +1C<// >ea#er chec% sequence 707A0D//format i#entifier / group i#entifier / group length A<A:AA7A//parameter i#entifier/length/value $ ma&imum information fiel# length transmit A1A:AA7A//parameter i#entifier/length /value $ ma&imum information fiel# length receive AHADAAAAAAA0//parameter i#entifier/length/value $ "in#o" siLe transmit A7ADAAAAAAA0//parameter i#entifier/length/value $ "in#o" siLe receive CE1' // +rame chec% sequence HE // >DLC frame closing flag AAR1/AARE e/&ha#$e Sent frameG S/3M HE'AA'AAA:AA:8:09807H0HE 3eceive# frameG ;' HE'A:8:0AAA:AA:8H8+1C<707A0DA<A:AA7AA1A:AA7AAHADAAAAAAA0A7AD AAAAAAA0CE1'HE Sent frameG ''3N HE'A:EAAA:AA:8:00AHEC4E1E1AA1A0D'0A9A1AH1A7<HDA<A7A0A04E0A ADAEA0AAAAAAA1<+0+ADAAAA8A0D++++DDC<HE CommentsG HE// opening flag

'A:E// frame type an# length AAA:AA:8:0// #estination an# source a##resses 0A// frame type , frame HEC4// >ea#er chec% sequence E1E1AA// LLC bytes 1A0D// ''3N tag an# length '0A9A1AH1A7<HDA<A7A0A0//'pplication conte&t name tag, length an# enco#e# value // !his application association is establishe# "ith lo"est level security, so authentication components are not present 4E0A// tag an# length for ''3N user fiel# ADAE// enco#ing the choice for user*information -OC!E! S!3,/5, universal. an# length A0// tag for &DLMS*,nitiate request AA// usage fiel# for #e#icate#*%ey component $ not use# AA// usage fiel# for the response allo"e# component $ not use# AA// usage fiel# of the propose#*quality*of*service component $ not use# A1// propose# #lms version number 1 <+0+// tag for conformance bloc% AD// length of the conformance bloc% AA// enco#ing the number of unuse# bits in the bit string AA8A0D//conformance bloc% ++++// client*ma&*receive*p#u*siLe DDC<// >DLC frame chec% sequence HE// closing flag 3eceive# frameG HE'A8':0AAA:AA:88A99D0E1EHAA10:9'0A9A1AH1A7<HDA<A7A0A0':A8A: A0AA'8A<'0A8A:A0AA4E0AADAEA7AAA1<+0+ADAAAA8A0D09AAAAAHAC<:HE CommentsG HE'A8':0AAA:AA:88A99D0//>DLC frame hea#er E1EHAA// LLC bytes 10:9//''3E tag an# length '0A9A1AH1A7<HDA<A7A0A0//'pplication conte&t name tag, length an# enco#e# value ':A8// tag an# length of the result component A://enco#ing the choice for result -,/!E5E3, universal. A0AA// length an# value of result -accepte#. '8A<// tag an# length for the result*source*#iagnostic component '0A8// tag an# length of the acse*service*user choice A:// enco#ing the choice for result*source*#iagnostic -,/!E5E3, universal. A0AA// length an# value of result*souce*#iagnostic 4E0A//tag an# length for ''3E user*fiel# ADAE// enco#ing the choice for user*information -OC!E! S!3,/5, universal. an# length A7// tag for &DLMS*,nitate response AA// usage fiel# of the negotiate#*quality*of*service component A1// negotiate# #lms version number 1 <+0+// tag for conformance bloc% AD// length of the conformance bloc% AA// enco#ing the number of unuse# bits in the bit string AA8A0D//negotiate# conformance bloc% 09AA// server*ma&*receive*p#u*siLe AAAH// I'' name -A&AAAH for L/ referencing. AC<:// >DLC frame chec% sequence HE// closing flag Rea'i#$ a#' setti#$ the &% &2 Sent frameG

HE'A099<H<<D178<E1E1AACAA070AAA7AAAAA0AAAA++A0AAAD+DHE CommentsG HE'A099<H<<D178<// >DLC hea#er E1E1AA// LLC bytes CAA0// 5E! request normal 70// invo%e*i# an# priority AAA7// interface class 7, cloc% AAAAA0AAAA++// logical name, O4,S co#e of the cloc% A0AA// as%ing for 0st attribute, logical name AD+DHE// >DLC frame closing 3eceive# frameG HE'A07H<9<HDE9E7E1EHAACDA070AAA9A1AAAAA0AAAA+++DD9HE CommentsG HE'A07H<9<HDE9E7E1EHAA CDA0//5E! response normal 70// invo%e*i# an# priority AA// 5et*Data*3esult choice #ata A9A1// octet string -1. AAAAA0AAAA++// logical name, O4,S co#e of the cloc% +DD9HE// >DLC closing Sent frameG HE'A099<H<H1H78HE1E1AACAA070AAA7AAAAA0AAAA++A:AA1<DHHE CommentsG HE'A099<H<H1H78HE1E1AA CAA070AAA7AAAAA0AAAA++A:AA// 5E! request normal, :n# attribute, time 1<DHHE 3eceive# frameG HE'A0EH<9<911+1HE1EHAACDA070AAA9ACAHD:ACADA8A'A1A4++AAH7AA+88AHE CommentsG HE'A0EH<9<911+1HE1EHAA// >DLC hea#er CDA0// 5E! response normal 70AA A9AC// octet string -0:. AHD:// year :AA: AC// month December AD// #ay Dth A8// #ay of the "ee%, We#nes#ay A'A1A4// time 0AGA1G0: ++// hun#re#ths not specifie# AAH7// #eviation 0:A minutes AA// status OM +88AHE Sent frameG HE'A:H9<H<9747D4E1E1AAC0A070AAA7AAAAA0AAAA++A:AAA9ACAHD:ACADA8A'A1A4++AAH 7AA1:+4HE CommentsG HE'A:H9<H<9747D4E1E1AA C0A0// SE! normal request 70 AAA7 AAAAA0AAAA++

A:AA// set the :n# attribute, time A9ACAHD:ACADA8A'A1A4++AAH7AA// )ust SE! the value rea# before 1:+4HE 3eceive# frameG HE'A0AH<9<47<0A0E1EHAAC<A070AA81C+HE CommentsG HE'A0AH<9<47<0A0E1EHAA C<A070AA// SE! response normal, success 81C+HE Sent frameG HE'A099<H<4'0784E1E1AACAA070AAA7AAAAA0AAAA++A8AA4DCEHE CommentsG HE'A099<H<4'0784E1E1AA CAA070AAA7AAAAA0AAAA++A8AA// 5E! request normal, 8# attribute, //time2Lone 4DCEHE 3eceive# frameG HE'A08H<9<D'771DE1EHAACDA070AA0AAAH7<18'HE CommentsG HE'A08H<9<D'771DE1EHAA CDA070AA// 5E! response normal 0A// integer 01 AAH7// 0:A minutes <18'HE Sent frameG HE'A0C9<H<DCH+<8E1E1AAC0A070AAA7AAAAA0AAAA++A8AA0AAAH7A00HHE CommentsG HE'A0C9<H<DCH+<8E1E1AA C0A070AAA7AAAAA0AAAA++// SE! request normal A8AA// thir# attribute 0AAAH7 //integer 01, 0:A minutes A00HHE 3eceive# frameG HE'A0AH<9<+CH0A<E1EHAAC<A070AA81C+HE CommentsG HE'A0AH<9<+CH0A<E1EHAA C<A070AA// SE! response normal, success 81C+HE Sent frameG HE'A099<H<+E878+E1E1AACAA070AAA7AAAAA0AAAA++ADAA4<78HE CommentsG HE'A099<H<+E878+E1E1AA CAA070AAA7AAAAA0AAAA++ADAA// 5E! request normal, Dth attribute, status 4<78HE 3eceive# frameG HE'A0:H<9<0E04+7E1EHAACDA070AA00AA'C<4HE CommentsG HE'A0:H<9<0E04+7E1EHAA

CDA070 AA00AA// Data, unsigne#7, OM 'C<4HE Sent frameG HE'A099<H<0AD780E1E1AACAA070AAA7AAAAA0AAAA++A<AA1D9'HE CommentsG HE'A099<H<0AD780E1E1AACAA070AAA7AAAAA0AAAA++A<AA// 5E! request normal, <th attribute, // #aylight savings begin1D9'HE 3eceive# frameG HE'A0EH<9<8A<8'HE1EHAACDA070AAA9AC++D+09+8AAHAAAAAAAAAAAA+A9A'HE CommentsG HE'A0EH<9<8A<8'HE1EHAA CDA070 AAA9AC// #ata, octet string-0:. ++++++++++++++++++7AAAAA// insignificant value A9A'HE Sent frameG HE'A099<H<8:<788E1E1AACAA070AAA7AAAAA0AAAA++A1AAA<4AHE CommentsG HE'A099<H<8:<788E1E1AACAA070AAA7AAAAA0AAAA++A1AA// 5E! request normal, 1th attribute, // #aylight2savings2en#A<4AHE 3eceive# frameG HE'A0EH<9<<:DHEHE1EHAACDA070AAA9AC++D+09+8AAHAAAAAAAAAAAA+A9A'HE CommentsG HE'A0EH<9<<:DHEHE1EHAA CDA070 AAA9AC// #ata, octet string -0:. ++++++++++++++++++7AAAAA// insignificant value A9A'HE Sent frameG HE'A099<H<<D178<E1E1AACAA070AAA7AAAAA0AAAA++AHAADD'9HE CommentsG HE'A099<H<<D178<E1E1AACAA070AAA7AAAAA0AAAA++AHAA// 5E! request normal, Hth attribute, //#aylight savings #eviationDD'9HE 3eceive# frameG HE'A0:H<9<HDDH8DE1EHAACDA070AAA+AA:D<DHE CommentG HE'A0:H<9<HDDH8DE1EHAA CDA070 AAA+AA//#ata, integer7, A :D<DHE Sent frameG HE'A099<H<H1H78HE1E1AACAA070AAA7AAAAA0AAAA++A7AA0<:'HE CommentsG HE'A099<H<H1H78HE1E1AA CAA070AAA7AAAAA0AAAA++A7AA// 5E! request normal, 7th attribute,

//#aylight2savings2enable# 0<:'HE 3eceive# frameG HE'A0:H<9<91<4+AE1EHAACDA070AAA8AA7D+DHE CommentsG HE'A0:H<9<91<4+AE1EHAA CDA070 AAA8AA// #ata, boolean, +'LSE 7D+DHE Sent frameG HE'A099<H<97A789E1E1AACAA070AAA7AAAAA0AAAA++A9AACD88HE CommentsG HE'A099<H<97A789E1E1AA CAA070AAA7AAAAA0AAAA++A9AA// 5E! request normal, 9th attribute, //cloc%2base CD88HE 3eceive# frameG HE'A0:H<9<47:H87E1EHAACDA070AA01A0:DAHHE CommentsG HE'A0:H<9<47:H87E1EHAA CDA070 AA01A0// #ata, enumerate#, 0, internal crystal :DAHHE