Cockpit Control System and Method

By taking over the graphics rendering and interactive processing of the vehicle cockpit from the mobile terminal, the problem of high cost and resource waste of the cockpit controller is eliminated, thus realizing a cockpit control system with reduced cost and optimized resources.

CN123104548APending Publication Date: 2026-11-17CHERY INTELLIGENT AUTOMOTIVE TECHNOLOGY (HEFEI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611382768.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-07
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the existing technology, dedicated controllers for vehicle cockpits are costly and have overlapping functions with mobile terminals, resulting in a waste of resources.

Method used

By installing a cockpit control application on a mobile terminal, a connection is established with the vehicle's communication processing module via wireless communication, taking over graphics rendering, interactive processing, and control logic, thus eliminating the need for a dedicated in-vehicle cockpit controller and utilizing the mobile terminal's own computing power and display resources.

Benefits of technology

Significantly reduce the overall vehicle hardware cost, avoid overlapping computing power and waste of resources, enhance the personalized cabin experience, and ensure safe and reliable control.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123104548A_ABST
    Figure CN123104548A_ABST
Patent Text Reader

Abstract

This application relates to the field of vehicle control technology, and particularly to a cockpit control system and method. The system includes a mobile terminal, a communication processing module installed in the vehicle, and cockpit hardware. The mobile terminal has a cockpit control application installed. The communication processing module establishes a communication connection with the mobile terminal via wireless communication. The communication processing module is configured to: after completing two-way authentication with the mobile terminal, in response to a takeover request from the mobile terminal, transfer control of the vehicle cockpit issued by the mobile terminal to the mobile terminal; receive cockpit control commands sent by the mobile terminal, and convert the cockpit control commands into control signals; the cockpit hardware is used to execute corresponding cockpit control operations in response to the control signals. This solves the problems of high cost of dedicated controllers and resource waste caused by functional overlap with mobile terminals in related technologies.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a cockpit control system and method. Background Technology

[0002] With the development of automotive intelligence, smart cockpits have become a standard feature in modern vehicles. They typically use dedicated controllers embedded in the vehicle (such as in-vehicle infotainment systems or domain controllers) to handle user input, drive displays, and control cockpit functions. However, dedicated controllers require high-performance chips and memory, which are costly. Furthermore, car owners generally own smartphones with stronger computing capabilities, leading to overlap between the functions of the in-vehicle controllers and smartphones, resulting in wasted resources. Summary of the Invention

[0003] This application provides a cockpit control system and method to solve the problems of high cost of dedicated controllers and resource waste caused by overlapping functions with mobile terminals in related technologies.

[0004] A first aspect of this application provides a cockpit control system, comprising: a mobile terminal having a cockpit control application installed thereon, the cockpit control application providing a graphical user interface (GUI) and generating cockpit control commands based on operation commands input by the user on the GUI; a communication processing module and cockpit hardware devices disposed on the vehicle end, wherein the communication processing module establishes a communication connection with the mobile terminal via wireless communication, and the communication processing module is configured to: after completing two-way authentication with the mobile terminal, in response to a takeover request from the mobile terminal, transfer control of the vehicle cockpit to the mobile terminal; receive cockpit control commands sent by the mobile terminal and convert the cockpit control commands into control signals; and cockpit hardware devices for executing corresponding cockpit control operations in response to the control signals.

[0005] Optionally, the communication processing module establishes a communication connection with the mobile terminal via at least one of Bluetooth, ultra-wideband, or near-field communication protocols.

[0006] Optionally, the communication processing module is a lightweight gateway chip or microcontroller that does not have graphics rendering capabilities.

[0007] Optionally, the cockpit control application of the mobile terminal is configured to: load a user profile stored in the mobile terminal, the user profile including at least one of seat position, rearview mirror angle, air conditioning preference and application layout, and configure the operating parameters of the cockpit hardware devices according to the user profile.

[0008] A second aspect of this application provides a cockpit control method applied to the cockpit control system of the above embodiments, comprising the following steps: establishing a communication connection between a mobile terminal and a communication processing module on the vehicle side; after completing two-way authentication between the communication processing module and the mobile terminal, transferring control of the vehicle cockpit to the mobile terminal in response to a takeover request from the mobile terminal; generating cockpit control commands through the mobile terminal based on operation instructions input by the user on the graphical user interface of the cockpit control application, and sending them to the communication processing module; converting the cockpit control commands into control signals suitable for the vehicle bus through the communication processing module, and sending them to the corresponding cockpit hardware device through the vehicle bus; and the cockpit hardware device executing the corresponding cockpit control operation in response to the control signals.

[0009] Optionally, converting cockpit control commands into control signals suitable for the vehicle bus includes: parsing the cockpit control commands to obtain a data packet containing a target device identifier and operating parameters; converting the data packet into a corresponding bus message based on the target device identifier; and distributing the bus message to the corresponding cockpit hardware device via the target bus.

[0010] Optionally, the cockpit control method further includes: collecting status information after the cockpit hardware performs cockpit control operations; encapsulating the status information into a data packet and sending it to the mobile terminal, so that the mobile terminal matches the corresponding cockpit control command according to the sequence number in the data packet and updates the graphical user interface to display the status information.

[0011] Optionally, the cockpit control method further includes granting control to the mobile terminal located in the driver's seat when multiple authorized mobile terminals are present in the vehicle.

[0012] Optionally, establishing a communication connection between the mobile terminal and the vehicle's communication processing module includes: entering a target listening mode when the vehicle is in a preset state; and establishing a connection between the communication processing module and the mobile terminal when the mobile terminal is detected to have entered a preset distance range in the target listening mode.

[0013] Optionally, the cockpit control method also includes: retaining voice control and shortcut button operations while disabling other operations when the vehicle's speed exceeds a preset threshold; monitoring the connection status between the mobile terminal and the communication processing module, and reclaiming control of the mobile terminal when the wireless connection is disconnected for more than a preset duration.

[0014] Therefore, this application has at least the following beneficial effects: In this embodiment, the mobile terminal reuses its own computing power and display resources to take over the graphics rendering, interaction processing, and control logic originally handled by the vehicle-mounted dedicated controller, thereby completely eliminating the need for a dedicated in-vehicle cockpit controller. This not only significantly reduces the overall vehicle hardware cost but also effectively avoids the overlap of computing power and waste of resources between the mobile terminal and the vehicle-mounted controller.

[0015] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0016] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a block diagram of a cockpit control system provided according to an embodiment of this application; Figure 2 This is an exemplary interface diagram of a cockpit control application on a mobile terminal provided according to an embodiment of this application; Figure 3 This is a block diagram of the overall architecture of the cockpit control system provided according to an embodiment of this application; Figure 4 This is a flowchart of a cockpit control method according to an embodiment of this application; Figure 5 This is an overall flowchart of a cockpit control method according to an embodiment of this application; Figure 6 This is a timing diagram of the instruction interaction between the vehicle terminal and the mobile terminal according to an embodiment of this application. Detailed Implementation

