Display device reverse control method and device, electronic device, and computer storage medium

Abstract

The application provides a display device reverse control method and device, electronic equipment and computer storage medium. The method comprises the following steps: receiving an input signal of an input device; matching the input device with a target driving module; converting a contact event in the input signal into a control event corresponding to the contact event; and outputting the control event to an external controlled device for the input device to control the external controlled device. Through the above method, the compatibility and adaptation capability of the display device to the peripheral input device can be enhanced, and the reverse control of the external controlled device can be realized.

Description

Technical Field

[0001] This application relates to the field of display device control, specifically to a display device reverse control method, apparatus, electronic device, and computer storage medium. Background Technology

[0002] With the increasing application of intelligent display terminals, monitors, and multi-source input devices, such as external mice and other human-computer interaction (HID) devices, these devices not only need to perform conventional cursor control, scrolling, and key input on the local system side, but are also increasingly used for reverse control of external connected devices. In related technologies, mouse devices typically connect to the system according to standard HID device protocols, and the system then identifies, parses, and reports input events through corresponding drivers.

[0003] However, in existing technologies, some systems still lack sufficient support for the aforementioned identification and adaptation, resulting in related functions failing to respond properly on the terminal side. Furthermore, in reverse control application scenarios, existing technologies lack solutions for using the converted data to control external input source devices, making it difficult to meet the needs of actual control scenarios.

[0004] Therefore, how to achieve the recognition, conversion, and reverse control of the input sensing area of ​​a specific device without being limited to specific application scenarios remains a technical problem to be solved in the existing technology. Summary of the Invention

[0005] This application provides a method, apparatus, electronic device, and computer storage medium for controlling a display device to solve the problems existing in the prior art.

[0006] On one hand, this application provides a method for reverse control of a display device. The method includes: receiving an input signal from an input device; matching the input device with a target driving module; converting a contact event in the input signal into a control event corresponding to the contact event; and outputting the control event to an external controlled device for control of the external controlled device by the input device.

[0007] Furthermore, this application also proposes that matching the input device with the target driver module includes: matching the input device to the target driver module based on the product identifier (PID) and / or manufacturer identifier (VID) of the input device.

[0008] Furthermore, this application also proposes that the target driving module includes: an adapted driving module adapted based on the PID and / or VID.

[0009] Furthermore, this application also proposes that converting the touch events in the input signal into control events corresponding to the touch events includes: the control events including scroll wheel events and / or button events; converting drag-type touch events in the touch events into scroll wheel events; and converting click-type touch events in the touch events into button events.

[0010] Furthermore, this application also proposes that the key event includes the middle key event.

[0011] Furthermore, this application also proposes that the drag-type contact event includes a sliding event along the input sensing area, and that the scrolling direction of the roller event is determined based on the sliding direction of the sliding event; the scrolling amount of the roller event is determined based on the sliding displacement of the sliding event.

[0012] Furthermore, this application also proposes that the input device includes a human-machine interface device (HID); the external controlled device is an external input source device connected to the display device, and the control event is output to the external controlled device in the form of a HID report; the external controlled device performs scrolling control and / or key control based on the control event.

[0013] On the other hand, this application provides a display device reverse control device. The device includes: The access module is used to receive input signals from input devices; The identification and driver matching module is used to match the input device with the target driver module; The event conversion module is used to convert the contact events in the input signal into control events corresponding to the contact events; The event output module is used to output the control events to external controlled devices; The reverse control execution module is used to enable the input device to control the external controlled device.

[0014] On the other hand, this application provides an electronic device including a processor and a memory, wherein the memory stores program instructions that, when executed by the processor, implement the steps in the above-described display device reverse control method.

[0015] On the other hand, this application provides a computer storage medium storing program instructions that, when executed by a processor, implement the steps in the above-described display device reverse control method.

[0016] The display device reverse control method, apparatus, electronic device and computer storage medium provided in this application can improve the input compatibility of a specific device in the display terminal and enable its input data to be output to external devices as a source of reverse control events, thereby realizing the reverse control function. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a schematic diagram of the steps of a display device reverse control method provided in an embodiment of this application; Figure 2 This is an interaction relationship between the input device, the display device, and the external controlled device in a display device reverse control method provided in an embodiment of this application; Figure 3 This is a schematic diagram of a display device reverse control device provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0019] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0020] The input device applicable to this application can be a mouse, particularly a type of mouse that uses a non-traditional mechanical scroll wheel structure for scrolling input. Such mice typically have cursor movement input functionality and can achieve scrolling input, button input, and / or gesture input through a touch area, touchpad, surface sensing structure, or other input sensing area. Unlike traditional mice with mechanical scroll wheels, the scrolling control of this type of mouse does not rely on an independent scroll wheel component, but rather generates corresponding input data by detecting information generated by the user in the input sensing area.

