Data reporting method and device, vehicle and storage medium

Abstract

The invention discloses a data reporting method and device, a vehicle and a storage medium, relates to the technical field of vehicles, and aims to solve the problem of low efficiency of collecting data of multiple operating systems. The data reporting method comprises the following steps: in response to a data acquisition instruction, calling a first operating system to acquire data of the first operating system and data of a second operating system; and in response to the data reporting instruction, calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server.

Description

Technical Field

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

[0002] Currently, with the continuous improvement of the intelligence level of automobiles, it has gradually become a development trend for in-vehicle systems to contain two or more operating systems. The realization of intelligent driving depends on the need to obtain data from various sensors while the vehicle is driving. At the same time, the car not only has a large central control screen as the main interactive port, but also a multimedia control terminal exclusively for rear passengers. In order to ensure the accuracy of the in-vehicle system, this information needs to be collected efficiently and then reported to the cloud server for accurate analysis. In related technologies, when there are multiple operating systems, a single monitoring system is used, which can only collect data from one operating system, resulting in low data collection efficiency, which in turn leads to low data reporting efficiency. Summary of the Invention

[0003] The purpose of this application is to provide a data reporting method, device, vehicle and storage medium, aiming to solve the problem of low efficiency in collecting data from multiple operating systems.

[0004] To achieve the above objectives, this application adopts the following technical solutions:

[0005] In a first aspect, the present application provides a data reporting method, comprising: in response to a data collection instruction, calling a first operating system to collect data of the first operating system and data of a second operating system; in response to a data reporting instruction, calling the first operating system to report the data of the first operating system and the data of the second operating system to a cloud server.

[0006] The data reporting method provided in the embodiment of the present application can collect data of the first operating system and the second operating system simultaneously after receiving the data collection instruction, thereby shortening the data collection time, greatly improving the efficiency of data collection, and thus improving the data reporting efficiency.

[0007] In some embodiments, before responding to the data collection instruction, the above also includes: receiving the data collection instruction, and the data collection instruction is triggered by at least one of the following methods: monitoring a change in the vehicle status; detecting a user's control operation; triggering according to a first preset time interval.

[0008] In some embodiments, before responding to the data reporting instruction, the above also includes: receiving the data reporting instruction, and the data reporting instruction is triggered by at least one of the following methods: receiving a data acquisition request sent by the cloud server; triggering according to a second preset time interval.

[0009] In some embodiments, after calling the first operating system to collect data of the first operating system and data of the second operating system, the method further includes: displaying the data of the first operating system and the data of the second operating system in a display interface.

[0010] In some embodiments, after calling the first operating system to collect data of the first operating system and data of the second operating system, the method further includes: when there is an abnormality in the data collected by the first operating system and the data of the second operating system, displaying a prompt message in the display interface; and / or, broadcasting the prompt message by voice.

[0011] In some embodiments, after calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the above method also includes: receiving a data analysis report sent by the cloud server through the first operating system, the data analysis report includes the data analysis report of the first operating system and / or the data analysis report of the second operating system; and displaying the data analysis report on the display interface.

[0012] In some embodiments, the above-mentioned calling of the first operating system to collect data of the first operating system and data of the second operating system includes: collecting data of the first operating system based on the first data collection SDK in the first operating system; collecting data of the second operating system based on the second data collection SDK in the second operating system; calling the collection server in the first operating system to obtain data of the first operating system from the first data collection SDK, and obtaining data of the second operating system from the second data collection SDK.

[0013] In some embodiments, the above-mentioned calling of the acquisition server in the first operating system to obtain data of the first operating system from the first data acquisition SDK, and obtaining data of the second operating system from the second data acquisition SDK, includes: the acquisition server sends data acquisition requests to the first data acquisition SDK and the second data acquisition SDK respectively through the virtual socket VSOCK channel; in response to the data acquisition request, the first data acquisition SDK sends the data of the first operating system to the acquisition server through the VSOCK channel; in response to the data acquisition request, the second data acquisition SDK sends the data of the second operating system to the acquisition server through the VSOCK channel.

[0014] In some embodiments, after collecting data of the second operating system based on the second data collection SDK in the second operating system, the above method also includes: calling the second data collection SDK to store the data of the second operating system to the shared memory; calling the collection server in the first operating system to obtain the data of the second operating system from the second data collection SDK, including: calling the collection server to read the data of the second operating system from the shared memory.

[0015] In some embodiments, before calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the method further includes: preprocessing the data of the first operating system and the data of the second operating system.

[0016] In some embodiments, the above-mentioned preprocessing includes data cleaning, and the above-mentioned preprocessing of the data of the first operating system and the data of the second operating system includes: removing duplicate data in the data of the first operating system and the data of the second operating system; removing noise data in the data of the first operating system and the data of the second operating system; removing data with missing fields in the data of the first operating system and the data of the second operating system.

[0017] In some embodiments, the above-mentioned preprocessing includes data verification, and the above-mentioned preprocessing of the data of the first operating system and the data of the second operating system includes: verifying the data integrity of the data of the first operating system and the data of the second operating system; verifying the data consistency of the data of the first operating system and the data of the second operating system; and verifying the data accuracy of the data of the first operating system and the data of the second operating system.

[0018] In some embodiments, the preprocessing includes data conversion, and the preprocessing of the data of the first operating system and the data of the second operating system includes: converting the data formats of the data of the first operating system and the data of the second operating system into the same data format.

[0019] In some embodiments, before calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the above method also includes: sending a communication request message to the cloud server, the communication request message is used to establish communication between the first operating system and the cloud server; in response to receiving a communication response message sent by the cloud server, establishing a connection with the cloud server; in response to not receiving a communication response message after a preset period of time, calling the first operating system to re-send the communication request message to the cloud.

