Information synchronization method, information synchronization system, electronic device, and readable storage medium

Abstract

This application provides an information synchronization method, an information synchronization system, an electronic device, and a readable storage medium. In some embodiments, the information synchronization method includes the following steps: in response to receiving an information synchronization request, determining identification information corresponding to the information synchronization request; determining the target vehicle-mounted application corresponding to the identification information; acquiring vehicle information sent by the target vehicle-mounted application, and sending the vehicle information to the development end so that the development end can synchronously display the vehicle information.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of computer technology, and more particularly, to an information synchronization method, an information synchronization system, an electronic device and a readable storage medium. BACKGROUND

[0002] Currently, developers will use development tools to develop and debug applications installed on vehicles, but in the prior art, the information of the application displayed on the car screen cannot be synchronized to the development tool, resulting in low development efficiency. SUMMARY

[0003] Embodiments of the present application provide an information synchronization method, an information synchronization system, an electronic device and a readable storage medium, which can at least partially solve the above problems or other problems existing in the prior art.

[0004] In one aspect, the embodiments of the present application provide an information synchronization method, comprising the following steps: in response to receiving an information synchronization request, determining identification information corresponding to the information synchronization request; determining a target car machine application corresponding to the identification information; obtaining vehicle information sent by the target car machine application, and sending the vehicle information to a development end to enable the development end to synchronously display the vehicle information.

[0005] In another aspect, the embodiments of the present application provide an information synchronization system, comprising: a car machine, a synchronization server and a development end, wherein the car machine is installed with at least one car machine application, and the car machine application is used to send an information synchronization request; the synchronization server is used to receive the information synchronization request, determine identification information corresponding to the information synchronization request, determine a target car machine application corresponding to the identification information, and obtain and send vehicle information sent by the target car machine application; and the development end is used to receive and synchronously display the vehicle information.

[0006] In another aspect, the embodiments of the present application provide an electronic device, comprising: at least one processor and a memory. The memory is in communication connection with the at least one processor and stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the information synchronization method mentioned in the above embodiments.

[0007] In another aspect, the embodiments of the present application provide a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the information synchronization method mentioned in the above embodiments.

[0008] According to some embodiments of this application, the information synchronization method, information synchronization system, electronic device, and readable storage medium provide that the vehicle-mounted application sends an information synchronization request to the server. After receiving the information synchronization request, the server determines the identification information corresponding to the information synchronization request and the vehicle-mounted application corresponding to the identification information. Then, it obtains the vehicle information sent by the vehicle-mounted application and sends the vehicle information to the development end. The development end will synchronously display the vehicle information, thereby realizing information synchronization between the vehicle-mounted terminal and the development end. Developers can further develop and debug the vehicle-mounted system or vehicle-mounted application based on the vehicle information synchronously displayed on the development end, improving the efficiency of development and debugging.

[0009] In some implementations, the identification information includes a vehicle identification number and an application identification number; and the step of determining the target vehicle application corresponding to the identification information includes: determining the target vehicle identification number corresponding to the vehicle identification number; and determining the target vehicle application from the vehicle applications installed on the target vehicle identification number based on the application identification number.

[0010] In some implementations, the target vehicle infotainment application is a 3D type application; and the step of identifying the target vehicle infotainment application from the vehicle infotainment applications installed on the target vehicle infotainment system based on the application identifier includes: identifying all 3D type applications from the vehicle infotainment applications installed on the target vehicle infotainment system; and identifying the target vehicle infotainment application from all 3D type applications based on the application identifier.

[0011] In some implementations, the identification information is generated based on the following steps: in response to receiving a registration instruction sent by the target vehicle infotainment application at startup, determining the application identifier of the target vehicle infotainment application and the vehicle infotainment identifier of the vehicle infotainment system on which the target vehicle infotainment application is installed; and associating and saving the application identifier and the vehicle infotainment identifier as identification information.

[0012] In some implementations, vehicle information includes: vehicle status information; and the step of sending vehicle information to the development end includes: sending the vehicle status information to the development end so that the development end can perform 3D rendering and display of the status information and generate a rendering interface.

[0013] In some implementations, the vehicle information also includes: road condition information during vehicle travel; and the step of sending the vehicle information to the development end further includes: sending the road condition information during vehicle travel to the development end so that the development end can perform 3D rendering and display of the road condition information on the rendering interface.

[0014] In some implementations, the information synchronization method further includes the following steps: obtaining log information output by the target vehicle application; and sending vehicle information to the development end, including sending vehicle information and log information to the development end.

[0015] In some implementations, the information synchronization method further includes the following steps: acquiring the interface content of the target vehicle infotainment application and sending the interface content to the development end so that the development end can adjust the interface content and generate control instructions based on the adjustment results; wherein, the interface content includes: interface layout and / or interface elements, and the control instructions include: interface layout adjustment instructions and / or interface element adjustment instructions.