[0021] The input sensing area is typically located on the surface of the mouse device and is used to sense user touch operation information on that area, such as contact position, movement direction, movement changes, and / or contact state changes, and generate corresponding input data accordingly. Specifically, the input sensing area can sense user operations through capacitive detection, pressure detection, optical detection, or other contact detection methods, and generate corresponding detection data. The control circuit preprocesses the detection results and identifies the corresponding contact operation type. Based on the identified contact operation type and / or the corresponding displacement parameters, it generates human-computer interaction input data for controlling mouse device functions or for reporting to the host computer. This input data can be further converted by the device side into reporting data related to scroll control, button control, or other human-computer interaction controls, thereby replacing some of the input functions implemented by traditional mechanical scroll wheels or independent buttons.

[0022] In some implementation scenarios, the aforementioned mouse device can be a composite human-machine interface device, capable of simultaneously reporting displacement data, button data, and input data corresponding to scrolling operations. This type of device can be wired or wireless; for wireless devices, an input connection can be established with the display terminal via a Bluetooth dongle, a Universal Serial Bus (USB) receiver, or other wireless receiving modules.

[0023] As an example, the aforementioned mouse devices include Apple's Magic Mouse and similar devices. These devices typically use a touch surface instead of a traditional mechanical scroll wheel as the input sensing area, generating data related to scrolling, button presses, or other control inputs by detecting contact movements within the input sensing area. However, it should be noted that this application is not limited to mouse devices of a specific brand, model, or product identifier. Any device that has a need to convert non-traditional scroll wheel inputs, particularly inputs from the input sensing area, into standard mouse input events for further control purposes is eligible for the technical solutions described in this application.

[0024] In a typical application scenario of existing technology, such as when applied to display terminals running the Android U operating system or kernel version 5.15, the display terminal still has insufficient compatibility support for the aforementioned specific mouse devices. Taking the Magic Mouse as an example, after being connected to the display terminal via a Universal Serial Bus Bluetooth receiver, the terminal often cannot correctly support the scroll wheel and button effects generated by its operation in its native state, resulting in the related inputs not responding properly on the display side, affecting the user's operating experience. At the same time, in reverse control application scenarios, even if the display terminal can respond locally to some input effects, existing solutions usually lack a mechanism to further output the converted input events to external input source devices, making it difficult to effectively control external input source devices connected to the display terminal using this mouse device.

[0025] This application uses a display device as an example for illustration, but the invention is not limited to display devices. In other embodiments, the invention can also be applied to products such as televisions, commercial displays, conference tablets, and terminal display devices with external signal input interfaces. After such devices are connected to an external input source device, they can receive and forward converted mouse control events via USB, Type-C interface, or other control channels, thereby forming a reverse control usage mode similar to that of display devices. For example, a user can use a Magic Mouse as an input device to control external hosts, terminals, or other signal source devices connected to the aforementioned display devices. Therefore, the invention has good device applicability and scenario scalability.

[0026] Therefore, this application aims to provide a method, apparatus, electronic device, and computer storage medium for controlling a display device, in order to solve the problem in the prior art that the display terminal does not support scroll input and key input of specific input devices, and that the converted input events cannot be used to control external input source devices.

[0027] In one type of embodiment, such as Figure 1 As shown, a method for controlling a display device is provided. This method includes at least steps S101 to S104, which are described in detail below: S101: Receives input signals from input devices; That is, the display device receives raw input data from the aforementioned mouse-type input device. The types of input devices have been described above, so they will not be repeated here.

[0028] The input signals may include contact-type input information generated by the input sensing area, such as displacement information and button information. For the device involved in this application, these input signals do not necessarily directly correspond to the scroll wheel or button signals of a standard mouse, but rather are raw input data reported by the device according to its own protocol or reporting format. This step aims to obtain the raw input source from the input device, providing a foundation for subsequent identification, conversion, and reverse control output.

[0029] For example, the input device is a Magic Mouse. The mouse establishes an input connection with the display device via a Universal Serial Bus Bluetooth receiver. The Bluetooth receiver receives mouse signals sent by the mouse and inputs the mouse signals to the display. The display device then receives the input signals through its Human-Machine Interface Device Access Port. A Human-Machine Interface Device Emulation Module (HID Gadget, HIDG) is associated with the interface port. The HIDG emulation module encapsulates the converted events into a Human-Machine Interface Device Report and outputs it to an external controlled device via the interface port.

[0030] S102: Match the input device with the target driver module; That is, after receiving an input signal from an input device or recognizing that an input device has been connected, the display device performs device identification on the input device and calls or matches the corresponding driver processing module according to the identification result.

[0031] The target driver module refers to a driver processing module adapted to the data reporting method of the input device, used to identify, parse, and process the input signals of the input device. Because different input devices differ in device structure, report format, and input data organization, after recognizing an input device connection, the display device needs to determine from multiple driver modules the corresponding driver module capable of processing the input device, and then the corresponding driver module will perform subsequent processing on the input data.