[0020] In some embodiments, the data of the above-mentioned first operating system includes at least one of the following: application layer data of the first operating system, framework layer data of the first operating system, vehicle data of the first operating system, common control data of the first operating system, and application data of the first operating system; the data of the second operating system includes at least one of the following: application layer data of the second operating system, framework layer data of the second operating system, vehicle data of the second operating system, common control data of the second operating system, and application data of the second operating system.

[0021] In a second aspect, the present application provides an electronic device comprising: a processor and a memory configured to store processor-executable instructions; wherein the processor is configured to execute the instructions to implement any one of the optional data reporting methods in the first aspect above.

[0022] In a third aspect, the present application provides a computer-readable storage medium having instructions stored thereon. When the instructions in the computer-readable storage medium are executed by a device, the device is enabled to execute any one of the optional data reporting methods in the first aspect above.

[0023] In a fourth aspect, the present application provides a vehicle comprising: the electronic device of the second aspect above, or the computer-readable storage medium of the third aspect.

[0024] In a fifth aspect, the present application provides a computer program product, which includes computer instructions. When the computer instructions are executed on a processor of a device, the device is enabled to execute any optional data reporting method as described in the first aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0026] Figure 1 A schematic diagram of the structure of a data reporting system provided in an embodiment of the present application;

[0027] Figure 2 A schematic diagram of the structure of another data reporting system provided in an embodiment of the present application;

[0028] Figure 3 A flowchart of a data reporting method provided in an embodiment of the present application;

[0029] Figure 4 A flowchart of another data reporting method provided in an embodiment of the present application;

[0030] Figure 5 A schematic diagram of a data collection process provided in an embodiment of the present application;

[0031] Figure 6 A schematic diagram of a data reporting process provided in an embodiment of the present application;

[0032] Figure 7 A schematic diagram of a data acquisition and interaction process provided in an embodiment of the present application;

[0033] Figure 8 A schematic diagram of the structure of a data reporting device provided in an embodiment of the present application;

[0034] Figure 9 A schematic diagram of the structure of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0036] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature specified as "first" or "second" may explicitly or implicitly include one or more of such features. Throughout this application, unless otherwise specified, "plurality" means two or more.

[0037] In the embodiments of the present application, the terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, article, or device comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of other identical elements in the process, article, or device comprising the element.

[0038] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0039] In the description of this specification, specific features, structures, materials or characteristics may be combined in an appropriate manner in any one or more embodiments or examples.

[0040] At present, with the continuous improvement of the intelligence level of automobiles, it has gradually become a development trend for in-vehicle systems to contain two or more operating systems. The realization of intelligent driving depends on the need for the vehicle to obtain data from various sensors during driving. At the same time, the car not only has a large central control screen as the main interactive port, but also a multimedia control terminal exclusively for rear passengers. In order to ensure the accuracy of the in-vehicle system, this information needs to be collected efficiently and then reported to the cloud server for accurate analysis. In related technologies, when there are multiple operating systems, a single monitoring system is used, which can only collect and report data from one operating system, resulting in low data collection efficiency, which in turn leads to low data reporting efficiency.

[0041] Based on this, the present application proposes a data reporting method, comprising: in response to a data collection instruction, calling a first operating system to collect data from the first operating system and data from a second operating system; and in response to the data reporting instruction, calling the first operating system to report the data from the first operating system and the data from the second operating system to a cloud server. After receiving the data collection instruction, the data from the first operating system and the data from the second operating system can be collected simultaneously, shortening the data collection time, greatly improving the efficiency of data collection, and thus improving the efficiency of data reporting.

[0042] For ease of understanding, the data acquisition system provided in this application is specifically introduced below with reference to the accompanying drawings.

[0043] The present application provides a vehicle including a data reporting system. It should be noted that the type of vehicle is not limited, for example, it can be a pure electric vehicle, a hybrid electric vehicle, a fuel cell vehicle, or other new energy vehicle including a battery pack.

[0044] like Figure 1 As shown, the data reporting system provided in the embodiment of the present application includes: a first operating system 10, a second operating system 20 and a cloud server 30, a first data acquisition software development kit (Software Development Kit, SDK) 110 and an acquisition server 120 are installed on the first operating system 10, and a second data acquisition SDK 210 is installed on the second operating system 20.

[0045] The first operating system 10 and the second operating system 20 may be the following operating systems: Linux, Android, Windows, or other operating systems. The first operating system 10 and the second operating system 20 may be the same type of operating system or different types of operating systems. For example, the first operating system 10 may be one of the Linux system and the Android system, and the second operating system 20 may be the other of the Linux system and the Android system.

[0046] As a possible implementation, develop and install a data acquisition SDK and acquisition server environment in the operating system. After the development environment is installed, obtain the data acquisition SDK source code or precompiled library files, as well as the acquisition server source code, and compile and build the data acquisition SDK and acquisition server source code to generate executable programs or library files. When the data acquisition SDK and acquisition server are working, calling the corresponding executable programs or library files can realize the corresponding functions.

[0047] As a possible implementation method, after installing the data collection SDK and the collection server, you need to configure the data collection SDK and the collection server.

[0048] The Data Collection SDK configuration process includes dependency configuration, permission configuration, and SDK parameter and option configuration. Dependency configuration involves installing the SDK's dependencies to enrich the data collection content. For example, by adding dependencies for processing sensor data like accelerometers and gyroscopes, the Data Collection SDK can more accurately collect vehicle motion information. Permission configuration involves assigning the necessary permissions to the Data Collection SDK in the operating system. For example, if the Data Collection SDK collects data from vehicle sensors, permission to read sensor data must be enabled for the SDK. Data Collection SDK parameter and option configuration includes the data acquisition path, acquisition frequency, and acquisition interface.

