Vehicle mileage data display method, device and system and vehicle

Abstract

The invention discloses a vehicle mileage data display method, device and system and a vehicle, and is applied to the technical field of vehicles, and the method comprises the following steps: starting a slave cabin domain controller of the vehicle under the condition that a fault of a master cabin domain controller of the vehicle is detected, and obtaining first mileage backup data of the vehicle from the slave cabin domain controller; acquiring second mileage backup data of the vehicle from a vehicle body domain controller of the vehicle; acquiring third mileage backup data of the vehicle from a cloud backup device; and determining target mileage data displayed by the vehicle according to the first mileage backup data, the second mileage backup data and the third mileage backup data. The accuracy of the mileage data displayed by the vehicle can be improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle mileage data display method, device, system and vehicle. Background Art

[0002] The mileage data of a vehicle refers to the total distance traveled by the vehicle from the time it left the factory to the current moment. The current mileage display processing method is to display and process the mileage data based on the main cockpit domain controller. However, when the main cockpit domain controller fails, the accuracy of the mileage data displayed by the vehicle will be reduced. Summary of the invention

[0003] Embodiments of the present application provide a vehicle mileage data display method, device, system and vehicle for improving the accuracy of mileage data displayed by the vehicle.

[0004] In one aspect, an embodiment of the present application provides a vehicle mileage data display method, the method comprising the following steps: In the case of detecting a failure of a main cockpit domain controller of a vehicle, enabling a slave cockpit domain controller of the vehicle, and acquiring the first mileage backup data of the vehicle from the slave cockpit domain controller; Acquire the second mileage backup data of the vehicle from the body domain controller of the vehicle; Acquire the third mileage backup data of the vehicle from a cloud backup device; The target mileage data displayed by the vehicle is determined according to the first mileage backup data, the second mileage backup data and the third mileage backup data.

[0005] On the other hand, an embodiment of the present application provides a vehicle mileage data display device, the device comprising: A first processing module is used to enable a slave cockpit domain controller of the vehicle and obtain first mileage backup data of the vehicle from the slave cockpit domain controller when a failure of the master cockpit domain controller of the vehicle is detected; A second processing module, configured to obtain second mileage backup data of the vehicle from a body domain controller of the vehicle; A third processing module, used for obtaining the third mileage backup data of the vehicle from the cloud backup device; The fourth processing module is used to determine the target mileage data displayed by the vehicle according to the first mileage backup data, the second mileage backup data and the third mileage backup data.

[0006] In another aspect, an embodiment of the present application provides a vehicle mileage data display system, the system comprising: The above-mentioned vehicle mileage data display device; A vehicle controller group, comprising a master cockpit domain controller, a slave cockpit domain controller and a body domain controller, wherein the master cockpit domain controller is used to obtain mileage data of the vehicle and send it to the body domain controller and a cloud backup device associated with the vehicle, the slave cockpit domain controller is used to obtain mileage data of the vehicle and store the mileage data as first mileage backup data, and the body domain controller is used to store the mileage data sent by the master cockpit domain controller as second mileage backup data; The cloud backup device is used to store the mileage data sent by the main cockpit domain controller as third mileage backup data.

[0007] In another aspect, an embodiment of the present application provides a vehicle, the vehicle comprising: at least one processor; at least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the above-mentioned vehicle mileage data display method.

[0008] The vehicle mileage data display method, device, system and vehicle of the present application can enable the vehicle's slave cockpit domain controller if a failure of the vehicle's main cockpit domain controller is detected, and then obtain the vehicle's first mileage backup data from the slave cockpit domain controller. In addition, the vehicle's second mileage backup data is obtained from the vehicle's body domain controller, and the vehicle's third mileage backup data is obtained from the cloud backup device; thereafter, the target mileage data displayed by the vehicle is determined based on the first mileage backup data, the second mileage backup data and the third mileage backup data, to achieve the vehicle's mileage display processing. It can be seen that the present application can back up the vehicle's mileage data to the vehicle's slave cockpit domain controller, the vehicle's body domain controller and the cloud backup device respectively, so that even in the event of a failure of the main cockpit domain controller, the mileage data displayed by the vehicle can be determined and displayed by obtaining these mileage backup data, so that the accuracy and reliability of the mileage data displayed by the vehicle can be improved.

[0009] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a flow chart of a vehicle mileage data display method provided in an embodiment of the present application; Figure 2 is a structural diagram of a vehicle mileage data display device provided in an embodiment of the present application; Figure 3 is a structural diagram of a vehicle mileage data display system provided in an embodiment of the present application; Figure 4 is an example diagram of a vehicle provided in an embodiment of the present application; Figure 5 This is a schematic diagram of the vehicle mileage data display provided by the embodiment of the present application; Figure 6 This is another schematic diagram of the vehicle mileage data display provided in the embodiment of the present application. DETAILED DESCRIPTION

[0011] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0012] The present application is further described below in conjunction with the accompanying drawings and specific embodiments. The described embodiments should not be regarded as limiting the present application, and all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

[0013] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0014] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0015] The mileage data of a vehicle refers to the total distance traveled by the vehicle from the time it left the factory to the current moment. The current mileage display processing method is to display and process the mileage data based on the mileage data of the main cockpit domain controller. However, when the main cockpit domain controller fails, the accuracy of the mileage data displayed by the vehicle will be reduced, and the correctness of the mileage data cannot be ensured.

[0016] In view of this, embodiments of the present application provide a vehicle mileage data display method, device, system and vehicle, aiming to improve the accuracy of the mileage data displayed by the vehicle.

[0017] First, the implementation steps of the vehicle mileage data display method provided in the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0018] The embodiment of the present application provides a vehicle mileage data display method, which can be applied to a terminal, a server, or software running in a terminal or a server. The terminal can be a tablet computer, a laptop computer, a desktop computer, etc., but is not limited to this. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms. In addition, the server can also be a node server in a blockchain network, but is not limited to this. Among them, blockchain is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm.

[0019] Reference Figure 1 , Figure 1 The flowchart of the vehicle mileage data display method provided in the embodiment of the present application mainly includes the following steps S101-S104: S101, when a failure of a main cockpit domain controller of a vehicle is detected, enabling a secondary cockpit domain controller of the vehicle, and obtaining first mileage backup data of the vehicle from the secondary cockpit domain controller; S102, obtaining the second mileage backup data of the vehicle from the vehicle body domain controller; S103, obtaining the third mileage backup data of the vehicle from the cloud backup device; S104, determining target mileage data displayed by the vehicle according to the first mileage backup data, the second mileage backup data and the third mileage backup data.

[0020] In the embodiment of the present application, if a failure of the main cockpit domain controller of the vehicle is detected, the slave cockpit domain controller of the vehicle is enabled, and then the first mileage backup data of the vehicle is obtained from the slave cockpit domain controller, the second mileage backup data of the vehicle is obtained from the body domain controller of the vehicle, and the third mileage backup data of the vehicle is obtained from the cloud backup device; thereafter, the target mileage data displayed by the vehicle is determined based on the first mileage backup data, the second mileage backup data, and the third mileage backup data, and the target mileage data will be displayed on the instrument panel of the vehicle, thereby realizing the mileage display processing of the vehicle. It can be seen that the embodiment of the present application can back up the mileage data of the vehicle to the slave cockpit domain controller, the body domain controller and the cloud backup device of the vehicle respectively, so that even in the case of a failure of the main cockpit domain controller, the mileage data displayed by the vehicle can be determined and displayed by obtaining these mileage backup data, so that the accuracy and reliability of the mileage data displayed by the vehicle can be improved.

[0021] In the above step S101, when the vehicle is powered on, the main cockpit domain controller of the vehicle is detected for faults; if a fault in the main cockpit domain controller is detected, the slave cockpit domain controller of the vehicle is enabled, and the first mileage backup data of the vehicle is obtained from the slave cockpit domain controller, so as to determine the target mileage data displayed by the vehicle based on the first mileage backup data and other mileage backup data in subsequent steps; if no fault in the main cockpit domain controller is detected, the step of performing fault detection on the main cockpit domain controller of the vehicle is returned to realize loop detection.

[0022] The above-mentioned main cockpit domain controller is used to obtain the vehicle's mileage data and send the mileage data to the vehicle's body domain controller and cloud backup device to achieve dual-path backup when there is no failure in the main cockpit domain controller.

