Module connection method and system for autonomous vehicle

Abstract

The invention provides a module connection method and system of an automatic driving vehicle. The module connection method and system can be applied to scenes such as ports, expressways, logistics, mines, closed parks or urban traffic. The method comprises the following steps: acquiring information stored in a first storage module of a module in response to an in-place signal generated when the module is inserted into a connector; performing standard verification on the module according to the information stored in the first storage module to determine whether the module is a standard module of the domain controller; if the module is the standard module of the domain controller, a power supply signal is generated, the power supply signal is used for controlling a power module of the domain controller to globally power on the module, and the power supply voltage of the standby power supply is smaller than that of the power module. According to the method provided by the invention, the accuracy and safety of connection between the module and the domain controller are improved.

Description

Technical Field

[0001] The present application relates to the field of autonomous driving technology, and in particular to a module connection method and system for an autonomous driving vehicle. Background Art

[0002] In the field of autonomous driving, in order to improve control flexibility and reduce costs, autonomous driving domains usually decouple functions, that is, the domain controller generally only includes a microcontroller unit (MCU), and the system on chip (SOC) is separately set up in the form of a module and connected to the domain controller through a connector to realize various calculations of the autonomous driving process.

[0003] In related technologies, modules are usually connected to connectors in the form of long and short pins. After the module is inserted into the connector, the connector will generate a presence signal. After the MCU reads the presence signal, it will control the power module in the domain controller to globally power on the module and complete the connection between the module and the domain controller. However, modules produced by different manufacturers often have the same size and pin definition, which may result in the module inserted into the connector not being a standard module compatible with the domain controller. An incompatible module may cause the domain controller to malfunction or short-circuit.

[0004] Therefore, there is a need for a module connection solution for autonomous driving vehicles that can improve the accuracy and security of the connection between the module and the domain controller. Summary of the invention

[0005] The embodiments of the present application provide a module connection method and system for an autonomous driving vehicle, which can improve the accuracy and security of the connection between the module and the domain controller.

[0006] In a first aspect, an embodiment of the present application provides a module connection method for an autonomous driving vehicle, which is applied to a domain controller, wherein a connector is provided on the domain controller, wherein the connector is electrically connected to a standby power supply, and wherein the standby power supply is used to power the connector, and wherein the method comprises:

[0007] In response to a presence signal generated by the module being inserted into the connector, information stored in a first storage module of the module is acquired, wherein the standby power supply is also used to supply power to the first storage module when the module is inserted into the connector;

[0008] Performing a standardization check on the module according to the information stored in the first storage module to determine whether the module is a standard module of the domain controller;

[0009] If the module is a standard module of the domain controller, a power supply signal is generated, and the power supply signal is used to control the power module of the domain controller to globally power on the module, and the supply voltage of the standby power supply is lower than the supply voltage of the power module.

[0010] In this embodiment, the connector can be electrically connected to the standby power supply, and an independent and low-voltage standby power supply is used to power the connector and the module, rather than the high-voltage power supply module in the domain controller, thereby avoiding the risk of short circuit caused by the insertion of an incompatible module into the connector. When the module is inserted into the connector, the standby power supply can only power the first storage module of the module, ensuring that only the storage module in the module can work normally, further avoiding the risk of short circuit when the inserted module is not a standard module, and improving the accuracy and safety of the connection between the module and the domain controller. Furthermore, when the domain controller detects the in-place signal generated by the module being inserted into the connector, the module can be checked for standardization based on the information stored in the first storage module to verify whether the module inserted into the connector is a standard module of the domain controller. Only when it is determined that the module is a standard module of the domain controller will the domain controller control the power module of the domain controller to globally power on the module and complete the connection between the module and the controller. Through such a setting, the information stored in the first storage module of the module can be used to perform standardization verification on the module, and global power-on control can only be performed on standard modules that have passed the verification, thereby avoiding the domain controller from malfunctioning or short-circuiting due to the insertion of non-standard modules into the connector, further improving the accuracy and security of the connection between the module and the domain controller, and ensuring that the domain controller can operate normally.

[0011] In a possible implementation manner, the information stored in the first storage module includes basic information of the first module, and the performing standardization check on the module according to the information stored in the first storage module to determine whether the module is a standard module of the domain controller includes:

[0012] Performing basic information verification on the module according to the basic information of the first module;

[0013] If the basic information verification of the module passes, performing a hash code verification on the module to determine whether the module is a standard module;

[0014] If the basic information verification of the module fails, it is determined that the module is not a standard module of the domain controller.

[0015] In this embodiment, when the module is checked for standardization, the basic information check and the hash code check can be performed on the module in sequence. The basic information can be used to check whether the basic information of the inserted module is accurate, that is, to perform hardware verification; the hash code can be used to check whether the version of the inserted module, the debugged program, etc. are accurate, that is, to perform software verification, thereby comprehensively and accurately determining whether the module is a standard module of the domain controller.

[0016] In a possible implementation manner, if the module basic information verification fails, the method further includes:

[0017] Generate and output first connection error prompt information according to the first module basic information, where the first connection error prompt information is used to prompt that verification of the module basic information has failed.

[0018] In this embodiment, if the basic information verification of the module fails, the domain controller may generate and output a first connection error prompt message to prompt the user that the model of the module is inaccurate and the module needs to be replaced in time.

[0019] In a possible implementation manner, the verifying basic information of the module according to the first module basic information includes:

[0020] Acquire basic information of the second module pre-stored in the second storage module of the domain controller, wherein the basic information of the module includes manufacturer information, module model information and serial number;

[0021] Determining whether the first module basic information is consistent with the second module basic information;

[0022] If they are consistent, it is determined that the basic information verification of the module has passed;

