Cockpit function triggering method, vehicle system, and vehicle

Abstract

The present application relates to the field of intelligent vehicle technology, and in particular, to a cockpit function triggering method, a vehicle system, and a vehicle. The cockpit function triggering method of the present application, applied to the vehicle system, needs to first detect the physical button that has been triggered and generate corresponding key event data; then, based on the monitoring of the key event data, send the key event data to the corresponding target application processing component; further, parse the key event data based on the target application processing component to determine the target operation; further, execute the target operation to trigger the cockpit function that matches the key event data. In this way, under the condition of limited buttons in the cockpit, the functions triggered by the buttons can be diversified, and the failure of the function buttons can be reduced in the process of coupling with the vehicle application.

Description

Technical Field

[0001] The present application relates to the field of intelligent vehicle technology, and in particular to a cockpit function triggering method, a vehicle system, and a vehicle. Background Art

[0002] With the continuous development of smart vehicles, the interior of the vehicle is becoming more and more intelligent. Many functions are realized through soft switches. However, when the driver wants to turn on or adjust related functions during driving, if the soft switch is clicked from the central control, it will affect driving safety. In addition, the rear passengers are also limited to the riding position, and it is difficult to control the relevant functions in the cockpit through the front central control. Therefore, physical buttons need to be set inside the cockpit to facilitate the driver and other passengers to control the applications on the vehicle.

[0003] In the related art, due to the limited number of buttons that can be set in the cockpit, in order to ensure the passenger experience, some buttons will be reused. When the buttons are reused, the reused functions need to be coupled with the application of the vehicle computer, and often the application cannot be started, resulting in the failure of the function button. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a cockpit function triggering method, a vehicle system, and a vehicle, which can diversify the functions triggered by buttons under the condition of limited buttons in the cockpit, and reduce the occurrence of failures of function buttons during the coupling process with vehicle application programs.

[0005] According to the cockpit function triggering method of the first aspect of the present application, applied to a vehicle system, the method includes:

[0006] Detect the physical keys that have been triggered and generate corresponding key event data;

[0007] Based on monitoring the key event data, sending the key event data to a corresponding target application processing component;

[0008] Parsing the key event data based on the target application processing component to determine a target operation;

[0009] The target operation is executed to trigger a cockpit function matching the key event data.

[0010] According to some embodiments of the present application, sending the key event data to a corresponding target application processing component based on monitoring the key event data includes:

[0011] In the case where the target application processing component is in a foreground running state, injecting the key event data into a native event distribution process;

[0012] Based on monitoring of the key event data, the key event data is distributed to the corresponding target application processing component through the native event distribution process.

[0013] According to some embodiments of the present application, the step of distributing the key event data to the corresponding target application processing component through the native event distribution process based on monitoring the key event data includes:

[0014] Distributing the key event data to the corresponding target application processing component through the native event distribution process;

[0015] Based on monitoring the key event data, obtaining the operation status corresponding to the key event data from the native event distribution process;

[0016] When the operation state is a consumed state, the corresponding key event data is intercepted.

[0017] According to some embodiments of the present application, the sending the key event data to the corresponding target application processing component based on the monitoring of the key event data further includes:

[0018] When the target application processing component is in a background running state, based on the key event data, determining the target application processing component that has pre-registered key monitoring for the key event data;

[0019] The key event data is called back to the target application processing component that has been pre-registered for key monitoring.

[0020] According to some embodiments of the present application, calling back the key event data to the target application processing component that has pre-registered key monitoring includes:

[0021] Determining the target application processing component that has been pre-registered for key monitoring from a preset key monitoring list;

[0022] Based on the callback function matched to the key listening registration, the key event data is distributed to the target application processing component that has pre-registered the key listening.

[0023] According to some embodiments of the present application, sending the key event data to a corresponding target application processing component based on monitoring the key event data includes:

[0024] Encapsulating the key event data in a standard format to obtain the key event data in a standard format;

[0025] Based on monitoring the key event data in a standard format, the key event data in a standard format is sent to a corresponding target application processing component.

[0026] According to some embodiments of the present application, the target operation list includes a plurality of the target operations, and the plurality of the target operations are executed in a corresponding list order of the target operation list. After the target application processing component is used to parse the key event data and determine the target operation, the following further includes:

[0027] Querying the target operation matching the operation shielding condition from the target operation list;

[0028] For the target operation matching the operation shielding condition, the operation state corresponding to the target operation is set to a consumed state.

[0029] According to some embodiments of the present application, before parsing the key event data based on the target application processing component to determine the target operation, the method further includes:

[0030] generating an application status signal according to an application status corresponding to the target application processing component;

[0031] In the vehicle system, real-time broadcasting of the application status signal is performed;

[0032] After parsing the key event data based on the target application processing component to determine the target operation, the method further includes:

[0033] Based on the application status signal broadcast in real time, the shielding status of the target application processing component at the current moment is determined, and a corresponding status response operation is performed.

[0034] According to some embodiments of the present application, determining the shielding state of the target application processing component at the current moment based on the application state signal broadcast in real time, and performing a corresponding state response operation includes:

[0035] When the application status signal broadcast in real time reflects that the target application processing component is in an application shielding state at the current moment, the target operation matching the target application processing component is intercepted.

