Vehicle function calling method, electronic device and vehicle

Abstract

This application discloses a vehicle function invocation method, electronic device, and vehicle, relating to the field of vehicle control technology. The method includes: receiving invocation requests for multiple adjustment functions of a vehicle; each adjustment function corresponding to the vehicle is configured with a corresponding first counter; in response to the invocation requests for multiple adjustment functions, incrementing the count value of the target first counter corresponding to each of the multiple adjustment functions, and reading the latest total invocation value recorded by a second counter; the second counter is used to count independently of the first counter and in an accumulating manner each time an invocation request for any adjustment function is received; and generating adjustment function trigger signals corresponding to the multiple target first counters based on the current count value and the latest total invocation value. This application can improve the reliability and accuracy of vehicle adjustment function invocation.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a method for invoking vehicle functions, electronic equipment, and a vehicle. Background Technology

[0002] Currently, vehicle cabins are generally equipped with personalized functions such as seat position adjustment and steering wheel position adjustment, which users can access and save. These functions can usually be accessed by users through buttons or voice commands when needed.

[0003] Function call identification is usually achieved using a counter mechanism. This involves configuring a dedicated counter for each function and setting a common call count flag. The initial value of the flag is 0 (0 indicates no new request, and 1 indicates a new request). When a function is triggered, the corresponding dedicated counter value is incremented by one and then assigned to the count flag. When a change in the count flag value is detected, it is determined that there is a new instruction and the corresponding function is executed.

[0004] However, when two or more different functions are called in succession within a short period of time, their corresponding dedicated counter values ​​may increase to the same value simultaneously. At this time, since the counter flag does not have time to be reset to zero between multiple calls, the value of the counter flag does not change after multiple assignments, which leads to a misjudgment that there is no new instruction, causing subsequent function calls to fail and resulting in a poor user experience. Summary of the Invention

[0005] This application provides a method for invoking vehicle functions, an electronic device, and a vehicle, which can accurately invoke various functions in the vehicle.

[0006] This application provides a method for invoking vehicle functions, including: Receive requests for multiple adjustment functions of the vehicle; The vehicle is equipped with a corresponding first counter for each of its different adjustment functions. The first counter is used to record the number of times the corresponding adjustment function is called. In response to the call requests of the multiple adjustment functions, the count values ​​of the target first counters corresponding to the multiple adjustment functions are incrementally updated, and the latest total call value recorded by the second counter is read. The second counter is used to count independently of the first counter each time a request to invoke any adjustment function is received; Based on the current count value corresponding to the multiple target first counters and the latest total call value, an adjustment function trigger signal corresponding to each of the multiple target first counters is generated.

[0007] This application configures an independent first counter for each adjustment function to record the corresponding number of calls, and a second counter, independent of the first counter and monotonically increasing, to record the total number of global calls. When responding to a call request, the count values ​​of the two counters are updated synchronously, and the corresponding adjustment function trigger signal is generated by combining the count values ​​of the two counters. This avoids the misjudgment problem caused by the traditional shared counter identifier not having time to return to zero and the count values ​​overlapping. It ensures that every adjustment function call request can be accurately identified and triggered, improving the reliability and accuracy of vehicle adjustment function calls and execution, while optimizing the user's driving experience.

[0008] Optionally, generating adjustment function trigger signals corresponding to the multiple target first counters based on the current count values ​​corresponding to the multiple target first counters and the latest total call value includes: obtaining the historical total call value corresponding to the second counter, and comparing the latest total call value with the historical total call value; the historical total call value is the second counter value recorded when the adjustment function trigger signal was last generated; if the latest total call value is different from the historical total call value, then multiple adjustment functions to be executed are determined according to the current count values ​​of the multiple target first counters, and adjustment function trigger signals corresponding to the multiple adjustment functions to be executed are generated.

[0009] In this optional implementation, by comparing the latest total call value of the second counter with the historical total call value recorded when the trigger signal was last generated, it is possible to accurately determine whether a new call request has been generated, avoiding misjudgments caused by the traditional identifier not having enough time to be zeroed; when it is determined that a new request exists due to different values, the current count values ​​of multiple target first counters are combined to accurately determine the adjustment function to be executed, which can effectively identify multiple call requests, ensure that each adjustment function can be triggered and executed normally, and improve the accuracy of identification and the stability of function operation.

[0010] Optionally, the step of determining multiple adjustment functions to be executed based on the current count values ​​of multiple target first counters, and generating adjustment function trigger signals corresponding to multiple adjustment functions to be executed, includes: For each of the target first counters, determine whether the current count value of the target first counter is consistent with the previous historical record value; If not, the adjustment function corresponding to the target first counter where the current count value is inconsistent with the historical record value is determined as the adjustment function to be executed, and the adjustment function trigger signal corresponding to the adjustment function to be executed is generated.

[0011] In this optional implementation, by comparing the current count value of each target first counter with the historical record value one by one, the adjustment function that made the call request can be accurately identified, ensuring that multiple triggered functions can be effectively distinguished. By generating a separate trigger signal for the target first counter whose count value changes, it can be ensured that each adjustment function request is executed reliably, avoiding the identification failure problem caused by continuous triggering of multiple functions in the traditional mechanism, and further improving the identification accuracy and function execution stability.

