Method and system for collecting consumption data measured by smart meter

Abstract

In an automation management system (100), an information system (110) delegates collection of consumption data to a data concentrator (120). Consumption data from the primary smart meter (150) is collected over the communication network (101) in the form of traffic data formatted according to the communication protocol P2. In order to collect consumption data from the secondary smart meter (151a), at least one gateway (140a) is used, which consumption data is then collected in the form of traffic data formatted according to the communication protocol P1. Asymmetric encryption is used end-to-end to ensure non-repudiation of the data collected from the secondary smart meter (151a), and the traffic data formatted according to the communication protocol P1 is encapsulated in traffic data formatted according to the communication protocol P2 to enable them to be transmitted via the communication network (101).

Description

Technical Field

[0001] At least one embodiment relates to a method and system for collecting consumption data measured by smart meters. The system in question is suitable for collecting such data from a plurality of smart meters, whether for measurement of consumption of fluids (such as gas, water, heat, gasoline) or electricity consumption measurement. Background Art

[0002] Smart meters, such as electricity meter type (electricity consumption meter) or fluid meter (fluid consumption meter), are known, which include a communication interface that enables an automated management system to carry out remote collection of consumption data. For example, a smart electricity meter includes a communication interface of the Power Line Communication (PLC) type. Thus, the consumption data can be sent at regular or irregular intervals to an information system IS that processes the consumption data in a centralized manner.

[0003] The collected consumption data must be free of errors in order to avoid any disputes related to the competition of their values. Errors may especially originate from changes during the transmission of the consumption data. In the event of a dispute between a customer and a service provider regarding the consumption data, one solution consists in the service provider assigning an operator to the customer to read the consumption data directly on the display of the meter. Such a solution is not satisfactory because it firstly requires the meter to be equipped with a display and secondly requires the operator to go to the customer's home, which is lengthy and expensive.

[0004] It is therefore desirable to provide a solution that makes it possible to prove that consumption data collected remotely from smart meters by an information system really comes from said smart meters. It is particularly desirable to provide a solution that makes it easy to change existing collection infrastructures (i.e., collection infrastructures that are already deployed in the field) while ensuring that the collected consumption data cannot be denied. Summary of the invention

[0005] For this purpose, a method is proposed for collecting consumption data by an information system in an automated management system, the automated management system comprising a data concentrator and a communication network, the information system entrusting this collection of data to the data concentrator, the data concentrator collecting, via the communication network, consumption data formatted according to a communication protocol P2 from smart meters of a first type, called primary smart meters, the automated management system also comprising at least one gateway connected to the communication network, each gateway acting as a relay for collecting consumption data formatted according to a communication protocol P1 from smart meters of a second type, called secondary smart meters, the method enabling:

[0006] - Each secondary smart meter sends its consumption data together with a hash code derived from said consumption data in transaction data formatted according to the communication protocol P1 and signed using a private asymmetric encryption key;

[0007] - Each gateway relays the data signed by the secondary smart meter to the data concentrator via the communication network, while encapsulating the data in service data formatted according to the communication protocol P2;

[0008] - the data concentrator relays to the information system the service data formatted according to the communication protocol P2 received via the communication network;

[0009] And when the service data formatted according to the communication protocol P2 includes the service data formatted according to the communication protocol

[0010] When processing business data in P1 format, the information system:

[0011] - decrypting the service data formatted according to the communication protocol P1 using the asymmetric public encryption key corresponding to the secondary smart meter from which the consumption data should be collected,

[0012] - generating a reference hash code from the consumption data received in the decrypted service data and from information known to the information system,

[0013] - comparing the generated reference hash code with the hash code received in the decrypted business data, and verifying the consumption data received in the decrypted business data when the generated reference hash code matches the hash code received in the decrypted business data.

[0014] Therefore, it is easy to change the existing collection infrastructure suitable for collecting consumption data from the primary smart meter (i.e., the collection infrastructure already deployed in the field) so as to further allow the collection of the consumption data from the secondary smart meter while ensuring the non-repudiation of the consumption data collected from the secondary smart meter.

[0015] In a particular embodiment, the primary smart meter is a smart electricity meter and the secondary smart meter is a smart meter for consumption of fluid (gas, water, petrol, etc.).

[0016] In a particular embodiment, the communication protocol P1 is a communication protocol of the M-Bus or wM-Bus type.

[0017] In a particular embodiment, the communication protocol P2 is a DLMS / COSEM type communication protocol.

[0018] In a particular embodiment, the hash code derived from the consumption data is calculated by applying a hash function to a four-tuple including the serial number of the meter, a cyclic redundancy code calculated using the metering software used to obtain the consumption data, a certificate number certifying that the secondary smart meter can be used in the automation management system, and the consumption data itself.

[0019] In a particular embodiment, the traffic data according to the protocol P2 are transmitted in encrypted form via the communication network using a symmetric encryption key specific to the communication between the gateway in question and the data concentrator.

[0020] In a particular embodiment, the traffic data according to the protocol P1 are transmitted in encrypted form from the secondary smart meter in question to the gateway in question using a symmetric encryption key specific to the communication between said secondary smart meter and the gateway in question.

