Display interaction method of cockpit instrument, cockpit instrument display system and vehicle

Abstract

The embodiment of the application provides a cockpit instrument display interaction method, a cockpit instrument display system and a vehicle. The method comprises the following steps: in the case that a communication driving microservice receives a to-be-processed signal, sending the to-be-processed signal to a business microservice corresponding to the communication driving microservice; obtaining target display data by processing the to-be-processed signal through the business microservice, and sending the target display data to a display microservice corresponding to the target display data; drawing the target display data through the display microservice to obtain a target layer, and pushing the target layer to a rendering microservice; performing synthesis processing based on the target layer through the rendering microservice to obtain a target rendering image frame, and pushing the target rendering image frame to a multimedia driving microservice; and displaying the target rendering image frame through the multimedia driving microservice. The method is used to improve the stability of the cockpit instrument display system.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of display interaction of vehicles, and in particular to a display interaction method of a cockpit instrument, a cockpit instrument display system and a vehicle. BACKGROUND

[0002] With the development of automobile intelligence, the functions of cockpit instruments are becoming more and more rich, and the data displayed by cockpit instruments will affect the decision of drivers. In order to ensure driving safety, stable operation of cockpit instruments is required.

[0003] In the related art, the data displayed by cockpit instruments is becoming more and more rich. If a certain data displayed on a cockpit instrument fails, the cockpit instrument as a whole may fail to display all data, resulting in poor stability of cockpit instrument operation. SUMMARY

[0004] The display interaction method of the cockpit instrument, the cockpit instrument display system and the vehicle provided by the embodiments of the present application are used to improve the stability of cockpit instrument display system operation.

[0005] In a first aspect, the embodiments of the present application provide a display interaction method of a cockpit instrument, applied to a cockpit instrument display system, the cockpit instrument display system comprising a plurality of microservices divided according to functions; the plurality of microservices comprising a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; the plurality of display microservices being configured to draw layers respectively corresponding to a plurality of data types; the display interaction method of the cockpit instrument comprising:

[0006] In a case where the communication driving microservice receives a to-be-processed signal, the communication driving microservice sends the to-be-processed signal to a business microservice corresponding to the communication driving microservice; the communication driving microservice corresponding to the business microservice processes the to-be-processed signal to obtain target display data, determines a target data type of the target display data, and sends the target display data to a display microservice corresponding to the target data type; the display microservice corresponding to the target data type draws the target display data to obtain a target layer, and pushes the target layer to the rendering microservice; the rendering microservice obtains other layers from other display microservices, composites the target layer and the other layers according to display priorities of the target layer and the other layers to obtain a target rendering image frame, and pushes the target rendering image frame to the multimedia driving microservice; and the multimedia driving microservice displays the target rendering image frame.

[0007] In a second aspect, the embodiments of the present application provide a cockpit instrument display system, comprising: a plurality of microservices divided according to functions; the plurality of microservices comprising a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; the plurality of display microservices being configured to draw layers respectively corresponding to a plurality of data types;

[0008] The communication driving microservice is configured to receive a to-be-processed signal and send the to-be-processed signal to a business microservice corresponding to the communication driving microservice; the business microservice is configured to process the to-be-processed signal to obtain target display data, determine a target data type of the target display data, and send the target display data to a display microservice corresponding to the target data type; the display microservice is configured to draw the target data type to obtain a target layer and push the target layer to a rendering microservice; the rendering microservice is configured to obtain other layers from other display microservices, perform synthesis processing on the target layer and the other layers according to display priorities of the target layer and the other layers, obtain a target rendering image frame, and push the target rendering image frame to a multimedia driving microservice; and the multimedia driving microservice is configured to display the target rendering image frame.

[0009] In a third aspect, an embodiment of the present application provides a vehicle, comprising: a cockpit instrument display system.

[0010] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores computer execution instructions. When the computer execution instructions are executed by a processor, the computer execution instructions are configured to implement the display interaction method of the cockpit instrument.

[0011] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising a computer program. When the computer program is executed by a processor, the computer program implements the display interaction method of the cockpit instrument.

[0012] The embodiment of the application provides a cockpit instrument display interaction method, a cockpit instrument display system and a vehicle, the cockpit instrument display interaction method is applied to the cockpit instrument display system, the cockpit instrument display system comprises a plurality of microservices divided according to functions; the plurality of microservices comprises a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; wherein the communication driving microservice is used for receiving a to-be-processed signal, the business microservice processes the to-be-processed signal to obtain target display data, determines a target data type of the target display data, sends the target display data to a display microservice corresponding to the target data type, the display microservice draws the target display data to obtain a target layer, the rendering microservice performs synthesis processing based on the target layer to obtain a target rendering image frame, and the multimedia driving microservice is used for driving display; through the plurality of display microservices, layer drawing of different data types is respectively processed, and then the rendering microservice synthesizes the layers drawn by the plurality of display microservices, in the case that a certain display microservice is single-point failed, only the layer processed by the display microservice is affected, the layer drawing of other display microservices is not affected, the rendering microservice can still synthesize other normal layers, the partial availability of the cockpit instrument is ensured, and the stability of cockpit instrument display system operation is improved; in addition, each display microservice draws a layer corresponding to a data type, so that the plurality of display microservices can draw layers in parallel, the problem of low data processing efficiency caused by drawing and rendering of multiple layers through one microservice is avoided, the real-time performance of data display in the instrument is improved, and the data displayed by the cockpit instrument is synchronized with the vehicle state. BRIEF DESCRIPTION OF DRAWINGS

