OTA task management method, system, device and storage medium based on behavior analysis

Abstract

Disclosed in the present invention are an OTA task management method, system, device and readable storage medium based on behavior analysis. The OTA task management method based on behavior analysis comprises the following steps: defining upgrade behaviors of a user, and constructing a user behavior library; on the basis of the user behavior library, creating and training a behavior analysis model; inputting a pre-released task into the behavior analysis model, so as to obtain a behavior analysis result; and on the basis of the pre-released task and the behavior analysis result, making an OTA upgrade package, and releasing an OTA upgrade task. By means of defining upgrade behaviors of a user and constructing a user behavior library, a behavior analysis model is created, such that a user behavior can be analyzed to obtain an OTA task requirement; and on the basis of the OTA task requirement, an OTA upgrade package is made, and then an OTA upgrade task is released, such that the upgrade willingness of users can be satisfied, the upgrade rate of the users is improved, and the whole process is automatically completed by a system, thereby improving the efficiency of OTA task releasing.

Description

OTA task management method, system and device based on behavior analysis and storage medium TECHNICAL FIELD

[0001] The present application relates to an OTA upgrade method, in particular to an OTA task management method, system and device based on behavior analysis and a storage medium. BACKGROUND

[0002] Over-the-Air Technology (OTA) is a technology for remotely managing mobile terminal devices and SIM card data through the air interface of mobile communication. OTA technology is also applied in the automotive industry to implement mass upgrades of vehicles.

[0003] In the process of planning OTA activities by vehicle manufacturers, there is a common phenomenon of excessive reliance on market expectations to guide the design and development of OTA. Although this approach can reflect the overall trend of the industry to some extent, it ignores the core needs of users as the ultimate recipients. When planning OTA, vehicle manufacturers often rely on market analysts' forecasts, competitors' dynamics or industry standard processes to quickly enter the development stage. However, these tests are often limited to pre-set scenarios and conditions, lacking the diversity and complexity of real user environments. More critically, due to the lack of in-depth research on user needs, vehicle manufacturers often struggle to accurately grasp users' real expectations and pain points. After the release of OTA tasks, there is a deviation between the upgrade content and user expectations, making it difficult for users to feel the value of the upgrade, resulting in low user willingness to upgrade, and even resistance, and low upgrade rates. Moreover, existing planning and management of OTA tasks are often based on statistics of the OTA upgrade process, lacking a definition of user upgrade behavior, and unable to accurately obtain users' upgrade willingness.

[0004] Therefore, there is an urgent need for an OTA task management method that can meet user needs, analyze user upgrade behavior, and release OTA upgrade tasks based on the analysis results to improve upgrade rates and reduce waste of development resources. SUMMARY

[0005] In view of the problem that current OTA task release cannot meet user expectations, resulting in low upgrade rates, the present application provides an OTA task management method based on behavior analysis, which builds a user behavior library, creates a behavior analysis model to analyze user upgrade behavior, and releases OTA upgrade tasks based on the analysis results to improve upgrade rates.

[0006] To achieve the above-mentioned purposes, the embodiments of the present application adopt the following technical solutions:

[0007] An OTA task management method based on behavior analysis, comprising:

[0008] define user upgrade behavior, build user behavior library;

[0009] create and train behavior analysis model according to user behavior library;

[0010] input pre-release task into the behavior analysis model to obtain behavior analysis result;

[0011] produce OTA upgrade package and release OTA upgrade task according to pre-release task and behavior analysis result.

[0012] According to one aspect of the present application, the definition of user upgrade behavior includes:

[0013] obtain user upgrade behavior;

[0014] define user upgrade behavior classification rule;

[0015] define user upgrade behavior under each classification rule according to user upgrade behavior classification rule.

[0016] According to one aspect of the present application, the user upgrade behavior classification rule includes at least: classification by historical upgrade period, classification by upgrade domain control, classification by upgrade attribute, classification by upgrade mode, classification by upgrade area, and infrequent upgrade.

[0017] According to one aspect of the present application, the creation and training of behavior analysis model according to user behavior library includes:

[0018] create single behavior analysis model for OTA upgrade task containing only single user upgrade behavior;

[0019] exhaustively enumerate possible OTA upgrade tasks containing multiple types of user upgrade behavior, and create multi-behavior analysis model based on the upgrade task;

[0020] obtain historical OTA upgrade task, and train the single behavior analysis model and multi-behavior analysis model.

[0021] According to one aspect of the present application, the creation and training of behavior analysis model further includes: judging whether multiple upgrade behaviors contained in the OTA upgrade task are compatible, and eliminating OTA upgrade tasks between incompatible upgrade behaviors.

[0022] According to one aspect of the present application, the obtaining of historical OTA upgrade task includes:

[0023] obtain historical OTA upgrade task and corresponding OTA upgrade package, analyze upgrade behavior and vehicle VIN code contained in the OTA upgrade package.

[0024] According to an aspect of the present application, the inputting the pre-release task into the behavior analysis model comprises:

[0025] Obtaining the pre-release task, and analyzing the user upgrade behavior possibly contained in the pre-release task;

[0026] If the pre-release task contains only a single user upgrade behavior, inputting the single-behavior analysis model to obtain an analysis result;

[0027] If the pre-release task contains multiple user upgrade behaviors, inputting the multi-behavior analysis model to obtain an analysis result.

[0028] According to an aspect of the present application, the OTA task management method based on user upgrade behavior analysis further comprises: generating an OTA task demand according to the pre-release task and the behavior analysis result, developing and verifying an OTA upgrade package, and automatically generating a formal OTA release task after completion.

[0029] According to an aspect of the present application, the OTA task management method based on user upgrade behavior analysis further comprises: automatically generating a vehicle portrait according to a completed historical OTA upgrade task.

[0030] According to an aspect of the present application, the vehicle portrait according to the completed historical OTA upgrade task comprises:

[0031] Obtaining the completed historical OTA upgrade task and the vehicle VIN code contained therein;

[0032] Analyzing the user upgrade behavior contained in the historical OTA upgrade task;

[0033] Selecting the vehicle VIN code, and performing the vehicle portrait according to the user upgrade behavior.

[0034] An OTA task management system based on behavior analysis, comprising:

[0035] A user behavior library, configured to define user upgrade behaviors and classify the user upgrade behaviors into defined user upgrade behaviors;

[0036] A behavior analysis model, created according to the user behavior library, configured to analyze the user upgrade behavior of an input pre-release task to obtain a behavior analysis result;

[0037] A training module, configured to train the behavior analysis model, and add the user upgrade behavior contained in the reported OTA upgrade data into the user behavior library to continuously train and correct the behavior analysis model;

[0038] The task publishing module is configured to generate an OTA task demand according to the pre-release task and the behavior analysis result, develop and verify an OTA upgrade package, automatically generate an OTA upgrade task after completion, and report OTA upgrade data after completion of the OTA upgrade task.

[0039] The vehicle profiling module is configured to perform vehicle profiling according to the completed historical OTA upgrade task, analyze the vehicle profiling, and generate an OTA upgrade task demand, develop and verify an OTA upgrade package, and automatically generate a formal OTA release task after completion.

[0040] An OTA task management device based on behavior analysis, comprising:

[0041] A memory configured to store a computer program;

[0042] A processor configured to execute the computer program to implement the steps of the OTA task management method based on behavior analysis.

[0043] An OTA task management storage medium based on behavior analysis, the storage medium storing a computer program, the computer program being executed to implement the steps of the OTA task management method based on behavior analysis.

[0044] The OTA task management method based on behavior analysis comprises the following steps: defining user upgrade behavior, constructing a user behavior library, creating and training a behavior analysis model according to the user behavior library, inputting a pre-release task into the behavior analysis model to obtain a behavior analysis result, and producing an OTA upgrade package and releasing an OTA upgrade task according to the pre-release task and the behavior analysis result. By defining user upgrade behavior and constructing a user behavior library to create a behavior analysis model, the user upgrade behavior can be analyzed to obtain an OTA task demand, the OTA upgrade package can be produced and the OTA upgrade task can be released according to the OTA task demand, the user upgrade willingness can be met, the user upgrade rate can be improved, the whole process system is automatically completed, and the efficiency of OTA task release is improved.

[0045] BRIEF DESCRIPTION OF DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0047] Fig. 1 is a flow chart of the OTA task management method based on behavior analysis according to the embodiment of the present application;

[0048] Fig. 2 is a flow chart of the OTA task management method based on behavior analysis according to an embodiment of the present application;

[0049] Fig. 3 is a structure block diagram of the OTA task management system based on behavior analysis according to an embodiment of the present application;

[0050] Fig. 4 is a schematic diagram of the OTA task management device based on behavior analysis according to an embodiment of the present application. DETAILED DESCRIPTION

[0051] The technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings of the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of the present application.

[0052] In the embodiments of the present application, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, device, product or equipment comprising a series of steps or modules does not have to be limited to the clearly listed steps or modules, but can include other steps or modules that are not clearly listed or inherent to the process, method, product or equipment.

[0053] In the embodiments of the present application, the naming or numbering of the steps does not mean that the steps in the method flow must be performed in the time / logical order indicated by the naming or numbering. The named or numbered flow steps can change the execution order according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved.

[0054] In this document, the term "embodiment" means that the specific features, structures or characteristics described in connection with the embodiment can be included in at least one embodiment of the present application. The phrase appears at various places in the specification does not necessarily all refer to the same embodiment, nor is it necessarily independent or alternative to other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0055] Embodiment one

