Vehicle upgrade state synchronization method, device and program product

Through the data communication and status synchronization request mechanism between the vehicle and the server, the status monitoring and orderly problems during the remote update of the vehicle are solved, and the accurate and orderly synchronization of the vehicle upgrade status is achieved, ensuring the stability of the vehicle during the update process. and driving ability.

CN118972251APending Publication Date: 2024-11-15BEIJING JIDU TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410946952.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-15
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

During the remote update of the vehicle, especially during the remote update of the firmware, it may cause the vehicle to lose its driving capability, and the prior art is difficult to effectively monitor and synchronize the vehicle upgrade status, resulting in inaccurate and poor orderliness of the update process.

Method used

Through data communication between the vehicle and the server, the synchronization of the vehicle upgrade status is achieved, and the state synchronization request and unique access control permissions are used to ensure the orderliness and accuracy of data updates, and overcome the impact of network transmission delay and parallel transmission.

Benefits of technology

Real-time monitoring and accurate synchronization of vehicle upgrade status is achieved, ensuring the orderliness and accuracy of data updates, and avoiding the risk of vehicle losing its driving ability during the update process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118972251A_ABST
    Figure CN118972251A_ABST
Patent Text Reader

Abstract

The invention provides a vehicle upgrade state synchronization method and device and a program product, and relates to the technical field of vehicles. The actual upgrade state information can be sent to the server in the upgrade process of the vehicle, so that the server can synchronize the upgrade state of the vehicle. When a server updates a vehicle upgrading state, synchronization information sent by a vehicle end can be converted into a state synchronization request of the vehicle upgrading state stored for the state of the server end, a target state request is determined from the state synchronization request, and a unique access permission is configured, so that data updating is carried out. Therefore, when the server synchronizes the vehicle upgrading state, the vehicle end data can be synchronized one by one in a similar serial mode, so that the influence of network transmission delay and parallel transmission is overcome, and the orderliness of data updating is ensured while the server receives the vehicle end data at a high speed. And meanwhile, the validity of the vehicle end data is judged during state updating, so that the accuracy of the vehicle upgrading state synchronization process is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle upgrade status synchronization method, device and program product. Background Art

[0002] As vehicle technology continues to develop, vehicle-related software is also constantly being updated. As a result, vehicles, especially electric vehicles, may need to be updated and maintained after leaving the factory.

[0003] To facilitate vehicle updates, OTA (Over-The-Air) technology can be used to remotely update vehicle software. From the perspective of update content, OTA can specifically include FOTA (Firmware Over-The-Air, firmware remote update) and SOTA (Software Over-The-Air, software remote update).

[0004] During the remote update of the vehicle, the actual update process of the vehicle is long, the vehicle will perform many operations, and errors may occur at any stage. Especially for the remote firmware update process, the update process may rewrite the driver of the vehicle-related equipment, and if there is a problem, the vehicle may lose its ability to drive.

[0005] Therefore, how to monitor the vehicle upgrade process is a technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0006] In view of this, the embodiments of the present application provide a vehicle upgrade status synchronization method, device and program product, which realize the synchronization of vehicle upgrade status through data communication between the vehicle side and the cloud, and then the vehicle upgrade process can be monitored in real time.

[0007] In a first aspect, the present application provides a vehicle upgrade status synchronization method. Applied to a server, the method includes: receiving at least one status synchronization request of a target vehicle, wherein the status synchronization request carries the actual upgrade status information of the target vehicle at the corresponding moment. Determine a target synchronization request from at least one status synchronization request, wherein the target synchronization request has unique access control authority to the vehicle upgrade status. When the target synchronization request meets the change requirements of the vehicle upgrade status of the target vehicle, update the vehicle upgrade status based on the target synchronization request, and send the actual upgrade status information to the user terminal corresponding to the target vehicle. When the target synchronization request does not meet the change requirements, reject / discard the target synchronization request and maintain the vehicle upgrade status.

[0008] In a second aspect, the present application provides an electronic device, comprising: a processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory. When the machine-readable instructions are executed by the processor, the processor executes the vehicle upgrade status synchronization method described in the first aspect.

[0009] In a third aspect, the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by an electronic device, the electronic device executes the vehicle upgrade status synchronization method of the first aspect.

[0010] The present application provides a method, device and program product for synchronizing vehicle upgrade status. During the upgrade process, the vehicle can send actual upgrade status information to the server so that the server can synchronize the vehicle upgrade status. When the server updates the vehicle upgrade status, the synchronization information sent by the vehicle side can be converted into a state synchronization request for the vehicle upgrade status stored in the server side state, and a target state request is determined therefrom and a unique access right is configured to perform data update. Thus, when synchronizing the vehicle upgrade status, the server can synchronize the vehicle side data one by one in a serial-like manner, thereby overcoming the influence of network transmission delay and parallel transmission, so that the server can ensure the orderliness of data update while receiving the vehicle side data at high speed. At the same time, the validity of the vehicle side data is judged when the status is updated, thereby ensuring the accuracy of the vehicle upgrade status synchronization process. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0012] Figure 1 It is an application scenario diagram of a vehicle communication system provided by an exemplary embodiment of the present application.

[0013] Figure 2 It is an exemplary flow chart of a vehicle upgrade status synchronization method provided by an exemplary embodiment of the present application.

[0014] Figure 3 It is an exemplary flow chart of a method for configuring unique access control permissions provided by an exemplary embodiment of the present application.

[0015] Figure 4 It is an exemplary flow chart of a vehicle upgrade status updating method provided by an exemplary embodiment of the present application.

