Vehicle-mounted middleware and control method thereof, mobile terminal and control method thereof, and vehicle

Abstract

The application relates to the technical field of vehicles, in particular to a vehicle-mounted middleware and a control method thereof, a mobile terminal and a control method thereof, and a vehicle. The vehicle-mounted middleware comprises a function discovery module and a function atlas issuing module; the function discovery module and the function atlas issuing module are in communication connection; wherein the function discovery module is used for discovering vehicle functions controllable by a cabin domain controller; a global function atlas is constructed by using function descriptions of the vehicle functions; the function atlas issuing module is used for, in response to receiving a function notification instruction sent by a mobile terminal, constructing a function description data packet based on the global function atlas called from the function discovery module; and the function description data packet is issued to the mobile terminal, so that the mobile terminal controls the vehicle functions by using the function description data packet, the software and hardware are highly decoupled, and the reuse rate of vehicle function control is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more particularly to the field of vehicle control technology, specifically to vehicle middleware and its control methods, mobile terminals and their control methods, and vehicles. Background Technology

[0002] Currently, with the development of intelligent connected vehicles, the interconnection experience between mobile terminals and in-vehicle terminal brackets has become a key focus. Furthermore, as living standards improve, users' demand for control over in-vehicle terminals is also increasing.

[0003] However, in related technologies, users on mobile terminals can only perform simple operations on commonly used vehicle functions based on preset applications. Moreover, when the in-vehicle terminal undergoes function updates, the mobile terminal cannot update accordingly in a timely and effective manner, and can only rely on application updates to complete the control updates, resulting in poor control efficiency. Therefore, this application proposes a more effective in-vehicle middleware and its control method. Summary of the Invention

[0004] This invention provides an in-vehicle middleware and its control method, a mobile terminal and its control method, and a vehicle, to at least solve the technical problem of low reusability of cross-terminal functional control in related technologies. The technical solution adopted in this application is as follows: In a first aspect, this application provides an in-vehicle middleware, including: a function detection module and a function graph distribution module; the function detection module and the function graph distribution module are communicatively connected; wherein, the function detection module is used to detect the vehicle functions that the cockpit domain controller can control; construct a global function graph using the function descriptions of each vehicle function; the function graph distribution module is used to respond to receiving a function notification command sent by a mobile terminal, construct a function description data packet based on the global function graph retrieved from the function detection module; and distribute the function description data packet to the mobile terminal so that the mobile terminal can control the vehicle functions using the function description data packet.

[0005] Based on the aforementioned technical means, this application designs an in-vehicle middleware to abstract the capabilities of the cockpit domain controller into standardized services and constructs a global functional graph. This enables a high degree of decoupling between software and hardware, significantly improving the reusability and iteration efficiency of vehicle functions. At the same time, it also allows for more flexible invocation of atomic services on mobile terminals, effectively reducing development costs and achieving a closed loop for vehicle function control.

[0006] In one possible implementation, the function detection module includes: a first function detection unit and a global function graph generation unit; the first function detection unit and the global function graph generation unit are communicatively connected; the first function detection unit is used to: automatically scan the bus nodes of the vehicle bus connected to the cockpit domain controller, as well as the operating system service list and operating system call interface of the cockpit domain controller, after the cockpit domain controller is woken up, to detect vehicle functions; and upload the vehicle functions to the global function graph generation unit; the global function graph generation unit is used to construct a global function graph based on the function descriptions of the respective vehicle functions; wherein, the vehicle functions include vehicle hardware functions and software functions of the operating system software of the cockpit domain controller; the function description includes a unique function identifier, function name, UI control type corresponding to the function, value range corresponding to the function state value, underlying security constraints to be followed when selecting the state value from the value range, and the current state value of the function.

[0007] Based on the aforementioned technical means, after the cockpit domain controller is woken up, this application automatically scans the vehicle's bus nodes and operating system service list and calling interfaces, enabling plug-and-play functionality of the vehicle's software and hardware. Furthermore, in the event of vehicle-level hardware upgrades or platform replacements, it can quickly connect without significant code modifications, ensuring compatibility with different vehicle models and suppliers' underlying hardware nodes and vehicle bus protocols, thereby enhancing the flexibility of vehicle function control.

[0008] In one possible implementation, the function detection module further includes: a second function detection unit; the second function detection unit is communicatively connected to both the first function detection unit and the global function map generation unit; the second function detection unit is used to detect the target vehicle function in response to receiving an execution completion instruction sent by the first function detection unit; and to update the global function map based on the function description of the target vehicle function in response to detecting the target vehicle function; wherein the target vehicle function is a newly added vehicle function that can be controlled by the cockpit domain controller.

[0009] Based on the aforementioned technical means, after generating the global functional map, this application updates the global functional map based on the functional description when a new vehicle function is detected. It can automatically detect and access the new vehicle function without recompiling or reconstructing the underlying layer, thereby obtaining a more comprehensive global functional map corresponding to the vehicle function, improving the flexibility of control and the consistency of user experience.

[0010] In one possible implementation, the function detection module further includes: a third function detection unit; the third function detection unit is communicatively connected to the first function detection unit and the global function map generation unit respectively; the third function detection unit is used to detect changes in the current function status value of the vehicle function in response to receiving an execution completion instruction sent by the first function detection unit; and update the global function map based on the changes.

[0011] Based on the aforementioned technical means, this application updates the global function map by detecting changes in the current state value of vehicle functions, which can ensure that the latest operating state of vehicle functions is effectively obtained, avoid deviations in function control, and enhance the consistency and reliability of user experience.

[0012] In one possible implementation, the function notification instruction includes: a unique identifier for the mobile terminal; a function map distribution module, including: an authentication unit and a generation unit; the authentication unit and the generation unit are communicatively connected; the authentication unit is used to authenticate the mobile terminal based on the unique identifier; in response to successful authentication, it determines the range of functions that the mobile terminal is allowed to control; and sends the range of functions to the generation unit; wherein, authentication is used to verify whether the mobile terminal has the right to control the vehicle; the generation unit is used to construct a local function map based on the range of functions and the global function map; generate a function description data packet based on the local function map; and distribute the function description data packet to the mobile terminal so that the mobile terminal can use the function description data packet to control the vehicle functions.

[0013] Based on the aforementioned technical means, this application uses a unique terminal identifier to authenticate the mobile terminal, enabling the configuration of corresponding permission function maps for different mobile terminals according to their identities. This allows users with different identities to adjust different vehicle functions on the mobile terminal, improving the flexibility of function operation.

[0014] In one possible implementation, the vehicle middleware further includes: a function control instruction execution module; the function control instruction execution module is used to respond to receiving a function control instruction issued by a mobile terminal based on a function description data packet; parse the function control instruction to obtain a control message; determine whether the control message violates a preset conflict rule based on the control message and the vehicle's driving state; and in response to determining that the control message does not violate the preset conflict rule, forward the control message to the cockpit domain controller so that the cockpit domain controller executes the control message; wherein, the preset conflict rule is used to indicate conflicting vehicle driving states and vehicle functions.