[0032] The target driving module functions as follows: firstly, it identifies and receives the raw input data reported by the input device; secondly, it processes the raw input data according to the report format and parsing rules corresponding to the input device, so that the touch events can be subsequently converted into scroll wheel events and / or key events. In other words, the target driving module is a functional module of the display device that performs dedicated input parsing and event conversion for the target input device.

[0033] S103: Convert the contact event in the input signal into a control event corresponding to the contact event; The target driving module parses the input signals reported by the input device to identify the contact events contained therein. These contact events can be event information corresponding to contact, movement, pressing, release, and state changes detected by the input sensing area of ​​the input device. The target driving module performs event conversion processing on the contact events based on their event type, direction of change, amount of change, and / or state change characteristics to generate control events that the system can recognize.

[0034] In this embodiment, the target driving module can first extract raw input data related to the contact operation from the input signal, and determine the type of user operation on the input sensing area based on the raw input data. For example, when the raw input data indicates that the user is performing a sliding action on the input sensing area, the target driving module identifies the contact event corresponding to the action and generates a corresponding control event; When the raw input data indicates that the user performs a click action on the input sensing area, the target driving module identifies the contact event corresponding to the click action and generates a corresponding control event.

[0035] The control event refers to an input event formed by parsing and converting contact events from the input device, which can be recognized and processed by the display device and / or the controlled device. Preferably, the control event corresponds to a standard mouse input event in terms of event semantics and control effect, enabling the display device and / or the controlled device to obtain control effects equivalent to conventional mouse input based on the control event. The control event may include one or more of the following: scroll wheel events, button events, and displacement events.

[0036] S104: Output the control event to an external controlled device for the input device to control the external controlled device.

[0037] On one hand, the target driving module organizes and reports control events according to a preset input event format, so that the display device can respond to the input locally, and provides standardized event data for subsequent output to external controlled devices. Through the above conversion process, contact input signals that do not directly correspond to standard mouse wheel input and button input are converted into control events that can be recognized and used by the display device.

[0038] On the other hand, the control event can be output to an external controlled device to enable the input device to control the external controlled device. Specifically, the display device can organize the control event according to a preset output format and send it to the external controlled device via the display device's output interface. In this embodiment, the control event can be encapsulated as a Human-Machine Interface (HID) report, and the output interface can be the display device's USB and / or Type-C channel, enabling the external controlled device to recognize the control event as an input event from a mouse device.

[0039] In some implementations, such as Figure 2 As shown, the display device can complete the converted event output processing at the driver layer, that is, the target driver module directly sends the control event to the corresponding output channel after completing the event conversion. In other embodiments, the system service module, input forwarding module, or other control module in the display device can also acquire, organize, and forward the control event and output it to the external controlled device. In other words, the output location of the control event can be set at the driver layer, system service layer, or application layer, as long as it can achieve the transmission of the control event to the external controlled device.

[0040] In this embodiment, the external controlled device can be an external device that serves as an input source for the display device, such as a signal input device connected to the monitor via an HDMI, DisplayPort (DP), Type-C, or other display / data interface. After receiving the original input signal generated by the input device and completing event conversion, the display device sends the converted event to the external controlled device via a USB and / or Type-C channel, thus making the input effect of the external controlled device equivalent to being directly connected to the input device. Therefore, the user can perform scrolling control, button control, and other corresponding control operations on the external controlled device through the input device connected to the display device, achieving reverse control functionality.

[0041] The term "reverse control" means that, unlike the connection relationship under the usual control path, the input device is not directly connected to the controlled device and transmits signals to the controlled device. Instead, the input device is first connected to the display device, which receives the input signal generated by the input device, identifies, matches, and converts it into an event, and then outputs the converted control event to the controlled device. This allows the controlled device to perform the corresponding control operation based on the control event, thus achieving the same control effect as if the controlled device were directly connected to the input device.

[0042] Furthermore, before being output to external controlled devices, the control events can undergo event format adaptation, event packaging, data caching, output timing control, and / or channel selection processing to meet the requirements of different external controlled devices for input event formats and transmission methods. For example, the control events can be encapsulated into input reports of the corresponding format based on the currently enabled reverse control output channel before being output; alternatively, the event codes, event sequences, or reporting rhythms of the control events can be adjusted according to the identification requirements of the external controlled devices. Through these methods, the adaptability of the control events to different external controlled devices and the stability of control can be improved.

[0043] Compared with the prior art, this application identifies the input device and matches the corresponding target driving module, and converts the contact events in the input signal, so that the contact input can form corresponding control events and further output them to the external controlled device. This not only improves the compatibility and support of the display device for this type of input device, but also allows the converted control events to be used as the source of reverse control events, thereby realizing the control of the external controlled device using the input device.