[0013] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0014] Figure 1 A flowchart of a cockpit instrument display interaction method provided by the application is shown in the figure;

[0015] Figure 2 A schematic diagram of an intelligent cockpit system provided by the application is shown in the figure;

[0016] Figure 3 A schematic diagram of interaction between microservices of a cockpit instrument display system provided by the application is shown in the figure;

[0017] Figure 4 A schematic diagram of a cockpit instrument display system provided by the application is shown in the figure Figure 1 .

[0018] Figure 5 A schematic diagram of a cockpit instrument display system provided by the application is shown in the figure Figure 2 .

[0019] The specific embodiments of the application have been shown and described in the above drawings and the following description. These drawings and description are not meant to limit the scope of the inventive concept in any way but are merely meant to illustrate the inventive concept to one of ordinary skill in the art by reference to particular embodiments. DETAILED DESCRIPTION

[0020] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The same numbers are used in different drawings to represent the same or similar elements. The following detailed description is not meant to limit the application in any way. Rather, the following description is meant to provide examplary embodiments of devices and methods consistent with the application as detailed in the appended claims.

[0021] The technical solutions of the application and how the technical solutions solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described again in some embodiments. The embodiments of the application will be described below with reference to the drawings.

[0022] The display interaction method of the cockpit instrument provided by the application is applied to a cockpit instrument display system. The cockpit instrument display system includes at least instrument display and head-up display. It can be understood that through the cockpit instrument display system, relevant data can be displayed on the instrument and on the head-up display device.

[0023] Figure 1 The flowchart of the display interaction method of the cockpit instrument provided by the application Figure 1 The display interaction method of the cockpit instrument is applied to a cockpit instrument display system. The cockpit instrument display system includes a plurality of microservices divided according to functions. The plurality of microservices includes a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice, and a multimedia driving microservice. The plurality of display microservices are used to draw layers corresponding to a plurality of data types respectively.

[0024] As shown in Figure 1 , the display interaction method of the cockpit instrument includes:

[0025] S101, in the case that the communication driving microservice receives a to-be-processed signal, the to-be-processed signal is sent to the business microservice corresponding to the communication driving microservice.

[0026] Specifically, as Figure 2As shown, the cockpit instrument display system is part of the intelligent cockpit system, which includes the cockpit instrument display system, a mobile terminal system, a virtualization system (or a hardware layer); the cockpit instrument display system is divided into an interactive display layer, a system middleware layer, and a driver layer according to functions; the interactive display layer is a HMI (Human-Machine Interaction Layer) layer; the HMI layer includes a rendering microservice and multiple display microservices, the system middleware layer includes multiple business microservices, and the driver layer includes a communication driver microservice and a multimedia driver microservice; if the SOC (System on Chip) of the vehicle is a virtualization system, the driver layer is adapted to the virtualization system; if the SOC of the vehicle is not a virtualization system, the driver layer directly adapts to the hardware layer; the mobile terminal system can be an Android system, and the cockpit instrument display system interacts with the mobile terminal through a cockpit agent service.

[0027] It should be noted that the cockpit instrument display system includes multiple microservices, which can be freely tailored and defined according to the functional requirements of different vehicle models, facilitating upgrading and expansion, and improving the richness and diversity of the cockpit instrument display system; decoupling each function of the cockpit instrument display system allows a microservice to handle one or part of the functions, and in the case of single-point failure of the microservice, only the function of the microservice will be affected, avoiding the problem that single-point failure causes the entire cockpit instrument display system to be unable to work, and improving the stability of the cockpit instrument display system.

[0028] Among them, the communication driver microservice includes driver microservices under different communication modes, such as network communication microservices and wired driver microservices; in actual application, more detailed microservice division can be made according to various communication modes supported by the cockpit instrument display system.

[0029] The business microservice includes business microservices under different communication modes, such as the communication driver microservice including network driver microservices and wired driver microservices, the network driver microservice corresponding to the network business microservice, and the wired driver microservice corresponding to the wired business microservice.

[0030] The business microservice can be used to analyze the to-be-processed signals sent by the communication driver microservice, as well as data management and distribution.

[0031] Specifically, each microservice included in the cockpit instrument display system can obtain data from other microservices by subscription or by sending a data request; for example, a business microservice subscribes to data in a communication driver microservice, and when the network driver microservice receives a to-be-processed signal, the to-be-processed signal is pushed to the business microservice that subscribes to the to-be-processed signal; for example, the communication driver microservice receives a to-be-processed signal, and when a data request for obtaining the to-be-processed signal is received from a business microservice, the to-be-processed signal is sent to the business microservice.

[0032] For example, the network driver microservice obtains a to-be-processed signal of a multimedia type, and the network driver microservice pushes the to-be-processed signal of the multimedia type to a network business microservice.

[0033] S102, obtaining target display data by processing the to-be-processed signal through a business microservice corresponding to the communication driver microservice, determining a target data type of the target display data, and sending the target display data to a display microservice corresponding to the target data type.

