Data interaction method and system, computer equipment and medium

Abstract

The invention provides a data interaction method and system, computer equipment and a medium, and the method comprises the steps: carrying out the architecture design of a data interaction system according to a data source framework layer, an application program framework layer and a data interaction layer, can improve the flexibility and maintainability of the data interaction system, and optimizes the user experience. Meanwhile, for different user interface designs and user experience designs, an external pre-developed service module is directly reused for adaptation, and the service module does not need to be developed independently, so that the system development period can be shortened, the system maintenance difficulty can be reduced, and the compatibility and flexibility of the data interaction system can be improved; and the application scene of the data interaction system becomes wider, so that the market demand can be met to the greatest extent in a short time. For different hardware and software environments, because the interaction interfaces of the man-machine interaction interface provided by a software supplier are consistent, the reuse of the man-machine interaction interface can be directly realized, the development period of the system is shortened, and the development cost and maintenance difficulty of the system are reduced.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a data interaction method and system, computer equipment, and media. Background Art

[0002] With the advancement of automotive electronics, the complexity of in-vehicle systems has increased, and users' requirements for dashboard functionality and interface are becoming increasingly demanding. However, some related technologies often use a single hardware and software environment for the design of in-vehicle HMI (Human Machine Interface) systems. This results in poor flexibility, long development cycles, and difficult maintenance, making it difficult to meet the rapidly changing market demands. Summary of the Invention

[0003] In view of the above-mentioned shortcomings of the prior art, the purpose of this application is to provide a data interaction method and system, computer equipment and medium, which are used to solve the technical problems existing in the prior art.

[0004] To achieve the above-mentioned and other related purposes, the present application provides a data interaction system, which includes:

[0005] A data source framework layer, configured to update the first uplink data to a data node of the human-computer interaction interface according to preset interaction requirements, transmit the first downlink data to a preset communication node, and communicate with a pre-developed business module via a first application programming interface to invoke the business module; wherein the business module is configured to respond to vehicle-side services;

[0006] An application framework layer, communicating with the data source framework layer through a second application program interface, for acquiring second uplink data according to a response result of the business module, and transmitting the second downlink data to a preset communication node;

[0007] A data interaction layer, associated with the application framework layer, for performing data interaction with the vehicle-side business through a preset communication node;

[0008] The first uplink data and the second uplink data are data transmitted to the human-computer interaction interface at different times, and the first downlink data and the second downlink data are data transmitted to the vehicle domain controller at different times.

[0009] In one embodiment of the present application, the data interaction layer includes an in-vehicle infotainment interaction system module, a state management module, a vehicle service bus module, and a dynamic graphics rendering service module;

[0010] Among them, after the in-vehicle infotainment interaction system module is associated with the application framework layer, the vehicle-side business performs data interaction with the in-vehicle central control through the preset communication node;

[0011] After the state management module is associated with the application framework layer, the vehicle-side service performs data exchange on the service state through a preset communication node;

[0012] After the vehicle service bus module is associated with the application framework layer, the vehicle-side service performs microcontroller data interaction through a preset communication node;

[0013] After the dynamic graphics rendering service module is associated with the application framework layer, data interaction of the startup animation is performed on the vehicle-side service through a preset communication node.

[0014] In one embodiment of the present application, the application framework layer includes a lighting control list module, a warning information list module, an instrument parameter list module, and an image list module;

[0015] The in-vehicle infotainment interaction system module is associated with the lighting control list module, and performs data interaction with the in-vehicle central control for the vehicle-side service through a preset communication node;

[0016] The status management module is associated with the warning information list module, and performs data exchange of the service status of the vehicle-side service through a preset communication node;

[0017] The vehicle service bus module is associated with the instrument parameter list and performs data interaction with the microcontroller for the vehicle-side service through a preset communication node;

[0018] The dynamic graphics rendering service module is associated with the image list module, and performs data interaction of the startup animation for the vehicle-side service through a preset communication node.

[0019] In one embodiment of the present application, when the business module responds to the vehicle-side business, it also includes processing vehicle power status data, vehicle driving mode data and vehicle language mode data, and / or processing vehicle speed, vehicle fuel data and vehicle output power data, and / or processing vehicle time and vehicle internal and external temperature data, and / or processing vehicle indicator light data, and / or processing vehicle key messages, and / or processing vehicle driving data, and / or processing vehicle alarm data, and / or processing vehicle driving assistance system data, and / or processing vehicle setting data.

[0020] In one embodiment of the present application, the system further includes a rendering engine for forming the data source framework layer, the application framework layer and / or the data interaction layer, and the rendering engine is independent of the data source framework layer, the application framework layer and the data interaction layer.

