Vehicle production line software upgrading method, system, device and computer readable storage medium

Abstract

The application discloses a whole vehicle production line software upgrading method, system and device and a computer readable storage medium, and belongs to the technical field of whole vehicle production line software upgrading. The whole vehicle production line software upgrading method comprises the following steps: establishing a filling table, the filling table storing a latest version upgrade package and production line data configuration; selecting a master node on a circulating vehicle, the master node setting a whole vehicle flashing component; writing the latest version upgrade package and the production line data configuration into the whole vehicle flashing component through the filling table; performing instruction interaction between a production line server and the whole vehicle flashing component, determining a controller to be upgraded on the circulating vehicle according to current software version information of the circulating vehicle and the latest version upgrade package, and completing the flashing by the whole vehicle flashing component. Before the vehicle is offline, the filling table and the production line server are used to compare the version information of the circulating vehicle and the latest version, the controller which is not the latest version is flashed, and it is ensured that the software of the vehicle when the vehicle is offline from the factory is the latest version.

Description

Technical Field

[0001] This invention relates to the field of vehicle production line software upgrade technology, and in particular to a method, system, device, and computer-readable storage medium for vehicle production line software upgrade. Background Technology

[0002] With the rapid development of the automotive industry, especially the rise of electric and intelligent vehicles, vehicle software has become increasingly complex and critical. Software upgrades are also becoming more frequent.

[0003] To ensure that the software of a vehicle is the latest version when it rolls off the factory line, it is either time-consuming and laborious to update the inventory parts offline, or to have the supplier reship parts with the latest software, which would affect the vehicle assembly schedule. Summary of the Invention

[0004] The purpose of this invention is to provide a method, system, device, and computer-readable storage medium for upgrading the software of a vehicle production line, so as to ensure that the software of a vehicle is the latest version when it rolls off the production line.

[0005] To address the aforementioned technical problems, the present invention provides a method for upgrading software on a vehicle production line, applicable to vehicles in transit on the production line. The method includes: establishing a filling station storing the latest version upgrade package and production line data configuration; selecting a master node on the vehicle in transit and setting up a vehicle flashing component on the master node; writing the latest version upgrade package and production line data configuration into the vehicle flashing component via the filling station; the production line server interacting with the vehicle flashing component to determine the controller on the vehicle requiring upgrade based on the current software version information of the vehicle in transit and the latest version upgrade package; and the vehicle flashing component performing the flashing process on the controller.

[0006] This technical solution has at least the following beneficial effects: before the vehicle rolls off the production line, the version information of the circulating vehicles is compared with the latest version through the filling station and the production line server. Controllers that are not the latest version are flashed, thereby ensuring that the software of the vehicle is the latest version when it rolls off the production line.

[0007] Optionally, the transfer vehicle is equipped with a cockpit domain control, and the step of selecting a master node on the transfer vehicle includes: The cockpit domain controller on the circulating vehicle is selected as the master node.

[0008] Optionally, the method further includes: The cockpit domain controller provides a user interface. The controller being flashed and the upgrade information are displayed on the user interface via the cockpit domain controller; The upgrade of the controller being upgraded is triggered by operating the user interface.

[0009] Optionally, the method further includes: The cockpit domain controller obtains the flashing progress and flashing result of the controller being flashed; The flashing progress and flashing results are displayed on the user interface.

[0010] Optionally, the software flashing component and the production line server are connected via Wi-Fi, and the software flashing component can support manual input of the Wi-Fi name and password.

[0011] Optionally, the method further includes: The master node diagnoses the mode changes of the circulating vehicles; When the mode of the circulating vehicle is switched to the production line flashing mode, the whole vehicle flashing component callback is triggered.

[0012] Optionally, the method further includes: Upgrades or rewrites are refused for the integrated chassis controller or cockpit controller, dual redundant microcontroller combination, parking assistance system, engine management system, integrated brake-by-wire system, battery management system, and highly automated driving system on the aforementioned vehicles.

[0013] A second aspect of the present invention provides a software upgrade system for a complete vehicle production line, applied to vehicles in transit on the production line, the system comprising: The master node is configured to select the circulating vehicle and set the whole vehicle flashing component; The filling station is configured to store the latest version upgrade package and production line data configuration, and to write the latest version upgrade package and production line data configuration to the vehicle flashing component; The production line server is configured to: read the version information of the circulating vehicles and interact with the vehicle flashing component to determine the controllers on the circulating vehicles that need to be upgraded; the vehicle flashing component is configured to complete the flashing of the controllers.