[0049] The acquisition server configuration process can refer to the data acquisition SDK configuration process: communication configuration, data storage configuration. Communication configuration refers to configuring the acquisition server's communication parameters, such as the communication baud rate and communication protocol. Data storage configuration refers to configuring the data storage method and location.

[0050] In some embodiments, a first data collection SDK 110 is used to collect data of a first operating system 10. A second data collection SDK 210 is used to collect data of a second operating system 20. A collection server 120 is used to obtain data of the first operating system 10 from the first data collection SDK 110 and obtain data of the second operating system 20 from the second data collection SDK 210, store the data of the first operating system 10 and the data of the second operating system 20, and upload the data of the first operating system 10 and the data of the second operating system 20 to a cloud server 30.

[0051] In some embodiments, the collection server 120 and the cloud server 30 can communicate based on the Hypertext Transfer Protocol (HTTP). When sending data, the collection server 120 constructs an HTTP request message. This message consists of a request line, a request header, and a request body. The client sends this request message over the network to the cloud server 30. Upon receiving it, the cloud server 30 parses and processes it to obtain data from the first operating system 10 and the second operating system 20.

[0052] It should be noted that to ensure the legitimacy and security of data transmission, the server typically requires the collection server 120 to authenticate. The collection server 120 must include the corresponding authentication information when sending a request message. Upon receiving the request, the server verifies the authentication information and only processes requests that pass verification. Authentication methods can include OAuth authentication, JWT (JSON Web Token) authentication, and other methods.

[0053] In some embodiments, the process of collecting operating system data through the data collection SDK includes: after completing the data collection SDK initialization, the data monitoring component in the data collection SDK will start to listen to data collection instructions. Whenever a data collection instruction is triggered, the data collection SDK calls the corresponding data collection interface to obtain the required data.

[0054] It should be noted that the data collected by the data collection SDK may contain sensitive information, such as user personal information, etc. Therefore, corresponding security measures such as data encryption and access control need to be taken to ensure data security.

[0055] In some embodiments, the data collection SDK may collect single data or batch data. The specific amount of data collected at a single time may be determined based on the application usage scenario and application requirements.

[0056] As a possible implementation method, the amount of data collected at a single time can be determined based on the frequency of interaction between the application and the user. For example, if the interaction frequency is high, batch data collection is adopted.

[0057] As another possible implementation, the amount of data collected in a single time can be determined according to the trigger type of the interactive operation. For example, if the trigger type is click, single data collection is adopted; if the trigger type is sliding, batch data collection is adopted.

[0058] In some embodiments, the collection server 120 mainly implements cross-system data interaction. Based on this interaction, the first operating system 10 and the second operating system 20 can obtain and synchronize data across systems, so that the data of the two operating systems remain consistent.

[0059] The first operating system 10 and the second operating system 20 interact via remote procedure call (RPC) and transmit data to the first operating system. The transmitted data includes but is not limited to attribute public data, configuration data, database data, etc.

[0060] For example, attribute public data may include necessary information such as vehicle identification, operating system version, etc. Configuration data may include information such as configuration parameters of applications within the operating system, and database data may include information such as vehicle mileage and fault records.

[0061] In some embodiments, the types of the first data acquisition SDK and the second data acquisition SDK can be determined according to acquisition requirements and characteristics of the operating system, and the corresponding data acquisition SDK is selected.

[0062] For example, if you want to collect operating system performance data, you can choose SystemTap, DTrace, etc. If you want to collect network data, you can choose libpcap, libnet, etc. to capture network data packets.

[0063] For example, when collecting system resource data on Linux systems, you can use the SystemTap SDK, DTrace SDK, etc. On Android systems, to collect sensor data such as accelerometers, gyroscopes, and light sensors, you can use the Android Sensor SDK.

[0064] It's important to note that before the Data Collection SDK collects data, it must ensure that the data source is accessible and can provide data stably. Therefore, before using the Data Collection SDK to collect data, first assess the reliability of the operating system's data and determine the permissions required for the Data Collection SDK to access each data source in the operating system.

[0065] like Figure 2 As shown, in some embodiments, there may be multiple second operating systems 20, and the types of the second operating systems 20 may be different. The collection server communicates with multiple second data collection SDKs and stores and reports data of the multiple second operating systems.

[0066] It should be noted that the data reporting method provided in the embodiment of the present application is applicable to a vehicle or a vehicle data reporting system. Figure 3 As shown, the data reporting method provided in the embodiment of the present application includes:

[0067] S301 : In response to a data collection instruction, call a first operating system to collect data of the first operating system and data of a second operating system.

[0068] In some embodiments, before responding to the data collection instruction, it also includes: receiving the data collection instruction, the data collection instruction is triggered by at least one of the following methods: monitoring a change in the vehicle status; detecting a user's control operation; triggering according to a first preset time interval.

[0069] As a possible implementation, detecting a change in vehicle status, such as a change in speed, fuel level, or remaining battery charge, triggers a data collection instruction. For example, when a vehicle accelerates from a standstill and its speed changes, the system detects this state change and triggers a data collection instruction to collect data related to the vehicle's acceleration, such as acceleration and engine power output.

[0070] As another possible implementation, various user-controlled vehicle operations can trigger data collection instructions. User-controlled operations include turning on or off various in-vehicle devices and touching the vehicle's display. When the user performs these operations, the system detects the corresponding operation signal and triggers data collection. For example, if the vehicle's air conditioning system experiences an anomaly, the user can trigger data collection by clicking the control on the display that collects air conditioning system data.

[0071] As another possible implementation, a fixed time interval (i.e., a first preset time interval) can be set to automatically trigger the data collection instruction at each time interval, regardless of the vehicle's state. For example, if the first preset time interval is set to 1 minute, the system will initiate data collection every 1 minute to collect various vehicle data at the current moment.

