Control method for accessibility service function, device interaction system, and computing device

Abstract

This specification provides a control method, device interaction system, and computing device for accessibility service functions. The solution is applied to an external human-computer interaction device, which establishes a bidirectional communication channel with a target terminal device. The method includes: sending a request to the target terminal device to enable an accessibility application list page, causing the target terminal device to display the accessibility application list page; and, once the accessibility application list page has been rendered, sending a simulated keyboard command to the target terminal device, causing the target terminal device to respond to the simulated keyboard command and perform an operation on the accessibility application list page to enable the accessibility service function. This improves convenience and efficiency while reducing maintenance costs.

Description

Technical Field

[0001] This specification relates to one or more embodiments in the technical field of computer applications and mobile Internet, and particularly to a control method for accessibility service functions. This specification also relates to another control method for accessibility service functions, a device interaction system, a computing device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] With the deep integration of mobile payment and Internet of Things technologies, human-computer interaction modes are widely used in external human-computer interaction devices and terminal devices.

[0003] Currently, in order to support specific lightweight services, terminal devices typically need to have the target application pre-installed, and the service process is called by the upper-layer Software as a Service (SaaS) application.

[0004] However, due to strict system function control on some terminal devices or differences in vendor customization strategies, target applications often struggle to automatically enable accessibility services, leading to the failure of accessibility services on certain models. Furthermore, traditional manual authorization paths are complex and time-consuming, prone to configuration errors, heavily reliant on on-site intervention, resulting in poor convenience, low configuration efficiency, and high maintenance costs. Therefore, a more convenient method for controlling accessibility services is urgently needed. Summary of the Invention

[0005] In view of this, one or more embodiments of this specification provide a control method, device interaction system and computing device for accessibility service functions to improve convenience and efficiency and reduce operation and maintenance costs.

[0006] According to a first aspect of one or more embodiments of this specification, a control method for accessibility service functions is provided, applied to an external human-computer interaction device, wherein a bidirectional communication channel is established between the external human-computer interaction device and a target terminal device, comprising: Send an accessibility application list page enable request to the target terminal device so that the target terminal device displays the accessibility application list page; Once the accessibility application list page has finished rendering, a simulated keyboard command is sent to the target terminal device, causing the target terminal device to respond to the simulated keyboard command and perform an operation to enable accessibility services on the accessibility application list page, thereby enabling the accessibility service function.

[0007] According to a second aspect of one or more embodiments of this specification, another method for controlling accessibility service functions is provided, applied to a target terminal device, wherein a bidirectional communication channel is established between the target terminal device and an external human-computer interaction device, comprising: Receive a request from the external human-computer interaction device to open the accessibility application list page; In response to the accessibility application list page opening request, the accessibility application list page is displayed; Receive simulated keyboard commands sent by the external human-computer interaction device after the accessibility application list page has been rendered; In response to the simulated keyboard command, an operation to enable accessibility services is performed on the accessibility application list page, thereby enabling the accessibility service function.

[0008] According to a third aspect of one or more embodiments of this specification, a device interaction system is provided, including an external human-computer interaction device and a target terminal device, wherein a bidirectional communication channel is established between the external human-computer interaction device and the target terminal device; The external human-computer interaction device is used to send a request to the target terminal device to open the accessibility application list page; The target terminal device is configured to receive the accessibility application list page opening request sent by the external human-computer interaction device, and in response to the accessibility application list page opening request, display the accessibility application list page. The external human-computer interaction device is used to send simulated keyboard commands to the target terminal device after the accessibility application list page has been rendered. The target terminal device is configured to receive simulated keyboard commands sent by the external human-computer interaction device, and in response to the simulated keyboard commands, perform an operation to enable accessibility services on the accessibility application list page, thereby enabling the accessibility service function.

[0009] According to a fourth aspect of one or more embodiments of this specification, a computing device is provided, including a memory, a processor, and computer instructions stored in the memory and executable on the processor, wherein the steps of a control method are described, wherein the processor executes the computer instructions to implement the accessibility service function.

[0010] According to a fourth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions, which, when executed by a processor, implement the steps of a control method for the accessibility service function.

[0011] According to a fifth aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the control method for the above-described accessibility service function.

[0012] One embodiment of this specification can achieve at least the following beneficial effects: by utilizing the keyboard simulation capability of the external human-computer interaction device and its bidirectional communication capability with the target terminal device, a request to open the accessibility application list page is sent to the target terminal device and the page rendering status is received. After the page is ready, standardized simulated keyboard commands are injected to automatically navigate and execute the opening operation. By automating and standardizing the opening of accessibility services through the external human-computer interaction device, convenience and efficiency are improved, and maintenance costs are reduced. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a schematic diagram of the overall scheme flow of a control method for an accessibility service function provided in the embodiments of this specification; Figure 2 This is a flowchart of a control method for an accessibility service function provided in one embodiment of this specification; Figure 3 This is a flowchart of another control method for an accessibility service function provided in one embodiment of this specification; Figure 4 This is a flowchart illustrating a control method for accessibility service functions in a practical application scenario, provided by one embodiment of this specification. Figure 5 This is a schematic diagram of a control method for accessibility service functions in a practical application scenario provided by an embodiment of this specification; Figure 6 This is a timing diagram of a control method for accessibility service functions in a practical application scenario provided by an embodiment of this specification. Figure 7 This is a schematic diagram of the structure of a device interaction system provided in one embodiment of this specification; Figure 8 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0015] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0016] This specification uses specific terms to describe embodiments thereof. Terms such as "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "an embodiment," "one embodiment," or "an alternative embodiment" in different locations throughout this specification do not necessarily refer to the same embodiment. Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described herein, as well as the features of those different embodiments or examples, without contradiction.

[0017] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “an,” “an,” “the,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification includes any or all possible combinations of one or more associated listed items.

[0018] The terms “comprising,” “including,” or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in the process, method, product, or apparatus that includes said elements is not excluded.

[0019] Although the terms "first," "second," etc., may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, "first" may also be referred to as "second," and similarly, "second" may also be referred to as "first," without departing from the scope of one or more embodiments of this specification. Ordinal numbers such as "first," "second," etc., do not necessarily indicate order; often they are used to facilitate the distinction of objects. For example, "first server" and "second server" usually refer to two servers. To distinguish these two servers, they are described as "first server" and "second server." Of course, sometimes these two servers may be the same server.

[0020] In this specification, the word "if" may be interpreted as "when," "when," or "in response to determination," depending on the context.

[0021] In this specification, unless explicitly stated otherwise, "receiving and sending data" does not necessarily mean direct receiving and sending; it can also mean indirect receiving and sending. For example, A receiving data sent by B can be understood as A directly receiving the data sent by B, or it can be understood as A indirectly receiving the data sent by B through other entities such as C. Similarly, B sending data to A can be understood as B sending the data directly to A, or it can be understood as B indirectly sending the data to A through other entities such as C. Here, C can be one entity, or it can be two or more entities.

[0022] In this specification, unless explicitly stated otherwise, the relationships between structures can be direct or indirect. For example, when describing "A is connected to B," unless it is explicitly stated that A and B are directly connected, it should be understood that A can be directly connected to B or indirectly connected to B. Similarly, when describing "A is on top of B," unless it is explicitly stated that A is directly above B (AB is adjacent and A is above B), it should be understood that A can be directly above B or indirectly above B (AB is separated by other elements, and A is above B). And so on.

[0023] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. The collection, use and processing of related data shall comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation entry points shall be provided for users to choose to authorize or refuse.

[0024] The following explains the terms and concepts used in one or more embodiments of this specification.

[0025] Small commands: In this field, this typically refers to a lightweight bidirectional data communication protocol or mechanism implemented based on near-field communication or physical wired connections (such as USB or serial ports). It establishes a stable command transmission channel at the hardware level or system level, enabling external devices to send control commands to the host device and receive execution results. This mechanism is widely used in scenarios requiring external devices to assist or control host service flows, such as the collaborative interaction between financial payment terminals and peripherals. Those skilled in the art should understand that this application is also applicable to other device combinations that support similar bidirectional command communication.

[0026] Assisted payment devices (APDs) are external human-machine interface devices equipped with near-field communication (NFC) capabilities (such as NFC and RFID) or standard wired interfaces. These devices typically have built-in security chips and communication modules, enabling them to establish stable two-way communication channels with host terminal devices (such as cash registers and POS machines) to achieve data exchange and service collaboration. In near-field communication-based payment scenarios, APDs can connect to the cash register wirelessly or via wired connections. Consumers can interact with the APD using mobile devices such as smartphones, for example, by tapping the device to make a payment via NFC. APDs can also act as passive near-field communication devices, providing tag information to the user's mobile terminal.

[0027] Accessibility Service: An assistive function provided by an operating system with advanced system capabilities. It allows authorized applications to observe the state of the user interface on behalf of the user and even simulate user interactions (such as clicking, swiping, and typing). Originally designed to help users with disabilities use smart devices more conveniently, in this application, this technology is innovatively applied to achieve automated system configuration operations across applications.

