New energy automobile OTA upgrading method and device based on driving behavior optimization

Abstract

The invention relates to a new energy automobile OTA upgrading method and device based on driving behavior optimization. The method comprises the following steps: acquiring user attribute data, vehicle attribute data and event attribute data of a vehicle; performing process type binding on the event attribute data; constructing a user tag based on the user attribute data, the vehicle attribute data and the event attribute data in combination with a tag rule; creating user groups based on the user attribute data, the vehicle attribute data and the user tags in combination with a grouping rule; creating a part number corresponding to the vehicle type project dimension, carrying out process type binding, and configuring a software package project corresponding to the part number after the process type binding; and configuring an OTA upgrading sequence of all parts corresponding to the vehicle type item dimensions, and creating and executing an OTA upgrading task based on the OTA upgrading sequence in combination with the software package items and the user groups. According to the method, the problem that the matching degree between the upgrading content of the OTA upgrading method and the customer demand is low is solved.

Description

Technical Field

[0001] The present application relates to the field of automobile OTA technology, and in particular to a new energy automobile OTA upgrade method and device based on driving behavior optimization. Background Art

[0002] OTA (Over-the-Air Download Technology) is a process of transmitting software updates, configuration files or other data to devices via wireless networks. In the automotive field, it allows automakers to remotely update and manage vehicle software without physical contact with the vehicle. In the field of automotive technology, OTA upgrade refers to the remote upgrade service of the vehicle. Through OTA technology, automakers can remotely push new software, functions or security updates to the vehicle to achieve online upgrades and maintenance of the vehicle.

[0003] With existing OTA upgrade technologies, many manufacturers tend to adopt a unified upgrade strategy, pushing the same upgrade content to all users, ignoring the differences in driving habits, vehicle usage environments, and personalized needs of different user groups, and adopting a "one-size-fits-all" upgrade approach. As a result, some users may not need or are not suitable for certain upgrade content, while other users may be in urgent need of solving specific problems but fail to obtain corresponding updates in a timely manner, and the OTA upgrade content has a low match with customer needs. In addition, due to the lack of refined upgrade sequence planning and resource allocation mechanisms, it may lead to resource waste and inefficiency during the upgrade process, especially when it involves the upgrade of multiple components and complex software packages.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The present application provides a new energy vehicle OTA upgrade method and device based on driving behavior optimization to solve the technical problem that the above-mentioned OTA upgrade method does not fully consider the user's driving behavior, resulting in a low match between the upgrade content and user needs.

[0006] According to one aspect of an embodiment of the present application, the present application provides an OTA upgrade method for new energy vehicles based on driving behavior optimization, including: obtaining user attribute data, vehicle attribute data and event attribute data of the vehicle; performing process type binding on the event attribute data; constructing user tags based on the user attribute data, the vehicle attribute data and the event attribute data after process type binding in combination with tag rules; creating user groups based on the user attribute data, the vehicle attribute data and the user tags in combination with grouping rules; creating component numbers corresponding to the vehicle model project dimension and performing process type binding, and configuring the software package project of the component number after process type binding; configuring the OTA upgrade order of all components corresponding to the vehicle model project dimension, and creating and executing OTA upgrade tasks based on the OTA upgrade order combined with the software package project and the user group.

[0007] Furthermore, the acquisition of user attribute data, vehicle attribute data and event attribute data of the vehicle includes: acquiring user attribute data of each vehicle through a vehicle after-sales system; acquiring vehicle attribute data of each vehicle through a vehicle production system; and acquiring event attribute data of the vehicle through a VHR system and vehicle sensors.

[0008] Furthermore, the process type binding of the event attribute data includes: determining a process type classification and setting a process type identifier based on the process type classification; analyzing the event attribute data to determine attribute characteristics of the event attribute data; matching the attribute characteristics with the process type, and binding the process type identifier to the event attribute data.

[0009] Furthermore, the user tag is constructed based on the user attribute data, the vehicle attribute data and the event attribute data after being bound to the process type in combination with the tag rules, including: setting a time range and determining a corresponding event name according to the user attribute data, the vehicle attribute data and the event attribute data after being bound to the process type; setting filtering conditions according to the attribute types corresponding to the event attribute data after being bound to the user attribute data, the vehicle attribute data and the process type, and setting corresponding logical relationships for the filtering conditions; obtaining corresponding attribute value input controls according to different filtering conditions, selecting corresponding attribute values ​​according to the attribute value input controls, and selecting indicator values ​​corresponding to different indicators at the same time; determining the corresponding process type and the completion status corresponding to the process type; creating an initial tag through preset tag rules according to the time range, completion status, process type, attribute name, filtering conditions, attribute value, indicator, operator and indicator value in combination with the logical relationship; and dividing the initial tags according to the numerical types to obtain user tags.

[0010] Furthermore, the creating of user groups based on the user attribute data, the vehicle attribute data and the user tags in combination with grouping rules includes: setting corresponding filtering conditions according to the data types corresponding to the user attribute data, the vehicle attribute data and the user tags; obtaining corresponding attribute value input controls based on the filtering conditions, and selecting attribute values ​​corresponding to the user attribute data, the vehicle attribute data and the user tag data respectively through the attribute value input controls; and creating user groups through preset grouping rules based on the filtering conditions, the attribute values ​​and attribute names in combination with corresponding logical relationships.

[0011] Furthermore, the software package project includes a software package or a software package group. The creating of the component number corresponding to the vehicle model project dimension and binding of the process type, and configuring the software package project of the component number after the process type binding include: creating the component number corresponding to each component of each vehicle model project dimension; obtaining the process type classification corresponding to each vehicle model project dimension, and binding of the process type to each component number based on the process type classification; configuring the software package corresponding to each component number after the process type binding; when a single function upgrade depends on multiple software packages or there is a dependency relationship between the software packages, configuring the software package group based on the dependent software packages; verifying the software package or the software package group, and publishing after passing the verification.