[0016] Figure 5 It is an exemplary flow chart of a method for generating state synchronization information provided by an exemplary embodiment of the present application.

[0017] Figure 6 It is a schematic diagram of a vehicle status map provided by an exemplary embodiment of the present application.

[0018] Figure 7 It is a system module diagram of a vehicle upgrade status synchronization system provided by an exemplary embodiment of the present application.

[0019] Figure 8 It is a schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only 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 creative work are within the scope of protection of this application.

[0021] Application Overview

[0022] To achieve data exchange between the vehicle and the server, the vehicle can communicate with the Internet of Vehicles platform through the Internet of Vehicles cloud gateway. To further describe the communication process between the vehicle side (vehicle) and the server side (server), this application also provides an application scenario diagram of the vehicle communication system ( Figure 1 ).

[0023] like Figure 1 As shown, the vehicle communication system 100 may include a plurality of vehicles 110, a server 120 and a vehicle network cloud gateway 130. The vehicle 110 may be connected to the server 120 through the vehicle network cloud gateway 130.

[0024] The vehicle 110 may refer to a highly electrified smart car. The vehicle 110 may include at least one controller (such as an electronic control unit ECU, a central controller HPC, etc.), and integrate the vehicle's application and the drivers (also called firmware) of various on-board devices in the controller, so as to control the vehicle and various devices in the vehicle. The update of the application is generally called SOTA, and the update of the driver is generally called FOTA.

[0025] The server 120 may refer to a cloud server system that can provide support for vehicle-related services. The server 120 may be based on a cloud computing technology architecture. For example, the server 120 may be a server cluster related to vehicle services. When working, the server 120 may host vehicle data, provide vehicle remote control functions, support vehicle remote diagnosis and maintenance, and other services.

[0026] In particular, the server 120 can provide technical support for the upgrade process of the vehicle 110. Among them, the server 120 can at least push a suitable OTA upgrade package to the vehicle 110, so that the vehicle 110 performs an OTA upgrade based on the OTA upgrade package.

[0027] The Internet of Vehicles cloud gateway 130 may refer to a communication hub between the vehicle 110 and the server 120, and may serve as a collection, transmission, and processing center for vehicle data. The Internet of Vehicles cloud gateway 130 may generally integrate various communication protocols and technologies, including cellular networks, Wi-Fi, Bluetooth, etc., to communicate with the controller inside the vehicle 110 and the external server 120.

[0028] Based on the aforementioned vehicle communication system 100 , when the vehicle 110 performs a remote upgrade, information reflecting different processes can be generated during the upgrade process and sent to the server 120 via the IoV cloud gateway 130 .

[0029] However, the above process will have the following technical problems in actual implementation:

[0030] First, the Internet of Vehicles cloud gateway 130 will interfere with the real-time nature of the relevant data. In actual work, the server 120 is generally connected to multiple vehicles 110 at the same time, so when acquiring data, it is generally acquired in parallel. That is, the Internet of Vehicles cloud gateway 130 can serve as a data transfer, receive relevant data within a cycle, and send it to the server 120 at a preset cycle, so that the server 120 can process the relevant data sent by each vehicle in parallel. In this process, even if the time series data sent by the vehicle 110 will be disrupted by the process, multiple data with different time series can be received by the server 120 at the same time.

[0031] Second, the vehicle 110 generally includes a timestamp when generating the aforementioned information. However, considering the instability of the vehicle 110 itself during the upgrade process and the accuracy issues in actual applications (especially the timestamp often needs to be generated by the controller that is being flashed), the timestamp in the aforementioned information cannot accurately distinguish the timing of the related data, which may cause the server 120 to be unable to distinguish the timing of the related data.

[0032] In order to solve the above technical problems, the present application provides a vehicle upgrade status synchronization method, device and program product, which relate to the field of vehicle technology. During the upgrade process, the vehicle can send actual upgrade status information to the server so that the server can synchronize the vehicle upgrade status. Among them, when the server updates the vehicle upgrade status, the synchronization information sent by the vehicle side can be converted into a state synchronization request for the vehicle upgrade status stored in the server-side state, and a target state request is determined therefrom and a unique access right is configured to update the data. Therefore, when the server synchronizes the vehicle upgrade status, it can synchronize the vehicle-side data one by one in a serial-like manner, thereby overcoming the influence of network transmission delay and parallel transmission, so that the server can ensure the orderliness of data update while receiving the vehicle-side data at high speed. At the same time, the validity of the vehicle-side data is judged when the status is updated, thereby ensuring the accuracy of the vehicle upgrade status synchronization process.

[0033] Therefore, based on the above method, the vehicle communication system 100 may include a user terminal 140. The user terminal 140 may refer to a computing terminal (such as a mobile phone, tablet, computer, etc.) used by a user of the vehicle 110. The user terminal 140 may be connected to the server 120 and the vehicle 110 for communication.

[0034] In actual applications, considering that the vehicle OTA process is relatively long, the user of the vehicle 110 can leave the vehicle for updating. At this time, the vehicle 110 will disconnect directly from the user terminal 140, thereby receiving relevant data of the vehicle 110 through the server 120.

[0035] Various non-limiting embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0036] Exemplary vehicle upgrade status synchronization method

[0037] Figure 2 is an exemplary flow chart of a vehicle upgrade status synchronization method provided by an exemplary embodiment of the present application. In some embodiments, Figure 2 The process P200 shown may be executed by the server 120 .

[0038] like Figure 2 As shown, the method shown in P200 may include the following steps:

[0039] S210: Receive at least one status synchronization request of a target vehicle.

[0040] S220. Determine a target synchronization request from at least one status synchronization request.

[0041] S230: When the target synchronization request satisfies the change requirement of the vehicle upgrade status of the target vehicle, the vehicle upgrade status is updated based on the target synchronization request, and the actual upgrade status information is sent to the user terminal corresponding to the target vehicle.

[0042] S240: When the target synchronization request does not meet the change requirements, reject / discard the target synchronization request and maintain the vehicle upgrade status.

[0043] In the aforementioned S210, the status synchronization request may reflect the vehicle-side communication information reflecting the upgrade status sent by the vehicle to the server during the upgrade process. The status synchronization request may carry the actual upgrade status information of the target vehicle at the corresponding time. That is, during the upgrade process, the vehicle may generate vehicle-side communication information based on the current actual upgrade status and send it to the server to inform the current upgrade status of the vehicle, and the corresponding time may refer to the generation time of the corresponding vehicle-side communication information.

[0044] Vehicle-side communication information may refer to information sent by the vehicle to the server. During the communication process between the vehicle and the server, the server can generally provide the required services for multiple vehicles. That is, the server can simultaneously receive the vehicle-side communication information sent by each vehicle, and provide corresponding services to the vehicle in response to the vehicle-side communication information. For example, the server can simultaneously receive upgrade requests, log information, online service requests (such as high-precision map services), etc. from each vehicle, and provide corresponding services for them.

[0045] In some embodiments, considering that in subsequent steps, the data stored at the server can be processed based on the status synchronization request, the aforementioned status synchronization request can be understood as a process generated based on the vehicle-side communication information for adjusting the corresponding vehicle upgrade status at the server, and the process can request to change the vehicle upgrade status stored at the server.

[0046] Considering the above Figure 1 The communication situation between the vehicle end and the server end shown in the figure is combined with the corresponding relationship between the state synchronization request and the vehicle end communication information, and the above S210 can be implemented based on the following steps in the actual execution process:

[0047] First, the vehicle-side communication information of each vehicle is received in parallel through the gateway. In order to distinguish each vehicle, the vehicle-side communication information may at least include specific information content and vehicle identification information.

[0048] Next, the vehicle-side communication information of the target vehicle is determined from the vehicle-side communication information of each vehicle based on the vehicle identification information.

[0049] Finally, a status synchronization request of the target vehicle is generated based on the vehicle-side communication information of the target vehicle.

[0050] In the above process, the vehicle identification information may refer to relevant information that can uniquely reflect the vehicle. For example, the vehicle identification information may be information such as the frame number, the motor number (or the engine number), or other identification information preset by the server (such as the vehicle ID). The vehicle identification information may be recorded in the vehicle-side communication information so that the server can identify the vehicle that sent the vehicle-side communication information based on the vehicle identification information.

[0051] It should be noted that the aforementioned target vehicle can be a general reference to a certain vehicle to be upgraded, and can be specifically implemented in each vehicle in actual work. For example, during work, it can first detect that a vehicle is being upgraded based on the vehicle-side communication information (such as an uploaded upgrade request), and then determine the vehicle identification information (such as vehicle ID) in the corresponding information as the target vehicle, so as to execute subsequent steps.

[0052] The actual upgrade status information may reflect the upgrade status change of the target vehicle during the upgrade process, wherein the actual upgrade status information may be specifically characterized as the stage or stage progress of the target vehicle during the upgrade process.

[0053] Taking the FOTA process as an example, from an overall perspective, the FOTA process includes two major stages: downloading the FOTA upgrade package and flashing the FOTA upgrade package. In the stage of downloading the FOTA upgrade package, different stage progresses can also be included, such as download reservation, download execution, and download processes with different completion ratios. In the stage of flashing the FOTA upgrade package, different stage progresses can also be included, such as appointment execution and flashing the upgrade packages related to each domain controller.

[0054] In some embodiments, the actual upgrade status information can be described by the currently executed upgrade operation and / or the specific upgrade status of the target vehicle. For example, the upgrade status change information can be represented by information such as "body domain controller program flashing completed", "car system flashing is being executed, progress 25%", etc. The specific presentation form of the actual upgrade status information can be adjusted according to actual needs, and is generally presented as the coded value of each upgrade status.

[0055] In some embodiments, considering that the aforementioned vehicle-side communication information is received in parallel, that is, the gateway can periodically cache the vehicle-side communication information during data transmission, and then send it to the server. At this time, the vehicle-side communication information within one cycle may include multiple vehicle-side communication information of the target vehicle. In order to achieve a one-to-one response to the vehicle-side communication information, the aforementioned status synchronization request can correspond to the vehicle-side communication information one by one. Among them, the information content of the vehicle-side communication information at least includes the actual upgrade status information of the target vehicle at the corresponding time, then the status synchronization request can carry the actual upgrade status information of the target vehicle at the corresponding time, so as to request to update the vehicle upgrade status stored at the server based on the actual upgrade status information.

[0056] In the aforementioned S220, the vehicle upgrade status can reflect the server's perception of the target vehicle upgrade process, that is, the vehicle upgrade status can be updated in real time based on the aforementioned vehicle-side communication information, so that the server can perceive the actual upgrade status of the target vehicle in real time and inform the corresponding user terminal.

[0057] In some embodiments, the aforementioned vehicle upgrade status can be represented as data in a specific format, so that the actual value of the data reflects the actual upgrade status of the target vehicle perceived by the server. Therefore, the aforementioned status synchronization request can be understood as an edit request for the vehicle upgrade status data, and specifically, a request can be made to change the specific value of the vehicle upgrade status so that the value is consistent with the actual upgrade status information corresponding to the request.