[0028] Human Interface Device (HID) protocol: A standardized device communication specification (usually based on the USB protocol) widely used for data interaction between external input devices such as keyboards, mice, and game controllers and the host computer. A key feature of the HID protocol is that the operating system typically includes its generic driver, supporting "plug and play" for devices. This allows external devices to quickly inject input events into the terminal device via the protocol.

[0029] In related technologies, once a target application possesses accessibility service capabilities, it can more accurately identify service call nodes and device operation trajectories. This is crucial for monitoring systems to perceive the real-time status of external devices and optimize the service interaction experience. Accessibility services for target applications often cannot be automatically activated; therefore, achieving automatic activation of accessibility services without manual intervention has become a key challenge.

[0030] To address the shortcomings in related technologies, this specification provides a more convenient method for controlling accessibility services in its embodiments. By utilizing the keyboard simulation capability of the external human-computer interaction device and its bidirectional communication capability with the target terminal device, a request to open the accessibility application list page is sent to the target terminal device, and the page rendering status is received. After the page is ready, standardized simulated keyboard commands are injected to automatically navigate and execute the opening operation. By automating and standardizing the opening of accessibility services through the external human-computer interaction device, convenience and efficiency are improved, and maintenance costs are reduced.

[0031] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0032] Figure 1 This is a schematic diagram of the overall scheme flow of a control method for an accessibility service function provided in an embodiment of this specification.

[0033] like Figure 1 As shown, the system includes an external human-computer interaction device 101, a target terminal device 102, a network 103, a server device 104, and a server storage device 105. A wired or wireless two-way communication channel is established between the external human-computer interaction device 101 and the target terminal device 102 for collaboratively automating service processes. The target terminal device 102 interacts with the server device 104 via the network 103. The server device 104 is connected to the server storage device 105 to store configuration information, service data, and accessibility service status records. When the target application is launched for the first time and accessibility services are detected not being enabled or malfunctioning, the external human-computer interaction device 101 can capture or generate input events and send a request to the target terminal device 102 to enable the accessibility application list page. In response to the request, the target terminal device 102 loads and displays the accessibility application list page and can also feed back the page rendering status to the external human-computer interaction device 101. After the external human-computer interaction device 101 detects that the page rendering is complete, it sends standardized simulated keyboard commands to the target terminal device 102, driving the target terminal device 102 to automatically locate and click the option to enable accessibility services without human intervention, thereby achieving automatic enabling of accessibility services.

[0034] In such Figure 1In the application scenarios shown, the server can connect to one or more terminal devices via a local area network (LAN), a wide area network (WAN), an internet connection, or other types of data networks. Figure 1 The servers mentioned can include, but are not limited to, any device, equipment, platform, or equipment cluster with computing and processing capabilities. Figure 1 The external human-computer interaction device 101 may include, but is not limited to, HID devices, assisted payment devices, or smartphones, tablets, laptops, PDAs, personal computers, smart home devices, in-vehicle devices, etc. The target terminal device 102 may include, but is not limited to, POS machines, cash registers, self-service checkout devices, or smart vending machines, or smartphones, tablets, laptops, PDAs, personal computers, smart home devices, in-vehicle devices, etc.

[0035] In one or more embodiments of this specification, a control method for an accessibility service function is provided. One or more embodiments of this specification also relate to another control method for an accessibility service function, a device interaction system, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0036] Figure 2 This is a flowchart of a control method for an accessibility service function provided in one embodiment of this specification. The execution subject of this process can be an external human-computer interaction device, and a two-way communication channel is established between the external human-computer interaction device and the target terminal device.

[0037] An external human-computer interaction (HID) device can be an external hardware device with a human-computer interaction interface and data processing capabilities. It can establish a communication connection with the target terminal device through standard protocols and simulate user input operations. An external HID device can have a built-in processor and storage unit, running firmware to control the communication process. For example, in a retail scenario, this device can be an auxiliary payment device or a shortcut key controller for the HID protocol, connected to a POS machine via a USB interface or wireless communication such as Bluetooth / WiFi.

[0038] The target terminal device can be an electronic device that carries service applications and processes core transaction logic, possessing a display interface and system settings functions. The target terminal device runs an operating system, manages system functions and a list of installed applications, and is responsible for responding to requests from external human-computer interaction devices and rendering the graphical user interface. For example, in a retail scenario, this device could be a smart POS machine, desktop cash register, self-checkout machine, or smart vending machine used by merchants for payment collection. For instance, the target terminal device could be a terminal device running the Android system, or it could be a terminal device running other operating systems.

[0039] A bidirectional communication channel serves as the physical link and logical protocol stack connecting external HMI devices and target terminal devices, supporting full-duplex or half-duplex data transmission. This channel can transmit not only service commands but also device status and interface feedback signals, ensuring that the external HMI device can perceive changes in the terminal interface in real time. For example, in retail scenarios, this channel could be a HMI protocol channel established via a USB interface or a wireless channel established via Bluetooth / WiFi.

[0040] like Figure 2 As shown, the process may include the following steps: Step 202: Send an accessibility application list page activation request to the target terminal device so that the target terminal device displays the accessibility application list page.

[0041] The accessibility app list page is a system-level page within the operating system settings menu of a target terminal device, used for centralized management of accessibility applications. The accessibility app column typically displays an enumeration of installed apps that declare accessibility features, even if these apps do not have accessibility services enabled. Users or simulated users can enable or disable accessibility services for specific apps. For example, in Android, this page corresponds to the "Settings -> Accessibility -> Downloaded Services" interface.

[0042] The accessibility app list page access request can be a request instruction packet sent by an external human-computer interaction device to trigger the target terminal device to navigate to a specific depth of system settings. The accessibility app list page access request can be encapsulated as a standard intent or deep link parameter, directly launching the settings page using system APIs, avoiding complex UI navigation. For example, in an Android scenario, this request can be an Intent broadcast request carrying the android.settings.ACCESSIBILITY_SETTINGS action. Alternatively, the external human-computer interaction device can send simulated key presses to the target terminal device via the Human-Computer Interaction Device (HID) protocol, simulating the user's manual operation path, clicking step-by-step to enter the "Accessibility" submenu under the "Settings" menu until navigating to the accessibility app list page.

[0043] Sending an accessibility application list page enable request to the target terminal device, specifically by sending the accessibility application list page enable request to the target terminal device through a two-way communication channel.

[0044] For example, in a retail POS deployment scenario, the external human-computer interaction device is an auxiliary payment device plugged into the USB port of an Android POS machine. During device cold starts, initial configuration after application upgrades, periodic heartbeat detection revealing functional loss, the upper-layer SaaS service application initiating a payment request but detecting no response, or a system upgrade resetting application functionality, the auxiliary payment device first sends an Intent request containing the android.settings.ACCESSIBILITY_SETTINGS action to the POS machine via the HID channel.

[0045] Step 204: Once the accessibility application list page has finished rendering, send a simulated keyboard command to the target terminal device so that the target terminal device responds to the simulated keyboard command and performs an operation to enable accessibility services on the accessibility application list page, thereby enabling the accessibility service function.

[0046] Simulated keyboard commands can be binary data streams that simulate the key sequences of a physical keyboard. These commands typically conform to Human-Computer Interaction (HID) device protocols and are sent sequentially to the terminal to simulate user actions such as focus switching, directional control, confirmation of selection, and deselection, thus automatically completing the click actions on the interface. For example, a simulated keyboard command might be: {DOWN key} (select application) -> {TAB key} (move focus to switch) -> {ENTER key} (confirm on).

[0047] Accessibility services can be high-priority interaction monitoring functions requested from the operating system. Once enabled, accessibility services can monitor window content and user actions, which is essential for automated data entry and process control. For example, in a retail scenario, accessibility services can automatically recognize and enter the amount in the payment input field, eliminating the need for cashiers to manually type. Another example is that accessibility services allow target applications to take over the system's HID event flow. When an external barcode scanner scans a product, the target application can capture the barcode through accessibility services and directly inject it into the currently active input field, achieving an accessible interactive experience.

[0048] Accessibility services allow authorized target applications to perform actions on behalf of users, such as AndroidAccessibilityService and iOS VoiceOver API.

[0049] Sending simulated keyboard commands to the target terminal device is specifically done by sending simulated keyboard commands to the target terminal device through a bidirectional communication channel.

[0050] When the accessibility application list page is rendered, one possible approach is to listen to the page rendering completion notification signal sent by the target terminal device to determine that the accessibility application list page is rendered. Another possible approach is to define the accessibility application list page as rendered after a preset delay. Yet another possible approach is to listen to the terminal screen of the target terminal device and determine the accessibility application list page is rendered based on the content displayed on the screen. No further limitation is made here.

