Methods, devices, equipment and media for intelligent gesture monitoring in automotive diagnostic equipment

CN116820320BActive Publication Date: 2026-09-01THINKCAR SOFTWARE TECH DEV CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202310208397.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-20
Publication Date
2026-09-01
Estimated Expiration
2042-07-20

AI Technical Summary

Technical Problem

[0006]为解决上述现有汽车诊断设备手势响应U I单一、功能单一的不足,本发明提供一种汽车诊断设备手势智能监听方法,包括以下步骤:

Benefits of technology

[0030]基于上述,与现有技术相比,本发明提供的一种汽车诊断设备手势智能监听方法,使得汽车诊断设备的手势返回操作能够满足设备运行过程中智能化监听、智能化响应的需求,对硬件资源进行调控,使汽车诊断设备能够根据不同情况进行响应,有效节省设备资源。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116820320B_ABST
    Figure CN116820320B_ABST
Patent Text Reader

Abstract

This invention relates to the field of automotive diagnostic technology, and particularly to a method, apparatus, device, and medium for intelligent gesture monitoring of automotive diagnostic equipment. One method for intelligent gesture monitoring of automotive diagnostic equipment includes the following steps: creating a corresponding core management class in a view layout existing in the source code; creating a gesture view through the core management class; generating a custom animated icon within the gesture view; displaying the animated icon on the screen; registering a gesture monitoring area in the core management class to monitor finger touch actions in real time; different monitoring frequencies for users with different permissions / devices; determining the validity of the finger touch action and the touch area in the gesture view based on the touch position and touch distance of the monitored finger touch action; and returning the corresponding animated icon and finger touch action response when the action is deemed valid. This invention enables the gesture return operation of automotive diagnostic equipment to adapt to different situations and saves hardware resources.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application filed on July 20, 2022, with application number 2022108501455 and entitled "Gesture Intelligent Response Processing Method, Device, Equipment and Medium for Automotive Diagnostic Equipment". Technical Field

[0002] This invention relates to the field of automotive diagnostic technology, and in particular to a method, apparatus, device, and medium for intelligent gesture monitoring of automotive diagnostic equipment. Background Technology

[0003] In the field of automotive diagnostic technology, due to the rapid development of the intelligent era, the design of diagnostic equipment is more inclined to improve the user experience. If the interface of a diagnostic device is limited to operation through fixed navigation buttons on the interface when returning to the previous interface, it seems a bit monotonous; and the gestures are relatively simple and cannot meet diverse and personalized needs.

[0004] For example, patent document CN105549838A, published on May 4, 2016, discloses a method for triggering the destruction of the current Activity by gesture swiping. The method includes: opening an application to enter a first Activity interface; pressing one end of the screen and then slowly swiping to the other side; when the swipe reaches one-third of the screen width, the application executes the finish() method; destroying the current Activity interface and returning to a second Activity interface. The purpose of implementing this invention is to provide a gesture response where swiping from left to right returns to the previous level and destroys the current Activity, achieving the effect of clicking a back button, facilitating user operation, and improving the user experience.

[0005] The above solution can achieve the return operation through gestures, but its gesture response technology has a simple overall function and cannot meet the needs of intelligent monitoring and intelligent response during the operation of automotive diagnostic equipment. It also has insufficient control over hardware resources and wastes hardware resources, so it still needs further optimization. Summary of the Invention

[0006] To address the shortcomings of existing automotive diagnostic equipment, such as limited UI and single function in gesture response, this invention provides a method for intelligent gesture monitoring in automotive diagnostic equipment, comprising the following steps:

[0007] S100. Create the corresponding core management class in the view layout that exists in the source code;

[0008] S200. Create a gesture view through the core management class;

[0009] S300. Generate a custom animated icon within the gesture view;

[0010] S400. Display the animated icon on the screen;

[0011] S500: Register a gesture listening area in the core management class to listen to finger touch actions in real time; the listening frequency varies depending on the user's permissions or the device they are using.

[0012] S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action;

[0013] When S700 determines that the action is valid, the core management class returns the corresponding animated icon and finger touch response.