[0023] The above-mentioned sending of mileage data to the vehicle's body domain controller and cloud backup device may include sending the mileage data to the vehicle's body domain controller through a preset first communication method; sending the mileage data to the Internet of Vehicles controller through a preset second communication method, so that the Internet of Vehicles controller sends the mileage data to the cloud backup device through a preset third communication method, but is not limited to this.

[0024] The above-mentioned Internet of Vehicles controller is used to forward the mileage data sent by the main cockpit domain controller to the cloud backup device.

[0025] The above-mentioned Internet of Vehicles controller can be configured according to actual conditions, and the embodiments of the present application do not specifically limit this.

[0026] For example, the above-mentioned Internet of Vehicles controller may be a T-Box, namely, Telematics BOX, but is not limited thereto.

[0027] The first communication mode, the second communication mode and the third communication mode can all be set according to actual conditions, and the embodiments of the present application do not specifically limit this.

[0028] For example, the first communication mode and the second communication mode may both be communication modes based on a controller area network (CAN); or, the first communication mode and the second communication mode may both be communication modes based on a service-oriented middleware protocol (Service-Oriented Middleware over IP, SOME / IP) of an international interconnection protocol network, but are not limited thereto.

[0029] For another example, the third communication method may be a communication method based on a fourth generation communication protocol; or, the third communication method may be a communication method based on a fifth generation communication protocol, but is not limited thereto.

[0030] The slave cockpit domain controller is used to obtain the mileage data of the vehicle and store the mileage data as first mileage backup data when the master cockpit domain controller is not faulty; and is enabled when the master cockpit domain controller fails.

[0031] The first mileage backup data is used to represent the mileage data stored by the slave cockpit domain controller.

[0032] The above-mentioned enabling of the vehicle's slave cockpit domain controller may include, if a failure of the vehicle's main cockpit domain controller is detected, sending an enabling instruction to the slave cockpit domain controller so that the slave cockpit domain controller is enabled based on the startup instruction while disabling the master cockpit domain controller, but is not limited to this.

[0033] The obtaining of the first mileage backup data of the vehicle from the cockpit domain controller may include directly obtaining the first mileage backup data of the vehicle from the cockpit domain controller through a preset fourth communication method.

[0034] Alternatively, the above-mentioned obtaining the first mileage backup data of the vehicle from the cockpit domain controller may include sending a first data acquisition request to the cockpit domain controller through a preset fourth communication method, so that the cockpit domain controller returns the first mileage backup data of the vehicle through the fourth communication method based on the first data acquisition request, but is not limited to this.

[0035] The fourth communication mode mentioned above can be set according to actual conditions, and the embodiment of the present application does not make any specific limitation on this.

[0036] For example, the fourth communication method may be a communication method based on the Diagnostic over Internet Protocol (DoIP); or, the fourth communication method may be a communication method based on a controller area network, but is not limited thereto.

[0037] In the above step S102, the second mileage backup data of the vehicle is obtained from the body domain controller of the vehicle, so that in subsequent steps, the target mileage data displayed by the vehicle is determined based on the second mileage backup data and other mileage backup data.

[0038] The body domain controller is used to store the mileage data sent by the main cockpit domain controller as second mileage backup data to achieve local backup.

[0039] The above-mentioned body domain controller can be set according to actual conditions, and the embodiment of the present application does not make any specific limitation on this.

[0040] For example, the body domain controller may be a vehicle dynamics controller (VDC), but is not limited thereto.

[0041] The second mileage backup data is used to represent the mileage data stored by the vehicle body domain controller, that is, the local backup data.

[0042] The obtaining of the second mileage backup data of the vehicle from the body domain controller of the vehicle may include directly obtaining the second mileage backup data of the vehicle from the body domain controller through a preset fifth communication method.

[0043] Alternatively, the above-mentioned obtaining the second mileage backup data of the vehicle from the body domain controller of the vehicle may include sending a second data acquisition request to the body domain controller through a preset fifth communication method, so that the body domain controller returns the second mileage backup data of the vehicle through the fifth communication method based on the second data acquisition request, but is not limited to this.

[0044] The fifth communication mode mentioned above can be set according to actual conditions, and the embodiment of the present application does not make any specific limitation on this.

[0045] For example, the fifth communication method may be a communication method based on a diagnostic communication protocol of an Internet protocol; or, the fifth communication method may be a communication method based on a controller area network, but is not limited thereto.

[0046] In the above step S103, the third mileage backup data of the vehicle is obtained from the cloud backup device, so that in the subsequent steps, the target mileage data displayed by the vehicle is determined based on the third mileage backup data and other mileage backup data.

[0047] The above-mentioned cloud backup device is used to store the mileage data sent by the main cockpit domain controller as third mileage backup data to achieve cloud backup.

[0048] The third mileage backup data is used to represent the mileage data stored by the cloud backup device, ie, the cloud backup data.

[0049] The obtaining of the third mileage backup data of the vehicle from the cloud backup device may include directly obtaining the third mileage backup data of the vehicle from the cloud backup device through a preset third communication method.

[0050] Alternatively, the above-mentioned obtaining of the third mileage backup data of the vehicle from the cloud backup device may include sending a third data acquisition request to the cloud backup device via a preset sixth communication method, so that the cloud backup device returns the third mileage backup data of the vehicle via the sixth communication method based on the third data acquisition request, but is not limited to this.

[0051] The sixth communication mode mentioned above can be set according to actual conditions, and the embodiment of the present application does not make any specific limitation on this.

[0052] For example, the sixth communication method may be a communication method based on Hypertext Transfer Protocol Secure (HTTPS); or, the sixth communication method may be a communication method based on Transmission Control Protocol / Internet Protocol (TCP / IP), but is not limited thereto.

[0053] The above-mentioned obtaining of the first mileage backup data of the vehicle from the cockpit domain controller, the above-mentioned obtaining of the second mileage backup data of the vehicle from the body domain controller of the vehicle, and the above-mentioned obtaining of the third mileage backup data of the vehicle from the cloud backup device may be executed in parallel.

[0054] For example, the first mileage backup data of the vehicle is obtained from the cockpit domain controller, the second mileage backup data of the vehicle is obtained from the body domain controller of the vehicle, and the third mileage backup data of the vehicle is obtained from the cloud backup device at the same time.

[0055] Alternatively, the obtaining of the first mileage backup data of the vehicle from the cockpit domain controller, the obtaining of the second mileage backup data of the vehicle from the body domain controller of the vehicle, and the obtaining of the third mileage backup data of the vehicle from the cloud backup device may be executed serially.

[0056] For example, the first mileage backup data of the vehicle is first obtained from the cockpit domain controller, then the second mileage backup data of the vehicle is obtained from the vehicle body domain controller, and finally the third mileage backup data of the vehicle is obtained from the cloud backup device.

[0057] For another example, the first mileage backup data of the vehicle is first obtained from the cockpit domain controller, and the second mileage backup data of the vehicle is obtained from the body domain controller of the vehicle and the third mileage backup data of the vehicle is obtained from the cloud backup device.

[0058] In the above step S104, the target mileage data displayed by the vehicle is determined by using the first mileage backup data, the second mileage backup data and the third mileage backup data, and the target mileage data is displayed on the instrument panel of the vehicle, thereby realizing the mileage display processing of the vehicle.

[0059] The above target mileage data refers to the mileage value finally displayed by the vehicle instrument.

[0060] Determining the target mileage data displayed by the vehicle based on the first mileage backup data, the second mileage backup data and the third mileage backup data may include obtaining the average of the first mileage backup data, the second mileage backup data and the third mileage backup data as the target mileage data displayed by the vehicle, but is not limited thereto.

[0061] The above steps will be further described below.

[0062] In some implementations, determining the target mileage data displayed by the vehicle based on the first mileage backup data, the second mileage backup data, and the third mileage backup data may include: Determine the total mileage backup data according to the second mileage backup data and the third mileage backup data; The target mileage data displayed by the vehicle is determined according to the total mileage backup data and the first mileage backup data.

[0063] In this implementation, first, the second mileage backup data and the third mileage backup data are used to obtain the total mileage backup data to ensure the accuracy of the mileage backup data; then, the total mileage backup data and the first mileage backup data are used to obtain the target mileage data displayed by the vehicle, thereby ensuring the accuracy of the mileage backup data stored in the cockpit domain controller and improving the accuracy and reliability of the vehicle mileage data.

[0064] The above total mileage backup data is used to represent the final two-way mileage backup data.

