Method for Secure Pairing between Onboard and Remote Sensors and a Concentrator

Abstract

One aspect of the present invention relates to a method for secure pairing between a sensor and a concentrator using a mobile terminal, comprising the steps of: - generating and publishing a confirmation code (103) by the concentrator; - converting the confirmation code into a sequence of optical signals used by at least one electroluminescent diode by the sensor (104); - converting the sequence of optical signals into a sequence code by the mobile terminal; - sending the sequence code to the concentrator (106); - comparing, by the concentrator, the sequence code with the generated confirmation code, and: - generating a warning (108) if the sequence code does not match the generated confirmation code; - pairing and exchanging information between the sensor and the concentrator (109-1) if the sequence code matches the generated confirmation code.

Description

Technical Field

[0001] The technical field of the present invention is a method for pairing between sensors and a concentrator in an airborne environment, and more specifically a method for pairing between a concentrator remote in an airborne environment and sensors, and wherein data from the sensors must have integrity and origin assurance.

[0002] The present invention relates to a method for pairing between an airborne sensor and a concentrator, and more particularly to a method for pairing between an airborne and remote sensor and a concentrator. The present invention also relates to sensors, concentrators, and mobile terminals enabling the implementation of the method for pairing. Background Art

[0003] In order for a concentrator, which serves to collect data from different sensors in a centralized manner, to collect information that must have its origin and integrity guaranteed by a given sensor, a mutual identification phase called pairing is essential.

[0004] When the concentrator and the sensors are mounted on a device such as an aircraft or a vehicle, the sensors are typically located in a highly restrictive environment. In less restrictive environments, the concentrator and the sensors are placed at a certain distance from each other.

[0005] In the case of replacing or installing a sensor, the pairing is performed in the operating environment, i.e., when the sensor and the concentrator are mounted on the device. It is therefore not possible to consider resorting to NFC (Near Field Communication) components because the distance between the sensor and the concentrator (from about one meter to several meters in the operating environment) is too long and cannot be reduced to a few centimeters (since the concentrator cannot be moved). Similarly, due to obstacles between the sensor and the concentrator, it is not possible to use a solution that resorts to transmitting data via a light beam (the IrDA technology for "Infrared Data Association", such as infrared connection for example).

[0006] Figure 1 Pairing in the operating environment is conventionally performed by method 10, wherein the link of the steps is as Figure 1 ​As shown. Method 10 is implemented by an operator located near sensor 202 and is provided with a human-machine interface 204 capable of communicating with concentrator 201 via a communication means such as Wi-Fi, 3G, or 4G. During the first step 11, the operator presses a button to place sensor 202 in pairing mode. During the second step 12, sensor 202 issues a pairing request, and the light-emitting diode 2020 of sensor 202 flashes to indicate that it is in pairing mode. During the third step 13, concentrator 201 receives the pairing request in continuous listening mode, performs pairing, and sends a pairing confirmation to sensor 201. During the fourth step 14, concentrator 201 sends a pairing confirmation notification to the operator via human-machine interface 204. Optionally, the operator provides data about sensor 202 to concentrator 201. Then concentrator 201 and sensor 202 are paired. During the fifth step 15, concentrator 201 and sensor 202 exchange data.

[0007] According to this method, it cannot be guaranteed that the concentrator has been paired with the correct sensor, and conversely, it cannot be guaranteed that, for example, sensor 202 is paired with another concentrator. During the pairing phase of two different devices, this situation may be unintentional. This method is also vulnerable to "man-in-the-middle" type attacks, the consequence of which is that the integrity of the operating devices is no longer guaranteed because the authenticity of the sensors or concentrators is no longer guaranteed. In this international context, a malicious actor, from the perspective of sensor 202, usurps the identity of concentrator 201, and / or from the perspective of concentrator 201, usurps the identity of sensor 202. Once the data exchanged between sensor 202 and concentrator 201 is intercepted and modified by a third party after pairing is performed, it is no longer confidential and loses its integrity.

