In-vehicle Ethernet diagnostic device and in-vehicle Ethernet diagnostic method

Abstract

The invention provides vehicle-mounted Ethernet diagnosis equipment and a vehicle-mounted Ethernet diagnosis method, and relates to the technical field of automatic driving, in particular to the technical field of vehicle-mounted Ethernet diagnosis. The vehicle-mounted Ethernet diagnostic equipment comprises a first vehicle-mounted Ethernet physical layer chip, a second vehicle-mounted Ethernet physical layer chip and a controller, the first vehicle-mounted Ethernet physical layer chip is connected with the automatic driving sensor and is used for storing a first connection state of the first vehicle-mounted Ethernet physical layer chip and the automatic driving sensor; the second vehicle-mounted Ethernet physical layer chip is connected with the automatic driving domain controller and is used for storing a second connection state of the second vehicle-mounted Ethernet physical layer chip and the automatic driving domain controller; the controller is connected between the first vehicle-mounted Ethernet physical layer chip and the second vehicle-mounted Ethernet physical layer chip and used for monitoring the first connection state and the second connection state and generating vehicle-mounted Ethernet diagnostic information.

Description

Technical Field

[0001] The present disclosure relates to the field of autonomous driving technology, and more particularly to the field of vehicle-mounted Ethernet diagnostic technology. Background Art

[0002] Ethernet diagnostic testing is a physical layer test that must be performed on vehicle Ethernet controllers. Most OEMs use manual testing to test Ethernet diagnostics, which has low test efficiency and large errors in test results. Summary of the invention

[0003] The embodiments of the present disclosure provide an in-vehicle Ethernet diagnostic device and an in-vehicle Ethernet diagnostic method, apparatus, device, storage medium, and program product.

[0004] In a first aspect, an embodiment of the present disclosure proposes an on-vehicle Ethernet diagnostic device, including: a first on-vehicle Ethernet physical layer chip, a second on-vehicle Ethernet physical layer chip and a controller; the first on-vehicle Ethernet physical layer chip is connected to an autonomous driving sensor, and is used to store a first connection state between the first on-vehicle Ethernet physical layer chip and the autonomous driving sensor; the second on-vehicle Ethernet physical layer chip is connected to an autonomous driving domain controller, and is used to store a second connection state between the second on-vehicle Ethernet physical layer chip and the autonomous driving domain controller; the controller is connected between the first on-vehicle Ethernet physical layer chip and the second on-vehicle Ethernet physical layer chip, and is used to monitor the first connection state and the second connection state, and generate on-vehicle Ethernet diagnostic information.

[0005] In a second aspect, an embodiment of the present disclosure proposes a vehicle Ethernet diagnostic method, including: monitoring a first connection state stored in a first vehicle Ethernet physical layer chip and a second connection state stored in a second vehicle Ethernet physical layer chip, wherein the first connection state is a connection state between the first vehicle Ethernet physical layer chip and an autonomous driving sensor, and the second connection state is a connection state between the second vehicle Ethernet physical layer chip and an autonomous driving domain controller; based on the first connection state and the second connection state, generating vehicle Ethernet diagnostic information.

[0006] In a third aspect, an embodiment of the present disclosure proposes an on-board Ethernet diagnostic device, comprising: a monitoring module, configured to monitor a first connection state stored in a first on-board Ethernet physical layer chip and a second connection state stored in a second on-board Ethernet physical layer chip, wherein the first connection state is a connection state between the first on-board Ethernet physical layer chip and an autonomous driving sensor, and the second connection state is a connection state between the second on-board Ethernet physical layer chip and an autonomous driving domain controller; a generation module, configured to generate on-board Ethernet diagnostic information based on the first connection state and the second connection state.

[0007] In a fourth aspect, an embodiment of the present disclosure proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method described in the first aspect.

[0008] In a fifth aspect, an embodiment of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to cause a computer to execute the method described in the first aspect.

[0009] In a sixth aspect, an embodiment of the present disclosure proposes a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor. An embodiment of the present disclosure proposes an on-board Ethernet diagnostic device, which is inserted between an autonomous driving sensor and an autonomous driving domain controller, and is suitable for signal relay of an on-board Ethernet device for autonomous driving, which enhances the transmission signal strength and extends the transmission distance. The design can reserve a margin, thereby ensuring high communication quality and reliability. The controller can monitor the first connection state and the second connection state to implement diagnosis of the physical layer of the on-board Ethernet device. Moreover, it can quickly locate whether the fault is on the autonomous driving sensor side or the autonomous driving domain controller side.

[0010] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Other features, purposes and advantages of the present disclosure will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings. The drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure. Among them:

[0012] Figure 1 is a structural schematic diagram of a first embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure;

[0013] Figure 2 is a structural schematic diagram of a second embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure;

[0014] Figure 3 is a structural schematic diagram of a third embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure;

[0015] Figure 4 is a structural schematic diagram of a fourth embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure;

[0016] Figure 5is a flow chart of an embodiment of a vehicle Ethernet diagnostic method according to the present disclosure;

[0017] Figure 6 is a structural schematic diagram of an embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure;

[0018] Figure 7 It is a block diagram of an electronic device used to implement the vehicle Ethernet diagnostic method of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0019] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0020] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0021] Figure 1 A schematic structural diagram of a first embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure is shown.

[0022] like Figure 1 As shown, the vehicle Ethernet diagnostic device 100 may include a first vehicle Ethernet physical layer chip 101 , a second vehicle Ethernet physical layer chip 102 and a controller 103 .

[0023] The first vehicle Ethernet physical layer chip 101 is connected to the autonomous driving sensor 200. The second vehicle Ethernet physical layer chip 102 is connected to the autonomous driving domain controller 300. The controller 103 is connected between the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102.