[0014] A third aspect of the present invention provides an apparatus including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform any of the above-described methods for upgrading software on a vehicle production line.

[0015] A fourth aspect of the present invention provides a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute any of the above-described methods for upgrading software on a vehicle production line when run on a computer or processor. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings: Figure 1 This is a flowchart of a vehicle production line software upgrade method according to an embodiment of the present invention; Figure 2 This is a structural block diagram of the vehicle production line software upgrade system according to an embodiment of the present invention. Detailed Implementation

[0017] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention. It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. According to an embodiment of the present invention, an embodiment of a method for upgrading software in a vehicle production line is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system containing at least a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here. This method embodiment can also be executed in an electronic system / device containing a memory and a processor, a similar control system, or in the cloud. Taking an electronic system / device as an example, the electronic system / device may include one or more processors and a memory for storing data. Optionally, the aforementioned electronic system / device may also include communication devices for communication functions and display devices. Those skilled in the art will understand that the above structural description is merely illustrative and does not limit the structure of the aforementioned electronic system / device. For example, the electronic system / device may also include more or fewer components than those described above, or have a different configuration than those described above. A processor may include one or more processing units. For example, a processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microcontroller unit (MCU), a field-programmable gate array (FPGA), a neural network processing unit (NPU), a tensor processing unit (TPU), and artificial intelligence (AI) type processors, etc. Different processing units may be independent components or integrated into one or more processors. In some instances, an electronic system may also include one or more processors. The memory can be used to store computer programs, such as the computer program corresponding to the method in the embodiments of the present invention. The processor implements the above-described method by running the computer program stored in the memory. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the electronic system via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. like Figure 1 As shown, a software upgrade method for a complete vehicle production line is applied to vehicles in transit on the production line. Here, "vehicles in transit on the production line" refers to automobiles / vehicles currently being manufactured on the line.

[0018] The software upgrade method for the entire vehicle production line includes the following steps: Step S100: Establish a filling station, which stores the latest version upgrade package and production line data configuration; select the master node on the circulating vehicle, and set the whole vehicle flashing component on the master node.

[0019] The filling station stores the latest version upgrade packages and production line data configurations. The version upgrade packages are generated from the baseline vehicle version compiled by R&D and then sent to the production line for storage. The filling station also stores basic information about the version upgrade packages. The production line data configurations, also known as critical configuration data, include things like the Vehicle Identification Number (VIN), Wi-Fi connection parameters, and the production line server interface (UFL).

[0020] Furthermore, a controller is selected as the master node on the transferred vehicle. When the vehicle's electronic and electrical architecture is domain-controlled, it may include a vehicle control domain, an intelligent driving domain, and an intelligent cockpit domain. In this embodiment, when the transferred vehicle is divided into a cockpit domain, the intelligent cockpit domain controller can be selected as the master node; the intelligent cockpit domain controller can be simply referred to as the cockpit domain controller. Depending on different scenarios, conditions, or requirements, in some other embodiments, a vehicle control domain controller or an intelligent driving domain controller can also be selected as the controller. In other embodiments, the vehicle's electronic and electrical architecture may also include five domains: powertrain domain, chassis domain, body domain, infotainment domain, and autonomous driving domain; in this case, the controller of one of these domains can also be selected as the master node.

[0021] The master node / cockpit domain controller is equipped with a vehicle flashing component. Essentially, the master node acts as the deployment controller for this component. It handles the production line flashing process, enabling rapid, batch, and automated flashing and activation of the software on vehicles in circulation.

[0022] Step S200: Write the latest version upgrade package and production line data configuration into the vehicle flashing component via the filling station.

[0023] The filling station is located on or near the production line and is connected to the master node via a wired connection. Specifically, the filling station is connected to the cabin domain controller via a solid wire for communication. It should be noted that a filling station refers to the station that handles the data transfer into the vehicle by filling bags; hence, it is called a filling station.