[0008] Therefore, there is a need for a method for securely pairing on-board and remote sensors with a concentrator in an operating environment. Summary of the Invention

[0009] The present invention provides a solution to the above problems by enabling the pairing of separate on-board sensors and concentrators in an operating environment, thereby ensuring the integrity of the data exchanged.

[0010] A first aspect of the present invention relates to a method for securely pairing between a sensor and a concentrator, the concentrator and the sensor being on-board and remote, the sensor including at least one light-emitting diode, the method being implemented using a mobile terminal configured to communicate with the concentrator via a secure channel and including the following steps:

[0011] - Placing the concentrator in pairing mode and having the concentrator issue a concentrator public key;

[0012] - Place the sensor in pairing mode and have the sensor send a pairing request, which includes pairing information encrypted with the concentrator public key and the sensor public key;

[0013] - Have the concentrator generate an acknowledgment code and send a pairing request acknowledgment that includes the acknowledged pairing information and the generated acknowledgment code, which is encrypted with the sensor public key;

[0014] - Have the sensor convert the received acknowledgment code into an optical signal sequence and have the light-emitting diode execute the optical signal sequence;

[0015] - Have the mobile terminal convert the executed optical signal sequence into an optical signal sequence acknowledgment code;

[0016] - Have the mobile terminal send the optical signal sequence acknowledgment code to the concentrator via a secure channel;

[0017] - Have the concentrator compare the optical signal sequence acknowledgment code with the generated acknowledgment code:

[0018] o Have the concentrator deactivate the acknowledgment code, and:

[0019] · If the optical signal sequence acknowledgment code does not match the generated acknowledgment code, generate a warning via the mobile terminal and have the concentrator delete the pairing information;

[0020] · If the optical signal sequence acknowledgment code matches the generated acknowledgment code, pair the sensor and the concentrator using the pairing information and exchange information between the sensor and the concentrator.

[0021] Due to the present invention, using an acknowledgment code that is first transmitted from the concentrator to the sensor and then from the sensor to the concentrator enables detection of non-compliant pairing operations by comparing with the acknowledgment code stored in the concentrator, regardless of whether the non-compliant pairing operation is caused by fraud or involuntary error, such as, for example, a pairing attempt with an incorrect sensor. Generating a warning enables the operator performing the pairing operation to be notified of the failure of the pairing operation.

[0022] Transmitting the acknowledgment code from the sensor to the concentrator via a mobile terminal that communicates with the concentrator via a secure channel enables protection of the transmission of the acknowledgment code from the mobile terminal to the concentrator, and transmitting the acknowledgment code from the sensor to the mobile terminal using an optical signal sequence enables protection of the transmission of the acknowledgment code from the sensor to the mobile terminal, because in order to obtain or input the optical signal sequence, a malicious person must be near the sensor and thus near the operator. Therefore, a malicious person cannot intercept the acknowledgment code remotely during the transmission of the acknowledgment code from the sensor to the concentrator, and it is also impossible to steal the identity of the sensor or the concentrator by intercepting the acknowledgment code during the transmission of the acknowledgment code from the concentrator to the sensor, because pairing will not occur if no acknowledgment code or if a modified acknowledgment code is sent to the concentrator.

[0023] Encrypting the data exchanged between the sensor and the concentrator before pairing makes it possible to protect the data exchange before pairing.

[0024] In addition to the features just mentioned in the previous paragraph, the method according to the first aspect of the present invention may have one or more of the following additional features, considered individually or in all technically possible combinations thereof.

[0025] According to an embodiment, the mobile terminal communicates with the concentrator via a short-range communication mode.

[0026] Therefore, in order to intercept the communication between the mobile terminal and the concentrator, a malicious person would have to be near both the concentrator and the mobile terminal.

[0027] According to an embodiment compatible with the foregoing embodiment, putting the concentrator into pairing mode is performed by the operator via the mobile terminal.