[0016] In some implementations, the information synchronization method further includes the following steps: receiving control commands sent by the development end; and sending the control commands to the target vehicle infotainment application so that the target vehicle infotainment application adjusts the interface content based on the control commands.

[0017] In some implementations, the synchronization server is also used to acquire and send log information output by the target vehicle infotainment application; the development end is also used to receive and synchronously display vehicle information and log information.

[0018] In some implementations, the information synchronization request includes an error request; and the development side is also used for 3D rendering to generate the processing result corresponding to the error request based on the rendered information. Attached Figure Description

[0019] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings. Wherein:

[0020] Figure 1 This is a flowchart illustrating the information synchronization method according to the first embodiment of this application;

[0021] Figure 2 This is a flowchart illustrating the information synchronization method according to the second embodiment of this application;

[0022] Figure 3 This is a schematic diagram of the system framework for the information synchronization method mentioned in the embodiments of this application;

[0023] Figure 4 These are schematic block diagrams of electronic devices according to some embodiments of this application. Detailed Implementation

[0024] To better understand this application, various aspects of this application will be described in more detail with reference to the accompanying drawings. It should be understood that these detailed descriptions are merely illustrative of exemplary embodiments of this application and are not intended to limit the scope of this application in any way. The expression "and / or" includes any and all combinations of one or more of the associated listed items.

[0025] It should also be understood that expressions such as "comprising," "including," "having," "containing," and / or "comprising" are open-ended rather than closed-ended expressions in this specification, indicating the presence of the stated features, elements, and / or components, but not excluding the presence of one or more other features, elements, components, and / or combinations thereof. Furthermore, when expressions such as "at least one of..." appear after a list of listed features, they modify the entire list of features, not just individual elements in the list. Additionally, when describing embodiments of this application, the word "may" is used to mean "one or more embodiments of this application." And the term "exemplary" is intended to refer to examples or illustrations.

[0026] Unless otherwise specified, all terms used herein (including engineering and technical terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that, unless expressly stated herein, terms defined in common dictionaries shall be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and not as having an idealized or overly formalized meaning.

[0027] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. Furthermore, unless explicitly limited or contradicted by the context, the specific steps included in the methods described in this application are not limited to the order in which they are described, but can be performed in any order or in parallel. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0028] Figure 1 This is a flowchart illustrating an information synchronization method according to a first embodiment of this application. The screen projection method 100 may include the following steps:

[0029] Step 101: In response to receiving an information synchronization request, determine the identification information corresponding to the information synchronization request.

[0030] In this embodiment, when the server receives an information synchronization request sent by the vehicle application on the vehicle terminal, it will determine the identification information corresponding to the information synchronization request, that is, determine the identification information of the vehicle application.

[0031] The in-vehicle infotainment system refers to the vehicle-mounted application system that has multiple in-vehicle applications installed. These applications are software systems or applications used in vehicles and can provide users with various functions such as navigation, music, calls, video, and games.

[0032] As examples, in-vehicle applications may include: 1) Infotainment system applications, such as multimedia entertainment applications and in-vehicle voice assistant applications. 2) Vehicle health and diagnostic applications, such as in-vehicle diagnostic systems and battery monitoring applications. 3) Security and monitoring applications, such as vehicle monitoring and anti-theft systems. 4) Cloud and networking applications, such as vehicle-to-everything (V2X) and remote control and services applications. 5) Personalization and comfort applications, such as cabin environment control and lighting and ambiance control.

[0033] In-vehicle applications may also include: 6) Driving-related applications, such as vehicle control applications, driver assistance system applications, and autonomous driving applications. Vehicle control applications may include: powertrain control systems, braking system management, and steering system management. Driver assistance system applications may include: adaptive cruise control (automatically adjusting vehicle speed based on the speed of the vehicle in front to maintain a safe distance), lane keeping assist (detecting lane lines and controlling the steering wheel to prevent the vehicle from deviating from its lane), blind spot monitoring (reminding the driver of vehicles or pedestrians in blind spots), automatic parking systems (detecting parking spaces through sensors and automatically performing parking operations), and collision warning and emergency braking (detecting potential collision risks and triggering alarms or automatic braking). Autonomous driving applications may include: environmental perception and processing (perceiving the vehicle's surrounding environment through cameras, radar, lidar, etc.), path planning and decision-making (planning the vehicle's driving path in real time, avoiding obstacles, and obeying traffic rules), and motion control (executing the planned path, including acceleration, steering, and braking).