[0044] In one possible implementation, matching the input device with the target driver module includes: matching the input device to the target driver module based on the product identifier (PID) and / or manufacturer identifier (VID) of the input device.

[0045] Specifically, after the display device receives the input signal from the input device, it can further acquire the device identification information of the input device. The device identification information may include at least a Product Identifier (PID) and / or a Vendor Identifier (VID), and may also include one or more of device type information, product name information, and report description information. The display device parses the Product Identifier and Vendor Identifier, and compares the parsing result with preset driver matching information. When the comparison result indicates that the input device meets the identification conditions of the target device, the input device is matched to the corresponding target driver module. The target driver module then performs subsequent parsing and processing of the input signal reported by the input device.

[0046] In this embodiment, the input device can be a Magic Mouse-like human-machine interface device, and the target driver module can be an HID driver module for processing input data from such devices, such as the driver processing module corresponding to "hid-magicmouse". In some implementations, the driver code implementation file of the driver processing module can be "hid-magicmouse.c". The display device can read the product identification code and manufacturer identification code of the input device and perform matching according to the matching items preset in the target driver module; when at least one of the product identification code and manufacturer identification code meets the preset matching conditions, or when the combination of the two meets the preset matching conditions, it is determined that the input device and the target driver module are successfully matched.

[0047] Furthermore, the matching based on product identification codes and / or manufacturer identification codes can include, but is not limited to, one or more of the following methods: determining the manufacturer of the input device based on the manufacturer identification code, determining the product category or model of the input device based on the product identification code, and determining the corresponding target driver module based on the combination of the two; or, if the manufacturer identification code already meets the target manufacturer condition, further determining whether to call the target driver module based on the product identification code; or, if the product identification code can uniquely identify the target device, directly completing the driver matching based on the product identification code. Thus, the matching association between the input device and the target driver module can be flexibly realized according to different product configurations and recognition accuracy requirements.

[0048] In some embodiments, the system may pre-store device identification information for one or more specific input devices, including but not limited to product identification codes and manufacturer identification codes. When the display device or its control system identifies an accessed input device, it can determine whether the input device belongs to a specific device requiring event conversion processing based on the device identification information.

[0049] In some optional embodiments, users can input, select, confirm, or edit the product identification code and manufacturer identification code of the device to be adapted through a user interface. This information can be persistently stored in a local configuration file, database, parameter partition, or other non-volatile storage medium. During system startup, driver initialization, device hot-plug detection, or input service loading, the aforementioned saved device identification information can be read to complete the automatic identification and adaptation of the target device.

[0050] Therefore, the present invention is not limited to a single model or a single pre-installed device, but can be extended to multiple input devices with different product identification codes or manufacturer identification codes and other identification information.

[0051] In one possible implementation, the target driving module includes: an adapted driving module adapted based on the PID and / or VID.

[0052] Because the system's native support for specific input devices is insufficient, the target driver module can be an adapted driver module formed by adapting the existing system. For example, in the HID driver code used to process Magic Mouse-like devices, a matching item for the product identifier code and / or manufacturer identifier code corresponding to the target input device can be added, enabling the driver module to include the input device in its processing scope when it recognizes the corresponding device identifier information. The adapted driver module can be a driver processing module formed by adding a device identifier matching table, supplementing target device identification conditions, modifying driver identification logic, and / or supplementing event parsing rules corresponding to the target input device, based on the existing driver module.

[0053] Furthermore, the adaptation driver module is not only used to match the input device with the driver processing logic, but also to specifically parse the input signals according to the data organization method unique to the input device. In other words, after completing the driver adaptation based on the product identification code and / or manufacturer identification code, the display device no longer processes the input device according to the default input processing method of a scroll wheel mouse. Instead, the adaptation driver module identifies, extracts, and converts the input signals reported by the input device, thereby providing a processing basis for subsequently converting touch events into corresponding control events.

[0054] In some embodiments, the adaptation driver module adapted based on the product identification code and / or manufacturer identification code can be a driver processing module corresponding to "hid-magicmouse"; in some embodiments, the driver code implementation file of the driver processing module can be "hid-magicmouse.c". Specifically, by adding adaptation items such as the product identification code and / or manufacturer identification code of a specific device to the driver module, the display device can automatically bind the input device to the adaptation driver module when it detects an input device that matches the adaptation item, so that the adaptation driver module can perform subsequent input event parsing and conversion processing. In other embodiments, the above-mentioned adaptation and event conversion functions can also be implemented by other modules such as HID driver modules, input subsystem adaptation modules, or processing modules located in the driver layer and input event reporting path, and this application does not limit this. As long as a specific input device can be identified and the original input event can be converted and processed to output a predetermined control event, the technical solution of this application can be applied.