[0021] The present application also provides a data interaction method, which includes the following steps:

[0022] updating the first uplink data to a data node of the human-computer interaction interface according to preset interaction requirements, transmitting the first downlink data to a preset communication node, and communicating with a pre-developed business module through a first application program interface to call the business module; wherein the business module is used to respond to the vehicle-side business;

[0023] Acquire second uplink data according to a response result of the service module, and transmit the second downlink data to a preset communication node;

[0024] Performing data interaction on the vehicle-side business through a preset communication node;

[0025] The first uplink data and the second uplink data are data transmitted to the human-computer interaction interface at different times, and the first downlink data and the second downlink data are data transmitted to the vehicle domain controller at different times.

[0026] In one embodiment of the present application, the process of performing data interaction for the vehicle-side business through a preset communication node includes: performing data interaction for the vehicle-side business with the on-board central control through a preset communication node; and / or, performing data interaction for the business status of the vehicle-side business through a preset communication node; and / or, performing data interaction for the vehicle-side business with the microcontroller through a preset communication node; and / or, performing data interaction for the vehicle-side business with the boot animation through a preset communication node.

[0027] In one embodiment of the present application, when the business module responds to the vehicle-side business, the method also includes processing vehicle power status data, vehicle driving mode data and vehicle language mode data, and / or processing vehicle speed, vehicle fuel data and vehicle output power data, and / or processing vehicle time and vehicle internal and external temperature data, and / or processing vehicle indicator light data, and / or processing vehicle key messages, and / or processing vehicle driving data, and / or processing vehicle alarm data, and / or processing vehicle driving assistance system data, and / or processing vehicle setting data.

[0028] The present application also provides a computer device, comprising a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of any one of the above-mentioned data interaction methods.

[0029] The present application also provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of any one of the above-mentioned data interaction methods when executed by a processor.

[0030] As described above, the present application provides a data interaction method and system, computer equipment and medium, which have the following beneficial effects: the present application designs the data interaction system (such as the vehicle-mounted human-computer interaction interface system) according to the data source framework layer, the application framework layer and the data interaction layer, and can perform interaction design in a modular, platform-based and intelligent manner, thereby improving the flexibility and maintainability of the data interaction system and optimizing the user experience. At the same time, for different user interface designs and user experience designs, external pre-developed business modules can be directly reused for adaptation, without the need to develop business modules separately, thereby shortening the system development cycle, reducing the difficulty of system maintenance, improving the compatibility and flexibility of the data interaction system, and making the application scenarios of the data interaction system more extensive, so as to meet market demand to the greatest extent in a short time. In addition, for different hardware and software environments, since the interaction interface of the human-computer interaction interface provided by the software supplier is consistent, there is no need to adjust the interaction interface when designing the architecture of the data interaction system, and the human-computer interaction interface can be directly reused, shortening the system development cycle, and reducing the system development cost and maintenance difficulty. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 This is a schematic diagram of the architecture of a data interaction system provided in one embodiment of the present application;

[0032] Figure 2 This is a schematic diagram of the architecture of a data interaction system provided in another embodiment of the present application;

[0033] Figure 3 A flowchart of a data interaction method provided in one embodiment of the present application;

[0034] Figure 4 The figure is a schematic diagram of the hardware structure of a computer device suitable for implementing one or more embodiments of the present application. DETAILED DESCRIPTION

[0035] The following describes the embodiments of the present application by specific specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present application. It is understood that, in the absence of conflict, the features in the following embodiments and embodiments can be combined with each other. In addition, it is understood that the illustrations provided in the following embodiments only illustrate the basic concept of the present application in a schematic manner, and only the components related to the present application are shown in the drawings rather than being drawn according to the number, shape and size of the components during actual implementation. The type, quantity and proportion of each component during actual implementation can be a kind of arbitrary change, and its component layout type may also be more complicated.

[0036] Figure 1 Schematic diagram of a data interaction system is shown. Specifically, in an exemplary embodiment, Figure 1 As shown, this embodiment provides a data interaction system, including:

[0037] The data source framework layer 110 is configured to update the first uplink data to the data node of the human-computer interaction interface according to preset interaction requirements, transmit the first downlink data to a preset communication node, and communicate with a pre-developed service module via a first application programming interface to invoke the pre-developed service module; wherein the pre-developed service module is configured to respond to vehicle-side services. In some examples, the preset interaction requirements can be selected or set based on actual circumstances. For example, when vehicle-side service processing is required on a vehicle instrument panel or vehicle display, the vehicle-side service interaction requirements at that time can be used as preset interaction requirements. In some examples, vehicle-side services include, but are not limited to, services that process vehicle power status data, vehicle driving mode data, vehicle language mode data, vehicle speed, vehicle fuel data, vehicle output power data, vehicle time, vehicle interior and exterior temperature data, vehicle indicator light data, vehicle keypad messages, vehicle driving data, vehicle alarm data, vehicle driver assistance system data, and / or vehicle setting data on the vehicle instrument panel or vehicle display. In some examples, the preset communication node can be a PPS (Persistent Publish Subscribe) node.