[0051] For example, in response to an Intent request containing the `android.settings.ACCESSIBILITY_SETTINGS` action, the POS machine immediately redirects to the accessibility service list page and sends a signal indicating that the page rendering is complete to the assisted payment device. Upon receiving the rendering completion signal, the assisted payment device, which has pre-stored page layout information for the accessibility settings interface of mainstream Android systems (either obtained from the POS machine or downloaded from the server), determines that the current system focus is on the first option at the top of the list. Then, based on the known index position of the target application ("Quick Payment Plugin") in the list (e.g., the 4th item), the assisted payment device calculates that the focus needs to be moved down three times, and therefore sends three consecutive `{DOWN}` key commands to precisely position the focus on the target application option in the list. Next, the device sends the {ENTER} key command to enter the accessibility service page of the target application. Finally, it sends the {TAB key} (to move the focus to the "On" switch) and the {ENTER key} to confirm, thereby enabling the accessibility service function of the target application. The authorization and activation of the accessibility service function are completed automatically without the cashier having to go into the system settings and click through cumbersome steps.

[0052] The payment technologies described in one or more embodiments of this specification may include, for example, Near Field Communication (NFC), Wi-Fi, 3G / 4G / 5G, POS machine card swiping technology, QR code scanning technology, barcode scanning technology, Bluetooth, infrared, Short Message Service (SMS), Multimedia Message Service (MMS), etc.

[0053] While one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is merely one possible execution order among many steps and does not represent the only possible execution order. The order of some steps may be adjusted according to actual needs, or some steps may be omitted. When the claims involve method steps, changes in the order of such steps, or parallel execution between steps, are also within the scope of protection of the claims.

[0054] Figure 2 The method described herein utilizes the keyboard simulation capability of the external human-computer interaction device and its bidirectional communication capability with the target terminal device to send an accessibility application list page opening request to the target terminal device and receive the page rendering status. After the page is ready, standardized simulated keyboard commands are injected to automatically navigate and execute the opening operation. By automating and standardizing the opening of accessibility services through the external human-computer interaction device, convenience and efficiency are improved, and operation and maintenance costs are reduced.

[0055] based on Figure 2 In addition to the method described herein, this specification also provides some specific implementation methods of the method, which will be described below.

[0056] In one optional embodiment of this specification, the simulated keyboard commands include at least one of focus switching key commands, directional control key commands, and confirmation selection key commands.

[0057] Focus switching key commands can be low-level input signals used to control the movement of focus between different interactive controls in a graphical user interface (GUI). For example, in a retail scenario, the Tab key, corresponding to a standard HID keyboard key, is used to switch the selected service item in the POS machine settings interface.

[0058] Directional control key commands can be low-level input signals used to control the focus or cursor movement in a graphical user interface (GUI). For example, in a retail scenario, the UP Arrow, Down Arrow, Left Arrow, and Right Arrow keys, corresponding to standard HID keyboard keys, are used to move the focus or cursor item by item in the accessibility application list on a POS machine.

[0059] Confirmation selection key commands can be low-level input signals used to trigger the default action of the control in a graphical user interface (GUI) where the focus or cursor is located. For example, in a retail scenario, the Enter key, corresponding to a standard HID keyboard, is used by the POS machine to confirm the activation of the selected "Quick Payment Plugin" (target application).

[0060] In the embodiments of this specification, the simulated keyboard commands include at least one of the following: focus switching key commands, directional control key commands, and confirmation selection key commands. This enables external human-computer interaction devices to inject underlying input events into the target terminal device, transforming touch simulation into key events. This achieves standardized and stable seamless automatic navigation and activation operations across system versions and device manufacturers, reducing the maintenance costs of offline devices.

[0061] In one optional embodiment of this specification, the simulated keyboard commands are generated based on a human-computer interaction device protocol; The focus switching button instruction, the direction control button instruction, and the confirm selection button instruction each correspond to a key value code; Based on the current focus position information and target control position information in the accessibility application list page or its subpage, determine the key value code or key value code combination to be sent. The focus switching button instruction is generated based on the current focus position information and the target control position information; the focus switching button instruction contains a key value code or key value code combination that can be recognized by the target terminal device for performing focus switching; The directional control button instruction is generated based on the position information of the current focus and the position information of the target control; the directional control button instruction contains a key value code or key value code combination that can be recognized by the target terminal device for directional control; The confirmation selection button instruction is generated based on the current focus position information and the target control position information; the confirmation selection button instruction contains a key value code or key value code combination that can be recognized by the target terminal device for confirming the selection.

[0062] The key value code for a focus switching button command can be a unique numerical code that identifies the focus switching button command. For example, in the Android system, it corresponds to the system-level key value KEYCODE_TAB (key value code 61).

[0063] The key value code for directional control button commands can be a unique numerical code that identifies the directional control button command. For example, in the Android system, the corresponding system-level key values ​​are: KEYCODE_DPAD_UP (key value code 19), KEYCODE_DPAD_DOWN (key value code 20), KEYCODE_DPAD_LEFT (key value code 21), and KEYCODE_DPAD_RIGHT (key value code 22).

[0064] The key value code for confirming a key selection command can be a unique numerical code that identifies the command. For example, in the Android system, it corresponds to the underlying system key value KEYCODE_ENTER (key value code 66).

[0065] The target control is an interactive control on the accessibility application list page or a subpage of the accessibility application list page that needs to enable the target application. Target controls include, but are not limited to: the application icon, application link, application name text, application toggle button, radio button, confirmation control, and back control of the target application whose accessibility service function needs to be enabled.

[0066] The current focus location information can be the coordinates of the current focus location within the accessibility application list page or a subpage of the accessibility application list page.

[0067] The location information of the target control can be the coordinates of the currently positioned interactive control in the accessibility application list page or a subpage of the accessibility application list page.

[0068] For example, when the external human-computer interaction device determines that the current focus is at the top of the accessibility application list page and the target application "Quick Payment Plugin" is the fourth item in the list, it automatically calculates, based on the vertical spacing between the two in the page layout information, that the focus needs to be moved down three times. Therefore, it generates a sequence of directional control button commands containing three "KEYCODE_DPAD_DOWN" (key value code 20) commands. Subsequently, when the external human-computer interaction device detects through the bidirectional communication channel that the focus has been correctly positioned in the control area of ​​the target application, it generates a confirmation selection button command containing "KEYCODE_ENTER" (key value code 66), completing the jump from the accessibility application list page to the accessibility service opening page of the target application.

[0069] In the embodiments described in this specification, by dynamically generating key-value codes or combinations of key-value codes based on the relative positional relationship between the current focus and the target control, external human-computer interaction devices can more accurately inject underlying input events into the target terminal device. This transforms touch simulation into physical-level button events that are directly responded to by the system's underlying layer, enabling automatic navigation and enabling accessibility services on the accessibility application list page. This automates and standardizes the enabling of accessibility services, improves convenience and efficiency, and reduces operation and maintenance costs.

[0070] In one optional embodiment of this specification, the simulated keyboard instructions include a first simulated keyboard instruction, a second simulated keyboard instruction, and a third simulated keyboard instruction; Sending a simulated keyboard command to the target terminal device, causing the target terminal device to respond to the simulated keyboard command and perform an operation to enable accessibility services on the accessibility application list page, thereby enabling the accessibility service function, includes: Send the first simulated keyboard command to the target terminal device so that the target terminal device responds to the first simulated keyboard command, selects the target application whose accessibility service function is to be enabled from the accessibility application list page, and displays the accessibility service opening page for the target application; Send the second simulated keyboard instruction to the target terminal device so that the target terminal device responds to the second simulated keyboard instruction, selects the enable radio button from the accessibility service opening page, and displays the accessibility service authorization pop-up; The third simulated keyboard instruction is sent to the target terminal device, so that the target terminal device responds to the third simulated keyboard instruction, selects the confirmation control from the accessibility service authorization pop-up, and enables the accessibility service function.

[0071] The first simulated keyboard command can be the low-level input signal used to execute the first step of the interface interaction in a multi-step graphical user interface (GUI) automated navigation process. When applied to an accessibility application list page, the first simulated keyboard command aims to locate and access the accessibility service page of the target application. For example, in a retail scenario, this corresponds to the sequence of key values ​​that follow: pressing the {Down key} to move the focus to the "Quick Payment Plugin" (the target application) in the list, and then pressing the {Enter key} to confirm.

[0072] The second simulated keyboard command can be the underlying input signal used to execute the second step of the interface interaction in a multi-step graphical user interface (GUI) automated navigation process. This second simulated keyboard command operates on the accessibility service opening page, aiming to locate and pop up the accessibility service authorization pop-up. For example, in a retail scenario, it corresponds to the key value sequence in the accessibility service opening page of the "Quick Payment Plugin" (target application), where the focus is moved to the "Enable" or "On" radio button using the {Tab key} and confirmed by pressing the {Enter key}.

[0073] The third simulated keyboard command can be the underlying input signal used to execute the third step of the interface interaction in a multi-step graphical user interface (GUI) automated navigation process. The third simulated keyboard command acts on the accessibility service authorization pop-up to locate and select the confirmation control. For example, in a retail scenario, corresponding to the pop-up "Allow the quick payment plugin to access accessibility features?" pop-up, it corresponds to the key value sequence of the confirmation operation performed by moving the focus to the "Allow" or "Confirm" button using the {Tab key} and pressing the {Enter key} in the {Allow} pop-up "Allow accessibility features?" pop-up.