[0015] Based on the aforementioned technical means, this application can intercept vehicle function control when it is determined that the control message violates the preset conflict rules, thereby avoiding safety risks during vehicle operation; and can execute vehicle function control corresponding to the control message when the control message does not violate the preset conflict rules, thereby meeting the user's personalized function execution needs under the premise of safe vehicle operation.

[0016] In one possible implementation, the function control instruction includes an instruction issuance timestamp, random anti-duplicate code, a unique identifier for the function of the vehicle to be controlled, and a target value for the function of the vehicle to be controlled. The function control instruction execution module is specifically used to: determine the target parsing plugin based on the vehicle type and the unique identifier for the function of the vehicle to be controlled; wherein, the target parsing plugin is one of a number of pre-set parsing plugins in the vehicle middleware; and use the target parsing plugin to parse the function control instruction to obtain the control message.

[0017] Based on the aforementioned technical means, this application, through a function identifier matching and parsing plugin for vehicle type and vehicle function, can achieve standardized and customized conversion of function control commands for mobile terminals, effectively shielding the differences in communication protocols imported by heterogeneous underlying hardware, and ensuring the accuracy and compatibility of control message generation.

[0018] In one possible implementation, the vehicle-mounted middleware further includes: a communication setup module; the communication setup module is configured to establish a Bluetooth communication connection between the mobile terminal and the vehicle-mounted middleware in response to determining that the spatial distance between the mobile terminal and the vehicle-mounted middleware is less than a preset spatial distance; in response to determining that the Bluetooth communication connection has been successfully established, send a local area network access certificate to the mobile terminal so that the mobile terminal establishes a local area network communication connection between the mobile terminal and the vehicle-mounted middleware based on the local area network access certificate; and control the mobile terminal to perform local area network communication with the vehicle-mounted middleware, and adjust the connection state of the Bluetooth communication connection from a normal connection state to a basic connection state; the basic connection state is used to maintain a basic heartbeat connection; and in response to determining that the network quality of the local area network connection is lower than the expected network quality, restore the connection state of the Bluetooth communication connection to the normal connection state, and control the mobile terminal to perform Bluetooth communication with the vehicle-mounted middleware.

[0019] Based on the above technical means, this application establishes a Bluetooth communication connection between the mobile terminal and the vehicle middleware when the spatial distance between the mobile terminal and the vehicle middleware is less than a preset spatial distance. Moreover, when the Bluetooth communication connection is established, a local area network communication connection is established between the mobile terminal and the vehicle middleware, thereby enabling faster and more efficient data transmission between the mobile terminal and the vehicle middleware. Furthermore, by using the Bluetooth communication connection as a redundant connection channel, effective data transmission can be guaranteed even when the network quality of the local area network channel is poor.

[0020] Secondly, this application provides a mobile terminal, including: an instruction issuing module and a rendering module; the instruction issuing module is communicatively connected to the vehicle middleware and the rendering module respectively; the instruction issuing module is used to send a function notification instruction to the vehicle middleware in response to monitoring a user triggering a first target UI control, so that the vehicle middleware issues a function description data packet; and to send the function description data packet to the rendering module; wherein, the function description data packet is determined based on a global function graph; the global function graph is constructed by the vehicle middleware detecting the vehicle functions that the cockpit domain controller can control and using the function descriptions of each vehicle function; the rendering module is used to render the UI control interface corresponding to the function description data packet in the target interface; the instruction issuing module is also used to generate a function control instruction in response to monitoring a touch operation on the UI control interface; and to send the function control instruction to the vehicle middleware, so that the vehicle middleware executes the control of the vehicle functions based on the function control instruction.

[0021] Based on the above technical means, when the application detects that the user intends to view or adjust vehicle functions, it receives the function description data packet of the vehicle middleware on the mobile terminal, and renders the function description data packet on the target interface. Then, the vehicle functions are controlled according to the rendered control interface. This eliminates the need to pre-set a large number of redundant interfaces, reduces the terminal storage and memory usage, and completely decouples the interface from the vehicle functions, realizing cross-terminal and cross-vehicle function control adaptation.

[0022] Thirdly, this application provides a control method for an in-vehicle middleware. The in-vehicle middleware includes: a function detection module and a function graph distribution module; the function detection module and the function graph distribution module are communicatively connected; the control method of the in-vehicle middleware includes: the function detection module detects the vehicle functions that the cockpit domain controller can control; and constructs a global function graph using the function descriptions of each vehicle function; the function graph distribution module, in response to receiving a function notification instruction sent by a mobile terminal, constructs a function description data packet based on the global function graph; and distributes the function description data packet to the mobile terminal so that the mobile terminal can control the vehicle functions using the function description data packet.

[0023] Based on the aforementioned technical means, this application designs an in-vehicle middleware to abstract the capabilities of the cockpit domain controller into standardized services and constructs a global functional graph. This enables a high degree of decoupling between software and hardware, significantly improving the reusability and iteration efficiency of vehicle functions. At the same time, it also allows for more flexible invocation of atomic services on mobile terminals, effectively reducing development costs and achieving a closed loop for vehicle function control.

[0024] In one possible implementation, the method further includes: after the cockpit domain controller is woken up, automatically scanning the bus nodes of the vehicle bus connected to the cockpit domain controller, as well as the operating system service list and operating system call interface of the cockpit domain controller, to discover vehicle functions; uploading the vehicle functions to the global function graph generation unit; the global function graph generation unit is used to construct a global function graph based on the function descriptions of the respective vehicle functions; wherein, the vehicle functions include vehicle hardware functions and software functions of the operating system software of the cockpit domain controller; the function description includes a unique function identifier, function name, UI control type corresponding to the function, value range corresponding to the function state value, underlying security constraints to be followed when selecting the state value from the value range, and the current state value of the function.

[0025] In one possible implementation, the process of detecting vehicle functions controllable by the cockpit domain controller and constructing a global functional graph using the functional descriptions of each vehicle function further includes: detecting a target vehicle function in response to receiving an execution completion instruction sent by the first functional detection unit; and updating the global functional graph based on the functional description of the target vehicle function in response to detecting the target vehicle function. The target vehicle function is a newly added vehicle function controllable by the cockpit domain controller.

[0026] In one possible implementation, the vehicle functions controllable by the cockpit domain controller are detected; a global function graph is constructed using the function descriptions of the respective vehicle functions; and the process further includes: in response to receiving an execution completion instruction sent by the first function detection unit, detecting changes in the current function state values ​​of the vehicle functions; and updating the global function graph based on the changes.

[0027] In one possible implementation, the function notification instruction includes: a unique identifier of the mobile terminal; in response to receiving the function notification instruction sent by the mobile terminal, constructing a function description data packet based on a global function map retrieved from a function detection module; sending the function description data packet to the mobile terminal so that the mobile terminal can use the function description data packet to control vehicle functions; further including: authenticating the mobile terminal based on the unique identifier; in response to confirming successful authentication, determining the range of functions that the mobile terminal is allowed to control; wherein, authentication is used to verify whether the mobile terminal has the right to control the vehicle; constructing a local function map based on the function range and the global function map; generating a function description data packet based on the local function map; and sending the function description data packet to the mobile terminal so that the mobile terminal can use the function description data packet to control vehicle functions.