[0038] The application framework layer 120 communicates with the data source framework layer through the second application program interface, is used to obtain the second uplink data according to the response result of the business module, and transmit the second downlink data to the preset communication node;

[0039] The data interaction layer 130 is associated with the application framework layer and is used to interact with vehicle-side services through preset communication nodes;

[0040] The first uplink data and the second uplink data are data transmitted to the human-computer interaction interface at different times, and the first downlink data and the second downlink data are data transmitted to the vehicle domain controller at different times.

[0041] As some examples, the pre-developed business modules may be a vehicle instrument panel human-computer interaction system module (denoted as Cluster HMI), a vehicle lighting control system (denoted as TTLamp), and a background processing module (denoted as Background).

[0042] As some examples, the first uplink data and the second uplink data are data transmitted to the human-computer interaction interface through the PPS node at different times, and the first downlink data and the second downlink data are data transmitted to the vehicle domain controller through the PPS node at different times. In some examples, the same or different PPS nodes can be used between multiple uplink data, the same or different PPS nodes can be used between multiple downlink data, and the same or different PPS nodes can be used between uplink data and downlink data. As some examples, the vehicle domain controller includes but is not limited to the vehicle system, the vehicle MCU (Microcontroller Unit, microcontroller, abbreviated as MCU) and the vehicle instrument, etc., that is, the uplink data can be data transmitted from the vehicle system, vehicle MCU and vehicle instrument to the human-computer interaction interface through the PPS node, and the downlink data can be data transmitted from the vehicle system, vehicle MCU and vehicle instrument through the PPS node. For example, the data transmitted from the vehicle system, vehicle MCU and vehicle instrument to the human-computer interaction interface through the PPS node at the first moment can be used as the first uplink data, and the data transmitted from the vehicle system, vehicle MCU and vehicle instrument to the human-computer interaction interface through the PPS node at the second moment can be used as the second uplink data. The data transmitted through the PPS node to the slave vehicle system, vehicle MCU, and vehicle instrument at the third time can be regarded as the first downlink data, and the data transmitted through the PPS node to the slave vehicle system, vehicle MCU, and vehicle instrument at the fourth time can be regarded as the second downlink data. The first time, the second time, the third time, and the fourth time are different times.

[0043] As some examples, the first application programming interface and the second application programming interface may be two different application programming interfaces (APIs).

[0044] In some exemplary embodiments, the data interaction layer may include an in-vehicle infotainment interaction system module, a state management module, a vehicle service bus module, and a dynamic graphics rendering service module. The in-vehicle infotainment interaction system module, after being associated with the application framework layer, interacts with the vehicle's central control system data for the vehicle-side business via a preset communication node. The state management module, after being associated with the application framework layer, interacts with the vehicle-side business's business status data via a preset communication node. The vehicle service bus module, after being associated with the application framework layer, interacts with the microcontroller data for the vehicle-side business via a preset communication node. The dynamic graphics rendering service module, after being associated with the application framework layer, interacts with the vehicle-side business's startup animation data via a preset communication node. In some exemplary embodiments, the in-vehicle infotainment interaction system module may be denoted as IVI Interaction, the state management module may be denoted as State Manager, the vehicle service bus module may be denoted as Vehicle Service, and the dynamic graphics rendering service module may be denoted as Animation Service.

[0045] In some exemplary embodiments, the application framework layer includes a lighting control list module, a warning information list module, an instrument parameter list module, and an image list module. The in-vehicle infotainment interaction system module is associated with the lighting control list module, interacting with the vehicle's central control system via a pre-set communication node. The status management module is associated with the warning information list module, interacting with the vehicle's service status via a pre-set communication node. The vehicle service bus module is associated with the instrument parameter list module, interacting with the vehicle's microcontroller via a pre-set communication node. The dynamic graphics rendering service module is associated with the image list module, interacting with the vehicle's service startup animation via a pre-set communication node. In some exemplary embodiments, the lighting control list module can be denoted as Lamp_List, the warning information list module can be denoted as Warn_List, the instrument parameter list module can be denoted as Meter_List, and the image list module can be denoted as Card_image_List.

