Vehicle-mounted button event distribution arbitration method and apparatus, electronic device and storage medium

Abstract

The present application discloses a vehicle-mounted button event distribution arbitration method, a vehicle-mounted button event distribution arbitration apparatus, an electronic device, a storage medium, and a vehicle. The method comprises: acquiring a button level trigger signal on a steering wheel hardware circuit; a hardware abstraction layer reporting a button trigger event on the basis of the button level trigger signal; a system framework layer encapsulating the button trigger event on the basis of the button trigger event; a system application layer monitoring whether the system framework layer has encapsulated the button trigger event or not; if the system application layer detects the encapsulated button trigger event, executing a service corresponding to the system application layer on the basis of the button trigger event, wherein an arbitration distribution layer is arranged between the system framework layer and the system application layer; and distributing the button trigger event on the basis of the arbitration distribution layer, and the system application layer detecting the encapsulated button trigger event. The solution improves the flexibility of expansion and modification of software applications.

Description

Vehicle-mounted key event distribution arbitration method, device, electronic device and storage medium Technical Field

[0001] The present application relates to the field of vehicle-mounted buttons, and in particular to a vehicle-mounted button event distribution arbitration method, a vehicle-mounted button event distribution arbitration device, an electronic device, a storage medium, and a vehicle. Background Art

[0002] As the most direct interaction module with users, steering wheel buttons provide users with a convenient way to interact, such as adjusting volume and answering calls. In the car system, corresponding actions must be responded to quickly, and the system must be flexible and can be expanded and modified for various models. In the car Android system, the main process of the traditional button system is as follows: 1. The car steering wheel button controller monitors the signal of the button device, performs anti-shake filtering on the key value and pressed / released status, and reports the signal to the HAL (Hardware Abstraction Layer) of the Andropid system; 2. The Android HAL processes the button signal and reports the button signal to the FrameWork layer; 3. The Android FrameWork layer encapsulates the signal into a button event that can be recognized by the app side and reports it to the app side; 4. The app side registers a listener for the button event to receive the button event reported by the FrameWork layer and then executes the corresponding business.

[0003] Traditional solutions have two problems: 1. From a multi-platform perspective, the functions of buttons on mobile phones, such as the volume, back, and home buttons, are relatively uniform, serving essentially the same functions across various phone functions. However, in-vehicle systems vary depending on the model, and steering wheel functions vary. For example, some steering wheels have not only volume buttons but also voice commands and audio source switching, while others have theme switching and multimedia control functions. In the absence of a unified standard, using traditional solutions to address multi-model system design requires extensive modifications throughout the entire software chain, from the Framework to the app. This violates the software design principle of "closed for modification, open for extension," significantly increasing the development cost of new models and leading to limited commercial adoption. 2. From a multi-functional button reuse perspective, a single button can have multiple functions. For example, a button k might have function a in scenario A and function b in scenario B. Therefore, applications A and B, while executing their services, must shield each other's services to account for the exclusive nature of the button's functions. Furthermore, if a button has multiple reused functions, they must shield each other, causing development and maintenance costs to increase exponentially with increasing system complexity.

[0004] Therefore, an in-vehicle key event distribution arbitration solution is needed, which can agree on a unified key reporting format and rules on different vehicle models and platforms, and uniformly distribute and process key events. For multi-function keys, an arbitration layer is added to dynamically prioritize the monitoring of each business registration, so as to achieve exclusive execution of key services without conflict.

[0005] Summary of the Invention

[0006] The object of the present invention is to provide a vehicle-mounted key event distribution arbitration method, a vehicle-mounted key event distribution arbitration device, an electronic device, a storage medium and a vehicle, so as to solve at least one of the above-mentioned technical problems.

[0007] The present invention provides the following solutions:

[0008] According to one aspect of the present invention, a method for distributing and arbitrating in-vehicle key events is provided, the method comprising:

[0009] Get the key level trigger signal on the steering wheel hardware circuit;

[0010] According to the key level trigger signal, the abstract hardware layer reports the key trigger event;