[0024] The filling station stores key configuration data into the master node / cockpit domain controller via diagnostics to ensure the automated process of the production line is completed. The relevant data configuration is defined according to the vehicle model diagnostic specifications, requiring diagnostics to be implemented no later than the trial production stage; in other words, diagnostics must be completed before the product rolls off the production line. Specifically, when selecting the master node, the master node / cockpit domain controller must be configured to store key configuration data via diagnostics.

[0025] Understandably, the production line flashing process requires loading the upgrade package onto the master node. The master node must support the UDS 0x38 RequestDownload, 0x36 TransferData, and 0x37 RequestTransferExit service processes to receive the upgrade file and write it to the specified file system directory. It is required that the maxNumberOfBlockLength corresponding to 0x38 be no less than 0xF000 to maximize transmission efficiency.

[0026] In step S300, the production line server interacts with the vehicle flashing component to determine the controllers that need to be upgraded on the vehicle based on the current software version information and the latest version upgrade package; the vehicle flashing component then completes the flashing of the controllers.

[0027] Specifically, the vehicle flashing component connects to the production line server via a Wi-Fi link. To ensure the vehicle flashing component can accurately and securely access the production line server, the master node also needs to support writing the factory server / production line server address. Production line software flashing connects to external Wi-Fi via a Wi-Fi module. The target vehicle requiring upgrade communicates with the production line server through a network of routers deployed on the production line. The Wi-Fi access controller needs to add specific ports to the whitelist to allow access when the software flashing component / vehicle flashing component connects to external Wi-Fi.

[0028] The Wi-Fi module must support Wi-Fi configuration management for the production line flashing mode of the whole vehicle flashing components.

[0029] When writing dynamically: the Wi-Fi module controller must support writing the Wi-Fi SSID and password through the diagnostic service; the master node / cabin domain controller must support manual input of the Wi-Fi SSID and password in the production line environment.

[0030] The network policy is as follows: after dynamically writing Wi-Fi parameters, the network must remain connected, and it can automatically connect to the corresponding network when entering the local area network range.

[0031] The production line server has the current software version information of the controllers in the vehicles in circulation and performs an online comparison with the latest version upgrade obtained by the master node / cockpit domain controller. This allows it to determine which controllers in the vehicles have outdated software versions, thus identifying the controllers that need to be upgraded / flashed. The vehicle flashing component then performs the flashing / upgrade on these controllers. The master node needs to support OTA (Over-The-Air) interface reading for vehicle-side components, enabling the vehicle flashing component to flash / upgrade the controllers.

[0032] Before a vehicle rolls off the production line, this invention compares the version information of the circulating vehicles with the latest version through the filling station and production line server. Controllers that are not the latest version are then flashed, ensuring that the software of the vehicle is the latest version when it rolls off the factory. This eliminates the need for suppliers to reship goods or for offline processing of inventory parts, making the operation convenient and flexible.

[0033] In one embodiment, the display of the circulating vehicle can also provide a user interface. When the master node is a cockpit domain controller, the cockpit domain controller can control the display to provide the user interface. The cockpit domain controller provides an APP interface on the display to trigger upgrades. The controller to be upgraded and upgrade information are displayed on the user interface through the cockpit domain controller, and the upgrade of the controller to be upgraded is triggered by operating the user interface.

[0034] Meanwhile, the cockpit domain controller also obtains the flashing progress and flashing results of the controller being flashed, and displays the flashing progress and flashing results on the user interface.

[0035] For example, the vehicle-mounted trigger app includes an interface display and navigation. Upon entering the workstation selection interface, four options are displayed: Flashing Stage 1, Flashing Stage 2, Rework, and Preparation. Clicking Flashing Stage 1 or Flashing Stage 2 prompts for secondary confirmation, asking if it's the target workstation. Confirmation completes the process; cancellation returns to the previous workstation selection interface. After receiving progress signals from the vehicle-side components, the vehicle-mounted trigger app displays the progress, including the title "Production Line Upgrading in Progress" and the upgrade progress of each controller being flashed. Upon receiving the upgrade result instruction, the app exits the progress interface and displays an upgrade result pop-up. The success / failure pop-ups in the vehicle-mounted trigger app must include a confirmation button; clicking the confirmation button returns the user to the workstation selection interface.

