Method and device for synchronizing vehicle attribute data between vehicle operating systems
By synchronizing vehicle attribute data between vehicle operating systems, the problem of data inconsistency in multi-system architecture is solved. Data fallback is avoided through the reverse synchronization mechanism, ensuring the correctness and consistency of the data and improving the reliability of the system sex.
Patent Information
- Application Number
- CN202411162613.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-23
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2044-08-23
AI Technical Summary
In a multi-system architecture, the synchronization of vehicle attribute data between on-board operating systems has the risk of unexpected data fallback, resulting in data inconsistency and affecting the provision and functional implementation of higher-level services.
By synchronizing vehicle attribute data between on-board operating systems, the data that needs to be synchronized is obtained, invalid data is determined, and stored locally as the basis for reverse synchronization, avoiding data backs caused by single direction synchronization and ensuring data Correctness.
It effectively avoids the risk of unexpected data regression during vehicle attribute data synchronization, ensures the correctness and consistency of data, and improves the reliability and stability of the system.
Smart Images

Figure CN118677910B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present specification generally relate to the field of vehicle-mounted communication technology, and more specifically, to a method and apparatus for synchronizing vehicle attribute data between vehicle-mounted operating systems. Background Art
[0002] The vehicle operating system runs on the vehicle chip. It is a collection of software that manages and controls the software and hardware resources of intelligent connected vehicles. It mainly provides a control platform for in-vehicle infotainment (IVI) and human-computer interaction in the vehicle. It is the operating environment for the vehicle to realize cockpit intelligence and multi-source information fusion. As the functions of vehicles gradually become richer and more intelligent from a single safe driving function, a single system can no longer meet the diverse functional requirements, and the architecture of the vehicle operating system has also begun to change from a single system architecture to a multi-system architecture.
[0003] In a multi-system architecture, different in-vehicle operating systems often need to synchronize vehicle attribute data to further provide a data basis for various higher-level functional software, application algorithm software, and various automotive services. Therefore, accurate and efficient synchronization of vehicle attribute data between different in-vehicle operating systems has become an important guarantee for the smooth provision of various in-vehicle services. Summary of the invention
[0004] In view of the above, the embodiments of this specification provide a method, device and system for synchronizing vehicle attribute data between vehicle-mounted operating systems. By using the scheme for synchronizing vehicle attribute data between vehicle-mounted operating systems, the vehicle attribute data to be synchronized can be obtained from the first vehicle-mounted operating system, and then invalid vehicle attribute data can be determined, and the corresponding current vehicle attribute data stored locally can be sent to the first vehicle-mounted operating system as the data basis for reverse synchronization of vehicle attribute data, thereby effectively avoiding the risk of accidental data rollback that may be caused when synchronizing vehicle attribute data from the first vehicle-mounted operating system to the second vehicle-mounted operating system in a single direction, and effectively ensuring the correctness of the synchronized vehicle attribute data.
[0005] According to one aspect of an embodiment of the present specification, a method for synchronizing vehicle attribute data between vehicle operating systems is provided, which is applied to a second vehicle operating system, and the method includes: obtaining a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid from a first vehicle operating system; determining whether the corresponding first attribute value is valid based on the obtained first data validity information; selecting a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system; and sending the selected second attribute value to the first vehicle operating system, so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value.
[0006] According to another aspect of an embodiment of the present specification, a method for synchronizing vehicle attribute data between vehicle operating systems is provided, which is applied to a first vehicle operating system, and the method includes: receiving a second attribute value corresponding to a target vehicle attribute sent by a second vehicle operating system; querying first data validity status information corresponding to the target vehicle attribute from first data validity status information stored in the first vehicle operating system for indicating whether the first attribute value corresponding to each vehicle attribute is valid; determining whether the corresponding first attribute value is valid based on the queried first data validity status information; and in response to determining that the corresponding first attribute value is invalid, updating the invalid first attribute value to the corresponding second attribute value.
[0007] According to another aspect of an embodiment of the present specification, a method for synchronizing vehicle attribute data between vehicle operating systems is provided, including: a second vehicle operating system obtains a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid from a first vehicle operating system; the second vehicle operating system determines whether the corresponding first attribute value is valid based on the obtained first data validity information; the second vehicle operating system selects a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the stored second attribute values corresponding to each vehicle attribute; the second vehicle operating system sends the selected second attribute value to the first vehicle operating system; the first vehicle operating system queries the first data validity status information corresponding to each vehicle attribute stored for first data validity status information corresponding to the same target vehicle attribute as the selected second attribute value; the first vehicle operating system determines whether the corresponding first attribute value is valid based on the queried first data validity status information; and in response to determining that the corresponding first attribute value is invalid, the first vehicle operating system updates the invalid first attribute value to the corresponding second attribute value.
[0008] According to another aspect of an embodiment of the present specification, a device for synchronizing vehicle attribute data between vehicle operating systems is provided, which is applied to a second vehicle operating system, and the device includes: a data acquisition unit, configured to acquire a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid from the first vehicle operating system; a data validity determination unit, configured to determine whether the corresponding first attribute value is valid based on the acquired first data validity information; a data selection unit, configured to select a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system; and a data sending unit, configured to send the selected second attribute value to the first vehicle operating system, so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value.
[0009] According to another aspect of an embodiment of the present specification, there is provided a device for synchronizing vehicle attribute data between vehicle operating systems, which is applied to a first vehicle operating system, and the device includes: a data receiving unit, configured to receive a second attribute value corresponding to a target vehicle attribute sent by a second vehicle operating system; a data query unit, configured to query first data validity status information corresponding to the target vehicle attribute from first data validity status information stored in the first vehicle operating system for indicating whether the first attribute value corresponding to each vehicle attribute is valid; a data validity determination unit, configured to determine whether the corresponding first attribute value is valid based on the queried first data validity status information; and a data update unit, configured to update the invalid first attribute value to the corresponding second attribute value in response to determining that the corresponding first attribute value is invalid.
[0010] According to another aspect of an embodiment of the present specification, a device for synchronizing vehicle attribute data between vehicle operating systems is provided, including: a data transmission unit, configured to transmit a first attribute value corresponding to a vehicle attribute obtained from a first vehicle operating system and first data validity status information indicating whether the first attribute value is valid to a second vehicle operating system; and send a second attribute value selected by the second vehicle operating system to the first vehicle operating system; a data validity determination unit, configured to determine whether the corresponding first attribute value is valid according to the first data validity information obtained by the second vehicle operating system; and determine whether the corresponding first attribute value is valid according to the first data validity status information queried by the first vehicle operating system; a data selection unit, configured to select a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system; a data query unit, configured to query first data validity status information corresponding to the same target vehicle attribute as the selected second attribute value from the first data validity status information corresponding to each vehicle attribute stored in the first vehicle operating system; and a data update unit, configured to update the invalid first attribute value in the first vehicle operating system to the corresponding second attribute value in response to determining that the corresponding first attribute value is invalid.
[0011] According to another aspect of an embodiment of the present specification, a vehicle-mounted system is provided, comprising: a first vehicle-mounted operating system, configured to execute the method for synchronizing vehicle attribute data between vehicle-mounted operating systems as described above and applied to the first vehicle-mounted operating system; and a second vehicle-mounted operating system, configured to execute the method for synchronizing vehicle attribute data between vehicle-mounted operating systems as described above and applied to the second vehicle-mounted operating system.
[0012] According to another aspect of an embodiment of the present specification, there is provided an electronic device, comprising: at least one processor, and a memory coupled to the at least one processor, the memory storing a computer program, and the at least one processor executing the computer program to implement the method for synchronizing vehicle attribute data between in-vehicle operating systems as described above.
[0013] According to another aspect of the embodiments of the present specification, a computer-readable storage medium is provided, which stores executable instructions. When the executable instructions are executed by a processor, the method for synchronizing vehicle attribute data between vehicle-mounted operating systems as described above is implemented. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] A further understanding of the nature and advantages of the content of this specification may be achieved by referring to the following drawings. In the drawings, similar components or features may have the same reference numerals.
[0015] Figure 1 An exemplary scenario of a method and apparatus for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification is shown.
[0016] Figure 2 A flowchart showing an example of a method for synchronizing vehicle attribute data between in-vehicle operating systems, which is applied to a second in-vehicle operating system according to an embodiment of the present specification.
[0017] Figure 3 A flowchart of an example of a process for acquiring a first attribute value and first data validity status information according to an embodiment of the present specification is shown.
[0018] Figure 4 A flowchart showing yet another example of a method for synchronizing vehicle attribute data between in-vehicle operating systems, which is applied to a second in-vehicle operating system according to an embodiment of the present specification.
[0019] Figure 5 A flowchart showing still another example of a method for synchronizing vehicle attribute data between in-vehicle operating systems, which is applied to a second in-vehicle operating system according to an embodiment of the present specification.
[0020] Figure 6 A flowchart showing an example of a method for synchronizing vehicle attribute data between in-vehicle operating systems, which is applied to a first in-vehicle operating system according to an embodiment of the present specification.
[0021] Figure 7 A signaling diagram showing another example of a method for synchronizing vehicle attribute data between in-vehicle operating systems according to an embodiment of the present specification.
[0022] Figure 8 A block diagram showing an example of a device for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification.
[0023] Fig. 9 A block diagram showing yet another example of an apparatus for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification.
[0024] Fig.10 A block diagram showing still another example of an apparatus for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification.
[0025] Fig.11 A block diagram showing an example of an in-vehicle system according to an embodiment of the present specification.
[0026] Fig.12 A schematic diagram showing an example of an electronic device according to an embodiment of the present specification. DETAILED DESCRIPTION
[0027] The subject matter described herein will be discussed below with reference to example implementations. It should be understood that the discussion of these implementations is only to enable those skilled in the art to better understand and implement the subject matter described herein, and is not a limitation of the scope of protection, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of protection of the embodiments of this specification. Various processes or components may be omitted, substituted or added to each example as needed. In addition, the features described relative to some examples may also be combined in other examples.
[0028] As used herein, the term "including" and its variations represent open terms, meaning "including but not limited to". The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other definitions may be included below, whether explicit or implicit. Unless the context clearly indicates otherwise, the definition of a term is consistent throughout the specification.
[0029] In this specification, the term "vehicle attribute data" may refer to various data corresponding to vehicle attributes, such as attribute values, data validity status information indicating whether the attribute values are valid, etc. "Vehicle attributes" can be used to describe information of various dimensions of a vehicle, such as the characteristics of the vehicle, the state it is in, etc. In some examples, "vehicle attributes" may include but are not limited to vehicle speed, acceleration, steering angle, engine speed, remaining fuel, air conditioning status, seat status, etc. In some examples, "vehicle attributes" may be embodied as the concept of Vehicle Property in the Android Automotive operating system.
[0030] At present, in some implemented systems, such as a multi-system architecture composed of an Android Automotive operating system and a QNX operating system, the synchronization operation is usually initiated by the Android Automotive side, and the vehicle attribute data obtained from the QNX side is used to update the corresponding information on the Android Automotive side. However, the inventors have found that in some cases, this one-way vehicle attribute data synchronization mechanism cannot guarantee that the vehicle attribute data obtained from the QNX side is in the latest state. For example, after the vehicle operating system has been working normally for a period of time, the Android Automotive side has synchronized the latest vehicle attribute data from the QNX side. If the QNX side is restarted for some reason, the vehicle attribute data will be restored to the default value, and the Android Automotive side will also re-establish a connection with the QNX side. At this time, if the Android Automotive side still obtains the vehicle attribute data from the QNX side for synchronization, it is very likely that the vehicle attribute data that was originally in an updated state will fall back to the default value, which will in turn have an adverse impact on the service provision and function implementation of the upper layer.
[0031] In view of this, the embodiments of this specification propose a solution for synchronizing vehicle attribute data between vehicle-mounted operating systems. In the solution for synchronizing vehicle attribute data between vehicle-mounted operating systems, the vehicle attribute data to be synchronized can be obtained from the first vehicle-mounted operating system, and then invalid vehicle attribute data can be determined, and the corresponding current vehicle attribute data stored locally can be sent to the first vehicle-mounted operating system as the data basis for reverse synchronization of the vehicle attribute data, thereby effectively avoiding the risk of accidental data rollback that may be caused when synchronizing vehicle attribute data from the first vehicle-mounted operating system to the second vehicle-mounted operating system in a single direction, and effectively ensuring the correctness of the synchronized vehicle attribute data.
[0032] The flowcharts used in this specification illustrate the operations implemented by the system according to some embodiments in this specification. It should be clearly understood that the operations of the flowcharts may not be implemented in sequence. On the contrary, the operations may be implemented in reverse order or simultaneously. In addition, one or more other operations may be added to the flowchart. One or more operations may be removed from the flowchart.
[0033] The method and device for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification will be described in detail below with reference to the accompanying drawings.
[0034] Figure 1 An exemplary scenario 100 of a method and apparatus for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of this specification is shown.
[0035] like Figure 1 As shown, the method and device for synchronizing vehicle attribute data between vehicle operating systems in the embodiment of this specification can be applied to the vehicle chip of the car 102. In this embodiment, the first vehicle operating system 112 and the second vehicle operating system 114 can run on the same set of hardware (such as a vehicle chip) to form a multi-system architecture. The first vehicle operating system 112 and the second vehicle operating system 114 can further provide a data basis for various higher-level functional software, application algorithm software and various automobile services by synchronizing vehicle attribute data.
[0036] In some examples, the first vehicle operating system 112 may be a basic operating system involving the underlying operating system and all system components (such as the system kernel, underlying drivers, virtual machines, etc.), such as QNX, Linux, etc. In some examples, the second vehicle operating system 114 may be a customized operating system that is customized and developed on top of the basic operating system (such as modifying the kernel, hardware drivers, runtime environment, application framework, etc.), such as Android Automotive, Hongmeng OS, AliOS, etc. In these examples, when the power system of the vehicle starts working, for example, the vehicle is in ACC (accessory) mode, since the first vehicle operating system 112 is closer to the hardware layer than the second vehicle operating system 114, the first vehicle operating system 112 can often be started earlier than the second vehicle operating system 114 and can update the vehicle attribute data to the latest state earlier. In some cases, the first vehicle operating system 112 may be restarted. In some cases, the second vehicle operating system 114 may also be restarted. In some cases, the first vehicle operating system 112 and the second vehicle operating system 114 may be reconnected due to various factors. In the above-mentioned cases, the problem of inconsistent vehicle attribute data between the first vehicle operating system 112 and the second vehicle operating system 114 can be solved by using a method of synchronizing vehicle attribute data between vehicle operating systems.
[0037] It is understood that the above-mentioned multi-system architecture of the embodiments of this specification may also include more vehicle-mounted operating systems. The various vehicle-mounted operating systems may form a multi-system infrastructure based on at least one of hardware isolation technology, virtual machine manager (Hypervisor) technology, and container technology. It should also be understood that the embodiments of this specification are not limited to the exemplary scenarios described above, but can also be applied to any variations of these exemplary scenarios and any other applicable scenarios.
[0038] Figure 2 A flowchart showing an example of a method 200 for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification is shown. The method may be applied to a second vehicle operating system.
[0039] like Figure 2 As shown, in step S210, a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid may be obtained from the first vehicle operating system. In some examples, for a vehicle attribute whose attribute value is to be obtained, the second vehicle operating system may obtain the first attribute value corresponding to the vehicle attribute and first data validity status information indicating whether the first attribute value is valid from the first vehicle operating system. It is understood that the vehicle attribute whose attribute value is to be obtained may be all or part of the vehicle attributes stored in the first vehicle operating system.
[0040] In some examples, the attribute values corresponding to various vehicle attributes stored locally in the first vehicle operating system may be referred to as "first attribute values". In some examples, there may be multiple vehicle attributes, such as vehicle speed, steering angle, air conditioning status, etc. The first vehicle operating system may obtain the attribute value corresponding to each attribute in various ways. In some examples, the first vehicle operating system may obtain the attribute values corresponding to various attributes through a vehicle bus, such as a CAN (Controller Area Network) bus, and store them locally in the first vehicle operating system as first attribute values. For example, the attribute value corresponding to the vehicle attribute "vehicle speed" may be "45km / h", the attribute value corresponding to the vehicle attribute "steering angle" may be "turn left 10°", and the attribute value corresponding to the vehicle attribute "air conditioning status" may be "turn on cooling".
[0041] Furthermore, the first vehicle operating system may locally store first data validity status information indicating whether the first attribute value is valid. In some examples, the first data validity status information may be in multiple forms. For example, "0" may be used to indicate that the corresponding first attribute value is invalid, and "1" may be used to indicate that the corresponding first attribute value is valid. For another example, the first data validity status information may also be used to indicate how long it will take for the corresponding first attribute value to become invalid. For another example, the first data validity status information may also be used to indicate whether the corresponding first attribute value has been updated. In some examples, the first data validity status information is typically maintained by the first vehicle operating system.
[0042] In some implementations, the first vehicle operating system may include QNX and the second vehicle operating system may include Android. In some examples, the second vehicle operating system may be Android Automotive.
[0043] In step S220, it can be determined whether the corresponding first attribute value is valid according to the acquired first data validity information. In some examples, it can be determined whether each acquired first attribute value is valid. In one example, it can be determined whether the corresponding first attribute value is valid directly according to the first data validity information indicating whether the data is valid. In another example, the first attribute value indicating that it has been updated can be determined as valid data, and the first attribute value indicating that it has not been updated can be determined as invalid data.
[0044] In step S230, a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value may be selected from the second attribute values corresponding to the various vehicle attributes stored in the second vehicle operating system. In some examples, the attribute values corresponding to the various vehicle attributes stored locally in the second vehicle operating system may be referred to as "second attribute values". Typically, the first attribute value and the second attribute value correspond to the same set of vehicle attributes. For example, if there are 50 vehicle attributes, the first attribute values corresponding to the 50 vehicle attributes may be stored in the first vehicle operating system, and the second attribute values corresponding to the 50 vehicle attributes may also be stored in the second vehicle operating system. It can be understood that since the first attribute value and the second attribute value corresponding to the same vehicle attribute can be stored in different vehicle operating systems, they may be different.
[0045] In some examples, if step S220 determines that the attribute value "turn on cooling" corresponding to the vehicle attribute "air conditioning status" is invalid, the second attribute value corresponding to the vehicle attribute "air conditioning status" (for example, "turn off") can be selected from the second attribute values stored in the second vehicle operating system.
[0046] In some examples, the vehicle attributes corresponding to the multiple invalid first attribute values determined in step S220 can be combined into a vehicle attribute group. Then, the second attribute values corresponding to the respective vehicle attributes in the above vehicle attribute group are selected from the stored second attribute values. For example, if step S220 determines that the attribute value "turn left 10°" corresponding to the vehicle attribute "steering angle" and the attribute value "sports mode" corresponding to the vehicle attribute "driving mode" are invalid, the vehicle attribute group {"steering angle", "driving mode"} can be determined first. Then, the second attribute values corresponding to the vehicle attributes "steering angle" and "driving mode" are selected from the stored second attribute values, such as "turn right 30°" and "energy-saving mode".
[0047] In step S240, the selected second attribute value is sent to the first vehicle operating system so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value. In some examples, referring to the aforementioned examples, the selected second attribute value (e.g., the second attribute value "off" corresponding to the vehicle attribute "air conditioning status") can be sent to the first vehicle operating system in various ways. In some cases, the first vehicle operating system can update the corresponding first attribute value (e.g., "turn on cooling") based on the above-mentioned selected second attribute value (e.g., "off"). It should be noted that the operation of the first vehicle operating system to update the corresponding first attribute value based on the selected second attribute value can refer to the following Figure 6 The detailed description of steps S620 to S640 will not be repeated here.
[0048] In some implementations, step S250 may be further executed to update the second attribute value corresponding to the corresponding vehicle attribute stored in the second vehicle operating system using the valid first attribute value. In some examples, if step S220 determines that the attribute value "45km / h" corresponding to the vehicle attribute "vehicle speed" is valid, the valid first attribute value (e.g., "45km / h") may be used to update the second attribute value corresponding to the corresponding vehicle attribute (e.g., "vehicle speed") stored in the second vehicle operating system. It is understandable that if step S220 determines multiple valid first attribute values, multiple second attribute values corresponding to the valid first attribute values may be updated accordingly. By synchronizing vehicle attribute data only based on the valid first attribute values, the correctness of the synchronized data can be guaranteed.
[0049] It should be understood that all steps and their order in process 200 are exemplary, and the embodiments of the present disclosure will also cover any modification of process 200. For example, in some implementations, step S250 may be performed after step S220, and then step S230 and step S240 may be performed.
[0050] Figure 3 FIG. 1 is a flowchart showing an example of a process 300 for obtaining a first attribute value and first data validity status information according to an embodiment of the present specification. Figure 2 An exemplary implementation of step S210 in .
[0051] like Figure 3As shown, in step S310, a first request for synchronizing vehicle attribute data may be sent to the first vehicle operating system. In some examples, the first request may include an attribute identifier of the vehicle attribute to be synchronized so that the first vehicle operating system can match the first attribute value corresponding to the vehicle attribute. In some examples, the first request may not include an attribute identifier of the vehicle attribute to be synchronized, indicating that the first attribute values corresponding to all vehicle attributes stored in the first vehicle operating system need to be obtained. In some examples, the first request may also include attribute identifiers of all vehicle attributes and the corresponding attribute values are all empty, indicating that the first attribute values corresponding to all vehicle attributes with empty corresponding attribute values need to be obtained. In some examples, the vehicle hardware abstraction layer (VehicleHal) of the second vehicle operating system Android Automotive may send a first request for synchronizing vehicle attribute data to a specific component in the first vehicle operating system QNX. In some examples, the above-mentioned specific component may be used to provide support for various vehicle service software at a higher level. For example, the above-mentioned specific component may be used to provide information conversion and information sending services between vehicle attribute data and vehicle signals for various functional modules in the QNX system. In one implementation, the above-mentioned specific component may be implemented as a functional module named VehicleService.
[0052] In some implementations, the sending of the first request may be performed in response to the second vehicle operating system re-establishing a communication connection with the first vehicle operating system. In some examples, the re-establishment of a communication connection between the second vehicle operating system and the first vehicle operating system may generally refer to the re-establishment of a communication connection between a target component in the second vehicle operating system and a corresponding component in the first vehicle operating system. For example, after the above-mentioned specific component in the first vehicle operating system is restarted, the vehicle hardware abstraction layer of the second vehicle operating system Android Automotive may re-establish a communication connection with the above-mentioned specific component. In some examples, whenever the communication connection is re-established between the above-mentioned two, the above-mentioned second vehicle operating system may send the above-mentioned first request to the first vehicle operating system.
[0053] In step S320, a response corresponding to the first request sent by the first vehicle operating system may be received. In this embodiment, the response corresponding to the first request may include first attribute values corresponding to each vehicle attribute to be synchronized and corresponding first data validity status information. In some examples, the first attribute values corresponding to each vehicle attribute to be synchronized and corresponding first data validity status information may exist in the form of a data packet in the response corresponding to the first request.
[0054] In step S330, the first attribute value corresponding to each vehicle attribute and the first data validity status information indicating whether the first attribute value is valid can be extracted from the response. In some examples, the above response can be parsed, and the first attribute value corresponding to each vehicle attribute and the first data validity status information indicating whether the first attribute value is valid can be extracted. In one example, the value corresponding to each variable VehiclePropValue can be parsed as the first attribute value, and the value of the status flag used to indicate the validity of the corresponding variable VehiclePropValue data is used as the corresponding first data validity status information. In one example, if the value of the status flag is "error" or "default", it can be determined that the corresponding first attribute value is invalid; if the value of the status flag is other values, it can be determined that the corresponding first attribute value is valid. It can be understood that other methods can also be used to determine whether each first attribute value is valid, which is not limited here.
[0055] use Figure 3 The method shown in provides a method for a second vehicle operating system to obtain initial attribute values and data validity status information by sending a first request for synchronizing vehicle attribute data to a first vehicle operating system and extracting the first attribute value corresponding to each vehicle attribute and the corresponding first data validity status information from the received response.
[0056] Figure 4 A flowchart showing yet another example of a method 400 for synchronizing vehicle attribute data between in-vehicle operating systems according to an embodiment of the present specification. Figure 4 is based on Figure 2 Another example process of the example process shown in Figure 4 Steps S410 to S420 and step S440 shown in FIG. Figure 2 The steps S210 to S220 and S240 shown in FIG. 1 are different in that: Figure 4 In order to avoid repeated description, only the differences are described here.
[0057] In this embodiment, each second attribute value may have second data validity status information for indicating whether the second attribute value is valid. The specific meaning of the second data validity status information can refer to the aforementioned Figure 2 The description of the first data valid status information in step S210 is just different in terms of the attribute value targeted, and the second data valid status information is usually maintained by the second vehicle-mounted operating system.
[0058] In step S430, a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value may be selected from the valid second attribute values corresponding to the various vehicle attributes stored in the second vehicle operating system. Figure 2 Based on the second attribute value selected in step S230, the second attribute value indicated by the second data validity status information is further selected. In some examples, the second attribute value indicated by the second data validity status information is first selected, and then the second attribute value corresponding to the same vehicle attribute as the invalid first attribute value is selected on this basis.
[0059] use Figure 4 The method shown in filters out invalid second attribute values through the second data valid status information, thereby ensuring that the selected second attribute value is in a valid state, and further ensuring that the second attribute value sent to the first vehicle operating system has a higher quality, avoiding the waste of resources caused by the sending of invalid information.
[0060] Figure 5 A flowchart showing another example of a method 500 for synchronizing vehicle attribute data between in-vehicle operating systems according to an embodiment of the present specification. Figure 5 is based on Figure 2 Another example process of the example process shown in Figure 5 Steps S510 to S530 shown in FIG. Figure 2 The steps S210 to S230 shown in FIG. 1 are different in that: Figure 5 In order to avoid repeated description, only the differences are described here.
[0061] In step S540, the selected second attribute value can be used as a request parameter to construct a second request for reverse synchronization of vehicle attributes. In this embodiment, the second request can at least include the selected second attribute value as the request parameter. In some examples, a second request including the second attribute value and the corresponding vehicle attribute can be constructed. For example, referring to the example of the aforementioned step S230, the constructed second request can include the attribute value "turn right 30°" of the vehicle attribute "steering angle" and the vehicle attribute "driving mode" and the attribute value "energy-saving mode". In some examples, the vehicle attribute corresponding to the selected second attribute value can be represented in a specific position in the constructed second request. In one example, each selected second attribute value can be stored in a corresponding position of an array for storing attribute values of all vehicle attributes. For example, the array for storing attribute values of all vehicle attributes contains 50 elements, and the selected attribute values "turn right 30°" and "energy-saving mode" can be stored in the position for storing the attribute value of the vehicle attribute "steering angle" (e.g., the 18th element) and the position for storing the attribute value of the vehicle attribute "driving mode" (e.g., the 27th element). Furthermore, other elements in the array for storing the attribute values of all vehicle attributes may be set to null. Thus, the above array may be used as a request parameter of the second request constructed for reverse synchronization of vehicle attributes.
[0062] In step S550, a second request is sent to the first vehicle operating system, so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value.
[0063] use Figure 5 The method shown in provides a mechanism for reversely synchronizing vehicle attribute data from the second vehicle operating system to the first vehicle operating system by constructing a second request for reverse synchronization of vehicle attributes based on the selected second attribute value and sending the second request to the first vehicle operating system.
[0064] use Figure 1-Figure 5 The method for synchronizing vehicle attribute data between vehicle operating systems disclosed in the disclosure can obtain the vehicle attribute data that needs to be synchronized from the first vehicle operating system, then determine the invalid vehicle attribute data therefrom, and then send the corresponding current vehicle attribute data stored locally to the first vehicle operating system as the data basis for reverse synchronization of the vehicle attribute data, thereby effectively avoiding the risks of unexpected data rollback that may be caused when synchronizing vehicle attribute data from the first vehicle operating system to the second vehicle operating system in a single direction, and effectively ensuring the correctness of the synchronized vehicle attribute data.
[0065] Figure 6A flowchart showing an example of a method 600 for synchronizing vehicle attribute data between in-vehicle operating systems according to an embodiment of the present specification is shown. The method may be applied to a first in-vehicle operating system.
[0066] like Figure 6 As shown, in step S610, the second attribute value corresponding to the target vehicle attribute sent by the second vehicle operating system can be received. In some examples, the second vehicle operating system can directly send the second attribute value corresponding to the target vehicle attribute. In some examples, the second vehicle operating system can send the second attribute value corresponding to the target vehicle attribute in the form of a second request as described in the aforementioned step S540. In these examples, the second attribute value corresponding to the target vehicle attribute can be extracted from the second request. For example, a second attribute value that is not empty can be extracted, and the vehicle attribute corresponding to the second attribute value is determined as the target vehicle attribute. For example, referring to the example of the aforementioned step S230, the second attribute values "turn right 30°" and "energy-saving mode" corresponding to the target vehicle attributes "steering angle" and "driving mode" can be received.
[0067] In step S620, the first data validity status information corresponding to the target vehicle attribute can be queried from the first data validity status information stored in the first vehicle operating system for indicating whether the first attribute value corresponding to each vehicle attribute is valid. In some examples, the first data validity status information can refer to the relevant description of the aforementioned step S210. For example, referring to the aforementioned example, the first data validity status information corresponding to the target vehicle attributes "steering angle" and "driving mode" can be queried from the first data validity status information stored in the first vehicle operating system for indicating whether the first attribute value corresponding to each vehicle attribute is valid.
[0068] In some implementations, the first data validity status information can be used to indicate at least one of the following: whether the first attribute value has been updated, whether the first attribute value is lost. In some examples, a first flag bit (e.g., valid) can be used to indicate whether the first attribute value has been updated. For example, if the value of the first flag bit is "true", it means that the first attribute value has been updated; if the value of the first flag bit is "false", it means that the first attribute value has not been updated. In some examples, a second flag bit (e.g., lost) can be used to indicate whether the first attribute value is in a lost state inside the first vehicle-mounted operating system. For example, if the value of the second flag bit is "true", it means that the first attribute value is in a lost state; if the value of the second flag bit is "false", it means that the first attribute value is not in a lost state.
[0069] In step S630, it can be determined whether the corresponding first attribute value is valid based on the first data valid status information queried. In some examples, reference can be made to the relevant description of the aforementioned step S220. In one example, referring to the example of the aforementioned step S230, it can be determined that the first attribute values "turn left 10°" and "sports mode" corresponding to the target vehicle attributes "steering angle" and "driving mode" are invalid based on the first data valid status information queried. In another example, before this, the first vehicle operating system may have updated the first attribute value "turn right 30°" corresponding to the target vehicle attribute "steering angle" through the vehicle bus and the corresponding first data valid status information is also updated accordingly to indicate that the first attribute value is valid. At this time, it can be determined that the first attribute value "turn right 30°" corresponding to the target vehicle attribute "steering angle" is valid based on the first data valid status information queried, and the first attribute value "sports mode" corresponding to the target vehicle attribute "driving mode" is invalid.
[0070] If step S630 is no, in S640, the invalid first attribute value may be updated to the corresponding second attribute value. In this embodiment, the corresponding invalid first attribute value may be updated using the received second attribute value. In some examples, referring to the example of the aforementioned step S630, for example, the invalid first attribute value "sports mode" may be updated to the corresponding second attribute value "energy saving mode". For another example, the invalid first attribute value "turn left 10°" may be updated to the corresponding second attribute value "turn right 30°".
[0071] In some implementations, if step S630 is yes, there is no need to update the valid first attribute value based on the corresponding second attribute value, thereby giving the vehicle attribute data of the first vehicle operating system a higher reliability, matching the more basic and reliable characteristics of the first vehicle operating system.
[0072] In some implementations, step S650 may be further performed to broadcast the updated first attribute value. In some examples, it may be further determined whether each first attribute value is in a lost state within the first vehicle-mounted operating system. If there is a first attribute value in a lost state, the corresponding updated first attribute value may be broadcast to correct the internal error state. If there is no first attribute value in a lost state, it may be further determined whether there is a subscription operation for the first attribute value. If so, the corresponding updated first attribute value may be broadcast so that the component subscribing to the first attribute value may be informed of the value update status in a timely manner.
[0073] use Figure 6The method shown in the embodiment sends the attribute value corresponding to the target vehicle attribute to the first vehicle operating system through the second vehicle operating system, and the first vehicle operating system updates the attribute value based on the attribute value provided by the second vehicle operating system according to the data validity information of the currently stored attribute value, thereby providing a more efficient and accurate vehicle attribute data synchronization mechanism.
[0074] Figure 7 A signaling diagram of another example of a method 700 for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification is shown. The method can be applied to a first vehicle operating system 702 and a second vehicle operating system 704 .
[0075] Figure 7 The processes involved in the signaling diagram shown can be referred to Figure 2 and Figure 6 The example process shown in . Figure 7 Steps S710 to S740 shown in FIG. Figure 2 Steps S210 to S240 shown in FIG. Figure 7 The steps S760-S770 shown in FIG. Figure 6 The steps S630-S640 shown in FIG. 1 are different in that: Figure 7 Step S750 shown in FIG. Figure 6 Steps S610 to S620 shown in FIG. 1 are modified adaptively. To avoid repeated description, only the differences are described here.
[0076] In step S750, the first vehicle operating system may query the first data valid state information corresponding to the same target vehicle attribute as the selected second attribute value from the first data valid state information corresponding to each stored vehicle attribute. In some examples, the target vehicle attribute here may refer to the vehicle attribute corresponding to the selected second attribute value, and thus may be understood with reference to the specific description of the aforementioned step S620.
[0077] use Figure 7 The method shown in the figure can first synchronize vehicle attribute data from the first vehicle operating system to the second vehicle operating system. Next, the second vehicle operating system can determine the invalid vehicle attribute data received, and send the corresponding current vehicle attribute data stored locally to the first vehicle operating system as the data basis for reverse synchronization of the vehicle attribute data. Furthermore, the first vehicle operating system can determine whether it is necessary to update the locally stored attribute values based on the vehicle attribute data sent by the second vehicle operating system based on the validity of the current vehicle attribute data. This provides a mechanism for bidirectional synchronization of vehicle attribute data based on data validity judgment, thereby ensuring the quality of the synchronized vehicle attribute data.
[0078] Figure 8 FIG. 8 is a block diagram showing an example of a device 800 for synchronizing vehicle attribute data between vehicle-mounted operating systems according to an embodiment of the present specification. Figure 2-Figure 5 Corresponding to the method embodiment shown, the device can be implemented by software, hardware or a combination of software and hardware, and can be specifically applied to various electronic devices.
[0079] like Figure 8 As shown, the device 800 for synchronizing vehicle attribute data between vehicle-mounted operating systems may include a data acquisition unit 810 , a data validity determination unit 820 , a data selection unit 830 and a data sending unit 840 .
[0080] The data acquisition unit 810 is configured to acquire, from the first vehicle operating system, a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid.
[0081] In some examples, the data acquisition unit 810 is further configured to: send a first request for synchronizing vehicle attribute data to the first vehicle operating system; receive a response corresponding to the first request sent by the first vehicle operating system; and extract first attribute values corresponding to each vehicle attribute and first data validity status information indicating whether the first attribute value is valid from the response.
[0082] In some examples, sending the first request is performed in response to the second in-vehicle operating system re-establishing a communication connection with the first in-vehicle operating system.
[0083] The data validity determination unit 820 is configured to determine whether the corresponding first attribute value is valid according to the acquired first data validity information.
[0084] The data selection unit 830 is configured to select a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system.
[0085] In some examples, each second attribute value has second data validity status information for indicating whether the second attribute value is valid. The data selection unit 830 is further configured to: select a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the valid second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system.
[0086] The data sending unit 840 is configured to send the selected second attribute value to the first vehicle operating system, so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value.
[0087] In some examples, the data sending unit 840 is further configured to: construct a second request for reverse synchronization of vehicle attributes using the selected second attribute value as a request parameter; and send the second request to the first vehicle operating system.
[0088] In some examples, the apparatus 800 for synchronizing vehicle attribute data between vehicle operating systems may further include a data updating unit 850 configured to update a second attribute value corresponding to a corresponding vehicle attribute stored in the second vehicle operating system using a valid first attribute value.
[0089] In some examples, the first in-vehicle operating system includes QNX and the second in-vehicle operating system includes Android.
[0090] Fig. 9 FIG. 1 is a block diagram showing another example of a device 900 for synchronizing vehicle attribute data between vehicle-mounted operating systems according to an embodiment of the present specification. Figure 6 Corresponding to the method embodiment shown, the device can be implemented by software, hardware or a combination of software and hardware, and can be specifically applied to various electronic devices.
[0091] like Fig. 9 As shown, the device 900 for synchronizing vehicle attribute data between vehicle-mounted operating systems may include a data receiving unit 910 , a data query unit 920 , a data validity determination unit 930 , and a data updating unit 940 .
[0092] The data receiving unit 910 is configured to receive a second attribute value corresponding to the target vehicle attribute sent by the second vehicle operating system.
[0093] The data query unit 920 is configured to query the first data validity status information corresponding to the target vehicle attribute from the first data validity status information stored in the first vehicle operating system and used to indicate whether the first attribute value corresponding to each vehicle attribute is valid.
[0094] In some examples, the first data validity status information is used to indicate at least one of the following: whether the first attribute value has been updated, and whether the first attribute value is lost.
[0095] The data validity determination unit 930 is configured to determine whether the corresponding first attribute value is valid according to the queried first data validity status information.
[0096] The data updating unit 940 is configured to update the invalid first attribute value to the corresponding second attribute value in response to determining that the corresponding first attribute value is invalid.
[0097] In some examples, the apparatus 900 for synchronizing vehicle attribute data between vehicle-mounted operating systems may further include a broadcast unit 950 configured to broadcast the updated first attribute value.
[0098] Fig.10 FIG. 1 is a block diagram showing another example of a device 1000 for synchronizing vehicle attribute data between vehicle-mounted operating systems according to an embodiment of the present specification. Figure 7 Corresponding to the method embodiment shown, the device can be implemented by software, hardware or a combination of software and hardware, and can be specifically applied to various electronic devices.
[0099] like Fig.10 As shown, the device 1000 for synchronizing vehicle attribute data between vehicle-mounted operating systems may include a data transmission unit 1010 , a data validity determination unit 1020 , a data selection unit 1030 , a data query unit 1040 and a data update unit 1050 .
[0100] The data transmission unit 1010 is configured to transmit a first attribute value corresponding to a vehicle attribute obtained from a first vehicle operating system and first data validity status information indicating whether the first attribute value is valid to a second vehicle operating system; and send a second attribute value selected by the second vehicle operating system to the first vehicle operating system.
[0101] The data validity determination unit 1020 is configured to determine whether the corresponding first attribute value is valid according to the first data validity information obtained by the second vehicle operating system; and determine whether the corresponding first attribute value is valid according to the first data validity status information queried by the first vehicle operating system.
[0102] The data selection unit 1030 is configured to select a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system.
[0103] The data query unit 1040 is configured to query the first data validity status information corresponding to the same target vehicle attribute as the selected second attribute value from the first data validity status information corresponding to each vehicle attribute stored in the first vehicle operating system.
[0104] The data updating unit 1050 is configured to update the invalid first attribute value in the first vehicle operating system to a corresponding second attribute value in response to determining that the corresponding first attribute value is invalid.
[0105] It can be understood that the specific description of the data acquisition unit 810, the data validity determination unit 820, the data selection unit 830 and the data sending unit 840, the data receiving unit 910, the data query unit 920, the data validity determination unit 930 and the data updating unit 940, the data transmission unit 1010, the data validity determination unit 1020, the data selection unit 1030, the data query unit 1040 and the data updating unit 1050 can refer to the aforementioned Figure 2-Figure 7 The specific steps in the embodiment will not be repeated here.
[0106] Fig.11 FIG. 1 is a block diagram showing an example of a vehicle-mounted system 1100 according to an embodiment of the present specification. The vehicle-mounted system embodiment can be used with Figure 2-Figure 7 Corresponding to the method embodiment shown, the device can be implemented by software, hardware or a combination of software and hardware, and can be specifically applied to various electronic devices.
[0107] like Fig.11 As shown, the vehicle system 1100 may include a first vehicle operating system 1110 and a second vehicle operating system 1120. The first vehicle operating system 1110 may be configured to execute the following Figure 6 The second vehicle operating system 1120 is configured to perform the following steps: Figure 2-Figure 5 A method of synchronizing vehicle attribute data between in-vehicle operating systems is described.
[0108] Reference above Figures 1 to 11 , describes an embodiment of a method, device and vehicle-mounted system for synchronizing vehicle attribute data between vehicle-mounted operating systems according to an embodiment of this specification.
[0109] The device for synchronizing vehicle attribute data between vehicle-mounted operating systems in the embodiments of this specification may be implemented by hardware, software, or a combination of hardware and software. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor of the device in which it is located reading the corresponding computer program instructions in the memory into the memory and running them. In the embodiments of this specification, the device for synchronizing vehicle attribute data between vehicle-mounted operating systems may be implemented, for example, by electronic devices.
[0110] Fig.12 A schematic diagram showing an example of an apparatus 1200 for synchronizing vehicle attribute data between vehicle operating systems according to an embodiment of the present specification.
[0111] like Fig.12 As shown, the apparatus 1200 for synchronizing vehicle attribute data between vehicle-mounted operating systems may include at least one processor 1210, a memory (e.g., a non-volatile memory) 1220, a memory 1230, and a communication interface 1240, and the at least one processor 1210, the memory 1220, the memory 1230, and the communication interface 1240 are connected together via a bus 1250. The at least one processor 1210 executes at least one computer-readable instruction (i.e., the above-mentioned element implemented in the form of software) stored or encoded in the memory.
[0112] In one embodiment, a computer executable instruction is stored in a memory, which, when executed, causes at least one processor 1210 to: obtain a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid from a first vehicle operating system; determine whether the corresponding first attribute value is valid based on the obtained first data validity information; select a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system; and send the selected second attribute value to the first vehicle operating system so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value; or receive the second attribute value corresponding to the target vehicle attribute sent by the second vehicle operating system; query the first data validity status information corresponding to the target vehicle attribute from the first data validity status information indicating whether the first attribute value corresponding to each vehicle attribute is valid stored in the first vehicle operating system; and determine whether the corresponding first attribute value is valid based on the queried first data validity status information; in response to Determine that the corresponding first attribute value is invalid, and update the invalid first attribute value to the corresponding second attribute value; or the second vehicle operating system obtains the first attribute value corresponding to the vehicle attribute and the first data validity status information used to indicate whether the first attribute value is valid from the first vehicle operating system; the second vehicle operating system determines whether the corresponding first attribute value is valid based on the acquired first data validity information; the second vehicle operating system selects the second attribute value corresponding to the same vehicle attribute as the invalid first attribute value from the stored second attribute values corresponding to each vehicle attribute; the second vehicle operating system sends the selected second attribute value to the first vehicle operating system; the first vehicle operating system queries the first data validity status information corresponding to the same target vehicle attribute as the selected second attribute value from the stored first data validity status information corresponding to each vehicle attribute; the first vehicle operating system determines whether the corresponding first attribute value is valid based on the queried first data validity status information; and in response to determining that the corresponding first attribute value is invalid, the first vehicle operating system updates the invalid first attribute value to the corresponding second attribute value.
[0113] It should be understood that the computer executable instructions stored in the memory, when executed, cause at least one processor 1210 to perform the above combined operations in various embodiments of the present specification. Figure 1-Figure 7 Describes the various operations and functions.
[0114] According to one embodiment, a computer-readable storage medium is provided. The computer-readable storage medium may store executable instructions (i.e., the above-mentioned elements implemented in the form of software), which, when executed by a computer, enables the computer to execute the above-mentioned combination of various embodiments of this specification. Figure 1-Figure 7 Describes the various operations and functions.
[0115] Specifically, a system or device equipped with a readable storage medium can be provided, on which software program codes that implement the functions of any of the above-mentioned embodiments are stored, and a computer or processor of the system or device can read and execute instructions stored in the readable storage medium.
[0116] In this case, the program code itself read from the machine-readable medium can realize the function of any one of the above-mentioned embodiments, and thus the machine-readable code and the machine-readable storage medium storing the machine-readable code constitute a part of the present invention.
[0117] The computer program code required for the operation of each part of this specification can be written in any one or more programming languages, including object-oriented programming languages, such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB, NET and Python, conventional procedural programming languages such as C language, Visual Basic 2003, Perl, COBOL 2002, PHP and ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code can be run on the user's computer, or run on the user's computer as an independent software package, or run partly on the user's computer and partly on a remote computer, or all on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any network form, such as a local area network (LAN) or a wide area network (WAN), or connected to an external computer (e.g., via the Internet), or in a cloud computing environment, or used as a service, such as software as a service (SaaS).
[0118] Examples of readable storage media include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD-RW), magnetic tapes, non-volatile memory cards, and ROMs. Optionally, the program code may be downloaded from a server computer or a cloud via a communication network.
[0119] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0120] Not all steps and units in the above-mentioned processes and system structure diagrams are necessary, and some steps or units can be ignored according to actual needs. The execution order of each step is not fixed and can be determined according to needs. The device structure described in the above-mentioned embodiments can be a physical structure or a logical structure, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or some components in multiple independent devices may be implemented together.
[0121] The term "exemplary" as used throughout this specification means "serving as an example, instance, or illustration" and does not imply "preferred" or "advantageous" over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, the techniques may be implemented without these specific details. In some instances, in order to avoid obscuring the concepts of the described embodiments, well-known structures and devices are shown in block diagram form.
[0122] The optional implementation modes of the embodiments of the present specification are described in detail above in conjunction with the accompanying drawings. However, the embodiments of the present specification are not limited to the specific details in the above implementation modes. Within the technical concept of the embodiments of the present specification, various simple modifications can be made to the technical solutions of the embodiments of the present specification, and these simple modifications all belong to the protection scope of the embodiments of the present specification.
[0123] The above description of the contents of this specification is provided to enable any person of ordinary skill in the art to implement or use the contents of this specification. Various modifications to the contents of this specification will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of protection of the contents of this specification. Therefore, the contents of this specification are not limited to the examples and designs described herein, but are consistent with the widest range of principles and novel features disclosed herein.
Claims
1. A method for synchronizing vehicle attribute data between vehicle operating systems, applied to a second vehicle operating system, the method comprising: Acquire, from a first vehicle operating system, a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid; Determine whether the corresponding first attribute value is valid according to the acquired first data validity information; Selecting, from the second attribute values corresponding to the respective vehicle attributes stored in the second vehicle operating system, a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value; as well as sending the selected second attribute value to the first vehicle operating system, so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value, The first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value, including: Querying the first data validity status information corresponding to the selected second attribute value from the first data validity status information stored in the first vehicle operating system and used to indicate whether the first attribute value corresponding to each vehicle attribute is valid; Determining whether the corresponding first attribute value is valid according to the retrieved first data validity status information; and In response to determining that the corresponding first attribute value is invalid, the invalid first attribute value is updated to the corresponding second attribute value.
2. The method of claim 1, wherein: The step of obtaining, from the first vehicle operating system, a first attribute value corresponding to the vehicle attribute and first data validity status information indicating whether the first attribute value is valid comprises: Sending a first request for synchronizing vehicle attribute data to the first vehicle operating system; receiving a response corresponding to the first request sent by the first vehicle operating system; and A first attribute value corresponding to each vehicle attribute and first data validity status information indicating whether the first attribute value is valid are extracted from the response.
3. The method of claim 2, wherein: The sending of the first request is performed in response to the second vehicle operating system re-establishing a communication connection with the first vehicle operating system.
4. The method of claim 1, wherein: Each second attribute value has second data validity status information for indicating whether the second attribute value is valid. The selecting, from the second attribute values corresponding to the respective vehicle attributes stored in the second vehicle operating system, a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value comprises: A second attribute value corresponding to the same vehicle attribute as the invalid first attribute value is selected from valid second attribute values corresponding to each vehicle attribute stored in the second vehicle operating system.
5. The method of claim 1, wherein: Before sending the selected second attribute value to the first vehicle operating system, the method further includes: Using the selected second attribute value as a request parameter, constructing a second request for reverse synchronization of vehicle attributes, The sending the selected second attribute value to the first vehicle operating system includes: The second request is sent to the first vehicle operating system.
6. The method of claim 1, wherein: The method further comprises: The second attribute value corresponding to the corresponding vehicle attribute stored in the second vehicle operating system is updated using the valid first attribute value.
7. The method of claim 1, wherein: The first in-vehicle operating system includes QNX, and the second in-vehicle operating system includes Android.
8. The method of claim 1, wherein: The first data validity status information is used to indicate at least one of the following: whether the first attribute value has been updated, whether the first attribute value is lost, The method further comprises: The updated first attribute value is broadcasted.
9. A method for synchronizing vehicle attribute data between vehicle operating systems, comprising: transmitting a first attribute value corresponding to the vehicle attribute stored in the first vehicle operating system and first data validity status information indicating whether the first attribute value is valid to the second vehicle operating system; The second vehicle operating system determines whether the corresponding first attribute value is valid according to the acquired first data validity information; The second vehicle operating system selects, from the stored second attribute values corresponding to the respective vehicle attributes, a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value; The second vehicle operating system sends the selected second attribute value to the first vehicle operating system; The first vehicle operating system searches for first data valid status information corresponding to the same target vehicle attribute as the selected second attribute value from the stored first data valid status information corresponding to each vehicle attribute; The first vehicle operating system determines whether the corresponding first attribute value is valid according to the queried first data validity status information; as well as In response to determining that the corresponding first attribute value is invalid, the first vehicle operating system updates the invalid first attribute value to a corresponding second attribute value.
10. A device for synchronizing vehicle attribute data between vehicle operating systems, applied to a second vehicle operating system, the device comprising: A data acquisition unit is configured to acquire, from a first vehicle operating system, a first attribute value corresponding to a vehicle attribute and first data validity status information indicating whether the first attribute value is valid; a data validity determination unit, configured to determine whether the corresponding first attribute value is valid according to the acquired first data validity information; a data selection unit configured to select, from the second attribute values corresponding to the respective vehicle attributes stored in the second vehicle operating system, a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value; as well as a data sending unit configured to send the selected second attribute value to the first vehicle operating system, so that the first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value; The first vehicle operating system updates the corresponding first attribute value based on the selected second attribute value, including: Querying the first data validity status information corresponding to the selected second attribute value from the first data validity status information stored in the first vehicle operating system and used to indicate whether the first attribute value corresponding to each vehicle attribute is valid; Determining whether the corresponding first attribute value is valid according to the retrieved first data validity status information; and In response to determining that the corresponding first attribute value is invalid, the invalid first attribute value is updated to the corresponding second attribute value.
11. A device for synchronizing vehicle attribute data between vehicle-mounted operating systems, comprising: A data transmission unit is configured to transmit a first attribute value corresponding to a vehicle attribute acquired from a first vehicle operating system and first data validity status information indicating whether the first attribute value is valid to a second vehicle operating system; and send a second attribute value selected by the second vehicle operating system to the first vehicle operating system; a data validity determination unit, configured to determine whether a corresponding first attribute value is valid according to the first data validity information acquired by the second vehicle operating system; Determining whether a corresponding first attribute value is valid according to the first data validity status information queried by the first vehicle operating system; a data selection unit configured to select, from the second attribute values corresponding to the respective vehicle attributes stored in the second vehicle operating system, a second attribute value corresponding to the same vehicle attribute as the invalid first attribute value; A data query unit is configured to query the first data valid state information corresponding to each vehicle attribute stored in the first vehicle operating system for the first data valid state information corresponding to the same target vehicle attribute as the selected second attribute value; as well as The data updating unit is configured to update the invalid first attribute value in the first vehicle operating system to a corresponding second attribute value in response to determining that the corresponding first attribute value is invalid.
12. A vehicle-mounted system, comprising: The first vehicle operating system is configured to receive a second attribute value corresponding to the target vehicle attribute sent by the second vehicle operating system; Querying the first data validity status information corresponding to the target vehicle attribute from the first data validity status information stored in the first vehicle operating system and used to indicate whether the first attribute value corresponding to each vehicle attribute is valid; Determine whether the corresponding first attribute value is valid according to the queried first data validity status information; and in response to determining that the corresponding first attribute value is invalid, updating the invalid first attribute value to the corresponding second attribute value; The second in-vehicle operating system is configured to execute the method for synchronizing vehicle attribute data between in-vehicle operating systems as claimed in any one of claims 1 to 8.
13. An electronic device comprising: At least one processor, and a memory coupled to the at least one processor, the memory storing a computer program, the at least one processor executing the computer program to implement the method for synchronizing vehicle attribute data between in-vehicle operating systems as described in any one of claims 1 to 8 or the method for synchronizing vehicle attribute data between in-vehicle operating systems as described in claim 9.
14. A computer-readable storage medium storing executable instructions, which, when executed by a processor, implement the method for synchronizing vehicle attribute data between vehicle-mounted operating systems as described in any one of claims 1 to 8 or the method for synchronizing vehicle attribute data between vehicle-mounted operating systems as described in claim 9.
Citation Information
Patent Citations
Resource transfer method and device, terminal and storage medium
CN111901283A
File synchronization method and device, equipment and storage medium
CN116016486A
Time synchronization method and device, electronic equipment and storage medium
CN116436995A
Dual-core CPU and inter-core data synchronization method for dual-core CPU
CN118093153A
Configurable distributed caching method, system and equipment based on XML (Extensible Markup Language) and medium
CN118193593A