[0012] Optionally, the method further includes: monitoring the operating status of the vehicle, and when the operating status of the vehicle is waking up from a hibernation state, initializing each of the first counters to a corresponding first preset initial value and the second counters to a corresponding second preset initial value. In this optional implementation, by uniformly initializing each of the first and second counters when the vehicle wakes up from hibernation, the residual count values ​​from the previous working cycle can be cleared, ensuring that both types of counters start counting again from a unified and stable preset initial value. This avoids problems such as counting anomalies and value overlap caused by historical counting interference, further ensuring that multiple adjustment function call requests can be accurately identified, and effectively improving counting reliability and function execution stability.

[0013] Optionally, after generating adjustment function trigger signals corresponding to the plurality of target first counters respectively, the method further includes: obtaining the receiving timestamps of the call requests corresponding to the plurality of adjustment functions; and, in response to the adjustment function trigger signals, executing the adjustment functions corresponding to the call requests sequentially based on the receiving timestamps of the call requests.

[0014] In this optional implementation, by obtaining the timestamp of the call request and executing the adjustment function based on its order, the timing relationship of multiple function calls within a preset time period can be accurately distinguished, and sequential and orderly serial execution can be achieved. This effectively avoids execution chaos or conflict caused by concurrent or sequential calls of multiple functions, further improving the stability and accuracy of operation and optimizing the user's actual driving experience.

[0015] Optionally, the method further includes: when at least two of the call requests have the same timestamp, obtaining the priority corresponding to the call request; and determining the execution order of the adjustment function corresponding to the call request based on the priority.

[0016] In this optional implementation, when multiple adjustment function call requests have the same timestamp and cannot be distinguished in sequence, the execution order can be determined by obtaining and based on the preset priority, which can effectively avoid function execution conflicts and confusion, ensure that high-priority functions respond first, and improve the rationality, stability and safety of vehicle adjustment function execution.

[0017] Optionally, the step of incrementally updating the count values ​​of the target first counters corresponding to the plurality of adjustment functions in response to the call requests of the plurality of adjustment functions includes: obtaining the target first counters corresponding to the plurality of adjustment functions based on a preset counter mapping table; the preset counter mapping table is used to record the mapping relationship between the adjustment functions in the vehicle cabin and the corresponding first counters; and incrementally updating the count values ​​of the target first counters corresponding to the plurality of adjustment functions.

[0018] In this optional implementation, the target first counter corresponding to each adjustment function is determined based on a preset counter mapping table, ensuring that the function and the counter correspond one-to-one and count independently, avoiding counting interference between multiple functions; by performing an increment operation on each target first counter, the number of times each adjustment function is called can be accurately recorded, providing a reliable data foundation for subsequent accurate identification and triggering of the corresponding function.

[0019] Optionally, the method further includes: when receiving consecutive call requests for the same adjustment function, obtaining the time interval between two adjacent call requests; determining whether the time interval is less than a preset anti-jitter time threshold; if so, determining the most recent call request as an invalid request so that the first counter and the second counter do not perform the count value update operation; if not, determining the most recent call request as a valid request so that the first counter and the second counter perform the count value update operation.

[0020] In this optional implementation, by obtaining the time interval between adjacent call requests and comparing it with a preset threshold, it can effectively identify and filter consecutive invalid requests for the same adjustment function in a short period of time caused by accidental touch, button bounce, or poor contact. This avoids the counter being frequently updated by invalid requests, ensuring the accuracy of the counting data and the reliability of function triggering. At the same time, it retains the execution permission for valid consecutive calls, improving the anti-interference capability of vehicle control and the fault tolerance of user operation.

[0021] This application also provides a vehicle function recall device, including: A receiving unit is configured to receive calls for multiple adjustment functions of a vehicle; wherein, each adjustment function corresponding to the vehicle is configured with a corresponding first counter, the first counter being used to record the number of times the corresponding adjustment function is called; The update unit is configured to, in response to the call requests of the plurality of adjustment functions, incrementally update the count values ​​of the target first counters corresponding to the plurality of adjustment functions respectively, and read the latest total call value recorded by the second counter; wherein, the second counter is configured to count independently of the first counter and in an accumulating manner each time a call request for any adjustment function is received; The generation unit is used to generate adjustment function trigger signals corresponding to the multiple target first counters based on the current count values ​​corresponding to the multiple target first counters and the latest total call value.

[0022] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of any of the above-described vehicle function invocation methods.

[0023] This application also provides a vehicle, including a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to implement any of the vehicle function invocation methods described above.

[0024] This application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of any of the above-described vehicle function invocation methods.

[0025] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described vehicle function invocation methods. Attached Figure Description

[0026] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is one of the flowcharts illustrating a vehicle function invocation method provided in an embodiment of this application; Figure 2 A second schematic flowchart illustrating a vehicle function invocation method provided in this application embodiment; Figure 3 The third flowchart illustrates a method for invoking vehicle functions provided in this application. Figure 4 This is a schematic diagram of a vehicle function calling device provided in an embodiment of this application. Detailed Implementation