[0056] As shown in Fig. 1, a method for OTA task management based on behavior analysis includes the following steps:

[0057] Step S1: defining user upgrade behavior, constructing a user behavior library of user upgrade behavior;

[0058] Step S11: obtaining user upgrade behavior;

[0059] Obtain raw user upgrade data containing user upgrade behavior. User upgrade data can be obtained through upgrade logs, manufacturer information, user feedback, etc., and user behavior can be analyzed based on the raw user upgrade data.

[0060] For example, when an OTA task is issued to upgrade a device, the relevant information about the upgrade will be recorded in the logs. These logs are usually uploaded to the manufacturer. User upgrade logs can be obtained as user upgrade data. This part of the data contains user upgrade behavior, but without defining user upgrade behavior and without analyzing the relevant data, it is impossible to obtain the specific user upgrade behavior.

[0061] Manufacturer information is generally user upgrade data obtained by the manufacturer within a certain period of time after the manufacturer releases the upgrade package. This part of the data may have been preliminarily processed by the manufacturer, or it may be raw data that does not contain specific user behavior.

[0062] User feedback can be collected through surveys issued by car manufacturers, and the results of these surveys can directly reveal user upgrade behaviors.

[0063] Step S12: Define user upgrade behavior classification rules;

[0064] Based on different behavioral habits during the OTA upgrade process, user upgrade behavior classification rules can be defined, including classification by upgrade time period, upgrade domain controller, upgrade attribute, upgrade method, upgrade region, and infrequent upgrades.

[0065] Step S13: Define the user upgrade behavior under each classification rule according to the user upgrade behavior classification rules.

[0066] In this embodiment, user upgrade behaviors of different categories are independent of each other and do not affect each other. The user upgrade behavior categories are defined as follows:

[0067] Classified by upgrade time period: Daytime upgrade, Nighttime upgrade;

[0068] Classified by upgrade domain control: chassis domain upgrade, body domain upgrade, power domain upgrade, entertainment domain upgrade, and driver assistance domain upgrade;

[0069] Upgrades can be categorized by their attributes: Bug-related upgrades, consumer-related upgrades, and after-sales upgrades.

[0070] Classified by upgrade method: mobile device planning upgrade, regular vehicle SDK upgrade, and post-diagnosis vehicle SDK upgrade.

[0071] The mobile device planning upgrade includes immediate upgrade of the mobile device, scheduled upgrade of the mobile device, and the like, and the mobile device includes, but is not limited to, a mobile phone, a notebook computer, a tablet computer, and the like; the conventional vehicle-side SDK upgrade includes immediate upgrade of the conventional vehicle-side SDK, scheduled upgrade of the conventional vehicle-side SDK, and the like.

[0072] It should be noted that the upgrade according to the upgrade time period is not classified according to the specific upgrade time, and is actually determined according to the attribute of the OTA upgrade package produced, for example, when an upgrade package needs to take a long upgrade time, the upgrade package will be defined as more suitable for night upgrade, and therefore, the classification according to the upgrade time period can be regarded as a strategy classification of the upgrade.

[0073] Infrequent upgrade means that the user upgrade frequency of the vehicle is low, and the threshold can be set, when the number of infrequent upgrades of a vehicle corresponding to a VIN number reaches the set threshold, the vehicle can be regarded as infrequently upgraded.

[0074] Step S14: constructing a user behavior library;

[0075] The user behavior library is a user initial behavior library, which is used to store the obtained original user data, analyzes the obtained original user data, classifies the original user upgrade data according to the user upgrade behavior classification rule to obtain the user upgrade behavior, and stores the classified user upgrade behavior in the user initial behavior library.

[0076] In actual application, the sorting and filtering conditions can be set according to different user upgrade behavior classification rules to manage the user upgrade behavior in the user behavior library.

[0077] In addition, the completed OTA upgrade task each time is obtained, the vehicle completing the OTA upgrade task is analyzed, the analysis result is associated with the vehicle VIN code and stored in the user initial behavior library, and new behavior is realized into the library.

[0078] After the new behavior is stored in the library, the user initial behavior library becomes a complete user behavior library, and the user upgrade behavior can be queried according to the vehicle VIN code.

[0079] Step S2: creating and training a behavior analysis model according to the user behavior library;

[0080] Step S21: creating a single behavior analysis model for an OTA upgrade task containing only a single user upgrade behavior;

[0081] For example, a single behavior analysis model of time period classification is created, the related information directly obtained and containing the user upgrade behavior is taken as the input of the analysis model, the single behavior analysis result is taken as the output of the model, the user upgrade behavior and the upgrade history time period to which the behavior belongs are obtained by analyzing the upgrade log.