[0072] In some embodiments, calling the first operating system to collect data from the first operating system and data from the second operating system includes: collecting the data from the first operating system through an application programming interface (API); and establishing a message queue between the first operating system and the second operating system. The second operating system sends the collected data to the message queue in the form of messages, and the first operating system reads the messages from the message queue, thereby collecting data from the second operating system.

[0073] S302: In response to the data reporting instruction, call the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server.

[0074] In some embodiments, before responding to the data reporting instruction, it also includes: receiving the data reporting instruction, and the data reporting instruction is triggered by at least one of the following methods: receiving a data acquisition request sent by the cloud server; triggering according to a second preset time interval.

[0075] As a possible implementation, when a cloud server needs data, it sends a data acquisition request to the vehicle system. Upon receiving this request, the vehicle system triggers a data reporting command. The vehicle then compiles and sends the previously collected data to the cloud server according to established rules and formats. For example, if the cloud server wants to know the fuel consumption data of multiple vehicles over a specific time period, it will send a data acquisition request to these vehicles. Upon receiving the request, the vehicle triggers a data reporting command, sending its own fuel consumption and other related data to the cloud server.

[0076] As another possible implementation, a specific time interval (i.e., a second preset time interval) can be pre-set. When this time interval is reached, the data reporting instruction will be triggered regardless of whether a data acquisition request from the cloud server is received. For example, if the second preset time interval is set to every half hour, then every half hour, the vehicle system will automatically organize and send the previously collected data that meets the reporting conditions to the cloud server.

[0077] In some embodiments, calling the first operating system to report data of the first operating system and data of the second operating system to the cloud server includes: the first operating system can use a network protocol to package the data into a specific format and send it to the cloud server through a network request.

[0078] In some embodiments, in order to improve the success rate of data transmission, the first operating system can set a retry mechanism. When data transmission fails, the first operating system will try to resend the message request after a certain time interval. The number of retries can be set according to actual conditions.

[0079] Therefore, after receiving the data collection instruction, the data of the first operating system and the data of the second operating system can be collected simultaneously, which shortens the data collection time, greatly improves the efficiency of data collection, and further improves the efficiency of data reporting.

[0080] In some embodiments, after calling the first operating system to collect data of the first operating system and data of the second operating system, the method further includes: displaying the data of the first operating system and the data of the second operating system in a display interface.

[0081] As a possible implementation method, the display method of the data of the first operating system and the data of the second operating system can be determined first, and the data of the first operating system and the data of the second operating system can be displayed in the display interface through full screen, split screen and other display methods.

[0082] For example, when the user needs to deeply analyze complex system performance data in the first operating system, such as the power curve of the engine over a long period of time, the full-screen display can fill the entire screen with these data in the form of large-size charts, detailed lists, etc., eliminating other interference.

[0083] For another example, the display interface is split into left and right screens, with the left side displaying data of the first operating system and the right side displaying data of the second operating system.

[0084] It should be noted that there may be multiple display screens in the vehicle, and therefore, the data of the first operating system and the data of the second operating system may be displayed on the display interfaces of different display screens.

[0085] In some embodiments, anomalies may occur during the data collection process. To prevent users from continuing operations without knowledge and causing further problems, after invoking the first operating system to collect data from the first operating system and the second operating system, the method further includes: displaying a prompt message on the display interface if an anomaly occurs during the data collection by the first operating system; and / or announcing the prompt message via voice.

[0086] As a possible implementation method, when a data collection anomaly is detected, a prompt message is displayed in the display interface through a pop-up dialog box, a status bar prompt, or a specific prompt text box, and the prompt message is broadcast by outputting a voice, for example, outputting a voice message of "Network anomaly, unable to collect data".

[0087] The prompt information may include specific content about the data anomaly, such as which part of the data is abnormal and possible reasons, etc., which can help users quickly locate the problem and save users time in finding and solving the problem.

[0088] The prompt information can also provide some simple solution suggestions or operation guidance, such as prompting users to check device connections, restart related services, etc., so that users can try to solve the problem by themselves as soon as possible.

[0089] In this way, users can be informed of abnormal data collection situations in the first place, preventing the accumulation of abnormal data or further propagation of errors, and improving the stability of the system.

[0090] In some embodiments, after invoking the first operating system to report data of the first operating system and data of the second operating system to the cloud server, the method further includes: receiving, via the first operating system, a data analysis report sent by the cloud server, and displaying the data analysis report on a display interface. The data analysis report includes the data analysis report of the first operating system and / or the data analysis report of the second operating system.

[0091] As one possible implementation, the cloud server packages the data analysis report and sends it to the first operating system. After receiving the data analysis report, the first operating system parses the data analysis report into objects or data structures that the first operating system can process. Based on the content of the data analysis report, the display interface can be divided into multiple areas, such as a title area, a report content area, and an operation button area.

[0092] As a result, users can obtain the latest data analysis reports in a timely manner, ensuring that they can grasp data dynamics and relevant information at the first time, making it easier to make timely decisions.

[0093] In some embodiments, before invoking the first operating system to report data from the first operating system and data from the second operating system to the cloud server, the method further includes: sending a communication request message to the cloud server; in response to receiving a communication response message from the cloud server, establishing a connection with the cloud server; and in response to not receiving a communication response message after a preset period of time, invoking the first operating system to resend a communication request message to the cloud. The communication request message is used to establish communication between the first operating system and the cloud server, thereby avoiding situations where system functions cannot function normally due to connection establishment failure.

[0094] In some embodiments, as Figure 4 As shown, the above-mentioned calling of the first operating system to collect data of the first operating system and data of the second operating system includes:

[0095] S401: Collect data of the first operating system based on a first data collection SDK in the first operating system.

[0096] S402: Collect data of the second operating system based on the second data collection SDK in the second operating system.

