OTA (over-the-air) upgrading system and method for dynamically supporting software updating of newly-added controller

Abstract

The invention provides an OTA upgrading system and method dynamically supporting newly-added controller software updating, the system comprises an OTA background server and a vehicle-mounted host system, the OTA background server supports management of newly-added controller information, configuration of upgrading parameters and generation of an OTA upgrading package and a configuration file, and the OTA upgrading package and the configuration file are connected with the vehicle-mounted host system. The vehicle-mounted host system has the functions of upgrading package downloading and analysis, part information reading and matching and upgrading execution. The upgrading process comprises two links of creating an upgrading task by a background and triggering upgrading by a vehicle-mounted terminal, and the information reading mode and the upgrading mode of the newly-added controller are dynamically adapted through a configuration file, so that OTA upgrading of the newly-added controller can be realized without updating a vehicle-mounted host system. According to the method, controller types can be expanded infinitely, the rapid iteration requirements of automobile types in the automobile industry are met, software upgrading flexibility and timeliness are improved, development and maintenance cost is reduced, and the method has wide application prospects.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of automotive electronics and remote upgrading, and particularly relates to an OTA upgrading system and method dynamically supporting software updating of newly added controllers. BACKGROUND

[0002] Remote OTA (Over-the-Air) upgrading technology is a key means to realize remote iteration of automotive software, which can complete the updating of automotive controller software through network without the user going to a 4S store, greatly improving the convenience and timeliness of software upgrading, and also reducing the after-sales maintenance cost of the vehicle manufacturer and improving the user experience. At present, the existing OTA upgrading system can realize software upgrading of controllers configured when the vehicle is shipped, and the core logic is to pre-embed the part information reading method, communication protocol and upgrading process of each controller in the vehicle host system, and to perform upgrading operation by matching the preset controller information.

[0003] However, in the current rapid development of the automotive industry, the existing OTA upgrading system has significant technical defects and cannot meet the needs of industry development: first, it cannot adapt to dynamically added controllers. With model upgrades, configuration upgrades or user personalized options, vehicles may add various controllers after shipment (such as controllers corresponding to newly added intelligent driving assistance modules, controllers corresponding to newly added vehicle entertainment system expansion modules, etc.), and the existing OTA upgrading system does not pre-store the related configuration information (including part information reading method, upgrading method, etc.) of these newly added controllers in the vehicle host system, resulting in the inability to remotely OTA upgrade these newly added controllers. If upgrading is to be achieved, the user needs to take the vehicle to a maintenance site for local upgrading through special equipment, which seriously affects the user experience and goes against the core advantage of OTA upgrading technology. Second, the system has poor expandability. The adaptation capability of the existing OTA upgrading system depends on the pre-configuration of the vehicle host system, and each time a new type of controller is added, the software of the vehicle host system needs to be redeveloped, tested and upgraded, which not only increases the development cost and cycle of the vehicle manufacturer, but also may cause new compatibility problems due to host system upgrading, and cannot realize unlimited expansion of controller types, making it difficult to meet the needs of rapid iteration of controllers in the automotive industry. Third, the upgrading efficiency is low. For the upgrading of newly added controllers, the existing technology needs to go through the multi-step process of "vehicle host system adaptation development - host system OTA upgrading - newly added controller OTA upgrading", which takes a long time and requires the user to cooperate multiple times, and cannot realize the rapid and real-time upgrading of newly added controllers. SUMMARY

[0004] The application aims to solve the problems in the prior art and provides an OTA upgrade system and method for dynamically supporting software update of a newly added controller.

[0005] To achieve the above object, the application adopts the following technical scheme: an OTA upgrade system for dynamically supporting software update of a newly added controller, comprising an OTA background server and a vehicle-mounted host system, which are connected through a wireless communication network (such as 4G, 5G, Internet of Vehicles, etc.) to cooperatively complete software upgrade of the newly added controller.

[0006] The OTA background server is configured to support management of part information of the newly added controller, receive and store upgrade original files of the newly added controller, combine the upgrade original files with the part information to generate an OTA upgrade package, configure part information reading mode and software upgrade mode and generate a configuration file, and create an OTA upgrade task associated with a target vehicle VIN and associate the upgrade task with the configuration file.