[0036] According to some embodiments of the present application, after intercepting the target operation matched to the target application processing component, the method further includes:

[0037] When the time for which the target application processing component is in the application shielding state exceeds a preset time threshold, the application state of the target application processing component is reset from the application shielding state to the application running state.

[0038] According to the second aspect of the present application, a vehicle system includes:

[0039] A key detection module is used to detect physical keys that have been triggered and generate corresponding key event data;

[0040] A data distribution module, configured to send the key event data to a corresponding target application processing component based on monitoring of the key event data;

[0041] An application layer module, configured to parse the key event data based on the target application processing component and determine a target operation;

[0042] A function execution module is used to execute the target operation to trigger a cockpit function matching the key event data.

[0043] A vehicle according to a third aspect of the present application includes:

[0044] The vehicle stores a program, and the program is executed to implement the cockpit function triggering method as described in any one of the embodiments of the first aspect of the present application, and the vehicle is equipped with the vehicle system as described in the embodiments of the second aspect of the present application.

[0045] The cockpit function triggering method, vehicle system, and vehicle according to the embodiments of the present application have at least the following beneficial effects:

[0046] The cockpit function triggering method of the present application is applied to the vehicle system, and needs to first detect the physical button that has been triggered and generate the corresponding key event data; then based on the monitoring of the key event data, send the key event data to the corresponding target application processing component; further, parse the key event data based on the target application processing component to determine the target operation; further, execute the target operation to trigger the cockpit function that matches the key event data. In this way, under the condition of limited buttons in the cockpit, the functions triggered by the buttons can be diversified, and the failure of the function buttons in the process of coupling with the vehicle application can be reduced.

[0047] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0049] Figure 1 A flowchart of a cockpit function triggering method provided in an embodiment of the present application;

[0050] Figure 2 Another schematic diagram of a flow chart of a cockpit function triggering method provided in an embodiment of the present application;

[0051] Figure 3 Another schematic diagram of a flow chart of a cockpit function triggering method provided in an embodiment of the present application;

[0052] Figure 4 Another schematic diagram of a flow chart of a cockpit function triggering method provided in an embodiment of the present application;

[0053] Figure 5 Another schematic diagram of a flow chart of a cockpit function triggering method provided in an embodiment of the present application;

[0054] Figure 6 Another schematic diagram of a flow chart of a cockpit function triggering method provided in an embodiment of the present application;

[0055] Figure 7 Another schematic diagram of a flow chart of a cockpit function triggering method provided in an embodiment of the present application;

[0056] Figure 8 Another schematic diagram of a flow chart of a cockpit function triggering method provided in an embodiment of the present application;

[0057] Fig. 9 is a structural diagram of a vehicle system provided in an embodiment of the present application;

[0058] Fig.10 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0059] The present application is further described in detail. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present application. They are only examples of devices / equipment and methods consistent with some aspects of the embodiments of the present application as detailed in the attached claims.

[0060] It is understood that the terms "first", "second", etc. used in this application can be used to describe various concepts in this article, but unless otherwise specified, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another concept. For example, without departing from the scope of the embodiment of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination".

[0061] The terms "at least one", "multiple", "each", "any", etc. used in this application, at least one includes one, two or more, multiple includes two or more, each refers to each of the corresponding multiple, and any refers to any one of the multiple.

[0062] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0063] With the continuous development of smart vehicles, the interior of the vehicle is becoming more and more intelligent. Many functions are realized through soft switches. However, when the driver wants to turn on or adjust related functions during driving, if the soft switch is clicked from the central control, it will affect driving safety. In addition, the rear passengers are also limited to the riding position, and it is difficult to control the relevant functions in the cockpit through the front central control. Therefore, physical buttons need to be set inside the cockpit to facilitate the driver and other passengers to control the applications on the vehicle.

[0064] For drivers, they can use physical buttons on the multi-function steering wheel to call up related applications, control many electronic devices on the vehicle, and clearly see the scenery ahead, which improves driving safety. The multi-function steering wheel can not only realize basic directional control functions, but also integrate more practical functions, such as voice control, navigation, intelligent driving assistance, making and receiving calls, etc. The addition of these functions has led to a growing demand for multi-function steering wheels. People have more and more requirements for vehicle driving experience, hoping to be able to easily control the vehicle while enjoying more convenience and safety.

[0065] For passengers, they can find corresponding physical buttons on the armrests, seats, etc., so as to make full use of the various applications or electronic devices equipped in the vehicle.

[0066] In the related art, due to the limited number of buttons that can be set in the cockpit, in order to ensure the passenger experience, some buttons will be reused. When the buttons are reused, the reused functions need to be coupled with the application of the vehicle computer, and often the application cannot be started, resulting in the failure of the function button.

[0067] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a cockpit function triggering method, a vehicle system, and a vehicle, which can diversify the functions triggered by buttons under the condition of limited buttons in the cockpit, and reduce the occurrence of failures of function buttons during the coupling process with vehicle application programs.

[0068] The cockpit function triggering method provided in the embodiment of the present application can be applied to a terminal or a server, and can also be software running in a terminal or a server. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and a vehicle-mounted terminal, etc., but is not limited thereto; the server side can be configured as an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The server can also be a node server in a blockchain network; the software can be an application that implements the method, etc., but is not limited to the above forms.

