PAIRING METHOD IN AN AUTOMATED SMART METER MANAGEMENT SYSTEM

Abstract

To pair an orphaned smart meter (201b) with a relevant information system (110b) designed to remotely manage smart meters in an automated management system comprising a plurality of candidate information systems, the orphaned smart meter (201b) transmits a pairing request to a multi-service gateway (200). This request includes cleartext information indicating the smart meter type. The multi-service gateway (200) locates, among the candidate information systems, those (110b, 110d) that remotely manage smart meters of the same type as that indicated in the pairing request and relays the pairing request accordingly. The relevant information system then transmits a positive acknowledgment in response, including cleartext information for the multi-service gateway (200) and encrypted information for the orphaned smart meter (201b). Figure to be published with the abbreviation: Fig. 4

Description

Title of the invention: PAIRING METHOD IN A MANAGEMENT SYSTEM AUTOMATED SMART METERS technical field

[0001] At least one embodiment relates to a pairing method in an automated management system for smart meters, such as electricity consumption meters, water consumption meters, gas consumption meters, etc. STATE OF PRIOR ART

[0002] It is known that smart meters, such as energy meters (electricity meters, heat meters, etc.) or fluid meters (fluid consumption meters: water, gas, etc.), include communication interfaces that allow an automated management system to remotely collect consumption data. Consumption data can thus be transmitted, at regular intervals or on demand, to an Information System (IS) for centralized processing.

[0003] Different IS systems can share the same network infrastructure, and each subscriber can purchase subscriptions from different distributors (suppliers) who can manage smart meters of the same type (e.g., smart water meters) or of different types (e.g., smart water meters and smart gas meters). However, once a subscription is purchased, it can be cumbersome to pair the smart meter in question with the correct IS system capable of managing it, based on the subscription purchased.

[0004] It is therefore desirable to provide a solution that allows smart meters to be paired efficiently and securely with their relevant IS (Information Systems). It is therefore desirable to provide a solution that allows smart meters in a building or residential complex to be paired with their relevant IS while limiting deployment costs (and resources). Description of the invention

[0005] To this end, he proposed a pairing method to pair a smart meter, referred to as an orphan smart meter, with an information system, referred to as the relevant information system, which is intended to remotely manage a subset of smart meters that are registered with said relevant information system, the pairing process being executed by a multi-service gateway in an automated management system comprising a plurality of candidate information systems sharing the same network infrastructure to remotely manage their respective subsets of smart meters, the process comprising:

[0006] - receive a pairing request from the orphaned smart meter, which includes smart meter type information, in plain text, and smart meter identifier information which is in encrypted form using a first symmetric key K_DSO known to the orphaned smart meter and the relevant information system;

[0007] - to find, among the candidate information systems, those that remotely manage smart meters of the same type as that indicated in the pairing request;

[0008] - send, using a secure protocol via the network infrastructure, to the systems information candidates found, a relayed pairing request which includes said smart meter identifier information in encrypted form as presented in the pairing request received;

[0009] - receive, via the secure protocol through the network infrastructure, in response to the relayed pairing request, a positive acknowledgment including information of identifier of the relevant information system in encrypted form thanks to said first symmetric key K_DSO, a second symmetric key K_WM specific to the orphan smart meter in clear and the same second symmetric key K_WM in encrypted form thanks to a third symmetric key MK_DSO known to the orphan smart meter and the relevant information system;

[0010] - transmit a pairing acceptance message to the orphaned smart meter, which includes the relevant information system identifier information in encrypted form and the second symmetric key K_WM in encrypted form, as presented in the received positive acknowledgment; and

[0011] - act as an intermediary between the orphaned smart meter then paired and the relevant information system during subsequent exchanges, using the symmetric key K_WM to communicate with the orphaned smart meter then paired.

[0012] Thus, thanks to the smart meter type information in the pairing request, the multi-service gateway is able to determine which information systems to solicit from among the candidate information systems. Since the smart meter identifier is encrypted in the pairing request, this information is protected, and an information system (or any other device) that does not have the appropriate K_DSO symmetric key will not be able to decrypt it. The same applies to the identifier information of the relevant information system when it is returned by said relevant information system. The K_WM symmetric key, The key used later between the multi-service gateway and the orphaned smart meter is protected by a secure protocol for communication to the multi-service gateway and by the appropriate K_DSO symmetric key for communication to the orphaned smart meter. This K_WM symmetric key cannot be captured by a third-party device. Pairing is thus performed efficiently and securely.

[0013] In a particular embodiment, the pairing process comprises:

[0014] - receive, in response to the pairing acceptance message, a message from Pairing confirmation, encrypted using the second symmetric key K_WM, which includes the identifier information of the relevant information system.

