Vehicle control APP burying point updating method and device, equipment, storage medium and computer program product

Abstract

The invention relates to the technical field of automobile electronic control, in particular to an automobile control APP burying point updating method and device, equipment, a storage medium and a computer program product. The method comprises the following steps: creating a buried point template, and carrying out unique version identification on the buried point template; determining a burying point updating strategy according to the application range of the burying point template; based on the burying point updating strategy, a burying point updating task is generated, and the burying point updating task comprises task effective time and an upgrading condition; pushing the burying point updating task to the to-be-updated APP; after the to-be-updated APP receives the burying point updating task, whether the to-be-updated APP meets an upgrading condition or not is judged based on the current version and the unique version identifier of the to-be-updated APP; if yes, the to-be-updated APP is updated based on the task effective time and the burying point template, and the efficiency and safety of vehicle control APP burying point updating are improved.

Description

Technical Field

[0001] The present application relates to the field of automotive electronic control technology, and in particular to a method, device, equipment, storage medium and computer program product for updating a vehicle control APP. Background Art

[0002] With the rapid development of smart car technology, automotive electronic control systems have gradually shifted from traditional mechanical control to a software-centric control mode. As an important part of the automotive electronic control system, the in-vehicle intelligent terminal is responsible for the interaction between people and cars. In this context, the car control APP (car control application) is a bridge connecting smart cars and users, and its functions and performance directly affect the user experience and the level of vehicle intelligence. In the field of software development, in order to better understand user behavior and optimize application performance, tracking technology is usually used. Tracking technology collects user behavior data, application performance data and other information by embedding code snippets in specific locations of the application. At present, the tracking technology of the car control APP is mainly based on static tracking, and static tracking cannot dynamically adjust the tracking field or structure according to actual needs. Once the tracking information needs to be added or modified, the application must be republished, which greatly increases the development cost and has an adverse impact on the user experience. In complex business scenarios, different tracking data may be required under different conditions, and static tracking cannot flexibly respond to diverse needs; in addition, static tracking information is easily tampered with during transmission or storage, which may cause data distortion or even malicious use, further threatening user privacy and data security. Therefore, how to improve the efficiency and security of vehicle control APP tracking updates has become a technical problem that needs to be solved urgently. Summary of the invention

[0003] The main purpose of this application is to provide a method, device, equipment, storage medium and computer program product for updating vehicle control APPs, aiming to solve the technical problem of how to improve the efficiency and security of updating vehicle control APPs.

[0004] To achieve the above purpose, the present application provides a method for updating a vehicle control APP tracking point, the method comprising the following steps:

[0005] Create a tracking template and uniquely identify the version of the tracking template;

[0006] Determine a tracking point update strategy according to the applicable scope of the tracking point template;

[0007] Based on the tracking point update strategy, generate a tracking point update task, wherein the tracking point update task includes a task effective time and an upgrade condition;

[0008] Push the tracking update task to the APP to be updated;

[0009] After the APP to be updated receives the tracking update task, based on the current version of the APP to be updated and the unique version identifier, it is determined whether the APP to be updated meets the upgrade condition;

[0010] If satisfied, the APP to be updated is updated based on the task effective time and the tracking template.

[0011] In one embodiment, after the step of updating the APP to be updated based on the task effective time and the tracking template if the conditions are met, the method further includes:

[0012] After the update is completed, the update result is obtained, which includes the update status, update time, and version numbers before and after the update;

[0013] If the update status is successful, sending a successful update notification to the user terminal;

[0014] If the update status is update failure, the APP to be updated is rolled back to the version status before the update.

[0015] In one embodiment, before the step of updating the APP to be updated based on the task effective time and the tracking template if the conditions are met, the step further includes:

[0016] If the APP to be updated does not meet the upgrade conditions, identify the reason for not meeting the conditions;

[0017] Based on the reasons for non-satisfaction, feedback information is generated, wherein the feedback information includes a preset solution strategy corresponding to the reasons for non-satisfaction;

[0018] The feedback information is pushed to the user terminal.

[0019] In one embodiment, the step of creating a tracking template and uniquely identifying the tracking template includes:

[0020] Based on the preset definition strategy, define the fields and attributes in the tracking template;

[0021] Classify the defined embedding templates;

[0022] Based on the classification result, the applicable scope of the embedding template is associated, and a unique version identification is performed on the embedding template.

[0023] In one embodiment, if the conditions are met, the step of updating the APP to be updated based on the task effective time and the tracking template includes:

[0024] If satisfied, obtain a preset verification code, and perform integrity verification on the embedding template based on the preset verification code;

[0025] If the tracking target passes the integrity verification, based on the structural requirements of the APP framework to be updated, the compatibility of the tracking template is verified;

[0026] If the tracking template passes the compatibility verification, back up the current template of the APP to be updated;

[0027] Replace the current template of the APP to be updated with the embedding template, and update the fields and attributes defined by the embedding template.

[0028] In one embodiment, the step of determining the tracking point update strategy according to the applicable scope of the tracking point template includes:

[0029] Convert the applicable scope of the tracking template into update conditions, where the update conditions include version matching rules, device matching rules, operating system rules, and target user rules;

[0030] The version matching rule, the device matching rule, the operating system rule and the target user rule are combined by logical operation, and the preset upgrade method and the preset time strategy are combined to obtain the tracking point update strategy.

[0031] In addition, to achieve the above purpose, the present application also proposes a vehicle control APP tracking update device, the vehicle control APP tracking update device comprising:

[0032] A template creation module is used to create a tracking template and uniquely identify the version of the tracking template;

[0033] An update strategy module, used to determine a tracking point update strategy according to the applicable scope of the tracking point template;

[0034] A task generation module, used to generate a tracking point update task based on the tracking point update strategy, wherein the tracking point update task includes a task effective time and an upgrade condition;

[0035] A push module is used to push the tracking update task to the APP to be updated;

[0036] A condition judgment module, configured to judge whether the APP to be updated meets the upgrade condition based on the current version of the APP to be updated and the unique version identifier after the APP to be updated receives the tracking update task;

[0037] The target module is used to update the APP to be updated based on the task effectiveness time and the tracking template if the conditions are met.

[0038] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle control APP tracking point update device, which includes: a memory, a processor, and a vehicle control APP tracking point update program stored in the memory and runnable on the processor, and the vehicle control APP tracking point update program is configured to implement the steps of the vehicle control APP tracking point update method described above.

[0039] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, on which a vehicle control APP tracking update program is stored. When the vehicle control APP tracking update program is executed by the processor, the steps of the vehicle control APP tracking update method described above are implemented.

