Vehicle software upgrade method and system

Abstract

The present application relates to the technical field of software upgrading, and particularly relates to a vehicle software upgrading method and system, the vehicle software upgrading method comprising: obtaining delivery attributes of a vehicle to be delivered, the delivery attributes at least comprising a planned delivery date; calculating a time window for the vehicle to be delivered to perform software upgrading according to the planned delivery date; sending a wake-up signal to a target vehicle to be delivered when the time window is reached; the target vehicle to be delivered automatically wakes up after receiving the wake-up signal and initiates a software upgrading request; checking whether the target vehicle to be delivered meets the applicable conditions of a software package based on pre-configured software package applicable condition rules, determining a target software package; returning download information of the target software package to the target vehicle to be delivered, and the target vehicle to be delivered completes software upgrading. The present application can solve the problems of pre-sale OTA upgrade relying on manual work and uneven utilization of vehicle cloud channel resources.

Description

Technical Field

[0001] This invention relates to the field of software upgrade technology, and specifically to a method and system for upgrading vehicle software. Background Technology

[0002] With the rapid development of intelligent connected vehicle technology, OEMs generally upgrade the software of pre-sale vehicles via Over-The-Air (OTA) updates before delivery to ensure that users receive the latest features and security patches upon vehicle pickup. Existing pre-sale OTA upgrade solutions mostly adopt a centralized cloud-based push model, where operations personnel issue upgrade commands in batches to vehicles awaiting delivery within a specific time window, and the vehicles passively receive and execute the upgrade tasks.

[0003] While existing OTA (Over-The-Air) upgrade solutions for vehicle pre-sales software can achieve unified push updates of basic vehicle software versions, significant technical defects and application shortcomings remain in practical applications. Current mainstream upgrade methods mostly rely on manual operation or semi-automated batch scheduling, requiring operations personnel to manually configure upgrade push tasks based on vehicle delivery plans. During peak periods of concentrated vehicle deliveries, this often incurs significant manpower costs for cross-departmental collaborative maintenance, resulting in low overall scheduling response efficiency and difficulty in adapting to mass production application scenarios with flexible delivery of large numbers of vehicles. Simultaneously, a large number of vehicles awaiting delivery concurrently initiating software package download requests within a short period close to delivery can easily cause instantaneous congestion in the vehicle-to-cloud communication link. This not only significantly increases the probability of software upgrade failures but also requires enterprises to over-allocate network bandwidth to handle peak traffic, resulting in idle and wasted communication resources during off-peak periods and an overall imbalance in network resource utilization. Furthermore, the existing pre-sales upgrade process is unilaterally and uniformly controlled by the manufacturer, lacking a mechanism for users to intervene in the configuration in advance. Users cannot personalize software functions such as welcome light style, taillight welcome message, and driving mode before vehicle delivery, making it difficult to match the current differentiated and customized delivery needs of users for vehicle software functions. There are obvious shortcomings in user experience and product delivery flexibility. Summary of the Invention

[0004] In view of the shortcomings of the prior art described above, the purpose of this invention is to provide a vehicle software upgrade method and system that can solve the problems of large human resource investment, uneven utilization of vehicle cloud channel resources, and / or lack of user autonomy in the pre-sales OTA upgrade relying on manual push, etc.

[0005] The first aspect of this invention provides a vehicle software upgrade method, comprising: Obtain the delivery attributes of the vehicle to be delivered, the delivery attributes including at least the planned delivery date; calculate the time window for the vehicle to be delivered to perform a software upgrade based on the planned delivery date; When the time window is reached, a wake-up signal is sent to the target vehicle to be delivered; upon receiving the wake-up signal, the target vehicle to be delivered automatically wakes up and proactively initiates a software upgrade request. Based on pre-configured software package applicability rules, the system verifies whether the target vehicle to be delivered meets the applicability conditions of the software package and determines the target software package. The download information of the target software package is returned to the target vehicle to be delivered, and the target vehicle to be delivered completes the software upgrade.