[0017] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0018] The cockpit control system and method of this application are described below with reference to the accompanying drawings. To address the problems mentioned in the background section, this application provides a cockpit control system in which a mobile terminal, by reusing its own computing power and display resources, takes over the graphics rendering, interactive processing, and control logic originally handled by a dedicated vehicle controller. This completely eliminates the need for a dedicated in-vehicle cockpit controller, significantly reducing the overall vehicle hardware cost and effectively avoiding computing power overlap and resource waste between the mobile terminal and the vehicle controller.

[0019] Specifically, Figure 1This is a block diagram of the cockpit control system according to an embodiment of this application.

[0020] like Figure 1 As shown, the cockpit control system includes: a mobile terminal 100, a vehicle terminal 200, a communication processing module 201, and cockpit hardware devices 202.

[0021] The mobile terminal 100 is equipped with a cockpit control application, which provides a graphical user interface (GUI) and generates cockpit control commands based on the user's input on the GUI. The communication processing module 201 establishes a communication connection with the mobile terminal 100 via wireless communication. The communication processing module 201 is configured to: after completing two-way authentication with the mobile terminal 100, transfer control of the vehicle cockpit to the mobile terminal 100 in response to a takeover request from the mobile terminal 100; receive cockpit control commands sent by the mobile terminal 100 and convert the cockpit control commands into control signals; and the cockpit hardware device 202 is used to execute corresponding cockpit control operations in response to the control signals.