[0007] The part information management module is used to receive part information of the newly added controller input by an operator, and the part information includes controller name, controller part number, controller supplier code, controller software version number and controller hardware version number. The module performs format checking (such as checking the coding rules of the part number and the format of the version number) on the input information to ensure the integrity and validity of the information, and stores the part information that passes the checking in a database.

[0008] The upgrade original file processing module is used to receive upgrade original files (including software installation package, program patch, complete firmware file, etc.) of the newly added controller uploaded by the operator, perform integrity checking (by calculating MD5 value, SHA256 value, etc.) and virus killing on the upgrade original files to avoid invalid files or malicious files from entering the system, and store the upgrade original files that pass the checking in a designated file server.

[0009] The OTA upgrade package generation module communicates with the part information management module and the upgrade original file processing module, obtains the part information and the upgrade original files that pass the checking, combines them by using a preset packing algorithm (such as ZIP packing algorithm, custom encryption packing algorithm, etc.) to generate an OTA upgrade package, and the OTA upgrade package contains the upgrade original files, part information, encryption identifier and check code, wherein the check code is used to verify the integrity of the upgrade package by the vehicle-mounted host system to prevent the upgrade package from being tampered with or damaged in the transmission process.

[0010] The configuration file generation module is configured to receive the part information reading mode and the software upgrade mode configured by the operator for the new controller, and automatically generate a configuration file according to the configuration information, wherein the configuration file adopts a resolvable format (such as XML, JSON, etc.), and the part information reading mode specifies the specific implementation method of the vehicle host system for obtaining each part information parameter (such as obtaining the controller name through a specific ID frame of the CAN bus, reading the supplier code through the TCP / IP protocol of the Ethernet, etc.), and the software upgrade mode specifies the key parameters of the upgrade process (such as the upgrade sequence, the upgrade priority, the power-off protection mechanism, the breakpoint resume mechanism, the upgrade timeout threshold, etc.).

[0011] The upgrade task management module is configured to establish the association between the OTA upgrade package and the target vehicle VIN (vehicle identification number), create an OTA upgrade task, associate the upgrade task with the configuration file, and simultaneously manage the state of the upgrade task in real time (such as to be executed, in execution, success, failure, etc.), receive the upgrade state information reported by the vehicle host system, and form a complete upgrade log.

[0012] Preferably, the part information reading mode includes a method for obtaining the controller name, a method for obtaining the controller part number, a method for obtaining the controller supplier code, a method for obtaining the controller software version number, and a method for obtaining the controller hardware version number.

[0013] The vehicle host system is in communication connection with the OTA background server, and is configured as an upgrade task parsing module for parsing the configuration file in the upgrade task, a part information reading module for reading the real-time part information of the new controller according to the configuration file, an information matching module for matching the real-time part information with the part information in the OTA upgrade package, and an upgrade execution module for performing a corresponding upgrade operation or prompting operation according to the matching result.

[0014] The vehicle host system is installed in the vehicle, and is in communication connection with each controller (including the original controller and the new controller) of the vehicle through a vehicle network (such as the CAN bus, the Ethernet, the LIN bus, etc.), and has the functions of upgrade task acquisition, configuration parsing, information reading, and upgrade execution, and the specific configuration is as follows: The upgrade task parsing module is configured to receive the OTA upgrade task issued by the OTA background server, parse the configuration file in the upgrade task, and extract the part information reading mode and the software upgrade mode, thereby providing a basis for subsequent information reading and upgrade execution.

[0015] The zero component information reading module reads the real-time zero component information of the new controller (including controller name, controller zero component number, controller supplier code, controller software version number, and controller hardware version number) according to the specified communication protocol and data format, and performs format conversion and preprocessing on the read information, so as to perform information matching, through the vehicle-mounted network and the new controller, according to the zero component information reading mode extracted from the configuration file.

[0016] The information matching module compares the preprocessed real-time zero component information with the zero component information contained in the OTA upgrade package one by one, and the specific comparison logic is: judging whether the controller name, controller zero component number, controller supplier code, and controller hardware version number are consistent, and whether the controller software version number is different; if the above conditions are met, it is determined that the matching is successful, and the subsequent upgrade process is triggered; if not, it is determined that the matching fails, and an error prompt is output.