[0006] As an optional implementation, the step of verifying whether the target vehicle to be delivered meets the applicable conditions of the software package based on pre-configured software package applicability rules, and determining the target software package, includes: Before performing the verification, the tested software package is published to the software package repository, and the software package applicability rules are configured synchronously. The software package applicability rules define the matching logic that a vehicle must meet to be allowed to download the software package. Obtain the Vehicle Identification Number (VIN) carried in the software upgrade request, and parse the actual vehicle model, year, and hardware configuration information of the target vehicle to be delivered based on the VIN. According to the matching logic, the parsed actual vehicle model, model year, and hardware configuration information are compared with the preset applicable parameters of each software package in the software package repository; A software package is considered a target software package if and only if the parsed information of the target vehicle to be delivered is completely consistent with the applicable parameters of a certain software package.

[0007] As an optional implementation, the delivery attributes also include user software configuration preferences; Based on the fact that the parsed information of the target vehicle to be delivered is completely consistent with the applicable parameters of a certain software package, the user software configuration preference is further matched and determined with the function configuration version corresponding to the software package according to the preset preference and function mapping rules. The software package shall be used as the target software package if and only if the applicable parameters are completely identical and the functional configuration version of the software package matches the user software configuration preference corresponding to the mapping rule.

[0008] As an optional implementation, the software upgrade step based on user software configuration preferences specifically includes: When a vehicle order is placed or an order status transition is completed, the user software preference settings interface is provided to the user terminal. Receive software function options returned through the software preference settings interface, and convert the software function options into standardized preference data; The preference data is bound to the Vehicle Identification Number (VIN) of the target vehicle to be delivered and stored as part of the delivery attributes.

[0009] As an optional implementation, calculating the time window for the software upgrade of the vehicle to be delivered based on the planned delivery date includes: Extract the planned delivery date for each vehicle to be delivered, and group vehicles with the same or similar delivery time periods. For each group of vehicles, during the preset idle period before the vehicles are officially delivered, an independent upgrade time window is calculated to avoid peak business periods.

[0010] As an optional implementation, when the time window is reached, a wake-up signal is sent to the target vehicle to be delivered; upon receiving the wake-up signal, the target vehicle to be delivered automatically wakes up and proactively initiates a software upgrade request, including: When the time window is reached, a lightweight wake-up command is sent to the target vehicle to be delivered. The lightweight wake-up command only activates the vehicle communication module and does not start the vehicle equipment, so that the vehicle switches to a state where it can request upgrades via the Internet. After receiving the lightweight wake-up command, the electronic control unit (ECU) of the target vehicle to be delivered completes the wake-up and actively initiates a software upgrade request.

[0011] A second aspect of the present invention provides a vehicle software upgrade system, including a cloud-based dispatch system and a vehicle to be delivered that is communicatively connected to the cloud-based dispatch system; The cloud-based scheduling system is configured to acquire the delivery attributes of the vehicle to be delivered, the delivery attributes including at least the planned delivery date; calculate the time window for the vehicle to be delivered to perform a software upgrade based on the planned delivery date; and send a wake-up signal to the target vehicle to be delivered when the time window is reached. The target vehicle to be delivered is configured to automatically wake up upon receiving the wake-up signal and actively initiate a software upgrade request to the cloud-based dispatch system. The cloud-based dispatch system is further configured to, upon receiving the software upgrade request, verify whether the target vehicle to be delivered meets the applicable conditions of the software package based on pre-configured software package applicability rules, thereby determining the target software package; and return the download information of the target software package to the target vehicle to be delivered. The target vehicle to be delivered is also configured to retrieve the corresponding software package based on the download information and complete the software upgrade.

[0012] As an optional implementation, the cloud-based dispatch system has a cloud-based software package repository. Before verifying whether a vehicle meets the software package applicability conditions, the tested software package is published to the cloud-based software package repository. The cloud-based software package repository is also configured with software package applicability condition rules, which define the matching logic that a vehicle must meet to be allowed to download the software package.

[0013] As an optional implementation, the delivery attributes also include user software configuration preferences; specifically, the cloud scheduling system is configured to: Obtain the Vehicle Identification Number (VIN) carried in the software upgrade request, and parse the actual vehicle model, year, and hardware configuration information of the target vehicle to be delivered based on the VIN. According to the matching logic, the parsed information is compared with the preset applicable parameters of each software package in the cloud software package repository; Based on the fact that the vehicle parsing information is completely consistent with the applicable parameters of a certain software package, the user software configuration preferences are matched and determined with the function configuration version of the software package according to the preset preference and function mapping rules. The software package is selected as the target software package only if the applicable parameters are completely identical and the functional configuration version of the software package matches the user software configuration preference corresponding to the mapping rule.

