Vehicle cabin operating system data interaction method, device, equipment and medium

Abstract

The invention discloses a data interaction method, device, equipment and medium for a vehicle cabin operating system, an abstract interface layer is additionally arranged between an application layer and a hardware layer of the vehicle cabin operating system, the data interaction method is applied to the abstract interface layer, and the data interaction method comprises the following steps: receiving interaction data sent by an application program; the interaction data is used for indicating target hardware equipment of the vehicle cabin to realize a target function; analyzing the interaction data, and determining a target abstract interface corresponding to the interaction data from at least one abstract interface predefined in an abstract interface layer; and sending the interaction data to a bottom layer function of the target hardware equipment through the target abstract interface, so that the bottom layer function realizes a target function of the target hardware equipment based on the interaction data. Thus, the abstract interface layer is created to package the bottom function of the hardware equipment, so that the application program can access different hardware equipment of the vehicle cabin operating system through the abstract interface layer, complex adaptation work does not need to be faced, and the development cost is reduced.

Description

Technical Field

[0001] The present application belongs to the field of vehicles, and specifically relates to a vehicle cockpit operating system data interaction method, device, equipment and medium. Background Art

[0002] The smart cockpit can integrate a variety of IT (Information Technology) and artificial intelligence technologies to create a new integrated digital platform in the car, provide drivers with an intelligent experience, and promote driving safety. For example, in the vehicle cockpit operating system, applications can analyze the in-car images collected by the camera to realize functions such as emotion recognition, age detection, object detection, and seat belt detection.

[0003] Among them, the application needs to communicate directly with the underlying hardware components of the vehicle's cockpit operating system to obtain data such as Bluetooth, audio, network, GPS (Global Positioning System) information and vehicle basic information.

[0004] However, this data interaction method has problems of complexity and inconsistency. The underlying hardware components of the vehicle cockpit operating system of different models may use different communication protocols and data formats, resulting in complex adaptation work for the application during development and maintenance. This not only increases development costs, but may also affect the stability of the vehicle cockpit operating system and user experience. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a vehicle cockpit operating system data interaction method, device, electronic device and storage medium, which can solve the problem that current applications need to face complex adaptation work during development and maintenance, which not only increases development costs but also may affect the stability of the vehicle cockpit operating system and user experience.

[0006] In a first aspect, an embodiment of the present application provides a vehicle cockpit operating system data interaction method, wherein an abstract interface layer is added between the application layer and the hardware layer of the vehicle cockpit operating system, and the data interaction method is applied to the abstract interface layer, including:

[0007] Receiving interaction data sent by the application; the interaction data is used to instruct a target hardware device in the vehicle cockpit to implement a target function;

[0008] Parsing the interaction data, and determining a target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer;

[0009] The interactive data is sent to the underlying function of the target hardware device through the target abstract interface, so that the underlying function implements the target function of the target hardware device based on the interactive data.

[0010] Optionally, sending the interaction data to an underlying function of the target hardware device through the target abstract interface includes:

[0011] Sending the interaction data to a hardware device adapter corresponding to the target abstract interface;

[0012] The interactive data is mapped to the underlying function of the target hardware device through the hardware device adapter.

[0013] Optionally, the receiving the interaction data sent by the application includes:

[0014] Receive interactive data sent by the application through the application interface.

[0015] Optionally, the abstract interface includes at least one abstract method, and the parsing of the interaction data, after determining a target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer, further includes:

[0016] Determine, from the abstract methods included in the target abstract interface, a target abstract method corresponding to the interaction data;

[0017] The step of sending the interactive data to the underlying function of the corresponding target hardware device through the target abstract interface includes:

[0018] The interaction data is sent to the underlying function of the target hardware device corresponding to the target abstract method.

[0019] Optionally, after sending the interaction data to the underlying function of the corresponding target hardware device through the target abstract interface, the method further includes:

[0020] Receive status information returned by the target hardware device; the status information is used to indicate the implementation status of the target function by the target hardware device;

[0021] The status information is returned to the application.

[0022] Optionally, the abstract interface includes at least one of the following:

[0023] Vehicle basic information interface, audio data interface, Bluetooth data interface, vehicle button information interface, battery life information interface, network information interface, vehicle screen data interface, telephone data interface and driving rules information interface.

[0024] In a second aspect, an embodiment of the present application provides a vehicle cockpit operating system data interaction device, wherein an abstract interface layer is added between the application layer and the hardware layer of the vehicle cockpit operating system, and the data interaction device is applied to the abstract interface layer, including:

[0025] A receiving module, used to receive interaction data sent by the application; the interaction data is used to instruct the target hardware device in the vehicle cockpit to implement the target function;

[0026] A parsing module, used for parsing the interaction data, and determining a target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer;

[0027] The processing module is used to send the interaction data to the underlying function of the target hardware device through the target abstract interface, so that the underlying function realizes the target function of the target hardware device based on the interaction data.

[0028] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0029] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the second aspect are implemented.

[0030] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the second aspect.

[0031] In a sixth aspect, an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the method described in the second aspect.

[0032] In the solution provided in the embodiment of the present application, an abstract interface layer is added between the application layer and the hardware layer of the vehicle cockpit operating system, and the interaction data sent by the application is received through the abstract interface layer; the interaction data is used to instruct the target hardware device in the vehicle cockpit to implement the target function; the interaction data is parsed, and the target abstract interface corresponding to the interaction data is determined from at least one abstract interface pre-defined in the abstract interface layer; the interaction data is sent to the underlying function of the target hardware device through the target abstract interface, so that the underlying function implements the target function of the target hardware device based on the interaction data.

[0033] In this way, by creating an abstract interface layer to encapsulate the underlying functions of the hardware devices, the application can access the different hardware devices of the vehicle cockpit operating system through the abstract interface layer. There is no need to pay attention to the different communication protocols and data formats that the hardware components may adopt, thereby shielding the differences between the various vehicle cockpit operating systems and eliminating the need to face complex adaptation work. The data interaction method between the application and the hardware devices is unified, reducing development costs and improving the stability of the vehicle cockpit operating system and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a flow chart showing a vehicle cockpit operating system data interaction method according to an exemplary embodiment;

[0035] Figure 2 is a schematic diagram of a system architecture of a vehicle cockpit operating system data interaction method according to an exemplary embodiment;

[0036] Figure 3 is a block diagram of a vehicle cockpit operating system data interaction device according to an exemplary embodiment;

[0037] Figure 4 is a block diagram of an electronic device according to an exemplary embodiment;

[0038] Figure 5 The figure is a schematic diagram of a hardware structure of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0040] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0041] The data interaction method provided in the embodiment of the present application is described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0042] Figure 1 The present invention is a flow chart of a vehicle cockpit operating system data interaction method according to an exemplary embodiment. An abstract interface layer is added between the application layer and the hardware layer of the vehicle cockpit operating system. The data interaction method is applied to the abstract interface layer, and includes the following steps:

[0043] Step S11: receiving interaction data sent by the application; the interaction data is used to instruct the target hardware device in the vehicle cockpit to implement the target function.

[0044] In a vehicle cockpit operating system, applications usually need to communicate directly with the hardware components of the vehicle cockpit operating system to obtain data such as Bluetooth, audio, network, GPS (Global Positioning System) information and basic vehicle information.

[0045] However, this data interaction method has problems of complexity and inconsistency. The underlying hardware components of the vehicle cockpit operating system of different models may use different communication protocols and data formats, resulting in complex adaptation work for the application during development and maintenance. This not only increases development costs, but may also affect the stability of the vehicle cockpit operating system and user experience.

[0046] Based on this, the present application provides a data interaction method, which realizes seamless and unified interaction between applications and hardware devices by creating an abstract interface layer between the application layer and the hardware layer of the vehicle cockpit operating system, thereby simplifying the development process of the vehicle cockpit operating system application and the compatibility issues between different vehicle platforms.

[0047] In this step, first, the abstract interface layer needs to receive the interaction data sent by the application, wherein the interaction data is used to instruct the target hardware device in the vehicle cockpit to implement the target function.