[0028] Therefore, an operator located near the sensor can put the concentrator into pairing mode at a distance from the concentrator.

[0029] According to an embodiment compatible with the foregoing embodiment, putting the sensor into pairing mode is performed by the operator by pressing a pairing button of the sensor.

[0030] Therefore, an operator located near the sensor can easily put the sensor into pairing mode.

[0031] According to an embodiment compatible with the foregoing embodiment, the pairing request is sent by the sensor in the form of a radio frequency frame in a loop.

[0032] Therefore, the chance for the concentrator to receive the pairing request is maximized relative to a single transmission.

[0033] According to an embodiment compatible with the foregoing embodiment, the pairing request confirmation also includes a shared key, and once the sensor and the concentrator are paired, the information exchanged between the sensor and the concentrator is encrypted with the shared key.

[0034] Therefore, the data exchange between the paired sensor and the concentrator is secure, and the process of defining a key for key exchange after pairing is avoided.

[0035] According to an embodiment compatible with the foregoing embodiment, the confirmation code is randomly generated by the concentrator.

[0036] Therefore, the concentrator does not pre-store a list of available confirmation codes that could be obtained by malicious persons.

[0037] According to an embodiment compatible with the foregoing embodiments, the optical signal sequence emitted by the light-emitting diode includes optical signals of different wavelengths.

[0038] Therefore, each light-emitting diode of the sensor can use a larger number of optical signal sequences.

[0039] According to a first embodiment compatible with the foregoing embodiments, converting the executed optical signal sequence into an optical signal sequence confirmation code includes: inputting the optical signal sequence by an operator via the human-machine interface of the mobile terminal, and converting the input optical signal sequence into an optical signal sequence confirmation code by the mobile terminal.

[0040] Therefore, the mobile terminal can be without a camera and the operator can verify and / or modify the input optical signal sequence.

[0041] According to a second embodiment compatible with the foregoing embodiments, converting the executed optical signal sequence into an optical signal sequence confirmation code includes acquiring the optical signal sequence by the camera of the mobile terminal, and converting the acquired optical signal sequence into an optical signal sequence confirmation code by the mobile terminal.

[0042] Therefore, contrary to the first embodiment, acquiring the optical signal sequence is not affected by human error, but the operator cannot verify and / or modify the acquired optical signal sequence.

[0043] According to an embodiment compatible with the foregoing embodiments, the method of the present invention further includes the step of: sending data input by an operator via the human-machine interface of the mobile terminal to the concentrator via a secure channel; if the optical signal sequence confirmation code does not match the generated confirmation code, the input data is deleted by the concentrator, and if the optical signal sequence confirmation code matches the generated confirmation code, the input data is used for pairing and retained by the concentrator.

[0044] Therefore, if pairing requires data input by the operator, the data is supplied to the concentrator in a secure manner.

[0045] According to an embodiment compatible with the foregoing embodiments, the method of the present invention further includes the step of sending a pairing confirmation from the concentrator to the mobile terminal via a secure channel.

[0046] Therefore, the operator is informed of the success of the pairing operation.

[0047] A second aspect of the present invention relates to a mobile terminal for implementing the method according to the first aspect of the present invention, including a human-machine interface and configured to:

[0048] - Manage data input via the human-machine interface;

[0049] - Exchange data with the concentrator via a secure channel;

[0050] - Convert a series of optical signals executed by the sensor into an optical signal sequence confirmation code;

[0051] - Generate a warning when the optical signal sequence confirmation code does not match the confirmation code generated by the concentrator.

[0052] Therefore, the mobile terminal is configured to implement the steps of the first embodiment of the method of the present invention implemented by or via the mobile terminal.

[0053] According to one embodiment, the mobile terminal includes a camera and is configured to acquire an optical signal sequence via the camera.

[0054] Therefore, the mobile terminal is configured to implement the steps of the first or second embodiment of the method of the present invention implemented by or via the mobile terminal.