[0023] If they are inconsistent, it is determined that the module basic information verification has failed.

[0024] In this implementation, by comparing the first module basic information stored in the module with the second module basic information pre-stored in the domain controller, the basic information of the module can be verified simply and accurately.

[0025] In a possible implementation manner, performing hash code verification on the module to determine whether the module is a standard module includes:

[0026] Obtaining a module hash code stored in a first storage module of the module, and obtaining a hash code pool pre-stored in a second storage module of the domain controller;

[0027] Determine whether there is a target hash code consistent with the module hash code in the hash code pool;

[0028] If so, determining that the module is a standard module of the domain controller;

[0029] If not, it is determined that the module is not a standard module of the domain controller, and a second connection error prompt message is output, where the second connection error prompt message is used to prompt that the module hash code verification has failed and the module hash code is wrong.

[0030] In this embodiment, before obtaining the module hash code of the module, it is also necessary to determine whether the module hash code exists in the first storage module of the module to determine whether the inserted module has been debugged. If the module hash code does not exist, it means that the module is still a general module and cannot be used without program debugging, thereby comprehensively verifying whether the module and the domain controller are software compatible.

[0031] In a possible implementation manner, before obtaining the module hash code stored in the first storage module of the module, the method further includes:

[0032] Determining whether a module hash code exists in a first storage module of the module;

[0033] If so, executing the step of obtaining the module hash code stored in the first storage module of the module;

[0034] If not, it is determined that the module is not a standard module of the domain controller, and a third connection error prompt message is output, where the third connection error prompt message is used to prompt that the module hash code verification has failed and the module hash code does not exist.

[0035] In this embodiment, before obtaining the module hash code of the module, it is also necessary to determine whether the module hash code exists in the first storage module of the module to determine whether the inserted module has been debugged. If the module hash code does not exist, it means that the module is still a general module and cannot be used without program debugging, thereby comprehensively verifying whether the module and the domain controller are software compatible.

[0036] In a second aspect, an embodiment of the present application provides a module connection system for an autonomous driving vehicle, comprising: a domain controller as described in any one of the first aspects, wherein the domain controller is provided with a connector, and the connector is electrically connected to a standby power supply;

[0037] The standby power supply is used to supply power to the connector and to supply power to the first storage module of the module when the module is inserted into the connector;

[0038] The connector is used to generate a presence signal when the module is inserted and connect the module and the domain controller;

[0039] The domain controller is used to obtain information stored in the first storage module of the module in response to an in-place signal generated by the module being inserted into the connector; perform a standardization check on the module based on the information stored in the first storage module to determine whether the module is a standard module of the domain controller; if the module is a standard module of the domain controller, generate a power supply signal, and the power supply signal is used to control the power supply module of the domain controller to globally power on the module, and the power supply voltage of the standby power supply is less than the power supply voltage of the power supply module.

[0040] In this embodiment, the connector can be electrically connected to the standby power supply, and an independent and low-voltage standby power supply is used to power the connector and the module, rather than the high-voltage power supply module in the domain controller, thereby avoiding the risk of short circuit caused by the insertion of an incompatible module into the connector. When the module is inserted into the connector, the standby power supply can only power the first storage module of the module, ensuring that only the storage module in the module can work normally, further avoiding the risk of short circuit when the inserted module is not a standard module, and improving the accuracy and safety of the connection between the module and the domain controller. Furthermore, when the domain controller detects the in-place signal generated by the module being inserted into the connector, the module can be checked for standardization based on the information stored in the first storage module to verify whether the module inserted into the connector is a standard module of the domain controller. Only when it is determined that the module is a standard module of the domain controller will the domain controller control the power module of the domain controller to globally power on the module and complete the connection between the module and the controller. Through such a setting, the information stored in the first storage module of the module can be used to perform standardization verification on the module, and global power-on control can only be performed on standard modules that have passed the verification, thereby avoiding the domain controller from malfunctioning or short-circuiting due to the insertion of non-standard modules into the connector, further improving the accuracy and security of the connection between the module and the domain controller, and ensuring that the domain controller can operate normally.

[0041] In a possible implementation, the connector is connected to the standby power supply through a first power supply circuit, and the first power supply circuit is in a conducting state, so that the standby power supply supplies power to the connector through the first power supply circuit, and when the module is inserted into the connector, the connector and the first storage module of the module are supplied with power through the first power supply circuit;

[0042] The connector is also connected to the power module through a second power supply circuit, and the second power supply circuit is in a disconnected state; the power supply signal is specifically used to control the conduction of the second power supply circuit, so that the power module powers on the module globally through the second power supply circuit and the connector in sequence.

[0043] In this embodiment, the standby power supply signal power supply can be connected to the connector through the first power supply circuit in the on state, so that the standby power supply always supplies power to the connector, and supplies power to the first storage module of the module when the module is inserted into the connector. The connector can also be connected to the power module through the second power supply circuit in the off state. When the module is not inserted or the module standardization check fails, the power module cannot supply power to the connector and the module. Only when the module standardization check passes and the domain controller sends a power supply signal to the second power supply circuit, the second power supply circuit will be turned on to enable the power module to supply power to the connector, thereby enabling the module to be powered on globally. Through such a setting, it is possible to avoid the domain controller from malfunctioning or short-circuiting due to the insertion of a non-standard module into the connector, thereby improving the accuracy and safety of the connection between the module and the domain controller.

[0044] In a possible implementation manner, the connector is further connected to the standby power supply via a signal path, and the signal path is used to transmit a high level signal generated by the standby power supply to the connector, so that the pin between the connector and the domain controller is at a high level;

[0045] The module is grounded, and when the module is inserted into the connector, the pin is changed from a high level to a low level, indicating a presence signal.