[0028] In one possible implementation, the method further includes: responding to receiving a function control instruction issued by a mobile terminal based on a function description data packet; parsing the function control instruction to obtain a control message; determining whether the control message violates a preset conflict rule based on the control message and the vehicle's driving state; and forwarding the control message to the cockpit domain controller in response to determining that the control message does not violate the preset conflict rule, so that the cockpit domain controller executes the control message; wherein the preset conflict rule is used to indicate conflicting vehicle driving states and vehicle functions.

[0029] In one possible implementation, the function control instruction includes an instruction issuance timestamp, random anti-duplicate code, a unique identifier of the function of the vehicle to be controlled, and a target value of the function of the vehicle to be controlled; parsing the function control instruction to obtain a control message includes: determining a target parsing plugin based on the vehicle type and the unique identifier of the function of the vehicle to be controlled; wherein, the target parsing plugin is one of a number of pre-set parsing plugins in the vehicle middleware; using the target parsing plugin, the function control instruction is parsed to obtain the control message.

[0030] In one possible implementation, the method further includes: establishing a Bluetooth communication connection between the mobile terminal and the vehicle middleware in response to determining that the spatial distance between the mobile terminal and the vehicle middleware is less than a preset spatial distance; sending a local area network access certificate to the mobile terminal in response to determining that the Bluetooth communication connection has been successfully established, so that the mobile terminal establishes a local area network communication connection between the mobile terminal and the vehicle middleware based on the local area network access certificate; controlling the mobile terminal to communicate with the vehicle middleware via the local area network, and adjusting the connection state of the Bluetooth communication connection from a normal connection state to a basic connection state; the basic connection state is used to maintain a basic heartbeat connection; and restoring the connection state of the Bluetooth communication connection to a normal connection state in response to determining that the network quality of the local area network connection is lower than the expected network quality, and controlling the mobile terminal to communicate with the vehicle middleware via Bluetooth.

[0031] Fourthly, this application provides a control method for a mobile terminal. The mobile terminal includes: an instruction issuing module and a rendering module; the instruction issuing module is communicatively connected to the vehicle middleware and the rendering module respectively; the control method for the mobile terminal includes: the instruction issuing module, in response to monitoring a user triggering a first target UI control, sending a function notification instruction to the vehicle middleware, so that the vehicle middleware issues a function description data packet; and sending the function description data packet to the rendering module; wherein, the function description data packet is determined based on a global function graph; the global function graph is constructed by the vehicle middleware detecting the vehicle functions that the cockpit domain controller can control, and using the function descriptions of each vehicle function; the rendering module renders the UI control interface corresponding to the function description data packet in the target interface; the instruction issuing module, in response to monitoring a touch operation on the UI control interface, generates a function control instruction; and sends the function control instruction to the vehicle middleware, so that the vehicle middleware executes control of the vehicle functions based on the function control instruction.

[0032] Based on the above technical means, when the application detects that the user intends to view or adjust vehicle functions, it receives the function description data packet of the vehicle middleware on the mobile terminal, and renders the function description data packet on the target interface. Then, the vehicle functions are controlled according to the rendered control interface. This eliminates the need to pre-set a large number of redundant interfaces, reduces the terminal storage and memory usage, and completely decouples the interface from the vehicle functions, realizing cross-terminal and cross-vehicle function control adaptation.

[0033] Fifthly, this application provides a vehicle including the vehicle-mounted middleware described in the first aspect, wherein the vehicle-mounted middleware is controlled using the control method for the vehicle-mounted middleware described in the third aspect.

[0034] In a sixth aspect, this application provides an electronic device, including: a processor and a memory, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the methods of the third aspect, the fourth aspect and any possible implementation thereof described above.

[0035] In a seventh aspect, this application provides a computer-readable storage medium that, when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform the methods described in the third aspect, the fourth aspect, and any possible implementation thereof.

[0036] Eighthly, this application provides a computer program product including computer instructions that, when executed on an electronic device, cause the electronic device to perform the methods described in the third and fourth aspects and any possible implementation thereof.

[0037] It should be noted that the technical effects of any of the implementation methods in aspects three through eight can be found in the technical effects of the corresponding implementation methods in aspects one and two, and will not be repeated here.

[0038] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application, and do not constitute an undue limitation of this application.

[0040] Figure 1 This is a schematic diagram of a vehicle shown in an embodiment of this application; Figure 2 This is a block diagram illustrating an in-vehicle middleware according to an embodiment of this application; Figure 3 This is a block diagram illustrating another vehicle-mounted middleware according to an embodiment of this application; Figure 4 This is a block diagram illustrating a mobile terminal according to an embodiment of this application; Figure 5 This is a flowchart illustrating a control method for an in-vehicle middleware according to an embodiment of this application; Figure 6 This is a flowchart illustrating a control method for a mobile terminal according to an embodiment of this application; Figure 7 This is a block diagram illustrating an electronic device according to an embodiment of this application. Detailed Implementation

[0041] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0042] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0043] In the embodiments of this application, the words "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a specific manner.

[0044] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0045] The vehicle service scheduling device provided in this application embodiment is used for one-time scheduling of vehicle services for vehicles (especially intelligent driving vehicles). Vehicles can also be referred to as vehicles, mobile carriers, electric vehicles (EVs), hybrid electric vehicles (HEVs), plug-in hybrid electric vehicles (PHEVs), fuel cell vehicles (FCVs), autonomous vehicles, intelligent and connected vehicles (ICVs), driverless vehicles, etc.

[0046] In this application, the vehicle can be a sedan, a sport utility vehicle (SUV), a truck, a special vehicle (such as an ambulance, fire truck, police car, etc.), a driverless taxi, a smart connected bus, an autonomous logistics vehicle, an electric truck, etc. Furthermore, this method is also applicable to various special-purpose vehicles, such as agricultural vehicles, mining vehicles, forestry vehicles, airport vehicles, and port vehicles. This application does not impose specific limitations in this regard.

[0047] like Figure 1 As shown, the vehicle in this application includes: an on-board middleware 101 and a cockpit domain controller 102.

[0048] The cockpit domain controller 102 is used to centrally integrate multiple electronic control units to achieve unified management of various functions within the vehicle cockpit.

[0049] The vehicle middleware 101 is used to detect the vehicle functions that the cockpit domain controller 102 can control, and to construct a global function graph using the function descriptions corresponding to the vehicle functions.

[0050] The vehicle middleware 101 is also used to construct a functional description data package based on the global functional map and send it to the mobile terminal.

[0051] In practical applications, the cockpit domain controller 102 can communicate with one or more vehicle middleware 101.

[0052] For ease of understanding, this application uses the communication connection between an in-vehicle middleware 101 and a cockpit domain controller 102 as an example for illustration.

[0053] As a feasible approach, Figure 1 The vehicle-mounted middleware 101 and cockpit domain controller 102 are installed in the vehicle. The vehicle-mounted middleware 101 and cockpit domain controller 102 can be functional modules integrated into the same device, or they can be independently installed devices. This application does not impose any limitations on the comparison.