[0055] The above method enables the display device to accurately select the appropriate driver processing module based on the product identification information and / or manufacturer identification information of the input device, thereby improving the recognition and compatibility processing capabilities of input devices such as Magic Mouse, and providing a driver foundation for subsequent input event conversion and reverse control output.

[0056] In one possible implementation, converting the touch events in the input signal into control events corresponding to the touch events includes: the control events including scroll wheel events and / or button events; converting drag-type touch events in the touch events into scroll wheel events; and converting click-type touch events in the touch events into button events.

[0057] Specifically, after matching is completed, the target driving module parses the input signal and extracts the contact events generated by the input sensing area of ​​the input device from the input signal. The contact events may include contact establishment, contact movement, contact holding, contact release, press state changes, and their corresponding event data. The target driving module classifies and identifies the contact events based on their event type, state change characteristics, displacement change characteristics, and / or timing characteristics, and performs corresponding event conversion processing.

[0058] On one hand, in some implementations, when the target driving module identifies the contact event as a drag-type contact event, it converts the drag-type contact event into a scroll wheel event. The drag-type contact event can be a sliding event detected by the input sensing area, i.e., a continuous contact movement event along the input sensing area. The target driving module can determine the scrolling direction and scrolling amount of the scroll wheel event based on the changes in contact position, movement direction, and / or displacement within a continuous sampling period, and generate corresponding scroll wheel event data. The event parameters of the scroll wheel event can be determined based on the displacement change, change rate, number of samplings, and / or a preset mapping relationship. Through the above processing, continuous movement-type contact events generated by the input sensing area of ​​the input device can be converted into standard mouse scroll wheel input events.

[0059] On the other hand, in some implementations, when the target driving module recognizes the contact event as a click-type contact event, it converts the click-type contact event into a button event. The click-type contact event can be a combination of contact establishment and contact release events detected by the input sensing area, a press state change event, and / or a state change event that meets preset click judgment conditions. The target driving module can generate corresponding button event data based on the establishment sequence, duration, state change sequence, and / or preset click judgment rules of the click-type contact event.

[0060] In one possible implementation, the key event includes the middle key event.

[0061] Specifically, when the target driving module detects a click-type contact event that meets preset key judgment conditions, it generates a middle button key event. The preset key judgment conditions may include at least one of the following: detecting a contact establishment event and a contact release event; the duration between the contact establishment event and the contact release event meeting a preset duration condition; and / or the contact state change within a preset detection period meeting the key event state switching rules. After determining it as a key event, the target driving module can output event data corresponding to the middle button pressed state and the middle button released state to form the middle button key event.

[0062] In some implementations, the target driving module can identify the click-type contact events based on their duration, state change process, and / or timing characteristics, and uniformly map them as middle-click events. In other words, for click-type contact events that meet preset button judgment conditions, the target driving module no longer distinguishes whether they belong to the middle-click type or the middle-click press type, but uniformly generates the middle-click event to meet the middle-click input requirements in both reverse control and input control scenarios.

[0063] Furthermore, in this embodiment, when the target driving module identifies click-type contact events, it does not distinguish between the number of contact points or the type of contact intensity. In other words, under the condition of meeting the preset button judgment criteria, it does not distinguish between single-finger contact and two-finger contact, nor between the source form of tapping or pressing; the corresponding click-type contact event can be converted into the middle button event. This method simplifies the event recognition and mapping logic, improving the display device's compatibility with target input devices and input events. In other embodiments, the dragging and clicking actions can also be mapped to other preset button events, shortcut control events, or custom function events. When the access device has multiple buttons, touch areas, or gesture input capabilities, different input actions can correspond to different output events according to preset mapping rules.

[0064] In some embodiments, the mapping rules can be set, modified, and saved through configuration files, parameter tables, databases, or user interfaces, and will be loaded and take effect after system startup, driver initialization, or configuration update. Therefore, the event transformation relationship in this invention is not fixed, but can be flexibly configured according to the target device type, usage scenario, or user needs.

[0065] In one possible implementation, the drag-type contact event includes a sliding event along the input sensing area, and the scrolling direction of the roller event is determined based on the sliding direction of the sliding event; the scrolling amount of the roller event is determined based on the sliding displacement of the sliding event.

[0066] Specifically, the target driving module can determine the sliding direction of the sliding event based on the contact position change information within a continuous sampling period. The sliding direction can be determined by the contact coordinate difference between adjacent sampling times, the displacement component along a preset reference axis, and / or the position change trend within multiple consecutive sampling periods. Correspondingly, the target driving module generates the rolling direction of the roller event based on the sliding direction. In other words, when the sliding event changes along a first direction, a roller event corresponding to the first rolling direction is generated; when the sliding event changes along a second direction opposite to the first direction, a roller event corresponding to the second rolling direction is generated. Here, the first direction and the second direction are opposite directions along the same preset reference axis. Thus, the sliding direction on the input sensing area can be mapped to the rolling direction of the roller event.