[0012] Furthermore, the OTA upgrade sequence of all components corresponding to the configured vehicle model item dimension creates and executes an OTA upgrade task based on the OTA upgrade sequence in combination with the software package project and the user grouping, including: obtaining each of the vehicle model item dimensions, and determining an initial OTA upgrade sequence corresponding to the vehicle model item dimension; tailoring the initial OTA upgrade sequence based on the components corresponding to the software package project to obtain a final OTA upgrade sequence corresponding to the vehicle model item dimension; identifying a user grouping set to be upgraded and a vehicle VIN code set corresponding to the user grouping set based on the software package project, the vehicle VIN code set including a current vehicle VIN code set and a vehicle VIN code set of the previous day; and creating and executing an OTA upgrade task based on the software package project, the final OTA upgrade sequence and the vehicle VIN code set.

[0013] Furthermore, the creating and executing the OTA upgrade task based on the software package project, the final OTA upgrade sequence and the vehicle VIN code set includes: obtaining a process type set bound to the software package project; matching a user group set according to the process type set to retrieve a current vehicle VIN code set and a vehicle VIN code set of the previous day corresponding to each user group; constructing a vehicle VIN code list based on a difference between the current vehicle VIN code set and the vehicle VIN code set of the previous day; and creating and executing the OTA upgrade task in combination with the final OTA upgrade sequence and the vehicle VIN code list.

[0014] According to another aspect of an embodiment of the present application, the present application provides an OTA upgrade device for new energy vehicles based on driving behavior optimization, including: an attribute acquisition module, used to acquire user attribute data, vehicle attribute data and event attribute data of the vehicle; a process type binding module, used to perform process type binding on event attribute data; a label construction module, used to construct user labels based on user attribute data, vehicle attribute data and event attribute data after process type binding in combination with label rules; a user group creation module, used to create user groups based on user attribute data, vehicle attribute data and user labels in combination with grouping rules; a software package group configuration module, used to create component numbers corresponding to vehicle model project dimensions and perform process type binding, and configure software package projects for component numbers after process type binding; an upgrade task configuration module, used to configure the OTA upgrade order of all components corresponding to the vehicle model project dimension, and create and execute OTA upgrade tasks based on the OTA upgrade order combined with software package projects and user groups.

[0015] According to another aspect of an embodiment of the present application, the present application provides an electronic device, including a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, and the memory and the processor communicate through the communication bus and the communication interface, and is characterized in that when the processor executes the computer program, it implements the instructions of the above-mentioned new energy vehicle OTA upgrade method based on driving behavior optimization.

[0016] According to another aspect of an embodiment of the present application, the present application also provides a readable storage medium storing program instructions. When the program instructions are read and executed by a computing device, the computing device executes the above-mentioned new energy vehicle OTA upgrade method based on driving behavior optimization.

[0017] The above technical solution provided by the embodiment of the present application has the following advantages compared with the related art:

[0018] This application uses user attribute data, vehicle attribute data and event attribute data, and combines tag rules and grouping rules to build user tags and user groups, formulates and executes OTA upgrade tasks based on user tags and user groups, takes into account the driving behavior of different customers, the attributes of the vehicle and the specific operating status, and ensures that the OTA upgrade content meets the actual needs of vehicle upgrades. At the same time, it can more accurately identify the needs of different user groups, and enable the OTA upgrade content to better match the needs of different customers. During the upgrade process, customized personalized upgrade content based on user groups can improve user satisfaction. By creating the component number corresponding to the vehicle model project and binding the process type, and configuring the OTA upgrade sequence of the components corresponding to the vehicle model project dimension, the refined management of the upgrade process is achieved, which helps to optimize the upgrade process, reduce resource waste, and shorten the upgrade time. Through the comprehensive analysis of user attribute data, vehicle attribute data and event attribute data, it is possible to intelligently allocate upgrade resources to ensure that vehicles in urgent need of upgrades receive timely services while avoiding excessive waste of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0021] Figure 1 A schematic diagram of the hardware environment of a new energy vehicle OTA upgrade method based on driving behavior optimization provided according to an embodiment of the present application;

[0022] Figure 2 A schematic diagram of a flow chart of an OTA upgrade method for a new energy vehicle based on driving behavior optimization provided according to an embodiment of the present application;

[0023] Figure 3 This is a user tag logical relationship setting interface diagram provided according to an embodiment of the present application;

[0024] Figure 4 Creating an interface diagram for a user tag provided according to an embodiment of the present application;

[0025] Figure 5 A schematic diagram of a user group creation process according to an embodiment of the present application;

[0026] Figure 6A schematic diagram of a process for creating an OTA upgrade task according to an embodiment of the present application;

[0027] Figure 7 An interface diagram for creating user groups according to an embodiment of the present application;

[0028] Figure 8 A structural block diagram of an OTA upgrade device for new energy vehicles based on driving behavior optimization provided according to an embodiment of the present application;

[0029] Fig. 9 A schematic diagram of an optional electronic device structure provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0031] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application and have no specific meaning. Therefore, "module" and "component" can be used interchangeably.

[0032] In related technologies, many manufacturers adopt a "one-size-fits-all" OTA upgrade approach. Since user needs are not fully considered, some users may not need or are not suitable for certain upgrade content, while other users may urgently need to solve specific problems but fail to obtain corresponding updates in a timely manner, resulting in a low match between OTA upgrade content and customer needs.

[0033] In order to solve the problems mentioned in the background technology, according to one aspect of an embodiment of the present application, an embodiment of an OTA upgrade method for a new energy vehicle based on driving behavior optimization is provided.

[0034] Optionally, in the embodiment of the present application, the above method can be applied to Figure 1 In the hardware environment composed of the terminal 101 and the server 103 shown in FIG. Figure 1As shown, the server 103 is connected to the terminal 101 via a network, and can be used to provide services for the terminal or a client installed on the terminal. A database 105 can be set on the server or independently of the server to provide data storage services for the server 103. The above-mentioned network includes but is not limited to: a wide area network, a metropolitan area network or a local area network, and the terminal 101 includes but is not limited to vehicle-mounted terminal equipment, PCs with new energy vehicle applications installed, mobile phones, tablet computers, etc.