[0046] In some exemplary embodiments, when the business module responds to the vehicle-side business, it also includes processing vehicle power status data, vehicle driving mode data and vehicle language mode data, and / or processing vehicle speed, vehicle fuel data and vehicle output power data, and / or processing vehicle time and vehicle internal and external temperature data, and / or processing vehicle indicator light data, and / or processing vehicle key messages, and / or processing vehicle driving data, and / or processing vehicle alarm data, and / or processing vehicle driving assistance system data, and / or processing vehicle setting data.

[0047] In some exemplary embodiments, the data interaction system further includes a rendering engine for forming a data source framework layer, an application framework layer, and / or a data interaction layer. The rendering engine is independent of the data source framework layer, the application framework layer, and the data interaction layer. As one example, the rendering engine may be a Kanzi engine or Kanzi Engine. As another example, the rendering engine may be a QT engine. QT is a cross-platform graphical user interface application development framework that can be used to build high-performance desktop, mobile, and web applications. It can also be used to develop non-GUI programs, such as console tools and servers.

[0048] In a specific example, take the data interaction system of the vehicle instrument HMI platform as an example. Figure 2As shown, the data interaction system includes a business module layer, a data source framework layer (Data Source), an application framework layer (Application), a data interaction layer, and a rendering engine (Kanzi Engine). Specifically, the business module layer and the data source framework layer (Data Source) communicate via interface calls, the data source framework layer (Data Source) and the application framework layer (Application) communicate via interface calls, and the application framework layer (Application) and the data interaction layer communicate via inter-process communication. The business module layer includes externally developed business modules such as the vehicle dashboard human-computer interaction system module Cluster HMI, the vehicle lighting control system TTLamp, and the background processing module Background. These modules can be later called via the application program interface, enabling reuse of these modules. The application framework layer (Application) includes a persistent publish / subscribe handler (PPS Handeler) and a data management center (Data Manager). The application framework layer (Application) includes PPS nodes corresponding to the lighting control list module Lamp_List, the warning information list module Warn_List, the instrument parameter list module Meter_List, and the image list module Card_image_List, referred to as the PPS Nodes module. The data interaction layer includes the in-vehicle infotainment interaction system module IVI Interaction, the state management module State Manager, the vehicle service bus module Vehicle Service, and the dynamic graphics rendering service module Animation Service. The application framework layer (Application) implements data interaction with the vehicle's central control system through PPS nodes and the in-vehicle infotainment interaction system module IVIInteraction in the data interaction layer; the application framework layer (Application) implements system status data interaction through PPS nodes and the state management module State Manager in the data interaction layer; the application framework layer (Application) implements data interaction with the MCU through PPS nodes and the vehicle service bus module Vehicle Service in the data interaction layer; and the application framework layer (Application) implements data interaction with the startup animation through PPS nodes and the dynamic graphics rendering service module Animation Service in the data interaction layer.

[0049] like Figure 2 As shown, the business module layer, data source framework layer, application framework layer, data interaction layer, and Kanzi Engine rendering engine can communicate data through application programming interfaces (APIs). For example, API-1 can be an API specifically provided for Kanzi Data Source, primarily used for communication with the Kanzi HMI. For example, API-1 can process uplink data according to screen requirements, update uplink data to the Kanzi HMI data node, and transmit downlink data to the corresponding PPS node. Kanzi Data Source is the data source framework layer based on the Kanzi engine, and Kanzi HMI is the human-computer interface based on the Kanzi engine. API-2 can be an API specifically provided for Kanzi Application, primarily used for data read and write preprocessing. For example, API-2 can obtain uplink data transmitted by the PPS node and transmit downlink data to the corresponding PPS node. API-3 can be an API used for internal data distribution among the business module layer, data source framework layer, application framework layer, data interaction layer, and Kanzi Engine rendering engine, primarily used for internal data distribution. For example, API-3 can obtain the uplink data transmitted by the PPS node, and can also serve as an extensible architecture to allow developers to add, subtract and adjust the logic processing submodules according to project requirements. As some examples, the uplink data obtained by the application interface API-1, application interface API-2 and application interface API-3 can be the same uplink data or different uplink data; the downlink data written by the application interface API-1 and application interface API-2 can be the same downlink data or different downlink data. Figure 2 As shown, the application interface API-1, the application interface API-2 and the application interface API-3 can be located in the same core of the SoC (System On Chip, SoC for short), for example, the application interface API-1, the application interface API-2 and the application interface API-3 are all located in the A core of the SoC.