[0021] It is also proposed an automation management system configured to collect consumption data, the automation management system comprising an information system and a data concentrator, the information system being configured to delegate this collection of data to the data concentrator, the automation management system also comprising a communication network via which the data concentrator collects consumption data formatted according to a communication protocol P2 from smart meters of a first type, referred to as primary smart meters, the automation management system also comprising at least one gateway connected to the communication network, each gateway acting as a relay for collecting consumption data formatted according to the communication protocol P1 from smart meters of a second type, referred to as secondary smart meters, the automation management system comprising an electronic circuit configured such that:

[0022] - Each secondary smart meter sends its consumption data together with a hash code derived from said consumption data in transaction data formatted according to the communication protocol P1 and signed using a private asymmetric encryption key;

[0023] - Each gateway relays the data signed by the secondary smart meter to the data concentrator via the communication network, while encapsulating the data in service data formatted according to the communication protocol P2;

[0024] - the data concentrator relays to the information system the service data formatted according to the communication protocol P2 received via the communication network;

[0025] And when the service data formatted according to the communication protocol P2 includes the service data formatted according to the communication protocol

[0026] When processing business data in P1 format, the information system:

[0027] - decrypting the service data formatted according to the communication protocol P1 using the asymmetric public encryption key corresponding to the secondary smart meter from which the consumption data should be collected,

[0028] - generating a reference hash code from the consumption data received in the decrypted service data and from information known to the information system,

[0029] - comparing the generated reference hash code with the hash code received in the decrypted business data, and verifying the consumption data received in the decrypted business data when the generated reference hash code matches the hash code received in the decrypted business data. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The above and other features of the present invention will appear more clearly upon reading the following description of at least one example embodiment, said description being made with respect to the accompanying drawings, in which:

[0031] Figure 1A Schematically illustrates an automated management system for collecting consumption data;

[0032] Figure 1B Schematically illustrates the arrangement of the information system of the automation management system in a specific embodiment;

[0033] Figure 2 An example of a hardware architecture of a device suitable for implementing an automated management system is schematically shown;

[0034] Figure 3A Schematically illustrating a first protocol stack suitable for collecting consumption data with respect to secondary smart meters in an automation management system;

[0035] Figure 3B schematically illustrates a second protocol stack suitable for collecting consumption data with respect to secondary smart meters in an automation management system;

[0036] Figure 3C schematically illustrates a third protocol stack suitable for collecting consumption data with respect to secondary smart meters in an automation management system;

[0037] Figure 4A Schematically illustrating a first protocol stack suitable for collecting consumption data with respect to primary smart meters in an automation management system;

[0038] Figure 4B schematically illustrates a second protocol stack suitable for collecting consumption data with respect to primary smart meters in an automation management system;

[0039] Figure 5schematically illustrates a series of sending and processing operations in the context of collecting consumption data from secondary smart meters;

[0040] Figure 6 schematically illustrates an algorithm implemented by a secondary smart meter for sending frames to a gateway;

[0041] Figure 7 schematically illustrates an algorithm implemented by a gateway for sending frames to a data concentrator;

[0042] Figure 8 schematically illustrates an algorithm implemented by a data concentrator for sending frames to an information system; and

[0043] Fig. 9 An algorithm implemented by an information system for processing frames received from a data concentrator is schematically shown. DETAILED DESCRIPTION

[0044] Figure 1A Schematically illustrated is an automation management system 100 in which the present invention may be implemented. The automation management system 100 is configured to collect consumption data resulting from measurements made by smart meters 150 , 151a , 151b , 152 .

[0045] exist Figure 1A Schematically shown above are two types of smart meters: a so-called primary smart meter (PSM) 150 and so-called secondary smart meters (SSM) 151a, 151b. The secondary smart meters SSM 151a, 151b are configured to implement a communication protocol P1. The primary smart meter PSM 150 is configured to implement a communication protocol P2 that is different from the communication protocol P1. The secondary smart meters SSM 151a, 151b do not implement the communication protocol P2.

[0046] As detailed below, Figure 1A A specific functionality is also shown, namely a primary smart meter functionality PSMF 152 attached to the gateway GW 140a, 140b. The primary smart meter functionality PSMF 152 is configured to implement the communication protocol P2, similar to the primary smart meter PSM 150.

[0047] The consumption data from the smart meters are collected via the communication network NET1 101. The primary smart meter PSM 150 has a communication interface with the communication network NET1 101. The consumption data from the primary smart meter PSM 150 is therefore collected directly from said primary smart meter PSM 150.

[0048] The consumption data from the secondary smart meters SSM 151a, 151b are collected through the gateways GW 140a, 140b. The gateways GW 140a, 140b act as relays for the consumption data from the secondary smart meters SSM 151a, 151b which do not have a communication interface suitable for the communication network NET1 101.