[0074] The target application can be a background service program pre-installed in the target terminal device to handle near-field communication. Target applications include, but are not limited to, small command applications, automated testing tools, remote assistance software, or system-level auxiliary plugins. For example, in a retail scenario, this application could be a "quick payment plugin" responsible for receiving and parsing instructions transmitted by the auxiliary payment device and using accessibility features to fill the parsed data into the POS machine's payment interface.

[0075] The accessibility service open page for a target application can be a system-level page within the target terminal device's operating system, specifically designed to display and configure the detailed status of the target application's accessibility services. This open page typically includes service on / off switches, feature status descriptions, and advanced settings options. For example, in a retail scenario, it corresponds to the detailed configuration interface in the Android system's "Settings -> Accessibility -> Quick Pay Plugin (Target Application)".

[0076] Enable radio buttons are front-end UI controls located on the accessibility service's open page, indicating whether to activate the application's accessibility service. Enable radio buttons typically appear as radio buttons or switches, and their selected state determines whether the background service starts with the system. For example, in a retail scenario, this corresponds to the "Use Quick Payment Plugin" switch control at the top of the "Quick Payment Plugin" details page.

[0077] Accessibility service authorization pop-ups can be warning and confirmation dialog boxes that are intercepted and displayed by the system security framework when an attempt is made to change the accessibility service status. For example, in a retail scenario, this corresponds to a system-level pop-up window that prompts "Allow the quick payment plugin to monitor your actions?" and includes "Cancel" and "OK" buttons.

[0078] The confirmation enable control can be a front-end UI element located in the accessibility service authorization pop-up, used to receive authorization instructions from the user (or a simulated user). Once the confirmation enable control is selected and activated, the system will officially write the feature configuration and set the service status to available. For example, in a retail scenario, this corresponds to the "OK" or "Allow" button on the right side of the aforementioned system-level pop-up.

[0079] Optionally, the first, second, and third simulated keyboard instructions are all configured as binary data packets containing a specific key value code sequence that conform to the Human-Computer Interaction Device (HID) protocol specification, so that the target terminal device can parse the data packets into corresponding physical keyboard input events.

[0080] The first simulated keyboard command is sent to the target terminal device via a bidirectional communication channel.

[0081] The second simulated keyboard command is sent to the target terminal device via a bidirectional communication channel.

[0082] The third simulated keyboard instruction is sent to the target terminal device via a bidirectional communication channel.

[0083] For example, after the assisted payment device learns that the POS machine has successfully rendered the "Accessibility Application List Page," it first sends a first simulated keyboard command (e.g., a HID command packet containing three {DOWN} and one {ENTER}) through a two-way communication channel. The POS machine parses this command, moves the focus down line by line on the screen, and finally selects "Quick Payment Plugin," then redirects to the accessibility service opening page for that application. Next, the assisted payment device sends a second simulated keyboard command (e.g., a HID command packet containing one {TAB} and one {ENTER}). The POS machine parses this command and clicks the "Enable" radio button by switching the focus. At this point, due to system security policy restrictions, an accessibility service authorization pop-up appears in the center of the screen asking "Allow the Quick Payment Plugin to monitor your operation?" Finally, the assisted payment device sends a third simulated keyboard command (e.g., a HID command packet containing one {TAB} and one {ENTER}). The POS machine parses this command, moves the focus from the default "Cancel" button to the "OK" button, and triggers a click event, thus completing the final authorization of the entire accessibility service function.

[0084] In the embodiments of this specification, a single complex automated activation operation is broken down into a multi-step, phased execution logic that includes a first simulated keyboard instruction, a second simulated keyboard instruction, and a third simulated keyboard instruction. The page state that the target terminal device should present (such as the accessibility service opening page, authorization pop-up, etc.) is clearly defined at each stage. This reduces the complexity of single-step instructions while improving the fault tolerance and readability of the overall automated process, and ensures the standardization and success rate of the accessibility service activation process.

[0085] In one optional embodiment of this specification, sending the first simulated keyboard command to the target terminal device includes: While delaying for a first preset time to allow the accessibility application list page to complete rendering, the first simulated keyboard instruction is sent to the target terminal device. Sending the second simulated keyboard command to the target terminal device includes: While delaying for a second preset time to allow the accessibility service open page to complete rendering, the second simulated keyboard command is sent to the target terminal device; Sending the third simulated keyboard command to the target terminal device includes: While delaying for a third preset time to allow the accessibility service authorization pop-up to complete rendering, the third simulated keyboard command is sent to the target terminal device.

[0086] The first preset duration can be a conservative waiting time interval set from the time the target terminal device is triggered to jump to the accessibility application list page until the external human-computer interaction device determines that the page is fully rendered and interactive. The first preset duration is intended to cover the page loading latency of the target terminal device and ensure that the UI thread is idle when the command is sent. For example, in a retail scenario, this corresponds to 500 milliseconds (ms) that the assisted payment device counts down using an internal timer after issuing a page opening request.

[0087] The second preset duration can be a conservative waiting time interval set from the time the target terminal device is triggered to jump to the accessibility service opening page of the target application until the external human-computer interaction device determines that the opening page is fully rendered and interactive. The second preset duration is intended to cover the page loading delay of the target terminal device and ensure that the UI thread is in an idle state when the command is sent. For example, in a retail scenario, this corresponds to 300 milliseconds (ms) after the POS machine responds to the first simulated keyboard command and jumps, and the auxiliary payment device counts down again through an internal timer.

[0088] The third preset duration can be a conservative waiting time interval set from the time the accessibility service authorization pop-up is displayed on the target terminal device until the external human-computer interaction device determines that the pop-up is fully rendered and interactive. The third preset duration is intended to cover the page loading delay of the target terminal device and ensure that the UI thread is idle when the command is sent. For example, it corresponds to 150 milliseconds (ms) for the auxiliary payment device to wait for the last time by counting down through the internal timer after the POS machine responds to the second simulated keyboard command and pops up the warning pop-up.

[0089] Optionally, the first preset duration, the second preset duration, and the third preset duration are all pre-configured in the storage unit of the external human-computer interaction device, and the size of each preset duration can be dynamically adjusted according to the historical page loading time of the target terminal device.

[0090] Optionally, the first preset duration, the second preset duration, and the third preset duration are all pre-configured in the storage unit of the external human-computer interaction device, and the size of each preset duration can be configured according to the hardware and software performance and / or system version of the target terminal device.

[0091] For example, the firmware of the assisted payment device has a pre-built adaptive timing control mechanism. When the assisted payment device sends a request to the POS machine to open the accessibility application list page, it does not immediately issue the first simulated keyboard command, but instead starts an internal timer to delay for a first preset duration (500ms) to ensure that the POS machine completes rendering. When the assisted payment device sends the first simulated keyboard command to the POS machine (selecting the small command application with the arrow keys and confirming entry into the details page), it does not immediately issue the second simulated keyboard command, but instead starts an internal timer to delay for a second preset duration (300ms) to ensure that even a POS machine with poor performance has sufficient time to complete the rendering of the accessibility service opening page. When the assisted payment device sends the second simulated keyboard command to the POS machine (switching focus and selecting the enable radio button to trigger the system pop-up), it does not immediately issue the third simulated keyboard command, but instead starts an internal timer to delay for a third preset duration (150ms) to ensure that even a POS machine with poor performance has sufficient time to complete the rendering of the accessibility service authorization pop-up.

[0092] In the embodiments of this specification, by introducing corresponding first preset duration, second preset duration and third preset duration as timing buffers before sending simulated keyboard commands at each stage, asynchronous synchronization of page rendering and execution between the external human-computer interaction device and the target terminal device is achieved. This ensures that each simulated input command is executed when the corresponding page is in an interactive state, greatly improving the compatibility across models and configurations of terminals and the robustness of the automated process.

[0093] In one optional embodiment of this specification, before sending the accessibility application list page opening request to the target terminal device, the method further includes: Upon receiving an accessibility service activation command from the server, or upon detecting that the target application is not authorized, a request for accessibility service function authorization status query is sent to the target terminal device. Receive the query results fed back by the target terminal device; Sending the accessibility application list page opening request to the target terminal device includes: If the query result indicates that accessibility services are not enabled, a request to enable the accessibility application list page is sent to the target terminal device.

[0094] Accessibility service activation commands can be low-level control signaling issued by the server to instruct the target terminal device to configure or activate the accessibility service functions of the target application. For example, in a retail scenario, this corresponds to the "initial deployment configuration" remote control signaling containing a specific service identifier issued by the cloud server to the assisted payment device.

[0095] An authorization status query request for accessibility services can be an inter-process communication data message initiated by an external human-computer interaction device to a target terminal device to detect whether a specific target application currently activates accessibility services. Authorization status query requests are typically encapsulated as standard system calls or custom communication protocols, aiming to obtain the on / off status of the corresponding service in the terminal system settings to avoid repeatedly executing unnecessary redundant operations. For example, in a retail scenario, this corresponds to a system function query command containing the package name "Quick Payment Plugin" sent by an auxiliary payment device to a POS machine through an established two-way communication channel.