[0050] like Figure 2As shown, the transmission and processing of uplink data includes: when the MCU, instrument system, or vehicle central control updates its status, uplink data is sent to the IVI Interaction node; based on the data source, the data is stored in the corresponding data structure; the Area Handler module in the Data Manager processes the data and updates it to the Kanzi HMI data node so that the data is reflected on the human-machine interaction screen. The Area Handler module can derive from the Area Handler Base class to provide the HMI with data processing capabilities based on various functions. Downlink data transmission includes: when the application framework layer's application status changes, such as changes in the application lifecycle or heartbeat, messages can be sent to the corresponding PPS node via the PPS Handler.

[0051] According to the above description, in some examples, if the data source framework layer Data Source is responsible for external interaction processing for the HMI, it can serve as an API that provides an interface for the vehicle instrument HMI, allowing data provided by the vehicle instrument via a plug-in to be updated to the human-machine interface in real time. For example, the data source framework layer Data Source can update upstream data to the Kanzi HMI via XML (Extensible Markup Language) data nodes. Whether the vehicle instrument HMI uses a Kanzi HMI generated by the Kanzi engine or a QT HMI generated by the QT engine, the data source framework layer Data Source can achieve compatibility. Data source compatibility can refer to interface normalization, meaning that when signals from different vehicle models are inconsistent, the HMI interface can be unified, allowing the HMI to remain unchanged even if the underlying signals change. Furthermore, unified adaptation through the data source framework layer Data Source is not only suitable for HMI normalization, but also for data adaptation in the Data Source for multiple vehicle models. Furthermore, if the project platform changes and the upper-layer (which can be the business module layer) HMI technology selection changes (here, the selection is mainly between the Kanzi engine and the QT engine), the data source framework layer and the lower layers can remain unchanged, thus maintaining compatibility across multiple projects through a single code base. Furthermore, the data source framework layer definition can include attribute definitions, action definitions, and trigger definitions.

[0052] As mentioned above, in some examples, Kanzi Engine can be designed as a separate module within the underlying data interaction system architecture, acting as a vehicle instrument rendering engine. This allows for decoupling. If other projects utilize QT or other engines, they can simply be added as separate modules alongside the QT engine, enhancing portability and compatibility within the data interaction system.

[0053] According to the above records, in some examples, the data of most application scenarios can be provided in the form of data nodes, which can isolate the source and method of data provision, achieve decoupling and isolation, and also achieve good compatibility and platformization. At the same time, since most vehicle instrument business scenario data are very common (such as vehicle speed, seat belt, warning light information, etc.), different platforms may provide different communication methods. For example, some platforms provide CAN (Controller Area Network, Controller Area Network, abbreviated as CAN) communication method, and some platforms provide SOME / IP (Scalable service-oriented Middleware over Internet Protocol, Scalable service-oriented communication middleware protocol based on Internet Protocol). However, here the main thing is that the PPS Nodes module is compatible with business scenarios, so there is no need to change the data interaction system, and direct reuse and project transplantation can be performed. For example, the PPS Nodes module compatible business scenarios can adapt to signal and vehicle model differences through the Data Source layer.

[0054] According to the above description, in a specific practical application scenario, for example, when a vehicle door is not properly closed, the vehicle service bus module (Vehicle Service) first receives the signal data indicating the door is not properly closed, then transmits it to the PPS Node module and, via Data Notify, to the HMIPPS File Ope. The HMIPPS File Ope is used to enable communication between the Kanzi Application and other processes. The HMIPPS File Ope transmits the data to the Area Handler module via PPS information, which then passes the data to the Kanzi HMI for display via the Data Proxy API. The Data Proxy API provides an external interface for invoking a Data Source. Furthermore, to automatically update the signal data arriving at the Vehicle Service bus module to the Kanzi HMI, a Data Source can be established through the HMI. For example, the Data Proxy API is initialized, and the Data Source is registered and registered. Once the registration is complete, callbacks can be sent to the registered object when the data changes.

[0055] In summary, the present application provides a data interaction system that can be architecturally designed according to the data source framework layer, application framework layer, and data interaction layer. The interactive design can be performed in a modular, platform-based, and intelligent manner, thereby improving the flexibility and maintainability of the data interaction system and optimizing the user experience. At the same time, for different user interface designs and user experience designs, external pre-developed business modules can be directly reused for adaptation, without the need to develop business modules separately, thereby shortening the system development cycle, reducing the difficulty of system maintenance, improving the compatibility and flexibility of the data interaction system, and making the application scenarios of the data interaction system more extensive, so as to meet market demand to the greatest extent in a short period of time. In addition, for different hardware and software environments, since the interaction interface of the human-computer interaction interface provided by the software vendor is consistent, there is no need to adjust the interaction interface when architecturally designing the data interaction system. The human-computer interaction interface can be directly reused, shortening the system development cycle, reducing system development costs and maintenance difficulties. For example, for an in-vehicle human-computer interaction interface system, the flexibility, scalability, and user experience of the in-vehicle system can be improved through a platform-based architecture to meet the future development needs of the automotive industry.