[0036] The production line flashing mode switch serves as a trigger signal, and the master node can notify the vehicle flashing component to switch the production line flashing mode in the following two ways: Method 1: The master node diagnoses changes in the vehicle's mode. When the vehicle's mode switches to production line flashing mode, a callback of the whole vehicle flashing component is triggered. The master node can determine through diagnostics that the VehicleMode in-vehicle bus signal has been set to production line flashing mode, triggering the whole vehicle flashing component callback. For example, this diagnostic method is triggered when a vehicle is subsequently taken to a 4S store and a diagnostic tool is connected.

[0037] Method 2: Vehicle-mounted APP triggering method. This method requires the master node / cockpit domain controller to enable vehicle-mounted APP triggering and support quick application installation and uninstallation. After clicking the vehicle-mounted option and confirming, a signal must be notified to the master node. Clicking "Flash Section 1" or "Flash Section 2" requires triggering a mode switching interface callback with workstation input parameters. Clicking the "Rework / Maintenance" option requires triggering a mode switching interface callback with workstation identifier input parameters.

[0038] In addition, the production line flashing and upgrade process requires two-way authentication, and the system time synchronization must conform to physical time (mainly the requirement for the production line server), with the error not exceeding the certificate validity period, to avoid the vehicle-cloud communication authentication from becoming invalid.

[0039] In one embodiment, the production line flashing and upgrade controller requires the supplier to have basic software and support diagnostic flashing. This involves controllers for functions such as start-up, high-voltage, driving, and parking, and the upgrade failure / abnormal state must not affect the vehicle's ability to reach the rework area. Furthermore, the production line flashing and upgrade controller designer (e.g., in this case, the parking controller IBC, referring to the IBC controller designer) needs to provide the flashing time and upgrade power consumption, which the factory will then evaluate and plan. Before pushing the package to the factory, the designer will conduct self-testing and submit it to the laboratory for testing, determining and providing the flashing time and upgrade power consumption based on the test results.

[0040] In one embodiment, the vehicle production line software upgrade method also refuses to upgrade or rewrite the integrated chassis controller or cockpit controller (ICC), dual redundant microcontroller combination (MCU1, MCU2), parking assistance system (PDC-S, PDC-M, PDC-T), engine management system (EMS), integrated brake-by-wire system (IBC), battery management system (BMS), and highly automated driving system (HAD) on the vehicles in circulation.

[0041] It should be noted that the software upgrade packages for integrated chassis controller or cockpit controller (ICC), dual redundant microcontroller combination (MCU1, MCU2), parking assistance system (PDC-S, PDC-M, PDC-T), engine management system (EMS), integrated brake-by-wire system (IBC), battery management system (BMS), and highly automated driving system (HAD) are relatively large. Instead of being pre-stored and then identified and flashed through cockpit domain control, they are directly flashed on-site via OBD.

[0042] In one embodiment, the near-field server is connected to the master node. Researchers can also remotely compare the information in the pre-set upgrade package of the cockpit domain controller through the near-field server, and then confirm to perform the flashing operation. Researchers do not need to go to the site to realize the operation between the researchers and the vehicle.

[0043] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention. This embodiment also provides a vehicle production line software upgrade system, which is used to implement the above embodiments and preferred embodiments, and will not be repeated as already described. As used below, the term "module" refers to a combination of software and / or hardware that can perform a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0044] like Figure 2 As shown, a vehicle production line software upgrade system is applied to vehicles moving along the production line. The vehicle production line software upgrade system includes: The master node is configured to select the circulating vehicle and set the whole vehicle flashing component; The filling station is configured to store the latest version upgrade package and production line data configuration, and to write the latest version upgrade package and production line data configuration to the vehicle flashing component; The production line server is configured to read the version information of the vehicles in circulation and interact with the vehicle flashing component to determine the controllers on the vehicles that need to be upgraded; the vehicle flashing component is configured to complete the flashing of the controllers.

[0045] The filling station stores the latest version upgrade packages and production line data configurations. The version upgrade packages are generated from the baseline vehicle version compiled by R&D and then sent to the production line for storage. The filling station also stores basic information about the version upgrade packages. The production line data configurations, also known as critical configuration data, include things like the Vehicle Identification Number (VIN), Wi-Fi connection parameters, and the production line server interface (UFL).