[0028] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0029] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0030] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0031] An embodiment of this application provides a method for invoking vehicle functions, referring to... Figure 1 The diagram shown is a flowchart of a vehicle function invocation method, which includes the following steps: S11. Receive requests to call multiple adjustment functions for the vehicle.

[0032] The vehicle is equipped with a corresponding first counter for each of its different adjustment functions. The first counter is used to record the number of times the corresponding adjustment function is called.

[0033] In some embodiments, when multiple adjustment function call requests are issued in succession within a short period of time, such as shortly after the vehicle is awakened from hibernation, the welcome call function and the seat memory function are triggered in succession. The traditional counting mechanism uses a shared counting identifier, which may cause the counting identifier to fail to return to zero in short-term continuous call scenarios, resulting in duplicate and overlapping count values. This leads to the system being unable to accurately distinguish between different call requests, ultimately causing function calls to fail or be missed.

[0034] To address the aforementioned issues, the vehicle function call method provided in this application, through a dual-counter counting logic where the first counter and the second counter are independent of each other, can effectively avoid the defects caused by sharing a counting identifier.

[0035] Specifically, the adjustment functions are a variety of functions in the vehicle that can be called by the user, including but not limited to functions that can be customized by the driver or passengers, such as seat position adjustment, steering wheel position adjustment, rearview mirror angle adjustment, seat welcome function activation, and cabin air conditioning preset mode adjustment; the trigger source for the call request may include physical button or touch operation of the in-vehicle human-machine interaction unit, voice command, automatic triggering of the vehicle's central electronic module (such as the welcome function after sleep wake-up), etc.

[0036] Furthermore, a unique first counter is pre-configured for each independent adjustment function. Each first counter counts independently and separately. Its core function is to accurately record the cumulative number of times the corresponding adjustment function is triggered. The initial count value of each first counter is 0, and the count value is incremented after each call request for the corresponding adjustment function is received.

[0037] For example, a first counter A is configured for the welcome call function, and a first counter B is configured for the seat memory function. When the welcome call function is triggered, the count value of the first counter A is incremented by one, and when the seat memory function is triggered, the count value of the first counter B is incremented by one.

[0038] S12. In response to the call request of the plurality of adjustment functions, the count value of the target first counter corresponding to the plurality of adjustment functions is incrementally updated, and the latest total call value recorded by the second counter is read.

[0039] The second counter is used to count independently of the first counter each time a request to invoke any adjustment function is received.

[0040] In this embodiment of the application, after receiving a call request for multiple adjustment functions from the vehicle cabin, both types of counters need to update their count values.

[0041] Specifically, when incrementally updating the count values ​​of the target first counters corresponding to the multiple adjustment functions, for each adjustment function that initiates a call request, the count value of its uniquely corresponding target first counter will be incrementally updated. The incremental update refers to accumulating the historical count value recorded in the previous instance of the target first counter, that is, recording the number of times the corresponding adjustment function is called this time, and accumulating the count incrementally based on the number of times it is called. The first counters corresponding to adjustment functions that are not called will keep their original count values ​​unchanged.

[0042] For example, if a user requests the seat adjustment function once, the count value of the first counter corresponding to the seat adjustment function will be incrementally updated based on the current value. For instance, if the current value is 2, it needs to be incremented from 2 to 3. Similarly, if the user requests the seat adjustment function twice, the count value of the first counter corresponding to the seat adjustment function will be incrementally updated twice consecutively based on the current value, increasing from 2 to 3, and then from 3 to 4. The first counters corresponding to other uncalled adjustment functions will remain unchanged. The same applies to other called functions; that is, each adjustment function request only triggers an update to its own corresponding first counter, while the first counters corresponding to other uncalled adjustment functions remain unchanged, ensuring that each first counter accurately and independently records the number of calls for a single function.

[0043] Specifically, after receiving multiple request calls for adjustment functions, regardless of the adjustment function or the corresponding call source, the second counter will perform an update operation for each request received. That is, the second counter will increment once. For example, after the vehicle is powered on and woken up, the seat adjustment is triggered once and the rearview mirror adjustment is triggered once in sequence. The first seat call will cause the value of the second counter to be incremented from the initial value, that is, the second counter will increase from the initial value of 0 to 1. The subsequent rearview mirror call will trigger the value to be incremented again, that is, the second counter will increase from the current base value of 1 to 2. Each independent call request corresponds to a count update, so as to reflect the call frequency in a true way through the value change.

[0044] It should be noted that the second counter can be understood as a pre-configured, globally unique global counter. This counter is independent of all first counters and is not bound to any individual adjustment function. It is used to record the total number of calls to all adjustment functions in the vehicle cabin and adopts an additive counting method. That is, no matter which adjustment function call request is received, and no matter whether the call request is initiated individually or multiple times sequentially, the count value of the second counter is updated once a call request for any adjustment function is received. Finally, the updated count value is determined as the latest total call value.

[0045] Furthermore, when multiple adjustment functions issue call requests in succession, the second counter will continuously increment with each request, ensuring that the latest total call value is a globally unique incrementing value, thus completely avoiding the problem of the shared counter value remaining unchanged in the traditional mechanism.