[0034] Among the aforementioned in-vehicle infotainment applications, driving-related applications are common 3D applications (hereinafter referred to as 3D applications), such as adaptive cruise control, lane keeping assist, blind spot monitoring, automatic parking systems, collision warning and emergency braking, route planning and decision-making, etc. 3D applications in vehicles are becoming increasingly important in modern automobiles, primarily used to enhance the driving experience, improve safety, support autonomous driving, and achieve intelligent interaction.

[0035] It should be understood that, without departing from the teachings of this application, in-vehicle applications may also be other types of applications, and this application does not limit the type of in-vehicle application.

[0036] The in-vehicle application installed on the in-vehicle infotainment system can send a request to the executing entity for information synchronization, namely an information synchronization request. This information synchronization request is used to indicate that the in-vehicle system and the development end are synchronizing information.

[0037] In some embodiments of this application, the vehicle-mounted infotainment system can automatically send information synchronization requests to the server at preset intervals to achieve information synchronization with the development side via the server. For example, the vehicle-mounted application can automatically send information synchronization requests to the server at five-minute intervals. As another example, the vehicle-mounted application can automatically send information synchronization requests to the server at three-minute intervals.

[0038] It should be understood that, without departing from the teachings of this application, the interval duration can be set according to actual needs, and this application does not impose any restrictions on the value of the interval duration.

[0039] In some embodiments of this application, when a vehicle malfunctions or the information displayed by the vehicle-mounted application is incorrect, the user may actively send an information synchronization request to the server. In this case, the information synchronization request may be an error reporting request.

[0040] It should be understood that, without departing from the teachings of this application, the vehicle-mounted application may also send information synchronization requests to the server in other circumstances, and the vehicle-mounted application may send information synchronization requests to the server in other ways. This application does not restrict the timing or method of the vehicle-mounted application sending information synchronization requests.

[0041] Furthermore, the development and debugging of in-vehicle infotainment applications rely on a range of development tools covering multiple areas such as perception, navigation, control, communication, data analysis, and human-machine interaction. Developers can use these tools to develop and debug in-vehicle infotainment applications.

[0042] As examples, development tools typically include: 1) Debugging and testing tools, such as hardware-in-the-loop testing tools and sensor data playback tools. 2) Control and motion planning development tools, such as control algorithm development tools and simulation and verification tools. 3) Data processing and machine learning tools, such as deep learning frameworks and big data processing tools. 4) Communication and networking debugging tools, such as communication protocol debugging tools and vehicle networking development tools.

[0043] Development tools may also include: 5) Environmental perception and sensor processing tools, such as point cloud processing tools, image processing tools, sensor simulation tools, etc. 6) Navigation and path planning development tools, such as high-precision map and SLAM tools, path planning development tools, etc. 7) Human-computer interaction (HMI) development tools, such as 3D visualization development tools, in-vehicle interface design tools. 3D visualization development tools may also include: Unity 3D, used to develop in-vehicle 3D display interfaces or augmented reality (AR) navigation systems; Unreal Engine, suitable for high-precision 3D visualization and virtual cockpit design. In-vehicle interface design tools may also include: Qt, a tool for developing interface tools for in-vehicle infotainment systems (IVI); Kanzi, a tool specifically designed for in-vehicle HMIs, supporting multi-screen interaction and 3D visualization.

[0044] Among the aforementioned development tools, environmental perception and sensor processing tools, navigation and path planning development tools, and human-computer interaction development tools are all common 3D development tools (hereinafter referred to as 3D development tools), such as point cloud processing tools, path planning development tools, Unity3D, etc.

[0045] The development and debugging of in-vehicle applications require extensive tool support, covering areas such as sensor processing, algorithm development, simulation testing, communication debugging, and human-machine interaction design. The combined use of these tools helps developers efficiently build, validate, and optimize vehicle application systems, providing reliable support for autonomous driving and intelligent connected technologies.

[0046] It should be understood that, without departing from the teachings of this application, the development tool may be other types of development tools, and this application does not limit the type of development tool.

[0047] In some embodiments of this application, the vehicle-mounted application will pre-register its identification information (e.g., application ID) with the server. After receiving the information synchronization request sent by the vehicle-mounted application, the server will determine the identification information corresponding to the vehicle-mounted application that sent the information synchronization request.

[0048] Step 102: Determine the target vehicle infotainment application corresponding to the identification information.

[0049] The server determines the in-vehicle infotainment application corresponding to the identification information, i.e., the target in-vehicle infotainment application. Since in-vehicle applications pre-register their identification information with the server, the server stores the mapping between identification information and in-vehicle applications. Therefore, the server can determine which in-vehicle application a particular application corresponds to based on the identification information, that is, it can identify the target in-vehicle infotainment application based on the identification information.

[0050] In some embodiments of this application, when the vehicle-mounted application starts up, it sends a registration command to the server. After receiving the registration command, the server determines the identification information of the vehicle-mounted application that sent the registration command and records the ID information (identification information) of the current application, thereby obtaining the correspondence between the vehicle-mounted application and the identification. Therefore, the server can determine the corresponding target vehicle-mounted application based on the identification information.