[0096] The query result can be the status code value that the target terminal device receives after receiving the authorization status query request, which is then verified by the underlying system function management service and fed back to the external human-machine interaction device. The query result can be a Boolean value, an enumerated status code, or a string with a specific format, used to clearly indicate the authorization status of the current function. For example, in a retail scenario, it corresponds to the Boolean status code value of "authorized" or "not enabled" fed back to the auxiliary payment device through the data channel after verification by the POS system.

[0097] Sending an authorization status query request for accessibility service functions to the target terminal device, specifically by sending the authorization status query request for accessibility service functions to the target terminal device through a two-way communication channel.

[0098] The query results are received from the target terminal device via a bidirectional communication channel.

[0099] For example, after the auxiliary payment device powers on and initializes, it first sends an accessibility service authorization status query request containing the package name "Quick Payment Plugin" to the POS machine via a two-way communication channel. Upon receiving and parsing the request, the POS machine's system service queries its internal settings database and finds that the plugin's accessibility function was reset and disabled due to a forced system update the previous day. Therefore, it sends a query result to the auxiliary payment device indicating "not enabled." The auxiliary payment device then triggers a subsequent action to send a request to the POS machine to enable the accessibility application list page.

[0100] For example, the firmware of the assisted payment device registers a hook event to listen for the BOOT_COMPLETED broadcast of the Android system. Upon detecting this broadcast via the HID channel, the assisted payment device immediately sends a request to the POS machine in the background to query the authorization status of the accessibility service function for the "Quick Payment Plugin". After receiving and parsing the request, the system service on the POS machine queries its internal settings database and finds that the accessibility function of the plugin has been reset and disabled due to a forced system update the previous day. Therefore, it sends a query result to the assisted payment device indicating "not enabled". The assisted payment device then triggers a subsequent action to send a request to the POS machine to enable the accessibility application list page.

[0101] In the embodiments of this specification, by adding a pre-query mechanism for authorization status before performing time-consuming operations such as page navigation and simulated input, the external human-computer interaction device can intelligently perceive the current functional configuration of the target terminal device, avoiding redundant operation processes in the authorized state, reducing unnecessary system resource consumption, and improving the intelligence level and execution efficiency of device interaction.

[0102] In one optional embodiment of this specification, after sending the simulated keyboard command to the target terminal device, the method further includes: Receive accessibility service activation status information from the target terminal device to determine whether the accessibility service function has been successfully activated; If the accessibility service function is not successfully enabled, return to the step of sending the accessibility application list page enable request.

[0103] Accessibility service activation status information can be a status code or confirmation signal sent by the target terminal device to an external human-computer interaction device after receiving a simulated keyboard command and attempting to change system settings, indicating the result of the function change. For example, in a retail scenario, this corresponds to the "activation successful" or "activation failed" status code sent by the POS machine to the assisted payment device after receiving a third simulated keyboard command and successfully writing the accessibility function.

[0104] The accessibility service activation status information fed back by the target terminal device is received in the following manner: through a two-way communication channel, the accessibility service activation status information fed back by the target terminal device is received.

[0105] For example, after sending the third simulated keyboard command to the POS machine, the auxiliary payment device does not immediately consider the task complete. Instead, it activates a timeout listener to wait for feedback from the POS machine. When it receives a "failed to open" status code from the POS machine, the auxiliary payment device firmware determines that the automated process is abnormal (such as encountering unexpected user operation interference), then clears the command queue, resends the accessibility application list page opening request to the POS machine, and executes a new round of automated opening process until it receives a "successful to open" status code.

[0106] In the embodiments of this specification, a closed-loop control system with self-healing capabilities is constructed by introducing a loop verification mechanism for the enabled state after the instruction is issued, and deciding whether to re-execute the enabling process based on the verification result. This effectively addresses occasional anomalies or external interference during the automation process, ensuring that the barrier-free service can ultimately be successfully enabled, and further improving the reliability and automation level of the system.

[0107] In one optional embodiment of this specification, if the accessibility service function fails to be enabled, the process returns to the step of sending the accessibility application list page enable request, including: If the query result indicates that the accessibility service function is not enabled, then determine whether the preset retry threshold has been reached. If the retry threshold is not reached, return to the step of sending the accessibility application list page enable request; If the retry count threshold is reached, a preset alarm operation and / or log recording operation will be performed.

[0108] The retry threshold can be a pre-set maximum limit on the number of times an external human-computer interaction device is allowed to repeatedly execute the accessibility service activation process. For example, in a retail scenario, it corresponds to the maximum number of times (e.g., 3 times) that is allowed to repeatedly attempt to launch the settings page and simulate a click, as preset in the firmware of the assisted payment device.

[0109] Alarm actions can be audio-visual or graphical prompts executed by external human-computer interaction devices or target terminal devices when the maximum retry threshold is reached and accessibility services still cannot be successfully activated, prompting on-site personnel to intervene manually. For example, in a retail scenario, this corresponds to controlling the LED indicator on the auxiliary payment device to switch to red and flash rapidly, while simultaneously displaying a pop-up message on the POS machine screen: "Automatic configuration failed, please contact technical support."

[0110] Log recording allows external human-computer interaction devices or target terminal devices to write detailed information about the failure (such as the time of failure, current step, and error code) to local storage or upload it to the server when the maximum retry threshold for enabling accessibility services has been reached. For example, in a retail scenario, for auxiliary payment devices, the failure log (containing "three retries failed, the last one received an unauthorized status") is packaged and encrypted, and then uploaded to the cloud server for analysis by operations and maintenance personnel when the network is restored.

[0111] For example, after sending a simulated keyboard command, the assistive payment device waits a moment and then sends another accessibility service authorization status query request to the POS machine for the "Quick Payment Plugin". If the query result from the POS machine shows that it is still not enabled, the assistive payment device increments its internal counter by 1 and compares the current counter value with the retry threshold (preset to 3 times). Assuming this is the first failure, the assistive payment device will resend the accessibility application list page enable request to restart the automated process. If the counter reaches 3 times and the last query result is still not enabled, the assistive payment device terminates the retry, controls its own buzzer to sound an alarm, and pops up an alarm message on the POS machine interface saying "Accessibility function configuration failed, please manually check system settings," while simultaneously recording the complete error stack in the log file.

[0112] In the embodiments described in this specification, a retry mechanism is added after the simulated keyboard command is executed, and alarm and log recording operations are introduced in combination with the retry number threshold. This constructs a closed-loop control logic with anomaly detection and fault self-healing capabilities. While further improving the success rate of enabling accessibility services, it avoids system deadlock caused by infinite retries, ensures timely and effective intervention in extreme cases, and improves automation efficiency and system stability.

[0113] In one optional embodiment of this specification, the external human-computer interaction device is a near-field communication external human-computer interaction device, the target terminal device is a cash register device, and the bidirectional communication channel is a bidirectional communication channel for small instruction software development data packets.

[0114] External human-machine interface devices (HMIs) with near-field communication (NFC) can be external hardware devices with built-in NFC modules that support short-range secure communication with target terminal devices via contactless RFID or point-to-point data transmission. For example, in retail scenarios, this corresponds to auxiliary payment devices that plug into a POS machine's USB port or connect wirelessly via Bluetooth / WiFi, support HID protocols, and have bidirectional communication capabilities.

[0115] POS devices can be dedicated electronic devices deployed in commercial retail locations to scan product barcodes, calculate transaction amounts, and process payment settlements. For example, in a retail setting, this corresponds to an Android smart POS machine or desktop POS terminal running at the merchant's front desk.

[0116] The Software Development Kit (SDK) is a pre-installed background service program in POS devices, handling near-field communication data parsing, hardware-software interaction, and lightweight service logic. As middleware, the SDK bridges the upper-layer Software as a Service (SaaS) service with the underlying hardware. After obtaining accessibility service functionality, it can listen to and acquire input information (such as product barcodes or card numbers) generated by external input devices (such as barcode scanners or physical keyboards) on the target terminal device, and inject this input information into the currently focused input box, thereby achieving automated data collection without manual input. For example, in a retail scenario, this corresponds to the "Quick Payment Plugin" SDK, which is responsible for parsing the encrypted card number transmitted by the auxiliary payment device and injecting it into the payment input box.

[0117] A bidirectional communication channel can be a logical path for full-duplex data exchange between external human-machine interface devices (HID) and point-of-sale (POS) devices, established based on small instruction software development data packages and supporting near-field communication. For example, in a retail scenario, this corresponds to a bidirectional data transmission pipeline established between an auxiliary payment device and a POS machine via a USB data cable, supporting the multiplexing of the HID protocol and the proprietary small instruction protocol.

[0118] For example, in a retail scenario, an Android smart POS machine (cash register) running at the merchant's front end is connected to an auxiliary payment device supporting near-field communication via Bluetooth. A bidirectional communication channel for the small instruction software development data package is established by reusing the Human-Machine Interface (HID) protocol and the small instruction private protocol. Upon the first startup each day or after a system update, the auxiliary payment device detects that the accessibility function of the pre-installed "Quick Payment Plugin" (small instruction SDK) is not configured, automatically launches the POS machine's accessibility settings page, and activates the accessibility service function by issuing simulated keyboard commands.