[0058] The target synchronization request may refer to a state synchronization request selected and executed from among the state synchronization requests. That is, in subsequent steps, the vehicle upgrade state at the server may be updated based on the target synchronization request.

[0059] In some embodiments, to avoid data conflicts caused by the simultaneous execution of multiple state synchronization requests, in this application, the aforementioned target synchronization request can be configured with a unique access control permission for the vehicle upgrade state. That is, the state synchronization request with the unique access control permission among the state synchronization requests is the target synchronization request.

[0060] The unique access control permission can refer to two levels of meaning. Among them, unique can mean that only one state synchronization request can have this permission. The access control permission can refer to the permission to access and change the actual data of the vehicle upgrade status. That is, when the target synchronization request has the unique access control permission, the actual value of the vehicle upgrade status can be changed.

[0061] In some embodiments, the determination process of the target synchronization request can be performed based on the occupation of the unique access control authority. Among them, when the unique access control authority is not occupied by the state synchronization request (in an idle state), a target synchronization request can be determined from each state synchronization request and the authority can be configured. When the unique access control authority is occupied (in an occupied state), each state synchronization request can be controlled to wait until the authority is idle.

[0062] That is, in response to the unique access control authority being in an idle state, a target synchronization request can be determined from at least one state synchronization request, and a unique access control authority can be configured for the target synchronization request. In response to the unique access control authority being in an occupied state, at least one state synchronization request is controlled to wait until the unique access control authority is in an idle state. For the specific configuration process of the unique access control authority, please refer to Figure 3And the related descriptions are not repeated here.

[0063] In some embodiments, the target synchronization request may be determined from each state synchronization request based on a preset selection rule. For example, a state synchronization request may be randomly selected as the target synchronization request. For another example, it may be performed based on the time sequence of the state synchronization requests. That is, the response sequence of at least one state synchronization request may be determined based on the acquisition time and / or built-in time information of at least one state synchronization request. The target synchronization request is determined from at least one state synchronization request based on the response sequence.

[0064] In some embodiments, when determining the target synchronization request based on the response order, each state synchronization request can be directly selected in chronological order to reduce the probability of the target synchronization request being inconsistent with the vehicle upgrade state. In some embodiments, when determining the target synchronization request based on the response order, the newly acquired state synchronization request can also be responded to first to enhance the real-time nature of the vehicle upgrade state.

[0065] When updating the vehicle upgrade status of the target vehicle based on the target synchronization request, it can be executed based on the relationship between the target synchronization request and the change request. Among them, the change requirements can reflect the change relationship / change logic between different stages in the upgrade process. For example, when the stage progress of the current stage is 51%, the progress of the same stage of the continued upgrade should not be less than 51%. The execution order of the nodes is similar to the aforementioned logic. Based on the specific content of the OTA upgrade package, the change logic of each node / stage can be pre-determined to construct the update conditions of each state.

[0066] The aforementioned S230 and S240 can be understood as two matching results of the target synchronization request and the change request. Among them, S230 can reflect the situation where the target synchronization request matches the change request (that is, the target synchronization request meets the change request). At this time, the vehicle upgrade status can be updated based on the target synchronization request and the user can be informed (such as sending it to the user terminal). S240 can reflect the situation where the target synchronization request does not match the change request (that is, the target synchronization request does not meet the change request). At this time, the request can be refused to execute, thereby ensuring that the vehicle upgrade status remains unchanged.

[0067] Considering the network transmission environment, the above determination of the update condition can be understood as satisfying the change logic of different stages, and it is not required to transfer from one node to the nearest subsequent node of the node. For example, if the above progress is 51%, the new status change information can be any value greater than 51% or an indication of entering the next stage. It is not required that the new status change information must be 52%.

[0068] In some embodiments, the change request and the determination of the change request may be performed based on the execution order requirements of the vehicle upgrade status, that is, the determination steps of the target synchronization request and the change request may be performed before the aforementioned S230 and S240.

[0069] Specifically, the target vehicle upgrade state of the target synchronization request can be determined first. Then, it is determined whether the target vehicle upgrade state meets the execution order requirement of the vehicle upgrade state, wherein the execution order requirement reflects the state transition order of multiple vehicle upgrade states of the target vehicle during the upgrade process. If so, it is determined that the target synchronization request meets the change requirement. If not, it is determined that the target synchronization request does not meet the change requirement. Thus, the aforementioned S230 and S240 are executed accordingly.

[0070] In some embodiments, the execution order requirement can reflect the order of changes in various states of the vehicle during the upgrade process. In the above judgment process, it can be directly judged whether the actual upgrade state information (recorded as the target vehicle upgrade state) contained in the target synchronization request is the subsequent state of the vehicle upgrade state in the server in the execution order requirement. If so, it is determined that the target synchronization request meets the change requirement. If not, it is determined that the target synchronization request does not meet the change requirement.

[0071] In some embodiments, the aforementioned execution order requirement can be represented as a state machine, and the aforementioned judgment process can also be implemented by state reversal of the state machine. For details, see Figure 4 and its related description.

[0072] In the aforementioned S230, after the target synchronization requests to update the vehicle upgrade status, the actual upgrade status information can be sent to the user terminal corresponding to the target vehicle. The value of the vehicle upgrade status can reflect the actual situation of the vehicle during the actual upgrade process. When the value of the vehicle upgrade status changes, it can indicate the change in the actual upgrade status of the vehicle. At this time, corresponding information can be generated to be sent to the user terminal.