[0014] A third aspect of the present invention provides an electronic device, comprising: at least one processor; and at least one memory communicatively connected to the processor, wherein: the memory stores program instructions executable by the processor, and the processor, by invoking the program instructions, can perform the steps of the method described in the first aspect of the present invention.

[0015] A fourth aspect of the present invention provides a readable storage medium storing a computer program that is executed by a processor as described in the first aspect of the present invention.

[0016] This invention transforms the traditional manual push model by OTA operators into an automatic pull mechanism based on vehicle delivery attributes, reducing manual intervention and cross-team collaboration burdens during peak delivery periods and decreasing overtime frequency. By dynamically allocating off-peak upgrade time windows based on planned delivery dates and combining a lightweight wake-up mechanism to control vehicles to actively request upgrades during off-peak hours, the originally concentrated instantaneous high-concurrency traffic on the delivery day is transformed into smoothly distributed time-limited traffic. This reduces the peak bandwidth occupancy rate of the vehicle-cloud channel on the delivery day, alleviates network congestion, and avoids idle channel resources during off-peak periods. At the same time, by using the user's pre-set software function preferences as a key component of delivery attributes and jointly verifying them with applicable condition rules during the software package matching stage, it ensures that the delivered software packages meet both vehicle hardware constraints and user personalized preferences. This allows for precise user-based software configuration before vehicle delivery, significantly improving the user delivery experience and functional gain. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating a vehicle software upgrade method according to a specific embodiment of the present invention.

[0019] Figure 2 This is a flowchart illustrating another vehicle software upgrade method in a specific embodiment of the present invention.

[0020] Figure 3 This is a flowchart illustrating another vehicle software upgrade method in a specific embodiment of the present invention.

[0021] Figure 4 This is a block diagram of a vehicle software upgrade system according to a specific embodiment of the present invention. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Furthermore, it should be understood that the specific embodiments described herein are only for illustration and explanation of this application and are not intended to limit this application.

[0023] It should be noted that the order of description of the following embodiments is not intended to limit the preferred order of the embodiments of this application. Furthermore, the descriptions of each embodiment in the following embodiments have their own emphasis; for parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0024] While existing technologies have attempted to introduce optimization strategies such as scheduled upgrades and off-peak distribution, they have still failed to systematically resolve the three core contradictions in pre-sales upgrades: "strong reliance on manpower, extensive resource scheduling, and lack of user participation." On the one hand, the time windows are mostly based on fixed rules or user history settings, and are not deeply coupled with the actual vehicle delivery plan. On the other hand, the software package matching logic usually only considers the vehicle model and hardware parameters, ignoring the software preferences actively set by the user. Furthermore, vehicle wake-up and upgrade requests are still mostly triggered actively by the cloud, failing to achieve a lightweight, on-demand wake-up, and vehicle-side autonomous retrieval collaborative mechanism.

[0025] In view of this, such as Figure 1 As shown, the first aspect of the present invention provides a vehicle software upgrade method, comprising the following steps.

[0026] Step S100: Obtain the delivery attributes of the vehicle to be delivered, the delivery attributes including at least the planned delivery date; calculate the time window for the vehicle to be delivered to perform a software upgrade based on the planned delivery date.

[0027] Specifically, the planned delivery date is the time base of this invention. The time window refers to the exclusive time interval planned by the cloud scheduling system based on the planned delivery date at the business level, allowing the target vehicle to perform remote wake-up and establish network communication to retrieve software packages. This time window is not only the trigger threshold for the vehicle's state to switch from "deep hibernation" to "network-available request state," but also the basic scheduling unit for the entire cloud system to allocate network bandwidth resources.

[0028] The step of calculating the time window for the software upgrade of the vehicles to be delivered based on the planned delivery date includes: extracting the planned delivery date of each vehicle to be delivered and grouping the vehicles to be delivered within the same or similar delivery time period. For each group of vehicles, during the preset idle period before the vehicles are officially delivered, an independent upgrade time window is calculated to avoid peak business periods.