[0048] The creation of the abstract interface layer requires collecting the underlying hardware device information first, understanding the hardware device's communication protocol, data format, functional characteristics, etc. in detail, identifying what data the hardware device can provide, and how this data is organized and transmitted. At the same time, it is also necessary to analyze the application requirements, clarify what data the application needs to obtain from the hardware device, and the application's requirements for the real-time, accuracy, format, etc. of the data.

[0049] Then, based on the information of the hardware device and the requirements of the application, the structure and function of the abstract interface are designed to ensure that the design of the abstract interface can both encapsulate the details of the hardware device and meet the requirements of the application. This includes defining multiple abstract interfaces included in the abstract interface layer, as well as the methods, parameters, return values, etc. in each abstract interface to ensure that they match the interaction methods of the hardware device and the application.

[0050] In one implementation, receiving interaction data sent by an application includes:

[0051] Receive interactive data sent by the application through the application interface.

[0052] That is to say, the system architecture of the vehicle cockpit operating system also includes an application interface, where the application interface is between the abstract interface layer and the application layer and can provide higher-level functions and services for the application. The application interface can further encapsulate and organize the methods and properties of the abstract interface layer according to specific application requirements, providing a more friendly and easy-to-use interface for the upper-layer application.

[0053] Step S12: Parse the interaction data, and determine the target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer.

[0054] In this application, an abstract interface layer is created to encapsulate the underlying details of the vehicle cockpit operating system hardware devices. The core idea of ​​the abstract interface layer design is to encapsulate the underlying functions of the hardware devices, thereby simplifying the interaction between applications and various hardware devices and providing a unified and standardized abstract interface for upper-level applications.

[0055] In this way, no matter how the specific implementation of the hardware device changes, the application does not need to care about these details and only needs to interact through the abstract interface layer.

[0056] The abstract interface layer includes multiple abstract interfaces, each of which defines a set of behavior specifications related to a certain hardware device or function. For example, the abstract interface includes at least one of the following:

[0057] Vehicle basic information interface, audio data interface, Bluetooth data interface, vehicle button information interface, battery life information interface, network information interface, vehicle screen data interface, telephone data interface and driving rules information interface.

[0058] Specifically, the vehicle computer basic information interface is an interface for abstracting the acquisition of vehicle computer basic information, wherein the interactive data corresponding to the vehicle computer basic information interface includes basic information such as VIN code (Vehicle Identification Number), equipment code, vehicle speed, gear position, etc.;

[0059] The audio data interface is an interface for abstracting audio data. The interactive data corresponding to the audio data interface includes information such as audio focus and volume.

[0060] The Bluetooth data interface is an interface for abstracting Bluetooth data. The interactive data corresponding to the Bluetooth data interface includes information such as device name, device address, and Bluetooth connection switch.

[0061] The car key information interface is an interface for abstracting car key information. The interactive data corresponding to the car key information interface includes information such as long press and short press of various hard keys in the car.

[0062] The endurance information interface is an interface for abstracting endurance information. The interactive data corresponding to the endurance information interface includes information such as fuel level, power level, and endurance mileage.

[0063] The network information interface is an interface for abstracting network connection status information. The interactive data corresponding to the network information interface includes mobile network and wireless network status information, etc.

[0064] The vehicle screen data interface is an interface for abstracting vehicle screen data. The interactive data corresponding to the vehicle screen data interface includes information such as screen brightness and screen switch status.

[0065] The phone data interface is an interface for abstracting phone data. The interactive data corresponding to the phone data interface includes dialing, answering, rejecting, viewing call records, and obtaining the latest call records in a Bluetooth phone.

[0066] The driving rule information interface is an interface for abstracting driving rule information. The interactive data corresponding to the driving rule information interface includes the acquisition of driving safety disclaimer information, the acquisition of driving rules, and status change notifications.

[0067] In one implementation, the abstract interface includes at least one abstract method, and after parsing the interaction data and determining the target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer, the method further includes:

[0068] The target abstract method corresponding to the interaction data is determined from the abstract methods included in the target abstract interface; then, in subsequent steps, the abstract interface layer can send the interaction data to the underlying function of the target hardware device corresponding to the target abstract method.

[0069] That is, each abstract interface includes one or more abstract methods, which represent operations or behaviors related to a certain function or a hardware device, and each abstract method may involve interaction with one or more hardware devices.

[0070] For example, for an audio data interface, there may be abstract methods such as adjusting volume, playing, and pausing, and each method may need to interact with multiple audio output devices; for a Bluetooth data interface, there may be abstract methods such as connecting and disconnecting, and each method may need to interact with multiple Bluetooth devices; and so on.

[0071] Step S13: sending the interaction data to the underlying function of the target hardware device through the target abstract interface, so that the underlying function implements the target function of the target hardware device based on the interaction data.

[0072] After determining the corresponding target abstract interface, the interaction data can be sent to the underlying function of the target hardware device through the target abstract interface, and then the underlying function can implement the target function of the target hardware device based on the interaction data. In this way, when developing applications, developers do not need to have an in-depth understanding of the specific operation methods of various hardware devices, but only need to develop according to the abstract interface provided by the abstract interface layer, which greatly simplifies the development process and improves development efficiency.

[0073] In one implementation, the interactive data is sent to the corresponding underlying function of the target hardware device through the target abstract interface, including:

[0074] Send the interaction data to the hardware device adapter corresponding to the target abstract interface;

[0075] Through the hardware device adapter, the interactive data is mapped to the underlying functions of the target hardware device.

[0076] That is to say, an adapter can be implemented for each hardware device between the abstract interface layer and the hardware layer to connect it to the abstract interface layer. Each hardware device has a corresponding adapter, and the role of the adapter is to map the abstract methods and properties of the abstract interface layer to the operations of the specific hardware device. Through the adapter, different hardware devices can interact with the abstract interface layer in a consistent way, thereby achieving the compatibility and interchangeability of hardware devices.

[0077] In this way, through the design of abstract interfaces and adapters, the coupling between applications and hardware devices is reduced. This means that if the hardware device changes, as long as the adapter can correctly map the abstract methods of the abstract interface layer to the new hardware device, the application and the abstract interface layer do not need to be modified, so that the hardware device can be easily replaced or upgraded, greatly improving the flexibility and scalability of the system.

[0078] In addition, in the present application, when designing the abstract interface layer, some redundant design space can be reserved so that when new hardware devices or functions need to be supported in the future, it is only necessary to add new interface definitions to the abstract interface layer and implement corresponding adapters for these new devices. The abstract interface or abstract method can be easily expanded without affecting existing devices.

[0079] In one implementation, after sending the interactive data to the underlying function of the corresponding target hardware device through the target abstract interface, it also includes:

[0080] Receive status information returned by the target hardware device; the status information is used to indicate the implementation status of the target function by the target hardware device;

[0081] Returns status information to the application.

[0082] That is to say, after executing the operation, the underlying function will generate corresponding status information based on the result of the operation or the status of the target hardware device. The status information may include confirmation of successful operation, error code, device status update, etc.

[0083] Then, if the underlying function needs to return status information to the upper layer, it will send the status information back to the abstract interface layer. As the middle layer, the abstract interface layer is responsible for receiving the status information returned by the underlying function, performing necessary processing or encapsulation, and then returning it to the application.

[0084] Figure 2 This is a schematic diagram of a system architecture of a data interaction method according to an exemplary embodiment. It includes:

[0085] Hardware devices: including Bluetooth modules, audio devices, network devices, etc., each of which has different functions, interfaces and communication protocols.

[0086] Device adapter: For each hardware device, there is a corresponding device adapter that converts the specific functions and interfaces of the hardware device into a form that the abstract interface layer can understand and call.

[0087] Abstract interface layer: defines a series of abstract interfaces, each of which includes at least one abstract method, providing a simple, intuitive and reliable interface for upper-layer applications to interact with device adapters, so that applications do not need to worry about the specific implementation details of the hardware devices.