[0069] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0070] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0071] Reference Figure 1 According to the cockpit function triggering method provided in the embodiment of the present application, which is applied to a vehicle system, the cockpit function triggering method may include:

[0072] Step S101, detecting a physical key that has been triggered and generating corresponding key event data;

[0073] Step S102, based on monitoring the key event data, sending the key event data to the corresponding target application processing component;

[0074] Step S103, analyzing the key event data based on the target application processing component to determine the target operation;

[0075] Step S104, executing the target operation to trigger the cockpit function matching the key event data.

[0076] The cockpit function triggering method of the present application is applied to the vehicle system. It is necessary to first detect the physical button that has been triggered and generate the corresponding key event data; then based on the monitoring of the key event data, send the key event data to the corresponding target application processing component; further, parse the key event data based on the target application processing component to determine the target operation; further, execute the target operation to trigger the cockpit function that matches the key event data. In this way, under the condition of limited buttons in the cockpit, the functions triggered by the buttons can be diversified, and the failure of the function buttons in the process of coupling with the vehicle application can be reduced.

[0077] In step S101 of some embodiments, the physical buttons that have been triggered are detected, and corresponding key event data is generated. It should be noted that, due to the limited number of buttons that can be set in the cabin, the embodiments of the present application will reuse the functions of some buttons in order to ensure the passenger experience. Based on this, in order to determine which physical buttons have been triggered, the embodiments of the present application need to detect the physical buttons, so as to generate corresponding key event data based on the physical buttons that have been triggered. It should be pointed out that since a physical button needs to reuse multiple functions, the physical button can be mapped to the corresponding function by detecting the triggering method of the physical button.

[0078] In some more specific embodiments, when the physical button has only a single function and no function multiplexing, pressing the physical button is triggered and a corresponding trigger action is generated; when the physical button includes a short press or long press function, the timing starts after the physical button is pressed. If the long press time is not reached, the short press action is responded to; if the timing reaches the long press time, the long press action is responded to.

[0079] It should be understood that there are various embodiments for detecting a triggered physical key and generating corresponding key event data, which may include, but are not limited to, the above examples.

[0080] In step S102 of some embodiments, based on the monitoring of key event data, the key event data is sent to the corresponding target application processing component. It should be noted that in the related art, when the key is reused in function, the reused function needs to be coupled with the application of the vehicle computer, and there is often a situation where the application cannot be started, resulting in the failure of the function key. Based on this, the embodiment of the present application can send the key event data to the corresponding target application processing component based on the monitoring of the key event data. It should be noted that in the software architecture, the target application processing component generally refers to a software module designed and implemented specifically for processing specific functions or tasks. In the context of the vehicle system, these components generally interact with the user interface, hardware devices or other applications to provide specific services or functions. The target application processing component can be used to respond to user input (such as by clicking on the steering wheel button), process business logic and interact with other parts of the system (such as services, hardware interfaces, user interfaces, etc.) to complete specific tasks or functions.

[0081] In this way, the embodiment of the present application can send different key event data to the corresponding target application processing component according to the functional requirements. It should be pointed out that the application of the monitoring mechanism can make some applications start the corresponding application only when a specific state or condition is detected (such as the user pressing the reused key). By realizing functional reuse in this way, the system service can be actively pulled up through the background for applications that cannot be started automatically at boot and survive in the background without occupying system resources.

[0082] Reference Figure 2 According to some embodiments of the present application, step S102 sends the key event data to the corresponding target application processing component based on monitoring the key event data, which may include:

[0083] Step S201, when the target application processing component is in the foreground running state, injecting key event data into the native event distribution process;

[0084] Step S202: Based on the monitoring of the key event data, the key event data is distributed to the corresponding target application processing component through the native event distribution process.

[0085] In steps S201 to S202 of some embodiments, when the target application processing component is in the foreground running state, the key event data is injected into the native event distribution process, and based on the monitoring of the key event data, the key event data is distributed to the corresponding target application processing component through the native event distribution process. It should be noted that when the target application processing component is in the foreground, the key event data generated by the triggering of the physical key can be monitored through the system native interface. Furthermore, when the target application processing component is in the foreground running state, the key event data is injected into the native event distribution process, and the injected key event data will be processed according to the native event distribution logic of the system, so that the key event data is injected into the native event distribution process through the native logic. In this way, the monitoring of the key event data can be achieved when the target application processing component is in the foreground.

[0086] In some more specific embodiments, key event data can be injected through InputManager. It should be clear that InputManager#injectInputEvent is a method that allows the system to inject key event data into the event distribution system. Through InputManager#injectInputEvent, the injected key event data will be processed according to the system's native event distribution logic, so that the key event data will be injected into the native event distribution process through the native logic, and then distributed in WindowManagerService. Among them, WindowManagerService is the service responsible for window management in the Android system, and it will participate in the distribution of key event data.

[0087] Furthermore, the target application processing component deployed in the application layer module can monitor and process key event data by overriding onKeyDown, onKeyUp and dispatchKeyEvent methods in Activity. It should be noted that in Android application development, Activity is a key component used to define the user interface and process user interaction events.