[0022] It is understood that in this application embodiment, the mobile terminal 100 (such as a smartphone) serves as the main control unit, and a cockpit control application is pre-installed or running internally. This application provides a visual graphical user interface, allowing users to input operation commands through interactive methods such as touch, thereby generating specific cockpit control commands. The interface is as follows: Figure 2 As shown, the communication processing module 201 is deployed on the vehicle end 200 and establishes a stable communication connection with the mobile terminal 100 via wireless communication. This module is configured to execute strict security logic: after completing two-way authentication with the mobile terminal 100 to ensure connection security, it responds to the takeover request initiated by the mobile terminal 100 and formally transfers control of the vehicle cockpit to the mobile terminal 100. Subsequently, the communication processing module 201 is responsible for receiving cockpit control commands sent by the mobile terminal 100, parsing them, and converting them into control signals that can be recognized by the cockpit hardware devices 202, driving the cockpit hardware devices 202 (such as air conditioning, seats, windows, etc.) to perform corresponding adjustment operations, thereby realizing the control of the vehicle cockpit using the mobile terminal 100.

[0023] Through the above architecture, the mobile terminal 100 of this application takes over the graphics rendering, interaction processing and control logic originally undertaken by the vehicle-mounted dedicated controller by reusing its own computing power and display resources, thereby completely eliminating the dedicated cockpit controller in the vehicle. This not only significantly reduces the hardware cost of the whole vehicle, but also effectively avoids the overlap of computing power and waste of resources between the mobile terminal 100 and the vehicle-mounted controller.

[0024] In this embodiment, the cockpit hardware device 202 includes, but is not limited to, an instrument panel display, a central control display, an audio system, an air conditioning system, a seat adjustment module, a window control module, and ambient lighting. In this embodiment, the cockpit hardware device 202, as the controlled object, is no longer connected to a central cockpit controller, but instead communicates directly with the communication processing module 201. By reusing the mobile terminal 100 to replace the traditional central cockpit controller, this application completely eliminates the need for a dedicated in-vehicle cockpit controller. The cockpit hardware device 202 only needs to respond to the underlying control signals converted by the communication processing module 201, effectively avoiding the overlap of computing power and resource waste between the mobile terminal 100 and the vehicle controller.

[0025] In this embodiment, the mobile terminal 100 is equipped with a dedicated cockpit control application. Once the mobile terminal 100 establishes a communication connection with the vehicle, the cockpit control application automatically starts and presents a control interface to the user. This control interface visually simulates the user interface (UI) of a traditional cockpit controller and supports user customization according to personal preferences.

[0026] During system operation, the cockpit control application performs the core functions of a traditional vehicle controller, specifically including: providing a complete graphical user interface, handling complex user interaction logic, and directly running in-vehicle applications such as navigation and music on the mobile terminal 100. Simultaneously, the application is responsible for translating user operations into final control commands and sending them to the communication processing module 201 of the vehicle terminal 200 via near-field communication.