[0029] In specific application scenarios, the specific process of calculating the independent upgrade time window includes: first, calculating a preset safety lead time (e.g., 3 days) based on the vehicle's planned delivery date to generate an initial upgrade allowable interval; then, assessing the expected concurrent load rate of the cloud network and vehicle-cloud channel within this initial interval, and finding a network idle time slice (e.g., early morning hours) with a concurrency number lower than a set threshold; simultaneously, obtaining the total capacity of the target software package matched to the vehicle, and calculating the expected duration based on the current network baseline transmission rate; finally, extracting a continuous interval with a length greater than or equal to the expected duration from the network idle time slice as the precise time window for the vehicle to perform the software upgrade.

[0030] This invention addresses the issue of staggering peak business hours for each vehicle group during pre-set idle periods before official vehicle delivery, allocating independent upgrade time windows for each vehicle. This allows a large number of vehicles awaiting delivery to download large-capacity software packages in batches and at off-peak times several days before delivery, effectively smoothing network traffic on the vehicle-to-cloud communication channel and ensuring a high download success rate. It also avoids vehicles being blindly and frequently polled or woken up throughout the entire delivery period, ensuring that when users actually pick up their vehicles, they are in the optimal state with the latest software and personalized functions ready.

[0031] Step S200: When the time window is reached, a wake-up signal is sent to the target vehicle to be delivered; the target vehicle to be delivered automatically wakes up after receiving the wake-up signal and actively initiates a software upgrade request.

[0032] Specifically, the wake-up signal is a lightweight wake-up command. When the specified time window arrives, a lightweight wake-up command is sent to the target vehicle to be delivered. This lightweight wake-up command only activates the vehicle's communication module and does not start the entire vehicle's equipment, switching the vehicle to a state where it can request an upgrade via the internet. Upon receiving the lightweight wake-up command, the target vehicle's Electronic Control Unit (ECU) completes the wake-up process and proactively initiates a software upgrade request. This request carries the vehicle's VIN code.

[0033] Here, the present invention significantly reduces the power consumption of the vehicle during the idle period by adopting a lightweight wake-up method that only activates the communication module, thus avoiding power depletion before vehicle delivery; at the same time, it effectively alleviates the concurrent pressure on the cloud and improves the upgrade success rate by combining the vehicle-side active request mechanism.

[0034] Step S300: Based on the pre-configured software package applicability rules, verify whether the target vehicle to be delivered meets the applicability conditions of the software package, and determine the target software package.

[0035] The software package applicability rules are a set of admission standards synchronously configured by the cloud when releasing software packages. These standards define the secure distribution and compatibility boundaries of the software packages, essentially acting as a hardware whitelist for each package. They clearly define the vehicle attributes that allow the software package to run stably, specifically including applicable vehicle models, model years, and hardware configuration requirements. The matching logic is a verification process executed by the cloud scheduling system after receiving a software upgrade request initiated by a vehicle. First, the system parses the Vehicle Identification Number (VIN) carried in the request to obtain the vehicle's actual model, model year, and hardware configuration information. Then, it compares the parsed actual vehicle parameters with the preset parameters in the software package applicability rules. Only when all parameters are completely identical is the vehicle deemed to meet the conditions for downloading the software package.

[0036] In one embodiment of the present invention, the step of verifying whether the target vehicle to be delivered meets the applicable conditions of the software package based on pre-configured software package applicability rules, and determining the target software package, includes: Before performing the verification, the tested software package is published to the software package repository, and the applicable rules for the software package are configured synchronously. Obtain the Vehicle Identification Number (VIN) carried in the software upgrade request, and parse the actual vehicle model, year, and hardware configuration information of the target vehicle to be delivered based on the VIN. According to the matching logic, the parsed actual vehicle model, model year, and hardware configuration information are compared with the preset applicable parameters of each software package in the software package repository; A software package is considered a target software package if and only if the parsed information of the target vehicle to be delivered is completely consistent with the applicable parameters of a certain software package.

[0037] Here, a reasonable verification mechanism is constructed by dynamically parsing the vehicle VIN code and performing a strict multi-dimensional consistency comparison with the applicable parameters of the software package. This method can reduce the risk of flashing failure caused by software mis-sending and improve the security of vehicle software upgrades.