[0088] Reference Figure 3 According to some embodiments of the present application, step S202 distributes the key event data to the corresponding target application processing component through the native event distribution process based on monitoring the key event data, which may include:

[0089] Step S301, distribute the key event data to the corresponding target application processing component through the native event distribution process;

[0090] Step S302, based on monitoring the key event data, obtaining the operation state corresponding to the key event data from the native event distribution process;

[0091] Step S303: when the operation state is the consumed state, the corresponding key event data is intercepted.

[0092] In some embodiments, steps S301 to S303 distribute key event data to corresponding target application processing components through a native event distribution process; based on monitoring the key event data, obtain the operation status corresponding to the key event data from the native event distribution process; when the operation status is a consumed state, intercept the corresponding key event data. In this way, the key event data can be filtered before being further transmitted, which can be used to intercept specific key operations, such as preventing users from pressing certain keys that should not be used in the current context. When the operation status is a consumed state, the corresponding key event data is intercepted, which can also avoid the execution of unnecessary event processing code, thereby saving system resources.

[0093] In some more specific embodiments, when a user interacts with an application by key operation, the key event data is distributed to the corresponding target application processing component, and the Activity can override the following three methods to monitor and process the key event data:

[0094] onKeyDown(int keyCode,KeyEvent event): This method is called when the user presses a key. It provides the key code (keyCode), which identifies the specific key that was pressed. The KeyEvent object contains detailed information about the key event data, such as the action (pressed or released), key code, repeat count (if the key was pressed for a long time), etc.

[0095] onKeyUp(int keyCode, KeyEvent event): This method is called when the user releases a key. Similar to onKeyDown, it also provides the key code and KeyEvent object. Typically, onKeyUp is used to confirm the end of a key operation, and can be used to perform some cleanup work or ensure the integrity of a key operation.

[0096] The above keyCode is an integer representing a specific key, such as "Back", "Home", "Menu", etc.

[0097] dispatchKeyEvent(KeyEvent event): This method is the central point for Activity to distribute key event data. All key event data is first passed to the dispatchKeyEvent method. If dispatchKeyEvent returns true, it means that the event has been consumed and will not be further passed to other components such as onKeyDown or onKeyUp. If it returns false, the event will continue to be passed to onKeyDown or onKeyUp, depending on the action of the key.

[0098] It should be understood that in an Activity, the distribution of key event data may first call dispatchKeyEvent, and if it returns false, onKeyDown or onKeyUp is called according to the key action.

[0099] By returning true in these methods, the target application processing component can "consume" the key event data, which means that the event will not be passed to other components, such as View or listeners in other Activities. If all key event data processing methods return false, the default behavior of the key event data will be executed.

[0100] It should be noted that in Android, View is the base class of all user interface components and represents a drawable element on the screen. The View class provides a framework that enables the embodiments of the present application to create custom graphical interface elements. In View, these three methods can also be overridden to monitor key event data. In addition, a key listener can be added by setting setOnKeyListener(View.OnKeyListener) to receive key messages.

[0101] The target application processing component can decide how to handle key event data based on the current context, such as the screen the user is currently on or the operation being performed. By overriding these methods, you can achieve precise control over key event data, define specific key behaviors for users, enhance user experience, and make applications more responsive and flexible. In a car environment, this mechanism is especially important for driving safety, because the driver may need to control the vehicle's entertainment system, navigation, or other functions through the buttons on the steering wheel without having to distract attention from operating the touch screen.

[0102] Reference Figure 4 According to some embodiments of the present application, step S102 sends the key event data to the corresponding target application processing component based on monitoring the key event data, and further includes:

[0103] Step S401, when the target application processing component is in the background running state, based on the key event data, determining the target application processing component that has pre-registered key monitoring for the key event data;

[0104] Step S402: Call back the key event data to the target application processing component that has been pre-registered for key monitoring.

[0105] In some embodiments, steps S401 to S402, when the target application processing component is in the background running state, determine the target application processing component that has pre-registered key monitoring for the key event data based on the key event data, and call back the key event data to the target application processing component that has pre-registered key monitoring. It should be noted that when the target application processing component is in the background running state, it is impossible to rely on the system's native event distribution logic to distribute the key event data to the corresponding target application processing component. In the embodiment of the present application, it is possible to determine the target application processing component that has pre-registered key monitoring for the key event data based on the key event data, and then distribute the key event data to the corresponding target application processing component by calling back the key event data.

[0106] In some more specific embodiments, CarKeyManager is an interface provided by the Android car library (Car-lib), which allows the application layer module to register a key listener to receive key event data triggered by the physical key in the cockpit. Therefore, in an Android-based car system, the target application processing component can register a key listener through the CarKeyManager interface in Car-lib. Specifically, the target application processing component can register a KeyEventListener through the registerKeyListener method of CarKeyManager, which allows the target application processing component to specify a listener for receiving key event data. Further, the registered listener will eventually be registered in CarInputService, which is a system service responsible for processing hard key events. When the user presses a physical key in the cockpit, the key event data can first be captured in the hardware abstraction layer (HAL) and then passed to CarInputService. CarInputService calls back the key event data to CarKeyManager across processes through the IKeyListener list registered by CarKeyManager. After receiving the key event data, CarKeyManager will pass the key event data to the KeyEventListener registered by the target application processing component, so that the target application processing component can receive and process the key event data.