[0055] A third aspect of the present invention relates to a sensor for implementing the method according to the first aspect of the present invention, including at least one light emitting diode and configured to:

[0056] - Generate a cryptographic key;

[0057] - Send a pairing request when the sensor is placed in the pairing mode;

[0058] - Receive a pairing request confirmation including a confirmation code from the concentrator;

[0059] - Convert the confirmation code received from the concentrator into an optical signal sequence;

[0060] - Execute the optical signal sequence via the light emitting diode;

[0061] - Once paired with the concentrator, exchange information with the concentrator.

[0062] Therefore, the sensor is configured to implement the steps of the method of the present invention implemented by or via the sensor.

[0063] A fourth aspect of the present invention relates to a concentrator for implementing the method according to the first aspect of the present invention, which is configured to:

[0064] - Generate a cryptographic key;

[0065] - Send a public key when the concentrator is placed in the pairing mode;

[0066] - Generate a confirmation code when receiving a pairing request from the sensor and send a pairing request confirmation including the generated confirmation code;

[0067] - Exchange data with the mobile terminal via a secure channel;

[0068] - Compare the optical signal sequence confirmation code received from the mobile terminal with the generated confirmation code;

[0069] - Delete data in case the optical signal sequence confirmation code does not match the generated confirmation code;

[0070] - Exchange information with the sensor once paired with the sensor.

[0071] Thus, the concentrator is configured to implement the steps of the method of the present invention implemented by or via the concentrator.

[0072] The fifth aspect of the present invention relates to a system for implementing the method according to the first aspect of the present invention, comprising:

[0073] - A mobile terminal according to the second aspect of the present invention;

[0074] - A sensor according to the third aspect of the present invention;

[0075] - A concentrator according to the fourth aspect of the present invention.

[0076] The present invention and its different applications will be better understood when reading the following description and examining the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The drawings are presented for the purpose of providing information and in no way limit the present invention.

[0078] - Figure 1 Shows a link of the steps of a pairing method between a sensor and a concentrator according to the prior art.

[0079] - Figure 2 Shows a link of the steps of a pairing method between a sensor and a concentrator according to the present invention using a mobile terminal.

[0080] - Figure 3 Shows a graphical representation of an aircraft having an on-board sensor and concentrator. DETAILED DESCRIPTION

[0081] Unless otherwise mentioned, the same elements appearing in different drawings have unique reference numerals.

[0082] The present invention has been described with reference to the prior art Figure 1 .

[0083] The first aspect of the present invention relates to a method for secure pairing between an on-board sensor and a concentrator that are remote from each other.

[0084] The term "pairing between two devices" means a mutual recognition phase between two devices, such that once the pairing is performed, data can be exchanged between the two devices in a manner that ensures integrity and origin. Pairing includes, for example, the exchange of cryptographic keys that will be used to encrypt the exchanged data once the pairing is performed, or the exchange of information related to the type of data that will be exchanged once the pairing is performed.

[0085] Thus, in the context of the present invention, if the sensor is a pressure sensor, the concentrator will be notified that the data transmitted by the sensor will be pressure data, rather than, for example, temperature data, and the concentrator can then adjust the data processing accordingly.

[0086] The term "concentrator" means a device configured to collect data from a plurality of other devices, such as sensors, and manage the collected data.

[0087] The concentrator includes a memory that allows it to store data and a processor that allows it to perform calculations.

[0088] The sensor includes at least one light-emitting diode.

[0089] Each light-emitting diode can, for example, emit light signals of different wavelengths. Thus, the light-emitting diode is capable of emitting, for example, green light signals and red light signals.

[0090] The light-emitting diode is capable of emitting, for example, each color in the visible range, such as each color of the rainbow.

[0091] The light-emitting diode is capable of emitting light signals having wavelengths that do not belong to the visible range, such as the infrared range.

[0092] The sensor is, for example, a pressure sensor, a temperature sensor, a light sensor, or an acoustic sensor.

