System update description processing method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application provide a system update description processing method and device, electronic equipment and storage medium, relating to the technical field of program updating, the method comprises: acquiring a system update description item and an original content element corresponding to the system update description item; then marking the original content element to obtain a corresponding first content element, the first content element comprising an element tag used to represent a vehicle condition group applicable to the first content element; then matching the element tag with a preset vehicle condition group to obtain a content element set corresponding to each preset vehicle condition group, and generating a system update description page corresponding to the content element set; and finally pushing the system update description page to a vehicle corresponding to the preset vehicle condition group, thereby reducing the resources required for system update description, ensuring the content accuracy of system update, reducing the cost resources of manual maintenance, and effectively ensuring the accuracy of content pushing.

Description

Technical Field

[0001] This invention relates to the field of program update technology, and in particular to a method for processing system update instructions, a device for processing system update instructions, an electronic device, and a computer-readable storage medium. Background Technology

[0002] With the rapid development of the automotive industry, automakers are launching new models at an increasingly faster pace, and the frequency of vehicle system updates is also increasing. Previously, vehicle system updates were typically conducted on an annual basis, but now they are done quarterly or even monthly. Higher-frequency system updates mean automakers need to release system update notes more frequently. However, currently, automakers primarily maintain these update notes manually for each model, resulting in separate update notes for each vehicle. In the era of new energy vehicles, differences in hardware such as power batteries, smart cockpit chips, and intelligent driving chips can lead to multiple configurations for a single model, significantly increasing the maintenance cost of system update notes. While the content of a single system update is largely the same across models, differences in hardware configurations can cause variations in the corresponding update notes. Manual maintenance of update notes prevents the reuse of common parts, further increasing maintenance costs. Summary of the Invention

[0003] The present invention provides a method, apparatus, electronic device, and computer-readable storage medium for processing system update instructions, in order to solve or partially solve the problem that system update instructions for vehicles require high maintenance costs.

[0004] This invention discloses a method for processing system update instructions, including:

[0005] Obtain the system update description entry and the original content element corresponding to the system update description entry;

[0006] The original content elements are tagged to obtain the corresponding first content elements, wherein the first content elements include at least element tags for characterizing the vehicle condition group to which the first content elements are applicable.

[0007] The element tags are matched with preset vehicle condition groups to obtain the content element set corresponding to each preset vehicle condition group, and the system update description page corresponding to the content element set is generated.

[0008] The system update instructions page is pushed to the vehicles corresponding to the preset vehicle condition group.

[0009] In some feasible implementations, pushing the system update instructions page to vehicles corresponding to the preset vehicle condition group includes:

[0010] Compare the content element sets corresponding to each of the preset vehicle condition groups, and determine the push range corresponding to the system update instructions page based on the comparison results;

[0011] The corresponding system update instructions page is pushed to the vehicles within the push range.

[0012] In some feasible implementations, comparing the content element sets corresponding to each of the preset vehicle condition groups and determining the push range corresponding to the system update description page based on the comparison results includes:

[0013] Obtain the element identifier corresponding to each of the first content elements in the content element set;

[0014] Add the preset vehicle condition groups corresponding to the target content element sets containing the exact same element identifier to the same push batch to obtain the push range corresponding to each push batch.

[0015] In some feasible implementations, the original content element includes at least a content element entity and an element identifier, and the step of tagging the original content element to obtain the corresponding first content element includes:

[0016] The content element entity is identified to obtain the vehicle information corresponding to the content element entity;

[0017] Obtain the target vehicle condition group corresponding to the vehicle information, and use the target vehicle condition group as the element tag corresponding to the content element entity.

[0018] The first content element corresponding to the original content element is constructed using the element identifier, the content element entity, and the element tag.

[0019] The vehicle information includes at least one of the following: vehicle model information, model year information, and vehicle configuration information.

[0020] In some feasible implementations, after constructing the first content element corresponding to the original content element using the element identifier, the content element entity, and the element tag, the method further includes:

[0021] In response to the correctness check operation for the first content element, a content template corresponding to the system update description entry is output, the content template including several first content elements that have passed the check.

[0022] In some feasible implementations, matching the element tags with a preset vehicle condition group to obtain the content element set corresponding to the preset vehicle condition group includes:

[0023] The preset vehicle condition group is matched with the content element tags in each of the first content elements in the content template, and the first content element containing the target content element tag of the preset vehicle condition group is taken as the second content element.

[0024] Each of the second content elements is combined into a content element set corresponding to the preset vehicle condition group.

[0025] In some feasible implementations, the content element entity includes at least display format information, and generating the system update description page corresponding to the content element set includes:

[0026] The content element set is converted into a corresponding system update instructions page using the aforementioned display format information.

[0027] This invention also discloses a system update description processing apparatus, comprising:

[0028] The data acquisition module is used to acquire system update description entries and the original content elements corresponding to the system update description entries;

[0029] The tagging module is used to tag the original content elements to obtain the corresponding first content element, wherein the first content element includes at least an element tag for characterizing the vehicle condition group to which the first content element is applicable.

[0030] The matching module is used to match the element tags with preset vehicle condition groups to obtain the content element set corresponding to each preset vehicle condition group, and generate the system update description page corresponding to the content element set.

[0031] The push module is used to push the system update instructions page to vehicles corresponding to the preset vehicle condition group.

[0032] In some feasible implementations, the push module is specifically used for:

[0033] Compare the content element sets corresponding to each of the preset vehicle condition groups, and determine the push range corresponding to the system update instructions page based on the comparison results;

[0034] The corresponding system update instructions page is pushed to the vehicles within the push range.

[0035] In some feasible implementations, the push module is specifically used for:

[0036] Obtain the element identifier corresponding to each of the first content elements in the content element set;

[0037] Add the preset vehicle condition groups corresponding to the target content element sets containing the exact same element identifier to the same push batch to obtain the push range corresponding to each push batch.

[0038] In some feasible implementations, the original content element includes at least a content element entity and an element identifier, and the tagging module is specifically used for:

[0039] The content element entity is identified to obtain the vehicle information corresponding to the content element entity;

[0040] Obtain the target vehicle condition group corresponding to the vehicle information, and use the target vehicle condition group as the element tag corresponding to the content element entity.

[0041] The first content element corresponding to the original content element is constructed using the element identifier, the content element entity, and the element tag.

[0042] The vehicle information includes at least one of the following: vehicle model information, model year information, and vehicle configuration information.

[0043] In some feasible implementations, the apparatus further includes:

[0044] The verification module is used to respond to the correctness verification operation for the first content element and output the content template corresponding to the system update description entry, wherein the content template includes several first content elements that have passed the verification.

[0045] In some feasible implementations, the matching module is specifically used for:

[0046] The preset vehicle condition group is matched with the content element tags in each of the first content elements in the content template, and the first content element containing the target content element tag of the preset vehicle condition group is taken as the second content element.

[0047] Each of the second content elements is combined into a content element set corresponding to the preset vehicle condition group.

[0048] In some feasible implementations, the content element entity includes at least display format information, and the matching module is specifically used for:

[0049] The content element set is converted into a corresponding system update instructions page using the aforementioned display format information.

[0050] This invention also discloses an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0051] The memory is used to store computer programs;

[0052] When the processor executes a program stored in the memory, it implements the method described in the embodiments of the present invention.

[0053] This invention also discloses a computer-readable storage medium storing instructions that, when executed by one or more processors, cause the processors to perform the methods described in this invention.

[0054] The embodiments of the present invention have the following advantages:

[0055] In this embodiment of the invention, during the vehicle system update process, system update description entries and their corresponding original content elements are obtained. These original content elements are then tagged to obtain corresponding first content elements. Each first content element includes at least an element tag representing the vehicle condition group to which it applies. The element tags are then matched with preset vehicle condition groups to obtain content element sets corresponding to each preset vehicle condition group. A system update description page corresponding to each content element set is then generated. The preset vehicle condition group can be an identifier representing a set of vehicles with the same vehicle attributes. Finally, the system update description page is pushed to the vehicles corresponding to the preset vehicle condition groups. Thus, during the system update process, by tagging system update description entries and matching them with vehicle condition groups, the content involved in the update process is effectively categorized, reducing the resources required for system update descriptions and ensuring the accuracy of the updated content. Simultaneously, by generating corresponding system update description pages, the cost of manual maintenance is further reduced, and pushing content according to vehicle condition groups effectively ensures the accuracy of the content push. Attached Figure Description

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