[0017] The upgrade execution module sends an upgrade instruction to the new controller through the vehicle-mounted network according to the software upgrade mode specified in the configuration file after the information matching is successful and the user confirms the upgrade, transmits the upgrade original file (supports breakpoint resume, if the network is interrupted during transmission, it can continue transmission from the breakpoint after the network is restored), monitors various state parameters (such as transmission progress, controller response state, and upgrade step execution situation) during the upgrade process, and executes the power-off protection mechanism (if the vehicle is accidentally powered off during the upgrade process, the upgrade process can be resumed after power-on again, avoiding damage to the controller firmware).

[0018] Preferably, the vehicle-mounted host system and the OTA background server are respectively provided with a vehicle-mounted host system communication module and an OTA background server communication module; the OTA background server communication module provides a communication interface with the vehicle-mounted host system, supports communication based on HTTP, HTTPS, MQTT, and the like, and realizes functions such as upgrade task issuing, upgrade state reporting, and data interaction; the vehicle-mounted host system communication module is adapted to the communication module of the OTA background server, establishes a stable communication connection with the OTA background server through a wireless communication network, and realizes data transmission such as upgrade task acquisition and state reporting.

[0019] Preferably, the vehicle-mounted host system further comprises a man-machine interaction module and a state reporting module; the man-machine interaction module provides a visual operation interface, shows the user prompt information related to upgrading (such as "there is an OTA upgrading task, please confirm upgrading" and "information matching error", etc.), receives the user's operation instructions (such as confirming upgrading and canceling upgrading), and displays the upgrading progress, the remaining time of upgrading and the current upgrading state (such as "upgrading (30%) " and "upgrading success", etc.) in real time; the state reporting module reports the information matching result and the upgrading execution state (success, failure, retry, etc.) to the OTA background server in real time, so as to facilitate the OTA background server to monitor and manage the upgrading task.

[0020] The OTA upgrading system dynamically supporting the software updating of the newly added controller further comprises an OTA upgrading method dynamically supporting the software updating of the newly added controller, comprising the following steps: S1: the OTA background server creates an OTA upgrading task, specifically comprising: S11: the operator accesses the OTA background server through a terminal device; enters the part information of the newly added controller in the OTA background server; the part information comprises the controller name, the controller part number, the controller supplier code, the controller software version number and the controller hardware version number; S12: the operator uploads the upgrading original file of the newly added controller to the OTA background server through the terminal device; S13: after receiving the upgrading original file, the OTA background server automatically combines the upgrading original file with the part information to generate an OTA upgrading package; S14: the operator configures the part information reading mode and the software upgrading mode of the newly added controller in the OTA background server through the terminal device; the part information reading mode comprises a specific implementation method of obtaining each part information parameter; S15: the OTA background server automatically generates a corresponding configuration file according to the configured part information reading mode and software upgrading mode; S16: the operator establishes the association between the OTA upgrading package and the target vehicle VIN in the OTA background server through the terminal device, creates an OTA upgrading task, and the OTA background server automatically establishes the association between the upgrading task and the configuration file; S2: the vehicle-mounted host system triggers and executes upgrading, specifically comprising: S21: After the vehicle is powered on, the vehicle host system starts and establishes a communication connection with the OTA background server, sends an upgrade task acquisition request to the OTA background server according to the vehicle VIN, and receives the OTA upgrade task corresponding to the vehicle returned by the OTA background server; S22: The vehicle host system parses the configuration file in the OTA upgrade task, extracts the component information reading mode and the software upgrade mode, and reads the real-time component information of the vehicle-end new controller according to the component information reading mode; S23: The vehicle host system compares the read real-time component information with the component information contained in the OTA upgrade package, judges whether the controller name, controller component number, controller supplier code and controller hardware version number are consistent, and whether the controller software version number is different; S24: If the comparison result is inconsistent, it is determined that the matching fails, the vehicle host system does not trigger the upgrade process, outputs an "information matching error" prompt on its display interface, and reports an "information matching error" status to the OTA background server; S25: If the comparison result is that the controller name, controller component number, controller supplier code and controller hardware version number are consistent and the controller software version number is different, it is determined that the matching is successful, and the vehicle host system outputs an "OTA upgrade task, please confirm upgrade" prompt on its display interface; S26: If the user selects "cancel upgrade" through the interactive interface of the vehicle host system, the vehicle host system exits the upgrade interface, and re-executes steps S21-S25 after the vehicle is powered on and started next time; S27: If the user selects "confirm upgrade" through the interactive interface of the vehicle host system, the vehicle host system performs software update operation on the new controller according to the software upgrade mode specified in the configuration file, and triggers the upgrade process; S28: If a failure occurs during the upgrade process, the vehicle host system automatically triggers the upgrade again, and if the upgrade fails for three consecutive times, reports an "OTA upgrade failure" status to the OTA background server; S29: If the upgrade process is completed normally, the vehicle host system reports an "OTA upgrade success" status to the OTA background server.