[0046] In this embodiment, the standby power supply can also provide a high-level signal to the connector through the signal path. When the module is inserted into the connector, the grounded module can pull the pin between the connector and the domain controller to a low level, thereby generating a presence signal. With such a setting, the domain controller can accurately detect that the module has been inserted into the connector based on the presence signal.

[0047] In a possible implementation, the standby power supply is further connected to a ground electrode via a discharge diode, and the discharge diode is used to maintain a high impedance state when the standby power supply works normally, and to be turned on when the standby power supply is short-circuited to discharge instantaneous current to the ground electrode.

[0048] In this embodiment, the standby power supply can also be connected to the ground electrode through a discharge diode. Even if a non-standard module is inserted into the connector and causes a short circuit in the standby power supply, the short-circuit current can be discharged through the discharge diode and will not cause a short circuit in the domain controller, further improving the security of the connection between the module and the domain controller. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 It is a structural schematic diagram of a module connection system in the related art;

[0050] Figure 2 This is a schematic diagram of the structure of a module connection system for an autonomous driving vehicle according to an embodiment of the present application;

[0051] Figure 3 This is a flowchart of a module connection method for an autonomous driving vehicle according to an embodiment of the present application.

[0052] Figure numerals: 1. module; 2. connector; 3. domain controller; 4. power module; 5. standby power supply; 6. discharge diode. DETAILED DESCRIPTION

[0053] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0054] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0055] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.

[0056] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0057] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0058] The module connection method and system of the autonomous driving vehicle of the present application can be used in the field of autonomous driving, and can also be used in any field except the field of autonomous driving, such as the field of module verification, etc. The application field of the module connection method and system of the autonomous driving vehicle of the present application is not limited.

[0059] The module connection method and system of the autonomous driving vehicle of the present application can be applied to scenarios such as ports, highways, logistics, mines, closed parks, or urban transportation. Any related scenarios involving the connection between domain controllers and modules, such as the connection between the vehicle's domain controller and the SOC module, the connection between the domain controller and other modules, etc., can all apply the module connection method and system of the autonomous driving vehicle of the present application.

[0060] First, the terms involved in this application are explained:

[0061] A module refers to a module or component, which is an independent functional unit that can be combined with other units to achieve more complex functions.

[0062] Standby power is used to provide power to certain key circuits or components when the main power is turned off or the system is in low power mode. It is usually a 3.3 volt power supply "3V3_stby".

[0063] MD5 (Message Digest Algorithm 5) is a widely used hash function that can generate a 128-bit hash value (32-character hexadecimal string) for file integrity verification and data authentication.

[0064] EEPROM (Electrically-Erasable Programmable Read-Only Memory, E2PROM) is a semiconductor memory device that can be electronically rewritten multiple times.

[0065] SOC (System on Chip) is an integrated circuit design method that integrates multiple components of a computer system into a single chip, including processor (CPU), graphics processing unit (GPU), memory, input / output interface (I / O), storage controller, power management unit (PMU), multimedia processing unit, wireless communication module, sensor interface and other structures.

[0066] High impedance state refers to an output state of a circuit, which is neither a high level nor a low level. If the high impedance state is input into the next level circuit, it will have no effect on the next level circuit, which is the same as not being connected.

[0067] The autonomous driving domain usually decouples functions, that is, the domain controller generally only includes the MCU, and the SOC is set up separately in the form of a module and connected to the domain controller through a connector to realize various calculations of the autonomous driving process.

[0068] In the related art, the module is usually connected to the connector in the form of long and short pins. Figure 1 It is a structural diagram of a module connection system in the related art, such as Figure 1 As shown, after module 1 is inserted into connector 2, connector 2 generates a presence signal. After the MCU of domain controller 3 reads the presence signal generated by connector 2, it controls the power module 4 in the domain controller to globally power on module 1, completing the connection between module 1 and domain controller 2.

[0069] However, modules produced by different manufacturers often have the same size and pin definition, which may result in the module inserted into the connector not being a standard module compatible with the domain controller. An incompatible module may cause the domain controller to malfunction or cause a short circuit.

[0070] Based on the above technical problems, the inventive concept of this application is: how to provide a module connection solution for autonomous driving vehicles that can improve the accuracy and safety of the connection between the module and the domain controller.

[0071] The embodiment of the present application provides a module connection method and system for an autonomous driving vehicle, which can use an independent and low-voltage standby power supply to only power the first storage module of the module when the module is inserted into the connector, and only ensure that the storage module in the module can work normally, avoiding the risk of short circuit caused by the inserted module is not a standard module. In addition, when the domain controller detects the in-place signal generated by the module being inserted into the connector, it can perform a standardization check on the module according to the information stored in the first storage module. Only when it is determined that the module is a standard module of the domain controller, the domain controller will control the power module of the domain controller to globally power on the module to complete the connection between the module and the controller, avoiding the domain controller not working properly or short circuit caused by the non-standard module being inserted into the connector, improving the accuracy and safety of the connection between the module and the domain controller, and ensuring that the domain controller can work normally.

[0072] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0073] Figure 2 FIG. 1 is a schematic diagram of a module connection system for an autonomous driving vehicle according to an embodiment of the present application. Figure 2 As shown, the module connection system of the autonomous driving vehicle may include a domain controller 3 , on which a connector 2 may be provided, and the connector 2 is electrically connected to a standby power supply 5 .

[0074] The standby power supply 5 can be used to supply power to the connector 2 and to supply power to the first storage module of the module 1 when the module 1 is inserted into the connector 2 .

[0075] The connector 2 can be used to generate a presence signal when the module 1 is inserted, and to connect the module 1 and the domain controller 33 .