[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the vehicle control APP tracking update method as described above.

[0041] This application creates a tracking template and uniquely identifies the version of the tracking template; determines the tracking update strategy according to the applicable scope of the tracking template; generates a tracking update task based on the tracking update strategy, and the tracking update task includes the task effective time and upgrade conditions; pushes the tracking update task to the APP to be updated; after the APP to be updated receives the tracking update task, it determines whether the APP to be updated meets the upgrade conditions based on the current version and unique version identifier of the APP to be updated; if it meets the conditions, the APP to be updated is updated based on the task effective time and the tracking template. This application achieves precise tracking management and version traceability to ensure the efficiency of the update by creating a tracking template and introducing a unique version identifier; by formulating an update strategy according to the applicable scope and generating a tracking update task including the task effective time and upgrade conditions, the tracking update is targeted and flexible; by pushing the update task to the APP to be updated and judging whether the upgrade conditions are met based on the current version and unique version identifier, redundant operations are avoided and resource utilization efficiency is further improved; at the same time, through strict effective time management and condition matching, the security and reliability of the update operation are ensured, thereby effectively improving the efficiency, security and flexibility of the tracking update of the vehicle control APP. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 This is a flow chart of the first embodiment of the method for updating the tracking points of the vehicle control APP of the present application;

[0043] Figure 2 This is a schematic diagram of a sub-flow in the second embodiment of the method for updating the tracking points of the vehicle control APP of this application;

[0044] Figure 3This is a schematic diagram of a sub-flow in the third embodiment of the method for updating the tracking points of the vehicle control APP of this application;

[0045] Figure 4 This is a schematic diagram of the module structure of the vehicle control APP tracking update device according to an embodiment of the present application;

[0046] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the vehicle control APP tracking update method in the embodiment of the present application.

[0047] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0048] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0049] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0050] It should be noted that with the rapid development of smart car technology, automotive electronic control systems have gradually shifted from traditional mechanical control to a software-based control mode. As an important part of the automotive electronic control system, the in-vehicle intelligent terminal is responsible for the interaction between people and cars. In this context, the car control APP (car control application) is a bridge connecting smart cars and users, and its functions and performance directly affect the user experience and the level of vehicle intelligence. In the field of software development, in order to better understand user behavior and optimize application performance, tracking technology is usually used. Tracking technology collects user behavior data, application performance data and other information by embedding code snippets in specific locations of the application. At present, the tracking technology of the car control APP is mainly based on static tracking, and static tracking cannot dynamically adjust the tracking field or structure according to actual needs. Once the tracking information needs to be added or modified, the application must be republished, which greatly increases the development cost and has an adverse impact on the user experience. In addition, in complex business scenarios, different tracking data may be required under different conditions, and static tracking cannot flexibly respond to diverse needs; in addition, static tracking information is easily tampered with during transmission or storage, which may cause data distortion or even malicious use, further threatening user privacy and data security. Therefore, how to improve the efficiency and security of vehicle control APP tracking updates has become a technical problem that needs to be solved urgently.

[0051] The main solution of this application is: by creating a tracking point template and uniquely identifying the version of the tracking point template; determining the tracking point update strategy according to the applicable scope of the tracking point template; generating a tracking point update task based on the tracking point update strategy, and the tracking point update task includes the task effective time and upgrade conditions; pushing the tracking point update task to the APP to be updated; after the APP to be updated receives the tracking point update task, judging whether the APP to be updated meets the upgrade conditions based on the current version and unique version identifier of the APP to be updated; if satisfied, updating the APP to be updated based on the task effective time and the tracking point template.

[0052] This application achieves precise tracking management and version traceability by creating a tracking template and introducing a unique version identifier, ensuring the efficiency of updates; by formulating update strategies according to the scope of application and generating tracking update tasks that include task effectiveness time and upgrade conditions, the application achieves targeted and flexible tracking updates; by pushing update tasks to the APP to be updated and judging whether the upgrade conditions are met based on the current version and the unique version identifier, redundant operations are avoided and resource utilization efficiency is further improved; at the same time, through strict effectiveness time management and condition matching, the safety and reliability of update operations are ensured, thereby effectively improving the efficiency, security and flexibility of tracking updates of vehicle control APPs.

[0053] It should be noted that the execution subject of the method of this embodiment can be a computing service device with data processing, network communication and program running functions, or it can be the above-mentioned vehicle control APP tracking update device with the same or similar functions. This embodiment and the following embodiments will be described by taking the vehicle control APP tracking update device as an example.

[0054] Based on this, the first embodiment of the method for updating the vehicle control APP tracking point of this application is proposed, please refer to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the vehicle control APP tracking update method of the present application.

[0055] In this embodiment, the vehicle control APP tracking update method includes the following steps:

[0056] S1: Create a tracking template and uniquely identify the version of the tracking template;

[0057] It should be noted that the tracking template is a standardized design for collecting behavioral data within applications. It contains a series of rules for describing and defining tracking events and their fields, such as event names, trigger conditions, data fields and their types. Tracking templates are used to unify the design and management of tracking information to facilitate dynamic adjustment and updates. The unique version identifier is a unique marking symbol used to mark each tracking template. It can be an incremental version number (such as v1.0, v1.1) or a globally unique identifier (UUID) generated based on a hash algorithm. This identifier is used to distinguish different versions of tracking templates to ensure the accuracy and traceability of the template during the update process.

[0058] Specifically, the process of creating a tracking point template first requires defining the tracking point events and fields based on the functional requirements and business goals of the application. Each tracking point event needs to clearly record the name of the event (such as "button click"), trigger conditions (such as "user clicks the submit button"), reported data fields (such as "button name" or "click time"), and field types (such as strings, integers) and length limits. The template needs to be compatible with the APP framework to ensure that it can be loaded at runtime and support dynamic adjustments. Subsequently, these events and their fields are organized into a template structure and stored in the template management system to facilitate subsequent version management and distribution.

[0059] Furthermore, after completing the template design, a unique version identifier needs to be generated for each template to mark the uniqueness and version information of the template. Version numbers such as v1.0 and v1.1 are generated according to time or operation sequence to facilitate distinguishing the iteration history of the template; the identifier is generated using a universally unique identifier (UUID) algorithm to ensure that there will be no conflicts in the distributed system; the template generation time and content summary are combined to generate an identifier to increase the security and uniqueness of the version identifier; the generated version identifier will be bound to the template and stored in the cloud template management system, and the template management interface provides viewing and operation functions to ensure unified management of the template during the update and distribution process.