[0021] Preferably, in step S11, the OTA background server provides a visual operation interface, an operator enters component information through the visual operation interface, and the OTA background server performs format verification on the entered component information to ensure the integrity and validity of each parameter.

[0022] Preferably, in step S12, the upgrade original file is a software installation package, a program patch or a complete firmware file corresponding to the new controller, and the OTA background server performs integrity check and virus killing on the uploaded upgrade original file.

[0023] Preferably, in step S13, the OTA background server merges the upgrade original file and the part information by using a preset packaging algorithm, and the generated OTA upgrade package contains an encryption identifier and a check code, and the check code is used for verifying the integrity of the upgrade package by the vehicle host system.

[0024] Preferably, in step S22, the vehicle host system establishes communication with the new controller through a CAN bus, an Ethernet or a LIN bus, and reads real-time part information according to a communication protocol and a data format specified in the part information reading mode.

[0025] Preferably, in step S27, the software upgrade mode includes one or more of an upgrade sequence, an upgrade priority, a power-off protection mechanism in the upgrade process, and an upgrade breakpoint resume mechanism.

[0026] Preferably, during the upgrade process, the vehicle host system shows the user the upgrade progress, the remaining upgrade time and the current upgrade state in real time, and prohibits the execution of operations that affect the upgrade during the upgrade process.

[0027] Compared with the prior art, the present application has the following advantages: the present application realizes dynamic adaptation of new controllers without upgrading the vehicle host system; the present application generates a configuration file in the OTA background server to specify the part information reading mode and the software upgrade mode of the new controller, and the vehicle host system only needs to parse the configuration file to obtain the relevant configuration, without the need for re-development, testing and upgrading of the software of the vehicle host system, thereby solving the technical bottleneck that the new controller needs to rely on the host system adaptation in the prior art, greatly reducing the development cost and cycle of the vehicle manufacturer, and avoiding the compatibility risk brought by the upgrade of the host system.

[0028] Secondly, the core of the present application is to realize dynamic adaptation of the vehicle host system and the new controller through the configuration file, regardless of the type of the new controller (such as intelligent driving controller, vehicle entertainment expansion controller, vehicle body control expansion controller, etc.), as long as the corresponding part information is recorded in the OTA background server, the upgrade original file is uploaded and the relevant reading and upgrade parameters are configured, the corresponding configuration file and OTA upgrade package can be generated to realize OTA upgrade of the controller, which is not limited by the type and number of controllers, and fully meets the needs of rapid iteration of vehicle models and diversification of controllers in the automotive industry.

[0029] Furthermore, the upgrading process of the application does not require the user to go to a maintenance site, and the software upgrading of the newly added controller can be completed through remote OTA, and the entire process has high automation degree, and only simple confirmation operation of the user is required on the vehicle host interface; at the same time, the system has breakpoint resume transmission, power-off protection and other mechanisms to ensure the stability and reliability of the upgrading process, and can automatically retry after upgrading failure, reducing the user operation cost; the progress and state are displayed in real time during the upgrading process, so that the user can clearly understand the upgrading situation, and the user experience is greatly improved.

[0030] Finally, the application adds an encryption identifier and a check code when generating an OTA upgrade package, and uses an HTTPS encrypted channel in the transmission process to prevent the upgrade package from being illegally analyzed, tampered with or stolen; integrity check and virus killing are performed when uploading the original upgrade file to avoid malicious files entering the system; the power-off protection and breakpoint resume transmission mechanism are executed during the upgrading process to prevent the controller firmware from being damaged and ensure the safety and reliability of the upgrading process; at the same time, the application is suitable for various types of newly added controllers of various types of vehicles (fuel vehicles, new energy vehicles, intelligent networked vehicles, etc.), supports various vehicle communication protocols such as CAN bus, Ethernet, LIN bus, etc., can be seamlessly connected with the existing OTA upgrading system, does not require large-scale modification of the existing vehicle hardware and software, has strong compatibility and promotion value. BRIEF DESCRIPTION OF DRAWINGS

