OTA upgrade task creation method and device, electronic equipment and storage medium

Abstract

The invention provides an OTA upgrade task creation method and device, electronic equipment and a storage medium. The method comprises the following steps: receiving an upgrade task creation request input by a user; wherein the upgrade task creation request comprises at least one upgrade service parameter; creating an upgrade software package and an upgrade software version based on the at least one upgrade service parameter; creating an OTA upgrade activity based on the upgrade software version, and creating an OTA upgrade task based on the at least one upgrade service parameter and the OTA upgrade activity; and synchronizing a creation result corresponding to the OTA upgrading task to the user. Thus, by receiving the service upgrading parameters in the upgrading task creation request input by the user, creation of the upgrading software package and the upgrading software version is automatically completed, and then the OTA upgrading task is constructed according to the created upgrading software package and upgrading software version, so that the parameter configuration and operation time of the user can be shortened, and the OTA upgrading efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of OTA upgrade technology, and in particular to methods, apparatus, electronic devices and storage media for creating OTA upgrade tasks. Background Technology

[0002] The TSP (Telematics Service Provider) platform is the core of connected car services, and OTA (Over-The-Air) upgrades are one of its most critical functions, used to remotely update in-vehicle software, including firmware, applications, map data, and more.

[0003] In related technologies, OTA upgrades are a complex and time-consuming process. Testers or product managers need to operate across multiple pages and input and configure a large number of parameters, which leads to excessive time consumption and affects the efficiency of OTA upgrades. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a method, apparatus, electronic device and storage medium for creating OTA upgrade tasks. By receiving service upgrade parameters in the upgrade task creation request input by the user, the method automatically completes the creation of upgrade software packages and upgrade software versions, and then constructs OTA upgrade tasks based on the created upgrade software packages and upgrade software versions. This can reduce the time required for user configuration parameters and operations, thereby improving the efficiency of OTA upgrades.

[0005] In a first aspect, embodiments of this application provide a method for creating OTA upgrade tasks, applied to user equipment, the method comprising: Receive an upgrade task creation request input by the user; wherein the upgrade task creation request includes at least one upgrade service parameter; An upgrade package and an upgrade software version are created based on at least one of the upgrade service parameters; wherein, there is an association between the upgrade software version and the upgrade package; An OTA upgrade activity is created based on the upgraded software version, and an OTA upgrade task is created based on at least one of the upgraded service parameters and the OTA upgrade activity. The creation result corresponding to the OTA upgrade task will be synchronized to the user.

[0006] In one possible implementation, creating the upgrade package based on at least one of the upgrade service parameters includes: The upgrade task creation request is extracted according to the preset task execution frequency. When the upgrade package is a download package, the package download interface is opened based on the download parameters in the upgrade service parameters to download the target package and parse the package name of the target package. Automatically log in to the OTA system backend, and based on the software package name and the hash function value corresponding to the software package, detect whether a software package consistent with the target software package already exists in the OTA system backend; If it exists, the software package existing in the OTA system backend will be identified as the upgrade software package; If it does not exist, an upgrade package is created based on the software part number parameter in the upgrade service parameters and the flashing time information of each part obtained by querying the control parameter code in the upgrade service parameters.

[0007] In one possible implementation, the upgraded software version is created through the following steps: Based on the software part number parameter, software version number and control parameter code in the upgrade business parameters, detect whether the software version existing in the current OTA system backend meets the version creation conditions. If the conditions are not met, the software version existing in the OTA system backend will be determined as the upgrade software version; If satisfied, the upgraded software version is created based on the software part number parameter, software version number, and control parameter code. Among them, the software versions existing in the current OTA system backend that meet the version creation conditions include either the absence of a corresponding software version in the current OTA system backend or the hash function value of the software package associated with the software version in the OTA system backend being inconsistent with the hash function value of the upgrade software package.

[0008] In one possible implementation, creating the upgraded software version based on the software part number parameter, software version number, and control parameter code includes: Based on the software part number parameter, the preset number of digits and the parameter of randomly generated preset fields in the software part number parameter are parsed to obtain the initial version number; If a version number with the same initial version number exists in the OTA system backend, modify the initial version number to obtain the upgrade version number; Based on the software part number parameter and the control parameter code, the upgrade package is determined, and the association between the upgrade version number and the upgrade package is determined. The upgrade software version is created based on the determined upgrade version number, software version number, and the association between the upgrade version number and the upgrade software package.

[0009] In one possible implementation, creating an OTA upgrade activity based on the upgraded software version includes: Based on the software version number in the upgrade service parameters, the created upgrade software version is automatically associated with the OTA upgrade activity to determine the association between the upgrade software version and the OTA upgrade activity; here, if there are multiple software version numbers in the upgrade service parameters, the OTA upgrade activity is associated with multiple upgrade software versions. Automatically select or fill in other activity parameters, and review the relationship between the other activity parameters and the upgraded software version and the OTA upgrade activity; If the review is approved, the OTA upgrade activity will be created.