[0046] It should be noted that the embodiments of this application also include a counter initialization step, which is used to uniformly reset each counter under specific vehicle conditions to avoid subsequent call identification errors due to residual historical count values ​​or count disorder. The specific steps are as follows: Monitor the vehicle's operating status, and when the vehicle's operating status is waking up from hibernation, initialize each of the first counters to the corresponding first preset initial value and the second counters to the corresponding second preset initial value. In this embodiment of the application, the current operating status of the vehicle will be monitored in real time, including but not limited to hibernation state, standby state, normal working state, power-on state, power-off state, and hibernation wake-up state.

[0047] Furthermore, by continuously monitoring the vehicle's operating status, it is possible to accurately identify when the vehicle switches from a low-power sleep mode to a normal operating mode. When the vehicle's operating status is detected as waking up from sleep mode, it indicates that the vehicle is about to enter a high-risk scenario involving multi-functional centralized triggering and short-term continuous calls. To avoid interference from residual count values ​​from the previous cycle in identifying the current call, and to ensure that the count starts from zero and is accurate and reliable within the current call cycle, the first counter is initialized to a first preset initial value, and the second counter is initialized to a second preset initial value.

[0048] Specifically, for the first counter corresponding to each adjustment function, it is uniformly initialized to a preset first initial value (for example, the first preset initial value is 0). At the same time, the global second counter is initialized to the corresponding second preset initial value (for example, the second preset initial value is 0). Since the second counter adopts a global monotonically increasing mechanism, the consistency of its initial value directly determines the accuracy of the subsequent total call count identification.

[0049] Furthermore, by uniformly initializing each of the first and second counters when the vehicle wakes up from hibernation, the residual count values ​​from the previous working cycle can be cleared, ensuring that both types of counters start counting again from a unified and stable preset initial value. This avoids problems such as counting anomalies and value overlap caused by historical counting interference, and further ensures that multiple adjustment function call requests issued after the vehicle wakes up can be accurately identified, effectively improving counting reliability and function execution stability.

[0050] S13. Based on the current count value corresponding to the multiple target first counters and the latest total call value, generate adjustment function trigger signals corresponding to the multiple target first counters respectively.

[0051] Specifically, in this step, it is necessary to first obtain the historical total call value corresponding to the second counter when the trigger signal was last generated, and then compare the current latest total call value with the historical total call value.

[0052] If the two are different, it indicates that a new call request has arrived, and it is necessary to further determine the type of adjustment function to be executed based on the current count value of each first counter.

[0053] Then, the current count value of each first counter is obtained, and it is compared with its corresponding historical record value. The adjustment function corresponding to the first counter whose current count value has changed compared with the historical record value is determined as the adjustment function to be executed, and a trigger signal corresponding to the adjustment function is generated.

[0054] For example, after the previous adjustment function was triggered, the value of the first counter A was 1, the value of the first counter B was 0, and the value of the second counter was 1. When a new call request is received, the first counter B is updated to 1, and the second counter is updated to 2. The change of the second counter value from 1 to 2 is detected, indicating a new request. Subsequently, the first counters are compared, and it is found that the value of the first counter B has changed from 0 to 1, while the value of the first counter A remains unchanged. Therefore, the function to be executed is determined to be the seat memory function corresponding to the first counter B, and a corresponding trigger signal is generated.

[0055] Based on the above S11-S13, this application embodiment configures an independent first counter for different adjustment functions to record the corresponding number of calls, and a second counter, independent of the first counter and monotonically increasing, records the total number of global calls. When responding to a call request, the count values ​​of the two counters are updated synchronously, and the corresponding adjustment function trigger signal is generated by combining the count values ​​of the two counters. This avoids the misjudgment problem caused by the traditional shared counting identifier not having time to return to zero and the count values ​​overlapping. It ensures that every adjustment function call request can be accurately identified and triggered, improves the reliability and accuracy of vehicle cabin adjustment function calls, and optimizes the user's driving experience.

[0056] As an extension and refinement of the above embodiments, refer to Figure 2 As shown, this application embodiment also provides another method for invoking vehicle functions, specifically including the following steps S21-S27: S21. Receive requests to call multiple adjustment functions for the vehicle.

[0057] The vehicle is equipped with a corresponding first counter for each of its different adjustment functions. The first counter is used to record the number of times the corresponding adjustment function is called.

[0058] S22. In response to the call request of the plurality of adjustment functions, obtain the target first counter corresponding to the plurality of adjustment functions based on the preset counter mapping table.

[0059] The preset counter mapping table is used to record the mapping relationship between the adjustment functions in the vehicle cabin and the corresponding first counter.

[0060] Specifically, after receiving multiple adjustment function call requests, the system queries and determines the first counter uniquely corresponding to each adjustment function according to the preset counter mapping table, and records it as the target first counter.

[0061] The preset counter mapping table can be pre-stored in the vehicle to establish and solidify the binding relationship between each adjustment function and its respective first counter, ensuring that different adjustment functions use independent counters, without interfering with or overwriting each other, thus providing a basis for subsequent independent counting.

