An intelligent driving data interaction system and method, product and electronic device

Abstract

This application provides an intelligent driving data interaction system, method, product, and electronic device. The intelligent driving data interaction system includes: a central gateway, which acquires the vehicle's driving status and outputs the vehicle's drive-by-wire chassis status based on the driving status; an autonomous driving domain controller, which outputs autonomous driving enable commands and drive-by-wire commands to the central gateway based on the drive-by-wire chassis status, enabling the vehicle to enter autonomous driving mode; a drive-by-wire module, which receives the autonomous driving enable commands and drive-by-wire commands, and outputs the module's operating status information and manual intervention information; the autonomous driving domain controller also receives the manual intervention information from the drive-by-wire module and controls the vehicle to enter manual driving mode or maintain autonomous driving mode based on the manual intervention information. This application optimizes and improves the efficiency of the system and method through technical and process optimizations, applying the intelligent driving data interaction system to new energy vehicles, and realizing the intelligent, efficient, and low-carbon development of engineering vehicle operations in steel plants.

Description

Technical Field

[0001] This application relates to the field of intelligent driving, and in particular to an intelligent driving data interaction system and method, product and electronic device. Background Technology

[0002] Since 2018, with the deepening development of the internet and the emergence of new-generation information technologies such as cloud computing, green and low-carbon development has primarily focused on reducing carbon emissions through the development and use of clean energy. Smart manufacturing, on the other hand, aims to apply new information and communication technologies to enable the entire production and management process to possess advanced manufacturing capabilities with deep self-sensing, self-decision-making, and self-execution. This is achieved through smart factories as the carrier and intelligentization of key manufacturing processes as the core, thereby improving production efficiency and reducing energy consumption. Engineering machinery, transportation vehicles, and related production equipment, as key production process elements in steel plants, have been applying information and communication technologies, electrical automation technologies, and new energy technologies. Research and implementation of new smart and green transportation and batching technologies for steel plants began successively in 2022.

[0003] How to apply the intelligent driving data interaction system and methods of pure electric dump trucks to intelligent driving vehicles for scrap steel transportation is one of the technical problems that urgently needs to be solved. Summary of the Invention

[0004] The purpose of this application is to provide an intelligent driving data interaction system, method, product, and electronic device to solve the technical problem that the intelligent driving data interaction system and method of pure electric dump trucks cannot be applied to intelligent driving vehicles for scrap steel transportation.

[0005] To achieve the above and other related objectives, a first aspect of this application provides an intelligent driving data interaction system. The intelligent driving data interaction system includes: a central gateway, an autonomous driving domain controller, and a drive-by-wire module; the central gateway is used to acquire the driving state of a vehicle and output the drive-by-wire chassis state of the vehicle based on the driving state; the autonomous driving domain controller is communicatively connected to the central gateway to receive the drive-by-wire chassis state output by the central gateway, and outputs an autonomous driving enable command and a drive-by-wire command to the central gateway based on the drive-by-wire chassis state to enable the vehicle to enter autonomous driving mode; the drive-by-wire module is communicatively connected to the central gateway to receive the autonomous driving enable command and the drive-by-wire command forwarded by the central gateway, and outputs the working status information and manual intervention information of the drive-by-wire module to the central gateway; the autonomous driving domain controller also receives the working status information and the manual intervention information of the drive-by-wire module forwarded by the central gateway, adjusts and outputs the autonomous driving enable command and the drive-by-wire command based on the working status information of the drive-by-wire module, and controls the vehicle to enter manual driving mode or maintain autonomous driving mode based on the manual intervention information.

[0006] In some embodiments of the first aspect of this application, the drive-by-wire chassis state includes: enabling autonomous driving; acquiring the driving state of the vehicle and outputting the drive-by-wire chassis state of the vehicle based on the driving state includes: acquiring the vehicle's readiness status and the vehicle's drive-by-wire switch status; determining whether the vehicle's readiness status and the vehicle's drive-by-wire switch status meet the conditions for autonomous driving; if they do, then outputting the vehicle's drive-by-wire chassis state; otherwise, keeping the vehicle in manual driving mode.

[0007] In some embodiments of the first aspect of this application, the drive-by-wire commands include: target steering angle and steering wheel speed commands, target deceleration commands, accelerator pedal opening commands, light control commands, gear control commands, and parking control commands; the central gateway forwarding the autonomous driving enable command and the drive-by-wire commands includes: obtaining the ID codes of the autonomous driving enable command and the drive-by-wire commands output by the autonomous driving domain controller; determining the drive-by-wire unit in the drive-by-wire module corresponding to the autonomous driving enable command and the drive-by-wire commands based on the ID codes; and distributing the autonomous driving enable command and the drive-by-wire commands to the corresponding drive-by-wire units according to the ID codes.