[0060] By creating tracking point templates, the tracking point information is standardized and modularized, avoiding the redundant design problems of traditional manual tracking points, and significantly improving the design and maintenance efficiency of tracking points. At the same time, the field definition and structure of the management template are unified to facilitate flexible iteration and rapid update of the template. The unique version identifier ensures the uniqueness and version distinction of the template, which helps to accurately match the tracking point information during the update and distribution process, and avoids tracking point information errors or repeated collection problems caused by template confusion. By assigning a version identifier to each template, the version iteration history of the template can be clearly recorded, which is convenient for developers to backtrack and compare historical versions. At the same time, combined with dynamic management capabilities, the latest template can be quickly located and applied when needed, improving system flexibility. The version identifier combined with the verification mechanism (such as hash value) can effectively prevent the template from being tampered with or using the wrong version, providing security for the transmission and update of tracking point information.

[0061] S2: Determine a tracking point update strategy according to the applicable scope of the tracking point template;

[0062] It should be noted that the scope of application refers to the specific conditions under which the tracking template can be applied, including the range of APP versions, device models, operating system versions, user groups, business function modules and other limiting conditions. The tracking update strategy refers to the update plan formulated according to the scope of application and specific needs of the tracking template, which determines how, when and for which devices or versions to update the tracking template.

[0063] Specifically, according to the applicable scope of the tracking template, it is necessary to first clarify the application conditions of the template. By analyzing the definition of the tracking template, determine the compatible APP version (such as applicable to v1.0 to v2.0), device model (such as "DF-100" and above devices), operating system version (such as Android 10 and above or iOS14 and above), and target user group (such as users in a specific area or high-frequency users). During the analysis process, the scope of application can be refined in combination with business needs, such as the tracking fields required in specific scenarios or the collection of specific user behaviors, to ensure the accuracy of the template's usage scenarios.

[0064] Furthermore, after clarifying the scope of application, generate a tracking update strategy based on these conditions. The update strategy must include the following: Version matching rules: define the range of APP versions to which the template applies, and ensure that the template only works on matching versions; Device and user matching rules: filter out device models or user groups that meet the template requirements; Update method and priority: determine the silent update or forced update method based on business needs, and assign priorities to tasks to ensure that important tasks are completed first; Time strategy: set the effective time and validity period of the task to avoid the distribution and execution of invalid tasks. The generated strategy will be stored in the cloud as logical rules (such as AND / OR) and bound to the template for subsequent distribution and execution.

[0065] By accurately defining the scope of application of the tracking template, it can ensure that the tracking update tasks are only distributed to qualified devices and user groups, avoiding the execution of redundant tasks and saving system resources. It supports dynamic adjustment of update strategies based on conditions such as device model, APP version, user group, etc., ensuring personalized and differentiated tracking updates in complex business scenarios to meet diverse needs. Task priority and effective time management based on update strategies can avoid congestion of system update tasks, ensure that key update tasks are completed first, and improve overall execution efficiency. Through strict definition of the scope of application and flexible selection of update methods (such as silent updates), it reduces interference to users, avoids the burden of unnecessary update operations on system operation, and improves system stability and user experience. The formulation of strategies combined with the tracking template version can provide a traceable basis for subsequent update tasks, and optimize future update strategies through statistical analysis results after the strategy is executed.

[0066] S3: Based on the tracking point update strategy, generate a tracking point update task, wherein the tracking point update task includes a task effective time and an upgrade condition.

[0067] It should be noted that the tracking point update strategy refers to the update rules formulated according to the applicable scope of the tracking point template, including the target APP version, device model, operating system version, user group and update method, etc., which are used to guide the distribution and execution of the tracking point template. The tracking point update task is a specific operation plan generated based on the tracking point update strategy. It clarifies the execution conditions and target devices of the task, and contains information such as the task effective time and upgrade conditions as the execution instructions for the update. The task effective time refers to the start time when the update task is allowed to be executed, which is used to ensure that the task is carried out within the correct time range. The upgrade condition refers to the specific conditions for the execution of the task, such as whether the APP version number and the template version number match, etc., which are used to determine whether the device to be updated meets the requirements for executing the task.

[0068] Specifically, before generating a tracking update task, you first need to clarify the execution scope of the task according to the established tracking update strategy. The system will analyze the target device conditions (such as APP version number, device model, operating system version, etc.) and user conditions (such as target groups or behavioral characteristics) set in the strategy, and filter the target devices. For example, filter out user devices with APP versions of v1.0 to v2.0, and at the same time meet the requirement that the operating system version is higher than Android 10. Next, the system determines the specific devices and number of devices that need to be distributed based on the screening results.

[0069] Furthermore, after the screening range is determined, the system will generate a specific tracking update task, and the following contents must be clarified in the task: Task effective time: Set the start time (such as 2024-12-01 00:00:00) and end time (such as 2024-12-15 23:59:59) of the task to ensure that the task is executed within the appropriate time window to avoid execution failure caused by too early or too late; Upgrade conditions: Specify the necessary conditions for task execution, such as whether the current version of the APP to be updated matches the target version range, whether the template version number is lower than the latest version on the cloud, etc.; Update method: Specify the update method of the task, such as silent update (background update without user perception) or forced update (prompting the user to upgrade immediately); The generated task will be bound to the corresponding tracking template and update strategy, and stored in the cloud task management system, to be pushed to the target device for execution.

[0070] By setting the task effective time, we can ensure that the update task is only executed within the appropriate time range to avoid update failure or user experience degradation caused by inappropriate time. Based on the screening of upgrade conditions, the update task can dynamically adapt to the devices and user groups that meet the requirements, avoid unnecessary update operations, and improve the accuracy and execution efficiency of the task. In the process of generating tasks, combined with the screened target device range and task conditions, it can effectively avoid distributing update instructions to irrelevant devices, reduce system resource waste, and realize automatic management and distribution of tasks. Supports multiple methods such as silent updates and forced updates, allowing developers to choose the most suitable update method according to different scenarios, reduce interference with user operations, improve the experience, and ensure the timeliness and effectiveness of task execution. The generated update tasks are bound to strategies and templates, and can optimize the subsequent task generation and execution process by recording and analyzing data such as task completion rate and failure reasons, further improving the overall efficiency and reliability of tracking point updates.

[0071] S4: Push the tracking update task to the APP to be updated;

[0072] It should be noted that push refers to transmitting the generated tracking update task from the cloud to the APP to be updated through network communication to ensure that the task can be accurately sent to the target device to trigger the update process. The APP to be updated refers to the target application whose current version of the tracking template is lower than the latest version in the cloud and meets the task upgrade conditions.

[0073] Specifically, after the tracking point update task is generated, the cloud system needs to push the task to the APP to be updated. First, the cloud task management system will screen out a list of target devices that meet the update conditions and establish a connection with the target devices through the communication channel. During the push process, the cloud will package the key information of the task (such as the task effective time, tracking point template version number, upgrade conditions, etc.) into an encrypted data packet to ensure the security of data transmission. At the same time, in order to reduce resource usage, task push can be carried out in batches and segments to gradually pass the task to the target device to avoid network congestion caused by one-time push.