[0011] According to the key trigger event, the system framework layer encapsulates the key trigger event;

[0012] The system application layer monitors whether the system framework layer encapsulates the key trigger event;

[0013] If the system application layer monitors the encapsulated key trigger event, then according to the key trigger event, the system application layer executes the corresponding service;

[0014] Wherein, an arbitration distribution layer is provided between the system framework layer and the system application layer;

[0015] The key trigger event is distributed according to the arbitration distribution layer, and the system application layer monitors the encapsulated key trigger event.

[0016] Furthermore, the distributing of the key trigger event according to the arbitration distribution layer, wherein the system application layer monitors the encapsulated key trigger event, includes:

[0017] Obtaining a monitoring list of the system application layer;

[0018] According to the monitoring list, the arbitration distribution layer distributes the key trigger event;

[0019] The monitoring list includes static monitoring and dynamic monitoring;

[0020] Obtaining scene information that generates the key trigger event;

[0021] The dynamic monitoring includes setting the response priority of the system application layer according to the scenario information of the key triggering event;

[0022] Corresponding to the response priority of the system application layer, the arbitration distribution layer distributes the key trigger event.

[0023] Furthermore, setting the response priority of the system application layer according to the scenario information of the key triggering event includes:

[0024] Acquire application software service information of the system application layer;

[0025] Matching the service of the application software according to the scenario information of the key triggering event;

[0026] The response priority of the system application layer is generated according to the compatibility of the scenario of the key triggering event with the application software business.

[0027] Furthermore, the matching of the application software service with the scenario of the key triggering event and setting the response priority of the system application layer includes:

[0028] Mark the timestamp of the key triggering event;

[0029] Matching the services of the application software according to the timestamp sequence;

[0030] The services of the application software are matched according to the timestamps from near to far.

[0031] Furthermore, the business of matching the application software according to the timestamp from near to far includes:

[0032] Determining the degree of compatibility between the scenario of the key triggering event and the application software service according to the order of the timestamps from recent to remote;

[0033] If the degree of compatibility is lower than a preset degree of compatibility, filtering the application software services according to the order of the timestamps from recent to remote;

[0034] If the time distance between the timestamps from near to far is less than the preset time distance, and the degree of compatibility of the scene of the key trigger event with the application software business is greater than or equal to the preset compatibility level, the application software business is executed according to the key trigger event.

[0035] Furthermore, the abstract hardware layer reporting the key trigger event according to the key level trigger signal includes:

[0036] The arbitration distribution layer presets a filtering mechanism for the key level trigger signal;

[0037] Filtering the classification of the key level trigger signals on the steering wheel hardware circuit according to the preset key level trigger signal filtering mechanism;

[0038] According to the classification of the key level trigger signal on the steering wheel hardware circuit, the key trigger event corresponding to the key level trigger signal on the steering wheel hardware circuit is generated.

[0039] According to two aspects of the present invention, there is provided an in-vehicle key event distribution arbitration device, the in-vehicle key event distribution arbitration device comprising:

[0040] The specific hardware layer module is used to obtain the key level trigger signal on the steering wheel hardware circuit;

[0041] An abstract hardware layer module, configured to report a key trigger event to the abstract hardware layer according to the key level trigger signal;

[0042] The system architecture layer module is used to encapsulate the key triggering event according to the key triggering event;

[0043] A trigger judgment module, configured for the system application layer to monitor whether the key trigger event encapsulated by the system framework layer is detected;

[0044] A service execution module, configured to execute a service corresponding to the system application layer according to the key triggering event if the system application layer monitors the encapsulated key triggering event;

[0045] An arbitration distribution module is used to provide an arbitration distribution layer between the system framework layer and the system application layer;

[0046] The trigger monitoring module is used to distribute the key trigger event according to the arbitration distribution layer, and the system application layer monitors the encapsulated key trigger event.

[0047] According to three aspects of the present invention, there is provided an electronic device, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0048] The memory stores a computer program, and when the processor executes the computer program, the processor executes the steps of the in-vehicle key event distribution arbitration method.