[0057] Figure 1 This is a flowchart illustrating the steps of a system update process provided in an embodiment of the present invention.

[0058] Figure 2This is a schematic diagram of the content template provided in an embodiment of the present invention;

[0059] Figure 3 This is a structural block diagram of a system update processing device provided in an embodiment of the present invention. Detailed Implementation

[0060] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0061] As an example, during the maintenance of vehicle system update content, the system update instructions for different models are generally the same. However, due to differences in vehicle hardware configuration, there are some differences in the system update instructions. If the system update instructions for each model are maintained manually, the same parts cannot be reused, thereby increasing maintenance costs.

[0062] In this invention, during the vehicle system update process, system update description entries and their corresponding original content elements are obtained. These original content elements are then tagged to obtain corresponding first content elements. Each first content element includes at least an element tag representing the vehicle condition group to which it applies. The element tags are then matched with preset vehicle condition groups to obtain content element sets corresponding to each preset vehicle condition group. A system update description page corresponding to each content element set is then generated. The preset vehicle condition group can be an identifier representing a set of vehicles with the same vehicle attributes. Finally, the system update description page is pushed to the vehicles corresponding to the preset vehicle condition groups. Thus, during the system update process, tagging system update description entries and matching them with vehicle condition groups effectively categorizes the content involved in the update process, reducing the resources required for system update descriptions and ensuring the accuracy of the updated content. Furthermore, generating corresponding system update description pages further reduces the cost of manual maintenance, and pushing content according to vehicle condition groups effectively ensures the accuracy of the content push.

[0063] To enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, some technical features involved in the embodiments of the present invention are explained and described below:

[0064] Vehicle condition group, which can be the identifier corresponding to a set of vehicles. A set of vehicles can contain at least one vehicle with the same vehicle attributes. Vehicle attributes can include information such as vehicle model, year, and configuration.

[0065] System updates can involve upgrading or repairing the firmware in vehicle equipment. Each system update is accompanied by a corresponding system update description, which explains the functional changes that the system update will bring to the vehicle.

[0066] System update description entries refer to the elements that make up the system update description. Each system update description entry can correspond to a vehicle function change caused by the system upgrade.

[0067] A system update note is a description of the functional changes that a system update will bring to the vehicle. A single system update note may contain multiple entries. Different vehicle models may have different system update notes for the same system update due to differences in their onboard hardware.

[0068] Content elements correspond to system update description entries, and each content element can be converted into a system update description entry. A content element can contain two attributes: a content element entity and a content element tag. Furthermore, each content element has its own element identifier, which is globally unique.

[0069] A content element entity refers to the content displayed to the user after the final update description entry is generated. It exists at least in the form of text descriptions and images. It should be noted that the content element entity includes vehicle condition information and display format information that the content element is adapted to (such as indicating whether the element is a first-level heading, second-level heading, or list item in the final presentation).

[0070] The content element tag refers to the vehicle model to which the content element is applicable. A content element can have multiple content element tags, indicating that the content element can be applied to multiple vehicle models at the same time.

[0071] Tagging model refers to the LLM (Large Language Model) introduced in the process of processing content elements. This large language model can analyze text content and automatically generate content element tags corresponding to the content elements.

[0072] The system update module can be divided into multiple update modules for a single system update, including but not limited to smart cockpit, smart driving, and smart electric. Each module has its own corresponding system update instructions. By aggregating the update content of each module together, we obtain the complete vehicle system update instructions for a single system update.

[0073] A content template is a container for content elements, containing all the content elements required for a single firmware update. Within the content template, the content elements can be managed, such as adding new content elements, editing content element entities, and editing content element tags.

[0074] Specifically, refer to Figure 1 The diagram illustrates a process flowchart for a system update description provided in an embodiment of the present invention, which may specifically include the following steps:

[0075] Step 101: Obtain the system update description entry and the original content element corresponding to the system update description entry;