[0027] In one embodiment of this application, to ensure the stability and low latency of control command transmission, the communication connection between the communication processing module 201 and the mobile terminal 100 supports multiple mainstream short-range wireless communication protocols. Specifically, the communication processing module 201 is configured to establish a communication link with the mobile terminal 100 via at least one of Bluetooth, ultra-wideband, or near-field communication protocols. For example, Bluetooth technology can be used to achieve universal data transmission and command interaction; ultra-wideband technology can be used to achieve high-precision distance detection and ranging, enhancing the reliability of identity authentication; or near-field communication technology can be used to achieve fast and secure short-range handshake connection. This multi-protocol support connection method not only improves the system's compatibility with different mobile terminals 100, but also allows for flexible selection of the optimal communication path according to actual scenario requirements (such as distance, power consumption, and bandwidth), ensuring real-time response of cockpit control.

[0028] As one possible approach, embodiments of this application may preferably use Bluetooth 5.0 or higher or UWB, as these technologies offer low power consumption and high-precision ranging capabilities, enabling seamless entry and automatic takeover.

[0029] In one embodiment, considering that the mobile terminal 100 already possesses powerful graphics rendering capabilities and computing power, the communication processing module 201 of the vehicle terminal 200 features a targeted lightweight design in its hardware selection. Specifically, the communication processing module 201 employs a lightweight gateway chip or microcontroller that does not have graphics rendering capabilities. Since the complex graphical user interface rendering and human-computer interaction logic are completely offloaded to the mobile terminal 100, the communication processing module 201 of the vehicle terminal 200 does not need to be configured with expensive high-performance graphics processing units or large-capacity memory. It only needs to be responsible for receiving instructions, protocol conversion, and signal forwarding, further reducing the hardware cost and power consumption of the vehicle terminal 200.

[0030] In one embodiment of this application, the cockpit control application of the mobile terminal 100 is configured to: load a user profile stored in the mobile terminal 100, the user profile including at least one of seat position, rearview mirror angle, air conditioning preference, and application layout; configure the operating parameters of the cockpit hardware device 202 according to the user profile, thereby realizing personalized cockpit settings. Since the user's personalized preference data is stored in the mobile terminal 100 carried by the user, when the user takes the vehicle with the mobile terminal 100 and takes over the vehicle, the system can automatically load the configuration and send it to the cockpit hardware. This not only eliminates the tedious manual adjustment process for different drivers and greatly improves the personalized cockpit experience, but also eliminates the need for the vehicle terminal 200 to allocate storage space for each user to save personalized data, further reducing the storage pressure and resource redundancy of the vehicle terminal 200.

[0031] According to the cockpit control system proposed in the embodiments of this application, the mobile terminal takes over the graphics rendering, interactive processing and control logic originally undertaken by the vehicle-mounted dedicated controller by reusing its own computing power and display resources, thereby completely eliminating the vehicle-mounted dedicated cockpit controller. This not only significantly reduces the hardware cost of the whole vehicle, but also effectively avoids the overlap of computing power and waste of resources between the mobile terminal and the vehicle-mounted controller.

[0032] As one possible way to achieve this, such as Figure 3 As shown, the specific hardware configuration of the cockpit control system in this embodiment is as follows: For mobile terminals (taking smartphones as an example), the hardware needs to have Bluetooth 5.0 or higher or a UWB (Ultra-Wideband) chip, and its computing power, memory, and graphics processing capabilities must fully meet the cockpit control requirements. Regarding the software, the mobile terminal has a dedicated cockpit control application (such as "Vehicle Cockpit") installed. This application can be downloaded from an app store and is initially bound to the vehicle's VIN code.