[0049] According to four aspects of the present invention, a computer-readable storage medium is provided, comprising: a computer program executable by an electronic device is stored therein, and when the computer program runs on the electronic device, the electronic device executes the steps of the vehicle-mounted key event distribution arbitration method.

[0050] According to five aspects of the present invention, there is provided a vehicle comprising:

[0051] An electronic device, used to implement the steps of the vehicle-mounted key event distribution arbitration method;

[0052] a processor, the processor running a program, and executing the steps of the vehicle-mounted key event distribution arbitration method based on data output by the electronic device when the program is running;

[0053] The storage medium is used to store a program, and when the program is running, it executes the steps of the vehicle-mounted key event distribution arbitration method for data output from the electronic device.

[0054] Through the above solution, the following beneficial technical effects are achieved:

[0055] This application increases the flexibility of software application expansion and modification by adding an arbitration distribution layer to manage and distribute key trigger events, so that key trigger events correspond to the monitoring of specified application software services.

[0056] This application sets a monitoring list and sets the response priority of the system application layer according to the scenario information of the key trigger event, so that the same key trigger event can be flexibly matched with multiple software applications, thereby suppressing the exponential increase in programming difficulty caused by the increase in software applications.

[0057] This application determines the compatibility of the scene matching application software business of the key trigger event by the order of timestamps from near to far, so that the key event corresponds to the software application with consistency and reduces the interference of invalid key events.

[0058] This application presets a filtering mechanism for key level trigger signals at the arbitration distribution layer to shield erroneous and invalid operations, thereby reducing the burden on the system application layer to monitor events such as erroneous key presses and false key triggering. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] FIG1 is a flowchart of a method for distributing and arbitrating in-vehicle key events provided by one or more embodiments of the present invention.

[0060] FIG2 is a structural diagram of an in-vehicle key event distribution arbitration device provided by one or more embodiments of the present invention.

[0061] FIG3 is a schematic diagram of adding a key distribution arbitration layer according to a specific embodiment of the present invention.

[0062] FIG4 is a schematic diagram of a key distribution arbitration layer structure according to a specific embodiment of the present invention.

[0063] FIG5 is a schematic diagram of a key event recording process according to a specific embodiment of the present invention.

[0064] FIG6 is a schematic diagram of a key event monitoring and sorting process according to a specific embodiment of the present invention.

[0065] FIG. 7 is a schematic diagram of a key event dynamic monitoring process according to a specific embodiment of the present invention.

[0066] FIG8 is a structural block diagram of an electronic device according to a method for distributing and arbitrating in-vehicle key events provided by one or more embodiments of the present invention. DETAILED DESCRIPTION

[0067] The technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0068] FIG1 is a flowchart of a method for distributing and arbitrating in-vehicle key events provided by one or more embodiments of the present invention.

[0069] The vehicle key event distribution arbitration method shown in FIG1 includes:

[0070] Step S1, obtaining a key level trigger signal on the steering wheel hardware circuit;

[0071] Step S2: According to the key level trigger signal, the abstract hardware layer reports the key trigger event;

[0072] Step S3: According to the key trigger event, the system framework layer encapsulates the key trigger event;

[0073] Step S4: the system application layer monitors whether the key trigger event encapsulated by the system framework layer is detected;

[0074] Step S5: If the system application layer monitors the encapsulated key trigger event, the system application layer executes the corresponding service according to the key trigger event;

[0075] Step S6, wherein an arbitration distribution layer is provided between the system framework layer and the system application layer;

[0076] Step S7: The arbitration distribution layer distributes the key trigger event, and the system application layer monitors the encapsulated key trigger event.