[0054] It is easy to understand that when the vehicle middleware 101 and the cockpit domain controller 102 are functional modules integrated within the same device, the communication method between the vehicle middleware 101 and the cockpit domain controller 102 is the same as the communication between modules within the device. In this case, the communication process between the two is the same as the "communication process when the vehicle middleware 101 and the cockpit domain controller 102 are set up independently". For ease of understanding, this application mainly uses the example of the vehicle middleware 101 and the cockpit domain controller 102 being set up independently for explanation.

[0055] When the vehicle-mounted middleware 101 and cockpit domain controller 102 are located at the terminal, the terminal can be a device providing data connectivity to vehicle users or vehicle owners, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The terminal can communicate with one or more core networks via a radio access network (RAN). The terminal can be a mobile terminal, such as a computer with a mobile terminal, or a mobile device that exchanges voice and / or data with the radio access network, such as a mobile phone, tablet, laptop, netbook, or personal digital assistant (PDA). This application does not impose any limitations on this.

[0056] It should be noted that the structures illustrated in the embodiments of this application do not constitute a limitation on the vehicle. The vehicle may include more or fewer components than illustrated, or combine or separate certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of both.

[0057] For ease of understanding, the following detailed description of the vehicle-mounted middleware and mobile terminal provided in this application is provided in conjunction with the accompanying drawings.

[0058] Figure 2 This is a block diagram illustrating an in-vehicle middleware according to an embodiment of this application, with reference to... Figure 2 The vehicle-mounted middleware 101 includes: a function detection module 201 and a function map distribution module 202.

[0059] The function detection module 201 and the function map distribution module 202 are connected in communication.

[0060] Function discovery module 201 is used to discover the vehicle functions that the cockpit domain controller can control; and to construct a global function map using the function descriptions of each vehicle function.

[0061] The aforementioned vehicle functions include both vehicle hardware functions and software functions of the operating system of the cockpit domain controller. For example, hardware functions include the adjustment functions of hardware devices such as seats, air conditioning, and windows. Software functions include audio playback software, video playback software, and navigation software, with features such as play, pause, volume adjustment, fast forward, and rewind.

[0062] The above functional description includes the unique identifier of the function, the function name, the type of UI control corresponding to the function, the value range corresponding to the function's state value, the underlying security constraints that must be followed when selecting a state value from the value range, and the current state value of the function.

[0063] As one feasible approach, the in-vehicle middleware abstracts the various vehicle functions controllable by the cockpit domain controller into structured files (e.g., JSON-formatted configuration files) based on a standardized data semantic model. During vehicle operation, it matches the current state values ​​of each vehicle function with the detected function's current state, thereby updating the structured description files. After a connection is established between the mobile terminal and the in-vehicle middleware, the middleware uploads the updated structured files to the mobile terminal.

[0064] The data semantic model described above has clear definitions for the transformation of information such as the function name of each vehicle function, the type of UI control corresponding to the function, and the value range corresponding to the function status value.

[0065] The aforementioned global functional graph is a complete panoramic knowledge graph of vehicle functions that can be updated in real time, which is constructed by scanning and summarizing the vehicle functions that can be controlled by the cockpit domain controller.

[0066] For example, the function's unique identifier is 001; the function name is "Air Conditioner"; the UI control type corresponding to the function can be a numerical slider for sliding temperature values, an enumeration list for selecting temperature values, or a Boolean switch for controlling the air conditioner to turn on or off; the value range corresponding to the function's state value is "Air conditioner temperature range is (-20 degrees Celsius, 60 degrees Celsius)"; the underlying safety constraint that must be followed when selecting a state value from the value range is "Air conditioner temperature safety constraint is (0 degrees Celsius, 40 degrees Celsius)"; the current state value of the function is "Air conditioner temperature 20 degrees Celsius".

[0067] As one possible implementation, the function detection module 201 includes: a first function detection unit and a global function map generation unit; the first function detection unit and the global function map generation unit are communicatively connected.

[0068] The first function detection unit is used to automatically scan the bus nodes of the vehicle bus connected to the cockpit domain controller, as well as the operating system service list and operating system call interface of the cockpit domain controller, after the cockpit domain controller is woken up, in order to detect the vehicle functions; and upload the vehicle functions to the global function map generation unit.

[0069] The aforementioned automatic scanning refers to the process by which the cockpit domain controller, when awakened or initialized, can automatically traverse and retrieve the vehicle's hardware and software functions without human intervention.

[0070] The aforementioned vehicle bus is a network used for data transmission and communication between various electronic control units within a vehicle. Common bus types include Controller Area Network (CAN) bus, Local Area Network (LIN) bus, and in-vehicle Ethernet.

[0071] The aforementioned bus nodes refer to the various electronic control units (ECUs) mounted on the vehicle's bus. These are modules capable of executing vehicle functions. Examples include modules that control door opening and closing, window movement, air conditioning temperature, and air conditioning airflow direction.

[0072] As one possible approach, the first functional detection unit scans the corresponding functions of the vehicle hardware using a preset electrical tester, as well as the physical status information of each hardware function reported via the vehicle's CAN bus. For example, the physical status information includes sensor data and actuator data such as vehicle speed, battery level, door and window status, and headlight status, as well as fault status information of each hardware function.

[0073] The above-mentioned operating system service list refers to the set of functions provided by the operating system running inside the cockpit domain controller. These services may involve functions such as audio and video playback, network connection, and voice recognition.

[0074] As one possible approach, the first function detection unit exposes a preset interface, through which the software provider transmits a list of operating system services for the functions to be controlled. This allows the software provider to obtain information such as the unique identifier of the function, the function name, the type of UI control corresponding to the function, the value range corresponding to the function's state value, the underlying security constraints to be followed when selecting a state value from the value range, and the current state value of the function.

[0075] The aforementioned operating system call interface is a standardized function entry point provided by the operating system, used to connect the vehicle's CAN / LIN bus and the cockpit controller.

[0076] As one possible approach, the operating system call interface is used to invoke the control capabilities of various software and hardware functions to the first function detection unit.

[0077] The global function map generation unit is used to construct a global function map based on the functional descriptions of each vehicle function.

[0078] The function map distribution module 202 is used to respond to receiving a function notification instruction sent by the mobile terminal, construct a function description data packet based on the global function map retrieved from the function detection module, and distribute the function description data packet to the mobile terminal so that the mobile terminal can use the function description data packet to control the vehicle functions.

[0079] The aforementioned function notification command refers to a command issued by the mobile terminal that contains the control intent of vehicle functions.

[0080] The aforementioned functional description data package refers to a description data package in JSON format, a standard lightweight data exchange format, which is transformed from the global functional map. The functional description data package includes information such as the unique identifier of each vehicle function, the function name, the UI control type corresponding to the function, the value range corresponding to the function's state value, the underlying safety constraints that must be followed when selecting the state value from the value range, and the current state value of the function.

[0081] As one possible approach, the function notification instruction includes: the mobile terminal's unique identifier.

[0082] The aforementioned unique terminal identifier is a terminal identifier used to distinguish different mobile terminals. Each unique terminal identifier is uniquely associated with a driver or passenger.

[0083] The functional map distribution module 202 includes: an authentication unit and a generation unit; the authentication unit and the generation unit are connected in communication.