[0067] Furthermore, the target driving module can also determine the scrolling amount of the roller event based on the sliding displacement of the sliding event. Specifically, the sliding displacement can be determined based on the displacement difference between adjacent sampling times, the cumulative displacement within a preset time window, the cumulative displacement between consecutive sampling points, and / or the effective displacement after filtering. The target driving module can map the sliding displacement to a preset mapping rule to obtain the scrolling amount parameter of the roller event. For example, when the sliding displacement increases, the scrolling amount of the roller event increases accordingly; when the sliding displacement decreases, the scrolling amount of the roller event decreases accordingly. In some embodiments, the target driving module can also perform threshold judgment, quantization, hierarchical mapping, and / or sensitivity adjustment on the sliding displacement to generate scrolling amount data that meets the system input requirements.

[0068] In some implementations, to improve the stability of event transitions, the target driving module may first perform debouncing, outlier filtering, and / or continuity determination on the position change data corresponding to the sliding event, and then determine the scrolling direction and scrolling amount accordingly. In other words, the sliding event is converted into a scrolling event only when the contact position change meets preset continuity conditions, displacement threshold conditions, and / or directional stability conditions, in order to avoid false triggering caused by occasional contact changes or noisy data.

[0069] In one possible implementation, the input device includes a human-machine interface device (HID); the external controlled device is an external input source device connected to the display device, and the control event is output to the external controlled device in the form of a HID report; the external controlled device performs scroll control and / or key control based on the control event.

[0070] Specifically, after generating the scroll wheel event and / or button event, the display device can further encapsulate the scroll wheel event and / or button event according to a preset report format to form a HID report, and output it to the external controlled device through the display device's output channel. The output channel can be a USB and / or Type-C channel. The HID report includes, but is not limited to, one or more of the following: event type identifier, button status identifier, scroll direction parameter, scroll amount parameter, and event timing information, so that the external controlled device can identify and process the converted event according to the human-machine interface device input method.

[0071] In this embodiment, the external controlled device can be an external input source device connected to the display device. The external input source device can be a data processing device or signal source device that establishes a display connection with the display device via HDMI, DP, Type-C, or other connection channels. While transmitting display signals to the external input source device, the display device can also send the converted events in HID report format to the external input source device via the USB output interface and / or Type-C channel, thereby enabling the external input source device to obtain input control capabilities corresponding to direct access to the input device. In other embodiments, the controlled device can also be a target functional module or input response object within the display device. The display device can provide the converted events to the corresponding processing module on its own side, so that the target functional module can perform corresponding control operations based on the converted events. In other words, the controlled device can be a device external to the display device or a controlled object internal to the display device; this application does not limit this.

[0072] Furthermore, when the HID report contains a scroll wheel event, the external controlled device can perform scrolling control based on the scroll wheel event. Specifically, the external controlled device can parse the scroll direction and scroll amount parameters in the scroll wheel event and perform interface scrolling, list scrolling, page scrolling, window content scrolling, and / or other control operations corresponding to scroll input accordingly. When the HID report contains a key event, the external controlled device can perform key control based on the key event. The key control can include at least one control operation corresponding to the key event, including but not limited to left key event, right key event, middle key event, and control operations corresponding to preset key functions.

[0073] In some implementations, to improve the stability of the external controlled device's recognition of the HID report, the display device may also perform event sorting, status completion, report caching, transmission timing adjustment and / or interface adaptation processing on the converted events before outputting the HID report.

[0074] In the above manner, the display device can output the original contact-type input signal generated by the input device to the external input source device connected to the display device in the form of an HID report after device recognition, drive matching and event conversion. This enables the external input source device to perform scrolling control based on the scroll wheel event and / or button control based on the button event, thereby realizing reverse control of the external input source device using the input device.

[0075] To facilitate better implementation of the device driving method of this application, this application also provides an apparatus based on the above-described display device reverse control method. The meanings of the terms used are the same as in the above-described display device reverse control method, and specific implementation details can be found in the description of the method embodiments.

[0076] like Figure 2 As shown, Figure 2 This paper illustrates an interactive relationship between an input device, a display device, and an external controlled device in a display device reverse control method, which is used to enable the input device to reverse control the external controlled device.

[0077] In the illustrated interaction, the input device can be a mouse-type input device such as a Magic Mouse. The input device responds to user actions, generating touch events such as dragging and clicking, and inputs these events to the display device. The display device identifies and processes these touch events, converting drag-type touch events into scroll wheel events and click-type touch events into button events, thus forming the converted scroll wheel and button events. Simultaneously, an external controlled device establishes a signal connection with the display device, inputting a signal source signal to the display device so that the display device can display the content output by the external controlled device. The controlled device can be a signal input device, such as an external host, external terminal, or other device capable of outputting display signals to the display device. The signal source signal can be input to the display device via one or more of HDMI, Type-C, and DP.