[0031] Fig. 1 is a flowchart of the OTA background server creating an OTA upgrade task according to the application; Fig. 2 is a flowchart of the vehicle host system triggering and executing the upgrade according to the application. DETAILED DESCRIPTION

[0032] In order to further understand the purpose, structure, features and functions of the application, the following detailed description is provided in conjunction with the embodiments.

[0033] Please refer to Figure 1 and Figure 2 , the application provides an OTA upgrading method for dynamically supporting software updating of newly added controllers, which includes two links of OTA background server creating an upgrade task and vehicle host system triggering and executing the upgrade, and the specific steps are as follows: S1: The OTA background server creates an OTA upgrade task This link is completed by the operator interacting with the OTA background server through a terminal device (such as a computer, a tablet computer, etc.), and the specific steps are as follows: S11: The operator accesses the visual operation interface of the OTA background server through the terminal device, inputs the login account and password for identity verification, and enters the new controller upgrade configuration page after verification. In this page, the operator enters the part information of the new controller according to the system prompt, and the part information includes the controller name (such as "XXXXX controller"), the controller part number (such as "XXX-20251125"), the controller supplier code (such as "DLS-001"), the controller software version number (such as "V1.0.0"), and the controller hardware version number (such as "H2.1"). The part information management module of the OTA background server performs format checking on the entered parameters, such as checking whether the part number conforms to the "controller type-date" coding rule and whether the version number conforms to the "V + number + number + number" format. If there is a missing parameter or format error, the system will prompt the operator to correct it until the information checking is passed. The part information that passes the checking is stored in the database.

[0034] S12: The operator uploads the upgrade original file of the new controller to the OTA background server through the file upload function in the new controller upgrade configuration page. The upgrade original file is a legal file verified by the vehicle manufacturer test (such as firmware file with.bin suffix, compressed installation package with.zip suffix, etc.). After receiving the upgrade original file, the upgrade original file processing module of the OTA background server calculates the MD5 value for integrity checking and performs security detection on the file through the built-in virus scanning engine. If the file is incomplete or has security risks, the system prompts the operator to upload it again. If the file passes the checking, the upgrade original file is stored in the file server and a unique file index is generated.

[0035] S13: The OTA upgrade package generation module of the OTA background server obtains the upgrade original file from the file server through the file index and obtains the corresponding part information from the database. The upgrade original file and the part information are merged and compressed using the ZIP packaging algorithm to generate the OTA upgrade package. During the packaging process, the system automatically adds an encryption identifier (encrypts the key information in the package using the AES encryption algorithm) and a check code (SHA256 value calculated based on the upgrade original file and the part information) to the OTA upgrade package. The encryption identifier is used to prevent the upgrade package from being illegally parsed, and the check code is used to verify the integrity of the upgrade package by the vehicle host system.

[0036] S14: The operator configures the part information reading method and software upgrade method of the new controller in the new controller upgrade configuration page. Part information reading method configuration: According to the communication protocol and data interface of the new controller, select or customize the acquisition method of each part information parameter.

[0037] Software upgrade mode configuration: Set the upgrade order (such as upgrading the underlying driver first, then upgrading the application), upgrade priority (such as high priority, prohibit other non-critical tasks during the upgrade process), power-off protection mechanism (such as detecting power-off during the upgrade process, immediately saving the current upgrade progress, and automatically resuming the upgrade next time the power is turned on), breakpoint resume mechanism (such as saving a breakpoint every 10% of data transmission, and continuing transmission from the latest breakpoint when reconnecting after network interruption), upgrade timeout threshold (such as setting the timeout time for a single upgrade step to 30 seconds, and retrying if it exceeds), and other parameters.