[0008] In some embodiments of the first aspect of this application, the steer-by-wire module includes: a steer-by-wire unit, a drive-by-wire unit, a brake-by-wire unit, a gear-by-wire unit, a light-by-wire unit, and a parking-by-wire unit; the steer-by-wire unit receives and executes the autonomous driving enable command and the target steering angle and steering wheel speed commands forwarded by the central gateway, and outputs the working status information of the steer-by-wire unit and steering manual takeover information; the drive-by-wire unit receives and executes the autonomous driving enable command and the accelerator pedal opening command forwarded by the central gateway, and outputs the working status information of the drive-by-wire unit and steering manual takeover information; the brake-by-wire unit receives the drive-by-wire enable command and the accelerator pedal opening command forwarded by the central gateway, and outputs the working status information of the drive-by-wire unit and steering manual takeover information; the brake-by-wire unit receives the drive-by-wire enable command and the target steering angle and steering wheel speed commands forwarded by the central gateway. The system forwards and executes the autonomous driving enable command and the target deceleration command from the central gateway, and outputs the working status and braking information of the brake-by-wire unit; the gear shift unit receives and executes the autonomous driving enable command and the gear shift control command forwarded by the central gateway, and outputs the working status information of the gear shift unit; the headlight unit receives and executes the autonomous driving enable command and the headlight control command forwarded by the central gateway, and outputs the working status information of the headlight unit; the parking brake unit receives and executes the autonomous driving enable command and the parking control command forwarded by the central gateway, and outputs the working status information of the parking brake unit.

[0009] In some embodiments of the first aspect of this application, the manual takeover information of the drive-by-wire module includes: steering manual takeover information, drive manual takeover information, and braking information; the autonomous driving domain controller controls the vehicle to enter manual driving mode or controls the vehicle to maintain autonomous driving mode based on the manual takeover information of the drive-by-wire module, including: determining whether the brake pedal has been manually taken over based on the braking information; if it has been manually taken over, the vehicle meets the conditions for exiting autonomous driving, and the autonomous driving domain controller stops outputting the autonomous driving enable command and the drive-by-wire command to enable the vehicle to enter manual driving mode; if it has not been manually taken over, determining whether the autonomous driving domain controller has received the steering manual takeover information or the drive manual takeover information; if either the steering manual takeover information or the drive manual takeover information is received by the autonomous driving domain controller, the vehicle meets the conditions for exiting autonomous driving, and the autonomous driving domain controller stops outputting the autonomous driving enable command and the drive-by-wire command to enable the vehicle to enter manual driving mode; otherwise, the vehicle meets the conditions for exiting autonomous driving, and the autonomous driving domain controller stops outputting the autonomous driving enable command and the drive-by-wire command to enable the vehicle to enter manual driving mode.

[0010] In some embodiments of the first aspect of this application, the autonomous driving domain controller adjusting and outputting the autonomous driving enable command and the drive-by-wire command based on the working state information of the drive-by-wire module includes: determining whether the autonomous driving enable command and the drive-by-wire command output by the autonomous driving domain controller are correctly executed based on the working state information of the drive-by-wire module; if they are correctly executed, then clearing the autonomous driving enable command and the drive-by-wire command and outputting a new autonomous driving enable command and a new drive-by-wire command; otherwise, re-outputting the autonomous driving enable command and the drive-by-wire command.

[0011] In some embodiments of the first aspect of this application, the system further includes: an intelligent driving remote receiving module and a vehicle control module; the intelligent driving remote receiving module outputs a hardware wake-up command and starts the vehicle power supply to wake up the vehicle control module based on a received remote start request; the vehicle control module performs a self-check on the vehicle and returns vehicle status information to the intelligent driving remote receiving module to assist the intelligent driving remote receiving module in starting the vehicle; and the intelligent driving remote receiving module outputs a high-voltage power-down request based on a received remote shutdown request; the vehicle control module receives and executes the high-voltage power-down request and returns vehicle status information to the intelligent driving remote receiving module to assist the intelligent driving remote receiving module in shutting down the vehicle.

[0012] To achieve the above and other related objectives, a second aspect of this application provides an intelligent driving data interaction method. The intelligent driving data interaction method includes: acquiring the driving state of a vehicle and outputting the drive-by-wire chassis state based on the driving state; receiving and forwarding an autonomous driving enable command and a drive-by-wire command output by an autonomous driving domain controller based on the drive-by-wire chassis state to a drive-by-wire module, so that the vehicle enters an autonomous driving mode; receiving and forwarding the operating status information and manual intervention information output by the drive-by-wire module to the autonomous driving domain controller, so that the autonomous driving domain controller adjusts and outputs the autonomous driving enable command and the drive-by-wire command based on the operating status information of the drive-by-wire module, and controls the vehicle to enter a manual driving mode or maintain an autonomous driving mode based on the manual intervention information.

[0013] To achieve the above and other related objectives, a third aspect of this application provides a computer program product, which includes computer program code. When the computer program code is run on a computer, the computer implements the intelligent driving data interaction method described in the second aspect of this application.

[0014] To achieve the above and other related objectives, a fourth aspect of this application provides a computer device / equipment / system / electronic terminal, including a memory, a processor, and a computer program stored in the memory; the processor executes the computer program to implement the intelligent driving data interaction method described in the second aspect of this application.

[0015] As described above, the intelligent driving data interaction system, method, product, and electronic device of this application have the following beneficial effects:

[0016] This application optimizes and improves the efficiency of the system and method in terms of technology and process, and applies the intelligent driving data interaction system to new energy vehicles to realize the intelligent, efficient and low-carbon development of steel plant engineering vehicle operation. After the vehicle is converted to electric drive and drive-by-wire, carbon emissions are reduced by 100%, and the intelligent driving data interaction efficiency is improved by 60% compared with traditional electric control. Attached Figure Description

[0017] Figure 1 The diagram shown is a structural schematic of an intelligent driving data interaction system according to an embodiment of this application.

[0018] Figure 2 The diagram shown is a flowchart of the central gateway in one embodiment of this application.

[0019] Figure 3 The diagram shown is a flowchart illustrating the forwarding of autonomous driving enable commands and drive-by-wire commands in one embodiment of this application.