[0074] Furthermore, when the APP to be updated receives the push task, the APP will verify the task data through local storage, including the integrity check of the task package (such as hash check) and the matching check of the task version (such as whether the task's tracking template version is higher than the local version). After the verification passes, the APP will store the task data in the local task queue and prepare to execute the subsequent update process. If the push fails or the verification fails, the cloud system will record the corresponding error cause and retry the push or report the problem to the administrator based on the cause of the failure (such as network problems or task mismatch).

[0075] Through the cloud batch push mechanism, update tasks can be quickly distributed to multiple eligible target devices, reducing the time and resource consumption required for distribution and improving the efficiency of task execution. During the push process, encrypted communication and verification mechanisms are used to ensure that task data is not tampered with or lost during transmission, enhancing the security and accuracy of the embedded update tasks. By pushing in batches, update tasks can be assigned to different devices to avoid excessive system load caused by one-time distribution. At the same time, the push strategy can be adjusted in real time according to the task status to improve the flexibility of task management. After pushing, the integrity check and version matching check on the APP side ensure that only eligible tasks will be executed, reducing unnecessary operations and laying a reliable foundation for subsequent update processes. When the push fails or the verification fails, the cloud system can record the cause of the failure and respond quickly, and efficiently troubleshoot the problem by retrying or reporting exceptions, thereby improving the success rate of the update task.

[0076] S5: After the APP to be updated receives the tracking update task, based on the current version of the APP to be updated and the unique version identifier, determine whether the APP to be updated meets the upgrade condition;

[0077] It should be noted that the upgrade conditions refer to the necessary conditions for executing the update task, including the current version range of the APP, whether the unique version identifier of the tracking template is lower than the cloud version, the task effective time, etc., which are used to determine whether the APP needs to perform the template update operation.

[0078] Specifically, after the APP to be updated receives the tracking update task pushed by the cloud, it first parses the task data. The parsing content includes: task effective time, unique version identifier of the target template, upgrade conditions and other related parameters. Subsequently, the APP to be updated will read its currently stored tracking template version identifier and current APP version information. This information will be compared with the conditions in the update task to determine whether it meets the update requirements.

[0079] Furthermore, compare the unique version identifier of the local tracking template with the version identifier of the target template in the task. If the local version identifier is lower than the target version, the update requirement is met; if the version is the same as or higher than the target version, the update is not performed. Verify whether the local APP version is within the version range specified by the task. For example, if the task requires the version to be v1.0 to v2.0, and the local version is v2.1, the upgrade condition is not met. Check whether the current time is within the task effective time range. If the task has not yet taken effect or has expired, the update is not performed. When all conditions are met, the APP marks the task as "pending" and enters the subsequent update process; otherwise, the task is marked as "not meeting the conditions" and the task execution is terminated.

[0080] By verifying the current version of the APP to be updated and the unique version identifier of the template, repeated updates or invalid update operations can be effectively avoided, ensuring that update operations are performed only when necessary, and improving the accuracy of tasks and resource utilization efficiency. The upgrade conditions are combined with multi-dimensional judgment criteria such as version number and effective time, which can flexibly adapt to complex business scenarios and ensure that the update requirements of different devices and versions are accurately met. By judging the conditions before the task is executed, devices that do not meet the update conditions are screened out in advance, reducing the number of invalid task executions, thereby improving the overall efficiency of the update process. Conditional judgment avoids the execution of erroneous tasks or premature tasks, prevents system anomalies caused by update errors or mismatches, and ensures the legitimacy and security of the update content through version verification. Recording the results of task condition judgment facilitates subsequent analysis of task success rate and failure reasons, and optimizes the distribution and execution strategies of subsequent tasks.

[0081] S6: If satisfied, update the APP to be updated based on the task effective time and the tracking template.

[0082] It should be noted that the task effective time refers to the time range in which the tracking update task is allowed to be executed, ensuring that the update task is performed at the appropriate time to avoid triggering the update too early or too late. Update means downloading the latest tracking template from the cloud to the APP to be updated and replacing its existing template to optimize and adjust the data collection function.

[0083] Specifically, after confirming that the APP to be updated meets the update conditions, you first need to check whether the current time is within the task effective time range. If the time meets the task requirements, the APP to be updated will start the update process. Before the update starts, the APP will request the latest tracking template from the cloud through an encrypted channel, and verify the integrity of the downloaded content (such as hash value verification) based on the unique version identifier of the template. After the verification passes, the APP will store the downloaded template in a local temporary area, and back up the existing template file for easy rollback.

[0084] Furthermore, after completing the download and verification of the template, the APP to be updated will stop the current tracking point collection task and replace the old template stored locally with the new template. After the new template is loaded into the APP framework, the APP will restart the tracking point collection function to ensure that the fields and event definitions of the new template are correctly applied. If the template fails to load or runs abnormally (such as field definition conflicts or template damage), the system will trigger the rollback mechanism and restore to the backed-up old template to ensure that the APP function is not affected. After the update is completed, the APP will report the update status to the cloud, including success or failure and detailed reasons (such as failure error codes).

[0085] Updates are made based on the time when the task takes effect, ensuring that the task is executed at the appropriate time, avoiding waste of resources or functional abnormalities caused by premature or late triggering. Encrypted transmission and integrity verification ensure that the downloaded tracking template has not been tampered with, and the backup and rollback mechanism prevents the update failure from causing irreversible effects on the APP. The loading of new templates can dynamically adjust the tracking field and event definition, quickly respond to changes in business needs, and thus improve the accuracy of data collection and application flexibility. The update process is completed silently in the background without user participation, avoiding bad experience caused by prompts or operation interruptions, and ensuring the imperceptibility of the update. After the update is completed, the status is reported to the cloud, which makes it easier for developers to understand the success rate and failure reasons of the update, thereby optimizing subsequent update strategies and improving system stability. By replacing and loading new templates, functional expansion can be achieved without re-releasing the APP, reducing development and operating costs while improving response speed.

[0086] This embodiment creates a point-of-sale template and uniquely identifies the version of the point-of-sale template; determines the point-of-sale update strategy according to the applicable scope of the point-of-sale template; generates a point-of-sale update task based on the point-of-sale update strategy, and the point-of-sale update task includes the task effective time and upgrade conditions; pushes the point-of-sale update task to the APP to be updated; after the APP to be updated receives the point-of-sale update task, it determines whether the APP to be updated meets the upgrade conditions based on the current version and unique version identification of the APP to be updated; if it meets the conditions, the APP to be updated is updated based on the task effective time and the point-of-sale template. This embodiment achieves the precision of point-of-sale management and version traceability by creating a point-of-sale template and introducing a unique version identification, ensuring the efficiency of the update; by formulating an update strategy according to the applicable scope and generating a point-of-sale update task including the task effective time and upgrade conditions, the pertinence and flexibility of the point-of-sale update are achieved; by pushing the update task to the APP to be updated and judging whether the upgrade conditions are met based on the current version and the unique version identification, redundant operations are avoided, and resource utilization efficiency is further improved; at the same time, through strict effective time management and condition matching, the security and reliability of the update operation are ensured, thereby effectively improving the efficiency, security and flexibility of the point-of-sale update of the vehicle control APP.

[0087] Based on the above first embodiment, a second embodiment of the method for updating the tracking points of the vehicle control APP of the present application is proposed. Figure 2 , Figure 2 This is a schematic diagram of a sub-process in the second embodiment of the vehicle control APP tracking update method of this application.

[0088] like Figure 2 As shown, in this embodiment, after step S6, the following steps are further included:

[0089] S6a: After the update is completed, the update result is obtained, and the update result includes the update status, update time, and version numbers before and after the update;

[0090] S6b: If the update status is update success, send an update success notification to the user terminal;

[0091] S6c: If the update status is update failure, roll back the APP to be updated to the version status before the update.

[0092] It should be noted that the update result refers to the feedback information generated after the update operation is completed, including the update status (success or failure), update time (the time point of task execution), and version numbers before and after the update (unique identifiers of the old and new versions). The update status refers to the execution result of the update task, which can be "update successful" or "update failed", and is used to guide subsequent operations. The user end refers to the user device interface associated with the APP to be updated, which is used to receive notifications of update results. Rollback means that when the update fails, the APP to be updated will be restored to the template and running state before the update to ensure the normal operation of the application.

[0093] Specifically, after the update is completed, the APP to be updated will obtain the update execution results through the self-check function. The update results include the following key contents: Update status: check whether the template download, verification, replacement and loading operations are successful; Update time: record the execution time of the update task; Version number before and after the update: record the version information of the old template and the new template through the version identifier for subsequent comparison and tracing. The update results will be stored locally and reported to the cloud management system through encrypted communication for developers to count and analyze.

[0094] Furthermore, if the update status is "update successful", the APP to be updated will send a notification to the user through the user end, such as "the tracking template has been successfully updated to the latest version (version number XXX)". The notification can be completed through message push, pop-up window in the APP or system notification. If the update status is "update failed", the APP to be updated will start the rollback mechanism, replace the current template with the old template backed up before the update, and reload it to ensure normal function. After the rollback is completed, the APP will report the reason for the failure (such as network error, verification failure, loading exception, etc.) to the cloud, and mark the task as "update failed" for developers to troubleshoot the problem.

[0095] By obtaining and recording the update results, including status, time, and version information, the execution of each update can be accurately tracked, providing a basis for subsequent analysis and optimization. After a successful update, a notification is sent to the user to let the user know the application status of the latest template in a timely manner, improving the user's transparency and trust. When the update fails, the rollback mechanism is used to quickly restore to the normal state before the update to avoid functional abnormalities or data collection interruptions caused by update failures. After the failure, the detailed reasons are reported to the cloud, which can help developers quickly locate the problem, improve the task completion rate, and optimize the update process. The results are obtained silently in the background and subsequent operations are processed to avoid unnecessary impacts on users due to failures or repeated notifications. After a successful update or rollback, the tracking templates are in an available state to ensure the accuracy and continuity of the data collection function.

[0096] Based on the first embodiment above, in this embodiment, before step S6, the following is further included:

[0097] S6A: If the APP to be updated does not meet the upgrade condition, identify the reason for not meeting the condition;

[0098] S6B: Generate feedback information based on the non-satisfaction reason, wherein the feedback information includes a preset solution strategy corresponding to the non-satisfaction reason;

[0099] S6C: Push the feedback information to the user terminal.

[0100] It should be noted that the non-satisfaction reason refers to the specific problem that causes the APP to be updated to fail to meet the upgrade conditions, such as version mismatch, task expiration, device unsupport, etc. Feedback information is a prompt information generated based on the non-satisfaction reason, including a description of the problem and the corresponding solution strategy, which is used to guide the user or the system to take subsequent actions. The preset solution strategy refers to a pre-set standardized solution designed for common non-satisfaction reasons, such as prompting users to upgrade the APP version, check the network connection, or contact technical support.

[0101] Specifically, when the APP to be updated is found to not meet the upgrade conditions, the specific reasons for the failure will be analyzed. Common reasons for non-satisfaction include: Version mismatch: The APP version is lower than the minimum version required by the update task or the template version is higher than the target version of the update task. The task has expired or has not taken effect: The current time exceeds the task effective time range. Device incompatibility: The device model or operating system version does not meet the requirements of the update policy. Network problem: The communication between the device and the cloud is abnormal, resulting in the inability to obtain the latest task. For the above reasons, the system will generate feedback information according to the preset rules, including: A specific description of the reason for non-satisfaction (such as "the current APP version is too low" or "the network connection failed"). The corresponding solution strategy (such as "please upgrade to the latest version and try again" or "please check the network connection and try again") The feedback information will be stored in the form of structured data and prepared to be sent to the user end.

[0102] Furthermore, the APP to be updated will send the generated feedback information to the user end through message push or pop-up window in the APP. Specific push methods include: Notification bar push: directly push feedback information to the notification bar of the user's device, such as "Update task failed: the current APP version is too low, please upgrade to the latest version." Pop-up window in the APP: When the user opens the APP, the feedback information is displayed through a pop-up window, providing clear solution guidance. Background log report: The feedback information is stored in the local log and uploaded to the cloud for developers to analyze and further optimize the solution strategy.

[0103] By identifying specific reasons for dissatisfaction, the system can generate targeted feedback information to help users or technical teams quickly understand the root cause of the problem. The feedback information contains preset solution strategies, which directly provide users with operational guidance, such as "Please check the network connection", reducing the time and difficulty of users to troubleshoot problems on their own. Uploading feedback information to the cloud can help developers analyze common failure reasons and optimize update strategies, gradually reducing the number of tasks that do not meet upgrade conditions. By pushing clear feedback information and solutions, users can reduce confusion and dissatisfaction caused by task failures, and enhance their trust and satisfaction with the APP. The system can collect and analyze feedback information, identify high-incidence scenarios for common problems, further adjust update strategies and solutions, and continuously optimize system performance.

[0104] This embodiment creates a point-of-sale template and uniquely identifies the version of the point-of-sale template; determines the point-of-sale update strategy according to the applicable scope of the point-of-sale template; generates a point-of-sale update task based on the point-of-sale update strategy, and the point-of-sale update task includes the task effective time and upgrade conditions; pushes the point-of-sale update task to the APP to be updated; after the APP to be updated receives the point-of-sale update task, it determines whether the APP to be updated meets the upgrade conditions based on the current version and unique version identification of the APP to be updated; if it meets the conditions, the APP to be updated is updated based on the task effective time and the point-of-sale template. This embodiment achieves the precision of point-of-sale management and version traceability by creating a point-of-sale template and introducing a unique version identification, ensuring the efficiency of the update; by formulating an update strategy according to the applicable scope and generating a point-of-sale update task including the task effective time and upgrade conditions, the pertinence and flexibility of the point-of-sale update are achieved; by pushing the update task to the APP to be updated and judging whether the upgrade conditions are met based on the current version and the unique version identification, redundant operations are avoided, and resource utilization efficiency is further improved; at the same time, through strict effective time management and condition matching, the security and reliability of the update operation are ensured, thereby effectively improving the efficiency, security and flexibility of the point-of-sale update of the vehicle control APP.

[0105] Based on the above second embodiment, a third embodiment of the vehicle control APP tracking update method of the present application is proposed. Figure 3 , Figure 3 This is a schematic diagram of a sub-process in the third embodiment of the vehicle control APP tracking update method of the present application.

[0106] In this embodiment, step S1 includes:

[0107] S11: Based on a preset definition strategy, define fields and attributes in the tracking template;

[0108] S12: classifying the defined embedding templates;

[0109] S13: Based on the classification result, the applicable scope of the embedding template is associated, and a unique version identification is performed on the embedding template.

[0110] It should be noted that the preset definition strategy refers to the tracking design rules that are pre-set according to the system function requirements or business scenarios, which are used to guide the definition of fields and attributes in the tracking template. For example, the strategy may include field name, data type, length limit, and trigger conditions of the field. Fields are the data content that needs to be collected in the tracking event, such as "button name" and "trigger time"; attributes are related characteristics of the field, such as the data type of the field (string, integer, etc.), length limit, and optionality. Tracking template classification is to divide the template into different categories according to the purpose or target scenario of the template, such as page tracking, user behavior tracking, performance tracking, etc., for subsequent management and application. The scope of application refers to the conditions or environment in which the tracking template can be applied, including the APP version range, device model, operating system version, etc.

[0111] Specifically, based on the preset definition strategy, the fields and attributes in the tracking point template are designed. The specific steps include: Determine the data fields that need to be collected according to business needs. For example: Page tracking point: fields include "page name", "loading time", etc.; user behavior tracking point: fields include "button name", "click time", etc. Set specific attributes for each field, including: data type: such as string, integer, Boolean; field length: limit data length to optimize storage; whether it is required: mark whether the field is required to be collected or optional. Ensure the standardization and uniformity of field definitions through the guidance of strategies.

[0112] Furthermore, after completing the definition of fields and attributes, classify the tracking templates according to function or purpose. For example, fields such as "page loading time" are classified as "performance tracking templates", while fields such as "button clicks" are classified as "behavior tracking templates". After the classification is completed, associate its scope of application based on the classification results of the template. For example: the performance tracking template is applicable to all devices and APP versions; the behavior tracking template may only be applicable to APP versions v2.0 and above. Finally, generate a unique version identifier for each template, and mark the template version with a timestamp, version number or UUID to ensure the uniqueness and traceability of the version.

[0113] By pre-setting definition strategies, we ensure the standardization of the definition of tracking points and attributes, reduce human errors, and improve the maintainability of templates. Template classification makes its management more intuitive and efficient, and the association of applicable scopes ensures that templates are applied in the correct scenarios to avoid the impact of wrong templates on data collection. The unique version identifier supports rapid version tracking and updating of templates, which helps developers clearly understand the iteration history of templates and improve management efficiency. The template management method based on classification and applicable scope can quickly respond to the needs of diverse business scenarios and support flexible expansion and dynamic adjustment. Through the precise association of applicable scopes, templates are only applied to required scenarios, avoiding unnecessary tracking data collection and improving the efficiency of system resource utilization.

[0114] Based on the above second embodiment, in this embodiment, step S6 includes:

[0115] S61: If the conditions are met, obtain a preset verification code, and perform integrity verification on the embedding template based on the preset verification code;

[0116] S62: If the tracking target passes the integrity verification, based on the structural requirements of the APP framework to be updated, perform compatibility verification on the tracking template;

[0117] S63: If the tracking template passes the compatibility verification, back up the current template of the APP to be updated;

[0118] S64: Replace the current template of the APP to be updated with the embedding template, and update the fields and attributes defined by the embedding template.

[0119] It should be noted that the preset check code is a hash value or encrypted signature used to verify the integrity of the tracking template. By comparing the actual hash value of the template with the preset check code, it is confirmed that the template has not been tampered with or damaged during transmission. Integrity verification is to ensure the integrity of the content of the tracking template, verify whether the template remains unchanged during transmission or storage, and there is no data loss or tampering. Compatibility verification refers to the structural verification of the received tracking template to ensure that its fields and attributes meet the technical requirements of the APP framework to be updated, to avoid template loading failure or exceptions. Field and attribute update refers to loading the fields and attributes defined in the tracking template into the APP, and dynamically adjusting them to match new data collection requirements.

[0120] Specifically, after the update conditions are met, the APP to be updated obtains the preset verification code (such as MD5 or SHA256) of the tracking template from the cloud, and performs hash calculation on the downloaded template file, and compares the calculation result with the preset verification code: If the verification code is consistent, it means that the template has not been tampered with or damaged, and proceeds to the next step of verification; if the verification code is inconsistent, the template integrity verification is determined to have failed, the update is terminated and the abnormality is reported to the cloud. After the integrity verification passes, the system will perform a compatibility check on the fields and attributes in the template according to the structural requirements of the APP framework to be updated: verify whether the field definition conforms to the type and length restrictions supported by the framework; check whether the new fields in the template conflict with the existing framework functions; ensure that the template will not affect the normal operation of the APP after loading. If the compatibility verification fails, the system will record the cause of the conflict and terminate the update process.

[0121] Furthermore, if the tracking template passes the compatibility verification, the system will back up the currently used template file to the local storage area to ensure that it can roll back to the backup state when the update fails to avoid interruption of the data collection function. After the backup is completed, the system replaces the current template with the newly downloaded tracking template, and dynamically adjusts the fields and attributes according to the definition in the new template: load the newly added fields and attributes in the new template; replace or update the existing field definition; delete the obsolete fields in the template. After the replacement is completed, the APP restarts the tracking collection function to ensure that the collection rules of the new template take effect.

[0122] Through integrity verification, we can ensure that the template has not been tampered with or damaged during transmission or storage, thereby improving the credibility and security of the updated data. Before updating, we can perform compatibility verification required by the framework structure to avoid abnormal collection functions caused by incompatible templates and improve the stability of the system. Back up the existing template before replacing the template to provide a guarantee for rollback when the update fails and avoid system function interruption caused by update errors. The update of the template fields and attributes supports dynamic adjustment of collection rules, quickly responds to changes in business needs, and realizes the expansion and optimization of the tracking point function. After replacing the template, the new collection rules are immediately enabled to ensure the accuracy and timeliness of data collection. At the same time, comprehensive verification is used to reduce interference with user use and improve user experience. Recording the detailed process of integrity verification, compatibility verification, and template replacement will help with problem troubleshooting and template version management, and further improve the maintainability of the system.

[0123] Based on the above second embodiment, in this embodiment, step S2 includes:

[0124] S21: converting the applicable scope of the tracking template into an update condition, wherein the update condition includes a version matching rule, a device matching rule, an operating system rule, and a target user rule;

[0125] S22: Using logical operations to combine the version matching rule, the device matching rule, the operating system rule, and the target user rule, and combining a preset upgrade method and a preset time strategy to obtain the tracking update strategy.

[0126] It should be noted that the scope of application of the tracking template refers to the application conditions of the tracking template, including information such as the supported APP version, device model, operating system version and target user group, which is used to limit the validity of the template. Logical operations are used to combine multiple update conditions (such as AND / OR / NOT) to form more complex judgment logic to adapt to diverse scenario requirements. The preset upgrade method refers to the execution method of the template update, such as silent update or forced update. The preset time policy refers to the time control rules of the template update task, such as the task effective time and expiration time. The tracking update strategy is an operation plan generated based on the update conditions, logical operations, upgrade methods and time policies, which is used to guide the execution of the template update task.

[0127] Specifically, set matching conditions according to the supported version range of the tracking template; define rules according to the device models to which the template applies; set rules for the operating system versions supported by the template; and set rules according to the user characteristics to which the template applies.

[0128] Furthermore, logical operations are used to combine multiple update conditions. For example, if the update condition is "APP version matches and the device model is 'DF-100' or 'DF-200' and the operating system is Android 10 and above", the combination rule is: (APP version>=1.0AND APP version<=2.0)AND(Device model IN('DF-100','DF-200'))AND(Operating system version>=Android 10). Combine the upgrade method and time strategy: Add preset upgrade methods and time strategies based on the condition combination rules: Preset upgrade methods: such as silent update or forced update; preset time strategy: such as the task effective time is 2024-12-01 00:00:00 to 2024-12-15 23:59:59. The final policy rule is: ((APP version>=1.0ANDAPP version<=2.0)AND(device model IN('DF-100','DF-200'))AND(operating system version>=Android10))WITH silent update AND effective time BETWEEN 2024-12-01AND2024-12-15. The generated tracking update policy will be stored in the cloud task management system for use in template update tasks. The policy is bound to the template to ensure the accuracy of the update operation.

[0129] Convert the template application scope into update conditions and combine them through logical operations to adapt to complex business scenarios and ensure the accuracy of the update strategy. Through the comprehensive application of version, device, operating system and user rules, update tasks only act on target devices and users that meet the conditions, avoiding unnecessary waste of resources. Combined with the preset upgrade method and time strategy, ensure that the task is executed in the correct way within the appropriate time range, improve the stability and update efficiency of the system. The combination of logical operations supports flexible adjustment of rules, which can quickly adapt to different business needs and improve the scalability and responsiveness of the system. Through rule-based policy generation, developers can quickly define and deploy update tasks, reduce the complexity of manual intervention, and optimize management efficiency.

[0130] This embodiment creates a point-of-sale template and uniquely identifies the version of the point-of-sale template; determines the point-of-sale update strategy according to the applicable scope of the point-of-sale template; generates a point-of-sale update task based on the point-of-sale update strategy, and the point-of-sale update task includes the task effective time and upgrade conditions; pushes the point-of-sale update task to the APP to be updated; after the APP to be updated receives the point-of-sale update task, it determines whether the APP to be updated meets the upgrade conditions based on the current version and unique version identification of the APP to be updated; if it meets the conditions, the APP to be updated is updated based on the task effective time and the point-of-sale template. This embodiment achieves the precision of point-of-sale management and version traceability by creating a point-of-sale template and introducing a unique version identification, ensuring the efficiency of the update; by formulating an update strategy according to the applicable scope and generating a point-of-sale update task including the task effective time and upgrade conditions, the pertinence and flexibility of the point-of-sale update are achieved; by pushing the update task to the APP to be updated and judging whether the upgrade conditions are met based on the current version and the unique version identification, redundant operations are avoided, and resource utilization efficiency is further improved; at the same time, through strict effective time management and condition matching, the security and reliability of the update operation are ensured, thereby effectively improving the efficiency, security and flexibility of the point-of-sale update of the vehicle control APP.

[0131] The present application also provides a vehicle control APP tracking update device, please refer to Figure 4 , Figure 4 This is a schematic diagram of the module structure of the vehicle control APP tracking update device according to an embodiment of the present application, and the vehicle control APP tracking update device includes:

[0132] The template creation module 401 is used to create a tracking template and uniquely identify the version of the tracking template;

[0133] An update strategy module 402 is used to determine a tracking point update strategy according to the applicable scope of the tracking point template;

[0134] A task generation module 403 is used to generate a tracking point update task based on the tracking point update strategy, wherein the tracking point update task includes a task effective time and an upgrade condition;

[0135] The push module 404 is used to push the tracking update task to the APP to be updated;

[0136] The condition judgment module 405 is used to judge whether the APP to be updated meets the upgrade condition based on the current version of the APP to be updated and the unique version identifier after the APP to be updated receives the tracking update task;

[0137] The target module 406 is used to update the APP to be updated based on the task effective time and the tracking template if the conditions are met.

[0138] The vehicle control APP tracking update device provided in the embodiment of the present application adopts the vehicle control APP tracking update method in the above embodiment, which can solve the technical problem of how to improve the efficiency and safety of the vehicle control APP tracking update. Compared with the prior art, the beneficial effects of the vehicle control APP tracking update device provided in the embodiment of the present application are the same as the beneficial effects of the vehicle control APP tracking update method provided in the above embodiment, and the other technical features in the vehicle control APP tracking update device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0139] The present application provides a vehicle control APP tracking update device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle control APP tracking update method in the above-mentioned embodiment.