[0076] In this embodiment of the invention, vehicles can be divided into different vehicle sets based on vehicle information. Each vehicle set contains vehicles with the same vehicle attributes. For example, a vehicle set may contain vehicles of the same model year, vehicles with the same vehicle configuration information, or vehicles with at least two of the same vehicle attributes (model year, vehicle configuration information, etc.). Simultaneously, each vehicle set is assigned a globally unique vehicle condition group, which is used to distinguish different vehicles.

[0077] Optionally, vehicle configuration information may include one of the following: intelligent cockpit configuration information, autonomous driving configuration information, powertrain configuration information, drive configuration information, and network configuration information. For example, intelligent cockpit configuration information may include configuration information related to the central control entertainment system and multimedia functions. During system updates, different vehicles with the same central control entertainment system and multimedia functions can be grouped into the same vehicle set. For autonomous driving configuration information, different vehicles with the same level of intelligence can be grouped into the same vehicle set, such as grouping L2-level vehicles into the same vehicle set and L3-level vehicles into the same vehicle set. Other vehicle configuration information can be grouped into the same vehicle set in the same way, so as to distinguish different vehicles based on vehicle condition groups and perform targeted system updates.

[0078] During vehicle system updates, since different vehicle sets may correspond to different system update instructions, it is necessary to process the data corresponding to the system update instructions first to ensure the accuracy of the content and delivery of the system update instructions. Specifically, the system update instruction entries and their corresponding original content elements can be obtained first to determine the update content involved in this system update process.

[0079] For example, during this system update, adding features such as "ELK (Emergency Lane Keeping) ability to avoid vehicles on the side" to vehicles will allow us to obtain the corresponding system update description entry and determine the original content element corresponding to that entry. Optionally, the original content element may include at least a sequence number, element identifier, and content element entity, etc., which is not limited in this invention.

[0080] In one example, a corresponding content template container can be created, and all content elements corresponding to all system update description entries included in this system update description can be added to the content template container to check the correctness between the content element entities and the content element tags one by one.

[0081] Step 102: Tag the original content element to obtain the corresponding first content element, wherein the first content element includes at least an element label for characterizing the vehicle condition group to which the first content element is applicable.

[0082] Once the original content elements are identified, i.e., the vehicle function changes involved in this system update are determined, these original content elements can be tagged to determine which vehicles each original content element is effective on, thus obtaining the tagged first content element. This first content element can at least include an element label representing the group of vehicle conditions to which the first content element applies. This element label accurately distinguishes the group of vehicle conditions to which different first content elements apply, i.e., determines which vehicles the content element is effective on. This facilitates subsequent content delivery based on element labels, ensuring the accuracy of the delivery results.

[0083] It should be noted that, unlike the original content element, the first content element can also contain a serial number, element identifier, and content element entity, as well as tagged element tags. The element tags can be used to determine which vehicles the vehicle function corresponding to the original content element is effective on.

[0084] In some feasible implementations, since the original content element includes at least the content element entity and the element identifier, the process of tagging the original content element can identify the content element entity, obtain the vehicle information corresponding to the content element entity, obtain the target vehicle condition group corresponding to the vehicle information, use the target vehicle condition group as the element label corresponding to the content element entity, and then use the element identifier, content element entity, and element label to construct the first content element corresponding to the original content element.

[0085] Optionally, the content element entity can be text, image, etc. By recognizing the content element entity, the vehicle information used by the content element marked in the content element entity can be effectively analyzed. Based on the recognized vehicle information, the corresponding target vehicle condition group can be determined, and the target vehicle condition group can be used as the element label of the original content element. Then, the element label is added to the original content element to obtain the tagged first content element. By tagging the system update content, the set of vehicles applicable to each system update content can be effectively divided, so that the system update content can be pushed to the corresponding vehicles in a targeted manner, ensuring the accuracy of the system update content and the accuracy of the push.

[0086] In addition, after the first content element is obtained by tagging, the tagging result of the first content element can be checked for correctness to determine whether the tagging result is accurate. Specifically, in response to the correctness check operation for the first content element, the content template corresponding to the system update description item can be output. The content template includes several first content elements that have passed the check. Thus, by checking the correctness of the tagging result, the accuracy of the system update content is further guaranteed.