[0073] In some embodiments, relevant information can be synchronized to the user terminal in the form of a message (such as state synchronization information). To avoid disorder at the user terminal again, a timestamp (i.e., high-precision time information) can be added to the message. That is, in response to the value change of the vehicle upgrade state, state synchronization information can be generated based on the changed vehicle upgrade state. The state synchronization information is sent to the user terminal so that the user terminal can obtain the vehicle upgrade state and its update time. In some embodiments, the recognition of the above value change can be achieved by monitoring the parameter of the vehicle upgrade state. For details, please refer to Figure 5 and its related description.

[0074] In some embodiments, the server may also respond to an abnormality in the target vehicle during the upgrade process (such as an upgrade failure) and synchronize it to the user terminal. Considering the rescue problem, when the server detects that the target vehicle fails to upgrade, it can further determine whether the vehicle can work normally (such as whether it has the ability to drive) and synchronize it to the user terminal to perform appropriate rescue. That is, in response to the upgrade failure of the target vehicle, the driving ability of the target vehicle can be determined. Then, notification information is generated based on the driving ability and sent to the user terminal of the target vehicle.

[0075] Based on the aforementioned P200, the vehicle can send actual upgrade status information to the server during the upgrade process so that the server can synchronize the vehicle upgrade status. When the server updates the vehicle upgrade status, the synchronization information sent by the vehicle can be converted into a state synchronization request for the vehicle upgrade status stored in the server state, and a target state request is determined from it and a unique access right is configured to perform data update.

[0076] Therefore, when synchronizing the vehicle upgrade status, the server can synchronize the vehicle-side data one by one in a similar serial manner, thereby overcoming the influence of network transmission delay and parallel transmission, so that the server can receive the vehicle-side data at high speed while ensuring the orderliness of data update. At the same time, the validity of the vehicle-side data is judged when the status is updated, thereby ensuring the accuracy of the vehicle upgrade status synchronization process.

[0077] Example of a method for configuring unique access control permissions

[0078] In some embodiments, in order to achieve the uniqueness of the unique access control authority, it can be ensured that only one status synchronization request is configured with the authority by means of identification information. That is, an identification data can be constructed in the target storage area to reflect the occupation request of the unique access control authority. That is, if the occupation identification is written in the target storage area (such as configuring the value of the identification data to a specific value), it can be determined that the unique access control authority is called, and other synchronization requests cannot call the access control authority of the vehicle upgrade status.

[0079] Based on the above-mentioned setting of the unique access control authority, in order to further illustrate the process of configuring the unique access control authority for the target synchronization request, the present application also provides a configuration method for the unique access control authority ( Figure 3 ).

[0080] like Figure 3 As shown, Figure 3 The process P300 in may include the following steps:

[0081] S310: Based on the target synchronization request, write an occupation identifier of the unique access control authority of the target synchronization request in the target storage area.

[0082] S320: Configure access control permissions for vehicle upgrade status for the target synchronization request.

[0083] In some embodiments, S310 may be executed based on the absence of an occupation mark in the target storage area, that is, the unique access control permission is configured for the target synchronization request only when the unique access control permission is not called.

[0084] In some embodiments, in order to distinguish different requests from different vehicles, the occupation flag can be constructed based on the vehicle identification information of the target vehicle, and its specific value can correspond to the number of the state synchronization request. For example, when a value is written within the data range corresponding to the occupation flag, it can be determined that the unique access control authority is occupied, and its specific value can correspond to the request number of the request.

[0085] In some embodiments, based on the occupancy identifier, each state synchronization request for the unique access control authority can also be implemented through an occupancy identifier write request. That is, the corresponding process of each state synchronization request may include a state synchronization request and an occupancy identifier write request. Among them, the occupancy identifier write request can be used to request to write the occupancy identifier for the unique access control authority in the target storage area. When the occupancy identifier write request is executed, the state synchronization request of the process serves as a target synchronization request.

[0086] In some embodiments, when there is an occupied mark in the target storage area, the occupied mark write request can be rejected and periodically regenerated until the request is responded to, so that the state synchronization request of the corresponding process is used as the target synchronization request. Alternatively, when there is an occupied mark in the target storage area, the aforementioned occupied mark write request can also continue to wait until the request is responded to.

[0087] Considering that the occupation flag of the unique access control permission can only be written by one status synchronization request, the uniqueness of the unique access control permission can be guaranteed. When configuring the unique access control permission, the target synchronization request access control permission can be directly granted. For example, the data address of the vehicle upgrade status can be provided to the target synchronization request to achieve access and overwrite of the data.

[0088] In some embodiments, after the vehicle upgrade status is updated based on the target synchronization request, the unique access control authority can be released so as to select and execute the next target synchronization request. Then the aforementioned P300 may further include the following steps:

[0089] S330: In response to the target synchronization request being executed, the access control authority of the target synchronization request is released and the related process of the target synchronization request is ended.

[0090] S340: Remove the occupation mark of the target synchronization request from the target storage area.

[0091] In some embodiments, the aforementioned S330 can be implemented by directly terminating the corresponding progress of the corresponding target synchronization request. Thus, if the unique access control authority is not occupied by the process, its occupation flag can be cleared to select the next target synchronization request.

[0092] In some embodiments, the aforementioned S340 can be executed based on whether a process (or request) corresponding to the actual value of the occupation identifier exists. That is, when the process is terminated based on the aforementioned S330, there is no corresponding process for the actual value of the occupation identifier, and the value in the occupation identifier can be cleared to make the unique access control permission idle.