[0119] When a customer checks out, the cashier uses an external barcode scanner to scan a bottle of mineral water purchased by the customer. Because the Mini-Instruction SDK has its accessibility service enabled, it can listen to and obtain the scanning events from the external barcode scanner at the system level of the POS device, thereby obtaining the standard product code scanned by the scanner. This compensates for the deficiency in conventional POS settlement, where only the merchant's self-maintained product internal code is uploaded to the server, resulting in the server's inability to identify the specific product type. Subsequently, the Mini-Instruction SDK sends the product code to the auxiliary payment device through an established two-way communication channel. After receiving the product code, the auxiliary payment device uploads it and the order number to the server. Upon receiving the data, the server matches it against the product database, identifies the product as "purified water," and then checks the user account associated with the order number to find a voucher for that type of purified water. The server then issues a rights verification instruction and the final settlement value. This means that even if the POS device sends a merchant-defined product code to the server, the auxiliary payment device can send the obtained standard product code information to the server. The server can then determine the applicable coupons and other benefits for the current transaction based on the obtained standard product code, improving payment accuracy. On the other hand, the POS device's small instruction SDK can also send settlement amount and other information to the auxiliary payment device. This allows the auxiliary payment device to send transaction information such as amount to the server. This information can be used to complete incomplete transaction information sent by the POS device, or to verify the information sent by the POS device, further improving transaction accuracy.

[0120] In the embodiments of this specification, the external human-computer interaction device is limited to a near-field communication external human-computer interaction device, the target terminal device is limited to a cash register device, and the bidirectional communication channel is a bidirectional communication channel of the small instruction software development data package. By utilizing the characteristics of the small instruction software development data package as a system-level middleware, the stable execution of the subsequent lightweight cash register service is ensured. This not only eliminates the cumbersome process of manual configuration of functions, but also significantly improves the accuracy of interaction and automation efficiency in the cash register scenario through the software and hardware collaboration mechanism, thereby enhancing the user's cash register experience.

[0121] The various technical features in the above embodiments can be combined arbitrarily, as long as there is no conflict or contradiction between the combinations of features. However, due to space limitations, they have not been described one by one. Therefore, the arbitrary combination of various technical features in the above embodiments is also within the scope of this specification.

[0122] Figure 3 This is a flowchart of another control method for an accessibility service function provided in an embodiment of this specification. The execution subject of this process can be a target terminal device, and a two-way communication channel is established between the target terminal device and an external human-computer interaction device.

[0123] like Figure 3 As shown, the process may include the following steps: Step 302: Receive the accessibility application list page opening request sent by the external human-computer interaction device.

[0124] Step 304: In response to the accessibility application list page opening request, display the accessibility application list page.

[0125] Step 306: Receive simulated keyboard commands sent by the external human-computer interaction device after the accessibility application list page has been rendered.

[0126] Step 308: In response to the simulated keyboard command, perform an operation to enable accessibility services on the accessibility application list page to enable the accessibility service function.

[0127] The embodiments in this specification are the same as those described above. Figure 2 The embodiments correspond to those in the specification, the difference being that the executing entity is the target terminal device, and the execution logic of the simulated keyboard commands and interface responses is the same as that described above. Figure 2 In this embodiment, the simulated keyboard commands sent by the external human-computer interaction device match the interface response. This has already been stated above. Figure 2 The detailed descriptions of instruction construction, key-value code definition, delay mechanism, and full-process interaction logic on the external device side in the embodiments will not be repeated here.

[0128] While one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is merely one possible execution order among many steps and does not represent the only possible execution order. The order of some steps may be adjusted according to actual needs, or some steps may be omitted. When the claims involve method steps, changes in the order of such steps, or parallel execution between steps, are also within the scope of protection of the claims.

[0129] Figure 3 The method described herein utilizes the keyboard simulation capability of the external human-computer interaction device and its bidirectional communication capability with the target terminal device to send an accessibility application list page opening request to the target terminal device and receive the page rendering status. After the page is ready, standardized simulated keyboard commands are injected to automatically navigate and execute the opening operation. By automating and standardizing the opening of accessibility services through the external human-computer interaction device, convenience and efficiency are improved, and operation and maintenance costs are reduced.

[0130] based on Figure 3 In addition to the method described herein, this specification also provides some specific implementation methods of the method, which will be described below.

[0131] In one optional embodiment of this specification, the simulated keyboard instructions include a first simulated keyboard instruction, a second simulated keyboard instruction, and a third simulated keyboard instruction; The step of responding to the simulated keyboard command by performing an accessibility service authorization operation on the accessibility application list page and enabling the accessibility service function includes: In response to the first simulated keyboard command, the target application for which the accessibility service function is to be enabled is selected from the accessibility application list page, and the accessibility service opening page for the target application is displayed; In response to the second simulated keyboard command, the enable radio button is selected from the accessibility service open page, and the accessibility service authorization pop-up is displayed; In response to the third simulated keyboard command, select the confirmation control from the accessibility service authorization pop-up to enable the accessibility service function.

[0132] The embodiments in this specification are the same as those described above. Figure 2 The embodiments correspond to those in the specification, the difference being that the executing entity is the target terminal device, and the parsing and execution logic of the simulated keyboard instructions is the same as that described above. Figure 2 In the embodiment, the sequence of instructions sent by the external human-computer interaction device matches. This has been stated above. Figure 2 The detailed description of the instruction sequence sent by the external human-computer interaction device in the embodiment will not be repeated here.

[0133] In the embodiments described in this specification, by pre-setting parsing and execution logic that matches the first, second, and third simulated keyboard commands, the target terminal device can accurately respond to the simulated keyboard commands injected by the external human-computer interaction device, and automatically complete each stage of the accessibility service activation process without human intervention, ensuring the accuracy of cross-device interaction and the continuity of process execution, and further improving the compatibility and reliability of the automated authorization process.

[0134] In one optional embodiment of this specification, before receiving the accessibility application list page opening request sent by the external human-computer interaction device, the method further includes: Receive the accessibility service function authorization status query request sent by the external human-computer interaction device; The system detects the current authorization status of the accessibility service and sends the query results back to the external human-computer interaction device.

[0135] The embodiments in this specification are the same as those described above. Figure 2 The embodiments correspond to those in the specification, the difference being that the executing entity is the target terminal device, and the processing logic of the authorization status query request is the same as that described above. Figure 2 In this embodiment, the query request sent by the external human-computer interaction device matches. This has been stated above. Figure 2 The details of the query requests sent by the external human-computer interaction device in the embodiments are not repeated here.

[0136] In the embodiments described in this specification, by responding to the authorization status query request of the external human-computer interaction device and feeding back the detection result, the target terminal device can cooperate with the external device to realize the pre-verification and dynamic decision of the authorization status, avoid performing redundant page jumps and simulation operations in the authorized state, reduce system resource consumption, and improve the efficiency and intelligence level of device interaction.

[0137] Based on the above description, the embodiments of this specification provide a practical application scenario, Figure 4 This specification provides a flowchart of a method for controlling accessibility service functions in a practical application scenario, as an embodiment of the present invention. Figure 4 As shown.

[0138] Step 402: When the auxiliary payment device receives the accessibility service activation instruction from the server, or detects that the mini-instruction SDK is not authorized, it sends an accessibility service function authorization status query request to the target terminal device through the bidirectional communication channel of the mini-instruction SDK.

[0139] The bidirectional communication channel of the Mini-Instruction Software Development Kit (SDK) enables the auxiliary payment device and the POS machine to establish a logical data link through their respective pre-built Mini-Instruction SDKs. This bidirectional communication channel reuses the Human-Machine Interface (HID) protocol to simulate keyboard commands, while simultaneously overlaying the Mini-Instruction SDK's proprietary protocol for transmitting authorization status queries and feedback, thereby enabling the auxiliary payment device to precisely control and perceive the status of the POS machine.

[0140] Step 404: The POS machine detects the current accessibility service authorization status through the bidirectional communication channel of the mini-instruction SDK, and sends the query results back to the auxiliary payment device through the bidirectional communication channel of the mini-instruction SDK.

[0141] Step 406: The auxiliary payment device receives the query result from the POS machine through the bidirectional communication channel of the mini-instruction SDK. If the query result indicates that the accessibility service function is not enabled, the auxiliary payment device sends a request to the POS machine to enable the accessibility application list page through the bidirectional communication channel of the mini-instruction SDK.

[0142] Step 408: The POS machine receives a request from the auxiliary payment device to open the accessibility application list page through the bidirectional communication channel of the small instruction SDK.

[0143] Step 410: The POS machine responds to the accessibility application list page opening request and displays the accessibility application list page.

[0144] Step 412: After a first preset time delay to allow the accessibility application list page to finish rendering, the auxiliary payment device sends a first simulated keyboard instruction to the POS machine through the bidirectional communication channel of the small instruction SDK. The first simulated keyboard instruction includes at least the key value code of the focus switching key instruction, the key value code of the direction control key instruction, and the key value code of the confirmation selection key instruction.

[0145] Step 414: The POS machine responds to the first simulated keyboard command, selects the Mini-Command SDK from the accessibility application list page, and displays the Mini-Command SDK's accessibility service open page.