[0034] The display microservice is configured to process the target display data; in the cockpit instrument display system, the data displayed is divided by type, and each display microservice is configured to process data of one data type.

[0035] Specifically, the to-be-processed signal is decoded and data conversion processed through the business microservice to obtain data that can be displayed on an instrument screen or a head-up display device, i.e., target display data; the business microservice can determine a target data type of the target display data and send the target display data to a display microservice that subscribes to the target data type.

[0036] In some embodiments, the plurality of data types include a basic data type, a multimedia data type, a welcome-guest data type, a navigation data type, a prompt data type, and an auxiliary driving data type; and the plurality of display microservices include a basic display microservice corresponding to the basic data type, a multimedia display microservice corresponding to the multimedia data type, a welcome-guest display microservice corresponding to the welcome-guest data type, a navigation display microservice corresponding to the navigation data type, a prompt display microservice corresponding to the prompt data type, and an auxiliary driving display microservice corresponding to the auxiliary driving data type.

[0037] For example, the target data type of the target display data is a multimedia type, and the business microservice pushes the target display data to a multimedia display microservice that subscribes to data of the multimedia type; for another example, the target data type of the target display data is a running data type, and the target display data is pushed to a basic information display microservice that subscribes to data of the running data type.

[0038] The business microservice can also send target display data to the display microservice according to the data request when receiving the data request sent by the display microservice.

[0039] S103, drawing the target display data through the display microservice corresponding to the target data type to obtain a target layer and pushing the target layer to a rendering microservice.

[0040] The target layer is a layer corresponding to a data type to which the target display data belongs.

[0041] Specifically, the display microservice draws the target layer according to the target display data and pushes the target layer to the rendering microservice.

[0042] S104, obtaining other layers from other display microservices through the rendering microservice, synthesizing the target layer and the other layers according to display priorities of the target layer and the other layers to obtain a target rendering image frame, and pushing the target rendering image frame to a multimedia driving microservice.

[0043] The display priority of the layer is a display requirement of the cockpit instrument display system and HMI planning. Specifically, the rendering microservice can receive the target layer sent by the display microservice and read the latest other layers from a layer buffer of the other display microservice. The rendering microservice obtains the display priorities of the target layer and the other layers, synthesizes the target layer and the other layers according to the display priorities of the target layer and the other layers to obtain the target rendering image frame. It should be noted that a layer with a higher display priority can be displayed on a layer with a lower display priority and can cover part of the information in the layer with the lower display priority.

[0044] Exemplarily, the display microservice is a welcome guest display microservice, the other microservices include a basic information microservice and a multimedia microservice, and the rendering microservice obtains a layer corresponding to the welcome guest display microservice, a layer corresponding to the basic information microservice, and a layer corresponding to the multimedia microservice. The display priority corresponding to the welcome guest display microservice is higher than the display priorities corresponding to the basic information microservice and the multimedia microservice. Therefore, in the target rendering image frame, the welcome guest animation is displayed on the upper layer and can block part of the basic information and multimedia data.

[0045] In the above embodiment, the display priorities of the layers are used to synthesize the layers, so that the target rendering image frame displayed meets the display requirement of the cockpit instrument display system. In the case of single-point failure of the display microservice, only the layer processed by the display microservice is affected, and the content of other layers is not affected, thereby avoiding the problem that the cockpit instrument display system cannot work normally as a whole due to single-point failure.

[0046] Specifically, the rendering microservice performs synthesis processing on the target layers sent by the plurality of display microservices to obtain a target rendering image frame; the target rendering image frame is an image frame finally displayed on the instrument screen or the head-up display device; and the rendering microservice pushes the target rendering image frame to the multimedia driving microservice.

[0047] It can be understood that the data displayed in the cockpit instrument display system is divided by type, each display microservice is used to process data of one data type to obtain a target layer of the data type, and the rendering microservice performs synthesis on a plurality of target layers to obtain an image frame finally displayed; in the case of single-point failure of the display microservice, only the layer processed by the display microservice is affected, and the content of other layers is not affected, thereby avoiding the problem that the cockpit instrument display system as a whole cannot work normally due to single-point failure; in addition, different types of data are processed and drawn according to different display microservices, so that multiple types of data can be processed in parallel, load balancing can be achieved, and the response of interactive display is improved.

[0048] S105, displaying the target rendering image frame through the multimedia driving microservice.

[0049] Specifically, the rendering microservice pushes the target rendering image to the multimedia driving microservice, and the multimedia driving microservice drives the display of the target rendering image frame.

[0050] In some embodiments, displaying the target rendering image frame through the multimedia driving microservice includes: displaying the target rendering image frame on the head-up display device through the multimedia driving microservice; or displaying the target rendering image frame on the instrument screen through the multimedia driving microservice.

[0051] Specifically, the target rendering image frame can be sent to the multimedia driving microservice through a display framework such as XDG / Weston of a Linux system, and the multimedia driving microservice drives the instrument screen to display the target rendering image frame; or the multimedia driving microservice can send the target rendering image frame to the head-up display device to display the target rendering image frame through the head-up display device; wherein the Linux system is an operating system, XDG (X Desktop Group) is a cross-desktop group, and Weston is a reference compositor.

