{"id":417925,"date":"2024-10-20T06:18:27","date_gmt":"2024-10-20T06:18:27","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-iec-ts-62056-9-12016-2\/"},"modified":"2024-10-26T11:45:55","modified_gmt":"2024-10-26T11:45:55","slug":"bsi-pd-iec-ts-62056-9-12016-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-iec-ts-62056-9-12016-2\/","title":{"rendered":"BSI PD IEC\/TS 62056-9-1:2016"},"content":{"rendered":"
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.<\/p>\n
The Web services defined in this Technical Specification concern the G2 interface according to the architecture defined in IEC 62056-1-0.<\/p>\n
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.<\/p>\n
The COSEM Access Client identifies the DLMS\/COSEM server by its system title (see IEC 62056-5-3).<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | 1 Scope 2 Normative references Figures Figure 1 \u2013 Reference model for the COSEM Access Client to DLMS\/COSEM server connection via a COSEM Access Service <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 3 Terms, definitions and abbreviations <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 4 Relation to the IEC\u00a062056 smart metering architecture 4.1 Overview 4.2 Example: Using the S-FSK profile according to IEC\u00a062056-8-3 5 Use cases 5.1 General Figure 2 \u2013 The smart metering architecture of IEC\u00a062056 <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 5.2 Use case: Device Access 5.2.1 Overview 5.2.2 On-demand Device Access <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | Figure 3 \u2013 Use case: On-demand Device Access <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 5.2.3 Scheduled Device Access <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | Figure 4 \u2013 Use case: Scheduled Device Access <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | Figure 5 \u2013 Use case: Scheduled Device Access with Events <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 5.2.4 Device Access with Data-Notification Figure 6 \u2013 Use case: Device Access with Data-Notification <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5.3 Use case: Device groups 6 Web services interface model 7 Message organisation for the WS interface 7.1 Overview 7.2 IEC\u00a062056 messages 7.2.1 Overview 7.2.2 General <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 7.2.3 Verbs Figure 7 \u2013 IEC\u00a062056 messages between CAS Client and COSEM Access Service (CAS) <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 7.2.4 Nouns 7.2.5 Payloads 7.2.6 Payload for noun Device Access Figure 8 \u2013 DeviceAccess overview structure <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Figure 9 \u2013 DeviceGroups structure <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | Figure 10 \u2013 CosemAccessDescriptor sub-structure Figure 11 \u2013 ACSEDescriptor sub-structure <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Figure 12 \u2013 XDLMSDescriptor substructure <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Figure 13 \u2013 cosemAccessResult substructure Figure 14 \u2013 errorResult substructure Figure 15 \u2013 ACSEResult substructure <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure 16 \u2013 XDLMSResult substructure <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 7.3 Common Message Envelope 7.3.1 Overview 7.3.2 General 7.3.3 Message header structure Figure 17 \u2013 Common Message Envelope <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Figure 18 \u2013 Common Message header structure <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 7.3.4 Request message structure <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Figure 19 \u2013 RequestMessage structure <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 7.3.5 Response message structure Figure 20 \u2013 XML for RequestMessage to create DeviceAccess <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Figure 21 \u2013 ResponseMessage structure <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Figure 22 \u2013 XML for ResponseMessage on create DeviceAccess <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 7.3.6 Event message structure Figure 23 \u2013 EventMessage structure <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 7.3.7 Fault message structure Figure 24 \u2013 XML for EventMessage on change of DeviceAccess <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 8 Interface specification 8.1 Overview 8.2 Interface using SOAP 8.2.1 General Figure 25 \u2013 FaultMessage structure Figure 26 \u2013 XML for FaultMessage on create of DeviceAccess <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 8.2.2 WSDL structure 8.2.3 SOAP envelope <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure 27 \u2013 SOAP message with RequestMessage <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Annex A (informative) XML schema for the COSEM XML representation A.1 COSEMpdu <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | A.2 XML schema for the payload definitions <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | A.3 XML Schema for common message envelope <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | A.4 WSDL for interface using SOAP <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" 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)<\/b><\/p>\n |