[0049] In a specific embodiment, if Figure 1A As shown, at least one gateway GW 140a has a primary smart meter functionality PSMF 152. The primary smart meter functionality PSMF 152 is included in the gateway GW 140a, or is implemented in a device connected to the gateway GW 140a via a simple electrical physical layer, such as a physical layer according to the standard EIA-485 (commonly known as RS-485) or according to the standard RS-232. In other words, the gateway GW 140a interacts with the primary smart meter functionality PSMF 152 in order to specifically obtain consumption data from the primary smart meter functionality PSMF 152 implementing the communication protocol P2. The assembly formed by the gateway GW 140a and the primary smart meter functionality PSMF 152 is therefore equivalent to the primary smart meter PSM 150 (where the gateway GW 140a, 140b provides access to the communication network NET1 101), and further has a relay capability on behalf of the secondary smart meters SSM151a, 151b.

[0050] In a particular embodiment, the communication network NET1 101 is a PLC network, the primary smart meter PSM 150 is an electricity meter, and the secondary smart meters SSM 151a, 151b are meters for consumption of fluids (gas, water or other). The secondary smart meters SSM 151a, 151b then typically run on batteries. For example, the communication network NET1 101 complies with the G3-PLC or PRIME or G3-Hybrid or PRIME-Hybrid specifications.

[0051] The collected consumption data is processed by the information system IS110. The information system IS110 delegates the collection of the consumption data to the data concentrators DC 120 in order to distribute the collection load. Each data concentrator DC 120 thus manages a collection network, such as the communication network NET1 101, and acts as a relay between the smart meters and the information system IS110. Thus, at least one data concentrator DC 120 manages the collection network to which the primary smart meters PSM 150 as well as the secondary smart meters SSM151a, 151b and possibly the primary smart meter functionality PSMF 152 are connected via gateways GW 140a, 140b.

[0052] like Figure 1AAs shown schematically, the data concentrator DC 120 is outside the information system IS110 and communicates with the information system IS110 through the communication network NET2 102. In a variant embodiment, the data concentrator DC 120 is virtualized in the information system IS110. For example, the communication network NET2102 is a wireless communication network of the 5G (fifth generation) type. According to other examples, the communication network NET2102 is a wireless communication network of the GPRS ("General Packet Radio Service"), UMTS ("Universal Mobile Telecommunications System"), LTE ("Long Term Evolution"), NB-IoT ("Narrowband Internet of Things"), 2G or 3G type.

[0053] The primary smart meter PSM 150 and the primary smart meter functionality PSMF 152 format the consumption data using formatting according to the communication protocol P2. The communication protocol P2 specifies the service data format (i.e. application data) and the transmission data and transmission rules suitable for sending these service data. Therefore, in order to be able to interpret these service data, the equipment must be compatible with the communication protocol P2 (i.e., in addition to the interpretation of the transmission data and the knowledge of the transmission rules). The data concentrator DC 120 is compatible with the communication protocol P2.

[0054] In a particular embodiment, the communication protocol P2 complies with the DLMS / COSEM ("Device Language Message Specification / Companion Specification for Energy Metering") specification, as described in the IEC 62056 series of standards.

[0055] The primary smart meters SSM 151a, 151b format their consumption data using formatting according to the communication protocol P1. The communication protocol P1 specifies the service data format (i.e. application data) as well as the transmission data and transmission rules suitable for sending these service data. Therefore, in order to be able to interpret these service data, the equipment must be compatible with the communication protocol P1 (i.e., in addition to the interpretation of the transmission data and the knowledge of the transmission rules). The communication protocol P1 is different from the communication protocol P2. The data concentrator DC 120 is not compatible with the communication protocol P1.

[0056] In a particular embodiment, the communication protocol P1 complies with the M-Bus ("Meter Bus") Remote Reading specification as defined in EN 13757-2 or the wM-Bus ("Wireless M-Bus") specification as defined in EN 13757-4.

[0057] Figure 1BThe arrangement of an information system IS 110 in a particular embodiment is schematically shown. Thus, the information system IS 110 includes various components, including a network headend system (HES) 112, a meter data management system (MDMS) 111, a first key management system (KMS) 113 denoted KMS1, and a second key management system 114 denoted KMS2.

[0058] The network headend system HDS112 is configured to manage the transmission in the context of collecting consumption data, and the meter data management system MDMS111 is configured to process the collected consumption data. The first key management system KMS1 113 is configured to store symmetric encryption keys. There is a first symmetric encryption key SK1 for each secondary smart meter SSM 151a, 151b, so as to communicate in a secure manner with the gateway GW 140a, 150b on which the secondary smart meter SSM 151a, 151b depends. There is a second symmetric encryption key SK2 for each primary smart meter PSM 150, so as to communicate in a secure manner with the data concentrator DC 120. There is also a second symmetric encryption key SK2 for each gateway GW 140a, 140b, so as to communicate in a secure manner with the data concentrator DC 120. The first key management system KMS1113 is configured to ensure that each device in the automation management system 100 has available each symmetric encryption key SK1, SK2 necessary for it.