[0076] The domain controller 3 can be used to respond to the in-place signal generated by the module 11 being inserted into the connector 2 to obtain the information stored in the first storage module of the module 1; based on the information stored in the first storage module, perform a standardization check on the module 1 to determine whether the module 1 is the standard module 1 of the domain controller 3; if the module 1 is the standard module 1 of the domain controller 3, generate a power supply signal, and the power supply signal is used to control the power module 4 of the domain controller 3 to globally power on the module 1, and the power supply voltage of the standby power supply 5 is less than the power supply voltage of the power module 4.

[0077] In this embodiment, the domain controller 3 may be a domain controller of the vehicle autonomous driving domain, or a domain controller of other domains such as a power domain, without any limitation.

[0078] It should be noted that the domain controller 3 mentioned in this embodiment may specifically be the MCU of the domain controller 3 .

[0079] In this embodiment, the connector 2 may be disposed on the base of the domain controller 3 . The connector 2 may be a mainstream Molex connector or other connectors, and no limitation is made here.

[0080] In this embodiment, module 1 may include units such as SOC, DDR, EMMC, and a power conversion module to provide computing power for the autonomous driving process.

[0081] In this embodiment, the standby power supply 5 is an independent low-voltage power supply, and the standby power supply 5 can be a 3.3v low-voltage power supply, that is, a 3V3-stby power supply. The power supply module 4 can be a power supply in the domain controller 3, which supplies power to components in the domain controller 3 and devices connected to the domain controller 3, and the power supply module 4 can be a 12V high-voltage power supply.

[0082] In this embodiment, the in-place signal can be a low-level signal generated on the connection pin between connector 2 and domain controller 3 when module 1 is inserted into connector 2, or it can be other signals. There is no limitation here as long as it can indicate that module 1 is inserted into connector 2.

[0083] In this embodiment, the standby power supply 5 is connected to the connector 2, and always supplies power to certain circuits inside the connector 2, regardless of whether a module 1 is inserted. When the module 1 is inserted into the connector 2, the standby power supply 5 also supplies power to the first storage module of the module 1, ensuring that only the first storage module works normally, and avoiding the risk of short circuit caused by the inserted module 1 being not a standard module 1.

[0084] In this embodiment, when module 1 is just inserted into connector 2, the high-voltage power module 4 in domain controller 3 will not supply power to module 1 and connector 2. Only when module 1 is determined to be a standard module 1 of domain controller 3, domain controller 3 will control power module 4 of domain controller 3 to globally power on module 1, so as to avoid the power module 4 being connected to the ground signal when a non-standard module 1 is inserted, causing a short circuit and damaging domain controller 3.

[0085] In this embodiment, control logic may be pre-stored in the register inside the module 1: when it is detected that the standby power supply 5 is supplying power, only the power supply path between the standby power supply 5 and the first storage module of the module 1 is turned on, that is, only the power-on of the first storage module is completed; when it is detected that the standby power supply 5 and the power module 4 are supplying power together, the power supply path between the power module 4 and each internal module is turned on to achieve global power-on.

[0086] In this embodiment, the first storage module may be an Electrically-Erasable Programmable Read-Only Memory (EEPROM / E2PROM for short), or may be other types of storage modules, which are not limited herein.

[0087] In this embodiment, the power supply signal can be flexibly set by those skilled in the art, as long as the power supply signal can control the domain power module 4 to globally power on the module 1 , and no limitation is made here.

[0088] In this embodiment, the implementation of the specific functions of the domain controller 3 can refer to the following method embodiments, which will not be described in detail here.

[0089] In this embodiment, the connector can be electrically connected to the standby power supply, and an independent and low-voltage standby power supply is used to power the connector and the module, rather than the high-voltage power supply module in the domain controller, thereby avoiding the risk of short circuit caused by the insertion of an incompatible module into the connector. When the module is inserted into the connector, the standby power supply can only power the first storage module of the module, ensuring that only the storage module in the module can work normally, further avoiding the risk of short circuit when the inserted module is not a standard module, and improving the accuracy and safety of the connection between the module and the domain controller. Furthermore, when the domain controller detects the in-place signal generated by the module being inserted into the connector, the module can be checked for standardization based on the information stored in the first storage module to verify whether the module inserted into the connector is a standard module of the domain controller. Only when it is determined that the module is a standard module of the domain controller will the domain controller control the power module of the domain controller to globally power on the module and complete the connection between the module and the controller. Through such a setting, the information stored in the first storage module of the module can be used to perform standardization verification on the module, and global power-on control can only be performed on standard modules that have passed the verification, thereby avoiding the domain controller from malfunctioning or short-circuiting due to the insertion of non-standard modules into the connector, further improving the accuracy and security of the connection between the module and the domain controller, and ensuring that the domain controller can operate normally.

[0090] In one possible embodiment, the connector 2 can be connected to the standby power supply 5 through a first power supply circuit, and the first power supply circuit is in an on state, so that the standby power supply 5 supplies power to the connector 2 through the first power supply circuit, and when the module 1 is inserted into the connector 2, the connector 2 and the first storage module of the module 1 are powered through the first power supply circuit.

[0091] Connector 2 can also be connected to the power module 4 through a second power supply circuit, and the second power supply circuit is in a disconnected state; the power supply signal is specifically used to control the conduction of the second power supply circuit, so that the power module 4 can power on the module 1 globally through the second power supply circuit and connector 2 in turn.

[0092] In this embodiment, the standby power supply 5 can be connected to the connector 2 through the first power supply circuit in the on state, and no matter whether the module 1 is inserted or not, the standby power supply 5 can always supply power to certain circuits inside the connector 2. The specific structure of the first power supply circuit can be flexibly set by those skilled in the art, for example, the first power supply circuit can be a power line, as long as the first power supply circuit is in the on state.