[0035] In the embodiment of the present application, a new energy vehicle OTA upgrade method based on driving behavior optimization can be executed by the server 103, or can be executed by the server 103 and the terminal 101 together, such as Figure 2 As shown, the method may include the following steps:

[0036] Step S202, obtaining the user attribute data, vehicle attribute data and event attribute data of the vehicle.

[0037] Specifically, step S202 includes:

[0038] Obtain user attribute data of each vehicle through the vehicle after-sales system;

[0039] Obtaining vehicle attribute data of each vehicle through a vehicle production system;

[0040] The event attribute data of each vehicle is obtained through the VHR system (Vehicle Health Record System) and vehicle sensors.

[0041] It can be understood that this embodiment mainly performs OTA (over-the-air download technology) upgrades on new energy vehicles. Through OTA technology, automobile manufacturers can remotely push new software, functions or security plug-in updates to vehicles to achieve online upgrades and maintenance of vehicles. This embodiment mainly groups users corresponding to vehicle projects, then creates OTA upgrade packages and matches them with user groups.

[0042] Specifically, firstly, the user attribute data of each vehicle is obtained from the vehicle after-sales system, and the user attribute data includes the user's gender, age stage and region. Among them, the user's gender includes male and female; the age stage includes youth, middle age and old age, the age group corresponding to youth is 18-30 years old, the age group corresponding to middle age is 30-50 years old, and the age group corresponding to old age is after 50 years old; the region is determined by weather factors combined with terrain factors, for example, the region includes North China, Northeast China, East China, Central South, Southwest China and Northwest China, among which North China includes Beijing, Tianjin, Northeast China includes Liaoning, Jilin and Heilongjiang, East China includes Shanghai, Jiangsu, Central South China includes Henan, Hubei, Southwest China includes Yunnan, Guizhou, Sichuan, Northwest China includes Shaanxi, Gansu, etc. The attribute types corresponding to the above-mentioned user attribute data include string type, numerical type, time type and Boolean type, for example, the region and user gender are string type, and the age stage is numerical type.

[0043] Furthermore, the vehicle attribute data of each corresponding vehicle is obtained from the vehicle production system. The vehicle attribute data specifically includes brand / model items, vehicle sales status and vehicle type. The brand / model items in this embodiment take SERES5 as an example. The sales status includes warehoused, returned and actually sold. The vehicle types include test vehicles, Beta vehicles (verification vehicles before mass production), ordinary vehicles and exhibition vehicles. Similarly, the attribute types corresponding to each vehicle attribute data also include string type, numeric type, time type and Boolean type.

[0044] Furthermore, the event attribute data of each vehicle corresponding to SERES5 is obtained from the VHR system and vehicle sensors. The event attribute data includes events of user behavior, system built-in, non-incremental, editable and bound process types, and empty bound process types. Similarly, the attribute types corresponding to the event attribute data of each vehicle also include string type, numerical type, time type and Boolean type. For example, the attribute type of the event attribute data "charging type" is a string type, including fast charging and slow charging, the attribute type of the event attribute data "stay-at-home car duration" is a numerical type, the attribute type of the event attribute data "start time" is a time type, and the attribute type of the event attribute data "whether there is a first-level alarm" is a Boolean type, including yes and no.

[0045] In the above embodiment, by obtaining the user attribute data of the vehicle from the vehicle after-sales system, the user attribute data can help analyze the different needs of different user groups for vehicle performance, functions and comfort, so that OTA upgrades can be customized and optimized for specific user groups, improving user satisfaction and driving experience. By obtaining vehicle attribute data from the vehicle production system, OTA upgrades can more accurately identify and solve performance problems in specific models or configurations, reduce invalid upgrades, and improve upgrade efficiency. By obtaining event attribute data from the VHR system and vehicle sensors, the user's driving behavior and vehicle usage status can be directly reflected, which improves energy utilization, extends vehicle life and ensures driving safety.

[0046] Step S204: Bind the event attribute data to a process type.

[0047] Specifically, step S204 includes:

[0048] Determine the process type classification and set the process type identification based on the process type classification;

[0049] Analyze the event attribute data to determine the attribute characteristics of the event attribute data;

[0050] According to the attribute characteristics, the process type is matched, and the process type identifier is bound to the corresponding event attribute data.

[0051] In this embodiment, for example, the process type bound to the event attribute data "number of speeding times", "number of sudden acceleration times", "hybrid mileage", etc. is "driving"; the process type bound to the event attribute data "total number of battery failures" is "charging"; the process types bound to the time attribute data "duration" are "driving", "charging", "parking" and "entertainment" respectively.

[0052] In the above embodiment, by determining the process type classification and setting the corresponding process type identifier, it is helpful to extract information directly related to specific driving behavior or vehicle status from complex event attribute data, thereby improving the accuracy and pertinence of data analysis. By analyzing the attribute characteristics of the event attribute data and matching it with the preset process type, the user's specific driving behavior and the vehicle's operating status can be accurately identified. By binding the process type identifier with the corresponding event attribute data, personalized driving behavior analysis for different users and different models can be achieved, and OTA upgrades can be performed based on these analysis results. Customized optimization solutions can be pushed based on different users' driving habits and vehicle usage.

[0053] Step S206, constructing a user tag based on the user attribute data, the vehicle attribute data and the event attribute data after the process type is bound in combination with the tag rule.

[0054] Specifically, step S206 includes:

[0055] Set the time range and determine the corresponding event name according to the user attribute data, vehicle attribute data and event attribute data bound to the process type;

[0056] Set filtering conditions according to the attribute types corresponding to the event attribute data after the user attribute data, the vehicle attribute data and the process type are bound, and set corresponding logical relationships for the filtering conditions;