[0051] In some embodiments of this application, the identification information includes a vehicle-mounted unit (VMU) identifier and an application identifier. The VMU identifier is the identification information of the VMU itself, used to distinguish different VMUs. The application identifier is the identification information of the VMU application, used to distinguish different VMU applications installed on the same VMU. When a VMU application starts, it sends a registration command to the server. Upon receiving the registration command, the server determines the VMU identifier of the VMU that sent the registration command and the corresponding application identifier. Then, it associates and saves the VMU identifier and application identifier as identification information. By binding the VMU application ID to the VMU ID, even if multiple VMU applications are installed on each VMU, they can be distinguished.

[0052] Accordingly, after determining the identification information corresponding to the information synchronization request, the server first identifies the target vehicle-to-vehicle (VTV) unit from among numerous VTV units. Then, it identifies the VTV application corresponding to the application identifier in the identification information from among the multiple VTV applications installed on the target VTV unit. In other words, the server can quickly determine the corresponding VTV unit based on the VTV unit identifier in the identification information, and then quickly determine the corresponding VTV application from the applications installed on that VTV unit based on the application identifier, thereby improving the accuracy of determining the target VTV application based on the identification information.

[0053] In some embodiments of this application, vehicle-mounted applications can be further divided into 3D applications and non-3D applications (i.e., non-3D type applications). Therefore, when a vehicle-mounted application is registered with the server, the server will divide all applications on the vehicle-mounted terminal into 3D applications and non-3D applications.

[0054] In some embodiments of this application, the target in-vehicle infotainment application is a 3D application. After determining the target in-vehicle infotainment system based on the in-vehicle infotainment system identifier in the identification information, the server will identify all 3D applications from all applications installed on the target in-vehicle infotainment system. Then, based on the application identifier in the identification information, the server will identify the target in-vehicle infotainment application from all 3D applications. By classifying in-vehicle infotainment applications into 3D and non-3D applications, the search for the target in-vehicle infotainment application can be more targeted, improving the efficiency of identifying the target in-vehicle infotainment application.

[0055] In some embodiments of this application, the target vehicle infotainment application is a non-3D application. In this case, after the server determines the target vehicle infotainment system based on the vehicle infotainment system identifier in the identification information, it will determine all non-3D applications from all applications installed on the target vehicle infotainment system. Then, based on the application identifier in the identification information, it will determine the target vehicle infotainment application from all non-3D applications.

[0056] Step 103: Obtain the vehicle information sent by the target vehicle application and send the vehicle information to the development end so that the development end can display the vehicle information synchronously.

[0057] In this embodiment, after determining the target vehicle infotainment application that sent the information synchronization request, the server obtains the vehicle information sent by the target vehicle infotainment application and forwards the vehicle information to the development end, so that the development end can synchronously display the vehicle information sent by the target vehicle infotainment application, thereby realizing information synchronization between the vehicle infotainment end and the development end.

[0058] In some embodiments of this application, vehicle information includes vehicle status information, which refers to some parameter information of the vehicle itself. Specifically, the status information may include: 1) basic operating status information, such as powertrain status (engine status, etc.), braking system status (brake status, etc.), steering system status (steering angle, etc.); 2) vehicle safety and diagnostic information, such as fault information, tire pressure and tire status, safety system status (airbag status, seat belt status, etc.); 3) vehicle status and control information, such as body status (door status, window status, light status, etc.), air conditioning and cabin status, etc.

[0059] It should be understood that, without departing from the teachings of this application, the vehicle status data may also be other types of data, and this application does not impose any restrictions on this.

[0060] The server retrieves the vehicle's status information from the target in-vehicle application and sends it to the development tools on the development side. The development tools then render and display the vehicle's status information in 3D, generating a rendered 3D interface. Developers can then more intuitively view the vehicle's information and status through this rendered 3D interface, thus improving development and debugging efficiency.

[0061] In some embodiments of this application, vehicle information includes road condition information during vehicle operation. Specifically, road condition information may include: lidar information, such as the distance, size, and speed of surrounding objects; camera visual data, such as lane lines, traffic signs, traffic lights, and detection information of pedestrians and vehicles; and millimeter-wave radar information, such as the relative speed and distance of objects ahead. Road condition information may also include: weather and environmental conditions, such as rain sensor detection (whether it is raining), and external light intensity (whether headlights need to be turned on); and road condition information such as road surface slippage detection and surrounding obstacle information.

[0062] It should be understood that, without departing from the teachings of this application, road condition information during vehicle operation may also be other types of data, and this application does not impose any restrictions on this.