[0015] Thus, when the pairing is confirmed by the orphan smart meter, the identifier information of the relevant information system, which has been protected by the appropriate symmetric key K_DSO from the relevant information system to the orphan smart meter, is communicated securely, thanks to the symmetric key K_WM now known to the multi-service gateway and the orphan smart meter, to the multi-service gateway.

[0016] Another pairing method (corresponding to the pairing method described above) is also proposed here for pairing a smart meter, referred to as an orphan smart meter, with an information system, referred to as the relevant information system, which is intended to remotely manage a subset of smart meters registered with said relevant information system. The pairing method is performed by the orphan smart meter in an automated management system comprising a plurality of candidate information systems sharing the same network infrastructure to remotely manage their respective subsets of smart meters. The method comprises:

[0017] - transmit, to a multi-service gateway intended to act as a relay between the orphan smart meter and the relevant information system, a pairing request which includes smart meter type information, in clear text, and smart meter identifier information which is in encrypted form using a first symmetric key K_DSO known to the orphan smart meter and the relevant information system;

[0018] - receive, from the multi-service gateway, a pairing acceptance message, which includes the identifier information of the relevant information system in encrypted form using the first symmetric key K_DSO, as well as a second symmetric key K_WM in encrypted form using a third symmetric key MK_DSO known to the orphaned smart meter and the relevant information system; and

[0019] - use the multi-service gateway as an intermediary between the meter intelligent orphan then paired and the relevant information system during subsequent exchanges, using the symmetric key K_WM to communicate with the multi-service gateway and the first symmetric key K_DSO to communicate with the relevant information system.

[0020] In a particular embodiment, this other pairing method comprises:

[0021] - transmitting, in response to the pairing acceptance message, a message of Pairing confirmation, encrypted using the second symmetric key K_WM, which includes the identifier information of the relevant information system.

[0022] In a particular embodiment, the pairing methods described above in any of their embodiments are such that the smart meter type is among a predefined set of candidate smart meter types including: electricity meter, water meter, and gas meter.

[0023] Thus, the pairing methods described above in any of their embodiments are easily applicable to various types of consumption metering by benefiting from the same network infrastructure for their automated remote management.

[0024] Also proposed here is a computer program product comprising instructions for executing either of the pairing methods described above in any of their embodiments, when the instructions are executed by a processor. Also proposed here is an information storage medium storing instructions for executing either of the pairing methods described above, when the instructions are read from the information storage medium and executed by a processor.

[0025] Also proposed herein is a multi-service gateway configured to pair a smart meter, referred to as an orphan smart meter, with an information system, referred to as the relevant information system, which is intended to remotely manage a subset of smart meters registered with said relevant information system. The multi-service gateway is intended for use in an automated management system comprising a plurality of candidate information systems sharing the same network infrastructure to remotely manage their respective subsets of smart meters. The multi-service gateway comprises electronic circuitry configured to:

[0026] - receive a pairing request from the orphaned smart meter, which includes smart meter type information, in plain text, and smart meter identifier information which is in encrypted form using a first symmetric key K_DSO known to the orphaned smart meter and the relevant information system;

[0027] - to find, among the candidate information systems, those which remotely manage smart meters of the same type as that indicated in the pairing request;

[0028] - send, using a secure protocol via the network infrastructure, to the systems information candidates found, a relayed pairing request which includes said smart meter identifier information in encrypted form as presented in the pairing request received;

[0029] - receive, via the secure protocol through the network infrastructure, in response to the relayed pairing request, a positive acknowledgment including information of identifier of the relevant information system in encrypted form thanks to said first symmetric key K_DSO, a second symmetric key K_WM specific to the orphan smart meter in clear and the same second symmetric key K_WM in encrypted form thanks to a third symmetric key MK_DSO known to the orphan smart meter and the relevant information system;

[0030] - transmit a pairing acceptance message to the orphaned smart meter, which includes the relevant information system identifier information in encrypted form and the second symmetric key K_WM in encrypted form, as presented in the received positive acknowledgment; and

[0031] - act as an intermediary between the orphaned smart meter then paired and the relevant information system during subsequent exchanges, using the symmetric key K_WM to communicate with the orphaned smart meter then paired.

[0032] Also proposed here is a smart meter configured to pair said smart meter, referred to as the orphan smart meter, with an information system, referred to as the relevant information system, which is intended to remotely manage a subset of smart meters registered with said relevant information system, the orphan smart meter being intended for use in an automated management system comprising a plurality of candidate information systems sharing the same network infrastructure to remotely manage their respective subsets of smart meters, the orphan smart meter comprising electronic circuitry configured to:

[0033] - transmit, to a multi-service gateway intended to act as a relay between the orphan smart meter and the relevant information system, a pairing request which includes smart meter type information, in clear text, and smart meter identifier information which is in encrypted form using a first symmetric key K_DSO known to the orphan smart meter and the relevant information system;

[0034] - receive, from the multi-service gateway, a pairing acceptance message, which includes the identifier information of the relevant information system under encrypted using the first symmetric key K_DSO, and a second symmetric key K_WM encrypted using a third symmetric key MK_DSO known to the orphaned smart meter and the relevant information system; and

[0035] - use the multi-service gateway as an intermediary between the meter intelligent orphan then paired and the relevant information system during subsequent exchanges, using the symmetric key K_WM to communicate with the multi-service gateway and the first symmetric key K_DSO to communicate with the relevant information system.

[0036] Also proposed here is a multi-service system comprising a multi-service gateway, as described above, and a plurality of smart meters, as described above, distributed into subgroups which each correspond to installations of the same subscriber. Brief description of the drawings

[0037] The features of the invention mentioned above, as well as others, will become clearer upon reading the following description of at least one exemplary embodiment, said description being made in relation to the accompanying drawings, among which:

[0038] [Fig-1] schematically illustrates an automated meter management system intelligent in which the present invention can be implemented;

[0039] [Fig.2] schematically illustrates an arrangement of a grouping system of smart meters of the automated smart meter management system;

[0040] [Fig.3] schematically illustrates an example of a device hardware architecture of the automated management system; and

[0041] [Fig.4] schematically illustrates exchanges occurring in the management system automated to perform pairing between a smart meter and a corresponding information system, to allow the information system in question to collect consumption data from the smart meter in question.

[0042] DETAILED DESCRIPTION OF EMBODIMENT METHODS

[0043] Figure 1 schematically illustrates an automated management system 100 in which the present invention can be implemented. The automated management system 100 is configured to collect consumption data from measurements taken by a set of smart meters.

[0044] The consumption data collected are processed by several IS (“Information System” in English) which share the same NET 101 network infrastructure in order to remotely manage respective smart meter subsets.

[0045] In general, the automated management system 100 comprises a quantity N of IS information systems. By way of illustration, [Fig. 1] presents four IS information systems.

[0046] Each IS information system is a centralized management equipment dedicated to a said subset of smart meters of the automated management system 100, which are registered with the IS information system in question, according to subscriptions taken out by respective users (called "subscribers") with a distributor for which said IS information system operates.For example, a first information system IS_ 1 110a is dedicated to processing consumption data from smart electricity meters on behalf of an electricity distributor A, a second information system IS2 110b is dedicated to processing consumption data from smart water meters on behalf of a first water distributor B, a third information system IS3 110c is dedicated to processing consumption data from smart gas meters on behalf of a gas distributor C, and a fourth information system IS4 1 lOd is dedicated to processing consumption data from smart water meters on behalf of a second water distributor D.

[0047] For example, each IS information system comprises various components, including a Head-End System (HES), a Meter Data Management System (MDMS), and a Key Management System (KMS). The HES is configured to manage transmissions for the purpose of collecting consumption data. The MDMS is configured to process the collected consumption data. The KMS is configured to store encryption keys required by the MDMS and the smart meters that depend on the IS information system, as well as any intermediate equipment between the IS information system and the smart meters.Information system (IS) components communicate, for example, using the Internet, or more generally an IP-type network (Internet Protocol), or potentially using a Virtual Private Network (VPN).

[0048] The automated management system 100 allows for the management of installations, such as buildings or residential complexes, where different smart meters are co-located. These are referred to as MU-SYS 150 multi-service systems ("Multi-Utility System" in English). The smart meters in these MU-SYS 150 multi-service systems can be of different types (i.e., are suitable for metering separate energy or fluid consumption) The smart meters of these MU-SYS 150 multi-service systems can be smart meters of the same type but for the account of different distributors (e.g., smart water meters for the account of the first water distributor B mentioned above and other smart water meters for the account of the second water distributor D mentioned above).

[0049] Fig. 2 schematically illustrates an arrangement of the MU-SYS 150 multi-service system. The MU-SYS 150 multi-service system is a system for grouping smart meters of the automated management system 100, typically within a building or residential complex.

[0050] The MU-SYS 150 multi-service system includes a MU-GW 200 multi-service gateway to manage this grouping of smart meters, and thus to serve as an intermediary between the IS_1 110a, IS_2 110b, IS_3 110c and IS_4 1 lOd information systems, on the one hand, and the smart meters of the grouping, on the other hand.