[0020] Figure 4The diagram shown is a flowchart of the steering-by-wire unit in one embodiment of this application.

[0021] Figure 5 The diagram shown is a flowchart of the working process of the drive unit by wire in one embodiment of this application.

[0022] Figure 6 The diagram shown is a flowchart of the operation of a linear control braking unit in one embodiment of this application.

[0023] Figure 7 The diagram shown is a flowchart of the working process of the drive-by-wire gear shift unit in one embodiment of this application.

[0024] Figure 8 The diagram shown is a flowchart of the operation of a wired lighting unit in one embodiment of this application.

[0025] Figure 9 The diagram shown is a flowchart of the working process of the drive-by-wire parking unit in one embodiment of this application.

[0026] Figure 10 The diagram shown is a flowchart of the autonomous driving domain controller in one embodiment of this application.

[0027] Figure 11 The diagram shown is a structural schematic of an intelligent driving data interaction system according to another embodiment of this application.

[0028] Figure 12 The diagram shows the workflow of the intelligent driving remote receiving module and the vehicle control module in one embodiment of this application.

[0029] Figure 13 The diagram shown is a flowchart illustrating the intelligent driving data interaction method in one embodiment of this application.

[0030] Figure 14 The diagram shown is a structural schematic of an electronic device according to an embodiment of this application.

[0031] Component designation

[0032] 100 Intelligent Driving Data Interaction System

[0033] 110 Central Gateway

[0034] 120 Autonomous Driving Domain Controller

[0035] 130 drive-by-wire module

[0036] 140 Intelligent Driving Remote Receiving Module

[0037] 150 Vehicle Control Module

[0038] 1400 Electronic Devices

[0039] 1401 processor

[0040] 1402 Memory

[0041] 14021 Operating System

[0042] Application 14022

[0043] 1403 Network Interface

[0044] 1404 bus system

[0045] 1405 User Interface Detailed Implementation

[0046] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, unless otherwise specified, the following embodiments and features in the embodiments can be combined with each other.

[0047] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0048] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, future 5th Generation (5G) communication systems, new radio access technology (NR), LTE Time Division Duplex (TDD), Worldwide Interoperability for Microwave Access (WiMAX), Universal Mobile Telecommunication System (UMTS), and vehicle-to-XV2X. V2X can include vehicle to network (V2N), vehicle to vehicle (V2V), vehicle to infrastructure (V2I), vehicle to pedestrian (V2P), Long Term Evolution-Vehicle (LTE-V), vehicle-to-everything (V2X), machine-type communication (MTC), Internet of Things (IoT), Long Term Evolution-Machine (LTE-M), and machine to machine (M2M).

[0049] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 Detailed explanation. Figure 1 A schematic diagram of the structure of an intelligent driving data interaction system according to an embodiment of this application is shown. The intelligent driving data interaction system 100 in this embodiment mainly includes: a central gateway 110, an autonomous driving domain controller 120, and a drive-by-wire module 130.

[0050] In this embodiment, the central gateway 110 is used to acquire the driving state of the vehicle and output the drive-by-wire chassis state based on the driving state; the autonomous driving domain controller 120 is communicatively connected to the central gateway 110 to receive the drive-by-wire chassis state output by the central gateway 110, and outputs an autonomous driving enable command and a drive-by-wire command to the central gateway 110 based on the drive-by-wire chassis state to enable the vehicle to enter the autonomous driving mode; the drive-by-wire module 130 is communicatively connected to the central gateway 110 to receive the autonomous driving enable command and the drive-by-wire command forwarded by the central gateway 110, and outputs the working status information and manual takeover information of the drive-by-wire module 130 to the central gateway 110; the autonomous driving domain controller 120 also receives the working status information and the manual takeover information of the drive-by-wire module 130 forwarded by the central gateway 110, and adjusts and outputs the autonomous driving enable command and the drive-by-wire command based on the working status information of the drive-by-wire module 130, and controls the vehicle to enter the manual driving mode or controls the vehicle to maintain the autonomous driving mode based on the manual takeover information.

[0051] The central gateway will be described in detail below.

[0052] Please see Figure 2 This is a flowchart of the central gateway's workflow.

[0053] In this embodiment, the drive-by-wire chassis state includes: enabling autonomous driving; the central gateway 110 acquires the vehicle's driving state and outputs the vehicle's drive-by-wire chassis state based on the driving state, including: acquiring the vehicle's readiness status and the vehicle's drive-by-wire switch status; determining whether the vehicle's readiness status and the vehicle's drive-by-wire switch status meet the conditions for autonomous driving; if they do, then outputting the vehicle's drive-by-wire chassis state; otherwise, keeping the vehicle in manual driving mode.

[0054] In this embodiment, when the vehicle is in the REDAY state and the drive-by-wire switch is active, the vehicle meets the conditions for autonomous driving, and the drive-by-wire chassis state that allows autonomous driving is output; otherwise, if the vehicle cannot simultaneously meet the conditions of being in the REDAY state and the drive-by-wire switch being active, the vehicle does not meet the conditions for autonomous driving, and the vehicle continues to maintain the manual driving mode.

[0055] In this embodiment, the central gateway 110 also receives the autonomous driving enable command and the drive-by-wire command output by the autonomous driving domain controller 120, and forwards the received autonomous driving enable command and the drive-by-wire command to the drive-by-wire module 130.

[0056] Specifically, the drive-by-wire commands include: target steering angle and steering wheel speed commands, target deceleration commands, accelerator pedal opening commands, light control commands, gear control commands, and parking control commands.