[0014] Preferably, the gesture view described in step S200 is carried across the entire screen.

[0015] Preferably, in step S500, the gesture listening area is registered through WindowsManagerService (WMS).

[0016] Preferably, in step S500, the listening device is woken up based on the diagnostic operation time of the vehicle diagnostic device.

[0017] Preferably, in step S600, different responses are achieved by judging the sliding distance of the finger.

[0018] Preferably, the gesture view generated in step S200 is associated and mapped with the user's permission ID, meaning that the same gesture view will produce different results depending on the user's permission.

[0019] Preferably, in step S700, the number of times a response is returned within a preset time is dynamically set and adjusted according to the frequency of finger touch actions detected in real time.

[0020] The present invention also provides a gesture-based intelligent monitoring device for automotive diagnostic equipment, including...

[0021] The core management module is used to create corresponding core management classes in the view layouts that exist in the source code;

[0022] A module is created to generate gesture views through the core management class;

[0023] A drawing module is used to generate custom animated icons within the gesture view;

[0024] The display module is used to display the animated icons on the screen;

[0025] The listening module is used to register gesture listening areas in the core management class to listen for finger touch actions in real time; the listening frequency is different for people with different permissions / people on different devices;

[0026] The judgment module is used to determine the validity of the finger touch action and the touch area based on the touch position and touch distance of the monitored finger touch action in the gesture view;

[0027] The response module is used to return the corresponding animated icon and finger touch action response through the core management class when the judgment module determines that it is valid.

[0028] The present invention also provides an automotive diagnostic device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the automotive diagnostic device gesture intelligent monitoring method as described above.

[0029] The present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the gesture-based intelligent monitoring method for automotive diagnostic equipment as described above.

[0030] Based on the above, compared with the prior art, the present invention provides a gesture-based intelligent monitoring method for automotive diagnostic equipment, which enables the gesture return operation of automotive diagnostic equipment to meet the needs of intelligent monitoring and intelligent response during equipment operation, regulates hardware resources, and enables automotive diagnostic equipment to respond according to different situations, effectively saving equipment resources.

[0031] Other features and beneficial effects of the invention will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other beneficial effects of the invention can be realized and obtained by means of the structures particularly pointed out in the description, claims and drawings. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Unless otherwise specified, the positional relationships shown in the drawings in the following description are based on the direction in which the components are drawn in the figure.

[0033] Figure 1 A flowchart of a gesture-based intelligent monitoring method for automotive diagnostic equipment provided by the present invention;

[0034] Figure 2This is an overall flowchart of the actual operation of Embodiment 1 of the present invention;

[0035] Figure 3 This invention provides a schematic diagram of the structure of a gesture-based intelligent listening device for automotive diagnostic equipment.

[0036] Figure 4 This is a schematic diagram of the structure of an automotive diagnostic device provided by the present invention.

[0037] Figure label:

[0038] 10 Core Management Modules 20 Creation Modules 30 Drawing Modules

[0039] 40 Display Module, 50 Listening Module, 60 Judgment Module

[0040] 70 Response Module Detailed Implementation