[0051] By way of illustration, the MU-SYS 150 multi-service system includes, as shown in [Fig. 2], a grouping of eight smart meters. These eight smart meters are in practice divided into three subgroups 250a, 250b, 250c, each corresponding to installations (e.g., premises) of the same subscriber. This division into subgroups 250a, 250b, 250c is not necessarily known, nor useful, from the point of view of the MU-GW 200 multi-service gateway, nor of the automated management system 100 more generally.

[0052] Thus, for example, the first subgroup 250a comprises a smart electricity meter SM1_1 201a for the first subscriber, a smart water meter SM2_1 201b for the first subscriber, and a smart gas meter SM3_1 201c for the first subscriber. The second subgroup 250b comprises a smart electricity meter SM1_2 202a for the second subscriber, a smart water meter SM2_2 202b for the second subscriber, and a smart gas meter SM3_2 202c for the second subscriber. Finally, the third subgroup 250c comprises a smart electricity meter SM3_2 203a for the third subscriber and a smart water meter SM2_3 203b for the third subscriber (no gas meter for this third subscriber).

[0053] The presence of the MU-GW 200 multi-service gateway allows the smart meters of the group to be equipped with short-range communication means rather than having to equip them with long-range communication means to communicate with the IS_1 110a, IS_2 110b, IS_3 110c and IS_4 110d information systems. The MU-GW 200 multi-service gateway thus reduces the complexity and manufacturing cost of the smart meters, since the Short-range communication technologies are typically less complex and expensive than long-range ones.

[0054] Thus, the smart meters in the group are equipped with a 210 short-range communication interface. For example, the 210 short-range communication interface is suitable for establishing a communication link conforming to the M-Bus (Meter Bus) remote meter reading specifications, as defined in standard EN 13757-2, or to the wM-Bus (Wireless M-Bus) specifications, as defined in standard EN 13757-4, with the MU-GW 200 multi-service gateway (which also has such a 210 short-range communication interface). Other short-range communication technologies can be used, such as Wi-Fi, Bluetooth, Zigbee, KNX, KNX-RF...

[0055] In addition, the MU-GW 200 multi-service gateway also has a 220 long-range communication interface for communicating with IS_1 110a, IS_2 110b, IS_3 110c and IS_4 110d information systems through the NET 101 communication network.

[0056] For example, the NET 101 communication network is a 5G (5th Generation) type wireless communication network. According to other examples, the NET 101 communication network is a GPRS (General Packet Radio Service), UMTS (Universal Mobile Telecommunications System), LTE-MTC (Long-Term Evolution Machine Type Communication) also known by the abbreviation LTE-M, or NB-IoT (NarrowBand Internet of Things) type wireless communication network.

[0057] Figure 3 schematically illustrates an example of a hardware architecture 300, which is suitable for implementing any device controller of the automated management system 100. The example hardware architecture is thus suitable for implementing an information system controller (IS), or any component of the information system (IS). The example hardware architecture is also suitable for implementing a smart meter controller. The example hardware architecture is also suitable for implementing a MU-GW multi-service gateway controller 200.

[0058] The hardware architecture 300 then comprises, connected by a communication bus 310: a processor or CPU (Central Processing Unit) 301; a RAM (Random Access Memory) 302; a ROM (Read Only Memory) 303, or EEPROM (Electrically Erasable Programmable ROM), or Flash memory; a DSM (Data Storage Medium) 304, such as a HDD (Hard Disk Drive), or a storage medium reader, such as an SD (Secure Digital) card reader; and at least a COM 305 communication interface. Depending on the device considered, the hardware architecture 300 may also include I / O 306 inputs / outputs, for example to perform consumption measurements.

[0059] The processor 301 is capable of executing instructions loaded into RAM 302 from ROM 303, external memory (not shown), a storage medium such as an SD card, or a communication network. When the hardware architecture 300 is powered on, the processor 301 is capable of reading instructions from RAM 302 and executing them. These instructions form a computer program causing the processor 301 to implement the steps and algorithms described herein in relation to the device or equipment concerned.

[0060] All or part of the steps and algorithms described herein can thus be implemented in software form by executing a set of instructions by a programmable machine, such as a DSP (Digital Signal Processor) or a microcontroller, or be implemented in hardware form by a machine or component (chip) or a set of components (chipset), such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Generally, each device or piece of equipment in the automated management system 100 comprises electronic circuitry arranged and configured to implement the steps and algorithms described herein in relation to the device or piece of equipment in question.

[0061] Fig. 4 schematically illustrates the exchanges taking place in the automated management system 100 to pair a smart meter, called an orphan smart meter (i.e., one that is not yet paired with an IS of the) with the IS of the distributor with whom the subscription of said smart meter was taken out, called the relevant information system.