[0057] Obtain the corresponding attribute value input control according to different screening conditions, select the corresponding attribute value according to the attribute value input control, and select the indicator value corresponding to different indicators at the same time;

[0058] Determine the corresponding process type and the completion status corresponding to the process type;

[0059] Create initial tags using preset tag rules based on time range, completion status, process type, attribute name, filter condition, attribute value, indicator, operator, and indicator value combined with logical relationships;

[0060] The initial tags are divided according to the numerical type to obtain user tags.

[0061] Further, first determine the tag name, query the preset tag rules, the field names in the tag rules include "time range", "did it", "process type", "attribute name", screening conditions, "attribute value", "indicator", "operator" and "indicator value", the type option corresponding to the time range is "time selection", and the type options corresponding to other field names are mainly "drop-down box", through the "drop-down box" to select the corresponding type, whether it is required in the system options include "yes" and "no", whether it is required option indicates whether the corresponding field needs to be selected. Among them, the fields "time range", "did it", "process type", "indicator", "operator" and "indicator value" corresponding to the required option is "yes", and other fields are "no". The field "time range" corresponds to the dynamic time period, and the dynamic time period includes yesterday, this week, last week, this month, last month, this year, last year, the past 7 days, the past 30 days and the past 90 days. The field "did it" includes done and not done. The field "process type" includes driving, charging, parking and entertainment. The field "attribute name" includes event attributes, user attributes and user tags. The field "Filter Condition" is divided into different filter conditions according to different data attributes. Among them, string types include equal, not equal, contain, not contain, empty, not empty, with value, no value; numerical types include equal, not equal, less than, greater than, interval, with value, no value; time types include absolute time, relative to current time point, relative to current time interval, with value, no value; Boolean types include true, false, with value, no value. The field "Attribute Value" provides corresponding attribute value input controls according to different filter conditions, including input boxes, date boxes, and drop-down boxes; when the filter condition is equal to or not equal to, the "Batch Copy and Paste" button is displayed after the attribute value. Click it to batch paste in the pop-up window. The rule requirement is "separated by line breaks, one value per line, and a maximum of 5,000 entries". The field "Indicator" includes the total number, distribution, and numerical aggregation of the corresponding event-related attributes. The numerical aggregation includes sum, maximum value, minimum value, and mean value; non-numeric event attributes correspond to the number of duplicate removal, and numerical event attributes correspond to the sum, mean value, maximum value, minimum value, and number of duplicate removal. The field "Operator" includes "=", "≠", ">", "<", etc. The field "Indicator Value" provides corresponding attribute value input controls, such as input boxes, date boxes, drop-down boxes, etc., according to different screening conditions.

[0062] Furthermore, if Figure 3The following is the user tag logical relationship setting interface. After determining the corresponding initial tag, you need to set the corresponding logical relationship. The logical relationship allows you to add multiple filter conditions and select "and" or "or". The default is "and" when adding for the first time. Then select "Division method" and set the initial tag to be divided by numerical type as required. You can choose "discrete value", "percentage", or "numerical range". For example, if the discrete value is divided by percentage, the user stratification label is set based on the proportion of the number of target users, and the default is to arrange the indicator value from large to small; if it is divided by numerical range, the numerical range is set as the threshold range of the indicator value, and the user stratification label is set based on the threshold range of the indicator value (only applicable to event attributes of numerical type); when dividing by discrete values, there is no need to stratify users. Finally, the tag data is counted. According to the dynamic time period selected when creating the tag, the tag data statistics are dynamically executed every day. For example, the statistical results obtained are the total number of completions / distribution / sum, mean, maximum value, minimum value, and deduplication number of the corresponding events in the processes of driving, charging, parking, and entertainment that have been done or not done in a specific time period, and that meet the screening conditions (if any), and the number of people is counted according to ("discrete value", "percentage", "value range").

[0063] In this embodiment, for example, the label name is "Pure electric mileage statistics for the past 30 days", and the label rule is set to perform layered statistics on the total pure electric mileage of the owner during driving in the past 30 days according to the numerical range, namely, the total pure electric mileage (0,10], the total mileage (10,30], and the total mileage greater than 30. Figure 4 The figure shows the user tag creation interface. It is calculated that in the past 30 days, the number of people whose total pure electric mileage during driving is (0,10] is 27, the number of people whose total mileage is (10,30] is 33, and the number of people whose total mileage is greater than 30 is 396. For example, if the tag name is "the maximum total number of battery failures in the past 30 days", the corresponding tag rule is the maximum total number of battery failures during the charging process of the car owner in the past 30 days, divided according to discrete numbers. The user tag statistics obtained are the maximum total number of battery failures during the charging process of the car owner in the past 30 days, the number of people with 0 failures is 435, the number of people with 1 failure is 29, and the number of people with 4 failures is 1.

[0064] In the above embodiment, by combining user attribute data, vehicle attribute data and event attribute data after process type binding, the user's driving behavior characteristics can be fully and accurately described. Based on the time range, screening conditions and event name combined with the preset label rules, the user label can be constructed to achieve a fine division of the user's driving behavior. The user label can not only reflect the user's driving habits, but also reveal the performance of the vehicle in different usage scenarios. Manufacturers can accurately formulate OTA upgrade optimization strategies based on user labels.

[0065] Step S208: Create user groups based on user attribute data, vehicle attribute data, and user tags in combination with grouping rules.

[0066] Specifically, step S208 includes:

[0067] Set corresponding filtering conditions according to the data types corresponding to user attribute data, vehicle attribute data and user tags;

[0068] Obtain corresponding attribute value input controls based on the screening conditions, and select attribute values ​​corresponding to user attribute data, vehicle attribute data, and user tag data respectively through the attribute value input controls;

[0069] Create user groups based on the filter conditions, attribute values, and attribute names combined with corresponding logical relationships using preset grouping rules.