[0088] Application interface layer: further encapsulates and organizes the methods and properties of the abstract interface layer, providing higher-level functions and services for upper-level applications.

[0089] Application: The upper-layer application interacts with the abstract interface layer through the application interface layer. When the application needs to call the function of the hardware device, it sends a request to the application interface layer. The application interface layer converts these requests into a format that the abstract interface layer can understand and passes them to the hardware device through the device adapter.

[0090] For example, you can first define a set of abstract interfaces to encapsulate the low-level details of the sunroof device in the vehicle cockpit operating system. For example, you may define an abstract method for "opening the sunroof".

[0091] Furthermore, for each hardware device, an adapter is implemented to connect it to the abstract interface layer, for example, the sunroof device adapter implements the function of opening the sunroof.

[0092] In addition, an application interface layer can be designed above the abstract interface layer to provide higher-level functions and services for applications. For example, a public service interface may be defined to encapsulate functions such as opening and closing the sunroof, and a simple application is provided to control these functions.

[0093] In this way, when the user clicks the "Open Sunroof" button in the application, the button will trigger the abstract method of "Open Sunroof" in the abstract interface layer, and then the abstract method of "Open Sunroof" will call the bottom layer of the sunroof device adapter to realize the function of opening the sunroof.

[0094] From the above, it can be seen that the technical solution provided by the embodiment of the present application, by creating an abstract interface layer to encapsulate the underlying functions of the hardware devices, enables the application to access the different hardware devices of the vehicle cockpit operating system through the abstract interface layer, without having to pay attention to the different communication protocols and data formats that may be adopted by the hardware components, thereby shielding the differences between the various vehicle cockpit operating systems and eliminating the need to face complex adaptation work. It unifies the data interaction methods between the application and the hardware devices, reduces development costs, and improves the stability of the vehicle cockpit operating system and user experience.

[0095] The vehicle cockpit operating system data interaction method provided in the embodiment of the present application can be executed by a vehicle cockpit operating system data interaction device. In the embodiment of the present application, a method for executing terminal access by a vehicle cockpit operating system data interaction device is taken as an example to illustrate the device of the vehicle cockpit operating system data interaction method provided in the embodiment of the present application.

[0096] Figure 3 The present invention is a block diagram of a vehicle cockpit operating system data interaction device according to an exemplary embodiment. An abstract interface layer is added between the application layer and the hardware layer of the vehicle cockpit operating system. The data interaction device is applied to the abstract interface layer, including:

[0097] The receiving module 201 is used to receive the interaction data sent by the application; the interaction data is used to instruct the target hardware device in the vehicle cockpit to achieve the target function;

[0098] A parsing module 202, configured to parse the interaction data and determine a target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer;

[0099] The processing module 203 is used to send the interaction data to the underlying function of the target hardware device through the target abstract interface, so that the underlying function realizes the target function of the target hardware device based on the interaction data.

[0100] From the above, it can be seen that the technical solution provided by the embodiment of the present application, by creating an abstract interface layer to encapsulate the underlying functions of the hardware devices, enables the application to access the different hardware devices of the vehicle cockpit operating system through the abstract interface layer, without having to pay attention to the different communication protocols and data formats that may be adopted by the hardware components, thereby shielding the differences between the various vehicle cockpit operating systems and eliminating the need to face complex adaptation work. It unifies the data interaction methods between the application and the hardware devices, reduces development costs, and improves the stability of the vehicle cockpit operating system and user experience.

[0101] The data interaction device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices other than a terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a car electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0102] The vehicle cockpit operating system data interaction device provided in the embodiment of the present application can achieve Figures 1 to 3 To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0103] Alternatively, if Figure 4 As shown, an embodiment of the present application also provides an electronic device 500, including a processor 501 and a memory 502, wherein the memory 502 stores programs or instructions that can be executed on the processor 501, and when the program or instructions are executed by the processor 501, the various steps of the above-mentioned data interaction method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, they are not repeated here.

[0104] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0105] Figure 5 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of the present application.

[0106] The electronic device 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010 and other components.

