Vehicle upgrading scheduling method and system based on cloud and vehicle
Through the cloud-based vehicle upgrade scheduling method, the upgrade operation is automatically performed during the vehicle idle time period, which solves the problems of upgrade delay and low success rate caused by user intervention, reduces operation and maintenance costs, and improves the upgrade rate.
Patent Information
- Application Number
- CN202411085743.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-08
- Publication Date
- 2024-12-03
AI Technical Summary
In the prior art, the vehicle upgrade process requires user intervention, resulting in a delay in upgrading, a low success rate, and an increase in operation and maintenance costs.
Through the cloud-based vehicle upgrade scheduling method, vehicle usage data is collected, idle time statistics are generated, idle situations are evaluated in different time periods, the upgrade time window is decided, and the upgrade operation is automatically performed within the specified time window to reduce user intervention.
It reduces the delay and expired cancellation of upgrade tasks, reduces the probability of problems due to compatibility between versions, reduces offline operation and maintenance costs, and improves the version upgrade rate.
Smart Images

Figure CN119071362A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of vehicle technology, and in particular to a cloud-based vehicle upgrade scheduling method, system, electronic equipment, storage medium and vehicle. Background Art
[0002] At present, the OTA technology of automobiles can upgrade the cockpit system software and controller software for the car computer. After the cloud upgrade package management platform releases the upgrade task, the car end can receive the task and download the upgrade package to the local car computer, and then the upgrade can be installed. At present, the better way to upgrade the car computer system is the silent installation method, that is, first perform the B-side installation without the user noticing. After the B-side installation is completed, the user is reminded to authorize the flip and A-side installation. This design must require user intervention.
[0003] The A-side installation and upgrade process is mainly for installation tasks that cannot be completed during operation and on the B-side installation, such as the upgrade and installation of the controller software.
[0004] If user intervention is required, the upgrade task may be delayed or canceled due to expiration. If the user does not upgrade or forgets to upgrade, the risk of upgrade success rate increases with the number of version iterations. If there is a compatibility problem between versions, offline operation and maintenance is required, which increases the operation and maintenance cost.
[0005] Therefore, the present application provides a cloud-based vehicle upgrade scheduling method to solve the above technical problems. Summary of the invention
[0006] The purpose of the present invention is to provide a cloud-based vehicle upgrade scheduling method, system, electronic device, storage medium and vehicle to solve the technical problems in the prior art that the upgrade process requires user intervention, resulting in upgrade delays, low upgrade success rate and increased operation and maintenance costs.
[0007] In order to solve the above technical problems, the present invention provides a cloud-based vehicle upgrade scheduling method, comprising:
[0008] a data collection and processing step, including generating statistical information regarding vehicle idle time in response to the collected vehicle usage data;
[0009] An idle time evaluation and decision step, comprising evaluating the idle conditions of the vehicle in different time periods in response to the statistical information of the idle time of the vehicle, and determining an upgrade time window based on the idle conditions;
[0010] a scheduling mode determination step, comprising assigning a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes a sending time and frequency of the upgrade instruction;
[0011] The control and response step includes executing the upgrade operation and reporting the upgrade result in response to the upgrade instruction within the specified upgrade time window.
[0012] In some specific embodiments, the data collection and processing step includes generating statistical information about vehicle idle time in response to the collected vehicle usage data, further comprising:
[0013] Acquire vehicle usage data including a timestamp, wherein the vehicle usage data includes a vehicle ignition event and a vehicle shutdown event;
[0014] Preprocessing the vehicle usage data to ensure the accuracy and completeness of the vehicle usage data;
[0015] The pre-processed vehicle usage data is classified according to the dimensions of date and time period, and the number of days that the vehicle is idle in each time period is calculated to generate the statistical information.
[0016] In some specific embodiments, the idle time evaluation and decision step includes evaluating the idle conditions of the vehicle in different time periods in response to the statistical information of the idle time of the vehicle, and determining the upgrade time window based on the idle conditions, further comprising:
[0017] Based on the statistical information, the proportion of idle days in the morning, afternoon and early morning time periods are calculated respectively;
[0018] Compare the calculated idle days ratio with a preset threshold to determine whether the idleness level of each time period meets the upgrade requirements;
[0019] According to the comparison result of the idle days ratio, a preset decision logic is applied to determine the applicable upgrade time window;
[0020] The decision result is output as configuration information of the upgrade time window.
[0021] In some specific embodiments, the scheduling mode determination step includes assigning a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes the sending time and frequency of the upgrade instruction, and further includes:
[0022] Traversing a scheduling mode library, the scheduling mode library includes a plurality of preset scheduling modes and corresponding parameter settings;
[0023] According to the idle time evaluation result, selecting a matching scheduling mode from the scheduling mode library;
[0024] Setting specific parameters for the selected scheduling mode, including the start and end time of the upgrade time window, the number of retries and the interval;
[0025] The set scheduling mode and parameters are applied to the vehicle, and the upgrade instruction is prepared to be sent within the specified upgrade time window.
[0026] In some specific embodiments, the control and response step includes executing the upgrade operation and reporting the upgrade result in response to the upgrade instruction within the specified upgrade time window, and further includes:
[0027] Sending the upgrade instruction within the specified upgrade time window;
[0028] In response to the upgrade instruction, confirm and check whether the system is currently in an idle state and meets the upgrade conditions;
[0029] When the upgrade conditions are met, the upgrade operation is performed, including downloading the upgrade package and installing the new version, and during the upgrade process, the upgrade progress and status are monitored;
[0030] When the upgrade is completed, the upgrade results will be reported.
[0031] In some specific embodiments, it also includes:
[0032] In response to the specified upgrade time window, the user can remotely reserve or cancel the upgrade operation;
[0033] During the upgrade operation, the upgrade progress is sent to the user in real time, and after the upgrade is completed, the upgrade result is informed, and the user is allowed to evaluate the upgrade effect.
[0034] Based on the same concept, the present invention also provides a cloud-based vehicle upgrade scheduling system, including:
[0035] a data collection and processing module configured to generate statistical information about vehicle idle time in response to the collected vehicle usage data;
[0036] an idle time evaluation and decision module, configured to include, in response to the statistical information of the idle time of the vehicle, evaluate the idle conditions of the vehicle in different time periods, and determine the upgrade time window based on the idle conditions;
[0037] a scheduling mode determination module, configured to allocate a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes a sending time and frequency of the upgrade instruction;
[0038] The control and response module is configured to execute the upgrade operation and report the upgrade result in response to the upgrade instruction within the specified upgrade time window.
[0039] Based on the same concept, the present invention also provides an electronic device, comprising: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the cloud-based vehicle upgrade scheduling method.
[0040] Based on the same concept, the present invention also provides a computer-readable storage medium, which stores a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the cloud-based vehicle upgrade scheduling method.
[0041] Based on the same concept, the present invention also provides a vehicle, wherein the vehicle is provided with the cloud-based vehicle upgrade scheduling system as described above.
[0042] Compared with the prior art, the invention has the following beneficial effects:
[0043] The present invention discloses a cloud-based vehicle upgrade scheduling method, system, electronic device, storage medium and vehicle, which can reduce operations requiring user intervention, reduce delays or cancellations of upgrade tasks due to expiration, reduce the probability of problems due to compatibility between versions, reduce possible offline operation and maintenance costs, and improve version upgrade rates. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 It is a flowchart of a cloud-based vehicle upgrade scheduling method in some specific embodiments of the present invention;
[0045] Figure 2 It is a schematic diagram of the user behavior data reporting process of a cloud-based vehicle upgrade scheduling method in some applications of the present invention;
[0046] Figure 3 It is a data class diagram and a conceptual definition diagram of a cloud-based vehicle upgrade scheduling method in some applications of the present invention;
[0047] Figure 4 It is a flowchart of a cloud-based vehicle upgrade scheduling method in some applications of the present invention;
[0048] Figure 5 It is a schematic diagram of a user behavior data analysis service process in some applications of a cloud-based vehicle upgrade scheduling method of the present invention;
[0049] Figure 6 It is a structural schematic diagram of a cloud-based vehicle upgrade scheduling system in some specific embodiments of the present invention;
[0050] Figure 7 It is a schematic diagram of the structure of an electronic device in some specific embodiments of the present invention. DETAILED DESCRIPTION
[0051] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all 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 the present application.
[0052] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings, and "multiple" generally includes at least two.
[0053] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0054] It should be understood that although the terms first, second, third, etc. may be used to describe in the embodiments of the present application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, without departing from the scope of the embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first.
[0055] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.
[0056] It should also be noted that the term "includes", "comprising" or any other variation thereof is intended to cover non-exclusive inclusion, so that a commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprising a ..." do not exclude the existence of other identical elements in the commodity or device including the elements.
[0057] It should be particularly noted that any symbols and / or numbers in the specification that are not marked in the accompanying drawings are not drawing marks.
[0058] Reference Figure 1 , a cloud-based vehicle upgrade scheduling method, comprising:
[0059] S101, a data collection and processing step, comprising generating statistical information about vehicle idle time in response to the collected vehicle usage data;
[0060] It is understood that idle time is defined as the period of time when the vehicle is not in motion and is not in use. In order to more precisely count the idle time, a day can be divided into multiple time windows (such as one window per hour, or the window size can be adjusted according to actual needs). Then, for each time window, the idle time of the vehicle in the window is calculated.
[0061] Based on the above idle time definition and time window division, statistical information about vehicle idle time is generated, including:
[0062] Daily idle time: Statistics on the total idle time of vehicles every day.
[0063] Idle time distribution: Lists the idle time of each time window in each day to form the distribution of idle time periods.
[0064] Consecutive Idle Days: Records the number of consecutive days the vehicle is idle.
[0065] Association between geographic location and idle time: Analyze the idle time distribution of vehicles in different geographic locations (such as home address, workplace, frequented places, etc.).
[0066] In some of the applications, the data collection and processing steps include generating statistical information about vehicle idle time in response to the collected vehicle usage data, obtaining vehicle usage data containing timestamps, the vehicle usage data including vehicle ignition events and vehicle shutdown events; preprocessing the vehicle usage data to ensure the accuracy and completeness of the vehicle usage data; classifying the preprocessed vehicle usage data according to the dimensions of date and time period, and calculating the number of days the vehicle is idle in each time period to generate statistical information.
[0067] It is understandable that the timestamp information including but not limited to the vehicle ignition event (engine start) and vehicle shutdown event (engine shutdown) is obtained. The rationality of the timestamp is checked (such as avoiding future timestamps, repeated timestamps, etc.), and the vehicle ignition and vehicle shutdown events are ensured to appear in pairs (that is, each ignition event has a corresponding shutdown event). The data integrity check is performed to ensure that there are corresponding vehicle ignition and vehicle shutdown records in each time period.
[0068] According to the needs, a day is divided into multiple time periods as the basic unit for counting idle days. The preprocessed vehicle usage data is classified according to the dimensions of date and time period. That is, for each date and time period, there is a corresponding vehicle usage record (including ignition and shutdown events). For each time period, by comparing the timestamps of the ignition and shutdown events, calculate whether the vehicle is idle during the time period (that is, there is no ignition event or the ignition is not started for a long time after being shut down). If the vehicle has been in the shutdown state for a period of time and there is no new ignition event, the vehicle in the time period is considered to be idle. For each date, the number of days the vehicle is idle in each time period is counted to generate a statistical report containing information such as date, time period, and idle days.
[0069] S102, an idle time evaluation and decision step, comprising evaluating the idle conditions of the vehicle in different time periods in response to the statistical information of the idle time of the vehicle, and determining an upgrade time window based on the idle conditions;
[0070] It is understandable that potential upgrade time windows are prioritized based on factors such as idle time, historical trends, and user preferences. Time periods with long idle time, stable historical trends, and in line with user preferences are preferred as upgrade time windows. Before deciding on the upgrade time window, a conflict check is performed. Ensure that there is no conflict with other important tasks of the vehicle (such as scheduled travel, emergency tasks, etc.) during the selected time period. If the initially selected upgrade time window conflicts or does not meet other constraints (such as network bandwidth limitations, server maintenance time, etc.), it is adjusted as needed. When adjusting, priority is given to retaining time periods with longer idle time and higher user preferences. After the upgrade time window is finally determined, a decision output is generated. The output includes information such as the specific time period of the upgrade time window, the estimated time required for the upgrade, and the scope of impact of the upgrade, so that the upgrade operation can be automatically performed.
[0071] In some of the applications, the idle time evaluation and decision-making steps include responding to the statistical information of the vehicle's idle time, evaluating the idle situation of the vehicle in different time periods, and determining the upgrade time window based on the idle situation; based on the statistical information, calculating the proportion of idle days in the morning, afternoon and early morning time periods; comparing the calculated proportion of idle days with a preset threshold to determine whether the idle degree of each time period meets the upgrade requirements; based on the comparison result of the proportion of idle days, applying the preset decision logic to determine the applicable upgrade time window; and outputting the decision result as configuration information of the upgrade time window.
[0072] It is understandable that the specific time periods of morning, afternoon and early morning are first clarified. For example, the morning time period can be defined as 06:00-12:00, the afternoon time period as 12:00-18:00, and the early morning time period as 00:00-06:00 (or adjusted according to actual needs). From the vehicle usage data statistics, the number of idle days in the morning, afternoon and early morning time periods are extracted respectively. The number of idle days refers to the sum of the number of days that the vehicle is not in use during the time period. The proportion of idle days in each time period to the total number of days in the time period is calculated separately, that is, the proportion of idle days. The calculation formula is: proportion of idle days = (number of idle days / total number of days) * 100%. According to the needs and user preferences, the preset thresholds of the proportion of idle days are set for the morning, afternoon and early morning time periods respectively. The threshold reflects the minimum idle degree suitable for the upgrade operation in the time period. The calculated proportion of idle days is compared with the corresponding preset threshold. If the proportion of idle days is higher than or equal to the preset threshold, it is considered that the idle degree of the time period meets the upgrade requirements; otherwise, it does not meet.
[0073] According to business needs and system characteristics, a preset decision logic is formulated. This logic can compare the results of the proportion of idle days in each time period and comprehensively consider multiple factors (such as user preferences, network bandwidth, server load, etc.) to determine the most suitable upgrade time window.
[0074] According to the decision logic, the comparison results of the morning, afternoon and early morning time periods are comprehensively analyzed. If multiple time periods meet the upgrade requirements, the most appropriate upgrade time window is selected based on priority (such as user preference, system resource utilization, etc.); if only one time period meets the requirements, the time period is directly selected; if all time periods do not meet the requirements, the decision logic is used to determine whether to delay the upgrade or take other measures.
[0075] According to the decision result, the configuration information of the upgrade time window is generated, including the specific time period of the upgrade time window, the estimated upgrade duration, and the impact scope of the upgrade.
[0076] S103, a scheduling mode determination step, comprising assigning a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes the sending time and frequency of the upgrade instruction;
[0077] It is understandable that multiple upgrade scheduling modes are defined, each mode corresponding to a different upgrade instruction sending time and frequency, so as to adapt to the idle time distribution of different vehicles and user preferences.
[0078] For example, in the immediate mode, the upgrade instruction is sent immediately after the vehicle is detected to be idle for a long time. In the scheduled mode, the upgrade instruction is sent at a specific time point (such as early morning) during the vehicle's idle time period to reduce the impact on users. In the batch mode, the upgrade task is dispersed in multiple idle time periods, and the upgrade instruction is sent at a lower frequency to avoid system pressure caused by centralized upgrades.
[0079] Based on the idle time evaluation results, a suitable upgrade scheduling mode is matched for each vehicle. For the selected scheduling mode, the specific upgrade instruction sending time and frequency are set.
[0080] Sending time: For example, send the upgrade instruction between 01:00 and 03:00 in the morning to perform the upgrade during the user's rest time.
[0081] Sending frequency: Set the appropriate sending frequency according to the complexity of the upgrade task and the continuity of the vehicle's idle time. For example, in batch mode, send the upgrade command every two hours until the upgrade is completed.
[0082] In some of the applications, the scheduling mode determination step includes allocating a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, the scheduling mode includes the sending time and frequency of the upgrade instruction, traversing the scheduling mode library, the scheduling mode library contains a variety of preset scheduling modes and corresponding parameter settings; according to the idle time evaluation result, selecting a matching scheduling mode from the scheduling mode library; setting specific parameters for the selected scheduling mode, including the start and end time of the upgrade time window, the number of retries and the interval; applying the set scheduling mode and parameters to the vehicle, and preparing to send the upgrade instruction within the specified upgrade time window.
[0083] It is understandable that the dispatch mode library contains a variety of dispatch modes and their corresponding parameter settings applicable to different scenarios. The dispatch mode library is traversed to select a dispatch mode that matches the idle time characteristics of the vehicle from the dispatch mode library.
[0084] Set specific parameters for the selected scheduling mode, including:
[0085] Based on the idle time assessment results and user preferences, determine the specific time when the upgrade task can start and end. For example, set it to 02:00 to 04:00 in the morning.
[0086] Retry times: During the upgrade process, if the upgrade fails due to network failure, vehicle abnormality, etc., set the number of retries to try to resume the upgrade process. For example, set it to 3 times.
[0087] Retry interval: During the retry process, set the interval time to avoid system burden caused by frequent retries. For example, the interval between each retry is 10 minutes.
[0088] Apply the set scheduling mode and parameters to the specified vehicle, and prepare to send the upgrade command within the specified upgrade time window.
[0089] S104, a control and response step, includes executing an upgrade operation and reporting an upgrade result in response to the upgrade instruction within the specified upgrade time window.
[0090] It is understood that within the specified upgrade time window, the system continuously listens and is ready to receive upgrade instructions. When an upgrade instruction is received, the instruction is verified to ensure the legality, integrity and accuracy of the instruction. The verification process includes checking the source, format, signature and other information of the instruction to prevent the intrusion of illegal instructions.
[0091] After verification, the upgrade operation is performed according to the requirements of the upgrade instruction. This includes downloading the upgrade package, verifying the integrity of the upgrade package, installing the upgrade package, restarting the vehicle service, and other steps. During the execution process, the operation log is recorded in real time.
[0092] Download upgrade package: Download the upgrade package from the specified server or storage location and check whether any errors occur during the download process.
[0093] Verify the integrity of the upgrade package: Use hash values, digital signatures, and other methods to verify the integrity and authenticity of the upgrade package to ensure that the upgrade package has not been tampered with.
[0094] Install the upgrade package: After confirming that the upgrade package is correct, start installing the upgrade package, including updating the software, configuration files, database, etc.
[0095] Restart vehicle services: Some upgrades may require restarting vehicle services to apply new configurations or updates.
[0096] After the upgrade operation is completed, the upgrade results are reported, including whether the upgrade is successful, key events during the upgrade process, any errors or exceptions, and follow-up operation suggestions.
[0097] In some of the applications, the control and response steps include responding to upgrade instructions within a specified upgrade time window, executing upgrade operations and reporting upgrade results, sending upgrade instructions within a specified upgrade time window; responding to the upgrade instructions, confirming to check whether the current state is idle and whether the upgrade conditions are met; when the upgrade conditions are met, executing the upgrade operation, including downloading the upgrade package and installing the new version, and monitoring the upgrade progress and status during the upgrade process; when the upgrade is completed, reporting the upgrade results.
[0098] It is understood that at the beginning of the scheduled upgrade time window, the upgrade instruction is sent according to the schedule. After receiving the upgrade instruction, a condition confirmation is performed to check whether the current vehicle is in an idle state and meets the upgrade conditions. The condition confirmation process includes but is not limited to:
[0099] Idle status check: Use the vehicle status monitoring system to confirm whether the vehicle is currently not in use, that is, there is no driving record, the doors are closed, the engine is turned off, etc.
[0100] Upgrade condition verification: Check whether the vehicle battery level, network connection status, storage space, etc. meet the upgrade requirements. For example, the battery level must be higher than 30%, the network connection must be stable and the speed must meet the download requirements, and the storage space must have enough space to store the upgrade package.
[0101] When the upgrade conditions are confirmed to be met, the upgrade operation is executed. During the upgrade process, the upgrade progress and vehicle status are monitored in real time to ensure that the upgrade process proceeds smoothly. The monitoring content includes but is not limited to:
[0102] Upgrade progress: Displays information such as the size of the downloaded upgrade package and the installed update content to help users understand the upgrade progress.
[0103] Vehicle status: Monitor indicators such as battery power and network connection status to ensure that the vehicle status is stable during the upgrade process.
[0104] Abnormality detection: timely discover and handle abnormal situations that occur during the upgrade process, such as network interruption, upgrade package damage, etc., to ensure that the upgrade process is not affected.
[0105] When the upgrade operation is completed, the upgrade results will be reported. The report content includes but is not limited to:
[0106] Upgrade Success / Failure Status: Clearly indicates whether the upgrade completed successfully.
[0107] Upgrade details: Provides key information during the upgrade process, such as upgrade time, upgrade package version, and installed update content.
[0108] Exception Report: If an exception or error occurs during the upgrade process, a detailed exception report and possible solutions will be provided.
[0109] In some of these applications, users can remotely schedule or cancel upgrade operations before the specified upgrade time window; during the upgrade operation, the upgrade progress is sent to the user in real time, and the upgrade results are informed after the upgrade is completed, and the user is allowed to evaluate the upgrade effect.
[0110] It is understandable that before the designated upgrade time window begins, users are provided with the function of remotely reserving or canceling the upgrade operation. Users can operate through channels such as mobile APP and web platform.
[0111] Upgrade reservation: The user selects the date and time for the upgrade and confirms the upgrade content. The user's reservation information is recorded and corresponding preparations are made before the appointment time.
[0112] Cancel upgrade: If the user needs to cancel the scheduled upgrade operation for some reason, they can cancel it through the same channel before the scheduled time. After receiving the cancellation request, all preparation activities related to the upgrade operation will be stopped immediately, and the user will be notified of the successful cancellation.
[0113] During the upgrade process, the upgrade progress is monitored and recorded in real time. The upgrade progress is sent to the user in real time through SMS, APP push, email and other methods. The upgrade progress information includes but is not limited to: the current upgrade stage (such as downloading, installing), the proportion of completed tasks, the estimated remaining time, etc. For example, when the upgrade package is downloaded to 50%, the user can be notified through APP push that "your vehicle upgrade is in progress, the current download progress is 50%, please wait".
[0114] When the upgrade operation is completed, the user will be informed of the upgrade result. The notification methods also include SMS, APP push, email, etc. The upgrade result information should clearly indicate whether the upgrade is successful and provide necessary follow-up operation guidance (such as restarting the vehicle to apply the new version).
[0115] In addition, the function of users evaluating the upgrade effect is also provided. After receiving the upgrade result notification, users can evaluate the upgrade effect through the corresponding channels. The evaluation content may include satisfaction ratings (such as five-star reviews), text comments, etc. The user's evaluation information is collected for subsequent improvement of the upgrade process and service quality.
[0116] Combine the following Figures 2 to 5 The following describes some examples of the cloud-based vehicle upgrade scheduling method of the present invention in some applications:
[0117] In this embodiment, the vehicle-side reports the user's vehicle usage behavior data. When the A-side upgrade needs to be performed after the silent upgrade (equivalent to the B-side upgrade) is completed, the analysis conclusions of these data are used to determine the time window for the cloud-controlled vehicle computer to automatically execute the A-side upgrade. Within this time window, the A-side upgrade is completed by sending instructions through the cloud.
[0118] like Figure 3 As shown, the data class diagram and concept-related definitions are:
[0119]
[0120]
[0121] like Figure 2 As shown in the figure, the user behavior data reporting process is as follows:
[0122] When the car is started, a car shutdown event EventNode is generated and reported to the cloud;
[0123] When the car is started, a car ignition event EventNode is generated and reported to the cloud;
[0124] The cloud receives reported vehicle ignition / vehicle shutdown events and stores them in the cloud database.
[0125] like Figure 5 As shown, user behavior data analysis service:
[0126] Get the EventNode data set reported within 15 days (excluding the current day) map:Map<day:Sting,LIst <eventnode>>
[0127] Data processing 1:
[0128] Pair the two EventNodes in each list of the map, the first one: the car is turned off + the second one: the car is turned on. Pair them into a TimePeriod, and then generate a map2:Map <day:Sring,List <timeperiod>>
[0129] Pairing rules description:
[0130] 0. The EventNode reported every day forms an event chain.
[0131] 1. The reported EventNode data has obvious time sequence characteristics. In each car use cycle, a car ignition event and a car shutdown event will be generated successively. After a car shutdown event, a car ignition event will inevitably be generated. The algorithm here takes [car ignition event -> car ignition event]
[0132] 2. If there is a car usage event reported on the day, but the timestamp of the earliest car ignition EventNode on the day is greater than or equal to 12:00, it is considered that the car was not used in the morning. A car shutdown event is created at 10:00 to indicate that the morning period is idle.
[0133] 3. If there is a car usage event reported on the day, but the timeStamp of the last car shutdown EventNode of the day is less than or equal to 14:00, it is considered that the car was not used in the afternoon. Then a car ignition event is created at 17:00 to indicate that the afternoon time period is free.
[0134] 4. [Car shutdown event · > Car ignition event] indicates an idle time period when a car is not in use. It is collected to represent the user's daily car idle time, used to generate the user's car usage habits and predict the user's car-free time interval.
[0135] Data processing 2:
[0136] For each list in map2, process each TimePeriod and assign a value to the type field.
[0137] Filtering and assignment rules:
[0138] 1. The stopUseTimestamp of TimePeriod is 6:30 <= stopUseTimestamp <= 10:00 on the same day;
[0139] startUseTimestamp is 12:00 <= stopUseTimestamp <= 14:00 on the same day;
[0140] It is identified as the morning idle period, and type is set to 1;
[0141] 2. The stopUseTimestamp of TimePeriod is 10:00 <= stopUseTimestamp <= 14:00 on the same day;
[0142] If startUseTimestamp is 17:00 <= startUseTimestamp <= 19:30 on the same day, it is identified as the afternoon idle period, and type is set to 2;
[0143] 3. The stopUseTimestamp of TimePeriod is 6:30 <= stopUseTimestamp <= 10:00 on the same day;
[0144] If startUseTimestamp is 17:00<=startUseTimestamp<=19:30 on the same day, it is identified as an idle period in both the morning and afternoon, and type is set to 3;
[0145] 4. For other cases, the TimePeriod type field is assigned a value of 0.
[0146] Data processing 3:
[0147] For the processed map2, we get map3; Map<day:Sting,feature:String>.
[0148] Rules Description:
[0149] 1. Feature value: 0 unknown; 1 free in the morning; 2 free in the afternoon; 3 free in both the morning and afternoon;
[0150] 2. List of each day in map2 <timeperiod>List; if there is a TimePeriod of type=3, the feature of that day in map3 is set to 3;
[0151] 3. List of each day in map2 <timeperiod>List: If there is no TimePeriod of type=3, but there are both TimePeriods of type=1 and type=2, the feature of that day in map3 is set to 3;
[0152] 3. List of each day in map2 <timeperiod>List: If there is no TimePeriod of type=3, but there is only a TimePeriod of type=1 or type=2, the feature of that day in map3 is set to 1 or 2;
[0153] 4. List<TimePeriod> for each day in map2: If there is no TimePeriod of type=3, type=1, and type=2 at the same time, the feature is set to 0 in map3.
[0154] Data processing 4:
[0155] Based on the proportion, the cloud sends the A-side upgrade instruction to the user's car computer in the corresponding upgrade time window.
[0156] Rules Description:
[0157] 1. According to map3, within 15 days:
[0158] Idleness A: the percentage of days with idleness (type=2+type=3) in the afternoon time period;
[0159] Idleness B: the percentage of days with idleness (type=1+type=3) in the morning time period;
[0160] 2. If both idle conditions are >= 0.7, the [Morning Window] and [Afternoon Window] can both be controlled by the cloud to perform the A-side upgrade until the A-side upgrade is completed.
[0161] 3. If the values in both cases are < 0.7, perform the A-side upgrade in the [Midnight Window] cloud control.
[0162] 4. If only case A>0.7, the A side upgrade will be executed in the cloud control only in the [Morning Window] and [Early Morning Window].
[0163] 5. If only case B>0.7, the cloud control will only perform the A-side upgrade in the [afternoon window] and [early morning window].
[0164] The user-schedulable upgrade window type is returned to the service call point.
[0165] like Figure 4 As shown in the figure, the process triggered by the silent upgrade and the cloud control process are as follows:
[0166] The process associated with silent upgrade of the vehicle computer:
[0167] The user has turned on the [Upgrade when idle] switch. After the car receives the OTA upgrade task, it downloads the upgrade package and completes the silent upgrade. After the silent upgrade completion event is reported to the cloud, the cloud will call the user behavior data analysis service to obtain the user's cloud-controlled automatic A-side upgrade scheduling mode (ScheduleMode). According to the scheduling mode, the user is placed in the scheduling queue corresponding to the corresponding window type. There is a scheduling queue for each window type in the cloud. The specific rules for the scheduling mode are described as follows:
[0168] The scheduling mode is: MODE_NIGHT_ONLY: If 0:00 <= current time <= 3:00, the upgrade will be scheduled in the night window of the same day; if 3:00 < current time <= 24:00, the upgrade will be scheduled in the night window of the next day.
[0169] The scheduling mode is: MODE_NIGHT_AND_AM: If 0:00<current time<=3:00, it will be scheduled and upgraded in the night window of the same day; if 4:00<current time<=11:00, it will be scheduled and upgraded in the morning window of the same day; if 11:00<current time<=24:00, it will be scheduled and upgraded in the night window of the next day.
[0170] The scheduling mode is: MODE_NIGHT_AND_PM: If 0:00<current time<=3:00, schedule and upgrade it in the night window of the same day; if 4:00<current time<=15:00, schedule and upgrade it in the afternoon window of the same day; if 15:00<current time<=24:00, schedule and upgrade it in the night window of the next day.
[0171] Cloud sub-process 1:
[0172] When the cloud time reaches the time interval of the three upgrade time windows (i.e. the defined morning window, afternoon window, and night window), the cloud logic will be triggered once, that is, the cloud controls the logic of automatic A-side upgrade on the vehicle side. After the trigger, it will traverse the users in the dispatch queue and execute the query logic first to query whether the user is using the vehicle:
[0173] If the user is using the car, the system will retry every 5 minutes, with a retry count of 5 (retryNum starts from 0), until the user is no longer using the car, and then start the next step of logic. If the user is detected to be using the car in three retries, the user will be added to the next user-schedulable window.
[0174] If the car is not in use or the user is not using the car after retries, the cloud sends a command to the car to trigger an upgrade of side A.
[0175] Cloud sub-process 2:
[0176] The vehicle receives the command from the cloud to trigger the upgrade of side A and starts the upgrade and processing of the upgrade results. If the upgrade is successful, the upgrade success is reported to the cloud and the cloud scheduling process ends; if the upgrade fails and the rollback fails, the upgrade failure is reported to the cloud and the cloud scheduling process ends; if the upgrade fails and the rollback fails, the cloud retry scheduling logic is triggered; if the rollback fails and fails after one retry, the upgrade is considered to have failed. The upgrade failure is reported to the cloud and the cloud scheduling process ends.
[0177] This embodiment is described below in conjunction with application scenarios:
[0178] There are many office workers who drive to get off work, and User A is one of them. User A drives to get off work almost every weekday. Occasionally, he takes a nap in the morning on weekends and drives out in the afternoon.
[0179] When using the car, after the car system receives the task issued by the cloud, it has completed the silent upgrade. At this time, the car interface receives an upgrade prompt, and there are message notifications and red dot reminders. However, the user did not care about the upgrade task because he did not have time or did not want to deal with it. This caused the task to be delayed, and there was no time to deal with it later. When he remembered it, he was busy with other things, and forgot about it after getting in the car. The car computer can be used normally without upgrading, and gradually he forgot about the upgrade. And several subsequent versions were not upgraded due to this reason.
[0180] The above situation caused the version of user A's car system to be too old. At this time, a new version was released in the cloud. After the new version was downloaded to the local computer, the silent upgrade was completed. At this time, user A noticed the upgrade task and finally clicked the upgrade manually. However, due to the large version difference and the uncontrollable unknown control software version compatibility problem, the user's upgrade failed and the rollback failed. At this time, user A had to follow the prompt of the upgrade failure and go to the offline store for help.
[0181] At this point, user A's experience was very bad. The user upgrade operation was not executed, and the version difference was too large, resulting in the failure of the final upgrade operation and rollback failure, which also showed that the design of the car computer upgrade application itself was not perfect. And ultimately incurred after-sales costs.
[0182] At this time, adopting this solution can provide the following advantages:
[0183] Add a prominent and guided [Upgrade during Idle Time] switch so that users can smoothly enable the Upgrade during Idle Time function.
[0184] If [Upgrade when Idle] is turned on, the cloud will issue an upgrade task. After the car receives the task, downloads the upgrade package, and completes the silent upgrade, it will report to the cloud. The cloud will analyze the user's car usage behavior data and conclude that user A belongs to [Idle Situation A]: the car is not used in the morning or in the morning and afternoon. At this time, the cloud will automatically control the car to perform the A-side upgrade in the morning window when the user is not using the car, thereby automatically upgrading the car system and controller version to the latest for user A. There is no need to worry about the problems in the above case.
[0185] It reduces user operation requirements, avoids users delaying upgrades, forgetting to upgrade, and even avoiding problems that lead to after-sales costs, improves user experience, and increases the upgrade installation rate of new versions.
[0186] For the method steps disclosed in the above embodiments, the method steps are described as a series of action combinations for the purpose of simple description, but those skilled in the art should know that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.
[0187] like Figure 6 As shown, the present invention also provides a cloud-based vehicle upgrade scheduling system, comprising:
[0188] A data collection and processing module 201 is configured to generate statistical information about vehicle idle time in response to the collected vehicle usage data;
[0189] an idle time evaluation and decision module 202, configured to include, in response to the statistical information of the idle time of the vehicle, evaluate the idle conditions of the vehicle in different time periods, and determine the upgrade time window based on the idle conditions;
[0190] The scheduling mode determination module 203 is configured to allocate a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes the sending time and frequency of the upgrade instruction;
[0191] The control and response module 204 is configured to execute the upgrade operation and report the upgrade result in response to the upgrade instruction within the specified upgrade time window.
[0192] It is worth noting that although only some basic functional modules are disclosed in the embodiments of the present invention, it does not mean that the composition of the present system is limited to the above basic functional modules. On the contrary, what the present embodiment wants to express is that on the basis of the above basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with the prior art to form an infinite number of embodiments or technical solutions. In other words, the present system is open rather than closed. Just because the present embodiment only discloses individual basic functional modules, it cannot be considered that the protection scope of the claims of the present invention is limited to the disclosed basic functional modules. At the same time, for the convenience of description, the above devices are described in terms of functions and are described separately in various units and modules. Of course, when implementing the present invention, the functions of each unit and module can be implemented in the same or one or more software and / or hardware.
[0193] like Figure 7 As shown, the present invention also provides an electronic device, comprising: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the cloud-based vehicle upgrade scheduling method.
[0194] Figure 7 Schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 7 The electronic device provided in the embodiment of the present invention includes: one or more processors 710 and a storage device 720; the processor 710 in the electronic device may be one or more, Figure 7 A processor 710 is taken as an example; the storage device 720 is used to store one or more programs; the one or more programs are executed by the one or more processors 710, so that the one or more processors 710 implement the cloud-based vehicle upgrade scheduling method as described in any one of the embodiments of the present invention.
[0195] The electronic device may further include: an input device 730 and an output device 740 .
[0196] The processor 710, storage device 720, input device 730 and output device 740 in the electronic device can be connected via a bus or other means. Figure 7 The example of connecting through bus is taken in the following.
[0197] The storage device 720 in the electronic device is a computer-readable storage medium that can be used to store one or more programs, which can be software programs, computer executable programs, and modules, such as program instructions / modules corresponding to the cloud-based vehicle upgrade scheduling method provided in the embodiment of the present invention. The processor 710 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the storage device 720, that is, realizing the cloud-based vehicle upgrade scheduling method in the above method embodiment.
[0198] The storage device 720 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device, etc. In addition, the storage device 720 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the storage device 720 may further include a memory remotely arranged relative to the processor 710, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0199] The input device 730 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the electronic device. The output device 740 may include a display device such as a display screen.
[0200] The present invention also provides a computer-readable storage medium storing a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of a cloud-based vehicle upgrade scheduling method.
[0201] Specifically, the computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present embodiment, the computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.
[0202] The present invention also provides a vehicle, wherein the vehicle is provided with the cloud-based vehicle upgrade scheduling system as described above.
[0203] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.< / timeperiod> < / timeperiod> < / timeperiod> < / timeperiod>
Claims
1. A cloud-based vehicle upgrade scheduling method, characterized in that: include: a data collection and processing step, including generating statistical information regarding vehicle idle time in response to the collected vehicle usage data; An idle time evaluation and decision step, comprising evaluating the idle conditions of the vehicle in different time periods in response to the statistical information of the idle time of the vehicle, and determining an upgrade time window based on the idle conditions; a scheduling mode determination step, comprising assigning a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes a sending time and frequency of the upgrade instruction; The control and response step includes executing the upgrade operation and reporting the upgrade result in response to the upgrade instruction within the specified upgrade time window.
2. The cloud-based vehicle upgrade scheduling method according to claim 1, characterized in that: The data collection and processing step includes generating statistical information about vehicle idle time in response to the collected vehicle usage data, further comprising: Acquire vehicle usage data including a timestamp, wherein the vehicle usage data includes a vehicle ignition event and a vehicle shutdown event; Preprocessing the vehicle usage data to ensure the accuracy and completeness of the vehicle usage data; The pre-processed vehicle usage data is classified according to the dimensions of date and time period, and the number of days the vehicle is idle in each time period is calculated to generate the statistical information.
3. The cloud-based vehicle upgrade scheduling method according to claim 1, characterized in that: The idle time evaluation and decision step includes evaluating the idle conditions of the vehicle in different time periods in response to the statistical information of the idle time of the vehicle, and determining the upgrade time window based on the idle conditions, further including: Based on the statistical information, the proportion of idle days in the morning, afternoon and early morning time periods are calculated respectively; Compare the calculated idle days ratio with a preset threshold to determine whether the idleness level of each time period meets the upgrade requirements; According to the comparison result of the idle days ratio, a preset decision logic is applied to determine the applicable upgrade time window; The decision result is output as configuration information of the upgrade time window.
4. The cloud-based vehicle upgrade scheduling method according to claim 1, characterized in that: The scheduling mode determination step includes allocating a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes the sending time and frequency of the upgrade instruction, and further includes: Traversing a scheduling mode library, the scheduling mode library includes a plurality of preset scheduling modes and corresponding parameter settings; According to the idle time evaluation result, selecting a matching scheduling mode from the scheduling mode library; Setting specific parameters for the selected scheduling mode, including the start and end time of the upgrade time window, the number of retries and the interval; The set scheduling mode and parameters are applied to the vehicle, and the upgrade instruction is prepared to be sent within the specified upgrade time window.
5. The cloud-based vehicle upgrade scheduling method according to claim 1, characterized in that: The control and response step includes executing the upgrade operation and reporting the upgrade result in response to the upgrade instruction within the specified upgrade time window, and further includes: Sending the upgrade instruction within the specified upgrade time window; In response to the upgrade instruction, confirm and check whether the system is currently in an idle state and meets the upgrade conditions; When the upgrade conditions are met, the upgrade operation is performed, including downloading the upgrade package and installing the new version, and during the upgrade process, the upgrade progress and status are monitored; When the upgrade is completed, the upgrade results will be reported.
6. The cloud-based vehicle upgrade scheduling method according to claim 5, characterized in that: Also includes: In response to the specified upgrade time window, the user can remotely reserve or cancel the upgrade operation; During the upgrade operation, the upgrade progress is sent to the user in real time, and after the upgrade is completed, the upgrade result is informed, and the user is allowed to evaluate the upgrade effect.
7. A cloud-based vehicle upgrade scheduling system, characterized in that: include: a data collection and processing module configured to generate statistical information about vehicle idle time in response to the collected vehicle usage data; an idle time evaluation and decision module, configured to include, in response to the statistical information of the idle time of the vehicle, evaluate the idle conditions of the vehicle in different time periods, and determine the upgrade time window based on the idle conditions; a scheduling mode determination module, configured to allocate a corresponding upgrade scheduling mode to the vehicle based on the idle time evaluation result, wherein the scheduling mode includes a sending time and frequency of the upgrade instruction; The control and response module is configured to execute the upgrade operation and report the upgrade result in response to the upgrade instruction within the specified upgrade time window.
8. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method described in any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that: It stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the method described in any one of claims 1 to 6.
10. A vehicle, characterized in that: The vehicle is provided with a cloud-based vehicle upgrade scheduling system as described in claim 7.