[0065] Determining the total mileage backup data based on the second mileage backup data and the third mileage backup data may include determining the maximum value of the mileage backup data from the second mileage backup data and the third mileage backup data as the total mileage backup data, but is not limited thereto.

[0066] Determining the target mileage data displayed on the vehicle based on the total mileage backup data and the first mileage backup data may include calculating the average of the total mileage backup data and the first mileage backup data as the target mileage data displayed on the vehicle, but is not limited thereto.

[0067] In some implementations, determining the total mileage backup data based on the second mileage backup data and the third mileage backup data may include: Obtaining a first confidence level of the second mileage backup data and a second confidence level of the third mileage backup data according to the communication data of the vehicle, the risk data of the vehicle body domain controller, and the risk data of the cloud backup device; Total mileage backup data is determined according to the second mileage backup data, the third mileage backup data, the first confidence level, and the second confidence level.

[0068] In this implementation, local backup may be lost or invalid due to network anomalies, hardware damage, etc., while cloud backup may be inaccurate and inaccurate due to network freezes, interruptions, or insufficient traffic. These phenomena will reduce the accuracy of mileage backup data. In addition, both local and cloud backups have the risk of human tampering with backup data, and the security and availability of mileage backup data cannot be guaranteed.

[0069] In this regard, first, the first confidence of the second mileage backup data and the second confidence of the third mileage backup data are determined using the vehicle's communication data, the risk data of the body domain controller, and the risk data of the cloud backup device. Each confidence is used to characterize the reliability of the mileage backup data; then, the total mileage backup data is determined using the first confidence of the second mileage backup data and the second confidence of the third mileage backup data. In this way, the confidence of the local backup data and the cloud backup data is determined by fully considering the vehicle's data transmission, the risk of the body domain controller, and the risk of the cloud backup device, effectively improving the confidence accuracy of each backup data, and then determining the final dual-channel mileage backup data through the confidence of each backup data, ensuring the accuracy of the mileage backup data, improving the security and availability of the mileage backup data, and thereby improving the accuracy of the target mileage data displayed by the vehicle.

[0070] The above communication data can be set according to actual conditions, and this embodiment does not specifically limit this.

[0071] For example, the communication data may include communication data of the first link and communication data of the second link.

[0072] The above-mentioned first link is a communication link connecting the body domain controller and the main cockpit domain controller.

[0073] The communication data of the above-mentioned first link may include the protocol efficiency of the first link. The protocol efficiency of the first link refers to the efficiency of transmitting mileage data from the main cockpit domain controller to the body domain controller through SOME / IP. The higher the protocol efficiency of the first link, the lower the possibility of network abnormality in the first link, and the higher the reliability of the second mileage backup data.

[0074] The protocol efficiency of the first link may be a ratio of a total amount of data received by the vehicle body domain controller to a transmission duration of the first link.

[0075] The transmission duration of the above-mentioned first link may be the difference between the actual transmission duration of the first link and the packet loss duration of the first link. The actual transmission duration of the first link may be the difference between the time value when the body domain controller receives the mileage data and the time value when the main cockpit domain controller sends the mileage data. The packet loss duration of the first link may be the duration of the packet loss phenomenon during the transmission process of the first link.

[0076] The above-mentioned second link is a communication link connecting the cloud backup device, the Internet of Vehicles controller and the main cockpit domain controller, wherein the communication link connecting the cloud backup device and the Internet of Vehicles controller is the first sub-link, and the communication link connecting the Internet of Vehicles controller and the main cockpit domain controller is the second sub-link.

[0077] The communication data of the above-mentioned second link may include the protocol efficiency of the second link. The protocol efficiency of the second link may be the sum of the protocol efficiency of the first sub-link and the protocol efficiency of the second sub-link, wherein the protocol efficiency of the first sub-link refers to the efficiency of transmitting mileage data from the main cockpit domain controller to the Internet of Vehicles controller through SOME / IP, and the protocol efficiency of the second sub-link refers to the efficiency of transmitting mileage data from the Internet of Vehicles controller to the cloud backup device through the fifth-generation communication protocol. The higher the protocol efficiency of the first sub-link and the protocol efficiency of the second sub-link, the lower the possibility of network abnormality in the second link, and the more reliable the third mileage backup data.

[0078] The protocol efficiency of the first sub-link may be a ratio of a total amount of data received by the Internet of Vehicles controller to a transmission duration of the first sub-link.

[0079] The transmission duration of the above-mentioned first sub-link may be the difference between the actual transmission duration of the first sub-link and the packet loss duration of the first sub-link. The actual transmission duration of the first sub-link may be the difference between the time value when the Internet of Vehicles controller receives the mileage data and the time value when the main cockpit domain controller sends the mileage data. The packet loss duration of the first sub-link may be the duration of the packet loss phenomenon during the transmission process of the first sub-link.

[0080] The protocol efficiency of the second sub-link may be a ratio of a total amount of data received by the cloud backup device to a transmission duration of the second sub-link.

[0081] The transmission duration of the above-mentioned second sub-link may be the difference between the actual transmission duration of the second sub-link and the packet loss duration of the second sub-link. The actual transmission duration of the second sub-link may be the difference between the time value when the cloud backup device receives the mileage data and the time value when the Internet of Vehicles controller sends the mileage data. The packet loss duration of the second sub-link may be the duration of the packet loss phenomenon during the transmission process of the second sub-link.

[0082] The risk data may include a plurality of parameters associated with mileage data storage, but is not limited thereto.

[0083] The above risk data can be set according to actual conditions, and this embodiment does not specifically limit this.

[0084] For example, the risk data of the vehicle body domain controller may include the failure frequency and data modification frequency of the vehicle body domain controller.

[0085] The failure frequency of the body domain controller is used to indicate the hardware failure condition of the body domain controller. The lower the failure frequency of the body domain controller is, the more stable the hardware of the body domain controller is, and the higher the reliability of the second mileage backup data is.

[0086] The failure frequency of the vehicle body domain controller may be a ratio of the number of failures of the vehicle body domain controller within a preset time period to the preset time period.

[0087] The data modification frequency of the body domain controller is used to indicate the data tampering of the body domain controller. The lower the data modification frequency of the body domain controller is, the lower the possibility of data stored in the body domain controller being tampered with is, and the more reliable the second mileage backup data is.

[0088] The data modification frequency of the vehicle body domain controller may be a ratio of the number of times the second mileage backup data is modified or accessed without authorization within a preset time period to the preset time period.

[0089] For another example, the risk data of the cloud backup device may include a data modification frequency of the cloud backup device.

[0090] The data modification frequency of the cloud backup device is used to indicate the data tampering of the cloud backup device. The lower the data modification frequency of the cloud backup device is, the lower the possibility of data stored in the cloud backup device being tampered with is, and the more reliable the third mile backup data is.

[0091] The data modification frequency of the cloud backup device may be a ratio of the number of times the third mileage backup data is modified or accessed without authorization within a preset time period to the preset time period.

[0092] The first confidence level of the second mileage backup data is used to indicate the reliability of the second mileage backup data.

[0093] The first confidence of the second mileage backup data is positively correlated with the reliability of the second mileage backup data, that is, the higher the first confidence of the second mileage backup data, the higher the reliability of the second mileage backup data; the lower the first confidence of the second mileage backup data, the lower the reliability of the second mileage backup data.

[0094] The second confidence level of the third mileage backup data is used to indicate the reliability of the third mileage backup data.

[0095] The second confidence of the third mileage backup data is positively correlated with the reliability of the third mileage backup data, that is, the higher the second confidence of the third mileage backup data, the higher the reliability of the third mileage backup data; the lower the second confidence of the third mileage backup data, the lower the reliability of the third mileage backup data.

[0096] The above-mentioned obtaining of the first confidence of the second mileage backup data and the second confidence of the third mileage backup data based on the vehicle's communication data, the risk data of the body domain controller and the risk data of the cloud backup device may include searching for the confidence corresponding to the vehicle's communication data and the risk data of the body domain controller from preset mapping data as the first confidence of the second mileage backup data, and searching for the confidence corresponding to the vehicle's communication data and the risk data of the cloud backup device from the first mapping data as the second confidence of the third mileage backup data, wherein the preset mapping data includes multiple first variables and the confidence corresponding to each first variable, and the first variables include preset communication data and preset risk data, but are not limited to this.