[0059] The second key management system KMS2 114 is configured to store public asymmetric encryption keys. There is a public asymmetric encryption key AK1 for each secondary smart meter SSM 151a, 151b. A private asymmetric encryption key AK2, which is stored in the automation management system 100 only by the secondary smart meter SSM151a, 151b in question, corresponds to each public asymmetric encryption key AK1. The private asymmetric encryption key AK2 is derived, for example, from the serial number of the corresponding secondary smart meter SSM 151a, 151b. The public asymmetric encryption key AK1 is used to decrypt the encrypted data by means of the corresponding private asymmetric encryption key AK2. Each pair consisting of the public asymmetric encryption key AK1 and the private asymmetric encryption key AK2 makes it possible to ensure the non-repudiation of the consumption data sent from the secondary smart meter SSM 151a, 151b in question to the information system IS110.

[0060] Therefore, the encryption keys stored by the second key management system KMS2 114 are accessed by the meter data management system MDMS 111. And, depending on the infrastructure of the information system IS 110 and the automation management system 100, the encryption keys stored by the first key management system KMS1 13 are accessed by the meter data management system MDMS 111 and / or by the network headend system HES 112.

[0061] In a variant, the first key management system KMS1 113 and the second key management system KMS2 114 are combined in the same key management system KMS, and then store the above-mentioned symmetric encryption keys and public asymmetric encryption keys.

[0062] The components of the information system IS110 communicate for example using the Internet or more generally using a network of the IP (“Internet Protocol”) type or potentially using a virtual private network VPN.

[0063] Figure 2 Schematically, an example of a hardware architecture 200 suitable for implementing any device of the automation management system 100 is shown. The example of the hardware architecture is therefore suitable for implementing a controller of the information system IS110 or any component of the information system IS110. The example of the hardware architecture is also suitable for implementing a controller of the data concentrator DC 120. The example of the hardware architecture is also suitable for implementing a controller of the primary smart meter PSM 150. The example of the hardware architecture is also suitable for implementing a controller of the secondary smart meters SSM 151a, 151b. The example of the hardware architecture is also suitable for implementing a controller of the gateway GW 140a, 140b. The example of the hardware architecture is also suitable for implementing a controller of a device implementing the primary smart meter functionality PSMF 152.

[0064] The hardware architecture 200 then comprises: a processor or CPU (“Central Processing Unit”) 201; a random access memory (RAM) 202; a read-only memory (ROM) 203 or EEPROM (“Electrically Erasable Programmable Read-Only Memory”) or Flash memory; a data storage medium (DSM) such as a hard disk drive HDD or a storage medium reader such as an SD (Secure Digital) card reader; and at least one communication interface COM 205, connected via a communication bus 210. Depending on the device involved, the hardware architecture 200 may also comprise inputs / outputs, for example to carry out consumption measurements.

[0065] The processor 201 is capable of executing instructions loaded from the ROM 203, from an external memory (not shown), from a storage medium (such as an SD card), or from a communication network in the RAM 202. When the hardware architecture 200 is powered on, the processor 201 is capable of reading instructions from the RAM 202 and executing the instructions. These instructions form a computer program that enables the processor 201 to implement the steps and methods described herein with respect to the devices involved.

[0066] All or some of the steps and algorithms described herein may thus be implemented in software by executing instruction sets by a programmable machine such as a DSP ("digital signal processor") or a microcontroller, or in hardware by a machine or a component (chip) or a set of components (chip set) such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). In general, each device of the automation management system 100 includes electronic circuits that are arranged and configured to implement the steps and algorithms described herein with respect to the device in question.

[0067] FIG. 3A to FIG. 3C A protocol stack suitable for collecting consumption data with respect to secondary smart meters SSM 151a , 151b in the automation management system 100 is schematically shown.

[0068] Figure 3A A first protocol stack is shown, which is suitable for sending consumption data from a secondary smart meter SSM 151a, 151b to a gateway GW 140a, 140b on which the secondary smart meter SSM 151a, 151b depends. The first protocol stack comprises:

[0069] - Business data BD_P1 301;

[0070] - Transmission data TD_P1 302.

[0071] The business data BD_P1 301 is formatted according to the communication protocol P1. The business data BD_P1 301 comprises consumption data, which has to be sent to the information system IS110. The business data BD_P1 301 is signed by the private asymmetric encryption key AK2 of the secondary smart meter SSM 151a, 151b from which said consumption data comes.

[0072] For example, the business data BD_P1 301 is obtained by asymmetrically encrypting a data set including a hash code represented as HASH from a four-tuple including:

[0073] - the serial number of the secondary smart meter SSM 151a, 151b in question;

[0074] - Cyclic Redundancy Code (CRC) which is used by the secondary smart meter SSM in question

[0075] 151a and 151b are calculated using the metrology software used;

[0076] - the MID (“Measuring Instrument Directive”) certificate number attributed to the secondary smart meter SSM 151a, 151b in question, said certificate certifying the secondary smart meter SSM in question

[0077] 151a, 151b have passed the certification test, thereby allowing them to be used in the automation management system 100 (especially to participate in consumption invoicing operations);

[0078] - Consumption data D.

