METHOD FOR AUTHENTICATION BETWEEN A CONTROL MODULE AND A LIGHTING MODULE FOR A MOTOR VEHICLE
20230047428 · 2023-02-16
Assignee
Inventors
- Patrice VOIRIN (Bobigny, FR)
- Houssem KOUKI (Bobigny, FR)
- Feng YANG (Bobigny, FR)
- Eric DONNAT (Bobigny, FR)
- Rodrigo CARBONELL (Bobigny, FR)
Cpc classification
B60Q11/00
PERFORMING OPERATIONS; TRANSPORTING
B60Q1/143
PERFORMING OPERATIONS; TRANSPORTING
Y02B20/40
GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
B60Q2300/146
PERFORMING OPERATIONS; TRANSPORTING
International classification
H04L9/08
ELECTRICITY
H04L9/32
ELECTRICITY
Abstract
A method for authentication between a control module and a lighting module for a motor vehicle, in which at least one of the two modules is a transmitter module, the other being a receiver module, the two modules comprising a unit for transmitting/receiving data and being linked by a data communication channel that enables the modules to exchange data. The method including transmitting of data describing at least one authentication factor from the transmitter module to the receiver module, verification of the authentication factor by means of a calculation unit, and abandoning communication, in the receiver module, with the transmitter module if the verification fails, or otherwise continuing communication.
Claims
1. A method for authentication between a control module and a lighting module for a motor vehicle, in which at least one of the two modules is a transmitter module, the other being a receiver module, the two modules each including a data transmission/reception unit and being linked by a data communication channel that allows the modules to exchange data, the method comprising: transmitting data describing at least one authentication factor from the transmitter module to the receiver module; verifying the authentication factor by a computing unit in the receiver module; and breaking off communication, by the receiver module, with the transmitter module if the verification fails.
2. The method as claimed in claim 1, wherein the authentication factor includes an indication of a date, or of a counter of data exchanges between the two modules.
3. The method as claimed in claim 1, wherein the authentication factor includes cryptographically encrypted data, with the receiver module including a memory element in which verification data is stored in order for the encrypted data can be verified.
4. The method as claimed in claim 3, wherein the cryptographically encrypted data comprise a hash value of a date indication, or of a counter of data exchanges between the two modules.
5. The method as claimed in claim 1, further comprising exchanging public encryption keys between the two modules, with the encryption keys forming part of public/private encryption pairs associated with the two modules.
6. The method as claimed in claim 1, wherein the authentication factor includes data signed or encrypted using a private key of the transmitter module.
7. The method as claimed in claim 1, wherein the transmitter module is the control module and in that the data describing the at least one authentication is included in a header of a data packet, with the data in the data packet describing at least part of a lighting setpoint, a default setpoint, or data relating to the motor vehicle.
8. The method as claimed in claim 1, wherein the transmitter module is the lighting module and in that the data describing the at least one authentication is included in a header of a data packet, with the data in the data packet describing at least some calibration data relating to a light source in the lighting module.
9. The method as claimed in claim 8, wherein the light source includes a matrix light source.
10. The method as claimed in claim 1, wherein the communication between the two modules is broken off following a predetermined number of failures to verify the data describing an authentication factor of the transmitter module.
11. A lighting system for a motor vehicle, the system comprising: a control module and a lighting module, each of the two modules including a transmission/reception unit and the two modules being linked by a data communication channel that allows the two modules to exchange data, wherein the control module and the lighting module are configured to transmit data describing at least one authentication factor between the two modules, verify the authentication factor by means of a computing unit in on of the two modules, and break off communication between the two modules if the verification fails.
12. (canceled)
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0035] Other features and advantages of the present invention will be better understood with the aid of the description of the examples and of the drawings, in which:
[0036]
[0037]
DETAILED DESCRIPTION OF THE INVENTION
[0038] Unless specified otherwise, technical features that are described in detail for one given embodiment may be combined with the technical features that are described in the context of other embodiments described by way of example and without limitation.
[0039] The description focuses on the elements of a lighting module for a motor vehicle that are required to understand the invention. Other elements, which in a known manner form part of such modules, will not be mentioned or described in detail. For example, the presence and operation of a converter circuit involved in supplying electrical power to a matrix light source, known per se, will not be described in detail. The same applies for optical elements such as lenses, for example.
[0040]
[0041]
[0042] The authentication function may, for example, comprise the exchange of public cryptographic keys between the two modules in question, thus allowing the reciprocal verification of the authenticity of data signed by means of the corresponding private cryptographic keys. Alternatively or in addition, the control/computing unit 130 for the lighting module 100 sends an acknowledgment of receipt to the control module 20 for a received data packet, the acknowledgment of receipt comprising at least one authentication factor 160 that allows the microcontroller that forms the computing unit 130 to be authenticated. The data packet may, for example, contain calibration data, and/or default image data and/or data for generating a default image and/or all or part of an image and/or of a group of images, and/or a packet from a compressed video stream. In one preferred embodiment, this authentication is not performed on all of the packets. In this way, the corresponding computing load is lightened and smoothed out over time. Still alternatively, the authentication function may comprise sending, from the control module 20 for the motor vehicle to the control unit 130 for the lighting module, of a header for a sent data packet, the header comprising a part allowing the control module 20 to be authenticated, the data packet being of the same type as defined above. Advantageously, this authentication is not performed on all of the packets. In this way, the corresponding computing load is lightened and smoothed out over time.
[0043] In order to perform the authentication function, the lighting module 100 and the control module 20 for the motor vehicle comprise computing means for generating the header or the acknowledgment of receipt used for authentication, respectively. Preferably, the authentication factor is generated according to a time or a date, which may be expressed in any unit of time, for example in milliseconds, or a counter counting exchanges or computing cycles, or another element that changes with the number of exchanges, which may be reset when it exceeds a predefined size.
[0044] If the two modules comprise synchronized clocks and/or counters, both may verify the data in the header by comparing them with the value from its own clock, or from its corresponding own counter. The data in the header may also be hashed using a cryptographic hash function. The receiver module may generate a hash value from its corresponding counter. Only if the two counters of the communicating modules are strictly identical will the hash value thus obtained be identical to that of the header.
[0045] In the event that authentication between the controller and the microcontroller fails, the lighting function may be put into a communication failure mode. Advantageously, the failure mode is activated only in the event of repeated authentication failures, which makes it possible to avoid activating failure mode if the link has been disrupted, for example by transient electromagnetic interference, which is particularly advantageous in the case of an authentication function using headers or acknowledgments of receipt.
[0046] In the case where the control unit 130 comprises a computer, it may implement a data exchange encryption function, in which data encrypted by the control module 20 for the motor vehicle are decrypted by the computer. Advantageously, the computer has a method for determining if the stream has not been decoded correctly. If the stream has not been decoded correctly, the computer may go into a communication failure mode. The communication failure mode may involve the following procedures, taken alone or in combination: [0047] stopping the lighting function or the lighting module projecting a default image, [0048] the control module 20 generating a failure signal sent to a central management system of the vehicle, [0049] the computer entering an authentication mode in which the computer continues launching an authentication procedure with respect to the computer for the control module 20 (or vice versa). In the authentication mode, the sending of data packets may be interrupted.
[0050] Once the initial authentication has ended successfully, the rest of the communication between the modules 20, 100 may, according to one preferred embodiment which will be described in a non-limiting manner below with reference to the illustration of
[0051] The lighting module 100 preferably comprises a matrix light source 110 grouping together a plurality of elementary light sources 112. In the example illustrated, this is a matrix of LEDs without, however, the invention being limited to this example. The matrix light source may also be produced by a micromirror device, for which each mirror is designed to generate one elementary light beam of a matrix. The module comprises a data reception and transmission unit 120; this is, for example, an interface capable of receiving and decoding messages over a data bus internal to the motor vehicle, such as a CAN (Controller Area Network) bus.
[0052] The data reception unit 120 is capable of receiving/sending data from/to at least one control module for the motor vehicle—in particular, it may carry out the exchanges of steps a) or b) of the authentication method described above. The control module 20 comprises data 22 relating to the motor vehicle, such as its attitude, the position of the lighting module in the motor vehicle, or other data. The module 100 further comprises a memory element 140, such as a flash-type memory, to which the control unit 130 is functionally connected and has read access, and in which calibration data 150 specific to the matrix source 112 are stored. By way of example, the data may comprise, for each elementary light source 112, a value indicating the difference in brightness with respect to the average brightness of the matrix source 110, possibly over a range of load current strengths. The data 150 may nevertheless comprise more complex optical or geometric calibration parameters, without thereby departing from the scope of the present invention.
[0053] The exchange of data between the light module 100 and the control module 20 for the motor vehicle after pairing the two modules allows some advantageous applications. In particular, it is proposed to combine data relating to the vehicle 22, such as, for example, orientation, position, or attitude parameters of the vehicle, or information relating to luminous fluxes emitted by other headlights of the vehicle, which are a priori only available at the control module 20, with the calibration data 150, available at the lighting module 100 and specific to the matrix source 110 installed therein. This information is used, according to one preferred embodiment but in a non-limiting manner, by the control module 20 for the motor vehicle to generate a default image or setpoint 001. To do this, the relevant portion of the calibration data 150 is first transmitted from the lighting module 100 to the control module 20, as indicated by the solid arrow in
[0054] Alternatively, this computation may be performed by the control unit 130 for the lighting module after a corresponding exchange of the data 22 required for this computation between the control unit for the motor vehicle on the one hand and the control unit for the lighting module on the other hand, represented by the dashed arrow in
[0055] A default image is an image that is projected by the module when a fault or failure is detected. Thus, the module may preferably comprise an electronic error detection circuit (not illustrated), or a microprocessor programmed for this purpose by a suitable computer program. The error detection circuit is configured to detect, for example, that the data received by the control module for the motor vehicle are inconsistent, or that the connection between the control module for the motor vehicle and the lighting module 100 is no longer reliable. Following this detection of an error, the default image 001 is projected instead of the current setpoint image, with the aim of avoiding potential dazzling of other road users. The default image is generated to take into account the specificities of the matrix light source 110 on the one hand, and of the vehicle equipped therewith on the other hand. Thus, the default image may, for example, be generated precisely and automatically for each motor vehicle and each lighting module with which the vehicle is equipped. Preferably, the default image resulting from this method is transmitted to the lighting module, which stores it permanently in a dedicated memory element. In the event of communication failure between the control module 20 for the motor vehicle and the lighting module 100, the default setpoint then serves as a control for the matrix light source. The default setpoint or image may, for example, correspond to low-beam headlight illumination. In particular, this image may correspond to a low-beam headlight cut-off. Specifically, the cut-off must be well defined in order to satisfy the regulations in force. The precise generation of the default setpoint, taking into account all of the described parameters, makes it possible in particular to prevent other road users from being dazzled when the default setpoint is projected by the lighting module.
[0056] According to one preferred embodiment, in the absence of a fault and following pairing of the motor vehicle with the lighting module, the control module 20 may, for example, send a lighting setpoint to the lighting module 100, which is responsible for controlling the matrix light source according to the received setpoint. Such a setpoint may, for example, comprise a brightness value, such as a grayscale level, encoded on a predetermined number of bits, to be produced by each of the elementary light sources 112. The lighting setpoint may therefore be a digital image, and it may in particular be a frame from a stream of such images, constituting a video signal. The control unit 130 is intended to control said matrix light source according to said lighting setpoint. The control unit may be connected to, or comprise, a circuit for driving the electrical power supply for the elementary light sources 112, which is controlled in order to supply the elementary light sources with power in such a way as to implement the lighting setpoint.
[0057] In order to ensure uniform light intensity, the control unit 130 adjusts the setpoint values received by the control module 20 by adding thereto or subtracting therefrom the respective differences described in the calibration data 150, before controlling the elementary light sources in accordance with the result. The data 150 may nevertheless comprise more complex optical or geometric calibration parameters, without thereby departing from the scope of the present invention. In such a case, instead of acting only at the level of each light source or at the level of each pixel individually, the correction of the original setpoint may advantageously produce a correction at the level of the entire setpoint, i.e. at the level of the entire image to be projected, or at the level of at least a portion or a region of this image. For example, the image projected without the setpoint correction might exhibit a concave curved appearance due to the projection optics in the vicinity of the projection region. Producing the precorrected setpoint, which takes into account the calibration data including the geometric deformation imposed by the projection optics, results in a projected image exhibiting a geometry closer to the desired, non-curved geometry. To apply a correction for geometric aberrations, a deformation is applied to the entire original setpoint image. As this is discretized, this deformation causes degradation of the information contained in the initial image. It is therefore advantageous for the setpoint image transmitted from the control unit for the vehicle to the control unit to have a resolution higher than the projection resolution of the light module.
[0058] The control unit 130 comprises a microcontroller element that has sufficient computing power to correct the setpoint 10, or a stream of setpoints, in real time, by applying the calibration data 150 thereto.
[0059] According to one preferred embodiment, the lighting module is arranged so as to transmit at least some of the calibration data 150, and preferably all of this data, to the control module 20. This is, for example, performed in a phase of initializing the lighting module. In order to guarantee uniform light intensity, the control module 20 takes into account the calibration data 150 thus received in order to determine the setpoint image. For example, the control module 20 adjusts the setpoint values by adding thereto or subtracting therefrom the respective differences before transmitting the result to the lighting module 100. The data 150 may nevertheless comprise more complex optical or geometric calibration parameters, without thereby departing from the scope of the present invention. In this embodiment, the control unit 130 is freed from the task of correcting the setpoint, and it may be performed by a less expensive microcontroller element that has less computing power.
[0060] It goes without saying that the described embodiments do not limit the scope of the protection of the invention. By referring to the description that has just been given, other embodiments may be contemplated without otherwise departing from the scope of the present invention.
[0061] The scope of protection is defined by the claims.