[0140] Reference below Figure 5 , Figure 5 The schematic diagram of the device structure of the hardware operating environment involved in the method for updating the vehicle control APP in the embodiment of the present application shows a schematic diagram of the structure of the vehicle control APP updating device suitable for implementing the embodiment of the present application. The vehicle control APP updating device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5The vehicle control APP tracking update device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0141] like Figure 5 As shown, the vehicle control APP buried point update device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 to the random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle control APP buried point update device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other via a bus 1005. The input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the vehicle control APP buried point update device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a vehicle control APP buried point update device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or provided alternatively.

[0142] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0143] The vehicle control APP tracking update device provided by this application adopts the vehicle control APP tracking update method in the above embodiment, which can solve the technical problem of how to improve the efficiency and safety of the vehicle control APP tracking update. Compared with the prior art, the beneficial effects of the vehicle control APP tracking update device provided by this application are the same as the beneficial effects of the vehicle control APP tracking update method provided by the above embodiment, and the other technical features in the vehicle control APP tracking update device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0144] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0145] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0146] The present application provides a computer-readable storage medium having computer-readable program instructions (i.e., computer programs) stored thereon, and the computer-readable program instructions are used to execute the vehicle control APP tracking update method in the above-mentioned embodiment.

[0147] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0148] The above-mentioned computer-readable storage medium may be included in the vehicle control APP embedding update device; or it may exist independently without being installed in the vehicle control APP embedding update device.