[0063] The server acquires road condition information during the vehicle's movement, initiated by the target in-vehicle application, and sends this information to the development team. This allows the development tools to further render and display the road condition information on the generated 3D interface. In other words, the development tools will render the road condition information on top of the vehicle's status information rendering interface, resulting in a 3D rendered interface. Developers can combine this vehicle status information with the road condition information during development and debugging, thereby improving both efficiency and accuracy.

[0064] In some embodiments of this application, in addition to obtaining vehicle information sent by the target vehicle infotainment application, the server also obtains log information output by the target vehicle infotainment application. Therefore, the server sends both the vehicle information and the log information to the development end. Thus, the development tool can not only synchronously display vehicle information but also synchronize the vehicle infotainment application's logs. By comprehensively referring to both vehicle information and log information, developers can perform development and debugging more quickly and accurately. When the vehicle infotainment application encounters errors, they can more quickly identify the problem and improve problem-solving efficiency.

[0065] Currently, when 3D applications are installed in vehicle infotainment systems, they are often based on a rig (a rig is a device used by developers that consists only of a host and a screen, and is part of the vehicle). Since there is no actual vehicle control data, the content displayed on the vehicle's screen cannot be synchronized to the development tools in real time. Furthermore, problems encountered by users during vehicle use are not logged. As a result, when problems occur, developers cannot resolve them in a timely manner, thus reducing the user experience.

[0066] According to some implementation methods of this application, the vehicle-mounted application sends an information synchronization request to the server. After receiving the information synchronization request, the server determines the identification information corresponding to the information synchronization request and the vehicle-mounted application corresponding to the identification information. Then, it obtains the vehicle information sent by the vehicle-mounted application and sends the vehicle information to the development end. The development end will display the vehicle information synchronously, thereby realizing information synchronization between the vehicle-mounted application and the development end. Developers can further develop and debug the vehicle-mounted application or vehicle-mounted application based on the vehicle information synchronously displayed on the development end, thereby improving the efficiency of development and debugging.

[0067] Figure 2 This is a flowchart illustrating the information synchronization method according to the second embodiment of this application. This embodiment is largely the same as the first embodiment, the main difference being that it exemplarily describes the process of controlling the interface of the vehicle-mounted application. For example... Figure 2 As shown, the information synchronization method 200 may include the following steps:

[0068] Step 201: In response to receiving an information synchronization request, determine the identification information corresponding to the information synchronization request.

[0069] Step 202: Determine the target vehicle infotainment application corresponding to the identification information.

[0070] Step 203: Obtain the vehicle information sent by the target vehicle application and send the vehicle information to the development end so that the development end can display the vehicle information synchronously.

[0071] In this embodiment, steps 201-203 and Figure 1 Steps 101-103 shown are largely the same and will not be repeated here.

[0072] Step 204: Obtain the interface content of the target vehicle infotainment application and send the interface content to the development end so that the development end can adjust the interface content and generate control commands based on the adjustment results.

[0073] In this embodiment, the server also obtains the interface content of the target vehicle infotainment application, that is, obtains the interface content displayed on the screen of the target vehicle infotainment application, and sends the interface content to the development end. The developers can adjust it according to the interface content displayed by the development tool, generate adjustment results, and generate control instructions based on the adjustment results. The control instructions indicate how to adjust the display interface of the target vehicle infotainment application and how to adjust it.

[0074] In some embodiments of this application, the interface content includes: interface layout and / or interface elements. Specifically, the server obtains the interface layout information and various elements of the target in-vehicle application displayed on the in-vehicle screen. Interface elements may include toolbars, controls, fields, etc., while the interface layout refers to the arrangement or positional relationship of the various elements. The development tool provides interactive operation tools, allowing developers to adjust the interface content through clicks, drags, zooms, and other operations, and generate control commands based on the developers' adjustments.

[0075] Accordingly, control instructions include: interface layout adjustment instructions and / or interface element adjustment instructions. That is, developers can perform adjustment operations on interface elements, including adding, deleting, etc., thereby generating interface element adjustment instructions. Developers can also adjust the layout of interface elements, such as adjusting the position of each interface element, thereby generating interface layout adjustment instructions.

[0076] Step 205: Receive control commands sent from the development end.

[0077] The server will receive control commands sent by the development team, namely, commands to adjust the interface layout and / or the interface elements.

[0078] Step 206: Send control commands to the target vehicle infotainment application so that the target vehicle infotainment application can adjust the interface content based on the control commands.

[0079] The server will send the received control commands to the target vehicle infotainment application, which will then adjust the interface content according to the control commands.

[0080] In some embodiments of this application, the control instructions include instructions for adjusting interface elements. The target vehicle infotainment application will perform operations such as adding or deleting elements displayed on the interface according to the instructions. For example, adding or deleting fields displayed on the interface. Another example is adding or deleting controls displayed on the interface. Thus, the interface elements displayed by the vehicle infotainment application are adjusted synchronously according to the adjustment results of the interface elements on the development side, realizing the control of the interface elements of the vehicle infotainment application by the development side.