[0093] As an alternative embodiment, the unique access control authority can also be roughly understood as a distributed lock. That is, when a certain data (vehicle upgrade status) is called by multiple processes (i.e., various status synchronization requests), a distributed lock can be configured to avoid call conflicts so that only the process that obtains the distributed lock (i.e., the target synchronization request with the unique access control authority) can adjust the data. The unique access control authority can also be allocated and configured with reference to the configuration method of the distributed lock, which will not be elaborated here.

[0094] Exemplary state change information update method

[0095] To further illustrate the process of changing the upgrade status, the present application also provides an upgrade status update method ( Figure 4 ).

[0096] like Figure 4 As shown, in Figure 4 The process P400 may include the following steps:

[0097] S410: Determine an upgrade state machine of the target vehicle based on a state transition sequence configuration of multiple vehicle upgrade states of the target vehicle during the upgrade process.

[0098] S420: Determine whether the target vehicle upgrade state satisfies the reversal condition of the upgrade state machine in the vehicle upgrade state.

[0099] S430: If yes, determine whether the target synchronization request meets the execution order requirement.

[0100] S440: If not, it is determined that the target synchronization request does not meet the execution order requirement.

[0101] In the aforementioned S410, the state machine may be a mathematical model for describing the transition and behavior of an object between different states. The state machine consists of a set of states, events, and transitions, and can be used to describe the behavior of an object responding to events and performing state transitions in different states. In the state machine, the state represents the state of the object, the event represents the triggering event that causes the state transition, and the transition represents the object transitioning from one state to another after receiving a specific event.

[0102] In some embodiments, each state of the state machine can be configured based on the state identifier, and the state transition process can be configured based on the theoretical execution order, so as to determine the transition conditions under each state. The state identifier can be a quantitative identifier of the stage / stage process / node in the aforementioned upgrade process, and different upgrade stages can be identified by different state identifiers.

[0103] In some embodiments, the aforementioned theoretical execution sequence can be described by graph data. Among them, each state identifier can be used as a node in the graph data, and its state transition sequence can be configured as a directed edge in the graph data, so that the aforementioned judgment process is characterized by finding a link from the current state identifier to the candidate state identifier in the graph data. If it exists, the condition is met, and if it does not exist, it is not met. In this way, the torsion conditions of the aforementioned upgrade state machine in each state can be constructed.

[0104] In the aforementioned S420, the actual state of the upgrade state machine may change with the update of the vehicle upgrade state, thereby reflecting the torsion condition in the current vehicle upgrade state. The torsion condition may reflect the condition that changes from the current vehicle upgrade state. For example, the torsion condition may include that the target vehicle upgrade state in the target synchronization request should not be a state before the current vehicle upgrade state.

[0105] The change of the upgrade state machine can be controlled by determining whether the upgrade state of the target vehicle meets the reversal condition. When the target synchronization request meets the execution order requirement, it can be determined that the target synchronization request meets the change requirement of the vehicle upgrade state of the target vehicle and the target vehicle upgrade state needs to be used as the current state of the upgrade state machine. When the target synchronization request does not meet the execution order requirement, it can be determined that the target synchronization request does not meet the change requirement and the current state of the upgrade state machine remains unchanged.

[0106] It should be noted that the state transition between different state identifiers may include other conditions in addition to the order, so the state reversal can also be based on other relevant information for collaborative judgment. For example, when the FOTA upgrade package is started to download at a specific time, manual confirmation is required at the target vehicle (such as interactive operation at the user terminal). When changing the corresponding upgrade state, the relevant data at the user terminal can also be combined for comprehensive judgment.

[0107] Based on the above process, the upgrade status of the vehicle can be effectively synchronized. For example, the vehicle sends three actual upgrade status information to the server (recorded as A, B, and C in sequence). Each actual upgrade status information is carried in a status synchronization request. Due to network delays and the influence of the Internet of Vehicles cloud gateway, the order of the actual upgrade status information may change when it arrives at the server. For example, the order in which the three actual upgrade status information arrive at the server may be A, C, and B; or A and C arrive concurrently, and B arrives later.

[0108] In the embodiment of the present invention, the three requests can be executed sequentially by using the unique access control authority of the vehicle upgrade status and the upgrade state machine. That is, when the server processes the three requests in sequence, it uses the upgrade state machine to check the state change. If it finds that C to B does not satisfy the state machine state reversal, it will discard it when processing the B request. When the cloud synchronizes to these two states, it will push them to the APP of the user terminal asynchronously in sequence, and a timestamp will be added when pushing.

[0109] Exemplary state synchronization information generation method

[0110] In some embodiments, in order to respond to the value change of the upgrade status in real time, the upgrade status can be monitored to generate a status synchronization request sent to the user terminal. Therefore, the present application also provides a status synchronization information generation method ( Figure 5 ).

[0111] like Figure 5 As shown, Figure 5 The process P500 in may include the following steps:

[0112] S510: Update the vehicle upgrade status based on the actual upgrade status information in the target synchronization request, and generate an update record of the vehicle upgrade status in a monitoring database of the vehicle upgrade status.

[0113] S520: In response to a new update record in the monitoring database, generate status synchronization information based on the latest update record in the monitoring database.

[0114] S530: Send status synchronization information to the user terminal.

[0115] In some embodiments, a monitoring database can be constructed based on the aforementioned upgrade status so that the monitoring database changes synchronously with the vehicle upgrade status. For example, the aforementioned monitoring database can be configured as log data. Exemplarily, the monitoring database can be a binlog log in database technology.