[0038] Step S400: Return the download information of the target software package to the target vehicle to be delivered, and the target vehicle to be delivered completes the software upgrade.

[0039] Specifically, by returning the downloaded information to the target vehicle to be delivered, the awakened target vehicle to be delivered is proactively initiating an upgrade request to the cloud server, thereby dispersing the push pressure on the cloud and partially transferring the upgrade leadership to the vehicle.

[0040] In a specific application scenario of this invention, the download information of the target software package is returned to the target vehicle to be delivered; the target vehicle to be delivered completes the download, installation and verification of the software package according to the download information, and reports the result after the upgrade is successful, and then re-enters the dormant state to wait for delivery.

[0041] This invention dynamically plans the upgrade time window by combining the planned delivery date, and uses a lightweight wake-up mechanism to reduce the power consumption of the whole vehicle. At the same time, it uses a dual verification mechanism based on the actual vehicle configuration and user personalized preferences based on VIN code parsing to ensure that the accurately matched software package is pushed only to eligible vehicles. This achieves automated and personalized deployment of software status before delivery, avoids the risk of manual intervention and accidental upgrades, and improves delivery efficiency and user experience.

[0042] like Figure 2 and Figure 3 As shown, in one embodiment of the present invention, the delivery attribute further includes user software configuration preferences; Based on the fact that the parsed information of the target vehicle to be delivered is completely consistent with the applicable parameters of a certain software package, the user software configuration preference is further matched and determined with the function configuration version corresponding to the software package according to the preset preference and function mapping rules. The software package shall be used as the target software package if and only if the applicable parameters are completely identical and the functional configuration version of the software package matches the user software configuration preference corresponding to the mapping rule.

[0043] In one embodiment of the present invention, when a vehicle order or order status completion event is detected, a user software preference settings interface is provided to the user terminal; wherein, after completing the vehicle order or order status transition, the user accesses the software preference settings interface through the official mobile application or the designated vehicle purchase configuration system, and selects software function options, including performance mode, user interface theme, advanced driver assistance function package activation status, and entertainment system preferences. The system receives software function options returned through the software preference settings interface and converts these options into standardized preference data. The selected software function options are converted into standardized preference data and bound to the vehicle identification number (VIN) of the vehicle, and stored in the cloud delivery management system as part of the delivery attributes. The preference data is bound to the Vehicle Identification Number (VIN) of the target vehicle to be delivered and stored as part of the delivery attributes.

[0044] Because existing technology only supports manufacturers to push fixed software versions in a one-way unified manner, it completely ignores the differences in users' dynamic intentions before purchasing a car. It cannot provide refined and differentiated software customization services for users with different degrees of certainty about purchasing a car, resulting in industry pain points such as poor customization flexibility and low user adaptability.

[0045] In one embodiment of the present invention, a layered software preference configuration mechanism based on the user's pre-sale car purchase stage is used to divide different car purchase intention levels according to the user's order flow status and to differentiate and open personalized software configuration permissions.

[0046] Specifically, in this invention, according to the order flow status, the user's pre-sale car purchase process is divided into at least a first purchase stage and a second purchase stage. Different stages correspond to different purchase certainty and product rights permissions, and the range of unlockable software custom configurations varies.

[0047] Once a user's order progresses to the second stage of the car purchase process, where they have higher authority, they can access a dedicated software preference configuration interface through the terminal application to pre-customize vehicle pre-sale software function parameters, including personalized configuration items such as taillight welcome messages, welcome light styles, driving modes, and in-vehicle interface themes.

[0048] The software configuration preferences selected by the user will be bound and stored with the VIN code of the corresponding vehicle to be delivered as part of the vehicle delivery attributes. This data will be used by the cloud dispatch system to accurately determine the final target software package based on the user's hierarchical configuration preferences after the hardware matching and screening of the compatible software package. The system will also coordinate the integrated scheduling of the upgrade time window and the upgrade task.

[0049] In specific implementation scenarios, the aforementioned first car purchase stage can correspond to the prepayment stage where the user initially locks in the vehicle purchase intention, and the second car purchase stage can correspond to the order confirmation stage where the user finally confirms the purchase. Different software customization permissions are matched under different car purchase certainty levels to realize refined pre-sales OTA customized upgrade services based on the user's pre-sales purchase intention.