[0107] Reference Figure 5 According to some embodiments of the present application, step S402 calls back the key event data to the target application processing component that has pre-registered key monitoring, which may include:

[0108] Step S501, determining a target application processing component that has been pre-registered for key monitoring from a preset key monitoring list;

[0109] Step S502: based on the callback function matching the key monitoring registration, the key event data is distributed to the target application processing component that has pre-registered the key monitoring.

[0110] In step S501 of some embodiments, a target application processing component that has been pre-registered for key monitoring is determined from a preset key monitoring list. It should be noted that the target application processing component can be deployed in the application layer module of the vehicle system, and the same application layer module can deploy multiple target application processing components, where different target application processing components are used to parse different key event data to complete different tasks. Based on this, the key monitoring list is used to manage multiple target application processing components that have been pre-registered for key monitoring.

[0111] In some more specific embodiments, when CarInputService receives a key event, it searches for a list of registered IKeyListener listeners. This list contains all listeners registered by the CarKeyManager.registerKeyListener() method. It should be understood that the registered IKeyListener listener list in the above embodiment is the key listener list.

[0112] In step S502 of some embodiments, based on the callback function matching the key listening registration, the key event data is distributed to the target application processing component that has pre-registered the key listening. It should be noted that after determining the target application processing component that has pre-registered the key listening from the preset key listening list, it is necessary to distribute the key event data to the corresponding target application processing component through the callback function matching the key listening registration.

[0113] In some more specific embodiments, CarInputService will traverse this list and use a callback mechanism to notify (i.e., call) each listener. In this case, the callback refers to the method defined in the IKeyListener interface, such as onKeyEvent(). When a key event occurs, CarInputService calls the onKeyEvent() method of each listener. Since CarInputService runs in the system process, and the target application processing component may run in a different application process, this callback process involves cross-process communication. The Android operating system provides an inter-process communication (IPC) mechanism that enables system services to interact with objects in the target application processing component process. In the application process, after CarKeyManager receives a key event from CarInputService, it passes the event to the KeyEventListener previously registered by the target application processing component. In this way, the target application processing component can process the key event in its own context, for example, perform a specific operation or update the user interface.

[0114] Through the embodiment shown in step S501 to step S502, the capture and transmission of the key event data triggered by the hardware can be separated from the business logic of the target application processing component, thereby improving the modularity and maintainability of the system. The target application processing component can register or unregister the listener as needed without paying attention to how the key event data is captured and transmitted. By directly calling back to the registered listener, the delay in key event data processing is reduced and the response speed is improved.

[0115] Reference Figure 6According to some embodiments of the present application, step S102 sends the key event data to the corresponding target application processing component based on monitoring the key event data, which may include:

[0116] Step S601, encapsulating the key event data in a standard format to obtain key event data in a standard format;

[0117] Step S602: based on monitoring the key event data in the standard format, the key event data in the standard format is sent to the corresponding target application processing component.

[0118] In steps S601 to S602 of some embodiments, the key event data is packaged in a standardized format to obtain key event data in a standardized format, and based on the monitoring of the key event data in the standardized format, the key event data in the standardized format is sent to the corresponding target application processing component. It should be noted that each key event data has its own attributes or characteristics. In order to distribute various key event data, the embodiments of the present application need to package the key event data in a standardized format to obtain key event data in a standardized format. Then, based on the monitoring of the key event data in the standardized format, the key event data in the standardized format is sent to the corresponding target application processing component.

[0119] It should be noted that the canonical format encapsulation provides a standardized way to describe key event data, so that the target application processing component and the system can understand and respond to key operations in a consistent manner. The canonical format encapsulation can contain detailed information about the key event data, such as action type, key code, repeat count, etc., which is essential for correctly interpreting the user's key intention. The embodiment of the present application can flexibly design the response behavior of the target application processing component according to the information provided by the canonical format encapsulation, for example, distinguishing between short press and long press, or adjusting the operation according to the state of the modifier key. The canonical format encapsulation allows the system and the target application processing component of the present application embodiment to not care about the specific implementation of the underlying hardware, thereby simplifying the development process. Since the canonical format encapsulation is standardized, the target application processing component can be more easily run on different devices without a lot of adaptation work for specific hardware. Through the control provided by the canonical format encapsulation, the system can ensure that only legitimate key event data is passed to the target application processing component, increasing the security of the system. The target application processing component can provide instant user interface feedback, such as key sound, vibration or visual prompts, according to the canonical format encapsulation to enhance the user experience. System resource management: Standard format encapsulation helps the system manage resources more efficiently, because it can decide whether to wake up or switch the target application processing component based on the attributes of the key event data. In a multi-tasking environment, standard format encapsulation ensures that the key event data can be correctly distributed to the currently active target application processing component or components.

[0120] According to some more specific embodiments provided by this application, in the Android operating system, especially in the context of the hardware abstraction layer (HAL), "KeyProperty" generally refers to the attributes or features related to key event data, so "KeyProperty" can be used as the basis for implementing the standard format encapsulation in the embodiments of this application. These properties provide detailed information about key operations, which are usually captured by the HAL and passed to the upper system for processing. The following is the information that "KeyProperty" can include, but is not limited to:

[0121] KeyCode: The code of the specific key that was pressed. Each key (such as volume up, volume down, power key, etc.) has a unique key code corresponding to it.

[0122] Action: Indicates the action type of the button. Common actions include ACTION_DOWN (button pressed) and ACTION_UP (button released).

[0123] Flags: May contain other flags about key event data, such as whether it is a long press, whether vibration feedback is generated, etc.

[0124] Time: Records the timestamp of the key event data.

[0125] It should be understood that in the Android system, the HAL passes these KeyProperties to the InputHALService of the Java layer through a callback function, and then these properties are encapsulated into KeyEvent objects. The target application processing component or system service can respond to key operations by listening to KeyEvent. For example, the steering wheel in a car system may have multiple buttons, each of which can perform different functions, such as answering a call, adjusting the volume, activating voice commands, etc. The HAL needs to capture the properties of these buttons and pass them to the CarInputService through the InputHALService, and finally pass them to the target application processing component of interest through the CarKeyManager. In the HAL layer of Android, the specific implementation of KeyProperty may vary depending on different hardware platforms and manufacturers, but the basic principle is similar, that is, capturing the physical events of the buttons and converting them into a standard format that the software can handle.

[0126] In step S103 of some embodiments, the target application processing component analyzes the key event data to determine the target operation. It should be noted that after sending the key event data to the corresponding target application processing component, the target application processing component needs to analyze the key event data to determine the target operation.

[0127] In some more specific embodiments, the types of target application processing components are various and may include, but are not limited to, the following examples:

[0128] DVR application component. Function: Responsible for handling DVR-related operations, such as taking photos, recording emergency videos, etc. Trigger condition: When the user triggers the DVR function through the multiplexed button on the steering wheel, the component will be activated.

[0129] Phone application component. Function: handles phone connection, hang-up, dialing and other operations. Trigger condition: the user performs phone-related operations using the phone buttons on the steering wheel.

[0130] Multimedia control component. Function: Control audio playback, such as play, pause, next song, previous song, etc. Trigger condition: The user controls music playback through the multimedia control buttons on the steering wheel.

[0131] Voice recognition component. Function: Activates the voice recognition service, allowing the user to control vehicle functions through voice commands. Trigger condition: The user long presses or short presses the voice recognition button on the steering wheel.

[0132] Navigation application component. Function: Start or switch to the navigation application for route planning and navigation guidance. Trigger condition: The user quickly enters the navigation mode using the navigation button on the steering wheel.

[0133] Vehicle settings component. Function: Provides quick access to vehicle settings, such as adjusting volume, muting, etc. Trigger condition: The user enters the vehicle settings menu through the settings button on the steering wheel.

[0134] Emergency rescue component. Function: In an emergency, quickly start emergency rescue services. Trigger condition: The user long presses the emergency rescue button on the steering wheel.

[0135] Bluetooth phone component. Function: Manage Bluetooth phone connections, answer, hang up or reject calls. Trigger condition: The user operates the Bluetooth phone button on the steering wheel.

[0136] Customized function component. Function: Allows users to customize the functions of certain buttons on the steering wheel, such as switching different vehicle modes or launching specific applications. Trigger condition: The user performs a user-defined operation through a customized button on the steering wheel.

[0137] Status prompt and user interface component. Function: Show the user prompts of successful operations, such as successful photo taking, emergency recording start, etc. Trigger condition: After executing a specific function, the system service displays feedback information to the user through this component.

[0138] These components are usually implemented in the application of the car system and combined with the event monitoring mechanism of the car system to ensure timely response when the user triggers the corresponding function through the steering wheel button. In this way, the target application processing component of the application layer module can improve driving safety and enhance the user experience. It should be understood that in addition to the steering wheel buttons, the target application processing components mentioned above can also send key event data to the corresponding target application processing components for parsing through physical buttons triggered at other locations in the cockpit to determine the target operation.

[0139] Reference Figure 7 According to some embodiments of the present application, the target operation list includes multiple target operations, and the multiple target operations are executed according to the corresponding list order of the target operation list. After the key event data is parsed based on the target application processing component in step S103 and the target operation is determined, the following is further included:

[0140] Step S701, searching the target operation list for a target operation that matches the operation shielding condition;

[0141] Step S702: for the target operation matching the operation shielding condition, the operation state corresponding to the target operation is set to a consumed state.

[0142] It should be noted that, for multiple key event data, the target operation corresponding to each key event data can be obtained by parsing them separately based on the corresponding target application processing components. These multiple target operations are included in the target operation list. It should be pointed out that these multiple target operations are constrained by the corresponding list order of the target operation list, and each target operation is executed in accordance with the corresponding list order of the target operation list to realize the corresponding functions in sequence. In the embodiment of the present application, the target operation matching the operation shielding condition is queried from the target operation list, wherein the operation shielding condition corresponds to the situation that the physical key operation should not be responded to under certain conditions. For example, when it is detected that the vehicle system is in the activation / login interface, system upgrade interface, parking assistance interface or theme switching loading interface and other scenes, the target operation that can be mapped to some or all physical keys will be constrained under the operation shielding condition, and for the target operation matching the operation shielding condition, the operation state corresponding to the target operation is set to the consumed state, aiming to shield the operation of some or all physical keys to prevent misoperation and inconvenience to the current scene.