[0024] The on-board Ethernet harness on an autonomous driving vehicle is usually relatively long, and the signal attenuation on it is relatively large. In particular, the length of the vehicle body of an autonomous driving truck or autonomous driving bus is relatively long, and the wiring length usually exceeds or is close to the requirement of 15 meters for the on-board Ethernet. The increase in the length of the harness and the number of connectors will lead to a deterioration in the insertion loss and return loss parameters, thereby increasing the probability of communication failure. In order to eliminate this effect, an on-board Ethernet diagnostic device 100 can be inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. After adding the on-board Ethernet diagnostic device 100, the theoretical transmission distance will be improved (such as doubled), which is suitable for the signal relay of the on-board Ethernet device for autonomous driving, enhancing the transmission signal strength and extending the transmission distance. The design can reserve a margin to ensure higher communication quality and reliability.

[0025] The autonomous driving sensor 200 may be any sensor on the autonomous driving vehicle, including but not limited to: a laser radar, a camera, etc. The autonomous driving sensor 200 may collect sensor data and transmit it to the autonomous driving domain controller 300. The autonomous driving domain controller 300 may generate control instructions based on the sensor data to control the driving of the autonomous driving vehicle.

[0026] The sensor data collected by the autonomous driving sensor 200 can be transmitted to the autonomous driving domain controller 300 through the first vehicle Ethernet physical layer chip 101, the controller 103 and the second vehicle Ethernet physical layer chip 102 in sequence. Therefore, the first vehicle Ethernet physical layer chip 101 can determine the first connection state between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200 based on the sensor data it receives. The first connection state can be stored in a register therein. Similarly, the second vehicle Ethernet physical layer chip 102 can determine the second connection state between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300 based on the sensor data it transmits. The second connection state can be stored in a register therein.

[0027] The controller 103 can monitor the first connection state and the second connection state, and generate vehicle Ethernet diagnostic information according to the first connection state and the second connection state. Specifically, by reading the registers of the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102, the first connection state and the second connection state can be obtained in real time, thereby realizing the diagnosis of the physical layer of the vehicle Ethernet device. If the first connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving sensor 200; if the second connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving domain controller 300. Among them, the Ethernet diagnostic information can be a diagnosis of the physical layer of the vehicle Ethernet device, including but not limited to the open and short circuit diagnosis of the wiring harness, the diagnosis of whether the physical layer is disconnected, the diagnosis of whether a CRC (Cyclic Redundancy Check) error occurs, and the like.

[0028] In some embodiments, the controller 103 may periodically (eg, every 1 second) access the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102 , thereby implementing real-time diagnosis of the physical layer of the vehicle Ethernet device.

[0029] The disclosed embodiment proposes an on-board Ethernet diagnostic device, which is inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. The on-board Ethernet diagnostic device 100 is suitable for the signal relay of the on-board Ethernet device of autonomous driving, and the transmission signal strength is enhanced to extend the transmission distance. The design can reserve a margin to ensure high communication quality and reliability. The controller 103 can monitor the first connection state and the second connection state to realize the diagnosis of the physical layer of the on-board Ethernet device. In addition, it can quickly locate whether the fault is on the autonomous driving sensor 200 side or the autonomous driving domain controller 300 side.

[0030] Figure 2 A schematic structural diagram of a second embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure is shown.

[0031] like Figure 2 As shown, the vehicle Ethernet diagnostic device 100 may include a first vehicle Ethernet physical layer chip 101 , a second vehicle Ethernet physical layer chip 102 , a controller 103 , a first connector 104 and a second connector 105 .

[0032] The first connector 104 is connected between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200, thereby realizing data transmission between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200. The second connector 105 is connected between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300, thereby realizing data transmission between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300. The controller 103 is connected between the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102. In addition, the first vehicle Ethernet physical layer chip 101 is connected to the second vehicle Ethernet physical layer chip 102, and communicates through the SGMII (Gigabit Media Independent Interface) protocol, thereby realizing data transmission between the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102.

[0033] The on-board Ethernet harness on an autonomous driving vehicle is usually relatively long, and the signal attenuation on it is relatively large. In particular, the length of the vehicle body of an autonomous driving truck or autonomous driving bus is relatively long, and the wiring length usually exceeds or is close to the requirement of 15 meters for the on-board Ethernet. The increase in the length of the harness and the number of connectors will lead to a deterioration in the insertion loss and return loss parameters, thereby increasing the probability of communication failure. In order to eliminate this effect, an on-board Ethernet diagnostic device 100 can be inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. After adding the on-board Ethernet diagnostic device 100, the theoretical transmission distance will be improved (such as doubled), which is suitable for the signal relay of the on-board Ethernet device for autonomous driving, enhancing the transmission signal strength and extending the transmission distance. The design can reserve a margin to ensure higher communication quality and reliability.

[0034] The autonomous driving sensor 200 may be any sensor on the autonomous driving vehicle, including but not limited to: a laser radar, a camera, etc. The autonomous driving sensor 200 may collect sensor data and transmit it to the autonomous driving domain controller 300. The autonomous driving domain controller 300 may generate control instructions based on the sensor data to control the driving of the autonomous driving vehicle.

[0035] The sensor data collected by the autonomous driving sensor 200 can be transmitted to the autonomous driving domain controller 300 through the first vehicle Ethernet physical layer chip 101, the controller 103 and the second vehicle Ethernet physical layer chip 102 in sequence. Therefore, the first vehicle Ethernet physical layer chip 101 can determine the first connection state between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200 based on the sensor data it receives. The first connection state can be stored in a register therein. Similarly, the second vehicle Ethernet physical layer chip 102 can determine the second connection state between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300 based on the sensor data it transmits. The second connection state can be stored in a register therein.

[0036] The controller 103 can monitor the first connection state and the second connection state, and generate vehicle Ethernet diagnostic information according to the first connection state and the second connection state. Specifically, by reading the registers of the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102, the first connection state and the second connection state can be obtained in real time, thereby realizing the diagnosis of the physical layer of the vehicle Ethernet device. If the first connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving sensor 200; if the second connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving domain controller 300. Among them, the Ethernet diagnostic information can be a diagnosis of the physical layer of the vehicle Ethernet device, including but not limited to the open and short circuit diagnosis of the wiring harness, the diagnosis of whether the physical layer is disconnected, the diagnosis of whether a CRC error occurs, and so on.