[0062] S23. Incrementally update the count values ​​of the target first counters corresponding to the plurality of adjustment functions respectively.

[0063] Specifically, since each target's first counter is independent of the others and is only updated when its corresponding adjustment function is called, it can accurately and independently record the number of times each adjustment function is called, and will not be affected by the call of other adjustment functions.

[0064] For multiple call requests issued, the first counters of multiple targets are incremented and updated to ensure that each call request is recorded accurately, avoiding omissions or misrecording, and providing a reliable basis for subsequent identification of functions to be executed.

[0065] Based on the above S22-S23, the target first counter corresponding to each adjustment function is determined by the preset counter mapping table, ensuring that the function and the counter correspond one-to-one and count independently, avoiding counting interference between multiple functions; by performing an increment operation on each target first counter, the number of times each adjustment function is called can be accurately recorded, providing a reliable data foundation for subsequent accurate identification and triggering of the corresponding function.

[0066] S24. Obtain the historical total call value corresponding to the second counter, and compare the latest total call value with the historical total call value.

[0067] The historical total call value is the value of the second counter recorded when the adjustment function trigger signal was last generated.

[0068] In this embodiment, the historical total call value is saved. This historical total call value is the count value of the second counter that was synchronously recorded when the adjustment function trigger signal was successfully generated last time. Between the generation of two trigger signals, the historical total call value remains static and does not change synchronously with the real-time update of the second counter, thus ensuring the stability and accuracy of the comparison benchmark.

[0069] Furthermore, after obtaining the historical total call value, a numerical comparison operation will be performed immediately to compare the latest total call value of the current second counter with the statically stored historical total call value.

[0070] Specifically, if a new call request exists, the second counter will inevitably be incremented and updated, and the latest total call value will be different from the historical total call value; if no new call request exists, the value of the second counter remains unchanged, and the latest total call value remains consistent with the historical total call value, thereby achieving preliminary screening of new call requests and completely avoiding the misjudgment problem in the traditional mechanism caused by the shared counter not having time to be reset to zero, which resulted in new requests but the value remaining unchanged.

[0071] Meanwhile, when multiple adjustment functions are invoked after the vehicle wakes up from hibernation, the global count change corresponding to this call request can be quickly identified by comparing the historical total call value with the latest total call value, laying the foundation for locating subsequent functions to be executed.

[0072] S25. If the latest total call value is different from the historical total call value, then based on the current count values ​​of the multiple target first counters, multiple adjustment functions to be executed are determined, and adjustment function trigger signals corresponding to the multiple adjustment functions to be executed are generated.

[0073] Specifically, when the latest total call value is detected to be different from the historical total call value, it can be clearly determined that there is a new adjustment function call request. It may be a single call request or multiple call requests issued successively within a preset time period. At this time, the process enters the function location and trigger signal generation stage.

[0074] The current count value of the multiple target first counters is the value after the first counter of each corresponding adjustment function is updated by one after responding to the multiple call requests. Each target first counter corresponds to the corresponding adjustment function, and they are independent of each other and their counting does not interfere with each other.

[0075] Then, by comparing the current count values ​​of each target's first counter, the target's first counter whose count value has changed is selected to determine multiple adjustment functions to be executed.

[0076] Based on the above S24-S25, by comparing the latest total call value of the second counter with the historical total call value recorded when the trigger signal was generated last time, it is possible to accurately determine whether a new call request has been generated, avoiding misjudgment caused by the traditional identifier not having enough time to be zeroed; when it is determined that there is a new request due to different values, the current count values ​​of multiple target first counters are combined to accurately determine the adjustment function to be executed, which can effectively identify multiple call requests, ensure that each adjustment function can be triggered and executed normally, and improve the accuracy of identification and the stability of function operation.

[0077] It should be noted that the above-mentioned S25, "determining multiple adjustment functions to be executed based on the current count values ​​of multiple target first counters, and generating adjustment function trigger signals corresponding to multiple adjustment functions to be executed", can be further refined into the following S251-S252: S251. For each of the target first counters, determine whether the current count value of the target first counter is consistent with the previous historical record value.

[0078] In this step, the first counter of each target is judged independently in turn, and its current count value is compared with the previously stored historical record value.

[0079] The current count value is the value of the target first counter after it is incremented by one after responding to the current adjustment function call request; the previous historical record value is the value of the target first counter recorded when the adjustment function trigger signal was generated last time, which remains static between the two determinations and is only used as the benchmark for this comparison.

[0080] Furthermore, by enumerating and testing one by one, it is possible to accurately determine which target first counters have changed counts during this call, thereby distinguishing between the triggered adjustment functions and the untriggered adjustment functions.

[0081] S252. If not, then the adjustment function corresponding to the target first counter where the current count value is inconsistent with the historical record value is determined as the adjustment function to be executed, and the adjustment function trigger signal corresponding to the adjustment function to be executed is generated.

[0082] Specifically, if the judgment result is that the current count value is inconsistent with the previous historical record value, it indicates that the adjustment function corresponding to the first counter of the target has received a new call request, and the adjustment function is determined to be the adjustment function to be executed.