[0079] In the context of legal metrology, a cyclic redundancy code CRC is calculated when the metrology software is generated. This cyclic redundancy code CRC is incorporated in the metrology software to which said cyclic redundancy code CRC corresponds. The metrology software is verified and then transmitted for authentication in order to obtain authentication. Once authentication is obtained, the MID certificate number is provided to the meter data management system MDMS111, which then stores, for each meter so authenticated, the cyclic redundancy code CRC of the meter software of said meter and the MID certificate number in a memory in association with the serial number of the meter in question.

[0080] To obtain the hash code, a hash function H(.) is used. The hash function H(.) is a specific function that calculates a numerical hash code for quickly identifying the initial data based on the data provided as input. In other words, a single hash code (i.e., the result of the hash function H(.)) corresponds to a given quadruple. Therefore, for two different quadruple groups Q1 and Q2, the secondary smart meters SSM 151a, 151b generate two different hash codes S1=H(Q1) and S2=H(Q2).

[0081] In one embodiment, the function H(.) is a SHA-2 function (e.g., SHA-224, SHA-256, SHA-384, or SHA-512). In the case where the function H(.) is of the SHA-256 type, the obtained hash code HASH includes 256 bits. In the case where the function H is of the SHA-512 type, the obtained hash code HASH includes 512 bits. Other functions can be used as the H(.) function, such as, for example, a SHA-3 function, an MD4 function, an MD5 function, or a SHA-1 function, all of which are well known in the field of cryptography.

[0082] In a variant embodiment, the quadruplet is supplemented by padding bits in order to obtain an alignment on an integer number of bytes suitable for the hash function H(.) to be applied.

[0083] The concatenation of the obtained hash code and the consumption data is then included in the business data BD_P1 301 while respecting the formatting according to the communication protocol P1 .

[0084] The transmission data TD_P1 302 is transmission data according to the communication protocol P1. The transmission data TD_P1 302 and the business data BD_P1 301 are encrypted by means of a symmetric encryption key SK1 known to the secondary smart meter SSM 151a, 151b in question and to the gateway GW 140a, 140b on which said secondary smart meter SSM 151a, 151b depends.

[0085] Figure 3B A second protocol stack is shown, which is suitable for sending consumption data from secondary smart meters SSM 151a, 151b from the gateway GW 140a, 140b (on which the secondary smart meters SSM 151a, 151b depend) to the data concentrator DC 120. The second protocol stack comprises:

[0086] - Business data BD_P1 301;

[0087] - Business data BD_P2 303;

[0088] - transmission data TD_P2 304;

[0089] -Transmission data TD_P3 305.

[0090] The business data BD_P1 301 is encapsulated in business data BD_P2 303, for example in an object described in the business data of the communication protocol P2 (for example a COSEM object). To this end, the business data BD_P1 301 was previously decrypted by a symmetric decryption key SK1 known to the secondary smart meter SSM 151a, 151b and the gateway GW 140a, 140b in question. However, the business data BD_P1 301 remains signed (by a private asymmetric encryption key AK2).

[0091] The transmission data TD_P2 304 is transmission data according to the communication protocol P2.

[0092] The transmission data TD_P2 304 and the business data BD_P2 303 (including the encapsulated business data BD_P1 301) are encrypted by means of a symmetric encryption key SK2 known to the gateway GW 140a, 140b and the data concentrator DC 120 in question.

[0093] The transmission data TD_P3 305 is transmission data suitable for transmitting frames in the communication network NET1 101. For example, the transmission data TD_P3 305 conforms to the transmission specified in the G3-PLC specification.

[0094] Figure 3C A third protocol stack is shown, which is suitable for sending consumption data from secondary smart meters SSM 151a, 151b from the data concentrator DC 120 to the information system IS 110. The third protocol stack comprises:

[0095] - Business data BD_P1 301;

[0096] - Business data BD_P2 303;

[0097] - transmission data TD_P4 306;

[0098] -Transmission data TD_P5 307.

[0099] To this end, the business data BD_P2 303 (including the encapsulated business data BD_P1 301) are previously decrypted by the symmetric encryption key SK2 known to the gateway GW 140a, 140b in question and the data concentrator DC 120. Here, the business data BD_P1 301 also remains signed (by the private asymmetric encryption key AK2). As described below, the information system IS110 decrypts them.

[0100] The transmission data TD_P4 306 is the transmission data of the intermediate layer (e.g., the network layer in the OSI model) or the application layer. For example, the transmission data TD_P4 306 conforms to the transmission specified in the XML / HTTPS ("Extensible Markup Language / Hypertext Transfer Protocol Security") standard. Therefore, several intermediate layers can be stacked in this third protocol stack.

[0101] The transmission data TD_P5 307 is transmission data suitable for transmitting frames in the communication network NET2 102. For example, the transmission data TD_P5 307 complies with the transmission specified in the 5G specification.

[0102] The third protocol stack can also be used schematically for transmitting consumption data in the information system IS110, typically from the network headend system HES112 to the meter data management system MDMS111, where other protocol layers are involved. For example, the transmission data TD_P4 306 is transmission data of type IPv6 or IPv4, and the transmission data TD_P5 307 is transmission data of Ethernet type.