[0081] In some embodiments of this application, the control instructions include interface layout adjustment instructions. The target vehicle infotainment application adjusts the interface layout according to the instructions. For example, the position of the elements displayed on the interface is adjusted. Another example is the overall layout of the interface content. Thus, the interface layout displayed by the vehicle infotainment application is adjusted synchronously based on the interface layout adjustment results from the development end, achieving control of the vehicle infotainment application's interface layout from the development end.

[0082] In some embodiments of this application, the control instructions include instructions for adjusting the interface layout and instructions for adjusting interface elements. The target vehicle infotainment application will perform operations such as adding or deleting elements displayed on the interface according to the instructions. The target vehicle infotainment application will also adjust the layout of the interface according to the instructions. For example, it may adjust the position of the elements displayed on the interface.

[0083] It should be understood that, without departing from the teachings of this application, step 203 may be performed before steps 204-206, or after steps 204-206, or even simultaneously with steps 204-206. This application does not restrict the execution order of steps 203 and steps 204-206.

[0084] According to some implementation methods of this application, the vehicle-mounted application sends an information synchronization request to the server. After receiving the information synchronization request, the server determines the identification information corresponding to the information synchronization request and the vehicle-mounted application corresponding to the identification information. Then, it obtains the vehicle information sent by the vehicle-mounted application and sends the vehicle information to the development end. The development end will synchronously display the vehicle information, thereby realizing information synchronization between the vehicle-mounted application and the development end. In addition, the server also sends the interface content of the target vehicle-mounted application to the development end. Developers can control and adjust the interface content displayed on the target vehicle-mounted application screen and synchronize the adjustment results to the target vehicle-mounted application. This allows developers to develop and debug the vehicle-mounted system or vehicle-mounted application based on the synchronously displayed vehicle information, while also controlling and adjusting the interface of the vehicle-mounted application, realizing two-way information interaction between the vehicle-mounted application and the development end.