[0056] In another exemplary embodiment of the present application, Figure 3 A flow chart of a data interaction method is shown. Specifically, Figure 3 As shown, this embodiment provides a data interaction method, including the following steps:

[0057] S310, updates the first uplink data to the data node of the human-computer interaction interface according to the preset interaction requirements, transmits the first downlink data to the preset communication node, and communicates with the pre-developed business module through the first application interface to call the business module; wherein the business module is used to respond to the vehicle-side business.

[0058] S320, acquiring second uplink data according to a response result of the service module, and transmitting the second downlink data to a preset communication node;

[0059] S330, performing data interaction with vehicle-side services through a preset communication node;

[0060] The first uplink data and the second uplink data are data transmitted to the human-computer interaction interface at different times, and the first downlink data and the second downlink data are data transmitted to the vehicle domain controller at different times.

[0061] In some exemplary embodiments, the process of performing data interaction for vehicle-side services through preset communication nodes includes: performing data interaction for vehicle-side services with the vehicle-mounted central control through preset communication nodes; and / or performing data interaction for vehicle-side services with the service status through preset communication nodes; and / or performing data interaction for vehicle-side services with the microcontroller through preset communication nodes; and / or performing data interaction for vehicle-side services with the boot animation through preset communication nodes.

[0062] In some exemplary embodiments, when the business module responds to the vehicle-side business, the data interaction method also includes processing vehicle power status data, vehicle driving mode data and vehicle language mode data, and / or processing vehicle speed, vehicle fuel data and vehicle output power data, and / or processing vehicle time and vehicle internal and external temperature data, and / or processing vehicle indicator light data, and / or processing vehicle key messages, and / or processing vehicle driving data, and / or processing vehicle alarm data, and / or processing vehicle driving assistance system data, and / or processing vehicle setting data.

[0063] It can be understood that the data interaction method provided in the above embodiment and the data interaction system provided in the above embodiment belong to the same concept, wherein the specific manner in which the data interaction system performs operations has been described in detail in the above embodiment and will not be repeated here. In actual applications, the data interaction system provided in the above embodiment can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the data interaction system into different functional modules, and then implement all or part of the functions of the corresponding functional modules through the data interaction method described in the above embodiment. For example, all or part of the functions of the data source framework layer 110 can be implemented or executed through the relevant step process of step S310, all or part of the functions of the application framework layer 120 can be implemented or executed through the relevant step process of step S320, and all or part of the functions of the data interaction layer 130 can be implemented or executed through the relevant step process of step S330. The specific implementation or execution process can be referred to the above embodiment and will not be described in detail here.

[0064] Therefore, the present application provides a data interaction method. By designing the data interaction system according to the data source framework layer, the application framework layer, and the data interaction layer, the interaction design can be carried out in a modular, platform-based, and intelligent manner, thereby improving the flexibility and maintainability of the data interaction system and optimizing the user experience. At the same time, for different user interface designs and user experience designs, external pre-developed business modules can be directly reused for adaptation, without the need to develop business modules separately, thereby shortening the system development cycle, reducing the difficulty of system maintenance, improving the compatibility and flexibility of the data interaction system, and making the application scenarios of the data interaction system more extensive, so as to meet market demand to the greatest extent in a short period of time. In addition, for different hardware and software environments, since the interaction interface of the human-computer interaction interface provided by the software vendor is consistent, there is no need to adjust the interaction interface when designing the architecture of the data interaction system. The human-computer interaction interface can be directly reused, shortening the system development cycle, reducing system development costs and maintenance difficulties. For example, for an in-vehicle human-computer interaction interface system, the flexibility, scalability, and user experience of the in-vehicle system can be improved through a platform-based architecture to meet the development needs of the future automotive industry.

[0065] In another exemplary embodiment of the present application, a computer device is further provided. The computer device may include a memory, a processor, and a computer program stored in the memory. The processor executes the computer program so that the computer device performs Figure 3 The steps of the data interaction method. Figure 4 FIG1 shows a schematic diagram of the structure of a computer device 1000. Figure 4As shown, the computer device 1000 includes: a processor 1010 , a memory 1020 , a power supply 1030 , a display unit 1040 , and an input unit 1060 .