[0093] In the context of the present invention, "the sensor and the concentrator are remote" means that the distance separating the sensor and the concentrator is such that a malicious person can position themselves between the sensor and the concentrator without being seen from the location of the sensor. The distance separating the sensor and the concentrator is, for example, greater than about ten meters.

[0094] Neither the sensor nor the concentrator has a human-machine interface.

[0095] The term "human-machine interface" means an interface that allows two-way interaction between a device equipped with a human-machine interface and an operator. According to this definition, a button is not a human-machine interface because a button does not allow the device equipped with the button to interact with the operator and because a button does not send any information.

[0096] The sensor and the concentrator are mounted on a device, which is, for example, a vehicle, and more specifically an aircraft.

[0097] Figure 3 Figure 3 A graphical representation showing the concentrator 201 and the sensors 202 on board the aircraft 300 is presented.

[0098] In Figure 3 the example shown, the aircraft 300 has a concentrator 201 and a plurality of sensors 202 on board. The concentrator 201 is located inside the aircraft 300, while each sensor 202 is located at the wheel of the landing gear. The sensor 202 is, for example, a pressure sensor, giving the pressure of the wheel on which it is mounted. Then a given sensor 202 is separated from the concentrator 201 by several meters.

[0099] The method of the present invention is implemented using a mobile terminal 203, which acts as a trusted entity communicating with the concentrator 201 via a secure channel 205.

[0100] The term "secure channel" means a channel that allows the transmission of a data stream that is encrypted, authenticated, and has integrity.

[0101] The secure channel 205 uses, for example, a security protocol based on TCP / IP (Transmission Control Protocol / Internet Protocol), such as a VPN (Virtual Private Network) of the SSL (Secure Sockets Layer) or IPSec (Internet Protocol Security) type or an application flow of the HTTPS (Hypertext Transfer Protocol Secure) type.

[0102] The mobile terminal 203 includes a human-machine interface 203 that allows data to be typed and read.

[0103] The mobile terminal 203 is, for example, a smartphone or a tablet. The human-machine interface of the mobile terminal 203 is, for example, a keyboard or a touch screen.

[0104] The mobile terminal 203 may include a camera.

[0105] The mobile terminal 203 and the concentrator 201 communicate via the secure channel 205, for example, by using a short-range secure communication mode, such as, for example, a WIFI, Bluetooth, or LoRa connection.

[0106] Figure 2 Figure 2 A link of the steps of the method 100 of the present invention is shown, which is implemented by the concentrator 201, the sensor 202, or the mobile terminal 203, or by the operator via the concentrator 201, the sensor 202, or the mobile terminal 203.

[0107] During the implementation of the method 100, the operator is located near the sensor 202 and is equipped with the mobile terminal 203.

[0108] ​​​​The first step of method 100 includes a first sub-step 101-1 implemented by the operator, including placing concentrator 201 in pairing mode.

[0109] As Figure 2 shown, getting concentrator 201 into pairing mode can be performed by the operator using mobile terminal 203, for example, by sending an instruction to enter pairing mode to concentrator 201 via secure channel 205.

[0110] The first step of method 100 further includes a second sub-step 101-2 implemented by concentrator 201, including sending the concentrator public key. The concentrator public key is sent out, for example, via radio frequency.

[0111] The term "public key" means a cryptographic key that is used to encrypt data in asymmetric cryptography encryption technology. For a given entity, the public key is paired with a private key that is used to decrypt the data encrypted with the public key. The public key can be transmitted without restriction, while the private key is secret, that is, only the entity knows the private key.

[0112] The concentrator public key is then the public key that concentrator 201 uses to encrypt the data sent before pairing. The concentrator public key is paired with a concentrator private key that is known only to concentrator 201.

[0113] The second step of method 100 includes a first sub-step 102-1 implemented by the operator, including placing sensor 202 in pairing mode.

[0114] As Figure 2 shown, placing sensor 202 in pairing mode can be performed by the operator pressing the pairing button of sensor 202. In this case, sensor 202 is provided with a pairing button 202 that is configured to place sensor 202 in pairing mode after being pressed.