[0107] Those skilled in the art will appreciate that the electronic device 1000 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1010 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 5 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0108] From the above, it can be seen that the technical solution provided by the embodiment of the present application, by creating an abstract interface layer to encapsulate the underlying functions of the hardware devices, enables the application to access the different hardware devices of the vehicle cockpit operating system through the abstract interface layer, without having to pay attention to the different communication protocols and data formats that may be adopted by the hardware components, thereby shielding the differences between the various vehicle cockpit operating systems and eliminating the need to face complex adaptation work. It unifies the data interaction methods between the application and the hardware devices, reduces development costs, and improves the stability of the vehicle cockpit operating system and user experience.

[0109] It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0110] The memory 1009 can be used to store software programs and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1009 may include a volatile memory or a non-volatile memory, or the memory 1009 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0111] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.

[0112] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data interaction method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0113] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0114] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data interaction method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0115] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0116] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned data interaction method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0117] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0118] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0119] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A vehicle cockpit operating system data interaction method, characterized in that: An abstract interface layer is added between the application layer and the hardware layer of the vehicle cockpit operating system, and the data interaction method is applied to the abstract interface layer, including: Receiving interaction data sent by the application; the interaction data is used to instruct a target hardware device in the vehicle cockpit to implement a target function; Parsing the interaction data, and determining a target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer; The interactive data is sent to the underlying function of the target hardware device through the target abstract interface, so that the underlying function implements the target function of the target hardware device based on the interactive data.

2. The vehicle cockpit operating system data interaction method according to claim 1, characterized in that: The step of sending the interactive data to the underlying function of the target hardware device through the target abstract interface includes: Sending the interaction data to a hardware device adapter corresponding to the target abstract interface; The interactive data is mapped to the underlying function of the target hardware device through the hardware device adapter.

3. The vehicle cockpit operating system data interaction method according to claim 1, characterized in that: The receiving of the interactive data sent by the application program includes: Receive interactive data sent by the application through the application interface.

4. The vehicle cockpit operating system data interaction method according to claim 1, characterized in that: The abstract interface includes at least one abstract method, and the parsing of the interaction data, after determining the target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer, further includes: Determine, from the abstract methods included in the target abstract interface, a target abstract method corresponding to the interaction data; The step of sending the interactive data to the underlying function of the corresponding target hardware device through the target abstract interface includes: The interaction data is sent to the underlying function of the target hardware device corresponding to the target abstract method.

5. The vehicle cockpit operating system data interaction method according to claim 1, characterized in that: After sending the interactive data to the underlying function of the corresponding target hardware device through the target abstract interface, the method further includes: Receive status information returned by the target hardware device; the status information is used to indicate the implementation status of the target function by the target hardware device; The status information is returned to the application.

6. The vehicle cockpit operating system data interaction method according to claim 1, characterized in that: The abstract interface includes at least one of the following: Vehicle basic information interface, audio data interface, Bluetooth data interface, vehicle button information interface, battery life information interface, network information interface, vehicle screen data interface, telephone data interface and driving rules information interface.

7. A vehicle cockpit operating system data interaction device, characterized in that: An abstract interface layer is added between the application layer and the hardware layer of the vehicle cockpit operating system, and the data interaction device is applied to the abstract interface layer, including: A receiving module, used to receive interaction data sent by the application; the interaction data is used to instruct the target hardware device in the vehicle cockpit to implement the target function; A parsing module, used for parsing the interaction data, and determining a target abstract interface corresponding to the interaction data from at least one abstract interface predefined in the abstract interface layer; The processing module is used to send the interaction data to the underlying function of the target hardware device through the target abstract interface, so that the underlying function realizes the target function of the target hardware device based on the interaction data.

8. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the vehicle cabin operating system data interaction method as described in any one of claims 1-6.

9. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the vehicle cabin operating system data interaction method as described in any one of claims 1-6 are implemented.

10. A computer program product, characterized in that The program product is stored in a storage medium, and the program product is executed by at least one processor to implement the steps of the vehicle cockpit operating system data interaction method as described in any one of claims 1 to 6.

Images