{"id":447310,"date":"2024-10-20T08:51:19","date_gmt":"2024-10-20T08:51:19","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-62056-5-32023-tc\/"},"modified":"2024-10-26T16:30:08","modified_gmt":"2024-10-26T16:30:08","slug":"bs-en-iec-62056-5-32023-tc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-62056-5-32023-tc\/","title":{"rendered":"BS EN IEC 62056-5-3:2023 – TC"},"content":{"rendered":"

This part of IEC 62056 specifies the DLMS\u00ae\/COSEM application layer in terms of structure, services and protocols for DLMS\u00ae\/COSEM clients and servers, and defines rules to specify the DLMS\u00ae\/COSEM communication profiles. It defines services for establishing and releasing application associations, and data communication services for accessing the methods and attributes of COSEM interface objects, defined in IEC 62056-6-2:2021 using either logical name (LN) or short name (SN) referencing. Annex A (normative) defines how to use the COSEM application layer in various communication profiles. It specifies how various communication profiles can be constructed for exchanging data with metering equipment using the COSEM interface model, and what are the necessary elements to specify in each communication profile. The actual, media-specific communication profiles are specified in separate parts of the IEC 62056 series. Annex B (normative) specifies the SMS short wrapper. Annex C (normative) specifies the gateway protocol. Annex D, Annex E and Annex F (informative) include encoding examples for APDUs. Annex G (normative) provides NSA Suite B elliptic curves and domain parameters. Annex H (informative) provides an example of an End entity signature certificate using P-256 signed with P-256. Annex I (normative) specifies the use of key agreement schemes in DLMS\u00ae\/COSEM. Annex J (informative) provides examples of exchanging protected xDLMS APDUs between a third party and a server. Annex K (informative) lists the main technical changes in this edition of the standard.<\/p>\n

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
523<\/td>\nundefined <\/td>\n<\/tr>\n
526<\/td>\nAnnex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n
529<\/td>\nEnglish
CONTENTS <\/td>\n<\/tr>\n
539<\/td>\nFOREWORD <\/td>\n<\/tr>\n
541<\/td>\nINTRODUCTION <\/td>\n<\/tr>\n
542<\/td>\n1 Scope
2 Normative references <\/td>\n<\/tr>\n
544<\/td>\n3 Terms, definitions, abbreviated terms and symbols
3.1 General DLMS\u00ae\/COSEM definitions <\/td>\n<\/tr>\n
549<\/td>\n3.2 Definitions related to cryptographic security <\/td>\n<\/tr>\n
559<\/td>\n3.3 Definitions and abbreviated terms related to the Galois\/Counter Mode <\/td>\n<\/tr>\n
561<\/td>\n3.4 General abbreviated terms <\/td>\n<\/tr>\n
565<\/td>\n3.5 Symbols related to the Galois\/Counter Mode
3.6 Symbols related the ECDSA algorithm <\/td>\n<\/tr>\n
566<\/td>\n3.7 Symbols related to the key agreement algorithms
4 Overview of DLMS\u00ae\/COSEM
4.1 Information exchange in DLMS\u00ae\/COSEM
4.1.1 General <\/td>\n<\/tr>\n
567<\/td>\n4.1.2 Communication model <\/td>\n<\/tr>\n
568<\/td>\n4.1.3 Naming and addressing
Figures
Figure 1 \u2013 Client\u2013server model and communication protocols <\/td>\n<\/tr>\n
569<\/td>\nFigure 2 \u2013 Naming and addressing in DLMS\u00ae\/COSEM <\/td>\n<\/tr>\n
570<\/td>\nTables
Table 1 \u2013 Client XE “Client” and server XE “Server” SAPs <\/td>\n<\/tr>\n
571<\/td>\n4.1.4 Connection oriented operation
Figure 3 \u2013 A complete communication session in the CO environment <\/td>\n<\/tr>\n
572<\/td>\n4.1.5 Application associations <\/td>\n<\/tr>\n
573<\/td>\n4.1.6 Messaging patterns XE “Messaging patterns” <\/td>\n<\/tr>\n
574<\/td>\n4.1.7 Data exchange between third parties and DLMS\u00ae\/COSEM servers
Figure 4 \u2013 DLMS\u00ae\/COSEM messaging patterns <\/td>\n<\/tr>\n
575<\/td>\n4.1.8 Communication profiles XE “Communication profile” <\/td>\n<\/tr>\n
576<\/td>\nFigure 5 \u2013 DLMS\u00ae\/COSEM generic communication profile XE “Generic communication profile” <\/td>\n<\/tr>\n
577<\/td>\n4.1.9 Model of a DLMS\u00ae\/COSEM metering system
4.1.10 Model of DLMS\u00ae\/COSEM servers XE “DLMS\/COSEM server model”
Figure 6 \u2013 Model of a DLMS\u00ae\/COSEM metering system <\/td>\n<\/tr>\n
578<\/td>\nFigure 7 \u2013 DLMS\u00ae\/COSEM server model <\/td>\n<\/tr>\n
579<\/td>\n4.1.11 Model of a DLMS\u00ae\/COSEM client XE “DLMS\/COSEM client model”
Figure 8 \u2013 Model of a DLMS\u00ae\/COSEM client using multiple protocol stacks <\/td>\n<\/tr>\n
580<\/td>\n4.1.12 Interoperability XE “Interoperability” and interconnectivity XE “Interconnectivity” in DLMS\u00ae\/COSEM
4.1.13 Ensuring interconnectivity: the protocol identification service XE “Protocol identification service”
4.1.14 System integration XE “System integration” and meter installation XE “Meter installation” <\/td>\n<\/tr>\n
581<\/td>\n4.2 DLMS\u00ae\/COSEM application layer main features
4.2.1 General
4.2.2 DLMS\u00ae\/COSEM application layer structure XE “DLMS\/COSEM AL, structure”
Figure 9 \u2013 The structure of the DLMS\u00ae\/COSEM application layers <\/td>\n<\/tr>\n
582<\/td>\n4.2.3 The Association Control Service Element XE “Association Control Service Element” , ACSE <\/td>\n<\/tr>\n
583<\/td>\n4.2.4 The xDLMS application service element XE “xDLMS ASE” <\/td>\n<\/tr>\n
588<\/td>\nFigure 10 \u2013 The concept of composable xDLMS messages <\/td>\n<\/tr>\n
590<\/td>\nTable 2 \u2013 Clarification of the meaning of PDU size for DLMS\u00ae\/COSEM <\/td>\n<\/tr>\n
591<\/td>\n4.2.5 Layer management services XE “DLMS\/COSEM AL, layer management services”
4.2.6 Summary of DLMS\u00ae\/COSEM application layer services
Figure 11 \u2013 Summary of DLMS\u00ae\/COSEM AL services <\/td>\n<\/tr>\n
592<\/td>\n4.2.7 DLMS\u00ae\/COSEM application layer protocols XE “DLMS\/COSEM AL, protocol specification”
5 Information security in DLMS\u00ae\/COSEM
5.1 Overview
5.2 The DLMS\u00ae\/COSEM security concept XE “DLMS\/COSEM security concept”
5.2.1 Overview <\/td>\n<\/tr>\n
593<\/td>\n5.2.2 Identification and authentication <\/td>\n<\/tr>\n
594<\/td>\nFigure 12 \u2013 Authentication mechanisms <\/td>\n<\/tr>\n
596<\/td>\n5.2.3 Security context XE “Security context”
5.2.4 Access rights XE “Access right”
5.2.5 Application layer message security XE “Application layer message security” <\/td>\n<\/tr>\n
597<\/td>\nFigure 13 \u2013 Client \u2013 server message security concept XE “Message security, client \u2013 server” <\/td>\n<\/tr>\n
598<\/td>\nFigure 14 \u2013 End-to-end message security XE “Message security, end-to-end” concept <\/td>\n<\/tr>\n
599<\/td>\n5.2.6 COSEM data security XE “COSEM data security”
5.3 Cryptographic algorithms XE “Cryptographic algorithm”
5.3.1 Overview
5.3.2 Hash function XE “Hash function” <\/td>\n<\/tr>\n
600<\/td>\n5.3.3 Symmetric key algorithms XE “Symmetric key algorithm”
Figure 15 \u2013 Hash function <\/td>\n<\/tr>\n
601<\/td>\nFigure 16 \u2013 Encryption and decryption <\/td>\n<\/tr>\n
602<\/td>\nFigure 17 \u2013 Message Authentication Codes (MACs) <\/td>\n<\/tr>\n
604<\/td>\nFigure 18 \u2013 GCM functions <\/td>\n<\/tr>\n
607<\/td>\n5.3.4 Public key algorithms XE “Public key algorithm” <\/td>\n<\/tr>\n
608<\/td>\nTable 3 \u2013 Elliptic curves in DLMS\u00ae\/COSEM security suites <\/td>\n<\/tr>\n
610<\/td>\nFigure 19 \u2013 Digital signatures <\/td>\n<\/tr>\n
612<\/td>\nFigure 20 \u2013 C(2e, 0s) scheme: each party contributes only an ephemeral key pair
Table 4 \u2013 Ephemeral Unified Model key agreement scheme summary <\/td>\n<\/tr>\n
613<\/td>\nFigure 21 \u2013 C(1e, 1s) schemes: party U contributes an ephemeral key pair, and party V contributes a static key pair <\/td>\n<\/tr>\n
614<\/td>\nTable 5 \u2013 One-pass Diffie-Hellman key agreement scheme summary <\/td>\n<\/tr>\n
615<\/td>\nFigure 22 \u2013 C(0e, 2s) scheme: each party contributes only a static key pair <\/td>\n<\/tr>\n
616<\/td>\nTable 6 \u2013 Static Unified Model key agreement scheme summary <\/td>\n<\/tr>\n
617<\/td>\n5.3.5 Random number generation XE “Random number generation”
Table 7 \u2013 OtherInfo subfields and substrings
Table 8 \u2013 Security algorithm ID-s XE “Security algorithm ID” <\/td>\n<\/tr>\n
618<\/td>\n5.3.6 Compression XE “Compression”
5.3.7 Security suite XE “Security suite”
Table 9 \u2013 DLMS\u00ae\/COSEM security suites <\/td>\n<\/tr>\n
619<\/td>\n5.4 Cryptographic keys \u2013 overview
5.5 Key used with symmetric key algorithms
5.5.1 Symmetric keys XE “Symmetric key” types <\/td>\n<\/tr>\n
620<\/td>\nTable 10 \u2013 Symmetric keys types <\/td>\n<\/tr>\n
621<\/td>\n5.5.2 Key information XE “Key information” with general-ciphering APDU and data protection
5.5.3 Key identification XE “Key identification”
Table 11 \u2013 Key information with general-ciphering APDU and data protection <\/td>\n<\/tr>\n
622<\/td>\n5.5.4 Key wrapping XE “Key wrapping”
5.5.5 Key agreement XE “Key agreement” <\/td>\n<\/tr>\n
623<\/td>\n5.5.6 Symmetric key cryptoperiods XE “Cryptoperiod”
5.6 Keys used with public key algorithms XE “Public key algorithm”
5.6.1 Overview
5.6.2 Key pair generation XE “Key pair generation”
Table 12 \u2013 Asymmetric keys types and their use <\/td>\n<\/tr>\n
624<\/td>\n5.6.3 Public key certificates and infrastructure <\/td>\n<\/tr>\n
626<\/td>\nFigure 23 \u2013 Architecture of a Public Key Infrastructure (example) <\/td>\n<\/tr>\n
627<\/td>\n5.6.4 Certificate and certificate extension profile XE “Certificate and certificate extension profile”
Table 13 \u2013 X.509 v3 Certificate structure <\/td>\n<\/tr>\n
628<\/td>\nTable 14 \u2013 X.509 v3 tbsCertificate fields <\/td>\n<\/tr>\n
629<\/td>\nTable 15 \u2013 Naming scheme for the Root-CA instance (informative)
Table 16 \u2013 Naming scheme for the Sub-CA instance (informative) <\/td>\n<\/tr>\n
630<\/td>\nTable 17 \u2013 Naming scheme for the end entity instance <\/td>\n<\/tr>\n
632<\/td>\nTable 18 \u2013 X.509 v3 Certificate extensions <\/td>\n<\/tr>\n
633<\/td>\nTable 19 \u2013 Key Usage extensions
Table 20 \u2013 Subject Alternative Name values <\/td>\n<\/tr>\n
634<\/td>\nTable 21 \u2013 Issuer Alternative Name values
Table 22 \u2013 Basic constraints extension values <\/td>\n<\/tr>\n
635<\/td>\n5.6.5 Suite B end entity certificate XE “End entity certificate” types to be supported by DLMS\u00ae\/COSEM servers
5.6.6 Management of certificates
Table 23 \u2013 Certificates handled by DLMS\u00ae\/COSEM end entities <\/td>\n<\/tr>\n
636<\/td>\nFigure 24 \u2013 MSC for provisioning the server with CA certificates <\/td>\n<\/tr>\n
637<\/td>\nFigure 25 \u2013 MSC for security personalisation of the server <\/td>\n<\/tr>\n
638<\/td>\nFigure 26 \u2013 Provisioning the server with the certificate of the client <\/td>\n<\/tr>\n
639<\/td>\nFigure 27 \u2013 Provisioning the client \/ third party with a certificate of the server
Figure 28 \u2013 Remove certificate from the server <\/td>\n<\/tr>\n
640<\/td>\n5.7 Applying cryptographic protection
5.7.1 Overview
5.7.2 Protecting xDLMS APDUs
Table 24 \u2013 Security policy values (“Security setup” version 1) <\/td>\n<\/tr>\n
641<\/td>\nTable 25 \u2013 Access rights values (“Association LN” ver 3 “Association SN” ver 4) <\/td>\n<\/tr>\n
642<\/td>\nTable 26 \u2013 Ciphered xDLMS APDUs <\/td>\n<\/tr>\n
643<\/td>\nFigure 29 \u2013 Cryptographic protection of information using AES-GCM <\/td>\n<\/tr>\n
644<\/td>\nTable 27 \u2013 Security control byte
Table 28 \u2013 Plaintext and Additional Authenticated Data <\/td>\n<\/tr>\n
645<\/td>\nFigure 30 \u2013 Structure of service-specific global XE “Service-specific global ciphering” \/ dedicated ciphering XE “Service-specific dedicated ciphering” xDLMS APDUs <\/td>\n<\/tr>\n
646<\/td>\nFigure 31 \u2013 Structure of general-glo-ciphering and general-ded-ciphering xDLMS APDUs <\/td>\n<\/tr>\n
647<\/td>\nFigure 32 \u2013 Structure of general-ciphering xDLMS APDUs <\/td>\n<\/tr>\n
648<\/td>\nTable 29 \u2013 Use of the fields of the ciphering xDLMS APDUs <\/td>\n<\/tr>\n
649<\/td>\nTable 30 \u2013 Example: glo-get-request xDLMS APDU <\/td>\n<\/tr>\n
651<\/td>\nTable 31 \u2013 ACCESS service with general-ciphering, One-Pass Diffie-Hellman C(1e, 1s, ECC CDH) key agreement scheme <\/td>\n<\/tr>\n
653<\/td>\n5.7.3 Multi-layer protection XE “Multi-layer protection” by multiple parties
Figure 33 \u2013 Structure of general-signing APDUs <\/td>\n<\/tr>\n
654<\/td>\n5.7.4 HLS authentication XE “HLS authentication” mechanisms <\/td>\n<\/tr>\n
655<\/td>\nTable 32 \u2013 DLMS\u00ae\/COSEM HLS authentication mechanisms <\/td>\n<\/tr>\n
656<\/td>\nTable 33 \u2013 HLS example using authentication-mechanism 5 with GMAC <\/td>\n<\/tr>\n
657<\/td>\n5.7.5 Protecting COSEM data XE “COSEM data protection”
Table 34 \u2013 HLS example using authentication-mechanism 7 with ECDSA <\/td>\n<\/tr>\n
658<\/td>\n6 DLMS\u00ae\/COSEM application layer service specification XE ” COSEM AL, service specification”
6.1 Service primitives and parameters
Figure 34 \u2013 Service primitives <\/td>\n<\/tr>\n
659<\/td>\nFigure 35 \u2013 Time sequence diagrams <\/td>\n<\/tr>\n
660<\/td>\n6.2 The COSEM-OPEN service XE “COSEM-OPEN service”
Table 35 \u2013 Codes for AL service parameters <\/td>\n<\/tr>\n
661<\/td>\nTable 36 \u2013 Service parameters of the COSEM-OPEN service primitives <\/td>\n<\/tr>\n
665<\/td>\n6.3 The COSEM-RELEASE service XE “COSEM-RELEASE service”
Table 37 \u2013 Service parameters of the COSEM-RELEASE service primitives <\/td>\n<\/tr>\n
668<\/td>\n6.4 COSEM-ABORT service XE “COSEM-ABORT service”
6.5 Protection and general block transfer XE “General block transfer” parameters
Table 38 \u2013 Service parameters of the COSEM-ABORT service primitives <\/td>\n<\/tr>\n
669<\/td>\nFigure 36 \u2013 Additional service parameters to control cryptographic protection and GBT <\/td>\n<\/tr>\n
670<\/td>\nTable 39 \u2013 Additional service parameters <\/td>\n<\/tr>\n
671<\/td>\nTable 40 \u2013 Security parameters <\/td>\n<\/tr>\n
672<\/td>\nTable 41 \u2013 APDUs used with security protection types <\/td>\n<\/tr>\n
673<\/td>\n6.6 The GET service XE “GET service” <\/td>\n<\/tr>\n
674<\/td>\nTable 42 \u2013 Service parameters of the GET service <\/td>\n<\/tr>\n
675<\/td>\nTable 43 \u2013 GET service request and response types <\/td>\n<\/tr>\n
676<\/td>\n6.7 The SET service XE “SET service” <\/td>\n<\/tr>\n
677<\/td>\nTable 44 \u2013 Service parameters of the SET service <\/td>\n<\/tr>\n
678<\/td>\nTable 45 \u2013 SET service request and response types <\/td>\n<\/tr>\n
680<\/td>\n6.8 The ACTION service XE “ACTION service”
Table 46 \u2013 Service parameters of the ACTION service <\/td>\n<\/tr>\n
681<\/td>\nTable 47 \u2013 ACTION service request and response types <\/td>\n<\/tr>\n
683<\/td>\n6.9 The ACCESS service
6.9.1 Overview \u2013 Main features <\/td>\n<\/tr>\n
685<\/td>\n6.9.2 Service specification <\/td>\n<\/tr>\n
686<\/td>\nTable 48 \u2013 Service parameters of the ACCESS service <\/td>\n<\/tr>\n
689<\/td>\n6.10 The DataNotification service XE “DataNotification service” <\/td>\n<\/tr>\n
690<\/td>\nTable 49 \u2013 Service parameters of the DataNotification service primitives <\/td>\n<\/tr>\n
691<\/td>\n6.11 The EventNotification service XE “EventNotification service”
Table 50 \u2013 Service parameters of the EventNotification service primitives <\/td>\n<\/tr>\n
692<\/td>\n6.12 The TriggerEventNotificationSending service XE “TriggerEventNotificationSending service”
Table 51 \u2013 Service parameters of the TriggerEventNotificationSending.request service primitive <\/td>\n<\/tr>\n
693<\/td>\n6.13 Variable access specification XE “Variable Access Specification”
6.14 The Read service XE “Read service”
Table 52 \u2013 Variable Access Specification <\/td>\n<\/tr>\n
694<\/td>\nTable 53 \u2013 Service parameters of the Read service <\/td>\n<\/tr>\n
695<\/td>\nTable 54 \u2013 Use of the Variable_Access_Specification variants and the Read.response choices <\/td>\n<\/tr>\n
697<\/td>\n6.15 The Write service XE “Write service” <\/td>\n<\/tr>\n
698<\/td>\nTable 55 \u2013 Service parameters of the Write service <\/td>\n<\/tr>\n
699<\/td>\nTable 56 \u2013 Use of the Variable_Access_Specification variants and the Write.response choices <\/td>\n<\/tr>\n
700<\/td>\n6.16 The UnconfirmedWrite service XE “UnconfirmedWrite service” <\/td>\n<\/tr>\n
701<\/td>\nTable 57 \u2013 Service parameters of the UnconfirmedWrite service
Table 58 \u2013 Use of the Variable_Access_Specification variants <\/td>\n<\/tr>\n
702<\/td>\n6.17 The InformationReport service XE “InformationReport service”
Table 59 \u2013 Service parameters of the InformationReport service <\/td>\n<\/tr>\n
703<\/td>\n6.18 Client side layer management services: the SetMapperTable.request XE “AL, management services” XE “Client side layer management services” XE “SetMapperTables.request”
6.19 Summary of services and LN\/SN data transfer service mapping XE “LN\/SN data transfer service mapping”
Table 60 \u2013 Service parameters of the SetMapperTable.request service primitives
Table 61 \u2013 Summary of ACSE services <\/td>\n<\/tr>\n
704<\/td>\n7 DLMS\u00ae\/COSEM application layer protocol specification XE “COSEM application layer, protocol specification”
7.1 The control function XE “Control function”
7.1.1 State definitions of the client side control function
Table 62 \u2013 Summary of xDLMS services XE “xDLMS services, LN referencing” <\/td>\n<\/tr>\n
705<\/td>\nFigure 37 \u2013 Partial state machine for the client side control function <\/td>\n<\/tr>\n
706<\/td>\n7.1.2 State definitions of the server side control function <\/td>\n<\/tr>\n
707<\/td>\nFigure 38 \u2013 Partial state machine for the server side control function <\/td>\n<\/tr>\n
708<\/td>\n7.2 The ACSE services and APDUs XE “ACSE services and APDUs”
7.2.1 ACSE functional units XE “ACSE functional units” , services and service parameters <\/td>\n<\/tr>\n
709<\/td>\nTable 63 \u2013 Functional Unit APDUs and their fields <\/td>\n<\/tr>\n
711<\/td>\n7.2.2 Registered COSEM names XE “Registered COSEM names” <\/td>\n<\/tr>\n
713<\/td>\nTable 64 \u2013 COSEM application context names XE “COSEM application context name”
Table 65 \u2013 COSEM authentication mechanism names XE “COSEM authentication mechanism name” <\/td>\n<\/tr>\n
714<\/td>\n7.2.3 APDU encoding rules
7.2.4 Protocol for application association establishment XE “Application association, establishment”
Table 66 \u2013 Cryptographic algorithm ID-s <\/td>\n<\/tr>\n
716<\/td>\nFigure 39 \u2013 MSC for successful AA establishment preceded by a successful lower layer connection establishment <\/td>\n<\/tr>\n
720<\/td>\n7.2.5 Protocol for application association release XE “Application association, release” <\/td>\n<\/tr>\n
721<\/td>\nFigure 40 \u2013 Graceful AA release using the A-RELEASE service <\/td>\n<\/tr>\n
722<\/td>\nFigure 41 \u2013 Graceful AA release by disconnecting the supporting layer <\/td>\n<\/tr>\n
723<\/td>\n7.3 Protocol for the data transfer services XE “Data transfer services, protocol”
7.3.1 Negotiation of services and options \u2013 the conformance block XE “Conformance block”
Figure 42 \u2013 Aborting an AA following a PH-ABORT.indication <\/td>\n<\/tr>\n
724<\/td>\n7.3.2 Confirmed and unconfirmed service invocations
Table 67 \u2013 xDLMS Conformance block <\/td>\n<\/tr>\n
726<\/td>\n7.3.3 Protocol for the GET service XE “GET service”
Figure 43 \u2013 MSC of the GET service
Table 68 \u2013 GET service types and APDUs <\/td>\n<\/tr>\n
727<\/td>\nFigure 44 \u2013 MSC of the GET service with block transfer <\/td>\n<\/tr>\n
729<\/td>\n7.3.4 Protocol for the SET service XE “SET service”
Figure 45 \u2013 MSC of the GET service with block transfer, long GET aborted
Table 69 \u2013 SET service types and APDUs <\/td>\n<\/tr>\n
730<\/td>\nFigure 46 \u2013 MSC of the SET service
Figure 47 \u2013 MSC of the SET service with block transfer <\/td>\n<\/tr>\n
732<\/td>\n7.3.5 Protocol for the ACTION service XE “ACTION service”
Figure 48 \u2013 MSC of the ACTION service
Table 70 \u2013 ACTION service types and APDUs <\/td>\n<\/tr>\n
734<\/td>\n7.3.6 Protocol for the ACCESS service XE “ACCESS service”
Figure 49 \u2013 MSC of the ACTION service with block transfer <\/td>\n<\/tr>\n
735<\/td>\n7.3.7 Protocol of the DataNotification service
Figure 50 \u2013 Access Service with long response
Figure 51 \u2013 Access Service with long request and response <\/td>\n<\/tr>\n
736<\/td>\nFigure 52 \u2013 MSC for the DataNotification service, case a) <\/td>\n<\/tr>\n
737<\/td>\nFigure 53 \u2013 MSC for the DataNotification service, case b) <\/td>\n<\/tr>\n
738<\/td>\n7.3.8 Protocol for the EventNotification service
Figure 54 \u2013 MSC for the DataNotification service, case c) <\/td>\n<\/tr>\n
739<\/td>\n7.3.9 Protocol for the Read service XE “Read service”
Table 71 \u2013 Mapping between the GET and the Read services <\/td>\n<\/tr>\n
740<\/td>\nTable 72 \u2013 Mapping between the ACTION and the Read services <\/td>\n<\/tr>\n
741<\/td>\nFigure 55 \u2013 MSC of the Read service used for reading an attribute
Figure 56 \u2013 MSC of the Read service used for invoking a method <\/td>\n<\/tr>\n
742<\/td>\n7.3.10 Protocol for the Write service XE “Write service”
Figure 57 \u2013 MSC of the Read Service used for reading an attribute, with block transfer <\/td>\n<\/tr>\n
743<\/td>\nTable 73 \u2013 Mapping between the SET and the Write services <\/td>\n<\/tr>\n
744<\/td>\nTable 74 \u2013 Mapping between the ACTION and the Write service <\/td>\n<\/tr>\n
745<\/td>\nFigure 58 \u2013 MSC of the Write service used for writing an attribute
Figure 59 \u2013 MSC of the Write service used for invoking a method <\/td>\n<\/tr>\n
746<\/td>\n7.3.11 Protocol for the UnconfirmedWrite service XE “UnconfirmedWrite service”
Figure 60 \u2013 MSC of the Write Service used for writing an attribute, with block transfer <\/td>\n<\/tr>\n
747<\/td>\n7.3.12 Protocol for the InformationReport service XE “InformationReport service”
Figure 61 \u2013 MSC of the Unconfirmed Write service used for writing an attribute
Table 75 \u2013 Mapping between the SET and the UnconfirmedWrite services
Table 76 \u2013 Mapping between the ACTION and the UnconfirmedWrite services <\/td>\n<\/tr>\n
748<\/td>\n7.3.13 Protocol of general block transfer mechanism
Table 77 \u2013 Mapping between the EventNotification and InformationReport services <\/td>\n<\/tr>\n
750<\/td>\nFigure 62 \u2013 Partial service invocations and GBT APDUs <\/td>\n<\/tr>\n
753<\/td>\nFigure 63 \u2013 The GBT procedure <\/td>\n<\/tr>\n
755<\/td>\nTable 78 \u2013 GBT procedure state variables <\/td>\n<\/tr>\n
757<\/td>\nFigure 64 \u2013 Send GBT APDU stream sub-procedure <\/td>\n<\/tr>\n
759<\/td>\nFigure 65 \u2013 Process GBT APDU sub-procedure <\/td>\n<\/tr>\n
761<\/td>\nFigure 66 \u2013 Check RQ and fill gaps sub-procedure <\/td>\n<\/tr>\n
762<\/td>\nFigure 67 \u2013 GET service with GBT, switching to streaming <\/td>\n<\/tr>\n
763<\/td>\nFigure 68 \u2013 GET service with partial invocations, GBT and streaming,recovery of 4th block sent in the 2nd stream <\/td>\n<\/tr>\n
765<\/td>\nFigure 69 \u2013 GET service with partial invocations, GBT and streaming,recovery of 4th and 5th block <\/td>\n<\/tr>\n
766<\/td>\nFigure 70 \u2013 GET service with partial invocations,GBT and streaming, recovery of last block <\/td>\n<\/tr>\n
767<\/td>\nFigure 71 \u2013 SET service with GBT, with server not supporting streaming,recovery of 3rd block <\/td>\n<\/tr>\n
768<\/td>\nFigure 72 \u2013 ACTION-WITH-LIST service with bi-directional GBT and block recovery <\/td>\n<\/tr>\n
770<\/td>\n7.3.14 Protocol of exception mechanism
Figure 73 \u2013 DataNotification service with GBT with partial invocation <\/td>\n<\/tr>\n
771<\/td>\n8 Abstract syntax XE “Abstract syntax, COSEM APDUs” of ACSE and COSEM APDUs
Table 79 \u2013 xDLMS exception mechanism <\/td>\n<\/tr>\n
790<\/td>\n9 COSEM APDU XML schema XE “XML schema”
9.1 General
9.2 XML Schema <\/td>\n<\/tr>\n
812<\/td>\nAnnex A (normative)Using the DLMS\u00ae\/COSEM application layer in various communications profiles
A.1 General
A.2 Targeted communication environments XE “Communication environment”
A.3 The structure of the profile XE “Communication profile structure”
A.4 Identification and addressing schemes XE “Identification and addressing scheme” <\/td>\n<\/tr>\n
813<\/td>\nA.5 Supporting layer services and service mapping XE “Supporting layer services and service mapping”
A.6 Communication profile specific parameters of the COSEM AL services XE “Communication profile specific parameters”
A.7 Specific considerations \/ constraints using certain services within a given profile
A.8 The 3-layer, connection-oriented, HDLC based communication profile
A.9 The TCP-UDP\/IP based communication profiles (COSEM_on_IP)
A.10 The wired and wireless M-Bus communication profiles
A.11 The S-FSK PLC profile <\/td>\n<\/tr>\n
814<\/td>\nAnnex B (normative)SMS short wrapper
Figure B.1 \u2013 Short wrapper
Table B.1 \u2013 Reserved Application Processes <\/td>\n<\/tr>\n
815<\/td>\nAnnex C (normative)Gateway protocol
C.1 General
Figure C.1 \u2013 General architecture with gateway <\/td>\n<\/tr>\n
816<\/td>\nC.2 The gateway protocol XE “Gateway protocol”
Figure C.2 \u2013 The fields used for pre-fixing the COSEM APDUs <\/td>\n<\/tr>\n
817<\/td>\nC.3 HES in the WAN\/NN acting as Initiator (Pull operation XE “Pull operation” )
Figure C.3 \u2013 Pull message sequence chart <\/td>\n<\/tr>\n
818<\/td>\nC.4 End devices in the LAN acting as Initiators (Push operation XE “Push operation” )
C.4.1 General
C.4.2 End device with WAN\/NN knowledge
C.4.3 End devices without WAN\/NN knowledge
C.5 Security
Figure C.4 \u2013 Push message sequence chart <\/td>\n<\/tr>\n
819<\/td>\nAnnex D (informative)AARQ and AARE encoding examples
D.1 General
D.2 Encoding of the xDLMS InitiateRequest \/ InitiateResponse APDU <\/td>\n<\/tr>\n
820<\/td>\nTable D.1 \u2013 Conformance block <\/td>\n<\/tr>\n
821<\/td>\nTable D.2 \u2013 A-XDR encoding of the xDLMS InitiateRequest APDU <\/td>\n<\/tr>\n
822<\/td>\nD.3 Specification of the AARQ and AARE APDUs
Table D.3 \u2013 A-XDR encoding of the xDLMS InitiateResponse APDU <\/td>\n<\/tr>\n
823<\/td>\nD.4 Data for the examples <\/td>\n<\/tr>\n
824<\/td>\nD.5 Encoding of the AARQ APDU <\/td>\n<\/tr>\n
825<\/td>\nTable D.4 \u2013 BER encoding of the AARQ APDU <\/td>\n<\/tr>\n
827<\/td>\nD.6 Encoding of the AARE APDU
Table D.5 \u2013 Complete AARQ APDU <\/td>\n<\/tr>\n
828<\/td>\nTable D.6 \u2013 BER encoding of the AARE APDU <\/td>\n<\/tr>\n
832<\/td>\nTable D.7 \u2013 The complete AARE APDU <\/td>\n<\/tr>\n
833<\/td>\nAnnex E (informative)Encoding examples: AARQ and AARE APDUs using a ciphered application context
E.1 A-XDR encoding of the xDLMS InitiateRequest APDU, carrying a dedicated key <\/td>\n<\/tr>\n
834<\/td>\nE.2 Authenticated encryption of the xDLMS InitiateRequest APDU
Table E.1 \u2013 A-XDR encoding of the xDLMS InitiateRequest APDU <\/td>\n<\/tr>\n
835<\/td>\nE.3 The AARQ APDU
Table E.2 \u2013 Authenticated encryption of the xDLMS InitiateRequest APDU <\/td>\n<\/tr>\n
836<\/td>\nTable E.3 \u2013 BER encoding of the AARQ APDU <\/td>\n<\/tr>\n
837<\/td>\nE.4 A-XDR encoding of the xDLMS InitiateResponse APDU <\/td>\n<\/tr>\n
838<\/td>\nE.5 Authenticated encryption of the xDLMS InitiateResponse APDU
Table E.4 \u2013 A-XDR encoding of the xDLMS InitiateResponse APDU <\/td>\n<\/tr>\n
839<\/td>\nE.6 The AARE APDU
Table E.5 \u2013 Authenticated encryption of the xDLMS InitiateResponse APDU <\/td>\n<\/tr>\n
840<\/td>\nTable E.6 \u2013 BER encoding of the AARE APDU <\/td>\n<\/tr>\n
841<\/td>\nE.7 The RLRQ APDU (carrying a ciphered xDLMS InitiateRequest APDU)
Table E.7 \u2013 BER encoding of the RLRQ APDU <\/td>\n<\/tr>\n
842<\/td>\nE.8 The RLRE APDU (carrying a ciphered xDLMS InitiateResponse APDU)
Table E.8 \u2013 BER encoding of the RLRE APDU <\/td>\n<\/tr>\n
843<\/td>\nAnnex F (informative)Data transfer service examples
F.1 GET \/ Read, SET \/ Write examples
Table F.1 \u2013 The objects used in the examples <\/td>\n<\/tr>\n
844<\/td>\nTable F.2 \u2013 Example: Reading the value of a single attribute without block transfer <\/td>\n<\/tr>\n
845<\/td>\nTable F.3 \u2013 Example: Reading the value of a list of attributes without block transfer <\/td>\n<\/tr>\n
847<\/td>\nTable F.4 \u2013 Example: Reading the value of a single attribute with block transfer <\/td>\n<\/tr>\n
849<\/td>\nTable F.5 \u2013 Example: Reading the value of a list of attributes with block transfer <\/td>\n<\/tr>\n
852<\/td>\nTable F.6 \u2013 Example: Writing the value of a single attribute without block transfer <\/td>\n<\/tr>\n
853<\/td>\nTable F.7 \u2013 Example: Writing the value of a list of attributes without block transfer <\/td>\n<\/tr>\n
855<\/td>\nTable F.8 \u2013 Example: Writing the value of a single attribute with block transfer <\/td>\n<\/tr>\n
857<\/td>\nTable F.9 \u2013 Example: Writing the value of a list of attributes with block transfer <\/td>\n<\/tr>\n
860<\/td>\nF.2 ACCESS service XE “ACCESS service” example
Table F.10 \u2013 Example: ACCESS service without block transfer <\/td>\n<\/tr>\n
861<\/td>\nF.3 Compact array encoding example
F.3.1 General <\/td>\n<\/tr>\n
862<\/td>\nF.3.2 The specification of compact-array <\/td>\n<\/tr>\n
863<\/td>\nF.3.3 Example 1: Compact array encoding an array of five long-unsigned values <\/td>\n<\/tr>\n
864<\/td>\nF.3.4 Example 2: Compact-array encoding of five octet-string values <\/td>\n<\/tr>\n
865<\/td>\nF.3.5 Example 3: Encoding of the buffer of a Profile generic object <\/td>\n<\/tr>\n
866<\/td>\nF.4 Profile generic IC buffer attribute encoding examples
F.4.1 General <\/td>\n<\/tr>\n
867<\/td>\nF.4.2 Get-response with Profile generic normal encoding example
Table F.11 \u2013 Profile generic buffer \u2013 get-response with normal encoding <\/td>\n<\/tr>\n
869<\/td>\nF.4.3 Get-response with Profile generic null-data compressed encoding example
Table F.12 \u2013 Profile generic buffer \u2013 get-response with null-data compression <\/td>\n<\/tr>\n
872<\/td>\nF.4.4 Get-response with Profile generic compact-array encoding example
Table F.13 \u2013 Profile generic buffer \u2013 get-response with compact-array encoding <\/td>\n<\/tr>\n
874<\/td>\nF.4.5 Get-response with Profile generic null-data and delta-value encoding example <\/td>\n<\/tr>\n
875<\/td>\nTable F.14 \u2013 Profile generic buffer \u2013 Get-response with null-dataand delta-value encoding <\/td>\n<\/tr>\n
877<\/td>\nF.4.6 Comparison of various encoding methods for Get-response APDU
F.4.7 Combination of the various encoding methods and V.44 compression
Table F.15 \u2013 Comparison of various encoding methods for get-response APDU <\/td>\n<\/tr>\n
878<\/td>\nTable F.16 \u2013 Combination of the various encoding methodsand V.44 compression for get-response APDU <\/td>\n<\/tr>\n
879<\/td>\nAnnex G (normative)NSA Suite B XE “NSA Suite B” elliptic curves and domain parameters
Table G.1 \u2013 ECC_P256_Domain_Parameters XE “ECC_P256_Domain_Parameters” <\/td>\n<\/tr>\n
880<\/td>\nTable G.2 \u2013 ECC_P384_Domain_Parameters XE “ECC_P384_Domain_Parameters” <\/td>\n<\/tr>\n
881<\/td>\nAnnex H (informative)Example of an End entity signature certificateusing P-256 signed with P-256
H.1 Fields of public key certificates
Table H.1 \u2013 Fields of public key Certificates using P-256 signed with P-256 <\/td>\n<\/tr>\n
882<\/td>\nH.2 Example of a Root-CA Certificate using P-256 signed with P-256 <\/td>\n<\/tr>\n
883<\/td>\nH.3 Example of an end entity digital signature Certificate using P-256 signed with P-256 <\/td>\n<\/tr>\n
884<\/td>\nAnnex I (normative)Use of key agreement schemes in DLMS\u00ae\/COSEM
I.1 Ephemeral Unified Model XE “Ephemeral Unified Model” C(2e, 0s, ECC CDH) scheme
Figure I.1 \u2013 MSC for key agreement using the Ephemeral Unified Model C(2e, 0s, ECC CDH) scheme <\/td>\n<\/tr>\n
885<\/td>\nTable I.1 \u2013 Test vector for key agreement using theEphemeral Unified Model C(2e, 0s, ECC CDH) scheme <\/td>\n<\/tr>\n
887<\/td>\nI.2 One-Pass Diffie-Hellman XE “One-Pass Diffie-Hellman” C(1e, 1s, ECC CDH) scheme
Figure I.2 \u2013 Ciphered xDLMS APDU protected by an ephemeral key established using the One-pass Diffie-Hellman (1e, 1s, ECC CDH) scheme <\/td>\n<\/tr>\n
888<\/td>\nTable I.2 \u2013 Test vector for key agreement using theOne-pass Diffie-Hellman (1e, 1s, ECC CDH) scheme <\/td>\n<\/tr>\n
890<\/td>\nI.3 Static Unified Model XE “Static Unified Model” C(0e, 2s, ECC CDH) scheme <\/td>\n<\/tr>\n
891<\/td>\nFigure I.3 \u2013 Ciphered xDLMS APDU protected by an ephemeral key established using the Static Unified Model C(0e, 2s, ECC CDH) scheme <\/td>\n<\/tr>\n
892<\/td>\nTable I.3 \u2013 Test vector for key agreement using theStatic-Unified Model (0e, 2s, ECC CDH) scheme <\/td>\n<\/tr>\n
894<\/td>\nAnnex J (informative)Exchanging protected xDLMS APDUs between TP and server
J.1 General
J.2 Example 1: Protection is the same in the two directions <\/td>\n<\/tr>\n
895<\/td>\nJ.3 Example 2: Protection is different in the two directions
Figure J.1 \u2013 Exchanging protected xDLMS APDUs between TP and server: example 1 <\/td>\n<\/tr>\n
896<\/td>\nFigure J.2 \u2013 Exchanging protected xDLMS APDUs between TP and server: example 2 <\/td>\n<\/tr>\n
897<\/td>\nAnnex K (informative)Significant technical changes with respect to IEC 62056\u20115\u20113:2017 <\/td>\n<\/tr>\n
900<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Tracked Changes. Electricity metering data exchange. The DLMS\u00ae\/COSEM suite – DLMS\u00ae\/COSEM application layer<\/b><\/p>\n\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2023<\/td>\n904<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":447320,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[498,2641],"product_tag":[],"class_list":{"0":"post-447310","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-29-080-30","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/447310","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/447320"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=447310"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=447310"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=447310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}