[0103] Figure 4A and Figure 4BSchematically shows a protocol stack suitable for collecting consumption data relative to the primary smart meter PSM 150 in the automation management system 100. In this case, the communication protocol P1 is not used. FIG. 3A to FIG. 3C Differently, asymmetric encryption is not used here, since the consumption data is directly formatted according to the communication protocol P2. In a variant, asymmetric encryption with the same properties as for the secondary smart meter can also be used here to achieve non-repudiation.

[0104] Figure 4A A first protocol stack suitable for sending consumption data from a primary smart meter PSM 150 to a data concentrator DC 120 is shown. The first protocol stack comprises:

[0105] - Business data BD_P2 401;

[0106] - transmission data TD_P2 402;

[0107] -Transmission data TD_P3 403.

[0108] The business data BD_P2 401 is formatted according to the communication protocol P2. The business data BD_P2 401 includes consumption data, which must be sent to the information system IS110.

[0109] For example, business data BD_P2 401 is a data set including a hash code denoted HASH calculated from a quadruple, as already described with respect to business data BD_P1 301 (without asymmetric encryption and also in a different format due to direct use of the communication protocol P2).

[0110] The transmission data TD_P2 402 is transmission data according to the communication protocol P2. As in the case of the secondary smart meters SSM 151a, 151b, the transmission data TD_P2 402 and the business data BD_P2 401 are encrypted by means of a symmetric encryption key SK2 known to the primary smart meter PSM 150 and the data concentrator DC 120 in question.

[0111] The transmission data TD_P3 403 is transmission data suitable for transmitting a frame in the communication network NET1 101 (similar to the transmission data TD_P3 305).

[0112] Figure 4B A second protocol stack is shown which is suitable for sending consumption data (from the primary smart meter PSM 150) from the data concentrator DC 120 to the information system IS 110. The second protocol stack comprises:

[0113] - Business data BD_P2 401;

[0114] - transmission data TD_P4 404;

[0115] -Transmission data TD_P5 405.

[0116] To this end, the business data BD_P2 401 is previously decrypted by means of the symmetric encryption key SK2 known to the gateway GW 140a, 140b and the data concentrator DC120 in question.

[0117] The transmission data TD_P4 404 (similar to the transmission data TD_P4 306) is the transmission data of the intermediate layer (eg the network layer in the OSI model) or the application layer. Therefore, several intermediate layers can be stacked in the second protocol stack.

[0118] The transmission data TD_P5 405 (similar to the transmission data TD_P5 307 ) is transmission data suitable for transmitting frames in the communication network NET2 102 .

[0119] It should be noted that, except for the FIG. 3A to FIG. 3C , Figure 4A and Figure 4B In addition to the symmetric encryption described above, intermediate protocol layers may also apply additional symmetric encryption.

[0120] Figure 5 A series of transmission and processing operations in the context of collecting consumption data from secondary smart meters SSM (eg, secondary smart meter SSM 151a ) via the gateway GW 140a are schematically illustrated.

[0121] The secondary smart meter SSM 151a implements the process 600 (similar to the process described below with respect to Figure 6 described) based on Figure 3A The protocol stack sends frame 501 to gateway GW 140a.

[0122] Gateway GW 140a then implements process 700 (similar to the following description of Figure 7 described) based on Figure 3B The protocol stack sends frame 502 to the data concentrator DC 120.

[0123] Data concentrator DC 120 then implements process 800 (similar to the following description of Figure 8 described) based on Figure 3C The protocol stack sends frame 503 to the information system IS110.

[0124] Information system IS110 then implements process 900 (similar to the following with respect to Fig. 9 described) to process the received consumption data.

[0125] Figure 6The algorithm implemented by the secondary smart meters SSM 151a , 151b for sending consumption data to the information system IS 110 via the gateways GW 140a , 140b is schematically shown.

[0126] In step 601 , the secondary smart meters SSM 151 a , 151 b obtain consumption data D to be sent to the information system IS 110 through their metering software.

[0127] In step 602, the secondary smart meter SSM 151a, 151b preferably generates a hash code HASH based on a data set including consumption data D. In a specific embodiment, as previously described with respect to Figure 3A Generate a hash code as described.

[0128] In step 603 , the secondary smart meter SSM 151a , 151b signs the hash code (or if that is not possible the consumption data D) by means of its private asymmetric encryption key AK2 and thus obtains a signed hash code HASH′.

[0129] In step 604, the secondary smart meters SSM 151a, 151b are configured to Figure 3A The protocol stack of the communication protocol P1 is used to send frames. Therefore, the service data formatted according to the communication protocol P1 includes the encrypted hash code HASH' (encrypted by the private asymmetric encryption key AK2). In addition, the service and transmission data according to the communication protocol P1 are encrypted by the symmetric encryption key SK1 stored by the secondary smart meter SSM 151a, 151b in question.