[0041] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. The technical features designed in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0042] In the description of this invention, it should be noted that all terms used in this invention (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains, and should not be construed as limiting the invention; it should be further understood that the terms used in this invention should be understood to have the same meaning as those in the context of this specification and in the relevant field, and should not be understood in an idealized or overly formal sense, except as expressly defined in this invention.

[0043] Example 1

[0044] To address the issue that gesture-responsive UIs are often limited and lack functionality, failing to meet diverse and personalized needs, this embodiment provides a method for intelligent gesture monitoring in automotive diagnostic equipment. Please refer to [link / reference]. Figure 1 and Figure 2 This method, applied to automotive diagnostic equipment, specifically includes the following steps:

[0045] S100. Create the corresponding core management class in the view layout that exists in the source code;

[0046] S200. Create a gesture view through the core management class;

[0047] S300. Generate a custom animated icon within the gesture view;

[0048] S400. Display the animated icon on the screen;

[0049] S500: Register a gesture listening area in the core management class to listen for finger touch actions in real time;

[0050] S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action;

[0051] When S700 determines that the action is valid, the core management class returns the corresponding animated icon and finger touch response.

[0052] The intelligent gesture monitoring method for automotive diagnostic equipment of this invention can be further developed based on Android 10. In actual development, an `EdgeBackGestureHandler` class can be created in SystemUI using the DI framework. The `EdgeBackGestureHandler` class is the core management class of the entire intelligent gesture monitoring method for automotive diagnostic equipment. During construction, the core management class needs to initialize preset parameters and variables required for gesture judgment. When creating the gesture view (`NavigationBarEdgePane`), the core management class injects the preset parameters and variables into the gesture view. Then, a custom animated icon is generated in the gesture view and displayed on the screen. Simultaneously, the core management class registers a monitoring area to monitor finger touch actions in real time. The specific monitoring area setting process is described in the `InputSelector` documentation. The gesture view determines the validity of the finger touch action and the touch area based on data such as the touch position and touch distance of the monitored finger touch action. If the action is deemed valid, the core management class returns the corresponding animated icon and finger touch action response.

[0053] refer to Figure 2S100 to S400 utilize the Factory Design Pattern to establish multiple sets of gesture UI switching functions and selectable user experiences. For example, User A wants a UI with a red dot containing a white arrow, and the function should return to the previous page when swiping from the left or right. Based on this requirement, API method 1 is created. User B wants an intuitive ripple animation effect, with swiping left returning to the previous page and swiping right pulling out the sidebar. API method 2 is created for this. After the overall methods are established, they respond according to actual operations. The advantages of custom animated icons are that, on the one hand, operations can be customized according to each user's behavior to improve efficiency; on the other hand, personalized services can be provided to enhance the user experience.

[0054] To complete the response, S500 needs to perform corresponding listening steps. S500 monitors the distance between the finger's pressed position and the screen edge. When the finger touches the screen edge within 30-40 pixels of the left or right edge, a response command is sent to the system-specified API method, displaying a custom icon effect on the screen. Then, depending on whether the finger slides left or right, a sliding distance within 0-30 pixels is considered a preset valid listening area. Next, step S600 checks if it's a valid listening area; if so, step S700 returns to the previous page. If S500 detects a distance between the finger's pressed position and the screen edge exceeding 30-40 pixels but less than the entire screen width, the area is invalid, and step S600 is not executed. Furthermore, since the application operates in normal immersive mode, if the user slides from the edge, the application will not recognize the gesture and cannot send a signal. Therefore, a sticky immersive mode is used globally, allowing the device to optimize the sliding effect without the system's top notification bar. Specifically, the creation of the gesture view and the registration of the listening area can be performed simultaneously at the code level.

[0055] Preferably, the gesture view described in step S200 can be carried across the entire screen.

[0056] Specifically, in step S500, the gesture listening area can be registered through WindowsManagerService (WMS).

[0057] In the gesture-based intelligent monitoring method, continuous monitoring would waste device resources. Therefore, in step S500, the monitoring frequency varies depending on the user's permissions / device. For example, senior administrators, due to their extensive operational privileges and complex operations, are monitored at a high frequency, while general users, whose gesture response interfaces are relatively small and whose gesture response types are more limited, are monitored at a low frequency.

[0058] Preferably, the monitoring module can be activated based on the duration of the diagnostic work performed by the vehicle diagnostic equipment. For example, monitoring can be stopped after the diagnostic work begins and activated again when the diagnostic process reaches its final stage. Alternatively, when the vehicle diagnostic equipment is not in operation for a set period (the specific time can be set by the user), monitoring can be stopped after no operation occurs within the set time, the vehicle diagnostic equipment will lower its screen brightness, and then restore the brightness and activate the monitoring module upon receiving an operation.

[0059] Example 2

[0060] To further address the issue of fixed response areas being unsuitable for certain practical applications, this invention also provides Embodiment 2 to adapt to different application scenarios, specifically including the following steps:

[0061] S100. Create the corresponding core management class in the view layout that exists in the source code;

[0062] S200. Create a gesture view through the core management class;

[0063] S300. Generate a custom animated icon within the gesture view;

[0064] S400. Display the animated icon on the screen;

[0065] S500: Register a gesture listening area in the core management class to listen to finger touch actions in real time. At the same time, dynamically adjust the range and position of the listening area according to the usage scenario and the user's permissions. The shape of the range and position is a custom non-geometric shape based on the device screen layout.

[0066] S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action;

[0067] When S700 determines that the action is valid, the core management class returns the corresponding animated icon and finger touch response.

[0068] If the gesture response area is fixed, it becomes unsuitable for some application scenarios. For example, automotive diagnostic equipment may be placed at a high or low position, and a fixed screen would make it inconvenient to use. Furthermore, physical damage to certain areas could render gesture response unusable. Therefore, in step S500, those skilled in the art can pre-set and dynamically adjust the range and position of the monitoring area according to the usage scenario and user permissions. The shape of the specific range and position can be a standard geometric shape or a custom shape based on the device screen layout. In practice, this can be achieved by pre-dividing the area and selecting it subsequently, or by customizing the area. Moreover, the specific range and position do not need to be displayed on the entire screen, saving hardware resources and avoiding the problem of unusable areas due to physical damage.

[0069] Furthermore, its non-geometric shape makes it unusable for users without professional training and guidance, thus avoiding malfunctions caused by misoperation or haphazard operation by non-professional users.

[0070] Example 3

[0071] To further address the issue of low efficiency and the need for multiple repetitions in gesture response during practical applications, this invention also provides Embodiment 3 to improve the efficiency of gesture operation response, including the following steps:

[0072] S100. Create the corresponding core management class in the view layout that exists in the source code;

[0073] S200. Create a gesture view through the core management class;

[0074] S300. Generate a custom animated icon within the gesture view;

[0075] S400. Display the animated icon on the screen;

[0076] S500: Register a gesture listening area in the core management class to listen for finger touch actions in real time;

[0077] S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action, and different responses are achieved by judging the sliding distance of the finger.

[0078] When S700 determines that the action is valid, the core management class returns the corresponding animated icon and finger touch response.

[0079] If the diagnostic device has a large software interface, using gestures to flip through pages one by one is inefficient. Therefore, the finger swipe distance in step S600 is judged to achieve different responses. Specifically, the finger swipe distance judgment in step S600 from 0 to 30 pixels can be divided into 3 segments, each segment corresponding to flipping 1 page, 2 pages, or 3 pages respectively. In this way, if the user wants to directly flip to the 2nd or 3rd page, it can be controlled according to the finger swipe distance, which improves efficiency and saves the device's hardware and software resources.

[0080] Example 4

[0081] In practical use of automotive diagnostic equipment, to address the problem of operator complexity leading to misoperation, this invention also provides Embodiment 4 to facilitate equipment operation and management, including the following steps:

[0082] S100. Create the corresponding core management class in the view layout that exists in the source code;

[0083] S200. Create a gesture view through the core management class, and associate and map the generated gesture view with the operation user permission ID. That is, the same user gesture will result in different response results due to different operation user permissions.

[0084] S300. Generate a custom animated icon within the gesture view;

[0085] S400. Display the animated icon on the screen;

[0086] S500: Register a gesture listening area in the core management class to listen for finger touch actions in real time;

[0087] S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action;

[0088] When S700 determines that the action is valid, the core management class returns the corresponding animated icon and finger touch response.

[0089] Current gesture responses lack management permission settings; once logged in, anyone with any permission can perform operations, which is detrimental to management. Therefore, the gesture view generated in step S200 is associated and mapped with the user's permission ID. This means that the same gesture view will respond differently depending on the user's permission (e.g., different users with different permissions may respond differently when performing left or right horizontal swipes). For example, a senior administrator has a larger gesture response area and can perform more gesture types; a regular user has a smaller gesture response area and more limited gesture types. This solves the management problems caused by ordinary users performing operations after a senior administrator logs in. In specific implementation, different permission accounts are set up at the device system level, each with a corresponding user permission ID, and a gesture library is configured with the user permission ID corresponding to the permission. Based on the device model and configuration, the corresponding permission account is activated through methods such as fingerprint recognition, gesture input, or activation password, and the corresponding user permission ID is configured. When creating the gesture view in the core management class, the content for judging the user permission ID is injected. After the gesture view is created, it is associated and mapped with the user permission ID, and then the gesture view can traverse the gesture library and make corresponding judgments.

[0090] Example 5

[0091] To address the issue of operators making mistakes due to excessively rapid operations during the actual use of gesture-based intelligent monitoring methods in automotive diagnostic equipment, this invention provides Embodiment 5, which optimizes the method and includes the following steps:

[0092] S100. Create the corresponding core management class in the view layout that exists in the source code;

[0093] S200. Create a gesture view through the core management class;

[0094] S300. Generate a custom animated icon within the gesture view;

[0095] S400. Display the animated icon on the screen;

[0096] S500: Register a gesture listening area in the core management class to listen for finger touch actions in real time;

[0097] S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action;

[0098] When S700 determines that the action is valid, it returns the corresponding animated icon and finger touch action response through the core management class, and dynamically adjusts the number of times the response is returned within a preset time according to the frequency of finger touch actions detected in real time.

[0099] Current gesture-based intelligent monitoring methods suffer from the problem of accidental operations due to users' rapid actions within a given time frame during return operations. Therefore, the S700 allows setting a preset number of return responses within a given time period. Specifically, it can be set to respond to only one gesture per unit of time, such as responding to only one gesture within 0.5 seconds. This avoids both accidental operations and the waste of device hardware resources caused by frequent operations.

[0100] Furthermore, the system can dynamically adjust the number of responses within a preset time period by detecting the frequency of finger touches in real time. For example, if a high frequency of finger touches is detected within a certain period, it indicates frequent operation and the need for a quick response, so the number of responses within the preset time period can be increased. Conversely, if a low frequency of finger touches is detected within a certain period, it indicates infrequent operation and the lack of a quick response, so the number of responses within the preset time period can be decreased. This satisfies operational needs while conserving the device's hardware and software resources.

[0101] Example 6

[0102] In actual use, automotive diagnostic equipment undergoes unpredictable operations, and prolonged monitoring can waste equipment resources. To address this issue, this invention provides Embodiment 6 for optimization, including the following steps:

[0103] S100. Create the corresponding core management class in the view layout that exists in the source code;

[0104] S200. Create a gesture view through the core management class;

[0105] S300. Generate a custom animated icon within the gesture view;

[0106] S400. Display the animated icon on the screen;

[0107] S500: Register a gesture listening area in the core management class to listen to finger touch actions in real time. At the same time, the listening frequency is different for people with different permissions / people with different devices.

[0108] S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action;

[0109] When S700 determines that the action is valid, the core management class returns the corresponding animated icon and finger touch response.

[0110] Example 7

[0111] This embodiment also provides a gesture-based intelligent monitoring device for automotive diagnostic equipment, such as... Figure 3 As shown, it includes a core management module, which is used to create corresponding core management classes in the view layouts that exist in the source code;

[0112] A module is created to generate gesture views through the core management class;

[0113] A drawing module is used to generate custom animated icons within the gesture view;

[0114] The display module is used to display the animated icons on the screen;

[0115] The listening module is used to register gesture listening areas in the core management class to listen for finger touch actions in real time.

[0116] The judgment module is used to determine the validity of the finger touch action and the touch area based on the touch position and touch distance of the monitored finger touch action in the gesture view;

[0117] The response module is used to return the corresponding animated icon and finger touch action response through the core management class when the judgment module determines that it is valid.

[0118] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. For example, a processing module can be a separate processing element, or it can be integrated into a chip within the above device. Alternatively, it can be stored as program code in the device's memory, and its functions can be called and executed by a processing element. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element mentioned here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0119] Example 8

[0120] This embodiment provides an automotive diagnostic device, such as... Figure 4 As shown, it includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps of the gesture intelligent monitoring method for automotive diagnostic equipment as described above.

[0121] This invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the gesture-based intelligent monitoring method for automotive diagnostic equipment as described above.

[0122] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the specific working processes of the devices, apparatuses, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. Those skilled in the art will recognize that the modules and 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 composition and steps of each example have been generally described in terms of function 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.

[0123] In the embodiments provided in this application, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Units with the same function may be grouped into one unit. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0124] Furthermore, those skilled in the art should understand that although many problems exist in the prior art, each embodiment or technical solution of the present invention can be improved in only one or a few aspects, without necessarily solving all the technical problems listed in the prior art or the background art simultaneously. Those skilled in the art should understand that any content not mentioned in a claim should not be construed as a limitation on that claim.