[0149] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the vehicle control APP tracking update device, the vehicle control APP tracking update device: creates a tracking template and uniquely identifies the version of the tracking template; determines the tracking update strategy according to the applicable scope of the tracking template; generates a tracking update task based on the tracking update strategy, and the tracking update task includes the task effective time and upgrade conditions; pushes the tracking update task to the APP to be updated; after the APP to be updated receives the tracking update task, it determines whether the APP to be updated meets the upgrade conditions based on the current version and unique version identification of the APP to be updated; if it meets the conditions, the APP to be updated is updated based on the task effective time and the tracking template. The computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, and the above-mentioned programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, C++, and also conventional procedural programming languages—such as "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0150] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0151] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0152] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle control APP tracking update method, and can solve the technical problem of how to improve the efficiency and safety of vehicle control APP tracking update. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the vehicle control APP tracking update method provided in the above-mentioned embodiment, and will not be repeated here.

[0153] An embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the above-mentioned vehicle control APP tracking update method.

[0154] The computer program product provided by this application can solve the technical problem of how to improve the efficiency and security of the vehicle control APP tracking update. Compared with the prior art, the beneficial effects of the computer program product provided by the embodiment of this application are the same as the beneficial effects of the vehicle control APP tracking update method provided by the above embodiment, which will not be repeated here.