[0082] Similarly, a separate single-behavior analysis model is created for upgrading the domain controller, upgrading the attribute, and whether to diagnose and upgrade afterwards.

[0083] In addition, the training of the behavior analysis model can also use the upgrade results contained in the newly completed OTA upgrade task. Step S22: Enumerate all possible OTA upgrade tasks containing multiple types of user upgrade behaviors, and create a multi-behavior analysis model based on the upgrade task;

[0084] Enumerate all possible OTA upgrade tasks containing multiple types of user upgrade behaviors.

[0085] Based on the OTA upgrade task containing multiple types of user upgrade behaviors, a multi-behavior analysis model is created, and the original user upgrade data is analyzed according to the defined user upgrade behavior classification rules to determine the possible user upgrade behaviors and determine the specific user upgrade behavior in the user upgrade behavior classification; for example, analyzing a certain original user upgrade data, it is found that the user upgrade data contains user upgrade behaviors such as night upgrade, chassis domain upgrade, and regular vehicle end SDK upgrade.

[0086] In addition, all user upgrade behaviors of a user in a certain time period can also be found according to the vehicle VIN code, and the user upgrade behaviors are analyzed to obtain the user upgrade preference; for example, from February 2024 to June 2024, the user has performed 5 times of auxiliary driving domain upgrade and 10 times of vehicle body domain upgrade, thereby obtaining the user's upgrade preference for auxiliary driving domain upgrade and vehicle body domain upgrade.

[0087] Step S23: Obtain historical OTA upgrade tasks, and train the single-behavior analysis model and the multi-behavior analysis model;

[0088] Obtain historical OTA upgrade tasks and corresponding OTA upgrade packages, and analyze the upgrade behaviors contained in the OTA upgrade packages.

[0089] According to the OTA upgrade task, obtain the original user upgrade data of the OTA upgrade task, and use the original user data as the input of the single-behavior analysis model and the multi-behavior analysis model, that is, the training set.

[0090] Correlate the upgrade behaviors contained in the OTA upgrade task with the original user upgrade data to obtain the actual user upgrade results and the user upgrade behaviors contained in the actual user upgrade results, and use the actual user upgrade results as the verification set.

[0091] Use the training set to train the single-behavior analysis model and the multi-behavior analysis model, and use the verification set to verify the output results of the model. Step S24: Determine whether the multiple upgrade behaviors contained in the OTA upgrade task are compatible, and eliminate the OTA upgrade tasks with incompatible upgrade behaviors.

[0092] In practical applications, there may be conflicts between user upgrade behaviors of different classification rules, such as incompatibility between consumer upgrades and post-diagnosis upgrades. Incompatible behaviors are excluded from the multi-behavior analysis model.

[0093] Step S3: inputting the pre-release task into the behavior analysis model to obtain a behavior analysis result;

[0094] Step S31: obtaining a pre-release task and analyzing user upgrade behaviors that the pre-release task may contain;

[0095] The pre-release task is obtained and analyzed to obtain all single user upgrade behaviors that it may contain, and it is determined whether there are multiple user upgrade behaviors containing multiple single user behaviors.

[0096] Step S32: if the pre-release task contains only a single user upgrade behavior, input the single behavior analysis model to obtain an analysis result;

[0097] If the pre-release task contains only a single user upgrade behavior, the pre-release task is input into the single behavior analysis model to obtain user upgrade preferences in each user upgrade behavior classification rule.

[0098] Step S33: if the pre-release task contains multiple user upgrade behaviors, input the multi-behavior analysis model to obtain an analysis result.

[0099] If the pre-release task contains multiple user upgrade behaviors, the pre-release task is input into the multi-behavior analysis model to obtain user upgrade preferences of multiple user upgrade behaviors containing multiple single user upgrade behaviors, for example, the pre-release task related content, the user is accustomed to upgrading at night, and the task belongs to Bug class upgrade, and the upgrade tends to upgrade the vehicle body domain and the auxiliary driving domain.

[0100] Step S4: according to the pre-release task and the behavior analysis result, an OTA upgrade package is made and an OTA upgrade task is released;

[0101] According to the pre-release task and the behavior analysis result, an OTA task requirement is generated, an OTA upgrade package is developed and verified, and an OTA upgrade task is officially released according to the behavior analysis result.

[0102] In addition, after the OTA upgrade task is officially released for a period of time, user upgrade data associated with the OTA upgrade task is obtained, which is used as a training set, and user upgrade results containing user upgrade behaviors are used as a verification set, and the single behavior analysis model and the multi-behavior analysis model are trained and corrected.