[0084] The authentication unit is used to authenticate the mobile terminal based on its unique identifier; in response to the successful authentication, it determines the range of functions that the mobile terminal is allowed to operate; and sends the range of functions to the generation unit.

[0085] Among them, identity authentication is used to verify whether the mobile terminal has the right to control the vehicle.

[0086] As one feasible approach, the vehicle driver or owner has control over the functions corresponding to the vehicle's overall functional map. Vehicle occupants have control over the functions corresponding to the vehicle's partial functional map. Non-vehicle occupants do not have control over the vehicle's functions.

[0087] The generation unit is used to construct a local functional map based on the functional scope and the global functional map; generate a functional description data package based on the local functional map; and send the functional description data package to the mobile terminal so that the mobile terminal can use the functional description data package to control the vehicle functions.

[0088] The aforementioned partial functional map refers to the functional map that corresponds to the identity authentication information and indicates the person or entity has control over the vehicle's functions. For example, rear-seat passengers do not have control over the steering wheel or engine.

[0089] Based on the aforementioned technical means, this application designs an in-vehicle middleware to abstract the capabilities of the cockpit domain controller into standardized services and constructs a global functional graph. This enables a high degree of decoupling between software and hardware, significantly improving the reusability and iteration efficiency of vehicle functions. At the same time, it also allows for more flexible invocation of atomic services on mobile terminals, effectively reducing development costs and achieving a closed loop for vehicle function control.

[0090] In some embodiments, after the initial generation of the global functional map, the functional detection module 201 further includes a second functional detection unit; the second functional detection unit is communicatively connected to the first functional detection unit and the global functional map generation unit.

[0091] The second function detection unit is used to detect the function of the target vehicle in response to receiving the execution completion instruction sent by the first function detection unit.

[0092] In response to the detection of target vehicle functions, the global function graph is updated based on the function description of the target vehicle functions.

[0093] The aforementioned target vehicle functions are new vehicle functions that can be controlled by the cockpit domain controller.

[0094] For example, the target vehicle function includes adding control functions for the audio and video player after the audio and video player is added to the in-vehicle terminal.

[0095] In some embodiments, the function detection module 201 further includes: a third function detection unit; the third function detection unit is communicatively connected to the first function detection unit and the global function map generation unit respectively.

[0096] The third function detection unit is used to detect changes in the current function status value of the vehicle function in response to receiving the execution completion instruction sent by the first function detection unit; and update the global function map based on the changes.

[0097] For example, the above changes could be changing the air conditioning temperature from 20 degrees Celsius to 17 degrees Celsius; or changing the window from closed to open.

[0098] As one possible approach, the aforementioned changes can be implemented by the vehicle's occupants manually adjusting the vehicle's functional status values ​​from inside the vehicle.

[0099] In some embodiments, when the above-mentioned changes occur, the cockpit domain controller sends a state change broadcast. After the vehicle middleware captures the broadcast, it immediately updates the state value in the global function graph and actively generates a synchronization message containing the latest state value and a unique function identifier, and pushes it to the mobile terminal.

[0100] In some embodiments, the function detection module 201 is further configured to, when there is a deletion of vehicle functions in the cockpit domain controller, take the deleted function as the target vehicle function, send it to the mobile terminal according to the unique function identifier of the target vehicle function, and delete the rendering of the target vehicle function, thereby realizing the update of the global function map.

[0101] In some embodiments, the function detection module 201 is further configured to update the global function map based on the function description of the target vehicle function when the target vehicle function exists in the cockpit domain controller and the target vehicle function is updated.

[0102] Figure 3 This is a block diagram illustrating another vehicle-mounted middleware according to an embodiment of this application, see reference. Figure 3 The vehicle-mounted middleware 101 includes: a function detection module 201, a function map distribution module 202, a function control command execution module 203, and a communication setup module 204. The function map distribution module 202 is communicatively connected to both the function control command execution module 203 and the communication setup module 204.

[0103] The function control instruction execution module 203 is used to respond to receiving a function control instruction issued by the mobile terminal based on a function description data packet.

[0104] The aforementioned control commands include command issuance timestamps, random anti-duplicate codes, unique function identifiers for the functions of the vehicle to be controlled, and target values ​​for the functions of the vehicle to be controlled.

[0105] As one possible approach, the function control instruction execution module 203 is specifically used to: determine the target parsing plugin based on the vehicle type and the unique identifier of the function of the vehicle to be controlled; wherein, the target parsing plugin is one of a number of pre-set parsing plugins in the vehicle middleware; and use the target parsing plugin to parse the function control instruction to obtain the control message.

[0106] The above vehicle types are related to the vehicle's brand and model.

[0107] The aforementioned target parsing plugin is a software module in the vehicle middleware architecture used to implement instruction translation and hardware / software decoupling. It converts function control instructions into standardized control messages. For example, for vehicle model A, the target parsing plugin translates the instruction into calling the Android system API "CarPropertyManager.setProperty();", which is equivalent to calling the "Set Vehicle Properties" method in the Android system property manager. For vehicle model B, the target parsing plugin translates it into sending a specific CAN matrix message to the vehicle gateway.

[0108] Because of the differences in vehicle type and the functions of the vehicle to be controlled, the target parsing plugin also differs. Therefore, a unique index is generated based on the vehicle type and the functions of the vehicle to be controlled, and the matching target parsing plugin is selected from multiple preset parsing plugins in the vehicle middleware.

[0109] The control message is obtained by parsing the function control command.

[0110] Based on the control message and the vehicle's driving status, determine whether the control message violates the preset conflict rules.

[0111] The aforementioned preset conflict rules are a set of safety strategies and logical constraints used to ensure driving safety and equipment lifespan. For example, if the vehicle is currently in a "high-speed driving" state and the received control message is "open the trunk", then the control message violates the preset conflict rules, and the control message needs to be intercepted, an error code is returned to the vehicle middleware, and then transmitted to the mobile terminal.

[0112] In response to determining that the control message does not violate the preset conflict rules, the control message is forwarded to the cockpit domain controller so that the cockpit domain controller can execute the control message.

[0113] Among them, the preset conflict rules are used to indicate the vehicle driving status and vehicle functions that conflict.

[0114] The communication setup module 204 is used to establish a Bluetooth communication connection between the mobile terminal and the vehicle middleware in response to determining that the spatial distance between the mobile terminal and the vehicle middleware is less than a preset spatial distance.

[0115] The aforementioned preset spatial distance is the maximum distance allowed by the local area network (LAN) when the vehicle-mounted middleware is used for LAN access. For example, the preset spatial distance can be 500 meters.

[0116] In response to the successful completion of the Bluetooth communication connection, a local area network access certificate is sent to the mobile terminal so that the mobile terminal can establish a local area network communication connection between the mobile terminal and the vehicle middleware based on the local area network access certificate.

[0117] The aforementioned LAN access credentials include the Service Set Identifier (SSID) of the vehicle WiFi hotspot, the dynamic password, and the assigned socket port number.

[0118] The aforementioned local area network (LAN) communication connection is achieved through a high-bandwidth, low-latency TCP / IP LAN data channel.

[0119] Additionally, it controls the mobile terminal to communicate with the vehicle middleware via a local area network, and adjusts the Bluetooth communication connection status from the normal connection status to the basic connection status; the basic connection status is used to maintain a basic heartbeat connection.

