Vehicle-mounted button custom control method, intelligent cabin and electronic equipment
Through the dual-end software architecture and JNI technology, the custom function of on-board buttons is realized, which solves the problem that the physical button function in the existing technology cannot meet the needs of different users, reduces the number of physical buttons, saves costs and improves the user experience.
Patent Information
- Application Number
- CN202411015481.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-26
- Publication Date
- 2024-11-15
AI Technical Summary
The existing in-car central control screen functions are complex, and the physical button function cannot meet the needs of different users. Increasing physical buttons will increase the cost of car companies and cannot meet the needs of users.
It adopts a dual-end software architecture, through the interaction between the Client and Service, the user-defined entity button function is realized, and the underlying data interaction is used to support user-defined key functions and update and display in real time, simplifying the development process and reducing the number of entity buttons.
Meet the different habit needs of multiple users, reduce the number of physical buttons, save production costs, support users to customize physical button functions, improve user experience and system flexibility, and realize personalized configuration of key functions.
Smart Images

Figure CN118953247A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a control method, a smart cockpit, and an electronic device, and in particular to a vehicle-mounted button customization control method, a smart cockpit, and an electronic device. Background Art
[0002] At present, the car's central control screen has more and more functions, and many physical button functions are placed on the central control screen. Some physical buttons have been removed, but this is inconsistent with the user's demand for physical buttons. Physical buttons may not fully meet user needs. Blindly increasing physical buttons will lead to increased costs for car companies. It can no longer meet people's requirements and urgently needs to be improved. Summary of the invention
[0003] The purpose of the present invention is to provide a method for customizing vehicle-mounted buttons, a smart cockpit, and an electronic device. The first technical problem to be solved is to coordinate the needs of different users for different configurations of physical buttons. The second technical problem to be solved is to personalize the vehicle-mounted buttons to solve the shortcomings of the existing technology.
[0004] The present invention provides the following scheme:
[0005] A vehicle button custom control method, applied to a vehicle button custom control system, comprises:
[0006] Setting custom function buttons based on a dual-end software architecture, the dual-end software architecture includes a client end and a service end, wherein the client end is used to set physical buttons, and the service end implements the logic functions of signal conversion and hard button display;
[0007] The client side includes a display client for realizing button icon changes, and a central control custom button client for realizing user-defined functions. The client side sends a button function verification message to the service application on the service side through interactive means;
[0008] The Service application on the Service side receives the button function verification message, determines the feasibility of the current setting, and if it is feasible, updates the vehicle signal table and notifies the Client side to update the hard key display; if it is not feasible, prompts the Client side to re-set the button through interactive means.
[0009] Furthermore, the dual-end software architecture implements underlying data interaction through JNI technology, where:
[0010] The Client side is the user interaction interface, and the Service side is the service processing module;
[0011] The client receives the hard key information selected by the user through the operation interface and sets a new response function. The client passes the newly set response function to the service through JNI;
[0012] After receiving the new response function, the Service performs logical processing and feeds the processing result back to the Client through JNI.
[0013] Further: The client provides a user interface for allowing the user to select and customize the functions of the hard keys;
[0014] The client stores the user-defined button function settings and displays the updated display content in the client in the physical button;
[0015] The client provides a confirmation button to apply the newly set response function to the selected hard key.
[0016] Furthermore, the Service application of the Service end receives the button function verification message and determines the feasibility of the current setting, further comprising:
[0017] The client side obtains the btn_signal information of a user randomly pressing a custom hard key, and sends the hard key information corresponding to the hard key to the Service application on the Service side through the vehicle system;
[0018] The Service application on the Service side traverses the vehicle signal table, finds the function information corresponding to the custom hard key information, and sends it to the vehicle system;
[0019] The vehicle system responds to the actual vehicle functions based on the signals received from the custom hard keys.
[0020] Furthermore, the dual-end software architecture realizes the underlying data interaction through JNI technology, and further includes:
[0021] The Service receives the button function verification message transmitted from the Client through JNI;
[0022] Case No.: FAW040548-C-XCN1240442 2
[0023] The server determines whether the newly set button function conflicts with the existing function or meets the system requirements based on the preset rules and logic;
[0024] If the newly set button function is feasible, the Service application updates the vehicle signal table and passes the updated signal table to the Client through JNI. The Client updates the hard button display according to the updated signal table.
[0025] If the newly set button function is not feasible, the Service application generates an error prompt message and passes it to the Client through JNI. After the Client receives the error prompt message, it prompts the user to re-set the button through the user interface.
[0026] A vehicle-mounted button custom control system, used to implement the vehicle-mounted button custom control method, comprising:
[0027] The dual-end software architecture builds an application module, and the custom function keys are set based on the dual-end software architecture. The dual-end software architecture includes a client end and a service end, wherein the client end is used to set the physical button, and the service end realizes the logic functions of signal conversion and hard key display;
[0028] The client-side function realization module includes a display client for realizing the button icon change and a central control custom button client for realizing user-defined functions. The client-side sends a button function verification message to the service application on the service side through interactive means;
[0029] The service-side function implementation module, the service application of the service side receives the button function verification message, determines the feasibility of the current setting, and if feasible, updates the vehicle signal table and notifies the client side to update the hard button display; if not feasible, prompts the client side to re-set the button through interactive means.
[0030] A vehicle computer is provided with the vehicle-mounted button custom control system and executes the vehicle-mounted button custom control method.
[0031] A smart cockpit, wherein the vehicle computer is arranged in the smart cockpit.
[0032] An electronic device comprises: 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; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method.
[0033] A computer-readable storage medium stores a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the method.
[0034] Compared with the prior art, the present invention has the following advantages:
[0035] The present invention can meet the needs of physical button functions in vehicles, meet the different habits of multiple users, help car companies reduce physical buttons in different usage scenarios, and save production costs. The present invention supports the use of a small number of physical function buttons to achieve multiple functions, supports users to customize physical button functions, and can change button indicator icons in real time, which is convenient for users to operate and use.
[0036] The present invention supports the customization of a small number of physical buttons in the vehicle. After the user sets them according to their own habits, they can quickly control the central control functions through the physical buttons. After the user customizes the button function, the present invention also designs a method for changing the backlight prompt of the vehicle button in real time, so as to prompt the user of the actual function corresponding to the button. The present invention adopts a one-to-many dual-end communication architecture to simplify the development process. The main business logic is implemented in the Service. The Client is only responsible for the simple button icon display and the implementation of the custom button function, realizing the functional decoupling of different ends. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0038] Figure 1 It is a flow chart of the vehicle button custom control method.
[0039] Figure 2 This is the architecture diagram of the vehicle button custom control system.
[0040] Figure 3 This is a flowchart for custom button settings.
[0041] Figure 4 It is a flowchart of implementing functions by customizing the button press response.
[0042] Figure 5 It is the flow chart of updating the vehicle signal table.
[0043] Figure 6 It is the flow chart of traversal of the vehicle signal table.
[0044] Figure 7It is a structural diagram of an electronic device. DETAILED DESCRIPTION
[0045] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0046] like Figure 1 The flowchart of the vehicle button customization control method shown in the figure is applied to the vehicle button customization control system, including:
[0047] Step S1, setting a custom function button based on a dual-end software architecture, wherein the dual-end software architecture includes a client end and a service end, wherein the client end is used to set a physical button, and the service end implements the logic functions of signal conversion and hard button display;
[0048] Step S2, the Client end includes a display Client for realizing the change of the button icon, and a central control custom button Client for realizing the user-defined function. The Client end sends a button function verification message to the Service application of the Service end through an interactive means;
[0049] Step S3, the Service application on the Service side receives the button function verification message, determines the feasibility of the current setting, and if it is feasible, updates the vehicle signal table and notifies the Client side to update the hard key display; if it is not feasible, prompts the Client side to re-set the button through interactive means.
[0050] In step S1 to step S3, the client sets the physical button display Client and the central control custom button Client, where the physical button display Client is used to realize the button icon change through a lightweight application, and the central control custom button Client is an application of the central control, which is used to realize the user-defined button function. Step S1 to step S3 describes a client (Client) setting the physical button display and the central control custom button function, as well as the data interaction process between the client (Client) and the Service:
[0051] Physical button display Client: refers to the function of changing the button icon through a lightweight application. This means that on the client, users can change the icon or status on the physical button by using a lightweight application. For example, in a smart cockpit, users can switch the physical button from "on" to "off" through the car computer, in-vehicle device or mobile phone app.
[0052] Central control custom buttons Client: refers to the central control application, which allows users to customize button functions. Through the central control application, users can assign different functions or operations to different buttons. For example, there is a central control panel inside the car, and the driver can use the preset buttons on the panel to adjust the volume, change the radio channel, etc.
[0053] Through the operations from step S1 to step S3, two different types of button functions can be implemented on the client: one is to change the physical button display through a lightweight application, and the other is to perform customized button operations through a unique central control application.
[0054] The lightweight application in step S1 to step S3 refers to the ability to customize the button functions by changing the icons or states on the physical buttons. For example, on the central control panel inside the car, the driver can use the lightweight application to personalize the preset button functions, such as adjusting the volume, changing the radio channel, etc.
[0055] Preferably, in the optimization technical solution in step S1, the dual-end software architecture implements underlying data interaction through JNI technology, wherein:
[0056] The Client side is the user interaction interface, and the Service side is the service processing module;
[0057] The client receives the hard key information selected by the user through the operation interface and sets a new response function. The client passes the newly set response function to the service through JNI;
[0058] After receiving the new response function, the Service performs logical processing and feeds the processing result back to the Client through JNI.
[0059] In the dual-end software architecture of this embodiment, the underlying data interaction between the Client and Service is realized through Java Native Interface (JNI) technology. The core of the JNI method is to allow the user to customize the response function of the hard keys through the user interface on the Client side, and pass these customized settings to the Service side for processing through JNI technology. After receiving this information, the Service side performs logical verification and processing, and feeds back the processing results to the Client side, thereby realizing real-time update and application of user-defined key functions.
[0060] JNI technology can be used to achieve cross-language data interaction, solve the data interaction problem between Java (Client) and local code (Service), and enable the customized settings of the user interface to be understood and processed by the server. Based on the real-time nature of JNI technology, the real-time transmission and processing of user-defined settings is ensured, avoiding the delays that may be caused by traditional communication methods. Finally, user-defined functions are realized, allowing users to customize the functions of hard keys according to their needs, improving the flexibility of the software and user experience, enhancing the user experience, users can customize the functions of hard keys according to their preferences and needs, making the software more personalized and easy to use, and realizing efficient data processing: the Service can receive and process the customized settings sent by the Client in a timely manner, ensuring the speed and accuracy of the software response. Extensibility and maintainability are achieved through JNI technology, making the software architecture have good extensibility, facilitating the addition and maintenance of future functions, and reducing the porting cost between different platforms.
[0061] Preferably, in some embodiments, the technical solution of step S1 can be further optimized:
[0062] The client provides a user interface to allow users to select and customize the functions of hard keys;
[0063] The client stores the user-defined button function settings and displays the updated display content in the client in the physical button;
[0064] The client provides a confirmation button to apply the newly set response function to the selected hard key.
[0065] Preferably, in step S3, the Service application of the Service end receives the button function verification message and determines the feasibility of the current setting, further comprising:
[0066] The client side obtains the btn_signal information of a user randomly pressing a custom hard key, and sends the hard key information corresponding to the hard key btn to the Service application on the Service side through the vehicle system;
[0067] The Service application on the Service side traverses the vehicle signal table, finds the function information Functional_signals corresponding to the custom hard button information btn_signal, and sends it to the vehicle system;
[0068] The vehicle system responds to the actual vehicle functions based on the signals received from the custom hard keys.
[0069] The optimized technical solution of step S3 realizes the association between user-defined buttons and vehicle functions, solves the association problem between user-defined button settings and vehicle system function responses, and allows users to set the functions of hard buttons according to their needs. In the process of signal processing, the real-time nature of signal transmission and processing can be ensured, ensuring the real-time and accuracy of signal transmission in the entire process from user operation to vehicle system response. Through the logical processing on the Service side, the flexibility and scalability of the vehicle system are improved, allowing the system to adjust functions according to the needs of different users, improving the flexibility and scalability of the vehicle system, and improving the user experience. Users can set the hard button functions according to their preferences, making vehicle control more personalized and convenient.
[0070] Preferably, in step S3, the dual-end software architecture implements underlying data interaction through JNI technology, further comprising:
[0071] Step S31, the Service side receives the button function verification message transmitted from the Client side through JNI;
[0072] Step S32, the Service determines whether the newly set button function conflicts with the existing function or meets the system requirements according to the preset rules and logic;
[0073] Step S33, if the newly set button function is feasible, the Service application updates the vehicle signal table and passes the updated signal table to the Client through JNI, and the Client updates the hard button display according to the updated signal table;
[0074] Step S34: If the newly set button function is not feasible, the Service application generates an error prompt message and transmits it to the Client through JNI. After the Client receives the error prompt message, it prompts the user to re-set the button through the user interface.
[0075] After processing from step S31 to step S32, the overall response capability of the vehicle-mounted system is enhanced, and the intelligent processing on the Service side ensures a quick response to user operations and improves the overall response capability of the system; improves the optimization resource utilization rate, optimizes the utilization of system resources by centrally processing user-defined settings, and reduces the repeated occupation of vehicle system resources; improves the maintainability of the vehicle-mounted system: centrally manages the mapping relationship between user-defined settings and function signals, which facilitates system maintenance and upgrades.
[0076] For the method steps disclosed in the above embodiments, the method steps are described as a series of action combinations for the purpose of simple description, but those skilled in the art should know that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.
[0077] Any process or method description described in a flowchart or other manner may be understood as representing a module, fragment or portion of a code including one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations, in which the order shown or discussed may not be followed, including executing and implementing the functions in a substantially simultaneous manner or in a reverse order according to the functions involved, or executing computer instructions and implementing the corresponding functions according to program structures such as loops and branches, which can be naturally understood by those skilled in the art when implementing the embodiments of the present invention.
[0078] like Figure 2 The vehicle button custom control system shown is used to implement the vehicle button custom control method described in item 1, including:
[0079] The dual-end software architecture builds an application module, and the custom function buttons are set based on the dual-end software architecture. The dual-end software architecture includes a client end and a service end, wherein the client end is used to set the physical button, and the service end realizes the logic functions of signal conversion and hard button display;
[0080] The client-side function realization module includes a display client for realizing the button icon change and a central control custom button client for realizing user-defined functions. The client-side sends a button function verification message to the service application on the service side through interactive means;
[0081] The service-side function implementation module, the service application of the service side receives the button function verification message, determines the feasibility of the current setting, and if feasible, updates the vehicle signal table and notifies the client side to update the hard button display; if not feasible, prompts the client side to re-set the button through interactive means.
[0082] The implementation methods of the system described above are merely illustrative, for example, the various functional modules, units or subsystems in the system may or may not be physically separated, or may or may not be physical units, that is, they may be located in the same place, or they may be distributed to multiple different systems and their subsystems or modules. Those skilled in the art may select some or all of the functional modules, units or subsystems according to actual needs to achieve the purpose of the embodiments of the present invention, and those of ordinary skill in the art may understand and implement the above-mentioned situations without creative work.
[0083] like Figures 3 to 6 As shown, the technical problem addressed by this embodiment is mainly: the physical central control functions of vehicles on the market are becoming more and more complex, and users expect to operate the central control functions easily, but the central control screen does not have the convenience of physical buttons when operating while driving. In order to resolve this contradiction, this embodiment provides a new technical solution to enable users to customize the functions of vehicle-mounted buttons, and supports the vehicle to customize a small number of physical buttons. After users set them according to their own habits, they can quickly control the central control functions through physical buttons. As a further improvement, after users customize the button functions, they can also change the backlight prompt method of the vehicle-mounted buttons in real time, so as to prompt users of the actual functions corresponding to the buttons.
[0084] This embodiment adopts a one-to-many dual-end communication architecture to simplify the development process. The main business logic is implemented in the Service, and the Client is only responsible for simple button icon display and custom key function implementation.
[0085] This embodiment implements the functions of user-defined function keys based on the dual-end software architecture. The specific implementation steps of the customized dual-end key settings are as follows:
[0086] 1. The two ends include the Client and the Service, and both sides realize the underlying data interaction through JNI technology.
[0087] 2. The Client is composed of two parts: the physical button display Client (multiple lightweight applications are responsible for the button icon changes) and the central control custom button Client. (The only central control application, used by users to customize which button corresponds to which function)
[0088] 3. The Service end is mainly used for signal conversion and the realization of the logical functions of hard key display.
[0089] 4. The user can select a hard key on the screen, and the operation interface sets a new response function for this key. The user clicks to confirm the change, and the change takes effect.
[0090] 5. After the user completes step 4, a message with the hard key ID and the new response function signal is sent to the Service application.
[0091] 6. The Service application determines whether the current settings are feasible.
[0092] 6.1 If the new button setting is feasible, update the vehicle signal table and update the hard button display;
[0093] 6.2 If the new button setting is not feasible, a pop-up window will be displayed to remind the user to return to step 41. The specific implementation steps for pressing the custom button include:
[0094] 2. The user randomly presses a custom hard button btn, and the hard button sends the btn_signal corresponding to btn to the Service application through the vehicle system;
[0095] 3. The Service application traverses the vehicle signal table, finds the Functional_signals corresponding to btn_signal, and sends it to the vehicle system;
[0096] 4. The vehicle system responds to the actual vehicle functions according to the signals received.
[0097] Specific steps to update the vehicle signal table:
[0098] 1. User operation central control settings custom hard button btn function
[0099] 2. The hard button sends the btn_signal and Functional_Signal corresponding to the btn to the Service application through the vehicle system
[0100] 3. The Service application has loaded the vehicle signal table into the memory when the vehicle is powered on. If the vehicle signal table does not exist in the memory, reload the vehicle signal table.
[0101] 4. The vehicle signal table is a Key\Value structure. Find the field whose Key is equal to btn_signal, rewrite the Functional_signals whose Value is, and write the updated signal table to the local disk.
[0102] 5. Every time the vehicle is powered on, the disk will load the vehicle signal table into the memory; every time the vehicle is powered off and the custom button function is set, the latest vehicle signal table will be written from the memory to the disk. The specific implementation steps for updating the vehicle signal table are:
[0103] 1. User operation: Press the hard button btn function.
[0104] 2. The hard button sends the btn_signal corresponding to btn to the Service application through the vehicle system.
[0105] 3. The Service application has loaded the vehicle signal table into the memory when the vehicle computer is powered on. The vehicle signal table is a Key\Value structure. Find the field with Key equal to btn_signal and send the Functional_signals corresponding to the Value to the vehicle computer system.
[0106] 4. After finding the field whose Key is equal to btn_signal in step 3, add one to the Key search count Time, and sort the vehicle signal table from large to small according to the Time size of each Key.
[0107] 5. Since the vehicle signal table is traversed sequentially from front to back each time, after executing step 4, the frequently used functions are sorted at the front; this will increase the speed of traversing the signal table and improve the response time of user operations.
[0108] like Figure 7 As shown, the present invention not only provides a vehicle-mounted button custom control method and system, but also provides corresponding electronic equipment, storage medium, vehicle computer and smart cockpit:
[0109] A vehicle computer is provided with the vehicle-mounted button custom control system and executes the vehicle-mounted button custom control method.
[0110] A smart cockpit, wherein the vehicle computer is arranged in the smart cockpit.
[0111] Case No.: FAW040548-C-XCN1240442 12
[0112] An electronic device comprises: 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; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method.
[0113] A computer-readable storage medium stores a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the method.
[0114] Figure 7A schematic diagram of the structure of a computer device provided in an embodiment of the present application. The device 800 includes a processor 801, a memory 802, a communication interface 803 and a bus 804. The processor 801, the memory 802 and the communication interface 803 communicate via the bus 804, and may also communicate via other means such as wireless transmission. The memory 802 is used to store instructions, and the processor 801 is used to execute instructions stored in the memory 802. The memory 802 stores program code 8021, and the processor 801 may call the program code 8021 stored in the memory 802 to execute the steps of the vehicle button custom control method.
[0115] It should be understood that in the embodiment of the present application, the processor 801 may be a CPU, and the processor 801 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0116] The memory 802 may include a read-only memory ROM and a random access memory RAM, and provide instructions and data to the processor 801. The memory 802 may also include a non-volatile random access memory. The memory 802 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory Case No.: FAW040548-C-XCN1240442 13
[0117] Random access memory (RAM) is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), and so on.
[0118] (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (doubledate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).
[0119] The bus 804 may include, in addition to the data bus, a power bus, a control bus, a status signal bus, etc. However, for the sake of clarity, various buses are labeled as the bus 804 in the figure.
[0120] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid state drive (SSD).
[0121] Case No.: FAW040548-C-XCN1240442 14
[0122] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0123] In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments. For example, any one of the embodiments claimed in the claims can be used in any combination in the embodiments of the present invention.
[0124] In the description of this specification, the description with reference to the terms "one embodiment", "example", "specific example", etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.
[0125] In addition, the technical solutions between the various embodiments of the present invention can be combined with each other, but it must be based on the fact that ordinary technicians in the field can implement it. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by the present invention.
[0126] All features disclosed in this specification, or steps in all methods or processes disclosed, except mutually exclusive features and / or steps, can be combined in any way. Any feature disclosed in this specification, unless otherwise stated, can be replaced by other equivalent or alternative features with similar purposes. That is, unless otherwise stated, each feature is only an example of a series of equivalent or similar features. Throughout the specification, the same reference numerals indicate the same elements.
[0127] Those skilled in the art will appreciate that the modules in the devices in the embodiments can be adaptively changed and set in one or more devices different from the embodiments. The modules or units or components in the embodiments can be combined into one module or unit or component, and in addition they can be divided into multiple submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including corresponding claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner can be combined in any combination. Unless otherwise explicitly stated, each feature disclosed in this specification (including corresponding claims, abstracts and drawings) can be replaced by an alternative feature that provides the same, equivalent or similar purpose.
[0128] 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 aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned 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 vehicle button custom control method, applied to a vehicle button custom control system, characterized in that: include: Setting custom function buttons based on a dual-end software architecture, the dual-end software architecture includes a client end and a service end, wherein the client end is used to set physical buttons, and the service end implements the logic functions of signal conversion and hard button display; The client side includes a display client for realizing button icon changes, and a central control custom button client for realizing user-defined functions. The client side sends a button function verification message to the service application on the service side through interactive means; The Service application on the Service side receives the button function verification message, determines the feasibility of the current setting, and if feasible, updates the vehicle signal table and notifies the Client side to update the hard button display; If this is not feasible, the client is prompted to reconfigure the buttons through interactive means.
2. The vehicle button customization control method according to claim 1, characterized in that: The dual-end software architecture implements underlying data interaction through JNI technology, where: The Client side is the user interaction interface, and the Service side is the service processing module; The client receives the hard key information selected by the user through the operation interface and sets a new response function. The client passes the newly set response function to the service through JNI; After receiving the new response function, the Service performs logical processing and feeds the processing result back to the Client through JNI.
3. The vehicle-mounted button custom control method according to claim 2, characterized in that: The client provides a user interface to allow users to select and customize the functions of hard keys; The client stores the user-defined button function settings and displays the updated display content in the client in the physical button; The client provides a confirmation button to apply the newly set response function to the selected hard key.
4. The vehicle-mounted button custom control method according to claim 2, characterized in that: The Service application on the Service end receives the button function verification message and determines the feasibility of the current setting, further comprising: The client side obtains the btn_signal information of a user randomly pressing a custom hard key, and sends the hard key information corresponding to the hard key to the Service application on the Service side through the vehicle system; The Service application on the Service side traverses the vehicle signal table, finds the function information corresponding to the custom hard key information, and sends it to the vehicle system; The vehicle system responds to the actual vehicle functions based on the signals received from the custom hard buttons.
5. The vehicle-mounted button custom control method according to claim 2, characterized in that: The dual-end software architecture realizes the underlying data interaction through JNI technology, and further includes: The Service receives the button function verification message transmitted from the Client through JNI; The server determines whether the newly set button function conflicts with the existing function or meets the system requirements based on the preset rules and logic; If the newly set button function is feasible, the Service application updates the vehicle signal table and passes the updated signal table to the Client through JNI. The Client updates the hard button display according to the updated signal table. If the newly set button function is not feasible, the Service application generates an error prompt message and passes it to the Client through JNI. After the Client receives the error prompt message, it prompts the user to re-set the button through the user interface.
6. A vehicle button custom control system, used to implement the vehicle button custom control method according to any one of claims 1 to 5, characterized in that: include: The dual-end software architecture builds an application module, and the custom function buttons are set based on the dual-end software architecture. The dual-end software architecture includes a client end and a service end, wherein the client end is used to set the physical button, and the service end realizes the logic functions of signal conversion and hard button display; The client-side function realization module includes a display client for realizing the button icon change and a central control custom button client for realizing user-defined functions. The client-side sends a button function verification message to the service application on the service side through interactive means; The service end function realization module, the service application of the service end receives the button function verification message, determines the feasibility of the current setting, and if feasible, updates the vehicle signal table and notifies the client end to update the hard button display; If this is not feasible, the client is prompted to reconfigure the buttons through interactive means.
7. A vehicle computer, characterized in that: The vehicle computer is provided with the vehicle button customization control system according to claim 6, and executes the vehicle button customization control method according to any one of claims 1 to 5.
8. A smart cockpit, characterized in that: The vehicle computer according to claim 7 is arranged in the smart cockpit.
9. An electronic device, characterized in that: include: 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; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method described in any one of claims 1 to 5.
10. A computer-readable storage medium, characterized in that: It stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the method described in any one of claims 1 to 5.