[0097] The above-mentioned determination of the total mileage backup data based on the second mileage backup data, the third mileage backup data, the first confidence level and the second confidence level may include taking a weighted average of the second mileage backup data and the third mileage backup data according to the first confidence level and the second confidence level to obtain the total mileage backup data, but is not limited thereto.

[0098] In some embodiments, obtaining the first confidence level of the second mileage backup data and the second confidence level of the third mileage backup data based on the communication data of the vehicle, the risk data of the vehicle body domain controller, and the risk data of the cloud backup device may include: According to the communication data of the vehicle and the risk data of the vehicle body domain controller, a confidence sequence of the second mileage backup data is obtained, where the confidence sequence of the second mileage backup data includes confidences of the second mileage backup data at multiple future moments; According to the communication data of the vehicle and the risk data of the cloud backup device, a confidence sequence of the third mileage backup data is obtained, wherein the confidence sequence of the third mileage backup data includes confidences of the third mileage backup data at multiple future moments; Obtaining a first confidence level of the second mileage backup data according to the confidence level sequence of the second mileage backup data; According to the confidence sequence of the third mileage backup data, a second confidence of the third mileage backup data is obtained.

[0099] In this embodiment, first, based on the communication data of the vehicle and the risk data of the body domain controller, a confidence sequence of the second mileage backup data is determined. The confidence sequence of the second mileage backup data may include the confidence of the second mileage backup data at multiple future moments. The confidence sequence can reflect the impact of hardware abnormalities and / or data tampering on the body domain controller in the future time period, and it also reflects the data storage reliability of the body domain controller in the future time period; and, based on the communication data of the vehicle and the risk data of the cloud backup device, a confidence sequence of the third mileage backup data is determined. The confidence sequence of the third mileage backup data may include the confidence of the third mileage backup data at multiple future moments. The confidence sequence can reflect the impact of data tampering on the cloud backup device in the future time period, and it also reflects the data storage reliability of the cloud backup device in the future time period; then, according to the confidence sequence of the second mileage backup data, the first confidence of the second mileage backup data is determined, and according to the confidence sequence of the third mileage backup data, the second confidence of the third mileage backup data is determined, thereby ensuring the confidence accuracy of each mileage backup data.

[0100] The confidence sequence of the above-mentioned second mileage backup data may include the confidence of the second mileage backup data at multiple future moments, which can reflect the impact of hardware anomalies and / or data tampering on the body domain controller in the future time period, as well as the data storage reliability of the body domain controller in the future time period.

[0101] The confidence sequence of the third mileage backup data may include the confidence of the third mileage backup data at multiple future moments, which can reflect the impact of data tampering on the cloud backup device in the future time period and the data storage reliability of the cloud backup device in the future time period.

[0102] The number of the above future moments can be set according to actual conditions, and this embodiment does not specifically limit this.

[0103] The above-mentioned obtaining the confidence sequence of the second mileage backup data based on the vehicle's communication data and the risk data of the body domain controller may include obtaining the confidence sequence of the second mileage backup data based on the vehicle's communication data and the risk data of the body domain controller in combination with a machine learning method.

[0104] The above-mentioned machine learning method can be set according to actual conditions, and the embodiments of the present application do not make any specific limitations on this.

[0105] For example, the above-mentioned machine learning method may be a gradient boosting machine; or, the above-mentioned machine learning method may be a random forest, but is not limited thereto.

[0106] Alternatively, obtaining the confidence sequence of the second mileage backup data based on the vehicle's communication data and the risk data of the body domain controller may include integrating the vehicle's communication data and the risk data of the body domain controller into one-dimensional sequence data, inputting the one-dimensional sequence data into a pre-trained first deep learning model, and predicting the confidence of the second mileage backup data at multiple future moments through the first deep learning model, thereby obtaining the confidence sequence of the second mileage backup data, but is not limited to this.

[0107] The above-mentioned first deep learning model can be trained through multiple first sample data and the confidence value corresponding to each first sample data, and each first sample data includes communication sample data of the vehicle and risk sample data of the body domain controller.

[0108] The above-mentioned first deep learning model can be set according to actual conditions, and the embodiment of the present application does not make any specific limitation on this.

[0109] For example, the first deep learning model may be a large model such as TimeGPT; or, the first deep learning model may be a neural network model such as a long short-term memory neural network model, but is not limited thereto.

[0110] The above-mentioned obtaining the confidence sequence of the third mileage backup data based on the vehicle's communication data and the risk data of the cloud backup device may include obtaining the confidence sequence of the third mileage backup data based on the vehicle's communication data and the risk data of the cloud backup device in combination with a machine learning method.

[0111] Alternatively, obtaining the confidence sequence of the third mileage backup data based on the vehicle's communication data and the risk data of the cloud backup device may include integrating the vehicle's communication data and the risk data of the cloud backup device into one-dimensional sequence data, inputting the one-dimensional sequence data into a pre-trained second deep learning model, and predicting the confidence of the third mileage backup data at multiple future moments through the second deep learning model, thereby obtaining the confidence sequence of the third mileage backup data, but is not limited to this.

[0112] The second deep learning model can be trained by using a plurality of second sample data and a confidence value corresponding to each second sample data, and each second sample data includes communication sample data of the vehicle and risk sample data of the cloud backup device.

[0113] The above-mentioned second deep learning model can be set according to actual conditions, and the embodiment of the present application does not make any specific limitation on this.

[0114] For example, the second deep learning model may be a large model such as TimeGPT; or, the second deep learning model may be a neural network model such as a long short-term memory neural network model, but is not limited thereto.

[0115] The above-mentioned obtaining the first confidence of the second mileage backup data based on the confidence sequence of the second mileage backup data may include weighting the confidence of the second mileage backup data at multiple future moments to obtain the first confidence of the second mileage backup data, and the sum of the weights of the confidence of the second mileage backup data at each future moment is one.

[0116] Alternatively, obtaining the first confidence of the second mileage backup data according to the confidence sequence of the second mileage backup data may include calculating the average of the confidences of the second mileage backup data at multiple future moments as the first confidence of the second mileage backup data, but is not limited thereto.

[0117] The above-mentioned method of obtaining the second confidence of the third mileage backup data based on the confidence sequence of the third mileage backup data may include weighting the confidence of the third mileage backup data at multiple future moments to obtain the second confidence of the third mileage backup data, and the sum of the weights of the confidence of the third mileage backup data at each future moment is one.

[0118] Alternatively, obtaining the second confidence of the third mileage backup data according to the confidence sequence of the third mileage backup data may include calculating the average of the confidences of the third mileage backup data at multiple future moments as the second confidence of the third mileage backup data, but is not limited thereto.

[0119] In some implementations, determining the total mileage backup number based on the second mileage backup data, the third mileage backup data, the first confidence level, and the second confidence level may include: Among the second mileage backup data and the third mileage backup data, the mileage backup data with the greatest confidence is selected as the total mileage backup data.

[0120] In this embodiment, the mileage backup data with the highest confidence level between the second mileage backup data and the third mileage backup data is selected, and the selected mileage backup data is used as the total mileage backup data to ensure the accuracy of the mileage backup data, improve the security and reliability of the mileage backup data, and thereby improve the accuracy of the target mileage data displayed by the vehicle.

[0121] In some implementations, determining the target mileage data displayed by the vehicle based on the total mileage backup data and the first mileage backup data may include: If the total mileage backup data is greater than the first mileage backup data, the total mileage backup data is determined as the target mileage data displayed by the vehicle; Alternatively, if the total mileage backup data is less than or equal to the first mileage backup data, the first mileage data is determined as the target mileage data displayed by the vehicle.

[0122] In this embodiment, the target mileage data displayed by the vehicle is obtained by using the total mileage backup data and the first mileage backup data, thereby updating the mileage backup data stored in the cockpit domain controller, ensuring the accuracy of the mileage backup data stored in the cockpit domain controller, and improving the accuracy and reliability of the mileage data displayed by the vehicle. Specifically, the total mileage backup data is compared to see whether it is greater than the first mileage backup data. If so, the total mileage backup data is determined as the target mileage data displayed by the vehicle, otherwise the first mileage data is determined as the target mileage data displayed by the vehicle.

[0123] In some embodiments, the above method may further include: Receive a zeroing instruction; In response to the zeroing instruction, the slave cockpit domain controller, the master cockpit domain controller, the body domain controller and the cloud backup device are reset to zero.