[0078] After the display device completes the event conversion, it can also output the wheel event and / or key event from the converted control event to the external controlled device in the form of an input event report. Specifically, the display device can send the converted event to the external controlled device in the form of a HID report via Type-C and / or USB. After receiving the HID report, the external controlled device can identify it as a mouse input event and perform scrolling control based on the wheel event, and / or key control based on the key event, thus achieving the same control effect as if the external controlled device were directly connected to the input device.

[0079] In other words, in this embodiment, the connection between the external controlled device and the display device can include two types of connections: one is a display signal connection for transmitting signal source signals, such as an HDMI connection, a Type-C connection, or a DP connection; the other is a data connection for transmitting converted input events, such as a Type-C connection and / or a USB connection. In some embodiments, the signal source signal connection and the input event data connection can be implemented through different interfaces; in other embodiments, signal source signal transmission and HID report transmission can also be implemented simultaneously through the same interface, which is not limited in this application.

[0080] Through the above interaction method, the contact events generated by the input device are converted by the display device and can not only be used for input response on the display device side, but also be further output to the controlled device, so that the controlled device can obtain control capabilities corresponding to the direct connection of the mouse, thereby realizing the reverse control function in the display device scenario.

[0081] Figure 3 An apparatus for implementing a method for reverse control of a display device is shown, comprising: The access module 201 is used to receive input signals from an input device. The input device can be an HID device conforming to a human-machine interface protocol. The access module can receive the raw input signals reported by the input device through the input interface of the display device. The raw input signals may include displacement information, key information, and data corresponding to contact events generated by the input sensing area of ​​the input device. The function of the access module is to provide a source of raw input data for subsequent device identification, drive matching, and event conversion.

[0082] In one possible implementation, the access module is used not only to receive input signals from the input device, but also to receive signal source signals from external controlled devices to the display device; in other implementations, the input access module and the signal source access module may be independently configured functional modules, and this application does not limit this.

[0083] The identification and driver matching module 202 is used to match the input device with a target driver module. Specifically, after detecting the input device's access, the identification and driver matching module can obtain the device identification information of the input device. The device identification information may include at least a product identification code and / or a manufacturer identification code, and may also include device type information, product name information, and / or report description information. The identification and driver matching module compares the device identification information with preset driver matching rules, and when the comparison result meets preset conditions, matches the input device to the target driver module. In some embodiments, the target driver module may include an adapted driver module adapted based on the product identification code and / or manufacturer identification code, such as the driver processing module corresponding to "hid-magicmouse". That is, the adapted driver module can be formed by supplementing the product identification code and / or manufacturer identification code matching items, and by extending the device identification logic and / or supplementing the event parsing rules, so that the target driver module can specifically parse and process the input signal according to the data organization method of the input device.

[0084] Event conversion module 203 is used to convert contact events in the input signal into corresponding control events, particularly scroll wheel events and / or button events. Specifically, the event conversion module can be implemented by the target driving module or work in conjunction with the target driving module. The event conversion module parses the input signal and extracts contact events generated by the input sensing area of ​​the input device. The event conversion module can classify and convert the contact events according to the event type, state change characteristics, displacement change characteristics, and / or timing characteristics. In some embodiments, the event conversion module can convert drag-type contact events into scroll wheel events and click-type contact events into button events. In some embodiments, the recognition of the middle button event does not distinguish between the number of contact points or the source form of tap or press; as long as a preset judgment condition is met, a corresponding middle button event is generated.

[0085] The event output module 204 is used to output control events to an external controlled device. Specifically, the event output module can organize the control events generated by the event conversion module according to a preset output format and output them to the external controlled device in the form of, for example, a HID report. The event output module can output the HID report via the USB output interface and / or Type-C channel of the display device. The HID report may include one or more of the following: event type identifier, scroll direction parameter, scroll amount parameter, button status identifier, and event timing information. In some embodiments, the event output module can also perform event sorting, status completion, report caching, transmission timing adjustment, and / or interface adaptation processing on the converted events to improve the stability of the external controlled device's recognition of the HID report.

[0086] The reverse control execution module 205 is used to enable the input device to control the external controlled device. Specifically, the external controlled device can be an external input source device connected to the display device. After receiving the HID report output by the event output module, the external input source device can parse the HID report and perform scrolling control based on the scroll wheel event, and / or perform key control based on the key event. Thus, the external controlled device functions as if it were directly connected to the input device, thereby realizing the reverse control process of the display device forwarding input events.

[0087] In some implementations, the event output module and the reverse control execution module can cooperate to achieve parallel processing of local reporting and reverse control output. In other words, the converted event can be used for response by the display device's local system, and can also be used synchronously as an input event source for external controlled devices. This improves the display device's compatibility with specific mouse-type input devices while enabling reverse control operations of external input source devices by the input device.