[0038] S15: The configuration file generation module of the OTA background server automatically generates a configuration file in JSON format according to the part information reading mode and software upgrade mode configured by the operator; the generated configuration file is associated with the corresponding OTA upgrade package through file indexing. S16: The operator inputs the VIN code of the target vehicle (single VIN input or multiple VIN batch import is supported) in the upgrade task creation page of the OTA background server, selects the generated OTA upgrade package, establishes the association between the OTA upgrade package and the target vehicle VIN, and clicks the "Create Upgrade Task" button; after receiving the instruction, the upgrade task management module of the OTA background server creates an OTA upgrade task, assigns a unique task ID, automatically associates the upgrade task with the corresponding configuration file, initializes the upgrade task status to "To be executed", and stores the task information in the task database.

[0039] S2: The vehicle host system triggers and executes the upgrade: This step is automatically triggered after the vehicle is powered on, without the need for operator intervention. The specific steps are: S21: After the vehicle is powered on, the vehicle host system automatically starts, and its communication module establishes an HTTPS connection with the communication module of the OTA background server through the 4G / 5G network, sends an upgrade task acquisition request to the OTA background server, and carries the VIN code of the vehicle in the request; after receiving the request, the upgrade task management module of the OTA background server queries the task database according to the VIN code, obtains the OTA upgrade task corresponding to the VIN (the status is "To be executed"), and downloads the OTA upgrade package (sent through an encrypted transmission channel) and the configuration file to the vehicle host system; after receiving, the vehicle host system stores it in the local storage module (such as vehicle hard disk, flash memory, etc.).

[0040] S22: The upgrade task analysis module of the vehicle host system parses the received configuration file, extracts the component information reading configuration and upgrade configuration, obtains the communication type, CAN ID, TCP port, and other reading parameters of each component information parameter, and the upgrade sequence, priority, and other upgrade parameters; then, the component information reading module of the vehicle host system establishes a communication connection with the new controller through the corresponding vehicle network (CAN bus or Ethernet) according to the component information reading mode obtained by parsing, sends a data reading request according to the specified parameters, receives the response data returned by the new controller, decodes and preprocesses the response data, and extracts the real-time component information (controller name, controller part number, controller vendor code, controller software version number, and controller hardware version number).

[0041] S23: The information matching module of the vehicle host system compares the extracted real-time component information with the component information contained in the OTA upgrade package one by one: First, compare the controller names. If the real-time reading controller name is inconsistent with the controller name in the upgrade package, it is directly determined that the matching fails. If the controller names are consistent, continue to compare the controller part numbers. If they are inconsistent, it is determined that the matching fails. If the controller part numbers are consistent, continue to compare the controller vendor codes. If they are inconsistent, it is determined that the matching fails. If the vendor codes are consistent, continue to compare the controller hardware version numbers. If they are inconsistent, it is determined that the matching fails. If the hardware version numbers are consistent, finally compare the controller software version numbers. If the software version numbers are the same, it is determined that the matching fails (no need to upgrade); if the software version numbers are different, it is determined that the matching succeeds (need to upgrade).

[0042] S24: If the information matching module determines that the matching fails, the human-computer interaction module of the vehicle host system pops up a "information matching error" prompt box on the display interface, and the state reporting module reports the "information matching error" state to the OTA background server through the communication module, and attaches the specific reasons for the matching failure (such as "controller part number inconsistency", "software version number same", etc.); after receiving, the OTA background server updates the upgrade task state to "matching failure", and records the relevant logs.

[0043] S25: If the information matching module determines that the matching succeeds, the human-computer interaction module of the vehicle host system pops up a "there is an OTA upgrade task, please confirm the upgrade" prompt box on the display interface, which contains the upgrade controller name, current software version number, target software version number, upgrade expected time, and other information, and provides "confirm upgrade" and "cancel upgrade" two operation buttons for user selection.

[0044] S26: If the user clicks the "cancel upgrade" button, the human-computer interaction module of the vehicle host system closes the upgrade prompt box, exits the upgrade interface, and at the same time marks the upgrade task state as "user cancellation" and stores it locally; the vehicle host system will re-execute steps S21-S25 and prompt the user again after the next vehicle power-on start.