[0146] Step 416: After a second preset time delay to allow the accessibility service page to finish rendering, the auxiliary payment device sends a second simulated keyboard instruction to the POS machine through the bidirectional communication channel of the small instruction SDK. The second simulated keyboard instruction includes at least the key value code of the focus switching key instruction, the key value code of the direction control key instruction, and the key value code of the confirmation selection key instruction.

[0147] Step 418: The POS machine responds to the second simulated keyboard command, selects the Enable radio button from the Accessibility Services page, and displays the Accessibility Services Authorization pop-up.

[0148] Step 420: After a third preset time delay to allow the accessibility service authorization pop-up to complete rendering, the auxiliary payment device sends a third simulated keyboard instruction to the POS machine through the bidirectional communication channel of the small instruction SDK. The third simulated keyboard instruction includes at least the key value code of the focus switching key instruction, the key value code of the direction control key instruction, and the key value code of the confirmation selection key instruction.

[0149] Step 422: The POS machine responds to the third simulated keyboard command, selects and confirms the enable control from the accessibility service authorization pop-up, and enables the accessibility service function.

[0150] In the embodiments of this specification, a fully automated accessibility service activation scheme is constructed by leveraging the bidirectional communication capabilities between the deep collaborative auxiliary payment device and the POS machine, as well as the keyboard simulation capabilities of the auxiliary payment device based on the Human-Computer Interaction (HID) protocol. This scheme solves the high-cost path of manually activating accessibility services and enables automated and standardized activation of accessibility services through external HID devices without human intervention, thereby improving convenience and efficiency and reducing operation and maintenance costs.

[0151] With the above Figure 4 Corresponding to the embodiments, Figure 5 This is a schematic diagram illustrating a control method for accessibility service functions in a practical application scenario, provided as an embodiment of this specification.

[0152] like Figure 5As shown, this illustrates the process logic of different functional modules and operational steps in the context of accessibility service function control for devices such as POS machines. The assisted payment device sends a request to open the accessibility application list page; the POS system responds to the request and displays the accessibility application list page, which clearly presents various available applications (including accessibility services, application A, application B, mini-program applications, and snack applications); the assisted payment device sends a first simulated keyboard command to accurately locate and trigger the target application (such as "mini-program application") in the list page, causing the system interface to jump to the operation interface of the mini-program application; the assisted payment device sends a second simulated keyboard command to trigger a specific interactive action in the mini-program application interface, waking up the accessibility service authorization pop-up, which displays the prompt "Allow the quick payment plugin to monitor your operation?" and provides two operation options: "Cancel" and "Confirm"; the assisted payment device sends a third simulated keyboard command to simulate the user's final confirmation operation (i.e., clicking the confirmation button in the pop-up), completing the subsequent interactive actions related to accessibility service authorization. The entire process revolves around the opening and authorization of accessibility services, using simulated keyboard commands to transmit operation instructions between different functional modules, realizing a complete logical closed loop from the list page opening request to the authorization pop-up interaction.

[0153] With the above Figure 4 Corresponding to the embodiments, Figure 6 This is a timing diagram illustrating a control method for accessibility service functions in a practical application scenario, provided as an embodiment of this specification. Figure 6 As shown, it includes the following steps: 1. The auxiliary payment device sends a request to open the obstacle application list page to the POS machine's small instruction SDK through the small instruction bidirectional communication channel.

[0154] 2. The POS machine displays a list of accessibility applications.

[0155] Upon receiving the aforementioned request, the POS machine's small instruction SDK can control the POS machine to display the accessibility application list page.

[0156] 3. The POS machine mini-command SDK returns the results of the accessibility application list page to the auxiliary payment device.

[0157] 4. The auxiliary payment device sends the first simulated keyboard command to the POS machine's small command SDK.

[0158] 5. The POS machine displays the accessibility service page of the small instruction SDK.

[0159] Upon receiving the aforementioned request, the POS machine's small instruction SDK can control the POS machine to display the accessibility service opening page.

[0160] 6. The auxiliary payment device sends a second simulated keyboard command to the POS machine's small command SDK.

[0161] 7. When the POS machine opens the Accessibility Services page, select the Enable radio button to display the Accessibility Services Authorization pop-up.

[0162] Upon receiving the aforementioned request, the POS machine's small instruction SDK can control the POS machine to display an accessibility service authorization pop-up.

[0163] 8. The auxiliary payment device sends third simulated keyboard commands to the POS machine's small command SDK.

[0164] 9. Select "Confirm Enable Control" in the accessibility service authorization pop-up window on the POS machine to enable the accessibility service function.

[0165] Based on the same idea, this specification also provides a device interaction system corresponding to the above method in its embodiments.

[0166] Corresponding to Figure 2 and Figure 3 , Figure 7 This is a schematic diagram of the structure of a device interaction system provided in one embodiment of this specification.

[0167] like Figure 7 As shown, the device interaction system 100 may include an external human-computer interaction device 101 and a target terminal device 102, and a two-way communication channel is established between the external human-computer interaction device 101 and the target terminal device 102. The external human-computer interaction device 101 is used to send a request to the target terminal device 102 to open the accessibility application list page. The target terminal device 102 is used to receive the accessibility application list page opening request sent by the external human-computer interaction device 101, and in response to the accessibility application list page opening request, display the accessibility application list page. The external human-computer interaction device 101 is used to send simulated keyboard commands to the target terminal device 102 when the accessibility application list page is rendered. The target terminal device 102 is used to receive the simulated keyboard command sent by the external human-computer interaction device 101, and in response to the simulated keyboard command, perform an operation to enable accessibility service on the accessibility application list page, thereby enabling the accessibility service function.

[0168] based on Figure 7 The device interaction system described in this specification also provides some specific implementation schemes of the method, which are described below.

[0169] Optionally, the simulated keyboard commands include at least one of focus switching key commands, directional control key commands, and confirmation selection key commands.

[0170] Optionally, the simulated keyboard commands are generated based on a human-computer interaction device protocol; The focus switching button instruction, the direction control button instruction, and the confirm selection button instruction each correspond to a key value code; The external human-computer interaction device pre-stores the interface layout information of the accessibility application list page of the target terminal device, and determines the key value code or key value code combination to be sent based on the current focus position and the position of the target control.

[0171] Optionally, the simulated keyboard instructions include a first simulated keyboard instruction, a second simulated keyboard instruction, and a third simulated keyboard instruction; The external human-computer interaction device 101 is specifically used to send the first simulated keyboard command to the target terminal device 102; The target terminal device 102 is specifically used to respond to the first simulated keyboard command, select the target application whose accessibility service function is to be enabled from the accessibility application list page, and display the accessibility service opening page for the target application; The external human-computer interaction device 101 is specifically used to send the second simulated keyboard command to the target terminal device 102; The target terminal device 102 is specifically used to respond to the second simulated keyboard command, select the enable radio button from the accessibility service opening page, and display the accessibility service authorization pop-up; The external human-computer interaction device 101 is specifically used to send the third simulated keyboard command to the target terminal device 102. The target terminal device 102 is specifically used to respond to the third simulated keyboard command, select the confirmation control from the accessibility service authorization pop-up, and enable the accessibility service function.

[0172] Optionally, the external human-computer interaction device 101 is specifically used to send the first simulated keyboard command to the target terminal device 102 after a first preset time delay to allow the rendering of the accessibility application list page to be completed. The external human-computer interaction device 101 is specifically used to send the second simulated keyboard command to the target terminal device 102 after a second preset time delay to allow the rendering of the accessibility service opening page to be completed. The external human-computer interaction device 101 is specifically used to send the third simulated keyboard command to the target terminal device 102 after a third preset time delay to allow the rendering of the accessibility service authorization pop-up.

[0173] Optionally, the external human-computer interaction device 101 is further configured to send an accessibility service authorization status query request to the target terminal device 102 when it receives an accessibility service activation instruction from the server or detects that the target application is not authorized. The target terminal device 102 receives an authorization status query request for the accessibility service function sent by the external human-computer interaction device 101; detects the current authorization status of the accessibility service, and feeds back the query result to the external human-computer interaction device 101; The external human-computer interaction device 101 is also used to receive the query results fed back by the target terminal device 102; The external human-computer interaction device 101 is specifically used to send a request to the target terminal device 102 to enable the accessibility application list page if the query result indicates that the accessibility service function is not enabled.

[0174] Optionally, the external human-computer interaction device 101 is further configured to receive accessibility service activation status information fed back by the target terminal device 102, so as to determine whether the accessibility service function has been successfully activated; if the accessibility service function has not been successfully activated, the process returns to the step of sending the accessibility application list page activation request.

[0175] Optionally, the external human-computer interaction device 101 is further configured to determine whether a preset retry threshold has been reached if the query result indicates that the accessibility service function is not enabled; if the retry threshold has not been reached, return to the step of sending the accessibility application list page enable request; if the retry threshold has been reached, execute a preset alarm operation and / or log recording operation.

[0176] Optionally, the external human-computer interaction device 101 is a near-field communication external human-computer interaction device 101, the target terminal device 102 is a cash register device, and the bidirectional communication channel is a bidirectional communication channel for small instruction software development data packets.