[0093] In this embodiment, the specific structure of the second power supply circuit can be flexibly set by those skilled in the art. For example, the second power supply circuit can be a circuit with a control switch. When no power supply signal is received, the control switch is disconnected. When a power supply signal is received, the control switch is closed to turn on the circuit. The control switch can be set on the power module 4, or on the connector 2, or between the two.

[0094] In this implementation, the power supply signal can be flexibly set by those skilled in the art, as long as the power supply signal can control the conduction of the second power supply circuit, and no limitation is made here.

[0095] In this embodiment, the standby power supply signal power supply can be connected to the connector through the first power supply circuit in the on state, so that the standby power supply always supplies power to the connector, and supplies power to the first storage module of the module when the module is inserted into the connector. The connector can also be connected to the power module through the second power supply circuit in the off state. When the module is not inserted or the module standardization check fails, the power module cannot supply power to the connector and the module. Only when the module standardization check passes and the domain controller sends a power supply signal to the second power supply circuit, the second power supply circuit will be turned on to enable the power module to supply power to the connector, thereby enabling the module to be powered on globally. Through such a setting, it is possible to avoid the domain controller from malfunctioning or short-circuiting due to the insertion of a non-standard module into the connector, thereby improving the accuracy and safety of the connection between the module and the domain controller.

[0096] In a possible implementation, the connector 2 may also be connected to the standby power supply 5 via a signal path, and the signal path is used to transmit the high level signal generated by the standby power supply 5 to the connector 2, so that the pin between the connector 2 and the domain controller 3 is at a high level;

[0097] The module 1 is grounded, and when the module 1 is inserted into the connector 2, the pin can be changed from a high level to a low level, indicating a presence signal.

[0098] In this embodiment, the presence signal is a low level signal. When the domain controller 3 detects that the pin between the connector 2 and the domain controller 3 becomes a low level (presence signal), it can be confirmed that the module 1 has been inserted into the connector 2.

[0099] In this embodiment, the connector 2 and the domain controller 3 are connected via a pin. When the module 1 is not inserted into the connector 2, the existence of the signal path and the standby power supply 5 pulls the pin between the connector 2 and the domain controller 3 to a high level; when the module 1 is inserted into the connector 2, the grounded module 1 pulls the high-level pin down to a low level.

[0100] In this embodiment, the standby power supply can also provide a high-level signal to the connector through the signal path. When the module is inserted into the connector, the grounded module can pull the pin between the connector and the domain controller to a low level, thereby generating a presence signal. With such a setting, the domain controller can accurately detect that the module has been inserted into the connector based on the presence signal.

[0101] In a possible implementation, the standby power supply 5 may also be connected to the ground electrode GND through a discharge diode 6, and the discharge diode 6 is used to maintain a high impedance state when the standby power supply 5 works normally, and to be turned on when the standby power supply 5 is short-circuited to discharge the instantaneous current to the ground electrode.

[0102] In this embodiment, the discharge diode is a discharge TVS tube (Transient Voltage Suppression Diode, also called transient voltage suppression diode), which is a protective device used to protect electronic circuits from transient voltages (such as lightning strikes, power surges, etc.). The discharge diode is in a high-resistance state under normal operating voltage. When the transient voltage exceeds its breakdown voltage, the discharge diode quickly conducts and discharges the transient current to the ground, thereby protecting subsequent circuits.

[0103] In this embodiment, the standby power supply can also be connected to the ground electrode through a discharge diode. Even if a non-standard module is inserted into the connector and causes a short circuit in the standby power supply, the short-circuit current can be discharged through the discharge diode and will not cause a short circuit in the domain controller, further improving the security of the connection between the module and the domain controller.

[0104] Figure 3 This is a flow chart of a module connection method for an autonomous driving vehicle according to an embodiment of the present application. Figure 2 The domain controller in the embodiment of the present invention is used to describe the module connection method of the autonomous driving vehicle. The domain controller is provided with a connector, which is electrically connected to the standby power supply. Figure 3 As shown, the module connection method of the autonomous driving vehicle may include the following steps:

[0105] S301: In response to a presence signal generated by a module being inserted into a connector, obtaining information stored in a first storage module of the module.

[0106] In this embodiment, the standby power supply can be used to power the connector and to power the first storage module when the module is inserted into the connector.

[0107] In this embodiment, the domain controller may be a domain controller of the vehicle autonomous driving domain, or a domain controller of other domains such as the power domain, without any limitation.

[0108] It should be noted that the domain controller mentioned in this embodiment may specifically be an MCU of the domain controller.

[0109] In this embodiment, the connector may be disposed on the base of the domain controller, and the connector may be a mainstream Molex connector or other connectors, without any limitation herein.

[0110] In this embodiment, the module may include SOC, DDR, EMMC, power conversion module and other units, which can provide computing power for the autonomous driving process.

[0111] In this embodiment, the in-place signal may be a low-level signal generated on the connection pin between the connector and the domain controller when the module is inserted into the connector, or may be other signals without any limitation as long as it can indicate that the module is inserted into the connector.

[0112] In this embodiment, the standby power supply is connected to the connector, and always supplies power to certain circuits inside the connector regardless of whether a module is inserted. When the module is inserted into the connector, the standby power supply also supplies power to the first storage module of the module, ensuring that only the first storage module works normally, thereby avoiding the risk of short circuit caused by the inserted module being non-standard.

[0113] In this embodiment, control logic may be pre-stored in the register inside the module: when it is detected that the standby power supply is supplied, only the power supply path between the standby power supply and the first storage module of the module is turned on, that is, only the power-on of the first storage module is completed; when it is detected that the standby power supply and the power supply module are supplied together, the power supply path between the power supply module and the internal modules is turned on to achieve global power-on.