[0120] The aforementioned heartbeat connection refers to a mechanism in network communication used to maintain a long-term connection and detect the health of the connection.

[0121] In addition, in response to determining that the network quality of the local area network connection is lower than the expected network quality, the connection status of the Bluetooth communication connection is restored to the normal connection status, and the mobile terminal is controlled to communicate with the vehicle middleware via Bluetooth.

[0122] The aforementioned network quality can be judged based on indicators such as latency, packet loss rate, throughput and bandwidth, jitter, signal strength, connection establishment time and reconnection success rate.

[0123] For example, when a vehicle is in an underground parking garage with strong interference, the network quality of the local area network connection will be lower than the expected network quality.

[0124] As an achievable method, when the packet loss rate of the local area network data channel exceeds the preset packet loss rate, the connection status of the Bluetooth communication connection is restored to the normal connection status, and the mobile terminal is controlled to communicate with the vehicle middleware via Bluetooth.

[0125] Figure 4 This is a block diagram of a mobile terminal shown in an embodiment of this application, with reference to... Figure 4The mobile terminal 400 includes an instruction issuing module 401 and a rendering module 402. The instruction issuing module 401 is communicatively connected to the vehicle-mounted middleware 101 and the rendering module 402, respectively.

[0126] The instruction issuing module 401 is used to respond to the monitoring of the user triggering the first target UI control, send a function notification instruction to the vehicle middleware, so that the vehicle middleware issues a function description data packet; and send the function description data packet to the rendering module; wherein, the function description data packet is determined based on the global function graph; the global function graph is constructed by the vehicle middleware discovering the vehicle functions that the cockpit domain controller can control, and using the function descriptions of the respective vehicle functions.

[0127] The aforementioned first target UI control is an interactive element on the mobile terminal's user interface that the user clicks, swipes, or operates to trigger any vehicle function; it is a function switch or function entry point. For example, the first target UI control can be a button, icon, card, or list item.

[0128] The rendering module 402 is used to render the UI control interface corresponding to the function description data package in the target interface; the instruction issuing module is also used to generate function control instructions in response to the monitored touch operation on the UI control interface; and to send the function control instructions to the vehicle middleware so that the vehicle middleware can perform the operation of vehicle functions based on the function control instructions.

[0129] The aforementioned touch operations refer to the behavior of users directly physically contacting a screen or panel with a touch-sensitive layer using their fingers or touch devices as input mediums to input commands or perform interactions. For example, touch operations include: clicking, long-pressing, swiping, dragging, two-finger zooming, and two-finger rotation.

[0130] Based on the above technical means, when the application detects that the user intends to view or adjust vehicle functions, it receives the function description data packet of the vehicle middleware on the mobile terminal, and renders the function description data packet on the target interface. Then, the vehicle functions are controlled according to the rendered control interface. This eliminates the need to pre-set a large number of redundant interfaces, reduces the terminal storage and memory usage, and completely decouples the interface from the vehicle functions, realizing cross-terminal and cross-vehicle function control adaptation.

[0131] In some embodiments, the vehicle middleware includes: a function detection module and a function graph distribution module; the function detection module and the function graph distribution module are communicatively connected. Figure 5 This is a flowchart illustrating a control method for an in-vehicle middleware according to an embodiment of this application, with reference to... Figure 5 The control method for the vehicle-mounted middleware includes: S501, the function detection module detects the vehicle functions that the cockpit domain controller can control.

[0132] S502, the function discovery module constructs a global function graph by utilizing the function descriptions of each vehicle function.

[0133] S503 The function map distribution module responds to the function notification instruction sent by the mobile terminal by constructing a function description data packet based on the global function map.

[0134] S504 The function map distribution module distributes the function description data package to the mobile terminal so that the mobile terminal can use the function description data package to control the vehicle functions.

[0135] Based on the aforementioned technical means, this application designs an in-vehicle middleware to abstract the capabilities of the cockpit domain controller into standardized services and constructs a global functional graph. This enables a high degree of decoupling between software and hardware, significantly improving the reusability and iteration efficiency of vehicle functions. At the same time, it also allows for more flexible invocation of atomic services on mobile terminals, effectively reducing development costs and achieving a closed loop for vehicle function control.

[0136] In one possible implementation, the method further includes: after the cockpit domain controller is woken up, automatically scanning the bus nodes of the vehicle bus connected to the cockpit domain controller, as well as the operating system service list and operating system call interface of the cockpit domain controller, to discover vehicle functions; uploading the vehicle functions to the global function graph generation unit; the global function graph generation unit is used to construct a global function graph based on the function descriptions of the respective vehicle functions; wherein, the vehicle functions include vehicle hardware functions and software functions of the operating system software of the cockpit domain controller; the function description includes a unique function identifier, function name, UI control type corresponding to the function, value range corresponding to the function state value, underlying security constraints to be followed when selecting the state value from the value range, and the current state value of the function.

[0137] In one possible implementation, the process of detecting vehicle functions controllable by the cockpit domain controller and constructing a global functional graph using the functional descriptions of each vehicle function further includes: detecting a target vehicle function in response to receiving an execution completion instruction sent by the first functional detection unit; and updating the global functional graph based on the functional description of the target vehicle function in response to detecting the target vehicle function. The target vehicle function is a newly added vehicle function controllable by the cockpit domain controller.

[0138] In one possible implementation, the vehicle functions controllable by the cockpit domain controller are detected; a global function graph is constructed using the function descriptions of the respective vehicle functions; and the process further includes: in response to receiving an execution completion instruction sent by the first function detection unit, detecting changes in the current function state values ​​of the vehicle functions; and updating the global function graph based on the changes.

[0139] In one possible implementation, the function notification instruction includes: a unique identifier of the mobile terminal; in response to receiving the function notification instruction sent by the mobile terminal, constructing a function description data packet based on a global function map retrieved from a function detection module; sending the function description data packet to the mobile terminal so that the mobile terminal can use the function description data packet to control vehicle functions; further including: authenticating the mobile terminal based on the unique identifier; in response to confirming successful authentication, determining the range of functions that the mobile terminal is allowed to control; wherein, authentication is used to verify whether the mobile terminal has the right to control the vehicle; constructing a local function map based on the function range and the global function map; generating a function description data packet based on the local function map; and sending the function description data packet to the mobile terminal so that the mobile terminal can use the function description data packet to control vehicle functions.

[0140] In one possible implementation, the method further includes: responding to receiving a function control instruction issued by a mobile terminal based on a function description data packet; parsing the function control instruction to obtain a control message; determining whether the control message violates a preset conflict rule based on the control message and the vehicle's driving state; and forwarding the control message to the cockpit domain controller in response to determining that the control message does not violate the preset conflict rule, so that the cockpit domain controller executes the control message; wherein the preset conflict rule is used to indicate conflicting vehicle driving states and vehicle functions.