[0010] In one possible implementation, creating an OTA upgrade task based on at least one of the upgrade service parameters and the OTA upgrade activity includes: Based on the vehicle identification code in the upgrade service parameters, an upgrade file is automatically generated; Based on the upgrade mode in the upgrade service parameters, the task generation mode is automatically selected; The OTA upgrade task is created based on the upgrade file, the task generation mode, and the OTA upgrade activity.

[0011] In one possible implementation, the creation method further includes: The upgrade task creation request is stored in the task database, and the status of the upgrade task creation request is marked as pending execution. After the OTA upgrade task is created, the status of the upgrade task creation request will be changed to "completed".

[0012] Secondly, embodiments of this application also provide an apparatus for creating OTA upgrade tasks, applied to a user equipment, the apparatus comprising: The request receiving module is used to receive an upgrade task creation request input by the user; wherein the upgrade task creation request includes at least one upgrade service parameter; The upgrade version determination module is used to create an upgrade package and an upgrade software version based on at least one of the upgrade service parameters; wherein, there is an association between the upgrade software version and the upgrade package; The upgrade task creation module is used to create an OTA upgrade activity based on the upgrade software version, and to create an OTA upgrade task based on at least one of the upgrade service parameters and the OTA upgrade activity; A creation result synchronization module is used to synchronize the creation result corresponding to the OTA upgrade task to the user.

[0013] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the OTA upgrade task creation method as described in any of the first aspects.

[0014] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the OTA upgrade task creation method as described in any of the first aspects.

[0015] The OTA upgrade task creation method, apparatus, electronic device, and storage medium provided in this application embodiment receive an upgrade task creation request input by a user. The upgrade task creation request includes at least one upgrade service parameter. An upgrade software package and an upgrade software version are created based on the at least one upgrade service parameter. An association exists between the upgrade software version and the upgrade software package. An OTA upgrade activity is created based on the upgrade software version, and an OTA upgrade task is created based on the at least one upgrade service parameter and the OTA upgrade activity. The creation result corresponding to the OTA upgrade task is synchronized to the user. Thus, by receiving the service upgrade parameters in the user-input upgrade task creation request, the creation of the upgrade software package and the upgrade software version is automatically completed, and then an OTA upgrade task is constructed based on the created upgrade software package and the upgrade software version. This reduces the time required for user parameter configuration and operation, thereby improving OTA upgrade efficiency.

[0016] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a method for creating an OTA upgrade task provided in an embodiment of this application; Figure 2 This is a flowchart illustrating the creation of an OTA upgrade task provided in an embodiment of this application. Figure 3A schematic diagram of the structure of an OTA upgrade task creation device provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, 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. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. Based on the embodiments of this application, every other embodiment obtained by those skilled in the art without inventive effort falls within the scope of protection of this application.

[0020] First, the applicable scenarios for this application will be introduced. This application can be applied to the field of OTA upgrade technology.

[0021] The TSP (Telematics Service Provider) platform is the core of connected car services, and OTA (Over-The-Air) upgrades are one of its most critical functions, used to remotely update in-vehicle software, including firmware, applications, map data, and more.

[0022] In related technologies, OTA upgrades are a complex and time-consuming process. Specifically, testers or product managers need to: navigate across multiple pages: sequentially performing operations on four pages—"Package Configuration," "Software Version Configuration," "Upgrade Activity Creation," and "Upgrade Task Creation"; configure numerous professional parameters: involving dozens of parameters, many of which (involving service logic judgments) require in-depth OTA business knowledge and are prone to errors; be excessively time-consuming: skilled engineers need more than 5 minutes to operate; if uploading a 5GB package is involved, it takes more than 1 hour in an external network environment; and have strong environment dependencies: access must be through the company's intranet or VPN, limiting the flexibility of outdoor scenarios such as real-vehicle testing. This results in excessively long OTA upgrade times, impacting OTA upgrade efficiency.

[0023] Based on this, embodiments of this application provide a method for creating OTA upgrade tasks to improve OTA upgrade efficiency.

[0024] Please see Figure 1 , Figure 1This is a flowchart illustrating a method for creating an OTA upgrade task, as provided in an embodiment of this application. Figure 1 As shown in the embodiments of this application, the method for creating an OTA upgrade task includes: S101. Receive an upgrade task creation request input by the user; wherein the upgrade task creation request includes at least one upgrade service parameter.

[0025] S102. Create an upgrade package and an upgrade software version based on at least one of the upgrade service parameters; wherein, there is an association between the upgrade software version and the upgrade package.

[0026] S103. Create an OTA upgrade activity based on the upgraded software version, and create an OTA upgrade task based on at least one of the upgraded service parameters and the OTA upgrade activity.