[0070] Furthermore, the clustering rules are mainly about the selection of "user attribute satisfaction", "logical relationship" and update method. In the clustering rules, "user attribute satisfaction" is mainly set through "attribute name", "filter condition" and "attribute value". "Attribute name", "filter condition" and "attribute value" are all required items. The field "attribute name" includes vehicle attributes, user attributes and user tags. The three attribute names of vehicle attributes, user attributes and user tags are not required items and can be selected multiple times, but one of the three attribute names must be filled in. The field "filter condition" is divided into different filter conditions according to the different data types of the attribute data. The field "attribute value" provides corresponding attribute value input controls according to different filter conditions, such as input boxes, date boxes, drop-down boxes, etc. The logical relationship is set to "user attribute satisfaction". "User attribute satisfaction" allows new filter conditions to be added and "and" or "or". The default relationship is "and" when it is first added. For example Figure 5 The following is a detailed flow chart of the complete process of user grouping, combined with Figure 5 As can be seen from the above embodiments, user grouping mainly involves first obtaining user attribute data, vehicle data and event attribute data, then binding the event attribute data to process types, and then constructing user tags based on the obtained attribute data, and then creating user groups by combining the obtained user tags. Among them, steps S501 to S511 correspond to steps S202 to S212 in the above embodiments.

[0071] For example, when the user group name is "SERES5-battery failure or pure electric mileage greater than 10", the corresponding grouping rules include selecting the user label-the maximum value of the total number of battery failures in the past 30 days is not equal to 0, or the user label-the pure electric mileage statistics in the past 30 days is equal to the total mileage (10,30] and the total mileage is greater than 30. The obtained result is intersected with the vehicle attribute-car series code equal to SERES5.

[0072] In the above embodiment, by comprehensively considering user attribute data, vehicle attribute data and user tags, users can be divided into different groups more accurately. Users in each group have similar driving behavior characteristics, vehicle usage habits and demand preferences, so that OTA upgrades can push more personalized upgrade content based on the characteristics of different user groups, thereby improving the pertinence and effectiveness of the upgrade.

[0073] Step S210, creating a component number corresponding to the vehicle model project dimension and binding the process type, and configuring the software package project of the component number after the process type is bound.

[0074] Specifically, the software package group in step S210 includes a software package or a software package group. Step S210 includes:

[0075] Create the corresponding part number for each part in each vehicle model project dimension;

[0076] Obtain the process type classification corresponding to each vehicle model project dimension, and bind each part number to the process type based on the process type classification;

[0077] The software packages corresponding to each part number after the configuration process type is bound;

[0078] When a single function upgrade depends on multiple software packages or there are dependencies between the software packages, configure the software package group based on the dependent software packages;

[0079] Verify the software package or software package group and release it after passing the verification.

[0080] Furthermore, first create the part number corresponding to each component of each model, for example, create the BCM part number under the model SERES5 as SERES5_32733-RA02-7482_0x726, and bind the BCM part number to the driving and charging process; create the TBOX part number under the model SERES5 as SERES5_3505140-RA01-1157_0x0516, and bind the TBOX part number to the driving, charging, parking, and entertainment process, IVI→entertainment, CDC→driving, BMS→charging, TBOX→driving, charging, parking, and entertainment. For example, the CDC part under the SERES5 model project has a part number of SERES5_2103500-RA09-8055_0x17E1, which is bound to the driving process. Then determine whether it is necessary to configure the software package group. If there is a specific function that requires multiple software packages to be upgraded before it can be used normally or a software package upgrade needs to rely on other software packages, then the software package group configuration is required to configure these software packages into the same group of software packages (i.e., software package group). First, determine the software packages corresponding to the aforementioned part numbers. For example, the software package corresponding to the BCM part number is PKG1, the software package corresponding to the TBOX part number is PKG2, and the software package corresponding to the CDC part number is PKG3. Function 1 requires that both software packages PKG1 and PKG2 are fully upgraded before it can be used normally. In this case, set software packages PKG1 and PKG2 as a software package group. Or, when software package PKG2 needs to use software package PKG3 during the upgrade, set software packages PKG2 and PKG3 as a software package group. When a software package in a software package group fails to upgrade, all software packages in the software package group will be rolled back to the previous version together. Finally, upload the obtained software package group or software package group to the software packages of BCM parts and TBOX parts under vehicle model SERES5.

[0081] In the above embodiment, by creating corresponding part numbers for each vehicle model and binding process types to these part numbers, it is possible to ensure that the specific parts that need to be upgraded or optimized are accurately located during the OTA upgrade process, reducing misoperations during the upgrade process and improving upgrade efficiency. When a function requires the use of multiple software packages for upgrade or other software packages are required for software package upgrades, configuring a software package group for the part number after process type binding avoids upgrade failures due to dependency issues, ensures that each software package is optimized for specific parts and process types, and can maximize the effect of OTA upgrades and improve vehicle performance and user experience.

[0082] Step S212, configure the OTA upgrade sequence of all components corresponding to the vehicle model project dimension, create and execute OTA upgrade tasks based on the OTA upgrade sequence combined with the software package project and user grouping.

[0083] Specifically, step S212 includes:

[0084] Obtain the project dimensions of each vehicle model and determine the initial OTA upgrade order corresponding to the project dimensions of each vehicle model;

[0085] The initial OTA upgrade sequence is trimmed based on the components corresponding to the software package project to obtain the final OTA upgrade sequence corresponding to the vehicle model project dimension;

[0086] Identifying a user group set to be upgraded based on the software package project and a vehicle VIN code set corresponding to the user group set, wherein the vehicle VIN code set includes a current vehicle VIN code set and a vehicle VIN code set of the previous day;

[0087] Create and execute OTA upgrade tasks based on software package projects, final OTA upgrade sequence and vehicle VIN code set.