[0103] The embodiment provides an OTA task management method based on behavior analysis, including the following steps: defining user upgrade behavior, constructing a user behavior library; creating and training a behavior analysis model according to the user behavior library; inputting a pre-release task into the behavior analysis model to obtain a behavior analysis result; and producing an OTA upgrade package and releasing an OTA upgrade task according to the pre-release task and the behavior analysis result. By defining user upgrade behavior and constructing a user behavior library to create a behavior analysis model, the user upgrade behavior can be analyzed to obtain an OTA task requirement, the OTA upgrade package can be produced and the OTA upgrade task can be released according to the OTA task requirement, the user upgrade willingness can be met, the user upgrade rate can be improved, the whole-process system automation is completed, and the efficiency of the OTA task release is improved.

[0104] Embodiment two

[0105] As shown in FIG. 1, an OTA task management method based on behavior analysis includes the following steps:

[0106] Step S1: defining user upgrade behavior, constructing a user behavior library;

[0107] Step S11: obtaining user upgrade behavior;

[0108] The original user upgrade data containing user upgrade behavior is obtained, and the user upgrade data can be obtained through upgrade logs, manufacturer information, user feedback and the like, and the behavior of the user is analyzed according to the original user upgrade data.

[0109] For example, the OTA task release device is upgraded, and the related information of the upgrade is recorded through a log, and the log is generally uploaded to the manufacturer. The user upgrade data can be obtained by obtaining the user upgrade log, and this part of data contains user upgrade behavior. However, when the user upgrade behavior is not defined and the related data is not analyzed, the specific user upgrade behavior cannot be obtained.

[0110] The manufacturer information is generally user upgrade data obtained within a certain time after the manufacturer releases an upgrade package. This part of data may be preliminarily processed by the manufacturer, or may be original data not containing specific user behavior.

[0111] The user feedback information can be counted through the questionnaire released by the vehicle manufacturer, and the user upgrade behavior contained in the questionnaire is directly obtained through the result of the questionnaire.

[0112] Step S12: defining user upgrade behavior classification rules;

[0113] According to different behavior habits in the OTA upgrade process, the user upgrade behavior classification rules can include classification according to upgrade time period, classification according to upgrade domain control, classification according to upgrade attribute, classification according to upgrade mode, classification according to upgrade region, and infrequent upgrade.

[0114] Step S13: According to the user upgrade behavior classification rule, the user behavior under each classification rule is defined.

[0115] In this embodiment, the different classifications of user upgrade behaviors are independent of each other and do not affect each other. The user upgrade behavior classification is defined as follows:

[0116] Classification by upgrade time period: daytime upgrade, nighttime upgrade;

[0117] Classification by upgrade domain control: chassis domain upgrade, vehicle body domain upgrade, power domain upgrade, entertainment domain upgrade, and auxiliary driving domain upgrade;

[0118] Classification by upgrade attribute: Bug class upgrade, consumer class upgrade, and after-sales class upgrade;

[0119] Classification by upgrade method: mobile device planning upgrade, regular vehicle end SDK upgrade, and diagnosis vehicle end SDK upgrade.

[0120] The mobile device planning upgrade includes mobile device immediate upgrade and mobile device scheduled upgrade, and the mobile device includes but is not limited to mobile phones, notebook computers, tablet computers, and the like. The regular vehicle end SDK upgrade includes regular vehicle end SDK immediate upgrade and regular vehicle end SDK scheduled upgrade.

[0121] It should be noted that the upgrade by upgrade time period is not classified according to the specific upgrade time. Instead, it is determined according to the attribute of the OTA upgrade package produced. For example, when an upgrade package needs to take a long upgrade time, the upgrade package will be defined as more suitable for nighttime upgrade. Therefore, the classification by upgrade time period can be regarded as a strategy classification of upgrade.

[0122] Infrequent upgrade means that the user upgrade frequency of the vehicle is low. The threshold can be set. When the number of infrequent upgrades of a vehicle corresponding to a VIN number reaches the set threshold, the vehicle can be regarded as infrequently upgraded.

[0123] Step S14: Construct a user behavior library.

[0124] The user behavior library is a user initial behavior library for storing the obtained original user data. The original user data is analyzed, the original user upgrade data is classified according to the user upgrade behavior classification rule to obtain the user upgrade behavior, and the classified user upgrade behavior is stored in the user initial behavior library.

[0125] In actual application, the sorting and filtering conditions can be set according to different user upgrade behavior classification rules to manage the user upgrade behavior in the user behavior library.

[0126] In addition, the OTA upgrade task completed each time is acquired, the vehicle completing the OTA upgrade task is analyzed, the analysis result is stored in the user initial behavior library after being associated with the vehicle VIN code, and new behaviors are realized into the library.

[0127] After the new behaviors are stored into the library, the user initial behavior library becomes a complete user behavior library, and user upgrade behavior query can be performed according to the vehicle VIN code.

[0128] Step S2: According to the user behavior library, a behavior analysis model is created and trained;