[0116] Based on the aforementioned synchronous update, when the value of the vehicle upgrade status changes, the monitoring database can record the new content, thereby generating status synchronization information according to the newly added update record. Among them, the status synchronization information can include the updated vehicle upgrade status and update time information.

[0117] In some embodiments, considering that the server may perform upgrade status synchronization of multiple vehicles at the same time, in order to provide appropriate status synchronization information to the user terminal, the aforementioned update record can be configured as time series data based on vehicle identification information. That is, when generating status synchronization information, it can be generated based on vehicle identification information, so that the status synchronization information reflects the time series changes of the corresponding vehicle upgrade status.

[0118] In actual implementation, the above update records can be configured as Kafka messages based on binlog logs. Considering the ordered nature of Kafka messages with single partition attributes, the vehicle ID can be used as the partition attribute value (partition key) to ensure that the Kafka message is time series data based on the vehicle ID.

[0119] In some embodiments, the state change message can be cached, so that appropriate information can be selected for packaging to generate state synchronization information. For example, the current state identifier can be converted into text information, and the state synchronization information can be generated in combination with the time signal (such as a timestamp) of the corresponding state change message to be presented in the user terminal.

[0120] Vehicle upgrade status synchronization process example

[0121] To further illustrate the vehicle upgrade status synchronization process, this application takes the complete process of FOTA as an example to illustrate the aforementioned process.

[0122] Figure 6 It is a vehicle status map provided by an exemplary embodiment of the present application.

[0123] like Figure 6 As shown, the vehicle FOTA process may include multiple states (nodes in the graph), and there is a sequential transfer relationship between each state.

[0124] For example, the vehicle FOTA process may include the appointment push status, the start download status, the download completion status, the waiting upgrade status, the execution upgrade status, and the upgrade success status. Each status may also include sub-states of different stages of the process. For example, the execution upgrade status may include multiple controller flash completion states reflecting the flash process of each controller.

[0125] In the actual FOTA process, the server can push the FOTA upgrade package first. After the target vehicle responds and before the agreed download time, the upgrade status of the target vehicle can be the scheduled push status. After the scheduled time is reached, the server can transmit the FOTA upgrade package to the vehicle, so that the vehicle is in the start download state until the download verification is completed and the download is completed.

[0126] After completing the download of the FOTA upgrade package, the user terminal / vehicle can make an appointment for the upgrade time so that the upgrade can start after the arrival time. Before this time, the vehicle can be in a waiting for upgrade state, after this time it can be in an execution generation state, and after completing the upgrade it can be in an upgrade success state.

[0127] Taking into account the abnormal situations in FOTA, the above-mentioned map may also include FOTA cancellation state, first failure state and second failure state. Among them, the first failure state can reflect that FOTA fails but does not affect the vehicle's driving ability, and the second failure state can reflect that FOTA fails but affects the vehicle's driving ability (need to dispatch rescue). Among them, the abnormal situation before executing the upgrade package flash can be turned to the aforementioned first failure state, and the abnormality during the flash process may be turned to the second failure state.

[0128] During the FOTA process, the states between the aforementioned graphs (as well as the invisible sub-states) need to flow in the direction of the arrows on the edges of the graphs, and the states are irreversible.

[0129] The push success is the starting state, and the FOTA failure-driving, FOTA failure-unable to drive, FOTA success, and FOTA cancellation are the ending states. For each FOTA process, all states are irreversible and can only be changed according to the state reversal in the state machine.

[0130] Exemplary Electronic Devices and Systems

[0131] Combination of the above Figures 1 to 6 , describes the method embodiment of the present application in detail, and the device embodiment of the present application is described in detail below. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the part not described in detail can refer to the previous method embodiment.

[0132] The present application also provides a vehicle upgrade status synchronization system, including a module for implementing the vehicle parameter polishing method provided by the present application. Figure 7 As shown, Figure 7 700 is a system module diagram of a vehicle upgrade status synchronization system provided by an exemplary embodiment of the present application. The vehicle upgrade status synchronization system 700 provided by the present application may include an acquisition module 710, a calling module 720, an execution module 730 and a discarding module 740.

[0133] The acquisition module 710 may be configured to receive at least one status synchronization request of a target vehicle, wherein the status synchronization request carries actual upgrade status information of the target vehicle at a corresponding moment.

[0134] The calling module 720 may be configured to determine a target synchronization request from at least one status synchronization request, wherein the target synchronization request has a unique access control authority to the vehicle upgrade status.

[0135] The execution module 730 may be configured to update the vehicle upgrade status based on the target synchronization request when the target synchronization request satisfies the change requirement of the vehicle upgrade status of the target vehicle, and send the actual upgrade status information to the user terminal corresponding to the target vehicle.

[0136] The discard module 740 can be used to reject / discard the target synchronization request and maintain the vehicle upgrade status when the target synchronization request does not meet the change requirements.

[0137] The present application also provides a server, which may include the vehicle upgrade status synchronization system provided by the present application, and can execute the vehicle upgrade status synchronization method provided by the present application. The server provided by the present application may be a distributed server as a server of the vehicle.

[0138] The present application also provides a vehicle, which may involve the vehicle upgrade status synchronization system provided in the present application, and may serve as an upgrade subject (target vehicle) and participate in the aforementioned upgrade status synchronization method. The vehicle provided in the present application may be a fully automatic driving vehicle or a semi-automatic driving vehicle, and may involve Figure 1 The specific vehicle model provided in this application can be a car, a commercial vehicle, a truck, a bus, a tram, etc.