[0097] In some embodiments, the data of the first operating system includes at least one of the following: application layer data of the first operating system, framework layer data of the first operating system, vehicle data of the first operating system, common control data of the first operating system, and application data of the first operating system.

[0098] The data of the second operating system includes at least one of the following: application layer data of the second operating system, framework layer data of the second operating system, vehicle computer data of the second operating system, common control data of the second operating system, and application data of the second operating system.

[0099] Application layer data refers to data generated, used, and processed during the application's operation. For example, information about music tracks played by users, such as song title, artist, album, play time, and progress, or data about vehicle air conditioning and seats.

[0100] Framework-level data refers to the data used and maintained by the framework when running and managing applications. For example, in Android development, when an application is launched, the Android framework records the application's lifecycle state data (such as creation, start, pause, and stop states).

[0101] Vehicle computer data refers to data generated and used by a vehicle's in-vehicle infotainment system (VCS) and related intelligent driving systems. For example, this includes driving data such as speed, acceleration, and mileage. Furthermore, in some vehicles equipped with intelligent assisted driving features, the VCS also collects and processes data from various sensors, such as road images captured by cameras and obstacle distances detected by radar.

[0102] Common control data refers to the data involved in building various common controls in the user interface (such as buttons, text boxes, and drop-down lists). This includes control property settings, status information, and data generated by user interactions with the controls. For example, a button's text content ("Submit," "Cancel," etc.), size, color, position, and usage frequency are all included.

[0103] Application data refers to the configuration data and cached data that the application relies on during operation. For example, the on / off settings of message reminders, font size selection, etc.; or the user profile pictures and article content that have been loaded; or the installation time and location of the application.

[0104] It should be noted that if Figure 5 As shown, integrate the data acquisition SDK within the application to collect application layer data and application data. Integrate the data acquisition SDK in the framework layer to collect framework layer data. Integrate the data acquisition SDK in the vehicle service to collect vehicle data. Integrate the data acquisition SDK in the common control to collect common control data.

[0105] The data collection SDK may be integrated into an application of the first operating system or the second operating system in the form of a shared object (SO).

[0106] It should be noted that the specific process of collecting data of the first operating system and the second operating system through the data collection SDK can be described in the above embodiments and will not be repeated here.

[0107] S403: Calling the collection server in the first operating system to obtain data of the first operating system from the first data collection SDK, and to obtain data of the second operating system from the second data collection SDK.

[0108] As a possible implementation method, the collection server sends data acquisition requests to the first data collection SDK and the second data collection SDK through the virtual socket VSOCK channel (VM sockets). In response to the data acquisition request, the first data collection SDK sends the data of the first operating system to the collection server through the VSOCK channel. In response to the data acquisition request, the second data collection SDK sends the data of the second operating system to the collection server through the VSOCK channel.

[0109] In some embodiments, the process of communicating via a VSOCK channel includes: first configuring the identifiers of the acquisition server, the first data acquisition SDK, and the second data acquisition SDK. Then, creating a socket, the address and port of the acquisition server, the address of the first data acquisition SDK, and the address of the second data acquisition SDK. Then, connecting the first and second data acquisition SDKs to the address and port of the acquisition server via the socket.

[0110] Among them, the VSOCK channel is used for communication between the virtual machine and the host machine or other virtual machines. In this application, the VSOCK channel is used for communication between the first data acquisition SDK and the acquisition server in the first operating system, or between the acquisition server of the first operating system and the second data acquisition SDK of the second operating system.

[0111] It should be understood that using VSOCK channels for data transmission avoids the packet duplication and context switching required by traditional network protocols, making data transmission more timely and improving data throughput. Furthermore, because VSOCK communication does not pass through the physical network, communicating through VSOCK channels improves data security.

[0112] In some embodiments, after collecting data of the second operating system based on the second data collection SDK in the second operating system, the method further includes: storing the data of the second operating system to a shared memory, and reading the data of the second operating system 20 from the shared memory.

[0113] As a possible implementation method, the first operating system is the host machine and the second operating system is the virtual machine. A section of physical memory is selected from the physical address of the host machine as the shared memory area, and the physical address of the shared memory area is mapped to the physical address of the virtual machine. The virtual machine and the host machine can exchange and share data by reading and writing the shared memory area.

[0114] In some embodiments, when the second data acquisition SDK writes the data of the second operating system into the shared memory and the acquisition server reads the data of the second operating system from the shared memory, it can write and read in batches, which can reduce frequent memory access, avoid resource waste and leakage, and improve system performance.

[0115] It should be noted that since shared memory reads and writes data directly from the main memory, it reduces the risk of delays and failures caused by disk I / O.

[0116] In some embodiments, as Figure 5 As shown, before calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the data of the first operating system and the data of the second operating system are preprocessed.

[0117] Among them, preprocessing includes at least one of the following: data cleaning, data verification, and data conversion.

[0118] In some embodiments, when the preprocessing includes data cleaning, the above-mentioned preprocessing of the data of the first operating system and the data of the second operating system includes: removing duplicate data in the data of the first operating system and the data of the second operating system; removing noise data in the data of the first operating system and the data of the second operating system; removing data with missing fields in the data of the first operating system and the data of the second operating system.

[0119] As a possible implementation, statistical analysis methods can be used to identify and remove noise data that significantly deviates from the normal range. Based on the query statement, the data from the first and second operating systems are grouped by key fields, and the number of occurrences of each data group is counted to identify duplicate data. Duplicate records are deleted, retaining only unique values. Data statistical tools are used to determine the missing values of each data field, and any data with missing fields is identified and deleted.

