Bsi bs en 62056 7 6 2013

BS EN 62056-7-6:2013 BSI Standards Publication Electricity metering data exchange — The DLMS/ COSEM suite Part 7–6: The 3-layer, connection-oriented HDLC based communication profile BRITISH STANDARD BS EN 62056-7-6:2013 National foreword This British Standard is the UK implementation of EN 62056-7-6:2013 It is identical to IEC 62056-7-6:2013 It partially supersedes BS EN 62056-53:2007 The UK participation in its preparation was entrusted to Technical Committee PEL/13, Electricity Meters A list of organizations represented on this committee can be obtained on request to its secretary This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application ©The British Standards Institution 2013 Published by BSI Standards Limited 2013 ISBN 978 580 75130 ICS 17.220.01; 35.110; 91.140.50 Compliance with a British Standard cannot confer immunity from legal obligations This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 September 2013 Amendments/corrigenda issued since publication Date Text affected BS EN 62056-7-6:2013 EN 62056-7-6 EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM September 2013 ICS 17.220; 35.110; 91.140.50 Supersedes EN 62056-53:2007 (partially) English version Electricity metering data exchange The DLMS/COSEM suite Part 7-6: The 3-layer, connection-oriented HDLC based communication profile (IEC 62056-7-6:2013) Echange des données de comptage de l'électricité La suite DLMS/COSEM Partie 7-6: Profil de communication couches, orienté connexion et basé sur HDLC (CEI 62056-7-6:2013) Datenkommunikation der elektrischen Energiemessung DLMS/COSEM Teil 7-6: HDLC basiertes 3-Schichten Kommunikations-Protokoll (IEC 62056-7-6:2013) This European Standard was approved by CENELEC on 2013-06-20 CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CENELEC member This European Standard exists in three official versions (English, French, German) A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung CEN-CENELEC Management Centre: Avenue Marnix 17, B - 1000 Brussels © 2013 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members Ref No EN 62056-7-6:2013 E BS EN 62056-7-6:2013 EN 62056-7-6:2013 -2- Foreword The text of document 13/1527/FDIS, future edition of IEC 62056-7-6, prepared by IEC/TC 13 "Electrical energy measurement, tariff- and load control" was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as EN 62056-7-6:2013 The following dates are fixed: • latest date by which the document has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2014-03-20 • latest date by which the national standards conflicting with the document have to be withdrawn (dow) 2016-06-20 EN 62056-7-6:2013 supersedes partially EN 62056-53:2007 It is based on EN 62056-53:2007, Electricity metering – Data exchange for meter reading, tariff and load control – Part 53: COSEM application layer, Annex B.2 The 3-layer, connection-oriented, HDLC based communication profile and introduces the following significant technical changes: NOTE EN 62056-53:2007 contains the specification of the DMS/COSEM communication profiles whereas the new edition, EN 62056-5-3:2013, which replaces it, does not • The title of the standard has been aligned with the title of other parts of the revised EN 62056 series; • A Figure showing the protocol stack has been added to Clause Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent rights Endorsement notice The text of the International Standard IEC 62056-7-6:2013 was approved by CENELEC as a European Standard without any modification -3- BS EN 62056-7-6:2013 EN 62056-7-6:2013 Annex ZA (normative) Normative references to international publications with their corresponding European publications The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application For dated references, only the edition cited applies For undated references, the latest edition of the referenced document (including any amendments) applies NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies Publication Year Title EN/HD Year IEC 62056-5-3 2013 Electricity metering data exchange - The DLMS/COSEM suite Part 5-3: DLMS/COSEM application layer EN 62056-5-3 2013 IEC 62056-21 2002 Electricity metering - Data exchange for meter EN 62056-21 reading, tariff and load control Part 21: Direct local data exchange 2002 IEC 62056-42 2002 Electricity metering - Data exchange for meter EN 62056-42 reading, tariff and load control Part 42: Physical layer services and procedures for connection-oriented asynchronous data exchange 2002 IEC 62056-46 + A1 2002 2006 Electricity metering - Data exchange for meter EN 62056-46 reading, tariff and load control + A1 Part 46: Data link layer using HDLC protocol 2002 2007 –2– BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 CONTENTS Scope Normative references Terms, definitions and abbreviations Targeted communication environments Structure of the profile 6 Identification and addressing scheme 7 Supporting layer services and service mapping 8 Communication profile specific service parameters of the DLMS/COSEM AL services 9 Specific considerations / constraints 9.1 Confirmed and unconfirmed AAs and data transfer service invocations, frame types used 9.2 Correspondence between AAs and data link layer connections, releasing AAs 10 9.3 Service parameters of the COSEM-OPEN / -RELEASE / -ABORT services 10 9.4 EventNotification service and protocol 11 9.5 Transporting long messages 13 9.6 Supporting multi-drop configurations 13 Bibliography 15 Index 16 Figure – The DLMS/COSEM 3-layer, connection oriented, HDLC based communication profile Figure – Identification/addressing scheme in the 3-layer, CO, HDLC-based communication profile Figure – Summary of data link layer services Figure – Example: EventNotificaton triggered by the client 12 Figure – Multi-drop configuration and its model 13 Figure – Master/ Slave operation on the multi-drop bus 13 Table – Application associations and data exchange in the 3-layer, CO, HDLC-based profile 10 BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 –5– ELECTRICITY METERING DATA EXCHANGE – THE DLMS/COSEM SUITE – Part 7-6: The 3-layer, connection-oriented HDLC based communication profile Scope This part of IEC 62056 specifies the DLMS/COSEM 3-layer, connection-oriented HDLC based communication profile Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application For dated references, only the edition cited applies For undated references, the latest edition of the referenced document (including any amendments) applies IEC 62056-21:2002, Electricity metering – Data exchange for meter reading, tariff and load control – Part 21: Direct local data exchange IEC 62056-42:2002, Electricity metering – Data exchange for meter reading, tariff and load control – Part 42: Physical layer services and procedures for connection-oriented asynchronous data exchange IEC 62056-46:2002, Electricity metering – Data exchange for meter reading, tariff and load control – Part 46: Data link layer using HDLC protocol Amendment 1:2006 IEC 62056-5-3:—, Electricity metering data exchange – The DLMS/COSEM suite – Part 5-3: DLMS/COSEM application layer NOTE See also the Bibliography Terms, definitions and abbreviations AA Application Association AARQ A-Associate Request – an APDU of the ACSE ACSE Association Control Service Element AL Application Layer APDU Application Layer Protocol Data Unit ASO Application Service Object Client A station, asking for services In the case of the 3-layer, CO HDLC based profile it is the master station cnf confirm service primitive CO Connection-oriented COSEM Companion Specification for Energy Metering DLMS Device Language Message Specification DLMS UA DLMS User Association –6– BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 GSM Global System for Mobile Communications HDLC High-level Data Link Control HHU Hand Held Unit I Information frame (a HDLC frame type) ind indication service primitive LLC Logical Link Control (Sublayer) MAC Medium Access Control (sublayer) MAC Message Authentication Code (cryptography) master Central station – station which takes the initiative and controls the data flow NRM Normal Response Mode OSI Open System Interconnection PDU Protocol Data Unit P/F Poll/Final PhL Physical Layer PSTN Public Switched Telephone Network req request service primitive res response service primitive RNR Receive Not Ready (a HDLC frame type) RR Receive Ready (a HDLC frame type) SAP Service Access Point SNRM Set Normal Response Mode (a HDLC frame type) Server A station, delivering services The tariff device (meter) is normally the server, delivering the requested values or executing the requested tasks Slave Station responding to requests of a master station The tariff device (meter) is normally a slave station UA Unnumbered Acknowledge (a HDLC frame type) UI Unnumbered Information (a HDLC frame type) Targeted communication environments The 3-layer, CO, HDLC-based profile is suitable for local data exchange with metering equipment via direct connection, or remote data exchange via the PSTN or GSM networks with appropriate modems Structure of the profile This profile is based on a three-layer (collapsed) OSI protocol architecture: • the DLMS/COSEM AL, specified in IEC 62056-5-3; • the data link layer based on the HDLC standard, specified in IEC 62056-46; • the physical layer; specified in IEC 62056-42 This three-layer architecture is shown in Figure The use of the PhL for the purposes of direct local data exchange using an optical port or a current loop physical interface is specified in IEC 62056-21:2002, Annex E BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 –7– DL-DATA services DL-DISCONNECT services DLMS/COSEM Application layer ACSE and xDLMS ASE Data security ASE IEC 62056-5-3 DL-CONNECT Physical connection manager xDLMS services COSEM-OPEN COSEM-RELEASE COSEM-ABORT services COSEM Application Process IEC 62056-6-1, IEC 62056-6-2 PH-ABORT indication PH-CONNECT PH-ABORT PH-DATA services PH-DATA services Data link layer using HDLC protocol IEC 62056-46 Physical layer IEC 62056-42 IEC 1143/13 Figure – The DLMS/COSEM 3-layer, connection oriented, HDLC based communication profile Identification and addressing scheme The HDLC-based data link layer provides services to the DLMS/COSEM AL at Data Link SAPs, also called as the Data Link- or HDLC addresses On the client side, only the client AP needs to be identified The addressing of the physical device hosting the client APs is done by the PhL (for example by using phone numbers) On the server side, several physical devices may share a common physical line (multidrop configuration) In the case of direct connection this may be a current loop as specified in IEC 62056-21 In the case of remote connection several physical devices may share a single telephone line Therefore both the physical devices and the logical devices hosted by the physical devices need to be identified This is done using the HDLC addressing mechanism as described in 6.4.2 of IEC 62056-46:2002, Amendment 1:2006 • physical devices are identified by their lower HDLC address; • logical devices within a physical device are identified by their upper HDLC address; • a COSEM AA is identified by a doublet, containing the identifiers of the two APs participating in the AA –8– BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 For example, an AA between Client_01 (HDLC address = 16) and Server in Host Device 02 (HDLC address = 2392) is identified by the doublet {16, 2392} Here, “23” is the upper HDLC address and “92” is the lower HDLC address All values are hexadecimal This scheme ensures that a particular COSEM AP (client or server) may support more than one AA simultaneously without ambiguity See Figure IEC 1144/13 Figure – Identification/addressing scheme in the 3-layer, CO, HDLC-based communication profile Supporting layer services and service mapping In this profile, the supporting layer of the DLMS/COSEM AL is the HDLC based data link layer It provides services for: • data link layer connection management; • connection-oriented data transfer; • connection-less data transfer Figure summarizes the data link layer services provided for and used by the DLMS/COSEM AL The DL-DATA.confirm primitive on the server side is available to support transporting long messages from the server to the client in a transparent manner to the AL See 9.5 In some cases, the correspondence between an AL (ASO) service invocation and the supporting data link layer service invocation is straightforward For example, invocation of a GET.request primitive directly implies the invocation of a DL-DATA.request primitive In some other cases, a direct service mapping cannot be established For example, the invocation of a COSEM-OPEN.request primitive with Service_Class == Confirmed involves a series of actions, starting with the establishment of the lower layer connection with the help of the DL-CONNECT service, and then sending out the AARQ APDU via this newly established connection using a DL-DATA.request service Examples for service mapping are given in IEC 62056-5-3:—, Clause BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 –9– DL-DATA.cnf DL-DATA.ind DL-DATA.req DL-DISCONNECT.res DL-CONNECT.res DL-CONNECT.ind DL-DATA.ind DL-DATA.req DL-DISCONNECT.ind DL-DISCONNECT.cnf DL-DISCONNECT.req DL-CONNECT.cnf DL-CONNECT.req DL-DISCONNECT.ind Server side application layer Client side application layer Server side data link layer Client side data link layer IEC 1145/13 Figure – Summary of data link layer services Communication profile specific service parameters of the DLMS/COSEM AL services Only the COSEM-OPEN service has communication profile specific parameters, the Protocol_Connection_Parameters parameter This contains the following data: • Protocol (Profile) Identifier 3-Layer, connection-oriented, HDLC-based; • Server_Lower_MAC_Address (COSEM Physical Device Address); • Server_Upper_MAC_Address (COSEM Logical Device Address); • Client_MAC_Address; • Server_LLC_Address; • Client_LLC_Address Any server (destination) address parameter may contain special addresses (All-station, Nostation, etc.) For more information, see IEC 62056-46 9.1 Specific considerations / constraints Confirmed and unconfirmed AAs and data transfer service invocations, frame types used Table summarizes the rules for establishing confirmed and unconfirmed AAs, the type of data transfer services available in such AAs and the HDLC frame types that carry the APDUs This table clearly shows one of the specific features of this profile: the Service_Class parameter of service invocations is linked to the frame type of the supporting layer: • If the COSEM-OPEN service – see 6.2 of IEC 62056-5-3:—, – is invoked with Service_Class == Confirmed, then the AARQ APDU is carried by an “I” frame On the other hand, if it is invoked with Service_Class == Unconfirmed, it is carried by a “UI” frame Therefore, in this profile, the response-allowed parameter of the xDLMS InitiateRequest APDU has no significance See also 7.2.4.1 of IEC 62056-5-3:—; • Similarly, if a data transfer service request primitive is invoked with Service_Class == Confirmed, then the corresponding APDU is transported by an “I” frame If it is invoked with Service_class == Unconfirmed, then the corresponding APDU is carried by a “UI” frame Consequently, Service_Class bit of the Invoke-Id-And-Priority field – see IEC 62056-5-3:—, Clause – is not relevant in this profile BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 – 10 – Table – Application associations and data exchange in the 3-layer, CO, HDLC-based profile Application association establishment Protocol connection parameters COSEM-OPEN service class Use Data exchange Type of established AA 1/ Connect data link layer Confirmed Id: HDLC LLC and MAC addresses Unconfirmed 9.2 2/ Exchange AARQ/AARE APDUs transported in “I” frames Send AARQ in a “UI” frame Service class Use Confirmed “I” frame Unconfirmed “UI” frame Confirmed (not allowed) - Unconfirmed “UI” frame Confirmed Unconfirmed Correspondence between AAs and data link layer connections, releasing AAs In this profile, a confirmed AA is bound to a supporting data link layer connection, in a one-toone basis Consequently: • establishing a confirmed AA implies the establishment of a connection between the client and server data link layers; • a confirmed AA in this profile can be non-ambiguously released by disconnecting the corresponding data link layer connection On the other hand, in this profile, establishing an unconfirmed AA does not need any lower layer connection: consequently, once established, unconfirmed AAs with servers not supporting the ACSE A-RELEASE service (see 6.3 and 7.2.5 of IEC 62056-5-3:—) cannot be released 9.3 Service parameters of the COSEM-OPEN / -RELEASE / -ABORT services Thanks to the possibility to transparently transport higher layer related information within the SNRM and DISC HDLC frames, this profile allows the use of the optional “User_Information” parameter of the COSEM-OPEN – see 6.2 of IEC 62056-5-3:— – and COSEM-RELEASE – see 6.3 of IEC 62056-5-3:— – services: • the User_Information parameter of a COSEM-OPEN.request primitive, if present, is inserted into the "User data subfield" of the SNRM frame, sent during the data link connection establishment; • if the SNRM frame received by the server contains a "User data subfield", its contents is passed to the server AP via the User_Information parameter of the COSEMOPEN.indication primitive; • the User_Information parameter of a COSEM-RELEASE.request primitive, if present, is inserted into the "User data subfield" of the DISC frame, sent during disconnecting the data link connection; • if the DISC frame received by the server contains a "User data subfield", its contents is passed to the server AP via the User_Information parameter of the COSEMRELEASE.indication primitive; • the User_Information parameter of the COSEM-RELEASE.response primitive, if present, is inserted into the "User data subfield" of the UA or HDLC frame, sent in response to the DISC frame; BS EN 62056-7-6:2013 62056-7-6 â IEC:2013 ã 11 if the UA or DM frame received by the client contains "User data subfield", its contents is passed to the client AP via the User_Information parameter of the COSEMRELEASE.confirm primitive In addition, for the COSEM-ABORT.indication service, the following rule applies: • 9.4 the Diagnostics parameter of the COSEM-ABORT.indication primitive – see 6.4 of IEC 62056-5-3:— – may contain an unnumbered send status parameter This parameter indicates whether, at the moment of the physical abort indication, the data link layer has or does not have a pending Unnumbered Information message (UI) The type and the value of this parameter is a local issue, thus it is not within the scope of this companion specification See also 5.2.2.3 and 6.2.2.3 of IEC 62056-46:2002, Amendment 1:2006 EventNotification service and protocol This subclause describes the communication profile specific elements of the protocol of the EventNotification service, see 6.9 of IEC 62056-5-3:— In this profile, an event is reported always by the server management logical device (mandatory, reserved upper HDLC address 0x01) to the client management AP (mandatory, reserved HDLC address 0x01) The EventNotificationRequest APDU is sent using connectionless data services, using an UI frame, at the first opportunity, i.e when the server side data link layer receives the right to talk The APDU shall fit into a single HDLC frame To be able to send out the APDU, a physical connection between the physical device hosting the server and a client device must exist, and the server side data link layer needs to receive the token from the client side data link layer If there is a data link connection between the client and the server when the event occurs, the server side data link layer may send out the PDU – carrying the EventNotificationRequest APDU – following the reception of an I, a UI or an RR frame from the client See 6.4.4.7 of IEC 62056-46:2002 Figure shows the procedure in the case, when there is no physical connection when the event occurs (but this connection to a client device can be established) NOTE Physical connection cannot be established when the server has only a local interface (for example an optical port as defined in IEC 62056-21) and the HHU, running the client application is not connected, or the server has a PSTN interface, but the telephone line is not available Handling such cases is implementation specific BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 – 12 – Client physical connectionand protocol identification manager Client management application process Client application layer control function Client supporting protocol layer (XX) Client physical layer Server physical layer Server supporting protocol layer (XX) Server application layer control function Server management application process Server physical connectionand protocol identification manager No physical connection is established between the server and client devices Event (to be notified) is detected PH-CONNECT.req Physical connection establishment PH-CONNECT.ind PH-CONNECT.cnf DLDATA.req PDU is pending EventNotification.req PHCONNECT_OK Protocol-Identification.req Protocol-Identification.res Profile-ID/ Parameters Trigger_Event Notification_ Sending.req EventNotification.ind DL-DATA.req DL-DATA.ind Sending an empty UI frame Sending the pending PDU IEC 1146/13 Figure – Example: EventNotificaton triggered by the client The first step is to establish this physical connection If successful, this is reported at both sides to the physical connection manager process At the server side, this indicates to the AP that the EventNotification.request service can be invoked now When it is done, the server AL builds an EventNotificationRequest APDU and invokes the connectionless DL-DATA.request primitive of the data link layer with the data parameter carrying the APDU However, the data link layer may not be able to send this APDU, thus it is stored in the data link layer, waiting to be sent (pending) When the client detects a successful physical connection establishment – and as there is no other reason to receive an incoming call – it supposes that this call is originated by a server intending to send the EventNotificationRequest APDU At this moment, the client may not know the protocol stack used by the calling server Therefore, it has to identify it first using the optional protocol identification service described in IEC 62056-42 This is shown as a “Protocol-Identification.request” – “ProtocolIdentification.response” message exchange in Figure Following this, the client is able to instantiate the right protocol stack The client AP then invokes the TriggerEventNotificationSending.request primitive (see 6.10 of IEC 62056-5-3:—) Upon invocation of this primitive, the AL invokes the connectionless DLDATA.request primitive of the data link layer with empty data, and the data link layer sends out an empty UI frame with the P/F bit set to TRUE, giving the permission to the server side data link layer to send the pending PDU When the client AL receives an EventNotificationRequest APDU, it generates the EventNotification.indication primitive The client is notified now about the event, the sequence is completed _ This physical connection establishment is done outside of the protocol stack BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 9.5 – 13 – Transporting long messages In this profile, the data link layer provides a method for transporting long messages in a transparent manner for the AL This is described in 6.4.4.5 of IEC 62056-46:2002 See also 4.2.3.12 of IEC 62056-5-3:— As transparent long data transfer is specified only for the direction from the server to the client, the server side supporting protocol layer provides special services for this purpose to the server AL As these services are specific to the supporting protocol layer, no specific AL services and protocols are specified for this purpose When the supporting protocol layer supports transparent long data transfer, the server side AL implementation may be able to manage these services 9.6 Supporting multi-drop configurations A multi-drop arrangement is often used allowing a data collection system to exchange data with multiple physical metering equipment, using a shared communication resource like a telephone modem Various physical arrangements are available, like a star, daisy chain or a bus topology These arrangements can be modelled with a logical bus, to which the metering equipment and the shared resource are connected, see Figure Daisy-chained CEMs CEM CEM n CEM Modem PSTN = CEM Logical bus CEM n PSTN CEM CEM = COSEM Energy Meter IEC 1147/13 Figure – Multi-drop configuration and its model As collision on the bus must be avoided, but a protocol controlling access to the shared resource is not available, access to the bus must be controlled by external rules In most cases, a Master-Slave arrangement is used, where the metering equipment are the Slaves (see Figure 6) Slave devices have no right to send messages without first receiving an explicit permission from the Master In DLMS/COSEM, data exchange takes place based on the Client/Server model Physical devices are modelled as a set of logical devices, acting as servers, providing responses to requests Obviously, the Master Station of a multi-drop configuration is located at the other end of the communication channel and it acts as the client, sending requests and expecting responses CEM n Slave n … CEM CEM Slave Slave Master Station Logical bus IEC 1148/13 Figure – Master/ Slave operation on the multi-drop bus The client may send requests at the same time to multiple servers, if no response is expected (multi-cast or broadcast) If the client expects a response, the request shall be sent to a single server, giving also the right to talk to the server It has to wait then for the response before it – 14 – BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 may send a request to another server and with this, giving the right to talk Arbitration of access to the common bus is thus controlled in a time-multiplexing fashion Messages from the client to the servers shall contain addressing information In this profile, it is ensured by using HDLC addresses If a multi-drop arrangement is used, the HDLC address is split to two parts: the lower HDLC address to address physical devices and the upper HDLC address to address logical devices within the physical device Both the lower and the upper address may contain a broadcast address For details, see 6.4.2 of IEC 62056-46:2002, Amendment 1:2006 To be able to report events, a server may initiate a connection to the client, using the nonclient/server type EventNotification / InformationReport services As events in several or all meters connected to a multidrop may occur simultaneously – for example in the case of a power failure – they may initiate a call to the client simultaneously For such cases, two problems have to be handled: • collision on the logical bus: For the reasons explained above, several physical devices may try to access the shared resource (for example sending AT commands to the modem) simultaneously Handling such situations is left to the manufacturers; • identification of the originator of the event report: this is possible by using the CALLING Physical Device Address, as described in 6.4.4.8 of IEC 62056-46:2002, Amendment 1:2006 BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 – 15 – Bibliography DLMS UA 1000-1:2010, COSEM Identification System and Interface Classes, the “Blue Book” DLMS UA 1000-2:2009, DLMS/COSEM Architecture and Protocols, the "Green Book" DLMS UA 1001-1:2010, DLMS/COSEM Conformance Test and certification process, the "Yellow Book" ISO/IEC 8802-2:1998, Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 2: Logical link control BS EN 62056-7-6:2013 62056-7-6 © IEC:2013 – 16 – Index CALLING Physical Device Address, 15 Client_LLC_Address, 10 Client_MAC_Address, 10 Collision, 15 COSEM logical device address, 10 COSEM physical device address, 10 DLMS/COSEM AL, EventNotification service, 3-layer, CO, HDLC based profile, 12 Identification and addressing scheme, Identification service, 13 Master/ Slave operation on the multi-drop bus, 14 Multi-drop configuration, 3-layer, CO, HDLC based profile, 14 Physical layer, Profile specific service parameters, 10 Protocol_Connection_Parameters, 10 Server_LLC_Address, 10 Service mapping, Supporting layer services, Transporting long messages, 3-layer, CO, HDLC based profile, 14 _ This page deliberately left blank NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW British Standards Institution (BSI) BSI is the national body responsible for preparing British Standards and other standards-related publications, information and services BSI is incorporated by Royal Charter British Standards and other standardization products are published by BSI Standards Limited About us Revisions We bring together business, industry, government, consumers, innovators and others to shape their combined experience and expertise into standards -based solutions Our British Standards and other publications are updated by amendment or revision The knowledge embodied in our standards has been carefully assembled in a dependable format and refined through our open consultation process Organizations of all sizes and across all sectors choose standards to help them achieve their goals Information on standards We can provide you with the knowledge that your organization needs to succeed Find out more about British Standards by visiting our website at bsigroup.com/standards or contacting our Customer Services team or Knowledge Centre Buying standards You can buy and download PDF versions of BSI publications, including British and adopted European and international standards, through our website at bsigroup.com/shop, where hard copies can also be purchased If you need international and foreign standards from other Standards Development Organizations, hard copies can be ordered from our Customer Services team Subscriptions Our range of subscription services are designed to make using standards easier for you For further information on our subscription products go to bsigroup.com/subscriptions With British Standards Online (BSOL) you’ll have instant access to over 55,000 British and adopted European and international standards from your desktop It’s available 24/7 and is refreshed daily so you’ll always be up to date You can keep in touch with standards developments and receive substantial discounts on the purchase price of standards, both in single copy and subscription format, by becoming a BSI Subscribing Member PLUS is an updating service exclusive to BSI Subscribing Members You will automatically receive the latest hard copy of your standards when they’re revised or replaced To find out more about becoming a BSI Subscribing Member and the benefits of membership, please visit bsigroup.com/shop With a Multi-User Network Licence (MUNL) you are able to host standards publications on your intranet Licences can cover as few or as many users as you wish With updates supplied as soon as they’re available, you can be sure your documentation is current For further information, email bsmusales@bsigroup.com BSI Group Headquarters 389 Chiswick High Road London W4 4AL UK We continually improve the quality of our products and services to benefit your business If you find an inaccuracy or ambiguity within a British Standard or other BSI publication please inform the Knowledge Centre Copyright All the data, software and documentation set out in all British Standards and other BSI publications are the property of and copyrighted by BSI, or some person or entity that owns copyright in the information used (such as the international standardization bodies) and has formally licensed such information to BSI for commercial publication and use Except as permitted under the Copyright, Designs and Patents Act 1988 no extract may be reproduced, stored in a retrieval system or transmitted in any form or by any means – electronic, photocopying, recording or otherwise – without prior written permission from BSI Details and advice can be obtained from the Copyright & Licensing Department Useful Contacts: Customer Services Tel: +44 845 086 9001 Email (orders): orders@bsigroup.com Email (enquiries): cservices@bsigroup.com Subscriptions Tel: +44 845 086 9001 Email: subscriptions@bsigroup.com Knowledge Centre Tel: +44 20 8996 7004 Email: knowledgecentre@bsigroup.com Copyright & Licensing Tel: +44 20 8996 7070 Email: copyright@bsigroup.com