[0027] S104. Synchronize the creation result corresponding to the OTA upgrade task to the user.

[0028] The OTA upgrade task creation method provided in this application embodiment automatically completes the creation of upgrade software packages and upgrade software versions by receiving service upgrade parameters in the upgrade task creation request input by the user, and then constructs OTA upgrade tasks based on the created upgrade software packages and upgrade software versions. This can reduce the time for users to configure parameters and perform operations, thereby improving OTA upgrade efficiency.

[0029] The exemplary steps of the embodiments of this application are described below: S101. Receive an upgrade task creation request input by the user; wherein the upgrade task creation request includes at least one upgrade service parameter.

[0030] In this embodiment of the application, the TSP platform is the core of the vehicle connectivity service, and OTA upgrade is one of its most critical functions, used to remotely update the vehicle software, including firmware, applications, map data, etc.

[0031] In related technologies, OTA upgrades are a complex and time-consuming process. Testers or product managers need to operate across multiple pages and input and configure a large number of parameters, which leads to excessive time consumption and affects the efficiency of OTA upgrades.

[0032] Based on this, in this embodiment of the application, by receiving the service upgrade parameters in the upgrade task creation request input by the user, the creation of the upgrade package and the upgrade software version is automatically completed, and then the OTA upgrade task is constructed according to the created upgrade package and the upgrade software version. This can reduce the time for users to configure parameters and perform operations, thereby improving the efficiency of OTA upgrades.

[0033] Here, user equipment can include terminal devices such as mobile phones or PC devices such as computers. These user devices are equipped with an automated agent engine, which can automatically complete the creation of upgrade packages and upgrade software versions by receiving the business upgrade parameters in the upgrade task creation request input by the user, thereby reducing the time for users to configure parameters and perform operations, and thus improving the efficiency of OTA upgrades.

[0034] In one possible implementation, the upgrade task creation request input by the user may include at least one upgrade service parameter. Specifically, the upgrade service parameter may include software part number parameters, software version number, control parameter code, upgrade target vehicle information, etc. These upgrade service parameters indicate the vehicle information and software version information that the user needs to upgrade.

[0035] Here, users can input at least one upgrade service parameter through a web page. After confirming that the user has input at least one upgrade service parameter, it is determined that the user has submitted an upgrade task creation request, and then the automatic proxy service interface is called to connect to the automatic proxy engine to carry out the subsequent OTA task creation process.

[0036] S102. Create an upgrade package and an upgrade software version based on at least one of the upgrade service parameters; wherein, there is an association between the upgrade software version and the upgrade package.

[0037] In one possible implementation, after confirming that the user has input an upgrade task creation request, the automated agent engine needs to automatically log in to the OTA system backend. Here, in order to ensure the accuracy of the login, the environment parameter "overseas" in the upgrade business parameters can be used to determine the OTA task creation environment. The automated agent engine will automatically determine whether to log in to the domestic or overseas OTA system backend.

[0038] Furthermore, after automatically logging into the OTA system backend, it is necessary to determine the source of the software package. Specifically, the automated agent engine can automatically process software packages from continuous integration platforms (e.g., Jenkins) or test software packages provided locally by testers, thereby improving the richness and comprehensiveness of OTA task creation.

[0039] In one possible implementation, test packages provided locally by testers can be directly received by uploading files; however, packages from continuous integration platforms (e.g., Jenkins) require parsing the corresponding links and downloading them, followed by further processing based on the packages available in the OTA system backend.

[0040] Specifically, the step "creating an upgrade package based on at least one of the upgrade service parameters" includes: a1: Extract the upgrade task creation request according to the preset task execution frequency. When the upgrade package is a download package, open the package download interface based on the download parameters in the upgrade service parameters, download the target package, and parse the package name of the target package.

[0041] a2: Automatically log in to the OTA system backend and, based on the package name and the hash function value corresponding to the package, detect whether a package identical to the target package already exists in the OTA system backend.

[0042] a3: If it exists, the software package existing in the OTA system backend is identified as the upgrade software package.

[0043] a4: If it does not exist, create an upgrade package based on the software part number parameter in the upgrade service parameters and the flashing time information of each part obtained by querying the control parameter code in the upgrade service parameters.

[0044] In one possible implementation, the automated agent engine processes upgrade task creation requests submitted by users periodically. Specifically, it can extract upgrade task creation requests according to a preset task execution frequency.

[0045] Here, the preset task execution frequency can be determined based on the number of upgrade task creation requests and the processing capacity of the automated agent engine.

[0046] Furthermore, for software packages that need to be downloaded, the download interface can be opened based on the download parameter ota_package_download_url in the upgrade service parameters entered by the user, and the corresponding target software package can be downloaded on the software package download interface, while automatically resolving the package name of the target software package.