[0129] Step S21: A single behavior analysis model is created for an OTA upgrade task containing only a single user upgrade behavior;

[0130] For example, a single behavior analysis model of a time period classification is created, the related information containing the user upgrade behavior is directly acquired as the input of the analysis model, the single behavior analysis result is taken as the output of the model, the user upgrade behavior and the upgrade history time period to which the behavior belongs are obtained by analyzing the upgrade log.

[0131] Similarly, independent single behavior analysis models are created for upgrade domain control, upgrade attribute, and whether to upgrade after diagnosis.

[0132] In addition, the upgrade result contained in the newly completed OTA upgrade task can also be used to train the behavior analysis model.

[0133] Step S22: All OTA upgrade tasks containing multiple types of user upgrade behaviors that may exist are exhausted, and a multi-behavior analysis model based on the upgrade task is created;

[0134] All OTA upgrade tasks containing multiple types of user upgrade behaviors that may exist are exhausted.

[0135] Based on the OTA upgrade task containing multiple types of user upgrade behaviors, a multi-behavior analysis model is created, the original user upgrade data is analyzed according to the defined user upgrade behavior classification rules, the user upgrade behaviors that may exist are judged, and the specific user upgrade behaviors belonging to the user upgrade behavior classification are judged; for example, a certain original user upgrade data is analyzed, and it is found that the user upgrade behaviors contained in the user upgrade data include night upgrade, chassis domain upgrade, and regular vehicle end SDK upgrade.

[0136] In addition, all user behaviors of a user in a certain time period can also be found according to the vehicle VIN code, and the user upgrade preference is obtained by analyzing the user behaviors; for example, in February 2024 to June 2024, the user performed 5 times of auxiliary driving domain upgrade and 10 times of vehicle body domain upgrade, and thus the user's upgrade preference is auxiliary driving domain upgrade and vehicle body domain upgrade.

[0137] Step S23: Obtain historical OTA upgrade tasks, and train the single-behavior analysis model and the multi-behavior analysis model.

[0138] Obtain historical OTA upgrade tasks and corresponding OTA upgrade packages, and analyze the upgrade behaviors contained in the OTA upgrade packages.

[0139] According to the OTA upgrade tasks, obtain original user upgrade data performed on the OTA upgrade tasks, and use the original user data as input of the single-behavior analysis model and the multi-behavior analysis model, that is, a training set.

[0140] Associate the upgrade behaviors contained in the OTA upgrade tasks with the original user upgrade data to obtain user actual upgrade results and user upgrade behaviors contained in the user actual upgrade results, and use the user actual upgrade results as a verification set.

[0141] Train the single-behavior analysis model and the multi-behavior analysis model using the training set, and verify the output results of the models using the verification set.

[0142] Step S24: Determine whether the multiple upgrade behaviors contained in the OTA upgrade tasks are compatible, and eliminate OTA upgrade tasks with incompatible upgrade behaviors.

[0143] In actual application, there may be conflicts between user upgrade behaviors of different classification rules, for example, consumption upgrade and post-diagnosis upgrade are generally incompatible, and the incompatible behaviors are eliminated from the multi-behavior analysis model.

[0144] Step S3: Input the pre-release task into the behavior analysis model to obtain a behavior analysis result.

[0145] Step S31: Obtain a pre-release task, and analyze user upgrade behaviors possibly contained in the pre-release task.

[0146] Obtain a pre-release task, analyze the pre-release task to obtain all single user upgrade behaviors possibly contained in the pre-release task, and determine whether there are multiple user upgrade behaviors containing multiple single user upgrade behaviors.

[0147] Step S32: If the pre-release task contains only a single user upgrade behavior, input the single-behavior analysis model to obtain an analysis result.

[0148] If the pre-release task contains only a single user upgrade behavior, input the pre-release task into the single-behavior analysis model to obtain user upgrade preferences in each user upgrade behavior classification rule.

[0149] Step S33: If the pre-release task contains multiple user upgrade behaviors, input the multi-behavior analysis model to obtain an analysis result.

[0150] If the pre-release task contains multiple user upgrade behaviors, the pre-release task is input into the multi-behavior analysis model to obtain the user upgrade preference of the multiple user upgrade behaviors containing multiple single user upgrade behaviors, for example, the pre-release task related content, the user is accustomed to upgrading at night, and the task belongs to Bug type upgrade, and the upgrade tends to upgrade the vehicle body domain and the auxiliary driving domain.

[0151] Step S4: According to the pre-release task and the behavior analysis result, an OTA upgrade package is made and an OTA upgrade task is released.

[0152] According to the pre-release task and the behavior analysis result, the OTA task demand is generated, the OTA upgrade package is developed and verified, and the OTA upgrade task is officially released according to the behavior analysis result.