[0052] In the embodiments of the present application, each microservice provides a unified IPC / RPC service interface to the outside, has functions such as service discovery, automatic connection, authentication registration, service management, and can adapt to communication modes such as shared memory, Socket, DDS, SOMEIP, etc.

[0053] The IPC / RPC service interface includes an IPC (Inter-Process Communication) service interface and an RPC (Remote Procedure Call) service interface; the Socket is a socket interface; the DDS (Data Distribution Service) is a data interaction mode of a publish / subscribe mode; and the SOMEIP (Scalable service-Oriented MiddlewarE over IP) is a service-oriented communication protocol for automotive electronics.

[0054] The unified IPC / RPC service interface is used for calling between the microservices, the interface description file does not need to be defined by the developer, and the calling code does not need to be generated, so as to avoid the problems of code bloat and management difficulty, reduce the development difficulty, and improve the development efficiency; in addition, among the multiple microservices, the microservices related to the platform, such as the microservices of the drive layer, can be adapted to the platform, and the microservices unrelated to the platform, such as the microservices of the HIM layer and the microservices of the system middleware layer, can be developed by using the C language, so as to improve the portability.

[0055] The cockpit instrument display interaction method provided in the application is applied to a cockpit instrument display system, the cockpit instrument display system includes multiple microservices divided according to functions; the multiple microservices include a rendering microservice, multiple display microservices, multiple business microservices, a communication driving microservice, and a multimedia driving microservice; in a development stage, the multiple microservices included in the cockpit instrument display system can be independently developed, so that the developer can focus on the development work of a certain microservice, the development difficulty is reduced, agile development and rapid iteration are realized, and the multiple microservices included in the cockpit instrument display system can be freely tailored and defined according to the functional requirements of different vehicle models, so as to facilitate upgrading and expansion; the communication driving microservice is used for receiving a to-be-processed signal, the business microservice processes the to-be-processed signal to obtain target display data, the display microservice draws the target display data to obtain a target layer, the rendering microservice performs synthesis processing based on the target layer to obtain a target rendering image frame, and the multimedia driving microservice is used for driving display; in the case of single-point failure of the display microservice, only the layer processed by the display microservice is affected, and the content of other layers is not affected, so that the stability of the cockpit display system is improved; in addition, each microservice processes a part of functions, so that some microservices can run in parallel, the microservices communicate with each other, load balancing can be realized, efficient communication can be realized in the cockpit instrument display system, and the response speed of the interactive display is improved.

[0056] Optionally, the display priorities of the target layer and the other layers can be configured in the rendering microservice, so that the rendering microservice can directly determine the display priorities of the target layer and the other layers.

[0057] Optionally, the plurality of business microservices include a layer management microservice; the display interaction method of the cockpit instrument further includes: sending a configuration request to the layer management microservice through the rendering microservice, and receiving layer configuration data returned by the layer management microservice; and determining the display priorities of the target layer and the other layers according to the layer configuration data through the rendering microservice.

[0058] The layer management microservice is configured to configure display parameters (such as display priorities) of each layer according to display requirements of the cockpit instrument display system and HMI planning, and generate a configuration file; and the layer configuration data includes the display priorities of the target layer and the other layers.

[0059] Specifically, the rendering microservice generates a configuration request according to the layer identifiers of the target layer and the other layers, sends the configuration request to the layer management service, the layer management service acquires the layer identifiers according to the configuration request, reads the display priorities corresponding to the layer identifiers from the configuration file according to the layer identifiers, generates layer configuration data according to the display priorities corresponding to the layer identifiers, and sends the layer configuration data to the rendering microservice, the rendering microservice acquires the display priorities of the target layer and the other layers from the configuration data, performs synthesis processing on the target layer and the other layers according to the display priorities, and obtains a target rendering image frame.

[0060] In the above embodiment, the display priorities of the layers are managed by the layer management microservice, the management of the display priorities is decoupled from the layer synthesis processing, and the maintainability and scalability are improved.

[0061] In some embodiments, the communication driving microservice includes a CAN driving microservice, a network driving microservice, and an interface driving microservice; the business microservice includes a CAN communication microservice, a network communication microservice, and an interface communication microservice; in the case that the communication driving microservice receives a to-be-processed signal, the to-be-processed signal is sent to the business microservice subscribed to the communication driving microservice, including: in the case that the CAN driving microservice acquires a to-be-processed signal on the CAN bus, the to-be-processed signal is pushed to the CAN communication microservice subscribed to the CAN driving microservice; in the case that the network driving microservice acquires a to-be-processed signal transmitted by the network, the to-be-processed signal is pushed to the network communication microservice subscribed to the network driving microservice; and in the case that the interface driving microservice acquires a to-be-processed signal transmitted by the hardware interface, the to-be-processed signal is pushed to the interface communication microservice subscribed to the interface driving microservice.

[0062] The interface driving microservice includes an SPI driving microservice, an I2C driving microservice and a GPIO driving microservice; and the business microservice includes an SPI communication microservice, an I2C communication microservice and a GPIO communication microservice.