[0047] In one possible implementation, the system can determine whether a package with the same name as the target package already exists in the OTA system backend based on the package name of the target package. If a package with the same name as the target package exists, the hash function value of the target package needs to be further compared with the hash function value of the package in the OTA system backend. If the hash function value of the target package is also consistent with the hash function value of the package in the OTA system backend, it is determined that a package with the same name as the target package already exists in the OTA system backend. The package creation process can be skipped directly, and the package existing in the OTA system backend can be identified as the upgrade package.

[0048] Here, the hash function value can be an MD5 value. MD5 (Message Digest Algorithm 5) is used to generate a 128-bit (16-byte) hash value. The MD5 algorithm is widely used in data integrity verification, password storage, and digital signatures for data comparison.

[0049] In another possible implementation, if there is no software package with the same name as the target software package in the OTA system backend, or if the hash function value of the target software package is inconsistent with the hash function value of the software package in the OTA system backend, the group needs to perform a software package creation process.

[0050] Specifically, in one possible implementation, for the test software package provided locally by the tester, the software package creation interface can be opened. This interface contains multiple fields that need to be filled in. Based on the software part number parameter `software_part_no` in the upgrade business parameters, the corresponding field in the software package creation interface is filled in. Then, based on the established relationship between the flashing durations of different parts obtained from the control parameter code `ecu_code` in the upgrade business parameters, the flashing duration of that `ecu_code` is read and filled into the corresponding field in the software package creation interface. Other fields in the software package creation interface can be automatically filled in by default. After the above fields are filled in, the submission button can be clicked automatically to complete the creation of the upgrade software package.

[0051] In another possible implementation, for the software package of the continuous integration platform, the software package creation interface can be opened. This interface contains multiple fields that need to be filled in. Based on the software part number parameter `software_part_no` in the upgrade business parameters, the corresponding field in the software package creation interface is filled in. Then, based on the established relationship between different part write times obtained from the control parameter code `ecu_code` in the upgrade business parameters, the write time of the `ecu_code` is read and filled into the corresponding field in the software package creation interface. Simultaneously, the automated agent engine automatically calculates the MD5 value of the software package and fills it into the corresponding field in the software package creation interface. Other fields in the software package creation interface can be automatically filled in by default. After the above fields are filled in, the submission button can be clicked automatically to complete the creation of the upgrade software package.

[0052] Furthermore, after the upgrade package is created, an upgrade software version can be created based on the software part number parameter, software version number, and control parameter code in the upgrade business parameters input by the user.

[0053] Specifically, the upgraded software version is created through the following steps: b1: Based on the software part number parameter, software version number and control parameter code in the upgrade business parameters, detect whether the software version existing in the current OTA system backend meets the version creation conditions.

[0054] b2: If not satisfied, the software version existing in the OTA system backend will be determined as the upgrade software version.

[0055] b3: If satisfied, create the upgraded software version based on the software part number parameter, software version number, and control parameter code.

[0056] Here, during the creation of the upgraded software version, it is necessary to automatically detect whether the corresponding software version already exists in the current OTA system backend based on the software part number parameter, software version number, and control parameter code in the upgrade business parameters. In other words, it is necessary to determine whether the software version existing in the OTA system backend meets the version creation conditions.

[0057] Here, the software version existing in the current OTA system backend meets the version creation conditions if there is no corresponding software version in the current OTA system backend or if the hash function value of the software package associated with the software version in the OTA system backend is inconsistent with the hash function value of the upgrade software package.

[0058] In one possible implementation, if it is determined that a corresponding software version exists in the current OTA system backend, or if the hash function value of the software package associated with the software version in the OTA system backend is consistent with the hash function value of the upgrade software package, then it is determined that a corresponding software version exists in the current OTA system backend. In this case, the process of creating the upgrade software version can be skipped, and the software version existing in the OTA system backend can be directly determined as the upgrade software version.

[0059] In another possible implementation, if the software version existing in the current OTA system backend meets the version creation conditions, including the absence of a corresponding software version in the current OTA system backend or the hash function value of the software package associated with the software version in the OTA system backend being inconsistent with the hash function value of the upgrade software package, and it is determined that the software version required by the user upgrade does not exist in the current OTA system backend, then it is necessary to create an upgrade software version based on the software part number parameter, software version number, and control parameter code.

[0060] Specifically, the step "creating the upgraded software version based on the software part number parameter, software version number, and control parameter code" includes: c1: Based on the software part number parameter, parse the preset number of digits and the parameters of the randomly generated preset fields in the software part number parameter to obtain the initial version number.

[0061] c2: If a version number with the same initial version number exists in the OTA system backend, modify the initial version number to obtain the upgrade version number.

[0062] c3: Based on the software part number parameter and the control parameter code, determine the upgrade package and the association between the upgrade version number and the upgrade package.