[0057] like Figure 3 As shown, the central gateway 110 forwards the autonomous driving enable command and the drive-by-wire command to the drive-by-wire module 130 via the following steps:

[0058] S31. Obtain the ID codes of the autonomous driving enable command and the drive-by-wire command output by the autonomous driving domain controller 120.

[0059] Specifically, the autonomous driving enabling commands include: steer-by-wire enabling command, braking enabling command, and drive enabling command; each of the steer-by-wire commands and each of the autonomous driving enabling commands has a corresponding unique ID code.

[0060] For example, the unique ID code corresponding to the steering-by-wire enable command is: 0x0CFFB19E Byte3 Bit1~4=0x01;

[0061] The unique ID code corresponding to the braking enable command is: 0x0CFFB69E Byte3 Bit3~4=0x01;

[0062] The unique ID code corresponding to the driver enable command is: 0x0CFFB39E Byte1 Bit1~2=0x01.

[0063] S32. Based on the ID encoding, determine the drive-by-wire unit in the drive-by-wire module 130 that corresponds to the autonomous driving enable command and the drive-by-wire command.

[0064] Specifically, the wire control unit in the wire control module corresponding to each wire control command is obtained based on the unique ID code corresponding to each wire control command, so that the central gateway 110 can obtain the forwarding object of each wire control command.

[0065] S33. Distribute the autonomous driving enable command and the drive-by-wire command to the corresponding drive-by-wire unit according to the ID encoding.

[0066] Each wire control command is forwarded according to the forwarding object of the acquired wire control command, so that the wire control unit of the wire control module 130 receives and executes the wire control command.

[0067] In this embodiment, the central gateway 110 also receives the working status information and manual takeover information of the drive-by-wire module 130 and forwards the working status information and the manual takeover information to the autonomous driving domain controller 120.

[0068] It should be noted that the working status information of the wired control module 130 and the manual takeover information also have corresponding unique ID codes, which will not be listed here.

[0069] The following is a detailed introduction to the drive-by-wire module.

[0070] The drive-by-wire module 130 includes: a drive-by-wire steering unit, a drive-by-wire drive unit, a brake-by-wire brake unit, a gear-by-wire gear shift unit, a light-by-wire unit, and a parking-by-wire unit.

[0071] Specifically, the steer-by-wire unit receives and executes the autonomous driving enable command and the target steering angle and steering wheel speed command forwarded by the central gateway 110, and outputs the working status information of the steer-by-wire unit and the information that the steering has been manually taken over.

[0072] The drive-by-wire unit receives and executes the autonomous driving enable command and the accelerator pedal opening command forwarded by the central gateway 110, and outputs the working status information of the drive-by-wire unit and the information that the drive has been manually taken over.

[0073] The brake-by-wire unit receives and executes the automatic driving enable command and the target deceleration command forwarded by the central gateway 110, and outputs the working status and braking information of the brake-by-wire unit.

[0074] The drive-by-wire gear shift unit receives and executes the automatic driving enable command and the gear shift control command forwarded by the central gateway 110, and outputs the working status information of the drive-by-wire gear shift unit.

[0075] The drive-by-wire lighting unit receives and executes the autonomous driving enable command and the lighting control command forwarded by the central gateway 110, and outputs the working status information of the drive-by-wire lighting unit.

[0076] The drive-by-wire parking unit receives and executes the autonomous driving enable command and the parking control command forwarded by the central gateway 110, and outputs the working status information of the drive-by-wire parking unit.

[0077] Please see Figure 4 The diagram shows the workflow of the steer-by-wire unit.

[0078] In this embodiment, before receiving the autonomous driving enable command and the target steering angle and steering wheel speed command forwarded by the central gateway 110, the steer-by-wire unit is in manual driving mode; after receiving the autonomous driving enable command and the target steering angle and steering wheel speed command, the steer-by-wire unit enters autonomous driving mode and executes actions according to the target steering angle and steering wheel speed command, while feeding back the working status information of the steer-by-wire unit after executing the actions to the central gateway 110, so that the central gateway 110 forwards the working status information of the steer-by-wire unit to the autonomous driving domain controller 120.

[0079] In this embodiment, the steer-by-wire unit also monitors the steering wheel torque information in real time and determines whether the steering wheel has been manually taken over based on the steering wheel torque information;

[0080] If the steering wheel is manually taken over, the steer-by-wire unit will automatically switch to manual driving mode and simultaneously send steering manual takeover information to the central gateway 110, so that the central gateway 110 will forward the steering manual takeover information to the autonomous driving domain controller 120.

[0081] If the steering wheel is not manually controlled, the steer-by-wire unit switches to manual driving mode (waiting for the next automatic driving enable command and the target steering angle and steering wheel speed command).

[0082] It should be noted that if the drive-by-wire gear shift unit does not receive a continuous drive-by-wire enable command and the target steering angle and steering wheel speed command after executing the automatic driving enable command and the target steering angle and steering wheel speed command, and is not manually taken over, then the drive-by-wire gear shift unit will enter the manual driving mode.

[0083] Please see Figure 5 The diagram shows the workflow of the drive unit.

[0084] In this embodiment, before receiving the autonomous driving enable command and the accelerator pedal opening command forwarded by the central gateway 110, the drive-by-wire unit is in manual driving mode; after receiving the autonomous driving enable command and the accelerator pedal opening command, the drive-by-wire unit enters autonomous driving mode and executes actions according to the accelerator pedal opening command. At the same time, the working status information of the drive-by-wire unit after executing the actions is fed back to the central gateway 110, so that the central gateway 110 forwards the working status information of the drive-by-wire unit to the autonomous driving domain controller 120.