[0083] Furthermore, a unique corresponding adjustment function trigger signal is generated for the adjustment function to be executed, which is used to drive the vehicle actuator to complete the corresponding adjustment action. Since this step independently judges and processes the first counter of each target, even if multiple adjustment functions are called sequentially or simultaneously, they can be identified one by one and trigger signals can be generated separately. There will be no missed judgment, misjudgment or function failure due to overlapping counts or the fact that the identifier cannot be zeroed in time, ensuring that all call requests can be accurately responded to and executed.

[0084] Based on the above S251-S252, by comparing the current count value of each target's first counter with the historical record value one by one, the adjustment function that has made the call request can be accurately identified, ensuring that multiple triggered functions can be effectively distinguished. By generating a separate trigger signal for the target's first counter whose count value changes, it can be ensured that each adjustment function request is executed reliably, avoiding the identification failure problem caused by continuous triggering of multiple functions in the traditional mechanism, and further improving the identification accuracy and function execution stability.

[0085] S26. Obtain the timestamps of the call requests corresponding to multiple adjustment functions.

[0086] In the process, when multiple adjustment function calls are received from within the vehicle cabin, a timing operation is triggered simultaneously to generate and obtain a unique receiving timestamp for each received call request.

[0087] The received timestamp is a time identifier that represents the actual time when the call request is received. It can be generated by a real-time clock module (RTC) or a high-precision timer and includes time dimension information such as year, month, day, hour, minute, second, and millisecond.

[0088] By obtaining this timestamp, the receiving order of each adjustment function call request can be accurately recorded, and the correspondence between each call request and time node can be established, laying the foundation for subsequent orderly execution.

[0089] S27. In response to the adjustment function trigger signal, based on the timestamp of the received call request, the adjustment function corresponding to the call request is executed sequentially.

[0090] Specifically, once an adjustment function trigger signal for multiple adjustment functions to be performed is generated in step S25, the system responds to the trigger signal and enters the execution process.

[0091] Then, the receiving timestamps of each call request recorded in step S26 are retrieved, and the multiple adjustment function call requests to be executed are sorted according to the time sequence of the timestamps.

[0092] Subsequently, based on the principle of sequential execution, control commands are sent to the corresponding actuators in the vehicle (such as seat adjustment motors, steering wheel adjustment motors, etc.) in sequence, driving the actuators to perform the corresponding adjustment actions in chronological order.

[0093] It should be noted that if multiple adjustment functions issue call requests almost simultaneously within a preset time period, the subtle differences in their order can be further distinguished by the millisecond-level precision of the timestamp, thereby achieving accurate and orderly execution of multiple call requests.

[0094] Based on the above S26-S27, by obtaining the timestamp of the call request and executing the adjustment function according to its order, the timing relationship of multiple function calls within a preset time period can be accurately distinguished, and sequential and orderly serial execution can be achieved. This effectively avoids execution chaos or conflict caused by concurrent or sequential calls of multiple functions, further improving the stability of operation and the accuracy of execution, and optimizing the user's actual driving experience.

[0095] It should be noted that the execution of S27 above further includes the following steps 1 and 2: Step 1: When at least two of the call requests have the same timestamp, obtain the priority corresponding to the call request.

[0096] When multiple request calls for adjustment functions are received at the same time, resulting in identical timestamps and making it impossible to distinguish the execution order based on time sequence, a preset priority corresponding to each request is further obtained. This priority is a pre-configured execution priority level used to differentiate the importance of different adjustment functions. For example, functions related to driving safety and driver control have a higher priority than ordinary comfort adjustment functions, thus ensuring that a reasonable execution order can still be determined even when timestamps cannot distinguish the timing.

[0097] Step 2: Determine the execution order of the adjustment functions corresponding to the call request based on priority.

[0098] Based on the priority of each adjustment function, multiple call requests with the same timestamp are sorted, with higher-priority adjustment functions executed first and lower-priority adjustment functions executed last. This priority sorting rule avoids execution conflicts, chaos, or disordered concurrency caused by multiple requests with the same timestamp, ensuring that the adjustment functions within the vehicle cabin are executed in an orderly, stable, and reasonable sequence, balancing reliability and safety.

[0099] Based on steps 1 and 2 above, when multiple adjustment function call requests have the same timestamp and cannot be distinguished in sequence, the execution order can be determined by obtaining and based on the preset priority. This can effectively avoid function execution conflicts and confusion, ensure that high-priority functions respond first, and improve the rationality, stability and safety of vehicle adjustment function execution.

[0100] As an extension and refinement of the above embodiments, refer to Figure 3 As shown, this application embodiment also provides a vehicle function invocation method, including the following steps S31-S34: S31. When receiving consecutive call requests for the same adjustment function, obtain the time interval between two adjacent call requests.

[0101] In some embodiments, when a series of calls for the same adjustment function are received, for example, when a user initiates multiple requests for the same function in a short period of time due to button sticking, accidental touch, or rapid repeated pressing, the receiving time of each call request will be automatically recorded, i.e., the precise receiving timestamp.