[0063] c4: Based on the determined upgrade version number, software version number, and the association between the upgrade version number and the upgrade software package, create the upgrade software version.

[0064] In one possible implementation, the initial version number can be obtained by parsing the software part number parameter, including a preset number of digits and a randomly generated preset field. For example, the first eight digits of the software part number parameter can be parsed, and the last two uppercase letters can be randomly generated to form the initial version number. The system then checks whether a version number with the same initial version number already exists in the OTA system backend. If it does, the initial version number is generated by modifying it according to the above method until no version number with the same initial version number exists in the OTA system backend, thus obtaining the upgrade version number.

[0065] In one possible implementation, a software version creation interface can be opened, which contains multiple fields that need to be filled in. The obtained upgrade version number is filled into the corresponding field of the software version creation interface. At the same time, the software version number in the business upgrade parameters entered by the user is filled into the corresponding field of the software version creation interface.

[0066] Furthermore, based on the software part number parameter and the control parameter code, the parsed software package name is automatically selected, and the successfully submitted upgrade software package is automatically selected. The association between the upgrade version number and the upgrade software package is determined. Other fields in the software version creation interface can be automatically filled in by default. After the above fields are filled in, the submission button can be clicked automatically to complete the creation of the upgrade software version.

[0067] Furthermore, after completing the creation of the upgrade package and upgrade software version, an OTA upgrade activity can be created based on the created upgrade package and upgrade software version.

[0068] S103. Create an OTA upgrade activity based on the upgraded software version, and create an OTA upgrade task based on at least one of the upgraded service parameters and the OTA upgrade activity.

[0069] In one possible implementation, OTA upgrade activities are determined based on automatically generated upgrade software version information, and one OTA upgrade activity can be associated with multiple software versions.

[0070] Specifically, the step "Create OTA upgrade activity based on the upgraded software version" includes: d1: Based on the software version number in the upgrade service parameters, automatically associate the created upgrade software version with the OTA upgrade activity to determine the association between the upgrade software version and the OTA upgrade activity; here, if there are multiple software version numbers in the upgrade service parameters, the OTA upgrade activity is associated with multiple upgrade software versions.

[0071] d2: Automatically select or fill in other activity parameters, and review the relationship between the other activity parameters and the upgraded software version and the OTA upgrade activity.

[0072] d3: If the review is approved, confirm the creation of the OTA upgrade activity.

[0073] In one possible implementation, the automated agent engine can automatically select the created upgrade version and associate the created upgrade software version with the OTA upgrade activity. If the number of software version numbers in the upgrade service parameters entered by the user is multiple, then one OTA upgrade activity can be associated with multiple software versions.

[0074] In one possible implementation, an upgrade activity creation interface can be opened, which contains multiple fields that need to be filled in. Other fields in the upgrade activity creation interface can be automatically filled in by default. After the fields are filled in, other activity parameters and the relationship between the upgraded software version and the OTA upgrade activity can be submitted for review. Here, the OTA upgrade activity can be automatically reviewed by an automated agent engine. After confirming that the OTA upgrade activity has been successfully reviewed, the OTA upgrade activity can be automatically published.

[0075] Furthermore, after creating an OTA upgrade activity, OTA upgrade tasks can be further enriched and created based on the upgrade business parameters.

[0076] Specifically, the step "creating an OTA upgrade task based on at least one of the upgrade service parameters and the OTA upgrade activity" includes: e1: Automatically generate upgrade files based on the vehicle identification code in the upgrade service parameters.

[0077] e2: Based on the upgrade mode in the upgrade service parameters, automatically select the task generation mode.

[0078] e3: Create the OTA upgrade task based on the upgrade file, the task generation mode, and the OTA upgrade activity.

[0079] In one possible implementation, the Vehicle Identification Number (VIN) can be obtained. It is a unique 17-character alphanumeric code that is universally applicable and unique to each vehicle.

[0080] Here, the vehicle identification code in the upgrade service parameters can specify the vehicle type or specific vehicle targeted by this OTA upgrade task, accurately identifying the upgrade scope of the OTA upgrade task and ensuring the accuracy of the OTA upgrade.

[0081] In one possible implementation, the upgrade file can be automatically generated based on the vehicle identification code in the upgrade service parameters. Specifically, after automatically generating the CSV file, the vehicle identification code in the upgrade service parameters is filled into the CSV file, thereby generating the upload upgrade file.

[0082] Furthermore, based on the upgrade mode (upgrade_mode) in the upgrade service parameters, the task generation mode is automatically selected.

[0083] In one possible implementation, an upgrade task creation interface can be opened, which contains multiple fields that need to be filled in. The "Adaptation Subject" option in the upgrade task creation interface is automatically selected as "[None Match]". Other fields in the upgrade task creation interface can be filled in by default. After the above fields are filled in, the task is submitted for review. The automated agent engine automatically reviews the OTA upgrade task and automatically publishes the OTA upgrade task after confirming that the OTA upgrade has been successfully reviewed.