[0037] The autonomous driving sensor 200 can collect sensor data and transmit it to the autonomous driving domain controller 300, so that the autonomous driving domain controller 300 controls the driving of the autonomous driving vehicle based on the sensor data. The specific steps are as follows:

[0038] The first connector 104 is connected to the autonomous driving sensor 200 via a first wiring harness, and sensor data can be transmitted from the autonomous driving sensor 200 to the first vehicle-mounted Ethernet physical layer chip 101 .

[0039] The first vehicle Ethernet physical layer chip 101 is connected to the second vehicle Ethernet physical layer chip 102 , and can transmit sensor data to the second vehicle Ethernet physical layer chip 102 .

[0040] The second connector 105 is connected to the autonomous driving domain controller 300 via a second wiring harness, and sensor data can be transmitted from the second on-board Ethernet physical layer chip 102 to the autonomous driving domain controller 300 .

[0041] In some embodiments, the autonomous driving domain controller 200 may send an event instruction to the controller 103 when the received sensor data is abnormal. The controller 103 may be used to access the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102 in response to the event instruction, thereby achieving timely diagnosis of the physical layer of the vehicle Ethernet device.

[0042] The autonomous driving domain controller 300 may transmit the sensor configuration data to the autonomous driving sensor 200, so that the autonomous driving sensor 200 performs relevant configurations based on the sensor configuration data. The specific steps are as follows:

[0043] The second connector 105 is connected to the autonomous driving domain controller 300 via a second wiring harness, and the sensor configuration information can be transmitted from the autonomous driving domain controller 300 to the second on-board Ethernet physical layer chip 102 .

[0044] The second vehicle-mounted Ethernet physical layer chip 102 is connected to the first vehicle-mounted Ethernet physical layer chip 101 , and can transmit sensor configuration information to the first vehicle-mounted Ethernet physical layer chip 101 .

[0045] The first connector 104 is connected to the autonomous driving sensor 200 via a first wiring harness, and the sensor configuration information can be transmitted from the first vehicle-mounted Ethernet physical layer chip 101 to the autonomous driving sensor 200 .

[0046] The disclosed embodiment proposes an on-board Ethernet diagnostic device, which is inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. The on-board Ethernet diagnostic device 100 is suitable for the signal relay of the on-board Ethernet device of autonomous driving, and the transmission signal strength is enhanced to extend the transmission distance. The design can reserve a margin to ensure high communication quality and reliability. The controller 103 can monitor the first connection state and the second connection state to realize the diagnosis of the physical layer of the on-board Ethernet device. In addition, it can quickly locate whether the fault is on the autonomous driving sensor 200 side or the autonomous driving domain controller 300 side.

[0047] Figure 3 A schematic structural diagram of a third embodiment of an in-vehicle Ethernet diagnostic device according to the present disclosure is shown.

[0048] like Figure 3 As shown, the vehicle Ethernet diagnostic device 100 may include a first vehicle Ethernet physical layer chip 101 , a second vehicle Ethernet physical layer chip 102 , a controller 103 , a first connector 104 , a second connector 105 , a first power supply module 106 and a second power supply module 107 .

[0049] The first connector 104 is connected between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200, thereby realizing data transmission between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200. The second connector 105 is connected between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300, thereby realizing data transmission between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300. The controller 103 is connected between the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102. In addition, the first vehicle Ethernet physical layer chip 101 is connected to the second vehicle Ethernet physical layer chip 102, and communicates through the SGMII protocol, thereby realizing data transmission between the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102. The first power supply module 106 is connected to the first connector 104. The second power supply module 107 is connected to the second connector 105.

[0050] The on-board Ethernet harness on an autonomous driving vehicle is usually relatively long, and the signal attenuation on it is relatively large. In particular, the length of the vehicle body of an autonomous driving truck or autonomous driving bus is relatively long, and the wiring length usually exceeds or is close to the requirement of 15 meters for the on-board Ethernet. The increase in the length of the harness and the number of connectors will lead to a deterioration in the insertion loss and return loss parameters, thereby increasing the probability of communication failure. In order to eliminate this effect, an on-board Ethernet diagnostic device 100 can be inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. After adding the on-board Ethernet diagnostic device 100, the theoretical transmission distance will be improved (such as doubled), which is suitable for the signal relay of the on-board Ethernet device for autonomous driving, enhancing the transmission signal strength and extending the transmission distance. The design can reserve a margin to ensure higher communication quality and reliability.

[0051] The autonomous driving sensor 200 may be any sensor on the autonomous driving vehicle, including but not limited to: a laser radar, a camera, etc. The autonomous driving sensor 200 may collect sensor data and transmit it to the autonomous driving domain controller 300. The autonomous driving domain controller 300 may generate control instructions based on the sensor data to control the driving of the autonomous driving vehicle.

[0052] The sensor data collected by the autonomous driving sensor 200 can be transmitted to the autonomous driving domain controller 300 through the first vehicle Ethernet physical layer chip 101, the controller 103 and the second vehicle Ethernet physical layer chip 102 in sequence. Therefore, the first vehicle Ethernet physical layer chip 101 can determine the first connection state between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200 based on the sensor data it receives. The first connection state can be stored in a register therein. Similarly, the second vehicle Ethernet physical layer chip 102 can determine the second connection state between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300 based on the sensor data it transmits. The second connection state can be stored in a register therein.

[0053] The controller 103 can monitor the first connection state and the second connection state, and generate vehicle Ethernet diagnostic information according to the first connection state and the second connection state. Specifically, by reading the registers of the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102, the first connection state and the second connection state can be obtained in real time, thereby realizing the diagnosis of the physical layer of the vehicle Ethernet device. If the first connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving sensor 200; if the second connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving domain controller 300. Among them, the Ethernet diagnostic information can be a diagnosis of the physical layer of the vehicle Ethernet device, including but not limited to the open and short circuit diagnosis of the wiring harness, the diagnosis of whether the physical layer is disconnected, the diagnosis of whether a CRC error occurs, and so on.