[0141] In one possible implementation, the function control instruction includes an instruction issuance timestamp, random anti-duplicate code, a unique identifier of the function of the vehicle to be controlled, and a target value of the function of the vehicle to be controlled; parsing the function control instruction to obtain a control message includes: determining a target parsing plugin based on the vehicle type and the unique identifier of the function of the vehicle to be controlled; wherein, the target parsing plugin is one of a number of pre-set parsing plugins in the vehicle middleware; using the target parsing plugin, the function control instruction is parsed to obtain the control message.

[0142] In one possible implementation, the method further includes: establishing a Bluetooth communication connection between the mobile terminal and the vehicle middleware in response to determining that the spatial distance between the mobile terminal and the vehicle middleware is less than a preset spatial distance; sending a local area network access certificate to the mobile terminal in response to determining that the Bluetooth communication connection has been successfully established, so that the mobile terminal establishes a local area network communication connection between the mobile terminal and the vehicle middleware based on the local area network access certificate; controlling the mobile terminal to communicate with the vehicle middleware via the local area network, and adjusting the connection state of the Bluetooth communication connection from a normal connection state to a basic connection state; the basic connection state is used to maintain a basic heartbeat connection; and restoring the connection state of the Bluetooth communication connection to a normal connection state in response to determining that the network quality of the local area network connection is lower than the expected network quality, and controlling the mobile terminal to communicate with the vehicle middleware via Bluetooth.

[0143] In some embodiments, the mobile terminal includes: an instruction issuing module and a rendering module; the instruction issuing module is communicatively connected to the vehicle-mounted middleware and the rendering module, respectively. Figure 6 This is a flowchart illustrating a control method for a mobile terminal according to an embodiment of this application. (Refer to...) Figure 6 The control method for the mobile terminal includes: S601, the instruction issuing module responds to the monitoring of the user triggering the first target UI control by sending a function notification instruction to the vehicle middleware, so that the vehicle middleware issues a function description data packet.

[0144] The functional description data package is determined based on the global functional map; the global functional map is constructed by the vehicle middleware discovering the vehicle functions that the cockpit domain controller can control and using the functional descriptions of each of the vehicle functions.

[0145] S602. The rendering module renders the UI control interface corresponding to the function description data package in the target interface.

[0146] S603, the instruction issuing module responds to the monitored touch operation on the UI control interface and generates function control instructions.

[0147] S604 The instruction issuing module sends function control instructions to the vehicle middleware, so that the vehicle middleware can perform control of vehicle functions based on the function control instructions.

[0148] Based on the above technical means, when the application detects that the user intends to view or adjust vehicle functions, it receives the function description data packet of the vehicle middleware on the mobile terminal, and renders the function description data packet on the target interface. Then, the vehicle functions are controlled according to the rendered control interface. This eliminates the need to pre-set a large number of redundant interfaces, reduces the terminal storage and memory usage, and completely decouples the interface from the vehicle functions, realizing cross-terminal and cross-vehicle function control adaptation.

[0149] Regarding the methods in the above embodiments, the specific manner in which each step is performed has been described in detail in the embodiments of the vehicle middleware and mobile terminal, and will not be elaborated here.

[0150] Figure 7 This is a block diagram illustrating an electronic device according to an embodiment of this application. Figure 7 As shown, the electronic device includes, but is not limited to, a processor 701 and a memory 702.

[0151] The memory 702 described above is used to store the executable instructions of the processor 701. It is understood that the processor 701 is configured to execute instructions to implement the vehicle middleware control method and the mobile terminal control method in the above embodiments.

[0152] It should be noted that those skilled in the art will understand that Figure 7 The electronic device structure shown does not constitute a limitation on the electronic device; the electronic device may include, but is not limited to, other electronic devices. Figure 7 This may indicate more or fewer components, or combinations of certain components, or different component arrangements.

[0153] Processor 701 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in memory 702, and by calling data stored in memory 702, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. Processor 701 may include one or more processing units. Processor 701 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into processor 701.

[0154] The memory 702 can be used to store software programs and various data. The memory 702 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, application programs required by at least one functional module (such as deterministic components, integrated components, etc.), etc. Furthermore, the memory 702 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0155] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 702 including instructions, which can be executed by a processor 701 of an electronic device to implement the methods in the above embodiments.

[0156] In actual implementation, Figure 2 The functional detection module 201 and the functional map distribution module 202, and Figure 4 The functions of the instruction issuing module 401 and the rendering module 402 can both be provided by... Figure 7 The processor 701 calls the computer program stored in the memory 702 to implement the process. The specific execution process can be found in the description of the method section in the previous embodiment, and will not be repeated here.

[0157] Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a read-only memory (ROM), random access memory (RAM), compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device. In an exemplary embodiment, this application also provides a computer program product including one or more instructions, which can be executed by the processor 701 of an electronic device to perform the methods in the above embodiments.

[0158] It should be noted that when one or more instructions in the computer-readable storage medium or computer program product are executed by the processor of an electronic device, they implement the various processes of the above method embodiments and achieve the same technical effect as the above method. To avoid repetition, they will not be described again here.

[0159] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0160] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0161] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0162] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0163] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0164] This application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the above method embodiments.

[0165] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method in the method flow shown in the above method embodiments.

[0166] The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, a register, a hard disk, an optical fiber, a portable compact disk read-only memory, an optical storage device, a magnetic storage device, or any suitable combination thereof, or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can reside in an application-specific integrated circuit (ASIC). In embodiments of this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0167] Since the vehicle middleware control method, mobile terminal control method, computer-readable storage medium, and computer program product in the embodiments of this application can be applied to the above-mentioned vehicle middleware and mobile terminal, the technical effects they can obtain can also be referred to the above-mentioned method embodiments. The embodiments of this application will not be repeated here.

[0168] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A vehicle-mounted middleware, characterized in that, The vehicle-mounted middleware includes: a function detection module and a function graph distribution module; the function detection module and the function graph distribution module are communicatively connected. The function detection module is used to detect the vehicle functions that the cockpit domain controller can control; and to construct a global function graph using the function descriptions of each vehicle function; wherein the function description includes a unique function identifier, function name, UI control type corresponding to the function, value range corresponding to the function state value, underlying security constraints to be followed when selecting a state value from the value range, and the current state value of the function. The function map distribution module is used to respond to receiving a function notification instruction sent by a mobile terminal, construct a function description data package based on the global function map retrieved from the function detection module, and distribute the function description data package to the mobile terminal so that the mobile terminal renders the corresponding UI control interface in the target interface according to the function description data package, and generates function control instructions in response to touch operations on the UI control interface. The vehicle-mounted middleware is used to receive the function control commands and perform operations on the vehicle functions based on the function control commands.

2. The vehicle-mounted middleware according to claim 1, characterized in that, The function detection module includes: a first function detection unit and a global function map generation unit; the first function detection unit and the global function map generation unit are communicatively connected. The first function detection unit is configured to: automatically scan the bus nodes of the vehicle bus connected to the cockpit domain controller, as well as the operating system service list and operating system call interface of the cockpit domain controller, after the cockpit domain controller is woken up, in order to detect the vehicle functions; and upload the vehicle functions to the global function map generation unit. The global function map generation unit is used to construct the global function map based on the functional descriptions of each of the vehicle functions. The vehicle functions include vehicle hardware functions and software functions of the operating system software of the cockpit domain controller.