[0033] On the vehicle side, the hardware mainly includes a near-field communication and positioning module, a communication processing module, and a cluster of cockpit hardware modules. The core chip of the near-field communication and positioning module can be a composite chip integrating Bluetooth 5.2 and UWB (such as NXP's Trimension™ series). At least two of these modules are deployed in locations such as the B-pillar and in front of the center console to accurately determine the mobile terminal's position inside the vehicle using triangulation (e.g., distinguishing between the driver's and passenger's seats). Functionally, Bluetooth handles initial broadcasting, discovery, and low-power connection; UWB is activated after connection is established for high-precision ranging (accuracy up to 10 cm) and high-speed data transmission, ensuring that critical control is only transferred when the mobile terminal is confirmed to be inside the vehicle.

[0034] The core chip of the communication processing module uses a low-cost, automotive-grade microcontroller (MCU, such as the ARM Cortex-M series), rather than a high-performance cockpit SoC (such as the Qualcomm 8155). This MCU does not need to run a complex operating system, but only a lightweight real-time operating system (RTOS). Its core responsibilities include: protocol bridging, i.e., embedding protocol conversion software to convert JSON or Protocol Buffers format commands sent wirelessly by the mobile terminal into vehicle CAN FD (or traditional CAN), LIN, or automotive Ethernet messages; command routing, i.e., routing messages to the corresponding bus according to the target address in the command (such as target: "ac_unit"); and status collection, i.e., periodically reading the cockpit hardware status from each bus, packaging it, and sending it back to the mobile terminal.

[0035] The cockpit hardware module cluster includes devices such as displays, air conditioning, audio, seats, doors and windows, and lights. These hardware components remain unchanged, but their control logic is altered. They no longer accept direct commands from the traditional cockpit domain controller, but instead listen to the vehicle bus and wait for commands forwarded from the communication processing module.

[0036] Next, referring to the accompanying drawings, a cockpit control method according to an embodiment of this application is described, which is applied to the cockpit control system of the above embodiment.

[0037] Figure 4 This is a schematic flowchart of a cockpit control method provided in an embodiment of this application.

[0038] like Figure 4 As shown, the cockpit control method includes the following steps: In step S101, a communication connection is established between the mobile terminal and the communication processing module of the vehicle.

[0039] In one embodiment of this application, establishing a communication connection between a mobile terminal and a vehicle-side communication processing module includes: entering a target listening mode when the vehicle is in a preset state; and establishing a connection between the communication processing module and the mobile terminal when the mobile terminal is detected to have entered a preset distance range in the target listening mode.

[0040] The preset state can be either engine off or vehicle locked, and the preset distance range can be set to 5-10 meters without any specific limitation.

[0041] Understandably, when the vehicle is off or locked, the vehicle's communication processing module automatically enters target monitoring mode to reduce power consumption and wait for device access. In this target monitoring mode, when an authorized mobile terminal is detected to be within approximately 5-10 meters, the communication processing module actively establishes a wireless communication connection with the mobile terminal, achieving a seamless connection when the user approaches the vehicle.

[0042] In step S102, after the communication processing module completes two-way authentication with the mobile terminal, it transfers control of the vehicle cabin to the mobile terminal in response to the takeover request from the mobile terminal.

[0043] like Figure 5 As shown, when the car owner enters a range of approximately 5-10 meters with their mobile phone, the mobile terminal's Bluetooth and the vehicle's Bluetooth need to perform a handshake verification. This two-way authentication ensures that only authorized users can obtain vehicle control, thus guaranteeing vehicle security. After successful authentication, the vehicle officially transfers cockpit control permissions to the mobile terminal. At this point, the cockpit control application on the mobile terminal completely takes over the cockpit's interaction and control logic.

[0044] In practice, the authentication process between the mobile terminal and the vehicle is divided into two stages: initial binding and subsequent use. During the initial binding stage, the system prompts the user to enter vehicle information in the mobile terminal's cockpit control application, or to complete two-way authentication by scanning a QR code displayed on the vehicle (such as the infotainment screen or B-pillar), thus establishing an initial trust relationship. During subsequent use after the initial binding, when the mobile terminal and vehicle re-establish a communication connection, the system automatically performs token authentication, requiring no further manual intervention from the user. This not only ensures absolute security during the transfer of vehicle control but also enables seamless connection and rapid takeover after the user enters the vehicle, significantly improving the smoothness of cockpit interaction.

[0045] For example, after successful authentication, the vehicle's communication processing module sends a "ready" signal to the mobile terminal (mobile app), along with a snapshot of the current cabin hardware status (such as current temperature and media volume). The mobile app is automatically activated or prompted to launch via a notification. The app loads the user's personalized profile (interface theme, seat position presets, frequently used applications, etc.). The app sends the command {"command": "take_control"} to the vehicle. After confirmation, the vehicle's controller replies with {"status": "control_granted"}. At this point, control is officially transferred.

[0046] In one embodiment of this application, to ensure absolute security of data transmission between the mobile terminal and the vehicle, the communication processing module and the mobile terminal employ a hierarchical encryption strategy during communication. Specifically, during the initial pairing phase, the communication processing module and the mobile terminal exchange keys using an asymmetric encryption algorithm (such as RSA) to securely negotiate and generate a session key, preventing the key from being stolen during transmission. In subsequent communication phases after the initial pairing, the communication processing module and the mobile terminal use a symmetric encryption algorithm (such as AES-128 / GCM) throughout the process to encrypt and verify the integrity of cockpit control commands and status feedback data. This ensures communication security while significantly reducing the computational overhead and communication latency caused by symmetric encryption and decryption, ensuring real-time response of cockpit control operations.

[0047] In step S103, the mobile terminal generates cockpit control commands based on the operation commands entered by the user on the graphical user interface of the cockpit control application, and sends them to the communication processing module.

[0048] It is understood that the mobile terminal in this application embodiment uses its own computing power to complete the rendering of the graphical interface and the processing of user interaction logic, converts the user's touch or voice operation into structured cockpit control commands in real time, and stably sends them to the communication processing module at the vehicle end through the established wireless communication link.

[0049] In step S104, the cockpit control command is converted into a control signal suitable for the vehicle bus by the communication processing module, and then sent to the corresponding cockpit hardware device via the vehicle bus. The cockpit hardware device executes the corresponding cockpit control operation in response to the control signal.

[0050] In one embodiment of this application, converting cockpit control commands into control signals suitable for vehicle bus includes: parsing cockpit control commands to obtain a data packet containing a target device identifier and operating parameters; converting the data packet into a corresponding bus message based on the target device identifier; and distributing the bus message to the corresponding cockpit hardware device via the target bus.

[0051] It is understood that the communication processing module in this application embodiment first parses the received cockpit control command, extracts the data packet containing the target device identifier and operation parameters, maps and converts the data packet into a bus message conforming to the vehicle bus protocol (such as CAN bus or LIN bus) according to the target device identifier, and accurately distributes the bus message to the corresponding cockpit hardware device through the target bus, so that the lightweight communication processing module can efficiently bridge the mobile terminal and the vehicle underlying hardware.

[0052] In one embodiment of this application, the cockpit control method further includes: collecting status information after the cockpit hardware device performs cockpit control operations; encapsulating the status information into a data packet and sending it to a mobile terminal, so that the mobile terminal matches the corresponding cockpit control command according to the sequence number in the data packet and updates the graphical user interface to display the status information.

[0053] In this embodiment, the vehicle-side data acquisition process collects real-time status information of the cockpit hardware after performing cockpit control operations, and encapsulates this status information into a data packet, which is then sent to the mobile terminal. Upon receiving the data packet, the mobile terminal matches the corresponding cockpit control command based on the sequence number within it and synchronously updates the graphical user interface to display the latest device status. This ensures consistency between the vehicle status displayed on the mobile terminal and the actual physical status, avoiding interface lag or status asynchrony caused by communication delays.

[0054] In one embodiment of this application, taking the adjustment of air conditioning temperature as an example, such as... Figure 6 As shown, the specific command interaction process is as follows: (1) Command generation and transmission: After the user performs an operation on the graphical user interface of the cockpit control application on the mobile terminal (for example, lowering the air conditioning temperature from 23°C to 22°C), the cockpit control application will generate a command packet (such as JSON format) containing structured information such as serial number (seq_id), timestamp, target device identifier (such as hvac), operation action and target parameters. This command packet is sent to the communication processing module on the vehicle end through the established wireless communication link (such as UWB high-speed data channel).

[0055] (2) Command parsing and forwarding: The vehicle-side communication processing module receives the command packet, parses it, and identifies the target device and specific operation. Subsequently, the protocol conversion logic in the communication processing module converts the command into a standard bus message (such as a CAN FD message) that conforms to the vehicle's underlying communication protocol. This message contains the address of the target hardware device and specific control data, and is broadcast to the vehicle bus through the vehicle bus driver.

[0056] (3) Hardware Execution and Status Feedback: After listening to the messages on the vehicle bus, the corresponding cabin hardware devices (such as the air conditioning control unit) identify the control commands belonging to themselves and then drive the corresponding actuators (such as dampers, compressors, etc.) to perform cabin control operations. After the operation is completed, the cabin hardware devices send the current actual operating status (such as the actual temperature) to the vehicle bus in the form of a status message. The communication processing module continuously listens to the bus and captures the status message, re-encapsulates it into a data packet containing the serial number, status type and actual value, and transmits it back to the mobile terminal via a wireless link.

[0057] (4) Interface update and interaction loop: After receiving the feedback data packet, the cockpit control application of the mobile terminal matches the previously issued cockpit control command according to the sequence number (seq_id) in the data packet, and synchronously updates the display content of the graphical user interface (for example, updating the current temperature display to 22.5°C). At this point, a complete cockpit control interaction loop is completed.

[0058] In one embodiment of this application, the cockpit control method further includes: when multiple authorized mobile terminals are present in the vehicle, granting control to the mobile terminal located in the driver's seat.

[0059] Understandably, when multiple authorized mobile terminals are present in the vehicle at the same time, the control of the cockpit will be given priority to the mobile terminal located in the driver's seat based on the location information of the mobile terminals. This ensures that when multiple people bring their devices into the vehicle at the same time, the ownership of vehicle control is clear, avoiding control conflicts caused by multiple terminals issuing commands at the same time, and ensuring driving safety.

[0060] In one embodiment of this application, when the vehicle's speed exceeds a preset threshold, voice control and shortcut button operations are retained while other operations are disabled; the connection status between the mobile terminal and the communication processing module is monitored, and when the wireless connection is disconnected for more than a preset duration, control of the mobile terminal is reclaimed.

[0061] The preset threshold and preset duration can be set according to the actual situation. For example, the preset threshold can be set to 10 km / h and the preset duration can be set to 3 seconds, without any specific limitation.

[0062] Understandably, when the vehicle speed exceeds 10 km / h, the mobile terminal's cockpit control application will automatically restrict operational permissions, retaining only voice control and shortcut button operations, and disabling other complex graphical interactions to prevent driver distraction. Simultaneously, it continuously monitors the wireless connection status between the mobile terminal and the communication processing module. If the wireless connection is lost for more than 3 seconds, it will automatically reclaim control of the mobile terminal and return cockpit control to the vehicle's default safety policy, ensuring that the vehicle cockpit remains safe and controllable even in the event of communication failure.

[0063] Furthermore, in this embodiment, safety-related signals (turn signals, brake lights) are processed entirely by the vehicle's underlying network and do not pass through mobile terminals.

[0064] In one embodiment of this application, to ensure driving safety under extreme conditions, the cockpit control system also incorporates a redundancy backup mechanism. Specifically, the vehicle retains a minimalist physical control panel with physical buttons for safety-related functions such as hazard lights, front defroster, and central locking, ensuring that users can still physically operate critical safety functions even if the mobile terminal fails. Simultaneously, a set of default control logic is pre-configured in the communication processing module. When the mobile terminal fails to connect or malfunctions, this default control logic is activated, ensuring that the vehicle's basic driving functions and core safety controls remain unaffected, thus improving the reliability and safety of the entire cockpit control system.

[0065] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0066] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0067] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0068] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0069] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0070] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A cockpit control system, characterized in that, include: A mobile terminal, wherein the mobile terminal is equipped with the cockpit control application, the cockpit control application provides a graphical user interface, and generates cockpit control commands based on the operation commands input by the user on the graphical user interface; The communication processing module and cockpit hardware are located in the vehicle, among which, The communication processing module establishes a communication connection with the mobile terminal via wireless communication. The communication processing module is configured to: after completing two-way authentication with the mobile terminal, in response to a takeover request from the mobile terminal, transfer control of the vehicle cabin to the mobile terminal. Receive the cockpit control command sent by the mobile terminal, and convert the cockpit control command into a control signal; The cockpit hardware is used to execute corresponding cockpit control operations in response to the control signals.