[0054] The autonomous driving sensor 200 can collect sensor data and transmit it to the autonomous driving domain controller 300, so that the autonomous driving domain controller 300 controls the driving of the autonomous driving vehicle based on the sensor data. The specific steps are as follows:

[0055] The first connector 104 is connected to the autonomous driving sensor 200 via a first wiring harness, and sensor data can be transmitted from the autonomous driving sensor 200 to the first vehicle-mounted Ethernet physical layer chip 101 .

[0056] The first vehicle Ethernet physical layer chip 101 is connected to the second vehicle Ethernet physical layer chip 102 , and can transmit sensor data to the second vehicle Ethernet physical layer chip 102 .

[0057] The second connector 105 is connected to the autonomous driving domain controller 300 via a second wiring harness, and sensor data can be transmitted from the second on-board Ethernet physical layer chip 102 to the autonomous driving domain controller 300 .

[0058] The autonomous driving domain controller 300 may transmit the sensor configuration data to the autonomous driving sensor 200, so that the autonomous driving sensor 200 performs relevant configurations based on the sensor configuration data. The specific steps are as follows:

[0059] The second connector 105 is connected to the autonomous driving domain controller 300 via a second wiring harness, and the sensor configuration information can be transmitted from the autonomous driving domain controller 300 to the second on-board Ethernet physical layer chip 102 .

[0060] The second vehicle-mounted Ethernet physical layer chip 102 is connected to the first vehicle-mounted Ethernet physical layer chip 101 , and can transmit sensor configuration information to the first vehicle-mounted Ethernet physical layer chip 101 .

[0061] The first connector 104 is connected to the autonomous driving sensor 200 via a first wiring harness, and the sensor configuration information can be transmitted from the first vehicle-mounted Ethernet physical layer chip 101 to the autonomous driving sensor 200 .

[0062] The first power supply module 106 is connected to the first connector 104, and can obtain power from the device and power the autonomous driving sensor 200. The second power supply module 107 is connected to the second connector 105, and is used to obtain power from the autonomous driving domain controller 300 and power the device. The power supply can be provided through the PODL (power on data line) function of the vehicle Ethernet or by using multiple wire cores in a wiring harness, without the need for additional power supply, and the design cost is lower.

[0063] The disclosed embodiment proposes an on-board Ethernet diagnostic device, which is inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. The on-board Ethernet diagnostic device 100 is suitable for signal relay of the on-board Ethernet device of autonomous driving, and the transmission signal strength is enhanced to extend the transmission distance. The design can reserve a margin, thereby ensuring high communication quality and reliability. The controller 103 can monitor the first connection state and the second connection state to realize the diagnosis of the physical layer of the on-board Ethernet device. In addition, it can quickly locate whether the fault is on the side of the autonomous driving sensor 200 or the side of the autonomous driving domain controller 300. The power supply can be provided by the PODL function of the on-board Ethernet or by using a power supply method of multiple cores in a wiring harness, without the need for additional power supply, and the design cost is lower.

[0064] Figure 4 A structural schematic diagram of a fourth embodiment of the in-vehicle Ethernet diagnostic device according to the present disclosure is shown.

[0065] like Figure 4As shown, the on-board Ethernet diagnostic device 100 may include a first on-board Ethernet physical layer chip 101, a second on-board Ethernet physical layer chip 102, a controller 103, a first connector 104, a second connector 105, a first power supply module 106, a second power supply module 107, a wireless communication module 108, an antenna module 109, a storage module 110 and a fault indication module 111.

[0066] The first connector 104 is connected between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200, thereby realizing data transmission between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200. The second connector 105 is connected between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300, thereby realizing data transmission between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300. The controller 103 is connected between the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102. In addition, the first vehicle Ethernet physical layer chip 101 is connected to the second vehicle Ethernet physical layer chip 102, and communicates through the SGMII protocol, thereby realizing data transmission between the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102. The first power supply module 106 is connected to the first connector 104. The second power supply module 107 is connected to the second connector 105. The wireless communication module 108 is connected to the controller 103. The antenna module 109 is connected to the wireless communication module 108. The storage module 110 is connected to the controller 103. The fault indication module 111 is connected to the controller 103 .

[0067] The on-board Ethernet harness on an autonomous driving vehicle is usually relatively long, and the signal attenuation on it is relatively large. In particular, the length of the vehicle body of an autonomous driving truck or autonomous driving bus is relatively long, and the wiring length usually exceeds or is close to the requirement of 15 meters for the on-board Ethernet. The increase in the length of the harness and the number of connectors will lead to a deterioration in the insertion loss and return loss parameters, thereby increasing the probability of communication failure. In order to eliminate this effect, an on-board Ethernet diagnostic device 100 can be inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. After adding the on-board Ethernet diagnostic device 100, the theoretical transmission distance will be improved (such as doubled), which is suitable for the signal relay of the on-board Ethernet device for autonomous driving, enhancing the transmission signal strength and extending the transmission distance. The design can reserve a margin to ensure higher communication quality and reliability.

[0068] The autonomous driving sensor 200 may be any sensor on the autonomous driving vehicle, including but not limited to: a laser radar, a camera, etc. The autonomous driving sensor 200 may collect sensor data and transmit it to the autonomous driving domain controller 300. The autonomous driving domain controller 300 may generate control instructions based on the sensor data to control the driving of the autonomous driving vehicle.

[0069] The sensor data collected by the autonomous driving sensor 200 can be transmitted to the autonomous driving domain controller 300 through the first vehicle Ethernet physical layer chip 101, the controller 103 and the second vehicle Ethernet physical layer chip 102 in sequence. Therefore, the first vehicle Ethernet physical layer chip 101 can determine the first connection state between the first vehicle Ethernet physical layer chip 101 and the autonomous driving sensor 200 based on the sensor data it receives. The first connection state can be stored in a register therein. Similarly, the second vehicle Ethernet physical layer chip 102 can determine the second connection state between the second vehicle Ethernet physical layer chip 102 and the autonomous driving domain controller 300 based on the sensor data it transmits. The second connection state can be stored in a register therein.