[0124] In this embodiment, first, a zeroing instruction is received, and the zeroing instruction is used to reset the mileage data stored in the master cockpit domain controller and the slave cockpit domain controller, as well as the mileage backup data of the local backup and the cloud backup; then, a response is made to the zeroing instruction to perform zeroing processing on the slave cockpit domain controller, the master cockpit domain controller, the body domain controller and the cloud backup device, so that the mileage data stored in the master cockpit domain controller and the slave cockpit domain controller are cleared, and the mileage backup data of the local backup and the cloud backup are cleared, which is beneficial to clear redundant mileage data, improve the resource utilization and availability of each controller and the cloud backup device, and ensure the normal progress of subsequent mileage backup.

[0125] The above reset command is used to reset the mileage data stored in the master cockpit domain controller and the slave cockpit domain controller, as well as the mileage backup data of the local backup and the cloud backup.

[0126] The receiving of the zeroing instruction may include receiving a zeroing instruction sent by a main control screen controller of the vehicle, wherein the zeroing instruction is configured to be generated by the main control screen controller when a zeroing control on the main control screen of the vehicle is triggered.

[0127] The triggering method of the above-mentioned zeroing control may include but is not limited to clicking. The above-mentioned zeroing control may be a click-confirmation button, or other scrolling / sliding selectors, drop-down menu selection units, etc. This embodiment does not make specific limitations on this.

[0128] Alternatively, the receiving of the zeroing instruction may include receiving a zeroing instruction sent by a center console controller of the vehicle, wherein the zeroing instruction is configured to be generated by the center console controller when a zeroing mechanical switch of a main console of the vehicle is triggered.

[0129] The specific structure or type of the zero-setting mechanical switch can be set according to actual conditions, and this embodiment does not specifically limit this.

[0130] The above-mentioned zeroing processing of the slave cockpit domain controller, the master cockpit domain controller, the body domain controller and the cloud backup device may include forwarding the zeroing instruction to the slave cockpit domain controller, the master cockpit domain controller, the body domain controller and the cloud backup device, so that the slave cockpit domain controller updates the first mileage backup data to zero based on the zeroing instruction, the master cockpit domain controller updates the stored mileage data to zero based on the zeroing instruction, the body domain controller updates the second mileage backup data to zero based on the zeroing instruction, and the cloud backup device updates the third mileage backup data to zero based on the zeroing instruction.

[0131] Alternatively, the above-mentioned zeroing processing of the slave cockpit domain controller, the master cockpit domain controller, the body domain controller and the cloud backup device may include forwarding the zeroing instruction to the master cockpit domain controller and the slave cockpit domain controller, so that the slave cockpit domain controller updates the first mileage backup data to zero based on the zeroing instruction, the master cockpit domain controller updates the stored mileage data to zero based on the zeroing instruction, generates a set signal based on the zeroing instruction, and sends the set signal to the body domain controller and the cloud backup device, the body domain controller updates the second mileage backup data to zero based on the set signal, and the cloud backup device updates the third mileage backup data to zero based on the set signal, but is not limited to this.

[0132] In some embodiments, the cloud backup device may include a cloud diagnostic server and a cloud backup server; and obtaining the third mileage backup data of the vehicle from the cloud backup device may include: A third data acquisition request is sent to the cloud diagnostic server, where the third data acquisition request carries a target identification code of the vehicle, so that the cloud diagnostic server obtains and returns the third mileage backup data corresponding to the target identification code from the cloud backup server.

[0133] In this embodiment, the cloud backup device may include a cloud diagnostic server and a cloud backup server. When the third mileage backup data of the vehicle needs to be obtained, a third data acquisition request is sent to the cloud diagnostic server. The third data acquisition request carries the target identification code of the vehicle, so that the cloud diagnostic server obtains the third mileage backup data corresponding to the target identification code from the cloud backup server and returns it. In this way, the cloud backup server can be prevented from directly communicating with other devices with tampering risks, ensuring the security of cloud backup, and obtaining the corresponding mileage backup data through the target identification code can ensure the correctness of the acquired data.

[0134] The cloud diagnostic server is used to obtain and return the third mileage backup data corresponding to the target identification code of the vehicle from the cloud backup server.

[0135] The obtaining of the third mileage backup data corresponding to the target identification code from the cloud backup server may include obtaining the third mileage backup data corresponding to the target identification code from the cloud backup server through a preset seventh communication method, but is not limited thereto.

[0136] The seventh communication method mentioned above may be a communication method based on the Transmission Control Protocol / Internet Protocol, but is not limited thereto.

[0137] The cloud backup server is used to store the third mileage backup data of the vehicle.

[0138] The cloud backup server can be connected to the Internet of Vehicles controller via a preset third communication method.

[0139] The third data acquisition request may carry a target identification code of the vehicle.

[0140] The above target identification code can be set according to actual conditions, and this embodiment does not specifically limit this.

[0141] In some implementations, before the above detection of a failure of the main cockpit domain controller of the vehicle, the above method may further include: Obtaining the mileage data of the vehicle through the instrument service module of the main cockpit domain controller and writing the mileage data to the microcontroller of the main cockpit domain controller, and sending the mileage data to the body domain controller and the cloud backup device; The mileage data is stored as the second mileage backup data through the vehicle body domain controller; The mileage data is stored as third mileage backup data via a cloud backup device.

[0142] In this embodiment, before a failure of the vehicle's main cockpit domain controller is detected, the vehicle's mileage data is obtained through the instrument service module of the main cockpit domain controller and the mileage data is written to the microcontroller of the main cockpit domain controller, and the microcontroller of the main cockpit domain controller will store the mileage data; and, the mileage data is sent to the body domain controller and the cloud backup device through the instrument service module of the main cockpit domain controller, and the mileage data is stored as the second mileage backup data through the body domain controller to achieve local backup, and the mileage data is stored as the third mileage backup data through the cloud backup device to achieve cloud backup, thereby achieving dual-channel mileage backup.

[0143] The above-mentioned main cockpit domain controller may include an instrument service module and a microcontroller. The instrument service module is configured with an instrument service. The instrument service module is used to obtain the vehicle's mileage data and write the mileage data to the microcontroller and send the mileage data to the body domain controller and the cloud backup device. The microcontroller is used to store the mileage data written by the instrument service module.

[0144] The instrument service module of the main cockpit domain controller may communicate with the microcontroller of the main cockpit domain controller via a serial peripheral interface (SPI), but is not limited thereto.

[0145] The microcontroller of the above-mentioned main cockpit domain controller can be configured with an electrically erasable programmable read-only memory (EEPROM), and the electrically erasable programmable read-only memory is provided with multiple storage space blocks, each storage space block is used to store the mileage data written by the instrument service module of the main cockpit domain controller at a corresponding moment to ensure the accuracy of the mileage data.

[0146] The above-mentioned acquisition of the vehicle's mileage data may include obtaining the vehicle's mileage data based on the vehicle's real-time speed and driving time, but is not limited thereto.

[0147] The above-mentioned writing of mileage data to the microcontroller of the main cockpit domain controller may include writing the mileage data to the microcontroller of the main cockpit domain controller while obtaining the mileage data, but is not limited to this.

[0148] The above-mentioned sending of mileage data to the body domain controller and the cloud backup device may include sending the mileage data to the body domain controller through a preset first communication method, and sending the mileage data to the Internet of Vehicles controller through a preset second communication method, so that the Internet of Vehicles controller transmits the mileage data to the cloud backup server in the cloud backup device through a preset third communication method, but is not limited to this.

[0149] In some implementations, before the above detection of a failure of the main cockpit domain controller of the vehicle, the above method may further include: The mileage data of the vehicle is obtained from the instrument service module of the cockpit domain controller as the first mileage backup data, and the first mileage backup data is written to the microcontroller of the cockpit domain controller.

[0150] In this implementation, in order to ensure that the vehicle mileage can be displayed normally in the event of a failure of the main cockpit domain controller, before the failure of the vehicle's main cockpit domain controller is detected, the vehicle's mileage data is obtained through the instrument service module of the slave cockpit domain controller as the first mileage backup data, and the first mileage backup data is written to the microcontroller of the slave cockpit domain controller. The microcontroller of the slave cockpit domain controller will store the first mileage backup data, and then in the event of a failure of the main cockpit domain controller, the slave cockpit domain controller can be enabled and the mileage data stored by the slave cockpit domain controller can be displayed.