[0077] Specifically, the key level trigger signal on the steering wheel hardware circuit is obtained, that is, the electrical signal caused by the user's mechanical operation of the key on the steering wheel. The hardware on the steering wheel can be used as the specific hardware layer, and the Android HAL layer is used as the abstract hardware layer to connect the key trigger events of the user operation. The Android Framework layer serves as the system framework layer, connecting the key trigger events with the software applications under the system application layer, such as APP. The software applications under the system application layer listen to the key trigger events of the user operation output from the Framework layer, so as to decide whether the APP responds to the user operation and executes the corresponding business. An arbitration distribution layer is set between the Framework layer and the system application layer to distribute the keys, so that among multiple APPs, only the distributed APPs can execute the corresponding business. The key events are distributed through the arbitration distribution layer, so that multiple APPs will respond only after listening to their own key events.

[0078] In this embodiment, according to the distribution of key trigger events by the arbitration distribution layer, the system application layer monitors the encapsulated key trigger events including:

[0079] Get the monitoring list of the system application layer;

[0080] According to the monitoring list, the arbitration distribution layer distributes key trigger events;

[0081] Among them, the monitoring list includes static monitoring and dynamic monitoring;

[0082] Get the scene information that generates the key trigger event;

[0083] Dynamic monitoring includes setting the response priority of the system application layer according to the scene information of the key trigger event;

[0084] Corresponding to the response priority of the system application layer, the arbitration distribution layer distributes key trigger events.

[0085] Specifically, according to the monitoring list and APP priority, key trigger events are monitored according to the priority. The arbitration distribution layer distributes key trigger events and distributes them in pairs with APPs. The monitoring list includes static monitoring and dynamic monitoring, where static monitoring is fixed and directly executes the monitored key trigger events. Dynamic monitoring needs to be determined based on the current scenario of generating key trigger events. In other words, the same key operation can control multiple APPs, but it is necessary to decide which one or several APPs will respond to the key trigger event and execute the business based on the scenario of the key trigger event. Since the scenario has a specific meaning, only the corresponding APP response is meaningful. For example, the user triggers the up and down buttons on the steering wheel, but the current music playback is turned off, the volume business of the music APP does not respond, and the current air conditioner is on, the temperature business of the air conditioner APP can respond.

[0086] In this embodiment, setting the response priority of the system application layer according to the scenario information of the key triggering event includes:

[0087] Obtain application software business information of the system application layer;

[0088] Match the application software's services based on the scenario information of the key trigger event;

[0089] The compatibility of the application software business is matched according to the scenario of the key trigger event, and the response priority of the system application layer is generated.

[0090] Specifically, the scenario-matching application software business for key-triggered events must be relevant to the app's current business. For example, there are currently navigation apps, headlight apps, and wiper apps. The headlight app has a business function for left and right illumination direction, while the navigation app and wiper app do not have business functions corresponding to left and right key events. Therefore, the headlight app has the highest degree of fit and receives the highest response priority at the system application layer.

[0091] In this embodiment, setting the response priority of the system application layer according to the compatibility of the key triggering event scenario with the application software service includes:

[0092] Mark the timestamp of the key trigger event;

[0093] Match the business of application software according to the timestamp sequence;

[0094] Among them, the business of the application software is matched according to the timestamp from recent to far.

[0095] Specifically, each keystroke trigger event is timestamped and dynamically monitored. The closest keystroke event is typically selected as the judgment target, as it best matches the current scenario. Because app execution requires time and a response process, the app's services are matched based on timestamps, starting from the nearest and the furthest.

[0096] In this embodiment, the services of matching application software according to the timestamps from recent to remote include:

[0097] Determine the suitability of the key triggering event scenario with the application software business based on the time stamp order from recent to recent.

[0098] If the compatibility is lower than the preset compatibility level, the application software business is filtered in the order of the timestamp from recent to remote;

[0099] If the time distance between the timestamps from near to far is less than the preset time distance, and the degree of compatibility between the scene of the key trigger event and the application software business is greater than or equal to the preset compatibility level, the application software business is executed according to the key trigger event.

[0100] Specifically, it is not ruled out that the same key trigger event can operate multiple apps, and the scenario is suitable for multiple apps to execute services. The compatibility of the key trigger event scenario with the application software service can be determined based on the order of timestamps from recent to recent. However, if a key trigger event that is too old is far away from the current scenario, so the time distance from the recent to recent timestamps is less than the preset time distance, and the compatibility of the key trigger event scenario with the application software service is greater than or equal to the preset compatibility level, the application software service will be executed according to the key trigger event.