[0050] This invention transforms the traditional cloud push mode into a pull mode initiated by the vehicle based on delivery attributes. It introduces business attributes such as delivery date and user preferences as core triggering conditions, controlling the vehicle to automatically wake up and initiate an upgrade request at a specific time before delivery, thus realizing personalized upgrades based on user software preferences.

[0051] like Figure 4 As shown, a second aspect of the present invention provides a vehicle software upgrade system, including a cloud dispatch system and a vehicle to be delivered that is communicatively connected to the cloud dispatch system; The cloud-based scheduling system is configured to acquire the delivery attributes of the vehicle to be delivered, the delivery attributes including at least the planned delivery date; calculate the time window for the vehicle to be delivered to perform a software upgrade based on the planned delivery date; and send a wake-up signal to the target vehicle to be delivered when the time window is reached. The target vehicle to be delivered is configured to automatically wake up upon receiving the wake-up signal and actively initiate a software upgrade request to the cloud-based dispatch system. The cloud-based dispatch system is also configured to, upon receiving the software upgrade request, verify whether the target vehicle to be delivered meets the applicable conditions of the software package based on pre-configured software package applicability rules, thereby determining the target software package; and return the download information of the target software package to the target vehicle to be delivered. The target vehicle to be delivered is also configured to retrieve the corresponding software package based on the download information and complete the software upgrade.

[0052] In one embodiment of the present invention, the cloud scheduling system is provided with a cloud software package repository. Before verifying whether a vehicle meets the software package applicability conditions, the tested software package is published to the cloud software package repository. The cloud software package repository is also configured with software package applicability condition rules, which define the matching logic that a vehicle must meet to be allowed to download the software package.

[0053] Specifically, the cloud-based software package repository stores tested and released software packages. Each software package is configured with corresponding applicability rules upon release, defining the matching logic that a vehicle must meet to be allowed to download the package. Vehicles awaiting delivery are in a low-power sleep state after leaving the factory, and their electronic control units have the ability to receive external signals and wake up autonomously.

[0054] In one embodiment of the present invention, the delivery attribute further includes user software configuration preferences; the cloud scheduling system is specifically configured to: Obtain the Vehicle Identification Number (VIN) carried in the software upgrade request, and parse the actual vehicle model, year, and hardware configuration information of the target vehicle to be delivered based on the VIN. According to the matching logic, the parsed information is compared with the preset applicable parameters of each software package in the cloud software package repository; Based on the fact that the vehicle parsing information is completely consistent with the applicable parameters of a certain software package, the user software configuration preferences are matched and determined with the function configuration version of the software package according to the preset preference and function mapping rules. A software package is designated as the target software package only if the applicable parameters are completely identical and the functional configuration version of the software package matches the user software configuration preference corresponding to the mapping rule.

[0055] Specifically, the cloud-based dispatch system retrieves delivery attributes linked to the Vehicle Identification Number (VIN) from the delivery management system. These attributes include at least the planned delivery date and may also include user software configuration preferences. After placing an order, the user accesses the software preference settings interface via the official mobile application. In this interface, they select options such as performance mode, user interface theme, advanced driver assistance function activation status, or entertainment system preferences. These selections are linked to the VIN and stored in the delivery management system as user software configuration preferences. Delivery or sales personnel simultaneously enter the planned delivery date for the vehicle into this system.

[0056] The cloud-based dispatch system automatically calculates the time window for software upgrades based on the planned delivery date, for example, setting it to 5 days before delivery, and adds the vehicle to the upgrade task queue. When this time window arrives, the cloud-based dispatch system sends a lightweight wake-up signal to the target vehicle to be delivered. Upon receiving this wake-up signal, the electronic control unit of the target vehicle to be delivered activates from sleep mode, establishes a communication connection with the cloud-based dispatch system, and proactively initiates a software upgrade request, which carries the vehicle's VIN code.

[0057] Upon receiving a software upgrade request, the cloud-based dispatch system first parses the VIN code to determine the actual vehicle model, year, and hardware configuration information of the target vehicle to be delivered. Then, the system compares the parsed information with the preset applicable parameters of each software package in the cloud software package repository to determine if a software package with completely identical applicable parameters exists. Based on this, if the delivery attributes include user software configuration preferences, the system further matches the user software configuration preferences with the available functional configuration versions of the software package according to preset preference and function mapping rules. Only when the vehicle model, year, and hardware configuration completely match the applicable parameters of the software package, and the functional configuration version of the software package meets the requirements mapped by the user's software configuration preferences, is the software package identified as the target software package.