[0087] It should be noted that during the aforementioned tagging and correctness verification process, the content element entities in the original content elements can be analyzed using a corresponding tagging model to identify the vehicle information applicable to the content elements tagged by those entities. Then, based on this vehicle information, the vehicle being used is identified, and based on the identification result, the target vehicle condition group to which the vehicle belongs is determined. Furthermore, after tagging is completed, the correctness of the tagging model's processing of content element labels can be verified manually, thus obtaining the tagged content elements.

[0088] In one example, suppose there exists an original content element containing the following content:

[0089] [Serial Number]: 1

[0090] ID: 1212165156151

[0091] [Content Element Entity]: [LL Only] ELK adds the ability to avoid vehicles on the side.

[0092] For the text content contained in the content element entity, the applicable vehicle information, namely the field "

LL Only

[0093] [Serial Number]: 1

[0094] ID: 1212165156151

[0095] [Content Element Entity]: [LL Only] ELK adds the ability to avoid vehicles on the side.

[0096] [Tags]: Vehicle Condition Group 1, Vehicle Condition Group 2

[0097] Furthermore, after tagging the original content elements, manual checks can be performed to verify the correctness of the tagging model's processing of the content element tags. Once the manual check is complete, the data contained in the content template can be... Figure 2 As shown, different content elements can correspond to at least one vehicle condition group, thereby effectively dividing the set of vehicles to which each system update content is applicable, so that the system update content can be pushed to the corresponding vehicles in a targeted manner, ensuring the accuracy of the system update content and the accuracy of the push.

[0098] Step 103: Match the element tags with preset vehicle condition groups to obtain the content element set corresponding to each preset vehicle condition group, and generate the system update description page corresponding to the content element set. The preset vehicle condition group is the identifier corresponding to a set of vehicles that represent the same vehicle attributes.

[0099] After tagging the content elements, the system update instructions can be further configured for all vehicles. This is achieved by matching each first content element in the content template with preset vehicle condition groups, obtaining the content element set corresponding to each preset vehicle condition group, and generating the corresponding system update instruction page. Here, the preset vehicle condition group is an identifier representing a set of vehicles with the same vehicle attributes; the system update instruction page is the page presented to the user, which can be a visualization of the content elements. This process ensures the accuracy of content delivery by matching the content element set with the preset vehicle condition group to determine the update content for each vehicle, and further reduces the cost of manual maintenance by generating the corresponding system update instruction page.

[0100] In some feasible implementations, by matching the preset vehicle condition group with the content element tags in each first content element in the content template, the first content element containing the target content element tag of the preset vehicle condition group is taken as the second content element. Then, each second content element is combined into a content element set corresponding to the preset vehicle condition group. Thus, by matching the content element tag (i.e., the target vehicle condition group) with the preset vehicle condition group, the mapping relationship between content elements and vehicles is determined. In other words, the mapping relationship between vehicle update content and vehicles that support vehicle update content is determined, ensuring the accuracy of content push.

[0101] For example, suppose the first content element includes at least:

[0102] First content element ①:

[0103] [Serial Number]: 1

[0104] [ID]: 1212165156150

[0105] [Content Element Entity]: Update Description Entry a

[0106] [Tags]: Vehicle Condition Group 1, Vehicle Condition Group 2

[0107] First content element ②:

[0108] [Serial Number]: 2

[0109] ID: 1212165156151

[0110] [Content Element Entity]: Update Description Entry b

[0111] [Tag]: Vehicle Condition Group 1

[0112] First content element ③:

[0113] [Serial Number]: 3

[0114] [ID]: 1212165156153

[0115] [Content Element Entity]: Update Description Entry c

[0116] [Tags]: Vehicle Condition Group 1, Vehicle Condition Group 2, Vehicle Condition Group 3

[0117] First content element ④:

[0118] [Serial Number]: 4

[0119] [ID]: 1212165156154

[0120] [Content Element Entity]: Update Description Entry d

[0121] [Tag]: Vehicle Condition Group 2

[0122] ……wait.

[0123] For the first content element mentioned above, the target vehicle condition group contained in the first content element can be matched with the preset vehicle condition group to determine the content element corresponding to each preset vehicle condition group, that is:

[0124] Assuming the vehicle condition groups include Vehicle Condition Group 1, Vehicle Condition Group 2, Vehicle Condition Group 3, etc., then the content elements corresponding to Vehicle Condition 1 include First Content Element ①, First Content Element ②, and First Content Element ③, representing that all vehicles corresponding to Vehicle Condition Group 1 need to undergo update description items a, b, and c for vehicle functions. The content elements corresponding to Vehicle Condition Group 2 include First Content Element ①, First Content Element ③, and First Content Element ④, representing that all vehicles corresponding to Vehicle Condition Group 1 need to undergo update description items a, c, and c for vehicle functions. The content elements corresponding to Vehicle Condition Group 3 include First Content Element ③, representing that all vehicles corresponding to Vehicle Condition Group 3 need to undergo update description item c for vehicle functions. By matching the content element tags (i.e., the target vehicle condition group) with the preset vehicle condition groups, the mapping relationship between content elements and vehicles is determined, that is, the mapping relationship between vehicle update content and vehicles that support vehicle update content is determined, ensuring the accuracy of content push.

[0125] Furthermore, since the content element entity includes at least display format information, the content element set can be converted into a corresponding system update instruction page using the display format information. This converts the content elements into a page that can be viewed by the user, so that in the subsequent content push process, the corresponding system update instruction page can be pushed to the relevant vehicle, allowing the user to intuitively perceive the relevant content to be updated for the vehicle through the system update instruction page.

[0126] Furthermore, since the entire vehicle system update can be divided into multiple update modules during a single system update, after being divided into different update modules, for each update module, the content elements corresponding to each update module can be matched, the element set corresponding to each update module can be determined, and then a system update description page corresponding to each update module can be generated so that users can intuitively view the update description content corresponding to the corresponding update module. This invention does not impose any limitations on this.

[0127] Step 104: Push the system update instructions page to the vehicles corresponding to the preset vehicle condition group.

[0128] After converting content elements into corresponding system update instruction pages, these pages can be pushed to vehicles corresponding to preset vehicle condition groups. During the system update process, by tagging system update instruction items and matching them with vehicle condition groups, the content involved in the update process can be effectively categorized, reducing the resources required for system update instructions and ensuring the accuracy of the updated content. At the same time, by generating corresponding system update instruction pages, the cost and resources of manual maintenance are further reduced, and pushing content according to vehicle condition groups can effectively ensure the accuracy of content delivery.

[0129] It should be noted that before officially pushing out the content, the completeness of the content can be verified. This means checking whether each vehicle condition group has the system update instructions corresponding to each update module. For example, does vehicle condition group 1 have the system update instructions corresponding to update modules such as smart cockpit, smart driving, and smart electric, thus ensuring the completeness of the content?

[0130] Furthermore, considering that different vehicle condition groups may have completely identical system update instructions during a single system update, a consistency check can be performed on the system update instructions before they are actually pushed to the corresponding vehicles. Specifically, the content element sets corresponding to each of the preset vehicle condition groups can be compared. Based on the comparison results, the push range corresponding to the system update instruction page can be determined. Then, the corresponding system update instruction page is pushed to the vehicles within the push range. By comparing the content element sets corresponding to different vehicle condition groups, a consistency check is achieved, thereby determining the push range and pushing the corresponding system update instructions to vehicles within the push range, reducing the number of times system update instructions are pushed.

[0131] In a specific implementation, the element identifiers corresponding to each of the first content elements in the content element set are obtained, and then the element identifiers corresponding to different content element sets are compared. Based on the comparison results, the preset vehicle condition groups corresponding to the target content element sets containing the same element identifiers are added to the same push batch, thereby obtaining the push range corresponding to each push batch. Then, the system update instructions page is pushed to the designated vehicle according to the determined push range, thereby reducing the number of times the system update instructions are pushed.

[0132] In one example, the process can be as follows: traverse the content element sets corresponding to all current preset vehicle condition groups and determine if the traversal is complete. If not, select an unprocessed preset vehicle condition group and obtain all element identifiers contained in the content element set corresponding to that preset vehicle condition group. Check if the content element sets corresponding to other preset vehicle condition groups contain the exact same element identifiers. If they do, create a push batch for that preset vehicle condition group and add both preset vehicle condition groups to the same push batch. If they do not contain the exact same element identifiers, create the corresponding push batches as well. Then, based on the preset vehicle condition groups corresponding to each push batch, determine the push range corresponding to each push batch (i.e., determine the vehicles to be pushed to in each push batch). Then, push the system update description page converted from the corresponding element content set to the corresponding vehicle. By comparing the content element sets corresponding to different vehicle condition groups, consistency judgment is achieved, thereby determining the push range. This allows the push of the corresponding system update description to vehicles within the push range, reducing the number of times system update descriptions are pushed.