[0084] In one possible implementation, in order to ensure the efficiency of the automated agent engine, after the user inputs the upgrade task creation request, the automated agent engine does not immediately process the upgrade task, but stores the upgrade task creation request in the task database, and retrieves the upgrade task creation request from the task database according to the scheduled task for subsequent processing.

[0085] Specifically, the creation method further includes: f1: Store the upgrade task creation request in the task database and mark the status of the upgrade task creation request as pending execution.

[0086] f2: After the OTA upgrade task is created, adjust the status of the upgrade task creation request to the completed status.

[0087] In one possible implementation, after storing the upgrade task creation request in the task database, the status of the upgrade task creation request that has not been processed is marked as pending execution. After receiving the scheduled task, the automated agent engine extracts the upgrade task creation request from the task database according to the preset task execution frequency, and prioritizes the upgrade task creation request that entered the task database earliest.

[0088] Furthermore, to avoid the automated agent engine repeatedly executing the same upgrade task creation request, which would affect the efficiency of OTA upgrade task creation, the status of the upgrade task creation request can be adjusted to the completed status after the OTA upgrade task creation is completed.

[0089] In one possible implementation, in order for users to receive the creation result of the OTA upgrade task in a timely manner, the creation result can be synchronized to the user after confirming that the OTA upgrade task has been successfully created.

[0090] S104. Synchronize the creation result corresponding to the OTA upgrade task to the user.

[0091] In one possible implementation, the creation result can be displayed on the web interface where the user inputs the upgrade task creation request, or the creation result corresponding to the OTA upgrade task can be sent to the user through communication software to notify the user that the current OAT upgrade task creation is complete.

[0092] Furthermore, after an OTA upgrade task is determined, the corresponding vehicles can be automatically upgraded via OTA according to the corresponding OTA upgrade task.

[0093] The following specific examples will illustrate the creation process of the OTA upgrade task in this embodiment of the disclosure: Please see Figure 2 , Figure 2 This is a flowchart illustrating the creation process of an OTA upgrade task provided in an embodiment of this application, such as... Figure 2As shown, the user submits upgrade business parameters through a web page, calls the automated agent service API interface, stores the upgrade task creation request in the task database, and marks the status as pending execution. The automated agent engine's scheduled task starts, polls the database, checks pending tasks, and detects if there are any pending tasks. If not, it waits for the next cycle; if there are, it retrieves the oldest "pending" task, automatically logs into the OTA configuration backend, checks the source of the software package, if it is a package downloaded via a link, it parses the download link and downloads it; if it is a package uploaded locally, it receives the uploaded file; it checks if the package already exists in the OTA backend, if it exists, it skips the upload and reuses it directly; if it does not exist, it uploads the package to the OTA backend; it automatically creates the software version, automatically creates the upgrade activity, automatically creates the upgrade task, and updates the database task status to completed; the scheduled task continues and notifies the user of the creation result.

[0094] The OTA upgrade task creation method provided in this application embodiment receives an upgrade task creation request input by a user; wherein the upgrade task creation request includes at least one upgrade service parameter; an upgrade software package and an upgrade software version are created based on at least one upgrade service parameter; wherein there is an association between the upgrade software version and the upgrade software package; an OTA upgrade activity is created based on the upgrade software version, and an OTA upgrade task is created based on at least one upgrade service parameter and the OTA upgrade activity; the creation result corresponding to the OTA upgrade task is synchronized to the user. In this way, by receiving the service upgrade parameters in the upgrade task creation request input by the user, the creation of the upgrade software package and the upgrade software version is automatically completed, and then the OTA upgrade task is constructed based on the created upgrade software package and the upgrade software version, which can reduce the time spent by the user in configuring parameters and performing operations, thereby improving the efficiency of OTA upgrades.

[0095] Based on the same inventive concept, this application also provides an OTA upgrade task creation device corresponding to the OTA upgrade task creation method. Since the principle of the device in this application is similar to the OTA upgrade task creation method described above in this application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0096] Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of an OTA upgrade task creation device provided in an embodiment of this application. Figure 3 As shown, the creation apparatus 300 includes: The request receiving module 310 is used to receive an upgrade task creation request input by the user; wherein the upgrade task creation request includes at least one upgrade service parameter; The upgrade version determination module 320 is used to create an upgrade package and an upgrade software version based on at least one of the upgrade service parameters; wherein, there is an association between the upgrade software version and the upgrade package; The upgrade task creation module 330 is used to create an OTA upgrade activity based on the upgrade software version, and to create an OTA upgrade task based on at least one of the upgrade service parameters and the OTA upgrade activity; The creation result synchronization module 340 is used to synchronize the creation result corresponding to the OTA upgrade task to the user.