[0085] In this embodiment, the drive-by-wire unit also monitors the accelerator pedal opening information in real time, and determines whether the accelerator pedal has been manually taken over based on the accelerator pedal opening information.

[0086] If the accelerator pedal is manually taken over, the drive-by-wire unit will automatically switch to manual driving mode and simultaneously send a drive-by-wire information to the central gateway 110, so that the central gateway 110 will forward the drive-by-wire information to the autonomous driving domain controller 120.

[0087] If the accelerator pedal is not manually controlled, the drive-by-wire unit switches to manual driving mode (waiting for the next autonomous driving enable command and accelerator pedal opening command).

[0088] It should be noted that if the drive-by-wire unit does not receive a continuous automatic driving enable command and accelerator pedal opening command after executing the automatic driving enable command and the accelerator pedal opening command, and is not manually taken over, the drive-by-wire unit will enter the manual driving mode.

[0089] Please see Figure 6 This is a flowchart of the workflow of the brake-by-wire unit.

[0090] In this embodiment, before receiving the autonomous driving enable command and the target deceleration command forwarded by the central gateway 110, the brake-by-wire unit is in manual driving mode; after receiving the autonomous driving command and the target deceleration command, the brake-by-wire unit enters autonomous driving mode and executes actions according to the target deceleration command, while feeding back the working status information of the brake-by-wire unit after executing the actions to the central gateway 110, so that the central gateway 110 forwards the working status information of the brake-by-wire unit to the autonomous driving domain controller 120.

[0091] In this embodiment, the brake-by-wire unit also monitors braking information in real time and feeds back the monitored braking information to the central gateway 110, so that the central gateway 110 forwards the braking information to the autonomous driving domain controller 120.

[0092] Specifically, the braking information includes: brake pedal position information.

[0093] Please see Figure 7 The diagram shows the workflow of the drive-by-wire gear shift unit.

[0094] In this embodiment, when the drive-by-wire gear shift unit does not receive the autonomous driving enable command and the gear shift control command forwarded by the central gateway 110, the drive-by-wire gear shift unit is in manual driving mode; after receiving the autonomous driving enable command and the gear shift control command, the drive-by-wire gear shift unit enters autonomous driving mode and executes actions according to the gear shift control command, while feeding back the working status information of the drive-by-wire gear shift unit after executing the actions to the central gateway 110, so that the central gateway 110 forwards the working status information of the drive-by-wire gear shift unit to the autonomous driving domain controller 120.

[0095] Please see Figure 8 The diagram shows the workflow of the wired lighting unit.

[0096] In this embodiment, when the drive-by-wire lighting unit does not receive the autonomous driving enable command and the lighting control command forwarded by the central gateway 110, the drive-by-wire lighting unit is in manual driving mode; after receiving the autonomous driving enable command and the lighting control command, the drive-by-wire lighting unit enters autonomous driving mode and executes actions according to the lighting control command, while feeding back the working status information of the drive-by-wire lighting unit after executing the actions to the central gateway 110, so that the central gateway 110 forwards the working status information of the drive-by-wire lighting unit to the autonomous driving domain controller 120.

[0097] Please see Figure 9 The diagram shows the workflow of the drive-by-wire parking unit.

[0098] In this embodiment, when the drive-by-wire parking unit does not receive the autonomous driving enable command and the parking control command forwarded by the central gateway 110, the drive-by-wire parking unit is in manual driving mode; after receiving the autonomous driving enable command and the parking control command, the drive-by-wire parking unit enters autonomous driving mode and executes actions according to the parking control command, while feeding back the working status information of the drive-by-wire parking unit after executing the actions to the central gateway 110, so that the central gateway 110 forwards the working status information of the drive-by-wire parking unit to the autonomous driving domain controller 120.

[0099] The following section will provide a detailed introduction to the autonomous driving domain controller.

[0100] The autonomous driving domain controller 120 receives the drive-by-wire chassis status output by the central gateway 110, and outputs an autonomous driving enable command and a drive-by-wire command to the central gateway 110 based on the drive-by-wire chassis status, so that the central gateway 110 forwards the autonomous driving enable command and the drive-by-wire command to the corresponding drive-by-wire unit in the drive-by-wire module 130 respectively.

[0101] The autonomous driving domain controller 120 can receive the working status information and manual takeover information of the drive-by-wire module 130 forwarded by the central gateway 110, and adjust and output the autonomous driving enable command and the drive-by-wire command based on the working status information of the drive-by-wire module 130, and control the vehicle to enter the manual driving mode or control the vehicle to maintain the autonomous driving mode based on the manual takeover information.

[0102] In this embodiment, the working status information of the drive-by-wire module 130 includes: the working status information of the drive-by-wire steering unit, the working status information of the drive-by-wire drive unit, the working status information of the brake-by-wire unit, the working status information of the gear-by-wire unit, the working status information of the light-by-wire unit, and the working status information of the parking-by-wire unit; the manual takeover information includes: steering manually taken over information, drive manually taken over information, and braking information.

[0103] Please see Figure 10 This is a flowchart of the workflow of the autonomous driving domain controller.