[0088] In this embodiment, by cutting the initial OTA upgrade sequence through the components corresponding to the software package project, the upgrade tasks that are not related to the current vehicle model project dimension can be removed, reducing unnecessary upgrade operations. The final OTA upgrade sequence after cutting is closer to actual needs, which improves the pertinence and effectiveness of the upgrade. Based on the software package project to identify the user group set that needs to be upgraded, it can ensure that the upgrade task accurately covers the user group that needs to be upgraded to avoid omissions or wrong upgrades. The VIN code of the vehicle is the vehicle identification code (frame number). By combining the current vehicle VIN code set with the vehicle VIN code set of the previous day to track the vehicle status in real time, the accuracy and timeliness of the upgrade task can be ensured. Based on the software package project, the final OTA upgrade sequence and the vehicle VIN code set, the OTA upgrade task is created and executed, which can realize the automation and intelligent execution of the upgrade task and improve the upgrade efficiency. Through a reasonable upgrade sequence and accurate user group identification, the impact on the normal use of the user's vehicle during the upgrade process can be reduced, and the user experience can be improved.

[0089] Specifically, an OTA upgrade task is created and executed based on the software package project, the final OTA upgrade sequence, and the vehicle VIN code set, including:

[0090] Get the process type collection bound to the software package project;

[0091] According to the process type set, the user group set is matched to retrieve the current vehicle VIN code set and the vehicle VIN code set of the previous day corresponding to each user group;

[0092] Building a vehicle VIN code list based on the difference between the current vehicle VIN code set and the vehicle VIN code set of the previous day;

[0093] Create and execute OTA upgrade tasks based on the final OTA upgrade sequence and vehicle VIN code list.

[0094] In this embodiment, the process type set bound to the software package project (software package group or software package) is matched to the user group to retrieve the current VIN code set and the vehicle VIN code set of the previous day, and the VIN code set of the previous day included in the current VIN code set is removed to construct the final OTA upgrade sequence of the vehicle VIN code list set to create an OTA upgrade task. Figure 6 The figure shows the flow chart of OTA upgrade task creation. It can be seen that the OTA upgrade task mainly configures and releases the software package or software package group first, then obtains the process type set and matches the user group, determines the current vehicle VIN code set and the vehicle BIN code set of the previous day based on the user group to obtain the vehicle VIN code list, and finally creates the OTA upgrade task based on the vehicle VIN code list and the final OTA upgrade sequence. Figure 6 Steps S602 to S612 in the embodiment correspond to steps S210 to S212 in the embodiment described above. Figure 7 As shown, for example, according to the user group "SERES5-battery failure or pure electric mileage greater than 10", the corresponding vehicle VIN codes of the car owners who meet the requirements are automatically obtained, and the upgrade task and the list of upgraded vehicle VIN codes are generated. The software package group or software package is pushed to the vehicle VIN code in the list of upgraded vehicle VIN codes. According to the OTA upgrade sequence after the vehicle parts are cut, the vehicle corresponding to the model project downloads the software package group or software package after receiving it, and performs the OTA upgrade according to the received cut upgrade sequence, and the status and progress of the upgrade process are synchronized to the platform.

[0095] In the above embodiment, a vehicle VIN code list is constructed based on the difference between the current vehicle VIN code set and the vehicle VIN code set of the previous day, which effectively identifies newly added or changed vehicles, thereby reducing redundancy and errors caused by repeated processing of the same vehicle or omission of newly added vehicles. By updating the vehicle VIN code set in real time and constructing upgrade tasks accordingly, it is possible to quickly respond to vehicle changes and ensure that newly added or changed vehicles can obtain necessary upgrades in a timely manner, thereby improving the user experience. Creating OTA upgrade tasks based on the vehicle VIN code list can associate each OTA upgrade task with a specific vehicle VIN code, which is helpful for subsequent upgrade record management and problem tracking. If problems occur during the upgrade process, the affected vehicles can be quickly located based on the vehicle VIN code list, and targeted problem troubleshooting and resolution can be performed.

[0096] According to another aspect of the embodiment of the present application, Figure 8 As shown, a new energy vehicle OTA upgrade device based on driving behavior optimization is provided, comprising:

[0097] The attribute acquisition module 801 is used to acquire the user attribute data, vehicle attribute data and event attribute data of the vehicle;

[0098] The process type binding module 803 is used to perform process type binding on event attribute data;

[0099] The tag construction module 805 is used to construct a user tag based on the user attribute data, the vehicle attribute data and the event attribute data after the process type is bound in combination with the tag rules;

[0100] User group creation module 807, used to create user groups based on user attribute data, vehicle attribute data and user tags combined with grouping rules;

[0101] The software package group configuration module 809 is used to create the component number corresponding to the vehicle model project dimension and perform process type binding, and configure the software package project of the component number after the process type binding;

[0102] The upgrade task configuration module 811 is used to configure the OTA upgrade sequence of all components corresponding to the vehicle model project dimension, and to create and execute OTA upgrade tasks based on the OTA upgrade sequence combined with the software package project and user grouping.

[0103] It should be noted that the attribute acquisition module 801 in this embodiment can be used to execute step S202 in the embodiment of the present application, the process type binding module 803 in this embodiment can be used to execute step S204 in the embodiment of the present application, the label construction module 805 in this embodiment can be used to execute step S206 in the embodiment of the present application, the user group creation module 807 in this embodiment can be used to execute step S208 in the embodiment of the present application, the software package group configuration module 809 in this embodiment can be used to execute step S210 in the embodiment of the present application, and the upgrade task configuration module 811 in this embodiment can be used to execute step S212 in the embodiment of the present application.

[0104] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules as part of the device can be run in Figure 1 In the hardware environment shown, it can be implemented by software or by hardware.

[0105] Furthermore, the attribute acquisition module is specifically used to: acquire user attribute data of each vehicle through a vehicle after-sales system; acquire vehicle attribute data of each vehicle through a vehicle production system; and acquire event attribute data of the vehicle through a VHR system and vehicle sensors.