2. The cockpit control system according to claim 1, characterized in that, The communication processing module establishes a communication connection with the mobile terminal via at least one of Bluetooth, ultra-wideband, or near-field communication protocols.

3. The cockpit control system according to claim 1, characterized in that, The communication processing module is a lightweight gateway chip or microcontroller that does not have graphics rendering capabilities.

4. The cockpit control system according to claim 1, characterized in that, The cockpit control application of the mobile terminal is configured to: load a user profile stored in the mobile terminal, the user profile including at least one of seat position, rearview mirror angle, air conditioning preference and application layout, and configure the operating parameters of the cockpit hardware device according to the user profile.

5. A cockpit control method, characterized in that, The cockpit control system applied to any one of claims 1-4 includes the following steps: Establish a communication connection between the mobile terminal and the vehicle's communication processing module; After the communication processing module completes two-way authentication with the mobile terminal, it transfers control of the vehicle cabin to the mobile terminal in response to a takeover request from the mobile terminal. The mobile terminal generates cockpit control commands based on the user's input on the graphical user interface of the cockpit control application, and sends them to the communication processing module. The communication processing module converts the cockpit control commands into control signals suitable for the vehicle bus and sends them to the corresponding cockpit hardware devices via the vehicle bus. The cockpit hardware devices then perform corresponding cockpit control operations in response to the control signals.