[0097] In one possible implementation, when the upgrade version determination module 320 is used to create an upgrade package based on at least one of the upgrade service parameters, the upgrade version determination module 320 is used to: The upgrade task creation request is extracted according to the preset task execution frequency. When the upgrade package is a download package, the package download interface is opened based on the download parameters in the upgrade service parameters to download the target package and parse the package name of the target package. Automatically log in to the OTA system backend, and based on the software package name and the hash function value corresponding to the software package, detect whether a software package consistent with the target software package already exists in the OTA system backend; If it exists, the software package existing in the OTA system backend will be identified as the upgrade software package; If it does not exist, an upgrade package is created based on the software part number parameter in the upgrade service parameters and the flashing time information of each part obtained by querying the control parameter code in the upgrade service parameters.

[0098] In one possible implementation, the upgrade version determination module 320 is used to create the upgrade software version through the following steps: Based on the software part number parameter, software version number and control parameter code in the upgrade business parameters, detect whether the software version existing in the current OTA system backend meets the version creation conditions. If the conditions are not met, the software version existing in the OTA system backend will be determined as the upgrade software version; If satisfied, the upgraded software version is created based on the software part number parameter, software version number, and control parameter code. Among them, the software versions existing in the current OTA system backend that meet the version creation conditions include either the absence of a corresponding software version in the current OTA system backend or the hash function value of the software package associated with the software version in the OTA system backend being inconsistent with the hash function value of the upgrade software package.

[0099] In one possible implementation, when the upgrade version determination module 320 creates the upgraded software version based on the software part number parameter, software version number, and control parameter code, the upgrade version determination module 320 is used to: Based on the software part number parameter, the preset number of digits and the parameter of randomly generated preset fields in the software part number parameter are parsed to obtain the initial version number; If a version number with the same initial version number exists in the OTA system backend, modify the initial version number to obtain the upgrade version number; Based on the software part number parameter and the control parameter code, the upgrade package is determined, and the association between the upgrade version number and the upgrade package is determined. The upgrade software version is created based on the determined upgrade version number, software version number, and the association between the upgrade version number and the upgrade software package.

[0100] In one possible implementation, when the upgrade task creation module 330 is used to create an OTA upgrade activity based on the upgrade software version, the upgrade task creation module 330 is used to: Based on the software version number in the upgrade service parameters, the created upgrade software version is automatically associated with the OTA upgrade activity to determine the association between the upgrade software version and the OTA upgrade activity; here, if there are multiple software version numbers in the upgrade service parameters, the OTA upgrade activity is associated with multiple upgrade software versions. Automatically select or fill in other activity parameters, and review the relationship between the other activity parameters and the upgraded software version and the OTA upgrade activity; If the review is approved, the OTA upgrade activity will be created.

[0101] In one possible implementation, when the upgrade task creation module 330 creates an OTA upgrade task based on at least one of the upgrade service parameters and the OTA upgrade activity, the upgrade task creation module 330 is used to: Based on the vehicle identification code in the upgrade service parameters, an upgrade file is automatically generated; Based on the upgrade mode in the upgrade service parameters, the task generation mode is automatically selected; The OTA upgrade task is created based on the upgrade file, the task generation mode, and the OTA upgrade activity.

[0102] In one possible implementation, the creation device 300 further includes a request status marker module (not shown in the figure), the request status marker module being used for: The upgrade task creation request is stored in the task database, and the status of the upgrade task creation request is marked as pending execution. After the OTA upgrade task is created, the status of the upgrade task creation request will be changed to "completed".

[0103] The OTA upgrade task creation apparatus provided in this application embodiment receives an upgrade task creation request input by a user. The upgrade task creation request includes at least one upgrade service parameter. An upgrade software package and an upgrade software version are created based on the at least one upgrade service parameter. An association exists between the upgrade software version and the upgrade software package. An OTA upgrade activity is created based on the upgrade software version, and an OTA upgrade task is created based on the at least one upgrade service parameter and the OTA upgrade activity. The creation result corresponding to the OTA upgrade task is synchronized to the user. In this way, by receiving the service upgrade parameters in the user-input upgrade task creation request, the creation of the upgrade software package and the upgrade software version is automatically completed, and then an OTA upgrade task is constructed based on the created upgrade software package and the upgrade software version. This reduces the time required for user parameter configuration and operations, thereby improving OTA upgrade efficiency.

[0104] Please see Figure 4 , Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 4 As shown, the electronic device 400 includes a processor 410, a memory 420, and a bus 430.