[0115] The second step of method 100 includes a second sub-step 102-2, which includes, for sensor 202, sending a pairing request after receiving the concentrator public key sent in the second sub-step 101-2 of the first step of method 100.

[0116] The pairing request includes the pairing information required for pairing, which is encrypted using the concentrator public key.

[0117] The pairing information includes, for example, the location and name of sensor 202.

[0118] The pairing request further includes a sensor public key.

[0119] The sensor public key is the public key that sensor 202 uses to encrypt the data sent before pairing. The sensor public key is paired with a sensor private key that is known only to sensor 202.

[0120] The pairing request is sent, for example, in a loop and is performed in the form of a radio frequency frame.

[0121] The third step 103 of method 100 is implemented by concentrator 201 when the pairing request sent by sensor 202 is received during the second sub-step 102-2 of the second step of method 100, and the pairing information has been decrypted using the concentrator private key.

[0122] The pairing information is stored in the memory of concentrator 201.

[0123] The third step 103 of method 100 includes generating an acknowledgment code and sending a pairing request acknowledgment. The pairing request acknowledgment is sent, for example, via WIFI, Bluetooth, or LoRa.

[0124] The pairing request acknowledgment includes the pairing information received in the acknowledged pairing request and the generated acknowledgment code.

[0125] The pairing request acknowledgment is encrypted using the sensor public key received in the pairing request.

[0126] The acknowledgment code is, for example, randomly generated, for example, by a random number generator used in a cryptographic function called PRNG (pseudo-random number generator) or from the information received in the pairing request.

[0127] The length of the acknowledgment code depends on the number of light-emitting diodes 2020 of sensor 202 and the characteristics of the light-emitting diodes 2020, such as, for example, the number of wavelengths at which they can emit light signals respectively.

[0128] In Figure 2 sensor 202 includes two light-emitting diodes 2020.

[0129] The fourth step 104 of method 100 is implemented by sensor 202 after receiving the pairing request acknowledgment and thus receiving the acknowledgment code, and the pairing request acknowledgment has been decrypted using the sensor private key.

[0130] The fourth step 104 of method 100 includes converting the received acknowledgment code into a sequence of optical signals and executing the sequence of optical signals via one or more light-emitting diodes 2020 of sensor 202.

[0131] The sequence of optical signals can be dynamic. The term "sequence of optical signals" means an ordered sequence of optical signals that can have different durations and different wavelengths.

[0132] For example, in the case where sensor 202 includes a first light-emitting diode 2020 and a second light-emitting diode 2020, executing the sequence of optical signals includes, for example, lighting the first light-emitting diode 2020 in green for 1 second and then lighting the second light-emitting diode 2020 in red for 2 seconds.

[0133] The optical signal sequence can be static. The term "optical signal sequence" means a visual pattern of optical signals that can have different wavelengths.

[0134] For example, in the case where the sensor 202 includes a first light-emitting diode 2020 and a second light-emitting diode 2020, performing an optical signal sequence includes, for example, simultaneously lighting the first light-emitting diode 2020 in green and the second light-emitting diode 2020 in red for a predetermined duration.

[0135] The fifth step 105 of the method 100 implemented by the mobile terminal 203 includes converting the optical signal sequence executed by the sensor 202 in the fourth step 104 of the method 100 into an optical signal sequence confirmation code.

[0136] According to the first embodiment, the optical signal sequence is manually input by an operator via the human-machine interface of the mobile terminal 203, and the mobile terminal 203 converts the input optical signal sequence into an optical signal sequence confirmation code. In this case, the wavelengths of the light-emitting diodes 2020 executed according to the optical signal sequence must belong to the visible light range.

[0137] According to the second embodiment, the optical signal sequence is acquired via the camera of the mobile terminal 203, and the mobile terminal 203 converts the acquired optical signal sequence into an optical signal sequence confirmation code.