[0058] The cloud-based dispatch system returns the download information of the target software package to the target vehicle awaiting delivery. The target vehicle then retrieves the corresponding software package from the cloud based on this download information, completes the installation, integrity verification, and functional verification in the background—all without manual intervention. After a successful upgrade, the vehicle reports the upgrade result to the cloud and re-enters a dormant state, awaiting final delivery. Through this mechanism, the vehicle automatically completes a software upgrade precisely matched to its hardware configuration and user preferences before delivery, ensuring that the vehicle is in its personalized software state when the user picks up the vehicle.

[0059] In a preferred embodiment, the cloud-based software package repository synchronously configures software package applicability rules when the software package is released, such as the rule "applicable to 2024 model A vehicles equipped with advanced audio systems", thereby ensuring the accuracy and security of the subsequent automatic matching process.

[0060] This invention can dynamically generate precise upgrade windows based on delivery attributes, trigger vehicle-side active requests through lightweight wake-up, and combine VIN code parsing and user preference binding mechanisms to support personalized configuration while ensuring software package applicability. This enables efficient, flexible, and user-participatory pre-sales OTA upgrades while reducing maintenance burden and balancing network load.

[0061] A third aspect of the present invention provides an electronic device, comprising: at least one processor; and at least one memory communicatively connected to the processor, wherein: the memory stores program instructions executable by the processor, and the processor invokes the program instructions to perform the steps of the method as described in any of the above embodiments.

[0062] A fourth aspect of the present invention discloses a readable storage medium storing a computer program, which is executed by a processor as described in any of the above embodiments.

[0063] Computer-readable storage media can include: any entity or device capable of carrying computer programs, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory, random access memory, and software distribution media, etc. Computer programs include computer program code. Computer program code can be in the form of source code, object code, executable files, or some intermediate form, etc. Computer-readable storage media can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory, random access memory, and software distribution media, etc.

[0064] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of the invention includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as will be understood by those skilled in the art to which embodiments of the invention pertain.

[0065] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a system including a processing module or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0066] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A vehicle software upgrade method, characterized in that, include: Obtain the delivery attributes of the vehicle to be delivered, the delivery attributes including at least the planned delivery date; calculate the time window for the vehicle to be delivered to perform a software upgrade based on the planned delivery date; When the time window is reached, a wake-up signal is sent to the target vehicle to be delivered; Upon receiving the wake-up signal, the target vehicle to be delivered automatically wakes up and proactively initiates a software upgrade request. Based on pre-configured software package applicability rules, the system verifies whether the target vehicle to be delivered meets the applicability conditions of the software package and determines the target software package. The download information of the target software package is returned to the target vehicle to be delivered, and the target vehicle to be delivered completes the software upgrade.

2. The vehicle software upgrade method according to claim 1, characterized in that, The method of verifying whether the target vehicle to be delivered meets the applicable conditions of the software package based on pre-configured software package application rules, and determining the target software package, includes: Before performing the verification, the tested software package is published to the software package repository, and the software package applicability rules are configured synchronously. The software package applicability rules define the matching logic that a vehicle must meet to be allowed to download the software package. Obtain the Vehicle Identification Number (VIN) carried in the software upgrade request, and parse the actual vehicle model, year, and hardware configuration information of the target vehicle to be delivered based on the VIN. According to the matching logic, the parsed actual vehicle model, model year, and hardware configuration information are compared with the preset applicable parameters of each software package in the software package repository; A software package is considered a target software package if and only if the parsed information of the target vehicle to be delivered is completely consistent with the applicable parameters of a certain software package.

3. The vehicle software upgrade method according to claim 2, characterized in that, The delivery attributes also include user software configuration preferences; Based on the fact that the parsed information of the target vehicle to be delivered is completely consistent with the applicable parameters of a certain software package, the user software configuration preference is further matched and determined with the function configuration version corresponding to the software package according to the preset preference and function mapping rules. The software package shall be used as the target software package if and only if the applicable parameters are completely identical and the functional configuration version of the software package matches the user software configuration preference corresponding to the mapping rule.