[0106] Furthermore, the process type binding module is specifically used to: determine the process type classification and set the process type identifier based on the process type classification; analyze the event attribute data to determine the attribute characteristics of the event attribute data; match the process type according to the attribute characteristics, and bind the process type identifier to the event attribute data.

[0107] Furthermore, the label construction module is specifically used to: set a time range and determine a corresponding event name according to the user attribute data, the vehicle attribute data and the event attribute data after being bound to the process type; set filtering conditions according to the attribute types corresponding to the event attribute data after being bound to the user attribute data, the vehicle attribute data and the process type, and set corresponding logical relationships for the filtering conditions; obtain corresponding attribute value input controls according to different filtering conditions, select corresponding attribute values ​​according to the attribute value input controls, and simultaneously select indicator values ​​corresponding to different indicators; determine the corresponding process type and the completion status corresponding to the process type; create an initial label according to the time range, completion status, process type, attribute name, filtering conditions, attribute value, indicator, operator and indicator value in combination with the logical relationship through preset label rules; and divide the initial labels according to the numerical types to obtain user labels.

[0108] Furthermore, the user grouping creation module is specifically used to: set corresponding filtering conditions according to the data types corresponding to the user attribute data, the vehicle attribute data and the user tags; obtain corresponding attribute value input controls based on the filtering conditions, and select attribute values ​​corresponding to the user attribute data, the vehicle attribute data and the user tag data respectively through the attribute value input controls; create user groups according to preset grouping rules based on the filtering conditions, the attribute values ​​and attribute names combined with corresponding logical relationships.

[0109] Furthermore, the software package project includes a software package or a software package group, and the software package group configuration module is specifically used to: create a part number corresponding to each part of each vehicle model project dimension; obtain a process type classification corresponding to each vehicle model project dimension, and perform process type binding on each part number based on the process type classification; configure the software package corresponding to each part number after process type binding; when a single function upgrade depends on multiple software packages or there is a dependency relationship between the software packages, configure the software package group based on the dependent software packages; verify the software package or the software package group, and publish it after passing the verification.

[0110] Furthermore, the upgrade task configuration module is specifically used to: obtain the dimensions of each vehicle model project, and determine the initial OTA upgrade order corresponding to the vehicle model project dimensions; tailor the initial OTA upgrade order based on the components corresponding to the software package project to obtain the final OTA upgrade order corresponding to the vehicle model project dimensions; identify the user group set to be upgraded and the vehicle VIN code set corresponding to the user group set based on the software package project, the vehicle VIN code set including the current vehicle VIN code set and the vehicle VIN code set of the previous day; create and execute the OTA upgrade task based on the software package project, the final OTA upgrade order and the vehicle VIN code set.

[0111] Furthermore, the upgrade task configuration module is also used to: obtain a process type set bound to the software package project; match a user group set according to the process type set to retrieve a current vehicle VIN code set and a vehicle VIN code set of the previous day corresponding to each user group; construct a vehicle VIN code list based on the difference between the current vehicle VIN code set and the vehicle VIN code set of the previous day; and create and execute an OTA upgrade task in combination with the final OTA upgrade sequence and the vehicle VIN code list.

[0112] According to another aspect of the embodiments of the present application, the present application provides an electronic device, such as Fig. 9 As shown, it includes a memory 901, a processor 903, a communication interface 905 and a communication bus 907. The memory 901 stores a computer program that can be run on the processor 903. The memory 901 and the processor 903 communicate through the communication interface 905 and the communication bus 907. When the processor 903 executes the computer program, the steps of the above method are implemented.

[0113] The memory and processor in the above electronic device communicate through the communication bus and the communication interface. The communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0114] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0115] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0116] According to another aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes a computer instruction, and the computer instruction is stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device performs the steps of any of the above embodiments.

[0117] Optionally, in an embodiment of the present application, the computer-readable medium is configured to store program codes for the processor to execute the following steps:

[0118] Step S202, obtaining user attribute data, vehicle attribute data and event attribute data of the vehicle;

[0119] Step S204, binding the event attribute data to a process type;

[0120] Step S206, constructing a user tag based on the user attribute data, the vehicle attribute data and the event attribute data after the process type is bound in combination with the tag rule;

[0121] Step S208, creating user groups based on user attribute data, vehicle attribute data and user tags combined with grouping rules;

[0122] Step S210, creating a component number corresponding to the vehicle model project dimension and performing process type binding, and configuring a software package project for the component number after the process type binding;

[0123] Step S212, configure the OTA upgrade sequence of all components corresponding to the vehicle model project dimension, create and execute OTA upgrade tasks based on the OTA upgrade sequence combined with the software package project and user grouping.

[0124] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0125] When the embodiments of the present application are specifically implemented, reference may be made to the above-mentioned embodiments, which have corresponding technical effects.

[0126] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of the present application, or a combination thereof.

[0127] For software implementation, the technology of this article can be implemented by a unit that performs the functions of this article. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0128] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0129] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0130] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

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

[0132] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0133] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk. It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, article or device. Without more constraints, an element defined by the phrase "comprising a ..." does not exclude the existence of other identical elements in the process, method, article or apparatus comprising the element.

[0134] The above is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A new energy vehicle OTA upgrade method based on driving behavior optimization, characterized in that: include: Obtaining user attribute data, vehicle attribute data and event attribute data of the vehicle; Performing process type binding on the event attribute data; Constructing a user tag based on the user attribute data, the vehicle attribute data and the event attribute data bound to the process type in combination with a tag rule; Creating user groups based on the user attribute data, the vehicle attribute data and the user tags in combination with grouping rules; Create a component number corresponding to the vehicle model project dimension and perform process type binding, and configure a software package project for the component number after process type binding; Configure the OTA upgrade sequence of all components corresponding to the vehicle model project dimension, and create and execute OTA upgrade tasks based on the OTA upgrade sequence combined with the software package project and the user grouping.