[0114] In this embodiment, when the module is inserted into the connector, the standby power supply can supply power to the first storage module of the module, and the domain controller can obtain relevant information from the first storage module that is working normally.

[0115] S302: Performing a standard check on the module according to the information stored in the first storage module.

[0116] S303: Determine whether the module is a standard module of the domain controller.

[0117] In this embodiment, the first storage module may be an Electrically-Erasable Programmable Read-Only Memory (EEPROM / E2PROM for short), or may be other types of storage modules, which are not limited herein.

[0118] In this embodiment, the standard module of the domain controller refers to a module produced by the same manufacturer as the domain controller and having a matching model.

[0119] S304: If the module is a standard module of the domain controller, a power supply signal is generated, and the power supply signal is used to control the power module of the domain controller to globally power on the module, and the supply voltage of the standby power supply is lower than the supply voltage of the power module.

[0120] In this embodiment, when the module is just inserted into the connector, the high-voltage power module in the domain controller will not supply power to the module and the connector. Only when it is determined that the module is a standard module of the domain controller will the domain controller control the power module of the domain controller to power on the module globally, so as to avoid the power module being connected to the ground signal when a non-standard module is inserted, causing a short circuit and damaging the domain controller.

[0121] In this embodiment, the power supply signal can be flexibly set by those skilled in the art, as long as the power supply signal can control the domain power module to globally power on the module, and no limitation is made here.

[0122] In this embodiment, the standby power supply is an independent low-voltage power supply, and the standby power supply can be a 3.3v low-voltage power supply, that is, a 3V3-stby power supply. The power supply module can be a power supply in the domain controller, which supplies power to components in the domain controller and devices connected to the domain controller, and the power supply module can be a 12V high-voltage power supply.

[0123] S305: If the module is not a standard module of the domain controller, a connection error prompt message is output.

[0124] In this embodiment, if the module is not a standard module of the domain controller, the domain controller does not generate a power supply signal, and the power module does not supply power to the module, so as to avoid the domain controller not being able to work properly or short-circuiting due to the non-standard module being inserted into the connector. At the same time, the domain controller also outputs a connection error prompt message to prompt the user to replace the inserted module in time.

[0125] In this embodiment, the connector can be electrically connected to the standby power supply, and an independent and low-voltage standby power supply is used to power the connector and the module, rather than the high-voltage power supply module in the domain controller, thereby avoiding the risk of short circuit caused by the insertion of an incompatible module into the connector. When the module is inserted into the connector, the standby power supply can only power the first storage module of the module, ensuring that only the storage module in the module can work normally, further avoiding the risk of short circuit when the inserted module is not a standard module, and improving the accuracy and safety of the connection between the module and the domain controller. Furthermore, when the domain controller detects the in-place signal generated by the module being inserted into the connector, the module can be checked for standardization based on the information stored in the first storage module to verify whether the module inserted into the connector is a standard module of the domain controller. Only when it is determined that the module is a standard module of the domain controller will the domain controller control the power module of the domain controller to globally power on the module and complete the connection between the module and the controller. Through such a setting, the information stored in the first storage module of the module can be used to perform standardization verification on the module, and global power-on control can only be performed on standard modules that have passed the verification, thereby avoiding the domain controller from malfunctioning or short-circuiting due to the insertion of non-standard modules into the connector, further improving the accuracy and security of the connection between the module and the domain controller, and ensuring that the domain controller can operate normally.

[0126] In a possible implementation, the information stored in the first storage module may include basic information of the first module. The above step S302 performs a standard check on the module according to the information stored in the first storage module to determine whether the module is a standard module of the domain controller, which may include:

[0127] S11: verifying the basic information of the module according to the basic information of the first module.

[0128] S12: If the basic information of the module passes the verification, a hash code verification is performed on the module to determine whether the module is a standard module.

[0129] S13: If the basic information verification of the module fails, it is determined that the module is not a standard module of the domain controller.

[0130] In this implementation, the domain controller may obtain the basic information of the first module stored in the first storage module through the management channel. The basic information of the first module may have been stored in the first storage module when the module leaves the factory.

[0131] In this embodiment, if the module is not a standard module of the domain controller, the domain controller does not send a power supply signal, and the module will not be powered on by the power module. At this time, the domain controller can output an alarm prompt message to prompt the user that the module is connected incorrectly.

[0132] In this embodiment, when the module is checked for standardization, the basic information check and the hash code check can be performed on the module in sequence. The basic information can be used to check whether the basic information of the inserted module is accurate, that is, to perform hardware verification; the hash code can be used to check whether the version of the inserted module, the debugged program, etc. are accurate, that is, to perform software verification, thereby comprehensively and accurately determining whether the module is a standard module of the domain controller.

[0133] In a possible implementation manner, if the module basic information verification fails, the following may also be included:

[0134] The first connection error prompt information is generated and output according to the first module basic information, and the first connection error prompt information is used to prompt that the module basic information verification fails.

[0135] In this implementation, the first connection error prompt information may include basic information of the non-standard module to prompt the user of the specific model of the non-standard module.

[0136] Alternatively, the first connection error prompt information may be generated and output according to the basic information of the standard module preset in the domain controller to prompt the user of the specific model of the standard module.

[0137] In this implementation, the domain controller may output the first connection error prompt information through the serial port.

[0138] In this embodiment, if the basic information verification of the module fails, the domain controller may generate and output a first connection error prompt message to prompt the user that the model of the module is inaccurate and the module needs to be replaced in time.

[0139] In a possible implementation, the step S11 of verifying the basic information of the module according to the basic information of the first module may include:

[0140] S21: Obtain basic information of the second module pre-stored in the second storage module of the domain controller, where the basic information of the module includes manufacturer information, module model information, and serial number.

[0141] S22: Determine whether the first module basic information is consistent with the second module basic information.

[0142] S23: If they are consistent, it is determined that the module basic information verification has passed.

[0143] S24: If they are inconsistent, it is determined that the module basic information verification has failed.

[0144] In this implementation, the second storage module of the domain controller may be a FLASH flash memory module or other types of storage modules, and no limitation is made here.

[0145] In this embodiment, the second storage module of the domain controller may pre-store basic information of the standard module corresponding to the domain controller, that is, the second module basic information. The second module basic information may be stored in the second storage module using a register.

[0146] In this implementation, those skilled in the art may flexibly set the specific basic information of the module, and is not limited to the above types, as long as the basic information of the module can identify different modules.

[0147] In this embodiment, by comparing the first module basic information stored in the module with the second module basic information pre-stored in the domain controller, the basic information of the module can be simply and accurately verified to determine whether the module and the domain controller are hardware compatible.

[0148] In a possible implementation manner, the hash code verification of the module in the above step S12 to determine whether the module is a standard module includes:

[0149] S31: Obtain a module hash code stored in a first storage module of the module, and obtain a hash code pool pre-stored in a second storage module of the domain controller.

[0150] S32: Determine whether there is a target hash code in the hash code pool that is consistent with the module hash code.

[0151] S33: If it exists, determine that the module is a standard module of the domain controller.

[0152] S34: If it does not exist, it is determined that the module is not a standard module of the domain controller, and a second connection error prompt message is output, where the second connection error prompt message is used to prompt that the module hash code verification has failed and the module hash code is wrong.

[0153] In this embodiment, the factory-produced module is a universal module. To connect to the domain controller, it needs to be debugged according to the version, firmware program, etc. of the domain controller to adapt to the program of the domain controller. After the module debugging is completed, the staff can use the MD5 tool to randomly generate a 128-bit hash code (MD5 code) and store the hash code as the module hash code in the first storage module of the module. The staff will also randomly generate multiple 128-bit hash codes and store the multiple hash codes in the hash code pool of the second storage module.

[0154] In this embodiment, if there is a target hash code consistent with the module hash code in the hash code pool, it means that the module has been debugged and is compatible with the program in the domain controller, and the module can work normally after connecting to the domain controller; if there is no target hash code consistent with the module hash code in the hash code pool, it means that the module program is wrong and is incompatible with the program in the domain controller, and the module cannot work normally after connecting to the domain controller.

[0155] In this embodiment, if there is no target hash code consistent with the module hash code in the hash code pool, the domain controller can output a second connection error prompt message through the serial port to prompt the user that the module program is wrong and needs to be re-debugged or replaced with a new module.

[0156] In this embodiment, by comparing the module hash code stored in the module with multiple hash codes in the hash code pool of the domain controller, the hash code of the module can be simply and accurately verified to determine whether the module and the domain controller are software compatible.

[0157] In a possible implementation manner, before obtaining the module hash code stored in the first storage module of the module, the following may also be included:

[0158] S41: Determine whether a module hash code exists in the first storage module of the module.

[0159] S42: If it exists, execute the step of obtaining the module hash code stored in the first storage module of the module.

[0160] S43: If it does not exist, it is determined that the module is not a standard module of the domain controller, and a third connection error prompt message is output, where the third connection error prompt message is used to prompt that the module hash code verification has failed and the module hash code does not exist.

[0161] In this embodiment, if it does not exist, it means that the module has not been debugged, and the module cannot work normally after connecting to the domain controller. The domain controller can output a third connection error prompt message through the serial port to prompt the user that the module program is debugged and the module program needs to be debugged.

[0162] In this embodiment, before obtaining the module hash code of the module, it is also necessary to determine whether the module hash code exists in the first storage module of the module to determine whether the inserted module has been debugged. If the module hash code does not exist, it means that the module is still a general module and cannot be used without program debugging, thereby comprehensively verifying whether the module and the domain controller are software compatible.

[0163] The module connection method of the autonomous driving vehicle of the present application is described below with a specific embodiment.

[0164] In a specific embodiment, a staff member needs to connect a SOC module to a domain controller of an autonomous driving domain of an autonomous driving vehicle. A molex connector is provided on the base of the domain controller. The molex connector is connected to a 3V3-stby power supply. The 3V3-stby power supply supplies power to the molex connector and provides a high-level signal to the molex connector through a signal circuit. The molex connector is also connected to a power module of the domain controller through a second power supply circuit, and the second power supply circuit is in a disconnected state.

[0165] The EEPROM of the SOC module includes the first basic information of the module, such as the manufacturer information, module model information and serial number of the module, and the SOC module is grounded. The FLASH of the domain controller includes the second basic information of the corresponding standard module, such as the manufacturer information, module model information and serial number.

[0166] The specific module connection process is as follows:

[0167] In the first step, the staff debugs the SOC module program and randomly generates a module hash code after debugging, and stores the module hash code in the SOC module's EEPROM. The staff also randomly generates multiple hash codes and stores them in the domain controller's FLASH.

[0168] In the second step, the staff inserts the SOC module into the connector. The grounded SOC module pulls the pin between the connector and the domain controller to a low level, thereby generating a presence signal. The 3V3-stby power supply powers the EEPROM of the SOC module.

[0169] In the third step, the domain controller detects a low-level signal, obtains the basic information of the first module stored in the EEPROM of the SOC module, and compares the basic information of the first module with the basic information of the second module stored in the FLASH of the domain controller. If the two are consistent, the basic information verification of the SOC module passes.