[0062] Let us consider, for example, that the pairing relates to the SM2_1 201b smart water meter (orphan smart meter).

[0063] In a 401 step, the SM2_1 201b smart water meter triggers a pairing request, which results in the SM2_1 201b smart water meter issuing a pairing request to the MU-GW 200 multi-service gateway.

[0064] It is important to note that the SM2_1 201b smart water meter does not know the IS information system to which said SM2_1 201b smart water meter is to be connected.

[0065] In a particular embodiment, the SM2_1 201b smart water meter has a button, for example on the front panel, which must be pressed (e.g., a long press for more than 2 seconds) to initiate a pairing request. Alternatively, the pairing request can be initiated by selecting an item from a drop-down menu in the meter's human-machine interface. intelligent water SM2_1 201b. The pairing request can also alternatively be triggered by receiving an external message or instruction, for example from the MU-GW 200 multi-service gateway.

[0066] The pairing request is a message that includes:

[0067] - a message type information (in plain text), which identifies that the message is a pairing request;

[0068] - smart meter type information (in plain text), which identifies which The consumption metering type is the smart meter which transmits the pairing request among a predefined set of several candidate types of smart meter;

[0069] - smart meter identifier information, in encrypted form, which identifies the smart meter in question, this identifier being known to the IS information system on which the smart meter in question depends (here the SM2_1 201b smart water meter).

[0070] Smart meter identifier information is, for example, a serial number of the smart meter in question or information derived from said serial number.

[0071] The smart meter identifier information is preferentially encrypted thanks to a symmetric key K_DSO, which is specific to the IS information system on which the smart meter in question depends and which is known to the smart meter in question.

[0072] The symmetric key K_DSO is, for example, configured in the memory of the smart meter in question during the installation of the smart meter in question and the subscription taken out with the relevant distributor. Subsequently, the symmetric key K_DSO specific to an IS_iV information system (with N = 1,..,4 in [Fig. 1]) is called K_DSO[ TV].

[0073] In a particular embodiment, the smart meter in question has another symmetric key, MK_DSO, specific to the IS information system on which the smart meter in question depends. This symmetric key, MK_DSO, is called the master key and is used to encrypt other keys. Hereafter, the master key MK_DSO specific to an ISUV information system (with N = 1, ..., 4 in [Fig. 1]) is referred to as MK_DSO[TV].

[0074] Unlike the smart meter identifier information, which is present in encrypted form in the pairing request, the smart meter type information is present in plain text. The smart meter type information can therefore be captured and used by the MU-GW 200 multi-service gateway.

[0075] In the case of the SM2_1 201b smart water meter, the smart meter type is "water meter". And the predefined set of candidate types of Examples of smart meters include electricity meters, water meters, and gas meters. The predefined set of candidate smart meter types can also include heat meters. Two bits are sufficient to encode the predefined set of candidate smart meter types. A different number of bits can be specified, depending on the number of candidate smart meter types to be allowed in the automated management system.

[0076] In step 402, the MU-GW 200 multi-service gateway receives the pairing request transmitted by the SM2_1 201b smart water meter in step 401. The MU-GW 200 multi-service gateway has several candidate information systems for pairing, namely IS_1 110a, IS_2 110b, IS_3 110c, and IS_4 110d. To reduce the search for the IS systems to be contacted, the MU-GW 200 multi-service gateway reads the smart meter type information included in the pairing request. The MU-GW 200 multi-service gateway then identifies which IS systems are designed to manage smart meters of the type indicated in the pairing request.