[0063] The network driving microservice is used for realizing data interaction through a network, the CAN driving microservice is used for realizing data interaction through a CAN bus, the SPI driving microservice is used for realizing data interaction through an SPI (Serial Peripheral Interface), the I2C driving microservice is used for realizing data interaction through an I2C (Inter-Integrated Circuit) serial communication bus, and the GPIO driving microservice is used for realizing data interaction through a GPIO (General Purpose Input / Output).

[0064] Specifically, the CAN communication microservice subscribes to the CAN driving microservice, and the CAN driving microservice pushes the to-be-processed signal to the CAN driving microservice in the case that the CAN driving microservice receives the to-be-processed signal; similarly, the network communication microservice subscribes to the network driving microservice, the SPI communication microservice subscribes to the SPI driving microservice, the I2C communication microservice subscribes to the I2C driving microservice, and the GPIO communication microservice subscribes to the GPIO driving microservice, and details are not described herein.

[0065] In the above embodiment, different driving microservices are used to receive data interacted through different communication modes of the cockpit instrument display system, and different communication microservices are used to process the data interacted through different communication modes, so that the maintainability and scalability are improved, load balancing is realized, the cockpit instrument display system can efficiently communicate internally, the response speed of interactive display is improved, and in the case that a communication mode fails, the data transmission of other communication modes is not affected, thereby avoiding the problem that the cockpit instrument display system as a whole cannot work normally due to single-point failure.

[0066] In some embodiments, the display interaction method of the cockpit instrument further includes: for each microservice, receiving a function identifier and a service address broadcast by other microservices when the microservice is started; determining a target function identifier and a target service address from the received function identifier and service address according to the requirement information of the microservice; establishing a communication connection between the target microservice corresponding to the target service address; subscribing to data corresponding to the target function identifier in the target microservice; or, sending a data request to the target microservice according to the target function identifier, so that the target microservice returns data corresponding to the target function identifier.

[0067] The function identifier of the microservice, i.e., a function ID, can represent a function that the microservice can provide, and the microservice can have one or more function IDs; the service address of the microservice is used to connect with other microservices; the service address can be a path, a unique identifier, an IP address, a port, or the like.

[0068] Specifically, the microservice has a broadcast function, and when the microservice is started, the function ID and the service address of the microservice are broadcasted, and then the microservice can also obtain the function ID and the service address of other microservices through broadcasting; the microservice matches the requirement information of the microservice with the received function ID, takes the function ID that is matched successfully as a target function ID, takes the microservice that sends the target function ID as a target microservice, and the service address of the target microservice is a target service address.

[0069] In actual applications, the requirement information can include a requirement identifier or a requirement name, and when the received function identifier is the same as the requirement identifier or the received function identifier has a mapping relationship with the requirement name, the function identifier is a target function identifier that is matched successfully; it should be noted that the present application embodiment defines the function identifiers corresponding to the functions supported by each microservice and the requirement information corresponding to the functions required by each microservice, and establishes a matching relationship between the function identifiers and the requirement information.

[0070] The microservice establishes a communication connection between the microservice and the target microservice corresponding to the target service address.

[0071] When the function corresponding to the target function ID belongs to a notification type, the microservice subscribes to data corresponding to the target function identifier in the target microservice, so that when the target microservice generates data corresponding to the target function ID, the target microservice automatically pushes the data to the microservice that subscribes to the data corresponding to the target function ID; optionally, when the microservice does not need the data corresponding to the target function ID, the microservice can cancel the subscription to the target microservice.

[0072] When the function corresponding to the target function ID belongs to a request type, the microservice can send a data request to the target microservice according to the target function ID, and the target microservice returns data corresponding to the function ID according to the data request, to realize the calling of the target microservice by the microservice; optionally, if the microservice no longer needs the data corresponding to the target function ID, the microservice can disconnect the communication connection with the target microservice.

[0073] In the above embodiment, the microservices establish a communication connection by broadcasting their own function identifiers and service addresses, and after the communication connection is established, the microservices obtain the data required by their own businesses through the function identifiers, and realize subscription or microservice calling through the function identifiers, without complex codes or the generation of complex calling functions, so that the interaction between the microservices is simpler, and the stability of the communication between the microservices is improved.

[0074] In some embodiments, the plurality of microservices further comprises a communication connection microservice; the display interaction method of the cockpit instrument further comprises: for each microservice, when the microservice starts, sending a connection request to the communication connection microservice, the connection request comprising a function identifier, a service address and requirement information of the microservice; receiving a target function identifier and a target service address returned by the communication connection microservice, which match the requirement information; establishing a communication connection between target microservices corresponding to the target service address according to the target service address; subscribing to data corresponding to the target function identifier in the target microservice, or sending a data request to the target microservice according to the target function identifier, so that the target microservice returns data corresponding to the target function identifier.

[0075] The communication connection microservice is configured to uniformly manage the function identifiers and the service addresses of the microservices.

[0076] Specifically, all microservices can communicate with the communication connection microservice; after the microservice starts, the function identifier, the service address and the requirement information of the microservice are sent to the communication connection microservice; the communication connection microservice matches the function identifiers, the service addresses and the requirement information sent by the plurality of microservices, and returns a target function identifier and a target service address matching the requirement information of each microservice to the microservice.