[0105] The memory 420 stores machine-readable instructions executable by the processor 410. When the electronic device 400 is running, the processor 410 communicates with the memory 420 via the bus 430. When the machine-readable instructions are executed by the processor 410, they can perform the operations described above. Figure 1 The steps of the OTA upgrade task creation method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0106] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described actions. Figure 1 The steps of the OTA upgrade task creation method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0107] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0108] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0109] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0110] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0111] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion 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 this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0112] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The scope of protection of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application. Such modifications, changes, 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 this application, and should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for creating an OTA upgrade task, characterized in that, Applied to user equipment, the creation method includes: Receive an upgrade task creation request input by the user; wherein the upgrade task creation request includes at least one upgrade service parameter; An upgrade package and an upgrade software version are created based on at least one of the upgrade service parameters; wherein, there is an association between the upgrade software version and the upgrade package; An OTA upgrade activity is created based on the upgraded software version, and an OTA upgrade task is created based on at least one of the upgraded service parameters and the OTA upgrade activity. The creation result corresponding to the OTA upgrade task will be synchronized to the user.

2. The creation method according to claim 1, characterized in that, The creation of the upgrade package based on at least one of the upgrade service parameters includes: The upgrade task creation request is extracted according to the preset task execution frequency. When the upgrade package is a download package, the package download interface is opened based on the download parameters in the upgrade service parameters to download the target package and parse the package name of the target package. Automatically log in to the OTA system backend, and based on the software package name and the hash function value corresponding to the software package, detect whether a software package consistent with the target software package already exists in the OTA system backend; If it exists, the software package existing in the OTA system backend will be identified as the upgrade software package; If it does not exist, an upgrade package is created based on the software part number parameter in the upgrade service parameters and the flashing time information of each part obtained by querying the control parameter code in the upgrade service parameters.

3. The creation method according to claim 1, characterized in that, The upgraded software version is created using the following steps: Based on the software part number parameter, software version number and control parameter code in the upgrade business parameters, detect whether the software version existing in the current OTA system backend meets the version creation conditions. If the conditions are not met, the software version existing in the OTA system backend will be determined as the upgrade software version; If satisfied, the upgraded software version is created based on the software part number parameter, software version number, and control parameter code. Among them, the software versions existing in the current OTA system backend that meet the version creation conditions include either the absence of a corresponding software version in the current OTA system backend or the hash function value of the software package associated with the software version in the OTA system backend being inconsistent with the hash function value of the upgrade software package.

4. The method according to claim 3, characterized in that, The process of creating the upgraded software version based on the software part number parameter, software version number, and control parameter code includes: Based on the software part number parameter, the preset number of digits and the parameter of randomly generated preset fields in the software part number parameter are parsed to obtain the initial version number; If a version number with the same initial version number exists in the OTA system backend, modify the initial version number to obtain the upgrade version number; Based on the software part number parameter and the control parameter code, the upgrade package is determined, and the association between the upgrade version number and the upgrade package is determined. The upgrade software version is created based on the determined upgrade version number, software version number, and the association between the upgrade version number and the upgrade software package.

5. The creation method according to claim 1, characterized in that, The creation of an OTA upgrade activity based on the upgraded software version includes: Based on the software version number in the upgrade service parameters, the created upgrade software version is automatically associated with the OTA upgrade activity to determine the association between the upgrade software version and the OTA upgrade activity; here, if there are multiple software version numbers in the upgrade service parameters, the OTA upgrade activity is associated with multiple upgrade software versions. Automatically select or fill in other activity parameters, and review the relationship between the other activity parameters and the upgraded software version and the OTA upgrade activity; If the review is approved, the OTA upgrade activity will be created.

6. The creation method according to claim 1, characterized in that, The step of creating an OTA upgrade task based on at least one of the upgrade service parameters and the OTA upgrade activity includes: Based on the vehicle identification code in the upgrade service parameters, an upgrade file is automatically generated; Based on the upgrade mode in the upgrade service parameters, the task generation mode is automatically selected; The OTA upgrade task is created based on the upgrade file, the task generation mode, and the OTA upgrade activity.

7. The method according to claim 1, characterized in that, The creation method also includes: The upgrade task creation request is stored in the task database, and the status of the upgrade task creation request is marked as pending execution. After the OTA upgrade task is created, the status of the upgrade task creation request will be changed to "completed".

8. An apparatus for creating OTA upgrade tasks, characterized in that, Applied to user equipment, the creation apparatus includes: The request receiving module is used to receive an upgrade task creation request input by the user; wherein the upgrade task creation request includes at least one upgrade service parameter; The upgrade version determination module is used to create an upgrade package and an upgrade software version based on at least one of the upgrade service parameters; wherein, there is an association between the upgrade software version and the upgrade package; The upgrade task creation module is used to create an OTA upgrade activity based on the upgrade software version, and to create an OTA upgrade task based on at least one of the upgrade service parameters and the OTA upgrade activity; A creation result synchronization module is used to synchronize the creation result corresponding to the OTA upgrade task to the user.

9. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the method for creating an OTA upgrade task as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the method for creating an OTA upgrade task as described in any one of claims 1 to 7.

Images