[0151] The above-mentioned slave cockpit domain controller may include an instrument service module and a microcontroller. The instrument service module is configured with an instrument service. The instrument service module is used to obtain the vehicle's mileage data as the first mileage backup data and write the first mileage backup data to the microcontroller. The microcontroller is used to store the first mileage backup data written by the instrument service module.

[0152] The instrument service module of the slave cockpit domain controller may communicate with the microcontroller of the slave cockpit domain controller via a serial peripheral interface, but is not limited thereto.

[0153] The microcontroller of the slave cockpit domain controller may be configured with an electrically erasable programmable read-only memory (EEPROM), which is provided with a plurality of storage space blocks, each storage space block being used to store the mileage data written by the instrument service module of the slave cockpit domain controller at a corresponding moment, so as to ensure the accuracy of the mileage data.

[0154] The above-mentioned acquisition of the vehicle's mileage data may include obtaining the vehicle's mileage data based on the vehicle's real-time speed and driving time, but is not limited thereto.

[0155] The above-mentioned writing of the mileage data into the microcontroller of the slave cockpit domain controller may include writing the mileage data into the microcontroller of the slave cockpit domain controller while obtaining the mileage data, but is not limited thereto.

[0156] In some embodiments, the microcontroller that writes the mileage data to the main cockpit domain controller may include: If the vehicle meets the writing conditions, the mileage data is written to the microcontroller of the main cockpit domain controller through the instrument service module of the main cockpit domain controller. The writing conditions include at least one of the following: A power-off command of the vehicle is detected, and the power-off command is used to control the vehicle to power off; The vehicle's mileage write difference is greater than a preset mileage threshold, and the mileage write difference is the difference between the mileage data at the current moment and the mileage data most recently written to the microcontroller of the main cockpit domain controller; The vehicle's mileage writing duration is greater than the preset duration threshold, and the mileage writing duration is the difference between the current moment and the time value of the most recent write processing to the microcontroller of the main cockpit domain controller.

[0157] In this implementation, in order to avoid writing a large amount of useless mileage data and improve the resource utilization of the microcontroller, if the vehicle meets the writing conditions, the mileage data is written to the microcontroller of the main cockpit domain controller through the instrument service module of the main cockpit domain controller. The writing conditions may include at least one of detecting a power-off instruction of the vehicle, the mileage writing difference of the vehicle being greater than a preset mileage threshold, and the mileage writing time of the vehicle being greater than a preset time threshold, wherein: The detected vehicle power-off instruction is used to indicate that the vehicle is powered off, that is, each time the vehicle is powered off, the mileage data is stored in the microcontroller of the main cockpit domain controller through the instrument service module of the main cockpit domain controller; The vehicle's mileage write difference value greater than the preset mileage threshold is used to indicate that the vehicle's mileage data has not been updated for a long time. At this time, the new mileage data needs to be stored in the microcontroller of the main cockpit domain controller through the instrument service module of the main cockpit domain controller; The vehicle's mileage writing time longer than the preset time threshold is used to indicate that the vehicle's mileage data has not been updated for a long time. At this time, the new mileage data needs to be stored in the microcontroller of the main cockpit domain controller through the instrument service module of the main cockpit domain controller.

[0158] The above mileage threshold and the above duration threshold can be set according to actual conditions, and this embodiment does not specifically limit this.

[0159] The above-mentioned writing conditions are also applicable to the above-mentioned writing of the first mileage backup data to the microcontroller of the cockpit domain controller, which will not be repeated here.

[0160] Secondly, the implementation of the vehicle mileage data display device provided in the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0161] Reference Figure 2 , Figure 2 : is a structural diagram of a vehicle mileage data display device provided in an embodiment of the present application, and the vehicle mileage data display device may include: The first processing module 201 is used to enable the slave cockpit domain controller of the vehicle and obtain the first mileage backup data of the vehicle from the slave cockpit domain controller when a failure of the master cockpit domain controller of the vehicle is detected; The second processing module 202 is used to obtain the second mileage backup data of the vehicle from the vehicle body domain controller; The third processing module 203 is used to obtain the third mileage backup data of the vehicle from the cloud backup device; The fourth processing module 204 is used to determine the target mileage data displayed by the vehicle according to the first mileage backup data, the second mileage backup data and the third mileage backup data.

[0162] The vehicle mileage data display device may be a diagnostic instrument, but is not limited thereto.

[0163] The contents of the above method embodiments are all applicable to the present device embodiments. The functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0164] Afterwards, the implementation of the vehicle mileage data display system provided in the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0165] Reference Figure 3 , Figure 3 This is a structural diagram of a vehicle mileage data display system provided in an embodiment of the present application. The vehicle mileage data display system may include: The above-mentioned vehicle mileage data display device; The vehicle controller group 301 includes a master cockpit domain controller, a slave cockpit domain controller and a body domain controller, the master cockpit domain controller is used to obtain the mileage data of the vehicle and send it to the body domain controller and a cloud backup device associated with the vehicle, the slave cockpit domain controller is used to obtain the mileage data of the vehicle and store the mileage data as first mileage backup data, and the body domain controller is used to store the mileage data sent by the master cockpit domain controller as second mileage backup data; The cloud backup device 302 is used to store the mileage data sent by the main cockpit domain controller as third mileage backup data.

[0166] In some embodiments, the vehicle mileage data display system may further include: The Internet of Vehicles controller is used to obtain the mileage data sent by the main cockpit domain controller and send the mileage data to the cloud backup device.

[0167] In some implementations, the cloud backup device may include: Cloud backup server, used to store the third mileage backup data of the vehicle; The cloud diagnostic server is used to obtain the third mileage backup data corresponding to the target identification code of the vehicle from the cloud backup server and return it to the above-mentioned vehicle mileage data display device.

[0168] The contents of the above method embodiments are all applicable to the present system embodiments. The functions specifically implemented by the present system embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0169] Finally, refer to Figure 4 The embodiment of the present application further provides a vehicle, the vehicle comprising: at least one processor 401; At least one memory 402, used to store at least one program; When at least one program is executed by at least one processor 401 , at least one processor 401 implements the above-mentioned vehicle mileage data display method.

[0170] The above-mentioned vehicles can be private cars, such as sedans, sport utility vehicles (SUV), multi-purpose vehicles (MPV) or pickup trucks, etc., or they can be commercial vehicles, such as vans, buses, small trucks or large trailers, etc. They can also be gasoline vehicles or new energy vehicles such as hybrid vehicles and pure electric vehicles.

[0171] The above-mentioned memory 402, as a non-transient network system, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 402 may optionally include a memory 402 remotely arranged relative to the processor 401, and these remote memories 402 may be connected to the processor 401 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.

[0172] The above-mentioned memory 402 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM). The memory 402 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 402, and the processor 401 is called to execute the method of the embodiment of this application.

[0173] The processor 401 may be implemented by a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solution provided in the embodiments of the present application.

[0174] In some embodiments, the vehicle may further include: Input / output interface, used to realize information input and output; Communication interface, used to realize communication interaction between this device and other devices. Communication can be realized through wired methods (such as USB, network cable, etc.) or wireless methods (such as mobile network, WIFI, Bluetooth, etc.); A bus that transmits information between various components of the device (e.g., processor 401, memory 402, input / output interfaces, and communication interfaces); The processor 401 , the memory 402 , the input / output interface and the communication interface can be connected to each other in communication within the device via a bus.

[0175] The contents of the above method embodiments are all applicable to the present vehicle embodiment. The functions specifically implemented by the present vehicle embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0176] To facilitate understanding of the vehicle mileage data display method, device, system and vehicle described above in the present application, actual application scenarios of the vehicle mileage data display method, device, system and vehicle described above in the present application are used as examples.

[0177] Reference Figure 5 In this example, the vehicle mileage data display system mainly includes a main cockpit domain controller, a slave cockpit domain controller, a body domain controller, a vehicle networking controller, a cloud backup device and a vehicle mileage data display device. The cloud backup device includes a cloud diagnostic server and a cloud backup server. The cloud backup server is a cloud TSP (Telematics Service Provider) server. The vehicle mileage data display device is a diagnostic instrument, and the vehicle networking controller is TBOX.

[0178] The connection methods of the above-mentioned structures are specifically as follows: the main cockpit domain controller is connected to the body domain controller and the Internet of Vehicles controller respectively through SOME / IP; the body domain controller is connected to the diagnostic instrument through DoIP; the Internet of Vehicles controller is connected to the cloud backup server through 5G; the diagnostic instrument is connected to the cloud diagnostic server through HTTPS, and the diagnostic instrument is connected to the slave cockpit domain controller through DoIP; the cloud diagnostic server is connected to the cloud backup server through TCP / IP.