[0046] Furthermore, a controller is selected as the master node on the transferred vehicle. When the vehicle's electronic and electrical architecture is domain-controlled, it may include a vehicle control domain, an intelligent driving domain, and an intelligent cockpit domain. In this embodiment, when the transferred vehicle is divided into a cockpit domain, the intelligent cockpit domain controller can be selected as the master node; the intelligent cockpit domain controller can be simply referred to as the cockpit domain controller. Depending on different scenarios, conditions, or requirements, in some other embodiments, a vehicle control domain controller or an intelligent driving domain controller can also be selected as the controller. In other embodiments, the vehicle's electronic and electrical architecture may also include five domains: powertrain domain, chassis domain, body domain, infotainment domain, and autonomous driving domain; in this case, the controller of one of these domains can also be selected as the master node.

[0047] The master node / cockpit domain controller is equipped with a vehicle flashing component. Essentially, the master node acts as the deployment controller for this component. It handles the production line flashing process, enabling rapid, batch, and automated flashing and activation of the software on vehicles in circulation.

[0048] The filling station is located on or near the production line and is connected to the master node via a wired connection. Specifically, the filling station is connected to the cabin domain controller via a solid wire for communication. It should be noted that a filling station refers to the station that handles the data transfer into the vehicle by filling bags; hence, it is called a filling station.

[0049] The filling station stores key configuration data into the master node / cockpit domain controller via diagnostics to ensure the automated process of the production line is completed. The relevant data configuration is defined according to the vehicle model diagnostic specifications, requiring diagnostics to be implemented no later than the trial production stage; in other words, diagnostics must be completed before the product rolls off the production line. Specifically, when selecting the master node, the master node / cockpit domain controller must be configured to store key configuration data via diagnostics.

[0050] Understandably, the production line flashing process requires loading the upgrade package onto the master node. The master node must support the UDS 0x38 RequestDownload, 0x36 TransferData, and 0x37 RequestTransferExit service processes to receive the upgrade file and write it to the specified file system directory. It is required that the maxNumberOfBlockLength corresponding to 0x38 be no less than 0xF000 to maximize transmission efficiency.

[0051] Specifically, the vehicle flashing component connects to the production line server via a Wi-Fi link. To ensure the vehicle flashing component can accurately and securely access the production line server, the master node also needs to support writing the factory server / production line server address. Production line software flashing connects to external Wi-Fi via a Wi-Fi module. The target vehicle requiring upgrade communicates with the production line server through a network of routers deployed on the production line. The Wi-Fi access controller needs to add specific ports to the whitelist to allow access when the software flashing component / vehicle flashing component connects to external Wi-Fi.

[0052] The Wi-Fi module must support Wi-Fi configuration management for the production line flashing mode of the whole vehicle flashing components.

[0053] When writing dynamically: the Wi-Fi module controller must support writing the Wi-Fi SSID and password through the diagnostic service; the master node / cabin domain controller must support manual input of the Wi-Fi SSID and password in the production line environment.

[0054] The network policy is as follows: after dynamically writing Wi-Fi parameters, the network must remain connected, and it can automatically connect to the corresponding network when entering the local area network range.

[0055] The production line server has the current software version information of the controllers in the vehicles in circulation and performs an online comparison with the latest version upgrade obtained by the master node / cockpit domain controller. This allows it to determine which controllers in the vehicles have outdated software versions, thus identifying the controllers that need to be upgraded / flashed. The vehicle flashing component then performs the flashing / upgrade on these controllers. The master node needs to support OTA (Over-The-Air) interface reading for vehicle-side components, enabling the vehicle flashing component to flash / upgrade the controllers.

[0056] Before a vehicle rolls off the production line, this invention compares the version information of the circulating vehicles with the latest version through the filling station and production line server. Controllers that are not the latest version are then flashed, ensuring that the software of the vehicle is the latest version when it rolls off the factory. This eliminates the need for suppliers to reship goods or for offline processing of inventory parts, making the operation convenient and flexible.

[0057] In one embodiment, the display of the circulating vehicle can also provide a user interface. When the master node is a cockpit domain controller, the cockpit domain controller can control the display to provide the user interface. The cockpit domain controller provides an APP interface on the display to trigger upgrades. The controller to be upgraded and upgrade information are displayed on the user interface through the cockpit domain controller, and the upgrade of the controller to be upgraded is triggered by operating the user interface.