6. The cockpit control method according to claim 5, characterized in that, Converting the cockpit control commands into control signals suitable for the vehicle bus includes: Parse the cockpit control commands to obtain a data packet containing the target device identifier and operating parameters; Based on the target device identifier, the data packet is converted into a corresponding bus message; The bus message is distributed to the corresponding cockpit hardware device via the target bus.

7. The cockpit control method according to claim 5, characterized in that, Also includes: Collect status information of the cockpit hardware devices after they perform the cockpit control operations; The status information is encapsulated into a data packet and sent to the mobile terminal, so that the mobile terminal matches the corresponding cockpit control command according to the serial number in the data packet and updates the graphical user interface to display the status information.

8. The cockpit control method according to claim 5, characterized in that, Also includes: When multiple authorized mobile terminals are present in the vehicle, control is granted to the mobile terminal located in the driver's seat.

9. The cockpit control method according to claim 5, characterized in that, Establishing a communication connection between the mobile terminal and the vehicle's communication processing module includes: When the vehicle is in a preset state, it enters the target detection mode; In the target listening mode, when the mobile terminal is detected to have entered a preset distance range, the communication processing module establishes a connection with the mobile terminal.

10. The cockpit control method according to claim 5, characterized in that, Also includes: When the vehicle speed exceeds a preset threshold, retain voice control and shortcut button operations, and disable other operations; The connection status between the mobile terminal and the communication processing module is monitored, and control of the mobile terminal is reclaimed when the wireless connection is disconnected for more than a preset time.