[0153] In addition, after the OTA upgrade task is officially released for a period of time, the user upgrade data associated with the OTA upgrade task is obtained, which is used as a training set, and the user upgrade result containing the user upgrade behavior is used as a verification set, and the single behavior analysis model and the multi-behavior analysis model are trained and corrected.

[0154] Step S5: Vehicle portrait according to completed historical OTA upgrade task.

[0155] Step S51: Obtain the completed historical OTA upgrade task and the vehicle VIN code contained therein.

[0156] Obtain the completed historical OTA upgrade task and all vehicle VIN codes appearing in the historical OTA upgrade task, and associate the vehicle VIN code with the user upgrade data contained in the historical OTA upgrade task.

[0157] Step S52: Analyze the user upgrade behavior contained in the historical OTA upgrade task.

[0158] Analyze the user upgrade data to obtain the user upgrade behavior under different user upgrade behavior classifications, and associate the user upgrade behavior with the vehicle VIN code.

[0159] Step S53: Automatic generation of vehicle portrait according to user upgrade behavior.

[0160] Integrate the user upgrade behaviors associated with the same vehicle VIN code to obtain the user upgrade behavior preference, thereby automatically generating the vehicle portrait.

[0161] Step S6: Analyze the vehicle portrait and directly generate the OTA upgrade task demand according to the user upgrade preference, develop and verify the OTA upgrade package, and automatically generate the official OTA release task after completion.

[0162] If the OTA upgrade task is suitable for multiple different vehicle images, the OTA upgrade package can also be tested on vehicles of different vehicle images, and the OTA upgrade package is adjusted and optimized according to the test results.

[0163] The OTA task management method based on behavior analysis provided by the embodiment also introduces a vehicle image, performs vehicle imaging according to a completed historical OTA upgrade task, analyzes the vehicle image, directly generates an OTA upgrade task, formulates an OTA task upgrade package according to the generated OTA upgrade task, and thereby can make OTA upgrade packages and publish upgrade tasks that users like, and can also modify and adjust OTA upgrade tasks through vehicle imaging.

[0164] Embodiment three

[0165] As shown in FIG. 3, an OTA task management system 2 based on behavior analysis includes:

[0166] A user behavior library 21 is configured to define user upgrade behaviors and classify user upgrade behaviors into defined user upgrade behaviors.

[0167] A behavior analysis model 22 is created according to the user behavior library 21 and is configured to analyze input pre-release task user upgrade behaviors to obtain behavior analysis results.

[0168] A training module 23 is configured to train the behavior analysis model 22 and add user upgrade behaviors contained in reported OTA upgrade data to the user behavior library to continuously train and correct the behavior analysis model.

[0169] A task publishing module 24 is configured to generate an OTA task demand according to a pre-release task and behavior analysis results, develop and verify an OTA upgrade package, automatically generate an OTA upgrade task after completion, and report OTA upgrade data after completion of the OTA upgrade task.

[0170] A vehicle imaging module 25 is configured to perform vehicle imaging according to a completed historical OTA upgrade task, analyze the vehicle image, and generate an OTA upgrade task demand, develop and verify an OTA upgrade package, and automatically generate a formal OTA release task after completion.

[0171] A test optimization module 26 is configured to test an OTA upgrade package on vehicles of different vehicle images, and adjust and optimize the OTA upgrade package according to test results.

[0172] Embodiment four

[0173] As shown in FIG. 4, an OTA task management device based on behavior analysis includes:

[0174] A memory 100 is configured to store a computer program.

[0175] A processor 200, configured to execute the computer program, implements the steps of the behavior analysis based OTA task management method according to Embodiment I and Embodiment II.

[0176] Embodiment V

[0177] A readable storage medium of a behavior analysis based OTA task management, storing a computer program, the computer program being executed to implement the steps of the behavior analysis based OTA task management method according to Embodiment I and Embodiment II.

[0178] The present application can be a system, a method, and / or a computer program product. The computer program product can include a computer readable storage medium (or media) having computer readable program instructions stored therein (or thereon), the computer readable program instructions being used to program a computer (or other processor-enabled device) to implement aspects of the present application.

[0179] The readable storage medium is a computer-readable storage medium, which can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium can be, for example but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanism that encodes instructions on a set of holes in a punch card, and any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanism that encodes instructions on a set of holes in a punch card, and any suitable combination of the foregoing.

[0180] Computer readable program instructions described herein can be downloaded to respective computing / processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network can comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions to a computer readable storage medium within the respective computing / processing device for storage and / or execution.

[0181] The computer program described herein is a computer readable program instruction that can be downloaded to a corresponding computing / processing device from a computer readable storage medium or to an external computer or an external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network can include copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions to storage media within the corresponding computing / processing device for execution.