[0143] According to some more specific embodiments of the present application, in the Android system, the interface may be composed of multiple layers, and each layer can be defined as a ViewType. ViewType can represent different interfaces, such as activation / login interface, OTA / SOTA upgrade interface, etc. Further, get the currently active ViewType: the list of all view types currently holding focus can be obtained through the AppFocusService.getAllActiveViews() method. Further, check whether this ViewType list contains the ViewType of the interface where the button needs to be blocked. If it is included, it can be determined that the current interface needs to block the button. For interfaces that need to block buttons, when the hard button is pressed, the system will capture the generated KeyEvent, and then directly consume the event, and prevent it from continuing to pass to other components. It should be understood that the embodiments of the present application are applicable to situations where key operations should not be responded to in specific interfaces, such as activation / login interfaces, system upgrade interfaces, parking assistance interfaces, or loading interfaces for theme switching.

[0144] Reference Figure 8 According to some embodiments of the present application, before step S103 of parsing the key event data based on the target application processing component to determine the target operation, the method further includes:

[0145] Step S801, generating an application status signal according to the application status corresponding to the target application processing component;

[0146] Step S802, in the vehicle system, real-time broadcasting of the application status signal;

[0147] After the key event data is parsed based on the target application processing component and the target operation is determined in step S103, the following steps are further included:

[0148] Step S803: based on the real-time broadcast application status signal, determine the shielding status of the target application processing component at the current moment, and perform a corresponding status response operation.

[0149] It should be noted that for different target application processing components, sometimes the target application processing component may be in a specific state, and at this time, the operation of the physical buttons needs to be blocked. For example, during a call, in order to avoid confusion and ensure that the call is not interrupted, some button functions may need to be blocked. For another example, when the in-vehicle navigation application enters full-screen mode and displays detailed maps and navigation instructions, some buttons may need to be blocked to prevent users from operating them by mistake.

[0150] In view of the above situation, in step S103, the embodiment of the present application analyzes the key event data based on the target application processing component, and before determining the target operation, it is necessary to generate an application status signal according to the application status corresponding to the target application processing component, and broadcast the application status signal in real time in the vehicle system. In this way, each link in the vehicle system can clearly know the application status of the target application processing component. Furthermore, based on the real-time broadcast application status signal, the shielding status of the target application processing component at the current moment can be determined, so as to perform the corresponding status response operation.

[0151] In some embodiments, when the real-time broadcast application status signal reflects that the target application processing component is in an application shielding state at the current moment, the target operation matching the target application processing component can be intercepted to prevent the target operation from being executed, resulting in erroneous operation and causing inconvenience to the current scenario.

[0152] In some embodiments, when the target application processing component is in the application shielding state for a time period exceeding a preset time threshold, the application state of the target application processing component can also be reset from the application shielding state to the application running state. In this way, even if the target application processing component does not correctly send the end state broadcast, the key shielding will not continue, thereby avoiding potential problems.

[0153] In some more specific embodiments, the vehicle system learns about these states by monitoring broadcasts from the target application processing component. The vehicle system decides whether to block the button based on the received broadcast status. For example, certain buttons may need to be blocked when restoring factory settings or in a call state. It should be noted that since there may be situations where the status broadcast may not be sent out in a timely manner, the vehicle system needs to implement a status reset mechanism. This usually involves setting a timer, and when no broadcast of the end of the state is received within a certain period of time, the timer triggers a status reset. In this way, it can be ensured that even if the target application processing component does not correctly send a broadcast of the end state, the button blocking will not continue, thereby avoiding potential problems.

[0154] It should be understood that the key shielding methods included in the present application are not limited to the above examples.

[0155] The embodiments of the present application can flexibly shield hard keys when needed to provide a better user experience and avoid misoperation. These mechanisms are particularly important for in-vehicle systems because they can ensure that the driver's attention is not distracted by accidental key operations during critical operations (such as navigation or calls).

[0156] In step S104 of some embodiments, the target operation is executed to trigger the cockpit function matching the key event data. It should be noted that after the target operation is determined, the target operation is executed to respond to the key event data and trigger the cockpit function matching the key event data.

[0157] Reference Fig. 9 According to the vehicle system provided in the embodiment of the present application, the vehicle system may include:

[0158] The key detection module 901 is used to detect the physical keys that have been triggered and generate corresponding key event data;

[0159] A data distribution module 902, configured to send the key event data to a corresponding target application processing component based on monitoring of the key event data;

[0160] Application layer module 903, used to parse key event data based on target application processing component and determine target operation;

[0161] The function execution module 904 is used to execute the target operation to trigger the cockpit function matching the key event data.

[0162] The vehicle provided according to the embodiment of the present application may include:

[0163] The vehicle stores a program, and the program is executed to implement any one of the cockpit function triggering methods provided in the embodiments of the present application, and the vehicle is equipped with the vehicle system provided in the embodiments of the present application.

[0164] It can be seen that the contents of the above-mentioned cockpit function triggering method embodiment are all applicable to the embodiment of this vehicle, the functions specifically implemented by the present vehicle embodiment are the same as those in the above-mentioned cockpit function triggering method embodiment, and the beneficial effects achieved are also the same as the beneficial effects achieved by the above-mentioned cockpit function triggering method embodiment.