[0139] The present application also provides an electronic device, such as Figure 8 The electronic device 800 provided in the present application includes a memory 810, a processor 820, and an input / output interface 830. The memory 810, the processor 820, and the input / output interface 830 are connected through an internal connection path, the memory 810 is used to store instructions, and the processor 820 is used to execute the instructions stored in the memory 810 to control the input / output interface 830 to receive input data and information, and output data such as operation results.

[0140] It should be understood that in the embodiment of the present application, the processor 820 can adopt a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits to execute relevant programs to implement the technical solution provided in the embodiment of the present application.

[0141] The memory 810 may include a read-only memory and a random access memory, and provides instructions and data to the processor 820. A portion of the processor 820 may also include a nonvolatile random access memory. For example, the processor 820 may also store information on the device type.

[0142] During the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 820 or the instruction in the form of software. The control method of the vehicle disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor execution, or it can be completed by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 810, and the processor 820 reads the information in the memory 810 and completes the steps of the above method in combination with its hardware. To avoid repetition, it is not described in detail here. The present application also provides a computer program product, including a computer program / instruction. When the computer program / instruction processor in the computer program product provided by the present application is executed, the control method of the vehicle provided by the present application can be implemented.

[0143] It should be understood that the term "and / or" in this article is only a description of the association relationship of the 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.

[0144] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0145] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units 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 through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0146] 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.

[0147] 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.

[0148] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, a core network device, operation and maintenance management (operation administration and maintenance, OAM) or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

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

Claims

1. A vehicle upgrade status synchronization method, characterized in that: Applied to a server, the method comprises: Receiving at least one state synchronization request of a target vehicle, wherein the state synchronization request carries actual upgrade state information of the target vehicle at a corresponding moment; Determine a target synchronization request from the at least one status synchronization request, wherein the target synchronization request has a unique access control authority to the vehicle upgrade status; When the target synchronization request satisfies the change requirement of the vehicle upgrade state of the target vehicle, updating the vehicle upgrade state based on the target synchronization request, and sending the actual upgrade state information to the user terminal corresponding to the target vehicle; When the target synchronization request does not meet the change requirement, the target synchronization request is rejected / discarded and the vehicle upgrade state is maintained.

2. The vehicle upgrade status synchronization method according to claim 1, characterized in that: The determining a target synchronization request from the at least one state synchronization request comprises: In response to the unique access control authority being in an idle state, determining a target synchronization request from the at least one state synchronization request, and configuring the unique access control authority for the target synchronization request; In response to the unique access control authority being in an occupied state, controlling the at least one state synchronization request to wait until the unique access control authority is in an idle state.

3. The vehicle upgrade status synchronization method according to claim 2, characterized in that: The configuring the unique access control permission for the target synchronization request includes: Based on the target synchronization request, an occupation mark of the target synchronization request for the unique access control authority is written into the target storage area, wherein the existence of the occupation mark in the target storage area reflects that the unique access control authority is in an occupied state; The target synchronization request is configured with access control permissions for the vehicle upgrade status.

4. The vehicle upgrade status synchronization method according to claim 3, characterized in that: The method further comprises: In response to the target synchronization request being executed, releasing the access control authority of the target synchronization request and ending the relevant process of the target synchronization request; The occupancy mark of the target synchronization request is removed from the target storage area.

5. The vehicle upgrade status synchronization method according to any one of claims 1 to 4, characterized in that: The determining the target synchronization request from the at least one state synchronization request comprises: Determine a response order of the at least one state synchronization request based on an acquisition time of the at least one state synchronization request and / or built-in time information; The target synchronization request is determined from the at least one state synchronization request based on the response order.

6. The vehicle upgrade status synchronization method according to any one of claims 1 to 4, characterized in that: The method further comprises: Determine the target vehicle upgrade status of the target synchronization request; Determining whether the target vehicle upgrade state satisfies the execution sequence requirement of the vehicle upgrade state, wherein the execution sequence requirement reflects the state transition sequence of multiple vehicle upgrade states of the target vehicle during the upgrade process; If so, determining that the target synchronization request satisfies the change requirement; If not, it is determined that the target synchronization request does not meet the change requirement.

7. The vehicle upgrade status synchronization method according to claim 6, characterized in that: The determining whether the target vehicle upgrade state meets the execution sequence requirement of the vehicle upgrade state includes: Determining an upgrade state machine of the target vehicle based on a state transition sequence configuration of a plurality of vehicle upgrade states of the target vehicle during an upgrade process; Determining whether the target vehicle upgrade state satisfies a reversal condition of the upgrade state machine in the vehicle upgrade state; If so, determining that the target synchronization request satisfies the execution order requirement; If not, it is determined that the target synchronization request does not meet the execution order requirement.

8. The vehicle upgrade status synchronization method according to any one of claims 1 to 4, characterized in that: The updating of the vehicle upgrade status based on the target synchronization request and sending the update to the user terminal corresponding to the target vehicle includes: updating the vehicle upgrade status based on the actual upgrade status information in the target synchronization request, and generating an update record of the vehicle upgrade status in a monitoring database of the vehicle upgrade status; In response to a newly added update record of the monitoring database, generating state synchronization information based on the latest update record of the monitoring database, wherein the state synchronization information includes an updated vehicle upgrade state and update time information; The state synchronization information is sent to the user terminal.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle upgrade status synchronization method described in any one of claims 1 to 8.

10. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction processor is executed, the vehicle upgrade status synchronization method according to any one of claims 1 to 8 is implemented.