2. The OTA upgrade method for new energy vehicles based on driving behavior optimization according to claim 1 is characterized in that: The step of obtaining the user attribute data, vehicle attribute data and event attribute data of the vehicle includes: Obtain user attribute data of each vehicle through the vehicle after-sales system; Obtaining vehicle attribute data of each vehicle through a vehicle production system; The event attribute data of the vehicle is obtained through the VHR system and vehicle sensors.

3. The OTA upgrade method for new energy vehicles based on driving behavior optimization according to claim 1 is characterized in that: The process type binding of the event attribute data includes: determining a process type classification and setting a process type identifier based on the process type classification; Analyzing the event attribute data to determine attribute characteristics of the event attribute data; The attribute feature is matched with the process type, and the process type identifier is bound to the event attribute data.

4. The OTA upgrade method for new energy vehicles based on driving behavior optimization according to claim 1, characterized in that: The step of constructing a user tag based on the user attribute data, the vehicle attribute data, and the event attribute data bound to the process type in combination with a tag rule includes: According to the user attribute data, the vehicle attribute data and the event attribute data bound to the process type, a time range is set and a corresponding event name is determined; Setting a screening condition according to the attribute type corresponding to the event attribute data after the user attribute data, the vehicle attribute data and the process type are bound, and setting a corresponding logical relationship for the screening condition; Acquire corresponding attribute value input controls according to different screening conditions, select corresponding attribute values ​​according to the attribute value input controls, and select indicator values ​​corresponding to different indicators at the same time; Determine a corresponding process type and a completion status corresponding to the process type; Creating an initial tag through a preset tag rule according to the time range, completion status, process type, attribute name, screening condition, attribute value, indicator, operator and indicator value in combination with the logical relationship; The initial tags are divided according to the value type to obtain user tags.

5. The OTA upgrade method for new energy vehicles based on driving behavior optimization according to claim 1, characterized in that: The creating user groups based on the user attribute data, the vehicle attribute data and the user tags in combination with grouping rules includes: Setting corresponding screening conditions according to the data types corresponding to the user attribute data, the vehicle attribute data and the user tag; Acquire a corresponding attribute value input control based on the screening condition, and select attribute values ​​corresponding to the user attribute data, the vehicle attribute data, and the user tag data respectively through the attribute value input control; User groups are created according to the screening conditions, the attribute values ​​and the attribute names in combination with corresponding logical relationships through preset grouping rules.

6. The OTA upgrade method for new energy vehicles based on driving behavior optimization according to claim 1, characterized in that: The software package project includes a software package or a software package group. The step of creating a component number corresponding to the vehicle model project dimension and performing process type binding, and configuring the software package project of the component number after process type binding includes: Create component numbers corresponding to each component of each vehicle model project dimension; Obtaining the process type classification corresponding to each vehicle model project dimension, and binding the process type to each component number based on the process type classification; The software packages corresponding to the component numbers after configuration process type binding; When a single function upgrade depends on multiple software packages or there is a dependency relationship between the software packages, configuring a software package group based on the dependent software packages; The software package or software package group is verified and released after passing the verification.

7. The OTA upgrade method for new energy vehicles based on driving behavior optimization according to claim 1, characterized in that: The OTA upgrade order of all components corresponding to the configuration vehicle model project dimension, creating and executing OTA upgrade tasks based on the OTA upgrade order combined with the software package project and user grouping, includes: Obtaining each of the vehicle model project dimensions, and determining an initial OTA upgrade order corresponding to the vehicle model project dimensions; Tailoring the initial OTA upgrade sequence based on the components corresponding to the software package project to obtain a final OTA upgrade sequence corresponding to the vehicle model project dimension; Identifying a user group set to be upgraded based on the software package project and a vehicle VIN code set corresponding to the user group set, wherein the vehicle VIN code set includes a current vehicle VIN code set and a vehicle VIN code set of a previous day; An OTA upgrade task is created and executed based on the software package items, the final OTA upgrade sequence and the vehicle VIN code set.

8. The OTA upgrade method for new energy vehicles based on driving behavior optimization according to claim 7 is characterized in that: The creating and executing the OTA upgrade task based on the software package project, the final OTA upgrade sequence and the vehicle VIN code set includes: Obtain a process type set bound to the software package project; Matching the user group set according to the process type set to retrieve the current vehicle VIN code set and the vehicle VIN code set of the previous day corresponding to each user group; Building a vehicle VIN code list based on the difference between the current vehicle VIN code set and the vehicle VIN code set of the previous day; An OTA upgrade task is created and executed in combination with the final OTA upgrade sequence and the vehicle VIN code list.

9. A new energy vehicle OTA upgrade device based on driving behavior optimization, applicable to the new energy vehicle OTA upgrade method based on driving behavior optimization as described in any one of claims 1-8, characterized in that: include: An attribute acquisition module, used to acquire user attribute data, vehicle attribute data and event attribute data of a vehicle; Process type binding module, used to perform process type binding on event attribute data; A label building module is used to build user labels based on user attribute data, vehicle attribute data and event attribute data bound to process types in combination with label rules; A user group creation module, used to create user groups based on user attribute data, vehicle attribute data and user tags combined with grouping rules; The software package group configuration module is used to create the part number corresponding to the vehicle model project dimension and bind the process type, and configure the software package project of the part number after the process type is bound; The upgrade task configuration module is used to configure the OTA upgrade sequence of all components corresponding to the vehicle model project dimension, and create and execute OTA upgrade tasks based on the OTA upgrade sequence combined with the software package project and user grouping.

10. An electronic device, comprising a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, and the memory and the processor communicate through the communication bus and the communication interface, characterized in that: When the processor executes the computer program, it implements the instructions of the new energy vehicle OTA upgrade method based on driving behavior optimization described in any one of 1-8 above.

11. A readable storage medium storing program instructions, when the program instructions are read and executed by a computing device, the computing device executes the new energy vehicle OTA upgrade method based on driving behavior optimization as claimed in any one of claims 1 to 8.

Images