[0104] In this embodiment, when the autonomous driving domain controller 120 does not receive the drive-by-wire chassis status sent by the central gateway 110, the vehicle is in manual driving mode. When the drive-by-wire chassis status is received, the autonomous driving domain controller 120 receives the drive-by-wire chassis ready instruction and sends an autonomous driving enable command and a drive-by-wire command to the central gateway 110, so that the central gateway 110 forwards the autonomous driving enable command and the drive-by-wire command to the corresponding drive-by-wire unit in the drive-by-wire module 130, respectively.

[0105] In this embodiment, the autonomous driving domain controller 120 further adjusts and outputs the autonomous driving enable command and the drive-by-wire command based on the working status information of the drive-by-wire module 130, including: determining whether the autonomous driving enable command and the drive-by-wire command output by the autonomous driving domain controller 120 are correctly executed based on the working status information of the drive-by-wire module 130.

[0106] If executed correctly, the autonomous driving enable command and the drive-by-wire command are cleared, and a new autonomous driving enable command and a new drive-by-wire command are output.

[0107] If not executed correctly, the autonomous driving enable command and the drive-by-wire command will be re-output.

[0108] In this embodiment, the autonomous driving domain controller 120 also controls the vehicle to enter the manual driving mode or controls the vehicle to maintain the autonomous driving mode based on the manual takeover information of the drive-by-wire module 130, including: determining whether the brake pedal has been manually taken over based on the braking information.

[0109] If the vehicle is manually taken over, it meets the conditions for exiting autonomous driving. The autonomous driving domain controller 120 stops outputting the autonomous driving enable command and the drive-by-wire command, so that the vehicle enters the manual driving mode.

[0110] If the vehicle is not manually controlled, the system determines whether the autonomous driving domain controller 120 has received information indicating that the steering or drive has been manually controlled. If either information is received, the vehicle meets the conditions for exiting autonomous driving, and the autonomous driving domain controller 120 stops outputting the autonomous driving enable command and the drive-by-wire command to allow the vehicle to enter manual driving mode. Otherwise, the vehicle meets the conditions for exiting autonomous driving, and the autonomous driving domain controller 120 stops outputting the autonomous driving enable command and the drive-by-wire command to allow the vehicle to enter manual driving mode.

[0111] It should be noted that, in the embodiments of this application, the words "exemplary" or "for example" indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0112] In particular, such as Figure 11 As shown, the intelligent driving data interaction system 100 in this application embodiment further includes: an intelligent driving remote receiving module 140 and a vehicle control module 150.

[0113] Specifically, the intelligent driving remote receiving module 140, based on the received remote start request, outputs a hardware wake-up command and starts the vehicle power supply to wake up the vehicle control module 150; the vehicle control module 150 performs a self-check on the vehicle and returns vehicle status information to the intelligent driving remote receiving module 140 to assist the intelligent driving remote receiving module 140 in starting the vehicle; and

[0114] The intelligent driving remote receiving module 140 outputs a high-voltage power-down request based on the received remote shutdown request; the vehicle control module 150 receives and executes the high-voltage power-down request, and returns vehicle status information to the intelligent driving remote receiving module 140, thus assisting the intelligent driving remote receiving module 140 in shutting down the vehicle.

[0115] The following section will provide a detailed introduction to the intelligent driving remote receiving module and the vehicle control module.

[0116] Please see Figure 12 The diagram shows the workflow of the intelligent driving remote receiving module and the vehicle control module.

[0117] In this embodiment, when the vehicle is in a power-off state and no remote start request is received, the intelligent driving remote receiving module 140 is in a sleep mode. After receiving the remote start request, the intelligent driving remote receiving module 140 controls the vehicle's main power relay to close, and at the same time hard-wires the drive-by-wire lighting unit to turn on the vehicle's Key-ON power, and outputs a high-voltage power-on request for the auxiliary driver to the vehicle module, while starting the vehicle control module to perform a low-voltage power-on self-test.

[0118] After the intelligent driving remote receiving module receives the completion of the high-voltage power-on of the auxiliary drive and the low-voltage power-on self-test of the vehicle control module 150 passes, the intelligent driving remote receiving module 140 sends a high-voltage power-on request for the main drive. After the vehicle control module 150 executes the high-voltage power-on process of the main drive and returns the vehicle status as "READY", the vehicle is ready to start and the vehicle starts remotely successfully.

[0119] In this embodiment, if the vehicle control module 150 fails the low-voltage power-on self-test, it will not proceed with the high-voltage power-on process and will return to a fault state.

[0120] In this embodiment, when the intelligent driving remote receiving module in startup mode receives a remote shutdown request, it sends a low-voltage power-down command and simultaneously causes the vehicle modules to power down at high voltage. The vehicle control module 150 determines whether the vehicle meets the high-voltage power-down conditions. When the vehicle meets the high-voltage power-down conditions, the vehicle control module 150 executes the high-voltage power-down process and returns the vehicle status as "main and auxiliary relays disconnected" to the intelligent driving remote receiving module 140. When the intelligent driving remote receiving module 140 receives the vehicle status as "main and auxiliary relays disconnected", it allows low-voltage power-down. Then, it further disconnects the wake-up signal of the drive-by-wire lighting unit and disconnects the vehicle power relay 10 seconds after disconnecting the wake-up signal of the drive-by-wire lighting unit.

[0121] It should be understood that the module division in the embodiments of this application is illustrative and only represents a logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0122] This application also provides a method for intelligent driving data interaction.

[0123] Please see Figure 13 The above is a flowchart of the intelligent driving data interaction method described in the embodiments of this application.

[0124] like Figure 12 As shown, the intelligent driving data interaction method includes the following steps:

[0125] S131. Obtain the driving status of the vehicle and output the drive-by-wire chassis status of the vehicle based on the driving status.

[0126] S132. Receive and forward the autonomous driving enable command and drive-by command output by the autonomous driving domain controller based on the state of the drive-by chassis to the drive-by module so that the vehicle enters the autonomous driving mode.

[0127] S133. Receive and forward the working status information and manual takeover information output by the drive-by-wire module to the autonomous driving domain controller, so that the autonomous driving domain controller adjusts and outputs the autonomous driving enable command and the drive-by-wire command based on the working status information of the drive-by-wire module, and controls the vehicle to enter the manual driving mode or controls the vehicle to maintain the autonomous driving mode based on the manual takeover information.

[0128] It should be noted that the protection scope of the intelligent driving data interaction method in this application is not limited to the execution order of the steps listed in this embodiment. Any solution implemented by adding, subtracting, or replacing steps in the prior art based on the principles of this application is included within the protection scope of this application.

[0129] The content of the intelligent driving data interaction method described in this application embodiment is the same as the working content of each module in the intelligent driving data interaction system described in this application embodiment, so it will not be described in detail here.

[0130] According to the intelligent driving data interaction method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute... Figures 2 to 13 Intelligent driving data interaction method of any of the embodiments shown.

[0131] According to the intelligent driving data interaction method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute... Figures 2 to 13 Intelligent driving data interaction method of any of the embodiments shown.

[0132] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0133] Figure 14 This is a schematic block diagram of the electronic device provided in an embodiment of this application. Figure 14 As shown, the electronic device 1400 includes at least one processor 1401, a memory 1402, at least one network interface 1403, and a user interface 1405. The various components in the device are coupled together via a bus system 1404. It is understood that the bus system 1404 is used to implement communication between these components. In addition to a data bus, the bus system 1404 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 14 The general will label all buses as bus systems.

[0134] The user interface 1405 may include a monitor, keyboard, mouse, trackball, clicker, button, touchpad, or touch screen.

[0135] It is understood that memory 1402 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM) or programmable read-only memory (PROM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM) and synchronous static random access memory (SSRAM). The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable categories of memory.

[0136] In this embodiment, the memory 1402 is used to store various types of data to support the operation of the electronic device 1400. Examples of this data include any executable program that operates on the electronic device 1400, such as the operating system 14021 and application program 14022. The operating system 14021 contains various system programs, such as the framework layer, core library layer, driver layer, etc., for implementing various basic services and handling hardware-based tasks. The application program 14022 may contain various applications, such as a media player, browser, etc., for implementing various application services. The intelligent driving data interaction method provided in this embodiment can be included in the application program 14022.

[0137] The methods disclosed in the embodiments of this application can be applied to processor 1401, or implemented by processor 1401. Processor 1401 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 1401 or by instructions in the form of software. The processor 1401 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 1401 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of this application. General-purpose processor 1401 may be a microprocessor or any conventional processor, etc. The steps of the accessory optimization method provided in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in memory. The processor reads the information in the memory and combines it with its hardware to complete the steps of the aforementioned method.

[0138] In an exemplary embodiment, the electronic device 1400 may be used by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), or complex programmable logic devices (CPLDs) to perform the aforementioned method.

[0139] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0140] In summary, this application provides an intelligent driving data interaction system and method, a storage medium, and an electronic device. This application optimizes and improves the efficiency of the system and method in terms of technology and process, enabling the application of the intelligent driving data interaction system to new energy vehicles. This achieves intelligent, efficient, and low-carbon development of engineering vehicle operations in steel plants. After converting the vehicles to electric drive and drive-by-wire systems, carbon emissions are reduced by 100%, and the efficiency of intelligent driving data interaction is improved by 60% compared to traditional electronic control. Therefore, this application effectively overcomes the various shortcomings of existing technologies and has high industrial application value.

[0141] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.

Claims

1. An intelligent driving data interaction system, characterized in that, The system includes: a central gateway, an autonomous driving domain controller, and a drive-by-wire module; The central gateway is used to obtain the driving status of the vehicle and output the drive-by-wire chassis status of the vehicle based on the driving status. The autonomous driving domain controller is communicatively connected to the central gateway to receive the drive-by-wire chassis status output by the central gateway, and outputs autonomous driving enable commands and drive-by commands to the central gateway based on the drive-by-wire chassis status, so as to enable the vehicle to enter autonomous driving mode. The drive-by-wire module is communicatively connected to the central gateway to receive the autonomous driving enable command and drive-by-wire command forwarded by the central gateway, and to output the working status information and manual takeover information of the drive-by-wire module to the central gateway. The autonomous driving domain controller also receives the working status information of the drive-by-wire module and the manual takeover information forwarded by the central gateway, and adjusts and outputs the autonomous driving enable command and the drive-by-wire command based on the working status information of the drive-by-wire module, and controls the vehicle to enter the manual driving mode or controls the vehicle to maintain the autonomous driving mode based on the manual takeover information.

2. The intelligent driving data interaction system according to claim 1, characterized in that, The drive-by-wire chassis status includes: enabling autonomous driving; acquiring the vehicle's driving status and outputting the vehicle's drive-by-wire chassis status based on the driving status includes: Obtain the vehicle's readiness status and the status of the vehicle's drive-by-wire switches; Determine whether the vehicle's readiness status and the status of the vehicle's drive-by-wire switch meet the conditions for autonomous driving. If the conditions are met, the vehicle's drive-by-wire chassis status will be output; otherwise, the vehicle will remain in manual driving mode.