[0088] The aforementioned modules can be implemented entirely or partially through software, hardware, or a combination thereof. For example, each module can be implemented by a processor executing program instructions stored in memory, or by one or more functional units from the driver layer, system service layer, and / or input forwarding processing module collaboratively; this application does not limit this. The aforementioned modules can be embedded in hardware or independently of the processor in a computer device, or stored in software in the memory of a computer device, so that the processor can call and execute the operations corresponding to each module.

[0089] In addition, this application also provides an electronic device, Figure 4 This is a schematic block diagram of an electronic device 300 provided in an embodiment of this application. The electronic device includes a processor 301 and a memory 302, which are communicatively connected. In some embodiments, the electronic device 300 can be a display device, such as a monitor, smart display terminal, television, commercial display device, or other display devices with signal source input and input event processing capabilities. The electronic device 300 may also include an input interface for receiving input signals from input devices, and / or an output interface for communicating with a controlled device. The input interface can be used to receive input signals reported by a mouse-type input device; the output interface can be used to output converted control events to the controlled device. The input interface and / or output interface may include one or more of the following: USB interface, Type-C interface, HDMI interface, DP interface, or other data / signal transmission interfaces.

[0090] In some embodiments, the electronic device 300 may further include a signal source interface for receiving signal source signals input from a controlled device. The signal source interface may include a USB interface, a Type-C interface, an HDMI interface, a DP interface, or other display / data interfaces. The controlled device can input signal source signals to the electronic device 300 through the signal source interface, and the electronic device 300 can display based on the signal source signals; simultaneously, the electronic device 300 can also generate control events based on the input signals from the input device and output the control events to the controlled device to achieve reverse control.

[0091] The memory 302 stores program instructions that can be executed by the processor 301 to implement the display device reverse control method described in any of the preceding embodiments. Specifically, the processor 301 can execute the program instructions to receive input signals from an input device, match the input device with a target driving module, convert contact events in the input signals into control events corresponding to the contact events, and output the converted control events to the controlled device to enable the input device to control the controlled device.

[0092] The controlled device can be an external input source device connected to the electronic device 300, or it can be a target function module or target processing object inside the electronic device 300. When the controlled device is an external input source device, the electronic device 300 can output the control event to the external input source device in the form of an HID report through a USB interface and / or a Type-C interface, so that the external input source device can obtain the input control effect corresponding to that of a directly connected input device.

[0093] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by software instructions.

[0094] It is understood that the memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0095] This application also provides a computer-readable storage medium for storing a computer program. Optionally, this computer-readable storage medium can be applied to the electronic device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the electronic device in the various methods of the embodiments of this application. For the sake of brevity, further details are omitted here.

[0096] Those skilled in the art will 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, or a combination of computer software and electronic hardware. 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.

[0097] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for reverse control of a display device, characterized in that, The method includes: Receive input signals from input devices; Match the input device with the target driver module; The contact events in the input signal are converted into control events corresponding to the contact events; The control event is output to an external controlled device for the input device to control the external controlled device.

2. The method according to claim 1, characterized in that, The step of matching the input device with the target driver module includes: Based on the product identifier (PID) and / or manufacturer identifier (VID) of the input device, the input device is matched to the target driver module.

3. The method according to claim 2, characterized in that, The target driving module includes: The adapted driver module is based on the PID and / or VID.

4. The method according to claim 1, characterized in that, The step of converting the contact event in the input signal into a control event corresponding to the contact event includes: The control events include scroll wheel events and / or key events; and Convert the drag-type contact events in the contact events into scroll wheel events; Convert click-type touch events in the touch events into button events.

5. The method according to claim 4, characterized in that: The key events include the middle key event.

6. The method according to claim 4, characterized in that: The drag-type contact events include sliding events along the input sensing area, and The rolling direction of the roller event is determined based on the sliding direction of the sliding event; the rolling amount of the roller event is determined based on the sliding displacement of the sliding event.

7. The method according to claim 1, characterized in that: The input device includes a human-machine interface device (HID); The external controlled device is an external input source device connected to the display device, and the control event is output to the external controlled device in the form of the HID report; The external controlled device performs scrolling control and / or key control based on the control event.

8. A display device reverse control device, characterized in that, The device includes: The access module is used to receive input signals from input devices; The identification and driver matching module is used to match the input device with the target driver module; The event conversion module is used to convert the contact events in the input signal into control events corresponding to the contact events; An event output module is used to output the control events to external controlled devices; The reverse control execution module is used to enable the input device to control the external controlled device.

9. An electronic device comprising a processor and a memory, the memory storing program instructions which, when executed by the processor, implement the steps of the method as claimed in any one of claims 1 to 7.

10. A computer storage medium storing program instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 7.

Images