[0120] In some embodiments, when the preprocessing includes data verification, the above-mentioned preprocessing of the data of the first operating system and the data of the second operating system includes: verifying the data integrity of the data of the first operating system and the data of the second operating system; verifying the data consistency of the data of the first operating system and the data of the second operating system; and verifying the data accuracy of the data of the first operating system and the data of the second operating system.

[0121] As a possible implementation manner, the data integrity, data consistency and data accuracy of the data of the first operating system and the data of the second operating system may be verified based on integrity verification rules, consistency verification rules and accuracy verification rules.

[0122] In some embodiments, when the preprocessing includes data conversion, the preprocessing of the data of the first operating system and the data of the second operating system includes: converting the data formats of the data of the first operating system and the data of the second operating system into the same data format.

[0123] As another possible implementation, the data of the first operating system and the data of the second operating system may be format converted to convert the collected data in different formats into the same format or type to meet the needs of subsequent analysis or processing.

[0124] In other embodiments, data from the first operating system and the second operating system can be pre-processed based on disk flushing rules and data storage space. Disk flushing rules include time flushing rules and data volume flushing rules. Data storage space includes estimated data storage capacity and file size.

[0125] In one possible implementation, data can be pre-processed based on time-based flushing rules, for example, flushing data to disk at fixed time intervals or fixed time points. Data can also be pre-processed based on data volume rules, for example, flushing data to disk based on data volume and the number of data records.

[0126] In one possible implementation, data can be preprocessed based on estimated data storage capacity. For example, the amount of data collected in each historical time period can be used to determine the future data storage capacity. The remaining memory space and the estimated data storage capacity can then be used to determine whether to clear memory space. Data can also be preprocessed based on file size. For example, if a file is too large, it can be split into multiple subfiles.

[0127] In some embodiments, after pre-processing the data of the first operating system and the data of the second operating system, the collection server transfers the data to a target location for storage, for example, converting the data into a JSON format and writing it into a file, which is then stored in a local file of the first operating system.

[0128] Therefore, by preprocessing the data of the first operating system and the data of the second operating system, the quality and availability of the data are improved.

[0129] In some embodiments, as Figure 6 As shown, the collection server can send the data of the first operating system and the data of the second operating system to the cloud server based on an event trigger mechanism or a timing trigger mechanism.

[0130] In one possible implementation, the cloud server sends a data acquisition request to the collection server. The data acquisition request carries the type of requested data, the range of requested data, and the cloud server's own identification. The collection server determines the data to be sent based on the data acquisition request and encapsulates the data to be sent, and then sends the data to the corresponding server based on the cloud server's identification.

[0131] In another possible implementation, the collection server can determine the timing trigger mechanism based on the processing capacity of the cloud server. Before each timing trigger time point arrives, the collection server needs to collect and integrate the data to be sent, and then send the data to the cloud server when the trigger time point arrives.

[0132] It should be noted that in order to ensure the security of data during transmission, the data will be encrypted. Symmetric encryption or asymmetric encryption algorithms can be used to encrypt the data to prevent the data from being stolen or tampered with.

[0133] In some embodiments, the collection server may also remove the uploaded data during the process of sending the data of the first operating system and the data of the second operating system to the cloud server to ensure that there is available space for subsequent data storage.

[0134] In other embodiments, after the collection server completes sending the data, it can also record error handling information, log records, upload information records, upload traffic records, etc. By analyzing error handling, log records, upload information records, upload traffic records, etc., not only can the availability and integrity of the data be ensured, but also the appropriate data sending strategy can be selected based on this information to improve the efficiency of data sending.

[0135] Among them, the error handling information means that after the collection server fails to send data to the cloud server, the collection server will record information such as the error type and data retransmission.

[0136] Log records include operations on the data collection server, storage space status, and data transmission error information. Operations include the time the data collected by the data collection SDK was acquired, the data processing steps, and the time the data was uploaded to the server. Storage space status includes memory usage and remaining space. Data transmission error information includes error type, error retransmission, and other information.

[0137] Upload information records include: upload time, which is the start and end time when the collection server sends data to the cloud server; upload data volume, which records the size of each data sent; and upload result, which indicates whether the data was successfully sent.

[0138] Upload traffic records include: data sending traffic, time range of traffic peak, etc.

[0139] Below Figure 7 The logic of data acquisition and data interaction between the first operating system 10 and the second operating system 20 will be introduced.

[0140] In some embodiments, the SDK acquisition module in the second operating system 20 collects the attribute public data, configuration data, database data, etc. of the second operating system 20, and then establishes communication with the SDK acquisition module of the second operating system 20 through the configuration service module. The acquisition service module obtains and stores the attribute public data, configuration data, database data, other data, etc. of the second operating system 20.

[0141] In other embodiments, the attribute public data, configuration data, database data, other data and other information of the second operating system 20 can be uploaded to the cloud server through the information upload module, and the attribute public data, configuration data, database data and other information of the second operating system 20 can also be directly exported through the information export module.

[0142] It should be noted that the data acquisition system in this embodiment of the application is based on the Rust language to implement data acquisition SDK for data acquisition and data preprocessing, storage, and upload by the acquisition server. By using the Rust language, stability, efficiency, and security can be guaranteed during data acquisition, processing, and transmission.

[0143] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to realize the above functions, the data acquisition device includes a hardware structure and / or software module corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0144] In the embodiment of the present application, the data acquisition device can be divided into functional modules according to the above method. For example, the data acquisition device can include functional modules corresponding to the functional divisions, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0145] Figure 8 This is a structural diagram of a data reporting device provided in an embodiment of the present application. Figure 8 The data reporting device 700 includes: a collection unit 710 and a processing unit 720.

[0146] The collection unit 710 is configured to call the first operating system to collect data of the first operating system and data of the second operating system in response to a data collection instruction.

[0147] The processing unit 720 is configured to call the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server in response to the data reporting instruction.