[0077] The specific process of establishing a communication connection between target microservices corresponding to the target service address, subscribing to data corresponding to the target function identifier in the target microservice, and sending a data request to the target microservice according to the target service address can be referred to the description in the above embodiments, and will not be repeated here.

[0078] In the above embodiments, the communication connection microservice can be used to perform matching of the function identifiers and the requirement information, to manage the communication connection between the plurality of microservices, reduce the amount of data communicated between the microservices, and reduce resource consumption; the function identifier is used to realize subscription or microservice calling, without complex code or generation of complex calling functions, so that the interaction between the microservices is simpler, and the stability and response efficiency of communication between the microservices are improved.

[0079] In some embodiments, after the communication connection between the target microservices corresponding to the target service address is established, the method further comprises: maintaining a heartbeat connection between the microservice and the target microservice; in the case of an abnormal heartbeat connection, disconnecting the communication connection between the microservice and the target microservice; periodically sending a connection request to the target microservice through the microservice according to the target service address.

[0080] Specifically, after establishing the communication connection between the microservice corresponding to the target service address, the microservice initiates authentication to the target microservice, receives the authentication result returned by the target microservice, and maintains the heartbeat connection between the microservice and the target microservice after the authentication passes. In the case of abnormal heartbeat connection (such as heartbeat response exceeding the preset heartbeat time, heartbeat packet loss, etc.), the communication connection is automatically disconnected, and if the microservice subscribes to the data corresponding to the target function identifier in the target microservice, the subscription is automatically cancelled. After the communication connection is disconnected, the microservice periodically initiates a connection request to the target microservice.

[0081] Exemplarily, as shown in Figure 3 microservice 1 broadcasts its function ID and service address; microservice 2 receives the function ID and service address broadcasted by each microservice, microservice 2 determines that the function ID broadcasted by microservice 1 matches the business requirement of microservice 2, and microservice 2 establishes a communication connection with microservice 1 according to the service address of microservice 1; microservice 2 initiates an authentication message to microservice 1, receives the authentication result returned by microservice 1, and maintains the heartbeat connection between microservice 1 and microservice 2 after the authentication passes.

[0082] When the function corresponding to the function ID belongs to the notification type, microservice 2 sends a subscription message to microservice 1 to subscribe to the data corresponding to the function ID in microservice 1, so that microservice 1 automatically pushes data to microservice 2 when the data corresponding to the function ID is generated in microservice 1; when microservice 2 does not need the data corresponding to the function ID, it can send a cancel subscription message to microservice 1.

[0083] When the function corresponding to the function ID belongs to the request type, microservice 2 can send a data request to microservice 1 according to the function ID, and microservice 1 returns the data corresponding to the function ID according to the data request; if microservice 2 no longer needs the data corresponding to the function ID, it can disconnect the communication connection with microservice 1.

[0084] In the case of abnormal heartbeat connection between microservice 1 and microservice 2, the communication connection is automatically disconnected, and if microservice 2 subscribes to the data of microservice 1, the subscription is automatically cancelled; after the communication connection is disconnected, microservice 2 can periodically initiate a connection request to microservice 1.

[0085] In the above embodiment, the heartbeat connection is maintained between the microservices, and in the case of abnormal heartbeat connection, a connection request is periodically initiated to attempt to re-establish the communication connection, which can establish the communication connection in the first time to eliminate the abnormality, and can improve the stability of the operation of the cockpit instrument display system.

[0086] The embodiment of the application provides a cockpit instrument display interaction method, a cockpit instrument display system and a vehicle. The cockpit instrument display interaction method is applied to the cockpit instrument display system, and the cockpit instrument display system comprises a plurality of microservices divided according to functions; the plurality of microservices comprises a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; wherein the communication driving microservice is used for receiving a to-be-processed signal, the business microservice processes the to-be-processed signal to obtain target display data, the target data type of the target display data is determined, the target display data is sent to the display microservice corresponding to the target data type, the display microservice draws the target display data to obtain a target layer, the rendering microservice performs synthesis processing based on the target layer to obtain a target rendering image frame, and the multimedia driving microservice is used for driving display; through the plurality of display microservices, layers of different data types are respectively processed for drawing, and then the rendering microservice synthesizes the layers drawn by the plurality of display microservices, in the case of single-point failure of a certain display microservice, only the layer processed by the display microservice is affected, the layer drawing of other display microservices is not affected, the rendering microservice can still synthesize other normal layers, the partial availability of the cockpit instrument is ensured, and the stability of cockpit instrument display system operation is improved; in addition, each display microservice draws a layer corresponding to a data type, so that the plurality of display microservices can draw layers in parallel, the problem of low data processing efficiency caused by drawing and rendering of multiple layers through one microservice is avoided, the real-time performance of data display in the instrument is improved, and the data displayed by the cockpit instrument is synchronized with the vehicle state.

[0087] It should be understood that, although each step in the flowchart involved in the above embodiments is displayed in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in the above embodiments can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence of these steps or stages is not necessarily sequential, but can be executed in rotation or alternation with at least part of other steps or steps or stages in other steps.

[0088] The cockpit instrument display system provided in the application refers to Figure 4 , comprising:

[0089] a plurality of microservices divided according to functions; the plurality of microservices comprises a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; the plurality of display microservices are used for drawing layers respectively corresponding to a plurality of data types;

