DIN EN 62056-53:2007-08

1 Scope
2 Normative references
3 Terms, definitions and abbreviations
4 The COSEM communications framework
  4.1 Client/server type operation, communication profiles
  4.2 Connection (association) oriented operation
5 Overview: the COSEM application layer
  5.1 Specification method
  5.2 Application layer structure
  5.3 Service specification
      5.3.1 Services provided for application association
            establishment and release
      5.3.2 Data communication services
  5.4 Layer management services
  5.5 Protocol specification
6 COSEM application layer - Service specification
  6.1 Summary of services
  6.2 Application association establishment and release
  6.3 Special application associations
      6.3.1 Mandatory application associations
      6.3.2 Pre-established application associations
      6.3.3 Non-confirmed application associations
  6.4 Data communication
  6.5 Client COSEM application layer services
      6.5.1 Application association establishment
      6.5.2 Application association release
      6.5.3 Client/server type data communication services
      6.5.4 Client side services for event notification
      6.5.5 Client side layer management services
  6.6 Server COSEM application layer services
      6.6.1 Application association establishment
      6.6.2 Application association release
      6.6.3 Client/server type data communication services
7 COSEM application layer protocol specification
  7.1 State definitions for the client side Control function
  7.2 State definitions for the server side Control function
  7.3 Protocol for application association establishment/release
      7.3.1 Establishment of an application association
      7.3.2 Establishment of special application associations
      7.3.3 The AARQ and AARE APDUs
      7.3.4 Managing the parameters for application association
            establishment
      7.3.5 Repeated COSEM-OPEN.request service invocations
      7.3.6 Releasing an application association
      7.3.7 Registered COSEM names
  7.4 Protocol for data communications
      7.4.1 Protocol for the xDLMS services using LN referencing
      7.4.2 Protocol for the xDLMS services using SN referencing
8 Specification of COSEM data types and APDU-s
  8.1 The COSEM APDUs
  8.2 The AARQ and AARE APDUs
  8.3 Useful types
  8.4 The xDLMS-Initiate.request/response/ConfirmedServiceError PDUs
  8.5 The conformance block
  8.6 Definition of APDUs for data communication
      8.6.1 COSEM APDUs using logical name referencing
      8.6.2 DLMS APDUs using short name referencing
Annex A (normative) The 3-layer, connection-oriented, HDLC based
        profile
      A.1 Introduction
      A.2 The HDLC-based data link layer - Overview
          A.2.1 Services of the HDLC based data link layer
Annex B (normative) The xDLMS application service element
      B.1 Introduction
      B.2 DLMS compliance
      B.3 Extensions to DLMS for COSEM
          8.3.1 Additional services
          B.3.2 Additional data types
          8.3.3 The conformance block
          8.3.4 DLMS version number
          B.3.5 Other necessary modifications
Annex C (informative) AARQ and AARE encoding examples
      C.l Encoding example of the xDLMS-Initiate.request PDU
      C.2 Encoding example of an AARQ not using the ACSE security
           mechanism
      C.3 Encoding example of an AARQ using low-level
           authentication
      C.4 Encoding example of an AARQ using high-level
           authentication
      C.5 Encoding example for the AARE APDU, case of success
      C.6 Encoding example of the xDLMS-Initiate.response PDU
      C.7 Encoding of the AARE not using security or using
           low-level security
      C.8 Encoding of the AARE using high-level security
      C.9 Encoding example for the AARE-pdu, case of failure
      C.10 Encoding example for the AARE APDU, case of failure
Annex D (informative) Data model and protocol
Annex ZA (normative) Normative references to international
         publications with their corresponding European
         publications

Describes the COSEM application layer in terms of structure, services and protocols, for COSEM clients and servers.