[0066] The processor 1010 is the control center of the computer device 1000. It connects various components using various interfaces and lines, and performs various functions of the computer device 1000 by running or executing computer programs / instructions stored in the memory 1020, thereby monitoring the computer device 1000 as a whole. In the embodiment of the present application, when the processor 1010 calls the computer program stored in the memory 1020, it executes the following Figure 3 The steps of the data interaction method are as follows. Optionally, the processor 1010 may include one or more processing units; preferably, the processor 1010 may integrate an application processor and a modem processor, wherein the application processor primarily processes the operating system, user interface, and applications, and the modem processor primarily processes wireless communications. In some embodiments, the processor and memory may be implemented on a single chip; in some embodiments, they may also be implemented on separate chips.

[0067] The memory 1020 may primarily include a program storage area and a data storage area. The program storage area may store an operating system, various applications, and the like; the data storage area may store instruction data and the like generated based on the use of the computer device 1000. Furthermore, the memory 1020 may include a high-speed random access memory and a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0068] The computer device 1000 also includes a power supply 1030 (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 1010 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0069] The display unit 1040 can be used to display information input by the user or information provided to the user, as well as various menus of the computer device 1000. In the embodiment of the present application, it is mainly used to display the display interface of each application in the computer device 1000 and objects such as text and pictures displayed on the display interface. The display unit 1040 may include a display panel 1050. The display panel 1050 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.

[0070] The input unit 1060 can be used to receive information such as numbers or characters input by the user. The input unit 1060 may include a touch panel 1070 and other input devices 1080. The touch panel 1070, also known as a touch screen, can receive user touch operations on or near it (for example, operations performed by the user using a finger, a stylus, or any other suitable object or accessory on or near the touch panel 1070).

[0071] Specifically, the touch panel 1070 can detect user touch operations and the signals generated by the touch operations, convert these signals into touch point coordinates, and send them to the processor 1010. It can also receive and execute commands sent by the processor 1010. In addition, the touch panel 1070 can be implemented using various types, such as resistive, capacitive, infrared, and surface acoustic wave. Other input devices 1080 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, a joystick, and the like.

[0072] Of course, the touch panel 1070 can cover the display panel 1050. When the touch panel 1070 detects a touch operation on or near it, it transmits it to the processor 1010 to determine the type of touch event. Then the processor 1010 provides corresponding visual output on the display panel 1050 according to the type of touch event. Figure 4 In the embodiment, the touch panel 1070 and the display panel 1050 are two independent components to realize the input and output functions of the computer device 1000, but in some embodiments, the touch panel 1070 and the display panel 1050 can be integrated to realize the input and output functions of the computer device 1000.

[0073] The computer device 1000 may further include one or more sensors, such as a pressure sensor, a gravity acceleration sensor, a proximity light sensor, etc. Of course, according to the needs of specific applications, the computer device 1000 may also include other components such as a camera.

[0074] In another exemplary embodiment of the present application, a computer-readable storage medium is further provided, wherein the storage medium stores a computer program / instruction, and when the computer program / instruction is executed by a processor, the above-mentioned device can execute the above-mentioned method in the present application. Figure 3 The steps of the data interaction method.

[0075] It will be understood by those skilled in the art that Figure 4This is merely an example of a computer device and does not constitute a limitation of the device. The device may include more or fewer components than shown, or a combination of certain components, or different components. For ease of description, the above sections are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.

[0076] It will be understood by those skilled in the art that the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be applied to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the functions in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including the instruction device, which implements the function specified in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0077] It is understood that the above embodiments, when collecting, storing, using, processing, transmitting, providing, disclosing, deleting, and other processing of relevant data (such as uplink data, downlink data, etc.), are completed with or with the consent of the user. For example, the uplink data and downlink data are authorized with the knowledge and consent of the user; or the user actively provides them after reading the relevant instructions, or the user actively authorizes / provides / uploads them when using some or all of the functions described in the above embodiments, or they are obtained through other means / channels with or with the consent of the user.

[0078] It is understood that, although the terms "first," "second," etc. may be used in embodiments of the present application to describe contextual data, these terms are merely used to distinguish contextual data from one another. For example, without departing from the scope of embodiments of the present application, the first contextual data may also be referred to as the second contextual data, and similarly, the second contextual data may also be referred to as the first contextual data.

[0079] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Anyone skilled in the art may modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by one of ordinary skill in the art without departing from the spirit and technical concepts disclosed in this application shall be covered by the claims of this application.

Claims