[0090] The communication driving microservice is configured to receive a to-be-processed signal, and send the to-be-processed signal to a business microservice corresponding to the communication driving microservice.

[0091] The business microservice is configured to process the to-be-processed signal to obtain target display data, determine a target data type of the target display data, and send the target display data to a display microservice corresponding to the target data type.

[0092] The display microservice is configured to draw the target data type to obtain a target layer, and push the target layer to a rendering microservice.

[0093] The rendering microservice is configured to obtain other layers from other display microservices, perform synthesis processing on the target layer and the other layers according to display priorities of the target layer and the other layers to obtain a target rendering image frame, and push the target rendering image frame to a multimedia driving microservice.

[0094] The multimedia driving microservice is configured to display the target rendering image frame.

[0095] In a specific example, referring to Figure 5 , the cockpit instrument display system is divided into an interactive display layer (HMI layer), a system middleware layer, and a driving layer according to functions.

[0096] The HMI layer includes a rendering microservice, a welcome and send-off display microservice, a basic information display microservice, an alarm arbitration display microservice, a multimedia display microservice, a navigation display microservice, and an auxiliary driving display microservice.

[0097] The system middleware layer includes a layer management microservice, an audio processing microservice, a power management microservice, a system upgrade microservice, a system monitoring microservice, a network communication microservice, a CAN communication microservice, an SPI communication microservice, an I2C communication microservice, and a GPIO communication microservice.

[0098] The driving layer includes a display driving microservice, an audio driving microservice, a network driving microservice, a CAN driving microservice, an SPI driving microservice, an I2C driving microservice, and a GPIO driving microservice.

[0099] The microservices in the HMI layer can call each other, the microservices in the system middleware layer can call each other, and the HMI layer, the system middleware layer, and the driving layer can also call each other through microservices.

[0100] The cockpit instrument display system provided by the embodiment of the present application comprises a plurality of microservices divided according to functions; the plurality of microservices comprises a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; wherein the communication driving microservice is configured to receive a to-be-processed signal, the business microservice is configured to process the to-be-processed signal to obtain target display data, determine a target data type of the target display data, and send the target display data to a display microservice corresponding to the target data type; the display microservice is configured to draw the target display data to obtain a target layer; the rendering microservice is configured to perform synthesis processing based on the target layer to obtain a target rendering image frame; and the multimedia driving microservice is configured to drive display. Through the plurality of display microservices, layers of different data types are respectively processed for drawing, and then the rendering microservice performs synthesis on the layers drawn by the plurality of display microservices, so that in the case of single-point failure of a certain display microservice, only the layer processed by the display microservice is affected, the drawing of the layers of other display microservices is not affected, the rendering microservice can still synthesize other normal layers, the availability of the cockpit instrument part is ensured, and the stability of the cockpit instrument display system is improved. In addition, each display microservice draws a layer corresponding to a data type, so that the plurality of display microservices can draw layers in parallel, avoiding the problem of low data processing efficiency caused by drawing and rendering of multiple layers by one microservice, improving the real-time performance of data display in the instrument, and synchronizing the data displayed by the cockpit instrument with the vehicle state.

[0101] The present application also provides a vehicle comprising the cockpit instrument display system in the above embodiment.

[0102] The present application also provides a computer program product comprising a computer program which, when executed by a processor, implements the above method.

[0103] The present application also provides a computer-readable storage medium having computer-executable instructions stored therein, which, when executed by a processor, implement the above method.

[0104] The above readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium accessible by a general-purpose or special-purpose computer.

[0105] An example readable storage medium is coupled to the processor such that the processor can read information from the readable storage medium and can write information to the readable storage medium. Of course, the readable storage medium can also be a part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0106] The division of units is only a logical functional division, and in actual implementation, there can be another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0107] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0108] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0109] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the part of the present application that essentially contributes to the prior art or the part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the embodiments of the present application. The foregoing storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0110] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The foregoing program can be stored in a computer readable storage medium. The program executes to perform the steps of the above-mentioned method embodiments; and the foregoing storage medium includes various media capable of storing program codes, such as ROM, RAM, magnetic disk, or optical disk.

[0111] Finally, it should be noted that other embodiments of the present application will readily occur to those skilled in the art upon consideration of the specification and practice of the present application disclosed herein. The present application is intended to include all such variations as fall within the general scope of the application, and includes the generic principles disclosed and the best mode known to the inventors to be currently practiced as well as variations thereof, without departing from the scope of the present application as defined by the claims. The specification and examples give the best application of the present application as known to at least one of the inventors at the time of the filing of this application. It is to be understood that since numerous modifications and changes will readily occur to those skilled in the art, the application is not to be limited to the exact construction and operation as illustrated and described. Accordingly, all such variations are intended to be included within the scope of the present application as defined in the claims. The application is to be limited only by the claims.

Claims