[0155] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent processing scope of the present application.

Claims

1. A method for updating a vehicle control APP, characterized in that: The method comprises: Create a tracking template and uniquely identify the version of the tracking template; Determine a tracking point update strategy according to the applicable scope of the tracking point template; Based on the tracking point update strategy, generate a tracking point update task, wherein the tracking point update task includes a task effective time and an upgrade condition; Push the tracking update task to the APP to be updated; After the APP to be updated receives the tracking update task, based on the current version of the APP to be updated and the unique version identifier, it is determined whether the APP to be updated meets the upgrade condition; If satisfied, the APP to be updated is updated based on the task effective time and the tracking template.

2. The method according to claim 1, characterized in that After the step of updating the APP to be updated based on the task effective time and the tracking template if the conditions are met, the method further includes: After the update is completed, the update result is obtained, which includes the update status, update time, and version numbers before and after the update; If the update status is successful, sending a successful update notification to the user terminal; If the update status is update failure, the APP to be updated is rolled back to the version status before the update.

3. The method according to claim 2, characterized in that Before the step of updating the APP to be updated based on the task effective time and the tracking template if the condition is satisfied, the method further includes: If the APP to be updated does not meet the upgrade conditions, identify the reason for not meeting the conditions; Based on the reasons for non-satisfaction, feedback information is generated, wherein the feedback information includes a preset solution strategy corresponding to the reasons for non-satisfaction; The feedback information is pushed to the user terminal.