[0179] In addition, both the master cockpit domain controller and the slave cockpit domain controller are configured with a chip-level system (System OnChip, SOC) and a microcontroller. An instrument service module is set on the chip-level system, and the instrument service module is connected to the microcontroller via SPI.

[0180] For the main cockpit domain controller, its instrument service module is mainly used to obtain the vehicle's mileage data and write it into the microcontroller, as well as to send the mileage data to the body domain controller and the Internet of Vehicles controller; its microcontroller is configured with an EEPROM, which is provided with multiple storage space blocks, each of which is used to store the vehicle's mileage data to ensure data accuracy.

[0181] For the slave cockpit domain controller, its instrument service module is mainly used to obtain the vehicle's mileage data as the first mileage backup data and write it into the microcontroller. The microcontroller is configured with an EEPROM, and the EEPROM is provided with multiple storage space blocks. Each storage space block is used to store the vehicle's mileage data to ensure data accuracy.

[0182] The body domain controller is configured with a mileage backup service, which is used to implement local backup, that is, to store the mileage data sent by the main cockpit domain controller as the second mileage backup data.

[0183] The Internet of Vehicles controller is configured with a data upload service, which is used to send the mileage data sent by the main cockpit domain controller to the cloud backup server.

[0184] The cloud backup server is configured with a TSP backup service, which is used to implement cloud backup, that is, to store the mileage data sent by the Internet of Vehicles server as third mileage backup data.

[0185] The cloud diagnostic server is configured with a cloud diagnostic service, which is used to obtain the third mileage backup data stored by the cloud backup server and return it to the diagnostic instrument.

[0186] Reference Figure 6 The specific process of implementing mileage data display in this application is as follows: steps S501-S507.

[0187] S501, when the vehicle is powered on, the instrument service module of the main cockpit domain controller obtains mileage data from the microcontroller of the main cockpit domain controller through the internal interface, and displays the mileage after processing by the preset algorithm of its instrument service.

[0188] S502, during the driving process of the vehicle, the instrument service module of the cockpit domain controller obtains the vehicle's mileage data as the first mileage backup data based on the vehicle's real-time speed and driving time. If the vehicle meets the writing conditions, the instrument service module of the cockpit domain controller writes the first mileage backup data into the microcontroller of the cockpit domain controller.

[0189] Furthermore, the instrument service module of the main cockpit domain controller obtains the mileage data of the vehicle according to the real-time speed and driving time of the vehicle and displays it cumulatively based on the original mileage data. At the same time, the instrument service module of the main cockpit domain controller sends the mileage data to the body domain controller and the Internet of Vehicles controller. The body domain controller stores the mileage data as the second mileage backup data through its mileage backup service. The Internet of Vehicles controller sends the mileage data sent by the main cockpit domain controller to the cloud backup server through its data upload service. The cloud backup server stores the mileage data sent by the Internet of Vehicles server as the third mileage backup data through its TSP backup service. In addition, after obtaining the mileage data of the vehicle, if the vehicle meets the write conditions, the instrument service module of the main cockpit domain controller writes the mileage data to the microcontroller of the main cockpit domain controller.

[0190] The write condition includes at least one of the following: A power-off command of the vehicle is detected, and the power-off command is used to control the vehicle to power off; The vehicle's mileage write difference is greater than a preset mileage threshold, and the mileage write difference is the difference between the mileage data at the current moment and the mileage data most recently written to the microcontroller of the main cockpit domain controller; The vehicle's mileage writing duration is greater than the preset duration threshold, and the mileage writing duration is the difference between the current moment and the time value of the most recent write processing to the microcontroller of the main cockpit domain controller.

[0191] If a power-off command of the vehicle is detected, the vehicle is powered off and the process returns to step S501 to wait for the vehicle to be started again.

[0192] S503, receiving an external zeroing instruction, and clearing the mileage data stored in the main cockpit domain controller, the first mileage backup data stored in the cockpit domain controller, the second mileage backup data stored in the body domain controller, and the third mileage backup data stored in the cloud backup server according to the zeroing instruction.

[0193] S504, if a fault in the main cockpit domain controller is detected, the diagnostic instrument controls the activation of the slave cockpit domain controller and disables the main cockpit domain controller at the same time.

[0194] S505, the diagnostic instrument directly obtains the first mileage backup data of the vehicle from the cockpit domain controller; and, the diagnostic instrument sends a second data acquisition request to the body domain controller, and the body domain controller returns the second mileage backup data of the vehicle to the diagnostic instrument based on the second data acquisition request; and, the diagnostic instrument sends a third data acquisition request to the cloud diagnostic server, and the third data acquisition request carries the target identification code of the vehicle, and the cloud diagnostic server obtains the third mileage backup data corresponding to the target identification code from the cloud backup server and returns it to the diagnostic instrument.

[0195] S506, determining total mileage backup data according to the second mileage backup data and the third mileage backup data.

[0196] For example, from among the second mileage backup data and the third mileage backup data, the maximum value of the mileage backup data is selected as the total mileage backup data.

[0197] For another example, the communication data of the vehicle and the risk data of the body domain controller are integrated into one-dimensional sequence data, and the one-dimensional sequence data is input into a pre-trained first deep learning model. The confidence of the second mileage backup data at multiple future moments is predicted by the first deep learning model, and then the confidence sequence of the second mileage backup data is obtained; the mean of the confidence of the second mileage backup data at multiple future moments is calculated as the first confidence of the second mileage backup data. Also, the communication data of the vehicle and the risk data of the cloud backup device are integrated into one-dimensional sequence data, and the one-dimensional sequence data is input into a pre-trained second deep learning model. The confidence of the third mileage backup data at multiple future moments is predicted by the second deep learning model, and then the confidence sequence of the third mileage backup data is obtained; the mean of the confidence of the third mileage backup data at multiple future moments is calculated as the second confidence of the third mileage backup data. Among the second mileage backup data and the third mileage backup data, the mileage backup data with the largest confidence is selected as the total mileage backup data.

[0198] Among them, the communication data includes the protocol efficiency of the first link and the protocol efficiency of the second link; the first link is the communication link connecting the body domain controller and the main cockpit domain controller, and the second link is composed of the first sub-link connecting the main cockpit domain controller and the Internet of Vehicles controller and the second sub-link connecting the Internet of Vehicles controller and the cloud backup server.

[0199] The protocol efficiency of the first link is the ratio of the total amount of data received by the body domain controller to the transmission duration of the first link. The transmission duration of the first link is the difference between the actual transmission duration of the first link and the packet loss duration of the first link. The actual transmission duration of the first link is the difference between the time value when the body domain controller receives the mileage data and the time value when the main cockpit domain controller sends the mileage data. The packet loss duration of the first link is the duration of packet loss during the transmission process of the first link. The protocol efficiency of the second link may include the sum of the protocol efficiency of the first sub-link and the protocol efficiency of the second sub-link, the protocol efficiency of the first sub-link is the ratio of the total amount of data received by the Internet of Vehicles controller to the transmission duration of the first sub-link, the transmission duration of the first sub-link is the difference between the actual transmission duration of the first sub-link and the packet loss duration of the first sub-link, the actual transmission duration of the first sub-link is the difference between the time value when the Internet of Vehicles controller receives the mileage data and the time value when the main cockpit domain controller sends the mileage data, and the packet loss duration of the first sub-link is the duration of the packet loss phenomenon during the transmission process of the first sub-link; the protocol efficiency of the second sub-link is the ratio of the total amount of data received by the cloud backup device to the transmission duration of the second sub-link; the transmission duration of the second sub-link is the difference between the actual transmission duration of the second sub-link and the packet loss duration of the second sub-link, the actual transmission duration of the second sub-link is the difference between the time value when the cloud backup device receives the mileage data and the time value when the Internet of Vehicles controller sends the mileage data, and the packet loss duration of the second sub-link is the duration of the packet loss phenomenon during the transmission process of the second sub-link.

[0200] The risk data of the body domain controller include the failure frequency and data modification frequency of the body domain controller. The failure frequency of the body domain controller is the ratio of the number of failures of the body domain controller within a preset time period to the preset time period. The data modification frequency of the body domain controller is the ratio of the number of times the second mileage backup data is modified or accessed without authorization within the preset time period to the preset time period.