[0085] It should be noted that the acquisition, storage, and application of user personal information involved in the technical solution disclosed herein all comply with relevant laws and regulations and do not violate public order and good morals. It should also be noted that the information in this embodiment was obtained after being authorized by the user (i.e., with the user's consent).

[0086] The steps of the various methods described above are only for clarity. In implementation, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the protection scope of this disclosure. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the protection scope of this disclosure.

[0087] Figure 3 This is a schematic diagram of the system framework for the information synchronization method mentioned in the embodiments of this application. For example... Figure 3As shown, the system 300 may include a vehicle-mounted infotainment system 310, a synchronization server 320, and a development terminal 330. The vehicle-mounted infotainment system 310 can synchronize information with the development terminal 330 through the synchronization server 320, and the development terminal 330 can also synchronize information with the vehicle-mounted infotainment system 310 through the synchronization server 320; that is, the vehicle-mounted infotainment system 310 and the development terminal 330 achieve bidirectional information interaction through the synchronization server 320. Both the vehicle-mounted infotainment system 310 and the development terminal 330 have network connections, enabling the vehicle-mounted infotainment system 310 to communicate with the synchronization server 320, and the development terminal 330 to communicate with the synchronization server 320.

[0088] The vehicle infotainment system 310 has multiple in-vehicle applications installed, namely in-vehicle application 1, in-vehicle application 2, ..., in-vehicle application N (N is a positive integer). These applications can send information synchronization requests to the synchronization server 320. Upon receiving a synchronization request, the synchronization server 320 determines the corresponding identifier, identifies the target application based on this identifier, retrieves the vehicle information sent by the target application, and sends this information to the development client 330. The development client 330 receives the vehicle information from the synchronization server 320 and displays it synchronously. The development client 330 can have multiple development tools installed, namely development tool 1, development tool 2, ..., development tool M (M is a positive integer).

[0089] In some implementations, the identification information includes a vehicle-mounted unit (VMU) identifier and an application identifier. The VMU identifier is the identification information of the VMU itself, used to distinguish different VMUs. The application identifier is the identification information of the VMU application, used to distinguish different VMU applications installed on the same VMU. The synchronization server 320 first determines the target VMU from among many VMUs based on the VMU identifier, and then determines the target VMU application from at least one VMU application installed on the target VMU based on the application identifier.

[0090] In some implementations, the target vehicle infotainment application is a 3D application, and driving-related applications are common 3D applications, such as adaptive cruise control, lane keeping assist, blind spot monitoring, automatic parking system, collision warning and emergency braking, route planning and decision-making, etc. Then, after determining the target vehicle infotainment system based on the vehicle infotainment system identifier in the identification information, the synchronization server 320 will identify all 3D applications from all applications installed on the target vehicle infotainment system, and then determine the target vehicle infotainment application from all 3D applications based on the application identifier in the identification information.

[0091] When the target vehicle infotainment application is a 3D application, the corresponding development tools on the development side are 3D development tools. Environmental perception and sensor processing tools, navigation and path planning development tools, and human-computer interaction development tools are all common 3D development tools, such as point cloud processing tools, path planning development tools, Unity 3D, etc.

[0092] In some implementations, the synchronization server 320 obtains the vehicle status information sent by the target vehicle infotainment application and sends the vehicle status information to the development server 330. The development server 330 receives the vehicle status information and performs 3D rendering on it, thereby generating a 3D rendered interface on the development server 330. The vehicle status information may include: basic operating status information, vehicle safety and diagnostic information, vehicle status and control information, etc.

[0093] In some implementations, the synchronization server 320 also acquires road condition information during vehicle operation sent by the target vehicle application and sends this information to the development server 330. The development server 330 receives and further renders and displays the road condition information on the 3D rendering interface. The road condition information during vehicle operation may specifically include: distance, size, and speed of surrounding objects; lane lines; traffic signs; traffic lights; pedestrian and vehicle detection information; relative speed and distance of objects ahead; road surface slippage detection; and surrounding obstacle information.

[0094] In some implementations, the synchronization server 320 also acquires log information output by the target vehicle infotainment application and sends it to the development server 330. Therefore, the development server 330 can synchronously display not only vehicle information but also the log information from the vehicle infotainment application. By comprehensively referencing both vehicle information and log information, developers can develop and debug more quickly and accurately, and when the vehicle infotainment application reports errors, they can more quickly identify the problem, improving problem-solving efficiency.

[0095] In some implementations, the information synchronization request sent by the in-vehicle application installed on the in-vehicle infotainment system 310 is an error reporting request. That is, when a vehicle malfunctions or the information displayed by the in-vehicle application is incorrect, the user will actively send an information synchronization request to the synchronization server 320; this information synchronization request is thus an error reporting request. After receiving the error reporting request, the synchronization server 320 determines the identification information corresponding to the error reporting request and identifies the target in-vehicle application corresponding to the identification information. Then, it obtains the vehicle information sent by the target in-vehicle application and sends the vehicle information to the development end 330. Upon receiving the vehicle information, the development end 330 performs 3D rendering of the obtained vehicle information, allowing developers to debug errors based on the 3D rendered interface information and generate the processing result corresponding to the error reporting request. By synchronously displaying the vehicle information sent by the in-vehicle application to the development end, and allowing the development end to perform 3D rendering of the vehicle information so that developers can debug based on the 3D rendered interface, the efficiency of error handling is improved.

[0096] Embodiments of this application also provide an electronic device, such as... Figure 4As shown, the electronic device 400 may include: at least one processor and a memory, the memory being communicatively connected to the at least one processor and storing instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the information synchronization method mentioned in the above embodiments.

[0097] One embodiment of this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the information synchronization method mentioned in the above embodiments.

[0098] Figure 4 This is a schematic block diagram of an electronic device 400 according to some embodiments of this application. For example... Figure 4 As shown, the electronic device 400 includes a processor 401, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 402 or a computer program loaded from a memory 408 into a random access memory (RAM) 403. The RAM 403 may also store various programs and data required for the operation of the electronic device 400. The processor 401, ROM 402, and RAM 403 are interconnected via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0099] Multiple components in electronic device 400 are connected to I / O interface 405, including: input unit 406, such as buttons or a touchscreen in a vehicle infotainment system; output unit 407, connected to various types of displays, speakers, etc., to output various forms of signals; memory 408, including any medium for storing computer-executable programs; and communication unit 409, such as a network interface card (NIC), modem, or wireless transceiver. Communication unit 409 allows electronic device 400 to exchange information / data with other devices via a local area network (LAN) or other wireless communication networks.

[0100] Processor 401 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 401 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 401 performs the various methods and processes described above, such as the information synchronization method mentioned in the above embodiments. For example, in some embodiments, the information synchronization method mentioned in the above embodiments can be implemented as a computer software program, which is tangibly contained in a computer-readable storage medium, such as memory 408. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 400 via ROM 402 and / or communication unit 409. When the computer program is loaded into RAM 403 and executed by processor 401, one or more steps of the information synchronization method mentioned in the above embodiments can be performed. Alternatively, in other embodiments, processor 401 can be configured to perform the information synchronization method mentioned in the above embodiments by any other suitable means (e.g., by means of firmware).

[0101] Various aspects of this application have been described herein with reference to flowchart illustrations and / or timing diagrams of methods, apparatus (systems), and computer program products according to exemplary embodiments of this application. It should be understood that each step of the flowchart illustrations and / or timing diagrams, as well as combinations of steps in the flowchart illustrations and / or timing diagrams, can be implemented by computer-readable program instructions.