[0070] The controller 103 can monitor the first connection state and the second connection state, and generate vehicle Ethernet diagnostic information according to the first connection state and the second connection state. Specifically, by reading the registers of the first vehicle Ethernet physical layer chip 101 and the second vehicle Ethernet physical layer chip 102, the first connection state and the second connection state can be obtained in real time, thereby realizing the diagnosis of the physical layer of the vehicle Ethernet device. If the first connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving sensor 200; if the second connection state is abnormal, it can be determined that the fault is on the side of the autonomous driving domain controller 300. Among them, the Ethernet diagnostic information can be a diagnosis of the physical layer of the vehicle Ethernet device, including but not limited to the open and short circuit diagnosis of the wiring harness, the diagnosis of whether the physical layer is disconnected, the diagnosis of whether a CRC error occurs, and so on.

[0071] The autonomous driving sensor 200 can collect sensor data and transmit it to the autonomous driving domain controller 300, so that the autonomous driving domain controller 300 controls the driving of the autonomous driving vehicle based on the sensor data. The specific steps are as follows:

[0072] The first connector 104 is connected to the autonomous driving sensor 200 via a first wiring harness, and sensor data can be transmitted from the autonomous driving sensor 200 to the first vehicle-mounted Ethernet physical layer chip 101 .

[0073] The first vehicle Ethernet physical layer chip 101 is connected to the second vehicle Ethernet physical layer chip 102 , and can transmit sensor data to the second vehicle Ethernet physical layer chip 102 .

[0074] The second connector 105 is connected to the autonomous driving domain controller 300 via a second wiring harness, and sensor data can be transmitted from the second on-board Ethernet physical layer chip 102 to the autonomous driving domain controller 300 .

[0075] The autonomous driving domain controller 300 may transmit the sensor configuration data to the autonomous driving sensor 200, so that the autonomous driving sensor 200 performs relevant configurations based on the sensor configuration data. The specific steps are as follows:

[0076] The second connector 105 is connected to the autonomous driving domain controller 300 via a second wiring harness, and the sensor configuration information can be transmitted from the autonomous driving domain controller 300 to the second on-board Ethernet physical layer chip 102 .

[0077] The second vehicle-mounted Ethernet physical layer chip 102 is connected to the first vehicle-mounted Ethernet physical layer chip 101 , and can transmit sensor configuration information to the first vehicle-mounted Ethernet physical layer chip 101 .

[0078] The first connector 104 is connected to the autonomous driving sensor 200 via a first wiring harness, and the sensor configuration information can be transmitted from the first vehicle-mounted Ethernet physical layer chip 101 to the autonomous driving sensor 200 .

[0079] The first power supply module 106 is connected to the first connector 104, and can obtain power from the device and power the autonomous driving sensor 200. The second power supply module 107 is connected to the second connector 105, and is used to obtain power from the autonomous driving domain controller 300 and power the device. The power supply can be provided by the PODL function of the vehicle Ethernet or by using multiple wires in one wiring harness, without the need for additional power supply, and the design cost is lower.

[0080] The wireless communication module 108 is connected to the controller 103, and can obtain vehicle Ethernet diagnostic information from the controller 103 and transmit it to the autonomous driving domain controller 300 through the gateway. The wireless communication module 108 provides wireless communication function, can realize multiple node networking diagnosis, the networking is simple, suitable for the multi-sensor diagnostic needs of autonomous driving, and transmits the vehicle Ethernet diagnostic information to the gateway device. In addition, the vehicle Ethernet diagnostic information can be transmitted through the wireless communication module 108 such as Bluetooth or wifi (mobile hotspot), without the need for additional wiring, making the device more portable. Among them, the devices that can be used as gateways on the autonomous driving vehicle may include but are not limited to the vehicle system, V2x OBU, TBox, etc. Use existing equipment to realize networking diagnosis without increasing costs. The final diagnostic information will be transferred to the autonomous driving domain controller 300 through the gateway. The autonomous driving domain controller 300 can run the autonomous driving decision control algorithm and apply the diagnostic information.

[0081] In some embodiments, the controller 103 can adopt a low-cost controller (optionally a SOC (System on Chip) with an integrated wireless communication module), does not interfere with network data, and only accesses the registers of the first on-board Ethernet physical layer chip 101 and the second on-board Ethernet physical layer chip 102, which not only ensures the real-time transmission of network data, but also achieves the monitoring purpose.

[0082] The antenna module 109 is connected to the wireless communication module 108 and can send and receive information. The antenna module 109 can be, for example, a PCB (Printed Circuit Board) onboard antenna or an external antenna.

[0083] The storage module 110 is connected to the controller 103, and can store the vehicle Ethernet diagnostic information when the wireless communication module 108 fails to transmit, and delete the vehicle Ethernet diagnostic information when the wireless communication module 108 transmits successfully, thereby ensuring the successful transmission of the vehicle Ethernet diagnostic information. The storage module 110 can be, for example, a low-cost memory such as Flash (flash memory) or EEPROM (Electrically Erasable Programmable read only memory).

[0084] The fault indication module 111 is connected to the controller 103 and can display fault information based on Ethernet diagnostic information. The fault indication module 111 can be, for example, a group of LED (light-emitting diode) arrays for displaying local fault information. Different faults can be indicated by different LEDs or LED combinations in the LED array, so that the faults can be displayed visually.