3. The vehicle-mounted middleware according to claim 2, characterized in that, The function detection module further includes: a second function detection unit; the second function detection unit is communicatively connected to the first function detection unit and the global function map generation unit, respectively; The second function detection unit is configured to detect the target vehicle function in response to receiving an execution completion instruction sent by the first function detection unit; and to update the global function map based on the function description of the target vehicle function in response to detecting the target vehicle function. The target vehicle function is a newly added vehicle function that can be controlled by the cockpit domain controller.

4. The vehicle-mounted middleware according to claim 2, characterized in that, The function detection module further includes: a third function detection unit; the third function detection unit is communicatively connected to the first function detection unit and the global function map generation unit respectively; The third function detection unit is used to detect changes in the current function status value of the vehicle function in response to receiving an execution completion instruction sent by the first function detection unit; and to update the global function map based on the changes.

5. The vehicle-mounted middleware according to any one of claims 1-4, characterized in that, The function notification instruction includes: the unique identifier of the mobile terminal; the function map distribution module includes: an authentication unit and a generation unit; the authentication unit and the generation unit are communicatively connected; The authentication unit is used to authenticate the mobile terminal based on the terminal's unique identifier; in response to determining that the authentication is successful, it determines the range of functions that the mobile terminal is allowed to control; and sends the range of functions to the generation unit; wherein, the authentication is used to verify whether the mobile terminal has the right to control the vehicle; The generation unit is configured to construct a local functional map based on the functional scope and the global functional map; generate the functional description data package based on the local functional map; and send the functional description data package to the mobile terminal so that the mobile terminal can use the functional description data package to control the vehicle functions.

6. The vehicle-mounted middleware according to any one of claims 1-4, characterized in that, The vehicle-mounted middleware also includes: a function control instruction execution module; The function control instruction execution module is configured to: respond to receiving a function control instruction issued by the mobile terminal based on the function description data packet; parse the function control instruction to obtain a control message; determine whether the control message violates a preset conflict rule based on the control message and the vehicle's driving status; and forward the control message to the cockpit domain controller in response to determining that the control message does not violate the preset conflict rule, so that the cockpit domain controller executes the control message. The preset conflict rules are used to indicate conflicting vehicle driving states and vehicle functions.

7. The vehicle-mounted middleware according to claim 6, characterized in that, The function control command includes a command issuance timestamp, a random anti-duplicate code, a unique identifier for the function of the vehicle to be controlled, and a target value for the function of the vehicle to be controlled; the function control command execution module is specifically used for: Based on the vehicle type and the unique functional identifier of the vehicle to be controlled, a target parsing plugin is determined; wherein, the target parsing plugin is one of a plurality of pre-set parsing plugins in the vehicle middleware; The target parsing plugin is used to parse the function control instructions to obtain the control message.

8. The vehicle-mounted middleware according to any one of claims 1-4, characterized in that, The vehicle-mounted middleware also includes: a communication setup module; The communication setup module is used to establish a Bluetooth communication connection between the mobile terminal and the vehicle middleware in response to determining that the spatial distance between the mobile terminal and the vehicle middleware is less than a preset spatial distance. In response to the successful completion of the Bluetooth communication connection, a local area network access certificate is sent to the mobile terminal so that the mobile terminal can establish a local area network communication connection between the mobile terminal and the vehicle middleware based on the local area network access certificate. In addition, the system controls the mobile terminal to communicate with the vehicle-mounted middleware via a local area network, and adjusts the Bluetooth communication connection status from a normal connection status to a basic connection status; the basic connection status is used to maintain a basic heartbeat connection. In addition, in response to determining that the network quality of the local area network connection is lower than the expected network quality, the connection state of the Bluetooth communication connection is restored to the normal connection state, and the mobile terminal is controlled to communicate with the vehicle middleware via Bluetooth.

9. A mobile terminal, characterized in that, The mobile terminal includes: an instruction issuing module and a rendering module; the instruction issuing module is communicatively connected to the vehicle-mounted middleware and the rendering module respectively; The instruction issuing module is used to respond to the monitoring of a user triggering a first target UI control by sending a function notification instruction to the vehicle middleware, so that the vehicle middleware issues a function description data packet; and to send the function description data packet to the rendering module; wherein, the function description data packet is determined based on a global function graph; the global function graph is constructed by the vehicle middleware by detecting the vehicle functions that the cockpit domain controller can control, and using the function descriptions of each vehicle function; wherein, the function description includes a unique function identifier, function name, the UI control type corresponding to the function, the value range corresponding to the function state value, the underlying security constraints to be followed when selecting the state value from the value range, and the current state value of the function; The rendering module is used to render the UI control interface corresponding to the function description data package in the target interface; The instruction issuing module is further configured to generate function control instructions in response to the detected touch operation on the UI control interface; and to send the function control instructions to the vehicle middleware, so that the vehicle middleware can perform control of the vehicle functions based on the function control instructions.

10. A control method for vehicle-mounted middleware, characterized in that, The vehicle-mounted middleware includes: a function detection module and a function graph distribution module; the function detection module and the function graph distribution module are communicatively connected; the control method of the vehicle-mounted middleware includes: The function detection module detects the vehicle functions that the cockpit domain controller can control; and constructs a global function graph using the function descriptions of each vehicle function; wherein, the function description includes a unique function identifier, function name, UI control type corresponding to the function, value range corresponding to the function state value, underlying security constraints to be followed when selecting a state value from the value range, and the current state value of the function; In response to receiving a function notification instruction from a mobile terminal, the function map distribution module constructs a function description data package based on the global function map retrieved from the function detection module; and distributes the function description data package to the mobile terminal so that the mobile terminal renders the corresponding UI control interface in the target interface according to the function description data package, and generates function control instructions in response to touch operations on the UI control interface. The vehicle-mounted middleware is used to receive the function control commands and to perform operations on the vehicle functions based on the function control commands.

11. A control method for a mobile terminal, characterized in that, The mobile terminal includes: an instruction issuing module and a rendering module; the instruction issuing module is communicatively connected to both the vehicle-mounted middleware and the rendering module; the control method of the mobile terminal includes: The instruction issuing module, in response to monitoring a user triggering a first target UI control, sends a function notification instruction to the vehicle middleware, causing the vehicle middleware to issue a function description data packet; and sends the function description data packet to the rendering module; wherein, the function description data packet is determined based on a global function graph; the global function graph is constructed by the vehicle middleware detecting vehicle functions controllable by the cockpit domain controller and utilizing the function descriptions of each vehicle function; wherein, the function description includes a unique function identifier, function name, UI control type corresponding to the function, value range corresponding to the function state value, underlying security constraints to be followed when selecting a state value from the value range, and the current state value of the function; The rendering module renders the UI control interface corresponding to the function description data package in the target interface; The instruction issuing module responds to the monitored touch operation on the UI control interface by generating a function control instruction; and sends the function control instruction to the vehicle middleware so that the vehicle middleware can perform control of the vehicle functions based on the function control instruction.

12. A vehicle, characterized in that, Includes the vehicle-mounted middleware as described in any one of claims 1-8, wherein the vehicle-mounted middleware is controlled by the control method for the vehicle-mounted middleware as described in claim 10.

Images