[0138] In both embodiments, the mobile terminal 203 performs the inverse operation of the conversion executed by the sensor 202 in the fourth step 104 of the method 100.

[0139] The sixth step 106 of the method 100 implemented by the mobile terminal 203 includes sending the optical signal sequence confirmation code obtained in the fifth step 105 of the method 100 to the concentrator 201 via the secure channel 205.

[0140] The seventh step 107 of the method 100 implemented by the concentrator 201 includes comparing the optical signal sequence confirmation code received in the sixth step 106 of the method 100 with the confirmation code generated in the third step 103 of the method 100.

[0141] If the optical signal sequence confirmation code does not match the generated confirmation code, i.e., if the optical signal sequence confirmation code is different from the generated confirmation code, the eighth step 108 of the method 100 is executed.

[0142] If the optical signal sequence confirmation code matches the generated confirmation code, i.e., if the optical signal sequence confirmation code is the same as the generated confirmation code, the ninth step of the method 100 is executed.

[0143] The eighth step 108 of method 100 includes the mobile terminal 203 generating a warning and the concentrator 201 deactivating the confirmation code and deleting the pairing information from its memory. Then the operator is notified that the pairing has failed.

[0144] Once the confirmation code is deactivated by the concentrator 201, the confirmation code can no longer be used to pair the concentrator 201 and the sensor 202.

[0145] The ninth step of method 100 includes a first sub-step 109-1, which includes the concentrator 201 deactivating the confirmation code, then the concentrator 201 and the sensor 202 pairing using the pairing information, and then exchanging information.

[0146] The exchanged information is encrypted using, for example, a shared key. The shared key is sent by the concentrator 201 to the sensor 202 in the pairing request confirmation during the third step 103 of method 100, for example.

[0147] The term "shared key" means a cryptographic key that is used by several entities to encrypt and decrypt data in symmetric cryptography encryption techniques.

[0148] The ninth step of method 100 may also include a second sub-step 109-2 implemented by the concentrator 201, including sending a pairing confirmation to the mobile terminal 203 via the secure channel 205. The operator is then notified that the pairing is successful.

[0149] Then method 100 may include a step implemented by the mobile terminal 203, including sending, via the secure channel 205, the data input by the operator via the human-machine interface of the mobile terminal 203 that is required for the pairing of the concentrator 201 and the sensor 202.

[0150] The input data is stored in the memory of the concentrator 201.

[0151] The input data includes, for example, the location of the sensor 202 and / or the identification of the device 300 on which the sensor 202 is mounted.

[0152] In Figure 3 the case of, the input data includes, for example, the location of the sensor 202 in the reference frame of the aircraft 300 and the identification of the aircraft 300.

[0153] Since the input data is required for the pairing of the concentrator 201 and the sensor 202, the input data is used for the pairing of the concentrator 201 and the sensor 202 during the first sub-step 109-1 of the ninth step of method 100, or deleted by the concentrator 201 from its memory during the eighth step 108 of method 100.

Claims

1. A method for secure pairing between a sensor and a concentrator, the concentrator and the sensor being airborne and remote, the sensor including at least one light-emitting diode, characterized in that the method is implemented using a mobile terminal configured to communicate with the concentrator via a secure channel and includes the following steps: - Place the concentrator in pairing mode and have the concentrator issue a concentrator public key; - Place the sensor in pairing mode and have the sensor issue a pairing request, the pairing request including pairing information encrypted with the concentrator public key and a sensor public key; - Have the concentrator generate an acknowledgement code and issue a pairing request acknowledgement including the acknowledged pairing information and the generated acknowledgement code, the pairing request acknowledgement being encrypted with the sensor public key; - Have the sensor convert the received acknowledgement code into an optical signal sequence and have the light-emitting diode execute the optical signal sequence; - Have the mobile terminal convert the executed optical signal sequence into an optical signal sequence acknowledgement code; - Have the mobile terminal send the optical signal sequence acknowledgement code to the concentrator via the secure channel; - Have the concentrator compare the optical signal sequence acknowledgement code and the generated acknowledgement code: o Have the concentrator deactivate the acknowledgement code, and: · If the optical signal sequence acknowledgement code does not match the generated acknowledgement code, generate a warning via the mobile terminal and have the concentrator delete the pairing information; · If the optical signal sequence acknowledgement code matches the generated acknowledgement code, pair the sensor and the concentrator using the pairing information and exchange information between the sensor and the concentrator.