[0125] Although this document frequently uses terms such as source code, core management class, and listener, the possibility of using other terms is not excluded. These terms are used merely for the convenience of describing and explaining the essence of the invention; interpreting them as any additional limitation would contradict the spirit of the invention. It should also be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or electronic device 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 electronic device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or electronic device that includes said element.

[0126] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions 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 gesture-based intelligent monitoring method for automotive diagnostic equipment, characterized in that, Includes the following steps: S100. Create the corresponding core management class in the view layout that exists in the source code; S200. Create a gesture view through the core management class; S300. Generate a custom animated icon within the gesture view; S400. Display the animated icon on the screen; S500: Register the gesture listening area in the core management class to listen to finger touch actions in real time; the listening frequency is different for people with different permissions / different devices; in step S500, the listening is activated according to the diagnostic work time of the car diagnostic equipment; S600: In the gesture view, the validity of the finger touch action and the touch area is determined based on the touch position and touch distance of the monitored finger touch action; When S700 determines that the action is valid, the core management class returns the corresponding animated icon and finger touch response.

2. The gesture-based intelligent monitoring method for automotive diagnostic equipment according to claim 1, characterized in that: The gesture view described in step S200 is displayed on the entire screen.

3. The gesture-based intelligent monitoring method for automotive diagnostic equipment according to claim 1, characterized in that: In step S500, the gesture listening area is registered through WindowManagerService.