[0085] The disclosed embodiment proposes an on-board Ethernet diagnostic device. The on-board Ethernet diagnostic device 100 is inserted between the autonomous driving sensor 200 and the autonomous driving domain controller 300. It is suitable for the signal relay of the on-board Ethernet device of autonomous driving, and the transmission signal strength is enhanced to extend the transmission distance. The design can reserve a margin, thereby ensuring high communication quality and reliability. The controller 103 can monitor the first connection state and the second connection state to realize the diagnosis of the physical layer of the on-board Ethernet device. In addition, it can quickly locate whether the fault is on the side of the autonomous driving sensor 200 or the side of the autonomous driving domain controller 300. The power supply can be provided by the PODL function of the on-board Ethernet or by using a power supply method of multiple wire cores in a wiring harness. No additional power supply is required, and the design cost is lower. The wireless communication module 108 provides a wireless communication function, which can realize the networking diagnosis of multiple nodes. The networking is simple and suitable for the diagnosis requirements of multiple sensors of autonomous driving, and the on-board Ethernet diagnostic information is transmitted to the gateway device. In addition, the on-board Ethernet diagnostic information can be transmitted through the wireless communication module 108 such as Bluetooth or wifi, without the need for additional wiring, making the device more portable.

[0086] Figure 5 A process 500 of an embodiment of a vehicle Ethernet diagnostic method according to the present disclosure is shown. The vehicle Ethernet diagnostic method comprises the following steps:

[0087] Step 501: monitor a first connection state stored in a first vehicle-mounted Ethernet physical layer chip and a second connection state stored in a second vehicle-mounted Ethernet physical layer chip.

[0088] In this embodiment, the execution subject of the vehicle Ethernet diagnostic method ( Figure 1 The controller 103 shown may monitor a first connection state stored in a first vehicle-mounted Ethernet physical layer chip and a second connection state stored in a second vehicle-mounted Ethernet physical layer chip.

[0089] The vehicle Ethernet diagnostic device may include a first vehicle Ethernet physical layer chip, a second vehicle Ethernet physical layer chip, and a controller.

[0090] The first vehicle Ethernet physical layer chip is connected to the autonomous driving sensor. The second vehicle Ethernet physical layer chip is connected to the autonomous driving domain controller. The controller is connected between the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip.

[0091] The in-vehicle Ethernet harnesses on autonomous vehicles are usually long, and the signal attenuation on them is large. In particular, the length of the in-vehicle Ethernet harnesses is long, and the wiring length usually exceeds or approaches the 15-meter requirement of the in-vehicle Ethernet. The increase in harness length and the number of connectors will lead to a deterioration in insertion loss and return loss parameters, which will increase the probability of communication failure. In order to eliminate this effect, an in-vehicle Ethernet diagnostic device can be inserted between the autonomous driving sensor and the autonomous driving domain controller. After adding the in-vehicle Ethernet diagnostic device, the theoretical transmission distance will be improved (such as doubled), which is suitable for the signal relay of the in-vehicle Ethernet device for autonomous driving, enhancing the transmission signal strength and extending the transmission distance. The design can reserve a margin to ensure high communication quality and reliability.

[0092] The autonomous driving sensor can be any sensor on the autonomous driving vehicle, including but not limited to: LiDAR, camera, etc. The autonomous driving sensor can collect sensor data and transmit it to the autonomous driving domain controller. The autonomous driving domain controller can generate control instructions based on the sensor data to control the driving of the autonomous driving vehicle.

[0093] The sensor data collected by the autonomous driving sensor can be transmitted to the autonomous driving domain controller through the first vehicle Ethernet physical layer chip, the controller, and the second vehicle Ethernet physical layer chip in sequence. Therefore, the first vehicle Ethernet physical layer chip can determine the first connection state between the first vehicle Ethernet physical layer chip and the autonomous driving sensor based on the sensor data it receives. The first connection state can be stored in a register therein. Similarly, the second vehicle Ethernet physical layer chip can determine the second connection state between the second vehicle Ethernet physical layer chip and the autonomous driving domain controller based on the sensor data it transmits. The second connection state can be stored in a register therein.

[0094] Step 502: Generate vehicle Ethernet diagnostic information based on the first connection state and the second connection state.

[0095] In this embodiment, the above-mentioned execution subject can monitor the first connection state and the second connection state, and generate the vehicle Ethernet diagnostic information according to the first connection state and the second connection state.

[0096] By reading the registers of the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip, the first connection state and the second connection state can be obtained in real time, thereby realizing the diagnosis of the physical layer of the vehicle Ethernet device. If the first connection state is abnormal, it can be determined that the fault is on the autonomous driving sensor side; if the second connection state is abnormal, it can be determined that the fault is on the autonomous driving domain controller side. Among them, the Ethernet diagnostic information can be a diagnosis of the physical layer of the vehicle Ethernet device, including but not limited to the open and short circuit diagnosis of the wiring harness, the diagnosis of whether the physical layer is disconnected, the diagnosis of whether a CRC error occurs, and so on.

[0097] In some embodiments, the wireless communication module is connected to the controller, and can obtain vehicle Ethernet diagnostic information from the controller and transmit it to the autonomous driving domain controller through the gateway. The wireless communication module provides wireless communication function, which can realize multiple node networking diagnosis. The networking is simple and suitable for the multi-sensor diagnostic needs of autonomous driving, and transmits the vehicle Ethernet diagnostic information to the gateway device. In addition, the vehicle Ethernet diagnostic information can be transmitted through wireless communication modules such as Bluetooth or WiFi, without the need for additional wiring, making the device more portable. Among them, the devices that can serve as gateways on autonomous driving vehicles may include but are not limited to vehicle-mounted systems, V2x OBU, TBox, etc. Networking diagnosis is realized using existing equipment without increasing costs. The final diagnostic information will be transferred to the autonomous driving domain controller through the gateway. The autonomous driving domain controller can run the autonomous driving decision control algorithm and apply the diagnostic information.

[0098] In some embodiments, the storage module is connected to the controller, and can store the vehicle Ethernet diagnostic information when the wireless communication module fails to transmit, and delete the vehicle Ethernet diagnostic information when the wireless communication module transmits successfully, thereby ensuring the successful transmission of the vehicle Ethernet diagnostic information. The storage module can be, for example, a low-cost memory such as Flash or eeprom.

[0099] In some embodiments, the fault indication module is connected to the controller and can display fault information based on Ethernet diagnostic information. The fault indication module can be, for example, a group of LED arrays for displaying local fault information. Different faults can be indicated by different LEDs or LED combinations in the LED array, so that the fault can be displayed visually.

[0100] In some embodiments, the above-mentioned execution subject can periodically (such as every 1 second) access the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip, so as to realize real-time diagnosis of the physical layer of the vehicle Ethernet device.

[0101] In some embodiments, the autonomous driving domain controller may send an event instruction to the above-mentioned execution subject when the received sensor data is abnormal. The above-mentioned execution subject may be used to access the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip in response to the event instruction, thereby realizing timely diagnosis of the physical layer of the vehicle Ethernet device.

[0102] Further references Figure 6 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a vehicle-mounted Ethernet diagnostic device. Figure 5 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0103] like Figure 6 As shown, the vehicle Ethernet diagnostic device 600 of this embodiment may include: a monitoring module 601 and a generating module 602. The monitoring module 601 is configured to monitor a first connection state stored in a first vehicle Ethernet physical layer chip and a second connection state stored in a second vehicle Ethernet physical layer chip, wherein the first connection state is a connection state between the first vehicle Ethernet physical layer chip and the autonomous driving sensor, and the second connection state is a connection state between the second vehicle Ethernet physical layer chip and the autonomous driving domain controller; the generating module 602 is configured to generate vehicle Ethernet diagnostic information based on the first connection state and the second connection state.