[0148] In some embodiments, the acquisition unit 710 is further configured to receive data acquisition instructions, which are triggered by at least one of the following methods: monitoring a change in the vehicle's status; detecting a user's control operation; or triggering at a first preset time interval.

[0149] In some embodiments, the processing unit 720 is further configured to receive a data reporting instruction, which is triggered by at least one of the following methods: receiving a data acquisition request sent by a cloud server; or triggering according to a second preset time interval.

[0150] In some embodiments, the processing unit 720 is further configured to display data of the first operating system and data of the second operating system on a display interface.

[0151] In some embodiments, the processing unit 720 is further configured to display a prompt message in a display interface when an abnormality exists in the data collected by the first operating system and the data collected by the second operating system; and / or to announce the prompt message by voice.

[0152] In some embodiments, the processing unit 720 is further used to receive a data analysis report sent by the cloud server through the first operating system, the data analysis report including the data analysis report of the first operating system and / or the data analysis report of the second operating system; and display the data analysis report on the display interface.

[0153] In some embodiments, the above-mentioned processing unit 720 is specifically used to collect data of the first operating system based on the first data collection SDK in the first operating system; collect data of the second operating system based on the second data collection SDK in the second operating system; call the collection server in the first operating system to obtain data of the first operating system from the first data collection SDK, and obtain data of the second operating system from the second data collection SDK.

[0154] In some embodiments, the above-mentioned processing unit 720 is specifically used for the acquisition server to send data acquisition requests to the first data acquisition SDK and the second data acquisition SDK respectively through the virtual socket VSOCK channel; in response to the data acquisition request, the first data acquisition SDK sends the data of the first operating system to the acquisition server through the VSOCK channel; in response to the data acquisition request, the second data acquisition SDK sends the data of the second operating system to the acquisition server through the VSOCK channel.

[0155] In some embodiments, after collecting data of the second operating system based on the second data collection SDK in the second operating system, the above-mentioned processing unit 720 is also used to call the second data collection SDK to store the data of the second operating system to the shared memory; call the collection server in the first operating system to obtain the data of the second operating system from the second data collection SDK, including: calling the collection server to read the data of the second operating system from the shared memory.

[0156] In some embodiments, before calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the processing unit 720 is further used to pre-process the data of the first operating system and the data of the second operating system.

[0157] In some embodiments, the above-mentioned preprocessing includes data cleaning, and the above-mentioned processing unit 720 is specifically used to remove duplicate data in the data of the first operating system and the data of the second operating system; remove noise data in the data of the first operating system and the data of the second operating system; and remove data with missing fields in the data of the first operating system and the data of the second operating system.

[0158] In some embodiments, the above-mentioned preprocessing includes data verification, and the above-mentioned processing unit 720 is specifically used to verify the data integrity of the data of the first operating system and the data of the second operating system; verify the data consistency of the data of the first operating system and the data of the second operating system; and verify the data accuracy of the data of the first operating system and the data of the second operating system.

[0159] In some embodiments, the preprocessing includes data conversion, and the processing unit 720 is specifically configured to convert the data formats of the data of the first operating system and the data of the second operating system into the same data format.

[0160] In some embodiments, before calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the above-mentioned processing unit 720 is also used to send a communication request message to the cloud server, and the communication request message is used to establish communication between the first operating system and the cloud server; in response to receiving a communication response message sent by the cloud server, establishing a connection with the cloud server; in response to not receiving a communication response message after a preset period of time, calling the first operating system to re-send the communication request message to the cloud.

[0161] In some embodiments, the data of the above-mentioned first operating system includes at least one of the following: application layer data of the first operating system, framework layer data of the first operating system, vehicle data of the first operating system, common control data of the first operating system, and application data of the first operating system; the data of the second operating system includes at least one of the following: application layer data of the second operating system, framework layer data of the second operating system, vehicle data of the second operating system, common control data of the second operating system, and application data of the second operating system.

[0162] Figure 9 This is a schematic diagram of the structure of a device provided in an embodiment of the present application. Figure 9 As shown, the device 900 includes but is not limited to: a processor 901 and a memory 902.

[0163] The memory 902 is configured to store executable instructions of the processor 901. It is understood that the processor 901 is configured to execute instructions to implement the group fault detection method in the above embodiment.

[0164] It should be noted that those skilled in the art can understand that Figure 9 The device structure shown in the figure does not constitute a limitation of the device, and the device may include Figure 9 More or fewer components may be shown, or certain components may be combined, or the components may be arranged differently.

[0165] The processor 901 is the control center of the device, connecting the various parts of the entire device using various interfaces and lines. By running or executing software programs and / or modules stored in the memory 902 and accessing data stored in the memory 902, it performs various functions of the device and processes data, thereby monitoring the entire device. The processor 901 may include one or more processing units. Optionally, the processor 901 may integrate an application processor and a modem processor, wherein the application processor primarily processes the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor described above may not be integrated into the processor 901.

[0166] The memory 902 can be used to store software programs and various data. The memory 902 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, application programs required by at least one functional module (such as a determination unit, a processing unit, etc.), etc. In addition, the memory 902 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device.

[0167] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 902 including instructions. The instructions can be executed by the processor 901 of the device 900 to implement the method in the above embodiment.

[0168] In actual implementation, Figure 8 Each module in the Figure 9 The processor 901 in the embodiment calls the computer program stored in the memory 902. The specific execution process can be referred to the description of the method part in the above embodiment, which will not be repeated here.

[0169] Optionally, the computer-readable storage medium may be a non-temporary computer-readable storage medium, for example, the non-temporary computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0170] In an exemplary embodiment, the present application also provides a vehicle, which can be executed by the processor 901 of the device to complete the method in the above embodiment.

