BS EN 62056-7-3:2017
$167.15
Electricity metering data exchange. The DLMS/COSEM suite – Wired and wireless M-Bus communication profiles for local and neighbourhood networks
| Published By | Publication Date | Number of Pages |
| BSI | 2017 | 44 |
This International Standard specifies DLMS/COSEM wired and wireless M-Bus communication profiles for local and neighbourhood networks.
Setting up and managing the M-Bus communication channels of M-Bus devices, the M-Bus network, registering slave devices and – when required – repeaters is out of the scope of this International Standard.
The scope of this communication profile standard is restricted to aspects concerning the use of communication protocols in conjunction with the COSEM data model and the DLMS/COSEM application layer. Data structures specific to a communication protocol are out of the scope of this standard. Any project-specific definitions of data structures and data contents may be provided in project-specific companion specifications.
Annex A (informative) provides information on M-Bus frame structures, addressing schemes and an encoding example.
Annex B (normative) points to COSEM interface classes to set up and manage the wired and wireless M-Bus communication channel.
Annex C (informative) provides MSCs for representative instances of communication.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | National foreword |
| 7 | CONTENTS |
| 9 | FOREWORD |
| 11 | INTRODUCTION |
| 12 | 1 Scope 2 Normative references |
| 13 | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions 3.2 Abbreviated terms |
| 14 | 4 Targeted communication environments 5 Use of the communication layers for this profile 5.1 Information related to the use of the standard specifying the lower layers 5.2 Structure of the communication profiles Figures Figure 1 – Entities and interfaces of a smart metering system using the terminology of IEC 62056-1-0 |
| 15 | 5.3 Lower protocol layers and their use 5.3.1 Physical layer 5.3.2 Link layer Figure 2 – The DLMS/COSEM wired and wireless M-Bus communication profiles |
| 16 | 5.3.3 Transport layer 5.4 Service mapping and adaptation layers 5.4.1 Overview |
| 17 | 5.4.2 MBUS-DATA service primitives Figure 3 – Summary of DLMS/COSEM M-Bus-based TL services |
| 19 | 5.4.3 MBUS-DATA protocol specification |
| 21 | 5.5 Registration and connection management 6 Identification and addressing scheme 6.1 Overview |
| 22 | 6.2 Link Layer Address for wired M-Bus Figure 4 – Identification and addressing scheme in the wired M-Bus profile |
| 23 | 6.3 Link Layer Address for wireless M-Bus 6.4 Link Layer Address for M-Bus broadcast Figure 5 – Link Layer Address for wireless M-Bus Tables Table 1 – Wired M-Bus Link Layer Addresses |
| 24 | 6.5 Transport layer address Table 2 – DLMS/COSEM M-Bus-based TL CITL values |
| 25 | Figure 6 – M-Bus TPDU formats Figure 7 – CITL without M-Bus data header |
| 26 | 6.6 Application addressing extension – M-Bus wrapper Table 3 – CI fields used for link management purposes Table 4 – Client and server SAPs |
| 27 | 7 Specific considerations and constraints for using certain services within profile 7.1 Overview 7.2 Application association establishment and release: ACSE services Table 5 – Application associations and data exchange in the M-Bus-based profiles |
| 28 | 7.3 xDLMS services 7.3.1 Request – response type services 7.3.2 Unsolicited services 7.3.3 Broadcast messages |
| 29 | 7.4 Security mechanisms 7.5 Transporting long application messages 7.6 Media access, bandwidth and timing considerations 8 Communication configuration and management |
| 30 | Annex A (informative)M-Bus frame structures, addressing schemes and examples A.1 General Figure A.1 – M-Bus communication paths direct or cascaded |
| 31 | A.2 None, short or long M-Bus data header |
| 32 | Figure A.2 – Wired M-Bus frame structure, none M-Bus data header Figure A.3 – Wired M-Bus frame structure with long M-Bus data header |
| 34 | Figure A.4 – Wireless M-Bus frame structure with short ELL, no M-Bus data header Figure A.5 – Wireless M-Bus frame structure with long ELL, no M-Bus data header |
| 35 | A.3 Encoding example: Data-Notification carrying daily billing data Figure A.6 – Wireless M-Bus frame structure with long ELL and long M-Bus data header |
| 36 | Table A.1 – Example: Daily billing data |
| 37 | Figure A.7 – Daily billing data without / with DLMS/COSEM security applied |
| 38 | Annex B (normative) New COSEM interface classes related to the M-Bus communication profiles |
| 39 | Annex C (informative)Message sequence charts |
| 42 | Bibliography |