4. The vehicle software upgrade method according to claim 3, characterized in that, The software upgrade steps based on user software configuration preferences specifically include: When a vehicle order is placed or an order status transition is completed, the user software preference settings interface is provided to the user terminal. Receive software function options returned through the software preference settings interface, and convert the software function options into standardized preference data; The preference data is bound to the Vehicle Identification Number (VIN) of the target vehicle to be delivered and stored as part of the delivery attributes.

5. The vehicle software upgrade method according to claim 1, characterized in that, The step of calculating the time window for the software upgrade of the vehicle to be delivered based on the planned delivery date includes: Extract the planned delivery date for each vehicle to be delivered, and group vehicles with the same or similar delivery time periods. For each group of vehicles, during the preset idle period before the vehicles are officially delivered, an independent upgrade time window is calculated to avoid peak business periods.

6. The vehicle software upgrade method according to claim 1, characterized in that, When the time window is reached, a wake-up signal is sent to the target vehicle to be delivered. Upon receiving the wake-up signal, the target vehicle to be delivered automatically wakes up and proactively initiates a software upgrade request, including: When the time window is reached, a lightweight wake-up command is sent to the target vehicle to be delivered. The lightweight wake-up command only activates the vehicle communication module and does not start the vehicle equipment, so that the vehicle switches to a state where it can request upgrades via the Internet. After receiving the lightweight wake-up command, the electronic control unit (ECU) of the target vehicle to be delivered completes the wake-up and actively initiates a software upgrade request.

7. A vehicle software upgrade system, characterized in that, This includes a cloud-based dispatch system and vehicles to be delivered that are communicatively connected to the cloud-based dispatch system; The cloud-based scheduling system is configured to acquire the delivery attributes of the vehicle to be delivered, the delivery attributes including at least the planned delivery date; and to calculate the time window for the vehicle to be delivered to perform a software upgrade based on the planned delivery date. And when the time window is reached, a wake-up signal is sent to the target vehicle to be delivered; The target vehicle to be delivered is configured to automatically wake up upon receiving the wake-up signal and actively initiate a software upgrade request to the cloud-based dispatch system. The cloud-based dispatch system is also configured to, upon receiving the software upgrade request, verify whether the target vehicle to be delivered meets the applicable conditions of the software package based on pre-configured software package applicability rules, so as to determine the target software package. The download information of the target software package will then be returned to the target vehicle to be delivered. The target vehicle to be delivered is also configured to retrieve the corresponding software package based on the download information and complete the software upgrade.

8. The vehicle software upgrade system according to claim 7, characterized in that, The cloud-based dispatch system has a cloud-based software package repository. Before verifying whether a vehicle meets the software package applicability conditions, the tested software packages are published to the cloud-based software package repository. The cloud-based software package repository is also configured with software package applicability condition rules, which define the matching logic that a vehicle must meet to be allowed to download the software package.

9. The vehicle software upgrade system according to claim 8, characterized in that, The delivery attributes also include user software configuration preferences; the cloud scheduling system is specifically configured to, when determining the target software package, as follows: Obtain the Vehicle Identification Number (VIN) carried in the software upgrade request, and parse the actual vehicle model, year, and hardware configuration information of the target vehicle to be delivered based on the VIN. According to the matching logic, the parsed information is compared with the preset applicable parameters of each software package in the cloud software package repository; Based on the fact that the vehicle parsing information is completely consistent with the applicable parameters of a certain software package, the user software configuration preferences are matched and determined with the function configuration version of the software package according to the preset preference and function mapping rules. The software package is selected as the target software package only if the applicable parameters are completely identical and the functional configuration version of the software package matches the user software configuration preference corresponding to the mapping rule.

10. An electronic device, characterized in that, include: At least one processor; And at least one memory communicatively connected to the processor, wherein: the memory stores program instructions executable by the processor, and the processor invokes the program instructions to perform the steps of the vehicle software upgrade method as described in any one of claims 1-6.

11. A readable storage medium storing a computer program, characterized in that, The computer program is executed by a processor using the steps of the vehicle software upgrade method as described in any one of claims 1-6.

Images