[0101] Executing applications does not preclude the simultaneous execution of multiple apps. For example, if a user presses the steering wheel button three times to increase the temperature inside the car, the door app and the air conditioning app can execute the function together. The door app closes the windows and sunroof, while the air conditioning app turns on the heater.

[0102] In this embodiment, according to the key level trigger signal, the abstract hardware layer reports the key trigger event including:

[0103] The arbitration distribution layer presets a filtering mechanism for key level trigger signals;

[0104] According to the preset key level trigger signal filtering mechanism, the classification of the key level trigger signal on the steering wheel hardware circuit is filtered;

[0105] According to the classification of the key level trigger signal on the steering wheel hardware circuit, a key trigger event corresponding to the key level trigger signal on the steering wheel hardware circuit is generated.

[0106] Specifically, the user's key level trigger signal on the steering wheel hardware circuit can be a single click, a long press, or the simultaneous operation of multiple keys, representing different key trigger events. After the arbitration distribution layer presets a filtering mechanism for key level trigger signals, case trigger events belonging to different apps can be filtered for the current app. For example, if the music app is currently in the foreground, displaying the volume interface, and a triple-click of the button is not a pause or volume adjustment operation related to the music app, it can be filtered out, reducing the burden on the music app to monitor. The filtered triple-click case trigger event is then open to the air conditioning app and the car door app, allowing the air conditioning app and the car door app to monitor the case event of executing the service of increasing the vehicle temperature.

[0107] FIG2 is a structural diagram of an in-vehicle key event distribution arbitration device provided by one or more embodiments of the present invention.

[0108] The vehicle-mounted key event distribution arbitration device shown in FIG2 includes: a specific hardware layer module, an abstract hardware layer module, a system architecture layer module, a trigger judgment module, a service execution module, an arbitration distribution module, and a trigger monitoring module;

[0109] The specific hardware layer module is used to obtain the key level trigger signal on the steering wheel hardware circuit;

[0110] The abstract hardware layer module is used to trigger signals according to the key level, and the abstract hardware layer reports key trigger events;

[0111] The system architecture layer module is used to trigger events based on keystrokes. The system framework layer encapsulates keystroke triggering events.

[0112] The trigger judgment module is used by the system application layer to monitor whether the key trigger event is encapsulated by the system framework layer;

[0113] The service execution module is used to execute the corresponding service of the system application layer according to the key trigger event if the system application layer monitors the encapsulated key trigger event;

[0114] Arbitration distribution module, which is used to set up an arbitration distribution layer between the system framework layer and the system application layer;

[0115] The trigger monitoring module is used to distribute key trigger events according to the arbitration distribution layer, and the system application layer monitors the encapsulated key trigger events.

[0116] It is worth noting that although this system only discloses the specific hardware layer module, the abstract hardware layer module, the system architecture layer module, the trigger judgment module, the service execution module, the arbitration distribution module, and the trigger monitoring module, relatively speaking, what the present invention wants to express is that, based on the above-mentioned basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with the existing technology to form an infinite number of embodiments or technical solutions. In other words, this system is open rather than closed. Just because this embodiment only discloses individual basic functional modules, it cannot be considered that the scope of protection of the claims of the present invention is limited to the above-mentioned basic functional modules.

[0117] Through the above solution, the following beneficial technical effects are achieved:

[0118] This application increases the flexibility of software application expansion and modification by adding an arbitration distribution layer to manage and distribute key trigger events, so that key trigger events correspond to the monitoring of specified application software services.

[0119] This application sets a monitoring list and sets the response priority of the system application layer according to the scenario information of the key trigger event, so that the same key trigger event can be flexibly matched with multiple software applications, thereby suppressing the exponential increase in programming difficulty caused by the increase in software applications.

[0120] This application determines the compatibility of the scene matching application software business of the key trigger event by the order of timestamps from near to far, so that the key event corresponds to the software application with consistency and reduces the interference of invalid key events.