4. The method according to claim 1, characterized in that The step of creating a tracking template and uniquely identifying the version of the tracking template includes: Based on the preset definition strategy, define the fields and attributes in the tracking template; Classify the defined embedding templates; Based on the classification result, the applicable scope of the embedding template is associated, and a unique version identification is performed on the embedding template.

5. The method according to claim 4, characterized in that If the conditions are met, the step of updating the APP to be updated based on the task effective time and the tracking template includes: If satisfied, obtain a preset verification code, and perform integrity verification on the embedding template based on the preset verification code; If the tracking target passes the integrity verification, based on the structural requirements of the APP framework to be updated, the compatibility of the tracking template is verified; If the tracking template passes the compatibility verification, back up the current template of the APP to be updated; Replace the current template of the APP to be updated with the embedding template, and update the fields and attributes defined by the embedding template.

6. The method according to claim 1, characterized in that The step of determining the tracking point update strategy according to the applicable scope of the tracking point template includes: Convert the applicable scope of the tracking template into update conditions, where the update conditions include version matching rules, device matching rules, operating system rules, and target user rules; The version matching rule, the device matching rule, the operating system rule and the target user rule are combined by logical operation, and the preset upgrade method and the preset time strategy are combined to obtain the tracking point update strategy.

7. A vehicle control APP tracking update device, characterized in that: The device comprises: A template creation module is used to create a tracking template and uniquely identify the version of the tracking template; An update strategy module, used to determine a tracking point update strategy according to the applicable scope of the tracking point template; A task generation module, used to generate a tracking point update task based on the tracking point update strategy, wherein the tracking point update task includes a task effective time and an upgrade condition; A push module is used to push the tracking update task to the APP to be updated; A condition judgment module, configured to judge whether the APP to be updated meets the upgrade condition based on the current version of the APP to be updated and the unique version identifier after the APP to be updated receives the tracking update task; The target module is used to update the APP to be updated based on the task effectiveness time and the tracking template if the conditions are met.

8. A computer device, characterized in that: The device includes: a memory, a processor, and a vehicle control APP tracking update program stored in the memory and executable on the processor, wherein the vehicle control APP tracking update program is configured to implement the steps of the vehicle control APP tracking update method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium stores a vehicle control APP tracking update program, and when the vehicle control APP tracking update program is executed by the processor, the steps of the vehicle control APP tracking update method as described in any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the vehicle control APP tracking update method as described in any one of claims 1 to 6 are implemented.

Images