3. The intelligent driving data interaction system according to claim 1, characterized in that, The drive-by-wire commands include: target steering angle and steering wheel speed commands, target deceleration commands, accelerator pedal opening commands, light control commands, gear control commands, and parking control commands; the central gateway forwards the autonomous driving enable commands and drive-by-wire commands, including: Obtain the ID codes of the autonomous driving enable command and the drive-by command output by the autonomous driving domain controller; Based on the ID encoding, the drive unit in the drive module corresponding to the autonomous driving enable command and the drive command is determined; The autonomous driving enable command and the drive-by-wire command are distributed to the corresponding drive-by-wire unit according to the ID encoding.

4. The intelligent driving data interaction system according to claim 3, characterized in that, The drive-by-wire module includes: a drive-by-wire steering unit, a drive-by-wire drive unit, a brake-by-wire braking unit, a gear-by-wire gear shifting unit, a light-by-wire unit, and a parking-by-wire unit; The steer-by-wire unit receives and executes the autonomous driving enable command and the target steering angle and steering wheel speed command forwarded by the central gateway, and outputs the working status information of the steer-by-wire unit and the information that the steering has been manually taken over. The drive-by-wire unit receives and executes the autonomous driving enable command and the accelerator pedal opening command forwarded by the central gateway, and outputs the working status information of the drive-by-wire unit and the information that the drive has been manually taken over. The brake-by-wire unit receives and executes the automatic driving enable command and the target deceleration command forwarded by the central gateway, and outputs the working status and braking information of the brake-by-wire unit. The drive-by-wire gear shift unit receives and executes the autonomous driving enable command and the gear shift control command forwarded by the central gateway, and outputs the working status information of the drive-by-wire gear shift unit. The drive-by-wire lighting unit receives and executes the autonomous driving enable command and the lighting control command forwarded by the central gateway, and outputs the working status information of the drive-by-wire lighting unit. The drive-by-wire parking unit receives and executes the autonomous driving enable command and the parking control command forwarded by the central gateway, and outputs the working status information of the drive-by-wire parking unit.

5. The intelligent driving data interaction system according to claim 1, characterized in that, The manual takeover information of the drive-by-wire module includes: steering manual takeover information, drive manual takeover information, and braking information; the autonomous driving domain controller controls the vehicle to enter manual driving mode or controls the vehicle to maintain autonomous driving mode based on the manual takeover information of the drive-by-wire module, including: Based on the braking information, determine whether the brake pedal has been manually controlled; If the vehicle is manually taken over, it meets the conditions for exiting autonomous driving. The autonomous driving domain controller stops outputting the autonomous driving enable command and the drive-by-wire command, so that the vehicle enters the manual driving mode. If the vehicle is not manually controlled, the system determines whether the autonomous driving domain controller has received information indicating that the steering or drive has been manually controlled. If either information is received, the vehicle meets the conditions for exiting autonomous driving, and the autonomous driving domain controller stops outputting the autonomous driving enable command and the drive-by-wire command to allow the vehicle to enter manual driving mode. Otherwise, the vehicle meets the conditions for exiting autonomous driving, and the autonomous driving domain controller stops outputting the autonomous driving enable command and the drive-by-wire command to allow the vehicle to enter manual driving mode.

6. The intelligent driving data interaction system according to claim 1, characterized in that, The autonomous driving domain controller adjusts and outputs the autonomous driving enable command and the drive-by command based on the working status information of the drive-by module, including: Based on the working status information of the drive-by-wire module, determine whether the autonomous driving enable command and the drive-by-wire command output by the autonomous driving domain controller are executed correctly; If executed correctly, the autonomous driving enable command and the drive-by-wire command are cleared and a new autonomous driving enable command and a new drive-by-wire command are output; otherwise, the autonomous driving enable command and the drive-by-wire command are re-output.

7. The intelligent driving data interaction system according to claim 1, characterized in that, The system also includes: a smart driving remote receiving module and a vehicle control module; The intelligent driving remote receiving module outputs a hardware wake-up command and starts the vehicle power supply to wake up the vehicle control module based on the received remote start request. The vehicle control module performs a self-check on the vehicle and returns vehicle status information to the intelligent driving remote receiving module to assist the intelligent driving remote receiving module in starting the vehicle; and The intelligent driving remote receiving module outputs a high-voltage power-down request based on the received remote shutdown request; The vehicle control module receives and executes the high-voltage power-off request, and returns vehicle status information to the intelligent driving remote receiving module, thus assisting the intelligent driving remote receiving module in shutting down the vehicle.

8. A method for intelligent driving data interaction, characterized in that, The method includes: The vehicle's driving status is obtained, and the vehicle's drive-by-wire chassis status is output based on the driving status. Receive and forward the autonomous driving enable command and drive-by command output by the autonomous driving domain controller based on the state of the drive-by chassis to the drive-by module, so that the vehicle enters the autonomous driving mode. The system receives and forwards the working status information and manual takeover information output by the drive-by-wire module to the autonomous driving domain controller, so that the autonomous driving domain controller adjusts and outputs the autonomous driving enable command and the drive-by-wire command based on the working status information of the drive-by-wire module, and controls the vehicle to enter the manual driving mode or control the vehicle to maintain the autonomous driving mode based on the manual takeover information.

9. A computer program product, characterized in that, The computer program product includes computer program code, which, when run on a computer, enables the computer to implement the intelligent driving data interaction method as described in claim 8.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the intelligent driving data interaction method as described in claim 8.

Images