[0177] It is understood that the modules mentioned above refer to computer programs or program segments used to perform one or more specific functions. Furthermore, the distinction between these modules does not imply that the actual program code must also be separate.

[0178] For ease of description, the above device interaction system is described by dividing it into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units. The device interaction system embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0179] The above is an illustrative scheme of a device interaction system according to this embodiment. It should be noted that the technical solution of this device interaction system and the technical solution of the above-mentioned accessibility service function control method belong to the same concept. For details not described in detail in the technical solution of the device interaction system, please refer to the description of the technical solution of the above-mentioned accessibility service function control method.

[0180] Based on the same idea, the embodiments of this specification also provide computing devices corresponding to the above methods.

[0181] Figure 8 A structural block diagram of a computing device provided in one embodiment of this specification is shown.

[0182] The computing device 800 includes: Memory 810 and processor 820; The memory 810 is used to store computer programs / instructions, and the processor 820 is used to execute the computer programs / instructions, which, when executed by the processor 820, implement the steps of the control method for the accessibility service function.

[0183] Specifically, the components of the computing device 800 include, but are not limited to, a memory 810 and a processor 820. The processor 820 is connected to the memory 810 via a bus 830, and the database 850 is used to store data.

[0184] The computing device 800 also includes an access device 840, which enables the computing device 800 to communicate via one or more networks 860. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 840 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0185] In one embodiment of this specification, the above-described components of the computing device 800 and Figure 8 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 8 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0186] The computing device 800 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 800 can also be a mobile or stationary server.

[0187] The steps of the control method for implementing the accessibility service function when the processor 820 executes the computer instructions are described.

[0188] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the above-described accessibility service function control method belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above-described accessibility service function control method.

[0189] An embodiment of this specification also provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the control method for the accessibility service function as described above.

[0190] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the above-described accessibility service function control method belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the above-described accessibility service function control method.

[0191] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the control method for the above-described accessibility service function.

[0192] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-mentioned accessibility service function control method belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the above-mentioned accessibility service function control method.

[0193] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the device interaction system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions of the method embodiments. The device interaction system and method provided in the embodiments of this specification correspond to each other; therefore, the device interaction system also has similar beneficial technical effects as the corresponding method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the corresponding device interaction system will not be repeated here.

[0194] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0195] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0196] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0197] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0198] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0199] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, the invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0200] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0201] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0202] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0203] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0204] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0205] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital character versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0206] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0207] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A control method for an accessibility service function, applied to an external human-computer interaction device, wherein a bidirectional communication channel is established between the external human-computer interaction device and a target terminal device, comprising: Send an accessibility application list page enable request to the target terminal device so that the target terminal device displays the accessibility application list page; Once the accessibility application list page has finished rendering, a simulated keyboard command is sent to the target terminal device, causing the target terminal device to respond to the simulated keyboard command and perform an operation to enable accessibility services on the accessibility application list page, thereby enabling the accessibility service function.

2. The method of claim 1, wherein, The simulated keyboard commands include at least one of the following: focus switching key commands, directional control key commands, and confirmation selection key commands.

3. The method of claim 2, wherein, The simulated keyboard commands are generated based on the human-computer interaction device protocol; The focus switching button instruction, the direction control button instruction, and the confirm selection button instruction each correspond to a key value code; Based on the current focus position information and target control position information in the accessibility application list page or its subpage, determine the key value code or key value code combination to be sent. The focus switching button instruction is generated based on the current focus position information and the target control position information; the focus switching button instruction contains a key value code or key value code combination that can be recognized by the target terminal device for performing focus switching; The directional control button instruction is generated based on the position information of the current focus and the position information of the target control; the directional control button instruction contains a key value code or key value code combination that can be recognized by the target terminal device for directional control; The confirmation selection button instruction is generated based on the current focus position information and the target control position information; the confirmation selection button instruction contains a key value code or key value code combination that can be recognized by the target terminal device for confirming the selection.

4. The method of claim 1, wherein, The simulated keyboard commands include a first simulated keyboard command, a second simulated keyboard command, and a third simulated keyboard command; Sending a simulated keyboard command to the target terminal device, causing the target terminal device to respond to the simulated keyboard command and perform an operation to enable accessibility services on the accessibility application list page, thereby enabling the accessibility service function, includes: Send the first simulated keyboard command to the target terminal device so that the target terminal device responds to the first simulated keyboard command, selects the target application whose accessibility service function is to be enabled from the accessibility application list page, and displays the accessibility service opening page for the target application; Send the second simulated keyboard instruction to the target terminal device so that the target terminal device responds to the second simulated keyboard instruction, selects the enable radio button from the accessibility service opening page, and displays the accessibility service authorization pop-up; The third simulated keyboard instruction is sent to the target terminal device, so that the target terminal device responds to the third simulated keyboard instruction, selects the confirmation control from the accessibility service authorization pop-up, and enables the accessibility service function.

5. The method according to claim 4, wherein sending the first simulated keyboard command to the target terminal device comprises: While delaying for a first preset time to allow the accessibility application list page to complete rendering, the first simulated keyboard instruction is sent to the target terminal device. Sending the second simulated keyboard command to the target terminal device includes: While delaying for a second preset time to allow the accessibility service open page to complete rendering, the second simulated keyboard command is sent to the target terminal device; Sending the third simulated keyboard command to the target terminal device includes: While delaying for a third preset time to allow the accessibility service authorization pop-up to complete rendering, the third simulated keyboard command is sent to the target terminal device.

6. The method according to claim 1, further comprising, before sending the accessibility application list page opening request to the target terminal device: Upon receiving an accessibility service activation command from the server, or upon detecting that the target application is not authorized, a request for accessibility service function authorization status query is sent to the target terminal device. Receive the query results fed back by the target terminal device; Sending the accessibility application list page opening request to the target terminal device includes: If the query result indicates that accessibility services are not enabled, a request to enable the accessibility application list page is sent to the target terminal device.

7. The method according to claim 1, further comprising, after sending the simulated keyboard command to the target terminal device: Receive accessibility service activation status information from the target terminal device to determine whether the accessibility service function has been successfully activated; If the accessibility service function is not successfully enabled, return to the step of sending the accessibility application list page enable request.

8. The method according to claim 7, wherein if the accessibility service function is not successfully enabled, the step of sending the request to enable the accessibility application list page is returned, comprising: If the query result indicates that the accessibility service function is not enabled, then determine whether the preset retry threshold has been reached. If the retry threshold is not reached, return to the step of sending the accessibility application list page enable request; If the retry count threshold is reached, a preset alarm operation and / or log recording operation will be performed.

9. The method according to claim 1, wherein the external human-computer interaction device is used for near-field communication, the target terminal device is a cash register device, and the bidirectional communication channel is a bidirectional communication channel for small instruction software development data packets.

10. A control method for an accessibility service function, applied to a target terminal device, wherein the target terminal device and an external human-computer interaction device establish a two-way communication channel, comprising: Receive a request from the external human-computer interaction device to open the accessibility application list page; In response to the accessibility application list page opening request, the accessibility application list page is displayed; Receive simulated keyboard commands sent by the external human-computer interaction device after the accessibility application list page has been rendered; In response to the simulated keyboard command, an operation to enable accessibility services is performed on the accessibility application list page, thereby enabling the accessibility service function.

11. The method of claim 10, wherein, The simulated keyboard commands include a first simulated keyboard command, a second simulated keyboard command, and a third simulated keyboard command; In response to the simulated keyboard command, the operation of enabling accessibility services on the accessibility application list page is performed, including: In response to the first simulated keyboard command, the target application for which the accessibility service function is to be enabled is selected from the accessibility application list page, and the accessibility service opening page for the target application is displayed; In response to the second simulated keyboard command, the enable radio button is selected from the accessibility service open page, and the accessibility service authorization pop-up is displayed; In response to the third simulated keyboard command, select the confirmation control from the accessibility service authorization pop-up to enable the accessibility service function.

12. The method according to claim 10, further comprising, before receiving the accessibility application list page opening request sent by the external human-computer interaction device: Receive the accessibility service function authorization status query request sent by the external human-computer interaction device; The system detects the current authorization status of the accessibility service and sends the query results back to the external human-computer interaction device.

13. A device interaction system, comprising an external human-computer interaction device and a target terminal device, wherein a bidirectional communication channel is established between the external human-computer interaction device and the target terminal device; The external human-computer interaction device is used to send a request to the target terminal device to open the accessibility application list page; The target terminal device is configured to receive the accessibility application list page opening request sent by the external human-computer interaction device, and in response to the accessibility application list page opening request, display the accessibility application list page. The external human-computer interaction device is used to send simulated keyboard commands to the target terminal device after the accessibility application list page has been rendered. The target terminal device is configured to receive simulated keyboard commands sent by the external human-computer interaction device, and in response to the simulated keyboard commands, perform an operation to enable accessibility services on the accessibility application list page, thereby enabling the accessibility service function.

14. A computing device, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the method according to any one of claims 1 to 12.

15. A computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 12.

16. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 12.

Images