[0102] Furthermore, the time difference between two adjacent call requests is calculated and obtained, which is the time interval between two adjacent call requests. This time interval provides a key quantitative basis for quantifying user operation intentions and accidental touch interference, and is a prerequisite for distinguishing between valid requests and invalid jitter requests.

[0103] S32. Determine whether the time interval is less than the preset anti-shake time threshold.

[0104] Then, the time interval obtained by S31 is compared with the preset anti-shake time threshold.

[0105] The preset anti-shake time threshold is an empirical value pre-set based on the actual human-computer interaction needs and hardware response characteristics of the vehicle's cabin adjustment function.

[0106] Furthermore, by determining whether the time interval is less than a preset threshold, it is possible to accurately distinguish which are intentional continuous operations by the user and which are repeated jitter requests in a short period of time caused by hardware button rebound, poor contact, or accidental touch.

[0107] In the above S32, if the time interval is less than the preset anti-shake time threshold, then the following S33 is executed; if the time interval is greater than or equal to the preset anti-shake time threshold, then the following S34 is executed. S33. Determine the most recent call request as an invalid request so that the first counter and the second counter do not perform the count value update operation.

[0108] In this embodiment, if the determination result shows that the time interval between two adjacent call requests is less than a preset debouncing threshold, it indicates that the most recent call request is highly likely to be an invalid interference signal caused by accidental touch, key bounce, or misoperation. In this case, a masking process is performed: the most recent call request is determined to be an invalid request. In the invalid request state, the call request is completely ignored, and the first counter (the single-function counter corresponding to the adjustment function) and the second counter (the global total call counter) will not continue to update their count values; thus effectively avoiding frequent counter jumps due to accidental touches, ensuring the purity of the counting logic and the accuracy of function triggering.

[0109] S34. Determine the most recent call request as a valid request, so that the first counter and the second counter perform a count value update operation.

[0110] In this embodiment of the application, if the determination result shows that the time interval between two adjacent call requests is greater than or equal to the preset debouncing threshold, it indicates that the user's operation is continuous and intentional, and the most recent call request is a valid request.

[0111] At this point, the validity of the call request is confirmed, and the counting update process is triggered normally. This involves incrementally updating the count value of the first counter corresponding to the adjustment function to accurately record the actual number of calls to the adjustment function. Simultaneously, the second counter is triggered to update its count value to generate the latest total call value.

[0112] This application embodiment obtains the time interval between adjacent call requests and compares it with a preset threshold. This can effectively identify and filter consecutive invalid requests for the same adjustment function in a short period of time caused by accidental touch, key bounce, or poor contact. This avoids the counter being frequently updated by invalid requests, ensuring the accuracy of the counting data and the reliability of function triggering. At the same time, it retains the execution permission of valid consecutive calls, improving the anti-interference capability and the fault tolerance of user operation.

[0113] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0114] Embodiments of this application also provide a vehicle function invocation device, which corresponds one-to-one with the method claims. Figure 4 This is a structural schematic diagram of the vehicle function call device 400 provided in this disclosure, as shown below. Figure 4 As shown, the device 400 of this embodiment includes: The receiving unit 41 is used to receive multiple call requests for adjustment functions of the vehicle; wherein, each adjustment function corresponding to the vehicle is configured with a corresponding first counter, and the first counter is used to record the number of times the corresponding adjustment function is called; The update unit 42 is used to respond to the call request of the plurality of adjustment functions by incrementally updating the count value of the target first counter corresponding to the plurality of adjustment functions respectively, and reading the latest total call value recorded by the second counter; wherein, the second counter is used to count independently of the first counter and in an accumulating manner each time a call request of any adjustment function is received; The generation unit 43 is used to generate adjustment function trigger signals corresponding to the multiple target first counters based on the current count values ​​corresponding to the multiple target first counters and the latest total call value.

[0115] As an optional implementation of this application, the generation unit 43 is specifically used to obtain the historical total call value corresponding to the second counter, and compare the latest total call value with the historical total call value; the historical total call value is the value of the second counter recorded when the adjustment function trigger signal was generated last time; if the latest total call value is different from the historical total call value, then based on the current count value of the multiple target first counters, multiple adjustment functions to be executed are determined, and multiple adjustment function trigger signals corresponding to the multiple adjustment functions to be executed are generated.

[0116] As an optional implementation of this application, the updating unit 42 is further configured to determine whether the current count value of each target first counter is consistent with the previous historical record value; if not, the adjustment function corresponding to the target first counter whose current count value is inconsistent with the historical record value is determined as the adjustment function to be executed, and the adjustment function trigger signal corresponding to the adjustment function to be executed is generated.

[0117] As an optional implementation of this application, the generation unit 43 is specifically used to monitor the operating status of the vehicle, and when the operating status of the vehicle is waking up from a hibernation state, initialize each of the first counters to the corresponding first preset initial value and the second counters to the corresponding second preset initial value. As an optional implementation of this application, the generation unit 43 is further configured to obtain the receiving timestamps of the call requests corresponding to multiple adjustment functions; in response to the adjustment function trigger signal, the adjustment functions corresponding to the call requests are executed sequentially based on the receiving timestamps of the call requests.