[0045] S27: If the user clicks the "confirm upgrade" button, the human-computer interaction module of the vehicle host system displays the upgrade progress interface and real-time upgrade state; at the same time, the upgrade execution module executes the upgrade process according to the software upgrade mode obtained by parsing the configuration file and the preset upgrade order: First, send an upgrade preparation instruction to the new controller to inform the controller to enter the upgrade mode; Then, according to the breakpoint resume mechanism, the upgrade original file in the OTA upgrade package is transmitted to the new controller in blocks, and a verification request is sent to the new controller every 10% of the file data transmission, and the transmission continues after confirming that the data reception is correct; During transmission, if a network interruption is detected (such as the vehicle entering a signal-free area), the upgrade execution module suspends transmission and saves the current transmission progress; after the network is restored, it automatically continues transmission from the nearest breakpoint; If it is detected that the vehicle is about to be powered off (such as the user turning off the ignition switch), the upgrade execution module immediately performs a power-off protection operation, saves the upgrade progress, and sends a power-off protection instruction to the new controller to ensure that the current firmware of the controller is not damaged; After the upgrade original file transmission is completed, an upgrade execution instruction is sent to the new controller, and the new controller starts to perform software update operation, and the vehicle host system receives the upgrade progress data feedback from the controller in real time and updates and displays it on the human-computer interaction interface.

[0046] S28: If the new controller feedbacks upgrade failure (such as file parsing error, upgrade step execution timeout, etc.) during the upgrade execution process, the upgrade execution module of the vehicle host system automatically triggers the retry mechanism and re-executes the upgrade process of step S27; if three consecutive retries fail, the upgrade execution module stops the upgrade, the human-computer interaction module displays the prompt "OTA upgrade failed, please contact customer service", the state reporting module reports the "OTA upgrade failed" state to the OTA background server with the failure reason (such as "file transmission timeout" "upgrade step execution failure" etc.); the OTA background server updates the upgrade task state to "upgrade failed" and records the log.

[0047] S29: If the upgrade execution process is successful, the new controller feeds back that the upgrade is completed and the verification is passed, the human-computer interaction module of the vehicle host system displays a prompt of "OTA upgrade success", and the state reporting module reports the "OTA upgrade success" state to the OTA background server; the OTA background server updates the upgrade task state to "upgrade success", records the upgrade completion time, software version numbers before and after the upgrade, and the like, and completes the entire upgrade process.

[0048] The present application has been described by the above-mentioned related embodiments, however, the above-mentioned embodiments are only examples for implementing the present application. It must be pointed out that the disclosed embodiments do not limit the scope of the present application. On the contrary, changes and modifications made without departing from the spirit and scope of the present application are within the scope of the patent protection of the present application.

Claims

1. An OTA upgrade system dynamically supporting new controller software update, characterized in that: The upgrading system comprises an OTA background server and a vehicle-mounted host system; The OTA background server is configured to support a component information management module for managing information of the added controller, a processing module for receiving and storing an original upgrading file of the added controller, an OTA upgrade package generation module for combining the processing module and the component information management module to generate an OTA upgrade package, a configuration file generation module for configuring a component information reading method and a software upgrading method and generating a configuration file, and an upgrading task management module for creating an OTA upgrading task associated with a target vehicle VIN and associating the upgrading task with the configuration file; The vehicle-mounted host system is in communication connection with the OTA background server and is configured to acquire an OTA upgrading task corresponding to a target vehicle, a upgrading task analysis module for analyzing a configuration file in the upgrading task, a component information reading module for reading real-time component information of the added controller according to the configuration file, an information matching module for matching the real-time component information with component information in the OTA upgrade package, and an upgrading execution module for performing a corresponding upgrading operation or prompting operation according to a matching result.

2. The OTA upgrade system dynamically supporting software update of a newly added controller according to claim 1, characterized in that: The component information comprises a controller name, a controller component number, a controller supplier code, a controller software version number and a controller hardware version number.

3. The OTA upgrade system dynamically supporting new controller software update according to claim 1, wherein: The component information reading method comprises a method for acquiring the controller name, a method for acquiring the controller component number, a method for acquiring the controller supplier code, a method for acquiring the controller software version number and a method for acquiring the controller hardware version number.