[0121] This application presets a filtering mechanism for key level trigger signals at the arbitration distribution layer to shield erroneous and invalid operations, thereby reducing the burden on the system application layer to monitor events such as erroneous key presses and false key triggering.

[0122] FIG3 is a schematic diagram of adding a key distribution arbitration layer according to a specific embodiment of the present invention.

[0123] FIG4 is a schematic diagram of a key distribution arbitration layer structure according to a specific embodiment of the present invention.

[0124] FIG5 is a schematic diagram of a key event recording process according to a specific embodiment of the present invention.

[0125] FIG6 is a schematic diagram of a key event monitoring and sorting process according to a specific embodiment of the present invention.

[0126] FIG. 7 is a schematic diagram of a key event dynamic monitoring process according to a specific embodiment of the present invention.

[0127] In a specific embodiment, as shown in FIG3 , a button arbitration layer is added above the Android Framework layer to solve the problem of agreeing on a unified button reporting format on different vehicle platforms and performing unified distribution processing on button events. In the case of multi-function buttons, the arbitration layer can dynamically prioritize the monitoring of each service registration to achieve exclusive execution of the button service, thereby solving the problem of no unified standard in the software development process and requiring a large number of modifications to the entire software chain from Android FrameWork to the APP side in response to multiple vehicle models.

[0128] In another specific embodiment, the Android arbitration module is implemented as a resident service in the Android system. It converts the key signals received from the Framework into unified key events for the APP side, and makes priority judgments on the key monitoring list registered on the APP side and selectively monitors them.

[0129] As shown in Figure 4, the key signal processing unit filters and reports the press and release signals, and the key event storage unit reports the key value and event type (e.g., short press followed by release, long press followed by release, long press without release, etc.). The key press event is reported to the monitoring arbitration unit. The APP arbitration unit obtains the mapped case event from the key value based on the monitoring list. After the corresponding monitoring arbitration unit matches the key event, the corresponding APP and APP's business function are executed.

[0130] The key signal processing unit receives key signals reported by the Android framework. These signals include the key value, press / release status, and timestamp. Invalid signals are filtered to ensure a complete press / release signal pair is reported. This is used by the key event encapsulation unit to determine the event type.

[0131] The key event encapsulation unit receives the signal from the key signal processing unit, encapsulates it into an event based on the timestamp and status of the signal, and reports it to the monitoring arbitration unit. This event contains the following information: key value, timestamp, and event type (long press, short press, long press and release).

[0132] In another specific embodiment, as shown in FIG5 , a timestamp is recorded for a pressing operation of a key value K, and the type of the key event is defined according to the timestamp, such as long press, short press, long press and release, etc.

[0133] In another specific embodiment, the APP registers to monitor the key monitoring list, and the monitoring is divided into static monitoring and dynamic monitoring according to the priority, and the dynamic monitoring has a higher priority than the static monitoring. Static monitoring is mainly the default function of the key, and dynamic monitoring is mainly used for the specific action of the key in a certain scenario. Dynamic monitoring is sorted by timestamp, and only the most recent monitoring is executed for static and dynamic monitoring. As shown in Figure 6, the APP monitors key events after registration. If static monitoring is registered, the APP process will be directly entered and exited. If dynamic monitoring is registered, it will be sorted from near to far according to the timestamp.

[0134] In another specific embodiment, as shown in FIG7 , the monitoring arbitration unit is the core module. Its input is the output monitoring list and key events. It finds the corresponding monitoring list according to the key value of the event, and then performs priority arbitration on the list, selects the monitoring with the highest priority and reports it to the APP side to execute the business.

[0135] For the key value of the reported signal, the corresponding listener list is retrieved from the listener map. If there are only static listeners in the listener list, the listener action is executed directly. If there are dynamic listeners in the listener list, the latest listener action is used.

[0136] FIG8 is a structural block diagram of an electronic device according to a method for distributing and arbitrating in-vehicle key events provided by one or more embodiments of the present invention.