[0077] Prior to the on-site installation of the MU-GW 200 multi-service gateway, information relating to IS information systems (e.g., electricity distribution, water distribution and gas distribution) to which the meters at the subscribers behind the MU-GW 200 multi-service gateway are likely to be paired is programmed into said MU-GW 200 multi-service gateway (at the factory, at the installer's or on-site, typically).

[0078] The MU-GW 200 multi-service gateway then transmits a relayed pairing request to each of these IS systems, which have been found to manage smart meters of the type indicated in the pairing request (e.g., smart water meters). This relayed pairing request includes, at a minimum, the smart meter identifier information as presented in the pairing request transmitted by the SM2_1 201b smart water meter (i.e., in encrypted form).

[0079] Note that at this stage the exchanges between the SM2_1 201b smart water meter and the MU-GW 200 multi-service gateway are not encrypted. As explained later, the exchanges between each smart meter of the MU-SYS 150 multi-service system and the MU-GW 200 multi-service gateway can subsequently, in a particular embodiment, be encrypted using a symmetric key K_WM, specific to the smart meter in question. Thereafter, the symmetric key K_WM specific to an SM AL smart meter (with X = 1,..,3 and Y = 1,..,3 in [Fig. 2]) is referred to as K_WM[X_L].

[0080] The exchanges between the MU-GW 200 multi-service gateway and each of the IS information systems of the automated management system 100 are carried out by means of a secure protocol, so as to ensure at least the confidentiality of the data exchanged, for example through the TLS protocol (“Transport Layer Security”).

[0081] Since the SM2_1 201b smart water meter is of the "water meter" type, the MU-GW 200 multi-service gateway generates a relayed pairing request for the IS_2 110b information system and the IS_4 HOd information system. Alternatively, a point-to-multipoint ("multicast") transmission can be used.

[0082] Let us consider, by way of illustration, that the intelligent water meter SM2_1 201b is assumed to be managed by the information system IS_2 110b (and not by the information system IS_4 HOd).

[0083] Then, in step 403, the IS_4 1 lOd information system decrypts the smart meter identifier information in the relayed pairing request transmitted to it. And after decryption using the symmetric key K_DSO[4], the IS_4 1 lOd information system does not recognize the smart meter identifier information as corresponding to a smart meter identifier that should be associated with it. Indeed, each IS information system of the automated management system 100 holds a list of all the smart meter identifiers that said IS information system is supposed to manage (i.e., according to the subscriptions taken out with the distributor concerned). So, the IS_4 1 lOd information system does not send a response to the MU-GW 200 multi-service gateway or sends a negative acknowledgment to the relayed peering request that was transmitted to it by the MU-GW 200 multi-service gateway.

[0084] In step 404, the IS_2 110b information system decrypts the smart meter identifier information in the relayed pairing request transmitted to it. After decryption using the symmetric key K_DSO[2], the IS_2 110b information system recognizes the smart meter identifier information as corresponding to a smart meter identifier that should be associated with it (i.e., a subscription with the relevant distributor). The IS_2 110b information system then responds to the MU-GW 200 multi-service gateway with a positive acknowledgment of the relayed pairing request transmitted to it by the MU-GW 200 multi-service gateway.

[0085] Positive acknowledgment is a message that includes:

[0086] - a message type information (in plain text), which identifies that the message is a positive acquittal to a pairing request;

[0087] - an IS_2 110b information system identifier (i.e., the identifier of the IS information system which supports the smart meter for which pairing has been requested), in encrypted form using the symmetric key K_DSO[2];

[0088] - the symmetric key K_WM[2J], specific to the SM2_1 smart water meter 201b, in plain language; and

[0089] - the same symmetric key K_WM[2J], encrypted using the master key MK_DSO[2],

[0090] Other information, intended for the smart water meter 201b, can be included in encrypted form using the symmetric key K_DSO[2] in the positive acknowledgment, such as configuration information to be applied by the smart water meter 201b.

[0091] Like the rest of the exchanges between the MU-GW 200 multi-service gateway and the IS_2 110b information system, the positive acknowledgment is transmitted using a secure protocol, for example using the TLS protocol.

[0092] In a step 405, the MU-GW 200 multi-service gateway reads and stores the symmetric key K_WM[2J] provided in plain text (beyond encryption, for example through the TLS protocol, applied in the exchanges between the MU-GW 200 multi-service gateway and the IS_2 110b information system) in the positive acknowledgment transmitted by the IS_2 110b information system.

[0093] Next, the MU-GW 200 multi-service gateway generates a pairing acceptance message to the SM2_1 201b smart water meter including the IS_2 110b information system identifier information, encrypted using the symmetric key K_DSO[2], and the symmetric key K_WM[2J], encrypted using the master key MK_DSO[2] (i.e., as presented in the positive acknowledgment message transmitted by the IS_2 110b information system).

[0094] Once the pairing acceptance message is received, in step 406, the SM2_1 201b smart water meter can decrypt the symmetric key K_WM[2J] using the master key MK_DSO[2], which allows subsequent encryption of communications between the SM2_1 201b smart water meter and the MU-GW 200 multiservice gateway. The SM2_1 201b smart water meter can also decrypt the identifier information of the IS_2 110b information system using the symmetric key K_DSO[2]. The SM2_1 201b smart water meter is then paired with the IS_2 110b information system.

[0095] Then, the SM2_1 201b smart water meter transmits to the MU-GW 200 multiservice gateway a pairing confirmation message, encrypted using the symmetric key K_WM[2J], in which the SM2_1 201b smart water meter transmits the IS_2 110b information system identifier information.

[0096] Then, in step 407, the MU-GW 200 multi-service gateway stores the IS_2 110b information system identifier information in association with a descriptor associated with the SM2_1 201b smart water meter, thus noting that The SM2_1 201b smart water meter is linked and paired with the IS_2 110b information system.

[0097] Subsequently, each time a message originates from the SM2_1 201b smart water meter, the MU-GW 200 multi-service gateway knows which IS information system to address. The MU-GW 200 multi-service gateway then acts as an intermediary between the SM2_1 201b smart water meter (the orphaned smart meter, which is then paired) and the IS_2 110b information system (the relevant information system) during subsequent exchanges to allow, among other operations, the IS_2 110b information system to collect consumption data established by the SM2_1 201b smart water meter.

[0098] The information exchanged between the SM2_1 201b smart water meter and the IS_2 110b information system (e.g., meter reading) is end-to-end encrypted with the K_DSO key[2]. The exchanges between the SM2_1 201b smart water meter and the IS_2 110b information system can, for example, be based on the DLMS / COSEM protocol ("Device Language Message Specification" / "Companion Specification for Energy Metering") or LwM2M ("Lightweight Machine to Machine").

[0099] The MU-GW 200 multi-service gateway therefore does not have access to this information exchanged between the SM2_1 201b smart water meter and the IS_2 110b information system. And the messages exchanged between the MU-GW 200 multi-service gateway and the SM2_1 201b smart water meter are encrypted with the symmetric key K_WM[2J], in order to ensure the protection of their contents.

Claims

1. Demands A pairing method for pairing a smart meter, referred to as an orphan smart meter (201b), with an information system, referred to as the relevant information system (110b), which is intended to remotely manage a subset of smart meters registered with said relevant information system, the pairing method being executed by a multi-service gateway (200) in an automated management system (100) comprising a plurality of candidate information systems (110a, 110b, 110c, HOd) sharing the same network infrastructure (101) to remotely manage their respective subsets of smart meters (201a, 201b, 201c, 202a, 202b, 202c, 203a, 203b), the method comprising: - receiving a pairing request from the orphan smart meter, which includes smart meter type information, in plain text,and smart meter identifier information that is in encrypted form using a first symmetric key K_DSO known to the orphaned smart meter (201b) and the relevant information system (110b); - find, among the candidate information systems (110a, 110b, 110c, 1 lOd), those which remotely manage smart meters of the same type as that indicated in the pairing request; - send, via a secure protocol through the network infrastructure (101), to the candidate information systems found (110b, HOd), a relayed pairing request which includes said smart meter identifier information in encrypted form as presented in the received pairing request; - receive, via the secure protocol via the network infrastructure (101), in response to the relayed pairing request, a positive acknowledgment including an identifier of the relevant information system in encrypted form thanks to said first symmetric key K_DSO, a second symmetric key K_WM specific to the orphan smart meter (201b) in plain text and the same second symmetric key K_WM in encrypted form thanks to a third symmetric key MK_DSO known to the orphan smart meter (210b) and the relevant information system (HOb); - transmit to the orphan smart meter (201b) a pairing acceptance message, which includes the identifier information of the relevant information system (110b) in encrypted form and the second symmetric key K_WM in encrypted form, as presented in the received positive acknowledgment; and - act as an intermediary between the then-paired orphan smart meter (201b) and the relevant information system (110b) in subsequent exchanges, using the symmetric key K_WM to communicate with the then-paired orphan smart meter (201b).

2. Pairing method according to claim 1, comprising: - receiving, in response to the pairing acceptance message, a pairing confirmation message, encrypted using the second symmetric key K_WM, which includes the identifier information of the relevant information system.

3. A pairing method for pairing a smart meter, referred to as an orphan smart meter (201b), with an information system, referred to as the relevant information system (110b), which is intended to remotely manage a subset of smart meters registered with said relevant information system (110b), the pairing method being performed by the orphan smart meter (201b) in an automated management system (100) comprising a plurality of candidate information systems (110a, 110b, 110c, 110d) sharing the same network infrastructure (101) to remotely manage respective subsets of smart meters (201a, 201b, 201c, 202a, 202b, 202c, 203a, 203b), the method comprising: - transmitting, to a multi-service gateway (200) intended to act as relay between the orphaned smart meter (201b) and the relevant information system (110b),a pairing request that includes smart meter type information in plain text and smart meter identifier information in encrypted form using a first symmetric key K_DSO known to the orphaned smart meter (201b) and the relevant information system (110b); - receive, from the multi-service gateway (200), a pairing acceptance message, which includes the identifier information of the relevant information system in encrypted form using, the first symmetric key K_DSO, as well as a second symmetric key K_WM in encrypted form thanks to a third symmetric key MK_DSO known to the orphan smart meter (201b) and the relevant information system (110b); and - use the multi-service gateway as an intermediary between the then paired orphan smart meter and the relevant information system in subsequent exchanges, using the symmetric key K_WM to communicate with the multi-service gateway and the first symmetric key K_DSO to communicate with the relevant information system (110b).

4. Pairing method according to claim 3, comprising: - transmitting, in response to the pairing acceptance message, a pairing confirmation message, encrypted using the second symmetric key K_WM, which includes the identifier information of the relevant information system.

5. A pairing method according to any one of claims 1 to 4, wherein the smart meter type is among a predefined set of candidate smart meter types including: electricity meter, water meter, and gas meter.

6. Product computer program comprising instructions to perform the pairing process according to claim 1 or 2, or the pairing process according to claim 3 or 4, when the instructions are executed by a processor (301).

7. Information storage medium storing instructions to perform the pairing process according to claim 1 or 2, or the pairing process according to claim 3 or 4, when the instructions are read from the information storage medium and executed by a processor (301).

8. A multi-service gateway (200) configured to pair a smart meter, referred to as an orphan smart meter (201b), with an information system, referred to as the relevant information system (110b), which is intended to remotely manage a subset of smart meters that are registered with said relevant information system (110b), the multi-service gateway (200) being intended to be used in an automated management system (100) comprising a plurality of candidate information systems (110a, 110b, 110c, 110d) sharing the same network infrastructure (101) to remotely manage respective subsets of smart meters (201a, 201b, 201c, 202a, 202b, 202c, 203a, 203b), the multi-service gateway (200) comprising electronic circuitry configured for: - receive a pairing request from the orphan smart meter (201b), which includes smart meter type information, in plain text, and smart meter identifier information which is in encrypted form using a first symmetric key K_DSO known to the orphan smart meter (201b) and the relevant information system (110b); - find, among the candidate information systems (110a, 110b, 110c, 1 lOd), those which remotely manage smart meters of the same type as that indicated in the pairing request; - send, via a secure protocol through the network infrastructure (101), to the candidate information systems found (110b, HOd), a relayed pairing request which includes said smart meter identifier information in encrypted form as presented in the received pairing request; - receive, through the secure protocol via the network infrastructure (101), in response to the relayed pairing request, a positive acknowledgment including an identifier of the relevant information system in encrypted form thanks to said first symmetric key K_DSO, a second symmetric key K_WM specific to the orphan smart meter (201b) in plain text and the same second symmetric key K_WM in encrypted form thanks to a third symmetric key MK_DSO known to the orphan smart meter (201b) and the relevant information system (HOb); - transmit to the orphaned smart meter (201b) a pairing acceptance message, which includes the identifier information of the relevant information system in encrypted form and the second symmetric key K_WM in encrypted form, as presented in the received positive acknowledgment; and - act as an intermediary between the orphan smart meter (201b) then paired and the relevant information system (110b) during subsequent exchanges, using the symmetric key K_WM to communicate with the orphan smart meter (201b) then paired.

9. Smart meter configured to pair said smart meter, referred to as orphan smart meter (201b), with an information system, referred to as relevant information system (110b), which is intended to remotely manage a subset of smart meters that are registered with said relevant information system (110b), the orphan smart meter (201b) being intended for use in an automated management system (100) comprising a plurality of candidate information systems (110a, 110b, 110c, 110d) sharing the same network infrastructure (101) to remotely manage respective subsets of smart meters (201a, 201b, 201c, 202a, 202b, 202c, 203a, 203b), the orphan smart meter (201b) comprising electronic circuitry configured to: - transmit,to a multi-service gateway (200) intended to act as a relay between the orphan smart meter (201b) and the relevant information system (110b), a pairing request which includes smart meter type information, in plain text, and smart meter identifier information which is in encrypted form using a first symmetric key K_DSO known to the orphan smart meter (201b) and the relevant information system (110b); - receive, from the multi-service gateway (200), a pairing acceptance message, which includes the identifier information of the relevant information system in encrypted form using the first symmetric key K_DSO,as well as a second symmetric key K_WM in encrypted form using a third symmetric key MK_DSO known to the orphaned smart meter (201b) and the relevant information system (110b); and - use the multi-service gateway (200) as an intermediary between the orphaned smart meter (201b), then paired, and the relevant information system (110b) during subsequent exchanges, using the symmetric key K_WM to communicate with the multi-service gateway (200) and the first symmetric key K_DSO to communicate with the relevant information system (110b).

10. Multi-service system (150) comprising a multi-service gateway (200) according to claim 8 and a plurality of smart meters (201a, 201b, 201c, 202a, 202b, 202c, 203a, 203b) according to claim 9 divided into subgroups (250a, 250b, 250c) which each correspond to installations of the same subscriber.

Images