{"id":420870,"date":"2024-10-20T06:33:18","date_gmt":"2024-10-20T06:33:18","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-iec-tr-61968-9002015-2\/"},"modified":"2024-10-26T12:15:58","modified_gmt":"2024-10-26T12:15:58","slug":"bsi-pd-iec-tr-61968-9002015-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-iec-tr-61968-9002015-2\/","title":{"rendered":"BSI PD IEC\/TR 61968-900:2015"},"content":{"rendered":"
This part of IEC 61968-9, which is a technical report, is a reference document and, as such, is not always suitable for someone new to the world of meter reading and control. In particular, it assumes significant domain knowledge.<\/p>\n
This technical report is a companion document to the official standard. It is written from the viewpoint of a software developer or systems integrator who is tasked with implementing IEC 61968-9. It is not intended as a complete description of this standard. For full details, please refer to IEC 61968-9.<\/p>\n
To get the most from this technical report, the user should have a good understanding of XML technologies, in particular of XML schema definitions and of web services.<\/p>\n
This technical report contains informative recommendations which may be used to guide implementations of IEC 61968-9 and IEC 61968-100. It does not attempt to be exhaustive. In particular, it focuses on the most common IEC 61968-9 interfaces and assumes the user is using web services or JMS as the underlying transport mechanism. If the user is using other systems or the transport services are something other than web services or JMS, the recommendations in this technical report may be less relevant but perhaps still useful.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
15<\/td>\n | 1 Scope 2 Normative references 3 IEC 61968-100 basics 3.1 General <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
16<\/td>\n | 3.2 IEC 61968-100 message exchange patterns 3.3 IEC 61968-100 message types 3.3.1 General <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
17<\/td>\n | 3.3.2 Request messages <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
18<\/td>\n | Figures Figure 1 \u2013 Example message for a simple meter read request <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
19<\/td>\n | 3.3.3 Response messages Figure 2 \u2013 Example response message to a simple meter read request <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
20<\/td>\n | 3.3.4 Unsolicited event messages Figure 3 \u2013 Example unsolicited event message <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21<\/td>\n | 3.4 IEC 61968-100 message content 3.4.1 General Figure 4 \u2013 RequestMessage definition according to Message.xsd Figure 5 \u2013 ResponseMessage definition according to Message.xsd <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
22<\/td>\n | 3.4.2 Verb and noun elements in the message header 3.4.3 Get requests Figure 6 \u2013 EventMessage definition according to Message.xsd <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
23<\/td>\n | 3.4.4 Other requests 3.4.5 The CorrelationID element 3.4.6 Other elements in the message header <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
24<\/td>\n | 3.4.7 The Message.xsd XSD schema definition file <\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
25<\/td>\n | 4 Request and response messages in detail 4.1 General 4.2 Several potential response messages for each request message Figure 7 \u2013 Subelements allowed inside a 26<\/td>\n | 4.3 Response messages contain a status indication | 4.4 Response messages containing data and error notifications 4.5 Specific error indications in the response messages Figure 8 \u2013 Example of a success indication in a Reply element <\/td>\n<\/tr>\n 27<\/td>\n | Figure 9 \u2013 Example of error indications in a Reply element (incomplete) <\/td>\n<\/tr>\n | 28<\/td>\n | Figure 10 \u2013 Subelements allowed inside a element <\/td>\n<\/tr>\n | 29<\/td>\n | 4.6 Implicit indication of success | Figure 11 \u2013 Subelements allowed inside a element <\/td>\n<\/tr>\n 30<\/td>\n | 4.7 General error indications in the response messages | 4.7.1 General 4.7.2 Setting the element Figure 12 \u2013 Example of overall indication of success in a Reply element Figure 13 \u2013 Example of error indications in a Reply element (corrected) <\/td>\n<\/tr>\n 31<\/td>\n | 4.7.3 Multiple response messages | 4.8 Multiple , and elements <\/td>\n<\/tr>\n 32<\/td>\n | 4.9 Implementation-specific messages | 5 The naming of objects 5.1 General 5.2 Naming meters <\/td>\n<\/tr>\n 33<\/td>\n | Figure 14 \u2013 EndDevice definition <\/td>\n<\/tr>\n | 34<\/td>\n | 5.3 EndDeviceGroups, UsagePoints and UsagePointGroups | Figure 15 \u2013 Example of a Meter Read Request with NameType and NameTypeAuthority <\/td>\n<\/tr>\n 35<\/td>\n | 5.4 Naming of other objects | 5.5 Provisioning and interrogating a system 6 Meter read requests and responses 6.1 General <\/td>\n<\/tr>\n 36<\/td>\n | 6.2 Message exchange patterns | 6.2.1 General 6.2.2 Request message with a single response message <\/td>\n<\/tr>\n 37<\/td>\n | 6.2.3 Request message with multiple response messages | Figure 16 \u2013 Message exchange pattern for a meter read requestwith a single response message <\/td>\n<\/tr>\n 39<\/td>\n | 6.3 GetMeterReadings request | 6.3.1 General Figure 17 \u2013 Message exchange pattern for a meter read requestwith multiple response messages <\/td>\n<\/tr>\n 41<\/td>\n | 6.3.2 Naming of meters | 6.3.3 The ReadingType element Figure 18 \u2013 GetMeterReadings definition according to GetMeterReadings.xsd <\/td>\n<\/tr>\n 43<\/td>\n | 6.3.4 The ReadingQuality element | Figure 19 \u2013 definition <\/td>\n<\/tr>\n 44<\/td>\n | 6.3.5 The TimeSchedule element | Figure 20 \u2013 definition <\/td>\n<\/tr>\n 45<\/td>\n | 6.3.6 Specifying multiple constraints in a request message | Figure 21 \u2013 definition <\/td>\n<\/tr>\n 47<\/td>\n | Figure 22 \u2013 Example of a request message for two ReadingType codes over two meters <\/td>\n<\/tr>\n | 48<\/td>\n | 6.3.7 Coincident meter reads | Figure 23 \u2013 Example of a request message for two meter\/ReadingType combinations <\/td>\n<\/tr>\n 49<\/td>\n | 6.4 On-demand meter reads | 6.4.1 General <\/td>\n<\/tr>\n 50<\/td>\n | Figure 24 \u2013 Message exchange pattern for an on-demand meter read <\/td>\n<\/tr>\n | 51<\/td>\n | 6.4.2 Pinging a meter | 6.5 MeterReadings response 6.5.1 General Figure 25 \u2013 Example of an on-demand meter read request message <\/td>\n<\/tr>\n 52<\/td>\n | Figure 26 \u2013 Example of a response to a meter read request <\/td>\n<\/tr>\n | 53<\/td>\n | 6.5.2 The element | Figure 27 \u2013 MeterReadings definition according to MeterReadings.xsd <\/td>\n<\/tr>\n 54<\/td>\n | 6.5.3 The element | Figure 28 \u2013 definition Figure 29 \u2013 definition <\/td>\n<\/tr>\n 55<\/td>\n | 6.5.4 The element | 6.5.5 The element 6.5.6 The elements 6.5.7 The EndDeviceType, ReadingQualityType and ReadingType elements Figure 30 \u2013 definition <\/td>\n<\/tr>\n 56<\/td>\n | Figure 31 \u2013 definition <\/td>\n<\/tr>\n | 58<\/td>\n | 6.6 Unsolicited meter reads | 6.6.1 General 6.6.2 Message exchange pattern Figure 32 \u2013 Example of a meter read response with namedReadingType and ReadingQuality elements <\/td>\n<\/tr>\n 59<\/td>\n | Figure 33 \u2013 Message exchange pattern for a set of unsolicted meter reads | Figure 34 \u2013 Example of an unsolicited meter read message <\/td>\n<\/tr>\n 60<\/td>\n | 6.6.3 Missing reads | Figure 35 \u2013 Example of a missing reading in a published message <\/td>\n<\/tr>\n 61<\/td>\n | 6.6.4 Unsolicited MeterReads together with EndDeviceEvents | Figure 36 \u2013 Example of a known missing reading in a published message <\/td>\n<\/tr>\n 62<\/td>\n | 6.7 More about timestamps and interval data | 6.7.1 General Figure 37 \u2013 Example of a message showing both an event and a reading <\/td>\n<\/tr>\n 63<\/td>\n | 6.7.2 Interval data | Figure 38 \u2013 Reading Timestamps <\/td>\n<\/tr>\n 64<\/td>\n | 6.7.3 The interval block | 6.7.4 Raw data <\/td>\n<\/tr>\n 65<\/td>\n | 7 Meter control requests and responses | 7.1 General Figure 39 \u2013 Example use of IntervalBlocks <\/td>\n<\/tr>\n 66<\/td>\n | 7.2 Message exchange pattern | Tables Table 1 \u2013 Common EndDeviceControls and their corresponding EndDeviceEvent codes <\/td>\n<\/tr>\n 67<\/td>\n | 7.3 Create(EndDeviceControls) message | 7.3.1 General Figure 40 \u2013 Message exchange pattern for a meter control operation <\/td>\n<\/tr>\n 68<\/td>\n | 7.3.2 EndDeviceControls element | Figure 41 \u2013 Example of a create(EndDeviceControls) message for one meter Figure 42 \u2013 Example of a create(EndDeviceControls) message for two meters <\/td>\n<\/tr>\n 69<\/td>\n | Figure 43 \u2013 EndDeviceControls definition <\/td>\n<\/tr>\n | 71<\/td>\n | Figure 44 \u2013 EndDeviceControl definition <\/td>\n<\/tr>\n | 72<\/td>\n | 7.4 Reply(EndDeviceControls) message | Figure 45 \u2013 EndDeviceControlType definition Figure 46 \u2013 Example of a reply(EndDeviceControls) message <\/td>\n<\/tr>\n 73<\/td>\n | 7.5 Created(EndDeviceEvents) message | 7.5.1 General 7.5.2 EndDeviceEvents element Figure 47 \u2013 Example of a created(EndDeviceEvents) message Figure 48 \u2013 EndDeviceEvents definition <\/td>\n<\/tr>\n 75<\/td>\n | Figure 49 \u2013 EndDeviceEvent definition <\/td>\n<\/tr>\n | 76<\/td>\n | 7.6 Unsolicited EndDeviceEvents Messages | 7.6.1 General Figure 50 \u2013 EndDeviceEventType definition <\/td>\n<\/tr>\n 77<\/td>\n | 7.6.2 Message exchange pattern | 7.7 Premises area networks 7.7.1 General 7.7.2 Message exchange pattern Figure 51 \u2013 Message exchange pattern for an unsolicted EndDevice event Table 2 \u2013 Common EndDeviceEvent codes for unsolicited messages <\/td>\n<\/tr>\n 78<\/td>\n | 7.7.3 Pairing the Meter and PAN device | 8 Configuration and provisioning 8.1 General <\/td>\n<\/tr>\n 79<\/td>\n | 8.2 Message exchange pattern | Table 3 \u2013 Config Profiles <\/td>\n<\/tr>\n 80<\/td>\n | 8.3 Meter configuration | 8.3.1 General Figure 52 \u2013 Message exchange pattern for a create(MeterConfig) message <\/td>\n<\/tr>\n 81<\/td>\n | 8.3.2 Create(MeterConfig) message | Figure 53 \u2013 MeterConfig definition <\/td>\n<\/tr>\n 82<\/td>\n | Figure 54 \u2013 Example of a create(MeterConfig) message <\/td>\n<\/tr>\n | 83<\/td>\n | 8.3.3 Reply(MeterConfig) message, success case | 8.3.4 Reply(MeterConfig) message, failure case 8.4 Master data linkage 8.4.1 General Figure 55 \u2013 Example of a reply(MeterConfig) message, success case Figure 56 \u2013 Example of a reply(MeterConfig) message, failure case <\/td>\n<\/tr>\n 84<\/td>\n | 8.4.2 Create(MasterDataLinkage) message | Figure 57 \u2013 MasterDataLinkageConfig Relationships <\/td>\n<\/tr>\n 85<\/td>\n | 8.5 OperationSets | 8.5.1 General Figure 58 \u2013 Example of a create(MasterDataLinkageConfig) message <\/td>\n<\/tr>\n 86<\/td>\n | 8.5.2 OperationSet request message <\/td>\n<\/tr>\n | 87<\/td>\n | Figure 59 \u2013 Example of an execute(OperationSet) message <\/td>\n<\/tr>\n | 88<\/td>\n | 8.5.3 OperationSet Response Message | Figure 60 \u2013 Example of a reply(OperationSet) message, success case <\/td>\n<\/tr>\n 89<\/td>\n | 9 Scheduling actions for future execution | 9.1 General 9.2 Scheduling a meter read 9.2.1 General Figure 61 \u2013 Example of a reply(OperationSet) message, failure case <\/td>\n<\/tr>\n 90<\/td>\n | 9.2.2 Message exchange pattern <\/td>\n<\/tr>\n | 91<\/td>\n | 9.2.3 MeterReadSchedule element | Figure 62 \u2013 Message exchange pattern for scheduling a set of meter reads <\/td>\n<\/tr>\n 92<\/td>\n | Figure 63 \u2013 MeterReadSchedule definition <\/td>\n<\/tr>\n | 94<\/td>\n | 9.3 Create(MeterReadSchedule) message | 9.3.1 General Figure 64 \u2013 MeterReadSchedule.TimeSchedule definition <\/td>\n<\/tr>\n 95<\/td>\n | 9.3.2 Reply(MeterReadSchedule) message | Figure 65 \u2013 Example of a meter read schedule request Figure 66 \u2013 Example of a response to a meter read schedule request <\/td>\n<\/tr>\n 96<\/td>\n | 9.4 Cancelling a request | 9.4.1 General 9.4.2 Cancel(MeterReadSchedule) request <\/td>\n<\/tr>\n 97<\/td>\n | 10 Transporting IEC 61968-9 messages | 10.1 General 10.2 Transporting over SOAP 10.2.1 General Figure 67 \u2013 Example of a meter read schedule cancel message Figure 68 \u2013 Example of a simple meter read request imbedded in a SOAP message <\/td>\n<\/tr>\n 98<\/td>\n | 10.2.2 Generic WSDL | 10.2.3 Simple acknowledgement messages <\/td>\n<\/tr>\n 99<\/td>\n | 10.2.4 Example message flow | Figure 69 \u2013 Example of a simple acknowledgement message <\/td>\n<\/tr>\n 100<\/td>\n | 10.3 Transporting over JMS | 10.3.1 General Figure 70 \u2013 Message exchange pattern showing the simple acknowledgement messages <\/td>\n<\/tr>\n 101<\/td>\n | 10.3.2 Explicit acknowledgements | 10.3.3 JMS property details 10.3.4 Process details Table 4 \u2013 JMS properties <\/td>\n<\/tr>\n 102<\/td>\n | 10.3.5 Object details | 11 Summary of message fields 11.1 General 11.2 Meter read operations 11.2.1 General 11.2.2 Request message <\/td>\n<\/tr>\n 103<\/td>\n | Table 5 \u2013 get(MeterReadings) fields <\/td>\n<\/tr>\n | 104<\/td>\n | 11.2.3 Response message <\/td>\n<\/tr>\n | 105<\/td>\n | Table 6 \u2013 reply(MeterReadings) fields <\/td>\n<\/tr>\n | 108<\/td>\n | 11.2.4 Unsolicited meter read | 11.3 Meter control operations 11.3.1 General 11.3.2 Request message elements <\/td>\n<\/tr>\n 109<\/td>\n | Table 7 \u2013 create(EndDeviceControls) fields <\/td>\n<\/tr>\n | 110<\/td>\n | 11.3.3 Initial response message | Table 8 \u2013 reply(EndDeviceControls) fields <\/td>\n<\/tr>\n 111<\/td>\n | 11.3.4 Subsequent consequential event messages | Table 9 \u2013 created(EndDeviceEvents) fields <\/td>\n<\/tr>\n 113<\/td>\n | 11.3.5 Unsolicited meter event | 11.4 Configuration and provisioning 11.4.1 General 11.4.2 Provisioning a meter Table 10 \u2013 create(MeterConfig) fields <\/td>\n<\/tr>\n 115<\/td>\n | 11.4.3 Creation of a ComModule | Table 11 \u2013 create(ComModuleConfig) fields <\/td>\n<\/tr>\n 116<\/td>\n | 11.4.4 ServiceLocation <\/td>\n<\/tr>\n | 117<\/td>\n | Table 12 \u2013 create(ServiceLocationConfig) fields <\/td>\n<\/tr>\n | 118<\/td>\n | 11.4.5 ServiceCategoryConfig | 11.4.6 Service supplier Table 13 \u2013 create(ServiceCategoryConfig) fields <\/td>\n<\/tr>\n 119<\/td>\n | Table 14 \u2013 create(ServiceSupplierConfig) fields <\/td>\n<\/tr>\n | 120<\/td>\n | 11.4.7 UsagePoint location <\/td>\n<\/tr>\n | 121<\/td>\n | Table 15 \u2013 create(UsagePointLocationConfig) fields <\/td>\n<\/tr>\n | 122<\/td>\n | 11.4.8 Usage point | Table 16 \u2013 create(UsagePointConfig) fields <\/td>\n<\/tr>\n 124<\/td>\n | 11.4.9 Customer <\/td>\n<\/tr>\n | 125<\/td>\n | Table 17 \u2013 create(CustomerConfig) fields <\/td>\n<\/tr>\n | 126<\/td>\n | 11.4.10 Customer account <\/td>\n<\/tr>\n | 127<\/td>\n | Table 18 \u2013 create(CustomerAccountConfig) fields <\/td>\n<\/tr>\n | 128<\/td>\n | 11.4.11 Customer Agreement | Table 19 \u2013 create(CustomerAgreementConfig) fields <\/td>\n<\/tr>\n 130<\/td>\n | 11.4.12 Pricing Structure | Table 20 \u2013 create(PricingStructureConfig) fields <\/td>\n<\/tr>\n 131<\/td>\n | 11.4.13 MasterDataLinkage | Table 21 \u2013 create(MasterDataLinkageConfig) fields, example 1 <\/td>\n<\/tr>\n 133<\/td>\n | Table 22 \u2013 create(MasterDataLinkageConfig) fields, example 2 <\/td>\n<\/tr>\n | 134<\/td>\n | 11.4.14 OperationSet | Table 23 \u2013 execute(OperationSet) Header and Payload fields, example 1 <\/td>\n<\/tr>\n 137<\/td>\n | Table 24 \u2013 execute(OperationSet) Header and Payload fields, example 2 <\/td>\n<\/tr>\n | 139<\/td>\n | 11.4.15 Adding, changing or deleting an object identifier <\/td>\n<\/tr>\n | 141<\/td>\n | Table 25 \u2013 execute(OperationSet) Header and Payload fields, example 3 <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" | Application integration at electric utilities. System interfaces for distribution management – Guidance for implementation of IEC 61968-9<\/b><\/p>\n |