[0118] As an optional implementation of this application, the generation unit 43 is further configured to obtain the priority corresponding to the call request when there are at least two call requests with the same timestamp; and determine the execution order of the adjustment function corresponding to the call request according to the priority.

[0119] As an optional implementation of this application, the update unit 42 is specifically used to respond to the call request of the plurality of adjustment functions, obtain the target first counter corresponding to the plurality of adjustment functions based on a preset counter mapping table; the preset counter mapping table is used to record the mapping relationship between the adjustment functions in the vehicle cabin and the corresponding first counters; and incrementally update the count values ​​of the target first counters corresponding to the plurality of adjustment functions.

[0120] As an optional implementation of this application, the receiving unit 41 is further configured to, when receiving consecutive call requests for the same adjustment function, obtain the time interval between two adjacent call requests; determine whether the time interval is less than a preset anti-jitter time threshold; if so, determine the most recent call request as an invalid request so that the first counter and the second counter do not perform the count value update operation; if not, determine the most recent call request as a valid request so that the first counter and the second counter perform the count value update operation.

[0121] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the vehicle function invocation method embodiments described above.

[0122] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the vehicle function invocation method embodiments described above when it is run.

[0123] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0124] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the vehicle function invocation method embodiments described above.

[0125] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps in any of the vehicle function invocation method embodiments described above.

[0126] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0127] The foregoing has provided a detailed description of a vehicle function invocation method, electronic device, and vehicle provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to aid in understanding the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A vehicle function calling method, characterized by, include: Receive requests for multiple adjustment functions of the vehicle; The vehicle is equipped with a corresponding first counter for each of its different adjustment functions. The first counter is used to record the number of times the corresponding adjustment function is called. In response to the call requests of the multiple adjustment functions, the count values ​​of the target first counters corresponding to the multiple adjustment functions are incrementally updated, and the latest total call value recorded by the second counter is read. The second counter is used to count independently of the first counter each time a request to invoke any adjustment function is received; Based on the current count value corresponding to the multiple target first counters and the latest total call value, an adjustment function trigger signal corresponding to each of the multiple target first counters is generated.

2. The method of claim 1, wherein, The step of generating adjustment function trigger signals corresponding to the multiple target first counters based on the current count values ​​corresponding to the multiple target first counters and the latest total call value includes: Obtain the historical total call value corresponding to the second counter, and compare the latest total call value with the historical total call value; the historical total call value is the value of the second counter recorded when the adjustment function trigger signal was last generated. If the latest total call value is different from the historical total call value, then based on the current count values ​​of the multiple target first counters, multiple adjustment functions to be executed are determined, and adjustment function trigger signals corresponding to the multiple adjustment functions to be executed are generated.

3. The method of claim 2, wherein, The step of determining multiple adjustment functions to be executed based on the current count values ​​of multiple target first counters, and generating adjustment function trigger signals corresponding to multiple adjustment functions to be executed, includes: For each of the target first counters, determine whether the current count value of the target first counter is consistent with the previous historical record value; If not, the adjustment function corresponding to the target first counter where the current count value is inconsistent with the historical record value is determined as the adjustment function to be executed, and the adjustment function trigger signal corresponding to the adjustment function to be executed is generated.

4. The method of claim 1, wherein, The method further includes: Monitor the vehicle's operating status, and when the vehicle's operating status is waking up from hibernation, initialize each of the first counters to the corresponding first preset initial value and the second counters to the corresponding second preset initial value.

5. The method of claim 1, wherein, After generating adjustment function trigger signals corresponding to the plurality of target first counters respectively, the method further includes: Obtain the timestamps of the received calls for the multiple adjustment functions; In response to the adjustment function trigger signal, the adjustment function corresponding to the call request is executed sequentially based on the timestamp of the call request.

6. The method of claim 5, wherein, The method further includes: When at least two of the call requests have the same timestamp, obtain the priority corresponding to the call request; The execution order of the adjustment functions corresponding to the call request is determined based on priority.

7. The method of claim 1, wherein, The step of incrementally updating the count values ​​of the target first counters corresponding to the plurality of adjustment functions in response to the call requests of the plurality of adjustment functions includes: In response to the call request of the plurality of adjustment functions, the target first counter corresponding to each of the plurality of adjustment functions is obtained based on a preset counter mapping table; the preset counter mapping table is used to record the mapping relationship between the adjustment functions in the vehicle cabin and the corresponding first counter; The count values ​​of the target first counters corresponding to the plurality of adjustment functions are incrementally updated.

8. The method of claim 1, wherein, The method further includes: When receiving consecutive call requests for the same adjustment function, obtain the time interval between two adjacent call requests; Determine whether the time interval is less than a preset anti-shake time threshold; If so, the most recent call request will be determined as an invalid request, so that the first counter and the second counter will not perform the count value update operation; If not, the most recent call request is determined to be a valid request, so that the first counter and the second counter perform a count value update operation.

9. An electronic device, comprising: include: Memory, used to store computer programs; A processor, configured to implement the steps of the vehicle function invocation method as described in any one of claims 1 to 8 when executing the computer program.

10. A vehicle characterized by comprising: It includes a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to implement the vehicle function invocation method as described in any one of claims 1 to 8.

Images