[0130] Figure 7 The algorithm implemented by the gateway GW 140a , 140b for relaying consumption data from the secondary smart meters SSM 151a , 151b to the information system IS 110 via the data concentrator DC 120 is schematically shown.

[0131] In step 701, the gateway GW SSM 140a, 140b according to Figure 3A The protocol stack receives the frame.

[0132] In step 702, the gateway GW 140a, 140b recovers the service data formatted according to the communication protocol P1 in the received frame (which therefore includes the encrypted hash code HASH'). The service and transmission data according to the communication protocol P1 are thus encrypted by the symmetric encryption key SK1 corresponding to the secondary smart meter SSM 151a, 151b in question.

[0133] In step 703, the secondary smart meters SSM 151a, 151b are configured according to Figure 3BThe service data formatted according to the communication protocol P2 then includes the hash code HASH'. In addition, the service and transmission data according to the communication protocol P2 are encrypted by the symmetric encryption key SK2 stored by the gateway GW 140a, 140b in question.

[0134] Figure 8 Schematically illustrated is an algorithm implemented by the data concentrator DC 120 for relaying consumption data from secondary smart meters SSM 151a , 151b and received via gateways GW 140a , 140b to the information system IS 110 .

[0135] In step 801, the data concentrator DC 120 receives Figure 3B The protocol stack receives the frame.

[0136] In step 802, the data concentrator DC 120 recovers in the received frame the service data formatted according to the communication protocol P2, which therefore includes the hash code HASH' (without the data concentrator DC 120 having to know this). Furthermore, the service and transmission data according to the communication protocol P2 are encrypted by means of the symmetric encryption key SK2 corresponding to the gateway GW 140a, 140b in question.

[0137] In step 803, the data concentrator DC 120 Figure 3C The frame includes service data formatted according to the communication protocol P2, and therefore includes a hash code HASH' in a format according to the communication protocol P1.

[0138] Fig. 9 Schematically illustrated is an algorithm implemented by the information system IS 110 for processing frames received from the data concentrator DC 120 in the context of collecting consumption data from secondary smart meters SSM 151a , 151b .

[0139] In step 901, the information system IS110 Figure 3C The protocol stack receives the frame.

[0140] In step 902, the information system IS110 (more specifically, the meter data management system MDMS 111) interprets the business data formatted according to the communication protocol P2 and then recovers the business data formatted according to the communication protocol P1 encapsulated therein. By interpreting the business data formatted according to the communication protocol P1, the information system IS110 then recovers the signed hash code HASH'.

[0141] The information system IS110 (more specifically, the meter data management system MDMS111) is able to determine whether the service data formatted according to the communication protocol P2 firstly relates to the primary smart meter PSM 150 or the primary smart meter functionality PSMF 152, or secondarily relates to the secondary smart meter SSM 151a, 151b. According to one possibility, the service data formatted according to the communication protocol P2 includes included objects (e.g., COSEM objects) that are specific to the service data formatted according to the communication protocol P1. According to another possibility, the service data formatted according to the communication protocol P2 includes information identifying the smart meter (such as a serial number), and the information system IS110 knows for each smart meter in the automation management system 100 whether it is primary or secondary.

[0142] In step 903, the information system IS110 (more specifically, the meter data management system MDMS 111) decrypts the signed hash code HASH' using the public asymmetric encryption key AK2 associated with the secondary smart meter that generated the signed hash code HASH'. The service data formatted according to the communication protocol P2 includes information (such as a serial number) identifying the secondary smart meter involved, and the information system IS110 stores the public asymmetric encryption key AK2 corresponding to the information identifying the secondary smart meter SSM 151a, 151b.

[0143] In step 904, the information system IS110 (more specifically, the meter data management system MDMS 111) generates a reference hash code with the information it holds about the secondary smart meter SSM 151a, 151b in question. The reference hash code is generated in the same way as the hash code HASH generated by the secondary smart meter SSM 151a, 151b.

[0144] In step 905, the information system IS 110 (more specifically, the meter data management system MDMS 111) compares the hash code decrypted in step 903 with the reference hash code obtained in step 904. If there is a match between the two hash codes, step 906 is executed; otherwise, step 907 is executed.

[0145] In step 906, the information system IS 110 (more specifically the meter data management system MDMS 111) validates the received consumption data. These are validly from the secondary smart meters SSM 151a, 151b and have not been altered.

[0146] In step 907, the information system IS110, more specifically the meter data management system MDMS 111, invalidates the received consumption data. These cannot be attributed to the secondary smart meters SSM 151a, 151b. The information system IS110 then generates an alarm.

[0147] Thus, according to the above teachings, it is easy to upgrade the capabilities of an automation management system adapted to collect consumption data from a first type of smart meters using a communication protocol (here the communication protocol P2, such as DLMS / COSEM) so that the automation management system is also adapted to collect consumption data from a second type of smart meters using another communication protocol (here the communication protocol P1, such as M-Bus or wM-Bus). The information system IS (and in particular the meter data management system MDMS) must then be compatible with this other communication protocol (P1) and the use of asymmetric encryption and the gateway GW enables the non-repudiation of the consumption data sent by the second type of smart meters to be ensured. The upgrade for supporting the second type of smart meters is transparent to the connection network (here the communication network NET1 101) and to the data concentrator DC (which may have already been deployed on site).

Claims

1. A method for collecting consumption data by an information system (110) in an automated management system (100), the automated management system (100) comprising a data concentrator (120) and a communication network (101), the information system (110) delegating the collection of data to the data concentrator, the data concentrator (120) collecting consumption data formatted according to a communication protocol P2 from a first type of smart meter, referred to as a primary smart meter (150), via the communication network, the automated management system (100) further comprising at least one gateway (140a, 140b) connected to the communication network (101), each gateway (140a, 140b) acting as a relay for collecting consumption data formatted according to a communication protocol P1 from a second type of smart meter, referred to as a secondary smart meter (151a, 151b), the method causing: - Each secondary smart meter (151a, 151b) sends its consumption data together with a hash code derived from said consumption data in transaction data formatted according to said communication protocol P1 and signed using a private asymmetric encryption key; - Each gateway (140a, 140b) relays the data signed by the secondary smart meter (151a, 151b) to the data concentrator via the communication network, while encapsulating the data in service data formatted according to the communication protocol P2; - the data concentrator (120) relays the service data formatted according to the communication protocol P2 received via the communication network (101) to the information system (110); And when the service data formatted according to the communication protocol P2 includes service data formatted according to the communication protocol P1, the information system (110): - decrypting said service data formatted according to said communication protocol P1 using the asymmetric public encryption key corresponding to said secondary smart meter (151a, 151b) from which said consumption data should be collected, - generating a reference hash code from the consumption data received in the decrypted business data and from information known to the information system (100), - comparing the generated reference hash code with said hash code received in the decrypted business data, and validating said consumption data received in the decrypted business data when the generated reference hash code matches said hash code received in the decrypted business data. 2 . The method according to claim 1 , wherein the primary smart meter is a smart electricity meter and the secondary smart meter is a smart meter for consumption of a fluid.

3. Method according to claim 2, wherein the communication protocol P1 is a communication protocol of the M-Bus or wM-Bus type.

4. Method according to one of claims 2 and 3, wherein the communication protocol P2 is a communication protocol of the DLMS / COSEM type.

5. A method according to any one of claims 1 to 4, wherein the hash code derived from the consumption data is calculated by applying a hash function to a four-tuple, the four-tuple comprising the serial number of the meter, a cyclic redundancy code calculated from the metering software used to obtain the consumption data, a certificate number certifying that the secondary smart meter (151a, 151b) can be used in the automation management system (100), and the consumption data itself.

6. A method according to any one of claims 1 to 5, wherein the business data according to the protocol P2 is transmitted in encrypted form via the communication network (101) using a symmetric encryption key dedicated to the communication between the gateway (140a, 140b) involved and the data concentrator (120).

7. A method according to any one of claims 1 to 6, wherein the service data according to the protocol P1 are transmitted in encrypted form from the secondary smart meter (151a, 151b) in question to the gateway (140a, 140b) in question using a symmetric encryption key specific to the communication between the secondary smart meter (151a, 151b) and the gateway (140a, 140b) in question.

8. An automation management system (100) configured to collect consumption data, the automation management system (100) comprising an information system (110) and a data concentrator (120), the information system (110) being configured to delegate the collection of data to the data concentrator (120), the automation management system (100) further comprising a communication network (101), the data concentrator (120) collecting consumption data formatted according to a communication protocol P2 from a first type of smart meter, referred to as a primary smart meter (150), via the communication network, the consumption data formatted according to a communication protocol P2, the automation management system (100) further comprising at least one gateway (140a, 140b) connected to the communication network (101), each gateway (140a, 140b) acting as a relay for collecting consumption data formatted according to a communication protocol P1 from a second type of smart meter, referred to as a secondary smart meter (151a, 151b), the automation management system (100) comprising an electronic circuit, the electronic circuit being configured such that: - Each secondary smart meter (151a, 151b) sends its consumption data together with a hash code derived from said consumption data in transaction data formatted according to said communication protocol P1 and signed using a private asymmetric encryption key; - Each gateway (140a, 140b) relays the data signed by the secondary smart meter (151a, 151b) to the data concentrator (120) via the communication network (101), while encapsulating the data in service data formatted according to the communication protocol P2; - the data concentrator (120) relays the service data formatted according to the communication protocol P2 received via the communication network (101) to the information system; And when the service data formatted according to the communication protocol P2 includes service data formatted according to the communication protocol P1, the information system (110): - decrypting said service data formatted according to said communication protocol P1 using the asymmetric public encryption key corresponding to said secondary smart meter (151a, 151b) from which said consumption data should be collected, - generating a reference hash code from said consumption data received in the decrypted business data and from information known to said information system, - comparing the generated reference hash code with said hash code received in the decrypted business data, and validating said consumption data received in the decrypted business data when the generated reference hash code matches said hash code received in the decrypted business data.

Images