4. The gesture-based intelligent monitoring method for automotive diagnostic equipment according to claim 1, characterized in that: In step S600, different responses are achieved by judging the sliding distance of the finger.

5. The gesture-based intelligent monitoring method for automotive diagnostic equipment according to claim 1, characterized in that: In step S200, the generated gesture view is associated and mapped with the operation user's permission ID. That is, the same gesture view will result in different responses depending on the operation user's permission.

6. The gesture-based intelligent monitoring method for automotive diagnostic equipment according to any one of claims 1-5, characterized in that: In step S700, the number of times a response is returned within a preset time is dynamically adjusted based on the frequency of finger touch actions detected in real time.

7. A gesture-based intelligent monitoring device for automotive diagnostic equipment, characterized in that: include The core management module is used to create corresponding core management classes in the view layouts that exist in the source code; A module is created to generate gesture views through the core management class; A drawing module is used to generate custom animated icons within the gesture view; The display module is used to display the animated icons on the screen; The listening module is used to register gesture listening areas in the core management class to listen for finger touch actions in real time. People with different permissions / devices listen at different frequencies; the listening cycle is activated based on the diagnostic time of the car diagnostic equipment. The judgment module is used to determine the validity of the finger touch action and the touch area based on the touch position and touch distance of the monitored finger touch action in the gesture view; The response module is used to return the corresponding animated icon and finger touch action response through the core management class when the judgment module determines that it is valid.

8. An automotive diagnostic device, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the gesture-based intelligent monitoring method for automotive diagnostic equipment as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the gesture-based intelligent monitoring method for automotive diagnostic equipment as described in any one of claims 1 to 6.

Citation Information

Patent Citations

  • Method for utilizing gesture sliding to trigger removal of current Activity

    CN105549838A

  • Gesture control method and device based on Android system

    CN105425966A

  • Cover controller hub architecture for improved touch experience

    CN114077320A