[0137] As shown in FIG8 , the present application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0138] A computer program is stored in the memory. When the computer program is executed by the processor, the processor is caused to execute steps of a vehicle-mounted key event distribution arbitration method.

[0139] The present application also provides a computer-readable storage medium storing a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of a vehicle-mounted key event distribution arbitration method.

[0140] The present application also provides a vehicle, comprising:

[0141] An electronic device for implementing the steps of the vehicle key event distribution arbitration method;

[0142] a processor, wherein the processor runs a program and, when the program runs, executes the steps of the vehicle key event distribution arbitration method based on data output by the electronic device;

[0143] The storage medium is used to store a program, and when the program is running, it executes the steps of the vehicle key event distribution arbitration method for data output from the electronic device.

[0144] The communication bus mentioned in the electronic device mentioned above may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0145] The electronic device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory. The operating system can be any one or more computer operating systems that control electronic devices through processes, such as the Linux operating system, the Unix operating system, the Android operating system, the iOS operating system, or the Windows operating system. In the embodiments of the present invention, the electronic device can be a handheld device such as a smartphone or a tablet computer, or an electronic device such as a desktop computer or a portable computer, which is not particularly limited in the embodiments of the present invention.

[0146] The execution subject of the electronic device control in the embodiment of the present invention can be an electronic device, or a functional module in the electronic device that can call a program and execute the program. The electronic device can obtain the firmware corresponding to the storage medium. The firmware corresponding to the storage medium is provided by the supplier. The firmware corresponding to different storage media can be the same or different, and is not limited here. After the electronic device obtains the firmware corresponding to the storage medium, it can write the firmware corresponding to the storage medium into the storage medium, specifically, burn the firmware corresponding to the storage medium into the storage medium. The process of burning the firmware into the storage medium can be implemented using existing technology and will not be described in detail in the embodiment of the present invention.

[0147] The electronic device can also obtain a reset command corresponding to the storage medium. The reset command corresponding to the storage medium is provided by the supplier. The reset commands corresponding to different storage media can be the same or different, and are not limited here.

[0148] In this case, the storage medium of the electronic device is a storage medium in which the corresponding firmware is written. The electronic device can respond to the reset command corresponding to the storage medium in which the corresponding firmware is written, thereby resetting the storage medium in which the corresponding firmware is written according to the reset command corresponding to the storage medium. The process of resetting the storage medium according to the reset command can be implemented in the existing technology and will not be described in detail in the embodiments of the present invention.

[0149] For the convenience of description, the above devices are described as various units and modules according to their functions. Of course, when implementing this application, the functions of each unit and module can be implemented in the same or multiple software and / or hardware.

[0150] Those skilled in the art will understand that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by those skilled in the art in the art to which the present invention pertains. It should also be understood that terms such as those defined in common dictionaries should be understood to have meanings consistent with those in the context of the prior art and, unless specifically defined, will not be interpreted in an idealized or overly formal sense.

[0151] For simplicity of description, the method embodiments are described as a series of actions. However, those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because certain steps can be performed in other orders or simultaneously according to the embodiments of the present invention. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0152] Through the description of the above embodiments, it can be seen that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general-purpose hardware platform. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present application or certain parts of the embodiments.

[0153] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for distributing and arbitrating in-vehicle button events, characterized in that, The in-vehicle button event distribution arbitration method includes: Obtain the button level trigger signal on the steering wheel hardware circuit; Abstract the button trigger event reported by the hardware layer according to the button level trigger signal; Package the button trigger event at the system framework layer according to the button trigger event; The system application layer monitors whether the button trigger event encapsulated by the system framework layer; If the system application layer monitors the encapsulated button trigger event, then according to the button trigger event, execute the corresponding service of the system application layer; Among them, an arbitration distribution layer is provided between the system framework layer and the system application layer; According to the arbitration distribution layer distributing the button trigger event, the system application layer monitors the encapsulated button trigger event.