[0170] In the fourth step, the domain controller obtains the module hash code stored in the EEPROM of the SOC module, and compares the module hash code with multiple hash codes stored in the FLASH of the domain controller. If it is determined that there is a target hash code in the FLASH that is consistent with the module hash code, the SOC module hash code verification passes.

[0171] In the fifth step, the domain controller generates a power supply signal and sends the power supply signal to the second power supply circuit. After receiving the power supply signal, the second power supply circuit switches to the on state so that the power module of the domain controller powers on the SOC module globally, completing the connection between the SOC module and the domain controller.

[0172] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0173] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0174] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0175] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0176] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0177] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the appended claims.

[0178] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A module connection method for an autonomous driving vehicle, characterized in that: Applied to a domain controller, the domain controller is provided with a connector, the connector is electrically connected to a standby power supply, the standby power supply is used to supply power to the connector, the method comprises: In response to a presence signal generated by the module being inserted into the connector, information stored in a first storage module of the module is acquired, wherein the standby power supply is also used to supply power to the first storage module when the module is inserted into the connector; Performing a standardization check on the module according to the information stored in the first storage module to determine whether the module is a standard module of the domain controller; If the module is a standard module of the domain controller, a power supply signal is generated, and the power supply signal is used to control the power module of the domain controller to globally power on the module, and the supply voltage of the standby power supply is lower than the supply voltage of the power module.

2. The module connection method of the autonomous driving vehicle according to claim 1, characterized in that: The information stored in the first storage module includes basic information of the first module, and the standardization check of the module is performed according to the information stored in the first storage module to determine whether the module is a standard module of the domain controller, including: Performing basic information verification on the module according to the basic information of the first module; If the basic information verification of the module passes, performing a hash code verification on the module to determine whether the module is a standard module; If the basic information verification of the module fails, it is determined that the module is not a standard module of the domain controller.

3. The module connection method of the autonomous driving vehicle according to claim 2, characterized in that: If the basic information verification of the module fails, the following further includes: Generate and output first connection error prompt information according to the first module basic information, where the first connection error prompt information is used to prompt that verification of the module basic information has failed.

4. The module connection method of the autonomous driving vehicle according to claim 2, characterized in that: The step of verifying basic information of the module according to the basic information of the first module includes: Acquire basic information of the second module pre-stored in the second storage module of the domain controller, wherein the basic information of the module includes manufacturer information, module model information and serial number; Determining whether the first module basic information is consistent with the second module basic information; If they are consistent, it is determined that the basic information verification of the module has passed; If they are inconsistent, it is determined that the module basic information verification has failed.

5. The module connection method of the autonomous driving vehicle according to claim 2, characterized in that: The performing hash code verification on the module to determine whether the module is a standard module includes: Obtaining a module hash code stored in a first storage module of the module, and obtaining a hash code pool pre-stored in a second storage module of the domain controller; Determine whether there is a target hash code consistent with the module hash code in the hash code pool; If so, determining that the module is a standard module of the domain controller; If not, it is determined that the module is not a standard module of the domain controller, and a second connection error prompt message is output, where the second connection error prompt message is used to prompt that the module hash code verification has failed and the module hash code is wrong.

6. The module connection method of the autonomous driving vehicle according to claim 5, characterized in that: Before obtaining the module hash code stored in the first storage module of the module, the method further includes: Determining whether a module hash code exists in a first storage module of the module; If so, executing the step of obtaining the module hash code stored in the first storage module of the module; If not, it is determined that the module is not a standard module of the domain controller, and a third connection error prompt message is output, where the third connection error prompt message is used to prompt that the module hash code verification has failed and the module hash code does not exist.

7. A module connection system for an autonomous driving vehicle, characterized in that: include: The domain controller according to any one of claims 1 to 6, wherein the domain controller is provided with a connector, and the connector is electrically connected to the standby power supply; The standby power supply is used to supply power to the connector and to supply power to the first storage module of the module when the module is inserted into the connector; The connector is used to generate a presence signal when the module is inserted and connect the module and the domain controller; The domain controller is used to obtain information stored in the first storage module of the module in response to a presence signal generated by the module being inserted into the connector; Performing a standardization check on the module according to the information stored in the first storage module to determine whether the module is a standard module of the domain controller; If the module is a standard module of the domain controller, a power supply signal is generated, and the power supply signal is used to control the power module of the domain controller to globally power on the module, and the supply voltage of the standby power supply is lower than the supply voltage of the power module.

8. The module connection system for an autonomous driving vehicle according to claim 7, characterized in that: The connector is connected to the standby power supply through a first power supply circuit, and the first power supply circuit is in a conducting state, so that the standby power supply supplies power to the connector through the first power supply circuit, and when the module is inserted into the connector, the connector and the first storage module of the module are supplied with power through the first power supply circuit; The connector is also connected to the power module through a second power supply circuit, and the second power supply circuit is in a disconnected state; the power supply signal is specifically used to control the conduction of the second power supply circuit, so that the power module powers on the module globally through the second power supply circuit and the connector in sequence.

9. The module connection system for an autonomous driving vehicle according to claim 8, characterized in that: The connector is also connected to the standby power supply via a signal path, and the signal path is used to transmit a high level signal generated by the standby power supply to the connector, so that the pin between the connector and the domain controller is at a high level; The module is grounded, and when the module is inserted into the connector, the pin is changed from a high level to a low level, indicating a presence signal.

10. The module connection system for an autonomous driving vehicle according to claim 9, characterized in that: The standby power supply is also connected to the ground electrode through a discharge diode, and the discharge diode is used to maintain a high impedance state when the standby power supply works normally, and to be turned on when the standby power supply is short-circuited to discharge the instantaneous current to the ground electrode.

Images