[0104] In this embodiment, in the vehicle Ethernet diagnostic device 600, the specific processing of the monitoring module 601 and the generating module 602 and the technical effects thereof can be referred to in Figure 5 The relevant descriptions of steps 501-502 in the corresponding embodiment are not repeated here.

[0105] In some optional implementations of this embodiment, the vehicle Ethernet diagnostic device 600 also includes: a first sending module, configured to send the vehicle Ethernet diagnostic information to the wireless communication module, so that the wireless communication module transmits the vehicle Ethernet diagnostic information to the autonomous driving domain controller through the gateway.

[0106] In some optional implementations of this embodiment, the vehicle Ethernet diagnostic device 600 also includes: a second sending module, which is configured to send the vehicle Ethernet diagnostic information to the storage module in response to the failure of the wireless communication module to transmit, so that the storage module stores the vehicle Ethernet diagnostic information, and delete the vehicle Ethernet diagnostic information when the wireless communication module transmits successfully.

[0107] In some optional implementations of this embodiment, the vehicle Ethernet diagnostic device 600 further includes: a third sending module configured to send the vehicle Ethernet diagnostic information to the fault indication module, so that the fault indication module displays fault information based on the vehicle Ethernet diagnostic information.

[0108] In some optional implementations of this embodiment, the monitoring module 601 is further configured to: periodically access the first vehicle-mounted Ethernet physical layer chip and the second vehicle-mounted Ethernet physical layer chip.

[0109] In some optional implementations of this embodiment, the monitoring module 601 is further configured to: in response to receiving an event instruction sent by the autonomous driving domain controller, access the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip.

[0110] In the technical solution disclosed herein, the acquisition, storage and application of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0111] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

[0112] Figure 7 A schematic block diagram of an example electronic device 700 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0113] like Figure 7 As shown, the device 700 includes a computing unit 701, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 702 or a computer program loaded from a storage unit 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 can also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0114] A number of components in the device 700 are connected to the I / O interface 705, including: an input unit 706, such as a keyboard, a mouse, etc.; an output unit 707, such as various types of displays, speakers, etc.; a storage unit 708, such as a disk, an optical disk, etc.; and a communication unit 709, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0115] The computing unit 701 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 701 performs the various methods and processes described above, such as the vehicle Ethernet diagnostic method. For example, in some embodiments, the vehicle Ethernet diagnostic method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 708. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 700 via the ROM 702 and / or the communication unit 709. When the computer program is loaded into the RAM 703 and executed by the computing unit 701, one or more steps of the vehicle Ethernet diagnostic method described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured to perform the vehicle Ethernet diagnostic method in any other appropriate manner (e.g., by means of firmware).

[0116] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0117] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0118] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0119] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0120] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0121] A computer system may include a client and a server. The client and the server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises through computer programs running on respective computers and having a client-server relationship to each other. The server may be a cloud server, a server in a distributed system, or a server combined with a blockchain.

[0122] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions provided by this disclosure can be achieved, and this document does not limit this.

[0123] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A vehicle Ethernet diagnostic device, comprising: A first vehicle Ethernet physical layer chip, a second vehicle Ethernet physical layer chip and a controller; The first vehicle Ethernet physical layer chip is connected to the autonomous driving sensor and is used to store a first connection state between the first vehicle Ethernet physical layer chip and the autonomous driving sensor; The second vehicle Ethernet physical layer chip is connected to the autonomous driving domain controller and is used to store a second connection state between the second vehicle Ethernet physical layer chip and the autonomous driving domain controller; The controller is connected between the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip, and is used to monitor the first connection state and the second connection state, and generate vehicle Ethernet diagnostic information.

2. The device according to claim 1, wherein: The device also includes a first connector and a second connector; The first connector is connected between the first vehicle Ethernet physical layer chip and the autonomous driving sensor, and is used to implement data transmission between the autonomous driving sensor and the first vehicle Ethernet physical layer chip; The first vehicle-mounted Ethernet physical layer chip is connected to the second vehicle-mounted Ethernet physical layer chip, so as to realize data transmission between the first vehicle-mounted Ethernet physical layer chip and the second vehicle-mounted Ethernet physical layer chip; The second connector is connected between the second on-board Ethernet physical layer chip and the autonomous driving domain controller, and is used to realize data transmission between the second on-board Ethernet physical layer chip and the autonomous driving domain controller.