[0133] It should be noted that the embodiments of the present invention include, but are not limited to, the examples described above. It is understood that those skilled in the art can make further settings according to actual needs under the guidance of the ideas in the embodiments of the present invention, and the present invention does not limit such settings.

[0134] In this embodiment of the invention, during the vehicle system update process, system update description entries and their corresponding original content elements are obtained. These original content elements are then tagged to obtain corresponding first content elements. Each first content element includes at least an element tag representing the vehicle condition group to which it applies. The element tags are then matched with preset vehicle condition groups to obtain content element sets corresponding to each preset vehicle condition group. A system update description page corresponding to each content element set is then generated. The preset vehicle condition group can be an identifier representing a set of vehicles with the same vehicle attributes. Finally, the system update description page is pushed to the vehicles corresponding to the preset vehicle condition groups. Thus, during the system update process, by tagging system update description entries and matching them with vehicle condition groups, the content involved in the update process is effectively categorized, reducing the resources required for system update descriptions and ensuring the accuracy of the updated content. Simultaneously, by generating corresponding system update description pages, the cost of manual maintenance is further reduced, and pushing content according to vehicle condition groups effectively ensures the accuracy of the content push.

[0135] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0136] Reference Figure 3 The diagram shows a structural block diagram of a system update processing device provided in an embodiment of the present invention, which may specifically include the following modules:

[0137] The data acquisition module 301 is used to acquire system update description entries and the original content elements corresponding to the system update description entries;

[0138] The tagging module 302 is used to tag the original content element to obtain the corresponding first content element, wherein the first content element includes at least an element label for characterizing the vehicle condition group to which the first content element is applicable.

[0139] The matching module 303 is used to match the element tags with preset vehicle condition groups to obtain the content element set corresponding to each preset vehicle condition group, and generate the system update description page corresponding to the content element set.

[0140] The push module 304 is used to push the system update instructions page to the vehicles corresponding to the preset vehicle condition group.

[0141] In some feasible implementations, the push module 304 is specifically used for:

[0142] Compare the content element sets corresponding to each of the preset vehicle condition groups, and determine the push range corresponding to the system update instructions page based on the comparison results;

[0143] The corresponding system update instructions page is pushed to the vehicles within the push range.

[0144] In some feasible implementations, the push module 304 is specifically used for:

[0145] Obtain the element identifier corresponding to each of the first content elements in the content element set;

[0146] Add the preset vehicle condition groups corresponding to the target content element sets containing the exact same element identifier to the same push batch to obtain the push range corresponding to each push batch.

[0147] In some feasible implementations, the original content element includes at least a content element entity and an element identifier, and the tagging module 302 is specifically used for:

[0148] The content element entity is identified to obtain the vehicle information corresponding to the content element entity;

[0149] Obtain the target vehicle condition group corresponding to the vehicle information, and use the target vehicle condition group as the element tag corresponding to the content element entity.

[0150] The first content element corresponding to the original content element is constructed using the element identifier, the content element entity, and the element tag.

[0151] The vehicle information includes at least one of the following: vehicle model information, model year information, and vehicle configuration information.

[0152] In some feasible implementations, the apparatus further includes:

[0153] The verification module is used to respond to the correctness verification operation for the first content element and output the content template corresponding to the system update description entry, wherein the content template includes several first content elements that have passed the verification.

[0154] In some feasible implementations, the matching module 303 is specifically used for:

[0155] The preset vehicle condition group is matched with the content element tags in each of the first content elements in the content template, and the first content element containing the target content element tag of the preset vehicle condition group is taken as the second content element.

[0156] Each of the second content elements is combined into a content element set corresponding to the preset vehicle condition group.

[0157] In some feasible implementations, the content element entity includes at least presentation format information, and the matching module 303 is specifically used for:

[0158] The content element set is converted into a corresponding system update instructions page using the aforementioned display format information.

[0159] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0160] In addition, this invention also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the various processes of the processing method embodiments described above for system update and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0161] Furthermore, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the processing method described above for system update.

[0162] As the apparatus embodiment is basically similar to the method embodiment, it is described in a relatively simple manner. For relevant details, please refer to the description of the method embodiment.

[0163] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0164] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus, or computer program products. Therefore, embodiments of the present invention can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of the present invention can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0165] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0166] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0167] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0168] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0169] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0170] The foregoing has provided a detailed description of a system update description processing method, a system update description processing apparatus, an electronic device, and a computer-readable storage medium. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for processing system update instructions, characterized in that, include: Obtain the system update description entry and the original content element corresponding to the system update description entry; The original content elements are tagged to obtain the corresponding first content elements, wherein the first content elements include at least element tags for characterizing the vehicle condition group to which the first content elements are applicable. The element tags are matched with preset vehicle condition groups to obtain the content element set corresponding to each preset vehicle condition group, and the system update description page corresponding to the content element set is generated. The system update instructions page is pushed to the vehicles corresponding to the preset vehicle condition group.

2. The method according to claim 1, characterized in that, The step of pushing the system update instructions page to vehicles corresponding to the preset vehicle condition group includes: Compare the content element sets corresponding to each of the preset vehicle condition groups, and determine the push range corresponding to the system update instructions page based on the comparison results; The corresponding system update instructions page is pushed to the vehicles within the push range.

3. The method according to claim 2, characterized in that, The step of comparing the content element sets corresponding to each of the preset vehicle condition groups and determining the push range corresponding to the system update instructions page based on the comparison results includes: Obtain the element identifier corresponding to each of the first content elements in the content element set; Add the preset vehicle condition groups corresponding to the target content element sets containing the exact same element identifier to the same push batch to obtain the push range corresponding to each push batch.

4. The method according to any one of claims 1 to 3, characterized in that, The original content element includes at least a content element entity and an element identifier. Tagging the original content element to obtain the corresponding first content element includes: The content element entity is identified to obtain the vehicle information corresponding to the content element entity; Obtain the target vehicle condition group corresponding to the vehicle information, and use the target vehicle condition group as the element tag corresponding to the content element entity. The first content element corresponding to the original content element is constructed using the element identifier, the content element entity, and the element tag. The vehicle information includes at least one of the following: vehicle model information, model year information, and vehicle configuration information.

5. The method according to claim 4, characterized in that, After constructing the first content element corresponding to the original content element using the element identifier, the content element entity, and the element tag, the method further includes: In response to the correctness check operation for the first content element, a content template corresponding to the system update description entry is output, the content template including several first content elements that have passed the check.

6. The method according to claim 5, characterized in that, The step of matching the element tags with a preset vehicle condition group to obtain the content element set corresponding to the preset vehicle condition group includes: The preset vehicle condition group is matched with the content element tags in each of the first content elements in the content template, and the first content element containing the target content element tag of the preset vehicle condition group is taken as the second content element. Each of the second content elements is combined into a content element set corresponding to the preset vehicle condition group.

7. The method according to claim 4 or 5, characterized in that, The content element entity includes at least display format information, and the generation of the system update description page corresponding to the content element set includes: The content element set is converted into a corresponding system update instructions page using the aforementioned display format information.

8. A processing apparatus for system update instructions, characterized in that, include: The data acquisition module is used to acquire system update description entries and the original content elements corresponding to the system update description entries; The tagging module is used to tag the original content elements to obtain the corresponding first content element, wherein the first content element includes at least an element tag for characterizing the vehicle condition group to which the first content element is applicable. The matching module is used to match the element tags with preset vehicle condition groups to obtain the content element set corresponding to each preset vehicle condition group, and generate the system update description page corresponding to the content element set. The push module is used to push the system update instructions page to vehicles corresponding to the preset vehicle condition group.

9. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; The memory is used to store computer programs; When the processor executes a program stored in the memory, it implements the method as described in any one of claims 1-7.

10. A computer-readable storage medium having instructions stored thereon that, when executed by one or more processors, cause the processors to perform the method as described in any one of claims 1-7.

Images