[0182] The computer readable program instructions can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer can 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 the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present application.

[0183] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0184] These computer readable program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer readable program instructions can also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including

[0185] The above merely illustrates the specific embodiments of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of the changes or replacements within the technical scope disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A behavior analysis-based OTA task management method, characterized in that, The OTA task management method based on behavior analysis comprises: defining user upgrade behavior, constructing user behavior library; creating and training behavior analysis model according to user behavior library; inputting pre-release task into the behavior analysis model to obtain behavior analysis result; generating OTA task demand according to pre-release task and behavior analysis result, developing and verifying OTA upgrade package, and automatically generating OTA upgrade task after completion; after completing OTA upgrade task, reporting OTA upgrade data, adding user upgrade behavior contained therein to user behavior library, and continuously training and correcting behavior analysis model; vehicle portrait is performed according to completed historical OTA upgrade task, vehicle portrait is analyzed, OTA upgrade task demand is generated, OTA upgrade package is developed and verified, and formal OTA release task is automatically generated after completion.

2. The behavior analysis based OTA task management method of claim 1, wherein, The definition of user upgrade behavior comprises: obtaining user upgrade behavior; defining user upgrade behavior classification rule; defining user upgrade behavior under each classification rule according to user upgrade behavior classification rule.

3. The behavior analysis based OTA task management method of claim 2, wherein, The user upgrade behavior classification rule comprises: classification according to historical upgrade period, classification according to upgrade domain control, classification according to upgrade attribute, classification according to upgrade mode, classification according to upgrade area and infrequent upgrade.

4. The behavior analysis based OTA task management method of claim 2, wherein, The creation and training of behavior analysis model according to user behavior library comprises: creating single behavior analysis model for OTA upgrade task containing only single user upgrade behavior; exhaustively creating multi-behavior analysis model based on OTA upgrade task containing multiple types of user upgrade behavior; obtaining historical OTA upgrade task, training the single behavior analysis model and the multi-behavior analysis model.

5. The behavior analysis based OTA task management method of claim 4, wherein, The creation and training of behavior analysis model further comprises: judging whether multiple upgrade behaviors contained in the OTA upgrade task are compatible, and eliminating OTA upgrade tasks incompatible between upgrade behaviors.

6. The behavior analysis based OTA task management method of claim 4, wherein, The obtaining of historical OTA upgrade task comprises: obtaining historical OTA upgrade task and corresponding OTA upgrade package, and analyzing upgrade behavior contained in the OTA upgrade package.

7. The behavior analysis based OTA task management method of claim 4, wherein, The inputting of pre-release task into the behavior analysis model and the obtaining of behavior analysis result comprise: obtaining pre-release task and analyzing user upgrade behavior contained in the pre-release task; if the pre-release task contains only single user upgrade behavior, inputting single behavior analysis model to obtain analysis result; if the pre-release task contains multiple user upgrade behaviors, inputting multi-behavior analysis model to obtain analysis result.

8. The behavior analysis based OTA task management method of claim 1, wherein, The vehicle portrait performed according to completed historical OTA upgrade task comprises: obtaining completed historical OTA upgrade task and vehicle VIN code contained therein; analyzing user upgrade behavior contained in the historical OTA upgrade task; selecting vehicle VIN code and automatically generating vehicle portrait according to user upgrade behavior.

9. A behavior analysis based OTA task management system characterized by, The OTA task management system based on behavior analysis comprises: user behavior library, used for defining user upgrade behavior and classifying user upgrade behavior into defined user upgrade behavior; behavior analysis model, created according to user behavior library, used for analyzing input user upgrade behavior pre-release task to obtain behavior analysis result; The training module is configured to train the behavior analysis model, and add the user upgrade behavior contained in the reported OTA upgrade data into a user behavior library, and continuously train and correct the behavior analysis model. The task publishing module is configured to generate an OTA task demand according to a pre-release task and a behavior analysis result, develop and verify an OTA upgrade package, automatically generate an OTA upgrade task after completion, report OTA upgrade data after completion of the OTA upgrade task, and the like. The vehicle profiling module is configured to perform vehicle profiling according to completed historical OTA upgrade tasks, analyze the vehicle profiling, generate an OTA upgrade task demand, develop and verify an OTA upgrade package, and automatically generate a formal OTA release task after completion.

10. A behavior analysis based OTA task management device, characterized in that, The behavior analysis-based OTA task management device includes: a memory configured to store a computer program; a processor configured to execute the computer program to implement the steps of the behavior analysis-based OTA task management method according to any one of claims 1-8.

11. An OTA task management storage medium based on behavior analysis, characterized by, The storage medium has the computer program stored thereon, and the computer program is executed to implement the steps of the behavior analysis-based OTA task management method according to any one of claims 1-8.

Images