3. The device according to claim 2, wherein: The first connector is used to transmit sensor data from the autonomous driving sensor to the first vehicle Ethernet physical layer chip; The first vehicle-mounted Ethernet physical layer chip is used to transmit the sensor data to the second vehicle-mounted Ethernet physical layer chip; The second connector is used to transmit the sensor data from the second on-board Ethernet physical layer chip to the autonomous driving domain controller.

4. The device according to claim 2, wherein: The second connector is used to transmit sensor configuration information from the autonomous driving domain controller to the second vehicle Ethernet physical layer chip; The second vehicle-mounted Ethernet physical layer chip is used to transmit the sensor configuration information to the first vehicle-mounted Ethernet physical layer chip; The first connector is used to transmit the sensor configuration information from the first on-board Ethernet physical layer chip to the autonomous driving sensor.

5. The device according to claim 3 or 4, wherein: The device also includes a first power supply module and a second power supply module; The first power supply module is connected to the first connector, and is used to obtain power from the device and supply power to the autonomous driving sensor; The second power supply module is connected to the second connector and is used to obtain power from the autonomous driving domain controller and power the device.

6. The device according to claim 1, wherein: The device also includes a wireless communication module; The wireless communication module is connected to the controller and is used to obtain the on-board Ethernet diagnostic information from the controller and transmit it to the autonomous driving domain controller through a gateway.

7. The device according to claim 6, wherein: The device also includes a storage module; The storage module is connected to the controller, and is used to store the vehicle Ethernet diagnostic information when the wireless communication module fails to transmit, and to delete the vehicle Ethernet diagnostic information when the wireless communication module transmits successfully.

8. The device according to claim 6, wherein: The device also includes an antenna module; The antenna module is connected to the wireless communication module for sending and receiving information.

9. The device according to claim 1, wherein: The device also includes a fault indication module; The fault indication module is connected to the controller and is used to display fault information based on the Ethernet diagnostic information.

10. The device according to claim 1, wherein: The controller is used to periodically access the first in-vehicle Ethernet physical layer chip and the second in-vehicle Ethernet physical layer chip.

11. The device according to claim 3, wherein: The autonomous driving domain controller is configured to send an event instruction to the controller when the received sensor data is abnormal; The controller is used to access the first vehicle-mounted Ethernet physical layer chip and the second vehicle-mounted Ethernet physical layer chip in response to the event instruction.

12. A vehicle Ethernet diagnostic method, comprising: Monitoring a first connection state stored in a first vehicle Ethernet physical layer chip and a second connection state stored in a second vehicle Ethernet physical layer chip, wherein the first connection state is a connection state between the first vehicle Ethernet physical layer chip and an autonomous driving sensor, and the second connection state is a connection state between the second vehicle Ethernet physical layer chip and an autonomous driving domain controller; In-vehicle Ethernet diagnostic information is generated based on the first connection state and the second connection state.

13. The method according to claim 12, wherein: The method further comprises: The vehicle Ethernet diagnostic information is sent to the wireless communication module, so that the wireless communication module transmits the vehicle Ethernet diagnostic information to the autonomous driving domain controller through the gateway.

14. The method according to claim 13, wherein: The method further comprises: In response to the wireless communication module transmission failure, the vehicle Ethernet diagnostic information is sent to the storage module so that the storage module stores the vehicle Ethernet diagnostic information, and deletes the vehicle Ethernet diagnostic information when the wireless communication module transmission is successful.

15. The method according to claim 12, wherein: The method further comprises: The vehicle Ethernet diagnostic information is sent to a fault indication module, so that the fault indication module displays fault information based on the vehicle Ethernet diagnostic information.

16. The method according to claim 12, wherein: The monitoring of the first connection state stored in the first vehicle-mounted Ethernet physical layer chip and the second connection state stored in the second vehicle-mounted Ethernet physical layer chip includes: The first vehicle-mounted Ethernet physical layer chip and the second vehicle-mounted Ethernet physical layer chip are periodically accessed.

17. The method according to claim 12, wherein: The monitoring of the first connection state stored in the first vehicle-mounted Ethernet physical layer chip and the second connection state stored in the second vehicle-mounted Ethernet physical layer chip includes: In response to receiving an event instruction sent by the autonomous driving domain controller, the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip are accessed.

18. An in-vehicle Ethernet diagnostic device, comprising: a monitoring module configured to monitor a first connection state stored in a first vehicle Ethernet physical layer chip and a second connection state stored in a second vehicle Ethernet physical layer chip, wherein the first connection state is a connection state between the first vehicle Ethernet physical layer chip and an autonomous driving sensor, and the second connection state is a connection state between the second vehicle Ethernet physical layer chip and an autonomous driving domain controller; The generating module is configured to generate vehicle Ethernet diagnostic information based on the first connection state and the second connection state.

19. The device according to claim 18, wherein: The device also includes: The first sending module is configured to send the vehicle Ethernet diagnostic information to the wireless communication module, so that the wireless communication module transmits the vehicle Ethernet diagnostic information to the autonomous driving domain controller through the gateway.

20. The device according to claim 19, wherein The device also includes: The second sending module is configured to send the vehicle Ethernet diagnostic information to the storage module in response to the failure of the wireless communication module to transmit, so that the storage module stores the vehicle Ethernet diagnostic information, and delete the vehicle Ethernet diagnostic information when the wireless communication module transmits successfully.

21. The device according to claim 18, wherein The device also includes: The third sending module is configured to send the vehicle Ethernet diagnostic information to the fault indication module, so that the fault indication module displays fault information based on the vehicle Ethernet diagnostic information.

22. The device according to claim 18, wherein The monitoring module is further configured to: The first vehicle-mounted Ethernet physical layer chip and the second vehicle-mounted Ethernet physical layer chip are periodically accessed.

23. The device according to claim 18, wherein The monitoring module is further configured to: In response to receiving an event instruction sent by the autonomous driving domain controller, the first vehicle Ethernet physical layer chip and the second vehicle Ethernet physical layer chip are accessed.

24. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 12 to 17.

25. A non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the method of any one of claims 12-17.

26. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 12 to 17.

Images