[0058] Meanwhile, the cockpit domain controller also obtains the flashing progress and flashing results of the controller being flashed, and displays the flashing progress and flashing results on the user interface.

[0059] For example, the vehicle-mounted trigger app includes an interface display and navigation. Upon entering the workstation selection interface, four options are displayed: Flashing Stage 1, Flashing Stage 2, Rework, and Preparation. Clicking Flashing Stage 1 or Flashing Stage 2 prompts for secondary confirmation, asking if it's the target workstation. Confirmation completes the process; cancellation returns to the previous workstation selection interface. After receiving progress signals from the vehicle-side components, the vehicle-mounted trigger app displays the progress, including the title "Production Line Upgrading in Progress" and the upgrade progress of each controller being flashed. Upon receiving the upgrade result instruction, the app exits the progress interface and displays an upgrade result pop-up. The success / failure pop-ups in the vehicle-mounted trigger app must include a confirmation button; clicking the confirmation button returns the user to the workstation selection interface.

[0060] The production line flashing mode switch serves as a trigger signal, and the master node can notify the vehicle flashing component to switch the production line flashing mode in the following two ways: Method 1: The master node diagnoses changes in the vehicle's mode. When the vehicle's mode switches to production line flashing mode, a callback of the whole vehicle flashing component is triggered. The master node can determine through diagnostics that the VehicleMode in-vehicle bus signal has been set to production line flashing mode, triggering the whole vehicle flashing component callback. For example, this diagnostic method is triggered when a vehicle is subsequently taken to a 4S store and a diagnostic tool is connected.

[0061] Method 2: Vehicle-mounted APP triggering method. This method requires the master node / cockpit domain controller to enable vehicle-mounted APP triggering and support quick application installation and uninstallation. After clicking the vehicle-mounted option and confirming, a signal must be notified to the master node. Clicking "Flash Section 1" or "Flash Section 2" requires triggering a mode switching interface callback with workstation input parameters. Clicking the "Rework / Maintenance" option requires triggering a mode switching interface callback with workstation identifier input parameters.

[0062] In addition, the production line flashing and upgrade process requires two-way authentication, and the system time synchronization must conform to physical time (mainly the requirement for the production line server), with the error not exceeding the certificate validity period, to avoid the vehicle-cloud communication authentication from becoming invalid.

[0063] In one embodiment, the production line flashing and upgrade controller requires the supplier to have basic software and support diagnostic flashing. This involves controllers for functions such as start-up, high-voltage, driving, and parking, and the upgrade failure / abnormal state must not affect the vehicle's ability to reach the rework area. Furthermore, the production line flashing and upgrade controller designer (e.g., in this case, the parking controller IBC, referring to the IBC controller designer) needs to provide the flashing time and upgrade power consumption, which the factory will then evaluate and plan. Before pushing the package to the factory, the designer will conduct self-testing and submit it to the laboratory for testing, determining and providing the flashing time and upgrade power consumption based on the test results.

[0064] In one embodiment, the vehicle production line software upgrade method also refuses to upgrade or rewrite the integrated chassis controller or cockpit controller (ICC), dual redundant microcontroller combination (MCU1, MCU2), parking assistance system (PDC-S, PDC-M, PDC-T), engine management system (EMS), integrated brake-by-wire system (IBC), battery management system (BMS), and highly automated driving system (HAD) on the vehicles in circulation.

[0065] It should be noted that the software upgrade packages for integrated chassis controller or cockpit controller (ICC), dual redundant microcontroller combination (MCU1, MCU2), parking assistance system (PDC-S, PDC-M, PDC-T), engine management system (EMS), integrated brake-by-wire system (IBC), battery management system (BMS), and highly automated driving system (HAD) are relatively large. Instead of being pre-stored and then identified and flashed through cockpit domain control, they are directly flashed on-site via OBD.

[0066] In one embodiment, the near-field server is connected to the master node. Researchers can also remotely compare the information in the pre-set upgrade package of the cockpit domain controller through the near-field server, and then confirm to perform the flashing operation. Researchers do not need to go to the site to realize the operation between the researchers and the vehicle.

[0067] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0068] Embodiments of the present invention also provide an apparatus including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to execute a vehicle production line software upgrade method as described in any of the above embodiments.

