🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BSI PD IEC/TS 62056-9-1:2016

BSI PD IEC/TS 62056-9-1:2016

$198.66

Electricity metering data exchange. The DLMS/COSEM suite – Communication profile using web-services to access a DLMS/COSEM server via a COSEM Access Service (CAS)

Published By Publication Date Number of Pages
BSI 2016 64
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This part of IEC 62056, which is a Technical Specification, defines how DLMS/COSEM servers can be accessed from a COSEM Access Client via an intermediate COSEM Access Service (CAS) providing Web services. The DLMS/COSEM server contains an application server supporting the data model of IEC 62056-6-1 / IEC 62056-6-2 and the application layer of IEC 62056-5-3. The underlying communication layers between the CAS and the DLMS/COSEM server are not covered by this specification. However, it is assumed that a profile standard exists describing how the underlying communication technology is used in conjunction with IEC 62056-6-1/ IEC 62056-6-2 and IEC 62056-5-3.

The Web services defined in this Technical Specification concern the G2 interface according to the architecture defined in IEC 62056-1-0.

The contents of this document define the Web services between the COSEM Access Client and the COSEM Access Service (CAS) as shown in Figure 1.

The COSEM Access Client identifies the DLMS/COSEM server by its system title (see IEC 62056-5-3).

PDF Catalog

PDF Pages PDF Title
4 CONTENTS
6 FOREWORD
8 1 Scope
2 Normative references
Figures
Figure 1 – Reference model for the COSEM Access Client to DLMS/COSEM server connection via a COSEM Access Service
9 3 Terms, definitions and abbreviations
10 4 Relation to the IEC 62056 smart metering architecture
4.1 Overview
4.2 Example: Using the S-FSK profile according to IEC 62056-8-3
5 Use cases
5.1 General
Figure 2 – The smart metering architecture of IEC 62056
11 5.2 Use case: Device Access
5.2.1 Overview
5.2.2 On-demand Device Access
12 Figure 3 – Use case: On-demand Device Access
13 5.2.3 Scheduled Device Access
14 Figure 4 – Use case: Scheduled Device Access
15 Figure 5 – Use case: Scheduled Device Access with Events
16 5.2.4 Device Access with Data-Notification
Figure 6 – Use case: Device Access with Data-Notification
17 5.3 Use case: Device groups
6 Web services interface model
7 Message organisation for the WS interface
7.1 Overview
7.2 IEC 62056 messages
7.2.1 Overview
7.2.2 General
18 7.2.3 Verbs
Figure 7 – IEC 62056 messages between CAS Client and COSEM Access Service (CAS)
19 7.2.4 Nouns
7.2.5 Payloads
7.2.6 Payload for noun Device Access
Figure 8 – DeviceAccess overview structure
20 Figure 9 – DeviceGroups structure
21 Figure 10 – CosemAccessDescriptor sub-structure
Figure 11 – ACSEDescriptor sub-structure
22 Figure 12 – XDLMSDescriptor substructure
23 Figure 13 – cosemAccessResult substructure
Figure 14 – errorResult substructure
Figure 15 – ACSEResult substructure
24 Figure 16 – XDLMSResult substructure
25 7.3 Common Message Envelope
7.3.1 Overview
7.3.2 General
7.3.3 Message header structure
Figure 17 – Common Message Envelope
26 Figure 18 – Common Message header structure
27 7.3.4 Request message structure
28 Figure 19 – RequestMessage structure
29 7.3.5 Response message structure
Figure 20 – XML for RequestMessage to create DeviceAccess
30 Figure 21 – ResponseMessage structure
31 Figure 22 – XML for ResponseMessage on create DeviceAccess
32 7.3.6 Event message structure
Figure 23 – EventMessage structure
33 7.3.7 Fault message structure
Figure 24 – XML for EventMessage on change of DeviceAccess
34 8 Interface specification
8.1 Overview
8.2 Interface using SOAP
8.2.1 General
Figure 25 – FaultMessage structure
Figure 26 – XML for FaultMessage on create of DeviceAccess
35 8.2.2 WSDL structure
8.2.3 SOAP envelope
36 Figure 27 – SOAP message with RequestMessage
37 Annex A (informative) XML schema for the COSEM XML representation
A.1 COSEMpdu
58 A.2 XML schema for the payload definitions
59 A.3 XML Schema for common message envelope
60 A.4 WSDL for interface using SOAP
61 Bibliography

Related products

BSI PD IEC/TS 62056-9-1:2016
$198.66