[0102] These computer-readable program instructions can be provided to a processor, general-purpose computer, special-purpose computer, or other programmable data processing unit in an electronic device to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing device, they create means for implementing the functions / steps specified in one or more steps of a flowchart and / or timing diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing device, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / steps specified in one or more steps of a flowchart and / or timing diagram.

[0103] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / steps specified in one or more steps of a flowchart and / or timing diagram.

[0104] The flowcharts and timing diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of this application. In this regard, each step in a flowchart or timing diagram may represent a module, segment, or part of an instruction that contains one or more executable instructions for implementing a specified logical function. In some alternative embodiments, the functions indicated in the steps may occur in a different order than those indicated in the drawings. For example, two consecutive steps may actually be performed substantially in parallel, and they may sometimes be performed in reverse order, depending on the functions involved. It should also be noted that each step in a timing diagram and / or flowchart, and combinations of steps in timing diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0105] The above description is merely an illustration of the embodiments of this application and the technical principles employed. Those skilled in the art should understand that the scope of protection involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the technical concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. An information synchronization method, comprising: In response to receiving an information synchronization request, determine the identification information corresponding to the information synchronization request; Determine the target in-vehicle application corresponding to the identification information; Obtain the vehicle information sent by the target vehicle infotainment application and send the vehicle information to the development end so that the development end can display the vehicle information synchronously.

2. The method according to claim 1, wherein, The identification information includes vehicle identification and application identification; as well as Determining the target vehicle application corresponding to the identification information includes: Identify the target vehicle unit corresponding to the vehicle unit identifier; Based on the application identifier, the target vehicle application is determined from the vehicle applications installed on the target vehicle system.

3. The method according to claim 2, wherein, The target in-vehicle infotainment application is a 3D application; as well as The step of determining the target in-vehicle application from the in-vehicle applications installed on the target in-vehicle system based on the application identifier includes: Identify all 3D-type applications from the in-vehicle applications installed on the target in-vehicle system; Based on the application identifier, the target vehicle infotainment application is determined from all applications of the 3D type.

4. The method according to claim 2, wherein, The identification information is generated based on the following steps: In response to receiving the registration instruction sent by the target vehicle infotainment application at startup, the application identifier of the target vehicle infotainment application and the vehicle infotainment identifier of the vehicle infotainment system on which the target vehicle infotainment application is installed are determined; The application identifier and the vehicle system identifier are associated and saved as the identifier information.

5. The method according to claim 1, wherein, The vehicle information includes: vehicle status information; and Sending the vehicle information to the development end includes: The vehicle's status information is sent to the development end, so that the development end can perform 3D rendering and display of the status information and generate a rendering interface.

6. The method according to claim 5, wherein, The vehicle information also includes: road condition information during the vehicle's journey; and Sending the vehicle information to the development end also includes: The road condition information during the vehicle's journey is sent to the development end, so that the development end can perform 3D rendering and display of the road condition information on the rendering interface.

7. The method according to claim 1, wherein, Also includes: Obtain the log information output by the target vehicle infotainment application; as well as Sending the vehicle information to the development end includes: The vehicle information and the log information are sent to the development end.

8. The method according to claim 1, wherein, Also includes: The interface content of the target vehicle infotainment application is obtained and sent to the development end so that the development end can adjust the interface content and generate control commands based on the adjustment results. The interface content includes: interface layout and / or interface elements, and the control instructions include: adjustment instructions for the interface layout and / or adjustment instructions for the interface elements.

9. The method according to claim 8, wherein, Also includes: Receive control commands sent by the development terminal; The control command is sent to the target vehicle infotainment application so that the target vehicle infotainment application adjusts the interface content based on the control command.

10. An information synchronization system, comprising: The vehicle infotainment system has at least one vehicle infotainment application installed on it, and the vehicle infotainment application is used to send information synchronization requests. A synchronization server is used to receive the information synchronization request and determine the identification information corresponding to the information synchronization request. Determine the target in-vehicle application corresponding to the identification information; Obtain and send the vehicle information sent by the target vehicle application; The development side is used to receive and synchronously display the vehicle information.

11. The system according to claim 10, wherein, The synchronization server is also used to acquire and send the log information output by the target vehicle infotainment application; The development terminal is also used to receive and synchronously display the vehicle information and the log information.

12. The system according to claim 11, wherein, The information synchronization request includes an error reporting request; and The development end is also used for 3D rendering, and generates the processing result corresponding to the error request based on the rendered information.

13. An electronic device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the information synchronization method as described in any one of claims 1 to 9.

14. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the information synchronization method as described in any one of claims 1 to 9.

Images