[0165] Reference Fig.10 , Fig.10 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0166] The processor 1001 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0167] The memory 1002 may be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 may store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 1002, and the processor 1001 calls and executes the cockpit function triggering method of the embodiment of this application;

[0168] Input / output interface 1003, used to implement information input and output;

[0169] Communication interface 1004, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0170] A bus 1005 , which transmits information between various components of the device (e.g., the processor 1001 , the memory 1002 , the input / output interface 1003 , and the communication interface 1004 );

[0171] The processor 1001 , the memory 1002 , the input / output interface 1003 and the communication interface 1004 are connected to each other in communication within the device via the bus 1005 .

[0172] The third aspect of the present application also provides a vehicle, which includes any of the above cockpit function triggering methods, and the vehicle is equipped with the vehicle system provided by the embodiment of the present application. Specifically, the vehicle can be a gasoline vehicle or a new energy vehicle. When the vehicle is a new energy vehicle, it can be a hybrid vehicle or a pure electric vehicle.

[0173] Specifically, the vehicle provided in the embodiment of the present application can be a gasoline vehicle or a new energy vehicle. When the vehicle is a new energy vehicle, it can be a hybrid vehicle or a pure electric vehicle.

[0174] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and the computer program implements the above method when executed by a processor.

[0175] It can be understood that the contents of the above method embodiments are all applicable to the present storage medium embodiments, the functions specifically implemented by the present storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0176] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0177] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0178] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0179] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0180] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0181] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0182] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, which may include any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0183] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0184] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0185] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0186] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and can include multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0187] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A cockpit function triggering method, characterized in that: Applied to a vehicle computer system, the method includes: Detect the physical keys that have been triggered and generate corresponding key event data; Based on monitoring the key event data, sending the key event data to a corresponding target application processing component; The step of sending the key event data to a corresponding target application processing component based on monitoring the key event data includes: When the target application processing component is in the foreground running state, injecting the key event data into the native event distribution process, distributing the key event data to the corresponding target application processing component through the native event distribution process, acquiring the operation state corresponding to the key event data from the native event distribution process based on monitoring the key event data, and intercepting the corresponding key event data when the operation state is a consumed state; When the target application processing component is in the background running state, based on the key event data, determine the target application processing component that has pre-registered key monitoring from a preset key monitoring list, and distribute the key event data to the target application processing component that has pre-registered key monitoring based on a callback function matching the key monitoring registration; generating an application status signal according to an application status corresponding to the target application processing component; In the vehicle system, real-time broadcasting of the application status signal is performed; Parsing the key event data based on the target application processing component to determine a target operation; When the application status signal broadcast in real time reflects that the target application processing component is in an application shielding state at the current moment, intercepting the target operation matching the target application processing component; When the time for which the target application processing component is in the application shielding state exceeds a preset time threshold, resetting the application state of the target application processing component from the application shielding state to the application running state; The target operation is executed to trigger a cockpit function matching the key event data.

2. The method according to claim 1, characterized in that The step of sending the key event data to a corresponding target application processing component based on monitoring the key event data includes: Encapsulating the key event data in a standard format to obtain the key event data in a standard format; Based on monitoring the key event data in a standard format, the key event data in a standard format is sent to a corresponding target application processing component.

3. The method according to claim 1, characterized in that The target operation list includes a plurality of the target operations, and the plurality of the target operations are executed in a corresponding list order of the target operation list. After the target application processing component parses the key event data and determines the target operation, the target operation further includes: Querying the target operation matching the operation shielding condition from the target operation list; For the target operation matching the operation shielding condition, the operation state corresponding to the target operation is set to a consumed state.

4. A vehicle system, characterized in that: include: A key detection module is used to detect physical keys that have been triggered and generate corresponding key event data; A data distribution module, configured to send the key event data to a corresponding target application processing component based on monitoring of the key event data; The step of sending the key event data to a corresponding target application processing component based on monitoring the key event data includes: When the target application processing component is in the foreground running state, injecting the key event data into the native event distribution process, distributing the key event data to the corresponding target application processing component through the native event distribution process, acquiring the operation state corresponding to the key event data from the native event distribution process based on monitoring the key event data, and intercepting the corresponding key event data when the operation state is a consumed state; When the target application processing component is in the background running state, based on the key event data, determine the target application processing component that has pre-registered key monitoring from a preset key monitoring list, and distribute the key event data to the target application processing component that has pre-registered key monitoring based on a callback function matching the key monitoring registration; The application layer module is used to generate an application status signal according to the application status corresponding to the target application processing component; in the vehicle system, broadcast the application status signal in real time; parse the key event data based on the target application processing component to determine the target operation; when the real-time broadcast application status signal reflects that the target application processing component is in an application shielding state at the current moment, intercept the target operation matching the target application processing component; when the time that the target application processing component is in the application shielding state exceeds a preset time threshold, reset the application state of the target application processing component from the application shielding state to the application running state; A function execution module is used to execute the target operation to trigger a cockpit function matching the key event data.

5. A vehicle, characterized in that: include: The vehicle stores a program, and the program is executed to implement the cockpit function triggering method as described in any one of claims 1 to 3, and the vehicle is equipped with the vehicle system as described in claim 4.

Images