4. An OTA upgrade method dynamically supporting new controller software update, characterized in that: The method comprises the following steps: S1: the OTA background server creates an OTA upgrading task, specifically comprising: S11: an operator accesses the OTA background server through a terminal device; component information of an added controller is input in the OTA background server; the component information comprises a controller name, a controller component number, a controller supplier code, a controller software version number and a controller hardware version number; S12: the operator uploads an original upgrading file of the added controller to the OTA background server through the terminal device; S13: after receiving the original upgrading file, the OTA background server automatically combines the original upgrading file with the component information to generate an OTA upgrade package; S14: the operator configures a component information reading method and a software upgrading method of the added controller in the OTA background server through the terminal device; the component information reading method comprises a specific implementation method for acquiring each component information parameter; S15: the OTA background server automatically generates a corresponding configuration file according to the configured component information reading method and software upgrading method; S16: the operator establishes an association between the OTA upgrade package and a target vehicle VIN in the OTA background server through the terminal device, creates an OTA upgrading task, and the OTA background server automatically establishes an association between the upgrading task and the configuration file; S2: the vehicle-mounted host system triggers and executes upgrading, specifically comprising: S21: After the vehicle is powered on, the vehicle host system starts and establishes a communication connection with the OTA background server, sends an upgrade task acquisition request to the OTA background server according to the vehicle VIN, and receives the OTA upgrade task corresponding to the vehicle returned by the OTA background server; S22: The vehicle host system parses the configuration file in the OTA upgrade task, extracts the component information reading mode and the software upgrade mode, and reads the real-time component information of the vehicle-end new controller according to the component information reading mode; S23: The vehicle host system compares the read real-time component information with the component information contained in the OTA upgrade package, judges whether the controller name, controller component number, controller supplier code and controller hardware version number are consistent, and whether the controller software version number is different; S24: If the comparison result is inconsistent, it is determined that the matching fails, the vehicle host system does not trigger the upgrade process, outputs "information matching error" prompt on its display interface, and reports "information matching error" status to the OTA background server; S25: If the comparison result is that the controller name, controller component number, controller supplier code and controller hardware version number are consistent and the controller software version number is different, it is determined that the matching is successful, and the vehicle host system outputs "OTA upgrade task, please confirm upgrade" prompt on its display interface; S26: If the user selects "cancel upgrade" through the interactive interface of the vehicle host system, the vehicle host system exits the upgrade interface, and re-executes steps S21-S25 after the vehicle is powered on and started next time; S27: If the user selects "confirm upgrade" through the interactive interface of the vehicle host system, the vehicle host system performs software update operation on the new controller according to the software upgrade mode specified in the configuration file, and triggers the upgrade process; S28: If a failure occurs during the upgrade process, the vehicle host system automatically triggers the upgrade again, and if the upgrade fails for three consecutive times, it reports "OTA upgrade failure" status to the OTA background server; S29: If the upgrade process is completed normally, the vehicle host system reports "OTA upgrade success" status to the OTA background server.

5. The OTA upgrade method of dynamically supporting new controller software updates of claim 4, wherein: In step S11, the OTA background server provides a visual operation interface, and an operator enters component information through the visual operation interface. The OTA background server performs format verification on the entered component information to ensure the integrity and validity of each parameter.

6. The OTA upgrade method of dynamically supporting new controller software updates of claim 4, wherein: In step S12, the upgrade original file is a software installation package, a program patch or a complete firmware file corresponding to the new controller, and the OTA background server performs integrity verification and virus killing on the uploaded upgrade original file.

7. The OTA upgrade method of dynamically supporting new controller software updates of claim 4, wherein: In step S13, the OTA background server merges the upgrade original file and the component information by using a preset packaging algorithm, generates an OTA upgrade package containing an encryption identifier and a check code, and the check code is used for the vehicle host system to verify the integrity of the upgrade package.

8. The OTA upgrade method of dynamically supporting new controller software updates of claim 4, wherein: In step S22, the vehicle host system establishes communication with the new controller through CAN bus, Ethernet or LIN bus, and reads real-time component information according to the communication protocol and data format specified in the component information reading mode.

9. The OTA upgrade method of dynamically supporting new controller software updates of claim 4, wherein: In step S27, the software upgrade mode includes one or more of the following: upgrade sequence, upgrade priority, power-off protection mechanism during upgrade, upgrade breakpoint resume mechanism.

10. The OTA upgrade method of dynamically supporting new controller software updates of claim 4, wherein: During the upgrade process, the vehicle host system shows the user the upgrade progress, the remaining upgrade time and the current upgrade state in real time, and prohibits the execution of operations that affect the upgrade during the upgrade process.

Images