1. A data interaction system, characterized in that: The system includes: A data source framework layer, configured to update the first uplink data to a data node of the human-computer interaction interface according to preset interaction requirements, transmit the first downlink data to a preset communication node, and communicate with a pre-developed business module via a first application programming interface to invoke the business module; wherein the business module is configured to respond to vehicle-side services; An application framework layer, communicating with the data source framework layer through a second application program interface, for acquiring second uplink data according to a response result of the business module, and transmitting the second downlink data to a preset communication node; A data interaction layer, associated with the application framework layer, for performing data interaction with the vehicle-side business through a preset communication node; The first uplink data and the second uplink data are data transmitted to the human-computer interaction interface at different times, and the first downlink data and the second downlink data are data transmitted to the vehicle domain controller at different times.

2. The data interaction system according to claim 1, characterized in that: The data interaction layer includes an in-vehicle infotainment interaction system module, a state management module, a vehicle service bus module, and a dynamic graphics rendering service module; Among them, after the in-vehicle infotainment interaction system module is associated with the application framework layer, the vehicle-side business performs data interaction with the in-vehicle central control through the preset communication node; After the state management module is associated with the application framework layer, the vehicle-side service performs data exchange on the service state through a preset communication node; After the vehicle service bus module is associated with the application framework layer, the vehicle-side service performs microcontroller data interaction through a preset communication node; After the dynamic graphics rendering service module is associated with the application framework layer, data interaction of the startup animation is performed on the vehicle-side service through a preset communication node.

3. The data interaction system according to claim 2, characterized in that: The application framework layer includes a lighting control list module, a warning information list module, an instrument parameter list module and an image list module; The in-vehicle infotainment interaction system module is associated with the lighting control list module, and performs data interaction with the in-vehicle central control for the vehicle-side service through a preset communication node; The status management module is associated with the warning information list module, and performs data exchange of the service status of the vehicle-side service through a preset communication node; The vehicle service bus module is associated with the instrument parameter list and performs data interaction with the microcontroller for the vehicle-side service through a preset communication node; The dynamic graphics rendering service module is associated with the image list module, and performs data interaction of the startup animation for the vehicle-side service through a preset communication node.

4. The data interaction system according to any one of claims 1 to 3, characterized in that: When the business module responds to the vehicle-side business, it also includes processing vehicle power status data, vehicle driving mode data and vehicle language mode data, and / or processing vehicle speed, vehicle fuel data and vehicle output power data, and / or processing vehicle time and vehicle internal and external temperature data, and / or processing vehicle indicator light data, and / or processing vehicle key messages, and / or processing vehicle driving data, and / or processing vehicle alarm data, and / or processing vehicle driving assistance system data, and / or processing vehicle setting data.

5. The data interaction system according to any one of claims 1 to 3, characterized in that: The system further includes a rendering engine for forming the data source framework layer, the application framework layer and / or the data interaction layer. The rendering engine is independent of the data source framework layer, the application framework layer and the data interaction layer.

6. A data interaction method, characterized in that: The method comprises the following steps: updating the first uplink data to a data node of the human-computer interaction interface according to preset interaction requirements, transmitting the first downlink data to a preset communication node, and communicating with a pre-developed business module through a first application program interface to call the business module; wherein the business module is used to respond to the vehicle-side business; Acquire second uplink data according to a response result of the service module, and transmit the second downlink data to a preset communication node; Performing data interaction on the vehicle-side business through a preset communication node; The first uplink data and the second uplink data are data transmitted to the human-computer interaction interface at different times, and the first downlink data and the second downlink data are data transmitted to the vehicle domain controller at different times.

7. The data interaction method according to claim 6, characterized in that: The process of performing data interaction for the vehicle-side business through a preset communication node includes: performing data interaction for the vehicle-side business with the on-board central control through a preset communication node; and / or performing data interaction for the vehicle-side business with the business status through a preset communication node; and / or performing data interaction for the vehicle-side business with the microcontroller through a preset communication node; and / or performing data interaction for the vehicle-side business with the boot animation through a preset communication node.

8. The data interaction method according to claim 6 or 7, characterized in that: When the service module responds to the vehicle-side service, the method also includes processing vehicle power status data, vehicle driving mode data and vehicle language mode data, and / or processing vehicle speed, vehicle fuel data and vehicle output power data, and / or processing vehicle time and vehicle internal and external temperature data, and / or processing vehicle indicator light data, and / or processing vehicle key messages, and / or processing vehicle driving data, and / or processing vehicle alarm data, and / or processing vehicle driving assistance system data, and / or processing vehicle setting data.

9. A computer device, characterized in that: The invention comprises a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the data interaction method according to any one of claims 6 to 8.

10. A computer-readable storage medium, characterized in that A computer program is stored thereon, and when the computer program is executed by a processor, the steps of the data interaction method described in any one of claims 6 to 8 are implemented.

Images