2. The method according to claim 1, wherein The mobile terminal communicates with the concentrator via a short-range communication mode.

3. The method according to any one of the preceding claims, characterized in that, Placing the concentrator in pairing mode is performed by an operator via the mobile terminal, and placing the sensor in pairing mode is performed by the operator by pressing a pairing button on the sensor.

4. The method according to claim 1 or 2, characterized in that, The pairing request is issued by the sensor in the form of a radio frequency frame in a loop.

5. The method according to claim 1 or 2, characterized in that, The pairing request acknowledgement further includes a shared key, and once the sensor and the concentrator are paired, the information exchanged between the sensor and the concentrator is encrypted with the shared key.

6. The method according to claim 1 or 2, characterized in that, The acknowledgement code is randomly generated by the concentrator.

7. The method according to claim 1 or 2, characterized in that The optical signal sequence emitted by the light-emitting diode includes optical signals of different wavelengths.

8. The method according to claim 1 or 2, characterized in that, Converting the executed optical signal sequence into an optical signal sequence acknowledgement code includes the following steps: - Have the operator input the optical signal sequence via a human-machine interface of the mobile terminal, and have the mobile terminal convert the input optical signal sequence into an optical signal sequence acknowledgement code; or - Have the camera of the mobile terminal acquire the optical signal sequence, and have the mobile terminal convert the acquired optical signal sequence into an optical signal sequence acknowledgement code.

9. The method according to claim 1 or 2, characterized in that, It further includes steps: sending data input by an operator via a human-machine interface of the mobile terminal to the concentrator via the secure channel, if the optical signal sequence confirmation code does not match the generated confirmation code, the input data is deleted by the concentrator, and if the optical signal sequence confirmation code matches the generated confirmation code, the input data is used for pairing and retained by the concentrator.

10. The method according to claim 1 or 2, characterized in that It further includes a step of sending a pairing confirmation from the concentrator to the mobile terminal via the secure channel.

11. A mobile terminal for implementing the method according to any one of the preceding claims, including a human-machine interface and configured to: - Manage data input via the human-machine interface; - Exchange data with the concentrator via the secure channel; - Convert an optical signal sequence executed by the sensor into an optical signal sequence confirmation code; - Generate a warning when the optical signal sequence confirmation code does not match the confirmation code generated by the concentrator.

12. The mobile terminal according to claim 11, characterized in that, It includes a camera and is configured to acquire the optical signal sequence via the camera.

13. A system for implementing the method according to any one of claims 1 to 10, including: - A mobile terminal according to any one of claims 11 or 12, - A sensor including at least one light-emitting diode; - A concentrator; The sensor is configured to: - Generate a cryptographic key; - Send a pairing request when the sensor is placed in the pairing mode; - Receive a pairing request confirmation including a confirmation code from the concentrator; - Convert the confirmation code received from the concentrator into an optical signal sequence; - Execute the optical signal sequence via the light-emitting diode; o Exchange information with the concentrator once paired with the concentrator; The concentrator is configured to: - Generate a cryptographic key; - Send a public key when the concentrator is placed in the pairing mode; - Generate a confirmation code when receiving a pairing request from the sensor and send a pairing request confirmation including the generated confirmation code; - Exchange data with the mobile terminal via the secure channel; - Compare the optical signal sequence confirmation code received from the mobile terminal with the generated confirmation code; - Delete data when the optical signal sequence confirmation code does not match the generated confirmation code; - Exchange information with the sensor once paired with the sensor.

Images