2. The on-vehicle button event distribution arbitration method according to claim 1, characterized in that, The system application layer monitoring the encapsulated button trigger event according to the arbitration distribution layer distributing the button trigger event includes: Obtain the monitoring list of the system application layer; According to the monitoring list, the arbitration distribution layer distributes the button trigger event; Among them, the monitoring list includes static monitoring and dynamic monitoring; Obtain the scenario information of the button trigger event; The dynamic monitoring includes setting the response priority of the system application layer according to the scenario information of the button trigger event; Corresponding to the response priority of the system application layer, the arbitration distribution layer distributes the button trigger event.

3. The in-vehicle button event distribution arbitration method according to claim 2, characterized in that, Setting the response priority of the system application layer according to the scenario information of the button trigger event includes: Obtain the application software service information of the system application layer; Match the service of the application software according to the scenario information of the button trigger event; Generate the response priority of the system application layer according to the matching degree of the application software service with the scenario of the button trigger event.

4. The in-vehicle button event distribution arbitration method according to claim 3, wherein, Setting the response priority of the system application layer according to the matching degree of the application software service with the scenario of the button trigger event includes: Mark the timestamp of the button trigger event; Match the service of the application software according to the order of the timestamps; Among them, according to the timestamps from near to far, match the service of the application software.

5. The on-vehicle button event distribution arbitration method according to claim 4, wherein Matching the service of the application software according to the timestamps from near to far includes: Judge the matching degree of the scenario of the button trigger event with the service of the application software according to the order of the timestamps from near to far; If the matching degree is lower than the preset matching degree level, then filter the service of the application software according to the order of the timestamps from near to far; If the time distance from near to far of the timestamps is less than the preset time distance, and the matching degree of the scenario of the button trigger event with the service of the application software is greater than or equal to the preset matching degree level, then execute the service of the application software according to the button trigger event.

6. The in-vehicle button event distribution arbitration method according to claim 5, wherein, Abstracting the button trigger event reported by the hardware layer according to the button level trigger signal includes: The arbitration distribution layer presets the filtering mechanism of the button level trigger signal; Filter the classification of the button level trigger signal on the steering wheel hardware circuit according to the preset filtering mechanism of the button level trigger signal. Generate the key trigger event corresponding to the key level trigger signal on the steering wheel hardware circuit according to the classification of the key level trigger signals on the steering wheel hardware circuit.

7. An in-vehicle button event distribution arbitration device, characterized in that, The vehicle-mounted key event distribution arbitration device includes: A specific hardware layer module, configured to obtain the key level trigger signal on the steering wheel hardware circuit; An abstract hardware layer module, configured to report a key trigger event in the abstract hardware layer according to the key level trigger signal; A system architecture layer module, configured to encapsulate the key trigger event in the system framework layer according to the key trigger event; A trigger judgment module, configured to monitor whether the key trigger event encapsulated by the system framework layer in the system application layer; A service execution module, configured to, if the system application layer monitors the encapsulated key trigger event, execute the corresponding service in the system application layer according to the key trigger event; An arbitration distribution module, configured to provide an arbitration distribution layer between the system framework layer and the system application layer; A trigger monitoring module, configured to distribute the key trigger event according to the arbitration distribution layer, and the system application layer monitors the encapsulated key trigger event.

8. An electronic device, characterized in that, including: A processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete mutual communication through the communication bus; A computer program is stored in the memory, and when the computer program is executed by the processor, the processor is caused to execute the steps of the vehicle-mounted key event distribution arbitration method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, including: It stores a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device is caused to execute the steps of the vehicle-mounted key event distribution arbitration method according to any one of claims 1 to 6.

10. A vehicle, characterized in that, including: An electronic device, configured to implement the steps of the vehicle-mounted key event distribution arbitration method according to any one of claims 1 to 6; A processor, the processor runs a program, and when the program runs, it executes the steps of the vehicle-mounted key event distribution arbitration method according to any one of claims 1 to 6 for the data output from the electronic device; A storage medium, configured to store a program, and the program executes the steps of the vehicle-mounted key event distribution arbitration method according to any one of claims 1 to 6 for the data output from the electronic device when running.

Images