[0201] The risk data of the cloud backup device includes the data modification frequency of the cloud backup device. The data modification frequency of the cloud backup device is the ratio of the number of times the third-mile backup data is modified or accessed without authorization within a preset time period to the preset time period.

[0202] S507, if the total mileage backup data is greater than the first mileage backup data, the total mileage backup data is determined as the target mileage data displayed by the vehicle; or, if the total mileage backup data is less than or equal to the first mileage backup data, the first mileage data is determined as the target mileage data displayed by the vehicle.

[0203] In some selectable embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the boxes can sometimes be executed in reverse order. In addition, the embodiment presented and described in the flow chart of the application is provided by way of example, for the purpose of providing a more comprehensive understanding of technology. The disclosed method is not limited to the operation and logic flow presented herein. Selectable embodiments are expected, wherein the order of various operations is changed and the sub-operation of a part for which is described as a larger operation is performed independently.

[0204] In addition, although the present application is described in the context of functional modules, it should be understood that, unless otherwise specified, one or more of the functions and / or features can be integrated into a single physical device and / or software module, or one or more functions and / or features can be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the present application. More specifically, in view of the properties, functions, and internal relationships of the various functional modules in the device disclosed herein, the actual implementation of the module will be understood within the conventional techniques of the engineer. Therefore, those skilled in the art can implement the present application set forth in the claims without excessive experimentation using ordinary techniques. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present application, which is determined by the full scope of the attached claims and their equivalents.

[0205] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several programs to enable a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, and other media that can store program codes.

[0206] The logic and / or steps represented in the flowchart or otherwise described herein, for example, may be considered as an ordered list of executable programs for implementing logical functions, and may be embodied in any computer-readable medium for use by a program execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch and execute a program from a program execution system, device or apparatus), or in conjunction with such program execution system, device or apparatus. For purposes of this specification, a "computer-readable medium" may be any device that can contain, store, communicate, propagate or transmit a program for use by a program execution system, device or apparatus, or in conjunction with such program execution system, device or apparatus.

[0207] More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be a paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or, if necessary, processing in another suitable manner, and then stored in a computer memory.

[0208] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable program execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0209] In the above description of this specification, the description with reference to the terms "one embodiment / example", "another embodiment / example" or "certain embodiments / examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0210] Although the embodiments of the present application have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present application, and that the scope of the present application is defined by the claims and their equivalents.

[0211] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the described embodiments. Technical personnel familiar with the field may make various equivalent modifications or substitutions without violating the spirit of the present application. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present application.

Claims

1. A vehicle mileage data display method, characterized in that: The method comprises the following steps: In the case of detecting a failure of a main cockpit domain controller of a vehicle, enabling a slave cockpit domain controller of the vehicle, and acquiring the first mileage backup data of the vehicle from the slave cockpit domain controller; Acquire the second mileage backup data of the vehicle from the body domain controller of the vehicle; Acquire the third mileage backup data of the vehicle from a cloud backup device; The target mileage data displayed by the vehicle is determined according to the first mileage backup data, the second mileage backup data and the third mileage backup data.

2. The vehicle mileage data display method according to claim 1, characterized in that: The determining the target mileage data displayed by the vehicle according to the first mileage backup data, the second mileage backup data and the third mileage backup data includes: determining total mileage backup data according to the second mileage backup data and the third mileage backup data; The target mileage data displayed by the vehicle is determined according to the total mileage backup data and the first mileage backup data.

3. The vehicle mileage data display method according to claim 2, characterized in that: The determining of the total mileage backup data according to the second mileage backup data and the third mileage backup data includes: Obtaining a first confidence level of the second mileage backup data and a second confidence level of the third mileage backup data according to the communication data of the vehicle, the risk data of the vehicle body domain controller, and the risk data of the cloud backup device; The total mileage backup data is determined according to the second mileage backup data, the third mileage backup data, the first confidence level, and the second confidence level.

4. The vehicle mileage data display method according to claim 3, characterized in that: The obtaining, according to the communication data of the vehicle, the risk data of the vehicle body domain controller and the risk data of the cloud backup device, a first confidence level of the second mileage backup data and a second confidence level of the third mileage backup data comprises: Obtaining a confidence sequence of the second mileage backup data according to the communication data of the vehicle and the risk data of the vehicle body domain controller, wherein the confidence sequence of the second mileage backup data includes confidences of the second mileage backup data at multiple future moments; Obtaining a confidence sequence of the third mileage backup data according to the communication data of the vehicle and the risk data of the cloud backup device, wherein the confidence sequence of the third mileage backup data includes confidences of the third mileage backup data at multiple future moments; Obtaining a first confidence level of the second mileage backup data according to the confidence level sequence of the second mileage backup data; According to the confidence sequence of the third mileage backup data, a second confidence of the third mileage backup data is obtained.

5. The vehicle mileage data display method according to claim 3, characterized in that: The determining the total mileage backup data according to the second mileage backup data, the third mileage backup data, the first confidence level, and the second confidence level includes: Among the second mileage backup data and the third mileage backup data, the mileage backup data with the highest confidence is selected as the total mileage backup data.

6. The vehicle mileage data display method according to claim 2, characterized in that: The determining, according to the total mileage backup data and the first mileage backup data, target mileage data displayed by the vehicle includes: If the total mileage backup data is greater than the first mileage backup data, determining the total mileage backup data as the target mileage data displayed by the vehicle; Alternatively, if the total mileage backup data is less than or equal to the first mileage backup data, the first mileage data is determined as the target mileage data displayed by the vehicle.

7. The vehicle mileage data display method according to claim 1, characterized in that: The method further comprises the following steps: Receive a zeroing instruction; In response to the zeroing instruction, the slave cockpit domain controller, the master cockpit domain controller, the body domain controller and the cloud backup device are zeroed.

8. The vehicle mileage data display method according to claim 1, characterized in that: Before detecting a failure of the main cockpit domain controller of the vehicle, the method further comprises the following steps: Acquiring the mileage data of the vehicle through the instrument service module of the main cockpit domain controller and writing the mileage data into the microcontroller of the main cockpit domain controller, and sending the mileage data to the body domain controller and the cloud backup device; storing the mileage data as the second mileage backup data through the vehicle body domain controller; The mileage data is stored as the third mileage backup data through the cloud backup device.

9. The vehicle mileage data display method according to claim 8, characterized in that: The microcontroller that writes the mileage data into the main cockpit domain controller includes: If the vehicle meets the writing condition, the mileage data is written to the microcontroller of the main cockpit domain controller through the instrument service module of the main cockpit domain controller, and the writing condition includes at least one of the following: detecting a power-off instruction of the vehicle, the power-off instruction being used to control power-off of the vehicle; The mileage write difference of the vehicle is greater than a preset mileage threshold, and the mileage write difference is the difference between the mileage data at the current moment and the mileage data most recently written to the microcontroller of the main cockpit domain controller; The mileage writing duration of the vehicle is greater than a preset duration threshold, and the mileage writing duration is the difference between the current moment and the time value of the most recent writing process to the microcontroller of the main cockpit domain controller.

10. A vehicle mileage data display device, characterized in that: include: A first processing module is used to enable a slave cockpit domain controller of the vehicle and obtain first mileage backup data of the vehicle from the slave cockpit domain controller when a failure of the master cockpit domain controller of the vehicle is detected; A second processing module, configured to obtain second mileage backup data of the vehicle from a body domain controller of the vehicle; A third processing module, used for obtaining the third mileage backup data of the vehicle from the cloud backup device; The fourth processing module is used to determine the target mileage data displayed by the vehicle according to the first mileage backup data, the second mileage backup data and the third mileage backup data.

11. A vehicle mileage data display system, characterized in that: include: A vehicle mileage data display device as claimed in claim 10; A vehicle controller group, comprising a master cockpit domain controller, a slave cockpit domain controller and a body domain controller, wherein the master cockpit domain controller is used to obtain mileage data of the vehicle and send it to the body domain controller and a cloud backup device associated with the vehicle, the slave cockpit domain controller is used to obtain mileage data of the vehicle and store the mileage data as first mileage backup data, and the body domain controller is used to store the mileage data sent by the master cockpit domain controller as second mileage backup data; The cloud backup device is used to store the mileage data sent by the main cockpit domain controller as third mileage backup data.

12. A vehicle, characterized in that: include: at least one processor; at least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the vehicle mileage data display method as described in any one of claims 1 to 9.

Images