[0171] In an exemplary embodiment, the present application also provides a computer program product including one or more instructions, which can be executed by the processor 901 of the device to implement the method in the above embodiment.

[0172] It should be noted that when the instructions in the above-mentioned computer-readable storage medium or one or more instructions in the computer program product are executed by the processor of the device, the various processes of the above-mentioned method embodiment are implemented and the same technical effect as the above-mentioned method can be achieved. To avoid repetition, they will not be repeated here.

[0173] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete the full classification or partial functions described above.

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

[0175] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0176] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0177] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the full classification part or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute the full classification part or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

[0178] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A data reporting method, characterized in that: include: In response to the data collection instruction, calling the first operating system to collect data of the first operating system and data of the second operating system; In response to the data reporting instruction, the first operating system is called to report the data of the first operating system and the data of the second operating system to the cloud server.

2. The method according to claim 1, characterized in that Before responding to the data collection instruction, the method further includes: Receive a data collection instruction, wherein the data collection instruction is triggered by at least one of the following methods: A change in the vehicle's status is detected; Detecting a user's control operation; The trigger is performed according to a first preset time interval.

3. The method according to claim 1, characterized in that Before responding to the data reporting instruction, the method further includes: Receive a data reporting instruction, where the data reporting instruction is triggered by at least one of the following methods: Receiving a data acquisition request sent by the cloud server; The trigger is performed according to a second preset time interval.

4. The method according to claim 1, wherein After calling the first operating system to collect data of the first operating system and data of the second operating system, the method further includes: The data of the first operating system and the data of the second operating system are displayed on the display interface.

5. The method according to claim 1, characterized in that After calling the first operating system to collect data of the first operating system and data of the second operating system, the method further includes: When the first operating system collects data of the first operating system and data of the second operating system and there is an abnormality, Displaying prompt information in the display interface; and / or, Prompt information is announced through voice broadcast.

6. The method according to claim 1, characterized in that After calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the method further includes: receiving, through the first operating system, a data analysis report sent by the cloud server, the data analysis report including the data analysis report of the first operating system and / or the data analysis report of the second operating system; The data analysis report is displayed on a display interface.

7. The method according to claim 1, characterized in that The calling the first operating system to collect data of the first operating system and data of the second operating system includes: Collecting data of the first operating system based on the first data collection SDK in the first operating system; collecting data of the second operating system based on a second data collection SDK in the second operating system; The collection server in the first operating system is called to obtain the data of the first operating system from the first data collection SDK, and to obtain the data of the second operating system from the second data collection SDK.

8. The method according to claim 7, characterized in that The calling of the collection server in the first operating system to obtain the data of the first operating system from the first data collection SDK, and obtaining the data of the second operating system from the second data collection SDK, includes: The acquisition server sends a data acquisition request to the first data acquisition SDK and the second data acquisition SDK respectively through a virtual socket VSOCK channel; In response to the data acquisition request, the first data acquisition SDK sends the data of the first operating system to the acquisition server through the VSOCK channel; In response to the data acquisition request, the second data acquisition SDK sends the data of the second operating system to the acquisition server through the VSOCK channel.

9. The method according to claim 7, characterized in that After collecting data of the second operating system based on the second data collection SDK in the second operating system, the method further includes: Calling the second data acquisition SDK to store the data of the second operating system into the shared memory; The calling of the collection server in the first operating system to obtain the data of the second operating system from the second data collection SDK includes: The acquisition server is called to read the data of the second operating system from the shared memory.

10. The method according to claim 1, characterized in that Before calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the method further includes: Preprocessing the data of the first operating system and the data of the second operating system.

11. The method according to claim 10, characterized in that The preprocessing includes data cleaning, and the preprocessing of the data of the first operating system and the data of the second operating system includes: removing duplicate data from the data of the first operating system and the data of the second operating system; removing noise data from the data of the first operating system and the data of the second operating system; Data with missing fields in the data of the first operating system and the data of the second operating system are removed.

12. The method according to claim 10, characterized in that The preprocessing includes data verification, and the preprocessing of the data of the first operating system and the data of the second operating system includes: Verifying data integrity of the first operating system and the second operating system; Verifying data consistency between the first operating system data and the second operating system data; The data of the first operating system and the data of the second operating system are verified for data accuracy.

13. The method according to claim 10, characterized in that The preprocessing includes data conversion, and the preprocessing of the data of the first operating system and the data of the second operating system includes: The data formats of the data of the first operating system and the data of the second operating system are converted into the same data format.

14. The method according to claim 1, wherein Before calling the first operating system to report the data of the first operating system and the data of the second operating system to the cloud server, the method further includes: Sending a communication request message to the cloud server, wherein the communication request message is used to establish communication between the first operating system and the cloud server; In response to receiving the communication response message sent by the cloud server, establishing a connection with the cloud server; In response to not receiving the communication response message after a preset period of time, calling the first operating system to resend the communication request message to the cloud.

15. The method according to any one of claims 1 to 14, characterized in that The data of the first operating system includes at least one of the following: application layer data of the first operating system, framework layer data of the first operating system, vehicle computer data of the first operating system, common control data of the first operating system, and application data of the first operating system; The data of the second operating system includes at least one of the following: application layer data of the second operating system, framework layer data of the second operating system, vehicle computer data of the second operating system, common control data of the second operating system, and application data of the second operating system.

16. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the data reporting method according to any one of claims 1 to 15.

17. A computer-readable storage medium, characterized in that When the computer-executable instructions stored in the computer-readable storage medium are executed by a processor of a device, the device can execute the data reporting method according to any one of claims 1 to 15.

18. A vehicle, characterized in that: include: The electronic device of claim 16, or the computer-readable storage medium of claim 17.

19. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed on a processor of a device, the device is enabled to execute the data reporting method according to any one of claims 1 to 15.

Images