1. A display interaction method of a cockpit instrument, characterized by, The application is applied to a cockpit instrument display system, and the cockpit instrument display system comprises a plurality of microservices divided according to functions; The plurality of microservices comprises a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; The plurality of display microservices are used for drawing layers corresponding to a plurality of data types respectively; The method comprises: In the case that the communication driving microservice receives a to-be-processed signal, the to-be-processed signal is sent to the business microservice corresponding to the communication driving microservice; The target display data is obtained by processing the to-be-processed signal through the business microservice corresponding to the communication driving microservice, the target data type of the target display data is determined, and the target display data is sent to the display microservice corresponding to the target data type; The target layer is obtained by drawing the target display data through the display microservice corresponding to the target data type, and the target layer is pushed to the rendering microservice; The target rendering image frame is obtained by synthesizing the target layer and other layers according to the display priorities of the target layer and the other layers through the rendering microservice, and the target rendering image frame is pushed to the multimedia driving microservice; The target rendering image frame is displayed through the multimedia driving microservice.

2. The method of claim 1, wherein, The plurality of data types comprise a basic data type, a multimedia data type, a welcoming and sending guest data type, a navigation data type, a prompt data type and an auxiliary driving data type; The plurality of display microservices comprise a basic display microservice corresponding to the basic data type, a multimedia display microservice corresponding to the multimedia data type, a welcoming and sending guest display microservice corresponding to the welcoming and sending guest data type, a navigation display microservice corresponding to the navigation data type, a prompt display microservice corresponding to the prompt data type and an auxiliary driving display microservice corresponding to the auxiliary driving data type.

3. The method of claim 1, wherein, The plurality of business microservices comprise a layer management microservice; The method further comprises: The configuration request is sent to the layer management microservice through the rendering microservice, and the layer configuration data returned by the layer management microservice is received; The display priorities of the target layer and the other layers are determined according to the layer configuration data through the rendering microservice.

4. The method of claim 1, wherein, The communication driving microservice comprises a CAN driving microservice, a network driving microservice and an interface driving microservice; The business microservice comprises a CAN communication microservice, a network communication microservice and an interface communication microservice; The method further comprises: In the case that the CAN driving microservice acquires the to-be-processed signal on the CAN bus, the to-be-processed signal is pushed to the CAN communication microservice; In the case that the network driving microservice acquires the to-be-processed signal transmitted by the network, the to-be-processed signal is pushed to the network communication microservice; In a case where the interface driving microservice acquires a to-be-processed signal transmitted by a hardware interface, the to-be-processed signal is pushed to the interface communication microservice.

5. The method of claim 1, wherein, The method further comprises: For each microservice, upon startup of the microservice, receiving a function identifier and a service address broadcast by other microservices; According to the requirement information of the microservice, determining a target function identifier and a target service address from the received function identifiers and service addresses; Establishing a communication connection between the target microservice corresponding to the target service address; Subscribing to data corresponding to the target function identifier in the target microservice, or sending a data request to the target microservice according to the target function identifier, so that the target microservice returns data corresponding to the target function identifier.

6. The method of claim 1, wherein, The plurality of microservices further comprises a communication connection microservice; the method further comprises: For each microservice, upon startup of the microservice, sending a connection request to the communication connection microservice; the connection request comprises a function identifier, a service address and requirement information of the microservice; Receiving a target function identifier and a target service address returned by the communication connection microservice, which match the requirement information; Establishing a communication connection between the target microservice corresponding to the target service address; Subscribing to data corresponding to the target function identifier in the target microservice, or sending a data request to the target microservice according to the target function identifier, so that the target microservice returns data corresponding to the target function identifier.

7. The method according to claim 5 or 6, characterized in that, After the communication connection between the target microservice corresponding to the target service address is established, the method further comprises: The microservice and the target microservice maintain a heartbeat connection; In a case where the heartbeat connection is abnormal, the communication connection between the microservice and the target microservice is disconnected; According to the target service address, the microservice periodically sends a connection request to the target microservice.

8. The method according to any one of claims 1 to 6, characterized in that, The target rendering image frame is displayed by the multimedia driving microservice, comprising: The target rendering image frame is displayed on a heads-up display device by the multimedia driving microservice; or, The target rendering image frame is displayed on an instrument screen by the multimedia driving microservice.

9. A cockpit instrument display system characterized by, Comprise: A plurality of microservices divided according to functions; The plurality of microservices comprises a rendering microservice, a plurality of display microservices, a plurality of business microservices, a communication driving microservice and a multimedia driving microservice; The plurality of display microservices are configured to draw layers corresponding to a plurality of data types respectively; The communication driving microservice is configured to receive a to-be-processed signal and send the to-be-processed signal to a business microservice corresponding to the communication driving microservice; The business microservice is configured to process the to-be-processed signal to obtain target display data, determine a target data type of the target display data, and send the target display data to a display microservice corresponding to the target data type; The display microservice is configured to draw the target data type to obtain a target layer, and push the target layer to the rendering microservice; The rendering microservice is configured to obtain other layers from other display microservices, perform synthesis processing on the target layer and the other layers according to display priorities of the target layer and the other layers, obtain a target rendering image frame, and push the target rendering image frame to the multimedia driving microservice. The multimedia driving microservice is configured to display the target rendering image frame.

10. A vehicle characterized by comprising: The cockpit instrument display system comprises: The cockpit instrument display system of claim 9.

11. A computer readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are configured to implement the method of any one of claims 1 to 8 when executed by the processor.

12. A computer program product, characterised in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are configured to implement the method of any one of claims 1 to 8 when executed by the processor.

Images