[0069] Optionally, in this embodiment, the processor in the above-described device may be configured to run a computer program to execute the steps of the control method in the foregoing embodiments: Step S100: Establish a filling station, which stores the latest version upgrade package and production line data configuration; select the master node on the circulating vehicle, and set the whole vehicle flashing component on the master node; Step S200: Write the latest version upgrade package and production line data configuration into the vehicle flashing component via the filling station; In step S300, the production line server interacts with the vehicle flashing component to determine the controllers that need to be upgraded on the vehicle based on the current software version information and the latest version upgrade package; the vehicle flashing component then completes the flashing of the controllers.

[0070] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0071] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute, when run on a computer or processor, a method for upgrading a vehicle production line software as described in any of the above embodiments.

[0072] Optionally, in this embodiment, the computer program described above may be configured to store a computer program for performing the control method steps in the foregoing embodiments: Step S100: Establish a filling station, which stores the latest version upgrade package and production line data configuration; select the master node on the circulating vehicle, and set the whole vehicle flashing component on the master node; Step S200: Write the latest version upgrade package and production line data configuration into the vehicle flashing component via the filling station; In step S300, the production line server interacts with the vehicle flashing component to determine the controllers that need to be upgraded on the vehicle based on the current software version information and the latest version upgrade package; the vehicle flashing component then completes the flashing of the controllers.

[0073] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here. In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. In some embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The system embodiments described above are merely illustrative; for example, the division of modules can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between modules may be electrical or other forms.

[0074] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0075] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for upgrading software on a vehicle production line, applied to vehicles in transit on the production line, characterized in that, The method includes: A filling station is established, which stores the latest version upgrade package and production line data configuration; Select a main node on the circulating vehicle, and set a whole vehicle flashing component on the main node; The latest version upgrade package and the production line data configuration are written into the vehicle flashing component through the filling station; The production line server interacts with the vehicle flashing component to determine the controller that needs to be upgraded on the vehicle based on the current software version information of the vehicle and the latest version upgrade package. The vehicle flashing component completes the flashing of the controller being flashed.

2. The method for upgrading the software of a vehicle production line according to claim 1, characterized in that, The transfer vehicle is equipped with a cockpit domain control, and the step of selecting a master node on the transfer vehicle includes: The cockpit domain controller on the circulating vehicle is selected as the master node.

3. The method for upgrading the software of a vehicle production line according to claim 2, characterized in that, The method further includes: The cockpit domain controller provides a user interface. The controller being flashed and the upgrade information are displayed on the user interface via the cockpit domain controller; The upgrade of the controller being upgraded is triggered by operating the user interface.

4. The method for upgrading the software of a vehicle production line according to claim 3, characterized in that, The method further includes: The cockpit domain controller obtains the flashing progress and flashing result of the controller being flashed; The flashing progress and flashing results are displayed on the user interface.

5. The method for upgrading vehicle production line software according to claim 1, characterized in that, The software flashing component and the production line server are connected via Wi-Fi, and the software flashing component can support manual input of the Wi-Fi name and password.

6. The method for upgrading vehicle production line software according to claim 1, characterized in that, The method further includes: The master node diagnoses the mode changes of the circulating vehicles; When the mode of the circulating vehicle is switched to the production line flashing mode, the whole vehicle flashing component callback is triggered.

7. The method for upgrading vehicle production line software according to claim 1, characterized in that, The method further includes: Upgrades or rewrites are refused for the integrated chassis controller or cockpit controller, dual redundant microcontroller combination, parking assistance system, engine management system, integrated brake-by-wire system, battery management system, and highly automated driving system on the aforementioned vehicles.

8. A software upgrade system for a complete vehicle production line, characterized in that, The system, which is used for transfer vehicles on the production line, includes: The master node is configured to select the circulating vehicle and set the whole vehicle flashing component; The filling station is configured to store the latest version upgrade package and production line data configuration, and to write the latest version upgrade package and production line data configuration to the vehicle flashing component; The production line server is configured to: read the version information of the circulating vehicles and interact with the vehicle flashing component to determine the controllers on the circulating vehicles that need to be upgraded; the vehicle flashing component is configured to complete the flashing of the controllers.

9. A device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to run the computer program to perform the vehicle production line software upgrade method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, wherein the computer program is configured to execute the vehicle production line software upgrade method as described in any one of claims 1 to 7 when running on a computer or processor.

Images